Re: [kitten] Fwd: New Version Notification for draft-vanrein-dnstxt-krb1-05.txt

Rick van Rein <rick@openfortress.nl> Fri, 18 September 2015 11:09 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 7E29D1B2AE6 for <kitten@ietfa.amsl.com>; Fri, 18 Sep 2015 04:09:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level:
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, 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 lvRY9lz49xT2 for <kitten@ietfa.amsl.com>; Fri, 18 Sep 2015 04:09:03 -0700 (PDT)
Received: from lb1-smtp-cloud3.xs4all.net (lb1-smtp-cloud3.xs4all.net [194.109.24.22]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DA03D1B2AE5 for <kitten@ietf.org>; Fri, 18 Sep 2015 04:09:02 -0700 (PDT)
Received: from airhead.local ([83.161.146.46]) by smtp-cloud3.xs4all.net with ESMTP id Jb8y1r00810HQrX01b8zDn; Fri, 18 Sep 2015 13:09:00 +0200
Message-ID: <55FBF0C8.6090904@openfortress.nl>
Date: Fri, 18 Sep 2015 13:08:56 +0200
From: Rick van Rein <rick@openfortress.nl>
User-Agent: Postbox 3.0.11 (Macintosh/20140602)
MIME-Version: 1.0
To: Benjamin Kaduk <kaduk@MIT.EDU>
References: <20150915143628.21162.89108.idtracker@ietfa.amsl.com> <55F82DA5.10504@openfortress.nl> <alpine.GSO.1.10.1509172254390.26829@multics.mit.edu>
In-Reply-To: <alpine.GSO.1.10.1509172254390.26829@multics.mit.edu>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/kitten/qXCTzAEBVfv6eQZQgy1JzQnHi6E>
Cc: "kitten@ietf.org" <kitten@ietf.org>
Subject: Re: [kitten] Fwd: New Version Notification for draft-vanrein-dnstxt-krb1-05.txt
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: <https://mailarchive.ietf.org/arch/browse/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: Fri, 18 Sep 2015 11:09:05 -0000

Hello,

> There seems to be some level of consensus settling around using PTR for
> _kerberos.fqdn to point to a realm name, with the concordant implications
> for the case of the realm name.  Since that is using a existing DNS record
> type and making backward-incompatible changes to the Kerberos standard,

Or, we could simply say

   "All retrieved _kerberos PTR data MUST be cast to all-uppercase characters
   before processing with Kerberos and/or GSS-API.  This compensates for the
   uncertainty of case mappings in DNS.  Kerberos realms that want to be
   reachable through these PTR records MUST accept requests with the
   realm name in all-uppercase form."

This does not change the semantics of Kerberos AFAIK, and it remains open to
future changes in case handling in the KDC.  The mapping to uppercase is not
a compensation for a temporary condition, but for the permanent uncertainty
around case handling of PTR record data.

> (It is not really appropriate
> for individual submissions to make changes to Proposed Standards with
> still-extant working groups.)

Shall I formulate the above in an individual submission and leave it to Kitten
whether they want to lift it up the a WG spec?  That way we'd at least be out
of the current impasse on this matter.

Thanks,
 -Rick