[cifs-protocol] 115102913315679 [MS-ADTS] 220.127.116.11.2.2.1 Subnet Object address range
srenaden at microsoft.com
Thu Oct 29 00:21:58 UTC 2015
Dochelp in Bcc
Casemail in Cc
Thank you for your inquiry about MS-ADTS specification. We have created incident 115102913315679 for investigating this issue. One of the Open specifications team member will contact you shortly.
Microsoft Windows Open specifications
From: Douglas Bagnall [mailto:douglas.bagnall at catalyst.net.nz]
Sent: Wednesday, October 28, 2015 5:48 PM
To: Interoperability Documentation Help
Cc: cifs-protocol at lists.samba.org
Subject: MS-ADTS 18.104.22.168.2.2.1 Subnet Object address range
I just wish to clarify my interpretation of MS-ADTS 22.214.171.124.2.2.1 (v20150630).
According to that document (and a small amount of testing against Windows 2012), a subnet IP range can't start with a leading zero. But with IPv6 it is possible create subnets with implicit leading zeros.
For example, "::ff00/120" and "0::ff00/120" refer to the same address range, but only the latter is forbidden. (right?)
Can I thus infer that no attempt is made to canonicalise an IPv6 subnet name, and collisions are only avoided by DN uniqueness? That is, could I simultaneously have subnets called "2001:DA8::/48" and "2001:DA8:0::/48" which evaluate to the same address range?
Also (as I understand point 6) it says the address part of an IPv4 CIDR can't exactly equal the implied mask. For example, "255.128.0.0/9" is not allowed because the "/9" implies a mask of "255.128.0.0". Just for clarity can you confirm that there is no analogous constraint on IPv6?
More information about the cifs-protocol