From l3vpn-bounces@ietf.org Mon Jan 02 12:12:45 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EtTEj-0003GM-Ic; Mon, 02 Jan 2006 12:12:45 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EtTEh-0003G5-OW
	for l3vpn@megatron.ietf.org; Mon, 02 Jan 2006 12:12:44 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA21529
	for <l3vpn@ietf.org>; Mon, 2 Jan 2006 12:11:30 -0500 (EST)
Received: from ihemail1.lucent.com ([192.11.222.161])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EtTJo-0006tv-DZ
	for l3vpn@ietf.org; Mon, 02 Jan 2006 12:18:01 -0500
Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com
	[135.85.76.62])
	by ihemail1.lucent.com (8.12.11/8.12.11) with ESMTP id k02HCXM2017297; 
	Mon, 2 Jan 2006 11:12:33 -0600 (CST)
Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service
	(5.5.2657.72) id <X5BR88N3>; Mon, 2 Jan 2006 18:12:31 +0100
Message-ID: <7D5D48D2CAA3D84C813F5B154F43B15508F1802F@nl0006exch001u.nl.lucent.com>
From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
To: jcucchiara@mindspring.com, Mark Townsley <townsley@cisco.com>
Date: Mon, 2 Jan 2006 18:12:10 +0100 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain;
	charset="iso-8859-1"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: df1883a27a831c1ea5e8cfe5eb3ad38e
Cc: l3vpn@ietf.org
Subject: RE: MIB Dr. Review of draft-ietf-l3vpn-vr-mib-04.txt 
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: l3vpn.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:l3vpn@ietf.org>
List-Help: <mailto:l3vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=subscribe>
Sender: l3vpn-bounces@ietf.org
Errors-To: l3vpn-bounces@ietf.org

Thanks Joan.

Let the authors and WG review and address your comments.

Bert

> -----Original Message-----
> From: jcucchiara@mindspring.com [mailto:jcucchiara@mindspring.com]
> Sent: Thursday, December 29, 2005 05:23
> To: jcucchiara@mindspring.com; Wijnen, Bert (Bert); Mark Townsley
> Cc: l3vpn@ietf.org
> Subject: MIB Dr. Review of draft-ietf-l3vpn-vr-mib-04.txt 
> 
> 
> 
> Hi Folks,
> 
> Following is the MIB Dr. Review of draft-ietf-l3vpn-vr-mib-04.txt
> 
> Thanks,
>   -Joan
> 
> -------------------
> 
> Compiler Issues
> -------------------------
> 
> Please fix the following compiler 
> issues:
> 
> 
> Output from smilint
> ----------------------
> Validation report
> File: VIRTUAL-ROUTER-MIB
> Severity level requested: 6
> 
> Line  Severity  Problem
> 72 5 warning: type `VrIdentifier' has no format specification
> 
> 
> Output from smicng
> -------------------
> E: f(VIRTUAL-ROUTER-MIB), (321,18) Default value 
> for "vrRpTrigger" must be named bits in "{ }"
> 
> 
> 
> 
> 
> GENERAL QUESTIONS OR OBSERVATIONS
> ---------------------------------
> 
> * Is this MIB supposed to be standards track?
>   There was some discussion on making the
>   IPSEC and VR VPN architectures informational.
> 
> * The abbreviation (VR) should be pluralized when
>   referring to more than one Virtual Router.
> 
> 
> * update to reference rfc4265.txt
>   which is the VPN-TC-STD-MIB
>   (both in MIB and in Normative Reference Section)
> 
> 
> TABLE OF CONTENTS
> ---------------------
> * Table of Contents needs to have
>   page numbers added.
> 
> * Also, no need to use .0 as in 1.0, 2.0, etc. for
>   sections.  Please just use numbers 1., 2., etc.
> 
> 
> 2.0 Introduction
> -------------------
> 
> * The document refers to PPVPN but the working group is
>   now L3VPN so should this be updated in the references
>   and elsewhere.
> 
> * The second and third goal should be removed.  The MIB Module
>   should be implementable and also provide functionality as
>   described by the first goal, so no need to state the 2nd
>   and 3rd goal.   Please combine the first goal with the
>   previous paragraph.
> 
> * Suggestion only:  you may want to combine the Terminology
>   Section with the Introduction.
> 
> 
> 4.0  Overview of the Virtual Router MIB Module
> ------------------------------------------------
> 
> 4.1 SNMP Contexts for Management for Virtual Routers
> -------------------------------------------------------
> 
> This section is somewhat troubling due to some statements
> such as "There is a need for a single agent..." mixed in
> with some insightful considerations that may be 
> taken into account by a network management
> architect of a Virtual Router device.
> 
> Could you list these considerations without mandating a 
> specific architecture?
> 
> For example, instead of mandating the use of VR 0 as an
> "Admin" domain which has certain properties, could you state
> that one consideration is to have a SNMP entity
> on the device that can view all of the data, including data
> that resides in the alll Virtual Routers.  
> 
> Additionally, the use of the context as a unique index accross the
> VPN seems wrong and not sure that this is actually
> enforceable.
> 
> Last but not least, some of the language used is inconsistent
> with that of RFC3411.  Since you reference RFC3411, please 
> be consistent with the use of terminology. 
> 
> 
> 4.3  Creation and Deletion of VRs
> ---------------------------------
> 
> * Please rename this to "The Virtual Router Configuration Table"
> and update the text as needed.
> 
> * The paragraph:
> "VRID 0 is assigned to the Administrative VR, which exists by default,
> and need not be created. Deletion of the Administrative VR will not be
> permitted.  The VRID of the Administrative VR (VRID 0) should be a
> reserved VRID number.  VRID 0 could be termed the "null VR" and it 
> could be the context that manages the resource pool of unattached 
> interfaces. Routing would then not exist in the context of 
> Administrative VR."  
> 
> Should probably be removed (again, this is imposing an
> architecture which is out of scope of a MIB document.)
> 
> 
> 4.4 Administrative and Operational Status of VRs
> -------------------------------------------------
> * could this be renamed "The Virtual Router Status Table"
> 
> 
> 4.4.1  VR Routing Protocol Trigger
> ------------------------------------
> * could you please put "Object" on the end of this.
> 
> 
> 4.6 Setting per VR limits
> ---------------------------
> * this should be a subsection under the vrConfigTable
> section. 
> 
> 4.8 Traps
> -----------
> * The current terminology is notification.  Please change
> this in the title of this section and through the document.
> 
> 4.9 Usability Considerations
> -------------------------------
> You may want to completely remove any architectual descriptions
> from this MIB document.  That would be my preference, but if
> you believe that it's best to include such  section than
> think you should list the above single SNMP agent description in
> this section, along with the multiple agent description.
> 
> 
> 4.9.2  Provisioning vs. Monitoring
> ----------------------------------
> 
> This section is not needed.  The MIB Module's conformance
> statements should specify both a read-write/create (full conformance)
> and a read-only conformance.
> 
> 5.1  Creation of a VR
> -------------------------
>  
> * Item #2 says "Using a context with a 'read-write' access
> for system level entities.  This should probably be reworded.
> 
> 6.0 Definition of the Virtual Router MIB Module
> --------------------------------------------------
> 
> * Name of the Module:  VIRTUAL-ROUTER-MIB
> 
> - Could you include VPN some place in this title? 
>   e.g. VIRTUAL-ROUTER-VPN-MIB.  This should be carried
>   as the prefix throughout the MIB, so would expect
>   to see vrVpnObjects, vrVpnConformance, etc.
> 
> 
> 
> - if this is a standard's track document, then also 
>   STD should be included in the MIB title to be consistent
>   with other MIB modules from this working group:
>   e.g. VIRTUAL-ROUTER-VPN-STD-MIB
> 
> * The following note should be removed as this is now RFC4265.
> -- RFC Ed.: VPN-TC-STD-MIB in Last Call in L3VPN WG
> 
> * DisplayString is no longer used in MIB Modules.  This is
>  because it does not support internationalized text.  
> see:  http://www.ops.ietf.org/mib-common-tcs.html
> Better to use SnmpAdminString defined in
> SNMP-FRAMEWORK-MIB [RFC3411], or some other TC which supports
> internationalization.
> 
> * VrIdentifier, please remove the VRID of 0 is the
>   Administrative VR.
> 
> * VrRpTriggerBitCode
>   Please specify that the value of 1 indicates that the
>   Routing Protocol will be or has been initiated on the
>   Virtual Router, and 0 indicates that the Routing protocol
>   is not running, or has been requested to be shutdown.
>   (In other words, please describe what the BIT values of
>    1 and 0 mean.)
> 
> * Please put top level OIDs together, for example:
> 
>     vrNotifications OBJECT IDENTIFIER ::= { virtualRouterMIB 0 }
>     vrMIBObjects OBJECT IDENTIFIER ::= { virtualRouterMIB 1 }
>     vrConformance OBJECT IDENTIFIER ::= { virtualRouterMIB 2 }
> 
> - Please rename: vrNotifications to vrVpnNotifications,
>   vrMIBObjects to vrVpnObjects, and
>  vrConformance to vrVpnConformance., 
> 
> * Please rename vrConfig to vrVpnConfigObjects
> 
> 
> 
> * vrConfigNextAvailableVrId could use the TC from
>   the DIFFSERV-MIB: IndexIntegerNextFree.  This TC is
>   in use in several MIBs and will provide the same 
>   functionality as you intend. 
> 
> 
> * VrConfigEntry
>   Suggestion only:  could you put the
>   object name and Type on the same line.
> 
>   Also, please put RowStatus as the last object in the
>   entry.  Granted these are more stylistic suggestions
>   but seem to be fairly common place in IETF MIB Modules.
> 
> 
> * vrId
> - as mentioned previously, please remove the discussion regarding
>   VRID 0.
> - Please include some discussion about how to use 
>   vrConfigNextAvailableVrId to acquire a value for this index.
>   (suggestion to look at DIFFSERV-MIB as an example.)
> 
> * vrTrapEnable
> - Please rename to vrNotificationEnabled
> - I *think* this object can be removed and the MIBs in RFC2573 be used
>   instead.  Please comment on this.  In other words, this object
>   might control whether or not 
>   the instrumentation generates a notification, but
>   the actual sending is controlled by the MIBs in RFC2573.
>   For this object, it would seem that the sending is more
>   the issue than the VR creation/deletion.
> 
> 
> * vrAdminStatus
> - Why is the DEFVAL { down } ?  
> 
> *vrMaxRoutesTrapEnable
> - same comments as with vrTrapEnable
> 
> 
> * vrStat
> - Please rename to vrStatusObjects, vrStatusScalars, etc.
> 
> * vrConfiguredVRs and vrActiveVRs seem to be objects that
>   could be figured out by the management station. Could you
>   explain what the motivation is for having them in the MIB?
> 
> - Also, these should be type Gauge32.
> 
> * vrStatTable -- the description should be changed to status and
>   not statistics.
> 
> * INDEX is the same as VrConfigTable, should this have an
>   AUGMENTS relationship?
> 
> * vrStatEntry - same comments as with vrConfigEntry
> 
> * vrStatRouteEntries and vrStatFIBEntries should probably be
>   Gauge32
> 
> *vrOperStatus - could unknown(3) be listed first?
>   Also, wouldn't testing be a valid status for this object?
> 
> 
> * vrIfConfig - please change to vrIfConfigObjects
> 
> * vrIfConfigTable's description is confusing.  Is this
>   table used to add and delete Interfaces that exist in
>   the ifTable to the Virtual Router?  If so then 
>   could that be stated in the DESCRIPTION for the table?
> 
> * vrNotificationPrefix should be removed
> 
> * vrUp - could the description be a little more generic, 
>   such as "operational status to up from any other state".
>   In other words, must it really go from "down to up"
>   or would it be valid to go from "testing to up"?
> 
> * vrDown - could you also include the vrAdminStatus for
>   this object?
> 
> * Conformance/Compliance statements need to include 
>   a statement for read-only compliance.  In other words,
>   if an implementation only wants to use this MIB for
>   monitoring, then they should also have a way to be
>   compliant.
> 
> - Also, regarding InetAddressType and InetAddress, you
>   may only want to require that an implementation support
>   a subset (example from DIFFSERV-MIB):
>     OBJECT diffServMultiFieldClfrAddrType
>     SYNTAX  InetAddressType { unknown(0), ipv4(1), ipv6(2) }
>     DESCRIPTION
>        "An implementation is only required to support IPv4 and IPv6
>        addresses."
> 
>     OBJECT diffServMultiFieldClfrDstAddr
>     SYNTAX  InetAddress (SIZE(0|4|16))
>     DESCRIPTION
>        "An implementation is only required to support IPv4 
> and globally
>        unique IPv6 addresses."
> 
> - also with RowStatus, you may want something like:
>     OBJECT diffServAlgDropStatus
>     SYNTAX RowStatus { active(1) }
>     WRITE-SYNTAX RowStatus { createAndGo(4), destroy(6) }
>     DESCRIPTION
>        "Support for createAndWait and notInService is not required."
> 
> 
> 7. Acknowledgements
> 
> Please add:
> 
> This document is a product of the L3VPN Working Group.
> 
> Thanks for the acknowledgement.
> 
> 
> 
> 8. Security Considerations
> 
> There are no objects listed but a couple of paragraphs say
> something like:
> " These are the tables and objects and their
> sensitivity/vulnerability:"
> 
> but then there aren't any objects listed.  Please update
> this section.  It was difficult to review as it seems incomplete.
> 
> 
> 9. References
> 
> Need to be updated.
> 
> [VPNTCMIB]  B. Schliesser, and T. Nadeau, "Definition of Textual
>      Conventions for Provider Provisioned Virtual Private Network
>      (PPVPN) Management.", Internet Draft
>      <draft-ietf-l3vpn-tc-mib-03.txt>, May 2004.
> 
> As previously mentioned this is now rfc4265.
> 
> And there are other drafts which are now RFCs listed.
> 
> 
> end.
> 
> 
> 




From l3vpn-bounces@ietf.org Wed Jan 04 09:51:38 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Eu9zG-0007Sc-Kq; Wed, 04 Jan 2006 09:51:38 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Eu9zF-0007SX-3a
	for l3vpn@megatron.ietf.org; Wed, 04 Jan 2006 09:51:37 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA09601
	for <l3vpn@ietf.org>; Wed, 4 Jan 2006 09:50:23 -0500 (EST)
Received: from ixe-nat1.juniper.net ([193.110.54.36] helo=up-smtp.jnpr.net)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EuA4h-0002m1-6n
	for l3vpn@ietf.org; Wed, 04 Jan 2006 09:57:18 -0500
Received: from emailemea1.jnpr.net ([172.26.192.140]) by up-smtp.jnpr.net with
	Microsoft SMTPSVC(6.0.3790.211); Wed, 4 Jan 2006 14:51:09 +0000
Received: from pi-smtp.jnpr.net ([10.10.2.36]) by emailemea1.jnpr.net with
	Microsoft SMTPSVC(6.0.3790.211); Wed, 4 Jan 2006 14:51:08 +0000
Received: from proton.jnpr.net ([10.10.2.37]) by pi-smtp.jnpr.net with
	Microsoft SMTPSVC(5.0.2195.6713); Wed, 4 Jan 2006 09:51:07 -0500
Received: from [172.23.1.79] ([172.23.1.79] RDNS failed) by proton.jnpr.net
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 4 Jan 2006 09:51:06 -0500
Message-ID: <43BBE0D5.2060607@juniper.net>
Date: Wed, 04 Jan 2006 09:51:01 -0500
From: Ron Bonica <rbonica@juniper.net>
User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: l3vpn@ietf.org
X-Enigmail-Version: 0.93.0.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 04 Jan 2006 14:51:07.0104 (UTC)
	FILETIME=[4B071E00:01C6113E]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8ac499381112328dd60aea5b1ff596ea
Content-Transfer-Encoding: 7bit
Subject: WG last call: draft-ietf-l3vpn-ppvpn-mcast-reqts-03
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: l3vpn.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:l3vpn@ietf.org>
List-Help: <mailto:l3vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=subscribe>
Sender: l3vpn-bounces@ietf.org
Errors-To: l3vpn-bounces@ietf.org

Folks,

This email initiates a WG last call for
draft-ietf-l3vpn-ppvpn-mcast-reqts-03. Last call ends Jan 19, 2006.

                               Ron




From l3vpn-bounces@ietf.org Thu Jan 05 16:39:26 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EucpS-00005r-8L; Thu, 05 Jan 2006 16:39:26 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EucpQ-0008SR-4G
	for l3vpn@megatron.ietf.org; Thu, 05 Jan 2006 16:39:24 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA25329
	for <l3vpn@ietf.org>; Thu, 5 Jan 2006 16:38:07 -0500 (EST)
Received: from colo-dns-ext2.juniper.net ([207.17.137.64])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Eucv9-0007N4-C7
	for l3vpn@ietf.org; Thu, 05 Jan 2006 16:45:21 -0500
Received: from merlot.juniper.net (merlot.juniper.net [172.17.27.10])
	by colo-dns-ext2.juniper.net (8.12.3/8.12.3) with ESMTP id
	k05LdC1Z099273
	for <l3vpn@ietf.org>; Thu, 5 Jan 2006 13:39:12 -0800 (PST)
	(envelope-from yakov@juniper.net)
Received: from juniper.net (sapphire.juniper.net [172.17.28.108])
	by merlot.juniper.net (8.11.3/8.11.3) with ESMTP id k05LdC501113;
	Thu, 5 Jan 2006 13:39:12 -0800 (PST)
	(envelope-from yakov@juniper.net)
Message-Id: <200601052139.k05LdC501113@merlot.juniper.net>
To: Ron Bonica <rbonica@juniper.net>
In-Reply-To: Your message of "Wed, 04 Jan 2006 09:51:01 EST."
	<43BBE0D5.2060607@juniper.net> 
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <92911.1136497151.1@juniper.net>
Date: Thu, 05 Jan 2006 13:39:12 -0800
From: Yakov Rekhter <yakov@juniper.net>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581
Cc: l3vpn@ietf.org
Subject: Re: WG last call: draft-ietf-l3vpn-ppvpn-mcast-reqts-03 
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: l3vpn.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:l3vpn@ietf.org>
List-Help: <mailto:l3vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=subscribe>
Sender: l3vpn-bounces@ietf.org
Errors-To: l3vpn-bounces@ietf.org

Ron,

> Folks,
> 
> This email initiates a WG last call for
> draft-ietf-l3vpn-ppvpn-mcast-reqts-03. Last call ends Jan 19, 2006.
> 
>                                Ron

I suggest to add the following to either 5.1.5 or 5.2.7:

   For security reasons service providers may want to confine
   direct control traffic exchange among the providers to a combination
   of ASBRs (or even a subset of ASBRs) that connect the providers,
   and (optionally) a designated set of BGP Route Reflectors.
   For one thing, doing this would allow to MD5-key all control
   traffic exchanges among providers, while confining MD5 key
   administration to just the ASBRs (or even a subset of ASBRs),
   and Route Reflectors.

Yakov.




From l3vpn-bounces@ietf.org Mon Jan 09 04:15:35 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Evt7n-0002Z9-T2; Mon, 09 Jan 2006 04:15:35 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Evt7m-0002Z4-3C
	for l3vpn@megatron.ietf.org; Mon, 09 Jan 2006 04:15:34 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA29006
	for <l3vpn@ietf.org>; Mon, 9 Jan 2006 04:14:15 -0500 (EST)
Received: from p-mail1.rd.francetelecom.com ([195.101.245.15])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EvtEE-0006Dx-Sk
	for l3vpn@ietf.org; Mon, 09 Jan 2006 04:22:15 -0500
Received: from ftrdmel10.rd.francetelecom.fr ([10.193.117.156]) by
	ftrdsmtp2.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.211); 
	Mon, 9 Jan 2006 10:15:13 +0100
Received: from l-at8613.rd.francetelecom.fr ([10.193.15.109]) by
	ftrdmel10.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.211); 
	Mon, 9 Jan 2006 10:15:13 +0100
From: Thomas Morin <thomas.morin@rd.francetelecom.com>
To: Yakov Rekhter <yakov@juniper.net>
In-Reply-To: <200601052139.k05LdC501113@merlot.juniper.net>
References: <200601052139.k05LdC501113@merlot.juniper.net>
Content-Type: text/plain
Organization: France Telecom R&D
Date: Mon, 09 Jan 2006 10:15:12 +0100
Message-Id: <1136798112.5792.12.camel@wintermute>
Mime-Version: 1.0
X-Mailer: Evolution 2.4.2 
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 09 Jan 2006 09:15:13.0492 (UTC)
	FILETIME=[329AB940:01C614FD]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228
Content-Transfer-Encoding: 7bit
Cc: L3VPN <l3vpn@ietf.org>
Subject: Re: WG last call: draft-ietf-l3vpn-ppvpn-mcast-reqts-03
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: l3vpn.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:l3vpn@ietf.org>
List-Help: <mailto:l3vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=subscribe>
Sender: l3vpn-bounces@ietf.org
Errors-To: l3vpn-bounces@ietf.org

Hi Yakov, folks, 

Yakov Rekhter:
> I suggest to add the following to either 5.1.5 or 5.2.7:
> 
>    For security reasons service providers may want to confine
>    direct control traffic exchange among the providers to a combination
>    of ASBRs (or even a subset of ASBRs) that connect the providers,
>    and (optionally) a designated set of BGP Route Reflectors.
>    For one thing, doing this would allow to MD5-key all control
>    traffic exchanges among providers, while confining MD5 key
>    administration to just the ASBRs (or even a subset of ASBRs),
>    and Route Reflectors.

I suggest adding the following atfer penultimate sentence of 5.2.7,
rephrased as follows:
"It is RECOMMENDED that corresponding procedures require the least
possible coordination between providers; more specificaly when specific
configurations or cryptographic keys have to be deployed, this shall be
limited to ASBRs (Autonomous Systems Border Routers) or a subset of
them, and optionnaly BGP Route Reflectors (or a subset of them)." 

("corresponding procedures" refers to "means to ensure the integrity and
authenticity of multicast-related exchanges across inter-ASes or
inter-provider borders")

I think this respect the initial idea, but without making any assumption
on the implementation.  What do you think?

-Thomas





From l3vpn-bounces@ietf.org Wed Jan 11 01:18:22 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EwZJO-0007kx-RM; Wed, 11 Jan 2006 01:18:22 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EwZJM-0007jK-Fp
	for l3vpn@megatron.ietf.org; Wed, 11 Jan 2006 01:18:20 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA17180
	for <l3vpn@ietf.org>; Wed, 11 Jan 2006 01:17:00 -0500 (EST)
Received: from zproxy.gmail.com ([64.233.162.205])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EwZQC-0008BU-BY
	for l3vpn@ietf.org; Wed, 11 Jan 2006 01:25:25 -0500
Received: by zproxy.gmail.com with SMTP id 9so80481nzo
	for <l3vpn@ietf.org>; Tue, 10 Jan 2006 22:18:18 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
	h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=kwldGGWc4skpJdSl6snc7D7gRvZ0cJDEr2dQUDcRsp60ZR4aihWST6jJambdWaS0qcG6WMFnpbeGYNsKG7ZCJaNuXQEIjYZ3Pm+dLAH6kCq0VO0Tea8p64X4DQJTV8+JXgRANfVjCDreq23kPM++n7j8jtZzclSSxiDDkueX/sk=
Received: by 10.36.38.3 with SMTP id l3mr388045nzl;
	Tue, 10 Jan 2006 22:18:18 -0800 (PST)
Received: by 10.36.46.2 with HTTP; Tue, 10 Jan 2006 22:18:18 -0800 (PST)
Message-ID: <dcad22d80601102218l1058192dw41411f55cda947b7@mail.gmail.com>
Date: Wed, 11 Jan 2006 01:18:18 -0500
From: Marshall Eubanks <marshall.eubanks@gmail.com>
To: Thomas Morin <thomas.morin@rd.francetelecom.com>
In-Reply-To: <1136798112.5792.12.camel@wintermute>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <200601052139.k05LdC501113@merlot.juniper.net>
	<1136798112.5792.12.camel@wintermute>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb
Content-Transfer-Encoding: quoted-printable
Cc: Yakov Rekhter <yakov@juniper.net>, L3VPN <l3vpn@ietf.org>
Subject: Re: WG last call: draft-ietf-l3vpn-ppvpn-mcast-reqts-03
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: l3vpn.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:l3vpn@ietf.org>
List-Help: <mailto:l3vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=subscribe>
Sender: l3vpn-bounces@ietf.org
Errors-To: l3vpn-bounces@ietf.org

On 1/9/06, Thomas Morin <thomas.morin@rd.francetelecom.com> wrote:
> Hi Yakov, folks,
>
> Yakov Rekhter:
> > I suggest to add the following to either 5.1.5 or 5.2.7:
> >
> >    For security reasons service providers may want to confine
> >    direct control traffic exchange among the providers to a combination
> >    of ASBRs (or even a subset of ASBRs) that connect the providers,
> >    and (optionally) a designated set of BGP Route Reflectors.
> >    For one thing, doing this would allow to MD5-key all control
> >    traffic exchanges among providers, while confining MD5 key
> >    administration to just the ASBRs (or even a subset of ASBRs),
> >    and Route Reflectors.
>
> I suggest adding the following atfer penultimate sentence of 5.2.7,
> rephrased as follows:
> "It is RECOMMENDED that corresponding procedures require the least
> possible coordination between providers; more specificaly when specific
> configurations or cryptographic keys have to be deployed, this shall be
> limited to ASBRs (Autonomous Systems Border Routers) or a subset of
> them, and optionnaly BGP Route Reflectors (or a subset of them)."
>
> ("corresponding procedures" refers to "means to ensure the integrity and
> authenticity of multicast-related exchanges across inter-ASes or
> inter-provider borders")
>
> I think this respect the initial idea, but without making any assumption
> on the implementation.  What do you think?

s/optionnaly/optionally/

Otherwise, OK.

Marshall

>
> -Thomas
>
>
>




From l3vpn-bounces@ietf.org Wed Jan 11 01:36:57 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EwZbN-0004j4-4i; Wed, 11 Jan 2006 01:36:57 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EwZbM-0004iz-Eg
	for l3vpn@megatron.ietf.org; Wed, 11 Jan 2006 01:36:56 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA18267
	for <l3vpn@ietf.org>; Wed, 11 Jan 2006 01:35:36 -0500 (EST)
Received: from zproxy.gmail.com ([64.233.162.192])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EwZiA-0000Df-GW
	for l3vpn@ietf.org; Wed, 11 Jan 2006 01:44:01 -0500
Received: by zproxy.gmail.com with SMTP id 9so82692nzo
	for <l3vpn@ietf.org>; Tue, 10 Jan 2006 22:36:52 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
	h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=Va94xnX3OT6AdJej07C0XJahjdtZuD4UJIFMsL6EQZIE620kLijHy0nBJyd+ALIJ8cSomm8ZsbSUInayub2D8gQwJeivLmM5eqU37pbMHmsl2HFjB0FBp5a2FbqRhPq+lGvcpMwp8C2ZD1xvcdDys86ByBdLN95HH1FIv+1JXjU=
Received: by 10.37.18.13 with SMTP id v13mr362501nzi;
	Tue, 10 Jan 2006 22:36:52 -0800 (PST)
Received: by 10.36.46.2 with HTTP; Tue, 10 Jan 2006 22:36:52 -0800 (PST)
Message-ID: <dcad22d80601102236u373871a7qb6f7636e5b7bbfcd@mail.gmail.com>
Date: Wed, 11 Jan 2006 01:36:52 -0500
From: Marshall Eubanks <marshall.eubanks@gmail.com>
To: Ron Bonica <rbonica@juniper.net>
In-Reply-To: <43BBE0D5.2060607@juniper.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <43BBE0D5.2060607@juniper.net>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab
Content-Transfer-Encoding: quoted-printable
Cc: l3vpn@ietf.org
Subject: Re: WG last call: draft-ietf-l3vpn-ppvpn-mcast-reqts-03
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: l3vpn.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:l3vpn@ietf.org>
List-Help: <mailto:l3vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=subscribe>
Sender: l3vpn-bounces@ietf.org
Errors-To: l3vpn-bounces@ietf.org

As my first attempt bounced, you can find my comments and corrections
on this document at

http://www.americafree.tv/papers/draft-ietf-l3vpn-ppvpn-mcast-reqts-03-tme.=
txt

I gave this document a careful read. In my opinion there are a bunch of mos=
tly
minor things that need to be corrected before it passes last call.

Regards
Marshall Eubanks

On 1/4/06, Ron Bonica <rbonica@juniper.net> wrote:
> Folks,
>
> This email initiates a WG last call for
> draft-ietf-l3vpn-ppvpn-mcast-reqts-03. Last call ends Jan 19, 2006.
>
>                                Ron
>
>




From l3vpn-bounces@ietf.org Wed Jan 11 12:30:22 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Ewjni-0004AL-SE; Wed, 11 Jan 2006 12:30:22 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Ewjnh-0004AA-Ei
	for l3vpn@megatron.ietf.org; Wed, 11 Jan 2006 12:30:21 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA28798
	for <l3vpn@ietf.org>; Wed, 11 Jan 2006 12:29:01 -0500 (EST)
Received: from colo-dns-ext2.juniper.net ([207.17.137.64])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Ewjud-0001ir-5e
	for l3vpn@ietf.org; Wed, 11 Jan 2006 12:37:32 -0500
Received: from merlot.juniper.net (merlot.juniper.net [172.17.27.10])
	by colo-dns-ext2.juniper.net (8.12.3/8.12.3) with ESMTP id
	k0BHU31Z072295; Wed, 11 Jan 2006 09:30:07 -0800 (PST)
	(envelope-from yakov@juniper.net)
Received: from juniper.net (sapphire.juniper.net [172.17.28.108])
	by merlot.juniper.net (8.11.3/8.11.3) with ESMTP id k0BHU2569112;
	Wed, 11 Jan 2006 09:30:02 -0800 (PST)
	(envelope-from yakov@juniper.net)
Message-Id: <200601111730.k0BHU2569112@merlot.juniper.net>
To: Thomas Morin <thomas.morin@rd.francetelecom.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <73565.1137000602.1@juniper.net>
Date: Wed, 11 Jan 2006 09:30:02 -0800
From: Yakov Rekhter <yakov@juniper.net>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 97adf591118a232206bdb5a27b217034
Cc: L3VPN <l3vpn@ietf.org>
Subject: Re: WG last call: draft-ietf-l3vpn-ppvpn-mcast-reqts-03 
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: l3vpn.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:l3vpn@ietf.org>
List-Help: <mailto:l3vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=subscribe>
Sender: l3vpn-bounces@ietf.org
Errors-To: l3vpn-bounces@ietf.org

Thomas,

> Hi Yakov, folks,
>
> Yakov Rekhter:
> > I suggest to add the following to either 5.1.5 or 5.2.7:
> >
> >    For security reasons service providers may want to confine
> >    direct control traffic exchange among the providers to a combination
> >    of ASBRs (or even a subset of ASBRs) that connect the providers,
> >    and (optionally) a designated set of BGP Route Reflectors.
> >    For one thing, doing this would allow to MD5-key all control
> >    traffic exchanges among providers, while confining MD5 key
> >    administration to just the ASBRs (or even a subset of ASBRs),
> >    and Route Reflectors.
>
> I suggest adding the following atfer penultimate sentence of 5.2.7,
> rephrased as follows:
> "It is RECOMMENDED that corresponding procedures require the least
> possible coordination between providers; more specificaly when specific
> configurations or cryptographic keys have to be deployed, this shall be
> limited to ASBRs (Autonomous Systems Border Routers) or a subset of
> them, and optionnaly BGP Route Reflectors (or a subset of them)."
>
> ("corresponding procedures" refers to "means to ensure the integrity and
> authenticity of multicast-related exchanges across inter-ASes or
> inter-provider borders")
>
> I think this respect the initial idea, but without making any assumption
> on the implementation.  What do you think?

That would be fine.

Yakov.




From l3vpn-bounces@ietf.org Sun Jan 15 11:40:04 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EyAvE-0001qt-6A; Sun, 15 Jan 2006 11:40:04 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EyAtj-0001Fp-Nu
	for l3vpn@megatron.ietf.org; Sun, 15 Jan 2006 11:38:31 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA13674
	for <l3vpn@ietf.org>; Sun, 15 Jan 2006 10:39:32 -0500 (EST)
Received: from colo-dns-ext2.juniper.net ([207.17.137.64])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EyA7Z-0007by-3G
	for l3vpn@ietf.org; Sun, 15 Jan 2006 10:48:49 -0500
Received: from merlot.juniper.net (merlot.juniper.net [172.17.27.10])
	by colo-dns-ext2.juniper.net (8.12.3/8.12.3) with ESMTP id
	k0FFeG1Z017361
	for <l3vpn@ietf.org>; Sun, 15 Jan 2006 07:40:18 -0800 (PST)
	(envelope-from yakov@juniper.net)
Received: from juniper.net (sapphire.juniper.net [172.17.28.108])
	by merlot.juniper.net (8.11.3/8.11.3) with ESMTP id k0FFeF583898;
	Sun, 15 Jan 2006 07:40:15 -0800 (PST)
	(envelope-from yakov@juniper.net)
Message-Id: <200601151540.k0FFeF583898@merlot.juniper.net>
To: Ron Bonica <rbonica@juniper.net>
In-Reply-To: Your message of "Wed, 04 Jan 2006 09:51:01 EST."
	<43BBE0D5.2060607@juniper.net> 
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <14289.1137339615.1@juniper.net>
Date: Sun, 15 Jan 2006 07:40:15 -0800
From: Yakov Rekhter <yakov@juniper.net>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 1ac7cc0a4cd376402b85bc1961a86ac2
Cc: l3vpn@ietf.org
Subject: Re: WG last call: draft-ietf-l3vpn-ppvpn-mcast-reqts-03 
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: l3vpn.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:l3vpn@ietf.org>
List-Help: <mailto:l3vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=subscribe>
Sender: l3vpn-bounces@ietf.org
Errors-To: l3vpn-bounces@ietf.org

Ron,

> Folks,
> 
> This email initiates a WG last call for
> draft-ietf-l3vpn-ppvpn-mcast-reqts-03. Last call ends Jan 19, 2006.

In 5.1.7 I would suggest to add the following to the bullet list:

      A solution must allow to control an extranet multicast 
      connectivity independently from the extranet unicast 
      connectivity

Yakov.




From l3vpn-bounces@ietf.org Sun Jan 15 13:03:00 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EyCCL-000733-Pf; Sun, 15 Jan 2006 13:01:49 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EyC9f-0004fE-86
	for l3vpn@megatron.ietf.org; Sun, 15 Jan 2006 12:59:03 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA00345
	for <l3vpn@ietf.org>; Sun, 15 Jan 2006 11:16:02 -0500 (EST)
From: benjamin.niven-jenkins@bt.com
Received: from smtp1.smtp.bt.com ([217.32.164.137])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Exoqo-0006B2-Ae
	for l3vpn@ietf.org; Sat, 14 Jan 2006 12:06:02 -0500
Received: from i2kc07-ukbr.domain1.systemhost.net ([193.113.197.14]) by
	smtp1.smtp.bt.com with Microsoft SMTPSVC(6.0.3790.211); 
	Sat, 14 Jan 2006 16:58:03 +0000
Received: from i2km86-ukdy.domain1.systemhost.net ([193.113.30.79]) by
	i2kc07-ukbr.domain1.systemhost.net with Microsoft
	SMTPSVC(6.0.3790.211); Sat, 14 Jan 2006 16:58:03 +0000
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Sat, 14 Jan 2006 16:58:24 -0000
Message-ID: <F5AAFD21F2034349BF638211B5F27B0F063A51D3@i2km86-ukdy.domain1.systemhost.net>
Thread-Topic: Review of draft-ietf-l3vpn-ppvpn-mcast-reqts-03
Thread-Index: AcYZK7sfy0mt1uHUSauPYA23WJJXRA==
To: <l3vpn@ietf.org>
X-OriginalArrivalTime: 14 Jan 2006 16:58:03.0364 (UTC)
	FILETIME=[AECDAA40:01C6192B]
X-Spam-Score: 0.3 (/)
X-Scan-Signature: b045c2b078f76b9f842d469de8a32de3
Content-Transfer-Encoding: quoted-printable
Subject: Review of draft-ietf-l3vpn-ppvpn-mcast-reqts-03
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: l3vpn.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:l3vpn@ietf.org>
List-Help: <mailto:l3vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=subscribe>
Sender: l3vpn-bounces@ietf.org
Errors-To: l3vpn-bounces@ietf.org

Colleagues,

I have started to review draft-ietf-l3vpn-ppvpn-mcast-reqts-03,
unfortunately due to other commitments I have only had time to get as
far as section 5.1.9 (and appendix A as far as the requirements in
section 5.1.9) and I won't have time for several weeks to review the
rest of the document.

Anyway, here are my comments and suggestions so far.  I have formatted
my e-mail as RTF so that I can highlight my proposed changes.  Deletions
are shown as strikethrough and additions are in bold.

General - The document appears to use L3VPN, L3 VPN, PP L3VPN and L3
PPVPN interchangeably.  I would suggest standardising on either one term
(say L3VPN) or two terms if the fact the VPN is provider provisioned
needs to be emphasied (say L3VPN and PPL3VPN).

Section 1:
1st paragraph: "VPN services satisfying the requirement defined in" and
"need not be aware of the VPN"

4th paragraph: "It clarifies the needs from of both VPN clients and
providers standpoints and formulates the problems that should be
addressed by technical solutions with as a the key objective being to
stay remain solution agnostic."

Section 2.1:
2nd paragraph: "Moreover we also propose here generic terms for concepts
that naturally appears when multicast in VPNs is discussed."

3rd paragraph: The definition of ASM isn't very helpful.  Maybe a more
descriptive definition of what ASM actuall is would be helpful.

4th paragraph: "whose core architecture supports"

8th paragraph: "multicast traffic will be conveyed transported across
the SP network.  This is meant in a generic way: such tunnels can be
either point-to-point or point-to-multipoint.  Although this definition
may seems to assume that distribution tunnels are unidirectional, but
the wording also encompasses bi-directional tunnels as well."

11th paragraph: "Refers to any network device that not only participates
to constitutes part of the deployment and the contributes to the
maintenance of the VPN"

Section 3.1:
4th paragraph: "(that is, with a scalable impact"

Section 3.2:
1st paragraph: Suggest changing favor for characteristics.

Section 3.3
1st paragraph: "since the latter is likely to requires maintaining"

Section 4:
2nd paragraph: "Most of the content of these sections"

The text as it stand implies to me that the deployments it talks about
are expected in summer 2005, is that correct, or was it that the survey
was done in summer 2005.  If it's the latter I would suggest rewording
the first sentence as follows: "Most of the content of these sections
originates from a survey done in summer 2005 among institutions and
providers that expect to deploy such solutions, in summer 2005."

3rd paragraph: "expressed in only in a few"

Section 4.1:
1st paragraph, 1st line: "mutlicast" =3D> "multicast" and "can be done
over"

2nd paragraph: "to impact most of the design"

Section 4.1.1:
1st paragraph: "A tTypical applications are"

4th bullet: "can be as high as hundreds"

5th bullet: "bandwidth will depend on the application, but may vary
between a few tens/hundreds of Kb/s"

6th bullet: "QoS requirements include"

8th bullet: "delay sensitivity will depend on the applications"

9th bullet: I don't think you mean "capillarity", I think you mean
"capability"

Section 4.1.2:
Title: "Symetric" =3D> "Symmetric"

2nd paragraph: "Theyir are characterisedtics is by the relatively"

4th paragraph: "it may significantly impact a lot how the
bandwidth/state is managed, because of:"

2nd bullet: "and possibly significantly"

5th paragraph: "indicate that oOptimizing bandwidth for this case may
require"

6th paragraph: "Lastly, some of these applications may involve"

Section 4.1.3:
1st paragraph: "multicast VPNs are non-realtime applications aimeding at
distributing data from a few sources and to many receivers."

Section 4.2:
1st paragraph: "scope to the mere current deployments"

Section 4.2.1:
1st paragraph: "we see an broad range"

Section 4.2.2:
2nd paragraph: "have to scale up to thousands of VPNs per PE."

Section 4.2.3:
2nd paragraph: "A solution SHOULD thus support"

Section 4.2.4:
1st paragraph: "number of PEs per multicast VPNs in"

Section 4.2.4.1:
1st paragraph: "The number of PEs, per VPNs, that would be connected to
sources, seems to be significantly lower than the number of PEs per
VPNs. This is obviously related to the fact that many respondents
mentioned"

Section 4.2.4.2:
1st paragraph: "same order of magnitude than as the number"

Section 4.2.5:
1st paragraph: "A solution SHOULD scale up to thousands of PEs having
multicast service enabled." This reads like a requirement but I can't
find it in the summary of requirements in appendix A.

Section 5:
2nd paragraph: "have taken two different the standpoints of two"

3rd paragraph: "document, we mean by "a solution" or "a multicast VPN
solution", we mean a solution that allows to perform multicast in an L3"

Section 5.1.1:
1st paragraph: "SHALL NOT require customer's devices (CEs) to".  These
edits also need to be made to the copy of the requirement in Appendix A.

Section 5.1.2:
1st paragraph: "Consequently to Section 3.1, the CEs and PEs CE-PE
protocol SHOULD employ existing multicast protocols." These edits also
need to be made to the copy of the requirement in Appendix A.  Also do
you really mean to refer to Section 3.1?

Section 5.1.3:
1st paragraph: "Firstly, the general considerations about regarding QoS
in L3 VPNs as developed described in section"

2nd paragraph: "In some cases, provided the agreed SLA may be different
between unicast and multicast, which will need service differentiation
mechanisms as such in order to monitor both SLAs."

3rd paragraph: "For instance the same traffic"

4th paragraph: "A multicast in VPN solution shall allow to define at
least the same level of quality of service than what as exists for
unicast, and than what as exists for multicast in a non-VPN context."
Also, who shall define the level of QoS, the provider?  In which case I
suggest "A multicast in VPN solution shall allow an ISP to define"

5th paragraph: "the solution should" should the should be in capitals.
Is this paragraph a requirement that also needs to be included in
appendix A?

7th paragraph: "is close to the bandwidth of a PE-CE link"

8th paragraph: "Lastly, a multicast VPN"


Section 5.1.4:
2nd paragraph: "which MAY possibly rely upon similar techniques (than to
those used by the unicast for unicast the same monitoring purposes)."

Section 5.1.5:
2nd bullet: "(when multiple CEs of a in the same VPN"

Section 5.1.6:

3rd paragraph: Suggest rewording/reorganising as follows: "The
monitoring of multicast specific parameters and statistics SHOULD MUST
include :

   o  multicast traffic statistics: total traffic conveyed, incoming,
      outgoing, dropped, etc., by period of time (as a MUST)

The monitoring of multicast specific parameters and statistics MAY
include=20
   o  IP Performance Metrics related information (IPPM, [RFC2330]) that
      is relevant to the multicast traffic usage: such information
      includes the one-way packet delay, the inter-packet delay
      variation, etc. (as a MAY)"

4th paragraph: "if their usage exceeds the agreed bounds". These edits
also need to be made to the copy of the requirement in Appendix A.

Section 5.1.7:
5th paragraph: "participating to in a BGP/MPLS"

Section 5.1.8:
1st paragraph: "somehow fits in the context"

2nd paragraph: "It should be considered OPTIONAL given the additional
considerations, such as security, needed to fulfill the requirements for
providing Internet Multicast side, such as security treatment."


Section 5.1.9:
1st paragraph: "and VRs [I-D.ietf-l3vpn-vpn-vr] define the "Carrier's
Carrier" model, where a "carrier's carrier" service provider supports
one or more customer ISPs, or "sub-carriers"."

3rd paragraph: "such as BGP/MPLS VPNs [I-D.ietf-l3vpn-rfc2547bis], this
means that some MPLS label distribution" to align it weith the
requirement in appendix A.

Appendix A:
Security requirements, 1st bullet: "same level of security both for both
unicast"

Extranet requirements, 1st bullet: "MUST support deployments where VRFs
or VRs are"


--=20
Ben Niven-Jenkins
Network Architect, BT Exact
 =20
E-mail: benjamin.niven-jenkins@bt.com=20
Office: +44 (0)1473 648225
Mobile: +44 (0)7918 077205
   Fax: +44 (0)1332 578827




From l3vpn-bounces@ietf.org Sun Jan 15 13:38:00 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EyClM-0001pJ-Sr; Sun, 15 Jan 2006 13:38:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EyAjW-0006Kc-9f
	for l3vpn@megatron.ietf.org; Sun, 15 Jan 2006 11:27:58 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA02543
	for <l3vpn@ietf.org>; Sun, 15 Jan 2006 11:23:13 -0500 (EST)
Received: from netcore.fi ([193.94.160.1])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ExmSH-0005CU-Er
	for l3vpn@ietf.org; Sat, 14 Jan 2006 09:32:34 -0500
Received: from netcore.fi (localhost [127.0.0.1])
	by netcore.fi (8.12.8/8.12.8) with ESMTP id k0EEOSYG001750
	for <l3vpn@ietf.org>; Sat, 14 Jan 2006 16:24:28 +0200
Received: from localhost (pekkas@localhost)
	by netcore.fi (8.12.8/8.12.8/Submit) with ESMTP id k0EEORVw001747
	for <l3vpn@ietf.org>; Sat, 14 Jan 2006 16:24:28 +0200
Date: Sat, 14 Jan 2006 16:24:27 +0200 (EET)
From: Pekka Savola <pekkas@netcore.fi>
To: l3vpn@ietf.org
Message-ID: <Pine.LNX.4.64.0601141618060.1639@netcore.fi>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-Virus-Scanned: ClamAV 0.87.1/1240/Fri Jan 13 18:57:12 2006 on otso.netcore.fi
X-Virus-Status: Clean
X-Spam-Status: No, score=-1.4 required=5.0 tests=ALL_TRUSTED autolearn=failed 
	version=3.1.0
X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on otso.netcore.fi
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b8f3559805f7873076212d6f63ee803e
X-Mailman-Approved-At: Sun, 15 Jan 2006 13:37:58 -0500
Subject: comments on draft-ietf-l3vpn-ppvpn-mcast-reqts-03
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: l3vpn.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:l3vpn@ietf.org>
List-Help: <mailto:l3vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=subscribe>
Sender: l3vpn-bounces@ietf.org
Errors-To: l3vpn-bounces@ietf.org

Hi,

On MBONED WG, folks were asked to take a look at 
draft-ietf-l3vpn-ppvpn-mcast-reqts-03, so here goes.

>From the external point of view, what's the relation to 
draft-ietf-l2vpn-vpls-mcast-reqts-xx?  It'd seem to me that it'd be 
HIGHLY desirable that at least the bulk of the solutions used could be 
the same...  Operators shouldn't need to deploy two completely 
different solutions for both L2 and L3VPNs.


more or less substantial comments
---------------------------------

5.1.2.  CE-PE Multicast routing and management protocols

    When IPv6 is supported by a VPN solution, relevant IPv6 corresponding
    protocols MUST also be supported, e.g.  Multicast Listener Discovery
    Protocol (MLD) (v1 [RFC2710]], v2 [RFC3810]]).

==> The IPv6 part requires wordsmithing.  The IETF will *NOT* allow 
specification of a standards track solution which does not support 
IPv6.  This text seems to imply that IPv6 support could be optional.

(you might also clarify which IGMP/MLD versions should be supported 
and which not.)

5.1.3.  Quality of Service (QoS)

....

    As multicast is often used to deliver high quality services such as
    TV broadcast, the solution should have additional features to support
    high QoS such as bandwidth reservation and admission control.

==> are these available for unicast?  Seems like you're asking more of a
multicast solution than from unicast.  I'd remove these kind of
"nice-to-have" reqs, or rephrase s/should/MAY/


5.1.11.  RP Engineering

    When PIM-SM (or bidir-PIM) is used in ASM mode on the VPN customer
    side, the location of the RP has to be chosen.  In some cases this
    engineering problem is not trivial: for instance, if sources and
    receivers are located in VPN sites that are different than that of
    the RP, then traffic may flow twice through the SP network and the
    CE-PE link of the RP (from source to RP, and then from RP to
    receivers) ; this is obviously not ideal.  A multicast VPN solution
    SHOULD propose a way to help on solving this RP engineering issue.

==> I'm not sure if this specific problem exists in practice.  If the 
RP sends Register-Stop, the multicast traffic is forwarded natively, 
and the data will short-cut inside the site without going to the RP 
and then back.  I.e., there should not be two times traffic once the 
forwarding is native.

5.1.13.  Minimum MTU

...

    It SHOULD also be compatible with Path MTU discovery mechanisms, such
    as those defined in [RFC1191] or [I-D.mathis-frag-harmful].

==> you may be interested in looking at 
draft-savola-mtufrag-network-tunneling-05.txt which was just recently 
approved for publication.  Depending on the MDT solution, this may 
have relevant discussion on MTU handling methods.

    For MDTunnels (multicast distribution tunnels, the means used to
    carry VPNs' multicast traffic over the provider's network), a
    solution SHOULD be able to use a range of tunneling technologies,
    including point-to-point and point-to-multipoint, such as GRE
    [RFC2784] (including GRE in multicast IP trees), MPLS [RFC3031]
    (including P2P or MP2P tunnels, and multipoint tunnels signaled with
    MPLS P2MP extensions to RSVP [I-D.ietf-mpls-rsvp-te-p2mp] or LDP
    [I-D.leroux-mpls-mp-ldp-reqs][I-D.minei-wijnands-mpls-ldp-p2mp]),
    L2TP (including L2TP for multicast [RFC4045]), IPsec [RFC2401], IP-
    in-IP [RFC1853], etc.

==> you should probably also a) specify, or b) require that the 
solution will specify one or two mandatory to implement tunneling 
mechanisms, so that there would be ways how MDTunnels between 
different vendors, operators, etc. could be interoperable..?

5.2.10.  Architectural Considerations

    As far as possible, the design of a solution should carefully
    consider the number of protocols within the core network.  If any
    additional protocols are introduced compared with unicast VPN, the
    balance between their advantage and operation burden should be
    examined thoroughly.

==> these are not "Architectural Considerations", maybe rather 
Operational Considerations, IMHO.  Let's take an example:  ISP is 
unicast-only and solution A proposed using standards-track multicast 
protocols to offer a service, and solution B would imply reinventing 
multicast signalling inside the unicast protocols.

In my opinion, solution A is clear architecturally a best solution.  The
above paragraph makes this sound like B would be favorable from the
*architectural* point-of-view.  Perhaps this section needs to be generalized
to bring out the different tradeoffs better, for example:
  - the benefits of using existing multicast technologies
  - the drawbacks of deploying the existing multicast technologies
  - the benefits of shorning multicast protocols into commonly deployed unicast
    protocols
  - the drawbacks of reinventing the wheel
  - etc.

editorial
---------

==> you should add a dummy IANA considerations section

    Service management should also include the TMN 'FCAPS'
    functionalities, as follows: Fault, Configuration, Accounting,
    Provisioning, and Security.

==> 'P' stands for Performance, I think.

    Resiliency is also crucial to infrastructure security, thus a
    multicast VPN solution SHOULD whether avoid single points of failures
    or propose some technical solution making possible to implement a
    fail-over mechanism.

==> s/whether/either/

    All or part of this information SHOULD be made available through
    standardized SNMP ([RFC1157]) MIBs (Management Information Base).

==> 1157 is no longer standardized, as it has been made Historic.  Refer to
the later SNMPv2/SNMPv3 RFCs?

    [RFC1853]  Simpson, W., "IP in IP Tunneling", RFC 1853, October 1995.

==> you should probably use RFC2003 instead, as RFC1853 just informational
while 2003 is standards track.


    [RFC3978]  Bradner, S., "IETF Rights in Contributions", BCP 78,
               RFC 3978, March 2005.

    [RFC2026]  Bradner, S., "The Internet Standards Process -- Revision
               3", BCP 9, RFC 2026, October 1996.

   [RFC2629]  Rose, M., "Writing I-Ds and RFCs using XML", RFC 2629,
               June 1999.

==> these are not referred to in the body of the draft (when the document
gets published by the RFC editor), so they can be removed.
(not sure if there are more of these)

8.2.  Informative references

    [RFC2547]  Rosen, E. and Y. Rekhter, "BGP/MPLS VPNs", RFC 2547,
               March 1999.

    [I-D.ietf-l3vpn-rfc2547bis]
               Rosen, E., "BGP/MPLS IP VPNs",
               draft-ietf-l3vpn-rfc2547bis-03 (work in progress),
               October 2004.

    [I-D.ietf-l3vpn-vpn-vr]
               Knight, P., Ould-Brahim, H., and B. Gleeson, "Network
               based IP VPN Architecture using Virtual Routers",
               draft-ietf-l3vpn-vpn-vr-02 (work in progress), April 2004.

==> these and many more are referred to in so many places of the drafts in a
very normative way, and should really be under the normative references. 
Some others as well -- please consider each with the following question in
mind:

  - is reading this reference required to understand this document?
    (rather than providing some optional additional information)
  - if the reference changed radically before publication, would this
    document need to be reflected as well?

If either of these is a "yes", then the reference should likely be
normative.

....

Appendix A.  Requirements summary

==> I'd consider removing this, because these should be extractable from the
body of the document, and these could get out of date easily if the editors
are not really, really careful.  Recent xml2rfc includes support for some
degree of autogeneration of these using xref format=title  (see RFC 3871 appendix A for
example)


-- 
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 l3vpn-bounces@ietf.org Mon Jan 16 06:47:53 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EySq1-0002mo-5T; Mon, 16 Jan 2006 06:47:53 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EySq0-0002m0-0r; Mon, 16 Jan 2006 06:47:52 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA05796;
	Mon, 16 Jan 2006 06:46:27 -0500 (EST)
Received: from mgw1.noc.ntt.com ([210.163.32.68])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1EySxs-0005Ri-Fq; Mon, 16 Jan 2006 06:56:03 -0500
Received: from mop3.noc.ntt.com
	by mgw1.noc.ntt.com (NTT-Com MailSV) with ESMTP id k0GBlKEK003684;
	Mon, 16 Jan 2006 20:47:20 +0900 (JST)
Received: from mip1.noc.ntt.com (mvi2.noc.ntt.com)
	by mop3.noc.ntt.com (NTT-Com MailSV) with ESMTP id
	<0IT600E2YOQWK1@ntt.com>; Mon, 16 Jan 2006 20:47:20 +0900 (JST)
Date: Mon, 16 Jan 2006 20:47:19 +0900
From: "Yuji KAMITE" <y.kamite@ntt.com>
In-reply-to: <Pine.LNX.4.64.0601141618060.1639@netcore.fi>
To: "'Pekka Savola'" <pekkas@netcore.fi>, l3vpn@ietf.org
Message-id: <0IT600L90OQV14@ntt.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1506
X-Mailer: Microsoft Office Outlook, Build 11.0.6353
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7bit
Thread-index: AcYaAuKQoIGwvXeXQeuJaZmJhWBsqQAhWS0g
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2a9ffb6f997442a3b543bcdaf483b990
Content-Transfer-Encoding: 7bit
Cc: l2vpn@ietf.org
Subject: RE: comments on draft-ietf-l3vpn-ppvpn-mcast-reqts-03
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: l3vpn.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:l3vpn@ietf.org>
List-Help: <mailto:l3vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=subscribe>
Sender: l3vpn-bounces@ietf.org
Errors-To: l3vpn-bounces@ietf.org

Hi Pekka,

> >From the external point of view, what's the relation to
> draft-ietf-l2vpn-vpls-mcast-reqts-xx?  It'd seem to me that 
> it'd be HIGHLY desirable that at least the bulk of the 
> solutions used could be the same...  Operators shouldn't need 
> to deploy two completely different solutions for both L2 and L3VPNs.

Yes,  it is definitely worth considering common viewpoints,
which would give us good opportunities to take similar approaches.
That's why l2vpn mcast requriment tries to borrow some l3vpn reqt's wording
and ideas that has common points (Actually l3vpn work item was preceding
l2vpn a little recently).

However, that's not enough yet.  Most other parts are needed to be
considered spearately in detail because they are dealing with different
layer protocols.  In l3vpn, there are lots of IP routing layer consideration, that is 
not needed in l2vpn, while l3vpn does not need to MAC address consideration.
We should avoid having just too generic and vague requirements.

Regards,

-Yuji


> -----Original Message-----
> From: l3vpn-bounces@ietf.org [mailto:l3vpn-bounces@ietf.org] 
> On Behalf Of Pekka Savola
> Sent: Saturday, January 14, 2006 11:24 PM
> To: l3vpn@ietf.org
> Subject: comments on draft-ietf-l3vpn-ppvpn-mcast-reqts-03
> 
> Hi,
> 
> On MBONED WG, folks were asked to take a look at 
> draft-ietf-l3vpn-ppvpn-mcast-reqts-03, so here goes.
> 
> >From the external point of view, what's the relation to
> draft-ietf-l2vpn-vpls-mcast-reqts-xx?  It'd seem to me that 
> it'd be HIGHLY desirable that at least the bulk of the 
> solutions used could be the same...  Operators shouldn't need 
> to deploy two completely different solutions for both L2 and L3VPNs.
> 
> 
> more or less substantial comments
> ---------------------------------
> 
> 5.1.2.  CE-PE Multicast routing and management protocols
> 
>     When IPv6 is supported by a VPN solution, relevant IPv6 
> corresponding
>     protocols MUST also be supported, e.g.  Multicast 
> Listener Discovery
>     Protocol (MLD) (v1 [RFC2710]], v2 [RFC3810]]).
> 
> ==> The IPv6 part requires wordsmithing.  The IETF will *NOT* 
> allow specification of a standards track solution which does 
> not support IPv6.  This text seems to imply that IPv6 support 
> could be optional.
> 
> (you might also clarify which IGMP/MLD versions should be 
> supported and which not.)
> 
> 5.1.3.  Quality of Service (QoS)
> 
> ....
> 
>     As multicast is often used to deliver high quality 
> services such as
>     TV broadcast, the solution should have additional 
> features to support
>     high QoS such as bandwidth reservation and admission control.
> 
> ==> are these available for unicast?  Seems like you're 
> asking more of a multicast solution than from unicast.  I'd 
> remove these kind of "nice-to-have" reqs, or rephrase s/should/MAY/
> 
> 
> 5.1.11.  RP Engineering
> 
>     When PIM-SM (or bidir-PIM) is used in ASM mode on the VPN customer
>     side, the location of the RP has to be chosen.  In some cases this
>     engineering problem is not trivial: for instance, if sources and
>     receivers are located in VPN sites that are different than that of
>     the RP, then traffic may flow twice through the SP network and the
>     CE-PE link of the RP (from source to RP, and then from RP to
>     receivers) ; this is obviously not ideal.  A multicast 
> VPN solution
>     SHOULD propose a way to help on solving this RP engineering issue.
> 
> ==> I'm not sure if this specific problem exists in practice. 
>  If the RP sends Register-Stop, the multicast traffic is 
> forwarded natively, and the data will short-cut inside the 
> site without going to the RP and then back.  I.e., there 
> should not be two times traffic once the forwarding is native.
> 
> 5.1.13.  Minimum MTU
> 
> ...
> 
>     It SHOULD also be compatible with Path MTU discovery 
> mechanisms, such
>     as those defined in [RFC1191] or [I-D.mathis-frag-harmful].
> 
> ==> you may be interested in looking at 
> draft-savola-mtufrag-network-tunneling-05.txt which was just 
> recently approved for publication.  Depending on the MDT 
> solution, this may have relevant discussion on MTU handling methods.
> 
>     For MDTunnels (multicast distribution tunnels, the means used to
>     carry VPNs' multicast traffic over the provider's network), a
>     solution SHOULD be able to use a range of tunneling technologies,
>     including point-to-point and point-to-multipoint, such as GRE
>     [RFC2784] (including GRE in multicast IP trees), MPLS [RFC3031]
>     (including P2P or MP2P tunnels, and multipoint tunnels 
> signaled with
>     MPLS P2MP extensions to RSVP [I-D.ietf-mpls-rsvp-te-p2mp] or LDP
>     [I-D.leroux-mpls-mp-ldp-reqs][I-D.minei-wijnands-mpls-ldp-p2mp]),
>     L2TP (including L2TP for multicast [RFC4045]), IPsec 
> [RFC2401], IP-
>     in-IP [RFC1853], etc.
> 
> ==> you should probably also a) specify, or b) require that 
> the solution will specify one or two mandatory to implement 
> tunneling mechanisms, so that there would be ways how 
> MDTunnels between different vendors, operators, etc. could be 
> interoperable..?
> 
> 5.2.10.  Architectural Considerations
> 
>     As far as possible, the design of a solution should carefully
>     consider the number of protocols within the core network.  If any
>     additional protocols are introduced compared with unicast VPN, the
>     balance between their advantage and operation burden should be
>     examined thoroughly.
> 
> ==> these are not "Architectural Considerations", maybe 
> rather Operational Considerations, IMHO.  Let's take an 
> example:  ISP is unicast-only and solution A proposed using 
> standards-track multicast protocols to offer a service, and 
> solution B would imply reinventing multicast signalling 
> inside the unicast protocols.
> 
> In my opinion, solution A is clear architecturally a best 
> solution.  The above paragraph makes this sound like B would 
> be favorable from the
> *architectural* point-of-view.  Perhaps this section needs to 
> be generalized to bring out the different tradeoffs better, 
> for example:
>   - the benefits of using existing multicast technologies
>   - the drawbacks of deploying the existing multicast technologies
>   - the benefits of shorning multicast protocols into 
> commonly deployed unicast
>     protocols
>   - the drawbacks of reinventing the wheel
>   - etc.
> 
> editorial
> ---------
> 
> ==> you should add a dummy IANA considerations section
> 
>     Service management should also include the TMN 'FCAPS'
>     functionalities, as follows: Fault, Configuration, Accounting,
>     Provisioning, and Security.
> 
> ==> 'P' stands for Performance, I think.
> 
>     Resiliency is also crucial to infrastructure security, thus a
>     multicast VPN solution SHOULD whether avoid single points 
> of failures
>     or propose some technical solution making possible to implement a
>     fail-over mechanism.
> 
> ==> s/whether/either/
> 
>     All or part of this information SHOULD be made available through
>     standardized SNMP ([RFC1157]) MIBs (Management Information Base).
> 
> ==> 1157 is no longer standardized, as it has been made 
> Historic.  Refer to the later SNMPv2/SNMPv3 RFCs?
> 
>     [RFC1853]  Simpson, W., "IP in IP Tunneling", RFC 1853, 
> October 1995.
> 
> ==> you should probably use RFC2003 instead, as RFC1853 just 
> informational while 2003 is standards track.
> 
> 
>     [RFC3978]  Bradner, S., "IETF Rights in Contributions", BCP 78,
>                RFC 3978, March 2005.
> 
>     [RFC2026]  Bradner, S., "The Internet Standards Process 
> -- Revision
>                3", BCP 9, RFC 2026, October 1996.
> 
>    [RFC2629]  Rose, M., "Writing I-Ds and RFCs using XML", RFC 2629,
>                June 1999.
> 
> ==> these are not referred to in the body of the draft (when 
> the document gets published by the RFC editor), so they can 
> be removed.
> (not sure if there are more of these)
> 
> 8.2.  Informative references
> 
>     [RFC2547]  Rosen, E. and Y. Rekhter, "BGP/MPLS VPNs", RFC 2547,
>                March 1999.
> 
>     [I-D.ietf-l3vpn-rfc2547bis]
>                Rosen, E., "BGP/MPLS IP VPNs",
>                draft-ietf-l3vpn-rfc2547bis-03 (work in progress),
>                October 2004.
> 
>     [I-D.ietf-l3vpn-vpn-vr]
>                Knight, P., Ould-Brahim, H., and B. Gleeson, "Network
>                based IP VPN Architecture using Virtual Routers",
>                draft-ietf-l3vpn-vpn-vr-02 (work in progress), 
> April 2004.
> 
> ==> these and many more are referred to in so many places of 
> the drafts in a very normative way, and should really be 
> under the normative references. 
> Some others as well -- please consider each with the 
> following question in
> mind:
> 
>   - is reading this reference required to understand this document?
>     (rather than providing some optional additional information)
>   - if the reference changed radically before publication, would this
>     document need to be reflected as well?
> 
> If either of these is a "yes", then the reference should 
> likely be normative.
> 
> ....
> 
> Appendix A.  Requirements summary
> 
> ==> I'd consider removing this, because these should be 
> extractable from the body of the document, and these could 
> get out of date easily if the editors are not really, really 
> careful.  Recent xml2rfc includes support for some degree of 
> autogeneration of these using xref format=title  (see RFC 
> 3871 appendix A for
> example)
> 
> 
> -- 
> 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 l3vpn-bounces@ietf.org Mon Jan 16 08:13:42 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EyUB4-0000wv-TC; Mon, 16 Jan 2006 08:13:42 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EyUB1-0000un-0C
	for l3vpn@megatron.ietf.org; Mon, 16 Jan 2006 08:13:40 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA11342
	for <l3vpn@ietf.org>; Mon, 16 Jan 2006 08:12:13 -0500 (EST)
Received: from p-mail2.rd.francetelecom.com ([195.101.245.16])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EyUIs-0008Tn-Or
	for l3vpn@ietf.org; Mon, 16 Jan 2006 08:21:50 -0500
Received: from ftrdmel10.rd.francetelecom.fr ([10.193.117.156]) by
	ftrdsmtp1.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.211); 
	Mon, 16 Jan 2006 14:13:31 +0100
Received: from l-at8613.rd.francetelecom.fr ([10.193.15.78]) by
	ftrdmel10.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.211); 
	Mon, 16 Jan 2006 14:13:31 +0100
From: Thomas Morin <thomas.morin@rd.francetelecom.com>
To: Marshall Eubanks <marshall.eubanks@gmail.com>
In-Reply-To: <dcad22d80601102236u373871a7qb6f7636e5b7bbfcd@mail.gmail.com>
References: <43BBE0D5.2060607@juniper.net>
	<dcad22d80601102236u373871a7qb6f7636e5b7bbfcd@mail.gmail.com>
Content-Type: text/plain; charset=iso-8859-13
Organization: France Telecom R&D
Date: Mon, 16 Jan 2006 14:13:19 +0100
Message-Id: <1137417200.15352.113.camel@wintermute>
Mime-Version: 1.0
X-Mailer: Evolution 2.4.2.1 
Content-Transfer-Encoding: quoted-printable
X-OriginalArrivalTime: 16 Jan 2006 13:13:31.0401 (UTC)
	FILETIME=[A5B6BF90:01C61A9E]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d437399464e10b52abe9a34ed7e712d0
Content-Transfer-Encoding: quoted-printable
Cc: l3vpn@ietf.org
Subject: Re: WG last call: draft-ietf-l3vpn-ppvpn-mcast-reqts-03
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: l3vpn.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:l3vpn@ietf.org>
List-Help: <mailto:l3vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=subscribe>
Sender: l3vpn-bounces@ietf.org
Errors-To: l3vpn-bounces@ietf.org

Hi Marshall,

Marshall Eubanks:
> As my first attempt bounced, you can find my comments and corrections
> on this document at
>=20
> http://www.americafree.tv/papers/draft-ietf-l3vpn-ppvpn-mcast-reqts-03-tm=
e.txt
>=20
> I gave this document a careful read. In my opinion there are a bunch of m=
ostly
> minor things that need to be corrected before it passes last call.

Thank you for your review and all your relevant comments, there are very
appreciated.

See below for comments to some of your suggestions or questions, and the
changes I propose to address them.  I integrated "as is" (or mostly "as
is") all of your others comments, which were definitely reasonable.

Cheers,

-Thomas





>    VRF or VR: By this phrase, we refer to the entity defined in a PE
>       dedicated to a specific VPN instance.  "VRF" refers to [RFC2547]
>       terminology, and "VR" to the VR [I-D.ietf-l3vpn-vpn-vr]
>       terminology.
>=20
> tme> I have read this several times and still don't know what "entity" is=
 being referred
> tme> to.
> tme> VR =3D=3D "Virtual Router"
> tme> VRF =3D=3D "Virtual Routing and Forwarding table"
> tme> This phrase is used 4 times, not counting here. The next is
> tme>=20
> tme> Moreover, the activation of multicast features SHOULD be possible:
> tme>    o  with a VRF or VR granularity
> tme> This is not really clear either.
> tme> Does it mean, for each routing table, or each entry on the routing t=
able ?
> tme> Note that VRF and VR are both used separately
> tme>=20
> tme> Here is a stab at a definition
> tme>
> tme> VRF or VR: By this phrase, we refer to the finest scale multicast ro=
uting=20
> tme> information available, as maintained by the Virtual Router (VR, see =
[I-D.ietf-l3vpn-vpn-vr])
> tme> or the Virtual Routing and Forwarding table (VRF, see [2547bis])


Well, a VRF is a routing table (not an entry), and a VR (virtual router)
is somehow of the same level (contains protocol routing instance, and
routing tables).

So, here is the wording I propose to avoid any confusion:

"By this phrase, we refer to the entity defined in a PE dedicated to a
specific VPN instance. "VRF" refers to "VPN Routing and Forwarding
table" as defined in [I-D.ietf-l3vpn-rfc2547bis], and "VR" to "Virtual
Router" as defined in  [I-D.ietf-l3vpn-vpn-vr] terminology."

Moreover, I reworded section in 5.1.5:
"Moreover, the activation of multicast features SHOULD be possible:
      * per VRF / per VR
      * per CE interface (when multiple CE of a same VPN are connected
        to a common VRF/VR)
      * per multicast group and/or per channel
      * with a distinction between multicast reception and emission"

[about section 3.3]
> tme> Why isn't is a general requirement to interoperate with existing _mu=
lticast_
> tme> deployments ?  rfc4021 says little about multicast - shouldn't this =
be explicit ?

Well the idea is to highlight the focus : in a VPN deployment context,
one of the most crucial requirement is to cohabit with the existing
service (unicast VPN).

You are right in the sense that deploying a multicast VPN solution
should nicely cohabit with existing deployment of multicast on P and PE
routers, and on CE routers. =20

I added two sentences:
- in 5.1.1:  "Enabling a VPN for multicast support SHOULD be possible
with no (or very limited impact) on existing multicast protocols
possibly already deployed on the CE devices."
- in 5.2 : "The deployment of a multicast VPN solution SHOULD be
possible with no (or very limited) impact on possibly existing
deployments of multicast protocols on P and PE routers."

Would that be ok ?
=20
>    o  some of these applications may involve rapid changes in customer
>       multicast memberships, but this will depend on audience and
>       capillarity of provider equipments
>=20
> tme> "capillarity" is a very obscure English word, and I do not know what=
 is meant here.
> tme> could this be a typo for "capabilities" ?

No typo, but maybe the use of this term is less common in english than
"capilarit'e" is in french... :)  We sometime use it metaphorically to
refer to the number of small elements at the periphery of something,
like leaves of a tree, with the image of capillary vessels in lungs for
instance.

I rephrased as: "some of these applications may involve rapid changes in
customer multicast memberships as seen by the PE, but this will depend
on audience patterns and on the number of provider equipments deployed
close to VPN customers".

> 4.1.2.  Symetric applications
>=20
> tme> nit : s/Symetric/ Symmetric /
>=20
>    Some use cases exposed by the survey can be grouped under this label,
>    and include many-to-many applications such as conferencing, clusters
>    monitoring.
>=20
> tme> (relative) nit : I do not know what "clusters monitoring" means in t=
his context.
> tme> Is this for entities like beowulf clusters over VPN's ?=20
> tme> An extra word to explain this would help.

Survey responses did not include such a level of detail, so I can only gues=
s here.
I rephrased as: "server clusters monitoring".=20


> 4.2.2.  Number of multicast VPNs per PE
>=20
>    The majority of survey answers express a number of multicast VPNs per
>    PE of around tens (8 responses between 5 and 50); a significant
>    number of them (4) expect deployments with hundreds or thousands (1
>    response) of multicast VPNs per PE.
>=20
>    A solution SHOULD support a number of multicast VPNs per PE of
>    several hundreds, and may have to scale up to thousands VPNs per PE.
>=20
> tme> PE means "provider edge". Does this mean, number per edge location, =
or
> tme> number over all locations. I would suggest
> tme> s/scale up to thousands VPNs per PE/scale up to thousands VPNs per P=
E location/
>=20

RFC4026 "Provider Provisioned VPN Terminology" section 5.2 precisely
suggest the use of "PE" and "CE" to refer to the devices themselves.
That actually what we are used to do in l3vpn (for brievity).

I added the following in the terminology section:
" "Provider Edge", "Customer Edge" (as defined in [RFC4026](Andersson,
L. and T. Madsen, =B4Provider Provisioned Virtual Private Network (VPN)
Terminology,=A1 March 2005.)). As suggested in [RFC4026](Andersson, L. and
T. Madsen, =B4Provider Provisioned Virtual Private Network (VPN)
Terminology,=A1 March 2005.), we will use these notations to refer to the
equipments/routers/devices themselves. Thus, "PE" will refer to the
router on the provider's edge, which faces the "CE", the router on the
customer's edge. "


> 5.1.2.  CE-PE Multicast routing and management protocols
>
[snip]
>=20
> tme> Note that IGMP v3 and MLD v2 support means support for IGMP v1,v2 an=
d MLD v1
> tme> So, I would suggest :
>=20
> tme>   Among those protocols, the support of PIM-SM (version 2, revised, =
which
> tme>   includes SSM model) and either IGMP v.3 (for IPv4 solutions) and /=
 or=20
> tme>   MLD v.2 (for IPv6 solutions) are REQUIRED.

Agreed.
I also followed your implicit suggestion, by mentioning that hosts only
implementing -v1 and -v2 are implicitely supported by IGMPv3 queriers.


>    A multicast in VPN solution shall allow to define at least the same
> tme> nit : s/shall allow to define/SHALL allow definition of/

maybe "SHALL allow the definition of" ?


>    As multicast is often used to deliver high quality services such as
>    TV broadcast, the solution should have additional features to support
> tme> nit : s/should/SHOULD/
>    high QoS such as bandwidth reservation and admission control.

Since when is it MANDATORY to use CAPITALIZED version of those words ?
Here I fell it hard to use a strict wording, considering how precise the
rest of the sentence is.


>    The solution MUST support SLA monitoring capabilities, which MAY
>    possibly rely upon similar techniques (than those used by the unicast
>=20
> tme> I puzzled over this - I suggest
> tme> s/similar techniques (than/different techniques than/
>    for the same monitoring purposes).
> tme> s/)//

Ok, that one indeed may be puzzling ; "which MAY possibly rely upon
techniques similar to those used for the unicast service for the same
monitoring purposes"  will be better I guess.


> 5.1.8.  Internet Multicast
>=20
>    Connectivity with Internet Multicast (as a source or receiver)
>    somehow fits in the context of the previous section.
>=20
> tme> Is this a stub for missing text ? This must be filled out to pass la=
st call IMHO.

Well, this section was supposed to be complete, describing the
connectivity to/from Internet Multicast a similar to the connectivity
to/from another multicast VPN.

>=20
>    It should be considered OPTIONAL given additional considerations
>    needed to fulfill requirements for Internet side, such as security
>    treatment.
>
tme> Here is some text :
>
[snip]

The text you propose is I think partly redundant with section 5.1.7
"Extranet".  I would like to just put in this section things that are
specific to Internet Multicast connectivity (if there are any):
- MSDP might be one of these, though I'd suspect not : MSDP is only
inter-RP, so if no RP is deployed in VRF (acceptable), then no MSDP
requirement is relevant here ; and in any case, I don't see that we'd
need to state MSDP-related requirement for the overall architecture
(same for embbeded-RP)
- we may need to state MBGP-related requirement: I'm not sure precisely
what we should say, since anything a bit precise would require
articulation with what is expected for unicast Internet Connectivity in
such a case.

Maybe adding the following would be enough : "MBGP support in VRF/VR
would be REQUIRED if a Multicast VPN solution supports connectivity with
Internet Multicast. MSDP support in VRF/VR also is REQUIRED for such a
solution, if it supports the RP functionality in VRF/VR".

Would you agree ?

>    The use of globally unique means of multicast-based service
>    identification at the scale of the domain where such services are
>    provided SHOULD be recommended.  If the ASM model is used, this
>=20
> tme> SSM also has source scoping, 239/8 can be used with either SSM or AS=
M. Therefore
> tme> s/If the ASM model is used, this/For IPv4 multicasts, this/

I rephrased as follows:

"For IPv4 multicast, this implies the use of the multicast
administratively scoped range, (239/8 as defined by [RFC2365]) for
services which are to be used only inside the VPN, and of or SSM-range
addresses (232/8 as defined by [I-D.ietf-ssm-arch]) or globally assigned
group addresses (e.g. GLOP [RFC3180], 233/8) for services for which
traffic may be transmitted outside the VPN ."



> 5.1.13.  Minimum MTU
>=20
>    For customers, it is often a serious issue whether transmitted
>    packets will be fragmented or not.  In particular, some multicast
>    applications might have different requirements than those that make
>    use of unicast, and they may expect services that guarantee available
>    packet length not to be fragmented.
>=20
>    Therefore, a multicast VPN solution SHOULD let customers' devices be
>    free of any fragmentation or reassembly activity.
>=20
>    A committed minimum path MTU size SHOULD be provided to customers.
>    Moreover, since Ethernet LAN segments are often located at first and
>    last hops, a minimum 1500 bytes IP MTU SHOULD be provided.
>=20
> tme> There are a lot of tunnels used in multicast, and they tend to
> tme> restrict MTU's to a little below the 1500 coming from Ethernet
> tme> Are you really saying that no existing GRE or PPPoE or IP-IP multica=
st
>tme> tunnel can be used in multicast VPN architectures ? This seems extrem=
e.

tme> In fact, since these tunnel types are allowed in Section 5.2.3.1.,
> tme> I do not know how they can be implemented in most networks (unless
> tme> jumbo frames are used throughout).

Encapsulation that would limit the MTU is encapsulation between PE
routers.  Those are often mutually reachable with high troughput links,
such as GE w/ Jumbo Frames, POS... for which MTU can be easily made
above 1500 I think.

What we are saying only means that:
a) if tunneling is used, then the provider should be able to commit to a mi=
nimum MTU
b) is possible (SHOULD) this MTU should be 1500, because this is what
will require the less tuning of customer application (which we expect
can initialy be used inside a LAN, without tunnels)

Consequently:
- if the Multicast VPN solution doesn't meet b), then it doesn't meet
the "SHOULD" (which may be acceptable, as soon as there is a rationale
behind it)
- it the provider's network cannot meet b), then it is less good than if
it would

Thus, a multicast VNP solution requiring the use of GRE or or IP-IP
multicast for PE to PE tunnels is completely be acceptable:
- GRE or IP-IP, by itself, doesn't I think limit the MTU=20
- a provider network for which some PE-to-PE path go through a small MTU
interface (like a Fast Ethernet LAN interface) won't be able to meet
this requirement : this is not so common I think, and in any case that
may be acceptable (client will tell you)

PPPoE is intrinsicaly more limited, but I think nobody would like to use
it for PE-to-PE communication right ?

In anycase, nothing precludes any tunneling mechanism by itself, and
1500-byte minimal MTU is only a SHOULD.


> tme>
> tme> I would suggest either s/1500/1476/ or=20
> tme> s/1500 bytes/1500 bytes, including any necessary tunnel headers/
> tme> but the latter is sure to be confusing.

We talk about "1500 byte IP MTU", which refers to the minimum MTU made avai=
lable to the customer
(who doesn't "see" any tunnel).  Isn't this precise enough.

[section 5.2.1]
>=20
> tme> This seems garbled. Do you mean "point to point, point to multipoint=
",
> tme> or is the first "point" just a duplicate ? As a guess,
> tme> s/point/point to point,/
>=20
Yes, "point" is a duplicate.


>=20
> tme> again, this seems garbled. I think this is meant :
> tme>  s/leaves/leafs/


Hmm. Isn't "leaf" like "knife", "life", or "scarf" ?


>    Unwanted multicast traffic (e.g. multicast traffic that may be sent
>    by a source located somewhere in the Internet and for which there is
>    no interested receiver connected to a given VPN infrastructure) MUST
>    NOT be propagated within a multicast-enabled VPN.
>=20
> tme> Is this consistent with Section 5.2.2.3. ? It seems to me that this=20
> tme> should be a SHOULD NOT to allow for sub-optimal solutions


While it might be acceptable (for provider-side scalability) that some
traffic reaches a PE even if this is not needed, it would not be
acceptable that such traffic be propagated toward the CE, inside the
customer network.

Isn't this reasonable ?


>    As an illustration, one can consider the case of a solution that
>    would use PIM-SM as a means to setup MDTunnels.  In such a case, the
>    PIM RP might be a single point of failure.  Such a solution should
>    thus be compatible with a solution implementing RP resiliency.
>=20
> tme> s/./, such as is provided by anycast RP [draft-ietf-pim-anycast-rp-0=
4]./

I also added BSR, for completeness.









From l3vpn-bounces@ietf.org Mon Jan 16 08:50:08 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EyUkK-0002Ub-1c; Mon, 16 Jan 2006 08:50:08 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EyUkJ-0002UW-At
	for l3vpn@megatron.ietf.org; Mon, 16 Jan 2006 08:50:07 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA14058
	for <l3vpn@ietf.org>; Mon, 16 Jan 2006 08:48:42 -0500 (EST)
Received: from p-mail1.rd.francetelecom.com ([195.101.245.15])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EyUsE-0001m4-7k
	for l3vpn@ietf.org; Mon, 16 Jan 2006 08:58:19 -0500
Received: from ftrdmel10.rd.francetelecom.fr ([10.193.117.156]) by
	ftrdsmtp1.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.211); 
	Mon, 16 Jan 2006 14:49:50 +0100
Received: from l-at8613.rd.francetelecom.fr ([10.193.15.78]) by
	ftrdmel10.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.211); 
	Mon, 16 Jan 2006 14:49:51 +0100
From: Thomas Morin <thomas.morin@rd.francetelecom.com>
To: Yakov Rekhter <yakov@juniper.net>
In-Reply-To: <200601151540.k0FFeF583898@merlot.juniper.net>
References: <200601151540.k0FFeF583898@merlot.juniper.net>
Content-Type: text/plain
Organization: France Telecom R&D
Date: Mon, 16 Jan 2006 14:49:39 +0100
Message-Id: <1137419379.15352.143.camel@wintermute>
Mime-Version: 1.0
X-Mailer: Evolution 2.4.2.1 
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 16 Jan 2006 13:49:51.0587 (UTC)
	FILETIME=[B934BB30:01C61AA3]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25
Content-Transfer-Encoding: 7bit
Cc: l3vpn@ietf.org
Subject: Re: WG last call: draft-ietf-l3vpn-ppvpn-mcast-reqts-03
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: l3vpn.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:l3vpn@ietf.org>
List-Help: <mailto:l3vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=subscribe>
Sender: l3vpn-bounces@ietf.org
Errors-To: l3vpn-bounces@ietf.org

Hello Yakov,

Yakov Rekhter:
> In 5.1.7 I would suggest to add the following to the bullet list:
> 
>       A solution must allow to control an extranet multicast 
>       connectivity independently from the extranet unicast 
>       connectivity

Agreed.
I just used capitalized "MUST" instead of "must".

Cheers,

-Thomas





From l3vpn-bounces@ietf.org Mon Jan 16 10:36:57 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EyWPh-00079g-1c; Mon, 16 Jan 2006 10:36:57 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EyWPf-000786-OZ
	for l3vpn@megatron.ietf.org; Mon, 16 Jan 2006 10:36:55 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA21012
	for <l3vpn@ietf.org>; Mon, 16 Jan 2006 10:35:29 -0500 (EST)
Received: from p-mail2.rd.francetelecom.com ([195.101.245.16])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EyWXW-0006Rf-AI
	for l3vpn@ietf.org; Mon, 16 Jan 2006 10:45:05 -0500
Received: from ftrdmel10.rd.francetelecom.fr ([10.193.117.156]) by
	ftrdsmtp2.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.211); 
	Mon, 16 Jan 2006 16:36:41 +0100
Received: from l-at8613.rd.francetelecom.fr ([10.193.15.78]) by
	ftrdmel10.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.211); 
	Mon, 16 Jan 2006 16:36:40 +0100
From: Thomas Morin <thomas.morin@rd.francetelecom.com>
To: Pekka Savola <pekkas@netcore.fi>
In-Reply-To: <Pine.LNX.4.64.0601141618060.1639@netcore.fi>
References: <Pine.LNX.4.64.0601141618060.1639@netcore.fi>
Content-Type: text/plain
Organization: France Telecom R&D
Date: Mon, 16 Jan 2006 16:36:28 +0100
Message-Id: <1137425789.15352.214.camel@wintermute>
Mime-Version: 1.0
X-Mailer: Evolution 2.4.2.1 
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 16 Jan 2006 15:36:40.0972 (UTC)
	FILETIME=[A57F44C0:01C61AB2]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 3f3e54d3c03ed638c06aa9fa6861237e
Content-Transfer-Encoding: 7bit
Cc: l3vpn@ietf.org
Subject: Re: comments on draft-ietf-l3vpn-ppvpn-mcast-reqts-03
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: l3vpn.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:l3vpn@ietf.org>
List-Help: <mailto:l3vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=subscribe>
Sender: l3vpn-bounces@ietf.org
Errors-To: l3vpn-bounces@ietf.org

Hi Pekka,

Thank your for having reviewed the draft and for your comments.

Pekka Savola:
> 5.1.2.  CE-PE Multicast routing and management protocols
> 
>     When IPv6 is supported by a VPN solution, relevant IPv6 corresponding
>     protocols MUST also be supported, e.g.  Multicast Listener Discovery
>     Protocol (MLD) (v1 [RFC2710]], v2 [RFC3810]]).
> 
> ==> The IPv6 part requires wordsmithing.  The IETF will *NOT* allow 
> specification of a standards track solution which does not support 
> IPv6.  This text seems to imply that IPv6 support could be optional.

Well, the draft aims at being v4/v6 generic, and is not supposed to let
the reader think that IPv6 support is optional for a multicast VPN
solution.  It aims at saying that IPv6 multicast support is required for
a _VPN_solution_ (e.g. a unicast VPN solution like VR) that supports v6
and is extended to support multicast.

Maybe the text could be a little clearer, what about : 
"When a multicast VPN solution is built on a VPN solution supporting
IPv6 unicast, it MUST also support v6 variants of the above protocols,
including  MLD v.2, and PIM-SM IPv6 specific procedures."
?

And we can even push a little further: "For a multicast VPN solution not
built on a unicast VPN solution supporting IPv6, it is RECOMMENDED that
the design favors the definition of procedures and encodings that will
provide an easy adaptation to IPv6".



> 
> 5.1.3.  Quality of Service (QoS)
> 
> ....
> 
>     As multicast is often used to deliver high quality services such as
>     TV broadcast, the solution should have additional features to support
>     high QoS such as bandwidth reservation and admission control.
> 
> ==> are these available for unicast?  Seems like you're asking more of a
> multicast solution than from unicast.  I'd remove these kind of
> "nice-to-have" reqs, or rephrase s/should/MAY/

Well, I would argue that:
- things like this exist for unicast (think RSVP-TE tunnels between PEs)
- it is worded "should" not "SHOULD" : the wording of the rest of the
sentence is vague enough to no let us make a strict requirement


> 5.1.11.  RP Engineering
> 
>     When PIM-SM (or bidir-PIM) is used in ASM mode on the VPN customer
>     side, the location of the RP has to be chosen.  In some cases this
>     engineering problem is not trivial: for instance, if sources and
>     receivers are located in VPN sites that are different than that of
>     the RP, then traffic may flow twice through the SP network and the
>     CE-PE link of the RP (from source to RP, and then from RP to
>     receivers) ; this is obviously not ideal.  A multicast VPN solution
>     SHOULD propose a way to help on solving this RP engineering issue.
> 
> ==> I'm not sure if this specific problem exists in practice.  If the 
> RP sends Register-Stop, the multicast traffic is forwarded natively, 
> and the data will short-cut inside the site without going to the RP 
> and then back.  I.e., there should not be two times traffic once the 
> forwarding is native.

Well...
1) even such transient peaks may not be something that you'll want
2) what if you lose connectivity to the remote site hosting the RP, are
you happy to lose local multicast on every other site?
3) what if you want to stick with RPT ? 
   [okay, maybe not so relevant, but what if the VPN customer wants to
    do this ?]


> 5.1.13.  Minimum MTU
> 
> ...
> 
>     It SHOULD also be compatible with Path MTU discovery mechanisms, such
>     as those defined in [RFC1191] or [I-D.mathis-frag-harmful].
> 
> ==> you may be interested in looking at 
> draft-savola-mtufrag-network-tunneling-05.txt which was just recently 
> approved for publication.  Depending on the MDT solution, this may 
> have relevant discussion on MTU handling methods.

Thank you to provide this one: I was just looking for a
usefull-and-non-expired reference about MTU issues !  ;)

> 
>     For MDTunnels (multicast distribution tunnels, the means used to
>     carry VPNs' multicast traffic over the provider's network), a
>     solution SHOULD be able to use a range of tunneling technologies,
>     including point-to-point and point-to-multipoint, such as GRE
>     [RFC2784] (including GRE in multicast IP trees), MPLS [RFC3031]
>     (including P2P or MP2P tunnels, and multipoint tunnels signaled with
>     MPLS P2MP extensions to RSVP [I-D.ietf-mpls-rsvp-te-p2mp] or LDP
>     [I-D.leroux-mpls-mp-ldp-reqs][I-D.minei-wijnands-mpls-ldp-p2mp]),
>     L2TP (including L2TP for multicast [RFC4045]), IPsec [RFC2401], IP-
>     in-IP [RFC1853], etc.
> 
> ==> you should probably also a) specify, or b) require that the 
> solution will specify one or two mandatory to implement tunneling 
> mechanisms, so that there would be ways how MDTunnels between 
> different vendors, operators, etc. could be interoperable..?

Yes, it would indeed be nice.
Still, today its unclear which one we would chose as mandatory.



> 5.2.10.  Architectural Considerations
> 
>     As far as possible, the design of a solution should carefully
>     consider the number of protocols within the core network.  If any
>     additional protocols are introduced compared with unicast VPN, the
>     balance between their advantage and operation burden should be
>     examined thoroughly.
> 
> ==> these are not "Architectural Considerations", maybe rather 
> Operational Considerations, IMHO.  
[snip]

You are right.

I propose to move this sentence to previous section "Management tools,
OAM", at the end of the paragraph saying "The operation of a multicast
VPN solution SHALL be as light as possible and providing automatic
configuration and discovery SHOULD be prioritized. Particularly the
operational cost of setting up multicast on a PE SHOULD be as low as
possible.".


> editorial
> ---------
> 
> ==> you should add a dummy IANA considerations section

Sorry, to nit-pick, but where is it stated that all document should do
this ? (where is the MUST in RFC2434?). Since this would be particularly
irrelevant for a requirement document such as this one, I'd prefer not
adding one more paragraph...


>     Service management should also include the TMN 'FCAPS'
>     functionalities, as follows: Fault, Configuration, Accounting,
>     Provisioning, and Security.
> 
> ==> 'P' stands for Performance, I think.

Yep. That one is in fact already corrected in my copy.


> 
>     All or part of this information SHOULD be made available through
>     standardized SNMP ([RFC1157]) MIBs (Management Information Base).
> 
> ==> 1157 is no longer standardized, as it has been made Historic.  Refer to
> the later SNMPv2/SNMPv3 RFCs?

Agreed.

> 
>     [RFC1853]  Simpson, W., "IP in IP Tunneling", RFC 1853, October 1995.
> 
> ==> you should probably use RFC2003 instead, as RFC1853 just informational
> while 2003 is standards track.

Agreed.


> 
> 
>     [RFC3978]  Bradner, S., "IETF Rights in Contributions", BCP 78,
>                RFC 3978, March 2005.
> 
>     [RFC2026]  Bradner, S., "The Internet Standards Process -- Revision
>                3", BCP 9, RFC 2026, October 1996.
> 
>    [RFC2629]  Rose, M., "Writing I-Ds and RFCs using XML", RFC 2629,
>                June 1999.
> 
> ==> these are not referred to in the body of the draft (when the document
> gets published by the RFC editor), so they can be removed.


RFC2629 is referred to in the appendix
RFC3978 is BCP 78, referred to in IPR boilerplate

2026 actually is not referred to

> (not sure if there are more of these)

There were some, now fixed.


> 8.2.  Informative references
> 
>     [RFC2547]  Rosen, E. and Y. Rekhter, "BGP/MPLS VPNs", RFC 2547,
>                March 1999.
> 
>     [I-D.ietf-l3vpn-rfc2547bis]
>                Rosen, E., "BGP/MPLS IP VPNs",
>                draft-ietf-l3vpn-rfc2547bis-03 (work in progress),
>                October 2004.
> 
>     [I-D.ietf-l3vpn-vpn-vr]
>                Knight, P., Ould-Brahim, H., and B. Gleeson, "Network
>                based IP VPN Architecture using Virtual Routers",
>                draft-ietf-l3vpn-vpn-vr-02 (work in progress), April 2004.
> 
> ==> these and many more are referred to in so many places of the drafts in a
> very normative way, and should really be under the normative references. 
> Some others as well -- please consider each with the following question in
> mind:
> 
>   - is reading this reference required to understand this document?
>     (rather than providing some optional additional information)
>   - if the reference changed radically before publication, would this
>     document need to be reflected as well?
> 
> If either of these is a "yes", then the reference should likely be
> normative.

Agreed.


> 
> ....
> 
> Appendix A.  Requirements summary
> 
> ==> I'd consider removing this, because these should be extractable from the
> body of the document, and these could get out of date easily if the editors
> are not really, really careful.  Recent xml2rfc includes support for some
> degree of autogeneration of these using xref format=title  (see RFC 3871 appendix A for
> example)

Well, this was suggested by a reviewer, and I think it can be useful.
I am open to other inputs, it is true that is requires particular
care... its somehow a matter of benefit/risk trade-off.

(the feature you quote is interesting indeed, but looks only useful with
one requirement item per sub-section, and subsection title chosen to
match there use in the resulting summary...)

Cheers,

-Thomas





From l3vpn-bounces@ietf.org Mon Jan 16 11:42:41 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EyXRJ-0000tt-39; Mon, 16 Jan 2006 11:42:41 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EyXRH-0000to-FT
	for l3vpn@megatron.ietf.org; Mon, 16 Jan 2006 11:42:39 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA25983
	for <l3vpn@ietf.org>; Mon, 16 Jan 2006 11:41:15 -0500 (EST)
Received: from p-mail1.rd.francetelecom.com ([195.101.245.15])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EyXZE-0000tP-ES
	for l3vpn@ietf.org; Mon, 16 Jan 2006 11:50:53 -0500
Received: from ftrdmel10.rd.francetelecom.fr ([10.193.117.156]) by
	ftrdsmtp2.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.211); 
	Mon, 16 Jan 2006 17:42:31 +0100
Received: from l-at8613.rd.francetelecom.fr ([10.193.15.78]) by
	ftrdmel10.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.211); 
	Mon, 16 Jan 2006 17:42:31 +0100
From: Thomas Morin <thomas.morin@rd.francetelecom.com>
To: Pekka Savola <pekkas@netcore.fi>
In-Reply-To: <Pine.LNX.4.64.0601161745530.8385@netcore.fi>
References: <Pine.LNX.4.64.0601141618060.1639@netcore.fi>
	<1137425789.15352.214.camel@wintermute>
	<Pine.LNX.4.64.0601161745530.8385@netcore.fi>
Content-Type: text/plain
Organization: France Telecom R&D
Date: Mon, 16 Jan 2006 17:42:19 +0100
Message-Id: <1137429739.15352.271.camel@wintermute>
Mime-Version: 1.0
X-Mailer: Evolution 2.4.2.1 
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 16 Jan 2006 16:42:31.0279 (UTC)
	FILETIME=[D81047F0:01C61ABB]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7e439b86d3292ef5adf93b694a43a576
Content-Transfer-Encoding: 7bit
Cc: l3vpn@ietf.org
Subject: Re: comments on draft-ietf-l3vpn-ppvpn-mcast-reqts-03
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: l3vpn.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:l3vpn@ietf.org>
List-Help: <mailto:l3vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=subscribe>
Sender: l3vpn-bounces@ietf.org
Errors-To: l3vpn-bounces@ietf.org

Hi Pekka,

(inline)

Pekka Savola:
> >> ==> The IPv6 part requires wordsmithing.  The IETF will *NOT* allow
> >> specification of a standards track solution which does not support
> >> IPv6.  This text seems to imply that IPv6 support could be optional.
> >
> > Well, the draft aims at being v4/v6 generic, and is not supposed to let
> > the reader think that IPv6 support is optional for a multicast VPN
> > solution.  It aims at saying that IPv6 multicast support is required for
> > a _VPN_solution_ (e.g. a unicast VPN solution like VR) that supports v6
> > and is extended to support multicast.
> 
> Good point, I missed this nuance of the text because I assumed that 1) 
> all the existing VPN solutions already support IPv6 (is there one that 
> doesn't?) or 2) the multicast VPN solutions might not depend on 
> the unicast VPN solutions.

Well, AFAIK, IPv6 support for PPVPN solution seems to be more the
exception than the rule: v6 support is in l3vpn charter,
draft-ietf-l3vpn-bgp-ipv6 is in "IESG Evaluation" state. Dunno about VR.


> > Maybe the text could be a little clearer, what about :
> > "When a multicast VPN solution is built on a VPN solution supporting
> > IPv6 unicast, it MUST also support v6 variants of the above protocols,
> > including  MLD v.2, and PIM-SM IPv6 specific procedures."
> > ?
> >
> > And we can even push a little further: "For a multicast VPN solution not
> > built on a unicast VPN solution supporting IPv6, it is RECOMMENDED that
> > the design favors the definition of procedures and encodings that will
> > provide an easy adaptation to IPv6".
> 
> Are there standards track unicast VPN solutions that don't support 
> IPv6?  If not, the language could probably be greatly simplified. If 
> yes, let me summon a lynching party... ;-)

See above.


> >> 5.1.3.  Quality of Service (QoS)
> >> ....
> >>
> >>     As multicast is often used to deliver high quality services such as
> >>     TV broadcast, the solution should have additional features to support
> >>     high QoS such as bandwidth reservation and admission control.
> >>
> >> ==> are these available for unicast?  Seems like you're asking more of a
> >> multicast solution than from unicast.  I'd remove these kind of
> >> "nice-to-have" reqs, or rephrase s/should/MAY/
> >
> > Well, I would argue that:
> > - things like this exist for unicast (think RSVP-TE tunnels between PEs)
> > - it is worded "should" not "SHOULD" : the wording of the rest of the
> > sentence is vague enough to no let us make a strict requirement
> 
> I do not know RSVP-TE well enough to know whether this is true or not, 
> but at least my impression is that even RSVP-TE does not support (at 
> least) _admission control_ (that seems something you'll need to set up 
> first).

RSVP-TE does admission control on its path.

>   Certainly not in such a manner that it would be visible to 
> the VPN sites at least?

True.

But if the provider does RSVP-TE (in its core) for the P2MP tunnels used
by his clients, that may will be an advantage for QoS related aspects.


> In other documents, lower-case keywords may sometimes be interpreted 
> as even stronger than uppercase, so unless the unicast mechanisms 
> really exist and have bene widely deployed, I'd still suggest a MAY or 
> rewording.

Ok, this would avoid any ambiguity: "a multicast VPN solution MAY
provide additional features [...]".


> >> 5.1.11.  RP Engineering
> >>
> >>     When PIM-SM (or bidir-PIM) is used in ASM mode on the VPN customer
> >>     side, the location of the RP has to be chosen.  In some cases this
> >>     engineering problem is not trivial: for instance, if sources and
> >>     receivers are located in VPN sites that are different than that of
> >>     the RP, then traffic may flow twice through the SP network and the
> >>     CE-PE link of the RP (from source to RP, and then from RP to
> >>     receivers) ; this is obviously not ideal.  A multicast VPN solution
> >>     SHOULD propose a way to help on solving this RP engineering issue.
> >>
> >> ==> I'm not sure if this specific problem exists in practice.  If the
> >> RP sends Register-Stop, the multicast traffic is forwarded natively,
> >> and the data will short-cut inside the site without going to the RP
> >> and then back.  I.e., there should not be two times traffic once the
> >> forwarding is native.
> >
> > Well...
> > 1) even such transient peaks may not be something that you'll want
> > 2) what if you lose connectivity to the remote site hosting the RP, are
> > you happy to lose local multicast on every other site?
> > 3) what if you want to stick with RPT ?
> >   [okay, maybe not so relevant, but what if the VPN customer wants to
> >    do this ?]
> 
> I should have been more specific.  I agree that the "RP engineering" 
> problem exists: deciding where to put the RP has many different 
> tradeoffs to consider -- there isn't a one-size-fits-all approach.
> 
> I was commenting on the double traffic issue specifically, 1) above. 
> I don't think it really exists for valid configurations.  RPs tend to 
> send Register-Stop *immediately* so you shouldn't see even a transient 
> peak (longer than less than a second that is) due to this.

Sorry, but isn't "a second" (even a very short one), transient ? 
Also, what does "immediately" mean (especially across a multicast VPN
and a provider core) ?



> >> editorial
> >> ---------
> >>
> >> ==> you should add a dummy IANA considerations section
> >
> > Sorry, to nit-pick, but where is it stated that all document should do
> > this ? (where is the MUST in RFC2434?). Since this would be particularly
> > irrelevant for a requirement document such as this one, I'd prefer not
> > adding one more paragraph...
> 
> That's a rather recent addition, so it isn't in any RFC, but it can be 
> found here:
> 
> http://www.ietf.org/ID-Checklist.html (see Changelog under Revision 
> 0.4)

Okay then. :)


> >
> > RFC2629 is referred to in the appendix
> > RFC3978 is BCP 78, referred to in IPR boilerplate
> 
> But RFC3978/BCP78 hasn't been referred in [square brackets], and 
> moreover, this is a bit against the spirit (as this is a _symbolic_ 
> reference) of ID-Checklist section 2.1 point:
> 
> "7. Do not add a numbered reference in the I-D boilerplate to RFC 3978 
> or RFC 3979 (or to RFC 2026, RFC 3667 or RFC 3668 for older 
> documents). If you do, it makes it harder for the RFC editor to 
> process the document when they strip off the I-D boilerplate."
> 
> In any case, the reference would be stripped off when publishing as 
> RFC, so...

Okay then.








From l3vpn-bounces@ietf.org Mon Jan 16 11:42:45 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EyXRN-0000vz-NF; Mon, 16 Jan 2006 11:42:45 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EyXRM-0000um-0c
	for l3vpn@megatron.ietf.org; Mon, 16 Jan 2006 11:42:44 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA25997
	for <l3vpn@ietf.org>; Mon, 16 Jan 2006 11:41:19 -0500 (EST)
Received: from p-mail2.rd.francetelecom.com ([195.101.245.16])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EyXZG-0000tZ-Es
	for l3vpn@ietf.org; Mon, 16 Jan 2006 11:50:57 -0500
Received: from ftrdmel10.rd.francetelecom.fr ([10.193.117.156]) by
	ftrdsmtp1.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.211); 
	Mon, 16 Jan 2006 17:42:36 +0100
Received: from l-at8613.rd.francetelecom.fr ([10.193.15.78]) by
	ftrdmel10.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.211); 
	Mon, 16 Jan 2006 17:42:36 +0100
From: Thomas Morin <thomas.morin@rd.francetelecom.com>
To: Pekka Savola <pekkas@netcore.fi>
In-Reply-To: <Pine.LNX.4.64.0601161745530.8385@netcore.fi>
References: <Pine.LNX.4.64.0601141618060.1639@netcore.fi>
	<1137425789.15352.214.camel@wintermute>
	<Pine.LNX.4.64.0601161745530.8385@netcore.fi>
Content-Type: text/plain
Organization: France Telecom R&D
Date: Mon, 16 Jan 2006 17:42:24 +0100
Message-Id: <1137429744.15352.273.camel@wintermute>
Mime-Version: 1.0
X-Mailer: Evolution 2.4.2.1 
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 16 Jan 2006 16:42:36.0107 (UTC)
	FILETIME=[DAF0F9B0:01C61ABB]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228
Content-Transfer-Encoding: 7bit
Cc: Adrian Farrel <adrian@olddog.co.uk>, l3vpn@ietf.org
Subject: Re: comments on draft-ietf-l3vpn-ppvpn-mcast-reqts-03
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: l3vpn.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:l3vpn@ietf.org>
List-Help: <mailto:l3vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=subscribe>
Sender: l3vpn-bounces@ietf.org
Errors-To: l3vpn-bounces@ietf.org

Hi folks,

Pekka Savola:
> >> Appendix A.  Requirements summary
> >>
> >> ==> I'd consider removing this, because these should be extractable from the
> >> body of the document, and these could get out of date easily if the editors
> >> are not really, really careful.  Recent xml2rfc includes support for some
> >> degree of autogeneration of these using xref format=title  (see RFC 3871 appendix A for
> >> example)
> >
> 
> > Well, this was suggested by a reviewer, and I think it can be useful.
> > I am open to other inputs, it is true that is requires particular
> > care... its somehow a matter of benefit/risk trade-off.
> >
> > (the feature you quote is interesting indeed, but looks only useful with
> > one requirement item per sub-section, and subsection title chosen to
> > match there use in the resulting summary...)
> 
> I'm OK with leaving it in if that's what the WG thinks is appropriate. 
> However, the document is already pretty long, and any means to reduce 
> the length should be considered.

Anyone opinion on this is welcome...
I can live without the burden of updating this "Requirements summary"
section, but I would also understand if people that find it useful ask
for keeping it: raise your voice if you are one of them.

-Thomas





From l3vpn-bounces@ietf.org Mon Jan 16 13:28:24 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EyZ5c-0006Eh-KI; Mon, 16 Jan 2006 13:28:24 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EyZ5b-0006EV-5E
	for l3vpn@megatron.ietf.org; Mon, 16 Jan 2006 13:28:23 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA04486
	for <l3vpn@ietf.org>; Mon, 16 Jan 2006 13:26:58 -0500 (EST)
Received: from sj-iport-3-in.cisco.com ([171.71.176.72]
	helo=sj-iport-3.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1EyZDX-0004jW-BH
	for l3vpn@ietf.org; Mon, 16 Jan 2006 13:36:37 -0500
Received: from sj-core-1.cisco.com ([171.71.177.237])
	by sj-iport-3.cisco.com with ESMTP; 16 Jan 2006 10:28:12 -0800
X-IronPort-AV: i="3.99,373,1131350400"; 
	d="scan'208"; a="392290931:sNHT34408596"
Received: from cisco.com (cypher.cisco.com [171.69.11.142])
	by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id k0GISBQi016366;
	Mon, 16 Jan 2006 10:28:11 -0800 (PST)
Received: from [5.18.5.101] (sjc-vpn6-1091.cisco.com [10.21.124.67])
	by cisco.com (8.8.8-Cisco List Logging/8.8.8) with ESMTP id KAA12881;
	Mon, 16 Jan 2006 10:28:11 -0800 (PST)
In-Reply-To: <1137419379.15352.143.camel@wintermute>
References: <200601151540.k0FFeF583898@merlot.juniper.net>
	<1137419379.15352.143.camel@wintermute>
Mime-Version: 1.0 (Apple Message framework v746.2)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <2F7ADC25-9746-4E1E-A947-871761CC4C6D@cisco.com>
Content-Transfer-Encoding: 7bit
From: Yiqun Cai <ycai@cisco.com>
Date: Mon, 16 Jan 2006 10:28:01 -0800
To: Thomas Morin <thomas.morin@rd.francetelecom.com>
X-Mailer: Apple Mail (2.746.2)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4d87d2aa806f79fed918a62e834505ca
Content-Transfer-Encoding: 7bit
Cc: Yakov Rekhter <yakov@juniper.net>, l3vpn@ietf.org
Subject: Re: WG last call: draft-ietf-l3vpn-ppvpn-mcast-reqts-03
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: l3vpn.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:l3vpn@ietf.org>
List-Help: <mailto:l3vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=subscribe>
Sender: l3vpn-bounces@ietf.org
Errors-To: l3vpn-bounces@ietf.org

Yakov,  Thomas,

I have some doubt regarding this.

By "extranet multicast connectivity",  do you mean procedure of RPF  
to the
source,  the distribution of multicast data traffic to the receivers  
in different
VPNs, or something else.

Multicast RPF is built based on unicast routing information.  So  
there is a
dependancy existing today.  A solution does provide more flexibility  
if it allows
RPF to be independent of unicast routing,  but I dont see it as a  
"must".

For distribution of multicast data,  since they are controlled by  
join/prune
messages,  they are independent of unicast data distribution in nature.
So I don't see how this bullet is applicable.

If it is something else,  could you please elaborate?

Thanks a lot.

On Jan 16, 2006, at 5:49 AM, Thomas Morin wrote:

> Hello Yakov,
>
> Yakov Rekhter:
>> In 5.1.7 I would suggest to add the following to the bullet list:
>>
>>       A solution must allow to control an extranet multicast
>>       connectivity independently from the extranet unicast
>>       connectivity
>
> Agreed.
> I just used capitalized "MUST" instead of "must".
>
> Cheers,
>
> -Thomas
>
>



--
Yiqun






From l3vpn-bounces@ietf.org Mon Jan 16 15:42:52 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EybBk-0004IG-Hm; Mon, 16 Jan 2006 15:42:52 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EybBi-0004IB-Nl
	for l3vpn@megatron.ietf.org; Mon, 16 Jan 2006 15:42:50 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA13750
	for <l3vpn@ietf.org>; Mon, 16 Jan 2006 15:41:25 -0500 (EST)
Received: from smtp12.wanadoo.fr ([193.252.22.20])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EybJh-0001TK-B5
	for l3vpn@ietf.org; Mon, 16 Jan 2006 15:51:06 -0500
Received: from me-wanadoo.net (localhost [127.0.0.1])
	by mwinf1201.wanadoo.fr (SMTP Server) with ESMTP id 14EE11C0007A
	for <l3vpn@ietf.org>; Mon, 16 Jan 2006 21:42:27 +0100 (CET)
Received: from home.treizh.net (ARennes-252-1-57-189.w83-195.abo.wanadoo.fr
	[83.195.248.189])
	by mwinf1201.wanadoo.fr (SMTP Server) with ESMTP id 00CC11C00050
	for <l3vpn@ietf.org>; Mon, 16 Jan 2006 21:42:27 +0100 (CET)
X-ME-UUID: 20060116204227338.00CC11C00050@mwinf1201.wanadoo.fr
Received: from [192.168.0.3] (unknown [192.168.0.3])
	by home.treizh.net (Postfix) with ESMTP id 8BDEE31116
	for <l3vpn@ietf.org>; Mon, 16 Jan 2006 21:42:26 +0100 (CET)
From: Thomas Morin <thomas.morin@rd.francetelecom.com>
To: L3VPN <l3vpn@ietf.org>
Content-Type: text/plain
Organization: France Telecom R&D
Date: Mon, 16 Jan 2006 21:38:12 +0100
Message-Id: <1137443892.20451.10.camel@wintermute>
Mime-Version: 1.0
X-Mailer: Evolution 2.4.2.1 
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 79899194edc4f33a41f49410777972f8
Content-Transfer-Encoding: 7bit
Subject: Update to draft-ietf-l3vpn-ppvpn-mcast-reqts
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: l3vpn.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:l3vpn@ietf.org>
List-Help: <mailto:l3vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=subscribe>
Sender: l3vpn-bounces@ietf.org
Errors-To: l3vpn-bounces@ietf.org

Hi folks,

I just posted version -04 of the draft.
(http://tools.ietf.org/wg/l3vpn/draft-ietf-l3vpn-ppvpn-mcast-reqts/
should soon provide you a nice HTML diff).

It is not meant to be a definitive version: a few things are still
discussed, and the requirement summary needs to be updated (or removed,
depending on how people feel).

So this is just so that people can read an updated revision and can
avoid repeating comments/corrections/nits already made.

Thank you to read this new one,

-Thomas








From l3vpn-bounces@ietf.org Mon Jan 16 21:27:50 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EygZa-00064W-Kp; Mon, 16 Jan 2006 21:27:50 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EygZY-00064O-Et
	for l3vpn@megatron.ietf.org; Mon, 16 Jan 2006 21:27:48 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA05680
	for <l3vpn@ietf.org>; Mon, 16 Jan 2006 21:26:22 -0500 (EST)
Received: from zproxy.gmail.com ([64.233.162.204])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EyghY-0006t0-4n
	for l3vpn@ietf.org; Mon, 16 Jan 2006 21:36:07 -0500
Received: by zproxy.gmail.com with SMTP id 9so1254198nzo
	for <l3vpn@ietf.org>; Mon, 16 Jan 2006 18:27:42 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
	h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=gRfYwqCVBptdI1aRdDfFTjKFd4aP8+joLpXoJ7iqBzKpa4Ob7WTnAGDkDOrXs0PJTiEMtC2IvOEYwD2UwwCshfEzZKF8Z1ei98CER9Bn62tnjb7G4J6HUfUIwiLJGK9SKWdFn1b/Hx61Jd+Ir+yComXl55RF7hri6zFiE4GClv0=
Received: by 10.36.224.12 with SMTP id w12mr898032nzg;
	Mon, 16 Jan 2006 18:27:42 -0800 (PST)
Received: by 10.36.46.2 with HTTP; Mon, 16 Jan 2006 18:27:42 -0800 (PST)
Message-ID: <dcad22d80601161827y7617a56aqa267b1219f1a8218@mail.gmail.com>
Date: Mon, 16 Jan 2006 21:27:42 -0500
From: Marshall Eubanks <marshall.eubanks@gmail.com>
To: Yiqun Cai <ycai@cisco.com>
In-Reply-To: <2F7ADC25-9746-4E1E-A947-871761CC4C6D@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <200601151540.k0FFeF583898@merlot.juniper.net>
	<1137419379.15352.143.camel@wintermute>
	<2F7ADC25-9746-4E1E-A947-871761CC4C6D@cisco.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 41c17b4b16d1eedaa8395c26e9a251c4
Content-Transfer-Encoding: quoted-printable
Cc: Yakov Rekhter <yakov@juniper.net>,
	Thomas Morin <thomas.morin@rd.francetelecom.com>, l3vpn@ietf.org
Subject: Re: WG last call: draft-ietf-l3vpn-ppvpn-mcast-reqts-03
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: l3vpn.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:l3vpn@ietf.org>
List-Help: <mailto:l3vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=subscribe>
Sender: l3vpn-bounces@ietf.org
Errors-To: l3vpn-bounces@ietf.org

Hello;

On 1/16/06, Yiqun Cai <ycai@cisco.com> wrote:
> Yakov,  Thomas,
>
> I have some doubt regarding this.
>
> By "extranet multicast connectivity",  do you mean procedure of RPF
> to the
> source,  the distribution of multicast data traffic to the receivers
> in different
> VPNs, or something else.
>
> Multicast RPF is built based on unicast routing information.  So
> there is a
> dependancy existing today.  A solution does provide more flexibility
> if it allows
> RPF to be independent of unicast routing,  but I dont see it as a
> "must".
>

For intra domain, I would agree. For interdomain multicast, MBGP allows for
different unicast and multicast routing topologies, and that would need
to be preserved.

As I read this, extranet means a situation where different unicast and
multicast routing topologies are likely, and thus I think that the
bullet is needed.

Regards
Marshall

> For distribution of multicast data,  since they are controlled by
> join/prune
> messages,  they are independent of unicast data distribution in nature.
> So I don't see how this bullet is applicable.
>
> If it is something else,  could you please elaborate?
>
> Thanks a lot.
>
> On Jan 16, 2006, at 5:49 AM, Thomas Morin wrote:
>
> > Hello Yakov,
> >
> > Yakov Rekhter:
> >> In 5.1.7 I would suggest to add the following to the bullet list:
> >>
> >>       A solution must allow to control an extranet multicast
> >>       connectivity independently from the extranet unicast
> >>       connectivity
> >
> > Agreed.
> > I just used capitalized "MUST" instead of "must".
> >
> > Cheers,
> >
> > -Thomas
> >
> >
>
>
>
> --
> Yiqun
>
>
>
>




From l3vpn-bounces@ietf.org Mon Jan 16 21:36:24 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Eyghs-0008IN-Oi; Mon, 16 Jan 2006 21:36:24 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Eyghq-0008I3-R6
	for l3vpn@megatron.ietf.org; Mon, 16 Jan 2006 21:36:22 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA06389
	for <l3vpn@ietf.org>; Mon, 16 Jan 2006 21:34:56 -0500 (EST)
Received: from zproxy.gmail.com ([64.233.162.206])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Eygpq-0007Ce-N4
	for l3vpn@ietf.org; Mon, 16 Jan 2006 21:44:41 -0500
Received: by zproxy.gmail.com with SMTP id 9so1255365nzo
	for <l3vpn@ietf.org>; Mon, 16 Jan 2006 18:36:19 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
	h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=VyJfC5HDRe58JL+OFwiKL8+TiJxGFu8dpiSg7NfXJ1Y+6pxCDbkUYm8PbGCHRvvom5aNFCyWs39WSQMUlEGYPPCVQd05CiIJoW11KaddhuaPWaNC39Ye+XG9h9RrhjQ5uQvurIsVCPHf7LqA5pA1bnnl/fB55ERo9d8+n9pa7Zo=
Received: by 10.36.49.12 with SMTP id w12mr5313923nzw;
	Mon, 16 Jan 2006 18:36:18 -0800 (PST)
Received: by 10.36.46.2 with HTTP; Mon, 16 Jan 2006 18:36:18 -0800 (PST)
Message-ID: <dcad22d80601161836u4783b79m5d59cb06cb374f07@mail.gmail.com>
Date: Mon, 16 Jan 2006 21:36:18 -0500
From: Marshall Eubanks <marshall.eubanks@gmail.com>
To: Thomas Morin <thomas.morin@rd.francetelecom.com>
In-Reply-To: <1137417200.15352.113.camel@wintermute>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <43BBE0D5.2060607@juniper.net>
	<dcad22d80601102236u373871a7qb6f7636e5b7bbfcd@mail.gmail.com>
	<1137417200.15352.113.camel@wintermute>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: dfc64cf6e4c6efdbf6b8f4c995df04df
Content-Transfer-Encoding: quoted-printable
Cc: l3vpn@ietf.org
Subject: Re: WG last call: draft-ietf-l3vpn-ppvpn-mcast-reqts-03
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: l3vpn.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:l3vpn@ietf.org>
List-Help: <mailto:l3vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=subscribe>
Sender: l3vpn-bounces@ietf.org
Errors-To: l3vpn-bounces@ietf.org

Hello;

I will read and respond when possible.

Two quick comments before breakfast  :

> Since when is it MANDATORY to use CAPITALIZED version of those words ?
> Here I fell it hard to use a strict wording, considering how precise the
> rest of the sentence is.
>
As it says,

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in RFC-2119.

I believe that the capitalization is required to trigger the RFC-2119
interpretations.

And, I have never seen  "capillarity" actually used in English. It's
in the dictionary, even in my spell checker, and it might be used in
botany, but it's not used metaphorically.

Regards
Marshall


On 1/16/06, Thomas Morin <thomas.morin@rd.francetelecom.com> wrote:
> Hi Marshall,
>
> Marshall Eubanks:
> > As my first attempt bounced, you can find my comments and corrections
> > on this document at
> >
> > http://www.americafree.tv/papers/draft-ietf-l3vpn-ppvpn-mcast-reqts-03-=
tme.txt
> >
> > I gave this document a careful read. In my opinion there are a bunch of=
 mostly
> > minor things that need to be corrected before it passes last call.
>
> Thank you for your review and all your relevant comments, there are very
> appreciated.
>
> See below for comments to some of your suggestions or questions, and the
> changes I propose to address them.  I integrated "as is" (or mostly "as
> is") all of your others comments, which were definitely reasonable.
>
> Cheers,
>
> -Thomas
>
>
>
>
>
> >    VRF or VR: By this phrase, we refer to the entity defined in a PE
> >       dedicated to a specific VPN instance.  "VRF" refers to [RFC2547]
> >       terminology, and "VR" to the VR [I-D.ietf-l3vpn-vpn-vr]
> >       terminology.
> >
> > tme> I have read this several times and still don't know what "entity" =
is being referred
> > tme> to.
> > tme> VR =3D=3D "Virtual Router"
> > tme> VRF =3D=3D "Virtual Routing and Forwarding table"
> > tme> This phrase is used 4 times, not counting here. The next is
> > tme>
> > tme> Moreover, the activation of multicast features SHOULD be possible:
> > tme>    o  with a VRF or VR granularity
> > tme> This is not really clear either.
> > tme> Does it mean, for each routing table, or each entry on the routing=
 table ?
> > tme> Note that VRF and VR are both used separately
> > tme>
> > tme> Here is a stab at a definition
> > tme>
> > tme> VRF or VR: By this phrase, we refer to the finest scale multicast =
routing
> > tme> information available, as maintained by the Virtual Router (VR, se=
e [I-D.ietf-l3vpn-vpn-vr])
> > tme> or the Virtual Routing and Forwarding table (VRF, see [2547bis])
>
>
> Well, a VRF is a routing table (not an entry), and a VR (virtual router)
> is somehow of the same level (contains protocol routing instance, and
> routing tables).
>
> So, here is the wording I propose to avoid any confusion:
>
> "By this phrase, we refer to the entity defined in a PE dedicated to a
> specific VPN instance. "VRF" refers to "VPN Routing and Forwarding
> table" as defined in [I-D.ietf-l3vpn-rfc2547bis], and "VR" to "Virtual
> Router" as defined in  [I-D.ietf-l3vpn-vpn-vr] terminology."
>
> Moreover, I reworded section in 5.1.5:
> "Moreover, the activation of multicast features SHOULD be possible:
>       * per VRF / per VR
>       * per CE interface (when multiple CE of a same VPN are connected
>         to a common VRF/VR)
>       * per multicast group and/or per channel
>       * with a distinction between multicast reception and emission"
>
> [about section 3.3]
> > tme> Why isn't is a general requirement to interoperate with existing _=
multicast_
> > tme> deployments ?  rfc4021 says little about multicast - shouldn't thi=
s be explicit ?
>
> Well the idea is to highlight the focus : in a VPN deployment context,
> one of the most crucial requirement is to cohabit with the existing
> service (unicast VPN).
>
> You are right in the sense that deploying a multicast VPN solution
> should nicely cohabit with existing deployment of multicast on P and PE
> routers, and on CE routers.
>
> I added two sentences:
> - in 5.1.1:  "Enabling a VPN for multicast support SHOULD be possible
> with no (or very limited impact) on existing multicast protocols
> possibly already deployed on the CE devices."
> - in 5.2 : "The deployment of a multicast VPN solution SHOULD be
> possible with no (or very limited) impact on possibly existing
> deployments of multicast protocols on P and PE routers."
>
> Would that be ok ?
>
> >    o  some of these applications may involve rapid changes in customer
> >       multicast memberships, but this will depend on audience and
> >       capillarity of provider equipments
> >
> > tme> "capillarity" is a very obscure English word, and I do not know wh=
at is meant here.
> > tme> could this be a typo for "capabilities" ?
>
> No typo, but maybe the use of this term is less common in english than
> "capilarit'e" is in french... :)  We sometime use it metaphorically to
> refer to the number of small elements at the periphery of something,
> like leaves of a tree, with the image of capillary vessels in lungs for
> instance.
>
> I rephrased as: "some of these applications may involve rapid changes in
> customer multicast memberships as seen by the PE, but this will depend
> on audience patterns and on the number of provider equipments deployed
> close to VPN customers".
>
> > 4.1.2.  Symetric applications
> >
> > tme> nit : s/Symetric/ Symmetric /
> >
> >    Some use cases exposed by the survey can be grouped under this label=
,
> >    and include many-to-many applications such as conferencing, clusters
> >    monitoring.
> >
> > tme> (relative) nit : I do not know what "clusters monitoring" means in=
 this context.
> > tme> Is this for entities like beowulf clusters over VPN's ?
> > tme> An extra word to explain this would help.
>
> Survey responses did not include such a level of detail, so I can only gu=
ess here.
> I rephrased as: "server clusters monitoring".
>
>
> > 4.2.2.  Number of multicast VPNs per PE
> >
> >    The majority of survey answers express a number of multicast VPNs pe=
r
> >    PE of around tens (8 responses between 5 and 50); a significant
> >    number of them (4) expect deployments with hundreds or thousands (1
> >    response) of multicast VPNs per PE.
> >
> >    A solution SHOULD support a number of multicast VPNs per PE of
> >    several hundreds, and may have to scale up to thousands VPNs per PE.
> >
> > tme> PE means "provider edge". Does this mean, number per edge location=
, or
> > tme> number over all locations. I would suggest
> > tme> s/scale up to thousands VPNs per PE/scale up to thousands VPNs per=
 PE location/
> >
>
> RFC4026 "Provider Provisioned VPN Terminology" section 5.2 precisely
> suggest the use of "PE" and "CE" to refer to the devices themselves.
> That actually what we are used to do in l3vpn (for brievity).
>
> I added the following in the terminology section:
> " "Provider Edge", "Customer Edge" (as defined in [RFC4026](Andersson,
> L. and T. Madsen, "Provider Provisioned Virtual Private Network (VPN)
> Terminology," March 2005.)). As suggested in [RFC4026](Andersson, L. and
> T. Madsen, "Provider Provisioned Virtual Private Network (VPN)
> Terminology," March 2005.), we will use these notations to refer to the
> equipments/routers/devices themselves. Thus, "PE" will refer to the
> router on the provider's edge, which faces the "CE", the router on the
> customer's edge. "
>
>
> > 5.1.2.  CE-PE Multicast routing and management protocols
> >
> [snip]
> >
> > tme> Note that IGMP v3 and MLD v2 support means support for IGMP v1,v2 =
and MLD v1
> > tme> So, I would suggest :
> >
> > tme>   Among those protocols, the support of PIM-SM (version 2, revised=
, which
> > tme>   includes SSM model) and either IGMP v.3 (for IPv4 solutions) and=
 / or
> > tme>   MLD v.2 (for IPv6 solutions) are REQUIRED.
>
> Agreed.
> I also followed your implicit suggestion, by mentioning that hosts only
> implementing -v1 and -v2 are implicitely supported by IGMPv3 queriers.
>
>
> >    A multicast in VPN solution shall allow to define at least the same
> > tme> nit : s/shall allow to define/SHALL allow definition of/
>
> maybe "SHALL allow the definition of" ?
>
>
> >    As multicast is often used to deliver high quality services such as
> >    TV broadcast, the solution should have additional features to suppor=
t
> > tme> nit : s/should/SHOULD/
> >    high QoS such as bandwidth reservation and admission control.
>
> Since when is it MANDATORY to use CAPITALIZED version of those words ?
> Here I fell it hard to use a strict wording, considering how precise the
> rest of the sentence is.
>
>
> >    The solution MUST support SLA monitoring capabilities, which MAY
> >    possibly rely upon similar techniques (than those used by the unicas=
t
> >
> > tme> I puzzled over this - I suggest
> > tme> s/similar techniques (than/different techniques than/
> >    for the same monitoring purposes).
> > tme> s/)//
>
> Ok, that one indeed may be puzzling ; "which MAY possibly rely upon
> techniques similar to those used for the unicast service for the same
> monitoring purposes"  will be better I guess.
>
>
> > 5.1.8.  Internet Multicast
> >
> >    Connectivity with Internet Multicast (as a source or receiver)
> >    somehow fits in the context of the previous section.
> >
> > tme> Is this a stub for missing text ? This must be filled out to pass =
last call IMHO.
>
> Well, this section was supposed to be complete, describing the
> connectivity to/from Internet Multicast a similar to the connectivity
> to/from another multicast VPN.
>
> >
> >    It should be considered OPTIONAL given additional considerations
> >    needed to fulfill requirements for Internet side, such as security
> >    treatment.
> >
> tme> Here is some text :
> >
> [snip]
>
> The text you propose is I think partly redundant with section 5.1.7
> "Extranet".  I would like to just put in this section things that are
> specific to Internet Multicast connectivity (if there are any):
> - MSDP might be one of these, though I'd suspect not : MSDP is only
> inter-RP, so if no RP is deployed in VRF (acceptable), then no MSDP
> requirement is relevant here ; and in any case, I don't see that we'd
> need to state MSDP-related requirement for the overall architecture
> (same for embbeded-RP)
> - we may need to state MBGP-related requirement: I'm not sure precisely
> what we should say, since anything a bit precise would require
> articulation with what is expected for unicast Internet Connectivity in
> such a case.
>
> Maybe adding the following would be enough : "MBGP support in VRF/VR
> would be REQUIRED if a Multicast VPN solution supports connectivity with
> Internet Multicast. MSDP support in VRF/VR also is REQUIRED for such a
> solution, if it supports the RP functionality in VRF/VR".
>
> Would you agree ?
>
> >    The use of globally unique means of multicast-based service
> >    identification at the scale of the domain where such services are
> >    provided SHOULD be recommended.  If the ASM model is used, this
> >
> > tme> SSM also has source scoping, 239/8 can be used with either SSM or =
ASM. Therefore
> > tme> s/If the ASM model is used, this/For IPv4 multicasts, this/
>
> I rephrased as follows:
>
> "For IPv4 multicast, this implies the use of the multicast
> administratively scoped range, (239/8 as defined by [RFC2365]) for
> services which are to be used only inside the VPN, and of or SSM-range
> addresses (232/8 as defined by [I-D.ietf-ssm-arch]) or globally assigned
> group addresses (e.g. GLOP [RFC3180], 233/8) for services for which
> traffic may be transmitted outside the VPN ."
>
>
>
> > 5.1.13.  Minimum MTU
> >
> >    For customers, it is often a serious issue whether transmitted
> >    packets will be fragmented or not.  In particular, some multicast
> >    applications might have different requirements than those that make
> >    use of unicast, and they may expect services that guarantee availabl=
e
> >    packet length not to be fragmented.
> >
> >    Therefore, a multicast VPN solution SHOULD let customers' devices be
> >    free of any fragmentation or reassembly activity.
> >
> >    A committed minimum path MTU size SHOULD be provided to customers.
> >    Moreover, since Ethernet LAN segments are often located at first and
> >    last hops, a minimum 1500 bytes IP MTU SHOULD be provided.
> >
> > tme> There are a lot of tunnels used in multicast, and they tend to
> > tme> restrict MTU's to a little below the 1500 coming from Ethernet
> > tme> Are you really saying that no existing GRE or PPPoE or IP-IP multi=
cast
> >tme> tunnel can be used in multicast VPN architectures ? This seems extr=
eme.
>
> tme> In fact, since these tunnel types are allowed in Section 5.2.3.1.,
> > tme> I do not know how they can be implemented in most networks (unless
> > tme> jumbo frames are used throughout).
>
> Encapsulation that would limit the MTU is encapsulation between PE
> routers.  Those are often mutually reachable with high troughput links,
> such as GE w/ Jumbo Frames, POS... for which MTU can be easily made
> above 1500 I think.
>
> What we are saying only means that:
> a) if tunneling is used, then the provider should be able to commit to a =
minimum MTU
> b) is possible (SHOULD) this MTU should be 1500, because this is what
> will require the less tuning of customer application (which we expect
> can initialy be used inside a LAN, without tunnels)
>
> Consequently:
> - if the Multicast VPN solution doesn't meet b), then it doesn't meet
> the "SHOULD" (which may be acceptable, as soon as there is a rationale
> behind it)
> - it the provider's network cannot meet b), then it is less good than if
> it would
>
> Thus, a multicast VNP solution requiring the use of GRE or or IP-IP
> multicast for PE to PE tunnels is completely be acceptable:
> - GRE or IP-IP, by itself, doesn't I think limit the MTU
> - a provider network for which some PE-to-PE path go through a small MTU
> interface (like a Fast Ethernet LAN interface) won't be able to meet
> this requirement : this is not so common I think, and in any case that
> may be acceptable (client will tell you)
>
> PPPoE is intrinsicaly more limited, but I think nobody would like to use
> it for PE-to-PE communication right ?
>
> In anycase, nothing precludes any tunneling mechanism by itself, and
> 1500-byte minimal MTU is only a SHOULD.
>
>
> > tme>
> > tme> I would suggest either s/1500/1476/ or
> > tme> s/1500 bytes/1500 bytes, including any necessary tunnel headers/
> > tme> but the latter is sure to be confusing.
>
> We talk about "1500 byte IP MTU", which refers to the minimum MTU made av=
ailable to the customer
> (who doesn't "see" any tunnel).  Isn't this precise enough.
>
> [section 5.2.1]
> >
> > tme> This seems garbled. Do you mean "point to point, point to multipoi=
nt",
> > tme> or is the first "point" just a duplicate ? As a guess,
> > tme> s/point/point to point,/
> >
> Yes, "point" is a duplicate.
>
>
> >
> > tme> again, this seems garbled. I think this is meant :
> > tme>  s/leaves/leafs/
>
>
> Hmm. Isn't "leaf" like "knife", "life", or "scarf" ?
>
>
> >    Unwanted multicast traffic (e.g. multicast traffic that may be sent
> >    by a source located somewhere in the Internet and for which there is
> >    no interested receiver connected to a given VPN infrastructure) MUST
> >    NOT be propagated within a multicast-enabled VPN.
> >
> > tme> Is this consistent with Section 5.2.2.3. ? It seems to me that thi=
s
> > tme> should be a SHOULD NOT to allow for sub-optimal solutions
>
>
> While it might be acceptable (for provider-side scalability) that some
> traffic reaches a PE even if this is not needed, it would not be
> acceptable that such traffic be propagated toward the CE, inside the
> customer network.
>
> Isn't this reasonable ?
>
>
> >    As an illustration, one can consider the case of a solution that
> >    would use PIM-SM as a means to setup MDTunnels.  In such a case, the
> >    PIM RP might be a single point of failure.  Such a solution should
> >    thus be compatible with a solution implementing RP resiliency.
> >
> > tme> s/./, such as is provided by anycast RP [draft-ietf-pim-anycast-rp=
-04]./
>
> I also added BSR, for completeness.
>
>
>
>
>
>




From l3vpn-bounces@ietf.org Mon Jan 16 22:12:29 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EyhGn-0002Sm-8S; Mon, 16 Jan 2006 22:12:29 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EyhGk-0002SJ-5V
	for l3vpn@megatron.ietf.org; Mon, 16 Jan 2006 22:12:26 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA08903
	for <l3vpn@ietf.org>; Mon, 16 Jan 2006 22:11:02 -0500 (EST)
Received: from sj-iport-4.cisco.com ([171.68.10.86])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EyhOm-0000If-79
	for l3vpn@ietf.org; Mon, 16 Jan 2006 22:20:45 -0500
Received: from sj-core-3.cisco.com ([171.68.223.137])
	by sj-iport-4.cisco.com with ESMTP; 16 Jan 2006 19:12:16 -0800
X-IronPort-AV: i="3.99,374,1131350400"; 
	d="scan'208"; a="1767148611:sNHT31464384"
Received: from cisco.com (cypher.cisco.com [171.69.11.142])
	by sj-core-3.cisco.com (8.12.10/8.12.6) with ESMTP id k0H3CFc1019694;
	Mon, 16 Jan 2006 19:12:15 -0800 (PST)
Received: from [5.18.5.101] (sjc-vpn5-771.cisco.com [10.21.91.3])
	by cisco.com (8.8.8-Cisco List Logging/8.8.8) with ESMTP id TAA16591;
	Mon, 16 Jan 2006 19:12:15 -0800 (PST)
In-Reply-To: <dcad22d80601161827y7617a56aqa267b1219f1a8218@mail.gmail.com>
References: <200601151540.k0FFeF583898@merlot.juniper.net>
	<1137419379.15352.143.camel@wintermute>
	<2F7ADC25-9746-4E1E-A947-871761CC4C6D@cisco.com>
	<dcad22d80601161827y7617a56aqa267b1219f1a8218@mail.gmail.com>
Mime-Version: 1.0 (Apple Message framework v746.2)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <C751681C-D492-4F81-A6AF-6B6B86DB133F@cisco.com>
Content-Transfer-Encoding: 7bit
From: Yiqun Cai <ycai@cisco.com>
Date: Mon, 16 Jan 2006 19:12:05 -0800
To: Marshall Eubanks <marshall.eubanks@gmail.com>
X-Mailer: Apple Mail (2.746.2)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a
Content-Transfer-Encoding: 7bit
Cc: Yakov Rekhter <yakov@juniper.net>,
	Thomas Morin <thomas.morin@rd.francetelecom.com>, l3vpn@ietf.org
Subject: Re: WG last call: draft-ietf-l3vpn-ppvpn-mcast-reqts-03
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: l3vpn.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:l3vpn@ietf.org>
List-Help: <mailto:l3vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=subscribe>
Sender: l3vpn-bounces@ietf.org
Errors-To: l3vpn-bounces@ietf.org


On Jan 16, 2006, at 6:27 PM, Marshall Eubanks wrote:


> As I read this, extranet means a situation where different unicast and
> multicast routing topologies are likely, and thus I think that the
> bullet is needed.

Marshall,

I'm not sure that is the case.

In simple multicast term,  extranet means that the sources and the
receivers may potentially belong to different MVPNs.  Although it is
not required,  it generally implies that the sources and receivers
also belong to different unicast VPNs.   When the underlying routing
topologies are not congruent, a solution of MVPN has to deal with it.
But I don't see that as a requirement of "extranet".  It is more a  
baseline
requirement.

Thanks.




--
Yiqun






From l3vpn-bounces@ietf.org Tue Jan 17 04:02:18 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EymjK-0003gN-AA; Tue, 17 Jan 2006 04:02:18 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EymjI-0003fz-Gp
	for l3vpn@megatron.ietf.org; Tue, 17 Jan 2006 04:02:16 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA28566
	for <l3vpn@ietf.org>; Tue, 17 Jan 2006 04:00:50 -0500 (EST)
Received: from p-mail1.rd.francetelecom.com ([195.101.245.15])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EymrN-0005Ts-MX
	for l3vpn@ietf.org; Tue, 17 Jan 2006 04:10:38 -0500
Received: from ftrdmel10.rd.francetelecom.fr ([10.193.117.156]) by
	ftrdsmtp1.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.211); 
	Tue, 17 Jan 2006 10:02:11 +0100
Received: from l-at8613.rd.francetelecom.fr ([10.193.15.36]) by
	ftrdmel10.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.211); 
	Tue, 17 Jan 2006 10:02:11 +0100
From: Thomas Morin <thomas.morin@rd.francetelecom.com>
To: L3VPN <l3vpn@ietf.org>
In-Reply-To: <F5AAFD21F2034349BF638211B5F27B0F063A56F2@i2km86-ukdy.domain1.systemhost.net>
References: <F5AAFD21F2034349BF638211B5F27B0F063A56F2@i2km86-ukdy.domain1.systemhost.net>
Content-Type: multipart/alternative; boundary="=-+WldcBIdoq9PNURpGPew"
Organization: France Telecom R&D
Date: Mon, 16 Jan 2006 21:41:33 +0100
Message-Id: <1137444094.20451.13.camel@wintermute>
Mime-Version: 1.0
X-Mailer: Evolution 2.4.2.1 
X-OriginalArrivalTime: 17 Jan 2006 09:02:11.0592 (UTC)
	FILETIME=[B3DC4080:01C61B44]
X-Spam-Score: 1.0 (+)
X-Scan-Signature: 680445c3afe8c9e96925f2dfef141924
Subject: RE: Review of draft-ietf-l3vpn-ppvpn-mcast-reqts-03
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: l3vpn.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:l3vpn@ietf.org>
List-Help: <mailto:l3vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=subscribe>
Sender: l3vpn-bounces@ietf.org
Errors-To: l3vpn-bounces@ietf.org


--=-+WldcBIdoq9PNURpGPew
Content-Type: text/plain; charset=iso-8859-13
Content-Transfer-Encoding: quoted-printable

Benjamin,

First, thank you for your careful review and sending all these
comments.=20
(I'm implicitly agreeing to and integrating the comments to which I am
not responding below.)


> General - The document appears to use L3VPN, L3 VPN, PP L3VPN and L3
> PPVPN interchangeably.  I would suggest standardising on either one
> term (say L3VPN) or two terms if the fact the VPN is provider
> provisioned needs to be emphasied (say L3VPN and PPL3VPN).


Ok, I did the following:
- replaced the few  "L3 VPN" left, by "L3VPN"
- added an item in terminology definitions:=20
 =20
     L3VPN, VPN:  Throughout this document, "L3VPN" or even just "VPN"
will refer to "Provider-Provisioned Layer 3 Virtual Private Network" (PP
L3VPNs), and will be prefered for readability."


> Section 1:
>=20
> 1st paragraph: "VPN services satisfying the requirement defined in"=20
>=20

In fact, a plural was missing.



> Section 2.1:

[...]=20

> 3rd paragraph: The definition of ASM isn=FFt very helpful.  Maybe a more
> descriptive definition of what ASM actuall is would be helpful.


Agreed. Here is the updated text:
"Any Source Multicast. One of the two multicast service models, in which
a terminal suscribes to a multicast group to receive data sent to the
group by any source."
Also updated SSM:
"Source Specific Multicast. One of the two multicast service models,
where a terminal subscribes to a multicast group to receive data sent to
the group by a specific source."



> 11th paragraph: "Refers to any network device that not only
> participates to constitutes part of the deployment and the contributes
> to the maintenance of the VPN"


Somebody already contributed the following: "Refers to any network
device that not only participates in the deployment and the maintenance
of the VPN infrastructure, but also in the establishment and the
maintenance of the MD Tunnel"=20



> Section 4:
>=20

[...]

> The text as it stand implies to me that the deployments it talks about
> are expected in summer 2005, is that correct, or was it that the
> survey was done in summer 2005.  If it's the latter I would suggest
> rewording the first sentence as follows: "Most of the content of these
> sections originates from a survey done in summer 2005 among
> institutions and providers that expect to deploy such solutions, in
> summer 2005."

Ack.



> Section 4.1:

[...]

> 2nd paragraph: "to impact most of the design"


The goal is to talk about things thay have a greater impact on the
design.
Would that be better english: "scenarios that are expected to impact the
most the design of a multicast VPN solution".


>=20
> 9th bullet: I don=FFt think you mean "capillarity", I think you mean
> "capability"


See my answer to Marshall. That was an adventurous export from
french. :)



> Section 4.1.2:
> =20
>=20
> 4th paragraph: "[...] managed, because of:"
>=20
> =20
>=20
> 2nd bullet: "and possibly significantly"
>=20
> =20
>=20
> 5th paragraph: "indicate that oOptimizing bandwidth for this case may
> require"


That was supposed to be bullets inside a sentence. I reshaped this as:

"Because of:
- small groups, and low predictability of the location of participants
("sparse groups")
- possibly significantly high bandwidth (a few Mb/s per participant)
...optimizing bandwidth may require introducing dedicated states in the
core network (typically as much as the number of groups)."
=20


> Section 4.2.5:
>=20
> 1st paragraph: "A solution SHOULD scale up to thousands of PEs having
> multicast service enabled." This reads like a requirement but I can't
> find it in the summary of requirements in appendix A.


True, requirement summary was not updated for -03.



>=20
> Section 5.1.2:
>=20
> 1st paragraph: "Consequently to Section 3.1, the CEs and PEs CE-PE
> protocol SHOULD employ existing multicast protocols." These edits also
> need to be made to the copy of the requirement in Appendix A. =20


Misunderstanding here: we can't reduce to one "CE-PE protocol"; there
can be many, e.g IGMP or PIM; and we don't want either to invent a new
CE-PE protocol that would reuse an exisiting mcast protocol.


> Also do you really mean to refer to Section 3.1?


Well spotted, it doesn't make much sense indeed. I guess it should be
5.1.1.





> Section 5.1.3:
>=20
> 1st paragraph: "Firstly, the general considerations about regarding
> QoS in L3 VPNs as developed described in section"

ok with s/as described/expressed/




> 2nd paragraph: "In some cases, provided the agreed SLA may be
> different between unicast and multicast, which will need service
> differentiation mechanisms as such in order to monitor both SLAs."
>=20

What about : " In some cases, the agreed SLA may be different between
unicast and multicast, and that will require differentiation mechanisms
in order to monitor both SLAs."




> 5th paragraph: "the solution should" should the should be in capitals.
> Is this paragraph a requirement that also needs to be included in
> appendix A?
>=20

As already suggested, I changed it to a MAY.
Requirement summary will be updated soon.



> Section 5.1.6:
>=20
> =20
>=20
> 3rd paragraph: Suggest rewording/reorganising as follows: "The
> monitoring of multicast specific parameters and statistics SHOULD MUST
> include :
>=20
> =20
>=20
>    o  multicast traffic statistics: total traffic conveyed, incoming,
>=20
>       outgoing, dropped, etc., by period of time (as a MUST)
>=20
> =20
>=20
> The monitoring of multicast specific parameters and statistics MAY
> include=20
>=20
>    o  IP Performance Metrics related information (IPPM, [RFC2330])
> that
>=20
>       is relevant to the multicast traffic usage: such information
>=20
>       includes the one-way packet delay, the inter-packet delay
>=20
>       variation, etc. (as a MAY)"


Made it one paragraph, as bullet lists with one item looks weird.
But reshaping the thing was a good suggestion.


Thank you again for your attention to detail !

Cheers,

-Thomas




benjamin.niven-jenkins@bt.com:=20

> Thomas Morin RD-CORE <mailto:thomas.morin@francetelecom.com> wrote:
> > Hi,
> >=20
> > benjamin.niven-jenkins@bt.com:
> >> I recently sent the e-mail below to the L3VPN mailing list but it
> >> appears that the list server converted it to plain text and therefore
> >> mangled it a bit so I am forwarding it to you as RTF so that you can
> >> see my proposed comments and edits as originally intended.
> >=20
> > That's still appearing as plain text in my mailer.
> > Would you mind sending us an attached file, or HTML ?
>=20
> OK.  See attached for word & HTML documents with the original e-mail in.
>=20
> Ben

--=-+WldcBIdoq9PNURpGPew
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 7bit

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
  <META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
  <META NAME="GENERATOR" CONTENT="GtkHTML/3.8.1">
</HEAD>
<BODY>
Benjamin,<BR>
<BR>
First, thank you for your careful review and sending all these comments. <BR>
(I'm implicitly agreeing to and integrating the comments to which I am not responding below.)<BR>
<BR>
<BLOCKQUOTE TYPE=CITE>
    General - The document appears to use L3VPN, L3 VPN, PP L3VPN and L3 PPVPN interchangeably.&nbsp; I would suggest standardising on either one term (say L3VPN) or two terms if the fact the VPN is provider provisioned needs to be emphasied (say L3VPN and PPL3VPN).<BR>
</BLOCKQUOTE>
<BR>
Ok, I did the following:<BR>
- replaced the few&nbsp; &quot;L3 VPN&quot; left, by &quot;L3VPN&quot;<BR>
- added an item in terminology definitions: <BR>
&nbsp; <BR>
&nbsp;&nbsp;&nbsp;&nbsp; L3VPN, VPN:&nbsp; Throughout this document, &quot;L3VPN&quot; or even just &quot;VPN&quot; will refer to &quot;Provider-Provisioned Layer 3 Virtual Private Network&quot; (PP L3VPNs), and will be prefered for readability.&quot;<BR>
<BR>
<BLOCKQUOTE TYPE=CITE>
    Section 1:<BR>
    <BR>
    1st paragraph: &quot;VPN services satisfying <B><FONT COLOR="#ff0000">the</FONT></B> requirement defined in&quot; <BR>
    <BR>
</BLOCKQUOTE>
In fact, a plural was missing.<BR>
<BR>
<BR>
<BLOCKQUOTE TYPE=CITE>
    Section 2.1:<BR>
</BLOCKQUOTE>
[...] <BR>
<BLOCKQUOTE TYPE=CITE>
    3rd paragraph: The definition of ASM isn&#8217;t very helpful.&nbsp; Maybe a more descriptive definition of what ASM actuall is would be helpful.<BR>
</BLOCKQUOTE>
<BR>
Agreed. Here is the updated text:<BR>
&quot;Any Source Multicast. One of the two multicast service models, in which a terminal suscribes to a multicast group to receive data sent to the group by any source.&quot;<BR>
Also updated SSM:<BR>
&quot;Source Specific Multicast. One of the two multicast service models, where a terminal subscribes to a multicast group to receive data sent to the group by a specific source.&quot;<BR>
<BR>
<BR>
<BLOCKQUOTE TYPE=CITE>
    11th paragraph: &quot;Refers to any network device that not only <S><FONT COLOR="#ff0000">participates to</FONT></S> <B><FONT COLOR="#ff0000">constitutes part of</FONT></B> the deployment and <S><FONT COLOR="#ff0000">the</FONT></S> <B><FONT COLOR="#ff0000">contributes to the</FONT></B> maintenance of the VPN&quot;<BR>
</BLOCKQUOTE>
<BR>
Somebody already contributed the following: &quot;Refers to any network device that not only participates in the deployment and the maintenance of the VPN infrastructure, but also in the establishment and the maintenance of the MD Tunnel&quot; <BR>
<BR>
<BR>
<BLOCKQUOTE TYPE=CITE>
    Section 4:<BR>
    <BR>
</BLOCKQUOTE>
[...]<BR>
<BLOCKQUOTE TYPE=CITE>
    The text as it stand implies to me that the deployments it talks about are expected in summer 2005, is that correct, or was it that the survey was done in summer 2005.&nbsp; If it's the latter I would suggest rewording the first sentence as follows: &quot;Most <B><FONT COLOR="#ff0000">of the</FONT></B> content of these sections originates from a survey done <B><FONT COLOR="#ff0000">in summer 2005</FONT></B> among institutions and providers that expect to deploy such solutions<S><FONT COLOR="#ff0000">, in summer 2005</FONT></S>.&quot;<BR>
</BLOCKQUOTE>
Ack.<BR>
<BR>
<BR>
<BLOCKQUOTE TYPE=CITE>
    Section 4.1:<BR>
</BLOCKQUOTE>
[...]<BR>
<BLOCKQUOTE TYPE=CITE>
    2nd paragraph: &quot;to impact most <B><FONT COLOR="#ff0000">of</FONT></B> the design&quot;<BR>
</BLOCKQUOTE>
<BR>
The goal is to talk about things thay have a greater impact on the design.<BR>
Would that be better english: &quot;scenarios that are expected to impact the most the design of a multicast VPN solution&quot;.<BR>
<BR>
<BLOCKQUOTE TYPE=CITE>
    <BR>
    9th bullet: I don&#8217;t think you mean &quot;capillarity&quot;, I think you mean &quot;capability&quot;<BR>
</BLOCKQUOTE>
<BR>
See my answer to Marshall. That was an adventurous export from french. :)<BR>
<BR>
<BR>
<BLOCKQUOTE TYPE=CITE>
    Section 4.1.2:<BR>
    &nbsp;<BR>
    <BR>
    4th paragraph: &quot;[...] managed, because <B><FONT COLOR="#ff0000">of</FONT></B>:&quot;<BR>
    <BR>
    &nbsp;<BR>
    <BR>
    2nd bullet: &quot;<S><FONT COLOR="#ff0000">and </FONT></S>possibly significantly&quot;<BR>
    <BR>
    &nbsp;<BR>
    <BR>
    5th paragraph: &quot;<S><FONT COLOR="#ff0000">indicate that o</FONT></S><FONT COLOR="#ff0000">Optimizing</FONT> bandwidth <B><FONT COLOR="#ff0000">for this case</FONT></B> may require&quot;<BR>
</BLOCKQUOTE>
<BR>
That was supposed to be bullets inside a sentence. I reshaped this as:<BR>
<BR>
&quot;Because of:<BR>
- small groups, and low predictability of the location of participants (&quot;sparse groups&quot;)<BR>
- possibly significantly high bandwidth (a few Mb/s per participant)<BR>
...optimizing bandwidth may require introducing dedicated states in the core network (typically as much as the number of groups).&quot;<BR>
&nbsp;<BR>
<BR>
<BLOCKQUOTE TYPE=CITE>
    Section 4.2.5:<BR>
    <BR>
    1st paragraph: &quot;A solution SHOULD scale up to thousands of PEs having multicast service enabled.&quot; This reads like a requirement but I can't find it in the summary of requirements in appendix A.<BR>
</BLOCKQUOTE>
<BR>
True, requirement summary was not updated for -03.<BR>
<BR>
<BR>
<BLOCKQUOTE TYPE=CITE>
    <BR>
    Section 5.1.2:<BR>
    <BR>
    1st paragraph: &quot;Consequently to Section 3.1, the <S><FONT COLOR="#ff0000">CEs and PEs</FONT></S><FONT COLOR="#ff0000"> </FONT><FONT COLOR="#ff0000"><B>CE-PE protocol</B></FONT> SHOULD employ existing multicast protocols.&quot; These edits also need to be made to the copy of the requirement in Appendix A.&nbsp; <BR>
</BLOCKQUOTE>
<BR>
Misunderstanding here:<FONT COLOR="#000000"> we can't reduce to</FONT> one &quot;<B><FONT COLOR="#000000">CE-PE protocol</FONT></B>&quot;; there can be many, e.g IGMP or PIM<FONT COLOR="#000000">; and we don't want either to invent a new CE-PE protocol that would reuse an exisiting mcast protocol.</FONT><BR>
<BR>
<BLOCKQUOTE TYPE=CITE>
    Also do you really mean to refer to Section 3.1?<BR>
</BLOCKQUOTE>
<BR>
Well spotted, it doesn't make much sense indeed. I guess it should be 5.1.1.<BR>
<BR>
<BR>
<BR>
<BR>
<BLOCKQUOTE TYPE=CITE>
    Section 5.1.3:<BR>
    <BR>
    1st paragraph: &quot;First<B><FONT COLOR="#ff0000">ly</FONT></B>, <B><FONT COLOR="#ff0000">the</FONT></B> general considerations <S><FONT COLOR="#ff0000">about</FONT></S><FONT COLOR="#ff0000"> </FONT><FONT COLOR="#ff0000"><B>regarding</B></FONT> QoS in L3 VPNs as <S><FONT COLOR="#ff0000">developed</FONT></S><FONT COLOR="#ff0000"> </FONT><FONT COLOR="#ff0000"><B>described</B></FONT> in section&quot;<BR>
</BLOCKQUOTE>
ok with s/as described/expressed/<BR>
<BR>
<BR>
<BR>
<BLOCKQUOTE TYPE=CITE>
    2nd paragraph: &quot;In some cases, <S><FONT COLOR="#ff0000">provided</FONT></S><FONT COLOR="#ff0000"> </FONT><FONT COLOR="#ff0000"><B>the agreed</B></FONT> SLA may be different between unicast and multicast, which will need service differentiation mechanisms <S><FONT COLOR="#ff0000">as such</FONT></S><FONT COLOR="#ff0000"><B> in order to monitor both SLAs</B></FONT>.&quot;<BR>
    <BR>
</BLOCKQUOTE>
What about : &quot; In some cases, the agreed SLA may be different between unicast and multicast, and that will require differentiation mechanisms in order to monitor both SLAs.&quot;<BR>
<BR>
<BR>
<BR>
<BLOCKQUOTE TYPE=CITE>
    5th paragraph: &quot;the solution should&quot; should the should be in capitals.&nbsp; Is this paragraph a requirement that also needs to be included in appendix A?<BR>
    <BR>
</BLOCKQUOTE>
As already suggested, I changed it to a MAY.<BR>
Requirement summary will be updated soon.<BR>
<BR>
<BR>
<BLOCKQUOTE TYPE=CITE>
    Section 5.1.6:<BR>
    <BR>
    &nbsp;<BR>
    <BR>
    3rd paragraph: Suggest rewording/reorganising as follows: &quot;The monitoring of multicast specific parameters and statistics <S><FONT COLOR="#ff0000">SHOULD</FONT></S><FONT COLOR="#ff0000"> </FONT><FONT COLOR="#ff0000"><B>MUST</B></FONT><FONT COLOR="#ff0000"> </FONT>include <S><FONT COLOR="#ff0000">:</FONT></S><BR>
    <BR>
    <FONT COLOR="#ff0000">&nbsp;</FONT><BR>
    <BR>
    <S><FONT COLOR="#ff0000">&nbsp;&nbsp; o&nbsp; </FONT></S><FONT COLOR="#ff0000">multicast</FONT> traffic statistics: total traffic conveyed, incoming,<BR>
    <BR>
    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; outgoing, dropped, etc., by period of time<S><FONT COLOR="#ff0000"> (as a MUST)</FONT></S><BR>
    <BR>
    &nbsp;<BR>
    <BR>
    <FONT COLOR="#ff0000">The monitoring of multicast specific parameters and statistics MAY include</FONT> <BR>
    <BR>
    <S><FONT COLOR="#ff0000">&nbsp;&nbsp; o&nbsp; </FONT></S><FONT COLOR="#ff0000">IP</FONT> Performance Metrics related information (IPPM, [RFC2330]) that<BR>
    <BR>
    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; is relevant to the multicast traffic usage: such information<BR>
    <BR>
    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; includes the one-way packet delay, the inter-packet delay<BR>
    <BR>
    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; variation, etc.<S><FONT COLOR="#ff0000"> (as a MAY)</FONT></S>&quot;<BR>
</BLOCKQUOTE>
<BR>
Made it one paragraph, as bullet lists with one item looks weird.<BR>
But reshaping the thing was a good suggestion.<BR>
<BR>
<BR>
Thank you again for your attention to detail !<BR>
<BR>
Cheers,<BR>
<BR>
-Thomas<BR>
<BR>
<BR>
<BR>
<BR>
benjamin.niven-jenkins@bt.com: 
<BLOCKQUOTE TYPE=CITE>
<PRE>
<FONT COLOR="#000000">Thomas Morin RD-CORE &lt;mailto:<A HREF="mailto:thomas.morin@francetelecom.com">thomas.morin@francetelecom.com</A>&gt; wrote:</FONT>
<FONT COLOR="#000000">&gt; Hi,</FONT>
<FONT COLOR="#000000">&gt; </FONT>
<FONT COLOR="#000000">&gt; <A HREF="mailto:benjamin.niven-jenkins@bt.com">benjamin.niven-jenkins@bt.com</A>:</FONT>
<FONT COLOR="#000000">&gt;&gt; I recently sent the e-mail below to the L3VPN mailing list but it</FONT>
<FONT COLOR="#000000">&gt;&gt; appears that the list server converted it to plain text and therefore</FONT>
<FONT COLOR="#000000">&gt;&gt; mangled it a bit so I am forwarding it to you as RTF so that you can</FONT>
<FONT COLOR="#000000">&gt;&gt; see my proposed comments and edits as originally intended.</FONT>
<FONT COLOR="#000000">&gt; </FONT>
<FONT COLOR="#000000">&gt; That's still appearing as plain text in my mailer.</FONT>
<FONT COLOR="#000000">&gt; Would you mind sending us an attached file, or HTML ?</FONT>

<FONT COLOR="#000000">OK.  See attached for word &amp; HTML documents with the original e-mail in.</FONT>

<FONT COLOR="#000000">Ben</FONT>
</PRE>
</BLOCKQUOTE>
</BODY>
</HTML>

--=-+WldcBIdoq9PNURpGPew--





From l3vpn-bounces@ietf.org Tue Jan 17 04:35:55 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EynFr-0005xW-7j; Tue, 17 Jan 2006 04:35:55 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EynFp-0005wv-Mf
	for l3vpn@megatron.ietf.org; Tue, 17 Jan 2006 04:35:53 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA29982
	for <l3vpn@ietf.org>; Tue, 17 Jan 2006 04:34:29 -0500 (EST)
From: benjamin.niven-jenkins@bt.com
Received: from smtp3.smtp.bt.com ([217.32.164.138])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EynNv-0006N8-52
	for l3vpn@ietf.org; Tue, 17 Jan 2006 04:44:16 -0500
Received: from i2kc07-ukbr.domain1.systemhost.net ([193.113.197.14]) by
	smtp3.smtp.bt.com with Microsoft SMTPSVC(6.0.3790.211); 
	Tue, 17 Jan 2006 09:35:41 +0000
Received: from i2km86-ukdy.domain1.systemhost.net ([193.113.30.79]) by
	i2kc07-ukbr.domain1.systemhost.net with Microsoft
	SMTPSVC(6.0.3790.211); Tue, 17 Jan 2006 09:35:41 +0000
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C61B49.5EE8F4E8"
Date: Tue, 17 Jan 2006 09:35:33 -0000
Message-ID: <F5AAFD21F2034349BF638211B5F27B0F06422598@i2km86-ukdy.domain1.systemhost.net>
Thread-Topic: Review of draft-ietf-l3vpn-ppvpn-mcast-reqts-03
Thread-Index: AcYbRY9kpu4wPIBuQjeo4so0iJTwagAAi1Og
To: <thomas.morin@rd.francetelecom.com>, <l3vpn@ietf.org>
X-OriginalArrivalTime: 17 Jan 2006 09:35:41.0232 (UTC)
	FILETIME=[61B2FB00:01C61B49]
X-Spam-Score: 1.0 (+)
X-Scan-Signature: 85fe3afc5d9560be77aa81420052017a
Cc: 
Subject: RE: Review of draft-ietf-l3vpn-ppvpn-mcast-reqts-03
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: l3vpn.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:l3vpn@ietf.org>
List-Help: <mailto:l3vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=subscribe>
Sender: l3vpn-bounces@ietf.org
Errors-To: l3vpn-bounces@ietf.org

This is a multi-part message in MIME format.

------_=_NextPart_001_01C61B49.5EE8F4E8
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Thomas,
=20
See in-line, my comments are marked [BPN].
=20
Ben
=20


________________________________

	From: l3vpn-bounces@ietf.org [mailto:l3vpn-bounces@ietf.org] On
Behalf Of Thomas Morin
	Sent: Monday, January 16, 2006 8:42 PM
	To: L3VPN
	Subject: RE: Review of draft-ietf-l3vpn-ppvpn-mcast-reqts-03
=09
=09
	Benjamin,
=09
	First, thank you for your careful review and sending all these
comments.=20
	(I'm implicitly agreeing to and integrating the comments to
which I am not responding below.)
=09
=09

		General - The document appears to use L3VPN, L3 VPN, PP
L3VPN and L3 PPVPN interchangeably.  I would suggest standardising on
either one term (say L3VPN) or two terms if the fact the VPN is provider
provisioned needs to be emphasied (say L3VPN and PPL3VPN).
	=09


	Ok, I did the following:
	- replaced the few  "L3 VPN" left, by "L3VPN"
	- added an item in terminology definitions:=20
	 =20
	     L3VPN, VPN:  Throughout this document, "L3VPN" or even just
"VPN" will refer to "Provider-Provisioned Layer 3 Virtual Private
Network" (PP L3VPNs), and will be prefered for readability."
	=20
	[BPN] OK, that's fine.=20
=09

		Section 1:
	=09
		1st paragraph: "VPN services satisfying the requirement
defined in"=20
	=09
	=09

	In fact, a plural was missing.
	=20
	[BPN] Then it should be "VPN services satifying the requirements
defined in"=20
=09
=09

		Section 2.1:
	=09

	[...]=20
=09

		3rd paragraph: The definition of ASM isn't very helpful.
Maybe a more descriptive definition of what ASM actuall is would be
helpful.
	=09


	Agreed. Here is the updated text:
	"Any Source Multicast. One of the two multicast service models,
in which a terminal suscribes to a multicast group to receive data sent
to the group by any source."
	Also updated SSM:
	"Source Specific Multicast. One of the two multicast service
models, where a terminal subscribes to a multicast group to receive data
sent to the group by a specific source."
=09
	[BPN] OK, that's fine.
=09

		11th paragraph: "Refers to any network device that not
only participates to constitutes part of the deployment and the
contributes to the maintenance of the VPN"
	=09


	Somebody already contributed the following: "Refers to any
network device that not only participates in the deployment and the
maintenance of the VPN infrastructure, but also in the establishment and
the maintenance of the MD Tunnel"=20
=09
	 [BPN] I prefer the text already contributed by somebody so go
with that and ignore my proposed edit.
	=20
=09

		Section 4:
	=09
	=09

	[...]
=09

		The text as it stand implies to me that the deployments
it talks about are expected in summer 2005, is that correct, or was it
that the survey was done in summer 2005.  If it's the latter I would
suggest rewording the first sentence as follows: "Most of the content of
these sections originates from a survey done in summer 2005 among
institutions and providers that expect to deploy such solutions, in
summer 2005."
	=09

	Ack.
=09
=09
=09

		Section 4.1:
	=09

	[...]
=09

		2nd paragraph: "to impact most of the design"
	=09


	The goal is to talk about things thay have a greater impact on
the design.
	Would that be better english: "scenarios that are expected to
impact the most the design of a multicast VPN solution".
	=20
	[BPN] I believe my original proposal is the best English and is
in line with your goal to talk about things that have a large impact on
the design.=20
=09


		9th bullet: I don't think you mean "capillarity", I
think you mean "capability"
	=09


	See my answer to Marshall. That was an adventurous export from
french. :)
=09
=09
=09

		Section 4.1.2:
		=20
	=09
		4th paragraph: "[...] managed, because of:"
	=09
		=20
	=09
		2nd bullet: "and possibly significantly"
	=09
		=20
	=09
		5th paragraph: "indicate that oOptimizing bandwidth for
this case may require"
	=09


	That was supposed to be bullets inside a sentence. I reshaped
this as:
=09
	"Because of:
	- small groups, and low predictability of the location of
participants ("sparse groups")
	- possibly significantly high bandwidth (a few Mb/s per
participant)
	...optimizing bandwidth may require introducing dedicated states
in the core network (typically as much as the number of groups)."
	 [BPN] OK, that's fine.
=09
=09

		Section 4.2.5:
	=09
		1st paragraph: "A solution SHOULD scale up to thousands
of PEs having multicast service enabled." This reads like a requirement
but I can't find it in the summary of requirements in appendix A.
	=09


	True, requirement summary was not updated for -03.
=09
=09
=09


		Section 5.1.2:
	=09
		1st paragraph: "Consequently to Section 3.1, the CEs and
PEs CE-PE protocol SHOULD employ existing multicast protocols." These
edits also need to be made to the copy of the requirement in Appendix A.

	=09


	Misunderstanding here: we can't reduce to one "CE-PE protocol";
there can be many, e.g IGMP or PIM; and we don't want either to invent a
new CE-PE protocol that would reuse an exisiting mcast protocol.
	=20
	[BPN] OK.  My concern is that by saying "CEs and PEs SHOULD
employ existing multicast protocols" implies that it is more than the
CE-PE protocol that you are referring to - i.e. that you are implying
that the PE-PE and MDT tunnel establishment protocols SHOULD also use
existing protocols.  How about something like "the CEs and PEs SHOULD
employ existing multicast protocols for communication with each other"?
	 =20
=09

		Also do you really mean to refer to Section 3.1?
	=09


	Well spotted, it doesn't make much sense indeed. I guess it
should be 5.1.1.
=09
=09
=09
=09
=09

		Section 5.1.3:
	=09
		1st paragraph: "Firstly, the general considerations
about regarding QoS in L3 VPNs as developed described in section"
	=09

	ok with s/as described/expressed/
=09
	[BPN] OK, that's fine.
=09
=09

		2nd paragraph: "In some cases, provided the agreed SLA
may be different between unicast and multicast, which will need service
differentiation mechanisms as such in order to monitor both SLAs."
	=09
	=09

	What about : " In some cases, the agreed SLA may be different
between unicast and multicast, and that will require differentiation
mechanisms in order to monitor both SLAs."
	[BPN] OK, that's fine.
=09
=09
=09

		5th paragraph: "the solution should" should the should
be in capitals.  Is this paragraph a requirement that also needs to be
included in appendix A?
	=09
	=09

	As already suggested, I changed it to a MAY.
	Requirement summary will be updated soon.
=09
=09
=09

		Section 5.1.6:
	=09
		=20
	=09
		3rd paragraph: Suggest rewording/reorganising as
follows: "The monitoring of multicast specific parameters and statistics
SHOULD MUST include :
	=09
		=20
	=09
		   o  multicast traffic statistics: total traffic
conveyed, incoming,
	=09
		      outgoing, dropped, etc., by period of time (as a
MUST)
	=09
		=20
	=09
		The monitoring of multicast specific parameters and
statistics MAY include=20
	=09
		   o  IP Performance Metrics related information (IPPM,
[RFC2330]) that
	=09
		      is relevant to the multicast traffic usage: such
information
	=09
		      includes the one-way packet delay, the
inter-packet delay
	=09
		      variation, etc. (as a MAY)"
	=09


	Made it one paragraph, as bullet lists with one item looks
weird.
	But reshaping the thing was a good suggestion.
=09
=09
	Thank you again for your attention to detail !
=09
	Cheers,
=09
	-Thomas
=09
=09
=09
=09
	benjamin.niven-jenkins@bt.com:=20

		Thomas Morin RD-CORE
<mailto:thomas.morin@francetelecom.com> wrote:
		> Hi,
		>=20
		> benjamin.niven-jenkins@bt.com:
		>> I recently sent the e-mail below to the L3VPN mailing
list but it
		>> appears that the list server converted it to plain
text and therefore
		>> mangled it a bit so I am forwarding it to you as RTF
so that you can
		>> see my proposed comments and edits as originally
intended.
		>=20
		> That's still appearing as plain text in my mailer.
		> Would you mind sending us an attached file, or HTML ?
	=09
		OK.  See attached for word & HTML documents with the
original e-mail in.
	=09
		Ben


------_=_NextPart_001_01C61B49.5EE8F4E8
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2800.1522" name=3DGENERATOR></HEAD>
<BODY>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D923542309-17012006><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Thomas,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D923542309-17012006><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D923542309-17012006><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>See in-line, my comments are marked=20
[BPN].</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D923542309-17012006><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D923542309-17012006><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Ben</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN =
class=3D923542309-17012006></SPAN>&nbsp;</DIV><BR>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px =
solid; MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
  <HR tabIndex=3D-1>
  <FONT face=3DTahoma size=3D2><B>From:</B> l3vpn-bounces@ietf.org=20
  [mailto:l3vpn-bounces@ietf.org] <B>On Behalf Of </B>Thomas=20
  Morin<BR><B>Sent:</B> Monday, January 16, 2006 8:42 PM<BR><B>To:</B>=20
  L3VPN<BR><B>Subject:</B> RE: Review of=20
  draft-ietf-l3vpn-ppvpn-mcast-reqts-03<BR></FONT><BR></DIV>
  <DIV></DIV>Benjamin,<BR><BR>First, thank you for your careful review =
and=20
  sending all these comments. <BR>(I'm implicitly agreeing to and =
integrating=20
  the comments to which I am not responding below.)<BR><BR>
  <BLOCKQUOTE TYPE=3D"CITE">General - The document appears to use L3VPN, =
L3 VPN,=20
    PP L3VPN and L3 PPVPN interchangeably.&nbsp; I would suggest =
standardising=20
    on either one term (say L3VPN) or two terms if the fact the VPN is =
provider=20
    provisioned needs to be emphasied (say L3VPN and =
PPL3VPN).<BR></BLOCKQUOTE>
  <DIV><BR>Ok, I did the following:<BR>- replaced the few&nbsp; "L3 VPN" =
left,=20
  by "L3VPN"<BR>- added an item in terminology definitions: <BR>&nbsp;=20
  <BR>&nbsp;&nbsp;&nbsp;&nbsp; L3VPN, VPN:&nbsp; Throughout this =
document,=20
  "L3VPN" or even just "VPN" will refer to "Provider-Provisioned Layer 3 =
Virtual=20
  Private Network" (PP L3VPNs), and will be prefered for =
readability."<BR><SPAN=20
  class=3D923542309-17012006><FONT face=3DArial color=3D#0000ff=20
  size=3D2>&nbsp;</FONT></SPAN></DIV>
  <DIV><SPAN class=3D923542309-17012006><FONT face=3DArial =
color=3D#0000ff=20
  size=3D2>[BPN] OK, that's fine.</FONT>&nbsp;</SPAN><BR></DIV>
  <BLOCKQUOTE TYPE=3D"CITE">Section 1:<BR><BR>1st paragraph: "VPN =
services=20
    satisfying <B><FONT color=3D#ff0000>the</FONT></B> requirement =
defined in"=20
    <BR><BR></BLOCKQUOTE>
  <DIV>In fact, a plural was missing.<BR><SPAN =
class=3D923542309-17012006><FONT=20
  face=3DArial color=3D#0000ff size=3D2>&nbsp;</FONT></SPAN></DIV>
  <DIV><SPAN class=3D923542309-17012006><FONT face=3DArial =
color=3D#0000ff=20
  size=3D2>[BPN]&nbsp;Then it should be "VPN services satifying the =
requirements=20
  defined in"</FONT>&nbsp;</SPAN><BR><BR></DIV>
  <BLOCKQUOTE TYPE=3D"CITE">Section 2.1:<BR></BLOCKQUOTE>[...] <BR>
  <BLOCKQUOTE TYPE=3D"CITE">3rd paragraph: The definition of ASM =
isn&#8217;t very=20
    helpful.&nbsp; Maybe a more descriptive definition of what ASM =
actuall is=20
    would be helpful.<BR></BLOCKQUOTE><BR>Agreed. Here is the updated=20
  text:<BR>"Any Source Multicast. One of the two multicast service =
models, in=20
  which a terminal suscribes to a multicast group to receive data sent =
to the=20
  group by any source."<BR>Also updated SSM:<BR>"Source Specific =
Multicast. One=20
  of the two multicast service models, where a terminal subscribes to a=20
  multicast group to receive data sent to the group by a specific=20
  source."<BR><BR><SPAN class=3D923542309-17012006><FONT face=3DArial =
color=3D#0000ff=20
  size=3D2>[BPN] OK, that's fine.</FONT></SPAN><BR>
  <BLOCKQUOTE TYPE=3D"CITE">11th paragraph: "Refers to any network =
device that=20
    not only <S><FONT color=3D#ff0000>participates to</FONT></S> =
<B><FONT=20
    color=3D#ff0000>constitutes part of</FONT></B> the deployment and =
<S><FONT=20
    color=3D#ff0000>the</FONT></S> <B><FONT color=3D#ff0000>contributes =
to=20
    the</FONT></B> maintenance of the VPN"<BR></BLOCKQUOTE>
  <DIV><BR>Somebody already contributed the following: "Refers to any =
network=20
  device that not only participates in the deployment and the =
maintenance of the=20
  VPN infrastructure, but also in the establishment and the maintenance =
of the=20
  MD Tunnel"&nbsp;<BR><BR><SPAN class=3D923542309-17012006><FONT =
face=3DArial=20
  color=3D#0000ff size=3D2>&nbsp;[BPN] I prefer the text already =
contributed by=20
  somebody so go with that and ignore my proposed =
edit.</FONT></SPAN></DIV>
  <DIV><SPAN class=3D923542309-17012006>&nbsp;</SPAN><BR></DIV>
  <BLOCKQUOTE TYPE=3D"CITE">Section 4:<BR><BR></BLOCKQUOTE>[...]<BR>
  <BLOCKQUOTE TYPE=3D"CITE">The text as it stand implies to me that the=20
    deployments it talks about are expected in summer 2005, is that =
correct, or=20
    was it that the survey was done in summer 2005.&nbsp; If it's the =
latter I=20
    would suggest rewording the first sentence as follows: "Most =
<B><FONT=20
    color=3D#ff0000>of the</FONT></B> content of these sections =
originates from a=20
    survey done <B><FONT color=3D#ff0000>in summer 2005</FONT></B> among =

    institutions and providers that expect to deploy such =
solutions<S><FONT=20
    color=3D#ff0000>, in summer =
2005</FONT></S>."<BR></BLOCKQUOTE>Ack.<BR><BR><BR>
  <BLOCKQUOTE TYPE=3D"CITE">Section 4.1:<BR></BLOCKQUOTE>[...]<BR>
  <BLOCKQUOTE TYPE=3D"CITE">2nd paragraph: "to impact most <B><FONT=20
    color=3D#ff0000>of</FONT></B> the design"<BR></BLOCKQUOTE>
  <DIV><BR>The goal is to talk about things thay have a greater impact =
on the=20
  design.<BR>Would that be better english: "scenarios that are expected =
to=20
  impact the most the design of a multicast VPN solution".<BR><SPAN=20
  class=3D923542309-17012006><FONT face=3DArial color=3D#0000ff=20
  size=3D2>&nbsp;</FONT></SPAN></DIV>
  <DIV><SPAN class=3D923542309-17012006><SPAN =
class=3D923542309-17012006><FONT=20
  face=3DArial color=3D#0000ff size=3D2>[BPN]&nbsp;I believe my original =
proposal is=20
  the best English and&nbsp;is in line with your goal to talk about =
things that=20
  have a large impact on the =
design.</FONT></SPAN>&nbsp;</SPAN><BR></DIV>
  <BLOCKQUOTE TYPE=3D"CITE"><BR>9th bullet: I don&#8217;t think you mean =

    "capillarity", I think you mean "capability"<BR></BLOCKQUOTE><BR>See =
my answer=20
  to Marshall. That was an adventurous export from french. =
:)<BR><BR><BR>
  <BLOCKQUOTE TYPE=3D"CITE">Section 4.1.2:<BR>&nbsp;<BR><BR>4th =
paragraph:=20
    "[...] managed, because <B><FONT=20
    color=3D#ff0000>of</FONT></B>:"<BR><BR>&nbsp;<BR><BR>2nd bullet: =
"<S><FONT=20
    color=3D#ff0000>and </FONT></S>possibly=20
    significantly"<BR><BR>&nbsp;<BR><BR>5th paragraph: "<S><FONT=20
    color=3D#ff0000>indicate that o</FONT></S><FONT=20
    color=3D#ff0000>Optimizing</FONT> bandwidth <B><FONT =
color=3D#ff0000>for this=20
    case</FONT></B> may require"<BR></BLOCKQUOTE><BR>That was supposed =
to be=20
  bullets inside a sentence. I reshaped this as:<BR><BR>"Because =
of:<BR>- small=20
  groups, and low predictability of the location of participants =
("sparse=20
  groups")<BR>- possibly significantly high bandwidth (a few Mb/s per=20
  participant)<BR>...optimizing bandwidth may require introducing =
dedicated=20
  states in the core network (typically as much as the number of=20
  groups)."<BR>&nbsp;<SPAN class=3D923542309-17012006><FONT face=3DArial =

  color=3D#0000ff size=3D2>[BPN] OK, that's fine.</FONT></SPAN><BR><BR>
  <BLOCKQUOTE TYPE=3D"CITE">Section 4.2.5:<BR><BR>1st paragraph: "A =
solution=20
    SHOULD scale up to thousands of PEs having multicast service =
enabled." This=20
    reads like a requirement but I can't find it in the summary of =
requirements=20
    in appendix A.<BR></BLOCKQUOTE><BR>True, requirement summary was not =
updated=20
  for -03.<BR><BR><BR>
  <BLOCKQUOTE TYPE=3D"CITE"><BR>Section 5.1.2:<BR><BR>1st paragraph:=20
    "Consequently to Section 3.1, the <S><FONT color=3D#ff0000>CEs and=20
    PEs</FONT></S><FONT color=3D#ff0000> </FONT><FONT =
color=3D#ff0000><B>CE-PE=20
    protocol</B></FONT> SHOULD employ existing multicast protocols." =
These edits=20
    also need to be made to the copy of the requirement in Appendix =
A.&nbsp;=20
  <BR></BLOCKQUOTE>
  <DIV><BR>Misunderstanding here:<FONT color=3D#000000> we can't reduce =
to</FONT>=20
  one "<B><FONT color=3D#000000>CE-PE protocol</FONT></B>"; there can be =
many, e.g=20
  IGMP or PIM<FONT color=3D#000000>; and we don't want either to invent =
a new=20
  CE-PE protocol that would reuse an exisiting mcast =
protocol.</FONT><BR><SPAN=20
  class=3D923542309-17012006><FONT face=3DArial color=3D#0000ff=20
  size=3D2>&nbsp;</FONT></SPAN></DIV>
  <DIV><SPAN class=3D923542309-17012006><FONT face=3DArial =
color=3D#0000ff=20
  size=3D2>[BPN] OK.&nbsp; My concern is that by saying "CEs and PEs =
SHOULD employ=20
  existing multicast protocols" implies that it is more than the CE-PE =
protocol=20
  that you are referring to - i.e. that you are implying that the PE-PE =
and MDT=20
  tunnel establishment protocols&nbsp;SHOULD also use existing =
protocols.&nbsp;=20
  How about something like "the CEs and PEs SHOULD employ existing =
multicast=20
  protocols for communication with each other"?</FONT></SPAN></DIV>
  <DIV><SPAN class=3D923542309-17012006>&nbsp;&nbsp;</SPAN><BR></DIV>
  <BLOCKQUOTE TYPE=3D"CITE">Also do you really mean to refer to Section=20
  3.1?<BR></BLOCKQUOTE><BR>Well spotted, it doesn't make much sense =
indeed. I=20
  guess it should be 5.1.1.<BR><BR><BR><BR><BR>
  <BLOCKQUOTE TYPE=3D"CITE">Section 5.1.3:<BR><BR>1st paragraph: =
"First<B><FONT=20
    color=3D#ff0000>ly</FONT></B>, <B><FONT =
color=3D#ff0000>the</FONT></B> general=20
    considerations <S><FONT color=3D#ff0000>about</FONT></S><FONT =
color=3D#ff0000>=20
    </FONT><FONT color=3D#ff0000><B>regarding</B></FONT> QoS in L3 VPNs =
as=20
    <S><FONT color=3D#ff0000>developed</FONT></S><FONT color=3D#ff0000> =
</FONT><FONT=20
    color=3D#ff0000><B>described</B></FONT> in =
section"<BR></BLOCKQUOTE>ok with s/as=20
  described/expressed/<BR><BR><SPAN class=3D923542309-17012006><FONT =
face=3DArial=20
  color=3D#0000ff size=3D2>[BPN] OK, that's fine.</FONT></SPAN><BR><BR>
  <BLOCKQUOTE TYPE=3D"CITE">2nd paragraph: "In some cases, <S><FONT=20
    color=3D#ff0000>provided</FONT></S><FONT color=3D#ff0000> =
</FONT><FONT=20
    color=3D#ff0000><B>the agreed</B></FONT> SLA may be different =
between unicast=20
    and multicast, which will need service differentiation mechanisms =
<S><FONT=20
    color=3D#ff0000>as such</FONT></S><FONT color=3D#ff0000><B> in order =
to monitor=20
    both SLAs</B></FONT>."<BR><BR></BLOCKQUOTE>What about : " In some =
cases, the=20
  agreed SLA may be different between unicast and multicast, and that =
will=20
  require differentiation mechanisms in order to monitor both =
SLAs."<BR><SPAN=20
  class=3D923542309-17012006><FONT face=3DArial color=3D#0000ff =
size=3D2>[BPN] OK,=20
  that's fine.</FONT></SPAN><BR><BR><BR>
  <BLOCKQUOTE TYPE=3D"CITE">5th paragraph: "the solution should" should =
the=20
    should be in capitals.&nbsp; Is this paragraph a requirement that =
also needs=20
    to be included in appendix A?<BR><BR></BLOCKQUOTE>As already =
suggested, I=20
  changed it to a MAY.<BR>Requirement summary will be updated =
soon.<BR><BR><BR>
  <BLOCKQUOTE TYPE=3D"CITE">Section 5.1.6:<BR><BR>&nbsp;<BR><BR>3rd =
paragraph:=20
    Suggest rewording/reorganising as follows: "The monitoring of =
multicast=20
    specific parameters and statistics <S><FONT=20
    color=3D#ff0000>SHOULD</FONT></S><FONT color=3D#ff0000> </FONT><FONT =

    color=3D#ff0000><B>MUST</B></FONT><FONT color=3D#ff0000> =
</FONT>include <S><FONT=20
    color=3D#ff0000>:</FONT></S><BR><BR><FONT=20
    color=3D#ff0000>&nbsp;</FONT><BR><BR><S><FONT =
color=3D#ff0000>&nbsp;&nbsp;=20
    o&nbsp; </FONT></S><FONT color=3D#ff0000>multicast</FONT> traffic =
statistics:=20
    total traffic conveyed, =
incoming,<BR><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    outgoing, dropped, etc., by period of time<S><FONT color=3D#ff0000> =
(as a=20
    MUST)</FONT></S><BR><BR>&nbsp;<BR><BR><FONT color=3D#ff0000>The =
monitoring of=20
    multicast specific parameters and statistics MAY include</FONT>=20
    <BR><BR><S><FONT color=3D#ff0000>&nbsp;&nbsp; o&nbsp; =
</FONT></S><FONT=20
    color=3D#ff0000>IP</FONT> Performance Metrics related information =
(IPPM,=20
    [RFC2330]) that<BR><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; is relevant to =
the=20
    multicast traffic usage: such=20
    information<BR><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; includes the =
one-way=20
    packet delay, the inter-packet =
delay<BR><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    variation, etc.<S><FONT color=3D#ff0000> (as a=20
  MAY)</FONT></S>"<BR></BLOCKQUOTE><BR>Made it one paragraph, as bullet =
lists=20
  with one item looks weird.<BR>But reshaping the thing was a good=20
  suggestion.<BR><BR><BR>Thank you again for your attention to detail=20
  =
!<BR><BR>Cheers,<BR><BR>-Thomas<BR><BR><BR><BR><BR>benjamin.niven-jenkins=
@bt.com:=20

  <BLOCKQUOTE TYPE=3D"CITE"><PRE><FONT color=3D#000000>Thomas Morin =
RD-CORE &lt;mailto:<A =
href=3D"mailto:thomas.morin@francetelecom.com">thomas.morin@francetelecom=
.com</A>&gt; wrote:</FONT>
<FONT color=3D#000000>&gt; Hi,</FONT>
<FONT color=3D#000000>&gt; </FONT>
<FONT color=3D#000000>&gt; <A =
href=3D"mailto:benjamin.niven-jenkins@bt.com">benjamin.niven-jenkins@bt.c=
om</A>:</FONT>
<FONT color=3D#000000>&gt;&gt; I recently sent the e-mail below to the =
L3VPN mailing list but it</FONT>
<FONT color=3D#000000>&gt;&gt; appears that the list server converted it =
to plain text and therefore</FONT>
<FONT color=3D#000000>&gt;&gt; mangled it a bit so I am forwarding it to =
you as RTF so that you can</FONT>
<FONT color=3D#000000>&gt;&gt; see my proposed comments and edits as =
originally intended.</FONT>
<FONT color=3D#000000>&gt; </FONT>
<FONT color=3D#000000>&gt; That's still appearing as plain text in my =
mailer.</FONT>
<FONT color=3D#000000>&gt; Would you mind sending us an attached file, =
or HTML ?</FONT>

<FONT color=3D#000000>OK.  See attached for word &amp; HTML documents =
with the original e-mail in.</FONT>

<FONT color=3D#000000>Ben</FONT>
</PRE></BLOCKQUOTE></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C61B49.5EE8F4E8--




From l3vpn-bounces@ietf.org Tue Jan 17 04:47:57 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EynRV-0001Xi-Ud; Tue, 17 Jan 2006 04:47:57 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EynRU-0001XW-HU
	for l3vpn@megatron.ietf.org; Tue, 17 Jan 2006 04:47:56 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA00565
	for <l3vpn@ietf.org>; Tue, 17 Jan 2006 04:46:32 -0500 (EST)
Received: from p-mail2.rd.francetelecom.com ([195.101.245.16])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EynZZ-0006l0-Oh
	for l3vpn@ietf.org; Tue, 17 Jan 2006 04:56:19 -0500
Received: from ftrdmel10.rd.francetelecom.fr ([10.193.117.156]) by
	ftrdsmtp2.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.211); 
	Tue, 17 Jan 2006 10:47:52 +0100
Received: from l-at8613.rd.francetelecom.fr ([10.193.15.36]) by
	ftrdmel10.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.211); 
	Tue, 17 Jan 2006 10:47:52 +0100
From: Thomas Morin <thomas.morin@rd.francetelecom.com>
To: benjamin.niven-jenkins@bt.com
In-Reply-To: <F5AAFD21F2034349BF638211B5F27B0F06422598@i2km86-ukdy.domain1.systemhost.net>
References: <F5AAFD21F2034349BF638211B5F27B0F06422598@i2km86-ukdy.domain1.systemhost.net>
Content-Type: multipart/alternative; boundary="=-3ENHNL2GzIvom4wXObmE"
Organization: France Telecom R&D
Date: Tue, 17 Jan 2006 10:47:46 +0100
Message-Id: <1137491266.6296.21.camel@wintermute>
Mime-Version: 1.0
X-Mailer: Evolution 2.4.2.1 
X-OriginalArrivalTime: 17 Jan 2006 09:47:52.0094 (UTC)
	FILETIME=[1553ABE0:01C61B4B]
X-Spam-Score: 1.0 (+)
X-Scan-Signature: ccfb4541e989aa743998098cd315d0fd
Cc: l3vpn@ietf.org
Subject: RE: Review of draft-ietf-l3vpn-ppvpn-mcast-reqts-03
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: l3vpn.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:l3vpn@ietf.org>
List-Help: <mailto:l3vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=subscribe>
Sender: l3vpn-bounces@ietf.org
Errors-To: l3vpn-bounces@ietf.org


--=-3ENHNL2GzIvom4wXObmE
Content-Type: text/plain
Content-Transfer-Encoding: 7bit

Hi Benjamin,

benjamin.niven-jenkins@bt.com:

>         > 
>         > 
>         > 1st paragraph: "VPN services satisfying the requirement
>         > defined in" 
>         > 
>         > 
>         In fact, a plural was missing.
>          
>         [BPN] Then it should be "VPN services satifying the
>         requirements defined in" 

Ok.



>         > 
>         > Section 4.1:
>         
>         [...]
>         
>         > 2nd paragraph: "to impact most of the design"
>         > 
>         
>         The goal is to talk about things thay have a greater impact on
>         the design.
>         Would that be better english: "scenarios that are expected to
>         impact the most the design of a multicast VPN solution".
>          
>         [BPN] I believe my original proposal is the best English and
>         is in line with your goal to talk about things that have a
>         large impact on the design. 


I'm not sure. 
Maybe "scenarios are expected to have a greater impact on the design of
a solution" ?




>         > Section 5.1.2:
>         > 
>         > 1st paragraph: "Consequently to Section 3.1, the CEs and PEs
>         > CE-PE protocol SHOULD employ existing multicast protocols."
>         > These edits also need to be made to the copy of the
>         > requirement in Appendix A.  
>         > 
>         
>         Misunderstanding here: we can't reduce to one "CE-PE
>         protocol"; there can be many, e.g IGMP or PIM; and we don't
>         want either to invent a new CE-PE protocol that would reuse an
>         exisiting mcast protocol.
>          
>         [BPN] OK.  My concern is that by saying "CEs and PEs SHOULD
>         employ existing multicast protocols" implies that it is more
>         than the CE-PE protocol that you are referring to - i.e. that
>         you are implying that the PE-PE and MDT tunnel establishment
>         protocols SHOULD also use existing protocols.  How about
>         something like "the CEs and PEs SHOULD employ existing
>         multicast protocols for communication with each other"?


I see your point now.
Maybe "[..] multicast-related protocol exchanges between a CE and its
directly connected PE should happen via existing multicast
protocols:"  ?

Thanks,

-Thomas


--=-3ENHNL2GzIvom4wXObmE
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 7bit

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
  <META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
  <META NAME="GENERATOR" CONTENT="GtkHTML/3.8.1">
</HEAD>
<BODY>
Hi Benjamin,<BR>
<BR>
benjamin.niven-jenkins@bt.com:
<BR>
<BLOCKQUOTE TYPE=CITE>
    <BLOCKQUOTE>
        <BLOCKQUOTE TYPE=CITE>
            <BR>
            <FONT COLOR="#000000">1st paragraph: &quot;VPN services satisfying </FONT><B><FONT COLOR="#ff0000">the</FONT></B><FONT COLOR="#000000"> requirement defined in&quot; </FONT><BR>
            <BR>
        </BLOCKQUOTE>
    </BLOCKQUOTE>
</BLOCKQUOTE>
<BLOCKQUOTE TYPE=CITE>
    <BLOCKQUOTE>
        <FONT COLOR="#000000">In fact, a plural was missing.</FONT><BR>
        <FONT SIZE="2"><FONT COLOR="#0000ff">&nbsp;</FONT></FONT>
    </BLOCKQUOTE>
</BLOCKQUOTE>
<BLOCKQUOTE TYPE=CITE>
    <BLOCKQUOTE>
        [BPN] Then it should be &quot;VPN services satifying the requirements defined in&quot;<FONT COLOR="#000000"> </FONT><BR>
    </BLOCKQUOTE>
</BLOCKQUOTE>
Ok.<BR>
<BR>
<BR>
<BR>
<BLOCKQUOTE TYPE=CITE>
    <BLOCKQUOTE>
        <BLOCKQUOTE TYPE=CITE>
            <FONT COLOR="#000000">Section 4.1:</FONT><BR>
        </BLOCKQUOTE>
        <FONT COLOR="#000000">[...]</FONT><BR>
        <BLOCKQUOTE TYPE=CITE>
            <FONT COLOR="#000000">2nd paragraph: &quot;to impact most </FONT><B><FONT COLOR="#ff0000">of</FONT></B><FONT COLOR="#000000"> the design&quot;</FONT>
        </BLOCKQUOTE>
    </BLOCKQUOTE>
</BLOCKQUOTE>
<BLOCKQUOTE TYPE=CITE>
    <BLOCKQUOTE>
        <BR>
        <FONT COLOR="#000000">The goal is to talk about things thay have a greater impact on the design.</FONT><BR>
        <FONT COLOR="#000000">Would that be better english: &quot;scenarios that are expected to impact the most the design of a multicast VPN solution&quot;.</FONT><BR>
        <FONT SIZE="2"><FONT COLOR="#0000ff">&nbsp;</FONT></FONT>
    </BLOCKQUOTE>
</BLOCKQUOTE>
<BLOCKQUOTE TYPE=CITE>
    <BLOCKQUOTE>
        [BPN] I believe my original proposal is the best English and is in line with your goal to talk about things that have a large impact on the design.<FONT COLOR="#000000"> </FONT><BR>
    </BLOCKQUOTE>
</BLOCKQUOTE>
<BR>
I'm not sure. <BR>
Maybe &quot;scenarios are expected to have a greater impact on the design of a solution&quot; ?<BR>
<BR>
<BR>
<BR>
<BLOCKQUOTE TYPE=CITE>
    <BLOCKQUOTE>
        <BLOCKQUOTE TYPE=CITE>
            <FONT COLOR="#000000">Section 5.1.2:</FONT><BR>
            <BR>
            <FONT COLOR="#000000">1st paragraph: &quot;Consequently to Section 3.1, the </FONT><S><FONT COLOR="#ff0000">CEs and PEs</FONT></S><FONT COLOR="#ff0000"> </FONT><FONT COLOR="#ff0000"><B>CE-PE protocol</B></FONT><FONT COLOR="#000000"> SHOULD employ existing multicast protocols.&quot; These edits also need to be made to the copy of the requirement in Appendix A.&nbsp; </FONT>
        </BLOCKQUOTE>
    </BLOCKQUOTE>
</BLOCKQUOTE>
<BLOCKQUOTE TYPE=CITE>
    <BLOCKQUOTE>
        <BR>
        <FONT COLOR="#000000">Misunderstanding here: we can't reduce to one &quot;</FONT><FONT COLOR="#000000"><B>CE-PE protocol</B></FONT><FONT COLOR="#000000">&quot;; there can be many, e.g IGMP or PIM; and we don't want either to invent a new CE-PE protocol that would reuse an exisiting mcast protocol.</FONT><BR>
        <FONT SIZE="2"><FONT COLOR="#0000ff">&nbsp;</FONT></FONT>
    </BLOCKQUOTE>
</BLOCKQUOTE>
<BLOCKQUOTE TYPE=CITE>
    <BLOCKQUOTE>
        <FONT SIZE="2"><FONT COLOR="#0000ff">[BPN] OK.&nbsp; My concern is that by saying &quot;CEs and PEs SHOULD employ existing multicast protocols&quot; implies that it is more than the CE-PE protocol that you are referring to - i.e. that you are implying that the PE-PE and MDT tunnel establishment protocols SHOULD also use existing protocols.&nbsp; How about something like &quot;the CEs and PEs SHOULD employ existing multicast protocols for communication with each other&quot;?</FONT></FONT><BR>
    </BLOCKQUOTE>
</BLOCKQUOTE>
<BR>
I see your point now.<BR>
Maybe &quot;[..] multicast-related protocol exchanges between a CE and its directly connected PE should happen via existing multicast protocols:&quot;&nbsp; ?<BR>
<BR>
Thanks,<BR>
<BR>
-Thomas
<PRE>

</PRE>
</BODY>
</HTML>

--=-3ENHNL2GzIvom4wXObmE--





From l3vpn-bounces@ietf.org Tue Jan 17 05:04:24 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EynhQ-0005ZI-T5; Tue, 17 Jan 2006 05:04:24 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EynhP-0005ZC-6e
	for l3vpn@megatron.ietf.org; Tue, 17 Jan 2006 05:04:23 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA01357
	for <l3vpn@ietf.org>; Tue, 17 Jan 2006 05:02:59 -0500 (EST)
Received: from p-mail2.rd.francetelecom.com ([195.101.245.16])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EynpV-0007QK-Mc
	for l3vpn@ietf.org; Tue, 17 Jan 2006 05:12:46 -0500
Received: from ftrdmel10.rd.francetelecom.fr ([10.193.117.156]) by
	ftrdsmtp1.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.211); 
	Tue, 17 Jan 2006 11:04:17 +0100
Received: from l-at8613.rd.francetelecom.fr ([10.193.15.36]) by
	ftrdmel10.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.211); 
	Tue, 17 Jan 2006 11:04:17 +0100
From: Thomas Morin <thomas.morin@rd.francetelecom.com>
To: Yiqun Cai <ycai@cisco.com>
In-Reply-To: <2F7ADC25-9746-4E1E-A947-871761CC4C6D@cisco.com>
References: <200601151540.k0FFeF583898@merlot.juniper.net>
	<1137419379.15352.143.camel@wintermute>
	<2F7ADC25-9746-4E1E-A947-871761CC4C6D@cisco.com>
Content-Type: text/plain
Organization: France Telecom R&D
Date: Tue, 17 Jan 2006 11:04:11 +0100
Message-Id: <1137492252.6296.38.camel@wintermute>
Mime-Version: 1.0
X-Mailer: Evolution 2.4.2.1 
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 17 Jan 2006 10:04:17.0740 (UTC)
	FILETIME=[60D150C0:01C61B4D]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cd26b070c2577ac175cd3a6d878c6248
Content-Transfer-Encoding: 7bit
Cc: L3VPN <l3vpn@ietf.org>
Subject: Re: WG last call: draft-ietf-l3vpn-ppvpn-mcast-reqts-03
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: l3vpn.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:l3vpn@ietf.org>
List-Help: <mailto:l3vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=subscribe>
Sender: l3vpn-bounces@ietf.org
Errors-To: l3vpn-bounces@ietf.org

Hi Yiqun,

The idea, I think, is to have the ability to have a VRF be associated to
multiple VPNs, independently for multicast and unicast, and also
independently for emission and reception.

First point : unicast is not dependent on multicast. So you may very
well want to have a VRF be associated to a VPN for unicast without
activating multicast reception from (or multicast emission to) this VPN.

Second point : as you explain, multicast reception is dependent on
unicast for RPF. However, if you want to emit mcast from a VRF to a VPN,
you don't depend on unicast (no need to have the routes of that VPN in
your VRF).  Thus, you could activate multicast emission to a VPN without
importing its routes into your VRF (just VRFs of that VPN will import
your routes).

I think its important for security aspects, to have full-control of what
routes you import/export and of which VPN you associate to for
emission/redeption.  Here, having coupling (being forced to activate a
broad scope feature, only to use a subset) would not be good I think.

Cheers,

-Thomas


Yiqun Cai:
> I have some doubt regarding this.
> 
> By "extranet multicast connectivity",  do you mean procedure of RPF  
> to the
> source,  the distribution of multicast data traffic to the receivers  
> in different
> VPNs, or something else.
> 
> Multicast RPF is built based on unicast routing information.  So  
> there is a
> dependancy existing today.  A solution does provide more flexibility  
> if it allows
> RPF to be independent of unicast routing,  but I dont see it as a  
> "must".
> 
> For distribution of multicast data,  since they are controlled by  
> join/prune
> messages,  they are independent of unicast data distribution in nature.
> So I don't see how this bullet is applicable.
> 
> If it is something else,  could you please elaborate?
> 
> Thanks a lot.
> 
> On Jan 16, 2006, at 5:49 AM, Thomas Morin wrote:
> 
> > Hello Yakov,
> >
> > Yakov Rekhter:
> >> In 5.1.7 I would suggest to add the following to the bullet list:
> >>
> >>       A solution must allow to control an extranet multicast
> >>       connectivity independently from the extranet unicast
> >>       connectivity
> >
> > Agreed.
> > I just used capitalized "MUST" instead of "must".
> >
> > Cheers,
> >
> > -Thomas
> >
> >
> 
> 
> 
> --
> Yiqun
> 
> 





From l3vpn-bounces@ietf.org Tue Jan 17 05:04:48 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Eynho-0005bh-RF; Tue, 17 Jan 2006 05:04:48 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Eynhn-0005bY-HJ
	for l3vpn@megatron.ietf.org; Tue, 17 Jan 2006 05:04:47 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA01375
	for <l3vpn@ietf.org>; Tue, 17 Jan 2006 05:03:23 -0500 (EST)
From: benjamin.niven-jenkins@bt.com
Received: from smtp4.smtp.bt.com ([217.32.164.151])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Eynpt-0007QS-Ng
	for l3vpn@ietf.org; Tue, 17 Jan 2006 05:13:10 -0500
Received: from i2km97-ukbr.domain1.systemhost.net ([193.113.197.30]) by
	smtp4.smtp.bt.com with Microsoft SMTPSVC(6.0.3790.211); 
	Tue, 17 Jan 2006 10:04:30 +0000
Received: from i2km86-ukdy.domain1.systemhost.net ([193.113.30.79]) by
	i2km97-ukbr.domain1.systemhost.net with Microsoft
	SMTPSVC(5.0.2195.6713); Tue, 17 Jan 2006 10:04:29 +0000
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C61B4D.67C5DDA8"
Date: Tue, 17 Jan 2006 10:04:28 -0000
Message-ID: <F5AAFD21F2034349BF638211B5F27B0F06422653@i2km86-ukdy.domain1.systemhost.net>
Thread-Topic: Review of draft-ietf-l3vpn-ppvpn-mcast-reqts-03
Thread-Index: AcYbSyrAUOWkuuptR3On1zRu7VFz7gAAgCXw
To: <thomas.morin@rd.francetelecom.com>
X-OriginalArrivalTime: 17 Jan 2006 10:04:29.0947 (UTC)
	FILETIME=[6817F4B0:01C61B4D]
X-Spam-Score: 1.3 (+)
X-Scan-Signature: ba0d4c5f57f7c289496fce758bbf4798
Cc: l3vpn@ietf.org
Subject: RE: Review of draft-ietf-l3vpn-ppvpn-mcast-reqts-03
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: l3vpn.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:l3vpn@ietf.org>
List-Help: <mailto:l3vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=subscribe>
Sender: l3vpn-bounces@ietf.org
Errors-To: l3vpn-bounces@ietf.org

This is a multi-part message in MIME format.

------_=_NextPart_001_01C61B4D.67C5DDA8
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Thomas,
=20
See in-line.  My comments are marked [BPN].
=20
Ben


________________________________

	From: Thomas Morin [mailto:thomas.morin@rd.francetelecom.com]=20
	Sent: Tuesday, January 17, 2006 9:48 AM
	To: Niven-jenkins,B,Ben,XDE73 R
	Cc: l3vpn@ietf.org
	Subject: RE: Review of draft-ietf-l3vpn-ppvpn-mcast-reqts-03
=09
=09
	Hi Benjamin,
=09
	benjamin.niven-jenkins@bt.com:=20
=09


				1st paragraph: "VPN services satisfying
the requirement defined in"=20
			=09
			=09

			In fact, a plural was missing.
			 =20

			[BPN] Then it should be "VPN services satifying
the requirements defined in"=20
		=09

	Ok.
=09
=09
=09
=09

				Section 4.1:
			=09

			[...]
		=09

				2nd paragraph: "to impact most of the
design"=20


			The goal is to talk about things thay have a
greater impact on the design.
			Would that be better english: "scenarios that
are expected to impact the most the design of a multicast VPN solution".
			 =20

			[BPN] I believe my original proposal is the best
English and is in line with your goal to talk about things that have a
large impact on the design.=20
		=09


	I'm not sure.=20
	Maybe "scenarios are expected to have a greater impact on the
design of a solution" ?
	=20
	[BPN] Greater impact than what?  How about "scenarios that are
expected to have a large impact on the design of a solution"?=20
=09
=09
=09

				Section 5.1.2:
			=09
				1st paragraph: "Consequently to Section
3.1, the CEs and PEs CE-PE protocol SHOULD employ existing multicast
protocols." These edits also need to be made to the copy of the
requirement in Appendix A. =20


			Misunderstanding here: we can't reduce to one
"CE-PE protocol"; there can be many, e.g IGMP or PIM; and we don't want
either to invent a new CE-PE protocol that would reuse an exisiting
mcast protocol.
			 =20

			[BPN] OK.  My concern is that by saying "CEs and
PEs SHOULD employ existing multicast protocols" implies that it is more
than the CE-PE protocol that you are referring to - i.e. that you are
implying that the PE-PE and MDT tunnel establishment protocols SHOULD
also use existing protocols.  How about something like "the CEs and PEs
SHOULD employ existing multicast protocols for communication with each
other"?
		=09


	I see your point now.
	Maybe "[..] multicast-related protocol exchanges between a CE
and its directly connected PE should happen via existing multicast
protocols:"  ?
	=20
	[BPN] OK.  That's fine.
	=20
	Thanks,
=09
	-Thomas=20
=09


------_=_NextPart_001_01C61B4D.67C5DDA8
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2800.1522" name=3DGENERATOR></HEAD>
<BODY>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D010480210-17012006><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Thomas,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D010480210-17012006><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D010480210-17012006><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>See in-line.&nbsp; My comments are marked=20
[BPN].</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D010480210-17012006><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D010480210-17012006><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Ben</FONT></SPAN></DIV><BR>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px =
solid; MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
  <HR tabIndex=3D-1>
  <FONT face=3DTahoma size=3D2><B>From:</B> Thomas Morin=20
  [mailto:thomas.morin@rd.francetelecom.com] <BR><B>Sent:</B> Tuesday, =
January=20
  17, 2006 9:48 AM<BR><B>To:</B> Niven-jenkins,B,Ben,XDE73 =
R<BR><B>Cc:</B>=20
  l3vpn@ietf.org<BR><B>Subject:</B> RE: Review of=20
  draft-ietf-l3vpn-ppvpn-mcast-reqts-03<BR></FONT><BR></DIV>
  <DIV></DIV>Hi Benjamin,<BR><BR>benjamin.niven-jenkins@bt.com: <BR>
  <BLOCKQUOTE TYPE=3D"CITE">
    <BLOCKQUOTE>
      <BLOCKQUOTE TYPE=3D"CITE"><BR><FONT color=3D#000000>1st paragraph: =
"VPN=20
        services satisfying </FONT><B><FONT =
color=3D#ff0000>the</FONT></B><FONT=20
        color=3D#000000> requirement defined in"=20
    </FONT><BR><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
  <BLOCKQUOTE TYPE=3D"CITE">
    <BLOCKQUOTE><FONT color=3D#000000>In fact, a plural was=20
      missing.</FONT><BR><FONT size=3D2><FONT =
color=3D#0000ff>&nbsp;</FONT></FONT>=20
    </BLOCKQUOTE></BLOCKQUOTE>
  <BLOCKQUOTE TYPE=3D"CITE">
    <BLOCKQUOTE>[BPN] Then it should be "VPN services satifying the=20
      requirements defined in"<FONT color=3D#000000>=20
  </FONT><BR></BLOCKQUOTE></BLOCKQUOTE>Ok.<BR><BR><BR><BR>
  <BLOCKQUOTE TYPE=3D"CITE">
    <BLOCKQUOTE>
      <BLOCKQUOTE TYPE=3D"CITE"><FONT color=3D#000000>Section=20
      4.1:</FONT><BR></BLOCKQUOTE><FONT color=3D#000000>[...]</FONT><BR>
      <BLOCKQUOTE TYPE=3D"CITE"><FONT color=3D#000000>2nd paragraph: "to =
impact=20
        most </FONT><B><FONT color=3D#ff0000>of</FONT></B><FONT =
color=3D#000000> the=20
        design"</FONT> </BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
  <BLOCKQUOTE TYPE=3D"CITE">
    <BLOCKQUOTE><BR><FONT color=3D#000000>The goal is to talk about =
things thay=20
      have a greater impact on the design.</FONT><BR><FONT =
color=3D#000000>Would=20
      that be better english: "scenarios that are expected to impact the =
most=20
      the design of a multicast VPN solution".</FONT><BR><FONT =
size=3D2><FONT=20
      color=3D#0000ff>&nbsp;</FONT></FONT> </BLOCKQUOTE></BLOCKQUOTE>
  <BLOCKQUOTE TYPE=3D"CITE">
    <BLOCKQUOTE>[BPN] I believe my original proposal is the best English =
and=20
      is in line with your goal to talk about things that have a large =
impact on=20
      the design.<FONT color=3D#000000> =
</FONT><BR></BLOCKQUOTE></BLOCKQUOTE>
  <DIV><BR>I'm not sure. <BR>Maybe "scenarios are expected to have a =
greater=20
  impact on the design of a solution" ?<BR><SPAN =
class=3D010480210-17012006><FONT=20
  face=3DArial color=3D#0000ff size=3D2>&nbsp;</FONT></SPAN></DIV>
  <DIV><SPAN class=3D010480210-17012006><FONT face=3DArial =
color=3D#0000ff=20
  size=3D2>[BPN] Greater impact than what?&nbsp; How about "scenarios =
that are=20
  expected to have a large impact on the design of=20
  a&nbsp;solution"?</FONT></SPAN><SPAN=20
  class=3D010480210-17012006>&nbsp;</SPAN><BR><BR><BR></DIV>
  <BLOCKQUOTE TYPE=3D"CITE">
    <BLOCKQUOTE>
      <BLOCKQUOTE TYPE=3D"CITE"><FONT color=3D#000000>Section=20
        5.1.2:</FONT><BR><BR><FONT color=3D#000000>1st paragraph: =
"Consequently to=20
        Section 3.1, the </FONT><S><FONT color=3D#ff0000>CEs and=20
        PEs</FONT></S><FONT color=3D#ff0000> </FONT><FONT =
color=3D#ff0000><B>CE-PE=20
        protocol</B></FONT><FONT color=3D#000000> SHOULD employ existing =
multicast=20
        protocols." These edits also need to be made to the copy of the=20
        requirement in Appendix A.&nbsp;=20
</FONT></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
  <BLOCKQUOTE TYPE=3D"CITE">
    <BLOCKQUOTE><BR><FONT color=3D#000000>Misunderstanding here: we =
can't reduce=20
      to one "</FONT><FONT color=3D#000000><B>CE-PE =
protocol</B></FONT><FONT=20
      color=3D#000000>"; there can be many, e.g IGMP or PIM; and we =
don't want=20
      either to invent a new CE-PE protocol that would reuse an =
exisiting mcast=20
      protocol.</FONT><BR><FONT size=3D2><FONT =
color=3D#0000ff>&nbsp;</FONT></FONT>=20
    </BLOCKQUOTE></BLOCKQUOTE>
  <BLOCKQUOTE TYPE=3D"CITE">
    <BLOCKQUOTE><FONT size=3D2><FONT color=3D#0000ff>[BPN] OK.&nbsp; My =
concern is=20
      that by saying "CEs and PEs SHOULD employ existing multicast =
protocols"=20
      implies that it is more than the CE-PE protocol that you are =
referring to=20
      - i.e. that you are implying that the PE-PE and MDT tunnel =
establishment=20
      protocols SHOULD also use existing protocols.&nbsp; How about =
something=20
      like "the CEs and PEs SHOULD employ existing multicast protocols =
for=20
      communication with each =
other"?</FONT></FONT><BR></BLOCKQUOTE></BLOCKQUOTE>
  <DIV><BR>I see your point now.<BR>Maybe "[..] multicast-related =
protocol=20
  exchanges between a CE and its directly connected PE should happen via =

  existing multicast protocols:"&nbsp; ?<BR><SPAN =
class=3D010480210-17012006><FONT=20
  face=3DArial color=3D#0000ff size=3D2>&nbsp;</FONT></SPAN></DIV>
  <DIV><SPAN class=3D010480210-17012006><FONT face=3DArial =
color=3D#0000ff=20
  size=3D2>[BPN] OK.&nbsp; That's fine.</FONT></SPAN></DIV>
  <DIV><SPAN =
class=3D010480210-17012006>&nbsp;</SPAN><BR>Thanks,<BR><BR>-Thomas=20
  </DIV><PRE>
</PRE></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C61B4D.67C5DDA8--




From l3vpn-bounces@ietf.org Tue Jan 17 05:33:31 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Eyo9b-0007OV-Sz; Tue, 17 Jan 2006 05:33:31 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Eyo9Z-0007OC-OK
	for l3vpn@megatron.ietf.org; Tue, 17 Jan 2006 05:33:29 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA03230
	for <l3vpn@ietf.org>; Tue, 17 Jan 2006 05:32:05 -0500 (EST)
Received: from p-mail2.rd.francetelecom.com ([195.101.245.16])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EyoHe-0008Sq-K3
	for l3vpn@ietf.org; Tue, 17 Jan 2006 05:41:52 -0500
Received: from ftrdmel10.rd.francetelecom.fr ([10.193.117.156]) by
	ftrdsmtp1.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.211); 
	Tue, 17 Jan 2006 11:33:25 +0100
Received: from l-at8613.rd.francetelecom.fr ([10.193.15.36]) by
	ftrdmel10.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.211); 
	Tue, 17 Jan 2006 11:33:25 +0100
From: Thomas Morin <thomas.morin@rd.francetelecom.com>
To: benjamin.niven-jenkins@bt.com
In-Reply-To: <F5AAFD21F2034349BF638211B5F27B0F06422653@i2km86-ukdy.domain1.systemhost.net>
References: <F5AAFD21F2034349BF638211B5F27B0F06422653@i2km86-ukdy.domain1.systemhost.net>
Content-Type: text/plain
Organization: France Telecom R&D
Date: Tue, 17 Jan 2006 11:33:19 +0100
Message-Id: <1137494000.6296.41.camel@wintermute>
Mime-Version: 1.0
X-Mailer: Evolution 2.4.2.1 
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 17 Jan 2006 10:33:25.0705 (UTC)
	FILETIME=[72AF9B90:01C61B51]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a
Content-Transfer-Encoding: 7bit
Cc: l3vpn@ietf.org
Subject: RE: Review of draft-ietf-l3vpn-ppvpn-mcast-reqts-03
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: l3vpn.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:l3vpn@ietf.org>
List-Help: <mailto:l3vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=subscribe>
Sender: l3vpn-bounces@ietf.org
Errors-To: l3vpn-bounces@ietf.org

Hi Benjamin,

benjamin.niven-jenkins@bt.com:
>         >         > Section 4.1:
>         >         [...]
>         >         > 2nd paragraph: "to impact most of the design" 
>         >         
>         >         The goal is to talk about things thay have a greater
>         >         impact on the design.
>         >         Would that be better english: "scenarios that are
>         >         expected to impact the most the design of a
>         >         multicast VPN solution".
>         >           
>         >         [BPN] I believe my original proposal is the best
>         >         English and is in line with your goal to talk about
>         >         things that have a large impact on the design. 
>         
>         I'm not sure. 
>         Maybe "scenarios are expected to have a greater impact on the
>         design of a solution" ?
>          
>         [BPN] Greater impact than what?  How about "scenarios that are
>         expected to have a large impact on the design of a solution"? 

Yes, fine.
Thank you again for your careful review.

-Thomas






From l3vpn-bounces@ietf.org Tue Jan 17 10:57:52 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EytDU-0008CP-RV; Tue, 17 Jan 2006 10:57:52 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EytDS-0008Bx-Qm
	for l3vpn@megatron.ietf.org; Tue, 17 Jan 2006 10:57:50 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA26394
	for <l3vpn@ietf.org>; Tue, 17 Jan 2006 10:56:26 -0500 (EST)
Received: from m106.maoz.com ([205.167.76.9])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EytLb-0005Ta-AI
	for l3vpn@ietf.org; Tue, 17 Jan 2006 11:06:16 -0500
Received: from m106.maoz.com (localhost.localdomain [127.0.0.1])
	by m106.maoz.com (8.13.4/8.13.4) with ESMTP id k0HFvch9028304;
	Tue, 17 Jan 2006 07:57:38 -0800
Received: (from dmm@localhost)
	by m106.maoz.com (8.13.4/8.12.11/Submit) id k0HFvX0e028298;
	Tue, 17 Jan 2006 07:57:33 -0800
X-Authentication-Warning: m106.maoz.com: dmm set sender to dmm@1-4-5.net using
	-f
Date: Tue, 17 Jan 2006 07:57:33 -0800
From: David Meyer <dmm@1-4-5.net>
To: Marshall Eubanks <marshall.eubanks@gmail.com>
Message-ID: <20060117155733.GA28261@1-4-5.net>
References: <43BBE0D5.2060607@juniper.net>
	<dcad22d80601102236u373871a7qb6f7636e5b7bbfcd@mail.gmail.com>
	<1137417200.15352.113.camel@wintermute>
	<dcad22d80601161836u4783b79m5d59cb06cb374f07@mail.gmail.com>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="FL5UXtIhxfXey3p5"
Content-Disposition: inline
In-Reply-To: <dcad22d80601161836u4783b79m5d59cb06cb374f07@mail.gmail.com>
User-Agent: Mutt/1.4.1i
X-public-key: http://www.1-4-5.net/~dmm/public-key.asc
X-gpg-fingerprint: 2409 8B50 B389 A307 BA5C 2A16 3918 03D6 A099 D8A7
X-philosophy: "I find your lack of faith disturbing." -- Darth Vader,
	Star Wars Episode IV.
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2
Cc: Thomas Morin <thomas.morin@rd.francetelecom.com>, l3vpn@ietf.org
Subject: Re: WG last call: draft-ietf-l3vpn-ppvpn-mcast-reqts-03
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: l3vpn.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:l3vpn@ietf.org>
List-Help: <mailto:l3vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=subscribe>
Sender: l3vpn-bounces@ietf.org
Errors-To: l3vpn-bounces@ietf.org


--FL5UXtIhxfXey3p5
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

> And, I have never seen  "capillarity" actually used in English. It's
> in the dictionary, even in my spell checker, and it might be used in
> botany, but it's not used metaphorically.


	As I was mentioning to Marshall earlier, actually, the
	term capillarity is in common use in the carrier industry
	(usually used to describe the extent and density of a
	carrier's transport network). As such, I don't find the
	fact the google doesn't know that disqualifying, and
	further, most of us who have worked in that side of the
	industry consider it common usage.

	Dave

--FL5UXtIhxfXey3p5
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFDzRPtORgD1qCZ2KcRAkCxAKCJRR5IItaS426F/Y3xD/q4LZ9ZlgCfRrGD
FS+ukrdNnHjIbF5MEf6wdhM=
=P+Yx
-----END PGP SIGNATURE-----

--FL5UXtIhxfXey3p5--




From l3vpn-bounces@ietf.org Tue Jan 17 16:22:35 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EyyHj-0006re-Bi; Tue, 17 Jan 2006 16:22:35 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EyyHh-0006rG-Eb
	for l3vpn@megatron.ietf.org; Tue, 17 Jan 2006 16:22:33 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA24898
	for <l3vpn@ietf.org>; Tue, 17 Jan 2006 16:21:07 -0500 (EST)
Received: from zproxy.gmail.com ([64.233.162.199])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EyyPs-0000z8-TC
	for l3vpn@ietf.org; Tue, 17 Jan 2006 16:31:02 -0500
Received: by zproxy.gmail.com with SMTP id 9so1460632nzo
	for <l3vpn@ietf.org>; Tue, 17 Jan 2006 13:22:30 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
	h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=lYJJPdzWIyNHezfX8h0g+HF1PmhQWE/sy0cKXhFs5+DU6V1rQlsFdu+PYXouao+DhpToNfwPDP6QHLESuqJp3ccAKOvzeUsWM8GYquPLNihBP/5YgGI/QmtSPeEDrt6zv8tY5ascs9JZ3d4zgRngAvBqR2Cu9LWij7u+hI+c9Z4=
Received: by 10.36.39.5 with SMTP id m5mr6004584nzm;
	Tue, 17 Jan 2006 13:22:29 -0800 (PST)
Received: by 10.36.46.2 with HTTP; Tue, 17 Jan 2006 13:22:29 -0800 (PST)
Message-ID: <dcad22d80601171322n58125885gf4a779a0e831e0dc@mail.gmail.com>
Date: Tue, 17 Jan 2006 16:22:29 -0500
From: Marshall Eubanks <marshall.eubanks@gmail.com>
To: David Meyer <dmm@1-4-5.net>
In-Reply-To: <20060117155733.GA28261@1-4-5.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <43BBE0D5.2060607@juniper.net>
	<dcad22d80601102236u373871a7qb6f7636e5b7bbfcd@mail.gmail.com>
	<1137417200.15352.113.camel@wintermute>
	<dcad22d80601161836u4783b79m5d59cb06cb374f07@mail.gmail.com>
	<20060117155733.GA28261@1-4-5.net>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228
Content-Transfer-Encoding: quoted-printable
Cc: Thomas Morin <thomas.morin@rd.francetelecom.com>, l3vpn@ietf.org
Subject: Re: WG last call: draft-ietf-l3vpn-ppvpn-mcast-reqts-03
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: l3vpn.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:l3vpn@ietf.org>
List-Help: <mailto:l3vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=subscribe>
Sender: l3vpn-bounces@ietf.org
Errors-To: l3vpn-bounces@ietf.org

Well, a google on the "capillarity of carrier network" (without the
quotes) does return 653 hits, so Dave is correct in that it is used
that way at least some, and I appreciate the education.

However, note that capillarity is not (in English) the "quality or
state of being capillary" but is simply a noun describing the
phenomenon itself,  so I do not regard the above as proper English
usage and I would recommend against its use in a standards document.

Regards
Marshall


On 1/17/06, David Meyer <dmm@1-4-5.net> wrote:
> > And, I have never seen  "capillarity" actually used in English. It's
> > in the dictionary, even in my spell checker, and it might be used in
> > botany, but it's not used metaphorically.
>
>
>         As I was mentioning to Marshall earlier, actually, the
>         term capillarity is in common use in the carrier industry
>         (usually used to describe the extent and density of a
>         carrier's transport network). As such, I don't find the
>         fact the google doesn't know that disqualifying, and
>         further, most of us who have worked in that side of the
>         industry consider it common usage.
>
>         Dave
>
>
>




From l3vpn-bounces@ietf.org Tue Jan 17 17:02:26 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EyyuI-0005tW-TA; Tue, 17 Jan 2006 17:02:26 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EymKJ-0003LT-Ug
	for l3vpn@megatron.ietf.org; Tue, 17 Jan 2006 03:36:28 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA27004
	for <l3vpn@ietf.org>; Tue, 17 Jan 2006 03:35:02 -0500 (EST)
Received: from netcore.fi ([193.94.160.1])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EymSP-0004P2-Al
	for l3vpn@ietf.org; Tue, 17 Jan 2006 03:44:50 -0500
Received: from netcore.fi (localhost [127.0.0.1])
	by netcore.fi (8.12.8/8.12.8) with ESMTP id k0H8aEYG000540
	for <l3vpn@ietf.org>; Tue, 17 Jan 2006 10:36:14 +0200
Received: from localhost (pekkas@localhost)
	by netcore.fi (8.12.8/8.12.8/Submit) with ESMTP id k0H8aEZY000537
	for <l3vpn@ietf.org>; Tue, 17 Jan 2006 10:36:14 +0200
Date: Tue, 17 Jan 2006 10:36:14 +0200 (EET)
From: Pekka Savola <pekkas@netcore.fi>
To: l3vpn@ietf.org
Message-ID: <Pine.LNX.4.64.0601171035090.32168@netcore.fi>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-Virus-Scanned: ClamAV 0.87.1/1243/Sun Jan 15 20:35:18 2006 on otso.netcore.fi
X-Virus-Status: Clean
X-Spam-Status: No, score=-1.4 required=5.0 tests=ALL_TRUSTED autolearn=failed 
	version=3.1.0
X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on otso.netcore.fi
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2a76bcd37b1c8a21336eb0a1ea6bbf48
X-Mailman-Approved-At: Tue, 17 Jan 2006 17:02:25 -0500
Subject: Re: comments on draft-ietf-l3vpn-ppvpn-mcast-reqts-03 (fwd)
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: l3vpn.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:l3vpn@ietf.org>
List-Help: <mailto:l3vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=subscribe>
Sender: l3vpn-bounces@ietf.org
Errors-To: l3vpn-bounces@ietf.org

Re-sending as this was probably accidentally rejected by the list 
administrator (for the policy, see 
http://www.ietf.org/IESG/STATEMENTS/mail-submit-policy.txt).

---------- Forwarded message ----------
Date: Mon, 16 Jan 2006 18:02:17 +0200 (EET)
From: Pekka Savola <pekkas@netcore.fi>
To: Thomas Morin <thomas.morin@rd.francetelecom.com>
Cc: l3vpn@ietf.org
Subject: Re: comments on draft-ietf-l3vpn-ppvpn-mcast-reqts-03

Inline (I've cut off some parts which we agree on),

On Mon, 16 Jan 2006, Thomas Morin wrote:
> Pekka Savola:
>> 5.1.2.  CE-PE Multicast routing and management protocols
>>
>>     When IPv6 is supported by a VPN solution, relevant IPv6 corresponding
>>     protocols MUST also be supported, e.g.  Multicast Listener Discovery
>>     Protocol (MLD) (v1 [RFC2710]], v2 [RFC3810]]).
>> 
>> ==> The IPv6 part requires wordsmithing.  The IETF will *NOT* allow
>> specification of a standards track solution which does not support
>> IPv6.  This text seems to imply that IPv6 support could be optional.
> 
> Well, the draft aims at being v4/v6 generic, and is not supposed to let
> the reader think that IPv6 support is optional for a multicast VPN
> solution.  It aims at saying that IPv6 multicast support is required for
> a _VPN_solution_ (e.g. a unicast VPN solution like VR) that supports v6
> and is extended to support multicast.

Good point, I missed this nuance of the text because I assumed that 1) all the 
existing VPN solutions already support IPv6 (is there one that doesn't?) or 2) 
the multicast VPN solutions might not depend on the unicast VPN solutions.

> Maybe the text could be a little clearer, what about :
> "When a multicast VPN solution is built on a VPN solution supporting
> IPv6 unicast, it MUST also support v6 variants of the above protocols,
> including  MLD v.2, and PIM-SM IPv6 specific procedures."
> ?
> 
> And we can even push a little further: "For a multicast VPN solution not
> built on a unicast VPN solution supporting IPv6, it is RECOMMENDED that
> the design favors the definition of procedures and encodings that will
> provide an easy adaptation to IPv6".

Are there standards track unicast VPN solutions that don't support IPv6?  If 
not, the language could probably be greatly simplified. If yes, let me summon a 
lynching party... ;-)

>> 5.1.3.  Quality of Service (QoS)
>> ....
>>
>>     As multicast is often used to deliver high quality services such as
>>     TV broadcast, the solution should have additional features to support
>>     high QoS such as bandwidth reservation and admission control.
>> 
>> ==> are these available for unicast?  Seems like you're asking more of a
>> multicast solution than from unicast.  I'd remove these kind of
>> "nice-to-have" reqs, or rephrase s/should/MAY/
> 
> Well, I would argue that:
> - things like this exist for unicast (think RSVP-TE tunnels between PEs)
> - it is worded "should" not "SHOULD" : the wording of the rest of the
> sentence is vague enough to no let us make a strict requirement

I do not know RSVP-TE well enough to know whether this is true or not, but at 
least my impression is that even RSVP-TE does not support (at least) _admission 
control_ (that seems something you'll need to set up first).  Certainly not in 
such a manner that it would be visible to the VPN sites at least?

In other documents, lower-case keywords may sometimes be interpreted as even 
stronger than uppercase, so unless the unicast mechanisms really exist and have 
bene widely deployed, I'd still suggest a MAY or rewording.

>> 5.1.11.  RP Engineering
>>
>>     When PIM-SM (or bidir-PIM) is used in ASM mode on the VPN customer
>>     side, the location of the RP has to be chosen.  In some cases this
>>     engineering problem is not trivial: for instance, if sources and
>>     receivers are located in VPN sites that are different than that of
>>     the RP, then traffic may flow twice through the SP network and the
>>     CE-PE link of the RP (from source to RP, and then from RP to
>>     receivers) ; this is obviously not ideal.  A multicast VPN solution
>>     SHOULD propose a way to help on solving this RP engineering issue.
>> 
>> ==> I'm not sure if this specific problem exists in practice.  If the
>> RP sends Register-Stop, the multicast traffic is forwarded natively,
>> and the data will short-cut inside the site without going to the RP
>> and then back.  I.e., there should not be two times traffic once the
>> forwarding is native.
> 
> Well...
> 1) even such transient peaks may not be something that you'll want
> 2) what if you lose connectivity to the remote site hosting the RP, are
> you happy to lose local multicast on every other site?
> 3) what if you want to stick with RPT ?
>   [okay, maybe not so relevant, but what if the VPN customer wants to
>    do this ?]

I should have been more specific.  I agree that the "RP engineering" problem 
exists: deciding where to put the RP has many different tradeoffs to consider 
-- there isn't a one-size-fits-all approach.

I was commenting on the double traffic issue specifically, 1) above. I don't 
think it really exists for valid configurations.  RPs tend to send 
Register-Stop *immediately* so you shouldn't see even a transient peak (longer 
than less than a second that is) due to this.

>> editorial
>> ---------
>> 
>> ==> you should add a dummy IANA considerations section
> 
> Sorry, to nit-pick, but where is it stated that all document should do
> this ? (where is the MUST in RFC2434?). Since this would be particularly
> irrelevant for a requirement document such as this one, I'd prefer not
> adding one more paragraph...

That's a rather recent addition, so it isn't in any RFC, but it can be found 
here:

http://www.ietf.org/ID-Checklist.html (see Changelog under Revision 0.4)

>>     [RFC3978]  Bradner, S., "IETF Rights in Contributions", BCP 78,
>>                RFC 3978, March 2005.
>>
>>     [RFC2026]  Bradner, S., "The Internet Standards Process -- Revision
>>                3", BCP 9, RFC 2026, October 1996.
>>
>>    [RFC2629]  Rose, M., "Writing I-Ds and RFCs using XML", RFC 2629,
>>                June 1999.
>> 
>> ==> these are not referred to in the body of the draft (when the document
>> gets published by the RFC editor), so they can be removed.
> 
> 
> RFC2629 is referred to in the appendix
> RFC3978 is BCP 78, referred to in IPR boilerplate

But RFC3978/BCP78 hasn't been referred in [square brackets], and moreover, this 
is a bit against the spirit (as this is a _symbolic_ reference) of ID-Checklist 
section 2.1 point:

"7. Do not add a numbered reference in the I-D boilerplate to RFC 3978 or RFC 
3979 (or to RFC 2026, RFC 3667 or RFC 3668 for older documents). If you do, it 
makes it harder for the RFC editor to process the document when they strip off 
the I-D boilerplate."

In any case, the reference would be stripped off when publishing as RFC, so...

>> Appendix A.  Requirements summary
>> 
>> ==> I'd consider removing this, because these should be extractable from the
>> body of the document, and these could get out of date easily if the editors
>> are not really, really careful.  Recent xml2rfc includes support for some
>> degree of autogeneration of these using xref format=title  (see RFC 3871 
>> appendix A for
>> example)
>

> Well, this was suggested by a reviewer, and I think it can be useful.
> I am open to other inputs, it is true that is requires particular
> care... its somehow a matter of benefit/risk trade-off.
> 
> (the feature you quote is interesting indeed, but looks only useful with
> one requirement item per sub-section, and subsection title chosen to
> match there use in the resulting summary...)

I'm OK with leaving it in if that's what the WG thinks is appropriate. However, 
the document is already pretty long, and any means to reduce the length should 
be considered.

-- 
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 l3vpn-bounces@ietf.org Tue Jan 17 17:02:27 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EyyuJ-0005tv-Fo; Tue, 17 Jan 2006 17:02:27 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EymKY-0003Lz-EC
	for l3vpn@megatron.ietf.org; Tue, 17 Jan 2006 03:36:42 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA27013
	for <l3vpn@ietf.org>; Tue, 17 Jan 2006 03:35:16 -0500 (EST)
Received: from netcore.fi ([193.94.160.1])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EymSe-0004Pf-3H
	for l3vpn@ietf.org; Tue, 17 Jan 2006 03:45:04 -0500
Received: from netcore.fi (localhost [127.0.0.1])
	by netcore.fi (8.12.8/8.12.8) with ESMTP id k0H8aWYG000552
	for <l3vpn@ietf.org>; Tue, 17 Jan 2006 10:36:32 +0200
Received: from localhost (pekkas@localhost)
	by netcore.fi (8.12.8/8.12.8/Submit) with ESMTP id k0H8aWq2000549
	for <l3vpn@ietf.org>; Tue, 17 Jan 2006 10:36:32 +0200
Date: Tue, 17 Jan 2006 10:36:32 +0200 (EET)
From: Pekka Savola <pekkas@netcore.fi>
To: l3vpn@ietf.org
Message-ID: <Pine.LNX.4.64.0601171036170.32168@netcore.fi>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-Virus-Scanned: ClamAV 0.87.1/1243/Sun Jan 15 20:35:18 2006 on otso.netcore.fi
X-Virus-Status: Clean
X-Spam-Status: No, score=-1.4 required=5.0 tests=ALL_TRUSTED autolearn=failed 
	version=3.1.0
X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on otso.netcore.fi
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 52f7a77164458f8c7b36b66787c853da
X-Mailman-Approved-At: Tue, 17 Jan 2006 17:02:25 -0500
Subject: Re: comments on draft-ietf-l3vpn-ppvpn-mcast-reqts-03 (fwd)
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: l3vpn.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:l3vpn@ietf.org>
List-Help: <mailto:l3vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=subscribe>
Sender: l3vpn-bounces@ietf.org
Errors-To: l3vpn-bounces@ietf.org

Re-sending as this was probably accidentally rejected by the list
administrator (for the policy, see
http://www.ietf.org/IESG/STATEMENTS/mail-submit-policy.txt).

---------- Forwarded message ----------
Date: Mon, 16 Jan 2006 18:58:43 +0200 (EET)
From: Pekka Savola <pekkas@netcore.fi>
To: Thomas Morin <thomas.morin@rd.francetelecom.com>
Cc: l3vpn@ietf.org
Subject: Re: comments on draft-ietf-l3vpn-ppvpn-mcast-reqts-03

On Mon, 16 Jan 2006, Thomas Morin wrote:
> Well, AFAIK, IPv6 support for PPVPN solution seems to be more the
> exception than the rule: v6 support is in l3vpn charter,
> draft-ietf-l3vpn-bgp-ipv6 is in "IESG Evaluation" state. Dunno about VR.

It'd be interesting to hear more comments on this.

>>>> 5.1.11.  RP Engineering
>>>>
>>>>     When PIM-SM (or bidir-PIM) is used in ASM mode on the VPN customer
>>>>     side, the location of the RP has to be chosen.  In some cases this
>>>>     engineering problem is not trivial: for instance, if sources and
>>>>     receivers are located in VPN sites that are different than that of
>>>>     the RP, then traffic may flow twice through the SP network and the
>>>>     CE-PE link of the RP (from source to RP, and then from RP to
>>>>     receivers) ; this is obviously not ideal.  A multicast VPN solution
>>>>     SHOULD propose a way to help on solving this RP engineering issue.
>>>> 
>>>> ==> I'm not sure if this specific problem exists in practice.  If the
>>>> RP sends Register-Stop, the multicast traffic is forwarded natively,
>>>> and the data will short-cut inside the site without going to the RP
>>>> and then back.  I.e., there should not be two times traffic once the
>>>> forwarding is native.
>>> 
>>> Well...
>>> 1) even such transient peaks may not be something that you'll want
>>> 2) what if you lose connectivity to the remote site hosting the RP, are
>>> you happy to lose local multicast on every other site?
>>> 3) what if you want to stick with RPT ?
>>>   [okay, maybe not so relevant, but what if the VPN customer wants to
>>>    do this ?]
>> 
>> I should have been more specific.  I agree that the "RP engineering"
>> problem exists: deciding where to put the RP has many different
>> tradeoffs to consider -- there isn't a one-size-fits-all approach.
>> 
>> I was commenting on the double traffic issue specifically, 1) above.
>> I don't think it really exists for valid configurations.  RPs tend to
>> send Register-Stop *immediately* so you shouldn't see even a transient
>> peak (longer than less than a second that is) due to this.
> 
> Sorry, but isn't "a second" (even a very short one), transient ?
> Also, what does "immediately" mean (especially across a multicast VPN
> and a provider core) ?

When the RP receives a Register message, it will (basically) send a 
Register-Stop immediately, see section 4.4.2 of the new PIM-SM spec. So, we're 
talking about 1 RTT between the DR and the RP.  I doubt this is a major problem 
-- the other RP engineering decisions are probably much more pressing.

-- 
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 l3vpn-bounces@ietf.org Tue Jan 17 23:26:17 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Ez4tl-0006ff-AC; Tue, 17 Jan 2006 23:26:17 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Ez4tj-0006fa-TR
	for l3vpn@megatron.ietf.org; Tue, 17 Jan 2006 23:26:15 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA01325
	for <l3vpn@ietf.org>; Tue, 17 Jan 2006 23:24:51 -0500 (EST)
Received: from sj-iport-2-in.cisco.com ([171.71.176.71]
	helo=sj-iport-2.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1Ez51z-0000ET-3b
	for l3vpn@ietf.org; Tue, 17 Jan 2006 23:34:48 -0500
Received: from sj-core-2.cisco.com ([171.71.177.254])
	by sj-iport-2.cisco.com with ESMTP; 17 Jan 2006 20:26:05 -0800
Received: from cisco.com (cypher.cisco.com [171.69.11.142])
	by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id k0I4Q4WF028875;
	Tue, 17 Jan 2006 20:26:05 -0800 (PST)
Received: from [5.18.5.101] (sjc-vpn7-561.cisco.com [10.21.146.49])
	by cisco.com (8.8.8-Cisco List Logging/8.8.8) with ESMTP id UAA07475;
	Tue, 17 Jan 2006 20:26:04 -0800 (PST)
In-Reply-To: <1137492252.6296.38.camel@wintermute>
References: <200601151540.k0FFeF583898@merlot.juniper.net>
	<1137419379.15352.143.camel@wintermute>
	<2F7ADC25-9746-4E1E-A947-871761CC4C6D@cisco.com>
	<1137492252.6296.38.camel@wintermute>
Mime-Version: 1.0 (Apple Message framework v746.2)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <A9446195-4040-4CA0-A59E-62570E65BC2C@cisco.com>
Content-Transfer-Encoding: 7bit
From: Yiqun Cai <ycai@cisco.com>
Date: Tue, 17 Jan 2006 20:25:53 -0800
To: Thomas Morin <thomas.morin@rd.francetelecom.com>
X-Mailer: Apple Mail (2.746.2)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: dbb8771284c7a36189745aa720dc20ab
Content-Transfer-Encoding: 7bit
Cc: L3VPN <l3vpn@ietf.org>
Subject: Re: WG last call: draft-ietf-l3vpn-ppvpn-mcast-reqts-03
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: l3vpn.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:l3vpn@ietf.org>
List-Help: <mailto:l3vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=subscribe>
Sender: l3vpn-bounces@ietf.org
Errors-To: l3vpn-bounces@ietf.org


On Jan 17, 2006, at 2:04 AM, Thomas Morin wrote:

> Hi Yiqun,
>
> The idea, I think, is to have the ability to have a VRF be  
> associated to
> multiple VPNs, independently for multicast and unicast, and also
> independently for emission and reception.

Hi Thomas,

The above is a little confusing. Especially with the statement of "a VRF
be associated to multiple VPNs".   Because this can mean multiple
things.  For example,

1.  A VRF can have interfaces connected to CEs belonging to different
VPNs.

2. A VRF can source traffic to receivers in different VPNs, or  
receive traffic
from senders from different VPNs.

I think you meant #2,  but I just want to be sure.  Because I don't  
think #1
is practical deployment.

>
> First point : unicast is not dependent on multicast. So you may very
> well want to have a VRF be associated to a VPN for unicast without
> activating multicast reception from (or multicast emission to) this  
> VPN.

Agree.

>
> Second point : as you explain, multicast reception is dependent on
> unicast for RPF. However, if you want to emit mcast from a VRF to a  
> VPN,
> you don't depend on unicast (no need to have the routes of that VPN in
> your VRF).  Thus, you could activate multicast emission to a VPN  
> without
> importing its routes into your VRF (just VRFs of that VPN will import
> your routes).
>

Agree as well.

> I think its important for security aspects, to have full-control of  
> what
> routes you import/export and of which VPN you associate to for
> emission/redeption.  Here, having coupling (being forced to activate a
> broad scope feature, only to use a subset) would not be good I think.
>

However,  I don't 100% agree with your conclusion.  The total separation
of control is something good to have.  But to say that a solution "MUST"
support it is a bit strong.  My reasoning behind it is that MVPN  
customers
are usually enterprises.  And most of the enterprises do have a  
congruent
topology for unicast and multicast.

Maybe we should say that a solution SHOULD provide such functionality
if non-congruency exists.

Thanks.


> Cheers,
>
> -Thomas
>
>
> Yiqun Cai:
>> I have some doubt regarding this.
>>
>> By "extranet multicast connectivity",  do you mean procedure of RPF
>> to the
>> source,  the distribution of multicast data traffic to the receivers
>> in different
>> VPNs, or something else.
>>
>> Multicast RPF is built based on unicast routing information.  So
>> there is a
>> dependancy existing today.  A solution does provide more flexibility
>> if it allows
>> RPF to be independent of unicast routing,  but I dont see it as a
>> "must".
>>
>> For distribution of multicast data,  since they are controlled by
>> join/prune
>> messages,  they are independent of unicast data distribution in  
>> nature.
>> So I don't see how this bullet is applicable.
>>
>> If it is something else,  could you please elaborate?
>>
>> Thanks a lot.
>>
>> On Jan 16, 2006, at 5:49 AM, Thomas Morin wrote:
>>
>>> Hello Yakov,
>>>
>>> Yakov Rekhter:
>>>> In 5.1.7 I would suggest to add the following to the bullet list:
>>>>
>>>>       A solution must allow to control an extranet multicast
>>>>       connectivity independently from the extranet unicast
>>>>       connectivity
>>>
>>> Agreed.
>>> I just used capitalized "MUST" instead of "must".
>>>
>>> Cheers,
>>>
>>> -Thomas
>>>
>>>
>>
>>
>>
>> --
>> Yiqun
>>
>>
>
>



--
Yiqun






From l3vpn-bounces@ietf.org Wed Jan 18 04:48:32 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Ez9vc-0001rF-MG; Wed, 18 Jan 2006 04:48:32 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Ez9va-0001pl-23
	for l3vpn@megatron.ietf.org; Wed, 18 Jan 2006 04:48:31 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA23420
	for <l3vpn@ietf.org>; Wed, 18 Jan 2006 04:47:03 -0500 (EST)
Received: from p-mail2.rd.francetelecom.com ([195.101.245.16])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EzA3t-0001w5-3g
	for l3vpn@ietf.org; Wed, 18 Jan 2006 04:57:05 -0500
Received: from ftrdmel10.rd.francetelecom.fr ([10.193.117.156]) by
	ftrdsmtp2.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.211); 
	Wed, 18 Jan 2006 10:48:27 +0100
Received: from l-at8613.rd.francetelecom.fr ([10.193.15.32]) by
	ftrdmel10.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.211); 
	Wed, 18 Jan 2006 10:48:26 +0100
From: Thomas Morin <thomas.morin@rd.francetelecom.com>
To: Marshall Eubanks <marshall.eubanks@gmail.com>
In-Reply-To: <dcad22d80601171322n58125885gf4a779a0e831e0dc@mail.gmail.com>
References: <43BBE0D5.2060607@juniper.net>
	<dcad22d80601102236u373871a7qb6f7636e5b7bbfcd@mail.gmail.com>
	<1137417200.15352.113.camel@wintermute>
	<dcad22d80601161836u4783b79m5d59cb06cb374f07@mail.gmail.com>
	<20060117155733.GA28261@1-4-5.net>
	<dcad22d80601171322n58125885gf4a779a0e831e0dc@mail.gmail.com>
Content-Type: text/plain
Organization: France Telecom R&D
Date: Wed, 18 Jan 2006 10:48:26 +0100
Message-Id: <1137577706.18466.15.camel@wintermute>
Mime-Version: 1.0
X-Mailer: Evolution 2.4.2.1 
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 18 Jan 2006 09:48:26.0994 (UTC)
	FILETIME=[548ABD20:01C61C14]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c1c65599517f9ac32519d043c37c5336
Content-Transfer-Encoding: 7bit
Cc: David Meyer <dmm@1-4-5.net>, l3vpn@ietf.org
Subject: Re: WG last call: draft-ietf-l3vpn-ppvpn-mcast-reqts-03
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: l3vpn.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:l3vpn@ietf.org>
List-Help: <mailto:l3vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=subscribe>
Sender: l3vpn-bounces@ietf.org
Errors-To: l3vpn-bounces@ietf.org

Well, I'm happy to know that my english is not so bad. Thank you,
Dave. :)

However, to make sure the draft is readable by anyone, I rephrased this
part to a more direct expression : " [some of these applications may
involve rapid changes in customer multicast memberships as seen by the
PE, but this will depend on audience patterns and on] the number of
provider equipments deployed close to VPN customers".

Cheers,

-Thomas

Marshall Eubanks: 
> Well, a google on the "capillarity of carrier network" (without the
> quotes) does return 653 hits, so Dave is correct in that it is used
> that way at least some, and I appreciate the education.
> 
> However, note that capillarity is not (in English) the "quality or
> state of being capillary" but is simply a noun describing the
> phenomenon itself,  so I do not regard the above as proper English
> usage and I would recommend against its use in a standards document.
> 
> Regards
> Marshall
> 
> 
> On 1/17/06, David Meyer <dmm@1-4-5.net> wrote:
> > > And, I have never seen  "capillarity" actually used in English. It's
> > > in the dictionary, even in my spell checker, and it might be used in
> > > botany, but it's not used metaphorically.
> >
> >
> >         As I was mentioning to Marshall earlier, actually, the
> >         term capillarity is in common use in the carrier industry
> >         (usually used to describe the extent and density of a
> >         carrier's transport network). As such, I don't find the
> >         fact the google doesn't know that disqualifying, and
> >         further, most of us who have worked in that side of the
> >         industry consider it common usage.
> >
> >         Dave
> >
> >
> >
> 





From l3vpn-bounces@ietf.org Wed Jan 18 05:27:46 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EzAXa-0001vj-Bl; Wed, 18 Jan 2006 05:27:46 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EzAXY-0001ve-2O
	for l3vpn@megatron.ietf.org; Wed, 18 Jan 2006 05:27:44 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA25960
	for <l3vpn@ietf.org>; Wed, 18 Jan 2006 05:26:19 -0500 (EST)
Received: from p-mail2.rd.francetelecom.com ([195.101.245.16])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EzAfr-00038K-7b
	for l3vpn@ietf.org; Wed, 18 Jan 2006 05:36:19 -0500
Received: from ftrdmel10.rd.francetelecom.fr ([10.193.117.156]) by
	ftrdsmtp1.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.211); 
	Wed, 18 Jan 2006 11:27:38 +0100
Received: from l-at8613.rd.francetelecom.fr ([10.193.15.32]) by
	ftrdmel10.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.211); 
	Wed, 18 Jan 2006 11:27:38 +0100
From: Thomas Morin <thomas.morin@rd.francetelecom.com>
To: Yiqun Cai <ycai@cisco.com>
In-Reply-To: <A9446195-4040-4CA0-A59E-62570E65BC2C@cisco.com>
References: <200601151540.k0FFeF583898@merlot.juniper.net>
	<1137419379.15352.143.camel@wintermute>
	<2F7ADC25-9746-4E1E-A947-871761CC4C6D@cisco.com>
	<1137492252.6296.38.camel@wintermute>
	<A9446195-4040-4CA0-A59E-62570E65BC2C@cisco.com>
Content-Type: text/plain
Organization: France Telecom R&D
Date: Wed, 18 Jan 2006 11:27:37 +0100
Message-Id: <1137580057.31955.25.camel@wintermute>
Mime-Version: 1.0
X-Mailer: Evolution 2.4.2.1 
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 18 Jan 2006 10:27:38.0243 (UTC)
	FILETIME=[CDFEDD30:01C61C19]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 848ed35f2a4fc0638fa89629cb640f48
Content-Transfer-Encoding: 7bit
Cc: L3VPN <l3vpn@ietf.org>
Subject: Re: WG last call: draft-ietf-l3vpn-ppvpn-mcast-reqts-03
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: l3vpn.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:l3vpn@ietf.org>
List-Help: <mailto:l3vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=subscribe>
Sender: l3vpn-bounces@ietf.org
Errors-To: l3vpn-bounces@ietf.org

Hi Yiqun,

Yiqun Cai: 
> On Jan 17, 2006, at 2:04 AM, Thomas Morin wrote:
> > The idea, I think, is to have the ability to have a VRF be 
> > associated to multiple VPNs, independently for multicast and 
> > unicast, and also independently for emission and reception. 
> 
> The above is a little confusing. Especially with the statement of "a VRF
> be associated to multiple VPNs".   Because this can mean multiple
> things.  For example,
> 
> 1.  A VRF can have interfaces connected to CEs belonging to different
> VPNs.
> 
> 2. A VRF can source traffic to receivers in different VPNs, or  
> receive traffic
> from senders from different VPNs.
> 
> I think you meant #2,  but I just want to be sure.
[...]

Yes. Definitely #2.

(I'm not sure what #1 would mean, if two interfaces are connected to a
same VRF, then for me, there are in the same VPN, because there is no
segmentation between them)

> > First point : unicast is not dependent on multicast. So you may very
> > well want to have a VRF be associated to a VPN for unicast without
> > activating multicast reception from (or multicast emission to) this  
> > VPN.
> 
> Agree.
> 
> >
> > Second point : as you explain, multicast reception is dependent on
> > unicast for RPF. However, if you want to emit mcast from a VRF to a  
> > VPN,
> > you don't depend on unicast (no need to have the routes of that VPN in
> > your VRF).  Thus, you could activate multicast emission to a VPN  
> > without
> > importing its routes into your VRF (just VRFs of that VPN will import
> > your routes).
> >
> 
> Agree as well.
> 
> > I think its important for security aspects, to have full-control of  
> > what
> > routes you import/export and of which VPN you associate to for
> > emission/redeption.  Here, having coupling (being forced to activate a
> > broad scope feature, only to use a subset) would not be good I think.
> >
> 
> However,  I don't 100% agree with your conclusion.  The total separation
> of control is something good to have.  But to say that a solution "MUST"
> support it is a bit strong.  

Accepting that enabling unicast-extranet with a VPN may force
multicast-extranet with that VPN, would be contradictory with other
statements in the draft (that a multicast VPN solution should not impact
unicast service).

Thus, I think its very reasonable to at least state that it is a MUST
that enabling unicast-extranet with a VPN doesn't force
multicast-extranet with that VPN.

> My reasoning behind it is that MVPN  customers are usually enterprises.  
> And most of the enterprises do have a  congruent topology for unicast and 
> multicast.
> Maybe we should say that a solution SHOULD provide such functionality
> if non-congruency exists.

I'm not sure why we talk about non-congruency : the proposed requirement
would be about activating multicast-extranet with a VPN without having
to both import and export unicast routes of that VPN (even if these
would be congruent).

Also, one thing to keep in mind is that it is a requirement document,
not a solution design document : this means that a MUST in the
requirements impact the solution and its design, not directly
implementations of this solution.  For me this means that a MUST in the
requirement draft could be understood as "the solution designed MUST
provide means so that this is possible", not necessarily as "all
implementations MUST implement this" (this latter degree of requirement
would I think belong to solution drafts).

Maybe we can reformulate as "a multicast VPN solution SHOULD allow ...
and its design MUST NOT preclude this from being possible" ?

In any case, I'll add bullets under the sentence, precising what
"independently" means : 
" - unicast-extranet MUST NOT force multicast-extranet
- it SHOULD be possible to independently enable multicast reception
from, and emission to, a VPN.  "

Cheers,

-Thomas




> > Cheers,
> >
> > -Thomas
> >
> >
> > Yiqun Cai:
> >> I have some doubt regarding this.
> >>
> >> By "extranet multicast connectivity",  do you mean procedure of RPF
> >> to the
> >> source,  the distribution of multicast data traffic to the receivers
> >> in different
> >> VPNs, or something else.
> >>
> >> Multicast RPF is built based on unicast routing information.  So
> >> there is a
> >> dependancy existing today.  A solution does provide more flexibility
> >> if it allows
> >> RPF to be independent of unicast routing,  but I dont see it as a
> >> "must".
> >>
> >> For distribution of multicast data,  since they are controlled by
> >> join/prune
> >> messages,  they are independent of unicast data distribution in  
> >> nature.
> >> So I don't see how this bullet is applicable.
> >>
> >> If it is something else,  could you please elaborate?
> >>
> >> Thanks a lot.
> >>
> >> On Jan 16, 2006, at 5:49 AM, Thomas Morin wrote:
> >>
> >>> Hello Yakov,
> >>>
> >>> Yakov Rekhter:
> >>>> In 5.1.7 I would suggest to add the following to the bullet list:
> >>>>
> >>>>       A solution must allow to control an extranet multicast
> >>>>       connectivity independently from the extranet unicast
> >>>>       connectivity
> >>>
> >>> Agreed.
> >>> I just used capitalized "MUST" instead of "must".
> >>>
> >>> Cheers,
> >>>
> >>> -Thomas
> >>>
> >>>
> >>
> >>
> >>
> >> --
> >> Yiqun
> >>
> >>
> >
> >
> 
> 
> 
> --
> Yiqun
> 
> 





From l3vpn-bounces@ietf.org Wed Jan 18 07:49:08 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EzCkO-0001Xd-83; Wed, 18 Jan 2006 07:49:08 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EzCkN-0001XT-DF
	for l3vpn@megatron.ietf.org; Wed, 18 Jan 2006 07:49:07 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA07976
	for <l3vpn@ietf.org>; Wed, 18 Jan 2006 07:47:41 -0500 (EST)
Received: from zproxy.gmail.com ([64.233.162.206])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EzCsh-00086R-KH
	for l3vpn@ietf.org; Wed, 18 Jan 2006 07:57:44 -0500
Received: by zproxy.gmail.com with SMTP id 9so1609911nzo
	for <l3vpn@ietf.org>; Wed, 18 Jan 2006 04:49:05 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
	h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=WhKnZsE4ApylAxQdUxoVaoBg9J2HjmYVjP83/Vl2aPpBd/+AtFkbrXNewnj4LcVpPqdtnw9mAcgfyAS9+jO3jptKmOBrDKiUO0HuBX5y0zwf9CwuIjIbaqyAZtJmGGksdae2Cw8JecW/FxHPkJkul6okV3lDNG6kzZG+m68MfsE=
Received: by 10.36.224.9 with SMTP id w9mr6625234nzg;
	Wed, 18 Jan 2006 04:49:05 -0800 (PST)
Received: by 10.36.46.2 with HTTP; Wed, 18 Jan 2006 04:49:05 -0800 (PST)
Message-ID: <dcad22d80601180449l1ee6312naaa5cf47d5aff626@mail.gmail.com>
Date: Wed, 18 Jan 2006 07:49:05 -0500
From: Marshall Eubanks <marshall.eubanks@gmail.com>
To: Thomas Morin <thomas.morin@rd.francetelecom.com>
In-Reply-To: <1137417200.15352.113.camel@wintermute>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <43BBE0D5.2060607@juniper.net>
	<dcad22d80601102236u373871a7qb6f7636e5b7bbfcd@mail.gmail.com>
	<1137417200.15352.113.camel@wintermute>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 544c2133b952fa264803d857bb70855b
Content-Transfer-Encoding: quoted-printable
Cc: l3vpn@ietf.org
Subject: Re: WG last call: draft-ietf-l3vpn-ppvpn-mcast-reqts-03
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: l3vpn.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:l3vpn@ietf.org>
List-Help: <mailto:l3vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=subscribe>
Sender: l3vpn-bounces@ietf.org
Errors-To: l3vpn-bounces@ietf.org

Hello;

On 1/16/06, Thomas Morin <thomas.morin@rd.francetelecom.com> wrote:
> Hi Marshall,
>
> Marshall Eubanks:
> > As my first attempt bounced, you can find my comments and corrections
> > on this document at
> >
> > http://www.americafree.tv/papers/draft-ietf-l3vpn-ppvpn-mcast-reqts-03-=
tme.txt
> >
> > I gave this document a careful read. In my opinion there are a bunch of=
 mostly
> > minor things that need to be corrected before it passes last call.
>
> Thank you for your review and all your relevant comments, there are very
> appreciated.
>
> See below for comments to some of your suggestions or questions, and the
> changes I propose to address them.  I integrated "as is" (or mostly "as
> is") all of your others comments, which were definitely reasonable.
>
> Cheers,
>
> -Thomas
>
>
>
>
>
> >    VRF or VR: By this phrase, we refer to the entity defined in a PE
> >       dedicated to a specific VPN instance.  "VRF" refers to [RFC2547]
> >       terminology, and "VR" to the VR [I-D.ietf-l3vpn-vpn-vr]
> >       terminology.
> >
> > tme> I have read this several times and still don't know what "entity" =
is being referred
> > tme> to.
> > tme> VR =3D=3D "Virtual Router"
> > tme> VRF =3D=3D "Virtual Routing and Forwarding table"
> > tme> This phrase is used 4 times, not counting here. The next is
> > tme>
> > tme> Moreover, the activation of multicast features SHOULD be possible:
> > tme>    o  with a VRF or VR granularity
> > tme> This is not really clear either.
> > tme> Does it mean, for each routing table, or each entry on the routing=
 table ?
> > tme> Note that VRF and VR are both used separately
> > tme>
> > tme> Here is a stab at a definition
> > tme>
> > tme> VRF or VR: By this phrase, we refer to the finest scale multicast =
routing
> > tme> information available, as maintained by the Virtual Router (VR, se=
e [I-D.ietf-l3vpn-vpn-vr])
> > tme> or the Virtual Routing and Forwarding table (VRF, see [2547bis])
>
>
> Well, a VRF is a routing table (not an entry), and a VR (virtual router)
> is somehow of the same level (contains protocol routing instance, and
> routing tables).
>
> So, here is the wording I propose to avoid any confusion:
>
> "By this phrase, we refer to the entity defined in a PE dedicated to a
> specific VPN instance. "VRF" refers to "VPN Routing and Forwarding
> table" as defined in [I-D.ietf-l3vpn-rfc2547bis], and "VR" to "Virtual
> Router" as defined in  [I-D.ietf-l3vpn-vpn-vr] terminology."
>
> Moreover, I reworded section in 5.1.5:
> "Moreover, the activation of multicast features SHOULD be possible:
>       * per VRF / per VR
>       * per CE interface (when multiple CE of a same VPN are connected
>         to a common VRF/VR)
>       * per multicast group and/or per channel
>       * with a distinction between multicast reception and emission"
>
> [about section 3.3]
> > tme> Why isn't is a general requirement to interoperate with existing _=
multicast_
> > tme> deployments ?  rfc4021 says little about multicast - shouldn't thi=
s be explicit ?
>
> Well the idea is to highlight the focus : in a VPN deployment context,
> one of the most crucial requirement is to cohabit with the existing
> service (unicast VPN).
>
> You are right in the sense that deploying a multicast VPN solution
> should nicely cohabit with existing deployment of multicast on P and PE
> routers, and on CE routers.
>
> I added two sentences:
> - in 5.1.1:  "Enabling a VPN for multicast support SHOULD be possible
> with no (or very limited impact) on existing multicast protocols
> possibly already deployed on the CE devices."
> - in 5.2 : "The deployment of a multicast VPN solution SHOULD be
> possible with no (or very limited) impact on possibly existing
> deployments of multicast protocols on P and PE routers."
>
> Would that be ok ?

Yes.

>
> >    o  some of these applications may involve rapid changes in customer
> >       multicast memberships, but this will depend on audience and
> >       capillarity of provider equipments
> >
> > tme> "capillarity" is a very obscure English word, and I do not know wh=
at is meant here.
> > tme> could this be a typo for "capabilities" ?
>
> No typo, but maybe the use of this term is less common in english than
> "capilarit'e" is in french... :)  We sometime use it metaphorically to
> refer to the number of small elements at the periphery of something,
> like leaves of a tree, with the image of capillary vessels in lungs for
> instance.
>
> I rephrased as: "some of these applications may involve rapid changes in
> customer multicast memberships as seen by the PE, but this will depend
> on audience patterns and on the number of provider equipments deployed
> close to VPN customers".
>
> > 4.1.2.  Symetric applications
> >
> > tme> nit : s/Symetric/ Symmetric /
> >
> >    Some use cases exposed by the survey can be grouped under this label=
,
> >    and include many-to-many applications such as conferencing, clusters
> >    monitoring.
> >
> > tme> (relative) nit : I do not know what "clusters monitoring" means in=
 this context.
> > tme> Is this for entities like beowulf clusters over VPN's ?
> > tme> An extra word to explain this would help.
>
> Survey responses did not include such a level of detail, so I can only gu=
ess here.
> I rephrased as: "server clusters monitoring".
>

OK

>
> > 4.2.2.  Number of multicast VPNs per PE
> >
> >    The majority of survey answers express a number of multicast VPNs pe=
r
> >    PE of around tens (8 responses between 5 and 50); a significant
> >    number of them (4) expect deployments with hundreds or thousands (1
> >    response) of multicast VPNs per PE.
> >
> >    A solution SHOULD support a number of multicast VPNs per PE of
> >    several hundreds, and may have to scale up to thousands VPNs per PE.
> >
> > tme> PE means "provider edge". Does this mean, number per edge location=
, or
> > tme> number over all locations. I would suggest
> > tme> s/scale up to thousands VPNs per PE/scale up to thousands VPNs per=
 PE location/
> >
>
> RFC4026 "Provider Provisioned VPN Terminology" section 5.2 precisely
> suggest the use of "PE" and "CE" to refer to the devices themselves.
> That actually what we are used to do in l3vpn (for brievity).
>
> I added the following in the terminology section:
> " "Provider Edge", "Customer Edge" (as defined in [RFC4026](Andersson,
> L. and T. Madsen, "Provider Provisioned Virtual Private Network (VPN)
> Terminology," March 2005.)). As suggested in [RFC4026](Andersson, L. and
> T. Madsen, "Provider Provisioned Virtual Private Network (VPN)
> Terminology," March 2005.), we will use these notations to refer to the
> equipments/routers/devices themselves. Thus, "PE" will refer to the
> router on the provider's edge, which faces the "CE", the router on the
> customer's edge. "
>

OK

>
> > 5.1.2.  CE-PE Multicast routing and management protocols
> >
> [snip]
> >
> > tme> Note that IGMP v3 and MLD v2 support means support for IGMP v1,v2 =
and MLD v1
> > tme> So, I would suggest :
> >
> > tme>   Among those protocols, the support of PIM-SM (version 2, revised=
, which
> > tme>   includes SSM model) and either IGMP v.3 (for IPv4 solutions) and=
 / or
> > tme>   MLD v.2 (for IPv6 solutions) are REQUIRED.
>
> Agreed.
> I also followed your implicit suggestion, by mentioning that hosts only
> implementing -v1 and -v2 are implicitely supported by IGMPv3 queriers.
>
>
> >    A multicast in VPN solution shall allow to define at least the same
> > tme> nit : s/shall allow to define/SHALL allow definition of/
>
> maybe "SHALL allow the definition of" ?
>
>
> >    As multicast is often used to deliver high quality services such as
> >    TV broadcast, the solution should have additional features to suppor=
t
> > tme> nit : s/should/SHOULD/
> >    high QoS such as bandwidth reservation and admission control.
>
> Since when is it MANDATORY to use CAPITALIZED version of those words ?
> Here I fell it hard to use a strict wording, considering how precise the
> rest of the sentence is.
>

Already diiscussed.

>
> >    The solution MUST support SLA monitoring capabilities, which MAY
> >    possibly rely upon similar techniques (than those used by the unicas=
t
> >
> > tme> I puzzled over this - I suggest
> > tme> s/similar techniques (than/different techniques than/
> >    for the same monitoring purposes).
> > tme> s/)//
>
> Ok, that one indeed may be puzzling ; "which MAY possibly rely upon
> techniques similar to those used for the unicast service for the same
> monitoring purposes"  will be better I guess.
>

Fine by me.

>
> > 5.1.8.  Internet Multicast
> >
> >    Connectivity with Internet Multicast (as a source or receiver)
> >    somehow fits in the context of the previous section.
> >
> > tme> Is this a stub for missing text ? This must be filled out to pass =
last call IMHO.
>
> Well, this section was supposed to be complete, describing the
> connectivity to/from Internet Multicast a similar to the connectivity
> to/from another multicast VPN.
>
> >
> >    It should be considered OPTIONAL given additional considerations
> >    needed to fulfill requirements for Internet side, such as security
> >    treatment.
> >
> tme> Here is some text :
> >
> [snip]
>
> The text you propose is I think partly redundant with section 5.1.7
> "Extranet".  I would like to just put in this section things that are
> specific to Internet Multicast connectivity (if there are any):
> - MSDP might be one of these, though I'd suspect not : MSDP is only
> inter-RP, so if no RP is deployed in VRF (acceptable), then no MSDP
> requirement is relevant here ; and in any case, I don't see that we'd
> need to state MSDP-related requirement for the overall architecture
> (same for embbeded-RP)
> - we may need to state MBGP-related requirement: I'm not sure precisely
> what we should say, since anything a bit precise would require
> articulation with what is expected for unicast Internet Connectivity in
> such a case.
>
> Maybe adding the following would be enough : "MBGP support in VRF/VR
> would be REQUIRED if a Multicast VPN solution supports connectivity with
> Internet Multicast. MSDP support in VRF/VR also is REQUIRED for such a
> solution, if it supports the RP functionality in VRF/VR".
>
> Would you agree ?
>

OK

> >    The use of globally unique means of multicast-based service
> >    identification at the scale of the domain where such services are
> >    provided SHOULD be recommended.  If the ASM model is used, this
> >
> > tme> SSM also has source scoping, 239/8 can be used with either SSM or =
ASM. Therefore
> > tme> s/If the ASM model is used, this/For IPv4 multicasts, this/
>
> I rephrased as follows:
>
> "For IPv4 multicast, this implies the use of the multicast
> administratively scoped range, (239/8 as defined by [RFC2365]) for
> services which are to be used only inside the VPN, and of or SSM-range

s/of or SSM-range/of either global SSM-range/

to correct a typo and to make it clear that 232 is intended for global
scope SSM.

> addresses (232/8 as defined by [I-D.ietf-ssm-arch]) or globally assigned
> group addresses (e.g. GLOP [RFC3180], 233/8) for services for which
> traffic may be transmitted outside the VPN ."
>
>
>
> > 5.1.13.  Minimum MTU
> >
> >    For customers, it is often a serious issue whether transmitted
> >    packets will be fragmented or not.  In particular, some multicast
> >    applications might have different requirements than those that make
> >    use of unicast, and they may expect services that guarantee availabl=
e
> >    packet length not to be fragmented.
> >
> >    Therefore, a multicast VPN solution SHOULD let customers' devices be
> >    free of any fragmentation or reassembly activity.
> >
> >    A committed minimum path MTU size SHOULD be provided to customers.
> >    Moreover, since Ethernet LAN segments are often located at first and
> >    last hops, a minimum 1500 bytes IP MTU SHOULD be provided.
> >
> > tme> There are a lot of tunnels used in multicast, and they tend to
> > tme> restrict MTU's to a little below the 1500 coming from Ethernet
> > tme> Are you really saying that no existing GRE or PPPoE or IP-IP multi=
cast
> >tme> tunnel can be used in multicast VPN architectures ? This seems extr=
eme.
>
> tme> In fact, since these tunnel types are allowed in Section 5.2.3.1.,
> > tme> I do not know how they can be implemented in most networks (unless
> > tme> jumbo frames are used throughout).
>
> Encapsulation that would limit the MTU is encapsulation between PE
> routers.  Those are often mutually reachable with high troughput links,
> such as GE w/ Jumbo Frames, POS... for which MTU can be easily made
> above 1500 I think.
>
> What we are saying only means that:
> a) if tunneling is used, then the provider should be able to commit to a =
minimum MTU
> b) is possible (SHOULD) this MTU should be 1500, because this is what
> will require the less tuning of customer application (which we expect
> can initialy be used inside a LAN, without tunnels)
>
> Consequently:
> - if the Multicast VPN solution doesn't meet b), then it doesn't meet
> the "SHOULD" (which may be acceptable, as soon as there is a rationale
> behind it)
> - it the provider's network cannot meet b), then it is less good than if
> it would
>
> Thus, a multicast VNP solution requiring the use of GRE or or IP-IP
> multicast for PE to PE tunnels is completely be acceptable:
> - GRE or IP-IP, by itself, doesn't I think limit the MTU
> - a provider network for which some PE-to-PE path go through a small MTU
> interface (like a Fast Ethernet LAN interface) won't be able to meet
> this requirement : this is not so common I think, and in any case that
> may be acceptable (client will tell you)
>
> PPPoE is intrinsicaly more limited, but I think nobody would like to use
> it for PE-to-PE communication right ?
>
> In anycase, nothing precludes any tunneling mechanism by itself, and
> 1500-byte minimal MTU is only a SHOULD.
>
>
> > tme>
> > tme> I would suggest either s/1500/1476/ or
> > tme> s/1500 bytes/1500 bytes, including any necessary tunnel headers/
> > tme> but the latter is sure to be confusing.
>
> We talk about "1500 byte IP MTU", which refers to the minimum MTU made av=
ailable to the customer
> (who doesn't "see" any tunnel).  Isn't this precise enough.
>

This is OK.


> [section 5.2.1]
> >
> > tme> This seems garbled. Do you mean "point to point, point to multipoi=
nt",
> > tme> or is the first "point" just a duplicate ? As a guess,
> > tme> s/point/point to point,/
> >
> Yes, "point" is a duplicate.
>
>
> >
> > tme> again, this seems garbled. I think this is meant :
> > tme>  s/leaves/leafs/
>
>
> Hmm. Isn't "leaf" like "knife", "life", or "scarf" ?

You are correct; my error. For some reason I cannot reconstruct, I was
thinking of
the verb. (A tree leafs out, it's branches then have leaves.)

>
>
> >    Unwanted multicast traffic (e.g. multicast traffic that may be sent
> >    by a source located somewhere in the Internet and for which there is
> >    no interested receiver connected to a given VPN infrastructure) MUST
> >    NOT be propagated within a multicast-enabled VPN.
> >
> > tme> Is this consistent with Section 5.2.2.3. ? It seems to me that thi=
s
> > tme> should be a SHOULD NOT to allow for sub-optimal solutions
>
>
> While it might be acceptable (for provider-side scalability) that some
> traffic reaches a PE even if this is not needed, it would not be
> acceptable that such traffic be propagated toward the CE, inside the
> customer network.
>
> Isn't this reasonable ?

Reasonable, but in normal multicast it is common to get multiple
packets when trees switch over.

>
>
> >    As an illustration, one can consider the case of a solution that
> >    would use PIM-SM as a means to setup MDTunnels.  In such a case, the
> >    PIM RP might be a single point of failure.  Such a solution should
> >    thus be compatible with a solution implementing RP resiliency.
> >
> > tme> s/./, such as is provided by anycast RP [draft-ietf-pim-anycast-rp=
-04]./
>
> I also added BSR, for completeness.
>
>

OK.

>
>
>
>

Marshall




From l3vpn-bounces@ietf.org Wed Jan 18 07:51:45 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EzCmv-0002UZ-GA; Wed, 18 Jan 2006 07:51:45 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EzCmu-0002TH-4l
	for l3vpn@megatron.ietf.org; Wed, 18 Jan 2006 07:51:44 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA08445
	for <l3vpn@ietf.org>; Wed, 18 Jan 2006 07:50:18 -0500 (EST)
Received: from zproxy.gmail.com ([64.233.162.206])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EzCvD-0008Ja-EW
	for l3vpn@ietf.org; Wed, 18 Jan 2006 08:00:19 -0500
Received: by zproxy.gmail.com with SMTP id 9so1610479nzo
	for <l3vpn@ietf.org>; Wed, 18 Jan 2006 04:51:41 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
	h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=HuOGjHx3ivNxxv5wFfzulM//SGkfRuz8etBWA8T8mISm1EkjbdkMHWDAH6fYpnX0DN7FvaxjuLYSal714P9SkjzUdQLScrbqTQHgi62juIsT9cmAgM1ygmjYHLqyUOoBbmBfjRxraDUuvs47Y3WvFS/htV8k5nvdqqOn2wdSGwI=
Received: by 10.36.135.18 with SMTP id i18mr6592054nzd;
	Wed, 18 Jan 2006 04:51:41 -0800 (PST)
Received: by 10.36.46.2 with HTTP; Wed, 18 Jan 2006 04:51:41 -0800 (PST)
Message-ID: <dcad22d80601180451u1cfb23f1q9d2a1c663a4abaa5@mail.gmail.com>
Date: Wed, 18 Jan 2006 07:51:41 -0500
From: Marshall Eubanks <marshall.eubanks@gmail.com>
To: Thomas Morin <thomas.morin@rd.francetelecom.com>
In-Reply-To: <1137577706.18466.15.camel@wintermute>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <43BBE0D5.2060607@juniper.net>
	<dcad22d80601102236u373871a7qb6f7636e5b7bbfcd@mail.gmail.com>
	<1137417200.15352.113.camel@wintermute>
	<dcad22d80601161836u4783b79m5d59cb06cb374f07@mail.gmail.com>
	<20060117155733.GA28261@1-4-5.net>
	<dcad22d80601171322n58125885gf4a779a0e831e0dc@mail.gmail.com>
	<1137577706.18466.15.camel@wintermute>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 082a9cbf4d599f360ac7f815372a6a15
Content-Transfer-Encoding: quoted-printable
Cc: David Meyer <dmm@1-4-5.net>, l3vpn@ietf.org
Subject: Re: WG last call: draft-ietf-l3vpn-ppvpn-mcast-reqts-03
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: l3vpn.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:l3vpn@ietf.org>
List-Help: <mailto:l3vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=subscribe>
Sender: l3vpn-bounces@ietf.org
Errors-To: l3vpn-bounces@ietf.org

Hello;

On 1/18/06, Thomas Morin <thomas.morin@rd.francetelecom.com> wrote:
> Well, I'm happy to know that my english is not so bad. Thank you,
> Dave. :)
>

Your English is pretty impeccable.

> However, to make sure the draft is readable by anyone, I rephrased this
> part to a more direct expression : " [some of these applications may
> involve rapid changes in customer multicast memberships as seen by the
> PE, but this will depend on audience patterns and on] the number of
> provider equipments deployed close to VPN customers".
>

Fine by me.

Regards
Marshall

> Cheers,
>
> -Thomas
>
> Marshall Eubanks:
> > Well, a google on the "capillarity of carrier network" (without the
> > quotes) does return 653 hits, so Dave is correct in that it is used
> > that way at least some, and I appreciate the education.
> >
> > However, note that capillarity is not (in English) the "quality or
> > state of being capillary" but is simply a noun describing the
> > phenomenon itself,  so I do not regard the above as proper English
> > usage and I would recommend against its use in a standards document.
> >
> > Regards
> > Marshall
> >
> >
> > On 1/17/06, David Meyer <dmm@1-4-5.net> wrote:
> > > > And, I have never seen  "capillarity" actually used in English. It'=
s
> > > > in the dictionary, even in my spell checker, and it might be used i=
n
> > > > botany, but it's not used metaphorically.
> > >
> > >
> > >         As I was mentioning to Marshall earlier, actually, the
> > >         term capillarity is in common use in the carrier industry
> > >         (usually used to describe the extent and density of a
> > >         carrier's transport network). As such, I don't find the
> > >         fact the google doesn't know that disqualifying, and
> > >         further, most of us who have worked in that side of the
> > >         industry consider it common usage.
> > >
> > >         Dave
> > >
> > >
> > >
> >
>
>




From l3vpn-bounces@ietf.org Wed Jan 18 09:27:30 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EzEHa-0002Pw-Nv; Wed, 18 Jan 2006 09:27:30 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EzEHZ-0002Pk-Dg
	for l3vpn@megatron.ietf.org; Wed, 18 Jan 2006 09:27:29 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA17491
	for <l3vpn@ietf.org>; Wed, 18 Jan 2006 09:26:02 -0500 (EST)
Received: from p-mail1.rd.francetelecom.com ([195.101.245.15])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EzEPs-0003ee-Ev
	for l3vpn@ietf.org; Wed, 18 Jan 2006 09:36:06 -0500
Received: from ftrdmel10.rd.francetelecom.fr ([10.193.117.156]) by
	ftrdsmtp1.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.211); 
	Wed, 18 Jan 2006 15:11:32 +0100
Received: from l-at8613.rd.francetelecom.fr ([10.193.15.32]) by
	ftrdmel10.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.211); 
	Wed, 18 Jan 2006 15:11:32 +0100
From: Thomas Morin <thomas.morin@rd.francetelecom.com>
To: Marshall Eubanks <marshall.eubanks@gmail.com>
In-Reply-To: <dcad22d80601180449l1ee6312naaa5cf47d5aff626@mail.gmail.com>
References: <43BBE0D5.2060607@juniper.net>
	<dcad22d80601102236u373871a7qb6f7636e5b7bbfcd@mail.gmail.com>
	<1137417200.15352.113.camel@wintermute>
	<dcad22d80601180449l1ee6312naaa5cf47d5aff626@mail.gmail.com>
Content-Type: text/plain
Organization: France Telecom R&D
Date: Wed, 18 Jan 2006 15:11:31 +0100
Message-Id: <1137593491.8691.15.camel@wintermute>
Mime-Version: 1.0
X-Mailer: Evolution 2.4.2.1 
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 18 Jan 2006 14:11:32.0204 (UTC)
	FILETIME=[1542A2C0:01C61C39]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4d87d2aa806f79fed918a62e834505ca
Content-Transfer-Encoding: 7bit
Cc: L3VPN <l3vpn@ietf.org>
Subject: Re: WG last call: draft-ietf-l3vpn-ppvpn-mcast-reqts-03
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: l3vpn.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:l3vpn@ietf.org>
List-Help: <mailto:l3vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=subscribe>
Sender: l3vpn-bounces@ietf.org
Errors-To: l3vpn-bounces@ietf.org

Hi Marshall,

Marshall Eubanks:
> > >    The use of globally unique means of multicast-based service
> > >    identification at the scale of the domain where such services are
> > >    provided SHOULD be recommended.  If the ASM model is used, this
> > >
> > > tme> SSM also has source scoping, 239/8 can be used with either SSM or ASM. Therefore
> > > tme> s/If the ASM model is used, this/For IPv4 multicasts, this/
> >
> > I rephrased as follows:
> >
> > "For IPv4 multicast, this implies the use of the multicast
> > administratively scoped range, (239/8 as defined by [RFC2365]) for
> > services which are to be used only inside the VPN, and of or SSM-range
> 
> s/of or SSM-range/of either global SSM-range/
> 
> to correct a typo and to make it clear that 232 is intended for global
> scope SSM.

Agreed.

> > >    Unwanted multicast traffic (e.g. multicast traffic that may be sent
> > >    by a source located somewhere in the Internet and for which there is
> > >    no interested receiver connected to a given VPN infrastructure) MUST
> > >    NOT be propagated within a multicast-enabled VPN.
> > >
> > > tme> Is this consistent with Section 5.2.2.3. ? It seems to me that this
> > > tme> should be a SHOULD NOT to allow for sub-optimal solutions
> >
> >
> > While it might be acceptable (for provider-side scalability) that some
> > traffic reaches a PE even if this is not needed, it would not be
> > acceptable that such traffic be propagated toward the CE, inside the
> > customer network.
> >
> > Isn't this reasonable ?
> 
> Reasonable, but in normal multicast it is common to get multiple
> packets when trees switch over.

A bit of misunderstanding here: we are just mandating that, in the same
way that traffic from a VPN doesn't reach another VPN, Internet
multicast traffic won't be routed inside a VPN that didn't make any such
multicast subscription.

In normal multicast, you are not supposed to route @G traffic to
somebody who only subscribed to @G' and @G'', right ?

-Thomas





From l3vpn-bounces@ietf.org Wed Jan 18 09:32:52 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EzEMm-0003Au-Po; Wed, 18 Jan 2006 09:32:52 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EzEMl-0003Ag-Di
	for l3vpn@megatron.ietf.org; Wed, 18 Jan 2006 09:32:51 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA17937
	for <l3vpn@ietf.org>; Wed, 18 Jan 2006 09:31:25 -0500 (EST)
Received: from zproxy.gmail.com ([64.233.162.200])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EzEV6-0003pS-0D
	for l3vpn@ietf.org; Wed, 18 Jan 2006 09:41:29 -0500
Received: by zproxy.gmail.com with SMTP id 9so1633153nzo
	for <l3vpn@ietf.org>; Wed, 18 Jan 2006 06:32:49 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
	h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=Cz0xVZ4Wy54/iXyD9Ib7mbNxZi4Ohs4cj7Kg1T5k0m5GIS2xHYjB7w8cmyKUnL7GT1659wIyS6NvZrlh1LAG0yhsWiKylDZaNwJqx1QiBIkbJYPp9DpYbnljONFAU8S+ugqUy1dMvfaeiX/U4oo015HRBe7b6uuqoAmzczUhHBk=
Received: by 10.37.14.38 with SMTP id r38mr6644611nzi;
	Wed, 18 Jan 2006 06:32:48 -0800 (PST)
Received: by 10.36.46.2 with HTTP; Wed, 18 Jan 2006 06:32:48 -0800 (PST)
Message-ID: <dcad22d80601180632i1640256cv1bc03428c082c7a2@mail.gmail.com>
Date: Wed, 18 Jan 2006 09:32:48 -0500
From: Marshall Eubanks <marshall.eubanks@gmail.com>
To: Thomas Morin <thomas.morin@rd.francetelecom.com>
In-Reply-To: <1137593491.8691.15.camel@wintermute>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <43BBE0D5.2060607@juniper.net>
	<dcad22d80601102236u373871a7qb6f7636e5b7bbfcd@mail.gmail.com>
	<1137417200.15352.113.camel@wintermute>
	<dcad22d80601180449l1ee6312naaa5cf47d5aff626@mail.gmail.com>
	<1137593491.8691.15.camel@wintermute>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: fb6060cb60c0cea16e3f7219e40a0a81
Content-Transfer-Encoding: quoted-printable
Cc: L3VPN <l3vpn@ietf.org>
Subject: Re: WG last call: draft-ietf-l3vpn-ppvpn-mcast-reqts-03
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: l3vpn.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:l3vpn@ietf.org>
List-Help: <mailto:l3vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=subscribe>
Sender: l3vpn-bounces@ietf.org
Errors-To: l3vpn-bounces@ietf.org

Hello;

On 1/18/06, Thomas Morin <thomas.morin@rd.francetelecom.com> wrote:
> Hi Marshall,
>
> Marshall Eubanks:
> > > >    The use of globally unique means of multicast-based service
> > > >    identification at the scale of the domain where such services ar=
e
> > > >    provided SHOULD be recommended.  If the ASM model is used, this
> > > >
> > > > tme> SSM also has source scoping, 239/8 can be used with either SSM=
 or ASM. Therefore
> > > > tme> s/If the ASM model is used, this/For IPv4 multicasts, this/
> > >
> > > I rephrased as follows:
> > >
> > > "For IPv4 multicast, this implies the use of the multicast
> > > administratively scoped range, (239/8 as defined by [RFC2365]) for
> > > services which are to be used only inside the VPN, and of or SSM-rang=
e
> >
> > s/of or SSM-range/of either global SSM-range/
> >
> > to correct a typo and to make it clear that 232 is intended for global
> > scope SSM.
>
> Agreed.
>
> > > >    Unwanted multicast traffic (e.g. multicast traffic that may be s=
ent
> > > >    by a source located somewhere in the Internet and for which ther=
e is
> > > >    no interested receiver connected to a given VPN infrastructure) =
MUST
> > > >    NOT be propagated within a multicast-enabled VPN.
> > > >
> > > > tme> Is this consistent with Section 5.2.2.3. ? It seems to me that=
 this
> > > > tme> should be a SHOULD NOT to allow for sub-optimal solutions
> > >
> > >
> > > While it might be acceptable (for provider-side scalability) that som=
e
> > > traffic reaches a PE even if this is not needed, it would not be
> > > acceptable that such traffic be propagated toward the CE, inside the
> > > customer network.
> > >
> > > Isn't this reasonable ?
> >
> > Reasonable, but in normal multicast it is common to get multiple
> > packets when trees switch over.
>
> A bit of misunderstanding here: we are just mandating that, in the same
> way that traffic from a VPN doesn't reach another VPN, Internet
> multicast traffic won't be routed inside a VPN that didn't make any such
> multicast subscription.
>
> In normal multicast, you are not supposed to route @G traffic to
> somebody who only subscribed to @G' and @G'', right ?
>

Yes, I agree. I was misunderstanding your meaning.

I think it is necessary to see the whole document again with the
various corrections to be sure these are all correct.

> -Thomas
>

Marshall

>




From l3vpn-bounces@ietf.org Wed Jan 18 09:55:12 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EzEiN-00012k-Vt; Wed, 18 Jan 2006 09:55:11 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EzEiL-00012T-U8
	for l3vpn@megatron.ietf.org; Wed, 18 Jan 2006 09:55:10 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA20306
	for <l3vpn@ietf.org>; Wed, 18 Jan 2006 09:53:43 -0500 (EST)
Received: from colo-dns-ext2.juniper.net ([207.17.137.64])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EzEqg-0004ib-FP
	for l3vpn@ietf.org; Wed, 18 Jan 2006 10:03:48 -0500
Received: from merlot.juniper.net (merlot.juniper.net [172.17.27.10])
	by colo-dns-ext2.juniper.net (8.12.3/8.12.3) with ESMTP id
	k0IEsx1Z061929; Wed, 18 Jan 2006 06:54:59 -0800 (PST)
	(envelope-from yakov@juniper.net)
Received: from juniper.net (sapphire.juniper.net [172.17.28.108])
	by merlot.juniper.net (8.11.3/8.11.3) with ESMTP id k0IEsw508342;
	Wed, 18 Jan 2006 06:54:58 -0800 (PST)
	(envelope-from yakov@juniper.net)
Message-Id: <200601181454.k0IEsw508342@merlot.juniper.net>
To: thomas.morin@rd.francetelecom.com
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <64944.1137596098.1@juniper.net>
Date: Wed, 18 Jan 2006 06:54:58 -0800
From: Yakov Rekhter <yakov@juniper.net>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb
Cc: l3vpn@ietf.org
Subject: Re: comments on draft-ietf-l3vpn-ppvpn-mcast-reqts-03 
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: l3vpn.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:l3vpn@ietf.org>
List-Help: <mailto:l3vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=subscribe>
Sender: l3vpn-bounces@ietf.org
Errors-To: l3vpn-bounces@ietf.org

Thomas,

> > 5.1.11.  RP Engineering
> > 
> >     When PIM-SM (or bidir-PIM) is used in ASM mode on the VPN customer
> >     side, the location of the RP has to be chosen.  In some cases this
> >     engineering problem is not trivial: for instance, if sources and
> >     receivers are located in VPN sites that are different than that of
> >     the RP, then traffic may flow twice through the SP network and the
> >     CE-PE link of the RP (from source to RP, and then from RP to
> >     receivers) ; this is obviously not ideal.  A multicast VPN solution
> >     SHOULD propose a way to help on solving this RP engineering issue.
> > 
> > ==> I'm not sure if this specific problem exists in practice.  If the 
> > RP sends Register-Stop, the multicast traffic is forwarded natively, 
> > and the data will short-cut inside the site without going to the RP 
> > and then back.  I.e., there should not be two times traffic once the 
> > forwarding is native.
> 
> Well...
> 1) even such transient peaks may not be something that you'll want
> 2) what if you lose connectivity to the remote site hosting the RP, are
> you happy to lose local multicast on every other site?
> 3) what if you want to stick with RPT ? 
>    [okay, maybe not so relevant, but what if the VPN customer wants to
>     do this ?]

Wrt your second point I think it would be highly desirable for a
solution to maintain multicast service among all the sites within
an MVPN that maintain connectivity among themselves, even when the
site(s) hosting the RP lose their connectivity.

Likewise, it would be highly desirable for a site that loses
connectivity to the service provider to maintain multicast service
within that site.

I would suggest to include both of the above points in the requirements
document.

Yakov.





From l3vpn-bounces@ietf.org Wed Jan 18 15:50:52 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EzKGa-00049l-KL; Wed, 18 Jan 2006 15:50:52 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EzKFs-0003wx-EH; Wed, 18 Jan 2006 15:50:08 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA22361;
	Wed, 18 Jan 2006 15:48:40 -0500 (EST)
Received: from [132.151.6.50] (helo=newodin.ietf.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1EzKOC-0000yl-1H; Wed, 18 Jan 2006 15:58:45 -0500
Received: from mlee by newodin.ietf.org with local (Exim 4.43)
	id 1EzKFm-0007Je-Ab; Wed, 18 Jan 2006 15:50:02 -0500
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1EzKFm-0007Je-Ab@newodin.ietf.org>
Date: Wed, 18 Jan 2006 15:50:02 -0500
X-Spam-Score: 0.4 (/)
X-Scan-Signature: 73734d43604d52d23b3eba644a169745
Cc: l3vpn@ietf.org
Subject: I-D ACTION:draft-ietf-l3vpn-ppvpn-mcast-reqts-04.txt 
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: l3vpn.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:l3vpn@ietf.org>
List-Help: <mailto:l3vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=subscribe>
Sender: l3vpn-bounces@ietf.org
Errors-To: l3vpn-bounces@ietf.org

--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		: Requirements for Multicast in L3 Provider-Provisioned VPNs
	Author(s)	: T. Morin
	Filename	: draft-ietf-l3vpn-ppvpn-mcast-reqts-04.txt
	Pages		: 52
	Date		: 2006-1-18
	
This document presents a set of functional requirements for network
   solutions that allow the deployment of IP multicast within L3
   Provider Provisioned virtual private networks (PPVPNs).  It specifies
   requirements both from the end user and service provider standpoints.
   It is intended that potential solutions specifying the support of IP
   multicast within such VPNs will use these requirements as guidelines.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-l3vpn-ppvpn-mcast-reqts-04.txt

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of the message.  
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.


Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-l3vpn-ppvpn-mcast-reqts-04.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-l3vpn-ppvpn-mcast-reqts-04.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
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: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body; access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID: <2006-1-18135113.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-l3vpn-ppvpn-mcast-reqts-04.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-l3vpn-ppvpn-mcast-reqts-04.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2006-1-18135113.I-D@ietf.org>


--OtherAccess--

--NextPart--





From l3vpn-bounces@ietf.org Wed Jan 18 16:26:29 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EzKp3-0001WF-6G; Wed, 18 Jan 2006 16:26:29 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EzKp1-0001Vs-8U
	for l3vpn@megatron.ietf.org; Wed, 18 Jan 2006 16:26:27 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA02718
	for <l3vpn@ietf.org>; Wed, 18 Jan 2006 16:25:00 -0500 (EST)
Received: from borg.juniper.net ([207.17.137.119])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EzKxM-00051f-Is
	for l3vpn@ietf.org; Wed, 18 Jan 2006 16:35:08 -0500
Received: from unknown (HELO proton.jnpr.net) ([10.10.2.37])
	by borg.juniper.net with ESMTP; 18 Jan 2006 13:26:10 -0800
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
X-IronPort-AV: i="3.99,381,1131350400"; 
	d="scan'208"; a="523594295:sNHT21021432"
Received: from [172.23.1.123] ([172.23.1.123] RDNS failed) by proton.jnpr.net
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 18 Jan 2006 16:26:12 -0500
Message-ID: <43CEB26F.8090804@juniper.net>
Date: Wed, 18 Jan 2006 16:26:07 -0500
From: Ron Bonica <rbonica@juniper.net>
User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: l3vpn@ietf.org
References: <43A98DEB.2000309@juniper.net>
In-Reply-To: <43A98DEB.2000309@juniper.net>
X-Enigmail-Version: 0.93.0.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 18 Jan 2006 21:26:12.0683 (UTC)
	FILETIME=[CE6FE9B0:01C61C75]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d6b246023072368de71562c0ab503126
Content-Transfer-Encoding: 7bit
Subject: Re: IETF 65
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: l3vpn.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:l3vpn@ietf.org>
List-Help: <mailto:l3vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=subscribe>
Sender: l3vpn-bounces@ietf.org
Errors-To: l3vpn-bounces@ietf.org

Folks,

To date, I have only received one request for agenda time at IETF 65.

If you would like agenda time, please submit your request to the WG
chairs by February 1. Requests received at the last minute may not be
serviced.
                                       Ron


Ron Bonica wrote:
> Folks,
> 
> If you plan on presenting to the L3VPN WG at IETF 65, please send the WG
> chairs a heads-up in January. This will help us determine how much
> meeting time we need to request.
> 
>                                    Ron
> 




From l3vpn-bounces@ietf.org Wed Jan 18 23:24:49 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EzRLt-0005Id-GX; Wed, 18 Jan 2006 23:24:49 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EzRLs-0005IY-2N
	for l3vpn@megatron.ietf.org; Wed, 18 Jan 2006 23:24:48 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA16218
	for <l3vpn@ietf.org>; Wed, 18 Jan 2006 23:23:20 -0500 (EST)
Received: from zproxy.gmail.com ([64.233.162.196])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EzRUI-0006qD-Uu
	for l3vpn@ietf.org; Wed, 18 Jan 2006 23:33:33 -0500
Received: by zproxy.gmail.com with SMTP id 9so116159nzo
	for <l3vpn@ietf.org>; Wed, 18 Jan 2006 20:24:45 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
	h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=ohVCQUXNzPY8ZA0A7PSbJdTOn9iA9tCj/hKI9QdpG3rJWBNIaIp8tGuVBtokoQAKQ6FKobP7OEbzE38y90Ikj5rIeHChP4pDazpvJn2oBrXYdnVCJwFbmKO4jFPncOJKTtLyjwtTiVNjvN/31hHrPaN+tTQY+r7Kp2RuXBoh2QM=
Received: by 10.36.56.18 with SMTP id e18mr112045nza;
	Wed, 18 Jan 2006 20:24:44 -0800 (PST)
Received: by 10.36.46.2 with HTTP; Wed, 18 Jan 2006 20:24:44 -0800 (PST)
Message-ID: <dcad22d80601182024t6c3ab1edv1300e04de0ec53b0@mail.gmail.com>
Date: Wed, 18 Jan 2006 23:24:44 -0500
From: Marshall Eubanks <marshall.eubanks@gmail.com>
To: Yakov Rekhter <yakov@juniper.net>
In-Reply-To: <200601181454.k0IEsw508342@merlot.juniper.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <200601181454.k0IEsw508342@merlot.juniper.net>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b5d20af10c334b36874c0264b10f59f1
Content-Transfer-Encoding: quoted-printable
Cc: thomas.morin@rd.francetelecom.com, l3vpn@ietf.org
Subject: Re: comments on draft-ietf-l3vpn-ppvpn-mcast-reqts-03
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: l3vpn.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:l3vpn@ietf.org>
List-Help: <mailto:l3vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=subscribe>
Sender: l3vpn-bounces@ietf.org
Errors-To: l3vpn-bounces@ietf.org

Hello;

On 1/18/06, Yakov Rekhter <yakov@juniper.net> wrote:
> Thomas,
>
> > > 5.1.11.  RP Engineering
> > >
> > >     When PIM-SM (or bidir-PIM) is used in ASM mode on the VPN custome=
r
> > >     side, the location of the RP has to be chosen.  In some cases thi=
s
> > >     engineering problem is not trivial: for instance, if sources and
> > >     receivers are located in VPN sites that are different than that o=
f
> > >     the RP, then traffic may flow twice through the SP network and th=
e
> > >     CE-PE link of the RP (from source to RP, and then from RP to
> > >     receivers) ; this is obviously not ideal.  A multicast VPN soluti=
on
> > >     SHOULD propose a way to help on solving this RP engineering issue=
.
> > >
> > > =3D=3D> I'm not sure if this specific problem exists in practice.  If=
 the
> > > RP sends Register-Stop, the multicast traffic is forwarded natively,
> > > and the data will short-cut inside the site without going to the RP
> > > and then back.  I.e., there should not be two times traffic once the
> > > forwarding is native.
> >
> > Well...
> > 1) even such transient peaks may not be something that you'll want
> > 2) what if you lose connectivity to the remote site hosting the RP, are
> > you happy to lose local multicast on every other site?
> > 3) what if you want to stick with RPT ?
> >    [okay, maybe not so relevant, but what if the VPN customer wants to
> >     do this ?]
>

As a practical matter, the RPT to SPT cutover is either 1 or infinity.
In other words,
you switch after 1 packet, or you never switch.

In BiDir, for example, you never switch and all traffic flows through
the RP. So, this is very relevant and needs to be supported.

Generally, when you do switch, duplicate flows last order 1 RTT, but
you are almost certain to get some duplicates at the beginning of the
stream in ASM (not SSM). BiDir does not use Register encapsulation,
nor does it swtich to a SPT, so in BiDir there should not be a pulse
of duplicates.

Generally, in ASM, if you loose connectivity with the RP, you cannot
set up more streams except for on the local LAN (i.e., if your DR
knows about the stream, you're OK). Existing streams (in ASM, not
BiDir) will be unaffected if you have switched to the SPT. Anycast RP
will allow for failover if you have one "locally."  (Or, you could use
BSR or autoRP, but then you will loose any information about past
flows.)

> Wrt your second point I think it would be highly desirable for a
> solution to maintain multicast service among all the sites within
> an MVPN that maintain connectivity among themselves, even when the
> site(s) hosting the RP lose their connectivity.
>

Maintaining Multicast service is ambigous. In ASM, if you loose the
RP, existing streams are not affected, but you can't join a new stream
unless your DR knows about them. In BiDir, you loose everything.

> Likewise, it would be highly desirable for a site that loses
> connectivity to the service provider to maintain multicast service
> within that site.

That's pretty automatic if connectivity to the DR isn't lost (or if
the local site is one LAN); otherwise you need either anycast RP with
a local RP or BSR.

I do not think that L3VPN should worry about offering a more robust
multicast service than native multicast would offer; I would think the
goal would be to make the multicast VPN service transparent, so that
people could do their own multicast engineering.

>
> I would suggest to include both of the above points in the requirements
> document.
>
> Yakov.
>

Marshall

>
>




From l3vpn-bounces@ietf.org Mon Jan 23 11:57:13 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1F150D-0001Ng-8M; Mon, 23 Jan 2006 11:57:13 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1F150B-0001NV-3J
	for l3vpn@megatron.ietf.org; Mon, 23 Jan 2006 11:57:11 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA02339
	for <l3vpn@ietf.org>; Mon, 23 Jan 2006 11:55:41 -0500 (EST)
Received: from p-mail2.rd.francetelecom.com ([195.101.245.16])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1F159X-0004jZ-Su
	for l3vpn@ietf.org; Mon, 23 Jan 2006 12:06:52 -0500
Received: from ftrdmel10.rd.francetelecom.fr ([10.193.117.156]) by
	ftrdsmtp1.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.211); 
	Mon, 23 Jan 2006 17:57:02 +0100
Received: from l-at8613.rd.francetelecom.fr ([10.193.15.65]) by
	ftrdmel10.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.211); 
	Mon, 23 Jan 2006 17:57:01 +0100
From: Thomas Morin <thomas.morin@rd.francetelecom.com>
To: l3vpn@ietf.org
In-Reply-To: <200601181454.k0IEsw508342@merlot.juniper.net>
References: <200601181454.k0IEsw508342@merlot.juniper.net>
Content-Type: multipart/alternative; boundary="=-JakXWg3wB/+5xHABg8LG"
Organization: France Telecom R&D
Date: Mon, 23 Jan 2006 17:57:01 +0100
Message-Id: <1138035421.14305.4.camel@wintermute>
Mime-Version: 1.0
X-Mailer: Evolution 2.4.2.1 
X-OriginalArrivalTime: 23 Jan 2006 16:57:01.0727 (UTC)
	FILETIME=[07C85AF0:01C6203E]
X-Spam-Score: 0.6 (/)
X-Scan-Signature: db284e046c8702920c1c6125bc4d0b7a
Cc: Yakov Rekhter <yakov@juniper.net>, Pekka Savola <pekkas@netcore.fi>
Subject: Re: comments on draft-ietf-l3vpn-ppvpn-mcast-reqts-03
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: l3vpn.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:l3vpn@ietf.org>
List-Help: <mailto:l3vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=subscribe>
Sender: l3vpn-bounces@ietf.org
Errors-To: l3vpn-bounces@ietf.org


--=-JakXWg3wB/+5xHABg8LG
Content-Type: text/plain; charset=iso-8859-13
Content-Transfer-Encoding: quoted-printable

Pekka, Yakov, folks,


Yakov Rekhter:=20

>=20
> > > 5.1.11.  RP Engineering
> > >=20
> > >     When PIM-SM (or bidir-PIM) is used in ASM mode on the VPN custome=
r
> > >     side, the location of the RP has to be chosen.  In some cases thi=
s
> > >     engineering problem is not trivial: for instance, if sources and
> > >     receivers are located in VPN sites that are different than that o=
f
> > >     the RP, then traffic may flow twice through the SP network and th=
e
> > >     CE-PE link of the RP (from source to RP, and then from RP to
> > >     receivers) ; this is obviously not ideal.  A multicast VPN soluti=
on
> > >     SHOULD propose a way to help on solving this RP engineering issue=
.
> > >=20
> > > =3D=3D> I'm not sure if this specific problem exists in practice.  If=
 the=20
> > > RP sends Register-Stop, the multicast traffic is forwarded natively,=20
> > > and the data will short-cut inside the site without going to the RP=20
> > > and then back.  I.e., there should not be two times traffic once the=20
> > > forwarding is native.
> >=20
> > Well...
> > 1) even such transient peaks may not be something that you'll want
> > 2) what if you lose connectivity to the remote site hosting the RP, are
> > you happy to lose local multicast on every other site?
> > 3) what if you want to stick with RPT ?=20
> >    [okay, maybe not so relevant, but what if the VPN customer wants to
> >     do this ?]
>=20
> Wrt your second point I think it would be highly desirable for a
> solution to maintain multicast service among all the sites within
> an MVPN that maintain connectivity among themselves, even when the
> site(s) hosting the RP lose their connectivity.
>=20
> Likewise, it would be highly desirable for a site that loses
> connectivity to the service provider to maintain multicast service
> within that site.
>=20
> I would suggest to include both of the above points in the requirements
> document.


I do agree that the unavailability of the RP may be a stronger reason
that transient bandwidth peaks happening when forwarding switches from
PIM-register-encapsulated to native.

However, the initial reason for this section 5.1.11 is that:
a) it seems that some VPN clients would be happy to _not_ have to bother
with running RP(s) =20
b) it seems that some providers may happily host the RP function
So I don't want focus to get lost...

Below is my suggestion for a reshaped section 5.1.11.=20
It aims at distinguishing between the three different problems that we
may have: RP outsourcing, RP availability, RP location.

Feel free to comment.

Cheers,

-Thomas

----------------------------

5.1.11. RP Engineering
When PIM-SM (or bidir-PIM) is used in ASM mode on the VPN customer side,
the RP function (or RP-address in the case of bidir-PIM) has to be
associated to a node running PIM, and configured on this node.



________________________________________________________________________


5.1.11.1. RP Outsourcing

In the case of PIM-SM in ASM mode, engineering of the RP function
requires the deployment of specific protocols and associated
configurations. Some service provider may offer to manage customer's
multicast protocol operation on behalf of them. This implies that it is
necessary to consider cases where the customer's RPs are outsourced
(e.g., on PEs). Consequently, a VPN solution MAY support the hosting of
the RP function in a VR or VRF.



________________________________________________________________________


5.1.11.2. RP Availability

Availability of the RP function (or address) is required for proper
operation of PIM-SM (ASM mode) and bidir-PIM. Loss of connectivity to
the RP from a receiver or source will impact the multicast service. For
this reason different mecanisms exist, such as BSR(Bhaskar, N.,
=B4Bootstrap Router (BSR) Mechanism for PIM,=A1 October 2005.)
[I-D.ietf-pim-sm-bsr] or anycast-RP (MSDP based(Kim, D., Kilmer, H., and
D. Farinacci, =B4Anycast RP mechanism using PIM and MSDP,=A1 May 2001.)
[I-D.ietf-mboned-anycast-rp] or PIM based(Farinacci, D. and Y. Cai,
=B4Anycast-RP using PIM,=A1 August 2005.) [I-D.ietf-pim-anycast-rp]).

These protocols and procedures SHOULD work transparently through a
multicast VPN, and MAY, if relevant, be implemented in a VRF/VR.

Moreover, a multicast VPN solution MAY improve the robustness of the ASM
multicast service regarding loss of connnectivity to the RP, by
providing specific features that help :

        a) maintaining ASM multicast service among all the sites within
        an MVPN that maintain connectivity among themselves, even when
        the site(s) hosting the RP lose their connectivity to the MVPN
        b) maintaining ASM multicast service within any site that loses
        connectivity to the service provider=20



________________________________________________________________________


5.1.11.3. RP Location
In the case of PIM-SM, when a source starts to emit traffic toward a
group (in ASM mode), if sources and receivers are located in VPN sites
that are different than that of the RP, then traffic may transiently
flow twice through the SP network and the CE-PE link of the RP (from
source to RP, and then from RP to receivers). This traffic peak, even
short, may no be convenient depending on the traffic and link bandwidth.

Thus, a VPN solution MAY provide features that solve or help mitigate
this potential issue.


--=-JakXWg3wB/+5xHABg8LG
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
  <META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; CHARSET=3DUTF-8">
  <META NAME=3D"GENERATOR" CONTENT=3D"GtkHTML/3.8.1">
</HEAD>
<BODY>
Pekka, Yakov, folks,<BR>
<BR>
<BR>
Yakov Rekhter:=20
<BLOCKQUOTE TYPE=3DCITE>
<PRE>

<FONT COLOR=3D"#000000">&gt; &gt; 5.1.11.  RP Engineering</FONT>
<FONT COLOR=3D"#000000">&gt; &gt; </FONT>
<FONT COLOR=3D"#000000">&gt; &gt;     When PIM-SM (or bidir-PIM) is used in=
 ASM mode on the VPN customer</FONT>
<FONT COLOR=3D"#000000">&gt; &gt;     side, the location of the RP has to b=
e chosen.  In some cases this</FONT>
<FONT COLOR=3D"#000000">&gt; &gt;     engineering problem is not trivial: f=
or instance, if sources and</FONT>
<FONT COLOR=3D"#000000">&gt; &gt;     receivers are located in VPN sites th=
at are different than that of</FONT>
<FONT COLOR=3D"#000000">&gt; &gt;     the RP, then traffic may flow twice t=
hrough the SP network and the</FONT>
<FONT COLOR=3D"#000000">&gt; &gt;     CE-PE link of the RP (from source to =
RP, and then from RP to</FONT>
<FONT COLOR=3D"#000000">&gt; &gt;     receivers) ; this is obviously not id=
eal.  A multicast VPN solution</FONT>
<FONT COLOR=3D"#000000">&gt; &gt;     SHOULD propose a way to help on solvi=
ng this RP engineering issue.</FONT>
<FONT COLOR=3D"#000000">&gt; &gt; </FONT>
<FONT COLOR=3D"#000000">&gt; &gt; =3D=3D&gt; I'm not sure if this specific =
problem exists in practice.  If the </FONT>
<FONT COLOR=3D"#000000">&gt; &gt; RP sends Register-Stop, the multicast tra=
ffic is forwarded natively, </FONT>
<FONT COLOR=3D"#000000">&gt; &gt; and the data will short-cut inside the si=
te without going to the RP </FONT>
<FONT COLOR=3D"#000000">&gt; &gt; and then back.  I.e., there should not be=
 two times traffic once the </FONT>
<FONT COLOR=3D"#000000">&gt; &gt; forwarding is native.</FONT>
<FONT COLOR=3D"#000000">&gt; </FONT>
<FONT COLOR=3D"#000000">&gt; Well...</FONT>
<FONT COLOR=3D"#000000">&gt; 1) even such transient peaks may not be someth=
ing that you'll want</FONT>
<FONT COLOR=3D"#000000">&gt; 2) what if you lose connectivity to the remote=
 site hosting the RP, are</FONT>
<FONT COLOR=3D"#000000">&gt; you happy to lose local multicast on every oth=
er site?</FONT>
<FONT COLOR=3D"#000000">&gt; 3) what if you want to stick with RPT ? </FONT=
>
<FONT COLOR=3D"#000000">&gt;    [okay, maybe not so relevant, but what if t=
he VPN customer wants to</FONT>
<FONT COLOR=3D"#000000">&gt;     do this ?]</FONT>

<FONT COLOR=3D"#000000">Wrt your second point I think it would be highly de=
sirable for a</FONT>
<FONT COLOR=3D"#000000">solution to maintain multicast service among all th=
e sites within</FONT>
<FONT COLOR=3D"#000000">an MVPN that maintain connectivity among themselves=
, even when the</FONT>
<FONT COLOR=3D"#000000">site(s) hosting the RP lose their connectivity.</FO=
NT>

<FONT COLOR=3D"#000000">Likewise, it would be highly desirable for a site t=
hat loses</FONT>
<FONT COLOR=3D"#000000">connectivity to the service provider to maintain mu=
lticast service</FONT>
<FONT COLOR=3D"#000000">within that site.</FONT>

<FONT COLOR=3D"#000000">I would suggest to include both of the above points=
 in the requirements</FONT>
<FONT COLOR=3D"#000000">document.</FONT>
</PRE>
</BLOCKQUOTE>
<BR>
I do agree that the unavailability of the RP may be a stronger reason that =
transient bandwidth peaks happening when forwarding switches from PIM-regis=
ter-encapsulated to native.<BR>
<BR>
However, the initial reason for this section 5.1.11 is that:<BR>
a) it seems that some VPN clients would be happy to _not_ have to bother wi=
th running RP(s)&nbsp; <BR>
b) it seems that some providers may happily host the RP function<BR>
So I don't want focus to get lost...<BR>
<BR>
Below is my suggestion for a reshaped section 5.1.11. <BR>
It aims at distinguishing between the three different problems that we may =
have: RP outsourcing, RP availability, RP location.<BR>
<BR>
Feel free to comment.<BR>
<BR>
Cheers,<BR>
<BR>
-Thomas<BR>
<BR>
----------------------------<BR>
<BR>
<B><FONT SIZE=3D"4">5.1.11.&nbsp;RP Engineering</FONT></B><BR>
When PIM-SM (or bidir-PIM) is used in ASM mode on the VPN customer side, th=
e RP function (or RP-address in the case of bidir-PIM) has to be associated=
 to a node running PIM, and configured on this node.<BR>
<BR>
<BR>

<HR>
<BR>
<BR>
<H3>
<B><FONT SIZE=3D"4">5.1.11.1.&nbsp;RP Outsourcing</FONT></B>
</H3>
In the case of PIM-SM in ASM mode, engineering of the RP function requires =
the deployment of specific protocols and associated configurations. Some se=
rvice provider may offer to manage customer's multicast protocol operation =
on behalf of them. This implies that it is necessary to consider cases wher=
e the customer's RPs are outsourced (e.g., on PEs). Consequently, a VPN sol=
ution MAY support the hosting of the RP function in a VR or VRF.<BR>
<BR>
<BR>

<HR>
<BR>
<BR>
<H3>
<B><FONT SIZE=3D"4">5.1.11.2.&nbsp;RP Availability</FONT></B>
</H3>
Availability of the RP function (or address) is required for proper operati=
on of PIM-SM (ASM mode) and bidir-PIM. Loss of connectivity to the RP from =
a receiver or source will impact the multicast service. For this reason dif=
ferent mecanisms exist, such as <A HREF=3D"file:///home/teom7365/.mirror/Ho=
me/Mes%20Documents/IETF/draft-workzone/mvpn%20requirements/draft-ietf-l3vpn=
-ppvpn-mcast-reqts-05-p01.expanded.html#I-D.ietf-pim-sm-bsr">BSR</A><A HREF=
=3D"file:///home/teom7365/.mirror/Home/Mes%20Documents/IETF/draft-workzone/=
mvpn%20requirements/draft-ietf-l3vpn-ppvpn-mcast-reqts-05-p01.expanded.html=
#I-D.ietf-pim-sm-bsr">(</A><A HREF=3D"file:///home/teom7365/.mirror/Home/Me=
s%20Documents/IETF/draft-workzone/mvpn%20requirements/draft-ietf-l3vpn-ppvp=
n-mcast-reqts-05-p01.expanded.html#I-D.ietf-pim-sm-bsr">Bhaskar, N., &#8220=
;Bootstrap Router (BSR) Mechanism for PIM,&#8221; October&nbsp;2005.</A><A =
HREF=3D"file:///home/teom7365/.mirror/Home/Mes%20Documents/IETF/draft-workz=
one/mvpn%20requirements/draft-ietf-l3vpn-ppvpn-mcast-reqts-05-p01.expanded.=
html#I-D.ietf-pim-sm-bsr">)</A> [I-D.ietf-pim-sm-bsr] or anycast-RP (<A HRE=
F=3D"file:///home/teom7365/.mirror/Home/Mes%20Documents/IETF/draft-workzone=
/mvpn%20requirements/draft-ietf-l3vpn-ppvpn-mcast-reqts-05-p01.expanded.htm=
l#I-D.ietf-mboned-anycast-rp">MSDP based</A><A HREF=3D"file:///home/teom736=
5/.mirror/Home/Mes%20Documents/IETF/draft-workzone/mvpn%20requirements/draf=
t-ietf-l3vpn-ppvpn-mcast-reqts-05-p01.expanded.html#I-D.ietf-mboned-anycast=
-rp">(</A><A HREF=3D"file:///home/teom7365/.mirror/Home/Mes%20Documents/IET=
F/draft-workzone/mvpn%20requirements/draft-ietf-l3vpn-ppvpn-mcast-reqts-05-=
p01.expanded.html#I-D.ietf-mboned-anycast-rp">Kim, D., Kilmer, H., and D. F=
arinacci, &#8220;Anycast RP mechanism using PIM and MSDP,&#8221; May&nbsp;2=
001.</A><A HREF=3D"file:///home/teom7365/.mirror/Home/Mes%20Documents/IETF/=
draft-workzone/mvpn%20requirements/draft-ietf-l3vpn-ppvpn-mcast-reqts-05-p0=
1.expanded.html#I-D.ietf-mboned-anycast-rp">)</A> [I-D.ietf-mboned-anycast-=
rp] or <A HREF=3D"file:///home/teom7365/.mirror/Home/Mes%20Documents/IETF/d=
raft-workzone/mvpn%20requirements/draft-ietf-l3vpn-ppvpn-mcast-reqts-05-p01=
.expanded.html#I-D.ietf-pim-anycast-rp">PIM based</A><A HREF=3D"file:///hom=
e/teom7365/.mirror/Home/Mes%20Documents/IETF/draft-workzone/mvpn%20requirem=
ents/draft-ietf-l3vpn-ppvpn-mcast-reqts-05-p01.expanded.html#I-D.ietf-pim-a=
nycast-rp">(</A><A HREF=3D"file:///home/teom7365/.mirror/Home/Mes%20Documen=
ts/IETF/draft-workzone/mvpn%20requirements/draft-ietf-l3vpn-ppvpn-mcast-req=
ts-05-p01.expanded.html#I-D.ietf-pim-anycast-rp">Farinacci, D. and Y. Cai, =
&#8220;Anycast-RP using PIM,&#8221; August&nbsp;2005.</A><A HREF=3D"file://=
/home/teom7365/.mirror/Home/Mes%20Documents/IETF/draft-workzone/mvpn%20requ=
irements/draft-ietf-l3vpn-ppvpn-mcast-reqts-05-p01.expanded.html#I-D.ietf-p=
im-anycast-rp">)</A> [I-D.ietf-pim-anycast-rp]).<BR>
<BR>
These protocols and procedures SHOULD work transparently through a multicas=
t VPN, and MAY, if relevant, be implemented in a VRF/VR.<BR>
<BR>
Moreover, a multicast VPN solution MAY improve the robustness of the ASM mu=
lticast service regarding loss of connnectivity to the RP, by providing spe=
cific features that help :<BR>
<BLOCKQUOTE>
    <DL>
        a) maintaining ASM multicast service among all the sites within an =
MVPN that maintain connectivity among themselves, even when the site(s) hos=
ting the RP lose their connectivity to the MVPN<BR>
        b) maintaining ASM multicast service within any site that loses con=
nectivity to the service provider <BR>
    </DL>
</BLOCKQUOTE>
<BR>

<HR>
<BR>
<BR>
<TABLE CELLPADDING=3D"0">
<TR>
<TD>
<BR>
</TD>
</TR>
</TABLE>
<B><FONT SIZE=3D"4">5.1.11.3.&nbsp;RP Location</FONT></B><BR>
In the case of PIM-SM, when a source starts to emit traffic toward a group =
(in ASM mode), if sources and receivers are located in VPN sites that are d=
ifferent than that of the RP, then traffic may transiently flow twice throu=
gh the SP network and the CE-PE link of the RP (from source to RP, and then=
 from RP to receivers). This traffic peak, even short, may no be convenient=
 depending on the traffic and link bandwidth.<BR>
<BR>
Thus, a VPN solution MAY provide features that solve or help mitigate this =
potential issue.<BR>
<BR>
</BODY>
</HTML>

--=-JakXWg3wB/+5xHABg8LG--





From l3vpn-bounces@ietf.org Mon Jan 23 23:41:12 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1F1FzU-00067u-0C; Mon, 23 Jan 2006 23:41:12 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1F1FzS-00067p-Cd
	for l3vpn@megatron.ietf.org; Mon, 23 Jan 2006 23:41:10 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA04499
	for <l3vpn@ietf.org>; Mon, 23 Jan 2006 23:39:40 -0500 (EST)
Received: from zproxy.gmail.com ([64.233.162.196])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1F1G8w-00006g-9l
	for l3vpn@ietf.org; Mon, 23 Jan 2006 23:50:58 -0500
Received: by zproxy.gmail.com with SMTP id 9so1062056nzo
	for <l3vpn@ietf.org>; Mon, 23 Jan 2006 20:41:08 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
	h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=SldFfQnqeujxO5POQwo/z51NR268JQYZyZUAYX2aDKmQ9crL7Tcvje5ystgcbrX8Mpb1062nvNwEUZhV84seHlovhrDioPpLHEiZBo+BmXj9S1ioQLXYGMm610rOj1OyIhc4t6P6uthnZ+ZIyE9hFEzQDuDtvIV1YeP9HiXVwew=
Received: by 10.36.97.8 with SMTP id u8mr2542743nzb;
	Mon, 23 Jan 2006 20:41:08 -0800 (PST)
Received: by 10.36.41.20 with HTTP; Mon, 23 Jan 2006 20:41:08 -0800 (PST)
Message-ID: <dcad22d80601232041pd6e848du1dfe2c2961813fd6@mail.gmail.com>
Date: Mon, 23 Jan 2006 23:41:08 -0500
From: Marshall Eubanks <marshall.eubanks@gmail.com>
To: Thomas Morin <thomas.morin@rd.francetelecom.com>
In-Reply-To: <1138035421.14305.4.camel@wintermute>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <200601181454.k0IEsw508342@merlot.juniper.net>
	<1138035421.14305.4.camel@wintermute>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 225414c974e0d6437992164e91287a51
Content-Transfer-Encoding: quoted-printable
Cc: Yakov Rekhter <yakov@juniper.net>, l3vpn@ietf.org,
	Pekka Savola <pekkas@netcore.fi>
Subject: Re: comments on draft-ietf-l3vpn-ppvpn-mcast-reqts-03
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: l3vpn.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:l3vpn@ietf.org>
List-Help: <mailto:l3vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=subscribe>
Sender: l3vpn-bounces@ietf.org
Errors-To: l3vpn-bounces@ietf.org

Dear Thomas;

This looks OK. Some suggestions and a question in line.

Marshall

On 1/23/06, Thomas Morin <thomas.morin@rd.francetelecom.com> wrote:
>  Pekka, Yakov, folks,
>
>
>  Yakov Rekhter:
>
> > > 5.1.11. RP Engineering
> > >
> > > When PIM-SM (or bidir-PIM) is used in ASM mode on the VPN customer
> > > side, the location of the RP has to be chosen. In some cases this
> > > engineering problem is not trivial: for instance, if sources and
> > > receivers are located in VPN sites that are different than that of
> > > the RP, then traffic may flow twice through the SP network and the
> > > CE-PE link of the RP (from source to RP, and then from RP to
> > > receivers) ; this is obviously not ideal. A multicast VPN solution
> > > SHOULD propose a way to help on solving this RP engineering issue.
> > >
> > > =3D=3D> I'm not sure if this specific problem exists in practice. If =
the
> > > RP sends Register-Stop, the multicast traffic is forwarded natively,
> > > and the data will short-cut inside the site without going to the RP
> > > and then back. I.e., there should not be two times traffic once the
> > > forwarding is native.
> >
> > Well...
> > 1) even such transient peaks may not be something that you'll want
> > 2) what if you lose connectivity to the remote site hosting the RP, are
> > you happy to lose local multicast on every other site?
> > 3) what if you want to stick with RPT ?
> > [okay, maybe not so relevant, but what if the VPN customer wants to
> > do this ?]
>
> Wrt your second point I think it would be highly desirable for a
> solution to maintain multicast service among all the sites within
> an MVPN that maintain connectivity among themselves, even when the
> site(s) hosting the RP lose their connectivity.
>
> Likewise, it would be highly desirable for a site that loses
> connectivity to the service provider to maintain multicast service
> within that site.
>
> I would suggest to include both of the above points in the requirements
> document.
>
>
>  I do agree that the unavailability of the RP may be a stronger reason th=
at
> transient bandwidth peaks happening when forwarding switches from
> PIM-register-encapsulated to native.
>
>  However, the initial reason for this section 5.1.11 is that:
>  a) it seems that some VPN clients would be happy to _not_ have to bother
> with running RP(s)
>  b) it seems that some providers may happily host the RP function
>  So I don't want focus to get lost...
>
>  Below is my suggestion for a reshaped section 5.1.11.
>  It aims at distinguishing between the three different problems that we m=
ay
> have: RP outsourcing, RP availability, RP location.
>
>  Feel free to comment.
>
>  Cheers,
>
>  -Thomas
>
>  ----------------------------
>
>  5.1.11. RP Engineering
>  When PIM-SM (or bidir-PIM) is used in ASM mode on the VPN customer side,
> the RP function (or RP-address in the case of bidir-PIM) has to be
> associated to a node running PIM, and configured on this node.
>
>
>  ________________________________
>
>
>
>  5.1.11.1. RP Outsourcing In the case of PIM-SM in ASM mode, engineering =
of
> the RP function requires the deployment of specific protocols and associa=
ted
> configurations. Some service provider may offer to manage customer's
> multicast protocol operation on behalf of them. This implies that it is

s/on behalf of them/on their behalf/

> necessary to consider cases where the customer's RPs are outsourced (e.g.=
,
> on PEs). Consequently, a VPN solution MAY support the hosting of the RP
> function in a VR or VRF.
>
>
>  ________________________________
>
>
>
>  5.1.11.2. RP Availability Availability of the RP function (or address) i=
s
> required for proper operation of PIM-SM (ASM mode) and bidir-PIM. Loss of
> connectivity to the RP from a receiver or source will impact the multicas=
t
> service. For this reason different mecanisms exist, such as BSR(Bhaskar, =
N.,
> "Bootstrap Router (BSR) Mechanism for PIM," October 2005.)
> [I-D.ietf-pim-sm-bsr] or anycast-RP (MSDP based(Kim, D., Kilmer, H., and =
D.
> Farinacci, "Anycast RP mechanism using PIM and MSDP," May 2001.)
> [I-D.ietf-mboned-anycast-rp] or PIM based(Farinacci, D. and Y. Cai,
> "Anycast-RP using PIM," August 2005.) [I-D.ietf-pim-anycast-rp]).
>
>  These protocols and procedures SHOULD work transparently through a
> multicast VPN, and MAY, if relevant, be implemented in a VRF/VR.
>
>  Moreover, a multicast VPN solution MAY improve the robustness of the ASM
> multicast service regarding loss of connnectivity to the RP, by providing
> specific features that help :
>
>  a) maintaining ASM multicast service among all the sites within an MVPN

s/maintaining/maintain/

> that maintain connectivity among themselves, even when the site(s) hostin=
g
> the RP lose their connectivity to the MVPN

Is this an "and" or an "or" here ? I would say and.

>  b) maintaining ASM multicast service within any site that loses
> connectivity to the service provider
>
>  ________________________________
>
>
>
>
>  5.1.11.3. RP Location
>  In the case of PIM-SM, when a source starts to emit traffic toward a gro=
up
> (in ASM mode), if sources and receivers are located in VPN sites that are
> different than that of the RP, then traffic may transiently flow twice
> through the SP network and the CE-PE link of the RP (from source to RP, a=
nd
> then from RP to receivers). This traffic peak, even short, may no be

s/no/not/

> convenient depending on the traffic and link bandwidth.
>
>  Thus, a VPN solution MAY provide features that solve or help mitigate th=
is
> potential issue.
>
>




From l3vpn-bounces@ietf.org Mon Jan 23 23:44:59 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1F1G39-000842-PZ; Mon, 23 Jan 2006 23:44:59 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1F1G37-00083x-VU
	for l3vpn@megatron.ietf.org; Mon, 23 Jan 2006 23:44:58 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA04836
	for <l3vpn@ietf.org>; Mon, 23 Jan 2006 23:43:26 -0500 (EST)
Received: from zproxy.gmail.com ([64.233.162.204])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1F1GCX-0000Fr-Nv
	for l3vpn@ietf.org; Mon, 23 Jan 2006 23:54:44 -0500
Received: by zproxy.gmail.com with SMTP id 9so1062707nzo
	for <l3vpn@ietf.org>; Mon, 23 Jan 2006 20:44:52 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
	h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=Lcb5n8kfCLsuKqHCu1lnkiDPfrKIvNfGkRB+ELklVSh1T+cNe5T9GgFmMhGQkZ09Sh3DeMgMXL3q4uRzuexuO3drlK4chFTeG5hZgTzwkMTzX+MtVVR5XJ0RWvEurN+F+oMUZBUJz77lfsPmQUIsQh1z5fHr0Je6FPPl7XRwpmY=
Received: by 10.36.101.4 with SMTP id y4mr4388467nzb;
	Mon, 23 Jan 2006 20:44:52 -0800 (PST)
Received: by 10.36.41.20 with HTTP; Mon, 23 Jan 2006 20:44:52 -0800 (PST)
Message-ID: <dcad22d80601232044j39ae50f2w9772491e40b4cfc2@mail.gmail.com>
Date: Mon, 23 Jan 2006 23:44:52 -0500
From: Marshall Eubanks <marshall.eubanks@gmail.com>
To: Thomas Morin <thomas.morin@rd.francetelecom.com>
In-Reply-To: <dcad22d80601232041pd6e848du1dfe2c2961813fd6@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <200601181454.k0IEsw508342@merlot.juniper.net>
	<1138035421.14305.4.camel@wintermute>
	<dcad22d80601232041pd6e848du1dfe2c2961813fd6@mail.gmail.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ded6070f7eed56e10c4f4d0d5043d9c7
Content-Transfer-Encoding: quoted-printable
Cc: Yakov Rekhter <yakov@juniper.net>, l3vpn@ietf.org,
	Pekka Savola <pekkas@netcore.fi>
Subject: Re: comments on draft-ietf-l3vpn-ppvpn-mcast-reqts-03
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: l3vpn.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:l3vpn@ietf.org>
List-Help: <mailto:l3vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=subscribe>
Sender: l3vpn-bounces@ietf.org
Errors-To: l3vpn-bounces@ietf.org

In 5.1.11.2 "b" also need

s/maintaining/maintain/

(Or, you can keep both "maintaining" and add

by providing specific features that help :

s/help/help by/

On 1/23/06, Marshall Eubanks <marshall.eubanks@gmail.com> wrote:
> Dear Thomas;
>
> This looks OK. Some suggestions and a question in line.
>
> Marshall
>
> On 1/23/06, Thomas Morin <thomas.morin@rd.francetelecom.com> wrote:
> >  Pekka, Yakov, folks,
> >
> >
> >  Yakov Rekhter:
> >
> > > > 5.1.11. RP Engineering
> > > >
> > > > When PIM-SM (or bidir-PIM) is used in ASM mode on the VPN customer
> > > > side, the location of the RP has to be chosen. In some cases this
> > > > engineering problem is not trivial: for instance, if sources and
> > > > receivers are located in VPN sites that are different than that of
> > > > the RP, then traffic may flow twice through the SP network and the
> > > > CE-PE link of the RP (from source to RP, and then from RP to
> > > > receivers) ; this is obviously not ideal. A multicast VPN solution
> > > > SHOULD propose a way to help on solving this RP engineering issue.
> > > >
> > > > =3D=3D> I'm not sure if this specific problem exists in practice. I=
f the
> > > > RP sends Register-Stop, the multicast traffic is forwarded natively=
,
> > > > and the data will short-cut inside the site without going to the RP
> > > > and then back. I.e., there should not be two times traffic once the
> > > > forwarding is native.
> > >
> > > Well...
> > > 1) even such transient peaks may not be something that you'll want
> > > 2) what if you lose connectivity to the remote site hosting the RP, a=
re
> > > you happy to lose local multicast on every other site?
> > > 3) what if you want to stick with RPT ?
> > > [okay, maybe not so relevant, but what if the VPN customer wants to
> > > do this ?]
> >
> > Wrt your second point I think it would be highly desirable for a
> > solution to maintain multicast service among all the sites within
> > an MVPN that maintain connectivity among themselves, even when the
> > site(s) hosting the RP lose their connectivity.
> >
> > Likewise, it would be highly desirable for a site that loses
> > connectivity to the service provider to maintain multicast service
> > within that site.
> >
> > I would suggest to include both of the above points in the requirements
> > document.
> >
> >
> >  I do agree that the unavailability of the RP may be a stronger reason =
that
> > transient bandwidth peaks happening when forwarding switches from
> > PIM-register-encapsulated to native.
> >
> >  However, the initial reason for this section 5.1.11 is that:
> >  a) it seems that some VPN clients would be happy to _not_ have to both=
er
> > with running RP(s)
> >  b) it seems that some providers may happily host the RP function
> >  So I don't want focus to get lost...
> >
> >  Below is my suggestion for a reshaped section 5.1.11.
> >  It aims at distinguishing between the three different problems that we=
 may
> > have: RP outsourcing, RP availability, RP location.
> >
> >  Feel free to comment.
> >
> >  Cheers,
> >
> >  -Thomas
> >
> >  ----------------------------
> >
> >  5.1.11. RP Engineering
> >  When PIM-SM (or bidir-PIM) is used in ASM mode on the VPN customer sid=
e,
> > the RP function (or RP-address in the case of bidir-PIM) has to be
> > associated to a node running PIM, and configured on this node.
> >
> >
> >  ________________________________
> >
> >
> >
> >  5.1.11.1. RP Outsourcing In the case of PIM-SM in ASM mode, engineerin=
g of
> > the RP function requires the deployment of specific protocols and assoc=
iated
> > configurations. Some service provider may offer to manage customer's
> > multicast protocol operation on behalf of them. This implies that it is
>
> s/on behalf of them/on their behalf/
>
> > necessary to consider cases where the customer's RPs are outsourced (e.=
g.,
> > on PEs). Consequently, a VPN solution MAY support the hosting of the RP
> > function in a VR or VRF.
> >
> >
> >  ________________________________
> >
> >
> >
> >  5.1.11.2. RP Availability Availability of the RP function (or address)=
 is
> > required for proper operation of PIM-SM (ASM mode) and bidir-PIM. Loss =
of
> > connectivity to the RP from a receiver or source will impact the multic=
ast
> > service. For this reason different mecanisms exist, such as BSR(Bhaskar=
, N.,
> > "Bootstrap Router (BSR) Mechanism for PIM," October 2005.)
> > [I-D.ietf-pim-sm-bsr] or anycast-RP (MSDP based(Kim, D., Kilmer, H., an=
d D.
> > Farinacci, "Anycast RP mechanism using PIM and MSDP," May 2001.)
> > [I-D.ietf-mboned-anycast-rp] or PIM based(Farinacci, D. and Y. Cai,
> > "Anycast-RP using PIM," August 2005.) [I-D.ietf-pim-anycast-rp]).
> >
> >  These protocols and procedures SHOULD work transparently through a
> > multicast VPN, and MAY, if relevant, be implemented in a VRF/VR.
> >
> >  Moreover, a multicast VPN solution MAY improve the robustness of the A=
SM
> > multicast service regarding loss of connnectivity to the RP, by providi=
ng
> > specific features that help :
> >
> >  a) maintaining ASM multicast service among all the sites within an MVP=
N
>
> s/maintaining/maintain/
>
> > that maintain connectivity among themselves, even when the site(s) host=
ing
> > the RP lose their connectivity to the MVPN
>
> Is this an "and" or an "or" here ? I would say and.
>
> >  b) maintaining ASM multicast service within any site that loses
> > connectivity to the service provider
> >
> >  ________________________________
> >
> >
> >
> >
> >  5.1.11.3. RP Location
> >  In the case of PIM-SM, when a source starts to emit traffic toward a g=
roup
> > (in ASM mode), if sources and receivers are located in VPN sites that a=
re
> > different than that of the RP, then traffic may transiently flow twice
> > through the SP network and the CE-PE link of the RP (from source to RP,=
 and
> > then from RP to receivers). This traffic peak, even short, may no be
>
> s/no/not/
>
> > convenient depending on the traffic and link bandwidth.
> >
> >  Thus, a VPN solution MAY provide features that solve or help mitigate =
this
> > potential issue.
> >
> >
>




From l3vpn-bounces@ietf.org Tue Jan 24 02:44:16 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1F1Iqe-0006Cf-UA; Tue, 24 Jan 2006 02:44:16 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1F1Iqb-0006CI-OK
	for l3vpn@megatron.ietf.org; Tue, 24 Jan 2006 02:44:13 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA16173
	for <l3vpn@ietf.org>; Tue, 24 Jan 2006 02:42:42 -0500 (EST)
Received: from p-mail1.rd.francetelecom.com ([195.101.245.15])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1F1J06-0006Dg-3B
	for l3vpn@ietf.org; Tue, 24 Jan 2006 02:54:03 -0500
Received: from ftrdmel10.rd.francetelecom.fr ([10.193.117.156]) by
	ftrdsmtp1.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.211); 
	Tue, 24 Jan 2006 08:44:06 +0100
Received: from l-at8613.rd.francetelecom.fr ([10.193.15.65]) by
	ftrdmel10.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.211); 
	Tue, 24 Jan 2006 08:44:06 +0100
From: Thomas Morin <thomas.morin@rd.francetelecom.com>
To: Marshall Eubanks <marshall.eubanks@gmail.com>
In-Reply-To: <dcad22d80601232041pd6e848du1dfe2c2961813fd6@mail.gmail.com>
References: <200601181454.k0IEsw508342@merlot.juniper.net>
	<1138035421.14305.4.camel@wintermute>
	<dcad22d80601232041pd6e848du1dfe2c2961813fd6@mail.gmail.com>
Content-Type: text/plain
Organization: France Telecom R&D
Date: Tue, 24 Jan 2006 08:44:05 +0100
Message-Id: <1138088645.5279.8.camel@wintermute>
Mime-Version: 1.0
X-Mailer: Evolution 2.4.2.1 
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 24 Jan 2006 07:44:06.0658 (UTC)
	FILETIME=[F4504E20:01C620B9]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a7d6aff76b15f3f56fcb94490e1052e4
Content-Transfer-Encoding: 7bit
Cc: Yakov Rekhter <yakov@juniper.net>, l3vpn@ietf.org,
	Pekka Savola <pekkas@netcore.fi>
Subject: Re: comments on draft-ietf-l3vpn-ppvpn-mcast-reqts-03
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: l3vpn.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:l3vpn@ietf.org>
List-Help: <mailto:l3vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=subscribe>
Sender: l3vpn-bounces@ietf.org
Errors-To: l3vpn-bounces@ietf.org

Marshall,

Marshall Eubanks:
> >  5.1.11.1. RP Outsourcing In the case of PIM-SM in ASM mode, engineering of
> > the RP function requires the deployment of specific protocols and associated
> > configurations. Some service provider may offer to manage customer's
> > multicast protocol operation on behalf of them. This implies that it is
> 
> s/on behalf of them/on their behalf/

Ack.

> >  a) maintaining ASM multicast service among all the sites within an MVPN
> 
> s/maintaining/maintain/

Ack.


> > that maintain connectivity among themselves, even when the site(s) hosting
> > the RP lose their connectivity to the MVPN
> 
> Is this an "and" or an "or" here ? I would say and.

I'm not sure we should make the wording heavier: this is "only" a MAY,
and someone may implement one and not the other, that'd be acceptable. 

> >  5.1.11.3. RP Location
> >  In the case of PIM-SM, when a source starts to emit traffic toward a group
> > (in ASM mode), if sources and receivers are located in VPN sites that are
> > different than that of the RP, then traffic may transiently flow twice
> > through the SP network and the CE-PE link of the RP (from source to RP, and
> > then from RP to receivers). This traffic peak, even short, may no be
> 
> s/no/not/

Ack.

Thanks for your comments,

-Thomas





From l3vpn-bounces@ietf.org Tue Jan 24 07:53:26 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1F1Nfq-0002zk-KF; Tue, 24 Jan 2006 07:53:26 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1F1IvK-0007AC-Bq
	for l3vpn@megatron.ietf.org; Tue, 24 Jan 2006 02:49:06 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA16435
	for <l3vpn@ietf.org>; Tue, 24 Jan 2006 02:47:35 -0500 (EST)
Received: from netcore.fi ([193.94.160.1])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1F1J4o-0006Mj-QQ
	for l3vpn@ietf.org; Tue, 24 Jan 2006 02:58:56 -0500
Received: from netcore.fi (localhost [127.0.0.1])
	by netcore.fi (8.12.8/8.12.8) with ESMTP id k0O7msHa008542;
	Tue, 24 Jan 2006 09:48:54 +0200
Received: from localhost (pekkas@localhost)
	by netcore.fi (8.12.8/8.12.8/Submit) with ESMTP id k0O7msK4008539;
	Tue, 24 Jan 2006 09:48:54 +0200
Date: Tue, 24 Jan 2006 09:48:54 +0200 (EET)
From: Pekka Savola <pekkas@netcore.fi>
To: Thomas Morin <thomas.morin@rd.francetelecom.com>
In-Reply-To: <1138035421.14305.4.camel@wintermute>
Message-ID: <Pine.LNX.4.64.0601240947320.8446@netcore.fi>
References: <200601181454.k0IEsw508342@merlot.juniper.net>
	<1138035421.14305.4.camel@wintermute>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-Virus-Scanned: ClamAV version 0.88,
	clamav-milter version 0.87 on otso.netcore.fi
X-Virus-Status: Clean
X-Spam-Status: No, score=-3.1 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 
	autolearn=ham version=3.1.0
X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on otso.netcore.fi
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25
X-Mailman-Approved-At: Tue, 24 Jan 2006 07:53:25 -0500
Cc: Yakov Rekhter <yakov@juniper.net>, l3vpn@ietf.org
Subject: Re: comments on draft-ietf-l3vpn-ppvpn-mcast-reqts-03
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: l3vpn.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:l3vpn@ietf.org>
List-Help: <mailto:l3vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=subscribe>
Sender: l3vpn-bounces@ietf.org
Errors-To: l3vpn-bounces@ietf.org

On Mon, 23 Jan 2006, Thomas Morin wrote:
> Below is my suggestion for a reshaped section 5.1.11.
> It aims at distinguishing between the three different problems that we
> may have: RP outsourcing, RP availability, RP location.
>
> Feel free to comment.
...

I think the general thrust of the new section is good; it properly 
separates the different issues wrt RP engineering, so I'm fine with 
it.

-- 
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 l3vpn-bounces@ietf.org Tue Jan 24 20:09:14 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1F1Z9u-0006v3-Hz; Tue, 24 Jan 2006 20:09:14 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1F1Z9t-0006us-72
	for l3vpn@megatron.ietf.org; Tue, 24 Jan 2006 20:09:13 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA23539
	for <l3vpn@ietf.org>; Tue, 24 Jan 2006 20:07:42 -0500 (EST)
Received: from zproxy.gmail.com ([64.233.162.192])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1F1ZJU-0001Rx-RN
	for l3vpn@ietf.org; Tue, 24 Jan 2006 20:19:12 -0500
Received: by zproxy.gmail.com with SMTP id 9so1321664nzo
	for <l3vpn@ietf.org>; Tue, 24 Jan 2006 17:09:04 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
	h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=rl4OxpEdzFej0F4LccQuQnDC3exJjW/bdIjwcO2csJKYCtG6HVrJoDRe/KiWGyS6krYdcWpiOTHQu1jDvpb6O6qo8TRFFy9WWQpVBzBpRVURQij08Iincdgdp+5REutJRdGPHo9JwasJ38Rac7e9PU1lDLK3HJyeE++NfUx8Dxk=
Received: by 10.37.13.24 with SMTP id q24mr100180nzi;
	Tue, 24 Jan 2006 17:09:04 -0800 (PST)
Received: by 10.36.41.20 with HTTP; Tue, 24 Jan 2006 17:09:04 -0800 (PST)
Message-ID: <dcad22d80601241709u66e3b41eubd180c37ee8feb1a@mail.gmail.com>
Date: Tue, 24 Jan 2006 20:09:04 -0500
From: Marshall Eubanks <marshall.eubanks@gmail.com>
To: Pekka Savola <pekkas@netcore.fi>
In-Reply-To: <Pine.LNX.4.64.0601240947320.8446@netcore.fi>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <200601181454.k0IEsw508342@merlot.juniper.net>
	<1138035421.14305.4.camel@wintermute>
	<Pine.LNX.4.64.0601240947320.8446@netcore.fi>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
Content-Transfer-Encoding: quoted-printable
Cc: Yakov Rekhter <yakov@juniper.net>,
	Thomas Morin <thomas.morin@rd.francetelecom.com>, l3vpn@ietf.org
Subject: Re: comments on draft-ietf-l3vpn-ppvpn-mcast-reqts-03
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: l3vpn.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:l3vpn@ietf.org>
List-Help: <mailto:l3vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=subscribe>
Sender: l3vpn-bounces@ietf.org
Errors-To: l3vpn-bounces@ietf.org

In case anyone missed it with the nit discussion flying around, I agree.

Marshall

On 1/24/06, Pekka Savola <pekkas@netcore.fi> wrote:
> On Mon, 23 Jan 2006, Thomas Morin wrote:
> > Below is my suggestion for a reshaped section 5.1.11.
> > It aims at distinguishing between the three different problems that we
> > may have: RP outsourcing, RP availability, RP location.
> >
> > Feel free to comment.
> ...
>
> I think the general thrust of the new section is good; it properly
> separates the different issues wrt RP engineering, so I'm fine with
> it.
>
> --
> 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 l3vpn-bounces@ietf.org Tue Jan 31 10:25:55 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1F3xOF-00042y-JR; Tue, 31 Jan 2006 10:25:55 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1F3xOD-0003xL-De
	for l3vpn@megatron.ietf.org; Tue, 31 Jan 2006 10:25:53 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA26474
	for <l3vpn@ietf.org>; Tue, 31 Jan 2006 10:24:08 -0500 (EST)
Received: from borg.juniper.net ([207.17.137.119])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1F3xZ3-0007NX-RC
	for l3vpn@ietf.org; Tue, 31 Jan 2006 10:37:07 -0500
Received: from unknown (HELO proton.jnpr.net) ([10.10.2.37])
	by borg.juniper.net with ESMTP; 31 Jan 2006 07:25:29 -0800
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
X-IronPort-AV: i="4.01,239,1136188800"; 
	d="scan'208"; a="526593134:sNHT20931896"
Received: from [172.23.1.142] ([172.23.1.142] RDNS failed) by proton.jnpr.net
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 31 Jan 2006 10:25:33 -0500
Message-ID: <43DF8169.6030703@juniper.net>
Date: Tue, 31 Jan 2006 10:25:29 -0500
From: Ron Bonica <rbonica@juniper.net>
User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: l3vpn@ietf.org
X-Enigmail-Version: 0.93.0.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 31 Jan 2006 15:25:34.0049 (UTC)
	FILETIME=[942D2510:01C6267A]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 68c8cc8a64a9d0402e43b8eee9fc4199
Content-Transfer-Encoding: 7bit
Subject: IETF 65
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: l3vpn.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:l3vpn@ietf.org>
List-Help: <mailto:l3vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>,
	<mailto:l3vpn-request@ietf.org?subject=subscribe>
Sender: l3vpn-bounces@ietf.org
Errors-To: l3vpn-bounces@ietf.org

Folks,

So far, the following individuals have asked to present at IETF 65:

- Eric Rosen and Rahul Aggrawal
- Thomas Morin
- Yiqun Cai

Are there any others? If so, please speak up now before we are allocated
a time slot.

                               Ron




