[Ecrit] Direction of holes draft

"Thomson, Martin" <Martin.Thomson@andrew.com> Tue, 23 June 2009 01:01 UTC

Return-Path: <Martin.Thomson@andrew.com>
X-Original-To: ecrit@core3.amsl.com
Delivered-To: ecrit@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CBBD43A6B05 for <ecrit@core3.amsl.com>; Mon, 22 Jun 2009 18:01:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.549
X-Spam-Level:
X-Spam-Status: No, score=-2.549 tagged_above=-999 required=5 tests=[AWL=0.050, BAYES_00=-2.599]
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 hhewWq6lMioC for <ecrit@core3.amsl.com>; Mon, 22 Jun 2009 18:01:36 -0700 (PDT)
Received: from andrew.com (smtp3.andrew.com [198.135.207.235]) by core3.amsl.com (Postfix) with ESMTP id 01B0A3A687C for <ecrit@ietf.org>; Mon, 22 Jun 2009 18:01:35 -0700 (PDT)
X-SEF-Processed: 5_0_0_910__2009_06_22_20_23_41
X-SEF-16EBA1E9-99E8-4E1D-A1CA-4971F5510AF: 1
Received: from aopexbh2.andrew.com [10.86.20.25] by smtp3.andrew.com - SurfControl E-mail Filter (5.2.1); Mon, 22 Jun 2009 20:23:41 -0500
Received: from AHQEX1.andrew.com ([10.86.20.21]) by aopexbh2.andrew.com with Microsoft SMTPSVC(6.0.3790.3959); Mon, 22 Jun 2009 20:01:51 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Date: Mon, 22 Jun 2009 20:01:49 -0500
Message-ID: <E51D5B15BFDEFD448F90BDD17D41CFF105EC7AB4@AHQEX1.andrew.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: Direction of holes draft
Thread-Index: AcnznjBhT/1RasU6TL6m/Y3jjLSIDw==
From: "Thomson, Martin" <Martin.Thomson@andrew.com>
To: ECRIT <ecrit@ietf.org>
X-OriginalArrivalTime: 23 Jun 2009 01:01:51.0623 (UTC) FILETIME=[316AB970:01C9F39E]
Subject: [Ecrit] Direction of holes draft
X-BeenThere: ecrit@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <ecrit.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Tue, 23 Jun 2009 01:01:36 -0000

Cullen raised some concerns about the additional feature that this document requires.  He suggested that an alternative would not require support of interior polygons, or holes.

I'd like to confirm that the WG is OK with taking the document as is, without making this proposed change.

Thanks,
Martin

Below is a summary of our discussion:
--
The alternative does not use the <interior> element of the polygon to create holes.  Instead, polygons are sliced into two or more sections so that the “holes” became external to each section.  Each section is created as a separate mapping.

We concluded that the alternative solution proposed is viable, but the existing method is best when considering the deployment implications.

Alternative pros:

No additional functions required by the protocol.
No additional functions required by LoST implementations.

Alternative cons:

This isn’t how people think about the problem.
Regions with holes would need to be divided up by a provisioning system into multiple regions with separate mappings.
This likely requires changes to the provisioning and GIS systems that feed LoST, these systems already exist and therefore the cost is higher (at least we know that LoST implementations barely exist).
The existing solution is already documented and agreed.

--

------------------------------------------------------------------------------------------------
This message is for the designated recipient only and may
contain privileged, proprietary, or otherwise private information.  
If you have received it in error, please notify the sender
immediately and delete the original.  Any unauthorized use of
this email is prohibited.
------------------------------------------------------------------------------------------------
[mf2]