Re: [sipcore] FW: [Technical Errata Reported] RFC3261 (4553)

["A. Jean Mahoney" <[e-mail]>]

Hi Christer,

+Ben and +sipcore since errata aren't sent automatically to the list. 
The AD pulls the levers on submitted errata.

Thanks,

Jean


On 12/5/15 9:42 AM, Christer Holmberg wrote:
> Hi chairs,
>
> I hope that we can move ahead with this errata asap. It may seem like a minor issue, but it is actually causing headaches in deployments, and within the test specification community.
>
> People supported the suggestion on the list, and nobody objected, so I assume it should not cause any problems.
>
> Regards,
>
> Christer
>
>
> -----Original Message-----
> From: RFC Errata System [mailto:[e-mail]]
> Sent: 04 December 2015 16:07
> To: [e-mail]; [e-mail]; Gonzalo Camarillo <[e-mail]>; [e-mail]; [e-mail]; [e-mail]; [e-mail]; [e-mail]; [e-mail]; [e-mail]; [e-mail]; [e-mail]
> Cc: Christer Holmberg <[e-mail]>; [e-mail]
> Subject: [Technical Errata Reported] RFC3261 (4553)
>
> The following errata report has been submitted for RFC3261,
> "SIP: Session Initiation Protocol".
>
> --------------------------------------
> You may review the report below and at:
> http://www.rfc-editor.org/errata_search.php?rfc=3261&eid=4553
>
> --------------------------------------
> Type: Technical
> Reported by: Christer Holmberg <[e-mail]>
>
> Section: 20.11
>
> Original Text
> -------------
> The handling parameter, handling-param, describes how the UAS should react if it receives a message body whose content type or disposition type it does not understand.  The parameter has defined values of \\"optional\\" and \\"required\\".  If the handling parameter is missing, the value \\"required\\" SHOULD be assumed.  The handling parameter is described in RFC 3204 [19].
>
>
> Corrected Text
> --------------
> The handling parameter, handling-param, describes how the UAS should react if it receives a message body whose content type or disposition type it does not understand.  The parameter has defined values of \\"optional\\" and \\"required\\".  If the handling parameter is missing, or if the Content-Disposition header field is missing, the value \\"required\\"
> MUST be assumed.  The handling parameter is described in RFC 3204 [19].
>
>
> Notes
> -----
> SIPCORE discussion: https://mailarchive.ietf.org/arch/msg/sipcore/bn-pRgDyGL2FP_M7eYpyT35zNp4
>
> 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.
>
> --------------------------------------
> RFC3261 (draft-ietf-sip-rfc2543bis-09)
> --------------------------------------
> Title               : SIP: Session Initiation Protocol
> Publication Date    : June 2002
> Author(s)           : J. Rosenberg, H. Schulzrinne, G. Camarillo, A. Johnston, J. Peterson, R. Sparks, M. Handley, E. Schooler
> Category            : PROPOSED STANDARD
> Source              : Session Initiation Protocol
> Area                : Real-time Applications and Infrastructure
> Stream              : IETF
> Verifying Party     : IESG
>