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

"Smith, Donald" <Donald.Smith@CenturyLink.com> Thu, 25 December 2014 18:47 UTC

Return-Path: <Donald.Smith@CenturyLink.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 69D9B1A885E for <idr@ietfa.amsl.com>; Thu, 25 Dec 2014 10:47:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.401
X-Spam-Level:
X-Spam-Status: No, score=0.401 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, MANGLED_TOOL=2.3] autolearn=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 tskjt44QQQ8S for <idr@ietfa.amsl.com>; Thu, 25 Dec 2014 10:47:19 -0800 (PST)
Received: from suomp64i.qwest.com (suomp64i.qwest.com [155.70.16.237]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6FBFE1A885F for <idr@ietf.org>; Thu, 25 Dec 2014 10:47:19 -0800 (PST)
Received: from lxdenvmpc030.qintra.com (lxdenvmpc030.qintra.com [10.1.51.30]) by suomp64i.qwest.com (8.14.4/8.14.4) with ESMTP id sBPIlG2a010390 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 25 Dec 2014 12:47:17 -0600 (CST)
Received: from lxdenvmpc030.qintra.com (unknown [127.0.0.1]) by IMSA (Postfix) with ESMTP id B90701E005E; Thu, 25 Dec 2014 11:47:11 -0700 (MST)
Received: from lxomp07u.corp.intranet (unknown [151.119.91.93]) by lxdenvmpc030.qintra.com (Postfix) with ESMTP id 7E0D51E004E; Thu, 25 Dec 2014 11:47:10 -0700 (MST)
Received: from lxomp07u.corp.intranet (localhost [127.0.0.1]) by lxomp07u.corp.intranet (8.14.8/8.14.8) with ESMTP id sBPIlAQr009220; Thu, 25 Dec 2014 12:47:10 -0600
Received: from vddcwhubex501.ctl.intranet (vddcwhubex501.ctl.intranet [151.119.128.28]) by lxomp07u.corp.intranet (8.14.8/8.14.8) with ESMTP id sBPIl9h7009215 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 25 Dec 2014 12:47:10 -0600
Received: from PDDCWMBXEX503.ctl.intranet ([fe80::9033:ef22:df02:32a9]) by vddcwhubex501.ctl.intranet ([2002:9777:801c::9777:801c]) with mapi id 14.03.0195.001; Thu, 25 Dec 2014 11:47:09 -0700
From: "Smith, Donald" <Donald.Smith@CenturyLink.com>
To: LUIS MIGUEL CONTRERAS MURILLO <luismiguel.contrerasmurillo@telefonica.com>, "idr@ietf.org" <idr@ietf.org>
Thread-Topic: WG adoption call for draft-xu-idr-performance-routing-01
Thread-Index: AdAgbI6qAjwYz79e0k2KEKRfJZozpQABkptV
Date: Thu, 25 Dec 2014 18:47:08 +0000
Message-ID: <68EFACB32CF4464298EA2779B058889D24C778C7@PDDCWMBXEX503.ctl.intranet>
References: <DB4PR06MB576D18C5E4A6B1AE49BA8C39E550@DB4PR06MB576.eurprd06.prod.outlook.com>
In-Reply-To: <DB4PR06MB576D18C5E4A6B1AE49BA8C39E550@DB4PR06MB576.eurprd06.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [155.70.40.132]
Content-Type: multipart/alternative; boundary="_000_68EFACB32CF4464298EA2779B058889D24C778C7PDDCWMBXEX503ct_"
MIME-Version: 1.0
X-TM-AS-MML: disable
X-CFilter-Loop: Reflected
Archived-At: http://mailarchive.ietf.org/arch/msg/idr/_Q_Rn5MJCjtDGah3kaPxcASf7qQ
Cc: "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: Thu, 25 Dec 2014 18:47:21 -0000

Good catch, I think: MUST be able to be disabled per peer/AS/session (so you can offer it intra peer, where when you want.)



(coffee != sleep) & (!coffee == sleep)
 Donald.Smith@centurylink.com<mailto:Donald.Smith@centurylink.com>
________________________________
From: Idr [idr-bounces@ietf.org] on behalf of LUIS MIGUEL CONTRERAS MURILLO [luismiguel.contrerasmurillo@telefonica.com]
Sent: Thursday, December 25, 2014 11:15 AM
To: idr@ietf.org
Cc: shares@ndzh.com
Subject: Re: [Idr] WG adoption call for draft-xu-idr-performance-routing-01

Hi all,

I do support the adoption of draft-xu-idr-performance-routing as WG document.

I have however a comment. In section 9, Security Considerations, bullet a, it is mentioned that “it MUST disable Performance Routing Capability negotiation between BGP peers which belong to different administration domains.” As stated along the draft, the performance-based routing capability is created to offer performance route selection criteria to customers of service providers which own networks formed by different ASes. In my understanding those customers are clearly different administration domains with regard the one of the service provider. Then Performance Routing Capability has to be enabled in that cases. So I would relax the sentence in the way: “it MAY be disabled …” or something like that, to be consistent  with the aim of  the draft.

Thanks

Best regards

Luis

From: Susan Hares [mailto:shares@ndzh.com]
Sent: Tuesday, December 23, 2014 10:37 PM
To: idr wg
Cc: Xuxiaohu; John G. Scudder
Subject: WG adoption call for draft-xu-idr-performance-routing-01

This is to begin a 2 Week WG adoption call for draft-xu-idr-performance-routing-01  (12/23/2014 to 01/6/2014).  The draft can be accessed at:

 http://datatracker.ietf.org/doc/draft-xu-idr-performance-routing/.

In your response, please discuss the pros/cons of this approach and indicate “support” or “no support”.

Thank you,

Sue Hares



________________________________

Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, puede contener información privilegiada o confidencial y es para uso exclusivo de la persona o entidad de destino. Si no es usted. el destinatario indicado, queda notificado de que la lectura, utilización, divulgación y/o copia sin autorización puede estar prohibida en virtud de la legislación vigente. Si ha recibido este mensaje por error, le rogamos que nos lo comunique inmediatamente por esta misma vía y proceda a su destrucción.

The information contained in this transmission is privileged and confidential information intended only for the use of the individual or entity named above. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this transmission in error, do not read it. Please immediately reply to the sender that you have received this communication in error and then delete it.

Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinatário, pode conter informação privilegiada ou confidencial e é para uso exclusivo da pessoa ou entidade de destino. Se não é vossa senhoria o destinatário indicado, fica notificado de que a leitura, utilização, divulgação e/ou cópia sem autorização pode estar proibida em virtude da legislação vigente. Se recebeu esta mensagem por erro, rogamos-lhe que nos o comunique imediatamente por esta mesma via e proceda a sua destruição
This communication is the property of CenturyLink and may contain confidential or privileged information. Unauthorized use of this communication is strictly prohibited and may be unlawful. If you have received this communication in error, please immediately notify the sender by reply e-mail and destroy all copies of the communication and any attachments.