Versions Compared

Old Version 2

changes.mady.by.user Hans Berg

Saved on

compared with

New Version 3

changes.mady.by.user Hans Berg

Saved on

Key

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

...

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.



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.

...