Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


 Date: 2019-02-12

Time: part 1 10:00-10:40 and part 2 11.30 to 12.30 CET

...

A more explicit transition process including new transport profile identifier (such as 'busdox-transport-as2-ver2p0') for the new AS2 profile could work smoother:

...

Also, from an organizational perspective, since the new AS2 protocol spec is backwards incompatible with current AS2 spec, a different protocol version will clearly denote that. As a side effect, we will also have the DEPRECATED flag on the codelist, making it clear that this is no longer used and that a new incompatible specification now is in use.


Summary

...


Migration processProsCons

Keep existing transport profile id

V1: required to receive

V2: migration period without changing the ID

  • Support for receiving documents with the new AS2 profile at date X. Forbidden to send with the new AS2 profile at this stage.
  • Support for sending  with the new AS2 profiles at date Y (Y > X).
  • Mandatory to only send and receive with the new AS2 profile after date Z (Z > Y).
  • Less effort for SPs
  • More failed transactions during the transition phase
  • Hard to get an overview of which APs that support the new AS2 profile.
New transport profile id
  • Remove/deprecate old transport profile id at a certain date/time
  • Assign new Transport Profile ID to all endpoints/participants after previous step has been performed.
  • More explicit and more control of who are supporting the new transport profile id
  • Less failed transactions during the transition phase
More effort for SPs with SMP metadata registrations






SMP providers should

  1. Remove old transport profile id at a certain date/time
  2. Assign new Transport Profile ID to all endpoints/participants after previous step has been performed.



To-do’s

  1. Include the new transport profile id 'busdox-transport-as2-ver2p0'
  2. Include http/1.1 (as in v.1.3) (see 
    Jira Legacy
    serverSystem JIRA
    serverIdb5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004
    keyTICC-69
    )
  3. Member review (until March 10)
  4. Comment resolution (until ≈ March 17)
  5. Release PEPPOL AS2 profile v.2.0 specification
  6. Decide a migration start date / end date for service providers
  7. Propose the above steps to the MC for approval

...