Icecast - Feb 2001 - RTP Payload for Vorbis Audio: draft-moffitt-vorbis-rtp-00.txt

Hi Jack,
> You're comments are welcome.
Here they are...

3.1 RTP Header Payload Type (PT):
I don't see an alternative to using a value of the dynamic range (96-127).
IIRC, other ranger are reserved for fixed values assigned by IETF.

"A dynamic payload type MUST be used - i.e., one in the range
[96,127]."

3.2 Payload Header
If you refer to RFC2119, please keep the capital letters of your key
words.

"Reserved, MUST be set to zero" and "this number SHOULD be
0".

4 Frame Packetizing
Is it possible to devide these long packets which need fragmentation into
smaller ADUs (see [3] RFC2736: minimum units of error recovery)?

5 Open Issues
Some of these are discussed in RFC2736, in particular the need for "Out of
band signalling" of codec parameters.

6 Security Considerations
Spelling error "Becase" -> "Because"

8 References:
Your reference to RFC2119 of 1 Introduction got lost.

 [1]  Bradner, S., "Key words for use in RFCs to Indicate Requirement
      Levels", RFC 2119, BCP 14, March 1997.

[1] in 6 Security Considerations will then be [2]:

 [2]  Schulzrinne, H., Casner, S., Frederick, R., and V. Jacobson,
      "RTP: A transport protocol for real-time applications," RFC
1889,
      January 1996.

Add this one:

 [3]  Handley, M.
      "Guidelines for Writers of RTP Payload Format Specifications"
      RFC 2736, December 1999.

Cheers,
Jochen

--- >8 ----
List archives:  http://www.xiph.org/archives/
icecast project homepage: http://www.icecast.org/
To unsubscribe from this list, send a message to 'icecast-request at
xiph.org'
containing only the word 'unsubscribe' in the body.  No subject is
needed.
Unsubscribe messages sent to the list will be ignored/filtered.