Hi Matthieu, >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 you 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 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 below, 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-supportedEncryptionTypes', pointing to '[MS-LSAD] section 2.2.7.18 TRUSTED_DOMAIN_SUPPORTED_ENCRYPTION_TYPES'. We haven't added this link because the relationship 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'. 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)'. We haven't added this link, because we think this 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 about 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. Therefore, instead of adding a cross reference between trustedDomain!msDs-supportedEncryptionTypes and NETLOGON_DOMAIN_INFO, we have added text in the [MS-ADTS] sections noted below providing information on the msDs-supportedEncryptionTypes 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_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). We haven't added these links, because when describing 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. Also, [MS-LSAD] does not need to reference [MS-NRPC] for the purposes of supported encryption types because MS-LSAD does not consume any encryption type definition in [MS-NRPC]. Additionally, [MS-LSAD] supportedEncryptionTypes usage is for trusts only, whereas [MS-NRPC] supportedEncryptionTypes usage is for both trusts and computers. 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'. 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: [email protected]<mailto:[email protected]> From: Matthieu Patou [mailto:[email protected]] Sent: Thursday, February 18, 2010 3:09 PM To: John Dunning Cc: MSSolve Case Email; [email protected]; [email protected]; Bill Wesse; Sebastian Canevari Subject: Re: [cifs-protocol] [REG:110011276087815] [MS-NRPC] 2.2.1.3.11 NETLOGON_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 regarding this case. I want to make sure that we address all of your outstanding questions in this regard. To my understanding you have 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. 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.
_______________________________________________ cifs-protocol mailing list [email protected] https://lists.samba.org/mailman/listinfo/cifs-protocol
