From b5c9018642ef50897f25507b34331b27836f80b7 Mon Sep 17 00:00:00 2001 From: Randy Bush Date: Thu, 30 May 2019 17:13:39 -0700 Subject: [PATCH] make clear announcement is only what's actually on the interface --- draft-ietf-lsvr-l3dl.xml | 19 +++++++++++-------- 1 file changed, 11 insertions(+), 8 deletions(-) diff --git a/draft-ietf-lsvr-l3dl.xml b/draft-ietf-lsvr-l3dl.xml index 2c19af2..678e639 100644 --- a/draft-ietf-lsvr-l3dl.xml +++ b/draft-ietf-lsvr-l3dl.xml @@ -275,13 +275,16 @@ discovery of new devices coming up on a multi-link topology, devices send periodic HELLOs forever, see . - Once a new device is recognized, both devices attempt to negotiate - and establish peering by sending unicast OPEN PDUs (). In an established peering, Encapsulations () 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. + Once a new device is recognized, both devices attempt to + negotiate and establish peering by sending unicast OPEN PDUs (). In an established peering, the Encapsulations + () 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.
@@ -378,7 +381,7 @@ If a PDU does not fit in a single datagram, it is broken into multiple datagrams and reassembled by the receiver a la . + target="RFC0791"/> Section 2.3 Fragmentation..