From b3211adc46f775ea6b0cb9808f67d45c7e2172ee Mon Sep 17 00:00:00 2001 From: Randy Bush Date: Fri, 21 Jun 2019 17:42:57 -0700 Subject: [PATCH] labels are what the sender is willing to accept for a prefix --- draft-ietf-lsvr-l3dl.xml | 13 +++++++++---- 1 file changed, 9 insertions(+), 4 deletions(-) diff --git a/draft-ietf-lsvr-l3dl.xml b/draft-ietf-lsvr-l3dl.xml index 80dab21..7356b47 100644 --- a/draft-ietf-lsvr-l3dl.xml +++ b/draft-ietf-lsvr-l3dl.xml @@ -1101,7 +1101,9 @@ q-->
As an MPLS enabled interface may have a label stack, see , a variable length list of labels is needed. + target="RFC3032"/>, a variable length list of labels is needed. + These are the labels the sender will accept for the prefix to + which the list is attached. The MPLS IPv4 Encapsulation describes a logical link's ability to exchange labeled IPv4 packets on one or more subnets. It does so by stating the interface's addresses the corresponding prefix - lengths, and the corresponding labels. + lengths, and the corresponding labels which will be accepted fpr + each address. The MPLS IPv4 Encapsulation describes a logical link's ability to exchange labeled IPv4 packets on one or more subnets. It does so by stating the interface's addresses, the corresponding prefix - lengths, and the corresponding labels. + lengths, and the corresponding labels which will be accepted fpr + each address. @@ -1204,7 +1208,8 @@ q--> The MPLS IPv6 Encapsulation describes a logical link's ability to exchange labeled IPv6 packets on one or more subnets. It does so by stating the interface's addresses, the corresponding prefix - lengths, and the corresponding labels. + lengths, and the corresponding labels which will be accepted fpr + each address.