| < draft-chen-ospf-tts-02.txt | draft-chen-ospf-tts-03.txt > | |||
|---|---|---|---|---|
| Internet Engineering Task Force H. Chen | Internet Engineering Task Force H. Chen | |||
| Internet-Draft Huawei Technologies | Internet-Draft Futurewei | |||
| Intended status: Standards Track M. Toy | Intended status: Standards Track M. Toy | |||
| Expires: January 21, 2018 Verizon | Expires: April 4, 2020 Verizon | |||
| V. Liu | V. Liu | |||
| China Mobile | China Mobile | |||
| L. Liu | L. Liu | |||
| Fijitsu | Fijitsu | |||
| July 20, 2017 | October 2, 2019 | |||
| Extensions to OSPF for Temporal LSP | Extensions to OSPF for Temporal LSP | |||
| draft-chen-ospf-tts-02.txt | draft-chen-ospf-tts-03.txt | |||
| Abstract | Abstract | |||
| This document specifies extensions to OSPF for distributing Traffic | This document specifies extensions to OSPF for distributing Traffic | |||
| Engineering (TE) information on a link in a sequence of time | Engineering (TE) information on a link in a sequence of time | |||
| intervals. | intervals. | |||
| 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 | |||
| skipping to change at page 1, line 37 ¶ | skipping to change at page 1, line 37 ¶ | |||
| 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 January 21, 2018. | This Internet-Draft will expire on April 4, 2020. | |||
| Copyright Notice | Copyright Notice | |||
| Copyright (c) 2017 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 | |||
| (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 | |||
| skipping to change at page 10, line 30 ¶ | skipping to change at page 10, line 30 ¶ | |||
| The author would like to thank people for their valuable comments on | The author would like to thank people for their valuable comments on | |||
| this draft. | this draft. | |||
| 9. References | 9. References | |||
| 9.1. Normative References | 9.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, DOI 10.17487/ | |||
| RFC2119, March 1997, | RFC2119, March 1997, | |||
| <http://www.rfc-editor.org/info/rfc2119>. | <https://www.rfc-editor.org/info/rfc2119>. | |||
| [RFC2328] Moy, J., "OSPF Version 2", STD 54, RFC 2328, DOI 10.17487/ | [RFC2328] Moy, J., "OSPF Version 2", STD 54, RFC 2328, DOI 10.17487/ | |||
| RFC2328, April 1998, | RFC2328, April 1998, | |||
| <http://www.rfc-editor.org/info/rfc2328>. | <https://www.rfc-editor.org/info/rfc2328>. | |||
| [RFC5250] Berger, L., Bryskin, I., Zinin, A., and R. Coltun, "The | [RFC5250] Berger, L., Bryskin, I., Zinin, A., and R. Coltun, "The | |||
| OSPF Opaque LSA Option", RFC 5250, DOI 10.17487/RFC5250, | OSPF Opaque LSA Option", RFC 5250, DOI 10.17487/RFC5250, | |||
| July 2008, <http://www.rfc-editor.org/info/rfc5250>. | July 2008, <https://www.rfc-editor.org/info/rfc5250>. | |||
| [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, | (TE) Extensions to OSPF Version 2", RFC 3630, | |||
| DOI 10.17487/RFC3630, September 2003, | DOI 10.17487/RFC3630, September 2003, | |||
| <http://www.rfc-editor.org/info/rfc3630>. | <https://www.rfc-editor.org/info/rfc3630>. | |||
| 9.2. Informative References | 9.2. Informative References | |||
| [RFC3209] Awduche, D., Berger, L., Gan, D., Li, T., Srinivasan, V., | [RFC3209] Awduche, D., Berger, L., Gan, D., Li, T., Srinivasan, V., | |||
| and G. Swallow, "RSVP-TE: Extensions to RSVP for LSP | and G. Swallow, "RSVP-TE: Extensions to RSVP for LSP | |||
| Tunnels", RFC 3209, DOI 10.17487/RFC3209, December 2001, | Tunnels", RFC 3209, DOI 10.17487/RFC3209, December 2001, | |||
| <http://www.rfc-editor.org/info/rfc3209>. | <https://www.rfc-editor.org/info/rfc3209>. | |||
| Authors' Addresses | Authors' Addresses | |||
| Huaimo Chen | Huaimo Chen | |||
| Huawei Technologies | Futurewei | |||
| Boston, MA | Boston, MA | |||
| US | US | |||
| Email: huaimo.chen@huawei.com | Email: huaimo.chen@futurewei.com | |||
| Mehmet Toy | Mehmet Toy | |||
| Verizon | Verizon | |||
| USA | USA | |||
| Email: mehmet.toy@verizon.com | Email: mehmet.toy@verizon.com | |||
| Vic Liu | Vic Liu | |||
| China Mobile | China Mobile | |||
| No.32 Xuanwumen West Street, Xicheng District | No.32 Xuanwumen West Street, Xicheng District | |||
| End of changes. 13 change blocks. | ||||
| 13 lines changed or deleted | 13 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/ | ||||