IETF Logo Mail Archive

Re: [Ecrit] draft-ietf-ecrit-similar-location-11.txt (was: Ecrit Digest, Vol 187, Issue 52)

"Caron, Guy" <g.caron@bell.ca> Tue, 05 October 2021 21:01 UTC

Return-Path: <prvs=9055f9792=g.caron@bell.ca>
X-Original-To: ecrit@ietfa.amsl.com
Delivered-To: ecrit@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 58E633A0474 for <ecrit@ietfa.amsl.com>; Tue, 5 Oct 2021 14:01:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Level:
X-Spam-Status: No, score=-2.1 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=bell.ca
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 RoRGMRZVJxjH for <ecrit@ietfa.amsl.com>; Tue, 5 Oct 2021 14:01:37 -0700 (PDT)
Received: from ESA1-Dor.bell.ca (esa1-dor.bell.ca [204.101.223.58]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2A1A63A0475 for <ecrit@ietf.org>; Tue, 5 Oct 2021 14:01:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bell.ca; i=@bell.ca; q=dns/txt; s=ESAcorp; t=1633467697; x=1665003697; h=from:to:subject:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version; bh=J29Ztdx/KjLMeZCejfS2U/gAobqfRmOATiwzqaMA8KQ=; b=eezcx7Ppn4DWlrIdRnsjL/4xe43ghZ/c9IistK6MZiwUSOqz842FOca5 ZujXK1/RvYjJETx+y3JRwS9yvuQd30qEki18BJ1RiJHbPOCdsmdMYhiQh 0KCat4lkYMKRuJpPfdIdItUQjtRLgVrqjV5gO6GoYk7uuwZZ+pnsjDnei dwB6fGmjLvd4Q7aMrAxF8D56dfF9CSpebOFAcx0K+mxGkIiZJXCd3BBy2 foNhSCrWyk3OQNdrnQl+bp8e4GQBnJ6RPcy8T162nihCbCjjq3sEt92Z4 b2MBEY+7ct5BtMN2Abh/9HmaKqijA00BE9Sx0SnBHcaUlgy1HbsxlXyp4 w==;
IronPort-SDR: Cc8NqKN86+EsoINuE2KaNJ1yceJpNPP81Y+hCKPz7cLqKD5WvrxfYhI61BnFqOxRqHh4ODaqls L8VDaSFce8Tg==
Received: from dc5cmy-d00.bellca.int.bell.ca (HELO DG1MBX01-WYN.bell.corp.bce.ca) ([198.235.121.229]) by esa01corp-dor.bell.corp.bce.ca with ESMTP; 05 Oct 2021 17:01:31 -0400
Received: from DG12MBX03-WYN.bell.corp.bce.ca (142.182.18.48) by DG1MBX01-WYN.bell.corp.bce.ca (142.182.18.11) with Microsoft SMTP Server (TLS) id 15.0.1497.18; Tue, 5 Oct 2021 17:01:30 -0400
Received: from DG12MBX01-WYN.bell.corp.bce.ca (142.182.18.46) by DG12MBX03-WYN.bell.corp.bce.ca (142.182.18.48) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2242.10; Tue, 5 Oct 2021 17:01:30 -0400
Received: from DG12MBX01-WYN.bell.corp.bce.ca ([fe80::e0dd:6ba7:3471:98e7]) by DG12MBX01-WYN.bell.corp.bce.ca ([fe80::e0dd:6ba7:3471:98e7%4]) with mapi id 15.01.2242.010; Tue, 5 Oct 2021 17:01:30 -0400
From: "Caron, Guy" <g.caron@bell.ca>
To: Victor Burton <victor.burton@comtechtel.com>, "ecrit@ietf.org" <ecrit@ietf.org>
Thread-Topic: draft-ietf-ecrit-similar-location-11.txt (was: Ecrit Digest, Vol 187, Issue 52)
Thread-Index: Ade2Qwi6EJM8JM95TQOkkSjP9BT8GwApctoQANBo1PA=
Date: Tue, 05 Oct 2021 21:01:30 +0000
Message-ID: <a61d764578974769a18d7dc169b6fc79@bell.ca>
References: <CO6PR09MB8007CE33670D83AFF6AE2C8498AA9@CO6PR09MB8007.namprd09.prod.outlook.com> <CO6PR09MB8007CB5EF4E55BF698CC086A98AB9@CO6PR09MB8007.namprd09.prod.outlook.com>
In-Reply-To: <CO6PR09MB8007CB5EF4E55BF698CC086A98AB9@CO6PR09MB8007.namprd09.prod.outlook.com>
Accept-Language: fr-CA, en-US
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [172.24.112.65]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/ecrit/XyiJXCFjyDYjJjqZHC7Qu1NQTqw>
Subject: Re: [Ecrit] draft-ietf-ecrit-similar-location-11.txt (was: Ecrit Digest, Vol 187, Issue 52)
X-BeenThere: ecrit@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Emergency Context Resolution with Internet Technologies <ecrit.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ecrit>, <mailto:ecrit-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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: Tue, 05 Oct 2021 21:01:43 -0000

Inline.

Guy

-----Message d'origine-----
De : Ecrit <ecrit-bounces@ietf.org> De la part de Victor Burton
Envoyé : 1 octobre 2021 13:22
À : ecrit@ietf.org
Objet : [EXT]Re: [Ecrit] draft-ietf-ecrit-similar-location-11.txt (was: Ecrit Digest, Vol 187, Issue 52)

Introduction: Delete "timely".
Use of this enhancement increases the likelihood that the correct and/or complete
   form of a civic location becomes timely known in those cases where it
   is incomplete or incorrect.
[GC] I think the use of "timely" is warranted since without the enhancement, the client would not even be aware of a location being incomplete. 

Terminology: Replace "can be" with is
Location:  The term Location can be used to refer to either a civic location or a geodetic location.

Section 3: Include "US" in the similarLocation address returned from LoST. It's a required CAType for addresses submitted to the ECRF, correct?
   Similar address #1: 6000 15th Ave NW Seattle, WA 98107 US
[GC] an ECRF is one specific embodiment of a LoST server and there are other use cases that may have different policies.

   Similar address #2: 6000 15th Ave NE Seattle, WA 98105 US After reading the example in section 5.2 which aligns with section 3, the Input address: 6000 15th Ave N Seattle, WA. should also include US. I assume the LVF will validate an address without <country> but then the description in section 3 would need to state that, correct?
[GC] The input address does not contain <country> so technically speaking, there is no requirement to include it in the response.

v2.23.0 | Report a Bug | By Email