[Pce] ISIS Separate instances [Was: New PCE working group I-Ds]

"Adrian Farrel" <adrian@olddog.co.uk> Thu, 16 August 2007 09:30 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 1ILbgx-0004Uk-Hj; Thu, 16 Aug 2007 05:30:59 -0400
Received: from pce by megatron.ietf.org with local (Exim 4.43) id 1ILbgw-0004N0-4z for pce-confirm+ok@megatron.ietf.org; Thu, 16 Aug 2007 05:30:58 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1ILbgv-0004KB-Ne for pce@ietf.org; Thu, 16 Aug 2007 05:30:57 -0400
Received: from asmtp1.iomartmail.com ([62.128.201.248]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ILbgu-0008Ii-6G for pce@ietf.org; Thu, 16 Aug 2007 05:30:57 -0400
Received: from asmtp1.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp1.iomartmail.com (8.12.11.20060308/8.12.8) with ESMTP id l7G9Ur0g009539; Thu, 16 Aug 2007 10:30:53 +0100
Received: from your029b8cecfe (dsl-sp-81-140-15-32.in-addr.broadbandscope.com [81.140.15.32]) (authenticated bits=0) by asmtp1.iomartmail.com (8.12.11.20060308/8.12.8) with ESMTP id l7G9UkqE009413; Thu, 16 Aug 2007 10:30:50 +0100
Message-ID: <03a401c7dfe8$1bcf0fb0$0300a8c0@your029b8cecfe>
From: Adrian Farrel <adrian@olddog.co.uk>
To: dpapadimitriou@psg.com, JP Vasseur <jvasseur@cisco.com>
References: <011001c7dcf6$ff420210$0300a8c0@your029b8cecfe> <8144761F31F48D43AD53D09F5350E380EDCC7A@FRVELSMBS22.ad2.ad.alcatel.com> <D109C8C97C15294495117745780657AE082031D3@ftrdmel1> <8144761F31F48D43AD53D09F5350E380EDCCF4@FRVELSMBS22.ad2.ad.alcatel.com><3E693EBA-BB4C-4CD4-923B-A8C71AC47214@cisco.com> <46C3F9F9.7030805@psg.com>
Date: Thu, 16 Aug 2007 10:30:32 +0100
MIME-Version: 1.0
Content-Type: text/plain; format="flowed"; charset="iso-8859-1"; reply-type="response"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.2180
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4d87d2aa806f79fed918a62e834505ca
Cc: Les Ginsberg <ginsberg@cisco.com>, Christian Hopps <chopps@rawdofmt.org>, pce@ietf.org, dward@cisco.com
Subject: [Pce] ISIS Separate instances [Was: New PCE working group I-Ds]
X-BeenThere: pce@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Adrian Farrel <adrian@olddog.co.uk>
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

>>>>> - still unclear to me whether isis pce disc. will or not use a
>>>>>   separate inst. (cf. gen-app discussion at isis working group)
>>>>
>>>> ISIS pce disc relies on procedures defined in 4971.
>>>> This is a deployment issue to use same or separate instances.
>>>
>>> do you assume that you would leave such choice possible ? i
>>> was left with the impression after last isis mtg discussion
>>> that there is a real incentive for making this a recommended
>>> behavior
>>
>> Just to avoid confusion: the PCED is being carried within the ISIS
>> Router Capability TLV, the processing of which is defined in RFC4971.
>
> indeed, i am not referring to 4971 at such, i am referring to the
> fact that if exchanging non-routing info w/ is-is result in recommending 
> separated instance then the ISIS PCE disc. w-g doc becomes a prime 
> candidate for such recommendation. just a matter of consistency.

My understanding of the discussion in the ISIS working group is that:
- They are tending towards believing that there should be a separation 
between
   flooding of IP link-state information and *all* other information
- They think that such a separation might reasonably be handled by using
   multiple (greater than one) instances of ISIS
- They have not yet reached a conclusion as to whether existing extensions
   fall into this category, but there was building opinion that TE 
advertisements
   might be strong candidates for off-loading to a second instance
- The Router Capability TLV would also be up for consideration

No slides for this topic from the ISIS working group in Chicago seem to have 
been posted yet.

The most recent version of the relevant I-D appears to be 
http://www.ietf.org/internet-drafts/draft-ginsberg-isis-genapp-01.txt 
although I know Les was planning some updates as a result of the Chicago 
meeting.

It seems to me that:
1. The ISIS working group is not going to reach a conclusion on this
   in a hurry.
2. When they do reach a conclusion we MUST fall in with it.
3. In the mean time, just as TE and Router Caps are currently
   carried in a single instance, the PCE discovery will be so
   carried.
4. You should all contribute to this discussion on the ISIS mailing list.

Cheers,
Adrian 




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