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

JORDI PALET MARTINEZ <jordi.palet@consulintel.es> Fri, 17 November 2017 07:21 UTC

Return-Path: <prvs=1494ff0e50=jordi.palet@consulintel.es>
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 DD3A712773A for <ipv6@ietfa.amsl.com>; Thu, 16 Nov 2017 23:21:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=consulintel.es; domainkeys=pass (1024-bit key) header.from=jordi.palet@consulintel.es header.d=consulintel.es
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 NkG_8aIayg6S for <ipv6@ietfa.amsl.com>; Thu, 16 Nov 2017 23:21:55 -0800 (PST)
Received: from mail.consulintel.es (mail.consulintel.es [217.126.185.215]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8B85912741D for <ipv6@ietf.org>; Thu, 16 Nov 2017 23:21:55 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=consulintel.es; s=MDaemon; t=1510903313; x=1511508113; q=dns/txt; h=DomainKey-Signature: Received:User-Agent:Date:Subject:From:To:Message-ID:Thread-Topic: References:In-Reply-To:Mime-version:Content-type: Content-transfer-encoding:Reply-To; bh=a0nz6j/lcLwD0649h10xv0CkL fKJGWvtgCwZTocfM5Y=; b=QTxOlrJKyAOdFK0TAFlPGg/TMhxMHm3XlfKNk+Dy3 S/3Ajcl0+o6BpVBTZQBTAxnLUpHjx5/OCZrHFlGtKkyxTxaquDyGGyxUNgizspXG yBA7oEAsdxtFi1L1qbhXV5KWoJ42z6grsoRfT27TGLxV8JmtYwFJl+uPWmsV6u+B UM=
DomainKey-Signature: a=rsa-sha1; s=MDaemon; d=consulintel.es; c=simple; q=dns; h=from:message-id; b=UjTP3Qe77tbYvzXSLXDDFzhYo3Ty1ppbml6vJp2O93WAGSGQsDiZyKQPVFYr HhbZ+7DVsbMMc5pi76wKF71f54o8EiA8iOTkXTbNCEyHoJOGV82qxbhNB WFY+3r+Zdr6VpM3n92CsQfUyo9i5tmckR0qMlXOWjmHQWrSQPj+mUA=;
X-MDAV-Processed: mail.consulintel.es, Fri, 17 Nov 2017 08:21:53 +0100
X-Spam-Processed: mail.consulintel.es, Fri, 17 Nov 2017 08:21:53 +0100
Received: from [172.20.60.6] by mail.consulintel.es (MDaemon PRO v11.0.3) with ESMTP id md50005626521.msg for <ipv6@ietf.org>; Fri, 17 Nov 2017 08:21:53 +0100
X-MDOP-RefID: re=0.000,fgs=0 (_st=1 _vt=0 _iwf=0)
X-Authenticated-Sender: jordi.palet@consulintel.es
X-HashCash: 1:20:171117:md50005626521::O2YVM3hmRo0s4/cS:00001bl8
X-Return-Path: prvs=1494ff0e50=jordi.palet@consulintel.es
X-Envelope-From: jordi.palet@consulintel.es
X-MDaemon-Deliver-To: ipv6@ietf.org
User-Agent: Microsoft-MacOutlook/f.27.0.171010
Date: Fri, 17 Nov 2017 15:21:42 +0800
Subject: Re: New Version Notification for draft-hinden-ipv4flag-00.txt
From: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
To: IPv6 List <ipv6@ietf.org>
Message-ID: <F6CEDD51-CA7E-45C6-BB79-6309F0B601F1@consulintel.es>
Thread-Topic: New Version Notification for draft-hinden-ipv4flag-00.txt
References: <151090059151.22321.3357672601322845792.idtracker@ietfa.amsl.com> <E838C63E-7612-4AA4-9375-854C184D699E@gmail.com>
In-Reply-To: <E838C63E-7612-4AA4-9375-854C184D699E@gmail.com>
Mime-version: 1.0
Content-type: text/plain; charset="UTF-8"
Content-transfer-encoding: 7bit
Reply-To: jordi.palet@consulintel.es
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/ZE_RMnVDZPuir0MvDopxK1d30XA>
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:21:58 -0000

At first sight, looks fine to me.

Regards,
Jordi
 

-----Mensaje original-----
De: ipv6 <ipv6-bounces@ietf.org>; en nombre de Bob Hinden <bob.hinden@gmail.com>;
Responder a: <bob.hinden@gmail.com>;
Fecha: viernes, 17 de noviembre de 2017, 14:42
Para: IPv6 List <ipv6@ietf.org>;
CC: Bob Hinden <bob.hinden@gmail.com>;
Asunto: Fwd: New Version Notification for draft-hinden-ipv4flag-00.txt

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



**********************************************
IPv4 is over
Are you ready for the new Internet ?
http://www.consulintel.es
The IPv6 Company

This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it.