Re: IPv4 outage at next IETF in Chicago

John C Klensin <john-ietf@jck.com> Thu, 26 January 2017 19:19 UTC

Return-Path: <john-ietf@jck.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 F0CFD1299A2 for <ietf@ietfa.amsl.com>; Thu, 26 Jan 2017 11:19:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.098
X-Spam-Level:
X-Spam-Status: No, score=-5.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-3.199, URIBL_BLOCKED=0.001] autolearn=ham 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 ykw4ILcAc39t for <ietf@ietfa.amsl.com>; Thu, 26 Jan 2017 11:19:33 -0800 (PST)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D2BAF12999F for <ietf@ietf.org>; Thu, 26 Jan 2017 11:19:33 -0800 (PST)
Received: from [198.252.137.70] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1cWpa0-000JWm-Su; Thu, 26 Jan 2017 14:19:32 -0500
Date: Thu, 26 Jan 2017 14:19:27 -0500
From: John C Klensin <john-ietf@jck.com>
To: Randy Bush <randy@psg.com>
Subject: Re: IPv4 outage at next IETF in Chicago
Message-ID: <06B2D816A120B2DB2867387A@PSB>
In-Reply-To: <m260l1iqgi.wl-randy@psg.com>
References: <844840869.114000858.1485299485194.JavaMail.zimbra@peachymango.org> <20170124235626.042F960836B0@rock.dv.isc.org> <158901d276b3$387d6050$a97820f0$@huitema.net> <CAAiTEH_4WgdmMZQm5nbFbvweibkZ0DAo2feN91zftspD4EbWjg@mail.gmail.com> <m260l1iqgi.wl-randy@psg.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.70
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/vDib__OXcDCA6pPvoe0_v4EP9Dk>
Cc: IETF Rinse Repeat <ietf@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, 26 Jan 2017 19:19:35 -0000

Noted and agreed.
   john


--On Thursday, January 26, 2017 11:14 -0800 Randy Bush
<randy@psg.com> wrote:

>> This strongly suggests that it would be a good idea for the
>> NOC to have a web-based reporting form that specifically asks
>> for (or, when possible, automagically fills in) whatever
>> information is needed to cause a ticket to make sense and be
>> useful.
> 
> will leave as exercise for student finding the network
> announcement from a recent meeting and following it to the
> existing ticketing system before micro-managing it.