Hi all,

A couple of nits that should help when this goes out for community review:

OLD
where there are verifiable reasons to believe they are RF
NEW
where there are verifiable reasons to believe they are available on an RF basis

OLD
an open source reference version of the codec will be developed in parallel 
with the working group
NEW
an open source reference version of the codec will be developed in parallel 
with the working group’s work

OLD
3. Source code for a reference implementation that includes both an encoder and 
a decoder.
NEW
3. Source code for a reference implementation (documented in an informational 
document) that includes both an encoder and a decoder.

Unless folks object to these changes, I’ll put this into the datatracker and 
get it moving through the approval process.

Alissa

On Apr 6, 2015, at 8:35 AM, Adam Roach <[email protected]> wrote:

> Okay, there seems to be support here for a new deliverable (most importantly, 
> from the people who will likely be doing the work to satisfy the 
> deliverable). The attached charter incorporates this new deliverable, as well 
> as the clarification based on Mo's earlier comment.
> 
> /a
> 
> On 4/3/15 17:01, Suhas Nandakumar wrote:
>> 
>> 
>> On Fri, Apr 3, 2015 at 11:17 AM, Timothy B. Terriberry <[email protected]> 
>> wrote:
>> Mo Zanaty (mzanaty) wrote:
>> Adam Roach <[email protected]> wrote:
>> I propose clarifying by changing the first milestone to be "Requirements and 
>> evaluation criteria to IESG..."
>> 
>> Works for me.
>> 
>> Also fine to keep the final milestone for the testing doc for now. We can 
>> revisit once there, which also gives time to see how opus handles this 
>> (currently no supply or demand interest).
>> 
>> Both sound fine to me.
>> 
>> Any objection to adding the deliverable for a reference implementation? 
>> Here's some proposed text:
>> 
>> "3. Source code for a reference implementation that includes both an encoder 
>> and a decoder."
>> 
>>   +1 for adding source code ref-impl.
>>  
>> 
>> _______________________________________________
>> video-codec mailing list
>> [email protected]
>> https://www.ietf.org/mailman/listinfo/video-codec
>> 
> 
> <netvc-charter-02.txt><netvc-charter-diffs-01-02.html>_______________________________________________
> video-codec mailing list
> [email protected]
> https://www.ietf.org/mailman/listinfo/video-codec

_______________________________________________
video-codec mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/video-codec

Reply via email to