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

Benjamin Kaduk <kaduk@MIT.EDU> Wed, 04 September 2013 15:56 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 254DD11E81D3 for <kitten@ietfa.amsl.com>; Wed, 4 Sep 2013 08:56:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.247
X-Spam-Level:
X-Spam-Status: No, score=-3.247 tagged_above=-999 required=5 tests=[AWL=0.352, 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 Z2MUXWiJL6z4 for <kitten@ietfa.amsl.com>; Wed, 4 Sep 2013 08:56:48 -0700 (PDT)
Received: from dmz-mailsec-scanner-2.mit.edu (dmz-mailsec-scanner-2.mit.edu [18.9.25.13]) by ietfa.amsl.com (Postfix) with ESMTP id 83E8B11E81CC for <kitten@ietf.org>; Wed, 4 Sep 2013 08:56:47 -0700 (PDT)
X-AuditID: 1209190d-b7f078e000000937-d5-5227583d13d6
Received: from mailhub-auth-1.mit.edu ( [18.9.21.35]) by dmz-mailsec-scanner-2.mit.edu (Symantec Messaging Gateway) with SMTP id 8D.7C.02359.D3857225; Wed, 4 Sep 2013 11:56:45 -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 r84FuihV001771; Wed, 4 Sep 2013 11:56:45 -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 r84FugEQ025035 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 4 Sep 2013 11:56:44 -0400
Received: (from kaduk@localhost) by multics.mit.edu (8.12.9.20060308) id r84FugZH002226; Wed, 4 Sep 2013 11:56:42 -0400 (EDT)
Date: Wed, 04 Sep 2013 11:56:42 -0400
From: Benjamin Kaduk <kaduk@MIT.EDU>
To: kitten@ietf.org
In-Reply-To: <alpine.GSO.1.10.1308062018070.24720@multics.mit.edu>
Message-ID: <alpine.GSO.1.10.1309041148130.16692@multics.mit.edu>
References: <20130806223553.CD3401A8EC@ld9781.wdf.sap.corp> <29F4D66E-3E8F-4033-8779-8EA158C1B72A@padl.com> <alpine.GSO.1.10.1308062018070.24720@multics.mit.edu>
User-Agent: Alpine 1.10 (GSO 962 2008-03-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; format="flowed"; charset="US-ASCII"
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrDIsWRmVeSWpSXmKPExsUixCmqrGsboR5k8GWPlMXRzatYLO5e+s/u wOSxZMlPJo+5H6axBDBFcdmkpOZklqUW6dslcGX8693GXLBBuOLmlR2MDYxL+bsYOTkkBEwk vjxfwAhhi0lcuLeerYuRi0NIYB+jxIzf/1ghnA2MEueu/mKEcA4ySSxaNJcFpEVIoF5i7v/Z YDaLgJbEk69P2UFsNgEViZlvNrKB2CICwhK7t75jBrGZBRQkLv/4CVTPwSEs4CyxcVcESJhT wEli6ox5YFfwCjhKPO48yw4xfiGjRFO/DogtKqAjsXr/FBaIGkGJkzOfsECMtJT4t/YX6wRG wVlIUrOQpBYwMq1ilE3JrdLNTczMKU5N1i1OTszLSy3SNdLLzSzRS00p3cQIDlRJ3h2M7w4q HWIU4GBU4uFtMFYPEmJNLCuuzD3EKMnBpCTKuzYYKMSXlJ9SmZFYnBFfVJqTWnyIUYKDWUmE V84bKMebklhZlVqUD5OS5mBREud9+vRsoJBAemJJanZqakFqEUxWhoNDSYL3ShhQo2BRanpq RVpmTglCmomDE2Q4D9DwFJAa3uKCxNzizHSI/ClGRSlx3kcgCQGQREZpHlwvLJG8YhQHekWY 9zlIFQ8wCcF1vwIazAQ0OO2zKsjgkkSElFQD40rX3ORmnpT9W6qlJ+YxPLvZeT5ybtq6/7fX Xnxc7G90+oxKdTO75PI16WL6Xu0306zbPlg88gzR/i3eVTThiMvmtVdTuESLZaZI5Av1tp1z rZZIWZx2paVlp6n/NzvrGYUXlkV3B85VmVF2vnPLrTfLLZfmXBCaaal31MjYhfHUaqt3C32O KrEUZyQaajEXFScCAJqIZQz/AgAA
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: Wed, 04 Sep 2013 15:56:54 -0000

On Tue, 6 Aug 2013, Benjamin Kaduk wrote:

> I'll tabulate these and send mail to iana@iana.org in a few days unless 
> alternate advice materializes.
> https://datatracker.ietf.org/doc/draft-ietf-abfab-gss-eap/ indicates that the 
> IESG has sent it to the RFC editor, so it may be a bit late to get it to 
> include the additional RFC 1964 token types.

It turns out that it would be easier for IANA if the abfab-gss-eap 
document which creates the registry was updated to include all the 
published values in existing RFCs.  With regard to non-final drafts, the 
document authors will probably be on the hook for getting values 
allocated:

> Unfortunately, we don't have an expert yet. I'll submit an item for
>    the next IESG telechat (on the 29th) asking an AD to find someone
>    they can designate. It may be possible to get someone designated on
>    that very telechat, but it could take longer.
>
> Finally, the authors of the in-process I-Ds need to send each request
>    to iana@iana.org themselves, if they're ready. If they suspect that
>    the details of those proposed registrations could change, they
>    should wait for IESG approval, at which point we'll make any
>    requested registrations anyway, as long as they're included in the
>    IANA Considerations section (although the values they want may not
>    be available).
>
> If they want to request specific values, I'd recommend submitting
>    their requests sooner than that, since we can't reserve values for
>    pending registrations. Whether an I-D-based request is ready for
>    registration or whether it should wait is up to the expert, though.

We mentioned a few in-progress documents:

draft-swift-win2k-krb-user2user-03 defines
    0400   KERB-TGT-REQUEST
    0401   KERB-TGT-REPLY

draft-ietf-krb-wg-iakerb-02 defines
    0501   IAKERB_PROXY

draft-howard-gss-browserid-04 section 4 defines
632C Initiator context token
432C Acceptor context token
442C Context deletion token
6D2C Initiator metadata token
4D2C Acceptor metadata token

Luke, I guess we can consider you informed, for the purposes of the 
browserid document :)

I guess we turned iakerb into a kitten wg document, so Jim should be able 
to take that on, I hope.

We might have some trouble finding an active author for U2U, though.  Once 
an expert reviewer is found for the registry, though, I suspect it won't 
be too hard to come to a resolution.

-Ben