IETF Logo Mail Archive

Re: [kitten] Document Action: 'AES Encryption with HMAC-SHA2 for Kerberos 5' to Informational RFC (draft-ietf-kitten-aes-cts-hmac-sha2-11.txt)

Stephen Farrell <stephen.farrell@cs.tcd.ie> Tue, 06 September 2016 00:52 UTC

Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: kitten@ietfa.amsl.com
Delivered-To: kitten@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 40D2412B096 for <kitten@ietfa.amsl.com>; Mon, 5 Sep 2016 17:52:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.809
X-Spam-Level:
X-Spam-Status: No, score=-5.809 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, RP_MATCHES_RCVD=-1.508, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cs.tcd.ie
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 M-56RjJi2cbc for <kitten@ietfa.amsl.com>; Mon, 5 Sep 2016 17:52:31 -0700 (PDT)
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 9B65412B006 for <kitten@ietf.org>; Mon, 5 Sep 2016 17:52:31 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 0DA97BE39; Tue, 6 Sep 2016 01:52:30 +0100 (IST)
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 mUgAqssiCaoC; Tue, 6 Sep 2016 01:52:28 +0100 (IST)
Received: from [10.87.48.210] (95-45-153-252-dynamic.agg2.phb.bdt-fng.eircom.net [95.45.153.252]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id AB50FBDF9; Tue, 6 Sep 2016 01:52:27 +0100 (IST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; s=mail; t=1473123148; bh=V49zNAjtVg4VNV7OqZ2PmL6fuq/V+qN/yB3PDjoPIW0=; h=Subject:To:References:Cc:From:Date:In-Reply-To:From; b=H1mnb2iMo18vs4Rf2ntOf9RSvg4F23ot+9kMWudEZeooYw4TSfhA/XYWC+BbBtX60 1tSbSqQaPNV3jHjWITBSD7eoCPFHvbCM9hYrm2YaEUZxkwqH1miJmfYLBBkB+BPlXH yYJneaBOzp+gg0Tg4BmBNkNV/Ads8ZaQ4KxiB1tk=
To: Benjamin Kaduk <kaduk@MIT.EDU>, Jeffrey Altman <jaltman@secure-endpoints.com>
References: <147276103576.32168.16561985797578576426.idtracker@ietfa.amsl.com> <9b612ac1-0288-dc0f-92b6-9045691ea872@secure-endpoints.com> <alpine.GSO.1.10.1609051713570.5272@multics.mit.edu>
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Openpgp: id=D66EA7906F0B897FB2E97D582F3C8736805F8DA2; url=
Message-ID: <8d70c265-cb18-fb41-bfc5-b3169eb2da06@cs.tcd.ie>
Date: Tue, 06 Sep 2016 01:52:27 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0
MIME-Version: 1.0
In-Reply-To: <alpine.GSO.1.10.1609051713570.5272@multics.mit.edu>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg="sha-256"; boundary="------------ms000405000707080307040501"
Archived-At: <https://mailarchive.ietf.org/arch/msg/kitten/a_KiHxoRxSNiCDQ4JTupMQhcAYc>
Cc: kitten@ietf.org
Subject: Re: [kitten] Document Action: 'AES Encryption with HMAC-SHA2 for Kerberos 5' to Informational RFC (draft-ietf-kitten-aes-cts-hmac-sha2-11.txt)
X-BeenThere: kitten@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Common Authentication Technologies - Next Generation <kitten.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/kitten>, <mailto:kitten-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/kitten/>
List-Post: <mailto:kitten@ietf.org>
List-Help: <mailto:kitten-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/kitten>, <mailto:kitten-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Sep 2016 00:52:33 -0000


On 05/09/16 22:19, Benjamin Kaduk wrote:
> On Fri, 2 Sep 2016, Jeffrey Altman wrote:
> 
>> On 9/1/2016 4:17 PM, The IESG wrote:
>>> The IESG has approved the following document:
>>> - 'AES Encryption with HMAC-SHA2 for Kerberos 5'
>>>   (draft-ietf-kitten-aes-cts-hmac-sha2-11.txt) as Informational RFC
>>
>> Now that approval has been obtained from the IESG, can the encryption
>> and checksum type numbers be allocated by the working group or do we
>> have to wait for an IANA action?
> 
> IANA has to perform the allocation, but they seem to have already started
> taking action, as can be seen at the document history
> (https://datatracker.ietf.org/doc/draft-ietf-kitten-aes-cts-hmac-sha2/history/).
> (There was a two hour gap between the "In Progress" and "On Hold" state
> transitions.)  Maybe that means they are asking the expert, though I did
> not think that the standards action policy required such consultation.

If getting numbers assigned is important, please say why and
we can see if it can happen sooner. Shouldn't be too long at
all though.

For future reference, please see [1] (I know the WG chairs
know that, but maybe other folks may not) which allows WGs
to ask for early allocations of codepoints.

S.

[1] https://tools.ietf.org/html/rfc7120


> 
> -Ben
> 
> _______________________________________________
> Kitten mailing list
> Kitten@ietf.org
> https://www.ietf.org/mailman/listinfo/kitten
>

v2.23.0 | Report a Bug | By Email