IETF Logo Mail Archive

[kitten] Updating IANA krb5 GSSAPI token type registry

Benjamin Kaduk <kaduk@MIT.EDU> Tue, 06 August 2013 20:44 UTC

Return-Path: <kaduk@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 4B43211E80D1 for <kitten@ietfa.amsl.com>; Tue, 6 Aug 2013 13:44:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level:
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 Qa2BiuL4iWMH for <kitten@ietfa.amsl.com>; Tue, 6 Aug 2013 13:43:58 -0700 (PDT)
Received: from dmz-mailsec-scanner-6.mit.edu (dmz-mailsec-scanner-6.mit.edu [18.7.68.35]) by ietfa.amsl.com (Postfix) with ESMTP id D7E7421F9EC3 for <kitten@ietf.org>; Tue, 6 Aug 2013 13:43:57 -0700 (PDT)
X-AuditID: 12074423-b7f168e00000095a-d0-5201600cf739
Received: from mailhub-auth-1.mit.edu ( [18.9.21.35]) by dmz-mailsec-scanner-6.mit.edu (Symantec Messaging Gateway) with SMTP id A1.A5.02394.C0061025; Tue, 6 Aug 2013 16:43:56 -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 r76KhuFN024730 for <kitten@ietf.org>; Tue, 6 Aug 2013 16:43:56 -0400
Received: from multics.mit.edu (system-low-sipb.mit.edu [18.187.2.37]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.13.8/8.12.4) with ESMTP id r76KhrFu010356 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <kitten@ietf.org>; Tue, 6 Aug 2013 16:43:56 -0400
Received: (from kaduk@localhost) by multics.mit.edu (8.12.9.20060308) id r76KhrgY010097; Tue, 6 Aug 2013 16:43:53 -0400 (EDT)
Date: Tue, 06 Aug 2013 16:43:53 -0400
From: Benjamin Kaduk <kaduk@MIT.EDU>
To: kitten@ietf.org
In-Reply-To: <alpine.GSO.1.10.1308051657030.24720@multics.mit.edu>
Message-ID: <alpine.GSO.1.10.1308061642470.24720@multics.mit.edu>
References: <20130411064110.29519.86993.idtracker@ietfa.amsl.com> <alpine.GSO.1.10.1308051657030.24720@multics.mit.edu>
User-Agent: Alpine 1.10 (GSO 962 2008-03-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"; format="flowed"
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrIIsWRmVeSWpSXmKPExsUixCmqrMuTwBhksHaLhcXRzatYHBg9liz5 yRTAGMVlk5Kak1mWWqRvl8CVseDLK8aCjawVD5cuYGlg3MzSxcjJISFgInHt2mQmCFtM4sK9 9WwgtpDAPkaJzm2MXYxcQPYxRok9f7YzQTjXmSRu7X3G3sXIAeTUS9xaLAjSwCKgJfHr9Q6w ZjYBFYmZbzaC2SICwhK7t75jBrGFBcwkZj+6A2ZzCjhJbH59jR3E5hVwlJj+ax0zxOJyiSOf r7GC2KICOhKr909hgagRlDg58wmYzSxgKXHuz3W2CYwCs5CkZiFJLWBkWsUom5JbpZubmJlT nJqsW5ycmJeXWqRrppebWaKXmlK6iREUeuwuyjsY/xxUOsQowMGoxMN7QYIxSIg1say4MvcQ oyQHk5Iob1EUUIgvKT+lMiOxOCO+qDQntfgQowQHs5IIrw9IOW9KYmVValE+TEqag0VJnPfZ 07OBQgLpiSWp2ampBalFMFkZDg4lCd4bsUCNgkWp6akVaZk5JQhpJg5OkOE8QMOl4kGGFxck 5hZnpkPkTzHqckw+u+U9oxBLXn5eqpQ47zmQQQIgRRmleXBzYCnjFaM40FvCvN0gVTzAdAM3 6RXQEiagJR4nGUCWlCQipKQaGIPi3ne+CzH7NOVYhoTXezurGyffnAo1yXzy4PzLvRuW/HhQ dk0nfcHCn9KyzSWcVXkdfEeU2Zaf2bJ529lPZl8nbml92N+h0luyX1aP5cK7Y6cYVvyNqFJ8 XlMW0eFh8f06T/Wvxp7QxcfVp1cu+WdWqdx/zdDkouL0o3w5eutiZq1XmrpM3kmJpTgj0VCL uag4EQCDOnGE9AIAAA==
Subject: [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 20:44:14 -0000

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?

-Ben

v2.23.0 | Report a Bug | By Email