This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/

proposal for inet-rtr obj extensions, for multicast, etc.

• Previous message (by thread): proposal for inet-rtr obj extensions, for multicast, etc.
• Next message (by thread): FYI: List of current proposals

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Petri Helenius pete at sms.fi
Wed Sep 18 23:21:05 CEST 1996

Wilfried Woeber writes:
 >   Dear all,
 > 
 >   		(to complete a long-standing RIPE action and to make progress)
 > 
 >   please find below a modified version of a document (originally by Erik-Jan Bos)
 >   which then was describing a multicast router in a routing registry. 
 > 
Your proposal does not take any stand on documenting scoped addressing
and the boundaries that make it happen. There is already a set of
boundaries that are going to augment the functionality previously
achieved only by thresholds.

Pete

• Previous message (by thread): proposal for inet-rtr obj extensions, for multicast, etc.
• Next message (by thread): FYI: List of current proposals

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

[ db-wg Archives ]