Re: [106attendees] Power strips ?

Barry Leiba <barryleiba@computer.org> Fri, 22 November 2019 05:03 UTC

Return-Path: <barryleiba.mailing.lists@gmail.com>
X-Original-To: 106attendees@ietfa.amsl.com
Delivered-To: 106attendees@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 827821207FF for <106attendees@ietfa.amsl.com>; Thu, 21 Nov 2019 21:03:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.406
X-Spam-Level:
X-Spam-Status: No, score=-1.406 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.244, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
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 PGsBWwl7l7ma for <106attendees@ietfa.amsl.com>; Thu, 21 Nov 2019 21:03:55 -0800 (PST)
Received: from mail-oi1-f175.google.com (mail-oi1-f175.google.com [209.85.167.175]) (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 A7276120103 for <106attendees@ietf.org>; Thu, 21 Nov 2019 21:03:55 -0800 (PST)
Received: by mail-oi1-f175.google.com with SMTP id n16so5452176oig.2 for <106attendees@ietf.org>; Thu, 21 Nov 2019 21:03:55 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=5Krxa0PhQWidebSiofXNXw0I2ynjHNZJAbrBvH7TqHM=; b=WQZFxR3zo7ckyHun1GoX/3ItnFrpGRyfohi5rcYIVO4Vmc1mAnlv2EqWODxYO6E9zd veQDsA+dU7H3vJ8u0bLBJsvqFpJYTwffuRRvnAZ+/p8sovao+qRzb6AJdYwG3NFN012E GDnsbKmRPwcXs/hidOeVK7HtdnihaIK5egjICRnZIbyOLQyxk8k0q7u/Gudlo8uJ+uJS mCX0uSWjGiRCsA4fPq2OE6KLxMEbcDhhpkALnvgieqKlRtyAx341F7mfzaX/URJc0qQd D07mZU2g45L9H2t04Or2PbiYKzmBIceoU54TbtC+CGQcWKbVJM+DU6d65dvOmutU9T6g /1cA==
X-Gm-Message-State: APjAAAUNQDvwRgzM5gSjXQnkFdET+z0qjOKhtnIeLa63ImzFW0L4KL80 8t5y0LyHZ9LurgvYhY05s9h/Ldb3zxGEhKFPXGObug==
X-Google-Smtp-Source: APXvYqysjXh9+rXtHWdVhnOdjuKXjR/QhThzu22WS/zXUskqGBpDfLO2DAWqhyHgu/ow/Nc3guTmzOrW+OywYQXiVvs=
X-Received: by 2002:aca:ef04:: with SMTP id n4mr10974633oih.91.1574399034507; Thu, 21 Nov 2019 21:03:54 -0800 (PST)
MIME-Version: 1.0
References: <CALaySJLQn=2w4dn1-Ox3fYoxboJE81+dn5PGROVfHzmCd8at_Q@mail.gmail.com> <20191122040103.29CF4F78245@dhcp-8506.meeting.ietf.org> <CAHw9_iJiBuOKuGBovZLEadFbY4YMwCi_829i3X=yRNxpfi=f-g@mail.gmail.com>
In-Reply-To: <CAHw9_iJiBuOKuGBovZLEadFbY4YMwCi_829i3X=yRNxpfi=f-g@mail.gmail.com>
From: Barry Leiba <barryleiba@computer.org>
Date: Fri, 22 Nov 2019 13:03:54 +0800
Message-ID: <CAC4RtVDD6G4CYSKSt8qLaimxv-pnAvPtbzeVE_By_6sK7m9MXQ@mail.gmail.com>
To: 106attendees@ietf.org
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/106attendees/Iy4AFjjXBckvSpEJuTfKMSyq39E>
Subject: Re: [106attendees] Power strips ?
X-BeenThere: 106attendees@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Mailing list of all 106 attendees for official communication <106attendees.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/106attendees>, <mailto:106attendees-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/106attendees/>
List-Post: <mailto:106attendees@ietf.org>
List-Help: <mailto:106attendees-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/106attendees>, <mailto:106attendees-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Nov 2019 05:03:58 -0000

Just picking an arbitrary message to reply to (the most recent), so
read nothing into that choice...

There's not a lot of use in comparing our meetings or financial
situation to ICANN's, and I never meant to.  I simply noted that ICANN
does use its own power strips, so it's possible.  I intend to look
into the costs and other complexities, so we can then determine
whether -- or not -- it's practical and useful for the IETF to do
this.  Until we get more concrete information about those costs and
complexities, we really don't need to be guessing.

Let me see what I can find out, and we'll go from there.  Maybe it's a
fine idea for us.  Maybe it's not.  We'll see.

Barry

On Fri, Nov 22, 2019 at 12:56 PM Warren Kumari <warren@kumari.net> wrote:
>
> On Fri, Nov 22, 2019 at 12:01 PM John Levine <ietf@johnlevine.com> wrote:
> >
> > In article <CALaySJLQn=2w4dn1-Ox3fYoxboJE81+dn5PGROVfHzmCd8at_Q@mail.gmail.com> you write:
> > >As I noted, ICANN does it, and it works.  We could find out from them
> > >what sorts of costs and approvals are involved, but they don't seem to
> > >have problems with their not being allowed.
> >
> > ICANN apparently sends so much stuff to their meetings that it fills
> > several shipping containers.  We learned this several meetings ago
> > when one of the containers got lost.
>
> And by "lost" you mean "caught on fire!!!!" (actually, this wasn't the
> ICANN container which caught alight, but it was affected by nearby
> fire -- more info here:
> https://www.icann.org/news/blog/fire-on-cargo-ship-affects-it-equipment-bound-for-icann57-hyderabad
> ). It's easy to forget that a: networks rely on physical thingies, and
> b: logistics are hard and c: planning for all eventualities is also
> hard!
>
> If the same thing happened to the IETF network gear, we would be
> scrambling to deal -- ICANN could "simply" buy their way out of the
> issue, but the vast majority of IETF gear is donated, we don't have
> N+1 of everything, nor an easy way to put down a credit-card and say
> "another pile of your finest routers / switches / servers / wireless
> please, good sir..."
>
> W
>
> >  A quick look at the ICANN budget
> > suggests that even though they are roughly the same size as our meetings,
> > typically 1000 people, they cost twice as much.  (This is the cost.  Their
> > meeting revenue is deliberately zero so it's not comparable.)
> >
> > I'm pretty sure this is not a direction that the IETF would like to go.
> >
> > R's,
> > John
> >
> > --
> > 106attendees mailing list
> > 106attendees@ietf.org
> > https://www.ietf.org/mailman/listinfo/106attendees
>
>
>
> --
> I don't think the execution is relevant when it was obviously a bad
> idea in the first place.
> This is like putting rabid weasels in your pants, and later expressing
> regret at having chosen those particular rabid weasels and that pair
> of pants.
>    ---maf
>
> --
> 106attendees mailing list
> 106attendees@ietf.org
> https://www.ietf.org/mailman/listinfo/106attendees