Re: [Ieprep] on the ieprep charter

Fred Baker <fred@cisco.com> Wed, 12 July 2006 16:49 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1G0hts-0004oJ-IG; Wed, 12 Jul 2006 12:49:24 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1G0hts-0004oD-5e for ieprep@ietf.org; Wed, 12 Jul 2006 12:49:24 -0400
Received: from sj-iport-4.cisco.com ([171.68.10.86]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G0htq-0005sZ-RI for ieprep@ietf.org; Wed, 12 Jul 2006 12:49:24 -0400
Received: from sj-dkim-1.cisco.com ([171.71.179.21]) by sj-iport-4.cisco.com with ESMTP; 12 Jul 2006 09:49:18 -0700
X-IronPort-AV: i="4.06,236,1149490800"; d="scan'208"; a="1837798375:sNHT5856514734"
Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254]) by sj-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id k6CGnI4A001160; Wed, 12 Jul 2006 09:49:18 -0700
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com [171.70.151.144]) by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id k6CGnFoI029734; Wed, 12 Jul 2006 09:49:15 -0700 (PDT)
Received: from xfe-sjc-211.amer.cisco.com ([171.70.151.174]) by xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211); Wed, 12 Jul 2006 09:49:15 -0700
Received: from [132.219.16.127] ([10.21.88.156]) by xfe-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211); Wed, 12 Jul 2006 09:49:14 -0700
In-Reply-To: <44B4F17B.70105@jhuapl.edu>
References: <44B4F17B.70105@jhuapl.edu>
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <80703C4C-C585-4601-9518-270A3A6A49CC@cisco.com>
Content-Transfer-Encoding: 7bit
From: Fred Baker <fred@cisco.com>
Subject: Re: [Ieprep] on the ieprep charter
Date: Wed, 12 Jul 2006 12:49:07 -0400
To: "Robert G. Cole" <robert.cole@jhuapl.edu>
X-Mailer: Apple Mail (2.752.2)
X-OriginalArrivalTime: 12 Jul 2006 16:49:14.0724 (UTC) FILETIME=[1BA6DA40:01C6A5D3]
DKIM-Signature: a=rsa-sha1; q=dns; l=2555; t=1152722958; x=1153586958; c=relaxed/simple; s=sjdkim1001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=fred@cisco.com; z=From:Fred=20Baker=20<fred@cisco.com> |Subject:Re=3A=20[Ieprep]=20on=20the=20ieprep=20charter; X=v=3Dcisco.com=3B=20h=3DhF46nYRTNqWFkPqT/8l/+JDUBL8=3D; b=A0SsFnkQvEoMfBsSbPiMo/3sya6Cuoy4yFlg14eDOseB6+yu8qcOpkga/FPUYPj72QPWmrDP WDvzFYRRteIzZzMlvNUoB6lX2Ar2SgEe/3F4xYyk4hCkE4SfSgEfNM9A;
Authentication-Results: sj-dkim-1.cisco.com; header.From=fred@cisco.com; dkim=pass ( sig from cisco.com verified; );
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 21c69d3cfc2dd19218717dbe1d974352
Cc: ieprep@ietf.org
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

On Jul 12, 2006, at 8:56 AM, Robert G. Cole wrote:
> + I agree with expanding the scope of the WG away from solely an  
> emergency Telecomm focus to a more general emergency communications  
> focus.  I do not think a totally military focus is correct however;  
> this is only one of several sectors the IETF needs to address.   
> There is significant overlap in the needs for emergency services  
> within Enterprise, Public and Military networks, that to focus on a  
> single sector would represent a disservice to all of these  
> communities.

yes.

My observation here is that in the PSTN there is a single common set  
of tools used, the information elements in SS7. The implementation of  
these vary: some networks use preemption (my observation is that most  
networks I have spoken with use preemption), and some use other  
techniques like call queuing, trunk queuing, and alternative call  
routing. That argues that it is not necessary and is perhaps  
inappropriate to attempt to mandate that a difference in underlying  
implementation forces a difference in protocol.

I would go a step further. At the end of the day, carriers and  
vendors are being asked to implement one thing or another, with  
enough options to cover the needs of their various countries. In the  
PSTN, this was done in an international body, the SS7 protocols are  
used world-wide, and basically those two options are used in common  
implementation throughout the world. This vendor sells not only to US  
DoD and US DHS/NCS and their contractors. Cisco sells to many service  
providers that offer service in multiple countries; one of such told  
me that their services were offered in 70 countries. Cisco also sells  
to NATO, which in the final analysis means that it provides tools to  
military networks i roughly 90 countries. Asking for this DHS/NSC vs  
DoD division is a microcosm of the reality that this working group  
needs to address.

In my humble opinion, which is of course always right (but I am too  
humble to say so), what we really need is a single common solution  
that can be interoperably deployed in preemption-ok and preemption- 
not-ok networks in a wide variety of countries, with configuration  
options to deal with the differences in implementation approach. If  
that is in the end not the objective, then I believe the working  
group should not be chartered. This ultimately hurts everyone, and is  
not my desire, but is the only thing that would make sense in the  
context.

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