[regext] Fwd: New Version Notification for draft-ietf-regext-epp-fees-00.txt

Dear colleagues, I have republished draft-brown-epp-fees-07 as draft-ietf-regext-epp-fees-00 (so farewell then, "the brown extension"). The intention is to publish an -01 draft with the "option C" changes discussed previously. Regards, -- Gavin Brown Chief Technology Offi

Re: [regext] TLD Phase Discovery

seen that a > launch phase would be used to group a set of domain names as a form of fee > classification. We can agree to disagree on this topic. I agree with Jim. The Launch Phase was not designed to deal with premium names: I would not have created the fee extension if it were.

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

s up with >> expectations for clients. > > That sound perfect to me. Thanks Scott for the text. > -- Gavin Brown Chief Technology Officer CentralNic Group plc (LSE:CNIC) Innovative, Reliable and Flexible Registry Services for ccTLD, gTLD and private domain name registries https://ww

Re: [regext] Provider status? (Problems with IP network requests)

is up, I'll add support for that too. Please (everyone) feel free to test, try to break, etc. Drop me a line with any feedback. G. On 16/05/2018 22:04, Gavin Brown wrote: > Hi Adam, > > I run rdap.org (in a personal capacity). Unfortunately it has not > received the attention it ne

Re: [regext] Fwd: New Version Notification for draft-brown-whoami-00.txt

Hi Patrick, apologies for the delay in responding. On 20/12/2017 22:25, Patrick Mevzek wrote: > > > On 20/12/2017 12:08, Gavin Brown wrote: >> Having thought about this topic for a little while, it occurred to me >> that there might be some benefit in a "s

[regext] draft-ietf-eppext-idnmap: extending the response

syntax for this: S: S: S: S: xn--espaol-zwa.example.com S: S: latn S: es S: S: S: S: What do you think? -- Gavin Brown Chief Technology Officer CentralNic Group plc (LSE:CNIC) Innovative, Reliable a

Re: [regext] EPP Contact Mapping for RDAP

to be an alternative to the vCard data format and to be unambiguous, extendable and simple to process. In contrast to the JSON-based jCard format, it is not a direct mapping from the vCard data model and expands semantics where appropriate. On 22/02/2019 13:41, Gavin Brown wrote

Re: [regext] EPP Contact Mapping for RDAP

he IETF. > > Overall, what is specified here looks good to me. Here are my comments for > improvements: > > 1. The country and region codes should be tied to ISO-3166 or a superset. > 2. There should be a place to spell out both region and country. Some > registries do not colle

Re: [regext] [gtld-tech] EPDP recommendations and EPP

ccTLD registries rely on the the XML schema in RFC 5733 to enforce their data collection policies, but if we change that schema, and they unknowingly update their implementation, then their data collection policy will be changed without them knowingly accepting it. G. [1]: http://regiops

Re: [regext] Security Lock anyone? (Was: Preliminary agenda for Prague, and call for agenda items)

are on the agenda, start preparing ;-) > > > > > Regards, Jim and Antoin > > - -- > Antoin Verschuren > > Tweevoren 6, 5672 SB Nuenen, NL > M: +31 6 37682392 > > > > > > ___ > regext mailing list > regext@ietf.org <mailto:regext@ietf.org>

[regext] EPP Contact Mapping for RDAP

consideration. G. -- Gavin Brown Chief Technology Officer CentralNic Group plc (LSE:CNIC) Innovative, Reliable and Flexible Registry Services for ccTLD, gTLD and private domain name registries https://www.centralnic.com/ +44.7548243029 CentralNic Group plc is a company registered in England and Wales

Re: [regext] Call for adoption: draft-loffredo-regext-rdap-partial-response

gt; > > ___ > regext mailing list > regext@ietf.org > https://www.ietf.org/mailman/listinfo/regext > -- Gavin Brown Chief Technology Officer CentralNic Group plc (LSE:CNIC) Innovative, Reliable and Flexible Registry Services for c

Re: [regext] Call for adoption: draft-loffredo-regext-rdap-reverse-search

gt; > > ___ > regext mailing list > regext@ietf.org > https://www.ietf.org/mailman/listinfo/regext > -- Gavin Brown Chief Technology Officer CentralNic Group plc (LSE:CNIC) Innovative, Reliable and Flexible Registry Services for c

Re: [regext] New Version Notification for draft-gould-regext-secure-authinfo-transfer-00.txt

