<d:Scopes> ldap:///ou=engineering,o=examplecom,c=us ldap:///ou=floor1,ou=b42,ou=anytown,o=examplecom,c=us http://itdept/imaging/deployment/2004-12-04 </d:Scopes> <d:MetadataVersion>75965</d:MetadataVersion> </d:ProbeMatch> <d:ProbeMatch> <a:EndpointReference> <a:Address> urn:uuid:70eda11c-200a-4a5e-b60e-d6793e77ace3 </a:Address> </a:EndpointReference> <d:Scopes> ldap:///ou=engineering,o=examplecom,c=us ldap:///ou=floor1,ou=b42,ou=anytown,o=examplecom,c=us http://itdept/imaging/deployment/2008-10-16 </d:Scopes> <d:XAddrs>http://prn-example/PRN42/b42-1668-b</d:XAddrs> <d:MetadataVersion>23654</d:MetadataVersion> </d:ProbeMatch> </d:ProbeMatches> </s:Body> </s:Envelope> Lines (07-09) in Table 11 indicate this message is a Probe Match; and Lines (13-15) indicate that it is a response to the Probe message in Table 10. Since this Probe Match message was sent over HTTP in response to the Probe message and since messages sent over HTTP are received in the order they are sent, it does not contain a header that identifies the instance number and message number like Line (19) in Table 2. Lines (20-32) describe a Target Service and they are identical to the corresponding lines (24-36) in Table 2. Lines (35-47) describe another Target Service, a basic printer service; that match the Probe in Table 10.
<d:Scopes> ldap:///ou=engineering,o=examplecom,c=us ldap:///ou=floor1,ou=b42,ou=anytown,o=examplecom,c=us http://itdept/imaging/deployment/2004-12-04 </d:Scopes> <d:MetadataVersion>75965</d:MetadataVersion> </d:ProbeMatch> <d:ProbeMatch> <a:EndpointReference> <a:Address> urn:uuid:70eda11c-200a-4a5e-b60e-d6793e77ace3 </a:Address> </a:EndpointReference> <d:Scopes> ldap:///ou=engineering,o=examplecom,c=us ldap:///ou=floor1,ou=b42,ou=anytown,o=examplecom,c=us http://itdept/imaging/deployment/2008-10-16 </d:Scopes> <d:XAddrs>http://prn-example/PRN42/b42-1668-b</d:XAddrs> <d:MetadataVersion>23654</d:MetadataVersion> </d:ProbeMatch> </d:ProbeMatches> </s:Body> </s:Envelope> Lines (07-09) in Table 11 indicate this message is a Probe Match; and Lines (13-15) indicate that it is a response to the Probe message in Table 10. Since this Probe Match message was sent over HTTP in response to the Probe message and since messages sent over HTTP are received in the order they are sent, it does not contain a header that identifies the instance number and message number like Line (19) in Table 2. Lines (20-32) describe a Target Service and they are identical to the corresponding lines (24-36) in Table 2. Lines (35-47) describe another Target Service, a basic printer service; that match the Probe in Table 10.