From l3vpn-bounces@ietf.org Mon Dec 03 17:13:17 2007
Return-path: <l3vpn-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IzJWz-0000Y8-G6; Mon, 03 Dec 2007 17:12:49 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IzJWy-0000Tt-Fg
	for l3vpn@ietf.org; Mon, 03 Dec 2007 17:12:48 -0500
Received: from exprod7og110.obsmtp.com ([64.18.2.173])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IzJWy-0001FB-2v
	for l3vpn@ietf.org; Mon, 03 Dec 2007 17:12:48 -0500
Received: from source ([66.129.224.36]) by exprod7ob110.postini.com
	([64.18.6.12]) with SMTP; Mon, 03 Dec 2007 14:12:09 PST
Received: from proton.jnpr.net ([10.10.2.37]) by emailsmtp56.jnpr.net with
	Microsoft SMTPSVC(6.0.3790.3959); Mon, 3 Dec 2007 14:12:40 -0800
Received: from [172.23.1.17] ([172.23.1.17] RDNS failed) by proton.jnpr.net
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 3 Dec 2007 17:12:38 -0500
Message-ID: <47547F53.2000306@juniper.net>
Date: Mon, 03 Dec 2007 17:12:35 -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: 03 Dec 2007 22:12:39.0207 (UTC)
	FILETIME=[9DE2BB70:01C835F9]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8ac499381112328dd60aea5b1ff596ea
Subject: Note-taker and Jabber-Scribe
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>
Errors-To: l3vpn-bounces@ietf.org

Folks,

If you are willing to serve as note-taker or jabber-scribe at IETF 70,
please email me privately.

                              Ron




From l3vpn-bounces@ietf.org Mon Dec 10 16:21:58 2007
Return-path: <l3vpn-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1J1q4R-000084-9W; Mon, 10 Dec 2007 16:21:47 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1J1q4Q-00007z-HZ
	for l3vpn@ietf.org; Mon, 10 Dec 2007 16:21:46 -0500
Received: from exprod7og104.obsmtp.com ([64.18.2.161])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1J1q4Q-0008S7-3g
	for l3vpn@ietf.org; Mon, 10 Dec 2007 16:21:46 -0500
Received: from source ([66.129.224.36]) by exprod7ob104.postini.com
	([64.18.6.12]) with SMTP; Mon, 10 Dec 2007 13:21:45 PST
Received: from proton.jnpr.net ([10.10.2.37]) by emailsmtp55.jnpr.net with
	Microsoft SMTPSVC(6.0.3790.1830); Mon, 10 Dec 2007 13:11:33 -0800
Received: from [172.23.1.197] ([172.23.1.197] RDNS failed) by proton.jnpr.net
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 10 Dec 2007 16:11:31 -0500
Message-ID: <475DAB80.7010900@juniper.net>
Date: Mon, 10 Dec 2007 16:11:28 -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: 10 Dec 2007 21:11:32.0120 (UTC)
	FILETIME=[3D05E980:01C83B71]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8ac499381112328dd60aea5b1ff596ea
Subject: draft-morin-l3vpn-mvpn-considerations
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>
Errors-To: l3vpn-bounces@ietf.org

Folks,

Unless I hear an objection before COB Friday, this document will become
a WG draft.

                                      Ron




From l3vpn-bounces@ietf.org Wed Dec 12 09:34:08 2007
Return-path: <l3vpn-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1J2Sez-00041N-97; Wed, 12 Dec 2007 09:34:05 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1J2Sex-00041C-Nh
	for l3vpn@ietf.org; Wed, 12 Dec 2007 09:34:03 -0500
Received: from rtp-iport-2.cisco.com ([64.102.122.149])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1J2Sev-0005md-T3
	for l3vpn@ietf.org; Wed, 12 Dec 2007 09:34:03 -0500
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by rtp-iport-2.cisco.com with ESMTP; 12 Dec 2007 09:34:01 -0500
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12])
	by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id lBCEY11D019465; 
	Wed, 12 Dec 2007 09:34:01 -0500
Received: from erosen-linux.cisco.com (erosen-linux.cisco.com [161.44.70.34])
	by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id
	lBCEY1a8006003; Wed, 12 Dec 2007 14:34:01 GMT
Received: from erosen-linux (localhost.localdomain [127.0.0.1])
	by erosen-linux.cisco.com (8.13.1/8.13.1) with ESMTP id lBCEY1IT017618; 
	Wed, 12 Dec 2007 09:34:01 -0500
To: l3vpn@ietf.org
Date: Wed, 12 Dec 2007 09:34:01 -0500
Message-ID: <17617.1197470041@erosen-linux>
From: Eric Rosen <erosen@cisco.com>
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=18971; t=1197470041;
	x=1198334041; c=relaxed/simple; s=rtpdkim1001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=erosen@cisco.com;
	z=From:=20Eric=20Rosen=20<erosen@cisco.com>
	|Subject:=20Comments=20on=20draft-morin-l3vpn-mvpn-consider
	ations-01.txt |Sender:=20 |To:=20l3vpn@ietf.org;
	bh=O4CX/qxC3Xwh1eGwGwWnYIeg48ugpwQQTIJuQuNs2fg=;
	b=abxodd5pnXNDUQWYCewc84rZ7iq3n++EjqHNc8M6vH3yoaI8I1H84fHExw
	6aPbk/iBxfdRgL7gwYO9WJ7FejUUhKiiqdyAeF5hrWD24PboVjvhTqZgQjk4
	tF51r/fD5P;
Authentication-Results: rtp-dkim-1; header.From=erosen@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim1001 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e95407604bef3289cd27cb4f3b3a35b4
Subject: Comments on draft-morin-l3vpn-mvpn-considerations-01.txt
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: erosen@cisco.com
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>
Errors-To: l3vpn-bounces@ietf.org

I have carefully  reread draft-morin-l3vpn-mvpn-considerations-01.txt, and I
have a number of comments.

In  general, I  think the  authors have  done  a good  job in  trying to  be
even-handed, but  I think there are some  errors in the details,  and I also
think that some of  the risks and overheads involved in the  use of BGP have
not been fully considered.  I also don't think that the different flavors of
MPLS multicast  LSPs have  been carefully considered.   I would like  to see
some of these issues addressed before adopting it as a WG draft.

On the general issue of comparing PIM vs. BGP, while the draft does not make
a recommendation, it  is heavy on PIM's disadvantages  and BGP's advantages.
So I  think it is  worth listing some  of the risk areas  of BGP.  I  do not
believe that  any of  these are "showstoppers"  for BGP, but  they certainly
should  be articulated  in  any document  that  purports to  be providing  a
balanced view. 

- As BGP  is generally  used, BGP churn  is a  function of real  or apparent
  topology changes.  BGP churn is NOT generally caused by enduser events.

  This changes when  BGP is used to distribute  multicast routes.  BGP churn
  can now  be initiated by PIM  Joins, and a PIM  Join may be  the result of
  some enduser clicking  a button on his PC (e.g.,  "receive video").  it is
  not clear that there is any limit on the rate at which such enduser events
  can occur.  We do not appear to  have adequate data from which we can draw
  conclusions as to the impact of enduser actions on BGP churn.

  It is easy to offer opinions about this, but facts are scarce.

- In some  multicast applications, "join  latency" is considered to  be very
  important.  No  one has ever claimed  BGP will provide  lower join latency
  than  PIM, the only  real question  is whether  latency will  be increased
  beyond  the  limits  that   some  applications  find  acceptable.   Again,
  different people have  different opinions about how much  this will matter
  in practice, but hard data is hard to come by.

- Churn  vs. latency:  To  control the  BGP  churn, we  have discussed  such
  features as  Join Dampening.   However, that can't  be expected to  have a
  salutary effect on the latency!

  There really should  be some recognition in the draft  that the effects on
  latency and churn are as yet poorly understood.

- Any time a new high volume address family is added to BGP. it is important
  to consider  the impact on  the route reflectors,  and whether it  will be
  necessary to add  new route reflectors, perhaps ones  dedicated to the new
  family.  One should also consider the impact (especially on the RRs) which
  one address family  may have on another, e.g.,  will an unexpectedly large
  amount  of churn  due  to PIM  cause  a slowdown  in  the unicast  routing
  convergence.  There should be some discussion of this.

- Transactional nature of PIM

  At first glance,  it may seem that having  PIM distribute multicast routes
  to BGP is no different than  having OSPF distribute unicast routes to BGP,
  i.e., that it is really  nothing new.  However, this isn't quite accurate.
  The issue  is that PIM isn't really  a "routing protocol" in  the sense of
  choosing  routes  based   on  topology.   It  is  a   protocol  that  uses
  router-to-router  transactions  to construct  paths  and  assign flows  to
  paths. In  some cases, especially when  Sparse Mode flows  are involved, a
  number of  transactions involving  multiple nodes may  need to  take place
  before the multicast "routing" stabilizes.  Each one of these transactions
  must  pass through  the RR,  placing more  load on  the RR  and increasing
  latency.

  In  some  cases, where  PIM-SM  has  data-driven  state changes,  we  have
  attempted  to avoid  putting the  data-driven state  changes into  BGP, by
  having BGP send extra  messages, including timer-driven messages.  While I
  tend to think that this is the right tradeoff, it does modify the dynamics
  of path construction,  and we don't have any hard data  to tell us whether
  we've made the right tradeoff,  or whether the "right tradeoff" depends on
  just how the applications are using multicast.
  
- Strange uses of PIM

  Talk  to  anyone  with a  lot  of  experience  in  PIM deployment  in  the
  enterprise, and you'll hear lots of  strange stories about how PIM is used
  in some enterprises.   Although PIM is optimized for  "many receivers, few
  sources", it isn't always used  that way.  I've also heard anecdotes about
  applications that make assumptions about the dynamic nature of PIM and may
  break if  anything changes.   As usual,  hard data is  hard to  find.  But
  there's always a risk that when you change the infrastructure underneath a
  crufty old application you will break the application.  There are people I
  respect, with  much more experience  in multicast deployment than  I have,
  who think it's  just foolish to do anything that changes  the way in which
  the infrastructure behaves for sparse mode.  While I am not convinced that
  they are  right, I think that  this does have  to be recognized as  a risk
  element.

Now let's look at some of the topics covered in the draft.

1. From section 3.1, "the operational burden of setting up multicast on a PE
   or for a VR/VRF SHOULD be as low as possible".

   I certainly  agree with  this!  However, I  don't think it  combines well
   with the  later recommendation to support outsourced  RPs.  Obviously the
   use of outsourced RPs increases the operational burden for the provider.

   I  note that  there doesn't  seem to  be any  requirement for  making the
   operational burden  of MVPN on the  SP's customer be as  low as possible,
   though such a requirement is  prominent in another SP requirements draft,
   viz.,  draft-mnapierala-mvpn-part-reqt-00.txt.  Such a  requirement would
   see to  militate against  the use  of the "outsourced  RP", at  least for
   MVPN customers who already use  multicast.  (Which I imagine would be the
   vast majority of them.)

2. Auto-discovery

   "BGP-based  auto-discovery is the  preferred solution  for auto-discovery
   ...  while  PIM/shared-tree  based  auto-discovery should  be  optionally
   considered for migration purposes only".

   There isn't  really a  dichotomy here.  The  facts are that  if PIM-based
   shared  trees  are  used,  BGP-based auto-discovery  doesn't  really  add
   anything,  but in  any  other circumstance,  BGP-based auto-discovery  is
   absolutely necessary.

   But  if the recommendation  here is  to provide  BGP-based auto-discovery
   even in the one case where  it isn't strictly needed, I certainly support
   that recommendation.  This  is, in fact, already true  of the majority of
   existing MVPN  deployments.  (Though  I have been  told that there  is at
   lest one vendor which does not support it in existing deployments.)

   There is a suggestion in the  draft that if PIM-based shared trees are in
   use, BGP auto-discovery can  help detect misconfigurations.  I'm not sure
   about that, as I can imagine  transition scenarios in which more than one
   shared tree is in use at some time.

3. Number of protocols

   "if any additional protocols are introduced compared with the unicast VPN
   service,  the  balance between  their  advantage  and operational  burden
   SHOULD be examined thoroughly"

   Well, who  could disagree with that?   The pros/cons of  any new protocol
   should always be  examined thoroughly.  In fact, the  pros/cons of adding
   new  functionality  to  existing  protocols  should  always  be  examined
   thoroughly  as well.   As  should  the pros/cons  of  adding new  address
   families, new procedures,  new dynamics, new events and  states, etc., to
   existing protocols.

   It is better to focus on the overall complexity of the system, and on the
   overall  behavior  of  the system,  than  just  to  count the  number  of
   protocols. 

4. S-PMSI Signaling

   The BGP-based S-PMSI  signaling mechanism does have a  risk factor that I
   have mentioned above, but that is not considered in the draft

   In current practice,  BGP changes are caused by  topology changes, not by
   end  user  activity.   However,   it  is  enduser  activity  that  causes
   invocation of the S-PMSI signaling  mechanism.  We simply do not have the
   data at  the present time  to determine how  much this will  increase the
   amount of churn  in BGP.  The S-PMSI signaling is  also something that is
   best done through a low latency  mechanism, and we do not at present have
   the data to determine whether BGP will significantly increase the latency
   when compared with the UDP-based proposal.

   In theory,  the use of BGP  S-PMSI signaling has a  number of advantages,
   but I  don't think  I would  recommend against the  use of  the UDP-based
   procedure unless and until I had some data about these pragmatic issues.

   By the  way, when I  say "data", I  don't mean "strongly held  and loudly
   voiced  opinions", even  though the  latter are  sometimes  confused with
   data.

   "The  UDP-based protocol  is  restricted  to use  within  MVPNs using  an
   MI-PMSI".

   This fact seems to me to be  neither here nor there.  It is true that the
   UDP-based protocol is unlikely to be useful unless PIM is the C-multicast
   routing control protocol, in which case  you have an MI-PMSI.  If you are
   using  BGP as  the C-multicast  routing protocol,  then you  have already
   determined that you don't care if BGP churn is caused by enduser events.

   The UDP-based S-PMSIs signaling is best considered as an optional part of
   the  PIM C-multicast  routing control  plane, rather  than as  a separate
   protocol with its own independent set of pros and cons.

   "the  use  of  the  UDP-based  protocol  does  not  preserve  AS  routing
    independence  when  used in  an  inter-AS  option  B context  (i.e.  the
    decision by  a PE in an  AS to use an  S-PMSI for a  given customer flow
    will impact routing state in other ASes)

   I  have no  idea what  this means,  so I  hope one  of the  authors will
   explain.   (I also  don't  know what  is  meant by  the  claim that  the
   BGP-based S-PMSI signaling  mechanism doesn't have whatever disadvantage
   this is.)

5. Off-loading processing onto route reflector

   The claim is made that, when using BGP to carry C-multicast routes, "some
   of  the processing burden  associated with  client multicast  routing [is
   offloaded] onto BGP route reflectors"

   I  would  like the  authors  to  specify  precisely what  this  offloaded
   processing burden is.  Some consideration of its effect on existing L3VPN
   route reflector systems would also be worthwhile.

   As the  text is now, it is  very difficult to understand  or evaluate the
   claim.

6. MI-PMSI issues

   "Moreover, mechanisms one and two are restricted to use within MVPNs
   using an MI-PMSI, thereby necessitating:

   a.  The use of a P-multicast tree technique that allows shared trees
       (for example PIM-SM in ASM mode or MP2MP LDP).

   b.  The use of one P-multicast tree per PE per VPN, even for PEs that
       do not have sources in their directly attached sites for that
       VPN."

   First,  claim b  is  not true,  as  explained in  draft-rosen-l3vpn-mvpn-
   profiles-00.txt, section 3.3.

   Second, the fact that a control  protocol requires that it be possible to
   instantiate a P-tunnel as a shared tree  of some sort does not seem to be
   to be  a "restriction" or disadvantage.   You might as well  say that the
   use  of  BGP  for  C-multicast  routing has  the  disadvantage  of  being
   "restricted"  to those networks  whose route  reflectors support  the BGP
   C-multicast routing address family.

   There are however some other things  that do seem to require the presence
   of an MI-PMSI:   autoRP and BSR.  Since many  SP customers use autoRP/BSR
   to discover  RPs, and since  it is not  clear how to provide  support for
   these without an  MI-PMSI, I am not convinced that one  can do without an
   MI-PMSI even if BGP is used for distributing C-multicast routes.


7. BGP doesn't eliminate PIM anyway
   
   "using BGP for customer routing distribution within multicast VPNs avoids
   the introduction of an  additional protocol that would require additional
   OAM processes and tools."

   It's not as if  PIM is eliminated by BGP.  As long as  PIM is used on the
   PE/CE links, the SP is still operating a PIM environment.  In fact, there
   may be significant  scaling problems due to PE-CE  PIM.  Some people with
   years of PIM  experience believe that the PE-CE  PIM scaling problems are
   actually worse  than the PE-PE PIM  scaling problems, and  hence that the
   attempt  to improve PE-PE  scaling by  using BGP  just attacks  the wrong
   problem. 

   In the absence of  actual data, the risk is that you  end up adding a lot
   of NEW stuff and don't even address the scaling bottlenecks.
 
   In  any  event, I'm  not  sure  I understand  how  adding  a  lot of  new
   functionality  to BGP  (multicast  path  creation) is  going  to be  done
   without the need for additional OAM processes and tools.

8. Consistency with unicast control mechanisms.

   "An illustrative example of the benefit brought by consistency with
   unicast design is how the "extranet" feature can be implemented :
   when BGP-based mechanisms are used, the well defined and well
   understood BGP route target import/export semantics are just reused."

   This seems like a red  herring.  Extranet capability is already supported
   in  the field  today  by existing  MVPN  deployments based  on PIM.   The
   primary impact is really on the auto-discovery phase, not the C-multicast
   routing phase.

9. Encapsulation techniques

    I notice that  there is one particular data plane  technique that is not
    addressed  by the  document, viz.,  the use  of ingress  replication and
    transmission through  unicast tunnels.  It would be  interesting to know
    whether SPs  have interest in this  technology; if not, maybe  it can be
    removed from the  drafts.  (I think it adds  complexity and frankly, I'm
    not sure it's fully and properly specified.)

    I think section 3.4 can be taken as a requirement for both a "BGP + GRE"
    profile  and a  "PIM +  MPLS" profile,  since it  seems to  advocate for
    independence between the the control  plane and the data plane.  But I'm
    not sure if that is what is intended, and would like clarification.

    I would like  to see a specific recommendation for  the support of MP2MP
    LSPs,  given their  importance in  C-bidir support  (for  either control
    plane, see draft-ietf-l3vpn-2547bis-  mcast-05.txt, section 12.2) and in
    general MPLS  multicast support  for the PIM  control plane  (see draft-
    rosen-l3vpn-mvpn-profiles-00.txt, section 3.3).

10. Upstream-Assigned Labels, MI-PMSI, and Scalability
   
    The  WG drafts frequently  discuss aggregation,  and the  possibility of
    aggregation is frequently touted as a major scalability advantage.

    What isn't always clear is  that all forms of S-PMSI aggregation require
    a  major   new  MPLS  feature,   upstream-assigned  labels.   Supporting
    upstream-assigned labels requires significant  changes to the data plane
    processing  of  many  different  platforms,  and is  not  likely  to  be
    available for some period of time.

    So realistically, for  the foreseeable future, the use  of an MI-PMSI is
    going  to remain  the  only  method of  aggregation.   Unless a  service
    provider does not care if their  P-routers have to maintain an amount of
    multicast state  which is proportional to  the sum of the  states of all
    their customers, the service provider should be requiring support for an
    MI-PMSI. 

    As  a further  note,  it should  be  pointed out  that inter-AS  segment
    S-PMSIs are on a per-PE basis, not a per-AS basis.  Therefore without the
    aggregation that  can be obtained  from upstream-assigned labels,  it is
    not clear that segmented inter-AS  S-PMSIs are scalable at all.  This is
    an issue which should be mentioned.

    I think the draft should have a clear recommendation that in the absence
    of upstream-assigned MPLS labels, MI-PMSIs should be used.

11. Outsourced RPs

    I  would like  to see  the  draft offer  much stronger  support for  its
    recommendation to  implement outsourced RPs,  or else to  eliminate that
    recommendation. 

    Outsourced RPs  (i.e., PE  as RP) have  a number of  disadvantages which
    need to be given more emphasis:

    - More work  for the PE (do  many SPs really want  to give a  lot of new
      work to their PEs)?

    - Not  likely to  be  of much  interest  to customers  with an  existing
      multicast infrastructure

    - Require  increased coordination  between SP  and  enterprise customer,
      such as agreement on RP (or RPL) addresses.
    
    - Not completely clear  how this works in scenarios  where an enterprise
      gets VPN  service from two different providers,  particularly if there
      is a site multihomed to two different providers.

    I presume  that the extra  operational work for  SP and customer  is not
    going to be justified by the  fact that it simplifies things for some of
    the SP's vendors.


12. The draft's conclusion

   "Consequently, at the present time and until there is experience with
   all of the proposed mechanisms it is not clear which of the above
   mechanisms should be recommended as the preferred solution to
   implementers.  However, it would appear prudent for implementations
   to consider supporting both the fourth (BGP-based) and first (full
   per-MPVN PIM peering) mechanisms.  Further experience on both
   implementation is likely to be required before some best practice can
   be defined."

   I certainly agree with this  conclusion.  Perhaps it should be given more
   prominence. 

13. My conclusion

    While  I do  think this  draft may  be a  good start  on the  project of
    comparing the  different MVPN options, I  don't think it is  ready to be
    adopted as a WG document, and it  needs a lot more work to deal with the
    issues I have raised in this note.

    I  also hope  it  is clearly  understood  that this  document should  be
    evaluated by the same criteria as any other internet-draft, i.e., by its
    technical quality.

    


    

 





From l3vpn-bounces@ietf.org Thu Dec 13 17:27:38 2007
Return-path: <l3vpn-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1J2wWi-00005U-SR; Thu, 13 Dec 2007 17:27:32 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1J2wWi-00005N-Bu
	for l3vpn@ietf.org; Thu, 13 Dec 2007 17:27:32 -0500
Received: from slb-smtpout-01.boeing.com ([130.76.64.48])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1J2wWi-0004Np-28
	for l3vpn@ietf.org; Thu, 13 Dec 2007 17:27:32 -0500
Received: from blv-av-01.boeing.com (blv-av-01.boeing.com [192.42.227.216])
	by slb-smtpout-01.ns.cs.boeing.com (8.14.0/8.14.0/8.14.0/SMTPOUT) with
	ESMTP id lBDMRQbX001691
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK);
	Thu, 13 Dec 2007 14:27:27 -0800 (PST)
Received: from blv-av-01.boeing.com (localhost [127.0.0.1])
	by blv-av-01.boeing.com (8.14.0/8.14.0/DOWNSTREAM_RELAY) with ESMTP id
	lBDMRQEO025795; Thu, 13 Dec 2007 14:27:26 -0800 (PST)
Received: from xch-swbh-11.sw.nos.boeing.com (xch-swbh-11.sw.nos.boeing.com
	[129.172.192.157])
	by blv-av-01.boeing.com (8.14.0/8.14.0/UPSTREAM_RELAY) with ESMTP id
	lBDMRG5R025530; Thu, 13 Dec 2007 14:27:26 -0800 (PST)
Received: from XCH-SW-5V2.sw.nos.boeing.com ([129.172.193.50]) by
	xch-swbh-11.sw.nos.boeing.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 13 Dec 2007 14:27:21 -0800
x-mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 13 Dec 2007 14:27:20 -0800
Message-ID: <51661468CBD1354294533DA79E85955A082004@XCH-SW-5V2.sw.nos.boeing.com>
In-Reply-To: <475DAB80.7010900@juniper.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: draft-morin-l3vpn-mvpn-considerations
Thread-Index: Acg7csvVaOG04JIISYecMZ3YQKVuugCYBeBQ
References: <475DAB80.7010900@juniper.net>
From: "Drake, John E" <John.E.Drake2@boeing.com>
To: "Ron Bonica" <rbonica@juniper.net>, <l3vpn@ietf.org>
X-OriginalArrivalTime: 13 Dec 2007 22:27:21.0980 (UTC)
	FILETIME=[5430B3C0:01C83DD7]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 93238566e09e6e262849b4f805833007
Cc: 
Subject: RE: draft-morin-l3vpn-mvpn-considerations
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>
Errors-To: l3vpn-bounces@ietf.org

Ron,

I'm in favor of this becoming a WG draft.  While some of the pieces in
the document may require further work, it's important that this be done
by the L3VPN working group.

Thanks,

John=20

>-----Original Message-----
>From: Ron Bonica [mailto:rbonica@juniper.net]=20
>Sent: Monday, December 10, 2007 1:11 PM
>To: l3vpn@ietf.org
>Subject: draft-morin-l3vpn-mvpn-considerations
>
>Folks,
>
>Unless I hear an objection before COB Friday, this document=20
>will become a WG draft.
>
>                                      Ron
>
>




From l3vpn-bounces@ietf.org Fri Dec 14 08:50:17 2007
Return-path: <l3vpn-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1J3AvA-0008Au-PT; Fri, 14 Dec 2007 08:49:44 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1J3Av9-0008Ao-GF
	for l3vpn@ietf.org; Fri, 14 Dec 2007 08:49:43 -0500
Received: from gc-na5.alcatel.fr ([64.208.49.5] helo=smail6.alcatel.fr)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1J3Av7-0005nI-J0
	for l3vpn@ietf.org; Fri, 14 Dec 2007 08:49:43 -0500
Received: from FRVELSBHS06.ad2.ad.alcatel.com (frvelsbhs06.ad2.ad.alcatel.com
	[155.132.6.78])
	by smail6.alcatel.fr (8.13.4/8.13.4/ICT) with ESMTP id lBEDltp9011835; 
	Fri, 14 Dec 2007 14:48:01 +0100
Received: from FRVELSMBS22.ad2.ad.alcatel.com ([155.132.6.52]) by
	FRVELSBHS06.ad2.ad.alcatel.com with Microsoft
	SMTPSVC(6.0.3790.2499); Fri, 14 Dec 2007 14:49:36 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 14 Dec 2007 14:49:27 +0100
Message-ID: <8144761F31F48D43AD53D09F5350E3800237BDD3@FRVELSMBS22.ad2.ad.alcatel.com>
In-Reply-To: <475DAB80.7010900@juniper.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: draft-morin-l3vpn-mvpn-considerations
Thread-Index: Acg7cssJFV+MtJjQQ4uNapqF22KhFABnwmpg
References: <475DAB80.7010900@juniper.net>
From: "PAPADIMITRIOU Dimitri" <Dimitri.Papadimitriou@alcatel-lucent.be>
To: "Ron Bonica" <rbonica@juniper.net>, <l3vpn@ietf.org>
X-OriginalArrivalTime: 14 Dec 2007 13:49:36.0082 (UTC)
	FILETIME=[29E29B20:01C83E58]
X-Scanned-By: MIMEDefang 2.51 on 155.132.188.84
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4b800b1eab964a31702fa68f1ff0e955
Cc: 
Subject: RE: draft-morin-l3vpn-mvpn-considerations
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>
Errors-To: l3vpn-bounces@ietf.org

hi ron, all

the document should focus on a solid analysis/description before
concluding with (strong) recommendations that are prescriptive and this,
at an early stage of the analysis.

here below a specific example to show that this analytical phase is not
completed to draw such conclusions/recommendations:

"By contrast, experience proves that PIM-based mechanisms are
operationally viable, but with well identified limitations.  Some of
those limitations may be improved upon (although there is currently no
clearly defined proposal to do this), however some of the limitations
appear to be intrinsic to the approach."

there are stated limitations but which limitations ? and to which extend
(all protocols developed by the IETF have certain limitations what.
matters is whether or not they are impacting in the interval of the
protocol operations and how degradations are impacting outside of this
interval)=20

more interestingly, the statement ack's they may be elevated but since
these limitations are stated to "appear as" intrinsic to the approach
and so they can not be elevated ? if this is the case where is the proof
for such statement ?

in general also, i suggest that authors keep protocol capabilities
analysis and consolidate their argumentation from feedback obtained on
the field as long as BGP-based approaches do not benefit from experience
on the field. indeed, in its current form, the document reads as
comparing disadvantages of experimental / deployment experience gained
from PIM wrt to theoretical expectations/advantages from new BGP-based
standards.

=3D> conclusions/recommendations need to be based on solid and fair
arguments enough to be perceived as truly prescriptive for driving the
protocol work and subsequent decisions of the working group. if these
conclusions/recommendation keep changing on per version basis (because
not complete or balanced enough) the document will miss its target.

imho, we have two solutions:

- either the document states that it is at an "early stage" of ongoing
investigation and removes statements that are, at this point in time,
interpretable and/or leading to early conclusions/ recommendations or
alike. hence, it can then become a WG document after re-spin. such
conclusions would be incorporated at final stage of analysis.=20

- or if the document wants to maintain its current conclusions it needs
to re-inforce and complete its argumentation/analysis. in that case
however, it is not ready in its current form to become now a working
group doc.

-d.

> -----Original Message-----
> From: Ron Bonica [mailto:rbonica@juniper.net]=20
> Sent: Monday, December 10, 2007 10:11 PM
> To: l3vpn@ietf.org
> Subject: draft-morin-l3vpn-mvpn-considerations
>=20
> Folks,
>=20
> Unless I hear an objection before COB Friday, this document=20
> will become
> a WG draft.
>=20
>                                       Ron
>=20
>=20




From l3vpn-bounces@ietf.org Fri Dec 14 09:02:09 2007
Return-path: <l3vpn-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1J3B76-0007ot-T0; Fri, 14 Dec 2007 09:02:04 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1J3B75-0007oo-Pf
	for l3vpn@ietf.org; Fri, 14 Dec 2007 09:02:03 -0500
Received: from exprod7og112.obsmtp.com ([64.18.2.177])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1J3B72-0006qV-RO
	for l3vpn@ietf.org; Fri, 14 Dec 2007 09:02:03 -0500
Received: from source ([66.129.224.36]) by exprod7ob112.postini.com
	([64.18.6.12]) with SMTP; Fri, 14 Dec 2007 06:01:49 PST
Received: from magenta.juniper.net ([172.17.27.123]) by emailsmtp56.jnpr.net
	with Microsoft SMTPSVC(6.0.3790.3959); 
	Fri, 14 Dec 2007 06:01:24 -0800
Received: from juniper.net (sapphire.juniper.net [172.17.28.108])
	by magenta.juniper.net (8.11.3/8.11.3) with ESMTP id lBEE1OE10396;
	Fri, 14 Dec 2007 06:01:24 -0800 (PST)
	(envelope-from yakov@juniper.net)
Message-Id: <200712141401.lBEE1OE10396@magenta.juniper.net>
To: erosen@cisco.com
In-Reply-To: Your message of "Wed, 12 Dec 2007 09:34:01 EST."
	<17617.1197470041@erosen-linux> 
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <63122.1197640883.1@juniper.net>
Date: Fri, 14 Dec 2007 06:01:23 -0800
From: Yakov Rekhter <yakov@juniper.net>
X-OriginalArrivalTime: 14 Dec 2007 14:01:24.0173 (UTC)
	FILETIME=[CFF0B7D0:01C83E59]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 94375f06b91351a23b2e62bbf6b5a18c
Cc: l3vpn@ietf.org
Subject: Re: Comments on draft-morin-l3vpn-mvpn-considerations-01.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>
Errors-To: l3vpn-bounces@ietf.org

Eric,

> I have carefully  reread draft-morin-l3vpn-mvpn-considerations-01.txt, and I
> have a number of comments.
>
> In  general, I  think the  authors have  done  a good  job in  trying to  be
> even-handed, but  I think there are some  errors in the details,  and I also
> think that some of  the risks and overheads involved in the  use of BGP have
> not been fully considered.
>

You fail to provide any specific facts below on the subject of risks
and overhead. Hence this can hardly be used as an objection against
progressing this document as a WG draft (see below for more...).

>  I also don't think that the different flavors of
> MPLS multicast  LSPs have  been carefully considered.
>

Agreed on this. However, considering different flavors of MPLS
multicast LSPs can be done after the document becomes a WG draft.
Remember that for a document to become a WG draft it doesn't have
to be perfect.

>    I would like  to see
> some of these issues addressed before adopting it as a WG draft.
>

See the previous comment.

> On the general issue of comparing PIM vs. BGP, while the draft does not make
> a recommendation, it  is heavy on PIM's disadvantages  and BGP's advantages.
> So I  think it is  worth listing some  of the risk areas  of BGP.  I  do not
> believe that  any of  these are "showstoppers"  for BGP, but  they certainly
> should  be articulated  in  any document  that  purports to  be providing  a
> balanced view.
 
The viewpoints should be based on rational *technical* arguments
and not FUD, and/or exercise in political correctness.

> - As BGP  is generally  used, BGP churn  is a  function of real  or apparent
>   topology changes.  BGP churn is NOT generally caused by enduser events.
>   This changes when  BGP is used to distribute  multicast routes.  BGP churn
>   can now  be initiated by PIM  Joins, and a PIM  Join may be  the result of
>   some enduser clicking  a button on his PC (e.g.,  "receive video").  it is
>   not clear that there is any limit on the rate at which such enduser events
>   can occur.  We do not appear to  have adequate data from which we can draw
>   conclusions as to the impact of enduser actions on BGP churn.
>
>   It is easy to offer opinions about this, but facts are scarce.
>

Precisely. So why should the draft talk about this since facts are
scarce ?

Moreover, what we are talking about here are two things (a) changes
in the multicast state on PEs due to receiving PIM Join/Prune from
CEs, and (b) a particular mechanism to propagate such changes among
PEs. The issue here is not "BGP churn", but the control plane load
due to (b). You failed to explain why control plane load due to (b)
would be less with PIM than with BGP. 

> - In some  multicast applications, "join  latency" is considered to  be very
>   important.  No  one has ever claimed  BGP will provide  lower join latency
>   than  PIM, the only  real question  is whether  latency will  be increased
>   beyond  the  limits  that   some  applications  find  acceptable.   Again,
>   different people have  different opinions about how much  this will matter
>   in practice, but hard data is hard to come by.

Again you fail to provide facts. This is just FUD. Moreover since PIM is
based on unreliable message exchange, "join latency" with PIM could be in
10s of seconds.

> - Churn  vs. latency:  To  control the  BGP  churn, we  have discussed  such
>   features as  Join Dampening.   However, that can't  be expected to  have a
>   salutary effect on the latency!
>
>   There really should  be some recognition in the draft  that the effects on
>   latency and churn are as yet poorly understood.
>

Section 16 of draft-ietf-l3vpn-2547bis-mcast-bgp discusses this in
sufficient detail. Moreover, Join Dampening is one, but not the
only one way to control control plane load. Another one is dampening
of withdrawls, which is described in Section 16.1. And quoting from
that section:

  "Dampening of withdrawals of C-multicast routes does not impede the
   multicast join latency observed by MVPN customers,"

Since you are a co-author on that draft, you should be aware of this.

>
> - Any time a new high volume address family is added to BGP. it is important
>   to consider  the impact on  the route reflectors,  and whether it  will be
>   necessary to add  new route reflectors, perhaps ones  dedicated to the new
>   family.  One should also consider the impact (especially on the RRs) which
>   one address family  may have on another, e.g.,  will an unexpectedly large
>   amount  of churn  due  to PIM  cause  a slowdown  in  the unicast  routing
>   convergence.  There should be some discussion of this.
>

