From kitten-bounces@lists.ietf.org Sun Jun 04 12:27:32 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FmvRq-0002QU-AD; Sun, 04 Jun 2006 12:27:30 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FeCuT-0005nn-I3
	for kitten@ietf.org; Thu, 11 May 2006 11:17:01 -0400
Received: from 178.230.13.217.in-addr.dgcsystems.net ([217.13.230.178]
	helo=yxa.extundo.com) by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1FeCuT-0006GY-3v
	for kitten@ietf.org; Thu, 11 May 2006 11:17:01 -0400
Received: from localhost.localdomain (yxa.extundo.com [217.13.230.178])
	(authenticated bits=0)
	by yxa.extundo.com (8.13.4/8.13.4/Debian-3sarge1) with ESMTP id
	k4BFGkkK023782
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO)
	for <kitten@ietf.org>; Thu, 11 May 2006 17:16:47 +0200
From: Simon Josefsson <jas@extundo.com>
To: kitten@ietf.org
References: <20060510184652.GZ28647@binky.Central.Sun.COM>
OpenPGP: id=B565716F; url=http://josefsson.org/key.txt
X-Hashcash: 1:22:060511:kitten@ietf.org::pcg9SlVyoFdAj9b/:YA7G
Date: Thu, 11 May 2006 17:16:46 +0200
In-Reply-To: <20060510184652.GZ28647@binky.Central.Sun.COM> (Nicolas
	Williams's message of "Wed, 10 May 2006 13:46:53 -0500")
Message-ID: <8764kcegm9.fsf@latte.josefsson.org>
User-Agent: Gnus/5.110006 (No Gnus v0.6) Emacs/22.0.50 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Spam-Status: No, score=-2.5 required=5.0 tests=AWL,BAYES_00,
	FORGED_RCVD_HELO autolearn=ham version=3.1.0
X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on yxa-iv
X-Virus-Scanned: ClamAV version 0.88.2,
	clamav-milter version 0.88.2 on yxa.extundo.com
X-Virus-Status: Clean
X-Spam-Score: 0.1 (/)
X-Scan-Signature: d0bdc596f8dd1c226c458f0b4df27a88
X-Mailman-Approved-At: Sun, 04 Jun 2006 12:27:28 -0400
Cc: 
Subject: Re: Updated I18N proposal
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

I'm jumping in late, ignoring the first proposal...

Nicolas Williams <Nicolas.Williams@sun.com> writes:

> So I offer, instead, this:
>
>  - In the GSS-APIv3 deprecate (note that deprecate != remove):
>
>     - GSS_Import_name() for any name type other than GSS_C_NT_EXPORTED_NAME
>     - GSS_Display_name()
>     - GSS_Display_status()

Given that running code implement these differently, that seem like a
good idea.

>  - In the GSS-APIv3 add versions of the above functions that specify the
>    use of Unicode in the abstract API, UTF-8 in the C bidnings, etc...
>
>     - GSS_Import_name_unicode() (gss_import_name_utf8() in C bindings)
>     - GSS_Display_name_unicode() (gss_display_name_utf8() in C bindings)
>     - GSS_Display_status_unicode() (gss_display_status_utf8() in C bindings)

Given that Unicode and UTF-8 is the natural choice for i18n of IETF
protocols, this also seem like a good idea to me.

On the names: What about GSS_Import_name2 and gss_import_name2
instead?  Then the naming style between bindings will be more
consistent.

>  - In the GSS-APIv3 add *optional* _utility_ function versions of the
>    above that utilize the CES of the current locale:
>
>     - GSS_Import_name_locale() (gss_import_name_locale())
>     - GSS_Display_name_locale() (gss_display_name_locale())
>     - GSS_Display_status_locale() (gss_display_status_locale())
>
>    Suitable warnings about the limited applicability of these functions
>    and the limited portability of applications that rely on these
>    interfaces will be included in the specs.

Why would those be provided?  I see two distinct reasons:

1) To provide backwards compatibility for applications that assumed
   GSS-API handled data in locale encodings.

2) To provide new APIs to make it easier for application, so
   applications can avoid to convert from locales to UTF-8 internally.

I don't think 1) is a good idea, it seems better to use the original
function names for backwards compatibility.

2) may be a good idea, in LibIDN I provide both UTF-8 and locale APIs
for application that want to do stringprep, and the locale APIs are
often used.

>  - In the GSS-APIv2u2 add a note about implementation history of the
>    Latin-1 requirements of the GSS-APIv2u1, but otherwise change
>    nothing.
>
>    Though we may want to add the above to the GSS-APIv2u2 as well; I see
>    no reason not to.

I agree.

> I believe this should make Jeff Altman happy (no GSS_C_CES_* symbols,
> values, no registry or reuse of existing registries), as well as Martin.
> It will certainly make me happy, and probably Jeff Hutzelman as well.

I'd be happy too.

Thanks,
Simon

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



From kitten-bounces@lists.ietf.org Sun Jun 04 12:27:32 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FmvRq-0002Rr-K0; Sun, 04 Jun 2006 12:27:30 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FeHRD-0000OX-Ed
	for kitten@ietf.org; Thu, 11 May 2006 16:07:07 -0400
Received: from ginger.cmf.nrl.navy.mil ([134.207.10.161])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FeHR8-0003CQ-QS
	for kitten@ietf.org; Thu, 11 May 2006 16:07:07 -0400
Received: from cmf.nrl.navy.mil (elvis.cmf.nrl.navy.mil [134.207.10.38])
	(authenticated bits=0)
	by ginger.cmf.nrl.navy.mil (8.12.11.20060308/8.12.11) with ESMTP id
	k4BK6rsX029750
	for <kitten@ietf.org>; Thu, 11 May 2006 16:06:53 -0400 (EDT)
