Re: Query about upstrean assigned label from draft-ietf-l3vpn-2547bis-mcast-07.txt
Subinoy Das <subinoy_das_82@yahoo.com> Thu, 20 November 2008 14:49 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 0885A3A6987; Thu, 20 Nov 2008 06:49:22 -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 98DE23A698C for <l3vpn@core3.amsl.com>; Thu, 20 Nov 2008 06:49:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.6
X-Spam-Level:
X-Spam-Status: No, score=-0.6 tagged_above=-999 required=5 tests=[AWL=0.602, BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=1.396, NORMAL_HTTP_TO_IP=0.001]
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 HeOa3TdwbHdY for <l3vpn@core3.amsl.com>; Thu, 20 Nov 2008 06:49:19 -0800 (PST)
Received: from n5a.bullet.tw1.yahoo.com (n5a.bullet.tw1.yahoo.com [119.160.244.192]) by core3.amsl.com (Postfix) with SMTP id 5F7733A6800 for <l3vpn@ietf.org>; Thu, 20 Nov 2008 06:49:19 -0800 (PST)
Received: from [119.160.244.77] by n5.bullet.tw1.yahoo.com with NNFMP; 20 Nov 2008 14:49:17 -0000
Received: from [203.212.168.61] by t2.bullet.tw1.yahoo.com with NNFMP; 20 Nov 2008 14:49:16 -0000
Received: from [203.104.17.87] by t2.bullet.kr1.yahoo.com with NNFMP; 20 Nov 2008 14:49:12 -0000
Received: from [127.0.0.1] by omp101.mail.in2.yahoo.com with NNFMP; 20 Nov 2008 14:49:11 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 799099.82725.bm@omp101.mail.in2.yahoo.com
Received: (qmail 58854 invoked by uid 60001); 20 Nov 2008 14:42:30 -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=pblhFUN9TUhoUiK8HfhAQV5B6BtLwUzx2CrtDs2PifwaLas+LBlGps0pVTVt34o8qa1OnYZYwohtOaY7nSPqmntBKnKYIyy77CIuinZHZ10mCiyBNgLvfk7Rw7zuDUpZnFeTua7ZesNunVK4UT2IqkAG/rpqu6149tcrGWpFEZQ=;
X-YMail-OSG: n76LAf8VM1nnUH7dehV8S2IMgkrdU2m_ce6J8Rc744TyC6m9O_BqcMTlU_2AbdB0EYL81KC7U.tig5600NsqFcBWB7aAvAT.ec7_OVyQdNz9cQjAgnclhCPLHJ21WhkwRq_J6dWrbYVNlD2etsrv9otwzPqjINO6NfJwY9uzik555Du2hRRcwRklqP81HQlOsIZ.cPdf7AhPiquzf56AqN2onR4jZLXDpYyrLYBThR9q3tkkDAWlIrrZFA944OWvg_TiaKJs5KCLpw--
Received: from [125.20.3.101] by web94915.mail.in2.yahoo.com via HTTP; Thu, 20 Nov 2008 20:12:29 IST
X-Mailer: YahooMailRC/1155.32 YahooMailWebService/0.7.260.1
References: <994376.19807.qm@web94907.mail.in2.yahoo.com> <70452ae70811200520qc600e1eh68b6be0850fc1905@mail.gmail.com>
Date: Thu, 20 Nov 2008 20:12:29 +0530
From: Subinoy Das <subinoy_das_82@yahoo.com>
Subject: Re: Query about upstrean assigned label from draft-ietf-l3vpn-2547bis-mcast-07.txt
To: Raveendra Torvi <pratiravi@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="0-1993716465-1227192149=:58299"
Message-ID: <118882.58299.qm@web94915.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
Each PE have (C-S,C-G) state for each C-flow per MVPN. Then what is the need of different label for different C-flow? Regards, Subinoy ________________________________ From: Raveendra Torvi <pratiravi@gmail.com> To: Subinoy Das <subinoy_das_82@yahoo.com> Sent: Thursday, 20 November, 2008 6:50:52 PM Subject: Re: Query about upstrean assigned label from draft-ietf-l3vpn-2547bis-mcast-07.txt You need route label to distinguish c-flows of a mvpn. -R On Thu, Nov 20, 2008 at 4:32 AM, Subinoy Das <subinoy_das_82@yahoo.com> wrote: Hi, Section Point 5 in 7.4.1.1. Advertising C-flow Binding to P-Tunnel in draft-ietf-l3vpn-2547bis-mcast-07.txt says "If at least some of the S-PMSIs aggregated onto the same P-tunnel belong to different MVPNs, then all these routes MUST carry an MPLS upstream assigned label [MPLS-UPSTREAM-LABEL, section 6.3.4]. If all these aggregated S-PMSIs belong to the same MVPN, then the routes MAY carry an MPLS upstream assigned label [MPLS-UPSTREAM-LABEL]. The labels MUST be distinct on a per MVPN basis, and MAY be distinct on a per route basis." I do not understand where 1 label per MVPN solves everything then what is the need to use 1 label per route. What is the need to keep multiple label for a single MVPN per PE router? Regards, Subinoy ________________________________ Add more friends to your messenger and enjoy! Invite them now. Get perfect Email ID for your Resume. Grab now http://in.promos.yahoo.com/address
- Query about upstrean assigned label from draft-ie… Subinoy Das
- Re: Query about upstrean assigned label from draf… Subinoy Das
- Re: Query about upstrean assigned label from draf… Eric Rosen
- Re: Query about upstrean assigned label from draf… Subinoy Das
- Re: Query about upstrean assigned label from draf… Yakov Rekhter