Re: [v6ops] IPv6 Extension Headers in the Real World

Tim Chown <tjc@ecs.soton.ac.uk> Thu, 02 October 2014 13:13 UTC

Return-Path: <tjc@ecs.soton.ac.uk>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 93E911A7D82 for <v6ops@ietfa.amsl.com>; Thu, 2 Oct 2014 06:13:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.006
X-Spam-Level:
X-Spam-Status: No, score=-2.006 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.786, SPF_NEUTRAL=0.779] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cziQPGsoJN0I for <v6ops@ietfa.amsl.com>; Thu, 2 Oct 2014 06:13:15 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [IPv6:2001:630:d0:f102::25e]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D8E741A701D for <v6ops@ietf.org>; Thu, 2 Oct 2014 06:13:13 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (localhost.ecs.soton.ac.uk [127.0.0.1]) by falcon.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id s92DD6Wf003912; Thu, 2 Oct 2014 14:13:06 +0100
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk s92DD6Wf003912
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=201304; t=1412255587; bh=3Sep6cnM7NviE5ntFVjTTTUugBc=; h=Mime-Version:Subject:From:In-Reply-To:Date:Cc:References:To; b=cPFUtAw1ci/Rc1P6PjIEz1cgydQqN5ihrrVlEzXxr6PpS4aQm3O7+L7zomdpJhF4R x9HAobxqBhIkDENDV1DEuSaqejPh7yvAqGYX5e+TvwpT9mBFS+UdELWRWHYEBFqtXh EBcfb9qPbYaknaEiHV6T3MSftA7Tfkk68c/BrQw0=
Received: from gander.ecs.soton.ac.uk ([2001:630:d0:f102:250:56ff:fea0:401]) by falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [2001:630:d0:f102:250:56ff:fea0:68da]) envelope-from <tjc@ecs.soton.ac.uk> with ESMTP (valid=N/A) id q91ED63054707044px ret-id none; Thu, 02 Oct 2014 14:13:07 +0100
Received: from [IPv6:2001:630:d0:ed04:8142:4437:7d2e:7792] ([IPv6:2001:630:d0:ed04:8142:4437:7d2e:7792]) (authenticated bits=0) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id s92DD3vO018650 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 2 Oct 2014 14:13:04 +0100
Content-Type: multipart/alternative; boundary="Apple-Mail=_08E3CD8A-0CFE-4B75-A517-230BD2EE417D"
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Tim Chown <tjc@ecs.soton.ac.uk>
In-Reply-To: <9062DD5BB047BF4C96BCE0CB9DA96D1B4DE1C0C7@ITSNT440.iowa.uiowa.edu>
Date: Thu, 02 Oct 2014 14:13:03 +0100
Message-ID: <EMEW3|0e9b5822392d744642b47f8f3cb94f76q91ED603tjc|ecs.soton.ac.uk|E69F8B2A-C8F9-4978-B2F8-0F6C74619BA0@ecs.soton.ac.uk>
References: <542A36AC.9030203@gont.com.ar> <542C81B7.10601@isi.edu> <99A3738D-954C-4A75-8055-E30D0D73DD80@ecs.soton.ac.uk> <EMEW3|fe883999a173b6d6b6b574badb6ebb53q90Niq03tjc|ecs.soton.ac.uk|99A3738D-954C-4A75-8055-E30D0D73DD80@ecs.soton.ac.uk> <542C8595.6080809@isi.edu> <CAKD1Yr2JB6V61D+JcUR2qj6-AGEAQr+Jn0eOUPSLEOKXZ1cEqw@mail.gmail.com> <9062DD5BB047BF4C96BCE0CB9DA96D1B4DE1C0C7@ITSNT440.iowa.uiowa.edu> <E69F8B2A-C8F9-4978-B2F8-0F6C74619BA0@ecs.soton.ac.uk>
To: "Metzler, Dan J" <dan-metzler@uiowa.edu>
X-Mailer: Apple Mail (2.1878.6)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=q91ED6305470704400; tid=q91ED63054707044px; client=relay,forged,no_ptr,ipv6; mail=; rcpt=; nrcpt=7:0; fails=0
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-ID: s92DD6Wf003912
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
Archived-At: http://mailarchive.ietf.org/arch/msg/v6ops/-cdaeAXaJlVaEOCnikHXKL0O33Y
Cc: IPv6 Operations <v6ops@ietf.org>, Fernando Gont <fernando@gont.com.ar>, "draft-gont-v6ops-ipv6-ehs-in-real-world@tools.ietf.org" <draft-gont-v6ops-ipv6-ehs-in-real-world@tools.ietf.org>, V6ops Chairs <v6ops-chairs@tools.ietf.org>
Subject: Re: [v6ops] IPv6 Extension Headers in the Real World
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.15
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: Thu, 02 Oct 2014 13:13:25 -0000

On 2 Oct 2014, at 12:51, Metzler, Dan J <dan-metzler@uiowa.edu> wrote:

> I would think that if it’s much easier to agree on “here’s what I saw”, then it would work better if the first draft includes the problem statement, and then later drafts flesh out “here’s what to do about it”.  Even in practice, simply agreeing on the nature of the problem, is of limited value without the knowledge of solutions, or even the knowledge that a solution may not exist yet.  Even if there are multiple solutions to a problem, it is always important to state the problem that each solution is designed to solve when presenting any solution.

Indeed. As an author of the ‘what I saw’ it seems appropriate to document an issue that others can discuss and decide what action(s) to take.  

So separation of authorship is one thing.

Another is that there might be multiple ‘here’s what to do about it’ documents, as there have been with other operational problem statements. There might be Informational or BCP documents in v6ops suggesting mitigation methods, and/or there might be protocol changes through 6man.

Tim