Re: [TLS] extension number conflict

You (plural) might want to look at BCP 100.

Tom Petch

----- Original Message -----
From: "Stefan Santesson" <stefans@microsoft.com>
To: "Mike" <mike-list@pobox.com>; <tls@ietf.org>
Sent: Friday, February 09, 2007 1:01 AM
Subject: RE: [TLS] extension number conflict

What about assigning an experimental/local range that can be used until the real
number is assigned.
That should avoid conflicts effectively.

Stefan Santesson
Senior Program Manager
Windows Security, Standards

> -----Original Message-----
> From: Mike [mailto:mike-list@pobox.com]
> Sent: den 8 februari 2007 15:44
> To: tls@ietf.org
> Subject: Re: [TLS] extension number conflict
>
> >> IANA makes assignments when the documents are approved.  It should
> >> have "TBD" in the document until that happens.
> >
> > Personally, I think that is somewhat late.
>
> I agree.  I had to disable the code that implements this feature
> since there is no way to access it.  This makes it difficult to
> test, especially between differing implementations.
>
> For a feature that will obviously be approved, shouldn't there
> be a way to assign it a number sooner than RFC publication?
>
> Mike
>
>

_______________________________________________
TLS mailing list
TLS@lists.ietf.org
https://www1.ietf.org/mailman/listinfo/tls