Documentation of IANA Assignments for Label Distribution Protocol (LDP), Resource ReSerVation Protocol (RSVP), and Resource ReSerVation Protocol-Traffic Engineering (RSVP-TE) Extensions for Optical UNI Signaling
RFC 3476
| Document | Type |
RFC - Informational
(April 2003; No errata)
Updated by RFC 3468
Was draft-bala-uni-ldp-rsvp-extensions (individual in tsv area)
|
|
|---|---|---|---|
| Last updated | 2015-10-14 | ||
| Stream | IETF | ||
| Formats | plain text html pdf htmlized bibtex | ||
| Stream | WG state | (None) | |
| Document shepherd | No shepherd assigned | ||
| IESG | IESG state | RFC 3476 (Informational) | |
| Consensus Boilerplate | Unknown | ||
| Telechat date | |||
| Responsible AD | Scott Bradner | ||
| IESG note | On IESG agenda for 23 Jan | ||
| Send notices to | (None) | ||
Network Working Group B. Rajagopalan
Request for Comments: 3476 Tellium, Inc.
Category: Informational March 2003
Documentation of IANA Assignments for Label Distribution Protocol
(LDP), Resource ReSerVation Protocol (RSVP), and Resource ReSerVation
Protocol-Traffic Engineering (RSVP-TE) Extensions
for Optical UNI Signaling
Status of this Memo
This memo provides information for the Internet community. It does
not specify an Internet standard of any kind. Distribution of this
memo is unlimited.
Copyright Notice
Copyright (C) The Internet Society (2003). All Rights Reserved.
Abstract
The Optical Interworking Forum (OIF) has defined extensions to the
Label Distribution Protocol (LDP) and the Resource ReSerVation
Protocol (RSVP) for optical User Network Interface (UNI) signaling.
These extensions consist of a set of new data objects and error
codes. This document describes these extensions.
1. Introduction
The OIF UNI signaling specification is described in [8]. This
specification utilizes IETF protocol standards as well as IETF work
in progress. Specifically, the following IETF specifications are
used:
o Label distribution protocol (LDP) [6]
o Resource reservation protocol (RSVP) [5]
o GMPLS signaling and GMPLS extensions for SONET/SDH [4]
o GMPLS RSVP-TE and CR-LDP extensions [2, 3]
The aim of the OIF UNI specification is the maximal re-use of IETF
protocol definitions. A few extensions to IETF protocols, however,
have been defined to serve UNI-specific needs. These extensions are
described in this document.
Rajagopalan Informational [Page 1]
RFC 3476 LDP & RSVP Extensions for Optical UNI Signaling March 2003
2. LDP Extensions for UNI Signaling
The LDP extensions for UNI signaling consist of new TLVs that capture
UNI-specific parameters and new UNI-specific status codes. The new
TLVs are Source ID (3 TLVs), Destination ID (3 TLVs), Egress Label,
Local Connection ID, Diversity, Contract ID, and UNI Service Level
[8]. These are described below. The new status codes are assigned
from the private use space of LDP codes, as described in [8]. The
UNI specification [8] also defines two new LDP messages, Status
Enquiry and Status Response. These messages have been obsoleted and
hence no code points are requested in this document for them.
2.1 Source ID TLVs
Three TLVs have been defined to encode the Source ID. The content and
usage of these TLVs are described in [8].
2.1.1 IPv4 Source ID
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|U|F|Source ID Type (0x0960) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
~ Contents ~
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
2.1.2 IPv6 Source ID
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|U|F|Source ID Type (0x0961) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
~ Contents ~
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Rajagopalan Informational [Page 2]
RFC 3476 LDP & RSVP Extensions for Optical UNI Signaling March 2003
2.1.3 NSAP Source ID
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|U|F|Source ID Type (0x0962) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
~ Contents ~
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
2.2 Destination ID TLVs
Three TLVs have been defined to encode the Destination ID. The
content and usage of these TLVs are described in [8].
2.2.1 IPv4 Destination ID
0 1 2 3
Show full document text