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

Jeffrey Hutzelman <jhutz@cmu.edu> Fri, 07 March 2014 00:01 UTC

Return-Path: <jhutz@cmu.edu>
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 A3FC21A017C for <kitten@ietfa.amsl.com>; Thu, 6 Mar 2014 16:01:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.447
X-Spam-Level:
X-Spam-Status: No, score=-2.447 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.547] 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 CZffST1eI4L7 for <kitten@ietfa.amsl.com>; Thu, 6 Mar 2014 16:01:29 -0800 (PST)
Received: from smtp01.srv.cs.cmu.edu (smtp01.srv.cs.cmu.edu [128.2.217.200]) by ietfa.amsl.com (Postfix) with ESMTP id 6BC561A0160 for <kitten@ietf.org>; Thu, 6 Mar 2014 16:01:28 -0800 (PST)
Received: from [128.2.193.239] (minbar.fac.cs.cmu.edu [128.2.193.239]) (authenticated bits=0) by smtp01.srv.cs.cmu.edu (8.13.6/8.13.6) with ESMTP id s2701MCn009056 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Thu, 6 Mar 2014 19:01:23 -0500 (EST)
Message-ID: <1394150482.4395.282.camel@minbar.fac.cs.cmu.edu>
From: Jeffrey Hutzelman <jhutz@cmu.edu>
To: kitten@ietf.org
Date: Thu, 06 Mar 2014 19:01:22 -0500
In-Reply-To: <alpine.GSO.1.10.1403061729070.1213@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> <alpine.GSO.1.10.1309041148130.16692@multics.mit.edu> <alpine.GSO.1.10.1403041135510.1213@multics.mit.edu> <tslzjl4ohbn.fsf@mit.edu> <1394031556.4290.53.camel@destiny.pc.cs.cmu.edu> <5317BD6E.6080309@oracle.com> <alpine.GSO.1.10.1403051916110.1213@multics.mit.edu> <tslpplzvdb0.fsf@mit.edu> <alpine.GSO.1.10.1403061729070.1213@multics.mit.edu>
Content-Type: text/plain; charset="UTF-8"
X-Mailer: Evolution 3.2.3-0ubuntu6
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0
X-Scanned-By: mimedefang-cmuscs on 128.2.217.200
Archived-At: http://mailarchive.ietf.org/arch/msg/kitten/VNXsRWSYYwHH_VSBW3CEgwt7B5k
Cc: jhutz@cmu.edu
Subject: Re: [kitten] Updating IANA krb5 GSSAPI token type registry
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: Fri, 07 Mar 2014 00:01:31 -0000

On Thu, 2014-03-06 at 17:51 -0500, Benjamin Kaduk wrote:

> Is there a magic phrase that invokes such an appeal?  (Or does it go 
> through IANA?)  I am unfamiliar with the process, and not necessarily 
> indicating intent to do so.

Sort of.  You have to do it intentionally, stating the reason for the
appeal and what remedy you want.  A chair or AD or really anyone
familiar with the process should be happy to help you, if you decide to
go that route.

Personally, I think there is usually little value in the appeal process
while you are having a discussion with the original decision-maker that
has not yet converged and does not yet appear not to do so.

-- Jeff