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

Xuxiaohu <xuxiaohu@huawei.com> Fri, 26 December 2014 01:29 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 DC3EF1A1B2F for <idr@ietfa.amsl.com>; Thu, 25 Dec 2014 17:29:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.911
X-Spam-Level:
X-Spam-Status: No, score=-1.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MANGLED_TOOL=2.3, 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 1C2_pHwkjjdi for <idr@ietfa.amsl.com>; Thu, 25 Dec 2014 17:29:50 -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 885821A1B2E for <idr@ietf.org>; Thu, 25 Dec 2014 17:29:49 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml401-hub.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BNI21532; Fri, 26 Dec 2014 01:29:47 +0000 (GMT)
Received: from NKGEML402-HUB.china.huawei.com (10.98.56.33) by lhreml401-hub.china.huawei.com (10.201.5.240) with Microsoft SMTP Server (TLS) id 14.3.158.1; Fri, 26 Dec 2014 01:29:46 +0000
Received: from NKGEML512-MBS.china.huawei.com ([169.254.8.199]) by nkgeml402-hub.china.huawei.com ([10.98.56.33]) with mapi id 14.03.0158.001; Fri, 26 Dec 2014 09:29:43 +0800
From: Xuxiaohu <xuxiaohu@huawei.com>
To: LUIS MIGUEL CONTRERAS MURILLO <luismiguel.contrerasmurillo@telefonica.com>, Robert Raszuk <robert@raszuk.net>, "Smith, Donald" <Donald.Smith@centurylink.com>
Thread-Topic: [Idr] WG adoption call for draft-xu-idr-performance-routing-01
Thread-Index: AdAgbI6qDeeSh60eTxGCTJRRuSQ2ov//hyQAgAANiQCAAA3SAP//Kb1Q
Date: Fri, 26 Dec 2014 01:29:42 +0000
Message-ID: <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE082EFA35@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>
In-Reply-To: <DB4PR06MB57639A06596D2CB0BFA83CB9E550@DB4PR06MB576.eurprd06.prod.outlook.com>
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/HOSudZvZF6IH7U5dV8GSeCbFiW8
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: Fri, 26 Dec 2014 01:29:53 -0000

Hi Robert, Luis and Smith,

Thanks a lot for your valuable comments. The logic of the statement of "MUST be able to be enabled" looks fine to me.

Therefore, how about saying something like "Performance Routing Capability negotiation between BGP peers which belong to different administration domains MUST be disabled by default."? 

Best regards,
Xiaohu

> -----Original Message-----
> From: Idr [mailto:idr-bounces@ietf.org] On Behalf Of LUIS MIGUEL CONTRERAS
> MURILLO
> Sent: Friday, December 26, 2014 4:25 AM
> To: Robert Raszuk; Smith, Donald
> Cc: idr@ietf.org; shares@ndzh.com
> Subject: Re: [Idr] WG adoption call for draft-xu-idr-performance-routing-01
> 
> Hi,
> 
> I agree. Probably the best formulation can be: "MUST be able to be enabled", in
> such a way that the performance routing capabilities are enabled in a by
> customer fashion.
> 
> Regards
> 
> Luis
> 
> -----Mensaje original-----
> De: rraszuk@gmail.com [mailto:rraszuk@gmail.com] En nombre de Robert
> Raszuk Enviado el: jueves, 25 de diciembre de 2014 20:36
> Para: Smith, Donald
> CC: LUIS MIGUEL CONTRERAS MURILLO; idr@ietf.org; shares@ndzh.com
> Asunto: Re: [Idr] WG adoption call for draft-xu-idr-performance-routing-01
> 
> The question here is what should be the default behavior. With your suggestions
> "MUST be able to be disabled" the default is ON which I think would be wrong.
> 
> If anything one may consider: "MUST be able to be enabled"
> 
> Cheers,
> r.
> 
> On Thu, Dec 25, 2014 at 7:47 PM, Smith, Donald
> <Donald.Smith@centurylink.com> wrote:
> > 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
> > ________________________________
> > 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.
> >
> > _______________________________________________
> > Idr mailing list
> > Idr@ietf.org
> > https://www.ietf.org/mailman/listinfo/idr
> >
> 
> ________________________________
> 
> 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
> _______________________________________________
> Idr mailing list
> Idr@ietf.org
> https://www.ietf.org/mailman/listinfo/idr