draft-ietf-pals-seamless-vccv-01.txt   draft-ietf-pals-seamless-vccv-02.txt 
Internet Engineering Task Force V. Govindan Internet Engineering Task Force V. Govindan
Internet-Draft C. Pignataro Internet-Draft C. Pignataro
Updates: 5885 (if approved) Cisco Systems Updates: 5885 (if approved) Cisco Systems
Intended status: Standards Track February 4, 2016 Intended status: Standards Track February 22, 2016
Expires: August 7, 2016 Expires: August 25, 2016
Seamless BFD for VCCV Seamless BFD for VCCV
draft-ietf-pals-seamless-vccv-01 draft-ietf-pals-seamless-vccv-02
Abstract Abstract
This document extends the procedures and Connectivity Verification This document extends the procedures and Connectivity Verification
(CV) types already defined for Bidirectional Forwarding Detection (CV) types already defined for Bidirectional Forwarding Detection
(BFD) for Virtual Circuit Connectivity Verification (VCCV) to define (BFD) for Virtual Circuit Connectivity Verification (VCCV) to define
Seamless BFD (S-BFD) for VCCV. This document will be extended in Seamless BFD (S-BFD) for VCCV. This document updates RFC 5885,
future to include definition of procedures for S-BFD over Tunnels. extending the CV Values and the Capability Selection.
This document extends the CV values defined in RFC5885.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on August 7, 2016. This Internet-Draft will expire on August 25, 2016.
Copyright Notice Copyright Notice
Copyright (c) 2016 IETF Trust and the persons identified as the Copyright (c) 2016 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 15 skipping to change at page 2, line 15
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Background . . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Background . . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Requirements Language . . . . . . . . . . . . . . . . . . 3 1.1. Requirements Language . . . . . . . . . . . . . . . . . . 3
2. S-BFD Connectivity Verification . . . . . . . . . . . . . . . 3 2. S-BFD Connectivity Verification . . . . . . . . . . . . . . . 3
2.1. Co-existence of S-BFD and BFD capabilites . . . . . . . . 4 2.1. Co-existence of S-BFD and BFD capabilites . . . . . . . . 4
2.2. S-BFD CV Operation . . . . . . . . . . . . . . . . . . . 4 2.2. S-BFD CV Operation . . . . . . . . . . . . . . . . . . . 4
2.2.1. S-BFD Initiator Operation . . . . . . . . . . . . . . 4 2.2.1. S-BFD Initiator Operation . . . . . . . . . . . . . . 4
2.2.2. S-BFD Reflector Operation . . . . . . . . . . . . . . 4 2.2.2. S-BFD Reflector Operation . . . . . . . . . . . . . . 5
2.2.2.1. S-BFD Reflector Demultiplexing . . . . . . . . . 5 2.2.2.1. Demultiplexing . . . . . . . . . . . . . . . . . 5
2.2.2.2. S-BFD Reflector transmission of control packets . 5 2.2.2.2. Transmission of Control Packets . . . . . . . . . 5
2.2.2.3. S-BFD Reflector advertisement of target 2.2.2.3. Advertisement of Target Discriminators using LDP 5
discriminators using LDP . . . . . . . . . . . . 5 2.2.2.4. Advertisement of Target Discriminators Using L2TP 5
2.2.2.4. S-BFD Reflector advertisement of target 2.2.2.5. Provisioning of Target Discriminators . . . . . . 6
discriminators using L2TP . . . . . . . . . . . . 5
2.2.2.5. Provisioning of S-BFD Reflector target
discriminators . . . . . . . . . . . . . . . . . 5
2.2.2.6. Probing of S-BFD Reflector target discriminators
using alert discriminators . . . . . . . . . . . 5
2.3. S-BFD Encapsulation . . . . . . . . . . . . . . . . . . . 6 2.3. S-BFD Encapsulation . . . . . . . . . . . . . . . . . . . 6
2.4. S-BFD CV Types . . . . . . . . . . . . . . . . . . . . . 6 2.4. S-BFD CV Types . . . . . . . . . . . . . . . . . . . . . 6
3. Capability Selection . . . . . . . . . . . . . . . . . . . . 6 3. Capability Selection . . . . . . . . . . . . . . . . . . . . 6
4. Security Considerations . . . . . . . . . . . . . . . . . . . 7 4. Security Considerations . . . . . . . . . . . . . . . . . . . 7
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7
5.1. MPLS CV Types for the VCCV Interface Parameters Sub-TLV . 7 5.1. MPLS CV Types for the VCCV Interface Parameters Sub-TLV . 7
5.2. L2TPv3 CV Types for the VCCV Capability AVP . . . . . . . 8 5.2. L2TPv3 CV Types for the VCCV Capability AVP . . . . . . . 8
5.3. PW Associated Channel Type . . . . . . . . . . . . . . . 8 5.3. PW Associated Channel Type . . . . . . . . . . . . . . . 8
6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 9 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 9
7. Contributing Authors . . . . . . . . . . . . . . . . . . . . 9 7. Contributing Authors . . . . . . . . . . . . . . . . . . . . 9
skipping to change at page 2, line 48 skipping to change at page 2, line 43
8.2. Informative References . . . . . . . . . . . . . . . . . 10 8.2. Informative References . . . . . . . . . . . . . . . . . 10
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 10 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 10
1. Background 1. Background
BFD for VCCV [RFC5885] defines the CV types for BFD using VCCV, BFD for VCCV [RFC5885] defines the CV types for BFD using VCCV,
protocol operation and the required packet encapsulation formats. protocol operation and the required packet encapsulation formats.
This document extends those procedures, CV type values to enable This document extends those procedures, CV type values to enable
S-BFD [I-D.ietf-bfd-seamless-base] operation for VCCV. S-BFD [I-D.ietf-bfd-seamless-base] operation for VCCV.
The new S-BFD CV Types are PW demultiplexer-agnostic, and hence The new S-BFD CV Types are Pseudowire (PW) demultiplexer-agnostic,
applicable for both MPLS and Layer Two Tunneling Protocol version 3 and hence applicable for both MPLS and Layer Two Tunneling Protocol
(L2TPv3) pseudowire demultiplexers. This document concerns itself version 3 (L2TPv3) pseudowire demultiplexers. This document concerns
with the S-BFD VCCV operation over single-segment pseudowires (SS- itself with the S-BFD VCCV operation over single-segment pseudowires
PWs). The scope of this document is as follows: (SS-PWs). The scope of this document is as follows:
This specification describes procedures only for S-BFD This specification describes procedures only for S-BFD
asynchronous mode. asynchronous mode.
S-BFD Echo mode is outside the scope of this specification. S-BFD Echo mode is outside the scope of this specification.
S-BFD operation for fault detection and status signaling is S-BFD operation for fault detection and status signaling is
outside the scope of this specification. outside the scope of this specification.
This document specifies the use of a single S-BFD discriminator per
Pseudowire. There are cases where multiple S-BFD discriminators per
PW can be useful. One such cases is using different S-BFD
discriminators per Flow within a FAT PW [RFC6391]; however, the
mapping between Flows and discriminators is a prerequisite. FAT PWs
can be supported as described in Section 7 of [RFC6391].
1.1. Requirements Language 1.1. Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in "OPTIONAL" in this document are to be interpreted as described in
[RFC2119]. [RFC2119].
2. S-BFD Connectivity Verification 2. S-BFD Connectivity Verification
S-BFD protocol provides continuity check services by monitoring the S-BFD protocol provides continuity check services by monitoring the
S-BFD control packets sent and received over the VCCV channel of the S-BFD control packets sent and received over the VCCV channel of the
PW. The term <Connectivity Verification> is used throughout this PW. The term "Connectivity Verification" is used throughout this
document to be consistent with [RFC5885]. document to be consistent with [RFC5885].
This section defines the CV types to be used for S-BFD. It also This section defines the CV types to be used for S-BFD. It also
defines the procedures for S-BFD discriminator advertisement for the defines the procedures for the S-BFD reflector and S-BFD Initiator
SBD reflector and the procedure for S-BFD Initiator operation. operation.
Two CV Types are defined for S-BFD. Table 1 summarizes the S-BFD CV Two CV Types are defined for S-BFD. Table 1 summarizes the S-BFD CV
Types, grouping them by encapsulation (i.e., with versus without IP/ Types, grouping them by encapsulation (i.e., with versus without IP/
UDP headers) for fault detection only. S-BFD for fault detection and UDP headers) for fault detection only. S-BFD for fault detection and
status signaling is outside the scope of this specification. status signaling is outside the scope of this specification.
+---------------------------------------+-----------+---------------+ +----------------------------------------+-----------+--------------+
| | Fault | Fault | | | Fault | Fault |
| | Detection | Detection and | | | Detection | Detection |
| | Only | Status | | | Only | and Status |
| | | Signaling | | | | Signaling |
+---------------------------------------+-----------+---------------+ +----------------------------------------+-----------+--------------+
| S-BFD, IP/UDP Encapsulation (with | TBD1 | N/A | | S-BFD, IP/UDP Encapsulation (with | TBD1 | N/A |
| IP/UDP Headers) | (Note1) | | | IP/UDP Headers) | | |
| | | | | | | |
| S-BFD, PW-ACH Encapsulation when | TBD2 | N/A | | S-BFD, PW-ACH Encapsulation when using | TBD2 | N/A |
| using MPLS PW or L2SS Encapsulation | (Note2) | | | MPLS PW or L2-Specific Sublayer (L2SS) | | |
| when using L2TP PW (without IP/UDP | | | | Encapsulation when using L2TP PW | | |
| Headers) | | | | (without IP/UDP Headers) | | |
+---------------------------------------+-----------+---------------+ +----------------------------------------+-----------+--------------+
Table 1: Bitmask Values for BFD CV Types Table 1: Bitmask Values for BFD CV Types
Two new bits are requested from IANA to indicate S-BFD operation. Two new bits are requested from IANA to indicate S-BFD operation.
2.1. Co-existence of S-BFD and BFD capabilites 2.1. Co-existence of S-BFD and BFD capabilites
Since the CV types for S-BFD and BFD are unique, BFD and S-BFD Since the CV types for S-BFD and BFD are unique, BFD and S-BFD
capabilities can be advertised concurrently. capabilities can be advertised concurrently.
2.2. S-BFD CV Operation 2.2. S-BFD CV Operation
2.2.1. S-BFD Initiator Operation 2.2.1. S-BFD Initiator Operation
The S-BFD Initiator SHOULD bootstrap S-BFD sessions after it learns The S-BFD Initiator SHOULD bootstrap S-BFD sessions after it learns
the discriminator of the remote target identifier through one or more the discriminator of the remote target identifier. This can be
of the following methods: achieved, for example but not limited to, through one or more of the
following methods:
1. Advertisements of S-BFD discriminators made through AVP/ TLVs 1. Advertisements of S-BFD discriminators made through a PW
defined in L2TP/ LDP. signaling protocol, for example AVP/TLVs defined in L2TP/LDP.
2. Provisioning of S-BFD discriminators. 2. Provisioning of S-BFD discriminators by manual configuration of
the PE/LCCEs.
3. Probing remote S-BFD discriminators through S-BFD Alert 3. Assignment of S-BFD discriminators by a controller.
discriminators [I-D.akiya-bfd-seamless-alert-discrim]
4. Probing remote S-BFD discriminators through a mechanism such as
S-BFD Alert discriminators [I-D.akiya-bfd-seamless-alert-discrim]
S-BFD Initiator operation MUST be according to the specifications in S-BFD Initiator operation MUST be according to the specifications in
Section 7.2 of [I-D.ietf-bfd-seamless-base]. Section 7.2 of [I-D.ietf-bfd-seamless-base].
2.2.2. S-BFD Reflector Operation 2.2.2. S-BFD Reflector Operation
When as pseudowire signalling protocol such as LDP or L2TPv3 is in When a pseudowire signalling protocol such as LDP or L2TPv3 is in
use the S-BFD Reflector advertises its target discriminators using use, the S-BFD Reflector can advertise its target discriminators
that signalling protocol. When static PWs are in use the target using that signalling protocol. When static PWs are in use the
discriminator of S-BFD needs to be provisioned on the S-BFD target discriminator of S-BFD needs to be provisioned on the S-BFD
Initiator nodes. Initiator nodes.
All point to point pseudowires are bidirectional, the S-BFD All point to point pseudowires are bidirectional, the S-BFD
Reflector therefore reflects the S-BFD packet back to the Reflector therefore reflects the S-BFD packet back to the
Initiator using the VCCV channel of the reverse direction of the Initiator using the VCCV channel of the reverse direction of the
PW on which it was received. PW on which it was received.
It is observed that the reflector has enough information to It is observed that the reflector has enough information to
reflect the S-BFD Async packet received by it back to the S-BFD reflect the S-BFD Async packet received by it back to the S-BFD
initiator using the fields of the L2TPv3 headers. initiator using the PW context (e.g., fields of the L2TPv3
headers).
S-BFD Reflector operation for BFD protocol fields MUST be S-BFD Reflector operation for BFD protocol fields MUST be
according to the specifications in Section TBD of according to the specifications of [I-D.ietf-bfd-seamless-base].
[I-D.ietf-bfd-seamless-base].
2.2.2.1. S-BFD Reflector Demultiplexing 2.2.2.1. Demultiplexing
TBD Demultiplexing of S-BFD is achieved using the PW context, following
the procedures in Section 7.1 of [I-D.ietf-bfd-seamless-base].
2.2.2.2. S-BFD Reflector transmission of control packets 2.2.2.2. Transmission of Control Packets
The procedures of S-BFD Reflector described in The procedures of S-BFD Reflector described in
[I-D.ietf-bfd-seamless-base] apply for S-BFD using VCCV. [I-D.ietf-bfd-seamless-base] apply for S-BFD using VCCV.
2.2.2.3. S-BFD Reflector advertisement of target discriminators using 2.2.2.3. Advertisement of Target Discriminators using LDP
LDP
TBD. The advertisement of the target discriminator using LDP is left for
further study. It should be noted that S-BFD can still be used with
signaled PWs over an MPLS PSN, by provisioning of the S-BFD
discriminators or by learning the S-BFD discriminators by other
means.
2.2.2.4. S-BFD Reflector advertisement of target discriminators using 2.2.2.4. Advertisement of Target Discriminators Using L2TP
L2TP
The S-BFD Reflector MUST use the AVP The S-BFD Reflector MUST use the AVP
[I-D.ietf-l2tpext-sbfd-discriminator] defined for advertising its [I-D.ietf-l2tpext-sbfd-discriminator] defined for advertising its
target discriminators using L2TP. target discriminators using L2TP.
2.2.2.5. Provisioning of S-BFD Reflector target discriminators 2.2.2.5. Provisioning of Target Discriminators
S-BFD target discriminators MAY be provisioned when static PWs are S-BFD target discriminators MAY be provisioned when static PWs are
used. used.
2.2.2.6. Probing of S-BFD Reflector target discriminators using alert
discriminators
S-BFD alert discriminators MAY be used to probe S-BFD target
discriminators. If a node implements S-BFD reflector, it SHOULD
respond to Alert discriminator requests received from potential S-BFD
Initiators.
2.3. S-BFD Encapsulation 2.3. S-BFD Encapsulation
Unless specified differently below, the encapsulation of S-BFD Unless specified differently below, the encapsulation of S-BFD
packets is the identical the method specified in Sec.3.2 [RFC5885] packets is identical to the method specified in Section 3.2 [RFC5885]
and in [RFC5880] for the encapsulation of BFD packets. and in [RFC5880] for the encapsulation of BFD packets.
o IP/UDP BFD Encapsulation (BFD with IP/UDP Headers) o IP/UDP BFD Encapsulation (BFD with IP/UDP Headers)
* The destination UDP port for the IP encapsulated S-BFD packet * The destination UDP port for the IP encapsulated S-BFD packet
MUST be 7784 [I-D.ietf-bfd-seamless-base]. MUST be 7784 [I-D.ietf-bfd-seamless-ip].
* The encapsulation of the S-BFD header fields MUST be according * The encapsulation of the S-BFD header fields MUST be according
to Sec.7.2.2 of [I-D.ietf-bfd-seamless-base]. to Section 7.3.2 of [I-D.ietf-bfd-seamless-base].
o PW-ACH/ L2SS BFD Encapsulation (BFD without IP/UDP Headers) o PW-ACH/ L2SS BFD Encapsulation (BFD without IP/UDP Headers)
* The encapsulation of S-BFD packets using this format MUST be * The encapsulation of S-BFD packets using this format MUST be
according to Sec.3.2 of [RFC5885] with the exception of the PW- according to Section 3.2 of [RFC5885] with the exception of the
ACH/ L2SS type. value for the PW-ACH/L2SS type.
* When VCCV carries PW-ACH/ L2SS-encapsulated S-BFD (i.e., "raw" * When VCCV carries PW-ACH/ L2SS-encapsulated S-BFD (i.e., "raw"
S-BFD), the PW-ACH (pseudowire CW's) or L2SS' Channel Type MUST S-BFD), the PW-ACH (pseudowire CW's) or L2SS' Channel Type MUST
be set to TBD2 to indicate "S-BFD Control, PW-ACH/ L2SS- be set to TBD3 to indicate "S-BFD Control, PW-ACH/ L2SS-
encapsulated" (i.e., S-BFD without IP/UDP headers; see encapsulated" (i.e., S-BFD without IP/UDP headers; see
Section 5.3). This is to allow the identification of the Section 5.3). This is to allow the identification of the
encased S-BFD payload when demultiplexing the VCCV control encased S-BFD payload when demultiplexing the VCCV control
channel. channel.
2.4. S-BFD CV Types 2.4. S-BFD CV Types
3. Capability Selection 3. Capability Selection
When multiple S-BFD CV Types are advertised, and after applying the When multiple S-BFD CV Types are advertised, and after applying the
skipping to change at page 7, line 8 skipping to change at page 7, line 8
number CV Type, and the CV Type with the lowest list number is used: number CV Type, and the CV Type with the lowest list number is used:
1. TBD1 - S-BFD IP/UDP-encapsulated, for PW Fault Detection only. 1. TBD1 - S-BFD IP/UDP-encapsulated, for PW Fault Detection only.
2. TBD2 - S-BFD PW-ACH/ L2SS-encapsulated (without IP/UDP headers), 2. TBD2 - S-BFD PW-ACH/ L2SS-encapsulated (without IP/UDP headers),
for PW Fault Detection only. for PW Fault Detection only.
The order of capability selection between S-BFD and BFD is defined as The order of capability selection between S-BFD and BFD is defined as
follows: follows:
+--------------------------+-----------+-----------+----------------+ +----------------------------+---------+----------+-----------------+
| Advertised capabilities | BFD Only | SBFD Only | Both S-BFD and | | Advertised capabilities of | BFD | SBFD | Both S-BFD and |
| of PE1/ PE2 | | | BFD | | PE1/ PE2 | Only | Only | BFD |
+--------------------------+-----------+-----------+----------------+ +----------------------------+---------+----------+-----------------+
| BFD Only | BFD | None | BFD Only | | BFD Only | BFD | None | BFD Only |
| | | (Note1) | | | | | | |
| | | | | | S-BFD Only | None | S-BFD | S-BFD only |
| S-BFD Only | None | S-BFD | S-BFD only | | | | | |
| | (Note1) | | | | Both S-BFD and BFD | BFD | S-BFD | Both SBFD and |
| | | | | | | only | only | BFD |
| Both S-BFD and BFD | BFD only | S-BFD | Both SBFD and | +----------------------------+---------+----------+-----------------+
| | | only | BFD |
+--------------------------+-----------+-----------+----------------+
Table 2: Capability Selection Matrix for BFD and S-BFD Table 2: Capability Selection Matrix for BFD and S-BFD
Note1: Can we mandate failing the bringup of the PW in case of a
capability mismatch?
4. Security Considerations 4. Security Considerations
Security measures described in [RFC5885] and Security considerations for VCCV are addressed in Section 10 of
[I-D.ietf-bfd-seamless-base] are to be followed. [RFC5085]. The introduction of the S-BFD Connectivity Verification
(CV) Types introduces no new security risks for VCCV. Routers that
implement the additional CV Types defined herein are subject to the
same security considerations as defined in [RFC5085], as well as
[I-D.ietf-bfd-seamless-base].
This specification does not raise any additional security issues
beyond these.
5. IANA Considerations 5. IANA Considerations
5.1. MPLS CV Types for the VCCV Interface Parameters Sub-TLV 5.1. MPLS CV Types for the VCCV Interface Parameters Sub-TLV
The VCCV Interface Parameters Sub-TLV codepoint is defined in The VCCV Interface Parameters Sub-TLV codepoint is defined in
[RFC4446], and the VCCV CV Types registry is defined in [RFC5085]. [RFC4446], and the VCCV CV Types registry is defined in [RFC5085].
This section lists the new BFD CV Types. This section lists the new BFD CV Types.
IANA has augmented the "VCCV Connectivity Verification (CV) Types" IANA has augmented the "MPLS VCCV Connectivity Verification (CV)
registry in the Pseudowire Name Spaces reachable from [IANA]. These Types" registry in the Pseudowire Name Spaces reachable from
are bitfield values. CV Type values TBD are specified in Section 2 [IANA-PWE3]. These are bitfield values. CV Type values are
of this document. specified in Section 2 of this document.
MPLS Connectivity Verification (CV) Types: MPLS Connectivity Verification (CV) Types:
Bit (Value) Description Reference Bit (Value) Description Reference
=========== =========== ============== =========== =========== ==============
TBD1(0xY) S-BFD IP/UDP-encapsulated, this document TBD1(0xY) S-BFD IP/UDP-encapsulated, This document
for PW Fault Detection only for PW Fault Detection only
TBD2(0xZ) S-BFD PW-ACH/L2SS-encapsulated, this document TBD2(0xZ) S-BFD PW-ACH-encapsulated, This document
for PW Fault Detection only for PW Fault Detection only
5.2. L2TPv3 CV Types for the VCCV Capability AVP 5.2. L2TPv3 CV Types for the VCCV Capability AVP
This section lists the new requests for S-BFD CV Types to be added to This section lists the new requests for S-BFD "L2TPv3 Connectivity
the existing "VCCV Capability AVP" registry in the L2TP name spaces. Verification (CV) Types" to be added to the existing "VCCV Capability
The Layer Two Tunneling Protocol "L2TP" Name Spaces are reachable AVP" registry in the L2TP name spaces. The Layer Two Tunneling
from [IANA]. IANA is requested to assign the following L2TPv3 Protocol "L2TP" Name Spaces are reachable from [IANA-L2TP]. IANA is
Connectivity Verification (CV) Types in the VCCV Capability AVP requested to assign the following L2TPv3 Connectivity Verification
Values registry. (CV) Types in the VCCV Capability AVP Values registry.
VCCV Capability AVP (Attribute Type 96) Values VCCV Capability AVP (Attribute Type 96) Values
---------------------------------------------- ----------------------------------------------
L2TPv3 Connectivity Verification (CV) Types: L2TPv3 Connectivity Verification (CV) Types:
Bit (Value) Description Reference Bit (Value) Description Reference
=========== =========== ============== =========== =========== ==============
TBD1(0xY) S-BFD IP/UDP-encapsulated, this document TBD1(0xY) S-BFD IP/UDP-encapsulated, This document
for PW Fault Detection only for PW Fault Detection only
TBD2(0xZ) S-BFD L2SS-encapsulated, this document TBD2(0xZ) S-BFD L2SS-encapsulated, This document
for PW Fault Detection only for PW Fault Detection only
5.3. PW Associated Channel Type 5.3. PW Associated Channel Type
As per the IANA considerations in [RFC5586], IANA is requested to As per the IANA considerations in [RFC5586], IANA is requested to
allocate the following Channel Types in the "MPLS Generalized allocate the following Channel Types in the "MPLS Generalized
Associated Channel (G-ACh) Types" registry: Associated Channel (G-ACh) Types" registry:
IANA has reserved a new Pseudowire Associated Channel Type value as IANA has reserved a new Pseudowire Associated Channel Type value as
follows: follows:
Registry: Registry:
TLV TLV
Value Description Follows Reference Value Description Follows Reference
------ ---------------------------------- ------- --------------- ------ ---------------------------------- ------- ---------------
TBD2 S-BFD Control, PW-ACH/L2SS No [This document] TBD3 S-BFD Control, PW-ACH/L2SS No [This document]
encapsulation encapsulation
(without IP/UDP Headers) (without IP/UDP Headers)
6. Acknowledgements 6. Acknowledgements
Authors would like to thank Nobo Akiya, Stewart Bryant, Pawel The authors would like to thank Nobo Akiya, Stewart Bryant, Greg
Sowinski and Greg Mirsky for providing the core inputs of this Mirsky, and Pawel Sowinski, Yuanlong, Andrew Malis, and Alexander
document and for performing thorough reviews and providing number of Vainshtein for providing input to this document and for performing
comments. Authors would also like to thank Yuanlong for comments thorough reviews and useful comments.
received.
7. Contributing Authors 7. Contributing Authors
Mallik Mudigonda Mallik Mudigonda
Cisco Systems Cisco Systems
Email: mmudigon@cisco.com Email: mmudigon@cisco.com
8. References 8. References
8.1. Normative References 8.1. Normative References
[I-D.akiya-bfd-seamless-alert-discrim]
Akiya, N., Pignataro, C., and D. Ward, "Seamless
Bidirectional Forwarding Detection (S-BFD) Alert
Discriminator", draft-akiya-bfd-seamless-alert-discrim-03
(work in progress), October 2014.
[I-D.ietf-bfd-seamless-base] [I-D.ietf-bfd-seamless-base]
Akiya, N., Pignataro, C., Ward, D., Bhatia, M., and J. Akiya, N., Pignataro, C., Ward, D., Bhatia, M., and J.
Networks, "Seamless Bidirectional Forwarding Detection Networks, "Seamless Bidirectional Forwarding Detection
(S-BFD)", draft-ietf-bfd-seamless-base-05 (work in (S-BFD)", draft-ietf-bfd-seamless-base-07 (work in
progress), February 2016.
[I-D.ietf-bfd-seamless-ip]
Akiya, N., Pignataro, C., and D. Ward, "Seamless
Bidirectional Forwarding Detection (S-BFD) for IPv4, IPv6
and MPLS", draft-ietf-bfd-seamless-ip-02 (work in
progress), June 2015. progress), June 2015.
[I-D.ietf-l2tpext-sbfd-discriminator] [I-D.ietf-l2tpext-sbfd-discriminator]
Govindan, V. and C. Pignataro, "Advertising S-BFD Govindan, V. and C. Pignataro, "Advertising S-BFD
Discriminators in L2TPv3", draft-ietf-l2tpext-sbfd- Discriminators in L2TPv3", draft-ietf-l2tpext-sbfd-
discriminator-02 (work in progress), January 2016. discriminator-02 (work in progress), January 2016.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997, DOI 10.17487/RFC2119, March 1997,
skipping to change at page 10, line 27 skipping to change at page 10, line 22
<http://www.rfc-editor.org/info/rfc5880>. <http://www.rfc-editor.org/info/rfc5880>.
[RFC5885] Nadeau, T., Ed. and C. Pignataro, Ed., "Bidirectional [RFC5885] Nadeau, T., Ed. and C. Pignataro, Ed., "Bidirectional
Forwarding Detection (BFD) for the Pseudowire Virtual Forwarding Detection (BFD) for the Pseudowire Virtual
Circuit Connectivity Verification (VCCV)", RFC 5885, Circuit Connectivity Verification (VCCV)", RFC 5885,
DOI 10.17487/RFC5885, June 2010, DOI 10.17487/RFC5885, June 2010,
<http://www.rfc-editor.org/info/rfc5885>. <http://www.rfc-editor.org/info/rfc5885>.
8.2. Informative References 8.2. Informative References
[IANA] Internet Assigned Numbers Authority, "Protocol [I-D.akiya-bfd-seamless-alert-discrim]
Registries", <http://www.iana.org>. Akiya, N., Pignataro, C., and D. Ward, "Seamless
Bidirectional Forwarding Detection (S-BFD) Alert
Discriminator", draft-akiya-bfd-seamless-alert-discrim-03
(work in progress), October 2014.
[IANA-L2TP]
Internet Assigned Numbers Authority, "Layer Two Tunneling
Protocol "L2TP"", May 2015,
<http://www.iana.org/assignments/l2tp-parameters>.
[IANA-PWE3]
Internet Assigned Numbers Authority, "Pseudowire Name
Spaces (PWE3)", January 2016,
<http://www.iana.org/assignments/pwe3-parameters>.
[RFC6391] Bryant, S., Ed., Filsfils, C., Drafz, U., Kompella, V.,
Regan, J., and S. Amante, "Flow-Aware Transport of
Pseudowires over an MPLS Packet Switched Network",
RFC 6391, DOI 10.17487/RFC6391, November 2011,
<http://www.rfc-editor.org/info/rfc6391>.
Authors' Addresses Authors' Addresses
Vengada Prasad Govindan Vengada Prasad Govindan
Cisco Systems Cisco Systems
Email: venggovi@cisco.com Email: venggovi@cisco.com
Carlos Pignataro Carlos Pignataro
Cisco Systems Cisco Systems
Email: cpignata@cisco.com Email: cpignata@cisco.com
 End of changes. 45 change blocks. 
125 lines changed or deleted 144 lines changed or added

This html diff was produced by rfcdiff 1.42. The latest version is available from http://tools.ietf.org/tools/rfcdiff/