Re: [sipcore] [Technical Errata Reported] RFCs 3515, 5502, 5360, ...

ISTM that it would be good to discuss all of these together, and perhaps 
solicit pointers to any others that need a similar fix.

	Thanks,
	Paul

On 3/31/16 7:36 AM, Brett Tate wrote:
> Copying sipcore since similar errata being discussed.
>
>> -----Original Message-----
>> From: Brett Tate [mailto:brett@broadsoft.com]
>> Sent: Tuesday, March 29, 2016 10:23 AM
>> To: 'RFC Errata System'; 'HansErik.van.Elburg@ericsson.com';
> 'iesg@ietf.org'
>> Subject: RE: [Technical Errata Reported] RFC5502 (4648)
>>
>> 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 9:54 AM
>>> To: HansErik.van.Elburg@ericsson.com; iesg@ietf.org
>>> Cc: brett@broadsoft.com; rfc-editor@rfc-editor.org
>>> Subject: [Technical Errata Reported] RFC5502 (4648)
>>>
>>> The following errata report has been submitted for RFC5502, "The SIP
>>> P- Served-User Private-Header (P-Header) for the 3GPP IP Multimedia
>>> (IM) Core Network (CN) Subsystem".
>>>
>>> --------------------------------------
>>> You may review the report below and at:
>>> http://www.rfc-editor.org/errata_search.php?rfc=5502&eid=4648
>>>
>>> --------------------------------------
>>> Type: Technical
>>> Reported by: Brett Tate <brett@broadsoft.com>
>>>
>>> Section: 6
>>>
>>> Original Text
>>> -------------
>>> EQUAL, HCOLON, SEMI, name-addr, addr-spec, and generic-param are
>>> defined in RFC 3261 [2].
>>>
>>>
>>> Corrected Text
>>> --------------
>>> EQUAL, HCOLON, SEMI, name-addr, addr-spec, and generic-param are
>>> defined in RFC 3261 [2].
>>>
>>> If the URI contains a comma, question mark or semicolon, the URI MUST
>>> be enclosed in angle brackets (< and >).
>>>
>>> Notes
>>> -----
>>> If addr-spec is used when there are parameters, it is ambiguous if the
>>> parameters are URI parameters or served-user-param.  For consistency
>>> with RFC
>>> 3261 section 20, the same bracket rule is indicated even if comma and
>>> question mark do not cause an issue.
>>>
>>> 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.
>>>
>>> --------------------------------------
>>> RFC5502 (draft-vanelburg-sipping-served-user-08)
>>> --------------------------------------
>>> Title               : The SIP P-Served-User Private-Header (P-Header)
> for
>> the
>>> 3GPP IP Multimedia (IM) Core Network (CN) Subsystem
>>> Publication Date    : April 2009
>>> Author(s)           : J. van Elburg
>>> Category            : INFORMATIONAL
>>> Source              : IETF - NON WORKING GROUP
>>> Area                : N/A
>>> Stream              : IETF
>>> Verifying Party     : IESG
>
> _______________________________________________
> sipcore mailing list
> sipcore@ietf.org
> https://www.ietf.org/mailman/listinfo/sipcore
>