1 / 7

LoST status draft-ietf-ecrit-lost-05

This document outlines the changes made to the LoST (Location-to-Service Translation) protocol, including added terms, extended descriptions, bug fixes, schema modifications, and updates to various sections. It also mentions ongoing work and completed tasks related to the protocol.

maggiea
Download Presentation

LoST status draft-ietf-ecrit-lost-05

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. LoST statusdraft-ietf-ecrit-lost-05 Ted Hardie Andy Newton Henning Schulzrinne Hannes Tschofenig IETF 68 - ECRIT

  2. Changes for LoST -05 • Added the terms 'Mapping', 'LoST Client and Server', 'Service Boundary', and 'Validation' to the terminology section • Extended the description in Section 3 "Overview of Protocol Usage". • Fixed a bug in the example of Section 4 "LoST servers and Their Resolution” • Removed the 'version' attribute of Section 5.1, from the Relax NG schema and from the examples. • Modified the schema to prevent empty <path> elements. IETF 68 - ECRIT

  3. Changes for LoST -05, cont’d. • Updated text in Section 5.5: "Defining the Service Region with the <serviceBoundary> Element", 5.6: Service Boundaries by Reference: the <serviceBoundaryReference> Element", 7.3.4: “Service Boundary", and 7.4.2: “Civic Address Validation: the <locationValidation> Element”. • Fixed a bug in the example related to srsName. • Updated Section 12: "Errors, Warnings, and Redirects”. • Changed the default value for the recursion attribute from 'true' to 'false’. IETF 68 - ECRIT

  4. Changes in LoST -05 • Added Jonathan Rosenberg's intro paragraph. • Took out the optional <path> for responses. • Added NO-CACHE and NO-EXPIRATION for expires attribute with corresponding text in Section 5.2. • Modified the description in Section 6: "Path of a Request” • Modified the description in Section 7.3.3: "Recursion and Iteration” • Update to location profiles in Section 11.1: "Location Profile Usage" and in Section 11.2: "Two Dimensional Geodetic Profile" IETF 68 - ECRIT

  5. LoST -04 (Feb.) • Removal of LoST URI • editorial changes IETF 68 - ECRIT

  6. LoST -03 (Jan.) • New <mapping> element which holds the important result data, and the ability to have multiple of <mapping> elements. Not only does this organize the data better, it will better enable re-use of these items in other specs (such as the fg-to-fg syncing spec) and with future things like XML DSig. • As discussed in San Diego, the errors and warnings have been reworked to be much more compartmentalized. • Address validation is separated out. • Requests and responses now have a new <path> element which contains the <via> elements. This better enables loop detection. • The <listServices> query has had the location version separated out into a new query called <listServicesByLocation>. IETF 68 - ECRIT

  7. LoST -06 (in progress) • Usual “oops” clean-up • SRS unrecognized error • Define whether <listServicesByLocationResponse> and <listServicesResponse> need ‘expires’ parameter? • Implementations and interop testing in progress • Wonsang Song and Yong-Jul Kim (Columbia U.) • completed -05 seeker, resolver, authoritative server, FG, ... • Krzysztof Rzecki, Piotr Blaszczyk, Anna Makarowska, Michal Niedzwiecki (CCNS SA with cooperation of Institute of Telecomputing at Cracow University of Technology) • DONE • until the IESG gets their hands on it... IETF 68 - ECRIT

More Related