from the time of > submission >until the htmlized version and diff are available at tools.ietf.org. > >The IETF Secretariat > > > > ___ > regext mailing list > regext@ietf.org > https://www.ietf

Re: [regext] CALL FOR ADOPTION: draft-arias-noguchi-dnrd-objects-mapping

list > regext@ietf.org > https://www.ietf.org/mailman/listinfo/regext -- Gavin Brown Chief Innovation Officer CentralNic Group plc (LSE:CNIC) https://www.centralnicgroup.com/ +44.7548243029 CentralNic Group plc is a company registered in England and Wales with company number 8576358. R

Re: [regext] CALL FOR ADOPTION: draft-arias-noguchi-registry-data-escrow

. > > If there are no objections, and we receive enough consensus for > adoption, the chairs will consider this document adopted. > > Thanks, > > Your REGEXT co-chairs Antoin and Jim > > ___ > regext mailing list > regext@

Re: [regext] Proposal about jCard replacement

Hi Mario, >> I would be happy to publish a new version of >> draft-brown-epp-contacts-in-rdap which uses JSContact rather than its own >> representation of contact data. That would glue JSContact and RDAP together. > > IMHO it would be better to write a new document with the contribution of

Re: [regext] 2nd factor for Login Security Extension for EPP

associate a cert with a specific client identity, so a client that connects using a certificate can only log in to a registrar account to which the certificate has been associated. That's how CentralNic's implementation works. G. -- Gavin Brown Chief Innovation Officer CentralNic Group plc (LSE:CN

Re: [regext] FW: New Version Notification for draft-gould-regext-secure-authinfo-transfer-00.txt

It's worth noting that there are "operational practices" RFCs (6781 being the obvious example) that do not describe a protocol, and are published as Informational documents. This document seems more like those than a protocol specification. G. > On 2 Jul 2019, at 06:56, Patrick Mevzek wrote:

Re: [regext] Proposal about jCard replacement

Hi Mario, I like JSContact and the current draft certainly looks good enough to be usable in RDAP. I imagine more work will be needed before JSContact will have feature parity with vCard/jCard. I would be happy to publish a new version of draft-brown-epp-contacts-in-rdap which uses JSContact

Re: [regext] RDAP RFC Update - PS or DS?

that require a Proposed Standard re-do? > > Scott > > ___ > regext mailing list > regext@ietf.org > https://www.ietf.org/mailman/listinfo/regext -- Gavin Brown Chief Innovation Officer CentralNic Group plc (LSE:CNIC) https://ww

Re: [regext] on jcard and jscontact migration

oubt there ever will be). G. -- Gavin Brown Chief Innovation Officer CentralNic Group plc (LSE:CNIC) https://www.centralnicgroup.com/ +44.7548243029 CentralNic Group plc is a company registered in England and Wales with company number 8576358. Registered Offices: Saddlers House, Gutter Lane, L

Re: [regext] rfc7484bis

> On 11 Aug 2020, at 19:33, Marc Blanchet wrote: > > On 4 Aug 2020, at 15:47, Patrick Mevzek wrote: > >> On Tue, Aug 4, 2020, at 14:32, Gavin Brown wrote: >>> 1. client implementers should be advised to prefer https:// base URLs >>> over http:// base

Re: [regext] rfc7484bis

ould be advised that if multiple base URLs with the same scheme are present in an entry, then all the RDAP endpoints referenced by these base URLs must return identical responses (for the same RDAP query). Thanks, G. -- Gavin Brown Head of Registry Services and Chief Innovation Officer Centr

Re: [regext] rfc7484bis

in the array MUST return > identical responses for the same RDAP query. » > > would that work? Looks good to me. G. -- Gavin Brown Head of Registry Services and Chief Innovation Officer CentralNic Group plc (LSE:CNIC) https://www.centralnic.com Tel: +44.7548243029 CentralNic

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

we have 3 authors, we need more reviewers to state support! > > This WG last call will end at close of business, Monday, 12 April 2021. > > > The document shepherd for this document is James Galvin. > > Regards, > > Antoin and Jim > > > > &

Re: [regext] EXTENDED: Re: CALL FOR ADOPTION: draft-loffredo-regext-rdap-jcard-deprecation-03

by >> REGEXT, and comment to the list, clearly stating your view. >> >> Please indicate if you are willing to contribute text, review text, or be a >> document shepherd. >> >> Please also indicate any preference you have for a proposed milestone date. >> >&g

[regext] Confusion around non-uniqueness of nameserver objects

