Re: [Tsv-art] Tsvart last call review of draft-ietf-opsec-ipv6-eh-filtering-06

Christopher Morrow <morrowc.lists@gmail.com> Tue, 04 December 2018 23:24 UTC

Return-Path: <christopher.morrow@gmail.com>
X-Original-To: tsv-art@ietfa.amsl.com
Delivered-To: tsv-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 25D6A127332; Tue, 4 Dec 2018 15:24:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 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, HTML_MESSAGE=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 c6vWXb4PldL7; Tue, 4 Dec 2018 15:24:09 -0800 (PST)
Received: from mail-io1-xd34.google.com (mail-io1-xd34.google.com [IPv6:2607:f8b0:4864:20::d34]) (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 CD0E912E7C1; Tue, 4 Dec 2018 15:24:08 -0800 (PST)
Received: by mail-io1-xd34.google.com with SMTP id x6so15103343ioa.9; Tue, 04 Dec 2018 15:24:08 -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; bh=XQS6VgfoBf7NphuBezLckvOm1t4Fhl061u2zgrFg4o4=; b=ogiyE0yjsVatLRvld/PWYjZulSV5KCoJo4IQT760e9Y2B7txlslx9ufkpGmV3I91bb 7ACnnI3JSvOg5CnxcC9sra+Ak/vAlYEUFYDVNLH5z6+rWWus1qfYTgRGE8e12HxQZ3RR zmVO9lxLGU8lbVGBt4Ggt4MmlP4O85lTFMI1wUteYES95eJNYr+IelkihKpbWpqZ8Fl5 IRR5Gdkiv/v9CzQTFavipZ97thbejjd0O0YSrGHT9ebaGyf8yQ1F834bjkYFs6Z9WGRw M582Y85rUGm1BgQK8QE3u+gCHcyGoDghtUqGY0ITBWOBSbNfjAdKo+8zKEehUdtukQpK pNQg==
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; bh=XQS6VgfoBf7NphuBezLckvOm1t4Fhl061u2zgrFg4o4=; b=SigVFbc3iuW9j7BELndHHvZPYfAhmHba6zSKPbg+dICzolkCE4IDv3HBXsYcAKrQMj u6PTFrhG0+89CqkDrba67iA1UksXEfJT4UOs6Lm/bb2tGsacfIP0bgsKY4wrGCSAaEGL 4q0n1+ze2NQxlggYF3EXBtXx4Y59HbwtHLvGeU/5uaDURrSR591L0GEjEei3/dq9l2X/ RYrnEH5j9dUGCxVDc84dXh4cBsOVNAbAGBRLhyXxI1tZY4tvW6g6KAHE+juHZu55AWK7 b9fq9xTOo+4afrPUh26gxeRyJfJgXXnhtOk/4Guqfeiy5MpZ0QBpvBLaVfxNF4RxZHt1 7sfg==
X-Gm-Message-State: AA+aEWacpvnpUQNrdcSl433R4YtIJ5ZGHXKSM8uzJh1Kxvrfp8UpvMoU QN5YNSfY6Lw3F/dDxQYlfeUfJaw0QDQ6kQ1vAqk=
X-Google-Smtp-Source: AFSGD/Uq4QXhbs8Lshcs5MtJD7ccpJs7wWvCFNLEyyYtqhUb/+TfiErfQBuFzPtNgmB8761T5IXo1wwJ+xiKTRAptR8=
X-Received: by 2002:a5d:8ac6:: with SMTP id e6mr10978718iot.235.1543965847885; Tue, 04 Dec 2018 15:24:07 -0800 (PST)
MIME-Version: 1.0
References: <CACL_3VGeJPzDhS0RVAvpQs9W8b4EODft-qJRwBD6Xxm+X6BZ6A@mail.gmail.com>
In-Reply-To: <CACL_3VGeJPzDhS0RVAvpQs9W8b4EODft-qJRwBD6Xxm+X6BZ6A@mail.gmail.com>
From: Christopher Morrow <morrowc.lists@gmail.com>
Date: Tue, 04 Dec 2018 18:23:55 -0500
Message-ID: <CAL9jLabK0bZz2nki=oFNHT0OrpVAB8pw7emAj2BtkHRCzkfmqQ@mail.gmail.com>
To: heard@pobox.com
Cc: Joe Touch <touch@strayalpha.com>, Stewart Bryant <stewart.bryant@gmail.com>, tsv-art@ietf.org, opsec wg mailing list <opsec@ietf.org>, ietf <ietf@ietf.org>, draft-ietf-opsec-ipv6-eh-filtering.all@ietf.org, Nick Hilliard <nick@foobar.org>
Content-Type: multipart/alternative; boundary="000000000000e89e15057c3a8fd5"
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsv-art/hJxmYNxSQ36jsOBataQsWXQWPPw>
Subject: Re: [Tsv-art] Tsvart last call review of draft-ietf-opsec-ipv6-eh-filtering-06
X-BeenThere: tsv-art@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Transport Area Review Team <tsv-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsv-art>, <mailto:tsv-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tsv-art/>
List-Post: <mailto:tsv-art@ietf.org>
List-Help: <mailto:tsv-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsv-art>, <mailto:tsv-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Dec 2018 23:24:12 -0000

On Tue, Dec 4, 2018 at 5:56 PM C. M. Heard <heard@pobox.com> wrote:

> On Tue, 4 Dec 2018 15:17:33 -0500 Christopher Morrow wrote:
> > A solution might be to have a mode where  a router may just ignore all
> > headers except the src/dst-ip and simply forward all packets, trusting
> > that the conversing adults will sort out problems with unknown/new/
> > experimental headers or with a tortured ordering of headers (for
> > instance).
>
> Glad to hear you say that, because that's exactly what RFC 7045
> envisions as the default forwarding behavior:
>
>
I'm glad I'm not too nuts :)


>    Any forwarding node along an IPv6 packet's path, which forwards the
>    packet for any reason, SHOULD do so regardless of any extension
>    headers that are present [...]
>
>
this does mean that: "please filter the flarbly protocol traffic, eh-1234"
is going to be very hard to do in the network.


> Recognizing that processing of Hop-by-Hop Options in the fast path is
> costly, RFC 8200 formally dropped the requirement for every router to
> process them by default:
>
>    NOTE: While [RFC2460] required that all nodes must examine and
>    process the Hop-by-Hop Options header, it is now expected that nodes
>    along a packet's delivery path only examine and process the
>    Hop-by-Hop Options header if explicitly configured to do so.
>
>
it's important to note that some platforms can't look beyond a certain
number of headers, and that ordering of the headers us up to the src, which
when they are being mean is ... bad :( Even platforms that can look more
than a few headers deep pay for that with clock cycles, so 100g -> 400g ->
1tbps interfaces are less and less likely to see further into the packet(s).


> What some of us would like to see is a statement in the draft that it's
> just fine to operate this way (Christian Huitema made that suggestion
> earlier in this thread, and so did I in my detailed last-call comments).
>
>
oh, good. I like that idea... noting that: "makes filtering bad traffic
pretty impossible" though.


> Mike Heard
>