| |
RFC 2822もobsoleteになって，RFC 5322になったものを眺め直して
みると，Message-IDフィールドについては
The message identifier (msg-id) itself MUST be a globally unique
identifier for a message. The generator of the message identifier
MUST guarantee that the msg-id is unique. There are several
algorithms that can be used to accomplish this. Since the msg-id has
a similar syntax to addr-spec (identical except that quoted strings,
comments, and folding white space are not allowed), a good method is
to put the domain name (or a domain literal IP address) of the host
on which the message identifier was created on the right-hand side of
the "@" (since domain names and IP addresses are normally unique),
and put a combination of the current absolute date and time along
with some other currently unique (perhaps sequential) identifier
available on the system (for example, a process id number) on the
left-hand side. Though other algorithms will work, it is RECOMMENDED
that the right-hand side contain some domain identifier (either of
the host itself or otherwise) such that the generator of the message
identifier can guarantee the uniqueness of the left-hand side within
the scope of that domain.
となって一部を除き変更がありませんでした。
@の右側については RECOMMENDED になっていますが，@の左側については
a combination of the current absolute date and time along
with some other currently unique (perhaps sequential) identifier
available on the system
がよかろうという表現になっています。
|
|