
From wwwrun@core3.amsl.com  Thu Oct  1 09:53:23 2009
Return-Path: <wwwrun@core3.amsl.com>
X-Original-To: l3vpn@ietf.org
Delivered-To: l3vpn@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 30) id 5083628C147; Thu,  1 Oct 2009 09:53:23 -0700 (PDT)
X-idtracker: yes
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Subject: Protocol Action: 'IPv6 Address Specific BGP Extended Communities Attribute' to Proposed Standard
Message-Id: <20091001165323.5083628C147@core3.amsl.com>
Date: Thu,  1 Oct 2009 09:53:23 -0700 (PDT)
Cc: l3vpn chair <l3vpn-chairs@tools.ietf.org>, Internet Architecture Board <iab@iab.org>, l3vpn mailing list <l3vpn@ietf.org>, RFC Editor <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: Thu, 01 Oct 2009 16:53:23 -0000

The IESG has approved the following document:

- 'IPv6 Address Specific BGP Extended Communities Attribute '
   <draft-ietf-l3vpn-v6-ext-communities-02.txt> as a Proposed Standard


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

The IESG contact persons are Ross Callon and Adrian Farrel.

A URL of this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-l3vpn-v6-ext-communities-02.txt

Technical Summary

   Current specifications of BGP Extended Communities [RFC4360] 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.

Working Group Summary

   No dissent reported (see PROTO writeup by Danny McPherson in the
   I.D. tracker). This was last called in both L3VPN and IDR working
   groups.  

Document Quality

   The equivalent capability for IPv4 is implemented and widely
   deployed. This is a quite straightforward extension of this 
   same capability for use in IPv6 networks.

Personnel

   Danny McPherson is the Document Shepherd for this document. Ross
   Callon is the Responsible Area Director.

RFC Editor Note

   Section 1, paragraph 1, spelling "Addres" should be "Address". 

   Please replace the existing security considerations section with
   the following:

     4. Security Considerations

     This document does not add new security issues. All the security 
     considerations for BGP Extended Communities apply here. At the
     time that this document was written there were significant efforts 
     underway to improve the security properties of BGP. For examples of 
     documents that have been produced up to this time of publication, 
     see [RFC4593] and [SIDR]. 

     There is a potential serious issue if a malformed optional 
     transitive attribute is received. This issue and the steps to
     avoid it are discussed in [OPT_TRANS]. 

   Please add to section 7 (Non-Normative references): 

     [OPT_TRANS] Scudder, Chen, "Error Handling for Optional Transitive 
                 BGP Attributes", work in progress, 
                 draft-ietf-idr-optional-transitive, April 2009. 
 
     [RFC4593]   Barbir, Murphy, Yang, "Generic Threats to Routing 
                 Protocols", RFC4593, October 2006. 
 
     [SIDR]      Lepinski, Kent, "An Infrastructure to Support Secure
                 Internet Routing", work in progress, 
                 draft-ietf-sidr-arch-08.txt, July, 2009.


From danny@tcb.net  Fri Oct  2 11:04:42 2009
Return-Path: <danny@tcb.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 0C6D83A687A for <l3vpn@core3.amsl.com>; Fri,  2 Oct 2009 11:04:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.117
X-Spam-Level: 
X-Spam-Status: No, score=-1.117 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, DNS_FROM_RFC_BOGUSMX=1.482]
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 m+p0zAWY9au1 for <l3vpn@core3.amsl.com>; Fri,  2 Oct 2009 11:04:41 -0700 (PDT)
Received: from sa.ma.arbor.net (bedford.lex.arbor.net [204.118.128.2]) by core3.amsl.com (Postfix) with ESMTP id 55B373A6811 for <l3vpn@ietf.org>; Fri,  2 Oct 2009 11:04:41 -0700 (PDT)
Received: from localhost (sa.ma.arbor.net [10.2.0.66]) by sa.ma.arbor.net (Postfix) with ESMTP id B0BB29070D for <l3vpn@ietf.org>; Fri,  2 Oct 2009 14:06:09 -0400 (EDT)
X-Virus-Scanned: amavisd-new at arbor.net
Received: from 10-1-15-25.aa.arbor.net (10-1-15-25.aa.arbor.net [10.1.15.25]) by sa.ma.arbor.net (Postfix) with ESMTP id 65B35906F2 for <l3vpn@ietf.org>; Fri,  2 Oct 2009 14:06:07 -0400 (EDT)
From: Danny McPherson <danny@tcb.net>
Content-Type: text/plain; charset=windows-1252; format=flowed; delsp=yes
Content-Transfer-Encoding: quoted-printable
Subject: Hiroshima Important Dates
Date: Fri, 2 Oct 2009 12:06:06 -0600
Message-Id: <4EFD1FE2-44E0-49B1-B8D1-A2A1232E22D7@tcb.net>
To: l3vpn@ietf.org
Mime-Version: 1.0 (Apple Message framework v1076)
X-Mailer: Apple Mail (2.1076)
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: Fri, 02 Oct 2009 18:04:42 -0000

FYI on some important dates for the upcoming meeting.

	=95 2009-10-02 (Friday): Preliminary agenda published for =
comment.
	=95 2009-10-09 (Friday): Cutoff date for requests to reschedule =
Working =20
Group and BOF meetings 17:00 PDT (24:00 UTC/GMT).
	=95 2009-10-12 (Monday): Working Group Chair approval for =
initial =20
document (Version -00) submissions appreciated by 17:00 PDT (24:00 UTC/=20=

GMT).
	=95 2009-10-16 (Friday): Final agenda to be published.
	=95 2009-10-19 (Monday): Internet Draft Cut-off for initial =
document =20
(-00) submission by 17:00 PDT (24:00 UTC/GMT), upload using IETF ID =20
Submission Tool.
	=95 2009-10-26 (Monday): Internet Draft final submission cut-off =
by =20
17:00 PDT (24:00 UTC/GMT), upload usingIETF ID Submission Tool.
	=95 2009-10-28 (Wednesday): Draft Working Group agendas due by =
17:00 =20
PDT (24:00 UTC/GMT), upload usingIETF Meeting Materials Management Tool.
	=95 2009-10-30 (Friday): Early Bird registration and payment =
cut-off at =20
17:00 PDT (24:00 UTC/GMT).
	=95 2009-11-02 (Monday): Revised Working Group agendas due by =
17:00 PST =20
(01:00 Tuesday, November 3 UTC/GMT), upload using IETF Meeting =20
Materials Management Tool.
	=95 2009-11-02 (Monday): Registration cancellation cut-off at =
17:00 PST =20
(01:00 Tuesday, November 3 UTC/GMT).
	=95 2009-11-06 (Friday): Final Pre-Registration and Pre-Payment =
cut-off =20
at 17:00 local Hiroshima time (00:00 PST, 08:00 UTC/GMT).
	=95 2009-11-08 - 2009-11-13: 76th IETF Meeting in Hiroshima, JP.

The full list is available here:

http://www.ietf.org/meeting/cutoff-dates.html

-danny=

