Re: [Isis-wg] ISIS-autoconf-04 submitted //FW: New Version Notification for draft-liu-isis-auto-conf-04.txt

"Acee Lindem (acee)" <> Fri, 05 June 2015 17:06 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 343751A904A for <>; Fri, 5 Jun 2015 10:06:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -14.51
X-Spam-Status: No, score=-14.51 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id Hve2IwfSoCLB for <>; Fri, 5 Jun 2015 10:06:27 -0700 (PDT)
Received: from ( []) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id EF7E61A8F3D for <>; Fri, 5 Jun 2015 10:06:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple;;; l=17359; q=dns/txt; s=iport; t=1433523987; x=1434733587; h=from:to:subject:date:message-id:references:in-reply-to: mime-version; bh=1e/MZjCiazbZIEUJfrTrnRgAeRoa/VrhO08xDWkPACg=; b=OCCVkjyHUi5srcps3cSX/E125RDHs24wuuOwA3KdpS4hZ8JhNJa2Ha/Q NOKHJP3p+foSO0gayLkJBYmUmaenS6rnolD4ZzbSWWzS5L4cCr93yyJfE yBBkglxTBSgFupxbSEy+mRJp1HX52xrO4hpUZ2PHuuZhi3yxGeRZnpbPI 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-AV: E=Sophos;i="5.13,560,1427760000"; d="scan'208,217";a="156679186"
Received: from ([]) by with ESMTP; 05 Jun 2015 17:06:26 +0000
Received: from ( []) by (8.14.5/8.14.5) with ESMTP id t55H6QIn002430 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 5 Jun 2015 17:06:26 GMT
Received: from ([]) by ([]) with mapi id 14.03.0195.001; Fri, 5 Jun 2015 12:06:25 -0500
From: "Acee Lindem (acee)" <>
To: Uma Chunduri <>, "Liubing (Leo)" <>, Karsten Thomann <>, "" <>
Thread-Topic: [Isis-wg] ISIS-autoconf-04 submitted //FW: New Version Notification for draft-liu-isis-auto-conf-04.txt
Thread-Index: AQHQmsUvhOb/9lHMUk2S32rA0gaCAZ2bqN8AgAIrooCAAKn8gP//wKKA
Date: Fri, 5 Jun 2015 17:06:24 +0000
Message-ID: <>
References: <> <2366384.fmjLvuEOoo@linne> <> <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
x-originating-ip: []
Content-Type: multipart/alternative; boundary="_000_D1974D8D20D5Eaceeciscocom_"
MIME-Version: 1.0
Archived-At: <>
Subject: Re: [Isis-wg] ISIS-autoconf-04 submitted //FW: New Version Notification for draft-liu-isis-auto-conf-04.txt
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF IS-IS working group <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Fri, 05 Jun 2015 17:06:29 -0000

From: Uma Chunduri <<>>
Date: Friday, June 5, 2015 at 12:53 PM
To: "Liubing (Leo)" <<>>, Karsten Thomann <<>>, "<>" <<>>
Subject: Re: [Isis-wg] ISIS-autoconf-04 submitted //FW: New Version Notification for draft-liu-isis-auto-conf-04.txt

I'm not really convinced that this will really be implemented in a home network or small enterprise networks, as ISIS isn't a protocol widely supported on that platforms.

I was thinking more about shortest path bridging switch autodiscovery, but this is only my own opinion.

[Bing] I agree ISIS is not widely supported on small devices nowadays. But I think it might has the potential in the future.

Actually, In Homenet the ISIS is already in the short list for their routing protocol choice (

Speaking as the Routing Area advisor to homenet:

Agreed. I would support going forward with this work. Even if the homenet WG doesn’t select IS-IS outright, the fact that it made it to the short list indicates that there is a requirement.


[Uma]:  Sure,  though still it’s complicated situation in Homenet, IS-IS is not out.  Some of you may aware, there was a design team formed including routing experts and

Homenet experts to come out with recommendations for the suitable RP for their needs.

And there is also some operator showed explicit requirement for ISIS in home routers.

[Uma]: We too have some discussions on this internally and I see the potential for future requests..

               IMO, this work should be progressed by closing on the corner cases further and I support this.



Uma C.