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

"Metzler, Dan J" <dan-metzler@uiowa.edu> Thu, 02 October 2014 11:51 UTC

Return-Path: <dan-metzler@uiowa.edu>
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 DA1761A1ADB for <v6ops@ietfa.amsl.com>; Thu, 2 Oct 2014 04:51:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.385
X-Spam-Level:
X-Spam-Status: No, score=-3.385 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.786] 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 sZnTjkbogM1x for <v6ops@ietfa.amsl.com>; Thu, 2 Oct 2014 04:51:55 -0700 (PDT)
Received: from ITSNT447.iowa.uiowa.edu (itsnt447.iowa.uiowa.edu [128.255.67.11]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EE2FE1A1AD0 for <v6ops@ietf.org>; Thu, 2 Oct 2014 04:51:54 -0700 (PDT)
Received: from ITSNT440.iowa.uiowa.edu ([169.254.2.150]) by ITSNT447.iowa.uiowa.edu ([128.255.67.11]) with mapi id 14.03.0195.001; Thu, 2 Oct 2014 06:51:51 -0500
From: "Metzler, Dan J" <dan-metzler@uiowa.edu>
To: Lorenzo Colitti <lorenzo@google.com>, Joe Touch <touch@isi.edu>
Thread-Topic: [v6ops] IPv6 Extension Headers in the Real World
Thread-Index: AQHP3cgE66Go8UIYvka1CtjXhjqwQpwcKteAgAACD4CAANPigP//ribA
Date: Thu, 02 Oct 2014 11:51:50 +0000
Message-ID: <9062DD5BB047BF4C96BCE0CB9DA96D1B4DE1C0C7@ITSNT440.iowa.uiowa.edu>
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>
In-Reply-To: <CAKD1Yr2JB6V61D+JcUR2qj6-AGEAQr+Jn0eOUPSLEOKXZ1cEqw@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [128.255.6.15]
Content-Type: multipart/alternative; boundary="_000_9062DD5BB047BF4C96BCE0CB9DA96D1B4DE1C0C7ITSNT440iowauio_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/v6ops/hAm-G_wUcRSciWmfDlvI0dfe2l4
Cc: "draft-gont-v6ops-ipv6-ehs-in-real-world@tools.ietf.org" <draft-gont-v6ops-ipv6-ehs-in-real-world@tools.ietf.org>, IPv6 Operations <v6ops@ietf.org>, V6ops Chairs <v6ops-chairs@tools.ietf.org>, Fernando Gont <fernando@gont.com.ar>
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 11:51:57 -0000

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.

From: v6ops [mailto:v6ops-bounces@ietf.org] On Behalf Of Lorenzo Colitti
Sent: Thursday, October 2, 2014 6:30 AM
To: Joe Touch
Cc: draft-gont-v6ops-ipv6-ehs-in-real-world@tools.ietf.org; V6ops Chairs; IPv6 Operations; Fernando Gont
Subject: Re: [v6ops] IPv6 Extension Headers in the Real World

On Thu, Oct 2, 2014 at 7:52 AM, Joe Touch <touch@isi.edu<mailto:touch@isi.edu>> wrote:
I don't see "here's what I saw" and "here's what to do about it" as
separately useful.

In theory having separate documents is useless.

In practice having separate documents is extremely useful, because it turns out that it's much easier to agree on "here's what I saw" than on "here's what to do about it". In a consensus-oriented body like the IETF, there's no output until people agree, so attempting to document both a problem and a solution at the same time can take months or even years longer than documenting the two separately.