IETF Logo Mail Archive

Re: [Taps] Charter change for security

Michael Welzl <michawe@ifi.uio.no> Tue, 18 July 2017 10:02 UTC

Return-Path: <michawe@ifi.uio.no>
X-Original-To: taps@ietfa.amsl.com
Delivered-To: taps@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CEE0D131463 for <taps@ietfa.amsl.com>; Tue, 18 Jul 2017 03:02:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.202
X-Spam-Level:
X-Spam-Status: No, score=-4.202 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_PASS=-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 Ze2gIqkLhLMO for <taps@ietfa.amsl.com>; Tue, 18 Jul 2017 03:02:40 -0700 (PDT)
Received: from mail-out01.uio.no (mail-out01.uio.no [IPv6:2001:700:100:10::50]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 25F95129AC4 for <taps@ietf.org>; Tue, 18 Jul 2017 03:02:39 -0700 (PDT)
Received: from mail-mx05.uio.no ([129.240.10.49]) by mail-out01.uio.no with esmtp (Exim 4.82_1-5b7a7c0-XX) (envelope-from <michawe@ifi.uio.no>) id 1dXPKv-0006qe-WB for taps@ietf.org; Tue, 18 Jul 2017 12:02:38 +0200
Received: from [185.81.136.26] (helo=[192.168.1.171]) by mail-mx05.uio.no with esmtpsa (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) user michawe (Exim 4.82_1-5b7a7c0-XX) (envelope-from <michawe@ifi.uio.no>) id 1dXPKu-000958-Nb; Tue, 18 Jul 2017 12:02:37 +0200
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
From: Michael Welzl <michawe@ifi.uio.no>
In-Reply-To: <CAJU8_nXN6tF4phBJ1Hpo+w4F-Y+s5pnKjU+ovZWxfNvqwZ0KBw@mail.gmail.com>
Date: Tue, 18 Jul 2017 12:02:34 +0200
Cc: "taps@ietf.org" <taps@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <05F414A1-A2B3-4EF6-A280-DC9DD421B3EC@ifi.uio.no>
References: <CAJU8_nXN6tF4phBJ1Hpo+w4F-Y+s5pnKjU+ovZWxfNvqwZ0KBw@mail.gmail.com>
To: Kyle Rose <Krose@krose.org>
X-Mailer: Apple Mail (2.3273)
X-UiO-SPF-Received: Received-SPF: neutral (mail-mx05.uio.no: 185.81.136.26 is neither permitted nor denied by domain of ifi.uio.no) client-ip=185.81.136.26; envelope-from=michawe@ifi.uio.no; helo=[192.168.1.171];
X-UiO-Ratelimit-Test: rcpts/h 2 msgs/h 1 sum rcpts/h 2 sum msgs/h 1 total rcpts 56365 max rcpts/h 54 ratelimit 0
X-UiO-Spam-info: not spam, SpamAssassin (score=-5.0, required=5.0, autolearn=disabled, AWL=0.000, UIO_MAIL_IS_INTERNAL=-5, uiobl=NO, uiouri=NO)
X-UiO-Scanned: 84CE5233914AE6BCF87B8C45FCD57685E2AB7CA4
X-UiO-SPAM-Test: remote_host: 185.81.136.26 spam_score: -49 maxlevel 80 minaction 2 bait 0 mail/h: 1 total 20 max/h 6 blacklist 0 greylist 0 ratelimit 0
Archived-At: <https://mailarchive.ietf.org/arch/msg/taps/w8fWOaYsQiZbbCQB7jrBpi0Eu60>
Subject: Re: [Taps] Charter change for security
X-BeenThere: taps@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Discussions on Transport Services <taps.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/taps>, <mailto:taps-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/taps/>
List-Post: <mailto:taps@ietf.org>
List-Help: <mailto:taps-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/taps>, <mailto:taps-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Jul 2017 10:02:42 -0000

Agree 100% - I think this proposal is exactly the right way to do it.

Cheers,
Michael


> On Jul 18, 2017, at 11:12 AM, Kyle Rose <Krose@krose.org> wrote:
> 
> Proposal:
> 
> (1) Strike the last paragraph of the charter ("TAPS is not chartered to perform detailed analysis...").
> 
> (2) Change the third bullet right above it to read "Extension, modification, or creation of transport or security protocols"
> 
> The idea being to permit analysis of the properties of security protocols with respect to the requirements of TAPS systems, but not to permit creation or customization of security protocols.
> 
> Thoughts?
> 
> Kyle
> _______________________________________________
> Taps mailing list
> Taps@ietf.org
> https://www.ietf.org/mailman/listinfo/taps

v2.23.0 | Report a Bug | By Email