From: [email-masked]
Date: Thu, 18 Apr 2002 18:21:53 -0500 (CDT)

with Microsoft SMTPSVC(5.0.2195.4905);
	 Thu, 18 Apr 2002 14:33:44 -0700
Received: from 157.54.8.23 by INET-VRS-03.redmond.corp.microsoft.com (InterScan E-Mail
VirusWall NT); Thu, 18 Apr 2002 14:34:20 -0700
Received: from red-imc-04.redmond.corp.microsoft.com ([157.54.2.168]) by
inet-hub-01.redmond.corp.microsoft.com with Microsoft SMTPSVC(5.0.2195.4905);
	 Thu, 18 Apr 2002 14:33:43 -0700
Received: from win-imc-01.wingroup.windeploy.ntdev.microsoft.com ([157.54.0.39]) by
red-imc-04.redmond.corp.microsoft.com with Microsoft SMTPSVC(5.0.2195.2966);
	 Thu, 18 Apr 2002 14:33:43 -0700
Received: from WIN-MSG-06.wingroup.windeploy.ntdev.microsoft.com ([157.54.2.22]) by
win-imc-01.wingroup.windeploy.ntdev.microsoft.com with Microsoft SMTPSVC(6.0.3604.0);
	 Thu, 18 Apr 2002 14:30:47 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.0.6177.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/mixed;
	boundary="------------InterScan_NT_MIME_Boundary"
Subject: item from bcn issues list
Date: Thu, 18 Apr 2002 14:30:21 -0700
Message-ID:
<[email-masked]>
Thread-Topic: item from bcn issues list
Thread-Index: AcHnIL673PW8HzstQdyfNhNFC1v5iw==
From: "John Brezak" <[email-masked]>
To: <[email-masked]>, <[email-masked]>
X-OriginalArrivalTime: 18 Apr 2002 21:30:47.0651 (UTC) FILETIME=[4DFD7330:01C1E720]
Sender: [email-masked]
Precedence: bulk

This is a multi-part message in MIME format.

--------------InterScan_NT_MIME_Boundary
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C1E720.3E4FE52C"

------_=_NextPart_001_01C1E720.3E4FE52C
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

I picked up on this from the Kerberos-clarifications issues list:

"Issues on streaming of multiple request on single TCP connection (not
clear what this was, looking at current text - brezak)"

The current I-D describes that a new connection will be established for
each authentication exchange. But further on in the paragraph, there is
a sentence - "The KDC may close the TCP stream after sending a response,
but may leave the stream open if it expects a followup.."

This implies that multiple requests can be done on the same connection.

Ideally, a single connection can be setup between the client and KDC.
The client would be able to send out as many requests as it needs then
wait for the replies. This is pipelined behavior. The KDC can linger on
closing the connection for some timeout to avoid having the client
setting up new connections all of the time.

It would be nice to not require strict request-response behavior as long
as the client can match up the results form the KDC.

Requests and responses benefit from a request nonce that can be used to
locating pairs. However the krb-error does not contain the request nonce
that generated the error. Adding a krb-error e-data Typed-data for
request-nonce would be useful for pipelining requests.=20

=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D=
-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D
John Brezak                       * mailto:[email-masked]
Microsoft Corporation        * 425-706-2602
One Microsoft Way
Redmond, WA 98052

------_=_NextPart_001_01C1E720.3E4FE52C
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.0.6177.0">
<TITLE>item from bcn issues list</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">I =
picked up on this from</FONT></SPAN><SPAN LANG=3D"en-us"> <FONT SIZE=3D2 =
FACE=3D"Arial">the</FONT></SPAN><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial"></FONT></SPAN><SPAN LANG=3D"en-us"> <FONT SIZE=3D2 =
FACE=3D"Arial">Kerberos</FONT></SPAN><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">-clarifications issues list</FONT></SPAN><SPAN =
LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">:</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN></P>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">&#8220;</FONT></SPAN><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">Issues on streaming of multiple request on single TCP =
connection (not clear what this was, looking at current text - =
breza</FONT></SPAN><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">k</FONT></SPAN><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">)</FONT></SPAN><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">&#8221;</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN></P>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">The =
current I-D describes that a new connection will be established for each =
authentication exchange.</FONT></SPAN><SPAN LANG=3D"en-us"> <FONT =
SIZE=3D2 FACE=3D"Arial">But further on in the paragraph, there is a =
sentence</FONT></SPAN><SPAN LANG=3D"en-us"> <FONT SIZE=3D2 =
FACE=3D"Arial">&#8211;</FONT></SPAN><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial"></FONT></SPAN><SPAN LANG=3D"en-us"> <FONT SIZE=3D2 =
FACE=3D"Arial">&#8220;</FONT></SPAN><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">The KDC may close the TCP stream after sending a =
response, but may leave the stream open if it expects a =
followup..</FONT></SPAN><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">&#8221;</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN></P>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">T</FONT></SPAN><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">his implies that multiple requests can be done on the =
same connection.</FONT></SPAN></P>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">Ideally, a single connection can be setup between the =
client and KDC. The client would be able to send out as many requests as =
it needs then wait for the replies. This is pipelined =
behavior.</FONT></SPAN><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial"> The KDC can linger on closing the connection for some =
timeout to avoid</FONT></SPAN><SPAN LANG=3D"en-us"> <FONT SIZE=3D2 =
FACE=3D"Arial">having the client setting up</FONT></SPAN><SPAN =
LANG=3D"en-us"> <FONT SIZE=3D2 FACE=3D"Arial">new =
connections</FONT></SPAN><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial"> all of the time.</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN></P>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">It =
would be nice to not require strict request-response behavior as long as =
the client can match up the results</FONT></SPAN><SPAN =
LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial"> form the =
KDC.</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN></P>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">Requests and responses benefit from a request nonce that =
can be used to locating pairs. However the krb-error does not contain =
the request nonce that generated the error. Adding a krb-error e-data =
Typed-data for request-nonce would be useful for pipelining =
requests.</FONT></SPAN><SPAN LANG=3D"en-us"> </SPAN></P>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"></SPAN><A NAME=3D""><SPAN =
LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Tahoma">=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D=
-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D</FONT></SPAN></A=
></P>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Tahoma">John =
Brezak&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</FONT><=
/SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"> <FONT COLOR=3D"#800000" SIZE=3D2 =
FACE=3D"Wingdings">*</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Tahoma"></FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><U></U></SPAN><U><SPAN LANG=3D"en-us"> <FONT =
COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Tahoma"><A =
HREF=3D"mailto:[email-masked]">mailto:[email-masked]</A></F=
ONT></SPAN></U><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"></SPAN></P>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Tahoma">Microsoft =
Corporation&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> =
<FONT COLOR=3D"#800000" SIZE=3D2 FACE=3D"Wingdings">(</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT SIZE=3D1 FACE=3D"Comic =
Sans MS"></FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> =
<FONT SIZE=3D2 FACE=3D"Tahoma">425-706-2602</FONT></SPAN></P>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Tahoma">One =
Microsoft Way</FONT></SPAN></P>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Tahoma">Redmond, WA 98052</FONT></SPAN></P>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"></SPAN></P>

</BODY>
</HTML>
------_=_NextPart_001_01C1E720.3E4FE52C--

--------------InterScan_NT_MIME_Boundary--