Section 15 of draft-ietf-l3vpn-2547bis-mcast-bgp addresses this.
Since you are a co-author on that draft you should be aware of this.
And if you think something is missing, you as a co-author should
be able to add the appropriate text to that draft.

> - Transactional nature of PIM
>
>   At first glance,  it may seem that having  PIM distribute multicast routes
>   to BGP is no different than  having OSPF distribute unicast routes to BGP,
>   i.e., that it is really  nothing new.  However, this isn't quite accurate.
>   The issue  is that PIM isn't really  a "routing protocol" in  the sense of
>   choosing  routes  based   on  topology.   It  is  a   protocol  that  uses
>   router-to-router  transactions  to construct  paths  and  assign flows  to
>   paths. In  some cases, especially when  Sparse Mode flows  are involved, a
>   number of  transactions involving  multiple nodes may  need to  take place
>   before the multicast "routing" stabilizes.  Each one of these transactions
>   must  pass through  the RR,  placing more  load on  the RR  and increasing
>   latency.

Can you give a precise example ?

>   In  some  cases, where  PIM-SM  has  data-driven  state changes,  we  have
>   attempted  to avoid  putting the  data-driven state  changes into  BGP, by
>   having BGP send extra  messages, including timer-driven messages.  While I
>   tend to think that this is the right tradeoff, it does modify the dynamics
>   of path construction,  and we don't have any hard data  to tell us whether
>   we've made the right tradeoff,  or whether the "right tradeoff" depends on
>   just how the applications are using multicast.
>

As worded above this is yet another FUD.

> - Strange uses of PIM
>
>   Talk  to  anyone  with a  lot  of  experience  in  PIM deployment  in  the
>   enterprise, and you'll hear lots of  strange stories about how PIM is used
>   in some enterprises.   Although PIM is optimized for  "many receivers, few
>   sources", it isn't always used  that way.  I've also heard anecdotes about
>   applications that make assumptions about the dynamic nature of PIM and may
>   break if  anything changes.   As usual,  hard data is  hard to  find.  But
>   there's always a risk that when you change the infrastructure underneath a
>   crufty old application you will break the application.  There are people I
>   respect, with  much more experience  in multicast deployment than  I have,
>   who think it's  just foolish to do anything that changes  the way in which
>   the infrastructure behaves for sparse mode.  While I am not convinced that
>   they are  right, I think that  this does have  to be recognized as  a risk
>   element.
>

This is yet another FUD.

> Now let's look at some of the topics covered in the draft.
>
> 1. From section 3.1, "the operational burden of setting up multicast on a PE
>    or for a VR/VRF SHOULD be as low as possible".
>
>    I certainly  agree with  this!  However, I  don't think it  combines well
>    with the  later recommendation to support outsourced  RPs.  Obviously the
>    use of outsourced RPs increases the operational burden for the provider.
>
>    I  note that  there doesn't  seem to  be any  requirement for  making the
>    operational burden  of MVPN on the  SP's customer be as  low as possible,
>    though such a requirement is  prominent in another SP requirements draft,
>    viz.,  draft-mnapierala-mvpn-part-reqt-00.txt.  Such a  requirement would
>    see to  militate against  the use  of the "outsourced  RP", at  least for
>    MVPN customers who already use  multicast.  (Which I imagine would be the
>    vast majority of them.)
>

First of all, it is for SPs to decide whether they want this option
or not,  as they are in a much better position than the vendors to
figure out whether this supposed additional burden offers a benefit.

Second, if you argue in favor of reducing operational burden of
MVPN on the SP's customers, then outsourcing RP does reduce such
burden, as it moves the burden of managing customer's RP from
customers to the service provider. In fact, this is fairly consistent
with the main point of 2547 VPNs - outsourcing routing to the service
provider. Outsourced RP is just an example of doing this in the
context of multicast.

Finally, the draft also requires to support non-outsourced RP as
well.

> 2. Auto-discovery
>
>    "BGP-based  auto-discovery is the  preferred solution  for auto-discovery
>    ...  while  PIM/shared-tree  based  auto-discovery should  be  optionally
>    considered for migration purposes only".
>
>    There isn't  really a  dichotomy here.  The  facts are that  if PIM-based
>    shared  trees  are  used,  BGP-based auto-discovery  doesn't  really  add
>    anything,  but in  any  other circumstance,  BGP-based auto-discovery  is
>    absolutely necessary.
>
>    But  if the recommendation  here is  to provide  BGP-based auto-discovery
>    even in the one case where  it isn't strictly needed, I certainly support
>    that recommendation.  This  is, in fact, already true  of the majority of
>    existing MVPN  deployments.  (Though  I have been  told that there  is at
>    lest one vendor which does not support it in existing deployments.)
>
>    There is a suggestion in the  draft that if PIM-based shared trees are in
>    use, BGP auto-discovery can  help detect misconfigurations.  I'm not sure
>    about that, as I can imagine  transition scenarios in which more than one
>    shared tree is in use at some time.


I don't see any strong objections here. But again, reflecting this
in the draft could be done after the draft gets accepted as an L3VPN
WG document.

> 3. Number of protocols
>
>    "if any additional protocols are introduced compared with the unicast VPN
>    service,  the  balance between  their  advantage  and operational  burden
>    SHOULD be examined thoroughly"
>
>    Well, who  could disagree with that?   The pros/cons of  any new protocol
>    should always be  examined thoroughly.  In fact, the  pros/cons of adding
>    new  functionality  to  existing  protocols  should  always  be  examined
>    thoroughly  as well.   As  should  the pros/cons  of  adding new  address
>    families, new procedures,  new dynamics, new events and  states, etc., to
>    existing protocols.
>
>    It is better to focus on the overall complexity of the system, and on the
>    overall  behavior  of  the system,  than  just  to  count the  number  of
>    protocols.

While there is nothing wrong in focusing "on the overall complexity
of the system", one should not ignore the fact that the number of 
protocols required does impact the complexity.

> 4. S-PMSI Signaling
>
>    The BGP-based S-PMSI  signaling mechanism does have a  risk factor that I
>    have mentioned above, but that is not considered in the draft
>
>    In current practice,  BGP changes are caused by  topology changes, not by
>    end  user  activity.   However,   it  is  enduser  activity  that  causes
>    invocation of the S-PMSI signaling  mechanism.  We simply do not have the

This is not exactly accurate, as S-PMSI signaling is triggered not
by the PEs connected to the receivers, but by the PE connected to the
source.

>    data at  the present time  to determine how  much this will  increase the
>    amount of churn  in BGP.

Again this is FUD, and not based on any facts. Moreover, it ignores
the fact that what we really talking about here is the control
plane load due to S-PMSI signaling. Please explain why the control
plane load due to S-PMSI signaling with BGP be any more than with
UDP-based signaling. 

>    The S-PMSI signaling is  also something that is
>    best done through a low latency  mechanism, and we do not at present have
>    the data to determine whether BGP will significantly increase the latency
>    when compared with the UDP-based proposal.

Perhaps you forgot that the UDP-based S-PMSI signaling doesn't have
a predictable bound on latency as its non-reliable. So a loss of a
message results in 60 secs latency.

And while we on this topic, could please quantify "significantly"
as you assert that "BGP will significantly increase the latency".

>    In theory,  the use of BGP  S-PMSI signaling has a  number of advantages,
>    but I  don't think  I would  recommend against the  use of  the UDP-based
>    procedure unless and until I had some data about these pragmatic issues.
>

This is yet another FUD.

>    By the  way, when I  say "data", I  don't mean "strongly held  and loudly
>    voiced  opinions", even  though the  latter are  sometimes  confused with
>    data.
>
>    "The  UDP-based protocol  is  restricted  to use  within  MVPNs using  an
>    MI-PMSI".
>
>    This fact seems to me to be  neither here nor there.  It is true that the
>    UDP-based protocol is unlikely to be useful unless PIM is the C-multicast
>    routing control protocol, in which case  you have an MI-PMSI.  If you are
>    using  BGP as  the C-multicast  routing protocol,  then you  have already
>    determined that you don't care if BGP churn is caused by enduser events.
>
>    The UDP-based S-PMSIs signaling is best considered as an optional part of
>    the  PIM C-multicast  routing control  plane, rather  than as  a separate
>    protocol with its own independent set of pros and cons.

This could be made after the draft is accepted as a WG document
(and it should be *based on the WG consensus*).

>
>    "the  use  of  the  UDP-based  protocol  does  not  preserve  AS  routing
>     independence  when  used in  an  inter-AS  option  B context  (i.e.  the
>     decision by  a PE in an  AS to use an  S-PMSI for a  given customer flow
>     will impact routing state in other ASes)
>
>    I  have no  idea what  this means,  so I  hope one  of the  authors will
>    explain.   (I also  don't  know what  is  meant by  the  claim that  the
>    BGP-based S-PMSI signaling  mechanism doesn't have whatever disadvantage
>    this is.)
>

It means couple of things. First of all, UDP based S-PMSI forces
all ASes to switch to the S-PMSI. In contrast with BGP based segmented
inter-AS S-PMSIs, each AS can decide on its own whether (a) to
propagate the S-PMSI or (b) aggregate S-PMSI into an I-PMSI.

Second, with UDP-based S-PMSI all the ASes have to use the same
tunneling technology. In contrast BGP-based S-PMSI supports segmented
inter-AS tunnels, which enables each AS to make its own choice with
respect to tunneling technology (something which is already supported
for 2547 unicast).

> 5. Off-loading processing onto route reflector
>
>    The claim is made that, when using BGP to carry C-multicast routes, "some
>    of  the processing burden  associated with  client multicast  routing [is
>    offloaded] onto BGP route reflectors"
>
>    I  would  like the  authors  to  specify  precisely what  this  offloaded
>    processing burden is.  Some consideration of its effect on existing L3VPN
>    route reflector systems would also be worthwhile.
>

As for the last "effect on existing L3VPN route reflector systems",
please note the the following text in Section 15 of
draft-ietf-l3vpn-2547bis-mcast-bgp:

   Moreover, Route Reflectors used for MVPN do not have to be 
   used for VPN-IP routes

And as a reminder, you are a co-author on that draft !


>    As the  text is now, it is  very difficult to understand  or evaluate the
>    claim.
>
>
> 6. MI-PMSI issues
>
>    "Moreover, mechanisms one and two are restricted to use within MVPNs
>    using an MI-PMSI, thereby necessitating:
>
>    a.  The use of a P-multicast tree technique that allows shared trees
>        (for example PIM-SM in ASM mode or MP2MP LDP).
>
>    b.  The use of one P-multicast tree per PE per VPN, even for PEs that
>        do not have sources in their directly attached sites for that
>        VPN."
>
>    First,  claim b  is  not true,  as  explained in  draft-rosen-l3vpn-mvpn-
>    profiles-00.txt, section 3.3.
>

What is described in section 3.3 of the sited draft restricts
tunneling technology to just *one* - mp2mp LSP with mLDP. As such 
what is described in section 3.3 of the sited draft violates one
of the requirements from rfc4834:

    the control plane SHALL NOT depend on which forwarding plane is used

>    Second, the fact that a control  protocol requires that it be possible to
>    instantiate a P-tunnel as a shared tree  of some sort does not seem to be
>    to be  a "restriction" or disadvantage.   You might as well  say that the
>    use  of  BGP  for  C-multicast  routing has  the  disadvantage  of  being
>    "restricted"  to those networks  whose route  reflectors support  the BGP
>    C-multicast routing address family.
>
>    There are however some other things  that do seem to require the presence
>    of an MI-PMSI:   autoRP and BSR.  Since many  SP customers use autoRP/BSR
>    to discover  RPs, and since  it is not  clear how to provide  support for
>    these without an  MI-PMSI, I am not convinced that one  can do without an
>    MI-PMSI even if BGP is used for distributing C-multicast routes.

First of all, autoRP is a cisco proprietary technology. Asking
standars to support cisco proprietary technology is inappropriate.

Second, just because you are "not convinced", does not mean it can
not be done.  In fact, just to remind you, supporting BSR without
MI-PMSI has been explained in the presentation at the L3VPN WG
meeting (with you as one of the co-authors on that presentation).

> 7. BGP doesn't eliminate PIM anyway
>
>    "using BGP for customer routing distribution within multicast VPNs avoids
>    the introduction of an  additional protocol that would require additional
>    OAM processes and tools."
>
>    It's not as if  PIM is eliminated by BGP.  As long as  PIM is used on the
>    PE/CE links, the SP is still operating a PIM environment.
>

It is not the same as using PIM in the backbone.

Moreover, it is not just about eliminating PIM, but also about
having the same architecture for both unicast and multicast vs
requiring two fundamentally different architectures, one for unicast
(aggregated routing), and another for multicast (virtual routers).

>
>    In fact, there
>    may be significant  scaling problems due to PE-CE  PIM.  Some people with
>    years of PIM  experience believe that the PE-CE  PIM scaling problems are
>    actually worse  than the PE-PE PIM  scaling problems, and  hence that the
>    attempt  to improve PE-PE  scaling by  using BGP  just attacks  the wrong
>    problem.

Let the SPs speak up and tell us that !

>    In the absence of  actual data, the risk is that you  end up adding a lot
>    of NEW stuff and don't even address the scaling bottlenecks.
>
>    In  any  event, I'm  not  sure  I understand  how  adding  a  lot of  new
>    functionality  to BGP  (multicast  path  creation) is  going  to be  done
>    without the need for additional OAM processes and tools.
>

Without any specifics this statement is yet another FUD.

> 8. Consistency with unicast control mechanisms.
>
>    "An illustrative example of the benefit brought by consistency with
>    unicast design is how the "extranet" feature can be implemented :
>    when BGP-based mechanisms are used, the well defined and well
>    understood BGP route target import/export semantics are just reused."
>
>    This seems like a red  herring.  Extranet capability is already supported
>    in  the field  today  by existing  MVPN  deployments based  on PIM.   The
>    primary impact is really on the auto-discovery phase, not the C-multicast
>    routing phase.
>

What is "in the field today" is hardly based on reuse of 2547 unicast
mechanisms. And moreover, it uses a completely different architecture
(Virtual Routers).

In fact, can you explain why having one architecture for unicast
VPN (aggregated routing) and another architecture for multicast VPN
(virtual routers) is any better than having the same architecture
for both unicast and multicast VPN ?

>
> 9. Encapsulation techniques
>
>     I notice that  there is one particular data plane  technique that is not
>     addressed  by the  document, viz.,  the use  of ingress  replication and
>     transmission through  unicast tunnels.  It would be  interesting to know
>     whether SPs  have interest in this  technology; if not, maybe  it can be
>     removed from the  drafts.  (I think it adds  complexity and frankly, I'm
>     not sure it's fully and properly specified.)
>

As for the former, I will let SPs decide. As for the latter can you point
out *precisely* what is not "fully and properly specified" ?

>     I think section 3.4 can be taken as a requirement for both a "BGP + GRE"
>     profile  and a  "PIM +  MPLS" profile,  since it  seems to  advocate for
>     independence between the the control  plane and the data plane.  But I'm
>     not sure if that is what is intended, and would like clarification.
>
>     I would like  to see a specific recommendation for  the support of MP2MP
>     LSPs,  given their  importance in  C-bidir support  (for  either control
>     plane, see draft-ietf-l3vpn-2547bis-  mcast-05.txt, section 12.2) and in
>     general MPLS  multicast support  for the PIM  control plane  (see draft-
>     rosen-l3vpn-mvpn-profiles-00.txt, section 3.3).
>

The flavor of MPLS multicast LSPs can be clarified after adopting this 
as a WG draft.

>
> 10. Upstream-Assigned Labels, MI-PMSI, and Scalability
>
>     The  WG drafts frequently  discuss aggregation,  and the  possibility of
>     aggregation is frequently touted as a major scalability advantage.
>
>     What isn't always clear is  that all forms of S-PMSI aggregation require
>     a  major   new  MPLS  feature,   upstream-assigned  labels.   Supporting
>     upstream-assigned labels requires significant  changes to the data plane
>     processing  of  many  different  platforms,  and is  not  likely  to  be
>     available for some period of time.
>
>     So realistically, for  the foreseeable future, the use  of an MI-PMSI is
>     going  to remain  the  only  method of  aggregation.
>

Do you speak just for cisco, or for all other vendors as well ?

>     Unless a  service
>     provider does not care if their  P-routers have to maintain an amount of
>     multicast state  which is proportional to  the sum of the  states of all
>     their customers, the service provider should be requiring support for an
>     MI-PMSI.
>
>     As  a further  note,  it should  be  pointed out  that inter-AS  segment
>     S-PMSIs are on a per-PE basis, not a per-AS basis.  Therefore without the
>     aggregation that  can be obtained  from upstream-assigned labels,  it is
>     not clear that segmented inter-AS  S-PMSIs are scalable at all.
>

Are they less scalable than non-segmented inter-AS S-PMSIs ?

>     This is an issue which should be mentioned.
>
>     I think the draft should have a clear recommendation that in the absence
>     of upstream-assigned MPLS labels, MI-PMSIs should be used.
>

I-PMSI vs S-PMSI offers service providers a tradeoff between state and
b/w. Each service provider should be able to make such a tradeoff on its
own, without standards mandating a particular tradeoff (in your own words
"one size doesn't fit all")

With this in mind the recommendations should reflect position of
SPs, not vendors (and you are part of the latter, not the former). 


> 11. Outsourced RPs
>
>     I  would like  to see  the  draft offer  much stronger  support for  its
>     recommendation to  implement outsourced RPs,  or else to  eliminate that
>     recommendation.
>
>     Outsourced RPs  (i.e., PE  as RP) have  a number of  disadvantages which
>     need to be given more emphasis:
>
>     - More work  for the PE (do  many SPs really want  to give a  lot of new
>       work to their PEs)?
>

If less work for the PEs is the goal, then one should not run 2547 VPNs,
but rather L2 VPN, or CE-based VPNs.

>     - Not  likely to  be  of much  interest  to customers  with an  existing
>       multicast infrastructure
>

Do you speak for the service providers ? As if not, then this is
to be determined by the service providers, not by vendors.

>     - Require  increased coordination  between SP  and  enterprise customer,
>       such as agreement on RP (or RPL) addresses.
>

Let's put this in a proper perspective (and strip the FUD).  For
all CE-PE links there has to be coordination between SP and customers
in terms of addresses used for these links. Requiring coordination
for *one more address* (and that is all what you need for outsourced
RP or RPL) does not seem like a significant increase.

>     - Not completely clear  how this works in scenarios  where an enterprise
>       gets VPN  service from two different providers,  particularly if there
>       is a site multihomed to two different providers.

What precisely is not "clear" ?

>     I presume  that the extra  operational work for  SP and customer  is not
>     going to be justified by the  fact that it simplifies things for some of
>     the SP's vendors.
>
>
> 12. The draft's conclusion
>
>    "Consequently, at the present time and until there is experience with
>    all of the proposed mechanisms it is not clear which of the above
>    mechanisms should be recommended as the preferred solution to
>    implementers.  However, it would appear prudent for implementations
>    to consider supporting both the fourth (BGP-based) and first (full
>    per-MPVN PIM peering) mechanisms.  Further experience on both
>    implementation is likely to be required before some best practice can
>    be defined."
>
>    I certainly agree with this  conclusion.  Perhaps it should be given more
>    prominence.
>
>
> 13. My conclusion
>
>     While  I do  think this  draft may  be a  good start  on the  project of
>     comparing the  different MVPN options, I  don't think it is  ready to be
>     adopted as a WG document, and it  needs a lot more work to deal with the
>     issues I have raised in this note.
>

Of the issues raised by you in the above the only legitimate ones
seems to be (a) more analysis on different flavor of multicast LSPs,
(b) whether there is a need for BGP-based auto-discovery with
PIM-based shared trees, and (c) whether the UDP-based S-PMSIs
signaling should be best considered as an optional part of the  PIM
C-multicast  routing control  plane.  All of these issues can be
addressed after the document gets adopted as a WG draft.

The rest of your issues fall in the category of either (a) FUD (not
subsantiated by facts), or (b) asking for editorial clarifications,
or (c) telling the SPs what choices they have to make, rather than
letting SPs to make these choices on their own.  None of these are
legitimate objections to accepting the draft as an L3VPN WG
document.

With this in min I support accepting 
draft-morin-l3vpn-mvpn-considerations-01.txt as an L3VPN WG document.

Yakov.




From l3vpn-bounces@ietf.org Fri Dec 14 09:21:44 2007
Return-path: <l3vpn-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1J3BQ2-0004GX-M1; Fri, 14 Dec 2007 09:21:38 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1J3BQ1-0004GQ-HQ
	for l3vpn@ietf.org; Fri, 14 Dec 2007 09:21:37 -0500
Received: from exprod7og110.obsmtp.com ([64.18.2.173])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1J3BQ0-0007Kz-Rx
	for l3vpn@ietf.org; Fri, 14 Dec 2007 09:21:37 -0500
Received: from source ([66.129.224.36]) by exprod7ob110.postini.com
	([64.18.6.12]) with SMTP; Fri, 14 Dec 2007 06:21:31 PST
Received: from magenta.juniper.net ([172.17.27.123]) by emailsmtp56.jnpr.net
	with Microsoft SMTPSVC(6.0.3790.3959); 
	Fri, 14 Dec 2007 06:21:15 -0800
Received: from juniper.net (sapphire.juniper.net [172.17.28.108])
	by magenta.juniper.net (8.11.3/8.11.3) with ESMTP id lBEEL5E13758;
	Fri, 14 Dec 2007 06:21:05 -0800 (PST)
	(envelope-from yakov@juniper.net)
Message-Id: <200712141421.lBEEL5E13758@magenta.juniper.net>
To: "PAPADIMITRIOU Dimitri" <Dimitri.Papadimitriou@alcatel-lucent.be>
In-Reply-To: Your message of "Fri, 14 Dec 2007 14:49:27 +0100."
	<8144761F31F48D43AD53D09F5350E3800237BDD3@FRVELSMBS22.ad2.ad.alcatel.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <68408.1197642065.1@juniper.net>
Date: Fri, 14 Dec 2007 06:21:05 -0800
From: Yakov Rekhter <yakov@juniper.net>
X-OriginalArrivalTime: 14 Dec 2007 14:21:15.0869 (UTC)
	FILETIME=[963F18D0:01C83E5C]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b5d20af10c334b36874c0264b10f59f1
Cc: l3vpn@ietf.org
Subject: Re: draft-morin-l3vpn-mvpn-considerations 
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>
Errors-To: l3vpn-bounces@ietf.org

Dimitri,

> hi ron, all
> 
> the document should focus on a solid analysis/description before
> concluding with (strong) recommendations that are prescriptive and this,
> at an early stage of the analysis.
> 
> here below a specific example to show that this analytical phase is not
> completed to draw such conclusions/recommendations:
> 
> "By contrast, experience proves that PIM-based mechanisms are
> operationally viable, but with well identified limitations.  Some of
> those limitations may be improved upon (although there is currently no
> clearly defined proposal to do this), however some of the limitations
> appear to be intrinsic to the approach."
> 
> there are stated limitations but which limitations ? and to which extend
> (all protocols developed by the IETF have certain limitations what.
> matters is whether or not they are impacting in the interval of the
> protocol operations and how degradations are impacting outside of this
> interval) 

Read section 3.3 of draft-morin-l3vpn-mvpn-considerations,
as it covers the issues you mentioned above.

> more interestingly, the statement ack's they may be elevated but since
> these limitations are stated to "appear as" intrinsic to the approach
> and so they can not be elevated ? if this is the case where is the proof
> for such statement ?
> 
> in general also, i suggest that authors keep protocol capabilities
> analysis and consolidate their argumentation from feedback obtained on
> the field as long as BGP-based approaches do not benefit from experience
> on the field. indeed, in its current form, the document reads as
> comparing disadvantages of experimental / deployment experience gained
> from PIM wrt to theoretical expectations/advantages from new BGP-based
> standards.

The document compares different *technologies*, and makes recommendations
based on such comparison. Such comparison reflects underlying
properties/characteristics of these technologies. Since these are
the properties/characteristics of the technologies, these
properties/characteristics do not depend on whether these technologies
are deployed or not.

> => conclusions/recommendations need to be based on solid and fair
> arguments enough to be perceived as truly prescriptive for driving the
> protocol work and subsequent decisions of the working group. if these
> conclusions/recommendation keep changing on per version basis (because
> not complete or balanced enough) the document will miss its target.
> 
> imho, we have two solutions:
> 
> - either the document states that it is at an "early stage" of ongoing
> investigation and removes statements that are, at this point in time,
> interpretable and/or leading to early conclusions/ recommendations or
> alike. hence, it can then become a WG document after re-spin. such
> conclusions would be incorporated at final stage of analysis. 
> 
> - or if the document wants to maintain its current conclusions it needs
> to re-inforce and complete its argumentation/analysis. in that case
> however, it is not ready in its current form to become now a working
> group doc.

While one may argue that the argumentation/analysis is not perfect,
it is good enough for the draft to be accepted as an L3VPN WG
document. The argumentation/analysis could be perfected after
the document is accepted, and it would reflect the L3VPN WG
consensus.

Yakov.

> 
> -d.
> 
> > -----Original Message-----
> > From: Ron Bonica [mailto:rbonica@juniper.net] 
> > Sent: Monday, December 10, 2007 10:11 PM
> > To: l3vpn@ietf.org
> > Subject: draft-morin-l3vpn-mvpn-considerations
> > 
> > Folks,
> > 
> > Unless I hear an objection before COB Friday, this document 
> > will become
> > a WG draft.
> > 
> >                                       Ron
> > 
> > 
> 
> 




From l3vpn-bounces@ietf.org Fri Dec 14 11:20:45 2007
Return-path: <l3vpn-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1J3DGM-0002Tb-Q8; Fri, 14 Dec 2007 11:19:46 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1J3DGL-0002Ry-B7
	for l3vpn@ietf.org; Fri, 14 Dec 2007 11:19:45 -0500
Received: from rtp-iport-1.cisco.com ([64.102.122.148])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1J3DGK-0001SN-At
	for l3vpn@ietf.org; Fri, 14 Dec 2007 11:19:45 -0500
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by rtp-iport-1.cisco.com with ESMTP; 14 Dec 2007 11:19:44 -0500
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13])
	by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id lBEGJiD0010703; 
	Fri, 14 Dec 2007 11:19:44 -0500
Received: from erosen-linux.cisco.com (erosen-linux.cisco.com [161.44.70.34])
	by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id
	lBEGJhZG024534; Fri, 14 Dec 2007 16:19:43 GMT
Received: from erosen-linux (localhost.localdomain [127.0.0.1])
	by erosen-linux.cisco.com (8.13.1/8.13.1) with ESMTP id lBEGJhQl010990; 
	Fri, 14 Dec 2007 11:19:43 -0500
To: Yakov Rekhter <yakov@juniper.net>
In-reply-to: Your message of Fri, 14 Dec 2007 06:01:23 -0800.
	<200712141401.lBEE1OE10396@magenta.juniper.net> 
Date: Fri, 14 Dec 2007 11:19:43 -0500
Message-ID: <10989.1197649183@erosen-linux>
From: Eric Rosen <erosen@cisco.com>
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=8463; t=1197649184;
	x=1198513184; c=relaxed/simple; s=rtpdkim1001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=erosen@cisco.com;
	z=From:=20Eric=20Rosen=20<erosen@cisco.com>
	|Subject:=20Re=3A=20Comments=20on=20draft-morin-l3vpn-mvpn-
	considerations-01.txt=20 |Sender:=20
	|To:=20Yakov=20Rekhter=20<yakov@juniper.net>;
	bh=wMgsHExttydrMzqTzAvzuzPpGqcTUq9067OisvQ9S28=;
	b=mciM7JyJV7zrIlRJY+Z4pGYo/xZWFIm80sHogyjIZ1HKxHRxzR9Fsys2ie
	4+gT9EMucaYnPNcqau3GBxc9e9Ot92CSDle1k4PZlLytS/gP56Wlwgt5lWL2
	J8ItKciJHB;
Authentication-Results: rtp-dkim-1; header.From=erosen@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim1001 verified; ); 
X-Spam-Score: -4.0 (----)
X-Scan-Signature: 848ed35f2a4fc0638fa89629cb640f48
Cc: erosen@cisco.com, l3vpn@ietf.org
Subject: Re: Comments on draft-morin-l3vpn-mvpn-considerations-01.txt 
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: erosen@cisco.com
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>
Errors-To: l3vpn-bounces@ietf.org


I think Yakov's  reply makes it pretty clear that  adoption of this document
as a WG document at the current time is premature.

I was  prepared for someone to  say that the  issues I raised can  be worked
after the  document is accepted.  However,  we see from  Yakov's answer that
he,  at least,  wants to  suppress discussion  of all  the  remaining issues
(after all, they're  all FUD ;-)).  I didn't think my  reputation in this WG
was that of a FUD-provider, but YMMV ;-)

For the kind of document that draft-morin seems to be, I think it is the job
of the authors to investigate all  the issues, not to say "we won't consider
any issue until some  else proves beyond a shadow of a  doubt that there's a
real problem".  Of  course, I'll be happy to work with  the authors to flesh
out  all the  arguments  pro and  con.  I'm  not  trying to  prove that  the
BGP-based scheme won't  work, but I'd have thought  that everyone knows that
all proposals have  pros and cons; a "considerations"  document should bring
out all the issues.

In fairness, Yakov isn't one of the  authors of the document, so it would be
interesting to know whether the authors  of the document agree that there is
no need to discuss any of the issues I've raised.

A few of the more outrageous comments do require some reply:

> why should the draft talk about this [variety of factors for which we lack
> hard data] since facts are scarce ?

Any choice  which is based  on opinion  rather than facts  is a risk,  and a
"considerations"  document should certainly  make it  clear when  such risks
exist.

> Moreover since PIM is based on unreliable message exchange, "join latency"
> with PIM could be in 10s of seconds.

The worst  case join latency in  either case could be  arbitrarily long, but
I'm sure everyone knows ((well, almost everyone ;-)) that's it's the average
join latency that is important.  Since packets don't usually get lost in the
backbone, that's  not much of  an issue.   I don't think  it takes a  lot of
fancy analysis  to determine  that it's  faster to send  a data  packet from
point A  to point B then  to send it from  point A to  an intermediate point
where it  is processed and then afterwards  sent along to point  C.  One can
argue  that the  latency increase  isn't significant,  or that  it's  a good
tradeoff  against something  else,  but it's  just  silly to  deny that  the
latency increase exists!

> could  please  quantify  "significantly"  as  you assert  that  "BGP  will
> significantly increase the latency".

I did  not state that  BGP will significantly  increase the latency,  I said
that we  do not have  the data to  determine whether BGP  will significantly
increase the latency.

A "significant  increase" would be one  that causes a visible  effect to the
users of a multicast-based application.

>  "Dampening of  withdrawals [as opposed to updates]  of C-multicast routes
>   does not impede the multicast join latency observed by MVPN customers,"

Sure, but  it doesn't have the same  effect on churn reduction  as does join
dampening, and it has other side-effects as well.  This is certainly an area
that would benefit from more analysis in any "considerations" document.

> Since you are a co-author on that draft, you should be aware of this.

I'm glad  you remembered that I'm  a co-conspirator (err,  co-author) of the
BGP-based multicast control plane.  As  a co-author, I am familiar with lots
of  issues  that  might  not  necessarily  be  obvious  to  the  authors  of
draft-morin.  Further,  I appear  to be the  only co-author who  thinks that
both  BGP and  PIM have  merits, and  that it  is important  to do  a pretty
thorough and unbiased comparison.

> As for the last "effect on existing L3VPN route reflector systems",
> please note the the following text in Section 15 of
> draft-ietf-l3vpn-2547bis-mcast-bgp:

>   Moreover, Route Reflectors used for MVPN do not have to be 
>   used for VPN-IP routes

> And as a reminder, you are a co-author on that draft !

Yes, I am well aware that you  can add new RRs expressly to handle multicast
routes.  In  a "considerations" document, the  need (or lack of  need) to do
this is one of the considerations  that should be discussed.  Unless the SPs
are willing to say up front "not to worry, we don't care how many additional
RRs we need, they come for free and do not increase our operational burden".

As you know, I am a big fan of the 2547 technology :-), but the issue of how
the VPN-IP routes affect BGP generally (and how much "BGP churn" they cause)
has  always  been with  us.   At  least VPN-IP  routes  do  not behave  much
differently than  IP routes, since  updates are still triggered  by topology
changes and  not by  enduser activity.  MVPN  introduces a different  set of
dynamics to BGP and the impact on  the rest of the BGP system is certainly a
consideration that needs to be better understood.

It is fair  to point out that additional BGP activity  is at least partially
compensated for by reduced PIM activity.  On the other hand, PIM activity 
doesn't impact the BGP system, so this comparison is not straightforward.

> In fact, can you explain why having one architecture for unicast
> VPN (aggregated routing) and another architecture for multicast VPN
> (virtual routers) is any better than having the same architecture
> for both unicast and multicast VPN ?

I  think the  choice between  the two  schemes should  be based  not  on the
elegance of  the architecture but on  the multitude of  facts that determine
(a) how well the multicast applications in the enterprise will be supported,
and (b) how much operational impact they have on the SP.  

Further, multicast  routing is  really a very  different thing  than unicast
routing, and  there is  no history of  success in  combining the two  into a
single architecture (e.g., MOSPF).

This is  not to say  that BGP is  a poor choice, but  just to explain  why I
don't  think that  the  uniformity  of the  architecture  is the  overriding
considerations. 

> First of all, autoRP is a cisco proprietary technology. Asking
> standards to support cisco proprietary technology is inappropriate.

If  an enterprise  is using  proprietary technology,  and if  a SP  wants to
provide MVPN service to that enterprise,  then I think the SP will certainly
want to know whether he has to  tell the enterprise "no MVPN service for you
until you change your deployed technologies" ;-)

A large number of enterprises use Cisco technology, and I imagine that other
vendors would like to be able to provide PEs that support those enterprises.

> supporting BSR without  MI-PMSI has been explained in  the presentation at
> the  L3VPN  WG  meeting  (with  you  as one  of  the  co-authors  on  that
> presentation).

Many of  the presentations  we've given over  the years  presented solutions
which  turned out  to  be  unsatisfactory.  Certainly  the  support or  lack
thereof  for  BSR  is  something  that a  "considerations"  document  should
examine.

>> realistically, for  the foreseeable future, the use  of an MI-PMSI is
>>     going  to remain  the  only  method of  aggregation.

> Do you speak just for cisco, or for all other vendors as well ?

I would highly recommend that before eliminating the MI-PMSI, the SPs should
get solid  delivery dates from  their vendors for  upstream-assigned labels!
;-)

>> it is not clear that segmented inter-AS  S-PMSIs are scalable at all.

> Are they less scalable than non-segmented inter-AS S-PMSIs ?

In my mind, the issue is whether there's a real good inter-provider solution
at all. 

> If less work for the PEs is the goal, then one should not run 2547 VPNs,

