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

[Gould, James]

I support publication, so +1.



Upon a re-review of -08, and I have the following nit feedback:



Section 1.2.1.2 “Supported DNS record types”



"This eliminates the need to update this document in the event that new DNS 
records that exist above a zone cut (Section 7 of [RFC9499]) see is 
specified.".  I believe that "see" needs to be removed, where it would read 
"...above a zone cut (Section 7 of [RFC9499]) is specified" or "...above a zone 
cut (see Section 7 of [RFC9499]) is specified".



Address the multiple which’s in the paragraph below, such as:



“A server that receives a  or  command, which includes an 
invalid DNS record type, MUST respond with a 2004 "Parameter value range" 
error.”





Section 1.2.1.2.1 "Glue records"



Update second paragraph to remove the multiple which's, such as:



“A server supporting host objects which receives a command that attempts to set 
TTL values for A and  records on a domain object MUST respond with a 2004 
"Parameter value range" error.”



Section 2.1.1 “EPP  command”



Add comma to be consist to the Default Mode bullet, such as:



“The Policy Mode (Section 
2.1.1.2),
 which …“



Section 2.1.1.1 “Default Mode”



Update the first paragraph by addressing the run on sentence and use double 
quotes for the attributes and values (“0” and “false”), such as:



“If a server receives an  command for a domain or host object which 
includes a  element with a “policy” attribute value of “0” or 
“false”, then the EPP response MUST contain  elements for all DNS 
record types that have non-default TTL values. These elements MUST NOT have the 
“min”, “default” and “max” attributes.”



Section 2.1.1.2 “Policy Mode”



Update the first paragraph by addressing the run on sentence and use double 
quotes for the attributes and values (“1” and “true”), such as:



“If a server receives an  command for a domain or host object which 
includes a  element with a “policy” attribute value of “1” or “true”, 
then the EPP response MUST contain  elements for all supported DNS 
record types, irrespective of whether those record types are in use by the 
object in question.”  These elements MUST have the “min”, “default” and “max” 
attributes.”



Section 5.1 “Operational impact of TTL values”



Revise the first paragraph for readability, such as:



“Domain registry operators must consider the balance between the registrant 
desire for domain changes to be visible in the DNS quickly, and the increased 
DNS query traffic that short TTLs can bring. Historically, registry operators 
have used a global TTL value for all delegations within their zones, which 
could then be tuned to an optimum value.”



Thanks,





--



JG







James Gould

Fellow Engineer

jgo...@verisign.com 




703-948-3271

12061 Bluemont Way

Reston, VA 20190



Verisign.com 









On 5/6/24, 3:27 AM, "regext on behalf of Mario Loffredo" 
mailto:regext-boun...@ietf.org> on behalf of 
mario.loffredo=40iit.cnr...@dmarc.ietf.org 
> wrote:





Caution: This email originated from outside the organization. Do not click 
links or open attachments unless you recognize the sender and know the content 
is safe.





+1





Mario





Il 29/04/2024 16:27, James Galvin ha scritto:

> The document editors have indicated that the following document is ready for 
> submission to the IESG to be considered for publication as a Proposed 
> Standard:

>

> Extensible Provisioning Protocol (EPP) mapping for DNS Time-To-Live (TTL) 
> values

> https://secure-web.cisco.com/1c1FkOdAKZ0pc8IHVuo4T0I5emiofMuSpTU--2s4xgNy06ipCF6iplze1N6Lt1ZW2FZ9y_CrkZaKrecsE7C6PKABKg9DciQ-01ZbJ1SRYlci293K7rKSFSxftmPGCFXDAGSYVWLfZmtQa68W2wS3k_aZ04bbVHBLMcYuAVRguqe9zQPz9TdbRuBGKTW-Slt8Ebd9HwZRRbRVn_h9YKPE9iWBrofBCMRVbcAmE9t0HJv1060Qe_bwZBUCeSkV2b44GNVF4epB4DJUQz7grrvEUNxBQiSEZnaK0l8aHRzSEXew/https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fdraft-ietf-regext-epp-ttl%2F08%2F
>  
> 

>

> Please indicate your support or no objection for the publication of this 
> document by replying to this message on list (a simple “+1” is sufficient).

>

> If any working group member has questions regarding the publication of this 
> document please respond on the list with your concerns by close of business 
> everywhere, Monday, 13 May 2024.

>

> If there are no objections the document will be submitted to the IESG.

>

> The Document Shepherd for this document is Andy Newton.

>

> Thanks,

>

> Antoin and Jim

> REGEXT 

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

[Mario Loffredo]

+1

Mario

Il 29/04/2024 16:27, James Galvin ha scritto:

The document editors have indicated that the following document is ready for 
submission to the IESG to be considered for publication as a Proposed Standard:

Extensible Provisioning Protocol (EPP) mapping for DNS Time-To-Live (TTL) values
https://datatracker.ietf.org/doc/draft-ietf-regext-epp-ttl/08/

Please indicate your support or no objection for the publication of this 
document by replying to this message on list (a simple “+1” is sufficient).

If any working group member has questions regarding the publication of this 
document please respond on the list with your concerns by close of business 
everywhere, Monday, 13 May 2024.

If there are no objections the document will be submitted to the IESG.

The Document Shepherd for this document is Andy Newton.

Thanks,

Antoin and Jim
REGEXT WG Co-Chairs

___
regext mailing list
regext@ietf.org
https://www.ietf.org/mailman/listinfo/regext


--
Dott. Mario Loffredo
Senior Technologist
Technological Unit “Digital Innovation”
Institute of Informatics and Telematics (IIT)
National Research Council (CNR)
via G. Moruzzi 1, I-56124 PISA, Italy
Phone: +39.0503153497
Web: http://www.iit.cnr.it/mario.loffredo

___
regext mailing list
regext@ietf.org
https://www.ietf.org/mailman/listinfo/regext

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

[Hollenbeck, Scott]

I've reviewed the draft again. I think it's ready modulo one minor nit:

Section 1.1: The text currently says "in this document are to be interpreted as 
described in [RFC2119]". Current convention is to say "in this document are to 
be interpreted as described in BCP 14 [RFC2119] [RFC8174] when, and only when, 
they appear in all capitals, as shown here".

Scott
___
regext mailing list
regext@ietf.org
https://www.ietf.org/mailman/listinfo/regext

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

[James Galvin]

The document editors have indicated that the following document is ready for 
submission to the IESG to be considered for publication as a Proposed Standard:

Extensible Provisioning Protocol (EPP) mapping for DNS Time-To-Live (TTL) values
https://datatracker.ietf.org/doc/draft-ietf-regext-epp-ttl/08/

Please indicate your support or no objection for the publication of this 
document by replying to this message on list (a simple “+1” is sufficient).

If any working group member has questions regarding the publication of this 
document please respond on the list with your concerns by close of business 
everywhere, Monday, 13 May 2024.

If there are no objections the document will be submitted to the IESG.

The Document Shepherd for this document is Andy Newton.

Thanks,

Antoin and Jim
REGEXT WG Co-Chairs

___
regext mailing list
regext@ietf.org
https://www.ietf.org/mailman/listinfo/regext