Re: [72attendees] Clarifying Host Responsibilities (was Re: Guestroom Network not under NOC Control)

"Rosen, Brian" <Brian.Rosen@neustar.biz> Tue, 29 July 2008 16:11 UTC

Return-Path: <72attendees-bounces@ietf.org>
X-Original-To: 72attendees-archive@ietf.org
Delivered-To: ietfarch-72attendees-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 79CE43A698B; Tue, 29 Jul 2008 09:11:58 -0700 (PDT)
X-Original-To: 72attendees@core3.amsl.com
Delivered-To: 72attendees@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AF4B43A698B for <72attendees@core3.amsl.com>; Tue, 29 Jul 2008 09:11:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EdkTqfbvFe+V for <72attendees@core3.amsl.com>; Tue, 29 Jul 2008 09:11:56 -0700 (PDT)
Received: from neustar.com (ns7.neustar.com [156.154.24.88]) by core3.amsl.com (Postfix) with ESMTP id 235C23A6927 for <72attendees@ietf.org>; Tue, 29 Jul 2008 09:11:56 -0700 (PDT)
DKIM-Signature: a=rsa-sha1; d=neustar.biz; s=neustarbiz; c=simple/simple; q=dns; t=1217347925; x=1217434325; h=From:Date:Subject:Message-ID:Content-class:Content-Type:Content-Transfer-Encod ing; b=Xfim8SJWffZ5fkTxZ1VpmqaVpoyvL67073hs6uB02joFCtwf1Bmoi5gfzD4JSe/rWRwuK/rf/b9hLx 7NEtIW5Q==
Received: from ([10.31.13.50]) by chihiron2.nc.neustar.com with ESMTP id 5202415.6844199; Tue, 29 Jul 2008 12:11:50 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 29 Jul 2008 12:11:46 -0400
Message-ID: <C80ADC57CB3BB64B94A9954A816306C549A61D@STNTEXCH11.cis.neustar.com>
In-Reply-To: <488F4098.1040106@dcrocker.net>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [72attendees] Clarifying Host Responsibilities (was Re: Guestroom Network not under NOC Control)
Thread-Index: AcjxlYCVroKw0TRsSkCS1/TdGeGEkgAADMfg
References: <C4B41B20.76FCE%jonne.soininen@nsn.com> <94A3C924-DB32-43B1-B9F5-66C54EA32926@muada.com><1217326884.3851.12.camel@victoria.pingtel.com> <488F4098.1040106@dcrocker.net>
From: "Rosen, Brian" <Brian.Rosen@neustar.biz>
To: <dcrocker@bbiw.net>
Cc: 72attendees@ietf.org
Subject: Re: [72attendees] Clarifying Host Responsibilities (was Re: Guestroom Network not under NOC Control)
X-BeenThere: 72attendees@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Discussion list for the attendees of IETF 72 meeting." <72attendees.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/72attendees>, <mailto:72attendees-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/72attendees>
List-Post: <mailto:72attendees@ietf.org>
List-Help: <mailto:72attendees-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/72attendees>, <mailto:72attendees-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: 72attendees-bounces@ietf.org
Errors-To: 72attendees-bounces@ietf.org

One word:  "Minneapolis"

> -----Original Message-----
> From: 72attendees-bounces@ietf.org
[mailto:72attendees-bounces@ietf.org]
> On Behalf Of Dave Crocker
> Sent: Tuesday, July 29, 2008 12:09 PM
> Cc: 72attendees@ietf.org
> Subject: Re: [72attendees] Clarifying Host Responsibilities (was Re:
> Guestroom Network not under NOC Control)
> 
> 
> 
> Dale Worley wrote:
> > It also doesn't help that this is a one-week event unlike any event
the
> > venue has ever had, or ever will have again.  There's not a lot of
time
> > for everyone to learn how to optimize all these trade-offs for this
> > particular audience,
> 
> 
> 
> This is key.
> 
> As long as our model has us usually going to places one time, there
can be
> no
> learning curve.
> 
> In spite of the considerable effort to get things right each time,
> actually
> achieving that will fail regularly.
> 
> The only way to get reliable performance of a meeting venue is to find
a
> few
> that we like and keep going back.
> 
> As long as we make the first priority be to find a host and let the
host
> choose
> a (new) venue, we will keep having venue problems.  We have 15+ years
of
> consistent history on this score.
> 
> d/
> 
> --
> 
>    Dave Crocker
>    Brandenburg InternetWorking
>    bbiw.net
> _______________________________________________
> 72attendees mailing list
> 72attendees@ietf.org
> https://www.ietf.org/mailman/listinfo/72attendees
_______________________________________________
72attendees mailing list
72attendees@ietf.org
https://www.ietf.org/mailman/listinfo/72attendees