
From dongjie_dj@huawei.com  Mon Nov  2 17:57:00 2009
Return-Path: <dongjie_dj@huawei.com>
X-Original-To: l3vpn@core3.amsl.com
Delivered-To: l3vpn@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DE8C13A6844; Mon,  2 Nov 2009 17:57:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.805
X-Spam-Level: 
X-Spam-Status: No, score=0.805 tagged_above=-999 required=5 tests=[AWL=1.300,  BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553,  RDNS_NONE=0.1]
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 6fpNRq2uqHhp; Mon,  2 Nov 2009 17:57:00 -0800 (PST)
Received: from szxga03-in.huawei.com (unknown [119.145.14.66]) by core3.amsl.com (Postfix) with ESMTP id DF0603A682F; Mon,  2 Nov 2009 17:56:59 -0800 (PST)
Received: from huawei.com (szxga03-in [172.24.2.9]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KSI00L6LG39GI@szxga03-in.huawei.com>; Tue, 03 Nov 2009 09:57:09 +0800 (CST)
Received: from huawei.com ([172.24.1.24]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KSI00A3XG39HH@szxga03-in.huawei.com>; Tue, 03 Nov 2009 09:57:09 +0800 (CST)
Received: from d65110 ([10.111.12.97]) by szxml04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0KSI00B0WG38NV@szxml04-in.huawei.com>; Tue, 03 Nov 2009 09:57:09 +0800 (CST)
Date: Tue, 03 Nov 2009 09:57:08 +0800
From: Jie Dong <dongjie_dj@huawei.com>
Subject: RE: Last Call: draft-ietf-l3vpn-2547bis-mcast-bgp (BGP Encodings andProcedures for Multicast in MPLS/BGP IP VPNs) to Proposed Standard
In-reply-to: <20090825204712.6F41628C290@core3.amsl.com>
To: ietf@ietf.org, 'IETF-Announce' <ietf-announce@ietf.org>
Message-id: <028201ca5c28$f3cc4c20$610c6f0a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
X-Mailer: Microsoft Office Outlook 11
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Thread-index: Acolxd/6RSMIS05DQ6a8ErKrXJXs2Q16ZHwQ
Cc: l3vpn@ietf.org
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <l3vpn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/l3vpn>, <mailto:l3vpn-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/l3vpn>
List-Post: <mailto:l3vpn@ietf.org>
List-Help: <mailto:l3vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/l3vpn>, <mailto:l3vpn-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 03 Nov 2009 01:57:01 -0000

Hi, 

Here are some comments on this draft. (hope this is not too late:)

1. 4-octets ASN support

The IANA Consideration section says the Source AS extended community is
2-octet AS specific. Consider that 4-octet ASN is supported in other
sections of this draft, a 4-octet AS specific equivalent  should also be
defined. 

2. Section 8: PE distinguish Labels Attribute

            +---------------------------------+
            |           PE Address            |
            +---------------------------------+
            |     Label (3 octets)            |
            +---------------------------------+
            .......
            +---------------------------------+
            |           PE Address            |
            +---------------------------------+
            |     Label (3 octets)            |
            +---------------------------------+

If my understanding is correct, this attribute can contain multiple PE
address-Label pairs. thus more than 1 PE address can exist in this
attribute. So the statement below may be inaccurate:

"The attribute is also considered to be malformed if the PE Address field is
expected to be an IPv4 address, and the length of the attribute minus 4 is
not a multiple of 3, or the PE Address field is expected to be an IPv6
address, and the length of the attribute minus 16 is not a multiple of 3."

3. In section 11.1.3, it says: 

"Inter-AS I-PMSI A-D routes are not used to support non-segmented inter-AS
tunnels...The Source AS field in the C-multicast route is set to value of
the Originating Router's IP Address field of the found Intra-AS I-PMSI A-D
route."

Does this mean that for non-segmented inter-AS tunnel, the Source AS filed
of C-multicast route will be filled with an IP address? It may not
consistent with statement in the first paragraph of this section:

"From the selected UMH route the local PE extracts (a) the autonomous system
number of the upstream PE (as carried in the Source AS extended community of
the route), and (b) the C-multicast Import RT of the VRF on the upstream PE
(the value of this C-multicast Import RT is the value of the VRF Route
Import Extended Community carried by the route). The Source AS field in the
C-multicast route is set to that autonomous system."

Besides, if the Originating Router's IP Address is an IPv6 address, it
cannot be filled into the Source AS field of C-multicast route (4-octet).

4. Considerations about Route advertising Efficiency

In this draft, A-D route may carry a PMSI tunnel attribute. MCAST-VPN NLRIs
with different PMSI tunnel attributes have to be advertised using different
BGP update messages. 

Different multicast flows using different P-tunnels will be advertised using
individual update messages. This can be acceptable.

However,  if multiple multicast flows are aggregated into the same P-tunnel,
due to the different upstream/downstream labels in their PMSI tunnel
attributes, they still cannot be combined into one update message. Maybe
there is some space to improve the efficiency? For example, the label field
in PMSI tunnel attribute could be moved into the NLRIs of A-D route.



Best regards,
Jie
 

> -----Original Message-----
> From: l3vpn-bounces@ietf.org [mailto:l3vpn-bounces@ietf.org] 
> On Behalf Of The IESG
> Sent: Wednesday, August 26, 2009 4:47 AM
> To: IETF-Announce
> Cc: l3vpn@ietf.org
> Subject: Last Call: draft-ietf-l3vpn-2547bis-mcast-bgp (BGP 
> Encodings andProcedures for Multicast in MPLS/BGP IP VPNs) to 
> Proposed Standard
> 
> The IESG has received a request from the Layer 3 Virtual 
> Private Networks WG (l3vpn) to consider the following document:
> 
> - 'BGP Encodings and Procedures for Multicast in MPLS/BGP IP VPNs '
>    <draft-ietf-l3vpn-2547bis-mcast-bgp-07.txt> as a Proposed Standard
> 
> The IESG plans to make a decision in the next few weeks, and 
> solicits final comments on this action.  Please send 
> substantive comments to the ietf@ietf.org mailing lists by 
> 2009-09-08. Exceptionally, comments may be sent to 
> iesg@ietf.org instead. In either case, please retain the 
> beginning of the Subject line to allow automated sorting.
> 
> The file can be obtained via
> http://www.ietf.org/internet-drafts/draft-ietf-l3vpn-2547bis-m
> cast-bgp-07.txt
> 
> 
> IESG discussion can be tracked via
> https://datatracker.ietf.org/public/pidtracker.cgi?command=vie
> w_id&dTag=15061&rfc_flag=0
> 


From thomas.morin@orange-ftgroup.com  Sun Nov  8 23:47:38 2009
Return-Path: <thomas.morin@orange-ftgroup.com>
X-Original-To: l3vpn@core3.amsl.com
Delivered-To: l3vpn@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 485CF28C1C0 for <l3vpn@core3.amsl.com>; Sun,  8 Nov 2009 23:47:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.32
X-Spam-Level: 
X-Spam-Status: No, score=-1.32 tagged_above=-999 required=5 tests=[AWL=-0.929,  BAYES_20=-0.74, HELO_EQ_FR=0.35]
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 GVKApew4VXvi for <l3vpn@core3.amsl.com>; Sun,  8 Nov 2009 23:47:37 -0800 (PST)
Received: from r-mail2.rd.francetelecom.com (r-mail2.rd.francetelecom.com [217.108.152.42]) by core3.amsl.com (Postfix) with ESMTP id 0C7B728C193 for <l3vpn@ietf.org>; Sun,  8 Nov 2009 23:47:36 -0800 (PST)
Received: from ftrdmel10.rd.francetelecom.fr ([10.192.128.44]) by ftrdsmtp2.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.3959);  Mon, 9 Nov 2009 08:48:01 +0100
Received: from [10.193.116.45] ([10.193.116.45]) by ftrdmel10.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.3959);  Mon, 9 Nov 2009 08:48:00 +0100
Message-ID: <4AF7C92E.4050904@orange-ftgroup.com>
Date: Mon, 09 Nov 2009 16:47:58 +0900
From: Thomas Morin <thomas.morin@orange-ftgroup.com>
Organization: France Telecom Orange
User-Agent: Mozilla/5.0 (X11; U; Linux i686; fr; rv:1.9.1.6pre) Gecko/20091104 Lightning/1.0pre Shredder/3.0pre
MIME-Version: 1.0
To: L3VPN <l3vpn@ietf.org>
Subject: draft-ietf-l3vpn-mvpn-considerations-05
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 09 Nov 2009 07:48:01.0218 (UTC) FILETIME=[F63F1220:01CA6110]
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <l3vpn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/l3vpn>, <mailto:l3vpn-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/l3vpn>
List-Post: <mailto:l3vpn@ietf.org>
List-Help: <mailto:l3vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/l3vpn>, <mailto:l3vpn-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 09 Nov 2009 07:47:38 -0000

