RFC 3608: Session Initiation Protocol (SIP) Extension Header Field for Service Route Discovery During Registration
In plain English — editorial summary, not part of the RFC
This document defines a Session Initiation Protocol (SIP) extension header field used in conjunction with responses to REGISTER requests to provide a mechanism by which a registrar may inform a registering user agent (UA) of a service route that the UA may use to request outbound services from the registrar's domain.
Document record
- Document ID
- RFC3608
- Published
- October 2003
- Authors
- D. Willis; B. Hoeneisen
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rai
- Pages
- 17
- Also known as
- —
- Updated by:
- RFC 5630
Topics
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3327Session Initiation Protocol (SIP) Extension Header Field for Registering Non-Adjacent ContactsUpdated
December 2002
- RFC 3680A Session Initiation Protocol (SIP) Event Package for RegistrationsUpdated
March 2004
- RFC 3840Indicating User Agent Capabilities in the Session Initiation Protocol (SIP)Current
August 2004
- RFC 3329Security Mechanism Agreement for the Session Initiation Protocol (SIP)Updated
January 2003
- RFC 3324Short Term Requirements for Network Asserted IdentityCurrent
December 2002
- RFC 3581An Extension to the Session Initiation Protocol (SIP) for Symmetric Response RoutingCurrent
August 2003
- RFC 3578Mapping of Integrated Services Digital Network (ISDN) User Part (ISUP) Overlap Signalling to the Session Initiation Protocol (SIP)Current
August 2003
- RFC 3515The Session Initiation Protocol (SIP) Refer MethodUpdated
April 2003
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?