On Tue, Oct 22, 2019 at 8:06 AM Stephen Farrell <stephen.farr...@cs.tcd.ie> wrote:
> > > On 22/10/2019 15:56, Ben Schwartz wrote: > > Sure. For example, tumblr limits usernames to 32 characters: > > https://unwrapping.tumblr.com/post/58535402323/tips-tumblr-username > > > > These usernames also form the subdomain part of the *.tumblr.com > > wildcard, so the longest allowed name is [32 chars].tumblr.com. > > > > I expect that most wildcard TLS hosts impose similar limits. > > > > Fair enough. Sub-domains (or whatever may be the right > term) can have such limits. However, IIUC most services > ilke hosters or CDNs will just allow anything that's a > valid DNS name so I argue that our design target ought > be to handle that well. (The current spec does handle > it, but not, IMO, well;-) On reflection, I’m not really comfortable with the code I’ve written on the client side. It does work, but I don’t think the DNS record should dictate the padding so precisely. I’d like my client to send 260 (or whatever the right number is) whenever possible. As specified, short TTLs and varying padding could be a problem. thanks, Rob >
_______________________________________________ TLS mailing list TLS@ietf.org https://www.ietf.org/mailman/listinfo/tls