Well, I'd like to hear the SPs  say that they don't care how much additional
work  the PEs  have to  do!  Or  that they  don't care  how  much additional
coordination they have  to do with their customers, or  that they don't care
how many  changes the customers  have to make  before they can buy  the SPs'
service. 

> the recommendations should  reflect position of SPs, not  vendors (and you
> are part of the latter, not the former).

I've yet to hear any SP say that they don't want my input because I work for
a  vendor.  If  any  do  feel that  way,  I'm sure  they  can  speak up  for
themselves.








From l3vpn-bounces@ietf.org Fri Dec 14 11:44:46 2007
Return-path: <l3vpn-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1J3Ddg-0005sD-3Q; Fri, 14 Dec 2007 11:43:52 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1J3Dde-0005pT-M1
	for l3vpn@ietf.org; Fri, 14 Dec 2007 11:43:50 -0500
Received: from p-mail2.rd.francetelecom.com ([195.101.245.16])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1J3Ddb-0001z6-5T
	for l3vpn@ietf.org; Fri, 14 Dec 2007 11:43:50 -0500
Received: from ftrdmel10.rd.francetelecom.fr ([10.193.117.156]) by
	ftrdsmtp2.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 14 Dec 2007 17:43:41 +0100
Received: from [10.193.15.109] ([10.193.15.109]) by
	ftrdmel10.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 14 Dec 2007 17:43:40 +0100
From: Thomas Morin <thomas.morin@orange-ftgroup.com>
To: erosen@cisco.com
In-Reply-To: <17617.1197470041@erosen-linux>
References: <17617.1197470041@erosen-linux>
Content-Type: text/plain
Organization: France Telecom R&D - Orange
Date: Fri, 14 Dec 2007 17:43:40 +0100
Message-Id: <1197650620.4979.103.camel@wintermute>
Mime-Version: 1.0
X-Mailer: Evolution 2.12.2 
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 14 Dec 2007 16:43:40.0952 (UTC)
	FILETIME=[7B834980:01C83E70]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2f46977da373544777a750d5247d6ccc
Cc: l3vpn@ietf.org
Subject: Re: Comments on draft-morin-l3vpn-mvpn-considerations-01.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>
Errors-To: l3vpn-bounces@ietf.org

Hi Eric,

I'm surprised to read such a long email from you, given that you didn't
make any comment on the presentation last Wednesday.

I think we would be, all co-authors of this document, happy to make
clarifications to address your comments.  There are definitely some
areas where content can be improved to be more precise on the pros/cons
of the different approaches. It is precisely the kind of feedback we
asked. I will go more in depth in a further email on items that I see
can be worked on.

However, among the items mentioned in your comments, there are also
points which are a bit "philosophical", or vague, or confusing, not to
mention a few ones which seem to me as erroneous or clearly misleading.
I'll explain in another email why I think some of your comments fall in
these categories, but to get to the point : I don't think diluting the
real content into risk-related worries or philosophical aspects would be
a good idea. On the contrary, we should focus on facts-driven
considerations that help distinguish relative merits on different
options between which we need to make a recommandation.  In light of
this, I don't think we can promise to say "yes sure we'll cover it" to
all your worries...

But in the end, given the support of the working group I would not
expect the improvements to be made as requiring delaying the adoption of
the draft by the working group, since it seems that we agree on the
intent, structure and general direction of the document. After all, if
adoption of a work by a working group was requiring having finished the
doc, then adoption as WG item and Last Call could be made at the same
time, right ?  ;-)

So, night is coming and I'll get back to thinking about buying christmas
gifts and follow up on this next week.

Cheers,

-Thomas


On mer, 2007-12-12 at 09:34 -0500, Eric Rosen wrote:
> I have carefully  reread draft-morin-l3vpn-mvpn-considerations-01.txt, and I
> have a number of comments.
> 
> In  general, I  think the  authors have  done  a good  job in  trying to  be
> even-handed, but  I think there are some  errors in the details,  and I also
> think that some of  the risks and overheads involved in the  use of BGP have
> not been fully considered.  I also don't think that the different flavors of
> MPLS multicast  LSPs have  been carefully considered.   I would like  to see
> some of these issues addressed before adopting it as a WG draft.
> 
> On the general issue of comparing PIM vs. BGP, while the draft does not make
> a recommendation, it  is heavy on PIM's disadvantages  and BGP's advantages.
> So I  think it is  worth listing some  of the risk areas  of BGP.  I  do not
> believe that  any of  these are "showstoppers"  for BGP, but  they certainly
> should  be articulated  in  any document  that  purports to  be providing  a
> balanced view. 
> 
> - As BGP  is generally  used, BGP churn  is a  function of real  or apparent
>   topology changes.  BGP churn is NOT generally caused by enduser events.
> 
>   This changes when  BGP is used to distribute  multicast routes.  BGP churn
>   can now  be initiated by PIM  Joins, and a PIM  Join may be  the result of
>   some enduser clicking  a button on his PC (e.g.,  "receive video").  it is
>   not clear that there is any limit on the rate at which such enduser events
>   can occur.  We do not appear to  have adequate data from which we can draw
>   conclusions as to the impact of enduser actions on BGP churn.
> 
>   It is easy to offer opinions about this, but facts are scarce.
> 
> - In some  multicast applications, "join  latency" is considered to  be very
>   important.  No  one has ever claimed  BGP will provide  lower join latency
>   than  PIM, the only  real question  is whether  latency will  be increased
>   beyond  the  limits  that   some  applications  find  acceptable.   Again,
>   different people have  different opinions about how much  this will matter
>   in practice, but hard data is hard to come by.
> 
> - Churn  vs. latency:  To  control the  BGP  churn, we  have discussed  such
>   features as  Join Dampening.   However, that can't  be expected to  have a
>   salutary effect on the latency!
> 
>   There really should  be some recognition in the draft  that the effects on
>   latency and churn are as yet poorly understood.
> 
> - Any time a new high volume address family is added to BGP. it is important
>   to consider  the impact on  the route reflectors,  and whether it  will be
>   necessary to add  new route reflectors, perhaps ones  dedicated to the new
>   family.  One should also consider the impact (especially on the RRs) which
>   one address family  may have on another, e.g.,  will an unexpectedly large
>   amount  of churn  due  to PIM  cause  a slowdown  in  the unicast  routing
>   convergence.  There should be some discussion of this.
> 
> - Transactional nature of PIM
> 
>   At first glance,  it may seem that having  PIM distribute multicast routes
>   to BGP is no different than  having OSPF distribute unicast routes to BGP,
>   i.e., that it is really  nothing new.  However, this isn't quite accurate.
>   The issue  is that PIM isn't really  a "routing protocol" in  the sense of
>   choosing  routes  based   on  topology.   It  is  a   protocol  that  uses
>   router-to-router  transactions  to construct  paths  and  assign flows  to
>   paths. In  some cases, especially when  Sparse Mode flows  are involved, a
>   number of  transactions involving  multiple nodes may  need to  take place
>   before the multicast "routing" stabilizes.  Each one of these transactions
>   must  pass through  the RR,  placing more  load on  the RR  and increasing
>   latency.
> 
>   In  some  cases, where  PIM-SM  has  data-driven  state changes,  we  have
>   attempted  to avoid  putting the  data-driven state  changes into  BGP, by
>   having BGP send extra  messages, including timer-driven messages.  While I
>   tend to think that this is the right tradeoff, it does modify the dynamics
>   of path construction,  and we don't have any hard data  to tell us whether
>   we've made the right tradeoff,  or whether the "right tradeoff" depends on
>   just how the applications are using multicast.
>   
> - Strange uses of PIM
> 
>   Talk  to  anyone  with a  lot  of  experience  in  PIM deployment  in  the
>   enterprise, and you'll hear lots of  strange stories about how PIM is used
>   in some enterprises.   Although PIM is optimized for  "many receivers, few
>   sources", it isn't always used  that way.  I've also heard anecdotes about
>   applications that make assumptions about the dynamic nature of PIM and may
>   break if  anything changes.   As usual,  hard data is  hard to  find.  But
>   there's always a risk that when you change the infrastructure underneath a
>   crufty old application you will break the application.  There are people I
>   respect, with  much more experience  in multicast deployment than  I have,
>   who think it's  just foolish to do anything that changes  the way in which
>   the infrastructure behaves for sparse mode.  While I am not convinced that
>   they are  right, I think that  this does have  to be recognized as  a risk
>   element.
> 
> Now let's look at some of the topics covered in the draft.
> 
> 1. From section 3.1, "the operational burden of setting up multicast on a PE
>    or for a VR/VRF SHOULD be as low as possible".
> 
>    I certainly  agree with  this!  However, I  don't think it  combines well
>    with the  later recommendation to support outsourced  RPs.  Obviously the
>    use of outsourced RPs increases the operational burden for the provider.
> 
>    I  note that  there doesn't  seem to  be any  requirement for  making the
>    operational burden  of MVPN on the  SP's customer be as  low as possible,
>    though such a requirement is  prominent in another SP requirements draft,
>    viz.,  draft-mnapierala-mvpn-part-reqt-00.txt.  Such a  requirement would
>    see to  militate against  the use  of the "outsourced  RP", at  least for
>    MVPN customers who already use  multicast.  (Which I imagine would be the
>    vast majority of them.)
> 
> 2. Auto-discovery
> 
>    "BGP-based  auto-discovery is the  preferred solution  for auto-discovery
>    ...  while  PIM/shared-tree  based  auto-discovery should  be  optionally
>    considered for migration purposes only".
> 
>    There isn't  really a  dichotomy here.  The  facts are that  if PIM-based
>    shared  trees  are  used,  BGP-based auto-discovery  doesn't  really  add
>    anything,  but in  any  other circumstance,  BGP-based auto-discovery  is
>    absolutely necessary.
> 
>    But  if the recommendation  here is  to provide  BGP-based auto-discovery
>    even in the one case where  it isn't strictly needed, I certainly support
>    that recommendation.  This  is, in fact, already true  of the majority of
>    existing MVPN  deployments.  (Though  I have been  told that there  is at
>    lest one vendor which does not support it in existing deployments.)
> 
>    There is a suggestion in the  draft that if PIM-based shared trees are in
>    use, BGP auto-discovery can  help detect misconfigurations.  I'm not sure
>    about that, as I can imagine  transition scenarios in which more than one
>    shared tree is in use at some time.
> 
> 3. Number of protocols
> 
>    "if any additional protocols are introduced compared with the unicast VPN
>    service,  the  balance between  their  advantage  and operational  burden
>    SHOULD be examined thoroughly"
> 
>    Well, who  could disagree with that?   The pros/cons of  any new protocol
>    should always be  examined thoroughly.  In fact, the  pros/cons of adding
>    new  functionality  to  existing  protocols  should  always  be  examined
>    thoroughly  as well.   As  should  the pros/cons  of  adding new  address
>    families, new procedures,  new dynamics, new events and  states, etc., to
>    existing protocols.
> 
>    It is better to focus on the overall complexity of the system, and on the
>    overall  behavior  of  the system,  than  just  to  count the  number  of
>    protocols. 
> 
> 4. S-PMSI Signaling
> 
>    The BGP-based S-PMSI  signaling mechanism does have a  risk factor that I
>    have mentioned above, but that is not considered in the draft
> 
>    In current practice,  BGP changes are caused by  topology changes, not by
>    end  user  activity.   However,   it  is  enduser  activity  that  causes
>    invocation of the S-PMSI signaling  mechanism.  We simply do not have the
>    data at  the present time  to determine how  much this will  increase the
>    amount of churn  in BGP.  The S-PMSI signaling is  also something that is
>    best done through a low latency  mechanism, and we do not at present have
>    the data to determine whether BGP will significantly increase the latency
>    when compared with the UDP-based proposal.
> 
>    In theory,  the use of BGP  S-PMSI signaling has a  number of advantages,
>    but I  don't think  I would  recommend against the  use of  the UDP-based
>    procedure unless and until I had some data about these pragmatic issues.
> 
>    By the  way, when I  say "data", I  don't mean "strongly held  and loudly
>    voiced  opinions", even  though the  latter are  sometimes  confused with
>    data.
> 
>    "The  UDP-based protocol  is  restricted  to use  within  MVPNs using  an
>    MI-PMSI".
> 
>    This fact seems to me to be  neither here nor there.  It is true that the
>    UDP-based protocol is unlikely to be useful unless PIM is the C-multicast
>    routing control protocol, in which case  you have an MI-PMSI.  If you are
>    using  BGP as  the C-multicast  routing protocol,  then you  have already
>    determined that you don't care if BGP churn is caused by enduser events.
> 
>    The UDP-based S-PMSIs signaling is best considered as an optional part of
>    the  PIM C-multicast  routing control  plane, rather  than as  a separate
>    protocol with its own independent set of pros and cons.
> 
>    "the  use  of  the  UDP-based  protocol  does  not  preserve  AS  routing
>     independence  when  used in  an  inter-AS  option  B context  (i.e.  the
>     decision by  a PE in an  AS to use an  S-PMSI for a  given customer flow
>     will impact routing state in other ASes)
> 
>    I  have no  idea what  this means,  so I  hope one  of the  authors will
>    explain.   (I also  don't  know what  is  meant by  the  claim that  the
>    BGP-based S-PMSI signaling  mechanism doesn't have whatever disadvantage
>    this is.)
> 
> 5. Off-loading processing onto route reflector
> 
>    The claim is made that, when using BGP to carry C-multicast routes, "some
>    of  the processing burden  associated with  client multicast  routing [is
>    offloaded] onto BGP route reflectors"
> 
>    I  would  like the  authors  to  specify  precisely what  this  offloaded
>    processing burden is.  Some consideration of its effect on existing L3VPN
>    route reflector systems would also be worthwhile.
> 
>    As the  text is now, it is  very difficult to understand  or evaluate the
>    claim.
> 
> 6. MI-PMSI issues
> 
>    "Moreover, mechanisms one and two are restricted to use within MVPNs
>    using an MI-PMSI, thereby necessitating:
> 
>    a.  The use of a P-multicast tree technique that allows shared trees
>        (for example PIM-SM in ASM mode or MP2MP LDP).
> 
>    b.  The use of one P-multicast tree per PE per VPN, even for PEs that
>        do not have sources in their directly attached sites for that
>        VPN."
> 
>    First,  claim b  is  not true,  as  explained in  draft-rosen-l3vpn-mvpn-
>    profiles-00.txt, section 3.3.
> 
>    Second, the fact that a control  protocol requires that it be possible to
>    instantiate a P-tunnel as a shared tree  of some sort does not seem to be
>    to be  a "restriction" or disadvantage.   You might as well  say that the
>    use  of  BGP  for  C-multicast  routing has  the  disadvantage  of  being
>    "restricted"  to those networks  whose route  reflectors support  the BGP
>    C-multicast routing address family.
> 
>    There are however some other things  that do seem to require the presence
>    of an MI-PMSI:   autoRP and BSR.  Since many  SP customers use autoRP/BSR
>    to discover  RPs, and since  it is not  clear how to provide  support for
>    these without an  MI-PMSI, I am not convinced that one  can do without an
>    MI-PMSI even if BGP is used for distributing C-multicast routes.
> 
> 
> 7. BGP doesn't eliminate PIM anyway
>    
>    "using BGP for customer routing distribution within multicast VPNs avoids
>    the introduction of an  additional protocol that would require additional
>    OAM processes and tools."
> 
>    It's not as if  PIM is eliminated by BGP.  As long as  PIM is used on the
>    PE/CE links, the SP is still operating a PIM environment.  In fact, there
>    may be significant  scaling problems due to PE-CE  PIM.  Some people with
>    years of PIM  experience believe that the PE-CE  PIM scaling problems are
>    actually worse  than the PE-PE PIM  scaling problems, and  hence that the
>    attempt  to improve PE-PE  scaling by  using BGP  just attacks  the wrong
>    problem. 
> 
>    In the absence of  actual data, the risk is that you  end up adding a lot
>    of NEW stuff and don't even address the scaling bottlenecks.
>  
>    In  any  event, I'm  not  sure  I understand  how  adding  a  lot of  new
>    functionality  to BGP  (multicast  path  creation) is  going  to be  done
>    without the need for additional OAM processes and tools.
> 
> 8. Consistency with unicast control mechanisms.
> 
>    "An illustrative example of the benefit brought by consistency with
>    unicast design is how the "extranet" feature can be implemented :
>    when BGP-based mechanisms are used, the well defined and well
>    understood BGP route target import/export semantics are just reused."
> 
>    This seems like a red  herring.  Extranet capability is already supported
>    in  the field  today  by existing  MVPN  deployments based  on PIM.   The
>    primary impact is really on the auto-discovery phase, not the C-multicast
>    routing phase.
> 
> 9. Encapsulation techniques
> 
>     I notice that  there is one particular data plane  technique that is not
>     addressed  by the  document, viz.,  the use  of ingress  replication and
>     transmission through  unicast tunnels.  It would be  interesting to know
>     whether SPs  have interest in this  technology; if not, maybe  it can be
>     removed from the  drafts.  (I think it adds  complexity and frankly, I'm
>     not sure it's fully and properly specified.)
> 
>     I think section 3.4 can be taken as a requirement for both a "BGP + GRE"
>     profile  and a  "PIM +  MPLS" profile,  since it  seems to  advocate for
>     independence between the the control  plane and the data plane.  But I'm
>     not sure if that is what is intended, and would like clarification.
> 
>     I would like  to see a specific recommendation for  the support of MP2MP
>     LSPs,  given their  importance in  C-bidir support  (for  either control
>     plane, see draft-ietf-l3vpn-2547bis-  mcast-05.txt, section 12.2) and in
>     general MPLS  multicast support  for the PIM  control plane  (see draft-
>     rosen-l3vpn-mvpn-profiles-00.txt, section 3.3).
> 
> 10. Upstream-Assigned Labels, MI-PMSI, and Scalability
>    
>     The  WG drafts frequently  discuss aggregation,  and the  possibility of
>     aggregation is frequently touted as a major scalability advantage.
> 
>     What isn't always clear is  that all forms of S-PMSI aggregation require
>     a  major   new  MPLS  feature,   upstream-assigned  labels.   Supporting
>     upstream-assigned labels requires significant  changes to the data plane
>     processing  of  many  different  platforms,  and is  not  likely  to  be
>     available for some period of time.
> 
>     So realistically, for  the foreseeable future, the use  of an MI-PMSI is
>     going  to remain  the  only  method of  aggregation.   Unless a  service
>     provider does not care if their  P-routers have to maintain an amount of
>     multicast state  which is proportional to  the sum of the  states of all
>     their customers, the service provider should be requiring support for an
>     MI-PMSI. 
> 
>     As  a further  note,  it should  be  pointed out  that inter-AS  segment
>     S-PMSIs are on a per-PE basis, not a per-AS basis.  Therefore without the
>     aggregation that  can be obtained  from upstream-assigned labels,  it is
>     not clear that segmented inter-AS  S-PMSIs are scalable at all.  This is
>     an issue which should be mentioned.
> 
>     I think the draft should have a clear recommendation that in the absence
>     of upstream-assigned MPLS labels, MI-PMSIs should be used.
> 
> 11. Outsourced RPs
> 
>     I  would like  to see  the  draft offer  much stronger  support for  its
>     recommendation to  implement outsourced RPs,  or else to  eliminate that
>     recommendation. 
> 
>     Outsourced RPs  (i.e., PE  as RP) have  a number of  disadvantages which
>     need to be given more emphasis:
> 
>     - More work  for the PE (do  many SPs really want  to give a  lot of new
>       work to their PEs)?
> 
>     - Not  likely to  be  of much  interest  to customers  with an  existing
>       multicast infrastructure
> 
>     - Require  increased coordination  between SP  and  enterprise customer,
>       such as agreement on RP (or RPL) addresses.
>     
>     - Not completely clear  how this works in scenarios  where an enterprise
>       gets VPN  service from two different providers,  particularly if there
>       is a site multihomed to two different providers.
> 
>     I presume  that the extra  operational work for  SP and customer  is not
>     going to be justified by the  fact that it simplifies things for some of
>     the SP's vendors.
> 
> 
> 12. The draft's conclusion
> 
>    "Consequently, at the present time and until there is experience with
>    all of the proposed mechanisms it is not clear which of the above
>    mechanisms should be recommended as the preferred solution to
>    implementers.  However, it would appear prudent for implementations
>    to consider supporting both the fourth (BGP-based) and first (full
>    per-MPVN PIM peering) mechanisms.  Further experience on both
>    implementation is likely to be required before some best practice can
>    be defined."
> 
>    I certainly agree with this  conclusion.  Perhaps it should be given more
>    prominence. 
> 
> 13. My conclusion
> 
>     While  I do  think this  draft may  be a  good start  on the  project of
>     comparing the  different MVPN options, I  don't think it is  ready to be
>     adopted as a WG document, and it  needs a lot more work to deal with the
>     issues I have raised in this note.
> 
>     I  also hope  it  is clearly  understood  that this  document should  be
>     evaluated by the same criteria as any other internet-draft, i.e., by its
>     technical quality.
> 
>     
> 
> 
>     
> 
>  
> 
> 





From l3vpn-bounces@ietf.org Fri Dec 14 11:53:49 2007
Return-path: <l3vpn-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1J3DmS-0006Pp-Es; Fri, 14 Dec 2007 11:52:56 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1J3DmR-0006Pk-KM
	for l3vpn@ietf.org; Fri, 14 Dec 2007 11:52:55 -0500
Received: from p-mail2.rd.francetelecom.com ([195.101.245.16])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1J3DmQ-0002w9-E3
	for l3vpn@ietf.org; Fri, 14 Dec 2007 11:52:55 -0500
Received: from ftrdmel10.rd.francetelecom.fr ([10.193.117.156]) by
	ftrdsmtp2.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 14 Dec 2007 17:52:50 +0100
Received: from [10.193.15.109] ([10.193.15.109]) by
	ftrdmel10.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 14 Dec 2007 17:52:50 +0100
From: Thomas Morin <thomas.morin@orange-ftgroup.com>
To: erosen@cisco.com
In-Reply-To: <10989.1197649183@erosen-linux>
References: <10989.1197649183@erosen-linux>
Content-Type: text/plain
Organization: France Telecom R&D - Orange
Date: Fri, 14 Dec 2007 17:52:49 +0100
Message-Id: <1197651169.4979.112.camel@wintermute>
Mime-Version: 1.0
X-Mailer: Evolution 2.12.2 
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 14 Dec 2007 16:52:50.0233 (UTC)
	FILETIME=[C2E8EA90:01C83E71]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: bf422c85703d3d847fb014987125ac48
Cc: Yakov Rekhter <yakov@juniper.net>, l3vpn@ietf.org
Subject: Re: Comments on draft-morin-l3vpn-mvpn-considerations-01.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>
Errors-To: l3vpn-bounces@ietf.org

Hi Eric,

Eric Rosen :
> I think Yakov's  reply makes it pretty clear that  adoption of this document
> as a WG document at the current time is premature.
> 
> I was  prepared for someone to  say that the  issues I raised can  be worked
> after the  document is accepted.  However,  we see from  Yakov's answer that
> he,  at least,  wants to  suppress discussion  of all  the  remaining issues
> (after all, they're  all FUD ;-)).  
[...]
> In fairness, Yakov isn't one of the  authors of the document, so it
> would be interesting to know whether the authors  of the document
> agree that there is no need to discuss any of the issues I've raised.

Please let me restate that the intent indeed is to rationally treat all
issues that can help make recommandations on the preferred approaches.

> I didn't think my reputation in this WG was that of a FUD-provider, but YMMV ;-)

What is sure is that, for some of the points you raised, it will be
useful to have more facts and/or explanations so that we can cover them
in our document.

Have a good week-end,

-Thomas



> For the kind of document that draft-morin seems to be, I think it is the job
> of the authors to investigate all  the issues, not to say "we won't consider
> any issue until some  else proves beyond a shadow of a  doubt that there's a
> real problem".  Of  course, I'll be happy to work with  the authors to flesh
> out  all the  arguments  pro and  con.  I'm  not  trying to  prove that  the
> BGP-based scheme won't  work, but I'd have thought  that everyone knows that
> all proposals have  pros and cons; a "considerations"  document should bring
> out all the issues.
> 

> A few of the more outrageous comments do require some reply:
> 
> > why should the draft talk about this [variety of factors for which we lack
> > hard data] since facts are scarce ?
> 
> Any choice  which is based  on opinion  rather than facts  is a risk,  and a
> "considerations"  document should certainly  make it  clear when  such risks
> exist.
> 
> > Moreover since PIM is based on unreliable message exchange, "join latency"
> > with PIM could be in 10s of seconds.
> 
> The worst  case join latency in  either case could be  arbitrarily long, but
> I'm sure everyone knows ((well, almost everyone ;-)) that's it's the average
> join latency that is important.  Since packets don't usually get lost in the
> backbone, that's  not much of  an issue.   I don't think  it takes a  lot of
> fancy analysis  to determine  that it's  faster to send  a data  packet from
> point A  to point B then  to send it from  point A to  an intermediate point
> where it  is processed and then afterwards  sent along to point  C.  One can
> argue  that the  latency increase  isn't significant,  or that  it's  a good
> tradeoff  against something  else,  but it's  just  silly to  deny that  the
> latency increase exists!
> 
> > could  please  quantify  "significantly"  as  you assert  that  "BGP  will
> > significantly increase the latency".
> 
> I did  not state that  BGP will significantly  increase the latency,  I said
> that we  do not have  the data to  determine whether BGP  will significantly
> increase the latency.
> 
> A "significant  increase" would be one  that causes a visible  effect to the
> users of a multicast-based application.
> 
> >  "Dampening of  withdrawals [as opposed to updates]  of C-multicast routes
> >   does not impede the multicast join latency observed by MVPN customers,"
> 
> Sure, but  it doesn't have the same  effect on churn reduction  as does join
> dampening, and it has other side-effects as well.  This is certainly an area
> that would benefit from more analysis in any "considerations" document.
> 
> > Since you are a co-author on that draft, you should be aware of this.
> 
> I'm glad  you remembered that I'm  a co-conspirator (err,  co-author) of the
> BGP-based multicast control plane.  As  a co-author, I am familiar with lots
> of  issues  that  might  not  necessarily  be  obvious  to  the  authors  of
> draft-morin.  Further,  I appear  to be the  only co-author who  thinks that
> both  BGP and  PIM have  merits, and  that it  is important  to do  a pretty
> thorough and unbiased comparison.
> 
> > As for the last "effect on existing L3VPN route reflector systems",
> > please note the the following text in Section 15 of
> > draft-ietf-l3vpn-2547bis-mcast-bgp:
> 
> >   Moreover, Route Reflectors used for MVPN do not have to be 
> >   used for VPN-IP routes
> 
> > And as a reminder, you are a co-author on that draft !
> 
> Yes, I am well aware that you  can add new RRs expressly to handle multicast
> routes.  In  a "considerations" document, the  need (or lack of  need) to do
> this is one of the considerations  that should be discussed.  Unless the SPs
> are willing to say up front "not to worry, we don't care how many additional
> RRs we need, they come for free and do not increase our operational burden".
> 
> As you know, I am a big fan of the 2547 technology :-), but the issue of how
> the VPN-IP routes affect BGP generally (and how much "BGP churn" they cause)
> has  always  been with  us.   At  least VPN-IP  routes  do  not behave  much
> differently than  IP routes, since  updates are still triggered  by topology
> changes and  not by  enduser activity.  MVPN  introduces a different  set of
> dynamics to BGP and the impact on  the rest of the BGP system is certainly a
> consideration that needs to be better understood.
> 
> It is fair  to point out that additional BGP activity  is at least partially
> compensated for by reduced PIM activity.  On the other hand, PIM activity 
> doesn't impact the BGP system, so this comparison is not straightforward.
> 
> > In fact, can you explain why having one architecture for unicast
> > VPN (aggregated routing) and another architecture for multicast VPN
> > (virtual routers) is any better than having the same architecture
> > for both unicast and multicast VPN ?
> 
> I  think the  choice between  the two  schemes should  be based  not  on the
> elegance of  the architecture but on  the multitude of  facts that determine
> (a) how well the multicast applications in the enterprise will be supported,
> and (b) how much operational impact they have on the SP.  
> 
> Further, multicast  routing is  really a very  different thing  than unicast
> routing, and  there is  no history of  success in  combining the two  into a
> single architecture (e.g., MOSPF).
> 
> This is  not to say  that BGP is  a poor choice, but  just to explain  why I
> don't  think that  the  uniformity  of the  architecture  is the  overriding
> considerations. 
> 
> > First of all, autoRP is a cisco proprietary technology. Asking
> > standards to support cisco proprietary technology is inappropriate.
> 
> If  an enterprise  is using  proprietary technology,  and if  a SP  wants to
> provide MVPN service to that enterprise,  then I think the SP will certainly
> want to know whether he has to  tell the enterprise "no MVPN service for you
> until you change your deployed technologies" ;-)
> 
> A large number of enterprises use Cisco technology, and I imagine that other
> vendors would like to be able to provide PEs that support those enterprises.
> 
> > supporting BSR without  MI-PMSI has been explained in  the presentation at
> > the  L3VPN  WG  meeting  (with  you  as one  of  the  co-authors  on  that
> > presentation).
> 
> Many of  the presentations  we've given over  the years  presented solutions
> which  turned out  to  be  unsatisfactory.  Certainly  the  support or  lack
> thereof  for  BSR  is  something  that a  "considerations"  document  should
> examine.
> 
> >> realistically, for  the foreseeable future, the use  of an MI-PMSI is
> >>     going  to remain  the  only  method of  aggregation.
> 
> > Do you speak just for cisco, or for all other vendors as well ?
> 
> I would highly recommend that before eliminating the MI-PMSI, the SPs should
> get solid  delivery dates from  their vendors for  upstream-assigned labels!
> ;-)
> 
> >> it is not clear that segmented inter-AS  S-PMSIs are scalable at all.
> 
> > Are they less scalable than non-segmented inter-AS S-PMSIs ?
> 
> In my mind, the issue is whether there's a real good inter-provider solution
> at all. 
> 
> > If less work for the PEs is the goal, then one should not run 2547 VPNs,
> 
> Well, I'd like to hear the SPs  say that they don't care how much additional
> work  the PEs  have to  do!  Or  that they  don't care  how  much additional
> coordination they have  to do with their customers, or  that they don't care
> how many  changes the customers  have to make  before they can buy  the SPs'
> service. 
> 
> > the recommendations should  reflect position of SPs, not  vendors (and you
> > are part of the latter, not the former).
> 
> I've yet to hear any SP say that they don't want my input because I work for
> a  vendor.  If  any  do  feel that  way,  I'm sure  they  can  speak up  for
> themselves.
> 
> 
> 
> 
> 





From l3vpn-bounces@ietf.org Fri Dec 14 11:59:33 2007
Return-path: <l3vpn-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1J3Dru-0001YD-Tg; Fri, 14 Dec 2007 11:58:34 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1J3Drt-0001Y0-Bj
	for l3vpn@ietf.org; Fri, 14 Dec 2007 11:58:33 -0500
Received: from colt-na7.alcatel.fr ([62.23.212.7] helo=smail6.alcatel.fr)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1J3Drs-00033n-BE
	for l3vpn@ietf.org; Fri, 14 Dec 2007 11:58:33 -0500
Received: from FRVELSBHS05.ad2.ad.alcatel.com (frvelsbhs05.ad2.ad.alcatel.com
	[155.132.6.77])
	by smail6.alcatel.fr (8.13.4/8.13.4/ICT) with ESMTP id lBEGsKoe008877; 
	Fri, 14 Dec 2007 17:56:52 +0100
Received: from FRVELSMBS22.ad2.ad.alcatel.com ([155.132.6.52]) by
	FRVELSBHS05.ad2.ad.alcatel.com with Microsoft
	SMTPSVC(6.0.3790.2499); Fri, 14 Dec 2007 17:58:27 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 14 Dec 2007 17:58:18 +0100
Message-ID: <8144761F31F48D43AD53D09F5350E3800237BF87@FRVELSMBS22.ad2.ad.alcatel.com>
In-Reply-To: <200712141421.lBEEL5E13758@magenta.juniper.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: draft-morin-l3vpn-mvpn-considerations 
Thread-Index: Acg+XKOxcS81YXSJTeGW3yWxZ+VbwwAAGxbg
References: Your message of "Fri, 14 Dec 2007 14:49:27 +0100."
	<8144761F31F48D43AD53D09F5350E3800237BDD3@FRVELSMBS22.ad2.ad.alcatel.com>
	<200712141421.lBEEL5E13758@magenta.juniper.net>
From: "PAPADIMITRIOU Dimitri" <Dimitri.Papadimitriou@alcatel-lucent.be>
To: "Yakov Rekhter" <yakov@juniper.net>
X-OriginalArrivalTime: 14 Dec 2007 16:58:27.0311 (UTC)
	FILETIME=[8BD2EFF0:01C83E72]
X-Scanned-By: MIMEDefang 2.51 on 155.132.188.84
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 995b2e24d23b953c94bac5288c432399
Cc: l3vpn@ietf.org
Subject: RE: draft-morin-l3vpn-mvpn-considerations 
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>
Errors-To: l3vpn-bounces@ietf.org


 yakov,

> -----Original Message-----
> From: Yakov Rekhter [mailto:yakov@juniper.net]=20
> Sent: Friday, December 14, 2007 3:21 PM
> To: PAPADIMITRIOU Dimitri
> Cc: Ron Bonica; l3vpn@ietf.org
> Subject: Re: draft-morin-l3vpn-mvpn-considerations=20
>=20
> Dimitri,
>=20
> > hi ron, all
> >=20
> > the document should focus on a solid analysis/description before
> > concluding with (strong) recommendations that are=20
> prescriptive and this,
> > at an early stage of the analysis.
> >=20
> > here below a specific example to show that this analytical=20
> phase is not
> > completed to draw such conclusions/recommendations:
> >=20
> > "By contrast, experience proves that PIM-based mechanisms are
> > operationally viable, but with well identified limitations.  Some of
> > those limitations may be improved upon (although there is=20
> currently no
> > clearly defined proposal to do this), however some of the=20
> limitations
> > appear to be intrinsic to the approach."
> >=20
> > there are stated limitations but which limitations ? and to=20
> which extend
> > (all protocols developed by the IETF have certain limitations what.
> > matters is whether or not they are impacting in the interval of the
> > protocol operations and how degradations are impacting=20
> outside of this
> > interval)=20
>=20
> Read section 3.3 of draft-morin-l3vpn-mvpn-considerations,
> as it covers the issues you mentioned above.

not possible to miss it. the problems i see are:

o) that exerpt from that section 3.3 reads

"BGP-based customer multicast routing clearly presents some advantages
   over the PIM-based alternatives.  However it has yet to be deployed
   within an operational MVPN, and service providers currently lack
   experience of its implementation.  By contrast, experience proves
   that PIM-based mechanisms are operationally viable, but with well
   identified limitations.  Some of those limitations may be improved
   upon (although there is currently no clearly defined proposal to do
   this), however some of the limitations appear to be intrinsic to the
   approach."

it is a general conclusion, meaning that either you detail "some"
limitations or you state the same for BGP that also comes with "some"
limitations (generic statements are to be used uniformly)

o) section 3.3 limits itself to a base analysis of the B interconnection
model and capabilities offered by PIM. for inst. it is not clear why one
would not consider PIM in combination with per AS-tree segmentation.

that section states there are robustness issues observed in PIM (if i
well understand because the section just refers to communication ?) but
do what do you define as robustness in the present case to come at the
conclusion reached that section ?=20

that section states that there are security issues in PE-to-PE
communication - well i think that in any inter-AS exchange you will have
security issues anyway - the base point is that before concluding
anything specific on security it would be appropriate to complete the
analysis on security and document trade-offs in intermediate in data and
routing protocol exchanges for mVPN.

o) an approach may necessitate a specific mechanism. but this is not a
limitation. this is a confusion that occurs many times in that specific
section. if authors want to describe the additional mechanisms needed
one should agree about starting points/RFCs.

> > more interestingly, the statement ack's they may be=20
> elevated but since
> > these limitations are stated to "appear as" intrinsic to=20
> the approach
> > and so they can not be elevated ? if this is the case where=20
> is the proof
> > for such statement ?
> >=20
> > in general also, i suggest that authors keep protocol capabilities
> > analysis and consolidate their argumentation from feedback=20
> obtained on
> > the field as long as BGP-based approaches do not benefit=20
> from experience
> > on the field. indeed, in its current form, the document reads as
> > comparing disadvantages of experimental / deployment=20
> experience gained
> > from PIM wrt to theoretical expectations/advantages from=20
> new BGP-based
> > standards.
>=20
> The document compares different *technologies*, and makes=20
> recommendations
> based on such comparison. Such comparison reflects underlying
> properties/characteristics of these technologies. Since these are
> the properties/characteristics of the technologies, these
> properties/characteristics do not depend on whether these technologies
> are deployed or not.

what i ask is to keep comparison at the same level. do not use
experimental experience to draw observation that are compared with
"theoretical" technological properties (having said this it is not
obvious without further analysis that the introdcution of multicast/mvpn
into BGP other than discovery would be verified)

> > =3D> conclusions/recommendations need to be based on solid and fair
> > arguments enough to be perceived as truly prescriptive for=20
> driving the
> > protocol work and subsequent decisions of the working=20
> group. if these
> > conclusions/recommendation keep changing on per version=20
> basis (because
> > not complete or balanced enough) the document will miss its target.
> >=20
> > imho, we have two solutions:
> >=20
> > - either the document states that it is at an "early stage"=20
> of ongoing
> > investigation and removes statements that are, at this=20
> point in time,
> > interpretable and/or leading to early conclusions/=20
> recommendations or
> > alike. hence, it can then become a WG document after re-spin. such
> > conclusions would be incorporated at final stage of analysis.=20
> >=20
> > - or if the document wants to maintain its current=20
> conclusions it needs
> > to re-inforce and complete its argumentation/analysis. in that case
> > however, it is not ready in its current form to become now a working
> > group doc.
>=20
> While one may argue that the argumentation/analysis is not perfect,
> it is good enough for the draft to be accepted as an L3VPN WG
> document. The argumentation/analysis could be perfected after
> the document is accepted, and it would reflect the L3VPN WG
> consensus.

this would read to me: agree on the conclusions before having a
sufficient level of confidence on the analysis itself.

-d.
> Yakov.
>=20
> >=20
> > -d.
> >=20
> > > -----Original Message-----
> > > From: Ron Bonica [mailto:rbonica@juniper.net]=20
> > > Sent: Monday, December 10, 2007 10:11 PM
> > > To: l3vpn@ietf.org
> > > Subject: draft-morin-l3vpn-mvpn-considerations
> > >=20
> > > Folks,
> > >=20
> > > Unless I hear an objection before COB Friday, this document=20
> > > will become
> > > a WG draft.
> > >=20
> > >                                       Ron
> > >=20
> > >=20
> >=20
> >=20
>=20




From l3vpn-bounces@ietf.org Fri Dec 14 12:57:46 2007
Return-path: <l3vpn-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1J3EmG-0000Xd-Vm; Fri, 14 Dec 2007 12:56:48 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1J3EmF-0000X1-Db
	for l3vpn@ietf.org; Fri, 14 Dec 2007 12:56:47 -0500
Received: from rtp-iport-2.cisco.com ([64.102.122.149])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1J3EmE-0003le-RV
	for l3vpn@ietf.org; Fri, 14 Dec 2007 12:56:47 -0500
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by rtp-iport-2.cisco.com with ESMTP; 14 Dec 2007 12:56:46 -0500
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13])
	by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id lBEHuk0j025211; 
	Fri, 14 Dec 2007 12:56:46 -0500
Received: from erosen-linux.cisco.com (erosen-linux.cisco.com [161.44.70.34])
	by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id
	lBEHugZG029271; Fri, 14 Dec 2007 17:56:42 GMT
Received: from erosen-linux (localhost.localdomain [127.0.0.1])
	by erosen-linux.cisco.com (8.13.1/8.13.1) with ESMTP id lBEHufCN012330; 
	Fri, 14 Dec 2007 12:56:41 -0500
To: Thomas Morin <thomas.morin@orange-ftgroup.com>
In-reply-to: Your message of Fri, 14 Dec 2007 17:43:40 +0100.
	<1197650620.4979.103.camel@wintermute> 
Date: Fri, 14 Dec 2007 12:56:41 -0500
Message-ID: <12329.1197655001@erosen-linux>
From: Eric Rosen <erosen@cisco.com>
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1094; t=1197655006;
	x=1198519006; c=relaxed/simple; s=rtpdkim1001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=erosen@cisco.com;
	z=From:=20Eric=20Rosen=20<erosen@cisco.com>
	|Subject:=20Re=3A=20Comments=20on=20draft-morin-l3vpn-mvpn-
	considerations-01.txt=20 |Sender:=20
	|To:=20Thomas=20Morin=20<thomas.morin@orange-ftgroup.com>;
	bh=tRSBP9O64LAZEmctR3wn0I+T3UK4/LsjI8e2c02aZuQ=;
	b=cJXM/hiyzxa5ksmlHLCUgQDb1cZo5KuwRLD3otg+JzIryxShXA/jr/3vz+
	A+fFjYHiKUj9MFrfheSz/FQWakx1kTdGE2HxAlq2OGuA5sH7TNPVN14O92ZN
	N0zr50w/wZ;
Authentication-Results: rtp-dkim-1; header.From=erosen@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim1001 verified; ); 
X-Spam-Score: -4.0 (----)
X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2
Cc: erosen@cisco.com, l3vpn@ietf.org
Subject: Re: Comments on draft-morin-l3vpn-mvpn-considerations-01.txt 
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: erosen@cisco.com
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>
Errors-To: l3vpn-bounces@ietf.org


> if adoption of a work by a working group was requiring having finished the
> doc, then adoption as WG item and Last Call could be made at the same
> time, right ?  ;-)

Absolutely.  But it  would be nice if there were some  agreement on just how
much more work it needs.

Until we've had  a fuller discussion on  which of my concerns do  and do not
need to  be addressed,  it's hard  to judge whether  the authors  are really
willing to  take this document in  the right direction.  That's  why I would
like to delay adopting it as a WG document.  

> we  should  focus on  facts-driven  considerations  that help  distinguish
> relative merits on different options

I thought that was the point I was making.  There are just too many areas in
which  the  relevant facts  are  either not  known  or  not considered.   If
decisions are being made based on assumptions or opinions rather than facts,
that should certainly be called out.

> So, night is coming and I'll get back to thinking about buying christmas
> gifts and follow up on this next week.

Fair enough!












From l3vpn-bounces@ietf.org Fri Dec 14 14:44:43 2007
Return-path: <l3vpn-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1J3GRq-00025F-0L; Fri, 14 Dec 2007 14:43:50 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1J3GRo-00021H-S0
	for l3vpn@ietf.org; Fri, 14 Dec 2007 14:43:48 -0500
Received: from exprod7og104.obsmtp.com ([64.18.2.161])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1J3GRo-0007yI-4V
	for l3vpn@ietf.org; Fri, 14 Dec 2007 14:43:48 -0500
Received: from source ([66.129.224.36]) by exprod7ob104.postini.com
	([64.18.6.12]) with SMTP; Fri, 14 Dec 2007 11:43:21 PST
Received: from magenta.juniper.net ([172.17.27.123]) by emailsmtp55.jnpr.net
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 14 Dec 2007 11:43:20 -0800
Received: from sapphire.juniper.net (sapphire.juniper.net [172.17.28.108])
	by magenta.juniper.net (8.11.3/8.11.3) with ESMTP id lBEJhKE87610;
	Fri, 14 Dec 2007 11:43:20 -0800 (PST)
	(envelope-from rahul@juniper.net)
Date: Fri, 14 Dec 2007 11:43:20 -0800 (PST)
From: Rahul Aggarwal <rahul@juniper.net>
To: Eric Rosen <erosen@cisco.com>
In-Reply-To: <10989.1197649183@erosen-linux>
Message-ID: <20071214105427.K92685@sapphire.juniper.net>
References: <10989.1197649183@erosen-linux>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-OriginalArrivalTime: 14 Dec 2007 19:43:20.0524 (UTC)
	FILETIME=[94A370C0:01C83E89]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a87a9cdae4ac5d3fbeee75cd0026d632
Cc: Yakov Rekhter <yakov@juniper.net>, l3vpn@ietf.org
Subject: Re: Comments on draft-morin-l3vpn-mvpn-considerations-01.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>
Errors-To: l3vpn-bounces@ietf.org


Hi Eric,

First, to me the goal of draft-morin is to provide a set of
mandatory and optional, options (from the set of options in
draft-ietf-l3vpn-2547bis-mcast) that would allow SPs to deploy
inter-operable implementations using technology/options that the *SPs
want*.

This is a very important excercise for the L3VPN WG to progress on the
MVPN subject. draft-morin IMO is an excellent start towards this
excercise. It should be adopted as a WG document and can evolve to address
*valid concerns*.

And valid concerns do not include philosophical arguments.
Unfortunately several of your concerns were philosphical in nature and do
not help with constructive progress.

More below:

On Fri, 14 Dec 2007, Eric Rosen wrote:

>
> I think Yakov's  reply makes it pretty clear that  adoption of this document
> as a WG document at the current time is premature.
>

On the contrary it shows that draft-morin is quite ready to become a WG
document ! I think his reply separates your valid concerns from the ones that are not
valid. And proves that the set of valid concerns is a) addressable and b)
can be addressed after WG adoption.

Let me repeat here what is the set of valid concerns that you seem to
have:

"Of the issues raised by you in the above the only legitimate ones
seems to be (a) more analysis on different flavor of multicast LSPs,
(b) whether there is a need for BGP-based auto-discovery with
PIM-based shared trees, and (c) whether the UDP-based S-PMSIs
signaling should be best considered as an optional part of the  PIM
C-multicast  routing control  plane.  All of these issues can be
addressed after the document gets adopted as a WG draft."


> I was  prepared for someone to  say that the  issues I raised can  be worked
> after the  document is accepted.  However,  we see from  Yakov's answer that
> he,  at least,  wants to  suppress discussion  of all  the  remaining issues
> (after all, they're  all FUD ;-)).

Yakov in his email asked you several specific questions. I don't
call that "supress discussion". If you have reasonable answers to have a
constructive discussion on those subjects, please speak up. Else it just
demonstrates that several of your points called out as FUD were indeed FUD
(or to put more politely philosophical) !

> For the kind of document that draft-morin seems to be, I think it is the job
> of the authors to investigate all  the issues, not to say "we won't consider
> any issue until some  else proves beyond a shadow of a  doubt that there's a
> real problem".

The discussion of the issues has to be grounded in *rational technical
arguments* put forth by SPs to guide the set of mandatory/optional
options.

>
> > Moreover since PIM is based on unreliable message exchange, "join latency"
> > with PIM could be in 10s of seconds.
>
> The worst  case join latency in  either case could be  arbitrarily long, but
> I'm sure everyone knows ((well, almost everyone ;-)) that's it's the average
> join latency that is important.

Try telling that to a SP who has an important financial feed that needs
*predictable* join latency.

>  Since packets don't usually get lost in the
> backbone, that's  not much of  an issue.   I don't think  it takes a  lot of
> fancy analysis  to determine  that it's  faster to send  a data  packet from
> point A  to point B then  to send it from  point A to  an intermediate point
> where it  is processed and then afterwards  sent along to point  C.  One can
> argue  that the  latency increase  isn't significant,  or that  it's  a good
> tradeoff  against something  else,  but it's  just  silly to  deny that  the
> latency increase exists!
>

There doesn't seem to be any technical argument on why the average join
latency will increase. The average has to take into account the worst case
latency, and the latency of first join and subsequent joins (which
is lesser than the latency of the first join).

> > supporting BSR without  MI-PMSI has been explained in  the presentation at
> > the  L3VPN  WG  meeting  (with  you  as one  of  the  co-authors  on  that
> > presentation).
>
> Many of  the presentations  we've given over  the years  presented solutions
> which  turned out  to  be  unsatisfactory.  Certainly  the  support or  lack
> thereof  for  BSR  is  something  that a  "considerations"  document  should
> examine.
>

To me this falls in the category of which multicast LSP flavor to choose.
And this can be done after the document becomes a WG document.

rahul




From l3vpn-bounces@ietf.org Fri Dec 14 15:07:45 2007
Return-path: <l3vpn-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1J3Go6-0001td-CB; Fri, 14 Dec 2007 15:06:50 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1J3Go4-0001qO-T1
	for l3vpn@ietf.org; Fri, 14 Dec 2007 15:06:48 -0500
Received: from exprod7og106.obsmtp.com ([64.18.2.165])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1J3Go4-0007Uv-GE
	for l3vpn@ietf.org; Fri, 14 Dec 2007 15:06:48 -0500
Received: from source ([66.129.224.36]) by exprod7ob106.postini.com
	([64.18.6.12]) with SMTP; Fri, 14 Dec 2007 12:06:47 PST
Received: from magenta.juniper.net ([172.17.27.123]) by emailsmtp56.jnpr.net
	with Microsoft SMTPSVC(6.0.3790.3959); 
	Fri, 14 Dec 2007 12:04:53 -0800
Received: from sapphire.juniper.net (sapphire.juniper.net [172.17.28.108])
	by magenta.juniper.net (8.11.3/8.11.3) with ESMTP id lBEK4rE92588;
	Fri, 14 Dec 2007 12:04:53 -0800 (PST)
	(envelope-from rahul@juniper.net)
Date: Fri, 14 Dec 2007 12:04:53 -0800 (PST)
From: Rahul Aggarwal <rahul@juniper.net>
To: Ronald Bonica <rbonica@juniper.net>
In-Reply-To: <51661468CBD1354294533DA79E85955A082004@XCH-SW-5V2.sw.nos.boeing.com>
Message-ID: <20071214115925.P92685@sapphire.juniper.net>
References: <475DAB80.7010900@juniper.net>
	<51661468CBD1354294533DA79E85955A082004@XCH-SW-5V2.sw.nos.boeing.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-OriginalArrivalTime: 14 Dec 2007 20:04:53.0504 (UTC)
	FILETIME=[97508800:01C83E8C]
X-Spam-Score: -4.0 (----)
X-Scan-Signature: 52e1467c2184c31006318542db5614d5
Cc: l3vpn@ietf.org
Subject: RE: draft-morin-l3vpn-mvpn-considerations
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>
Errors-To: l3vpn-bounces@ietf.org


Hi Ron,

I strongly support adopting this document as a WG draft.

To me the goal of draft-morin is to provide a set of
mandatory and optional, options (from the set of options in
draft-ietf-l3vpn-2547bis-mcast) that would allow SPs to deploy
inter-operable implementations using technology/options that the *SPs
want*.

This is a very important excercise for the L3VPN WG to progress on the
MVPN subject. draft-morin IMO is an excellent start towards this
excercise. It should be adopted as a WG document and can evolve to address
areas that require further work.

rahul


> >-----Original Message-----
> >From: Ron Bonica [mailto:rbonica@juniper.net]
> >Sent: Monday, December 10, 2007 1:11 PM
> >To: l3vpn@ietf.org
> >Subject: draft-morin-l3vpn-mvpn-considerations
> >
> >Folks,
> >
> >Unless I hear an objection before COB Friday, this document
> >will become a WG draft.
> >
> >                                      Ron
> >
> >
>
>
>




From l3vpn-bounces@ietf.org Fri Dec 14 15:40:06 2007
Return-path: <l3vpn-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1J3HJM-0003yI-Pi; Fri, 14 Dec 2007 15:39:08 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1J3HJL-0003yC-6B
	for l3vpn@ietf.org; Fri, 14 Dec 2007 15:39:07 -0500
Received: from exprod7og106.obsmtp.com ([64.18.2.165])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1J3HJK-00008Q-Rq
	for l3vpn@ietf.org; Fri, 14 Dec 2007 15:39:07 -0500
Received: from source ([66.129.224.36]) by exprod7ob106.postini.com
	([64.18.6.12]) with SMTP; Fri, 14 Dec 2007 12:39:05 PST
Received: from magenta.juniper.net ([172.17.27.123]) by emailsmtp56.jnpr.net
	with Microsoft SMTPSVC(6.0.3790.3959); 
	Fri, 14 Dec 2007 12:38:07 -0800
Received: from zircon.juniper.net (zircon.juniper.net [172.17.28.113])
	by magenta.juniper.net (8.11.3/8.11.3) with ESMTP id lBEKc7E01480;
	Fri, 14 Dec 2007 12:38:07 -0800 (PST)
	(envelope-from lenny@juniper.net)
Received: from zircon.juniper.net (localhost [127.0.0.1])
	by zircon.juniper.net (8.12.11/8.12.3) with ESMTP id lBEKc7ap053928;
	Fri, 14 Dec 2007 12:38:07 -0800 (PST)
	(envelope-from lenny@juniper.net)
Received: from localhost (lenny@localhost)
	by zircon.juniper.net (8.12.11/8.12.3/Submit) with ESMTP id
	lBEKc7uU053923; Fri, 14 Dec 2007 12:38:07 -0800 (PST)
X-Authentication-Warning: zircon.juniper.net: lenny owned process doing -bs
Date: Fri, 14 Dec 2007 12:38:06 -0800 (PST)
From: Leonard Giuliano <lenny@juniper.net>
To: Ron Bonica <rbonica@juniper.net>
In-Reply-To: <20071214123516.V50822@zircon.juniper.net>
Message-ID: <20071214123546.T50822@zircon.juniper.net>
References: <20071214123516.V50822@zircon.juniper.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-OriginalArrivalTime: 14 Dec 2007 20:38:07.0684 (UTC)
	FILETIME=[3BF04040:01C83E91]
X-Spam-Score: -4.0 (----)
X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f
Cc: l3vpn@ietf.org
Subject: draft-morin-l3vpn-mvpn-considerations
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>
Errors-To: l3vpn-bounces@ietf.org


I support adoption of this draft by L3VPN and think it provides useful 
guidance.


-) ---------- Forwarded message ----------
-) Date: Mon, 10 Dec 2007 16:11:28 -0500
-) From: Ron Bonica <rbonica@juniper.net>
-) To: l3vpn@ietf.org
-) Subject: draft-morin-l3vpn-mvpn-considerations
-) 
-) Folks,
-) 
-) Unless I hear an objection before COB Friday, this document will become
-) a WG draft.
-) 
-)                                       Ron
-) 




From l3vpn-bounces@ietf.org Fri Dec 14 16:48:47 2007
Return-path: <l3vpn-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1J3INt-0004qb-Cp; Fri, 14 Dec 2007 16:47:53 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1J3INs-0004qR-B7
	for l3vpn@ietf.org; Fri, 14 Dec 2007 16:47:52 -0500
Received: from mail121.messagelabs.com ([216.82.241.195])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1J3INr-0003YE-Vn
	for l3vpn@ietf.org; Fri, 14 Dec 2007 16:47:52 -0500
X-VirusChecked: Checked
X-Env-Sender: mnapierala@att.com
X-Msg-Ref: server-10.tower-121.messagelabs.com!1197668870!22366251!1
X-StarScan-Version: 5.5.12.14.2; banners=-,-,-
X-Originating-IP: [144.160.20.54]
Received: (qmail 24765 invoked from network); 14 Dec 2007 21:47:50 -0000
Received: from sbcsmtp7.sbc.com (HELO mlpi135.enaf.sfdc.sbc.com)
	(144.160.20.54)
	by server-10.tower-121.messagelabs.com with AES256-SHA encrypted SMTP;
	14 Dec 2007 21:47:50 -0000
Received: from enaf.sfdc.sbc.com (localhost.localdomain [127.0.0.1])
	by mlpi135.enaf.sfdc.sbc.com (8.14.0/8.14.0) with ESMTP id
	lBELloT6000863; Fri, 14 Dec 2007 16:47:50 -0500
Received: from kcclust06evs1.ugd.att.com (kcst11.ugd.att.com [135.38.164.88])
	by mlpi135.enaf.sfdc.sbc.com (8.14.0/8.14.0) with ESMTP id
	lBELldhK000814; Fri, 14 Dec 2007 16:47:45 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 14 Dec 2007 15:47:39 -0600
Message-ID: <7AFE40EF30EE754DA967D1B5968457CA1381BF9D@KCCLUST06EVS1.ugd.att.com>
In-Reply-To: <20071214123546.T50822@zircon.juniper.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: draft-morin-l3vpn-mvpn-considerations
Thread-Index: Acg+kX+CO25W4aw3Rt6id3PE97nZ2AACKqnA
References: <20071214123516.V50822@zircon.juniper.net>
	<20071214123546.T50822@zircon.juniper.net>
From: "NAPIERALA, MARIA H, ATTLABS" <mnapierala@att.com>
To: "Ron Bonica" <rbonica@juniper.net>, <l3vpn@ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb
Cc: 
Subject: RE: draft-morin-l3vpn-mvpn-considerations
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>
Errors-To: l3vpn-bounces@ietf.org

The draft is a very good start but there are still some outstanding
mandatory design aspects that need to be addressed:=20
- support of non-static RP solutions like BSR. There are current large
MVPNs in SP network that use BSR
- support of "PIM-like" Anycast-RP by allowing multiple RP's to send
traffic in parallel=20
- the recommended approach for a source PE to decide when to start
transmitting customer multicast traffic on a S-PMSI (namely, the source
PE waits for a pre-configured period of time) is not satisfactory in my
opinion. A different approach is proposed in
draft-mnapierala-mvpn-rev-03
- what is still missing in this draft as well as in RFC4834 is the
requirement to support PIM Bidir on CE-PE links. This requirement is
coming, e.g., from large financial firms for which using PIM-SM for
certain business critical applications does not scale. Not to mention
the SP :-))

Also, I would suggest that "co-located RP" recommendation is removed
from the document. Co-locating C-RP on PE should not be positioned as a
mandatory mechanism in MVPN, which this draft is addressing.

Sorry for late comments. I might have comments but wanted to send those
COB today.=20

Maria=20

-) ---------- Forwarded message ----------
-) Date: Mon, 10 Dec 2007 16:11:28 -0500
-) From: Ron Bonica <rbonica@juniper.net>
-) To: l3vpn@ietf.org
-) Subject: draft-morin-l3vpn-mvpn-considerations
-)=20
-) Folks,
-)=20
-) Unless I hear an objection before COB Friday, this document will
become
-) a WG draft.
-)=20
-)                                       Ron
-)=20





From l3vpn-bounces@ietf.org Fri Dec 14 17:21:18 2007
Return-path: <l3vpn-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1J3ItJ-0002yd-3B; Fri, 14 Dec 2007 17:20:21 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1J3ItH-0002wa-6W
	for l3vpn@ietf.org; Fri, 14 Dec 2007 17:20:19 -0500
Received: from mail120.messagelabs.com ([216.82.250.83])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1J3ItG-0004M7-M7
	for l3vpn@ietf.org; Fri, 14 Dec 2007 17:20:19 -0500
X-VirusChecked: Checked
X-Env-Sender: mnapierala@att.com
X-Msg-Ref: server-9.tower-120.messagelabs.com!1197670813!28406811!1
X-StarScan-Version: 5.5.12.14.2; banners=-,-,-
X-Originating-IP: [144.160.20.54]
Received: (qmail 16423 invoked from network); 14 Dec 2007 22:20:16 -0000
Received: from sbcsmtp7.sbc.com (HELO mlpi135.enaf.sfdc.sbc.com)
	(144.160.20.54)
	by server-9.tower-120.messagelabs.com with AES256-SHA encrypted SMTP;
	14 Dec 2007 22:20:16 -0000
Received: from enaf.sfdc.sbc.com (localhost.localdomain [127.0.0.1])
	by mlpi135.enaf.sfdc.sbc.com (8.14.0/8.14.0) with ESMTP id
	lBEMKCdI019449; Fri, 14 Dec 2007 17:20:13 -0500
Received: from kcclust06evs1.ugd.att.com (kcst11.ugd.att.com [135.38.164.88])
	by mlpi135.enaf.sfdc.sbc.com (8.14.0/8.14.0) with ESMTP id
	lBEMK71f019410; Fri, 14 Dec 2007 17:20:08 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 14 Dec 2007 16:20:07 -0600
Message-ID: <7AFE40EF30EE754DA967D1B5968457CA1381BFA6@KCCLUST06EVS1.ugd.att.com>
In-Reply-To: <7AFE40EF30EE754DA967D1B5968457CA1381BF9D@KCCLUST06EVS1.ugd.att.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: draft-morin-l3vpn-mvpn-considerations
Thread-Index: Acg+kX+CO25W4aw3Rt6id3PE97nZ2AACKqnAAAE3TbA=
References: <20071214123516.V50822@zircon.juniper.net>
	<20071214123546.T50822@zircon.juniper.net>
	<7AFE40EF30EE754DA967D1B5968457CA1381BF9D@KCCLUST06EVS1.ugd.att.com>
From: "NAPIERALA, MARIA H, ATTLABS" <mnapierala@att.com>
To: "Ron Bonica" <rbonica@juniper.net>, <l3vpn@ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7aafa0432175920a4b3e118e16c5cb64
Cc: 
Subject: RE: draft-morin-l3vpn-mvpn-considerations
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>
Errors-To: l3vpn-bounces@ietf.org

Ron,
I would like that those issues are addressed before this draft is
adopted as a WG document since addressing those issues might impact
other recommendations stated in the draft.

Maria

-----Original Message-----
From: NAPIERALA, MARIA H, ATTLABS=20
Sent: Friday, December 14, 2007 4:48 PM
To: 'Ron Bonica'; 'l3vpn@ietf.org'
Subject: RE: draft-morin-l3vpn-mvpn-considerations

The draft is a very good start but there are still some outstanding
mandatory design aspects that need to be addressed:=20
- support of non-static RP solutions like BSR. There are current large
MVPNs in SP network that use BSR
- support of "PIM-like" Anycast-RP by allowing multiple RP's to send
traffic in parallel=20
- the recommended approach for a source PE to decide when to start
transmitting customer multicast traffic on a S-PMSI (namely, the source
PE waits for a pre-configured period of time) is not satisfactory in my
opinion. A different approach is proposed in
draft-mnapierala-mvpn-rev-03
- what is still missing in this draft as well as in RFC4834 is the
requirement to support PIM Bidir on CE-PE links. This requirement is
coming, e.g., from large financial firms for which using PIM-SM for
certain business critical applications does not scale. Not to mention
the SP :-))

Also, I would suggest that "co-located RP" recommendation is removed
from the document. Co-locating C-RP on PE should not be positioned as a
mandatory mechanism in MVPN, which this draft is addressing.

Sorry for late comments. I might have comments but wanted to send those
COB today.=20

Maria=20

-) ---------- Forwarded message ----------
-) Date: Mon, 10 Dec 2007 16:11:28 -0500
-) From: Ron Bonica <rbonica@juniper.net>
-) To: l3vpn@ietf.org
-) Subject: draft-morin-l3vpn-mvpn-considerations
-)=20
-) Folks,
-)=20
-) Unless I hear an objection before COB Friday, this document will
become
-) a WG draft.
-)=20
-)                                       Ron
-)=20





From l3vpn-bounces@ietf.org Mon Dec 17 07:18:30 2007
Return-path: <l3vpn-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1J4Eua-0002FD-4o; Mon, 17 Dec 2007 07:17:32 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1J4EuZ-0002F8-9t
	for l3vpn@ietf.org; Mon, 17 Dec 2007 07:17:31 -0500
Received: from smtp4.smtp.bt.com ([217.32.164.151])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1J4EuX-0000KC-Oz
	for l3vpn@ietf.org; Mon, 17 Dec 2007 07:17:31 -0500
Received: from E03MVY1-UKDY.domain1.systemhost.net ([193.113.30.60]) by
	smtp4.smtp.bt.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 17 Dec 2007 12:17:46 +0000
Received: from 217.32.164.172 ([217.32.164.172]) by
	E03MVY1-UKDY.domain1.systemhost.net ([193.113.30.114]) via
	Exchange Front-End Server mail.bt.com ([193.113.197.86]) with
	Microsoft Exchange Server HTTP-DAV ; Mon, 17 Dec 2007 12:17:43 +0000
User-Agent: Microsoft-Entourage/11.2.1.051115
Date: Mon, 17 Dec 2007 12:17:23 +0000
From: Ben Niven-Jenkins <benjamin.niven-jenkins@bt.com>
To: Thomas Morin <thomas.morin@orange-ftgroup.com>,
	<erosen@cisco.com>
Message-ID: <C38C1953.3E5%benjamin.niven-jenkins@bt.com>
Thread-Topic: Comments on draft-morin-l3vpn-mvpn-considerations-01.txt
Thread-Index: AchApscmBYnr7KyaEdyypAAbY64lKQ==
In-Reply-To: <1197650620.4979.103.camel@wintermute>
Mime-version: 1.0
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit
X-OriginalArrivalTime: 17 Dec 2007 12:17:46.0603 (UTC)
	FILETIME=[D53813B0:01C840A6]
X-Spam-Score: 1.6 (+)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
Cc: l3vpn@ietf.org
Subject: Re: Comments on draft-morin-l3vpn-mvpn-considerations-01.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>
Errors-To: l3vpn-bounces@ietf.org

On 14/12/07 16:43, "Thomas Morin" <thomas.morin@orange-ftgroup.com> wrote:
> I think we would be, all co-authors of this document, happy to make
> clarifications to address your comments.  There are definitely some
> areas where content can be improved to be more precise on the pros/cons
> of the different approaches. It is precisely the kind of feedback we
> asked.

Fully agree, as co-author I welcome any comments on the draft and we can
work towards incorporating those.
 
> But in the end, given the support of the working group I would not
> expect the improvements to be made as requiring delaying the adoption of
> the draft by the working group, since it seems that we agree on the
> intent, structure and general direction of the document.

I also agree that the comments so far should not prevent the draft from
becoming a WG draft as I believe the draft to provide useful guidance to the
WG and the current solutions draft(s).

Ben

Sent using the Microsoft Entourage 2004 for Mac Test Drive.





From l3vpn-bounces@ietf.org Mon Dec 17 08:48:28 2007
Return-path: <l3vpn-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1J4GJd-0007Kq-Kz; Mon, 17 Dec 2007 08:47:29 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1J4GJd-0007Kl-3Y
	for l3vpn@ietf.org; Mon, 17 Dec 2007 08:47:29 -0500
Received: from exprod7og110.obsmtp.com ([64.18.2.173])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1J4GJc-00080e-I7
	for l3vpn@ietf.org; Mon, 17 Dec 2007 08:47:29 -0500
Received: from source ([66.129.224.36]) by exprod7ob110.postini.com
	([64.18.6.12]) with SMTP; Mon, 17 Dec 2007 05:47:22 PST
Received: from magenta.juniper.net ([172.17.27.123]) by emailsmtp56.jnpr.net
	with Microsoft SMTPSVC(6.0.3790.3959); 
	Mon, 17 Dec 2007 05:46:26 -0800
Received: from juniper.net (sapphire.juniper.net [172.17.28.108])
	by magenta.juniper.net (8.11.3/8.11.3) with ESMTP id lBHDkQE93684;
	Mon, 17 Dec 2007 05:46:26 -0800 (PST)
	(envelope-from yakov@juniper.net)
Message-Id: <200712171346.lBHDkQE93684@magenta.juniper.net>
To: "NAPIERALA, MARIA H, ATTLABS" <mnapierala@att.com>
In-Reply-To: Your message of "Fri, 14 Dec 2007 16:20:07 CST."
	<7AFE40EF30EE754DA967D1B5968457CA1381BFA6@KCCLUST06EVS1.ugd.att.com> 
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <45706.1197899186.1@juniper.net>
Date: Mon, 17 Dec 2007 05:46:26 -0800
From: Yakov Rekhter <yakov@juniper.net>
X-OriginalArrivalTime: 17 Dec 2007 13:46:26.0908 (UTC)
	FILETIME=[385E31C0:01C840B3]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 02ec665d00de228c50c93ed6b5e4fc1a
Cc: l3vpn@ietf.org
Subject: Re: draft-morin-l3vpn-mvpn-considerations 
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>
Errors-To: l3vpn-bounces@ietf.org

Maria,

> Ron,
> I would like that those issues are addressed before this draft is
> adopted as a WG document since addressing those issues might impact
> other recommendations stated in the draft.

The issues you brought up below are outside the scope of
draft-morin-l3vpn-mvpn-considerations, and therefore should not be
covered/addressed by draft-morin-l3vpn-mvpn-considerations.

See in-line for more...

> Maria
> 
> -----Original Message-----
> From: NAPIERALA, MARIA H, ATTLABS 
> Sent: Friday, December 14, 2007 4:48 PM
> To: 'Ron Bonica'; 'l3vpn@ietf.org'
> Subject: RE: draft-morin-l3vpn-mvpn-considerations
> 
> The draft is a very good start but there are still some outstanding
> mandatory design aspects that need to be addressed: 
> - support of non-static RP solutions like BSR. There are current large
> MVPNs in SP network that use BSR

Please keep in mind that draft-morin-l3vpn-mvpn-considerations is
about examining different proposed alternative mechanisms *as
documented in L3VPN WG documents*, not about specifying missing
pieces in these document.

I certainly agree that support for BSR has to be documented in one
of the L3VPN WG documents  (either draft-ietf-l3vpn-2547bis-mcast
or draft-ietf-l3vpn-2547bis-mcast-bgp).

> - support of "PIM-like" Anycast-RP by allowing multiple RP's to send
> traffic in parallel 

See my previous comment.

> - the recommended approach for a source PE to decide when to start
> transmitting customer multicast traffic on a S-PMSI (namely, the source
> PE waits for a pre-configured period of time) is not satisfactory in my
> opinion. A different approach is proposed in
> draft-mnapierala-mvpn-rev-03

See my previous comment.

> - what is still missing in this draft as well as in RFC4834 is the
> requirement to support PIM Bidir on CE-PE links. This requirement is
> coming, e.g., from large financial firms for which using PIM-SM for
> certain business critical applications does not scale. Not to mention
> the SP :-))

See my previous comment. Also, draft-morin-l3vpn-mvpn-considerations
is based on the requirements as specified in rfc4834.

If you want to change rfc4834, then this has to be discussed on its own,
and should not impact progress of draft-morin-l3vpn-mvpn-considerations.

Yakov.




