Changing the LoST Location Profile Registry Policy
draft-ecrit-location-profile-registry-policy-01
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Randall Gellens | ||
| Last updated | 2020-09-25 | ||
| Replaced by | draft-ietf-ecrit-location-profile-registry-policy | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-ecrit-location-profile-registry-policy | |
| 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
This document changes the policy of the Location-to-Service Translation (LoST) Location Profile registry established by RFC5222 from Standards Action to Specification Required. This allows standards development organizations (SDOs) other than the IETF to add new values.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)