RE: [Sipping-emergency] RE: Civil location syntax validation - wa s RE: How to handle Validation failures

"Marc Linsner" <mlinsner@cisco.com> Wed, 29 September 2004 13:57 UTC

Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA04955 for <sipping-emergency-web-archive@ietf.org>; Wed, 29 Sep 2004 09:57:33 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CCf5d-0007Dp-Ne for sipping-emergency-web-archive@ietf.org; Wed, 29 Sep 2004 10:05:55 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CCekV-0003lW-D9; Wed, 29 Sep 2004 09:44:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CCeY7-00012R-JI for sipping-emergency@megatron.ietf.org; Wed, 29 Sep 2004 09:31:15 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA02351 for <sipping-emergency@ietf.org>; Wed, 29 Sep 2004 09:31:13 -0400 (EDT)
Received: from sj-iport-3-in.cisco.com ([171.71.176.72] helo=sj-iport-3.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CCeg9-0006WK-7Q for sipping-emergency@ietf.org; Wed, 29 Sep 2004 09:39:34 -0400
Received: from sj-core-2.cisco.com (171.71.177.254) by sj-iport-3.cisco.com with ESMTP; 29 Sep 2004 06:44:13 +0000
X-BrightmailFiltered: true
Received: from malone.cisco.com (malone.cisco.com [171.70.157.157]) by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id i8TDUdwp016614; Wed, 29 Sep 2004 06:30:39 -0700 (PDT)
Received: from mlinsnerzk7abh (ssh-sjc-1.cisco.com [171.68.225.134]) by malone.cisco.com (8.8.6 (PHNE_14041)/CISCO.SERVER.1.2) with ESMTP id GAA11480; Wed, 29 Sep 2004 06:30:38 -0700 (PDT)
From: Marc Linsner <mlinsner@cisco.com>
To: 'Jonathan Rosenberg' <jdrosen@dynamicsoft.com>, "'Peterson, Jon'" <jon.peterson@neustar.biz>
Subject: RE: [Sipping-emergency] RE: Civil location syntax validation - wa s RE: How to handle Validation failures
Date: Wed, 29 Sep 2004 09:30:40 -0400
Message-ID: <000201c4a628$83fb6590$8501a8c0@mlinsnerzk7abh>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4510
Importance: Normal
In-Reply-To: <415A262C.60904@dynamicsoft.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
X-Spam-Score: 1.1 (+)
X-Scan-Signature: 82c9bddb247d9ba4471160a9a865a5f3
Content-Transfer-Encoding: 7bit
Cc: sipping-emergency@ietf.org
X-BeenThere: sipping-emergency@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: sipping-emergency.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping-emergency>, <mailto:sipping-emergency-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping-emergency@ietf.org>
List-Help: <mailto:sipping-emergency-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping-emergency>, <mailto:sipping-emergency-request@ietf.org?subject=subscribe>
Sender: sipping-emergency-bounces@ietf.org
Errors-To: sipping-emergency-bounces@ietf.org
X-Spam-Score: 1.1 (+)
X-Scan-Signature: 02ec665d00de228c50c93ed6b5e4fc1a
Content-Transfer-Encoding: 7bit

Jonathan,

In-line.....

> 
> Peterson, Jon wrote:
> 
> > So, just to make sure I understand, validation uses the
> same network
> > operation, basically, that would be used for a route query?
> > 
> > Agreed that it should be possible for a route query to return 'I
> > didn't understand your address format', 'I understand your 
> address and
> > it isn't actually valid', and so on beyond just the
> sunny-day case of
> > returning the route. Also, plus or minus some authorization and
> > operational issues, I agree that an ordinary user should be able to 
> > launch this sort of query outside the context of an emergency call.
> 
> I'm not so sure of that.
> 
> It seems that there is a lot of very useful information in
> this database 
> - which addresses exist, which do not, and information on the 
> relative 
> proximity of civil addresses to each other (two addresses that map to 
> the same ERC would be "close" in some way). As a result, I feel that 
> there are probably privacy implications of allowing worldwide open 
> access to this database. Seems like it would be mined by spammers to 
> validate mailing addresses, and used for all sorts of other nefarious 
> purposes.
> 
> Along those lines, I think it might be a good idea to
> sprinkle some nice 
> words into the charter about taking into consideration 
> privacy concerns, 
> and properly balancing them with the needs of emergency call routing.
> 
> -Jonathan R.
> 

If you don't open up the ability to view the civil address routing
information, including the ability to 'mine' the address information, the
alternative would be to create a for-fee service to gain access to this
public information.  I suggest you look at and play with:

http://zip4.usps.com/zip4/welcome.jsp

In your example, spammers would love this site.

Street addresses are already public information that is freely available.

-Marc Linsner-



_______________________________________________
Sipping-emergency mailing list
Sipping-emergency@ietf.org
https://www1.ietf.org/mailman/listinfo/sipping-emergency