[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] (EBXMLMSG-51) MessageId Format Clarification
[ https://tools.oasis-open.org/issues/browse/EBXMLMSG-51?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sander Fieten updated EBXMLMSG-51: ---------------------------------- Proposal: Provide that clarification - suggest that an MSH may accept messages with a MessageId that does not conform to RFC2822 (was: Provide that clarification - suggest that an MSH may accept messages with MessageId that does not conform to RFC2822) > MessageId Format Clarification > ------------------------------ > > Key: EBXMLMSG-51 > URL: https://tools.oasis-open.org/issues/browse/EBXMLMSG-51 > Project: OASIS ebXML Messaging Services TC > Issue Type: Improvement > Components: Core Spec > Reporter: Theo Kramer > Priority: Minor > > Section 5.2.2.1 states the following > eb:Messaging/eb:UserMessage/eb:MessageInfo/eb:MessageId: This REQUIRED element has a value representing – for each message - a globally unique identifier conforming to MessageId [RFC2822] > This does not indicate if an MSH must, should, may reject/accept messages that do not conform to RFC 2822 -- This message was sent by Atlassian JIRA (v6.2.2#6258)
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]