Re: [Technical Errata Reported] RFC2326 (5079)

Magnus Westerlund <[email protected]> Fri, 25 Aug 2017 10:45:29 +0200
Newsgroups gmane.ietf.mmusic
Message-ID <[email protected]>
Hi,

Thanks for reporting, however considering how many issues there are in 
RFC 2326, and why RFC 7826 was produced, I frankly don't know if its 
worth accepting this errata or not.

The errata is clearly right in that the RFC is wrong. If one follows the 
format for text/parameters defined in RTSP 2.0: 
https://datatracker.ietf.org/doc/rfc7826/ then there should be CRLF at 
the end of each line, and there are no EOF marker. Thus the length 
should be: 26. So maybe with that edit it is simplest to accept it.

Cheers

Magnus Westerlund



Den 2017-08-08 kl. 18:52, skrev RFC Errata System:
> The following errata report has been submitted for RFC2326,
> "Real Time Streaming Protocol (RTSP)".
>
> --------------------------------------
> You may review the report below and at:
> http://www.rfc-editor.org/errata/eid5079
>
> --------------------------------------
> Type: Technical
> Reported by: Vadim Zhukov <[email protected]>
>
> Section: 10.8
>
> Original Text
> -------------
>       S->C: GET_PARAMETER rtsp://example.com/fizzle/foo RTSP/1.0
>             CSeq: 431
>             Content-Type: text/parameters
>             Session: 12345678
>             Content-Length: 15
>
>             packets_received
>             jitter
>
> Corrected Text
> --------------
>       S->C: GET_PARAMETER rtsp://example.com/fizzle/foo RTSP/1.0
>             CSeq: 431
>             Content-Type: text/parameters
>             Session: 12345678
>             Content-Length: 24
>
>             packets_received
>             jitter
>
> Notes
> -----
> The Content-Length value is wrong, it should be either 24 (as proposed) or 26, depending on end-of-line marker used for message content.
>
> 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
> can log in to change the status and edit the report, if necessary.
>
> --------------------------------------
> RFC2326 (no draft string recorded)
> --------------------------------------
> Title               : Real Time Streaming Protocol (RTSP)
> Publication Date    : April 1998
> Author(s)           : H. Schulzrinne, A. Rao, R. Lanphier
> Category            : PROPOSED STANDARD
> Source              : Multiparty Multimedia Session Control RAI
> Area                : Real-time Applications and Infrastructure
> Stream              : IETF
> Verifying Party     : IESG
>
> _______________________________________________
> mmusic mailing list
> [email protected]
> https://www.ietf.org/mailman/listinfo/mmusic

-- 

Magnus Westerlund

----------------------------------------------------------------------
Media Technologies, Ericsson Research
----------------------------------------------------------------------
Ericsson AB                 | Phone  +46 10 7148287
Torshamnsgatan 23           | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden | mailto: [email protected]
----------------------------------------------------------------------

_______________________________________________
mmusic mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/mmusic
smime.p7s (application/pkcs7-signature, 4 KB) - not displayed