One document matched: draft-ietf-ccamp-rsvp-te-mpls-tp-oam-ext-00.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-ccamp-rsvp-te-mpls-tp-oam-ext-00"
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="RSVP-TE Ext for MPLS-TP OAM Config">RSVP-TE Extensions for
MPLS-TP OAM Configuration</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>Farogatan 6</street>
<!-- Reorder these if your country does things differently -->
<city>Kista</city>
<region></region>
<code>164 40</code>
<country>Sweden</country>
</postal>
<phone>+46 761440785</phone>
<email>elisa.bellagamba@ericsson.com</email>
<!-- uri and facsimile elements may also be added -->
</address>
</author>
<author fullname="Loa Andersson" initials="L.A." role="editor"
surname="Andersson">
<organization>Ericsson</organization>
<address>
<postal>
<street>Farogatan 6</street>
<!-- Reorder these if your country does things differently -->
<city>Kista</city>
<region></region>
<code>164 40</code>
<country>Sweden</country>
</postal>
<phone></phone>
<email>loa.andersson@ericsson.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>
<!-- 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="1" month="March" year="2010" />
<area>Signaling</area>
<workgroup>CCAMP Working Group</workgroup>
<keyword>RSVP-TE</keyword>
<keyword>GMPLS</keyword>
<keyword>MPLS</keyword>
<keyword>MPLS-TP</keyword>
<abstract>
<t>This specification is complementary to the GMPLS OAM Configuration
Framework [OAM-CONF-FWK] and describes technology specific aspects
for the configuration of pro-active MPLS Operations, Administration
and Maintenance (OAM) functions.</t>
</abstract>
</front>
<middle>
<section title="Introduction">
<t>This document defines the technology specific extensions of
RSVP-TE for the configuration of pro-active MPLS Operations,
Administration and
Maintenance (OAM) functions. In particular it specifies
extensions to establish MPLS OAM entities monitoring a signaled LSP,
and defines information elements and procedures to configure pro-active
MPLS OAM functions. Initialization and control of on-demand MPLS 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 of this document.</t>
<t>Pro-active MPLS OAM is based on the Bidirectional
Forwarding Detection (BFD) protocol [BFD]. Bidirectional Forwarding
Detection (BFD), as described in [BFD], defines a protocol that
provides low-overhead, short-duration 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 track the liveliness of MPLS-TP point-to-point and p2mp
connections and detect data plane failures.</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. [MPLS-TP-OAM-REQ] defines
the requirements by which the OAM functionality of MPLS-TP should abide.</t>
<t>BFD has been chosen to be the basis of pro-active MPLS-TP OAM functions.
MPLS OAM extensions for transport applications, which are relevant for
this document, are specified in [BFD-CCCV], [MPLS-PM] and [MPLS-FMS].</t>
<section title="Contributing Authors">
<t>The editors gratefully acknowledge the contributions of Attila Takacs and
Benoit Tremblay.</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 title="Overview of BFD OAM operation">
<t>BFD is a simple hello protocol that in many respects is similar to
the detection components of well-known routing protocols. A pair of systems transmits BFD packets periodically over each path between the
two systems, and if a system stops receiving BFD packets for long
enough, some component in that particular bidirectional path to the
neighboring system is assumed to have failed. Systems may also
negotiate to not send periodic BFD packets in order to reduce
overhead.</t>
<t>A path is only declared to be operational when two-way communication
has been established between systems, though this does not preclude
the use of unidirectional links to support bidirectional paths
(co-routed or bidirectional or associated bidirectional).</t>
<t>Each system estimates how quickly it can send and receive BFD packets
in order to come to an agreement with its neighbor about how rapidly
detection of failure will take place. These estimates can be
modified in real time in order to adapt to unusual situations. This
design also allows for fast systems on a shared medium with a slow
system to be able to more rapidly detect failures between the fast
systems while allowing the slow system to participate to the best of
its ability.</t>
<t>The ability of each system to control the BFD packet transmission
rate in both directions provides a mechanism for congestion control,
particularly when BFD is used across multiple network hops.</t>
<t>As recommended in [BFD-CCCV], the BFD tool needs to be extended for the
proactive CV functionality by the addition of an unique identifier in order to meet the requirements. The document in [BFD-CCCV] specifies the BFD
extension and behavior to meet the requirements for MPLS-TP proactive
Continuity Check and Connectivity Verification functionality and the
RDI functionality as defined in [MPLS-TP-OAM-REQ].</t>
</section>
</section>
<section title="Overview of MPLS OAM for Transport Applications">
<t>[MPLS-TP-OAM-FWK] describes how MPLS OAM mechanisms are operated
to meet transport requirements outlined in [MPLS-TP-OAM-REQ].</t>
<t>[BFD-CCCV] 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>[MPLS-PM] specifies mechanisms for performance monitoring of LSPs,
in particular it specifies loss and delay measurement OAM functions.</t>
<t>[MPLS-FMS] 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 Locked Report (LKR). To indicate client
faults associated with the attachment circuits Client Signal Failure
Indication (CSF) can be used. CSF is described in [MPLS-TP-OAM-FWK].</t>
<t>[MPLS-TP-OAM-FWK] 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 a signal fail condition.</t>
</section>
<section title="RSVP-TE Extensions">
<section title="MPLS OAM Configuration Operation Overview">
<t>RSVP-TE can be used to simply establish (i.e., bootstrap) a
BFD session or it can configure, at different level of details,
all pro-active MPLS OAM functions. When RSVP-TE is used to configure
BFD, BFD MUST be run in asynchronous mode and both sides should be
in active mode.</t>
<t>In the simplest scenario RSVP-TE signaling is used only to
bootstrap the BFD session. In this case in the Path message the
OAM Type in the "OAM Configuration TLV" is set to "MPLS
OAM". Only the "CC" OAM Function flag is set in the "OAM
Configuration TLV" and a "BFD Configuration sub-TLV" is
inserted in the "OAM Configuration TLV", carrying a "Local
Discriminator sub-TLV" with the discriminator value selected locally
for the BFD session of the signaled LSP. The N bit MUST be set to enable
timer negotiation/re-negotiation via BFD Control Messages. The receiving
node MUST use the Local Discriminator value received in the Path message
to identify the remote end of the BFD session, select a local
discriminator value and MUST start sending BFD Control Messages after
it sent the Resv message. The Resv message MUST include the
LSP_ATTRIBUTES Object reflecting back the contents of the "OAM
Configuration TLV", except that the "Local Discriminator
sub-TLV" MUST carry the discriminator value used by the sender
of the Resv message. Timer negotiation is left to subsequent BFD
control messages. This operation is similar to LSP Ping based
bootstrapping described in [BFD-MPLS].
</t>
<t>For detailed MPLS OAM configuration RSVP-TE can be used to
configure all parameters of pro-active MPLS OAM mechanisms.
If "CC mode" OAM is to be established, the OAM Type in the "OAM
Configuration TLV" is set to MPLS OAM, only the "CC" OAM Function
flag is set in the "OAM Configuration TLV" and the "BFD Configuration
TLV" is inserted in the "OAM Configuration TLV". The "Local
Discriminator sub-TLV" is used as described above.
Timer negotiation in this case is done via the RSVP-TE control
plane, hence the N bit MUST be cleared to disable timer
negotiation/re-negotiation via BFD Control Messages.
The "Timer Negotiation Parameters sub-TLV" MUST be present in the
"BFD configuration TLV" to specify the acceptable interval for the
BFD CC messages.</t>
<t>When timer negotiation is done via the RSVP-TE control plane,
two configuration options are available:
symmetric and asymmetric configuration. If symmetric configuration
is required, S flag in "BFD configuration TLV" MUST be set.
If the flag is cleared, the configuration is completed asymmetrically
in the two directions. Section 3.3.2 includes a detailed explanation
of such configuration.</t>
<t>In the case of the "CV/CC mode" OAM [BFD-CCCV],
the "CV" flag MUST be set in addition to the CC flag
in the "OAM Configuration TLV". The information required
to support this functionality is defined in [MPLS-TP-IDENTIF] and
can be found respectively in the SESSION and SENDER_TEMPLATE object
with no need of further sub-TLV as described in section 3.2.</t>
<t>Additional OAM functions can be requested by setting the
PM/Loss and PM/Delay OAM Function flags in the "OAM
Configuration TLV". If these flags are set, corresponding
sub-TLVs may be included in the "OAM Configuration TLV".</t>
<t>If Fault Management Signals [MPLS-FMS] are required, the
Fault Management Signals (FMS) OAM Function flag needs to be set
in the "OAM Configuration TLV". If this flag is set, an
additional "FMS sub-TLV" may be included in the OAM
Configuration TLV.</t>
</section>
<section title="OAM Configuration TLV">
<t>Below is specified the "OAM Configuration TLV", defined in [OAM-CONF-
FWK]. It specifies which OAM technology/method should be used for
the LSP. The "OAM Configuration TLV" is carried in the
LSP_ATTRIBUTES
object in Path 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type (2) (IANA) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| OAM Type | Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
~ sub-TLVs ~
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
]]></artwork>
</figure>
</t>
<t>Type: indicates the "OAM Configuration TLV" (2) (IANA to assign).</t>
<t>OAM Type: one octet that specifies the technology specific OAM Type.
If the requested OAM Type is not supported, an error must be
generated: "OAM Problem/Unsupported OAM Type".</t>
<t> This document defines a new OAM Type: "MPLS OAM" (suggested value 2,
IANA to assign) from the "RSVP-TE OAM Configuration Registry".
The "MPLS OAM" type is to be set in the "OAM Configuration TLV"
[OAM-CONF-FWK] to request the establishment of OAM entities for
MPLS LSPs.</t>
<t>The receiving LER when the MPLS-TP OAM Type is requested should
check which OAM Function Flags are set in the "Function
Flags TLV" and look for the corresponding technology specific
configuration TLV.</t>
<t>This document specifies the following sub-TLVs to be
carried in the "OAM Configuration TLV" for MPLS OAM
configuration.</t>
<t><list>
<t>- "BFD Configuration sub-TLV", which MUST be included if the
CC 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.</t>
<t>- "MPLS OAM PM Loss 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.</t>
<t>- "MPLS OAM PM Delay 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>
<t>Moreover, if the CV flag is set, the CC flag MUST be set at the
same time. The format of an MPLS-TP CV/CC message is shown in
[BFD-CCCV] and it requires, together with the BFD control packet
information, the "Unique MEP-ID of source of BFD packet".
[MPLS-TP-IDENTIF] defines the composition of such identifier as:</t>
<t><"Unique MEP-ID of source of BFD packet"> ::= <src_node_id><src_tunnel_num><lsp_num></t>
<!--
<t>
<figure>
<artwork><![CDATA[
<"Unique MEP-ID of source of BFD packet"> ::= <src_node_id><src_tunnel_num><lsp_num>
]]></artwork>
</figure>
</t>
-->
<t>GMPLS signaling [RFC 3473] uses a 5-tuple to uniquely identify an
LSP within an operator's network. This tuple is composed of a Tunnel
Endpoint Address, Tunnel_ID, Extended Tunnel ID, and Tunnel Sender
Address and (GMPLS) LSP_ID.</t>
<t>Hence, the following mapping is used without the need of redefining
a new TLV for MPLS-TP proactive CV purpose.</t>
<t>
<list>
<t>- Tunnel ID = src_tunnel_num</t>
<t>- Tunnel Sender Address = src_node_id</t>
<t>- LSP ID = LSP_Num</t>
</list>
</t>
<t>"Tunnel ID" and "Tunnel Sender Address" are included in
the "SESSION" object [RFC 3209], which is mandatory in both Path
and Resv messages.</t>
<t>"LSP ID" will be the same on both directions and it is
included in the "SENDER_TEMPLATE" object [RFC 3209] which
is mandatory in Path messages.</t>
<t>[Author's note: the same "Unique MEP-ID of source"
will be likely required for Performance monitoring purposes.
However for the moment in [MPLS-PM] it is stated: "The question
of ACH TLV usage and the manner of supporting metadata such as authentication
keys and node identifiers is deliberately omitted. These issues will be addressed
in a future version of the document."]</t>
</section>
<section title="BFD Configuration TLV">
<t>The "BFD Configuration TLV" (depicted below) is defined for BFD
OAM specific configuration parameters. The "BFD Configuration
TLV" is carried as a sub-TLV of the "OAM Configuration TLV" in the
LSP_ATTRIBUTES object both in Path and Resv messages.</t>
<t>This new 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type (3) (IANA) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Vers.| PHB |N|S| Reserved (set to all 0s) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
~ sub TLVs ~
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
]]></artwork>
</figure>
</t>
<t>Type: indicates a new type, the "BFD
Configuration TLV" (IANA to define).</t>
<t>Length: indicates the total length including sub-TLVs.</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 &rdquo".</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>The "BFD Configuration TLV" MUST include the following sub-TLVs
in the Path message:</t>
<t><list>
<t>- "Local Discriminator sub-TLV";</t>
<t>- "Negotiation Timer Parameters sub-TLV" if N flag is cleared.</t>
</list></t>
<t>The "BFD Configuration TLV" MUST include the following
sub-TLVs in the Resv message:</t>
<t><list>
<t>- "Local Discriminator sub-TLV;"</t>
<t>- "Negotiation Timer Parameters sub-TLV" if:
<list>
<t>- N flag and S are cleared </t>
<t>- N flag is cleared and S flag is set and a timing value
higher than the one received needs to be used</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 in both Path and Resv messages. It 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type (1) (IANA) | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Local Discriminator |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
]]></artwork>
</figure>
</t>
<t>Type: indicates a new type, the Local Discriminator sub TLV (1)
(IANA to define).</t>
<t>Length: indicates the TLV total length in octets.</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">
<t>The "Negotiation Timer Parameters sub-TLV" 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Req. TX int. Type (2) (IANA) | Length = 20 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Acceptable Min. Asynchronous TX interval |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Acceptable Min. Asynchronous RX interval |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Required Echo TX Interval |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Detect. Mult.| Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
]]></artwork>
</figure>
</t>
<t>Type: indicates a new type, the "Negotiation Timer Parameters
sub-TLV" (IANA to define).</t>
<t>Length: indicates the TLV total length in octets.</t>
<t>Acceptable Min. Asynchronous TX interval: in case of S
(symmetric) flag set in the "BFD Configuration" TLV,
it expresses the desired time interval (in microseconds) at
which the LER initiating the signaling intends to both transmit
and receive BFD periodic control packets. If the receiving LER can
not support such value, it is allowed to reply back with an interval
greater than the one proposed.</t>
<t>In case of S (symmetric) flag cleared in the "BFD
Configuration TLV", this field expresses the desired
time interval (in microseconds) at which a LER 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 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
TLV", it expresses the minimum time interval (in microseconds)
at which LERs can receive BFD periodic control packets. In case
this value is greater than the "Acceptable Min. Asynchronous TX
interval" received from the other LER, such LER 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
[BFD] 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 an error MUST be generated "Unsupported BFD TX
rate interval".</t>
<t>Detection time multiplier: The negotiated transmit interval,
multiplied by this value, provides the Detection Time for the
receiving system in Asynchronous mode.</t>
</section>
</section>
<section title="MPLS OAM PM Loss TLV">
<t></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 (3) (IANA) | Length = 16 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Vers.|E|C| | Reserved | PHB |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Measurement Interval |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Loss Threshold |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
]]></artwork>
</figure>
</t>
<t>Type: indicates a new type, the "PM Loss" (IANA to define).</t>
<t>Length: indicates the TLV total length in octets.</t>
<t>Version: indicates the Loss measurement protocol version.</t>
<t>Configuration Flags:
<list>
<t>- E: exclude from the Loss Measurement all G-ACh messages</t>
<t>- C: require the use of a counter in the "Querier Context"
field described in [MPLS-PM]</t>
<t>- Remaining bits: Reserved for future specification and set to 0.</t>
</list>
</t>
<t>PHB: identifies the per-hop behavior of packets with
loss information.</t>
<t>Measurement Interval: the time interval (in microseconds)
at which Loss Measurement query messages MUST be sent on both
directions. If the LER receiving the Path message can not support
such value, it can reply back with a higher interval.</t>
<t>Loss Threshold: the threshold value of lost packets over
which protections MUST be triggered.</t>
</section>
<section title="MPLS OAM PM Delay TLV">
<t>"PM Delay sub-TLV" 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| PM Delay Type (4) (IANA) | Length = 16 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Vers.| Flags | Reserved | PHB |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Measurement Interval |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Delay Threshold |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
]]></artwork>
</figure>
</t>
<t>Type: indicates a new type, the "PM Delay" (IANA to define).</t>
<t>Length: indicates the TLV total length in octets.</t>
<t>Version: indicates the Delay measurement protocol version.</t>
<t>Configuration Flags:
<list>
<t>- E: exclude from the Loss Measurement all G-ACh messages</t>
<t>- C: require the use of a counter in the "Querier Context" field
described in [MPLS-PM]</t>
<t>- Remaining bits: Reserved for future specification and set to 0.</t>
</list>
</t>
<t>PHB: - identifies the per-hop behavior of packets with delay
information.</t>
<t>Measurement Interval: the time interval (in microseconds)
at which Delay Measurement query messages MUST be sent on both
directions. If the LER receiving the Path message can not support
such value, it can reply back with a higher interval.</t>
<t>Delay Threshold: the threshold value of lost packets over which
protections MUST be triggered.</t>
<t>[Author's note: TBD if we want to include the timestamp
format negotiation as in [MPLS-PM] 4.2.5.]</t>
</section>
<section title="MPLS OAM FMS TLV">
<t></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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type (5) (IANA) | Length (12) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|A|D|L|C| Reserved | |E| PHB |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Refresh Timer |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
]]></artwork>
</figure>
</t>
<t>Type: indicates a new type, the "PM Delay" (IANA to define).</t>
<t>Length: indicates the TLV total length in octets.</t>
<t>Signal Flags: are used to enable the following signals:
<list>
<t>- A: Alarm Indication Signal (AIS) as described in [MPLS-FMS]</t>
<t>- D: Link Down Indication (LDI) as described in [MPLS-FMS]</t>
<t>- L: Locked Report (LKR) as described in [MPLS-FMS]</t>
<t>- C: Client Signal Failure (CSF) as described in [MPLS-CSF]</t>
</list>
</t>
<t>Configuration Flags:
<list>
<t>- E: used to enable/disable explicitly clearing faults</t>
<t>- PHB: identifies the per-hop behavior of packets with fault
management information</t>
</list>
</t>
<t>Refresh Timer: indicates the refresh timer (in microseconds)
of fault indication messages. If the LER receiving the Path message
can not support such value, it can reply back with a higher interval.</t>
</section>
</section>
<!-- Possibly a 'Contributors' section ... -->
<section anchor="IANA" title="IANA Considerations">
<t>This document specifies the following new TLV types:</t>
<t><list>
<t>- "BFD Configuration" type: 2;</t>
<t>- "MPLS OAM PM Loss" type: 3;</t>
<t>- "MPLS OAM PM Delay" type: 4;</t>
<t>- "MPLS OAM PM FMS" type: 5.</t>
</list> </t>
<t>sub-TLV types to be carried in the "BFD Configuration sub-TLV":
<list>
<t>- "Local Discriminator" sub-TLV type: 1;</t>
<t>- "Negotiation Timer Parameters" sub-TLV type: 2.</t>
</list>
</t>
</section>
<section title="BFD OAM configuration errors">
<t>In addition to error values specified in [OAM-CONF-FWK] and [ETH-OAM]
this document defines the following values for the "OAM Problem" Error Code:</t>
<t><list>
<t>- "MPLS OAM Unsupported Functionality";</t>
<t>- "OAM Problem/Unsupported TX rate interval".</t>
</list>
</t>
</section>
<section title="Acknowledgements">
<t>The authors would like to thank David Allan,
Lou Berger, Annamaria Fulignoli, Eric Gray, Andras Kern, David Jocha and David Sinicrope
for their useful comments.</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 would request
liveliness monitoring, with frequent periodic messages, for a high
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 MATTER ***** -->
<back>
<!-- References split into informative and normative -->
<!-- There are 2 ways to insert reference entries from the citation libraries:
1. define an ENTITY at the top, and use "ampersand character"RFC2629; here (as shown)
2. simply use a PI "less than character"?rfc include="reference.RFC.2119.xml"?> here
(for I-Ds: include="reference.I-D.narten-iana-considerations-rfc2434bis.xml")
Both are cited textually in the same manner: by using xref elements.
If you use the PI option, xml2rfc will, by default, try to find included files in the same
directory as the including file. You can also define the XML_LIBRARY environment variable
with a value containing a set of directories to search. These can be either in the local
filing system or remote ones accessed by http (http://domain/dir/... ).-->
<references title="Normative References">
<!--?rfc include="http://xml.resource.org/public/rfc/bibxml/reference.RFC.2119.xml"?-->
<?rfc include="reference.RFC.3471"?>
<?rfc include="reference.RFC.2119"?>
<?rfc include="reference.RFC.5586"?>
<reference anchor="MPLS-TP-OAM-REQ"
target="draft-ietf-mpls-tp-oam-requirements">
<!-- the following is the minimum to make xml2rfc happy -->
<front>
<title>Requirements for OAM in MPLS Transport Networks</title>
<author initials="M" surname="Vigoureux">
<organization></organization>
</author>
<author initials="D" surname="Ward">
<organization></organization>
</author>
<author initials="M" surname="Betts">
<organization></organization>
</author>
<date year="2009" />
</front>
</reference>
<reference anchor="BFD"
target="draft-ietf-bfd-base">
<!-- the following is the minimum to make xml2rfc happy -->
<front>
<title>Bidirectional Forwarding Detection</title>
<author initials="D" surname="Katz">
<organization></organization>
</author>
<author initials="D" surname="Ward">
<organization></organization>
</author>
<date year="2009" />
</front>
</reference>
<reference anchor="OAM-CONF-FWK"
target="draft-ietf-ccamp-oam-configuration-fwk">
<!-- the following is the minimum to make xml2rfc happy -->
<front>
<title>OAM Configuration Framework for GMPLS RSVP-TE</title>
<author initials="A" surname="Takacs">
<organization></organization>
</author>
<author initials="D" surname="Fedyk">
<organization></organization>
</author>
<author initials="J" surname="van He">
<organization></organization>
</author>
<date year="2009" />
</front>
</reference>
<reference anchor="MPLS-TP-IDENTIF"
target="draft-swallow-mpls-tp-identifiers">
<!-- the following is the minimum to make xml2rfc happy -->
<front>
<title>MPLS-TP Identifiers</title>
<author initials="M" surname="Bocci">
<organization></organization>
</author>
<author initials="G" surname="Swallow">
<organization></organization>
</author>
<date year="2009" />
</front>
</reference>
<reference anchor="MPLS-PM"
target="draft-frost-mpls-tp-loss-delay">
<!-- the following is the minimum to make xml2rfc happy -->
<front>
<title>Packet Loss and Delay Measurement for the
MPLS Transport Profile</title>
<author initials="S" surname="Bryant">
<organization></organization>
</author>
<author initials="D" surname="Frost">
<organization></organization>
</author>
<date year="2009" />
</front>
</reference>
<reference anchor="MPLS-FMS"
target="draft-sfv-mpls-tp-fault">
<!-- the following is the minimum to make xml2rfc happy -->
<front>
<title>MPLS Fault Management OAM</title>
<author initials="G" surname="Swallow">
<organization></organization>
</author>
<author initials="A" surname="Fulignoli">
<organization></organization>
</author>
<author initials="M" surname="Vigoureux">
<organization></organization>
</author>
<date year="2009" />
</front>
</reference>
<reference anchor="MPLS-CSF"
target="draft-he-mpls-tp-csf">
<!-- the following is the minimum to make xml2rfc happy -->
<front>
<title>Indication of Client Failure in MPLS-TP</title>
<author initials="J" surname="He">
<organization></organization>
</author>
<author initials="H" surname="Li">
<organization></organization>
</author>
<date year="2009" />
</front>
</reference>
</references>
<references title="Informative References">
<reference anchor="BFD-CCCV"
target="draft-asm-mpls-tp-bfd-cc-cv">
<!-- the following is the minimum to make xml2rfc happy -->
<front>
<title>MPLS-TP BFD for Proactive CC-CV and RDI</title>
<author initials="A" surname="Fulignoli">
<organization></organization>
</author>
<author initials="S" surname="Boutros">
<organization></organization>
</author>
<author initials="M" surname="Vigoreux">
<organization></organization>
</author>
<date year="2009" />
</front>
</reference>
<reference anchor="MPLS-TP-OAM-FWK"
target="draft-ietf-mpls-tp-oam-framework">
<!-- the following is the minimum to make xml2rfc happy -->
<front>
<title>MPLS-TP OAM Framework and Overview</title>
<author initials="I" surname="Busi">
<organization></organization>
</author>
<author initials="B" surname="Niven-Jenkins">
<organization></organization>
</author>
<date year="2009" />
</front>
</reference>
<reference anchor="MPLS-TP-FWK"
target="draft-ietf-mpls-tp-framework">
<!-- the following is the minimum to make xml2rfc happy -->
<front>
<title>OAM Configuration Framework for GMPLS RSVP-TE</title>
<author initials="M" surname="Bocci">
<organization></organization>
</author>
<author initials="S" surname="Bryant">
<organization></organization>
</author>
<author initials="D" surname="Frost">
<organization></organization>
</author>
<author initials="L" surname="Levrau">
<organization></organization>
</author>
<date year="2009" />
</front>
</reference>
<?rfc include="reference.RFC.4447"?>
<reference anchor="ETH-OAM"
target="draft-ietf-ccamp-rsvp-te-eth-oam-ext">
<!-- the following is the minimum to make xml2rfc happy -->
<front>
<title>GMPLS RSVP-TE Extensions for Ethernet OAM</title>
<author initials="A" surname="Takacs">
<organization></organization>
</author>
<author initials="B" surname="Gero">
<organization></organization>
</author>
<author initials="D" surname="Fedyk">
<organization></organization>
</author>
<author initials="D" surname="Mohan">
<organization></organization>
</author>
<author initials="D" surname="Long">
<organization></organization>
</author>
<date year="2009" />
</front>
</reference>
<reference anchor="MPLS-TP OAM Analysis"
target="draft-sprecher-mpls-tp-oam-analysis">
<!-- the following is the minimum to make xml2rfc happy -->
<front>
<title>MPLS-TP OAM Analysis</title>
<author initials="N" surname="Sprecher">
<organization></organization>
</author>
<author initials="T" surname="Nadeau">
<organization></organization>
</author>
<author initials="H" surname="van Helvoort">
<organization></organization>
</author>
<author initials="" surname="Weingarten">
<organization></organization>
</author>
<date year="2006" />
</front>
</reference>
<reference anchor="LSP Ping"
target="RFC 3479">
<!-- the following is the minimum to make xml2rfc happy -->
<front>
<title>Detecting Multi-Protocol Label Switched (MPLS) Data Plane Failures</title>
<author initials="K" surname="Kompella">
<organization></organization>
</author>
<author initials="G" surname="Swallow">
<organization></organization>
</author>
<date year="2006" />
</front>
</reference>
</references>
<section anchor="app-additional" title="Additional Stuff">
<t>This becomes an Appendix.</t>
</section>
</back>
</rfc>
| PAFTECH AB 2003-2026 | 2026-04-23 12:16:29 |