Re: [kitten] meeting in Seoul?

Nathaniel McCallum <npmccallum@redhat.com> Thu, 25 August 2016 20:08 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 ACB2012D0AD for <kitten@ietfa.amsl.com>; Thu, 25 Aug 2016 13:08:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.469
X-Spam-Level:
X-Spam-Status: No, score=-6.469 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HK_RANDOM_ENVFROM=0.001, HK_RANDOM_FROM=1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.548, 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 AoUkSTj3tIt7 for <kitten@ietfa.amsl.com>; Thu, 25 Aug 2016 13:08:23 -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 465C712B040 for <kitten@ietf.org>; Thu, 25 Aug 2016 13:08:23 -0700 (PDT)
Received: from int-mx09.intmail.prod.int.phx2.redhat.com (int-mx09.intmail.prod.int.phx2.redhat.com [10.5.11.22]) (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 E06BA7F7A9; Thu, 25 Aug 2016 20:02:39 +0000 (UTC)
Received: from dhcp137-207.rdu.redhat.com (dhcp137-207.rdu.redhat.com [10.13.137.207]) by int-mx09.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id u7PK2c4C012806 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 25 Aug 2016 16:02:39 -0400
Message-ID: <1472155358.25965.9.camel@redhat.com>
From: Nathaniel McCallum <npmccallum@redhat.com>
To: Benjamin Kaduk <kaduk@MIT.EDU>, kitten@ietf.org
Date: Thu, 25 Aug 2016 16:02:38 -0400
In-Reply-To: <alpine.GSO.1.10.1608242050500.5272@multics.mit.edu>
References: <alpine.GSO.1.10.1608242050500.5272@multics.mit.edu>
Content-Type: text/plain; charset="UTF-8"
Mime-Version: 1.0
Content-Transfer-Encoding: 8bit
X-Scanned-By: MIMEDefang 2.68 on 10.5.11.22
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.28]); Thu, 25 Aug 2016 20:02:40 +0000 (UTC)
Archived-At: <https://mailarchive.ietf.org/arch/msg/kitten/c0j1CUPX79fmr_pc9WIH8d_2GNU>
Cc: Matt Rogers <mrogers@redhat.com>
Subject: Re: [kitten] meeting in Seoul?
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: Thu, 25 Aug 2016 20:08:24 -0000

On Wed, 2016-08-24 at 20:53 -0400, Benjamin Kaduk wrote:
> Hi all,
> 
> Session requests are now open for IETF 97 in Seoul (November 13-
> 18).  Does
> anyone have topic(s) they would like to cover there?  If there are no
> responses, I will assume that we will not meet and submit a session
> request to that effect.
> 
> Please send in any topics by September 7.

I would definitely like to discuss my three outstanding drafts:
  * Authentication Indicators
  * URI Discovery
  * SPAKE Preauth

This discussion doesn't have to be in Seoul, though I may be there for
other reasons.

In the case of Authentication Indicators, the authors feel this draft
is complete and is ready for WGLC.

Regarding the other two drafts, I am about to issue new revisions
(today or tomorrow). I would very much like them to be adopted by the
working group.

In the case of URI Discovery, we are close to merging a patch
supporting the feature.
    https://github.com/krb5/krb5/pull/481

In the case of SPAKE, we have a basic implementation working and plan
to expand it to support second features in the coming months.
    https://github.com/greghudson/krb5/tree/spake

We would very much like to move these drafts along as quickly as
possible.

Nathaniel