Re: [Isis-wg] WG Adoption Call for draft-xu-isis-encapsulation-cap

"Les Ginsberg (ginsberg)" <ginsberg@cisco.com> Wed, 13 January 2016 01:25 UTC

Return-Path: <ginsberg@cisco.com>
X-Original-To: isis-wg@ietfa.amsl.com
Delivered-To: isis-wg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 258CF1A6F38 for <isis-wg@ietfa.amsl.com>; Tue, 12 Jan 2016 17:25:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.501
X-Spam-Level:
X-Spam-Status: No, score=-14.501 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, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id q8IvQ0uonJxH for <isis-wg@ietfa.amsl.com>; Tue, 12 Jan 2016 17:25:04 -0800 (PST)
Received: from alln-iport-5.cisco.com (alln-iport-5.cisco.com [173.37.142.92]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A142F1AC3F2 for <isis-wg@ietf.org>; Tue, 12 Jan 2016 17:25:04 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=10075; q=dns/txt; s=iport; t=1452648304; x=1453857904; h=from:to:subject:date:message-id:references:in-reply-to: mime-version; bh=y25A5FJCW4OsKLGFZ2WKLLg1Q9lhRr2YEV/pGZL2ruo=; b=EXf5nnLyz8kj0F09gZRokArgbxyWbGcgvR9aGTZyrxyJxdJAnxwf9YkJ PIsQnkIj0NjxVAr/Pz1r5O+QCEGqdaktbckWV4xbIRHbtnz8kw5exvpis 764WB+9lcpdOEPrCNPXExX6xIk6pzd6Aid8AZWXlnVx0ih3EOXmHbT9Ug M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0BJAgA5ppVW/5xdJa1egm5MUm0GiFOzIwENgWQihW0CgSo4FAEBAQEBAQGBCoQ0AQEBBB0QXAIBCA4DBAEBKAcyFAkIAgQBEgiIJg6/YwEBAQEBAQEBAQEBAQEBAQEBAQEBARQEhlaEf4QmCwYBTAmEMAWTEIQDAYVCiA+BZYRDiFuOUgEgAQFChApyhHoIFyOBCAEBAQ
X-IronPort-AV: E=Sophos;i="5.22,286,1449532800"; d="scan'208,217";a="224944205"
Received: from rcdn-core-5.cisco.com ([173.37.93.156]) by alln-iport-5.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 13 Jan 2016 01:25:03 +0000
Received: from XCH-RCD-004.cisco.com (xch-rcd-004.cisco.com [173.37.102.14]) by rcdn-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id u0D1P3sj028976 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 13 Jan 2016 01:25:03 GMT
Received: from xch-aln-001.cisco.com (173.36.7.11) by XCH-RCD-004.cisco.com (173.37.102.14) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Tue, 12 Jan 2016 19:25:02 -0600
Received: from xch-aln-001.cisco.com ([173.36.7.11]) by XCH-ALN-001.cisco.com ([173.36.7.11]) with mapi id 15.00.1104.009; Tue, 12 Jan 2016 19:25:02 -0600
From: "Les Ginsberg (ginsberg)" <ginsberg@cisco.com>
To: Christian Hopps <chopps@chopps.org>, "isis-wg@ietf.org list" <isis-wg@ietf.org>
Thread-Topic: [Isis-wg] WG Adoption Call for draft-xu-isis-encapsulation-cap
Thread-Index: AQHRKSDuT28sdMgL3ESJe3s68xYgBJ62KrQAgELBV1A=
Date: Wed, 13 Jan 2016 01:25:02 +0000
Message-ID: <2d9f516b68fd4443853f512a533bd9d6@XCH-ALN-001.cisco.com>
References: <4C33F1DA-351A-4E4C-AB2D-EB9C530EBA36@chopps.org> <05BB1848-0F89-4A06-B1C6-7E955C41C9E9@chopps.org>
In-Reply-To: <05BB1848-0F89-4A06-B1C6-7E955C41C9E9@chopps.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.154.208.27]
Content-Type: multipart/alternative; boundary="_000_2d9f516b68fd4443853f512a533bd9d6XCHALN001ciscocom_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/isis-wg/rsgCGZ9B-CdFPYG5l5JAUrCX6a4>
Subject: Re: [Isis-wg] WG Adoption Call for draft-xu-isis-encapsulation-cap
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/isis-wg>, <mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/isis-wg/>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/isis-wg>, <mailto:isis-wg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Jan 2016 01:25:08 -0000

Apologies for the very late response on this...

I have a couple of concerns regarding taking on this work.

The draft is straightforward enough in terms of the protocol extensions defined, but I am not at all clear on the usefulness of the information being advertised. The introduction to the draft discusses a variety of tunnel types which might be used in a network but does not offer an y reason why advertising the tunnel types supported is of benefit. Given this information is only advertised within a single administrative domain it does not seem to provide any information that is not already known to the network operator. It also logically leads to requiring a configuration for what tunnel types to advertise. If this information is meant to drive automatic configuration of tunnels I presume that the network operator would want to limit what is advertised - not simply accept what the implementation is capable of supporting. So it seems we have simply traded one configuration for another.  I would like to see more detail on this before deciding whether it is worth doing.

It is clear that the information is not at all useful to IS-IS itself - which brings me to my second concern. This is advertising information that has nothing to with IS-IS. Router Capabilities is not meant to be used as a vehicle to advertise information not of direct use to the protocol. In fact, the existence of a couple of exceptions to this guideline is what prompted the creation of GENAPP (RFC 6823) as the appropriate place to advertise such information.

I would like to see further discussion of the above before deciding that WG adoption (which almost always indicates an intent to progress to RFC) is appropriate.

    Les


From: Isis-wg [mailto:isis-wg-bounces@ietf.org] On Behalf Of Christian Hopps
Sent: Monday, November 30, 2015 11:45 PM
To: isis-wg@ietf.org list
Subject: Re: [Isis-wg] WG Adoption Call for draft-xu-isis-encapsulation-cap

[It seems due to some sneaky cut and paste error, the URL was wrong in the original email, I've corrected in this message]

Hi Folks,

The authors have requested the IS-IS WG adopt:

https://datatracker.ietf.org/doc/draft-xu-isis-encapsulation-cap/

as a working group document.

Please indicate support or no-support for taking on this work.

Thanks,
Chris.