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

Hi Karsten,

Thanks for your review and comments. Please see replies inline.

From: Karsten Thomann [mailto:karsten_thomann@linfre.de]
Sent: Thursday, June 04, 2015 5:36 AM
To: isis-wg@ietf.org
Cc: Liubing (Leo)
Subject: Re: [Isis-wg] ISIS-autoconf-04 submitted //FW: New Version Notification for draft-liu-isis-auto-conf-04.txt

Hi,

some comments after reading the draft:

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 (http://datatracker.ietf.org/doc/draft-mrw-homenet-rtg-comparison/). And there is also some operator showed explicit requirement for ISIS in home routers.

Furthermore, the scope might not only limit to home/enterprise scenarios. Maybe the operators would find this auto-conf tool is also benefit for them one day:)

Regarding 3.3.2:

What is exactly the duplication resolution, if the NET is used by an ISIS Router not capable of autoconfig?

In my opinion the device which is auto config capable MUST recalculate its NET, if the other router does not advertise a Router-Fingerprint TLV.

[Bing] The autoconfig should be a dedicated ISIS process that it won't be mixed with the non-autoconf routers. This is prevented by the Authentication TLV as described in 3.4.1.

I'm not able to find a similar approach for the OSPF RFC, as it seems to have the same problem.

I don't know if this is typical for english texts, but I'm not familiar with the form of ".etc" only "etc." as this is written many times in that form.

[Bing] My bad, sorry for the language issue.

Section 1.

andSection 3.5)./and Section 3.5). (missing space)

Section 3.4.3

Names TVL (TLV 137/Names TLV (TLV 137

[Bing] I'll correct them accordingly. Thanks for the careful check:)

Best regards,

Bing

Kind regards

Karsten

Am Samstag, 30. Mai 2015, 10:41:29 schrieb Liubing:

> Hi Dear all,

>

> We've submitted a new version of the draft.

>

> Main revisions is summarized as the following:

> 1. Revise the SysID generation to NOT prescriptive to only using MAC

> address. 2. Added a new Section 3.3.3 "SysID and Router-Fingerprint

> Generation Considerations", to specifically discuss the constrained

> entropies for generating the fields in small devices. 3. Revise the NET

> duplication procedures to remove the purge operation 4. Added a new Section

> 3.3.4 " Double-Duplication of both NET and Router-Fingerprint"

>

> We believed this version improves a lot and removes most of the worries

> raised in previous meetings and discussions. Looking forward to your

> feedback. Thanks!

>

> Best regards,

> Bing

>

>

>

> -----Original Message-----

> From: internet-drafts@ietf.org<mailto:internet-drafts@ietf.org> [mailto:internet-drafts@ietf.org]

> Sent: Saturday, May 30, 2015 6:27 PM

> To: Mikael Abrahamsson; Bruno Decraene; Ian Farrer; Liubing (Leo); Bruno

> Decraene; Mikael Abrahamsson; Ian Farrer; Liubing (Leo) Subject: New

> Version Notification for draft-liu-isis-auto-conf-04.txt

>

>

> A new version of I-D, draft-liu-isis-auto-conf-04.txt has been successfully

> submitted by Bing Liu and posted to the IETF repository.

>

> Name: draft-liu-isis-auto-conf

> Revision: 04

> Title: ISIS Auto-Configuration

> Document date: 2015-05-30

> Group: Individual Submission

> Pages: 11

> URL:

> https://www.ietf.org/internet-drafts/draft-liu-isis-auto-conf-04.txt

> Status: https://datatracker.ietf.org/doc/draft-liu-isis-auto-conf/

> Htmlized: https://tools.ietf.org/html/draft-liu-isis-auto-conf-04

> Diff:

> https://www.ietf.org/rfcdiff?url2=draft-liu-isis-auto-conf-04

>

> Abstract:

> This document specifies an IS-IS auto-configuration technology. The

> key mechanisms of this technology are IS-IS NET (Network Entity

> Title) self-generation, duplication detection and duplication

> resolution. This technology fits the environment where plug-and-play

> is expected, e.g., home networks and small or medium size enterprise

> networks.

>

>

>

>

> Please note that it may take a couple of minutes from the time of submission

> until the htmlized version and diff are available at tools.ietf.org.

>

> The IETF Secretariat

>

> _______________________________________________

> Isis-wg mailing list

> Isis-wg@ietf.org<mailto:Isis-wg@ietf.org>

> https://www.ietf.org/mailman/listinfo/isis-wg