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

Fernando Gont <fernando@gont.com.ar> Fri, 17 November 2017 07:56 UTC

Return-Path: <fernando@gont.com.ar>
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 B6A141243F6 for <ipv6@ietfa.amsl.com>; Thu, 16 Nov 2017 23:56:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham 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 juB8r57FYPep for <ipv6@ietfa.amsl.com>; Thu, 16 Nov 2017 23:56:08 -0800 (PST)
Received: from fgont.go6lab.si (fgont.go6lab.si [91.239.96.14]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D9376126557 for <ipv6@ietf.org>; Thu, 16 Nov 2017 23:56:07 -0800 (PST)
Received: from [IPv6:2001:67c:1232:144:9ac:99fc:64d1:1909] (unknown [IPv6:2001:67c:1232:144:9ac:99fc:64d1:1909]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by fgont.go6lab.si (Postfix) with ESMTPSA id 871A880197; Fri, 17 Nov 2017 08:56:05 +0100 (CET)
Subject: Re: Fwd: New Version Notification for draft-hinden-ipv4flag-00.txt
To: Bob Hinden <bob.hinden@gmail.com>, IPv6 List <ipv6@ietf.org>
References: <151090059151.22321.3357672601322845792.idtracker@ietfa.amsl.com> <E838C63E-7612-4AA4-9375-854C184D699E@gmail.com>
From: Fernando Gont <fernando@gont.com.ar>
Message-ID: <4393db44-6427-5905-c3b4-60a546f88807@gont.com.ar>
Date: Fri, 17 Nov 2017 15:57:52 +0800
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0
MIME-Version: 1.0
In-Reply-To: <E838C63E-7612-4AA4-9375-854C184D699E@gmail.com>
Content-Type: text/plain; charset=windows-1252
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/CBdCnOu_Y6ZF59MhhFRgi2ZE5Q0>
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 07:56:11 -0000

HI, BOb,

Comments/questions:

* How about the case in which a user employs an IPv4-only printer on an
IPv6-only network?

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

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

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


* 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
> --------------------------------------------------------------------
> 


-- 
Fernando Gont
e-mail: fernando@gont.com.ar || fgont@si6networks.com
PGP Fingerprint: 7809 84F5 322E 45C7 F1C9 3945 96EE A9EF D076 FFF1