Re: [earlywarning] Finishing the Charter Text Discussions

"DALY, BRIAN K (ATTCINW)" <BD2985@att.com> Wed, 07 April 2010 20:22 UTC

Return-Path: <BD2985@att.com>
X-Original-To: earlywarning@core3.amsl.com
Delivered-To: earlywarning@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9691228C10B for <earlywarning@core3.amsl.com>; Wed, 7 Apr 2010 13:22:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level:
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 q54F7eeHWRkQ for <earlywarning@core3.amsl.com>; Wed, 7 Apr 2010 13:22:46 -0700 (PDT)
Received: from mail161.messagelabs.com (mail161.messagelabs.com [216.82.253.115]) by core3.amsl.com (Postfix) with ESMTP id 9924F28C13B for <earlywarning@ietf.org>; Wed, 7 Apr 2010 13:22:12 -0700 (PDT)
X-VirusChecked: Checked
X-Env-Sender: BD2985@att.com
X-Msg-Ref: server-3.tower-161.messagelabs.com!1270671727!26506086!1
X-StarScan-Version: 6.2.4; banners=-,-,-
X-Originating-IP: [144.160.112.25]
Received: (qmail 24003 invoked from network); 7 Apr 2010 20:22:08 -0000
Received: from sbcsmtp3.sbc.com (HELO tlph064.enaf.dadc.sbc.com) (144.160.112.25) by server-3.tower-161.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 7 Apr 2010 20:22:08 -0000
Received: from enaf.dadc.sbc.com (localhost.localdomain [127.0.0.1]) by tlph064.enaf.dadc.sbc.com (8.14.3/8.14.3) with ESMTP id o37KM6Jt011585; Wed, 7 Apr 2010 15:22:06 -0500
Received: from td03xsmtp008.US.Cingular.Net (intexchapp01.us.cingular.net [135.179.64.42] (may be forged)) by tlph064.enaf.dadc.sbc.com (8.14.3/8.14.3) with ESMTP id o37KM05E011466; Wed, 7 Apr 2010 15:22:00 -0500
Received: from BD01XSMTP003.US.Cingular.Net ([135.163.18.44]) by td03xsmtp008.US.Cingular.Net with Microsoft SMTPSVC(6.0.3790.3959); Wed, 7 Apr 2010 15:22:00 -0500
Received: from BD01MSXMB016.US.Cingular.Net ([135.214.27.50]) by BD01XSMTP003.US.Cingular.Net with Microsoft SMTPSVC(6.0.3790.3959); Wed, 7 Apr 2010 13:21:58 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 7 Apr 2010 13:21:56 -0700
Message-ID: <FDFC6E6B2064844FBEB9045DF1E3FBBC4F8160@BD01MSXMB016.US.Cingular.Net>
In-Reply-To: <C7E260A8.2C983%br@brianrosen.net>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [earlywarning] Finishing the Charter Text Discussions
thread-index: AcrWi0usG9/KhYhZR3OiTWO1oA9w7wAAJi8QAADfTYsAAAkRwA==
References: <FDFC6E6B2064844FBEB9045DF1E3FBBC4F8124@BD01MSXMB016.US.Cingular.Net> <C7E260A8.2C983%br@brianrosen.net>
From: "DALY, BRIAN K (ATTCINW)" <BD2985@att.com>
To: "Brian Rosen" <br@brianrosen.net>, "ken carlberg" <carlberg@g11.org.uk>, "SENNETT, DEWAYNE A (ATTCINW)" <DS2225@att.com>
X-OriginalArrivalTime: 07 Apr 2010 20:21:58.0029 (UTC) FILETIME=[F90963D0:01CAD68F]
Cc: Hannes Tschofenig <Hannes.Tschofenig@gmx.net>, earlywarning@ietf.org
Subject: Re: [earlywarning] Finishing the Charter Text Discussions
X-BeenThere: earlywarning@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Discussion list for Authority-to-Individuals \(Early Warning\) Emergency " <earlywarning.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/earlywarning>, <mailto:earlywarning-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/earlywarning>
List-Post: <mailto:earlywarning@ietf.org>
List-Help: <mailto:earlywarning-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/earlywarning>, <mailto:earlywarning-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Apr 2010 20:22:47 -0000

We are just stating that ATOCA contradicts the CMAS (& EAS) rules, as
well as iPAWS and DMOpen architectures, and thus is in a different
class. Thus we believe we do need to be up front in the charter and nto
to confuse the industry.

Brian

-----Original Message-----
From: Brian Rosen [mailto:br@brianrosen.net] 
Sent: Wednesday, April 07, 2010 1:18 PM
To: DALY, BRIAN K (ATTCINW); ken carlberg; SENNETT, DEWAYNE A (ATTCINW)
Cc: Hannes Tschofenig; earlywarning@ietf.org
Subject: Re: [earlywarning] Finishing the Charter Text Discussions

In what way would any RFC not have to meet that requirement?

I understand that you are concerned that this work overlaps layer 2
specific
solutions.  However, there is no need to explicitly put this work in
second
class.  It's not going to affect any words in a protocol specification.
If
there is a regulatory requirement that makes ATOCA compliant
implementations, like any other service, subservient in some way to some
other service, so be it.  The charter, and the spec, don't need to say
that;
it's always true.

Brian




On 4/7/10 3:56 PM, "DALY, BRIAN K (ATTCINW)" <BD2985@att.com> wrote:

> The second is more than a market decision - it is an interaction with
a
> regulatory requirement.
> 
> Perhaps a better way to phrase is as follows:
> 
> "Additionally, ATOCA will not interfere with nor replace solutions
> designed to meet regulatory requirements for any authority to citizen
> alerting of any access technology."
> 
> Brian Daly
> AT&T
> 
> -----Original Message-----
> From: earlywarning-bounces@ietf.org
> [mailto:earlywarning-bounces@ietf.org] On Behalf Of ken carlberg
> Sent: Wednesday, April 07, 2010 12:48 PM
> To: SENNETT, DEWAYNE A (ATTCINW)
> Cc: Hannes Tschofenig; earlywarning@ietf.org
> Subject: Re: [earlywarning] Finishing the Charter Text Discussions
> 
> 
> On Apr 7, 2010, at 11:30 AM, SENNETT, DEWAYNE A (ATTCINW) wrote:
> 
>> "The ATOCA solutions will not adversely affect the ability of any
> access
>> technology to provide emergency services to the citizens (e.g. 9-1-1
>> calls) or to provide communication services to first responders or
> other
>> authorized emergency services personnel.  Additionally, ATOCA is not
>> replacement solution for any authority to citizen alerting supported
> by
>> any access technology."
> 
> given the previous thread on this list, I'm a bit leery of that first
> sentence.  But, if it were agreed to add it in, then I would expect
the
> individuals who make a claim that an ATOCA solution adversely affects
> 9-1-1 type calls will be required to prove it instead of simply
stating
> a position.
> 
> as for the second sentence, that is out of scope of the IETF.  any
> deployment of what is considered an ATOCA solution is a market
decision.
> 
> -ken
> 
> _______________________________________________
> earlywarning mailing list
> earlywarning@ietf.org
> https://www.ietf.org/mailman/listinfo/earlywarning
> _______________________________________________
> earlywarning mailing list
> earlywarning@ietf.org
> https://www.ietf.org/mailman/listinfo/earlywarning