Using TTLs with Administratively Scoped IP Multicast Addresses
draft-finlayson-ttl-admin-scope-00

Document Type Expired Internet-Draft (individual)
Author Ross Finlayson 
Last updated 1997-03-26
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
pdf htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-finlayson-ttl-admin-scope-00.txt

Abstract

The use of 'administratively scoped' multicast address ranges (as described in [1]) leads to a multicast traffic scoping mechanism that is superior to the original 'TTL scoping' mechanism. Contrary to popular opinion, however, administrative (often abbreviated as 'admin') scoping does not truly *replace* TTL scoping. In particular, multicast-based applications must still be aware of which TTL value(s) they use. In this document, we note that each definition of a range of admin scoped multicast addresses should be accompanied by a corresponding 'maximum effective TTL' that should be used with these addresses. We describe how these TTL values are used by applications, and how they may influence the configuration of multicast border routers.

Authors

Ross Finlayson (finlayson@cs.stanford.edu)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)