Subject: [MMUSIC] Rtspspec-bugs digest, Vol 1 #23 - 1 msg

From: [email-masked]
Date: Tue, 19 Feb 2002 12:33:11 -0800

This is an automatic digest of bugs submitted and changed on the RTSP bug tracker.  To see a list of bugs, visit:

http://sf.net/projects/rtspspec

When replying, please make your Subject line more specific than "Re: Rtspspec-bugs digest"

Today's Topics:

   1. [ rtspspec-Bugs-461083 ] Body w/o Content-Length clarification ([email-masked])

--__--__--

Message: 1
To: [email-masked]
From: [email-masked]
Date: Mon, 18 Feb 2002 16:52:22 -0800
Subject: [rtspspec-bugs] [ rtspspec-Bugs-461083 ] Body w/o Content-Length clarification

Bugs item #461083, was opened at 2001-09-12 18:50
You can respond by visiting: 
http://sourceforge.net/tracker/?func=detail&atid=377744&aid=461083&group_id=23194

Category: General
>Group: Fixed in CVS/Need WG Approval
Status: Open
Resolution: None
Priority: 5
Submitted By: Jason Lango (jasonlango)
Assigned to: Rob Lanphier (robla)
Summary: Body w/o Content-Length clarification

Initial Comment:
RFC 2326 says: 

4.4 Message Length

   When a message body is included with a message, the
length of that body is determined by one of the
following (in order of precedence):
 
   1.     Any response message which MUST NOT include a
message body
          (such as the 1xx, 204, and 304 responses) is
always terminated
          by the first empty line after the header
fields, regardless of
          the entity-header fields present in the
message. (Note: An
          empty line consists of only CRLF.)

   2.     If a Content-Length header field (section
12.14) is present,
          its value in bytes represents the length of
the message-body.
          If this header field is not present, a value
of zero is
          assumed.
 
   3.     By the server closing the connection.
(Closing the connection
          cannot be used to indicate the end of a
request body, since
          that would leave no possibility for the
server to send back a
          response.)
 
.. so it is saying that closing the connection is Ok to
indicate the length.

.. but then in section 12.14, it also says that the
Content-Length header MUST be sent.

The two sections should probably be made consistent.

Currently a popular RTSP server implementation (QTSS)
sends
"Connection: Close" followed by a message body for
certain
RTSP error status responses.

It might be worth requiring 'Connection: Close' in item
3 of
section 4.4 to reduce the ambiguity of whether or not a
compatible implementation may expect a response to
contain
a message body.

Alternatively it might be worth -not- saying that
message length
may be determined by the server closing the connection.

----------------------------------------------------------------------

>Comment By: Rob Lanphier (robla)
Date: 2002-02-18 16:52

Message:
Logged In: YES 
user_id=3796

Eliminated item #3 from the list.

----------------------------------------------------------------------

Comment By: David W. Walker (davidwwalker)
Date: 2002-01-28 14:28

Message:
Logged In: YES 
user_id=437905

RESOLUTION: (Jan 9, 2002 teleconference)

Eliminate implicit body-length via connection: close.  
COntactt David SInger on this issues and encourage f 
future participation.  Verify resolution is consistent 
with SIP specificaiton.

----------------------------------------------------------------------

Comment By: Rob Lanphier (robla)
Date: 2001-12-13 09:32

Message:
Logged In: YES 
user_id=3796

This is a potentially gnarly issue.  We agree that this is a problem that needs fixing.

We propose that we eliminate the option of implied Content-Length if possible (need 
to check with implementors on this....Darwin server in particular).  If we can't do 
that, require Connection: close, and change header definition.

----------------------------------------------------------------------

You can respond by visiting: 
http://sourceforge.net/tracker/?func=detail&atid=377744&aid=461083&group_id=23194

End of Rtspspec-bugs Digest

_______________________________________________
mmusic mailing list
[email-masked]
https://www1.ietf.org/mailman/listinfo/mmusic