Re: [irs-discuss] Comments on Topology API use case document

"Sadler, Jonathan B." <Jonathan.Sadler@tellabs.com> Wed, 03 October 2012 12:49 UTC

Return-Path: <Jonathan.Sadler@tellabs.com>
X-Original-To: irs-discuss@ietfa.amsl.com
Delivered-To: irs-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 293DA21F8680 for <irs-discuss@ietfa.amsl.com>; Wed, 3 Oct 2012 05:49:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.589
X-Spam-Level:
X-Spam-Status: No, score=-1.589 tagged_above=-999 required=5 tests=[AWL=2.010, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 9p48UCU8T+sV for <irs-discuss@ietfa.amsl.com>; Wed, 3 Oct 2012 05:49:30 -0700 (PDT)
Received: from am1outboundpool.messaging.microsoft.com (am1ehsobe001.messaging.microsoft.com [213.199.154.204]) by ietfa.amsl.com (Postfix) with ESMTP id 7C72121F867F for <irs-discuss@ietf.org>; Wed, 3 Oct 2012 05:49:29 -0700 (PDT)
Received: from mail21-am1-R.bigfish.com (10.3.201.249) by AM1EHSOBE003.bigfish.com (10.3.204.23) with Microsoft SMTP Server id 14.1.225.23; Wed, 3 Oct 2012 12:49:27 +0000
Received: from mail21-am1 (localhost [127.0.0.1]) by mail21-am1-R.bigfish.com (Postfix) with ESMTP id 89A72240104; Wed, 3 Oct 2012 12:49:27 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:204.154.129.150; KIP:(null); UIP:(null); IPV:NLI; H:usnvwwmspedge02.tellabs-west.tellabsinc.net; RD:none; EFVD:NLI
X-SpamScore: -31
X-BigFish: VPS-31(zz98dI9371I8fcdK542M1432I604Izz1202h1d1ah1d2ahzz1033IL17326ah8275bh8275dhz2ei2a8h668h839h944hd25hf0ah107ah1220h1288h12a5h12a9h12bdh137ah13b6h1441h1155h)
Received-SPF: neutral (mail21-am1: 204.154.129.150 is neither permitted nor denied by domain of tellabs.com) client-ip=204.154.129.150; envelope-from=Jonathan.Sadler@tellabs.com; helo=usnvwwmspedge02.tellabs-west.tellabsinc.net ; llabsinc.net ;
Received: from mail21-am1 (localhost.localdomain [127.0.0.1]) by mail21-am1 (MessageSwitch) id 1349268565449221_2420; Wed, 3 Oct 2012 12:49:25 +0000 (UTC)
Received: from AM1EHSMHS013.bigfish.com (unknown [10.3.201.249]) by mail21-am1.bigfish.com (Postfix) with ESMTP id 69CF5220109; Wed, 3 Oct 2012 12:49:25 +0000 (UTC)
Received: from usnvwwmspedge02.tellabs-west.tellabsinc.net (204.154.129.150) by AM1EHSMHS013.bigfish.com (10.3.207.151) with Microsoft SMTP Server (TLS) id 14.1.225.23; Wed, 3 Oct 2012 12:49:23 +0000
Received: from usnvwwmspht01.tellabs-west.tellabsinc.net (172.23.211.69) by usnvwwmspedge02.tellabs-west.tellabsinc.net (204.154.131.191) with Microsoft SMTP Server (TLS) id 8.3.83.0; Wed, 3 Oct 2012 07:49:09 -0500
Received: from EX-NAP.tellabs-west.tellabsinc.net ([172.23.211.71]) by usnvwwmspht01.tellabs-west.tellabsinc.net ([172.23.211.69]) with mapi; Wed, 3 Oct 2012 07:49:22 -0500
From: "Sadler, Jonathan B." <Jonathan.Sadler@tellabs.com>
To: Shane Amante <shane@castlepoint.net>, Joel M.Halpern <jmh@joelhalpern.com>
Date: Wed, 3 Oct 2012 07:49:21 -0500
Thread-Topic: [irs-discuss] Comments on Topology API use case document
Thread-Index: Ac2hI4bmdhAAIg9XShKxS1diNRROpQAPWIdg
Message-ID: <5292FFA96EC22A4386067E9DBCC0CD2B01417B01B449@EX-NAP.tellabs-west.tellabsinc.net>
References: <506BA52E.2060008@joelhalpern.com> <1522D7C2-0CE1-478C-8FD9-A0ABFBFB1CDA@castlepoint.net>
In-Reply-To: <1522D7C2-0CE1-478C-8FD9-A0ABFBFB1CDA@castlepoint.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: tellabs.com
Cc: "irs-discuss@ietf.org" <irs-discuss@ietf.org>
Subject: Re: [irs-discuss] Comments on Topology API use case document
X-BeenThere: irs-discuss@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Interface to The Internet Routing System \(IRS\)" <irs-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/irs-discuss>, <mailto:irs-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/irs-discuss>
List-Post: <mailto:irs-discuss@ietf.org>
List-Help: <mailto:irs-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/irs-discuss>, <mailto:irs-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Oct 2012 12:49:31 -0000

Shane, Joel, et al -

You may be interested in modeling work that was done at ITU-T discussing multi-layer topology relationships.  The specific document to look at is G.800 (2012): Unified Functional Architecture of Transport Networks. (http://www.itu.int/rec/T-REC-G.800)

The specific component in this approach to describing networks that describes multi-layer topology relationships is the Transitional Link.  See Section 6.2.1.

There was a liaison sent from ITU-T SG 15 to CCAMP that described how this topological component can be used in multi-layer ODU networks.  Please see SG15 LS221 - Examples of the use of Transitional Links (ITU-T G.709) (https://datatracker.ietf.org/liaison/953/).

>From this, work has been started on how a transitional link can be represented in link-state routing protocols thereby providing detail of the hierarchical relationships to path computation entities.

I see strong value in including this in IRS style applications as it enables the entity interested in topology to be able to understand all of the details where the service provider wishes it to be known (i.e. subject to policy controls).

Jonathan Sadler

-----Original Message-----
From: irs-discuss-bounces@ietf.org [mailto:irs-discuss-bounces@ietf.org] On Behalf Of Shane Amante
Sent: Tuesday, October 02, 2012 11:57 PM
To: Joel M.Halpern
Cc: irs-discuss@ietf.org
Subject: Re: [irs-discuss] Comments on Topology API use case document

Hi Joel,

Thanks for your review.  Please see below.

On Oct 2, 2012, at 8:38 PM, Joel M. Halpern <jmh@joelhalpern.com> wrote:
> Overall, this looks very helpful.
>
> In the terminology section, two things struck me:
> First, we probably need to consistently qualify the term "Policy Manager".  What is described in this document as the "Policy Manager" is a very interesting and powerful function.  it is a policy function.  But it is no more the entire policy manager than a security policy manager is the entire policy manager.  It seems to me that this is a discipline we need to acquire early, or we will forever find ourselves arguing about the meaning of terms when we actually agree.  (The later description of the Policy Manager edges into the broader perspective, but isn't really the same.)

We'll look at making the text in terminology section better align with the broader definition of a Policy Manager in Section 3.3.

Indeed, a "Policy Management" function is indeed critical.  Arguably, it's in the top two most critical elements of this work, IMO.  And, you're right that we need to align on definitions for what it is for fear or forever qualifying it.  The reason we chose "Policy Manager" is that it seemed the closest match to what are (likely) considered routine functions in networking today, namely, "routing policies" (cf: BGP), "security policies" (cf: ACL preventing/allowing packets through), etc.  Is that part clear?  Note, at this stage, we're depicting this as a single "Policy Manager" function; however, if this work evolves it's likely this will get broken down into sub-components (security, routing, etc.) to more precisely define their domain-specific attributes.


> I have to disagree with the definition of Multi-Layer Topology.  I agree that topologies are layered.  However, the OSI topology abstraction is absolutely wrong.  As was pointed out to me many years ago, and has become more prevalent ever sine, w run L2 VPN services on MPLS infrastructure on IP infrastructure, which is in term supported by Ethernet, some which may actually be emulated Ethernet on MPLS on ...

Hrm.  Ultimately, what I think you're describe is a perfect example of building a specific hierarchical network.  The problem is, today, we *DO NOT* have any (standards-based) way to represent the reality of those hierarchical relationships /outside of/ the data-plane and control-plane[1].  Over the years, we've clearly engineered such hierarchy directly into the routing (and, forwarding) planes of network equipment.  In addition, we've barely enumerated some attributes of *individual* protocols or network components, (cf: SNMP MIB's), but they are entirely /standalone/.  Instead, we need to take the next step.  Specifically, we need to fully enumerate attributes and, more importantly, metadata of individual control & data-plane protocols (and, related network components) using a common, standards-based *vocabulary*.  Only once we do that will it be possible to:
a) Define hierarchical relationships between network components (protocols, services, etc.), using the aforementioned attributes/metadata as filtering/selection criteria, as appropriate; and,
b) Summarize all of this vocabulary into schemas/data-models that can then be exchanged between systems that *DO NOT* (cannot *and* will not) directly participate in routing & forwarding.
Ultimately, this is the core essence of SDN/IRS.

[1] BGP recursing to an IGP for next-hop; LDP relying on IGP to determine shortest-path, etc.


> While I appreciate the importance of the Inventory function in evaluating SRLGs, I think the document should probably point out that this often depends upon physical realities not visible to any automated system.  (The number of stories of operators failing to meet diversity guarantees are legion.)

Really!?!?  ;-)

