IETF Logo Mail Archive

Re: WG Review: CURves, Deprecating and a Little more Encryption (curdle)

Donald Eastlake <d3e3e3@gmail.com> Mon, 07 December 2015 21:05 UTC

Return-Path: <d3e3e3@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 41F311A88D1 for <ietf@ietfa.amsl.com>; Mon, 7 Dec 2015 13:05:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.749
X-Spam-Level:
X-Spam-Status: No, score=-1.749 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, 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 l8kEHEEHYQF2 for <ietf@ietfa.amsl.com>; Mon, 7 Dec 2015 13:05:56 -0800 (PST)
Received: from mail-ob0-x22d.google.com (mail-ob0-x22d.google.com [IPv6:2607:f8b0:4003:c01::22d]) (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 26FAD1A88C9 for <ietf@ietf.org>; Mon, 7 Dec 2015 13:05:56 -0800 (PST)
Received: by obciw8 with SMTP id iw8so35338068obc.1 for <ietf@ietf.org>; Mon, 07 Dec 2015 13:05:55 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=yVFTLpxZ5+gqc4U2rOcMT1zdT8GawVHCJ3DglC2dEPo=; b=g+07d/NYVrN5j3ssbhx0mYA3M9jdSkUoGyg6TEAi9A3DzzF2BN1PdTe5lrx7sQLKP1 awThABbgi5zxPJhFvKfWNckwkzg+2yLIP3KfTN2CZcJTHg628cxmDSTgjrHa3X6ilVgG E5FXDYjYtcw5I5MNYJ61OUYJZ/vs+tz42xLiD6OnxvOuk+EBncrc2oECfo0KtJGTd3Jn fGEc7+p5dJo0D2OTgbtNK5djzuNjaogE22zE3/N7HOnqp8phhfqsq6FKKnvZF+j2eZls FxQs41OHkatQ6mqFQBrB79GWsJhhbja1nQqeJ/uQJ25YaSzr9S31UH4kN4pFBmE7wYoY 5t6w==
X-Received: by 10.182.79.200 with SMTP id l8mr21938037obx.18.1449522355428; Mon, 07 Dec 2015 13:05:55 -0800 (PST)
MIME-Version: 1.0
Received: by 10.76.19.102 with HTTP; Mon, 7 Dec 2015 13:05:40 -0800 (PST)
In-Reply-To: <CAMm+LwhzJVOcTdHjaiXbXVFV3hu6wDKtfE1CovH7pzwGnf_oQQ@mail.gmail.com>
References: <20151204170507.5160.44472.idtracker@ietfa.amsl.com> <56656C43.5070501@alvestrand.no> <56656DD2.9010609@cs.tcd.ie> <CAMm+LwhfJGvE-LvxJwRzRHjpcohQtSnhodF5a7rmbh_Foc5fBw@mail.gmail.com> <5665C419.6060201@cs.tcd.ie> <CAMm+LwhzJVOcTdHjaiXbXVFV3hu6wDKtfE1CovH7pzwGnf_oQQ@mail.gmail.com>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Mon, 07 Dec 2015 16:05:40 -0500
Message-ID: <CAF4+nEG1-9Te3QbtTn-vhntTGPnE395WHvrsZy9MtffmXJ+J3A@mail.gmail.com>
Subject: Re: WG Review: CURves, Deprecating and a Little more Encryption (curdle)
To: Phillip Hallam-Baker <phill@hallambaker.com>, Stephen Farrell <stephen.farrell@cs.tcd.ie>
Content-Type: multipart/alternative; boundary="089e0122a88216e377052655391d"
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/3qDcm6DnSu6cr9jCQtK6FGfJ8ng>
Cc: Harald Alvestrand <harald@alvestrand.no>, IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 07 Dec 2015 21:05:57 -0000

On Mon, Dec 7, 2015 at 3:53 PM, Phillip Hallam-Baker <phill@hallambaker.com>
wrote:

> ...
>
> Fair enough. I just want to make sure that this is inclusive.
>
> One other related question is XML Encryption. given that all that is
> needed to define code points in XML Encryption is to generate a URL, I
> suggest that there be some sort of statement in the charter that allows
> that to happen, whether through a liaison with W3C or just doing it.
>

Just as a side note,  I currently
maintain draft-eastlake-rfc6931bis-xmlsec-uris as a place where XML
Security URIs can be accumulated.

Thanks,
Donald
=============================
 Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
 155 Beaver Street, Milford, MA 01757 USA
 d3e3e3@gmail.com

v2.23.0 | Report a Bug | By Email