From wwwrun@core3.amsl.com  Tue Oct  6 08:47:03 2009
Return-Path: <wwwrun@core3.amsl.com>
X-Original-To: l3vpn@ietf.org
Delivered-To: l3vpn@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 30) id 666E23A6A05; Tue,  6 Oct 2009 08:47:03 -0700 (PDT)
X-idtracker: yes
To: IETF-Announce <ietf-announce@ietf.org> 
From: The IESG <iesg-secretary@ietf.org>
Subject: Last Call: draft-ietf-l3vpn-e2e-rsvp-te-reqts (Requirements for supporting Customer RSVP and RSVP-TE over a BGP/MPLS IP-VPN) to Informational RFC
Message-Id: <20091006154703.666E23A6A05@core3.amsl.com>
Date: Tue,  6 Oct 2009 08:47:03 -0700 (PDT)
Cc: l3vpn@ietf.org
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: ietf@ietf.org
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, 06 Oct 2009 15:47:03 -0000

The IESG has received a request from the Layer 3 Virtual Private Networks 
WG (l3vpn) to consider the following document:

- 'Requirements for supporting Customer RSVP and RSVP-TE over a BGP/MPLS 
   IP-VPN '
   <draft-ietf-l3vpn-e2e-rsvp-te-reqts-04.txt> as an Informational RFC

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-10-20. 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-e2e-rsvp-te-reqts-04.txt


IESG discussion can be tracked via
https://datatracker.ietf.org/public/pidtracker.cgi?command=view_id&dTag=17192&rfc_flag=0


From rcallon@juniper.net  Wed Oct  7 11:51:42 2009
Return-Path: <rcallon@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 555CB3A6976 for <l3vpn@core3.amsl.com>; Wed,  7 Oct 2009 11:51:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.153
X-Spam-Level: 
X-Spam-Status: No, score=-6.153 tagged_above=-999 required=5 tests=[AWL=-0.155, BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 FohNGaGUeJWy for <l3vpn@core3.amsl.com>; Wed,  7 Oct 2009 11:51:41 -0700 (PDT)
Received: from exprod7og111.obsmtp.com (exprod7og111.obsmtp.com [64.18.2.175]) by core3.amsl.com (Postfix) with ESMTP id AD9E13A685D for <l3vpn@ietf.org>; Wed,  7 Oct 2009 11:51:39 -0700 (PDT)
Received: from source ([66.129.224.36]) (using TLSv1) by exprod7ob111.postini.com ([64.18.6.12]) with SMTP ID DSNKSszjnGMu+1inqhA3x4LGNJlEvydOPqEU@postini.com; Wed, 07 Oct 2009 11:53:22 PDT
Received: from p-emfe01-wf.jnpr.net (172.28.145.24) by P-EMHUB03-HQ.jnpr.net (172.24.192.37) with Microsoft SMTP Server (TLS) id 8.1.375.2; Wed, 7 Oct 2009 11:51:23 -0700
Received: from EMBX01-WF.jnpr.net ([fe80::1914:3299:33d9:e43b]) by p-emfe01-wf.jnpr.net ([fe80::d0d1:653d:5b91:a123%11]) with mapi; Wed, 7 Oct 2009 14:51:21 -0400
From: Ross Callon <rcallon@juniper.net>
To: "l3vpn@ietf.org" <l3vpn@ietf.org>
Date: Wed, 7 Oct 2009 14:51:20 -0400
Subject: Change in L3VPN Co-chair
Thread-Topic: Change in L3VPN Co-chair
Thread-Index: AcpHfyhFcutt89+pR0uPMmU79Bbz4A==
Message-ID: <DF7F294AF4153D498141CBEFADB177049A0AFCEE32@EMBX01-WF.jnpr.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_DF7F294AF4153D498141CBEFADB177049A0AFCEE32EMBX01WFjnprn_"
MIME-Version: 1.0
Cc: "benjamin.niven-jenkins@bt.com" <benjamin.niven-jenkins@bt.com>, "tme@multicasttech.com" <tme@multicasttech.com>, "adrian.farrel@huawei.com" <adrian.farrel@huawei.com>, Danny McPherson <danny@tcb.net>, Callon <rcallon@juniper.net>, Ross
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: Wed, 07 Oct 2009 18:51:42 -0000

--_000_DF7F294AF4153D498141CBEFADB177049A0AFCEE32EMBX01WFjnprn_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Danny McPherson has asked to step down as co-chair of the L3VPN working gro=
up. I am very pleased to announce that Ben Niven-Jenkins has agreed to serv=
e as co-chair (along with Marshall Eubanks, who will continue as co-chair).

It is not unusual for IETF WG co-chairs to also be document authors. When t=
his happens, the author/chair needs to recuse himself from the role as co-c=
hair for the consideration of that one document, and allow the other chair(=
s) to judge WG consensus and otherwise serve as chair for that document. Si=
nce Ben is co-author of the considerations draft, Danny has agreed to stay =
on as co-chair for the purpose of progressing this one document and to cont=
inue the role that Danny has already been filling of attempting to help res=
olve all remaining comments on the considerations draft.

While Danny has only been co-chair since the Dublin IETF (July 2008), he ha=
s nonetheless played a major role over the past 15 months in helping the L3=
VPN working group make important progress in this time period. I would like=
 to thank Danny for his considerable help in this area (as well as for agre=
eing to let me twist his arm into staying on while the considerations draft=
 is progressed).

Thanks, Ross


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

<html xmlns:o=3D"urn:schemas-microsoft-com:office:office" xmlns:w=3D"urn:sc=
hemas-microsoft-com:office:word" xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<style>
<!--
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:Arial;
	color:windowtext;}
@page Section1
	{size:8.5in 11.0in;
	margin:.8in .8in 45.35pt .8in;}
div.Section1
	{page:Section1;}
-->
</style>

</head>

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

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'>Danny McPherson has asked to step down as co-chair of th=
e
L3VPN working group. I am very pleased to announce that Ben Niven-Jenkins h=
as
agreed to serve as co-chair (along with Marshall Eubanks, who will continue=
 as
co-chair). <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'>It is not unusual for IETF WG co-chairs to also be docum=
ent
authors. When this happens, the author/chair needs to recuse himself from t=
he
role as co-chair for the consideration of that one document, and allow the
other chair(s) to judge WG consensus and otherwise serve as chair for that
document. Since Ben is co-author of the considerations draft, Danny has agr=
eed
to stay on as co-chair for the purpose of progressing this one document and=
 to
continue the role that Danny has already been filling of attempting to help
resolve all remaining comments on the considerations draft. <o:p></o:p></sp=
an></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'>While Danny has only been co-chair since the Dublin IETF
(July 2008), he has nonetheless played a major role over the past 15 months=
 in
helping the L3VPN working group make important progress in this time period=
. I
would like to thank Danny for his considerable help in this area (as well a=
s
for agreeing to let me twist his arm into staying on while the consideratio=
ns
draft is progressed). <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'>Thanks, Ross<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

</div>

</body>

</html>

--_000_DF7F294AF4153D498141CBEFADB177049A0AFCEE32EMBX01WFjnprn_--

