No subject
Fri Jan 22 03:43:47 MST 2010
see the following text) and then you responded indicating you had one addit=
ional question about what should be returned. It is not clear to me that yo=
u ever received an answer from #4 (see text) If you did not let me know and=
I will follow up on that question as well.
Text from email:
"ood morning Matthieu. Thanks for your patience. Our documentation team has=
responded to 3 of the four cross-reference requests. Details are shown bel=
ow, as well as an attached pdf ([MS-ADTS]_Changes.pdf) showing new text for=
that document.
1. A request was made for a link in '[MS-ADTS] section 7.1.6.7.3 msDs-suppo=
rtedEncryptionTypes', pointing to '[MS-LSAD] section 2.2.7.18 TRUSTED_DOMAI=
N_SUPPORTED_ENCRYPTION_TYPES'.
We haven't added this link because the relationship between the trustedDoma=
in!msDs-supportedEncryptionTypes attribute and TRUSTED_DOMAIN_SUPPORTED_ENC=
RYPTION_TYPES structure is already specified in '[MS-LSAD] section 3.1.1.5 =
Trusted Domain Object Data Model'.
2. A request was made for a link in '[MS-ADTS] section 7.1.6.7.3 msDs-suppo=
rtedEncryptionTypes', pointing to '[MS-NRPC] section 2.2.1.3.11 NETLOGON_DO=
MAIN_INFO (SupportedEncTypes)'.
We haven't added this link, because we think this link would be inappropria=
te, since these two sections are about two different types of object. '[MS-=
ADTS] section 7.1.6.7.3 msDs-supportedEncryptionTypes' is about trustedDoma=
in objects; however, the NETLOGON_DOMAIN_INFO structure in '[MS-NRPC] secti=
on 2.2.1.3.11 NETLOGON_DOMAIN_INFO' provides information on a domain joined=
computer object.
Therefore, instead of adding a cross reference between trustedDomain!msDs-s=
upportedEncryptionTypes and NETLOGON_DOMAIN_INFO, we have added text in the=
[MS-ADTS] sections noted below providing information on the msDs-supported=
EncryptionTypes attribute of the computer object.
[MS-ADTS] 7.4.1 State of a Machine Joined to a Domain
[MS-ADTS] 7.4.2 State in an Active Directory Domain
[MS-ADTS] 7.4.3 Relationship to Protocols
3. A request was made for links in '[MS-LSAD] section 2.2.7.18 TRUSTED_DOMA=
IN_SUPPORTED_ENCRYPTION_TYPES', pointing to '[MS-ADTS] 7.1.6.7.3 msDs-suppo=
rtedEncryptionTypes' and '[MS-NRPC] 2.2.1.3.11 NETLOGON_DOMAIN_INFO' (Suppo=
rtedEncTypes).
We haven't added these links, because when describing the member SupportedE=
ncTypes of struct NETLOGON_DOMAIN_INFO, '[MS-NRPC] section 2.2.1.3.11 NETLO=
GON_DOMAIN_INFO' links to section '[MS-LSAD] 2.2.7.18 TRUSTED_DOMAIN_SUPPOR=
TED_ENCRYPTION_TYPES', which describes the structure represented in Support=
edEncTypes. Additionally '[MS-LSAD] section 3.1.1.5 Trusted Domain Object D=
ata Model' references '[MS-ADTS] section 7.1.6.7.3 msDs-supportedEncryption=
Types' to link the data retrieved from AD.
Also, [MS-LSAD] does not need to reference [MS-NRPC] for the purposes of su=
pported encryption types because MS-LSAD does not consume any encryption ty=
pe definition in [MS-NRPC].
Additionally, [MS-LSAD] supportedEncryptionTypes usage is for trusts only, =
whereas [MS-NRPC] supportedEncryptionTypes usage is for both trusts and com=
puters.
4. A request was made for links in '[MS-NRPC] 2.2.1.3.11 NETLOGON_DOMAIN_IN=
FO (SupportedEncTypes)', pointing to '[MS-ADTS] 7.1.6.7.3 msDs-supportedEnc=
ryptionTypes'.
This request is currently pending review."
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++=
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++=
++++++++++++++++++++++++++++++++++++++++++++++++++
Please let me know if this helps to clear things up.
Thanks
John Dunning
Senior Escalation Engineer Microsoft Corporation US-CSS DSC PROTOCOL TEAM
Email: johndun at microsoft.com<mailto:johndun at microsoft.com>
From: Matthieu Patou [mailto:mat at matws.net]
Sent: Thursday, February 18, 2010 3:09 PM
To: John Dunning
Cc: MSSolve Case Email; pfif at tridgell.net; cifs-protocol at samba.org; Bill We=
sse; Sebastian Canevari
Subject: Re: [cifs-protocol] [REG:110011276087815] [MS-NRPC] 2.2.1.3.11 NET=
LOGON_DOMAIN_INFO SupportedEncTypes
Hi johnOn 18/02/2010 23:45, John Dunning wrote:
Hello Matthieu.
The Microsoft Escalation Engineer that you have been working with, Bill=
Wesse, is out of our office. I will be handling this case in his absence.=
Unfortunately I have not been privy to all of the email exchanges regardin=
g this case. I want to make sure that we address all of your outstanding qu=
estions in this regard. To my understanding you have one remaining question=
in this area which is: The very first time the SupportedEncTypes is retur=
ned, if the DC has no information about the workstation, what should be ret=
urned? 0x00 or 0xFF or something else.
Is it accurate that this is the only remaining question regarding this case=
?
I think so but I must confess that my question was asked already some times=
ago and as you broke the thread I have some difficulties to remember it in=
all the details.
Matthieu.
--_000_F0A207595A30EE47858890749689FE4F2D46DABETK5EX14MBXC133r_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3DGenerator content=3D"Microsoft Word 12 (filtered medium)">
<style>
<!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
color:black;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body bgcolor=3Dwhite lang=3DEN-US link=3Dblue vlink=3Dpurple>
<div class=3DSection1>
<p class=3DMsoNormal><span style=3D'color:#1F497D'>Hi </span>Matthieu,<o:p>=
</o:p></p>
<p class=3DMsoNormal><o:p> </o:p></p>
<p class=3DMsoNormal>From our case notes I found that Bill had sent you an =
email
on 25-January (see the following text) and then you responded indicating yo=
u
had one additional question about what should be returned. It is not clear =
to
me that you ever received an answer from #4 (see text) If you did not let m=
e
know and I will follow up on that question as well.<o:p></o:p></p>
<p class=3DMsoNormal><o:p> </o:p></p>
<p class=3DMsoNormal>Text from email:<o:p></o:p></p>
<p class=3DMsoNormal><o:p> </o:p></p>
<p class=3DMsoNormal>“ood morning Matthieu. Thanks for your patience.=
Our
documentation team has responded to 3 of the four cross-reference requests.
Details are shown below, as well as an attached pdf ([MS-ADTS]_Changes.pdf)
showing new text for that document.<o:p></o:p></p>
<p class=3DMsoNormal><o:p> </o:p></p>
<p class=3DMsoNormal>1. A request was made for a link in '[MS-ADTS] section
7.1.6.7.3 msDs-supportedEncryptionTypes', pointing to '[MS-LSAD] section
2.2.7.18 TRUSTED_DOMAIN_SUPPORTED_ENCRYPTION_TYPES'.<o:p></o:p></p>
<p class=3DMsoNormal><o:p> </o:p></p>
<p class=3DMsoNormal>We haven’t added this link because the relations=
hip between
the trustedDomain!msDs-supportedEncryptionTypes attribute and
TRUSTED_DOMAIN_SUPPORTED_ENCRYPTION_TYPES structure is already specified in
'[MS-LSAD] section 3.1.1.5 Trusted Domain Object Data Model'.<o:p></o:p></p=
>
<p class=3DMsoNormal><o:p> </o:p></p>
<p class=3DMsoNormal>2. A request was made for a link in '[MS-ADTS] section
7.1.6.7.3 msDs-supportedEncryptionTypes', pointing to '[MS-NRPC] section
2.2.1.3.11 NETLOGON_DOMAIN_INFO (SupportedEncTypes)'.<o:p></o:p></p>
<p class=3DMsoNormal><o:p> </o:p></p>
<p class=3DMsoNormal>We haven’t added this link, because we think thi=
s link would
be inappropriate, since these two sections are about two different types of
object. '[MS-ADTS] section 7.1.6.7.3 msDs-supportedEncryptionTypes' is abou=
t
trustedDomain objects; however, the NETLOGON_DOMAIN_INFO structure in
'[MS-NRPC] section 2.2.1.3.11 NETLOGON_DOMAIN_INFO' provides information on=
a
domain joined computer object.<o:p></o:p></p>
<p class=3DMsoNormal><o:p> </o:p></p>
<p class=3DMsoNormal>Therefore, instead of adding a cross reference between
trustedDomain!msDs-supportedEncryptionTypes and NETLOGON_DOMAIN_INFO, we ha=
ve
added text in the [MS-ADTS] sections noted below providing information on t=
he
msDs-supportedEncryptionTypes attribute of the computer object.<o:p></o:p><=
/p>
<p class=3DMsoNormal><o:p> </o:p></p>
<p class=3DMsoNormal>[MS-ADTS] 7.4.1 State of a Machine Joined to a Domain<=
o:p></o:p></p>
<p class=3DMsoNormal>[MS-ADTS] 7.4.2 State in an Active Directory Domain<o:=
p></o:p></p>
<p class=3DMsoNormal>[MS-ADTS] 7.4.3 Relationship to Protocols<o:p></o:p></=
p>
<p class=3DMsoNormal><o:p> </o:p></p>
<p class=3DMsoNormal>3. A request was made for links in '[MS-LSAD] section
2.2.7.18 TRUSTED_DOMAIN_SUPPORTED_ENCRYPTION_TYPES', pointing to '[MS-ADTS]
7.1.6.7.3 msDs-supportedEncryptionTypes' and '[MS-NRPC] 2.2.1.3.11
NETLOGON_DOMAIN_INFO' (SupportedEncTypes).<o:p></o:p></p>
<p class=3DMsoNormal><o:p> </o:p></p>
<p class=3DMsoNormal>We haven’t added these links, because when descr=
ibing the
member SupportedEncTypes of struct NETLOGON_DOMAIN_INFO, '[MS-NRPC] section
2.2.1.3.11 NETLOGON_DOMAIN_INFO' links to section '[MS-LSAD] 2.2.7.18
TRUSTED_DOMAIN_SUPPORTED_ENCRYPTION_TYPES', which describes the structure
represented in SupportedEncTypes. Additionally '[MS-LSAD] section 3.1.1.5
Trusted Domain Object Data Model' references '[MS-ADTS] section 7.1.6.7.3
msDs-supportedEncryptionTypes' to link the data retrieved from AD.<o:p></o:=
p></p>
<p class=3DMsoNormal><o:p> </o:p></p>
<p class=3DMsoNormal>Also, [MS-LSAD] does not need to reference [MS-NRPC] f=
or the
purposes of supported encryption types because MS-LSAD does not consume any
encryption type definition in [MS-NRPC].<o:p></o:p></p>
<p class=3DMsoNormal><o:p> </o:p></p>
<p class=3DMsoNormal>Additionally, [MS-LSAD] supportedEncryptionTypes usage=
is
for trusts only, whereas [MS-NRPC] supportedEncryptionTypes usage is for bo=
th
trusts and computers.<o:p></o:p></p>
<p class=3DMsoNormal><o:p> </o:p></p>
<p class=3DMsoNormal>4. A request was made for links in '[MS-NRPC] 2.2.1.3.=
11
NETLOGON_DOMAIN_INFO (SupportedEncTypes)', pointing to '[MS-ADTS] 7.1.6.7.3
msDs-supportedEncryptionTypes'.<o:p></o:p></p>
<p class=3DMsoNormal><o:p> </o:p></p>
<p class=3DMsoNormal>This request is currently pending review.”<o:p><=
/o:p></p>
<p class=3DMsoNormal><o:p> </o:p></p>
<p class=3DMsoNormal>++++++++++++++++++++++++++++++++++++++++++++++++++++++=
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++=
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++<o:p=
></o:p></p>
<p class=3DMsoNormal><o:p> </o:p></p>
<p class=3DMsoNormal>Please let me know if this helps to clear things up.<s=
pan
style=3D'color:#1F497D'><o:p></o:p></span></p>
<p class=3DMsoNormal><span style=3D'color:#1F497D'><o:p> </o:p></span>=
</p>
<div>
<p class=3DMsoNormal><span style=3D'font-size:10.5pt;font-family:Consolas;
color:#1F497D'>Thanks<o:p></o:p></span></p>
<p class=3DMsoNormal><span style=3D'font-size:10.5pt;font-family:Consolas;
color:#1F497D'>John Dunning<o:p></o:p></span></p>
<p class=3DMsoNormal><span style=3D'font-size:10.5pt;font-family:Consolas;
color:#1F497D'>Senior Escalation Engineer Microsoft Corporation US-CSS DSC
PROTOCOL TEAM<o:p></o:p></span></p>
<p class=3DMsoNormal><span style=3D'font-size:10.5pt;font-family:Consolas;
color:#1F497D'>Email: <a href=3D"mailto:johndun at microsoft.com">johndun at micr=
osoft.com</a><o:p></o:p></span></p>
</div>
<p class=3DMsoNormal><span style=3D'color:#1F497D'><o:p> </o:p></span>=
</p>
<div>
<div style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in'>
<p class=3DMsoNormal><b><span style=3D'font-size:10.0pt;font-family:"Tahoma=
","sans-serif";
color:windowtext'>From:</span></b><span style=3D'font-size:10.0pt;font-fami=
ly:
"Tahoma","sans-serif";color:windowtext'> Matthieu Patou [mailto:mat at matws.n=
et] <br>
<b>Sent:</b> Thursday, February 18, 2010 3:09 PM<br>
<b>To:</b> John Dunning<br>
<b>Cc:</b> MSSolve Case Email; pfif at tridgell.net; cifs-protocol at samba.org; =
Bill
Wesse; Sebastian Canevari<br>
<b>Subject:</b> Re: [cifs-protocol] [REG:110011276087815] [MS-NRPC] 2.2.1.3=
.11
NETLOGON_DOMAIN_INFO SupportedEncTypes<o:p></o:p></span></p>
</div>
</div>
<p class=3DMsoNormal><o:p> </o:p></p>
<p class=3DMsoNormal>Hi johnOn 18/02/2010 23:45, John Dunning wrote: <o:p><=
/o:p></p>
<p class=3DMsoNormal>Hello Matthieu.<o:p></o:p></p>
<p class=3DMsoNormal> The Microsoft Escalation Engineer t=
hat
you have been working with, Bill Wesse, is out of our office. I will =
be
handling this case in his absence. Unfortunately I have not been privy to a=
ll
of the email exchanges regarding this case. I want to make sure that we add=
ress
all of your outstanding questions in this regard. To my understanding you h=
ave
one remaining question in this area which is: The very first time the
SupportedEncTypes is returned, if the DC has no information about the
workstation, what should be returned? 0x00 or 0xFF or something else.<o:p><=
/o:p></p>
<p class=3DMsoNormal> <o:p></o:p></p>
<p class=3DMsoNormal>Is it accurate that this is the only remaining questio=
n
regarding this case?<o:p></o:p></p>
<p class=3DMsoNormal><span style=3D'font-size:12.0pt;font-family:"Times New=
Roman","serif"'>I
think so but I must confess that my question was asked already some times a=
go
and as you broke the thread I have some difficulties to remember it in all =
the
details.<br>
<br>
<o:p></o:p></span></p>
<p class=3DMsoNormal> <o:p></o:p></p>
<p class=3DMsoNormal><span style=3D'font-size:12.0pt;font-family:"Times New=
Roman","serif"'><o:p> </o:p></span></p>
<p class=3DMsoNormal><span style=3D'font-size:12.0pt;font-family:"Times New=
Roman","serif"'>Matthieu.<o:p></o:p></span></p>
</div>
</body>
</html>
--_000_F0A207595A30EE47858890749689FE4F2D46DABETK5EX14MBXC133r_--
More information about the cifs-protocol
mailing list