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

upcase BGP, buy found by warren

Browse source
This commit is contained in:
Randy Bush 2019-02-15 13:26:52 -08:00
parent 4b115c67de
commit 2c9a7e3c28
1 changed files with 5 additions and 5 deletions
Download patch file Download diff file Expand all files Collapse all files

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

@ -11,7 +11,7 @@
<?rfc tocindent="yes"?> <?rfc tocindent="yes"?>
<?rfc tocompact="yes"?> <?rfc tocompact="yes"?>
<rfc category="std" docName="draft-ietf-grow-wkc-behavior-02" ipr="trust200902"> <rfc category="std" docName="draft-ietf-grow-wkc-behavior-032" ipr="trust200902">
<front> <front>
@ -39,7 +39,7 @@
<city>Bainbridge Island</city> <city>Bainbridge Island</city>
<region>WA</region> <region>WA</region>
<code>98110</code> <code>98110</code>
<country>US</country> <country>United States of America</country>
</postal> </postal>
<email>randy@psg.com</email> <email>randy@psg.com</email>
</address> </address>
@ -81,8 +81,8 @@
current implementations. This results in difficulties for current implementations. This results in difficulties for
operators. Network operators are encouraged to deploy consistent operators. Network operators are encouraged to deploy consistent
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. Also, bgp implementors are expected to not create consideration. Also, BGP implementors are expected to not create
any further inconsistencies from this point forward.</t> any further inconsistencies from this point forward.</t>
</abstract> </abstract>
@ -166,7 +166,7 @@
<section anchor="impls" title="Documentation of Vendor Implementations"> <section anchor="impls" title="Documentation of Vendor Implementations">
<t>In this section we document the syntax and observed behavior of <t>In this section we document the syntax and observed behavior of
the "set" directive in several popular bgp implementations.</t> the "set" directive in several popular BGP implementations.</t>
<t>In Juniper Networks' JunOS, "community set" removes all received <t>In Juniper Networks' JunOS, "community set" removes all received
communities, Well-Known or otherwise.</t> communities, Well-Known or otherwise.</t>