IETF Logo Mail Archive

Re: [Ietf-hub-boston] next IETF Boston community meeting

<rmukherjee@128technology.com> Thu, 26 April 2018 15:27 UTC

Return-Path: <rmukherjee@128technology.com>
X-Original-To: ietf-hub-boston@ietfa.amsl.com
Delivered-To: ietf-hub-boston@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 589F712DA21 for <ietf-hub-boston@ietfa.amsl.com>; Thu, 26 Apr 2018 08:27:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.01
X-Spam-Level:
X-Spam-Status: No, score=-0.01 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=1.989, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=128technology.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 BFMnHqtBO0df for <ietf-hub-boston@ietfa.amsl.com>; Thu, 26 Apr 2018 08:27:04 -0700 (PDT)
Received: from mail-pf0-x229.google.com (mail-pf0-x229.google.com [IPv6:2607:f8b0:400e:c00::229]) (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 9E87B12E041 for <ietf-hub-boston@ietf.org>; Thu, 26 Apr 2018 08:27:04 -0700 (PDT)
Received: by mail-pf0-x229.google.com with SMTP id a11so666190pfn.9 for <ietf-hub-boston@ietf.org>; Thu, 26 Apr 2018 08:27:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=128technology.com; s=google; h=from:to:cc:references:in-reply-to:subject:date:message-id :mime-version:thread-index:content-language; bh=6yo+a9Qj1StP1Umc8h5qQK2cFuJQNh32djS2zVpBDr4=; b=Nfib0TerN6sIFrRihmecjm/i9YPqqjw8TOVuGlvX9vmjo8S5fErkKWR6pJ+fM6JOum 3cfTmuJEn+O3i2ZLJWu0HFb9K/0KyaGL/6nLgIVltmvHnmi+kUqziO2iWqjepQZgATLr HzCcWYyMgab60QiqfCTxPxYdFci2j1r4x1NVE=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:references:in-reply-to:subject:date :message-id:mime-version:thread-index:content-language; bh=6yo+a9Qj1StP1Umc8h5qQK2cFuJQNh32djS2zVpBDr4=; b=BR8OPyba93GaAk7XOAW87Q+0BQxdPNKT/0kRNWVV84MJbXpGUDOTF6JBE7Mfdui8Hv ZyPWkOIud5KKSFVyTMwINWef4johOVE3pp3EwPC/1cmaWd4NSWEyZL9jcquYBrJb86yK PfeSm+vlBjEidGhEv9pJmslGVBSCNmgCTMcS9l1OTLNs51o9COCVG7XGw/Pfik5FMIPa pVC3oQSSqFX2IQaiGxa1QgwJB/KXgUP5BiHCrCJ3/N9GullkOUfIfTzYsNmD7JVECf90 hK8VVyZsNONBzGb+p120jz38ew5ocHRUxr1a7HCWiNseJQ1izaBztmp2Lgd0hIijyc35 /Vjw==
X-Gm-Message-State: ALQs6tCTucEX+AjEa+JCIVBlhy1v3w964uATUefjGBk4vZ5bzahNW0a1 Ps8bXnWbp3Jmngwm50lJI+MSyQ==
X-Google-Smtp-Source: AB8JxZp4eVHToxTjM1gYQYPkjvQ4lKq9b2yuhLnGxAjsPtoxTOkJiPYFTeeLuaDVYC0e+Jnc2Zv01w==
X-Received: by 10.167.133.131 with SMTP id w3mr12909207pfn.197.1524756424055; Thu, 26 Apr 2018 08:27:04 -0700 (PDT)
Received: from DESKTOP8FK1D5K ([216.9.110.5]) by smtp.gmail.com with ESMTPSA id v16sm42035744pfj.123.2018.04.26.08.27.02 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 26 Apr 2018 08:27:03 -0700 (PDT)
From: rmukherjee@128technology.com
To: "'Salz, Rich'" <rsalz@akamai.com>, 'Aaron Falk' <aaron.falk@gmail.com>, 'Alia Atlas' <akatlas@gmail.com>
Cc: ietf-hub-boston@ietf.org, 'Dan York' <york@isoc.org>
References: <CAG4d1rffG1NAsjSCeaL-ma0OQfLZeXxmRT9tuhudAZ+1RZSyhQ@mail.gmail.com> <7BCC05F5-73B4-41AD-930E-E9B85549B1FD@isoc.org> <CAG4d1rfELBqNZbDBdqz2HxDjecsN6o-YHu_4Xp-=yq11C=tXbQ@mail.gmail.com> <69814607-5DC2-413E-95F8-B6E5468C9CC3@gmail.com> <86649E8C-481A-413E-858C-7D31641CEFC8@akamai.com>
In-Reply-To: <86649E8C-481A-413E-858C-7D31641CEFC8@akamai.com>
Date: Thu, 26 Apr 2018 11:27:00 -0400
Message-ID: <002b01d3dd73$06aec190$140c44b0$@128technology.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_002C_01D3DD51.7FA9A4B0"
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQJjPAeUakFjiXGz3mxfntpU+ZOzxQH9x+K4AeumW1ABxz9N7ALX9RXRorAonUA=
Content-Language: en-us
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-hub-boston/pzxBhatXCLrmFlUvUvkAtuMIZUA>
Subject: Re: [Ietf-hub-boston] next IETF Boston community meeting
X-BeenThere: ietf-hub-boston@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "For IETFers in the Boston area." <ietf-hub-boston.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-hub-boston>, <mailto:ietf-hub-boston-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-hub-boston/>
List-Post: <mailto:ietf-hub-boston@ietf.org>
List-Help: <mailto:ietf-hub-boston-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-hub-boston>, <mailto:ietf-hub-boston-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 26 Apr 2018 15:27:12 -0000

You are welcome to use a meeting room at 128 Technology on May 08th. Let me know.

 

 

From: Ietf-hub-boston <ietf-hub-boston-bounces@ietf.org> On Behalf Of Salz, Rich
Sent: Thursday, April 26, 2018 11:15 AM
To: Aaron Falk <aaron.falk@gmail.com>; Alia Atlas <akatlas@gmail.com>
Cc: ietf-hub-boston@ietf.org; Dan York <york@isoc.org>
Subject: Re: [Ietf-hub-boston] next IETF Boston community meeting

 

Miscommunication between Aaron and me, I take part of the blame.

 

From: Aaron Falk <aaron.falk@gmail.com <mailto:aaron.falk@gmail.com> >
Date: Thursday, April 26, 2018 at 11:02 AM
To: "akatlas@gmail.com <mailto:akatlas@gmail.com> " <akatlas@gmail.com <mailto:akatlas@gmail.com> >
Cc: Dan York <york@isoc.org <mailto:york@isoc.org> >, "ietf-hub-boston@ietf.org <mailto:ietf-hub-boston@ietf.org> " <ietf-hub-boston@ietf.org <mailto:ietf-hub-boston@ietf.org> >, Rich Salz <rsalz@akamai.com <mailto:rsalz@akamai.com> >
Subject: Re: [Ietf-hub-boston] next IETF Boston community meeting

 

Sorry, Gang. I mistakenly assumed we had a room reserved for May 8th at Akamai and the big meeting rooms aren’t available. We need to consider an alternative date or venue.

--aaron

On 5 Apr 2018, at 22:29, Alia Atlas wrote:

Given that our plan was to hold it on May 8 at Akamai  and 

that Rich can't host then, would it make more sense to move it

May 22 - when both Rich and I could make it?   (I can make May 8,

but not the week of May 15).  Holding it the same day will require

someone else to volunteer to host (or to try a pub with slightly more

preparation for projection.)

 

I've created a form for suggested dates ( <https://urldefense.proofpoint.com/v2/url?u=https-3A__goo.gl_forms_N0cbmzZKOL9pFneC3&d=DwMFaQ&c=96ZbZZcaMF4w0F4jpN6LZg&r=4LM0GbR0h9Fvx86FtsKI-w&m=1NFvM56FwU55yRn63Wq7CTDj3qNKe5mIiy16EwQlh4Q&s=r_V3I6T-iULjeYP84A1XqwG9ipeRRE3kmIuVQAgI6rw&e=> https://goo.gl/forms/N0cbmzZKOL9pFneC3 )

so that we don't have a lot of emails.  

 

I can summarize on Monday/Tues.

 

Thanks,

Alia

 

On Thu, Apr 5, 2018 at 10:07 PM, Dan York < <mailto:york@isoc.org> york@isoc.org> wrote:



> On Apr 5, 2018, at 4:38 PM, Alia Atlas < <mailto:akatlas@gmail.com> akatlas@gmail.com> wrote:
>
> The next IETF Boston community meeting is scheduled for May 8.
> Does that still work for folks?

I think so, but need to check on one more thing before I can 100% confirm.

> Do we folks interested in doing a talk?

If I can make it, I could do something short about creating Internet drafts using Markdown if that is of interest.

Dan

 

_______________________________________________
Ietf-hub-boston mailing list
 <mailto:Ietf-hub-boston@ietf.org> Ietf-hub-boston@ietf.org
 <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ietf.org_mailman_listinfo_ietf-2Dhub-2Dboston&d=DwMFaQ&c=96ZbZZcaMF4w0F4jpN6LZg&r=4LM0GbR0h9Fvx86FtsKI-w&m=1NFvM56FwU55yRn63Wq7CTDj3qNKe5mIiy16EwQlh4Q&s=wnzFL6UxbYCB5PvPYk9vlAyQHOqh7uKnJrjqrO3sJdI&e=> https://www.ietf.org/mailman/listinfo/ietf-hub-boston

v2.23.0 | Report a Bug | By Email