draft-ietf-isis-rfc4971bis-02.txt   draft-ietf-isis-rfc4971bis-03.txt 
Networking Working Group L. Ginsberg Networking Working Group L. Ginsberg
Internet-Draft S. Previdi Internet-Draft S. Previdi
Intended status: Standards Track Cisco Systems Obsoletes: 4971 (if approved) Cisco Systems
Expires: February 11, 2017 M. Chen Intended status: Standards Track M. Chen
Huawei Technologies Co., Ltd Expires: February 16, 2017 Huawei Technologies Co., Ltd
August 10, 2016 August 15, 2016
IS-IS Extensions for Advertising Router Info IS-IS Extensions for Advertising Router Info
draft-ietf-isis-rfc4971bis-02.txt draft-ietf-isis-rfc4971bis-03.txt
Abstract Abstract
This document defines a new optional Intermediate System to This document defines a new optional Intermediate System to
Intermediate System (IS-IS) TLV named CAPABILITY, formed of multiple Intermediate System (IS-IS) TLV named CAPABILITY, formed of multiple
sub-TLVs, which allows a router to announce its capabilities within sub-TLVs, which allows a router to announce its capabilities within
an IS-IS level or the entire routing domain. an IS-IS level or the entire routing domain. This document obsoletes
RFC 4971.
Requirements Language Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119]. document are to be interpreted as described in RFC 2119 [RFC2119].
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 41 skipping to change at page 1, line 42
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 February 11, 2017. This Internet-Draft will expire on February 16, 2017.
Copyright Notice Copyright Notice
Copyright (c) 2016 IETF Trust and the persons identified as the Copyright (c) 2016 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
skipping to change at page 2, line 21 skipping to change at page 2, line 24
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. IS-IS Router CAPABILITY TLV . . . . . . . . . . . . . . . . . 3 2. IS-IS Router CAPABILITY TLV . . . . . . . . . . . . . . . . . 3
3. Elements of Procedure . . . . . . . . . . . . . . . . . . . . 4 3. Elements of Procedure . . . . . . . . . . . . . . . . . . . . 4
4. Interoperability with Routers Not Supporting the Capability 4. Interoperability with Routers Not Supporting the Capability
TLV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 TLV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
5. Security Considerations . . . . . . . . . . . . . . . . . . . 6 5. Security Considerations . . . . . . . . . . . . . . . . . . . 6
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 6 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 7
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 7 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 7
8.1. Normative References . . . . . . . . . . . . . . . . . . 7 8.1. Normative References . . . . . . . . . . . . . . . . . . 7
8.2. Informational References . . . . . . . . . . . . . . . . 8 8.2. Informational References . . . . . . . . . . . . . . . . 8
Appendix A. Changes to RFC 4971 . . . . . . . . . . . . . . . . 8 Appendix A. Changes to RFC 4971 . . . . . . . . . . . . . . . . 8
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 8 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 9
1. Introduction 1. Introduction
There are several situations where it is useful for the IS-IS There are several situations where it is useful for the IS-IS
[ISO10589] [RFC1195] routers to learn the capabilities of the other [ISO10589] [RFC1195] routers to learn the capabilities of the other
routers of their IS-IS level, area, or routing domain. For the sake routers of their IS-IS level, area, or routing domain. For the sake
of illustration, three examples related to MPLS Traffic Engineering of illustration, three examples related to MPLS Traffic Engineering
(TE) are described here: (TE) are described here:
1. Mesh-group: the setting up of a mesh of TE Label Switched Paths 1. Mesh-group: the setting up of a mesh of TE Label Switched Paths
 End of changes. 6 change blocks. 
9 lines changed or deleted 10 lines changed or added

This html diff was produced by rfcdiff 1.45. The latest version is available from http://tools.ietf.org/tools/rfcdiff/