[TLS] New Liaison Statement, "Response to "Request to reserve TLS extension type for ITU-T draft Recommendation X.tsm-1""

[Pasi Eronen (IETF TLS WG) <pasi.eronen at nokia.com>]

Title: Response to "Request to reserve TLS extension type for ITU-T draft Recommendation X.tsm-1"
Submission Date: 2007-05-11
URL of the IETF Web page: https://datatracker.ietf.org/public/liaison_detail.cgi?detail_id=328 

From: Pasi Eronen(IETF TLS WG) <pasi.eronen at nokia.com>
To: ITU-T SG 17(tsbsg17 at itu.int, xiaoya.yang at itu.int, sebek at itu.int)
Cc: tim.polk at nist.gov
hartmans-ietf at mit.edu
sob at harvard.edu
ekr at networkresonance.com
tls at ietf.org
Reponse Contact: 
Technical Contact: 
Purpose: In response 
Body: I have understood that Yoshiaiki Isobe contacted Harald Alvestrand
and Thomas Narten about this topic in December 2006; at that time,
Harald provided advice similar to the following.

RFC 4366 Section 5 defines the procedures for assigning a new TLS
extension type.  TLS extension types are assigned to
Internet-Drafts that have been approved by the IESG.

So, you need to publish your extension as an Internet-Draft and
seek review of your draft.  Once you have built a sufficient
consensus behind your draft, you can propose that your draft be
adopted by the TLS working group or published as an Area Director
(AD) sponsored submission.  Sections 3.2 and 4 of RFC 4775 provide
more details on the procedures for an SDO working with the IETF to
extend an IETF protocol in this way.  Note that because of the
requirements of RFC 4366, only the first option discussed in
Section 4 is available in this instance.

The TLS working group chairs and security ADs will be happy to
answer any process questions you may have as you attempt to build
consensus behind your draft.

Best regards,
Pasi Eronen
TLS working group co-chair
Attachment(s):
No document has been attached



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