Status of This Memo
draft-edge-appconfig-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Charles S Edge Jr | ||
| Last updated | 2023-03-30 (Latest revision 2022-09-26) | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
Many Service Providers offer application configuration options that manage the state of applications on mobile devices. AppConfig is used to distribute settings to applications upon installation or updated arbitrarily via a trusted Mobile Device Management (MDM) service. This document defines the specification by allowing a standardized format for data to stream into applications via XML (RFC 3470) or JSON interfaces (RFC 4627).
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)