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

-08 published

Browse source
This commit is contained in:
Randy Bush 2019-06-13 08:52:09 -07:00
parent f3e4aaa418
commit 491feac381
1 changed files with 3 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

6
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-07" updates="1997" ipr="trust200902"> <rfc category="std" docName="draft-ietf-grow-wkc-behavior-08" updates="1997" ipr="trust200902">
<front> <front>
@ -239,7 +239,7 @@
<t>When establishing new [RFC1997]-like attributes (large <t>When establishing new [RFC1997]-like attributes (large
communities, wide communities, etc.), RFC authors should state communities, wide communities, etc.), RFC authors should state
explicitly how the > new attribute is to be handled.</t> explicitly how the new attribute is to be handled.</t>
</section> </section>
@ -252,7 +252,7 @@
<t>Unfortunately, it would be operationally disruptive for vendors <t>Unfortunately, it would be operationally disruptive for vendors
to change their current implementations.</t> to change their current implementations.</t>
<t>Vendors SHOULD clearly document the behavior of "set" directive <t>Vendors MUST clearly document the behavior of "set" directive
in their implementations.</t> in their implementations.</t>
<t>Vendors MUST ensure that their implementations' "set" directive <t>Vendors MUST ensure that their implementations' "set" directive