Re: [Pce] New Version Notification for draft-lu-ospf-area-tlv-01.txt

Wenhu Lu <wenhu.lu@ericsson.com> Tue, 19 July 2011 21:32 UTC

Return-Path: <wenhu.lu@ericsson.com>
X-Original-To: pce@ietfa.amsl.com
Delivered-To: pce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7E1FA11E808B for <pce@ietfa.amsl.com>; Tue, 19 Jul 2011 14:32:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level:
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RLVhhtjsFcQa for <pce@ietfa.amsl.com>; Tue, 19 Jul 2011 14:32:46 -0700 (PDT)
Received: from imr3.ericy.com (imr3.ericy.com [198.24.6.13]) by ietfa.amsl.com (Postfix) with ESMTP id D2BA511E8087 for <pce@ietf.org>; Tue, 19 Jul 2011 14:32:39 -0700 (PDT)
Received: from eusaamw0706.eamcs.ericsson.se ([147.117.20.31]) by imr3.ericy.com (8.13.8/8.13.8) with ESMTP id p6JLWZ17009903 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 19 Jul 2011 16:32:35 -0500
Received: from EUSAACMS0703.eamcs.ericsson.se ([169.254.1.253]) by eusaamw0706.eamcs.ericsson.se ([147.117.20.31]) with mapi; Tue, 19 Jul 2011 17:32:34 -0400
From: Wenhu Lu <wenhu.lu@ericsson.com>
To: Dhruv Dhody <dhruvd@huawei.com>, 'JP Vasseur' <jpv@cisco.com>
Date: Tue, 19 Jul 2011 17:32:33 -0400
Thread-Topic: [Pce] New Version Notification for draft-lu-ospf-area-tlv-01.txt
Thread-Index: AcxCD/dtvi2qNmg4QZK1YWwGwHVOzwAlksPwAOch8wA=
Message-ID: <8249B703AE8442429AF89B86E8206AA26F41373471@EUSAACMS0703.eamcs.ericsson.se>
References: <8249B703AE8442429AF89B86E8206AA26F412CE017@EUSAACMS0703.eamcs.ericsson.se> <FEFE5B9D80A543B09B2A222828251D11@china.huawei.com> <13299477-5A32-4E4A-93E8-EF75EE22D69D@cisco.com> <5C6B651E4AEE4379887AC8561B68F826@china.huawei.com>
In-Reply-To: <5C6B651E4AEE4379887AC8561B68F826@china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_8249B703AE8442429AF89B86E8206AA26F41373471EUSAACMS0703e_"
MIME-Version: 1.0
Cc: "pce@ietf.org" <pce@ietf.org>
Subject: Re: [Pce] New Version Notification for draft-lu-ospf-area-tlv-01.txt
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.12
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: <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: Tue, 19 Jul 2011 21:32:47 -0000

Thanks Dhruv for the summary.
At least the authors of the two drafts have the same vision that advertising OSPF area IDs will help PCE's multi-area path computation, so that operators do not have to configure manually the list of boundary routers.
PCEers, please voice your opinions whether it's a good idea to automate the discovery of the OSPF area IDs.

If we agree that automating the ABR provisioning is a good thing, please be advised that the rationale and approaches of the two drafts are quite different.

draft-lu-ospf-area-tlv focuses on one thing, i.e. to enable CSPF to do multi-area path computation with no need of manual ABR provisioning. Here're several key points (please refer to the draft for detail):
1. An OSPF Area-ID-TLV is introduced. This TLV tells whether and how CSPF can extend its LSP computation to across area boundaries.
2. The originating point is OSPF's TE function. The TLV is kept under OSPF TE extensions (like router-address TLV and link TLV). This is to ensure that the ABR is an LSR capable of transit TE traffic. This is important because an ABR is not necessary an LSR.
3. From CSPF point-of-view, if the area-id info is readily available in TED, CSPF's job will be easy (please see use-cases 1 and 2). It doesn't need to talk to OSPF or other network components to acquire ABR information. The change to CSPF is minimal.
4. It addresses only multi-area path computation. It does not address multi-AS path computation.

