Re: [Mops] Milestones changed for mops WG

Kyle Rose <krose@krose.org> Wed, 06 April 2022 01:25 UTC

Return-Path: <krose@krose.org>
X-Original-To: mops@ietfa.amsl.com
Delivered-To: mops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 808FD3A1797 for <mops@ietfa.amsl.com>; Tue, 5 Apr 2022 18:25:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.108
X-Spam-Level:
X-Spam-Status: No, score=-2.108 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, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=krose.org
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 s5sQ0aSWB9QW for <mops@ietfa.amsl.com>; Tue, 5 Apr 2022 18:25:53 -0700 (PDT)
Received: from mail-wr1-x436.google.com (mail-wr1-x436.google.com [IPv6:2a00:1450:4864:20::436]) (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 F1F633A1794 for <mops@ietf.org>; Tue, 5 Apr 2022 18:25:52 -0700 (PDT)
Received: by mail-wr1-x436.google.com with SMTP id b19so925072wrh.11 for <mops@ietf.org>; Tue, 05 Apr 2022 18:25:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=krose.org; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=lO6CklszbEhxtDl37OmDeZmfHSL6WGT5jq2ssfrpBVQ=; b=c+7yyCwi5hPS1E3T5ZF1M3xope+lHNVrtl/xDpaNTOscFpEgkvxUtTfFsmzM2MkOp2 r+CdNy9vxdsyU7R3tWO7McQV8564EEP+zgeRO5zhc9zo+gNv9AiD6q4Da6D4VMtNrziU XwvuLqvTd6eRE5sMw3beVnydWkIlIuHnlg5OI=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=lO6CklszbEhxtDl37OmDeZmfHSL6WGT5jq2ssfrpBVQ=; b=D79WCT5icuq6XNJfk0UGtmIcz6111if97DZBjk8lY4exlcFopqYsFrFR/nUtYkVKzK 0HbJBBa2vKUHb4mi06vPp3dJqOcX7VoxG5y863MvOxZHI5CY1yDfIptkrSBhzVeT9Hoz gmE5B4nngD6nO55dtK+Hvk2EnH6C5KKxAUgWKgtG7t9bHElNEDqat7ywV74/bVrLhwgK oWb83inwwKPYBj9hXdRRFyi95zM+8TQvoE0gSnRMyWK7WAyA9eIJNcryMmQ3D6nDeKKT Jk4s9hMvPoj2a1jNPP0yQe6F8doxxYyeHXN5j3cQIhALCA3MQ275pPDjhoIkPeaVrDD5 8MRg==
X-Gm-Message-State: AOAM531X0jvSSE4TGm6KFFPm4vLF0fFjLamTZfVVmVap/Kv8UzFLNper 1x8vGj3nO8PzuQMUIL8yzdQPAIQtGtAMH/IzeLHKIwgeIyemvg==
X-Google-Smtp-Source: ABdhPJzga7SfQQbTJrc7GVz30S0AJLisZvI3GUKn96vno27d5iHz1/3/T/aia0msizR+oES2o5MISUnYY8RTjtKFPmM=
X-Received: by 2002:adf:f88d:0:b0:206:1102:60c5 with SMTP id u13-20020adff88d000000b00206110260c5mr4441932wrp.600.1649208350429; Tue, 05 Apr 2022 18:25:50 -0700 (PDT)
MIME-Version: 1.0
References: <164920815765.670.217019879551789866@ietfa.amsl.com>
In-Reply-To: <164920815765.670.217019879551789866@ietfa.amsl.com>
From: Kyle Rose <krose@krose.org>
Date: Tue, 05 Apr 2022 21:25:39 -0400
Message-ID: <CAJU8_nVZ+VVHMqXTyjZPKYF=HLTE1agB08b1L5Z3qGk1N=1LZg@mail.gmail.com>
To: mops@ietf.org
Cc: Leslie Daigle <ldaigle@thinkingcat.com>
Content-Type: multipart/alternative; boundary="000000000000e364d205dbf23d23"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mops/pLlW5OeI1JONCs9uati7yz_zP0w>
Subject: Re: [Mops] Milestones changed for mops WG
X-BeenThere: mops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Media OPerationS <mops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mops>, <mailto:mops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mops/>
List-Post: <mailto:mops@ietf.org>
List-Help: <mailto:mops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mops>, <mailto:mops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Apr 2022 01:25:58 -0000

I've adjusted the milestones to reflect the chairs' proposal from IETF 113.
Rather than "TBD", I had to put in a date for LC of the low-latency opcons
draft, so I pulled Nov 2022 out of a hat since that's what was pre-selected
by the data tracker.

Kyle

On Tue, Apr 5, 2022 at 9:22 PM IETF Secretariat <
ietf-secretariat-reply@ietf.org> wrote:

> Deleted milestone "Last-call document on edge network considerations for
> streaming media".
>
> Deleted milestone "Draft documenting Society of Motion Picture and
> Television
> Engineers (SMPTE) protocol reliance on IETF protocols".
>
> Changed milestone "IESG to decide whether continue, re-charter or close
> MOPS
> WG", resolved as "Done".
>
> Changed milestone "Revised draft operational considerations for low latency
> streaming video applications", set due date to February 2022 from July
> 2021,
> resolved as "Done".
>
> Changed milestone "Draft documenting Streaming Video Alliance (SVA)
> reliance
> on IETF protocols", set due date to July 2022 from July 2021.
>
> Deleted milestone "Last-call document on Society of Motion Picture and
> Television Engineers (SMPTE) protocol reliance on IETF protocols (including
> explicit outreach to SMPTE)".
>
> Changed milestone "Last-call document on operational considerations for low
> latency streaming video applications", set due date to November 2022 from
> November 2021.
>
> Changed milestone "Last-call document on Streaming Video Alliance (SVA)
> reliance on IETF protocols (including explicit outreach to SVA)", set due
> date to November 2022 from July 2022.
>
> URL: https://datatracker.ietf.org/wg/mops/about/
>
> --
> Mops mailing list
> Mops@ietf.org
> https://www.ietf.org/mailman/listinfo/mops
>