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 04E6C3A6979;
 Thu, 20 Nov 2008 01:32:57 -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 3E7AE3A6888
 for <l3vpn@core3.amsl.com>; Thu, 20 Nov 2008 01:32:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.002
X-Spam-Level: 
X-Spam-Status: No, score=0.002 tagged_above=-999 required=5
 tests=[BAYES_50=0.001, HTML_MESSAGE=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 UPm4nOW++iRX for <l3vpn@core3.amsl.com>;
 Thu, 20 Nov 2008 01:32:55 -0800 (PST)
Received: from n2a.bullet.in.yahoo.com (n2a.bullet.in.yahoo.com
 [202.43.219.19]) by core3.amsl.com (Postfix) with SMTP id B21213A6979
 for <l3vpn@ietf.org>; Thu, 20 Nov 2008 01:32:54 -0800 (PST)
Received: from [202.86.4.171] by n2.bullet.in.yahoo.com with NNFMP;
 20 Nov 2008 09:32:51 -0000
Received: from [203.104.18.49] by t2.bullet.in.yahoo.com with NNFMP;
 20 Nov 2008 09:32:51 -0000
Received: from [127.0.0.1] by omp110.mail.in2.yahoo.com with NNFMP;
 20 Nov 2008 09:32:49 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 111241.33410.bm@omp110.mail.in2.yahoo.com
Received: (qmail 19898 invoked by uid 60001); 20 Nov 2008 09:32:49 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com;
 h=X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:MIME-Version:Content-Type:Message-ID;
 b=nt6RKur2r0UMe8NSjhF3+sff5DWfc5jNkNYW0oo3zZGN3eAANH12SKdDKUQaMSU/0PgtgIBWkKttGst2+Yhe1qVsgrZdbS3aI4v2tM9+iBwM3zYSi6g8d+PrDnRDxxvGuPiat1jiVSEZ0w+HRla5hunDwF2JoLpTD1LlcqKJl6c=;
X-YMail-OSG: BBc7SJYVM1nuJHhXi5pKuc7C09cYQWSpjxnF9v.8qIdoroZVvRRNQKmOAzmnhT05atMZg7yeSREZnUck2uxHv14_nQLsDHbrddYGZmiciCHcW6ejZver_rt0QglGt41VGfSMPNQ9QF9Lwx9IqVFIhPQadwWtJZPUuGmqBjZhZEGt4F_6rnMvHwQ741m9_u7_K4Jr0co8LNE2dXo-
Received: from [125.20.3.101] by web94907.mail.in2.yahoo.com via HTTP;
 Thu, 20 Nov 2008 15:02:48 IST
X-Mailer: YahooMailRC/1155.32 YahooMailWebService/0.7.260.1
Date: Thu, 20 Nov 2008 15:02:48 +0530 (IST)
From: Subinoy Das <subinoy_das_82@yahoo.com>
Subject: Query about upstrean assigned label from
 draft-ietf-l3vpn-2547bis-mcast-07.txt
To: l3vpn@ietf.org
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="0-97422663-1227173568=:19807"
Message-ID: <994376.19807.qm@web94907.mail.in2.yahoo.com>
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

--0-97422663-1227173568=:19807
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

Hi,=0A=0ASection Point 5 in 7.4.1.1. Advertising C-flow Binding to P-Tunnel=
 in draft-ietf-l3vpn-2547bis-mcast-07.txt says =0A=0A"If at least some of t=
he S-PMSIs aggregated onto the same=0AP-tunnel belong to different MVPNs, t=
hen all these routes MUST=0Acarry an MPLS upstream assigned label [MPLS-UPS=
TREAM-LABEL,=0Asection 6.3.4]. If all these aggregated S-PMSIs belong to th=
e=0Asame MVPN, then the routes MAY carry an MPLS upstream assigned=0Alabel =
[MPLS-UPSTREAM-LABEL]. The labels MUST be distinct on a=0Aper MVPN basis, a=
nd MAY be distinct on a per route basis."=0A=0AI do not understand where 1 =
label per MVPN solves everything then what is the need to use 1 label per r=
oute. What is the need to keep multiple label for a single MVPN per PE rout=
er?=0A=0ARegards,=0ASubinoy=0A=0A=0A=0A      Add more friends to your messe=
nger and enjoy! Go to http://messenger.yahoo.com/invite/
--0-97422663-1227173568=:19807
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: quoted-printable

<html><head><style type=3D"text/css"><!-- DIV {margin:0px;} --></style></he=
ad><body><div style=3D"font-family:times new roman,new york,times,serif;fon=
t-size:12pt"><div>Hi,<br><br>Section Point 5 in 7.4.1.1. Advertising C-flow=
 Binding to P-Tunnel in draft-ietf-l3vpn-2547bis-mcast-07.txt says <br><br>=
"If at least some of the S-PMSIs aggregated onto the same<br>P-tunnel belon=
g to different MVPNs, then all these routes MUST<br>carry an MPLS upstream =
assigned label [MPLS-UPSTREAM-LABEL,<br>section 6.3.4]. <span style=3D"text=
-decoration: underline;">If all these aggregated S-PMSIs belong to the</spa=
n><br style=3D"text-decoration: underline;"><span style=3D"text-decoration:=
 underline;">same MVPN, then the routes MAY carry an MPLS upstream assigned=
</span><br style=3D"text-decoration: underline;"><span style=3D"text-decora=
tion: underline;">label</span> [MPLS-UPSTREAM-LABEL]. The labels MUST be di=
stinct on a<br>per MVPN basis, and <span style=3D"text-decoration: underlin=
e;">MAY
 be distinct on a per route basis</span>."<br><br>I do not understand where=
 1 label per MVPN solves everything then what is the need to use 1 label pe=
r route. What is the need to keep multiple label for a single MVPN per PE r=
outer?<br><br>Regards,<br>Subinoy<br></div></div><br>=0A      <!--6--><hr s=
ize=3D1></hr> Add more friends to your messenger and enjoy! <a href=3D"http=
://in.rd.yahoo.com/tagline_messenger_6/*http://messenger.yahoo.com/invite/"=
> Invite them now.</a></body></html>
--0-97422663-1227173568=:19807--


