Re: [Acme] IDN encoding

2016-08-29 Thread Roland Bracewell Shoemaker
On 08/29/2016 04:36 PM, Richard Barnes wrote: > Yeah, there's no reason to use U-labels here. Let's just require that > the names be in ASCII. I don't think there's really a need to require > anything further than that (servers can do case folding). > That is what this patch does, but actuall

Re: [Acme] IDN encoding

2016-08-29 Thread Roland Bracewell Shoemaker
The referenced RFCs describe punycode encoding using the 'xn--' ACE prefix. On 08/29/2016 04:21 PM, Philipp Junghannß wrote: > shouldnt IDNs just get Punycoded? at least that's the common standard > for IDN stuff iirc. > > 2016-08-30 0:51 GMT+02:00 Roland Bracewell Shoemaker > mailto:rol...@letse

Re: [Acme] IDN encoding

2016-08-29 Thread Richard Barnes
Yeah, there's no reason to use U-labels here. Let's just require that the names be in ASCII. I don't think there's really a need to require anything further than that (servers can do case folding). Note that this only affects Authorization.identifier.value for Authorization.identifier.type == "d

Re: [Acme] IDN encoding

2016-08-29 Thread Philipp Junghannß
shouldnt IDNs just get Punycoded? at least that's the common standard for IDN stuff iirc. 2016-08-30 0:51 GMT+02:00 Roland Bracewell Shoemaker : > I'd be interested in hearing peoples thoughts about this PR which adds > language about how IDNs should be encoded by clients who wish to use > them a

[Acme] IDN encoding

2016-08-29 Thread Roland Bracewell Shoemaker
I'd be interested in hearing peoples thoughts about this PR which adds language about how IDNs should be encoded by clients who wish to use them as identifier values. https://github.com/ietf-wg-acme/acme/pull/184 ___ Acme mailing list Acme@ietf.org http

[Acme] FW: NomCom 2016-2017: Call for Nominations

2016-08-29 Thread Salz, Rich
In particular, Stephen isn't re-upping, so there's an opening in the Security Area. -- Senior Architect, Akamai Technologies IM: richs...@jabber.at Twitter: RichSalz -Original Message- From: NomCom Chair 2016 [mailto:nomcom-chair-2...@ietf.org] Sent: Monday, August 29, 2016 4:37 PM T

Re: [Acme] Terms of service agreement changes

2016-08-29 Thread Salz, Rich
Okay, then. We'll see if we can get consensus during early September. -- Senior Architect, Akamai Technologies IM: richs...@jabber.at Twitter: RichSalz > -Original Message- > From: Jacob Hoffman-Andrews [mailto:j...@eff.org] > Sent: Monday, August 29, 2016 2:36 PM > To: Salz, Rich; R

Re: [Acme] Terms of service agreement changes

2016-08-29 Thread Jacob Hoffman-Andrews
I disagree strongly on this. I've been on vacation last week, and will be on vacation through Sep 5, but happy to resume the conversation when I get back. On 08/26/2016 02:47 PM, Salz, Rich wrote: >> I'd like to try to close the loop on this. I'm hearing pretty broad >> agreement here on a few p