Re: New version of <draft-ietf-6man-ipv6only-flag-01.txt> published

Brian E Carpenter <brian.e.carpenter@gmail.com> Mon, 02 July 2018 22:27 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 3D5EA1313D1 for <ipv6@ietfa.amsl.com>; Mon, 2 Jul 2018 15:27:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 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, URIBL_BLOCKED=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 J-uLPkn4aDnc for <ipv6@ietfa.amsl.com>; Mon, 2 Jul 2018 15:27:26 -0700 (PDT)
Received: from mail-pl0-x230.google.com (mail-pl0-x230.google.com [IPv6:2607:f8b0:400e:c01::230]) (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 90E99131229 for <ipv6@ietf.org>; Mon, 2 Jul 2018 15:27:26 -0700 (PDT)
Received: by mail-pl0-x230.google.com with SMTP id y15-v6so6706524pll.9 for <ipv6@ietf.org>; Mon, 02 Jul 2018 15:27:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=RGSY4Hfg2ZWwF7bM+n3zqSgZ4wF7cPQ9MvNOpd1qzdc=; b=lkeH2CXKyLi0u42fNpzeXX1wVf7INCHT9gglxVaFfhR73kfQdNGDBqd2ZUCfXgLVmY Xz7nYvSZnSOPbBC8nJzcU3s0a5KOJWuVstJyWiDBrk6Fuihp6/c3qOUInB5Ivdq8mOao aabtqvOeuhht8yIhxZT6SsNpEys04E3k7d8UYmtmDRMh+WSp5sv0GFxmwjJm0eyB9MLB bqPI5p1XV0kdg4qBmfo75C1KGfSzjHLiIMk1ilNaI7U/jDohb4FwaZjzppsgz8RPB1G9 WUkC8oIII9FfA/MJ05XbEkRSaBOs55x2HiTpWJfdVrh6h5lWAacKppKNh3uJLmHaN6Z4 7UMw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=RGSY4Hfg2ZWwF7bM+n3zqSgZ4wF7cPQ9MvNOpd1qzdc=; b=QwB/62+UOKGjLfui4Adh2GhPlrBa0TOQVaaJrIDcwF1dQz9B2Qa8ZUQ+hoh7LSq3Dt SCtafVBGgmSdFbFxN1ZelPUHiiodAzZOi3TqUMXCaBXsl9EPK9egVpcFXe7wf6g/Pn0/ 9uTlKMdGKHf+VUvuZ2JPisUgO78Kl6Mpv1gQnTg8mOrAR+KgwDTf3vYJU221SiQq9578 IJP6yj4oibjhGr4/t9c95nUW0Ha3J/I1AnXTi+4X1lwbT+NGkrMXpwHNpz549p7Bw/JY /nbQYA+ltd9JC9gHe47tQVMp021cv9EpKtdJoQcHcVr5g1YHp+DFn7AjU9fQI2dhex1i AMDg==
X-Gm-Message-State: APt69E36RSdSjrN9geuIOIH7Jaiy5tuod15jOe47AGENT8AbAGTDF3Wu ookEmp0HYVoMXzxQpi944yQkZg==
X-Google-Smtp-Source: ADUXVKJoIZH28SzPvFMi5mcsp+eIk1jBG3lVHU1w19Y1YCMnOJeynkJHvH7RreyBhg1CeVpEOkz/UQ==
X-Received: by 2002:a17:902:b48f:: with SMTP id y15-v6mr27761442plr.261.1530570445654; Mon, 02 Jul 2018 15:27:25 -0700 (PDT)
Received: from [130.216.38.164] (sc-cs-567-laptop.uoa.auckland.ac.nz. [130.216.38.164]) by smtp.gmail.com with ESMTPSA id v14-v6sm14718069pfi.55.2018.07.02.15.27.22 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 02 Jul 2018 15:27:24 -0700 (PDT)
Subject: Re: New version of <draft-ietf-6man-ipv6only-flag-01.txt> published
To: Bob Hinden <bob.hinden@gmail.com>, David Farmer <farmer@umn.edu>
Cc: IPv6 List <ipv6@ietf.org>
References: <5953C6DE-F443-45CC-91C1-D4267049FA0D@gmail.com> <CAN-Dau0OYPbeck6_Lq6FQ+-6nztP9PVCpb75YFKcFzNUwBToSg@mail.gmail.com> <94212705-F7B8-44F2-87F0-794DD913A402@gmail.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <0c510f7c-e063-deda-5893-abc04b9db52b@gmail.com>
Date: Tue, 03 Jul 2018 10:27:21 +1200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0
MIME-Version: 1.0
In-Reply-To: <94212705-F7B8-44F2-87F0-794DD913A402@gmail.com>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/wa_Dt_LFuIMAKX4642EqoHT8Zc4>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.26
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: Mon, 02 Jul 2018 22:27:36 -0000

On 03/07/2018 07:36, Bob Hinden wrote:
> David,
> 
>> On Jul 1, 2018, at 9:19 PM, David Farmer <farmer@umn.edu> wrote:
>>
>> I agree that this flag should only be set if the router is configured to do so by an administrator. However, regardless of the configuration, the flag MUST NOT be set if the router has an IPv4 configuration for the interface in question. Put another way; it should not be possible to configure the router to lie.
>>
>> Maybe change the second paragraph of section 6 to something like the following;
>>
>> The intent is that the administrator of the router configures the router to set the IPv6-Only flag if she/he wants to tell the hosts on the link that the link is IPv6-Only. This is a configuration flag; it is not something that the router decides on its own. However, regardless of its configuration, the router MUST NOT set the flag if there is an IPv4 configuration on, or one is added to, the interface in question. If configured to set the flag and there is an IPv4 configuration on the interface in question, the router MAY also locally log a configuration error.
> 
> I worry that covering possible configuration errors will be problematic.   For example, what if the router administrator just turned off IPv4, but left the rest of the configuration of IPv4 on the router?   A lot of this is going to be implementation dependent and hard to specify in a document like this.

I tend to agree with Bob. Also, the best approach may depend on
the design of the router and its management interface.  I could
imagine a SOHO router in which it might be better to fully
automate things. So probably we should put all this at a SHOULD
level.

   Brian

> 
> I think the focus should be on what the desired behavior is on the wire.
> 
> Bob
> 
> 
>>
>> Thanks
>>
>> On Sat, Jun 30, 2018 at 10:36 PM, Bob Hinden <bob.hinden@gmail.com> wrote:
>> Hi,
>>
>> We published a new version of draft-ietf-6man-ipv6only-flag-01.txt.  The changes, based on recent list discussion, are:
>>
>>       *  Added text to section 4 that defines what IPv6-Only includes to
>>          clarify that only other version of the Internet protocol are in
>>          scope.
>>       *  Added clarification if the lifetime of all routers expire.
>>       *  Editorial changes.
>>
>> Please review, links below.
>>
>> Bob & Brian
>>
>> p.s. The diff and html version don’t seem to be available at the moment.  I have notified the secretariat.  Hopefully it will be fixed soon.
>>
>>
>> ———--------------
>>
>> Begin forwarded message:
>>
>> From: internet-drafts@ietf.org
>> Subject: I-D Action: draft-ietf-6man-ipv6only-flag-01.txt
>> Date: June 30, 2018 at 8:20:31 PM PDT
>> To: <i-d-announce@ietf.org>
>> Cc: ipv6@ietf.org
>>
>>
>> A New Internet-Draft is available from the on-line Internet-Drafts directories.
>> This draft is a work item of the IPv6 Maintenance WG of the IETF.
>>
>>        Title           : IPv6 Router Advertisement IPv6-Only Flag
>>        Authors         : Robert M. Hinden
>>                          Brian Carpenter
>>         Filename        : draft-ietf-6man-ipv6only-flag-01.txt
>>         Pages           : 11
>>         Date            : 2018-06-30
>>
>> Abstract:
>>   This document specifies a Router Advertisement Flag to indicate to
>>   hosts that the administrator has configured the router to advertise
>>   that the link is IPv6-Only.  This document updates RFC5175.
>>
>>
>> The IETF datatracker status page for this draft is:
>> https://datatracker.ietf.org/doc/draft-ietf-6man-ipv6only-flag/
>>
>> There are also htmlized versions available at:
>> https://tools.ietf.org/html/draft-ietf-6man-ipv6only-flag-01
>> https://datatracker.ietf.org/doc/html/draft-ietf-6man-ipv6only-flag-01
>>
>> A diff from the previous version is available at:
>> https://www.ietf.org/rfcdiff?url2=draft-ietf-6man-ipv6only-flag-01
>>
>>
>> Please note that it may take a couple of minutes from the time of submission
>> until the htmlized version and diff are available at tools.ietf.org.
>>
>> Internet-Drafts are also available by anonymous FTP at:
>> ftp://ftp.ietf.org/internet-drafts/
>>
>>
>>
>> --------------------------------------------------------------------
>> IETF IPv6 working group mailing list
>> ipv6@ietf.org
>> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
>> --------------------------------------------------------------------
>>
>>
>>
>>
>> --
>> ===============================================
>> David Farmer               Email:farmer@umn.edu
>> Networking & Telecommunication Services
>> Office of Information Technology
>> University of Minnesota
>> 2218 University Ave SE        Phone: 612-626-0815
>> Minneapolis, MN 55414-3029   Cell: 612-812-9952
>> ===============================================
> 
> 
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>