From l3vpn-bounces@ietf.org Mon Dec 17 17:18:42 2007
Return-path: <l3vpn-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1J4OII-0002jB-Iu; Mon, 17 Dec 2007 17:18:38 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1J4OIH-0002j6-RR
	for l3vpn@ietf.org; Mon, 17 Dec 2007 17:18:37 -0500
Received: from p-mail2.rd.francetelecom.com ([195.101.245.16])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1J4OIG-0003TV-5U
	for l3vpn@ietf.org; Mon, 17 Dec 2007 17:18:37 -0500
Received: from ftrdmel10.rd.francetelecom.fr ([10.193.117.156]) by
	ftrdsmtp1.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 17 Dec 2007 23:18:11 +0100
Received: from [127.0.0.1] ([10.193.4.45]) by ftrdmel10.rd.francetelecom.fr
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 17 Dec 2007 23:18:33 +0100
From: Thomas Morin <thomas.morin@orange-ftgroup.com>
To: L3VPN <l3vpn@ietf.org>
In-Reply-To: <17617.1197470041@erosen-linux>
References: <17617.1197470041@erosen-linux>
Content-Type: text/plain
Organization: France Telecom R&D - Orange
Date: Mon, 17 Dec 2007 22:38:43 +0100
Message-Id: <1197927524.4927.409.camel@wintermute>
Mime-Version: 1.0
X-Mailer: Evolution 2.12.2 
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 17 Dec 2007 22:18:34.0207 (UTC)
	FILETIME=[C343EEF0:01C840FA]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4adaf050708fb13be3316a9eee889caa
Cc: Eric Rosen <erosen@cisco.com>
Subject: Re: Comments on draft-morin-l3vpn-mvpn-considerations-01.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>
Errors-To: l3vpn-bounces@ietf.org

Hi Eric, working group,

I already extensively replied to Eric's comments, some of which seem to
me indeed as calling for relevant updates/additions to our draft, but I
want to highlight an answer to one specific comment...

Eric Rosen :
>
> 11. Outsourced RPs
>
>     I  would like  to see  the  draft offer  much stronger  support
>     for  its recommendation to  implement outsourced RPs,  or else to 
>     eliminate that recommendation.
[snip]
> 
>     Outsourced RPs  (i.e., PE  as RP) have  a number of  disadvantages which
>     need to be given more emphasis: [...]
>
>     I presume  that the extra  operational work for  SP and customer  is not
>     going to be justified by the  fact that it simplifies things for some of
>     the SP's vendors.

Everybody having read the draft can see that it actually not only say
that the RP-colocation feature is useful but also that an implementation
should _not_ require using this feature.  So, Eric, your underlying
suggestion that co-authors of mvpn-considerations state that "the
outsourced-RP feature should be implemented" to to simplify things for
some particular vendor(s) is really ridiculous.

If this is the kind of plot you have in mind, the amount of opposition
you have to mvpn-considerations becoming a working group document is in
fact not surprising !  ;)

But I think the working group support to this work shows that not
everybody has such conspiracy theories in mind, and that many people
understand that operators have just a sincere interest in trying to
identify a best candidate for becoming a standard (vs. a set of
"profiles").   If you happen to disagree with this perspective, then it
would be nice to hear you say that it is the main reason for you
opposition, that will spare a few photos and electrons of l3vpn mailing
list traffic !

Thanks,

-Thomas





From l3vpn-bounces@ietf.org Mon Dec 17 17:18:43 2007
Return-path: <l3vpn-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1J4OIM-0002ks-Vu; Mon, 17 Dec 2007 17:18:42 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1J4OIL-0002jR-D5
	for l3vpn@ietf.org; Mon, 17 Dec 2007 17:18:41 -0500
Received: from p-mail2.rd.francetelecom.com ([195.101.245.16])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1J4OIH-00031Q-OS
	for l3vpn@ietf.org; Mon, 17 Dec 2007 17:18:41 -0500
Received: from ftrdmel10.rd.francetelecom.fr ([10.193.117.156]) by
	ftrdsmtp1.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 17 Dec 2007 23:18:09 +0100
Received: from [127.0.0.1] ([10.193.4.45]) by ftrdmel10.rd.francetelecom.fr
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 17 Dec 2007 23:18:31 +0100
From: Thomas Morin <thomas.morin@orange-ftgroup.com>
To: Eric Rosen <erosen@cisco.com>, L3VPN <l3vpn@ietf.org>
In-Reply-To: <17617.1197470041@erosen-linux>
References: <17617.1197470041@erosen-linux>
Content-Type: text/plain
Organization: France Telecom R&D - Orange
Date: Mon, 17 Dec 2007 22:27:17 +0100
Message-Id: <1197926837.4927.395.camel@wintermute>
Mime-Version: 1.0
X-Mailer: Evolution 2.12.2 
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 17 Dec 2007 22:18:32.0270 (UTC)
	FILETIME=[C21C5EE0:01C840FA]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ce33913643759a19ac4c14fdbab27ca9
Cc: 
Subject: Re: Comments on draft-morin-l3vpn-mvpn-considerations-01.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>
Errors-To: l3vpn-bounces@ietf.org

Hi Eric,

Following my reply on yesterday, I'll try to go in detail through your
comments and see what are the points that I think could be better
covered in draft-mvpn-considerations.

* First, some of your comments shows that there is much confusion
related to the theme of "what new is put into BGP vs. what PIM does /
what BGP does new that PIM was/wasn't doing". I admit I would have
expected a co-author of the solution drafts to actually clear up that
kind of confusion, but let's focus on what can be done in
mvpn-considerations to improve everybody's understanding : I propose we
add a section detailing what is done by PIM in the Full PIM peering
approach (both the case where explicit tracking is done by upstream PEs,
and the case where Join suppression is made) and what is done by BGP in
the BGP approach, on the PE and on the RRs. We won't try to compare
things quantitatively, but I think spelling out the details can help
shed light on the general debate of the relative merits of PIM and BGP
to carry C-multicast routing information.  (see below, in reply to your
"transactional nature of PIM", a rough cut of the things we can explain
to help evaluate how the multicast routing processing is spread onto the
different entities).

* On the general theme of BGP routing activity due to C-multicast route
and route reflectors : you are right in saying the document could talk
more about it. I think we can incorporate content explaining that moving
some processing from PIM to BGP will require adjusting the route
reflectors infrastructure by whether by increasing route reflector
processing resources and taking care of not badly impacting unicast
routes (e.g. distinct BGP sessions), or more likely by introducing
distinct route reflectors for mVPN.  We can also talk about the tools to
control the impact of end user activity to the amount of processing done
by the control plane (leave dampening, join dampening, impact of join
dampening on join latency).

* About join latency : for sure minimizing join latency can be important
for some specific applications and I agree we should talk about it. As
said earlier, I think the draft should use fact-based arguments and here
the facts that can be talked about is that the C-multicast routing join
latency relative performance in the BGP and PIM cases, will depend on
BGP performance of the PE and RR(s) relatively compared to PE PIM
processing performance on the PEs, and also on the network latency that
will be added at each processing "hop" (one in the case of PIM, one, two
or more in the case of BGP). All these performance aspects being to
consider in both the low scale space and the higher scale space, since
both PIM and BGP approaches can be expected to be differently impacted
by higher scale scenarios, for join-latency. Last, I think we should
state that absolute performance figure in the end depend on
implementations.

* On outsourcing the RP : the draft currently basically says that the
feature has applicability and should be implemented, but that in no way
it should be required to enable it (and we do mention drawbacks similar
to those you insisted upon).  This section needs some improvement : as
suggested by Yiqun Cai during the meeting, we don't exactly distinguish
between the two role associated with the "RP" label in such a context --
PIM register decapsulation and RP routing function vs.
Anycast-RP-related functions.  We plan to update this section in this
sense, then if you have precise comments on stuff that we
should/shouldn't talk about, please make them (see below inlined, I
didn't really understood what you disagree with in the current text).

* Remark about using BGP autodiscovery to detect misconfigurations, and
the fact it may not be helpful in transitions scenarios : I agree, and I
think we can definitely mention this in an updated version.

* On Extranet : the current text we propose is only saying that the BGP
approach for C-multicast routing reuses the RT import/export semantics
to define Extranet, to illustrate the benefits brought by using the same
protocol/semantics for unicast and multicast. You insist on reminding us
that an early implementation of the Full PIM peering approach do also
support this : if it also is a good illustration of reusing existing RT
import/export semantics, then we should also mention it for sure. The
fact is that Extranet for the Full PIM peering approach is not (yet?)
described in any spec (AFAIK).  So what I propose is that you first
point us toward a description of such a feature and (a) tell us if that
would be relevant to include in that section mentioning consistency
brought by the reuse of RT import/export semantics, and (b) we provide a
section trying to compare the relative merits of the different
approaches to provide an Extranet feature.

* On encapsulation techniques : as you suggest, we can highlight the
benefits of using MP2MP MPLS trees for facilitating the implementation
of some of the different proposed ways of supporting C-bidir-PIM. We can
certainly also explain how it would facilitate the support of the Full
PIM peering approach, but (see below inlined) I'm not sure I do yet
understand well what you suggest.  Another point (that you didn't
mention) is the expected scalability benefits of using MP2MP trees with
one MP2MP tree per VPN, we can also mention this.

* You highlight the fact that the scalability benefits brought by
aggregation of the traffic multiple VPNs in a PSMI-tunnel, requires the
support of upstream assigned labels : this is something that I'm not
against mentioning in the document, but I'm unsure how this will help
see which control plane approach is better than another one, since such
aggregation is supported whatever control plane approach you take...
(any idea ?)

* You make some comments related to S-PSMI scalability in inter-AS in
the segmented inter-AS model : there indeed were recent discussions
about among authors of draft-ietf-l3vpn-2547bis-mcast-bgp, which you and
me happen to be in, on possible improvements needed to make the
segmented approach better in this respect.  We will need to update
mvpn-considerations accordingly (this was in fact planned before your
comments, as mentioned in the slides presented in Vancouver). 

* BSR/auto-rp support : we can definitely tackle this point. It is true
that current specs for the BGP approach doesn't explain in detail how to
cover this.

Please tell us if you feel that the above proposed updates are relevant.
It seems to me that it integrates a fair amount of useful comments that
you made, and that can indeed make the document at the same time more
balanced and precise.


See inlined below, a few reactions I have on your comments.


Eric Rosen :
>
> - As BGP  is generally  used, BGP churn  is a  function of real  or apparent
>   topology changes.  BGP churn is NOT generally caused by enduser events.
> 
>   This changes when  BGP is used to distribute  multicast routes.  BGP churn
>   can now  be initiated by PIM  Joins, and a PIM  Join may be  the result of
>   some enduser clicking  a button on his PC (e.g.,  "receive video").  it is
>   not clear that there is any limit on the rate at which such enduser events
>   can occur.  We do not appear to  have adequate data from which we can draw
>   conclusions as to the impact of enduser actions on BGP churn.

Yes, as said above, I propose to add content in the draft to talk about
new routing to be taken care of by BGP. It also has to be said, to be
fair, that (a) BGP updates can be caused by routing events in customer
sites and that BGP has tools to cope with such things (such as
dampening) which can be reused for C-multicast routes and that (b) the
"input" to this processing problem is the same whatever control plane
approach is chosen.


[...]
> - Churn  vs. latency:  To  control the  BGP  churn, we  have discussed  such
>   features as  Join Dampening.   However, that can't  be expected to  have a
>   salutary effect on the latency!
> 
>   There really should  be some recognition in the draft  that the effects on
>   latency and churn are as yet poorly understood.

Well... do you deliberately chose to omit that what is first suggested
by the mvpn bgp solution draft (which you co-author!) is leave-dampening
and has no effect on join latency ? do you really honestly "poorly
understand" the effects of join-dampening on churn and latency ?

You are in fact spreading FUD through strawman here :
- "strawman" because nobody is saying "join dampening" should be
extensively be used, and "join dampening" is in no way a key argument in
the rest of the debate (_leave_ dampening is an important tool) 
- "FUD" because you use vague terms ("poorly understood") to suggest
that something is proposed without having well been thought out ; "join
dampening" is in fact not in this case. It has actually well identified
effects: good effect on "churn" (higher dampening => lower churn) and
impacts latency ("higher dampening" => "higher join latency for the
first receiver"). The solution drafts already formulate this limitation
of join dampening, and I don't think mvpn-consideration has to repeat
this.

So as formulated in the head of this mail: the key thing is "how control
plane copes with join/leave events ? what impact on latency ?", and we
can definitely talk about this.  But we will focus on constructive
points like looking at what tools are proposed for the different
approaches to cope/reduce this load. We can even go further and suggest
that, even though the Full PIM peering approach doesn't
document/proposes such features, join/leave dampening could also be
supported with slight changes to PIM implementations. 



> - Transactional nature of PIM
> 
>   At first glance,  it may seem that having  PIM distribute multicast routes
>   to BGP is no different than  having OSPF distribute unicast routes to BGP,
>   i.e., that it is really  nothing new.  However, this isn't quite accurate.

(let me point your use of a "strawman" argument here again : when did
anyone suggest it was the same ? doesn the mvpn-considerations draft
state anything like that ?)


> The issue  is that PIM isn't really  a "routing protocol" in  the sense of
>   choosing  routes  based   on  topology.   It  is  a   protocol  that  uses
>   router-to-router  transactions  to construct  paths  and  assign flows  to
>   paths. In  some cases, especially when  Sparse Mode flows  are involved, a
>   number of  transactions involving  multiple nodes may  need to  take place
>   before the multicast "routing" stabilizes.  Each one of these transactions
>   must  pass through  the RR,  placing more  load on  the RR  and increasing
>   latency.
>
>   In  some  cases, where  PIM-SM  has  data-driven  state changes,  we  have
>   attempted  to avoid  putting the  data-driven state  changes into  BGP, by
>   having BGP send extra  messages, including timer-driven messages.  While I
>   tend to think that this is the right tradeoff, it does modify the dynamics
>   of path construction,  and we don't have any hard data  to tell us whether
>   we've made the right tradeoff,  or whether the "right tradeoff" depends on
>   just how the applications are using multicast.


You are formulating things in a "PIM is transactional / BGP is not", but
I think that this formulation has two drawbacks:

- talking about the "transactional nature" of PIM, and "router to router
transactions" is in fact unprecise/bogus:
  * first, because on a LAN, PIM message are not send from "router to
router", but rather received AND processed by all PIM routers on the LAN
(they are sent to a multicast group address) -- this is true for Hellos,
Join, Leave, and assert messages -- in many case the processing made
will then be different depending on if the router is the upstream PE or
not for the said Join.
  * second, "translation" is a surprising term in fact : PIM messages
are not acknowledged in any way; they can be lost or unprocessed,
without the router at the origin of a message being aware ; that is, one
of the entity taking part into the "transaction" could be unaware that
the "transaction" didn't happen -- weird for a "transaction", right ?
(BGP being TCP-based, depending on what you mean by "transaction", you
could very much argue than BGP is in fact more "transactional"...)

- this formulation is really hiding one very important thing in how PIM
behaves on a LAN, to resolve the one question important for an upstream
router "is there still somebody needing such (C-s,C-g) across the
mvpn ?"

  * by default, PIM uses the "join suppression/prune override"mechanism,
    on a LAN : this mode help scaling PIM by reducing messaging, by two
    means:
      => when a router sends a Join for a said (s,g), other routers will
         omit sending theirs for some time, sparing each time a PIM Join
      => on reception of a Prune, the upstream router relies on other
         routers on the LAN to know if there are some PE left that need
         the steam 
     The downside of the above is that a PE router has to process all
   Joins sent on the LAN to know if it has to reset a timer or not for 
   Join suppression, and to all Prunes sent on the LAN to know whether
   or not it shall override the Prune.   This really not a "router to
   router" conversation.

[  * optionally, on a LAN, PIM can desactivate these mechanism, but only
  if all routers on a LAN are able to do so (detected through a Hello
  option), and obviously the benefits are lost : more messages will be
  exchanged, and more state has to be maintained (explicit tracking) by
  the upstream PE  // this approach is not pushed by anybody AFAIK  ]

- now, let's look at what BGP does (Eric, I know you know that
already!):

  * it finds a right trade-off between the two extremes possible with
PIM (between "everybody participates to see if there is any downstream
PE left" and "upstream PE does all the work by explicitly tracking who
are the downstream PEs") : the route reflectors are introduced, the set
of route reflectors carrying C-multicast routes for a said VPN virtually
collaborate to maintain the "count", the upstream PE is 100% relieved
from this processing/state effort, which burden is put on the route
reflector(s).  This means you have the tooling to adapt your
architecture to the work load : you can choose to use zero route
reflector (to minimize latency e.g. if you happen to have a specific use
case), or one route reflector, or a hierarchy of route reflectors... you
can choose to you partition the different VPNs to have them by treated
by specific route reflectors... you have _already_ existing tools to
handle the load in high scale scenarios.  None of this you can do with
PIM LAN procedures !

  * by nature (contrarily to PIM exchanges on a LAN by default) the
semantics of C-multicast route processing with the proposed BGP
extension are "router to router" : C-multicast routes are addressed to
one specific upstream router and BGP has the tooling required to respect
this semantic with RT-contraint (reused from unicast).



> - Strange uses of PIM
> 
>   Talk  to  anyone  with a  lot  of  experience  in  PIM deployment  in  the
>   enterprise, and you'll hear lots of  strange stories about how PIM is used
>   in some enterprises.   Although PIM is optimized for  "many receivers, few
>   sources", it isn't always used  that way.  I've also heard anecdotes about
>   applications that make assumptions about the dynamic nature of PIM and may
>   break if  anything changes.   As usual,  hard data is  hard to  find.  But
>   there's always a risk that when you change the infrastructure underneath a
>   crufty old application you will break the application.  There are people I
>   respect, with  much more experience  in multicast deployment than  I have,
>   who think it's  just foolish to do anything that changes  the way in which
>   the infrastructure behaves for sparse mode.  While I am not convinced that
>   they are  right, I think that  this does have  to be recognized as  a risk
>   element.

Interesting. You will certainly agree that there is not much we can say
based on so scarce information. Given the above, I would myself even
fear that the specifics of the use of PIM LAN procedures in the context
of draft-ietf-l3vpn-2547bis-mcast would have any side effect...

-> Why wasn't this suggested for incorporation in what is now RFC4834
(mvpn requirements) ?
-> Can you provide more data points and details on what are these
strange use of PIM ? (Or can (the) provider(s) having such use case give
more details ?)  It would be useful to let "the community" and
co-authors of mvpn-considerations evaluate what the limitations of the
BGP C-multicast routing proposal would be. 


> Now let's look at some of the topics covered in the draft.
> 
> 1. From section 3.1, "the operational burden of setting up multicast on a PE
>    or for a VR/VRF SHOULD be as low as possible".
> 
>    I certainly  agree with  this!  However, I  don't think it  combines well
>    with the  later recommendation to support outsourced  RPs.  Obviously the
>    use of outsourced RPs increases the operational burden for the provider.
> 
>    I  note that  there doesn't  seem to  be any  requirement for  making the
>    operational burden  of MVPN on the  SP's customer be as  low as possible,
>    though such a requirement is  prominent in another SP requirements draft,
>    viz.,  draft-mnapierala-mvpn-part-reqt-00.txt.  Such a  requirement would
>    see to  militate against  the use  of the "outsourced  RP", at  least for
>    MVPN customers who already use  multicast.  (Which I imagine would be the
>    vast majority of them.)


I already mentioned this in the head of my answer: the draft precisely
says that an implementation should not require activating an RP function
on the PE.   

        "...support for a co-located RP model within an implementation
        should not restrict deployments to using a co-located RP
        model,..."
        
What do you exactly disagree with ??


> 2. Auto-discovery
> 
>    "BGP-based  auto-discovery is the  preferred solution  for auto-discovery
>    ...  while  PIM/shared-tree  based  auto-discovery should  be  optionally
>    considered for migration purposes only".
> 
>    There isn't  really a  dichotomy here.  The  facts are that  if PIM-based
>    shared  trees  are  used,  BGP-based auto-discovery  doesn't  really  add
>    anything,  but in  any  other circumstance,  BGP-based auto-discovery  is
>    absolutely necessary.
> 
>    But  if the recommendation  here is  to provide  BGP-based auto-discovery
>    even in the one case where  it isn't strictly needed, I certainly support
>    that recommendation.  This  is, in fact, already true  of the majority of
>    existing MVPN  deployments.  (Though  I have been  told that there  is at
>    lest one vendor which does not support it in existing deployments.)
>
>   There is a suggestion in the  draft that if PIM-based shared trees are in
> use, BGP auto-discovery can  help detect misconfigurations.  I'm not sure
>    about that, as I can imagine  transition scenarios in which more than one
>    shared tree is in use at some time.

I see that we agree here. We can add consideration about limitations of
misconfiguration detection.



> 4. S-PMSI Signaling
> 
>    The BGP-based S-PMSI  signaling mechanism does have a  risk factor that I
>    have mentioned above, but that is not considered in the draft
> 
>    In current practice,  BGP changes are caused by  topology changes, not by
>    end  user  activity. However,   it  is  enduser  activity  that  causes
>    invocation of the S-PMSI signaling  mechanism.

( Come on Eric, why do you chose a formulation that suggest a dynamic
activity triggered by end-users, while we are talking about an optional
optimisation that can be fully controlled/enabled/disabled by the
provider without impacting the service ?  )


> [...]The S-PMSI signaling is  also something that is
>    best done through a low latency  mechanism, and we do not at present have
>    the data to determine whether BGP will significantly increase the latency
>    when compared with the UDP-based proposal.

I disagree : the time between "the condition for triggering a Data-MDT"
triggering Data-MDT being true" and "traffic being put on the Data-MDT"
is something that currently already takes a fair among of time with some
implementations (many 10s of seconds).  And this only temporarily
reduces the bandwidth optimisation gain, and -again- with no impact on
the service provided to the user.

That said, comparing the signaling latency of S-PMSI with BGP and the
UDP protocol, is a bit like comparing apples and oranges (yes, Pink
Floyd's fans in the crowd, it is normal if you start hearing a little
singing voice) because BGP signaling ensures the delivery of this
information. The actual signaling minimal latency in both cases will
then depend partly on implementation, and on the number of processing
"hops" and on the network-related latency.

> In theory,  the use of BGP  S-PMSI signaling has a  number of advantages,
>    but I  don't think  I would  recommend against the  use of  the UDP-based
>    procedure unless and until I had some data about these pragmatic issues.

( You know that we do have recent facts about pragmatic issues related
to Data-MDT signaling with the UDP scheme, that would not have arised
with the BGP signaling approach. )


> "The  UDP-based protocol  is  restricted  to use  within  MVPNs using  an
>    MI-PMSI".
> 
>    This fact seems to me to be  neither here nor there.  It is true that the
>    UDP-based protocol is unlikely to be useful unless PIM is the C-multicast
>    routing control protocol, in which case  you have an MI-PMSI.   [...]

Hmmm... I don't read any such thing in draft-ietf-l3vpn-2547bis-mcast.

As I see it, there are two proposed control plane approaches for S-PMSI
signaling. We are trying to focus the solution draft on only providing
one (which will help produce a "standard"), and we happen to see that
there is one of the two that require a specific type of data plane. 


> The UDP-based S-PMSIs signaling is best considered as an optional part of
>    the  PIM C-multicast  routing control  plane, rather  than as  a separate
>    protocol with its own independent set of pros and cons.

Hmmm... can you explain why the BGP signaling for S-PMSI would not apply
if PIM is used for C-multicast routing ? it seems to me that it is
totally applicable.

Said differently: why BGP-based autodiscovery of I-PMSI would be a good
fit for the Full PIM peering approach, and BGP-based S-PMSI signaling
would not?


> "the  use  of  the  UDP-based  protocol  does  not  preserve  AS  routing
>     independence  when  used in  an  inter-AS  option  B context  (i.e.  the
>     decision by  a PE in an  AS to use an  S-PMSI for a  given customer flow
>     will impact routing state in other ASes)
> 
>    I  have no  idea what  this means,  so I  hope one  of the  authors will
>    explain.   (I also  don't  know what  is  meant by  the  claim that  the
>    BGP-based S-PMSI signaling  mechanism doesn't have whatever disadvantage
>    this is.)

The thing is that the BGP segmented model provide means so that an AS
can trigger an S-PMSI without forcing neighbor ASes to create more state
in their backbone.  The drawback of not allowing this is I think fairly
clear : bandwidth optimization decisions made by one provider won't
impact the amount of state another provider will have to cope with.

But, you knew that already, so it really seems like a matter of wording.
We will try to improve this.


> 5. Off-loading processing onto route reflector
> 
>    The claim is made that, when using BGP to carry C-multicast routes, "some
>    of  the processing burden  associated with  client multicast  routing [is
>    offloaded] onto BGP route reflectors"
> 
>    I  would  like the  authors  to  specify  precisely what  this  offloaded
>    processing burden is.  Some consideration of its effect on existing L3VPN
>    route reflector systems would also be worthwhile.
> 
>    As the  text is now, it is  very difficult to understand  or evaluate the
>    claim.

See above (answer to your "Transactional nature of PIM" item).


> 6. MI-PMSI issues
> 
>    "Moreover, mechanisms one and two are restricted to use within
> MVPNs using an MI-PMSI, thereby necessitating [...] (b) The use of one
> P-multicast tree per PE per VPN, even for PEs that do not have sources
> in their directly attached sites for that VPN."
> 
>    First,  claim b  is  not true,  as  explained in  draft-rosen-l3vpn-mvpn-
>    profiles-00.txt, section 3.3.

Eric, you know very well that mvpn-considerations-01  (from which you
extract these statement) was submitted in early October, but
draft-rosen-l3vpn-mvpn-profiles-00, which is the first proposal of the
use of PIM across a set of M2PMP tunnels, was submitted one month later,
in early November...

So:
- we can make all the effort to be as balanced as possible, but we can't
read into the future !  ;)
- are we expected to cover all mvpn architecture proposal that are not
yet WG documents ?
- even, after reading -profiles section 3.3, it doesn't really appear to
me that this a use of the Full or Lightweight PIM peering approaches,
but rather a fifth proposal to adapt PIM to a specific dynamic mesh of
MP2MP trees 



> Second, the fact that a control  protocol requires that it be possible to
>    instantiate a P-tunnel as a shared tree  of some sort does not seem to be
>    to be  a "restriction" or disadvantage.

I would disagree : if one control plane option was restricting the
choice of the possible underlying encapsulation technique, that would
certainly be a restriction and thus a disadvantage.

But...rereading our text, I see that we don't say the right thing.
The full and lightweight PIM peering approaches do _not_ require a
provider protocol supporting shared trees, but _do_ require setting up
an MI-PMSI (and a set of trees rooted at each PE would thus obviously
allow to support PIM for C-multicast routing).  We will definitely
correct this text.


> There are however some other things  that do seem to require the presence
>    of an MI-PMSI:   autoRP and BSR.  Since many  SP customers use autoRP/BSR
>    to discover  RPs, and since  it is not  clear how to provide  support for
>    these without an  MI-PMSI, I am not convinced that one can do without an
>    MI-PMSI even if BGP is used for distributing C-multicast routes.

On the other hand, when talking about higher scales, you have to look a
few years down the road. And these days, two things are preferred:
anycast-RP for ASM support, and SSM.  These don't require any
autoRP/BSR.  So, for me, we should ask ourselves : shall deployments or
services/applications to come (SSM) incur the penalty of past choices
(ASM related complexity) ?


> 7. BGP doesn't eliminate PIM anyway
>    
>    "using BGP for customer routing distribution within multicast VPNs avoids
>    the introduction of an  additional protocol that would require additional
>    OAM processes and tools."
> 
>    It's not as if  PIM is eliminated by BGP.  As long as  PIM is used on the
>    PE/CE links, the SP is still operating a PIM environment.  

Well, it is true (and I'll propose we update this statement), but it is
also true that much of the complex things to operate with PIM relate to
PIM LAN procedures that are not necessarily used on PE-CE links (but
that are used when you use the Full PIM peering approach). Operation
people would need more expertise on PIM, to work with the Full PIM
peering approach, than when they only have to work on PIM on point to
point PE-CE links.

> [...] 
> In  any  event, I'm  not  sure  I understand  how  adding  a  lot of  new
>    functionality  to BGP  (multicast  path  creation) is  going  to be  done
>    without the need for additional OAM processes and tools.

You have existing tools to observe/handle MP-BGP routes, extending them
to understand/troubleshoot BGP mVPN routing looks easier to me than
making tools to understand/troubleshoot multicast routing event with the
Full PIM peering approach.


> 9. Encapsulation techniques
> 
>     I notice that  there is one particular data plane  technique that is not
>     addressed  by the  document, viz.,  the use  of ingress  replication and
>     transmission through  unicast tunnels.  It would be  interesting to know
>     whether SPs  have interest in this  technology; if not, maybe  it can be
>     removed from the  drafts.  (I think it adds  complexity and frankly, I'm
>     not sure it's fully and properly specified.)

( As I said earlier the goal is to identify what can be MANDATORY
options to implement. Removing one option wouldn't help in this
respect... )


> I think section 3.4 can be taken as a requirement for both a "BGP + GRE"
>     profile  and a  "PIM +  MPLS" profile,  since it  seems to  advocate for
>     independence between the the control  plane and the data plane.  But I'm
>     not sure if that is what is intended, and would like clarification.

I don't really see where your interpretation comes from. Please quote
specific text.   In my views, we aim in fact at quit the opposite : we
want to privileges an choice of control plane independent of the data
plane, to not be in a "profile" situation where control plane and data
plane engineering choices are coupled. 


> 10. Upstream-Assigned Labels, MI-PMSI, and Scalability
>    
>     The  WG drafts frequently  discuss aggregation,  and the  possibility of
>     aggregation is frequently touted as a major scalability advantage.
> 
>     What isn't always clear is  that all forms of S-PMSI aggregation require
>     a  major   new  MPLS  feature,   upstream-assigned  labels.   Supporting
>     upstream-assigned labels requires significant  changes to the data plane
>     processing  of  many  different  platforms,  and is  not  likely  to  be
>     available for some period of time.
> 
>     So realistically, for  the foreseeable future, the use  of an MI-PMSI is
>     going  to remain  the  only  method of  aggregation.   Unless a  service
>     provider does not care if their  P-routers have to maintain an amount of
>     multicast state  which is proportional to  the sum of the  states of all
>     their customers, the service provider should be requiring support for an
>     MI-PMSI. 

There is much confusion in the above statement, between aggregation of
traffic from different VPNs into a PMSI tunnel, and aggregation of
distinct (c-s,c-g) flows of a VPN into a same PSMI tunnel:
- aggregation of traffic from different VPNs into a PMSI tunnel does
require upstream assigned labels
- aggregation of distinct (c-s,c-g) flows of a VPN into a same PSMI
tunnel does _not_ require upstream assigned labels

So you can aggregate traffic of distinct (c-s,c-g) flows of a same VPN
into a same PSMI tunnel, but you _don't_ need it to be an MI-PMSI
tunnel. You can also do this with I-PMSIs, and you can do this with an
S-PMSI tunnel too.    Also, the limitation of requiring
upstream-assigned labels to aggregate traffic from distinct VPNs is not
solved by the use of MI-PMSI, this limitation is common to all PMSI
flavors.

( Really, I don't understand what you are trying to suggest... merely
creating confusion ? )


> As  a further  note,  it should  be  pointed out  that inter-AS  segment
>     S-PMSIs are on a per-PE basis, not a per-AS basis.  Therefore without the
>     aggregation that  can be obtained  from upstream-assigned labels,  it is
>     not clear that segmented inter-AS  S-PMSIs are scalable at all.  This is
>     an issue which should be mentioned.

As said above, we plan to update mvpn-considerations to take into
account recent discussions/proposals about S-PMSI and inter-AS.  

But you make a rather interesting statement : "it is not clear that
segmented inter-AS S-PMSIs are scalable at all".  In fact the segmented
model merits are to introduce means to better scale all PMSI-related
state.  If the answer to the question was "no, segmented inter-AS
S-PMSIs are not scalable at all", then S-PMSI would not be scalable in
the non-segmented model either (where S-PMSI is by design per-PE!).

>    I think the draft should have a clear recommendation that in
>    the absence of upstream-assigned MPLS labels, MI-PMSIs should be
>    used.

???
That would be bogus :
* there is an applicability for scenarios where only I-PMSI are used
(where only trees toward PE having sources are instantiated)
* S-PMSI obviously have applicability and can be used

(Again, I apart from generating confusion, I really don't get your
point)



> 11. Outsourced RPs
> 
>     I  would like  to see  the  draft offer  much stronger  support for  its
>     recommendation to  implement outsourced RPs,  or else to  eliminate that
>     recommendation. 

Your already stated this in your item "1".
Maybe you wrote too many comments ?  ;-)


[...]
> I presume  that the extra  operational work for  SP and customer  is not
>     going to be justified by the  fact that it simplifies things for some of
>     the SP's vendors.

Oh....?!??
You definitely wrote too many comments...
Despite all the respect I have for you, this is totally bogus.
- First, you imply that the four operators co-authors of mvpn-considerations 
are adding content in mvpn-considerations to simplify the work of specific 
vendor(s). You must be living in a funky world full of conspiracy theories.
- Second, you have missed one important thing : the draft actually state
that implementing only the "outsourced RP" model is not acceptable. I
don't how this is supposed to "simplify things for some [..] vendor(s)",
and doesn't really fit your conspiracy theory plot.


> 12. The draft's conclusion
> 
>    "Consequently, at the present time and until there is experience with
>    all of the proposed mechanisms it is not clear which of the above
>    mechanisms should be recommended as the preferred solution to
>    implementers.  However, it would appear prudent for implementations
>    to consider supporting both the fourth (BGP-based) and first (full
>    per-MPVN PIM peering) mechanisms.  Further experience on both
>    implementation is likely to be required before some best practice can
>    be defined."
> 
>    I certainly agree with this  conclusion.  Perhaps it should be given more
>    prominence. 

It is nice to see you agree. 
A few things though :
- this is not the only conclusion of the draft (this talks about about
C-multicast routing)
- this draft is a work in progress: "final" conclusions will be the one
in whatever final version is produced, taking into account feedback,
comments, and experience gained on all solutions

-Thomas





From l3vpn-bounces@ietf.org Mon Dec 17 17:18:43 2007
Return-path: <l3vpn-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1J4OIN-0002mH-C9; Mon, 17 Dec 2007 17:18:43 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1J4OIL-0002jX-NI
	for l3vpn@ietf.org; Mon, 17 Dec 2007 17:18:41 -0500
Received: from p-mail1.rd.francetelecom.com ([195.101.245.15])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1J4OIJ-0003TZ-Tn
	for l3vpn@ietf.org; Mon, 17 Dec 2007 17:18:41 -0500
Received: from ftrdmel10.rd.francetelecom.fr ([10.193.117.156]) by
	ftrdsmtp1.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 17 Dec 2007 23:18:13 +0100
Received: from [127.0.0.1] ([10.193.4.45]) by ftrdmel10.rd.francetelecom.fr
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 17 Dec 2007 23:18:35 +0100
From: Thomas Morin <thomas.morin@orange-ftgroup.com>
To: "NAPIERALA, MARIA H, ATTLABS" <mnapierala@att.com>
In-Reply-To: <7AFE40EF30EE754DA967D1B5968457CA1381BF9D@KCCLUST06EVS1.ugd.att.com>
References: <20071214123516.V50822@zircon.juniper.net>
	<20071214123546.T50822@zircon.juniper.net>
	<7AFE40EF30EE754DA967D1B5968457CA1381BF9D@KCCLUST06EVS1.ugd.att.com>
Content-Type: text/plain
Organization: France Telecom R&D - Orange
Date: Mon, 17 Dec 2007 23:01:16 +0100
Message-Id: <1197928876.4927.430.camel@wintermute>
Mime-Version: 1.0
X-Mailer: Evolution 2.12.2 
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 17 Dec 2007 22:18:35.0895 (UTC)
	FILETIME=[C4458070:01C840FA]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b280b4db656c3ca28dd62e5e0b03daa8
Cc: l3vpn@ietf.org
Subject: RE: draft-morin-l3vpn-mvpn-considerations
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>
Errors-To: l3vpn-bounces@ietf.org

Hi Maria,

NAPIERALA, MARIA H, ATTLABS wrote:
> The draft is a very good start but there are still some outstanding
> mandatory design aspects that need to be addressed: 
> - support of non-static RP solutions like BSR. There are current large
> MVPNs in SP network that use BSR

I agree (see reply to Eric) that our draft can mention BSR support.
There is only one currently proposed approach for BSR support, applying
to both the Full PIM peering approach and the BGP approach, so there
isn't that much to "compare", but the current requirement for MI-PMSI
for BSR support, even in the case where BGP is used for C-multicast
routing, has to be mentioned.

> - what is still missing in this draft as well as in RFC4834 is the
> requirement to support PIM Bidir on CE-PE links. This requirement is
> coming, e.g., from large financial firms for which using PIM-SM for
> certain business critical applications does not scale. Not to mention
> the SP :-))
> - support of "PIM-like" Anycast-RP by allowing multiple RP's to send
> traffic in parallel 