From wwwrun@core3.amsl.com  Fri Oct  9 06:29:49 2009
Return-Path: <wwwrun@core3.amsl.com>
X-Original-To: l3vpn@ietf.org
Delivered-To: l3vpn@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 30) id 7C05028C11B; Fri,  9 Oct 2009 06:29:49 -0700 (PDT)
X-idtracker: yes
To: IETF-Announce <ietf-announce@ietf.org> 
From: The IESG <iesg-secretary@ietf.org>
Subject: Last Call: draft-ietf-l3vpn-ospfv3-pece (OSPFv3 as a PE-CE routing protocol) to Proposed Standard
Message-Id: <20091009132949.7C05028C11B@core3.amsl.com>
Date: Fri,  9 Oct 2009 06:29:49 -0700 (PDT)
Cc: l3vpn@ietf.org
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: ietf@ietf.org
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: Fri, 09 Oct 2009 13:29:49 -0000

The IESG has received a request from the Layer 3 Virtual Private Networks 
WG (l3vpn) to consider the following document:

- 'OSPFv3 as a PE-CE routing protocol '
   <draft-ietf-l3vpn-ospfv3-pece-03.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-10-23. 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.

Please note that draft-ietf-l3vpn-ospfv3-pece-03.txt contains a normative
reference to RFC2547, which is an informational RFC and is therefore 
currently a downref. This reference will be moved to be an informative 
reference prior to publication as an RFC. 

The file can be obtained via
http://www.ietf.org/internet-drafts/draft-ietf-l3vpn-ospfv3-pece-03.txt


IESG discussion can be tracked via
https://datatracker.ietf.org/public/pidtracker.cgi?command=view_id&dTag=17761&rfc_flag=0


From julien.meuric@orange-ftgroup.com  Wed Oct  7 06:28:04 2009
Return-Path: <julien.meuric@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 BBA153A6AA9; Wed,  7 Oct 2009 06:28:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.815
X-Spam-Level: 
X-Spam-Status: No, score=-1.815 tagged_above=-999 required=5 tests=[AWL=0.434,  BAYES_00=-2.599, 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 R8vRDq8K5Gbl; Wed,  7 Oct 2009 06:28:04 -0700 (PDT)
Received: from r-mail2.rd.francetelecom.com (r-mail2.rd.francetelecom.com [217.108.152.42]) by core3.amsl.com (Postfix) with ESMTP id 1AC773A6AA1; Wed,  7 Oct 2009 06:28:02 -0700 (PDT)
Received: from ftrdmel1.rd.francetelecom.fr ([10.192.128.40]) by ftrdsmtp2.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.3959);  Wed, 7 Oct 2009 15:29:42 +0200
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: Last Call: draft-ietf-l3vpn-e2e-rsvp-te-reqts (Requirements forsupporting Customer RSVP and RSVP-TE over a BGP/MPLS IP-VPN) toInformational RFC
Date: Wed, 7 Oct 2009 15:29:41 +0200
Message-ID: <D109C8C97C15294495117745780657AE0C01B20A@ftrdmel1>
In-Reply-To: <20091006154703.666E23A6A05@core3.amsl.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Last Call: draft-ietf-l3vpn-e2e-rsvp-te-reqts (Requirements forsupporting Customer RSVP and RSVP-TE over a BGP/MPLS IP-VPN) toInformational RFC
Thread-Index: AcpGnItsrkzElNoLRzShR1TLhDzOUQAr+f2g
References: <20091006154703.666E23A6A05@core3.amsl.com>
From: <julien.meuric@orange-ftgroup.com>
To: <ietf@ietf.org>
X-OriginalArrivalTime: 07 Oct 2009 13:29:42.0454 (UTC) FILETIME=[3A4DAD60:01CA4752]
X-Mailman-Approved-At: Mon, 12 Oct 2009 15:21:24 -0700
Cc: pce@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: Wed, 07 Oct 2009 13:28:04 -0000

Hi all.

Just a few minor comments:
- The I-D refers to the "EXP" field several times (pages 11, 13, 15,
17...) whereas it is now named "Traffic Class", as per RFC 5462.
- Section 5.8 tackles PCE, thus putting some requirements on the PCE WG:
do we expect that they are endorsed tacitly? In this specific case, it
is only specified as "SHOULD", so impact is limited, but what is the
status of this kind of draft defining requirements over multiple WGs? In
case it be superset by draft-ietf-pce-vpn-req, a reference would be
welcome.

Thanks,

Julien


-----Original Message-----
From: ietf-announce-bounces@ietf.org
[mailto:ietf-announce-bounces@ietf.org] On Behalf Of The IESG

The IESG has received a request from the Layer 3 Virtual Private
Networks=20
WG (l3vpn) to consider the following document:

- 'Requirements for supporting Customer RSVP and RSVP-TE over a BGP/MPLS

   IP-VPN '
   <draft-ietf-l3vpn-e2e-rsvp-te-reqts-04.txt> as an Informational RFC

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-10-20. Exceptionally,=20
comments may be sent to iesg@ietf.org instead. In either case, please=20
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-e2e-rsvp-te-reqts-0
4.txt


IESG discussion can be tracked via
https://datatracker.ietf.org/public/pidtracker.cgi?command=3Dview_id&dTag=
=3D
17192&rfc_flag=3D0

_______________________________________________
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/ietf-announce

From RBhatt@ixiacom.com  Mon Oct 12 01:42:26 2009
Return-Path: <RBhatt@ixiacom.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 C762E3A67E6 for <l3vpn@core3.amsl.com>; Mon, 12 Oct 2009 01:42:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.91
X-Spam-Level: *
X-Spam-Status: No, score=1.91 tagged_above=-999 required=5 tests=[BAYES_50=0.001, HTML_MESSAGE=0.001, RCVD_ILLEGAL_IP=1.908]
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 FYFNBUZZMfiE for <l3vpn@core3.amsl.com>; Mon, 12 Oct 2009 01:42:23 -0700 (PDT)
Received: from ixqw-mail-out.ixiacom.com (ixqw-mail-out.ixiacom.com [66.77.12.12]) by core3.amsl.com (Postfix) with ESMTP id C92483A677D for <l3vpn@ietf.org>; Mon, 12 Oct 2009 01:42:23 -0700 (PDT)
Received: from ixcaexch07.ixiacom.com ([fe80:0000:0000:0000:e021:fcf5:238.143.231.20]) by ixqw-hc1.ixiacom.com ([10.210.5.15]) with mapi; Mon, 12 Oct 2009 01:42:23 -0700
From: Rakesh Bhatt <RBhatt@ixiacom.com>
To: "l3vpn@ietf.org" <l3vpn@ietf.org>
Date: Mon, 12 Oct 2009 01:42:20 -0700
Subject: draft-ietf-l3vpn-2547bis-mcast-07.txt
Thread-Topic: draft-ietf-l3vpn-2547bis-mcast-07.txt
Thread-Index: AcpLF+lbbkO0P+CrSL2y8I4ncA1dnQ==
Message-ID: <716209EC190CA740BA799AC4ACCBFB5D15E7D09FCF@IXCAEXCH07.ixiacom.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_716209EC190CA740BA799AC4ACCBFB5D15E7D09FCFIXCAEXCH07ixi_"
MIME-Version: 1.0
X-Mailman-Approved-At: Mon, 12 Oct 2009 15:21:24 -0700
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, 12 Oct 2009 09:44:47 -0000

--_000_716209EC190CA740BA799AC4ACCBFB5D15E7D09FCFIXCAEXCH07ixi_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi Team

In section 6.4.1 ,

