IETF Logo Mail Archive

Re: I-D Action: draft-ietf-6man-ipv6only-flag-03.txt

Job Snijders <job@ntt.net> Fri, 19 October 2018 12:35 UTC

Return-Path: <job@ntt.net>
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 1CCAF130E63 for <ipv6@ietfa.amsl.com>; Fri, 19 Oct 2018 05:35:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 T7BAkpr0A_HW for <ipv6@ietfa.amsl.com>; Fri, 19 Oct 2018 05:35:48 -0700 (PDT)
Received: from mail3.dllstx09.us.to.gin.ntt.net (mail3.dllstx09.us.to.gin.ntt.net [IPv6:2001:418:3ff:5::26]) (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 EC750127AC2 for <ipv6@ietf.org>; Fri, 19 Oct 2018 05:35:47 -0700 (PDT)
Received: by mail3.dllstx09.us.to.gin.ntt.net with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.90_1) (envelope-from <job@ntt.net>) id 1gDU0I-000EAK-HW (job@us.ntt.net) for ipv6@ietf.org; Fri, 19 Oct 2018 12:35:46 +0000
Received: by mail-ot1-f46.google.com with SMTP id l1so33006421otj.5 for <ipv6@ietf.org>; Fri, 19 Oct 2018 05:35:45 -0700 (PDT)
X-Gm-Message-State: ABuFfoj2VUuU8VrDg5c3dSRyeixWKIa7THhoN1sxtGOKDiOh2Za6QXUe 6XYgpacAM/YPjIzaHV4KkEeXqGL0AeGnaJfbbMl4LA==
X-Google-Smtp-Source: ACcGV60RUIguIjZjNIFv1dDXuTbmrvITJ8u4UTp4r6qGQZmhuFBdfj7YTGPlWltPGW4ehvfa4VQhiQVAPItg3did57Q=
X-Received: by 2002:a9d:193:: with SMTP id e19mr24005603ote.313.1539952545525; Fri, 19 Oct 2018 05:35:45 -0700 (PDT)
MIME-Version: 1.0
References: <153973137181.9473.10666616544238076833@ietfa.amsl.com> <092346e1-6350-e54e-e711-9c5ee6dc4e6b@gmail.com> <CAFU7BASO_ByzbanhLKnWV280O_fASd-8W+ujpj3sN6d2-whw2w@mail.gmail.com>
In-Reply-To: <CAFU7BASO_ByzbanhLKnWV280O_fASd-8W+ujpj3sN6d2-whw2w@mail.gmail.com>
From: Job Snijders <job@ntt.net>
Date: Fri, 19 Oct 2018 14:35:34 +0200
X-Gmail-Original-Message-ID: <CACWOCC-u7aAPwAOcixYvt2On=-o_8X25GhqdXTfA+tWRC1o2XA@mail.gmail.com>
Message-ID: <CACWOCC-u7aAPwAOcixYvt2On=-o_8X25GhqdXTfA+tWRC1o2XA@mail.gmail.com>
Subject: Re: I-D Action: draft-ietf-6man-ipv6only-flag-03.txt
To: 6man WG <ipv6@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000072870d057894242b"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/Lc6IsDgtlGCPtMF0leLDAaCQqbw>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.29
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, 19 Oct 2018 12:35:50 -0000

I think it would be good to have some running code before advancing this to
IESG review and RFC publication. I don’t mean someone being able to send
the flag in a RA, but an operating system reacting to receiving a RA with
the flag set.

Operating system implementers will be able to provide valuable feedback to
the working group on how to mitigate risk for some of the suspected attack
vectors - and it’ll be educational to see how this works in practice. I
think running code will improve this specification.

Kind regards,

Job

v2.23.0 | Report a Bug | By Email