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

Jen Linkova <furry13@gmail.com> Sat, 18 November 2017 14:40 UTC

Return-Path: <furry13@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 B9A14127077 for <ipv6@ietfa.amsl.com>; Sat, 18 Nov 2017 06:40:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.55
X-Spam-Level:
X-Spam-Status: No, score=-0.55 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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 jNQP5beG1MaP for <ipv6@ietfa.amsl.com>; Sat, 18 Nov 2017 06:40:05 -0800 (PST)
Received: from mail-lf0-x233.google.com (mail-lf0-x233.google.com [IPv6:2a00:1450:4010:c07::233]) (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 DF6E4120726 for <ipv6@ietf.org>; Sat, 18 Nov 2017 06:40:04 -0800 (PST)
Received: by mail-lf0-x233.google.com with SMTP id f134so5623552lfg.8 for <ipv6@ietf.org>; Sat, 18 Nov 2017 06:40:04 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=Z8asHcJs1gsml2FazpHF8rrKqy2r5WpNBHFsz7Ie+xo=; b=ErtYMh3JU8LFnM9p3pUdNz/TWrn3Dad2LEs0U519Bjvq1ve8uvqkEJlw7P8o5JBiMZ tXUA9OA677irNXjE8XCiHUbXmmcBlH8arJPKGkjpQpv+nFgjOfreqkZoMYWL9GOvSRWM OEXQE+UuqHdNCx5eja4FEvudcBHzXfhht9tJbZAKhUecwFz6+PiTgpkPEcm1btxQ/wCA EydJB7a4n65L0oZwUG88lKmHm+lySP1z7y2WmvScsH1x01hWcD3mzeDksA/mamFwF9uk oH+wsacWWZQudROE+lCIOf71ZcAcZyr5pqiIQgef8Fh8mwSNEWiYkwWyMN9Q1DFckhir ClOg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=Z8asHcJs1gsml2FazpHF8rrKqy2r5WpNBHFsz7Ie+xo=; b=F63X3042fMkyMKnkIeeM116kNUR94jk2YHwvsODwOyHJ04eimGybpxaSU+4tuWwH4/ 7UKTB31XKT5Fx1U7yMEG8lDC3YEu+05uZqlGfEXqSjcyz9bZwPg5HBeSZXi3Hw8euaho +4q45KrkqrkgyUOmxnMBn1wJ3+4XSVU+9/vckz15E/wmJXgL36EOplDWFHLUH7BU5gMa pBYHWvdKAIm+8q6oRr1UAFAOuS5TTRvMweraOFTYEcvi06ck1gCc6y97Fzz5dteqQGgd 0GM48bEI2T5jGLAxFH5KRGLwKjsE9QcYvyImHf60sVH7zs4X1fkC+vgIcAiQbtyseFqq 1g2A==
X-Gm-Message-State: AJaThX6fNiclpBNQkxjtmLKdU9zMF8tN2KjcjNrZpsf9iKrxI33JSU4D C/42bE6ecxHs8H5qGLSq5P2z7Q165MLoksDS+wE=
X-Google-Smtp-Source: AGs4zMYoGFBBKkL5pf0NJiTr/I6q+HjK5pNCOwfckGxRJeSlWyhhScPIj+ghtbCjFwx88CAnen1AlFpeCueT6wS2QBs=
X-Received: by 10.25.26.143 with SMTP id a137mr1969044lfa.105.1511016002960; Sat, 18 Nov 2017 06:40:02 -0800 (PST)
MIME-Version: 1.0
Received: by 10.25.205.2 with HTTP; Sat, 18 Nov 2017 06:39:42 -0800 (PST)
In-Reply-To: <E838C63E-7612-4AA4-9375-854C184D699E@gmail.com>
References: <151090059151.22321.3357672601322845792.idtracker@ietfa.amsl.com> <E838C63E-7612-4AA4-9375-854C184D699E@gmail.com>
From: Jen Linkova <furry13@gmail.com>
Date: Sun, 19 Nov 2017 01:39:42 +1100
Message-ID: <CAFU7BAQKoWPcEFQZgU3k_d0gUL4en6d2pyNq1V4RMNZ6HrSG8w@mail.gmail.com>
Subject: Re: New Version Notification for draft-hinden-ipv4flag-00.txt
To: Bob Hinden <bob.hinden@gmail.com>
Cc: IPv6 List <ipv6@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/4tUJlhFTr2n576IwTo-Kue8mC2A>
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: Sat, 18 Nov 2017 14:40:07 -0000

Hi Bob,

To be honest I'm not convinced that there is a real problem to be solved..
The draft says

'A mechanism is needed  to inform hosts that there is no IPv4 support
and that they should turn off IPv4.'
and it would be great to have more detailed problem statement IMHO...

It looks to me that when you are saying 'there is no IPv4 support on a
link' you mean 'a router does not provide IPv4 connectivity'.  However
it still might be
IPv4 connectivity within the given broadcast domain and the router has
nothing to do with it.

If the problem is 'IPv4 broadcast noise on the link' then it should be
solved on L2 level and the network should not switch ethertype 0x0800.
If the problem is 'all those noisy DHCPv4 requests the first-hop
router has to drop because DHCP relay is not configured' then the
router interface should not accept IPv4 packets at all, problem
solved.

Also it's not clear what a host is supposed to do if it'd been
receiving RAs with that flag set 0 and at some point subsequent RAs
started to arrive with that bit set to 1...
Shall the host stop all IPv4 operations attempts? Basically how that
information could be updated?


On Fri, Nov 17, 2017 at 5:42 PM, Bob Hinden <bob.hinden@gmail.com>; 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
> 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>;, "Robert Hinden"
> <bob.hinden@gmail.com>;, "Brian Carpenter" <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.
>
> The IETF Secretariat
>
>
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>



-- 
SY, Jen Linkova aka Furry