Re: [ietf-privacy] protocol discussion

Christian Huitema <huitema@huitema.net> Wed, 04 April 2018 18:26 UTC

Return-Path: <huitema@huitema.net>
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 0DF54126C0F for <ietf-privacy@ietfa.amsl.com>; Wed, 4 Apr 2018 11:26:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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 js7gCeTtRzDI for <ietf-privacy@ietfa.amsl.com>; Wed, 4 Apr 2018 11:26:34 -0700 (PDT)
Received: from mx43-out1.antispamcloud.com (mx43-out1.antispamcloud.com [138.201.61.189]) (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 1CA601200C1 for <ietf-privacy@ietf.org>; Wed, 4 Apr 2018 11:26:34 -0700 (PDT)
Received: from xsmtp12.mail2web.com ([168.144.250.177]) by mx61.antispamcloud.com with esmtps (TLSv1.2:AES128-SHA:128) (Exim 4.89) (envelope-from <huitema@huitema.net>) id 1f3n79-0007hE-Cr for ietf-privacy@ietf.org; Wed, 04 Apr 2018 20:26:32 +0200
Received: from [10.5.2.14] (helo=xmail04.myhosting.com) by xsmtp12.mail2web.com with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from <huitema@huitema.net>) id 1f3n74-0005pO-Jy for ietf-privacy@ietf.org; Wed, 04 Apr 2018 14:26:28 -0400
Received: (qmail 19213 invoked from network); 4 Apr 2018 18:26:22 -0000
Received: from unknown (HELO [192.168.1.103]) (Authenticated-user:_huitema@huitema.net@[172.56.42.61]) (envelope-sender <huitema@huitema.net>) by xmail04.myhosting.com (qmail-ldap-1.03) with ESMTPA for <ietf-privacy@ietf.org>; 4 Apr 2018 18:26:22 -0000
To: David Lloyd-Jones <david.lloydjones@gmail.com>, F_against <f_against@protonmail.com>
Cc: "ietf-privacy@ietf.org" <ietf-privacy@ietf.org>
References: <3MAQ6M1tPggPvHftmQw7aTiWFOtqKife0JD9XL884XYpcJsybJHf144FOhmbl4piOji6qyxVsvgo2D_mQbrQBUKsSZrH3uY4VwQBM-FoHSw=@protonmail.com> <CAG-id0asDC8Xbes9rrCfD-18p3qxoXX9oxQRNL5aEkcHOr9ScQ@mail.gmail.com>
From: Christian Huitema <huitema@huitema.net>
Openpgp: preference=signencrypt
Message-ID: <aff7ce17-52ee-b9d6-6ee6-07788dec15b0@huitema.net>
Date: Wed, 4 Apr 2018 11:26:21 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0
MIME-Version: 1.0
In-Reply-To: <CAG-id0asDC8Xbes9rrCfD-18p3qxoXX9oxQRNL5aEkcHOr9ScQ@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------1812ECBAFB09031A96A3DEE1"
Content-Language: en-US
X-Originating-IP: 168.144.250.177
X-AntiSpamCloud-Domain: xsmtpout.mail2web.com
X-AntiSpamCloud-Username: 168.144.250.0/24
Authentication-Results: antispamcloud.com; auth=pass smtp.auth=168.144.250.0/24@xsmtpout.mail2web.com
X-AntiSpamCloud-Outgoing-Class: unsure
X-AntiSpamCloud-Outgoing-Evidence: Combined (0.19)
X-Recommended-Action: accept
X-Filter-ID: EX5BVjFpneJeBchSMxfU5qn8U+H+bNqX4C6RsLdIIV9602E9L7XzfQH6nu9C/Fh9KJzpNe6xgvOx q3u0UDjvO1CuLYGlsc2dELanO/z+1tPet4fAxQqrkOpIF05F5G4UQ+9us9+2Ef5XEiO2R2SOqQLz x65UW6iPOfhIHI2hlyp4Jg2LtUh6VaLwPYdf2smTCayQ2nWOuTEKQRGN6UiOn5FVgpT1b21uZVck Gp0ccOYNj3IsPxUoOvqBoVWc32LibjGdSRNeAsqwADJIlioxB5mjPOHqKGcBQEyg/4uHaCBhWuGz JRMkDgEAR16TU1huKPGp/DIIBivDZ+qRALOR3OQXHsr+iXG12RzSj/S+AfQVJuDlUTgrT6t9ZVVn LRv9AeMY32a63w9Ris2VIbjVVzf94V2ITgyR5oZTlUn/zMWbPUpnfd45XXUaprtwt1YI4dshMpNV JApMAVUDxwUl6z97kd0eMZUiEU5gA6hyfeuNIB0kforpHoK+IwXp54FjXZdz6BA0fiUca79E4tqU GeuAAVf5s3YldHVxiElBLLfxrnInHN3gw1+KaudyvnmbwGYi9Cb8XR0Ucdv/GvnDGjEoWfEb+mgv 9xrtuPbVIpL6DHu5Bq4vtX30G5AXcPITw95cPWLsHiU6tFs2fFlaJieT1ZuJlfz56vkpDKK2csbT PpuFqUUQz+mM8JAD4ECWkBLY5j3+LqY56KwXVLdUg0ah5ko+v4i3/ve6D6GN3tdQyLKkqHpu4ImQ NSjCFzZkWFyXdwbUTMm+lgpzUbYFiyG7X+t1TW39Ja77LGPpOwBul3X3htX/IiTeQpzOfU/1muJW PvebixQdJ44tVUYBugOXkZRu7i9hiq2F2dIGpVt7fhNj6zeWP9GANChogIpDRAkItDUeJoEcUbeN ONztbH05L0kxSBv41I9o4wcr3L2rN0xIVg8gIyxajQUQ1mOqxZNZ6Vkd1Ha3Q1A2E6wNv7dvK/cK OEqlCIPGIfYQDNLMPSA9n7O4Y7McSYkIYqEQ
X-Report-Abuse-To: spam@quarantine6.antispamcloud.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-privacy/JHZ80Sikr65v22VClxVV-LdD-kc>
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: Wed, 04 Apr 2018 18:26:37 -0000

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
> <mailto:f_against@protonmail.com>> wrote:
>
>     Hello Everyone,
>
>     I want to talk about protocol, that has similar characteristics to
>     otp.
>     Are you interessted?
>
>     Greetings
>     F.
>
>     _______________________________________________
>     ietf-privacy mailing list
>     ietf-privacy@ietf.org <mailto:ietf-privacy@ietf.org>
>     https://www.ietf.org/mailman/listinfo/ietf-privacy
>     <https://www.ietf.org/mailman/listinfo/ietf-privacy>
>
>
>
>
> _______________________________________________
> ietf-privacy mailing list
> ietf-privacy@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf-privacy