Re: [Taps] Charter change for security

Robert Moskowitz <rgm-ietf@htt-consult.com> Tue, 18 July 2017 11:40 UTC

Return-Path: <rgm-ietf@htt-consult.com>
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 41F5F131DE5 for <taps@ietfa.amsl.com>; Tue, 18 Jul 2017 04:40:51 -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 SBafyEskW2_H for <taps@ietfa.amsl.com>; Tue, 18 Jul 2017 04:40:48 -0700 (PDT)
Received: from z9m9z.htt-consult.com (z9m9z.htt-consult.com [50.253.254.3]) (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 1D1671317BE for <taps@ietf.org>; Tue, 18 Jul 2017 04:40:48 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by z9m9z.htt-consult.com (Postfix) with ESMTP id 46DFF621BF; Tue, 18 Jul 2017 07:40:46 -0400 (EDT)
X-Virus-Scanned: amavisd-new at htt-consult.com
Received: from z9m9z.htt-consult.com ([127.0.0.1]) by localhost (z9m9z.htt-consult.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id krl9lEU7SOyD; Tue, 18 Jul 2017 07:40:39 -0400 (EDT)
Received: from lx120e.htt-consult.com (dhcp-831f.meeting.ietf.org [31.133.131.31]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by z9m9z.htt-consult.com (Postfix) with ESMTPSA id 050A362196; Tue, 18 Jul 2017 07:40:35 -0400 (EDT)
To: Tommy Pauly <tpauly@apple.com>, "Brian Trammell (IETF)" <ietf@trammell.ch>
References: <CAJU8_nXN6tF4phBJ1Hpo+w4F-Y+s5pnKjU+ovZWxfNvqwZ0KBw@mail.gmail.com> <05F414A1-A2B3-4EF6-A280-DC9DD421B3EC@ifi.uio.no> <406114AF-F4DC-4FB4-B75E-54922F78799A@trammell.ch> <1EDFF789-D5D2-4A52-ABF6-5D6D1B1E61C3@apple.com>
Cc: Kyle Rose <Krose@krose.org>, Michael Welzl <michawe@ifi.uio.no>, "taps@ietf.org" <taps@ietf.org>
From: Robert Moskowitz <rgm-ietf@htt-consult.com>
Message-ID: <d00fa098-fdb8-3bf8-994b-612ab8e72b88@htt-consult.com>
Date: Tue, 18 Jul 2017 13:40:29 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <1EDFF789-D5D2-4A52-ABF6-5D6D1B1E61C3@apple.com>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/taps/3H32tgf6KdRXoMdqo1z71UKhTek>
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 11:40:51 -0000

I just joined this list.

I can work with this.

Bob

On 07/18/2017 01:36 PM, Tommy Pauly wrote:
> Agreed. Thanks for the text proposal, Kyle!
>
> Tommy
>
>> On Jul 18, 2017, at 12:15 PM, Brian Trammell (IETF) <ietf@trammell.ch> wrote:
>>
>> +1.
>>
>> Cheers,
>>
>> Brian
>>
>>> On 18 Jul 2017, at 12:02, Michael Welzl <michawe@ifi.uio.no> wrote:
>>>
>>> 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
>>> _______________________________________________
>>> Taps mailing list
>>> Taps@ietf.org
>>> https://www.ietf.org/mailman/listinfo/taps
>> _______________________________________________
>> Taps mailing list
>> Taps@ietf.org
>> https://www.ietf.org/mailman/listinfo/taps
> _______________________________________________
> Taps mailing list
> Taps@ietf.org
> https://www.ietf.org/mailman/listinfo/taps