RE: [mpls] draft-raggarwa-mpls-rsvp-upstream-00 for wg doc?

"Pal, Anjaneya" <anjan@riverstonenet.com> Thu, 16 February 2006 15:30 UTC

Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F9l5X-0000t1-58; Thu, 16 Feb 2006 10:30:35 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F9l5V-0000sD-BD for mpls@megatron.ietf.org; Thu, 16 Feb 2006 10:30:33 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA03352 for <mpls@ietf.org>; Thu, 16 Feb 2006 10:28:44 -0500 (EST)
Received: from generic.riverstonenet.com ([66.17.149.13] helo=riverstonenet.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1F9lJV-0001WE-I9 for mpls@ietf.org; Thu, 16 Feb 2006 10:45:17 -0500
Received: from gondor.rs.riverstonenet.com by riverstonenet.com (8.9.3+Sun/SMI-SVR4-Yago) id HAA13211; Thu, 16 Feb 2006 07:30:01 -0800 (PST)
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [mpls] draft-raggarwa-mpls-rsvp-upstream-00 for wg doc?
Date: Thu, 16 Feb 2006 21:00:06 +0530
Message-ID: <FCAF0E8A270B6E4781D91431E853F6F301C6C6F0@GONDOR.rs.riverstonenet.com>
Thread-Topic: [mpls] draft-raggarwa-mpls-rsvp-upstream-00 for wg doc?
Thread-Index: AcYxbvQfx1TCHldVS2S8mTh2WAbdIABnTGRQ
From: "Pal, Anjaneya" <anjan@riverstonenet.com>
To: "Vijayanand C - CTD, Chennai." <vijayc@hcl.in>, Loa Andersson <loa@pi.se>, mpls@ietf.org
X-Spam-Score: 0.2 (/)
X-Scan-Signature: e1b0e72ff1bbd457ceef31828f216a86
Content-Transfer-Encoding: quoted-printable
Cc:
X-BeenThere: mpls@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/mpls>
List-Post: <mailto:mpls@lists.ietf.org>
List-Help: <mailto:mpls-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@lists.ietf.org?subject=subscribe>
Sender: mpls-bounces@lists.ietf.org
Errors-To: mpls-bounces@lists.ietf.org

Vijay,

I think the collision won't happen bcoz Rd will be using different
(context-specific) labelspace for the label distributed by peer Ru (as a
part of upstream assigned label) and that distributed by itself to other
peers (as a part of downstream assigned label). So if Rd support
upstream-assigned label bindings then it maintains different ILM tables
for different context-specific labelspaces. And when Rd gets a labeled
pkt it first determines the context-specific labelspace and hence looks
up for the label in the corresponding ILM table. Section 7 of
"draft-raggarwa-mpls-upstream-label-01.txt" gives some insight on this.

Regards,
-Anjan


-----Original Message-----
From: mpls-bounces@lists.ietf.org [mailto:mpls-bounces@lists.ietf.org]
On Behalf Of Vijayanand C - CTD, Chennai.
Sent: Tuesday, February 14, 2006 7:27 PM
To: Loa Andersson; mpls@ietf.org
Subject: RE: [mpls] draft-raggarwa-mpls-rsvp-upstream-00 for wg doc?

I have a question/suggestion here applicable to both the drafts-
 While the downstream(Rd) indicates its capability to accept upstream
labels
from its peer(Ru),would nt it be desirable for it to advertise a label
range
it can accept. This would avoid problems of the upstream assigned label
distributed by a peer(Ru)  colliding with an LSRs(Rd) own downstream
assigned label which it has distributed out to its other peers(other
than
Ru) for other FECs/flows, especially when the upstream label is not
tunneled
in ip or mpls.

Regards,
Vijay

> -----Original Message-----
> From: mpls-bounces@lists.ietf.org 
> [mailto:mpls-bounces@lists.ietf.org]On
> Behalf Of Loa Andersson
> Sent: Friday, February 03, 2006 9:46 PM
> To: mpls@ietf.org
> Subject: [mpls] draft-raggarwa-mpls-rsvp-upstream-00 for wg doc?
> 
> 
> All,
> 
> the authors of draft-raggarwa-mpls-rsvp-upstream-00
> has requested that it is made a working group document.
> 
> Please review, comment and respond to the working group mailing
> list if you support it becoming a wg or not.
> 
> /Loa and George
> 
> PS
> 
> yes - there are two separate polls one for
> 
> draft-raggarwa-mpls-ldp-upstream-00
> and one for
> draft-raggarwa-mpls-rsvp-upstream-00
> 
> :)
> 
> 
> -- 
> Loa Andersson
> 
> Principal Networking Architect
> Acreo AB                           phone:  +46 8 632 77 14
> Isafjordsgatan 22                  mobile: +46 739 81 21 64
> Kista, Sweden                      email:  loa.andersson@acreo.se
>                                             loa@pi.se
> 
_______________________________________________
> mpls mailing list
> mpls@lists.ietf.org
> https://www1.ietf.org/mailman/listinfo/mpls
> 
DISCLAIMER 
This message and any attachment(s) contained here are information that
is confidential, proprietary to HCL Technologies 
and its customers. Contents may be privileged or otherwise protected by
law. The information is solely intended for the 
individual or the entity it is addressed to. If you are not the intended
recipient of this message, you are not authorized to 
read, forward, print, retain, copy or disseminate this message or any
part of it. If you have received this e-mail in error, 
please notify the sender immediately by return e-mail and delete it from
your computer


_______________________________________________
mpls mailing list
mpls@lists.ietf.org
https://www1.ietf.org/mailman/listinfo/mpls

_______________________________________________
mpls mailing list
mpls@lists.ietf.org
https://www1.ietf.org/mailman/listinfo/mpls