IETF Logo Mail Archive

Re: [irs-discuss] What's in a name?

Ross Callon <rcallon@juniper.net> Mon, 12 November 2012 15:33 UTC

Return-Path: <rcallon@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 E493221F85C4 for <irs-discuss@ietfa.amsl.com>; Mon, 12 Nov 2012 07:33:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.391
X-Spam-Level:
X-Spam-Status: No, score=-103.391 tagged_above=-999 required=5 tests=[AWL=0.076, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, UNRESOLVED_TEMPLATE=3.132, USER_IN_WHITELIST=-100]
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 YAcjHH0bV7VD for <irs-discuss@ietfa.amsl.com>; Mon, 12 Nov 2012 07:33:40 -0800 (PST)
Received: from exprod7og104.obsmtp.com (exprod7og104.obsmtp.com [64.18.2.161]) by ietfa.amsl.com (Postfix) with ESMTP id 60D0321F85AC for <irs-discuss@ietf.org>; Mon, 12 Nov 2012 07:33:40 -0800 (PST)
Received: from P-EMHUB03-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob104.postini.com ([64.18.6.12]) with SMTP ID DSNKUKEW0xAPCr3sjBwePN9a5IcZXRyEKniv@postini.com; Mon, 12 Nov 2012 07:33:40 PST
Received: from P-CLDFE02-HQ.jnpr.net (172.24.192.60) by P-EMHUB03-HQ.jnpr.net (172.24.192.37) with Microsoft SMTP Server (TLS) id 8.3.213.0; Mon, 12 Nov 2012 07:30:19 -0800
Received: from o365mail.juniper.net (207.17.137.224) by o365mail.juniper.net (172.24.192.60) with Microsoft SMTP Server id 14.1.355.2; Mon, 12 Nov 2012 07:30:19 -0800
Received: from co1outboundpool.messaging.microsoft.com (216.32.180.184) by o365mail.juniper.net (207.17.137.224) with Microsoft SMTP Server (TLS) id 14.1.355.2; Mon, 12 Nov 2012 07:37:15 -0800
Received: from mail127-co1-R.bigfish.com (10.243.78.248) by CO1EHSOBE006.bigfish.com (10.243.66.69) with Microsoft SMTP Server id 14.1.225.23; Mon, 12 Nov 2012 15:30:16 +0000
Received: from mail127-co1 (localhost [127.0.0.1]) by mail127-co1-R.bigfish.com (Postfix) with ESMTP id 2E4C9A800E4 for <irs-discuss@ietf.org.FOPE.CONNECTOR.OVERRIDE>; Mon, 12 Nov 2012 15:30:16 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.244.213; KIP:(null); UIP:(null); (null); H:CH1PRD0510HT004.namprd05.prod.outlook.com; R:internal; EFV:INT
X-SpamScore: -23
X-BigFish: PS-23(zz9371I542M4015Izz1de0h1202h1d1ah1d2ahzz1033IL8275dhz2dh2a8h668h839h944hd25hf0ah1220h1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh15d0l1155h)
Received: from mail127-co1 (localhost.localdomain [127.0.0.1]) by mail127-co1 (MessageSwitch) id 1352734214788863_9932; Mon, 12 Nov 2012 15:30:14 +0000 (UTC)
Received: from CO1EHSMHS029.bigfish.com (unknown [10.243.78.234]) by mail127-co1.bigfish.com (Postfix) with ESMTP id B499F98004A; Mon, 12 Nov 2012 15:30:14 +0000 (UTC)
Received: from CH1PRD0510HT004.namprd05.prod.outlook.com (157.56.244.213) by CO1EHSMHS029.bigfish.com (10.243.66.39) with Microsoft SMTP Server (TLS) id 14.1.225.23; Mon, 12 Nov 2012 15:30:11 +0000
Received: from CH1PRD0510MB355.namprd05.prod.outlook.com ([169.254.2.125]) by CH1PRD0510HT004.namprd05.prod.outlook.com ([10.255.150.39]) with mapi id 14.16.0233.002; Mon, 12 Nov 2012 15:30:10 +0000
From: Ross Callon <rcallon@juniper.net>
To: "adrian@olddog.co.uk" <adrian@olddog.co.uk>, "irs-discuss@ietf.org" <irs-discuss@ietf.org>
Thread-Topic: [irs-discuss] What's in a name?
Thread-Index: Ac3A5PsIVqU8XiJmRGOy8kKrHtrEtQABNjBQ
Date: Mon, 12 Nov 2012 15:30:09 +0000
Message-ID: <62CCD4C52ACDAD4481149BD5D8A72FD302525590@CH1PRD0510MB355.namprd05.prod.outlook.com>
References: <015701cdc0e4$fbc439f0$f34cadd0$@olddog.co.uk>
In-Reply-To: <015701cdc0e4$fbc439f0$f34cadd0$@olddog.co.uk>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [66.129.232.2]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn%
X-FOPE-CONNECTOR: Id%12219$Dn%OLDDOG.CO.UK$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
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\)" <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: Mon, 12 Nov 2012 15:33:42 -0000

I don't like the "IRS" acronym due to the similarity to the US tax folks. 

RSI seems like a sensible acronym to me, and similar enough that people can make the connection. I am not sure what else RSI stands for, but Googling it right now I didn't see anything that would either confuse us, sue us, or audit our taxes (repetitive strain injury being the most obvious use of it -- I am assuming that Radio Slovakia won't notice if we use the acronym for something else). 

Ross

-----Original Message-----
From: irs-discuss-bounces@ietf.org [mailto:irs-discuss-bounces@ietf.org] On Behalf Of Adrian Farrel
Sent: Monday, November 12, 2012 9:50 AM
To: irs-discuss@ietf.org
Subject: [irs-discuss] What's in a name?

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

v2.23.0 | Report a Bug | By Email