RE: [TLS] extension number conflict
Stefan Santesson <stefans@microsoft.com> Fri, 09 February 2007 00:02 UTC
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HFJDN-0001ox-Dx; Thu, 08 Feb 2007 19:02:09 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HFJDI-0001lS-EB for tls@ietf.org; Thu, 08 Feb 2007 19:02:05 -0500
Received: from smtp-dub.microsoft.com ([213.199.138.191]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HFJCg-0003EH-Qr for tls@ietf.org; Thu, 08 Feb 2007 19:02:04 -0500
Received: from DUB-EXHUB-C301.europe.corp.microsoft.com (65.53.213.91) by DUB-EXGWY-E801.partners.extranet.microsoft.com (10.251.129.1) with Microsoft SMTP Server (TLS) id 8.0.685.24; Fri, 9 Feb 2007 00:01:25 +0000
Received: from EA-EXMSG-C307.europe.corp.microsoft.com ([65.53.221.19]) by DUB-EXHUB-C301.europe.corp.microsoft.com ([65.53.213.91]) with mapi; Fri, 9 Feb 2007 00:01:25 +0000
From: Stefan Santesson <stefans@microsoft.com>
To: Mike <mike-list@pobox.com>, "tls@ietf.org" <tls@ietf.org>
Date: Fri, 09 Feb 2007 00:01:16 +0000
Subject: RE: [TLS] extension number conflict
Thread-Topic: [TLS] extension number conflict
Thread-Index: AcdL2vIfXlI6Lu6oTDW6nUwD4HiggwAAhhdw
Message-ID: <A15AC0FBACD3464E95961F7C0BCD1FF01DA29082@EA-EXMSG-C307.europe.corp.microsoft.com>
References: <200702082259.XAA10273@uw1048.wdf.sap.corp> <45CBB5B5.9020305@pobox.com>
In-Reply-To: <45CBB5B5.9020305@pobox.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2
Cc:
X-BeenThere: tls@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "This is the mailing list for the Transport Layer Security working group of the IETF." <tls.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tls>, <mailto:tls-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/tls>
List-Post: <mailto:tls@lists.ietf.org>
List-Help: <mailto:tls-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tls>, <mailto:tls-request@lists.ietf.org?subject=subscribe>
Errors-To: tls-bounces@lists.ietf.org
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 _______________________________________________ TLS mailing list TLS@lists.ietf.org https://www1.ietf.org/mailman/listinfo/tls
- [TLS] extension number conflict Mike
- Re: [TLS] extension number conflict Russ Housley
- Re: [TLS] extension number conflict Martin Rex
- Re: [TLS] extension number conflict Mike
- RE: [TLS] extension number conflict Stefan Santesson
- RE: [TLS] extension number conflict Paul Hoffman
- RE: [TLS] extension number conflict Pasi.Eronen
- Re: [TLS] extension number conflict Mike
- Re: [TLS] extension number conflict tom.petch
- RE: [TLS] extension number conflict Stefan Santesson