[Mops] Martin Vigoureux's No Objection on charter-ietf-mops-00-01: (with COMMENT)

Martin Vigoureux via Datatracker <noreply@ietf.org> Thu, 17 October 2019 11:40 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: mops@ietf.org
Delivered-To: mops@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 0104E120119; Thu, 17 Oct 2019 04:40:29 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Martin Vigoureux via Datatracker <noreply@ietf.org>
To: The IESG <iesg@ietf.org>
Cc: mops-chairs@ietf.org, mops@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.105.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Martin Vigoureux <martin.vigoureux@nokia.com>
Message-ID: <157131242894.9380.7742689852610715402.idtracker@ietfa.amsl.com>
Date: Thu, 17 Oct 2019 04:40:28 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/mops/xP7rL7Fx8YgKp2fc_0TGyotdO24>
Subject: [Mops] Martin Vigoureux's No Objection on charter-ietf-mops-00-01: (with COMMENT)
X-BeenThere: mops@ietf.org
X-Mailman-Version: 2.1.29
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: Thu, 17 Oct 2019 11:40:29 -0000

Martin Vigoureux has entered the following ballot position for
charter-ietf-mops-00-01: 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:
----------------------------------------------------------------------

I like the idea of having such type of WG.
However, I find that publishing something like 4 or 5 RFCs is a lot (too much?)
compared to the scope of the group. In comparison LAKE doesn't even plan on
publishing (as an RFC) requirements for the technology it will develop.