RFC 5388: Information Model and XML Data Model for Traceroute Measurements

This document describes a standard way to store the configuration and the results of traceroute measurements. This document first describes the terminology…

Read RFC 5388 on the RFC Editor

Outgoing relationships (17 related RFCs)

Normative reference — RFC 2119: Key words for use in RFCs to Indicate Requirement Levels
Normative reference — RFC 2460: Internet Protocol, Version 6 (IPv6) Specification
Normative reference — RFC 3629: UTF-8, a transformation format of ISO 10646
Normative reference — RFC 2863: The Interfaces Group MIB
Normative reference — RFC 3032: MPLS Label Stack Encoding
Normative reference — RFC 3339: Date and Time on the Internet: Timestamps
Normative reference — RFC 4001: Textual Conventions for Internet Network Addresses
Normative reference — RFC 5198: Unicode Format for Network Interchange
Informative reference — RFC 3688: The IETF XML Registry
Informative reference — RFC 2578: Structure of Management Information Version 2 (SMIv2)
Informative reference — RFC 2579: Textual Conventions for SMIv2
Informative reference — RFC 2580: Conformance Statements for SMIv2
Informative reference — RFC 2474: Definition of the Differentiated Services Field (DS Field) in the IPv4 and IPv6 Headers
Informative reference — RFC 1812: Requirements for IP Version 4 Routers
Informative reference — RFC 5101: Specification of the IP Flow Information Export (IPFIX) Protocol for the Exchange of IP Traffic Flow Information
Informative reference — RFC 5102: Information Model for IP Flow Information Export
Informative reference — RFC 2681: A Round-trip Delay Metric for IPPM

Incoming relationships (1 related RFC)

Informatively referenced by — RFC 6632: An Overview of the IETF Network Management Standards