RFC 2636: Wireless Device Configuration (OTASP/OTAPA) via ACAP
In plain English — editorial summary, not part of the RFC
This paper describes a viable and attractive means to provide OTASP/OTAPA via IS-707, using the ACAP protocol. This memo provides information for the Internet community.
Document record
- Document ID
- RFC2636
- Published
- July 1999
- Authors
- R. Gellens
- Status
- INFORMATIONAL
- Stream
- Legacy
- Area
- —
- Pages
- 29
- Also known as
- —
- Obsoletes:
- RFC 2604
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2683IMAP4 Implementation RecommendationsUpdated
September 1999
- RFC 2713Schema for Representing Java(tm) Objects in an LDAP DirectoryCurrent
October 1999
- RFC 2714Schema for Representing CORBA Object References in an LDAP DirectoryCurrent
October 1999
- RFC 2798Definition of the inetOrgPerson LDAP Object ClassUpdated
April 2000
- RFC 2367PF_KEY Key Management API, Version 2Current
July 1998
- RFC 2359IMAP4 UIDPLUS extensionObsoleted
June 1998
- RFC 2985PKCS #9: Selected Object Classes and Attribute Types Version 2.0Current
November 2000
- RFC 2271An Architecture for Describing SNMP Management FrameworksObsoleted
January 1998
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?