The two points above would look to me as belonging to the mvpn
requirement document (RFC4834). 

The requirement for CE-PE bidir-PIM is actually already in that
document. The way of supporting bidir-PIM is definitely distinct in the
BGP approach and in the Full PIM peering approach, but it seems to me
that both should be able to support it. Do you think that
mvpn-consideration should discuss the relative advantage of the
different proposals for bidir-PIM support ?

For the other requirement, the better is probably to explain to solution
draft authors, what would be the need. Do you think that it could help
distinguish one of the proposed approaches ?


> - the recommended approach for a source PE to decide when to start
> transmitting customer multicast traffic on a S-PMSI (namely, the source
> PE waits for a pre-configured period of time) is not satisfactory in my
> opinion. A different approach is proposed in
> draft-mnapierala-mvpn-rev-03

Is this something mvpn-consideration should talk about to help
distinguish a better approach among the proposed ones ?

> Also, I would suggest that "co-located RP" recommendation is removed
> from the document. Co-locating C-RP on PE should not be positioned as a
> mandatory mechanism in MVPN, which this draft is addressing.

As I said earlier, mvpn-considerations does not at all push this feature
as mandatory at all.

> I might have comments but wanted to send those COB today. 

As I told you in Prague, your comments and contributions to this draft
are always welcome. 

Thanks,

-Thomas



> -) ---------- Forwarded message ----------
> -) Date: Mon, 10 Dec 2007 16:11:28 -0500
> -) From: Ron Bonica <rbonica@juniper.net>
> -) To: l3vpn@ietf.org
> -) Subject: draft-morin-l3vpn-mvpn-considerations
> -) 
> -) Folks,
> -) 
> -) Unless I hear an objection before COB Friday, this document will
> become
> -) a WG draft.
> -) 
> -)                                       Ron
> -) 
> 
> 





From l3vpn-bounces@ietf.org Mon Dec 17 19:20:32 2007
Return-path: <l3vpn-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1J4QCB-0008UY-Bb; Mon, 17 Dec 2007 19:20:27 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1J4QC9-0008Tp-9b
	for l3vpn@ietf.org; Mon, 17 Dec 2007 19:20:25 -0500
Received: from email1.etri.re.kr ([129.254.16.131] helo=email1.etri.info)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1J4QC8-0005Mb-RX
	for l3vpn@ietf.org; Mon, 17 Dec 2007 19:20:25 -0500
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C8410C.B4E8CF39"
X-MimeOLE: Produced By Microsoft Exchange V6.5
Date: Tue, 18 Dec 2007 09:27:01 +0900
Message-ID: <4C86297B4AC6554B8BA018F0806590CE01397BA8@email1>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: unsubscribe
Thread-Index: AchBC7XRdSdVCzLDRXyEVbDJnPNjUg==
From: =?ks_c_5601-1987?B?udq5zLfm?= <mrpark@etri.re.kr>
To: <l3vpn@ietf.org>
X-Spam-Score: 2.9 (++)
X-Scan-Signature: 5011df3e2a27abcc044eaa15befcaa87
Subject: unsubscribe
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>
Errors-To: l3vpn-bounces@ietf.org

This is a multi-part message in MIME format.

------_=_NextPart_001_01C8410C.B4E8CF39
Content-Type: text/plain;
	charset="ks_c_5601-1987"
Content-Transfer-Encoding: quoted-printable

unsubscribe

=20

=20


------_=_NextPart_001_01C8410C.B4E8CF39
Content-Type: text/html;
	charset="ks_c_5601-1987"
Content-Transfer-Encoding: quoted-printable

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

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dks_c_5601-1987">
<meta name=3DGenerator content=3D"Microsoft Word 12 (filtered medium)">
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:"=B8=BC=C0=BA =B0=ED=B5=F1";
	panose-1:2 11 5 3 2 0 0 2 0 4;}
@font-face
	{font-family:"\@=B8=BC=C0=BA =B0=ED=B5=F1";
	panose-1:2 11 5 3 2 0 0 2 0 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	text-align:justify;
	text-justify:inter-ideograph;
	text-autospace:none;
	word-break:break-hangul;
	font-size:10.0pt;
	font-family:"=B8=BC=C0=BA =B0=ED=B5=F1";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"=B8=BC=C0=BA =B0=ED=B5=F1";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;}
 /* Page Definitions */
 @page Section1
	{size:612.0pt 792.0pt;
	margin:3.0cm 72.0pt 72.0pt 72.0pt;}
div.Section1
	{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

<body lang=3DKO link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal><span =
lang=3DEN-US>unsubscribe<o:p></o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p>

</div>

</body>

</html>

------_=_NextPart_001_01C8410C.B4E8CF39--




From l3vpn-bounces@ietf.org Tue Dec 18 10:22:38 2007
Return-path: <l3vpn-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1J4eGx-00024h-5h; Tue, 18 Dec 2007 10:22:19 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1J4eGw-00024a-9d
	for l3vpn@ietf.org; Tue, 18 Dec 2007 10:22:18 -0500
Received: from rtp-iport-1.cisco.com ([64.102.122.148])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1J4eGv-0006Is-Ss
	for l3vpn@ietf.org; Tue, 18 Dec 2007 10:22:18 -0500
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by rtp-iport-1.cisco.com with ESMTP; 18 Dec 2007 10:22:17 -0500
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12])
	by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id lBIFMH7k022568; 
	Tue, 18 Dec 2007 10:22:17 -0500
Received: from erosen-linux.cisco.com (erosen-linux.cisco.com [161.44.70.34])
	by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id
	lBIFMHvB015639; Tue, 18 Dec 2007 15:22:17 GMT
Received: from erosen-linux (localhost.localdomain [127.0.0.1])
	by erosen-linux.cisco.com (8.13.1/8.13.1) with ESMTP id lBIFMCbo019461; 
	Tue, 18 Dec 2007 10:22:16 -0500
To: Thomas Morin <thomas.morin@orange-ftgroup.com>
In-reply-to: Your message of Mon, 17 Dec 2007 22:38:43 +0100.
	<1197927524.4927.409.camel@wintermute> 
Date: Tue, 18 Dec 2007 10:22:12 -0500
Message-ID: <19460.1197991332@erosen-linux>
From: Eric Rosen <erosen@cisco.com>
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=2464; t=1197991337;
	x=1198855337; c=relaxed/simple; s=rtpdkim1001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=erosen@cisco.com;
	z=From:=20Eric=20Rosen=20<erosen@cisco.com>
	|Subject:=20Re=3A=20Comments=20on=20draft-morin-l3vpn-mvpn-
	considerations-01.txt=20 |Sender:=20
	|To:=20Thomas=20Morin=20<thomas.morin@orange-ftgroup.com>;
	bh=TxDbvFDr/rzdbAEsCgbml+SNg/Qdpdwk9keTvn6Qhzg=;
	b=OyDtI0j7FBMR3vz/hhQz/UJvsaDOTE7Wgv4u/4ambFXUNfYaGl1FA04TVb
	tZbmLjBJX1YjN2amrk5/GDjacsCCGRsuRXqXM035xE5J7+7UpjKyla/vfVll
	5hllYw8cdo;
Authentication-Results: rtp-dkim-1; header.From=erosen@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim1001 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 538aad3a3c4f01d8b6a6477ca4248793
Cc: Eric Rosen <erosen@cisco.com>, L3VPN <l3vpn@ietf.org>
Subject: Re: Comments on draft-morin-l3vpn-mvpn-considerations-01.txt 
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: erosen@cisco.com
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>
Errors-To: l3vpn-bounces@ietf.org


Thomas  raises  a lot  of  issues,  which  deserve discussion  (probably  in
separate threads), and which will take a bit of time to respond to.

But there're two issues I want to respond to right away:

Eric> I would  like to  see the  draft offer much  stronger support  for its
Eric> recommendation to implement outsourced  RPs, or else to eliminate that
Eric> recommendation.

This is addressed at the text from section 4 of the draft:

        "It is therefore the recommendation of the authors
        that implementations should support a co-located RP model"

Thus it seems  to me that the draft recommends that  the co-located RP model
be implemented, and I think I am within my rights to oppose the inclusion of
that recommendation.

Thomas> Everybody having read the draft can see that it actually not only say
Thomas> that the RP-colocation feature is useful but also that an implementation
Thomas> should _not_ require using this feature

That's a  completely different issue, I  never said that  the draft requires
the co-located RP feature to be deployed.

Thomas> your  underlying suggestion  that co-authors  of mvpn-considerations
Thomas> state  that "the  outsourced-RP  feature should  be implemented"  to
Thomas> simplify things for some particular vendor(s)

I apologize if my words led you  to make that inference, but that was not my
intended  implication.   I  do  think  that  the  outsourced-RP  feature  is
primarily a  simplification for the  vendor, and really just  a complication
for the  SP and its customers.   However, my assumption is  that the authors
have  an  honest disagreement  with  me, not  that  they  have any  ulterior
motives.

Thomas> operators have just a sincere  interest in trying to identify a best
Thomas> candidate for becoming a standard (vs. a set of "profiles")

At no time did  I question the sincerity of the authors,  nor have I accused
anyone  of attempting to  spread FUD,  of telling  lies, or  having ulterior
motives.  I hope you will agree that ad hominem attacks of that sort have no
place on this ML.  I suppose  I have accused people of not fully considering
all the issues, but that does seem appropriate for this ML.

Thomas> If you happen to disagree with this perspective

I don't disagree about the sincerity  of the authors, but I don't think it's
either possible  or desirable at this  point to dispense with  the notion of
profiles.






From l3vpn-bounces@ietf.org Tue Dec 18 11:05:17 2007
Return-path: <l3vpn-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1J4ewS-0000dO-Mr; Tue, 18 Dec 2007 11:05:12 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1J4ewR-0000an-MU
	for l3vpn@ietf.org; Tue, 18 Dec 2007 11:05:11 -0500
Received: from p-mail1.rd.francetelecom.com ([195.101.245.15])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1J4ewP-0002Q5-Ua
	for l3vpn@ietf.org; Tue, 18 Dec 2007 11:05:11 -0500
Received: from ftrdmel10.rd.francetelecom.fr ([10.193.117.156]) by
	ftrdsmtp2.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 18 Dec 2007 17:05:06 +0100
Received: from [10.193.15.109] ([10.193.15.109]) by
	ftrdmel10.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 18 Dec 2007 17:05:05 +0100
From: Thomas Morin <thomas.morin@orange-ftgroup.com>
To: erosen@cisco.com
In-Reply-To: <19460.1197991332@erosen-linux>
References: <19460.1197991332@erosen-linux>
Content-Type: text/plain
Organization: France Telecom R&D - Orange
Date: Tue, 18 Dec 2007 17:05:04 +0100
Message-Id: <1197993905.6132.38.camel@wintermute>
Mime-Version: 1.0
X-Mailer: Evolution 2.12.2 
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 18 Dec 2007 16:05:05.0679 (UTC)
	FILETIME=[C127A9F0:01C8418F]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c0bedb65cce30976f0bf60a0a39edea4
Cc: L3VPN <l3vpn@ietf.org>
Subject: Re: Comments on draft-morin-l3vpn-mvpn-considerations-01.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>
Errors-To: l3vpn-bounces@ietf.org

Hi Eric,

Eric Rosen :
>
> Eric> I would  like to  see the  draft offer much  stronger support  for its
> Eric> recommendation to implement outsourced  RPs, or else to eliminate that
> Eric> recommendation.
> 
> This is addressed at the text from section 4 of the draft:
> 
>         "It is therefore the recommendation of the authors
>         that implementations should support a co-located RP model"
> 
> Thus it seems  to me that the draft recommends that  the co-located RP model
> be implemented, and I think I am within my rights to oppose the inclusion of
> that recommendation.

For sure and nobody contested this right.

I'm interested in understanding why you have such a strong feeling about
a statement that only recommends a relatively minor optional feature,
that actually happens to be implemented by numerous vendors in multicast
VRFs, including the one you work for.

The mVPN requirements (RFC4834) actually talk in terms of "MAY" about
this feature. Is it the difference between "MAY" and "should", that
makes you so strongly react ?


> Thomas> your  underlying suggestion  that co-authors  of mvpn-considerations
> Thomas> state  that "the  outsourced-RP  feature should  be implemented"  to
> Thomas> simplify things for some particular vendor(s)
> 
> I apologize if my words led you  to make that inference, but that was not my
> intended  implication.   I  do  think  that  the  outsourced-RP  feature  is
> primarily a  simplification for the  vendor, and really just  a complication
> for the  SP and its customers.

To fully clarify what caused this misunderstanding, can you explain how
implementing this optional feature is "primarily a simplification for
the vendor" ?

> However, my assumption is  that the authors have  an  honest
> disagreement  with  me, not  that  they  have any  ulterior
> motives.

Nice to see you clarify this point.

> Thomas> operators have just a sincere  interest in trying to identify a best
> Thomas> candidate for becoming a standard (vs. a set of "profiles")
> 
> At no time did  I question the sincerity of the authors,  nor have I accused
> anyone  of attempting to  spread FUD,  of telling  lies, or  having ulterior
> motives.  I hope you will agree that ad hominem attacks of that sort have no
> place on this ML.

Ad hominem attacks indeed are not appropriate. 

You will hopefully agree too, that critics on the statements made (and
not on the people who make them) or the form of reasoning used (and not
on the people who use them), certainly do have a place here. 

You can also agree that it is quite natural to wonder about the
motivations when trying to better understand the issue raised.

-Thomas





From l3vpn-bounces@ietf.org Tue Dec 18 11:49:10 2007
Return-path: <l3vpn-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1J4faM-0002nG-0l; Tue, 18 Dec 2007 11:46:26 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1J4faK-0002mt-Ri
	for l3vpn@ietf.org; Tue, 18 Dec 2007 11:46:24 -0500
Received: from rtp-iport-1.cisco.com ([64.102.122.148])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1J4faB-00043q-OX
	for l3vpn@ietf.org; Tue, 18 Dec 2007 11:46:24 -0500
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by rtp-iport-1.cisco.com with ESMTP; 18 Dec 2007 11:46:10 -0500
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12])
	by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id lBIGkAqV009539; 
	Tue, 18 Dec 2007 11:46:10 -0500
Received: from erosen-linux.cisco.com (erosen-linux.cisco.com [161.44.70.34])
	by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id
	lBIGkAvB021402; Tue, 18 Dec 2007 16:46:10 GMT
Received: from erosen-linux (localhost.localdomain [127.0.0.1])
	by erosen-linux.cisco.com (8.13.1/8.13.1) with ESMTP id lBIGk9Gb020011; 
	Tue, 18 Dec 2007 11:46:10 -0500
To: Thomas Morin <thomas.morin@orange-ftgroup.com>
In-reply-to: Your message of Tue, 18 Dec 2007 17:05:04 +0100.
	<1197993905.6132.38.camel@wintermute> 
Date: Tue, 18 Dec 2007 11:46:09 -0500
Message-ID: <20010.1197996369@erosen-linux>
From: Eric Rosen <erosen@cisco.com>
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1908; t=1197996370;
	x=1198860370; c=relaxed/simple; s=rtpdkim1001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=erosen@cisco.com;
	z=From:=20Eric=20Rosen=20<erosen@cisco.com>
	|Subject:=20Re=3A=20Comments=20on=20draft-morin-l3vpn-mvpn-
	considerations-01.txt=20 |Sender:=20
	|To:=20Thomas=20Morin=20<thomas.morin@orange-ftgroup.com>;
	bh=gnjxPlhH6K5TYtw66LKk/9VtHRMmqlpPiE+imNCee/8=;
	b=bD3gR06vicfMo9co38dxq6D/IGdytx+97VcmP3ZfqOTYkdSAAgU2nVycfG
	adxDJgkt5zFwc8RUdgNnUUwk2k1bY4PCNNyloD9gnwyFNZQTecJor7123vjX
	SjeoCfDZTB;
Authentication-Results: rtp-dkim-1; header.From=erosen@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim1001 verified; ); 
X-Spam-Score: -4.0 (----)
X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb
Cc: erosen@cisco.com, L3VPN <l3vpn@ietf.org>
Subject: Re: Comments on draft-morin-l3vpn-mvpn-considerations-01.txt 
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: erosen@cisco.com
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>
Errors-To: l3vpn-bounces@ietf.org


> I'm interested in understanding why you have such a strong feeling about
> a statement that only recommends a relatively minor optional feature,

I am uncomfortable with it for a number of reasons:

- If an SP  wants to offer "outsourced RP" service  to its customers, that's
  fine.  That does  not necessarily require that the PEs  serve as RPs.  The
  "PE  as RP"  model  is a  particular  way of  deploying  an outsourced  RP
  service.   How best  to deploy  an outsourced  RP service  is a  topic for
  discussion between  an SP and  its vendors, and not  necessarily something
  that the IETF even needs to be involved in.

- I  cannot believe  that "PE  as RP"  is really  going to  be  the superior
  "outsourced RP" deployment model at scale.  

- The draft  gives the  appearance of recommending  (even if  not requiring)
  both the "outsourced RP" model and this particular method of deploying it.

- The  model itself  has what  I consider  to be  significant disadvantages,
  especially if  you try to deploy it  with a customer that  has an existing
  multicast infrastructure.

- I  don't think  the impression  you get  from the  draft is  that it  is a
  "relatively minor optional feature".   That sort of minor optional feature
  would typically get a "may" rather than a "should".

> The mVPN requirements (RFC4834) actually talk in terms of "MAY" about
> this feature. Is it the difference between "MAY" and "should", that
> makes you so strongly react ?

No objection to MAY.

> can you  explain how  implementing this optional  feature is  "primarily a
> simplification for the vendor" ?

It allows a vendor to ship product which supports only the "PE as RP" model,
while  still claiming  to have  ASM support  in its  MVPN product.   This is
considerably less  of an  implementation effort than  is required  to really
provide ASM support.





From l3vpn-bounces@ietf.org Tue Dec 18 12:18:47 2007
Return-path: <l3vpn-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1J4g5Y-0003sn-8r; Tue, 18 Dec 2007 12:18:40 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1J4g5W-0003qK-Hy
	for l3vpn@ietf.org; Tue, 18 Dec 2007 12:18:38 -0500
Received: from p-mail2.rd.francetelecom.com ([195.101.245.16])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1J4g5V-0003qo-Va
	for l3vpn@ietf.org; Tue, 18 Dec 2007 12:18:38 -0500
Received: from ftrdmel10.rd.francetelecom.fr ([10.193.117.156]) by
	ftrdsmtp1.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 18 Dec 2007 18:18:11 +0100
Received: from [10.193.15.109] ([10.193.15.109]) by
	ftrdmel10.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 18 Dec 2007 18:18:34 +0100
From: Thomas Morin <thomas.morin@orange-ftgroup.com>
To: erosen@cisco.com
In-Reply-To: <20010.1197996369@erosen-linux>
References: <20010.1197996369@erosen-linux>
Content-Type: text/plain
Organization: France Telecom R&D - Orange
Date: Tue, 18 Dec 2007 17:18:33 +0000
Message-Id: <1197998313.6132.60.camel@wintermute>
Mime-Version: 1.0
X-Mailer: Evolution 2.12.2 
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 18 Dec 2007 17:18:34.0320 (UTC)
	FILETIME=[04E8E500:01C8419A]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4d87d2aa806f79fed918a62e834505ca
Cc: L3VPN <l3vpn@ietf.org>
Subject: Re: Comments on draft-morin-l3vpn-mvpn-considerations-01.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>
Errors-To: l3vpn-bounces@ietf.org

Eric Rosen :
>
> - The draft  gives the  appearance of recommending  (even if  not requiring)
>   both the "outsourced RP" model and this particular method of deploying it.

The draft actually has 5 short paragraphs about co-located-RP: 
- 2 paragraphs are quotes of the requirements draft reminding the
context and the benefits of the feature
- 2 paragraphs detail the disadvantages of this approach
- the last paragraphs concludes by saying "should be implemented" but
"must not be required to use"

It seems to me that this is quite balanced...


> - I  don't think  the impression  you get  from the  draft is  that it  is a
>   "relatively minor optional feature".   That sort of minor optional feature
>   would typically get a "may" rather than a "should".

The use of "should" in the text, and not "SHOULD" precisely shows that
the "level of requirement" wasn't strongly defined, this is typically
the type of wording that gets refined once a document progresses
further...


> > can you  explain how  implementing this optional feature is 
> > "primarily a simplification for the vendor" ?
> 
> It allows a vendor to ship product which supports only the "PE as RP"
> model, while  still claiming  to have  ASM support  in its  MVPN
> product. This is considerably less  of an  implementation effort than
> is required  to really provide ASM support.

It doesn't simplify anything as soon as it is required to support
deployment of ASM without using this feature. Which precisely is what
our draft is suggesting to impose. 

> > The mVPN requirements (RFC4834) actually talk in terms of "MAY"
> > about this feature. Is it the difference between "MAY" and "should",
> > that makes you so strongly react ?
> 
> No objection to MAY.

(Which I wouldn't object either.)

So, in the end, this colocation-RP subject that takes 10% of your
comments seem to be resolved by a "should" being refined into a "MAY". 
Do such type of changes usually justify opposing that a draft becomes a
WG doc ?

-Thomas





From l3vpn-bounces@ietf.org Tue Dec 18 12:24:59 2007
Return-path: <l3vpn-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1J4gBc-0004iZ-S8; Tue, 18 Dec 2007 12:24:56 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1J4gBc-0004iU-9l
	for l3vpn@ietf.org; Tue, 18 Dec 2007 12:24:56 -0500
Received: from p-mail2.rd.francetelecom.com ([195.101.245.16])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1J4gBa-0005U3-LF
	for l3vpn@ietf.org; Tue, 18 Dec 2007 12:24:56 -0500
Received: from ftrdmel10.rd.francetelecom.fr ([10.193.117.156]) by
	ftrdsmtp2.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 18 Dec 2007 18:24:52 +0100
Received: from [10.193.15.109] ([10.193.15.109]) by
	ftrdmel10.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 18 Dec 2007 18:24:50 +0100
From: Thomas Morin <thomas.morin@orange-ftgroup.com>
To: erosen@cisco.com
In-Reply-To: <19460.1197991332@erosen-linux>
References: <19460.1197991332@erosen-linux>
Content-Type: text/plain
Organization: France Telecom R&D - Orange
Date: Tue, 18 Dec 2007 18:24:50 +0100
Message-Id: <1197998690.6132.66.camel@wintermute>
Mime-Version: 1.0
X-Mailer: Evolution 2.12.2 
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 18 Dec 2007 17:24:51.0101 (UTC)
	FILETIME=[E57D1CD0:01C8419A]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25
Cc: L3VPN <l3vpn@ietf.org>
Subject: Re: Comments on draft-morin-l3vpn-mvpn-considerations-01.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>
Errors-To: l3vpn-bounces@ietf.org

Eric Rosen :
> Thomas  raises  a lot  of  issues,

Replying to your numerous comments does indeed take some time ! ;)

> which  deserve discussion  (probably  in
> separate threads), and which will take a bit of time to respond to.

It would be great if you can tell the working group if the updates I
propose in the head of my reply (not that long) are enough to address
your concerns.

Thank you,

-Thomas





From l3vpn-bounces@ietf.org Tue Dec 18 12:34:46 2007
Return-path: <l3vpn-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1J4gL5-0001DY-1S; Tue, 18 Dec 2007 12:34:43 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1J4gL3-0001CP-90
	for l3vpn@ietf.org; Tue, 18 Dec 2007 12:34:41 -0500
Received: from mail120.messagelabs.com ([216.82.250.83])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1J4gL1-0005jb-CV
	for l3vpn@ietf.org; Tue, 18 Dec 2007 12:34:41 -0500
X-VirusChecked: Checked
X-Env-Sender: mnapierala@att.com
X-Msg-Ref: server-3.tower-120.messagelabs.com!1197999263!24970645!1
X-StarScan-Version: 5.5.12.14.2; banners=-,-,-
X-Originating-IP: [144.160.20.54]
Received: (qmail 28064 invoked from network); 18 Dec 2007 17:34:24 -0000
Received: from sbcsmtp7.sbc.com (HELO mlpi135.enaf.sfdc.sbc.com)
	(144.160.20.54)
	by server-3.tower-120.messagelabs.com with AES256-SHA encrypted SMTP;
	18 Dec 2007 17:34:24 -0000
Received: from enaf.sfdc.sbc.com (localhost.localdomain [127.0.0.1])
	by mlpi135.enaf.sfdc.sbc.com (8.14.0/8.14.0) with ESMTP id
	lBIHYNX4029141 for <l3vpn@ietf.org>; Tue, 18 Dec 2007 12:34:23 -0500
Received: from kcclust06evs1.ugd.att.com (kcst11.ugd.att.com [135.38.164.88])
	by mlpi135.enaf.sfdc.sbc.com (8.14.0/8.14.0) with ESMTP id
	lBIHYE34029038 for <l3vpn@ietf.org>; Tue, 18 Dec 2007 12:34:18 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 18 Dec 2007 11:34:14 -0600
Message-ID: <7AFE40EF30EE754DA967D1B5968457CA1381BFD2@KCCLUST06EVS1.ugd.att.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: RE: draft-morin-l3vpn-mvpn-considerations
Thread-Index: AchA+sz6Mzuq0UPMSqmtIcjSEsaiKAAmH8UQAAGKbgAAAKKA4A==
From: "NAPIERALA, MARIA H, ATTLABS" <mnapierala@att.com>
To: "Thomas Morin" <thomas.morin@orange-ftgroup.com>
X-Spam-Score: -4.0 (----)
X-Scan-Signature: 8fbbaa16f9fd29df280814cb95ae2290
Cc: l3vpn@ietf.org
Subject: RE: draft-morin-l3vpn-mvpn-considerations
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>
Errors-To: l3vpn-bounces@ietf.org

Hi Thomas,
thanks for the reply. See my responses in-line.

Maria=20

-----Original Message-----
From: Thomas Morin [mailto:thomas.morin@orange-ftgroup.com]=20
Sent: Monday, December 17, 2007 5:01 PM
To: NAPIERALA, MARIA H, ATTLABS
Cc: Ron Bonica; l3vpn@ietf.org
Subject: RE: draft-morin-l3vpn-mvpn-considerations

Hi Maria,

NAPIERALA, MARIA H, ATTLABS wrote:
> The draft is a very good start but there are still some outstanding
> mandatory design aspects that need to be addressed:=20
> - support of non-static RP solutions like BSR. There are current large
> MVPNs in SP network that use BSR

I agree (see reply to Eric) that our draft can mention BSR support.
There is only one currently proposed approach for BSR support, applying
to both the Full PIM peering approach and the BGP approach, so there
isn't that much to "compare", but the current requirement for MI-PMSI
for BSR support, even in the case where BGP is used for C-multicast
routing, has to be mentioned.

<maria> yes, I agree. The need for MI-PMSI should be stated as the only
currently available solution for BSR. Since there are existing MVPN
deployments that use BSR, it needs to be supported.

> - what is still missing in this draft as well as in RFC4834 is the
> requirement to support PIM Bidir on CE-PE links. This requirement is
> coming, e.g., from large financial firms for which using PIM-SM for
> certain business critical applications does not scale. Not to mention
> the SP :-))
> - support of "PIM-like" Anycast-RP by allowing multiple RP's to send
> traffic in parallel=20

The two points above would look to me as belonging to the mvpn
requirement document (RFC4834).=20

<maria> actually, those requirements are already stated in
draft-mnapierala-mvpn-part-reqt-00.

The requirement for CE-PE bidir-PIM is actually already in that
document.=20

<maria> that's true but RFC4834 only "recommends" PIM-Bidir support on
PE-CE interfaces. The draft-mnapierala-mvpn-part-req makes it a
requirement. We have many large VPN customers requiring it.

The way of supporting bidir-PIM is definitely distinct in the
BGP approach and in the Full PIM peering approach, but it seems to me
that both should be able to support it. Do you think that
mvpn-consideration should discuss the relative advantage of the
different proposals for bidir-PIM support ?

<maria> Definitely.

For the other requirement, the better is probably to explain to solution
draft authors, what would be the need. Do you think that it could help
distinguish one of the proposed approaches ?

<maria> surely. Some of the argumentation from a service provider point
of view is in draft-mnapierala-mvpn-part-reqt.

> - the recommended approach for a source PE to decide when to start
> transmitting customer multicast traffic on a S-PMSI (namely, the
source
> PE waits for a pre-configured period of time) is not satisfactory in
my
> opinion. A different approach is proposed in
> draft-mnapierala-mvpn-rev-03

Is this something mvpn-consideration should talk about to help
distinguish a better approach among the proposed ones ?

<maria> I think so. There are multiple approaches and they should be
compared in this aspect.=20

> Also, I would suggest that "co-located RP" recommendation is removed
> from the document. Co-locating C-RP on PE should not be positioned as
a
> mandatory mechanism in MVPN, which this draft is addressing.

As I said earlier, mvpn-considerations does not at all push this feature
as mandatory at all.

<maria>  What confused me is, quoting from the draft section 1:=20
"The aim of this document is to leverage the already expressed
requirements [RFC4834] to identify the mechanisms that the authors
believe are good candidates for being part of a core set of MANDATORY
mechanisms which can be used to provide a base for interoperable
solutions." (my underline of "mandatory").
I also think that in a "big scheme of things" co-locating C-RP with PE
is an insignificant recommendation... This is already supported by
vendors and if a service provider wants to use it, it is free to do so
:-)
=20

> I might have comments but wanted to send those COB today.=20

As I told you in Prague, your comments and contributions to this draft
are always welcome.=20

<maria> surely!

Thanks,

-Thomas



> -) ---------- Forwarded message ----------
> -) Date: Mon, 10 Dec 2007 16:11:28 -0500
> -) From: Ron Bonica <rbonica@juniper.net>
> -) To: l3vpn@ietf.org
> -) Subject: draft-morin-l3vpn-mvpn-considerations
> -)=20
> -) Folks,
> -)=20
> -) Unless I hear an objection before COB Friday, this document will
> become
> -) a WG draft.
> -)=20
> -)                                       Ron
> -)=20
>=20
>=20





From l3vpn-bounces@ietf.org Tue Dec 18 14:50:44 2007
Return-path: <l3vpn-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1J4iSU-00032A-QW; Tue, 18 Dec 2007 14:50:30 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1J4iST-00031x-MQ
	for l3vpn@ietf.org; Tue, 18 Dec 2007 14:50:29 -0500
Received: from exprod7og106.obsmtp.com ([64.18.2.165])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1J4iST-00019b-6Q
	for l3vpn@ietf.org; Tue, 18 Dec 2007 14:50:29 -0500
Received: from source ([66.129.224.36]) by exprod7ob106.postini.com
	([64.18.6.12]) with SMTP; Tue, 18 Dec 2007 11:50:07 PST
Received: from magenta.juniper.net ([172.17.27.123]) by emailsmtp55.jnpr.net
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 18 Dec 2007 11:50:14 -0800
Received: from juniper.net (sapphire.juniper.net [172.17.28.108])
	by magenta.juniper.net (8.11.3/8.11.3) with ESMTP id lBIJoEE94154;
	Tue, 18 Dec 2007 11:50:14 -0800 (PST)
	(envelope-from yakov@juniper.net)
Message-Id: <200712181950.lBIJoEE94154@magenta.juniper.net>
To: erosen@cisco.com
In-Reply-To: Your message of "Tue, 18 Dec 2007 11:46:09 EST."
	<20010.1197996369@erosen-linux> 
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <11455.1198007414.1@juniper.net>
Date: Tue, 18 Dec 2007 11:50:14 -0800
From: Yakov Rekhter <yakov@juniper.net>
X-OriginalArrivalTime: 18 Dec 2007 19:50:14.0737 (UTC)
	FILETIME=[352E5410:01C841AF]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
Cc: Thomas Morin <thomas.morin@orange-ftgroup.com>, L3VPN <l3vpn@ietf.org>
Subject: Re: Comments on draft-morin-l3vpn-mvpn-considerations-01.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>
Errors-To: l3vpn-bounces@ietf.org

Eric,

> > I'm interested in understanding why you have such a strong feeling about
> > a statement that only recommends a relatively minor optional feature,
> 
> I am uncomfortable with it for a number of reasons:
> 
> - If an SP  wants to offer "outsourced RP" service  to its customers, that's
>   fine.  That does  not necessarily require that the PEs  serve as RPs.  The
>   "PE  as RP"  model  is a  particular  way of  deploying  an outsourced  RP
>   service.   How best  to deploy  an outsourced  RP service  is a  topic for
>   discussion between  an SP and  its vendors, and not  necessarily something
>   that the IETF even needs to be involved in.

For the same reason the IETF should not preclude the ability to co-located 
RP and PE.

> - I  cannot believe  that "PE  as RP"  is really  going to  be  the superior
>   "outsourced RP" deployment model at scale.  

"I cannot believe" is not a technical argument.

Yakov.




From l3vpn-bounces@ietf.org Tue Dec 18 15:00:38 2007
Return-path: <l3vpn-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1J4icF-0007sq-V9; Tue, 18 Dec 2007 15:00:35 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1J4icD-0007si-Jn
	for l3vpn@ietf.org; Tue, 18 Dec 2007 15:00:33 -0500
Received: from exprod7og103.obsmtp.com ([64.18.2.159])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1J4icC-0001SU-UA
	for l3vpn@ietf.org; Tue, 18 Dec 2007 15:00:33 -0500
