Document: Review of draft-ietf-geopriv-pidf-lo-02.txt
Reviewer: john.loughney@nokia.com
Date: 18 augusti 2004


Summary:

Document is quite readable. I think the proposal is quite reasonable, 
but I
would note that I was involved in a pre-GEOPRIV BOF, so I may be more
ammenable to working on this type of solution. Perhaps someone more 
paranoid
may want to have text warning of the dangers, etc., but as most of this 
stuff
is being done already in one form or another, without IETF oversight, I 
think
it is important for the IETF to standardize this work.  I'd approve it,
as long as the comments & nits get fixed.  These are fairly minor, so
could be handled with an RFC Editor's note.

Comments:

1) IANA considerations say:

	Any party may  register new 'method' tokens with the IANA as needed.

    Should the document specify how?  are methods assigned on a first 
come,
    first serve basis (or other basis)?

2) "Password-based Encryption for CMS", RFC 3211 is used with a 
keyword, so
    it should be made a normative reference, I suppose.

Nits:

1) RFC 3667/8 text needed.
2) GEOPRIV in title - should this be expanded?
3) Spacing on page 8/9 could be improved - i.e. - include a space 
between
    field descriptions.
4) Appendix B: I guess James didn't provide much text, or did some text
    get cut-off?

	   James Polk provided the text related to the 'method' element, and
	   much of the text for

5) Page header says: "GEOPRIV Location Obj", would it hurt to spell out
    Object?

Reviewer notes:

1) I'm no XML expert, so I didn't review the XML.