draft-ietf-ccamp-gmpls-g-694-lambda-labels-01.txt   draft-ietf-ccamp-gmpls-g-694-lambda-labels-02.txt 
INTERNET DRAFT Tomohiro Otani INTERNET DRAFT Tomohiro Otani
Updates: RFC 3471 KDDI R&D Labs Updates: RFC 3471 KDDI R&D Labs
Intended status: standard track (Editor) Intended status: standard track (Editor)
Expires: Nov. 27, 2008 May 27, 2008 Expires: Jan. 31, 2009 July 14, 2008
Generalized Labels for G.694 Lambda-Switching Capable Label Switching Generalized Labels for G.694 Lambda-Switching Capable Label Switching
Routers Routers
Document: draft-ietf-ccamp-gmpls-g-694-lambda-labels-01.txt Document: draft-ietf-ccamp-gmpls-g-694-lambda-labels-02.txt
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79. aware will be disclosed, in accordance with Section 6 of 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
skipping to change at page 2, line 14 skipping to change at page 2, line 14
Status of this Memo................................................ 1 Status of this Memo................................................ 1
Abstract........................................................... 1 Abstract........................................................... 1
1. Introduction.................................................... 3 1. Introduction.................................................... 3
2. Conventions used in this document............................... 3 2. Conventions used in this document............................... 3
3. Assumed network model and related problem statement............. 3 3. Assumed network model and related problem statement............. 3
4. Label Related Formats........................................... 5 4. Label Related Formats........................................... 5
5. Security consideration.......................................... 8 5. Security consideration.......................................... 8
6. Acknowledgement................................................. 8 6. Acknowledgement................................................. 8
7. References...................................................... 8 7. References...................................................... 8
7.1. Normative References.......................................... 8 7.1. Normative References.......................................... 8
7.2. Informative References........................................ 8 7.2. Informative References........................................ 9
Editor's address................................................... 9 Editor's address................................................... 9
Contributors' address.............................................. 9 Contributors' address.............................................. 9
Intellectual property considerations............................... 9 Intellectual property considerations.............................. 10
Copyright statement............................................... 10 Copyright statement............................................... 10
1. Introduction 1. Introduction
As described in [RFC3945], Generalized MPLS (GMPLS) extends MPLS from As described in [RFC3945], Generalized MPLS (GMPLS) extends MPLS from
supporting only packet (Packet Switching Capable - PSC) interfaces supporting only packet (Packet Switching Capable - PSC) interfaces
and switching to also include support for four new classes of and switching to also include support for four new classes of
interfaces and switching: 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)
skipping to change at page 6, line 42 skipping to change at page 6, line 42
an index is not appropriate in this case. an index is not appropriate in this case.
4.2 DWDM Wavelength Label 4.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 |S| Reserved | n | |Grid | C.S | Reserved | 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 |
+----------+---------+ +----------+---------+
skipping to change at page 7, line 25 skipping to change at page 7, line 25
+----------+---------+ +----------+---------+
| 25 | 2 | | 25 | 2 |
+----------+---------+ +----------+---------+
| 50 | 3 | | 50 | 3 |
+----------+---------+ +----------+---------+
| 100 | 4 | | 100 | 4 |
+----------+---------+ +----------+---------+
|Future use| 5 - 15 | |Future use| 5 - 15 |
+----------+---------+ +----------+---------+
(3) S: 1 bit (3) n: 17 bits
Sign for the value of n, set to 1 for (-) and 0 for (+)
(4) n: 16 bits
n is an integer to take either a negative, zero or a positive value.
The value used to compute the frequency as shown above. The value used to compute the frequency as shown above.
4.3 CWDM Wavelength Label 4.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 | Reserved | n | |Grid | C.S | Reserved | n |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The structure of the label in the case of CWDM is the same as 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 |
+----------+---------+ +----------+---------+
|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) Lambda: 8 bits (2) C.S.(channel spacing): 4 bits
The value used to compute the wavelength as shown above. CWDM channel spacing is defined as follows.
+----------+---------+
| C.S(nm) | Value |
+----------+---------+
| 20 | 1 |
+----------+---------+
|Future use| 2 - 15 |
+----------+---------+
(3) n: 17 bits
n is an integer. The value used to compute the 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.
5. Security consideration 5. Security consideration
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.
6. Acknowledgement 6. Acknowledgement
The authors would like to thank Adrian Farrel, Lawrence Mao and Zafar The authors would like to thank Adrian Farrel, Lawrence Mao, Zafar
Ali for the discussion. Ali and Dan Li for the discussion.
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 Tunnels", RFC and G. Swallow, "RSVP-TE: Extensions to RSVP for LSP Tunnels", RFC
 End of changes. 12 change blocks. 
15 lines changed or deleted 28 lines changed or added

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