IETF Logo Mail Archive

Re: [kitten] draft-ietf-kitten-kerberos-iana-registries -- KerberosFlags limited to 0..31?

Rick van Rein <rick@openfortress.nl> Wed, 23 July 2014 10:46 UTC

Return-Path: <rick@openfortress.nl>
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 191061A017E for <kitten@ietfa.amsl.com>; Wed, 23 Jul 2014 03:46:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.594
X-Spam-Level: *
X-Spam-Status: No, score=1.594 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, HELO_EQ_NL=0.55, HOST_EQ_NL=1.545, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no
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 m74Ky4QPYp_W for <kitten@ietfa.amsl.com>; Wed, 23 Jul 2014 03:46:09 -0700 (PDT)
Received: from smtp-vbr4.xs4all.nl (smtp-vbr4.xs4all.nl [194.109.24.24]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 63BAB1A00A3 for <kitten@ietf.org>; Wed, 23 Jul 2014 03:46:08 -0700 (PDT)
Received: from [10.0.1.225] (phantom.vanrein.org [83.161.146.46]) (authenticated bits=0) by smtp-vbr4.xs4all.nl (8.13.8/8.13.8) with ESMTP id s6NAk4BH030917 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 23 Jul 2014 12:46:05 +0200 (CEST) (envelope-from rick@openfortress.nl)
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
Content-Type: text/plain; charset="windows-1252"
From: Rick van Rein <rick@openfortress.nl>
In-Reply-To: <53CD270A.4030102@mit.edu>
Date: Wed, 23 Jul 2014 12:46:04 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <0B295561-1AB0-481B-BCB0-6D8C1F106944@openfortress.nl>
References: <93975EF5-D151-417E-8043-6B54D36FD9DC@openfortress.nl> <53CD270A.4030102@mit.edu>
To: Greg Hudson <ghudson@mit.edu>
X-Mailer: Apple Mail (2.1878.6)
X-Virus-Scanned: by XS4ALL Virus Scanner
Archived-At: http://mailarchive.ietf.org/arch/msg/kitten/g7-D78IX0o1bwAv4YTTI7o59GFc
Cc: kitten@ietf.org
Subject: Re: [kitten] draft-ietf-kitten-kerberos-iana-registries -- KerberosFlags limited to 0..31?
X-BeenThere: kitten@ietf.org
X-Mailman-Version: 2.1.15
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, 23 Jul 2014 10:46:11 -0000

Hi,

> I believe this is in deference to implementations which store flag
> values in fixed 32-bit flags.

I’m fairly new to this list, so I may have missed that discussion.

> If the IETF decides that this implementation cost is warranted, the
> standards action which assigns the flag value could amend the registry
> to accomodate it.

So you are saying that the Kitten list has agreed to do it this way?

IMHO, standards should not be dictated by software; it ought to be the
other way around, thus celebrating the soft in software.  It will take long
before we run over the 32 bits, and by then software could be adapted.
Meanwhile, we’re not introducing a “64 kB ought to be enough for everyone”.

But, if all this has been discussed in the past and the group has decided
in favour of the current proposal than I feel it is warranted to ignore this opinion.

-Rick

v2.23.0 | Report a Bug | By Email