Re: [cifs-protocol] CAR - ldap display specifiers
Hi Hongwei, >Thanks for your request. We will work on it and let you know as >soon as we complete the investigation. Any progress on this? Would you like us to give you a tool that produces the appropriate output in LDIF format? Cheers, Tridge ___ cifs-protocol mailing list cifs-protocol@cifs.org https://lists.samba.org/mailman/listinfo/cifs-protocol
Re: [cifs-protocol] CAR - ldap display specifiers
Hi Bill, Thanks for the LDIF! Can we assume the license on this is the same as for the schema? For the schema the version we got from MS had the license at the top, which you can see here: For the schema license, see this: http://samba.org/ftp/unpacked/samba_4_0_test/source4/setup/ad-schema/MS-AD_Schema_2K8_Classes.txt I'm pretty sure you intend us to just use the same license, but I thought I should check. Cheers, Tridge ___ cifs-protocol mailing list cifs-protocol@cifs.org https://lists.samba.org/mailman/listinfo/cifs-protocol
Re: [cifs-protocol] CAR - ldap display specifiers
You're completely welcome. The notice in the schema is not exactly the same as what is in our current document postings. For the moment, however, the below text is the notice I have been advised should apply. I will ask for additional clarification on this today, since I think it would be *not a good idea* to make any assumptions about, given the textual discrepancies between the below and that provided in the schema. Intellectual Property Rights Notice for Open Specifications Documentation o Technical Documentation. Microsoft publishes Open Specifications documentation for protocols, file formats, languages, standards as well as overviews of the interaction among each of these technologies. o Copyrights. This documentation is covered by Microsoft copyrights. Regardless of any other terms that are contained in the terms of use for the Microsoft website that hosts this documentation, you may make copies of it in order to develop implementations of the technologies described in the Open Specifications and may distribute portions of it in your implementations using these technologies or your documentation as necessary to properly document the implementation. You may also distribute in your implementation, with or without modification, any schema, IDL's, or code samples that are included in the documentation. This permission also applies to any documents that are referenced in the Open Specifications. o No Trade Secrets. Microsoft does not claim any trade secret rights in this documentation. o Patents. Microsoft has patents that may cover your implementations of the technologies described in the Open Specifications. Neither this notice nor Microsoft's delivery of the documentation grants any licenses under those or any other Microsoft patents. However, a given Open Specification may be covered by Microsoft's Open Specification Promise (available here: http://www.microsoft.com/interop/osp) or the Community Promise (available here: http://www.microsoft.com/interop/cp/default.mspx). If you would prefer a written license, or if the technologies described n the Open Specifications are not covered by the Open Specifications Promise or Community Promise, as applicable, patent licenses are available by contacting i...@microsoft.com. o Trademarks. The names of companies and products contained in this documentation may be covered by trademarks or similar intellectual property rights. This notice does not grant any licenses under those rights. Reservation of Rights. All other rights are reserved, and this notice does not grant any rights other than specifically described above, whether by implication, estoppel, or otherwise. o Tools. The Open Specifications do not require the use of Microsoft programming tools or programming environments in order for you to develop an implementation. If you have access to Microsoft programming tools and environments you are free to take advantage of them. Certain Open Specifications are intended for use in conjunction with publicly available standard specifications and network programming art, and assumes that the reader either is familiar with the aforementioned material or has immediate access to it. Regards, Bill Wesse MCSE, MCTS / Senior 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: tri...@samba.org [mailto:tri...@samba.org] Sent: Friday, July 17, 2009 5:39 AM To: Bill Wesse Cc: cifs-proto...@samba.org; m...@samba.org Subject: RE: CAR - ldap display specifiers Hi Bill, Thanks for the LDIF! Can we assume the license on this is the same as for the schema? For the schema the version we got from MS had the license at the top, which you can see here: For the schema license, see this: http://samba.org/ftp/unpacked/samba_4_0_test/source4/setup/ad-schema/MS-AD_Schema_2K8_Classes.txt I'm pretty sure you intend us to just use the same license, but I thought I should check. Cheers, Tridge ___ cifs-protocol mailing list cifs-protocol@cifs.org https://lists.samba.org/mailman/listinfo/cifs-protocol
Re: [cifs-protocol] CAR - ldap display specifiers
Tridge - every out of band release has a unique Intellectual Property notice. So the notice that was included in the schema is unique, and pertains only to the schema release that we provided (it can be obtained on the 'Microsoft Open Specification Support Team Blog' blog at): Using the Windows Server Protocols documentation set to better understand the Active Directory Schema http://blogs.msdn.com/openspecification/archive/2009/06/26/using-the-windows-server-protocols-documentation-set-to-better-understand-the-active-directory-schema.aspx Once document development has detailed the precise nature of the final data we will be supplying, an IP notice will be attached! Regards, Bill Wesse MCSE, MCTS / Senior 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: Bill Wesse Sent: Friday, July 17, 2009 7:18 AM To: 'tri...@samba.org' Cc: cifs-proto...@samba.org; m...@samba.org Subject: RE: CAR - ldap display specifiers You're completely welcome. The notice in the schema is not exactly the same as what is in our current document postings. For the moment, however, the below text is the notice I have been advised should apply. I will ask for additional clarification on this today, since I think it would be *not a good idea* to make any assumptions about, given the textual discrepancies between the below and that provided in the schema. Intellectual Property Rights Notice for Open Specifications Documentation o Technical Documentation. Microsoft publishes Open Specifications documentation for protocols, file formats, languages, standards as well as overviews of the interaction among each of these technologies. o Copyrights. This documentation is covered by Microsoft copyrights. Regardless of any other terms that are contained in the terms of use for the Microsoft website that hosts this documentation, you may make copies of it in order to develop implementations of the technologies described in the Open Specifications and may distribute portions of it in your implementations using these technologies or your documentation as necessary to properly document the implementation. You may also distribute in your implementation, with or without modification, any schema, IDL's, or code samples that are included in the documentation. This permission also applies to any documents that are referenced in the Open Specifications. o No Trade Secrets. Microsoft does not claim any trade secret rights in this documentation. o Patents. Microsoft has patents that may cover your implementations of the technologies described in the Open Specifications. Neither this notice nor Microsoft's delivery of the documentation grants any licenses under those or any other Microsoft patents. However, a given Open Specification may be covered by Microsoft's Open Specification Promise (available here: http://www.microsoft.com/interop/osp) or the Community Promise (available here: http://www.microsoft.com/interop/cp/default.mspx). If you would prefer a written license, or if the technologies described n the Open Specifications are not covered by the Open Specifications Promise or Community Promise, as applicable, patent licenses are available by contacting i...@microsoft.com. o Trademarks. The names of companies and products contained in this documentation may be covered by trademarks or similar intellectual property rights. This notice does not grant any licenses under those rights. Reservation of Rights. All other rights are reserved, and this notice does not grant any rights other than specifically described above, whether by implication, estoppel, or otherwise. o Tools. The Open Specifications do not require the use of Microsoft programming tools or programming environments in order for you to develop an implementation. If you have access to Microsoft programming tools and environments you are free to take advantage of them. Certain Open Specifications are intended for use in conjunction with publicly available standard specifications and network programming art, and assumes that the reader either is familiar with the aforementioned material or has immediate access to it. Regards, Bill Wesse MCSE, MCTS / Senior 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: tri...@samba.org [mailto:tri...@samba.org] Sent: Friday, July 17, 2009 5:39 AM To: Bill Wesse Cc: cifs-proto...@samba.org; m...@samba.org Subject: RE: CAR - ldap display specifiers Hi Bill, Thanks for the LDIF! Can we assume the license on this is the same as for the schema? For the schema the version we got from MS had the license at the top, which you can see here: For the schema license, see this: http://samba.org/ftp/unpacked/samba_4_0_test/sour
Re: [cifs-protocol] CAR - ldap display specifiers
On Fri, 2009-07-17 at 07:38 -0700, Bill Wesse wrote: > Tridge - every out of band release has a unique Intellectual Property > notice. So the notice that was included in the schema is unique, and > pertains only to the schema release that we provided (it can be > obtained on the 'Microsoft Open Specification Support Team Blog' blog > at): > > Using the Windows Server Protocols documentation set to better understand the > Active Directory Schema > http://blogs.msdn.com/openspecification/archive/2009/06/26/using-the-windows-server-protocols-documentation-set-to-better-understand-the-active-directory-schema.aspx > > Once document development has detailed the precise nature of the final data > we will be supplying, an IP notice will be attached! I'm confused. What is the copyright licence applicable to the contents of the zip file you just mailed? Andrew Bartlett -- Andrew Bartlett http://samba.org/~abartlet/ Authentication Developer, Samba Team http://samba.org Samba Developer, Cisco Inc. signature.asc Description: This is a digitally signed message part ___ cifs-protocol mailing list cifs-protocol@cifs.org https://lists.samba.org/mailman/listinfo/cifs-protocol
Re: [cifs-protocol] CAR - ldap display specifiers
On Mon, 2009-07-20 at 18:15 +1000, Andrew Bartlett wrote: > On Fri, 2009-07-17 at 07:38 -0700, Bill Wesse wrote: > > Tridge - every out of band release has a unique Intellectual Property > > notice. So the notice that was included in the schema is unique, and > > pertains only to the schema release that we provided (it can be > > obtained on the 'Microsoft Open Specification Support Team Blog' blog > > at): > > > > Using the Windows Server Protocols documentation set to better understand > > the Active Directory Schema > > http://blogs.msdn.com/openspecification/archive/2009/06/26/using-the-windows-server-protocols-documentation-set-to-better-understand-the-active-directory-schema.aspx > > > > Once document development has detailed the precise nature of the final data > > we will be supplying, an IP notice will be attached! > > I'm confused. What is the copyright licence applicable to the contents > of the zip file you just mailed? Also, if it is the licence you posted earlier in this thread, is this considered 'schema'? (Given we need to incorporate the whole file, I need it to fall under the exception to the 'portions of' rule). Thanks, Andrew Bartlett -- Andrew Bartlett http://samba.org/~abartlet/ Authentication Developer, Samba Team http://samba.org Samba Developer, Cisco Inc. signature.asc Description: This is a digitally signed message part ___ cifs-protocol mailing list cifs-protocol@cifs.org https://lists.samba.org/mailman/listinfo/cifs-protocol
Re: [cifs-protocol] CAR - ldap display specifiers
Good morning Andrew! There is no copyright license for the attachments - yet; nevertheless, I expect the below text - or something like it - to apply. I cannot guarantee there will be no changes between now and when the CAR request is fulfilled. I certainly expect this will not take as long as it did with the schema. Intellectual Property Rights Notice for Open Specifications Documentation o Technical Documentation. Microsoft publishes Open Specifications documentation for protocols, file formats, languages, standards as well as overviews of the interaction among each of these technologies. o Copyrights. This documentation is covered by Microsoft copyrights. Regardless of any other terms that are contained in the terms of use for the Microsoft website that hosts this documentation, you may make copies of it in order to develop implementations of the technologies described in the Open Specifications and may distribute portions of it in your implementations using these technologies or your documentation as necessary to properly document the implementation. You may also distribute in your implementation, with or without modification, any schema, IDL's, or code samples that are included in the documentation. This permission also applies to any documents that are referenced in the Open Specifications. o No Trade Secrets. Microsoft does not claim any trade secret rights in this documentation. o Patents. Microsoft has patents that may cover your implementations of the technologies described in the Open Specifications. Neither this notice nor Microsoft's delivery of the documentation grants any licenses under those or any other Microsoft patents. However, a given Open Specification may be covered by Microsoft's Open Specification Promise (available here: http://www.microsoft.com/interop/osp) or the Community Promise (available here: http://www.microsoft.com/interop/cp/default.mspx). If you would prefer a written license, or if the technologies described n the Open Specifications are not covered by the Open Specifications Promise or Community Promise, as applicable, patent licenses are available by contacting i...@microsoft.com. o Trademarks. The names of companies and products contained in this documentation may be covered by trademarks or similar intellectual property rights. This notice does not grant any licenses under those rights. Reservation of Rights. All other rights are reserved, and this notice does not grant any rights other than specifically described above, whether by implication, estoppel, or otherwise. o Tools. The Open Specifications do not require the use of Microsoft programming tools or programming environments in order for you to develop an implementation. If you have access to Microsoft programming tools and environments you are free to take advantage of them. Certain Open Specifications are intended for use in conjunction with publicly available standard specifications and network programming art, and assumes that the reader either is familiar with the aforementioned material or has immediate access to it. Regards, Bill Wesse MCSE, MCTS / Senior 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: Andrew Bartlett [mailto:abart...@samba.org] Sent: Monday, July 20, 2009 7:15 AM To: Bill Wesse Cc: tri...@samba.org; m...@samba.org; cifs-proto...@samba.org Subject: Re: [cifs-protocol] CAR - ldap display specifiers On Mon, 2009-07-20 at 18:15 +1000, Andrew Bartlett wrote: > On Fri, 2009-07-17 at 07:38 -0700, Bill Wesse wrote: > > Tridge - every out of band release has a unique Intellectual > > Property notice. So the notice that was included in the schema is > > unique, and pertains only to the schema release that we provided (it > > can be obtained on the 'Microsoft Open Specification Support Team > > Blog' blog > > at): > > > > Using the Windows Server Protocols documentation set to better > > understand the Active Directory Schema > > http://blogs.msdn.com/openspecification/archive/2009/06/26/using-the > > -windows-server-protocols-documentation-set-to-better-understand-the > > -active-directory-schema.aspx > > > > Once document development has detailed the precise nature of the final data > > we will be supplying, an IP notice will be attached! > > I'm confused. What is the copyright licence applicable to the > contents of the zip file you just mailed? Also, if it is the licence you posted earlier in this thread, is this considered 'schema'? (Given we need to incorporate the whole file, I need it to fall under the exception to the 'portions of' rule). Thanks, Andrew Bartlett -- Andrew Bartlett http://samba.org/~abartlet/ Authentication Deve
Re: [cifs-protocol] CAR - ldap display specifiers
On Mon, 2009-07-20 at 06:30 -0700, Bill Wesse wrote: > Good morning Andrew! > > There is no copyright license for the attachments - yet; nevertheless, I > expect the below text - or something like it - to apply. Bill, Honestly, this really isn't very useful. I can search against an AD server as well as you can, as can the users who have been bugging me to include into Samba the results of their own searches. What we are asking for is this kind of output, but under a the previously agreed licence, with the output defined as 'schema' (ie, falling clearly under the inclusion exception). I think what we need is to get a procedure in place whereby we can get this kind of thing released under a licence that works for both the PFIF and Microsoft. In particular it needs single licence, preferably the one we have on the schema. In particular it really does need not to be unique per release - each new text has to be cleared by multiple Linux vendors. I'm sure we can work something out. Thanks, Andrew Bartlett -- Andrew Bartlett http://samba.org/~abartlet/ Authentication Developer, Samba Team http://samba.org Samba Developer, Cisco Inc. signature.asc Description: This is a digitally signed message part ___ cifs-protocol mailing list cifs-protocol@cifs.org https://lists.samba.org/mailman/listinfo/cifs-protocol
Re: [cifs-protocol] CAR - ldap display specifiers (SRX090713600122)
Good morning once again Andrew. Our document development folks (for [MS-ADTS], [MS-ADSC] & [MS-ADA(1,2,3)]) are currently working on ldif dumps for Windows 2000 and beyond; these, of course will omit domain specific information and replication metadata. We will provide these as soon as possible, along with licensing information, of course. I have forwarded your comments to those involved in that. Regards, Bill Wesse MCSE, MCTS / Senior 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: Andrew Bartlett [mailto:abart...@samba.org] Sent: Tuesday, July 21, 2009 2:57 AM To: Bill Wesse Cc: m...@samba.org; cifs-proto...@samba.org Subject: Re: [cifs-protocol] CAR - ldap display specifiers On Mon, 2009-07-20 at 06:30 -0700, Bill Wesse wrote: > Good morning Andrew! > > There is no copyright license for the attachments - yet; nevertheless, I > expect the below text - or something like it - to apply. Bill, Honestly, this really isn't very useful. I can search against an AD server as well as you can, as can the users who have been bugging me to include into Samba the results of their own searches. What we are asking for is this kind of output, but under a the previously agreed licence, with the output defined as 'schema' (ie, falling clearly under the inclusion exception). I think what we need is to get a procedure in place whereby we can get this kind of thing released under a licence that works for both the PFIF and Microsoft. In particular it needs single licence, preferably the one we have on the schema. In particular it really does need not to be unique per release - each new text has to be cleared by multiple Linux vendors. I'm sure we can work something out. Thanks, Andrew Bartlett -- Andrew Bartlett http://samba.org/~abartlet/ Authentication Developer, Samba Team http://samba.org Samba Developer, Cisco Inc. ___ cifs-protocol mailing list cifs-protocol@cifs.org https://lists.samba.org/mailman/listinfo/cifs-protocol
Re: [cifs-protocol] CAR - ldap display specifiers (SRX090713600122)
Good morning again - just touching bases with you concerning the ldif dumps for the display specifiers. The ldf files have been generated, and work on the licensing agreement is in progress. As soon as we have, I will provide the ldf content to you. Here is a list of covered versions (by platform): Windows 2000 Windows 2003 Windows 2003R2 Windows 2008 Windows 2008R2 Public posting locations are still to be determined, but I do expect clearance to make them (unofficially) available on our blog, similar to where we have posted the previous schema content: Using the Windows Server Protocols documentation set to better understand the Active Directory Schema http://blogs.msdn.com/openspecification/archive/2009/06/26/using-the-windows-server-protocols-documentation-set-to-better-understand-the-active-directory-schema.aspx Thanks again for your patience! Regards, Bill Wesse MCSE, MCTS / Senior 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: Bill Wesse Sent: Tuesday, July 21, 2009 11:43 AM To: 'Andrew Bartlett' Cc: m...@samba.org; cifs-proto...@samba.org; 'tri...@samba.org' Subject: RE: [cifs-protocol] CAR - ldap display specifiers (SRX090713600122) Good morning once again Andrew. Our document development folks (for [MS-ADTS], [MS-ADSC] & [MS-ADA(1,2,3)]) are currently working on ldif dumps for Windows 2000 and beyond; these, of course will omit domain specific information and replication metadata. We will provide these as soon as possible, along with licensing information, of course. I have forwarded your comments to those involved in that. Regards, Bill Wesse MCSE, MCTS / Senior 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: Andrew Bartlett [mailto:abart...@samba.org] Sent: Tuesday, July 21, 2009 2:57 AM To: Bill Wesse Cc: m...@samba.org; cifs-proto...@samba.org Subject: Re: [cifs-protocol] CAR - ldap display specifiers On Mon, 2009-07-20 at 06:30 -0700, Bill Wesse wrote: > Good morning Andrew! > > There is no copyright license for the attachments - yet; nevertheless, I > expect the below text - or something like it - to apply. Bill, Honestly, this really isn't very useful. I can search against an AD server as well as you can, as can the users who have been bugging me to include into Samba the results of their own searches. What we are asking for is this kind of output, but under a the previously agreed licence, with the output defined as 'schema' (ie, falling clearly under the inclusion exception). I think what we need is to get a procedure in place whereby we can get this kind of thing released under a licence that works for both the PFIF and Microsoft. In particular it needs single licence, preferably the one we have on the schema. In particular it really does need not to be unique per release - each new text has to be cleared by multiple Linux vendors. I'm sure we can work something out. Thanks, Andrew Bartlett -- Andrew Bartlett http://samba.org/~abartlet/ Authentication Developer, Samba Team http://samba.org Samba Developer, Cisco Inc. ___ cifs-protocol mailing list cifs-protocol@cifs.org https://lists.samba.org/mailman/listinfo/cifs-protocol
Re: [cifs-protocol] CAR - ldap display specifiers (SRX090713600122)
On Fri, 2009-07-24 at 06:38 -0700, Bill Wesse wrote: > Good morning again - just touching bases with you concerning the ldif dumps > for the display specifiers. > > The ldf files have been generated, and work on the licensing agreement is in > progress. As soon as we have, I will provide the ldf content to you. Here is > a list of covered versions (by platform): This is all taking rather a long time, and is blocking us releasing the next Samba4 alpha. Can you please provide us with an ETA on the ldif dumps? Should we expect this to take just as long as the schema issue to resolve? Thanks, Andrew Bartlett -- Andrew Bartlett http://samba.org/~abartlet/ Authentication Developer, Samba Team http://samba.org Samba Developer, Cisco Inc. signature.asc Description: This is a digitally signed message part ___ cifs-protocol mailing list cifs-protocol@cifs.org https://lists.samba.org/mailman/listinfo/cifs-protocol
