Service URN Classification and Update Policy (for non-emergency services) Henning Schulzrinne Andrea Forte Columbia University IETF 77 - Anaheim, California IETF 77 - ECRIT WG

Service URN Classification draft-forte-ecrit-service-classification-03.txt Motivation – Standard classification of service URNs needed for non-emergency location- based services Proposed classification – Based on Wikipedia, Yellow Pages, etc. – Starting point, not meant to be comprehensive GPS provides practical experience – Can be updated following the URN policy draft Critiques – Difficult to do, borderline with semantic web but GPS devices and YP have done this for years some classification is better than random choices – avoid different names for essentially same services – Check existing classifications and perhaps just link to those none found so far many not particularly useful for location-based services (e.g., NAICS) IETF 77 - ECRIT WG

Service URN Update Policy draft-forte-ecrit-service-urn-policy-01 Motivation – Today STANDARDS action is required for defining urn:service:food.pizza Solution – Update Section 4.1 of [RFC5031] Policy for adding top-level service labels is "Expert Review The expert is designated by the IESG Area Director Issues raised – Who can be an expert reviewer? Alternatives – Define one more open top-level service (misc?) IETF 77 - ECRIT WG