ebxml-msg message

Subject: [OASIS Issue Tracker] Created: (EBXMLMSG-37) AS4 5.2 Usage Agreement for X.509 token profile use

From: OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>
To: ebxml-msg@lists.oasis-open.org
Date: Sat, 12 Oct 2013 13:56:39 +0000 (UTC)

AS4 5.2 Usage Agreement for X.509 token profile use
---------------------------------------------------

                 Key: EBXMLMSG-37
                 URL: http://tools.oasis-open.org/issues/browse/EBXMLMSG-37
             Project: OASIS ebXML Messaging Services TC
          Issue Type: Improvement
          Components: AS4 Profile
            Reporter: Pim van der Eijk
            Priority: Minor


Section 5. defines some operational aspects of AS4 that have to be agreed on in communities.  This section obviously does not have to (and cannot) be complete,  but it is not clear why section 5.2.6 (b) asks which encryption algorithms and minimum key lengths are required, (c) which Certificate Authorities are acceptable for server authentication etc.  these same questions could be asked for SOAP message security,  parameters defined in 2.1.3.6 


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira