RE: WG LC: draft-ietf-l3vpn-2547bis-mcast-bgp

"NAPIERALA, MARIA H, ATTLABS" <mnapierala@att.com> Mon, 15 December 2008 13:54 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 A06EB3A6A06; Mon, 15 Dec 2008 05:54:52 -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 C99373A69DF for <l3vpn@core3.amsl.com>; Mon, 15 Dec 2008 05:54:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.299
X-Spam-Level:
X-Spam-Status: No, score=-106.299 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_45=0.6, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 VWq-AONbHHVz for <l3vpn@core3.amsl.com>; Mon, 15 Dec 2008 05:54:50 -0800 (PST)
Received: from mail146.messagelabs.com (mail146.messagelabs.com [216.82.241.147]) by core3.amsl.com (Postfix) with ESMTP id C08DF3A684E for <l3vpn@ietf.org>; Mon, 15 Dec 2008 05:54:49 -0800 (PST)
X-VirusChecked: Checked
X-Env-Sender: mnapierala@att.com
X-Msg-Ref: server-11.tower-146.messagelabs.com!1229349281!12423706!1
X-StarScan-Version: 6.0.0; banners=-,-,-
X-Originating-IP: [144.160.20.54]
Received: (qmail 29095 invoked from network); 15 Dec 2008 13:54:42 -0000
Received: from sbcsmtp7.sbc.com (HELO mlpi135.enaf.sfdc.sbc.com) (144.160.20.54) by server-11.tower-146.messagelabs.com with AES256-SHA encrypted SMTP; 15 Dec 2008 13:54:42 -0000
Received: from enaf.sfdc.sbc.com (localhost.localdomain [127.0.0.1]) by mlpi135.enaf.sfdc.sbc.com (8.14.3/8.14.3) with ESMTP id mBFDsfil022845; Mon, 15 Dec 2008 08:54:41 -0500
Received: from misout7msgusr7e.ugd.att.com (misout7msgusr7e.ugd.att.com [144.155.43.107]) by mlpi135.enaf.sfdc.sbc.com (8.14.3/8.14.3) with ESMTP id mBFDsXPJ022764; Mon, 15 Dec 2008 08:54:33 -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
Subject: RE: WG LC: draft-ietf-l3vpn-2547bis-mcast-bgp
Date: Mon, 15 Dec 2008 08:54:31 -0500
Message-ID: <2F1DE4DFCFF32144B771BD2C246E6A200166D81D@misout7msgusr7e.ugd.att.com>
In-Reply-To: <F9AA9B4C-3FEA-4723-BBBD-7FF91270E07D@tcb.net>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: WG LC: draft-ietf-l3vpn-2547bis-mcast-bgp
Thread-Index: AclL4HImX3E6SNArSReplAEZkvSR5wS3BjvA
References: <F9AA9B4C-3FEA-4723-BBBD-7FF91270E07D@tcb.net>
From: "NAPIERALA, MARIA H, ATTLABS" <mnapierala@att.com>
To: Danny McPherson <danny@tcb.net>, 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

Comments on section 13.2:

  "When as a result of receiving a new Source Active A-D route a PE
   updates its VRF with the route, the PE MUST check if the newly
   received route matches any <C-*, C-G> entries. If (a) there is a
   matching entry, (b) the PE does not have (C-S, C-G) state in its
   MVPN-TIB for (C-S, C-G) carried in the route, and (c) the received
   route is selected as the best(using the BGP route selection
   procedures), then the PE sets up its forwarding path to receive (C-S,
   C-G) traffic from the tunnel the originator of the selected Source
   Active A-D route uses for sending (C-S, C-G)."

The condition (b) above excludes the following case: a PE that received
a Source Active A-D route for (C-S,C-G) has both (C-*, C-G) and (C-S,
C-G) states in its MVPN-TIB (because its locally attached site switched
to SPT for C-S). If this PE does not join the tunnel used for C-S
traffic, this PE will not receive the C-S traffic.

Also, the section 13.2 has no procedure for the case when a PE that
received a Source Active A-D route for (C-S,C-G) has the (C-S,C-G) state
but not the (C-*, C-G) state in its MVPN-FIB. This could be the case,
for example, when the PE is attached to (a site with) C-RP but it is not
directly attached to any (C-*, C-G) receiver sites, except those behind
the C-RP. This PE will also have to join the tunnel used for C-S traffic
to deliver traffic to those receivers.


Maria

> -----Original Message-----
> From: l3vpn-bounces@ietf.org [mailto:l3vpn-bounces@ietf.org] On Behalf
> Of Danny McPherson
> Sent: Friday, November 21, 2008 8:52 AM
> To: l3vpn@ietf.org
> Subject: WG LC: draft-ietf-l3vpn-2547bis-mcast-bgp
> 
> 
> Please consider today the start of a 2-week last call
> for draft-ietf-l3vpn-2547bis-mcast-bgp, available here:
> 
> http://tools.ietf.org/html/draft-ietf-l3vpn-2547bis-mcast-bgp-05
> 
> Input on this draft's suitability for publication as an
> Internet Standards Track document is solicited, feedback
> ends December 9, 2008.
> 
> Thanks in advance for your feedback!
> 
> Danny & Marshall