Re: [Int-area] I-D Action: draft-shen-traceroute-ping-ext-04.txt

"Eggert, Lars" <lars@netapp.com> Sat, 03 March 2012 08:56 UTC

Return-Path: <lars@netapp.com>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B3B7521F86F0 for <int-area@ietfa.amsl.com>; Sat, 3 Mar 2012 00:56:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.377
X-Spam-Level:
X-Spam-Status: No, score=-10.377 tagged_above=-999 required=5 tests=[AWL=0.222, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 l+TMlgrCkt3w for <int-area@ietfa.amsl.com>; Sat, 3 Mar 2012 00:56:03 -0800 (PST)
Received: from mx2.netapp.com (mx2.netapp.com [216.240.18.37]) by ietfa.amsl.com (Postfix) with ESMTP id 0D5B621F86EF for <int-area@ietf.org>; Sat, 3 Mar 2012 00:56:03 -0800 (PST)
X-IronPort-AV: E=Sophos; i="4.73,525,1325491200"; d="p7s'?scan'208"; a="630374755"
Received: from smtp1.corp.netapp.com ([10.57.156.124]) by mx2-out.netapp.com with ESMTP; 03 Mar 2012 00:55:46 -0800
Received: from vmwexceht04-prd.hq.netapp.com (vmwexceht04-prd.hq.netapp.com [10.106.77.34]) by smtp1.corp.netapp.com (8.13.1/8.13.1/NTAP-1.6) with ESMTP id q238tkp7012432; Sat, 3 Mar 2012 00:55:46 -0800 (PST)
Received: from SACEXCMBX04-PRD.hq.netapp.com ([169.254.6.92]) by vmwexceht04-prd.hq.netapp.com ([10.106.77.34]) with mapi id 14.02.0247.003; Sat, 3 Mar 2012 00:54:53 -0800
From: "Eggert, Lars" <lars@netapp.com>
To: Naiming Shen <naiming@cisco.com>
Thread-Topic: [Int-area] I-D Action: draft-shen-traceroute-ping-ext-04.txt
Thread-Index: AQHM+Rtrgvojn5f6E0aFnPeUKN41pQ==
Date: Sat, 03 Mar 2012 08:55:45 +0000
Message-ID: <709D93F8-C6C0-4F7D-A823-35540D683EE6@netapp.com>
References: <20120227213938.20370.68711.idtracker@ietfa.amsl.com> <9C0C873C-D52F-4EC8-939C-FD2373FDC9ED@cisco.com>
In-Reply-To: <9C0C873C-D52F-4EC8-939C-FD2373FDC9ED@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-originating-ip: [10.104.60.115]
Content-Type: multipart/signed; boundary="Apple-Mail=_F6582E1C-3217-4CFB-BCF8-FCBBE1355B74"; protocol="application/pkcs7-signature"; micalg="sha1"
MIME-Version: 1.0
Cc: "int-area@ietf.org" <int-area@ietf.org>
Subject: Re: [Int-area] I-D Action: draft-shen-traceroute-ping-ext-04.txt
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/int-area>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 03 Mar 2012 08:56:03 -0000

Hi,

> 8.  IANA Considerations
> 
>    The IANA is requested to assign a well-known port number, Trace-Ping
>    Port, for the UDP and TCP of this Trace-Ping extensions.

I'm curious why you think you need a port number for this ping extension. Ping is a diagnostic procedure that can be used with any port, and placing payload into the packet sent to elicit the ICMP response doesn't change that.

In other words, ping isn't a protocol.

Also, with regards to TCP ping, do you envision your payload data to be placed inside the SYN?

Lars