Re: [sipcore] Fwd: [Technical Errata Reported] RFC3323 (5184)

Christer Holmberg <christer.holmberg@ericsson.com> Fri, 17 November 2017 09:52 UTC

Return-Path: <christer.holmberg@ericsson.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 2C9D8126C25 for <sipcore@ietfa.amsl.com>; Fri, 17 Nov 2017 01:52:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level:
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-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 Wkft2ru_Qirz for <sipcore@ietfa.amsl.com>; Fri, 17 Nov 2017 01:52:45 -0800 (PST)
Received: from sesbmg22.ericsson.net (sesbmg22.ericsson.net [193.180.251.48]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 88F3C124D6C for <sipcore@ietf.org>; Fri, 17 Nov 2017 01:52:45 -0800 (PST)
X-AuditID: c1b4fb30-df9f99c000002554-43-5a0eb16beaf2
Received: from ESESSHC011.ericsson.se (Unknown_Domain [153.88.183.51]) by sesbmg22.ericsson.net (Symantec Mail Security) with SMTP id 96.57.09556.B61BE0A5; Fri, 17 Nov 2017 10:52:43 +0100 (CET)
Received: from ESESSMB102.ericsson.se ([169.254.2.99]) by ESESSHC011.ericsson.se ([153.88.183.51]) with mapi id 14.03.0352.000; Fri, 17 Nov 2017 10:52:36 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>, "sipcore@ietf.org" <sipcore@ietf.org>
Thread-Topic: [sipcore] Fwd: [Technical Errata Reported] RFC3323 (5184)
Thread-Index: AQHTXz5Uw8dI58mDOEuhj94C2xcC0qMYAwaAgABQrCA=
Date: Fri, 17 Nov 2017 09:52:36 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B6BFE453C@ESESSMB102.ericsson.se>
References: <20171116022038.047B6B8104D@rfc-editor.org> <05021C56-903E-46A2-9CC0-DD07C3147EC2@nostrum.com> <a5295754-80a2-a8a8-4d5a-8a7869a001a1@alum.mit.edu>
In-Reply-To: <a5295754-80a2-a8a8-4d5a-8a7869a001a1@alum.mit.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [153.88.183.154]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrPLMWRmVeSWpSXmKPExsUyM2K7sW72Rr4og/03DSxWbDjAavH1xyY2 ByaPv+8/MHksWfKTKYApissmJTUnsyy1SN8ugSvjwsLrLAVHWCqWbNnN1sC4haWLkZNDQsBE oun8V+YuRi4OIYHDjBJ7ty9hhXAWM0qserAVKMPBwSZgIdH9TxukQUQgUOLqkgnMILawgJtE 640OVoi4u0THw0YmCNtKYs68z2A2i4CqxOq5e8BsXgFfictLDzNCzF/EKNG95SRYM6eAg8ST JZvAbEYBMYnvp9aANTALiEvcejKfCeJSAYkle84zQ9iiEi8f/2OFsJUkFt0GWcYBVK8psX6X PkSrosSU7ofsEHsFJU7OfMIygVFkFpKpsxA6ZiHpmIWkYwEjyypG0eLU4qTcdCMjvdSizOTi 4vw8vbzUkk2MwGg4uOW3wQ7Gl88dDzEKcDAq8fAyrOGLEmJNLCuuzD3EKMHBrCTCO2M5UIg3 JbGyKrUoP76oNCe1+BCjNAeLkjjvSU/eKCGB9MSS1OzU1ILUIpgsEwenVAPjokpZ3b4XU8XL ovY4fPG76bzXIs7u6927LE0bHkyYecxB5+mnUwyypp9jo371/NksnKkltZqXZc/XjQEyeoV3 OdbOO68d/pRNV7t+n9m8DQHrhPu3L+RuqL6X68FzZUP5jymMHxnPKElkze/fdf7+8r+e0k9P m7YJuSQ43Gzlm9o1u4jn9/IyJZbijERDLeai4kQAU+HPpIICAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/sipcore/xFpMQrorC8_eZTBzw0iq8jQQX-Y>
Subject: Re: [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 09:52:47 -0000

Hi,

...

> BUT given the late date that this has come to light much concern must be paid to what has been 
> deployed. I looked (not very hard) for published examples that have multiple privacy values, but didn't find any.

I believe there are cases with multiple values. It's a little difficult for me to look for them while in Singapore, but once I'm back in office it will be easier.

Regards,

Christer