Hello working group,

Feedback is highly welcome on the last revision of 
draft-ietf-l3vpn-mvpn-considerations, especially on the non editorial 
changes such as the now fully revised Appendix A that compares the 
behavior of the different C-multicast routing approaches with reference 
to mVPN SSM/ASM routing scalability.

The changes made in this revision and the previous one are described in 
the slides presented this afternoon ( 
http://tools.ietf.org/agenda/76/slides/l3vpn-0.pdf ).

Thank you,

-Thomas

From wim.henderickx@alcatel-lucent.be  Mon Nov  9 13:40:17 2009
Return-Path: <wim.henderickx@alcatel-lucent.be>
X-Original-To: l3vpn@core3.amsl.com
Delivered-To: l3vpn@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A0D6428C0D8 for <l3vpn@core3.amsl.com>; Mon,  9 Nov 2009 13:40:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.649
X-Spam-Level: 
X-Spam-Status: No, score=-5.649 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35, 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 bC6QVVLIrt2U for <l3vpn@core3.amsl.com>; Mon,  9 Nov 2009 13:40:16 -0800 (PST)
Received: from smail3.alcatel.fr (smail3.alcatel.fr [62.23.212.56]) by core3.amsl.com (Postfix) with ESMTP id 25E5528C278 for <l3vpn@ietf.org>; Mon,  9 Nov 2009 13:39:57 -0800 (PST)
Received: from FRVELSBHS02.ad2.ad.alcatel.com (frvelsbhs02.dc-m.alcatel-lucent.com [155.132.6.74]) by smail3.alcatel.fr (8.13.8/8.13.8/ICT) with ESMTP id nA9LeLtp030164;  Mon, 9 Nov 2009 22:40:21 +0100
Received: from FRVELSMBS22.ad2.ad.alcatel.com ([155.132.6.55]) by FRVELSBHS02.ad2.ad.alcatel.com with Microsoft SMTPSVC(6.0.3790.3959); Mon, 9 Nov 2009 22:40:21 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: draft-ietf-l3vpn-mvpn-considerations-05
Date: Mon, 9 Nov 2009 22:40:20 +0100
Message-ID: <B128F666D4C8BD4FBF56CEAFB2DB66D7066E665D@FRVELSMBS22.ad2.ad.alcatel.com>
In-Reply-To: <4AF7C92E.4050904@orange-ftgroup.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: draft-ietf-l3vpn-mvpn-considerations-05
Thread-Index: AcphEP7OPp8G0ZQvRZWgKFBQf6m+eAAc/u/g
References: <4AF7C92E.4050904@orange-ftgroup.com>
From: "HENDERICKX Wim" <wim.henderickx@alcatel-lucent.be>
To: "Thomas Morin" <thomas.morin@orange-ftgroup.com>, "L3VPN" <l3vpn@ietf.org>
X-OriginalArrivalTime: 09 Nov 2009 21:40:21.0713 (UTC) FILETIME=[3D19DC10:01CA6185]
X-Scanned-By: MIMEDefang 2.57 on 155.132.188.83
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <l3vpn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/l3vpn>, <mailto:l3vpn-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/l3vpn>
List-Post: <mailto:l3vpn@ietf.org>
List-Help: <mailto:l3vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/l3vpn>, <mailto:l3vpn-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 09 Nov 2009 21:40:17 -0000

I did an extensive review today especially on the appendix and I must
admit this is a great piece of work and support the statements made in
the draft.

-----Original Message-----
From: l3vpn-bounces@ietf.org [mailto:l3vpn-bounces@ietf.org] On Behalf
Of Thomas Morin
Sent: maandag 9 november 2009 8:48
To: L3VPN
Subject: draft-ietf-l3vpn-mvpn-considerations-05

Hello working group,

Feedback is highly welcome on the last revision of=20
draft-ietf-l3vpn-mvpn-considerations, especially on the non editorial=20
changes such as the now fully revised Appendix A that compares the=20
behavior of the different C-multicast routing approaches with reference=20
to mVPN SSM/ASM routing scalability.

The changes made in this revision and the previous one are described in=20
the slides presented this afternoon (=20
http://tools.ietf.org/agenda/76/slides/l3vpn-0.pdf ).

Thank you,

-Thomas

From yakov@juniper.net  Mon Nov  9 14:16:26 2009
Return-Path: <yakov@juniper.net>
X-Original-To: l3vpn@core3.amsl.com
Delivered-To: l3vpn@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 831933A68C1; Mon,  9 Nov 2009 14:16:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 fEcBMnovhoMM; Mon,  9 Nov 2009 14:16:25 -0800 (PST)
Received: from exprod7og118.obsmtp.com (exprod7og118.obsmtp.com [64.18.2.8]) by core3.amsl.com (Postfix) with ESMTP id B8C8B3A6904; Mon,  9 Nov 2009 14:16:21 -0800 (PST)
Received: from source ([66.129.224.36]) (using TLSv1) by exprod7ob118.postini.com ([64.18.6.12]) with SMTP ID DSNKSviU0Mi45XmH4hQtYStJ42cy24XNzNyO@postini.com; Mon, 09 Nov 2009 14:16:52 PST
Received: from p-emfe01-sac.jnpr.net (66.129.254.72) by P-EMHUB01-HQ.jnpr.net (172.24.192.35) with Microsoft SMTP Server id 8.1.375.2; Mon, 9 Nov 2009 14:15:45 -0800
Received: from p-emlb02-sac.jnpr.net ([66.129.254.47]) by p-emfe01-sac.jnpr.net with Microsoft SMTPSVC(6.0.3790.3959); Mon, 9 Nov 2009 14:15:45 -0800
Received: from emailsmtp55.jnpr.net ([172.24.18.132]) by p-emlb02-sac.jnpr.net with Microsoft SMTPSVC(6.0.3790.3959); Mon, 9 Nov 2009 14:15:44 -0800
Received: from magenta.juniper.net ([172.17.27.123]) by emailsmtp55.jnpr.net with Microsoft SMTPSVC(6.0.3790.3959); Mon, 9 Nov 2009 14:15:44 -0800
Received: from juniper.net (sapphire.juniper.net [172.17.28.108])	by magenta.juniper.net (8.11.3/8.11.3) with ESMTP id nA9MFij39175; Mon, 9 Nov 2009 14:15:44 -0800 (PST)	(envelope-from yakov@juniper.net)
Message-ID: <200911092215.nA9MFij39175@magenta.juniper.net>
To: Jie Dong <dongjie_dj@huawei.com>
Subject: Re: Last Call: draft-ietf-l3vpn-2547bis-mcast-bgp (BGP Encodings andProcedures for Multicast in MPLS/BGP IP VPNs) to Proposed Standard 
In-Reply-To: <028201ca5c28$f3cc4c20$610c6f0a@china.huawei.com> 
References: <028201ca5c28$f3cc4c20$610c6f0a@china.huawei.com>
X-MH-In-Reply-To: Jie Dong <dongjie_dj@huawei.com> message dated "Tue, 03 Nov 2009 09:57:08 +0800."
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <76878.1257804943.1@juniper.net>
Date: Mon, 9 Nov 2009 14:15:44 -0800
From: Yakov Rekhter <yakov@juniper.net>
X-OriginalArrivalTime: 09 Nov 2009 22:15:44.0474 (UTC) FILETIME=[2E5D7BA0:01CA618A]
Cc: ietf@ietf.org, 'IETF-Announce' <ietf-announce@ietf.org>, l3vpn@ietf.org
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <l3vpn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/l3vpn>, <mailto:l3vpn-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/l3vpn>
List-Post: <mailto:l3vpn@ietf.org>
List-Help: <mailto:l3vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/l3vpn>, <mailto:l3vpn-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 09 Nov 2009 22:16:26 -0000

Jie,

> Hi, 
> 
> Here are some comments on this draft. (hope this is not too late:)

see in-line...

> 1. 4-octets ASN support
> 
> The IANA Consideration section says the Source AS extended community is
> 2-octet AS specific. Consider that 4-octet ASN is supported in other
> sections of this draft, a 4-octet AS specific equivalent  should also be
> defined. 

Agreed. 

> 2. Section 8: PE distinguish Labels Attribute
> 
>             +---------------------------------+
>             |           PE Address            |
>             +---------------------------------+
>             |     Label (3 octets)            |
>             +---------------------------------+
>             .......
>             +---------------------------------+
>             |           PE Address            |
>             +---------------------------------+
>             |     Label (3 octets)            |
>             +---------------------------------+
> 
> If my understanding is correct, this attribute can contain multiple PE
> address-Label pairs. thus more than 1 PE address can exist in this
> attribute. So the statement below may be inaccurate:
> 
> "The attribute is also considered to be malformed if the PE Address field is
> expected to be an IPv4 address, and the length of the attribute minus 4 is
> not a multiple of 3, or the PE Address field is expected to be an IPv6
> address, and the length of the attribute minus 16 is not a multiple of 3."

Thanks for catching this. The correct text should be as follows:

 "The attribute is also considered to be malformed if the PE Address field is
 expected to be an IPv4 address, and the length of the attribute is
 not a multiple of 7, or the PE Address field is expected to be an IPv6
 address, and the length of the attribute is not a multiple of 19."

> 3. In section 11.1.3, it says: 
> 
> "Inter-AS I-PMSI A-D routes are not used to support non-segmented inter-AS
> tunnels...The Source AS field in the C-multicast route is set to value of
> the Originating Router's IP Address field of the found Intra-AS I-PMSI A-D
> route."
> 
> Does this mean that for non-segmented inter-AS tunnel, the Source AS filed
> of C-multicast route will be filled with an IP address? 

Yes.

> It may not consistent with statement in the first paragraph of this section:
>
> "From the selected UMH route the local PE extracts (a) the autonomous system
> number of the upstream PE (as carried in the Source AS extended community of
> the route), and (b) the C-multicast Import RT of the VRF on the upstream PE
> (the value of this C-multicast Import RT is the value of the VRF Route
> Import Extended Community carried by the route). The Source AS field in the
> C-multicast route is set to that autonomous system."

The text you are quoting above applies when one uses segmented
inter-AS tunnels.

> Besides, if the Originating Router's IP Address is an IPv6 address, it
> cannot be filled into the Source AS field of C-multicast route (4-octet).
>  
> 4. Considerations about Route advertising Efficiency
> 
> In this draft, A-D route may carry a PMSI tunnel attribute. MCAST-VPN NLRIs
> with different PMSI tunnel attributes have to be advertised using different
> BGP update messages. 
> 
> Different multicast flows using different P-tunnels will be advertised using
> individual update messages. This can be acceptable.
> 
> However,  if multiple multicast flows are aggregated into the same P-tunnel,
> due to the different upstream/downstream labels in their PMSI tunnel
> attributes, they still cannot be combined into one update message. Maybe
> there is some space to improve the efficiency? For example, the label field
> in PMSI tunnel attribute could be moved into the NLRIs of A-D route.

When multiple multicast flows are aggregated into the same P-tunnel,
and each of these flows uses different upstream-assigned label,
then it is likely that these flows belong to different MVPNs. As
such, the routes that advertise these flows and their P-tunnel have
different RTs, and thus should not be combined into a single BGP
Update message.
  
Yakov.

From rahul@juniper.net  Mon Nov  9 23:05:00 2009
Return-Path: <rahul@juniper.net>
X-Original-To: l3vpn@core3.amsl.com
Delivered-To: l3vpn@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8AAB33A6905 for <l3vpn@core3.amsl.com>; Mon,  9 Nov 2009 23:05:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 i4nhAH4sfhYD for <l3vpn@core3.amsl.com>; Mon,  9 Nov 2009 23:04:59 -0800 (PST)
Received: from exprod7og119.obsmtp.com (exprod7og119.obsmtp.com [64.18.2.16]) by core3.amsl.com (Postfix) with ESMTP id 985753A6899 for <l3vpn@ietf.org>; Mon,  9 Nov 2009 23:04:58 -0800 (PST)
Received: from source ([66.129.224.36]) (using TLSv1) by exprod7ob119.postini.com ([64.18.6.12]) with SMTP ID DSNKSvkQtVqwgWOwIiBcKkfyGWTS/roww9k0@postini.com; Mon, 09 Nov 2009 23:05:27 PST
Received: from p-emfe01-sac.jnpr.net (66.129.254.72) by P-EMHUB01-HQ.jnpr.net (172.24.192.35) with Microsoft SMTP Server id 8.1.375.2; Mon, 9 Nov 2009 23:02:09 -0800
Received: from p-emlb02-sac.jnpr.net ([66.129.254.47]) by p-emfe01-sac.jnpr.net with Microsoft SMTPSVC(6.0.3790.3959); Mon, 9 Nov 2009 23:02:09 -0800
Received: from emailsmtp56.jnpr.net ([172.24.60.77]) by p-emlb02-sac.jnpr.net with Microsoft SMTPSVC(6.0.3790.3959); Mon, 9 Nov 2009 23:02:08 -0800
Received: from magenta.juniper.net ([172.17.27.123]) by emailsmtp56.jnpr.net with Microsoft SMTPSVC(6.0.3790.3959); Mon, 9 Nov 2009 23:02:08 -0800
Received: from sapphire.juniper.net (sapphire.juniper.net [172.17.28.108])	by magenta.juniper.net (8.11.3/8.11.3) with ESMTP id nAA727j80668; Mon, 9 Nov 2009 23:02:07 -0800 (PST)	(envelope-from rahul@juniper.net)
Date: Mon, 9 Nov 2009 23:02:07 -0800
From: Rahul Aggarwal <rahul@juniper.net>
To: Thomas Morin <thomas.morin@orange-ftgroup.com>
Subject: Re: draft-ietf-l3vpn-mvpn-considerations-05
In-Reply-To: <4AF7C92E.4050904@orange-ftgroup.com>
Message-ID: <20091109230120.S25926@sapphire.juniper.net>
References: <4AF7C92E.4050904@orange-ftgroup.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
X-OriginalArrivalTime: 10 Nov 2009 07:02:08.0153 (UTC) FILETIME=[B7B47090:01CA61D3]
Cc: L3VPN <l3vpn@ietf.org>
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <l3vpn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/l3vpn>, <mailto:l3vpn-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/l3vpn>
List-Post: <mailto:l3vpn@ietf.org>
List-Help: <mailto:l3vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/l3vpn>, <mailto:l3vpn-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 10 Nov 2009 07:05:00 -0000

I commend the authors for the revised analysis in Appendix A. I have
reviewed this and the draft is ready to be moved forward to
the IESG.

rahul



On Mon, 9 Nov 2009, Thomas Morin wrote:

> Hello working group,
>
> Feedback is highly welcome on the last revision of
> draft-ietf-l3vpn-mvpn-considerations, especially on the non editorial
> changes such as the now fully revised Appendix A that compares the
> behavior of the different C-multicast routing approaches with reference
> to mVPN SSM/ASM routing scalability.
>
> The changes made in this revision and the previous one are described in
> the slides presented this afternoon (
> http://tools.ietf.org/agenda/76/slides/l3vpn-0.pdf ).
>
> Thank you,
>
> -Thomas
>

From yakov@juniper.net  Thu Nov 12 05:36:20 2009
Return-Path: <yakov@juniper.net>
X-Original-To: l3vpn@core3.amsl.com
Delivered-To: l3vpn@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C6FA53A6B7B for <l3vpn@core3.amsl.com>; Thu, 12 Nov 2009 05:36:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, 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 Ifwk0CrtawJP for <l3vpn@core3.amsl.com>; Thu, 12 Nov 2009 05:36:20 -0800 (PST)
Received: from exprod7og101.obsmtp.com (exprod7og101.obsmtp.com [64.18.2.155]) by core3.amsl.com (Postfix) with ESMTP id B876F3A6BAA for <l3vpn@ietf.org>; Thu, 12 Nov 2009 05:36:18 -0800 (PST)
Received: from source ([66.129.224.36]) (using TLSv1) by exprod7ob101.postini.com ([64.18.6.12]) with SMTP ID DSNKSvwPb52pH/j+kv0h1cUVsUUoM+99GciR@postini.com; Thu, 12 Nov 2009 05:36:49 PST
Received: from p-emfe01-sac.jnpr.net (66.129.254.72) by P-EMHUB01-HQ.jnpr.net (172.24.192.35) with Microsoft SMTP Server id 8.1.375.2; Thu, 12 Nov 2009 05:32:59 -0800
Received: from p-emlb01-sac.jnpr.net ([66.129.254.46]) by p-emfe01-sac.jnpr.net with Microsoft SMTPSVC(6.0.3790.3959); Thu, 12 Nov 2009 05:32:59 -0800
Received: from emailsmtp55.jnpr.net ([172.24.18.132]) by p-emlb01-sac.jnpr.net with Microsoft SMTPSVC(6.0.3790.3959); Thu, 12 Nov 2009 05:32:59 -0800
Received: from magenta.juniper.net ([172.17.27.123]) by emailsmtp55.jnpr.net with Microsoft SMTPSVC(6.0.3790.3959); Thu, 12 Nov 2009 05:32:57 -0800
Received: from juniper.net (sapphire.juniper.net [172.17.28.108])	by magenta.juniper.net (8.11.3/8.11.3) with ESMTP id nACDWuj03440; Thu, 12 Nov 2009 05:32:57 -0800 (PST)	(envelope-from yakov@juniper.net)
Message-ID: <200911121332.nACDWuj03440@magenta.juniper.net>
To: "Thomas Morin" <thomas.morin@orange-ftgroup.com>
Subject: Re: draft-ietf-l3vpn-mvpn-considerations-05 
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <35571.1258032776.1@juniper.net>
Date: Thu, 12 Nov 2009 05:32:56 -0800
From: Yakov Rekhter <yakov@juniper.net>
X-OriginalArrivalTime: 12 Nov 2009 13:32:57.0404 (UTC) FILETIME=[A55FAFC0:01CA639C]
Cc: l3vpn@ietf.org
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <l3vpn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/l3vpn>, <mailto:l3vpn-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/l3vpn>
List-Post: <mailto:l3vpn@ietf.org>
List-Help: <mailto:l3vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/l3vpn>, <mailto:l3vpn-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 12 Nov 2009 13:36:20 -0000

Thomas,
 
> Hello working group,
> 
> Feedback is highly welcome on the last revision of 
> draft-ietf-l3vpn-mvpn-considerations, especially on the non editorial 
> changes such as the now fully revised Appendix A that compares the 
> behavior of the different C-multicast routing approaches with reference 
> to mVPN SSM/ASM routing scalability.
> 
> The changes made in this revision and the previous one are described in 
> the slides presented this afternoon ( 
> http://tools.ietf.org/agenda/76/slides/l3vpn-0.pdf ).
> 
> Thank you,
> 
> -Thomas

I reviewed the latest (05) revision of
draft-ietf-l3vpn-mvpn-considerations, paying special attention to
the non editorial changes in Appendix A. The latest text in Appendix A
provides a detailed and accurate analysis of using both PIM and
BGP for exchanging C-multicast routes. It covers both PIM-SM in
SSM mode and PIM-SM in ASM mode scenarios. Moreover, as part of
the analysis of using BGP for exchanging C-multicast routes, the
latest text correctly reflects interaction between Route Target
Constrains and the propagation of C-multicast routes.

It is time to move this draft to the IESG.

Yakov.

From rfc-editor@rfc-editor.org  Mon Nov 23 16:35:55 2009
Return-Path: <rfc-editor@rfc-editor.org>
X-Original-To: l3vpn@core3.amsl.com
Delivered-To: l3vpn@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 712353A6AFF; Mon, 23 Nov 2009 16:35:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.13
X-Spam-Level: 
X-Spam-Status: No, score=-17.13 tagged_above=-999 required=5 tests=[AWL=-0.131, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, USER_IN_DEF_WHITELIST=-15]
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 L8Uu3+pG6SxG; Mon, 23 Nov 2009 16:35:54 -0800 (PST)
Received: from bosco.isi.edu (bosco.isi.edu [128.9.168.207]) by core3.amsl.com (Postfix) with ESMTP id AC5983A6AE6; Mon, 23 Nov 2009 16:35:54 -0800 (PST)
Received: by bosco.isi.edu (Postfix, from userid 70) id 4E61E372B7E; Mon, 23 Nov 2009 16:30:41 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 5701 on IPv6 Address Specific BGP Extended Community Attribute
From: rfc-editor@rfc-editor.org
Message-Id: <20091124003041.4E61E372B7E@bosco.isi.edu>
Date: Mon, 23 Nov 2009 16:30:41 -0800 (PST)
Cc: l3vpn@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <l3vpn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/l3vpn>, <mailto:l3vpn-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/l3vpn>
List-Post: <mailto:l3vpn@ietf.org>
List-Help: <mailto:l3vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/l3vpn>, <mailto:l3vpn-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 24 Nov 2009 00:35:55 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 5701

        Title:      IPv6 Address Specific BGP Extended 
                    Community Attribute 
        Author:     Y. Rekhter
        Status:     Standards Track
        Date:       November 2009
        Mailbox:    yakov@juniper.net
        Pages:      5
        Characters: 9626
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-l3vpn-v6-ext-communities-02.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5701.txt

Current specifications of BGP Extended Communities (RFC 4360)
support the IPv4 Address Specific Extended Community, but do not
support an IPv6 Address Specific Extended Community.  The lack of an IPv6 Address Specific Extended Community may be a problem when an application
uses the IPv4 Address Specific Extended Community, and one wants to use
this application in a pure IPv6 environment.  This document defines
a new BGP attribute, the 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.  [STANDARDS
TRACK]

This document is a product of the Layer 3 Virtual Private Networks Working Group of the IETF.

This is now a Proposed Standard Protocol.

STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Internet
Official Protocol Standards (STD 1) for the standardization state and
status of this protocol.  Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
USC/Information Sciences Institute



From root@core3.amsl.com  Mon Nov 23 20:45:03 2009
Return-Path: <root@core3.amsl.com>
X-Original-To: l3vpn@ietf.org
Delivered-To: l3vpn@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0) id 08E193A6B32; Mon, 23 Nov 2009 20:45:01 -0800 (PST)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Subject: I-D Action:draft-ietf-l3vpn-ospfv3-pece-04.txt 
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20091124044503.08E193A6B32@core3.amsl.com>
Date: Mon, 23 Nov 2009 20:45:01 -0800 (PST)
Cc: l3vpn@ietf.org
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <l3vpn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/l3vpn>, <mailto:l3vpn-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/l3vpn>
List-Post: <mailto:l3vpn@ietf.org>
List-Help: <mailto:l3vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/l3vpn>, <mailto:l3vpn-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 24 Nov 2009 04:45:03 -0000

--NextPart

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           : OSPFv3 as a PE-CE routing protocol
	Author(s)       : P. Pillay-Esnault, et al.
	Filename        : draft-ietf-l3vpn-ospfv3-pece-04.txt
	Pages           : 21
	Date            : 2009-11-23

Many Service Providers (SPs) offer Virtual Private Network (VPN)
services to their customers using a technique in which Customer Edge
(CE) routers are routing peers of Provider Edge (PE) routers.  The
Border Gateway Protocol (BGP) is used to distribute the customer's
routes across the provider's IP backbone network, and Multiprotocol
Label Switching (MPLS) is used to tunnel customer packets across the
provider's backbone.  This is known as a "BGP/MPLS IP VPN".
Originally only IPv4 was supported and it was later extended to
support IPv6 VPNs as well.  Extensions were later added for the
support of the Open Shortest Path First protocol version 2 (OSPFv2)
as a PE-CE routing protocol for the IPv4 VPNs.  This document extends
those specifications to support OSPF version 3 (OSPFv3) as a PE-CE
routing protocol.  The OSPFv3 PE-CE functionality is identical to
that of OSPFv2 except for the differences described in this document.

Status of This Memo

This Internet-Draft is submitted to IETF in full conformance with the
provisions of BCP 78 and BCP 79.

Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups.  Note that
other groups may also distribute working documents as Internet-
Drafts.

Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time.  It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."

The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt.

The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html.

This Internet-Draft will expire on May 28, 2010.

Copyright Notice

Copyright (c) 2009 IETF Trust and the persons identified as the
document authors.  All rights reserved.

This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document.  Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document.  Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the BSD License.

This document may contain material from IETF Documents or IETF
Contributions published or made publicly available before November
10, 2008.  The person(s) controlling the copyright in some of this
material may not have granted the IETF Trust the right to allow
modifications of such material outside the IETF Standards Process.
Without obtaining an adequate license from the person(s) controlling
the copyright in such materials, this document may not be modified
outside the IETF Standards Process, and derivative works of it may
not be created outside the IETF Standards Process, except to format
it for publication as an RFC or to translate it into languages other
than English.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-l3vpn-ospfv3-pece-04.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.

--NextPart
Content-Type: Message/External-body;
	name="draft-ietf-l3vpn-ospfv3-pece-04.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2009-11-23204402.I-D@ietf.org>


--NextPart--

From daniel@olddog.co.uk  Tue Nov 24 01:24:40 2009
Return-Path: <daniel@olddog.co.uk>
X-Original-To: l3vpn@core3.amsl.com
Delivered-To: l3vpn@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 264483A68A6 for <l3vpn@core3.amsl.com>; Tue, 24 Nov 2009 01:24:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.256
X-Spam-Level: 
X-Spam-Status: No, score=0.256 tagged_above=-999 required=5 tests=[AWL=-0.346,  BAYES_50=0.001, 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 66VCOJHckKwj for <l3vpn@core3.amsl.com>; Tue, 24 Nov 2009 01:24:39 -0800 (PST)
Received: from asmtp3.iomartmail.com (asmtp3.iomartmail.com [62.128.193.159]) by core3.amsl.com (Postfix) with ESMTP id 33BDA3A6810 for <l3vpn@ietf.org>; Tue, 24 Nov 2009 01:24:39 -0800 (PST)
Received: from asmtp3.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp3.iomartmail.com (8.13.8/8.13.8) with ESMTP id nAO9ODV0020575 for <l3vpn@ietf.org>; Tue, 24 Nov 2009 09:24:19 GMT
Received: from Serenity (88-97-23-122.dsl.zen.co.uk [88.97.23.122]) (authenticated bits=0) by asmtp3.iomartmail.com (8.13.8/8.13.8) with ESMTP id nAO9OCUc020550 for <l3vpn@ietf.org>; Tue, 24 Nov 2009 09:24:12 GMT
From: "Daniel King" <daniel@olddog.co.uk>
To: <l3vpn@ietf.org>
Subject: Draft L3VPN Minutes for IETF 76
Date: Tue, 24 Nov 2009 09:24:12 -0000
Message-ID: <001a01ca6ce7$e2d8baa0$a88a2fe0$@co.uk>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_001B_01CA6CE7.E2D8BAA0"
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Acps5+JMPF7XOsSaTeWA8G2vbv749Q==
Content-Language: en-gb
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <l3vpn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/l3vpn>, <mailto:l3vpn-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/l3vpn>
List-Post: <mailto:l3vpn@ietf.org>
List-Help: <mailto:l3vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/l3vpn>, <mailto:l3vpn-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 24 Nov 2009 09:24:40 -0000

This is a multi-part message in MIME format.

------=_NextPart_000_001B_01CA6CE7.E2D8BAA0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Hello all, 

 

Please find the draft l3vpn minutes for our IETF 76 session:

 

http://www.ietf.org/proceedings/09nov/minutes/l3vpn.htm

 

If you have any comments or requests please email the chairs and myself.
Please let us have any comments by  Tuesday, December 8th, 2009.  

 

Br, Dan

 


------=_NextPart_000_001B_01CA6CE7.E2D8BAA0
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 12 (filtered medium)">
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;}
@page Section1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.Section1
	{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

<body lang=3DEN-GB link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal>Hello all, <o:p></o:p></p>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<p class=3DMsoNormal>Please find the draft l3vpn minutes for our IETF 76 =
session:<o:p></o:p></p>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<p class=3DMsoNormal><a
href=3D"http://www.ietf.org/proceedings/09nov/minutes/l3vpn.htm">http://w=
ww.ietf.org/proceedings/09nov/minutes/l3vpn.htm</a><o:p></o:p></p>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<p class=3DMsoNormal>If you have any comments or requests please email =
the chairs
and myself. Please let us have any comments by &nbsp;Tuesday, December =
8<sup>th</sup>,
2009. &nbsp;<o:p></o:p></p>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<p class=3DMsoNormal>Br, Dan<o:p></o:p></p>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

</div>

</body>

</html>

------=_NextPart_000_001B_01CA6CE7.E2D8BAA0--


From root@core3.amsl.com  Mon Nov 30 09:00:01 2009
Return-Path: <root@core3.amsl.com>
X-Original-To: l3vpn@ietf.org
Delivered-To: l3vpn@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0) id 9DBB63A6AB0; Mon, 30 Nov 2009 09:00:01 -0800 (PST)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Subject: I-D Action:draft-ietf-l3vpn-2547bis-mcast-09.txt 
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20091130170001.9DBB63A6AB0@core3.amsl.com>
Date: Mon, 30 Nov 2009 09:00:01 -0800 (PST)
Cc: l3vpn@ietf.org
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <l3vpn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/l3vpn>, <mailto:l3vpn-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/l3vpn>
List-Post: <mailto:l3vpn@ietf.org>
List-Help: <mailto:l3vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/l3vpn>, <mailto:l3vpn-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 30 Nov 2009 17:00:01 -0000

--NextPart

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           : Multicast in MPLS/BGP IP VPNs
	Author(s)       : R. Aggarwal, et al.
	Filename        : draft-ietf-l3vpn-2547bis-mcast-09.txt
	Pages           : 89
	Date            : 2009-11-30

In order for IP multicast traffic within a BGP/MPLS IP VPN (Virtual
Private Network) to travel from one VPN site to another, special
protocols and procedures must be implemented by the VPN Service
Provider.  These protocols and procedures are specified in this
document.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-l3vpn-2547bis-mcast-09.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.

--NextPart
Content-Type: Message/External-body;
	name="draft-ietf-l3vpn-2547bis-mcast-09.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2009-11-30085140.I-D@ietf.org>


--NextPart--
