draft-ietf-lsr-isis-extended-hierarchy-04.txt   draft-ietf-lsr-isis-extended-hierarchy-05.txt 
Internet Engineering Task Force T. Li Internet Engineering Task Force T. Li
Internet-Draft Arista Networks Internet-Draft Arista Networks
Intended status: Standards Track L. Ginsberg Intended status: Standards Track L. Ginsberg
Expires: January 1, 2022 P. Wells Expires: June 29, 2022 P. Wells
Cisco Systems Cisco Systems
June 30, 2021 December 26, 2021
IS-IS Extended Hierarchy IS-IS Extended Hierarchy
draft-ietf-lsr-isis-extended-hierarchy-04 draft-ietf-lsr-isis-extended-hierarchy-05
Abstract Abstract
The IS-IS routing protocol was originally defined with a two level The IS-IS routing protocol was originally defined with a two level
hierarchical structure. This was adequate for the networks at the hierarchical structure. This was adequate for the networks at the
time. As we continue to expand the scale of our networks, it is time. As we continue to expand the scale of our networks, it is
apparent that additional hierarchy would be a welcome degree of apparent that additional hierarchy would be a welcome degree of
flexibility in network design. flexibility in network design.
This document defines IS-IS Levels 3 through 8. This document defines IS-IS Levels 3 through 8.
skipping to change at page 1, line 38 skipping to change at page 1, line 38
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 January 1, 2022. This Internet-Draft will expire on June 29, 2022.
Copyright Notice Copyright Notice
Copyright (c) 2021 IETF Trust and the persons identified as the Copyright (c) 2021 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 16, line 20 skipping to change at page 16, line 20
themselves. This document proposes no changes to those security themselves. This document proposes no changes to those security
architectures. architectures.
13. Normative References 13. Normative References
[ISO10589] [ISO10589]
International Organization for Standardization, International Organization for Standardization,
"Intermediate System to Intermediate System Intra-Domain "Intermediate System to Intermediate System Intra-Domain
Routing Exchange Protocol for use in Conjunction with the Routing Exchange Protocol for use in Conjunction with the
Protocol for Providing the Connectionless-mode Network Protocol for Providing the Connectionless-mode Network
Service (ISO 8473)", ISO/IEC 10589:2002, Nov. 2002. Service (ISO 8473)", ISO/IEC 10589:2002, November 2002.
[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>.
[RFC5309] Shen, N., Ed. and A. Zinin, Ed., "Point-to-Point Operation [RFC5309] Shen, N., Ed. and A. Zinin, Ed., "Point-to-Point Operation
over LAN in Link State Routing Protocols", RFC 5309, over LAN in Link State Routing Protocols", RFC 5309,
DOI 10.17487/RFC5309, October 2008, DOI 10.17487/RFC5309, October 2008,
<https://www.rfc-editor.org/info/rfc5309>. <https://www.rfc-editor.org/info/rfc5309>.
 End of changes. 5 change blocks. 
5 lines changed or deleted 5 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/