RFC 9036: Changing the Location-to-Service Translation (LoST) Location Profiles Registry Policy
In plain English — editorial summary, not part of the RFC
This document changes the policy of the "Location-to-Service Translation (LoST) Location Profiles" IANA registry established by RFC 5222 from Standards Action to Specification Required. This allows standards development organizations (SDOs) other than the IETF to add new values.
Document record
- Document ID
- RFC9036
- Published
- June 2021
- Authors
- R. Gellens
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- art
- Pages
- 4
- Also known as
- —
- Updates:
- RFC 5222
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9042Sieve Email Filtering: Delivery by MAILBOXIDCurrent
June 2021
- RFC 9043FFV1 Video Coding Format Versions 0, 1, and 3Current
August 2021
- RFC 9027Assertion Values for Resource Priority Header and SIP Priority Header Claims in Support of Emergency Services NetworksCurrent
June 2021
- RFC 9051Internet Message Access Protocol (IMAP) - Version 4rev2Current
August 2021
- RFC 9060Secure Telephone Identity Revisited (STIR) Certificate DelegationCurrent
September 2021
- RFC 9007Handling Message Disposition Notification with the JSON Meta Application Protocol (JMAP)Current
March 2021
- RFC 9073Event Publishing Extensions to iCalendarCurrent
August 2021
- RFC 9074"VALARM" Extensions for iCalendarCurrent
August 2021
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?