Re: draft-rosen-l3vpn-mvpn-spmsi-joins-00.txt
Thomas Morin <thomas.morin@orange-ftgroup.com> Tue, 27 April 2010 15:16 UTC
Return-Path: <thomas.morin@orange-ftgroup.com>
X-Original-To: l3vpn@core3.amsl.com
Delivered-To: l3vpn@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DF67D28C24E for <l3vpn@core3.amsl.com>; Tue, 27 Apr 2010 08:16:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.649
X-Spam-Level:
X-Spam-Status: No, score=-0.649 tagged_above=-999 required=5 tests=[BAYES_50=0.001, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hmDmfEO4RGQ0 for <l3vpn@core3.amsl.com>; Tue, 27 Apr 2010 08:16:30 -0700 (PDT)
Received: from p-mail2.rd.francetelecom.com (p-mail2.rd.francetelecom.com [195.101.245.16]) by core3.amsl.com (Postfix) with ESMTP id 7D2F028C252 for <l3vpn@ietf.org>; Tue, 27 Apr 2010 08:10:40 -0700 (PDT)
Received: from p-mail2.rd.francetelecom.com (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with SMTP id E3107760006 for <l3vpn@ietf.org>; Tue, 27 Apr 2010 17:10:08 +0200 (CEST)
Received: from ftrdsmtp2.rd.francetelecom.fr (unknown [10.192.128.47]) by p-mail2.rd.francetelecom.com (Postfix) with ESMTP id 11607760028 for <l3vpn@ietf.org>; Tue, 27 Apr 2010 17:09:50 +0200 (CEST)
Received: from ftrdmel10.rd.francetelecom.fr ([10.192.128.44]) by ftrdsmtp2.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.3959); Tue, 27 Apr 2010 17:09:14 +0200
Received: from [10.193.15.53] ([10.193.15.53]) by ftrdmel10.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.3959); Tue, 27 Apr 2010 17:09:13 +0200
Message-ID: <4BD6FE19.3000809@orange-ftgroup.com>
Date: Tue, 27 Apr 2010 17:09:13 +0200
From: Thomas Morin <thomas.morin@orange-ftgroup.com>
Organization: France Telecom Orange
User-Agent: Mozilla/5.0 (X11; U; ; ; ) Gecko/2010 Thunderbird/3.0.x
MIME-Version: 1.0
To: l3vpn@ietf.org
Subject: Re: draft-rosen-l3vpn-mvpn-spmsi-joins-00.txt
References: <26520.1271424851@erosen-linux>
In-Reply-To: <26520.1271424851@erosen-linux>
X-Enigmail-Version: 1.0.1
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 27 Apr 2010 15:09:13.0902 (UTC) FILETIME=[9901D4E0:01CAE61B]
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <l3vpn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/l3vpn>, <mailto:l3vpn-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/l3vpn>
List-Post: <mailto:l3vpn@ietf.org>
List-Help: <mailto:l3vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/l3vpn>, <mailto:l3vpn-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Apr 2010 15:16:31 -0000
Eric,
Eric Rosen :
> b. RFC 4834 ("Requirements for Multicast in Layer 3 Provider-Provisioned
> Virtual Private Networks (PPVPNs)" says explicitly that "the control
> plane SHALL NOT depend on which forwarding plane is used". This
> requirement does not seem compatible with a WG decision to make the
> S-PMSI Join mechanism illegal when MPLS is used for forwarding!
>
RFC4834, as the input for building a standard multicast VPN solution
(not two!), should not be interpreted by abusing the fact that
draft-ietf-2547bis-mcast did not select between two alternative
mechanisms for S-PMSI signalling. Note also that
draft-ietf-2547bis-mcast and draft-ietf-l3vpn-mvpn-considerations
together do provide a specification of a standard with a control plane
that can be used independently of the forwarding plane that is used.
-Thomas
- draft-rosen-l3vpn-mvpn-spmsi-joins-00.txt Eric Rosen
- Re: draft-rosen-l3vpn-mvpn-spmsi-joins-00.txt Thomas Morin
- Re: draft-rosen-l3vpn-mvpn-spmsi-joins-00.txt Eric Rosen
- Re: draft-rosen-l3vpn-mvpn-spmsi-joins-00.txt Thomas Morin
- Re: draft-rosen-l3vpn-mvpn-spmsi-joins-00.txt Eric Rosen