Re: [regext] AD review of draft-ietf-regext-rfc7482bis-02

2021-01-26 Thread Hollenbeck, Scott
> -Original Message- > From: Barry Leiba > Sent: Monday, January 25, 2021 4:25 PM > To: draft-ietf-regext-rfc7482bis@ietf.org > Cc: regext > Subject: [EXTERNAL] AD review of draft-ietf-regext-rfc7482bis-02 > > Caution: This email originated from outside the organization. Do not click

Re: [regext] AD review of draft-ietf-regext-rfc7482bis-02

2021-01-26 Thread Barry Leiba
Of course, yes, 8174. My fingers had a light bout of dylsexia, so it seesm. b On Tue, Jan 26, 2021 at 7:42 AM Hollenbeck, Scott wrote: > > -Original Message- > > From: Barry Leiba > > Sent: Monday, January 25, 2021 4:25 PM > > To: draft-ietf-regext-rfc7482bis@ietf.org > > Cc: rege

Re: [regext] AD review of draft-ietf-regext-unhandled-namespaces-06

2021-01-26 Thread Martin Casanova
Barry Thanks for your review. Since James Gould is the main author of this draft I think it is better if he comments your suggestions. Nevertheless I try to answer your question about section 3. RFC 5730 chapter 2.6: Zero or more OPTIONAL elements that can be used to provide additional

Re: [regext] AD review of draft-ietf-regext-unhandled-namespaces-06

2021-01-26 Thread Gould, James
Barry, I respond to your feedback embedded below. I saw Martin's reply that I reference for section 3 below. I will publish draft-ietf-regext-unhandled-namespaces-07 once these items are agreed to. Let me know if you agree with the proposed updates below or if you have any additional propos

Re: [regext] AD review of draft-ietf-regext-unhandled-namespaces-06

2021-01-26 Thread Barry Leiba
All good, and thanks. Go ahead and post a revised I-D when you're ready. >> The answer to all of that might be “no”, but it would be good to… as >> we used to say in school, show your work. > > Yes, the quick answer is that I don't see the server using this as a > source for an attack, b

[regext] I-D Action: draft-ietf-regext-unhandled-namespaces-07.txt

2021-01-26 Thread internet-drafts
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 : Extensible Provisioning Protocol (EPP) Unhandled Namespaces Authors : James Gould

Re: [regext] AD review of draft-ietf-regext-unhandled-namespaces-06

2021-01-26 Thread Gould, James
Barry, Done, draft-ietf-regext-unhandled-namespaces-07 has been posted. Let us know if you have any additional feedback. Thanks, -- JG James Gould Fellow Engineer jgo...@verisign.com 703-948-3271 12061 Bluemont Way Reston, VA 20190 Verisign.com On 1/26/21,

[regext] Last Call: (Extensible Provisioning Protocol (EPP) Unhandled Namespaces) to Proposed Standard

2021-01-26 Thread The IESG
The IESG has received a request from the Registration Protocols Extensions WG (regext) to consider the following document: - 'Extensible Provisioning Protocol (EPP) Unhandled Namespaces' as Proposed Standard The IESG plans to make a decision in the next few weeks, and solicits final comments

Re: [regext] WG LAST CALL: draft-ietf-regext-epp-registry-maintenance-09

2021-01-26 Thread Quoc@registry.godaddy
Hi Antoin and all, I apologies for my late contribution on this subject, as a backend that has implemented (albeit an older draft) of the maintenance draft, I have the following to share on the list of actions posted by James Gould on 2021-01-15 (that would be my local date in Melbourne, Austra