You are very welcome; I anticipated more detail would go into the document than
what did (further delineation in the document would have to go, of necessity,
in the Windows Behavior section.
Thank you for both your patience, understanding and document improvement
feedback. It has been a pleasur
On Tue, Dec 16, 2008 at 04:06:46AM -0800, Bill Wesse wrote:
> Good afternoon Mr. Simpkins. Thank you for your patience.
>
> We have modified [MS-NLMP] for a future posting, as shown below, to address
> your comments (which I have also included, for the sake of completeness).
>
> Please let me kn
Good afternoon Mr. Simpkins. Thank you for your patience.
We have modified [MS-NLMP] for a future posting, as shown below, to address
your comments (which I have also included, for the sake of completeness).
Please let me know if this meets your needs.
==
Thank you Adam - I have added your comments to the change request.
Regards,
Bill Wesse
MCSE, MCTS / Escalation Engineer, US-CSS DSC PROTOCOL TEAM
8055 Microsoft Way
Charlotte, NC 28273
TEL: +1(980) 776-8200
CELL: +1(704) 661-5438
FAX: +1(704) 665-9606
-Original Message-
From: Adam Simpk
On Tue, Nov 04, 2008 at 02:57:00AM -0800, Bill Wesse wrote:
> Thank you very much for your considerations. I have filed a
> documentation change request against [MS-NLMP] concerning NTLMSSP
> InitialContextTokens (see 'Expected' below)..
Thanks, Bill. I do have one comment about some of your text
Thank you very much for your considerations. I have filed a documentation
change request against [MS-NLMP] concerning NTLMSSP InitialContextTokens (see
'Expected' below)..
==
Change Comment / Request:
The documentation
On Mon, Nov 03, 2008 at 07:24:08AM -0800, Bill Wesse wrote:
> While I agree with your comments concerning RFC 4178 /
> GSS_Accept_sec_context(), that is not the case with the Windows
> implementation, which accepts raw NTLM and Kerberos tokens - as specified in
> the SPNEGO document ([MS-SPNG] 3
While I agree with your comments concerning RFC 4178 /
GSS_Accept_sec_context(), that is not the case with the Windows implementation,
which accepts raw NTLM and Kerberos tokens - as specified in the SPNEGO
document ([MS-SPNG] 3.2.5.2 Universal Receiver), and as evidenced in the
network traces.
On Fri, Oct 31, 2008 at 09:06:38AM -0700, Bill Wesse wrote:
> I am curious about your thoughts concerning the below; I did a bit
> more looking into the traces:
>
> A note concerning 'spnego_ntlmssp.cap': the Network Monitor 3.1 parser
> incorrectly marks the token as an 'InnerContextToken' instea
I am curious about your thoughts concerning the below; I did a bit more looking
into the traces:
A note concerning 'spnego_ntlmssp.cap': the Network Monitor 3.1 parser
incorrectly marks the token as an 'InnerContextToken' instead of an
'InitialContextToken'.
>From what I can see, spnego_ntlmssp.
Thanks! I will proceed with that info.
Regards,
Bill Wesse
MCSE, MCTS / Escalation Engineer, US-CSS DSC PROTOCOL TEAM
8055 Microsoft Way
Charlotte, NC 28273
TEL: +1(980) 776-8200
CELL: +1(704) 661-5438
FAX: +1(704) 665-9606
-Original Message-
From: Adam Simpkins [mailto:[EMAIL PROTECTE
On Wed, Oct 29, 2008 at 09:37:05AM -0700, Bill Wesse wrote:
> Adam, thank you very much for your persistence.
>
> I apologize for responding against the two issues with the same
> answer. In order to make sure I don't commit another mix-up, I have
> superseded SRX080803600053 with SRX081029600208.
Adam, thank you very much for your persistence.
I apologize for responding against the two issues with the same answer. In
order to make sure I don't commit another mix-up, I have superseded
SRX080803600053 with SRX081029600208.
I did a careful backtrack on the question/response history, and no
On Tue, Oct 28, 2008 at 02:45:19AM -0700, Bill Wesse wrote:
> Good morning Mr. Simpkins. I have attached '[MS-SPNG]_Changes.pdf',
> which shows the changes we have made to [MS-SPNG], as well as the
> responses to your comments and questions (below).
> Please let me know if this answers your questio
Good morning Mr. Simpkins. Out document developers have provided the below
change information for [MS-SMB], adding a cross reference to [MS-SPNG] in
section 3.2.4.2.3. Please note that the other change request for [MS-SPNG]
(Windows Behavior <9>, replace reference RFC2743 with RFC4178) is still
You are, as always, completely welcome!
Regards,
Bill Wesse
MCSE / Escalation Engineer, US-CSS DSC PROTOCOL TEAM
8055 Microsoft Way
Charlotte, NC 28273
TEL: +1(980) 776-8200
CELL: +1(704) 661-5438
FAX: +1(704) 665-9606
We're Hiring
http://members.microsoft.com/careers/search/details.aspx?JobID=
On Wed, Oct 08, 2008 at 07:55:52AM -0700, Bill Wesse wrote:
> My pleasure!
>
> Here is copy of tentative text changes to the [MS-SPNG] document (these are
> waiting for internal approval - I will advise you as soon as the text is
> finalized):
Thanks. The new text looks good.
--
Adam Simpkin
My pleasure!
Here is copy of tentative text changes to the [MS-SPNG] document (these are
waiting for internal approval - I will advise you as soon as the text is
finalized):
==
OID 1.2.840.113554.1.2.2 is ALWAYS include
On Fri, Oct 03, 2008 at 07:18:05AM -0700, Bill Wesse wrote:
> Good morning again! Our documentation development team advises me the
> following change will be implemented in a future posting of [MS-SMB]:
>
> [MS-SMB]: Server Message Block (SMB) Protocol Specification
> Section 3.2.4.2.3 User Auth
19 matches
Mail list logo
