From kitten-bounces@lists.ietf.org Tue Sep 05 07:39:54 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GKZH2-0006bD-Rw; Tue, 05 Sep 2006 07:39:24 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GKZH1-0006Z5-26
	for kitten@ietf.org; Tue, 05 Sep 2006 07:39:23 -0400
Received: from rufus.isode.com ([62.3.217.251])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GKZGz-0005ys-Ab
	for kitten@ietf.org; Tue, 05 Sep 2006 07:39:23 -0400
Received: from [172.16.1.99] (shiny.isode.com [62.3.217.250]) 
	by rufus.isode.com (submission channel) via TCP with ESMTPA 
	id <RP1h5QAtqbJt@rufus.isode.com>; Tue, 5 Sep 2006 12:39:19 +0100
Message-ID: <44FD61DE.30105@isode.com>
Date: Tue, 05 Sep 2006 12:39:10 +0100
From: Alexey Melnikov <alexey.melnikov@isode.com>
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
MIME-Version: 1.0
To: Nicolas Williams <Nicolas.Williams@sun.com>
References: <20060829205723.GM10458@binky.Central.Sun.COM>
	<20060831171239.GB29007@binky.Central.Sun.COM>
In-Reply-To: <20060831171239.GB29007@binky.Central.Sun.COM>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3
Cc: kitten@ietf.org, ietf-krb-wg@anl.gov, ietf-sasl@imc.org
Subject: Re: Text (Re: Proposed updates for domain-based drafts)
X-BeenThere: kitten@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Common Authentication Technologies - Next Generation
	<kitten.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/kitten>,
	<mailto:kitten-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/kitten>
List-Post: <mailto:kitten@lists.ietf.org>
List-Help: <mailto:kitten-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/kitten>,
	<mailto:kitten-request@lists.ietf.org?subject=subscribe>
Errors-To: kitten-bounces@lists.ietf.org

Nicolas Williams wrote:

>    A domain-based name consists of three required elements:
> 
>    o  a service name
> 
>    o  a domain name
> 
>    o  a hostname
> 
>+   For the purposes of domain-based names a "domain" is defined by the
>+   applications that use domain-based names.  An application protocol
>+   might use a simple DNS domainname, such as "example.com" for naming,
>+   while another it might use the DNS domainname of the SRV RRs it
>+   queries (e.g., "_tcp._foo.example.com"), and yet another may use
>+   something that does not resemble a DNS domainname.  Application
>+   protocol specifications that provide for use of domain-based service
>+   names MUST define the domain-portion of their domain-based names.
>  
>
I like the suggested changes, except for the last sentence quoted above. 
Here you are trying to put requirements on application protocols, which 
is probably Ok. But you are effectively declaring all existing 
application layer protocols non compliant with this MUST. Was this the 
intent?


_______________________________________________
Kitten mailing list
Kitten@lists.ietf.org
https://www1.ietf.org/mailman/listinfo/kitten



From kitten-bounces@lists.ietf.org Tue Sep 05 09:09:04 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GKafd-0005P5-Fy; Tue, 05 Sep 2006 09:08:53 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GKafb-0005Od-RM
	for kitten@ietf.org; Tue, 05 Sep 2006 09:08:51 -0400
