One document matched: draft-ietf-mpls-lsp-ping-mpls-tp-oam-conf-06.xml
<?xml version="1.0" encoding="US-ASCII"?>
<!-- This template is for creating an Internet Draft using xml2rfc,
which is available here: http://xml.resource.org. -->
<!DOCTYPE rfc SYSTEM "rfc2629.dtd" [
<!-- One method to get references from the online citation libraries.
There has to be one entity for each item to be referenced.
An alternate method (rfc include) is described in the references. -->
<!ENTITY RFC2119 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2119.xml">
<!ENTITY RFC2629 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2629.xml">
<!ENTITY RFC3552 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.3552.xml">
<!ENTITY I-D.narten-iana-considerations-rfc2434bis SYSTEM "http://xml.resource.org/public/rfc/bibxml3/reference.I-D.narten-iana-considerations-rfc2434bis.xml">
]>
<?xml-stylesheet type='text/xsl' href='rfc2629.xslt' ?>
<!-- used by XSLT processors -->
<!-- For a complete list and description of processing instructions (PIs),
please see http://xml.resource.org/authoring/README.html. -->
<!-- Below are generally applicable Processing Instructions (PIs) that most I-Ds might want to use.
(Here they are set differently than their defaults in xml2rfc v1.32) -->
<?rfc strict="yes" ?>
<!-- give errors regarding ID-nits and DTD validation -->
<!-- control the table of contents (ToC) -->
<?rfc toc="yes"?>
<!-- generate a ToC -->
<?rfc tocdepth="4"?>
<!-- the number of levels of subsections in ToC. default: 3 -->
<!-- control references -->
<?rfc symrefs="yes"?>
<!-- use symbolic references tags, i.e, [RFC2119] instead of [1] -->
<?rfc sortrefs="yes" ?>
<!-- sort the reference entries alphabetically -->
<!-- control vertical white space
(using these PIs as follows is recommended by the RFC Editor) -->
<?rfc compact="yes" ?>
<!-- do not start each main section on a new page -->
<?rfc subcompact="no" ?>
<!-- keep one blank line between list items -->
<!-- end of list of popular I-D processing instructions -->
<rfc category="std" docName="draft-ietf-mpls-lsp-ping-mpls-tp-oam-conf-06"
ipr="trust200902">
<!-- category values: std, bcp, info, exp, and historic
ipr values: full3667, noModification3667, noDerivatives3667
you can add the attributes updates="NNNN" and obsoletes="NNNN"
they will automatically be output with "(if approved)" -->
<!-- ***** FRONT MATTER ***** -->
<front>
<!-- The abbreviated title is used in the page header - it is only necessary if the
full title is longer than 39 characters -->
<title abbrev="Extensions for MPLS-TP OAM Conf">Configuration of Pro-Active
Operations, Administration, and Maintenance (OAM) Functions for MPLS-based Transport Networks using
LSP Ping</title>
<!-- add 'role="editor"' below for the editors if appropriate -->
<!-- Another author who claims to be an editor -->
<author fullname="Elisa Bellagamba" initials="E.B." role="editor"
surname="Bellagamba">
<organization>Ericsson</organization>
<address>
<postal>
<street>Torshamnsgatan 48</street>
<!-- Reorder these if your country does things differently -->
<city>Kista</city>
<region></region>
<code>164 40</code>
<country>Sweden</country>
</postal>
<email>elisa.bellagamba@ericsson.com</email>
<!-- uri and facsimile elements may also be added -->
</address>
</author>
<author fullname="Loa Andersson" initials="L.A."
surname="Andersson">
<organization>Huawei</organization>
<address>
<postal>
<street>Skanorvagen 3</street>
<!-- Reorder these if your country does things differently -->
<city>Johanneshov</city>
<region></region>
<code>121 52</code>
<country>Sweden</country>
</postal>
<phone></phone>
<email>loa@mail01.huawei.com</email>
<!-- uri and facsimile elements may also be added -->
</address>
</author>
<author fullname="Pontus Skoldstrom" initials="P.S." role="editor"
surname="Skoldstrom">
<organization>Acreo AB</organization>
<address>
<postal>
<street>Electrum 236</street>
<!-- Reorder these if your country does things differently -->
<city>Kista</city>
<region></region>
<code>164 40</code>
<country>Sweden</country>
</postal>
<phone>+46 8 6327731</phone>
<email>pontus.skoldstrom@acreo.se</email>
<!-- uri and facsimile elements may also be added -->
</address>
</author>
<author fullname="Dave Ward" initials="D.W." surname="Ward">
<organization>Cisco</organization>
<address>
<postal>
<street></street>
<!-- Reorder these if your country does things differently -->
<city></city>
<region></region>
<code></code>
<country></country>
</postal>
<phone></phone>
<email>dward@cisco.com</email>
<!-- uri and facsimile elements may also be added -->
</address>
</author>
<author fullname="John Drake" initials="J.D." surname="Drake">
<organization>Juniper</organization>
<address>
<postal>
<street></street>
<!-- Reorder these if your country does things differently -->
<city></city>
<region></region>
<code></code>
<country></country>
</postal>
<phone></phone>
<email>jdrake@juniper.net</email>
<!-- uri and facsimile elements may also be added -->
</address>
</author>
<!-- If the month and year are both specified and are the current ones, xml2rfc will fill
in the current day for you. If only the current year is specified, xml2rfc will fill
in the current day and month for you. If the year is not the current one, it is
necessary to specify at least a month (xml2rfc assumes day="1" if not specified for the
purpose of calculating the expiry date). With drafts it is normally sufficient to
specify just the year. -->
<!-- Meta-data Declarations -->
<date day="21" month="February" year="2013" />
<area>Signaling</area>
<workgroup>MPLS Working Group</workgroup>
<keyword>LSP-PING</keyword>
<keyword>MPLS</keyword>
<keyword>MPLS-TP</keyword>
<abstract>
<t>This specification describes the configuration of pro-active MPLS-TP
Operations, Administration, and Maintenance (OAM) Functions for a given
LSP using a set of TLVs that are carried by the LSP-Ping protocol.</t>
<t>This document is a product of a joint Internet Engineering Task Force
(IETF) / International Telecommunication Union Telecommunication
Standardization Sector (ITU-T) effort to include an MPLS Transport Profile
within the IETF MPLS and PWE3 architectures to support the capabilities
and functionalities of a packet transport network.
</t>
</abstract>
</front>
<middle>
<section title="Introduction">
<t>This document describes the configuration of pro-active MPLS-TP
Operations, Administration, and Maintenance (OAM) Functions for a given
LSP using TLVs carried in LSP-Ping [RFC4379].
In particular it specifies the mechanisms necessary to establish MPLS-TP OAM
entities at the maintenance points for monitoring and performing measurements on an LSP, as well
as defining information elements and procedures to configure pro-active
MPLS-TP OAM functions running between LERs. Initialization and control of on-demand MPLS-TP OAM
functions are expected to be carried out by directly accessing network
nodes via a management interface; hence configuration and control of
on-demand OAM functions are out-of-scope for this document.</t>
<t>The Transport Profile of MPLS must, by definition [RFC5654], be
capable of operating without a control plane. Therefore there are
several options for configuring MPLS-TP OAM, without a control plane
by either using an NMS or LSP Ping, or with a control plane using signaling
protocols RSVP-TE and/or T-LDP.
</t>
<t>Pro-active MPLS-TP OAM is performed by four different protocols,
Bi-directional Forwarding Detection (BFD) [RFC6428] for Continuity
Check/Connectivity Verification, the delay measurement protocol (DM)
[RFC6374] for delay and delay variation (jitter) measurements, and the
loss measurement protocol (LM) [RFC6374] for packet loss and throughput
measurements. Additionally there is a number of Fault Management Signals
that can be configured.
</t>
<t>BFD is a protocol that provides low-overhead, fast detection of
failures in the path between two forwarding engines, including the
interfaces, data link(s), and to the extent possible the forwarding
engines themselves. BFD can be used to monitor the liveliness and detect
data plane failures of MPLS-TP point-to-point and might also be
extended to support point-to-multipoint connections.
</t>
<t>The delay and loss measurements protocols [RFC6374] use a simple
query/response model for performing bidirectional measurements that allows
the originating node to measure packet loss and delay in both
directions. By timestamping and/or writing current packet counters to the
measurement packets at four times (Tx and Rx in both directions) current
delays and packet losses can be calculated. By performing successive delay
measurements the delay variation (jitter) can be calculated. Current
throughput can be calculated from the packet loss measurements by dividing
the number of packets sent/received with the time it took to perform the
measurement, given by the timestamp in LM header. Combined with a packet
generator the throughput measurement can be used to measure the maximum
capacity of a particular LSP. It should be noted that here we are not
configuring on-demand throughput estimates based on saturating the
connection as defined in [RFC6371]. Rather, we only enable the estimation
of the current throughput based on loss measurements.
</t>
<t>MPLS Transport Profile (MPLS-TP) describes a profile of MPLS that
enables operational models typical in transport networks, while providing
additional OAM, survivability and other maintenance functions not
currently supported by MPLS. [RFC5860] defines the requirements for the
OAM functionality of MPLS-TP.</t>
<t>This document is a product of a joint Internet Engineering Task Force
(IETF) / International Telecommunication Union Telecommunication
Standardization Sector (ITU-T) effort to include an MPLS Transport Profile
within the IETF MPLS and PWE3 architectures to support the capabilities
and functionalities of a packet transport network.
</t>
<section title="Contributing Authors">
<t>This document is the result of a large team of authors and
contributors. The following is a list of the co-authors:</t>
<t>
<list>
<t>Gregory Mirsky</t>
</list>
</t>
</section>
<section title ="Requirements Language">
<t>
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described
in <xref target="RFC2119">RFC 2119</xref>.
</t>
</section>
</section>
<!--
<section title="Overview of MPLS OAM for Transport Applications">
<t>[RFC6371] describes how MPLS-TP OAM mechanisms are operated to
meet transport requirements outlined in [RFC5860].</t>
<t>[RFC6428] specifies two BFD operation modes: 1) "CC mode", which uses
periodic BFD message exchanges with symmetric timer settings, supporting
Continuity Check, 2) "CV/CC mode" which sends unique maintenance entity
identifiers in the periodic BFD messages supporting Connectivity
Verification as well as Continuity Check.</t>
<t>[RFC6374] specifies mechanisms for performance monitoring of LSPs, in
particular it specifies loss and delay measurement OAM functions.</t>
<t>[RFC6427] specifies fault management signals with which a server LSP
can notify client LSPs about various fault conditions to suppress alarms
or to be used as triggers for actions in the client LSPs. The following
signals are defined: Alarm Indication Signal (AIS), Link Down Indication
(LDI) and Lock Report (LKR). </t>
<t>[RFC6371] describes the mapping of fault conditions to
consequent actions. Some of these mappings may be configured by the
operator, depending on the application of the LSP. The following defects
are identified: Loss Of Continuity (LOC), Misconnectivity, MEP
Misconfiguration and Period Misconfiguration. Out of these defect
conditions, the following consequent actions may be configurable: 1)
whether or not the LOC defect should result in blocking the outgoing data
traffic; 2) whether or not the "Period Misconfiguration defect" should
result in a signal fail condition.</t>
</section>
-->
<section title="Theory of Operations">
<section title="MPLS OAM Configuration Operation Overview">
<t>The MPLS-TP OAM tool set are described in [RFC6669]. </t>
<t>LSP Ping, or alternatively RSVP-TE [RSVP-TE-CONF], can be used to
simply enable the different OAM functions, by setting the corresponding
flags in the "OAM Functions TLV". For a more detailed configuration one
may include sub-TLVs for the different OAM functions in order to specify
various parameters in detail.</t>
<t>Typically intermediate nodes should not process or modify any of the OAM
configuration TLVs but simply forward them to the end-node.
There is one exception to this and that is if the "MPLS OAM FMS sub-TLV"
is present. This sub-TLV has to be examined even by intermediate nodes. The sub-TLV MAY
be present if a flag is set in the "OAM Functions TLV".</t>
<section title="Configuration of BFD sessions">
<t> For this specification, BFD MUST be run in either one of the two modes:</t>
<t>
<list>
<t>- Asynchronous mode, where both sides should be in active mode</t>
<t>- Unidirectional mode</t>
</list>
</t>
<t>In the simplest scenario LSP Ping, or alternatively RSVP-TE [RSVP-TE CONF],
is used only to bootstrap a BFD session for an LSP, without any timer negotiation.</t>
<t>Timer negotiation can be performed either in subsequent BFD control
messages (in this case the operation is similar to LSP Ping based bootstrapping
described in [RFC5884]) or directly in the LSP-Ping configuration messages.</t>
<t>When BFD Control packets are transported in the G-ACh they are not
protected by any end-to-end checksum, only lower-layers are providing
error detection/correction. A single bit error, e.g. a flipped bit in
the BFD State field could cause the receiving end to wrongly conclude
that the link is down and in turn trigger protection switching. To
prevent this from happening the "BFD Configuration sub-TLV" has an
Integrity flag that when set enables BFD Authentication using Keyed SHA1
with an empty key (all 0s) [RFC5880]. This would make every BFD Control
packet carry an SHA1 hash of itself that can be used to detect
errors.</t>
<t>If BFD Authentication using a pre-shared key / password is desired
(i.e. authentication and not only error detection) the "BFD
Authentication sub-TLV" MUST be included in the "BFD Configuration
sub-TLV". The "BFD Authentication sub-TLV" is used to specify which
authentication method that should be used and which pre-shared key /
password that should be used for this particular session. How the key
exchange is performed is out of scope of this document.</t>
</section>
<section title="Configuration of Performance Monitoring">
<t>It is possible to configure Performance Monitoring functionalities such as Loss,
Delay, Delay variation (jitter), and Throughput as described in [RFC6374].</t>
<t>When configuring Performance monitoring functionalities it is
possible to choose either the default configuration, by only setting the
respective flags in the "OAM functions TLV", or a customized
configuration. To customize the configuration one would set the
respective flags in the including the respective Loss and/or Delay
sub-TLVs). </t>
<t>By setting the PM Loss flag in the "OAM Functions TLV" and including the
"MPLS OAM PM Loss sub-TLV" one can configure the measurement interval
and loss threshold values for triggering protection.</t>
<t>Delay measurements are configured by setting PM Delay flag in the "OAM
Functions TLV" and including the "MPLS OAM PM Loss sub-TLV" one can
configure the measurement interval and the delay threshold values for
triggering protection.</t>
</section>
<section title="Configuration of Fault Management Signals">
<t>To configure Fault Monitoring Signals and their refresh time the
FMS flag in the "OAM Functions TLV" MUST be set and the "MPLS OAM FMS
sub-TLV" included. When configuring Fault Monitoring Signals it can be
chosen either the default configuration (by only setting the
respective flags in the "OAM functions TLV") or a customized
configuration (by including the "MPLS OAM FMS sub-TLV"). </t>
<t>If an intermediate point is meant to originate fault management
signal messages this means that such an intermediate point is
associated to a server MEP through a co-located MPLS-TP client/server
adaptation function. Such a server MEP needs to be configured by its
own LSP-ping session (or, alternatively, via an NMS or
RSVP-TE). However, by setting the "Fault Management subscription"
flag in the "MPLS OAM FMS sub-TLV" a client LSP can indicate that it
would like an association to be created to the server MEP(s) on any
intermediate nodes.</t>
</section>
</section>
<section title="OAM Functions TLV">
<t>The "OAM Functions TLV" depicted below is carried as a TLV of the LSP
Echo request/response messages.</t>
<t>
<figure>
<artwork><![CDATA[
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| OAM Func. Type (16) (IANA) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|C|V|L|D|F| OAM Function Flags |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
~ sub-TLVs ~
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
]]></artwork>
</figure>
</t>
<t>The "OAM Functions TLV" contains a number of flags indicating which OAM functions should be activated as well as OAM function specific sub-TLVs with configuration parameters for the particular function.</t>
<t>Type: indicates a new type, the "OAM Functions TLV" (IANA to define,
suggested value 16).</t>
<t>Length: the length of the OAM Function Flags field including the
total length of the sub-TLVs in octets.</t>
<t>OAM Function Flags: a bitmap numbered from left to right as shown in
the figure.</t>
<t>These flags are defined in this document:</t>
<t>
<figure>
<artwork><![CDATA[
OAM Function Flag bit# Description
--------------------- ---------------------------
0 (C) Continuity Check (CC)
1 (V) Connectivity Verification (CV)
2 (F) Fault Management Signals (FMS)
3 (L) Performance Monitoring/Loss (PM/Loss)
4 (D) Performance Monitoring/Delay (PM/Delay)
5 (T) Throughput Measurement
6-31 Reserved (set all to 0s)
]]></artwork>
</figure>
</t>
<t>Sub-TLVs corresponding to the different flags are as follows:</t>
<t><list>
<t>- "BFD Configuration sub-TLV", which MUST be included if the CC and/or the CV
OAM Function flag is set. This sub-TLV MUST carry a "BFD Local
Discriminator sub-TLV" and a "Timer Negotiation Parameters sub-TLV"
if the N flag is cleared. The "MPLS OAM Source MEP-ID sub-TLV" MUST also be
included. If the I flag is set, the "BFD Authentication sub-TLV" may be included.</t>
<t>- "MPLS OAM PM Loss sub-TLV" within the "Performance Monitoring sub-TLV", which MAY be included if the
PM/Loss OAM Function flag is set. If the "MPLS OAM PM Loss sub-TLV"
is not included, default configuration values are used. Such sub-TLV MAY also be
included in case the Throughput function flag is set and there is the need to specify measurement interval different from
the default ones. In fact the throughput measurement make use of the same tool as the loss measurement,
hence the same TLV is used.</t>
<t>- "MPLS OAM PM Delay sub-TLV" within the "Performance Monitoring sub-TLV", which MAY be included if the
PM/Delay OAM Function flag is set. If the "MPLS OAM PM Delay
sub-TLV" is not included, default configuration values are used.</t>
<t>- "MPLS OAM FMS sub-TLV", which MAY be included if the FMS OAM
Function flag is set. If the "MPLS OAM FMS sub-TLV" is not included,
default configuration values are used.</t>
</list></t>
<section title="BFD Configuration sub-TLV">
<t>The "BFD Configuration sub-TLV" (depicted below) is defined for BFD
OAM specific configuration parameters. The "BFD Configuration
sub-TLV" is carried as a sub-TLV of the "OAM Functions TLV".</t>
<t>This TLV accommodates generic BFD OAM information and carries
sub-TLVs.</t>
<t>
<figure>
<artwork><![CDATA[
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| BFD Conf. Type (1) (IANA) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Vers.| PHB |N|S|I|G|U|B| Reserved (set to all 0s) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
~ sub-TLVs ~
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
]]></artwork>
</figure>
</t>
<t>Type: indicates a new type, the "BFD Configuration sub-TLV" (IANA
to define, suggested value 1).</t>
<t>Length: indicates the length of the TLV including sub-TLVs but
excluding the Type and Length field, in octets.</t>
<t>Version: identifies the BFD protocol version. If a node does not
support a specific BFD version an error must be generated: "OAM
Problem/Unsupported OAM Version".</t>
<t>PHB: Identifies the Per-Hop Behavior (PHB) to be used for periodic
continuity monitoring messages.</t>
<t>BFD Negotiation (N): If set timer negotiation/re-negotiation via
BFD Control Messages is enabled, when cleared it is disabled.</t>
<t>Symmetric session (S): If set the BFD session MUST use symmetric
timing values. </t>
<t>Integrity (I): If set BFD Authentication MUST be enabled. If the "BFD
Configuration sub-TLV" does not include a "BFD Authentication sub-TLV" the
authentication MUST use Keyed SHA1 with an empty pre-shared key (all 0s). </t>
<t>Encapsulation Capability (G): if set,
it shows the capability of encapsulating BFD messages into G-Ach channel.
If both the G bit and U bit are set, configuration gives precedence to the G bit.</t>
<t>Encapsulation Capability (U): if set,
it shows the capability of encapsulating BFD messages into UDP packets.
If both the G bit and U bit are set, configuration gives precedence to the G bit.</t>
<t>Bidirectional (B): if set, it configures BFD in the Bidirectional mode.
If it is not set it configures BFD in unidirectional mode. In the second case,
the source node does not expect any Discriminator values back from the destination node.</t>
<t>Reserved: Reserved for future specification and set to 0 on transmission and ignored when received.</t>
<t>The "BFD Configuration sub-TLV" MUST include the following sub-TLVs
in the LSP Echo request message:</t>
<t><list>
<t>- "Local Discriminator sub-TLV";</t>
<t>- "Negotiation Timer Parameters sub-TLV" if the N flag is
cleared.</t>
</list></t>
<t>The "BFD Configuration sub-TLV" MUST include the following sub-TLVs
in the LSP Echo reply message:</t>
<t><list>
<t>- "Local Discriminator sub-TLV;"</t>
<t>- "Negotiation Timer Parameters sub-TLV" if:
<list>
<t>- the N and S flags are cleared, or if: </t>
<t>- the N flag is cleared and the S flag is set, and the Negotiation Timer Parameters sub-TLV received by the egress contains unsupported values.
In this case an updated Negotiation Timer Parameters sub-TLV, containing values supported by the egress node, is returned to the ingress.</t>
</list>
</t>
</list></t>
<section title="Local Discriminator sub-TLV">
<t>The "Local Discriminator sub-TLV" is carried as a sub-TLV of the
"BFD Configuration sub-TLV" and is depicted below.</t>
<t>
<figure>
<artwork><![CDATA[
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Lcl. Discr. Type (1) (IANA) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Local Discriminator |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
]]></artwork>
</figure>
</t>
<t>Type: indicates a new type, the "Local Discriminator sub-TLV"
(IANA to define, suggested value 1).</t>
<t>Length: indicates the TLV length in octets, excluding the Type and Length field. (4)</t>
<t>Local Discriminator: A unique, nonzero discriminator value
generated by the transmitting system and referring to itself, used
to demultiplex multiple BFD sessions between the same pair of
systems.</t>
</section>
<section title="Negotiation Timer Parameters sub-TLV">
<t>The "Negotiation Timer Parameters sub-TLV" is carried as a
sub-TLV of the "BFD Configuration sub-TLV" and is depicted
below.</t>
<t>
<figure>
<artwork><![CDATA[
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Nego. Timer Type (2) (IANA) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Acceptable Min. Asynchronous TX interval |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Acceptable Min. Asynchronous RX interval |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Required Echo TX Interval |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
]]></artwork>
</figure>
</t>
<t>Type: indicates a new type, the "Negotiation Timer Parameters sub-TLV" (IANA to define, suggested value 2).</t>
<t>Length: indicates the length of the parameters in octets
(12).</t>
<t>Acceptable Min. Asynchronous TX interval: in case of S (symmetric)
flag set in the "BFD Configuration sub-TLV", it expresses the desired time
interval (in microseconds) at which the ingress LER
intends to both transmit and receive BFD periodic control packets. If
the receiving edge LSR can not support such value, it SHOULD
reply with an interval greater than the one proposed.</t>
<t>In case of S (symmetric) flag cleared in the "BFD Configuration
sub-TLV", this field expresses the desired time interval (in
microseconds) at which a edge LSR intends to transmit BFD periodic
control packets in its transmitting direction.</t>
<t>Acceptable Min. Asynchronous RX interval: in case of S (symmetric)
flag set in the "BFD Configuration sub-TLV", this field MUST be equal to
"Acceptable Min. Asynchronous TX interval" and has no additional
meaning respect to the one described for "Acceptable Min. Asynchronous
TX interval".</t>
<t>In case of S (symmetric) flag cleared in the "BFD Configuration
sub-TLV", it expresses the minimum time interval (in microseconds) at
which edge LSRs can receive BFD periodic control packets. In case this
value is greater than the "Acceptable Min. Asynchronous TX interval"
received from the other edge LSR, such edge LSR MUST adopt the
interval expressed in this "Acceptable Min. Asynchronous RX
interval".</t>
<t>Required Echo TX Interval: the minimum interval (in microseconds)
between received BFD Echo packets that this system is capable of
supporting, less any jitter applied by the sender as described in
[RFC5880] sect. 6.8.9. This value is also an indication for the
receiving system of the minimum interval between transmitted BFD
Echo packets. If this value is zero, the transmitting system does
not support the receipt of BFD Echo packets. If the receiving
system can not support this value the "Unsupported BFD TX Echo rate interval" error MUST be generated.
By default the value is set to 0.</t>
</section>
<section title="BFD Authentication sub-TLV">
<t>The "BFD Authentication sub-TLV" is carried as a sub-TLV of the
"BFD Configuration sub-TLV" and is depicted below.</t>
<t>
<figure>
<artwork><![CDATA[
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| BFD Auth. Type (3) (IANA) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Auth Type | Auth Key ID | Reserved (0s) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
]]></artwork>
</figure>
</t>
<t>Type: indicates a new type, the "BFD Authentication sub-TLV" (IANA to define).</t>
<t>Length: indicates the TLV total length in octets, exluding the Type and Length fields. (4)</t>
<t>Auth Type: indicates which type of authentication to use. The
same values as are defined in section 4.1 of [RFC5880] are
used. </t>
<t>Auth Key ID: indicates which authentication key or password
(depending on Auth Type) should be used. How the key exchange is
performed is out of scope of this document.</t>
<t>Reserved: Reserved for future specification and set to 0 on transmission and ignored when received.</t>
</section>
</section>
<section title="MPLS OAM Source MEP-ID sub-TLV">
<t>The "MPLS OAM Source MEP-ID sub-TLV" depicted below is carried as
a sub-TLV of the "OAM Functions TLV".</t>
<t>Note that support of ITU IDs is out-of-scope.</t>
<t>
<figure>
<artwork><![CDATA[
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Source MEP-ID Type (4) (IANA) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Source Node ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tunnel ID | LSP ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
]]></artwork>
</figure>
</t>
<t>Type: indicates a new type, the "MPLS OAM Source MEP-ID sub-TLV"
(IANA to define, suggested value 3).</t>
<t>Length: indicates the length of the TLV in octets, excluding the Type and Length fields. (8)</t>
<t>Source Node ID: 32-bit node identifier as defined in
[RFC6370].</t>
<t>Tunnel ID: a 16-bit unsigned integer unique to the node as
defined in [RFC6370].</t>
<t>LSP ID: a 16-bit unsigned integer unique within the Tunnel_ID as
defined in [RFC6370].</t>
</section>
<section title="Performance Monitoring sub-TLV">
<t>If the "OAM functions TLV" has either the L (Loss), D (Delay) or T (Throughput)
flag set, the "Performance Monitoring sub-TLV" MUST be present.</t>
<t>The "Performance Monitoring sub-TLV" provides the configuration information mentioned in Section 7 of
[RFC6374]. It includes support for the configuration of quality thresholds and, as described in [RFC6374], "the
crossing of which will trigger warnings or alarms, and result reporting and exception notification will be
integrated into the system-wide network management and reporting framework."</t>
<t>In case the values need to be different than the default ones the "Performance Monitoring sub-TLV",
"MPLS OAM PM Loss sub-TLV" MAY include the following sub-TLVs:
<list>
<t>- "MPLS OAM PM Loss sub-TLV" if the L flag is set in the "OAM functions TLV";</t>
<t>- "MPLS OAM PM Delay sub-TLV" if the D flag is set in the "OAM functions TLV";</t>
</list>
</t>
<t>The "Performance Monitoring sub-TLV" depicted below is carried as a
sub-TLV of the "OAM Functions TLV".</t>
<t>
<figure>
<artwork><![CDATA[
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Perf Monitoring Type (2)(IANA)| Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|D|L|J|Y|K|C| Reserved (set to all 0s) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
~ sub-TLVs ~
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
]]></artwork>
</figure>
</t>
<t>Type: indicates a new type, the "Performance Monitoring sub-TLV"
(IANA to define, suggested value 2).</t>
<t> Length: indicates the TLV length in octets, exluding the Type and Length fields.</t>
<t>Configuration Flags, for the specific function description please refer to [RFC6374]:
<list>
<t>- D: Delay inferred/direct (0=INFERRED, 1=DIRECT)</t>
<t>- L: Loss inferred/direct (0=INFERRED, 1=DIRECT)</t>
<t>- J: Delay variation/jitter (1=ACTIVE, 0=NOT ACTIVE)</t>
<t>- Y: Dyadic (1=ACTIVE, 0=NOT ACTIVE)</t>
<t>- K: Loopback (1=ACTIVE, 0=NOT ACTIVE)</t>
<t>- C: Combined (1=ACTIVE, 0=NOT ACTIVE)</t>
</list>
</t>
<t>Reserved: Reserved for future specification and set to 0 on transmission and ignored when received.</t>
<section title="MPLS OAM PM Loss sub-TLV">
<t>The "MPLS OAM PM Loss sub-TLV" depicted below is carried as a
sub-TLV of the "Performance Monitoring sub-TLV".</t>
<t>
<figure>
<artwork><![CDATA[
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| PM Loss Type (1) (IANA) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| OTF |T|B| Reserved (set to all 0s) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Measurement Interval |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Test Interval |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Loss Threshold |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
]]></artwork>
</figure>
</t>
<t>Type: indicates a new type, the "MPLS OAM PM Loss sub-TLV" (IANA to
define, suggested value 1).</t>
<t>Length: indicates the length of the parameters in octets (16).</t>
<t>OTF: Origin Timestamp Format of the Origin Timestamp field described in [RFC6374].
By default it is set to IEEE 1588 version 1.</t>
<t>Configuration Flags, please refer to [RFC6374] for further details:
<list>
<t>- T: Traffic-class-specific measurement indicator. Set to 1 when
the measurement operation is scoped to packets of a particular
traffic class (DSCP value), and 0 otherwise. When set to 1, the
DS field of the message indicates the measured traffic class.
By default it is set to 1.</t>
<t>- B: Octet (byte) count. When set to 1, indicates that the Counter
1-4 fields represent octet counts. When set to 0, indicates that
the Counter 1-4 fields represent packet counts.
By default it is set to 0.</t>
</list>
</t>
<t>Reserved: Reserved for future specification and set to 0 on transmission and ignored when received.</t>
<t>Measurement Interval: the time interval (in milliseconds) at which
Loss Measurement query messages MUST be sent on both directions. If
the edge LSR receiving the Path message can not support such value, it
SHOULD reply with a higher interval. By default it is set to (100) as per [RFC6375].</t>
<t>Test Interval: test messages interval in milliseconds as described in [RFC6374].
By default it is set to (10) as per [RFC6375].</t>
<t>Loss Threshold: the threshold value of measured lost packets per measurement over which action(s)
SHOULD be triggered. </t>
</section>
<section title="MPLS OAM PM Delay sub-TLV">
<t>The "MPLS OAM PM Delay sub-TLV" depicted below is carried as a
sub-TLV of the "Performance Monitoring sub-TLV".</t>
<t>
<figure>
<artwork><![CDATA[
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| PM Delay Type (2) (IANA) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| OTF |T|B| Reserved (set to all 0s) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Measurement Interval |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Test Interval |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Delay Threshold |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
]]></artwork>
</figure>
</t>
<t>Type: indicates a new type, the "MPLS OAM PM Loss sub-TLV" (IANA to
define, suggested value 2).</t>
<t>Length: indicates the length of the parameters in octets (16).</t>
<t>OTF: Origin Timestamp Format of the Origin Timestamp field described in [RFC6374].
By default it is set to IEEE 1588 version 1.</t>
<t>Configuration Flags, please refer to [RFC6374] for further details:
<list>
<t>- T: Traffic-class-specific measurement indicator. Set to 1 when
the measurement operation is scoped to packets of a particular
traffic class (DSCP value), and 0 otherwise. When set to 1, the
DS field of the message indicates the measured traffic class.
By default it is set to 1.</t>
<t>- B: Octet (byte) count. When set to 1, indicates that the Counter
1-4 fields represent octet counts. When set to 0, indicates that
the Counter 1-4 fields represent packet counts.
By default it is set to 0.</t>
</list>
</t>
<t>Reserved: Reserved for future specification and set to 0 on transmission and ignored when received.</t>
<t>Measurement Interval: the time interval (in milliseconds) at which
Delay Measurement query messages MUST be sent on both directions. If
the edge LSR receiving the Path message can not support such value, it
can reply with a higher interval. By default it is set to (1000) as per [RFC6375].</t>
<t>Test Interval: test messages interval (in milliseconds) as described in [RFC6374].
By default it is set to (10) as per [RFC6375].</t>
<t>Delay Threshold: the threshold value of measured two-way delay (in milliseconds) over which action(s)
SHOULD be triggered. </t>
</section>
</section>
<section title="MPLS OAM FMS sub-TLV">
<t>The "MPLS OAM FMS sub-TLV" depicted below is carried as a sub-TLV of
the "OAM Configuration sub-TLV". When both working and protection paths
are configured, both LSPs SHOULD be configured with identical settings of
the E flag, T flag, and the refresh timer.</t>
<t>
<figure>
<artwork><![CDATA[
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| MPLS OAM FMS Type (3) (IANA) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|E|S|T| Reserved (set to all 0s)| Refresh Timer | PHB |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
]]></artwork>
</figure>
</t>
<t>Type: indicates a new type, the "MPLS OAM FMS sub-TLV" (IANA to
define, suggested value 3).</t>
<t>Length: indicates the length of the parameters in octets (4).</t>
<t>FMS Signal Flags are used to enable the FMS signals at end point MEPs and
the Server MEPs of the links over which the LSP is forwarded. In this
document only the S flag pertains to Server MEPs. </t>
<t>The following flags are defined:
<list>
<t>- E: Enable Alarm Indication Signal (AIS) and Lock Report (LKR) signalling
as described in [RFC6427]. Default value is 1 (enabled). </t>
<t>- S: Indicate to a server MEP that its should transmit AIS and LKR signals on
the client LSP. Default value is 0 (disabled).</t>
<t>- T: Set timer value, enabled the configuration of a specific timer value.
Default value is 0 (disabled).</t>
<t>- Remaining bits: Reserved for future specification and set to 0.</t>
</list>
</t>
<t>Refresh Timer: indicates the refresh timer of fault indication messages, in seconds. The value MUST be
between 1 to 20 seconds as specified for the Refresh Timer field in [RFC6427]. If the edge LSR receiving the
Path message can not support the value it SHOULD reply with a higher timer value. </t>
<t>PHB: identifies the per-hop behavior of packets with fault
management information. </t>
</section>
</section>
</section>
<section anchor="IANA" title="IANA Considerations">
<t>This document specifies the following new TLV types:
<list>
<t>- "OAM Functions" type: 16;</t>
</list></t>
<t>sub-TLV types to be carried in the "OAM Functions TLV":
<list>
<t>- "BFD Configuration" type: 1;</t>
<t>- "MPLS OAM Performance Monitoring" type: 2;</t>
<t>- "MPLS OAM FMS" type: 3;</t>
<t>- "MPLS OAM Source MEP-ID" type: 4. </t>
</list>
</t>
<t>sub-TLV types to be carried in the "BFD Configuration sub-TLV":
<list>
<t>- "Local Discriminator" type: 1;</t>
<t>- "Negotiation Timer Parameters" type: 2;</t>
<t>- "BFD Authentication" sub-TLV type: 3. </t>
</list>
</t>
<t>sub-TLV types to be carried in the "Performance monitoring sub-TLV":
<list>
<t>- "MPLS OAM PM Loss" type: 1;</t>
<t>- "MPLS OAM PM Delay" type: 2;</t>
</list>
</t>
<!-- </section>
<section title="OAM configuration errors">
-->
<!-- We probably need more error codes here -->
<t>This document specifies additional Return Codes to LSP Ping:</t>
<t><list>
<t>- "MPLS OAM Unsupported Functionality";</t>
<t>- "OAM Problem/Unsupported TX rate interval";</t>
<t>- "OAM Problem/Unsupported RX rate interval";</t>
<t>- "OAM Problem/Unsupported unsupported Authentication Type";</t>
<t>- "OAM Problem, mismatch of Authentication Key ID ".</t>
</list>
</t>
</section>
<section anchor="Security" title="Security Considerations">
<t>The signaling of OAM related parameters and the automatic establishment
of OAM entities introduces additional security considerations to those
discussed in [RFC3473]. In particular, a network element could be
overloaded if an attacker were to request high frequency liveliness
monitoring of a large number of LSPs, targeting a single network element.</t>
<!--
<t>Security aspects will be covered in more detailed in subsequent
versions of this document.</t>
-->
</section>
</middle>
<back>
<references title="Normative References">
<?rfc include="reference.RFC.2119"?>
<?rfc include="reference.RFC.3473"?>
<?rfc include="reference.RFC.5654"?>
<?rfc include="reference.RFC.5860"?>
<?rfc include="reference.RFC.5880"?>
<?rfc include="reference.RFC.5884"?>
<?rfc include="reference.RFC.6370"?>
<?rfc include="reference.RFC.6374"?>
<?rfc include="reference.RFC.6427"?>
<?rfc include="reference.RFC.6428"?>
</references>
<references title="Informative References">
<?rfc include="reference.RFC.4379"?>
<?rfc include="reference.RFC.6371"?>
<?rfc include="reference.RFC.6375"?>
<?rfc include="reference.RFC.6669"?>
<reference anchor="RSVP-TE-CONF"
target="draft-ietf-ccamp-rsvp-te-mpls-tp-oam-ext">
<front>
<title>Configuration of pro-active MPLS-TP Operations, Administration, and Maintenance (OAM) Functions Using RSVP-TE</title>
<author initials="E" surname="Bellagamba">
<organization>Ericsson</organization>
</author>
<author initials="L" surname="Andersson">
<organization>Ericsson</organization>
</author>
<author initials="D" surname="Ward">
<organization>Cisco</organization>
</author>
<author initials="P" surname="Skoldstrom">
<organization>Acreo</organization>
</author>
<date year="2012" />
</front>
</reference>
</references>
</back>
</rfc>
| PAFTECH AB 2003-2026 | 2026-04-23 06:45:34 |