Re: [Uta] Alissa Cooper's Discuss on draft-ietf-uta-tls-bcp-09: (with DISCUSS and COMMENT)

Peter Saint-Andre - &yet <peter@andyet.net> Tue, 17 February 2015 21:31 UTC

Return-Path: <peter@andyet.net>
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 CEF631A90CC for <uta@ietfa.amsl.com>; Tue, 17 Feb 2015 13:31:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level:
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, 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 XGkscnubTaiw for <uta@ietfa.amsl.com>; Tue, 17 Feb 2015 13:31:21 -0800 (PST)
Received: from mail-ie0-f171.google.com (mail-ie0-f171.google.com [209.85.223.171]) (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 6D3FB1A90DD for <uta@ietf.org>; Tue, 17 Feb 2015 13:31:19 -0800 (PST)
Received: by iecrp18 with SMTP id rp18so28762240iec.1 for <uta@ietf.org>; Tue, 17 Feb 2015 13:31:18 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=67iPFGrYcCEXSpb5MJ+rbW+xkPqmO6WJ8YSqqcmOxNU=; b=EXcGtA1ig8NxN30/Xaps3fDnP3vIyXz/60iX53uVJUcIB7AKGy1wZVxCR55928alUe tgvlUVKARRozPXYVSC9qZVvh1oADuS5uO3Q985K9AtOMqS29JO2UVp29J0WHc5YX+LqS Safi0hA61QUeBKl+qNtDX2F2BsFa3H9HdVkTbDV+VshmwzYQzj4gzVlhU3ZY/5Bz2Pvf vYxEvHqDjCzGcW9PYOF9vX7J8VcGQVXsOF8mE/GkDr8Dv5flo0ysopaqyhSyRI2lx0Ps p2C8YjNM0JWJ6H5xsONHkEc44UJbAbzhwpUjd46Rlm1WrmeWyrBOQvkoenlle2CCYb00 Dl8A==
X-Gm-Message-State: ALoCoQkX/k43k+EZORSyrMQwZvq1UgzRcaESJU2o3E2MURBlhBGBMfa3FttWG8YasF7atJ3FgvLy
X-Received: by 10.107.35.145 with SMTP id j139mr39280053ioj.11.1424208678851; Tue, 17 Feb 2015 13:31:18 -0800 (PST)
Received: from aither.local (c-73-34-202-214.hsd1.co.comcast.net. [73.34.202.214]) by mx.google.com with ESMTPSA id p138sm11903550ioe.9.2015.02.17.13.31.17 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 17 Feb 2015 13:31:18 -0800 (PST)
Message-ID: <54E3B324.8090006@andyet.net>
Date: Tue, 17 Feb 2015 14:31:16 -0700
From: Peter Saint-Andre - &yet <peter@andyet.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
MIME-Version: 1.0
To: Pete Resnick <presnick@qti.qualcomm.com>
References: <20150217194951.32741.94403.idtracker@ietfa.amsl.com> <54E39F72.9000709@andyet.net> <54E3AE7C.9040303@qti.qualcomm.com>
In-Reply-To: <54E3AE7C.9040303@qti.qualcomm.com>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/uta/Ljx06ADP1ktrhnGhHz8-cV7TvCs>
Cc: oritl@microsoft.com, uta@ietf.org, Alissa Cooper <alissa@cooperw.in>, uta-chairs@ietf.org, The IESG <iesg@ietf.org>, draft-ietf-uta-tls-bcp.all@ietf.org
Subject: Re: [Uta] Alissa Cooper's Discuss on draft-ietf-uta-tls-bcp-09: (with DISCUSS and COMMENT)
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: Tue, 17 Feb 2015 21:31:22 -0000

On 2/17/15 2:11 PM, Pete Resnick wrote:
> On 2/17/15 2:07 PM, Peter Saint-Andre - &yet wrote:
>
>> On 2/17/15 12:49 PM, Alissa Cooper wrote:
>>
>>> So my question is whether we should consider this document effectively
>>> silent about the choice of cipher suites to be used when we
>>> standardize a
>>> new application protocol in the IETF, or an update to an existing
>>> protocol.
>>
>> If an application protocol wishes to follow the recommendations here,
>> someone needs to write a document that says so.
>
> What about new protocols?

Right, I was thinking of existing protocols. For new protocols, I do 
think it makes sense to reference this BCP. Something vaguely along the 
lines of what we did in RFC 6648 seems sensible.

>>> That is the impression that I get from the text right now, and
>>> it doesn't quite match the way we've been using/citing the document in
>>> some recent discussions of other drafts.
>>
>> Do you have examples?
>
> http://tools.ietf.org/html/draft-ietf-paws-protocol-20#section-7

Thanks. That reference seems fine to me.

Peter

-- 
Peter Saint-Andre
https://andyet.com/