Received: from cpe-68-175-91-105.nyc.res.rr.com ([68.175.91.105]
	helo=www.secure-endpoints.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GKafa-0004Ms-H5
	for kitten@ietf.org; Tue, 05 Sep 2006 09:08:51 -0400
Received: from [192.168.1.13] by secure-endpoints.com
	(Cipher TLSv1:RC4-MD5:128) (MDaemon PRO v9.0.6)
	with ESMTP id md50000028469.msg
	for <kitten@ietf.org>; Tue, 05 Sep 2006 09:10:58 -0400
Message-ID: <44FD7763.2010704@secure-endpoints.com>
Date: Tue, 05 Sep 2006 09:10:59 -0400
From: Jeffrey Altman <jaltman@secure-endpoints.com>
Organization: Secure Endpoints Inc.
User-Agent: Thunderbird 1.5.0.5 (Windows/20060719)
MIME-Version: 1.0
To: Alexey Melnikov <alexey.melnikov@isode.com>
References: <20060829205723.GM10458@binky.Central.Sun.COM>	<20060831171239.GB29007@binky.Central.Sun.COM>
	<44FD61DE.30105@isode.com>
In-Reply-To: <44FD61DE.30105@isode.com>
X-Enigmail-Version: 0.94.0.0
X-Authenticated-Sender: jaltman@secure-endpoints.com
X-Spam-Processed: secure-endpoints.com, Tue, 05 Sep 2006 09:10:58 -0400
	(not processed: message from valid local sender)
X-Return-Path: jaltman@secure-endpoints.com
X-Envelope-From: jaltman@secure-endpoints.com
X-MDaemon-Deliver-To: kitten@ietf.org
X-Spam-Score: 0.2 (/)
X-Scan-Signature: c83ccb5cc10e751496398f1233ca9c3a
Cc: kitten@ietf.org, ietf-krb-wg@anl.gov, ietf-sasl@imc.org,
	Nicolas Williams <Nicolas.Williams@sun.com>
Subject: Re: Text (Re: Proposed updates for domain-based drafts)
X-BeenThere: kitten@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Common Authentication Technologies - Next Generation
	<kitten.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/kitten>,
	<mailto:kitten-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/kitten>
List-Post: <mailto:kitten@lists.ietf.org>
List-Help: <mailto:kitten-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/kitten>,
	<mailto:kitten-request@lists.ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============2123152819=="
Errors-To: kitten-bounces@lists.ietf.org

This is a cryptographically signed message in MIME format.

--===============2123152819==
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature";
	micalg=sha1; boundary="------------ms050509090406060804050909"

This is a cryptographically signed message in MIME format.

--------------ms050509090406060804050909
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Alexey Melnikov wrote:
> Nicolas Williams wrote:
> 
>>    A domain-based name consists of three required elements:
>>
>>    o  a service name
>>
>>    o  a domain name
>>
>>    o  a hostname
>>
>> +   For the purposes of domain-based names a "domain" is defined by the
>> +   applications that use domain-based names.  An application protocol
>> +   might use a simple DNS domainname, such as "example.com" for naming,
>> +   while another it might use the DNS domainname of the SRV RRs it
>> +   queries (e.g., "_tcp._foo.example.com"), and yet another may use
>> +   something that does not resemble a DNS domainname.  Application
>> +   protocol specifications that provide for use of domain-based service
>> +   names MUST define the domain-portion of their domain-based names.
>>  
>>
> I like the suggested changes, except for the last sentence quoted above.
> Here you are trying to put requirements on application protocols, which
> is probably Ok. But you are effectively declaring all existing
> application layer protocols non compliant with this MUST. Was this the
> intent?

The way I read this is that the MUST does not apply to existing
application protocols because they do not "provide for the use of
domain-based service names".  Only new application protocols that
specify the use of domain-based service names will need to define what a
"domain" is for that application.

Jeffrey Altman

--------------ms050509090406060804050909
Content-Type: application/x-pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIJeTCC
AxcwggKAoAMCAQICEBW00lKwoWJXt8wbmTl1M0kwDQYJKoZIhvcNAQEEBQAwYjELMAkGA1UE
BhMCWkExJTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMT
I1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBMB4XDTA2MDUyNzIyMDMzMloX
DTA3MDUyNzIyMDMzMlowczEPMA0GA1UEBBMGQWx0bWFuMRUwEwYDVQQqEwxKZWZmcmV5IEVy
aWMxHDAaBgNVBAMTE0plZmZyZXkgRXJpYyBBbHRtYW4xKzApBgkqhkiG9w0BCQEWHGphbHRt
YW5Ac2VjdXJlLWVuZHBvaW50cy5jb20wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIB
AQC19SD7DncCP/+wfQlLzAAcxf1nJ/7UQgh4o/nxzvuY55XwHdLQjqWuFUnM5vecfyZKwq0o
fGCucDfcQbSIrkhHD9z4TZ8vDaYWVY9Foz8Rp8G0PNdbRFoFtfJbaeVBX5hG3aQXIc/T1b9U
8uN3kLyqXAFIGWKO8DJVGTKKtOiPVOp1U+9CwujyYmUSKF+suutKABhhK1ZGHsTnFczLZ2g0
ma0H7PiFJ2kLfOf///07E1fbr4IRb+cd87kpWLcjtEZ0rbBr9HlOy9dkeEii/qFoo1ahfKCD
A9bNErMiOXA3dudaNNzXlN/70slq5fboBXbepamJGrsnXYcCsS9+LtCTAgMBAAGjOTA3MCcG
A1UdEQQgMB6BHGphbHRtYW5Ac2VjdXJlLWVuZHBvaW50cy5jb20wDAYDVR0TAQH/BAIwADAN
BgkqhkiG9w0BAQQFAAOBgQDBzWhkrW+ol3iyT1rV8ZBQB0+z/6dFH3djQfNf7jDXNoXx4Vbo
pA7BAR4ihAPibv7j7ZaxmyMxWiDACRGS934uvUS0K6L6q14hTWMostJgFsAEDArrmbrES03v
L3EVETiGFqTB2sLp5MLc6+z+72pLXRuDPL3lO2GOQuBbILswRzCCAxcwggKAoAMCAQICEBW0
0lKwoWJXt8wbmTl1M0kwDQYJKoZIhvcNAQEEBQAwYjELMAkGA1UEBhMCWkExJTAjBgNVBAoT
HFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25h
bCBGcmVlbWFpbCBJc3N1aW5nIENBMB4XDTA2MDUyNzIyMDMzMloXDTA3MDUyNzIyMDMzMlow
czEPMA0GA1UEBBMGQWx0bWFuMRUwEwYDVQQqEwxKZWZmcmV5IEVyaWMxHDAaBgNVBAMTE0pl
ZmZyZXkgRXJpYyBBbHRtYW4xKzApBgkqhkiG9w0BCQEWHGphbHRtYW5Ac2VjdXJlLWVuZHBv
aW50cy5jb20wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQC19SD7DncCP/+wfQlL
zAAcxf1nJ/7UQgh4o/nxzvuY55XwHdLQjqWuFUnM5vecfyZKwq0ofGCucDfcQbSIrkhHD9z4
TZ8vDaYWVY9Foz8Rp8G0PNdbRFoFtfJbaeVBX5hG3aQXIc/T1b9U8uN3kLyqXAFIGWKO8DJV
GTKKtOiPVOp1U+9CwujyYmUSKF+suutKABhhK1ZGHsTnFczLZ2g0ma0H7PiFJ2kLfOf///07
E1fbr4IRb+cd87kpWLcjtEZ0rbBr9HlOy9dkeEii/qFoo1ahfKCDA9bNErMiOXA3dudaNNzX
lN/70slq5fboBXbepamJGrsnXYcCsS9+LtCTAgMBAAGjOTA3MCcGA1UdEQQgMB6BHGphbHRt
YW5Ac2VjdXJlLWVuZHBvaW50cy5jb20wDAYDVR0TAQH/BAIwADANBgkqhkiG9w0BAQQFAAOB
gQDBzWhkrW+ol3iyT1rV8ZBQB0+z/6dFH3djQfNf7jDXNoXx4VbopA7BAR4ihAPibv7j7Zax
myMxWiDACRGS934uvUS0K6L6q14hTWMostJgFsAEDArrmbrES03vL3EVETiGFqTB2sLp5MLc
6+z+72pLXRuDPL3lO2GOQuBbILswRzCCAz8wggKooAMCAQICAQ0wDQYJKoZIhvcNAQEFBQAw
gdExCzAJBgNVBAYTAlpBMRUwEwYDVQQIEwxXZXN0ZXJuIENhcGUxEjAQBgNVBAcTCUNhcGUg
VG93bjEaMBgGA1UEChMRVGhhd3RlIENvbnN1bHRpbmcxKDAmBgNVBAsTH0NlcnRpZmljYXRp
b24gU2VydmljZXMgRGl2aXNpb24xJDAiBgNVBAMTG1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFp
bCBDQTErMCkGCSqGSIb3DQEJARYccGVyc29uYWwtZnJlZW1haWxAdGhhd3RlLmNvbTAeFw0w
MzA3MTcwMDAwMDBaFw0xMzA3MTYyMzU5NTlaMGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxU
aGF3dGUgQ29uc3VsdGluZyAoUHR5KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwg
RnJlZW1haWwgSXNzdWluZyBDQTCBnzANBgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEAxKY8VXNV
+065yplaHmjAdQRwnd/p/6Me7L3N9VvyGna9fww6YfK/Uc4B1OVQCjDXAmNaLIkVcI7dyfAr
hVqqP3FWy688Cwfn8R+RNiQqE88r1fOCdz0Dviv+uxg+B79AgAJk16emu59l0cUqVIUPSAR/
p7bRPGEEQB5kGXJgt/sCAwEAAaOBlDCBkTASBgNVHRMBAf8ECDAGAQH/AgEAMEMGA1UdHwQ8
MDowOKA2oDSGMmh0dHA6Ly9jcmwudGhhd3RlLmNvbS9UaGF3dGVQZXJzb25hbEZyZWVtYWls
Q0EuY3JsMAsGA1UdDwQEAwIBBjApBgNVHREEIjAgpB4wHDEaMBgGA1UEAxMRUHJpdmF0ZUxh
YmVsMi0xMzgwDQYJKoZIhvcNAQEFBQADgYEASIzRUIPqCy7MDaNmrGcPf6+svsIXoUOWlJ1/
TCG4+DYfqi2fNi/A9BxQIJNwPP2t4WFiw9k6GX6EsZkbAMUaC4J0niVQlGLH2ydxVyWN3amc
OY6MIE9lX5Xa9/eH1sYITq726jTlEBpbNU1341YheILcIRk13iSx0x1G/11fZU8xggNkMIID
YAIBATB2MGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxUaGF3dGUgQ29uc3VsdGluZyAoUHR5
KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwgRnJlZW1haWwgSXNzdWluZyBDQQIQ
FbTSUrChYle3zBuZOXUzSTAJBgUrDgMCGgUAoIIBwzAYBgkqhkiG9w0BCQMxCwYJKoZIhvcN
AQcBMBwGCSqGSIb3DQEJBTEPFw0wNjA5MDUxMzEwNTlaMCMGCSqGSIb3DQEJBDEWBBQ3H0NZ
hKlCSemD06BrNEvHMGXe3jBSBgkqhkiG9w0BCQ8xRTBDMAoGCCqGSIb3DQMHMA4GCCqGSIb3
DQMCAgIAgDANBggqhkiG9w0DAgIBQDAHBgUrDgMCBzANBggqhkiG9w0DAgIBKDCBhQYJKwYB
BAGCNxAEMXgwdjBiMQswCQYDVQQGEwJaQTElMCMGA1UEChMcVGhhd3RlIENvbnN1bHRpbmcg
KFB0eSkgTHRkLjEsMCoGA1UEAxMjVGhhd3RlIFBlcnNvbmFsIEZyZWVtYWlsIElzc3Vpbmcg
Q0ECEBW00lKwoWJXt8wbmTl1M0kwgYcGCyqGSIb3DQEJEAILMXigdjBiMQswCQYDVQQGEwJa
QTElMCMGA1UEChMcVGhhd3RlIENvbnN1bHRpbmcgKFB0eSkgTHRkLjEsMCoGA1UEAxMjVGhh
d3RlIFBlcnNvbmFsIEZyZWVtYWlsIElzc3VpbmcgQ0ECEBW00lKwoWJXt8wbmTl1M0kwDQYJ
KoZIhvcNAQEBBQAEggEAY66skqLeJFCxiVXywXg4ErTHAfBjchmgY/jSNipD9u7MAOngo4aV
bO3ulQSY7XLBf/ClgZpM5yrY77QMDF/Pk5SuvTICvaVmCVokIRMePfuswz2R0aW4prxkx0z8
ll3E4pO0d3JNa+Py98jTK5ZgBWrssj+9ns2KxxgRU1yWB8vxfgJTpkyXrIC1EW8w0ykLBBf/
hJJwKXXe1laCNmzxoSLkmJ+CoLGgfbFPQActwcCzBvTUBjMG2LOK2wzO+xPUCPgo5WIAcY4b
AurMCMOy928Zx/N1+wBJ3zkYGrGpMhufPI1h7BKR+bAA20OFIwFd28yr9eUmpkZgVVdjsSLM
/QAAAAAAAA==
--------------ms050509090406060804050909--



--===============2123152819==
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

--===============2123152819==--





From kitten-bounces@lists.ietf.org Tue Sep 05 09:26:49 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GKawq-000255-OQ; Tue, 05 Sep 2006 09:26:40 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GKawp-000240-FW
	for kitten@ietf.org; Tue, 05 Sep 2006 09:26:39 -0400
Received: from nwkea-mail-1.sun.com ([192.18.42.13])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GKawm-000255-0f
	for kitten@ietf.org; Tue, 05 Sep 2006 09:26:39 -0400
Received: from centralmail4brm.central.Sun.COM ([129.147.62.198])
	by nwkea-mail-1.sun.com (8.13.6+Sun/8.12.9) with ESMTP id
	k85DQZcU029808
	for <kitten@ietf.org>; Tue, 5 Sep 2006 06:26:35 -0700 (PDT)
Received: from binky.Central.Sun.COM (binky.Central.Sun.COM [129.153.128.104])
	by centralmail4brm.central.Sun.COM (8.13.6+Sun/8.13.6/ENSMAIL,
	v2.2) with ESMTP id k85DQJQQ026996
	for <kitten@ietf.org>; Tue, 5 Sep 2006 07:26:34 -0600 (MDT)
Received: from binky.Central.Sun.COM (localhost [127.0.0.1])
	by binky.Central.Sun.COM (8.13.6+Sun/8.13.6) with ESMTP id
	k85DOiSI027994; Tue, 5 Sep 2006 08:24:54 -0500 (CDT)
Received: (from nw141292@localhost)
	by binky.Central.Sun.COM (8.13.6+Sun/8.13.6/Submit) id k85DOhfN027993; 
	Tue, 5 Sep 2006 08:24:43 -0500 (CDT)
Date: Tue, 5 Sep 2006 08:24:43 -0500
From: Nicolas Williams <Nicolas.Williams@sun.com>
To: Alexey Melnikov <alexey.melnikov@isode.com>
Message-ID: <20060905132442.GC27961@binky.Central.Sun.COM>
Mail-Followup-To: Alexey Melnikov <alexey.melnikov@isode.com>,
	kitten@ietf.org, ietf-sasl@imc.org, ietf-krb-wg@anl.gov
References: <20060829205723.GM10458@binky.Central.Sun.COM>
	<20060831171239.GB29007@binky.Central.Sun.COM>
	<44FD61DE.30105@isode.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <44FD61DE.30105@isode.com>
User-Agent: Mutt/1.5.7i
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 93238566e09e6e262849b4f805833007
Cc: kitten@ietf.org, ietf-krb-wg@anl.gov, ietf-sasl@imc.org
Subject: Re: Text (Re: Proposed updates for domain-based drafts)
X-BeenThere: kitten@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Common Authentication Technologies - Next Generation
	<kitten.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/kitten>,
	<mailto:kitten-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/kitten>
List-Post: <mailto:kitten@lists.ietf.org>
List-Help: <mailto:kitten-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/kitten>,
	<mailto:kitten-request@lists.ietf.org?subject=subscribe>
Errors-To: kitten-bounces@lists.ietf.org

On Tue, Sep 05, 2006 at 12:39:10PM +0100, Alexey Melnikov wrote:
> Nicolas Williams wrote:
> >+   For the purposes of domain-based names a "domain" is defined by the
> >+   applications that use domain-based names.  An application protocol
> >+   might use a simple DNS domainname, such as "example.com" for naming,
> >+   while another it might use the DNS domainname of the SRV RRs it
> >+   queries (e.g., "_tcp._foo.example.com"), and yet another may use
> >+   something that does not resemble a DNS domainname.  Application
> >+   protocol specifications that provide for use of domain-based service
> >+   names MUST define the domain-portion of their domain-based names.
> > 
> >
> I like the suggested changes, except for the last sentence quoted above. 
> Here you are trying to put requirements on application protocols, which 
> is probably Ok. But you are effectively declaring all existing 
> application layer protocols non compliant with this MUST. Was this the 
> intent?

Not at all -- existing apps don't know how to use domain-based names, so
they will require updating anyways.  This is a requirement only for
applications that wish to support the use of domain-based names.

Nico
-- 

_______________________________________________
Kitten mailing list
Kitten@lists.ietf.org
https://www1.ietf.org/mailman/listinfo/kitten



From kitten-bounces@lists.ietf.org Tue Sep 05 10:50:35 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GKcFm-0004pw-54; Tue, 05 Sep 2006 10:50:18 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GKcFc-0004nC-ST
	for kitten@lists.ietf.org; Tue, 05 Sep 2006 10:50:08 -0400
Received: from ns1.neustar.com ([2001:503:c779:1a::9c9a:108a])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GKcFV-0001tZ-Ng
	for kitten@lists.ietf.org; Tue, 05 Sep 2006 10:50:08 -0400
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns1.neustar.com (Postfix) with ESMTP id A323A2AB67;
	Tue,  5 Sep 2006 14:50:01 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1GKcFV-0008Nx-HJ; Tue, 05 Sep 2006 10:50:01 -0400
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1GKcFV-0008Nx-HJ@stiedprstage1.ietf.org>
Date: Tue, 05 Sep 2006 10:50:01 -0400
X-Spam-Score: -2.5 (--)
X-Scan-Signature: a2c12dacc0736f14d6b540e805505a86
Cc: kitten@lists.ietf.org
Subject: I-D ACTION:draft-ietf-kitten-gss-naming-05.txt 
X-BeenThere: kitten@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Common Authentication Technologies - Next Generation
	<kitten.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/kitten>,
	<mailto:kitten-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/kitten>
List-Post: <mailto:kitten@lists.ietf.org>
List-Help: <mailto:kitten-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/kitten>,
	<mailto:kitten-request@lists.ietf.org?subject=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		: Desired Enhancements to GSSAPI Version 3 Naming
	Author(s)	: S. Hartman
	Filename	: draft-ietf-kitten-gss-naming-05.txt
	Pages		: 17
	Date		: 2006-9-5
	
The Generic Security Services API (GSS-API) provides a naming
architecture that supports name-based authorization.  GSS-API
authenticates two named parties to each other.  Names can be stored
on access control lists to make authorization decisions.  Advances in
security mechanisms and the way implementers wish to use GSS-API
require this model to be extended for the next version of GSS-API.
As people move within an organization or change their names, the name
authenticated by GSS-API may change.  Using some sort of constant
identifier would make ACLs more stable.  Some mechanisms such as
public-key mechanisms do not have a single name to be used across all
environments.  Other mechanisms such as Kerberos may include group
membership or role information as part of authentication.  This
document motivates extensions to GSS-API naming and describes the
extensions under discussion.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-kitten-gss-naming-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-gss-naming-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-gss-naming-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: <2006-9-5021629.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-kitten-gss-naming-05.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-kitten-gss-naming-05.txt"; site="ftp.ietf.org";
	access-type="anon-ftp"; directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2006-9-5021629.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 Tue Sep 05 11:15:02 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GKcdi-0000ld-BA; Tue, 05 Sep 2006 11:15:02 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GKcdh-0000jh-N0
	for kitten@ietf.org; Tue, 05 Sep 2006 11:15:01 -0400
Received: from carter-zimmerman.dyn.mit.edu ([18.188.3.148]
	helo=carter-zimmerman.mit.edu)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GKcdg-0007MF-Hb
	for kitten@ietf.org; Tue, 05 Sep 2006 11:15:01 -0400
Received: by carter-zimmerman.mit.edu (Postfix, from userid 8042)
	id CE916E0127; Tue,  5 Sep 2006 11:14:52 -0400 (EDT)
From: Sam Hartman <hartmans-ietf@mit.edu>
To: kitten@ietf.org
References: <E1GKcFV-0008Nx-HJ@stiedprstage1.ietf.org>
Date: Tue, 05 Sep 2006 11:14:52 -0400
In-Reply-To: <E1GKcFV-0008Nx-HJ@stiedprstage1.ietf.org>
	(Internet-Drafts@ietf.org's message of "Tue, 05 Sep 2006 10:50:01
	-0400")
Message-ID: <tsly7sy2vmb.fsf@cz.mit.edu>
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: 01485d64dfa90b45a74269b3ca9d5574
Cc: 
Subject: Re: I-D ACTION:draft-ietf-kitten-gss-naming-05.txt
X-BeenThere: kitten@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Common Authentication Technologies - Next Generation
	<kitten.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/kitten>,
	<mailto:kitten-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/kitten>
List-Post: <mailto:kitten@lists.ietf.org>
List-Help: <mailto:kitten-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/kitten>,
	<mailto:kitten-request@lists.ietf.org?subject=subscribe>
Errors-To: kitten-bounces@lists.ietf.org

This version of the draft addresses minor AD review comments from Russ
Housley.


_______________________________________________
Kitten mailing list
Kitten@lists.ietf.org
https://www1.ietf.org/mailman/listinfo/kitten



From kitten-bounces@lists.ietf.org Tue Sep 05 15:00:47 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GKg9z-00064I-7o; Tue, 05 Sep 2006 15:00:35 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GKg9x-00063P-VD
	for kitten@ietf.org; Tue, 05 Sep 2006 15:00:33 -0400
Received: from chokecherry.srv.cs.cmu.edu ([128.2.185.41])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GKg9v-0000nY-MK
	for kitten@ietf.org; Tue, 05 Sep 2006 15:00:33 -0400
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
	k85J0NcV005375
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Tue, 5 Sep 2006 15:00:23 -0400 (EDT)
Date: Tue, 05 Sep 2006 15:00:23 -0400
From: Jeffrey Hutzelman <jhutz@cmu.edu>
To: Nicolas Williams <Nicolas.Williams@sun.com>,
	Alexey Melnikov <alexey.melnikov@isode.com>
Message-ID: <0DE3D5E3F7A0FB1DC2EAB136@sirius.fac.cs.cmu.edu>
In-Reply-To: <20060905132442.GC27961@binky.Central.Sun.COM>
References: <20060829205723.GM10458@binky.Central.Sun.COM>
	<20060831171239.GB29007@binky.Central.Sun.COM>
	<44FD61DE.30105@isode.com>
	<20060905132442.GC27961@binky.Central.Sun.COM>
Originator-Info: login-token=Mulberry:01dJ2io94FFxfA6BokpxvSEgsP2c770RvhEtAIqh0=;
	token_authority=postmaster@andrew.cmu.edu
X-Mailer: Mulberry/3.1.6 (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: b19722fc8d3865b147c75ae2495625f2
Cc: kitten@ietf.org, ietf-krb-wg@anl.gov, ietf-sasl@imc.org,
	Jeffrey Hutzelman <jhutz@cmu.edu>
Subject: Re: Text (Re: Proposed updates for domain-based drafts)
X-BeenThere: kitten@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Common Authentication Technologies - Next Generation
	<kitten.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/kitten>,
	<mailto:kitten-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/kitten>
List-Post: <mailto:kitten@lists.ietf.org>
List-Help: <mailto:kitten-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/kitten>,
	<mailto:kitten-request@lists.ietf.org?subject=subscribe>
Errors-To: kitten-bounces@lists.ietf.org



On Tuesday, September 05, 2006 08:24:43 AM -0500 Nicolas Williams 
<Nicolas.Williams@sun.com> wrote:

> On Tue, Sep 05, 2006 at 12:39:10PM +0100, Alexey Melnikov wrote:
>> Nicolas Williams wrote:
>> > +   For the purposes of domain-based names a "domain" is defined by the
>> > +   applications that use domain-based names.  An application protocol
>> > +   might use a simple DNS domainname, such as "example.com" for
>> > naming, +   while another it might use the DNS domainname of the SRV
>> > RRs it +   queries (e.g., "_tcp._foo.example.com"), and yet another
>> > may use +   something that does not resemble a DNS domainname.
>> > Application +   protocol specifications that provide for use of
>> > domain-based service +   names MUST define the domain-portion of their
>> > domain-based names.
>> >
>> >
>> I like the suggested changes, except for the last sentence quoted above.
>> Here you are trying to put requirements on application protocols, which
>> is probably Ok. But you are effectively declaring all existing
>> application layer protocols non compliant with this MUST. Was this the
>> intent?
>
> Not at all -- existing apps don't know how to use domain-based names, so
> they will require updating anyways.  This is a requirement only for
> applications that wish to support the use of domain-based names.

Right.  Just as an application which uses host-based service names needs to 
specify a service name, and application which uses domain-based names needs 
to specify both a service name and how to derive the "domain" component.

-- Jeff

_______________________________________________
Kitten mailing list
Kitten@lists.ietf.org
https://www1.ietf.org/mailman/listinfo/kitten



From kitten-bounces@lists.ietf.org Tue Sep 05 16:03:59 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GKh96-0006rE-Lz; Tue, 05 Sep 2006 16:03:44 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GKh95-0006r3-Vk
	for kitten@ietf.org; Tue, 05 Sep 2006 16:03:43 -0400
Received: from brmea-mail-4.sun.com ([192.18.98.36])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GKh94-0007ck-Ho
	for kitten@ietf.org; Tue, 05 Sep 2006 16:03:43 -0400
Received: from centralmail4brm.central.Sun.COM ([129.147.62.198])
	by brmea-mail-4.sun.com (8.13.6+Sun/8.12.9) with ESMTP id
	k85K3gCZ010515
	for <kitten@ietf.org>; Tue, 5 Sep 2006 14:03:42 -0600 (MDT)
Received: from binky.Central.Sun.COM (binky.Central.Sun.COM [129.153.128.104])
	by centralmail4brm.central.Sun.COM (8.13.6+Sun/8.13.6/ENSMAIL,
	v2.2) with ESMTP id k85K3Qgh024464
	for <kitten@ietf.org>; Tue, 5 Sep 2006 14:03:41 -0600 (MDT)
Received: from binky.Central.Sun.COM (localhost [127.0.0.1])
	by binky.Central.Sun.COM (8.13.6+Sun/8.13.6) with ESMTP id
	k85K2pRH028597; Tue, 5 Sep 2006 15:02:51 -0500 (CDT)
Received: (from nw141292@localhost)
	by binky.Central.Sun.COM (8.13.6+Sun/8.13.6/Submit) id k85K2noV028596; 
	Tue, 5 Sep 2006 15:02:49 -0500 (CDT)
Date: Tue, 5 Sep 2006 15:02:49 -0500
From: Nicolas Williams <Nicolas.Williams@sun.com>
To: Alexey Melnikov <alexey.melnikov@isode.com>, kitten@ietf.org,
	ietf-sasl@imc.org, ietf-krb-wg@anl.gov
Message-ID: <20060905200248.GD28489@binky.Central.Sun.COM>
Mail-Followup-To: Alexey Melnikov <alexey.melnikov@isode.com>,
	kitten@ietf.org, ietf-sasl@imc.org, ietf-krb-wg@anl.gov
References: <20060829205723.GM10458@binky.Central.Sun.COM>
	<20060831171239.GB29007@binky.Central.Sun.COM>
	<44FD61DE.30105@isode.com>
	<20060905132442.GC27961@binky.Central.Sun.COM>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20060905132442.GC27961@binky.Central.Sun.COM>
User-Agent: Mutt/1.5.7i
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab
Cc: 
Subject: Re: Text (Re: Proposed updates for domain-based drafts)
X-BeenThere: kitten@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Common Authentication Technologies - Next Generation
	<kitten.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/kitten>,
	<mailto:kitten-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/kitten>
List-Post: <mailto:kitten@lists.ietf.org>
List-Help: <mailto:kitten-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/kitten>,
	<mailto:kitten-request@lists.ietf.org?subject=subscribe>
Errors-To: kitten-bounces@lists.ietf.org

On Tue, Sep 05, 2006 at 08:24:43AM -0500, Nicolas Williams wrote:
> On Tue, Sep 05, 2006 at 12:39:10PM +0100, Alexey Melnikov wrote:
> > Nicolas Williams wrote:
> > I like the suggested changes, except for the last sentence quoted above. 
> > Here you are trying to put requirements on application protocols, which 
> > is probably Ok. But you are effectively declaring all existing 
> > application layer protocols non compliant with this MUST. Was this the 
> > intent?
> 
> Not at all -- existing apps don't know how to use domain-based names, so
> they will require updating anyways.  This is a requirement only for
> applications that wish to support the use of domain-based names.

Also, if your concern is about DIGEST-MD5 applications that use
serv-name then worry not: these drafts are specifically for GSS-API
applications, and clearly no SASL/GS1 applications have used
domain-based names in the past.

OT:  Now, about DIGEST-MD5's support for domain-based naming...  Are
there SASL applications that use this?  Does Cyrus SASL implement this?
Any other implementations?  Please answer off-list, or at least off the
KITTEN list, as this would be off-topic there.

_______________________________________________
Kitten mailing list
Kitten@lists.ietf.org
https://www1.ietf.org/mailman/listinfo/kitten



From kitten-bounces@lists.ietf.org Wed Sep 13 10:50:44 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GNW4U-0003K7-Eb; Wed, 13 Sep 2006 10:50:38 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GNW4R-0003Hc-9P
	for kitten@lists.ietf.org; Wed, 13 Sep 2006 10:50:35 -0400
Received: from stsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.16.129]
	helo=chiedprmail1.ietf.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GNW4R-0007cG-6X
	for kitten@lists.ietf.org; Wed, 13 Sep 2006 10:50:35 -0400
Received: from ns3.neustar.com ([156.154.24.138])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1GNW4O-0000gI-SF
	for kitten@lists.ietf.org; Wed, 13 Sep 2006 10:50:35 -0400
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns3.neustar.com (Postfix) with ESMTP id 92A191758D;
	Wed, 13 Sep 2006 14:50:02 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1GNW3u-00080t-63; Wed, 13 Sep 2006 10:50:02 -0400
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1GNW3u-00080t-63@stiedprstage1.ietf.org>
Date: Wed, 13 Sep 2006 10:50:02 -0400
X-Spam-Score: -5.9 (-----)
X-Scan-Signature: b280b4db656c3ca28dd62e5e0b03daa8
Cc: kitten@lists.ietf.org
Subject: I-D ACTION:draft-ietf-kitten-krb5-gssapi-domain-based-names-03.txt 
X-BeenThere: kitten@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Common Authentication Technologies - Next Generation
	<kitten.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/kitten>,
	<mailto:kitten-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/kitten>
List-Post: <mailto:kitten@lists.ietf.org>
List-Help: <mailto:kitten-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/kitten>,
	<mailto:kitten-request@lists.ietf.org?subject=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-03.txt
	Pages		: 5
	Date		: 2006-9-13
	
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-03.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-03.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-03.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 From kitten-bounces@lists.ietf.org Wed Sep 13 10:50:44 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GNW4U-0003K7-Eb; Wed, 13 Sep 2006 10:50:38 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GNW4R-0003Hc-9P
	for kitten@lists.ietf.org; Wed, 13 Sep 2006 10:50:35 -0400
Received: from stsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.16.129]
	helo=chiedprmail1.ietf.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GNW4R-0007cG-6X
	for kitten@lists.ietf.org; Wed, 13 Sep 2006 10:50:35 -0400
Received: from ns3.neustar.com ([156.154.24.138])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1GNW4O-0000gI-SF
	for kitten@lists.ietf.org; Wed, 13 Sep 2006 10:50:35 -0400
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns3.neustar.com (Postfix) with ESMTP id 92A191758D;
	Wed, 13 Sep 2006 14:50:02 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1GNW3u-00080t-63; Wed, 13 Sep 2006 10:50:02 -0400
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1GNW3u-00080t-63@stiedprstage1.ietf.org>
Date: Wed, 13 Sep 2006 10:50:02 -0400
X-Spam-Score: -5.9 (-----)
X-Scan-Signature: b280b4db656c3ca28dd62e5e0b03daa8
Cc: kitten@lists.ietf.org
Subject: I-D ACTION:draft-ietf-kitten-krb5-gssapi-domain-based-names-03.txt 
X-BeenThere: kitten@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Common Authentication Technologies - Next Generation
	<kitten.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/kitten>,
	<mailto:kitten-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/kitten>
List-Post: <mailto:kitten@lists.ietf.org>
List-Help: <mailto:kitten-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/kitten>,
	<mailto:kitten-request@lists.ietf.org?subject=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-03.txt
	Pages		: 5
	Date		: 2006-9-13
	
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-03.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-03.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-03.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: <2006-9-13095638.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-kitten-krb5-gssapi-domain-based-names-03.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-kitten-krb5-gssapi-domain-based-names-03.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2006-9-13095638.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 Wed Sep 13 10:50:44 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GNW4U-0003KC-Ia; Wed, 13 Sep 2006 10:50:38 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GNW4R-0003Hl-GM
	for kitten@lists.ietf.org; Wed, 13 Sep 2006 10:50:35 -0400
Received: from stsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.16.129]
	helo=chiedprmail1.ietf.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GNW4R-0007cM-EC
	for kitten@lists.ietf.org; Wed, 13 Sep 2006 10:50:35 -0400