draft-dhody-pce-bn-discovery-ospf is not tied with TE but kept generic (some use-cases would be helpful). It focuses on both multi-area and multi-AS. I believe the topic is also important.

Thanks,
-wenhu

________________________________
From: Dhruv Dhody [mailto:dhruvd@huawei.com]
Sent: Thursday, July 14, 2011 9:49 PM
To: 'JP Vasseur'
Cc: Wenhu Lu; pce@ietf.org
Subject: RE: [Pce] New Version Notification for draft-lu-ospf-area-tlv-01.txt

Hi,

BN Discovery draft was kept generic for the purpose of ease and extensibility.
I see further growth in this ID as the work on PCE-VPN and PCE-INTER-LAYER advances.

As a WG, we need consensus on the Motivation and Need for this kind of work.
Then we can discuss on the way we achieve this via area-tlv in OSPF-TE or a generic Boundary Node Discovery.

Regards,
Dhruv

Note: the obvious difference between the IDs
1. draft-lu focuses on ABRs with TE property for PCEs to compute LSPs.  draft-dhody focuses on the discovery of both ABRs/ASBRs.
2. draft-lu's area TLV is part of ospf TE extension. draft-dhody's (Boundary Node Discovery) BND TLV is generic.

***************************************************************************************
Dhruv Dhody, Senior Tecnical Leader, Huawei Tecnologies, Bangalore, India, Ph. +91-9845062422
This e-mail and 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: JP Vasseur [mailto:jpv@cisco.com]
Sent: Thursday, July 14, 2011 3:50 PM
To: Dhruv Dhody
Cc: 'Wenhu Lu'; pce@ietf.org
Subject: Re: [Pce] New Version Notification for draft-lu-ospf-area-tlv-01.txt

Hi Dhruv,

On Jul 14, 2011, at 6:15 AM, Dhruv Dhody wrote:



Dear Wenhu and WG,



I wanted to mention here in WG about the idea presented in IETF-78 in Maastricht.

OSPF Protocol Extensions for Boundary Node Discovery (BND)

http://datatracker.ietf.org/doc/draft-dhody-pce-bn-discovery-ospf/



During the meeting WG can evaluate if any collaboration and/or consensus be reached in this area.

Would you want to share with the WG how you see the positioning of these two ID ?

Thanks.

JP.





Thanks & Regards,

Dhruv



***************************************************************************************

Dhruv Dhody, Senior Tecnical Leader, Huawei Tecnologies, Bangalore, India, Ph. +91-9845062422



This e-mail and 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!



-----Original Message-----
From: pce-bounces@ietf.org<mailto:pce-bounces@ietf.org> [mailto:pce-bounces@ietf.org] On Behalf Of Wenhu Lu
Sent: Thursday, July 14, 2011 6:46 AM
To: pce@ietf.org<mailto:pce@ietf.org>
Subject: [Pce] New Version Notification for draft-lu-ospf-area-tlv-01.txt



Dear all,



A new version of I-D, draft-lu-ospf-area-tlv-01.txt has been successfully submitted by Wenhu Lu and posted to the IETF repository. http://tools.ietf.org/html/draft-lu-ospf-area-tlv-01



There's quite a bit of updates over the 00 version, mainly on the clarifications, motivations, and use-cases, thanks to all that provided comments and inputs.



I'll be grateful for your further review and comments before the upcoming IETF when I plan to use the PCE slot to address the concerns and issues.



Regards,

-wenhu

_______________________________________________

Pce mailing list

Pce@ietf.org<mailto:Pce@ietf.org>

https://www.ietf.org/mailman/listinfo/pce
_______________________________________________
Pce mailing list
Pce@ietf.org<mailto:Pce@ietf.org>
https://www.ietf.org/mailman/listinfo/pce