Re: [Mops] Mirja Kühlewind's No Objection on charter-ietf-mops-00-03: (with COMMENT)

"Leslie Daigle" <ldaigle@thinkingcat.com> Wed, 30 October 2019 21:31 UTC

Return-Path: <ldaigle@thinkingcat.com>
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 4C8D6120A4D; Wed, 30 Oct 2019 14:31:34 -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, HTML_MESSAGE=0.001, 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 (1024-bit key) header.d=thinkingcat.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 RmiTZUv1j9d1; Wed, 30 Oct 2019 14:31:31 -0700 (PDT)
Received: from crane.ash.relay.mailchannels.net (crane.ash.relay.mailchannels.net [23.83.222.43]) (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 20A961208F8; Wed, 30 Oct 2019 14:31:28 -0700 (PDT)
X-Sender-Id: dreamhost|x-authsender|ldaigle@thinkingcat.com
Received: from relay.mailchannels.net (localhost [127.0.0.1]) by relay.mailchannels.net (Postfix) with ESMTP id 170528C1429; Wed, 30 Oct 2019 21:31:25 +0000 (UTC)
Received: from pdx1-sub0-mail-a30.g.dreamhost.com (100-96-92-150.trex.outbound.svc.cluster.local [100.96.92.150]) (Authenticated sender: dreamhost) by relay.mailchannels.net (Postfix) with ESMTPA id 5C1C78C16E0; Wed, 30 Oct 2019 21:31:24 +0000 (UTC)
X-Sender-Id: dreamhost|x-authsender|ldaigle@thinkingcat.com
Received: from pdx1-sub0-mail-a30.g.dreamhost.com ([TEMPUNAVAIL]. [64.90.62.162]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384) by 0.0.0.0:2500 (trex/5.18.5); Wed, 30 Oct 2019 21:31:24 +0000
X-MC-Relay: Neutral
X-MailChannels-SenderId: dreamhost|x-authsender|ldaigle@thinkingcat.com
X-MailChannels-Auth-Id: dreamhost
X-Cure-Harbor: 3e12d618564d857b_1572471084811_2197547788
X-MC-Loop-Signature: 1572471084811:882028050
X-MC-Ingress-Time: 1572471084811
Received: from pdx1-sub0-mail-a30.g.dreamhost.com (localhost [127.0.0.1]) by pdx1-sub0-mail-a30.g.dreamhost.com (Postfix) with ESMTP id 3AB2280D84; Wed, 30 Oct 2019 14:31:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=thinkingcat.com; h=from:to :cc:subject:date:message-id:in-reply-to:references:mime-version :content-type:content-transfer-encoding; s=thinkingcat.com; bh=e HpVBY6V6AkHUmqbVz7JBc/90tw=; b=bpjaoUlfCTsJ5uBw2u7omKEYhNHtFmPap aSiaelOtnxN1ymCGl9lVjMGRrOhS9wk7Nh3LRvkVirD/ybqbmgj7VAYg76syquh7 cT9mZCWe/4hhQ4k7WNqQyUzsxKgYBqTgCude9l+O+i4/GhOb5VWgQo7+azFCwWmC 17u8EqblYE=
Received: from [192.168.1.57] (vtelinet-216-66-102-83.vermontel.net [216.66.102.83]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: ldaigle@thinkingcat.com) by pdx1-sub0-mail-a30.g.dreamhost.com (Postfix) with ESMTPSA id C9F36971CD; Wed, 30 Oct 2019 14:31:17 -0700 (PDT)
X-DH-BACKEND: pdx1-sub0-mail-a30
From: Leslie Daigle <ldaigle@thinkingcat.com>
To: Mirja Kühlewind <ietf@kuehlewind.net>
Cc: The IESG <iesg@ietf.org>, mops-chairs@ietf.org, mops@ietf.org
Date: Wed, 30 Oct 2019 17:31:03 -0400
X-Mailer: MailMate (1.13r5655)
Message-ID: <62E597EC-4FC1-461A-A2D8-C0ADA23C5114@thinkingcat.com>
In-Reply-To: <157245520739.32588.18268012598112433098.idtracker@ietfa.amsl.com>
References: <157245520739.32588.18268012598112433098.idtracker@ietfa.amsl.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="=_MailMate_ABC0829E-732E-4892-8EF4-F9E9D82621C6_="
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/mops/pO9LRomy3TGsfrA4Dmcn9KK1YdA>
Subject: Re: [Mops] Mirja Kühlewind's No Objection on charter-ietf-mops-00-03: (with COMMENT)
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, 30 Oct 2019 21:31:34 -0000

Hi,

Thanks — some thoughts, inline:

On 30 Oct 2019, at 13:06, Mirja Kühlewind via Datatracker wrote:

> Mirja Kühlewind has entered the following ballot position for
> charter-ietf-mops-00-03: No Objection
>
> When responding, please keep the subject line intact and reply to all
> email addresses included in the To and CC lines. (Feel free to cut 
> this
> introductory paragraph, however.)
>
>
>
> The document, along with other ballot positions, can be found here:
> https://datatracker.ietf.org/doc/charter-ietf-mops/
>
>
>
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
>
> Two small editorial comments:
> 1) "Internet- and Internet-protocol-delivered media"
> Not sure I understand the difference here. I would assume that a media 
> that is
> sent over the Internet would also use some Internet-protocol...?

Yeah, this text was the result of us trying to capture the opposite 
case:  when something uses the Internet-Protocol but doesn’t go out 
over the big-I Internet.


>
> 2)"existing protocols and/or networks are challenged by these updated
> requirements." "these" seems to be out of context now.

Could be deleted, indeed.

>
> And two questions:
>
> 1) "If there is no longer sufficient interest in the
> Working Group in a work item, the item may be removed from the list of 
> Working
> Group items."
> Where/how is the list of Working Group Items maintain? Are we talking 
> here
> about working group documents, or milestones, or something else (in a 
> wiki
> maybe)? And what does removing mean? That it cannot be discussed on 
> the mailing
> list anymore? That is will not get any presentation time? Something 
> else? Not
> sure how easy it will be to enforce these things or what that means in
> practice...

My thinking was along the lines of adopting items as formal working 
group documents (draft-ietf-mops…).  If there is no longer interest, 
the documents can be pursued as individual I-Ds, etc.

For other items — agenda time, etc — I think it will require chair 
discretion as to whether there is continued interest (and that can be 
contested on the mailing list, of course).

Yes, in practice, it’s going to take a bit of work…

>
> 2) The charter only talks about documenting problems. Does that mean 
> any kind
> of BCP-like work is out of scope?

For operations, there is mention of documenting work arounds:
“2/ Solicit input from network operators and users to identify 
operational
issues with media delivery in and across networks, and determine 
solutions or
workarounds to those issues.”

But, for most existing technology, BCP work would probably belong in a 
different WG — one focused on that technology.

Leslie.

-- 

-------------------------------------------------------------------
Leslie Daigle
Principal, ThinkingCat Enterprises
ldaigle@thinkingcat.com
-------------------------------------------------------------------