Re: [Uta] Proposed list of deliverables

Alexey Melnikov <alexey.melnikov@isode.com> Mon, 20 January 2014 11:51 UTC

Return-Path: <alexey.melnikov@isode.com>
X-Original-To: uta@ietfa.amsl.com
Delivered-To: uta@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6352C1A010F for <uta@ietfa.amsl.com>; Mon, 20 Jan 2014 03:51:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.536
X-Spam-Level:
X-Spam-Status: No, score=-2.536 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.535, SPF_PASS=-0.001] autolearn=ham
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 5P9a-iWZBkA8 for <uta@ietfa.amsl.com>; Mon, 20 Jan 2014 03:51:34 -0800 (PST)
Received: from waldorf.isode.com (waldorf.isode.com [62.3.217.251]) by ietfa.amsl.com (Postfix) with ESMTP id 951D21A00F1 for <uta@ietf.org>; Mon, 20 Jan 2014 03:51:34 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1390218693; d=isode.com; s=selector; i=@isode.com; bh=+BvCY4/2uSgWkNj9cR2plLgqqGj/H1NxjE6/7oc7Umg=; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version: In-Reply-To:References:Content-Type:Content-Transfer-Encoding: Content-ID:Content-Description; b=c5vsq7757VeLIUbqtJY/D+3Jz0nJxFAcmurLLywiux3+4zTEzO78EPEPgX1/fxp8F6m1Vy wu5dXiovG9B8yZgy4ZYQRTJ+QV5RZw18E+y9cnpoLhZYYLIjhtqlcBKHAw6LY9ojlmqW+R 0hfALLUQksd03xtNjQtBbKST/ttifwA=;
Received: from [172.17.128.75] (richard.isode.com [62.3.217.249]) by waldorf.isode.com (submission channel) via TCP with ESMTPSA id <Ut0NxAAIP4XD@waldorf.isode.com>; Mon, 20 Jan 2014 11:51:33 +0000
X-SMTP-Protocol-Errors: PIPELINING
Message-ID: <52DD0DC4.4010207@isode.com>
Date: Mon, 20 Jan 2014 11:51:32 +0000
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
To: "Orit Levin (LCA)" <oritl@microsoft.com>
References: <0bc674da169f4772b0fb2173ed679115@BY2PR03MB300.namprd03.prod.outlook.com>
In-Reply-To: <0bc674da169f4772b0fb2173ed679115@BY2PR03MB300.namprd03.prod.outlook.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: "uta@ietf.org" <uta@ietf.org>, Pete Resnick <presnick@qti.qualcomm.com>, Barry Leiba <barryleiba@computer.org>
Subject: Re: [Uta] Proposed list of deliverables
X-BeenThere: uta@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: UTA working group mailing list <uta.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/uta>, <mailto:uta-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/uta/>
List-Post: <mailto:uta@ietf.org>
List-Help: <mailto:uta-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/uta>, <mailto:uta-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Jan 2014 11:51:37 -0000

Hi,
This looks sensible, but I am trying to figure out how existing drafts 
fit into this plan.

On 18/01/2014 06:24, Orit Levin (LCA) wrote:
> Below is the list of deliverables for your consideration:
>
> 1. A threat analysis document containing a collection of known security breaches to application protocols due to poor use of TLS (Likely an Informational RFC)
> 2. Applications' independent document recommending best existing and future practices for using TLS (Likely a BCP or a Proposed Standard RFC)
> 3. A set of documents, each describing best existing and future practices for using TLS with a specific application protocol, i.e., SMTP, POP, IMAP, XMPP, HTTP 1.1, etc. (Case-by-case likely a BCP or a Proposed Standard RFC)
It sounds like the following 2 would cover this for SMTP/POP/IMAP:

http://datatracker.ietf.org/doc/draft-melnikov-email-tls-certs/
http://datatracker.ietf.org/doc/draft-moore-email-tls/

(Some pieces of draft-newman-email-deep might apply here as well).
> 4. A document discussing (and potentially defining) how to apply the opportunistic encryption approach (preliminary outlined in draft-farrelll-mpls-opportunistic-encrypt-00.txt) to TLS. (Category TBD)

There is a document defining this for email:
http://datatracker.ietf.org/doc/draft-newman-email-deep/

Last time I talked to Chris and Keith, they were planning to merge it 
with Keith's document:
http://datatracker.ietf.org/doc/draft-moore-email-tls/


I would like to confirm with WG chairs that the proposal above makes sense.

Best Regards,
Alexey
> Please, send your feedback to the list (including short +1s to indicate that the direction makes sense to you).
>
> Thanks,
> Leif and Orit - the chairs.