Re: [Pce] Re: Progress on draft-ietf-pce-discovery-reqs-01.txt

JP Vasseur <jvasseur@cisco.com> Thu, 08 September 2005 21:30 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EDTyo-0005OZ-Qq; Thu, 08 Sep 2005 17:30:46 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EDTyn-0005OM-Oe for pce@megatron.ietf.org; Thu, 08 Sep 2005 17:30:45 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA19195 for <pce@ietf.org>; Thu, 8 Sep 2005 17:30:42 -0400 (EDT)
Received: from sj-iport-4.cisco.com ([171.68.10.86]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EDU2F-0000XT-DF for pce@ietf.org; Thu, 08 Sep 2005 17:34:20 -0400
Received: from sj-core-4.cisco.com ([171.68.223.138]) by sj-iport-4.cisco.com with ESMTP; 08 Sep 2005 14:30:37 -0700
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com [64.102.31.102]) by sj-core-4.cisco.com (8.12.10/8.12.6) with ESMTP id j88LUTum022427; Thu, 8 Sep 2005 14:30:33 -0700 (PDT)
Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211); Thu, 8 Sep 2005 17:30:11 -0400
Received: from [192.168.1.100] ([10.86.240.233]) by xfe-rtp-202.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211); Thu, 8 Sep 2005 17:30:10 -0400
In-Reply-To: <20050908211059.90810.qmail@web30508.mail.mud.yahoo.com>
References: <20050908211059.90810.qmail@web30508.mail.mud.yahoo.com>
Mime-Version: 1.0 (Apple Message framework v734)
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Message-Id: <9FCAD292-562F-472F-8FDB-0E884BD2B512@cisco.com>
Content-Transfer-Encoding: 7bit
From: JP Vasseur <jvasseur@cisco.com>
Subject: Re: [Pce] Re: Progress on draft-ietf-pce-discovery-reqs-01.txt
Date: Thu, 08 Sep 2005 17:30:38 -0400
To: Stephen Morris <stephenbjm@yahoo.com>
X-Mailer: Apple Mail (2.734)
X-OriginalArrivalTime: 08 Sep 2005 21:30:10.0434 (UTC) FILETIME=[7D9ED620:01C5B4BC]
X-Spam-Score: 0.7 (/)
X-Scan-Signature: 9cc83ac38bbbabacbf00f656311dd8d8
Content-Transfer-Encoding: 7bit
Cc: pce@ietf.org
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>
Sender: pce-bounces@lists.ietf.org
Errors-To: pce-bounces@lists.ietf.org

Hi Stephen,

On Sep 8, 2005, at 5:10 PM, Stephen Morris wrote:

> Hi JP
> I'd be happy to help with the MIB work.

good, thanks.

JP.