If an RSVP-TE P2MP LSP is being used to carry a set of C-flows
   traveling along a bidirectional C-Tree, using the procedures of
   section 11.2, the head end MUST include the PE Distinguisher Labels
   attribute in its I-PMSI Intra-AS A-D route or S-PMSI A-D route, and
   MUST provide an upstream-assigned label for each PE that it has
   selected as the upstream PE for the C-tree's RPA ("Rendezvous Point
   Address").  See section 11.2 for details.

Is this always necessary to put PE Distinguisher Labels  Attribute ?
If we don't have Inter AS then do we need to add this attribute ?

Thanks
Rakesh Bhatt

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

<html xmlns:o=3D"urn:schemas-microsoft-com:office:office" xmlns:w=3D"urn:sc=
hemas-microsoft-com:office:word" xmlns:st1=3D"urn:schemas-microsoft-com:off=
ice:smarttags" xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<o:SmartTagType namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"State"/>
<o:SmartTagType namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"City"/>
<o:SmartTagType namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"place"/>
<!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:Arial;
	color:windowtext;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
-->
</style>

</head>

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

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'>Hi Team <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'>In section 6.4.1 ,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'>If an RSVP-TE P2MP LSP is being used to carry a set of
C-flows<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'>&nbsp;&nbsp; traveling along a bidirectional C-Tree, usi=
ng the
procedures of<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'>&nbsp;&nbsp; section 11.2, the head end MUST include the=
 PE
Distinguisher Labels<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'>&nbsp;&nbsp; attribute in its I-PMSI Intra-AS A-D route =
or S-PMSI A-D
route, and<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'>&nbsp;&nbsp; MUST provide an upstream-assigned label for=
 each PE that
it has<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'>&nbsp;&nbsp; selected as the upstream PE for the C-tree'=
s RPA
(&quot;Rendezvous Point<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'>&nbsp;&nbsp; Address&quot;).&nbsp; See section 11.2 for =
details.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'>Is this always necessary to put PE Distinguisher Labels =
&nbsp;Attribute
? <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'>If we don&#8217;t have <st1:place w:st=3D"on"><st1:City =
w:st=3D"on">Inter</st1:City>
 <st1:State w:st=3D"on">AS</st1:State></st1:place> then do we need to add t=
his
attribute ?<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'>Thanks<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'>Rakesh Bhatt<o:p></o:p></span></font></p>

</div>

</body>

</html>

--_000_716209EC190CA740BA799AC4ACCBFB5D15E7D09FCFIXCAEXCH07ixi_--

From yakov@juniper.net  Tue Oct 13 06:51:18 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 8D5BC28C2EB for <l3vpn@core3.amsl.com>; Tue, 13 Oct 2009 06:51:18 -0700 (PDT)
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 2KqXpjWjTOKy for <l3vpn@core3.amsl.com>; Tue, 13 Oct 2009 06:51:17 -0700 (PDT)
Received: from chip3og55.obsmtp.com (chip3og55.obsmtp.com [64.18.14.175]) by core3.amsl.com (Postfix) with ESMTP id 99A2028C0D9 for <l3vpn@ietf.org>; Tue, 13 Oct 2009 06:51:17 -0700 (PDT)
Received: from source ([66.129.224.36]) (using TLSv1) by chip3ob55.postini.com ([64.18.6.12]) with SMTP ID DSNKStSF1gD24bPv0MTBZRUTMBFrfjnF51WK@postini.com; Tue, 13 Oct 2009 06:51:19 PDT
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; Tue, 13 Oct 2009 06:40:16 -0700
Received: from p-emlb01-sac.jnpr.net ([66.129.254.46]) by p-emfe01-sac.jnpr.net with Microsoft SMTPSVC(6.0.3790.3959); Tue, 13 Oct 2009 06:40:16 -0700
Received: from emailsmtp55.jnpr.net ([172.24.18.132]) by p-emlb01-sac.jnpr.net with Microsoft SMTPSVC(6.0.3790.3959); Tue, 13 Oct 2009 06:40:16 -0700
Received: from magenta.juniper.net ([172.17.27.123]) by emailsmtp55.jnpr.net with Microsoft SMTPSVC(6.0.3790.3959); Tue, 13 Oct 2009 06:40:15 -0700
Received: from juniper.net (sapphire.juniper.net [172.17.28.108])	by magenta.juniper.net (8.11.3/8.11.3) with ESMTP id n9DDe5j70403; Tue, 13 Oct 2009 06:40:15 -0700 (PDT)	(envelope-from yakov@juniper.net)
Message-ID: <200910131340.n9DDe5j70403@magenta.juniper.net>
To: Rakesh Bhatt <RBhatt@ixiacom.com>
Subject: Re: draft-ietf-l3vpn-2547bis-mcast-07.txt 
In-Reply-To: <716209EC190CA740BA799AC4ACCBFB5D15E7D09FCF@IXCAEXCH07.ixiacom.com>
References: <716209EC190CA740BA799AC4ACCBFB5D15E7D09FCF@IXCAEXCH07.ixiacom.com>
X-MH-In-Reply-To: Rakesh Bhatt <RBhatt@ixiacom.com> message dated "Mon, 12 Oct 2009 01:42:20 -0700."
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <9473.1255441205.1@juniper.net>
Date: Tue, 13 Oct 2009 06:40:05 -0700
From: Yakov Rekhter <yakov@juniper.net>
X-OriginalArrivalTime: 13 Oct 2009 13:40:15.0635 (UTC) FILETIME=[B22FEE30:01CA4C0A]
Cc: "l3vpn@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: Tue, 13 Oct 2009 13:51:18 -0000

Rakesh,

> Hi Team
> 
> In section 6.4.1 ,
> 
> If an RSVP-TE P2MP LSP is being used to carry a set of C-flows
>    traveling along a bidirectional C-Tree, using the procedures of
>    section 11.2, the head end MUST include the PE Distinguisher Labels
>    attribute in its I-PMSI Intra-AS A-D route or S-PMSI A-D route, and
>    MUST provide an upstream-assigned label for each PE that it has
>    selected as the upstream PE for the C-tree's RPA ("Rendezvous Point
>    Address").  See section 11.2 for details.
> 
> Is this always necessary to put PE Distinguisher Labels Attribute ?

*Under the conditions you quoted above* (P2MP LSP is being used to
carry a set of C-flows traveling along a bidirectional C-tree, using
the procedures of section 11.2) it is always necessary to carry PE
Distinguisher Labels Attribute. See 11.2.2 for more details on this
attribute, as well as on its usage.

Yakov.

From erosen@cisco.com  Mon Oct 19 07:44:49 2009
Return-Path: <erosen@cisco.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 2A06328C133; Mon, 19 Oct 2009 07:44:49 -0700 (PDT)
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 MkB4NO2cc8Dw; Mon, 19 Oct 2009 07:44:47 -0700 (PDT)
Received: from sj-iport-5.cisco.com (sj-iport-5.cisco.com [171.68.10.87]) by core3.amsl.com (Postfix) with ESMTP id 592F53A6928; Mon, 19 Oct 2009 07:44:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=erosen@cisco.com; l=12351; q=dns/txt; s=sjiport05001; t=1255963494; x=1257173094; h=from:sender:reply-to:subject:date:message-id:to:cc: mime-version:content-transfer-encoding:content-id: content-description:resent-date:resent-from:resent-sender: resent-to:resent-cc:resent-message-id:in-reply-to: references:list-id:list-help:list-unsubscribe: list-subscribe:list-post:list-owner:list-archive; z=From:=20Eric=20Rosen=20<erosen@cisco.com>|Reply-To:=20er osen@cisco.com|Subject:=20Re:=20Last=20Call:=20draft-ietf -l3vpn-2547bis-mcast=20(Multicast=20in=20MPLS/BGP=20IP=20 VPNs)=20to=20Proposed=20Standard=20|Date:=20Mon,=2019=20O ct=202009=2010:44:52=20-0400|Message-ID:=20<26940.1255963 492@erosen-linux>|To:=20Pekka=20Savola=20<pekkas@netcore. fi>|cc:=20ietf@ietf.org,=20l3vpn-chairs@tools.ietf.org, =20l3vpn@ietf.org,=0D=0A=20=20=20=20=20=20=20=20draft-iet f-l3vpn-2547bis-mcast@tools.ietf.org|In-reply-to:=20Your =20message=20of=20Wed,=2009=20Sep=202009=2010:34:37=20+03 00.=0D=0A=20=20=20=20=20=20=20=20=20=20=20=20=20<alpine.L RH.2.00.0909091031150.12395@netcore.fi>=20; bh=lr9V/j/LWybLszTriAVui3Hi248T0jLKeBNCNKJ8evI=; b=aNifYA34D5qy2f/vZ0bW0WJyytGnCRxpCd/JU/ZylFMbW7yP3oyuGxFA M6CSU9QjYxnCCsbWLVCoMCEQey4dww+7TWS5oJjlsedKj7nKqfIAbOow4 x8ezn/yBtkxWdvgBH9lHGO6W2+Z0bg0c5mq1EpvoLkG9zyTgaVjVIKR3m c=;
Authentication-Results: sj-iport-5.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-AV: E=Sophos;i="4.44,585,1249257600"; d="scan'208";a="99523250"
Received: from sj-core-2.cisco.com ([171.71.177.254]) by sj-iport-5.cisco.com with ESMTP; 19 Oct 2009 14:44:54 +0000
Received: from erosen-linux.cisco.com (erosen-linux.cisco.com [161.44.70.34]) by sj-core-2.cisco.com (8.13.8/8.14.3) with ESMTP id n9JEirrw017109;  Mon, 19 Oct 2009 14:44:54 GMT
Received: from erosen-linux (localhost.localdomain [127.0.0.1]) by erosen-linux.cisco.com (8.13.1/8.13.1) with ESMTP id n9JEiqeW026941;  Mon, 19 Oct 2009 10:44:53 -0400
To: Pekka Savola <pekkas@netcore.fi>
Subject: Re: Last Call: draft-ietf-l3vpn-2547bis-mcast (Multicast in MPLS/BGP IP VPNs) to Proposed Standard 
In-reply-to: Your message of Wed, 09 Sep 2009 10:34:37 +0300. <alpine.LRH.2.00.0909091031150.12395@netcore.fi> 
Date: Mon, 19 Oct 2009 10:44:52 -0400
Message-ID: <26940.1255963492@erosen-linux>
From: Eric Rosen <erosen@cisco.com>
Cc: l3vpn-chairs@tools.ietf.org, ietf@ietf.org, draft-ietf-l3vpn-2547bis-mcast@tools.ietf.org, l3vpn@ietf.org
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: erosen@cisco.com
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, 19 Oct 2009 14:44:49 -0000

Thank you for your review.  I will try to address your technical comments.
Some of your comments are not really technical objections, but criticisms of
the way the document is constructed, or of the scope of the document, or of
the approach adopted by the WG.  As the construction of the document is the
result of years of difficult negotiation and careful compromise, I will not
address those issues.  Also, I will not attempt to address the
"philosophical issues" having to do with what is and is not a proper use of
BGP.

Pekka> 1) IPv6 support.  The spec apparently aims to support both IPv4 and
Pekka>    IPv6 because it refers to both in a couple of places.  Yet, there
Pekka>    is at least one explicit place in the spec (S 7.4.2.2) that's not
Pekka>    compatible.

