One document matched: draft-ietf-ccamp-rsvp-te-mpls-tp-oam-ext-07.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-07"
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
RSVP-TE</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." role="editor"
surname="Andersson">
<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>
<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>
<author fullname="Dave Ward" initials="D.W." role=""
surname="Ward">
<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>dward@juniper.net</email>
<!-- uri and facsimile elements may also be added -->
</address>
</author>
<author fullname="Attila Takacs" initials="A.T." role=""
surname="Takacs">
<organization>Ericsson</organization>
<address>
<postal>
<street>1. Laborc u.
</street>
<!-- Reorder these if your country does things differently -->
<city>Budapest</city>
<region></region>
<code></code>
<country>HUNGARY</country>
</postal>
<phone></phone>
<email>attila.takacs@ericsson.com</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="31" month="October" year="2011" />
<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 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 RSVP-TE 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 by RSVP-TE [RFC3209].
In particular it specifies the mechanisms necessary to establish MPLS-TP OAM
entities at and points for monitoring and performing measurements on an LSP, as well
as defining information elements and procedures to configure pro-active
MPLS OAM functions runnineg between LERs. 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 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
three options for configuring MPLS-TP OAM, without a control plane
by either using an NMS or LSP Ping, or with a control plane using GMPLS
(specifically RSVP-TE) .</t>
<t>
<!-- What should and shouldn't be capitilized here? -->
Pro-active MPLS OAM is performed by three different protocols,
Bidirectional Forwarding Detection (BFD) [RFC5880] 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 track 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.
</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>John Drake</t>
<t>Benoit Tremblay</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>[MPLS-TP-OAM-FWK] describes how MPLS OAM mechanisms are operated to
meet transport requirements outlined in [RFC5860].</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>[RFC6374] 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] and in the context of this
document is for further study.</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 in a signal fail condition.</t>
</section>
<section title="Theory of Operations">
<section title="MPLS OAM Configuration Operation Overview">
<t>RSVP-TE, or alternatively LSP Ping [LSP-PING CONF], can be used to
simply enable the different OAM functions, by setting the corresponding
flags in the "OAM Functions TLV". Additionally one may include
sub-TLVs for the different OAM functions in order to specify different
parameters in detail. </t>
<t>The presence of OAM configuration TLVs at intermediate nodes is
justified because the mid-points need to forward the RSVP-TE message
to the end point. No TLV processing or modification or following OAM
actions need to be taken at the intermediate points. </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 and Throughput as described in [RFC6374].</t>
<t>When configuring Performance monitoring functionalities 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 respective Loss and/or Delay sub-TLVs).</t>
</section>
<section title="Configuration of Fault Management Signals">
<t>Additional OAM functions may be configured by setting the appropriate
flags in the "OAM Functions TLV", these include Performance
Measurements (packet loss, throughput, delay, and delay variation) and
Fault Management Signal handling.</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>
<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. If an intermediate point is meant to originate fault
management signal messages this mean that such intermediate point is
associated to a server MEP through a co-located MPLS-TP client/server
adaptation function and such server MEP needs to be configured by its
own RSVP-TE session (or, in alternative, NMS or LSP ping).</t>
<!-- TODO Add more description about loss, delay, and especially FMS -->
</section>
</section>
<section title="OAM Configuration TLV">
<t>The "OAM Configuration TLV" is depicted in the following figure. It
specifies the OAM functions that are to be used for the LSP and
it is defined in [OAM-CONF-FWK]. The "OAM Configuration
TLV" is carried in the LSP_ATTRIBUTES object in Path and Resv
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 set to request the establishment of OAM functions for
MPLS-TP LSPs. The specific OAM functions are specified in the "Function
Flags" sub-TLV as depicted in [OAM-CONF-FWK].</t>
<t>The receiving edge LSR when the MPLS-TP OAM Type is requested should
check which OAM Function Flags are set in the "Function Flags TLV" (also defined in [OAM-CONF-FWK]) and
look for the corresponding technology specific configuration TLVs.</t>
<t>Additional corresponding sub-TLVs 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. 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>
<!-- TODO check this wuith Cc & CV -->
<t>Moreover, if the CV or CC 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 [RFC3473] 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 [RFC3209], 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 [RFC3209] 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. This need to be agreed with
[RFC6374] authors.]</t>
</section>
<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 Configuration 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type (3) (IANA) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Vers.| PHB |N|S|I| Reserved (set to all 0s) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
~ sub-TLVs ~
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
]]></artwork>
</figure>
</t>
<t>Type: indicates a new type, the "BFD Configuration sub-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".</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>The "BFD Configuration sub-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 the N flag is
cleared.</t>
</list></t>
<t>The "BFD Configuration sub-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>- the N and S flags are cleared </t>
<t>- the N flag is cleared and the S flag is set and a timing
interval larger than the one received needs to be used</t>
</list>
</t>
</list></t>
<t>Reserved: Reserved for future specification and set to 0.</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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 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 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Timer Neg. Type (2) (IANA) | Length = 20 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 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).</t>
<t>Length: indicates the TLV total length in octets. (20)</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 can
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 an error MUST be generated "Unsupported BFD TX
rate interval".</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 = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 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. (8)</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. </t>
</section>
</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>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 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 (IANA)| Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|D|L|J|Y|K|C| Reserved (set to all 0s) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
~ sub-TLVs ~
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
]]></artwork>
</figure>
</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>
<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 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 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 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 (12).</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>Measurement Interval: the time interval (in microseconds) 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
can reply back with a higher interval. By default it is set to (TBD).</t>
<t>Test Interval: test messages interval as described in [RFC6374].
By default it is set to (TBD).</t>
<t>Loss Threshold: the threshold value of lost packets over which
protections MUST be triggered. By default it is set to (TBD).</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 "OAM Functions TLV".</t>
<t>
<figure>
<artwork><![CDATA[
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 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 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 1).</t>
<t>Length: indicates the length of the parameters in octets (12).</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>Measurement Interval: the time interval (in microseconds) 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 back with a higher interval. By default it is set to (TBD).</t>
<t>Test Interval: test messages interval as described in [RFC6374].
By default it is set to (TBD).</t>
<t>Delay Threshold: the threshold value of measured delay (in
microseconds) over which protections MUST be triggered. By default it is set to (TBD).</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".</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 (set all to 0s) | PHB |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Refresh Timer |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
]]></artwork>
</figure>
</t>
<t>Type: indicates a new type, the "MPLS OAM FMS sub-TLV" (IANA to define).</t>
<t>Length: indicates the TLV total length in octets.</t>
<t>Signal Flags should not be processed at intermediate nodes as they only have an end-point significance.
They are used to enable the following signals at end points:
<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>
<t>- Remaining bits: Reserved for future specification and set to
0.</t>
</list>
</t>
<t>Configuration Flags:
<list>
<t>- PHB: identifies the per-hop behavior of packets with fault
management information. It is significant only when C flag is set.</t>
</list>
</t>
<t>Refresh Timer: indicates the refresh timer (in microseconds) of
fault indication messages. If the edge LSR 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 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>
<t>- "BFD Authentication" sub-TLV type: 3.</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 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 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"?>
<?rfc include="reference.RFC.5654"?>
<?rfc include="reference.RFC.5880"?>
<?rfc include="reference.RFC.3209"?>
<?rfc include="reference.RFC.3473"?>
<?rfc include="reference.RFC.5884"?>
<?rfc include="reference.RFC.5860"?>
<?rfc include="reference.RFC.6374"?>
<?rfc include="reference.RFC.6375"?>
<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-ietf-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>
<author initials="E" surname="Gray">
<organization></organization>
</author>
<date year="2010" />
</front>
</reference>
<reference anchor="MPLS-FMS"
target="draft-ietf-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>
<author initials="S" surname="Boutros">
<organization></organization>
</author>
<author initials="D" surname="Ward">
<organization></organization>
</author>
<date year="2009" />
</front>
</reference>
</references>
<references title="Informative References">
<reference anchor="LSP-PING CONF"
target="draft-ietf-mpls-lsp-ping-mpls-tp-oam-conf">
<!-- the following is the minimum to make xml2rfc happy -->
<front>
<title>Configuration of pro-active MPLS-TP Operations, Administration, and Maintenance (OAM) Functions Using LSP Ping</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="2010" />
</front>
</reference>
<reference anchor="BFD-CCCV"
target="draft-ietf-mpls-tp-bfd-cc-cv-rdi">
<!-- the following is the minimum to make xml2rfc happy -->
<front>
<title>Proactive Connectivity Verification, Continuity Check and Remote Defect indication for MPLS Transport Profile</title>
<author initials="D" surname="Allan">
<organization></organization>
</author>
<author initials="G" surname="Swallow">
<organization></organization>
</author>
<author initials="J" surname="Drake">
<organization></organization>
</author>
<date year="2010" />
</front>
</reference>
<reference anchor="BFD-Ping"
target="draft-ietf-mpls-tp-lsp-ping-bfd-procedures-02">
<!-- the following is the minimum to make xml2rfc happy -->
<front>
<title>LSP Ping and BFD encapsulation over ACH</title>
<author initials="N" surname="Bahadur">
<organization></organization>
</author>
<author initials="R" surname="Aggarwal">
<organization></organization>
</author>
<author initials="D" surname="Ward">
<organization></organization>
</author>
<author initials="T" surname="Nadeau">
<organization></organization>
</author>
<author initials="N" surname="Sprecher">
<organization></organization>
</author>
<author initials="Y" surname="Weingarten">
<organization></organization>
</author>
<date year="2010" />
</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>Operations, Administration and Maintenance Framework for MPLS-based Transport Networks</title>
<author initials="M" surname="Bocci">
<organization></organization>
</author>
<author initials="D" surname="Allan">
<organization></organization>
</author>
<date year="2010" />
</front>
</reference>
<?rfc include="reference.RFC.4447"?>
<?rfc include="reference.RFC.5921"?>
<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-ietf-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="Y" surname="Weingarten">
<organization></organization>
</author>
<author initials="E" surname="Bellagamba">
<organization></organization>
</author>
<date year="2011" />
</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:11:08 |