Re: [xrblock] Plans for the AVTCORE, PAYLOAD, and XRBLOCK working groups

Barry Leiba <barryleiba@computer.org> Thu, 15 August 2019 19:04 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 0A2E11200D6; Thu, 15 Aug 2019 12:04:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.401
X-Spam-Level:
X-Spam-Status: No, score=-1.401 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.249, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=no 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 E073aMTFsBIj; Thu, 15 Aug 2019 12:04:03 -0700 (PDT)
Received: from mail-io1-f42.google.com (mail-io1-f42.google.com [209.85.166.42]) (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 081431200C4; Thu, 15 Aug 2019 12:04:03 -0700 (PDT)
Received: by mail-io1-f42.google.com with SMTP id i22so1281526ioh.2; Thu, 15 Aug 2019 12:04:02 -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=eRWySqwo1sP2F36vjM1A/azL63ZMJ0PcJbCbgcvQAjI=; b=GV3L/+Ogp2m1Uw/1pKhV5OM/jrTmEKYz54/domq/WiJbe/ELGnCs3T1HPhzpPaUWOg ZQPRyqJPlnClKyuSJ/gzVOu/A/Pu9TmCluf4d265kXBcJ5TcSsAE1DrgpS5fN9w6qala /O2l0CeDZ3xw1pNR2/exnRht/9dsq5LaUgAeYzCyVzJBSlhuMSvCHwFU7IURWUGR3Bwo 0NJg/d3vnW6+4umvmclwVy+kAnBg3zQX+aDBKXK6ii1z/vidaLYCGFqNDjUj53yHSqWR WjtPilkDSSLYSoVO0FMh14loE89h/zoMiFo2fQkztqUhZkPd5GdDWrnPqhV0+Yom/oIG gd4A==
X-Gm-Message-State: APjAAAWIZYsiwtPoQJa4aDgXGWRIXmwnZLD7MLGA9qLGIuXTxWoHecKX YjewSIEvfwXzHae8dwK7U0tOEJKdUFbnz8o986uZhB4n
X-Google-Smtp-Source: APXvYqwyyPpnpvWpopJq8n0oiS6As9n1GI7WVdAdeD1UuEtjVkevmL342EzafpLwWCOLeIx7SYcakcEVYA786B2EnKo=
X-Received: by 2002:a5d:9613:: with SMTP id w19mr6092649iol.140.1565895841731; Thu, 15 Aug 2019 12:04:01 -0700 (PDT)
MIME-Version: 1.0
References: <CALaySJJAGU-FyodaNz5sZ3Ct3VfetCDEA+mjdoKxz_nXehN_mw@mail.gmail.com>
In-Reply-To: <CALaySJJAGU-FyodaNz5sZ3Ct3VfetCDEA+mjdoKxz_nXehN_mw@mail.gmail.com>
From: Barry Leiba <barryleiba@computer.org>
Date: Thu, 15 Aug 2019 15:03:50 -0400
Message-ID: <CALaySJ+prVrQtFz1dp_Q3Q47MRo0nft=eHyUFCHpWiLVczCd2A@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/2lLMze_hzW8aPQSG7zJxVNcpV5s>
Subject: Re: [xrblock] Plans for the AVTCORE, PAYLOAD, and XRBLOCK working groups
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: Thu, 15 Aug 2019 19:04:05 -0000

I have prepared a merged charter for the new AVTCORE working group:

https://datatracker.ietf.org/doc/charter-ietf-avtcore/

It's currently a draft, and comments and tweaks are encouraged.
What's there is essentially the three existing charters merged, with
some minor editorial changes and a format change to make the result
flow well.  Please let me know whether it looks right, or whether
there are changes we should make.

I've also merged the AVTCORE and PAYLOAD milestones, which you can see
below the draft charter.  It would be nice if before we send it to the
IESG for review we have some fresh dates for the 2019 milestones that
are already in the past.  Can the chairs please estimate some new
dates for those and let me know?

Barry

On Thu, Aug 1, 2019 at 3:04 PM Barry Leiba <barryleiba@computer.org> wrote:
>
> The ART ADs have discussed the AVTCORE, PAYLOAD, and XRBLOCK working
> groups, the reasons the latter two were split off, and the current
> situation.  After discussing those with the other (and former) ART ADs
> and with the chairs of those working groups, I’ve decided to re-merge
> them.  There is no longer a heavy stream of documents for PAYLOAD and
> XRBLOCK, and we don’t expect those that do come in to distract the
> AVTCORE working group from its core (sorry) work.  At the same time,
> it makes sense to keep that work visible to the AVTCORE community.
>
> As Dan Romaşcanu and Shida Schubert have reduced their IETF activity
> and are no longer attending meetings, they are stepping down as
> chairs.  Ali Begen will also step down, and I will be looking for
> opportunities to use his expertise in chairing other groups.  I very
> much thank all of them for their service, and urge others to add their
> thanks privately.
>
> We will have three chairs for the merged working group, which will
> retain the AVTCORE name: Rachel Huang and Jonathan Lennox will
> continue, and Roni Even will join them and bring his expertise in
> shepherding PAYLOAD documents through the process.  Thanks very much
> to them, also, for their continued service.
>
> Before I “push the button” on this, I’d like to give the working group
> a chance to comment: if you feel that there’s a really strong reason
> not to do this or to do it differently, please let me know, privately
> or on list (in which case, please CC me so I don’t overlook it).  I
> plan to start the process of rechartering AVTCORE and making this
> merge in a week or two.
>
> Also, I’m asking the tools team if there’s a reasonable way to merge
> the datatracker document histories of AVTEXT (12 RFCs and 2 drafts in
> cluster 238), PAYLOAD (17 RFCs and 5 drafts), and XRBLOCK (19 RFCs)
> into the AVTCORE document list, so we have one place to go for the
> list of documents.  I probably will not look to add the AVT working
> group's RFCs as well, as there are 115 of them.  I don’t know whether
> it’s feasible, but I’ll ask.
>
> Barry, ART Director