Received: from ns4.neustar.com ([156.154.24.139])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1GNW4O-0000gG-F7
	for kitten@lists.ietf.org; Wed, 13 Sep 2006 10:50:35 -0400
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns4.neustar.com (Postfix) with ESMTP id 6190C2AC25;
	Wed, 13 Sep 2006 14:50:02 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1GNW3u-00080q-5S; Wed, 13 Sep 2006 10:50:02 -0400
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1GNW3u-00080q-5S@stiedprstage1.ietf.org>
Date: Wed, 13 Sep 2006 10:50:02 -0400
X-Spam-Score: -5.9 (-----)
X-Scan-Signature: 386e0819b1192672467565a524848168
Cc: kitten@lists.ietf.org
Subject: I-D ACTION:draft-ietf-kitten-gssapi-domain-based-names-03.txt 
X-BeenThere: kitten@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Common Authentication Technologies - Next Generation
	<kitten.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/kitten>,
	<mailto:kitten-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/kitten>
List-Post: <mailto:kitten@lists.ietf.org>
List-Help: <mailto:kitten-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/kitten>,
	<mailto:kitten-request@lists.ietf.org?subject=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 and Name Type
	Author(s)	: N. Williams
	Filename	: draft-ietf-kitten-gssapi-domain-based-names-03.txt
	Pages		: 11
	Date		: 2006-9-13
	
