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

Keith Moore <moore@network-heretics.com> Sun, 14 August 2011 22:03 UTC

Return-Path: <moore@network-heretics.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 3875111E808A for <v6ops@ietfa.amsl.com>; Sun, 14 Aug 2011 15:03:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.45
X-Spam-Level:
X-Spam-Status: No, score=-3.45 tagged_above=-999 required=5 tests=[AWL=0.149, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 HBbARv0L9jAz for <v6ops@ietfa.amsl.com>; Sun, 14 Aug 2011 15:03:52 -0700 (PDT)
Received: from out4.smtp.messagingengine.com (out4.smtp.messagingengine.com [66.111.4.28]) by ietfa.amsl.com (Postfix) with ESMTP id 92F9611E8088 for <v6ops@ietf.org>; Sun, 14 Aug 2011 15:03:52 -0700 (PDT)
Received: from compute3.internal (compute3.nyi.mail.srv.osa [10.202.2.43]) by gateway1.messagingengine.com (Postfix) with ESMTP id 554C42226B; Sun, 14 Aug 2011 18:04:36 -0400 (EDT)
Received: from frontend1.messagingengine.com ([10.202.2.160]) by compute3.internal (MEProxy); Sun, 14 Aug 2011 18:04:36 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=subject:mime-version:content-type:from :in-reply-to:date:cc:content-transfer-encoding:message-id :references:to; s=smtpout; bh=r/A2PC5w7u0acvG26uQKREQfgqY=; b=fK q6/pRf77lFc42lUAVgJekD0WHLKkxVi2H+2gxnK26rfqibj70TrijwisNUC+xK0B 4D7bttaq33z+swg6cx2/FVqbjePk2II3Akv1GEitVLrDbiudYPpO6W8z3zUFp0rr 8GhTy8pgVSqvnRFlDz3ehLGvd5cRoTpoBQadY2UY8=
X-Sasl-enc: SqNNsgPPd4KpN42+fX+6gRtdeY1SMW94srtx+lCUvsYr 1313359475
Received: from host65-16-145-177.birch.net (host65-16-145-177.birch.net [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id 80D1A41D712; Sun, 14 Aug 2011 18:04:35 -0400 (EDT)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset="us-ascii"
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <4E47FFD4.5080307@cisco.com>
Date: Sun, 14 Aug 2011 18:04:34 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <961433FA-6907-4D5E-BC74-CCA0F56EC9BA@network-heretics.com>
References: <D6008BA7-7B05-49C2-B40D-DCD92A0FAF39@bogus.com> <4E47FFD4.5080307@cisco.com>
To: Carlos Pignataro <cpignata@cisco.com>
X-Mailer: Apple Mail (2.1084)
Cc: v6ops@ietf.org
Subject: Re: [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 22:03:53 -0000

On Aug 14, 2011, at 1:03 PM, Carlos Pignataro wrote:

> 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).

Yes, this can happen.  But that doesn't mean the mechanism is useless.   It just means that the potential error introduced by the mechanism needs to be taken into account when making measurements based on it.

(Just as Heisenberg's principle doesn't prevent us from measuring either present position or future momentum of a particle.  It just says that there's a limit to the precision with which both can be measured simultaneously.)

I basically think that it's a potentially good idea.  The real trick is understanding how to implement it in hosts so that it can be turned on when appropriate without affecting (much) the applications generating the affected traffic.

Keith