About RIPE | Contact  | Search | Sitemap    
Homepage RIPE  
RIPE Policy Proposals
search  
     
Next Sectionyou are here: RIPE > Policy Development > Policy Proposals
RIPE Navigation Ends
green dot Current Policy Proposals
green dot Archived Policy Proposals
green dot Subscribe to the Policy-Announce List
green dot Policy Proposal Template
green dot Policy Development Process Info (PDF)
RIPE NCC Navigation Ends
Next Section

RIPE Policy Proposal 2005-11

Number:
 2005-11
Policy Proposal Name:
 Multicast Monitoring on RIPE NCC Test Traffic Boxes
Author:
spacer		 Gert Doering

SpaceNet AG
Proposal Version:
 1.0
Submission Date:
 31 October 2005
Current Status :
 Discussion Phase – Open for Discussion - Extended
Suggested WG for Discussion and Publication:
 Test Traffic
Proposal Type:
 New
Policy Term:
Permanent
Policy Document to be Affected:
N/A
Draft RIPE Document :
N/A at this stage
Summary of Proposal:

I propose to add testing of multicast connectivity between the RIPE NCC Test Traffic boxes that are connected to multicast-capable networks.

The test setup could consist of the following components:

  • Multicast beacons, that send packets in regular intervals to well-known multicast addresses (some beacons already exist).
  • Multicast listeners, that monitor incoming beacon packets, and complain if packets from given senders stop arriving.
  • Some high level monitoring infrastructure that can use the data from "lots of beacons and listeners" to figure out where the problem is (it has to be in this or that Autonomous System (AS), or in between).

 
Draft Policy Text

I am not really sure if there are policy documents that describe what the test-boxes do and don't do, but if yes, they should be modified appropriately.

 
Rationale:

a. Arguments supporting the proposal:

The RIPE NCC Test Traffic boxes form a very useful measurement platform, distributed over a large number of provider networks.

IP Multicast monitoring is inherently difficult, as you cannot easily probe connectivity from a single point of view - some problems need testing and monitoring from multiple different locations to identify "black holes" on some paths.

When troubleshooting connectivity issues spanning multiple networks, things are a lot easier if a neutral entity does the monitoring and pinpointing of problem areas.

I think the RIPE NCC Test Traffic network is uniquely qualified to do this.

b. Arguments opposing the proposal:
Some arguments have been brought forward that there are not enough multicast-capable networks to make this a worthwile action.

 
RELATED TOPICS
RIPE DATABASE SEARCH


 

Next Section
     About RIPE | Site Map | LIR Portal | About the RIPE NCC | Contact | © RIPE Community. All rights reserved.
RIPE.NET Homepage LIR Portal RIPE Community