nit in draft-ietf-2547bis-mcast bgp section 14.1

Thomas Morin <thomas.morin@orange-ftgroup.com> Fri, 12 December 2008 15:16 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 CC6B328C123; Fri, 12 Dec 2008 07:16:50 -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 E476B3A6B1B for <l3vpn@core3.amsl.com>; Fri, 12 Dec 2008 07:16:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.149
X-Spam-Level:
X-Spam-Status: No, score=-3.149 tagged_above=-999 required=5 tests=[AWL=0.100, BAYES_00=-2.599, 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 w-ABpzQQm0Oc for <l3vpn@core3.amsl.com>; Fri, 12 Dec 2008 07:16:49 -0800 (PST)
Received: from p-mail2.rd.francetelecom.com (p-mail2.rd.francetelecom.com [195.101.245.16]) by core3.amsl.com (Postfix) with ESMTP id BE8F43A6AF9 for <l3vpn@ietf.org>; Fri, 12 Dec 2008 07:16:48 -0800 (PST)
Received: from ftrdmel10.rd.francetelecom.fr ([10.193.117.156]) by ftrdsmtp2.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.1830); Fri, 12 Dec 2008 16:16:39 +0100
Received: from [10.193.15.230] ([10.193.15.230]) by ftrdmel10.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.1830); Fri, 12 Dec 2008 16:16:39 +0100
Subject: nit in draft-ietf-2547bis-mcast bgp section 14.1
From: Thomas Morin <thomas.morin@orange-ftgroup.com>
To: Yakov Rekhter <yakov@juniper.net>, Rahul Aggarwal <rahul@juniper.net>, Eric Rosen <erosen@cisco.com>
Content-Type: text/plain
Organization: France Telecom R&D - Orange Labs
Date: Fri, 12 Dec 2008 16:16:54 +0100
Message-Id: <1229095014.29755.75.camel@l-at11168.FTRD>
Mime-Version: 1.0
X-Mailer: Evolution 2.22.3.1
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 12 Dec 2008 15:16:39.0664 (UTC) FILETIME=[A1BEF700:01C95C6C]
Cc: L3VPN <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 folks,

Current text of draft-ietf-2547bis-mcast section 14.1 includes :

   When a PE using any of the above methods first learns of a new
   (multicast) source within that MVPN, the PE constructs a Source
   Active A-D route, and sends this route to all other PEs that have one
   or more sites of that MVPN connected to them. The route carries a
   single MCAST-VPN NLRI constructed as follows:

     + The RD in this NLRI is set to the RD of the VRF of the MVPN on
       the PE.

     + The Multicast Source field MUST be set to the source IP address
       of the multicast data packet carried in the PIM-Register message.
       The Multicast Source Length field is set appropriately to reflect
       this.

     + The Multicast Group field MUST be set to the group address of the
       multicast data packet carried in the PIM-Register message. The
       Multicast Group Length field is set appropriately to reflect
       this.

In the above, the "of the multicast data packet carried in the
PIM-Register message" does not take into account the case where the
source was learned through MSDP. 

Proposed change:

     + The Multicast Source field MUST be set to the source IP address 
       of the multicast data packet carried in the PIM-Register
       message (RP/PIM register case) or of the MSDP Source-Active
       message (MSDP case). The Multicast Source Length field is set
       appropriately to reflect this.

     + The Multicast Group field MUST be set to the group IP address 
       of the multicast data packet carried in the PIM-Register
       message (RP/PIM register case) or of the MSDP Source-Active
       message (MSDP case). The Multicast Group Length field is set  
       appropriately to reflect this.

Cheers,

-Thomas