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

Philip Christian <philip.christian@pscan.eu> Mon, 29 February 2016 11:30 UTC

Return-Path: <philip.christian@pscan.eu>
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 927E31B3090 for <isis-wg@ietfa.amsl.com>; Mon, 29 Feb 2016 03:30:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_51=0.6, RCVD_IN_DNSWL_LOW=-0.7] 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 dTZxN6Vrx_i3 for <isis-wg@ietfa.amsl.com>; Mon, 29 Feb 2016 03:30:22 -0800 (PST)
Received: from know-smtprelay-omc-5.server.virginmedia.net (know-smtprelay-omc-5.server.virginmedia.net [80.0.253.69]) by ietfa.amsl.com (Postfix) with ESMTP id A0A031B308E for <isis-wg@ietf.org>; Mon, 29 Feb 2016 03:30:21 -0800 (PST)
Received: from christiantena.net ([82.13.85.13]) by know-smtprelay-5-imp with bizsmtp id QBWK1s00v0HFYiy01BWL6J; Mon, 29 Feb 2016 11:30:20 +0000
X-Originating-IP: [82.13.85.13]
X-Spam: 0
X-Authority: v=2.1 cv=GKL1ab5K c=1 sm=1 tr=0 a=j0AvSjNDViVSPqYGGWZBsw==:117 a=j0AvSjNDViVSPqYGGWZBsw==:17 a=L9H7d07YOLsA:10 a=9cW_t1CCXrUA:10 a=s5jvgZ67dGcA:10 a=IkcTkHD0fZMA:10 a=MKtGQD3n3ToA:10 a=1oJP67jkp3AA:10 a=ZZnuYtJkoWoA:10 a=jFJIQSaiL_oA:10 a=WFZaTFp8ZY4A:10 a=48vgC7mUAAAA:8 a=hZG83p_yAAAA:8 a=ek1ZzK3JAAAA:8 a=YCrN2x3QGqf-w3F4_-kA:9 a=QEXdDO2ut3YA:10
Received: from [10.0.1.121] by christiantena.net with esmtpsa (TLSv1:DHE-RSA-AES128-SHA:128) (Exim 4.82 (FreeBSD)) (envelope-from <philip.christian@pscan.eu>) id 1aaM1r-000Ad6-5P for isis-wg@ietf.org; Mon, 29 Feb 2016 11:30:19 +0000
To: isis-wg@ietf.org
References: <4C33F1DA-351A-4E4C-AB2D-EB9C530EBA36@chopps.org> <0F26584357FD124DB93F1535E4B0A6505FCA84AB@szxema508-mbx.china.huawei.com> <40746B2300A8FC4AB04EE722A593182B9FC929D7@ONWVEXCHMB04.ciena.com>
From: Philip Christian <philip.christian@pscan.eu>
Message-ID: <56D42BCA.3060707@pscan.eu>
Date: Mon, 29 Feb 2016 11:30:18 +0000
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Icedove/38.6.0
MIME-Version: 1.0
In-Reply-To: <40746B2300A8FC4AB04EE722A593182B9FC929D7@ONWVEXCHMB04.ciena.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/isis-wg/pGm6AFFut8XT8FymhSRJKbL0idM>
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: Mon, 29 Feb 2016 11:47:37 -0000

Please can people explain how

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

might fit in with, or cause problems with this

https://tools.ietf.org/html/draft-ietf-isis-auto-encap-03

which was adopted by the ITU-T and appears to be still very much part of 
IT-T G.7712.
The PDF of that document is available here

https://www.itu.int/rec/T-REC-G.7712-201009-I/en

and you probably want to go to page 46.

or it is defining something entirely different?

The ITU-T version defines an "Encapsulation capability TLV" with code 16 
decimal, whereas draft-xu-isis-encapsulation-cap says "routers 
advertises their supported encapsulation type(s) by advertising a new 
sub-TLV of the IS-IS Router CAPABILITY TLV"

is it dangerous to have two mechanisms to advertise the same thing?

also it seems a shame when TLV 16 is already defined as using subTLVs 
and so could easily be used for the new purposes that 
xu-isis-encapsulation-cap suggests.

Apologies if I have misunderstood something; I have been away from this 
for a long time.

regards, Philip Christian




On 01/12/15 03:53, Shah, Himanshu wrote:
> /You are right the hyperlink is WRONG../
>
> //
>
> /I support
> https://datatracker.ietf.org/doc/draft-xu-isis-encapsulation-cap/   (the
> right link)/
>
> //
>
> /Thanks,/
>
> /Himanshu/
>
> //
>
> *From:*Isis-wg [mailto:isis-wg-bounces@ietf.org] *On Behalf Of *Wunan (Eric)
> *Sent:* Monday, November 30, 2015 10:21 PM
> *To:* Christian Hopps; isis-wg@ietf.org list
> *Subject:* Re: [Isis-wg] WG Adoption Call for
> draft-xu-isis-encapsulation-cap
>
> Hi Chris,
>
> Is it only for me or other people also same that I was redirected to
> auto-cfg draft using link below? Or this is the implication for your
> crush on that draft?J
>
> Anyway, I think the scenario described in [5512] is still valid in IS-IS
> networks and It would be useful, so I support it.
>
> Regards
>
> Eric
>
> *发件人**:*Christian Hopps [mailto:chopps@chopps.org]
> *发送时间:* 2015年11月27日 22:35
> *收件人:* isis-wg@ietf.org <mailto:isis-wg@ietf.org> list
> *主题:* [Isis-wg] WG Adoption Call for draft-xu-isis-encapsulation-cap
>
> Hi Folks,
>
> The authors have requested the IS-IS WG adopt:
> https://datatracker.ietf.org/doc/draft-xu-isis-encapsulation-cap/
> <https://datatracker.ietf.org/doc/draft-liu-isis-auto-conf/>
>
> as a working group document.
>
> Please indicate support or no-support for taking on this work.
>
> Thanks,
> Chris.
>
>
>
> _______________________________________________
> Isis-wg mailing list
> Isis-wg@ietf.org
> https://www.ietf.org/mailman/listinfo/isis-wg
>