Re: accepting draft-fedyk-bgp-te-attribute-02.txt as a CCAMP WG document

[Yakov Rekhter <yakov@juniper.net>]

Adrian,

> Hi Yakov,
> 
> Could you explain why we would want to adopt 
> draft-fedyk-bgp-te-attribute-03.txt (note that your draft is at revision 03) 
> rather than draft-vasseur-ccamp-ce-ce-te-02.txt

Are you proposing to adopt draft-vasseur-ccamp-ce-ce-te-02.txt
as a CCAMP WG document ? (simple "yes/no" would suffice).

For one thing, draft-vasseur-ccamp-ce-ce-te-02.txt is unimplementable,
as (quoting from the draft) "The format of the BGP TE attribute will 
be defined in a further revision of this document." In contrast,
draft-fedyk-bgp-te-attribute-03.txt does define the format of the
BGP TE attribute, and is sufficient for implementing the attribute.

> The scope of your draft seems to be very open-ended which is quite worrying. 
> Perhaps you could help by telling us what the application space is. 

As you said below, *an* application of this draft is L1VPN.

> Your introduction section suggests that *an* application is L1VPN, and 
> if that is a representative application then your scope is identical 
> to the Vasseur draft.

Yakov.

> 
> Thanks,
> Adrian
> ----- Original Message ----- 
> From: "Yakov Rekhter" <yakov@juniper.net>
> To: "Adrian Farrel" <adrian@olddog.co.uk>; "Brungard, Deborah A, ALABS" 
> <dbrungard@att.com>; <ccamp@ops.ietf.org>
> Cc: "Hamid Ould-Brahim" <hbrahim@nortel.com>; "Don Fedyk" 
> <dwfedyk@nortel.com>; <yakov@juniper.net>
> Sent: Monday, October 01, 2007 8:06 PM
> Subject: accepting draft-fedyk-bgp-te-attribute-02.txt as a CCAMP WG 
> document
> 
> 
> > Deborah and Adrian,
> >
> > On behalf of the authors of draft-fedyk-bgp-te-attribute-02.txt we
> > would like to propose to accept this draft as a CCAMP WG document.
> > This draft went through IDR review and we incorporated the comments
> > in the latest version.
> >
> > Yakov.
> >
> > 
> 
>