This document describes domainname-based service principal names and
the corresponding name type for the Generic Security Service
Application Programming Interface (GSS-API).

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 achilocal 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: <2006-9-13095638.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-kitten-krb5-gssapi-domain-based-names-03.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-kitten-krb5-gssapi-domain-based-names-03.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2006-9-13095638.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 Wed Sep 13 10:50:44 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GNW4U-0003KC-Ia; Wed, 13 Sep 2006 10:50:38 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GNW4R-0003Hl-GM
	for kitten@lists.ietf.org; Wed, 13 Sep 2006 10:50:35 -0400
Received: from stsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.16.129]
	helo=chiedprmail1.ietf.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GNW4R-0007cM-EC
	for kitten@lists.ietf.org; Wed, 13 Sep 2006 10:50:35 -0400
Received: from ns4.neustar.com ([156.154.24.139])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1GNW4O-0000gG-F7
	for kitten@lists.ietf.org; Wed, 13 Sep 2006 10:50:35 -0400
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns4.neustar.com (Postfix) with ESMTP id 6190C2AC25;
	Wed, 13 Sep 2006 14:50:02 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1GNW3u-00080q-5S; Wed, 13 Sep 2006 10:50:02 -0400
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1GNW3u-00080q-5S@stiedprstage1.ietf.org>
Date: Wed, 13 Sep 2006 10:50:02 -0400
X-Spam-Score: -5.9 (-----)
X-Scan-Signature: 386e0819b1192672467565a524848168
Cc: kitten@lists.ietf.org
Subject: I-D ACTION:draft-ietf-kitten-gssapi-domain-based-names-03.txt 
X-BeenThere: kitten@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Common Authentication Technologies - Next Generation
	<kitten.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/kitten>,
	<mailto:kitten-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/kitten>
