Re: Query related to Auto Discovery as in draft-ietf-l3vpn-2547bis-mcast-07.txt
Subinoy Das <subinoy_das_82@yahoo.com> Tue, 02 December 2008 08:08 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 AA1943A6A82; Tue, 2 Dec 2008 00:08:56 -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 BBA6C3A68D2 for <l3vpn@core3.amsl.com>; Tue, 2 Dec 2008 00:08:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.989
X-Spam-Level:
X-Spam-Status: No, score=0.989 tagged_above=-999 required=5 tests=[AWL=-1.009, BAYES_50=0.001, HTML_MESSAGE=0.001, J_CHICKENPOX_13=0.6, MIME_QP_LONG_LINE=1.396]
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 0uMYDOYtq958 for <l3vpn@core3.amsl.com>; Tue, 2 Dec 2008 00:08:55 -0800 (PST)
Received: from n1a.bullet.in.yahoo.com (n1a.bullet.in.yahoo.com [202.43.219.18]) by core3.amsl.com (Postfix) with SMTP id 225D93A6A82 for <l3vpn@ietf.org>; Tue, 2 Dec 2008 00:08:53 -0800 (PST)
Received: from [202.86.4.170] by n1.bullet.in.yahoo.com with NNFMP; 02 Dec 2008 08:08:48 -0000
Received: from [203.104.18.50] by t1.bullet.in.yahoo.com with NNFMP; 02 Dec 2008 08:08:48 -0000
Received: from [127.0.0.1] by omp111.mail.in2.yahoo.com with NNFMP; 02 Dec 2008 08:08:48 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 198879.47622.bm@omp111.mail.in2.yahoo.com
Received: (qmail 75633 invoked by uid 60001); 2 Dec 2008 08:08:47 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Mailer:References:Date:From:Subject:To:Cc:MIME-Version:Content-Type:Message-ID; b=0AwmAuWDMdLMI0DH24MNnyRZZ9DUmGz49TbP/eY0qg6OLs+KCdirsY9mgKMpTSPVOfowShzRYlXvmQBmVXCiykGdZ9a/vBEk7y2+jduLqvv96VLUlnga9MmIJZrRYDMrn3V5FtiaAcM/b3DCP8f1fnJp2j+TrzIWMV408dGbaIU=;
X-YMail-OSG: z9vlAsEVM1lX1xQYBjWnn0KUrX7b8ct4Jvz5xnTjBl_HQMILgExTZZPUll4.zdqSSXAjI7oYQhYs3DJKSUlVBgXjnC49ywkhZlPaKt_rSzWa1BGWZUwAoH4eFIhkPulTKLn2hSXS1h9zCMbu4eZQBhyWEAE-
Received: from [125.20.3.101] by web94903.mail.in2.yahoo.com via HTTP; Tue, 02 Dec 2008 13:38:47 IST
X-Mailer: YahooMailRC/1155.32 YahooMailWebService/0.7.260.1
References: <531227.8809.qm@web94904.mail.in2.yahoo.com> <200811261359.mAQDxLM62607@magenta.juniper.net>
Date: Tue, 02 Dec 2008 13:38:47 +0530
From: Subinoy Das <subinoy_das_82@yahoo.com>
Subject: Re: Query related to Auto Discovery as in draft-ietf-l3vpn-2547bis-mcast-07.txt
To: Yakov Rekhter <yakov@juniper.net>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="0-1910773228-1228205327=:53879"
Message-ID: <913955.53879.qm@web94903.mail.in2.yahoo.com>
Cc: L3VPN MAIL <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
Thanks for answer. I still have confision about the exact process..
If local policy states to discard route if RT does not match Import then what happen if new VPN support is added to a PE? How does it comes to know all routes for that VPN? Should all other PEs send I-PMSI A-D Route, S-PMSI A-D Route, Source Active A-D Route, C-Multicast Route to that PE?
Thanks,
Subinoy
________________________________
From: Yakov Rekhter <yakov@juniper.net>
To: Subinoy Das <subinoy_das_82@yahoo.com>
Cc: L3VPN MAIL <l3vpn@ietf.org>
Sent: Wednesday, 26 November, 2008 7:29:21 PM
Subject: Re: Query related to Auto Discovery as in draft-ietf-l3vpn-2547bis-mcast-07.txt
Subinoy,
> Hi,
>
> I have one query about Auto Discovery using BGP to exchange multicast
> route in provider network.
>
> When a PE receives Intra-AS I-PMSI A-D route it matches Import RT
> of all VRF it supports with all RTs in the packet. If no match found
> then what does PE do? Is it stores the information in database or
> just discard the packet?
It is a matter of local policy on the PE. Not that much different
from the scenario where a PE receives a (unicast) VPN-IPv4 route
whose RT does not match Import RT of any of the VRFs on the PE.
Yakov.
Add more friends to your messenger and enjoy! Go to http://messenger.yahoo.com/invite/
- Query related to Auto Discovery as in draft-ietf-… Subinoy Das
- Re: Query related to Auto Discovery as in draft-i… Yakov Rekhter
- Re: Query related to Auto Discovery as in draft-i… Subinoy Das
- Re: Query related to Auto Discovery as in draft-i… Yakov Rekhter