This is a proposed draft of a routing message schema for use with the MASS schema. The purpose of the draft is to propose a structure for the routing message elements agreed upon by the MASS Account Origination and Maintenance subcommittee. The routing message is intended to be associated with a business message of a type defined in the MASS specification. The purpose of the business message is to convey specific transaction instructions from one business participant to the other. The purpose of the routing message is to facilitate communication of the business message from its originator to its recipient through zero or more intermediate systems. Unlike the MASS message schema, this schema is not intended as a specification, but as guidance to industry participants implementing transport mechanisms for MASS messages. The network address of the originator. The originator is the system that created the business message. The unique identification number given to the business message by the originator. When the message was sent by the originator. Version of the message schema used to create this message. The method by which the associated business message has been encrypted. Indicator where a true value means the business message is for test purposes only. The network address of the system to which the business message is intended to be delivered. An address to which a copy of the business message should be sent for information only. The path the business message has taken to travel from the originatorAddress to the recipientAddress. Indicates that the business message may be a repeat of a message sent previously. A unique locator for a participant system. The unique identifier of the network on which this address exists. A unique address for the participant system on the network. The transit of the routing message (and associated business message) from one node to another. Nodes may be either endpoints or hubs. The address of the system beginning this hop. The unique ID assigned to the routing message for this routing hop. The address of the system terminating this hop. The number of this hop in the attempts of the senderAddress to reach the receiverAddress. A collection of routingHops that traces the path of a message being send from the originatorAddress to the recipientAddress. A specific leg of the route between one sender and one receiver. The number of attempts, including this one, for which the sender has tried to reach the receiver. The time at which the sender initiated the route on this attempt. The time at which the receiver received the successful attempt. Only one attempt (the last, successful one) between a given sender and receiver can have a received time stamp.