Re: Adoption call for <draft-hinden-ipv4flag-03>

David Schinazi <dschinazi@apple.com> Thu, 22 March 2018 18:00 UTC

Return-Path: <dschinazi@apple.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 4151F1200A0 for <ipv6@ietfa.amsl.com>; Thu, 22 Mar 2018 11:00:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.311
X-Spam-Level:
X-Spam-Status: No, score=-4.311 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=apple.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 zXzKoHJwZ-GX for <ipv6@ietfa.amsl.com>; Thu, 22 Mar 2018 11:00:19 -0700 (PDT)
Received: from mail-in3.euro.apple.com (mail-in3.euro.apple.com [17.72.148.13]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5B5D5126D45 for <ipv6@ietf.org>; Thu, 22 Mar 2018 11:00:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; d=apple.com; s=mailout2048s; c=relaxed/simple; q=dns/txt; i=@apple.com; t=1521741616; x=2385655216; h=From:Sender:Reply-To:Subject:Date:Message-id:To:Cc:MIME-version:Content-type: Content-transfer-encoding:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-reply-to:References:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=1rqHewpZblAX6vfh7dYbsHvI0rMXcGdgUsTUC2WlgKE=; b=QJYPsuXSeZkA0w4O3nPZC6QKbRKNvmHXGlub9CN8egCDU0UmQvvgROU7TD1TMBcd fwCaet5cAc8BwMUxEEUw/iFhdNSwYIQR+MuXkCvDfmH2ZNlz9t83kisPsqqUx6sn Zq33baaHo9cXOqrtKsDvBlmJ7VZnIGDZgp8ovacQrJ35CX18WserXHfNAv+LVh6Z RSjoYen4KcBChjltTdpXwxyw9uDET5ciaFFHy/dT7BcSVa+3eUwKoUr8lY4TW6+i e4JPrQWK3EUkE2wAVNukWr9hwWpJ2WwhdzjFbwD/zpo+YnrIWR3fh/1XCwIbCgYu 9hI1CX/k85hqJ164/A7Chw==;
Received: from relay2.euro.apple.com ( [17.66.55.12]) (using TLS with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mail-in3.euro.apple.com (Apple Secure Mail Relay) with SMTP id FD.2C.06134.03FE3BA5; Thu, 22 Mar 2018 18:00:16 +0000 (GMT)
X-AuditID: 1148940d-d1bf19e0000017f6-45-5ab3ef30d552
Received: from crk-mmpp-sz03.euro.apple.com ( [17.66.12.165]) (using TLS with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by relay2.euro.apple.com (Symantec Mail Security) with SMTP id C5.62.16087.03FE3BA5; Thu, 22 Mar 2018 18:00:16 +0000 (GMT)
MIME-version: 1.0
Content-type: text/plain; charset="utf-8"
Received: from [17.235.239.61] (unknown [17.235.239.61]) by crk-mmpp-sz03.euro.apple.com (Oracle Communications Messaging Server 8.0.2.2.20180130 64bit (built Jan 30 2018)) with ESMTPSA id <0P6000IW77CFNA30@crk-mmpp-sz03.euro.apple.com>; Thu, 22 Mar 2018 18:00:16 +0000 (GMT)
Sender: dschinazi@apple.com
Subject: Re: Adoption call for <draft-hinden-ipv4flag-03>
From: David Schinazi <dschinazi@apple.com>
In-reply-to: <D771C20B-83E1-4AF8-A2C0-DA44A45C4004@employees.org>
Date: Thu, 22 Mar 2018 18:00:14 +0000
Cc: 6man WG <ipv6@ietf.org>, 6man-chairs@ietf.org
Content-transfer-encoding: quoted-printable
Message-id: <E8E0AB30-371F-45D1-9140-1A50C26237ED@apple.com>
References: <562A6850-000D-4C39-BE50-1DB6C759D6AD@employees.org> <D771C20B-83E1-4AF8-A2C0-DA44A45C4004@employees.org>
To: Ole Troan <otroan@employees.org>
X-Mailer: Apple Mail (2.3445.5.20)
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrDLMWRmVeSWpSXmKPExsUi6GTOo2vwfnOUwbF5aha7p0xjs3h59j2T xeS2FWwOzB4Hj31k9Fiy5CdTAFMUl01Kak5mWWqRvl0CV8ajY0vZCi7yV/xrnczewPiZp4uR k0NCwERi0YxXrF2MXBxCAouZJFou/mKESZz5d4wJIrGCSWLm7icsIAleAUGJH5PvAdkcHMwC 6hJTpuRC1Mxmklj8uwGsRlhAWqLrwl1WCNtSYuaKB0wg9WwCWhIH1hiBmJwCjhK3urhBKlgE VCX2X5/LDjHRUOLnbHuQMLOAtsSTdxdYQcK8AjYSi755goSFBMolXr24yw5iiwioSJyf9g7q YCWJ6d9vs4EcIyEwgU3i282HTBMYhWchuXkWws2zkGxYwMi8ilE8NzEzRzczz1gvtbQoXy+x oCAnVS85P3cTIyjMPabw7mC8ftDwEKMAB6MSD++Ck5ujhFgTy4orcw8xSnAwK4nw5q8FCvGm JFZWpRblxxeV5qQWH2KU5mBREudNeewXJSSQnliSmp2aWpBaBJNl4uCUamCsNPIQC/def8Rs zfZtNz498N8QFf9Fw7aUrz/v+qp7VeXXOMImrYrw//Ho7M6kPIfZ4eErnd0TCnetmnt2q4/J 2ybO/OlSMX8MNrFoThWveR4WOXGX/X3DPbt7+JeUSfKLqb+dLSJidW7arJd/GQuduzJjxJfd vrGU8cYbe+n9MT3SexpE88uVWIozEg21mIuKEwGpyXTybwIAAA==
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrCLMWRmVeSWpSXmKPExsUi6MSzVNfg/eYog1VbVSx2T5nGZvHy7Hsm i8ltK9gcmD0OHvvI6LFkyU+mAKYoLpuU1JzMstQifbsEroxHx5ayFVzkr/jXOpm9gfEzTxcj J4eEgInEmX/HmLoYuTiEBFYwSczc/YQFJMErICjxY/I9IJuDg1lAXWLKlFyImtlMEot/N4DV CAtIS3RduMsKYVtKzFzxgAmknk1AS+LAGiMQk1PAUeJWFzdIBYuAqsT+63PZISYaSvycbQ8S ZhbQlnjy7gIrSJhXwEZi0TdPkLCQQLnEqxd32UFsEQEVifPT3jFCHKwkMf37bbYJjAKzkJw5 C+HMWUiGLmBkXsUoWpSak1hppJdaWpSvl1hQkJOql5yfu4kRHJbmPDsYXx00PMQowMGoxMNb /W5zlBBrYllxZe4hRgkOZiUR3vy1QCHelMTKqtSi/Pii0pzU4kOM0hwsSuK8tr78UUIC6Ykl qdmpqQWpRTBZJg5OqQbGujezltWdrLj8bGIS58FDsz3nCAcmXpTcFPXWfbWv5I8zR06UfanN vdwQor1C2PhlIPfyqd/dzmq3V0WXFh/Z0CSutfLYk8zfcx1NaoVi/qkvCW+6Gmf1Vsrxu8Ct 3bMuZIrI2L5T4ru/WSQqc0f9PuffmoH3ir8pxfY+sfYPO3nY9AfHhR5pJZbijERDLeai4kQA oxb/nkcCAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/aPrwF0498XVh7HMUWnxZgKzWGfY>
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: Thu, 22 Mar 2018 18:00:22 -0000

I do not support adoption of draft-hinden-ipv4flag as it currently stands.
It's still unclear to me what actual problems this draft is trying to solve, and that an RA flag is the right solution.
For example, perhaps deprecating RFC 3927 is another way to solve some of the problems described in the introduction.

Thanks,
David Schinazi


> On Mar 22, 2018, at 17:37, Ole Troan <otroan@employees.org> wrote:
> 
> I would love to hear from host implementers. If they would implement support for this flag.
> 
> Best regards,
> Ole
> 
>> On 22 Mar 2018, at 16:47, Ole Troan <otroan@employees.org> wrote:
>> 
>> This message starts a two week 6MAN call on adopting:
>> 
>>    Title     : IPv6 Router Advertisement IPv4 Unavailable Flag
>>    Authors   : R. Hinden, B. Carpenter
>>    Filename  : draft-hinden-ipv4flag-03
>>    Pages     : 9
>>    Date      : 2018-03-02
>> 
>>    https://datatracker.ietf.org/doc/draft-hinden-ipv4flag/
>> 
>> as a working group item. Substantive comments and statements of support
>> for adopting this document should be directed to the mailing
>> list. Editorial suggestions can be sent to the authors.  This adoption
>> call will end on April 5th, 2018.
>> 
>> See also the gap analysis from sunset4 on disabling IPv4:
>> https://tools.ietf.org/html/draft-ietf-sunset4-gapanalysis-09#section-3
>> 
>> Regards,
>> 
>> Ole Trøan
>> --------------------------------------------------------------------
>> IETF IPv6 working group mailing list
>> ipv6@ietf.org
>> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
>> --------------------------------------------------------------------
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------