RFC 7913: P-Access-Network-Info ABNF Update
In plain English — editorial summary, not part of the RFC
This document updates RFC 7315, by modifying the extension-access- info part of the P-Access-Network-Info header field Augmented Backus- Naur Form (ABNF), and by adding the following 'access-info' header field parameter values to the list of 'access-info' header field parameter values in the ABNF: 'operator-specific-GI' and 'utran-sai-3gpp'. The values are defined in the ABNF but are not included in the list.
Document record
- Document ID
- RFC7913
- Published
- June 2016
- Authors
- C. Holmberg
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- —
- Pages
- 4
- Also known as
- —
- Updates:
- RFC 7315
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7976Updates to Private Header (P-Header) Extension Usage in Session Initiation Protocol (SIP) Requests and ResponsesObsoleted
September 2016
- RFC 8101IANA Registration of New Session Initiation Protocol (SIP) Resource-Priority Namespace for Mission Critical Push To Talk ServiceCurrent
March 2017
- RFC 75493GPP SIP URI Inter-Operator Traffic Leg ParameterCurrent
May 2015
- RFC 8498A P-Served-User Header Field Parameter for an Originating Call Diversion (CDIV) Session Case in the Session Initiation Protocol (SIP)Current
February 2019
- RFC 7255Using the International Mobile station Equipment Identity (IMEI) Uniform Resource Name (URN) as an Instance IDCurrent
May 2014
- RFC 9878Updates to Private Header (P-Header) Extension Usage in Session Initiation Protocol (SIP) Requests and ResponsesCurrent
November 2025
- RFC 5002The Session Initiation Protocol (SIP) P-Profile-Key Private Header (P-Header)Updated
August 2007
- RFC 4457The Session Initiation Protocol (SIP) P-User-Database Private-Header (P-Header)Current
April 2006
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?