Pekka>    I suspect many of the BGP attributes used, possibly
Pekka>    also the MCAST-VPN BGP SAFI and others are not IPv6 compatible.

MCAST-VPN BGP SAFI is certainly IPv6 compatible; the details may be found in
draft-ietf-l3vpn-2547bis-mcast-bgp-08.text.  Section 4 of that draft
discusses the use of AFI 2 (IPv6) with the MCAST-VPN SAFI, and all talk of
"VPN-IP" routes in that document is meant to indicate either VPN-IPv4 or
VPN-IPv6. 

Pekka>    At the minimum, the status (intent) of the spec should be
Pekka>    clarified. Even better would be to improve and include the support
Pekka>    here.

In general, the procedures specified in the document will enable an IPv4 SP
backbone to support customer use of IPv6 multicast.  You are correct that
section 7.4.2.2 is incomplete in this respect.  

Pekka> 2) RP configuration in SP network.  It's not clear if SP network
Pekka>    needs to know how customer sites have configured their RPs (when
Pekka>    the customer provides the RP).  At least traditional PIM
Pekka>    signalling would require SP to know this.  But if auto-rp or BSR
Pekka>    is not used by the customer, how is this information learned and
Pekka>    maintained?  Would it require manual configuration?

A PE router does function as a PIM peer of a CE router, and hence needs some
way to get the group-to-RP mappings of the customer.  How this is done is
for the SP and the customer to determine.

Pekka> 5) Active source BGP messages.  This is a duplication of a similar
Pekka>    mechanism in MSDP (RFC3618) which has caused much grief in
Pekka>    Internet.  Does this meant that when a host does 'nmap -sU
Pekka>    224.0.0.0/4' at a VPN site, this will result in about 268 million
Pekka>    BGP active source updates being sent (2^28) in the SP backbone?

There are two uses of Source Active routes, described respectively in
sections 9 and 10.  As used in section 9, this problem cannot arise because
the SA routes are not generated as the result of receiving data traffic.
The use described in section 10 does however need to be discussed in the
security considerations.

Pekka>    This problem is not described in security considerations.

>From the Security Considerations section:

   "an implementation SHOULD provide mechanisms that allow a SP to place
   limitations on the following:

     - total number of (C-*,C-G) and/or (C-S,C-G) states per VRF"

Since SA AD routes are generated only as a result of creating the
corresponding multicast states, limiting the number of multicast states per
VRF results in limiting the number of Source Active routes.

A more specific discussion can be found in the Security Considerations
section of draft-ietf-l3vpn-mcast-bgp:

  "In conjunction with the procedures specified in Section "Supporting
   PIM-SM without Inter-Site Shared C-trees" an implementation SHOULD
   provide capabilities to impose an upper bound on the number of Source
   Active A-D routes, as well as on how frequently they may be
   originated. This SHOULD be provided on a per PE, per MVPN granularity."


Pekka> 6) PIM-BIDIR usage.  May the SP use PIM-BIDIR internally even if the
Pekka>    customer interface would use PIM-SM?

