rws@EXPO.LCS.MIT.EDU (Bob Scheifler) (09/07/89)
An MIT X Consortium draft standard of the X Display Manager Control Protocol (XDMCP) is now available for Public Review. This draft standard establishes a protocol for managing remote X displays, such as X terminals. The objective of Public Review is to determine if the current draft is acceptable as a Consortium standard. Public Review can result in changes to the draft standard. Public Review of XDMCP is scheduled to end December 8. The X community is encouraged to review the draft and submit comments by electronic mail to xdmcp@expo.lcs.mit.edu Comments sent to other addresses are not guaranteed to be considered. Commentors should take the review process seriously, and should: 1. Identify objectionable wording in the document. 2. Suggest specific alternative wording. and most importantly: 3. Provide a rationale for the suggested change. Commentors should also carefully distinguish between: 1. Problems that they regard as intolerable and that must be corrected before the document becomes a standard. 2. Aspects that they don't like but could live with for a few years until a future revision of the standard. 3. Additional functionality that they can live without in an initial standard but would like to see in a future revision. A Consortium committee will review the comments and respond to commentors. The following documents are available via anonymous ftp to expo.lcs.mit.edu in the directory /pub/XDMCP/ xdmcp.ms XDMCP troff source xdmcp.ps XDMCP in PostScript xdmcp.text XDMCP in plain text The documents are also available via the archive server at xstuff@expo.lcs.mit.edu. The following items are available, by sending a message with the Subject: line of "send etc <itemname>" and an empty message body: xdmcp.ms XDMCP troff source xdmcp.ps.1 XDMCP in PostScript split in 3 parts xdmcp.ps.3 xdmcp.ps.4 xdmcp.text.1 XDMCP in plain text split in 2 parts xdmcp.text.2 For example, use "send etc xdmcp.ms" to retrieve troff source. Some mailers produce mail headers that are unusable for extracting return addresses. If you use such a mailer, you won't get any response. If you happen to know an explicit path, you can include a line like path foo%bar.bitnet@mitvma.mit.edu or path bar!foo!frotz in the body of your message, and the daemon will use it. If you simply cannot obtain the XDMCP from the network, you may request a paper copy by writing to: Michelle Leger Laboratory for Computer Science 545 Technology Square Cambridge, MA 02139