ISIS Auto-Configuration
draft-ietf-isis-auto-conf-04

Document Type Active Internet-Draft (isis WG)
Last updated 2017-03-22 (latest revision 2016-11-21)
Replaces draft-liu-isis-auto-conf
Stream IETF
Intended RFC status Proposed Standard
Formats plain text pdf html bibtex
Reviews
Stream WG state Submitted to IESG for Publication
Document shepherd Hannes Gredler
Shepherd write-up Show (last changed 2017-03-15)
IESG IESG state In Last Call (ends 2017-04-10)
Consensus Boilerplate Yes
Telechat date On agenda of 2017-04-13 IESG telechat
Responsible AD Alia Atlas
Send notices to "Hannes Gredler" <hannes@gredler.at>
IANA IANA review state IANA - Review Needed
IANA action state None
isis                                                         B. Liu, Ed.
Internet-Draft                                       Huawei Technologies
Intended status: Standards Track                             B. Decraene
Expires: May 26, 2017                                             Orange
                                                               I. Farrer
                                                     Deutsche Telekom AG
                                                          M. Abrahamsson
                                                               T-Systems
                                                             L. Ginsberg
                                                           Cisco Systems
                                                       November 22, 2016

                        ISIS Auto-Configuration
                      draft-ietf-isis-auto-conf-04

Abstract

   This document specifies IS-IS auto-configuration mechanisms.  The key
   components are IS-IS System ID self-generation, duplication detection
   and duplication resolution.  These mechanisms provide limited IS-IS
   functions, and so are suitable for networks where plug-and-play
   configuration is expected.

Requirements Language

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
   "OPTIONAL" in this document are to be interpreted as described in
   [RFC2119] when they appear in ALL CAPS.  When these words are not in
   ALL CAPS (such as "should" or "Should"), they have their usual
   English meanings, and are not to be interpreted as [RFC2119] key
   words.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

Liu, et al.               Expires May 26, 2017                  [Page 1]
Internet-Draft          draft-ietf-isis-auto-conf          November 2016

   This Internet-Draft will expire on May 26, 2017.

Copyright Notice

   Copyright (c) 2016 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Protocol Specification  . . . . . . . . . . . . . . . . . . .   3
     3.1.  IS-IS Default Configuration . . . . . . . . . . . . . . .   3
     3.2.  IS-IS NET Generation  . . . . . . . . . . . . . . . . . .   4
     3.3.  Router-Fingerprint TLV  . . . . . . . . . . . . . . . . .   5
     3.4.  Protocol Operation  . . . . . . . . . . . . . . . . . . .   6
       3.4.1.  Start-Up mode . . . . . . . . . . . . . . . . . . . .   6
       3.4.2.  Adjacency Formation . . . . . . . . . . . . . . . . .   6
       3.4.3.  IS-IS System ID Duplication Detection and Resolution    7
       3.4.4.  Duplicate System ID Resolution Procedures . . . . . .   7
       3.4.5.  System ID and Router-Fingerprint Generation
               Considerations  . . . . . . . . . . . . . . . . . . .   8
       3.4.6.  Double-Duplication of both System ID and Router-
               Fingerprint . . . . . . . . . . . . . . . . . . . . .   9
     3.5.  Additional IS-IS TLVs Usage Guidelines  . . . . . . . . .  10
       3.5.1.  Authentication TLV  . . . . . . . . . . . . . . . . .  10
       3.5.2.  Metric Used in Reachability TLVs  . . . . . . . . . .  11
       3.5.3.  Dynamic Host Name TLV . . . . . . . . . . . . . . . .  11
   4.  Security Considerations . . . . . . . . . . . . . . . . . . .  11
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  11
Show full document text