draft-ietf-teas-gmpls-scsi-02.txt   draft-ietf-teas-gmpls-scsi-03.txt 
TEAS Working Group D. Ceccarelli TEAS Working Group D. Ceccarelli
Internet-Draft Ericsson Internet-Draft Ericsson
Intended status: Standards Track L. Berger Intended status: Standards Track L. Berger
Expires: September 28, 2017 LabN Consulting, L.L.C. Expires: December 30, 2017 LabN Consulting, L.L.C.
March 27, 2017 June 28, 2017
Generalized Interface Switching Capability Descriptor - Switching Generalized Interface Switching Capability Descriptor - Switching
Capability Specific Information Capability Specific Information
draft-ietf-teas-gmpls-scsi-02 draft-ietf-teas-gmpls-scsi-03
Abstract Abstract
This document defines a generic information structure for information This document defines a generic information structure for information
carried in routing protocol Interface Switching Capability Descriptor carried in routing protocol Interface Switching Capability Descriptor
(ISCD) Switching Capability Specific Information (SCSI) fields. This (ISCD) Switching Capability Specific Information (SCSI) fields. This
"Generalized SCSI" can be used with routing protocols that define "Generalized SCSI" can be used with routing protocols that define
GMPLS ISCDs, and any specific technology. This document does not GMPLS ISCDs, and any specific technology. This document does not
modify an existing technology specific formats and is defined for use modify any existing technology specific formats and is defined for
in conjunction with new GMPLS Switching Capability types. use in conjunction with new GMPLS Switching Capability types. The
context for this document is Generalized MPLS, and the reader is
expected to be familiar with the GMPLS architecture and associate
protocol standards.
Status of this Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted 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). 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 http://datatracker.ietf.org/drafts/current/. Drafts is at http://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 September 28, 2017. This Internet-Draft will expire on December 30, 2017.
Copyright Notice Copyright Notice
Copyright (c) 2017 IETF Trust and the persons identified as the Copyright (c) 2017 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
(http://trustee.ietf.org/license-info) in effect on the date of (http://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
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. Generalized SCSI Formats . . . . . . . . . . . . . . . . . . . 3 3. Generalized SCSI Formats . . . . . . . . . . . . . . . . . . 3
4. Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . 4 4. Procedures . . . . . . . . . . . . . . . . . . . . . . . . . 4
5. Security Considerations . . . . . . . . . . . . . . . . . . . . 5 5. Security Considerations . . . . . . . . . . . . . . . . . . . 4
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 5 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 6 7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 5
8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 6 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 5
8.1. Normative References . . . . . . . . . . . . . . . . . . . 6 8.1. Normative References . . . . . . . . . . . . . . . . . . 5
8.2. Informative References . . . . . . . . . . . . . . . . . . 6 8.2. Informative References . . . . . . . . . . . . . . . . . 6
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 7 8.3. URIs . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 7
1. Introduction 1. Introduction
The context for this document is Generalized MPLS, and the reader is
expected to be familiar with the GMPLS architecture, associate
terminology and protocol standards. Notably, but not limited to,
[RFC3945], [RFC4202], [RFC4203] and [RFC5307].
The Interface Switching Capability Descriptor (ISCD) [RFC4202] allows The Interface Switching Capability Descriptor (ISCD) [RFC4202] allows
routing protocols such as OSPF and ISIS to carry technology specific routing protocols such as OSPF and ISIS to carry technology specific
information in the the Switching Capability-specific information information in the the Switching Capability-specific information
(SCSI) field, see [RFC4203] and [RFC5307]. The format of an SCSI (SCSI) field, see [RFC4203] and [RFC5307]. The format of an SCSI
field is dictated by the specific technology being represented as field is dictated by the specific technology being represented as
indicated by the ISCD Switching Capability (SC) type field. Existing indicated by the ISCD Switching Capability (SC) type field. Existing
Switching Capabilities are managed by IANA in the Switching Types Switching Capabilities are managed by IANA in the Switching Types
registry and the related "IANA-GMPLS-TC-MIB" definitions. registry [1] and the related "IANA-GMPLS-TC-MIB" definitions.
[RFC7138] introduced a "sub-TLV" structure to its technology specific [RFC7138] introduced a "sub-TLV" structure to its technology specific
SCSI field. The Sub-Type-Length-Value (TLV) based approach allows SCSI field. The Sub-Type-Length-Value (TLV) based approach allows
for greater flexibility in the structure, ordering, and ability to for greater flexibility in the structure, ordering, and ability to
support extensions of the SC (technology) specific format. This Sub- support extensions of the SC (technology) specific format. This Sub-
TLV approach is also used in [RFC7688]. TLV approach is also used in [RFC7688].
This document generalizes this approach and defines a new generalized This document generalizes this approach and defines a new generalized
SCSI field format for use by future specific technologies and SCSI field format for use by future specific technologies and
Switching Capability types. The generalized SCSI carries SCSI-TLVs Switching Capability types. The generalized SCSI carries SCSI-TLVs
that may be defined within the scope of a specific technology, or that may be defined within the scope of a specific technology, or
shared across multiple technologies (e.g., shared across multiple technologies (e.g.,
[I-D.ietf-ccamp-ospf-availability-extension]). This document also [I-D.ietf-ccamp-ospf-availability-extension]). This document also
establishes a registry for SCSI-TLV definitions that may be shared establishes a registry for SCSI-TLV definitions that may be shared
across multiple technologies. across multiple technologies.
2. Terminology 2. Terminology
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
document are to be interpreted as described in [RFC2119]. "OPTIONAL" in this document are to be interpreted as described in
[RFC2119].
The reader is expected to be familiar with GMPLS terminology, e.g. as
found in [RFC3945], as well as the terminology used in [RFC4202],
[RFC4203] and [RFC5307].
3. Generalized SCSI Formats 3. Generalized SCSI Formats
The Generalized SCSI is composed of zero or more variable length The Generalized SCSI is composed of zero or more variable length
type-length-value fields which are each called a SCSI-TLV. There are type-length-value fields which are each called a SCSI-TLV. There are
no specific size restrictions on these SCSI-TLV. Size and other no specific size restrictions on these SCSI-TLV. Size and other
formatting restrictions may be imposed by the routing protocol ISCD formatting restrictions may be imposed by the routing protocol ISCD
field, refer to [RFC4203] and [RFC5307]. field, refer to [RFC4203] and [RFC5307].
The SCSI-TLV format is: The SCSI-TLV format is:
skipping to change at page 4, line 19 skipping to change at page 3, line 43
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | | Type | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
... Value ... ... Value ...
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 1: TLV format Figure 1: TLV format
Type (2 octets): Type (2 octets):
This field indicates the type and structure of the information This field indicates the type and structure of the information
contained in the Value field. Note that the value range of this contained in the Value field.
field has been split in two. The lower range is used to indicated
technology specific formats, while the higher range is reserved
for formats that can be used with more than one technology. See
Section 6
Length (2 octets): Length (2 octets):
This field MUST be set to the size, in octets (bytes), of the This field MUST be set to the size, in octets (bytes), of the
Value field. The value of the field MUST be zero or divisible by Value field. The value of the field MUST be zero or divisible by
4. Note that this implies that the Value field can be omitted or 4. Note that this implies that the Value field can be omitted or
contain padding. contain padding.
Value (variable): Value (variable):
A variable length field, formatted according to the value of the A variable length field, formatted according to the definition
Type field. This field can be omitted for certain types. indicated by value of the Type field. This field can be omitted
for certain types.
4. Procedures 4. Procedures
The ISCD can include a Generalized SCSI when advertising technologies The ISCD can include a Generalized SCSI when advertising technologies
whose Switching Capability definition references this document. The whose Switching Capability definition references this document. The
corollary of this is that the Generalized SCSI MUST NOT be used for corollary of this is that the Generalized SCSI MUST NOT be used for
ISCDs of technologies whose Switching Capability definition do not ISCDs of technologies whose Switching Capability definition do not
reference this document. reference this document.
The Generalized SCSI MAY contain a sequence of zero or more SCSI- The Generalized SCSI MAY contain a sequence of zero or more SCSI-
skipping to change at page 5, line 29 skipping to change at page 4, line 50
This document defines a new SCSI-TLV that is carried in the SCSI This document defines a new SCSI-TLV that is carried in the SCSI
field of the ISCDs defined in [RFC4203] and [RFC5307]. The SCSI-TLV field of the ISCDs defined in [RFC4203] and [RFC5307]. The SCSI-TLV
includes a 16-bit type identifier (the Type field). The same Type includes a 16-bit type identifier (the Type field). The same Type
field values are applicable to the new SCSI-TLV. field values are applicable to the new SCSI-TLV.
IANA is requested to create and maintain a new registry, the IANA is requested to create and maintain a new registry, the
"Generalized SCSI (Switching Capability Specific Information) TLVs "Generalized SCSI (Switching Capability Specific Information) TLVs
Types" registry under either the the "Generalized Multi-Protocol Types" registry under either the the "Generalized Multi-Protocol
Label Switching (GMPLS) Signaling Parameters" registry or a new Label Switching (GMPLS) Signaling Parameters" registry or a new
"Generalized Multi-Protocol Label Switching (GMPLS) Routing "Generalized Multi-Protocol Label Switching (GMPLS) Routing
Parameters" registry. Parameters" registry, at their desecration.
The definition of the new registry is as follows: The definition of the new registry is as follows:
Value SCSI-TLV Switching Type Reference Value SCSI-TLV Switching Type Reference
--------- ----------------------- -------------- --------- --------- ----------------------- -------------- ---------
0 Reserved [This ID] 0 Reserved [This ID]
1-65535 Unassigned (Any, or [This ID] 1-65535 Unassigned (value list) [This ID]
value list)
New allocation requests to this registry must indicate the value or New allocation requests to this registry must indicate the value or
values to be used in the Switching Type column. values to be used in the Switching Type column.
The registry should be established with registration policies of The registry should be established with registration policies of
"Specification Required", see [RFC5226]. "Specification Required", see [RFC5226].
REMOVE THIS AFTER PUBLICATION: The designated expert will be REMOVE THIS AFTER PUBLICATION: The designated expert will be
appointed by the Routing AD. It is suggested to appoint any current appointed by the Routing AD. It is suggested to appoint any current
TEAS WG chair. TEAS WG chair.
7. Acknowledgements 7. Acknowledgments
The authors would like to thank Adrian Farrel and Julien Meuric for The authors would like to thank Adrian Farrel and Julien Meuric for
the careful review and suggestions. the careful review and suggestions. Thomas Heide Clausen provided
useful comments as part of the Routing Directorate review.
8. References 8. References
8.1. Normative References 8.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, DOI 10.17487/ Requirement Levels", BCP 14, RFC 2119,
RFC2119, March 1997, DOI 10.17487/RFC2119, March 1997,
<http://www.rfc-editor.org/info/rfc2119>. <http://www.rfc-editor.org/info/rfc2119>.
[RFC4202] Kompella, K., Ed. and Y. Rekhter, Ed., "Routing Extensions [RFC4202] Kompella, K., Ed. and Y. Rekhter, Ed., "Routing Extensions
in Support of Generalized Multi-Protocol Label Switching in Support of Generalized Multi-Protocol Label Switching
(GMPLS)", RFC 4202, DOI 10.17487/RFC4202, October 2005, (GMPLS)", RFC 4202, DOI 10.17487/RFC4202, October 2005,
<http://www.rfc-editor.org/info/rfc4202>. <http://www.rfc-editor.org/info/rfc4202>.
[RFC4203] Kompella, K., Ed. and Y. Rekhter, Ed., "OSPF Extensions in [RFC4203] Kompella, K., Ed. and Y. Rekhter, Ed., "OSPF Extensions in
Support of Generalized Multi-Protocol Label Switching Support of Generalized Multi-Protocol Label Switching
(GMPLS)", RFC 4203, DOI 10.17487/RFC4203, October 2005, (GMPLS)", RFC 4203, DOI 10.17487/RFC4203, October 2005,
skipping to change at page 6, line 40 skipping to change at page 6, line 10
[RFC5307] Kompella, K., Ed. and Y. Rekhter, Ed., "IS-IS Extensions [RFC5307] Kompella, K., Ed. and Y. Rekhter, Ed., "IS-IS Extensions
in Support of Generalized Multi-Protocol Label Switching in Support of Generalized Multi-Protocol Label Switching
(GMPLS)", RFC 5307, DOI 10.17487/RFC5307, October 2008, (GMPLS)", RFC 5307, DOI 10.17487/RFC5307, October 2008,
<http://www.rfc-editor.org/info/rfc5307>. <http://www.rfc-editor.org/info/rfc5307>.
8.2. Informative References 8.2. Informative References
[I-D.ietf-ccamp-ospf-availability-extension] [I-D.ietf-ccamp-ospf-availability-extension]
Long, H., Ye, M., Mirsky, G., D'Alessandro, A., and H. Long, H., Ye, M., Mirsky, G., D'Alessandro, A., and H.
Shah, "OSPF-TE Link Availability Extension for Links with Shah, "OSPF-TE Link Availability Extension for Links with
Variable Discrete Bandwidth", Variable Discrete Bandwidth", draft-ietf-ccamp-ospf-
draft-ietf-ccamp-ospf-availability-extension-09 (work in availability-extension-09 (work in progress), February
progress), February 2017. 2017.
[RFC2154] Murphy, S., Badger, M., and B. Wellington, "OSPF with [RFC2154] Murphy, S., Badger, M., and B. Wellington, "OSPF with
Digital Signatures", RFC 2154, DOI 10.17487/RFC2154, Digital Signatures", RFC 2154, DOI 10.17487/RFC2154, June
June 1997, <http://www.rfc-editor.org/info/rfc2154>. 1997, <http://www.rfc-editor.org/info/rfc2154>.
[RFC3945] Mannie, E., Ed., "Generalized Multi-Protocol Label
Switching (GMPLS) Architecture", RFC 3945,
DOI 10.17487/RFC3945, October 2004,
<http://www.rfc-editor.org/info/rfc3945>.
[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an
IANA Considerations Section in RFCs", BCP 26, RFC 5226, IANA Considerations Section in RFCs", RFC 5226,
DOI 10.17487/RFC5226, May 2008, DOI 10.17487/RFC5226, May 2008,
<http://www.rfc-editor.org/info/rfc5226>. <http://www.rfc-editor.org/info/rfc5226>.
[RFC5304] Li, T. and R. Atkinson, "IS-IS Cryptographic [RFC5304] Li, T. and R. Atkinson, "IS-IS Cryptographic
Authentication", RFC 5304, DOI 10.17487/RFC5304, Authentication", RFC 5304, DOI 10.17487/RFC5304, October
October 2008, <http://www.rfc-editor.org/info/rfc5304>. 2008, <http://www.rfc-editor.org/info/rfc5304>.
[RFC7138] Ceccarelli, D., Ed., Zhang, F., Belotti, S., Rao, R., and [RFC7138] Ceccarelli, D., Ed., Zhang, F., Belotti, S., Rao, R., and
J. Drake, "Traffic Engineering Extensions to OSPF for J. Drake, "Traffic Engineering Extensions to OSPF for
GMPLS Control of Evolving G.709 Optical Transport GMPLS Control of Evolving G.709 Optical Transport
Networks", RFC 7138, DOI 10.17487/RFC7138, March 2014, Networks", RFC 7138, DOI 10.17487/RFC7138, March 2014,
<http://www.rfc-editor.org/info/rfc7138>. <http://www.rfc-editor.org/info/rfc7138>.
[RFC7688] Lee, Y., Ed. and G. Bernstein, Ed., "GMPLS OSPF [RFC7688] Lee, Y., Ed. and G. Bernstein, Ed., "GMPLS OSPF
Enhancement for Signal and Network Element Compatibility Enhancement for Signal and Network Element Compatibility
for Wavelength Switched Optical Networks", RFC 7688, for Wavelength Switched Optical Networks", RFC 7688,
DOI 10.17487/RFC7688, November 2015, DOI 10.17487/RFC7688, November 2015,
<http://www.rfc-editor.org/info/rfc7688>. <http://www.rfc-editor.org/info/rfc7688>.
8.3. URIs
[1] http://www.iana.org/assignments/gmpls-sig-parameters/gmpls-sig-
parameters.xml#gmpls-sig-parameters-3
Authors' Addresses Authors' Addresses
Daniele Ceccarelli Daniele Ceccarelli
Ericsson Ericsson
Torshamnsgatan 21 Torshamnsgatan 21
Kista - Stockholm Kista - Stockholm
Sweden Sweden
Email: daniele.ceccarelli@ericsson.com Email: daniele.ceccarelli@ericsson.com
 End of changes. 21 change blocks. 
44 lines changed or deleted 65 lines changed or added

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