[Medup] Issues draft-birk-pep-trustwords (was: New Version Notification for draft-birk-pep-trustwords-03.txt)

Bernie Hoeneisen <bernie@ietf.hoeneisen.ch> Fri, 22 March 2019 22:55 UTC

Return-Path: <bernie@ietf.hoeneisen.ch>
X-Original-To: medup@ietfa.amsl.com
Delivered-To: medup@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7C6DD1310FD for <medup@ietfa.amsl.com>; Fri, 22 Mar 2019 15:55:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, URIBL_BLOCKED=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 BF-GdNUhzn87 for <medup@ietfa.amsl.com>; Fri, 22 Mar 2019 15:55:43 -0700 (PDT)
Received: from softronics.hoeneisen.ch (softronics.hoeneisen.ch [62.2.86.178]) (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 24D021310DD for <medup@ietf.org>; Fri, 22 Mar 2019 15:55:42 -0700 (PDT)
Received: from localhost ([127.0.0.1]) by softronics.hoeneisen.ch with esmtp (Exim 4.86_2) (envelope-from <bernie@ietf.hoeneisen.ch>) id 1h7T4e-0002jK-Di for medup@ietf.org; Fri, 22 Mar 2019 23:55:40 +0100
Date: Fri, 22 Mar 2019 23:55:40 +0100
From: Bernie Hoeneisen <bernie@ietf.hoeneisen.ch>
X-X-Sender: bhoeneis@softronics.hoeneisen.ch
To: IETF MEDUP ML <medup@ietf.org>
In-Reply-To: <c3e504db-695d-dd2a-5e6f-8d4cbb60c540@pep.foundation>
Message-ID: <alpine.DEB.2.20.1903222318030.28768@softronics.hoeneisen.ch>
References: <155234487151.23050.3654986147342430959.idtracker@ietfa.amsl.com> <c3e504db-695d-dd2a-5e6f-8d4cbb60c540@pep.foundation>
User-Agent: Alpine 2.20 (DEB 67 2015-01-07)
MIME-Version: 1.0
Content-Type: multipart/mixed; BOUNDARY="37663318-639557791-1553295340=:28768"
X-SA-Exim-Connect-IP: 127.0.0.1
X-SA-Exim-Mail-From: bernie@ietf.hoeneisen.ch
X-SA-Exim-Scanned: No (on softronics.hoeneisen.ch); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/medup/X3G6gMZzl8YFn9yqoOuSn024CSM>
Subject: [Medup] Issues draft-birk-pep-trustwords (was: New Version Notification for draft-birk-pep-trustwords-03.txt)
X-BeenThere: medup@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Missing Elements for Decentralized and Usable Privacy <medup.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/medup>, <mailto:medup-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/medup/>
List-Post: <mailto:medup@ietf.org>
List-Help: <mailto:medup-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/medup>, <mailto:medup-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Mar 2019 22:55:47 -0000

Dear MEDUP list

The IANA Registration for trustwords (a basic concept applied in pEp)
https://www.ietf.org/internet-drafts/draft-birk-pep-trustwords-03.txt
has several open issues, we'd need your feedback on, e.g.:


1) Localization:
    How should non-ASCII-7bit letters or language symbols be represented
    in the wordlists? UTF-8? HTML-like encoding? IDNA? Any better solution?


2) Registration format:
    The format for registrations of at IANA is normaly (peudo-)XML.
    While XML is concise for registering wordlists, the files
    for registration will contain lot of XML overhead and thus get rather
    long. Is this an issue? Use another format, e.g. CSV?


3) ISO language code:
    Which ISO language code either 639-1 or 639-3 shall be used, to
    designate the language, i.e.,
    ISO-639-1 (e.g., ca, de, en, ...) as currently used in pEp
    implementations (running code) or ISO-639-3 (eng, deu, ita, ...)
    With ISO-639-3 more languages can be addressed, in particular
    less widespread languages and dialects.


4) Bitsize (how many bits can be mapped with a wordlist):
    e.g. a bitsize of 16 allows for a list containing 2^16 = 655536 words.

    Should this be kept open or should only certain values for bitsize
    be allowed to be registerd?
    If latter applies, which values are useful (e.g. 8, 12 and 16)


Looking forward to your input!


So long!

  Bernie





On Tue, 19 Mar 2019, Hernâni Marques (p≡p foundation) wrote:

> Dear MEDUP list
>
> Please be aware of the trustwords drafts (now in rev 03), which -- as is
> -- is a mapping of fingerprints to natural language words: in messaging
> contexts, it's usuable to authenticate peers in a less cumbersome way.
>
> Greets
>
> Hernani
>
> -------- Forwarded Message --------
> Subject: New Version Notification for draft-birk-pep-trustwords-03.txt
> Date: Mon, 11 Mar 2019 15:54:31 -0700
> From: internet-drafts@ietf.org
> To: Bernie Hoeneisen (bernhard.hoeneisen AT ucom.ch)
> <bernie@ietf.hoeneisen.ch>, Volker Birk <volker.birk@pep.foundation>,
> Hernani Marques <hernani.marques@pep.foundation>
>
>
> A new version of I-D, draft-birk-pep-trustwords-03.txt
> has been successfully submitted by Hernani Marques and posted to the
> IETF repository.
>
> Name:		draft-birk-pep-trustwords
> Revision:	03
> Title:		IANA Registration of Trustword Lists: Guide, Template and IANA
> Considerations
> Document date:	2019-03-11
> Group:		Individual Submission
> Pages:		14
> URL:
> https://www.ietf.org/internet-drafts/draft-birk-pep-trustwords-03.txt
> Status:         https://datatracker.ietf.org/doc/draft-birk-pep-trustwords/
> Htmlized:       https://tools.ietf.org/html/draft-birk-pep-trustwords-03
> Htmlized:
> https://datatracker.ietf.org/doc/html/draft-birk-pep-trustwords
> Diff:
> https://www.ietf.org/rfcdiff?url2=draft-birk-pep-trustwords-03
>
> Abstract:
>   This document specifies the IANA Registration Guidelines for
>   Trustwords, describes corresponding registration procedures, and
>   provides a guideline for creating Trustword list specifications.
>
>   Trustwords are common words in a natural language (e.g., English) to
>   which the hexadecimal strings are mapped to.  This makes verification
>   processes (e.g., comparison of fingerprints), more practical and less
>   prone to misunderstandings.
>
>
>
>
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at tools.ietf.org.
>
> The IETF Secretariat
>
>