Re: [AVTCORE] Mail regarding draft-ietf-payload-tetra
"Roni Even (A)" <[email protected]>
| Newsgroups | gmane.ietf.avt |
|---|---|
| Message-ID | <6E58094ECC8D8344914996DAD28F1CCD23D7A7BB@DGGEMM506-MBX.china.huawei.com> |
Hi, This issue was discussed with the authored and the AD. This problem started that during the work in payload WG on tetra RTP payload there was a request from ETSI to IANA to register the tetra media subtype name. this request did not go also to payload WG chairs so it was missed otherwise the payload chairs would have asked to first see how to synchronize those two requests . The conclusion was that if the RTP media subtype specifications are different we can have another RTP media subtype with a different name. See the last mail https://mailarchive.ietf.org/arch/msg/payload/5ZLf35CXB1LaWZX_zTCLUKG2h2U Roni Even AVTcore WG co-chair (former Payload WG co-chair) -----Original Message----- From: avt [mailto:[email protected]] On Behalf Of Marc Weustink Sent: Tuesday, October 08, 2019 2:37 PM To: [email protected] Subject: [AVTCORE] Mail regarding draft-ietf-payload-tetra Hi, Has the payload description any relation to ETSI TS 100 392-19-2 ? Imo it should be avoided to have 2 different RTP payload descriptions for the same (?) TETRA ACELP. Best regards, Marc Weustink _______________________________________________ Audio/Video Transport Core Maintenance [email protected] https://www.ietf.org/mailman/listinfo/avt _______________________________________________ Audio/Video Transport Core Maintenance [email protected] https://www.ietf.org/mailman/listinfo/avt