IETF Logo Mail Archive

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

"Palani Chinnakannan (pals)" <pals@cisco.com> Mon, 12 November 2012 20:17 UTC

Return-Path: <pals@cisco.com>
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 AAAE921F85BB for <irs-discuss@ietfa.amsl.com>; Mon, 12 Nov 2012 12:17:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.598
X-Spam-Level:
X-Spam-Status: No, score=-10.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
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 zv1mPyuI8Z5u for <irs-discuss@ietfa.amsl.com>; Mon, 12 Nov 2012 12:17:08 -0800 (PST)
Received: from rcdn-iport-5.cisco.com (rcdn-iport-5.cisco.com [173.37.86.76]) by ietfa.amsl.com (Postfix) with ESMTP id 83E4921F85AF for <irs-discuss@ietf.org>; Mon, 12 Nov 2012 12:17:08 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=11693; q=dns/txt; s=iport; t=1352751428; x=1353961028; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=5AMB9ewp0Fv+Th0AesZt04K+888Npln5dYmgcJJfUx0=; b=EdsWreJzkWDQhJasrZx9n2d1+zs257pOLxJQkWua2Rhih8q7CZzNTWSI u5vXe3D+LzNhaGUJvjZEq1gy1V1hWwyncQTEc1R8KqwG30NZZv8atj1HU UUE7V4rY7A8NBBr9a8z77H+anLJa82EV/4NjpPBx5GHoBu+X2cqi2QMAR Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgAFAC5YoVCtJXHA/2dsb2JhbABEgknBGIEIgh4BAQEEAQEBDwEaQQsQAgEIEQQBAQsdBycLFAkIAgQOBQgTB4dnAQuZXaAEBIwVhWlhA6RUgWuCb4IZ
X-IronPort-AV: E=McAfee;i="5400,1158,6894"; a="141419568"
Received: from rcdn-core2-5.cisco.com ([173.37.113.192]) by rcdn-iport-5.cisco.com with ESMTP; 12 Nov 2012 20:17:07 +0000
Received: from xhc-aln-x10.cisco.com (xhc-aln-x10.cisco.com [173.36.12.84]) by rcdn-core2-5.cisco.com (8.14.5/8.14.5) with ESMTP id qACKH7q3021518 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 12 Nov 2012 20:17:07 GMT
Received: from xmb-aln-x05.cisco.com ([169.254.11.251]) by xhc-aln-x10.cisco.com ([173.36.12.84]) with mapi id 14.02.0318.001; Mon, 12 Nov 2012 14:17:07 -0600
From: "Palani Chinnakannan (pals)" <pals@cisco.com>
To: Jakob Heitz <jakob.heitz@ericsson.com>
Thread-Topic: [irs-discuss] What's in a name?
Thread-Index: AQHNwQc8AF7Qd7B0YEa0VdWmP9+oKpfnAhgA//+fy/A=
Date: Mon, 12 Nov 2012 20:17:07 +0000
Message-ID: <7AB3E60F793B2E42BA2E4A8A761E249C756D8F@xmb-aln-x05.cisco.com>
References: <015701cdc0e4$fbc439f0$f34cadd0$@olddog.co.uk> <CAOndX-uiOo4cO3t6wym1SECSs7YTByAWWu9=ZVBLbLjMArnVjA@mail.gmail.com> <2F3EBB88EC3A454AAB08915FBF0B8C7E0D898D@EUSAAMB109.ericsson.se>
In-Reply-To: <2F3EBB88EC3A454AAB08915FBF0B8C7E0D898D@EUSAAMB109.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [171.71.139.238]
x-tm-as-product-ver: SMEX-10.2.0.1135-7.000.1014-19356.005
x-tm-as-result: No--45.588800-8.000000-31
x-tm-as-user-approved-sender: No
x-tm-as-user-blocked-sender: No
Content-Type: multipart/alternative; boundary="_000_7AB3E60F793B2E42BA2E4A8A761E249C756D8Fxmbalnx05ciscocom_"
MIME-Version: 1.0
Cc: "irs-discuss@ietf.org" <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\)" <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 20:17:10 -0000

In general,  the reason why some of us feel that we should a use a much generic name like INS (Interface to network system) or INE (Interface to network element) etc is because the  operations, data models and the requirements spelled out in IRS as much wider scope that the routing table.  IMHO,  its scope is a full network system.  By introducing a name at a higher scope paves way for defining several other interface to components of a network (routing, transport, network, NE ...) in a consistent framework as spelled in IRS.

pals

From: irs-discuss-bounces@ietf.org [mailto:irs-discuss-bounces@ietf.org] On Behalf Of Jakob Heitz
Sent: Monday, November 12, 2012 11:56 AM
Cc: irs-discuss@ietf.org
Subject: Re: [irs-discuss] What's in a name?

The similarity between
Routing Information Protocol
and
Rest In Peace
never confused anyone.
Did it?

--
Jakob Heitz.


________________________________
From: irs-discuss-bounces@ietf.org<mailto:irs-discuss-bounces@ietf.org> [mailto:irs-discuss-bounces@ietf.org]<mailto:[mailto:irs-discuss-bounces@ietf.org]> On Behalf Of Sriganesh Kini
Sent: Monday, November 12, 2012 10:55 AM
To: adrian@olddog.co.uk<mailto:adrian@olddog.co.uk>
Cc: irs-discuss@ietf.org<mailto:irs-discuss@ietf.org>
Subject: Re: [irs-discuss] What's in a name?
PRI - Programmatic Routing Interface

Though this clashes with PRI of ISDN fame that has long been buried. IRS, besides the obvious clash can mess up the search results. Also, I don't see a good reason to include 'System' in the acronym.

On Mon, Nov 12, 2012 at 6:49 AM, Adrian Farrel <adrian@olddog.co.uk<mailto: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 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<mailto:irs-discuss@ietf.org>
https://www.ietf.org/mailman/listinfo/irs-discuss



--
- Sri

v2.23.0 | Report a Bug | By Email