2.2.1 Common Conventions
All paths in REQ_GET_DFS_REFERRAL and RESP_GET_DFS_REFERRAL messages MUST be encoded with exactly one leading backslash, not two leading backslashes as is common to user-visible UNC paths. For example, the UNC path "\\server\namespace\directory\subdirectory\file" would be encoded as "\server\namespace\directory\subdirectory\file".
All strings in REQ_GET_DFS_REFERRAL (section 2.2.2) and RESP_GET_DFS_REFERRAL (section 2.2.4) messages MUST be encoded as null-terminated strings of UTF-16 characters, as specified in [UNICODE]. Constructs of the form "<value>" in strings are placeholders to be replaced with client or server-specified values. For example, the string description "\<domain>\<namespace>" would take the form "\contoso\templates" when populated with the values "contoso" for the <domain> placeholder and "templates" for the <namespace> placeholder.
All 16-bit and 32-bit integers in REQ_GET_DFS_REFERRAL and RESP_GET_DFS_REFERRAL messages MUST be encoded as unsigned little-endian values.