Re: [Pce] Query on Usage of LSP Identifier TLV in SR
Julien Meuric <julien.meuric@orange.com> Tue, 13 October 2015 09:07 UTC
Return-Path: <julien.meuric@orange.com>
X-Original-To: pce@ietfa.amsl.com
Delivered-To: pce@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ECC641A1EF6; Tue, 13 Oct 2015 02:07:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.106
X-Spam-Level:
X-Spam-Status: No, score=0.106 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, FREEMAIL_REPLY=1, HELO_EQ_FR=0.35, SPF_SOFTFAIL=0.665, T_RP_MATCHES_RCVD=-0.01] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7Gl1x-3-KT-k; Tue, 13 Oct 2015 02:07:54 -0700 (PDT)
Received: from p-mail2.rd.orange.com (p-mail2.rd.orange.com [161.106.1.3]) by ietfa.amsl.com (Postfix) with ESMTP id 797D41A1EF1; Tue, 13 Oct 2015 02:07:54 -0700 (PDT)
Received: from p-mail2.rd.orange.com (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with SMTP id 90CC5E300A4; Tue, 13 Oct 2015 11:07:53 +0200 (CEST)
Received: from FTRDCH01.rd.francetelecom.fr (unknown [10.194.32.11]) by p-mail2.rd.orange.com (Postfix) with ESMTP id 81C25E30096; Tue, 13 Oct 2015 11:07:53 +0200 (CEST)
Received: from [10.193.71.204] (10.193.71.204) by FTRDCH01.rd.francetelecom.fr (10.194.32.11) with Microsoft SMTP Server id 14.3.224.2; Tue, 13 Oct 2015 11:07:52 +0200
To: Girish Birajdar <girish134@gmail.com>
References: <23CE718903A838468A8B325B80962F9B8C421A83@BLREML509-MBX.china.huawei.com> <CAJO-zKeE-5L8pM-x-8U=VgzuLPZRxmgxf=Q4Co4x-576QoxVYw@mail.gmail.com>
From: Julien Meuric <julien.meuric@orange.com>
Organization: Orange
Message-ID: <561CC9E9.1060401@orange.com>
Date: Tue, 13 Oct 2015 11:07:53 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0
MIME-Version: 1.0
In-Reply-To: <CAJO-zKeE-5L8pM-x-8U=VgzuLPZRxmgxf=Q4Co4x-576QoxVYw@mail.gmail.com>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/pce/oXAa8lFD7poeTnbzEq_2FoND5mU>
Cc: "draft-ietf-pce-stateful-pce@tools.ietf.org" <draft-ietf-pce-stateful-pce@tools.ietf.org>, "pce@ietf.org" <pce@ietf.org>, "draft-ietf-pce-segment-routing@ietf.org" <draft-ietf-pce-segment-routing@ietf.org>
Subject: Re: [Pce] Query on Usage of LSP Identifier TLV in SR
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Path Computation Element <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pce/>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 13 Oct 2015 09:07:56 -0000
Hi Girish, Due to the very different levels of maturity between stateful-pce and MBB I-Ds, we do not see them merging. MBB I-D was very briefly discussed on the list a while ago, we do not know what the plans of the authors are... Regards, Julien Oct. 12, 2015 - girish134@gmail.com: > > piggy backing on Dhruv email ... > > During PCUpdate for SR LSP - MBB process mentioned in > draft-tanaka-pce-stateful-pce-mbb applicable? The MBB draft has > expired, will it be incorporated in stateful-pce draft? > > Thanks, > Girish > > On Sun, Oct 11, 2015 at 10:58 PM, Dhruv Dhody <dhruv.dhody@huawei.com > <mailto:dhruv.dhody@huawei.com>> wrote: > > Hi Authors, > > In the stateful PCE draft [1], it says – > > The LSP Identifiers TLV MUST be included in the LSP object in PCRpt > > messages for RSVP-signaled LSPs. > > The SR draft [2] did not mention anything about LSP Identifier TLV. > > And in implementations that I am aware of, SR-TE LSP still uses > the LSP-Identifier TLV. Is that correct? (I personally think so!!) > > If yes, do you think there is a need to update – > > -[1] to say all LSPs (and not just RSVP-signaled). > > -Or [2] to say that LSP-Identifier TLV are also applicable to SR > and MUST be included. > > Thanks! > > Dhruv > > [1] > https://tools.ietf.org/html/draft-ietf-pce-stateful-pce-11#section-7.3.1 > > [2] http://datatracker.ietf.org/doc/draft-ietf-pce-segment-routing/ > > > _______________________________________________ > Pce mailing list > Pce@ietf.org <mailto:Pce@ietf.org> > https://www.ietf.org/mailman/listinfo/pce > > > > > _______________________________________________ > Pce mailing list > Pce@ietf.org > https://www.ietf.org/mailman/listinfo/pce
- Re: [Pce] Query on Usage of LSP Identifier TLV in… Jeff Tantsura
- [Pce] Query on Usage of LSP Identifier TLV in SR Dhruv Dhody
- Re: [Pce] Query on Usage of LSP Identifier TLV in… Girish Birajdar
- Re: [Pce] Query on Usage of LSP Identifier TLV in… Julien Meuric
- Re: [Pce] Query on Usage of LSP Identifier TLV in… Dhruv Dhody
- Re: [Pce] Query on Usage of LSP Identifier TLV in… Robert Varga
- Re: [Pce] Query on Usage of LSP Identifier TLV in… Dhruv Dhody
- Re: [Pce] Query on Usage of LSP Identifier TLV in… Dhruv Dhody
- Re: [Pce] Query on Usage of LSP Identifier TLV in… Dhruv Dhody
- Re: [Pce] Query on Usage of LSP Identifier TLV in… Dhruv Dhody