One document matched: draft-ietf-mpls-tp-ach-tlv-02.xml
<?xml version="1.0" encoding="US-ASCII"?>
<!DOCTYPE rfc SYSTEM "rfc2629.dtd">
<?rfc toc="yes"?>
<?rfc tocompact="yes"?>
<?rfc symrefs="no"?>
<?rfc sortrefs="yes"?>
<?rfc compact="yes"?>
<?rfc subcompact="no"?>
<?rfc toc="yes"?>
<rfc category="std" docName="draft-ietf-mpls-tp-ach-tlv-02" ipr="trust200902">
<front>
<title abbrev="ACH TLV">Definition of ACH TLV Structure</title>
<author fullname="Sami Boutros" initials="S" surname="Boutros">
<organization>Cisco Systems</organization>
<address>
<postal>
<street></street>
</postal>
<email>sboutros@cisco.com</email>
</address>
</author>
<author fullname="Stewart Bryant" initials="S" role="editor"
surname="Bryant">
<organization>Cisco Systems</organization>
<address>
<postal>
<street></street>
</postal>
<email>stbryant@cisco.com</email>
</address>
</author>
<author fullname="Siva Sivabalan" initials="S" surname="Sivabalan">
<organization>Cisco Systems</organization>
<address>
<postal>
<street></street>
</postal>
<email>msiva@cisco.com</email>
</address>
</author>
<author fullname="George Swallow" initials="G " surname="Swallow">
<organization>Cisco Systems</organization>
<address>
<postal>
<street></street>
</postal>
<email>swallow@cisco.com</email>
</address>
</author>
<author fullname="David Ward" initials="D" surname="Ward">
<organization>Juniper Networks</organization>
<address>
<postal>
<street></street>
</postal>
<email>dward@Juniper.net</email>
</address>
</author>
<author fullname="Vishwas Manral" initials="V" surname="Manral ">
<organization>IP Infusion Inc.</organization>
<address>
<postal>
<street>Bamankhola,</street>
<city>Bansgali,</city>
<region>Almora, Uttaranchal</region>
<code>263601</code>
<country>India</country>
</postal>
<email>vishwas.ietf@gmail.com</email>
</address>
</author>
<date year="2010" />
<area>Internet</area>
<workgroup>MPLS</workgroup>
<keyword></keyword>
<keyword></keyword>
<keyword>MPLS</keyword>
<keyword>Internet-Draft</keyword>
<abstract>
<t>In some application of the associated channel header (ACH), it is
necessary to have the ability to include a set of TLVs to provide
additional context information for the ACH payload. This document
defines a number of TLV types.</t>
<t>This document is a product of a joint Internet Engineering Task Force
(IETF) / International Telecommunications Union Telecommunications
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 as
defined by the ITU-T.</t>
</abstract>
<note 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">RFC2119</xref>.</t>
</note>
</front>
<middle>
<section title="Introduction">
<t>The MPLS generic associated channel header specification <xref
target="RFC5586"></xref> (GACH) describes a TLV structure that is used
to provide additional context information for the ACH payload. This
document defines a number of TLVs that are required by the MPLS-TP
design <xref target="RFC5654"></xref>, <xref
target="I-D.ietf-mpls-tp-framework"></xref>.</t>
</section>
<section title="ACH TLV Object Definitions">
<t>This section provides the definition for a number of ACH TLV objects.
In each case the length in the TLV header is the length of only the
value component.</t>
<section title="The Null TLV Object">
<t>The Null TLV provides an OPTIONAL mechanism of restoring 32bit
alignment of the following element in the packet and also provides an
OPTIONAL mechanism to reserve space in the packet to be used by TLV
objects that will be written by LSR that perform some operation on the
packet at a later time. For security reasons the value must be
zero.</t>
<t><figure anchor="NullTLV" title="Null TLV Object">
<preamble></preamble>
<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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AchTlvType = 0 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
~ Value = 0 ~
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
]]></artwork>
<postamble></postamble>
</figure></t>
</section>
<section anchor="SAv4s" title="IPv4 Source Address">
<t>This TLV specifies the IPv4 <xref target="RFC0791"></xref> source
address (SAv4) of an ACH packet.</t>
<t>Where the packet is associated with a maintenance request/response
operation it refers to the requester of the operation, i.e. It is the
address of the Maintenance End Point that initiated the operation
being either requested, or is being responded to.</t>
<t><figure anchor="SAv4" title="IPv4 Source Address">
<preamble></preamble>
<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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AchTlvType = 1 | Length = 4 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| IPv4 Address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
]]></artwork>
<postamble></postamble>
</figure></t>
</section>
<section anchor="SAv6s" title="IPv6 Source Address">
<t>This TLV specifies the IPv6 <xref target="RFC2460"></xref> source
address (SAv6) of an ACH packet.</t>
<t>Where the packet is associated with a maintenance request/response
operation it refers to the requester of the operation, i.e. It is the
address of the Maintenance End Point that initiated the operation
being either requested, or is being responded to.</t>
<t><figure anchor="SAv6" title="IPv4 Source Address">
<preamble></preamble>
<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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AchTlvType = 2 | Length = 16 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
~ IPv6 Address |
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
]]></artwork>
<postamble></postamble>
</figure></t>
</section>
<section anchor="ICCs" title="ITU-T Carrier Code">
<t>This TLV is used to carry an ITU-T Carrier Code Identifier (ICC) as
defined in M.1400 <xref target="M1400"></xref>.</t>
<figure anchor="ICC" title="ITU-T Carrier Code">
<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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AchTlvType = 3 | Length = 16 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ICC |
| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
]]></artwork>
</figure>
<t></t>
<t>The ICC is encoded in ASCII in a fixed format 6 byte field, with
unused trailing bytes set to NULL (0).</t>
</section>
<section anchor="GIDs" title="Global Identifier">
<t>This TLV is used to carry a Global Identifier (Global_ID) <xref
target="I-D.ietf-mpls-tp-identifiers"></xref> .<figure anchor="GID"
title="Global_ID TLV">
<preamble></preamble>
<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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AchTlvType = 4 | Length = 4 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Global ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
]]></artwork>
<postamble></postamble>
</figure></t>
</section>
<section anchor="IFIDs" title="Network Interface Identifier ">
<t>This TLV is used to carry Network Interface ID (IF_ID) <xref
target="I-D.ietf-mpls-tp-identifiers"></xref> . As defined in <xref
target="I-D.ietf-mpls-tp-identifiers"></xref>, an IF_ID consists of a
node identifier (Node_ID) and a Logical Interface Handle (LIH), both
or which are 32 bit identifiers.</t>
<t><figure anchor="IFID" title="IF_ID TLV">
<preamble></preamble>
<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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AchTlvType = 5 | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Node_ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| LIH |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
]]></artwork>
<postamble></postamble>
</figure></t>
</section>
<section title="Authentication">
<t>The structure of the ACH authentication (auth) TLV is as
follows:</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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AchTlvType = 6 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Auth Type | Auth Len | Authentication Data... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+]]></artwork>
</figure>
<t></t>
<t>The authentication proceedures and data format used is the same as
that defined in Sections 4.1, 4.2, 4.3 and 4.4 of <xref
target="I-D.ietf-bfd-base"></xref> .</t>
<t>Each document which defines a channel type needs to define whether
an authentication TLV is required, permitted, or disallowed, and the
actions to be taken in normal and error situations.</t>
<t>An application not supporting data origin authentication MAY use
this mechanism instead of defining its own proprietery mechanism.</t>
</section>
</section>
<section title="Security Considerations">
<t>This specification defines a mechanism to identify a set of protocol
parameters. The necessary security considerations will be described in
the definition of the protocols that uses these parameters.</t>
</section>
<section title="IANA Considerations">
<t>IANA is requested to create a new registry in the pseudowire name
spaces: the ACH TLV Registry.</t>
<t>The ACH TLV Registry should be initialized with the following
entries. The allocation policy for this registry is IETF consensus.</t>
<figure>
<artwork><![CDATA[
Name Type Length Description Reference
(octets)
Null 0 3 Null TLV This Draft
SAv4 1 4 IPv4 Source Address This Draft
SAv6 2 16 IPv6 Source Address This Draft
ICC 3 6 ITU-T Carrier Code This Draft
Global_ID 4 4 Global Identifier This Draft
IF_ID 5 8 Network Interface ID This Draft
Auth 6 var Authentication This Draft
]]></artwork>
<postamble></postamble>
</figure>
<t></t>
</section>
</middle>
<back>
<references title="Normative References">
<?rfc include='reference.RFC.2119'?>
<?rfc include='reference.RFC.0791'?>
<?rfc include='reference.RFC.2460'?>
<?rfc include='reference.I-D.ietf-mpls-tp-identifiers'?>
<reference anchor="M1400">
<front>
<title>ITU-T Recommendation M.1400, "Designations for
interconnections among operators' networks"</title>
<author>
<organization></organization>
</author>
<date year="2006" />
</front>
</reference>
</references>
<references title="Informative References">
<?rfc include='reference.RFC.5586'?>
<?rfc include='reference.RFC.5654'?>
<?rfc include='reference.I-D.ietf-mpls-tp-framework'?>
<?rfc include='reference.I-D.ietf-bfd-base'?>
</references>
</back>
</rfc>
| PAFTECH AB 2003-2026 | 2026-04-21 20:52:31 |