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

<stephane.litkowski@orange.com> Mon, 05 January 2015 16:21 UTC

Return-Path: <stephane.litkowski@orange.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 142CA1A1A9F for <idr@ietfa.amsl.com>; Mon, 5 Jan 2015 08:21:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] 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 1iMdRYItk0N9 for <idr@ietfa.amsl.com>; Mon, 5 Jan 2015 08:21:08 -0800 (PST)
Received: from relais-inet.francetelecom.com (relais-ias92.francetelecom.com [193.251.215.92]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F07571A1A95 for <idr@ietf.org>; Mon, 5 Jan 2015 08:21:07 -0800 (PST)
Received: from omfedm06.si.francetelecom.fr (unknown [xx.xx.xx.2]) by omfedm11.si.francetelecom.fr (ESMTP service) with ESMTP id 5EED33B41F0; Mon, 5 Jan 2015 17:21:06 +0100 (CET)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [10.114.31.5]) by omfedm06.si.francetelecom.fr (ESMTP service) with ESMTP id 4207F27C067; Mon, 5 Jan 2015 17:21:06 +0100 (CET)
Received: from OPEXCLILM34.corporate.adroot.infra.ftgroup ([169.254.4.68]) by OPEXCLILH01.corporate.adroot.infra.ftgroup ([::1]) with mapi id 14.03.0210.002; Mon, 5 Jan 2015 17:21:06 +0100
From: stephane.litkowski@orange.com
To: Xuxiaohu <xuxiaohu@huawei.com>
Thread-Topic: [Idr] WG adoption call for draft-xu-idr-performance-routing-01
Thread-Index: AdAgbI6qy548yW861UONDiDEo41VuP///H0AgAANiACAAA3TAIAAVR8AgAEQtgD/8FDYEA==
Date: Mon, 05 Jan 2015 16:21:05 +0000
Message-ID: <3390_1420474866_54AAB9F2_3390_41_1_9E32478DFA9976438E7A22F69B08FF920C74AB55@OPEXCLILM34.corporate.adroot.infra.ftgroup>
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>
In-Reply-To: <DB4PR06MB5765D44ADA00BE2C55FEDC79E520@DB4PR06MB576.eurprd06.prod.outlook.com>
Accept-Language: fr-FR, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.168.234.3]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-PMX-Version: 6.0.3.2322014, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2014.12.16.73920
Archived-At: http://mailarchive.ietf.org/arch/msg/idr/awZEN1c0G_QiWH1DsPncITPFTBo
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: Mon, 05 Jan 2015 16:21:10 -0000

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.