IETF Logo Mail Archive

Re: [v6ops] IPv6 Diagnostic Option

Erik Kline <ek@google.com> Fri, 22 July 2011 06:35 UTC

Return-Path: <ek@google.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B82E911E8070 for <ipv6@ietfa.amsl.com>; Thu, 21 Jul 2011 23:35:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.939
X-Spam-Level:
X-Spam-Status: No, score=-105.939 tagged_above=-999 required=5 tests=[AWL=0.038, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 XUg+krSb4a5g for <ipv6@ietfa.amsl.com>; Thu, 21 Jul 2011 23:35:41 -0700 (PDT)
Received: from smtp-out.google.com (smtp-out.google.com [74.125.121.67]) by ietfa.amsl.com (Postfix) with ESMTP id A50EA11E8079 for <ipv6@ietf.org>; Thu, 21 Jul 2011 23:35:40 -0700 (PDT)
Received: from wpaz13.hot.corp.google.com (wpaz13.hot.corp.google.com [172.24.198.77]) by smtp-out.google.com with ESMTP id p6M6Zd2V014712 for <ipv6@ietf.org>; Thu, 21 Jul 2011 23:35:39 -0700
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta; t=1311316539; bh=kRxK+sWY51G7WW35LXKetz0sROs=; h=MIME-Version:In-Reply-To:References:Date:Message-ID:Subject:From: To:Cc:Content-Type; b=rvQkpbu9JXDcqvju1lUq7AuDr0MqyHBy25r69OGVh9WsKXonvGpDOQM9JOytYaaJ0 aRy9yTY4rOZ8w8AAYbXEg==
DomainKey-Signature: a=rsa-sha1; s=beta; d=google.com; c=nofws; q=dns; h=dkim-signature:mime-version:in-reply-to:references:date: message-id:subject:from:to:cc:content-type:x-system-of-record; b=n1lMcD61CynWY3v2gjeyYj8Yz5Vf/yAPsNgET9yljKj1QOrAhKHTkQs86ufN7qN+V dhgcjBH6yTH4KLaDGF7yw==
Received: from qwf7 (qwf7.prod.google.com [10.241.194.71]) by wpaz13.hot.corp.google.com with ESMTP id p6M6ZbuG010893 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NOT) for <ipv6@ietf.org>; Thu, 21 Jul 2011 23:35:38 -0700
Received: by qwf7 with SMTP id 7so1264190qwf.24 for <ipv6@ietf.org>; Thu, 21 Jul 2011 23:35:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=beta; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=ioT0gSkT6dA+jd5vmIusFdyjhJj6uUO4BeADtmOmLsU=; b=M1IrWQ6H5/fpV2lN8ivPhzl2g16oxjPbYRfpzLrPlAyfmD8pjVeTS6gnxbQkeznMpy NCfQtj4VCE/QOrrVxEeQ==
MIME-Version: 1.0
Received: by 10.224.200.5 with SMTP id eu5mr976844qab.189.1311316537786; Thu, 21 Jul 2011 23:35:37 -0700 (PDT)
Received: by 10.229.136.66 with HTTP; Thu, 21 Jul 2011 23:35:37 -0700 (PDT)
In-Reply-To: <4E290D99.3030300@kit.edu>
References: <1311309532.77035.YahooMailClassic@web2814.biz.mail.ne1.yahoo.com> <4E290D99.3030300@kit.edu>
Date: Fri, 22 Jul 2011 15:35:37 +0900
Message-ID: <CAAedzxr5JrXKfRAfo+e7CwkvvFBRju3n8CL2xpRvhaS7hcjPng@mail.gmail.com>
Subject: Re: [v6ops] IPv6 Diagnostic Option
From: Erik Kline <ek@google.com>
To: Roland Bless <roland.bless@kit.edu>
Content-Type: text/plain; charset="UTF-8"
X-System-Of-Record: true
Cc: v6ops@ietf.org, ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Jul 2011 06:35:41 -0000

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

Agreed.

I also think use of the flowlabel will prove operationally simpler.
Some devices drop IPv6 packets that have any kind of headers, even
fragment headers, since they lack the ability to look beyond these
headers at line rate.

v2.23.0 | Report a Bug | By Email