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

Bob Hinden <bob.hinden@gmail.com> Tue, 06 November 2018 02:52 UTC

Return-Path: <bob.hinden@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 97BAB130DD1 for <ipv6@ietfa.amsl.com>; Mon, 5 Nov 2018 18:52:40 -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, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=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 SJQ6MxYIzknb for <ipv6@ietfa.amsl.com>; Mon, 5 Nov 2018 18:52:38 -0800 (PST)
Received: from mail-pf1-x430.google.com (mail-pf1-x430.google.com [IPv6:2607:f8b0:4864:20::430]) (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 70839130DCC for <ipv6@ietf.org>; Mon, 5 Nov 2018 18:52:38 -0800 (PST)
Received: by mail-pf1-x430.google.com with SMTP id r64-v6so5377479pfb.13 for <ipv6@ietf.org>; Mon, 05 Nov 2018 18:52:38 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=WAgErqetdMgBe2xg4qoIGLmXgspKu+hXOSK2Ze6bxO0=; b=JRgo3njb1wnI0Mu8Ys4E6E0dwWIfYU5DXvIwXz3NHzP2bVoCHY+DgJ4/vhXdOlwgg4 PB9gkCH2T9ClNjCrdQKBmtivRYLyNS9hcyD0vZKWBRPtXnfFWBw9oo9aQv/PzHhpJsF1 Y2LRhql6NCW034Okkupt1Xryt/2hvf8bfWmetTAsbirYk9vVcXKto5U3tzqb+v9wpCFE H052TpawKjtDrziRx4sQ5/QQutgpaKMwlRdULo7lx6H5S2ueJ5mALCkg/kQKRKj2HbJa g/dxnE1n/YgBD/jl1U28sSN7Jw8EdtTuu5wQ3JVnuLfwFpmJcm55YTlT8Nghp0pQIXJQ UUdA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=WAgErqetdMgBe2xg4qoIGLmXgspKu+hXOSK2Ze6bxO0=; b=nh+88y/ScQK90FzFHfC7cMbb8hbXdaJBy174GKUTNQzVEUBi+OrgjJvomacvU0p6f1 qVqC4JCl7QpaJp4A5EUJjEiFdgt9AwXdI2IEFSTpQAlVio+5o9XQJt0RHdruE0byJeAX To+/iU1dRCSxVRG2IPVi+dQMDu+YjPU24YLHoiepqYfA8EDnmr3G4mco48wEd7XAiHxN Q+bIKwGnOqXBq8X8XQXEWzIVdyHhW4OoRx3Uk5W7WT88ZsiuUwlK2vZK2HA+/hXGAWMT oRuRsw3CPVCe8ry5QKIzeJdli0tuUv2oBZPPPOlwlGvJ1rE+nTo08cMTX7VLQesRqMtN BSbQ==
X-Gm-Message-State: AGRZ1gIfrafcrd8XSazcioLxVJGRr12Lql+XrI7MGtmxNLgKjrXG7z31 X8j72V2hPsS+Rd5b51w+VFM=
X-Google-Smtp-Source: AJdET5fvFw1EEXu/t/l/zr9WiMOwJKbN6sFzgLJMc8WIA58Y3M0NDVNxuj8jQfcG6fVZJJI7Faw5PQ==
X-Received: by 2002:a63:e101:: with SMTP id z1mr18806061pgh.310.1541472757785; Mon, 05 Nov 2018 18:52:37 -0800 (PST)
Received: from ?IPv6:2001:67c:370:128:7c70:a184:8d35:e91e? ([2001:67c:370:128:7c70:a184:8d35:e91e]) by smtp.gmail.com with ESMTPSA id z5-v6sm47766107pfd.99.2018.11.05.18.52.35 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 05 Nov 2018 18:52:36 -0800 (PST)
From: Bob Hinden <bob.hinden@gmail.com>
Message-Id: <EF98CBAA-60FB-46B1-AAA7-BB7FF7A742B3@gmail.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_BAFC4832-FA0B-4D34-B8E6-1A019623C289"; protocol="application/pgp-signature"; micalg="pgp-sha512"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: you have running code ... I-D Action: draft-ietf-6man-ipv6only-flag-03.txt
Date: Tue, 06 Nov 2018 09:52:34 +0700
In-Reply-To: <10a71216-7aed-8089-3b6c-a8f952daaf4c@gmail.com>
Cc: Bob Hinden <bob.hinden@gmail.com>, Nick Hilliard <nick@foobar.org>, IPv6 List <ipv6@ietf.org>
To: Brian Carpenter <brian.e.carpenter@gmail.com>
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> <10a71216-7aed-8089-3b6c-a8f952daaf4c@gmail.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/mPjD0Z6yj0s-ZlTkc2HAeJT0Gyg>
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: Tue, 06 Nov 2018 02:52:41 -0000

Hi,

> On Nov 6, 2018, at 2:37 AM, Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
> 
> 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.

To clarify, the draft says that hosts SHOULD do what the flag specifies.  It doesn’t say it is advisory.   RFC2119 defines SHOULD as:

3. SHOULD   This word, or the adjective "RECOMMENDED", mean that there
   may exist valid reasons in particular circumstances to ignore a
   particular item, but the full implications must be understood and
   carefully weighed before choosing a different course.

This discussion would be better if we used the words that are in the draft in the discussion.

I do agree that a node that doesn’t support IPv4 will not see IPv4 traffic, this needs to be clarified in the current draft.

Thanks,
Bob





> 
> 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
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------