Re: [hybi] With deflate-stream / websocket traceroute action

John Tamplin <jat@google.com> Fri, 25 February 2011 13:34 UTC

Return-Path: <jat@google.com>
X-Original-To: hybi@core3.amsl.com
Delivered-To: hybi@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 726453A69C1 for <hybi@core3.amsl.com>; Fri, 25 Feb 2011 05:34:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.87
X-Spam-Level:
X-Spam-Status: No, score=-105.87 tagged_above=-999 required=5 tests=[AWL=0.106, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 g18KPRACepF8 for <hybi@core3.amsl.com>; Fri, 25 Feb 2011 05:34:13 -0800 (PST)
Received: from smtp-out.google.com (smtp-out.google.com [216.239.44.51]) by core3.amsl.com (Postfix) with ESMTP id DBD7E3A69BA for <hybi@ietf.org>; Fri, 25 Feb 2011 05:34:12 -0800 (PST)
Received: from wpaz29.hot.corp.google.com (wpaz29.hot.corp.google.com [172.24.198.93]) by smtp-out.google.com with ESMTP id p1PDZ4v5000430 for <hybi@ietf.org>; Fri, 25 Feb 2011 05:35:04 -0800
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta; t=1298640904; bh=FpujIpF0ZDlFNy7YZDpGxJeGwcA=; h=MIME-Version:In-Reply-To:References:From:Date:Message-ID:Subject: To:Cc:Content-Type; b=ZoS5FneD4V1t17+MLkQIMV+iH7EXwCcCVM2Y2MD+O7QTRn5GkJ3PX2mftckNuQ1hJ kISftJjrZbU6cTao3tWPA==
Received: from yxt33 (yxt33.prod.google.com [10.190.5.225]) by wpaz29.hot.corp.google.com with ESMTP id p1PDZ3FU014500 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NOT) for <hybi@ietf.org>; Fri, 25 Feb 2011 05:35:03 -0800
Received: by yxt33 with SMTP id 33so784913yxt.28 for <hybi@ietf.org>; Fri, 25 Feb 2011 05:35:03 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=beta; h=domainkey-signature:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=5V9W9A/0Lx3vus/N1EQ5DIO6mPgiemx6niWVu6mA9f8=; b=QTEd8OM9xloyQq56Q3fMPper5isgpNmBAWvcFQVpFpHtVVoVxUu1QTX6/XLCa87306 sL9bfg4yShuvpSThZhTA==
DomainKey-Signature: a=rsa-sha1; c=nofws; d=google.com; s=beta; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; b=FBonb9+fknyM/dTWYkffANGN8XrqTqq9rv6X8ojuvwiAjjJFEdOMWivetwbNBew+81 V5qK+NXVVQAQqiTATUHw==
Received: by 10.150.198.11 with SMTP id v11mr3545484ybf.388.1298640903235; Fri, 25 Feb 2011 05:35:03 -0800 (PST)
MIME-Version: 1.0
Received: by 10.150.200.16 with HTTP; Fri, 25 Feb 2011 05:34:42 -0800 (PST)
In-Reply-To: <4D6777BB.4070605@warmcat.com>
References: <OF9EDDF2DA.D45B4501-ON88257842.0027DEB4-88257842.002C3B97@playstation.sony.com> <4D6777BB.4070605@warmcat.com>
From: John Tamplin <jat@google.com>
Date: Fri, 25 Feb 2011 08:34:42 -0500
Message-ID: <AANLkTinCzHU+qKd9oPNX_eUEFNTkoNH_hadCsGa3YSpn@mail.gmail.com>
To: Andy Green <andy@warmcat.com>
Content-Type: multipart/alternative; boundary="000e0cd34888ba6813049d1b6501"
X-System-Of-Record: true
Cc: hybi-bounces@ietf.org, hybi@ietf.org, Yutaka_Takeda@playstation.sony.com
Subject: Re: [hybi] With deflate-stream / websocket traceroute action
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Server-Initiated HTTP <hybi.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/hybi>, <mailto:hybi-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/hybi>
List-Post: <mailto:hybi@ietf.org>
List-Help: <mailto:hybi-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/hybi>, <mailto:hybi-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 25 Feb 2011 13:34:14 -0000

On Fri, Feb 25, 2011 at 4:34 AM, Andy Green <andy@warmcat.com> wrote:

> In fact you can do traceroute just with PING / PONG if the standard allowed
> for
>
>  1) PONG MAY contain additional text after the PING payload echo
>
>  2) PING MUST contain a TTL byte at the start
>
>  3) Intermediaries MAY decrement the TTL when passing on PING
>
>  4) PONG SHOULD be issued by intermediary IF TTL = 0 after the decrement
> and MUST be by the endpoint regardless of TTL
>
>  5) When PONG issued, intermediary or endpoint MAY append its ID text
>

I am not sure how useful it would be if all these are MAY's -- in particular
the TTL seems useless if you don't require that it be decremented at each
hop.

However, requiring this would be complicate some simple intermediaries
dramatically -- I don't know if the value gained is worth anything.  Also,
there would seem to be a problem exposing this to JS -- you wouldn't want
hostile JS to be able to get a layout of the network behind the firewall.

What does this gain over using ICMP or UDP-based traceroute?

-- 
John A. Tamplin
Software Engineer (GWT), Google