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

Brian E Carpenter <brian.e.carpenter@gmail.com> Tue, 30 October 2018 19:43 UTC

Return-Path: <brian.e.carpenter@gmail.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 241E6130E03 for <ipv6@ietfa.amsl.com>; Tue, 30 Oct 2018 12:43:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 KaeMJm8tiVL8 for <ipv6@ietfa.amsl.com>; Tue, 30 Oct 2018 12:43:45 -0700 (PDT)
Received: from mail-pl1-x62c.google.com (mail-pl1-x62c.google.com [IPv6:2607:f8b0:4864:20::62c]) (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 3E3B2130E1D for <ipv6@ietf.org>; Tue, 30 Oct 2018 12:43:45 -0700 (PDT)
Received: by mail-pl1-x62c.google.com with SMTP id n4-v6so5484059plp.2 for <ipv6@ietf.org>; Tue, 30 Oct 2018 12:43:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language:content-transfer-encoding; bh=+ndaPwTkMol8XeR3to+eugwvWIiTXUucxsmmNTs2f+k=; b=r+wLXrBsooxMfbM9idCcZiRs4LILEwcsECmHkLXw3/0rkmPPdeyxkJIG0BBX7Hac5x 1dgW0C5amYwkJ4act7Qn6VeeTeYGPJsHtLCyjs3uFghgFIOn/j2sPtYxJmReX1pCVPaw wVzJQ0gX8w8PU1gIq7eGBT+8t6PWky5mQnJBwKg++BKmWJ/2lzY2abXb/c1z96HcX0CN CPY4CIt9h3o2kSDh9YtTzzQiYVB3ViO+ZjeQLM2myskASETDgv2L+WgoSi8+rb+gA3UL QmpEPboOLyeD+A3ctBDDJCDM2iopR0wHcRzKQz3SXO9mmUe0waeTNi5l19gDyhjM8zP3 D7vA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=+ndaPwTkMol8XeR3to+eugwvWIiTXUucxsmmNTs2f+k=; b=brf90j/cmgJyQldxiN8eBoSrGIBGnNyUYW7XXGrPUmZNqGXaqH9JnOt/f7wJpu/Nbs kc8DN8YfmchoB0idWwUN+EJ8Ozwg6Wcts82f/baqxK3wGwlgEdyZVEibVkPzIU5vzT+j ekZulAeFJZtoQf/g4dOeahJ3hVps6U1n2KZY915Bcv3okHgUfZt8eQnmxVX8OkD3c9Zs RWCncyBiMzdlrTSSOVZfO0jlzMBv3TNm4UR+oz2Y3m8tiiMM27Dum2CCGCvwiZEae3gO CAsDGDMSY82IURXpx0OkSHjYu5PQKf2Icm3bkPjZh/7/FbPFVx3ehKiH4p3XneyGYxlb uEdw==
X-Gm-Message-State: AGRZ1gLlFGbJgKwnHx48gJ4jqH/GoU1UOkwM7/3DhA71KAy0m14yT2Ga T9mIsNWTN4cIZxDuPne9EtouXZ2J
X-Google-Smtp-Source: AJdET5d30R0LBNDXECN89Dkz6pwM2EiEEM9260zZ9ur9tbIhIjF8kfUwNNKikISzKgAmufDF7XXnpg==
X-Received: by 2002:a17:902:7484:: with SMTP id h4-v6mr45963pll.227.1540928624349; Tue, 30 Oct 2018 12:43:44 -0700 (PDT)
Received: from [192.168.178.30] ([118.148.76.40]) by smtp.gmail.com with ESMTPSA id y71-v6sm37560215pfk.70.2018.10.30.12.43.42 for <ipv6@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 30 Oct 2018 12:43:43 -0700 (PDT)
Subject: Re: Running code (Was: I-D Action: draft-ietf-6man-ipv6only-flag-03.txt)
To: ipv6@ietf.org
References: <CAFU7BASO_ByzbanhLKnWV280O_fASd-8W+ujpj3sN6d2-whw2w@mail.gmail.com> <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> <1157b739-3a66-8d45-e3e1-e5f904dfb9bc@asgard.org> <a00607f9-7ced-f889-b5cb-c2fe16367d73@si6networks.com> <66759b73-0a22-e1a9-49db-21154e8e1267@gmail.com> <37ba23b3-df19-9c2a-bdbe-ba7a99d72d05@si6networks.com> <0d6008a4-337b-2ccb-2d9f-837f786eca65@gmail.com> <bfa4397a-aa7a-1184-4147-4cbfbfd13603@si6networks.com> <8C587906-F0EE-4A61-9046-2BF AC52588C0@isc.org> <E8DE18B5-94FC-411C-A310-E49A382E0079@thehobsons.co.uk> <e0fa8fad1b4249c9af79788323b0a922@boeing.com> <3A03A073-72E2-43A8-90A4-5C29DF445361@thehobsons.co.uk> <27fdbd71125842d888c5136684bf6e7b@boeing.com> <9A4368D6-E4B1-474C-9838-B584AF6D70C8@thehobsons.co.uk> <m1gHUMI-0000I6C@stereo.hq.phicoh.net>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <9e3f31a2-2a38-cb47-a7b0-73a4c3cbf21b@gmail.com>
Date: Wed, 31 Oct 2018 08:43:40 +1300
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1
MIME-Version: 1.0
In-Reply-To: <m1gHUMI-0000I6C@stereo.hq.phicoh.net>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/EnDLFDx34OEahRUS0PKwpdWrQ-Q>
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: Tue, 30 Oct 2018 19:44:00 -0000

On 2018-10-31 02:47, Philip Homburg wrote:
>> So, here's the challenge which you seem to be holding back from,
>> write down the actual rules. No hand waving that "that's a good
>> clue", but actual rules that "if you see <some observable state>
>> then <do some specific action>".

If by "rules" you mean "a typical heuristic", sure. But there will
be hosts that follow a different logic for their own good reasons.
That simply isn't the IETF's business.

The draft is quite clear on this:

   Dual stack hosts that have a good reason to use IPv4, for example for
   a specific IPv4 link-local service, can attempt to do so.  Therefore
   respect of the IPv6-Only flag is recommended, not mandatory, for
   hosts.

On 2018-10-31 04:18, Toerless Eckert wrote:
...
> IMHO:
> 
> If the host sees the ipv6only flag from all IPv6 routers, it MUST NOT
> perform IPv4 DHCP.

Who cares? Legacy hosts will try DHCP anyway. We don't want an updated
host to waste spectrum on this, but that's a SHOULD NOT, because such
traffic won't actually break anything.

    Brian