RFC 2776 on MZAP
RFC Editor <rfc-ed@ISI.EDU> Tue, 22 February 2000 21:02 UTC
Received: from loki.ietf.org (loki [10.27.2.29]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA23018; Tue, 22 Feb 2000 16:02:12 -0500 (EST)
Received: (from adm@localhost) by loki.ietf.org (8.9.1b+Sun/8.9.1) id PAA03042 for ietf-123-outbound.10@ietf.org; Tue, 22 Feb 2000 15:55:02 -0500 (EST)
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 PAA03001 for <all-ietf@loki.ietf.org>; Tue, 22 Feb 2000 15:47:36 -0500 (EST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA22526 for <all-ietf@ietf.org>; Tue, 22 Feb 2000 15:47:33 -0500 (EST)
Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by boreas.isi.edu (8.8.7/8.8.6) with ESMTP id MAA18025; Tue, 22 Feb 2000 12:47:32 -0800 (PST)
Message-Id: <200002222047.MAA18025@boreas.isi.edu>
To: IETF-Announce:;
Subject: RFC 2776 on MZAP
Cc: rfc-ed@ISI.EDU, mboned@network-services.uoregon.edu
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Tue, 22 Feb 2000 12:47:32 -0800
From: RFC Editor <rfc-ed@ISI.EDU>
A new Request for Comments is now available in online RFC libraries. RFC 2776 Title: Multicast-Scope Zone Announcement Protocol (MZAP) Author(s): M. Handley, D. Thaler, R. Kermode Status: Standards Track Date: February 2000 Mailbox: mjh@aciri.org, dthaler@microsoft.com, Roger_Kermode@email.mot.com Pages: 27 Characters: 61628 Updates/Obsoletes/See Also: None I-D Tag: draft-ietf-mboned-mzap-06.txt URL: ftp://ftp.isi.edu/in-notes/rfc2776.txt This document defines a protocol, the Multicast-Scope Zone Announcement Protocol (MZAP), for discovering the multicast administrative scope zones that are relevant at a particular location. MZAP also provides mechanisms whereby common misconfigurations of administrative scope zones can be discovered. This document is a product of the MBONE Deployment 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.
- RFC 2776 on MZAP RFC Editor