using the bootstrap registry). My question to this group is how useful this would be? Does it solve a real problem? Thanks, -- Gavin Brown Head of Registry Services CentralNic Group plc (LSE:CNIC) https://centralnicregistry.com Cal: http://cnic.link/gbcalendar CentralNic Group plc is a company r

Re: [regext] Confusion around non-uniqueness of nameserver objects

uld be? Does it solve a real >> problem? > > [SAH] Sounds useful to me. What did the otherwise clueful person think? He agreed that the above solution would be effective. G. -- Gavin Brown Head of Registry Services CentralNic Group plc (LSE:CNIC) https://centralnicregistry.com Cal

Re: [regext] New Version Notification for draft-ietf-regext-rdap-jscontact-04.txt

lgende geschreven: >>> >>> Hi folks, >>> this new version addresses the feedback provided by Jasdip except for the >>> following two points left for WG discussion: >>> 1) In the sentence "To aid interoperability, RDAP providers are RECOMME

Re: [regext] Fwd: New Version Notification for draft-loffredo-regext-epp-over-http-00.txt

one day be replaced by RDAP, which is HTTP based. I look forward to one day putting my entire infrastructure behind $YOUR_CLOUD_BASED_REVERSE_PROXY_OF_CHOICE - which necessitates retiring (or at least deprecating) ports 43 and 700. G. -- Gavin Brown Head of Registry Services CentralNic

Re: [regext] [Ext] New Version Notification for draft-ietf-regext-epp-ttl-02.txt

023, 14:00, internet-dra...@ietf.org <mailto:internet-dra...@ietf.org wrote: A new version of Internet-Draft draft-ietf-regext-epp-ttl-02.txt has been successfully submitted by Gavin Brown and posted to the IETF repository. Name: draft-ietf-regext-epp-ttl Revision: 02 Title:Extensible

Re: [regext] JSON Schema for RDAP RFC-9083

Hi there, Further to Scott’s email, some time ago Mario and Maurizio from .IT created some schemas which I pinched and put in this Git repository: https://github.com/gbxyz/rdap-json-schemas These are based on RFC 7483, but with a bit of work could be updated and form the basis of a draft. G.

Re: [regext] [Ext] New Version Notification for draft-ietf-regext-epp-ttl-02.txt

on > Date: Thursday, 14 September 2023 at 20:22 > To: Marc Groeneweg > Cc: Gavin Brown , regext@ietf.org > Subject: Re: [regext] [Ext] New Version Notification for > draft-ietf-regext-epp-ttl-02.txt > On Tue, Sep 12, 2023 at 6:34 AM Marc Groeneweg > wrote: > Hi

Re: [regext] Call for agenda items IETF 118

Those interested in this topic may want to watch the recording of a panel session I ran at the 11th Registration Operations Workshop back in 2022: https://icann.zoom.us/rec/share/LbpHF4gIkTXDZUU8k1FAEX4Wj3heVjooXoL1rWBsRDMLqd2fyVrlZ31VlSm7Atyq.mPnxau32-dlHUoH8 Passcode: !@.!&7+ver - skip to

[regext] Fwd: New Version Notification for draft-regext-brown-epp-ttl-02.txt

Submitted version -02 with a first stab at both domain and host mapping. G. > Begin forwarded message: > > From: internet-dra...@ietf.org > Subject: New Version Notification for draft-regext-brown-epp-ttl-02.txt > Date: 27 September 2022 at 13:48:36 BST > To: "Gavi

Re: [regext] New Version Notification for draft-regext-brown-epp-ttl-01.txt

TTL at the host object level would apply to registries > that implement sibling glue as well as CentralNic and TANGO that implement > in-bailiwick only glue. > > -- > > JG > > > > James Gould > Fellow Engineer > jgo...@verisign.com > > > 703-948-327

Re: [regext] New Version Notification for draft-regext-brown-epp-ttl-01.txt

dation is to just reference the EPP Change Poll Extension for > implementing the out-of-band change. Thanks, I'll consider this for the next version. G. -- Gavin Brown Head of Registry Services CentralNic Group plc (LSE:CNIC) https://centralnicregistry.com Cal: https://cnic.link/gbcalen

[regext] Fwd: New Version Notification for draft-regext-brown-epp-ttl-01.txt

@ietf.org > Subject: New Version Notification for draft-regext-brown-epp-ttl-01.txt > Date: 14 September 2022 at 12:26:38 BST > To: "Gavin Brown" > > > A new version of I-D, draft-regext-brown-epp-ttl-01.txt > has been successfully submitted by Gavin Brown and po

