-08 published
This commit is contained in:
parent
f3e4aaa418
commit
491feac381
1 changed files with 3 additions and 3 deletions
|
|
@ -11,7 +11,7 @@
|
|||
<?rfc tocindent="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>
|
||||
|
||||
|
|
@ -239,7 +239,7 @@
|
|||
|
||||
<t>When establishing new [RFC1997]-like attributes (large
|
||||
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>
|
||||
|
||||
|
|
@ -252,7 +252,7 @@
|
|||
<t>Unfortunately, it would be operationally disruptive for vendors
|
||||
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>
|
||||
|
||||
<t>Vendors MUST ensure that their implementations' "set" directive
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue