On 15.4.2014 10:46, Matthijs Mekking wrote:
2.1.1.1. The SOA Serial Field
First, this document talks about serial being greater than... It might
be good to reference RFC 1982 serial number arithmetic that defines
serial comparison.
Second, I don't like having a special value of 0 to indicate something.
0 is a valid serial number, which is now not allowed to be used in
restrictions. Perhaps it is better to define a new flag in the Flags
Field that says a serial restriction is being advertised.
I support this proposal.
Couple nits I have noticed:
- Term "DNS Publisher" is not used in the whole text except it's definition
and section 5. Acknowledgments :-)
- I'm bit nervous about "should be processed" in section:
2.2.2. CSYNC Record Types
This document defines how the following record types may be processed
if the CSYNC Type Bit Map field indicates they should be processed.
Did you mean SHOULD? Or maybe MUST?
- Document structure seems a bit too nested to me.
Compare draft-ietf-dnsop-child-syncronization-00:
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1. Terminology Used in This Document . . . . . . . . . . . . 3
2. Definition of the CSYNC RRType . . . . . . . . . . . . . . . . 4
2.1. The CSYNC Resource Record Format . . . . . . . . . . . . . 4
2.1.1. The CSYNC Resource Record Wire Format . . . . . . . . 4
2.1.2. The CSYNC Presentation Format . . . . . . . . . . . . 6
2.1.3. CSYNC RR Example . . . . . . . . . . . . . . . . . . . 6
2.2. CSYNC Data Processing . . . . . . . . . . . . . . . . . . 7
2.2.1. Processing Procedure . . . . . . . . . . . . . . . . . 7
2.2.2.1. The NS type
^^^^^ 4th level is not in TOC but is present in the text
... with draft-ietf-dnsop-delegation-trust-maintainance-11:
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 4
1.2. Requirements Notation . . . . . . . . . . . . . . . . . . 4
2. Background . . . . . . . . . . . . . . . . . . . . . . . . . 4
2.1. DNS Delegations . . . . . . . . . . . . . . . . . . . . . 4
2.2. Relationship Between Parent and Child DNS Operator . . . 5
2.2.1. Solution Space . . . . . . . . . . . . . . . . . . . 6
2.2.2. DNSSEC key change process . . . . . . . . . . . . . . 7
3. CDS / CDNSKEY (Child DS/ Child DNSKEY) Record Definitions . . 7
3.1. CDS Resource Record Format . . . . . . . . . . . . . . . 8
3.2. CDNSKEY Resource Record Format . . . . . . . . . . . . . 8
4. Automating DS Maintainance With CDS/CDNSKEY records . . . . . 8
4.1. CDS / CDNSKEY Processing Rules . . . . . . . . . . . . . 8
5. CDS / CDNSKEY Publication . . . . . . . . . . . . . . . . . . 9
6. Parent Side CDS / CDNSKEY Consumption . . . . . . . . . . . . 9
6.1. Detecting a Changed CDS / CDNSKEY . . . . . . . . . . . . 9
6.1.1. CDS / CDNSKEY Polling . . . . . . . . . . . . . . . . 10
6.1.2. Other Mechanisms . . . . . . . . . . . . . . . . . . 10
6.2. Using the New CDS / CDNSKEY Records . . . . . . . . . . . 11
6.2.1. Parent Calculates DS . . . . . . . . . . . . . . . . 11
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 12
IMHO moving section 2.2. CSYNC Data Processing and 2.3. Operational
Considerations to top-level sections (3., 4.) would make it more readable.
- Typo: "I.e,"
Have a nice day!
--
Petr^2 Spacek
_______________________________________________
DNSOP mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/dnsop
