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

make clear announcement is only what's actually on the interface

Browse source
This commit is contained in:
Randy Bush 2019-05-30 17:13:39 -07:00
parent ac441e4246
commit b5c9018642
1 changed files with 11 additions and 8 deletions
Download patch file Download diff file Expand all files Collapse all files

19
draft-ietf-lsvr-l3dl.xml
View file

@ -275,13 +275,16 @@
discovery of new devices coming up on a multi-link topology, devices
send periodic HELLOs forever, see <xref target="dhello"/>.</t>
<t>Once a new device is recognized, both devices attempt to negotiate
and establish peering by sending unicast OPEN PDUs (<xref
target="open"/>). In an established peering, Encapsulations (<xref
target="afisafi"/>) may be announced and modified. When two
devices on a link have compatible Encapsulations and addresses,
i.e. the same AFI/SAFI and the same subnet, the link is announced
via the BGP-LS API.</t>
<t>Once a new device is recognized, both devices attempt to
negotiate and establish peering by sending unicast OPEN PDUs (<xref
target="open"/>). In an established peering, the Encapsulations
(<xref target="afisafi"/>) configured on an end point may be
announced and modified. Note that these are only the encapsuation
and addresses on the announcing interface; though a device's
loopback interface(s) may also be announced. When two devices on a
link have compatible Encapsulations and addresses, i.e. the same
AFI/SAFI and the same subnet, the link is announced via the BGP-LS
API.</t>
<section anchor="ladder" title="L3DL Ladder Diagram">
@ -378,7 +381,7 @@
<t>If a PDU does not fit in a single datagram, it is broken into
multiple datagrams and reassembled by the receiver a la <xref
target="RFC0791"/>.</t>
target="RFC0791"/> Section 2.3 Fragmentation..</t>
<!--
protocol "Version:8,L:1,Datagram Number:7,Datagram Length:16,Checksum:32"