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

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

Return-Path: <bob.hinden@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 041D2127843 for <ipv6@ietfa.amsl.com>; Thu, 16 Nov 2017 22:42:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.698
X-Spam-Status: No, score=-2.698 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, 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=gmail.com
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id yltAgPfaq-5S for <ipv6@ietfa.amsl.com>; Thu, 16 Nov 2017 22:42:10 -0800 (PST)
Received: from mail-wm0-x229.google.com (mail-wm0-x229.google.com [IPv6:2a00:1450:400c:c09::229]) (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 89FB21200C1 for <ipv6@ietf.org>; Thu, 16 Nov 2017 22:42:09 -0800 (PST)
Received: by mail-wm0-x229.google.com with SMTP id l8so4271360wmg.4 for <ipv6@ietf.org>; Thu, 16 Nov 2017 22:42:09 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:mime-version:subject:date:references:cc:to:message-id; bh=2xzu7updVFp2m19ZUBDfBA4O+t3Qg/XkffjKSYdFwXk=; b=N/SOsAjBzFUyCIZ1S7f7S0sLaCFvYBvXK4wh8kBr0MoI8wjVaixISxJgaJQIHC43Ef hpZdSN8/L82I2X6lJORSghwJnZDRBr5HKbkTOX+k6Q7CH+z89MIhdCx6HA6fb2dng2nU 1Xaam2P0j5+ICrbWXwojsQgJg+0sweatwXxdXXvvA+eRuxY/aiXbIBil5tPVu3mqbXi2 N3JxZU1XefDs7hRgRwmQ9h9cvKaFgaVShvUGVKk9JP8/3TM+KHeOXkHBGBOMAch126dC 2dqzd3xHgjPh9hv0lW1WOtZmbi3jIa6RTBh3Xw8EzHNiNMFanOs3BjT08apz7P9yBVdV AYxg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:mime-version:subject:date:references:cc:to :message-id; bh=2xzu7updVFp2m19ZUBDfBA4O+t3Qg/XkffjKSYdFwXk=; b=c+Qyx5LwsRT7EBUjCKh0B5IUzxfERwUiINgwBoO4XTYEs+AbdLcRlxVzU+3Mmk6fuM zPQw241Pr0kwIaE1kMAnWjM/pG+J5DA9kdZWjIs+n6BRhRqdPevKO7beWbLEh5CWVR7L 4UWtIcvRZZZcZpChteD/FVbulEBJjAts8FbYhPzPGijzo04jORD/+8O4a8TOsv5mFs7m IiA3U2THHsa6v4QoyK/Z1kwPwmMlcu7hsT4hn2ruSdcNO2v9EjYHLXNSo05kxAKRz8nz aVM4Kn5gi3jWAgbPCMcNfZZmkHcUgtfvgABiZQKSeVFLZxcTltXFpvNQjU6IBNOTIOYE wOEg==
X-Gm-Message-State: AJaThX4PWRd2d6WTPvwGXUIcqqFCHl3t4jxjXUDJmS8B+ZwAkf82J55u 642pwEzlMDfnh9uytxG1hDSZHE3+
X-Google-Smtp-Source: AGs4zMYrXyLb6tyAwrd+SPHe7VA9+R+vHlK9gpMIcLbenPJz9CIXQMSwo0+KSpjr5wiMe5sjtYowjQ==
X-Received: by with SMTP id x18mr5836373eda.4.1510900927794; Thu, 16 Nov 2017 22:42:07 -0800 (PST)
Received: from ?IPv6:2001:67c:1232:144:c8f6:2068:15f9:6113? ([2001:67c:1232:144:c8f6:2068:15f9:6113]) by smtp.gmail.com with ESMTPSA id j6sm1958040edj.58.2017. (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 16 Nov 2017 22:42:06 -0800 (PST)
From: Bob Hinden <bob.hinden@gmail.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_A7F2F96A-8770-41FC-A120-CDAFCDAD84D9"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Fwd: New Version Notification for draft-hinden-ipv4flag-00.txt
Date: Fri, 17 Nov 2017 14:42:03 +0800
References: <151090059151.22321.3357672601322845792.idtracker@ietfa.amsl.com>
Cc: Bob Hinden <bob.hinden@gmail.com>, Brian Carpenter <brian.e.carpenter@gmail.com>
To: IPv6 List <ipv6@ietf.org>
Message-Id: <E838C63E-7612-4AA4-9375-854C184D699E@gmail.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/aTIYDqLPmE_sHx_ycFOsSOLXmXQ>
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 06:42:13 -0000


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.

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>om>, "Robert Hinden" <bob.hinden@gmail.com>om>, "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