[sipcore] Misalignments between the P- header definitions in RFC 3455, RFC 7315 and 3GPP TS 24.229: P-Visited-Network-ID
Christer Holmberg <christer.holmberg@ericsson.com> Thu, 03 December 2015 11:43 UTC
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: sipcore@ietfa.amsl.com
Delivered-To: sipcore@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1FCA51B33F6 for <sipcore@ietfa.amsl.com>; Thu, 3 Dec 2015 03:43:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3ewTLxug5swC for <sipcore@ietfa.amsl.com>; Thu, 3 Dec 2015 03:43:23 -0800 (PST)
Received: from sessmg22.ericsson.net (sessmg22.ericsson.net [193.180.251.58]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 99BD71B33F4 for <sipcore@ietf.org>; Thu, 3 Dec 2015 03:43:22 -0800 (PST)
X-AuditID: c1b4fb3a-f79df6d0000013b1-a8-56602ad8a188
Received: from ESESSHC024.ericsson.se (Unknown_Domain [153.88.183.90]) by sessmg22.ericsson.net (Symantec Mail Security) with SMTP id E7.6B.05041.8DA20665; Thu, 3 Dec 2015 12:43:20 +0100 (CET)
Received: from ESESSMB209.ericsson.se ([169.254.9.142]) by ESESSHC024.ericsson.se ([153.88.183.90]) with mapi id 14.03.0248.002; Thu, 3 Dec 2015 12:43:19 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: SIPCORE <sipcore@ietf.org>
Thread-Topic: Misalignments between the P- header definitions in RFC 3455, RFC 7315 and 3GPP TS 24.229: P-Visited-Network-ID
Thread-Index: AdEtvjAFN3DP+SmxT12yXvf2PtW+sAAAXi7A
Date: Thu, 03 Dec 2015 11:43:19 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B37C7CDC8@ESESSMB209.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [153.88.183.17]
Content-Type: multipart/alternative; boundary="_000_7594FB04B1934943A5C02806D1A2204B37C7CDC8ESESSMB209erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrHLMWRmVeSWpSXmKPExsUyM2J7lO4NrYQwg869ZhZff2xic2D0WLLk J1MAYxSXTUpqTmZZapG+XQJXRuvujawFm2wrLh/ay9rA2GjWxcjJISFgInFu3m5GCFtM4sK9 9WxdjFwcQgKHGSUmH37DBOEsZpRYsfMScxcjBwebgIVE9z9tEFNEQE5i9o0YkF5hgUqJPXM/ soHYIgJ1Eq/W7WSHsI0k9r/7ChZnEVCR2NZ3E8zmFfCVmDD5PwuIzQi09/upNUwgNrOAuMSt J/OZIO4RkFiy5zwzhC0q8fLxP1aQtRICihLL++VATGaBfInGgwIQEwUlTs58wjKBUWgWkkGz EKpmIamCKNGRWLD7ExuErS2xbOFrZhj7zIHHTMjiCxjZVzGKFqcWF+emGxnppRZlJhcX5+fp 5aWWbGIExsLBLb+tdjAefO54iFGAg1GJh/dDeXyYEGtiWXFl7iFGCQ5mJRHeb2uBQrwpiZVV qUX58UWlOanFhxilOViUxHmbmR6ECgmkJ5akZqemFqQWwWSZODilGhgzDyVUPZvN6Ln2SJTf kne9PKndH+e3/TidOem1kM75FJW9eq/7p02se8yr9YD592H+b55mxl19B034Mxf6efG4n19g Upy5rf3KxB27PX/JH1v1/JyTkP29i90eLG3lGZXrq2S5w9Yctu14Jt9RcFn1kFG+QT277bfd U/iOrVCxEzQ+vGeG3XQlluKMREMt5qLiRABRfL/WgQIAAA==
Archived-At: <http://mailarchive.ietf.org/arch/msg/sipcore/f-sfqpQuFTKQd9NJeAjqq0RUuRM>
Subject: [sipcore] Misalignments between the P- header definitions in RFC 3455, RFC 7315 and 3GPP TS 24.229: P-Visited-Network-ID
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.15
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: <https://mailarchive.ietf.org/arch/browse/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: Thu, 03 Dec 2015 11:43:25 -0000
Hi,
3GPP has been studying possible misalignments between the P- header definitions in RFC 3455, RFC 7315 and 3GPP TS 24.229.
Rather than posting all the issues in a single e-mail, I will send e-mails per header field. This e-mail is about P-Visited-Network-ID (PCNI), where one issue was identified.
Issue 1) RFC 7315 allows PCNI in requests and responses.
RFC 3455 and 3GPP TS 24.229 allow PCNI in requests only. However, RFC 7315 allows PCNI in both requests and responses..
Chapters 4.3.2, 4.3.2.1 and 4.3.2.2 only talks about PCNI in requests.
However, chapter 5.7 says:
"The P-Visited-Network-ID header field can appear in all
SIP methods except ACK, BYE, and CANCEL and all responses."
I assume this is just a bug in section 5.7, which could be fixed with an errata:
OLD TEXT:
"The P-Visited-Network-ID header field can appear in all
SIP methods except ACK, BYE, and CANCEL and all responses."
NEW TEXT:
"The P-Visited-Network-ID header field can appear in all
SIP methods except ACK, BYE, and CANCEL."
Regards,
Christer
- [sipcore] Misalignments between the P- header def… Christer Holmberg