IETF Logo Mail Archive

Re: [Idr] WG adoption call for draft-xu-idr-performance-routing-01

Xuxiaohu <xuxiaohu@huawei.com> Tue, 06 January 2015 01:15 UTC

Return-Path: <xuxiaohu@huawei.com>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D5FA81A90B1 for <idr@ietfa.amsl.com>; Mon, 5 Jan 2015 17:15:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level:
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 OpWdCepRmdBe for <idr@ietfa.amsl.com>; Mon, 5 Jan 2015 17:15:06 -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 D5DCB1A90BF for <idr@ietf.org>; Mon, 5 Jan 2015 17:15:05 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml405-hub.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BNP82387; Tue, 06 Jan 2015 01:15:04 +0000 (GMT)
Received: from NKGEML401-HUB.china.huawei.com (10.98.56.32) by lhreml405-hub.china.huawei.com (10.201.5.242) with Microsoft SMTP Server (TLS) id 14.3.158.1; Tue, 6 Jan 2015 01:15:03 +0000
Received: from NKGEML512-MBS.china.huawei.com ([169.254.8.199]) by nkgeml401-hub.china.huawei.com ([10.98.56.32]) with mapi id 14.03.0158.001; Tue, 6 Jan 2015 09:14:57 +0800
From: Xuxiaohu <xuxiaohu@huawei.com>
To: "stephane.litkowski@orange.com" <stephane.litkowski@orange.com>
Thread-Topic: [Idr] WG adoption call for draft-xu-idr-performance-routing-01
Thread-Index: AdAgbI6qDeeSh60eTxGCTJRRuSQ2ov//hyQAgAANiQCAAA3SAP//Kb1QgAI8GACAD5+ngP/+5VNQ
Date: Tue, 06 Jan 2015 01:14:56 +0000
Message-ID: <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE082F0B1F@NKGEML512-MBS.china.huawei.com>
References: <DB4PR06MB576D18C5E4A6B1AE49BA8C39E550@DB4PR06MB576.eurprd06.prod.outlook.com> <68EFACB32CF4464298EA2779B058889D24C778C7@PDDCWMBXEX503.ctl.intranet> <CA+b+ERmwQs+9fxJ+Gj=vCkDffZ52agcx8kEQVTMgOwJPPSaQ9A@mail.gmail.com> <DB4PR06MB57639A06596D2CB0BFA83CB9E550@DB4PR06MB576.eurprd06.prod.outlook.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE082EFA35@NKGEML512-MBS.china.huawei.com> <DB4PR06MB5765D44ADA00BE2C55FEDC79E520@DB4PR06MB576.eurprd06.prod.outlook.com> <3390_1420474866_54AAB9F2_3390_41_1_9E32478DFA9976438E7A22F69B08FF920C74AB55@OPEXCLILM34.corporate.adroot.infra.ftgroup>
In-Reply-To: <3390_1420474866_54AAB9F2_3390_41_1_9E32478DFA9976438E7A22F69B08FF920C74AB55@OPEXCLILM34.corporate.adroot.infra.ftgroup>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.111.98.134]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: http://mailarchive.ietf.org/arch/msg/idr/LZ7c1kEYN5s0Mxar8CTv2BVFxqI
Cc: "idr@ietf.org" <idr@ietf.org>, "shares@ndzh.com" <shares@ndzh.com>
Subject: Re: [Idr] WG adoption call for draft-xu-idr-performance-routing-01
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/idr/>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Jan 2015 01:15:08 -0000

Hi Stephane,

It's a very good suggestion and I would incorporate it in the future version.

Best regards,
Xiaohu

> -----Original Message-----
> From: stephane.litkowski@orange.com [mailto:stephane.litkowski@orange.com]
> Sent: Tuesday, January 06, 2015 12:21 AM
> To: Xuxiaohu
> Cc: idr@ietf.org; shares@ndzh.com
> Subject: RE: [Idr] WG adoption call for draft-xu-idr-performance-routing-01
> 
> Hi,
> 
> I'm wondering what happens if a specific BGP Speaker in the path vector is
> supporting this extension but for some (many) reason, cannot provide a latency
> information.
> In this case, there must be an information encoded saying that the
> NETWORK_LATENCY cannot be used for this specific path because part of the
> latency will be missing. For example, we can set the value to the worst value
> (like a MED missing as worst ? :) ).
> 
> 
> Best regards,
> 
> Stephane
> 
> 
> _____________________________________________________________
> ____________________________________________________________
> 
> Ce message et ses pieces jointes peuvent contenir des informations
> confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou
> copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le
> signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages
> electroniques etant susceptibles d'alteration, Orange decline toute responsabilite
> si ce message a ete altere, deforme ou falsifie. Merci.
> 
> This message and its attachments may contain confidential or privileged
> information that may be protected by law; they should not be distributed, used
> or copied without authorisation.
> If you have received this email in error, please notify the sender and delete this
> message and its attachments.
> As emails may be altered, Orange is not liable for messages that have been
> modified, changed or falsified.
> Thank you.

v2.23.0 | Report a Bug | By Email