RE: [ippm] Update proposal for draf-ietf-ippm-storetraceroutes - addingarbitrary data

["Saverio Niccolini" <Saverio.Niccolini at netlab.nec.de>]

Dear Antonin,

Thanks for this additional input, actually my only concern is:

you say you gather this additional data not using traceroute measurements, our draft actually focuses on traceroute measurements, then we (inside the IPPM group) need to decide if we want to broaden the scope of the draft of not.

If there is consensus on the fact that the scope can be broadened then we can discuss how to extend the schema and the draft.

Cheers,
Saverio

> -----Original Message-----
> From: Antonin Kral [mailto:A.Kral at sh.cvut.cz]
> Sent: Thursday, June 07, 2007 7:12 AM
> To: ippm at ietf.org
> Subject: [ippm] Update proposal for draf-ietf-ippm-storetraceroutes -
> addingarbitrary data
> 
> Hello,
> 
> I am working on one project in CESNET (Czech NREN), this project is part
> of PerfSonar project as well. We want to store more information than
> only RTT for each hop. These values could contain information like
> available bandwidth on particular link, or installed capacity, queue
> load etc. These information are not fetched by traceroute itself, but
> from other programs which are able to communicate with so called
> Measurement Points. Our idea is to use XML schema proposed by you to
> stored measured data. Unfortunately there is no way how to add new
> attributes without schema modification in current RFC draft.
> 
> I would like to propose new attribute, which could contain arbitrary
> (application-dependant) data. Support for semantic of particular
> attribute will be optional (every application will have own set of
> supported attributes and their meaning). My idea is something like
> the following XML (not schema):
> 
> <AdditionalData>
>   <Attribute name="installed_bw" dataType="Unsigned32">
>     1000
>   </Attribute>
>   <Attribute name="available_bw" dataType="Unsigned32">
>     900
>   </Attribute>
>   <Attribute name="queue_length" dataType="Unsigned32">
>     12
>   </Attribute>
>   <Attribute name="ingest_interface_name" dataType="String">
>     GigabitEthernet6/0/1
>   </Attribute>
> </AdditionalData>
> 
> <AdditionalData> attribute should be optional in measurement description
> (complex type _Metadata) as well as measurement results (complex type
> _Measurement).
> 
> If you like the proposed way, I will be happy to prepare relevant XML
> schema for this.
> 
> Thank you, best regards,
> 
>     Antonin Kral
> 
> _______________________________________________
> ippm mailing list
> ippm at ietf.org
> https://www1.ietf.org/mailman/listinfo/ippm

_______________________________________________
ippm mailing list
ippm at ietf.org
https://www1.ietf.org/mailman/listinfo/ippm