List-Post: <mailto:kitten@lists.ietf.org>
List-Help: <mailto:kitten-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/kitten>,
	<mailto:kitten-request@lists.ietf.org?subject=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 and Name Type
	Author(s)	: N. Williams
	Filename	: draft-ietf-kitten-gssapi-domain-based-names-03.txt
	Pages		: 11
	Date		: 2006-9-13
	
This document describes domainname-based service principal names and
the corresponding name type for the Generic Security Service
Application Programming Interface (GSS-API).

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-03.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-03.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-03.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: <2006-9-13095419.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-kitten-gssapi-domain-based-names-03.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-kitten-gssapi-domain-based-names-03.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2006-9-13095419.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--







eved 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-03.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-03.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-03.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: <2006-9-13095419.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-kitten-gssapi-domain-based-names-03.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-kitten-gssapi-domain-based-names-03.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2006-9-13095419.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 Sep 22 11:33:54 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GQn26-0001HO-L6; Fri, 22 Sep 2006 11:33:42 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GQn25-0001HG-GN
	for kitten@ietf.org; Fri, 22 Sep 2006 11:33:41 -0400
Received: from brmea-mail-3.sun.com ([192.18.98.34])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GQn21-0003KM-NH
	for kitten@ietf.org; Fri, 22 Sep 2006 11:33:41 -0400
