Re: Remote Hubs

Pat Thaler <pat.thaler@broadcom.com> Thu, 10 March 2016 01:32 UTC

Return-Path: <pat.thaler@broadcom.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1006012DCC7 for <ietf@ietfa.amsl.com>; Wed, 9 Mar 2016 17:32:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 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, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=broadcom.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 D4ePMknlMvrg for <ietf@ietfa.amsl.com>; Wed, 9 Mar 2016 17:32:41 -0800 (PST)
Received: from mail-io0-x22d.google.com (mail-io0-x22d.google.com [IPv6:2607:f8b0:4001:c06::22d]) (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 A7A9F12DCD4 for <ietf@ietf.org>; Wed, 9 Mar 2016 17:32:40 -0800 (PST)
Received: by mail-io0-x22d.google.com with SMTP id n190so88845630iof.0 for <ietf@ietf.org>; Wed, 09 Mar 2016 17:32:40 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=broadcom.com; s=google; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=/6EpZHO3Dw6Yidc2gdljvavKM3KBI3UdMP05JUef8u8=; b=av3IDCKVX4DTxlAmY3nTEzFrtCgo261Sf5LX5TuisPzp8S5tJlEOAQbSCW1cMPViFV YyQiHdjYpjDmjlli59IAZwEBnC7cB9jKoObeyL7rlPW4brps+Zv6FnIz3kmun9KhV/PY n8NyFn0VXsp4GmYq2RKknNuLhlm8yEWEyj9gc=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=/6EpZHO3Dw6Yidc2gdljvavKM3KBI3UdMP05JUef8u8=; b=k8vUpFiVSgAAO0K4GT7J7mUIJXKu0Ax2YQ49l+QvhgHYdczKTqobBh9JShQ6QGstWD lQfG5jo4a9jY30Cjd6SqKq+gMeVA+G8k2nJmSe+GrIYdI19Hyu1EhfBIa6Dh48PV5nTo xeRjVnSgL2kdKfT16mIyAfzPAjgs2m6k79eg3xbf69Pirb6aPxM/TsTxxoK8UxZNbtTi 2vrqc4TnXTwHMA9b7s7J2I72fgDgFwmMFzgE3d+QSV43s86NMHTTuyvsxKAKO5oH5k6k MBOsJf0jaTcywPuejDthALQ4oMwq7F0brIIs15GAOhr7YpXifoKmd/KZaHkKcuspS95M BqIw==
X-Gm-Message-State: AD7BkJLKRFfPXZbMEUBFN+zKqMrUrUJARA7seeohp/CH+FFPhF8pVHCrGlcjTU3PozkvyOm8c6v5XeWqx5fsmW90
MIME-Version: 1.0
X-Received: by 10.107.28.134 with SMTP id c128mr801090ioc.86.1457573559735; Wed, 09 Mar 2016 17:32:39 -0800 (PST)
Received: by 10.36.130.1 with HTTP; Wed, 9 Mar 2016 17:32:39 -0800 (PST)
In-Reply-To: <1022465394.3606828.1457568222041.JavaMail.yahoo@mail.yahoo.com>
References: <1022465394.3606828.1457568222041.JavaMail.yahoo.ref@mail.yahoo.com> <1022465394.3606828.1457568222041.JavaMail.yahoo@mail.yahoo.com>
Date: Wed, 9 Mar 2016 17:32:39 -0800
Message-ID: <CAJt_5EigsZGsRtoHGt__cCtk=mvZkKGF38D9JEAmHKspfEttBg@mail.gmail.com>
Subject: Re: Remote Hubs
From: Pat Thaler <pat.thaler@broadcom.com>
To: Nalini Elkins <nalini.elkins@insidethestack.com>
Content-Type: multipart/alternative; boundary=001a113ff30c43c9cb052da7cac3
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/1IGeZW5SjqYYXW5ZnXXPszKm5h0>
Cc: IETF Discussion List <ietf@ietf.org>, "vmeet@ietf.org" <vmeet@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 Mar 2016 01:32:43 -0000

There isn't a reason for singling out Asia in: 2.5
6. Scheduling across time zones could be an issue, especially if time zone
of meeting is Asia. Can remote hubs use recordings and watch together to
address time zone differences.

No matter which 3rd of the world the meeting is in, part of the meeting day
overlaps the Midnight to 6 AM hours in one of the other 2.
http://www.timeanddate.com/worldclock/meetingtime.html?month=3&day=16&year=2016&p1=900&p2=43&p3=136&p4=33&iv=0

Watching a recording instead of being on line real time removes the ability
to interact and give input to the meeting. That works for some goals of
attending (e.g. observing the work or keeping up with what is going on when
one can't attend in person).

On Wed, Mar 9, 2016 at 4:03 PM, <nalini.elkins@insidethestack.com> wrote:

> All,
>
> We have written a summary of the current thinking on Remote IETF hubs as
> well as what has been done in Latin America.  There is also quite a bit of
> activity in India with remote hubs.
> They will be posting a draft soon.
>
> We wrote these to serve as community memory and to serve as a starting
> point for discussion.  As our knowledge of how to do remote hubs increases,
> we will update the drafts.
>
> Please view:
>
> https://datatracker.ietf.org/doc/draft-elkins-ietf-remote-hubs/
>
> and
>
> https://datatracker.ietf.org/doc/draft-oflaherty-ietf-remote-hubs-lac/
>
>
> Please let us know any comments or suggestions.
>
> Thanks,
>
> Nalini Elkins
> Inside Products, Inc.
> www.insidethestack.com
> (831) 659-8360
>
>