Hi Michael, Thanks for taking care of the comments from Erik and John. I see that you responded to Orie and Eric’s comments, and since they have not come back, I am going to assume they are ok with the changes you have made.
I have asked Joe/Benoit to help me with the document. In the meantime, reviewing the remaining comments, here are two additional edits from Murray that would help. First a nit. You rewrote the section, but left the title with “in-protocol’, which is not a word, as far as we can tell. Section 4.1: I think "inprotocol" should be "in-protocol", although I don't know if that's a word either. I would use neither; it's fine without. But more importantly the following comment. I noticed you removed all the SHOULDs from the sections, but retained most of the text related to them. I think the idea was that the BCP should state what the best practice is, and those who deviate are doing can still do it at their discretion. Did you feel differently, and that is why you retained the text? For a BCP, Section 6.5 feels mushy. It says the best practice is (thing), but then buffers it with SHOULDs. I think you should say what the best practice is and stop. If someone elects to deviate, then they're not doing what the best practice is Cheers. > On Aug 15, 2024, at 10:27 AM, Michael Richardson <mcr+i...@sandelman.ca> > wrote: > > > Mahesh, > https://author-tools.ietf.org/iddiff?url1=draft-ietf-opsawg-mud-iot-dns-considerations-16&url2=draft-ietf-opsawg-mud-iot-dns-considerations-17&difftype=--html > > contains changes to: > > * remove "geofenced" from the appendix > * synchronizes expectation in Introduction for cooperation text in the > Security Considerations. > > I would appreciate someone new to the document to proof the result. > s/requires/required/ at least. > > -- > Michael Richardson <mcr+i...@sandelman.ca> . o O ( IPv6 IøT consulting ) > Sandelman Software Works Inc, Ottawa and Worldwide > > > > Mahesh Jethanandani mjethanand...@gmail.com
_______________________________________________ OPSAWG mailing list -- opsawg@ietf.org To unsubscribe send an email to opsawg-le...@ietf.org
