| < draft-ietf-ospf-ospfv2-hbit-03.txt | draft-ietf-ospf-ospfv2-hbit-04.txt > | |||
|---|---|---|---|---|
| OSPF K. Patel | OSPF K. Patel | |||
| Internet-Draft Arrcus | Internet-Draft Arrcus | |||
| Intended status: Standards Track P. Pillay-Esnault | Intended status: Standards Track P. Pillay-Esnault | |||
| Expires: December 16, 2017 Huawei Technologies | Expires: August 1, 2018 Huawei Technologies | |||
| M. Bhardwaj | M. Bhardwaj | |||
| S. Bayraktar | S. Bayraktar | |||
| Cisco Systems | Cisco Systems | |||
| June 14, 2017 | January 28, 2018 | |||
| H-bit Support for OSPFv2 | H-bit Support for OSPFv2 | |||
| draft-ietf-ospf-ospfv2-hbit-03 | draft-ietf-ospf-ospfv2-hbit-04 | |||
| Abstract | Abstract | |||
| OSPFv3 defines an option field for router-LSAs known as a R-bit in | OSPFv3 defines an option field for router-LSAs known as a R-bit in | |||
| RFC5340. If the R-bit is clear, an OSPFv3 router can participate in | RFC5340. If the R-bit is clear, an OSPFv3 router can participate in | |||
| OSPF topology distribution without acting as a forwarder to forward | OSPF topology distribution without acting as a forwarder to forward | |||
| the transit traffic. In such cases, an OSPF router would only accept | the transit traffic. In such cases, an OSPF router would only accept | |||
| traffic intended for local delivery. This draft defines R-bit | traffic intended for local delivery. This draft defines R-bit | |||
| functionality for OSPFv2 defined in RFC2328. | functionality for OSPFv2 defined in RFC2328. | |||
| 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 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 December 16, 2017. | This Internet-Draft will expire on August 1, 2018. | |||
| Copyright Notice | Copyright Notice | |||
| Copyright (c) 2017 IETF Trust and the persons identified as the | Copyright (c) 2018 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 | (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 | |||
| described in the Simplified BSD License. | described in the Simplified BSD License. | |||
| Table of Contents | Table of Contents | |||
| 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 | 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 | |||
| skipping to change at page 7, line 16 ¶ | skipping to change at page 7, line 16 ¶ | |||
| Initial Version: April 23 2015 | Initial Version: April 23 2015 | |||
| 11. References | 11. References | |||
| 11.1. Normative References | 11.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, | |||
| <http://www.rfc-editor.org/info/rfc2119>. | <https://www.rfc-editor.org/info/rfc2119>. | |||
| [RFC2328] Moy, J., "OSPF Version 2", STD 54, RFC 2328, | [RFC2328] Moy, J., "OSPF Version 2", STD 54, RFC 2328, | |||
| DOI 10.17487/RFC2328, April 1998, | DOI 10.17487/RFC2328, April 1998, | |||
| <http://www.rfc-editor.org/info/rfc2328>. | <https://www.rfc-editor.org/info/rfc2328>. | |||
| [RFC5340] Coltun, R., Ferguson, D., Moy, J., and A. Lindem, "OSPF | [RFC5340] Coltun, R., Ferguson, D., Moy, J., and A. Lindem, "OSPF | |||
| for IPv6", RFC 5340, DOI 10.17487/RFC5340, July 2008, | for IPv6", RFC 5340, DOI 10.17487/RFC5340, July 2008, | |||
| <http://www.rfc-editor.org/info/rfc5340>. | <https://www.rfc-editor.org/info/rfc5340>. | |||
| [RFC7770] Lindem, A., Ed., Shen, N., Vasseur, JP., Aggarwal, R., and | [RFC7770] Lindem, A., Ed., Shen, N., Vasseur, JP., Aggarwal, R., and | |||
| S. Shaffer, "Extensions to OSPF for Advertising Optional | S. Shaffer, "Extensions to OSPF for Advertising Optional | |||
| Router Capabilities", RFC 7770, DOI 10.17487/RFC7770, | Router Capabilities", RFC 7770, DOI 10.17487/RFC7770, | |||
| February 2016, <http://www.rfc-editor.org/info/rfc7770>. | February 2016, <https://www.rfc-editor.org/info/rfc7770>. | |||
| 11.2. Informative References | 11.2. Informative References | |||
| [I-D.ietf-idr-bgp-optimal-route-reflection] | [I-D.ietf-idr-bgp-optimal-route-reflection] | |||
| Raszuk, R., Cassar, C., Aman, E., Decraene, B., Litkowski, | Raszuk, R., Cassar, C., Aman, E., Decraene, B., Litkowski, | |||
| S., and K. Wang, "BGP Optimal Route Reflection (BGP-ORR)", | S., and K. Wang, "BGP Optimal Route Reflection (BGP-ORR)", | |||
| draft-ietf-idr-bgp-optimal-route-reflection-13 (work in | draft-ietf-idr-bgp-optimal-route-reflection-13 (work in | |||
| progress), January 2017. | progress), January 2017. | |||
| [RFC6987] Retana, A., Nguyen, L., Zinin, A., White, R., and D. | [RFC6987] Retana, A., Nguyen, L., Zinin, A., White, R., and D. | |||
| McPherson, "OSPF Stub Router Advertisement", RFC 6987, | McPherson, "OSPF Stub Router Advertisement", RFC 6987, | |||
| DOI 10.17487/RFC6987, September 2013, | DOI 10.17487/RFC6987, September 2013, | |||
| <http://www.rfc-editor.org/info/rfc6987>. | <https://www.rfc-editor.org/info/rfc6987>. | |||
| Authors' Addresses | Authors' Addresses | |||
| Keyur Patel | Keyur Patel | |||
| Arrcus | Arrcus | |||
| Email: keyur@arrcus.com | Email: keyur@arrcus.com | |||
| Padma Pillay-Esnault | Padma Pillay-Esnault | |||
| Huawei Technologies | Huawei Technologies | |||
| 2330 Central Expressway | 2330 Central Expressway | |||
| End of changes. 12 change blocks. | ||||
| 12 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/ | ||||