From owner-ietf-cat-wg@lists.Stanford.EDU Wed Sep 10 18:15:11 2003 Received: from lists.Stanford.EDU (lists.Stanford.EDU [171.64.14.236]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA20970 for ; Wed, 10 Sep 2003 18:15:10 -0400 (EDT) Received: (from root@localhost) by lists.Stanford.EDU (8.12.9/8.12.9) id h8AKXlWK018267 for ietf-cat-wg-out720680; Wed, 10 Sep 2003 13:33:47 -0700 (PDT) Received: from konishi-polis.mit.edu (KONISHI-POLIS.MIT.EDU [18.18.3.10]) by lists.Stanford.EDU (8.12.9/8.12.9) with ESMTP id h8AKXiUT018260 for ; Wed, 10 Sep 2003 13:33:44 -0700 (PDT) Received: by konishi-polis.mit.edu (Postfix, from userid 8042) id 7826D152029; Wed, 10 Sep 2003 16:33:43 -0400 (EDT) To: ietf-cat-wg@lists.Stanford.EDU Cc: nicolas.williams@sun.com Subject: [Nicolas Williams] Re: GSSAPI naming and domain-based names From: Sam Hartman Date: Wed, 10 Sep 2003 16:33:43 -0400 Message-ID: User-Agent: Gnus/5.1002 (Gnus v5.10.2) Emacs/21.2 (gnu/linux) MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="=-=-=" X-Perlmx-Spam: Gauge=, Probability=0%, Report="SPAM_PHRASE_08_13, USER_AGENT, USER_AGENT_GNUS_UA" Sender: owner-ietf-cat-wg@lists.Stanford.EDU Precedence: bulk --=-=-= Hi. Over in the SASL working group we have been discussing the problem of GSSAPI and naming for SASL mechanisms. The problem is that if you are using some protocol like LDAP that does SRV records, you need to make sure that you authenticate both the name the user typed in as well as the eventual hostname that you ended up using at the GSSAPI layer. Nico is going to work on a proposal that he will presumably submit as a proposed standard. At this time, this is not a work item of the SASL working group, although we expect to discuss the issues on our mailing lists. Interested CAT fanciers may want to follow that discussion. --=-=-= Content-Type: message/rfc822 Content-Disposition: inline Return-Path: Received: from solipsist-nation ([unix socket]) by solipsist-nation (Cyrus v2.1.5-Debian2.1.5-1) with LMTP; Wed, 10 Sep 2003 15:44:51 -0400 X-Sieve: CMU Sieve 2.2 Return-Path: Received: from fort-point-station.mit.edu (FORT-POINT-STATION.MIT.EDU [18.7.7.76]) by suchdamage.org (Postfix) with ESMTP id 2B7F413230 for ; Wed, 10 Sep 2003 15:44:51 -0400 (EDT) Received: from brmea-mail-3.sun.com (brmea-mail-3.Sun.COM [192.18.98.34]) by fort-point-station.mit.edu (8.12.4/8.9.2) with ESMTP id h8AJipvI011920 for ; Wed, 10 Sep 2003 15:44:51 -0400 (EDT) Received: from centralmail1brm.Central.Sun.COM ([129.147.62.1]) by brmea-mail-3.sun.com (8.12.9/8.12.9) with ESMTP id h8AJinHD000250; Wed, 10 Sep 2003 13:44:49 -0600 (MDT) Received: from binky.central.sun.com (binky.Central.Sun.COM [129.153.128.104]) by centralmail1brm.Central.Sun.COM (8.12.9+Sun/8.12.9/ENSMAIL,v2.2) with ESMTP id h8AJin6c012368; Wed, 10 Sep 2003 13:44:49 -0600 (MDT) Received: from binky.central.sun.com (localhost [127.0.0.1]) by binky.central.sun.com (8.12.5+Sun/8.12.3) with ESMTP id h8AJfAQx018641; Wed, 10 Sep 2003 12:41:10 -0700 (PDT) Received: (from nw141292@localhost) by binky.central.sun.com (8.12.5+Sun/8.12.3/Submit) id h8AJfAOe018640; Wed, 10 Sep 2003 12:41:10 -0700 (PDT) Date: Wed, 10 Sep 2003 12:41:10 -0700 From: Nicolas Williams To: Sam Hartman Cc: ietf-sasl@imc.org Subject: Re: GSSAPI naming and domain-based names Message-ID: <20030910194110.GT11118@binky.central.sun.com> References: <20030910190645.2D2D3152029@konishi-polis.mit.edu> In-Reply-To: <20030910190645.2D2D3152029@konishi-polis.mit.edu> User-Agent: Mutt/1.4i X-Spam-Status: No, hits=-4.4 required=5.0 tests=IN_REP_TO version=2.20 X-Spam-Level: MIME-Version: 1.0 I will write two drafts: one about GSS-API domain-based names and one about domain-based names for the Kerberos V GSS-API mechanism. Cheers, Nico On Wed, Sep 10, 2003 at 03:06:45PM -0400, Sam Hartman wrote: > So, several people spoke up in favor of looking at the GSSAPI name > issue and no one seemed to object to looking at the problem. > > would you be interested in writing up an individual draft that defines > the new GSSAPI name type for domain-based services? I haven't talked > to Kurt about whether he thinks this work is in scope, but even if it > is, we'll want to see an individual draft first and later make it a > working group document. > > If you do write up an individual draft, I'd request that you have the > draft announcement copied here and to ietf-cat-wg@lists.stanford.edu. --=-=-=-- -++**==--++**==--++**==--++**==--++**==--++**==--++**== This message was posted through the Stanford campus mailing list server. If you wish to unsubscribe from this mailing list, send the message body of "unsubscribe ietf-cat-wg" to majordomo@lists.stanford.edu