Revision Summary Date Revision History Revision Class Comments 12/18/2006 0.01 Version 0.01 release 3/2/2007 1.0 Version 1.0 release 4/3/2007 1.1 Version 1.1 release 5/11/2007 1.2 Version 1.2 release 6/1/2007 1.2.1 Editorial Changed language and formatting in the technical content. 7/3/2007 1.2.2 Editorial Changed language and formatting in the technical content. 7/20/2007 1.2.3 Editorial Changed language and formatting in the technical content. 8/10/2007 1.2.4 Editorial Changed language and formatting in the technical content. 9/28/2007 1.2.5 Editorial Changed language and formatting in the technical content. 10/23/2007 1.2.6 Editorial Changed language and formatting in the
12/16/2011 9.0 Major Updated and revised the technical content. 3/30/2012 9.0 None No changes to the meaning, language, or formatting of the technical content. 7/12/2012 9.1 Minor Clarified the meaning of the technical content. 10/25/2012 9.1 None No changes to the meaning, language, or formatting of the technical content. 1/31/2013 9.1 None No changes to the meaning, language, or formatting of the technical content. 8/8/2013 10.0 Major Updated and revised the technical content. 11/14/2013 10.0 None No changes to the meaning, language, or formatting of the technical content. 2/13/2014 10.0 None No changes to the meaning, language,
Protocol Details Client Details The Remote Mailslot Protocol clients are higher-layer applications that use the mailslot protocol to send a message to the server, as described in section . Because this is an unreliable, unidirectional protocol, there is neither a connection phase nor an acknowledgment from the server for the send from the client. Abstract Data None. Timers None. Initialization None. Triggered Events Application Writes to a Mailslot The application provides the following: TargetName: The 16-character NetBIOS name of the target to which the mailslot message MUST be sent. The name MAY be a "unique name" or a "group name" as specified in section 5.2. MailslotName: The name of the mailslot on the target server to which the message MUST be delivered. Message: The mailslot message to be sent. The maximum length of the message is limited by the underlying transport protocol. On receipt of a request from a higher-layer application to send a mailslot message, the client mailslot implementation MUST package the data to be sent and the destination mailslot name in a SMB_COM_TRANSACTION data structure by filling in the various fields, as specified in section . The MailslotName in the SMB_COM_TRANSACTION request MUST be of the form "\MAILSLOT\MailslotName." The client MUST send the SMB_COM_TRANSACTION request to TargetName using the "send datagram" primitive described in [RFC1001] section 5.4. The NetBIOS datagram service on the client machine determines whether the supplied TargetName is a "unique" or "group" name by using one of the mechanisms described in [RFC1001] section 15.1.2 and section 15.3. Based on the type of name, it sends a NetBIOS datagram to the target(s) as described in [RFC1001] section 17. <13> The Remote Mailslot Protocol itself does not provide for multi-packet segmentation. As a result, if the invoking application specifies data that is too large to be handled by the NetBIOS datagram service, the request MUST be failed with an implementation-specific error.
Index A Abstract data model 12 13 13 13 13 6 C 7 23 Client 12 12 12 13 12 13 12 12 13 12 D Data model - abstract 12 13 13 13 13 E 17 F 7 G 5 H Higher-layer triggered events 12 14 application 15 14 14 14 I 19 19 6 Initialization 12 13 5 L Local events 13 16 M 8 8 Message processing 12 15 Messages 8 8 8 8 N 5 O Other local events 13 16 6 P 19 6 6 20 R 5 6 5 6 S Security 19 19 Sequencing rules 12 15 Server 13 13 13