Re: [irs-discuss] I-D Action: draft-ward-irs-framework-00.txt

Susan Hares <> Wed, 01 August 2012 18:00 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 8C4B221F8818 for <>; Wed, 1 Aug 2012 11:00:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -3.516
X-Spam-Status: No, score=-3.516 tagged_above=-999 required=5 tests=[AWL=3.083, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id U0zKZrwGChKO for <>; Wed, 1 Aug 2012 11:00:32 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id 4364B11E8318 for <>; Wed, 1 Aug 2012 11:00:32 -0700 (PDT)
Received: from (EHLO ([]) by (MOS 4.2.3-GA FastPath) with ESMTP id AIP41066; Wed, 01 Aug 2012 10:00:32 -0800 (PST)
Received: from ( by ( with Microsoft SMTP Server (TLS) id 14.1.323.3; Wed, 1 Aug 2012 10:58:13 -0700
Received: from ([]) by ([]) with mapi id 14.01.0323.003; Wed, 1 Aug 2012 10:58:09 -0700
From: Susan Hares <>
To: Alia Atlas <>
Thread-Topic: [irs-discuss] I-D Action: draft-ward-irs-framework-00.txt
Thread-Index: AQHNbqDE0RghEMqjhk+pxE1DLzQQ1JdClGzAgAB8jgCAAh3/0A==
Date: Wed, 1 Aug 2012 17:58:09 +0000
Message-ID: <>
References: <> <> <> <>
In-Reply-To: <>
Accept-Language: en-US, zh-CN
Content-Language: en-US
x-originating-ip: []
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Cc: "Joel M. Halpern" <>, "" <>
Subject: Re: [irs-discuss] I-D Action: draft-ward-irs-framework-00.txt
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Interface to The Internet Routing System \(IRS\)" <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 01 Aug 2012 18:00:34 -0000


The hierarchical of interfaces (To routing system) is one of the areas that requires prioritization. The prioritization must be able to handle "preempt me", "after you", and "after me".  

It is also key to understand that irs system must handle multi-interfaces struggles at the lowest layer.  You need to look at the MIF WG (+/-) for some of the struggles of mobility. 

-----Original Message-----
From: Alia Atlas [] 
Sent: Monday, July 30, 2012 6:33 PM
To: Susan Hares
Cc: Joel M. Halpern;
Subject: Re: [irs-discuss] I-D Action: draft-ward-irs-framework-00.txt

Hi Sue,

On Mon, Jul 30, 2012 at 9:16 PM, Susan Hares <>; wrote:
> Joel and irs-folks:
> +1 on Joel.
>  Beyond your comments, the requirement prioritization of the interworking of these interfaces is not clearly delineated in this work. This type of prioritization and sequencing is key to multi-interfaces operation on the monitoring, configuration or insertion of information into the depth.

[Alia] Can you further clarify, maybe with an example, which aspect
you are thinking of?   Do you mean the ability of an application to
access multiple sub-interfaces?  The interaction of operations
requested by differerent applications?

> In addition, if you are going to do configuration with roll-forward/roll-back - you need a transaction based processing.

[Alia] I'm pretty sure that I avoided the word "transaction" in both
drafts.  That was deliberate.  Of course, we can have a discussion
about whether or not some form of transactions might be desirable.  I
am concerned about their potentially heavy-weight nature.

> Therefore, you've skipped even requiring the hard problems.

[Alia] Can I optimistically pretend that means that the requirements
we do have don't seem too hard?  For the responsiveness and throughput
goals, I've put a stake in the ground to avoid transaction-based
semantics.  Naturally, the hordes can run over that stake, if

[Sue]: The requirements are necessary even if they are hard.  

[Alia] For the interaction between different layers of sub-interfaces,
I've been assuming that we'll define the interactions between the
layers based on how they are generally done.  For instance, perhaps we
standardize the idea of preference value - and then the RIB can pick
the best route based upon those preferences.  For interaction between
different applications, I think there's a mixture of
authorization/authentication to get right plus a good set of events
that an application could register for.

[Sue]: As someone who has lived with "local pref" in BGP for a long time, there is a bit more to unwrap in the statement.  However, it breaks down to prioritization that is pre-set by preferences.

The policy issues behind the local-pref setting have been studied by the BGP policy community. This is substantial good work on this from the academic researchers, vendors, and operator. Griffins, Rexford, Bush, Feamster, ..... and lots others are much better on the theory than I am.  

> Is this just the -00.draft?

[Alia] Certainly, I expect that we'll uncover more requirements as we
go along.  As I said, some of this is initially setting parts  out of

---> Scope == good.  Setting scope allows us to pick a piece of this work and standardize it for interoperability.


> Sue
> -----Original Message-----
> From: [] On Behalf Of Joel M. Halpern
> Sent: Monday, July 30, 2012 3:15 PM
> To:
> Subject: Re: [irs-discuss] I-D Action: draft-ward-irs-framework-00.txt
> I am finding this document quite confusing.
> The primary confusion is that the document first says that it is about
> information that can not be manipulated with existing systems, and then
> proceeds to give a list of use cases all of which can be manipulated
> with existing systems at a suitable degree of abstraction.
> As a lesser confusion, the document says that "streaming" is important,
> but then describes "streaming" as "fast, interactive access."  That is
> not streaming.  And depending upon what one means by interactive, plenty
> of systems provide "fest, interactive access."  I realize the document
> later goes on tot talk about speed and frequency of state updates.   But
> that section simply reasserts the earlier terms withotu better
> description or justification.
> Yours,
> Joel
> On 7/30/2012 2:08 PM, wrote:
>> A New Internet-Draft is available from the on-line Internet-Drafts directories.
>>       Title           : Interface to the Routing System Framework
>>       Author(s)       : Alia Atlas
>>                            Thomas Nadeau
>>                            Dave Ward
>>       Filename        : draft-ward-irs-framework-00.txt
>>       Pages           : 21
>>       Date            : 2012-07-30
>> Abstract:
>>     This document describes a framework for a standard, programmatic
>>     interface for full-duplex, streaming state transfer in and out of the
>>     Internet's routing system.  It lists the information that might be
>>     exchanged over the interface, and describes the uses of an interface
>>     to the Internet routing system.
> _______________________________________________
> irs-discuss mailing list
> _______________________________________________
> irs-discuss mailing list