1. DISCUSS on draft-ietf-ecrit- mapping-arch-03 Henning Schulzrinne Columbia University hgs@cs.columbia.edu 7/29/081ECRIT - IETF 72 (Dublin)

2. Regions My understanding is the queries supported here need to match the queries possible in LOST. If this is incorrect, please let me know. Right now this document does not allow the Polygon, Circle, Ellipse, ArcBand that are allowed in Lost. Synchronization problem; fixed. 7/29/08ECRIT - IETF 72 (Dublin)2

3. Coverage regions We need to have this document in sync with LOST about what shapes are allowed in a location. Right now Lost seems to allow Point, Polygon, Circle, Ellipse, ArcBand. Coverage regions are described by sets of polygons enclosing contiguous geographic areas or by descriptors enumerating groups of civic locations. For the former, the LoST server performs a point-in-polygon operation to find the polygon that contains the query point. (More complicated geometric matching algorithms may be added in the future.) The forest guides need to decide which coverage region the query is in. I think the WG need to use the same algorithm that the LOST servers use or it is possible to miss the correct tree. Agreed; needs wording. 7/29/08ECRIT - IETF 72 (Dublin)3

4. Experimental? Looking at http://www.ietf.org/u/ietfchair/info- exp.html (especially Guideline 3), I wonder why this is not Experimental. WG decision 7/29/08ECRIT - IETF 72 (Dublin)4

5. Comment One thing that I would have wished as a reader is more clarity on the organization of mapping information at the beginning of the document. The described architecture uses "forest guides" and trees of LoST servers for mapping resolution. It would be helpful for the reader if the document would define forest guides as the top level of a single conceptual hierarchy, which, at lower levels, branches into what is called "trees" in the document. The reader may wonder why the forest guides in figure 1 are interconnected. It may be worthwhile to explicitly state that these connections symbolize the optional synchronization protocol that may be executed between them. Agreed. 7/29/08ECRIT - IETF 72 (Dublin)5

6. References TLS, CMS and XML digital signatures should be informative references. Yup. 7/29/08ECRIT - IETF 72 (Dublin)6