Re: [AVTCORE] [External] Re: Fwd: New Version Notification for draft-ietf-avtcore-rtp-evc-00.txt

Ye-Kui Wang <yekui.wang@bytedance.com> Tue, 02 February 2021 18:10 UTC

Return-Path: <yekui.wang@bytedance.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 1C1AF3A0D27 for <avt@ietfa.amsl.com>; Tue, 2 Feb 2021 10:10:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_FONT_LOW_CONTRAST=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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=bytedance-com.20150623.gappssmtp.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 D0EGn7oqqg2w for <avt@ietfa.amsl.com>; Tue, 2 Feb 2021 10:10:06 -0800 (PST)
Received: from mail-pf1-x431.google.com (mail-pf1-x431.google.com [IPv6:2607:f8b0:4864:20::431]) (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 DD92C3A0D25 for <avt@ietf.org>; Tue, 2 Feb 2021 10:10:05 -0800 (PST)
Received: by mail-pf1-x431.google.com with SMTP id f63so14860456pfa.13 for <avt@ietf.org>; Tue, 02 Feb 2021 10:10:05 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bytedance-com.20150623.gappssmtp.com; s=20150623; h=from:to:references:in-reply-to:subject:date:message-id:mime-version :thread-index:content-language; bh=fYKdsFh8kBqbdq5zzqMqMC2+lwHLronB2PILT4kWQ8s=; b=H67nHmugChvJUZt9AcGS6wrBX9F6Hm9G8dK+EoE7xy5nAR8gpPl2Wy+AJ1xHHBPWf3 BH/90UCNkqfYdibynzaaqgQJPvud5XaFyDQFzgIRb0VZtIuCFN2CPnVmBnq8V0feA0Cn CapYCzhqhQnHjXJ0n0/qip0C+Thw/iWht0sPnLcX5hZEybtTld4k8dUQGImT2HRWU2cR TNsqcdF6+IPKYgUzJHJopFbd9M9MKxacpqYMkkzMJJri3Rp4hQHg2Bw8jfeOyZsgHD+t vS8ldyqzXWavevofCW1WY9W+PDk1kpVwsjamoHSlWYzG+lIfiwyhY/J3stikVK33n2gW T3SQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:references:in-reply-to:subject:date :message-id:mime-version:thread-index:content-language; bh=fYKdsFh8kBqbdq5zzqMqMC2+lwHLronB2PILT4kWQ8s=; b=EYjvl1/Oqu9ciszcRu4Dr6vSocioP6oRdg39eUZaDdN9WDsfnDps6iszpQJHt6+/e1 4eNsTtJKAAv5R/7UZ8N3Qqy3HvIbZyM/zg6iCkhLg2Li5njT8x1Iclpi6T4ZahvvjKwJ pjEYOWqLlrN2dO4U9a5AOdlw6nVcDnPByvjdpSxcUD8+DdQybuGr2zouwPQNCIFP7hH1 t/OdIn9HXvkBmN8A5HSpC5I2m2aOtDs2ze/YQCwMpZE4FaY7UoucoZ2hPEGK1gGrnbtn 9BtI5taniPLkKFUfJtRLW5s6QObY5fdwRt+ucUx7dXXc2qBRO47xwelZ9q7WAceS14uO PpWg==
X-Gm-Message-State: AOAM531W6tUgbr5qpLpI9TeMBbRpNmKc4H//NrN7RQMei5MsBS5fxani owW+whwsXALuHXk5AOp7pT/KduV2VKmgPw==
X-Google-Smtp-Source: ABdhPJzmSaEkDuYwIv2UX8oVsWOVBHXWrtfY21oFQfMyzpFWYrskFW/TxZKFFHdt1IZD15EC3ZUAZA==
X-Received: by 2002:aa7:9585:0:b029:1c5:10ce:ba7f with SMTP id z5-20020aa795850000b02901c510ceba7fmr22701463pfj.79.1612289404550; Tue, 02 Feb 2021 10:10:04 -0800 (PST)
Received: from BTJS3X2BJA (cpe-70-95-86-203.san.res.rr.com. [70.95.86.203]) by smtp.gmail.com with ESMTPSA id g17sm23049426pgg.78.2021.02.02.10.10.02 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Tue, 02 Feb 2021 10:10:03 -0800 (PST)
From: Ye-Kui Wang <yekui.wang@bytedance.com>
To: 'Stephan Wenger' <stewe@stewe.org>, 'Youngkwon Lim' <yklwhite@gmail.com>, 'shuai zhao' <shuai.zhao@ieee.org>, avt@ietf.org
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>
In-Reply-To: <E797DFDF-6908-4061-8DFB-C70BD6B1B559@stewe.org>
Date: Tue, 02 Feb 2021 10:10:01 -0800
Message-ID: <0c9e01d6f98e$a0bbc1e0$e23345a0$@bytedance.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0C9F_01D6F94B.929FADD0"
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQEerWhsTUsz4as/H1FsVKqL4DRmJgIarqLDAZs52DMCLugHNwJXoJoAq3PeUvA=
Content-Language: en-us
Archived-At: <https://mailarchive.ietf.org/arch/msg/avt/gZ8UY1ECC5N3M3mR2_vm4FYcj3k>
Subject: Re: [AVTCORE] [External] Re: Fwd: 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 18:10:09 -0000

Having Young working together with you guys on the EVC payload format is good.

 

BR, YK

 

From: avt <avt-bounces@ietf.org> On Behalf Of Stephan Wenger
Sent: Tuesday, February 2, 2021 7:41
To: Youngkwon Lim <yklwhite@gmail.com>; shuai zhao <shuai.zhao@ieee.org>; avt@ietf.org
Subject: [External] Re: [AVTCORE] Fwd: New Version Notification for draft-ietf-avtcore-rtp-evc-00.txt

 

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