> Just one reply
> below :-).
> Best wishes
> Stephen
>
> --- JP Vasseur <jvasseur@cisco.com> wrote:
>
>
>> Hi,
>>
>> Adding a few comments.
>>
>> On Sep 7, 2005, at 6:00 AM, Adrian Farrel wrote:
>>
>>
>>> Hi,
>>>
>>>
>>>
>>>> A network manager would probably want NMS data on
>>>>
>> all
>>
>>>> of the PCEs in the network. It's a useful
>>>>
>> mechanism in
>>
>>>> discovery to let the managed entities (PCEs in
>>>>
>> this
>>
>>>> case) notify the NMS about changes (such as
>>>> capability).
>>>>
>>
>> As pointed out in other emails related to this
>> thread, there is
>> nothing preventing the NMS to listen the PCE
>> discovery protocol.
>>
>> That said,
>> (1) NMS will undoubtedly require more data that what
>> will/should be
>> provided by PCE discovery (since PCCs will not need
>> as much data as NMS)
>> (2) Some NMS may not support the PCE discovery
>> protocol.
>>
>> We're seeking for volunteers to work on future MIBs
>> ... Could we
>> count you in ?
>>
>>
>>>> This is particularly so in cases where
>>>> there are many such entities.
>>>>
>>>>
>>>
>>> Yes, but let's not get things out of proportion.
>>>
>> There will always
>>
>>> be at
>>> least as many network switches/routers as there
>>>
>> are PCEs in any
>>
>>> network
>>> (such is the nature of the architecture).
>>>
>>> How do switches/routers currently keep their
>>>
>> capabilities (i.e.
>>
>>> inventory)
>>> up-to-date with NMS? Why shouldn't PCEs use the
>>>
>> same technique?
>>
>>>
>>>
>>>
>>>> So, I think we have 2 related points here:
>>>> (1) External entities (e.g., NMS) should be able
>>>>
>> to
>>
>>>> listen in on PCE changes, including detecting new
>>>>
>> PCEs
>>
>>>> as they appear. This reduces polling.
>>>>
>>>>
>>>
>>> Agreed. If the NMS is capable of listening, there
>>>
>> is nothing in any
>>
>>> of the
>>> suggestions that prohibits it. However, we should
>>>
>> not, I think,
>>
>>> make it
>>> compulsory for an NMS to listen to the PCE
>>>
>> discovery protocols
>>
>>> since this
>>> may be operationally impossible in some
>>>
>> configurations.
>>
>
> Good point. Often, the NMS will have its own of
> discovery software that relies on a heady cocktail of
> MIBs, ping, etc. I guess my main point is that the PCE
> discovery requirements should try to make life a
> little easier on the NMS :-).
>
>
>>>
>>>
>>
>> See my comment (2) above.
>>
>>
>>>
>>>
>>>> (2) PCEs should be able to assist the NMS in
>>>> discovering them and their capabilities
>>>>
>>>>
>>>
>>> Certainly if we allow capabilities exchange as
>>>
>> part of the PCC-PCE
>>
>>> protocol, this would be possible. The NMS would
>>>
>> simply behave as a PCC
>>
>>> (which it will probably want to do anyway for
>>>
>> computational purposes).
>>
>>>
>>>
>>
>> I'm not really convinced here ... If the NMS does
>> not require path
>> computation (which is likely to be the case in
>> various
>> circumstances), having the NMS acting as a PCC (even
>> if the PCE
>> communication protocol support detailed capability
>> discovery), I'd
>> prefer the NMS to rely on MIBs.
>>
>> Thanks.
>>
>> JP.
>>
>>
>>>
>>>
>>>> I'm basically trying to reduce the amount of
>>>> discovery-related traffic. The latter often gives
>>>> network management a bad name :-).
>>>>
>>>> Best wishes
>>>> Stephen
>>>>
>>>> --- Adrian Farrel <adrian@olddog.co.uk> wrote:
>>>>
>>>>
>>>>
>>>>> Hi,
>>>>>
>>>>> Jean-Louis is right; the requirement is focused
>>>>>
>> on
>>
>>>>> allowing PCEs to convey
>>>>> information to PCCs.
>>>>>
>>>>> Another entity would be able to "listen in" and
>>>>> gather information for its
>>>>> own use, but such a requirement is out of scope
>>>>>
>> for
>>
>>>>> this document.
>>>>>
>>>>> I guess it depends on the purpose of the
>>>>>
>> function
>>
>>>>> you are suggesting. For
>>>>> example, if you want the NMS to be able to track
>>>>>
>> the
>>
>>>>> status of the PCE,
>>>>> this would probably be a perfectly adequate
>>>>> technique. However, it does
>>>>> rely on the NMS being able to listen in. That
>>>>>
>> is:
>>
>>>>> suppose the solution to
>>>>> PCE discovery is an opaque LSA in OSPF; you
>>>>>
>> would
>>
>>>>> need the NMS to be able
>>>>> to participate (at least passively) in the OSPF
>>>>> exchanges. Since the NMS
>>>>> may be remote through a distinct management
>>>>>
>> plane
>>
>>>>> network, this might not
>>>>> be possible.
>>>>>
>>>>> The alternative solution to gathering status
>>>>> information at the NMS would
>>>>> appear to be unchanged from the way network
>>>>>
>> devices
>>
>>>>> report status
>>>>> information today. From an IETF standardisation
>>>>> point of view, this
>>>>> requires MIB modules to allow the NMS to read
>>>>> information and to let the
>>>>> PCE report asynchronous Notifications.
>>>>>
>> Obviously,
>>
>>>>> piles of other
>>>>> proprietary or standard mechanisms exist outside
>>>>>
>> the
>>
>>>>> IETF.
>>>>>
>>>>> Cheers,
>>>>> Adrian
>>>>>
>>>>> ----- Original Message -----
>>>>> From: "LE ROUX Jean-Louis RD-CORE-LAN"
>>>>> <jeanlouis.leroux@francetelecom.com>
>>>>> To: "Stephen Morris" <stephenbjm@yahoo.com>;
>>>>> <dpapadimitriou@psg.com>;
>>>>> <dimitri.papadimitriou@alcatel.be>; "JP Vasseur"
>>>>> <jvasseur@cisco.com>
>>>>> Cc: "Ting_Wo Chung" <ting_wo.chung@bell.ca>;
>>>>> <pce@ietf.org>; "Richard
>>>>> Rabbat" <richard.rabbat@us.fujitsu.com>;
>>>>> "raymond.zhang"
>>>>> <raymond.zhang@bt.infonet.com>; "Paul Mabey"
>>>>> <paul.mabey@qwest.com>
>>>>> Sent: Monday, September 05, 2005 6:49 AM
>>>>> Subject: RE: [Pce] Re: Progress on
>>>>> draft-ietf-pce-discovery-reqs-01.txt
>>>>>
>>>>>
>>>>> Hi Stephen,
>>>>>
>>>>> If the "interested entity" is a PCC then the
>>>>>
>> answer
>>
>>>>> is YES.
>>>>>
>>>>>
>>>>> Regards
>>>>>
>>>>> JL
>>>>>
>>>>>
>>>>>
>>>>>> -----Message d'origine-----
>>>>>> De : pce-bounces@lists.ietf.org
>>>>>> [mailto:pce-bounces@lists.ietf.org] De la part
>>>>>>
>> de
>>
>>
> === message truncated ===
>
>
>
>
> ___________________________________________________________
> How much free photo storage do you get? Store your holiday
> snaps for FREE with Yahoo! Photos http://uk.photos.yahoo.com
>

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