IETF Logo Mail Archive

Re: [rfc-i] New proposal/New SOW comment period

S Moonesamy <sm+ietf@elandsys.com> Sat, 31 August 2019 05:34 UTC

Return-Path: <rfc-interest-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-interest-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-interest-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 974FC120026 for <ietfarch-rfc-interest-archive@ietfa.amsl.com>; Fri, 30 Aug 2019 22:34:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.752
X-Spam-Level:
X-Spam-Status: No, score=-4.752 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=opendkim.org header.b=H1r86Wux; dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=elandsys.com header.b=dJlFenmW
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 THIPoAtDti6q for <ietfarch-rfc-interest-archive@ietfa.amsl.com>; Fri, 30 Aug 2019 22:34:46 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B9C891200DE for <rfc-interest-archive-eekabaiReiB1@ietf.org>; Fri, 30 Aug 2019 22:34:46 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id BDB81B81376; Fri, 30 Aug 2019 22:34:28 -0700 (PDT)
X-Original-To: rfc-interest@rfc-editor.org
Delivered-To: rfc-interest@rfc-editor.org
Received: from localhost (localhost [127.0.0.1]) by rfc-editor.org (Postfix) with ESMTP id 6B9CFB81373 for <rfc-interest@rfc-editor.org>; Fri, 30 Aug 2019 22:34:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at rfc-editor.org
Authentication-Results: rfcpa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=opendkim.org header.b=H1r86Wux; dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=elandsys.com header.b=dJlFenmW
Received: from rfc-editor.org ([127.0.0.1]) by localhost (rfcpa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Phufteck4Om4 for <rfc-interest@rfc-editor.org>; Fri, 30 Aug 2019 22:34:26 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by rfc-editor.org (Postfix) with ESMTP id 8FEB2B81372 for <rfc-interest@rfc-editor.org>; Fri, 30 Aug 2019 22:34:26 -0700 (PDT)
Received: from DESKTOP-K6V9C2L.elandsys.com ([102.115.199.34]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id x7V5YKvb002967 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 30 Aug 2019 22:34:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1567229674; x=1567316074; bh=dz2D2HNC2IwPU5FK6MU8gr6Y78sESuswYwtUCJyOr5k=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=H1r86WuxJCbn+xMRwkrkE3l+j2qEtZYGdonfL++WbFMG5EMRYh3du9/azf0wU1RVC secIHi661807XvsTQwK2Dleb6+Pcla9i+V751K8qx/ZUAcpBahuo2TcsocLESowBOO MIvnD2FK0FmHmxkeJwvPWeETK1E0bzXLfliRjHuc=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1567229674; x=1567316074; i=@elandsys.com; bh=dz2D2HNC2IwPU5FK6MU8gr6Y78sESuswYwtUCJyOr5k=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=dJlFenmWLY7klhdAozUeg01gxzVKQpCSoWF/TXDB1DlqLgyICcGKGQ9KZldL3qOKs FQQ+fr82DP40mdOQjQq3CeLOmO9lR3TGnTabho3pC9RWbKylAmdind3VGBvTz+DVJJ JcdcpFqm0geCpf+KT9srH5suDqbaKvD/0LbzNxWo=
Message-Id: <6.2.5.6.2.20190830214019.0ba94918@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Fri, 30 Aug 2019 22:34:05 -0700
To: Adam Roach <adam@nostrum.com>, rfc-interest@rfc-editor.org
From: S Moonesamy <sm+ietf@elandsys.com>
In-Reply-To: <5dd85c7b-84d4-9192-db70-28e61ed3bf01@nostrum.com>
References: <4675DA5C-0CFE-4E02-980D-770B17907D35@encrypted.net> <6.2.5.6.2.20190830124138.08d4ab38@elandnews.com> <5dd85c7b-84d4-9192-db70-28e61ed3bf01@nostrum.com>
Mime-Version: 1.0
Subject: Re: [rfc-i] New proposal/New SOW comment period
X-BeenThere: rfc-interest@rfc-editor.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "A list for discussion of the RFC series and RFC Editor functions." <rfc-interest.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-interest>, <mailto:rfc-interest-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-interest/>
List-Post: <mailto:rfc-interest@rfc-editor.org>
List-Help: <mailto:rfc-interest-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-interest>, <mailto:rfc-interest-request@rfc-editor.org?subject=subscribe>
Cc: rsoc@iab.org
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Errors-To: rfc-interest-bounces@rfc-editor.org
Sender: rfc-interest <rfc-interest-bounces@rfc-editor.org>

Hi Adam,
At 01:15 PM 30-08-2019, Adam Roach wrote:
>The IAB sent a follow-up note addressing this point.

Thanks for the pointer.

I am a bit skeptical when I see words such as "tactical" and 
"strategic" in organizational plans.  I would list that the execution 
of a plan under "tactical".

As a minor point, there has been several comments [1] about seeking 
someone with "RFC author" experience.  I don't understand the 
rationale for insisting on having that in.

Regards,
S. Moonesamy

1. One of the comments was from an IAB member. 

_______________________________________________
rfc-interest mailing list
rfc-interest@rfc-editor.org
https://www.rfc-editor.org/mailman/listinfo/rfc-interest

v2.23.0 | Report a Bug | By Email