1. March 2004GEOPRIV - IETF 59 (Seoul)1 GEOPRIV Policy draft-ietf-geopriv-policy draft-ietf-geopriv-common-policy Henning Schulzrinne Columbia University with J. Morris, H. Tschofenig, J. Cuellar, J. Polk, J. Rosenberg

2. March 2004GEOPRIV - IETF 59 (Seoul)2 Issues Commonality: should privacy rules be part of PIDF, not just PIDF-LO? Editorial – mostly resolved in author meeting yesterday

3. March 2004GEOPRIV - IETF 59 (Seoul)3 Policy relationships geopriv-specificpresence-specific common policy RPIDCIPID future

4. March 2004GEOPRIV - IETF 59 (Seoul)4 Basic structure of rules Conditions –identity, sphere, validity –identity as or + Actions Transformations

5. March 2004GEOPRIV - IETF 59 (Seoul)5 Exceptions for identity matching Very restricted set of exceptions, but better viewed as more capable matching Match domain and then check if user matches exceptions Can be translated into row matching conditions (D;U 1,U 2,…): –domain == D && user NOT IN (U 1,U 2,…) Does not interfere with additive nature or order-independence Will modify to only allow user, not user@domain to avoid nonsensical “all in example.com except joe@bar.com”

6. March 2004GEOPRIV - IETF 59 (Seoul)6 Combining rules Rule matches if all conditions match Combine matching rules only –additive permissions –order immaterial –Any field can be Undef (“NULL”) name, type (integer, bool and enum; set; …), value –TRUE has a lower privacy protection –larger integer = lower privacy –set union = lower privacy

7. March 2004GEOPRIV - IETF 59 (Seoul)7 Combining rules Boolean: TRUE iff any row = TRUE Integer: max(rows) Set: union

8. March 2004GEOPRIV - IETF 59 (Seoul)8 Open issues Additional data types needed? URI in common is really a user identifier –depends on using protocol and authentication mechanism –in SIP, could be From, PAI or authentication user name

9. March 2004GEOPRIV - IETF 59 (Seoul)9 Geo conditions Civil location match –any set of civil coordinates –currently, can express “if I’m on Main Street anywhere” useful mostly if user doesn’t know full hierarchy Geo location match –current location fully contained within spherical trapezoid of longitude/latitude values –should specify ordering,,,,

10. March 2004GEOPRIV - IETF 59 (Seoul)10 Geo transformations Set distribute flag Set retention time Keep rule (should this be generic, not just geopriv?) Provide civil location –none, country, region, city, building, full Provide geospatial location –resolution in bits –will add datum qualifier Provide timezone

11. March 2004GEOPRIV - IETF 59 (Seoul)11 Example 2003-10-01T17:00:00+01:00 2004-10-01T00:00:00+01:00 DE Bavaria Munich Perlach false full false true

12. March 2004GEOPRIV - IETF 59 (Seoul)12 Conclusion Will produce new documents with editorial changes Using protocol document needed to flesh out (was: ) element Believed to be ready for WGLC