Received: from source ([66.129.224.36]) by exprod7ob103.postini.com
	([64.18.6.12]) with SMTP; Tue, 18 Dec 2007 12:00:27 PST
Received: from magenta.juniper.net ([172.17.27.123]) by emailsmtp55.jnpr.net
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 18 Dec 2007 12:00:17 -0800
Received: from juniper.net (sapphire.juniper.net [172.17.28.108])
	by magenta.juniper.net (8.11.3/8.11.3) with ESMTP id lBIK0HE97000;
	Tue, 18 Dec 2007 12:00:17 -0800 (PST)
	(envelope-from yakov@juniper.net)
Message-Id: <200712182000.lBIK0HE97000@magenta.juniper.net>
To: "NAPIERALA, MARIA H, ATTLABS" <mnapierala@att.com>
In-Reply-To: Your message of "Tue, 18 Dec 2007 11:34:14 CST."
	<7AFE40EF30EE754DA967D1B5968457CA1381BFD2@KCCLUST06EVS1.ugd.att.com> 
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <12464.1198008017.1@juniper.net>
Date: Tue, 18 Dec 2007 12:00:17 -0800
From: Yakov Rekhter <yakov@juniper.net>
X-OriginalArrivalTime: 18 Dec 2007 20:00:17.0327 (UTC)
	FILETIME=[9C5A43F0:01C841B0]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4b800b1eab964a31702fa68f1ff0e955
Cc: Thomas Morin <thomas.morin@orange-ftgroup.com>, l3vpn@ietf.org
Subject: Re: draft-morin-l3vpn-mvpn-considerations 
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>
Errors-To: l3vpn-bounces@ietf.org

Maria,

> Hi Thomas,
> thanks for the reply. See my responses in-line.

see in-line...

> Maria 
> 
> -----Original Message-----
> From: Thomas Morin [mailto:thomas.morin@orange-ftgroup.com] 
> Sent: Monday, December 17, 2007 5:01 PM
> To: NAPIERALA, MARIA H, ATTLABS
> Cc: Ron Bonica; l3vpn@ietf.org
> Subject: RE: draft-morin-l3vpn-mvpn-considerations
> 
> Hi Maria,
> 
> NAPIERALA, MARIA H, ATTLABS wrote:
> > The draft is a very good start but there are still some outstanding
> > mandatory design aspects that need to be addressed: 
> > - support of non-static RP solutions like BSR. There are current large
> > MVPNs in SP network that use BSR
> 
> I agree (see reply to Eric) that our draft can mention BSR support.
> There is only one currently proposed approach for BSR support, applying
> to both the Full PIM peering approach and the BGP approach, so there
> isn't that much to "compare", but the current requirement for MI-PMSI
> for BSR support, even in the case where BGP is used for C-multicast
> routing, has to be mentioned.
> 
> <maria> yes, I agree. The need for MI-PMSI should be stated as the only
> currently available solution for BSR. 

There is a way to support BSR without using MI-PMSI. As I mentioned
in my reply to Eric's original e-mail, supporting BSR without MI-PMSI
has been explained in the presentation at the L3VPN WG meeting. The
authors of 

> Since there are existing MVPN
> deployments that use BSR, it needs to be supported.

I agree that BSR certainly has to be supported. But that does not 
mean that supporting BSR requires MI-PMSI.

> > - what is still missing in this draft as well as in RFC4834 is the
> > requirement to support PIM Bidir on CE-PE links. This requirement is
> > coming, e.g., from large financial firms for which using PIM-SM for
> > certain business critical applications does not scale. Not to mention
> > the SP :-))
> > - support of "PIM-like" Anycast-RP by allowing multiple RP's to send
> > traffic in parallel 
> 
> The two points above would look to me as belonging to the mvpn
> requirement document (RFC4834). 
> 
> <maria> actually, those requirements are already stated in
> draft-mnapierala-mvpn-part-reqt-00.
> 
> The requirement for CE-PE bidir-PIM is actually already in that
> document. 
> 
> <maria> that's true but RFC4834 only "recommends" PIM-Bidir support on
> PE-CE interfaces. The draft-mnapierala-mvpn-part-req makes it a
> requirement. We have many large VPN customers requiring it.

Changing "recommends" to something else has to do with changing
rfc4834, not with draft-morin-l3vpn-mvpn-considerations.
  
Yakov.




From l3vpn-bounces@ietf.org Tue Dec 18 15:10:58 2007
Return-path: <l3vpn-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1J4imF-0006V7-Ez; Tue, 18 Dec 2007 15:10:55 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1J4imD-0006Ux-U6
	for l3vpn@ietf.org; Tue, 18 Dec 2007 15:10:53 -0500
Received: from mail203.messagelabs.com ([216.82.254.243])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1J4imD-0001mq-8j
	for l3vpn@ietf.org; Tue, 18 Dec 2007 15:10:53 -0500
X-VirusChecked: Checked
X-Env-Sender: mnapierala@att.com
X-Msg-Ref: server-11.tower-203.messagelabs.com!1198008651!1128407!1
X-StarScan-Version: 5.5.12.14.2; banners=-,-,-
X-Originating-IP: [144.160.20.54]
Received: (qmail 11678 invoked from network); 18 Dec 2007 20:10:52 -0000
Received: from sbcsmtp7.sbc.com (HELO mlpi135.enaf.sfdc.sbc.com)
	(144.160.20.54)
	by server-11.tower-203.messagelabs.com with AES256-SHA encrypted SMTP;
	18 Dec 2007 20:10:52 -0000
Received: from enaf.sfdc.sbc.com (localhost.localdomain [127.0.0.1])
	by mlpi135.enaf.sfdc.sbc.com (8.14.0/8.14.0) with ESMTP id
	lBIKApxK013607; Tue, 18 Dec 2007 15:10:51 -0500
Received: from kcclust06evs1.ugd.att.com (kcst11.ugd.att.com [135.38.164.88])
	by mlpi135.enaf.sfdc.sbc.com (8.14.0/8.14.0) with ESMTP id
	lBIKAiFC013548; Tue, 18 Dec 2007 15:10:45 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 18 Dec 2007 14:10:44 -0600
Message-ID: <7AFE40EF30EE754DA967D1B5968457CA1381BFD6@KCCLUST06EVS1.ugd.att.com>
In-Reply-To: <200712182000.lBIK0HE97000@magenta.juniper.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: draft-morin-l3vpn-mvpn-considerations 
Thread-Index: AchBsK4zDXI4AnvYQGuUjeXpSdmuZQAAQ7/A
References: Your message of "Tue, 18 Dec 2007 11:34:14 CST."
	<7AFE40EF30EE754DA967D1B5968457CA1381BFD2@KCCLUST06EVS1.ugd.att.com>
	<200712182000.lBIK0HE97000@magenta.juniper.net>
From: "NAPIERALA, MARIA H, ATTLABS" <mnapierala@att.com>
To: "Yakov Rekhter" <yakov@juniper.net>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8de5f93cb2b4e3bee75302e9eacc33db
Cc: Thomas Morin <thomas.morin@orange-ftgroup.com>, l3vpn@ietf.org
Subject: RE: draft-morin-l3vpn-mvpn-considerations 
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>
Errors-To: l3vpn-bounces@ietf.org

Yakov,

>There is a way to support BSR without using MI-PMSI. As I mentioned
>in my reply to Eric's original e-mail, supporting BSR without MI-PMSI
>has been explained in the presentation at the L3VPN WG meeting. The
>authors of=20

>I agree that BSR certainly has to be supported. But that does not=20
>mean that supporting BSR requires MI-PMSI.

OK. Is there more information about the specifics of this BSR support?=20

Maria

=20

-----Original Message-----
From: Yakov Rekhter [mailto:yakov@juniper.net]=20
Sent: Tuesday, December 18, 2007 3:00 PM
To: NAPIERALA, MARIA H, ATTLABS
Cc: Thomas Morin; l3vpn@ietf.org
Subject: Re: draft-morin-l3vpn-mvpn-considerations=20

Maria,

> Hi Thomas,
> thanks for the reply. See my responses in-line.

see in-line...

> Maria=20
>=20
> -----Original Message-----
> From: Thomas Morin [mailto:thomas.morin@orange-ftgroup.com]=20
> Sent: Monday, December 17, 2007 5:01 PM
> To: NAPIERALA, MARIA H, ATTLABS
> Cc: Ron Bonica; l3vpn@ietf.org
> Subject: RE: draft-morin-l3vpn-mvpn-considerations
>=20
> Hi Maria,
>=20
> NAPIERALA, MARIA H, ATTLABS wrote:
> > The draft is a very good start but there are still some outstanding
> > mandatory design aspects that need to be addressed:=20
> > - support of non-static RP solutions like BSR. There are current
large
> > MVPNs in SP network that use BSR
>=20
> I agree (see reply to Eric) that our draft can mention BSR support.
> There is only one currently proposed approach for BSR support,
applying
> to both the Full PIM peering approach and the BGP approach, so there
> isn't that much to "compare", but the current requirement for MI-PMSI
> for BSR support, even in the case where BGP is used for C-multicast
> routing, has to be mentioned.
>=20
> <maria> yes, I agree. The need for MI-PMSI should be stated as the
only
> currently available solution for BSR.=20

There is a way to support BSR without using MI-PMSI. As I mentioned
in my reply to Eric's original e-mail, supporting BSR without MI-PMSI
has been explained in the presentation at the L3VPN WG meeting. The
authors of=20

> Since there are existing MVPN
> deployments that use BSR, it needs to be supported.

I agree that BSR certainly has to be supported. But that does not=20
mean that supporting BSR requires MI-PMSI.

> > - what is still missing in this draft as well as in RFC4834 is the
> > requirement to support PIM Bidir on CE-PE links. This requirement is
> > coming, e.g., from large financial firms for which using PIM-SM for
> > certain business critical applications does not scale. Not to
mention
> > the SP :-))
> > - support of "PIM-like" Anycast-RP by allowing multiple RP's to send
> > traffic in parallel=20
>=20
> The two points above would look to me as belonging to the mvpn
> requirement document (RFC4834).=20
>=20
> <maria> actually, those requirements are already stated in
> draft-mnapierala-mvpn-part-reqt-00.
>=20
> The requirement for CE-PE bidir-PIM is actually already in that
> document.=20
>=20
> <maria> that's true but RFC4834 only "recommends" PIM-Bidir support on
> PE-CE interfaces. The draft-mnapierala-mvpn-part-req makes it a
> requirement. We have many large VPN customers requiring it.

Changing "recommends" to something else has to do with changing
rfc4834, not with draft-morin-l3vpn-mvpn-considerations.
 =20
Yakov.




From l3vpn-bounces@ietf.org Wed Dec 19 04:36:13 2007
Return-path: <l3vpn-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1J4vLX-0007I9-DF; Wed, 19 Dec 2007 04:36:11 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1J4vLW-0007I4-UD
	for l3vpn@ietf.org; Wed, 19 Dec 2007 04:36:11 -0500
Received: from p-mail1.rd.francetelecom.com ([195.101.245.15])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1J4vLV-0002A3-Ot
	for l3vpn@ietf.org; Wed, 19 Dec 2007 04:36:10 -0500
Received: from ftrdmel10.rd.francetelecom.fr ([10.193.117.156]) by
	ftrdsmtp1.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 19 Dec 2007 10:35:40 +0100
Received: from [10.193.15.109] ([10.193.15.109]) by
	ftrdmel10.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 19 Dec 2007 10:36:04 +0100
From: Thomas Morin <thomas.morin@orange-ftgroup.com>
To: "NAPIERALA, MARIA H, ATTLABS" <mnapierala@att.com>
In-Reply-To: <7AFE40EF30EE754DA967D1B5968457CA1381BFD2@KCCLUST06EVS1.ugd.att.com>
References: <7AFE40EF30EE754DA967D1B5968457CA1381BFD2@KCCLUST06EVS1.ugd.att.com>
Content-Type: text/plain
Organization: France Telecom R&D - Orange
Date: Wed, 19 Dec 2007 10:36:04 +0100
Message-Id: <1198056964.5281.40.camel@wintermute>
Mime-Version: 1.0
X-Mailer: Evolution 2.12.2 
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 19 Dec 2007 09:36:04.0571 (UTC)
	FILETIME=[932EFAB0:01C84222]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 03fb21b15d5177c512a4caa19876f30a
Cc: l3vpn@ietf.org
Subject: RE: draft-morin-l3vpn-mvpn-considerations
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>
Errors-To: l3vpn-bounces@ietf.org

Hi Maria,

NAPIERALA, MARIA H, ATTLABS :
>
> > > - what is still missing in this draft as well as in RFC4834 is the
> > > requirement to support PIM Bidir on CE-PE links. This requirement
> > > is coming, e.g., from large financial firms for which using PIM-SM
> > > for certain business critical applications does not scale. Not to
> > > mention the SP :-))
> > > - support of "PIM-like" Anycast-RP by allowing multiple RP's to
> > > send traffic in parallel 
> > 
> > The two points above would look to me as belonging to the mvpn
> > requirement document (RFC4834). 
> > [...]
>
> <maria>
> that's true but RFC4834 only "recommends" PIM-Bidir support on 
> interfaces. The draft-mnapierala-mvpn-part-req makes it a
> requirement. We have many large VPN customers requiring it.

If you have the need to drive new or different requirement than the ones
defined in RFC4834, after a quite long process and a survey aiming at,
among other things, identifying the different levels of requirements for
CE-PE PIM variants, then this is a different matter than what
draft-mvpn-considerations proposes to do.



> > The way of supporting bidir-PIM is definitely distinct in the
> > BGP approach and in the Full PIM peering approach, but it seems to
> > me that both should be able to support it. Do you think that
> > mvpn-consideration should discuss the relative advantage of the
> > different proposals for bidir-PIM support ?
> 
> <maria> Definitely.

Well, then please contribute by detailing what differences between the
different proposals for bidir-PIM support make one of these
better/worse, from the VPN customer perspective and/or provider
perspective.


> > For the other requirement, the better is probably to explain to
> > solution draft authors, what would be the need. Do you think that it
> > could help distinguish one of the proposed approaches ?
> 
> <maria> surely. 
> Some of the argumentation from a service provider point of view is in
> draft-mnapierala-mvpn-part-reqt.

After reading draft-mnapierala-mvpn-part-reqt, nothing makes it obvious
that your requirement would be easily met nor by the BGP-based approach
or the Full PIM peering approach for C-multicast routing.

It will really be helpful if you can detail your idea that this new
requirement would be differently addressed/not-addressed by the BGP or
the PIM approach, or by different ways of signaling S-PMSI.


> > > - the recommended approach for a source PE to decide when to start
> > > transmitting customer multicast traffic on a S-PMSI (namely, the
> > > source PE waits for a pre-configured period of time) is not
> > > satisfactory in my opinion. A different approach is proposed in
> > > draft-mnapierala-mvpn-rev-03
> > 
> > Is this something mvpn-consideration should talk about to help
> > distinguish a better approach among the proposed ones ?
> 
> <maria> I think so. There are multiple approaches and they should be
> compared in this aspect. 

It would really be nice if you can expand more...

As far as I know "waiting for some pre-configured period of time before
transmitting traffic" is _common_ to both the BGP-based S-PMSI signaling
and to the UDP-based S-PMSI signaling, just because some signaling has
to reach all PEs before the PE signaling the S-PMSI can use it.  How
would your specific need/proposal help the working group elect one of
the proposed approach ?


> > > Also, I would suggest that "co-located RP" recommendation is
> > > removed from the document. Co-locating C-RP on PE should not be
> > > positioned as a
> > > mandatory mechanism in MVPN, which this draft is addressing.
> > 
> > As I said earlier, mvpn-considerations does not at all push this
> > feature as mandatory at all.
> 
> <maria>  What confused me is, quoting from the draft section 1: 
> "The aim of this document is to leverage the already expressed
> requirements [RFC4834] to identify the mechanisms that the authors
> believe are good candidates for being part of a core set of MANDATORY
> mechanisms which can be used to provide a base for interoperable
> solutions." (my underline of "mandatory").
> 
> I also think that in a "big scheme of things" co-locating C-RP with PE
> is an insignificant recommendation... This is already supported by
> vendors and if a service provider wants to use it, it is free to do so
> :-)
 
Ok, so I see there was indeed some confusion.
I think that it is now clarified that providing the RP-colocation
feature was never recommended as a mandatory mechanism.
We will further clarify that point in next revision.

Cheers,

-Thomas




> > > -) ---------- Forwarded message ----------
> > > -) Date: Mon, 10 Dec 2007 16:11:28 -0500
> > > -) From: Ron Bonica <rbonica@juniper.net>
> > > -) To: l3vpn@ietf.org
> > > -) Subject: draft-morin-l3vpn-mvpn-considerations
> > > -) 
> > > -) Folks,
> > > -) 
> > > -) Unless I hear an objection before COB Friday, this document will
> > > become
> > > -) a WG draft.
> > > -) 
> > > -)                                       Ron
> > > -) 
> > > 
> > > 
> > 
>
> Hi Maria,
> 
> NAPIERALA, MARIA H, ATTLABS wrote:
> > The draft is a very good start but there are still some outstanding
> > mandatory design aspects that need to be addressed: 
> > - support of non-static RP solutions like BSR. There are current large
> > MVPNs in SP network that use BSR
> 
> I agree (see reply to Eric) that our draft can mention BSR support.
> There is only one currently proposed approach for BSR support, applying
> to both the Full PIM peering approach and the BGP approach, so there
> isn't that much to "compare", but the current requirement for MI-PMSI
> for BSR support, even in the case where BGP is used for C-multicast
> routing, has to be mentioned.
> 
> <maria> yes, I agree. The need for MI-PMSI should be stated as the only
> currently available solution for BSR. Since there are existing MVPN
> deployments that use BSR, it needs to be supported.
> 
> > - what is still missing in this draft as well as in RFC4834 is the
> > requirement to support PIM Bidir on CE-PE links. This requirement is
> > coming, e.g., from large financial firms for which using PIM-SM for
> > certain business critical applications does not scale. Not to mention
> > the SP :-))
> > - support of "PIM-like" Anycast-RP by allowing multiple RP's to send
> > traffic in parallel 
> 
> The two points above would look to me as belonging to the mvpn
> requirement document (RFC4834). 
> 
> <maria> actually, those requirements are already stated in
> draft-mnapierala-mvpn-part-reqt-00.
> 
> The requirement for CE-PE bidir-PIM is actually already in that
> document. 
> 
> <maria> that's true but RFC4834 only "recommends" PIM-Bidir support on
> PE-CE interfaces. The draft-mnapierala-mvpn-part-req makes it a
> requirement. We have many large VPN customers requiring it.
> 
> The way of supporting bidir-PIM is definitely distinct in the
> BGP approach and in the Full PIM peering approach, but it seems to me
> that both should be able to support it. Do you think that
> mvpn-consideration should discuss the relative advantage of the
> different proposals for bidir-PIM support ?
> 
> <maria> Definitely.
> 
> For the other requirement, the better is probably to explain to solution
> draft authors, what would be the need. Do you think that it could help
> distinguish one of the proposed approaches ?
> 
> <maria> surely. Some of the argumentation from a service provider point
> of view is in draft-mnapierala-mvpn-part-reqt.
> 
> > - the recommended approach for a source PE to decide when to start
> > transmitting customer multicast traffic on a S-PMSI (namely, the
> source
> > PE waits for a pre-configured period of time) is not satisfactory in
> my
> > opinion. A different approach is proposed in
> > draft-mnapierala-mvpn-rev-03
> 
> Is this something mvpn-consideration should talk about to help
> distinguish a better approach among the proposed ones ?
> 
> <maria> I think so. There are multiple approaches and they should be
> compared in this aspect. 
> 
> > Also, I would suggest that "co-located RP" recommendation is removed
> > from the document. Co-locating C-RP on PE should not be positioned as
> a
> > mandatory mechanism in MVPN, which this draft is addressing.
> 
> As I said earlier, mvpn-considerations does not at all push this feature
> as mandatory at all.
> 
> <maria>  What confused me is, quoting from the draft section 1: 
> "The aim of this document is to leverage the already expressed
> requirements [RFC4834] to identify the mechanisms that the authors
> believe are good candidates for being part of a core set of MANDATORY
> mechanisms which can be used to provide a base for interoperable
> solutions." (my underline of "mandatory").
> I also think that in a "big scheme of things" co-locating C-RP with PE
> is an insignificant recommendation... This is already supported by
> vendors and if a service provider wants to use it, it is free to do so
> :-)
>  
> 
> > I might have comments but wanted to send those COB today. 
> 
> As I told you in Prague, your comments and contributions to this draft
> are always welcome. 
> 
> <maria> surely!
> 
> Thanks,
> 
> -Thomas
> 
> 
> 
> > -) ---------- Forwarded message ----------
> > -) Date: Mon, 10 Dec 2007 16:11:28 -0500
> > -) From: Ron Bonica <rbonica@juniper.net>
> > -) To: l3vpn@ietf.org
> > -) Subject: draft-morin-l3vpn-mvpn-considerations
> > -) 
> > -) Folks,
> > -) 
> > -) Unless I hear an objection before COB Friday, this document will
> > become
> > -) a WG draft.
> > -) 
> > -)                                       Ron
> > -) 
> > 
> > 
> 





From l3vpn-bounces@ietf.org Wed Dec 19 04:47:13 2007
Return-path: <l3vpn-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1J4vW9-0001y4-CO; Wed, 19 Dec 2007 04:47:09 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1J4vW7-0001xx-Sv
	for l3vpn@ietf.org; Wed, 19 Dec 2007 04:47:07 -0500
Received: from p-mail1.rd.francetelecom.com ([195.101.245.15])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1J4vW7-00082z-CQ
	for l3vpn@ietf.org; Wed, 19 Dec 2007 04:47:07 -0500
Received: from ftrdmel10.rd.francetelecom.fr ([10.193.117.156]) by
	ftrdsmtp2.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 19 Dec 2007 10:47:03 +0100
Received: from [10.193.15.109] ([10.193.15.109]) by
	ftrdmel10.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 19 Dec 2007 10:47:02 +0100
From: Thomas Morin <thomas.morin@orange-ftgroup.com>
To: Yakov Rekhter <yakov@juniper.net>
In-Reply-To: <200712182000.lBIK0HE97000@magenta.juniper.net>
References: <200712182000.lBIK0HE97000@magenta.juniper.net>
Content-Type: text/plain
Organization: France Telecom R&D - Orange
Date: Wed, 19 Dec 2007 10:47:02 +0100
Message-Id: <1198057622.5281.50.camel@wintermute>
Mime-Version: 1.0
X-Mailer: Evolution 2.12.2 
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 19 Dec 2007 09:47:02.0759 (UTC)
	FILETIME=[1B7E7F70:01C84224]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17
Cc: l3vpn@ietf.org
Subject: Re: draft-morin-l3vpn-mvpn-considerations
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>
Errors-To: l3vpn-bounces@ietf.org

Yakov Rekhter :
>
> > NAPIERALA, MARIA H, ATTLABS wrote:
> > > The draft is a very good start but there are still some outstanding
> > > mandatory design aspects that need to be addressed: 
> > > - support of non-static RP solutions like BSR. There are current large
> > > MVPNs in SP network that use BSR
> > 
> > I agree (see reply to Eric) that our draft can mention BSR support.
> > There is only one currently proposed approach for BSR support, applying
> > to both the Full PIM peering approach and the BGP approach, so there
> > isn't that much to "compare", but the current requirement for MI-PMSI
> > for BSR support, even in the case where BGP is used for C-multicast
> > routing, has to be mentioned.
>  
> maria> yes, I agree. The need for MI-PMSI should be stated as the only
> maria> currently available solution for BSR. 
> 
> There is a way to support BSR without using MI-PMSI. As I mentioned
> in my reply to Eric's original e-mail, supporting BSR without MI-PMSI
> has been explained in the presentation at the L3VPN WG meeting. 

Yakov, mvpn-considerations cannot definitely not take into account stuff
that is not fully described yet.

Until a mechanism like the one is proposed, it is logical to state that
"current proposed approaches require an MI-PMSI for BSR support" and
update the section of mvpn-consideration talking about MI-PMSI in this
respect.  That can (and will) obviously be updated later if proposal to
do BSR without an MI-PMSI are made.

Thanks,

-Thomas





From l3vpn-bounces@ietf.org Wed Dec 19 11:47:41 2007
Return-path: <l3vpn-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1J5249-0005yR-A6; Wed, 19 Dec 2007 11:46:41 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1J5248-0005yL-8b
	for l3vpn@ietf.org; Wed, 19 Dec 2007 11:46:40 -0500
Received: from mail120.messagelabs.com ([216.82.250.83])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1J5246-0006qb-U5
	for l3vpn@ietf.org; Wed, 19 Dec 2007 11:46:40 -0500
X-VirusChecked: Checked
X-Env-Sender: mnapierala@att.com
X-Msg-Ref: server-8.tower-120.messagelabs.com!1198082795!22021514!1
X-StarScan-Version: 5.5.12.14.2; banners=-,-,-
X-Originating-IP: [144.160.20.54]
Received: (qmail 14529 invoked from network); 19 Dec 2007 16:46:36 -0000
Received: from sbcsmtp7.sbc.com (HELO mlpi135.enaf.sfdc.sbc.com)
	(144.160.20.54)
	by server-8.tower-120.messagelabs.com with AES256-SHA encrypted SMTP;
	19 Dec 2007 16:46:36 -0000
Received: from enaf.sfdc.sbc.com (localhost.localdomain [127.0.0.1])
	by mlpi135.enaf.sfdc.sbc.com (8.14.0/8.14.0) with ESMTP id
	lBJGkZTx030288 for <l3vpn@ietf.org>; Wed, 19 Dec 2007 11:46:35 -0500
Received: from kcclust06evs1.ugd.att.com (kcst11.ugd.att.com [135.38.164.88])
	by mlpi135.enaf.sfdc.sbc.com (8.14.0/8.14.0) with ESMTP id
	lBJGkUeO030248 for <l3vpn@ietf.org>; Wed, 19 Dec 2007 11:46:30 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 19 Dec 2007 10:46:29 -0600
Message-ID: <7AFE40EF30EE754DA967D1B5968457CA1381BFE7@KCCLUST06EVS1.ugd.att.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: draft-morin-l3vpn-mvpn-considerations
Thread-Index: AchCIphCVlrpQPb3RF+0/dF5Seg37gALVOhgAANj09A=
From: "NAPIERALA, MARIA H, ATTLABS" <mnapierala@att.com>
To: "Thomas Morin" <thomas.morin@orange-ftgroup.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cbb41f2dbf0f142369614756642005e3
Cc: l3vpn@ietf.org
Subject: FW: draft-morin-l3vpn-mvpn-considerations
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>
Errors-To: l3vpn-bounces@ietf.org

Hi Thomas,
Please see in-line..

Maria

-----Original Message-----
From: Thomas Morin [mailto:thomas.morin@orange-ftgroup.com]=20
Sent: Wednesday, December 19, 2007 4:36 AM
To: NAPIERALA, MARIA H, ATTLABS
Cc: l3vpn@ietf.org
Subject: RE: draft-morin-l3vpn-mvpn-considerations

Hi Maria,

NAPIERALA, MARIA H, ATTLABS :
>
> > > - what is still missing in this draft as well as in RFC4834 is the
> > > requirement to support PIM Bidir on CE-PE links. This requirement
> > > is coming, e.g., from large financial firms for which using PIM-SM
> > > for certain business critical applications does not scale. Not to
> > > mention the SP :-))
> > > - support of "PIM-like" Anycast-RP by allowing multiple RP's to
> > > send traffic in parallel=20
> >=20
> > The two points above would look to me as belonging to the mvpn
> > requirement document (RFC4834).=20
> > [...]
>
> <maria>
> that's true but RFC4834 only "recommends" PIM-Bidir support on=20
> interfaces. The draft-mnapierala-mvpn-part-req makes it a
> requirement. We have many large VPN customers requiring it.

If you have the need to drive new or different requirement than the ones
defined in RFC4834, after a quite long process and a survey aiming at,
among other things, identifying the different levels of requirements for
CE-PE PIM variants, then this is a different matter than what
draft-mvpn-considerations proposes to do.

<maria> Thomas, I just want to make sure that PIM-Bidir is a requirement
for MVPN. If this is not part of RFC4843 then it has to stand on its own
in draft-mnapierala-mvpn-part-req. If draft-mvpn-considerations has no
intention to refer to draft-mnapierala-mvpn-part-req then it cannot
represent all SP's (at least not the one I work for).


> > The way of supporting bidir-PIM is definitely distinct in the
> > BGP approach and in the Full PIM peering approach, but it seems to
> > me that both should be able to support it. Do you think that
> > mvpn-consideration should discuss the relative advantage of the
> > different proposals for bidir-PIM support ?
>=20
> <maria> Definitely.

Well, then please contribute by detailing what differences between the
different proposals for bidir-PIM support make one of these
better/worse, from the VPN customer perspective and/or provider
perspective.

<maria> I can definitely do that provided that my above comment is
addressed. Otherwise it would not make much sense to address it in
draft-mvpn-considerations.

> > For the other requirement, the better is probably to explain to
> > solution draft authors, what would be the need. Do you think that it
> > could help distinguish one of the proposed approaches ?
>=20
> <maria> surely.=20
> Some of the argumentation from a service provider point of view is in
> draft-mnapierala-mvpn-part-reqt.

After reading draft-mnapierala-mvpn-part-reqt, nothing makes it obvious
that your requirement would be easily met nor by the BGP-based approach
or the Full PIM peering approach for C-multicast routing.

<maria> My requirement for PIM Bidir (as well as any other PIM mode)
calls for independence from inter-PE multicast signaling protocol. Such
solution is specified in draft-mnapierala-mvpn-rev-03.

It will really be helpful if you can detail your idea that this new
requirement would be differently addressed/not-addressed by the BGP or
the PIM approach, or by different ways of signaling S-PMSI.

<maria> I can do that.=20

> > > - the recommended approach for a source PE to decide when to start
> > > transmitting customer multicast traffic on a S-PMSI (namely, the
> > > source PE waits for a pre-configured period of time) is not
> > > satisfactory in my opinion. A different approach is proposed in
> > > draft-mnapierala-mvpn-rev-03
> >=20
> > Is this something mvpn-consideration should talk about to help
> > distinguish a better approach among the proposed ones ?
>=20
> <maria> I think so. There are multiple approaches and they should be
> compared in this aspect.=20

It would really be nice if you can expand more...

As far as I know "waiting for some pre-configured period of time before
transmitting traffic" is _common_ to both the BGP-based S-PMSI signaling
and to the UDP-based S-PMSI signaling, just because some signaling has
to reach all PEs before the PE signaling the S-PMSI can use it.  How
would your specific need/proposal help the working group elect one of
the proposed approach ?

<maria> this requires more elaboration because it has to do with an
entire procedure defined in draft-mnapierala-mvpn-rev-03. The gist of it
is that a PE attached to C-S starts transmitting traffic on S-PMSI
announced for C-S once it received the 1st (C-S, C-G) join. The PE's
attached to receivers join the S-PMSI once the advertisement from the
ingress PE is received.=20

> > > Also, I would suggest that "co-located RP" recommendation is
> > > removed from the document. Co-locating C-RP on PE should not be
> > > positioned as a
> > > mandatory mechanism in MVPN, which this draft is addressing.
> >=20
> > As I said earlier, mvpn-considerations does not at all push this
> > feature as mandatory at all.
>=20
> <maria>  What confused me is, quoting from the draft section 1:=20
> "The aim of this document is to leverage the already expressed
> requirements [RFC4834] to identify the mechanisms that the authors
> believe are good candidates for being part of a core set of MANDATORY
> mechanisms which can be used to provide a base for interoperable
> solutions." (my underline of "mandatory").
>=20
> I also think that in a "big scheme of things" co-locating C-RP with PE
> is an insignificant recommendation... This is already supported by
> vendors and if a service provider wants to use it, it is free to do so
> :-)
=20
Ok, so I see there was indeed some confusion.
I think that it is now clarified that providing the RP-colocation
feature was never recommended as a mandatory mechanism.
We will further clarify that point in next revision.

Cheers,

-Thomas




> > > -) ---------- Forwarded message ----------
> > > -) Date: Mon, 10 Dec 2007 16:11:28 -0500
> > > -) From: Ron Bonica <rbonica@juniper.net>
> > > -) To: l3vpn@ietf.org
> > > -) Subject: draft-morin-l3vpn-mvpn-considerations
> > > -)=20
> > > -) Folks,
> > > -)=20
> > > -) Unless I hear an objection before COB Friday, this document
will
> > > become
> > > -) a WG draft.
> > > -)=20
> > > -)                                       Ron
> > > -)=20
> > >=20
> > >=20
> >=20
>
> Hi Maria,
>=20
> NAPIERALA, MARIA H, ATTLABS wrote:
> > The draft is a very good start but there are still some outstanding
> > mandatory design aspects that need to be addressed:=20
> > - support of non-static RP solutions like BSR. There are current
large
> > MVPNs in SP network that use BSR
>=20
> I agree (see reply to Eric) that our draft can mention BSR support.
> There is only one currently proposed approach for BSR support,
applying
> to both the Full PIM peering approach and the BGP approach, so there
> isn't that much to "compare", but the current requirement for MI-PMSI
> for BSR support, even in the case where BGP is used for C-multicast
> routing, has to be mentioned.
>=20
> <maria> yes, I agree. The need for MI-PMSI should be stated as the
only
> currently available solution for BSR. Since there are existing MVPN
> deployments that use BSR, it needs to be supported.
>=20
> > - what is still missing in this draft as well as in RFC4834 is the
> > requirement to support PIM Bidir on CE-PE links. This requirement is
> > coming, e.g., from large financial firms for which using PIM-SM for
> > certain business critical applications does not scale. Not to
mention
> > the SP :-))
> > - support of "PIM-like" Anycast-RP by allowing multiple RP's to send
> > traffic in parallel=20
>=20
> The two points above would look to me as belonging to the mvpn
> requirement document (RFC4834).=20
>=20
> <maria> actually, those requirements are already stated in
> draft-mnapierala-mvpn-part-reqt-00.
>=20
> The requirement for CE-PE bidir-PIM is actually already in that
> document.=20
>=20
> <maria> that's true but RFC4834 only "recommends" PIM-Bidir support on
> PE-CE interfaces. The draft-mnapierala-mvpn-part-req makes it a
> requirement. We have many large VPN customers requiring it.
>=20
> The way of supporting bidir-PIM is definitely distinct in the
> BGP approach and in the Full PIM peering approach, but it seems to me
> that both should be able to support it. Do you think that
> mvpn-consideration should discuss the relative advantage of the
> different proposals for bidir-PIM support ?
>=20
> <maria> Definitely.
>=20
> For the other requirement, the better is probably to explain to
solution
> draft authors, what would be the need. Do you think that it could help
> distinguish one of the proposed approaches ?
>=20
> <maria> surely. Some of the argumentation from a service provider
point
> of view is in draft-mnapierala-mvpn-part-reqt.
>=20
> > - the recommended approach for a source PE to decide when to start
> > transmitting customer multicast traffic on a S-PMSI (namely, the
> source
> > PE waits for a pre-configured period of time) is not satisfactory in
> my
> > opinion. A different approach is proposed in
> > draft-mnapierala-mvpn-rev-03
>=20
> Is this something mvpn-consideration should talk about to help
> distinguish a better approach among the proposed ones ?
>=20
> <maria> I think so. There are multiple approaches and they should be
> compared in this aspect.=20
>=20
> > Also, I would suggest that "co-located RP" recommendation is removed
> > from the document. Co-locating C-RP on PE should not be positioned
as
> a
> > mandatory mechanism in MVPN, which this draft is addressing.
>=20
> As I said earlier, mvpn-considerations does not at all push this
feature
> as mandatory at all.
>=20
> <maria>  What confused me is, quoting from the draft section 1:=20
> "The aim of this document is to leverage the already expressed
> requirements [RFC4834] to identify the mechanisms that the authors
> believe are good candidates for being part of a core set of MANDATORY
> mechanisms which can be used to provide a base for interoperable
> solutions." (my underline of "mandatory").
> I also think that in a "big scheme of things" co-locating C-RP with PE
> is an insignificant recommendation... This is already supported by
> vendors and if a service provider wants to use it, it is free to do so
> :-)
> =20
>=20
> > I might have comments but wanted to send those COB today.=20
>=20
> As I told you in Prague, your comments and contributions to this draft
> are always welcome.=20
>=20
> <maria> surely!
>=20
> Thanks,
>=20
> -Thomas
>=20
>=20
>=20
> > -) ---------- Forwarded message ----------
> > -) Date: Mon, 10 Dec 2007 16:11:28 -0500
> > -) From: Ron Bonica <rbonica@juniper.net>
> > -) To: l3vpn@ietf.org
> > -) Subject: draft-morin-l3vpn-mvpn-considerations
> > -)=20
> > -) Folks,
> > -)=20
> > -) Unless I hear an objection before COB Friday, this document will
> > become
> > -) a WG draft.
> > -)=20
> > -)                                       Ron
> > -)=20
> >=20
> >=20
>=20





