Re: [irs-discuss] IRS comments

Lin Han <> Wed, 08 August 2012 23:58 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 2B9B611E80F5 for <>; Wed, 8 Aug 2012 16:58:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id do53a-qAXt62 for <>; Wed, 8 Aug 2012 16:58:25 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id 3205411E809B for <>; Wed, 8 Aug 2012 16:58:25 -0700 (PDT)
Received: from (EHLO ([]) by (MOS 4.3.5-GA FastPath) with ESMTP id AJB12620; Wed, 08 Aug 2012 15:58:24 -0800 (PST)
Received: from ( by ( with Microsoft SMTP Server (TLS) id 14.1.323.3; Wed, 8 Aug 2012 16:56:16 -0700
Received: from ([]) by ([]) with mapi id 14.01.0323.003; Wed, 8 Aug 2012 16:56:10 -0700
From: Lin Han <>
To: Thomas Nadeau <>, Gert Grammel <>, Lenny Giuliano <>, Alia Atlas <>
Thread-Topic: IRS comments
Thread-Index: Ac1utoJXMLn1Fv5cTmO9ZkEBmEbA7gABwUJeAb9NQrAADyLEAAAOKtSw
Date: Wed, 8 Aug 2012 23:56:10 +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: "" <>
Subject: Re: [irs-discuss] IRS comments
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, 08 Aug 2012 23:58:26 -0000

Hi, Tom,

I got the slide after digging tons of threads.
I agree that we should have a tech talk about what is the difference of IRS and SDN/OF. This will make the frame work more convincing.
For example, after looking at the picture of Alias slide page 5, It cannot stop me to think that IRS protocol does similar things as north bound API, or OF, depending on what is the format of table we are going to use.
This frame work gave me a impression that we assume that we don't want to simplify router architecture (for example, keep routing protocol running on router; IRS is just an extra new component), then what we can provide the same thing (programming-ability) like SDN. Is this the best solution?

-----Original Message-----
From: Thomas Nadeau [] 
Sent: Wednesday, August 08, 2012 4:22 PM
To: Lin Han; Gert Grammel; Lenny Giuliano; Alia Atlas
Subject: Re: IRS comments

On 8/8/12 7:14 PM, "Lin Han" <> wrote:

>Similar confusion by wisely avoidance -:)
>If possible, Someone can draw a simple picture of IRS location in a
>router with existence of other components.

	Did you see the slides that Alia sent out from the IETF Presentation?
Unicast me if not and I will get them to you.

>Also, I think people are confused by the comparison with SDN and OF. More
>clarification will be helpful.

	For that, we really should set up some internal tech talk thing. Slides
can help, but having a decent presentation on this would go a long way.
Let me see what we can do in this regard.


>-----Original Message-----
>From: []
>On Behalf Of Gert Grammel
>Sent: Monday, July 30, 2012 6:41 PM
>To: Thomas Nadeau; Lenny Giuliano; Alia Atlas
>Subject: Re: [irs-discuss] IRS comments
>It is confusing to understand whether IRS belongs to a new network
>management plane or if it's more of a control plane extension. The draft
>wisely avoids this classification.
>To me IRS appears to be a completely different beast which should best be
> characterized as 'Network Programming Plane' NPP.
>It neither aims to do full provisioning (as a management plane would do)
>nor aims to replace routing (as a control plane would do).
>Hence we better name the baby NPP -- thereby avoiding any linkage to
>----- Original Message -----
>From: <>
>To: Lenny Giuliano; Alia Atlas
>Cc: <>
>Sent: Tue Jul 31 01:50:40 2012
>Subject: Re: [irs-discuss] IRS comments
>[Re-adding IRS]
>	Thank you for reviewing and the comments. We will incorporate the edits
>in the next rev.
>	--Tom
>On 7/30/12 5:04 PM, "Lenny Giuliano" <> wrote:
>>Minor points:
>>-section 4, para 2, 3rd sentence, "Howeve,r"
>>-4.1.3 "There is no bidirectional programmatic interface to add, modify,
>>    remove or read state from the multicast RIB."
>> 	-How is this unique to mcast?  Couldn't you say the same thing
>> 	about unicast?
>>-4.1.3 "The multicast state added need not match to well-known protocol
>>    installed state.  For instance, traffic received on an specified set,
>>    or all, interfaces that is destined to a particular prefix from all
>>    sources or a particular prefix could be subject to the specified
>>    replication."
>> 	-Not clear to me at all what this para is saying.
>>-"IRS"- you may want to select a different acronym that isn't related to
>>something as unpopular as taxation (something we learned with AMT).
>>RSI instead...
>>Overall, I found the doc to be clearly written and straightforward.
>>Sounds like Openflow for routers.  Not sure if it's intentional that you
>>didn't mention Openflow, but it did seem like an elephant in the room as
>>was reading thru.  Also, I did wonder what was new and novel here, as
>>sounded like our SDK which has been around for years.
>irs-discuss mailing list
>irs-discuss mailing list