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

mrex@sap.com (Martin Rex) Tue, 04 March 2014 21:48 UTC

Return-Path: <mrex@sap.com>
X-Original-To: kitten@ietfa.amsl.com
Delivered-To: kitten@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 543E61A00FF for <kitten@ietfa.amsl.com>; Tue, 4 Mar 2014 13:48:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.552
X-Spam-Level:
X-Spam-Status: No, score=-6.552 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_HI=-5, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] 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 ETvlu16-DAxn for <kitten@ietfa.amsl.com>; Tue, 4 Mar 2014 13:47:59 -0800 (PST)
Received: from smtpde02.sap-ag.de (smtpde02.sap-ag.de [155.56.68.140]) by ietfa.amsl.com (Postfix) with ESMTP id 6F6E71A0139 for <kitten@ietf.org>; Tue, 4 Mar 2014 13:47:59 -0800 (PST)
Received: from mail05.wdf.sap.corp by smtpde02.sap-ag.de (26) with ESMTP id s24LlsVB026394 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 4 Mar 2014 22:47:54 +0100 (MET)
In-Reply-To: <alpine.GSO.1.10.1403041135510.1213@multics.mit.edu>
To: Benjamin Kaduk <kaduk@MIT.EDU>
Date: Tue, 04 Mar 2014 22:47:54 +0100
X-Mailer: ELM [version 2.4ME+ PL125 (25)]
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="US-ASCII"
Message-Id: <20140304214754.32AC81AC3B@ld9781.wdf.sap.corp>
From: mrex@sap.com
X-SAP: out
Archived-At: http://mailarchive.ietf.org/arch/msg/kitten/OngaQbcLvMsIZbtBc1g_7FIqSfM
Cc: kitten@ietf.org
Subject: Re: [kitten] Updating IANA krb5 GSSAPI token type registry
X-BeenThere: kitten@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: mrex@sap.com
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, 04 Mar 2014 21:48:03 -0000

Benjamin Kaduk wrote:
> 
> In particular, the value 0405 from draft-ietf-krb-wg-gssapi-cfx-02 which 
> was removed before that document became RFC 4121, and the value 0501 from 
> draft-ietf-kitten-iakerb-00 (now -01), were not added.
>
>  [...]
> 
> To me, this seems like a(nother) bug in RFC 7055, but of course it is not 
> one that can be reasonably fixed.  I guess that the easiest way forward is 
> to publish a quick document that reserves 0405 and 0501 noting that they 
> were in use before the registry was established.

This should be easily fixed with a small amount of common sense
applied by consenting AD & WG chairs, no documents necesssary.

As long as we're not facing depletion of the pool, simply marking
the code point as "Reserved to avoid conflicts" should be feasible.

See the TLS cipher suites registry for comparison:

   http://www.iana.org/assignments/tls-parameters/tls-parameters.xhtml#tls-parameters-4

   cipher suite code points 0x00, 0x040  through  0x00, 0x60
   that are in the "Standards Action" range


-Martin