Re: [Idr] Fwd: WG LC:draft-ietf-l3vpn-v6-ext-communities

"Cayle Spandon" <cayle.spandon@gmail.com> Mon, 24 November 2008 17:59 UTC

Return-Path: <idr-bounces@ietf.org>
X-Original-To: idr-archive@megatron.ietf.org
Delivered-To: ietfarch-idr-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 683FA3A6932; Mon, 24 Nov 2008 09:59:18 -0800 (PST)
X-Original-To: idr@core3.amsl.com
Delivered-To: idr@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 553893A6932 for <idr@core3.amsl.com>; Mon, 24 Nov 2008 09:59:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.298
X-Spam-Level:
X-Spam-Status: No, score=-2.298 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_13=0.6]
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 jmzDO4onLLVT for <idr@core3.amsl.com>; Mon, 24 Nov 2008 09:59:15 -0800 (PST)
Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.176]) by core3.amsl.com (Postfix) with ESMTP id 65AC23A679C for <idr@ietf.org>; Mon, 24 Nov 2008 09:59:15 -0800 (PST)
Received: by wa-out-1112.google.com with SMTP id n4so1068241wag.5 for <idr@ietf.org>; Mon, 24 Nov 2008 09:59:12 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type:references; bh=UuDNcf6Lqp+qIOCpYzJtsbqwiOP2ZoPO1+9HHLrCq3g=; b=Oti7hiSnN630I51ORTTYU1jwOKNCRyQLked9EbNOdHvpQCpXlXtTf0STEAQCq8qfq5 diC/yK1xKGiC/d0URHwen491DgX/mLw1rSIujqwtaemFAtX1snAldRhnZHFP6CwnWHxk Js8Se3EkfSE9r6/Hq1scEqaDgK0az85P6uN6g=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:references; b=kA0/pRKAwhEvy8Nm3bD+kAMh4R6Kem8Gz+EQukPgk+96bgHFl9Js2sacH47GuCYDFp NK0nGoSor6XrbI4LQB2mbUz1/60cx33UNLod3HoWD/nNt2WXRl/8QJ9Agvaw5Xdnv3xZ Kz/wz9tL9SujLvFQyIlDV1/+OSeZhF3TVCDbQ=
Received: by 10.114.208.20 with SMTP id f20mr2021383wag.225.1227549552701; Mon, 24 Nov 2008 09:59:12 -0800 (PST)
Received: by 10.114.177.4 with HTTP; Mon, 24 Nov 2008 09:59:12 -0800 (PST)
Message-ID: <71c13900811240959k29e37997p5f17afda329b2a4c@mail.gmail.com>
Date: Mon, 24 Nov 2008 12:59:12 -0500
From: Cayle Spandon <cayle.spandon@gmail.com>
To: Yakov Rekhter <yakov@juniper.net>
In-Reply-To: <200811241656.mAOGutM45844@magenta.juniper.net>
MIME-Version: 1.0
References: <200811241656.mAOGutM45844@magenta.juniper.net>
Cc: idr@ietf.org
Subject: Re: [Idr] Fwd: WG LC:draft-ietf-l3vpn-v6-ext-communities
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: multipart/mixed; boundary="===============0859189742=="
Sender: idr-bounces@ietf.org
Errors-To: idr-bounces@ietf.org

