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

worley@ariadne.com (Dale R. Worley) Sat, 18 November 2017 02:54 UTC

Return-Path: <worley@alum.mit.edu>
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 01765126D0C for <sipcore@ietfa.amsl.com>; Fri, 17 Nov 2017 18:54:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.934
X-Spam-Level:
X-Spam-Status: No, score=-1.934 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_SOFTFAIL=0.665] autolearn=no 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 7z3yfGgwNJe9 for <sipcore@ietfa.amsl.com>; Fri, 17 Nov 2017 18:54:56 -0800 (PST)
Received: from resqmta-ch2-12v.sys.comcast.net (resqmta-ch2-12v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:44]) (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 C7B62126BF3 for <sipcore@ietf.org>; Fri, 17 Nov 2017 18:54:56 -0800 (PST)
Received: from resomta-ch2-13v.sys.comcast.net ([69.252.207.109]) by resqmta-ch2-12v.sys.comcast.net with ESMTP id FtHJediEshVw8FtHTeAR6f; Sat, 18 Nov 2017 02:54:55 +0000
Received: from hobgoblin.ariadne.com ([IPv6:2601:192:4603:9471:222:fbff:fe91:d396]) by resomta-ch2-13v.sys.comcast.net with SMTP id FtHSeYzzHbSXWFtHSeJzNj; Sat, 18 Nov 2017 02:54:55 +0000
Received: from hobgoblin.ariadne.com (hobgoblin.ariadne.com [127.0.0.1]) by hobgoblin.ariadne.com (8.14.7/8.14.7) with ESMTP id vAI2srAG015172; Fri, 17 Nov 2017 21:54:53 -0500
Received: (from worley@localhost) by hobgoblin.ariadne.com (8.14.7/8.14.7/Submit) id vAI2srHb015169; Fri, 17 Nov 2017 21:54:53 -0500
X-Authentication-Warning: hobgoblin.ariadne.com: worley set sender to worley@alum.mit.edu using -f
From: worley@ariadne.com
To: Ben Campbell <ben@nostrum.com>
Cc: sipcore@ietf.org
In-Reply-To: <05021C56-903E-46A2-9CC0-DD07C3147EC2@nostrum.com> (ben@nostrum.com)
Sender: worley@ariadne.com
Date: Fri, 17 Nov 2017 21:54:53 -0500
Message-ID: <87ine8fg8y.fsf@hobgoblin.ariadne.com>
X-CMAE-Envelope: MS4wfOMM3logH5qiwCAGzl04J08fpJoQWOli/f4fjssUYwzm9kbobqf/JvCUnpTq94LidlPYqY+uWkHCIJtTZv1FdaddyrHIhuWK2ZYPlQe/JN5v4vZ3TQ8u vwGKMJbX38IDzPbdV6jH0wdM0zAFRUOOpYvCeSlyxu3JrvCLNxXZngUGhyXP7rUHOv9rq6XfebmNew==
Archived-At: <https://mailarchive.ietf.org/arch/msg/sipcore/1zEtvc_d0eQ42uCNPdS-gJC7r2c>
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: Sat, 18 Nov 2017 02:54:58 -0000

>> The following errata report has been submitted for RFC3323,
>> "A Privacy Mechanism for the Session Initiation Protocol (SIP)".

>> Original Text
>> -------------
>> Privacy-hdr  =  "Privacy" HCOLON priv-value *(";" priv-value)
>> 
>> 
>> Corrected Text
>> --------------
>> Privacy-hdr  =  "Privacy" HCOLON priv-value *("," priv-value)

My suspicion is that the syntax with semicolon was chosen specifically
to prevent the rule for combining header fields from being applicable.
This ensures that if the UA sends a single Privacy header with multiple
values, no intermediary can split it into multiple Privacy headers.
(The text only speaks of a single Privacy header, never multiple ones.)

But as Paul says, (1) it should be SEMI and (2) we must pay attention to
what has been deployed.

Dale