Return-Path: 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 4E9DC21F86EA for ; Mon, 12 Nov 2012 09:21:31 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.466 X-Spam-Level: X-Spam-Status: No, score=-3.466 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, UNRESOLVED_TEMPLATE=3.132] 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 YeNF9QRKxSv4 for ; Mon, 12 Nov 2012 09:21:29 -0800 (PST) Received: from exprod7og110.obsmtp.com (exprod7og110.obsmtp.com [64.18.2.173]) by ietfa.amsl.com (Postfix) with ESMTP id B0A0221F86EB for ; Mon, 12 Nov 2012 09:21:26 -0800 (PST) Received: from P-EMHUB02-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob110.postini.com ([64.18.6.12]) with SMTP ID DSNKUKEwFcd91xBwAYvvK1ycabIqUHVBwAB2@postini.com; Mon, 12 Nov 2012 09:21:26 PST Received: from P-CLDFE01-HQ.jnpr.net (172.24.192.59) by P-EMHUB02-HQ.jnpr.net (172.24.192.36) with Microsoft SMTP Server (TLS) id 8.3.213.0; Mon, 12 Nov 2012 09:21:04 -0800 Received: from o365mail.juniper.net (207.17.137.224) by o365mail.juniper.net (172.24.192.59) with Microsoft SMTP Server id 14.1.355.2; Mon, 12 Nov 2012 09:21:03 -0800 Received: from ch1outboundpool.messaging.microsoft.com (216.32.181.183) by o365mail.juniper.net (207.17.137.224) with Microsoft SMTP Server (TLS) id 14.1.355.2; Mon, 12 Nov 2012 09:27:59 -0800 Received: from mail99-ch1-R.bigfish.com (10.43.68.225) by CH1EHSOBE014.bigfish.com (10.43.70.64) with Microsoft SMTP Server id 14.1.225.23; Mon, 12 Nov 2012 17:21:00 +0000 Received: from mail99-ch1 (localhost [127.0.0.1]) by mail99-ch1-R.bigfish.com (Postfix) with ESMTP id 41827360200 for ; Mon, 12 Nov 2012 17:21:00 +0000 (UTC) X-Forefront-Antispam-Report: CIP:157.56.232.213; KIP:(null); UIP:(null); (null); H:BLUPRD0511HT001.namprd05.prod.outlook.com; R:internal; EFV:INT X-SpamScore: -26 X-BigFish: PS-26(zzbb2dI98dI9371Ic85eh542M1432I4015Izz1de0h1202h1d1ah1d2ahzz8275ch1033IL17326ah8275bh8275dhz2dh2a8h668h839hd25hf0ah1288h12a5h12bdh137ah1441h1504h1537h153bh15d0l1155h) Received: from mail99-ch1 (localhost.localdomain [127.0.0.1]) by mail99-ch1 (MessageSwitch) id 1352740858837647_12896; Mon, 12 Nov 2012 17:20:58 +0000 (UTC) Received: from CH1EHSMHS025.bigfish.com (snatpool1.int.messaging.microsoft.com [10.43.68.248]) by mail99-ch1.bigfish.com (Postfix) with ESMTP id C9D76340180; Mon, 12 Nov 2012 17:20:58 +0000 (UTC) Received: from BLUPRD0511HT001.namprd05.prod.outlook.com (157.56.232.213) by CH1EHSMHS025.bigfish.com (10.43.70.25) with Microsoft SMTP Server (TLS) id 14.1.225.23; Mon, 12 Nov 2012 17:20:56 +0000 Received: from BLUPRD0511MB436.namprd05.prod.outlook.com ([169.254.4.84]) by BLUPRD0511HT001.namprd05.prod.outlook.com ([10.255.135.164]) with mapi id 14.16.0233.002; Mon, 12 Nov 2012 17:20:51 +0000 From: Geoffrey Mattson To: Alia Atlas , Ross Callon Thread-Topic: [irs-discuss] What's in a name? Thread-Index: Ac3A5PsIVqU8XiJmRGOy8kKrHtrEtQAAkBWdAAFO/IAAANLaAAAAcbLQAAHPbYD//31PAA== Date: Mon, 12 Nov 2012 17:20:51 +0000 Message-ID: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.2.3.120616 x-originating-ip: [10.255.135.132] Content-Type: multipart/alternative; boundary="_000_BDBDE06394B5D448AC51F6A965506BE807984EBLUPRD0511MB436na_" MIME-Version: 1.0 X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn% X-FOPE-CONNECTOR: Id%12219$Dn%GMAIL.COM$RO%2$TLS%5$FQDN%onpremiseedge-1018244.customer.frontbridge.com$TlsDn%o365mail.juniper.net X-FOPE-CONNECTOR: Id%12219$Dn%HUAWEI.COM$RO%2$TLS%5$FQDN%onpremiseedge-1018244.customer.frontbridge.com$TlsDn%o365mail.juniper.net X-FOPE-CONNECTOR: Id%12219$Dn%IETF.ORG$RO%2$TLS%5$FQDN%onpremiseedge-1018244.customer.frontbridge.com$TlsDn%o365mail.juniper.net Cc: Lucy yong , "irs-discuss@ietf.org" Subject: Re: [irs-discuss] What's in a name? X-BeenThere: irs-discuss@ietf.org 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: Mon, 12 Nov 2012 17:21:31 -0000 --_000_BDBDE06394B5D448AC51F6A965506BE807984EBLUPRD0511MB436na_ Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable I'd like to suggest: Programmatic Interface to Routing System or PIRS. There are other interfaces to the routing system but IRS is programmatic. S= o=85 From: Alia Atlas > Date: Monday, November 12, 2012 9:11 AM To: Ross Callon > Cc: Lucy yong >, "irs-dis= cuss@ietf.org" > Subject: Re: [irs-discuss] What's in a name? IRS, I2RS or ITRS all sound fine to me. Alia On Mon, Nov 12, 2012 at 11:21 AM, Ross Callon > wrote: I am fine with any of: ITRS, I2RS, or RSI. Any of them are similar enough t= o IRS to help us make the connection, without being confused or reminding m= e of something else. Ross -----Original Message----- From: irs-discuss-bounces@ietf.org [ma= ilto:irs-discuss-bounces@ietf.org] On = Behalf Of Lucy yong Sent: Monday, November 12, 2012 11:07 AM To: stbryant@cisco.com; Raveendra Torvi Cc: >; irs-discuss@ietf.org= Subject: Re: [irs-discuss] What's in a name? I like this name: I2RS. Lucy > -----Original Message----- > From: irs-discuss-bounces@ietf.org [= mailto:irs-discuss-bounces@ietf.org] > On Behalf Of Stewart Bryant > Sent: Monday, November 12, 2012 9:44 AM > To: Raveendra Torvi > Cc: >; irs-discuss@ietf.o= rg > Subject: Re: [irs-discuss] What's in a name? > > On 12/11/2012 15:06, Raveendra Torvi wrote: > > My first set of suggestions: > > > > I2RS- interface 2 routing system. > That as well > > Stewart > > > > > IRNE - interface to routing network element. > > IRE - interface to routing element > > INE - interface to network element. > > APIRS - API to RS. > > APIRE > > > > Ravi > > On Nov 12, 2012, at 9:56 AM, "Adrian Farrel" > > wrote: > > > >> Personally, I find discussions of what name/acronym to use a bit sad. > I've had > >> enough code review hours wasted debating the names of variables to > not want to > >> spend any more time on this sort of thing. > >> > >> However, I note that there was some unease about the use of IRS. If > we really > >> need to find a new name for this work (and I note that RSI is also > used for > >> something else) we need to find a solution soon. > >> > >> Can I suggest that only those people who have a strong objection to > IRS need to > >> contribute to the discussion. Furthermore, we don't need suggestions > to be > >> floated, we need solid and definite proposals. That way we will > possibly reach a > >> serious conclusion quickly. > >> > >> Thanks, > >> Adrian > >> > >> _______________________________________________ > >> irs-discuss mailing list > >> irs-discuss@ietf.org > >> https://www.ietf.org/mailman/listinfo/irs-discuss > >> > > _______________________________________________ > > irs-discuss mailing list > > irs-discuss@ietf.org > > https://www.ietf.org/mailman/listinfo/irs-discuss > > > > > -- > For corporate legal information go to: > > http://www.cisco.com/web/about/doing_business/legal/cri/index.html > > _______________________________________________ > irs-discuss mailing list > irs-discuss@ietf.org > https://www.ietf.org/mailman/listinfo/irs-discuss _______________________________________________ irs-discuss mailing list irs-discuss@ietf.org https://www.ietf.org/mailman/listinfo/irs-discuss _______________________________________________ irs-discuss mailing list irs-discuss@ietf.org https://www.ietf.org/mailman/listinfo/irs-discuss --_000_BDBDE06394B5D448AC51F6A965506BE807984EBLUPRD0511MB436na_ Content-Type: text/html; charset="Windows-1252" Content-ID: Content-Transfer-Encoding: quoted-printable
I'd like to suggest:
Programmatic Interface to Routing System or PIRS.

