 | Channel: MZL & Novatech Product and Service NewsNewsfeed of MZL & Novatech Traffic & Bandwidth Statistics product and service releases
Berlin/Germany, 10/31/04
Change of Data Labeling IPDR of MZL & Novatech TrafficStatistic's IP Detail Records requested by ipdr.org - now called IPTDR
Formerly we, MZL & Novatech TrafficStatistic, named our IPTDR data records in openly published format IPDR as the data our traffic statistics program collects are Internet Protocol Detail Records in the meaning of the words: Usage Detail records from Internet Protocol Network Layer.
In billing industry it is common to name abbreviate detail records with DR and prepend the type of detail records in front of it like CDR for Call Detail Records in voice services, EDR for Event Detail Records for 3G services or XDR on a way to an RFC as a description of Any Detail Records just analog to the XML specified only after the specific HTML case. As the MZL & Novatech TrafficStatistic program collects IP Detail Records, using the abbreviation IPDR was just a logical implication.
Since an organisation named IPDR.org claims now in October 2004 to have the abbreviation IPDR protected by a trademark "IPDR compliant (TM)", Traffic Statistics respect the wish of ipdr.org to have us changing the wording of the Traffic Statistics Detail Records, though ipdr.org does not even provide a specification of real IPDR as IP Detail Records in narrow sense of the word, but provides a specification for network data usage information in general, as Marianne Jenkinson from ipdr.org remarks in her letter requesting MZL & Novatech TrafficStatistic to change the wording. So, as consequence to the request of Marianne Jenkinson we changed the wording of our Internet Protocol data record format to IPTDR as abbreviation for Internet Protocol Traffic Detail Records.
Anyway it might happen, that due to technical reasons in some parts of the Traffic Statistics software or the website the string IPDR still occurs. In this case, please read it as if it would have been written IPTDR.
Please note, that Traffic Statistics does not follow the IPDR specification as published by IPDR.org nor intends to do so, because Traffic Statistics does believe that fulfilling the IPDR specification by IPDR.org would
- consume too much memory and CPU power (users wouldn't like to order an extra CPU for IPDR compliance),
- would enlarge our software to useless complexity and
- Traffic Statistics believes, that the IPDR format from IPDR.org is far less popular and less sensible as a standard than Cisco's NetFlow(TM) format.
Link provided: http://www.trafficstatistic.com/help/ipdr_format.html
Added by: Traffic Statistics Management
Previous news item - - - Next news item
| |
Home 