Since we have to introduce a new attribute code anyway, I wonder if it is
worth going the extra mile by doing something more flexible (e.g.
http://www.watersprings.org/pub/id/draft-lange-flexible-bgp-communities-02.txt)
rather than pick another (bigger) fixed-length format.

On Mon, Nov 24, 2008 at 11:56 AM, Yakov Rekhter <yakov@juniper.net> wrote:

> Folks,
>
> As requested by L3VPN WG chairs, this is to share L3VPN WG LC on
> draft-ietf-l3vpn-v6-ext-communities. LC ends Dec 9, 2008.
>
> Yakov.
> ------- Forwarded Message
>
> Date:    Mon, 24 Nov 2008 09:51:05 -0700
> From:    Danny McPherson <danny@tcb.net>
> To:      Yakov Rekhter <yakov@juniper.net>, Sue Hares <shares@ghs.com>
> cc:      Marshall Eubanks <tme@multicasttech.com>
> Subject: Fwd: WG LC:draft-ietf-l3vpn-v6-ext-communities
>
>
> Given the content of this draft and past discussions of it's
> relation to IDR, we believe it to be useful to explicitly share
> this L3VPN WG LC with the IDR WG and welcome any feedback they
> might provide on it's content.
>
> As such, can you please share this with the IDR WG?
>
> Thanks!
>
> - -danny
>
>
> Begin forwarded message:
>
> > From: Danny McPherson <danny@tcb.net>
> > Date: November 24, 2008 9:45:48 AM MST
> > To: l3vpn@ietf.org
> > Subject: WG LC:draft-ietf-l3vpn-v6-ext-communities
> >
> >
> > Please consider today the start of a 2-week last call
> > for draft-ietf-l3vpn-v6-ext-communities, available here:
> >
> > http://tools.ietf.org/html/draft-ietf-l3vpn-v6-ext-communities
> >
> > Input on this draft's suitability for publication as an
> > Internet Standards Track document is solicited, WG Last
> > Call ends December 9, 2008.
> >
> > Note that draft-ietf-l3vpn-ospfv3-pece-01, for which the
> > status was discussed at the meeting last week (see the
> > proceeding and minutes in the meeting materials tool),
> > is dependent on this specification.
> >
> > Thanks in advance for your feedback!
> >
> > Danny & Marshall
> >
> >
> > Begin forwarded message:
> >
> >> From: Internet-Drafts@ietf.org
> >> Date: September 29, 2008 11:30:01 AM MDT
> >> To: i-d-announce@ietf.org
> >> Cc: l3vpn@ietf.org
> >> Subject: I-D ACTION:draft-ietf-l3vpn-v6-ext-communities-00.txt
> >>
> >> A New Internet-Draft is available from the on-line Internet-Drafts
> >> directories.
> >> This draft is a work item of the Layer 3 Virtual Private Networks
> >> Working Group of the IETF.
> >>
> >>      Title           : IPv6 Address Specific BGP Extended Communities
> Attrib
> ute
> >>      Author(s)       : Y. Rekhter
> >>      Filename        : draft-ietf-l3vpn-v6-ext-communities-00.txt
> >>      Pages           : 6
> >>      Date            : 2008-9-29
> >>
> >> Current specifications of BGP Extended Communities [BGP-EXTCOMM]
> >>  support IPv4 Address Specific Extended Community, but do not support
> >>  IPv6 Address Specific Extended Community. The lack of IPv6 Address
> >>  Specific Extended Community may be a problem when an application
> >> uses
> >>  IPv4 Address Specific Extended Community, and one wants to use this
> >>  application in a pure IPv6 environment. This document defines a new
> >>  BGP attribute, IPv6 Address Specific Extended Community that
> >>  addresses this problem. The IPv6 Address Specific Extended Community
> >>  is similar to the IPv4 Address Specific Extended Community, except
> >>  that it carries an IPv6 address rather than an IPv4 address.
> >>
> >>
> >>
> >>
> >> A URL for this Internet-Draft is:
> >>
> http://www.ietf.org/internet-drafts/draft-ietf-l3vpn-v6-ext-communities-00.t
> xt<http://www.ietf.org/internet-drafts/draft-ietf-l3vpn-v6-ext-communities-00.txt>
> >>
> >> Internet-Drafts are also available by anonymous FTP at:
> >> ftp://ftp.ietf.org/internet-drafts/
> >>
> >> Below is the data which will enable a MIME compliant mail reader
> >> implementation to automatically retrieve the ASCII version of the
> >> Internet-Draft.
> >>
> >
>
>
> ------- End of Forwarded Message
>
> _______________________________________________
> Idr mailing list
> Idr@ietf.org
> https://www.ietf.org/mailman/listinfo/idr
>
_______________________________________________
Idr mailing list
Idr@ietf.org
https://www.ietf.org/mailman/listinfo/idr