< draft-ggalimbe-ccamp-flexigrid-carrier-label-05.txt   draft-ggalimbe-ccamp-flexigrid-carrier-label-06.txt >
Internet Engineering Task Force G. Galimberti, Ed. Internet Engineering Task Force G. Galimberti, Ed.
Internet-Draft D. La Fauci Internet-Draft D. La Fauci
Intended status: Experimental Cisco Intended status: Experimental Cisco
Expires: April 25, 2019 A. Zanardi, Ed. Expires: September 12, 2019 A. Zanardi, Ed.
L. Galvagni L. Galvagni
FBK-CreateNet FBK-CreateNet
October 22, 2018 March 11, 2019
Signaling extensions for Media Channel sub-carriers configuration in Signaling extensions for Media Channel sub-carriers configuration in
Spectrum Switched Optical Networks (SSON) in Lambda Switch Capable (LSC) Spectrum Switched Optical Networks (SSON) in Lambda Switch Capable (LSC)
Optical Line Systems. Optical Line Systems.
draft-ggalimbe-ccamp-flexigrid-carrier-label-05 draft-ggalimbe-ccamp-flexigrid-carrier-label-06
Abstract Abstract
This memo defines the signaling extensions for managing Spectrum This memo defines the signaling extensions for managing Spectrum
Switched Optical Network (SSON) parameters shared between the Client Switched Optical Network (SSON) parameters shared between the Client
and the Network and inside the Network in accordance to the model and the Network and inside the Network in accordance to the model
described in RFC 7698. The extensions are in accordance and described in RFC 7698. The extensions are in accordance and
extending the parameters defined in ITU-T Recommendation extending the parameters defined in ITU-T Recommendation
G.694.1.[ITU.G694.1] and its extensions and G.872.[ITU.G872]. G.694.1.[ITU.G694.1] and its extensions and G.872.[ITU.G872].
skipping to change at page 1, line 45 skipping to change at page 1, line 45
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
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."
This Internet-Draft will expire on April 25, 2019. This Internet-Draft will expire on September 12, 2019.
Internet-Drafdraft-ggalimbe-ccamp-flexigrid-carrier-label-0 October 2018
Copyright Notice Copyright Notice
Copyright (c) 2018 IETF Trust and the persons identified as the Copyright (c) 2019 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
(https://trustee.ietf.org/license-info) in effect on the date of (https://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 respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
skipping to change at page 2, line 33 skipping to change at page 2, line 31
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Client interface parameters . . . . . . . . . . . . . . . . . 3 2. Client interface parameters . . . . . . . . . . . . . . . . . 3
3. Use Cases . . . . . . . . . . . . . . . . . . . . . . . . . . 5 3. Use Cases . . . . . . . . . . . . . . . . . . . . . . . . . . 5
4. Signalling Extensions . . . . . . . . . . . . . . . . . . . . 5 4. Signalling Extensions . . . . . . . . . . . . . . . . . . . . 5
4.1. New LSP set-up parameters . . . . . . . . . . . . . . . . 5 4.1. New LSP set-up parameters . . . . . . . . . . . . . . . . 5
4.2. Extension to LSP set-up reservation . . . . . . . . . . . 7 4.2. Extension to LSP set-up reservation . . . . . . . . . . . 7
4.2.1. Sub-carrier list content . . . . . . . . . . . . . . 9 4.2.1. Sub-carrier list content . . . . . . . . . . . . . . 9
4.2.2. Sub-carrier sub-TLV . . . . . . . . . . . . . . . . . 10 4.2.2. Sub-carrier sub-TLV . . . . . . . . . . . . . . . . . 10
4.3. RSVP Protocol Extensions considerations . . . . . . . . . 12 4.3. RSVP Protocol Extensions considerations . . . . . . . . . 12
5. Security Considerations . . . . . . . . . . . . . . . . . . . 13 5. Security Considerations . . . . . . . . . . . . . . . . . . . 14
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 13 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14
7. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 13 7. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 14
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 13 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 14
8.1. Normative References . . . . . . . . . . . . . . . . . . 13 8.1. Normative References . . . . . . . . . . . . . . . . . . 14
8.2. Informative References . . . . . . . . . . . . . . . . . 15 8.2. Informative References . . . . . . . . . . . . . . . . . 16
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 15 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 16
1. Introduction 1. Introduction
Generalised Multiprotocol Label Switched (GMPLS) is widely used in Generalised Multiprotocol Label Switched (GMPLS) is widely used in
Wavelength Switched Optical Network (WSON) to support the optical Wavelength Switched Optical Network (WSON) to support the optical
circuits set-up through the signalling between Core Nodes and Edge circuits set-up through the signalling between Core Nodes and Edge
Nodes. This extension addresses the use cases described by [RFC7698] Nodes. This extension addresses the use cases described by [RFC7698]
Ch.3.3 and supports the information, needed in Spectrum Switched Ch.3.3 and supports the information, needed in Spectrum Switched
Optical Network (SSON), to signal a Media Channel and the associated Optical Network (SSON), to signal a Media Channel and the associated
carriers set request. The new set of parameters is related to the carriers set request. The new set of parameters is related to the
Media Channel and the carrier(s) routed with it and keep the backward Media Channel and the carrier(s) routed with it and keep the backward
compatibility with the WSON signalling. In particular this memo compatibility with the WSON signalling. In particular this memo
wants do address the use cases where the SSON LSP (the Media Channel wants do address the use cases where the SSON LSP (the Media Channel
in RFC7698) carries multiple carrier (OTSi) containing same Payload. in RFC7698) carries multiple carrier (OTSi) containing same Payload.
The set of the carriers can be seen as single Logical circuit. This The set of the carriers can be seen as single Logical circuit. This
Internet-Drafdraft-ggalimbe-ccamp-flexigrid-carrier-label-0 October 2018
memo can be considered as the extension of [RFC7792]. The contents memo can be considered as the extension of [RFC7792]. The contents
and the parameters reflect the experimental activity on IP over SSON and the parameters reflect the experimental activity on IP over SSON
recently done by some vendors and research consortia. recently done by some vendors and research consortia.
Figure 1 shows how the multiple carrier are mapped into a Media Figure 1 shows how the multiple carrier are mapped into a Media
Channel. A set of parameters must be shared on the UNI to allow the Channel. A set of parameters must be shared on the UNI to allow the
GMPLS to do the proper routing and Spectrum Assignment and decide the GMPLS to do the proper routing and Spectrum Assignment and decide the
carrier position. carrier position.
+------+ +------+ _________ +------+ +------+ +------+ +------+ _________ +------+ +------+
skipping to change at page 4, line 4 skipping to change at page 4, line 4
in terms of: in terms of:
Number of subcarriers: Number of subcarriers:
This parameter indicates the number of subcarriers available for This parameter indicates the number of subcarriers available for
the super-channel in case the Transceiver can support multiple the super-channel in case the Transceiver can support multiple
carrier circuits. carrier circuits.
Central frequency (see G.694.1 Table 1): Central frequency (see G.694.1 Table 1):
This parameter indicates the Central frequency value that Ss and This parameter indicates the Central frequency value that Ss and
Rs will be set to work (in THz). See the details in Section 6/ Rs will be set to work (in THz). See the details in Section 6/
Internet-Drafdraft-ggalimbe-ccamp-flexigrid-carrier-label-0 October 2018
G.694.1 or based on "n" value explanation and the following "k" G.694.1 or based on "n" value explanation and the following "k"
values definition in case of multicarrier transceivers. values definition in case of multicarrier transceivers.
Central frequency granularity: Central frequency granularity:
This parameter indicates the Central frequency granularity This parameter indicates the Central frequency granularity
supported by the transceiver, this value is combined with k and n supported by the transceiver, this value is combined with k and n
value to calculate the central frequency of the carrier or sub- value to calculate the central frequency of the carrier or sub-
carriers. carriers.
Minimum channel spacing: Minimum channel spacing:
skipping to change at page 5, line 5 skipping to change at page 5, line 5
receiver input power: receiver input power:
This parameter provisions the Min and MAX input pover suppotred by This parameter provisions the Min and MAX input pover suppotred by
the Transceiver, i.e. Receiver Sensitivity. the Transceiver, i.e. Receiver Sensitivity.
The above parameters are related to the Edge Node Transceiver and are The above parameters are related to the Edge Node Transceiver and are
used by the Core Network GMPLS in order to calculate the optical used by the Core Network GMPLS in order to calculate the optical
feasibility and the spectrum allocation. The parameters can be feasibility and the spectrum allocation. The parameters can be
shared between the Client and the Network via LMP or provisioned to shared between the Client and the Network via LMP or provisioned to
the Network by an EMS or an operator OSS. the Network by an EMS or an operator OSS.
Internet-Drafdraft-ggalimbe-ccamp-flexigrid-carrier-label-0 October 2018
3. Use Cases 3. Use Cases
The use cases are described in draft-ietf-ccamp-dwdm-if-mng-ctrl-fwk The use cases are described in draft-ietf-ccamp-dwdm-if-mng-ctrl-fwk
and [RFC7698] and [RFC7698]
4. Signalling Extensions 4. Signalling Extensions
Some of the above parameters can be applied to RFC7792 (SENDER_TSPEC/ Some of the above parameters can be applied to RFC7792 (SENDER_TSPEC/
FLOWSPEC). The above parameters could be applied to [RFC4208] FLOWSPEC). The above parameters could be applied to [RFC4208]
scenarios but they are valid also in case of non UNI scenarios. The scenarios but they are valid also in case of non UNI scenarios. The
skipping to change at page 6, line 5 skipping to change at page 6, line 5
carried by the multiple carrier circuit carried by the multiple carrier circuit
Policy (strict/loose): Policy (strict/loose):
Strict/loose referred to B/W and subcarrier number. This is to Strict/loose referred to B/W and subcarrier number. This is to
give some flexibility to the GMPLS in order to commit client give some flexibility to the GMPLS in order to commit client
request. request.
Subcarrier bandwidth tunability: Subcarrier bandwidth tunability:
(optional) e.g. 34Ghz, 48GHz. (optional) e.g. 34Ghz, 48GHz.
Internet-Drafdraft-ggalimbe-ccamp-flexigrid-carrier-label-0 October 2018
The TLV define the resource constraints for the requested Media The TLV define the resource constraints for the requested Media
Channel. Channel.
The format of the this sub-object is as follows: The format of the this sub-object is as 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|S|B| Reserved | Carrier Number | |S|B| Reserved | Carrier Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 7, line 4 skipping to change at page 7, line 4
(B must be 0) (B must be 0)
B Bandwidth constraints B Bandwidth constraints
- B = 0: the value is the maximum requested bandwidth (a lower - B = 0: the value is the maximum requested bandwidth (a lower
value can be allocated if resources are not available) value can be allocated if resources are not available)
- B = 1: the requested bandwidth is the minimum value to be - B = 1: the requested bandwidth is the minimum value to be
allocated (a higher value can be allocated if requested allocated (a higher value can be allocated if requested
by the physical constraints of the ports) by the physical constraints of the ports)
Reserved: unused bit (for future use, should be 0) Reserved: unused bit (for future use, should be 0)
Internet-Drafdraft-ggalimbe-ccamp-flexigrid-carrier-label-0 October 2018
Note: bandwidth unit is defined in accordance to RFC 3471 Note: bandwidth unit is defined in accordance to RFC 3471
chap. 3.1.2 Bandwith Encoding specification. Bandwidth higher chap. 3.1.2 Bandwith Encoding specification. Bandwidth higher
than 40Gb/s values must be defined (e.g. 100Gb/s, 150Gb/s than 40Gb/s values must be defined (e.g. 100Gb/s, 150Gb/s
400Gb/s, etc.) 400Gb/s, etc.)
TLV Usage: TLV Usage:
Head UNI-C PATH: requested traffic constraints, the Head UNI-N node Head UNI-C PATH: requested traffic constraints, the Head UNI-N node
must satisfy when reserving the optical resources and defining must satisfy when reserving the optical resources and defining
the carriers configuration the carriers configuration
The TLV can be omitted: no traffic constraints is defined (resources The TLV can be omitted: no traffic constraints is defined (resources
skipping to change at page 8, line 5 skipping to change at page 8, line 5
Circuits. Circuits.
Central frequency granularity (J): Central frequency granularity (J):
This parameter indicates the Central frequency granularity This parameter indicates the Central frequency granularity
supported by the transceiver, this value is combined with K and n supported by the transceiver, this value is combined with K and n
value to calculate the central frequency on the carrier or sub- value to calculate the central frequency on the carrier or sub-
carriers. carriers.
Central frequency (see G.694.1 Table 1): Central frequency (see G.694.1 Table 1):
Internet-Drafdraft-ggalimbe-ccamp-flexigrid-carrier-label-0 October 2018
Grid, Identifiers, central frequency and granularity. Grid, Identifiers, central frequency and granularity.
Laser Output power: Laser Output power:
This parameter provisions the Transceiver Output power, it can be This parameter provisions the Transceiver Output power, it can be
either a setting and measured value. either a setting and measured value.
Circuit Path, RRO, etc: Circuit Path, RRO, etc:
All these info are defined in [RFC4208]. All these info are defined in [RFC4208].
Path Error: Path Error:
skipping to change at page 9, line 5 skipping to change at page 9, line 5
Value 0 is reserved to be used if no value is defined Value 0 is reserved to be used if no value is defined
- FEC: the signal Forward Error Corrections type (16-bit - FEC: the signal Forward Error Corrections type (16-bit
unsigned integer), the defined values are: unsigned integer), the defined values are:
- <TBD> (ITU-T reference) - <TBD> (ITU-T reference)
- 32768 (first bit is 1): custom defined values - 32768 (first bit is 1): custom defined values
Value 0 is reserved to be used if no value is defined Value 0 is reserved to be used if no value is defined
- Baud Rate: the signal symbol rate (IEEE 32-bit float, - Baud Rate: the signal symbol rate (IEEE 32-bit float,
in bauds/s) in bauds/s)
Value 0 is reserved to be used if no value is defined Value 0 is reserved to be used if no value is defined
Internet-Drafdraft-ggalimbe-ccamp-flexigrid-carrier-label-0 October 2018
Notes: Notes:
- The PATH request from the Head UNI-C node can specify all or - The PATH request from the Head UNI-C node can specify all or
only a subset of the parameters (e.g. the Modulation and the only a subset of the parameters (e.g. the Modulation and the
baud rate as required but not the FEC) setting to 0 for the baud rate as required but not the FEC) setting to 0 for the
undefined parameters. undefined parameters.
When forwarding the PATH message, the UNI-N will set the When forwarding the PATH message, the UNI-N will set the
undefined parameters based on the optical impairment calculation undefined parameters based on the optical impairment calculation
and the constraints giveng by the UNI-C and the constraints giveng by the UNI-C
- Custom codes (values > 0x8000) interpretation is a local - Custom codes (values > 0x8000) interpretation is a local
installation matter. installation matter.
skipping to change at page 10, line 5 skipping to change at page 10, line 5
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Carrier Identifier | j | | Carrier Identifier | j |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| k | | k |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| sub-TLVs | | sub-TLVs |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 4: Sub-Carrier parameters Figure 4: Sub-Carrier parameters
Internet-Drafdraft-ggalimbe-ccamp-flexigrid-carrier-label-0 October 2018
Carrier set-up: Carrier set-up:
- Carrier identifier field: sub-carrier - Carrier identifier field: sub-carrier
identifier inside the mediachannel. Identifies the carrier identifier inside the mediachannel. Identifies the carrier
position inside the Media Channel (16-bit unsigned integer) position inside the Media Channel (16-bit unsigned integer)
The Carrier Identifier is the logical circuit sub-lane The Carrier Identifier is the logical circuit sub-lane
position, a TLV for each value from 1 to the number of position, a TLV for each value from 1 to the number of
allocated carriers must be present. allocated carriers must be present.
- J field: granularity of the channel spacing, can be a - J field: granularity of the channel spacing, can be a
multiple of 0.01GHz. - default value is 0.1GHz. multiple of 0.01GHz. - default value is 0.1GHz.
skipping to change at page 11, line 4 skipping to change at page 11, line 4
-4 -3 -2 -1 0 1 2 3 4 5 6 7 8 9 10 11 12 -4 -3 -2 -1 0 1 2 3 4 5 6 7 8 9 10 11 12
--+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+- --+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+-
| n=4 | | n=4 |
K1 -236 | +236 K2 K1 -236 | +236 K2
<------------------------ Media Channel -----------------------> <------------------------ Media Channel ----------------------->
4.2.2. Sub-carrier sub-TLV 4.2.2. Sub-carrier sub-TLV
The defined sub-TLVs are Port Identifiers and Carrier Power The defined sub-TLVs are Port Identifiers and Carrier Power
Internet-Drafdraft-ggalimbe-ccamp-flexigrid-carrier-label-0 October 2018
Source Port Identifier Source Port Identifier
The format of this sub-object (Type = TBA, Length = TBD) is The format of this sub-object (Type = TBA, Length = TBD) is
as follows: as 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type (TBA) | Length (TBD) | | Type (TBA) | Length (TBD) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 12, line 5 skipping to change at page 12, line 5
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type (TBA) | Length (TBD) | | Type (TBA) | Length (TBD) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Destination Port Identifier | | Destination Port Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 6: Destination Port Identifiers Figure 6: Destination Port Identifiers
Internet-Drafdraft-ggalimbe-ccamp-flexigrid-carrier-label-0 October 2018
Destination Port Identifier: the local upstream optical logical Destination Port Identifier: the local upstream optical logical
destination end point identifier (32-bits integer, ifindex) destination end point identifier (32-bits integer, ifindex)
TLV Usage: TLV Usage:
- Head UNI-C PATH: used to force specific carrier ports - Head UNI-C PATH: used to force specific carrier ports
[optional use, e.g. with external PCE scenario] [optional use, e.g. with external PCE scenario]
- Tail UNI-N PATH: set selected configuration on tail node - Tail UNI-N PATH: set selected configuration on tail node
- RESV: report selected configuration to HEAD UNI-C node - RESV: report selected configuration to HEAD UNI-C node
Carrier Power Carrier Power
skipping to change at page 13, line 5 skipping to change at page 13, line 5
Media Channel supported traffic. It could be encoded in the Media Channel supported traffic. It could be encoded in the
SENDER_TSPEC/FLOW_SPEC objects by extending the SSON_SENDER_TSPEC/ SENDER_TSPEC/FLOW_SPEC objects by extending the SSON_SENDER_TSPEC/
SSON_FLOW_SPEC defined in RFC 7792 (or defining a new C-Type) with an SSON_FLOW_SPEC defined in RFC 7792 (or defining a new C-Type) with an
optional TLV list or it could be encoded in a newly defined entry optional TLV list or it could be encoded in a newly defined entry
(new OBJECT or new LSP_ATTRIBUTES OBJECT TLV) (new OBJECT or new LSP_ATTRIBUTES OBJECT TLV)
This solution is consistent with other technology specific extensions This solution is consistent with other technology specific extensions
(e.g. SDH), but requires the explicit handling of the extensions by (e.g. SDH), but requires the explicit handling of the extensions by
all nodes. all nodes.
Internet-Drafdraft-ggalimbe-ccamp-flexigrid-carrier-label-0 October 2018
Beside this, some of the additional information defined is local to Beside this, some of the additional information defined is local to
the head/tail UNI link (e.g. the carrier/port association), while the the head/tail UNI link (e.g. the carrier/port association), while the
traffic spec info should be valid end-to-end. traffic spec info should be valid end-to-end.
There can be different methods to model and signal the carriers as
described in draft-lee-ccamp-optical-impairment-topology-yang. The
Media Channel, Network Media Channel and lables are well modelled by
the RFC7698, RFC7699 and RFC7792 reflecting the ITU-T Recommendations
G.694.1 and G.698.2.
Some work is in progress in ITU-T SG15/Q12 to define Network Media
Channel (group) that is capable of accommodating the optical
tributary signals (OTSi) belonging to optical tributary signal group
(OTSiG) (see new ITU-T Draft Recommendation G.807). Currently, no
models exist (in the IETF nor ITU-T SG15) that define how the optical
tributary signals are described inside the Network Media Channel
Group in terms of OTSi identifier, OTSi carrier frequency and OTSi
signal width.
Other the encoding proposal reported in this draft, there are several
at least two other methods to describe the parameters. An option is
to describe the OTSi carrier frequency relative to the anchor
frequency 193.1THz based on a well-defined granularity (e.g. OTSi
carrier frequency = 193100 (GHz) + K * granularity (GHz) where K is a
signed integer value). A second option is to explicitly describe the
OTSi carrier frequency and the OTSi signal width in GHz with a
certain accuracy.
The second option which is independent of the n, m values already
defined in ITU-T Recommendation G.694.1. The OTSi carrier frequency
is described in GHz with 3 fractional digits (decimal 64 fraction
digits 3). The OTSi signal width is described in GHz with 3
fractional digits (decimal 64 fraction digits 3) and includes the
signal roll off as well as some guard band.
The accuracy of 0.001 GHz does not impose a requirement on the
optical transceiver components (optical transmitter) in terms of
carrier frequency tunability precision. Today's components typically
provide a tunability precision in the range of 1..1.5GHz (carrier
frequency offset compared to the configured nominal carrier
frequency). Future components may provide a better precision as
technology evolves. If needed, a controller may retrieve the
transceiver properties in terms of carrier frequency tunability
precision in order to be capable of properly configuring the
underlying transceiver.
NOTE FROM THE EDITORS: As this description is arbitrarily proposed by
the authors to cover a lack of information in IETF and ITU-T, a
liaison request to ITU-T is needed. The authors are willing to
contribute to Liaison editing and to consider any feedback and
proposal from ITU-T.
5. Security Considerations 5. Security Considerations
GMPLS message security uses IPsec, as described in xxxx. This GMPLS message security uses IPsec, as described in xxxx. This
document only defines new UNI objects that are carried in existing document only defines new UNI objects that are carried in existing
UNI messages, similar to the UNI objects in xxx. This document does UNI messages, similar to the UNI objects in xxx. This document does
not introduce new security considerations. not introduce new security considerations.
6. IANA Considerations 6. IANA Considerations
T.B.D. T.B.D.
skipping to change at page 14, line 5 skipping to change at page 15, line 5
International Telecommunications Union, "Amplified International Telecommunications Union, "Amplified
multichannel dense wavelength division multiplexing multichannel dense wavelength division multiplexing
applications with single channel optical interfaces", applications with single channel optical interfaces",
ITU-T Recommendation G.698.2, November 2009. ITU-T Recommendation G.698.2, November 2009.
[ITU.G709] [ITU.G709]
International Telecommunications Union, "Interface for the International Telecommunications Union, "Interface for the
Optical Transport Network (OTN)", ITU-T Recommendation Optical Transport Network (OTN)", ITU-T Recommendation
G.709, June 2016. G.709, June 2016.
Internet-Drafdraft-ggalimbe-ccamp-flexigrid-carrier-label-0 October 2018
[ITU.G872] [ITU.G872]
International Telecommunications Union, "Architecture of International Telecommunications Union, "Architecture of
optical transport networks", ITU-T Recommendation G.872, optical transport networks", ITU-T Recommendation G.872,
January 2017. January 2017.
[ITU.G874.1] [ITU.G874.1]
International Telecommunications Union, "Optical transport International Telecommunications Union, "Optical transport
network (OTN): Protocol-neutral management information network (OTN): Protocol-neutral management information
model for the network element view", ITU-T Recommendation model for the network element view", ITU-T Recommendation
G.874.1, November 2016. G.874.1, November 2016.
skipping to change at page 15, line 5 skipping to change at page 16, line 5
"Framework for GMPLS and Path Computation Element (PCE) "Framework for GMPLS and Path Computation Element (PCE)
Control of Wavelength Switched Optical Networks (WSONs)", Control of Wavelength Switched Optical Networks (WSONs)",
RFC 6163, DOI 10.17487/RFC6163, April 2011, RFC 6163, DOI 10.17487/RFC6163, April 2011,
<https://www.rfc-editor.org/info/rfc6163>. <https://www.rfc-editor.org/info/rfc6163>.
[RFC6205] Otani, T., Ed. and D. Li, Ed., "Generalized Labels for [RFC6205] Otani, T., Ed. and D. Li, Ed., "Generalized Labels for
Lambda-Switch-Capable (LSC) Label Switching Routers", Lambda-Switch-Capable (LSC) Label Switching Routers",
RFC 6205, DOI 10.17487/RFC6205, March 2011, RFC 6205, DOI 10.17487/RFC6205, March 2011,
<https://www.rfc-editor.org/info/rfc6205>. <https://www.rfc-editor.org/info/rfc6205>.
Internet-Drafdraft-ggalimbe-ccamp-flexigrid-carrier-label-0 October 2018
[RFC7698] Gonzalez de Dios, O., Ed., Casellas, R., Ed., Zhang, F., [RFC7698] Gonzalez de Dios, O., Ed., Casellas, R., Ed., Zhang, F.,
Fu, X., Ceccarelli, D., and I. Hussain, "Framework and Fu, X., Ceccarelli, D., and I. Hussain, "Framework and
Requirements for GMPLS-Based Control of Flexi-Grid Dense Requirements for GMPLS-Based Control of Flexi-Grid Dense
Wavelength Division Multiplexing (DWDM) Networks", Wavelength Division Multiplexing (DWDM) Networks",
RFC 7698, DOI 10.17487/RFC7698, November 2015, RFC 7698, DOI 10.17487/RFC7698, November 2015,
<https://www.rfc-editor.org/info/rfc7698>. <https://www.rfc-editor.org/info/rfc7698>.
[RFC7699] Farrel, A., King, D., Li, Y., and F. Zhang, "Generalized [RFC7699] Farrel, A., King, D., Li, Y., and F. Zhang, "Generalized
Labels for the Flexi-Grid in Lambda Switch Capable (LSC) Labels for the Flexi-Grid in Lambda Switch Capable (LSC)
Label Switching Routers", RFC 7699, DOI 10.17487/RFC7699, Label Switching Routers", RFC 7699, DOI 10.17487/RFC7699,
skipping to change at page 16, line 4 skipping to change at page 17, line 4
Authors' Addresses Authors' Addresses
Gabriele Galimberti (editor) Gabriele Galimberti (editor)
Cisco Cisco
Via S. Maria Molgora, 48 c Via S. Maria Molgora, 48 c
20871 - Vimercate 20871 - Vimercate
Italy Italy
Phone: +390392091462 Phone: +390392091462
Email: ggalimbe@cisco.com Email: ggalimbe@cisco.com
Internet-Drafdraft-ggalimbe-ccamp-flexigrid-carrier-label-0 October 2018
Domenico La Fauci Domenico La Fauci
Cisco Cisco
Via S. Maria Molgora, 48 c Via S. Maria Molgora, 48 c
20871 - Vimercate 20871 - Vimercate
Italy Italy
Phone: +390392091946 Phone: +390392091946
Email: dlafauci@cisco.com Email: dlafauci@cisco.com
Andrea Zanardi (editor) Andrea Zanardi (editor)
 End of changes. 21 change blocks. 
47 lines changed or deleted 60 lines changed or added

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