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

Simon Perreault <sperreault@jive.com> Fri, 17 November 2017 14:00 UTC

Return-Path: <sperreault@jive.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 7D0CA126CB6 for <ipv6@ietfa.amsl.com>; Fri, 17 Nov 2017 06:00:29 -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, HTML_MESSAGE=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=jive.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 UBWFI34pWrTk for <ipv6@ietfa.amsl.com>; Fri, 17 Nov 2017 06:00:26 -0800 (PST)
Received: from mail-it0-x233.google.com (mail-it0-x233.google.com [IPv6:2607:f8b0:4001:c0b::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 9D866120727 for <ipv6@ietf.org>; Fri, 17 Nov 2017 06:00:26 -0800 (PST)
Received: by mail-it0-x233.google.com with SMTP id b5so4120754itc.3 for <ipv6@ietf.org>; Fri, 17 Nov 2017 06:00:26 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=jive.com; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=n9bFQFcKLgHL7pU4GlTuSIhOyEa49tXmShXehhf+dRo=; b=rbPubWHr2HsX2zNHfCP3GUn93Y/u71QvTsqbGbRT99esOoLhSZn6x3JgYaXbcGCZbl bRr2y3Pj64YY6crS1EqpakKvIHO/W9AS07Thl9JSU4qm6xC3tSDJq5jmoijCb09YyXQd 4BntjzXMigSvXh7aBU1759cjHHAMfZfjqlL53/ggQeJ7iybITWAZNhuwP62FVjzHItxe ovG4vJyYyyj8l3ROfcUHJp7iFvjlFXxuMPqdItBG7UEZPV9Ke4aL249BnkW/lrOmycOU 0XGuZkCEVkDmife8GPctK8wyfahHIwoR7wPBSVxyEazIiT0KpUCSCYNDXEDegW8B9/7g rqBg==
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=n9bFQFcKLgHL7pU4GlTuSIhOyEa49tXmShXehhf+dRo=; b=LQ50ng8uWCFLs54njYegLqtPPMSgjCZwyqSy8044yDxDWAslcw/5JJ3hFfX6reXmW5 6/ND8VKbtvStoVHoZ6d+GavCdirY28GEoJu+kKMg/Zy2Itbn84VljY/qL7ayQHPf5Yqh HdsPR8MrKKN5wvBKgwvabLBSDDq2cYqXKmGce5bphUkmgpSu/E/P5FT1nSAA7CEK1Ibd K8cwaZ9fKsLW7H1wafqxjtre6f5MrZVa7EXvesodDcPJRxcy37eVMc2DtLekL/1BMxpj sECLgEz96Q+COFDDT7mVO5a2O1sXzgnyrJs6ATTyVG7gNNTk+qtFW5G6inbksWerQxBK c2RA==
X-Gm-Message-State: AJaThX4vnjcfKqc7j1ZiCHLzYtLcs19F04k6HFGbS0GACJj4sBn+8b4U rIVMGaKrSniH2nXVOSaJp83XmaNxlkuWa2HA29bZ6Q==
X-Google-Smtp-Source: AGs4zMb51seINn1WMdEt08BVasA25cGZp9SLr8Lzrx4PGtegCZCW1pxYIxLZk/QCP9umGcvNqe8g6i4r8us5oqtwBVc=
X-Received: by 10.36.23.68 with SMTP id 65mr6125476ith.62.1510927225907; Fri, 17 Nov 2017 06:00:25 -0800 (PST)
MIME-Version: 1.0
Received: by 10.107.146.193 with HTTP; Fri, 17 Nov 2017 06:00:05 -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: Simon Perreault <sperreault@jive.com>
Date: Fri, 17 Nov 2017 09:00:05 -0500
Message-ID: <CANO7kWCE08tjXFFeNpiWBV=ih1MXdJRp1m_8cNxdv=uSYksH9A@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: multipart/alternative; boundary="001a11439010953220055e2e2871"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/XqWGkLlG7RyX2bEB-PM60s2xP64>
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 14:00:29 -0000

Hi Bob,

How is this different from
https://tools.ietf.org/html/draft-ietf-sunset4-noipv4-01 ?

Thanks,
Simon

2017-11-17 1:42 GMT-05:00 Bob Hinden <bob.hinden@gmail.com>;:

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