Re: IPv6 first-hop risks and threats and mitigations

Christopher Morrow <christopher.morrow@gmail.com> Thu, 17 December 2020 17:29 UTC

Return-Path: <christopher.morrow@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 D055F3A0E34; Thu, 17 Dec 2020 09:29:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, SPF_HELO_NONE=0.001, 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 jlcPOW2RugOc; Thu, 17 Dec 2020 09:28:59 -0800 (PST)
Received: from mail-qk1-x729.google.com (mail-qk1-x729.google.com [IPv6:2607:f8b0:4864:20::729]) (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 670B43A0E33; Thu, 17 Dec 2020 09:28:59 -0800 (PST)
Received: by mail-qk1-x729.google.com with SMTP id 186so27098213qkj.3; Thu, 17 Dec 2020 09:28:59 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=A1i8XNM/pUD6QTs1IKzj7Ww6W5SqW2QCIujokXcvT0k=; b=ltoqwFO++LEG6knUG4Ru1wDiaSfOtcIAmu+6eftJG5BsNzFg74usZ87JnlcBxCDm9m HHksX/49RWUvMsEKXOFrlNOmR56fs/VWZ/o/uNE+3syyXPy7YiKK1mFQCVXUzEgTqe6F nqpZKZTxN1Yox6Z5IISr8cHcG1GrgBuW8rMoBbHlKZTJy0dn8wQFPMpZzfrvWXlEt+kz H6npqPZYo2+pu+OfEHU1OHYO4Ts2NXdYmmc2Gw6MnQuU7HyUO0vVI0fvgMDMji1jdDqs bdnI3zlo2mdZfCl3fPVOOLs+DlCxN/An2eMKPI+c5T3ws3b4PSh6nsTFvf/wxs4H4f7T KMDQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=A1i8XNM/pUD6QTs1IKzj7Ww6W5SqW2QCIujokXcvT0k=; b=IeGcj8JI6DGl5pJEXkJZoN6Q+ks+NWz8nMOIAvKPs/QEl669+Z52FPN5O4y45agdcA X9LmvSUpd28GgFh+TBTNRFtMzCfBBCxTQKmi1DrQG2akNjfAUtf5owigG35psPy3hfDz MRgh5OXtA6DHnXSJDGfkBIonlegEMWNOA749dIWo+G5ttfCH4m8rWAqGlnB3RYnOtRKo 81vVXrFjSBX22Urs9x+i4wFrljDBpW1fGxPMNLXHnIyAfrz2WAcmYRuiGegATmMId8YZ 3biDqfyxfiXfhU4Bb6dQC4tN0kCadBd7e35ouvogc5J7VZ4pvpnlkrW9dpq+qtyILaJQ szTA==
X-Gm-Message-State: AOAM533ig9zQz1gHantEmK+ngsieSEAnGfHSthWi6MDdWe+oNUjExfQo oL7P/05duLDZL+t7FNsGAzCyQ0ZnhYYV4owmKHM=
X-Google-Smtp-Source: ABdhPJy6JVs772u5GW8cKobXM6twqcVuP4xlzmQ9cN4z72Ih+0/fR+PjIenj/PUaTfyNZbd9WfzGkCzSJZGjpbI4ZZs=
X-Received: by 2002:a37:a06:: with SMTP id 6mr322286qkk.376.1608226138372; Thu, 17 Dec 2020 09:28:58 -0800 (PST)
MIME-Version: 1.0
References: <160603202606.8188.11893701417034577472@ietfa.amsl.com> <7B0EBC9E-4831-4005-98D9-5010CD1097F6@cisco.com> <CAMugd_UrsgmYTSg-abzuHt5ry2dxrU8gLFAQn+WkgcupGbrc5Q@mail.gmail.com> <74f40b386fc24d288412663a707517e4@huawei.com> <20462.1606091054@localhost> <c3267d8670d74df2a61e260c65981ad5@huawei.com>
In-Reply-To: <c3267d8670d74df2a61e260c65981ad5@huawei.com>
From: Christopher Morrow <christopher.morrow@gmail.com>
Date: Thu, 17 Dec 2020 12:28:47 -0500
Message-ID: <CAL9jLaYzHPK10otASo8f5MS8+FcEPvPz3RRYGVkbH-M3hA4BMQ@mail.gmail.com>
Subject: Re: IPv6 first-hop risks and threats and mitigations
To: Xipengxiao <xipengxiao@huawei.com>
Cc: Michael Richardson <mcr+ietf@sandelman.ca>, Nabil Benamar <benamar73@gmail.com>, "Pascal Thubert (pthubert)" <pthubert=40cisco.com@dmarc.ietf.org>, 6man Chairs <6man-chairs@ietf.org>, "ipv6@ietf.org" <ipv6@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/R69CVsBDSrh0irhVvf_ErP0UkPg>
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: Thu, 17 Dec 2020 17:29:01 -0000

I thought this was work Fernando Gont / Jen Linkova already
undertook... or had already taking some large steps to cover at any
rate.
Were their docs not helpful here?

On Wed, Dec 16, 2020 at 3:37 PM Xipengxiao <xipengxiao@huawei.com> wrote:
>
> Hi Michael,
>
>
>
> >> So, the idea being to write down the issues, give the attacks names, and then clarify what defenses we have already and how well they work?
>
>
>
> Yes.  Are you interested in working on this together?  Happy holidays!
>
>
>
> XiPeng
>
>
>
> -----Original Message-----
> From: Michael Richardson [mailto:mcr+ietf@sandelman.ca]
> Sent: Monday, November 23, 2020 1:24 AM
> To: Xipengxiao <xipengxiao@huawei.com>om>; Nabil Benamar <benamar73@gmail.com>om>; Pascal Thubert (pthubert) <pthubert=40cisco.com@dmarc.ietf.org>rg>; 6man Chairs <6man-chairs@ietf.org>rg>; ipv6@ietf.org
> Subject: IPv6 first-hop risks and threats and mitigations
>
>
>
>
>
> Xipengxiao <xipengxiao@huawei.com> wrote:
>
>     > I also think that it’s a good piece of work, and shouldn’t be given up.
>
>
>
>     > I would also like to take this opportunity to propose that the WG start
>
>     > a “problem statement of IPv6 first-hop protocols” draft.  The rationale
>
>     > is: many IPv6 first-hop protocols like ND, SLAAC were designed long
>
>     > time ago; many things have changed over the years, e.g. the advent of
>
>     > wireless, mobility, IoT, overlays;  lately there are multiple drafts
>
>     > trying to fix various issues in a number of IPv6 first-hop protocols,
>
>     > including:
>
>
>
> So, the idea being to write down the issues, give the attacks names, and then clarify what defenses we have already and how well they work?
>
>
>
> --
>
> Michael Richardson <mcr+IETF@sandelman.ca>   . o O ( IPv6 IøT consulting )
>
>            Sandelman Software Works Inc, Ottawa and Worldwide
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------