Re: [Ieprep] on the ieprep charter

"Howard C. Berkowitz" <hcb@layer3arts.com> Thu, 27 July 2006 19:54 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1G6Bwf-0003xA-Mc; Thu, 27 Jul 2006 15:54:57 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1G6Bwe-0003x0-8P for ieprep@ietf.org; Thu, 27 Jul 2006 15:54:56 -0400
Received: from mail.manske.org ([65.127.251.7]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G6Bwc-0002aA-Sm for ieprep@ietf.org; Thu, 27 Jul 2006 15:54:56 -0400
Received: from mail.manske.org (localhost.manske.org [127.0.0.1]) by mail.manske.org (8.13.6/8.13.4) with ESMTP id k6RJskWD059064 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ieprep@ietf.org>; Thu, 27 Jul 2006 14:54:46 -0500 (CDT) (envelope-from hcb@layer3arts.com)
Received: (from nobody@localhost) by mail.manske.org (8.13.6/8.13.4/Submit) id k6RJsk9p059063 for ieprep@ietf.org; Thu, 27 Jul 2006 14:54:46 -0500 (CDT) (envelope-from hcb@layer3arts.com)
X-Authentication-Warning: mail.manske.org: nobody set sender to hcb@layer3arts.com using -f
Received: from 24-182-173-239.dhcp.stls.mo.charter.com (24-182-173-239.dhcp.stls.mo.charter.com [24.182.173.239]) by webmail.layer3arts.com (IMP) with HTTP for <howard@localhost>; Thu, 27 Jul 2006 14:54:46 -0500
Message-ID: <1154030086.44c91a06e60f0@webmail.layer3arts.com>
Date: Thu, 27 Jul 2006 14:54:46 -0500
From: "Howard C. Berkowitz" <hcb@layer3arts.com>
To: ieprep@ietf.org
Subject: Re: [Ieprep] on the ieprep charter
References: <44B4F17B.70105@jhuapl.edu> <80703C4C-C585-4601-9518-270A3A6A49CC@cisco.com> <44C9089E.3050802@jhuapl.edu> <B8C892A4-F711-4928-8EDA-FD7E717B702F@cisco.com>
In-Reply-To: <B8C892A4-F711-4928-8EDA-FD7E717B702F@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
User-Agent: Internet Messaging Program (IMP) 3.2.1
X-Originating-IP: 24.182.173.239
X-manske.org-MailScanner-Information: Please contact the ISP for more information
X-manske.org-MailScanner: Found to be clean
X-manske.org-MailScanner-From: hcb@layer3arts.com
X-Spam-Status: No
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>, <mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>, <mailto:ieprep-request@ietf.org?subject=subscribe>
Errors-To: ieprep-bounces@ietf.org

Quoting Fred Baker <fred@cisco.com>om>:


> Note that I carefully separated that into three broad categories:  
> UNI, NNI, and everything else. "everything else" is within a network,  
> and I think that is the network's problem although I may have some  
> suggestions. NNI may be able to be handled by SLAs, although one  
> could argue that the entire discussion here is regarding edge  
> conditions in SLAs. It is the UNI that concerns me the most, as it  
> tends to be the place where the biggest problems occur, and where  
> problems occur at NNIs they can be treated as a variety of aggregated  
> UNI. It is the NNI and the UNI that are most in view in RFC 4542.

As a newbie to the list, but not necessarily emergency operations, there may be
additional cases. In a large disaster, it may well be that telecommunications
operating facilities may be the only available buildings with adequate backup
power, HVAC, and physical ruggedness to stay in service. I've encountered some
very ad hoc situation where emergency responders, PSAPs, etc., temporarily
operated out of telco COs and the like. 

It's not inconceivable, in such a circumstance, that such people may bring
equipment meant for UNI, in a facility with mostly NNI and other interfaces. I'd
encourage thinking about that sort of ad hoc operational requirement. 

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep