search

ietf-wg-dnsop / draft-ietf-dnsop-glue-is-not-optional

1 stars 3 forks source link

Misc updates based on recent discussion with co-authors. #16

Closed shuque closed 3 years ago

shuque commented 3 years ago

Misc updates ..

Rework Sibling Glue section, and clarify that they MUST be included, and also subject to TC=1 if they don't fit.

Remove the cross parent zone cyclic dependency example, which doesn't work (I think we agreed to that, but I can be persuaded to add it back, if we want to point out a misconfiguration as a warning).

Move the paragraph about non-optionality of types of additional section data into the tail end of the Intro. It deserves to be more prominently mentioned than buried at the end of the example of missing glue.

Addressed Duane's comment that the "Why is Glue Required?" section did not actually say why, but instead just gave examples. Instead, I added a one phrase explaining why to the Intro section that defines glue records. I don't think it requires a separate section.

Removed Duane's comment about "I think the document should say that some servers might experience an increase in TCP if implementations require all glue or set TC=1. If not in this section then somewhere else._". I agree we should address this, so I've made an "issue" for it. And we can add the relevant text in the next update, once we figure out where it goes (an "Operational Considerations" section perhaps?).

shuque commented 3 years ago

@wessels - added your tweaks. Please review/approve!