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 process | Pros | Cons | |
---|---|---|---|
Keep existing transport profile id V1: required to receive V2: migration period without changing the ID |
|
|
|
New transport profile id |
|
| More effort for SPs with SMP metadata registrations |
SMP providers should
- Remove old transport profile id at a certain date/time
- Assign new Transport Profile ID to all endpoints/participants after previous step has been performed.
To-do’s
- Include the new transport profile id 'busdox-transport-as2-ver2p0'
- Include http/1.1 (as in v.1.3) (see
)Jira Legacy server System JIRA serverId b5b0ccd0-0a1a-35a3-9e9e-6e3b9531d004 key TICC-69 - Member review (until March 10)
- Comment resolution (until ≈ March 17)
- Release PEPPOL AS2 profile v.2.0 specification
- Decide a migration start date / end date for service providers
- Propose the above steps to the MC for approval
...