Thanks, Corey. Updated the PR. On Thu, Aug 30, 2018 at 9:01 AM Corey Bonnell <cbonn...@trustwave.com> wrote:
> Hello, > > I just wanted to point out that RFC 5234 defines a core set of production > rules in Appendix B (https://tools.ietf.org/html/rfc5234#appendix-B) that > define commonly used rules such as “DIGIT”, “ALPHA”, etc. Using them would > make the base64url rule clearer: > > > > base64url = ALPHA / DIGIT / “-“ / “_” > > > > Thanks, > > Corey > > > > *From: *Acme <acme-boun...@ietf.org> on behalf of Richard Barnes > <r...@ipv.sx> > *Date: *Thursday, August 30, 2018 at 8:21 AM > *To: *"Manger, James H" <james.h.man...@team.telstra.com> > *Cc: *IETF ACME <acme@ietf.org> > *Subject: *Re: [Acme] Alexey Melnikov's No Objection on > draft-ietf-acme-acme-14: (with COMMENT) > > > > Thanks, James. Fixed in the PR. > > > > On Wed, Aug 29, 2018 at 10:41 PM Manger, James < > james.h.man...@team.telstra.com> wrote: > > >> base64url = [A-Z] / [a-z] / [0-9] / "-" / "_" > > > base64url = (%x40-5A) / (%x61-7A) / (%x30-39) / "-" / "_" > > > > “A” is %x41 (not %x40) > > > > -- > > James Manger > >
_______________________________________________ Acme mailing list Acme@ietf.org https://www.ietf.org/mailman/listinfo/acme