From l3vpn-bounces@ietf.org Wed Dec 19 14:40:55 2007
Return-path: <l3vpn-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1J54me-0002cO-Up; Wed, 19 Dec 2007 14:40:48 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1J54md-0002cI-QQ
	for l3vpn@ietf.org; Wed, 19 Dec 2007 14:40:47 -0500
Received: from stl-smtpout-01.boeing.com ([130.76.96.56])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1J54mc-00039S-K6
	for l3vpn@ietf.org; Wed, 19 Dec 2007 14:40:47 -0500
Received: from stl-av-01.boeing.com (stl-av-01.boeing.com [192.76.190.6])
	by stl-smtpout-01.ns.cs.boeing.com (8.14.0/8.14.0/8.14.0/SMTPOUT) with
	ESMTP id lBJJeWYR006395
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK);
	Wed, 19 Dec 2007 13:40:37 -0600 (CST)
Received: from stl-av-01.boeing.com (localhost [127.0.0.1])
	by stl-av-01.boeing.com (8.14.0/8.14.0/DOWNSTREAM_RELAY) with ESMTP id
	lBJJeWcq024366; Wed, 19 Dec 2007 13:40:32 -0600 (CST)
Received: from xch-swbh-11.sw.nos.boeing.com (xch-swbh-11.sw.nos.boeing.com
	[129.172.192.157])
	by stl-av-01.boeing.com (8.14.0/8.14.0/UPSTREAM_RELAY) with ESMTP id
	lBJJeWeG024345; Wed, 19 Dec 2007 13:40:32 -0600 (CST)
Received: from XCH-SW-5V2.sw.nos.boeing.com ([129.172.193.50]) by
	xch-swbh-11.sw.nos.boeing.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 19 Dec 2007 11:40:32 -0800
x-mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 19 Dec 2007 11:40:32 -0800
Message-ID: <51661468CBD1354294533DA79E85955A082017@XCH-SW-5V2.sw.nos.boeing.com>
In-Reply-To: <7AFE40EF30EE754DA967D1B5968457CA1381BFE7@KCCLUST06EVS1.ugd.att.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: draft-morin-l3vpn-mvpn-considerations
Thread-Index: AchCIphCVlrpQPb3RF+0/dF5Seg37gALVOhgAANj09AABlAMwA==
References: <7AFE40EF30EE754DA967D1B5968457CA1381BFE7@KCCLUST06EVS1.ugd.att.com>
From: "Drake, John E" <John.E.Drake2@boeing.com>
To: "NAPIERALA, MARIA H, ATTLABS" <mnapierala@att.com>,
	"Thomas Morin" <thomas.morin@orange-ftgroup.com>
X-OriginalArrivalTime: 19 Dec 2007 19:40:32.0149 (UTC)
	FILETIME=[04583450:01C84277]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 731ea0e9f5725b67e634db1918f3b951
Cc: l3vpn@ietf.org
Subject: RE: draft-morin-l3vpn-mvpn-considerations
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>
Errors-To: l3vpn-bounces@ietf.org

Maria,

Your I-D is not yet even a working group draft.  Would you please stop
asserting that the requirements it contains are in any way binding?

Thanks,

John
>-----Original Message-----
>From: NAPIERALA, MARIA H, ATTLABS [mailto:mnapierala@att.com]=20
>Sent: Wednesday, December 19, 2007 8:46 AM
>To: Thomas Morin
>Cc: l3vpn@ietf.org
>Subject: FW: draft-morin-l3vpn-mvpn-considerations
>
>Hi Thomas,
>Please see in-line..
>
>Maria
>
>-----Original Message-----
>From: Thomas Morin [mailto:thomas.morin@orange-ftgroup.com]
>Sent: Wednesday, December 19, 2007 4:36 AM
>To: NAPIERALA, MARIA H, ATTLABS
>Cc: l3vpn@ietf.org
>Subject: RE: draft-morin-l3vpn-mvpn-considerations
>
>Hi Maria,
>
>NAPIERALA, MARIA H, ATTLABS :
>>
>> > > - what is still missing in this draft as well as in=20
>RFC4834 is the=20
>> > > requirement to support PIM Bidir on CE-PE links. This=20
>requirement=20
>> > > is coming, e.g., from large financial firms for which=20
>using PIM-SM=20
>> > > for certain business critical applications does not=20
>scale. Not to=20
>> > > mention the SP :-))
>> > > - support of "PIM-like" Anycast-RP by allowing multiple RP's to=20
>> > > send traffic in parallel
>> >=20
>> > The two points above would look to me as belonging to the mvpn=20
>> > requirement document (RFC4834).
>> > [...]
>>
>> <maria>
>> that's true but RFC4834 only "recommends" PIM-Bidir support on=20
>> interfaces. The draft-mnapierala-mvpn-part-req makes it a=20
>requirement.=20
>> We have many large VPN customers requiring it.
>
>If you have the need to drive new or different requirement=20
>than the ones defined in RFC4834, after a quite long process=20
>and a survey aiming at, among other things, identifying the=20
>different levels of requirements for CE-PE PIM variants, then=20
>this is a different matter than what draft-mvpn-considerations=20
>proposes to do.
>
><maria> Thomas, I just want to make sure that PIM-Bidir is a=20
>requirement for MVPN. If this is not part of RFC4843 then it=20
>has to stand on its own in draft-mnapierala-mvpn-part-req. If=20
>draft-mvpn-considerations has no intention to refer to=20
>draft-mnapierala-mvpn-part-req then it cannot represent all=20
>SP's (at least not the one I work for).
>
>
>> > The way of supporting bidir-PIM is definitely distinct in the BGP=20
>> > approach and in the Full PIM peering approach, but it seems to me=20
>> > that both should be able to support it. Do you think that=20
>> > mvpn-consideration should discuss the relative advantage of the=20
>> > different proposals for bidir-PIM support ?
>>=20
>> <maria> Definitely.
>
>Well, then please contribute by detailing what differences=20
>between the different proposals for bidir-PIM support make one=20
>of these better/worse, from the VPN customer perspective=20
>and/or provider perspective.
>
><maria> I can definitely do that provided that my above=20
>comment is addressed. Otherwise it would not make much sense=20
>to address it in draft-mvpn-considerations.
>
>> > For the other requirement, the better is probably to explain to=20
>> > solution draft authors, what would be the need. Do you=20
>think that it=20
>> > could help distinguish one of the proposed approaches ?
>>=20
>> <maria> surely.=20
>> Some of the argumentation from a service provider point of=20
>view is in=20
>> draft-mnapierala-mvpn-part-reqt.
>
>After reading draft-mnapierala-mvpn-part-reqt, nothing makes=20
>it obvious that your requirement would be easily met nor by=20
>the BGP-based approach or the Full PIM peering approach for=20
>C-multicast routing.
>
><maria> My requirement for PIM Bidir (as well as any other PIM=20
>mode) calls for independence from inter-PE multicast signaling=20
>protocol. Such solution is specified in draft-mnapierala-mvpn-rev-03.
>
>It will really be helpful if you can detail your idea that=20
>this new requirement would be differently=20
>addressed/not-addressed by the BGP or the PIM approach, or by=20
>different ways of signaling S-PMSI.
>
><maria> I can do that.=20
>
>> > > - the recommended approach for a source PE to decide=20
>when to start=20
>> > > transmitting customer multicast traffic on a S-PMSI (namely, the=20
>> > > source PE waits for a pre-configured period of time) is not=20
>> > > satisfactory in my opinion. A different approach is proposed in
>> > > draft-mnapierala-mvpn-rev-03
>> >=20
>> > Is this something mvpn-consideration should talk about to help=20
>> > distinguish a better approach among the proposed ones ?
>>=20
>> <maria> I think so. There are multiple approaches and they should be=20
>> compared in this aspect.
>
>It would really be nice if you can expand more...
>
>As far as I know "waiting for some pre-configured period of=20
>time before transmitting traffic" is _common_ to both the=20
>BGP-based S-PMSI signaling and to the UDP-based S-PMSI=20
>signaling, just because some signaling has to reach all PEs=20
>before the PE signaling the S-PMSI can use it.  How would your=20
>specific need/proposal help the working group elect one of the=20
>proposed approach ?
>
><maria> this requires more elaboration because it has to do=20
>with an entire procedure defined in=20
>draft-mnapierala-mvpn-rev-03. The gist of it is that a PE=20
>attached to C-S starts transmitting traffic on S-PMSI=20
>announced for C-S once it received the 1st (C-S, C-G) join.=20
>The PE's attached to receivers join the S-PMSI once the=20
>advertisement from the ingress PE is received.=20
>
>> > > Also, I would suggest that "co-located RP" recommendation is=20
>> > > removed from the document. Co-locating C-RP on PE should not be=20
>> > > positioned as a mandatory mechanism in MVPN, which this draft is=20
>> > > addressing.
>> >=20
>> > As I said earlier, mvpn-considerations does not at all push this=20
>> > feature as mandatory at all.
>>=20
>> <maria>  What confused me is, quoting from the draft section 1:=20
>> "The aim of this document is to leverage the already expressed=20
>> requirements [RFC4834] to identify the mechanisms that the authors=20
>> believe are good candidates for being part of a core set of=20
>MANDATORY=20
>> mechanisms which can be used to provide a base for interoperable=20
>> solutions." (my underline of "mandatory").
>>=20
>> I also think that in a "big scheme of things" co-locating=20
>C-RP with PE=20
>> is an insignificant recommendation... This is already supported by=20
>> vendors and if a service provider wants to use it, it is=20
>free to do so
>> :-)
>=20
>Ok, so I see there was indeed some confusion.
>I think that it is now clarified that providing the=20
>RP-colocation feature was never recommended as a mandatory mechanism.
>We will further clarify that point in next revision.
>
>Cheers,
>
>-Thomas
>
>
>
>
>> > > -) ---------- Forwarded message ----------
>> > > -) Date: Mon, 10 Dec 2007 16:11:28 -0500
>> > > -) From: Ron Bonica <rbonica@juniper.net>
>> > > -) To: l3vpn@ietf.org
>> > > -) Subject: draft-morin-l3vpn-mvpn-considerations
>> > > -)
>> > > -) Folks,
>> > > -)
>> > > -) Unless I hear an objection before COB Friday, this document
>will
>> > > become
>> > > -) a WG draft.
>> > > -)=20
>> > > -)                                       Ron
>> > > -)
>> > >=20
>> > >=20
>> >=20
>>
>> Hi Maria,
>>=20
>> NAPIERALA, MARIA H, ATTLABS wrote:
>> > The draft is a very good start but there are still some=20
>outstanding=20
>> > mandatory design aspects that need to be addressed:
>> > - support of non-static RP solutions like BSR. There are current
>large
>> > MVPNs in SP network that use BSR
>>=20
>> I agree (see reply to Eric) that our draft can mention BSR support.
>> There is only one currently proposed approach for BSR support,
>applying
>> to both the Full PIM peering approach and the BGP approach, so there=20
>> isn't that much to "compare", but the current requirement=20
>for MI-PMSI=20
>> for BSR support, even in the case where BGP is used for C-multicast=20
>> routing, has to be mentioned.
>>=20
>> <maria> yes, I agree. The need for MI-PMSI should be stated as the
>only
>> currently available solution for BSR. Since there are existing MVPN=20
>> deployments that use BSR, it needs to be supported.
>>=20
>> > - what is still missing in this draft as well as in RFC4834 is the=20
>> > requirement to support PIM Bidir on CE-PE links. This=20
>requirement is=20
>> > coming, e.g., from large financial firms for which using=20
>PIM-SM for=20
>> > certain business critical applications does not scale. Not to
>mention
>> > the SP :-))
>> > - support of "PIM-like" Anycast-RP by allowing multiple=20
>RP's to send=20
>> > traffic in parallel
>>=20
>> The two points above would look to me as belonging to the mvpn=20
>> requirement document (RFC4834).
>>=20
>> <maria> actually, those requirements are already stated in=20
>> draft-mnapierala-mvpn-part-reqt-00.
>>=20
>> The requirement for CE-PE bidir-PIM is actually already in that=20
>> document.
>>=20
>> <maria> that's true but RFC4834 only "recommends" PIM-Bidir=20
>support on=20
>> PE-CE interfaces. The draft-mnapierala-mvpn-part-req makes it a=20
>> requirement. We have many large VPN customers requiring it.
>>=20
>> The way of supporting bidir-PIM is definitely distinct in the BGP=20
>> approach and in the Full PIM peering approach, but it seems=20
>to me that=20
>> both should be able to support it. Do you think that=20
>> mvpn-consideration should discuss the relative advantage of the=20
>> different proposals for bidir-PIM support ?
>>=20
>> <maria> Definitely.
>>=20
>> For the other requirement, the better is probably to explain to
>solution
>> draft authors, what would be the need. Do you think that it=20
>could help=20
>> distinguish one of the proposed approaches ?
>>=20
>> <maria> surely. Some of the argumentation from a service provider
>point
>> of view is in draft-mnapierala-mvpn-part-reqt.
>>=20
>> > - the recommended approach for a source PE to decide when to start=20
>> > transmitting customer multicast traffic on a S-PMSI (namely, the
>> source
>> > PE waits for a pre-configured period of time) is not=20
>satisfactory in
>> my
>> > opinion. A different approach is proposed in
>> > draft-mnapierala-mvpn-rev-03
>>=20
>> Is this something mvpn-consideration should talk about to help=20
>> distinguish a better approach among the proposed ones ?
>>=20
>> <maria> I think so. There are multiple approaches and they should be=20
>> compared in this aspect.
>>=20
>> > Also, I would suggest that "co-located RP" recommendation=20
>is removed=20
>> > from the document. Co-locating C-RP on PE should not be positioned
>as
>> a
>> > mandatory mechanism in MVPN, which this draft is addressing.
>>=20
>> As I said earlier, mvpn-considerations does not at all push this
>feature
>> as mandatory at all.
>>=20
>> <maria>  What confused me is, quoting from the draft section 1:=20
>> "The aim of this document is to leverage the already expressed=20
>> requirements [RFC4834] to identify the mechanisms that the authors=20
>> believe are good candidates for being part of a core set of=20
>MANDATORY=20
>> mechanisms which can be used to provide a base for interoperable=20
>> solutions." (my underline of "mandatory").
>> I also think that in a "big scheme of things" co-locating=20
>C-RP with PE=20
>> is an insignificant recommendation... This is already supported by=20
>> vendors and if a service provider wants to use it, it is=20
>free to do so
>> :-)
>> =20
>>=20
>> > I might have comments but wanted to send those COB today.=20
>>=20
>> As I told you in Prague, your comments and contributions to=20
>this draft=20
>> are always welcome.
>>=20
>> <maria> surely!
>>=20
>> Thanks,
>>=20
>> -Thomas
>>=20
>>=20
>>=20
>> > -) ---------- Forwarded message ----------
>> > -) Date: Mon, 10 Dec 2007 16:11:28 -0500
>> > -) From: Ron Bonica <rbonica@juniper.net>
>> > -) To: l3vpn@ietf.org
>> > -) Subject: draft-morin-l3vpn-mvpn-considerations
>> > -)
>> > -) Folks,
>> > -)
>> > -) Unless I hear an objection before COB Friday, this=20
>document will=20
>> > become
>> > -) a WG draft.
>> > -)=20
>> > -)                                       Ron
>> > -)
>> >=20
>> >=20
>>=20
>
>
>




From l3vpn-bounces@ietf.org Thu Dec 20 08:03:04 2007
Return-path: <l3vpn-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1J5L32-00019i-8D; Thu, 20 Dec 2007 08:02:48 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1J5L30-00019H-Oj
	for l3vpn@ietf.org; Thu, 20 Dec 2007 08:02:46 -0500
Received: from p-mail2.rd.francetelecom.com ([195.101.245.16])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1J5L2y-000869-H4
	for l3vpn@ietf.org; Thu, 20 Dec 2007 08:02:46 -0500
Received: from ftrdmel10.rd.francetelecom.fr ([10.193.117.156]) by
	ftrdsmtp2.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 20 Dec 2007 14:02:25 +0100
Received: from [10.193.15.109] ([10.193.15.109]) by
	ftrdmel10.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 20 Dec 2007 14:02:25 +0100
From: Thomas Morin <thomas.morin@orange-ftgroup.com>
To: PAPADIMITRIOU Dimitri <Dimitri.Papadimitriou@alcatel-lucent.be>
In-Reply-To: <8144761F31F48D43AD53D09F5350E3800237BDD3@FRVELSMBS22.ad2.ad.alcatel.com>
References: <475DAB80.7010900@juniper.net>
	<8144761F31F48D43AD53D09F5350E3800237BDD3@FRVELSMBS22.ad2.ad.alcatel.com>
Content-Type: text/plain
Organization: France Telecom R&D - Orange
Date: Thu, 20 Dec 2007 14:02:24 +0100
Message-Id: <1198155744.4903.17.camel@wintermute>
Mime-Version: 1.0
X-Mailer: Evolution 2.12.2 
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 20 Dec 2007 13:02:25.0168 (UTC)
	FILETIME=[9101E900:01C84308]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f66b12316365a3fe519e75911daf28a8
Cc: l3vpn@ietf.org
Subject: RE: draft-morin-l3vpn-mvpn-considerations
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>
Errors-To: l3vpn-bounces@ietf.org

Hi Dimitri,

Thanks for your comments, a few reply below...

PAPADIMITRIOU Dimitri :
>
> the document should focus on a solid analysis/description before
> concluding with (strong) recommendations that are prescriptive and this,
> at an early stage of the analysis.
> 
> here below a specific example to show that this analytical phase is not
> completed to draw such conclusions/recommendations:
> 
> "By contrast, experience proves that PIM-based mechanisms are
> operationally viable, but with well identified limitations.  Some of
> those limitations may be improved upon (although there is currently no
> clearly defined proposal to do this), however some of the limitations
> appear to be intrinsic to the approach."
> 
> there are stated limitations but which limitations ? and to which extend
> (all protocols developed by the IETF have certain limitations what.
> matters is whether or not they are impacting in the interval of the
> protocol operations and how degradations are impacting outside of this
> interval) 

The limitations of the Full PIM peering solution is something that has
been discussed quite a lot in this working group in the past years. But
you are right in highlighting that we should be more explicit. The aim
is not not repeat in mvpn-considerations many things that have been
already discussed a lot, but I think we can improve the doc by making a
few things more explicit (such as the limitations of PIM, as you
mentioned, but also as pointed out by Eric, on a few other points).

> more interestingly, the statement ack's they may be elevated but since
> these limitations are stated to "appear as" intrinsic to the approach
> and so they can not be elevated ? if this is the case where is the proof
> for such statement ?

We actually say that some limitations seem to offer place for
improvement, whereas some others appear as intrinsic. 

The reference (too implicit, I agree) is to elements such as the
scalability limitations of PIM that may be improved upon by improvements
of PIM such as the refresh reduction worked on by the PIM WG
(non-intrinsic limitation), and such as the fact that the use of PIM for
C-multicast routing doesn't offer the level of consistency between
unicast and multicast that the BGP approach is providing (intrinsic
limitation).

We will clarify this in the document.


> in general also, i suggest that authors keep protocol capabilities
> analysis and consolidate their argumentation from feedback obtained on
> the field as long as BGP-based approaches do not benefit from experience
> on the field. indeed, in its current form, the document reads as
> comparing disadvantages of experimental / deployment experience gained
> from PIM wrt to theoretical expectations/advantages from new BGP-based
> standards.

Not exactly : we do also look at theoretical
aspects/advantages/drawbacks of the PIM approach.  

And as soon as experience is gained from the BGP approach, we should be
able to also talk in terms of experimental experience about this
approach.  

Thanks for your input,

-Thomas



> > -----Original Message-----
> > From: Ron Bonica [mailto:rbonica@juniper.net] 
> > Sent: Monday, December 10, 2007 10:11 PM
> > To: l3vpn@ietf.org
> > Subject: draft-morin-l3vpn-mvpn-considerations
> > 
> > Folks,
> > 
> > Unless I hear an objection before COB Friday, this document 
> > will become
> > a WG draft.
> > 
> >                                       Ron
> > 
> > 
> 





From l3vpn-bounces@ietf.org Wed Dec 26 13:35:34 2007
Return-path: <l3vpn-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1J7b5L-00007E-KO; Wed, 26 Dec 2007 13:34:31 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1J7b5J-000077-Tg
	for l3vpn@ietf.org; Wed, 26 Dec 2007 13:34:29 -0500
Received: from exprod7og104.obsmtp.com ([64.18.2.161] helo=psmtp.com)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1J7b5I-00026b-Fj
	for l3vpn@ietf.org; Wed, 26 Dec 2007 13:34:29 -0500
Received: from source ([66.129.224.36]) by exprod7ob104.postini.com
	([64.18.6.12]) with SMTP; Wed, 26 Dec 2007 10:34:27 PST
Received: from proton.jnpr.net ([10.10.2.37]) by emailsmtp56.jnpr.net with
	Microsoft SMTPSVC(6.0.3790.3959); Wed, 26 Dec 2007 10:33:58 -0800
Received: from [172.23.1.44] ([172.23.1.44] RDNS failed) by proton.jnpr.net
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 26 Dec 2007 13:33:57 -0500
Message-ID: <47729E90.5030106@juniper.net>
Date: Wed, 26 Dec 2007 13:33:52 -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: multipart/mixed; boundary="------------060303070609060908010302"
X-OriginalArrivalTime: 26 Dec 2007 18:33:58.0048 (UTC)
	FILETIME=[E0910200:01C847ED]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8a85b14f27c9dcbe0719e27d46abc1f8
Subject: IETF 70 minutes
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>
Errors-To: l3vpn-bounces@ietf.org

This is a multi-part message in MIME format.
--------------060303070609060908010302
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Folks,

Thanks to David Sinicrope for scribing our meeting at IETF 70. I have
already posted his notes to our web site. If anyone sees any
inaccuracies, I will gladly correct them.

                                Ron

--------------060303070609060908010302
Content-Type: text/plain;
 name="l3vpn.txt"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
 filename="l3vpn.txt"

Layer 3 Virtual Private Networks (Internet Area)

Wednesday, December 5, 2007
=========================

Chairs:
Rick Wilder <rick@rhwilder.net>
Ron Bonica  <rbonica@juniper.net>

Agenda:

09:00-09:10  Working Group Status and Charter - R. Bonica, R.Wilder
Ron did a brief update, we only have multicast VPN left to do.



09:10-09:40 T. Morin - draft-morin-l3vpn-mvpn-considerations-01
Thomas presented slides on the draft.
goal: discuss the options proposed and choose the better candidate
Question from Cisco, clarification do you need a colocated RP?  Yes.
would like additional clarification of colocated RP and usage in the draft.
Plan for refining the following subjects (slides) 5
test abou tspmsi for the inter AS context
comparison of segmented/nonseg inter as depending on  unicast option b or c
security or OAM related issues that cand ifferenciate the different propsoed options
Contributions welcom
expanding scope of document is not planned

need to identifiy a core set of mandatory procedures to make document useful as a standard
proposed as a WG draft.
those that read the draft agreed to make it a WG draft to be confirmed on the list.
Ron will post email asking if objections to making it a WG draft.


09:40-10:00 M. Napiera - draft-mnapierala-mvpn-part-reqt
Maria was not present to present the draft. No substitutes identified so draft presentation postponed for now.

10:00-10:30 B. Davies - draft-davie-tsvwg-rsvp-l3vpn
bruce presented slides...
need to determine the wg for the draft tsvwg or l3vpn
problem addmission control desired on ce-pe links of l3vpns
running rsvp across these links presents issues
need to associate rsvp with vrf context
need to intercept path messages at egress pe but router alert IP option not visible
may also wish to do admission control across backbone.
need inter AS operation and make sure admission control works in all cases.  This is where work on draft was.

problem to solve is when Path or Resv received at PE which VRF should be operating in.
P routers need to stay uninvolved. Messages must be transparently passed.

A fair number have read a version of the draft.
New objects placed in RSVP messages in service provider network to allow routers to figure out which VRF they apply to.
normally PATH message sent to end point, but instead sent directly to next router so that router alert processing not needed.
can use 4804 for admission control over provider backbones

Inter AS operation - in most recent version of the draft
Option A - just works ASBRs operate like PEs, two separate networks implement solution all information on the links.
Option C - just works  using a PE to PE LSP ASBRs in the middle transparent to RSVP.  If need to do ad control  across backbone then use TE tunnel accross
Option B - all heavy lifing here.  requries ASBRs to process Pathand resv messages and store state to enable revers fwding of RESV
OK solution if you want to do CAC on ASBR link.  IF no CAC needed then storing state for no benefit.  Will ddress in next draft revision

Also dealt with all messages that weren't PATH or RESV.  Details spelled out in draft.
When no CAC offered to customers don't just throw away RSVP messages, treat as IP data grams

Appendix A added to record rejected approaches so not revisited.  Should eventually be removed.

Open Issues
the VRF_ID  in current draft led to state storage in ASBRs evenif CAC not needed. - solution instead of VRF_ID (used to identify VRF, but needs to be recorded and stored as ASBRs. locally significant)
 use VPNv4 PHOP (globally significant) generated by ingress PE, can use LSP that leads to that VPNv4 address.  Transparent to ASBRs.

A suggestion made (Yakove Rekhter) that Path messages should carry the VPN_v4 address of the path message vs. the VPN label.  They are 1:1 and can forward PATH to destination.

Kumaki et al requested support for RSVP-TE from CEs - authors believe feasible, but not yet done.  Next draft version.

Summary
solution sticks to principle of no changes to 4364.

Authors think that with one more rev, draft would be pretty complete.
Draft will be presented in TSV - they own change control for RSVP.  Where do we go with the draft.  Not as much interest in TSV.
ADs could pursue work in this WG and have TSV review.

Is changing the addressing a change to RSVP?  Yes because changing the objects.

If given the OK to pursue document here would people support making it a WG document?  Question withdrawn
Is there agreement to tackle the problem here?
Agreement to tackle problem
Is there agreement that this document should form the basis for the work?
agreement that this document should form the basis for the work

Concern that changing semantic of session object is significant and shoudl be described before agreeing to wg document.  
Comment noted but does not reflect consensus of room.

Support that most of problems addressed by this is related to L3VPN wg.

Some concern that after a reboot there would be inconsistency between up and downstream and this is an RSVP issue.

Will be presented at TSV tomorrow.
Next draft anticipated in a few weeks.
Call for whether it should be a WG document should be made on the list after that.





10:30-11:00 E. Rosen & R. Aggarwal - draft-ietf-l3vpn-2547bis-mcast
Rahul presented the draft with slides (not uploaded)
Some technical loose ends presented (see slide 2)

Goal is to take draft to last call before next IETF

Rahul presented changes from previous version (slide 3, 4, 5)

review is encouraged particularly from those familiar with 2547 and multicast
Maria met with Rahul to address her issues from the last meeting.  Attempts have been made to accomodate her comments in the current draft.
Further discussions with Maria to examine the requirement that this be transparent to the customer to address move from FR, ATM to IPVPN.


Chair's note: too few folks are looking at drafts.  The chair asked for volunteers to review and offer objective, 
constructive techncial comments to the WG.

Dimitri P.
John Drake
Bruce Davie

There are implementations, so this work has not been done in a vacuum.  The work should not be given any special 
treatment.  However, if there is a last call and there are few comments and it looks like it has not had 
adequate review, it is appropriate for the chairs to ask for volunteers to explicitly review the work.


11:00-11:30 E. Rosen - draft-rosen-l3vpn-mvpn-profiles-00

MPVN profiles
The framework allows many choices at different layers by design.
Not desireable to reduce the set of options to one set and no consensus
But - no vendor wants to implement all combinations of options

Need to define profiles to group options that make sense and can be implemented as a set for a particular applciations

reducing the options forces once size fits all, not enough experience to show one set is enough and no consensus

Eric gave brief rationale for including PIM 
Briefly overview of potential BGP for multicast risks

In the draft there is focus on PIM+GRE and PIM+MPLS
Legacy subprofile addresses prestandard from 1999 that doesn't exactly conform to existing set of documents.  
PIM+GRE gives interop with deployed base and helps move deployment to standards(???)

PIM+GRE Profile
Legacy does not support MPLS data plane.  

PIM+MPLS profile 
based on MP to MP LSPs for data and conrol packet.  

Draft currently an individual draft to be pursued as Informational RFC after WG documents go to RFC.
Does the group want to adopt profiles and stnadardize some?

Discussion

One participant wants a mandatory set of options in solutions draft and then profile others.  Profiles long winded.
Mark T.  Progressing after may not be timely to give this work to the IESG.  Also need an applicability statement 
for each profile to say why and where the profile is applicable.  Either have one mandatory set or have more than one
mandatory set and position them.

What is the diff between a BCP and a profile.  A BCP has IETF consensus and informational document does not.

Participant (T. Morin) should use profile approach as last step. 

(Eric) Don't want to turn this into a PIM vs. BGP because still not clear which is right.  Was debated in the past.  Not enough facts
because not enough deployments.

There is a document (T. Morin) written by services providers to capture requirements that has been accepted by WG.   
A contribution by any service provider to add to it is welcome.

Does this document compete with the Morin document?  The Morin document tries to achieve a single mandatory profile, 
this one does not

The requirements should be added to the Morin document
This document is more than a profile, it has protocol spec that is non standard and should not be called a profile or 
profile should be defined.
For informational document it is valid to document protocols used rather than leave them up in the air.

Concerned that there was some misleading information concerning PIM LAN procedures.  It was countered that there are 
no PIM LAN procedures but rather PIM is used in a different way on a LAN.

For many building blocks there is one solution. There should be one set of mandatory procedures 
in the framework, but should not exclude other procedures.

Unicast 2547 does not have profiles why do we have them for multicast.
Multicast deployment predates the standards by a few years and is more complicated than unicast.

Do we want to forward the framework document with options and then profile it?
or do we want to define a mandatory set of options and forget the profiles?
WG must decide.  It was countered that even with a set of mandatory options profiles 
will be needed to define what makes sense of the others.

It was felt that the authors are using the profiles to document their pre-standard implementation.

Let the architecture draft reflect the services provider consensus.

WG needs to decide if one mandatory profile or multiple, if multiple need text to show tradeoffs.

Mark T proposed if the Morin draft describes the mandatory profile then the profile work needs to be folded into it.
A home needs to be found for the additional protocol spec.  It can be found after the standards are done.
The work needs to be done for the pros and cons of the different profiles so the working group can make a decision.

AP Morin draft question to the WG to adopt as a WG doc
AP two volunteers to review document
 
Meeting was adjourned.

--------------060303070609060908010302--




From l3vpn-bounces@ietf.org Thu Dec 27 00:51:45 2007
Return-path: <l3vpn-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1J7ldf-00050k-Oh; Thu, 27 Dec 2007 00:50:39 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1J7lde-00050f-Mv
	for l3vpn@ietf.org; Thu, 27 Dec 2007 00:50:38 -0500
Received: from smtp1.smtp.bt.com ([217.32.164.137])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1J7ldd-0000Y2-5x
	for l3vpn@ietf.org; Thu, 27 Dec 2007 00:50:38 -0500
Received: from E03MVY1-UKDY.domain1.systemhost.net ([193.113.30.59]) by
	smtp1.smtp.bt.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 27 Dec 2007 05:50:35 +0000
Received: from 217.32.164.172 ([217.32.164.172]) by
	E03MVY1-UKDY.domain1.systemhost.net ([193.113.30.114]) via
	Exchange Front-End Server mail.bt.com ([193.113.197.86]) with
	Microsoft Exchange Server HTTP-DAV ; Thu, 27 Dec 2007 05:50:34 +0000
User-Agent: Microsoft-Entourage/11.2.1.051115
Date: Thu, 27 Dec 2007 05:50:34 +0000
From: Ben Niven-Jenkins <benjamin.niven-jenkins@bt.com>
To: <erosen@cisco.com>,
	Thomas Morin <thomas.morin@orange-ftgroup.com>
Message-ID: <C398EDAA.736%benjamin.niven-jenkins@bt.com>
Thread-Topic: Comments on draft-morin-l3vpn-mvpn-considerations-01.txt 
Thread-Index: AchITGWjpE5MnrQ/EdyPlwAbY64lKQ==
In-Reply-To: <12329.1197655001@erosen-linux>
Mime-version: 1.0
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit
X-OriginalArrivalTime: 27 Dec 2007 05:50:35.0831 (UTC)
	FILETIME=[66BB1470:01C8484C]
X-Spam-Score: 1.6 (+)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
Cc: l3vpn@ietf.org
Subject: Re: Comments on draft-morin-l3vpn-mvpn-considerations-01.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>
Errors-To: l3vpn-bounces@ietf.org

Eric,

On 14/12/07 17:56, "Eric Rosen" <erosen@cisco.com> wrote:
>> if adoption of a work by a working group was requiring having finished the
>> doc, then adoption as WG item and Last Call could be made at the same
>> time, right ?  ;-)
> 
> Absolutely.  But it  would be nice if there were some  agreement on just how
> much more work it needs.
> 
> Until we've had  a fuller discussion on  which of my concerns do  and do not
> need to  be addressed,  it's hard  to judge whether  the authors  are really
> willing to  take this document in  the right direction.  That's  why I would
> like to delay adopting it as a WG document.

Do Thomas's responses thus far (which I support & endorse) related to which
of your comments we can start to address & incorporate into draft-morin
satisfy your concerns above?

Ben

Sent using the Microsoft Entourage 2004 for Mac Test Drive.





