RFC 2604 on OTASP/OTAPA via ACAP
RFC Editor <rfc-ed@ISI.EDU> Fri, 11 June 1999 17:50 UTC
Received: from loki.ietf.org (loki [10.27.2.29]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA04417; Fri, 11 Jun 1999 13:50:45 -0400 (EDT)
Received: (from adm@localhost) by loki.ietf.org (8.9.1b+Sun/8.9.1) id NAA29191 for ietf-123-outbound.10@ietf.org; Fri, 11 Jun 1999 13:45:01 -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 NAA29112 for <all-ietf@loki.ietf.org>; Fri, 11 Jun 1999 13:33:40 -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 NAA03913 for <all-ietf@ietf.org>; Fri, 11 Jun 1999 13:29:59 -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 KAA27205; Fri, 11 Jun 1999 10:30:00 -0700 (PDT)
Message-Id: <199906111730.KAA27205@boreas.isi.edu>
To: IETF-Announce:;
Subject: RFC 2604 on OTASP/OTAPA via ACAP
Cc: rfc-ed@ISI.EDU
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Fri, 11 Jun 1999 10:30:00 -0700
From: RFC Editor <rfc-ed@ISI.EDU>
A new Request for Comments is now available in online RFC libraries. RFC 2604: Title: Wireless Device Configuration (OTASP/OTAPA) via ACAP Author(s): R. Gellens Status: Informational Date: June 1999 Mailbox: randy@qualcomm.com Pages: 29 Characters: 65329 Updates/Obsoletes/See Also: None I-D Tag: draft-gellens-otasp-acap-01.txt pathname on ftp.isi.edu: in-notes/rfc2604.txt URL: ftp://ftp.isi.edu/in-notes/rfc2604.txt This paper describes a viable and attractive means to provide OTASP/OTAPA via IS-707, using the ACAP [ACAP] protocol. 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 2604 on OTASP/OTAPA via ACAP RFC Editor