Re: [irs-discuss] IRS comments

Thomas Nadeau <tnadeau@juniper.net> Tue, 31 July 2012 00:53 UTC

Return-Path: <tnadeau@juniper.net>
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 17A2121F8539 for <irs-discuss@ietfa.amsl.com>; Mon, 30 Jul 2012 17:53:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.381
X-Spam-Level:
X-Spam-Status: No, score=-6.381 tagged_above=-999 required=5 tests=[AWL=0.218, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HXbTNQJqftBN for <irs-discuss@ietfa.amsl.com>; Mon, 30 Jul 2012 17:53:03 -0700 (PDT)
Received: from exprod7og104.obsmtp.com (exprod7og104.obsmtp.com [64.18.2.161]) by ietfa.amsl.com (Postfix) with ESMTP id EE1C721F8530 for <irs-discuss@ietf.org>; Mon, 30 Jul 2012 17:53:01 -0700 (PDT)
Received: from P-EMHUB01-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob104.postini.com ([64.18.6.12]) with SMTP ID DSNKUBcsbVVGogjZrFSwkmr9HqMAh9KsiTks@postini.com; Mon, 30 Jul 2012 17:53:01 PDT
Received: from p-emfe02-wf.jnpr.net (172.28.145.25) by P-EMHUB01-HQ.jnpr.net (172.24.192.35) with Microsoft SMTP Server (TLS) id 8.3.213.0; Mon, 30 Jul 2012 17:50:43 -0700
Received: from EMBX01-WF.jnpr.net ([fe80::1914:3299:33d9:e43b]) by p-emfe02-wf.jnpr.net ([fe80::c126:c633:d2dc:8090%11]) with mapi; Mon, 30 Jul 2012 20:50:42 -0400
From: Thomas Nadeau <tnadeau@juniper.net>
To: Lenny Giuliano <lenny@juniper.net>, Alia Atlas <akatlas@juniper.net>
Date: Mon, 30 Jul 2012 20:50:40 -0400
Thread-Topic: IRS comments
Thread-Index: Ac1utoJXMLn1Fv5cTmO9ZkEBmEbA7g==
Message-ID: <CC3C79C1.2996%tnadeau@juniper.net>
In-Reply-To: <20120730164422.U88614@eng-mail01.juniper.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.2.3.120616
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "irs-discuss@ietf.org" <irs-discuss@ietf.org>
Subject: Re: [irs-discuss] IRS comments
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: Tue, 31 Jul 2012 00:53:04 -0000

[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" <lenny@juniper.net> 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).
>Maybe 
>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
>I 
>was reading thru.  Also, I did wonder what was new and novel here, as
>this 
>sounded like our SDK which has been around for years.
>
>
>-Lenny