Re: [Isis-wg] WG Last Call for draft-ietf-isis-auto-conf-04

"Acee Lindem (acee)" <> Sun, 22 January 2017 23:56 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id D6253129498; Sun, 22 Jan 2017 15:56:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -17.721
X-Spam-Status: No, score=-17.721 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-3.199, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id N5ZwKvQ2J2gT; Sun, 22 Jan 2017 15:56:35 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id E3F29129493; Sun, 22 Jan 2017 15:56:34 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple;;; l=6294; q=dns/txt; s=iport; t=1485129395; x=1486338995; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=6rdNjIlSDI6xqLzL4Uoaxy1uLAhHW/eW1DAReE8WK74=; b=E2UM22upXsWGXJF5PENudzYVppS9h4RWFBOrrFVvroLuHImfL2MWMLUU evkAPXavhf3zmsmivkQ0JqEvT3uuSM8R5jjk8b3Gc0ZPqxW5eMUOapW9U TmsHTIhsRcWtLCWKK8gs2xvXFuVy3HkH4LIv4sdJhIz6MKhLdob3IpDV1 o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-AV: E=Sophos;i="5.33,270,1477958400"; d="scan'208";a="198483043"
Received: from ([]) by with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 22 Jan 2017 23:56:19 +0000
Received: from ( []) by (8.14.5/8.14.5) with ESMTP id v0MNuIxu011995 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Sun, 22 Jan 2017 23:56:19 GMT
Received: from ( by ( with Microsoft SMTP Server (TLS) id 15.0.1210.3; Sun, 22 Jan 2017 18:56:18 -0500
Received: from ([]) by ([]) with mapi id 15.00.1210.000; Sun, 22 Jan 2017 18:56:18 -0500
From: "Acee Lindem (acee)" <>
To: "Les Ginsberg (ginsberg)" <>, Christian Hopps <>, "" <>
Thread-Topic: [Isis-wg] WG Last Call for draft-ietf-isis-auto-conf-04
Thread-Index: AQHScLlfiAQ81s+pYEybS3QN6rpQoqFEiGEAgACb/QCAABBiAA==
Date: Sun, 22 Jan 2017 23:56:17 +0000
Message-ID: <>
References: <> <> <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: []
Content-Type: text/plain; charset="euc-kr"
Content-ID: <>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <>
Cc: "" <>, "" <>, "" <>
Subject: Re: [Isis-wg] WG Last Call for draft-ietf-isis-auto-conf-04
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF IS-IS working group <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Sun, 22 Jan 2017 23:56:37 -0000

Hi Les, 

On 1/22/17, 12:57 PM, "Les Ginsberg (ginsberg)" <> wrote:

>Acee -
>Thanx for reviewing the document.
>Responses inline.
>> -----Original Message-----
>> From: Isis-wg [] On Behalf Of Acee Lindem
>> (acee)
>> Sent: Sunday, January 22, 2017 5:39 AM
>> To: Christian Hopps;
>> Cc:;;
>> Subject: Re: [Isis-wg] WG Last Call for draft-ietf-isis-auto-conf-04
>> Hi IS-IS WG,
>> I have reviewed the document and support publication. I have the
>> minor comments:
>>     1. It should be made clear that the A-Bit indicates that an IS-IS
>> supports auto-configuration and, is not, necessarily auto-configured
>> After reading the whole draft, I know that this is the definition of
>>the bit but
>> the initial text says the router is ³operating in auto-configuration
>[Les:] It is clearly stated that the A flag does indeed mean
>" the router is operating in auto-configuration mode."
>I do not see any text which suggests otherwise.

But there is no prior definition of “auto-configuration mode”. I think
most readers would believe that this indicates that only routers
performing auto-configuration will form adjacencies. Yet the documents

   This document also defines mechanisms to prevent the unintentional
   interoperation of auto-configured routers with non-autoconfigured
   routers.  See Section 3.3.

Where is the interoperation? This definitely needs to be clarified - I
don’t see how the authors can argue on this point!

>>     2. In the duplicate detection in section 3.4.3, could you note that
>>an IS-IS
>> router should be able to detect discern the case where two interfaces
>>on the
>> IS-IS router performing auto-configuration are connected to the same
>> network.
>[Les:] Multiple connections of the same system to the same network can
>occur in the absence of auto-configuration and detection of this case is
>not altered by auto-configuration. This is detected by receiving a hello
>with the same source MAC address as a local interface. There are then the
>following cases:
>1)Two interfaces on the local router are connected to the same media.
>This is further validated by having the same systemID. The means for
>detecting this as well as resolving this are not altered by
>2)Two neighbors connected to the same network have the same source MAC
>address. This is distinguished by having different system IDs in the
>hellos. The means for detecting this as well as resolving this are not
>altered by auto-configuration.
>3)Two neighbors connected to the same network have the same source MAC
>address and the same systemID. This is distinguished by having different
>router fingerprint TLVs in the hellos - something only an auto-config
>router could do. But the additional detection capability does not provide
>any additional means to correct this issue.
>The authors discussed this point during the writing of the draft and
>decided specifically NOT to comment on this issue as it by nature is no
>different than what can occur without auto-config and there is no good
>way to automatically recover from this case i.e. clearly we cannot alter
>the physical connections by programmatic means - nor do we assume/require
>a programmatic capability of assigning MAC addresses.
>So, I am not sure what we could say other than to note that this can
>occur - but non-auto-config implementations already have to detect this -
>so does it make sense to comment on this in the auto-config draft?

Given that consequences of this mis-wiring are more severe when IS-IS
auto-configuration is being used, I think this deserves at least the
discussion above included in the draft.


>   Les
>> Thanks,
>> Acee
>> On 1/17/17, 7:00 AM, "Isis-wg on behalf of Christian Hopps"
>> < on behalf of> wrote:
>> >
>> >Hi Folks,
>> >
>> >We are starting a WG Last Call for
>> >
>> >  "ISIS Auto-Configuration"
>> >  -
>> >
>> >The WGLC will expire in 2 weeks on Jan 31, 2017.
>> >
>> >Thanks,
>> >Chris & Hannes.
>> _______________________________________________
>> Isis-wg mailing list