Re: [TLS] TLS extension

To: TLS at lists.ietf.org
Subject: Re: [TLS] TLS extension
From: Mike <mike-list at pobox.com>
Date: Sat, 20 Jan 2007 16:31:54 -0800
Cc:
In-reply-to: <003201c73cf0$537172f0$7ea95e41@pbo8f8e10aowa>
List-archive: <http://www1.ietf.org/pipermail/tls>
List-help: <mailto:tls-request@lists.ietf.org?subject=help>
List-id: "This is the mailing list for the Transport Layer Security working group of the IETF." <tls.lists.ietf.org>
List-post: <mailto:tls@lists.ietf.org>
List-subscribe: <https://www1.ietf.org/mailman/listinfo/tls>, <mailto:tls-request@lists.ietf.org?subject=subscribe>
List-unsubscribe: <https://www1.ietf.org/mailman/listinfo/tls>, <mailto:tls-request@lists.ietf.org?subject=unsubscribe>
References: <003201c73cf0$537172f0$7ea95e41@pbo8f8e10aowa>
User-agent: Thunderbird 1.5.0.9 (Windows/20061207)

What is the cleanest (or clean enough) way to extend TLS on server and on
the client? I recall reading in some posts about even an RFC to do it.


There is an extension mechanism, but you can't use it for private
extensions.  All extensions must be approved by the IETF since
they could compromise the security of TLS.  See RFC 4366.

Mike

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

Follow-Ups:
- Re: [TLS] TLS extension
  - From: home_pw

References:
- [TLS] TLS extension
  - From: Omirjan Batyrbaev

Prev by Date: [TLS] TLS extension
Next by Date: Re: [TLS] TLS extension
Previous by thread: [TLS] TLS extension
Next by thread: Re: [TLS] TLS extension
Index(es):
- Date
- Thread

Re: [TLS] TLS extension

Note: Messages sent to this list are the opinions of the senders and do not imply endorsement by the IETF.