IETF Logo Mail Archive

Re: [OPSAWG] 🔔 WG Adoption Call for draft-feng-opsawg-incident-management-04

Henk Birkholz <henk.birkholz@ietf.contact> Tue, 20 February 2024 15:33 UTC

Return-Path: <henk.birkholz@ietf.contact>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EC47CC14F702; Tue, 20 Feb 2024 07:33:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.897
X-Spam-Level:
X-Spam-Status: No, score=-2.897 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, NICE_REPLY_A=-0.091, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H5=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=ietf.contact
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NVCXyV_ip9QS; Tue, 20 Feb 2024 07:32:59 -0800 (PST)
Received: from smtp04-ext3.udag.de (smtp04-ext3.udag.de [62.146.106.41]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1343DC14F700; Tue, 20 Feb 2024 07:32:59 -0800 (PST)
Received: from [192.168.16.50] (p4fce9f0e.dip0.t-ipconnect.de [79.206.159.14]) by smtp04-ext3.udag.de (Postfix) with ESMTPA id F1FC2E013E; Tue, 20 Feb 2024 16:32:56 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ietf.contact; s=uddkim-202310; t=1708443177; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=ge01ty4TQcboLTDaHM2noj+7T/tD3WjzyBlPPShHDtw=; b=XCfKEgNhlAaGhIur2Be5wQGeQ0RrkH5uIphlEvj9lcwD+x82pbzpB+8GMMSkt6fslsHtBc eBidUCxsQt5n54/ux5Z6qkWlXIGY2NM71eSOJn0mESxLdsfj4RvQbcR3jesynBbRjEVNq/ /CSPUOs6CefEgiIQtTH+OxAEahfIeMxu5LF+dtw8UHEs/FcfiZd8rpLcWc9KPTMMGfDNDp yS6tSieYx0pe4lhhOAem1N5Beg2bsCFDUSWEd9cQI/ExYl+Fgsuay0EozxmMq+FsfnSx7S T1yWuDXT62PeJOxsMdsVfrPqbRkM1d6jB8jB7OProLA2QYSIwpWeW7sZgD2IKg==
Message-ID: <9c50682a-ca4d-cfdf-fc5a-407c2ffe724b@ietf.contact>
Date: Tue, 20 Feb 2024 16:32:56 +0100
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.11.0
Content-Language: en-US
To: Michael Richardson <mcr+ietf@sandelman.ca>, OPSAWG <opsawg@ietf.org>, "nmop@ietf.org" <nmop@ietf.org>
References: <97e25762a5d54b1f9ff9fd22f741059e@huawei.com> <31922.1708440512@obiwan.sandelman.ca>
From: Henk Birkholz <henk.birkholz@ietf.contact>
In-Reply-To: <31922.1708440512@obiwan.sandelman.ca>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Authentication-Results: smtp04-ext3.udag.de; auth=pass smtp.auth=henk.birkholz@ietf.contact smtp.mailfrom=henk.birkholz@ietf.contact
Archived-At: <https://mailarchive.ietf.org/arch/msg/opsawg/0mahr8cHBTBvdb-7qe1Y4EV2k04>
Subject: Re: [OPSAWG] 🔔 WG Adoption Call for draft-feng-opsawg-incident-management-04
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsawg/>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Feb 2024 15:33:03 -0000

We'll conclude the WG Adoption Call in OPSAWG as planned and the result 
will be one input to the NMOP chairs. Another input, of course, is the 
notion of that "yet another set of terminology" would require 
"collaboration and cooperation being clearly spelled out" to ensure 
consistency.

The former is an adoption consideration, the latter is both an adoption 
consideration and a potential WG item task.

On 20.02.24 15:48, Michael Richardson wrote:
> 
> Qin Wu <bill.wu=40huawei.com@dmarc.ietf.org> wrote:
>      > Hi, NMOP Chairs: Since this document has been discussed in OPSAWG for a
>      > long time, and because it was ready for adoption there, and considering
>      > that it is now 'suddenly' in scope for NMOP, could we please consider
>      > moving the existing adoption poll to NMOP (perhaps extending it to make
>      > up for time when NMOP was not aware of the poll).
> 
> That sounds like a good idea to me.
> 
> I'll point out that WG chairs adopt documents by fiat: it's up to them.
> [with being replaced by the AD if they do the wrong thing]
> This business with consulting people is a courtesy :-)
> So, Benoit and Mohammed (NMOP chairs) can just do this.
> 
> 
> --
> Michael Richardson <mcr+IETF@sandelman.ca>   . o O ( IPv6 IøT consulting )
>             Sandelman Software Works Inc, Ottawa and Worldwide
> 
> 
> 
> 
> 
> _______________________________________________
> OPSAWG mailing list
> OPSAWG@ietf.org
> https://www.ietf.org/mailman/listinfo/opsawg

v2.28.0 | Report a Bug | By Email | System Status