draft-ietf-lsr-pce-discovery-security-support-03.txt | draft-ietf-lsr-pce-discovery-security-support-04.txt | |||
---|---|---|---|---|
PCE working group D. Lopez | PCE working group D. Lopez | |||
Internet-Draft Telefonica I+D | Internet-Draft Telefonica I+D | |||
Updates: 5088,5089 (if approved) Q. Wu | Updates: 5088,5089 (if approved) Q. Wu | |||
Intended status: Standards Track D. Dhody | Intended status: Standards Track D. Dhody | |||
Expires: May 2, 2020 Z. Wang | Expires: April 24, 2021 Q. Ma | |||
Huawei | Huawei | |||
D. King | D. King | |||
Old Dog Consulting | Old Dog Consulting | |||
October 30, 2019 | October 21, 2020 | |||
IGP extension for PCEP security capability support in the PCE discovery | IGP extension for PCEP security capability support in the PCE discovery | |||
draft-ietf-lsr-pce-discovery-security-support-03 | draft-ietf-lsr-pce-discovery-security-support-04 | |||
Abstract | Abstract | |||
When a Path Computation Element (PCE) is a Label Switching Router | When a Path Computation Element (PCE) is a Label Switching Router | |||
(LSR) participating in the Interior Gateway Protocol (IGP), or even a | (LSR) participating in the Interior Gateway Protocol (IGP), or even a | |||
server participating in IGP, its presence and path computation | server participating in IGP, its presence and path computation | |||
capabilities can be advertised using IGP flooding. The IGP | capabilities can be advertised using IGP flooding. The IGP | |||
extensions for PCE discovery (RFC 5088 and RFC 5089) define a method | extensions for PCE discovery (RFC 5088 and RFC 5089) define a method | |||
to advertise path computation capabilities using IGP flooding for | to advertise path computation capabilities using IGP flooding for | |||
OSPF and IS-IS respectively. However these specifications lack a | OSPF and IS-IS respectively. However these specifications lack a | |||
skipping to change at page 2, line 4 ¶ | skipping to change at page 2, line 4 ¶ | |||
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 May 2, 2020. | This Internet-Draft will expire on April 24, 2021. | |||
Copyright Notice | Copyright Notice | |||
Copyright (c) 2019 IETF Trust and the persons identified as the | Copyright (c) 2020 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 7, line 29 ¶ | skipping to change at page 7, line 29 ¶ | |||
7 KEY-CHAIN-NAME [This.I.D] | 7 KEY-CHAIN-NAME [This.I.D] | |||
This registry is also used by IS-IS PCED sub-TLV. | This registry is also used by IS-IS PCED sub-TLV. | |||
9. Acknowledgments | 9. Acknowledgments | |||
The authors of this document would also like to thank Acee Lindem, | The authors of this document would also like to thank Acee Lindem, | |||
Julien Meuric, Les Ginsberg, Aijun Wang, Adrian Farrel for the review | Julien Meuric, Les Ginsberg, Aijun Wang, Adrian Farrel for the review | |||
and comments. | and comments. | |||
The authors would also like to speical thank Michale Wang for his | ||||
major contributions to the initial version. | ||||
10. References | 10. References | |||
10.1. Normative References | 10.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, | Requirement Levels", BCP 14, RFC 2119, | |||
DOI 10.17487/RFC2119, March 1997, | DOI 10.17487/RFC2119, March 1997, | |||
<https://www.rfc-editor.org/info/rfc2119>. | <https://www.rfc-editor.org/info/rfc2119>. | |||
[RFC5088] Le Roux, JL., Ed., Vasseur, JP., Ed., Ikejiri, Y., and R. | [RFC5088] Le Roux, JL., Ed., Vasseur, JP., Ed., Ikejiri, Y., and R. | |||
skipping to change at page 9, line 19 ¶ | skipping to change at page 9, line 27 ¶ | |||
Authors' Addresses | Authors' Addresses | |||
Diego R. Lopez | Diego R. Lopez | |||
Telefonica I+D | Telefonica I+D | |||
Spain | Spain | |||
Email: diego.r.lopez@telefonica.com | Email: diego.r.lopez@telefonica.com | |||
Qin Wu | Qin Wu | |||
Huawei Technologies | Huawei Technologies | |||
12 Mozhou East Road, Jiangning District | 101 Software Avenue, Yuhua District | |||
Nanjing, Jiangsu 210012 | Nanjing, Jiangsu 210012 | |||
China | China | |||
Email: bill.wu@huawei.com | Email: bill.wu@huawei.com | |||
Dhruv Dhody | Dhruv Dhody | |||
Huawei Technologies | Huawei Technologies | |||
Divyashree Techno Park, Whitefield | Divyashree Techno Park, Whitefield | |||
Bangalore, Karnataka 560037 | Bangalore, Karnataka 560037 | |||
India | India | |||
Email: dhruv.ietf@gmail.com | Email: dhruv.ietf@gmail.com | |||
Michael Wang | Qiufang Ma | |||
Huawei | Huawei | |||
12 Mozhou East Road, Jiangning District | 101 Software Avenue, Yuhua District | |||
Nanjing, Jiangsu 210012 | Nanjing, Jiangsu 210012 | |||
China | China | |||
Email: wangzitao@huawei.com | Email: maqiufang1@huawei.com | |||
Daniel King | Daniel King | |||
Old Dog Consulting | Old Dog Consulting | |||
UK | UK | |||
Email: daniel@olddog.co.uk | Email: daniel@olddog.co.uk | |||
End of changes. 10 change blocks. | ||||
10 lines changed or deleted | 12 lines changed or added | |||
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/ |