RFC 2907 on MADCAP Multicast Scope Nesting State Option
RFC Editor <rfc-ed@ISI.EDU> Thu, 21 September 2000 17:09 UTC
Received: from loki.ietf.org (loki [10.27.2.29]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA10128; Thu, 21 Sep 2000 13:09:26 -0400 (EDT)
Received: (from adm@localhost) by loki.ietf.org (8.9.1b+Sun/8.9.1) id MAA16088 for ietf-123-outbound.10@ietf.org; Thu, 21 Sep 2000 12:55:00 -0400 (EDT)
Received: from ietf.org (odin.ietf.org [10.27.2.28]) by loki.ietf.org (8.9.1b+Sun/8.9.1) with ESMTP id MAA16061 for <all-ietf@loki.ietf.org>; Thu, 21 Sep 2000 12:51:18 -0400 (EDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA09867 for <all-ietf@ietf.org>; Thu, 21 Sep 2000 12:51:17 -0400 (EDT)
Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by boreas.isi.edu (8.9.3/8.9.3) with ESMTP id JAA11774; Thu, 21 Sep 2000 09:51:17 -0700 (PDT)
Message-Id: <200009211651.JAA11774@boreas.isi.edu>
To: IETF-Announce:;
Subject: RFC 2907 on MADCAP Multicast Scope Nesting State Option
Cc: rfc-ed@ISI.EDU, malloc@catarina.usc.edu
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Thu, 21 Sep 2000 09:51:17 -0700
From: RFC Editor <rfc-ed@ISI.EDU>
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. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs.