IETF Logo Mail Archive

Re: [Eligibility-discuss] Virtual BoF for draft-moonesamy-recall-rev

Suresh Krishnan <suresh.krishnan@gmail.com> Fri, 07 June 2019 02:28 UTC

Return-Path: <suresh.krishnan@gmail.com>
X-Original-To: eligibility-discuss@ietfa.amsl.com
Delivered-To: eligibility-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DD6441200FF for <eligibility-discuss@ietfa.amsl.com>; Thu, 6 Jun 2019 19:28:18 -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, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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 (2048-bit key) header.d=gmail.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 Vl6oxSIOZur8 for <eligibility-discuss@ietfa.amsl.com>; Thu, 6 Jun 2019 19:28:17 -0700 (PDT)
Received: from mail-qt1-x831.google.com (mail-qt1-x831.google.com [IPv6:2607:f8b0:4864:20::831]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 811ED1200F8 for <eligibility-discuss@ietf.org>; Thu, 6 Jun 2019 19:28:17 -0700 (PDT)
Received: by mail-qt1-x831.google.com with SMTP id i34so623200qta.6 for <eligibility-discuss@ietf.org>; Thu, 06 Jun 2019 19:28:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=5PVuoL9v7OfKt0I13jP0aaT9EKp3S0BobshJnObK5O0=; b=B6g34JVVWn2UST9TzXi86m19KuPgty4F4/TYPHCQ/bq6qU9GqVNvc9xSDfcbGUFxmz 9SUVE6oUYGlQVQmup65yUIpQ0YJvc3tpLJWkShBjCuPasxjuufPbRVBD5WPm41wBVOpO l3AD0dS7o4BqA2UHQZetju37UUObLUA/vE9zb/yzTDMOFveAK81m4pHkc+NwKjxbt0OD AY/cjCXYwxX2b7vHtOZmmXFwPUrEdkhk/QvqeKAT5JA567KNgauT2xyB+9t7Y9Dlc1ss J39iApVa/dXxCcPgbMMEE5j3Df7JcY/TaURV5uGYf8Z9Dcfaw8ieqUmMAYLYj5utnZR3 j7NA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=5PVuoL9v7OfKt0I13jP0aaT9EKp3S0BobshJnObK5O0=; b=MqOj5uh2cTZFMey0zx0In4wH46euU/sbMKORypTbb+Q2PNDHXWnAR5yloj4MNbwLSD Vp8KsvlNlAhq7VNRfhCwb5+lwwAbIekoqnhOHDU7hczfx4C3jIfm1cf+RjevlU3bhkKS v1eWIFUw6uBxpgioYCpu76Ms66kcEHsp4V8p3qBlpIOE0qNshEelWOArjXvLO1zbotoX AUqpSFrz8uVzuScBfgNboAxefiXcBIHDwaw1H0LZtUJuF2KEKFINmREX94NJdtTtg8ov 67fKeeJ0ehz2l9n0T7jETV+9TgK88ikHstcEKeI08QYTm9hhVImp1yoxwdRvA8UrfH9Y +iPg==
X-Gm-Message-State: APjAAAUMjQr2N6w9pFdcqRN9mFrEl+8OEmaWZLlALtNP6qV61eDutOa2 6hTyrTmhm3lDKDCxDACc6s4=
X-Google-Smtp-Source: APXvYqzA3hiLrwlYKQQuALUwuR8pPX2rTZkt+OxCrsR9V2WIb5tYkkH8ufWzORLXEh2apXJyySsOpA==
X-Received: by 2002:ac8:7652:: with SMTP id i18mr35719513qtr.10.1559874496581; Thu, 06 Jun 2019 19:28:16 -0700 (PDT)
Received: from [10.0.0.15] (45-19-110-76.lightspeed.tukrga.sbcglobal.net. [45.19.110.76]) by smtp.gmail.com with ESMTPSA id v186sm376664qkc.36.2019.06.06.19.28.15 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 06 Jun 2019 19:28:15 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
From: Suresh Krishnan <suresh.krishnan@gmail.com>
In-Reply-To: <6.2.5.6.2.20190604124032.0c2f0ca0@elandnews.com>
Date: Thu, 06 Jun 2019 22:28:14 -0400
Cc: eligibility-discuss@ietf.org, Warren Kumari <warren@kumari.net>, Alexey Melnikov <aamelnikov@fastmail.fm>
Content-Transfer-Encoding: quoted-printable
Message-Id: <942E0B4F-1A9D-4154-84E4-2CDCD8876BF4@gmail.com>
References: <6.2.5.6.2.20190525144314.0e72bb68@elandnews.com> <6.2.5.6.2.20190601204707.0bf89070@elandnews.com> <D58B591C-9140-4273-AA11-59E2EBD101FE@gmail.com> <6.2.5.6.2.20190604124032.0c2f0ca0@elandnews.com>
To: S Moonesamy <sm+ietf@elandsys.com>
X-Mailer: Apple Mail (2.3445.104.11)
Archived-At: <https://mailarchive.ietf.org/arch/msg/eligibility-discuss/_3FIkyAPgQUpvfbynwojUlHuJgg>
Subject: Re: [Eligibility-discuss] Virtual BoF for draft-moonesamy-recall-rev
X-BeenThere: eligibility-discuss@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <eligibility-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/eligibility-discuss>, <mailto:eligibility-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/eligibility-discuss/>
List-Post: <mailto:eligibility-discuss@ietf.org>
List-Help: <mailto:eligibility-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/eligibility-discuss>, <mailto:eligibility-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Jun 2019 02:28:19 -0000

Hi SM,

> On Jun 4, 2019, at 3:49 PM, S Moonesamy <sm+ietf@elandsys.com> wrote:
> 
> Hi Suresh,
> At 08:22 PM 03-06-2019, Suresh Krishnan wrote:
>> Also, mention whether you would like this to be a working group forming BoF or not. One other suggestion I would make is to put the virtual BoF request into
> 
> Thank you for responding.
> 
> The advice from the IETF Chair was to have a BOF to process the draft.  I approached the Area Directors, as suggested by the IETF Chair, about the BOF.  Could Warren, Alexey or you provide some expert advice on whether a working group forming BoF should be requested?

Just speaking for myself here. I think this depends on how you want to scope the discussion. If you can go with a fairly narrow set of goals with a defined scope and deliverables, I think a WG forming BoF would be a good idea. If you want to explore the problem space a bit, I think a non-WG forming BoF might be a better fit.

Thanks
Suresh

v2.23.0 | Report a Bug | By Email