RFC 5628: Registration Event Package Extension for Session Initiation Protocol (SIP) Globally Routable User Agent URIs (GRUUs)
In plain English — editorial summary, not part of the RFC
RFC 3680 defines a Session Initiation Protocol (SIP) event package for registration state. This package allows a watcher to learn about information stored by a SIP registrar, including its registered contact. However, the registered contact is frequently unreachable and thus not useful for watchers. The Globally Routable User Agent URI (GRUU), defined in RFC 5627, is a URI that is capable of reaching a particular contact. However this URI is not included in the document format defined in RFC 3680. This specification defines an extension to the registration event package to include GRUUs assigned by the registrar. [STANDARDS-TRACK]
Document record
- Document ID
- RFC5628
- Published
- October 2009
- Authors
- P. Kyzivat
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rai
- Pages
- 14
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5627Obtaining and Using Globally Routable User Agent URIs (GRUUs) in the Session Initiation Protocol (SIP)Current
October 2009
- RFC 8003Host Identity Protocol (HIP) Registration ExtensionCurrent
October 2016
- RFC 9876Updates to the IANA Registration Procedures for Constrained Application Protocol (CoAP) Content-FormatsCurrent
November 2025
- RFC 5629A Framework for Application Interaction in the Session Initiation Protocol (SIP)Current
October 2009
- RFC 5626Managing Client-Initiated Connections in the Session Initiation Protocol (SIP)Current
October 2009
- RFC 5630The Use of the SIPS URI Scheme in the Session Initiation Protocol (SIP)Current
October 2009
- RFC 5621Message Body Handling in the Session Initiation Protocol (SIP)Updated
September 2009
- RFC 5606Implications of 'retransmission-allowed' for SIP Location ConveyanceCurrent
August 2009
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?