draft-ietf-ccamp-flexible-grid-ospf-ext-05.txt   draft-ietf-ccamp-flexible-grid-ospf-ext-06.txt 
CCAMP Working Group Xian Zhang CCAMP Working Group Xian Zhang
Internet-Draft Haomian Zheng Internet-Draft Haomian Zheng
Intended status: Standards Track Huawei Intended status: Standards Track Huawei
Ramon Casellas Ramon Casellas
CTTC CTTC
O. Gonzalez de Dios O. Gonzalez de Dios
Telefonica Telefonica
D. Ceccarelli D. Ceccarelli
Ericsson Ericsson
Expires: February 10, 2017 August 10, 2016 Expires: March 23, 2017 September 23, 2016
GMPLS OSPF-TE Extensions in support of Flexi-grid DWDM networks GMPLS OSPF-TE Extensions in support of Flexi-grid DWDM networks
draft-ietf-ccamp-flexible-grid-ospf-ext-05.txt draft-ietf-ccamp-flexible-grid-ospf-ext-06.txt
Abstract Abstract
This memo describes the OSPF-TE extensions in support of GMPLS This memo describes the OSPF-TE extensions in support of GMPLS
control of networks that include devices that use the new flexible control of networks that include devices that use the new flexible
optical grid. optical grid.
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.
Internet-Drafts are draft documents valid for a maximum of six Internet-Drafts are draft documents valid for a maximum of six
months and may be updated, replaced, or obsoleted by other months and may be updated, replaced, or obsoleted by other
documents at any time. It is inappropriate to use Internet-Drafts documents at any time. It is inappropriate to use Internet-Drafts
as reference material or to cite them other than as "work in as reference material or to cite them other than as "work in
progress." 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 February 10, 2017. This Internet-Draft will expire on March 23, 2017.
Copyright Notice Copyright Notice
Copyright (c) 2015 IETF Trust and the persons identified as the Copyright (c) 2016 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 carefully, as they describe your rights and restrictions with
respect to this document. Code Components extracted from this respect to this document. Code Components extracted from this
document must include Simplified BSD License text as described in document must include Simplified BSD License text as described in
Section 4.e of the Trust Legal Provisions and are provided without Section 4.e of the Trust Legal Provisions and are provided without
skipping to change at page 14, line 13 skipping to change at page 14, line 13
1 Frequency availability bitmap [This.I-D] 1 Frequency availability bitmap [This.I-D]
6. Implementation Status 6. Implementation Status
[RFC Editor Note: Please remove this entire section prior to [RFC Editor Note: Please remove this entire section prior to
publication as an RFC.] publication as an RFC.]
This section records the status of known implementations of the This section records the status of known implementations of the
protocol defined by this specification at the time of posting of protocol defined by this specification at the time of posting of
this Internet-Draft, and is based on a proposal described in RFC this Internet-Draft, and is based on a proposal described in RFC
6982[RFC6982]. The description of implementations in this section 7942. The description of implementations in this section
is intended to assist the IETF in its decision processes in is intended to assist the IETF in its decision processes in
progressing drafts to RFCs. Please note that the listing of any progressing drafts to RFCs. Please note that the listing of any
individual implementation here does not imply endorsement by the individual implementation here does not imply endorsement by the
IETF. Furthermore, no effort has been spent to verify the IETF. Furthermore, no effort has been spent to verify the
information presented here that was supplied by IETF contributors. information presented here that was supplied by IETF contributors.
This is not intended as, and must not be construed to be, a catalog This is not intended as, and must not be construed to be, a catalog
of available implementations or their features. Readers are advised of available implementations or their features. Readers are advised
to note that other implementations may exist. to note that other implementations may exist.
According to RFC 6982, "this will allow reviewers and working groups According to RFC 7942, "this will allow reviewers and working groups
to assign due consideration to documents that have the benefit of to assign due consideration to documents that have the benefit of
running code, which may serve as evidence of valuable running code, which may serve as evidence of valuable
experimentation and feedback that have made the implemented experimentation and feedback that have made the implemented
protocols more mature. It is up to the individual working groups to protocols more mature." It is up to the individual working groups to
use this information as they see fit. use this information as they see fit.
6.1. Centre Tecnologic de Telecomunicacions de Catalunya (CTTC) 6.1. Centre Tecnologic de Telecomunicacions de Catalunya (CTTC)
Organization Responsible for the Implementation: CTTC - Centre Organization Responsible for the Implementation: CTTC - Centre
Tecnologic de Telecomunicacions de Catalunya (CTTC), Optical Tecnologic de Telecomunicacions de Catalunya (CTTC), Optical
Networks and Systems Department, http://wikiona.cttc.es. Networks and Systems Department, http://wikiona.cttc.es.
Implementation Name and Details: ADRENALINE testbed, Implementation Name and Details: ADRENALINE testbed,
http://networks.cttc.es/experimental-testbeds/ http://networks.cttc.es/experimental-testbeds/
Brief Description: Experimental testbed implementation of Brief Description: Experimental testbed implementation of
GMPLS/PCE control plane. GMPLS/PCE control plane.
Level of Maturity: Implemented as extensions to a mature Level of Maturity: Implemented as extensions to a mature
GMLPS/PCE control plane. It is limited to research / prototyping GMLPS/PCE control plane. It is limited to research / prototyping
stages but it has been used successfully for more than the last five stages but it has been used successfully for more than the last five
years. years.
Coverage: Support for the 64 bit label [FLEC-LBL] for flexi-grid Coverage: Support for the 64 bit label [RFC7699] for flexi-grid
as described in this document, with available label set encoded as as described in this document, with available label set encoded as
bitmap. bitmap.
It is expected that this implementation will evolve to follow the It is expected that this implementation will evolve to follow the
evolution of this document. evolution of this document.
Licensing: Proprietary Licensing: Proprietary
Implementation Experience: Implementation of this document Implementation Experience: Implementation of this document
reports no issues. General implementation experience has been reports no issues. General implementation experience has been
skipping to change at page 16, line 5 skipping to change at page 16, line 5
9. Contributors' Addresses 9. Contributors' Addresses
Adrian Farrel Adrian Farrel
Old Dog Consulting Old Dog Consulting
Email: adrian@olddog.co.uk Email: adrian@olddog.co.uk
Fatai Zhang Fatai Zhang
Huawei Technologies Huawei Technologies
Email: zhangfatai@huawei.com Email: zhangfatai@huawei.com
Lei Wang, Lei Wang,
ZTE Beijing University of Post and Telecommunications
Email: wang.lei@bupt.edu.cn Email: wang.lei@bupt.edu.cn
Guoying Zhang, Guoying Zhang,
China Academy of Telecom Research China Academy of Telecom Research
Email: zhangguoying@ritt.cn Email: zhangguoying@ritt.cn
10. References 10. References
10.1. Normative References 10.1. Normative References
[RFC2119] S. Bradner, "Key words for use in RFCs to indicate [RFC2119] S. Bradner, "Key words for use in RFCs to indicate
requirements levels", RFC 2119, March 1997. requirements levels", RFC 2119, March 1997.
[G.694.1] ITU-T Recommendation G.694.1 (revision 2), "Spectral grids [G.694.1] ITU-T Recommendation G.694.1 (revision 2), "Spectral grids
for WDM applications: DWDM frequency grid", February 2012. for WDM applications: DWDM frequency grid", February 2012.
[RFC4203] K. Kompella, Y. Rekhter, " OSPF Extensions in Support of
Generalized Multi-Protocol Label Switching (GMPLS)",
October 2005.
[RFC7579] Bernstein, G., Lee, Y., Li, D., and W. Imajuku, "General [RFC7579] Bernstein, G., Lee, Y., Li, D., and W. Imajuku, "General
Network Element Constraint Encoding for GMPLS Controlled Network Element Constraint Encoding for GMPLS Controlled
Networks", RFC 7579, June 2015. Networks", RFC 7579, June 2015.
[RFC7580] F. Zhang, Y. Lee, J. Han, G. Bernstein and Y. Xu, "OSPF-TE [RFC7580] F. Zhang, Y. Lee, J. Han, G. Bernstein and Y. Xu, "OSPF-TE
Extensions for General Network Element Constraints ", RFC Extensions for General Network Element Constraints ", RFC
7580, June 2015. 7580, June 2015.
[RFC6205] T. Otani and D. Li, "Generalized Labels for Lambda-Switch- [RFC6205] T. Otani and D. Li, "Generalized Labels for Lambda-Switch-
Capable (LSC) Label Switching Routers", RFC 6205, March Capable (LSC) Label Switching Routers", RFC 6205, March
skipping to change at page 17, line 16 skipping to change at page 17, line 16
Ceccarelli, D., and I. Hussain, "Framework and Ceccarelli, D., and I. Hussain, "Framework and
Requirements for GMPLS based control of Flexi-grid DWDM Requirements for GMPLS based control of Flexi-grid DWDM
networks', RFC 7698, August 2015. networks', RFC 7698, August 2015.
[RFC7688] Y. Lee and G. Bernstein, "GMPLS OSPF Enhancement for [RFC7688] Y. Lee and G. Bernstein, "GMPLS OSPF Enhancement for
Signal and Network Element Compatibility for Wavelength Signal and Network Element Compatibility for Wavelength
Switched Optical Networks ", RFC7688, August 2015. Switched Optical Networks ", RFC7688, August 2015.
[RFC2328] Moy, J., "OSPF Version 2", STD 54, RFC 2328, April 1998. [RFC2328] Moy, J., "OSPF Version 2", STD 54, RFC 2328, April 1998.
[RFC3630] D. Katz, K. Kompella, D. Yeung, " Traffic Engineering
(TE) Extensions to OSPF Version 2", September 2003.
[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
Protocols (KARP) Design Guide", RFC 6863, March 2013. Protocols (KARP) Design Guide", RFC 6863, March 2013.
Authors' Addresses Authors' Addresses
Xian Zhang Xian Zhang
Huawei Technologies Huawei Technologies
Email: zhang.xian@huawei.com Email: zhang.xian@huawei.com
 End of changes. 12 change blocks. 
12 lines changed or deleted 19 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/