1 / 20

Network Measurements Working Group

Network Measurements Working Group. Summary of the Work on "new" Schemata Richard Hughes-Jones Main Contributors: Dan Gunter, Martin Swany, Jason Zurawski NM-WG GGF13 Seoul. Introduction: The Hierarchy Document.

Download Presentation

Network Measurements Working Group

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Network Measurements Working Group Summary of the Work on "new" Schemata Richard Hughes-Jones Main Contributors: Dan Gunter, Martin Swany, Jason Zurawski NM-WG GGF13 Seoul NMWG GGF13 Seoul March 2005 R. Hughes-Jones Manchester

  2. Introduction: The Hierarchy Document • “A Hierarchy of Network Performance Characteristics for Grid Applications and Services” • Document defines terms & relations: • Network characteristics • Measurement methodologies • Observation • Nodes & Paths • Defines the meanings • Discusses the use & relations • For each Characteristic • Defines the meaning • Stated the attributes that SHOULD be included • Discusses the issues to consider when making an observation • GGF Proposed Recommendation GFD-R.023 www.gridforum.org/documents/GWD-R/GFD-R.023.pdf NMWG GGF13 Seoul March 2005 R. Hughes-Jones Manchester

  3. Schemata: Overview • NM-WG then focused on standardizing schemas for exchanging network measurements • Extended concept to • Requesting historical network measurements • Requesting measurements to be made on demand • NM-WG has Two sets of schemata: • v.1::Monolithic, straight mapping of “characteristics” doc (Mark’s talk) • v.2::Framework: • Base schema - common components, types, topology • Add separate sub-schema for each characteristic and/or tool • Separation of Metadata & Network information • Framework has extensibility to just about anything  • Schema language: Relax-NG compact syntax NMWG GGF13 Seoul March 2005 R. Hughes-Jones Manchester

  4. Version 2 Schemas: Recap [1] • Request: • Just has a metadata section - containers for: • characteristic – namespace required(e.g. http://www.ggf.org/nmwg/iperf) • subject (e.g. host pair) • parameters appropriate either for making a test or filtering historic data (e.g. TTL, TCP buffer size …) • Time/date (of required observation) Time is a range Other parameters are specified or implied * NMWG GGF13 Seoul March 2005 R. Hughes-Jones Manchester

  5. Version2 Schemas: Recap [2] • Response: • metadata: <same as Request> • These are the “conditions” / parameters / tool used for the test. • Parameters could be • The same parameters and values as in the Request • Same parameters but values modified • Additional Parameter-value tuples • data: • <Content depends on the characteristic> Anything in xml eg bin64 encoded (but don’t expect to be sending binary) Could include a reference to other sources of data NMWG GGF13 Seoul March 2005 R. Hughes-Jones Manchester

  6. NM-WG V2 Schemas: 8 Easy Examples !! With thanks to Dan Gunter • Request • Base request example • traceroute request example • Base request schema • Traceroute request schema • Response example • Base response • traceroute example • Base response schema • traceroute schema • Color-coded: base ; traceroute NMWG GGF13 Seoul March 2005 R. Hughes-Jones Manchester

  7. 1. Base Request Example <nmwg:request xmlns:nmwg="http://www.ggf.org/nmwg/"> <metadata id="M001"> <subject id="S001"> </subject> <parameters> </parameters> </metadata> </nmwg:request> Details go here Details go here NMWG GGF13 Seoul March 2005 R. Hughes-Jones Manchester

  8. 2. Traceroute Request Example Base Namespace Namespace specifies traceroute Characteristicelements will have :tr <nmwg:request xmlns:nmwg="http://www.ggf.org/nmwg/" xmlns:tr= “ http://www.ggf.org/nmwg/characteristics/traceroute/ "> <tr:metadata id="M001"> <tr:subject id="S001"> <nmwg:hostPairQuery> <src type="ipv4"> 131.243.243.21 </src> <dst type="hostnameWildcard"> *.udel.edu </dst> </nmwg:hostPairQuery> </tr:subject> <tr:parameters id="P001"> <maxttl> 32 </maxttl> <nqueries> 3 </nqueries> <waittime> 5 </waittime> </tr:parameters> </tr:metadata> </nmwg:request> details NMWG GGF13 Seoul March 2005 R. Hughes-Jones Manchester

  9. 3. Base Request Schema default namespace =http://www.ggf.org/nmwg/ Request = element metadata { Metadata }* Metadata = attribute id { xsd:string } Subject = attribute id { xsd:string } Parameters = attribute id { xsd:string } HostPairQuery = element hostPairQuery { element src { EndpointPattern }, element dst { EndpointPattern } } EndpointPattern = attribute type { token }, element address { string }, element port { xsd:int }? Extend these three elements NMWG GGF13 Seoul March 2005 R. Hughes-Jones Manchester

  10. 4. Traceroute Request Schema namespace tr = http://www.ggf.org/nmwg/characteristics/traceroute namespace nmwg =http://www.ggf.org/nmwg/ import “nmwg-base-schema.rnc” Request = element tr:metadata { Metadata }* TrMetadata =nmwg:Metadata & element tr:subject { TrSubject } element tr:parameters { TrParameters } TrSubject = nmwg:Subject & ( nmwg:HostPair | nmwg:HostPairQuery ) TrParameters = nmwg:Parameters & ( element maxttl { xsd:int }? & element nqueries { xsd:int }? & element waittime { xsd:int }? ) Extended for traceroute NMWG GGF13 Seoul March 2005 R. Hughes-Jones Manchester

  11. 5. Base Response Example <nmwg:response xmlns:nmwg="http://www.ggf.org/nmwg/"> <metadata id="M001"> </metadata> <data> <timestamp>2005-03-13T00:00:00</timestamp> <results> </results> </nmwg:response> Metadata Details go here Added timestamp Results Details go here NMWG GGF13 Seoul March 2005 R. Hughes-Jones Manchester

  12. 6. Traceroute Response Example [1] Metadata <nmwg:response xmlns:nmwg="http://www.ggf.org/nmwg/" xmlns:tr= "http://www.ggf.org/nmwg/characteristics/traceroute/ "> <tr:metadata id="M001"> <tr:subject id="S001"> <nmwg:hostPairQuery> <src type="ipv4"> 131.243.243.21 </src> <dst type="hostname"> huey.udel.edu </dst> </nmwg:hostPairQuery> </tr:subject> <tr:parameters id="trp2"> <tr:maxttl> 30 </tr:maxttl> <tr:nqueries> 3 </tr:nqueries> <tr:dontFragment> 0 </tr:dontFragment> <tr:mode> UDP </tr:mode> </tr:parameters> </tr:metadata> wildcard becomes actual hostname modified added NMWG GGF13 Seoul March 2005 R. Hughes-Jones Manchester

  13. 6. Traceroute Response Example [2] Results probe = setting of the ttl query = observation at a given ttl <tr:data> <nmwg:time> 2005-03-13T00:00:00 </time> <results> <tr:probe num='1'> <query num='1'> <hopValue> ir100gw-r2 </hopValue> <value> 0.233 </value> </query> query num='2' … <query num=‘3'> <hopValue> ir100gw-r2 </hopValue> <value> 0.218 </value> </query> </tr:probe> <tr:probe num=‘2'> etc. … </results> <tr:data> </nmwg:response> NMWG GGF13 Seoul March 2005 R. Hughes-Jones Manchester

  14. 7. Base Response Schema default namespace = http://www.ggf.org/nmwg/ Response = ( element metadata { Metadata } | element data { Data } )* Metadata = attribute id { xsd:string } Subject = attribute id { xsd:string } Parameters = attribute id { xsd:string } Data = attribute id { Identifier }, attribute metadataId { Identifier }, element time { Time }?, element units { token }?, Extend these three elements Data Details go here NMWG GGF13 Seoul March 2005 R. Hughes-Jones Manchester

  15. 8. Traceroute Response Schema [1] namespace tr = http://www.ggf.org/nmwg/characteristics/traceroute namespace nmwg = http://www.ggf.org/nmwg/ import “nmwg-base-schema.rnc” Response = element tr: (metadata { Metadata } | element tr:data { TrData } )* TrMetadata =nmwg:Metadata& element tr:subject { TrSubject } element tr:parameters { TrParameters } TrSubject = nmwg:Subject & ( nmwg:HostPair | nmwg:HostPairQuery ) TrParameters = nmwg:Parameters & ( element maxttl { xsd:int }? & element nqueries { xsd:int }? & element waittime { xsd:int }? & element dontFragment {xsd:bool}? & element mode { token }? ) NMWG GGF13 Seoul March 2005 R. Hughes-Jones Manchester

  16. 8. Traceroute Response Schema [2] TrData = nmwg:Data & element tr:probe { attribute num { xsd:int }, element query { attribute num { xsd:int }, element hopValue { nmwg:Endpoint }, element rtt { xsd:float } } }+ traceroute details NMWG GGF13 Seoul March 2005 R. Hughes-Jones Manchester

  17. The Developer's Guide (only V2 Schemata) • Draft Document (version 1) GGF-NMWG-03-I Nov 2004 • Finish the descriptive examples. • Provide notes & a “toolkit” to aid other network monitor developers to add NM-WG capability. • Toolkit will give reference implementations. i.e. language+ schemas in some tooling – simply this code makes the web service DAN • Perl (Internet2) • Python (Dan) • Java (Dante, Europe Grid) • .net (large market – need assistance here) • WS-RF integration needs discussion & work • Advertising capability (feature negotiation, etc.) • Security – permission to run test / access historic data (NESC Strategy doc “Web service grids an Evolutionary Approach”) NMWG GGF13 Seoul March 2005 R. Hughes-Jones Manchester

  18. Where are we now with V2 Schemata? • v.2 base schema has been around for a while • Sub-schema for common characteristics/tools: • iperf, ping, traceroute • With extensibility to just about anything • Need implementor feedback • Working on the developer's guide to smooth transition and help with Web Svcs details • not yet published, but v.0.1 is availableon our new web site: http://nmwg.internet2.edu/devguide.pdf • A draft “How-to write your own schema” by Dan Gunter NMWG GGF13 Seoul March 2005 R. Hughes-Jones Manchester

  19. Next Steps for Adoption • NM-WG to get rough consensus on common tools eg ping, iperf, traceroute (Almost there) • Put these in the canonical NM-WG namespace (ie schemas, parameters are NM_WG specific) • Publish v2 Schemas doc in GGF via GFSG- Draft Recommendation • Get 2+ implementations to interoperate • Iterate, using developer's guide as read/write resource NMWG GGF13 Seoul March 2005 R. Hughes-Jones Manchester

  20. NMWG GGF13 Seoul March 2005 R. Hughes-Jones Manchester

More Related