Re: Last Call: Upgrading to TLS Within HTTP/1.1 to Proposed Standard

Jeffrey Schiller (jis@mit.edu)
Wed, 13 Oct 1999 03:54:57 +0100 (BST) 

I didn't realize you were waiting for me to approve. Please do make=20
the necessary changes and submit a new document.

				-Jeff

>>>>>>>>>>>>>>>>>> Original Message <<<<<<<<<<<<<<<<<<

On 9/22/99, 5:23:55 PM, "Scott Lawrence" <lawrence@agranat.com> wrote=20
regarding Re: Last Call: Upgrading to TLS Within HTTP/1.1 to Proposed=20
Standard:


> > >The IESG has received a request from the Transport Layer Security
> > >Working Group to consider Upgrading to TLS Within HTTP/1.1
> > ><draft-ietf-tls-http-upgrade-02.txt> as a Proposed Standard.

> > >To: iesg@ietf.org, IETF-Announce:;
> > >From: Harald Tveit Alvestrand <Harald@Alvestrand.no>
> > >Subject: Re: Last Call: Upgrading to TLS Within HTTP/1.1 to Propose=
d
> > >   Standard
> [...]
> >IANA considerations section for upgrade tokens is not thought=20
through.
> >At the least, the registrant should be allowed to change the contact
> details
> >for a registration, so the statement
> >
> >  > 1. The registration for a given token MUST NOT be changed once
> registered.
> >
> >is obviously not what's desired.
> >
> >I'd suggest the following rules:
> >
> >1. A token, once registered, stays registered forever.
> >2. The registration MUST name a responsible party for the=20
registration.
> >3. The registration MUST name a point of contact.
> >4. The registration MAY name the documentation required for the=20
token.
> >5. The responsible party MAY change the registration at any time. The=

> >     IANA will keep a record of all such changes, and make them
> available
> >     upon request.
> >6. The responsible party for the first registration of a "product"
> token
> >     MUST approve later registrations of a "version" token together
> with that
> >     "product" token before they can be registered.
> >7. If absolutely required, the IESG MAY reassign the responsibility=20
for
> >     a token. This will normally only be used in the case when a
> responsible
> >     party cannot be contacted.
> >
> >A lot more words, but I think it's more workable.

> An excellent formulation.  The authors will gratefully accept this as =

a
> friendly amendment if the IESG concurs.

> --
> Scott Lawrence           Director of R & D       =20
<lawrence@agranat.com>
> Agranat Systems, Inc.  Embedded Web Technology  =20
http://www.agranat.com/


> ---
> You are currently subscribed to ietf-tls as: [jis@mit.edu]
> To unsubscribe, forward this message to=20
leave-ietf-tls-557Y@lists.consensus.com