[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]


To: "'Patrick'" <patrick@gandi.net>, ietf-provreg@cafax.se
From: "Hollenbeck, Scott" <shollenbeck@verisign.com>
Date: Thu, 17 Jan 2002 19:33:26 -0500
Sender: owner-ietf-provreg@cafax.se
Subject: RE: <info> Command and authInfo

> -----Original Message-----
> From: Patrick [mailto:patrick@gandi.net]
> Sent: Thursday, January 17, 2002 5:30 PM
> To: ietf-provreg@cafax.se
> Subject: Re: <info> Command and authInfo
> 
> 
> But again, we shifted, my main point was having auth info used not
> only for transfer but for other tasks. Or at least having the
> _protocol_ not forbidding things, that a policy may wish to better
> control.

OK, here's my angst: we _had_ this in the protocol once before, and no one
objected to changing things to where they are now.  If there's a strong
desire to revisit that decision, I'd really like to see a lot more support
for putting it back in before I spend the time putting text back in what I
had to rip out last year.

So, I'd like to ask a basic question assuming that the compromise position
on the <info> command has already been accepted:

Should we put auth info back into the base protocol for possible use with
any transform command or not?

-Scott-

[1]
http://www.cafax.se/ietf-provreg/maillist/2001-04/msg00138.html

Home | Date list | Subject list