RFC 8217 · PROPOSED STANDARD · 2017

Clarifications for When to Use the name-addr Production in SIP Messages

Overview

RFC 8217, “Clarifications for When to Use the name-addr Production in SIP Messages”, is a Proposed Standard document published in August 2017 by R. Sparks. It updates RFC 3261, RFC 3325, RFC 3515, RFC 3892, RFC 4508, RFC 5002, RFC 5318, RFC 5360, RFC 5502. The canonical text is published by the RFC Editor.

Abstract

RFC 3261 constrained several SIP header fields whose grammar contains the "name-addr / addr-spec" alternative to use name-addr when certain characters appear. Unfortunately, it expressed the constraints with prose copied into each header field definition, and at least one header field was missed. Further, the constraint has not been copied into documents defining extension headers whose grammar contains the alternative.

This document updates RFC 3261 to state the constraint generically and clarifies that the constraint applies to all SIP header fields where there is a choice between using name-addr or addr-spec. It also updates the RFCs that define extension SIP header fields using the alternative to clarify that the constraint applies (RFCs 3325, 3515, 3892, 4508, 5002, 5318, 5360, and 5502).

Abstract as published in the RFC, via rfc-editor.org.

What “Proposed Standard” means

An entry-level standards-track specification: stable, peer-reviewed and a solid basis for implementation, though it may still evolve before becoming an Internet Standard.

Read this RFC

The canonical text of RFC 8217 is hosted at rfc-editor.org. Available in TXT,HTML.

Relationships to other RFCs
Other RFCs from 2017

Who Is Online

In total there are 72 users online: 0 registered, 64 guests and 8 bots.

Most users ever online was 5,555 on 17 Jul 2026, 3:23 am.

Bots: AhrefsBot Applebot Baiduspider Bingbot Googlebot Other Bot PetalBot SemrushBot

Users active in the past 15 minutes. Total registered members: 372