[Editorial Errata Reported] RFC4244 (2608)

[RFC Errata System]

The following errata report has been submitted for RFC4244,
"An Extension to the Session Initiation Protocol (SIP) for Request History Information".

--------------------------------------
You may review the report below and at:
http://www.rfc-editor.org/errata_search.php?rfc=4244&eid=2608

--------------------------------------
Type: Editorial
Reported by: Hadriel Kaplan <***@acmepacket.com>

Section: 4.5

Original Text
-------------
History-Info: <sip:***@P1.example.com>;index=1,
<sip:***@P2.example.com>; index=1.1,
<sip:***@UA2.example.com?Reason=SIP;\
cause=408;text="RequestTimeout">;index=1.1.1,
<sip:***@UA3.example.com?Reason=SIP; \
cause=487;text="Request Terminated">; index=1.1.2,
<sip:***@UA4.example.com?Reason=SIP;\
cause=603;text="Decline">; index=1.1.3

Corrected Text
--------------
History-Info: <sip:***@P1.example.com>;index=1,
<sip:***@P2.example.com>; index=1.1,
<sip:***@UA2.example.com?Reason=SIP%3B\
cause%3D408%3Btext%3D%22RequestTimeout%22>;index=1.1.1,
<sip:***@UA3.example.com?Reason=SIP%3B\
cause%3D487%3Btext%3D%22Request%20Terminated%22>; index=1.1.2,
<sip:***@UA4.example.com?Reason=SIP%3B\
cause%3D603%3Btext%3D%22Decline%22>; index=1.1.3

Notes
-----
This is one of many incorrect examples in section 4.5, 4.5.1, 4.5.2, etc. The ";", "=", double-quotes, and space are not legal tokens in URI-embedded headers.

Instructions:
-------------
This errata 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.

--------------------------------------
RFC4244 (draft-ietf-sip-history-info-06)
--------------------------------------
Title : An Extension to the Session Initiation Protocol (SIP) for Request History Information
Publication Date : November 2005
Author(s) : M. Barnes, Ed.
Category : PROPOSED STANDARD
Source : Session Initiation Protocol
Area : Real-time Applications and Infrastructure
Stream : IETF
Verifying Party : IESG
_______________________________________________
Sip mailing list https://www.ietf.org/mailman/listinfo/sip
This list is essentially closed and only used for finishing old business.
Use sip-***@cs.columbia.edu for questions on how to develop a SIP implementation.
Use ***@ietf.org for new developments on the application of sip.
Use ***@ietf.org for issues related to maintenance of the core SIP specifications.