Re: you have running code ... I-D Action: draft-ietf-6man-ipv6only-flag-03.txt

Alexandre Petrescu <alexandre.petrescu@gmail.com> Mon, 05 November 2018 11:49 UTC

Return-Path: <alexandre.petrescu@gmail.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 93A12128CFD for <ipv6@ietfa.amsl.com>; Mon, 5 Nov 2018 03:49:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.633
X-Spam-Level:
X-Spam-Status: No, score=-2.633 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_MED=-2.3, SPF_SOFTFAIL=0.665] 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 ySvRmEIJKN3f for <ipv6@ietfa.amsl.com>; Mon, 5 Nov 2018 03:49:34 -0800 (PST)
Received: from oxalide-smtp-out.extra.cea.fr (oxalide-smtp-out.extra.cea.fr [132.168.224.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 6D4BD1277CC for <ipv6@ietf.org>; Mon, 5 Nov 2018 03:49:34 -0800 (PST)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by oxalide-sys.extra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id wA5BnWgr009193 for <ipv6@ietf.org>; Mon, 5 Nov 2018 12:49:32 +0100
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 45C382043D0 for <ipv6@ietf.org>; Mon, 5 Nov 2018 12:49:32 +0100 (CET)
Received: from muguet1-smtp-out.intra.cea.fr (muguet1-smtp-out.intra.cea.fr [132.166.192.12]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 3C1032042CE for <ipv6@ietf.org>; Mon, 5 Nov 2018 12:49:32 +0100 (CET)
Received: from [10.8.34.184] (is227335.intra.cea.fr [10.8.34.184]) by muguet1-sys.intra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id wA5BnV7j006276 for <ipv6@ietf.org>; Mon, 5 Nov 2018 12:49:32 +0100
Subject: Re: you have running code ... I-D Action: draft-ietf-6man-ipv6only-flag-03.txt
To: ipv6@ietf.org
References: <153973137181.9473.10666616544238076833@ietfa.amsl.com> <6264F7A1-59EB-467D-A576-E5F2F0DEE7DD@lists.zabbadoz.net> <CACWOCC-xL0PfkNHgCqhB28GE-jCWUUagQE4PukdpXK+YHgWpyg@mail.gmail.com> <97ba35ff-b4a7-314c-3010-297d06be645d@foobar.org> <01c2a55e-1888-3ebc-3252-11b9005b8272@gmail.com> <0abd7b4d-b0e0-b1bc-2468-678befbc7cac@asgard.org> <3e155df0-5799-8788-5fbe-767a7421828c@gmail.com> <18646396-e3f7-b9ad-3871-69868468859a@asgard.org> <d080497b-4f39-b877-1524-f23d9b1446e0@gmail.com> <95654922-acd1-3cb3-c650-942c97e3cc85@asgard.org> <cb3e14a8-91d7-f247-e6aa-d08f38b58bc5@gmail.com> <b067b06e-084b-b32f-21fb-137b39985b83@foobar.org>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <95330b88-890b-731e-236b-e25d96c738d6@gmail.com>
Date: Mon, 05 Nov 2018 12:49:31 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1
MIME-Version: 1.0
In-Reply-To: <b067b06e-084b-b32f-21fb-137b39985b83@foobar.org>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: fr
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/BCOInFwUzDJTn9qWs8iG7boJRrg>
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: Mon, 05 Nov 2018 11:49:37 -0000


Le 05/11/2018 à 12:15, Nick Hilliard a écrit :
> Brian E Carpenter wrote on 05/11/2018 07:38:
>> And yes, a host MAY ignore it (that's the complement to the SHOULD
>> in the draft). We've never said anything else.
> 
> yes, but you have stated "On an IPv6-Only link, IPv4 might be used for 
> malicious purposes and pass unnoticed by IPv6-Only monitoring mechanisms".
> 
> If you want ipv6only-flag to be advisory, then you need to remove this 
> bullet-point from the document because the presence or absence of an RA 
> with ipv6only-flag set will not have any effect on malicious use of ipv4 
> on an otherwise "ipv6-only" network.
> 
> You cannot use security to justify something unless the proposal 
> provides a mechanism for enforcement; if you have no means of 
> enforcement, it's fluff, not security.

Well there is the Secure Neighbor Discovery protocol (SeND).  With it 
one can claim the link to be secure if IPv6-Only and insecure if IPv4 is 
present.

Simpler but less strong than SeND, there can be mechanisms to ensure a 
certain level of security, about the MAC address in the L2 header of the RA.

Alex

> 
> Nick
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>