4.1 Transport Activation and Initial Service Descriptor

When the underlying transport is activated, the protocol begins transmitting. Peer A begins by publishing its pre-initialized Service Descriptor message (section 2.2.8) on the well-known channel: "Windows.windows.com/SD". Length = 56 bytes.


0


1


2


3


4


5


6


7


8


9

1
0


1


2


3


4


5


6


7


8


9

2
0


1


2


3


4


5


6


7


8


9

3
0


1

ActivationChannelID (the SourceID of Peer A's NfpService) =

0x80, 0x29, 0x84, 0xF4

0xD6, 0x0E, 0x8D, 0x2B

0xD6, 0x0E, 0x8D, 0x2B

0x80, 0x29, 0x84, 0xF4

...

OOB Connector ServiceActivationUUID = {E46EDA50-9B5D-41F1-B89E-327B5EA38B16}

0x50, 0xDA, 0x6E, 0xE4

0x5D, 0x9B, 0xF1, 0x41

0xB8, 0x9E, 0x32, 0x7B

0x5E, 0xA3, 0x8B, 0x16

...

...

ExtendedInfo1 = 0x00, 0x00

ServiceVersion = 0x00, 0x01

ExtendedInfo2 = 0x00, 0x00

ExtendedPayloadLength = 0x00, 0x00

Session Factory ServiceActivationUUID: {F1DEBC56-CFBA-4129-983B-7D79499D1A7D}

0x56, 0xBC, 0xDE, 0xF1

0xBA, 0xCF, 0x29, 0x41

0x98, 0x3B, 0x7D, 0x79

0x49, 0x9D, 0x1A, 0x7D

...

...

ExtendedInfo1 = 0x00, 0x00

ServiceVersion = 0x00, 0x01

ExtendedInfo2 = 0x00, 0x00

ExtendedPayloadLength = 0x00, 0x00