draft-holmberg-dispatch-pani-abnf.xml

<?xml version="1.0" encoding="iso-8859-1"?>
<!-- comment -->
<!DOCTYPE rfc SYSTEM "rfc2629.dtd"[]>
<?rfc toc="yes" ?>
<?rfc compact="yes" ?>
<?rfc sortrefs="no" ?>
<rfc ipr="trust200902" category="info" docName="draft-holmberg-dispatch-pani-abnf-02" updates="7315" submissionType="IETF" xml:lang="en">
  <front>
    <title abbrev="PANI ABNF">
		P-Access-Network-Info ABNF Update
	</title>
    <author fullname="Christer Holmberg" initials="C.H." surname="Holmberg">
      <organization abbrev="Ericsson">Ericsson</organization>
      <address>
        <postal>
          <street>Hirsalantie 11</street>
          <city>Jorvas</city>
          <region></region>
          <code>02420</code>
          <country>Finland</country>
        </postal>
        <phone></phone>
        <email>christer.holmberg@ericsson.com</email>
      </address>
    </author> 
    	
    <date year="2015" />
    <area>Transport</area>
    <keyword>PANI</keyword>
	<keyword>ABNF</keyword>
	<keyword>P-Access-Network-Info</keyword>
	<keyword>3GPP</keyword>
	<keyword>IMS</keyword>
    <abstract>
        <t>
            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). 
        </t>
    </abstract>
</front>

<middle>
    <section title="Introduction">
		<t>
            <xref target="RFC7315" pageno="false" format="default"/> defines the 
            Session Initiation Protocol (SIP) <xref target="RFC3261" pageno="false" 
            format="default"/> P-Access-Network-Info header field.
        </t>
        <t>
            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 <xref target="RFC3261" pageno="false" 
            format="default"/>. However, currently the Augmented Backus-Naur Form 
            (ABNF) <xref target="RFC5234" pageno="false" format="default"/> requires 
            new values to follow the 'gen-value' rule <xref target="RFC3261" 
            pageno="false" format="default"/>, 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.
        </t>
        <t>
            This document updates section 5.4 of <xref target="RFC7315" pageno="false" 
            format="default"/>, by modifying the extension-access-info part of the 
            P-Access-Network-Info header field ABNF. 
        </t>
        <t>
            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  <xref target="TS.3GPP.24.229" 
            pageno="false" format="default"/>, the update is not seen to cause
            backward compatibility concerns.
        </t>
    </section>
		
    <section title="Conventions">
		<t>
			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 <xref target="RFC2119"></xref>.
		</t>
    </section>
    
    <section title="Update to RFC 7315">
			<t>
                This section updates the ABNF defined in section 5.4 of RFC 7315, 
                as described below:
            </t>
            <figure>
				<artwork align="left"><![CDATA[
                
Old syntax:

    extension-access-info  = gen-value
    

New syntax:

    extension-access-info  = generic-param

				]]></artwork>
			</figure>
	</section>
	
	<section title="Security Considerations">
		<t>
            The security considerations for the P-Access-Network-Info header field
            are defined in <xref format="default" pageno="false" target="RFC7315"/>.
            The ABNF update defined in this document does not impact the security
            considerations.
		</t>
	</section>

	<section anchor="section.iana" title="IANA Considerations">
        <t>
            This document makes no requests from IANA.
        </t>
	</section>
                   
	<section title="Acknowledgments">
		<t>
            TBD
		</t>
	</section>
		
	<section title="Change Log">	
		<t>[RFC EDITOR NOTE: Please remove this section when publishing]</t>
        <t>Changes from draft-holmberg-dispatch-pani-abnf-01
			<list style="symbols">
                <t>- Editorial fixes based on comments from Jean Mahoney.</t>
                <t>- Reference to 3GPP 24.229 added.</t>
			</list>
		</t>		
        <t>Changes from draft-holmberg-dispatch-pani-abnf-00
			<list style="symbols">
                <t>- Category changed to 'Informational'.</t>
			</list>
		</t>		
	</section>
</middle>

<back>
    <references title="Normative References">
		<?rfc include="reference.RFC.2119"?>
		<?rfc include="reference.RFC.3261"?>
        <?rfc include="reference.RFC.5234"?>
        <?rfc include="reference.RFC.7315"?>
        <reference anchor="TS.3GPP.24.229">
			<front> 
				<title>
                    IP multimedia call control protocol based on Session Initiation Protocol (SIP)
                    and Session Description Protocol (SDP);Stage 3
                </title>
				<author><organization>3GPP</organization></author>
				<date year="2015" month="September" day="25"/>
			</front> 
			<seriesInfo value="24.229 13.3.1" name="3GPP TS"/> 
			<format type="HTML" target="http://www.3gpp.org/ftp/Specs/html-info/24229.htm"/> 
		</reference>
    </references>
</back>
</rfc>