One document matched: draft-ietf-malloc-madcap-nest-opt-05.txt

Differences from draft-ietf-malloc-madcap-nest-opt-04.txt

A new Request for Comments is now available in online RFC libraries.


        RFC 2907

        Title:      MADCAP Multicast Scope Nesting State Option
        Author(s):  R. Kermode
        Status:     Standards Track
        Date:       September 2000
        Mailbox:    Roger.Kermode@motorola.com
        Pages:      13
        Characters: 27572
        Updates/Obsoletes/SeeAlso:  None

        I-D Tag:    draft-ietf-malloc-madcap-nest-opt-05.txt

        URL:        ftp://ftp.isi.edu/in-notes/rfc2907.txt


This document defines a new option to the Multicast Address Dynamic
Client Allocation Protocol (MADCAP) to support nested scoping. The
new option's purpose is to allow clients to learn which scopes nest
inside each other, and hence it may be used for expanding scope
searches or hierarchical multicast transport.

This document is a product of the Multicast-Address Allocation Working
Group of the IETF.

This is now a Proposed Standard Protocol.

This document specifies an Internet standards track protocol for
the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the
"Internet Official Protocol Standards" (STD 1) for the
standardization state and status of this protocol.  Distribution
of this memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo 
Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.