Re: [Pce] Switching type Constraint in PCEP
"fabien.verhaeghe" <fabien.verhaeghe@atosorigin.com> Wed, 28 March 2007 14:06 UTC
Return-path: <pce-bounces@lists.ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HWYnN-0002Jo-3O; Wed, 28 Mar 2007 10:06:37 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HWYnL-0002Jj-W3 for pce@ietf.org; Wed, 28 Mar 2007 10:06:35 -0400
Received: from smtp1.mail.atosorigin.com ([160.92.103.80] helo=wpwuee01s.mail.mercury.atosorigin.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HWYnG-0001Wi-Fn for pce@ietf.org; Wed, 28 Mar 2007 10:06:35 -0400
Received: from wpwuee01s.mail.mercury.atosorigin.com (localhost [127.0.0.1]) by wpwuee01s.mail.mercury.atosorigin.com (Postfix) with ESMTP id 9B297F4085; Wed, 28 Mar 2007 16:06:27 +0200 (CEST)
Received: from AOFR11476 (unknown [10.10.10.10]) by wpwuee01s.mail.mercury.atosorigin.com (Postfix) with ESMTP id 79DE6F4089; Wed, 28 Mar 2007 16:06:27 +0200 (CEST)
Message-ID: <002a01c77142$2cda9050$15600337@AOFR11476>
From: "fabien.verhaeghe" <fabien.verhaeghe@atosorigin.com>
To: Adrian Farrel <adrian@olddog.co.uk>, LE ROUX Jean-Louis RD-CORE-LAN <jeanlouis.leroux@orange-ftgroup.com>, Dan Li <danli@huawei.com>, pce@ietf.org
References: <D109C8C97C15294495117745780657AE074F261A@ftrdmel1.rd.francetelecom.fr> <0cb301c7712e$c1f03e10$ea138182@your029b8cecfe>
Subject: Re: [Pce] Switching type Constraint in PCEP
Date: Wed, 28 Mar 2007 16:05:42 +0200
MIME-Version: 1.0
Content-Type: text/plain; format="flowed"; charset="iso-8859-1"; reply-type="response"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.3028
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3028
X-Virus-Scanned: ClamAV using ClamSMTP
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 848ed35f2a4fc0638fa89629cb640f48
Cc:
X-BeenThere: pce@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Path Computation Element <pce.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/pce>
List-Post: <mailto:pce@lists.ietf.org>
List-Help: <mailto:pce-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@lists.ietf.org?subject=subscribe>
Errors-To: pce-bounces@lists.ietf.org
Hi Dan, JL, Adrian, Reading the generic and inter layer requirement documents it is not clear to me if Switching Type is really specific to inter layer application. As far as I understand inter-layer requirement refers to path computation which result path may comprise multiple layer technologies. Though I understand Switching type is required in this context, it is also required for mono layer path computation in a multi-layer environment (e.g. to computate a Lambda path using a TE Database that contains also TDM TE Links). So it is more a GMPLS specific requirement to me. Acually it is not clear to me what is the scope of generic and "application specific" requirements. Generic Requirement RFC4657 section 5.1.16 mention Switching and encoding type as "GMPLS specific requirements". Does it mean "GMPLS specific" is "considered as generic? Concerning the necessity of "encoding type" in PCEP I have to admit that I'm not sure to correctly understand the meaning of this parameter in the GMPLS architecture :-). What I understand at least is that it is both an interface and an LSP property, so from this it seems to be required in PCEP. I would be interested to see discussion about encoding type requirement in PCEP cause it may clarify the encoding type meaning to me ;-). Regards Fabien ----- Original Message ----- From: "Adrian Farrel" <adrian@olddog.co.uk> To: "LE ROUX Jean-Louis RD-CORE-LAN" <jeanlouis.leroux@orange-ftgroup.com>; "Dan Li" <danli@huawei.com>; "fabien.verhaeghe" <fabien.verhaeghe@atosorigin.com>; <pce@ietf.org> Sent: Wednesday, March 28, 2007 1:46 PM Subject: Re: [Pce] Switching type Constraint in PCEP Just to complete the sequence of referenced I-Ds... http://www.ietf.org/internet-drafts/draft-ietf-pce-inter-layer-req-04.txt discusses the requirements for multi-layer path computation (while http://www.ietf.org/internet-drafts/draft-ietf-pce-inter-layer-frwk-03.txt gives a framework for the use of PCE in a multi-layer network). Section 5.1.3 of draft-ietf-pce-inter-layer-req-04.txt describes the specific requirements that you mention for switching type. And section 5.1.4 discusses adaptation capabilities. We have not, so far, added a requirement for encoding type and are not clear whether this is a constraint that is necessary. We'd be interested to have this discussion. Before the Prague meeting, Eiji Oki started to put together the necessary protocol extensions in support of this work, but we held off publication because the base PCEP needed to advance a bit more. I guess this sounds like the community is ready for this draft now. Cheers, Adrian ----- Original Message ----- From: "LE ROUX Jean-Louis RD-CORE-LAN" <jeanlouis.leroux@orange-ftgroup.com> To: "Dan Li" <danli@huawei.com>; "fabien.verhaeghe" <fabien.verhaeghe@atosorigin.com>; <pce@ietf.org> Sent: Wednesday, March 28, 2007 11:18 AM Subject: RE: [Pce] Switching type Constraint in PCEP Hi Fabien, The switching type/encoding type used to be carried in earlier versions of PCEP ( GENERALIZED LABEL OBJECT in http://www.watersprings.org/pub/id/draft-vasseur-pce-pcep-00.txt). We decided to remove it from the base spec as this is application specific. This will be covered in a separate document (for instance switching/encoding type could be encoded in a optional TLV of the LSPA object). Best Regards, JL ________________________________ De : Dan Li [mailto:danli@huawei.com] Envoyé : mercredi 28 mars 2007 11:36 À : fabien.verhaeghe; pce@ietf.org Objet : Re: [Pce] Switching type Constraint in PCEP Hi Fabien, There is a draft "draft-otani-ccamp-gmpls-cspf-constraints-05.txt" which may relate to this issue. But the switching/encoding type may be considered as an attribute of a TE-link, so I doubt it has something to do with the PCEP. Regards, Dan ----- Original Message ----- From: fabien.verhaeghe <mailto:fabien.verhaeghe@atosorigin.com> To: pce@ietf.org Sent: Wednesday, March 28, 2007 4:56 PM Subject: [Pce] Switching type Constraint in PCEP Hi, In RFC4657 one of the generic requirement concerns the support of switching/encoding type constraint for GMPLS. Is there any ongoing work about this item? Thanks Fabien ________________________________ _______________________________________________ Pce mailing list Pce@lists.ietf.org https://www1.ietf.org/mailman/listinfo/pce > _______________________________________________ > Pce mailing list > Pce@lists.ietf.org > https://www1.ietf.org/mailman/listinfo/pce > _______________________________________________ Pce mailing list Pce@lists.ietf.org https://www1.ietf.org/mailman/listinfo/pce
- [Pce] Switching type Constraint in PCEP fabien.verhaeghe
- Re: [Pce] Switching type Constraint in PCEP Dan Li
- RE: [Pce] Switching type Constraint in PCEP LE ROUX Jean-Louis RD-CORE-LAN
- Re: [Pce] Switching type Constraint in PCEP Adrian Farrel
- Re: [Pce] Switching type Constraint in PCEP fabien.verhaeghe
- Re: [Pce] Switching type Constraint in PCEP Adrian Farrel
- Re: [Pce] Switching type Constraint in PCEP Tomohiro Otani
- Re: [Pce] Switching type Constraint in PCEP fabien.verhaeghe
- Re: [Pce] Switching type Constraint in PCEP fabien.verhaeghe
- RE: [Pce] Switching type Constraint in PCEP Daniel King