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

kill Restart PDU

Browse source 
clarify unique attr type so v4 and v6 allowed in same pdu
This commit is contained in:
Randy Bush 2022-03-20 18:17:44 -07:00
parent cb9258ff64
commit 99a4d37104
1 changed files with 26 additions and 21 deletions
Download patch file Download diff file Expand all files Collapse all files

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

@ -103,7 +103,7 @@
PDU is defined as follows:</t> PDU is defined as follows:</t>
<!-- <!--
protocol "Version = 0:8,Type = 8:8,Payload Length:32,ULPC Type:8,AttrCount:8,Serial Number:32,Attribute List ...:32" protocol "Version = 0:8,Type = 8:8,Payload Length:32,ULPC Type:8,AttrCount:8,Serial Number:32,Attribute Sub-TLV List ...:32"
--> -->
<figure> <figure>
@ -189,13 +189,13 @@
for an particular address family on a specific link at any point for an particular address family on a specific link at any point
in time; receipt of a new BGP ULPC PDU for a particular address in time; receipt of a new BGP ULPC PDU for a particular address
family replaces the data any previous one; but does not actually family replaces the data any previous one; but does not actually
affect the session unless there is a BGP Restart Attribute affect the session<!-- unless there is a BGP Restart Attribute
sub-TLV.</t> sub-TLV-->.</t>
<t>If there are one or more open BGP sessions, absent a BGP <t>If there are one or more open BGP sessions, <!-- absent a BGP
Restart sub-TLV, receipt of a new BGP ULPC PDU SHOULD not affect Restart sub-TLV, --> receipt of a new BGP ULPC PDU SHOULD not
these sessions. The received data are stored for a future session affect these sessions. The received data are stored for a future
restart.</t> session restart.</t>
<t>As a link may have multiple encapsulations and multiple <t>As a link may have multiple encapsulations and multiple
addresses for an IP encapsulation, which address of which addresses for an IP encapsulation, which address of which
@ -210,22 +210,27 @@
<t>If a peering address has been announced as a loopback, i.e. <t>If a peering address has been announced as a loopback, i.e.
MUST BE flagged as such in the L3ND Encapsulation PDU (see <xref MUST BE flagged as such in the L3ND Encapsulation PDU (see <xref
target="I-D.ymbk-idr-l3nd"/> Sec. 10.2), a two or three hop BGP target="I-D.ymbk-idr-l3nd"/> Sec. 10.2), a two or three hop BGP
session MUST be established. Otherwise a direct one hop session session MUST be established as needed. Otherwise a direct one hop
is used. The BGP session to a loopback will forward to the peer's session is used. The BGP session to a loopback will forward to
address which was marked as Primary in the L3ND Encapsulation the peer's address which was marked as Primary in the L3ND
Flags, iff it is in a subnet which is shared with both BGP Encapsulation Flags, iff it is in a subnet which is shared with
speakers. If the primary is not in a common subnet, then the BGP both BGP speakers. If the primary is not in a common subnet, then
speaker MAY pick a forwarding next hop that is in a subnet they the BGP speaker MAY pick a forwarding next hop that is in a subnet
share. If there are multiple choices, the BGP speaker SHOULD have they share. If there are multiple choices, the BGP speaker SHOULD
signaled which subnet to choose in an Upper-Layer Protocol have signaled which subnet to choose in an Upper-Layer Protocol
Configuration PDU Attribute.</t> Configuration PDU Attribute.</t>
<t>Attributes MUST be unique in the Attribute List. I.e. a <t>Attributes MUST be unique in the Attribute List. I.e. a
particular Attr Type MUST NOT occur more than once in the particular Attr Type MUST NOT occur more than once in the
Attribute List. If a ULPC PDU is received with multiple Attribute List. If a ULPC PDU is received with more than one
occurances of the same Attr Type, an Error ACK should be occurrence of a particular Attr Type, an Error ACK MUST be
returned.</t> returned.</t>
<t>As there are separate PDU Attr Types for IPv4 and IPv6 peering
addresses, separate sessions for the two AFIs MAY be created for
the same ASN in one ULPC PDU.</t>
<!--
<section anchor="restart" title="BGP Restart"> <section anchor="restart" title="BGP Restart">
<t>When all attributes in PDU have been processed, stop the <t>When all attributes in PDU have been processed, stop the
@ -238,9 +243,9 @@
<t>If there is no current BGP session to the specified peer, <t>If there is no current BGP session to the specified peer,
start one.</t> start one.</t>
<!-- <!- -
protocol "Attr Type = 0:8,Attr Len = 4/16:8,Dest IP:128" protocol "Attr Type = 0:8,Attr Len = 4/16:8,Dest IP:128"
--> - ->
<figure> <figure>
<artwork> <artwork>
@ -260,7 +265,7 @@
</artwork> </artwork>
</figure> </figure>
</section> </section>
-->
<section anchor="asn" title="BGP ASN"> <section anchor="asn" title="BGP ASN">
<t>The four octet Autonomous System number MUST be specified. <t>The four octet Autonomous System number MUST be specified.
@ -323,7 +328,7 @@
<t>As usual, the BGP OPEN capability negotiation will determine <t>As usual, the BGP OPEN capability negotiation will determine
the AFI/SAFIs to be transported over the peering, see <xref the AFI/SAFIs to be transported over the peering, see <xref
target="RFC4760"/> .</t> target="RFC4760"/>.</t>
<!-- <!--
protocol "Attr Type = 3:8,Attr Len = 17:8,My IPv6 Peering Address:128,Prefix Len:8" protocol "Attr Type = 3:8,Attr Len = 17:8,My IPv6 Peering Address:128,Prefix Len:8"