Re: [regext] Fwd: New Version Notification for draft-regext-brown-epp-ttl-01.txt

Hi Thomas, Thanks for the suggestions. I will add them to the next version. G. > On 15 Sep 2022, at 01:11, Thomas Corte (TANGO support) > wrote: > > On 9/14/22 13:35, Gavin Brown wrote: > >> Greetings all, >> >> Many years ago CentralNic had a propr

[regext] Fwd: New Version Notification for draft-regext-brown-epp-ttl-03.txt

ocument up in the near future. Gavin. > Begin forwarded message: > > From: internet-dra...@ietf.org > Subject: New Version Notification for draft-regext-brown-epp-ttl-03.txt > Date: 16 November 2022 at 16:12:04 GMT > To: "Gavin Brown" > > > A new version

Re: [regext] draft-ietf-regext-epp-eai Path Forward

I support Jim’s proposal – the “cardinality of two” option is unnecessarily complex and would require more work to implement on client and server side for little benefit. G. On Thursday, March 2, 2023 at 7:50 AM, Gould, James jgo...@verisign.com wrote: I’ve

Re: [regext] FW: New Version Notification for draft-regext-brown-epp-ttl-04.txt

of host attribute servers who would implement this extension if it was modified to accommodate them! G. From: Hugo Salgado Date: Thursday, 2 March 2023 at 14:46 To: Gavin Brown Cc: regext@ietf.org Subject: Re: [regext] FW: New Version Notification for draft-regext-brown-epp-ttl-04.txt Hi Gavin

Re: [regext] FW: New Version Notification for draft-regext-brown-epp-ttl-04.txt

This is because using syntax like would make the TTL ambiguous for the RR types not listed: it would be better to explicitly list the TTL values for each RR type. G. From: Hugo Salgado Date: Thursday, 9 March 2023 at 16:54 To: Gavin Brown Cc: regext@ietf.org Subject: Re: [regext] FW: New Version

Re: [regext] Call for agenda items IETF 116

Hi Antoin, I'd like to request a slot to discuss draft-regext-brown-epp-ttl. I will be remote. Thanks, G. -- Gavin Brown CentralNic Group plc (LSE:CNIC) https://centralnicregistry.com CentralNic Group plc is a company registered in England and Wales with company number 8576358. Registered

[regext] FW: New Version Notification for draft-regext-brown-epp-ttl-04.txt

. (forgive HTML email, Outlook no longer provides a way to send in plain text) From: internet-dra...@ietf.org Date: Thursday, 23 February 2023 at 10:41 To: Gavin Brown Subject: New Version Notification for draft-regext-brown-epp-ttl-04.txt A new version of I-D, draft-regext-brown-epp-ttl-04.txt

[regext] Adoption request for draft-regext-brown-epp-ttl

Greetings, As the author of the above document, I'd like to ask the chairs to consider it for adoption by the REGEXT working group. Thanks in advance, Gavin. ___ regext mailing list regext@ietf.org https://www.ietf.org/mailman/listinfo/regext

[regext] Fw: New Version Notification for draft-regext-brown-epp-related-objects-00.txt

etf.org Sent: 27 March 2023 11:59 To: Gavin Brown Subject: New Version Notification for draft-regext-brown-epp-related-objects-00.txt A new version of I-D, draft-regext-brown-epp-related-objects-00.txt has been successfully submitted by Gavin Brown and posted to the IETF repository. Name:

Re: [regext] Redacting JSContact uid in RDAP

Please, express your preference(s). > > Best, > > Mario -- Gavin Brown CentralNic Group plc (LSE:CNIC) https://centralnicregistry.com CentralNic Group plc is a company registered in England and Wales with company number 8576358. Registered Offices: Sadd

Re: [regext] New Version Notification for draft-regext-brown-epp-related-objects-00.txt

... Where an object cannot be included, then the would be empty but would have "code" and "msg" attributes that would mirror the values that the client would see if they did an command on the same object. G. -- Gavin Brown CentralNic Group plc (LSE:CNIC) https://central

Re: [regext] New Version Notification for draft-regext-brown-epp-related-objects-00.txt

les for the same data accessed via a different path. Agreed - will fix. G. -- Gavin Brown CentralNic Group plc (LSE:CNIC) https://centralnicregistry.com CentralNic Group plc is a company registered in England and Wales with company number 8576358. Registered Offices: Saddlers House, Gutter

