4.5 Peer A Session Factory Service Activation Received by Peer B, Responds with Session Activation

When Peer A's valid Session Factory Service Activation message (section 2.2.12) is received by Peer B, it responds by launching the Adventure Works App, creating a Session Factory object, creating a Session object (section 3.1.1.4), and replying with a Session Activation message (section 2.2.11) on the received ReplyChannelID, which is the SessionFactoryID of Peer A's Session Factory object (section 3.1.1.3) for the Adventure Works application: "Windows.bDMWicFcpEs". Length is equal to 96 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

SourceID (the SourceID of Peer B's NfpService) =

0xF3, 0x88, 0xC0, 0x6B

0xE9, 0xCF, 0xD4, 0xDE

...

ActivatedSessionFactoryID (newly created Session Factory object's SessionFactoryID) =

0x40, 0xCA, 0xDB, 0x31

0x50, 0x96, 0xD8, 0x32

...

ReplyChannelID (newly created Session object's SessionID) = "rhlJshr/7Ew"

0xAE, 0x19, 0x49, 0xB2

0x1A, 0xFF, 0xEC, 0x4C

...

ECDHPublicKeyMagicNumber = 0x45, 0x43, 0x4B, 0x31

ECDHPublicKeyLength (little-endian) = 0x20, 0x00, 0x00, 0x00

ECDHXParam

ECDHYParam