Re: Fwd: New Version Notification for draft-hinden-ipv4flag-00.txt

Brian E Carpenter <brian.e.carpenter@gmail.com> Fri, 17 November 2017 08:15 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 2487F1293E4 for <ipv6@ietfa.amsl.com>; Fri, 17 Nov 2017 00:15:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 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_LOW=-0.7, 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 gFBbbjjCkFwc for <ipv6@ietfa.amsl.com>; Fri, 17 Nov 2017 00:15:21 -0800 (PST)
Received: from mail-it0-x230.google.com (mail-it0-x230.google.com [IPv6:2607:f8b0:4001:c0b::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 CCB14124319 for <ipv6@ietf.org>; Fri, 17 Nov 2017 00:15:20 -0800 (PST)
Received: by mail-it0-x230.google.com with SMTP id u132so3176123ita.0 for <ipv6@ietf.org>; Fri, 17 Nov 2017 00:15:20 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:organization:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=layFOthoU0bqp2x63BAeIQLsVbdLtAF5fO7oDLZQM9M=; b=A8F6iVs2Ja08YfaeftjUvnS4mIJySGPskerLZDZYqEeoOlnpuNhyncHXdf/cKXeA1Y 0/YmLE75k49/4sE7HwZQiBRWIcGvC+qafaba2YZ/B9yAiwXuPhk1F6S9TiDuWczVhdQ2 STC11JBxskaDDfYMq06emG/wGNcCU7RTFt72ZGibJ99wrV0oTZ6oo07jL8bslxlEXRz3 a2832E1o7UvOOhNLnLOrNmVQzKn+0OwRxhHSgW2Rc/n4G6OpMEVP1klwPrNNhZciE5Pw jvYuYoEa/vUxiYlI1BCGZXRI2bNylxMA71yYcm6IQBaGAh7sDbhgLnkBWDnMIh56ypCv J86A==
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:organization :message-id:date:user-agent:mime-version:in-reply-to :content-language:content-transfer-encoding; bh=layFOthoU0bqp2x63BAeIQLsVbdLtAF5fO7oDLZQM9M=; b=Pe7M2CGWWfsht0GBuR0HI+HmN2Rj6NRUocrs8AtJnTzrhqMcbo8+50+kZibrlzrfCN cpV8QuVTgMKxQQngpNJUmI53E9HAVkinv4QFBDvCG9PtVhJNAHNM+r5rBzHaFNz6e/bz g+6NKfwwBwt9FQ4nXLBOy1Akw54smu3Je6gWWC43kZ2zrYyQ68lyFDwycqBC7xsLCRBp XF6GNN7YNnkGWnKo5RhlnvZyq3HliPMPD7I65rEJ6ozayqBPPRDTk2y5rv25xFYibdWm Vo0YkbdhBoism8ZZEr0/EzvBbSSsk7zX6lWxWKfUnmzmnol2WkHlETHfjiQIci1ZEGDW lGrA==
X-Gm-Message-State: AJaThX6+TdbLpCGfNlLW2NjoYo2md4ah8mP9Wk7GGYAiTt0fT1wkZQJ1 ocGd4fqnRhUIkjcnpLPLylhujw==
X-Google-Smtp-Source: AGs4zMZzuEvxI76hS5ztefHbeRqcpJyxGQj9O9fE6W+aVA3m45AgIT9F74R3WbPBd1Ermj3IiWsmNQ==
X-Received: by 10.36.178.78 with SMTP id h14mr5346337iti.107.1510906519878; Fri, 17 Nov 2017 00:15:19 -0800 (PST)
Received: from [172.16.132.82] ([101.100.166.3]) by smtp.gmail.com with ESMTPSA id t69sm1852866itt.37.2017.11.17.00.15.17 for <ipv6@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 17 Nov 2017 00:15:18 -0800 (PST)
Subject: Re: Fwd: New Version Notification for draft-hinden-ipv4flag-00.txt
To: ipv6@ietf.org
References: <151090059151.22321.3357672601322845792.idtracker@ietfa.amsl.com> <E838C63E-7612-4AA4-9375-854C184D699E@gmail.com> <4393db44-6427-5905-c3b4-60a546f88807@gont.com.ar>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <3814984e-4016-6574-b9cc-c961e939b57c@gmail.com>
Date: Fri, 17 Nov 2017 21:15:23 +1300
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0
MIME-Version: 1.0
In-Reply-To: <4393db44-6427-5905-c3b4-60a546f88807@gont.com.ar>
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/nZq20G_60c-7DD2pFovC6_48F80>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.22
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: Fri, 17 Nov 2017 08:15:23 -0000

On 17/11/2017 20:57, Fernando Gont wrote:
> HI, BOb,
> 
> Comments/questions:
> 
> * How about the case in which a user employs an IPv4-only printer on an
> IPv6-only network?

That question makes my head hurt. Why would you configure the flag =1 on
such a network?

> 
> * Does this document imply that IPv6 is bootstrapped first than, or in
> parallel of, IPv4?

First. Maybe we need to state that.

> 
> * If IPv4-has already been bootstrapped, would 4=1 still cause the node
> to disable IPv4?

There is a cunning "should not" in the text to cover corner cases. But
we probably need to discuss the corner cases anyway.

> 
> * If 4=1, but later 4=0, shuld that transition of the 4 bit trigger IPv4
> configuration?

Yes, we need to say something about that - linked to router lifetimes, I
think.

me -> airport shortly.

   Brian
> 
> 
> * Sec cons: see RFC7113 -- it seems that still the current state of
> affairs for many implementations (unfortunately).
> 
> 
> Thanks!
> 
> Cheers,
> Fernando
> 
> 
> 
> 
> On 11/17/2017 02:42 PM, Bob Hinden wrote:
>> Hi,
>>
>> Brian and I took a cut a defining an IPv4 Availability Flag for IPv6 ND
>> Router Advertisements.  From the Introduction:
>>
>>    Hosts that support IPv4 and IPv6, usually called dual stack hosts,
>>    need to work on IPv6 only networks.  That is, a link where there are
>>    no IPv4 routers and/or IPv4 services.  Monitoring of IPv6-only
>>    networks, for example at the IETF 100 meeting in Singapore, shows
>>    that current dual stack hosts will create local auto-configured IPv4
>>    addresses and attempt to reach IPv4 services.  A mechanism is needed
>>    to inform hosts that there is no IPv4 support and that they should
>>    turn off IPv4.
>>
>>    Because there is no IPv4 support on these links, the only way to
>>    notify the dual stack hosts on the link is to use an IPv6 mechanism.
>>    An active notification will be much more robust than attempting to
>>    deduce this state by the lack of IPv4 responses or traffic.
>>
>>    IPv4-only hosts, and dual-stack hosts that do not recognize the new
>>    flag, will continue to attempt IPv4 operations, in particular IPv4
>>    discovery protocols typically sent as link-layer broadcasts.  This
>>    legacy traffic cannot be prevented by any IPv6 mechanism.  The value
>>    of the new flag is limited to dual-stack hosts that recognize it.
>>
>> We were originally thinking it would be an April 1 submission, but after
>> reading the discussion on the IPv6 list, we decided it makes sense as a
>> real submission :-)
>>
>> Please review and comment.
>>
>> Thanks,
>> Bob and Brian
>>
>>
>>> Begin forwarded message:
>>>
>>> *From: *internet-drafts@ietf.org <mailto:internet-drafts@ietf.org>
>>> *Subject: **New Version Notification for draft-hinden-ipv4flag-00.txt*
>>> *Date: *November 17, 2017 at 2:36:31 PM GMT+8
>>> *To: *"Robert M. Hinden" <bob.hinden@gmail.com
>>> <mailto:bob.hinden@gmail.com>>, "Robert Hinden" <bob.hinden@gmail.com
>>> <mailto:bob.hinden@gmail.com>>, "Brian Carpenter"
>>> <brian.e.carpenter@gmail.com <mailto:brian.e.carpenter@gmail.com>>
>>>
>>>
>>> A new version of I-D, draft-hinden-ipv4flag-00.txt
>>> has been successfully submitted by Robert M. Hinden and posted to the
>>> IETF repository.
>>>
>>> Name:draft-hinden-ipv4flag
>>> Revision:00
>>> Title:IPv6 Router Advertisement IPv4 Availability Flag
>>> Document date:2017-11-17
>>> Group:Individual Submission
>>> Pages:5
>>> URL:
>>>            https://www.ietf.org/internet-drafts/draft-hinden-ipv4flag-00.txt
>>> Status:         https://datatracker.ietf.org/doc/draft-hinden-ipv4flag/
>>> Htmlized:       https://tools.ietf.org/html/draft-hinden-ipv4flag-00
>>> Htmlized:
>>>       https://datatracker.ietf.org/doc/html/draft-hinden-ipv4flag-00
>>>
>>>
>>> Abstract:
>>>   This document specifies a Router Advertisement Flag to indicate that
>>>   there is no IPv4 service on the advertising router.  This document
>>>   updates RFC5175.
>>>
>>>
>>>
>>>
>>> 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
>>> <http://tools.ietf.org>;.
>>>
>>> The IETF Secretariat
>>>
>>
>>
>>
>> --------------------------------------------------------------------
>> IETF IPv6 working group mailing list
>> ipv6@ietf.org
>> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
>> --------------------------------------------------------------------
>>
> 
>