Subject: [Ecrit] [Fwd: COMMENT: draft-ietf-ecrit-mapping-arch]

From: Hannes Tschofenig <[email-masked]>
Date: Thu, 21 Feb 2008 20:41:06 +0200

FYI

-------- Original Message --------
Subject: 	COMMENT: draft-ietf-ecrit-mapping-arch
Date: 	Thu, 21 Feb 2008 08:29:07 -0800 (PST)
From: 	Jari Arkko <[email-masked]>
To: 	[email-masked]
CC: 	[email-masked],[email-masked], 
[email-masked]

Comment:
Christian Vogt's review:

This document describes an architecture for location based service discovery.  The architecture resolves location information into URLs.

The document is well written and about ready for publication.

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.

A smaller nit:  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.

_______________________________________________
Ecrit mailing list
[email-masked]
http://www.ietf.org/mailman/listinfo/ecrit