Re: [regext] FW: New Version Notification for draft-gould-regext-login-security-00.txt

Jim, It should work for us too. And indeed, the minimum from the current login as already accepted as default, so why not hold on to this... Regards, Marc On 11/06/2018, 20:11, "regext on behalf of Hollenbeck, Scott" wrote: Works for me, Jim. Scott > -Original Mess

Re: [regext] Proposed Revision to our Charter

Good Morning, I agree with those saying this new wording seems a bit broad, what if "...related to the operation of Internet identifier registries..." was changed to "...related to the operation of Internet domain name registration systems"? Thanks Roger -Original Message

Re: [regext] Proposed Revision to our Charter

On Wed, Jun 13, 2018 at 10:35 AM, Roger D Carney wrote: > Good Morning, > > > > I agree with those saying this new wording seems a bit broad, what if > "...related to the operation of Internet identifier registries..." was > changed to "...related to the operation of Internet domain name registrat

Re: [regext] Proposed Revision to our Charter

Good Morning, I was definitely not thinking of two working groups. The focus of the WG is EPP and RDAP extensions. The additional suggested wording just adds on the ability to take on relevant (as determined by WG and AD) work (e.g. Third Party DNS Operator…). My suggestion was not to exclu

Re: [regext] Proposed Revision to our Charter

Broadening the charter beyond EPP and RDAP would enable the WG to take on the file format drafts that relate to the domain industry and should involve the same REGEXT participants, which include: 1. Data Escrow * Registry Data Escrow Specifications - draft-arias-noguchi-registry-data

[regext] I-D Action: draft-ietf-regext-tmch-func-spec-04.txt

A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Registration Protocols Extensions WG of the IETF. Title : ICANN TMCH functional specifications Author : Gustavo Lozano Filename: dr

Re: [regext] Proposed Revision to our Charter

Thanks for the clarification, Roger. The file formats seem like appropriate work to me. That said, the wording of the proposed charter seemed to indicate to me there was a broader motivation. If there is such, it be best if it were stated. -andy On Wed, Jun 13, 2018 at 11:52 AM, Roger D Carney

Re: [regext] FW: New Version Notification for draft-gould-regext-login-security-00.txt

On Mon, Jun 11, 2018, at 19:43, Gould, James wrote: > In thinking about decreasing the minimum from 8 to 1, I have a concern > that we're going to support a minimum that is below the existing RFC > 5730 of 6 characters. I believe it would be best for the Login Security > Extension to at least

Re: [regext] FW: New Version Notification for draft-gould-regext-login-security-00.txt

On Mon, Jun 11, 2018, at 21:57, Gould, James wrote: > Patrick, > > > > > JG - Thanks, I'll take a closer look at the PRECIS framework in RFC 7564 > > > and 8265. > > > > Please also look at the SASL framework (RFC4422 and RFC4616 for its > PLAIN version which is basically what w

Re: [regext] FW: New Version Notification for draft-gould-regext-login-security-00.txt

I have nothing to add. Just letting know I share the same opinion. -- Pieter Vandepitte Product Expert +32 16 28 49 70 www.dnsbelgium.be On 14/06/18 00:45, "regext on behalf of Patrick Mevzek" wrote: On Mon, Jun 11, 2018, at 19:43, Gould, James