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

Susan Hares <> Tue, 31 July 2012 01:18 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id DC47711E80DE for <>; Mon, 30 Jul 2012 18:18:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.398
X-Spam-Status: No, score=-2.398 tagged_above=-999 required=5 tests=[AWL=4.201, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id hez-WyZwVKBw for <>; Mon, 30 Jul 2012 18:18:25 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id 3ADFC11E80DB for <>; Mon, 30 Jul 2012 18:18:25 -0700 (PDT)
Received: from (EHLO ([]) by (MOS 4.2.3-GA FastPath) with ESMTP id AIM23359; Mon, 30 Jul 2012 21:18:25 -0400 (EDT)
Received: from ( by ( with Microsoft SMTP Server (TLS) id 14.1.323.3; Mon, 30 Jul 2012 18:16:18 -0700
Received: from ([]) by ([]) with mapi id 14.01.0323.003; Mon, 30 Jul 2012 18:16:15 -0700
From: Susan Hares <>
To: "Joel M. Halpern" <>, "" <>
Thread-Topic: [irs-discuss] I-D Action: draft-ward-irs-framework-00.txt
Thread-Index: AQHNbqDE0RghEMqjhk+pxE1DLzQQ1JdClGzA
Date: Tue, 31 Jul 2012 01:16:14 +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
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: Tue, 31 Jul 2012 01:18:26 -0000

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.

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

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

Is this just the -00.draft? 


-----Original Message-----
From: [] On Behalf Of Joel M. Halpern
Sent: Monday, July 30, 2012 3:15 PM
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.


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