IETF Logo Mail Archive

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

Ole Troan <otroan@employees.org> Wed, 12 December 2018 08:32 UTC

Return-Path: <otroan@employees.org>
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 43BF012EB11; Wed, 12 Dec 2018 00:32:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham 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 Fkc3e25fIumt; Wed, 12 Dec 2018 00:32:02 -0800 (PST)
Received: from bugle.employees.org (accordion.employees.org [IPv6:2607:7c80:54:3::74]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 47A811294D0; Wed, 12 Dec 2018 00:32:02 -0800 (PST)
Received: from astfgl.hanazo.no (77.18.55.26.tmi.telenormobil.no [77.18.55.26]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by bugle.employees.org (Postfix) with ESMTPSA id DE9C5FECBFCD; Wed, 12 Dec 2018 08:32:01 +0000 (UTC)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by astfgl.hanazo.no (Postfix) with ESMTP id D40C7AF3818; Wed, 12 Dec 2018 09:31:57 +0100 (CET)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 12.1 \(3445.101.1\))
From: Ole Troan <otroan@employees.org>
In-Reply-To: <CAHw9_iK59mb2twkzkCd+at7=2=NfwvkPwuPCfT6kLx=WaBQ3zA@mail.gmail.com>
Date: Wed, 12 Dec 2018 09:31:57 +0100
Cc: 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: <999BE505-0121-4298-BD02-D4B9EF436FC4@employees.org>
References: <CAHw9_iK59mb2twkzkCd+at7=2=NfwvkPwuPCfT6kLx=WaBQ3zA@mail.gmail.com>
To: Warren Kumari <warren@kumari.net>
X-Mailer: Apple Mail (2.3445.101.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/opsec/wUVzGAxmBK8Cur_YswgYYqIDbXg>
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 08:32:03 -0000

Warren,

Thank you for your note.

> On 12 Dec 2018, at 00:58, Warren Kumari <warren@kumari.net> wrote:
> 
> The IETF LC thread on the document, and the TSVART review (and corresponding thread) both generated useful, and actionable comments, and I've asked the authors to go through them carefully and address them -- these fall into the "on the document" category. I think that once these have been done, the document itself will be in acceptable shape to proceed (but keep reading!) 

How do I interpret this? Are you saying you think there is IETF consensus to publish?

Cheers,
Ole

v2.23.0 | Report a Bug | By Email