Chris, I conceptually agree with the proposed change.
At the same time, at the risk of duplicating prior comments, I see this allows for the HOSTNAME to reference a logical entity which may be a subset or superset of a physical entity. For example, foo.bar.com may easily refer to a web server process, a load-balancing switch for several e-mail servers, or a vanilla-flavor physical host machine of arbitrary use. This suggests that HOSTNAME does not and cannot unambiguously (or authentically) identify the source of the message. Is this a problem? Glen -----Original Message----- From: Christopher Lonvick --vvv--- Proposed change to Section 2.2 ---vvv--- The HOSTNAME field will contain an indication of the originator of the message in one of four formats: only the hostname, the hostname and domainname, the IPv4 address, or the IPv6 address. The preferred value is the hostname and domainname in the format specified in STD-13 [RFC 1034 and 1035]. This format will be referred to in this document as HOSTNAME-STD13. If only the hostname is used, the HOSTNAME field MUST contain the hostname only of the device as specified in STD-13 [4]. This format is discouraged but provides for legacy compatability with the format described in RFC 3164. This format will be referred to in this document as HOSTNAME-3164. In this format, the Domain Name MUST NOT be included in the HOSTNAME field. If the IPv4 address is used, it MUST be shown as the dotted decimal notation as used in STD-13 [5], and will be referred to as HOSTNAME-IPV4. If an IPv6 address is used, any valid representation used in RFC-2373 [6] MAY be used and will be referred to as HOSTNAME-IPV6. A single space character MUST also follow the HOSTNAME field. Messages containing Signature Blocks and Certificate Blocks as described in this document MUST use the HOSTNAME-STD13 format in the HOSTNAME field. ---^^^--- Proposed change to Section 2.2 ---^^^--- ------------------------------------------------------------------------------- This message and any included attachments are from Siemens Medical Solutions Health Services Corporation and are intended only for the addressee(s). The information contained herein may include trade secrets or privileged or otherwise confidential information. Unauthorized review, forwarding, printing, copying, distributing, or using such information is strictly prohibited and may be unlawful. If you received this message in error, or have reason to believe you are not authorized to receive it, please promptly delete this message and notify the sender by e-mail with a copy to [EMAIL PROTECTED] Thank you
