| < draft-xu-lsr-isis-flooding-reduction-in-msdc-00.txt | draft-xu-lsr-isis-flooding-reduction-in-msdc-01.txt > | |||
|---|---|---|---|---|
| Network Working Group X. Xu | Network Working Group X. Xu | |||
| Internet-Draft Alibaba Inc | Internet-Draft Alibaba, Inc | |||
| Intended status: Standards Track L. Fang | Intended status: Standards Track L. Fang | |||
| Expires: October 19, 2018 Expedia, Inc | Expires: April 21, 2019 Expedia, Inc | |||
| J. Tantsura | J. Tantsura | |||
| Nuage Networks | Apstra, Inc. | |||
| S. Ma | S. Ma | |||
| Juniper | Juniper | |||
| April 17, 2018 | October 18, 2018 | |||
| IS-IS Flooding Reduction in MSDC | IS-IS Flooding Reduction in MSDC | |||
| draft-xu-lsr-isis-flooding-reduction-in-msdc-00 | draft-xu-lsr-isis-flooding-reduction-in-msdc-01 | |||
| Abstract | Abstract | |||
| IS-IS is commonly used as an underlay routing protocol for MSDC | IS-IS is commonly used as an underlay routing protocol for MSDC | |||
| (Massively Scalable Data Center) networks. For a given IS-IS router | (Massively Scalable Data Center) networks. For a given IS-IS router | |||
| within the CLOS topology, it would receive multiple copies of exactly | within the CLOS topology, it would receive multiple copies of exactly | |||
| the same LSP from multiple IS-IS neighbors. In addition, two IS-IS | the same LSP from multiple IS-IS neighbors. In addition, two IS-IS | |||
| neighbors may send each other the same LSP simultaneously. The | neighbors may send each other the same LSP simultaneously. The | |||
| unneccessary link-state information flooding wastes the precious | unneccessary link-state information flooding wastes the precious | |||
| process resource of IS-IS routers greatly due to the fact that there | process resource of IS-IS routers greatly due to the fact that there | |||
| skipping to change at page 2, line 7 ¶ | skipping to change at page 2, line 7 ¶ | |||
| 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 October 19, 2018. | This Internet-Draft will expire on April 21, 2019. | |||
| Copyright Notice | Copyright Notice | |||
| Copyright (c) 2018 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 | |||
| (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 | |||
| skipping to change at page 6, line 14 ¶ | skipping to change at page 6, line 14 ¶ | |||
| 7.2. Informative References | 7.2. Informative References | |||
| [RFC4136] Pillay-Esnault, P., "OSPF Refresh and Flooding Reduction | [RFC4136] Pillay-Esnault, P., "OSPF Refresh and Flooding Reduction | |||
| in Stable Topologies", RFC 4136, DOI 10.17487/RFC4136, | in Stable Topologies", RFC 4136, DOI 10.17487/RFC4136, | |||
| July 2005, <https://www.rfc-editor.org/info/rfc4136>. | July 2005, <https://www.rfc-editor.org/info/rfc4136>. | |||
| Authors' Addresses | Authors' Addresses | |||
| Xiaohu Xu | Xiaohu Xu | |||
| Alibaba Inc | Alibaba, Inc | |||
| Email: xiaohu.xxh@alibaba-inc.com | Email: xiaohu.xxh@alibaba-inc.com | |||
| Luyuan Fang | Luyuan Fang | |||
| Expedia, Inc | Expedia, Inc | |||
| Email: luyuanf@gmail.com | Email: luyuanf@gmail.com | |||
| Jeff Tantsura | Jeff Tantsura | |||
| Nuage Networks | Apstra, Inc. | |||
| Email: jefftant@gmail.com | Email: jefftant.ietf@gmail.com | |||
| Shaowen Ma | Shaowen Ma | |||
| Juniper | Juniper | |||
| Email: mashao@juniper.net | Email: mashao@juniper.net | |||
| End of changes. 9 change blocks. | ||||
| 9 lines changed or deleted | 9 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/ | ||||