search for: rfc4566

...RFC4288 [RFC4288] > > 4.1.1. Registration of media type audio/speex > > Media type name: audio > > Media subtype name: speex > > Required parameters: > > None > > Optional parameters: > > ptime: SHOULD be a multiple of 20 msec [RFC4566] > > maxptime: SHOULD be a multiple of 20 msec [RFC4566] > > Encoding considerations: > > This media type is framed and binary, see section 4.8 in > [RFC4288]. > > Security considerations: See Section 6 > > Interoperability considerat...

...s payload format. The section registers the media types, as per RFC4288 [RFC4288] 4.1.1. Registration of media type audio/speex Media type name: audio Media subtype name: speex Required parameters: None Optional parameters: ptime: SHOULD be a multiple of 20 msec [RFC4566] maxptime: SHOULD be a multiple of 20 msec [RFC4566] Encoding considerations: This media type is framed and binary, see section 4.8 in [RFC4288]. Security considerations: See Section 6 Interoperability considerations: None. Published specification: RFC XXX...

Do not forget to add the "Copying conditions" to the RFC. Check http://wiki.debian.org/NonFreeIETFDocuments That page contains a section titled "Template for RFC authors to release additional rights". To follow that guideline a section like the following should be added: x. Copying conditions The author(s) agree to grant third parties the irrevocable right to

...s payload format. The section registers the media types, as per RFC4288 [RFC4288] 4.1.1. Registration of media type audio/speex Media type name: audio Media subtype name: speex Required parameters: None Optional parameters: ptime: SHOULD be a multiple of 20 msec [RFC4566] maxptime: SHOULD be a multiple of 20 msec [RFC4566] Encoding considerations: This media type is framed and binary, see section 4.8 in [RFC4288]. Security considerations: See Section 6 Interoperability considerations: None. Published specification: RFC XXX...

...deo Transport working group delegated from the IESG. Herlein, et al. Expires October 24, 2007 [Page 10] Internet-Draft Speex April 2007 5. SDP usage of Speex When conveying information by SDP [RFC4566], the encoding name MUST be set to "speex". An example of the media representation in SDP for offering a single channel of Speex at 8000 samples per second might be: m=audio 8088 RTP/AVP 97 a=rtpmap:97 speex/8000 Note that the RTP payload type code...

...000 or 32000: I would recommend to make it clear: The value of the sampling frequency MUST be either 8000 for narrow band operation, 16000 for wide band operation, and 32000 for ultra-wide band operation. ptime: duration of each packet in milliseconds. http://www.ietf.org/rfc/rfc4566.txt specify that in the ptime definition: "it is intended as a recommendation for the encoding/packetisation of audio". Thus, I would recommend to specify the same text as in rfc3264 for sdp offer/answer model: "If the ptime attribute is present for a stream, it indicates the...

...ear: > > The value of the sampling frequency MUST be either 8000 for narrow band > operation, 16000 for wide band operation, and 32000 for ultra-wide > band operation. Agreed. > > ptime: duration of each packet in milliseconds. > > http://www.ietf.org/rfc/rfc4566.txt specify that in the ptime definition: > "it is intended as a recommendation for the encoding/packetisation of > audio". Thus, I would recommend to specify the same text as in rfc3264 > for sdp offer/answer model: > > "If the ptime attribute is present for a str...

...of the sampling frequency MUST be either 8000 for narrow band >> operation, 16000 for wide band operation, and 32000 for ultra-wide >> band operation. > > Agreed. Good. >> ptime: duration of each packet in milliseconds. >> >> http://www.ietf.org/rfc/rfc4566.txt specify that in the ptime definition: >> "it is intended as a recommendation for the encoding/packetisation of >> audio". Thus, I would recommend to specify the same text as in rfc3264 >> for sdp offer/answer model: >> >> "If the ptime attribute i...