P-Access-Network-Info ABNF Update
draft-holmberg-dispatch-pani-abnf-02

Abstract

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).

Status of This Memo

This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.

Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet-Drafts is at http://datatracker.ietf.org/drafts/current/.

Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."

This Internet-Draft will expire on May 4, 2016.

Copyright Notice

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

This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License.

Table of Contents

• 1. Introduction
• 2. Conventions
• 3. Update to RFC 7315
• 4. Security Considerations
• 5. IANA Considerations
• 6. Acknowledgments
• 7. Change Log
• 8. Normative References
• Author's Address

1. Introduction

[RFC7315] defines the Session Initiation Protocol (SIP) [RFC3261] P-Access-Network-Info header field.

The header field syntax contains an 'access-info' header field parameter, with a set of pre-defined values. Most pre-defined values follow the 'generic-param' rule [RFC3261]. However, currently the Augmented Backus-Naur Form (ABNF) [RFC5234] requires new values to follow the 'gen-value' rule [RFC3261], which is more restrictive than 'generic-param'. There is no justification for the restriction, and new values have already been defined following the 'generic-param' rule.

This document updates section 5.4 of [RFC7315], by modifying the extension-access-info part of the P-Access-Network-Info header field ABNF.

As the P-Access-Network-Info header field is mainly used in networks defined by the 3rd-Generation Partnership Project (3GPP), where new values following the 'generic-param' rule have been defined [TS.3GPP.24.229], the update is not seen to cause backward compatibility concerns.

2. Conventions

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [RFC2119].

3. Update to RFC 7315

This section updates the ABNF defined in section 5.4 of RFC 7315, as described below:

                
Old syntax:

    extension-access-info  = gen-value
    

New syntax:

    extension-access-info  = generic-param

				

4. Security Considerations

The security considerations for the P-Access-Network-Info header field are defined in [RFC7315]. The ABNF update defined in this document does not impact the security considerations.

5. IANA Considerations

This document makes no requests from IANA.

6. Acknowledgments

TBD

7. Change Log

[RFC EDITOR NOTE: Please remove this section when publishing]

Changes from draft-holmberg-dispatch-pani-abnf-01

• - Editorial fixes based on comments from Jean Mahoney.
• - Reference to 3GPP 24.229 added.

Changes from draft-holmberg-dispatch-pani-abnf-00

• - Category changed to 'Informational'.

8. Normative References

Author's Address