[v6ops] draft-elkins-6man-ipv6-diagnostic-header (Was: draft minutes ietf 81, 3 meetings...)

Carlos Pignataro <cpignata@cisco.com> Sun, 14 August 2011 17:02 UTC

Return-Path: <cpignata@cisco.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0F84F21F8570 for <v6ops@ietfa.amsl.com>; Sun, 14 Aug 2011 10:02:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level:
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
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 XPgAWd5DuaLU for <v6ops@ietfa.amsl.com>; Sun, 14 Aug 2011 10:02:43 -0700 (PDT)
Received: from av-tac-rtp.cisco.com (hen.cisco.com [64.102.19.198]) by ietfa.amsl.com (Postfix) with ESMTP id 65E4A21F8565 for <v6ops@ietf.org>; Sun, 14 Aug 2011 10:02:43 -0700 (PDT)
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 p7EH3Pjn006196 for <v6ops@ietf.org>; Sun, 14 Aug 2011 13:03:25 -0400 (EDT)
Received: from [10.117.115.54] (rtp-cpignata-8915.cisco.com [10.117.115.54]) by rooster.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id p7EH3P7I002861 for <v6ops@ietf.org>; Sun, 14 Aug 2011 13:03:25 -0400 (EDT)
Message-ID: <4E47FFD4.5080307@cisco.com>
Date: Sun, 14 Aug 2011 13:03:16 -0400
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.24) Gecko/20100228 Thunderbird/2.0.0.24 Mnenhy/0.7.6.0
MIME-Version: 1.0
To: v6ops@ietf.org
References: <D6008BA7-7B05-49C2-B40D-DCD92A0FAF39@bogus.com>
In-Reply-To: <D6008BA7-7B05-49C2-B40D-DCD92A0FAF39@bogus.com>
X-Enigmail-Version: 1.2
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
Subject: [v6ops] draft-elkins-6man-ipv6-diagnostic-header (Was: draft minutes ietf 81, 3 meetings...)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 14 Aug 2011 17:02:44 -0000

Hi,

I believe there was one further point raised in regards to
draft-elkins-6man-ipv6-diagnostic-header (though I don't recall if it
was at the mike by Andrew Y., in a corridor, or only in my head): the
Heisenbug principle -- if this is used in debugging (and diagnostics),
the issue being studied or attempted to reproduce alters its behavior or
goes away when modifying the packet (like compiling with different -o).
I think this is one of the most important arguments against this
proposal. The use of fragment header is interesting, a new header could
show much more pronounced deviation of observed behaviour than without it.

For completeness, I did ask some services escalation engineers about how
they use the ip-id in IPv4 for troubleshooting, and basically got two
main uses for very corner case situations in: i. identify middleboxes
and their characteristics (by check IP ID increment patterns, find if
packets generated by the same box), and ii. track set of packets along
different points in the network (e.g., back-to-back packets and see
rate, drops, out of order). But it's built into the v4 header.

Thanks,

-- Carlos.

On 8/2/2011 1:24 PM, Joel Jaeggli wrote:
> * Presentation - RFC for IPv6 IP identification field (header) - Mike Ackerman
> 	     http://tools.ietf.org/agenda/81/slides/v6ops-7.ppt
> 	     http://tools.ietf.org/html/draft-elkins-6man-ipv6-diagnostic-header
> 
> Fred B - Question for the group, do you use the IPID in ipv4? (no
> respondants other than presenters)
> 
> Weg G - We use it all the time? I've never heard of it...
> 
> Francis D - it's potentially a covert channel, also why not use the
> fregmentation header?
> 
> Bob H - We diefintently want to hear if this is useful. I don't know
> who puts this header in the packet?
> 
> Nalini ? - The host clearly
> 
> Andrei Y - typical use case for this header would be to see if a
> middle box is modifying the packet. 
> 
> Fred B - What I'm out of this discussion is that the application isn't
> a bad one, it could be simulated in a fregment.
> 
> Fred Baker - Meeting complete, go to Lunch