draft-ietf-ccamp-gmpls-g-694-lambda-labels-05.txt   draft-ietf-ccamp-gmpls-g-694-lambda-labels-06.txt 
Network Working Group Tomohiro Otani Network Working Group Tomohiro Otani
Internet Draft Takehiro Tsuritani Internet Draft Takehiro Tsuritani
Updates: RFC3471 KDDI Updates: RFC3471 KDDI
Category: Standards Track Dan Li Category: Standards Track Dan Li
Huawei Huawei
Expires: June 2010 December 7, 2009 Expires: September 2010 March 19, 2010
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-05.txt draft-ietf-ccamp-gmpls-g-694-lambda-labels-06.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 the
provisions of BCP 78 and BCP 79. 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 Task Force (IETF), its areas, and its working groups. Note that
other 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 months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." 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 September 19, 2010.
Copyright Notice Copyright Notice
Copyright (c) 2009 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 in effect on the date of Provisions Relating to IETF Documents
publication of this document (http://trustee.ietf.org/license-info). (http://trustee.ietf.org/license-info) in effect on the date of
Please review these documents carefully, as they describe your rights publication of this document. Please review these documents
and restrictions with respect to this document. carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
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 has
been developed and is currently being deployed. However, [RFC3471] been developed and is currently being deployed. However, [RFC3471]
has defined that a wavelength label (section 3.2.1.1) "only has has defined that a wavelength label (section 3.2.1.1) "only has
significance between two neighbors" and global wavelength continuity significance between two neighbors" and global wavelength continuity
is not considered. In order to achieve interoperability in a network is not considered. In order to achieve interoperability in a network
composed of next generation lambda switch-capable equipment, this composed of next generation lambda switch-capable equipment, this
skipping to change at page 2, line 35 skipping to change at page 2, line 35
document are to be interpreted as described in [RFC2119]. document are to be interpreted as described in [RFC2119].
Table of Contents Table of Contents
1. Introduction..................................................2 1. Introduction..................................................2
2. Assumed network model and related problem statement...........3 2. Assumed network model and related problem statement...........3
3. Label Related Formats.........................................6 3. Label Related Formats.........................................6
3.1. Wavelength Labels........................................6 3.1. Wavelength Labels........................................6
3.2. DWDM Wavelength Label....................................7 3.2. DWDM Wavelength Label....................................7
3.3. CWDM Wavelength Label....................................8 3.3. CWDM Wavelength Label....................................8
4. Security Considerations.......................................9 4. Security Considerations......................................10
5. IANA Considerations...........................................9 5. IANA Considerations..........................................10
6. Acknowledgments..............................................10 6. Acknowledgments..............................................10
7. References...................................................10 7. References...................................................10
7.1. Normative References....................................10 7.1. Normative References....................................10
7.2. Informative References..................................10 7.2. Informative References..................................11
8. Author's Address.............................................11 8. Author's Address.............................................12
9. Appendix A. DWDM Example.....................................12 9. Appendix A. DWDM Example.....................................13
10. Appendix B. CWDM Example....................................12 10. Appendix B. CWDM Example....................................13
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)
skipping to change at page 4, line 5 skipping to change at page 4, line 5
signaling. The way the Constrained Shortest Path First (CSPF) is signaling. The way the Constrained Shortest Path First (CSPF) is
performed is outside the scope of this document. performed is outside the scope of this document.
It is needless to say, a LSP must be appropriately provisioned It is needless to say, a 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 also
over multiple domains satisfying wavelength constraints. 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 A
and Domain B. 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+-+ |
|| || | +++++++++ +-+ +-+ +++++++++ || || | +++++++++ +-+ +-+ +++++++++
|| Node-3 || | ||||||| ||||||| || Node-3 || | ||||||| |||||||
|| +--------+ || | +++++++++ +++++++++ || +--------+ || | +++++++++ +++++++++
||===| WXC +===|| | | DWDM | | DWDM | ||===| WXC +===|| | | DWDM | | DWDM |
| (LSC) | | +--++---+ +--++---+ | (LSC) | | +--++---+ +--++---+
||===+ +===|| | || || ||===+ +===|| | || ||
|| +--------+ || | +--++---+ +--++---+ || +--------+ || | +--++---+ +--++---+
|| || | | DWDM | | DWDM | || || | | DWDM | | DWDM |
+--------+ +--------+ | +++++++++ +++++++++ +--------+ +--------+ | +++++++++ +++++++++
| ROADM | | ROADM | | ||||||| ||||||| | ROADM | | ROADM | | ||||||| |||||||
| or WXC +========+ or WXC +=+ | +-+ +++++++++ +-+ +-+ +++++++++ | or WXC +========+ or WXC +=+ | +-+ +++++++++ +-+ +-+ +++++++++
| (LSC) | | (LSC) | | | |D|-| PXC +-+D| |D+-+ PXC | | (LSC) | | (LSC) | | | |D|-| PXC +-+D| |D+-+ PXC |
+--------+ +--------+ +=|==+W|-| +-+W+=====+W+-+ | +--------+ +--------+ +=|==+W|-| +-+W+=====+W+-+ |
Node-4 Node-5 | |D|-| (LSC) +-+D| |D+-+ (LSC) | Node-4 Node-5 | |D|-| (LSC) +-+D| |D+-+ (LSC) |
| |M|-| +-+M| |M+-+ | | |M|-| +-+M| |M+-+ |
| +-+ +-------+ +-+ +-+ +-------+ | +-+ +-------+ +-+ +-+ +-------+
| Node-8 Node-9 | Node-8 Node-9
Figure 1 Wavelength-based network model Figure 1 Wavelength-based network model
+-------------------------------------------------------------+ +-------------------------------------------------------------+
| Domain A | Domain B | | Domain A | Domain B |
| | | | | |
| +---+ lambda 1 | +---+ | | +---+ lambda 1 | +---+ |
| | |---------------|---------| | | | | |---------------|---------| | |
| WDM | N | lambda 2 | | N | WDM | | WDM | N | lambda 2 | | N | WDM |
| =====| O |---------------|---------| O |===== | | =====| O |---------------|---------| O |===== |
| O | D | . | | D | O | | O | D | . | | D | O |
| T WDM | E | . | | E | WDM T | | T WDM | E | . | | E | WDM T |
| H =====| 2 | lambda n | | 6 |===== H | | H =====| 2 | lambda n | | 6 |===== H |
| E | |---------------|---------| | E | | E | |---------------|---------| | E |
| R +---+ | +---+ R | | R +---+ | +---+ R |
| | | | | |
| N +---+ | +---+ N | | N +---+ | +---+ N |
| O | | | | | O | | O | | | | | O |
| D WDM | N | | | N | WDM D | | D WDM | N | | | N | WDM D |
| E =====| O | WDM | | O |===== E | | E =====| O | WDM | | O |===== E |
| S | D |=========================| D | S | | S | D |=========================| D | S |
| 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. In order bidirectional LSP from ingress switch 1 to egress switch 9. In order
to satisfy wavelength continuity constraint, a fixed wavelength to satisfy wavelength continuity constraint, a fixed wavelength
(lambda 1) needs to be used in domain A and domain B. A Path message (lambda 1) needs to be used in domain A and domain B. A Path message
will be used for the signaling, the PATH message must contain the will be used for the signaling, the PATH message must contain the
upstream label and a label set object; both containing the same upstream label and a label set object; both containing the same
lambda. The label set object is made by only one sub channel that lambda. The label set object is made by only one sub channel that
skipping to change at page 7, line 24 skipping to change at page 7, line 24
, 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, so
an index is not appropriate in this case. an index is not appropriate in this case.
3.2. DWDM Wavelength Label 3.2. DWDM Wavelength Label
For the case of DWDM, the information carried in a Wavelength label For the case of DWDM, the information carried in a Wavelength label
is: 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 | Reserved | n | |Grid | C.S | Identifier | n |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
(1) Grid: 3 bits (1) Grid: 3 bits
The value for grid is set to 1 for ITU-T DWDM Grid as defined in The value for grid is set to 1 for ITU-T DWDM Grid as defined in
[G.694.1]. [G.694.1].
+----------+---------+ +----------+---------+
| Grid | Value | | Grid | Value |
+----------+---------+ +----------+---------+
| Reserved | 0 | | Reserved | 0 |
+----------+---------+ +----------+---------+
|ITU-T DWDM| 1 | |ITU-T DWDM| 1 |
+----------+---------+ +----------+---------+
|ITU-T CWDM| 2 | |ITU-T CWDM| 2 |
+----------+---------+ +----------+---------+
|Future use| 3 - 7 | |Future use| 3 - 7 |
+----------+---------+ +----------+---------+
(2) C.S.(channel spacing): 4 bits (2) C.S.(channel spacing): 4 bits
DWDM channel spacing is defined as follows. DWDM channel spacing is defined as follows.
+----------+---------+ +----------+---------+
| C.S(GHz) | Value | | C.S(GHz) | Value |
+----------+---------+ +----------+---------+
| Reserved | 0 | | Reserved | 0 |
+----------+---------+ +----------+---------+
| 100 | 1 | | 100 | 1 |
+----------+---------+ +----------+---------+
| 50 | 2 | | 50 | 2 |
+----------+---------+ +----------+---------+
| 25 | 3 | | 25 | 3 |
+----------+---------+ +----------+---------+
| 12.5 | 4 | | 12.5 | 4 |
+----------+---------+ +----------+---------+
|Future use| 5 - 15 | |Future use| 5 - 15 |
+----------+---------+ +----------+---------+
(3) n: 16 bits (3) Identifier: 9 bits
The identifier field is a per-node assigned and scoped value. This
field MAY change on a per-hop basis. In all cases but one, a node MAY
select any value, including zero (0), for this field. Once selected,
the value MUST NOT change until the LSP is torn down and the value
MUST be used 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
corresponding LSP.
(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 or a
positive value. The value used to compute the frequency as shown positive value. The value used to compute the frequency as shown
above. above.
3.3. CWDM Wavelength Label 3.3. CWDM Wavelength Label
For the case of CWDM, the information carried in a Wavelength label For the case of CWDM, the information carried in a Wavelength label
is: 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 | Reserved | 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 that of
DWDM case. 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 |
+----------+---------+ +----------+---------+
|ITU-T DWDM| 1 | |ITU-T DWDM| 1 |
+----------+---------+ +----------+---------+
|ITU-T CWDM| 2 | |ITU-T CWDM| 2 |
+----------+---------+ +----------+---------+
|Future use| 3 - 7 | |Future use| 3 - 7 |
+----------+---------+ +----------+---------+
(2) C.S.(channel spacing): 4 bits (2) C.S.(channel spacing): 4 bits
CWDM channel spacing is defined as follows. CWDM channel spacing is defined as follows.
+----------+---------+ +----------+---------+
| C.S(nm) | Value | | C.S(nm) | Value |
+----------+---------+ +----------+---------+
| Reserved | 0 | | Reserved | 0 |
+----------+---------+ +----------+---------+
| 20 | 1 | | 20 | 1 |
+----------+---------+ +----------+---------+
|Future use| 2 - 15 | |Future use| 2 - 15 |
+----------+---------+ +----------+---------+
(3) n: 16 bits (3) Identifier: 9 bits
The identifier field is a per-node assigned and scoped value. This
field MAY change on a per-hop basis. In all cases but one, a node MAY
select any value, including zero (0), for this field. Once selected,
the value MUST NOT change until the LSP is torn down and the value
MUST be used 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
corresponding LSP.
(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.
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 label
as above needs to be defined. as above needs to be defined.
4. Security Considerations 4. Security Considerations
This document introduces no new security considerations to [RFC3473]. This document introduces no new security considerations to [RFC3473].
GMPLS security is described in section 11 of [RFC3471] and refers to GMPLS security is described in section 11 of [RFC3471] and refers to
[RFC3209] for RSVP-TE. [RFC3209] for RSVP-TE.
5. IANA Considerations 5. IANA Considerations
This document has no actions for IANA. This document has no actions for IANA.
6. Acknowledgments 6. Acknowledgments
The authors would like to thank Adrian Farrel, Lawrence Mao, Zafar The authors would like to thank Adrian Farrel, Lou Berger, Lawrence
Ali and Daniele Ceccarelli for the discussion and their comments. Mao, Zafar Ali and Daniele Ceccarelli for the discussion 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.
[RFC3209] Awduche, D., Berger, L., Gan, D., Li, T., Srinivasan, V., [RFC3209] Awduche, D., Berger, L., Gan, D., Li, T., Srinivasan, V.,
and G. Swallow, "RSVP-TE: Extensions to RSVP for LSP and G. Swallow, "RSVP-TE: Extensions to RSVP for LSP
Tunnels", RFC 3209, December 2001. Tunnels", RFC 3209, December 2001.
[RFC3471] Berger, L., "Generalized Multi-Protocol Label Switching [RFC3471] Berger, L., "Generalized Multi-Protocol Label Switching
(MPLS) Signaling Functional Description", RFC 3471, (MPLS) Signaling Functional Description", RFC 3471, January
January 2003. 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 Switching
(GMPLS) Architecture", RFC 3945, October 2004. (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.
8. Author's Address 8. Author's Address
Tomohiro Otani Tomohiro Otani
KDDI Corporation KDDI Corporation
2-3-2 Nishishinjuku Shinjuku-ku Tokyo, 163-8003, Japan 2-3-2 Nishishinjuku Shinjuku-ku Tokyo, 163-8003, Japan
Phone: +81-3-3347-6006 Phone: +81-3-3347-6006
Email: tm-otani@kddi.com Email: tm-otani@kddi.com
Takehiro Tsuritani Takehiro Tsuritani
skipping to change at page 12, line 17 skipping to change at page 13, line 17
Considering the network displayed in figure 1 it is possible to show Considering the network displayed in figure 1 it is possible to show
an example of LSP set up using the lambda labels. 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 to
Node 9. The ITU-T grid to be used is the DWDM one, the channel 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 4.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 | Reserved | n | |Grid | C.S |R| Identifier | n |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Where: Where:
Grid = 1 : ITU-T DWDM grid Grid = 1 : ITU-T DWDM grid
C.S. = 2 : 50 GHz channel spacing C.S. = 2 : 50 GHz channel spacing
n = 5 : n = 5 :
Frequency (THz) = 193.1 THz + n * channel spacing (THz) Frequency (THz) = 193.1 THz + n * channel spacing (THz)
skipping to change at page 13, line 5 skipping to change at page 14, line 5
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 environment. example of signaling using the Wavelength Label in a CWDM environment.
This time the signaling of an LSP from Node 4 to Node 7 is considered. 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 spacing and Such LSP exploits the CWDM ITU-T grid with a 20nm channel spacing and
is to established using wavelength equal to 1331 nm. 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 4.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 | Reserved | n | |Grid | C.S |R| Identifier | n |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Where: Where:
Grid = 2 : ITU-T CWDM grid Grid = 2 : ITU-T CWDM grid
C.S. = 1 : 20 nm channel spacing C.S. = 1 : 20 nm channel spacing
n = -7 : n = -7 :
Wavelength (nm) = 1471 nm + n * 20 nm Wavelength (nm) = 1471 nm + n * 20 nm
 End of changes. 29 change blocks. 
145 lines changed or deleted 179 lines changed or added

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