Re: [Endymail] Another view of the problem and what the IETF could do

Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com> Wed, 03 September 2014 14:56 UTC

Return-Path: <kathleen.moriarty.ietf@gmail.com>
X-Original-To: endymail@ietfa.amsl.com
Delivered-To: endymail@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AA0BA1A03C2 for <endymail@ietfa.amsl.com>; Wed, 3 Sep 2014 07:56:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.399
X-Spam-Level:
X-Spam-Status: No, score=-1.399 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, J_CHICKENPOX_14=0.6, SPF_PASS=-0.001] autolearn=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 feqwAzguyyHU for <endymail@ietfa.amsl.com>; Wed, 3 Sep 2014 07:56:27 -0700 (PDT)
Received: from mail-la0-x22f.google.com (mail-la0-x22f.google.com [IPv6:2a00:1450:4010:c03::22f]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BF4CF1A03E6 for <endymail@ietf.org>; Wed, 3 Sep 2014 07:55:37 -0700 (PDT)
Received: by mail-la0-f47.google.com with SMTP id el20so1408857lab.34 for <endymail@ietf.org>; Wed, 03 Sep 2014 07:55:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=EM0si6C2bdhrEmX4J3vNkGlwT32V/75ztPWr1OSntO8=; b=dJEyA/iPxJjFnSZnm494EInjPLUzy603sbhc+RZ+mLG9V/DE3lugI17MsmHGBXu3OF ijEytM0AFxRpeDWiFkZ+u2bA0ZdoUazjxySuWbhJMNfcmfJecYTL8YQpO5M6xYxMScP/ HDLkVlQ8OORu2IcLmd3iaNvi1y5Ex0RUw17Y5xzNYEoYGQ2sO4/XMxfcCeNfP3tyRYz3 GwecTBIUXBzzydp8zHQoL/lOEB3bUl+bjAQtAUifwXktf7k/avV3G6ray83JCy7Etyhr cOHGo7tUq6iw7yjKCQyCavS4eHClkPcaKBK5QA0k8Ar+ndACpMlVnZQz1b0ZdFIo76nZ Bl2w==
MIME-Version: 1.0
X-Received: by 10.112.169.35 with SMTP id ab3mr39334281lbc.41.1409756135975; Wed, 03 Sep 2014 07:55:35 -0700 (PDT)
Received: by 10.112.64.170 with HTTP; Wed, 3 Sep 2014 07:55:35 -0700 (PDT)
In-Reply-To: <87egvtjhhe.fsf@vigenere.g10code.de>
References: <CAHBU6iuxfqs9RszSaJLaTV_obKBCJ9Pzii+t9XANN3q+bJm-3Q@mail.gmail.com> <878um3prio.fsf@vigenere.g10code.de> <cddbc815-a98a-48e5-8dea-c3d8a68ca4d9@gulbrandsen.priv.no> <87y4u2laqh.fsf@vigenere.g10code.de> <20140902114217.lp_a_yD8%sdaoden@yandex.com> <20140902160206.GA7900@vegoda.org> <5405EEB8.1060107@cs.tcd.ie> <87egvtjhhe.fsf@vigenere.g10code.de>
Date: Wed, 3 Sep 2014 10:55:35 -0400
Message-ID: <CAHbuEH5q4MBno379mwZzRZibH5o3=gi-YY4e-JDV4dhxoFUjYA@mail.gmail.com>
From: Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com>
To: Werner Koch <wk@gnupg.org>
Content-Type: multipart/alternative; boundary=001a11c2696ab46f9c05022a6d65
Archived-At: http://mailarchive.ietf.org/arch/msg/endymail/y082tFH4ue7KY6hH5ReSumxLNrk
Cc: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>, Leo Vegoda <leo@vegoda.org>, endymail@ietf.org, Stephen Farrell <stephen.farrell@cs.tcd.ie>
Subject: Re: [Endymail] Another view of the problem and what the IETF could do
X-BeenThere: endymail@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <endymail.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/endymail>, <mailto:endymail-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/endymail/>
List-Post: <mailto:endymail@ietf.org>
List-Help: <mailto:endymail-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/endymail>, <mailto:endymail-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Sep 2014 14:56:31 -0000

On Wed, Sep 3, 2014 at 3:22 AM, Werner Koch <wk@gnupg.org> wrote:

> On Tue,  2 Sep 2014 18:22, stephen.farrell@cs.tcd.ie said:
>
> > Similarly, if the list concludes that users have to understand
> > keys then that's also easy - we know that will never happen
> > and so could also call it a day.
>
> Users do understand mail addresses and thus a key should be identified
> by the mail address and not by any other property.
>
> > reinvent X.400 email security here please? (Or PEM, or MOSS,
>
> What problem do you see with MOSS?  Except for the commonly ignored
> micalg parameter it is a well working part of MIME and not a problem at
> all.  This is true for S?MIME as well as for PGP/MIME.  We are still
> talking about mail, tight?  Or is the goal of the list to replace the
> rfc822 mail format - that will never happen in the foreseeable future.
>

I think we should be open to a possible change for messaging in general and
not limit ourselves to mail.

>
>
> Salam-Shalom,
>
>    Werner
>
> --
> Die Gedanken sind frei.  Ausnahmen regelt ein Bundesgesetz.
>
> _______________________________________________
> Endymail mailing list
> Endymail@ietf.org
> https://www.ietf.org/mailman/listinfo/endymail
>



-- 

Best regards,
Kathleen