[104all] IETF 104 Network Information

Jim Martin <jim@daedelus.com> Sat, 23 March 2019 10:14 UTC

Return-Path: <jim@daedelus.com>
X-Original-To: 104all@ietfa.amsl.com
Delivered-To: 104all@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A5D3A1293B1 for <104all@ietfa.amsl.com>; Sat, 23 Mar 2019 03:14:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=daedelus-com.20150623.gappssmtp.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 o1e581dElYD4 for <104all@ietfa.amsl.com>; Sat, 23 Mar 2019 03:14:15 -0700 (PDT)
Received: from mail-pg1-x52b.google.com (mail-pg1-x52b.google.com [IPv6:2607:f8b0:4864:20::52b]) (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 E7CE412D84C for <104all@ietf.org>; Sat, 23 Mar 2019 03:14:14 -0700 (PDT)
Received: by mail-pg1-x52b.google.com with SMTP id h8so3182162pgp.6 for <104all@ietf.org>; Sat, 23 Mar 2019 03:14:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=daedelus-com.20150623.gappssmtp.com; s=20150623; h=from:mime-version:subject:message-id:date:to; bh=uT9o+/t7TwiI/fMp7fmVcunNwnmXVuUFxiFGw3/OSt8=; b=l/LcoOnykhAFImF7BFH4BeTpy/J+zAkI+cBuPT8PjWHmMFJbeQ2Tpkdbk5zCAt44J7 eb874hSoSdPavMUY9ErK0Qmfw2X99bTCd18WXg8FLuS2muaYAOGqt0R+4K1QXn0YFaSv tSOJJlqPR1mFQnKfKO8MOJQ/+eRtDhbdXlWO2cwMi2vN7a+YHmeAsQl12qnY1eLGewgY ayYOIDI0llb5BiPfOx9+U+KBBXPv0JUdQRsntocG3SBTeUxociX3OjzO5jXsLU3piX/Z HDZ0gRpvKdlIMHTvVth6nvxpryZ2KYqM4aQLgniYYObU0P7ZQGeSpNnKRuIPWy9hOmGS 1r6g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:mime-version:subject:message-id:date:to; bh=uT9o+/t7TwiI/fMp7fmVcunNwnmXVuUFxiFGw3/OSt8=; b=P2bwHgeUBiGEQ292eJZv3bj24ZQ5yzg3t/pjJfLOtFCXC0G01o2Cj6IP0jnkeXP5oU OAYo2HsMGgYwEIKKi+cXtLZs2Mkj8JDf5YkhYyGRfo7A0rdc7V6n5UNyP/n6WA4M6mlv nngILxRRi9/RLWqrscVA/oZ6ndd04icdr8AgcGisq0Bb4ufOVEfJpIOlrlPQcqo7AwRF +4mOXBM+63ar1yRtuLcuWnD5xD4/yrmB4SR5nrhZexa8RDhQj1B8oCLVLU9Vi9YPcwvi GGrmTIcVX/irDnS1FrZFCHrJ2vBkwi38i4nbS9gHA5iUswVjSLxYLGNspXE1r+/pG4qt j6yg==
X-Gm-Message-State: APjAAAXBCGWdbeVrLLjR6N+w97XhyhDFQXgjJl+SbBV+DJH/OdOKRe0c Aj6TqVOeNA3SQCKDZsUV84gUp1MZ0dnaSQ==
X-Google-Smtp-Source: APXvYqxweuHKKhjad+YMB5MCbwYUbmG6jliYCcQs2aWBDgQ9wo4WGH5nZZlXwcNu8U1ko+TInQPcmg==
X-Received: by 2002:a17:902:1121:: with SMTP id d30mr14445370pla.104.1553336053859; Sat, 23 Mar 2019 03:14:13 -0700 (PDT)
Received: from ?IPv6:2001:4f8:fffa:192:8000::43? ([2001:4f8:fffa:192:8000::43]) by smtp.gmail.com with ESMTPSA id b85sm16081498pfj.56.2019.03.23.03.14.11 for <104all@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 23 Mar 2019 03:14:13 -0700 (PDT)
From: Jim Martin <jim@daedelus.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_B1F79EE1-7716-4E8D-B72D-5C722FAC155A"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.8\))
Message-Id: <824DBAA9-701B-4D4A-9FDB-8B583239561C@daedelus.com>
Date: Sat, 23 Mar 2019 11:14:08 +0100
To: 104all@ietf.org
X-Mailer: Apple Mail (2.3445.104.8)
Archived-At: <https://mailarchive.ietf.org/arch/msg/104all/cVLPwZ6l_6-L6dkcmon-9AsZX60>
Subject: [104all] IETF 104 Network Information
X-BeenThere: 104all@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Official Communication about IETF 104 <104all.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/104all>, <mailto:104all-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/104all/>
List-Post: <mailto:104all@ietf.org>
List-Help: <mailto:104all-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/104all>, <mailto:104all-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 23 Mar 2019 10:14:18 -0000

Gentlepeople,
	Welcome back to Prague! As we did in Bangkok, we’re attempting to reduce complexity, so we’re emailing this streamlined version of the Network Information document. For full details, please see the full document at https://tickets.meeting.ietf.org/wiki/IETF104network

What’s New
---------------
	The Network Help Desk and “Terminal Room Printer” have moved to the registration area to make support and printing more accessible to everyone. 

	The hotel’s wireless contractor has kindly provided the IETF NOC with significant control of their network. As we’ve done previously in the Concord in Paris, the NOC team has reconfigured the power levels, channels, and other parameters to improve the guest room wireless experience. If you do find areas that are problematic, please let us know, as we now have far more ability to make changes to improve your experience!

	Many thanks to Juniper for the donation of new MX204 Routers for the NOC! Sadly, they just missed the shipping cutoff for this meeting, but they’ll be used starting in Montreal. These new routers will handle faster links, new features like streaming telemetry, and perhaps most importantly improve failure recover times.

IETF Wireless
-------------------
	In the lobby, public spaces, and guest rooms of the Hilton Prague, please use the open “ietf-hotel” wireless network. 

	In the meeting areas, we encourage you to use the secure “ietf” network, with a username of “ietf” and a password of “ietf”. If you aren’t able to use the secure network, the “ietf-legacy104” network is available with no security.

Getting Help
-----------------
	To get help in person, the help desk is available in the registration area in the Lower Level in the Conference Hall Foyer, starting at 4pm on Sunday, and then daily starting at 8am until 6pm. 

	To submit or view network trouble tickets via the web interface please see https://tickets.meeting.ietf.org <https://tickets.meeting.ietf.org/>;. To submit a ticket via email, please send to tickets@meeting.ietf.org <mailto:tickets@meeting.ietf.org>. 

	Thank to our many sponsors and volunteers that make the network happen!

	We hope you have a great meeting and enjoy Prague!

	
	-Jim & the IETF NOC Team