Re: [regext] Genart last call review of draft-ietf-regext-login-security-05

2019-11-05 Thread Gould, James
Brian, Thank you for your review and feedback. My responses are embedded below. I will include updates based on your feedback in draft-ietf-regext-login-security-06 at the conclusion of the last call. -- JG James Gould Distinguished Engineer jgo...@verisign.com 703-948-32

Re: [regext] Genart last call review of draft-ietf-regext-login-security-05

2019-11-05 Thread Brian E Carpenter
James, Comments in line: On 06-Nov-19 07:58, Gould, James wrote: > Brian,   > > Thank you for your review and feedback.  My responses are embedded below.  I > will include updates based on your feedback in > draft-ietf-regext-login-security-06 at the conclusion of the last call. > > --   > >

Re: [regext] AD review for draft-ietf-regext-login-security-04

2019-11-05 Thread Gould, James
Patrick, The trimming and collapsing of whitespace in draft-ietf-regext-login-security is a feature of the XML schema “token” type that exists today based on what’s defined in RFC 5730. There is no issue with complying with the NIST recommendation, where the use of the trimming and collapsing

Re: [regext] AD review for draft-ietf-regext-login-security-04

2019-11-05 Thread Patrick Mevzek
On Tue, Nov 5, 2019, at 16:37, Gould, James wrote: > The trimming and collapsing of whitespace in > draft-ietf-regext-login-security is a feature of the XML schema “token” > type that exists today based on what’s defined in RFC 5730. I know. I was just going into Barry's way, as it makes no s