ebxml-msg-as4 message
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]
Subject: proposed updates to Deplyment section
- From: "Durand, Jacques R." <JDurand@us.fujitsu.com>
- To: <ebxml-msg-as4@lists.oasis-open.org>
- Date: Sun, 30 Nov 2008 22:11:54 -0800
After reviewing the Deployment Profile section,
it looks like it needs some update and could be
split in :
(1) profiling rules for previously described
features,
that are to be enforced in order to be AS4
compliant
(2) agreement options (and possible additional
profiling) that are covered by PMode.
Most trading partner agrements items will be agred
on in the PMode.
This would include the Operational Profile
(currently section 4.10)
In (1) we'd have:
4.2.1: Only the bundling option makes sense for
deplt profile.
Maybe this table should be focused on bundling
options, especially for the Receipt,
with any possible restriction.
Other content not needed (already mentioned in Conf
Profile feature tables,
and the PMode aspect is not needed.)
4.6.1: Security element content profiling rules
4.6.2: Message Signing profiling rules
4.6.3: Attachment Signing profiling rules
4.6.4: Encryption profiling rules (+ new PMode
parameter?)
4.6.5: Attachment Encryption profiling rules
4.6.8 Authentication profiling rules e
4.6.9 Receipt signing profiling rules
In (2) we'd remind of the PMode parameters and
other AS4-relevant options
that need be agreed on:
4.3.1: PMode options.
4.5.1: PMode options.
- add PMode option for compression
- add PMode option for delivery
awareness
Subsections that can be removed, or repurposed for
V3
4.4.1: remove
4.6.6 remove (a non-profiled core V3
option)
4.6.7 remove: covered in the CP
sections
4.6.10 remove (a non-profiled core V3
option)
4.7.1: remove (V2)
4.8.1: remove (V2)
4.9.1
4.9.2
4.9.3
4.9.4: repurpose for V3
-jacques
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]