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

Yakov Rekhter <yakov@juniper.net> Tue, 16 December 2008 16:03 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 9D56E3A695B; Tue, 16 Dec 2008 08:03:53 -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 49F563A695B for <l3vpn@core3.amsl.com>; Tue, 16 Dec 2008 08:03:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.179
X-Spam-Level:
X-Spam-Status: No, score=-6.179 tagged_above=-999 required=5 tests=[AWL=-0.180, BAYES_00=-2.599, J_CHICKENPOX_45=0.6, RCVD_IN_DNSWL_MED=-4]
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 ClrYHaLZxNzP for <l3vpn@core3.amsl.com>; Tue, 16 Dec 2008 08:03:51 -0800 (PST)
Received: from exprod7og113.obsmtp.com (exprod7og113.obsmtp.com [64.18.2.179]) by core3.amsl.com (Postfix) with ESMTP id 55DCA3A67E9 for <l3vpn@ietf.org>; Tue, 16 Dec 2008 08:03:50 -0800 (PST)
Received: from source ([66.129.224.36]) (using TLSv1) by exprod7ob113.postini.com ([64.18.6.12]) with SMTP ID DSNKSUfRX4pWPG0HEG01zT2ylxmBWhKHf988@postini.com; Tue, 16 Dec 2008 08:03:44 PST
Received: from p-emfe01-sac.jnpr.net (66.129.254.72) by P-EMHUB01-HQ.jnpr.net (172.24.192.35) with Microsoft SMTP Server id 8.1.311.2; Tue, 16 Dec 2008 08:00:16 -0800
Received: from p-emlb01-sac.jnpr.net ([66.129.254.46]) by p-emfe01-sac.jnpr.net with Microsoft SMTPSVC(6.0.3790.3959); Tue, 16 Dec 2008 08:00:16 -0800
Received: from emailsmtp56.jnpr.net ([172.24.60.77]) by p-emlb01-sac.jnpr.net with Microsoft SMTPSVC(6.0.3790.3959); Tue, 16 Dec 2008 08:00:16 -0800
Received: from magenta.juniper.net ([172.17.27.123]) by emailsmtp56.jnpr.net with Microsoft SMTPSVC(6.0.3790.3959); Tue, 16 Dec 2008 08:00: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 mBGG0FM61025; Tue, 16 Dec 2008 08:00:15 -0800 (PST) (envelope-from yakov@juniper.net)
Message-ID: <200812161600.mBGG0FM61025@magenta.juniper.net>
To: "NAPIERALA, MARIA H, ATTLABS" <mnapierala@att.com>
Subject: Re: WG LC: draft-ietf-l3vpn-2547bis-mcast-bgp
In-Reply-To: <2F1DE4DFCFF32144B771BD2C246E6A200166DDB5@misout7msgusr7e.ugd.att.com>
References: <F9AA9B4C-3FEA-4723-BBBD-7FF91270E07D@tcb.net> <2F1DE4DFCFF32144B771BD2C246E6A200166D81D@misout7msgusr7e.ugd.att.com> <200812160046.mBG0kfM59345@magenta.juniper.net> <2F1DE4DFCFF32144B771BD2C246E6A200166DDB5@misout7msgusr7e.ugd.att.com>
X-MH-In-Reply-To: "NAPIERALA, MARIA H, ATTLABS" <mnapierala@att.com> message dated "Mon, 15 Dec 2008 22:50:46 -0500."
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <10650.1229443210.1@juniper.net>
Date: Tue, 16 Dec 2008 08:00:10 -0800
From: Yakov Rekhter <yakov@juniper.net>
X-OriginalArrivalTime: 16 Dec 2008 16:00:15.0756 (UTC) FILETIME=[62B5ECC0:01C95F97]
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

Maria,

> Yakov,
> 
> what functionality does the following paragraph in section 13.2
> introduces beyond what is already covered in section 12.3:
> 
> "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)."

Titles of 12.3 and 13.2 provide an answer to your question.

Yakov.


> 
> Maria
> 
> > -----Original Message-----
> > From: Yakov Rekhter [mailto:yakov@juniper.net]
> > Sent: Monday, December 15, 2008 7:47 PM
> > To: NAPIERALA, MARIA H, ATTLABS
> > Cc: Danny McPherson; l3vpn@ietf.org
> > Subject: Re: WG LC: draft-ietf-l3vpn-2547bis-mcast-bgp
> > 
> > Maria,
> > 
> > [small correction to my previous reply...]
> > 
> > > 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.
> > 
> > The current spec allows (C-S, C-G) to be carried either on I-PMSI or
> S-
> > PMSI.
> > 
> > When (C-S, C-G) is carried on I-PMSI the PE joins the tunnel(s) used
> by
> > I-PMSI at provisioning time, and therefore does not need to join
> > any I-PMSI tunnel(s) when it receives a Source Active A-D route.
> > 
> > When (C-S, C-G) is carried over an S-PMSI text in 12.3 covers the
> issue
> > of joining the tunnel.
> > 
> > So, the current spec already addresses your comment wrt joining
> > the tunnel.
> > 
> > Yakov.
> > 
> > >
> > >
> > > 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
> > >
>