Re: [TLS] extension number conflict
Martin Rex <martin.rex@sap.com> Thu, 08 February 2007 23:00 UTC
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HFIFF-0004dF-80; Thu, 08 Feb 2007 18:00:01 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HFIFD-0004d8-Gc for tls@ietf.org; Thu, 08 Feb 2007 17:59:59 -0500
Received: from smtpde02.sap-ag.de ([155.56.68.170]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HFIFB-0001yV-JS for tls@ietf.org; Thu, 08 Feb 2007 17:59:59 -0500
Received: from sap-ag.de (smtpde02) by smtpde02.sap-ag.de (out) with ESMTP id XAA24559; Thu, 8 Feb 2007 23:59:51 +0100 (MEZ)
From: Martin Rex <martin.rex@sap.com>
Message-Id: <200702082259.XAA10273@uw1048.wdf.sap.corp>
Subject: Re: [TLS] extension number conflict
To: housley@vigilsec.com
Date: Thu, 08 Feb 2007 23:59:50 +0100
In-Reply-To: <E1HFC6a-0001JJ-Rj@megatron.ietf.org> from "Russ Housley" at Feb 8, 7 11:26:28 am
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
X-SAP: out
X-SAP: out
X-SAP: out
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 1ac7cc0a4cd376402b85bc1961a86ac2
Cc: tls@ietf.org
X-BeenThere: tls@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: martin.rex@sap.com
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
Russ Housley wrote: > > 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. How about defining a process to "last call" whether a feature should be added to the next revision of a document/protocol standards so that IANA could issue a number before the actual document gets last called -- so that implementors will not have to change code later on. -Martin _______________________________________________ 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