randy/draft-wkc
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

jay's review

Browse source
This commit is contained in:
Randy Bush 2019-05-29 22:13:41 -07:00
parent b4a68e2568
commit c325b189f5
1 changed files with 4 additions and 11 deletions
Download patch file Download diff file Expand all files Collapse all files

15
draft-ietf-grow-wkc-behavior.xml
View file

@ -83,7 +83,7 @@
community handling across their networks, taking the inconsistent community handling across their networks, taking the inconsistent
behaviors from the various BGP implementations they operate into behaviors from the various BGP implementations they operate into
consideration. This document recommends specific actions to limit consideration. This document recommends specific actions to limit
future inconsistency, namely BGP implementors should not create future inconsistency, namely BGP implementors must not create
further inconsistencies from this point forward.</t> further inconsistencies from this point forward.</t>
</abstract> </abstract>
@ -236,11 +236,9 @@
<section anchor="note" title="Note for Those Writing RFCs for New Community-Like Attributes"> <section anchor="note" title="Note for Those Writing RFCs for New Community-Like Attributes">
<t>Care should be taken when establishing new <xref <t>> When establishing new [RFC1997]-like attributes (large
target="RFC1997"/>-like attributes (large communities, wide communities, wide communities, etc.), RFC authors should state
communities, etc.), RFCs MUST make clear how the new community explicitly how the > new attribute is to be handled.</t>
attribute is to to be handled, avoiding repeating
inconsistencies.</t>
</section> </section>
@ -271,11 +269,6 @@
a neighbor ASN, the operator should confirm with that neighbor how a neighbor ASN, the operator should confirm with that neighbor how
the community will be treated.</t> the community will be treated.</t>
<t>Network operators are encouraged to limit their use of the "set"
directive (within reason), to improve the readability of their
configurations and hopefully to achieve behavioral consistency
across platforms.</t>
</section> </section>
<section anchor="security" title="Security Considerations"> <section anchor="security" title="Security Considerations">