[Taps] Charter change for security
Kyle Rose <krose@krose.org> Tue, 18 July 2017 09:12 UTC
Return-Path: <krose@krose.org>
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 E228D131DC7 for <taps@ietfa.amsl.com>; Tue, 18 Jul 2017 02:12:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=krose.org
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 sChS09KYbkVw for <taps@ietfa.amsl.com>; Tue, 18 Jul 2017 02:12:30 -0700 (PDT)
Received: from mail-qt0-x229.google.com (mail-qt0-x229.google.com [IPv6:2607:f8b0:400d:c0d::229]) (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 D3276131945 for <taps@ietf.org>; Tue, 18 Jul 2017 02:12:29 -0700 (PDT)
Received: by mail-qt0-x229.google.com with SMTP id b40so10808652qtb.2 for <taps@ietf.org>; Tue, 18 Jul 2017 02:12:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=krose.org; s=google; h=mime-version:from:date:message-id:subject:to; bh=Y4xz4BfG0XVkzSoAWD4NuHybo8VJsFUk1cG9yyFFF6k=; b=lZSvefPYL5dxOKEMNP8UF/EktbJoCddo9/K71mMmHgIlJ4b9oowkRKLxKgPzX9Yami cSrMHYJ6qzLkwzBy1FzB2A/iK6WD7R+qtgrQIBGxcAUD+c/nBbdPXt0VyK5qLD2r1uq8 yn/NSpzsQHkERC95ph9y1uUT1RpsPxjaWJEwQ=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=Y4xz4BfG0XVkzSoAWD4NuHybo8VJsFUk1cG9yyFFF6k=; b=SUjvZGmr/mkyH5VqG8l3mhuY7Psha9olVDZJ6t9jh87N+zu0lkqfm2Rw2vgXYHhsGy kqIT26vyQAxWQ+ZxUAsaXIwrKPVwTR2aeonD5bSPo7GpnlHljnB7hSK7WVke21d6J6pu iz7cyH+lm/ttt89boK+iNg6HQ5vAFHAqivyggkxOyHIPqnP3odeRf2h8KrbX3McTjAyY 7atx3QwmQ1J/5RcmvOplevFBBRK/QXNY4TdZjLi+MkAvIAVFyZC/NDFFb4HznkOPhS+Z xrHX0R+9tZfEB2B76CwOiB88CyKpM5KPuLc7DnxKwTa1/ziEy15aqqlTBhNPgA6vEMR0 OdtQ==
X-Gm-Message-State: AIVw1130jXnW5dHRVAdvn1kIKX71zRU4htdRqM7/WV9l/QNzMEEAV/eV 4SYlTshA07rbVdmSMW0CHb76Tqdo7qWD7Sfj4Q==
X-Received: by 10.237.32.70 with SMTP id 64mr699808qta.218.1500369148721; Tue, 18 Jul 2017 02:12:28 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.55.128.194 with HTTP; Tue, 18 Jul 2017 02:12:28 -0700 (PDT)
X-Originating-IP: [2001:67c:370:128:5d46:1ee8:bdb9:d77a]
From: Kyle Rose <krose@krose.org>
Date: Tue, 18 Jul 2017 11:12:28 +0200
Message-ID: <CAJU8_nXN6tF4phBJ1Hpo+w4F-Y+s5pnKjU+ovZWxfNvqwZ0KBw@mail.gmail.com>
To: taps@ietf.org
Content-Type: multipart/alternative; boundary="94eb2c0c98c8245197055493eaa0"
Archived-At: <https://mailarchive.ietf.org/arch/msg/taps/359ewr6nWfHBr38WMRuK_Vq0dYk>
Subject: [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 09:12:32 -0000
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] Charter change for security Kyle Rose
- Re: [Taps] Charter change for security Brian Trammell (IETF)
- Re: [Taps] Charter change for security Michael Welzl
- Re: [Taps] Charter change for security Tommy Pauly
- Re: [Taps] Charter change for security Robert Moskowitz
- Re: [Taps] Charter change for security Aaron Falk
- Re: [Taps] Charter change for security Tommy Pauly
- Re: [Taps] Charter change for security Aaron Falk
- Re: [Taps] Charter change for security Kyle Rose