I'm not sure I understand exactly what you are asking.  The technology for
building the P-tunnels is completely independent of the multicast technology
used by the customer.

Pekka> 7) Type 0 Route Distinguisher.  The spec mandates using type 0 RD which
Pekka>    embeds 16-bit AS-number.

Good catch.  This is actually an error in the spec.  The material in section
8.2 reflects some earlier thinking about procedures that were revised and
worked out in more detail in draft-ietf-l3vpn-2547bis-mcast-bgp.  What we
will do is eliminate the text in section 8.2 and replace it with a reference
to the mcast-bgp draft.


> 3.2. P-Multicast Service Interfaces (PMSIs)

>      Multicast data packets received by a PE over a PE-CE interface must
>      be forwarded to one or more of the other PEs in the same MVPN for
>      delivery to one or more other CEs.

Pekka> .. is this strictly accurate?  doesn't this depend on where the RP is
Pekka> configured to be?  This seems to assume that the RP configuration is
Pekka> always provided by the customer, never by SP?  Because if RP is
Pekka> provided by the service provider, then the same packets could be
Pekka> forwarded back to the CE, without being forwarded at all to other
Pekka> PEs.

I'm not sure I see what the RP has to do with it, but it would be more
accurate to say "A PE must have the ability to forward multicast data
packets received from a CE to one or more of the other PEs in the same MVPN
for delivery to one or more other CEs."

Pekka> In 3.2,

>    - PIM
>
>        A PMSI can be instantiated as (a set of) Multicast Distribution
>        Trees created by the PIM P-instance ("P-trees").
>
>        The multicast distribution trees that instantiate I-PMSIs may be
>        either shared trees or source-specific trees.

Pekka> ... I-PMSI with PIM is not really described;

The specification for instantiating PMSIs using the different tunneling
technologies is in section 6.

Pekka> this part only describes S-PMSI's.

I don't know why you think so, that's not the intention.

> FWIW, S5.2 only discusses MI-PMSI

Section 5.2 is about running C-PIM over an MI-PMSI.  The material you cite
from section 3.2 is about using P-PIM to create P-tunnels that instantiate
PMSIs.  These are different topics.

> 6.4.2 PIM Trees
> 
>    The RP or RPA
>    corresponding to the P-group address is not specified.  It must of
>    course be known to all the PEs.  It is presupposed that the PEs use
>    one of the methods for automatically learning the RP-to-group
>    correspondences (e.g., Bootstrap Router Protocol [BSR]), or else that
>    the correspondence are configured.

Pekka> .. a clarification?  Do P or PE routers need to know the RP mappings
Pekka> of C-trees, i.e., when the customer has configured one of its own
Pekka> routers as the RP, does SP need to know the IP address?

Section 6.4.2 is not about C-trees, it's about P-trees ;-)  

> 6.4.5 Ingress replication
>
>    This draft defines a number of optional procedures which require that
>    a tunnel egress, upon receiving a tunnel packet, be able to identify
>    the tunnel ingress.  Unicast P-tunnel mechanisms which do not provide
>    this property (e.g., multi-hop LSPs for which penultimate-hop-popping
>    is done) should therefore be used with caution.  In particular, such
>    mechanisms MUST NOT be used unless either (a) PIM over MI-PMSI is
>    being used for distributing PE-PE C-multicast routing information, or
>    (b) the procedures of section 9 are being followed.

Pekka> .. who is the target audience of this 'caution' and 'MUST NOT'?  An
Pekka> implementer, operator or both?  It is not clear enough if this is
Pekka> actionable if it's implementer; it's not clear if this is clear
Pekka> enough if it's the operator.

I have to agree that this is a rather convoluted paragraph.  I think the
following rewording may be better:

   Section 9.1 specifies three different methods that can be used to prevent
   duplication of multicast data packets.  Any given deployment must use at
   least one of those methods.  Note that the method described in section
   9.1.1 ("Discarding Packets from the Wrong PE") presupposes that the
   egress PE of a P-tunnel can, upon receiving a packet from the P-tunnel,
   determine the identity of the PE that transmitted the packet into the
   P-tunnel. SPs that use ingress replication to instantiate their PMSIs are
   cautioned against the use for this purpose of unicast P-tunnel
   technologies that do not allow the egress PE to identify the ingress PE
   (e.g., MP2P LSPs, or P2P/P2MP LSPs for which penultimate hop popping is
   done).  Deployment of ingress replication with such a P-tunnel technology
   MUST NOT be done unless it is known that the deployment relies entirely
   on the procedures of section 9.1.2 or 9.1.3 for duplicate prevention.


>12.1.2. Encapsulation in IP
>
>    IP-in-IP [RFC1853] is also a viable option.
>

Pekka> .. 1853 is informational.  RFC2003 is standards track version of
Pekka> IP-in-IP spec.

Fixed.

Pekka> there is no section 12.2.3, what are you referring to?

11.2.3, fixed.

> 12.4.1. MTU (Maximum Transmission Unit)
>
>
>    It is the responsibility of the originator of a C-packet to ensure
>    that the packet is small enough to reach all of its destinations,
>    even when it is encapsulated within IP or GRE.

Pekka> I think you're refererring to the host at a customer site, right?
Pekka> Assigning "responsibility" this way is understandable, but it is in
Pekka> conflict with the IP service model, where the originator has no such
Pekka> responsibility.

That may be true in theory, but in practice the hosts do have this
responsibility. 

> Security Considerations:

Pekka> ... what about BGP signalling mechanisms?  Which attributes
Pekka> should/could be filtered and how?

This should be covered in the Security Considerations of RFCs 4364 and 4365
(referenced) and draft-ietf-l3vpn-2547bis-mcast-bgp (to which a reference
has been added).

> In particular, an implementation SHOULD provide mechanisms that allow
> a SP to place limitations on the following:

Pekka> ... this list should include the source active A-D routes and similar
Pekka> signalling which is triggered by a host sending into a random group.

Discussed above.


Pekka> editorial
Pekka> ---------

Pekka> In S 2.2.1, the term "C-tree" is introduced without a prior
Pekka> explanation. (An explanation of a kind appears to be in S 3.1)

Explanation added to 2.2.1.


>S 9.1.1
>
>    If an I-PMSI is used for carrying the packets, the I-PMSI spans
>    multiple ASes, and the I-PMSI is realized via segmented inter-AS
>    P-tunnels, if C-S or C-RP is multi-homed to different PEs, as long as
>    each such PE is in a different AS, the egress PE can detect duplicate
>    traffic as such duplicate traffic will arrive on a different (inter-
>    AS) P-tunnel.

Pekka> .. I had difficulties following this pretty long sentence, break it up?

How about:

   Consider the case of an I-PMSI that spans multiple ASes and that is
   instantiated by segmented Inter-AS P-tunnels.  Suppose it is carrying
   data this is traveling along a particular C-tree.  Suppose also that
   the C-root of that C-tree is multi-homed to two or more PEs, and that
   each such PE is in a different AS than the others.  Then if there is
   any duplicate traffic, the duplicates will arrive on a different
   P-tunnel.


> 12.2.2. Encapsulation in IP


