IETF Logo Mail Archive

[sipcore] Multiple P-Access-Network-Info header in the same SIP request

Surya Yarramilli <surya.yarramilli@oracle.com> Mon, 04 November 2013 16:50 UTC

Return-Path: <surya.yarramilli@oracle.com>
X-Original-To: sipcore@ietfa.amsl.com
Delivered-To: sipcore@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E7CC011E82DA for <sipcore@ietfa.amsl.com>; Mon, 4 Nov 2013 08:50:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level:
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eovkc8SV1lWZ for <sipcore@ietfa.amsl.com>; Mon, 4 Nov 2013 08:50:18 -0800 (PST)
Received: from aserp1040.oracle.com (aserp1040.oracle.com [141.146.126.69]) by ietfa.amsl.com (Postfix) with ESMTP id B14E121E81BC for <sipcore@ietf.org>; Mon, 4 Nov 2013 08:48:17 -0800 (PST)
Received: from ucsinet21.oracle.com (ucsinet21.oracle.com [156.151.31.93]) by aserp1040.oracle.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.1) with ESMTP id rA4GmGPa001323 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for <sipcore@ietf.org>; Mon, 4 Nov 2013 16:48:17 GMT
Received: from aserz7022.oracle.com (aserz7022.oracle.com [141.146.126.231]) by ucsinet21.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id rA4GmFXE027068 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <sipcore@ietf.org>; Mon, 4 Nov 2013 16:48:16 GMT
Received: from abhmp0019.oracle.com (abhmp0019.oracle.com [141.146.116.25]) by aserz7022.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id rA4GmFvh015319 for <sipcore@ietf.org>; Mon, 4 Nov 2013 16:48:15 GMT
MIME-Version: 1.0
Message-ID: <f6e119cd-5b30-459e-a538-8e6d37acc971@default>
Date: Mon, 04 Nov 2013 08:48:12 -0800
From: Surya Yarramilli <surya.yarramilli@oracle.com>
Sender: Surya Yarramilli <surya.yarramilli@oracle.com>
To: sipcore@ietf.org
X-Priority: 3
X-Mailer: Oracle Beehive Extensions for Outlook 2.0.1.8 (707110) [OL 12.0.6680.5000 (x86)]
Content-Type: multipart/alternative; boundary="__138358369495038913abhmp0019.oracle.com"
X-Source-IP: ucsinet21.oracle.com [156.151.31.93]
X-Mailman-Approved-At: Mon, 04 Nov 2013 09:58:19 -0800
Subject: [sipcore] Multiple P-Access-Network-Info header in the same SIP request
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: SIP Core Working Group <sipcore.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sipcore>, <mailto:sipcore-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sipcore>
List-Post: <mailto:sipcore@ietf.org>
List-Help: <mailto:sipcore-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sipcore>, <mailto:sipcore-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Nov 2013 17:21:55 -0000

Hi,

 

According to RFC specification this header(PANI) should be a single valued header, while in 3GPP specification, this header is defined as multiple valued header. 

 

Normally we build our software following SIP RFC specification. Actually even inside the 3GPP specification the same RFC specification also has been referenced.
But there are differences between 3GPP spec and the RFC even though the 3GPP spec references the same RFC.  So clearly there is an ambiguity here.

 

Could you bring some clarity on the SIP RFC spec and  3GPP spec?

 

Thanks and Regards,

Surya Yarramilli | Principal Software Engineer
ORACLE

v2.23.0 | Report a Bug | By Email