[sipcore] Fwd: [Technical Errata Reported] RFC3323 (5184)
Ben Campbell <ben@nostrum.com> Fri, 17 November 2017 00:52 UTC
Return-Path: <ben@nostrum.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 9B446126BF0 for <sipcore@ietfa.amsl.com>; Thu, 16 Nov 2017 16:52:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.877
X-Spam-Level:
X-Spam-Status: No, score=-1.877 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 860pGa1QeDit for <sipcore@ietfa.amsl.com>; Thu, 16 Nov 2017 16:52:17 -0800 (PST)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 14AC3126CB6 for <sipcore@ietf.org>; Thu, 16 Nov 2017 16:52:10 -0800 (PST)
Received: from [10.178.73.221] (mobile-166-170-37-195.mycingular.net [166.170.37.195]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id vAH0q62E026396 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for <sipcore@ietf.org>; Thu, 16 Nov 2017 18:52:10 -0600 (CST) (envelope-from ben@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host mobile-166-170-37-195.mycingular.net [166.170.37.195] claimed to be [10.178.73.221]
From: Ben Campbell <ben@nostrum.com>
Content-Type: multipart/alternative; boundary="Apple-Mail-6592039E-7380-4450-B44B-270379212C85"
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (1.0)
Date: Fri, 17 Nov 2017 08:52:00 +0800
Message-Id: <05021C56-903E-46A2-9CC0-DD07C3147EC2@nostrum.com>
References: <20171116022038.047B6B8104D@rfc-editor.org>
To: sipcore@ietf.org
X-Mailer: iPhone Mail (15B93)
Archived-At: <https://mailarchive.ietf.org/arch/msg/sipcore/jsQ_c5bfJLc6U6Bt7i9GrSuUrAY>
Subject: [sipcore] Fwd: [Technical Errata Reported] RFC3323 (5184)
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.22
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: Fri, 17 Nov 2017 00:52:19 -0000
Hi, Does anyone in sipcore have thoughts on this? Thanks, Ben. Begin forwarded message: > From: RFC Errata System <rfc-editor@rfc-editor.org> > Date: November 16, 2017 at 10:20:38 AM GMT+8 > To: jon.peterson@neustar.biz, ben@nostrum.com, aamelnikov@fastmail.fm, adam@nostrum.com, dean.willis@softarmor.com, drage@alcatel-lucent.com > Cc: isly33@gmail.com, rfc-editor@rfc-editor.org > Subject: [Technical Errata Reported] RFC3323 (5184) > > The following errata report has been submitted for RFC3323, > "A Privacy Mechanism for the Session Initiation Protocol (SIP)". > > -------------------------------------- > You may review the report below and at: > http://www.rfc-editor.org/errata/eid5184 > > -------------------------------------- > Type: Technical > Reported by: DONG O YI <isly33@gmail.com> > > Section: 4.2 Expre... > > Original Text > ------------- > Privacy-hdr = "Privacy" HCOLON priv-value *(";" priv-value) > > > Corrected Text > -------------- > Privacy-hdr = "Privacy" HCOLON priv-value *("," priv-value) > > > Notes > ----- > RFC3261 says, > > Specifically, any SIP header whose grammar is of the form > > header = "header-name" HCOLON header-value *(COMMA header-value) > > allows for combining header fields of the same name into a comma- > separated list. > > So, RFC3323 conflicts RFC3261. > > Instructions: > ------------- > This erratum is currently posted as "Reported". If necessary, please > use "Reply All" to discuss whether it should be verified or > rejected. When a decision is reached, the verifying party > can log in to change the status and edit the report, if necessary. > > -------------------------------------- > RFC3323 (draft-ietf-sip-privacy-general-01) > -------------------------------------- > Title : A Privacy Mechanism for the Session Initiation Protocol (SIP) > Publication Date : November 2002 > Author(s) : J. Peterson > Category : PROPOSED STANDARD > Source : Session Initiation Protocol > Area : Real-time Applications and Infrastructure > Stream : IETF > Verifying Party : IESG
- [sipcore] Fwd: [Technical Errata Reported] RFC332… Ben Campbell
- Re: [sipcore] Fwd: [Technical Errata Reported] RF… Christer Holmberg
- Re: [sipcore] [EXTERNAL] Fwd: [Technical Errata R… Peterson, Jon
- Re: [sipcore] Fwd: [Technical Errata Reported] RF… Paul Kyzivat
- Re: [sipcore] Fwd: [Technical Errata Reported] RF… Christer Holmberg
- Re: [sipcore] Fwd: [Technical Errata Reported] RF… R.Jesske
- Re: [sipcore] Fwd: [Technical Errata Reported] RF… R.Jesske
- Re: [sipcore] Fwd: [Technical Errata Reported] RF… Dale R. Worley
- Re: [sipcore] Fwd: [Technical Errata Reported] RF… Christer Holmberg
- Re: [sipcore] Fwd: [Technical Errata Reported] RF… Dean Willis