Re: [kitten] shepherd review of draft-ietf-kitten-krb-auth-indicator-02

Nathaniel McCallum <npmccallum@redhat.com> Wed, 28 September 2016 16:50 UTC

Return-Path: <npmccallum@redhat.com>
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 6A36312B635 for <kitten@ietfa.amsl.com>; Wed, 28 Sep 2016 09:50:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.217
X-Spam-Level:
X-Spam-Status: No, score=-9.217 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HK_RANDOM_ENVFROM=0.001, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-2.316, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 0uIrWSBtDiVo for <kitten@ietfa.amsl.com>; Wed, 28 Sep 2016 09:50:17 -0700 (PDT)
Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5259212B270 for <kitten@ietf.org>; Wed, 28 Sep 2016 09:47:50 -0700 (PDT)
Received: from int-mx14.intmail.prod.int.phx2.redhat.com (int-mx14.intmail.prod.int.phx2.redhat.com [10.5.11.27]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id D7E233F1FA; Wed, 28 Sep 2016 16:41:17 +0000 (UTC)
Received: from dhcp137-207.rdu.redhat.com (dhcp137-207.rdu.redhat.com [10.13.137.207]) by int-mx14.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id u8SGfHwa016608 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 28 Sep 2016 12:41:17 -0400
Message-ID: <1475080876.9001.7.camel@redhat.com>
From: Nathaniel McCallum <npmccallum@redhat.com>
To: Benjamin Kaduk <kaduk@MIT.EDU>
Date: Wed, 28 Sep 2016 12:41:16 -0400
In-Reply-To: <alpine.GSO.1.10.1609251734290.5272@multics.mit.edu>
References: <alpine.GSO.1.10.1609251734290.5272@multics.mit.edu>
Content-Type: text/plain; charset="UTF-8"
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.68 on 10.5.11.27
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.30]); Wed, 28 Sep 2016 16:41:17 +0000 (UTC)
Archived-At: <https://mailarchive.ietf.org/arch/msg/kitten/y3EeE1Js3NdkPrTAWCWF7o5ad7s>
Cc: kitten@ietf.org
Subject: Re: [kitten] shepherd review of draft-ietf-kitten-krb-auth-indicator-02
X-BeenThere: kitten@ietf.org
X-Mailman-Version: 2.1.17
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: Wed, 28 Sep 2016 16:50:18 -0000

On Sun, 2016-09-25 at 19:20 -0400, Benjamin Kaduk wrote:
> I also suspect that the last paragraph of the security considerations
> should be rewritten in a normative fashion and moved to section 3, to
> make
> it clear what the presence of a given string in the authdata
> indicates.
> (Do we know of reasons why someone might use this AD element to
> indicate
> something other than a positive indication that the indicated
> requirements
> were met during the initial authentication?)

IMHO, I think this is not necessary. Section 3 already contains this
paragraph:

"Each UTF8String value is a short string that indicates that a
particular set of requirements was met during the initial
authentication."

This sentence is the normative definition of precisely what an
indicator is. The paragraph in the security considerations section is a
warning about what would happen if you tried to use indicators for
another purpose: ambiguity would arise. This is a security
consideration.

This warning is necessary precisely because the majority use of
indicators will be as site-defined strings.