Standardisation related to INTERMON project

Performance measurement

IETF IP Performance Metrics Working Group – IPPM WG
defines specific metrics and procedures for accurately measuring and documenting these metrics

• Connectivity
• One-way delay and loss
• Round-trip delay and loss
• Delay variation
• Loss patterns
• Packet reordering
• Bulk transport capacity
• Link bandwidth capacity

Realtime Traffic Flow Measurement

IETF Realtime Traffic Flow Measurement Charter'' – RTFM WG defines Traffic Flow Model considering at least the following:

• Efficient hardware implementation
• Effect of IPv6 on traffic measurement
• Extension of the accounting model to widen the range of measurable quantities
• Simpler ways to specify flows of interest
• Maintain existing focus on data reduction capabilities
  

Flow Information Export

IP Flow Information Export IPFIX WG

• Defines "standard IP flow."
• Devise data encodings that support analysis of IPv4 and IPv6 unicast and multicast flows.
• IP flow information export based upon packet sampling.
• Security privacy concerns affecting flow data
• Specify the transport mapping for carrying IP flow information
• Ensure that the flow export system is reliable
  

Packet Sampling

Packet Sampling – PSAMP WG

• Selectors for packet sampling
• Packet Information
• Sampled packet reports
• Report Streams
• Multiple Report Streams
• Configuration and MIB
• Presentation, Export, and Transport of Packet Reports
  

Remote Network Monitoring

Remote Network Monitoring – RMONMIB WG
define a set of managed objects for remote monitoring of networks.

• Application Performance Measurement. Extensions to the RMON-2 MIB. SNMP retrieval.
• Monitoring support for Differentiated Services. Statistics Collection.
• Interface TopN Reporting. Determining the most congested (highest utilized) physical ports and links in an RMON-capable device with multiple interfaces.
• Token Ring MIB (RFC 1513).
• Transport Performance Measurement: Selectable performance metrics and statistics using passive and active traffic generation sources.
• RMON PI Reference
• Synthetic Sources for Performance Monitoring Mechanisms for the remote control of synthetic packet sources and destinations.
• RMON Framework
• Real-time Application QoS Monitoring MIB
• Extend the RMON framework to monitor end
  devices such as IP Phones, pagers, Instant Message Clients, Cell Phones, and PDA devices. An end-to-end user experience of the quality of service (QoS) and performance for such an application is a combination of device and network performance. Monitoring should be performed at the application layer that reflects a specific end user experience on a particular IP end point
• SMON MIB
• RMON-2 MIB

ISP & SP core tunneling measurement

• Common Control and Measurement Plane – CCAMP WG
• Signalling protocols and measurement protocols for multiple physical path and tunnel technologies (e.g. O-O and O-E-O optical switches, ATM and Frame Relay switches, MPLS, GRE) using input from technology-specific working groups such as MPLS, IPO, etc.
• Signalling and measurement protocols that are independent of each other. This allows applications other than the signalling
  protocol to use the measurement protocol; it also allows the signalling protocol to use knowledge obtained by means other than the
  measurement protocol.
• Develop and define a set of protocol-independent metrics and parameters for describing links and paths that can be carried in protocols. These will be developed in conjunction with requests and requirements from other WGs (e.g., TEWG, PPVPN, etc.) to insure overall usefulness.
• Abstract link and path properties needed for link and path protection.
• Signalling mechanisms for path protection,
• Diverse routing and fast path restoration. Ensure that multi-layer path protection and
  restoration functions are achievable using the defined signalling and measurement protocols, either separately or in combination.
• Define how the properties of network resources gathered by the measurement protocol can be distributed in existing routing
  protocols, such as OSPF and IS-IS.
• Define the relationship between layer 3 routing protocols and the common signalling protocol for establishing and maintaining paths.
• Using input from the TE working group, ensure that the signalling and measurement protocols provide both the information and the control functions adequate to support the traffic provisioning and engineering operations of service providers.

Inter-domain routing

Inter-Domain Routing

Inter-Domain Routing - IDR WG

• Revise and clarify the base BGP4 document (RFC 1771); BGP4 MIB; AS Confederations and Route Reflection; Multiprotocol BGP
• BGP MIB v2 that includes support for AS Confederations, Route Reflection, Communities, Multi-Protocol BGP, BGP Extended Communities, support for 4-byte AS numbers.
• A BGP-based mechanism that allows a BGP speaker to send to its BGP peer a set of route filters that the peer would use to constrain/filter its outbound routing updates to the speaker.
• Standards track an Outbound Router Filter (ORF) type for BGP, that can be used to perform aspath based route filtering.
• A BGP Graceful Restart mechanism along standards track.
• Subcodes for BGP Cease Notification Message along standards track.
• AS-wide Unique BGP Identifier for BGP-4 along standards track.
• Dynamic Capability for BGP-4 along standards track.
  

Resource control & policy framework

Resource Allocation

Resource Allocation Protocol –RAP WG

• Development of Common Open Policy Service Protocol (COPS) RFC 2748 defining general-purpose objects that facilitate the manipulation of policies and provisioned objects available through COPS and COPS-PR.
• A standards track framework document describing the usage of COPS in carrying usage reporting and unsolicited state change information between a PDP and a PEP
  

QoS Policy

Policy Framework – policy WG

• Represent, manage, share, and reuse policies
  and policy information in a vendor-independent, interoperable, and scalable manner.
• High-level policy information is translated into device configuration information for network QoS applications.
• Coordination of the core and QoS schemata, the PIB and MIB being developed in DiffServ, and possibly extensions to COPS provisioning.