On Wed, 4 Feb 2004, Bob Hinden wrote: > > > I agree this could be stated better. I think it would be good to > > > change it to "Any router that is used between sites....", as it is > > > not the routing protocols doing the filtering, but the router based > > > on it's configuration. > > > >But then it's an operational guidance, right? Maybe not uppercase > >material? > > I don't have any problem making this change, but I don't understand > the difference between upper and lower case in these sections.
[and:] > > > Routers that maintain peering arrangements between Autonomous > > > Systems throughout the Internet SHOULD obey the recommendations for > > > site border routers unless configured otherwise. > > > >Ok, that's understandable. But again, why use an uppercase SHOULD > >keyword? This is a requirement for operators, not a protocol > >interoperability issue? > > As above, please explain the difference? As far as I can see, upper-case MUST/SHOULDs are something implementations should do. In addition to those, specifications often also include some language giving advice (or even stronger than that) to operators of the products based on those implementations what they should do. IMHO, the document should be very clear which statements are "operator advice/requirements" which "implementation requirements".. because the implementors (from whom we'll be collecting implementation reports etc.) *cannot* ensure that such advice/ops-reqs are followed -- if they could, it would be an implementation requirement. One way to achieve this would be to describe operational aspects in a separate section (e.g., "Operational Considerations and Requirements") which should make this clearer. Another way could be avoiding upper-case keywords and stating clearly that these are requirements or advice placed on the operators of the specification, not the implementers. Hope this clarified how I see the difference between an implementation requirement and operational advice. -- Pekka Savola "You each name yourselves king, yet the Netcore Oy kingdom bleeds." Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings -------------------------------------------------------------------- IETF IPv6 working group mailing list [EMAIL PROTECTED] Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6 --------------------------------------------------------------------
