Re: [AVTCORE] New Version Notification for draft-ietf-avtcore-rtp-evc-00.txt(Internet mail)

"shuaiizhao(Shuai Zhao)" <shuaiizhao@tencent.com> Wed, 03 February 2021 00:11 UTC

Return-Path: <shuaiizhao@tencent.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 D50643A102F for <avt@ietfa.amsl.com>; Tue, 2 Feb 2021 16:11:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 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, 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 (1024-bit key) header.d=tencent.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 tjIPRDkWFhzC for <avt@ietfa.amsl.com>; Tue, 2 Feb 2021 16:11:30 -0800 (PST)
Received: from mail3.tencent.com (mail3.tencent.com [203.205.248.63]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CA69B3A0FFB for <avt@ietf.org>; Tue, 2 Feb 2021 16:11:29 -0800 (PST)
Received: from EX-SZ022.tencent.com (unknown [10.28.6.88]) by mail3.tencent.com (Postfix) with ESMTP id 851DF942B3; Wed, 3 Feb 2021 08:11:23 +0800 (CST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=tencent.com; s=s202002; t=1612311083; bh=yj45/jmDlW9NVXRz+tU5E9YZhOROMop989S1uzqTgmc=; h=From:To:CC:Subject:Date:References:In-Reply-To; b=CojtIXQweAz3iXgbpyyMDzjbKZAkjsEzkmyRmGn42+nv9MNlDTSgUWUVYAdhbKDGS pKqvFJIJw8Ns8Ofug+DF1wtabLBBPNrX45Sn8hDjVWnFRBGjBibRXRFPgb7NpNnRJ1 HLLKuGW9lhXCoaa77OpO7xbv60JMp4pezyu5+fQU=
Received: from EX-US01.tencent.com (10.93.1.207) by EX-SZ022.tencent.com (10.28.6.88) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2106.2; Wed, 3 Feb 2021 08:11:22 +0800
Received: from EX-US01.tencent.com (10.93.1.207) by EX-US01.tencent.com (10.93.1.207) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2106.2; Wed, 3 Feb 2021 08:11:20 +0800
Received: from EX-US01.tencent.com ([fe80::dd89:24b4:594b:5bbe]) by EX-US01.tencent.com ([fe80::dd89:24b4:594b:5bbe%4]) with mapi id 15.01.2106.002; Wed, 3 Feb 2021 08:11:20 +0800
From: "shuaiizhao(Shuai Zhao)" <shuaiizhao@tencent.com>
To: Youngkwon Lim <yklwhite@gmail.com>, Jonathan Lennox <jonathan.lennox@8x8.com>, Stephan Wenger <stewe@stewe.org>
CC: "avt@ietf.org" <avt@ietf.org>, shuai zhao <shuai.zhao@ieee.org>
Thread-Topic: [AVTCORE] New Version Notification for draft-ietf-avtcore-rtp-evc-00.txt(Internet mail)
Thread-Index: AQHW+aWjmXe61t6k/U63KUi8nIL9BapE8dwA//+Q0YA=
Date: Wed, 03 Feb 2021 00:11:20 +0000
Message-ID: <AFED97B3-BD77-413D-9825-EA9F377BBB7B@tencent.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> <emd866a2a5-434f-41e2-a65a-60bf4eeca228@2030009338>
In-Reply-To: <emd866a2a5-434f-41e2-a65a-60bf4eeca228@2030009338>
Accept-Language: en-US, zh-CN
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/16.45.21011103
x-originating-ip: [9.218.225.15]
Content-Type: multipart/alternative; boundary="_000_AFED97B3BD77413D9825EA9F377BBB7Btencentcom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/avt/HDftZytOW-fwONz34nPNnOgwFpg>
Subject: Re: [AVTCORE] New Version Notification for draft-ietf-avtcore-rtp-evc-00.txt(Internet mail)
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: Wed, 03 Feb 2021 00:11:34 -0000

I will be uploading a revision shortly to address those comments. Thanks, YoungKown and welcome you onboard.

Best,
Shuai

From: avt <avt-bounces@ietf.org> on behalf of Youngkwon Lim <yklwhite@gmail.com>
Reply-To: Youngkwon Lim <yklwhite@gmail.com>
Date: Tuesday, February 2, 2021 at 2:50 PM
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>
Subject: Re: [AVTCORE] New Version Notification for draft-ietf-avtcore-rtp-evc-00.txt(Internet mail)

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<mailto:jonathan.lennox@8x8.com>>
To: "Stephan Wenger" <stewe@stewe.org<mailto:stewe@stewe.org>>
Cc: "avt@ietf.org<mailto:avt@ietf.org>" <avt@ietf.org<mailto:avt@ietf.org>>; "Youngkwon Lim" <yklwhite@gmail.com<mailto:yklwhite@gmail.com>>; "shuai zhao" <shuai.zhao@ieee.org<mailto: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<mailto: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<mailto:avt-bounces@ietf.org>> on behalf of Youngkwon Lim <yklwhite@gmail.com<mailto:yklwhite@gmail.com>>
Reply-To: Youngkwon Lim <yklwhite@gmail.com<mailto:yklwhite@gmail.com>>
Date: Monday, February 1, 2021 at 21:05
To: shuai zhao <shuai.zhao@ieee.org<mailto:shuai.zhao@ieee.org>>, "avt@ietf.org<mailto:avt@ietf.org>" <avt@ietf.org<mailto: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<mailto:shuai.zhao@ieee.org>>
To: avt@ietf.org<mailto: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<mailto: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<mailto:shuai.zhao@ieee.org>>, "Stephan Wenger" <stewe@stewe.org<mailto: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<http://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<mailto:shuai.zhao@ieee.org>>
To: avt@ietf.org<mailto: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<mailto: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<mailto:shuai.zhao@ieee.org>>, "Stephan Wenger" <stewe@stewe.org<mailto: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<http://tools.ietf.org/>.

The IETF Secretariat

_______________________________________________
Audio/Video Transport Core Maintenance
avt@ietf.org<mailto:avt@ietf.org>
https://www.ietf.org/mailman/listinfo/avt