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

small hacks, octet counts, ...

Browse source
This commit is contained in:
Randy Bush 2022-03-07 04:03:14 -08:00
parent 5cb85c4cff
commit a7aacbdd5a
1 changed files with 11 additions and 11 deletions
Download patch file Download diff file Expand all files Collapse all files

22
draft-ymbk-idr-l3nd-ulpc.xml
View file

@ -135,16 +135,16 @@
deployments use.</t> deployments use.</t>
<?rfc subcompact="yes"?> <?rfc subcompact="yes"?>
<t>ULPC Type: An integer denoting the type of the upper-layer <t>ULPC Type: A one byte integer denoting the type of the
protocol upper-layer protocol
<list style="hanging" hangIndent="6"> <list style="hanging" hangIndent="6">
<t hangText="0 :">Reserved</t> <t hangText="0 :">Reserved</t>
<t hangText="1 :">BGP</t> <t hangText="1 :">BGP</t>
<t hangText="2-255 :">Reserved</t> <t hangText="2-255 :">Reserved</t>
<?rfc subcompact="no"?></list></t> <?rfc subcompact="no"?></list></t>
<t>The AttrCount is the number of attribute sub-TLVs in the <t>The one octet AttrCount is the number of attribute sub-TLVs in
Attribute List.</t> the Attribute List.</t>
<t>The Attribute List is a, possibly null, set of sub-TLVs <t>The Attribute List is a, possibly null, set of sub-TLVs
describing the configuration attributes of the specific upper-layer describing the configuration attributes of the specific upper-layer
@ -183,7 +183,7 @@
<t>If there are multiple BGP sessions on a link, e.g., IPv4 and <t>If there are multiple BGP sessions on a link, e.g., IPv4 and
IPv6, then multiple sets of BGP sub-TLVs MAY BE exchanged within IPv6, then multiple sets of BGP sub-TLVs MAY BE exchanged within
the BGP ULPC PDU or multiple BGP ULPC PDUs may be sent, one for the BGP ULPC PDU or sepatate BGP ULPC PDUs may be sent, one for
each address family.</t> each address family.</t>
<t>A peer receiving BGP ULPC PDUs has only one active BGP ULPC PDU <t>A peer receiving BGP ULPC PDUs has only one active BGP ULPC PDU
@ -208,11 +208,11 @@
Attribute may be used to signal preferences.</t> Attribute may be used to signal preferences.</t>
<t>If a peering address has been announced as a loopback, <t>If a peering address has been announced as a loopback,
i.e. MUST BE flagged as such in the L3DL Encapsulation PDU (see i.e. MUST BE flagged as such in the L3ND Encapsulation PDU (see
<xref target="I-D.ymbk-idr-l3nd"/> Sec. 10.3), a two or three <xref target="I-D.ymbk-idr-l3nd"/> Sec. 10.3), a two or three
hop BGP session will be established. Otherwise a direct one hop hop BGP session will be established. Otherwise a direct one hop
session is used. The BGP session to a loopback will forward to session is used. The BGP session to a loopback will forward to
the peer's address which was marked as Primary in the L3DL the peer's address which was marked as Primary in the L3ND
Encapsulation Flags, iff it is in a subnet which is shared with Encapsulation Flags, iff it is in a subnet which is shared with
both BGP speakers. If the primary is not in a common subnet, then both BGP speakers. If the primary is not in a common subnet, then
the BGP speaker MAY pick a forwarding next hop that is in a subnet the BGP speaker MAY pick a forwarding next hop that is in a subnet
@ -345,7 +345,7 @@
<t>The BGP session OPEN has extensive, and a bit complex, <t>The BGP session OPEN has extensive, and a bit complex,
capability negotiation facilities. In case one or more extra capability negotiation facilities. In case one or more extra
attributes might be needed, the BGP Miscellaneous Flags sub-TLV attributes might be needed, the BGP Miscellaneous Flags sub-TLV
may be used. No flags are currently defined.</t> may be used.</t>
<!-- <!--
protocol "Attr Type = 5:8,Attr Len = 4:8,Misc Flags:16" protocol "Attr Type = 5:8,Attr Len = 4:8,Misc Flags:16"
--> -->
@ -397,7 +397,7 @@
<section anchor="iana" title="IANA Considerations"> <section anchor="iana" title="IANA Considerations">
<t>This document requests the IANA create a new entry in the L3DL PDU <t>This document requests the IANA create a new entry in the L3ND PDU
Type registry as follows:</t> Type registry as follows:</t>
<figure> <figure>
<artwork> <artwork>
@ -408,9 +408,9 @@
</artwork> </artwork>
</figure> </figure>
<t>This document requests the IANA create a registry for L3DL ULPC <t>This document requests the IANA create a registry for L3ND ULPC
Type, which may range from 0 to 255. The name of the registry Type, which may range from 0 to 255. The name of the registry
should be L3DL-ULPC-Type. The policy for adding to the registry is should be L3ND-ULPC-Type. The policy for adding to the registry is
RFC Required per <xref target="RFC5226"/>, either standards track or RFC Required per <xref target="RFC5226"/>, either standards track or
experimental. The initial entries should be the following:</t> experimental. The initial entries should be the following:</t>
<figure> <figure>