RE: [mpls] Review of draft-ietf-mpls-residence-time-12

Mach Chen <mach.chen@huawei.com> Sun, 22 January 2017 01:46 UTC

Return-Path: <mach.chen@huawei.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F092012956C; Sat, 21 Jan 2017 17:46:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.42
X-Spam-Level:
X-Spam-Status: No, score=-7.42 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-3.199, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 ap6Q4gqh59Xv; Sat, 21 Jan 2017 17:46:22 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 011FC129564; Sat, 21 Jan 2017 17:46:20 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml703-cah.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id DEY75369; Sun, 22 Jan 2017 01:46:18 +0000 (GMT)
Received: from SZXEMA417-HUB.china.huawei.com (10.82.72.34) by lhreml703-cah.china.huawei.com (10.201.5.104) with Microsoft SMTP Server (TLS) id 14.3.301.0; Sun, 22 Jan 2017 01:46:18 +0000
Received: from SZXEMA510-MBX.china.huawei.com ([169.254.3.116]) by SZXEMA417-HUB.china.huawei.com ([10.82.72.34]) with mapi id 14.03.0235.001; Sun, 22 Jan 2017 09:46:13 +0800
From: Mach Chen <mach.chen@huawei.com>
To: "adrian@olddog.co.uk" <adrian@olddog.co.uk>, "'Acee Lindem (acee)'" <acee@cisco.com>, "'Hannes Gredler'" <hannes@gredler.at>, "'Les Ginsberg (ginsberg)'" <ginsberg@cisco.com>, "'John E Drake'" <jdrake@juniper.net>, "'Alexander Vainshtein'" <Alexander.Vainshtein@ecitele.com>, "'Greg Mirsky'" <gregimirsky@gmail.com>
Subject: RE: [mpls] Review of draft-ietf-mpls-residence-time-12
Thread-Topic: [mpls] Review of draft-ietf-mpls-residence-time-12
Thread-Index: AQHScbmPhy9sX53JF0ue0R0cnNvvWqE+F5eAgAA5zICAARrRgIAAA9UAgAAAuACAAAQ7gIAABj6AgAABeICAAAEZAIAAAeQAgAAIqoCAALn1gIAAihuAgAA5h4CAArjKEA==
Date: Sun, 22 Jan 2017 01:46:13 +0000
Message-ID: <F73A3CB31E8BE34FA1BBE3C8F0CB2AE28FDBA4A7@SZXEMA510-MBX.china.huawei.com>
References: <148414970343.8167.4538946698521330202.idtracker@ietfa.amsl.com> <CA+RyBmU9W5QP4EjbPezoCpdLHv1RJCrzJvxQmeTnAvjO_6vbJA@mail.gmail.com> <CA+RyBmVrvyiwDp2kV3VLiQtqOaL=MaVjZugGbvgWnp6y3dwP3Q@mail.gmail.com> <95d41b52-5c85-869f-2139-6713816e9637@nostrum.com> <CA+RyBmWcvU70BZYRj8ZHUZrmkcwq1eHS38jFpyZOq3A_5eXZ9g@mail.gmail.com> <D4A55AE0.9483E%acee@cisco.com> <CA+RyBmWrDhZUmVN0t8aLsL6F3ZfnvBu8FW_2VjDmwj-ercLd5w@mail.gmail.com> <f315026a140148898250f8fa3bdb0123@XCH-ALN-001.cisco.com> <CA+RyBmWMBAXd+zntuAeOU9x7xs9BQSk7J-z9+yyUDvKPd3v2MA@mail.gmail.com> <HE1PR0301MB22660A73C0D5A96BA8F3F0D39D7E0@HE1PR0301MB2266.eurprd03.prod.outlook.com> <D4A65103.94DF0%acee@cisco.com> <DM5PR05MB3001952D0DDD2AA672697094C77E0@DM5PR05MB3001.namprd05.prod.outlook.com> <D4A6573B.94E53%acee@cisco.com> <DM5PR05MB3001ED6AF8296F5DBE5E38EFC77E0@DM5PR05MB3001.namprd05.prod.outlook.com> <3f43cfdfe76e437bb2df6159e5644ae5@XCH-ALN-001.cisco.com> <01e66ab2-aea1-4d60-63c6-9304d644381f@gredler.at> <D4A77012! .95F4B%acee@cisco.com> <081b01d27337$c32b0e20$49812a60$@olddog.co.uk>
In-Reply-To: <081b01d27337$c32b0e20$49812a60$@olddog.co.uk>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.111.194.201]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A020202.58840EEB.011A, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0, ip=169.254.3.116, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: d9b0f707505a610b0b650e5a99939e32
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/HBR2g0372DhGN9My_E4H5YPTR2Y>
X-Mailman-Approved-At: Mon, 23 Jan 2017 10:49:06 -0800
Cc: "mpls@ietf.org" <mpls@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>, "isis-chairs@ietf.org" <isis-chairs@ietf.org>, "draft-ietf-mpls-residence-time.all@ietf.org" <draft-ietf-mpls-residence-time.all@ietf.org>, "'Abhay Roy \(akr\)'" <akr@cisco.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 22 Jan 2017 01:46:24 -0000

Sounds like a good idea, I agree with this.

Best regards,
Mach

-----Original Message-----
From: mpls [mailto:mpls-bounces@ietf.org] On Behalf Of Adrian Farrel
Sent: Saturday, January 21, 2017 12:11 AM
To: 'Acee Lindem (acee)'; 'Hannes Gredler'; 'Les Ginsberg (ginsberg)'; 'John E Drake'; 'Alexander Vainshtein'; 'Greg Mirsky'
Cc: mpls@ietf.org; ietf@ietf.org; isis-chairs@ietf.org; gen-art@ietf.org; draft-ietf-mpls-residence-time.all@ietf.org; 'Abhay Roy (akr)'; 'Robert Sparks'
Subject: Re: [mpls] Review of draft-ietf-mpls-residence-time-12

I agree with Hannes on this.

However, if the document was to highlight strongly that the data is "a non-routing related capability" (if that's what we believe!) and stress that the information "that does not change frequently" (perhaps with some explanation of
"frequently") I believe that might help everyone.

Adrian

> >we have taken turns long-time ago to advertise non-routing related 
> >information which is only relevant to controllers (l2bundles comes 
> >into mind ;-)).
> >
> >while it would have been nice to get at least notice that an IS-IS 
> >extension is being worked on (i mean prior to IANA asking for expert 
> >review :-/ ) i see no reason why we should hold this back. - we can 
> >argue perhaps whether it should be part of GENAPP or ROUTERCAP TLVs, 
> >but i cannot see the sky falling to advertise a non-routing related 
> >capability, that does not change frequently.
> 
> I agree but was just trying to get a better idea of precisely how the 
> information will be used and whether interface is the right granularity.

_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls