Re: Running code (Was: I-D Action: draft-ietf-6man-ipv6only-flag-03.txt)

Job Snijders <job@ntt.net> Wed, 24 October 2018 13:52 UTC

Return-Path: <job@instituut.net>
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 F291F12785F for <ipv6@ietfa.amsl.com>; Wed, 24 Oct 2018 06:52:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.652
X-Spam-Level:
X-Spam-Status: No, score=-1.652 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001] autolearn=no autolearn_force=no
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 A5QWGFNqMpBx for <ipv6@ietfa.amsl.com>; Wed, 24 Oct 2018 06:52:38 -0700 (PDT)
Received: from mail-ed1-f50.google.com (mail-ed1-f50.google.com [209.85.208.50]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 22E55127133 for <ipv6@ietf.org>; Wed, 24 Oct 2018 06:52:38 -0700 (PDT)
Received: by mail-ed1-f50.google.com with SMTP id r1-v6so5114777edd.7 for <ipv6@ietf.org>; Wed, 24 Oct 2018 06:52:37 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=ph+py2nNLutrUsKWBEaZvVkixBlxGqkUbwkXXZ3JbaU=; b=PXmZAURrSi0ivVosy3Q0jvvgaCXovK8/jkKo37zGUkKWQ10BnjdVCkUnzJtWndv17a lZowlocgVdhgGzOY6eRVzsTNZJF4hK3Bl5uNXupOcd7yKkAIgGuPk/WmjHbpEFMrHEh8 +KdxJi7RZ2m6/eCrseSsuW/s3Tcfvma9fUNPkayw+EbB8mchZxTtvCcWmwSGXy4zpSEE j91C9SvYrolVYwmvXL4dm6CRO1lqerKq9+oOCLVhpnt9ttvhsHCQOVoAg7xUpODeTHAt LdTqH9owjQ0vEzje6SYmlMeHySrseVra+iFsDMpVj8gIk2YWvODKnQlwbFQO7aO4g2pI 8zBw==
X-Gm-Message-State: ABuFfogRHQKk291/WYlEQU7Dd6yu2syuXh/N3ZGcbOyjyIHLRoEi8HVt gggryB7IQbCgE/1IY0Mm/mfblA==
X-Google-Smtp-Source: ACcGV63LAqXJhcCUQJNmDTfSPOOWPWCVAicfBlfemT6F9HhX1rQ0p5HopvJ+q2OlrXOh/X2I1OnfiQ==
X-Received: by 2002:a50:b2a6:: with SMTP id p35-v6mr19246164edd.261.1540389156209; Wed, 24 Oct 2018 06:52:36 -0700 (PDT)
Received: from localhost ([2001:67c:208c:10:cd20:709f:1fd8:6996]) by smtp.gmail.com with ESMTPSA id w31-v6sm2002650edb.8.2018.10.24.06.52.34 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 24 Oct 2018 06:52:35 -0700 (PDT)
Date: Wed, 24 Oct 2018 15:52:33 +0200
From: Job Snijders <job@ntt.net>
To: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
Cc: Job Snijders <job@ntt.net>, Fernando Gont <fgont@si6networks.com>, Suresh Krishnan <suresh.krishnan@gmail.com>, 6man WG <ipv6@ietf.org>
Subject: Re: Running code (Was: I-D Action: draft-ietf-6man-ipv6only-flag-03.txt)
Message-ID: <CACWOCC-JmOKv-vmWBM5GF6c+=szv3a09o2oqMfvRXJwLRdWd3Q@mail.gmail.com>
References: <0927741c-4e8e-fcf7-ddd6-3ba500ba4c3d@si6networks.com> <7B48A11D-31DE-443C-B73A-14642EA0A397@jisc.ac.uk> <7526af75-4359-6fc6-e39b-eb94024a04de@si6networks.com> <E1BB1232-C1A2-496A-8157-0682D91EED42@steffann.nl> <5E75F3CA-F1D2-4F4F-9CF7-EEEE59634C1E@gmail.com> <C46C990E-0A4F-4731-8CB1-FD204858935E@consulintel.es> <9B53019C-3506-4C9E-AFCF-D6125FA1A65B@gmail.com> <2DC241B3-310B-4A3A-BD4C-C0005FCE6155@consulintel.es> <20181024103057.GD924@hanna.meerval.net> <1F8FC133-7887-457C-A316-D2E6FCD450E9@consulintel.es>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <1F8FC133-7887-457C-A316-D2E6FCD450E9@consulintel.es>
User-Agent: Mutt/1.10.1 (2018-07-13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/S0tnH6bW51DbK-f4cWqIPrRvQ1k>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.29
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: <https://mailarchive.ietf.org/arch/browse/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: Wed, 24 Oct 2018 13:52:40 -0000

Dear Jordi,

On Wed, Oct 24, 2018 at 1:08 PM JORDI PALET MARTINEZ <jordi.palet@consulintel.es> wrote:
> Then the vendors that have the power to implement everything they
> want, definitively win, only because they are able to implement it,
> not necessarily because it is good or bad, and the argument of the
> implementation will be a tool to reach consensus, even if it takes
> longer, more versions, etc. This is real life.

I wouldn't position yourself as 'powerless': you can fork any Linux or
BSD IP stacks yourself and make modifications - or you can hire people
to do so, or work with students. We are all vendors if we choose to be -
we all have this "power". And even if it takes longer, if drafts need to
go through more revisions - it usually is a sign the quality and
readability are increasing.

> Very good ideas that don't become standards because during the ID
> development don't get implemented (even if they will become
> implemented once they become RFCs), lose.

Can you point me to a protocol extension specification that was a
valuable publication, specifically as RFC, but does not have any
implementations? I see no harm for such drafts to wait for publication
until some implementation is done.

> I'm sure there have been already many IETF documents that have been in
> both situations. Market decides at the end. But that's the thing: at
> the end, most of the time only when there is an RFC.
>
> A couple of examples I can remember, IPv6 site local (it was an RFC)
> and draft-ietf-ipv6-dns-discovery, different process stages, both got
> implemented by many OS vendors and also Linux. No longer used.

No longer used? Consider proposing them to be deprecated! Pruning
specifications that turned out to be "not the best idea" is also an
important part of protocol maintenance.

> I'm sorry but it is discrimination.

I really don't see it, for more information on what discrimination means
to people please take a look at https://en.wikipedia.org/wiki/Discrimination

I suspect you are using such strong words to make an appeal to emotion.

Kind regards,

Job