Return-Path: <lamberto.sterling@gmail.com>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix)
 with ESMTP id 76B2B3A677E; Sat, 11 Sep 2010 18:25:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.489
X-Spam-Level: 
X-Spam-Status: No, score=-1.489 tagged_above=-999 required=5 tests=[AWL=1.109,
 BAYES_00=-2.599, 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 wKc71nFUtyJ0;
 Sat, 11 Sep 2010 18:25:38 -0700 (PDT)
Received: from mail-px0-f194.google.com (mail-px0-f194.google.com
 [209.85.212.194]) by core3.amsl.com (Postfix) with ESMTP id 42AFA3A67A4;
 Sat, 11 Sep 2010 18:25:38 -0700 (PDT)
Received: by pxi20 with SMTP id 20so1437224pxi.1 for <multiple recipients>;
 Sat, 11 Sep 2010 18:26:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
 h=domainkey-signature:mime-version:received:received:date:message-id
 :subject:from:to:cc:content-type;
 bh=mnaUwLBMxPCaqR//eiIXW6zpOIk1J4poFl2kqGc0HGs=;
 b=Pq8JBRHlAPJNPkMLWBDyAsaKMG03owNza2e+Rl/cUz5PhPjmM8H6D2d+u5AxbgsdUR
 o11DyXLRztJQJQHjKBn4NtMsrmHhXnKkIE2W2UB+CwLhG11pGHb1T6z6y6Vc4Qb65Udq
 tUGTCdbAvJN6erYa/HJrMX6U/rNi02/YFVfK4=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
 h=mime-version:date:message-id:subject:from:to:cc:content-type;
 b=qR1ieSE1GZmWWO1gGnNe8OhzwAQRNt1MWi7sva5zHRjDFPPOtnp0YODlpMWUMfaHlK
 Ol6NR/MSTMC1PpuqSvApDBQL2QsV4Z6VoJkTCUo+B45L3hiBQLHQHhrIEQqgEnaa64lG
 Nq6hHK2y3JDaF0wz+7nwE81HS1SmhCSzUpbYo=
MIME-Version: 1.0
Received: by 10.114.24.3 with SMTP id 3mr1906402wax.31.1284254759887;
 Sat, 11 Sep 2010 18:25:59 -0700 (PDT)
Received: by 10.115.74.3 with HTTP; Sat, 11 Sep 2010 18:25:59 -0700 (PDT)
Date: Sun, 12 Sep 2010 09:25:59 +0800
Message-ID: <AANLkTinkNTDm4zKpZz2OhP5WZvRkPiH_UM-3C6ZkmVhb@mail.gmail.com>
From: Sterling Lamberto <lamberto.sterling@gmail.com>
To: zhang.fei3@zte.com.cn
Content-Type: multipart/alternative; boundary=00163641799fc3a931049005dc46
Cc: mpls@ietf.org, ccamp@ietf.org, mpls-tp@ietf.org
Subject: Re: [mpls] Collecting comments on associated bidirectional LSP
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
 <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
 <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 12 Sep 2010 01:25:39 -0000

--00163641799fc3a931049005dc46
Content-Type: text/plain; charset=ISO-8859-1

Hi Fei,
After a brief review of the draft, there are several points:
1. section 4.1, point 3, why node B sends PATH message of LSP2 with
ASSOCIATION object with same  value as that of LSP1? It seems a bit strange,
what's your consideration about that?
2. in section 4.2 peer mode, what if the backward LSP has been already setup
before setting up the forward LSP? In that case, if backward LSP without
ASSOCIATION object does not wish to be bound, how to handle that case?
3. will asymmetric bandwidth allocation for associated LSP be described in
future draft?

Lamberto.

==========================================================
Hi all,

Associated bidirectional LSP, defined in RFC5654, is useful for protection
switching, for OAM that requires a reply (from MIP or MEP), and for defect
correlation.

There are potentially several solutions, such as GMPLS call, the Association
object, and the LSP_TUNNEL_INTERFACE_ID object. Furthermore, the scheme
based on the extensions to

the Association object has been presented in IETF77, and there are some
discussions on the mailinglist.

We need to receive more comments on this topic to push this work forward,
then update the document,

http://tools.ietf.org/html/draft-zhang-mpls-tp-rsvpte-ext-associated-lsp-00,
which is recently expired.

Any comments are welome.

B.R.

Fei

:)

--00163641799fc3a931049005dc46
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div>Hi Fei,</div>
<div>After a brief review of the draft, there are several points:</div>
<div>1. section 4.1, point 3, why=A0node=A0B sends PATH message of LSP2 wit=
h ASSOCIATION object=A0with same=A0 value as that of LSP1? It seems a bit s=
trange, what&#39;s your consideration about that?</div>
<div>2. in section 4.2 peer mode, what if the backward LSP has been already=
 setup before setting up the forward LSP? In that case, if backward LSP wit=
hout ASSOCIATION object=A0does not wish to be bound, how to handle that cas=
e?</div>

<div>3. will asymmetric bandwidth allocation for associated LSP be describe=
d in future draft?</div>
<div>=A0</div>
<div>Lamberto.</div>
<div>=A0</div>
<div>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D</div>
<div>Hi all, <br><br><font face=3D"sans-serif" size=3D"2">Associated bidire=
ctional LSP, defined in RFC5654, is useful for</font><font size=3D"2"><tt> =
protection switching, for OAM that requires a reply (from MIP or MEP), and =
for defect correlation. </tt></font><br>
<br><font size=3D"2"><tt>There are potentially several solutions, such as G=
MPLS call, the Association object, and the LSP_TUNNEL_INTERFACE_ID object. =
Furthermore, the scheme based on the extensions to</tt></font> <br><br><fon=
t size=3D"2"><tt>the Association object has been presented in IETF77, and t=
here are some discussions on the mailinglist. </tt></font><br>
<br><font size=3D"2"><tt>We need to receive more comments on this topic to =
push this work forward, then update the document, </tt></font><br><br><font=
 size=3D"2"><tt><a href=3D"http://tools.ietf.org/html/draft-zhang-mpls-tp-r=
svpte-ext-associated-lsp-00">http://tools.ietf.org/html/draft-zhang-mpls-tp=
-rsvpte-ext-associated-lsp-00</a>, which is recently expired.</tt></font> <=
br>
<br><font size=3D"2"><tt>Any comments are welome.</tt></font> <br><br><font=
 size=3D"2"><tt>B.R.</tt></font> <br><br><font size=3D"2"><tt>Fei </tt></fo=
nt><br><br><font size=3D"2"><tt>:)</tt></font> </div>

--00163641799fc3a931049005dc46--