Re: [regext] CALL FOR ADOPTION: draft-regext-brown-epp-ttl

Hi Patrick, On Tue, 25 Apr 2023 18:41:26 -0500 Patrick Mevzek wrote: > Two (+1) quick points on the content for draft version 4. > > Section 8.1 uses twice the same XML namespace for both cases. I suspect > `:schema:` is missing in the second one. Thanks, this is fixed. > As for TTL values:

Re: [regext] New Version Notification for draft-regext-brown-epp-ttl-04.txt

Hi Rick, On Thu, 30 Mar 2023, at 22:55, Rick Wilhelm wrote: > Two points in this email: > • one related to the on a comment that I made at the mic during the 30 > March meeting at IETF 116; and > • one higher level issue that came up during Yet Another Read of the > draft > > Point One: > >

Re: [regext] Thoughts on the fundamental premise of JSContact

Hi Andy, I made the original proposal to replace jCard, with a straight mapping of RFC5733 contact objects into JSON, back in 2019: https://mailarchive.ietf.org/arch/msg/regext/bZA9yGAdy2fPaDxiMuMr5CE-z74/ A certain Mr Newton (perhaps you know him) raised the point that this would exclude

[regext] Fwd: New Version Notification for draft-ietf-regext-epp-ttl-01.txt

