Search the Archives

RFC 2327: In section 6 (SDP Specification), where the RFC discusses...

Reader comments:

Comment by Tom Gerke
Submitted on 5/19/2005
Related RFC: RFC 2327
Rating: Not yet rated	Rate this comment:
In section 6 (SDP Specification), where the RFC discusses the format of <session ID> in the "o=" field, it reads as follows:"<session id> is a numeric string such that the tuple of <username>, <session id>, <network type>, <address type> and <address> form a globally unique identifier for the session.The method of <session id> allocation is up to the creating tool, but it has been suggested that a Network Time Protocol (NTP) timestamp be used to ensure uniqueness [1]."It might be safer to state that <session ID> is a 'positive' numeric string. As it's conceivable that implementors could be using "%d" formating, and that their session ID could go over the value 2^31. This would cause a negative number for the session ID. The resultant preceeding "-" on that negative number might make it difficult for parsers expecting "-" as a possibility for the <username>.

FAQS.ORG makes no guarantees as to the accuracy of the posts. Each post is the personal opinion of the poster. These posts are not intended to substitute for medical, tax, legal, investment, accounting, or other professional advice. FAQS.ORG does not endorse any opinion or any product or service mentioned mentioned in these posts.

<< Back to: RFC 2327