From kitten-bounces@lists.ietf.org Thu Jan 17 14:09:32 2008 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1JFa7F-0004W9-8p; Thu, 17 Jan 2008 14:09:29 -0500 Received: from kitten by megatron.ietf.org with local (Exim 4.43) id 1JFa7D-0004W4-L5 for kitten-confirm+ok@megatron.ietf.org; Thu, 17 Jan 2008 14:09:27 -0500 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1JFa7D-0004Vw-Ac for kitten@ietf.org; Thu, 17 Jan 2008 14:09:27 -0500 Received: from carter-zimmerman.suchdamage.org ([69.25.196.178]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1JFa7C-0001dL-OJ for kitten@ietf.org; Thu, 17 Jan 2008 14:09:27 -0500 Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id 233F64819; Thu, 17 Jan 2008 14:09:24 -0500 (EST) From: Sam Hartman To: kitten@ietf.org Date: Thu, 17 Jan 2008 14:09:24 -0500 Message-ID: User-Agent: Gnus/5.110006 (No Gnus v0.6) Emacs/21.4 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Spam-Score: 0.0 (/) X-Scan-Signature: 93238566e09e6e262849b4f805833007 Cc: Subject: Concerns about domain based names drafts X-BeenThere: kitten@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Common Authentication Technologies - Next Generation List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: kitten-bounces@lists.ietf.org Folks, trying to resolve the domain based name drafts. In the base spec, the IANA considerations does not describe which registry IANA should make an OID assignment in. Also, the text sounds like you are recommending a value for the ASN.1 OID string. However your recommended value includes underscores; I didn't think that was permitted. I think you want to separate the OID assignment from the recommended constant name (and value) for C bindings. Section 5 seems to normatively introduce gss_import_name_utf8. The specification of that function is not sufficient for implementation. In addition, I didn't think we planned to introduce import_name_utf8 or display_name_utf8 in this spec. I thought we intended to have an informational note explaining how those functions will deal with the domain based names. The behavior for ACE encodings ing existings functions does need to be normative. The kerberos draft still uses .tld examples rather than .example examples. _______________________________________________ Kitten mailing list Kitten@lists.ietf.org https://www1.ietf.org/mailman/listinfo/kitten From kitten-bounces@lists.ietf.org Thu Jan 17 14:11:33 2008 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1JFa9E-00009H-Ri; Thu, 17 Jan 2008 14:11:32 -0500 Received: from kitten by megatron.ietf.org with local (Exim 4.43) id 1JFa9C-00009B-W3 for kitten-confirm+ok@megatron.ietf.org; Thu, 17 Jan 2008 14:11:30 -0500 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1JFa9C-000093-Lo for kitten@ietf.org; Thu, 17 Jan 2008 14:11:30 -0500 Received: from carter-zimmerman.suchdamage.org ([69.25.196.178]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1JFa9C-0001fe-9d for kitten@ietf.org; Thu, 17 Jan 2008 14:11:30 -0500 Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id ADF344819; Thu, 17 Jan 2008 14:11:27 -0500 (EST) From: Sam Hartman To: kitten@ietf.org References: Date: Thu, 17 Jan 2008 14:11:27 -0500 In-Reply-To: (Sam Hartman's message of "Thu, 17 Jan 2008 14:09:24 -0500") Message-ID: User-Agent: Gnus/5.110006 (No Gnus v0.6) Emacs/21.4 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Spam-Score: 0.0 (/) X-Scan-Signature: 0f1ff0b0158b41ac6b9548d0972cdd31 Cc: Subject: Re: Concerns about domain based names drafts X-BeenThere: kitten@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Common Authentication Technologies - Next Generation List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: kitten-bounces@lists.ietf.org Another important issue: The ABNF is hugely garbled in the draft. _______________________________________________ Kitten mailing list Kitten@lists.ietf.org https://www1.ietf.org/mailman/listinfo/kitten From kitten-bounces@lists.ietf.org Fri Jan 18 05:06:54 2008 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1JFo7c-0000fX-3M; Fri, 18 Jan 2008 05:06:48 -0500 Received: from kitten by megatron.ietf.org with local (Exim 4.43) id 1JFo7b-0000c7-2H for kitten-confirm+ok@megatron.ietf.org; Fri, 18 Jan 2008 05:06:47 -0500 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1JFo7a-0000bz-9S for kitten@ietf.org; Fri, 18 Jan 2008 05:06:46 -0500 Received: from rufus.isode.com ([62.3.217.251]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1JFo7Z-0006fb-Vq for kitten@ietf.org; Fri, 18 Jan 2008 05:06:46 -0500 Received: from [172.16.1.99] (shiny.isode.com [62.3.217.250]) by rufus.isode.com (submission channel) via TCP with ESMTPA id ; Fri, 18 Jan 2008 10:06:44 +0000 Message-ID: <47907A33.3060507@isode.com> Date: Fri, 18 Jan 2008 10:06:43 +0000 From: Alexey Melnikov User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915 X-Accept-Language: en-us, en To: Sam Hartman References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: 08e48e05374109708c00c6208b534009 Cc: kitten@ietf.org Subject: Re: Concerns about domain based names drafts X-BeenThere: kitten@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Common Authentication Technologies - Next Generation List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: kitten-bounces@lists.ietf.org Sam Hartman wrote: >Another important issue: >The ABNF is hugely garbled in the draft. > > Yes, my mistake. I forgot to insert "=" :-). _______________________________________________ Kitten mailing list Kitten@lists.ietf.org https://www1.ietf.org/mailman/listinfo/kitten From kitten-bounces@lists.ietf.org Fri Jan 18 15:39:29 2008 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1JFxzs-0007aC-LZ; Fri, 18 Jan 2008 15:39:28 -0500 Received: from kitten by megatron.ietf.org with local (Exim 4.43) id 1JFxzr-0007a7-P8 for kitten-confirm+ok@megatron.ietf.org; Fri, 18 Jan 2008 15:39:27 -0500 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1JFxzr-0007Zx-EF for kitten@ietf.org; Fri, 18 Jan 2008 15:39:27 -0500 Received: from rufus.isode.com ([62.3.217.251]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1JFxzq-0003ql-Tl for kitten@ietf.org; Fri, 18 Jan 2008 15:39:27 -0500 Received: from [172.16.1.99] (shiny.isode.com [62.3.217.250]) by rufus.isode.com (submission channel) via TCP with ESMTPA id ; Fri, 18 Jan 2008 20:39:25 +0000 Message-ID: <47910E5D.7040206@isode.com> Date: Fri, 18 Jan 2008 20:38:53 +0000 From: Alexey Melnikov User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915 X-Accept-Language: en-us, en To: Sam Hartman References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b Cc: kitten@ietf.org Subject: Re: Concerns about domain based names drafts X-BeenThere: kitten@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Common Authentication Technologies - Next Generation List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: kitten-bounces@lists.ietf.org Hi Sam, Sam Hartman wrote: >Folks, trying to resolve the domain based name drafts. > >In the base spec, the IANA considerations does not describe which registry IANA should make an OID assignment in. > > I need help on locating the corresponding registry. >Also, the text sounds like you are recommending a value for the ASN.1 >OID string. >However your recommended value includes underscores; I didn't think that was permitted. > > There seem to be some mistake here. The parent OID had no underscores anywhere. >I think you want to separate the OID assignment from the recommended constant name (and value) for C bindings. > > Right. >Section 5 seems to normatively introduce gss_import_name_utf8. The >specification of that function is not sufficient for implementation. >In addition, I didn't think we planned to introduce import_name_utf8 >or display_name_utf8 in this spec. I thought we intended to have an >informational note explaining how those functions will deal with the >domain based names. >The behavior for ACE encodings ing existings functions does need to be normative. > > Nico should comment on this. >The kerberos draft still uses .tld examples rather than .example >examples. > > _______________________________________________ Kitten mailing list Kitten@lists.ietf.org https://www1.ietf.org/mailman/listinfo/kitten From kitten-bounces@lists.ietf.org Mon Jan 21 23:12:19 2008 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1JHAUi-00041m-5O; Mon, 21 Jan 2008 23:12:16 -0500 Received: from kitten by megatron.ietf.org with local (Exim 4.43) id 1JHAUg-00041C-VU for kitten-confirm+ok@megatron.ietf.org; Mon, 21 Jan 2008 23:12:14 -0500 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1JHAUg-000414-Ha for kitten@ietf.org; Mon, 21 Jan 2008 23:12:14 -0500 Received: from brmea-mail-4.sun.com ([192.18.98.36]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1JHAUg-0004Jm-3m for kitten@ietf.org; Mon, 21 Jan 2008 23:12:14 -0500 Received: from dm-central-01.central.sun.com ([129.147.62.4]) by brmea-mail-4.sun.com (8.13.6+Sun/8.12.9) with ESMTP id m0M4CDj5007686 for ; Tue, 22 Jan 2008 04:12:13 GMT Received: from binky.Central.Sun.COM (binky.Central.Sun.COM [129.153.128.104]) by dm-central-01.central.sun.com (8.13.8+Sun/8.13.8/ENSMAIL, v2.2) with ESMTP id m0M4CD8M046034 for ; Mon, 21 Jan 2008 21:12:13 -0700 (MST) Received: from binky.Central.Sun.COM (localhost [127.0.0.1]) by binky.Central.Sun.COM (8.14.1+Sun/8.14.1) with ESMTP id m0M4CDWM009565; Mon, 21 Jan 2008 22:12:13 -0600 (CST) Received: (from nw141292@localhost) by binky.Central.Sun.COM (8.14.1+Sun/8.14.1/Submit) id m0M4CDcg009564; Mon, 21 Jan 2008 22:12:13 -0600 (CST) X-Authentication-Warning: binky.Central.Sun.COM: nw141292 set sender to Nicolas.Williams@sun.com using -f Date: Mon, 21 Jan 2008 22:12:13 -0600 From: Nicolas Williams To: Sam Hartman Message-ID: <20080122041212.GA6591@Sun.COM> Mail-Followup-To: Sam Hartman , kitten@ietf.org References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.7i X-Spam-Score: -1.0 (-) X-Scan-Signature: 7aafa0432175920a4b3e118e16c5cb64 Cc: kitten@ietf.org Subject: Re: Concerns about domain based names drafts X-BeenThere: kitten@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Common Authentication Technologies - Next Generation List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: kitten-bounces@lists.ietf.org On Thu, Jan 17, 2008 at 02:09:24PM -0500, Sam Hartman wrote: > In the base spec, the IANA considerations does not describe which > registry IANA should make an OID assignment in. OK, this is not a problem. > Also, the text sounds like you are recommending a value for the ASN.1 > OID string. Yes. IANA gets a pass at the document before it makes it onto the RFC-Editor queue, so this did not trouble me. > However your recommended value includes underscores; I didn't think > that was permitted. -05 says: IANA is requested to assign a new OID for the new GSS-API name type defined in this document. This OID should have the following prefix: {iso(1) org(3) dod(6) internet(1) security(5) nametypes(6) gss- domain-based(5)} No underscores there... :) > I think you want to separate the OID assignment from the recommended > constant name (and value) for C bindings. The constant name is not being registered (there being no registry for the name). Hmmm... Is there even a registry for {iso(1) org(3) dod(6) internet(1) security(5) nametypes(6)}? I don't see one. > Section 5 seems to normatively introduce gss_import_name_utf8. The > specification of that function is not sufficient for implementation. I what way is it not sufficient? > In addition, I didn't think we planned to introduce import_name_utf8 > or display_name_utf8 in this spec. I thought we intended to have an > informational note explaining how those functions will deal with the > domain based names. I don't see why we cannot introduce these here. These functions are pretty much the result of the discussions at Chicago and on the list. > The behavior for ACE encodings ing existings functions does need to be > normative. It isn't? > The kerberos draft still uses .tld examples rather than .example > examples. Oops, I can fix that. _______________________________________________ Kitten mailing list Kitten@lists.ietf.org https://www1.ietf.org/mailman/listinfo/kitten From kitten-bounces@lists.ietf.org Tue Jan 22 08:17:56 2008 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1JHJ0l-0002Hs-NS; Tue, 22 Jan 2008 08:17:55 -0500 Received: from kitten by megatron.ietf.org with local (Exim 4.43) id 1JHJ0k-0002Hh-HM for kitten-confirm+ok@megatron.ietf.org; Tue, 22 Jan 2008 08:17:54 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1JHJ0k-0002HY-32 for kitten@ietf.org; Tue, 22 Jan 2008 08:17:54 -0500 Received: from carter-zimmerman.suchdamage.org ([69.25.196.178]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1JHJ0j-0000QF-SS for kitten@ietf.org; Tue, 22 Jan 2008 08:17:54 -0500 Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id 3CC0AC400B; Tue, 22 Jan 2008 08:17:49 -0500 (EST) From: Sam Hartman To: kitten@ietf.org References: <20080122041212.GA6591@Sun.COM> Date: Tue, 22 Jan 2008 08:17:49 -0500 In-Reply-To: <20080122041212.GA6591@Sun.COM> (Nicolas Williams's message of "Mon, 21 Jan 2008 22:12:13 -0600") Message-ID: User-Agent: Gnus/5.110006 (No Gnus v0.6) Emacs/21.4 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Spam-Score: 0.0 (/) X-Scan-Signature: 8ac499381112328dd60aea5b1ff596ea Cc: Subject: Re: Concerns about domain based names drafts X-BeenThere: kitten@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Common Authentication Technologies - Next Generation List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: kitten-bounces@lists.ietf.org >>>>> "Nicolas" == Nicolas Williams writes: Nicolas> Oops, I can fix that. _______________________________________________ Kitten mailing list Kitten@lists.ietf.org https://www1.ietf.org/mailman/listinfo/kitten From kitten-bounces@lists.ietf.org Tue Jan 22 11:12:41 2008 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1JHLjl-0000G0-Pe; Tue, 22 Jan 2008 11:12:33 -0500 Received: from kitten by megatron.ietf.org with local (Exim 4.43) id 1JHLjj-0000FB-KM for kitten-confirm+ok@megatron.ietf.org; Tue, 22 Jan 2008 11:12:31 -0500 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1JHLjj-0000Ew-7W for kitten@ietf.org; Tue, 22 Jan 2008 11:12:31 -0500 Received: from sca-ea-mail-2.sun.com ([192.18.43.25]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1JHLji-0000rL-MX for kitten@ietf.org; Tue, 22 Jan 2008 11:12:31 -0500 Received: from dm-central-01.central.sun.com ([129.147.62.4]) by sca-ea-mail-2.sun.com (8.13.7+Sun/8.12.9) with ESMTP id m0MGCHWj003353 for ; Tue, 22 Jan 2008 16:12:27 GMT Received: from binky.Central.Sun.COM (binky.Central.Sun.COM [129.153.128.104]) by dm-central-01.central.sun.com (8.13.8+Sun/8.13.8/ENSMAIL, v2.2) with ESMTP id m0MGCHqf047693 for ; Tue, 22 Jan 2008 09:12:17 -0700 (MST) Received: from binky.Central.Sun.COM (localhost [127.0.0.1]) by binky.Central.Sun.COM (8.14.1+Sun/8.14.1) with ESMTP id m0MGCH24009780; Tue, 22 Jan 2008 10:12:17 -0600 (CST) Received: (from nw141292@localhost) by binky.Central.Sun.COM (8.14.1+Sun/8.14.1/Submit) id m0MGCHq2009779; Tue, 22 Jan 2008 10:12:17 -0600 (CST) X-Authentication-Warning: binky.Central.Sun.COM: nw141292 set sender to Nicolas.Williams@sun.com using -f Date: Tue, 22 Jan 2008 10:12:17 -0600 From: Nicolas Williams To: Sam Hartman Message-ID: <20080122161216.GF6591@Sun.COM> Mail-Followup-To: Sam Hartman , kitten@ietf.org References: <20080122041212.GA6591@Sun.COM> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.7i X-Spam-Score: 0.0 (/) X-Scan-Signature: 6d62ab47271805379d7172ee693a45db Cc: kitten@ietf.org Subject: Re: Concerns about domain based names drafts X-BeenThere: kitten@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Common Authentication Technologies - Next Generation List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: kitten-bounces@lists.ietf.org On Tue, Jan 22, 2008 at 08:17:49AM -0500, Sam Hartman wrote: > Nicolas> Oops, I can fix that. Did you mean to say something other than quoting me? :) Or is this a hint that I should just submit a new I-D? _______________________________________________ Kitten mailing list Kitten@lists.ietf.org https://www1.ietf.org/mailman/listinfo/kitten From kitten-bounces@lists.ietf.org Tue Jan 22 17:27:47 2008 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1JHRas-00063Q-7j; Tue, 22 Jan 2008 17:27:46 -0500 Received: from kitten by megatron.ietf.org with local (Exim 4.43) id 1JHRar-00063L-Ax for kitten-confirm+ok@megatron.ietf.org; Tue, 22 Jan 2008 17:27:45 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1JHRar-00063C-0X for kitten@ietf.org; Tue, 22 Jan 2008 17:27:45 -0500 Received: from carter-zimmerman.suchdamage.org ([69.25.196.178]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1JHRaq-00022e-IE for kitten@ietf.org; Tue, 22 Jan 2008 17:27:44 -0500 Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id BB86DC400B; Tue, 22 Jan 2008 17:27:43 -0500 (EST) From: Sam Hartman To: kitten@ietf.org References: <20080122041212.GA6591@Sun.COM> <20080122161216.GF6591@Sun.COM> Date: Tue, 22 Jan 2008 17:27:43 -0500 In-Reply-To: <20080122161216.GF6591@Sun.COM> (Nicolas Williams's message of "Tue, 22 Jan 2008 10:12:17 -0600") Message-ID: User-Agent: Gnus/5.110006 (No Gnus v0.6) Emacs/21.4 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Spam-Score: 0.0 (/) X-Scan-Signature: a7d6aff76b15f3f56fcb94490e1052e4 Cc: Subject: Re: Concerns about domain based names drafts X-BeenThere: kitten@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Common Authentication Technologies - Next Generation List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: kitten-bounces@lists.ietf.org >> I think you want to separate the OID assignment from the >> recommended constant name (and value) for C bindings. Nicolas> The constant name is not being registered (there being no Nicolas> registry for the name). Hmmm... Is there even a Nicolas> registry for {iso(1) org(3) dod(6) internet(1) Nicolas> security(5) nametypes(6)}? I don't see one. I think you do want to say what constant people should use; I don't think you can register it since there is no registry. >> Section 5 seems to normatively introduce gss_import_name_utf8. >> The specification of that function is not sufficient for >> implementation. Nicolas> I what way is it not sufficient? Doesn't define inputs, outputs, statuses, semantics. Yes, a lot of this text will be copied from the existing spec. However if you are going to define new functions you need to actually specify all the things that 2743 does for the functions. >> In addition, I didn't think we planned to introduce >> import_name_utf8 or display_name_utf8 in this spec. I thought >> we intended to have an informational note explaining how those >> functions will deal with the domain based names. Nicolas> I don't see why we cannot introduce these here. These Nicolas> functions are pretty much the result of the discussions Nicolas> at Chicago and on the list. They are not within the scope of the draft. >> The behavior for ACE encodings ing existings functions does >> need to be normative. Nicolas> It isn't? No, I was making it clear that this should not change. _______________________________________________ Kitten mailing list Kitten@lists.ietf.org https://www1.ietf.org/mailman/listinfo/kitten From kitten-bounces@lists.ietf.org Tue Jan 22 17:56:27 2008 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1JHS2c-0006xb-2p; Tue, 22 Jan 2008 17:56:26 -0500 Received: from kitten by megatron.ietf.org with local (Exim 4.43) id 1JHS2a-0006xV-Lu for kitten-confirm+ok@megatron.ietf.org; Tue, 22 Jan 2008 17:56:24 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1JHS2Z-0006xM-Uv for kitten@ietf.org; Tue, 22 Jan 2008 17:56:23 -0500 Received: from brmea-mail-2.sun.com ([192.18.98.43]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1JHS2Z-0002l2-HK for kitten@ietf.org; Tue, 22 Jan 2008 17:56:23 -0500 Received: from dm-central-02.central.sun.com ([129.147.62.5]) by brmea-mail-2.sun.com (8.13.6+Sun/8.12.9) with ESMTP id m0MMuNIx011067 for ; Tue, 22 Jan 2008 22:56:23 GMT Received: from binky.Central.Sun.COM (binky.Central.Sun.COM [129.153.128.104]) by dm-central-02.central.sun.com (8.13.8+Sun/8.13.8/ENSMAIL, v2.2) with ESMTP id m0MMuMPm043680 for ; Tue, 22 Jan 2008 15:56:22 -0700 (MST) Received: from binky.Central.Sun.COM (localhost [127.0.0.1]) by binky.Central.Sun.COM (8.14.1+Sun/8.14.1) with ESMTP id m0MMuMjY010124; Tue, 22 Jan 2008 16:56:22 -0600 (CST) Received: (from nw141292@localhost) by binky.Central.Sun.COM (8.14.1+Sun/8.14.1/Submit) id m0MMuM3a010123; Tue, 22 Jan 2008 16:56:22 -0600 (CST) X-Authentication-Warning: binky.Central.Sun.COM: nw141292 set sender to Nicolas.Williams@sun.com using -f Date: Tue, 22 Jan 2008 16:56:22 -0600 From: Nicolas Williams To: Sam Hartman Message-ID: <20080122225622.GS6591@Sun.COM> Mail-Followup-To: Sam Hartman , kitten@ietf.org References: <20080122041212.GA6591@Sun.COM> <20080122161216.GF6591@Sun.COM> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.7i X-Spam-Score: -1.0 (-) X-Scan-Signature: c1c65599517f9ac32519d043c37c5336 Cc: kitten@ietf.org Subject: Re: Concerns about domain based names drafts X-BeenThere: kitten@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Common Authentication Technologies - Next Generation List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: kitten-bounces@lists.ietf.org On Tue, Jan 22, 2008 at 05:27:43PM -0500, Sam Hartman wrote: > I think you do want to say what constant people should use; I don't > think you can register it since there is no registry. Either way, there's no registry even for that OID arc. > >> Section 5 seems to normatively introduce gss_import_name_utf8. > >> The specification of that function is not sufficient for > >> implementation. > > Nicolas> I what way is it not sufficient? > > Doesn't define inputs, outputs, statuses, semantics. Yes, a lot of > this text will be copied from the existing spec. However if you are > going to define new functions you need to actually specify all the > things that 2743 does for the functions. I disagree. The text reads: Support for non-ASCII internationalized domain names SHOULD be provided through a new function, GSS_Import_name_utf8(), that operates exactly like GSS_Import_name(), except that it MUST accept internationalized domain names both, as UTF-8 strings and as ACE- encoded strings via its input_name_string argument. GSS_Import_name_utf8() is defined in terms of GSS_Import_name(). I think that should be sufficient. Perhaps the text should be a bit clearer ("operates exactly like" might not imply "has the same input and output parameters" to some readers), but otherwise I think that cutting and pasting text from RFC2743 and RFC2744 would do a disservice to readers. > >> In addition, I didn't think we planned to introduce > >> import_name_utf8 or display_name_utf8 in this spec. I thought > >> we intended to have an informational note explaining how those > >> functions will deal with the domain based names. > > Nicolas> I don't see why we cannot introduce these here. These > Nicolas> functions are pretty much the result of the discussions > Nicolas> at Chicago and on the list. > > They are not within the scope of the draft. Please elaborate; why not? Nico -- _______________________________________________ Kitten mailing list Kitten@lists.ietf.org https://www1.ietf.org/mailman/listinfo/kitten From kitten-bounces@lists.ietf.org Fri Jan 25 00:10:38 2008 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1JIGpo-0004iI-Mg; Fri, 25 Jan 2008 00:10:36 -0500 Received: from kitten by megatron.ietf.org with local (Exim 4.43) id 1JIGpl-0004cq-5c for kitten-confirm+ok@megatron.ietf.org; Fri, 25 Jan 2008 00:10:33 -0500 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1JIGpk-0004cW-LR for kitten@lists.ietf.org; Fri, 25 Jan 2008 00:10:32 -0500 Received: from ns3.neustar.com ([156.154.24.138]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1JIGpk-0000Rj-8L for kitten@lists.ietf.org; Fri, 25 Jan 2008 00:10:32 -0500 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns3.neustar.com (Postfix) with ESMTP id CC543175CF; Fri, 25 Jan 2008 05:10:01 +0000 (GMT) Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1JIGpF-0006DR-Bd; Fri, 25 Jan 2008 00:10:01 -0500 Content-Type: Multipart/Mixed; Boundary="NextPart" Mime-Version: 1.0 To: i-d-announce@ietf.org From: Internet-Drafts@ietf.org Message-Id: Date: Fri, 25 Jan 2008 00:10:01 -0500 X-Spam-Score: 0.0 (/) X-Scan-Signature: 386e0819b1192672467565a524848168 Cc: kitten@lists.ietf.org Subject: I-D Action:draft-ietf-kitten-gssapi-domain-based-names-06.txt X-BeenThere: kitten@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Common Authentication Technologies - Next Generation List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: kitten-bounces@lists.ietf.org --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Kitten (GSS-API Next Generation) Working Group of the IETF. Title : GSS-API Internationalization and Domain-Based Service Names and Name Type Author(s) : N. Williams, A. Melnikov Filename : draft-ietf-kitten-gssapi-domain-based-names-06.txt Pages : 13 Date : 2008-01-25 This document describes domainname-based service principal names and the corresponding name type for the Generic Security Service Application Programming Interface (GSS-API). Internationalization of the GSS-API is also covered. Domain-based service names are similar to host-based service names, but using a domain name (not necessarily an Internet domain name) in addition to a hostname. The primary purpose of domain-based names is to provide a measure of protection to applications that utilize insecure service discovery protocols. This is achieved by providing a way to name clustered services after the "domain" which they service, thereby allowing their clients to authorize the service's servers based on authentication of their service names. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-kitten-gssapi-domain-based-names-06.txt To remove yourself from the I-D Announcement list, send a message to i-d-announce-request@ietf.org with the word unsubscribe in the body of the message. You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce to change your subscription settings. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-kitten-gssapi-domain-based-names-06.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-kitten-gssapi-domain-based-names-06.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2008-01-25000945.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-kitten-gssapi-domain-based-names-06.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-kitten-gssapi-domain-based-names-06.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2008-01-25000945.I-D\@ietf.org> --OtherAccess-- --NextPart Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Kitten mailing list Kitten@lists.ietf.org https://www1.ietf.org/mailman/listinfo/kitten --NextPart-- From kitten-bounces@lists.ietf.org Fri Jan 25 00:10:38 2008 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1JIGpo-0004h3-Eb; Fri, 25 Jan 2008 00:10:36 -0500 Received: from kitten by megatron.ietf.org with local (Exim 4.43) id 1JIGpk-0004cX-Me for kitten-confirm+ok@megatron.ietf.org; Fri, 25 Jan 2008 00:10:32 -0500 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1JIGpk-0004cO-4M for kitten@lists.ietf.org; Fri, 25 Jan 2008 00:10:32 -0500 Received: from ns4.neustar.com ([156.154.24.139]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1JIGpj-0000Rd-OQ for kitten@lists.ietf.org; Fri, 25 Jan 2008 00:10:32 -0500 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns4.neustar.com (Postfix) with ESMTP id 88F442AC5E; Fri, 25 Jan 2008 05:10:01 +0000 (GMT) Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1JIGpF-0006DM-AF; Fri, 25 Jan 2008 00:10:01 -0500 Content-Type: Multipart/Mixed; Boundary="NextPart" Mime-Version: 1.0 To: i-d-announce@ietf.org From: Internet-Drafts@ietf.org Message-Id: Date: Fri, 25 Jan 2008 00:10:01 -0500 X-Spam-Score: 0.0 (/) X-Scan-Signature: d185fa790257f526fedfd5d01ed9c976 Cc: kitten@lists.ietf.org Subject: I-D Action:draft-ietf-kitten-krb5-gssapi-domain-based-names-05.txt X-BeenThere: kitten@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Common Authentication Technologies - Next Generation List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: kitten-bounces@lists.ietf.org --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Kitten (GSS-API Next Generation) Working Group of the IETF. Title : GSS-API Domain-Based Service Names Mapping for the Kerberos V GSS Mechanism Author(s) : N. Williams Filename : draft-ietf-kitten-krb5-gssapi-domain-based-names-05.txt Pages : 6 Date : 2008-01-25 This document describes the mapping of GSS-API domainname-based service principal names onto Kerberos V principal names. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-kitten-krb5-gssapi-domain-based-names-05.txt To remove yourself from the I-D Announcement list, send a message to i-d-announce-request@ietf.org with the word unsubscribe in the body of the message. You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce to change your subscription settings. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-kitten-krb5-gssapi-domain-based-names-05.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-kitten-krb5-gssapi-domain-based-names-05.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2008-01-25000931.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-kitten-krb5-gssapi-domain-based-names-05.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-kitten-krb5-gssapi-domain-based-names-05.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2008-01-25000931.I-D\@ietf.org> --OtherAccess-- --NextPart Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Kitten mailing list Kitten@lists.ietf.org https://www1.ietf.org/mailman/listinfo/kitten --NextPart-- From kitten-bounces@lists.ietf.org Fri Jan 25 00:13:39 2008 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1JIGsk-00072B-Jw; Fri, 25 Jan 2008 00:13:38 -0500 Received: from kitten by megatron.ietf.org with local (Exim 4.43) id 1JIGsj-000710-Nn for kitten-confirm+ok@megatron.ietf.org; Fri, 25 Jan 2008 00:13:37 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1JIGsj-00070s-Db for kitten@ietf.org; Fri, 25 Jan 2008 00:13:37 -0500 Received: from brmea-mail-3.sun.com ([192.18.98.34]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1JIGsj-0003sd-1H for kitten@ietf.org; Fri, 25 Jan 2008 00:13:37 -0500 Received: from dm-central-02.central.sun.com ([129.147.62.5]) by brmea-mail-3.sun.com (8.13.6+Sun/8.12.9) with ESMTP id m0P5DaBf019484 for ; Fri, 25 Jan 2008 05:13:36 GMT Received: from binky.Central.Sun.COM (binky.Central.Sun.COM [129.153.128.104]) by dm-central-02.central.sun.com (8.13.8+Sun/8.13.8/ENSMAIL, v2.2) with ESMTP id m0P5DaAl007191 for ; Thu, 24 Jan 2008 22:13:36 -0700 (MST) Received: from binky.Central.Sun.COM (localhost [127.0.0.1]) by binky.Central.Sun.COM (8.14.1+Sun/8.14.1) with ESMTP id m0P5DaMh012587; Thu, 24 Jan 2008 23:13:36 -0600 (CST) Received: (from nw141292@localhost) by binky.Central.Sun.COM (8.14.1+Sun/8.14.1/Submit) id m0P5DWlu012586; Thu, 24 Jan 2008 23:13:32 -0600 (CST) X-Authentication-Warning: binky.Central.Sun.COM: nw141292 set sender to Nicolas.Williams@sun.com using -f Date: Thu, 24 Jan 2008 23:13:32 -0600 From: Nicolas Williams To: Sam Hartman Message-ID: <20080125051331.GF12183@Sun.COM> Mail-Followup-To: Sam Hartman , kitten@ietf.org References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.7i X-Spam-Score: -1.0 (-) X-Scan-Signature: 8b431ad66d60be2d47c7bfeb879db82c Cc: kitten@ietf.org Subject: Re: Concerns about domain based names drafts X-BeenThere: kitten@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Common Authentication Technologies - Next Generation List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: kitten-bounces@lists.ietf.org On Thu, Jan 17, 2008 at 02:09:24PM -0500, Sam Hartman wrote: > Folks, trying to resolve the domain based name drafts. > > In the base spec, the IANA considerations does not describe which > registry IANA should make an OID assignment in. I've fixed this. There is no such registry, therefore there are no IANA considerations. However, the manner in which the OID was obtained is now described. > Also, the text sounds like you are recommending a value for the ASN.1 > OID string. Now we just out and out allocate it. > However your recommended value includes underscores; I didn't think > that was permitted. There were no underscores in the OID in the I-D. > I think you want to separate the OID assignment from the recommended > constant name (and value) for C bindings. This is now irrelevant :) > Section 5 seems to normatively introduce gss_import_name_utf8. The > specification of that function is not sufficient for implementation. > In addition, I didn't think we planned to introduce import_name_utf8 > or display_name_utf8 in this spec. I thought we intended to have an > informational note explaining how those functions will deal with the > domain based names. > The behavior for ACE encodings ing existings functions does need to be > normative. I believe the *_utf8() functions belong in this document. I see no reason to publish a separate RFC just describing those two functions. I've seen no objections from the WG, but if desired we can call for consensus. I've updated the description, however, to be more exact. The *_utf8() functions are recommended, while the ACE behaviour of the regular functions is required. > The kerberos draft still uses .tld examples rather than .example > examples. Fixed. New I-Ds have been submitted. Nico -- _______________________________________________ Kitten mailing list Kitten@lists.ietf.org https://www1.ietf.org/mailman/listinfo/kitten From kitten-bounces@lists.ietf.org Fri Jan 25 05:29:08 2008 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1JILo3-0004uV-6C; Fri, 25 Jan 2008 05:29:07 -0500 Received: from kitten by megatron.ietf.org with local (Exim 4.43) id 1JILo1-0004uN-7r for kitten-confirm+ok@megatron.ietf.org; Fri, 25 Jan 2008 05:29:05 -0500 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1JILnt-0004gG-W3 for kitten@ietf.org; Fri, 25 Jan 2008 05:28:58 -0500 Received: from rufus.isode.com ([62.3.217.251]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1JILnt-00018S-Es for kitten@ietf.org; Fri, 25 Jan 2008 05:28:57 -0500 Received: from [172.16.1.99] (shiny.isode.com [62.3.217.250]) by rufus.isode.com (submission channel) via TCP with ESMTPA id ; Fri, 25 Jan 2008 10:28:55 +0000 Message-ID: <4799B9E6.60309@isode.com> Date: Fri, 25 Jan 2008 10:28:54 +0000 From: Alexey Melnikov User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915 X-Accept-Language: en-us, en To: Nicolas Williams References: <20080125051331.GF12183@Sun.COM> In-Reply-To: <20080125051331.GF12183@Sun.COM> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32 Cc: kitten@ietf.org, Sam Hartman Subject: Re: Concerns about domain based names drafts X-BeenThere: kitten@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Common Authentication Technologies - Next Generation List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: kitten-bounces@lists.ietf.org Nicolas Williams wrote: >>Section 5 seems to normatively introduce gss_import_name_utf8. The >>specification of that function is not sufficient for implementation. >>In addition, I didn't think we planned to introduce import_name_utf8 >>or display_name_utf8 in this spec. I thought we intended to have an >>informational note explaining how those functions will deal with the >>domain based names. >>The behavior for ACE encodings ing existings functions does need to be >>normative. >> >> >I believe the *_utf8() functions belong in this document. I see no >reason to publish a separate RFC just describing those two functions. >I've seen no objections from the WG, but if desired we can call for >consensus. I've updated the description, however, to be more exact. > > Speaking as an individual: no objections from me. >The *_utf8() functions are recommended, while the ACE behaviour of the >regular functions is required. > > _______________________________________________ Kitten mailing list Kitten@lists.ietf.org https://www1.ietf.org/mailman/listinfo/kitten From kitten-bounces@lists.ietf.org Mon Jan 28 15:42:53 2008 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1JJaod-0000J6-1A; Mon, 28 Jan 2008 15:42:51 -0500 Received: from kitten by megatron.ietf.org with local (Exim 4.43) id 1JJaoa-0000Ev-Ey for kitten-confirm+ok@megatron.ietf.org; Mon, 28 Jan 2008 15:42:48 -0500 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1JJaoZ-0000CS-VN for kitten@ietf.org; Mon, 28 Jan 2008 15:42:48 -0500 Received: from brmea-mail-3.sun.com ([192.18.98.34]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1JJaoY-0001I2-Sv for kitten@ietf.org; Mon, 28 Jan 2008 15:42:47 -0500 Received: from dm-central-02.central.sun.com ([129.147.62.5]) by brmea-mail-3.sun.com (8.13.6+Sun/8.12.9) with ESMTP id m0SKgkAb027401 for ; Mon, 28 Jan 2008 20:42:46 GMT Received: from binky.Central.Sun.COM (binky.Central.Sun.COM [129.153.128.104]) by dm-central-02.central.sun.com (8.13.8+Sun/8.13.8/ENSMAIL, v2.2) with ESMTP id m0SKgjZB009441 for ; Mon, 28 Jan 2008 13:42:46 -0700 (MST) Received: from binky.Central.Sun.COM (localhost [127.0.0.1]) by binky.Central.Sun.COM (8.14.1+Sun/8.14.1) with ESMTP id m0SKggZ7014787; Mon, 28 Jan 2008 14:42:42 -0600 (CST) Received: (from nw141292@localhost) by binky.Central.Sun.COM (8.14.1+Sun/8.14.1/Submit) id m0SKgfjY014786; Mon, 28 Jan 2008 14:42:41 -0600 (CST) X-Authentication-Warning: binky.Central.Sun.COM: nw141292 set sender to Nicolas.Williams@sun.com using -f Date: Mon, 28 Jan 2008 14:42:41 -0600 From: Nicolas Williams To: Jeffrey Hutzelman Message-ID: <20080128204241.GK12865@Sun.COM> Mail-Followup-To: Jeffrey Hutzelman , Larry Zhu , IETF Kerberos Working Group , hyc@symas.com, kitten@ietf.org References: <4d569c330712071206q2284c13foad072cecb7ec81fd@mail.gmail.com> <2D438E30-4D65-4CE4-A85D-D096CE162F7E@jpl.nasa.gov> <20080127210717.GU12865@Sun.COM> <20080128194159.GF12865@Sun.COM> <2F99489E062D6942992B552C@sirius.fac.cs.cmu.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <2F99489E062D6942992B552C@sirius.fac.cs.cmu.edu> User-Agent: Mutt/1.5.7i X-Spam-Score: -1.0 (-) X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581 Cc: kitten@ietf.org, Larry Zhu , hyc@symas.com, IETF Kerberos Working Group Subject: Re: [Ietf-krb-wg] the PKU2U DN to Kerberos Principal name mapping X-BeenThere: kitten@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Common Authentication Technologies - Next Generation List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: kitten-bounces@lists.ietf.org On Mon, Jan 28, 2008 at 03:38:17PM -0500, Jeffrey Hutzelman wrote: > I should note that this is not a krb-wg document, and is getting close to > off-topic here. I started the discussion here because I was raising an > issue specifically related to Kerberos and potentially broader than just > PKU2U; namely, handling of mapping X.500 DN's to Kerberos principal names. > It seems that particular issue has been resolved, at least for PKU2U, by > observing that PKU2U needn't expose Kerberos principal names and so doesn't > actually need such a mapping. > > At this point, I think the remaining issues are not particularly Kerberos > specific, and in fact much of this seems to touch on things that affect > other GSS-API mechanisms and the work of the Kitten WG. I think it might > be worth taking the discussion of naming issues and especially naming > extensions to the Kitten list. KITTEN doesn't work on mechanisms either, but KITTEN is appropriate for discussion of GSS-API naming issues. So, yes, we should take this to the KITTEN list, though eventually PKU2U will be off-topic there also. Nico -- _______________________________________________ Kitten mailing list Kitten@lists.ietf.org https://www1.ietf.org/mailman/listinfo/kitten From kitten-bounces@lists.ietf.org Mon Jan 28 17:19:10 2008 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1JJcJo-0007cF-TN; Mon, 28 Jan 2008 17:19:08 -0500 Received: from kitten by megatron.ietf.org with local (Exim 4.43) id 1JJcJo-0007cA-AO for kitten-confirm+ok@megatron.ietf.org; Mon, 28 Jan 2008 17:19:08 -0500 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1JJcJn-0007c2-VU for kitten@ietf.org; Mon, 28 Jan 2008 17:19:08 -0500 Received: from chokecherry.srv.cs.cmu.edu ([128.2.185.41]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1JJcJn-0005ic-J1 for kitten@ietf.org; Mon, 28 Jan 2008 17:19:07 -0500 Received: from SIRIUS.FAC.CS.CMU.EDU (SIRIUS.FAC.CS.CMU.EDU [128.2.209.170]) (authenticated bits=0) by chokecherry.srv.cs.cmu.edu (8.13.6/8.13.6) with ESMTP id m0SMJ4IE006988 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 28 Jan 2008 17:19:04 -0500 (EST) Date: Mon, 28 Jan 2008 17:19:04 -0500 From: Jeffrey Hutzelman To: Nicolas Williams Message-ID: <921751834C5870A618F2887B@sirius.fac.cs.cmu.edu> In-Reply-To: <20080128204241.GK12865@Sun.COM> References: <4d569c330712071206q2284c13foad072cecb7ec81fd@mail.gmail.com> <2D438E30-4D65-4CE4-A85D-D096CE162F7E@jpl.nasa.gov> <20080127210717.GU12865@Sun.COM> <20080128194159.GF12865@Sun.COM> <2F99489E062D6942992B552C@sirius.fac.cs.cmu.edu> <20080128204241.GK12865@Sun.COM> X-Mailer: Mulberry/4.0.8 (Linux/x86) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Spam-Score: 0.0 (/) X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d Cc: kitten@ietf.org, Larry Zhu , IETF Kerberos Working Group , jhutz@cmu.edu, hyc@symas.com Subject: Re: [Ietf-krb-wg] the PKU2U DN to Kerberos Principal name mapping X-BeenThere: kitten@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Common Authentication Technologies - Next Generation List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: kitten-bounces@lists.ietf.org --On Monday, January 28, 2008 02:42:41 PM -0600 Nicolas Williams wrote: > On Mon, Jan 28, 2008 at 03:38:17PM -0500, Jeffrey Hutzelman wrote: >> I should note that this is not a krb-wg document, and is getting close >> to off-topic here. I started the discussion here because I was raising >> an issue specifically related to Kerberos and potentially broader than >> just PKU2U; namely, handling of mapping X.500 DN's to Kerberos >> principal names. It seems that particular issue has been resolved, at >> least for PKU2U, by observing that PKU2U needn't expose Kerberos >> principal names and so doesn't actually need such a mapping. >> >> At this point, I think the remaining issues are not particularly >> Kerberos specific, and in fact much of this seems to touch on things >> that affect other GSS-API mechanisms and the work of the Kitten WG. I >> think it might be worth taking the discussion of naming issues and >> especially naming extensions to the Kitten list. > > KITTEN doesn't work on mechanisms either, but KITTEN is appropriate for > discussion of GSS-API naming issues. So, yes, we should take this to > the KITTEN list, though eventually PKU2U will be off-topic there also. I agree, PKU2U is clearly not in KITTEN's charter. However, IMHO it is an appropriate source for expert advice on GSS-API naming issues, and for expertise on GSS-API in general. I believe its members have been asked to look at PKU2U in the past, and their comments would certainly be welcome now, as it nears completion. -- Jeff _______________________________________________ Kitten mailing list Kitten@lists.ietf.org https://www1.ietf.org/mailman/listinfo/kitten From kitten-bounces@lists.ietf.org Mon Jan 28 18:55:11 2008 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1JJdoi-0007m1-CF; Mon, 28 Jan 2008 18:55:08 -0500 Received: from kitten by megatron.ietf.org with local (Exim 4.43) id 1JJdoh-0007lv-2C for kitten-confirm+ok@megatron.ietf.org; Mon, 28 Jan 2008 18:55:07 -0500 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1JJdog-0007ln-H8 for kitten@ietf.org; Mon, 28 Jan 2008 18:55:06 -0500 Received: from brmea-mail-3.sun.com ([192.18.98.34]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1JJdog-0000Qm-3S for kitten@ietf.org; Mon, 28 Jan 2008 18:55:06 -0500 Received: from dm-central-02.central.sun.com ([129.147.62.5]) by brmea-mail-3.sun.com (8.13.6+Sun/8.12.9) with ESMTP id m0SNt5AM000006 for ; Mon, 28 Jan 2008 23:55:05 GMT Received: from binky.Central.Sun.COM (binky.Central.Sun.COM [129.153.128.104]) by dm-central-02.central.sun.com (8.13.8+Sun/8.13.8/ENSMAIL, v2.2) with ESMTP id m0SNt5TF048755 for ; Mon, 28 Jan 2008 16:55:05 -0700 (MST) Received: from binky.Central.Sun.COM (localhost [127.0.0.1]) by binky.Central.Sun.COM (8.14.1+Sun/8.14.1) with ESMTP id m0SNt53J014922; Mon, 28 Jan 2008 17:55:05 -0600 (CST) Received: (from nw141292@localhost) by binky.Central.Sun.COM (8.14.1+Sun/8.14.1/Submit) id m0SNt42S014921; Mon, 28 Jan 2008 17:55:04 -0600 (CST) X-Authentication-Warning: binky.Central.Sun.COM: nw141292 set sender to Nicolas.Williams@sun.com using -f Date: Mon, 28 Jan 2008 17:55:04 -0600 From: Nicolas Williams To: "Henry B. Hotz" Message-ID: <20080128235504.GR12865@Sun.COM> Mail-Followup-To: "Henry B. Hotz" , kitten@ietf.org References: <4d569c330712071206q2284c13foad072cecb7ec81fd@mail.gmail.com> <2D438E30-4D65-4CE4-A85D-D096CE162F7E@jpl.nasa.gov> <20080127210717.GU12865@Sun.COM> <20080128194159.GF12865@Sun.COM> <2F99489E062D6942992B552C@sirius.fac.cs.cmu.edu> <20080128204241.GK12865@Sun.COM> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.7i X-Spam-Score: -1.0 (-) X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d Cc: kitten@ietf.org Subject: Re: [Ietf-krb-wg] the PKU2U DN to Kerberos Principal name mapping X-BeenThere: kitten@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Common Authentication Technologies - Next Generation List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: kitten-bounces@lists.ietf.org On Mon, Jan 28, 2008 at 03:46:07PM -0800, Henry B. Hotz wrote: > Since I'm not on that list, I'll throw my 2 cents in here: [Cc'ing the KITTEN list and you, dropping the KRB WG list.] > It would be nice if you could do a gss_compare_name() between > smith@EXAMPLE.COM and uid=smith,ou=People,dc=example,dc=com and get a > "true" result. I think the detail you threw out was headed in that > direction, but it wasn't clear to me if it would get you all the way > there. Well, that might work given the text I gave Larry in a very specific context, namely that if one of the arguments to GSS_Compare_name() is a NAME object imported with GSS_Import_name() but not canonicalized and the other argument is a NAME object that is what I called a CMN (and therefore there's an underlying cert) then the comparison could be true if that cert had a id-pkinit-san SAN with that krb5 principal name. I'm not sure that we actually want GSS_Compare_name() to sport such behaviour, as opposed to having a new function that does, because it's pushing things a bit to say that the two NAME objects passed to it are equal representations of the same principal. They are representations of the same principal name, just not _equal_ representations of it. I think I'd want a GSS_Match_name() function, or something, to embody this kind of functionality. Nico -- _______________________________________________ Kitten mailing list Kitten@lists.ietf.org https://www1.ietf.org/mailman/listinfo/kitten From kitten-bounces@lists.ietf.org Tue Jan 29 12:42:41 2008 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1JJuTo-0006qc-Mh; Tue, 29 Jan 2008 12:42:40 -0500 Received: from kitten by megatron.ietf.org with local (Exim 4.43) id 1JJuTo-0006qG-7I for kitten-confirm+ok@megatron.ietf.org; Tue, 29 Jan 2008 12:42:40 -0500 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1JJuTn-0006n4-5O for kitten@ietf.org; Tue, 29 Jan 2008 12:42:39 -0500 Received: from jackfruit.srv.cs.cmu.edu ([128.2.201.16]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1JJuTm-0001TZ-Rb for kitten@ietf.org; Tue, 29 Jan 2008 12:42:39 -0500 Received: from SIRIUS.FAC.CS.CMU.EDU (SIRIUS.FAC.CS.CMU.EDU [128.2.209.170]) (authenticated bits=0) by jackfruit.srv.cs.cmu.edu (8.13.6/8.13.6) with ESMTP id m0THgZ4P002112 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 29 Jan 2008 12:42:35 -0500 (EST) Date: Tue, 29 Jan 2008 12:42:35 -0500 From: Jeffrey Hutzelman To: Nicolas Williams , "Henry B. Hotz" Message-ID: In-Reply-To: <20080128235504.GR12865@Sun.COM> References: <4d569c330712071206q2284c13foad072cecb7ec81fd@mail.gmail.com> <2D438E30-4D65-4CE4-A85D-D096CE162F7E@jpl.nasa.gov> <20080127210717.GU12865@Sun.COM> <20080128194159.GF12865@Sun.COM> <2F99489E062D6942992B552C@sirius.fac.cs.cmu.edu> <20080128204241.GK12865@Sun.COM> <20080128235504.GR12865@Sun.COM> X-Mailer: Mulberry/4.0.8 (Linux/x86) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Spam-Score: 0.0 (/) X-Scan-Signature: 08170828343bcf1325e4a0fb4584481c Cc: kitten@ietf.org, jhutz@cmu.edu Subject: Re: [Ietf-krb-wg] the PKU2U DN to Kerberos Principal name mapping X-BeenThere: kitten@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Common Authentication Technologies - Next Generation List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: kitten-bounces@lists.ietf.org --On Monday, January 28, 2008 05:55:04 PM -0600 Nicolas Williams wrote: > I'm not sure that we actually want GSS_Compare_name() to sport such > behaviour, as opposed to having a new function that does, because it's > pushing things a bit to say that the two NAME objects passed to it are > equal representations of the same principal. They are representations > of the same principal name, just not _equal_ representations of it. That's OK. GSS_Compare_name is defined to return a true result when the names represent the same entity, not only when they are the same. This appears to be exactly what GSS_Compare_name is for, so no, I don't think we need a new interface for this. -- Jeff _______________________________________________ Kitten mailing list Kitten@lists.ietf.org https://www1.ietf.org/mailman/listinfo/kitten From kitten-bounces@lists.ietf.org Tue Jan 29 14:20:47 2008 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1JJw0j-00052L-Kt; Tue, 29 Jan 2008 14:20:45 -0500 Received: from kitten by megatron.ietf.org with local (Exim 4.43) id 1JJw0i-0004wX-4G for kitten-confirm+ok@megatron.ietf.org; Tue, 29 Jan 2008 14:20:44 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1JJw0h-0004us-Oi for kitten@ietf.org; Tue, 29 Jan 2008 14:20:43 -0500 Received: from brmea-mail-1.sun.com ([192.18.98.31]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1JJw0h-0000pN-AY for kitten@ietf.org; Tue, 29 Jan 2008 14:20:43 -0500 Received: from dm-central-02.central.sun.com ([129.147.62.5]) by brmea-mail-1.sun.com (8.13.6+Sun/8.12.9) with ESMTP id m0TJKgsC021596 for ; Tue, 29 Jan 2008 19:20:42 GMT Received: from binky.Central.Sun.COM (binky.Central.Sun.COM [129.153.128.104]) by dm-central-02.central.sun.com (8.13.8+Sun/8.13.8/ENSMAIL, v2.2) with ESMTP id m0TJKg5Y017091 for ; Tue, 29 Jan 2008 12:20:42 -0700 (MST) Received: from binky.Central.Sun.COM (localhost [127.0.0.1]) by binky.Central.Sun.COM (8.14.1+Sun/8.14.1) with ESMTP id m0TJKgs8015409; Tue, 29 Jan 2008 13:20:42 -0600 (CST) Received: (from nw141292@localhost) by binky.Central.Sun.COM (8.14.1+Sun/8.14.1/Submit) id m0TJKb6Y015408; Tue, 29 Jan 2008 13:20:37 -0600 (CST) X-Authentication-Warning: binky.Central.Sun.COM: nw141292 set sender to Nicolas.Williams@sun.com using -f Date: Tue, 29 Jan 2008 13:20:37 -0600 From: Nicolas Williams To: Jeffrey Hutzelman Message-ID: <20080129192037.GZ12865@Sun.COM> Mail-Followup-To: Jeffrey Hutzelman , "Henry B. Hotz" , kitten@ietf.org References: <2D438E30-4D65-4CE4-A85D-D096CE162F7E@jpl.nasa.gov> <20080127210717.GU12865@Sun.COM> <20080128194159.GF12865@Sun.COM> <2F99489E062D6942992B552C@sirius.fac.cs.cmu.edu> <20080128204241.GK12865@Sun.COM> <20080128235504.GR12865@Sun.COM> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.7i X-Spam-Score: -1.0 (-) X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228 Cc: kitten@ietf.org, "Henry B. Hotz" Subject: Re: the PKU2U DN to Kerberos Principal name mapping X-BeenThere: kitten@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Common Authentication Technologies - Next Generation List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: kitten-bounces@lists.ietf.org On Tue, Jan 29, 2008 at 12:42:35PM -0500, Jeffrey Hutzelman wrote: > --On Monday, January 28, 2008 05:55:04 PM -0600 Nicolas Williams > wrote: > > >I'm not sure that we actually want GSS_Compare_name() to sport such > >behaviour, as opposed to having a new function that does, because it's > >pushing things a bit to say that the two NAME objects passed to it are > >equal representations of the same principal. They are representations > >of the same principal name, just not _equal_ representations of it. > > That's OK. GSS_Compare_name is defined to return a true result when the > names represent the same entity, not only when they are the same. This > appears to be exactly what GSS_Compare_name is for, so no, I don't think we > need a new interface for this. OK, good. Then I think the text I gave Larry is pretty close. I suppose we need to decide what name-types *must* be supported. I propose: - GSS_C_NT_DN (because that's what the canonical names will be based on! it simply must be supported) - GSS_C_NT_HOSTBASED_SERVICE (because most acceptors will be hosts and generic GSS apps will be using this name-type) - GSS_KRB5_PRINCIPAL_NAME (because, PKU2U being built on PKINIT technology, it should be trivial to support this when id-pkinit-san is present) The other name-types should all be optional. _______________________________________________ Kitten mailing list Kitten@lists.ietf.org https://www1.ietf.org/mailman/listinfo/kitten From kitten-bounces@lists.ietf.org Wed Jan 30 16:37:17 2008 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1JKKcL-0003WD-MA; Wed, 30 Jan 2008 16:37:13 -0500 Received: from kitten by megatron.ietf.org with local (Exim 4.43) id 1JJdgD-0006hD-Pf for kitten-confirm+ok@megatron.ietf.org; Mon, 28 Jan 2008 18:46:21 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1JJdgD-0006h5-6K for kitten@ietf.org; Mon, 28 Jan 2008 18:46:21 -0500 Received: from nmta.jpl.nasa.gov ([137.78.160.214] helo=nmta1.jpl.nasa.gov) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1JJdgC-0001VP-O7 for kitten@ietf.org; Mon, 28 Jan 2008 18:46:21 -0500 Received: from xmta3.jpl.nasa.gov (xmta3.jpl.nasa.gov [137.78.160.111]) by nmta1.jpl.nasa.gov (Switch-3.2.6/Switch-3.2.6) with ESMTP id m0SNkDrj021413; Mon, 28 Jan 2008 15:46:13 -0800 Received: from [128.149.133.44] (laphotz.jpl.nasa.gov [128.149.133.44]) by xmta3.jpl.nasa.gov (Switch-3.2.6/Switch-3.2.6) with ESMTP id m0SNkBaC025775; Mon, 28 Jan 2008 15:46:12 -0800 In-Reply-To: <20080128204241.GK12865@Sun.COM> References: <4d569c330712071206q2284c13foad072cecb7ec81fd@mail.gmail.com> <2D438E30-4D65-4CE4-A85D-D096CE162F7E@jpl.nasa.gov> <20080127210717.GU12865@Sun.COM> <20080128194159.GF12865@Sun.COM> <2F99489E062D6942992B552C@sirius.fac.cs.cmu.edu> <20080128204241.GK12865@Sun.COM> Mime-Version: 1.0 (Apple Message framework v753) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: "Henry B. Hotz" Date: Mon, 28 Jan 2008 15:46:07 -0800 To: Nicolas Williams X-Mailer: Apple Mail (2.753) X-Source-IP: laphotz.jpl.nasa.gov [128.149.133.44] X-Source-Sender: hotz@jpl.nasa.gov X-AUTH: Authorized X-Spam-Score: -4.0 (----) X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081 X-Mailman-Approved-At: Wed, 30 Jan 2008 16:37:12 -0500 Cc: kitten@ietf.org, hyc@symas.com, IETF Kerberos Working Group , Jeffrey Hutzelman Subject: Re: [Ietf-krb-wg] the PKU2U DN to Kerberos Principal name mapping X-BeenThere: kitten@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Common Authentication Technologies - Next Generation List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: kitten-bounces@lists.ietf.org On Jan 28, 2008, at 12:42 PM, Nicolas Williams wrote: > On Mon, Jan 28, 2008 at 03:38:17PM -0500, Jeffrey Hutzelman wrote: >> I should note that this is not a krb-wg document, and is getting >> close to >> off-topic here. I started the discussion here because I was >> raising an >> issue specifically related to Kerberos and potentially broader >> than just >> PKU2U; namely, handling of mapping X.500 DN's to Kerberos >> principal names. >> It seems that particular issue has been resolved, at least for >> PKU2U, by >> observing that PKU2U needn't expose Kerberos principal names and >> so doesn't >> actually need such a mapping. >> >> At this point, I think the remaining issues are not particularly >> Kerberos >> specific, and in fact much of this seems to touch on things that >> affect >> other GSS-API mechanisms and the work of the Kitten WG. I think >> it might >> be worth taking the discussion of naming issues and especially naming >> extensions to the Kitten list. > > KITTEN doesn't work on mechanisms either, but KITTEN is appropriate > for > discussion of GSS-API naming issues. So, yes, we should take this to > the KITTEN list, though eventually PKU2U will be off-topic there also. > > Nico Since I'm not on that list, I'll throw my 2 cents in here: It would be nice if you could do a gss_compare_name() between smith@EXAMPLE.COM and uid=smith,ou=People,dc=example,dc=com and get a "true" result. I think the detail you threw out was headed in that direction, but it wasn't clear to me if it would get you all the way there. ------------------------------------------------------------------------ The opinions expressed in this message are mine, not those of Caltech, JPL, NASA, or the US Government. Henry.B.Hotz@jpl.nasa.gov, or hbhotz@oxy.edu _______________________________________________ Kitten mailing list Kitten@lists.ietf.org https://www1.ietf.org/mailman/listinfo/kitten From kitten-bounces@lists.ietf.org Wed Jan 30 16:54:19 2008 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1JKKss-0000sF-Gf; Wed, 30 Jan 2008 16:54:18 -0500 Received: from kitten by megatron.ietf.org with local (Exim 4.43) id 1JKKsq-0000pu-Q1 for kitten-confirm+ok@megatron.ietf.org; Wed, 30 Jan 2008 16:54:16 -0500 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1JKKsp-0000oy-Vs for kitten@ietf.org; Wed, 30 Jan 2008 16:54:16 -0500 Received: from biscayne-one-station.mit.edu ([18.7.7.80]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1JKKsp-00038T-Hm for kitten@ietf.org; Wed, 30 Jan 2008 16:54:15 -0500 Received: from outgoing.mit.edu (OUTGOING-AUTH.MIT.EDU [18.7.22.103]) by biscayne-one-station.mit.edu (8.13.6/8.9.2) with ESMTP id m0ULpsIR004792; Wed, 30 Jan 2008 16:51:54 -0500 (EST) Received: from [18.18.1.160] (NOME-KING.MIT.EDU [18.18.1.160]) (authenticated bits=0) (User authenticated as raeburn@ATHENA.MIT.EDU) by outgoing.mit.edu (8.13.6/8.12.4) with ESMTP id m0ULprKE013757 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Wed, 30 Jan 2008 16:51:53 -0500 (EST) References: <47A0F0B7.7070602@stpeter.im> Mime-Version: 1.0 (Apple Message framework v753) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <413CA133-249C-43F5-AC12-3EBB1E98D0DC@mit.edu> From: Ken Raeburn Date: Wed, 30 Jan 2008 16:51:52 -0500 To: kitten@ietf.org X-Mailer: Apple Mail (2.753) X-Scanned-By: MIMEDefang 2.42 X-Spam-Flag: NO X-Spam-Score: 0.00 Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: 4adaf050708fb13be3316a9eee889caa Cc: Subject: Fwd: [Ietf-krb-wg] [Fwd: [Standards] NEW: XEP-0233 (Use of Domain-Based Service Names in XMPP SASL Negotiation)] X-BeenThere: kitten@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Common Authentication Technologies - Next Generation List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: kitten-bounces@lists.ietf.org Also (more?) of interest in the kitten working group... Ken Begin forwarded message: > From: Peter Saint-Andre > Date: January 30, 2008 16:48:39 EST > To: ietf-krb-wg@lists.anl.gov > Subject: [Ietf-krb-wg] [Fwd: [Standards] NEW: XEP-0233 (Use of > Domain-Based Service Names in XMPP SASL Negotiation)] > X-Spam-Score: 0.12 > > This reuse of the "domain-based-names" I-Ds may be of interest here. > > /psa > > -------- Original Message -------- > From: XMPP Extensions Editor > To: standards@xmpp.org > Date: Wed, 30 Jan 2008 15:28:40 -0600 (CST) > Subject: [Standards] NEW: XEP-0233 (Use of Domain-Based Service Names > in XMPP SASL Negotiation) > > Version 0.1 of XEP-0233 (Use of Domain-Based Service Names in XMPP > SASL > Negotiation) has been released. > > Abstract: This specification defines a method by which a connection > manager associated with an XMPP server can inform a connecting client > about its domain-based service name. > > Changelog: Initial published version. (psa) > > Diff: N/A > > URL: http://www.xmpp.org/extensions/xep-0233.html > > > > _______________________________________________ > ietf-krb-wg mailing list > ietf-krb-wg@lists.anl.gov > https://lists.anl.gov/mailman/listinfo/ietf-krb-wg _______________________________________________ Kitten mailing list Kitten@lists.ietf.org https://www1.ietf.org/mailman/listinfo/kitten