> Rather than the IP-in-IP encapsulation discussed in section 12.1.2,
> we use the MPLS-in-IP encapsulation.  This is specified in [MPLS-IP].
> The IP protocol number MUST be set to the value identifying the
> payload as an MPLS unicast packet. (There is no "MPLS multicast
> packet" protocol number.)


Pekka> .. the IANA registry only seems to have "MPLS-in-IP" (value 137).  Is
Pekka> this the one?  Given that 'unicast' is not mentioned in the registry,
Pekka> should you just say "MPLS-in-IP" and/or the decimal value here?

I think the cited text is necessary for clarity if someone actually reads
[MPLS-IP] rather than just looking at the IANA page.



From daniel@olddog.co.uk  Tue Oct 20 02:44:52 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 AE4E93A67E1 for <l3vpn@core3.amsl.com>; Tue, 20 Oct 2009 02:44:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.999
X-Spam-Level: 
X-Spam-Status: No, score=-0.999 tagged_above=-999 required=5 tests=[AWL=-1.601, 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 NRM5Bt8W1XVj for <l3vpn@core3.amsl.com>; Tue, 20 Oct 2009 02:44:52 -0700 (PDT)
Received: from asmtp1.iomartmail.com (asmtp1.iomartmail.com [62.128.201.248]) by core3.amsl.com (Postfix) with ESMTP id C40413A6801 for <l3vpn@ietf.org>; Tue, 20 Oct 2009 02:44:50 -0700 (PDT)
Received: from asmtp1.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp1.iomartmail.com (8.13.8/8.13.8) with ESMTP id n9K9ihd1006190;  Tue, 20 Oct 2009 10:44:48 +0100
Received: from Serenity (88-97-23-122.dsl.zen.co.uk [88.97.23.122]) (authenticated bits=0) by asmtp1.iomartmail.com (8.13.8/8.13.8) with ESMTP id n9K9ifgX006172;  Tue, 20 Oct 2009 10:44:42 +0100
From: "Daniel King" <daniel@olddog.co.uk>
To: <l3vpn@ietf.org>
Subject: Agenda Requests for IETF 76
Date: Tue, 20 Oct 2009 10:44:43 +0100
Message-ID: <001b01ca5169$f43bb4d0$dcb31e70$@co.uk>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_001C_01CA5172.56001CD0"
X-Mailer: Microsoft Office Outlook 12.0
Thread-index: AcpRafMpbXbuGWIbR3uvekjHiiTemw==
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, 20 Oct 2009 09:44:52 -0000

This is a multi-part message in MIME format.

------=_NextPart_000_001C_01CA5172.56001CD0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Konichiwa, 

 

Our L3VPN session is currently scheduled for 13:00-15:00 on Monday, November
9.  If you have an agenda request, please let me know by October 28. 

 

Br, Dan. 


------=_NextPart_000_001C_01CA5172.56001CD0
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>Konichiwa, <o:p></o:p></p>

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

<p class=3DMsoNormal>Our L3VPN session is currently scheduled for =
13:00-15:00 on Monday,
November 9. &nbsp;If you have an agenda request, please let me know by =
October 28.
<o:p></o:p></p>

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

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

</div>

</body>

</html>

------=_NextPart_000_001C_01CA5172.56001CD0--


From pekkas@netcore.fi  Tue Oct 20 23:31:47 2009
Return-Path: <pekkas@netcore.fi>
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 BA2593A68FE; Tue, 20 Oct 2009 23:31:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.353
X-Spam-Level: 
X-Spam-Status: No, score=-2.353 tagged_above=-999 required=5 tests=[AWL=0.246,  BAYES_00=-2.599]
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 YkFyEAO2Ks24; Tue, 20 Oct 2009 23:31:46 -0700 (PDT)
Received: from netcore.fi (eunet-gw.ipv6.netcore.fi [IPv6:2001:670:86:3001::1]) by core3.amsl.com (Postfix) with ESMTP id 4C14C3A67D4; Tue, 20 Oct 2009 23:31:46 -0700 (PDT)
Received: from netcore.fi (localhost [127.0.0.1]) by netcore.fi (8.13.8/8.13.8) with ESMTP id n9L6VfjQ024719 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 21 Oct 2009 09:31:41 +0300
Received: from localhost (pekkas@localhost) by netcore.fi (8.13.8/8.13.8/Submit) with ESMTP id n9L6Ve0e024715; Wed, 21 Oct 2009 09:31:40 +0300
Date: Wed, 21 Oct 2009 09:31:40 +0300 (EEST)
From: Pekka Savola <pekkas@netcore.fi>
To: Eric Rosen <erosen@cisco.com>
Subject: Re: Last Call: draft-ietf-l3vpn-2547bis-mcast (Multicast in MPLS/BGP IP VPNs) to Proposed Standard 
In-Reply-To: <26940.1255963492@erosen-linux>
Message-ID: <alpine.LRH.2.00.0910210906360.23684@netcore.fi>
References: <26940.1255963492@erosen-linux>
User-Agent: Alpine 2.00 (LRH 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII
X-Virus-Scanned: clamav-milter 0.95.2 at otso.netcore.fi
X-Virus-Status: Clean
Cc: l3vpn-chairs@tools.ietf.org, ietf@ietf.org, draft-ietf-l3vpn-2547bis-mcast@tools.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: Wed, 21 Oct 2009 06:31:47 -0000

I'll only comment on a couple of followups below. I think I've 
described my POV and I probably won't do further follow-ups.

On Mon, 19 Oct 2009, Eric Rosen wrote:
> Pekka>    At the minimum, the status (intent) of the spec should be
> Pekka>    clarified. Even better would be to improve and include the support
> Pekka>    here.
>
> In general, the procedures specified in the document will enable an IPv4 SP
> backbone to support customer use of IPv6 multicast.  You are correct that
> section 7.4.2.2 is incomplete in this respect.

Do you intend to correct this?  One could argue that this does not 
fulfill the requirements for PS as it stands.

> Pekka> 2) RP configuration in SP network.  It's not clear if SP network
> Pekka>    needs to know how customer sites have configured their RPs (when
> Pekka>    the customer provides the RP).  At least traditional PIM
> Pekka>    signalling would require SP to know this.  But if auto-rp or BSR
> Pekka>    is not used by the customer, how is this information learned and
> Pekka>    maintained?  Would it require manual configuration?
>
> A PE router does function as a PIM peer of a CE router, and hence needs some
> way to get the group-to-RP mappings of the customer.  How this is done is
> for the SP and the customer to determine.

Do you intend to spell this out more clearly?  This seems like a major 
configuration and O&M issue?  Unfortunately this does not have good 
solutions, and I suppose those ones that do exist do not have rough 
consensus in the community.  As it stands it seems like the spec chose 
to punt an issue that is required to be resolved in order to operate 
the protocol.

>> From the Security Considerations section:
>
>   "an implementation SHOULD provide mechanisms that allow a SP to place
>   limitations on the following:
>
>     - total number of (C-*,C-G) and/or (C-S,C-G) states per VRF"
>
> Since SA AD routes are generated only as a result of creating the
> corresponding multicast states, limiting the number of multicast states per
> VRF results in limiting the number of Source Active routes.

I may be missing something but it's not clear why you say so.  At 
least in regular PIM-SM, source state can be created without creating 
receiver state.  S 10.1.2.2 seems to imply that AD routes would be 
generated based on the receipt of Register messages, at which point 
there is not yet necessarily any join state.

> A more specific discussion can be found in the Security Considerations
> section of draft-ietf-l3vpn-mcast-bgp:
>
>  "In conjunction with the procedures specified in Section "Supporting
>   PIM-SM without Inter-Site Shared C-trees" an implementation SHOULD
>   provide capabilities to impose an upper bound on the number of Source
>   Active A-D routes, as well as on how frequently they may be
>   originated. This SHOULD be provided on a per PE, per MVPN granularity."

While this is on a different spec, experience with MSDP has shown that 
SHOULD is insufficient; these requirements are a MUST from O&M 
perspective.

> Pekka> 6) PIM-BIDIR usage.  May the SP use PIM-BIDIR internally even if the
> Pekka>    customer interface would use PIM-SM?
>
> I'm not sure I understand exactly what you are asking.  The technology for
> building the P-tunnels is completely independent of the multicast technology
> used by the customer.

Ok, that is what I wanted to hear.  Maybe it was clear enough but I 
wasn't 100% sure.

>> 3.2. P-Multicast Service Interfaces (PMSIs)
>
>>      Multicast data packets received by a PE over a PE-CE interface must
>>      be forwarded to one or more of the other PEs in the same MVPN for
>>      delivery to one or more other CEs.
>
> Pekka> .. is this strictly accurate?  doesn't this depend on where the RP is
> Pekka> configured to be?  This seems to assume that the RP configuration is
> Pekka> always provided by the customer, never by SP?  Because if RP is
> Pekka> provided by the service provider, then the same packets could be
> Pekka> forwarded back to the CE, without being forwarded at all to other
> Pekka> PEs.
>
> I'm not sure I see what the RP has to do with it, but it would be more
> accurate to say "A PE must have the ability to forward multicast data
> packets received from a CE to one or more of the other PEs in the same MVPN
> for delivery to one or more other CEs."

Agreed.  This underlines the need for "ability", not that it actually 
happens.  I was referring to the degenerate case where all MVPN's 
sources and receivers would (at that point in time) happen to be 
behind the same PE.

-- 
Pekka Savola                 "You each name yourselves king, yet the
Netcore Oy                    kingdom bleeds."
Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings

From root@core3.amsl.com  Mon Oct 26 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 CF6323A6A97; Mon, 26 Oct 2009 09:00:01 -0700 (PDT)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Subject: I-D Action:draft-ietf-l3vpn-mvpn-considerations-05.txt 
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20091026160001.CF6323A6A97@core3.amsl.com>
Date: Mon, 26 Oct 2009 09:00:01 -0700 (PDT)
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, 26 Oct 2009 16: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           : Mandatory Features in a Layer 3 Multicast BGP/MPLS VPN Solution
	Author(s)       : T. Morin, et al.
	Filename        : draft-ietf-l3vpn-mvpn-considerations-05.txt
	Pages           : 39
	Date            : 2009-10-26

More that one set of mechanisms to support multicast in a layer 3
BGP/MPLS VPN has been defined.  These are presented in the documents
that define them as optional building blocks.

To enable interoperability between implementations, this document
defines a subset of features that is considered mandatory for a
multicast BGP/MPLS VPN implementation.  This will help implementers
and deployers understand which L3VPN multicast requirements are best
satisfied by each option.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-l3vpn-mvpn-considerations-05.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-mvpn-considerations-05.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

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


--NextPart--

From daniel@olddog.co.uk  Wed Oct 28 02:44:21 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 AF58428C0DC for <l3vpn@core3.amsl.com>; Wed, 28 Oct 2009 02:44:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.343
X-Spam-Level: 
X-Spam-Status: No, score=-0.343 tagged_above=-999 required=5 tests=[AWL=-0.203, BAYES_20=-0.74, 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 R0zXLQUFBBuh for <l3vpn@core3.amsl.com>; Wed, 28 Oct 2009 02:44:20 -0700 (PDT)
Received: from asmtp2.iomartmail.com (asmtp2.iomartmail.com [62.128.201.249]) by core3.amsl.com (Postfix) with ESMTP id B281C28C0DE for <l3vpn@ietf.org>; Wed, 28 Oct 2009 02:44:07 -0700 (PDT)
Received: from asmtp2.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp2.iomartmail.com (8.13.8/8.13.8) with ESMTP id n9S9i8Xl016582 for <l3vpn@ietf.org>; Wed, 28 Oct 2009 09:44:13 GMT
Received: from Serenity (88-97-23-122.dsl.zen.co.uk [88.97.23.122]) (authenticated bits=0) by asmtp2.iomartmail.com (8.13.8/8.13.8) with ESMTP id n9S9i6Qh016562 for <l3vpn@ietf.org>; Wed, 28 Oct 2009 09:44:08 GMT
From: "Daniel King" <daniel@olddog.co.uk>
To: <l3vpn@ietf.org>
Subject: IETF 76: L3VPN Draft Agenda
Date: Wed, 28 Oct 2009 09:44:09 -0000
Message-ID: <001901ca57b3$336ffc20$9a4ff460$@co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcpXszKEtlITu7sbSj2YCaW5y1mCyA==
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: Wed, 28 Oct 2009 09:44:21 -0000

Hello All,  

The draft l3vpn agenda for IETF 76 is now online:

http://www.ietf.org/proceedings/09nov/agenda/l3vpn.txt

If your presenting during the session, please send me your slides no later
than Friday, November 6.

The l3vpn session is scheduled for Monday, November 9, 2009. (1300-1500 -
Afternoon Session I). 

Br, Dan.


From rfc-editor@rfc-editor.org  Wed Oct 28 09:20:36 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 B1EB43A6822; Wed, 28 Oct 2009 09:20:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -16.916
X-Spam-Level: 
X-Spam-Status: No, score=-16.916 tagged_above=-999 required=5 tests=[AWL=0.083, 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 UpeswwhLIxi3; Wed, 28 Oct 2009 09:20:36 -0700 (PDT)
Received: from bosco.isi.edu (bosco.isi.edu [128.9.168.207]) by core3.amsl.com (Postfix) with ESMTP id DF21E28C1CA; Wed, 28 Oct 2009 09:20:35 -0700 (PDT)
Received: by bosco.isi.edu (Postfix, from userid 70) id 46895356983; Wed, 28 Oct 2009 09:17:46 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 5668 on 4-Octet AS Specific BGP Extended Community
From: rfc-editor@rfc-editor.org
Message-Id: <20091028161746.46895356983@bosco.isi.edu>
Date: Wed, 28 Oct 2009 09:17:46 -0700 (PDT)
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: Wed, 28 Oct 2009 16:20:36 -0000

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

        
        RFC 5668

        Title:      4-Octet AS Specific BGP Extended 
                    Community 
        Author:     Y. Rekhter, S. Sangli,
                    D. Tappan
        Status:     Standards Track
        Date:       October 2009
        Mailbox:    yakov@juniper.net, 
                    rsrihari@cisco.com, 
                    Dan.Tappan@Gmail.com
        Pages:      5
        Characters: 9017
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-l3vpn-as4octet-ext-community-03.txt

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

This document defines a new type of a BGP extended community, which
carries a 4-octet Autonomous System (AS) number.  [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