Received: from centralmail3brm.Central.Sun.COM ([129.147.62.199])
	by brmea-mail-3.sun.com (8.13.6+Sun/8.12.9) with ESMTP id
	k8MFXbZC013082
	for <kitten@ietf.org>; Fri, 22 Sep 2006 09:33:37 -0600 (MDT)
Received: from binky.Central.Sun.COM (binky.Central.Sun.COM [129.153.128.104])
	by centralmail3brm.Central.Sun.COM (8.13.6+Sun/8.13.6/ENSMAIL,
	v2.2) with ESMTP id k8MFXalQ024789
	for <kitten@ietf.org>; Fri, 22 Sep 2006 09:33:36 -0600 (MDT)
Received: from binky.Central.Sun.COM (localhost [127.0.0.1])
	by binky.Central.Sun.COM (8.13.6+Sun/8.13.6) with ESMTP id
	k8MFXZ43001251; Fri, 22 Sep 2006 10:33:35 -0500 (CDT)
Received: (from nw141292@localhost)
	by binky.Central.Sun.COM (8.13.6+Sun/8.13.6/Submit) id k8MFXZkC001250; 
	Fri, 22 Sep 2006 10:33:35 -0500 (CDT)
Date: Fri, 22 Sep 2006 10:33:34 -0500
From: Nicolas Williams <Nicolas.Williams@sun.com>
To: Alexey Melnikov <alexey.melnikov@isode.com>
Message-ID: <20060922153334.GW18305@binky.Central.Sun.COM>
Mail-Followup-To: Alexey Melnikov <alexey.melnikov@isode.com>,
	Hai Zaar <haizaar@gmail.com>, kitten@ietf.org
