Re: [ietf-privacy] protocol discussion

F_against <f_against@protonmail.com> Thu, 05 April 2018 08:14 UTC

Return-Path: <f_against@protonmail.com>
X-Original-To: ietf-privacy@ietfa.amsl.com
Delivered-To: ietf-privacy@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EA815126CC4 for <ietf-privacy@ietfa.amsl.com>; Thu, 5 Apr 2018 01:14:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=protonmail.com
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 IscmYC3xSf57 for <ietf-privacy@ietfa.amsl.com>; Thu, 5 Apr 2018 01:14:23 -0700 (PDT)
Received: from mail-1857040132.protonmail.ch (mail-1857040132.protonmail.ch [185.70.40.132]) (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 2ABAF120725 for <ietf-privacy@ietf.org>; Thu, 5 Apr 2018 01:14:22 -0700 (PDT)
Date: Thu, 05 Apr 2018 04:14:15 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=protonmail.com; s=default; t=1522916058; bh=gXLTmZxChQsvfPVEBKHa+rN+N6LJxm8B6YnDQz4U/IY=; h=Date:To:From:Cc:Reply-To:Subject:In-Reply-To:References: Feedback-ID:From; b=s62ari2zYJocDQfr/Fmwz4wAsMZUbkTsC7UPePC71i2JHy3BIwdNRLIXkuiv6guyM k5pXkmCckW5hbKew/qK383igIOoC0pObYkSMQUYPKfwZd0zKHL9tf0E/pXDVTNqDsh B/D77DjST+6ltZ/7jrfTkjojIezS0czEcJEOuKmM=
To: Christian Huitema <huitema@huitema.net>
From: F_against <f_against@protonmail.com>
Cc: David Lloyd-Jones <david.lloydjones@gmail.com>, "ietf-privacy@ietf.org" <ietf-privacy@ietf.org>
Reply-To: F_against <f_against@protonmail.com>
Message-ID: <Wwp1GmmDJ12n91vmj4rDsAhYJlnaeupJ3SqyBQtgkuTgwow5PLz_qXq9hcCNkOdnUDoiY_oEs_p8ka6YY-l32OVKopLRsm5r4RYn9ClqMYc=@protonmail.com>
In-Reply-To: <aff7ce17-52ee-b9d6-6ee6-07788dec15b0@huitema.net>
References: <3MAQ6M1tPggPvHftmQw7aTiWFOtqKife0JD9XL884XYpcJsybJHf144FOhmbl4piOji6qyxVsvgo2D_mQbrQBUKsSZrH3uY4VwQBM-FoHSw=@protonmail.com> <CAG-id0asDC8Xbes9rrCfD-18p3qxoXX9oxQRNL5aEkcHOr9ScQ@mail.gmail.com> <aff7ce17-52ee-b9d6-6ee6-07788dec15b0@huitema.net>
Feedback-ID: k56xQq7_TYsnTMoUxbfBMmJtguUP1KkoQupyqZ8Bsq2d0y8N8qccnJzvAV9Q8xV4JeRm5gAaQ7vGTrHjZ4vDfQ==:Ext:ProtonMail
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="b1_9ea6dac7bf631cea57faee0f533811d7"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-privacy/-GhKctFfaJQ6156mdZaGQnoEA_0>
X-Mailman-Approved-At: Sun, 08 Apr 2018 08:17:36 -0700
Subject: Re: [ietf-privacy] protocol discussion
X-BeenThere: ietf-privacy@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Internet Privacy Discussion List <ietf-privacy.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-privacy>, <mailto:ietf-privacy-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-privacy/>
List-Post: <mailto:ietf-privacy@ietf.org>
List-Help: <mailto:ietf-privacy-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-privacy>, <mailto:ietf-privacy-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 05 Apr 2018 08:14:27 -0000

Thank you for supporting me Christian. I will do a writeup and save some comma.

Sent with [ProtonMail](https://protonmail.com) Secure Email.

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On 4 April 2018 8:26 PM, Christian Huitema <huitema@huitema.net> wrote:

> Anonymity and commas apart, this request falls in the general category of "starting new work in the IETF". I wish we had a specific page on the IETF web site explaining how to do that. For your specific proposal on alternative to OTP, I would:
>
> 1) Write a white paper explaining the problem you want to solve -- emphasis on problem, rather than solution. This will be the basis for the initial discussions.
>
> 2) Demonstrate that there is interest in solving the problem in some community. It has to be more than just you, there has to be some people or companies who think solving the problem is important, and who are ready to work in the IETF to develop a standard and later implement and deploy the standardized solution.
>
> 3) Contact the relevant area director in the IETF on the best way to proceed. In your case, that would be the directors of the security area, Benjamin Kaduk and Eric Rescorla. (See addresses at https://datatracker.ietf.org/wg/). They will advise you on the next step, which can be either more research, or working with an existing working group, or start the process towards creation of a working group.
>
> Note that there is a big tension between anonymity and standardization. The standardization process requires transparency to prevent abuses such as insertion of patented technology in standards without proper disclosure.
>
> -- Christian Huitema
>
> On 4/4/2018 2:58 AM, David Lloyd-Jones wrote:
>
>> Um, I think you need to get a handle on how the comma works and how its working affects meaning.  The ancient usage of the comma in the Second Amendment of the US Constitution is a good example of the trouble one can get into with misplaced commas.
>>
>> Your odd use of the comma in your message suggests that you are not yet ready to take on the sometimes crucial topic of protocols, anonymous F.
>>
>> Sorry 'bout 'dat, but frankness is sometimes the best policy.
>>
>> Best wishes,
>> -dlj.
>>
>> On 3 April 2018 at 15:32, F_against <f_against@protonmail.com> wrote:
>>
>>> Hello Everyone,
>>>
>>> I want to talk about protocol, that has similar characteristics to otp.
>>> Are you interessted?
>>>
>>> GreetingsF.
>>>
>>> _______________________________________________
>>> ietf-privacy mailing list
>>> ietf-privacy@ietf.org
>>> https://www.ietf.org/mailman/listinfo/ietf-privacy
>>
>> _______________________________________________
>> ietf-privacy mailing list
>> ietf-privacy@ietf.org
>>
>> https://www.ietf.org/mailman/listinfo/ietf-privacy