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

Brian E Carpenter <brian.e.carpenter@gmail.com> Mon, 05 November 2018 19:37 UTC

Return-Path: <brian.e.carpenter@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 3D1AB130E10 for <ipv6@ietfa.amsl.com>; Mon, 5 Nov 2018 11:37:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id E_hEfsRv-UGJ for <ipv6@ietfa.amsl.com>; Mon, 5 Nov 2018 11:37:45 -0800 (PST)
Received: from mail-pf1-x434.google.com (mail-pf1-x434.google.com [IPv6:2607:f8b0:4864:20::434]) (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 9EB071277D2 for <ipv6@ietf.org>; Mon, 5 Nov 2018 11:37:45 -0800 (PST)
Received: by mail-pf1-x434.google.com with SMTP id y18-v6so2520755pfn.1 for <ipv6@ietf.org>; Mon, 05 Nov 2018 11:37:45 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=lTavgP8FeoM3Xgdjxa4LAJk3sRbfR8dfALh8SLcJW6Y=; b=rySOmNesnoNqubWDqc37Re4i+TneffEZ0G8u1NzJgG3eigbyjBqU5tlFb2Etp08nky u42k5vz/FeX+6Pw+CtaFdCo4EIw3BUi647I4UtfniIp7LkyQZl3pFMXUc4sbeeSlF0X+ ttMAgiKNeLlBNH9uoIhI6lwmagTqCFN2o4jsvpqv0GbXi2SKskgTezrFaPXTyEkul5KD QF783GWSliDHKVk8PgB3PzBN7Dvtk3EmpivNTdp/Seb4y4NUPwMIJNlS1tOFXqQVYk7z mLVn3OyrKqxreQhZN7WeH3wMYINCiB3R/I8y+i8RiT2s5FKQbgctQQjfZ6V+P93Vsa3Y ERPQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=lTavgP8FeoM3Xgdjxa4LAJk3sRbfR8dfALh8SLcJW6Y=; b=efmgseGhVtiIbHS/MZKEuoucH6rz44WYGYXfObtX1GPyoDe66IYqcDGdfd3YbbsFCp JBjzyP/B03McuKBSIuD5WBwfsIOlTqVG4Lx3itTtt6i1S7SuIqA+5VXIctt1pYYb3fSI rwiUdjiczQvvQlgixIur9bXl2cq6rSnRbEYXFX6eWWqU+7N1kVDxX1oI6xOPkVM8aTLS bYLnjiOH6BjMmDfpVr4zj8lRapPM5Yuk4mXOhfMSTr0ZMIkR282hL2YwS6Ughc/PZvIw Aq9E/srhkP1NlqsfUTeuuxXY/74qtYFluUDGfoD3xgjeELCMKIYb726hwMz0F9EM6AQY QRGA==
X-Gm-Message-State: AGRZ1gI3bJbefd99ww8RmxqeDyWAJKl2IpW6oPrPygyn85AcF7FzPJXp acSNRToFW3iwYG+fE0bfE4gyQS/8
X-Google-Smtp-Source: AJdET5dS/7ngn7hCEQyAkRqgrtdDkS8kt14wUtNtT2u8YNmlE5ZhSpQWLudH6KR5jnVK4HAYRmtZ2A==
X-Received: by 2002:a63:2744:: with SMTP id n65mr21050360pgn.65.1541446664770; Mon, 05 Nov 2018 11:37:44 -0800 (PST)
Received: from [192.168.178.30] ([118.148.76.40]) by smtp.gmail.com with ESMTPSA id 80-v6sm13404587pfv.154.2018.11.05.11.37.42 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 05 Nov 2018 11:37:43 -0800 (PST)
Subject: Re: you have running code ... I-D Action: draft-ietf-6man-ipv6only-flag-03.txt
To: Nick Hilliard <nick@foobar.org>
Cc: 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: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <10a71216-7aed-8089-3b6c-a8f952daaf4c@gmail.com>
Date: Tue, 06 Nov 2018 08:37:38 +1300
User-Agent: Mozilla/5.0 (Windows NT 10.0; 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"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/iBHTAZIztFYHC-3uYdpQjCqyrVY>
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 19:37:47 -0000

On 2018-11-06 00:15, Nick Hilliard wrote:
> 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.

Yes, you're correct. There is a slight mitigation effect - hosts that *do*
use the flag to shut down IPv4 operations will not see any malicious IPv4
traffic.

Some rewording is needed.

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

Thanks
   Brian