More seriously, I thought this was made clear in the first two paragraphs of Section 4.1.1, "Capacity Planning and Traffic Engineering":
---snip---
   [...] Due to this inefficiency, the
   underlying physical network inventory information, (containing SRLG
   and corresponding critical network asset information), used by the
   IP/MPLS Capacity Planning and TE applications is not updated
   frequently, thus exposing the network to, at minimum, inefficient
   utilization and, at worst, critical impairments.
---snip---


> I find it strange that this draft describes change application using a different paradigm than the other IRS drafts.  Is this deliberate, indicating that these use cases need a different mechanism than is elsewhere described?  (I wold have simply indicated that the Topology manager will need to apply changes, and left it there as far as this document is concerned.

I'm not sure I understand the above comment.  Can you elaborate?

-shane
_______________________________________________
irs-discuss mailing list
irs-discuss@ietf.org
https://www.ietf.org/mailman/listinfo/irs-discuss


============================================================
The information contained in this message may be privileged
and confidential and protected from disclosure. If the reader
of this message is not the intended recipient, or an employee
or agent responsible for delivering this message to the
intended recipient, you are hereby notified that any reproduction,
dissemination or distribution of this communication is strictly
prohibited. If you have received this communication in error,
please notify us immediately by replying to the message and
deleting it from your computer. Thank you. Tellabs
============================================================