Re: [Pce] PCEP ERO
"Adrian Farrel" <adrian@olddog.co.uk> Mon, 16 June 2014 13:59 UTC
Return-Path: <adrian@olddog.co.uk>
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 930401A0029 for <pce@ietfa.amsl.com>; Mon, 16 Jun 2014 06:59:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.9
X-Spam-Level:
X-Spam-Status: No, score=-101.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, USER_IN_WHITELIST=-100] autolearn=ham
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 u0bD7LQIQSW1 for <pce@ietfa.amsl.com>; Mon, 16 Jun 2014 06:59:54 -0700 (PDT)
Received: from asmtp5.iomartmail.com (asmtp5.iomartmail.com [62.128.201.176]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8360D1A0008 for <pce@ietf.org>; Mon, 16 Jun 2014 06:59:54 -0700 (PDT)
Received: from asmtp5.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp5.iomartmail.com (8.13.8/8.13.8) with ESMTP id s5GDxo19020931; Mon, 16 Jun 2014 14:59:50 +0100
Received: from 950129200 (4513.ip.megatro.com [46.253.45.13] (may be forged)) (authenticated bits=0) by asmtp5.iomartmail.com (8.13.8/8.13.8) with ESMTP id s5GDxnFE020908 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 16 Jun 2014 14:59:50 +0100
From: Adrian Farrel <adrian@olddog.co.uk>
To: 'Igor Bryskin' <IBryskin@advaoptical.com>, 'Dhruv Dhody' <dhruv.ietf@gmail.com>, 'Julien Meuric' <julien.meuric@orange.com>
References: <23CE718903A838468A8B325B80962F9B7556E603@szxeml556-mbs.china.huawei.com> <539EB1E9.2040008@orange.com> <CAB75xn475ROzMBxN1YY=4a+vqxgyYddBi3KQncetznLp3md_yA@mail.gmail.com> <00cb01cf8956$c92fcea0$5b8f6be0$@olddog.co.uk> <c8db482c6d2c4dedbfc8a4444763633b@ATL-SRV-MBX1.advaoptical.com>
In-Reply-To: <c8db482c6d2c4dedbfc8a4444763633b@ATL-SRV-MBX1.advaoptical.com>
Date: Mon, 16 Jun 2014 14:59:51 +0100
Message-ID: <010e01cf896b$3efb0d20$bcf12760$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQK1l1N/qAZMYeQ3qq/OkN2eGZIDxAHd47r8AmofzOgBUW/S0AIBaCiPmWrNz+A=
Content-Language: en-gb
X-TM-AS-MML: disable
X-TM-AS-Product-Ver: IMSS-7.1.0.1576-7.5.0.1017-20760.007
X-TM-AS-Result: No--40.280-10.0-31-10
X-imss-scan-details: No--40.280-10.0-31-10
X-TMASE-MatchedRID: hwsFDxVJcFmi+SMpuaYbamzBijri5+RVHFUfbqk2vLLzA+2i6Sr179Ew +lHrZKHlVWGMp4XddOjl1WOr70Uc34txqz5phrcNRiuPjII4dpJ742HbyXvuz47a7EVQuEMrwBc NAbqB9IlNYvDaO9t+nDWGBU0NLH/37K35r0y1/56M29hkek7Xd6TYf9v9flolfTmijOF2J84mqh yu6WdG0QZ5A9b/VHvWbyJ6my3Qt+gTY/HRCFabdNjko+KiQPUG4FBhMAaXjUxFRkv0B4bwgixJw y0d6Q5dwCvw6cgh9GT0oooVAwvHrVzabEGBFXGpZlRzaO1xpJ20NJ9wxH7tk4nFh++ML/iBO/Ze DlAvVGdt4WeAFQ+B01wKCBg8tH58okiHrSMXD7QdxBAG5/hkW8KAC/KBFs0QnvbaEOoeixOoBfC x2HzmBgKAepfv4IHnqvGFQ7EaOzSk0F4/j+0gRilrosmS0SOAYLTkznvC2b9NEl8XeFvcyJEEgo g03+h84vh2ZTYa+apJM0gKcNO/pdagiCnwHRd7ysTdXzwb9+HIaXDWlZeIbFVqIv0mjuMG4Q8Hl PP5GowjA2gQ1AzqY0n5yeZhaZqT7EkdYXi1lRGIWiitCNuhaRI1EOUVOliSYshnYWETuzMshthR aNLvKJtkedx/3uErOTazGT39uuRLhDcj8t5Q56wOh3D3JSTGQKuv8uQBDjrJ2i9a4v4pV1PWus3 yxQNWt+odoSua73aRk6XtYogiarQ/aqQZTRfKwLhRRmviVIWig9GohOPnOKu6xVHLhqfxvECLuM +h4RB+3BndfXUhXQ==
Archived-At: http://mailarchive.ietf.org/arch/msg/pce/2q8Q-cnyGLkTH9s2uRO6WGp5Rvc
Cc: pce@ietf.org
Subject: Re: [Pce] PCEP ERO
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: adrian@olddog.co.uk
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: <http://www.ietf.org/mail-archive/web/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: Mon, 16 Jun 2014 13:59:57 -0000
OK, so this is an RSVP-TE question, not a PCEP one :-) I am distracted at the moment because I am at the PACE workshop on Future Uses of PCE http://www.craax.upc.edu/saconet2014/pace2014.html (twitter @paceict) However... I think that your question is not specific to unnumbered interfaces. Consider a numbered interface that appears in an ERO. The interface is not a local address, so it an address that applies to the "next hop". But is it an incoming or outgoing interface at the next hop? Well, the rule is "find a route to the next hop". So that inevitably means that if you want to control the outgoing interface from a node, you need to include some other hop information (ideally the incoming interface) as a hop earlier in the ERO. A > -----Original Message----- > From: Igor Bryskin [mailto:IBryskin@advaoptical.com] > Sent: 16 June 2014 13:23 > To: adrian@olddog.co.uk; 'Dhruv Dhody'; 'Julien Meuric' > Cc: pce@ietf.org > Subject: RE: [Pce] PCEP ERO > > Hello, > You are right Julien and Adrian, this is a very old issue. One thing that has been > missing IMO is a flag in a numbered/unnumbered link ERSO indicating whether > the indicated side of the link is outbound or inbound wrt the path direction from > its source to destination. The lack of said flag has been especially a problem when > combined with the LOOSE flag. Consider, for example, the situation when a > 1.1.24.1/loose is found in the ERO. If 1.1.24.1 interface is meant to be inbound, > the path should *enter* the NE that terminates the interface. However, If > 1.1.24.1 interface is meant to be outbound, the path should *exit*the said NE. > So, if the ERO is specified as a path computation constraint, the PCE may produce > very different resulting paths depending on the PCE's assumptions/ > interpretations. The introduction of said flag would resolve the ambiguity and > provide the flexibility (e.g. Druv is talking about) for the ERO encoding. > > Regards, > Igor > > > -----Original Message----- > From: Pce [mailto:pce-bounces@ietf.org] On Behalf Of Adrian Farrel > Sent: Monday, June 16, 2014 7:33 AM > To: 'Dhruv Dhody'; 'Julien Meuric' > Cc: pce@ietf.org > Subject: Re: [Pce] PCEP ERO > > Julien is right (of course). > > This survey led (in part) to RFC 4990. section 6 may be what Dhruv is looking for. > > A nasty question lurking in the background is whether a PCC needs to indicate > which construction of ERO is prefers. Consider if the interface was CLI not > PCEP: in this case the supported construction of ERO is part of the CLI definition. > However, given that most of the ERO is not for local consumption and does not > need to be examined by the PCC, this question may be of debatable value. > > Adrian > > > -----Original Message----- > > From: Pce [mailto:pce-bounces@ietf.org] On Behalf Of Dhruv Dhody > > Sent: 16 June 2014 10:27 > > To: Julien Meuric > > Cc: pce@ietf.org > > Subject: Re: [Pce] PCEP ERO > > > > Hi Julien, > > > > Thanks for the pointer, this surely helps. > > Time to dive into the archives..... > > > > Dhruv > > > > On Mon, Jun 16, 2014 at 2:29 PM, Julien Meuric > > <julien.meuric@orange.com> > > wrote: > > > Hi Dhruv. > > > > > > PCEP does not mandates more rules on ERO than RSVP-TE, which reminds > > > me > > of > > > an old discussion in CCAMP. You may want to have a look at > > > http://tools.ietf.org/html/draft-farrel-ccamp-ero-survey-00 and dive > > > into the associated thread back in 2006. > > > > > > Julien > > > > > > > > > Jun. 16, 2014 - Dhruv Dhody: > > >> > > >> Attaching the figure in a pdf, in case you could not view in my > > >> previous mail. > > >> > > >> Regards, > > >> > > >> Dhruv > > >> > > >> --------------------------------------------------------------- > > >> > > >> *Dhruv Dhody * > > >> > > >> > > >> System Architect, > > >> > > >> Huawei Technologies India Pvt. Ltd., > > >> > > >> Banagalore > > >> > > >> Mobile: +91-9845062422 > > >> > > >> This e-mail and its attachments contain confidential information > > >> from HUAWEI, which > > >> > > >> is intended only for the person or entity whose address is listed above. > > >> Any use of the > > >> > > >> information contained herein in any way (including, but not limited > > >> to, total or partial > > >> > > >> disclosure, reproduction, or dissemination) by persons other than > > >> the intended > > >> > > >> recipient(s) is prohibited. If you receive this e-mail in error, > > >> please notify the sender by > > >> > > >> phone or email immediately and delete it! > > >> > > >> *From:*Dhruv Dhody > > >> *Sent:* 16 June 2014 11:52 > > >> *To:* pce@ietf.org > > >> *Subject:* PCEP ERO > > >> > > >> > > >> Dear WG, > > >> > > >> > > >> Consider the below topology, PCE computes a path from RTA to RTC. > > >> > > >> This path maybe encoded in PCEP ERO as - > > >> > > >> ~ (10.1.1.1, 10.1.1.2, 20.1.1.1, 20.1.1.2) > > >> > > >> or > > >> > > >> ~ (10.1.1.2, 20.1.1.1, 20.1.1.2) [without local IP address of > > >> ingress] > > >> > > >> IMO both should be considered as viable options. > > >> > > >> Is there any reason for PCC to consider one of them as incorrect? > > >> > > >> Regards, > > >> > > >> Dhruv > > >> > > >> --------------------------------------------------------------- > > >> > > >> Dhruv Dhody > > >> > > >> System Architect, > > >> > > >> Huawei Technologies India Pvt. Ltd., > > >> > > >> Banagalore > > >> > > >> Mobile: +91-9845062422 > > >> > > >> > > >> > > >> _______________________________________________ > > >> Pce mailing list > > >> Pce@ietf.org > > >> https://www.ietf.org/mailman/listinfo/pce > > >> > > > > > > _______________________________________________ > > > Pce mailing list > > > Pce@ietf.org > > > https://www.ietf.org/mailman/listinfo/pce > > > > _______________________________________________ > > Pce mailing list > > 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] PCEP ERO Julien Meuric
- [Pce] PCEP ERO Dhruv Dhody
- Re: [Pce] PCEP ERO Dhruv Dhody
- Re: [Pce] PCEP ERO Dhruv Dhody
- Re: [Pce] PCEP ERO Dhruv Dhody
- Re: [Pce] PCEP ERO Adrian Farrel
- Re: [Pce] PCEP ERO Igor Bryskin
- Re: [Pce] PCEP ERO Adrian Farrel
- Re: [Pce] PCEP ERO Zhangxian (Xian)
- Re: [Pce] PCEP ERO Adrian Farrel
- Re: [Pce] PCEP ERO Igor Bryskin
- Re: [Pce] PCEP ERO Adrian Farrel
- Re: [Pce] PCEP ERO Zhangxian (Xian)
- Re: [Pce] PCEP ERO Igor Bryskin
- Re: [Pce] PCEP ERO Eric Gray
- Re: [Pce] PCEP ERO Igor Bryskin
- Re: [Pce] PCEP ERO Eric Gray
- Re: [Pce] PCEP ERO Igor Bryskin