1 / 4

Policy for Defining New Non-Emergency Service Labels

This draft proposes a policy for defining new non-emergency service labels to address the need for descriptive terms for location-based services. It suggests a classification system and updates the IANA section of RFC 5031 for adding top-level service labels.

jnicholas
Download Presentation

Policy for Defining New Non-Emergency Service Labels

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Henning Schulzrinne Andrea Forte Dept. of Computer Science Columbia University Policy for defining new service-identifying labelsdraft-forte-ecrit-service-urn-policy-00 ECRIT - IETF 74 (March 2009) - San Francisco

  2. Introduction • Non-emergency location-based services are widespread • Descriptive terms for such services are almost unbounded • A policy for defining new non-emergency service labels is needed ECRIT - IETF 74 (March 2009) - San Francisco

  3. Current Approach • New service identifying labels • Creating a new service requires IANA action • Policy for adding top-level service labels is ‘Standard Action’ • True for both emergency and non-emergency services ECRIT - IETF 74 (March 2009) - San Francisco

  4. Proposed Solution • Emergency Services • Limited number of possible services • Classification is critical • Adding top-level emergency services still requires standard action • Non-emergency services • Very large number of possible services • Classification is less critical • Updating IANA section of RFC 5031 • Policy for adding top-level service labels is "Expert Review". • The expert is designated by the RAI Area Director. ECRIT - IETF 74 (March 2009) - San Francisco

More Related