[Ecrit] review of draft-marshall-ecrit-similar-location-03

"Bradner, Scott" <sob@harvard.edu> Wed, 26 March 2014 01:00 UTC

Return-Path: <sob@harvard.edu>
X-Original-To: ecrit@ietfa.amsl.com
Delivered-To: ecrit@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F05401A027B for <ecrit@ietfa.amsl.com>; Tue, 25 Mar 2014 18:00:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.301
X-Spam-Level:
X-Spam-Status: No, score=-1.301 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_22=0.6, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001] autolearn=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 rwleE5JgdKKl for <ecrit@ietfa.amsl.com>; Tue, 25 Mar 2014 18:00:28 -0700 (PDT)
Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn14138.inbound.protection.outlook.com [207.46.163.138]) by ietfa.amsl.com (Postfix) with ESMTP id 849A71A027A for <ecrit@ietf.org>; Tue, 25 Mar 2014 18:00:27 -0700 (PDT)
Received: from BY2PR07MB599.namprd07.prod.outlook.com (10.141.222.19) by BY2PR07MB599.namprd07.prod.outlook.com (10.141.222.19) with Microsoft SMTP Server (TLS) id 15.0.898.11; Wed, 26 Mar 2014 01:00:24 +0000
Received: from BY2PR07MB599.namprd07.prod.outlook.com ([10.141.222.19]) by BY2PR07MB599.namprd07.prod.outlook.com ([10.141.222.19]) with mapi id 15.00.0898.005; Wed, 26 Mar 2014 01:00:24 +0000
From: "Bradner, Scott" <sob@harvard.edu>
To: "ecrit@ietf.org" <ecrit@ietf.org>
Thread-Topic: review of draft-marshall-ecrit-similar-location-03
Thread-Index: AQHPSI7ErtejmZkPIkOts419lHvLcQ==
Date: Wed, 26 Mar 2014 01:00:24 +0000
Message-ID: <48A82192-DF6E-43D5-B35F-8D68515ED067@harvard.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [2001:4830:142:0:3056:dab4:a718:9ab0]
x-forefront-prvs: 0162ACCC24
x-forefront-antispam-report: SFV:NSPM; SFS:(10019001)(6009001)(428001)(199002)(189002)(81342001)(56816005)(74366001)(92566001)(74876001)(69226001)(90146001)(97186001)(97336001)(20776003)(63696002)(49866001)(92726001)(79102001)(77982001)(75432001)(80976001)(81686001)(81816001)(85852003)(47976001)(50986001)(59766001)(4396001)(47736001)(33656001)(83322001)(56776001)(76482001)(98676001)(46102001)(53806001)(51856001)(82746002)(76176001)(36756003)(2656002)(87936001)(86362001)(47446002)(74502001)(74662001)(81542001)(31966008)(80022001)(74706001)(76796001)(93136001)(94946001)(54356001)(83072002)(85306002)(87266001)(54316002)(95666003)(94316002)(83716003)(93516002)(95416001)(76786001)(65816001)(3826001); DIR:OUT; SFP:1102; SCL:1; SRVR:BY2PR07MB599; H:BY2PR07MB599.namprd07.prod.outlook.com; FPR:7EB8F0D9.A236460A.8FF1B9BF.8CD4D540.20315; MLV:sfv; PTR:InfoNoRecords; A:1; MX:1; LANG:en;
received-spf: None (: harvard.edu does not designate permitted sender hosts)
Content-Type: text/plain; charset="Windows-1252"
Content-ID: <C2307BD2D5B3F9409838D27EB9185E40@namprd07.prod.outlook.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: harvard.edu
Archived-At: http://mailarchive.ietf.org/arch/msg/ecrit/Pjbmkx_QoWUl54t-Pw6WyF8sN5Q
Cc: "draft-marshall-ecrit-similar-location@tools.ietf.org" <draft-marshall-ecrit-similar-location@tools.ietf.org>
Subject: [Ecrit] review of draft-marshall-ecrit-similar-location-03
X-BeenThere: ecrit@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <ecrit.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ecrit>, <mailto:ecrit-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ecrit/>
List-Post: <mailto:ecrit@ietf.org>
List-Help: <mailto:ecrit-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ecrit>, <mailto:ecrit-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Mar 2014 01:00:30 -0000

as I agreed to do during the ecrit meeting - here is a review of  draft-marshall-ecrit-similar-location-03

This looks like a very useful and simple (the two do not always go together) addition to LoST - 
something that could be lifesaver in some cases.  (There was a story on the news within the last 
year about sending emergency response to the wrong address because of just the type of issue 
that is included as an example - the address was incomplete and the responders were sent to 
the only address that came up - at least that is how the low pass filter of the news reported it)

Section 1.

current text:

This enhancement to the validation feature within LoST is required in order to ensure a high level 
of address matching, to overcome user and system input errors, and to support the usefulness of
 location-based systems in general.

Comment:

seems to me that the underlying purpose is to increase the likelihood of returning the 
actual correct civic address at the cost of possibly returning additional valid but incorrect addresses.

 

Section 2.

The RFC 2119 cite is not needed since the capitalized terms are not used in the document

 
overall.

Would there be benefit to adding a section describing the behavior where the LoST server has 
been upgraded to support this feature but the client has not?  e.g., would there be a way to also
return some indication in the completeLocation to say that there are similar addresses and that 
they should update their client - and maybe return one of the similar addresses or double them up?

     e.g. 6000 15th Ave NW|SW Seattle, WA 98107

Ugly to be sure - but …  (if this is done there should be guidance that says what the client should do -
e.g. if there is a similarLocation then ignore the completeLocation)

also - should there be any discussion of what errors or warnings a LoST server should or should not 
return if it is returning a similarLocation? (maybe to deal with the upgrade question above)

Scott