[vmeet] Comments about draft-atlas-geo-focused-activities-00
S Moonesamy <sm+ietf@elandsys.com> Fri, 11 August 2017 22:02 UTC
Return-Path: <sm@elandsys.com>
X-Original-To: vmeet@ietfa.amsl.com
Delivered-To: vmeet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D352B1326A9 for <vmeet@ietfa.amsl.com>; Fri, 11 Aug 2017 15:02:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.79
X-Spam-Level:
X-Spam-Status: No, score=-1.79 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, T_DKIM_INVALID=0.01] autolearn=no 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=fK6dOd3o; dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=elandsys.com header.b=EyoyeHF3
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 SLM3uAJf_IMm for <vmeet@ietfa.amsl.com>; Fri, 11 Aug 2017 15:02:12 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id A67FC132256 for <vmeet@ietf.org>; Fri, 11 Aug 2017 15:02:12 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([197.227.83.78]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id v7BM1voB024423 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 11 Aug 2017 15:02:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1502488931; x=1502575331; bh=3HR7JujSV2q6u3xh9OYGcCsGsC5dhLiqBNcdrqIssWc=; h=Date:To:From:Subject:Cc; b=fK6dOd3ovfETS8egZQPQaRAZn+0AWcDKg6Git0yT1ksDkikICxzFDyo2zVZvPJNUx XJkD27unG07/0rb1q/ibk63w2rRxiYCk9zLpso6Oi4yejiOlEj7cNglOjf94NBzwuS lGMpG+kit4giKkUuRj+pwuNK+jV0VO+Hbm7W6eFE=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1502488931; x=1502575331; i=@elandsys.com; bh=3HR7JujSV2q6u3xh9OYGcCsGsC5dhLiqBNcdrqIssWc=; h=Date:To:From:Subject:Cc; b=EyoyeHF3Z4HqLHLPeDbwfyH5dzIR49sPl4C5S7x/lGKtG74OP61QPScPBt7Es1qmD iVJVaQvppwD7MVyCRLam6lZK/XZPSqeBZIK/CK+b4fRWRxQGHiQ3/4ilc+RC7sxkgw BsozSf2flda3UeiW5T+iblWH05jLOk7s2KoBI4so=
Message-Id: <6.2.5.6.2.20170811143655.0ee31580@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Fri, 11 Aug 2017 15:01:36 -0700
To: Alia Atlas <akatlas@juniper.net>, Christian O'Flaherty <oflaherty@isoc.org>, Harish Chowdhary <harish@nixi.in>
From: S Moonesamy <sm+ietf@elandsys.com>
Cc: vmeet@ietf.org
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/vmeet/Z-_-ctL6SIquSAMdDBmhrbV2jAc>
Subject: [vmeet] Comments about draft-atlas-geo-focused-activities-00
X-BeenThere: vmeet@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF remote participation meeting services discussion <vmeet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/vmeet>, <mailto:vmeet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/vmeet/>
List-Post: <mailto:vmeet@ietf.org>
List-Help: <mailto:vmeet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/vmeet>, <mailto:vmeet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 11 Aug 2017 22:02:14 -0000
Hi Alia, Christian, Harish,
I have a few comments about
draft-atlas-geo-focused-activities-00. Is the "IETF Local Community"
meant to be a local chapter of the IETF?
In Section 3:
"It is expected that oversight MAY be delegated to the Directorate
member in charge of Outreach Programs; the Directorate MUST be
notified of such and MAY choose to override the decision."
The sentence could be rephrased to avoid overuse of RFC 2119 keywords.
As I read the rest of the draft, I was left with a sense that the RFC
2119 keywords are there to provide rules without providing explanations.
In an IETF session, it is not only a matter of showing the "Note
Well" and explaining what it means. There is also some "paper trail"
to verify whether there was an issue. How is that done for a remote hub?
Section 4.5 allows the "IETF logo and IETF name, with suitable
oversight". If I understood that section correctly, it would be up
to the (local) Coordinators to provide oversight?
Is there a wiki with information from Section 7 given that there has
been remote hubs for past meetings?
Regards,
S. Moonesamy