FYI Begin forwarded message: From: internet-dra...@ietf.org Subject: New Version Notification for draft-ietf-regext-epp-ttl-01.txt Date: 1 August 2023 at 12:58:25 BST To: "Gavin Brown" [You don't often get email from internet-dra...@ietf.org. Learn why this is important at http

Re: [regext] draft-ietf-regext-epp-ttl Feedback

plemented in a period of time — at least > equal to the current TTL — before the planned change." > • Section 8.2 "EPP extension registry" > • Nit - Change Document Status from "Experimental" to "Standards > Track" > Thanks, > -- >

Re: [regext] draft-ietf-regext-epp-ttl Feedback

Thanks Andy! WG chairs, please note. G. > On 1 Aug 2023, at 13:41, Andrew Newton wrote: > > [You don't often get email from a...@hxr.us. Learn why this is important at > https://aka.ms/LearnAboutSenderIdentification ] > > On Tue, Aug 1, 2023 at 7:49 AM Gavin Brown wro

[regext] Fwd: New Version Notification for draft-ietf-regext-epp-ttl-00.txt

in advance, G. Begin forwarded message: From: internet-dra...@ietf.org Subject: New Version Notification for draft-ietf-regext-epp-ttl-00.txt Date: 16 May 2023 at 13:32:40 BST To: "Gavin Brown" [You don't often get email from internet-dra...@ietf.org. Learn why this is importan

Re: [regext] [Ext] I-D Action: draft-ietf-regext-epp-ttl-05.txt

s now available. It is a >> work >> item of the Registration Protocols Extensions (REGEXT) WG of the IETF. >> >> Title: Extensible Provisioning Protocol (EPP) mapping for DNS >> Time-To-Live (TTL) values >> Author: Gavin Brown >> Name:draft-ietf-

Re: [regext] [Ext] I-D Action: draft-ietf-regext-epp-ttl-05.txt

is in use by the object without the "min", > "default", and "max" policy attributes. > > Section 2.1.1 may be a duplicate of the description in section 1.3, but I > believe that's ok. > > Thanks, > > -- > > JG > > > > J

Re: [regext] [Ext] I-D Action: draft-ietf-regext-epp-ttl-04.txt

raft-ietf-regext-epp-ttl-04.txt is now available. It is a work > item of the Registration Protocols Extensions (REGEXT) WG of the IETF. > > Title: Extensible Provisioning Protocol (EPP) mapping for DNS > Time-To-Live (TTL) values > Author: Gavin Brown > Name:d

Re: [regext] [Ext] I-D Action: draft-ietf-regext-epp-ttl-03.txt

ustom" command enumerated value with the "customName" > attribute in RFC 8748 [datatracker.ietf.org]. > i. Providing a predefined enumeration list supports XML parser > validation by default and supports extensibility for new values for the > future. This makes s

[regext] TTL extension for RDAP

information in RDAP responses. Given bandwidth constraints, I would not seek WG adoption until the EPP document is published as an RFC, but wanted to publish an early draft for review. Feedback welcome! G. -- Gavin Brown Principal Engineer, Global Domains & Strategy Internet Corpora

Re: [regext] [Ext] TTL extension for RDAP

gn.com > <https://urldefense.com/v3/__http://verisigninc.com/__;!!PtGJab4!-twuq17rqSKX-pCKHkTFhmzOXZaiQ1nbrzbWhB81AVnwvlHzeutZfLJ89yfRnjIyun6gaZT9bPAZBBwW9FcwU_pM$ > [verisigninc[.]com]> > > > > > On 1/2/24, 9:03 AM, "regext on behalf of Gavin Brown" >

Re: [regext] [Ext] TTL extension for RDAP

pdated date, transfer date, sponsorship) >> that may have value to the public. My recommendation is to focus management >> of TTL in EPP with its impact on DNS and leave RDAP alone. Let's not go >> down the slippery slope of bloating RDAP by replicating DNS information wh

Re: [regext] [Ext] TTL extension for RDAP

Hi Andy, > On 4 Jan 2024, at 14:22, Andrew Newton wrote: > > On Wed, Jan 3, 2024 at 10:20 AM Gavin Brown wrote: >> >> Do you think the ttl_values object needs an events array then? >> >> To support this I would change the ttl_values object as follows: >

Re: [regext] [Ext] TTL extension for RDAP

http://secure-web.cisco.com/1G5fgdFkXdulNRG5Wp0MVgw1N8i2VEWJQUqwCuJTkvB2kDu268F7-47Eg0aesDAxPh36PrN-BVhPV2ZborUE-FR1IZFEvNJXO8R7Ccnpd9dkn-4xLoRNmcdjvygo-HiW5AILZ210BGYByHPgWFMY_t8bn4rN0Kiie59Tp9nF9VQzp64FkNBUd469D9wtTrM6babIyDlob_xhplmt2cCazwGsgYlGbD8LZCuiW8hPPfGISqINVDEjI4cfTuKnRxbHfDLfhlUrIY1E_uGUQNLS5XNkRNQVAuFoIdFHGMWCy5fY/http*3A*2F*2Fverisigninc.com*2F__;JSUlJQ!!PtGJab4!5GuTiuq9XrUu8aQd2RokjKHNwmwEZ5tlC8tsJDWbNrI3g7ADTmvE53

Re: [regext] [Ext] I-D Action: draft-ietf-regext-epp-ttl-03.txt

DNS > Time-To-Live (TTL) values > Author: Gavin Brown > Name:draft-ietf-regext-epp-ttl-03.txt > Pages: 19 > Dates: 2023-11-22 > > Abstract: > > This document describes an extension to the Extensible Provisioning > Protocol (EPP) that allows EPP client

Re: [regext] [Ext] Call for agenda items IETF119

/www.ietf.org/mailman/listinfo/regext__;!!PtGJab4!-R8-coMHyTpJs2cx1rrT50_63TuWXTB3nHIfKQZT-qxGeD_MQDL0sxn6nsC7BfXDu3YYIR0MVYZ1LHCS3o62qEyQf9x5I7YfVYD2XIoB$ > [ietf[.]org] -- Gavin Brown Principal Engineer, Global Domains & Strategy Internet Corporation for Assigned Names and Numbers (ICANN)

Re: [regext] [Ext] I-D Action: draft-ietf-regext-epp-ttl-05.txt

> Time-To-Live (TTL) values > Author: Gavin Brown > Name:draft-ietf-regext-epp-ttl-05.txt > Pages: 26 > Dates: 2024-01-26 > > Abstract: > > This document describes an extension to the Extensible Provisioning > Protocol (EPP) that allows EP

Re: [regext] [Ext] CALL FOR ADOPTION: draft-hollenbeck-regext-epp-delete-bcp

yq8aquwGJ-1njwhyjfJrLaaMBKxNZTe5Ouov-EBPHtnX0K-WCeZAtRuujBMRf2yWzsjkgM6P9clGTC$ > [ietf[.]org] -- Gavin Brown Principal Engineer, Global Domains & Strategy Internet Corporation for Assigned Names and Numbers (ICANN) https://www.icann.org ___ regext mailing list regext@ietf.org https://www.ietf.org/mailman/listinfo/regext

Re: [regext] [Ext] I-D Action: draft-ietf-regext-epp-ttl-04.txt

ion with all support TTL > records by default in every domain and host response. > > Thanks, > > -- > > JG > > > > James Gould > Fellow Engineer > jgo...@verisign.com > > > 703-948-3271 > 12061 Bluemont Way > Reston, VA 20190 > > Veri

Re: [regext] [Ext] Re: RDAP-X draft adoption

On 16 Nov 2023, at 15:34, Andrew Newton wrote: > Consider a network operator > writing a shell script using curl and jq to find the most specific > covering networking of an IP. Using the bootstrap files requires > downloading the appropriate file (there are different ones for v4 and > v6),

Re: [regext] [Ext] CALL FOR ADOPTION: draft-jasdips-regext-rdap-geofeed

GJab4!-QAxQKFphWOHxBEdNCnOSOvcd2N0KVhrsg_243VjMVQwRL21YfOEnD3JMkrnwXqaJfLNswubklpWrM-DfDdmaXWKpoHD6yZJ4o5zn8YO$ > [ietf[.]org] -- Gavin Brown Principal Engineer, Global Domains & Strategy Internet Corporation for Assigned Names and Numbers (ICANN) https://www.icann.org smime.p7s Descrip

Re: [regext] [Ext] ACTION REQUESTED: split draft-ietf-regext-rdap-jscontact

__ > regext mailing list > regext@ietf.org > https://urldefense.com/v3/__https://www.ietf.org/mailman/listinfo/regext__;!!PtGJab4!5VnbfMvjkdb91qk4OBUxF1QEN2yM0_zQG6pRrvJqprNUBr3vF5kejsi7x7XuFWGVwkG1Fu7WDPKaMVJSsR6iqvI$ > [ietf[.]org] -- Gavin Brown Principal Engineer, Global Domains &am

Re: [regext] [Ext] I-D Action: draft-ietf-regext-epp-ttl-06.txt

p-ttl-06.txt is now available. It is a work > item of the Registration Protocols Extensions (REGEXT) WG of the IETF. > > Title: Extensible Provisioning Protocol (EPP) mapping for DNS > Time-To-Live (TTL) values > Author: Gavin Brown > Name:draft-ietf-regext-epp-ttl-06.txt >

Re: [regext] [Ext] I-D Action: draft-ietf-regext-epp-ttl-05.txt

fR0HrgHAu3Tue2WFr-2APuvO-K2D7ZFgCCrlAR_fhQARHLdz5$ > [verisigninc[.]com]> > > > > > On 2/7/24, 12:43 PM, "Gavin Brown" <mailto:gavin.br...@icann.org>> wrote: > > > Caution: This email originated from outside the organization. Do not click >

Re: [regext] [Ext] I-D Action: draft-ietf-regext-epp-ttl-06.txt

hanks, > -- JGJames Gould > Fellow Engineer > jgo...@verisign.com > > 703-948-3271 > 12061 Bluemont Way > Reston, VA 20190 > Verisign.com <http://verisigninc.com/> On 3/1/24, 7:52 AM, "regext on > behalf of Gavin Brown" <mailto:reg

Re: [regext] [Ext] [EXTERNAL] I-D Action: draft-ietf-regext-epp-ttl-07.txt

think that the notion of “striking a balance” is a value > judgement, but to “consider the balance” is judgement-free. Hmm!! Agreed, I've updated the wording. Diff here: https://github.com/gbxyz/epp-ttl-extension/commit/d25d21fc54c877bb399205bddbc45ae616ccc385 G. -- Gavin Brown Principal Engineer, Global Domains & Strategy Internet Corporation for Assigned Names and Numbers (ICANN) https://www.icann.org ___ regext mailing list regext@ietf.org https://www.ietf.org/mailman/listinfo/regext

Re: [regext] [Ext] I-D Action: draft-ietf-regext-epp-ttl-07.txt

tl-07.txt is now available. It is a work > item of the Registration Protocols Extensions (REGEXT) WG of the IETF. > > Title: Extensible Provisioning Protocol (EPP) mapping for DNS > Time-To-Live (TTL) values > Author: Gavin Brown > Name:draft-ietf-regext-epp-ttl-07.tx

Re: [regext] [Ext] I-D Action: draft-ietf-regext-epp-ttl-08.txt

ration Protocols Extensions (REGEXT) WG of the IETF. > > Title: Extensible Provisioning Protocol (EPP) mapping for DNS > Time-To-Live (TTL) values > Author: Gavin Brown > Name:draft-ietf-regext-epp-ttl-08.txt > Pages: 28 > Dates: 2024-04-16 > > Abstrac

Re: [regext] [Ext] I-D Action: draft-ietf-regext-epp-ttl-08.txt

Hi Jim and Antoin, Please can you also submit this document to the DNS Directorate for review? Thanks, > On 16 Apr 2024, at 07:18, Gavin Brown wrote: > > Hi all, > > This version of the draft incorporates Rick's feedback as discussed last week. > > Chairs: I would li

Re: [regext] [Ext] Re-chartering REGEXT?

out all the details > but we do feel that this is not an issue. I think this is a matter that you should address urgently since EPP's extensibility is fundamental to its success as a protocol, and implementers (of both clients and servers) will be extremely reluctant to jettison two decades'

Re: [regext] [Ext] WGLC: draft-ietf-regext-epp-ttl-08

> regext mailing list > regext@ietf.org > https://urldefense.com/v3/__https://www.ietf.org/mailman/listinfo/regext__;!!PtGJab4!4P3dFZLoTlnATMxQfwQUEqHl3nEMTgvzLTQrWoPldTKjY-XFAeDDpN2wFELc4nJFJ8XDVaIClNKmEatwKXUyTJzSLhdxS2QItqr7lBp_$ > [ietf[.]org] -- Gavin Brown Principal E

Re: [regext] [Ext] Re-chartering REGEXT?

eve the same effect, and altering the XML schema just to avoid duplication throws the baby out of the bathwater. I would strongly recommend that the schemas from RFCs 5730-5733 remain unchanged. G. -- Gavin Brown Principal Engineer, Global Domains & Strat

[regext] Re: [Ext] WGLC: draft-ietf-regext-epp-ttl-08

www.ietf.org%2Fmailman%2Flistinfo%2Fregext > > <https://secure-web.cisco.com/1BCU29KkyrRwXsVnp2SCDnWq8JA-lZcDf-1PUkJB0ixWpHA1iSWHnLCFKwW51BeUqekjUmq-mP9IpgZgNMZsHMOCV__s352UM6oCzAmrVhzMkVxk5E_p-DN5euABUCFpJjnu-orG1au2TUONfaFotfFc-A_l_FZieXpz9PqUyNT2-oBRdb0vkwy9FjRHl-oi9SCuuuSdbhuFwEQRnrxwWBNUu1Hw5S4ksV4KFOp3QcJmX9FwXYkaEsXC30Oq0QqAZnXlFV5EjTV0aqJsUdkB5KyipEp8sQrvQxpe1HnUk2Fo/https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Fregext> > ___ > regext mailing list > regext@ietf.org > https://www.ietf.org/mailman/listinfo/regext -- Gavin Brown Principal Engineer, Global Domains & Strategy Internet Corporation for Assigned Names and Numbers (ICANN) https://www.icann.org ___ regext mailing list -- regext@ietf.org To unsubscribe send an email to regext-le...@ietf.org

[regext] Re: [Ext] Re: I-D Action: draft-ietf-regext-epp-delete-bcp-02.txt

ribes best practices to >> delete domain and host objects that reduce the risk of DNS resolution >> failure and maintain client-server data consistency. > > [SAH] With this update the editors believe this draft is ready for working > group last call. Please say otherwise

[regext] Re: [Ext] I-D Action: draft-ietf-regext-epp-ttl-09.txt

Registration Protocols Extensions (REGEXT) WG of the IETF. > > Title: Extensible Provisioning Protocol (EPP) mapping for DNS > Time-To-Live (TTL) values > Author: Gavin Brown > Name:draft-ietf-regext-epp-ttl-09.txt > Pages: 28 > Dates: 2024-05-13 &g

[regext] Re: [Ext] Re: I-D Action: draft-ietf-regext-epp-delete-bcp-02.txt

sk and have been > observed in operation" to 6.1 and "The practices in this section are > described as "proposed best practices" because they address the operational > risk and haven't been observed in operation" to 6.2. Would that help? Yes, I t

[regext] Re: [Ext] Dnsdir early review of draft-ietf-regext-epp-ttl-09

er reading the > section again more carefully it says that supported > record types would be returned by the server - perhaps one could be more > explicit in section 3.1 to make reference to the ttl:info portion of the info > response? > > Thanks for your hard work on

[regext] Re: [Ext] I-D Action: draft-ietf-regext-epp-ttl-10.txt

> > Title: Extensible Provisioning Protocol (EPP) mapping for DNS > Time-To-Live (TTL) values > Author: Gavin Brown > Name:draft-ietf-regext-epp-ttl-10.txt > Pages: 29 > Dates: 2024-05-16 > > Abstract: > > This document describes an extension to