Re: Comments on draft-ietf-l3vpn-mvpn-considerations-00

Thomas Morin <thomas.morin@orange-ftgroup.com> Tue, 02 December 2008 14:57 UTC

Return-Path: <l3vpn-bounces@ietf.org>
X-Original-To: l3vpn-archive@megatron.ietf.org
Delivered-To: ietfarch-l3vpn-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D672F3A69A3; Tue, 2 Dec 2008 06:57:10 -0800 (PST)
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 2A09F3A69A3 for <l3vpn@core3.amsl.com>; Tue, 2 Dec 2008 06:57:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.649
X-Spam-Level:
X-Spam-Status: No, score=-2.649 tagged_above=-999 required=5 tests=[AWL=-0.600, BAYES_00=-2.599, HELO_EQ_FR=0.35, J_CHICKENPOX_13=0.6, J_CHICKENPOX_14=0.6, 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 D6hg4pgkI5dU for <l3vpn@core3.amsl.com>; Tue, 2 Dec 2008 06:57:09 -0800 (PST)
Received: from p-mail1.rd.francetelecom.com (p-mail1.rd.francetelecom.com [195.101.245.15]) by core3.amsl.com (Postfix) with ESMTP id F25653A6768 for <l3vpn@ietf.org>; Tue, 2 Dec 2008 06:57:08 -0800 (PST)
Received: from ftrdmel10.rd.francetelecom.fr ([10.193.117.156]) by ftrdsmtp2.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.1830); Tue, 2 Dec 2008 15:57:05 +0100
Received: from [10.193.15.189] ([10.193.15.189]) by ftrdmel10.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.1830); Tue, 2 Dec 2008 15:57:03 +0100
Subject: Re: Comments on draft-ietf-l3vpn-mvpn-considerations-00
From: Thomas Morin <thomas.morin@orange-ftgroup.com>
To: Adrian Farrel <adrian@olddog.co.uk>
In-Reply-To: <052A8EA5C9904A56B7EE12EB4692CBB0@your029b8cecfe>
References: <052A8EA5C9904A56B7EE12EB4692CBB0@your029b8cecfe>
Content-Type: text/plain
Organization: France Telecom R&D - Orange Labs
Date: Tue, 02 Dec 2008 14:57:13 +0000
Message-Id: <1228229833.5252.107.camel@l-at11168.FTRD>
Mime-Version: 1.0
X-Mailer: Evolution 2.22.3.1
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 02 Dec 2008 14:57:03.0858 (UTC) FILETIME=[3CC7B520:01C9548E]
Cc: l3vpn@ietf.org
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <l3vpn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/l3vpn>, <mailto:l3vpn-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/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>
Sender: l3vpn-bounces@ietf.org
Errors-To: l3vpn-bounces@ietf.org

Hi Adrian,

Adrian Farrel :
>
> In view of the somewhat heated discussion, I think that it is critical to 
> get the title and Abstract of this draft right so that we have a good 
> context within which to review its content.
> 
> Can I float the changes below as a straw man to produce some text that will 
> get a bit more focus in the draft?

These changes look to me as very relevant.
Except if anybody disagrees, we will incorporate them in next revision.

We were planning to update the wording of the introduction to also
better encompass the content of the document, and we will propose new
text in next revision.

Thank you,

-Thomas



> ===
> OLD
> 
>      Considerations about Multicast for BGP/MPLS VPN Standardization
>                  draft-ietf-l3vpn-mvpn-considerations-00
> 
> Abstract
> 
>    The current proposal for multicast in BGP/MPLS includes multiple
>    alternative mechanisms for some of the required building blocks of
>    the solution. The aim of this document is to leverage previously
>    documented requirements to identify the key elements and help move
>    forward solution design, toward the definition of a standard having a
>    well defined set of mandatory procedures.  The different proposed
>    alternative mechanisms are examined in the light of requirements
>    identified for multicast in L3VPNs, and suggestions are made about
>    which of these mechanisms standardization should favor.  Issues
>    related to existing deployments of early implementations are also
>    addressed.
> 
> ===
> NEW
> 
>       Mandatory Features in a Layer 3 Multicast BGP/MPLS VPN Solution
>                 draft-ietf-l3vpn-mvpn-considerations-00
> 
> Abstract
> 
>    More that one set of mechanisms to support multicast in a layer 3
>    BGP/MPLS VPN has been defined. These are presented in the documents
>    that define them as optional building blocks.
> 
>    To enable interoperability between implementations, this document
>    defines a subset of features that is considered mandatory for a
>    multicast BGP/MPLS VPN implementation. This will help implementers
>    and deployers understand which L3VPN multicast requirements are best
>    satisfied by each option.
> ===
>