Re: [OPSEC] Architectural implications of EH / filtering
Wes Hardaker <wjhns1@hardakers.net> Fri, 14 December 2018 18:31 UTC
Return-Path: <wjhns1@hardakers.net>
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 6E151131213; Fri, 14 Dec 2018 10:31:06 -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 C3jFrHN0-0WI; Fri, 14 Dec 2018 10:31:04 -0800 (PST)
Received: from mail.hardakers.net (mail.hardakers.net [168.150.192.181]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C6C85131210; Fri, 14 Dec 2018 10:31:04 -0800 (PST)
Received: from localhost (unknown [10.0.0.3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.hardakers.net (Postfix) with ESMTPSA id 1436727A22; Fri, 14 Dec 2018 10:31:02 -0800 (PST)
From: Wes Hardaker <wjhns1@hardakers.net>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
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
References: <CAHw9_iK59mb2twkzkCd+at7=2=NfwvkPwuPCfT6kLx=WaBQ3zA@mail.gmail.com> <3661a5b9-9178-d20a-a781-ed773140c8af@cs.tcd.ie>
Date: Fri, 14 Dec 2018 10:31:01 -0800
In-Reply-To: <3661a5b9-9178-d20a-a781-ed773140c8af@cs.tcd.ie> (Stephen Farrell's message of "Wed, 12 Dec 2018 00:20:55 +0000")
Message-ID: <ybl4lbgq7tm.fsf@w7.hardakers.net>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain
Archived-At: <https://mailarchive.ietf.org/arch/msg/opsec/GrPDZ9Bo43DYFOCNtbz0xLXDU24>
Subject: Re: [OPSEC] Architectural implications of 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: Fri, 14 Dec 2018 18:31:06 -0000
Stephen Farrell <stephen.farrell@cs.tcd.ie> writes: > Maybe consider moving IEPG to a more prime-time IETF > meeting week slot? One huge advantage of doing this is it then falls into conflict-avoidance play; right now I can pretty much never make the IEPG meetings due to other non-movable meetings. Rotating it around the IETF schedule, with conflict avoidance especially for speakers, will mean wider attendance and variation with those that can only attend "sometimes". -- Wes Hardaker USC/ISI
- [OPSEC] Architectural implications of EH / filter… Warren Kumari
- Re: [OPSEC] Architectural implications of EH / fi… Stephen Farrell
- Re: [OPSEC] Architectural implications of EH / fi… tjw ietf
- Re: [OPSEC] Architectural implications of EH / fi… Ole Troan
- Re: [OPSEC] [Tsv-art] Architectural implications … Spencer Dawkins at IETF
- Re: [OPSEC] Architectural implications of EH / fi… Warren Kumari
- Re: [OPSEC] Architectural implications of EH / fi… Fernando Gont
- Re: [OPSEC] Architectural implications of EH / fi… Warren Kumari
- Re: [OPSEC] Architectural implications of EH / fi… Wes Hardaker