draft-ietf-ccamp-gmpls-g-694-lambda-labels-10.txt   draft-ietf-ccamp-gmpls-g-694-lambda-labels-11.txt 
Network Working Group Tomohiro Otani(Ed.) Network Working Group Tomohiro Otani(Ed.)
Internet Draft KDDI Internet Draft KDDI
Updates: 3471(if approved) Dan Li(Ed.) Updates: 3471(if approved) Dan Li(Ed.)
Category: Standards Track Huawei Category: Standards Track Huawei
Expires: June 2011 December 13, 2010 Expires: July 2011 January 11, 2011
Generalized Labels for Lambda-Switching Capable Label Switching Generalized Labels for Lambda-Switching Capable Label Switching
Routers Routers
draft-ietf-ccamp-gmpls-g-694-lambda-labels-10.txt draft-ietf-ccamp-gmpls-g-694-lambda-labels-11.txt
Status of this Memo Status of this Memo
This Internet-Draft is submitted to IETF in full conformance with the This Internet-Draft is submitted to IETF in full conformance with
provisions of BCP 78 and BCP 79. the provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that other Task Force (IETF), its areas, and its working groups. Note that
groups may also distribute working documents as Internet-Drafts. other groups may also distribute working documents as Internet-
Drafts.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six
and may be updated, replaced, or obsoleted by other documents at any months and may be updated, replaced, or obsoleted by other
time. It is inappropriate to use Internet-Drafts as reference documents at any time. It is inappropriate to use Internet-Drafts
material or to cite them other than as "work in progress." as reference material or to cite them other than as "work in
progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html http://www.ietf.org/shadow.html
This Internet-Draft will expire on June 13, 2011. This Internet-Draft will expire on July 11, 2011.
Copyright Notice Copyright Notice
Copyright (c) 2010 IETF Trust and the persons identified as the Copyright (c) 2010 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with
to this document. Code Components extracted from this document must respect to this document. Code Components extracted from this
include Simplified BSD License text as described in Section 4.e of document must include Simplified BSD License text as described in
the Trust Legal Provisions and are provided without warranty as Section 4.e of the Trust Legal Provisions and are provided
described in the Simplified BSD License. without warranty as described in the Simplified BSD License.
This document may contain material from IETF Documents or IETF This document may contain material from IETF Documents or IETF
Contributions published or made publicly available before November Contributions published or made publicly available before
10, 2008. The person(s) controlling the copyright in some of this November 10, 2008. The person(s) controlling the copyright in
material may not have granted the IETF Trust the right to allow some of this material may not have granted the IETF Trust the
modifications of such material outside the IETF Standards Process. right to allow modifications of such material outside the IETF
Without obtaining an adequate license from the person(s) controlling Standards Process. Without obtaining an adequate license from the
the copyright in such materials, this document may not be modified person(s) controlling the copyright in such materials, this
outside the IETF Standards Process, and derivative works of it may document may not be modified outside the IETF Standards Process,
not be created outside the IETF Standards Process, except to format and derivative works of it may not be created outside the IETF
it for publication as an RFC or to translate it into languages other Standards Process, except to format it for publication as an RFC
than English. or to translate it into languages other than English.
Abstract Abstract
Technology in the optical domain is constantly evolving and as a Technology in the optical domain is constantly evolving and as a
consequence new equipment providing lambda switching capability has consequence new equipment providing lambda switching capability
been developed and is currently being deployed. has been developed and is currently being deployed.
Generalized MPLS (GMPLS) is a family of protocols that can be used Generalized MPLS (GMPLS) is a family of protocols that can be
to operate networks built from a range of technologies including used to operate networks built from a range of technologies
wavelength (or lambda) switching. For this purpose, GMPLS defined including wavelength (or lambda) switching. For this purpose,
that a wavelength label only has significance between two neighbors GMPLS defined that a wavelength label only has significance
and global wavelength semantics are not considered. between two neighbors and global wavelength semantics are not
considered.
In order to facilitate interoperability in a network composed of In order to facilitate interoperability in a network composed of
next generation lambda switch-capable equipment, this document next generation lambda switch-capable equipment, this document
defines a standard lambda label format that is compliant with Dense defines a standard lambda label format that is compliant with
Wavelength Division Multiplexing and Coarse Wavelength Division Dense Wavelength Division Multiplexing and Coarse Wavelength
Multiplexing grids defined by the International Telecommunication Division Multiplexing grids defined by the International
Union Telecommunication Standardization Sector. The label format Telecommunication Union Telecommunication Standardization Sector.
defined in this document can be used in GMPLS signaling and routing The label format defined in this document can be used in GMPLS
protocols. signaling and routing protocols.
Conventions used in this document Conventions used in this document
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and
document are to be interpreted as described in [RFC2119]. "OPTIONAL" in this document are to be interpreted as described in
[RFC2119].
1. Introduction 1. Introduction
As described in [RFC3945], Generalized MPLS (GMPLS) extends MPLS As described in [RFC3945], Generalized MPLS (GMPLS) extends MPLS
from supporting only packet (Packet Switching Capable - PSC) from supporting only packet (Packet Switching Capable - PSC)
interfaces and switching to also include support for four new interfaces and switching to also include support for four new
classes of interfaces and switching: classes of interfaces and switching:
o Layer-2 Switch Capable (L2SC) o Layer-2 Switch Capable (L2SC)
o Time-Division Multiplex (TDM) o Time-Division Multiplex (TDM)
o Lambda Switch Capable (LSC) o Lambda Switch Capable (LSC)
o Fiber-Switch Capable (FSC). o Fiber-Switch Capable (FSC).
A functional description of the extensions to MPLS signaling needed A functional description of the extensions to MPLS signaling
to support new classes of interfaces and switching is provided in needed to support new classes of interfaces and switching is
[RFC3471]. provided in [RFC3471].
This document presents details that are specific to the use of GMPLS This document presents details that are specific to the use of
with Lambda Switch Capable (LSC) equipment. Technologies such as GMPLS with Lambda Switch Capable (LSC) equipment. Technologies
Reconfigurable Optical Add/Drop Multiplex (ROADM) and Wavelength such as Reconfigurable Optical Add/Drop Multiplex (ROADM) and
Cross-Connect (WXC) operate at the wavelength switching level. Wavelength Cross-Connect (WXC) operate at the wavelength
[RFC3471] has defined that a wavelength label (section 3.2.1.1) "only switching level. [RFC3471] has defined that a wavelength label
has significance between two neighbors" and global wavelength (section 3.2.1.1) "only has significance between two neighbors"
semantics is not considered. In order to facilitate interoperability and global wavelength semantics is not considered. In order to
in a network composed of lambda switch-capable equipment, this facilitate interoperability in a network composed of lambda
document defines a standard lambda label format, which is compliant switch-capable equipment, this document defines a standard lambda
with both [G.694.1](Dense Wavelength Division Multiplexing (DWDM)- label format, which is compliant with both [G.694.1](Dense
grid) or [G.694.2](Coarse Wavelength Division Multiplexing (CWDM)- Wavelength Division Multiplexing (DWDM)-grid) or [G.694.2](Coarse
grid). Wavelength Division Multiplexing (CWDM)-grid).
2. Assumed Network Model and Related Problem Statement 2. Assumed Network Model and Related Problem Statement
Figure 1 depicts an all-optically switched network consisting of Figure 1 depicts an all-optically switched network consisting of
different vendors' optical network domains. Vendor A's network different vendors' optical network domains. Vendor A's network
consists of ROADM or WXC, and vendor B's network consists of a number consists of ROADM or WXC, and vendor B's network consists of a
of photonic cross-connect (PXC) and DWDM multiplexer & demultiplexer, number of photonic cross-connect (PXC) and DWDM multiplexer &
otherwise both vendors' networks might be based on the same demultiplexer, otherwise both vendors' networks might be based on
technology. the same technology.
In this case, the use of standardized wavelength label information is In this case, the use of standardized wavelength label
quite significant to establish a wavelength-based LSP. It is also an information is quite significant to establish a wavelength-based
important constraint when conducting CSPF calculation for use by LSP. It is also an important constraint when conducting CSPF
Generalized Multi-Protocol Label Switching (GMPLS) RSVP-TE signaling, calculation for use by Generalized Multi-Protocol Label Switching
[RFC3473]. The way the Constrained Shortest Path First (CSPF) is (GMPLS) RSVP-TE signaling, [RFC3473]. The way the Constrained
performed is outside the scope of this document. Shortest Path First (CSPF) is performed is outside the scope of
this document.
It is needless to say, an LSP must be appropriately provisioned It is needless to say, an LSP must be appropriately provisioned
between a selected pair of ports not only within Domain A but also between a selected pair of ports not only within Domain A but
over multiple domains satisfying wavelength constraints. also over multiple domains satisfying wavelength constraints.
Figure 2 illustrates in detail the interconnection between Domain A Figure 2 illustrates in detail the interconnection between Domain
and Domain B. A and Domain B.
| |
Domain A (or Vendor A) | Domain B (or Vendor B) Domain A (or Vendor A) | Domain B (or Vendor B)
| |
Node-1 Node-2 | Node-6 Node-7 Node-1 Node-2 | Node-6 Node-7
+--------+ +--------+ | +-------+ +-+ +-+ +-------+ +--------+ +--------+ | +-------+ +-+ +-+ +-------+
| ROADM | | ROADM +---|------+ PXC +-+D| |D+-+ PXC | | ROADM | | ROADM +---|------+ PXC +-+D| |D+-+ PXC |
| or WXC +========+ or WXC +---|------+ +-+W+=====+W+-+ | | or WXC +========+ or WXC +---|------+ +-+W+=====+W+-+ |
| (LSC) | | (LSC) +---|------+ (LSC) +-+D| |D+-+ (LSC) | | (LSC) | | (LSC) +---|------+ (LSC) +-+D| |D+-+ (LSC) |
+--------+ +--------+ | | +-|M| |M+-+ | +--------+ +--------+ | | +-|M| |M+-+ |
skipping to change at page 5, line 33 skipping to change at page 5, line 33
| WDM | E | | | E | WDM | | WDM | E | | | E | WDM |
| =====| 5 | | | 8 |===== | | =====| 5 | | | 8 |===== |
| | | | | | | | | | | | | |
| +---+ | +---+ | | +---+ | +---+ |
+-------------------------------------------------------------+ +-------------------------------------------------------------+
Figure 2 Interconnecting details between two domains Figure 2 Interconnecting details between two domains
In the scenario of Figure 1, consider the setting up of a In the scenario of Figure 1, consider the setting up of a
bidirectional LSP from ingress switch 1 to egress switch 9 using bidirectional LSP from ingress switch 1 to egress switch 9 using
GMPLS RSVP-TE. In order to satisfy wavelength continuity constraint, GMPLS RSVP-TE. In order to satisfy wavelength continuity
a fixed wavelength (lambda 1) needs to be used in domain A and domain constraint, a fixed wavelength (lambda 1) needs to be used in
B. A Path message will be used for signaling. The Path message will domain A and domain B. A Path message will be used for signaling.
contain the Upstream_Label object and a Label_Set object; both The Path message will contain the Upstream_Label object and a
containing the same value. The Label_Set object is made by only one Label_Set object; both containing the same value. The Label_set
sub channel that must be same as the Upstream_Label object. The Path object shall contain a single sub-channel that must be the same
setup will continue downstream to switch 9 by configuring each lambda as the Upstream_Label object. The Path setup will continue
switch based on the wavelength label. If a node has a tunable downstream to switch 9 by configuring each lambda switch based on
wavelength transponder, the tuning wavelength is considered as a part the wavelength label. If a node has a tunable wavelength
of wavelength switching operation. transponder, the tuning wavelength is considered as a part of
wavelength switching operation.
Not using a standardized label would add undue burden on the operator Not using a standardized label would add undue burden on the
to enforce policy as each manufacturer may decide on a different operator to enforce policy as each manufacturer may decide on a
representation and therefore each domain may have its own label different representation and therefore each domain may have its
formats. Moreover, manual provisioning may lead to misconfiguration own label formats. Moreover, manual provisioning may lead to
if domain-specific labels are used. misconfiguration if domain-specific labels are used.
Therefore, a wavelength label should be standardized in order to Therefore, a wavelength label should be standardized in order to
allow interoperability between multiple domains; otherwise allow interoperability between multiple domains; otherwise
appropriate existing labels are identified in support of wavelength appropriate existing labels are identified in support of
availability. As identical wavelength information, the ITU-T wavelength availability. As identical wavelength information, the
frequency grid specified in [G.694.1] for DWDM and wavelength ITU-T frequency grid specified in [G.694.1] for DWDM and
information in [G.694.2] for CWDM are used by Label Switching Routers wavelength information in [G.694.2] for CWDM are used by Label
(LSRs) and should be followed as a wavelength label. Switching Routers (LSRs) and should be followed as a wavelength
label.
3. Label Related Formats 3. Label Related Formats
To deal with the widening scope of MPLS into the optical and time To deal with the widening scope of MPLS into the optical and time
domains, several new forms of "label" have been defined in [RFC3471]. domains, several new forms of "label" have been defined in
This section contains a definition of a Wavelength label based on [RFC3471]. This section contains a definition of a Wavelength
[G.694.1] or [G.694.2] for use by LSC LSRs. label based on [G.694.1] or [G.694.2] for use by LSC LSRs.
3.1. Wavelength Labels 3.1. Wavelength Labels
In section 3.2.1.1 of [RFC3471], a Wavelength label is defined to In section 3.2.1.1 of [RFC3471], a Wavelength label is defined to
have significance between two neighbors, and the receiver may need to have significance between two neighbors, and the receiver may
convert the received value into a value that has local significance. need to convert the received value into a value that has local
significance.
We do not need to define a new type as the information stored is We do not need to define a new type as the information stored is
either a port label or a wavelength label. Only the wavelength label either a port label or a wavelength label. Only the wavelength
as below needs to be defined. label as below needs to be defined.
LSC equipment uses multiple wavelengths controlled by a single LSC equipment uses multiple wavelengths controlled by a single
control channel. In a case, the label indicates the wavelength to be control channel. In a case, the label indicates the wavelength to
used for the LSP. This document defines a standardize wavelength be used for the LSP. This document defines a standardized
label format. As an example of wavelength values, the reader is wavelength label format. As an example of wavelength values, the
referred to [G.694.1] which lists the frequencies from the ITU-T DWDM reader is referred to [G.694.1] which lists the frequencies from
frequency grid. The same can be done for CWDM technology by using the ITU-T DWDM frequency grid. The same can be done for CWDM
the wavelength defined in [G.694.2]. technology by using the wavelength defined in [G.694.2].
Since the ITU-T DWDM grid is based on nominal central frequencies, we Since the ITU-T DWDM grid is based on nominal central frequencies,
need to indicate the appropriate table, the channel spacing in the we need to indicate the appropriate table, the channel spacing in
grid and a value n that allows the calculation of the frequency. That the grid and a value n that allows the calculation of the
value can be positive or negative. frequency. That value can be positive or negative.
The frequency is calculated as such in [G.694.1]: The frequency is calculated as such in [G.694.1]:
Frequency (THz) = 193.1 THz + n * channel spacing (THz) Frequency (THz) = 193.1 THz + n * channel spacing (THz)
Where "n" is a two's-complement integer (positive, negative or 0) and Where "n" is a two's-complement integer (positive, negative or 0)
"channel spacing" is defined to be 0.0125, 0.025, 0.05 or 0.1 THz. and "channel spacing" is defined to be 0.0125, 0.025, 0.05 or 0.1
When wider channel spacing such as 0.2 THz is utilized, the THz. When wider channel spacing such as 0.2 THz is utilized, the
combination of narrower channel spacing and the value "n" can provide combination of narrower channel spacing and the value "n" can
proper frequency with that channel spacing. Channel spacing is not provide proper frequency with that channel spacing. Channel
utilized to indicate the LSR capability but only to specify a spacing is not utilized to indicate the LSR capability but only
frequency in signaling. to specify a frequency in signaling.
For the other example of the case of the ITU-T CWDM grid, the spacing For the other example of the case of the ITU-T CWDM grid, the
between different channels was defined to be 20nm, so we need to pass spacing between different channels was defined to be 20nm, so we
the wavelength value in nanometers(nm) in this case. Examples of CWDM need to pass the wavelength value in nanometers(nm) in this case.
wavelengths are 1471, 1491, etc. nm. Examples of CWDM wavelengths are 1471, 1491, etc. nm.
The wavelength is calculated as follows The wavelength is calculated as follows
Wavelength (nm) = 1471 nm + n * 20 nm Wavelength (nm) = 1471 nm + n * 20 nm
Where "n" is a two's-complement integer (positive, negative or 0). Where "n" is a two's-complement integer (positive, negative or 0).
The grids listed in [G.694.1] and [G.694.2] are not numbered and The grids listed in [G.694.1] and [G.694.2] are not numbered and
change with the changing frequency spacing as technology advances, so change with the changing frequency spacing as technology advances,
an index is not appropriate in this case. so an index is not appropriate in this case.
3.2. DWDM Wavelength Label 3.2. DWDM Wavelength Label
For the case of lambda switching (LSC) of DWDM, the information For the case of lambda switching (LSC) of DWDM, the information
carried in a Wavelength label is: carried in a Wavelength label is:
0 1 2 3 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 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Grid | C.S | Identifier | n | |Grid | C.S | Identifier | n |
skipping to change at page 8, line 23 skipping to change at page 8, line 39
+----------+---------+ +----------+---------+
| 25 | 3 | | 25 | 3 |
+----------+---------+ +----------+---------+
| 12.5 | 4 | | 12.5 | 4 |
+----------+---------+ +----------+---------+
|Future use| 5 - 15 | |Future use| 5 - 15 |
+----------+---------+ +----------+---------+
(3) Identifier: 9 bits (3) Identifier: 9 bits
The identifier field is a per-node assigned and scoped value. This The identifier field in lambda label format is used to
field MAY change on a per-hop basis. In all cases but one, a node MAY distinguish different lasers (in one node) when they can transmit
select any value, including zero (0), for this field. Once selected, the same frequency lambda. The identifier field is a per-node
the value MUST NOT change until the LSP is torn down and the value assigned and scoped value. This field MAY change on a per-hop
MUST be used in all LSP related messages, e.g., in Resv messages and basis. In all cases but one, a node MAY select any value,
label RRO subobjects. The sole special case occurs when this label including zero (0), for this field. Once selected, the value MUST
format is used in a label ERO subobject. In this case, the special NOT change until the LSP is torn down and the value MUST be used
value of zero (0) means that the referenced node MAY assign any in all LSP related messages, e.g., in Resv messages and label RRO
subobjects. The sole special case occurs when this label format
is used in a label ERO subobject. In this case, the special value
of zero (0) means that the referenced node MAY assign any
Identifier field value, including zero (0), when establishing the Identifier field value, including zero (0), when establishing the
corresponding LSP. corresponding LSP. When non-zero value is assigned to the
identifier field in a label ERO subobject, the referenced node
MUST use the assigned value for the identifier field in the
corresponding LSP related messages.
(4) n: 16 bits (4) n: 16 bits
n is a two's-complement integer to take either a negative, zero or a n is a two's-complement integer to take either a negative, zero
positive value. The value used to compute the frequency as shown or a positive value. The value used to compute the frequency as
above. shown above.
3.3. CWDM Wavelength Label 3.3. CWDM Wavelength Label
For the case of lambda switching (LSC) of CWDM, the information For the case of lambda switching (LSC) of CWDM, the information
carried in a Wavelength label is: carried in a Wavelength label is:
0 1 2 3 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 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Grid | C.S | Identifier | n | |Grid | C.S | Identifier | n |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The structure of the label in the case of CWDM is the same as that of The structure of the label in the case of CWDM is the same as
DWDM case. that of DWDM case.
(1) Grid: 3 bits (1) Grid: 3 bits
The value for grid is set to 2 for ITU-T CWDM Grid as defined in The value for grid is set to 2 for ITU-T CWDM Grid as defined in
[G.694.2]. [G.694.2].
+----------+---------+ +----------+---------+
| Grid | Value | | Grid | Value |
+----------+---------+ +----------+---------+
| Reserved | 0 | | Reserved | 0 |
skipping to change at page 9, line 47 skipping to change at page 10, line 33
+----------+---------+ +----------+---------+
| Reserved | 0 | | Reserved | 0 |
+----------+---------+ +----------+---------+
| 20 | 1 | | 20 | 1 |
+----------+---------+ +----------+---------+
|Future use| 2 - 15 | |Future use| 2 - 15 |
+----------+---------+ +----------+---------+
(3) Identifier: 9 bits (3) Identifier: 9 bits
The identifier field is a per-node assigned and scoped value. This The identifier field in lambda label format is used to
field MAY change on a per-hop basis. In all cases but one, a node MAY distinguish different lasers (in one node) when they can transmit
select any value, including zero (0), for this field. Once selected, the same frequency lambda. The identifier field is a per-node
the value MUST NOT change until the LSP is torn down and the value assigned and scoped value. This field MAY change on a per-hop
MUST be used in all LSP related messages, e.g., in Resv messages and basis. In all cases but one, a node MAY select any value,
label RRO subobjects. The sole special case occurs when this label including zero (0), for this field. Once selected, the value MUST
format is used in a label ERO subobject. In this case, the special NOT change until the LSP is torn down and the value MUST be used
value of zero (0) means that the referenced node MAY assign any in all LSP related messages, e.g., in Resv messages and label RRO
subobjects. The sole special case occurs when this label format
is used in a label ERO subobject. In this case, the special value
of zero (0) means that the referenced node MAY assign any
Identifier field value, including zero (0), when establishing the Identifier field value, including zero (0), when establishing the
corresponding LSP. corresponding LSP. When non-zero value is assigned to the
identifier field in a label ERO subobject, the referenced node
MUST use the assigned value for the identifier field in the
corresponding LSP related messages.
(4) n: 16 bits (4) n: 16 bits
n is a two's-complement integer. The value used to compute the n is a two's-complement integer. The value used to compute the
wavelength as shown above. wavelength as shown above.
4. Security Considerations 4. Security Considerations
This document introduces no new security considerations to [RFC3471] This document introduces no new security considerations to
and [RFC3473]. For a general discussion on MPLS and GMPLS related [RFC3471] and [RFC3473]. For a general discussion on MPLS and
security issues, see the MPLS/GMPLS security framework [RFC5920]. GMPLS related security issues, see the MPLS/GMPLS security
framework [RFC5920].
5. IANA Considerations 5. IANA Considerations
IANA maintains the "Generalized Multi-Protocol Label Switching IANA maintains the "Generalized Multi-Protocol Label Switching
(GMPLS) Signaling Parameters" registry. IANA is requested to add (GMPLS) Signaling Parameters" registry. IANA is requested to add
three new subregistries to track the codepoints (Grid and C.S.) used three new subregistries to track the codepoints (Grid and C.S.)
in the DWDM and CWDM Wavelength Labels, which are described in the used in the DWDM and CWDM Wavelength Labels, which are described
following sections. in the following sections.
5.1. Grid Subregistry 5.1. Grid Subregistry
Initial entries in this subregistry are as follows: Initial entries in this subregistry are as follows:
Value Grid Reference Value Grid Reference
----- ------------------------- ---------- ----- ------------------------- ----------
0 Reserved [This.I-D] 0 Reserved [This.I-D]
1 ITU-T DWDM [This.I-D] 1 ITU-T DWDM [This.I-D]
2 ITU-T CWDM [This.I-D] 2 ITU-T CWDM [This.I-D]
skipping to change at page 11, line 30 skipping to change at page 12, line 30
Value Channel Spacing (nm) Reference Value Channel Spacing (nm) Reference
----- ------------------------- ---------- ----- ------------------------- ----------
0 Reserved [This.I-D] 0 Reserved [This.I-D]
1 20 [This.I-D] 1 20 [This.I-D]
2-15 Not assigned at this time [This.I-D] 2-15 Not assigned at this time [This.I-D]
New values are assigned according to Standards Action. New values are assigned according to Standards Action.
6. Acknowledgments 6. Acknowledgments
The authors would like to thank Adrian Farrel, Lou Berger, Lawrence The authors would like to thank Adrian Farrel, Lou Berger,
Mao, Zafar Ali and Daniele Ceccarelli for the discussion and their Lawrence Mao, Zafar Ali and Daniele Ceccarelli for the discussion
comments. and their comments.
7. References 7. References
7.1. Normative References 7.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC3471] Berger, L., "Generalized Multi-Protocol Label Switching [RFC3471] Berger, L., "Generalized Multi-Protocol Label Switching
(MPLS) Signaling Functional Description", RFC 3471, January (MPLS) Signaling Functional Description", RFC 3471,
2003. January 2003.
[RFC3473] Berger, L., "Generalized Multi-Protocol Label Switching [RFC3473] Berger, L., "Generalized Multi-Protocol Label Switching
(MPLS) Signaling - Resource ReserVation Protocol Traffic (MPLS) Signaling - Resource ReserVation Protocol Traffic
Engineering (RSVP-TE) Extensions", RFC 3473, January 2003. Engineering (RSVP-TE) Extensions", RFC 3473, January
2003.
[RFC3945] Mannie, E., Ed., "Generalized Multiprotocol Label Switching [RFC3945] Mannie, E., Ed., "Generalized Multiprotocol Label
(GMPLS) Architecture", RFC 3945, October 2004. Switching (GMPLS) Architecture", RFC 3945, October 2004.
7.2. Informative References 7.2. Informative References
[G.694.1] ITU-T Recommendation G.694.1, "Spectral grids for WDM [G.694.1] ITU-T Recommendation G.694.1, "Spectral grids for WDM
applications: DWDM frequency grid", June 2002. applications: DWDM frequency grid", June 2002.
[G.694.2] ITU-T Recommendation G.694.2, "Spectral grids for WDM [G.694.2] ITU-T Recommendation G.694.2, "Spectral grids for WDM
applications: CWDM wavelength grid", December 2003. applications: CWDM wavelength grid", December 2003.
[RFC5920] Fang, L., "Security Framework for MPLS and GMPLS [RFC5920] Fang, L., "Security Framework for MPLS and GMPLS
skipping to change at page 14, line 7 skipping to change at page 15, line 7
Takehiro Tsuritani Takehiro Tsuritani
KDDI R&D Laboratories Inc. KDDI R&D Laboratories Inc.
2-1-15 Ohara Fujimino-shi 2-1-15 Ohara Fujimino-shi
Saitama, 356-8502, Japan Saitama, 356-8502, Japan
Phone: +81-49-278-7806 Phone: +81-49-278-7806
Email: tsuri@kddilabs.jp Email: tsuri@kddilabs.jp
9. Appendix A. DWDM Example 9. Appendix A. DWDM Example
Considering the network displayed in figure 1 it is possible to show Considering the network displayed in figure 1 it is possible to
an example of LSP set up using the lambda labels. show an example of LSP set up using the lambda labels.
Node 1 receives the request for establishing an LSP from itself to Node 1 receives the request for establishing an LSP from itself
Node 9. The ITU-T grid to be used is the DWDM one, the channel to Node 9. The ITU-T grid to be used is the DWDM one, the channel
spacing is 50Ghz and the wavelength to be used is 193,35 THz. spacing is 50Ghz and the wavelength to be used is 193,35 THz.
Node 1 signals the LSP via a Path message including a Wavelength Node 1 signals the LSP via a Path message including a Wavelength
Label structured as defined in section 4.2: Label structured as defined in section 3.2:
0 1 2 3 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 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Grid | C.S | Identifier | n | |Grid | C.S | Identifier | n |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Where: Where:
Grid = 1 : ITU-T DWDM grid Grid = 1 : ITU-T DWDM grid
skipping to change at page 14, line 44 skipping to change at page 15, line 44
n = (193.35-193.1)/0.05 = 5 n = (193.35-193.1)/0.05 = 5
10. Appendix B. CWDM Example 10. Appendix B. CWDM Example
The network displayed in figure 1 can be used also to display an The network displayed in figure 1 can be used also to display an
example of signaling using the Wavelength Label in a CWDM example of signaling using the Wavelength Label in a CWDM
environment. environment.
This time the signaling of an LSP from Node 4 to Node 7 is This time the signaling of an LSP from Node 4 to Node 7 is
considered. Such LSP exploits the CWDM ITU-T grid with a 20nm channel considered. Such LSP exploits the CWDM ITU-T grid with a 20nm
spacing and is to established using wavelength equal to 1331 nm. channel spacing and is to established using wavelength equal to
1331 nm.
Node 4 signals the LSP via a Path message including a Wavelength Node 4 signals the LSP via a Path message including a Wavelength
Label structured as defined in section 4.3: Label structured as defined in section 3.3:
0 1 2 3 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 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Grid | C.S | Identifier | n | |Grid | C.S | Identifier | n |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Where: Where:
Grid = 2 : ITU-T CWDM grid Grid = 2 : ITU-T CWDM grid
 End of changes. 47 change blocks. 
167 lines changed or deleted 190 lines changed or added

This html diff was produced by rfcdiff 1.40. The latest version is available from http://tools.ietf.org/tools/rfcdiff/