Re: [sipcore] [Technical Errata Reported] RFC5318 (4651)

"Ben Campbell" <ben@nostrum.com> Wed, 30 March 2016 20:06 UTC

From: Ben Campbell <ben@nostrum.com>
To: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>, SIPCORE <sipcore@ietf.org>
Date: Wed, 30 Mar 2016 15:06:02 -0500
Message-ID: <B39D9D90-67F0-4A2C-89D9-F17A604B98CF@nostrum.com>
In-Reply-To: <56FBFAD5.1090806@ericsson.com>
References: <20160329160146.E71EB180004@rfc-editor.org> <edea3ca213d3545652f43b4ea4a50fa8@mail.gmail.com> <56FBFAD5.1090806@ericsson.com>
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/sipcore/SUl7XOamfL3LGtl5BKEuenURZYY>
Cc: Jani.Hautakorpi@ericsson.com, RFC Errata System <rfc-editor@rfc-editor.org>, iesg@ietf.org
Subject: Re: [sipcore] [Technical Errata Reported] RFC5318 (4651)
Precedence: list

(copying sipcore)

On 30 Mar 2016, at 11:12, Gonzalo Camarillo wrote:

> Hi Brett,
>
> I have the same comment as on the other document. I would talk about the
> name-addr form instead. Let's agree on the text we want to use for the
> three documents, since it is the same issue.
>
> Cheers,
>
> Gonzalo
>
> On 29/03/2016 7:06 PM, Brett Tate wrote:
>> Hi,
>>
>> My proposed resolution is similar to what occurred within RFC 3325 errata
>> (3744 and 3894).
>>
>>> -----Original Message-----
>>> From: RFC Errata System [mailto:rfc-editor@rfc-editor.org]
>>> Sent: Tuesday, March 29, 2016 12:02 PM
>>> To: Jani.Hautakorpi@ericsson.com; Gonzalo.Camarillo@ericsson.com;
>>> iesg@ietf.org
>>> Cc: brett@broadsoft.com; rfc-editor@rfc-editor.org
>>> Subject: [Technical Errata Reported] RFC5318 (4651)
>>>
>>> The following errata report has been submitted for RFC5318, "The Session
>>> Initiation Protocol (SIP) P-Refused-URI-List Private-Header (P-Header)".
>>>
>>> --------------------------------------
>>> You may review the report below and at:
>>> http://www.rfc-editor.org/errata_search.php?rfc=5318&eid=4651
>>>
>>> --------------------------------------
>>> Type: Technical
>>> Reported by: Brett Tate <brett@broadsoft.com>
>>>
>>> Section: 5
>>>
>>> Original Text
>>> -------------
>>> The members P-Header parameter MUST contain a cid-url, which is defined
>> in
>>> RFC 2392 [2].
>>>
>>> Corrected Text
>>> --------------
>>> The members P-Header parameter MUST contain a cid-url, which is defined
>> in
>>> RFC 2392 [2].
>>>
>>> If the URI contains a comma, question mark or semicolon, the URI MUST be
>>> enclosed in angle brackets (< and >).
>>>
>>> Notes
>>> -----
>>> Comma and semicolon can cause decode ambiguities when the header
>> contains
>>> addr-spec values instead of name-addr values.  For consistency with RFC
>> 3261
>>> section 20, the same bracket rule is indicated to resolve the ambiguity.
>>>
>>> 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 (IESG) can log in to change the
>>> status and edit the report, if necessary.
>>>
>>> --------------------------------------
>>> RFC5318 (draft-hautakorpi-sipping-uri-list-handling-refused-03)
>>> --------------------------------------
>>> Title               : The Session Initiation Protocol (SIP)
>> P-Refused-URI-
>>> List Private-Header (P-Header)
>>> Publication Date    : December 2008
>>> Author(s)           : J. Hautakorpi, G. Camarillo
>>> Category            : INFORMATIONAL
>>> Source              : IETF - NON WORKING GROUP
>>> Area                : N/A
>>> Stream              : IETF
>>> Verifying Party     : IESG

Re: [sipcore] [Technical Errata Reported] RFC5318… Ben Campbell
[sipcore] name-addr vs addr-spec requirements (wa… Robert Sparks