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

alyssa's changes, 2119 too

Browse source
This commit is contained in:
Randy Bush 2019-06-10 17:29:14 -07:00
parent 49187dfda9
commit ffd70b88de
1 changed files with 12 additions and 10 deletions
Download patch file Download diff file Expand all files Collapse all files

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

@ -91,11 +91,11 @@
<note title="Requirements Language"> <note title="Requirements Language">
<t>The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL <t>The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL
NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED",
are to be interpreted as described in <xref target="RFC2119">RFC "MAY", and "OPTIONAL" in this document are to be interpreted as
2119</xref> only when they appear in all upper case. They may described in BCP 14 <xref target="RFC2119"/> <xref
also appear in lower or mixed case as English words, without target="RFC8174"/> when, and only when, they appear in all capitals,
normative meaning.</t> as shown here.</t>
</note> </note>
@ -223,9 +223,10 @@
community" will not overwrite diverges from the IANA's list of community" will not overwrite diverges from the IANA's list of
Well-Known communities. Quite a few Well-Known communities from Well-Known communities. Quite a few Well-Known communities from
IANA's list do not receive special treatment in Cisco IOS XR, and IANA's list do not receive special treatment in Cisco IOS XR, and
at least one specific community on Cisco IOS XR's special at least one community on Cisco IOS XR's special treatment list,
treatment list (internet == 0:0) is not really on IANA's list -- internet == 0:0, is not formally a Well-Known Community as it is
it's taken from the "Reserved" range [0x00000000-0x0000FFFF].</t> not in <xref target="IANA-WKC"/>; but taken from the Reserved
range [0x00000000-0x0000FFFF].</t>
<t>This merely notes an inconsistency. It is not a plea to <t>This merely notes an inconsistency. It is not a plea to
'protect' the entire IANA list from "set community."</t> 'protect' the entire IANA list from "set community."</t>
@ -236,7 +237,7 @@
<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>> 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>
@ -302,8 +303,9 @@
<back> <back>
<references title="Normative References"> <references title="Normative References">
<?rfc include="reference.RFC.2119"?>
<?rfc include="reference.RFC.1997"?> <?rfc include="reference.RFC.1997"?>
<?rfc include="reference.RFC.2119"?>
<?rfc include="reference.RFC.8174"?>
<reference anchor="IANA-WKC" target="https://www.iana.org/assignments/bgp-well-known-communities"> <reference anchor="IANA-WKC" target="https://www.iana.org/assignments/bgp-well-known-communities">
<front> <front>
<title>Border Gateway Protocol (BGP) Well-Known Communities</title> <title>Border Gateway Protocol (BGP) Well-Known Communities</title>