RFC 7913

P-Access-Network-Info ABNF Update

📅 published June 2016, from ietf

RFC 7913: P-Access-Network-Info ABNF Update 💖

Internet Engineering Task Force (IETF) 🎀 Author: Christer Holmberg, Ericsson. Date: June 2016. Category: Informational. This doc updates RFC 7315 and obsoletes nothing. ISSN: 2070-1721. Okay bestie, that's the header, now let's get into it ✨

Abstract

okay so this doc updates RFC 7315 🦋 It tweaks the extension-access-info part of the P-Access-Network-Info header field ABNF, and it adds two access-info parameter values to the list: operator-specific-GI and utran-sai-3gpp. They're already defined in the ABNF, but they weren't in the list. Lowkey a glow-up for the grammar 💅

Status of This Memo

not me being a stickler, but this one is not a Standards Track spec. It's published for informational purposes 🌸

This is an IETF product. It reflects consensus from the IETF community, got public review, and was approved for publication by the Internet Engineering Steering Group (IESG). Not every IESG-approved doc is a candidate for any level of Internet Standard, so check Section 2 of RFC 7841 if you're curious 🧚

More info on the current status, errata, and how to send feedback lives at http://www.rfc-editor.org/info/rfc7913 🔥

Copyright (c) 2016 IETF Trust and the persons identified as the document authors. All rights reserved. 💜

This doc is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) as they stood on the publication date. Read these carefully, because they spell out your rights and restrictions for this doc 🙈

Code Components pulled out of this doc have to include Simplified BSD License text, as described in Section 4.e of the Trust Legal Provisions. They come with no warranty, as described in the Simplified BSD License ⭐

Table of Contents

1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
2.  Update to RFC 7315  . . . . . . . . . . . . . . . . . . . . .   3
3.  Security Considerations . . . . . . . . . . . . . . . . . . .   3
4.  Normative References  . . . . . . . . . . . . . . . . . . . .   4
Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . .   4
Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   4

1. Introduction ✨

okay so [RFC7315] defines the P-Access-Network-Info header field for the Session Initiation Protocol (SIP) [RFC3261] 🦋

That header has an access-info parameter with a set of pre-defined values. Most of them follow the generic-param rule [RFC3261]. BUT the Augmented Backus-Naur Form (ABNF) [RFC5234] in [RFC7315] says new values have to follow the gen-value rule [RFC3261], which is way more restrictive than generic-param. There's no real justification for that, and new values have already been defined using generic-param anyway 💀

The ABNF also defines operator-specific-GI and utran-sai-3gpp, but they never got added to the list of access-info values. Main character energy, but still left out 😭

This doc updates Section 5.4 of [RFC7315] by changing the extension-access-info part of the P-Access-Network-Info header field ABNF 🎀

The header is mostly used in networks defined by the 3rd-Generation Partnership Project (3GPP), where new values following the generic-param rule have already been defined [TS.3GPP.24.229]. So the update isn't considered to cause backward compatibility issues. Periodt 💅

2. Update to RFC 7315 🌈

This section updates the ABNF in Section 5.4 of RFC 7315, like so:

Old syntax:

    access-info            = cgi-3gpp / utran-cell-id-3gpp /
                             dsl-location / i-wlan-node-id /
                             ci-3gpp2 / eth-location /
                             ci-3gpp2-femto / fiber-location /
                             np / gstn-location /local-time-zone /
                             dvb-rcs2-node-id / extension-access-info
    np                     = "network-provided"
    extension-access-info  = gen-value

New syntax:

    access-info            = cgi-3gpp / utran-cell-id-3gpp /
                             dsl-location / i-wlan-node-id /
                             ci-3gpp2 / eth-location /
                             ci-3gpp2-femto / fiber-location /
                             np / gstn-location /local-time-zone /
                             dvb-rcs2-node-id / operator-specific-GI /
                             utran-sai-3gpp / extension-access-info
    np                     = "network-provided"
    extension-access-info  = generic-param

3. Security Considerations 🔥

The security considerations for the P-Access-Network-Info header field are defined in [RFC7315]. The ABNF update in this doc does not impact them, so you're still covered ✨

4. Normative References 🧚

Acknowledgments 💜

Big thanks to Ben Campbell, Cullen Jennings, Gonzalo Salgueiro, Jean Mahoney, Menachem Dodge, Olafur Gudmundsson, Paul Kyzivat, and the 3GPP community for the guidance, input, and comments. You're all iconic 🫶

Author's Address 🌸

Christer Holmberg
Ericsson
Hirsalantie 11
Jorvas  02420
Finland

Email: christer.holmberg@ericsson.com

That's the whole RFC, bestie 🌈✨

📦 where this page comes from