IETF Logo Mail Archive

Re: [kitten] Updating IANA krb5 GSSAPI token type registry

Tom Yu <tlyu@MIT.EDU> Tue, 06 August 2013 21:17 UTC

Return-Path: <tlyu@mit.edu>
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 3A17521F991F for <kitten@ietfa.amsl.com>; Tue, 6 Aug 2013 14:17:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.599
X-Spam-Level:
X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aCEwbuA6qWM2 for <kitten@ietfa.amsl.com>; Tue, 6 Aug 2013 14:17:24 -0700 (PDT)
Received: from dmz-mailsec-scanner-8.mit.edu (dmz-mailsec-scanner-8.mit.edu [18.7.68.37]) by ietfa.amsl.com (Postfix) with ESMTP id 3D27621F9967 for <kitten@ietf.org>; Tue, 6 Aug 2013 14:17:23 -0700 (PDT)
X-AuditID: 12074425-b7f0c8e000000953-bf-520167e211b0
Received: from mailhub-auth-1.mit.edu ( [18.9.21.35]) by dmz-mailsec-scanner-8.mit.edu (Symantec Messaging Gateway) with SMTP id BF.D8.02387.2E761025; Tue, 6 Aug 2013 17:17:22 -0400 (EDT)
Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) by mailhub-auth-1.mit.edu (8.13.8/8.9.2) with ESMTP id r76LHGBm028763; Tue, 6 Aug 2013 17:17:17 -0400
Received: from cathode-dark-space.mit.edu (cathode-dark-space.mit.edu [18.18.1.96]) (authenticated bits=56) (User authenticated as tlyu@ATHENA.MIT.EDU) by outgoing.mit.edu (8.13.8/8.12.4) with ESMTP id r76LHEGV022366 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 6 Aug 2013 17:17:16 -0400
Received: (from tlyu@localhost) by cathode-dark-space.mit.edu (8.12.9.20060308) id r76LHEWK008271; Tue, 6 Aug 2013 17:17:14 -0400 (EDT)
To: Benjamin Kaduk <kaduk@mit.edu>
References: <20130411064110.29519.86993.idtracker@ietfa.amsl.com> <alpine.GSO.1.10.1308051657030.24720@multics.mit.edu> <alpine.GSO.1.10.1308061642470.24720@multics.mit.edu>
From: Tom Yu <tlyu@MIT.EDU>
Date: Tue, 06 Aug 2013 17:17:14 -0400
In-Reply-To: <alpine.GSO.1.10.1308061642470.24720@multics.mit.edu> (Benjamin Kaduk's message of "Tue, 6 Aug 2013 16:43:53 -0400 (EDT)")
Message-ID: <ldvsiym4izp.fsf@cathode-dark-space.mit.edu>
Lines: 24
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrAIsWRmVeSWpSXmKPExsUixCmqrPsonTHIYNU/PYujm1exODB6LFny kymAMYrLJiU1J7MstUjfLoEro/PsdKaCtRwVPw79YW9g/MTWxcjJISFgInHn3xEmCFtM4sK9 9UBxLg4hgX2MEuf+NUA5G4Cc6evZIZyzTBI/zk5jhXA6GSVen9nLCNIvIqAksfhsC9hcZgFh ieVrzgLZHBzCAs4SG3dFQNRvZJQ4/2gbC0icTUBa4ujiMpByFgFVicOPj4Bt4xRoZ5To+QGy gJODV8BC4sfjFewgNo8Ap8Tkbz3MEHFBiZMzn7BA7NKSuPHvJdMERsFZSFKzkKQWMDKtYpRN ya3SzU3MzClOTdYtTk7My0st0rXQy80s0UtNKd3ECApMdhfVHYwTDikdYhTgYFTi4a0QYwwS Yk0sK67MPcQoycGkJMp7LRkoxJeUn1KZkVicEV9UmpNafIhRgoNZSYTXRwIox5uSWFmVWpQP k5LmYFES533+9GygkEB6YklqdmpqQWoRTFaGg0NJgndzGlCjYFFqempFWmZOCUKaiYMTZDgP 0PC5IDW8xQWJucWZ6RD5U4y6HJPPbnnPKMSSl5+XKiXOWwdSJABSlFGaBzcHllBeMYoDvSXM uxGkigeYjOAmvQJawgS0xOMkA8iSkkSElFQDo3TevafZ5xZU8p+NUxV+OP3t6WVmX6xfFpjI up7vbzViD5/QO2Vlo//LybYvZBI1Az3q/3T0TA1t6O2a51TwMMjElMusgpUhZ5Wmp4Bk8Em5 6OdLpR7euTpDYXZDWn+m75nJV7Z68s5k0n70LP+uSrXInMXanEzX9sxeVrlTaPWZC9GTco+l KbEUZyQaajEXFScCADMLdXIDAwAA
Cc: kitten@ietf.org
Subject: Re: [kitten] Updating IANA krb5 GSSAPI token type registry
X-BeenThere: kitten@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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 Aug 2013 21:17:29 -0000

Benjamin Kaduk <kaduk@MIT.EDU> writes:

> On Tue, 6 Aug 2013, Benjamin Kaduk wrote:
>
>> Looking up the TOK_ID for IAKERB_PROXY (or rather, how assignments
>> of such values are performed) reveals that the IANA registry for
>> token types is
>> incomplete(!). http://www.iana.org/assignments/kerberos-v-gss-api/kerberos-v-gss-api.xhtml#token-types
>> lists only 0100, 0200, 0300, 0404, 0504, 0601, and 0602 as assigned,
>> but 0101, 0201, and 0102 are documented in RFC1964.
>> Unfortunately, I still don't have an understanding of the rationale
>> behind TOK_ID assignments; the current set seems quite sparse.
>
> What is the mechanism to get IANA to update the registry with the
> additional values from RFC 1964?

It seems like GSS-EAP establishes the registry:

    http://tools.ietf.org/html/draft-ietf-abfab-gss-eap-09

and the allocation procedure for TOK_ID values is expert review.  I'm
also noticing that the RFC 4121 reserved values for 6000 through 60ff
(see section 4.4) are not marked as reserved in the registry for some
reason.

v2.23.0 | Report a Bug | By Email