Administrative Domain Reqest Interface access interface Response Interface

Administrative Domain Reqest Interface (access interface) Response Interface (inter-domain interface) Request. Controller AAA Charact eristic parser PMC database Tool check Schedu le check PMC controller Remote check Distribu tor Inter-domain controller

Request. Interface – input message <in 0> Normally the client would specify either a characteristic or a (set of) tools, and the tools <characteristic would be filled out by the domain interfaces name=“network. delay. roundtrip”/> Tools to use, ranked in <tool name=“ping” rank=“ 1”/> order of preference <tool name=“pingmon” rank=“ 3”/> <source host=“a. b. c. d”/> Source and sink hosts <sink host=“e. f. g. h”/> A time specification <when now=“true”/> for authorisation and <credential>…</credential> Credentials authentication. This is an any. Type </in 0> element, for extensibility

Request. Interface – output message <out 0> <location xsi: type=“SQLQuery”> <host>foo. bar</host> <query>SELECT * FROM measurements WHERE id=myuniqueid</query> </location> </out 0> The location is of type any. Type, so any sort of reference can be put in here (this SQLQuery is just an example)

Request. Interface - faults • Faults are used to indicate failures. <Blah. Exception> <message>Gone wrong</message> further information for some faults </Blah. Exception> • • Tool. Unavailable. Exception Characteristic. Unavailable. Exception Time. Unavailable. Exception Malformed. Request. Exception

Response. Interface • Takes a Measurement. Request • Returns a Measurement. Request or one of the faults • Both interfaces may add new source/sink elements: – <source host=“i. b. c. d” type=“pmc”/> – <sink host=“j. f. g. h” type=“pmc”/> • Either may remove tool elements • Either may add credentials

More Information • See http: //www. hep. ucl. ac. uk/~pdm/e 2 epipes/d omain. html