There are other interfaces to the routing system but IRS is programmat= ic. So=85

From: Alia Atlas <akatlas@gmail.com>
Date: Monday, November 12, 2012 9:1= 1 AM
To: Ross Callon <rcallon@juniper.net>
Cc: Lucy yong <lucy.yong@huawei.com>, "irs-discuss@ietf.org" <irs-discuss@ietf.org>
Subject: Re: [irs-discuss] What's i= n a name?

IRS, I2RS or ITRS all sound fine to me.

Alia


On Mon, Nov 12, 2012 at 11:21 AM, Ross Callon <rcallon@junipe= r.net> wrote:
I am fine with any of: ITRS, I2RS, or RSI. Any of them are similar enough t= o IRS to help us make the connection, without being confused or reminding m= e of something else.

Ross

-----Original Message-----
From: irs-discuss-bounces@i= etf.org [mailto:irs-dis= cuss-bounces@ietf.org] On Behalf Of Lucy yong
Sent: Monday, November 12, 2012 11:07 AM
To: stbryant@cisco.com; Raveendra= Torvi
Cc: <adrian@olddog.co.uk>;= irs-discuss@ietf.org
Subject: Re: [irs-discuss] What's in a name?

I like this name: I2RS.
Lucy

> -----Original Message-----
> From: irs-discuss-boun= ces@ietf.org [mailto:ir= s-discuss-bounces@ietf.org]
> On Behalf Of Stewart Bryant
> Sent: Monday, November 12, 2012 9:44 AM
> To: Raveendra Torvi
> Cc: <adrian@olddog.co.uk= >; irs-discuss@ietf.org
> Subject: Re: [irs-discuss] What's in a name?
>
> On 12/11/2012 15:06, Raveendra Torvi wrote:
> > My first set of suggestions:
> >
> > I2RS- interface 2 routing system.
> That as well
>
> Stewart
>
> >
> > IRNE - interface to routing network element.
> > IRE - interface to routing element
> > INE - interface to network element.
> > APIRS - API to RS.
> > APIRE
> >
> > Ravi
> > On Nov 12, 2012, at 9:56 AM, "Adrian Farrel" <adrian@olddog.co.uk>
> wrote:
> >
> >> Personally, I find discussions of what name/acronym to use a = bit sad.
> I've had
> >> enough code review hours wasted debating the names of variabl= es to
> not want to
> >> spend any more time on this sort of thing.
> >>
> >> However, I note that there was some unease about the use of I= RS. If
> we really
> >> need to find a new name for this work (and I note that RSI is= also
> used for
> >> something else) we need to find a solution soon.
> >>
> >> Can I suggest that only those people who have a strong object= ion to
> IRS need to
> >> contribute to the discussion. Furthermore, we don't need sugg= estions
> to be
> >> floated, we need solid and definite proposals. That way we wi= ll
> possibly reach a
> >> serious conclusion quickly.
> >>
> >> Thanks,
> >> Adrian
> >>
> >> _______________________________________________
> >> irs-discuss mailing list
> >> irs-discuss@ietf.org<= /a>
> >> https://www.ietf.org/mailman/listinfo/irs-discuss
> >>
> > _______________________________________________
> > irs-discuss mailing list
> > irs-discuss@ietf.org<= br> > > https://www.ietf.org/mailman/listinfo/irs-discuss
> >
>
>
> --
> For corporate legal information go to:
>
> http://www.cisco.com/web/about/doing_business/legal/cri/index.html
>
> _______________________________________________
> irs-discuss mailing list
> irs-discuss@ietf.org
> https://www.ietf.org/mailman/listinfo/irs-discuss
_______________________________________________
irs-discuss mailing list
irs-discuss@ietf.org
https://www.ietf.org/mailman/listinfo/irs-discuss


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

 --_000_BDBDE06394B5D448AC51F6A965506BE807984EBLUPRD0511MB436na_--