
From nobody Thu Aug  1 12:04:24 2019
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 6862C120182; Thu,  1 Aug 2019 12:04:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.697
X-Spam-Level: 
X-Spam-Status: No, score=-1.697 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.001, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.201, 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 2t9zk1tBWmvh; Thu,  1 Aug 2019 12:04:21 -0700 (PDT)
Received: from mail-io1-f54.google.com (mail-io1-f54.google.com [209.85.166.54]) (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 19D96120059; Thu,  1 Aug 2019 12:04:21 -0700 (PDT)
Received: by mail-io1-f54.google.com with SMTP id i10so33429714iol.13; Thu, 01 Aug 2019 12:04:21 -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:from:date:message-id:subject:to :content-transfer-encoding; bh=zfQ07fgRxhbheuHbsN9Cg1XlEIe677kz1CFFXTeIemQ=; b=SbAKReQXW3BAUbcu/jVTWQ2UR6r5wYsk1YX1fc7RqH/J5rcOtrtzAK4pOG76lWFAdq ZyFxueI2eFf1brHd/GesiaxI1t03y63EPdGSnyVwmzKT2osZ4jk6+Y/V+xFj9Ry2C3DI jpvdj8EJogmN0jx7GuZ2OVgRHxhpdg1PozvA/8K6Z6YuQ5DcijQ4SV0ZZOmKeYfaDV6G VWrgBBUAkno/+cE6uC5BTBYIYb9qdptAyu7rcf7+W4nACs9zCHntPpZjHqrf1nmdZYIW dOuJwtbDR+HaqiVrKHYOE86MJFxpt+Ict4RYCtJroXo0T1o1mQL/3FXusgl56Q9zqkck 2YHg==
X-Gm-Message-State: APjAAAVhI+sfOtMErwnzKJw4b49H8f36nNh9FtMaktdSusoU/irQtoO6 MzuM+EiuMankeuvQnHkOilF+vtsF9dizUNj++jLjelzH
X-Google-Smtp-Source: APXvYqz55p8GynyYpoaMKAvLE4goByvZo/HSOK/z7SC9Lac+9CVkMUoJdSwgstwBFMfWDmbtpaIwNcBQUMqwBbJxIaE=
X-Received: by 2002:a6b:fb0f:: with SMTP id h15mr16309438iog.266.1564686259568;  Thu, 01 Aug 2019 12:04:19 -0700 (PDT)
MIME-Version: 1.0
From: Barry Leiba <barryleiba@computer.org>
Date: Thu, 1 Aug 2019 15:04:08 -0400
Message-ID: <CALaySJJAGU-FyodaNz5sZ3Ct3VfetCDEA+mjdoKxz_nXehN_mw@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/4BCeHz-T9mIqLUZNaysDl88mO6s>
Subject: [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, 01 Aug 2019 19:04:23 -0000

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=E2=80=99ve decided to re-mer=
ge
them.  There is no longer a heavy stream of documents for PAYLOAD and
XRBLOCK, and we don=E2=80=99t 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=C5=9Fcanu 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 =E2=80=9Cpush the button=E2=80=9D on this, I=E2=80=99d like to giv=
e the working group
a chance to comment: if you feel that there=E2=80=99s a really strong reaso=
n
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=E2=80=99t overlook it).  I
plan to start the process of rechartering AVTCORE and making this
merge in a week or two.

Also, I=E2=80=99m asking the tools team if there=E2=80=99s 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=E2=80=99t know wheth=
er
it=E2=80=99s feasible, but I=E2=80=99ll ask.

Barry, ART Director


From nobody Mon Aug  5 12:52:53 2019
Return-Path: <drageke@ntlworld.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 A4398120033 for <xrblock@ietfa.amsl.com>; Mon,  5 Aug 2019 12:52:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=ntlworld.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 K_jqEvB7jVNj for <xrblock@ietfa.amsl.com>; Mon,  5 Aug 2019 12:52:43 -0700 (PDT)
Received: from know-smtprelay-omc-11.server.virginmedia.net (know-smtprelay-omc-11.server.virginmedia.net [80.0.253.75]) (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 D3BBF12006A for <xrblock@ietf.org>; Mon,  5 Aug 2019 12:52:40 -0700 (PDT)
Received: from [10.107.36.156] ([46.233.78.54]) by cmsmtp with ESMTPA id uj25hOLytXaJRuj25hMGBT; Mon, 05 Aug 2019 20:52:38 +0100
X-Originating-IP: [46.233.78.54]
X-Authenticated-User: drageke@ntlworld.com
X-Spam: 0
X-Authority: v=2.3 cv=IZIzplia c=1 sm=1 tr=0 a=Xe+udFrlaOj9AubnzwbJgA==:117 a=Xe+udFrlaOj9AubnzwbJgA==:17 a=jpOVt7BSZ2e4Z31A5e1TngXxSK0=:19 a=IkcTkHD0fZMA:10 a=48vgC7mUAAAA:8 a=Y03Oi5npF82XuCJYKTIA:9 a=QEXdDO2ut3YA:10 a=w1C3t2QeGrPiZgrLijVG:22
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ntlworld.com; s=meg.feb2017; t=1565034758; bh=cbx43fxo7tszWGSOFynraBKLWtqqP73/pI770XqwJJ8=; h=Subject:To:References:From:Date:In-Reply-To; b=yRsJvQ+8F6EDCLUDDRjWOmi1Pu2s+2gh5Lm3a77A1d0CFWkOCCaKg/ENFiID5siMF LJQnobRgWBfaC1mIyn1wA5PtZd1kXK11mIuw+89eLVL4MN/MMvi5QWwO3qfCgYc5bg CXTPHwwwi1DIyFJXTKKLpGcTeQt1yoa8woSOYj0riiAr2oPhtNNJQP4nctUYij2vJ4 DduiboxEUO009y/7Pa1oTQhxOxy+JXewNGXvRmK0OMyh7C069AqSmP2pOW6MhoISWm 4tFk9lGA3HcZ9YmMs7IFkwYA1CUJhPLS3DXHsHEKk3XuJw599A1OMZLRX7F77/iDEu 7tA7ZnY9mixhg==
To: Barry Leiba <barryleiba@computer.org>, avt@ietf.org, payload@ietf.org, xrblock@ietf.org
References: <CALaySJJAGU-FyodaNz5sZ3Ct3VfetCDEA+mjdoKxz_nXehN_mw@mail.gmail.com>
From: Keith Drage <drageke@ntlworld.com>
Message-ID: <1da5e102-50d0-7244-10a4-2a9e002fb926@ntlworld.com>
Date: Mon, 5 Aug 2019 18:55:41 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0
MIME-Version: 1.0
In-Reply-To: <CALaySJJAGU-FyodaNz5sZ3Ct3VfetCDEA+mjdoKxz_nXehN_mw@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-GB
X-CMAE-Envelope: MS4wfElX7comecCRgNQKvrxms3hdT09Hb02GM5GbV3SH++NzwMH6/9j53F7I5D0MWGwep/iSAwDbIvt7cbkrujihyBNmx0/qevxkMCscA+jrjQWtI+P0Idmo awGSxNzwsEMgp1ZGLDatTNmKK9x3Crs0tR4en6MD2c4ePjX1asDCMS7TXwRUWokx8L0z5Imcu6Li4ID9z1VaYbTfRtYScQeNiSkpiEpWpGyNUr7MkSCjas4I BIHlM2vgSjq/ptvWHoEZ/w==
Archived-At: <https://mailarchive.ietf.org/arch/msg/xrblock/wq9xbKNrZMaTTkaIkSRyJO1G1tg>
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: Mon, 05 Aug 2019 19:52:45 -0000

A comment.

One of the reasons for separating out payload in the first place was to 
distinguish documents that really required a mechanism for expert review 
(in order to assign a payload type) from those documents that required a 
real design group.

Normally a WG is not needed for expert review, but there was a body of 
opinion that some better criteria than a single expert was required. 
Perhaps rather than transferring payload terms of reference to the 
combined group, you should investigate whether there are now more 
appropriate means of handling this.

I would note that for payload, in general the review within the WG seems 
to come from a very small set of experts.

Keith

On 01/08/2019 20:04, Barry Leiba 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
>
> _______________________________________________
> xrblock mailing list
> xrblock@ietf.org
> https://www.ietf.org/mailman/listinfo/xrblock


From nobody Thu Aug 15 12:04:06 2019
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=E2=80=99ve decided to re-m=
erge
> them.  There is no longer a heavy stream of documents for PAYLOAD and
> XRBLOCK, and we don=E2=80=99t expect those that do come in to distract th=
e
> 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=C5=9Fcanu 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 =E2=80=9Cpush the button=E2=80=9D on this, I=E2=80=99d like to g=
ive the working group
> a chance to comment: if you feel that there=E2=80=99s a really strong rea=
son
> 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=E2=80=99t overlook it). =
 I
> plan to start the process of rechartering AVTCORE and making this
> merge in a week or two.
>
> Also, I=E2=80=99m asking the tools team if there=E2=80=99s a reasonable w=
ay 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=E2=80=99t know whe=
ther
> it=E2=80=99s feasible, but I=E2=80=99ll ask.
>
> Barry, ART Director


From nobody Thu Aug 15 12:41:30 2019
Return-Path: <dromasca@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 2C3CE120071; Thu, 15 Aug 2019 12:41:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level: 
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-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 utEAAkNl-BFF; Thu, 15 Aug 2019 12:41:18 -0700 (PDT)
Received: from mail-io1-xd31.google.com (mail-io1-xd31.google.com [IPv6:2607:f8b0:4864:20::d31]) (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 185B312007C; Thu, 15 Aug 2019 12:41:18 -0700 (PDT)
Received: by mail-io1-xd31.google.com with SMTP id q22so1516594iog.4; Thu, 15 Aug 2019 12:41:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=RlbrcAOLYsNRwRd32t6KWzPCAx0171YLlXqtRjQPmMQ=; b=HSY4ECfDXD1RD7L/dzCNZenlj3UZilgVbTfGZfyqZ0ZWN4oAVnj7I1buUAEGHdNAei nWq4YAbyMSCm22C6iQrciGbnVn6DyqoRz3nvbAtbasS3k/6d8fdAn5sTkgEhdxdkYWi+ OZkMOemgfp3TnLERA3X3SmIK3ddIItWD9O1WU+jE5DzrZqY5bd1Dqa94UG8X75+sSOis LJvlnc4GF8izGpmL0cjG1qoq3zRbyVR9gFlKYV/zGipuu4ib8V3pW9CYGo8E7A4aM2Id Wlma3kjqy+ubLfwJPOBGHKrQCXsW7bvXdgZ57kognUDRD8pEycmvxe54LCHeLqS7+Uoh ZV4g==
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:cc; bh=RlbrcAOLYsNRwRd32t6KWzPCAx0171YLlXqtRjQPmMQ=; b=onbyUOzuq7OBaGIs7FDSAJg83pl2bOFRxP9iYacRaFYz3vXeboTyjSTFoJM09XLzXF 7YGN/jowK1BiK8ZfKuLmTa9GhLBww/K0II3eapSQNKeh9gh3fUvytWR28dbspUIxfLqS dYKSXA1uodws/UuKQR2CvYuSk449BiRbzQfVp1MTxnsi0ELEDg/se6dNsJwgRF43PtmX xrcDMlGoCwvN6cBJ9+V4oSS6pCIoh+jfF3amkefXMk8sChL+D4k/UNW3RcAcx7QRhBlH SgdFYRlk0ccIG5iyIjOImV79JFUzuVu6cwyMfBAzUEIUSFwbkPXG00cSKKPHmW7utvYp 5b3w==
X-Gm-Message-State: APjAAAWhKTVa7xe0clRrhg3yGx3yPXe5JkgqWjb9nXbaI0dxVGO5He7r rex3pkZZ+XGdsVBqKEPOoR7mCYuKgopzgRX/oqU=
X-Google-Smtp-Source: APXvYqxGFb+LkDJf0aPKW/tmMnW8bmfUqGDEOcdHT9WAK8wTshr7FmIMqfeSg7HHRsNbGZQREYZ8VbW9l5akbEQCoCU=
X-Received: by 2002:a6b:8f47:: with SMTP id r68mr293209iod.204.1565898077296;  Thu, 15 Aug 2019 12:41:17 -0700 (PDT)
MIME-Version: 1.0
References: <CALaySJJAGU-FyodaNz5sZ3Ct3VfetCDEA+mjdoKxz_nXehN_mw@mail.gmail.com> <CALaySJ+prVrQtFz1dp_Q3Q47MRo0nft=eHyUFCHpWiLVczCd2A@mail.gmail.com>
In-Reply-To: <CALaySJ+prVrQtFz1dp_Q3Q47MRo0nft=eHyUFCHpWiLVczCd2A@mail.gmail.com>
From: Dan Romascanu <dromasca@gmail.com>
Date: Thu, 15 Aug 2019 22:41:05 +0300
Message-ID: <CAFgnS4XmP62j_gmTguT2e8kDfUwZaCWb5yzAFfgLBUPNPJVFGA@mail.gmail.com>
To: Barry Leiba <barryleiba@computer.org>
Cc: avt@ietf.org, payload@ietf.org, xrblock <xrblock@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000a6dc6b05902d0e15"
Archived-At: <https://mailarchive.ietf.org/arch/msg/xrblock/jxSH2nvMPIJoYVyMTCj9hs-lqUo>
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:41:21 -0000

--000000000000a6dc6b05902d0e15
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

This looks great to me.

Thanks to all authors and contributors for their dedicated work in XRBLOCK.
Good luck in the continuation of this work in the reunited AVTCORE WG.

Regards,

Dan



On Thu, Aug 15, 2019 at 10:04 PM Barry Leiba <barryleiba@computer.org>
wrote:

> 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=E2=80=99ve decided to re=
-merge
> > them.  There is no longer a heavy stream of documents for PAYLOAD and
> > XRBLOCK, and we don=E2=80=99t 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=C5=9Fcanu and Shida Schubert have reduced their IETF activi=
ty
> > 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 =E2=80=9Cpush the button=E2=80=9D on this, I=E2=80=99d like to=
 give the working group
> > a chance to comment: if you feel that there=E2=80=99s a really strong r=
eason
> > 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=E2=80=99t overlook it)=
.  I
> > plan to start the process of rechartering AVTCORE and making this
> > merge in a week or two.
> >
> > Also, I=E2=80=99m asking the tools team if there=E2=80=99s 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=E2=80=99t know w=
hether
> > it=E2=80=99s feasible, but I=E2=80=99ll ask.
> >
> > Barry, ART Director
>
> _______________________________________________
> xrblock mailing list
> xrblock@ietf.org
> https://www.ietf.org/mailman/listinfo/xrblock
>

--000000000000a6dc6b05902d0e15
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>This looks great to me. <br></div><div><br></div><div=
>Thanks to all authors and contributors for their dedicated work in XRBLOCK=
. Good luck in the continuation of this work in the reunited AVTCORE WG. <b=
r></div><div><br></div><div>Regards,</div><div><br></div><div>Dan</div><div=
><br></div><div><br></div></div><br><div class=3D"gmail_quote"><div dir=3D"=
ltr" class=3D"gmail_attr">On Thu, Aug 15, 2019 at 10:04 PM Barry Leiba &lt;=
<a href=3D"mailto:barryleiba@computer.org">barryleiba@computer.org</a>&gt; =
wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0=
px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">I have pr=
epared a merged charter for the new AVTCORE working group:<br>
<br>
<a href=3D"https://datatracker.ietf.org/doc/charter-ietf-avtcore/" rel=3D"n=
oreferrer" target=3D"_blank">https://datatracker.ietf.org/doc/charter-ietf-=
avtcore/</a><br>
<br>
It&#39;s currently a draft, and comments and tweaks are encouraged.<br>
What&#39;s there is essentially the three existing charters merged, with<br=
>
some minor editorial changes and a format change to make the result<br>
flow well.=C2=A0 Please let me know whether it looks right, or whether<br>
there are changes we should make.<br>
<br>
I&#39;ve also merged the AVTCORE and PAYLOAD milestones, which you can see<=
br>
below the draft charter.=C2=A0 It would be nice if before we send it to the=
<br>
IESG for review we have some fresh dates for the 2019 milestones that<br>
are already in the past.=C2=A0 Can the chairs please estimate some new<br>
dates for those and let me know?<br>
<br>
Barry<br>
<br>
On Thu, Aug 1, 2019 at 3:04 PM Barry Leiba &lt;<a href=3D"mailto:barryleiba=
@computer.org" target=3D"_blank">barryleiba@computer.org</a>&gt; wrote:<br>
&gt;<br>
&gt; The ART ADs have discussed the AVTCORE, PAYLOAD, and XRBLOCK working<b=
r>
&gt; groups, the reasons the latter two were split off, and the current<br>
&gt; situation.=C2=A0 After discussing those with the other (and former) AR=
T ADs<br>
&gt; and with the chairs of those working groups, I=E2=80=99ve decided to r=
e-merge<br>
&gt; them.=C2=A0 There is no longer a heavy stream of documents for PAYLOAD=
 and<br>
&gt; XRBLOCK, and we don=E2=80=99t expect those that do come in to distract=
 the<br>
&gt; AVTCORE working group from its core (sorry) work.=C2=A0 At the same ti=
me,<br>
&gt; it makes sense to keep that work visible to the AVTCORE community.<br>
&gt;<br>
&gt; As Dan Roma=C5=9Fcanu and Shida Schubert have reduced their IETF activ=
ity<br>
&gt; and are no longer attending meetings, they are stepping down as<br>
&gt; chairs.=C2=A0 Ali Begen will also step down, and I will be looking for=
<br>
&gt; opportunities to use his expertise in chairing other groups.=C2=A0 I v=
ery<br>
&gt; much thank all of them for their service, and urge others to add their=
<br>
&gt; thanks privately.<br>
&gt;<br>
&gt; We will have three chairs for the merged working group, which will<br>
&gt; retain the AVTCORE name: Rachel Huang and Jonathan Lennox will<br>
&gt; continue, and Roni Even will join them and bring his expertise in<br>
&gt; shepherding PAYLOAD documents through the process.=C2=A0 Thanks very m=
uch<br>
&gt; to them, also, for their continued service.<br>
&gt;<br>
&gt; Before I =E2=80=9Cpush the button=E2=80=9D on this, I=E2=80=99d like t=
o give the working group<br>
&gt; a chance to comment: if you feel that there=E2=80=99s a really strong =
reason<br>
&gt; not to do this or to do it differently, please let me know, privately<=
br>
&gt; or on list (in which case, please CC me so I don=E2=80=99t overlook it=
).=C2=A0 I<br>
&gt; plan to start the process of rechartering AVTCORE and making this<br>
&gt; merge in a week or two.<br>
&gt;<br>
&gt; Also, I=E2=80=99m asking the tools team if there=E2=80=99s a reasonabl=
e way to merge<br>
&gt; the datatracker document histories of AVTEXT (12 RFCs and 2 drafts in<=
br>
&gt; cluster 238), PAYLOAD (17 RFCs and 5 drafts), and XRBLOCK (19 RFCs)<br=
>
&gt; into the AVTCORE document list, so we have one place to go for the<br>
&gt; list of documents.=C2=A0 I probably will not look to add the AVT worki=
ng<br>
&gt; group&#39;s RFCs as well, as there are 115 of them.=C2=A0 I don=E2=80=
=99t know whether<br>
&gt; it=E2=80=99s feasible, but I=E2=80=99ll ask.<br>
&gt;<br>
&gt; Barry, ART Director<br>
<br>
_______________________________________________<br>
xrblock mailing list<br>
<a href=3D"mailto:xrblock@ietf.org" target=3D"_blank">xrblock@ietf.org</a><=
br>
<a href=3D"https://www.ietf.org/mailman/listinfo/xrblock" rel=3D"noreferrer=
" target=3D"_blank">https://www.ietf.org/mailman/listinfo/xrblock</a><br>
</blockquote></div>

--000000000000a6dc6b05902d0e15--