Message-Id: <200605112006.k4BK6rsX029750@ginger.cmf.nrl.navy.mil>
To: kitten@ietf.org
In-Reply-To: <200605111958.VAA24539@uw1048.wdf.sap.corp> 
X-Face: "Evs"_GpJ]],xS)b$T2#V&{KfP_i2`TlPrY$Iv9+TQ!6+`~+l)#7I)0xr1>4hfd{#0B4
	WIn3jU;bql;{2Uq%zw5bF4?%F&&j8@KaT?#vBGk}u07<+6/`.F-3_GA@6Bq5gN9\+s;_d
	gD\SW #]iN_U0 KUmOR.P<|um5yP<ea#^"SJK; C*}fMI;
	Mv(aiO2z~9n.w?@\>kEpSD@*e`
Date: Thu, 11 May 2006 16:06:53 -0400
From: Ken Hornstein <kenh@cmf.nrl.navy.mil>
X-Spam-Score: () hits=0 User Authenticated
X-Virus-Scanned: NAI Completed
X-Scanned-By: MIMEDefang 2.30 (www . roaringpenguin . com / mimedefang)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 08170828343bcf1325e4a0fb4584481c
X-Mailman-Approved-At: Sun, 04 Jun 2006 12:27:28 -0400
Cc: 
Subject: Re: Updated I18N proposal 
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

>Really, it is much easier if you can check whether some library implements
>a functionality with a simple "nm libxyz.so" or "dumpbin /exports xyz32.dll"
>than having to write code, compile, run and look at the return code in
>order to find out.

I agree that it's easier to check if the symbols aren't present ... but
it makes it a lot harder to write portable code.  You have to clutter
things up with some sort of autoconf-like test and put #ifdefs in your
code.  From a portability standpoint, I'd rather be able to check that
stuff at runtime.  Maybe if there was some preprocessor symbol that the
header file defined if those functions didn't exist, it wouldn't be so
bad ... but that means you can't just upgrade a shared library and have
things automatically work.

--Ken

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

From kitten-bounces@lists.ietf.org Sun Jun 04 12:27:32 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FmvRq-0002Sa-S2; Sun, 04 Jun 2006 12:27:30 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FmvLA-0004oX-AC
	for kitten@ietf.org; Sun, 04 Jun 2006 12:20:36 -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 1FmvL9-0004Oy-2C
	for kitten@ietf.org; Sun, 04 Jun 2006 12:20:36 -0400
Received: from [192.168.1.13] by secure-endpoints.com
	(Cipher TLSv1:RC4-MD5:128) (MDaemon PRO v9.0.1)
	with ESMTP id md50000022457.msg
	for <kitten@ietf.org>; Sun, 04 Jun 2006 12:20:54 -0400
Message-ID: <44830862.7050308@secure-endpoints.com>
Date: Sun, 04 Jun 2006 12:20:50 -0400
From: Jeffrey Altman <jaltman@secure-endpoints.com>
Organization: Secure Endpoints Inc.
User-Agent: Thunderbird 1.5.0.4 (Windows/20060516)
MIME-Version: 1.0
To: Kitten <kitten@ietf.org>
X-Enigmail-Version: 0.94.0.0
X-Authenticated-Sender: jaltman@secure-endpoints.com
X-Spam-Processed: secure-endpoints.com, Sun, 04 Jun 2006 12:20:54 -0400
	(not processed: message from valid local sender)
X-Return-Path: jaltman@secure-endpoints.com
X-MDaemon-Deliver-To: kitten@ietf.org
X-Spam-Score: 0.4 (/)
X-Scan-Signature: c3a18ef96977fc9bcc21a621cbf1174b
X-Mailman-Approved-At: Sun, 04 Jun 2006 12:27:28 -0400
Cc: 
Subject: Meeting Request Deadline Monday
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="===============1993955932=="
Errors-To: kitten-bounces@lists.ietf.org

This is a cryptographically signed message in MIME format.

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

This is a cryptographically signed message in MIME format.

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

Monday is the deadline for submitting meeting requests for IETF 66 in
Montreal.   Are there any other working groups or known BOFs that we
need to avoid?  This is the list from our last meeting:

SASL, KRB-WG, SECMECH, NFSV4, KINK, PKIX, SECSH, ISMS,
BTNS, SAAG, SIEVE, IMAPEXT, HASH

Jeffrey Altman

--------------ms010408020905090404040507
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
AQcBMBwGCSqGSIb3DQEJBTEPFw0wNjA2MDQxNjIwNTBaMCMGCSqGSIb3DQEJBDEWBBRlyjIO
m9rQtmzkOwUuZw9kc9xFUDBSBgkqhkiG9w0BCQ8xRTBDMAoGCCqGSIb3DQMHMA4GCCqGSIb3
DQMCAgIAgDANBggqhkiG9w0DAgIBQDAHBgUrDgMCBzANBggqhkiG9w0DAgIBKDCBhQYJKwYB
BAGCNxAEMXgwdjBiMQswCQYDVQQGEwJaQTElMCMGA1UEChMcVGhhd3RlIENvbnN1bHRpbmcg
KFB0eSkgTHRkLjEsMCoGA1UEAxMjVGhhd3RlIFBlcnNvbmFsIEZyZWVtYWlsIElzc3Vpbmcg
Q0ECEBW00lKwoWJXt8wbmTl1M0kwgYcGCyqGSIb3DQEJEAILMXigdjBiMQswCQYDVQQGEwJa
QTElMCMGA1UEChMcVGhhd3RlIENvbnN1bHRpbmcgKFB0eSkgTHRkLjEsMCoGA1UEAxMjVGhh
d3RlIFBlcnNvbmFsIEZyZWVtYWlsIElzc3VpbmcgQ0ECEBW00lKwoWJXt8wbmTl1M0kwDQYJ
KoZIhvcNAQEBBQAEggEAceBLg5doKBFhGno7qVDmCsCQPxvQkb0YtA54WhqqhVPML8Lj25d7
VDyyleSfR7vpLdulHZau8yJBUEvkBCHhpl+PPyLfbPJiuRIWNn3AWrg6HqE9qOQNONFmJcps
iFDLh/kFOHLIxnsPB0leHPm16+wZEhmqdjFG3XQ+8xYRtC1SfnSEvRDK14LLf31XdVBMHA19
6BKQjsk63AzvpO7opFyNrnZpn3d16ElUtK7Q9GTc6yAj5D6FSM2BsphN3/HUmfbCy7axjGPN
YgsdyZ62aYBOu45Dv5G/62BqU8UDUCEWOuqF3u7GRuKfCmriWx7s4fE/n7Cj3J1TILHy1It+
awAAAAAAAA==
--------------ms010408020905090404040507--



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

--===============1993955932==--







From kitten-bounces@lists.ietf.org Sun Jun 04 12:27:32 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FmvRq-0002R1-Ej; Sun, 04 Jun 2006 12:27:30 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FeD3O-0000kC-K6
	for kitten@ietf.org; Thu, 11 May 2006 11:26:14 -0400
Received: from 178.230.13.217.in-addr.dgcsystems.net ([217.13.230.178]
	helo=yxa.extundo.com) by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1FeD3N-0006jx-5c
	for kitten@ietf.org; Thu, 11 May 2006 11:26:14 -0400
Received: from localhost.localdomain (yxa.extundo.com [217.13.230.178])
	(authenticated bits=0)
	by yxa.extundo.com (8.13.4/8.13.4/Debian-3sarge1) with ESMTP id
	k4BFQ31n024961
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO)
	for <kitten@ietf.org>; Thu, 11 May 2006 17:26:04 +0200
From: Simon Josefsson <jas@extundo.com>
To: kitten@ietf.org
References: <20060508203042.GF27799@binky.Central.Sun.COM>
OpenPGP: id=B565716F; url=http://josefsson.org/key.txt
X-Hashcash: 1:22:060511:kitten@ietf.org::+KEYZhMDExrt0Xz0:3l4B
Date: Thu, 11 May 2006 17:26:03 +0200
In-Reply-To: <20060508203042.GF27799@binky.Central.Sun.COM> (Nicolas
	Williams's message of "Mon, 8 May 2006 15:30:42 -0500")
Message-ID: <87y7x8d1mc.fsf@latte.josefsson.org>
User-Agent: Gnus/5.110006 (No Gnus v0.6) Emacs/22.0.50 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Spam-Status: No, score=-2.5 required=5.0 tests=AWL,BAYES_00,
	FORGED_RCVD_HELO autolearn=ham version=3.1.0
X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on yxa-iv
X-Virus-Scanned: ClamAV version 0.88.2,
	clamav-milter version 0.88.2 on yxa.extundo.com
X-Virus-Status: Clean
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d
X-Mailman-Approved-At: Sun, 04 Jun 2006 12:27:28 -0400
Cc: 
Subject: Re: I18N & L10N proposal for GSS-API (v2u2/v3)
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 <Nicolas.Williams@sun.com> writes:

> 6) L10N
>
>    We might as well tackle L10N and give GSS_Display_status() an input
>    parameter indicating an RFC3066 language tag or tags to be used for
>    localization of error messages.

Isn't it better to use standard locale/gettext behaviour for l10n?

My GSS implementation support non-English error messages, and they are
returned whenever the calling application is running in a locale that
the errors are translated to.  This is how I'd expect things to work:
a function that is intended to return human readable strings should
return them in the user's language.

There is a problem if the application is a server that sends
GSS_Display_Name output over the network to a client (presumable to be
displayed to the user), but this is typically handled by having the
server set itself up to invoke GSS_Display_Name in the C locale.  Of
course, if the protocol is l18n-capable, the server would know which
proper locale to use instead.

I wouldn't be opposed to a GSS_Display_status2 that took a RFC 3066
language tag explicitly, for non-POSIX platforms, because that would
be easy to implement for me.

Thanks,
Simon

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



From kitten-bounces@lists.ietf.org Mon Jun 05 00:46:37 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fn6yx-0003VX-LH; Mon, 05 Jun 2006 00:46:27 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Fn6yw-0003UK-F0
	for kitten@ietf.org; Mon, 05 Jun 2006 00:46:26 -0400
Received: from brmea-mail-1.sun.com ([192.18.98.31])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fn6yv-0008Qq-2C
	for kitten@ietf.org; Mon, 05 Jun 2006 00:46:26 -0400
Received: from centralmail3brm.Central.Sun.COM ([129.147.62.199])
	by brmea-mail-1.sun.com (8.13.6+Sun/8.12.9) with ESMTP id
	k554kOOE016886
	for <kitten@ietf.org>; Sun, 4 Jun 2006 22:46:24 -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 k554j3k5000854
	for <kitten@ietf.org>; Sun, 4 Jun 2006 22:45:04 -0600 (MDT)
Received: from binky.Central.Sun.COM (localhost [127.0.0.1])
	by binky.Central.Sun.COM (8.13.3+Sun/8.13.3) with ESMTP id
	k554kNMx002426; Sun, 4 Jun 2006 23:46:23 -0500 (CDT)
Received: (from nw141292@localhost)
	by binky.Central.Sun.COM (8.13.3+Sun/8.13.3/Submit) id k554kMbo002425; 
	Sun, 4 Jun 2006 23:46:22 -0500 (CDT)
Date: Sun, 4 Jun 2006 23:46:22 -0500
From: Nicolas Williams <Nicolas.Williams@sun.com>
To: Jeffrey Altman <jaltman@secure-endpoints.com>
Message-ID: <20060605044622.GD28402@binky.Central.Sun.COM>
Mail-Followup-To: Jeffrey Altman <jaltman@secure-endpoints.com>,
	Kitten <kitten@ietf.org>
References: <44830862.7050308@secure-endpoints.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <44830862.7050308@secure-endpoints.com>
User-Agent: Mutt/1.5.11
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad
Cc: Kitten <kitten@ietf.org>
Subject: Re: Meeting Request Deadline Monday
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 Sun, Jun 04, 2006 at 12:20:50PM -0400, Jeffrey Altman wrote:
> Monday is the deadline for submitting meeting requests for IETF 66 in
> Montreal.   Are there any other working groups or known BOFs that we
> need to avoid?  This is the list from our last meeting:
> 
> SASL, KRB-WG, SECMECH, NFSV4, KINK, PKIX, SECSH, ISMS,
> BTNS, SAAG, SIEVE, IMAPEXT, HASH

KINK is done...  I only want to avoid the various BoFs like DIX and
WARP as well as BTNS and SAAG.

That's it.


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



From kitten-bounces@lists.ietf.org Mon Jun 05 00:54:25 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fn76c-0000qH-DA; Mon, 05 Jun 2006 00:54:22 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Fn76b-0000qC-4P
	for kitten@ietf.org; Mon, 05 Jun 2006 00:54:21 -0400
Received: from brmea-mail-4.sun.com ([192.18.98.36])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fn76Z-0000SR-9t
	for kitten@ietf.org; Mon, 05 Jun 2006 00:54:21 -0400
Received: from centralmail3brm.Central.Sun.COM ([129.147.62.199])
	by brmea-mail-4.sun.com (8.13.6+Sun/8.12.9) with ESMTP id
	k554sIrc004281
	for <kitten@ietf.org>; Sun, 4 Jun 2006 22:54:18 -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 k554qwIp002184
	for <kitten@ietf.org>; Sun, 4 Jun 2006 22:52:58 -0600 (MDT)
Received: from binky.Central.Sun.COM (localhost [127.0.0.1])
	by binky.Central.Sun.COM (8.13.3+Sun/8.13.3) with ESMTP id
	k554sH8e002433; Sun, 4 Jun 2006 23:54:17 -0500 (CDT)
Received: (from nw141292@localhost)
	by binky.Central.Sun.COM (8.13.3+Sun/8.13.3/Submit) id k554sHlj002432; 
	Sun, 4 Jun 2006 23:54:17 -0500 (CDT)
Date: Sun, 4 Jun 2006 23:54:17 -0500
From: Nicolas Williams <Nicolas.Williams@sun.com>
To: Simon Josefsson <jas@extundo.com>
Message-ID: <20060605045417.GE28402@binky.Central.Sun.COM>
Mail-Followup-To: Simon Josefsson <jas@extundo.com>, kitten@ietf.org
References: <20060510184652.GZ28647@binky.Central.Sun.COM>
	<8764kcegm9.fsf@latte.josefsson.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <8764kcegm9.fsf@latte.josefsson.org>
User-Agent: Mutt/1.5.11
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0ddefe323dd869ab027dbfff7eff0465
Cc: kitten@ietf.org
Subject: Re: Updated I18N proposal
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 Thu, May 11, 2006 at 05:16:46PM +0200, Simon Josefsson wrote:
> Nicolas Williams <Nicolas.Williams@sun.com> writes:
> >     - GSS_Import_name_unicode() (gss_import_name_utf8() in C bindings)
> >     - GSS_Display_name_unicode() (gss_display_name_utf8() in C bindings)
> >     - GSS_Display_status_unicode() (gss_display_status_utf8() in C bindings)
> 
> Given that Unicode and UTF-8 is the natural choice for i18n of IETF
> protocols, this also seem like a good idea to me.
> 
> On the names: What about GSS_Import_name2 and gss_import_name2
> instead?  Then the naming style between bindings will be more
> consistent.

We decided at some point that only the C bindings will get these.

> >  - In the GSS-APIv3 add *optional* _utility_ function versions of the
> >    above that utilize the CES of the current locale:
> >
> >     - GSS_Import_name_locale() (gss_import_name_locale())
> >     - GSS_Display_name_locale() (gss_display_name_locale())
> >     - GSS_Display_status_locale() (gss_display_status_locale())
> >
> >    Suitable warnings about the limited applicability of these functions
> >    and the limited portability of applications that rely on these
> >    interfaces will be included in the specs.
> 
> Why would those be provided?  I see two distinct reasons:
> 
> 1) To provide backwards compatibility for applications that assumed
>    GSS-API handled data in locale encodings.
> 
> 2) To provide new APIs to make it easier for application, so
>    applications can avoid to convert from locales to UTF-8 internally.

(2).

Basically, some of us would end up writing utility functions that amount
to having these *_locale() functions around.

> I don't think 1) is a good idea, it seems better to use the original
> function names for backwards compatibility.
> 
> 2) may be a good idea, in LibIDN I provide both UTF-8 and locale APIs
> for application that want to do stringprep, and the locale APIs are
> often used.

(2) is a good idea because it reduces code duplication.

Nico
-- 

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



From kitten-bounces@lists.ietf.org Sat Jun 17 20:43:51 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FrlOE-0001C1-V4; Sat, 17 Jun 2006 20:43:46 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FrlOE-0001BS-5D
	for kitten@ietf.org; Sat, 17 Jun 2006 20:43:46 -0400
Received: from au.padl.com ([203.13.32.1])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FrlOC-0003oh-E0
	for kitten@ietf.org; Sat, 17 Jun 2006 20:43:46 -0400
Received: from au.padl.com (localhost.padl.com [127.0.0.1])
	by au.padl.com (8.12.11/8.12.11) with ESMTP id k5I0hWlU075741
	for <kitten@ietf.org>; Sun, 18 Jun 2006 10:43:32 +1000 (EST)
	(envelope-from lukeh@au.padl.com)
Received: (from lukeh@localhost)
	by au.padl.com (8.12.11/8.12.11/Submit) id k5I0hVLM075739;
	Sun, 18 Jun 2006 10:43:31 +1000 (EST) (envelope-from lukeh)
From: Luke Howard <lukeh@padl.com>
Message-Id: <200606180043.k5I0hVLM075739@au.padl.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Organization: PADL Software Pty Ltd
To: kitten@ietf.org
Date: Sun, 18 Jun 2006 10:43:31 +1000
Versions: dmail (bsd44) 2.6d/makemail 2.10
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.63
X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on au.padl.com
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d17f825e43c9aed4fd65b7edddddec89
Cc: 
Subject: SIP and GSS
X-BeenThere: kitten@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: lukeh@padl.com
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


Has anyone thought about a profile for doing GSS authentication in
SIP?

Presumably it could use a similar method to existing approaches
for HTTP authentication (although integrity protecting the header
is probably important, too).

-- Luke

--

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



From kitten-bounces@lists.ietf.org Sat Jun 17 23:36:03 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fro4t-0000RG-0r; Sat, 17 Jun 2006 23:35:59 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Fro4p-0000Pa-Ph
	for kitten@ietf.org; Sat, 17 Jun 2006 23:35:55 -0400
Received: from li4-142.members.linode.com ([66.220.1.142])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Frnuj-0004Dl-2K
	for kitten@ietf.org; Sat, 17 Jun 2006 23:25:30 -0400
Received: from quark.foo.net (c-69-142-196-170.hsd1.nj.comcast.net
	[69.142.196.170])
	(using TLSv1 with cipher EDH-RSA-DES-CBC3-SHA (168/168 bits))
	(No client certificate requested)
	by li4-142.members.linode.com (Postfix) with ESMTP
	id A29E642B80; Sat, 17 Jun 2006 23:25:27 -0400 (EDT)
Date: Sat, 17 Jun 2006 23:25:07 -0400
From: Michael B Allen <mba2000@ioplex.com>
To: lukeh@padl.com
Message-Id: <20060617232507.3add6287.mba2000@ioplex.com>
In-Reply-To: <200606180043.k5I0hVLM075739@au.padl.com>
References: <200606180043.k5I0hVLM075739@au.padl.com>
X-Mailer: Sylpheed version 1.0.6 (GTK+ 1.2.10; i386-redhat-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.6 (/)
X-Scan-Signature: 93238566e09e6e262849b4f805833007
Cc: kitten@ietf.org
Subject: Re: SIP and GSS
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 Sun, 18 Jun 2006 10:43:31 +1000
Luke Howard <lukeh@padl.com> wrote:

> 
> Has anyone thought about a profile for doing GSS authentication in
> SIP?
> 
> Presumably it could use a similar method to existing approaches
> for HTTP authentication (although integrity protecting the header
> is probably important, too).

I don't know anything about SIP but I think it's worth pointing out that
I think there is a potential issue with trying to perform multi-step
authentication over stateless protocols like HTTP. Or at least there
is if you're pipelining requests. For this reason, I would recommend
considering having a multiplex id somewhere (e.g. a separate header with
a numeric value).

Mike

-- 
Michael B Allen
PHP Extension for SSO w/ Windows Group Authorization
http://www.ioplex.com/

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



From kitten-bounces@lists.ietf.org Sat Jun 17 23:37:15 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fro67-0001CL-9N; Sat, 17 Jun 2006 23:37:15 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Fro65-0001CG-SM
	for kitten@ietf.org; Sat, 17 Jun 2006 23:37:13 -0400
Received: from au.padl.com ([203.13.32.1])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fro62-0005IK-37
	for kitten@ietf.org; Sat, 17 Jun 2006 23:37:13 -0400
Received: from au.padl.com (localhost.padl.com [127.0.0.1])
	by au.padl.com (8.12.11/8.12.11) with ESMTP id k5I3auAv083917;
	Sun, 18 Jun 2006 13:36:56 +1000 (EST)
	(envelope-from lukeh@au.padl.com)
Received: (from lukeh@localhost)
	by au.padl.com (8.12.11/8.12.11/Submit) id k5I3audJ083916;
	Sun, 18 Jun 2006 13:36:56 +1000 (EST) (envelope-from lukeh)
From: Luke Howard <lukeh@padl.com>
Message-Id: <200606180336.k5I3audJ083916@au.padl.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Organization: PADL Software Pty Ltd
To: mba2000@ioplex.com
References: <200606180043.k5I0hVLM075739@au.padl.com>
	<20060617232507.3add6287.mba2000@ioplex.com>
Date: Sun, 18 Jun 2006 13:36:55 +1000
Versions: dmail (bsd44) 2.6d/makemail 2.10
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.63
X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on au.padl.com
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a
Cc: kitten@ietf.org
Subject: Re: SIP and GSS
X-BeenThere: kitten@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: lukeh@padl.com
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


>I don't know anything about SIP but I think it's worth pointing out that
>I think there is a potential issue with trying to perform multi-step
>authentication over stateless protocols like HTTP. Or at least there
>is if you're pipelining requests. For this reason, I would recommend
>considering having a multiplex id somewhere (e.g. a separate header with
>a numeric value).

I'm not terribly familiar with the protocol either but I think you
could use the Call-ID for this. From RFC 3261:

   Call-ID contains a globally unique identifier for this call,
   generated by the combination of a random string and the softphone's
   host name or IP address.  The combination of the To tag, From tag,
   and Call-ID completely defines a peer-to-peer SIP relationship
   between Alice and Bob and is referred to as a dialog.

It appears that MS supports Kerberos authentication in SIP, see:

   http://www.mcse.ms/archive246-2006-1-2073250.html

The header is different to draft-jaganathan-kerberos-http-01.txt,
though -- it's unclear whether Negotiate would work.

-- Luke

--

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



From kitten-bounces@lists.ietf.org Mon Jun 19 14:17:48 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FsOJn-0006Qw-Pi; Mon, 19 Jun 2006 14:17:47 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FsOJm-0006QP-U0
	for kitten@ietf.org; Mon, 19 Jun 2006 14:17:46 -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 1FsOJl-0006sH-Oq
	for kitten@ietf.org; Mon, 19 Jun 2006 14:17:46 -0400
Received: by carter-zimmerman.mit.edu (Postfix, from userid 8042)
	id 4B54AE007A; Mon, 19 Jun 2006 14:17:42 -0400 (EDT)
From: Sam Hartman <hartmans-ietf@mit.edu>
To: lukeh@padl.com
References: <200606180043.k5I0hVLM075739@au.padl.com>
	<20060617232507.3add6287.mba2000@ioplex.com>
	<200606180336.k5I3audJ083916@au.padl.com>
Date: Mon, 19 Jun 2006 14:17:42 -0400
In-Reply-To: <200606180336.k5I3audJ083916@au.padl.com> (Luke Howard's message
	of "Sun, 18 Jun 2006 13:36:55 +1000")
Message-ID: <tslwtbdqabd.fsf@cz.mit.edu>
User-Agent: Gnus/5.110004 (No Gnus v0.4) 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: kitten@ietf.org
Subject: Re: SIP and GSS
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

I was hoping to do something like http negotiate authentication for
sip after we get something reasonable with channel bindings for http


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



From kitten-bounces@lists.ietf.org Mon Jun 19 16:46:43 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FsQdv-0008HD-Om; Mon, 19 Jun 2006 16:46:43 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FsQdo-0007gz-VB
	for kitten@ietf.org; Mon, 19 Jun 2006 16:46:36 -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 1FsQdk-0006Aj-Nf
	for kitten@ietf.org; Mon, 19 Jun 2006 16:46:36 -0400
Received: by carter-zimmerman.mit.edu (Postfix, from userid 8042)
	id 4CF88E0079; Mon, 19 Jun 2006 16:46:28 -0400 (EDT)
From: Sam Hartman <hartmans-ietf@mit.edu>
To: martin.rex@sap.com
References: <200606192040.WAA17036@uw1048.wdf.sap.corp>
Date: Mon, 19 Jun 2006 16:46:28 -0400
In-Reply-To: <200606192040.WAA17036@uw1048.wdf.sap.corp> (Martin Rex's message
	of "Mon, 19 Jun 2006 22:40:47 +0200 (MET DST)")
Message-ID: <tsl64iwrhzv.fsf@cz.mit.edu>
User-Agent: Gnus/5.110004 (No Gnus v0.4) Emacs/21.4 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7bac9cb154eb5790ae3b2913587a40de
Cc: kitten@ietf.org
Subject: Re: SIP and GSS
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

>>>>> "Martin" == Martin Rex <martin.rex@sap.com> writes:

    Martin> But you do realize that http negotiate requires HTTP/1.1
    Martin> Connection:keep-alive and does not provide data integrity,
    Martin> so the use of SSL/HTTPS to protect the communication
    Martin> channel is strongly advised.

Yes.  I do hope to fix the keep alive requirement and to look at
channel bindings for integrity.


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



From kitten-bounces@lists.ietf.org Mon Jun 19 17:05:15 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FsQvq-0007DJ-6u; Mon, 19 Jun 2006 17:05:14 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FsQvp-0007CF-5E
	for kitten@ietf.org; Mon, 19 Jun 2006 17:05:13 -0400
Received: from smtpde03.sap-ag.de ([155.56.68.140])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FsQvn-0000Z0-GR
	for kitten@ietf.org; Mon, 19 Jun 2006 17:05:13 -0400
Received: from sap-ag.de (smtpde03)
	by smtpde03.sap-ag.de (out) with ESMTP id XAA04206;
	Mon, 19 Jun 2006 23:04:53 +0200 (MESZ)
From: Martin Rex <martin.rex@sap.com>
Message-Id: <200606192104.XAA17720@uw1048.wdf.sap.corp>
To: hartmans-ietf@mit.edu (Sam Hartman)
Date: Mon, 19 Jun 2006 23:04:52 +0200 (MET DST)
In-Reply-To: <tsl64iwrhzv.fsf@cz.mit.edu> from "Sam Hartman" at Jun 19,
	6 04:46:28 pm
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-SAP: out
X-SAP: out
X-SAP: out
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a7d6aff76b15f3f56fcb94490e1052e4
Cc: kitten@ietf.org
Subject: Re: SIP and GSS
X-BeenThere: kitten@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: martin.rex@sap.com
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

Sam Hartman wrote:
> 
> >>>>> "Martin" == Martin Rex <martin.rex@sap.com> writes:
> 
>     Martin> But you do realize that http negotiate requires HTTP/1.1
>     Martin> Connection:keep-alive and does not provide data integrity,
>     Martin> so the use of SSL/HTTPS to protect the communication
>     Martin> channel is strongly advised.
> 
> Yes.  I do hope to fix the keep alive requirement and to look at
> channel bindings for integrity.

Microsoft NTLM and negotiate authentication impose TCP-session semantics
on the HTTP protocol carried within.  Every new TCP-session will be
forced through a new handshake with 401 Unauthorized replies until
the handshake completes, and every follup HTTP-Request does not
carry any HTTP headers refering to the initial authentication.

The authentication scheme is based on Microsoft's impersonation model,
where the server thread is expected to impersonate the client in order
to perform all the authorization decisions when processing the request
at the OS level.  The thread is supposed to work exclusively for
all of the pipelined HTTP/1.1 Connection: keep-alive requests.

The I-D proposal (which originally expired in 2002 and was reissued
in 2004 under a different name, but it has also expired), does account
for client-side proxies (client-aware proxies), but is totally ignorant
about server-side proxies (which are usually invisible to the client).

If you add code at the application layer to issue some kind of
session-credential (secure session id) in the reply to the browser
which the browser can and will resend with every new request,
then this would be a possibility to limit the negotiate authentication
requirement for HTTP/1.1 connection keep-alive to the initial handshake
-- which, in case of negotiate/Kerberos, makes it sort-of stateless again.
It requires just one round-trip for authentication and carries the initial
token (AP_REQ) together with the entirely unprotected HTTP request and
the final token (AP_REP) together with the equally unprotected HTTP
response in case the authentication succeeded.


-Martin 

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



From kitten-bounces@lists.ietf.org Mon Jun 19 17:07:23 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FsQxu-00047E-QX; Mon, 19 Jun 2006 17:07:22 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FsQxt-0003vG-A6
	for kitten@ietf.org; Mon, 19 Jun 2006 17:07:21 -0400
Received: from nwkea-mail-2.sun.com ([192.18.42.14])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FsQxs-0000pJ-S5
	for kitten@ietf.org; Mon, 19 Jun 2006 17:07:21 -0400
Received: from centralmail4brm.central.Sun.COM ([129.147.62.198])
	by nwkea-mail-2.sun.com (8.13.6+Sun/8.12.9) with ESMTP id
	k5JL7KQN004065
	for <kitten@ietf.org>; Mon, 19 Jun 2006 14:07:20 -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 k5JL7JlV027426
	for <kitten@ietf.org>; Mon, 19 Jun 2006 15:07:19 -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
	k5JL7JJG017634; Mon, 19 Jun 2006 16:07:19 -0500 (CDT)
Received: (from nw141292@localhost)
	by binky.Central.Sun.COM (8.13.6+Sun/8.13.6/Submit) id k5JL7JlZ017633; 
	Mon, 19 Jun 2006 16:07:19 -0500 (CDT)
Date: Mon, 19 Jun 2006 16:07:19 -0500
From: Nicolas Williams <Nicolas.Williams@sun.com>
To: Martin Rex <martin.rex@sap.com>
Message-ID: <20060619210719.GU5688@binky.Central.Sun.COM>
Mail-Followup-To: Martin Rex <martin.rex@sap.com>,
	Sam Hartman <hartmans-ietf@mit.edu>, kitten@ietf.org
References: <tsl64iwrhzv.fsf@cz.mit.edu>
	<200606192104.XAA17720@uw1048.wdf.sap.corp>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200606192104.XAA17720@uw1048.wdf.sap.corp>
User-Agent: Mutt/1.5.11
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7aefe408d50e9c7c47615841cb314bed
Cc: kitten@ietf.org, Sam Hartman <hartmans-ietf@mit.edu>
Subject: Re: SIP and GSS
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 Mon, Jun 19, 2006 at 11:04:52PM +0200, Martin Rex wrote:
> The I-D proposal (which originally expired in 2002 and was reissued
> in 2004 under a different name, but it has also expired), does account
> for client-side proxies (client-aware proxies), but is totally ignorant
> about server-side proxies (which are usually invisible to the client).

There's a new I-D coming that deals with both!

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



From kitten-bounces@lists.ietf.org Mon Jun 19 17:07:51 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FsQyN-0006Ef-Dt; Mon, 19 Jun 2006 17:07:51 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FsQyN-0006EG-3F
	for kitten@ietf.org; Mon, 19 Jun 2006 17:07:51 -0400
Received: from smtp3.su.se ([130.237.93.228])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FsQyK-0000qe-Q5
	for kitten@ietf.org; Mon, 19 Jun 2006 17:07:51 -0400
Received: from localhost (localhost [127.0.0.1])
	by smtp3.su.se (Postfix) with ESMTP id E842C3BF85;
	Mon, 19 Jun 2006 23:07:47 +0200 (CEST)
Received: from smtp3.su.se ([127.0.0.1])
	by localhost (smtp3.su.se [127.0.0.1]) (amavisd-new,
	port 10024) with LMTP
	id 12569-01-11; Mon, 19 Jun 2006 23:07:47 +0200 (CEST)
Received: from [10.0.0.242] (1-1-2-20a.rny.sth.bostream.se [82.182.132.64])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by smtp3.su.se (Postfix) with ESMTP id 85F493BF24;
	Mon, 19 Jun 2006 23:07:47 +0200 (CEST)
Message-ID: <44971220.1070602@it.su.se>
Date: Mon, 19 Jun 2006 23:07:44 +0200
From: Leif Johansson <leifj@it.su.se>
User-Agent: Thunderbird 1.5.0.2 (X11/20060420)
MIME-Version: 1.0
To: Sam Hartman <hartmans-ietf@mit.edu>
References: <200606192040.WAA17036@uw1048.wdf.sap.corp>
	<tsl64iwrhzv.fsf@cz.mit.edu>
In-Reply-To: <tsl64iwrhzv.fsf@cz.mit.edu>
X-Enigmail-Version: 0.94.0.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by amavisd-new at smtp.su.se
X-Spam-Status: No, hits=-1.586 tagged_above=-99 required=7 tests=[AWL=0.079,
	BAYES_00=-1.665]
X-Spam-Level: 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32
Cc: kitten@ietf.org
Subject: Re: SIP and GSS
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

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Sam Hartman wrote:
>>>>>> "Martin" == Martin Rex <martin.rex@sap.com> writes:
> 
>     Martin> But you do realize that http negotiate requires HTTP/1.1
>     Martin> Connection:keep-alive and does not provide data integrity,
>     Martin> so the use of SSL/HTTPS to protect the communication
>     Martin> channel is strongly advised.
> 
> Yes.  I do hope to fix the keep alive requirement and to look at
> channel bindings for integrity.

The draft(s) Sam so cryptically is referring to are under way.

	Cheers Leif
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFElxIg8Jx8FtbMZncRArK2AJ42pO4h/Xbh/EZ8Z7HtrSxpfVNrbwCeNsjF
o9x3ydjgh3Q83EzMIbKhshg=
=Yzza
-----END PGP SIGNATURE-----

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



From kitten-bounces@lists.ietf.org Mon Jun 19 17:19:16 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FsR9Q-0006vu-87; Mon, 19 Jun 2006 17:19:16 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FsR9O-0006vj-QH
	for kitten@ietf.org; Mon, 19 Jun 2006 17:19:14 -0400
Received: from smtpde02.sap-ag.de ([155.56.68.170])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FsR9N-0001EQ-Eb
	for kitten@ietf.org; Mon, 19 Jun 2006 17:19:14 -0400
Received: from sap-ag.de (smtpde02)
	by smtpde02.sap-ag.de (out) with ESMTP id XAA20763;
	Mon, 19 Jun 2006 23:19:06 +0200 (MESZ)
From: Martin Rex <martin.rex@sap.com>
Message-Id: <200606192119.XAA18160@uw1048.wdf.sap.corp>
To: leifj@it.su.se (Leif Johansson)
Date: Mon, 19 Jun 2006 23:19:05 +0200 (MET DST)
In-Reply-To: <44971220.1070602@it.su.se> from "Leif Johansson" at Jun 19,
	6 11:07:44 pm
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-SAP: out
X-SAP: out
X-SAP: out
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
Cc: kitten@ietf.org, hartmans-ietf@mit.edu
Subject: Re: SIP and GSS
X-BeenThere: kitten@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: martin.rex@sap.com
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

Leif Johansson wrote:
> 
> >>>>>> "Martin" == Martin Rex <martin.rex@sap.com> writes:
> > 
> >     Martin> But you do realize that http negotiate requires HTTP/1.1
> >     Martin> Connection:keep-alive and does not provide data integrity,
> >     Martin> so the use of SSL/HTTPS to protect the communication
> >     Martin> channel is strongly advised.
> > 
> > Yes.  I do hope to fix the keep alive requirement and to look at
> > channel bindings for integrity.
> 
> The draft(s) Sam so cryptically is referring to are under way.

Well, the original drafts were informational and supposed to describe
the behaviour of an incredibly large installed base of Web clients
and Web servers.  While there is nothing wrong to come up with a
better proposal, we will likely have to live with many the originally
documented installations for quite some time.

-Martin



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



From kitten-bounces@lists.ietf.org Mon Jun 19 17:23:07 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FsRD8-0007gf-1P; Mon, 19 Jun 2006 17:23:06 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FsRD6-0007ga-Pt
	for kitten@ietf.org; Mon, 19 Jun 2006 17:23:04 -0400
Received: from nwkea-mail-4.sun.com ([192.18.42.26])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FsRD5-0001Kt-Ba
	for kitten@ietf.org; Mon, 19 Jun 2006 17:23:04 -0400
Received: from centralmail4brm.central.Sun.COM ([129.147.62.198])
	by nwkea-mail-4.sun.com (8.13.6+Sun/8.12.9) with ESMTP id
	k5JLN2F7018698
	for <kitten@ietf.org>; Mon, 19 Jun 2006 14:23:02 -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 k5JLN20E005056
	for <kitten@ietf.org>; Mon, 19 Jun 2006 15:23:02 -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
	k5JLN10k017653; Mon, 19 Jun 2006 16:23:02 -0500 (CDT)
Received: (from nw141292@localhost)
	by binky.Central.Sun.COM (8.13.6+Sun/8.13.6/Submit) id k5JLN1Yi017652; 
	Mon, 19 Jun 2006 16:23:01 -0500 (CDT)
Date: Mon, 19 Jun 2006 16:23:01 -0500
From: Nicolas Williams <Nicolas.Williams@sun.com>
To: Martin Rex <martin.rex@sap.com>
Message-ID: <20060619212301.GV5688@binky.Central.Sun.COM>
Mail-Followup-To: Martin Rex <martin.rex@sap.com>,
	Leif Johansson <leifj@it.su.se>, kitten@ietf.org,
	hartmans-ietf@mit.edu
References: <44971220.1070602@it.su.se>
	<200606192119.XAA18160@uw1048.wdf.sap.corp>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200606192119.XAA18160@uw1048.wdf.sap.corp>
User-Agent: Mutt/1.5.11
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad
Cc: kitten@ietf.org, hartmans-ietf@mit.edu
Subject: Re: SIP and GSS
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 Mon, Jun 19, 2006 at 11:19:05PM +0200, Martin Rex wrote:
> Leif Johansson wrote:
> > The draft(s) Sam so cryptically is referring to are under way.
> 
> Well, the original drafts were informational and supposed to describe
> the behaviour of an incredibly large installed base of Web clients
> and Web servers.  While there is nothing wrong to come up with a
> better proposal, we will likely have to live with many the originally
> documented installations for quite some time.

This is true of anything we do in this space.  We can't let that
paralyze us.  As Sam says, the browser must change, and then not only
the browser.

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



From kitten-bounces@lists.ietf.org Mon Jun 19 17:52:27 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FsRfW-0006Yp-6u; Mon, 19 Jun 2006 17:52:26 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FsRfV-0006Yb-1m
	for kitten@ietf.org; Mon, 19 Jun 2006 17:52:25 -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 1FsR14-0000vf-2t
	for kitten@ietf.org; Mon, 19 Jun 2006 17:10:38 -0400
Received: from smtpde02.sap-ag.de ([155.56.68.170])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1FsQYe-0008IA-Ur
	for kitten@ietf.org; Mon, 19 Jun 2006 16:41:18 -0400
Received: from sap-ag.de (smtpde02)
	by smtpde02.sap-ag.de (out) with ESMTP id WAA00299;
	Mon, 19 Jun 2006 22:40:48 +0200 (MESZ)
From: Martin Rex <martin.rex@sap.com>
Message-Id: <200606192040.WAA17036@uw1048.wdf.sap.corp>
To: hartmans-ietf@mit.edu (Sam Hartman)
Date: Mon, 19 Jun 2006 22:40:47 +0200 (MET DST)
In-Reply-To: <tslwtbdqabd.fsf@cz.mit.edu> from "Sam Hartman" at Jun 19,
	6 02:17:42 pm
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-SAP: out
X-SAP: out
X-SAP: out
X-Spam-Score: -1.0 (-)
X-Scan-Signature: d17f825e43c9aed4fd65b7edddddec89
Cc: kitten@ietf.org
Subject: Re: SIP and GSS
X-BeenThere: kitten@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: martin.rex@sap.com
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

Sam Hartman wrote:
> 
> I was hoping to do something like http negotiate authentication for
> sip after we get something reasonable with channel bindings for http

But you do realize that http negotiate requires
HTTP/1.1 Connection:keep-alive and does not provide data integrity,
so the use of SSL/HTTPS to protect the communication channel is
strongly advised.

-Martin

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



From kitten-bounces@lists.ietf.org Mon Jun 19 18:27:39 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FsSDZ-0002yj-Oe; Mon, 19 Jun 2006 18:27:37 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FsSDY-0002ye-JX
	for kitten@ietf.org; Mon, 19 Jun 2006 18:27:36 -0400
Received: from au.padl.com ([203.13.32.1])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FsSDW-00004q-Tk
	for kitten@ietf.org; Mon, 19 Jun 2006 18:27:36 -0400
Received: from au.padl.com (localhost.padl.com [127.0.0.1])
	by au.padl.com (8.12.11/8.12.11) with ESMTP id k5JMRLeS027361
	for <kitten@ietf.org>; Tue, 20 Jun 2006 08:27:21 +1000 (EST)
	(envelope-from lukeh@au.padl.com)
Received: (from lukeh@localhost)
	by au.padl.com (8.12.11/8.12.11/Submit) id k5JMRLjI027358;
	Tue, 20 Jun 2006 08:27:21 +1000 (EST) (envelope-from lukeh)
From: Luke Howard <lukeh@padl.com>
Message-Id: <200606192227.k5JMRLjI027358@au.padl.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Organization: PADL Software Pty Ltd
To: kitten@ietf.org
References: <200606192040.WAA17036@uw1048.wdf.sap.corp>
	<tsl64iwrhzv.fsf@cz.mit.edu>
Date: Tue, 20 Jun 2006 08:27:21 +1000
Versions: dmail (bsd44) 2.6d/makemail 2.10
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.63
X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on au.padl.com
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7aefe408d50e9c7c47615841cb314bed
Cc: 
Subject: Re: SIP and GSS
X-BeenThere: kitten@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: lukeh@padl.com
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


Also it would be interesting to consider the interaction with key
exchange proposals for SRTP (eg draft-ietf-mmusic-sdescriptions-12.txt).

-- Luke

--

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



From kitten-bounces@lists.ietf.org Tue Jun 20 01:02:15 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FsYNN-00007m-9W; Tue, 20 Jun 2006 01:02:09 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FsYNM-00007M-GS
	for kitten@ietf.org; Tue, 20 Jun 2006 01:02:08 -0400
Received: from smtp3.su.se ([130.237.93.228])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FsYNL-0001Px-71
	for kitten@ietf.org; Tue, 20 Jun 2006 01:02:08 -0400
Received: from localhost (localhost [127.0.0.1])
	by smtp3.su.se (Postfix) with ESMTP id 1A58D3BF61;
	Tue, 20 Jun 2006 07:02:04 +0200 (CEST)
Received: from smtp3.su.se ([127.0.0.1])
	by localhost (smtp3.su.se [127.0.0.1]) (amavisd-new,
	port 10024) with LMTP
	id 05704-01-25; Tue, 20 Jun 2006 07:02:03 +0200 (CEST)
Received: from [10.0.0.242] (1-1-2-20a.rny.sth.bostream.se [82.182.132.64])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by smtp3.su.se (Postfix) with ESMTP id 6F4D63BE9C;
	Tue, 20 Jun 2006 07:02:02 +0200 (CEST)
Message-ID: <4497813F.9010509@it.su.se>
Date: Tue, 20 Jun 2006 07:01:51 +0200
From: Leif Johansson <leifj@it.su.se>
User-Agent: Thunderbird 1.5.0.2 (X11/20060420)
MIME-Version: 1.0
To: martin.rex@sap.com
References: <200606192040.WAA17036@uw1048.wdf.sap.corp>
In-Reply-To: <200606192040.WAA17036@uw1048.wdf.sap.corp>
X-Enigmail-Version: 0.94.0.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by amavisd-new at smtp.su.se
X-Spam-Status: No, hits=-1.586 tagged_above=-99 required=7 tests=[AWL=0.079,
	BAYES_00=-1.665]
X-Spam-Level: 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 93238566e09e6e262849b4f805833007
Cc: kitten@ietf.org, Sam Hartman <hartmans-ietf@mit.edu>
Subject: Re: SIP and GSS
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

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Martin Rex wrote:
> Sam Hartman wrote:
>> I was hoping to do something like http negotiate authentication for
>> sip after we get something reasonable with channel bindings for http
> 
> But you do realize that http negotiate requires
> HTTP/1.1 Connection:keep-alive and does not provide data integrity,
> so the use of SSL/HTTPS to protect the communication channel is
> strongly advised.

Yup, however it is possible to add support for mutual authentication.

	MVH leifj
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFEl4E/8Jx8FtbMZncRAgKvAJ9n5JhLMKmUrduNiwjtJwVQnQbitQCdFE6G
TprCGuDysLXndpotJ2WWFAo=
=Tyix
-----END PGP SIGNATURE-----

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



From kitten-bounces@lists.ietf.org Mon Jun 26 07:42:59 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FupUW-0001pr-EU; Mon, 26 Jun 2006 07:42:56 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FupUV-0001pm-Qa
	for kitten@ietf.org; Mon, 26 Jun 2006 07:42:55 -0400
Received: from brmea-mail-2.sun.com ([192.18.98.43])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FupUU-0008AE-B9
	for kitten@ietf.org; Mon, 26 Jun 2006 07:42:55 -0400
Received: from centralmail4brm.central.Sun.COM ([129.147.62.198])
	by brmea-mail-2.sun.com (8.13.6+Sun/8.12.9) with ESMTP id
	k5QBgsGS024674
	for <kitten@ietf.org>; Mon, 26 Jun 2006 05:42:54 -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 k5QBgrvs012637
	for <kitten@ietf.org>; Mon, 26 Jun 2006 05:42:53 -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
	k5QBgre8003978; Mon, 26 Jun 2006 06:42:53 -0500 (CDT)
Received: (from nw141292@localhost)
	by binky.Central.Sun.COM (8.13.6+Sun/8.13.6/Submit) id k5QBgrRI003977; 
	Mon, 26 Jun 2006 06:42:53 -0500 (CDT)
Date: Mon, 26 Jun 2006 06:42:53 -0500
From: Nicolas Williams <Nicolas.Williams@sun.com>
To: "Liqiang(Larry) Zhu" <lzhu@windows.microsoft.com>,
	Jeffrey Altman <jaltman@columbia.edu>, kitten@ietf.org
Message-ID: <20060626114252.GB21559@binky.Central.Sun.COM>
Mail-Followup-To: "Liqiang(Larry) Zhu" <lzhu@windows.microsoft.com>,
	Jeffrey Altman <jaltman@columbia.edu>, kitten@ietf.org
References: <440773C8.4010007@columbia.edu>
	<DAC3FCB50E31C54987CD10797DA511BA13D4D95F@WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com>
	<20060303173002.GC3676@binky.Central.Sun.COM>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20060303173002.GC3676@binky.Central.Sun.COM>
User-Agent: Mutt/1.5.11
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25
Cc: 
Subject: Re: WGLC for domain-based service principal names?
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 Fri, Mar 03, 2006 at 11:30:02AM -0600, Nicolas Williams wrote:
> On Fri, Mar 03, 2006 at 01:10:09AM -0800, Liqiang(Larry) Zhu wrote:
> > The name representations seems unchanged after the initial discussion.
> 
> No?  I'll dig up the e-mails and double check.

I can't find them.

Please remind me what convention Windows uses...

I've resubmitted the I-Ds with little change.

Thanks,

Nico
-- 

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



From kitten-bounces@lists.ietf.org Mon Jun 26 07:53:31 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fupek-0004Ht-3x; Mon, 26 Jun 2006 07:53:30 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Fupei-0004Bg-IU
	for kitten@ietf.org; Mon, 26 Jun 2006 07:53:28 -0400
Received: from au.padl.com ([203.13.32.1])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fupeg-0001Hy-SO
	for kitten@ietf.org; Mon, 26 Jun 2006 07:53:28 -0400
Received: from au.padl.com (localhost.padl.com [127.0.0.1])
	by au.padl.com (8.12.11/8.12.11) with ESMTP id k5QBr47i067857;
	Mon, 26 Jun 2006 21:53:04 +1000 (EST)
	(envelope-from lukeh@au.padl.com)
Received: (from lukeh@localhost)
	by au.padl.com (8.12.11/8.12.11/Submit) id k5QBr3hd067856;
	Mon, 26 Jun 2006 21:53:03 +1000 (EST) (envelope-from lukeh)
From: Luke Howard <lukeh@padl.com>
Message-Id: <200606261153.k5QBr3hd067856@au.padl.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Organization: PADL Software Pty Ltd
To: Nicolas.Williams@sun.com
References: <440773C8.4010007@columbia.edu>
	<DAC3FCB50E31C54987CD10797DA511BA13D4D95F@WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com>
	<20060303173002.GC3676@binky.Central.Sun.COM>
	<20060626114252.GB21559@binky.Central.Sun.COM>
Date: Mon, 26 Jun 2006 21:53:03 +1000
Versions: dmail (bsd44) 2.6d/makemail 2.10
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.63
X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on au.padl.com
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 30ac594df0e66ffa5a93eb4c48bcb014
Cc: kitten@ietf.org, lzhu@windows.microsoft.com
Subject: Re: WGLC for domain-based service principal names?
X-BeenThere: kitten@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: lukeh@padl.com
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


>Please remind me what convention Windows uses...

Windows SPNs that contain a domain component are of the form
service/host/domain.

-- Luke

--

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



From kitten-bounces@lists.ietf.org Mon Jun 26 07:57:55 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fupj0-0007tP-OS; Mon, 26 Jun 2006 07:57:54 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Fupiz-0007tK-Rg
	for kitten@ietf.org; Mon, 26 Jun 2006 07:57:53 -0400
Received: from brmea-mail-4.sun.com ([192.18.98.36])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fupiy-0001n4-GR
	for kitten@ietf.org; Mon, 26 Jun 2006 07:57:53 -0400
Received: from centralmail3brm.Central.Sun.COM ([129.147.62.199])
	by brmea-mail-4.sun.com (8.13.6+Sun/8.12.9) with ESMTP id
	k5QBvqMP011383
	for <kitten@ietf.org>; Mon, 26 Jun 2006 05:57:52 -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 k5QBtjVM010322
	for <kitten@ietf.org>; Mon, 26 Jun 2006 05:55:45 -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
	k5QBvpc6004010; Mon, 26 Jun 2006 06:57:51 -0500 (CDT)
Received: (from nw141292@localhost)
	by binky.Central.Sun.COM (8.13.6+Sun/8.13.6/Submit) id k5QBvpq6004009; 
	Mon, 26 Jun 2006 06:57:51 -0500 (CDT)
Date: Mon, 26 Jun 2006 06:57:51 -0500
From: Nicolas Williams <Nicolas.Williams@sun.com>
To: Luke Howard <lukeh@padl.com>
Message-ID: <20060626115751.GG5688@binky.Central.Sun.COM>
Mail-Followup-To: Luke Howard <lukeh@padl.com>, kitten@ietf.org,
	lzhu@windows.microsoft.com
References: <440773C8.4010007@columbia.edu>
	<DAC3FCB50E31C54987CD10797DA511BA13D4D95F@WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com>
	<20060303173002.GC3676@binky.Central.Sun.COM>
	<20060626114252.GB21559@binky.Central.Sun.COM>
	<200606261153.k5QBr3hd067856@au.padl.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200606261153.k5QBr3hd067856@au.padl.com>
User-Agent: Mutt/1.5.11
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 08170828343bcf1325e4a0fb4584481c
Cc: kitten@ietf.org, lzhu@windows.microsoft.com
Subject: Re: WGLC for domain-based service principal names?
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 Mon, Jun 26, 2006 at 09:53:03PM +1000, Luke Howard wrote:
> >Please remind me what convention Windows uses...
> 
> Windows SPNs that contain a domain component are of the form
> service/host/domain.

Thanks, that's what
draft-ietf-kitten-krb5-gssapi-domain-based-names-02.txt says (as did
-01).

The only thing left to do is to assign a raw krb5 name type for this.
IIRC Tom Yu is the registrar, yes?

Nico
-- 

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



From kitten-bounces@lists.ietf.org Mon Jun 26 13:14:38 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FuufU-0003KU-3j; Mon, 26 Jun 2006 13:14:36 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FuufS-0003KF-QU
	for kitten@ietf.org; Mon, 26 Jun 2006 13:14:34 -0400
Received: from chokecherry.srv.cs.cmu.edu ([128.2.185.41])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FuufQ-0002xs-IB
	for kitten@ietf.org; Mon, 26 Jun 2006 13:14:34 -0400
Received: from mariner.pc.cs.cmu.edu (MARINER.PC.CS.CMU.EDU [128.2.200.130])
	(authenticated bits=0)
	by chokecherry.srv.cs.cmu.edu (8.13.6/8.13.6) with ESMTP id
	k5QHEFBN020703
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Mon, 26 Jun 2006 13:14:22 -0400 (EDT)
Date: Mon, 26 Jun 2006 13:14:15 -0400
From: Jeffrey Hutzelman <jhutz@cmu.edu>
To: Nicolas Williams <Nicolas.Williams@sun.com>, Luke Howard <lukeh@padl.com>
Message-ID: <B9C0864628CEDD7E9C3627B4@mariner.pc.cs.cmu.edu>
In-Reply-To: <20060626115751.GG5688@binky.Central.Sun.COM>
References: <440773C8.4010007@columbia.edu>
	<DAC3FCB50E31C54987CD10797DA511BA13D4D95F@WIN-MSG-10.wingroup.windeploy.ntde
	v.microsoft.com>	<20060303173002.GC3676@binky.Central.Sun.COM>
	<20060626114252.GB21559@binky.Central.Sun.COM>
	<200606261153.k5QBr3hd067856@au.padl.com>
	<20060626115751.GG5688@binky.Central.Sun.COM>
Originator-Info: login-token=Mulberry:01DpL0oXj6aRVa3WwiQRAkEKUEK8yVxm17ByIGRBI=;
	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: ea4ac80f790299f943f0a53be7e1a21a
Cc: kitten@ietf.org, lzhu@windows.microsoft.com,
	Jeffrey Hutzelman <jhutz@cmu.edu>
Subject: Re: WGLC for domain-based service principal names?
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 Monday, June 26, 2006 06:57:51 AM -0500 Nicolas Williams 
<Nicolas.Williams@sun.com> wrote:

> On Mon, Jun 26, 2006 at 09:53:03PM +1000, Luke Howard wrote:
>> > Please remind me what convention Windows uses...
>>
>> Windows SPNs that contain a domain component are of the form
>> service/host/domain.
>
> Thanks, that's what
> draft-ietf-kitten-krb5-gssapi-domain-based-names-02.txt says (as did
> -01).
>
> The only thing left to do is to assign a raw krb5 name type for this.
> IIRC Tom Yu is the registrar, yes?

Formally, name type numbers are administered by the Kerberos working group 
(we expect that to change with the eventual publication of RFC1510ter). 
When the last call happens, we'll run a simultaneous last call on the 
number assignment.  Assuming that succeeds, I'll ask Tom to assign a number 
which can be substituted into the document before it is published.

Incidentally, it's normal for documents which require new values in 
existing registries to proceed through the entire IETF process with the new 
values listed as 'TBD'.  Actual values are normally assigned by the IANA 
after the document has been approved.

-- Jeff

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



From kitten-bounces@lists.ietf.org Thu Jun 29 15:50:12 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fw2WZ-0004kX-Nz; Thu, 29 Jun 2006 15:50:03 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fw2WY-0004j2-3u; Thu, 29 Jun 2006 15:50:02 -0400
Received: from willow.neustar.com ([209.173.53.84])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1Fw2WX-0001Y2-QN; Thu, 29 Jun 2006 15:50:02 -0400
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10])
	by willow.neustar.com (8.12.8/8.12.8) with ESMTP id k5TJo19F012740
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT);
	Thu, 29 Jun 2006 19:50:01 GMT
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1Fw2WX-0003Qx-Bb; Thu, 29 Jun 2006 15: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: <E1Fw2WX-0003Qx-Bb@stiedprstage1.ietf.org>
Date: Thu, 29 Jun 2006 15:50:01 -0400
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 3002fc2e661cd7f114cb6bae92fe88f1
Cc: kitten@lists.ietf.org
Subject: I-D ACTION:draft-ietf-kitten-gssapi-naming-exts-02.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 Naming Extensions
	Author(s)	: N. Williams
	Filename	: draft-ietf-kitten-gssapi-naming-exts-02.txt
	Pages		: 19
	Date		: 2006-6-29
	
The Generic Security Services API (GSS-API) provides a simple naming
   architecture that supports name-based authorization.  This document
   introduces new APIs that extend the GSS-API naming and authorization
   model.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-kitten-gssapi-naming-exts-02.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-naming-exts-02.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-naming-exts-02.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-6-29100212.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-kitten-gssapi-naming-exts-02.txt

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

Content-Type: text/plain
Content-ID: <2006-6-29100212.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 Thu Jun 29 15:50:14 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fw2Wj-0004xM-U6; Thu, 29 Jun 2006 15:50:13 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fw2WY-0004jP-Ev; Thu, 29 Jun 2006 15:50:02 -0400
Received: from stsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.16.129]
	helo=pine.neustar.com) by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1Fw2WX-0001Y3-Tk; Thu, 29 Jun 2006 15:50:02 -0400
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10])
	by pine.neustar.com (8.12.8/8.12.8) with ESMTP id k5TJo1UA025372
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT);
	Thu, 29 Jun 2006 19:50:01 GMT
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1Fw2WX-0003R3-Cs; Thu, 29 Jun 2006 15: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: <E1Fw2WX-0003R3-Cs@stiedprstage1.ietf.org>
Date: Thu, 29 Jun 2006 15:50:01 -0400
X-Spam-Score: -2.5 (--)
X-Scan-Signature: 32b73d73e8047ed17386f9799119ce43
Cc: kitten@lists.ietf.org
Subject: I-D ACTION:draft-ietf-kitten-extended-mech-inquiry-02.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		: Extended Generic Security Service Mechanism Inquiry APIs
	Author(s)	: N. Williams
	Filename	: draft-ietf-kitten-extended-mech-inquiry-02.txt
	Pages		: 14
	Date		: 2006-6-29
	
This document introduces new application programming interfaces
(APIs) to the Generic Security Services API (GSS-API) for extended
mechanism attribute inquiry.  These interfaces are primarily intended
for use in mechanism composition, but also to reduce instances of
hardcoding of mechanism identifiers in GSS applications.

These interfaces include: mechanism attributes and attribute sets, a
function for inquiring the attributes of a mechanism, a function for
indicating mechanisms that posses given attributes, and a function
for displaying mechanism attributes.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-kitten-extended-mech-inquiry-02.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-extended-mech-inquiry-02.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-extended-mech-inquiry-02.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-6-29100629.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-kitten-extended-mech-inquiry-02.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-kitten-extended-mech-inquiry-02.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2006-6-29100629.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 Thu Jun 29 15:50:22 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fw2Ws-0005JV-0f; Thu, 29 Jun 2006 15:50:22 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fw2WY-0004jV-IH; Thu, 29 Jun 2006 15:50:02 -0400
Received: from willow.neustar.com ([209.173.53.84])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1Fw2WY-0001Y5-04; Thu, 29 Jun 2006 15:50:02 -0400
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10])
	by willow.neustar.com (8.12.8/8.12.8) with ESMTP id k5TJo19F012744
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT);
	Thu, 29 Jun 2006 19:50:01 GMT
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1Fw2WX-0003RR-I3; Thu, 29 Jun 2006 15: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: <E1Fw2WX-0003RR-I3@stiedprstage1.ietf.org>
Date: Thu, 29 Jun 2006 15:50:01 -0400
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 32b73d73e8047ed17386f9799119ce43
Cc: kitten@lists.ietf.org
Subject: I-D ACTION:draft-ietf-kitten-stackable-pseudo-mechs-02.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		: Stackable Generic Security Service Pseudo-Mechanisms
	Author(s)	: N. Williams
	Filename	: draft-ietf-kitten-stackable-pseudo-mechs-02.txt
	Pages		: 17
	Date		: 2006-6-29
	
This document defines and formalizes the concept of stackable pseudo-
mechanisms, and associated concept of composite mechanisms, for the
Generic Security Service Application Programming Interface (GSS-API),
as well as several utility functions.

Stackable GSS-API pseudo-mechanisms allow for the composition of new
mechanisms that combine features from multiple mechanisms.  Stackable
mechanisms that add support for Perfect Forward Security (PFS), data
compression, additional authentication factors, etc... are
facilitated by this document.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-kitten-stackable-pseudo-mechs-02.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-stackable-pseudo-mechs-02.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-stackable-pseudo-mechs-02.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-6-29102436.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-kitten-stackable-pseudo-mechs-02.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-kitten-stackable-pseudo-mechs-02.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2006-6-29102436.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 Thu Jun 29 17:47:45 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fw4MT-0007bC-IX; Thu, 29 Jun 2006 17:47:45 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fw4MP-0007XI-Co; Thu, 29 Jun 2006 17:47:41 -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 1Fw3En-0007Cp-FF; Thu, 29 Jun 2006 16:35:45 -0400
Received: from cypress.neustar.com ([209.173.57.84])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1Fw2m1-00030T-1D; Thu, 29 Jun 2006 16:06:03 -0400
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10])
	by cypress.neustar.com (8.12.8/8.12.8) with ESMTP id k5TJo1jx010143
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT);
	Thu, 29 Jun 2006 19:50:01 GMT
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1Fw2WX-0003Ra-K0; Thu, 29 Jun 2006 15: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: <E1Fw2WX-0003Ra-K0@stiedprstage1.ietf.org>
Date: Thu, 29 Jun 2006 15:50:01 -0400
X-Spam-Score: -2.6 (--)
X-Scan-Signature: 31247fb3be228bb596db9127becad0bc
Cc: kitten@lists.ietf.org
Subject: I-D ACTION:draft-ietf-kitten-krb5-gssapi-domain-based-names-02.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-02.txt
	Pages		: 8
	Date		: 2006-6-29
	
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-02.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-02.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-02.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-6-29102919.I-D@ietf.org>

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

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

Content-Type: text/plain
Content-ID: <2006-6-29102919.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 Thu Jun 29 18:10:22 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fw4iM-0001V2-4O; Thu, 29 Jun 2006 18:10:22 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fw4iH-0001Jv-BU; Thu, 29 Jun 2006 18:10:17 -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 1Fw3El-0007CF-Hf; Thu, 29 Jun 2006 16:35:43 -0400
Received: from cypress.neustar.com ([209.173.57.84])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1Fw2lz-00030T-Fx; Thu, 29 Jun 2006 16:06:00 -0400
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10])
	by cypress.neustar.com (8.12.8/8.12.8) with ESMTP id k5TJo2jx010185
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT);
	Thu, 29 Jun 2006 19:50:03 GMT
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1Fw2WY-0003VB-Tx; Thu, 29 Jun 2006 15: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: <E1Fw2WY-0003VB-Tx@stiedprstage1.ietf.org>
Date: Thu, 29 Jun 2006 15:50:02 -0400
X-Spam-Score: -2.6 (--)
X-Scan-Signature: b7b9551d71acde901886cc48bfc088a6
Cc: kitten@lists.ietf.org
Subject: I-D ACTION:draft-ietf-kitten-gssapi-channel-bindings-02.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		: Clarifications and Extensions to the GSS-API for the Use of Channel Bindings
	Author(s)	: N. Williams
	Filename	: draft-ietf-kitten-gssapi-channel-bindings-02.txt
	Pages		: 15
	Date		: 2006-6-29
	
This document clarifies and generalizes the GSS-API "channel
   bindings" facility.  This document also specifies the format of the
   various types of channel bindings.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-kitten-gssapi-channel-bindings-02.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-channel-bindings-02.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-channel-bindings-02.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-6-29121227.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-kitten-gssapi-channel-bindings-02.txt

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

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





