RFC 2614 on Service Location API
RFC Editor <rfc-ed@ISI.EDU> Wed, 23 June 1999 20:10 UTC
Received: from loki.ietf.org (loki [10.27.2.29]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA13154; Wed, 23 Jun 1999 16:10:13 -0400 (EDT)
Received: (from adm@localhost) by loki.ietf.org (8.9.1b+Sun/8.9.1) id QAA06446 for ietf-123-outbound.10@ietf.org; Wed, 23 Jun 1999 16:05:02 -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 OAA06000 for <all-ietf@loki.ietf.org>; Wed, 23 Jun 1999 14:52:20 -0400 (EDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA09363 for <all-ietf@ietf.org>; Wed, 23 Jun 1999 14:48:23 -0400 (EDT)
Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by boreas.isi.edu (8.8.7/8.8.6) with ESMTP id LAA24042; Wed, 23 Jun 1999 11:48:24 -0700 (PDT)
Message-Id: <199906231848.LAA24042@boreas.isi.edu>
To: IETF-Announce:;
Subject: RFC 2614 on Service Location API
Cc: rfc-ed@ISI.EDU
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Wed, 23 Jun 1999 11:48:24 -0700
From: RFC Editor <rfc-ed@ISI.EDU>
A new Request for Comments is now available in online RFC libraries. RFC 2614: Title: An API for Service Location Author(s): J. Kempf, E. Guttman Status: Informational Date: June 1999 Mailbox: james.kempf@sun.com, erik.guttman@sun.com Pages: 91 Characters: 164002 Updates/Obsoletes/See Also: None I-D Tag: draft-ietf-svrloc-api-09.txt URL: ftp://ftp.isi.edu/in-notes/rfc2614.txt This document describes standardized APIs for SLP in C and Java. The APIs are modular and are designed to allow implementations to offer just the feature set needed. In addition, standardized file formats for configuration and serialized registrations are defined, allowing SLP agents to set network and other parameters in a portable way. This document is a product of the Service Location Protocol Working Group of the IETF. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. 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 Alegre Ramos 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 2614 on Service Location API RFC Editor