[AVT] Re: Comments on draft-hatanaka-avt-rtp-atracx-03.txt

[Magnus Westerlund <[e-mail]>]

Dear Jun,

I hope that you are not discouraged to continue the work by my rather 
long mail. As I see it there are some problems that one faces when 
trying to write a payload format for a codec within the AVT WG. The 
first is a matter of learning. One needs to have a rather good 
understanding of the codecs capabilities and working to know what 
requirements it has on the transport, thus it is usually codec people 
that comes to AVT. Then one must learn about how RTP and IP works and 
what the available mechanisms are. This will require one to learn a 
rather big pile of documents. Sorry to say we chairs or other group 
members does not always have the time to early enough point out some 
important details. I hope we in the future can improve this and also 
create some more informational material to help RTP payload designers.

I am also very sorry to hear that you are not coming to Minneapolis, I 
would have very much liked to discuss your payload format's design. 
Having direct communication can help immensely to ensure that the 
important aspects are covered.

I would also recommend that you try to create a new proposal in good 
time prior to the IETF meeting, thus we can make better progress. People 
usually have more time for discussion things when not stressed by 
deadlines or hugh workload prior to a meeting. It also allows you time 
to discuss or ask questions halfway the design process.

When it comes to payload format design I think there are some general 
things that needs to be ensured:

- Follow the application level framing principle, i.e. self contained 
packets.
- Keep it simple.
- Utilize the available mechanism in RTP in a good way.

Again if you have questions regarding design choices, please voice them 
to the list.

Best Regards

Magnus


Jun Matsumoto wrote:

> Dear Mr.Westerlund,
> 
> 
>>In my opinion you need to go back to the drawing board and rethink the design. 
>>This design seems to be much to complex for the purpose. However as you haven't clearly 
>>communicated the purpose I am not certain. I think there exist simple solutions.
> 
> 
> OK, We agree that the complexity of our proposal.
> Reffering your advise, we will re-design a simplified payload format,
> and then make a proposal as ***-atracx-04.txt by Seoul meeting.
> 
> We have decided we do not go to Minneapolis meeting, so we would like you 
> to cancel our presentation time slot.
> 
> Thank you very much for your useful advise.
> 
> Best Regards,
> 
> --------------------------------------
>   Jun Matsumoto
>    
>   Audio Codec Development Department
>   Sony Corporation, IMNC  
> 
>   [e-mail]
> --------------------------------------

-- 

Magnus Westerlund

Multimedia Technologies, Ericsson Research EAB/TVA/A
----------------------------------------------------------------------
Ericsson AB                | Phone [phone]
Torshamsgatan 23           | Fax   [phone]
S-164 80 Stockholm, Sweden | mailto: [e-mail]


_______________________________________________
Audio/Video Transport Working Group
[e-mail]
https://www1.ietf.org/mailman/listinfo/avt