[TLS] Encoding of data for Server Name Indication?

To: tls mailing list <tls at ietf.org>
Subject: [TLS] Encoding of data for Server Name Indication?
From: Brad Hards <bradh at kdelabs.net>
Date: Wed, 13 Jun 2007 04:41:01 +1000
Cc:
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>
User-agent: KMail/1.9.1

I am working on some Qt code for TLS (that wraps OpenSSL and other libraries). 
We are planning to support the Server Name Indication extension (assuming 
that the underlying library also supports it), but have come up with an 
issue.

Based on 3280bis, the Certificate commonName and dNSName are supposed to be 
punycode encoded. Is SNI also supposed to be encoded with punycode?

Brad

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

Follow-Ups:
- RE: [TLS] Encoding of data for Server Name Indication?
  - From: Pasi.Eronen

Prev by Date: Re: [TLS] Straw poll on TLS SRP status
Next by Date: [TLS] I-D ACTION:draft-ietf-tls-srp-14.txt
Previous by thread: Re: [TLS] Patents and draft-housley-authz-extns-07 (fwd)
Next by thread: RE: [TLS] Encoding of data for Server Name Indication?
Index(es):
- Date
- Thread

[TLS] Encoding of data for Server Name Indication?

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