On Thu, Jun 13, 2019 at 9:56 AM Warren Kumari <[email protected]> wrote:
> Hi there all, > > The IESG felt that (esp because this is listed as Standards Track) > that we should replace: > "Vendors SHOULD clearly document the behavior of "set" directive in > their implementations." > with: > "Vendors MUST clearly document the behavior of "set" directive in > their implementations." > (s/SHOULD/MUST/). > > The document had sufficient support to be approved as is, but I think > that this is a useful improvement, and so agreed that we would make > that change (and the document is approved). I was initially > uncomfortable with the IETF telling vendors what they "MUST" do, but > then realized that we implicitly do this all throughout the IETF > series. Please let me know by 2019-06-19 if you *strongly* object to > this change. > > Thank you all, > W > > This change doesn't my support for the document, I still support it. I brought this up previously, so feel free to ignore it. In RFC1997 the three Well-known Communities are defined using MUST NOT, that seems at odds with the idea that the communities can be removed, SHOULD NOT seems compatible with the ability to remove them and effectively ignore them. Thanks. -- =============================================== David Farmer Email:[email protected] Networking & Telecommunication Services Office of Information Technology University of Minnesota 2218 University Ave SE Phone: 612-626-0815 Minneapolis, MN 55414-3029 Cell: 612-812-9952 ===============================================
_______________________________________________ GROW mailing list [email protected] https://www.ietf.org/mailman/listinfo/grow
