Uploaded image for project: 'PrintTalk'
  1. PrintTalk
  2. PTK-69

define http/https as the standard protocol

    XMLWordPrintable

    Details

    • Type: Story
    • Status: Implemented (View Workflow)
    • Priority: Normal
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.0-IP-1
    • Component/s: Introduction
    • Labels:
      None

      Description

      the current wording is:
      This document does not specify the transport for a PrintTalk object. The selection of transport is left to the implementer.
      For example, a PrintTalk object MAY be sent via email as an attachment, or it MAY be sent via HTTP using the POST or GET method.

      we might want to change that.

        Draft

        1 Introduction
        ...
        The following pages describe the Business Objects that make up PrintTalk. See Chapter 3 Business Objects for a complete
        list of Business Objects and a description of each.

        Chapers 2-4 provide the requirements of the XML data. Chapter 5 System Requirements defines the transport protocol and security requirements.

        2 Structure
        ...
        This document does not specify the transport for a PrintTalk object. The selection of transport is left to the implementer.
        For example, a PrintTalk object MAY be sent via email as an attachment, or it MAY be sent via HTTP using the POST or
        GET method.
        Note: Future ICS documents MAY restrict the transport protocol for PrintTalk in the context of specific interfaces.
        The following pages provide a detailed explanation of each PrintTalk element.

        < add cr>Figure 1 shows a high level view of the
        PrintTalk structure, where each box represents either an XML declaration (the first one) or a PrintTalk element.

        5 System Requirements
        A system that uses Printtalk will typically be deployed over the internet and therefore security and authentication need to be addressed. Since PrintTalk can contain sensitive data, it is strongly encouraged to use encryption technology whenever possible.

        5.1 Transport protocol
        PrintTalk SHALL be implemented using the request-response model using either HTTP or HTTPS as defined in cXML section 3.1.1 Request-Response Model.
        The one-way protocol defined in cXML 3.1.10 One-Way (Asynchronous) Model MAY be implemented as a secondary protocol, e.g. using hot-folders or email attachments.

        5.2 Authentication
        Whereas encryption allows for secure communication in the internet by hiding the contents of transactions from third parties, authentication is used to verify that the sender of a message is actually the entity that it claims to be. Authentification is therefore extremely important when fulfilling contracts. RFC 6750 provides methods to verify the identity of a message sender. PrintTalk defines no proprietary authentication methods but it is emphasized that authentication is important in all business transactions.

        5.3 Packaging

         

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  Unassigned
                  Reporter:
                  prosi Rainer Prosi
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  3 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: