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

Bob Hinden <bob.hinden@gmail.com> Fri, 17 November 2017 08:17 UTC

Return-Path: <bob.hinden@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 BE393126E01 for <ipv6@ietfa.amsl.com>; Fri, 17 Nov 2017 00:17:51 -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 TH3A_6V9dR6X for <ipv6@ietfa.amsl.com>; Fri, 17 Nov 2017 00:17:49 -0800 (PST)
Received: from mail-wm0-x231.google.com (mail-wm0-x231.google.com [IPv6:2a00:1450:400c:c09::231]) (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 1E7A7124319 for <ipv6@ietf.org>; Fri, 17 Nov 2017 00:17:49 -0800 (PST)
Received: by mail-wm0-x231.google.com with SMTP id y80so4719586wmd.0 for <ipv6@ietf.org>; Fri, 17 Nov 2017 00:17:49 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=30iuZU4tM4zO09liMG4Kw5MrS7jrHEB5BYIj8AWQwnc=; b=cbe/C7S88IVMXTNWVJkOInQDXlQXCmy9zIEEiFa9tebMAp0/FgZDOuBkBiJBdBoHr3 SDCwdMrRkfu2z7f+Yw72IRAG7qYJzdMwl3ab73Uf1jxCiQTRe/HCBO5ohOBdAc4DMgtR i90JoP4Ua3bZkMwTcrM+a0fCInmIFCmnjLSjoxYzSNAhg4ohEsqf826yIoa/kzVF7dH9 h4CAkBDMHceVIm1C8jsyMDzyhOFaaSJn7DFQph5iSeyUvezw7H8aOcbUQ070rN0YEK/i sOMHtrbzDOk6pnIR98GKoUFgNE1I3pBgdMHWVo1ZWWmMDSya5z97C43VGZg0nQ6fM6TE q6QQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=30iuZU4tM4zO09liMG4Kw5MrS7jrHEB5BYIj8AWQwnc=; b=VZoEFs2MoFidLmaE/CSNTynbKMRZggHdAZbouYxndnGLxkDA787VDWXagu4lzztoHg Doz22AM+imG0eKbgrHsbBgZmQGVnofPWBMqGY8et/2IesM3wipDzvm6lU2Ik6/8hELJ5 c5t7zBCUiDXvUks2SQ7RIuD8MdBPCbTxGStY1WNfTTRRKYbq0gLlaJ1iBdNAdxEezk+7 Bx76hWOX3a3D9F1ZnqF0SgdAdLX5smY2M93J8ziENKizQ8rb4KqCVVKhR10vzLpW2MxJ ckTXJRpZUI3fN3q8U6sgyoPcMKm+Wok6AkpsYbYQeSYAJbgAu5dyIfLepXF49hUne8E2 KZHQ==
X-Gm-Message-State: AJaThX7ywIKziKtQa3Hf6XHt10vRmK9QJeVhpOnGGpi82OyzKki92xMq 8dZIBB8R7bOY97L1lrKRD85TV1jU
X-Google-Smtp-Source: AGs4zMZeO9iZtec2GvqauDCoPTc95RLvmqQNl4PLRhIoWpESbdeAQKftg6vfyof6gkazme+oJsx0qQ==
X-Received: by 10.28.18.1 with SMTP id 1mr3917294wms.88.1510906667575; Fri, 17 Nov 2017 00:17:47 -0800 (PST)
Received: from ?IPv6:2001:67c:1232:144:47d:205e:4d5:c349? ([2001:67c:1232:144:47d:205e:4d5:c349]) by smtp.gmail.com with ESMTPSA id c22sm133257wme.2.2017.11.17.00.17.44 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 17 Nov 2017 00:17:46 -0800 (PST)
From: Bob Hinden <bob.hinden@gmail.com>
Message-Id: <0F60023D-9EDA-4C5D-9ABB-27BEAD294780@gmail.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_82561F55-6C62-4C17-A999-EF4C500A53CD"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: New Version Notification for draft-hinden-ipv4flag-00.txt
Date: Fri, 17 Nov 2017 16:17:40 +0800
In-Reply-To: <4393db44-6427-5905-c3b4-60a546f88807@gont.com.ar>
Cc: Bob Hinden <bob.hinden@gmail.com>, IPv6 List <ipv6@ietf.org>
To: Fernando Gont <fernando@gont.com.ar>
References: <151090059151.22321.3357672601322845792.idtracker@ietfa.amsl.com> <E838C63E-7612-4AA4-9375-854C184D699E@gmail.com> <4393db44-6427-5905-c3b4-60a546f88807@gont.com.ar>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/aOVPQLaCrMdOJSDfsRFIzNmPqQ8>
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:17:52 -0000

Fernando,

> On Nov 17, 2017, at 3:57 PM, Fernando Gont <fernando@gont.com.ar>; wrote:
> 
> HI, BOb,
> 
> Comments/questions:
> 
> * How about the case in which a user employs an IPv4-only printer on an
> IPv6-only network?

That’s not an IPv6-only network.  If the user or networks wants to use IPv4, then it shouldn’t set Flag=1.

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

The flag is to tell the host to not use IPv4.  Once the host see the Flag=1, it should stop sending IPv4.

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

Then start using IPv4 again.

> 
> * Sec cons: see RFC7113 -- it seems that still the current state of
> affairs for many implementations (unfortunately).

OK, thanks.

Bob

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