OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

ebxml-msg message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]


Subject: [ebxml-msg] Comments on the 1.09 about MessageId


Please delete Line 877 in Page 21.

  3.1.6.1 MessageId element

  The REQUIRED element MessageId is a unique identifier for each message
  conforming to [RFC2392]. The "local part" of the identifier as defined
                           ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  in [RFC2392] is implementation dependent.
  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

When we discussed MessageId's format in a face-to-face meeting, we used
the term "local part" as following:

    An idea of MessageId format = [local part]@[full domain name]

However the RFC2392 does not define actual format of MessageId and does
not use the term "local part". RFC2392 just says that:

  "... A common technique used by many message systems is to use
   a time and date stamp along with the local host's domain name, e.g.,
   950124.162336@XIson.com."

So please delete the Line 877. It causes confusing. 


P.S.
Definition of MessageId format is still one of our issues (IssueID 11).


Regards, 

--
SHIMAMURA Masayoshi <shima.masa@jp.fujitsu.com>
TEL:+81-45-476-4590(ext.7128-4241)  FAX:+81-45-476-4726(ext.7128-6783)
Planning Dep., Strategic Planning Div., Software Group, FUJITSU LIMITED



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]


Powered by eList eXpress LLC