Re: [Ecrit] WGLC draft-ietf-ecrit-similar-location-11 -- end date Oct 13
Dan Banks <dbanks@ddti.net> Tue, 05 October 2021 21:31 UTC
Return-Path: <dbanks@ddti.net>
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 1C6403A08A6 for <ecrit@ietfa.amsl.com>; Tue, 5 Oct 2021 14:31:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.101
X-Spam-Level:
X-Spam-Status: No, score=-2.101 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_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ddti.net
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 zSOXSfSAIu0T for <ecrit@ietfa.amsl.com>; Tue, 5 Oct 2021 14:31:01 -0700 (PDT)
Received: from NAM12-DM6-obe.outbound.protection.outlook.com (mail-dm6nam12on2040.outbound.protection.outlook.com [40.107.243.40]) (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 BA98B3A089B for <ecrit@ietf.org>; Tue, 5 Oct 2021 14:31:01 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=RQ7jHKaAh2p4zltOvzUiUF8OO/5ilWnzsAbpEJ5zxDwpW3hX82nrAkPHp6MvZlbAPLYP9uoODL6rJmB6xWxEg7+lNjCDIIcTAhIFiCcXohYnwxQl7xhNLE29xQ2xU7Z/l3L0xciwIgUFMX9W3+4QTciMnIKb7ORzCHeMyyUAobHMcI3lGb7E3yPStMq9cv6ymjrdrUthkhWQIRMtUawjwbu3epk7ohBU+PZqaCW+nV4pj0lRYl+NKsXsFidteBlnd2eUd/1eRFeyiTdn+iO3VTa4PYCmbZsBjm2mQKIJXhNGjvSF/BIFzOnmbKtwjtnfDEQAIbuPkBAOrfQ8Z91bdw==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=ejoVWBBD5oIhFttG+hj3YVvVQycqNGh4XwB31ENmnlc=; b=n120mcMFT+XHvzInxfrmImz//+izOwxGxZMnRpTEAUwWFkHaAVKFJbyp7DeZgWh1swDDrBoSy1V9u5+dS98vTo4Kgn8wFtp2wFlHt710D2sU40tK7KZJBwq2TOqgGfoIaSkaxhDav/cCD84HQ7Gl0hLsvnuxq9O16U4i5cNXxjqZOKVoK8YjG2wwqwVykCTOUBHXjiQWQrOWks7hdtUnCv0IEh8R2Mz36oUvkgS4O0HDMHDcWhzVUMmRNDtRzk+a9XNtIx2ooa7skd7JSXeNQRLxP67OCrNqB2L9Uw28lXGd5G+K1GXT+bAS2L8Qd7iHjhqumxikU49P9XsiUkyrUQ==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=ddti.net; dmarc=pass action=none header.from=ddti.net; dkim=pass header.d=ddti.net; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ddti.net; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=ejoVWBBD5oIhFttG+hj3YVvVQycqNGh4XwB31ENmnlc=; b=WCuWZ+9GG86EbSxGIfrdFv7+TAs3C1LyI+y/l1CX3ajdO0xwyeixBmUsmxn+z2pPRjTrH/SL6UnHUn7fqvOOwLqmrIfgZt2tuOgHfpkMqEeWS59zB+VAaFn07oDHQ+j1g8LV4TDkBwJB6y85PYx3XlHcYpJHkNwJ/wwiKdKq5dY=
Received: from DM5PR1701MB1818.namprd17.prod.outlook.com (2603:10b6:4:1c::19) by DM5PR1701MB1753.namprd17.prod.outlook.com (2603:10b6:4:20::11) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.4566.21; Tue, 5 Oct 2021 21:30:59 +0000
Received: from DM5PR1701MB1818.namprd17.prod.outlook.com ([fe80::6436:ffa4:8d34:e4ed]) by DM5PR1701MB1818.namprd17.prod.outlook.com ([fe80::6436:ffa4:8d34:e4ed%8]) with mapi id 15.20.4566.022; Tue, 5 Oct 2021 21:30:58 +0000
From: Dan Banks <dbanks@ddti.net>
To: Randall Gellens <rg+ietf@randy.pensive.org>, ECRIT <ecrit@ietf.org>
Thread-Topic: [Ecrit] WGLC draft-ietf-ecrit-similar-location-11 -- end date Oct 13
Thread-Index: AQHXtWtw8lohM9YlLU+gKQfMlDBJjavEtaXg
Date: Tue, 05 Oct 2021 21:30:58 +0000
Message-ID: <DM5PR1701MB1818510A235B96FEAC3A64EAA7AF9@DM5PR1701MB1818.namprd17.prod.outlook.com>
References: <6AA591C6-B84B-4A7E-936A-10C95C5FA936@randy.pensive.org>
In-Reply-To: <6AA591C6-B84B-4A7E-936A-10C95C5FA936@randy.pensive.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: randy.pensive.org; dkim=none (message not signed) header.d=none; randy.pensive.org; dmarc=none action=none header.from=ddti.net;
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: e6208682-fa51-414d-3832-08d988476c40
x-ms-traffictypediagnostic: DM5PR1701MB1753:
x-microsoft-antispam-prvs: <DM5PR1701MB17530C44E59D7DE223F29A8EA7AF9@DM5PR1701MB1753.namprd17.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-ms-exchange-senderadcheck: 1
x-ms-exchange-antispam-relay: 0
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: Z9luZ7BaU41cBRH597V2yP+iR2PyRQV+drLuHFl4tf9WpjrRJQeyygOanzKhQkFxxMAvxvQMnhiotXqz5vFWd/KUvvB1sJ2k2mHmXnlvMIiMOgdslnxkUeCIFYPLuvzMpw5cqZ0+vOwZ3GAU902hP77wN1/wt/Xjbsg7v+mQZdyQh7DRUiQHNG+J/PVBA1R9tKwIUYhDP+kNOzQQRJT6texxOdcdlhiKk0HuD5bJdrzluTSjrGB+4O+rtfiX/iwhrul400P87nPdYTxe9Tc1Iv1tkew4HVMrEjxuREAec+bbPeggBlsFUcFUeT1/EnSkmIgXri5IVu8ADmGidUkDFXas86PgJpK05rIiVJPrTGnz+V7yDvaAAWIrQbGUxt8s3XmF/H9V3wkqxh0oqfjvaQvoniBs7pF4GFVre5DrLOroMSfC1Vl7U2aB/nx/gx77m5QHpDQ46PUQldhhupwsaVbXdTRl+MMY3Us1Kw0m16OqV+/Cp9rkLX1t45+pfsz55KCT2iGk0N78BnCLqrboUIiRFuukljVMvsQ5fhVaQWunxqwTxVTb1FnxFQzfpBzHNgkUsstASanJt1zYAem/E0+OUvcNmdWsrNqKMuELUPInpo4fLBopQaYk2WfsggXnnvkIMjNtCjsIBvGXoYZeQtKEFE9dUx2Em40Dk5bJJU0tKVVWKakz37pKMzpwPpDvgWxj833VAsmwgKoVkZTwYyaLNc4Sg4NA6TnOSG0UvS7G5gT9QnU3RJl3XLcXArFUMaFo6CD+AHY1D9JcYOUkb87Bl+4CKM4TvjbhZGE8WYQ=
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:DM5PR1701MB1818.namprd17.prod.outlook.com; PTR:; CAT:NONE; SFS:(4636009)(366004)(396003)(346002)(39830400003)(376002)(136003)(2906002)(83380400001)(966005)(186003)(26005)(8936002)(33656002)(5660300002)(45080400002)(508600001)(38070700005)(122000001)(38100700002)(8676002)(53546011)(6506007)(86362001)(66946007)(66446008)(7696005)(110136005)(64756008)(9686003)(316002)(52536014)(66556008)(55016002)(66476007)(76116006)(71200400001); DIR:OUT; SFP:1101;
x-ms-exchange-antispam-messagedata-chunkcount: 1
x-ms-exchange-antispam-messagedata-0: lXXy2z7iBccZON1cWJgxJQj1oQ3Ko1oxrDcwgFB4Opxrg/NyTgmIoFir7ExC11GtN7wPkFvHKJyr1yrPPH4nvJAGCE1yGsm32zA5nV99M5uw6Pn5qhrIX6y3zE/1xKnTZKON/9yop17OVbMUzcmj/Ktrv4ha9I2PzGxzoetz2NuC0uAo2JScvpEgeV+xaIasL+VOi9gz0MCYSVujierxKOoGOFT77KWaT2MaWBXhtXdXK5EtMXzm8L+yg2bETcPd+OHfb7cYVf9ndTDmGgnAhO2yL3yHK2jlF7FTn5dZ+AKa8yNncR28+0nXzV6yTwsSSexDj+jpqFdXcoXRDQ1ybwJnngXfN9H3HOhd8uJeJoGRmLC62I+wAvdMmMkV9pCCiLTmW1yr5jUaYjZa/TokF0Iw0wQN3cRYrhng7h4K8xsy141FWxdd1rBvwJzydKcSrgsykJL965rKRfWWBlaFprRgbNJN+VA4KV6igp1QnnmuK6gSkXEg7wPRQGLIiPUjXziU+emLHnt+W0eT2cyZA4Kp+RbCjkXffaBh6kxBTyL2VJ7vCBzVG15NEwuZacWE9YGQzeVOfAC58twab5nSWqiFZR2q7HbDmnWEksKdba/QrkEJqyrGoNBHzz5CpqWP3pUlVXwlDaSazuxBuXZ2Fw/14C1pw+oIl5MWtyWIBOc4bVEugYznXw7i+ul1h7foo9/OjiMo2sL5CEEna9wIkXep3Nu08lbQzuhDj3NPO6VeA96s/Gvm30w9N33udOXSNpr/7H5RuBCJ11h7mVjmaLIs9VPr+PvWH3RdkF4rWscXvZVQdIR6kP6aYpI3nQ456d/Tv8E0+GDMtbwWX4SEG/zU50lKYr+cGGdirlb1uI4vZgAMI3tVhFV4kmTmgbseAB4nJi5s7tvmhbXsQeDqzRmN5f8Insr47bf3MEOcI5+gf0UVHStr6huR+TsLkaTlS7c+xIgVeoiPjpPd7qAktRVdyxGKL6Ikd9v3dzeca67f8rUH7pkVqNvtZm/L3qP6C2yURNvl0RwwRnXwiK5mcnHyaTY6Prsn6/VwiNl7/bMcRxeiP9iZt4h97/edJ+7iMQee8aPewli9gFQA1tDYaNm5xaFRH+z/33MwWx6t9ril5XqBhfWA3b0BCE2DPy2csCKj24e8SkH+nfa+7ffdmmAewgVH27FaHuxvXo3NjVS6gnq8fWt3iNssGkxSG8Mbhp2JTUbSdeIjhO/dRlfOvplBuIKOwnwc6i8EDES3I9n3AXXEu6SuWp8l6SA26zOyOmIht9MCnuis1Jx3eA9i0muavRSHcNfUDTT24+xV1/FeSydGevh5xq4RGMFU7mOp
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: ddti.net
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: DM5PR1701MB1818.namprd17.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: e6208682-fa51-414d-3832-08d988476c40
X-MS-Exchange-CrossTenant-originalarrivaltime: 05 Oct 2021 21:30:58.8919 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 4c0f48ba-5f29-44b1-b29c-1aff8251101b
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: 4mG4xMfTws646TNU021GJBF+Y6UiRiL96RO/rHz/Zv4bFU6hvxONMkv2wRHbe4VJ
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM5PR1701MB1753
Archived-At: <https://mailarchive.ietf.org/arch/msg/ecrit/5F5WUQhrlBFPwP4Vskr2rl78-GU>
Subject: Re: [Ecrit] WGLC draft-ietf-ecrit-similar-location-11 -- end date Oct 13
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:31:08 -0000
I have reviewed draft -11 and in addition to my earlier response to Victor's comments, I have the following suggestions and feedback: In section 2, Terminology Change: Civic Address Element: The term Civic Address Element is used within this document to apply to an individual CAtype data descriptor, for example, as is described in [RFC4776], [RFC5774], and [RFC6848]. To: Civic Address Element: The term Civic Address Element is used within this document to indicate any individual XML element used within the <civicAddress> type defined in [RFC5139], including elements used at the extension point therein such as those defined in [RFC6848] and elsewhere. This term also includes the reference to such elements by qualified name as defined within the <locationValidation> element in [RFC5222]. The definitions of Invalid Location and Valid Location being constrained to those locations that have actually been queried against a LoST server is problematic for the usage elsewhere in the document. While we could argue that a location is neither Valid nor Invalid until we actually test it, then we would have to separately define "expected" valid and invalid locations. I think it would be better to modify the definitions as follows: Change: Valid Location: A Civic Location that was included in a LoST query with 'validateLocation' set and subsequently returned with all Civic Address Elements in the <valid> or <unchecked> lists. To: Valid Location: A Civic Location that, when included in a LoST query with 'validateLocation' set, will obtain a response having all Civic Address Elements in the <valid> or <unchecked> lists. Change Invalid Location: A Civic Location that was included in a LoST request with 'validateLocation' set and subsequently returned with one or more Civic Address Elements marked as invalid. Note that location information may be submitted in the <findService> request that causes the LoST server to return Civic Address Elements in the <invalid> list. It is also possible that the location information submitted is so inaccurate that this extension can not be used, and the LoST server may return a <notFound> error. In this document, we use the term Invalid Location only to refer to a case where the LoST server returns one or more elements in the <invalid> list. To: Invalid Location: A Civic Location that, when included in a LoST query with 'validateLocation' set, will obtain a response having one or more Civic Address Elements in the <invalid> list. Note that It is also possible that the location information submitted is so inaccurate that location validation cannot be performed, and the LoST server may return a <notFound> or <locationInvalid> error. In this document, the term Invalid Location only refers to a case where the LoST server returns one or more elements in the <invalid> list; the error conditions are not considered. I suggest rewording the definition for Similar Location to make it more clear. Change: A suggested civic location that is similar to the civic location which was input, but which had one or more invalid civic address elements returned by the LoST server or was missing Civic Adddress Elements the server has for the location. To: A suggested civic location that is similar to an Invalid Location which was used in a LoST query, but which has one or more elements added, modified, or removed such that the suggested location is a Valid Location. It's probably good for the draft to allow the use of not-yet-defined location profiles that "derive" from the civic profile, but it is also a bit problematic. Even in RFC 5222, the concept of location validation is really only discussed with respect to the baseline civic profile. I think we need a few changes related to that. In section three, first paragraph: Change: This extension is applicable when the location information in the <findService> request is in a civic profile as described in RFC5222 or in another profile derived from that civic profile. To: This extension is applicable when the location information in the <findService> request is in the Basic Civic profile as described in RFC5222 or in another profile derived from the Basic Civic profile. Because such derived profiles have not yet been defined, this document describes the returned location extension primarily in terms of how it is to be used with the Basic Civic profile. Future definitions of profiles deriving from the Basic Civic profile SHOULD provide instructions concerning the use of their respective profiles with this extension. In addition, the following restriction is imposed: A server MUST NOT include Returned Location Information using a location profile that differs from the profile of the location used to answer the query and, by extension, MUST NOT include Returned Location Information using a location profile that was not used by the client in the request. In section four, first paragraph, Change: The <completeLocation> and <similarLocation> elements contain a list of Civic Address Elements identical to the elements used in the location element with the 'civic' profile in [RFC5222] or another profile derived from the civic profile. To: The <completeLocation> and <similarLocation> elements are of type "locationInformation" as defined by the LoST schema in [RFC5222], and contain location information in the same profile of the location used to answer the query. These elements MAY contain location information either in the Basic Civic profile defined in [RFC5222] or in another profile that derives from the Basic Civic profile when such a profile has been defined. When used with the Basic Civic profile, these elements contain a <civicAddress> element as defined in [RFC5139]. In the middle of section three, Change: in the case where a LoST server response includes one or more Civic Address Elements marked as invalid, constituting an Invalid Location response. To: in the case where a LoST server response includes one or more Civic Address Elements marked as invalid, indicating an Invalid Location used in the query. Change: The other use case for this extension is when Invalid Location is received from the LoST server. To: The other use case for this extension is when Invalid Location has been used To query the LoST server. And also change: When a LoST server returns a response to a <findService> request that contains a set of Civic Address Elements with one or more labeled as invalid, the location information in the <findServiceResponse> can be extended to include one or more locations that might be the location desired. To: When a LoST server returns a response to a <findService> request that contains a set of Civic Address Elements with one or more labeled as invalid, the validation portion of the <findServiceResponse> can be extended to include one or more locations that might be the location desired. In the final paragraph of section three, Change: This extension allows the LoST server to include the above similar addresses in the response to 'validateLocaton' request. To: This extension allows the LoST server to include the above similar addresses in the response to a <findService> request having 'validateLocaton' = true. In the schema, the <group> element still needs to be corrected to include an xs: prefix. Overall, section three, the "overview", has the same concepts expressed more than once. This seems unnecessary. Also, the overview is about twice as long as section four. I would like to see some effort to make these two sections better organized. I believe the extension defined here is useful (and implemented a version of it quite some time ago), but I think the draft deserves another pass or two before it advances. Dan Banks > -----Original Message----- > From: Ecrit <ecrit-bounces@ietf.org> On Behalf Of Randall Gellens > Sent: Wednesday, September 29, 2021 3:52 PM > To: ECRIT <ecrit@ietf.org> > Subject: [Ecrit] WGLC draft-ietf-ecrit-similar-location-11 -- end date Oct 13 > > This starts WGLC for draft-ietf-ecrit-similar-location-11, a LoST extension to > return complete or similar location info. > > Please send both comments and messages that you support advancement of > the draft to this mailing list before October 13. > > Thank you, > > --Randall > > _______________________________________________ > Ecrit mailing list > Ecrit@ietf.org > https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fww > w.ietf.org%2Fmailman%2Flistinfo%2Fecrit&data=04%7C01%7Cdbanks% > 40ddti.net%7Caa8d2edeb98a4a7b667108d98382903a%7C4c0f48ba5f2944b1b2 > 9c1aff8251101b%7C0%7C0%7C637685419081084242%7CUnknown%7CTWFpb > GZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI > 6Mn0%3D%7C1000&sdata=%2BmezKd%2FhSQT3mUcMvQcEg3IWNUus > 1yuz%2FU%2B0dim%2BTfI%3D&reserved=0
- [Ecrit] WGLC draft-ietf-ecrit-similar-location-11… Randall Gellens
- Re: [Ecrit] WGLC draft-ietf-ecrit-similar-locatio… Dwight Purtle
- Re: [Ecrit] WGLC draft-ietf-ecrit-similar-locatio… Caron, Guy
- Re: [Ecrit] WGLC draft-ietf-ecrit-similar-locatio… Dan Banks
- Re: [Ecrit] WGLC draft-ietf-ecrit-similar-locatio… Randall Gellens
- Re: [Ecrit] WGLC draft-ietf-ecrit-similar-locatio… Randall Gellens
- Re: [Ecrit] WGLC draft-ietf-ecrit-similar-locatio… Caron, Guy
- Re: [Ecrit] WGLC draft-ietf-ecrit-similar-locatio… Randall Gellens
- Re: [Ecrit] WGLC draft-ietf-ecrit-similar-locatio… Dan Banks
- Re: [Ecrit] WGLC draft-ietf-ecrit-similar-locatio… Randall Gellens
- Re: [Ecrit] WGLC draft-ietf-ecrit-similar-locatio… Randall Gellens
- Re: [Ecrit] WGLC draft-ietf-ecrit-similar-locatio… Roger Marshall
- Re: [Ecrit] WGLC draft-ietf-ecrit-similar-locatio… Jeff Martin