IETF Logo Mail Archive

Re: Questions regarding the security mechanisms//RE: CRH and RH0

Nick Hilliard <nick@foobar.org> Sat, 16 May 2020 19:31 UTC

Return-Path: <nick@foobar.org>
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 F1B5A3A07A0 for <ipv6@ietfa.amsl.com>; Sat, 16 May 2020 12:31:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0
X-Spam-Level:
X-Spam-Status: No, score=0 tagged_above=-999 required=5 tests=[SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=unavailable 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 O1e8xhkFvwXw for <ipv6@ietfa.amsl.com>; Sat, 16 May 2020 12:31:13 -0700 (PDT)
Received: from mail.netability.ie (mail.netability.ie [IPv6:2a03:8900:0:100::5]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 876053A07AD for <6man@ietf.org>; Sat, 16 May 2020 12:31:13 -0700 (PDT)
X-Envelope-To: 6man@ietf.org
Received: from crumpet.local (089-101-070074.ntlworld.ie [89.101.70.74] (may be forged)) (authenticated bits=0) by mail.netability.ie (8.15.2/8.15.2) with ESMTPSA id 04GJV74g099488 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 16 May 2020 20:31:08 +0100 (IST) (envelope-from nick@foobar.org)
X-Authentication-Warning: cheesecake.ibn.ie: Host 089-101-070074.ntlworld.ie [89.101.70.74] (may be forged) claimed to be crumpet.local
Subject: Re: Questions regarding the security mechanisms//RE: CRH and RH0
To: John Scudder <jgs=40juniper.net@dmarc.ietf.org>
Cc: 6man <6man@ietf.org>
References: <23488ea0d4eb474c9d7155086f940dae@huawei.com> <006c01d62aa1$8c195520$a44bff60$@com> <DM6PR05MB634863122645FD4981B97F71AEBD0@DM6PR05MB6348.namprd05.prod.outlook.com> <CALx6S35thGuTgTmCFozU=3MULW8V95OwA5GdqQ7OGrA-agR7Hw@mail.gmail.com> <891ccad03b484c7386ab527d89143f8c@huawei.com> <87E86EE4-7D6C-49A3-A965-317C3F95A346@juniper.net>
From: Nick Hilliard <nick@foobar.org>
Message-ID: <8854a4c6-705b-ca46-c2c9-ee931cb55d41@foobar.org>
Date: Sat, 16 May 2020 20:31:06 +0100
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:52.0) Gecko/20100101 PostboxApp/7.0.15
MIME-Version: 1.0
In-Reply-To: <87E86EE4-7D6C-49A3-A965-317C3F95A346@juniper.net>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-GB
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/ZGBlIloCM3WLFlzbqQ3znMM8KIQ>
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: Sat, 16 May 2020 19:31:15 -0000

John Scudder wrote on 16/05/2020 20:18:
> network. For this reason, I think the “complemented per-node 
> protection” is of little value. It may be of negative value if it 
> leads to a sense of complacency on the part of the victim.

separate to this from a security point of view, there should be a knob
to enable CRH processing, defaulting to off.  Suggested text:

> Routers which process CRHs MUST have a configuration knob to
> control whether CRH processing is enabled or not.  The default value
> of this knob MUST be to disable CRH processing.

Nick

v2.23.0 | Report a Bug | By Email