Re: [v6ops] IPv6 Diagnostic Option

Roland Bless <roland.bless@kit.edu> Fri, 22 July 2011 05:41 UTC

Return-Path: <roland.bless@kit.edu>
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 9DE4321F866A; Thu, 21 Jul 2011 22:41:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.249
X-Spam-Level:
X-Spam-Status: No, score=-6.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ETJGdMEovsHQ; Thu, 21 Jul 2011 22:41:53 -0700 (PDT)
Received: from iramx2.ira.uni-karlsruhe.de (iramx2.ira.uni-karlsruhe.de [141.3.10.81]) by ietfa.amsl.com (Postfix) with ESMTP id 9A22A21F8669; Thu, 21 Jul 2011 22:41:52 -0700 (PDT)
Received: from irams1.ira.uni-karlsruhe.de ([141.3.10.5]) by iramx2.ira.uni-karlsruhe.de with esmtps port 25 id 1Qk8Ub-0001kM-Na; Fri, 22 Jul 2011 07:41:51 +0200
Received: from i72vorta.tm.uni-karlsruhe.de ([141.3.71.26] helo=vorta.tm.kit.edu) by irams1.ira.uni-karlsruhe.de with esmtp port 25 id 1Qk8Ub-0004nJ-JS; Fri, 22 Jul 2011 07:41:45 +0200
Received: from [IPv6:::1] (localhost [127.0.0.1]) by vorta.tm.kit.edu (Postfix) with ESMTPS id 788C6A800D4; Fri, 22 Jul 2011 07:41:45 +0200 (CEST)
Message-ID: <4E290D99.3030300@kit.edu>
Date: Fri, 22 Jul 2011 07:41:45 +0200
From: Roland Bless <roland.bless@kit.edu>
Organization: Institute of Telematics, Karlsruhe Institute of Technology (KIT)
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.1) Gecko/20060111 Thunderbird/1.5 Mnenhy/0.7.3.0
MIME-Version: 1.0
To: v6ops@ietf.org
References: <1311309532.77035.YahooMailClassic@web2814.biz.mail.ne1.yahoo.com>
In-Reply-To: <1311309532.77035.YahooMailClassic@web2814.biz.mail.ne1.yahoo.com>
X-Enigmail-Version: 1.1.2
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-ATIS-AV: ClamAV (irams1.ira.uni-karlsruhe.de)
X-ATIS-AV: ClamAV (iramx2.ira.uni-karlsruhe.de)
X-ATIS-AV: Kaspersky (iramx2.ira.uni-karlsruhe.de)
X-ATIS-Timestamp: iramx2.ira.uni-karlsruhe.de 1311313311.417554000
Cc: ipv6@ietf.org
Subject: Re: [v6ops] IPv6 Diagnostic Option
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: Fri, 22 Jul 2011 05:41:54 -0000

Hi,

On 22.07.2011 06:38, nalini.elkins@insidethestack.com wrote:
> Would love to get feedback on an Internet Draft we have submitted.

> The issue we are addressing is that the IP Identification field which
> was available with IPv4 in the main header is available with IPv6
> only in the Fragment Header.

I don't think that your proposed solution is necessary, since
IPv6 has the Flow Label, that - if set by the source - may be
very well suited for your purpose (tracking flows along a path).
Please see http://datatracker.ietf.org/doc/draft-ietf-6man-flow-3697bis/
for more details.

Kind regards,
 Roland