IETF Logo Mail Archive

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

Stephen Farrell <stephen.farrell@cs.tcd.ie> Mon, 07 December 2015 21:39 UTC

Return-Path: <stephen.farrell@cs.tcd.ie>
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 6C3571A92FE for <ietf@ietfa.amsl.com>; Mon, 7 Dec 2015 13:39:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.311
X-Spam-Level:
X-Spam-Status: No, score=-4.311 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 yNbX-1tJhvTQ for <ietf@ietfa.amsl.com>; Mon, 7 Dec 2015 13:39:48 -0800 (PST)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 92E391A8897 for <ietf@ietf.org>; Mon, 7 Dec 2015 13:39:48 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 37014BE49; Mon, 7 Dec 2015 21:39:46 +0000 (GMT)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kdCF7_j765v8; Mon, 7 Dec 2015 21:39:45 +0000 (GMT)
Received: from [10.87.48.91] (unknown [86.46.30.27]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 4E21DBE47; Mon, 7 Dec 2015 21:39:44 +0000 (GMT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; s=mail; t=1449524385; bh=47LmC4IjZgEt0w9s/2oaKwFR2dmrWAkJybHM5ganUwU=; h=Subject:To:References:Cc:From:Date:In-Reply-To:From; b=S2wO0XA04dudUrGKTS7soGDhFsMWW13jn84ARLrJEScunqpc8O5GdybPucxxRGwV2 XqsGDByZi4p6NZl4se6kjcY6VYTHjGd6oVlBJQIfzXeQKJdxWcxVikVAxdeK4QKnuM uVDuxCB2MUgMyuyf8x5aWyWx9UxI8lPqLEl0+wOI=
Subject: Re: WG Review: CURves, Deprecating and a Little more Encryption (curdle)
To: Donald Eastlake <d3e3e3@gmail.com>, Phillip Hallam-Baker <phill@hallambaker.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> <CAF4+nEG1-9Te3QbtTn-vhntTGPnE395WHvrsZy9MtffmXJ+J3A@mail.gmail.com>
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Openpgp: id=D66EA7906F0B897FB2E97D582F3C8736805F8DA2; url=
Message-ID: <5665FC9F.3050205@cs.tcd.ie>
Date: Mon, 07 Dec 2015 21:39:43 +0000
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.4.0
MIME-Version: 1.0
In-Reply-To: <CAF4+nEG1-9Te3QbtTn-vhntTGPnE395WHvrsZy9MtffmXJ+J3A@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/23UF1XUns7lt3NYyYP7xJTH2VUc>
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:39:50 -0000


On 07/12/15 21:05, Donald Eastlake wrote:
> 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.

Please check out the curdle list archive. I raised that and I think
it's in hand though we need to make a decision as to what's best,
including considering what W3C want.

S.

> 
> 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