Re: [Gen-art] Gen-ART review of draft-atlas-icmp-unnumbered-08

Carlos Pignataro <cpignata@cisco.com> Mon, 28 December 2009 16:49 UTC

Return-Path: <cpignata@cisco.com>
X-Original-To: gen-art@core3.amsl.com
Delivered-To: gen-art@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D6D6A3A6824 for <gen-art@core3.amsl.com>; Mon, 28 Dec 2009 08:49:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.999
X-Spam-Level:
X-Spam-Status: No, score=-5.999 tagged_above=-999 required=5 tests=[AWL=-0.600, BAYES_00=-2.599, J_CHICKENPOX_42=0.6, J_CHICKENPOX_43=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PtAY1scWhKP4 for <gen-art@core3.amsl.com>; Mon, 28 Dec 2009 08:49:24 -0800 (PST)
Received: from av-tac-rtp.cisco.com (hen.cisco.com [64.102.19.198]) by core3.amsl.com (Postfix) with ESMTP id 01CAA3A6829 for <gen-art@ietf.org>; Mon, 28 Dec 2009 08:49:23 -0800 (PST)
X-TACSUNS: Virus Scanned
Received: from rooster.cisco.com (localhost.cisco.com [127.0.0.1]) by av-tac-rtp.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id nBSGmvPT025335; Mon, 28 Dec 2009 11:48:57 -0500 (EST)
Received: from [64.102.157.137] (dhcp-64-102-157-137.cisco.com [64.102.157.137]) by rooster.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id nBSGmu4c008441; Mon, 28 Dec 2009 11:48:56 -0500 (EST)
Message-ID: <4B38E178.4050509@cisco.com>
Date: Mon, 28 Dec 2009 11:48:56 -0500
From: Carlos Pignataro <cpignata@cisco.com>
Organization: cisco Systems, Inc.
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.23) Gecko/20090812 Thunderbird/2.0.0.23 Mnenhy/0.7.6.0
MIME-Version: 1.0
To: Black_David@emc.com
References: <C2D311A6F086424F99E385949ECFEBCB012C42D7@CORPUSMX80B.corp.emc.com>
In-Reply-To: <C2D311A6F086424F99E385949ECFEBCB012C42D7@CORPUSMX80B.corp.emc.com>
X-Enigmail-Version: 0.96.0
X-Face: *3w8NvnQ|kS~V{&{U}$?G9U9EJQ8p9)O[1[1F'1i>XIc$5FR!hdAIf5}'Xu-3`^Z']h0J* ccB'fl/XJYR[+, Z+jj`4%06nd'y9[ln&ScJT5S+O18e^
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Cc: JR Rivers <jrrivers@alumni.calpoly.edu>, rbonica@juniper.net, gen-art@ietf.org, naiming@cisco.com, jari.arkko@piuha.net, alia.atlas@bt.com
Subject: Re: [Gen-art] Gen-ART review of draft-atlas-icmp-unnumbered-08
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 28 Dec 2009 16:49:24 -0000

David,

Please find one additional comment response to your suggestion.

Excerpts from Black_David@emc.com on 12/27/2009:
> I suggest adding a Section 3.3 to discuss use of ifIndex with ICMP and
> network management tools (e.g., enhanced traceroute plus an SNMP
> manager)

I still feel that discussing this use would be a strong distraction and
divertion, and not add substativeness to the spec, ultimatelly causing
confusion.

My traceroute app at home does IP address-to-name mapping, querying DNS
and reporting hostnames; ICMP timexceeded was not spec'ed that way, but
a 'traceroute + hostname manager querier' was useful. It also does:
      -A: Report AS# at each hop (from GRR)
      -O: Report owner at each hop (from DNS)

because it was useful, and reports TOS change, none of which was
including on the ICMP timeexceeded or unreachable definitions.

A public use of the ifIndex can be to see different interfaces in a
router, seeing ECMPs with unnumbered, and not mapping them to an
interface name with an SNMP manager. That is a degree of idenfication,
to know they are different.

Describing an app like you suggest would implicitly limit, I think. We
are not spec'ing an application, only the extensions of ICMP, and it
seems to me that there is enough contextual applicability and motivation
(without falling into over-framing and under-scoping).

Thanks,

-- Carlos.