Re: [OPSEC] Architectural implications of EH / filtering (was: draft-ietf-opsec-ipv6-eh-filtering)

tjw ietf <tjw.ietf@gmail.com> Wed, 12 December 2018 02:33 UTC

Return-Path: <tjw.ietf@gmail.com>
X-Original-To: opsec@ietfa.amsl.com
Delivered-To: opsec@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6959B131021; Tue, 11 Dec 2018 18:33:49 -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 3Xus5wwBt-hU; Tue, 11 Dec 2018 18:33:47 -0800 (PST)
Received: from mail-io1-xd2c.google.com (mail-io1-xd2c.google.com [IPv6:2607:f8b0:4864:20::d2c]) (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 5BE34131016; Tue, 11 Dec 2018 18:33:47 -0800 (PST)
Received: by mail-io1-xd2c.google.com with SMTP id x6so13578843ioa.9; Tue, 11 Dec 2018 18:33:47 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=cqxCTR9yvq0My9hc/VuefhE4F22/lQmKCFcZT/sSt5s=; b=K2IlQhZtre8nQtJVycFopLpXBnGSIKgJ7z9CgaynEUU+KCtHeql07GS2WR2JR4q7t0 uUwRGTmD1FGpLPnLB8Vcl+HL6RapB21188tKMaS4q7As8N/SvxXeDoE1wQ5+EB5tInRu ED72wbwKKSC742t6GgTdC04Yrno9xcCbM09ud7YB6l+nhX2NoP+kOZEpdfLdstaShs4I /Ec/8nMpjeHcI6dLZGPNTIcgSt63UksSU3dIh5OQEK1cvTAib/qhVvQV0yPY0q3lSteC nRIQpmdFpdqMQu9flp0TjEYfxsJdbAipcTMpuT8p97yrUqN+aZthZWWpKgfUyt/EQT8b Nq+g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=cqxCTR9yvq0My9hc/VuefhE4F22/lQmKCFcZT/sSt5s=; b=KUs1ZQM0nQwgXgYAipnMknMIrV75m4Oh9r+ULJ0nS/ZibpNbnF6bEw2H8Ni9ZZFhcz flTYFzKYECerwTrk5CcbBeI+n/C9CimvyM+xe8i983wBMeqDc6+RvE2MADsXVpUoYzaK Z0D4P1har1T+7NESHO0Fljdj0u0oCJcW/FE0yAw/gnc26G257ZYJmCOOIqn8cBVktKOm U2pC0PACZlrcorkxSgTWM69b8rxASCJNRAfgjy3Tc62ApO2dKcONG3baj8u8gO/4ZqyH tgzE+m0sFPIad2U9UM8QuvHnv8+28CrP9yI5z0e1T2ID/OL3tTizoyZaY1JB2oZqSjhA MY+g==
X-Gm-Message-State: AA+aEWY27yJdA2x9DEcjA64JKwoI2AMgv4shzbQEbl+9NAUPjTNXh9OP OIWE3CO5iYUjuD45BRt1Irvgrlbc
X-Google-Smtp-Source: AFSGD/WvemyQzub/5ANbs2Q2d61jPWb//nfE0JXtPstjlXQ6wniIGayEoP3JHHqb6HeP6OBTyhWKrw==
X-Received: by 2002:a6b:f404:: with SMTP id i4mr13794598iog.281.1544582026460; Tue, 11 Dec 2018 18:33:46 -0800 (PST)
Received: from [192.168.1.34] (184-15-162-166.dsl2.chtn.wv.frontiernet.net. [184.15.162.166]) by smtp.gmail.com with ESMTPSA id m37sm1994057iti.6.2018.12.11.18.33.45 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 11 Dec 2018 18:33:45 -0800 (PST)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (1.0)
From: tjw ietf <tjw.ietf@gmail.com>
X-Mailer: iPhone Mail (16C50)
In-Reply-To: <3661a5b9-9178-d20a-a781-ed773140c8af@cs.tcd.ie>
Date: Tue, 11 Dec 2018 21:33:45 -0500
Cc: Warren Kumari <warren@kumari.net>, IETF Discuss <ietf@ietf.org>, opsec wg mailing list <opsec@ietf.org>, tsv-art@ietf.org, draft-ietf-opsec-ipv6-eh-filtering.all@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <0F89B980-2C64-4EC7-B8A6-31D6FBE240CA@gmail.com>
References: <CAHw9_iK59mb2twkzkCd+at7=2=NfwvkPwuPCfT6kLx=WaBQ3zA@mail.gmail.com> <3661a5b9-9178-d20a-a781-ed773140c8af@cs.tcd.ie>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Archived-At: <https://mailarchive.ietf.org/arch/msg/opsec/H59NtM6oYmegHde3w8EHY37-J1k>
Subject: Re: [OPSEC] Architectural implications of EH / filtering (was: draft-ietf-opsec-ipv6-eh-filtering)
X-BeenThere: opsec@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: opsec wg mailing list <opsec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsec>, <mailto:opsec-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsec/>
List-Post: <mailto:opsec@ietf.org>
List-Help: <mailto:opsec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsec>, <mailto:opsec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Dec 2018 02:33:50 -0000

I can not agree with mr Farrell enough on this.  

Tim

From my high tech gadget

> On Dec 11, 2018, at 19:20, Stephen Farrell <stephen.farrell@cs.tcd.ie> wrote:
> 
> 
> Hiya,
> 
>> On 11/12/2018 23:58, Warren Kumari wrote:
>> * having some presentations / discussions on "how X works when deployed /
>> implementation shortcomings". As an example, at the IEPG meeting in
>> Yokohama (IETF94) these was a presentation on "MODERN ROUTER ARCHITECTURE
>> FOR PROTOCOL DESIGNERS" -
>> http://www.iepg.org/2015-11-01-ietf94/IEPG-RouterArchitecture-jgs.pdf . As
>> another example, I was recently informed of a surprising limitation in TLS
>> libraries -- these are apparently well known to those who work in this
>> space, but I'd certainly never heard of them. I think that we (IETF
>> participants in general) sometimes fall into believing that we know how
>> technology X works because we've helped design it, but don't necessarily
>> know what happens once it escapes our clutches / flies out of the nest.
>> * consider having a BoF on this / these topics.
>> * perhaps something like a workshop?
> 
> Maybe consider moving IEPG to a more prime-time IETF
> meeting week slot? (Or any equivalent.) The couple of
> times I've gotten to IEPG, I was struck by how it was
> higher quality than average IETF presentations. For
> me, I always really like finding out about cases where
> reality != theory and I bet I'm far from alone.
> 
> So, I'd argue a bit against a one-off BoF or workshop
> and more for a recurring opportunity for fact-based
> detailed presentations.
> 
> S.
> <0x5AB2FAF17B172BEA.asc>