IETF Logo Mail Archive

Re: [Softwires] WG Last Calldraft-ietf-softwire-bgp-te-attribute-00.txt

"Hamid Ould-Brahim" <hbrahim@nortel.com> Mon, 07 July 2008 15:35 UTC

Return-Path: <softwires-bounces@ietf.org>
X-Original-To: softwires-archive@megatron.ietf.org
Delivered-To: ietfarch-softwires-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8BBCE3A6AB2; Mon, 7 Jul 2008 08:35:30 -0700 (PDT)
X-Original-To: softwires@core3.amsl.com
Delivered-To: softwires@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E3E263A690A for <softwires@core3.amsl.com>; Mon, 7 Jul 2008 08:35:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.999
X-Spam-Level:
X-Spam-Status: No, score=-5.999 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BmeZ0M5UeMkX for <softwires@core3.amsl.com>; Mon, 7 Jul 2008 08:35:29 -0700 (PDT)
Received: from zrtps0kn.nortel.com (zrtps0kn.nortel.com [47.140.192.55]) by core3.amsl.com (Postfix) with ESMTP id DAABF3A65A6 for <softwires@ietf.org>; Mon, 7 Jul 2008 08:35:28 -0700 (PDT)
Received: from zcarhxm0.corp.nortel.com (zcarhxm0.corp.nortel.com [47.129.230.95]) by zrtps0kn.nortel.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id m67FZTR23370; Mon, 7 Jul 2008 15:35:29 GMT
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 07 Jul 2008 11:35:38 -0400
Message-ID: <085091CB2CA14E4B8B163FFC37C84E9D15906CE5@zcarhxm0.corp.nortel.com>
In-Reply-To: <011001c8d23a$7781cab0$84071fac@samitacD600>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [Softwires] WG Last Calldraft-ietf-softwire-bgp-te-attribute-00.txt
Thread-Index: AcjSLXlFCIoxvMGRSW+zYAv5kNnFJgAC8S0AA4M9SxA=
References: <3DF33E26-3F86-4FA8-B810-951EDBAED0E0@cisco.com> <C24FB26C-3CD4-40CE-A254-4EC7675E2CDB@cisco.com> <011001c8d23a$7781cab0$84071fac@samitacD600>
From: Hamid Ould-Brahim <hbrahim@nortel.com>
To: Samita Chakrabarti <samitac@ipinfusion.com>, David Ward <dward@cisco.com>, softwires@ietf.org, Yakov Rekhter <yakov@juniper.net>, Don Fedyk <dwfedyk@nortel.com>
Subject: Re: [Softwires] WG Last Calldraft-ietf-softwire-bgp-te-attribute-00.txt
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/softwires>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/softwires>, <mailto:softwires-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: softwires-bounces@ietf.org
Errors-To: softwires-bounces@ietf.org

Hi Samita,

Thanks for the feedback. I think there are already some 
sentences in the draft that cover precisely
this request such as:

  In certain cases (e.g., L1VPN [L1VPN]) it may be useful to augment
  reachability information carried in BGP with the Traffic Engineering
  information.
   
  This document defines a new BGP attribute, Traffic Engineering
  attribute, than enables BGP [BGP-4] to carry Traffic Engineering
  information.

Do you see we need to add more to this? 

Hamid.

 

> -----Original Message-----
> From: Samita Chakrabarti [mailto:samitac@ipinfusion.com] 
> Sent: Thursday, June 19, 2008 2:30 PM
> To: 'David Ward'; softwires@ietf.org; 'Yakov Rekhter'; Fedyk, 
> Don (BL60:1A00); Ould-Brahim, Hamid (CAR:1A14)
> Cc: alain_durand@cable.comcast.com
> Subject: RE: [Softwires] WG Last 
> Calldraft-ietf-softwire-bgp-te-attribute-00.txt
> 
> Hi all:
> 
> I have reviewed the draft. It would be very useful if this 
> document provides a section on applicability of this new 
> attribute. Currently, it is not clear, to the general reader 
> in which scenario this attribute should be added/configured 
> to a BGP implementation. A few sentences on a deployment 
> scenario for which this attribute will be sent and received 
> will seem to benefit this work.
> 
> Thanks,
> -Samita
> 
> >-----Original Message-----
> >From: softwires-bounces@ietf.org 
> [mailto:softwires-bounces@ietf.org] On 
> >Behalf Of David Ward
> >Sent: Thursday, June 19, 2008 9:57 AM
> >To: softwires@ietf.org; Yakov Rekhter; Don Fedyk; Hamid Ould-Brahim
> >Subject: Re: [Softwires] WG Last 
> >Calldraft-ietf-softwire-bgp-te-attribute-
> >00.txt
> >
> >
> >All -
> >
> >	We are starting a two week working group (in the 
> softwires WG)  last 
> >call for the draft:
> >
> >http://www.ietf.org/internet-drafts/draft-ietf-softwire-bgp-te-
> >attribute-00.txt
> >
> >
> >Please send your comments before 1700 CDT 2008.07.03
> >
> >Thanks
> >
> >DWard, Alain
> >
> >_______________________________________________
> >Softwires mailing list
> >Softwires@ietf.org
> >https://www.ietf.org/mailman/listinfo/softwires
> 
> 
> 
> 
_______________________________________________
Softwires mailing list
Softwires@ietf.org
https://www.ietf.org/mailman/listinfo/softwires

v2.23.0 | Report a Bug | By Email