LTAP status IETF 68 - Praha March 20, 2007 Peter Sylvester - EdelWeb

Protocol reminder Conceptually asynchronous Client/server –Simplifies transfer of responsability –Model borrowed from ebXML Request + ack + confirmation Out of scope security of transfer –Can carry identifiers Very « backend » oriented

Operations Basic: –Archive, Status, Export, Verify, Delete Extended: –Out of scope, examples: transfer, split Specialized front end as proxies, controllers, management, …

Layers Transactions –Several states Operations –Idempotence, 2 results, ack +confirmation Request/response/error notice Low level types –Two layers

Flavours Defined in ASN.1and XSD –XSD automatically generated from ASN.1 Not in current draft but the next OSS Nokalva provided tool to create xsd and validate ASN.1 –ASN.1 « current » and 88 syntax Few Imports from 2005 itu database and pkix Itu results in more than 60 modules to import

XSD issues Generated schema is large –Need to split into LTAP plus « imported » –Some simplification possible Example contstraints not to use some choices of generalname Xsd can be nicer if some e-XER is added –Ex: transfer some fields into attributs

Metadata A structure inspired by mibs rdf, … –Avoid open types in ASN.1 Some metadata are global, defined by protocol: –Datatype: mime-type/oid/uri

Comparisons Webdav and Atompub –no verify –Mapping of operations to http LTAP simple operation layer –Allows encapsulation in various lower layers Smime, soap, …

status Ltans-ltap-04 –Already obsolete Xsd stuff

To be done Fit in result of automatic xsd creation Add some xsd import module Fill in details of what fields are to be set for operation –Initial request and retries –Define error types Cleanup transport, bindings and security