draft-ietf-ccamp-gmpls-signaling-g709v3-08.txt   draft-ietf-ccamp-gmpls-signaling-g709v3-09.txt 
Network Working Group Fatai Zhang, Ed. Network Working Group Fatai Zhang, Ed.
Internet Draft Huawei Internet Draft Huawei
Updates: 4328 Guoying Zhang Updates: 4328 Guoying Zhang
Category: Standards Track CATR Category: Standards Track CATR
Sergio Belotti Sergio Belotti
Alcatel-Lucent Alcatel-Lucent
D. Ceccarelli D. Ceccarelli
Ericsson Ericsson
Khuzema Pithewan Khuzema Pithewan
Infinera Infinera
Expires: October 8, 2013 April 8, 2013 Expires: November 31, 2013 May 31, 2013
Generalized Multi-Protocol Label Switching (GMPLS) Signaling Generalized Multi-Protocol Label Switching (GMPLS) Signaling
Extensions for the evolving G.709 Optical Transport Networks Control Extensions for the evolving G.709 Optical Transport Networks Control
draft-ietf-ccamp-gmpls-signaling-g709v3-08.txt draft-ietf-ccamp-gmpls-signaling-g709v3-09.txt
Status of this Memo Status of this Memo
This Internet-Draft is submitted to IETF in full conformance with This Internet-Draft is submitted to IETF in full conformance with
the 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 Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
skipping to change at page 1, line 40 skipping to change at page 1, line 40
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 October 8, 2013. This Internet-Draft will expire on November 31, 2013.
Abstract Abstract
ITU-T Recommendation G.709 [G709-2012] has introduced new Optical ITU-T Recommendation G.709 [G709-2012] has introduced new Optical
channel Data Unit (ODU) containers (ODU0, ODU4, ODU2e and ODUflex) channel Data Unit (ODU) containers (ODU0, ODU4, ODU2e and ODUflex)
and enhanced Optical Transport Networking (OTN) flexibility. and enhanced Optical Transport Networking (OTN) flexibility.
This document updates RFC4328 to provide the extensions to the This document updates RFC4328 to provide the extensions to the
Generalized Multi-Protocol Label Switching (GMPLS) signaling to Generalized Multi-Protocol Label Switching (GMPLS) signaling to
control the evolving OTN addressing ODUk multiplexing and new control the evolving OTN addressing ODUk multiplexing and new
skipping to change at page 2, line 24 skipping to change at page 2, line 24
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
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 .................................................. 3 1. Introduction .................................................. 3
2. Terminology ................................................... 3 2. Terminology ................................................... 3
3. GMPLS Extensions for the Evolving G.709 - Overview ............ 3 3. GMPLS Extensions for the Evolving G.709 - Overview ............ 3
4. Generalized Label Request ..................................... 4 4. Generalized Label Request ..................................... 4
5. Extensions for Traffic Parameters for the Evolving G.709 ...... 6 5. Extensions for Traffic Parameters for the Evolving G.709 ...... 6
5.1. Usage of ODUflex(CBR) Traffic Parameters ................. 7 5.1. Usage of ODUflex(CBR) Traffic Parameters ................. 8
5.2. Usage of ODUflex(GFP) Traffic Parameters ................ 10 5.2. Usage of ODUflex(GFP) Traffic Parameters ................ 10
5.3. Notification on Errors of OTN-TDM Traffic Parameters .... 10 5.3. Notification on Errors of OTN-TDM Traffic Parameters .... 10
6. Generalized Label ............................................ 11 6. Generalized Label ............................................ 11
6.1. OTN-TDM Switching Type Generalized Label ................ 11 6.1. OTN-TDM Switching Type Generalized Label ................ 11
6.2. Procedures .............................................. 13 6.2. Procedures .............................................. 14
6.2.1. Notification on Label Error ........................ 15 6.2.1. Notification on Label Error ........................ 15
6.3. Supporting Virtual Concatenation and Multiplication ..... 16 6.3. Supporting Virtual Concatenation and Multiplication ..... 16
6.4. Examples ................................................ 16 6.4. Examples ................................................ 17
7. Supporting Hitless Adjustment of ODUflex (GFP) ............... 18 7. Supporting Hitless Adjustment of ODUflex (GFP) ............... 18
8. Control Plane Backward Compatibility Considerations........... 19 8. Control Plane Backward Compatibility Considerations........... 19
9. Security Considerations ...................................... 20 9. Security Considerations ...................................... 20
10. IANA Considerations.......................................... 20 10. IANA Considerations.......................................... 20
11. References .................................................. 21 11. References .................................................. 22
11.1. Normative References ................................... 21 11.1. Normative References ................................... 22
11.2. Informative References ................................. 22 11.2. Informative References ................................. 23
12. Contributors ................................................ 23 12. Contributors ................................................ 23
13. Authors' Addresses .......................................... 24 13. Authors' Addresses .......................................... 24
14. Acknowledgment .............................................. 26 14. Acknowledgment .............................................. 26
1. Introduction 1. Introduction
With the evolution and deployment of OTN technology, it is necessary With the evolution and deployment of OTN technology, it is necessary
that appropriate enhanced control technology support be provided for that appropriate enhanced control technology support be provided for
[G709-2012]. [G709-2012].
skipping to change at page 5, line 7 skipping to change at page 5, line 7
This document follows these extensions and a new Switching Type is This document follows these extensions and a new Switching Type is
introduced to indicate the ODUk switching capability [G709-2012] in introduced to indicate the ODUk switching capability [G709-2012] in
order to support backward compatibility with [RFC4328], as described order to support backward compatibility with [RFC4328], as described
in [OTN-FWK]. The new Switching Type (OTN-TDM Switching Type) is in [OTN-FWK]. The new Switching Type (OTN-TDM Switching Type) is
defined in [OTN-OSPF]. defined in [OTN-OSPF].
This document also updates the G-PID values defined in [RFC4328]: This document also updates the G-PID values defined in [RFC4328]:
Value G-PID Type Value G-PID Type
----- ---------- ----- ----------
47 ODU-2.5G: Transport of Digital Paths (e.g., at 2.5, 10 and 47 Type field updated from "G.709 ODUj" to "ODU-2.5G" to
40 Gbps) via 2.5Gbps TSG indicates transport of Digital Paths (e.g., at 2.5, 10 and
40 Gbps) via 2.5Gbps TSG
49 CBRa: Asynchronous Constant Bit Rate (CBR) (e.g.,
mapping of CBR2G5, CBR10G and CBR40G)
50 CBRb: Bit synchronous Constant Bit Rate (e.g., mapping
of CBR2G5, CBR10G, CBR40G, CBR10G3 and supra-
2.488 CBR Gbit/s signal (carried by OPUflex))
32 ATM: Mapping of Asynchronous Transfer Mode (ATM) cell
stream (e.g., at 1.25, 2.5, 10 and 40 Gbps)
51 BSOT: Non-specific client Bit Stream with Octet Timing
(e.g., Mapping of 1.25, 2.5, 10, 40 and 100 Gbps
Bit Stream)
52 BSNT: Non-specific client Bit Stream without Octet 56 Type field updated from "ESCON" to "SBCON/ESCON" to align
Timing (e.g., Mapping of 1.25, 2.5, 10, 40 and with [G709-2012] payload type 0x1A.
100 Gbps Bit Stream)
Note: Values 32, 47, 49 and 50 include mapping of Synchronous Digital Note: Value 47 includes mapping of Synchronous Digital Hierarchy
Hierarchy (SDH). (SDH).
In the case of ODU multiplexing, the Lower Order ODU (LO ODU) (i.e., In the case of ODU multiplexing, the Lower Order ODU (LO ODU) (i.e.,
the client signal) may be multiplexed into Higher Order ODU (HO ODU) the client signal) may be multiplexed into Higher Order ODU (HO ODU)
via 1.25G TSG, 2.5G TSG or any one of them (i.e., TSG via 1.25G TSG, 2.5G TSG or any one of them (i.e., TSG
Auto_Negotiation is enabled). Since the G-PID type "ODUk" defined in Auto_Negotiation is enabled). Since the G-PID type "ODUk" defined in
[RFC4328] is only used for 2.5Gbps TSG, two new G-PID types are [RFC4328] is only used for 2.5Gbps TSG, two new G-PID types are
defined as follows: defined as follows:
- ODU-1.25G: Transport of Digital Paths at 1.25, 2.5, 10, 40 and 100 - ODU-1.25G: Transport of Digital Paths at 1.25, 2.5, 10, 40 and 100
Gbps via 1.25Gbps TSG Gbps via 1.25Gbps TSG
- ODU-any: Transport of Digital Paths at 1.25, 2.5, 10, 40 and 100 - ODU-any: Transport of Digital Paths at 1.25, 2.5, 10, 40 and 100
Gbps via 1.25 or 2.5Gbps TSG (i.e., the fallback Gbps via 1.25 or 2.5Gbps TSG (i.e., the fallback
procedure is enabled and the default value of 1.25Gbps procedure is enabled and the default value of 1.25Gbps
TSG can be fallen back to 2.5Gbps if needed) TSG can be fallen back to 2.5Gbps if needed)
In addition, some other new G-PID types are defined to support other The full list of payload types defined in [G709-2012] and their
new client signals described in [G709-2012]: mapping to existing and new G-PID types are as follows:
- CBRc: Mapping of constant bit-rate signals with justification
into OPUk (k = 0, 1, 2, 3, 4) via Generic Mapping
Procedure (GMP) (i.e., mapping of sub-1.238, supra-
1.238 to sub-2.488, close-to 9.995, close-to 40.149
and close-to 104.134 Gbit/s CBR client signal)
- 1000BASE-X: Mapping of a 1000BASE-X signal via timing transparent
transcoding into OPU0
- FC-1200: Mapping of a FC-1200 signal via timing transparent
transcoding into OPU2e
The following table summarizes the new G-PID values with respect to G.709
the LSP Encoding Type: Payload
Type G-PID Type/Comment LSP Encoding
==== ===== ===================== ===================
0x01 No standard value
0x02 49 CBRa G.709 ODUk
0x03 50 CBRb G.709 ODUk
0x04 32 ATM G.709 ODUk
0x05 59(TBA) Framed GFP G.709 ODUk
54 Ethernet MAC (framed GFP) G.709 ODUk
70(TBA) 64B/66B GFP-F Ethernet G.709 ODUk (k=2)
0x06 Not signaled
0x07 55 Ethernet PHY G.709 ODUk (k=0,3,4)
(transparent GFP)
0x08 58 Fiber Channel G.709 ODUk (k=2e)
0x09 59(TBA) Framed GFP G.709 ODUk (k=2)
70(TBA) 64B/66B GFP-F Ethernet G.709 ODUk (k=2)
Value G-PID Type LSP Encoding Type 0x0A 60(TBA) STM-1 G.709 ODUk (k=0)
----- ---------- ----------------- 0x0B 61(TBA) STM-4 G.709 ODUk (k=0)
59(TBA) G.709 ODU-1.25G G.709 ODUk 0x0C 58 Fiber Channel G.709 ODUk (k=0)
60(TBA) G.709 ODU-any G.709 ODUk 0x0D 58 Fiber Channel G.709 ODUk (k=1)
61(TBA) CBRc G.709 ODUk 0x0E 58 Fiber Channel G.709 ODUflex
62(TBA) 1000BASE-X G.709 ODUk (k=0) 0x0F 58 Fiber Channel G.709 ODUflex
63(TBA) FC-1200 G.709 ODUk (k=2e) 0x10 51 BSOT G.709 ODUk
0x11 52 BSNT G.709 ODUk
0x12 62(TBA) InfiniBand G.709 ODUflex
0x13 62(TBA) InfiniBand G.709 ODUflex
0x14 62(TBA) InfiniBand G.709 ODUflex
0x15 63(TBA) Serial Digital Interface G.709 ODUk (k=0)
0x16 64(TBA) Serial Digital G.709 ODUk (k=1)
Interface/1.001
0x17 63(TBA) Serial Digital Interface G.709 ODUk (k=1)
0x18 64(TBA) Serial Digital G.709 ODUflex
Interface/1.001
0x19 63(TBA) Serial Digital Interface G.709 ODUflex
0x1A 56 SBCON/ESCON G.709 ODUk (k=0)
(IANA to update Type field)
0x1B 65(TBA) DVB_ASI G.709 ODUk (k=0)
0x1C 58 Fiber Channel G.709 ODUk
0x20 47 G.709 ODU-2.5G G.709 ODUk (k=2,3)
(IANA to update Type field)
66(TBA) G.709 ODU-1.25G G.709 ODUk (k=1)
0x21 66(TBA) G.709 ODU-1.25G G.709 ODUk (k=2,3,4)
67(TBA) G.709 ODU-Any G.709 ODUk (k=2,3)
0x55 No standard value
0x66 No standard value
0x80-0x8F No standard value
0xFD 68(TBA) Null Test G.709 ODUk
0xFE 69(TBA) Random Test G.709 ODUk
0xFF No standard value
Note: Values 59 and 60 include mapping of SDH. Note: Values 59 and 70 include mapping of SDH.
Note that the mapping types for ODUj into OPUk are unambiguously per Note that the mapping types for ODUj into OPUk are unambiguously per
Table 7-10 of [G709-2012], so it does not need to carry mapping type Table 7-10 of [G709-2012], so it does not need to carry mapping type
information in the signaling. information in the signaling.
Note also that additional information on G.709 client mapping can be
found in [G7041].
5. Extensions for Traffic Parameters for the Evolving G.709 5. Extensions for Traffic Parameters for the Evolving G.709
The Traffic Parameters for OTN-TDM capable Switching Type are carried The Traffic Parameters for OTN-TDM capable Switching Type are carried
in the OTN-TDM SENDER_TSPEC and FLOWSPEC objects. The objects have in the OTN-TDM SENDER_TSPEC and FLOWSPEC objects. The objects have
the following class and type: the following class and type:
- OTN-TDM SENDER_TSPEC Object: Class = 12, C-Type = 7 (TBA) - OTN-TDM SENDER_TSPEC Object: Class = 12, C-Type = 7 (TBA)
- OTN-TDM FLOWSPEC Object: Class = 9, C-Type = 7 (TBA) - OTN-TDM FLOWSPEC Object: Class = 9, C-Type = 7 (TBA)
The format of Traffic Parameters in these two objects is defined as The format of Traffic Parameters in these two objects is defined as
skipping to change at page 13, line 6 skipping to change at page 13, line 30
| |ODU2e &|1~32|ODU2es and ODUflexes' TPNs | | |ODU2e &|1~32|ODU2es and ODUflexes' TPNs |
| |ODUflex| | | | |ODUflex| | |
+-------+-------+----+----------------------------------------------+ +-------+-------+----+----------------------------------------------+
| ODU4 |Any ODU|1~80|Flexible, != ANY other existing LO ODUs' TPNs | | ODU4 |Any ODU|1~80|Flexible, != ANY other existing LO ODUs' TPNs |
+-------+-------+----+----------------------------------------------+ +-------+-------+----+----------------------------------------------+
Note that in the case of "Flexible", the value of TPN MAY not be Note that in the case of "Flexible", the value of TPN MAY not be
corresponding to the TS number as per [G709-2012]. corresponding to the TS number as per [G709-2012].
Length (12 bits): indicates the number of bits of the Bit Map field, Length (12 bits): indicates the number of bits of the Bit Map field,
i.e., the total number of TS in the HO ODUk link. The valid values i.e., the total number of TS in the HO ODUk link. The TS granularity,
for this field are 0, 2, 4, 8, 16, 32 and 80. 1.25Gbps or 2.5Gbps, may be derived by dividing the HO ODUk link's
rate by the value of the Length field. In the context of [G709-2012],
the values of 4 and 16 indicate a TS granularity of 2.5Gps, and the
values 2, 8, 32 and 80 indicate a TS granularity of 1.25Gps.
In case of an ODUk mapped into OTUk, there is no need to indicate In case of an ODUk mapped into OTUk, there is no need to indicate
which tributary slots will be used, so the length field MUST be set which tributary slots will be used, so the length field MUST be set
to 0. to 0.
Bit Map (variable): indicates which tributary slots in HO ODUk that Bit Map (variable): indicates which tributary slots in HO ODUk that
the LO ODUj will be multiplexed into. The sequence of the Bit Map is the LO ODUj will be multiplexed into. The sequence of the Bit Map is
consistent with the sequence of the tributary slots in HO ODUk. Each consistent with the sequence of the tributary slots in HO ODUk. Each
bit in the bit map represents the corresponding tributary slot in HO bit in the bit map represents the corresponding tributary slot in HO
ODUk with a value of 1 or 0 indicating whether the tributary slot ODUk with a value of 1 or 0 indicating whether the tributary slot
skipping to change at page 14, line 25 skipping to change at page 15, line 6
reserved tributary slots in the ODUk by its downstream neighbor reserved tributary slots in the ODUk by its downstream neighbor
node according to the position of the bits that are set to 1 in node according to the position of the bits that are set to 1 in
the Bit Map field. The node determines the TS type (according to the Bit Map field. The node determines the TS type (according to
the total TS number of the ODUk, or pre-configured TS type), so the total TS number of the ODUk, or pre-configured TS type), so
that the node can multiplex the ODUj into the ODUk based on the TS that the node can multiplex the ODUj into the ODUk based on the TS
type. The node MUST also retrieve the TPN value assigned by its type. The node MUST also retrieve the TPN value assigned by its
downstream neighbor node from the label, and fill the TPN into the downstream neighbor node from the label, and fill the TPN into the
related MSI byte(s) in the OPUk overhead in the data plane, so related MSI byte(s) in the OPUk overhead in the data plane, so
that the downstream neighbor node can check whether the TPN that the downstream neighbor node can check whether the TPN
received from the data plane is consistent with the ExMSI and received from the data plane is consistent with the ExMSI and
determine whether there is any mismatch defect. Note that the determine whether there is any mismatch defect.
Length field in the label format MAY be used to indicate the TS
type of the HO ODUk (i.e., TS granularity at 1.25Gbps or 2.5Gbps)
since the HO ODUk type can be known from IF_ID RSVP_HOP Object. In
some cases when there is no Link Management Protocol (LMP) or
routing to make the two end points of the link to know the TSG,
the TSG information used by another end can be deduced from the
label format. For example, for HO ODU2 link, the value of the
length filed will be 4 or 8, which indicates the TS granularity is
2.5Gbps or 1.25Gbps, respectively.
- In case of ODUk to OTUk mapping, the size of Bit Map field MUST be - In case of ODUk to OTUk mapping, the size of Bit Map field MUST be
0 and no additional procedure is needed. 0 and no additional procedure is needed.
When a downstream node or egress node receives a Path message When a downstream node or egress node receives a Path message
containing Generalized Label Request object for setting up an ODUj containing Generalized Label Request object for setting up an ODUj
LSP from its upstream neighbor node, the node MUST generate an OTN- LSP from its upstream neighbor node, the node MUST generate an OTN-
TDM label according to the Signal Type of the requested LSP and the TDM label according to the Signal Type of the requested LSP and the
free resources (i.e., free tributary slots of ODUk) that will be free resources (i.e., free tributary slots of ODUk) that will be
reserved for the LSP, and send the label to its upstream neighbor reserved for the LSP, and send the label to its upstream neighbor
skipping to change at page 20, line 16 skipping to change at page 20, line 34
This document introduces no new security considerations to the This document introduces no new security considerations to the
existing GMPLS signaling protocols. Referring to [RFC3473] and existing GMPLS signaling protocols. Referring to [RFC3473] and
[RFC4328], further details of the specific security measures are [RFC4328], further details of the specific security measures are
provided. Additionally, [RFC5920] provides an overview of security provided. Additionally, [RFC5920] provides an overview of security
vulnerabilities and protection mechanisms for the GMPLS control vulnerabilities and protection mechanisms for the GMPLS control
plane. plane.
10. IANA Considerations 10. IANA Considerations
Three RSVP C-Types are defined for OTN-TDM Traffic Parameters and Two RSVP C-Types are defined for OTN-TDM Traffic Parameters in this
OTN-TDM Generalized Label in this document: document:
http://www.iana.org/assignments/rsvp-parameters http://www.iana.org/assignments/rsvp-parameters
- OTN-TDM SENDER_TSPEC and FLOWSPEC objects: - OTN-TDM SENDER_TSPEC and FLOWSPEC objects:
o OTN-TDM SENDER_TSPEC Object: Class = 12, C-Type = 7 (see o OTN-TDM SENDER_TSPEC Object: Class = 12, C-Type = 7 (see
Section 5) Section 5)
o OTN-TDM FLOWSPEC Object: Class = 9, C-Type = 7 (see Section 5) o OTN-TDM FLOWSPEC Object: Class = 9, C-Type = 7 (see Section 5)
IANA maintains the "Generalized Multi-Protocol Label Switching IANA maintains the "Generalized Multi-Protocol Label Switching
(GMPLS) Signaling Parameters" registry (see (GMPLS) Signaling Parameters" registry (see
http://www.iana.org/assignments/gmpls-sig-parameters). "Generalized http://www.iana.org/assignments/gmpls-sig-parameters). "Generalized
PIDs (G-PID)" subregistry is included in this registry, which will be PIDs (G-PID)" subregistry is included in this registry, which will be
extended and updated by this document as below: extended and updated by this document as below:
- Generalized PID (G-PID): - Generalized PID (G-PID):
Name: G-PID Name: G-PID
skipping to change at page 20, line 36 skipping to change at page 21, line 11
IANA maintains the "Generalized Multi-Protocol Label Switching IANA maintains the "Generalized Multi-Protocol Label Switching
(GMPLS) Signaling Parameters" registry (see (GMPLS) Signaling Parameters" registry (see
http://www.iana.org/assignments/gmpls-sig-parameters). "Generalized http://www.iana.org/assignments/gmpls-sig-parameters). "Generalized
PIDs (G-PID)" subregistry is included in this registry, which will be PIDs (G-PID)" subregistry is included in this registry, which will be
extended and updated by this document as below: extended and updated by this document as below:
- Generalized PID (G-PID): - Generalized PID (G-PID):
Name: G-PID Name: G-PID
Format: 16-bit number Format: 16-bit number
Values: Values:
[0..31, 36..46] defined in [RFC3471] Value Type/Comment LSP Encoding/Technology
[32] defined in [RFC3471] and updated by Section 4 ======= ====================== =======================
[33..35] defined in [RFC3471] and updated by [RFC4328] 47 G.709 ODU-2.5G G.709 ODUk (k=2,3)
[47, 49..52] defined in [RFC4328] and updated by Section 4 (IANA to update Type field)
[48, 53..58] defined in [RFC4328] 56 SBCON/ESCON G.709 ODUk, Lambda, Fiber
[59..63] defined in Section 4 of this document (IANA to update Type field)
59(TBA) Framed GFP G.709 ODUk
Allocation Policy (as defined in [RFC4328]): 60(TBA) STM-1 G.709 ODUk (k=0)
61(TBA) STM-4 G.709 ODUk (k=0)
[0..31743] Assigned by IANA via IETF Standards Track RFC 62(TBA) InfiniBand G.709 ODUflex
Action. 63(TBA) Serial Digital Interface G.709 ODUk (k=0,1,flex)
[31744..32767] Assigned temporarily for Experimental Usage 64(TBA) Serial Digital Interface/1.001 G.709 ODUk (k=1,flex)
[32768..65535] Not assigned. Before any assignments can be 65(TBA) DVB_ASI G.709 ODUk (k=0)
made in this range, there MUST be a Standards 66(TBA) G.709 ODU-1.25G G.709 ODUk
Track RFC that specifies IANA Considerations 67(TBA) G.709 ODU-Any G.709 ODUk (k=2,3)
that covers the range being assigned. 68(TBA) Null Test G.709 ODUk
69(TBA) Random Test G.709 ODUk
70(TBA) 64B/66B GFP-F Ethernet G.709 ODUk (k=2)
"Signal Type" subregistry to the "Generalized Multi-Protocol Label "Signal Type" subregistry to the "Generalized Multi-Protocol Label
Switching (GMPLS) Signaling Parameters" will be defined by this Switching (GMPLS) Signaling Parameters" will be defined by this
document as below: document as below:
Value Signal Type Reference Value Signal Type Reference
----- ----------- --------- ----- ----------- ---------
0 Not significant [RFC4328] 0 Not significant [RFC4328]
1 ODU1 (i.e., 2.5 Gbps) [RFC4328] 1 ODU1 (i.e., 2.5 Gbps) [RFC4328]
2 ODU2 (i.e., 10 Gbps) [RFC4328] 2 ODU2 (i.e., 10 Gbps) [RFC4328]
skipping to change at page 22, line 40 skipping to change at page 23, line 18
RFC6344, August 2011. RFC6344, August 2011.
11.2. Informative References 11.2. Informative References
[OTN-FWK] Fatai Zhang et al, "Framework for GMPLS and PCE Control of [OTN-FWK] Fatai Zhang et al, "Framework for GMPLS and PCE Control of
G.709 Optical Transport Networks", Work in Progress: draft- G.709 Optical Transport Networks", Work in Progress: draft-
ietf-ccamp-gmpls-g709-framework, February 2013. ietf-ccamp-gmpls-g709-framework, February 2013.
[OTN-INFO] S. Belotti et al, "Information model for G.709 Optical [OTN-INFO] S. Belotti et al, "Information model for G.709 Optical
Transport Networks (OTN)", Work in Progress: draft-ietf- Transport Networks (OTN)", Work in Progress: draft-ietf-
ccamp-otn-g709-info-model, April 2013. ccamp-otn-g709-info-model, May 2013.
[OTN-OSPF] D. Ceccarelli et al, "Traffic Engineering Extensions to [OTN-OSPF] D. Ceccarelli et al, "Traffic Engineering Extensions to
OSPF for Generalized MPLS (GMPLS) Control of Evolving G.709 OSPF for Generalized MPLS (GMPLS) Control of Evolving G.709
OTN Networks", Work in Progress: draft-ietf-ccamp-gmpls- OTN Networks", Work in Progress: draft-ietf-ccamp-gmpls-
ospf-g709v3, April 2013. ospf-g709v3, April 2013.
[G709-2012] ITU-T, "Interfaces for the Optical Transport Network [G709-2012] ITU-T, "Interfaces for the Optical Transport Network
(OTN)", G.709/Y.1331 Recommendation, February 2012. (OTN)", G.709/Y.1331 Recommendation, February 2012.
[G7044] ITU-T, "Hitless adjustment of ODUflex", G.7044/Y.1347, [G7044] ITU-T, "Hitless adjustment of ODUflex", G.7044/Y.1347,
October 2011. October 2011.
[G7041] ITU-T, "Generic framing procedure", G.7041/Y.1303, April
2011.
[RFC4506] M. Eisler, Ed., "XDR: External Data Representation [RFC4506] M. Eisler, Ed., "XDR: External Data Representation
Standard", RFC 4506, May 2006. Standard", RFC 4506, May 2006.
[RFC5920] Fang, L., Ed., "Security Framework for MPLS and GMPLS [RFC5920] Fang, L., Ed., "Security Framework for MPLS and GMPLS
Networks", RFC5920, July 2010. Networks", RFC5920, July 2010.
[IEEE] "IEEE Standard for Binary Floating-Point Arithmetic", [IEEE] "IEEE Standard for Binary Floating-Point Arithmetic",
ANSI/IEEE Standard 754-1985, Institute of Electrical and ANSI/IEEE Standard 754-1985, Institute of Electrical and
Electronics Engineers, August 1985. Electronics Engineers, August 1985.
 End of changes. 25 change blocks. 
90 lines changed or deleted 105 lines changed or added

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