References: <mailman.6604.1158840193.29353.cyrus-sasl@lists.andrew.cmu.edu>
	<cfb54190609210507o717942dcn7e421d1f511d62eb@mail.gmail.com>
	<4512C6B1.6050000@isode.com>
	<20060921183500.GL18305@binky.Central.Sun.COM>
	<4513DBCE.3000005@isode.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4513DBCE.3000005@isode.com>
User-Agent: Mutt/1.5.7i
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8de5f93cb2b4e3bee75302e9eacc33db
Cc: kitten@ietf.org, Hai Zaar <haizaar@gmail.com>
Subject: GSS-API QoPs and SASL SSF (Re: SASL always returns ssf=56 for
	GSSAPI)
X-BeenThere: kitten@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Common Authentication Technologies - Next Generation
	<kitten.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/kitten>,
	<mailto:kitten-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/kitten>
List-Post: <mailto:kitten@lists.ietf.org>
List-Help: <mailto:kitten-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/kitten>,
	<mailto:kitten-request@lists.ietf.org?subject=subscribe>
Errors-To: kitten-bounces@lists.ietf.org

Cc'ing KITTEN to record my thoughts on this topic, which started out as
a question about the SASL SSF of the SASL "GSSAPI" mechanism (as in "why
is it always 56?").

IMO absolute SSF values are a broken concept, and dangerous too, because
the relative strengths of individual cryptographic algorithms and
constructions vary over time as cryptanalysis develops.

Local SSF assignments based on local policy that does not rely on a
notion of absolute strength would be better.

Local policies alone would be even better.  (Of course, policies can be
distributed, but must be enforced locally.)

The GSS-API has a limited notion of QoPs that at least does not pretend
to be an absolute SSF-like thing.  Which is very good, but it has its
limitations.

On Fri, Sep 22, 2006 at 01:49:18PM +0100, Alexey Melnikov wrote:
> Nicolas Williams wrote:
> 
> >On Thu, Sep 21, 2006 at 06:06:57PM +0100, Alexey Melnikov wrote:
> > 
> >
> >>As far as I know there is no portable way to extract strength of the 
> >>strongest cipher from GSSAPI.
> >>Let me know if I am wrong.
> >>   
> >>
> >You are right.
> > 
> >
> So basically I was trying to use presence of a define for AES cipher as 
> a signal that the underlying GSS-API library supports AES. But I guess 
> it didn't work.
> Which GSS-API are you using?

First, the GSS-API notion of QoPs is mechanism-specific, and lacks
useful symbolic names (it's an integer namespace).

Second, there's no way to know what set of QoPs a mechanism[*] or
credential can negotiate.

Third, there's no way to constrain the set of QoPs that will be used nor
negotiated during security context establishment.

Fourth, there's no way to constrain the set of QoPs that a credential
handle can be used to negotiate during security context establishment.

The second, third and fourth points mean that one can't reject
mechanisms or credentials out of hand prior to negotiating mechanisms.
Thus one can negotiate a mechanism that you'll then decide is no good,
at which point one can typically only abort the connection/whatever (ONC
RPC w/ RPCSEC_GSS is an exception).

Fifth, the Kerberos V mechanism doesn't define any useful QoPs.  I think
it should, since:

    There is, however, a way to query what QoPs are available for an
    established security context: GSS_Wrap_size_limit() takes a QoP as
    input!  So if you know what QoPs are available for a mechanism then
    you can ask one by one which ones are available.

So it does make sense, I see now, to define QoPs for the Kerberos V
mechanism other than the default QoP.  Particularly if the limitations
of the GSS-API w.r.t. QoP negotiation are addressed.

I can see the following sorts of extensions to the GSS-API:

 - a function(s) to inquire QoPs supported by individual mechanisms
 - a function(s) to inquire QoPs supported by individual credentials
 - a function(s) to inquire QoPs supported by individual security contexts
   (iterating GSS_Wrap_size_limit() over known QoPs seems a bit clunky)

 - a function to map {qop_name, [mech_OID]} -> {qop_num,  description}
 - a function to map {qop_num, mech_OID}    -> {qop_name, description}

Finally, I think we need a general purpose (i.e., not specific to the
GSS-API) way to express cryptographic policy whereby: a) administrators
get to write simple, but meaningful policies, b) applications can refer
to these by name (including a default policy name), c) frameworks and
mechanisms can provide necessary details for policy evaluation.  Given
the above extensions then such policies could be applied to {mech_oid,
qop_num}, {mech_OID, qop_num_set/range}, {credential}, {credential,
mech_OID} and {security_context}.

[*]  The Solaris RPCSEC_GSS API does provide a way to list the QoPs
     supported by a GSS-API mechanism: see the
     rpc_gss_get_mech_info(3NSL) manpage.

     This relies on a file, /etc/gss/qop, that lists {qop_name, qop,
     mech_name} values.  But it could instead rely on the mechanisms
     providing the information directly through the SPI.


Nico
-- 

_______________________________________________
Kitten mailing list
Kitten@lists.ietf.org
https://www1.ietf.org/mailman/listinfo/kitten



