On Tue, 2006-01-17 at 07:45 +0200, Erez Morabia wrote:
> So, if I want to add my own nonstandard media-format to media with
> transport TCP, should I document it in some standard? If yes, where?
>
> For example,
> m=control 1234 tcp MyNonStandardFormat
> c=IN IP4 10.10.10.10
> a=fmtp: MyNonStandardFormat Data={bla bla bla}
It would be wise to start the name of any nonstandard media format with
"x-", as that prefix is usually reserved for nonstandard values to
ensure that they never collide with values that are standardized later.
In a perfect world, you should document your media format in a standard,
but there is no guarantee that you will be able to get your document
approved as a standard. So you will need an interim strategy.
> When I write application that parses such SDP, should I make my
> application ignore such “unknown” formats?
That depends on whether the caller of the parser is capable of dealing
with unknown format names showing up in the parser's output.
Dale
---
interop.pingtel.com -- the public SIP phone interoperability test server
_______________________________________________
Sip-implementors mailing list
[email protected]
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
