Re: [AVTCORE] New Version Notification for draft-ietf-avtcore-rtp-evc-00.txt
Youngkwon Lim <yklwhite@gmail.com> Tue, 02 February 2021 22:49 UTC
Return-Path: <yklwhite@gmail.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D97253A0AD4 for <avt@ietfa.amsl.com>; Tue, 2 Feb 2021 14:49:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.096
X-Spam-Level:
X-Spam-Status: No, score=-2.096 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_FONT_LOW_CONTRAST=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lksc7sCaNEzm for <avt@ietfa.amsl.com>; Tue, 2 Feb 2021 14:49:47 -0800 (PST)
Received: from mail-ot1-x333.google.com (mail-ot1-x333.google.com [IPv6:2607:f8b0:4864:20::333]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 18C553A0AD1 for <avt@ietf.org>; Tue, 2 Feb 2021 14:49:47 -0800 (PST)
Received: by mail-ot1-x333.google.com with SMTP id s107so919885otb.8 for <avt@ietf.org>; Tue, 02 Feb 2021 14:49:46 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:to:subject:cc:date:message-id:in-reply-to:references:reply-to :user-agent:mime-version; bh=qQY1bZQiSqZdpI7KDXCs1VQy9xMogD6gqD4QcT8onMk=; b=T4SvUhSabl7njF9DWhUTCYiQVqVsxj0DJZsAKBogTwLFyWZvkAapjxXEQvslwr8zgU JK0LN8jMG/fPfB9ksY4Fici4bLUycH2GDm5/TR+EgwZUFScRbNpQKcNdpdu25DtwChhM QVQgg+QtoQ2PPkeFOmfBgSaRDRLwF7Fx/Ujz0fgjyI5/at0CnB/njFKqd/pcAhSCYkKF zBx4ntCek3xK/R86yJyOcIEcpy1W+XZ79KTqOIMhzYKbkvbabsho6xNksRji6W+xoi9F EuNkujBbYt+drsZd5+Y/eBhyan99zGAVbFR1XYZvInDL2Vnlqi/MxbsS2q/qzjgoUa5j +Crw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:subject:cc:date:message-id:in-reply-to :references:reply-to:user-agent:mime-version; bh=qQY1bZQiSqZdpI7KDXCs1VQy9xMogD6gqD4QcT8onMk=; b=O7lc+B/ZiuL0EH2zdKbRCmCs2tx3uPzvEP7Rc6V9mwEn5ep11k5sfd6w8HJuQ8Fbot XZpfLZ6YGgjLJ3PCtV4EZbTw5HS1/C46Z923hVeoe3Esk1eB4S6vSqdNj0LKQHAJFbiN Tql3bVXDo37FHJltkF2cUvyRjZQhdTiLFrB4A7hM1RngxLVE7NX0+LPq6x8icY/FtwmF uPAKUO9DZAv09ydgtKEA3r1qOIZbjYR/LWgExeXYBDBxP1pXqy3UKYOivhkUIcekWhgN 57L4mJoxtC5A+2COM/CFQwlLLXgtDwmotCT0W8NAoYm2agqaIzj1p0KVvL0DZRyqKkEq rV+w==
X-Gm-Message-State: AOAM530I2s4EOgPIF7nzqLMUy6VYaOq1dojTx0PV/HGbB7WtdQhQC8e5 tdZp/JyBxBqkYSbm+SPqp04=
X-Google-Smtp-Source: ABdhPJxQcj+YK2s63BuTcl2nd1JiWXmEpPWJH5g6z2PlL3bNMdiWBr0r0VbQVp1GqrRqPBtk928+7w==
X-Received: by 2002:a9d:5cc2:: with SMTP id r2mr16378350oti.173.1612306186314; Tue, 02 Feb 2021 14:49:46 -0800 (PST)
Received: from ?IPv6:2600:1700:1040:f20:c5c0:9cc:96ca:d4ea? ([2600:1700:1040:f20:c5c0:9cc:96ca:d4ea]) by smtp.gmail.com with ESMTPSA id 33sm53929ota.69.2021.02.02.14.49.44 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Tue, 02 Feb 2021 14:49:45 -0800 (PST)
From: Youngkwon Lim <yklwhite@gmail.com>
To: Jonathan Lennox <jonathan.lennox@8x8.com>, Stephan Wenger <stewe@stewe.org>
Cc: "avt@ietf.org" <avt@ietf.org>, shuai zhao <shuai.zhao@ieee.org>
Date: Tue, 02 Feb 2021 22:49:16 +0000
Message-Id: <emd866a2a5-434f-41e2-a65a-60bf4eeca228@2030009338>
In-Reply-To: <52EC0A0A-51A2-45C7-BBEB-AF5F53492ABF@8x8.com>
References: <160972920752.32158.3348863571557347558@ietfa.amsl.com> <16847060-8519-433A-84C4-3707A794D18C@ieee.org> <eme1eb8d54-279c-4d3e-b945-6ef6b2425087@2030009338> <em4198658a-24a0-4923-acaf-824f9c5ba055@2030009338> <E797DFDF-6908-4061-8DFB-C70BD6B1B559@stewe.org> <52EC0A0A-51A2-45C7-BBEB-AF5F53492ABF@8x8.com>
Reply-To: Youngkwon Lim <yklwhite@gmail.com>
User-Agent: eM_Client/8.1.1054.0
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="------=_MBF0655D53-DA9A-44BF-99D4-2CF04F9F3986"
Archived-At: <https://mailarchive.ietf.org/arch/msg/avt/-kNqLQJMzSWOjgL6kmjJGo5tCXw>
Subject: Re: [AVTCORE] New Version Notification for draft-ietf-avtcore-rtp-evc-00.txt
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/avt/>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Feb 2021 22:49:50 -0000
Hi all, Thanks for the consideration. I'll be happy to join as a co-author and contribution further. Sincerely, Young ------ Original Message ------ From: "Jonathan Lennox" <jonathan.lennox@8x8.com> To: "Stephan Wenger" <stewe@stewe.org> Cc: "avt@ietf.org" <avt@ietf.org>; "Youngkwon Lim" <yklwhite@gmail.com>; "shuai zhao" <shuai.zhao@ieee.org> Sent: 02/02/21 14:54:12 Subject: Re: [AVTCORE] New Version Notification for draft-ietf-avtcore-rtp-evc-00.txt >If Young wants to be a co-author and the current authors want him to be >a co-author, I have no objection. Subject expertise is always very >useful! > >Jonathan > >>On Feb 2, 2021, at 10:40 AM, Stephan Wenger <stewe@stewe.org> wrote: >> >>Hi Young, >>Thanks very much for these excellent comments. It’s good to see such >>a distinguished member of the MPEG world, and such an EVC expert >>contributing here. >> >>AVT, chairs: >>Young and us had private communication about various other aspects of >>the draft before, and we are sure he can help a lot on the missing >>parts of the draft, especially wrt. to the SDP and O/A sections. We >>would love to have him on the authors’ team. Is that OK? >> >>Thanks, >>Stephan >> >>From: avt <avt-bounces@ietf.org> on behalf of Youngkwon Lim >><yklwhite@gmail.com> >>Reply-To: Youngkwon Lim <yklwhite@gmail.com> >>Date: Monday, February 1, 2021 at 21:05 >>To: shuai zhao <shuai.zhao@ieee.org>, "avt@ietf.org" <avt@ietf.org> >>Subject: Re: [AVTCORE] Fwd: New Version Notification for >>draft-ietf-avtcore-rtp-evc-00.txt >> >>Dear Shuai and all, >> >>This is Youngkwon Lim from Samsung. I have had a chance to review the >>draft and got some quick comments. >> >> The first line of the Section 1 should be updated to reflect that the >>standard has been already published in the last summer. >>In the first paragraph of the section 1, it would be useful to clarify >>that the Baseline profile achieves royalty free nature by using the >>technologies published more than 20 years or otherwise freely >>available for use, whereas a more advanced profile, Main profile, >>licensable with a reasonable and non-discriminatory licensing terms. >>Main profile adds small number of tools each of which can be either >>cleanly disabled or switched to the corresponding Baseline profile >>tool on an individual basis. >>Throughout the document, the name of profile, Baseline and Main, >>should be capitalized. >>In the first paragraph of the section 1.1, the “toolset” syntax >>element should be modified to “toolset_idc_h and toolset_idc_l” to >>reflect the changes of the specification >>In the first paragraph of the section 1.1.1, it should be mentioned >>that the largest CTU size for Baseline profile is 64x64 instead of >>128x128 >> In the first paragraph of the section 1.1.1, the block to be >>independently encoded/decoded should refer the slices instead of the >>tiles. >>In the second paragraph of the page 5, ‘In the previous technology’ >>should be ‘In [EVC]’ >>I can confirm the note at the bottom of the page 6, the random-access >>points mechanism is IDR only. >>Section 1.1.3 can mention about independently decodable slices as a >>parallel processing unit. >>The last sentence of the informative note below Figure 2, after the >>Market bit should be modified to >>equal to 28 or in the range of 29 to 55. >> >>I hope these are useful. Please review and reflect accordingly. I'll >>have more in depth review and provide more soon. >> >>Sincerely, >>Young >> >> >> >>------ Original Message ------ >>From: "shuai zhao" <shuai.zhao@ieee.org> >>To: avt@ietf.org >>Sent: 01/03/21 23:01:14 >>Subject: [AVTCORE] Fwd: New Version Notification for >>draft-ietf-avtcore-rtp-evc-00.txt >> >>Dear Group, Happy 2021… >> >>As agreed on IETF 109, here is the first WG draft for EVC RTP payload >>format. >> >>No major changes since last individual draft. You can skip this review >>and waiting for next revision. >> >>Best, >>Shuai >> >> >>Begin forwarded message: >> >>From: internet-drafts@ietf.org >>Subject: New Version Notification for >>draft-ietf-avtcore-rtp-evc-00.txt >>Date: January 3, 2021 at 19:00:07 PST >>To: "Shuai Zhao" <shuai.zhao@ieee.org>, "Stephan Wenger" >><stewe@stewe.org> >> >> >>A new version of I-D, draft-ietf-avtcore-rtp-evc-00.txt >>has been successfully submitted by Shuai Zhao and posted to the >>IETF repository. >> >>Name: draft-ietf-avtcore-rtp-evc >>Revision: 00 >>Title: RTP Payload Format for Essential Video Coding (EVC) >>Document date: 2020-12-08 >>Group: avtcore >>Pages: 36 >>URL: >>https://www.ietf.org/archive/id/draft-ietf-avtcore-rtp-evc-00.txt >>Status: >>https://datatracker.ietf.org/doc/draft-ietf-avtcore-rtp-evc/ >>Htmlized: >>https://datatracker.ietf.org/doc/html/draft-ietf-avtcore-rtp-evc >>Htmlized: >>https://tools.ietf.org/html/draft-ietf-avtcore-rtp-evc-00 >> >> >>Abstract: >> This memo describes an RTP payload format for the video coding >> standard ISO/IEC International Standard 23094-1 [ISO23094-1], also >> known as Essential Video Coding [EVC] and developed by ISO/IEC >> JTC1/SC29/WG11. The RTP payload format allows for packetization of >> one or more Network Abstraction Layer (NAL) units in each RTP packet >> payload as well as fragmentation of a NAL unit into multiple RTP >> packets. The payload format has wide applicability in >> videoconferencing, Internet video streaming, and high-bitrate >> entertainment-quality video, among other applications. >> >> >> >> >>Please note that it may take a couple of minutes from the time of >>submission >>until the htmlized version and diff are available at tools.ietf.org. >> >>The IETF Secretariat >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >>equal to 28 or in the range of 29 to 55. >> >>I hope these are useful. Please review and reflect accordingly. I'll >>have more in depth review and provide more soon. >> >>Sincerely, >>Young >> >>> >>> >>>------ Original Message ------ >>>From: "shuai zhao" <shuai.zhao@ieee.org> >>>To: avt@ietf.org >>>Sent: 01/03/21 23:01:14 >>>Subject: [AVTCORE] Fwd: New Version Notification for >>>draft-ietf-avtcore-rtp-evc-00.txt >>> >>>>Dear Group, Happy 2021… >>>> >>>>As agreed on IETF 109, here is the first WG draft for EVC RTP >>>>payload format. >>>> >>>>No major changes since last individual draft. You can skip this >>>>review and waiting for next revision. >>>> >>>>Best, >>>>Shuai >>>> >>>> >>>>>Begin forwarded message: >>>>> >>>>>From: internet-drafts@ietf.org >>>>>Subject: New Version Notification for >>>>>draft-ietf-avtcore-rtp-evc-00.txt >>>>>Date: January 3, 2021 at 19:00:07 PST >>>>>To: "Shuai Zhao" <shuai.zhao@ieee.org>, "Stephan Wenger" >>>>><stewe@stewe.org> >>>>> >>>>> >>>>>A new version of I-D, draft-ietf-avtcore-rtp-evc-00.txt >>>>>has been successfully submitted by Shuai Zhao and posted to the >>>>>IETF repository. >>>>> >>>>>Name: draft-ietf-avtcore-rtp-evc >>>>>Revision: 00 >>>>>Title: RTP Payload Format for Essential Video Coding (EVC) >>>>>Document date: 2020-12-08 >>>>>Group: avtcore >>>>>Pages: 36 >>>>>URL: >>>>>https://www.ietf.org/archive/id/draft-ietf-avtcore-rtp-evc-00.txt >>>>>Status: >>>>>https://datatracker.ietf.org/doc/draft-ietf-avtcore-rtp-evc/ >>>>>Htmlized: >>>>>https://datatracker.ietf.org/doc/html/draft-ietf-avtcore-rtp-evc >>>>>Htmlized: >>>>>https://tools.ietf.org/html/draft-ietf-avtcore-rtp-evc-00 >>>>> >>>>> >>>>>Abstract: >>>>> This memo describes an RTP payload format for the video coding >>>>> standard ISO/IEC International Standard 23094-1 [ISO23094-1], >>>>>also >>>>> known as Essential Video Coding [EVC] and developed by ISO/IEC >>>>> JTC1/SC29/WG11. The RTP payload format allows for packetization >>>>>of >>>>> one or more Network Abstraction Layer (NAL) units in each RTP >>>>>packet >>>>> payload as well as fragmentation of a NAL unit into multiple RTP >>>>> packets. The payload format has wide applicability in >>>>> videoconferencing, Internet video streaming, and high-bitrate >>>>> entertainment-quality video, among other applications. >>>>> >>>>> >>>>> >>>>> >>>>>Please note that it may take a couple of minutes from the time of >>>>>submission >>>>>until the htmlized version and diff are available at >>>>>tools.ietf.org. >>>>> >>>>>The IETF Secretariat >>>>> >>>>> >>>> >>_______________________________________________ >>Audio/Video Transport Core Maintenance >>avt@ietf.org >>https://www.ietf.org/mailman/listinfo/avt >
- [AVTCORE] Fwd: New Version Notification for draft… shuai zhao
- Re: [AVTCORE] Fwd: New Version Notification for d… Youngkwon Lim
- Re: [AVTCORE] Fwd: New Version Notification for d… Stephan Wenger
- Re: [AVTCORE] [External] Re: Fwd: New Version Not… Ye-Kui Wang
- Re: [AVTCORE] New Version Notification for draft-… Jonathan Lennox
- Re: [AVTCORE] New Version Notification for draft-… Youngkwon Lim
- Re: [AVTCORE] [External] Re: Fwd: New Version Not… Youngkwon Lim
- Re: [AVTCORE] New Version Notification for draft-… shuaiizhao(Shuai Zhao)