draft-ietf-ccamp-gmpls-signaling-g709v3-06.txt   draft-ietf-ccamp-gmpls-signaling-g709v3-07.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: July 24, 2013 January 24, 2013 Expires: August 21, 2013 February 21, 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-06.txt draft-ietf-ccamp-gmpls-signaling-g709v3-07.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 July 24, 2013. This Internet-Draft will expire on August 21, 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 6, line 41 skipping to change at page 6, line 41
- 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
follows: follows:
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Signal Type | N | Tolerance | | Signal Type | Reserved | Tolerance |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| NVC | Multiplier (MT) | | NVC | Multiplier (MT) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Bit_Rate | | Bit_Rate |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Signal Type: 8 bits Signal Type: 8 bits
As defined in [RFC4328] Section 3.2.1, with the following As defined in [RFC4328] Section 3.2.1, with the following
additional values: additional values:
skipping to change at page 7, line 20 skipping to change at page 7, line 20
9 OCh at 100 Gbps 9 OCh at 100 Gbps
10 ODU0 (i.e., 1.25 Gbps) 10 ODU0 (i.e., 1.25 Gbps)
11 ODU2e (i.e., 10Gbps for FC1200 and GE LAN) 11 ODU2e (i.e., 10Gbps for FC1200 and GE LAN)
12~19 Reserved (for future use) 12~19 Reserved (for future use)
20 ODUflex(CBR) (i.e., 1.25*N Gbps) 20 ODUflex(CBR) (i.e., 1.25*N Gbps)
21 ODUflex(Generic Framing Procedure-Framed (GFP-F)), 21 ODUflex(Generic Framing Procedure-Framed (GFP-F)),
resizable (i.e., 1.25*N Gbps) resizable (i.e., 1.25*N Gbps)
22 ODUflex(GFP-F), non resizable (i.e., 1.25*N Gbps) 22 ODUflex(GFP-F), non resizable (i.e., 1.25*N Gbps)
23~255 Reserved (for future use) 23~255 Reserved (for future use)
N: 8 bits
In case of ODUflex(GFP) signal types (both resizable and non
resizable), this field indicates the number of tributary slots
needed for the requested ODUflex(GFP). For other signal types,
this field is not necessary and MUST be set to 0.
NVC: 16 bits NVC: 16 bits
As defined in [RFC4328] Section 3.2.3. As defined in [RFC4328] Section 3.2.3.
Multiplier (MT): 16 bits Multiplier (MT): 16 bits
As defined in [RFC4328] Section 3.2.4. As defined in [RFC4328] Section 3.2.4.
Bit_Rate: 32 bits Bit_Rate: 32 bits
In case of ODUflex(CBR) signal type, this field indicates the In case of ODUflex including ODUflex(CBR) and ODUflex(GFP) signal
nominal bit rate of ODUflex(CBR) expressed in bytes per second, types, this field indicates the nominal bit rate of ODUflex
encoded as a 32-bit IEEE single-precision floating-point number expressed in bytes per second, encoded as a 32-bit IEEE single-
(referring to [RFC4506] and [IEEE]). The value contained in the precision floating-point number (referring to [RFC4506] and
Bit Rate field has to keep into account both 239/238 factor and [IEEE]). For other signal types, this field is not necessary and
the Transcoding factor. For other signal types, this field is not MUST be set to 0.
necessary and MUST be set to 0.
Tolerance: 16 bits Tolerance: 16 bits
In case of ODUflex(CBR) signal type, this field indicates the bit In case of ODUflex(CBR) signal type, this field indicates the bit
rate tolerance (part per million, ppm) of the ODUflex(CBR) rate tolerance (part per million, ppm) of the ODUflex(CBR)
encoded as an unsigned integer, which MUST be bounded in encoded as an unsigned integer. The ODUflex(CBR) bit rate
0~100ppm. For other signal types, this field is not necessary and tolerance is always specified as 100 ppm per Table 7-2 of [G709-
MUST be set to 0. 2012], so it MUST be set to 100ppm. For other signal types, this
field is not necessary and MUST be set to 0.
5.1. Usage of ODUflex(CBR) Traffic Parameters 5.1. Usage of ODUflex(CBR) Traffic Parameters
In case of ODUflex(CBR), the information of Bit_Rate and Tolerance in In case of ODUflex(CBR), the information of Bit_Rate and Tolerance in
the ODUflex Traffic Parameters MUST be used to determine the actual the ODUflex Traffic Parameters MUST be used to determine the actual
bandwidth of ODUflex(CBR) (i.e., Bit_Rate * (1 +/- Tolerance)). bandwidth of ODUflex(CBR) (i.e., Bit_Rate * (1 +/- Tolerance)).
Therefore the total number of tributary slots N in the HO ODUk link Therefore the total number of tributary slots N in the HO ODUk link
can be reserved correctly. Here: can be reserved correctly. Here:
N = Ceiling of N = Ceiling of
skipping to change at page 10, line 22 skipping to change at page 10, line 19
5.2. Usage of ODUflex(GFP) Traffic Parameters 5.2. Usage of ODUflex(GFP) Traffic Parameters
[G709-2012] recommends that the ODUflex(GFP) will fill an integral [G709-2012] recommends that the ODUflex(GFP) will fill an integral
number of tributary slots of the smallest HO ODUk path over which the number of tributary slots of the smallest HO ODUk path over which the
ODUflex(GFP) may be carried, as shown in Table 2. ODUflex(GFP) may be carried, as shown in Table 2.
Table 2 - Recommended ODUflex(GFP) bit rates and tolerance Table 2 - Recommended ODUflex(GFP) bit rates and tolerance
ODU type | Nominal bit-rate | Tolerance ODU type | Nominal bit-rate | Tolerance
--------------------------------+------------------+----------- --------------------------------+------------------+-----------
ODUflex(GFP) of N TS, 1<=N<=8 | N * ODU2.ts | +/-100 ppm ODUflex(GFP) of n TS, 1<=n<=8 | n * ODU2.ts | +/-100 ppm
ODUflex(GFP) of N TS, 9<=N<=32 | N * ODU3.ts | +/-100 ppm ODUflex(GFP) of n TS, 9<=n<=32 | n * ODU3.ts | +/-100 ppm
ODUflex(GFP) of N TS, 33<=N<=80 | N * ODU4.ts | +/-100 ppm ODUflex(GFP) of n TS, 33<=n<=80 | n * ODU4.ts | +/-100 ppm
Since each hop on an ODUflex(GFP) LSP requires the same number of According to this table, the Bit_Rate field for ODUflex(GFP) MUST
tributary slots (i.e., "N" in Table 2), the Traffic Parameters for equal to one of the 80 values listed below:
ODUflex(GFP) just need to carry "N" value to indicate the number of
TSs rather than carrying the Bit_Rate and Tolorance. 1 * ODU2.ts; 2 * ODU2.ts; ...; 8 * ODU2.ts;
9 * ODU3.ts; 10 * ODU3.ts, ...; 32 * ODU3.ts;
33 * ODU4.ts; 34 * ODU4.ts; ...; 80 * ODU4.ts.
In this way, the number of required tributary slots for the
ODUflex(GFP) (i.e., the value of "n" in Table 2) can be deduced from
the Bit_Rate field.
5.3. Notification on Errors of OTN-TDM Traffic Parameters 5.3. Notification on Errors of OTN-TDM Traffic Parameters
There is no Adspec associated with the OTN-TDM SENDER_TSPEC. Either There is no Adspec associated with the OTN-TDM SENDER_TSPEC. Either
the Adspec is omitted or an Int-serv Adspec with the Default General the Adspec is omitted or an Int-serv Adspec with the Default General
Characterization Parameters and Guaranteed Service fragment is used, Characterization Parameters and Guaranteed Service fragment is used,
see [RFC2210]. see [RFC2210].
For a particular sender in a session, the contents of the FLOWSPEC For a particular sender in a session, the contents of the FLOWSPEC
object received in a Resv message SHOULD be identical to the contents object received in a Resv message SHOULD be identical to the contents
skipping to change at page 20, line 22 skipping to change at page 20, line 22
plane. plane.
10. IANA Considerations 10. IANA Considerations
Three RSVP C-Types are defined for OTN-TDM Traffic Parameters and Three RSVP C-Types are defined for OTN-TDM Traffic Parameters and
OTN-TDM Generalized Label in this document: OTN-TDM Generalized Label in this 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)
- OTN-TDM Generalized Label Object: - OTN-TDM Generalized Label Object:
o OTN-TDM Generalized Label Object: Class = 16, C-Type = 2 (see o OTN-TDM Generalized Label Object: Class = 16, C-Type = 2 (see
Section 6.1) Section 6.1)
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
 End of changes. 12 change blocks. 
33 lines changed or deleted 32 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/