draft-ietf-ccamp-ospf-availability-extension-12.txt   draft-ietf-ccamp-ospf-availability-extension-13.txt 
Network Working Group H. Long, M.Ye Network Working Group H. Long, M.Ye
Internet Draft Huawei Technologies Co., Ltd Internet Draft Huawei Technologies Co., Ltd
Intended status: Standards Track G. Mirsky Intended status: Standards Track G. Mirsky
ZTE ZTE
A.D'Alessandro A.D'Alessandro
Telecom Italia S.p.A Telecom Italia S.p.A
H. Shah H. Shah
Ciena Ciena
Expires: May 2018 November 10, 2017 Expires: June 2018 December 5, 2017
OSPF-Traffic Engineering Link Availability Extension for Links with OSPF-Traffic Engineering Link Availability Extension for Links with
Variable Discrete Bandwidth Variable Discrete Bandwidth
draft-ietf-ccamp-ospf-availability-extension-12.txt draft-ietf-ccamp-ospf-availability-extension-13.txt
Abstract Abstract
A network may contain links with variable discrete bandwidth, e.g., A network may contain links with variable discrete bandwidth, e.g.,
copper, radio, etc. The bandwidth of such links may change copper, radio, etc. The bandwidth of such links may change
discretely in reaction to changing external environment. discretely in reaction to changing external environment.
Availability is typically used for describing such links during Availability is typically used for describing such links during
network planning. This document defines a new type of the network planning. This document defines a new type of the
Generalized Switching Capability-specific information (SCSI) TLV to Generalized Switching Capability-specific information (SCSI) TLV to
extend the Generalized Multi-Protocol Label Switching (GMPLS) Open extend the Generalized Multi-Protocol Label Switching (GMPLS) Open
skipping to change at page 2, line 16 skipping to change at page 2, line 16
months and may be updated, replaced, or obsoleted by other documents months and may be updated, replaced, or obsoleted by other documents
at any time. It is inappropriate to use Internet-Drafts as at any time. It is inappropriate to use Internet-Drafts as
reference material or to cite them other than as "work in progress." reference 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 April 10, 2018. This Internet-Draft will expire on June 5, 2018.
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
skipping to change at page 2, line 42 skipping to change at page 2, line 42
Table of Contents Table of Contents
1. Introduction ................................................ 3 1. Introduction ................................................ 3
2. Acronyms .................................................... 3 2. Acronyms .................................................... 3
3. Overview .................................................... 4 3. Overview .................................................... 4
4. TE Metric Extension to OSPF-TE............................... 4 4. TE Metric Extension to OSPF-TE............................... 4
4.1. Availability SCSI-TLV................................... 4 4.1. Availability SCSI-TLV................................... 4
4.2. Processing Procedures................................... 5 4.2. Processing Procedures................................... 5
5. Security Considerations...................................... 6 5. Security Considerations...................................... 6
6. IANA Considerations ......................................... 7 6. IANA Considerations ......................................... 6
7. References .................................................. 7 7. References .................................................. 7
7.1. Normative References.................................... 7 7.1. Normative References.................................... 7
7.2. Informative References.................................. 8 7.2. Informative References.................................. 7
8. Acknowledgments ............................................. 8 8. Acknowledgments ............................................. 8
Conventions used in this document Conventions used in this document
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED","MAY", and "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED","MAY", and
"OPTIONAL" in this document are to be interpreted as described in "OPTIONAL" in this document are to be interpreted as described in
BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all
capitals, as shown here. capitals, as shown here.
1. Introduction 1. Introduction
skipping to change at page 4, line 46 skipping to change at page 4, line 46
Note, the mechanisms described in this document only distribute Note, the mechanisms described in this document only distribute
availability information. The methods for measuring the information availability information. The methods for measuring the information
or using the information for route computation are outside the scope or using the information for route computation are outside the scope
of this document. of this document.
4. TE Metric Extension to OSPF-TE 4. TE Metric Extension to OSPF-TE
4.1. Availability SCSI-TLV 4.1. Availability SCSI-TLV
The Generalized SCSI is defined in [I-D. ietf-teas-gmpls-scsi]. The The Generalized SCSI is defined in [RFC8258]. The Availability TLV
Availability TLV defined in this document is a new type of defined in this document is a new type of Generalized SCSI-TLV. The
Generalized SCSI-TLV. The Availability SCSI-TLV can be included for Availability SCSI-TLV can be included for one or more times. The
one or more times. The Availability SCSI-TLV has the following Availability SCSI-TLV has the following format:
format:
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 | Length | | Type | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Availability level | | Availability level |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| LSP Bandwidth at Availability level n | | LSP Bandwidth at Availability level n |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 6, line 25 skipping to change at page 6, line 25
bandwidth link with the highest availability value. bandwidth link with the highest availability value.
Only one Availability SCSI-TLV for the specific availability level Only one Availability SCSI-TLV for the specific availability level
SHOULD be sent. If multiple are present, the Availability SCSI-TLV SHOULD be sent. If multiple are present, the Availability SCSI-TLV
with the lowest bandwidth value SHALL be processed. If an with the lowest bandwidth value SHALL be processed. If an
Availability SCSI-TLV with an invalid value (e.g., large than 1) is Availability SCSI-TLV with an invalid value (e.g., large than 1) is
received, the Availability SCSI-TLV will be ignored. received, the Availability SCSI-TLV will be ignored.
5. Security Considerations 5. Security Considerations
This document does not introduce security issues beyond those This document specifies the contents of Opaque LSAs in OSPFv2.
discussed in [RFC4203]. As with [RFC4203], it specifies the content Tampering with GMPLS TE LSAs may have an effect on traffic
of an Opaque LSAs in OSPFv2. As Opaque LSAs are not used for engineering computations. [RFC3630] suggests mechanisms such as
Shortest Path First (SPF) computation or normal routing, the [RFC2154] to protect the transmission of this information, and those
extensions specified here have no direct effect on IP routing. or other mechanisms should be used to secure and/or authenticate the
Tampering with GMPLS TE LSAs may have an impact on the ability to information carried in the Opaque LSAs. An analysis of the security
set up connections in the underlying data plane network. As the of OSPF is provided in [RFC6863] and applies to the extensions to
additional availability information may represent information that OSPF as described in this document. Any new mechanisms developed to
an operator may wish to keep private, consideration should be given protect the transmission of information carried in Opaque LSAs will
to securing this information. [RFC3630] notes that the security also automatically protect the extensions defined in this document.
mechanisms described in [RFC2328] apply to Opaque LSAs carried in
OSPFv2. An analysis of the security of OSPF is provided in
[RFC6863] and applies to the extensions to OSPF as described in this
document. Any new mechanisms developed to protect the transmission
of information carried in Opaque LSAs will also automatically
protect the extensions defined in this document.
Please refer to [RFC5920] for details on security threats; defensive Please refer to [RFC5920] for details on security threats; defensive
techniques; monitoring, detection, and reporting of security techniques; monitoring, detection, and reporting of security
attacks; and requirements. attacks; and requirements.
6. IANA Considerations 6. IANA Considerations
This document introduces a new type for availability of the This document introduces a new type for availability of the
Generalized SCSI-TLV of the TE Link TLV in the TE Opaque LSA for Generalized SCSI-TLV of the TE Link TLV in the TE Opaque LSA for
OSPF v2. Technology-specific documents will reference this document OSPF v2. Technology-specific documents will reference this document
to describe specific use of this Availability SCSI-TLV. to describe specific use of this Availability SCSI-TLV.
IANA has created a registry called the "Generalized SCSI (Switching IANA has created a registry called the "Generalized SCSI (Switching
Capability Specific Information) TLVs Types" registry. The registry Capability Specific Information) TLVs Types" registry. The registry
is needed to be updated to include the Availability SCSI-TLV. This is needed to be updated to include the Availability SCSI-TLV. This
document proposes a suggested value for the Availability SCSI-TLV; document proposes a suggested value for the Availability SCSI-TLV;
it is requested that the suggested value be granted by IANA. it is requested that the suggested value be granted by IANA.
Note (Please REMOVE this note before publication): the registry will Note (Please REMOVE this note before publication): the registry will
be created by draft-ietf-teas-gmpls-scsi. The requested value should be created by [RFC8258]. The requested value should be added to it
be added to it when it is created. when it is created.
Type Description Reference Type Description Reference
--- ------------------ ----------- --- ------------------ -----------
0x01 Availability [This ID] 0x01 Availability [This ID]
7. References 7. References
7.1. Normative References 7.1. Normative References
[I-D. ietf-teas-gmpls-scsi] Ceccarelli, D. and Berger, L., [RFC8258] Ceccarelli, D. and Berger, L., "Generalized Routing
"Generalized Routing Interface Switching Capability Interface Switching Capability Descriptor Switching
Descriptor Switching Capability Specific Information", Capability Specific Information", RFC 8258, October, 2017.
Work in Progress, August, 2017.
[RFC4202] Kompella, K. and Rekhter, Y. (Editors), "Routing [RFC4202] Kompella, K. and Rekhter, Y. (Editors), "Routing
Extensions in Support of Generalized Multi-Protocol Label Extensions in Support of Generalized Multi-Protocol Label
Switching (GMPLS)", RFC 4202, October 2005. Switching (GMPLS)", RFC 4202, October 2005.
[RFC4203] Kompella, K., Ed., and Y. Rekhter, Ed., "OSPF Extensions [RFC4203] Kompella, K., Ed., and Y. Rekhter, Ed., "OSPF Extensions
in Support of Generalized Multi-Protocol Label Switching in Support of Generalized Multi-Protocol Label Switching
(GMPLS)", RFC 4203, October 2005. (GMPLS)", RFC 4203, October 2005.
[IEEE754-2008] IEEE standards, "IEEE Standard for Floating-Point [IEEE754-2008] IEEE standards, "IEEE Standard for Floating-Point
Arithmetic", IEEE Standard 754, August 2008 Arithmetic", IEEE Standard 754, August 2008
7.2. Informative References 7.2. Informative 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", RFC 2119, March 1997. Requirement Levels", RFC 2119, March 1997.
[RFC2328] Moy, J., "OSPF Version 2", STD 54, RFC 2328, April 1998. [RFC2154] Murphy, S., Badger, M., Wellington, B., "OSPF with Digital
Signatures", RFC2154, June 1997.
[RFC3630] Katz, D., Kompella, K., and D. Yeung, "Traffic Engineering [RFC3630] Katz, D., Kompella, K., and D. Yeung, "Traffic Engineering
(TE) Extensions to OSPF Version 2", RFC 3630, September (TE) Extensions to OSPF Version 2", RFC 3630, September
2003. 2003.
[RFC5920] Fang, L., "Security Framework for MPLS and GMPLS [RFC5920] Fang, L., "Security Framework for MPLS and GMPLS
Networks", RFC 5920, July 2010. Networks", RFC 5920, July 2010.
[RFC6863] Hartman, S. and D. Zhang, "Analysis of OSPF Security [RFC6863] Hartman, S. and D. Zhang, "Analysis of OSPF Security
According to the Keying and Authentication for Routing According to the Keying and Authentication for Routing
 End of changes. 10 change blocks. 
33 lines changed or deleted 26 lines changed or added

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