.msrcincident format with ipv6 addresses

Question

We generate a incident ticket using GetNoviceUserInfo and then parsing the resulting connection string into a msrcincident file format. How should ipv6 addresses be formatted in the file? Right now we have something like this:

RCTICKET="65538,1,fexx::xxxx:97f1:4061:504b%11:55017;fexx::xxxx:10.105.xx.xx%18:55018;20xx:dead:c01d:beef:0:xxxx:10.105.xx.xx:55019;20xx:db8::xxxx:e1d3:8300:xxxx:55020;10.105.xx.xx:55021,

This obviously fails because the colons of the IPv6 adresses conflict with the IP:PORT interpretation. So how do we format it?

Answer 1

Hi pichkoo,
                Thank you for your inquiry about MS-RAI protocol. One of the Open specifications team member will contact you shortly.
 
Regards,
Sreekanth Nadendla
Microsoft Windows Open specifications

Answer 2

Hi,

I will investigate this and follow-up.

Thanks,

Edgar

Answer 3

I may be wrong - but I think there is a new format for tickets which uses xml and works fine for IPv6.

"2.2.2 Remote Assistance Connection String 2"

http://msdn.microsoft.com/en-us/library/cc240132%28v=prot.20%29.aspx

<E>
    <A KH="YiKwWUY8Ioq5NB3wAQHSbs5kwrM=" ID="8rYm30RBW8/4dAWoUsWbFCF5jno/7jr5t
NpHQc2goLbw4uuBBJvLsU02YYLlBMg5"/>
    <C>
        <T ID="1" SID="1440550163">
            <L P="49749" N="2001:4898:1a:5:79e2:3356:9b22:3470"/>
            <L P="49751" N="172.31.250.64"/>
        </T>
    </C>
</E> 

Answer 4

I came across this but just dumping the connection string into a .msrincident file in this format does not work. Windows Remote Assistance expects the ticket to be in a certain format (like having LHTICKET,RCTICKET,UPLOADED, etc attributes).  

Answer 5

Hi guys, is there any update on this? To clarify the question I need to create RA tickets programmatically which will work in both ipv4/6 environments. I have mentioned my previous approach above where I just generate RCTICKET variable from RA Connection String 2. The RCTICKET variable does not seem to accept ipv6 addresses in any format I tried(square brackets, semicolon). 

Answer 6

The Connection String 2 can include IPv6 and IPv4 addresses. The Encrypted RA Connection String 2 is hex format is transported as LHTICKET attribute of the MSRcincident file (see Product behavior notes <18> and <19>).

The format of the RA Connection String 2 is documented in Section 2.2.2.

2.2.2 Remote Assistance Connection String 2

http://msdn.microsoft.com/en-us/library/cc240132.aspx

Connection String 1 can only have IPv4 address. Connection String 1 is specific to Windows XP and Windows 2003.

2.2.1 Remote Assistance Connection String 1

http://msdn.microsoft.com/en-us/library/cc240131.aspx

6 Appendix A: Remote Assistance Invitation File Format

http://msdn.microsoft.com/en-us/library/cc240167.aspx

See description of the format and fields of MSRcincident of second type:

Following is a sample Remote Assistance Invitation File of the second type:<17>

For RA Invitation file of second type, the UPLOADDATA contains the LHTICKET and RCTICKET attributes.

The RCTICKET attribute can be present for compatibility with Windows XP and Windows 2003.

LHTICKET: The encrypted Remote Assistance Connection String 2 where each byte is converted to two HEX numbers<18>

RCTICKET: The version-specific<19>Remote Assistance Connection String.

<17> Section 6: This type is specific to Windows Vista, Windows Server 2008, Windows 7, Windows Server 2008 R2, Windows 8, and Windows Server 2012.

<18> Section 6: In Windows Vista, Windows Server 2008, Windows 7, Windows Server 2008 R2, Windows 8, and Windows Server 2012, the password is mandatory and it is encrypted using the MS_ENH_RSA_AES_PROV predefined Cryptographic provider with CALG_SHA hashing and the CALG_AES_128 encryption algorithm. The cipher mode used can be CRYPT_MODE_CBC and the password used during the encryption process is a Unicode string.

Following is the password encryption flow diagram in the case of Windows Vista, Windows Server 2008, Windows 7, Windows Server 2008 R2, Windows 8, and Windows Server 2012:

<19> Section 6: This attribute can be present for Windows XP and Windows Server 2003 compatibility.

Answer 7

Right, thanks for the help!

Answer 8

Thanks, it is very useful...but can anyone show some code about how to convert connectionstring to Remote Assistance Invitation File ?

Answer 9

Hello Palim_z,
The purpose of this forum is to support only the Open Specifications documentation. You can read about the Microsoft Open Specifications program from http://www.microsoft.com/openspecifications/en/us/default.aspx.
The library of Open Specification documents can be accessed from http://msdn.microsoft.com/en-us/library/dd208104(PROT.10).aspx.

There is no draft implementation of Open Specifications to provide code samples for the protocols.

If you are reading and implementing the Remote Assistance specifications and have a question about those documents, you may start a separate thread citing the sections and details.

Regards,
Sreekanth Nadendla
Microsoft Windows Open Specifications