1. PEPPOL SMP OASIS BDXR TC July 25 2012

2. The PEPPOL infrastructure

3. Overall architecture CENTRAL GOVERNANCE POINTS DISTRIBUTED REPLICATED SCALED SYSTEMS SERVICE METADATA LOCATOR (SML) PEPPOL CERTIFICATE AUTHORITY (PKI) SERVICE METADATA PUBLISHER (SMP) ACCESS POINT SERVICE (GATEWAY)

4. Steps for sending documents SERVICE METADATA LOCATOR (SML) PEPPOL CERTIFICATE AUTHORITY (PKI) SERVICE METADATA PUBLISHER (SMP) RECEIVER’S ACCESS POINT SERVICE RECEIVER’S ACCESS POINT SERVICE SENDER’S ACCESS POINT SERVICE SENDER’S ACCESS POINT SERVICE 1: DNS lookup 2: HTTP GET metadata 3: Check certificate validity 4: Send document 5: Check certificate validity

5. Why is the SMP separate from the gateway (Access Point)? – Orthogonal – Can use metadata without using START – Can use START without looking up metadata e.g. hardcoded endpoints – Allows new protocols to be added – Allows alternate governance models Metadata Transport

6. How the SMP is currently being used PEPPOL infrastructure SMP service Access Point service SMP service Access Point service SMP service Access Point service National infrastructure Access Point service Nationa l SMP VANS Shared Access Point Service provider Shared SMP Service provider PEPPOL SML

7. The SMP data model ServiceGroup – Holds the participant identifier of the recipient, and a list of references to individual ServiceMetadata resources that are associated with that participant identifier SignedServiceMetadata – Holds all of the metadata about a Service, or a redirection URL to another Service Metadata Publisher holding this information

8. Example SMP data ServiceGroup – http://alfa1lab.publisher.sml.peppolcentral.org/iso6523- actorid-upis%3A%3A9902%3ADK28158815 http://alfa1lab.publisher.sml.peppolcentral.org/iso6523- actorid-upis%3A%3A9902%3ADK28158815 SignedServiceMetadata: – http://alfa1lab.publisher.sml.peppolcentral.org/iso6523- actorid- upis%3A%3A9902%3ADK28158815/services/busdox- docid- qns%3A%3Aurn%3Aoasis%3Anames%3Aspecification%3A ubl%3Aschema%3Axsd%3AInvoice- 2%3A%3AInvoice%23%23urn%3Awww.cenbii.eu%3Atrans action%3Abiicoretrdm010%3Aver1.0%3A%23urn%3Awww. peppol.eu%3Abis%3Apeppol4a%3Aver1.0%3A%3A2.0 http://alfa1lab.publisher.sml.peppolcentral.org/iso6523- actorid- upis%3A%3A9902%3ADK28158815/services/busdox- docid- qns%3A%3Aurn%3Aoasis%3Anames%3Aspecification%3A ubl%3Aschema%3Axsd%3AInvoice- 2%3A%3AInvoice%23%23urn%3Awww.cenbii.eu%3Atrans action%3Abiicoretrdm010%3Aver1.0%3A%23urn%3Awww. peppol.eu%3Abis%3Apeppol4a%3Aver1.0%3A%3A2.0

9. Some issues SMP data model is very “hardcoded” to PEPPOL’s needs and requirements SMP does not support security – all information in the SMP is always publicly displayed – Dale has pointed out some issues with using HTTPS – (partly SML related)