draft-ietf-isis-auto-conf-02.txt   draft-ietf-isis-auto-conf-03.txt 
isis B. Liu, Ed. isis B. Liu, Ed.
Internet-Draft Huawei Technologies Internet-Draft Huawei Technologies
Intended status: Standards Track B. Decraene Intended status: Standards Track B. Decraene
Expires: January 21, 2017 Orange Expires: May 4, 2017 Orange
I. Farrer I. Farrer
Deutsche Telekom AG Deutsche Telekom AG
M. Abrahamsson M. Abrahamsson
T-Systems T-Systems
L. Ginsberg L. Ginsberg
Cisco Systems Cisco Systems
July 20, 2016 October 31, 2016
ISIS Auto-Configuration ISIS Auto-Configuration
draft-ietf-isis-auto-conf-02 draft-ietf-isis-auto-conf-03
Abstract Abstract
This document specifies IS-IS auto-configuration mechanisms. The key This document specifies IS-IS auto-configuration mechanisms. The key
components are IS-IS System ID self-generation, duplication detection components are IS-IS System ID self-generation, duplication detection
and duplication resolution. These mechanisms provide limited IS-IS and duplication resolution. These mechanisms provide limited IS-IS
functions, thus they are fit for the networks where plug-and-play functions, and so are suitable for networks where plug-and-play
configuration is expected. configuration is expected.
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 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 January 21, 2017. This Internet-Draft will expire on May 4, 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 3, line 18 skipping to change at page 3, line 18
4. ISIS TLV utilization (Authentication TLV, Wide Metric TLV, and 4. ISIS TLV utilization (Authentication TLV, Wide Metric TLV, and
Dynamic Host Name TLV). Dynamic Host Name TLV).
This document also defines mechanisms to prevent the unintentional This document also defines mechanisms to prevent the unintentional
interoperation of auto-configured routers with non-autoconfigured interoperation of auto-configured routers with non-autoconfigured
routers. See Section 3.3.1. routers. See Section 3.3.1.
2. Scope 2. Scope
The auto-configuring mechanisms support both IPv4 and IPv6 The auto-configuration mechanism supports both IPv4 and IPv6
deployments. deployments.
These auto-configuration mechanisms aim to cover simple deployment These auto-configuration mechanisms aim to cover simple deployment
cases. The following important features are not supported: cases. The following important features are not supported:
o Multiple IS-IS instances. o Multiple IS-IS instances.
o Multi-area and level-2 routing. o Multi-area and level-2 routing.
o Interworking with other routing protocols. o Interworking with other routing protocols.
IS-IS auto-configuration is primarily intended for use in small (i.e.
10s of devices) and unmanaged deployments. Its allows IS-IS to be
used as the IGP without the need for any configuration by the user.
It is not recommended for larger deployments.
3. Protocol Specification 3. Protocol Specification
3.1. IS-IS Default Configuration 3.1. IS-IS Default Configuration
o IS-IS interfaces MUST be auto-configured to an interface type o IS-IS interfaces MUST be auto-configured to an interface type
corresponding to their layer-2 capability. For example, Ethernet corresponding to their layer-2 capability. For example, Ethernet
interfaces will be auto-configured as broadcast networks and interfaces will be auto-configured as broadcast networks and
Point-to-Point Protocol (PPP) interfaces will be auto-configured Point-to-Point Protocol (PPP) interfaces will be auto-configured
as Point-to-Point interfaces. as Point-to-Point interfaces.
 End of changes. 7 change blocks. 
6 lines changed or deleted 11 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/