Re: [xrblock] WG Action: Rechartered Audio/Video Transport Core Maintenance (avtcore)

Barry Leiba <barryleiba@computer.org> Fri, 20 September 2019 18:14 UTC

Return-Path: <barryleiba@gmail.com>
X-Original-To: xrblock@ietfa.amsl.com
Delivered-To: xrblock@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 37FBC120808; Fri, 20 Sep 2019 11:14:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.922
X-Spam-Level:
X-Spam-Status: No, score=-1.922 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.001, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.026, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 qC-EfSaGuG0f; Fri, 20 Sep 2019 11:14:41 -0700 (PDT)
Received: from mail-io1-f47.google.com (mail-io1-f47.google.com [209.85.166.47]) (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 9AA43120045; Fri, 20 Sep 2019 11:14:41 -0700 (PDT)
Received: by mail-io1-f47.google.com with SMTP id k5so18259794iol.5; Fri, 20 Sep 2019 11:14:41 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:content-transfer-encoding; bh=ntnwSWphdGXe1BF+sY6QC+vpawZf2uPXO3mQTP6Qcgc=; b=D1Aqh0aHoGZbE9YfQmXCjAK+1UUTIpgd8NqreaYJgFMt5cMPRgo+Ee414Uddq0rPkH gVXCtPHv2F6auZQZsK4juSxmIjbaGGVh1tYwCvJKItuXjO+buCXXZHAjk+pCLf5+Sf/F 18tJozuyfII4DaupsV6kl8MJs9lOiH3uOw1XajZ5gCZTaOly/gJCnpcyKNPsr2YiJGE/ l1/gvBLte5DeeQtjtqoNnvwucbuoq0FRmS8SKMUse1zsqxJwASsJqMqJdckXyUj59ck/ QCPsRwC/MQ+9WPz6keyE67azNRk2wWOFEuSp8g43n/Kq7FneGf3YbMlbP5ecOZilEmtI z0Hg==
X-Gm-Message-State: APjAAAXTNB5+dDZq1jD53IMo+VbaFOnYa5TUEZMpMwIXNYuEhu48iXTH PRzkePwi386N9vwLRZdLA9Jpe7gNkfyCXO33Q6bdMA==
X-Google-Smtp-Source: APXvYqx1ufH194w39RWT8PMG7t3vYcvV6fYnXxQ9W9f9aI43MFiTMFy1oFEtqNYCampYPrKPCWBCsw3X3yjsJUuSePU=
X-Received: by 2002:a02:b882:: with SMTP id p2mr21097715jam.16.1569003280424; Fri, 20 Sep 2019 11:14:40 -0700 (PDT)
MIME-Version: 1.0
References: <156900171769.30287.2556830232611310049.idtracker@ietfa.amsl.com>
In-Reply-To: <156900171769.30287.2556830232611310049.idtracker@ietfa.amsl.com>
From: Barry Leiba <barryleiba@computer.org>
Date: Fri, 20 Sep 2019 14:14:29 -0400
Message-ID: <CALaySJLth0v2pO3rSspy2imjo-br3Ah=oc=oLQg0MyowqJnAhg@mail.gmail.com>
To: avt@ietf.org, payload@ietf.org, xrblock@ietf.org
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/xrblock/Dm5CCpQgdcXMbSO97QC1Lt5XTbM>
Subject: Re: [xrblock] WG Action: Rechartered Audio/Video Transport Core Maintenance (avtcore)
X-BeenThere: xrblock@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Metric Blocks for use with RTCP's Extended Report Framework working group discussion list <xrblock.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xrblock>, <mailto:xrblock-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/xrblock/>
List-Post: <mailto:xrblock@ietf.org>
List-Help: <mailto:xrblock-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xrblock>, <mailto:xrblock-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Sep 2019 18:14:44 -0000

Hi, all,
Now that the AVTCORE recharter is official and the PAYLOAD and XRBLOCK
work is officially moved back into AVTCORE, it's time to close the
other two working groups.

As I announced earlier, Roni Even has joined Rachel and Jonathan as
co-chair of AVTCORE, and he will continue shepherding payload-related
documents.  Thanks to all three of you for your continuing service and
for the work you do.

After I send this I will "push the button" on PAYLOAD and XRBLOCK, and
I'll give here my appreciation for the work and the years of service
as chairs by Ali Begen, Dan Romaşcanu, and Shida Schubert.

I intend to close the mailing lists of PAYLOAD and XRBLOCK and have
them automatically redirect to <avt@ietf.org>.

Barry, ART AD

On Fri, Sep 20, 2019 at 1:48 PM The IESG <iesg-secretary@ietf.org> wrote:
>
> The Audio/Video Transport Core Maintenance (avtcore) WG in the Applications
> and Real-Time Area of the IETF has been rechartered. For additional
> information, please contact the Area Directors or the WG Chairs.
>
> Audio/Video Transport Core Maintenance (avtcore)
> -----------------------------------------------------------------------
> Current status: Active WG
>
> Chairs:
>   Jonathan Lennox <jonathan.lennox42@gmail.com>
>   Rachel Huang <rachel.huang@huawei.com>
>   Roni Even <roni.even@huawei.com>
>
> Assigned Area Director:
>   Barry Leiba <barryleiba@computer.org>
>
> Applications and Real-Time Area Directors:
>   Adam Roach <adam@nostrum.com>
>   Alexey Melnikov <aamelnikov@fastmail.fm>
>   Barry Leiba <barryleiba@computer.org>
>
> Mailing list:
>   Address: avt@ietf.org
>   To subscribe: https://www.ietf.org/mailman/listinfo/avt
>   Archive: https://mailarchive.ietf.org/arch/browse/avt/
>
> Group page: https://datatracker.ietf.org/group/avtcore/
>
> Charter: https://datatracker.ietf.org/doc/charter-ietf-avtcore/
>
> The Real-time Transport Protocol (RTP) along with its associated profiles
> and payload formats provides for real-time transmission of audio and
> video over unicast and multicast transports. RTP is widely implemented
> and deployed for a broad range of applications, from telephony to
> television over IP. RTP itself is now an Internet Standard. Its
> associated profiles, extensions, and payload formats are currently at
> various levels of standards maturity. As new applications emerge, there
> is a need for guidelines for the use of the RTP/RTCP protocols and
> extensions specific to those applications.
>
> The AVTCORE working group is chartered for the following tasks:
>
> 1. To maintain the core RTP/RTCP specifications and the AVP, SAVP, AVPF,
> and SAVPF profiles. The group will provide architectural guidance for
> extending the protocols and guidelines for their proper use.
>
> 2. To develop application-specific guidelines for the use of RTP/RTCP
> protocols with the AVP, SAVP, AVPF, and SAVPF profiles, and extensions to
> those protocols that are driven by application-specific needs.
>
> 3. To specify and maintain payload formats for use with RTP. The working
> group will develop RTP payload formats for new media codecs, review and
> revise existing payload formats to advance those that are especially
> useful to Internet Standard, and declare others Historic.  The group will
> follow the guidelines established in "Guidelines for Writers of RTP
> Payload Format Specifications" [BCP 36] and "How to Write an RTP Payload
> Format" (RFC 8088), and is responsible for maintaining those guidelines.
>
> 4. To evaluate and process proposals for RTP eXtended Report Block
> (XRBLOCK) definitions containing new metrics. The group will work within
> the framework defined by RFC 3611, "RTP Control Protocol Extended Reports
> (RTCP XR)" along with other RTP monitoring architecture being developed
> in the working group. It will follow the guidelines established in RFC
> 5968, "Guidelines for Extending the RTP Control Protocol (RTCP)" and RFC
> 6390, "Guidelines for Considering New Performance Metric Development".
>
> The AVTCORE working group will coordinate closely with the Security Area
> while working on maintenance and enhancements to the SRTP Profile (SAVP).
>
> Milestones:
>
>   Feb 2019 - Submit Guidelines for using the Multiplexing Features of RTP for
>   Informational
>
>   Mar 2019 - Submit RTP Payload Format for the TETRA Audio Codec
>
>   Apr 2019 - Submit RTP Header Extension for Video Frame Information for
>   Proposed Standard
>
>   Jun 2019 - Submit Feedback Mechanism for RTP Congestion Control for
>   Proposed Standard
>
>   Nov 2019 - Submit RTP Payload Format for VP9 Video for Proposed Standard
>
>   Mar 2020 - Submit RTP Payload Format for ISO/IEC 21122 (JPEG XS) for
>   Proposed Standard
>
>   Mar 2020 - Submit RTP Payload Format for TTML Timed Text for Proposed
>   Standard
>
>