RFC 3528 on Mesh-enhanced Service Location Protocol (mSLP)
rfc-editor@rfc-editor.org Thu, 01 May 2003 20:00 UTC
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA05663; Thu, 1 May 2003 16:00:20 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10) id 19BJnj-0006x1-00 for ietf-announce-list@ran.ietf.org; Thu, 01 May 2003 15:33:03 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org) by ran.ietf.org with esmtp (Exim 4.10) id 19BJiF-0006X8-00 for all-ietf@ran.ietf.org; Thu, 01 May 2003 15:27:23 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA02382 for <all-ietf@ietf.org>; Thu, 1 May 2003 15:23:37 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19BJgi-0005cC-00 for all-ietf@ietf.org; Thu, 01 May 2003 15:25:48 -0400
Received: from gamma.isi.edu ([128.9.144.145]) by ietf-mx with esmtp (Exim 4.12) id 19BJgc-0005aT-00 for all-ietf@ietf.org; Thu, 01 May 2003 15:25:42 -0400
Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6p2/8.11.2) with ESMTP id h41JOS014245; Thu, 1 May 2003 12:24:28 -0700 (PDT)
Message-Id: <200305011924.h41JOS014245@gamma.isi.edu>
To: IETF-Announce:;
Subject: RFC 3528 on Mesh-enhanced Service Location Protocol (mSLP)
Cc: rfc-editor@rfc-editor.org
From: rfc-editor@rfc-editor.org
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Thu, 01 May 2003 12:24:27 -0700
Sender: owner-ietf-announce@ietf.org
Precedence: bulk
A new Request for Comments is now available in online RFC libraries.
RFC 3528
Title: Mesh-enhanced Service Location Protocol (mSLP)
Author(s): W. Zhao, H. Schulzrinne, E. Guttman
Status: Experimental
Date: April 2003
Mailbox: zwb@cs.columbia.edu, hgs@cs.columbia.edu,
Erik.Guttman@sun.com
Pages: 15
Characters: 35208
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-zhao-slp-da-interaction-16.txt
URL: ftp://ftp.rfc-editor.org/in-notes/rfc3528.txt
This document describes the Mesh-enhanced Service Location Protocol
(mSLP). mSLP enhances the Service Location Protocol (SLP) with a
scope-based fully-meshed peering Directory Agent (DA) architecture.
Peer DAs exchange new service registrations in shared scopes via
anti-entropy and direct forwarding. mSLP improves the reliability and
consistency of SLP DA services, and simplifies Service Agent (SA)
registrations in systems with multiple DAs. mSLP is backward
compatible with SLPv2 and can be deployed incrementally.
This memo defines an Experimental Protocol for the Internet community.
It does not specify an Internet standard of any kind. Discussion and
suggestions for improvement are requested. 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.