draft-ietf-sigtran-mdtp-01.txt   draft-ietf-sigtran-mdtp-02.txt 
Network Working Group R. R. Stewart Network Working Group R. R. Stewart
INTERNET-DRAFT Motorola INTERNET-DRAFT Motorola
Q. Xie Q. Xie
Motorola Motorola
Expires in six months 15 Feburary 1999 Expires in six months 22 March 1999
MULTI_NETWORK DATAGRAM TRANSMISSION PROTOCOL MULTI_NETWORK DATAGRAM TRANSMISSION PROTOCOL
<draft-sigtran-mdtp-01.txt> <draft-ietf-sigtran-mdtp-02.txt>
Status of This Memo Status of This Memo
This document is an Internet-Draft and is in full conformance This document is an Internet-Draft and is in full conformance
with all provisions of Section 10 of RFC2026. Internet-Drafts are working with all provisions of Section 10 of RFC2026. Internet-Drafts are working
documents of the Internet Engineering Task Force (IETF), its areas, documents of the Internet Engineering Task Force (IETF), its areas,
and its working groups. Note that other groups may also distribute and its working groups. Note that other groups may also distribute
working documents as Internet-Drafts. working documents as Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
skipping to change at page 10, line ? skipping to change at page 10, line ?
communication with this endpoint in reliable mode. communication with this endpoint in reliable mode.
In normal data transfer (after the initiate sequence) this In normal data transfer (after the initiate sequence) this
bit should be set to 0, except when responding to a RTT Ack bit should be set to 0, except when responding to a RTT Ack
request. request.
NOB - No Bundling. This bit is used in negotiation and NOB - No Bundling. This bit is used in negotiation and
is set to indicate that the sender does not wish to perform of is set to indicate that the sender does not wish to perform of
bundling or un-bundling of datagrams. When this bit has been set bundling or un-bundling of datagrams. When this bit has been set
in negotiation, the receiver should prevent its application from in negotiation, the receiver should prevent its application from
putting communication with this endpoint in bundled mode. putting communication with this endpoint in bundled mode.
In normal data transfer (after the initiate sequence) this
bit should be set to 0, except when sending a Heart Beat Ack
at which time this bit must be set to 1.
WIN - Window Up. This bit is set by the sender of this datagram WIN - Window Up. This bit is set by the sender of this datagram
to indicate that the sender needs the receiver to acknowledge on to indicate that the sender needs the receiver to acknowledge on
previously received datagrams before it can send more datagrams. previously received datagrams before it can send more datagrams.
ISB - Is Bundled. This bit is set by the sender to indicate that ISB - Is Bundled. This bit is set by the sender to indicate that
this datagram is bundled. This bit should never be set if during this datagram is bundled. This bit should never be set if during
negotiation either end set the NOB bit. negotiation either end set the NOB bit.
FIR - First Datagram. This flag is set to indicate that this is a FIR - First Datagram. This flag is set to indicate that this is a
skipping to change at page 10, line ? skipping to change at page 10, line ?
either endpoint set the NOG flag during negotiation. either endpoint set the NOG flag during negotiation.
UNR - Unreliable Mode. This bit is set to indicate that UNR - Unreliable Mode. This bit is set to indicate that
unreliable mode is in effect for the sender and the sender does unreliable mode is in effect for the sender and the sender does
not expect an acknowledgement. This bit has special meanings if not expect an acknowledgement. This bit has special meanings if
BRO or SHU bit is set (see above). BRO or SHU bit is set (see above).
Version: 8 bits Version: 8 bits
This field represents the version number of the MDTP This field represents the version number of the MDTP
protocol. It is currently set to 1. protocol. If these bits are set to 1, then the sender does
not support Round Trip Time (RTT) caclulation or Heart
Beat of reliable protcol. If these bits are set to 2 then
this version does support RTT and Heartbeat.
In Queue: 8 bits In Queue: 8 bits
Stewart & Xie [Page 9] Stewart & Xie [Page 9]
This field contains the number of messages the sender has on its This field contains the number of messages the sender has on its
incoming queue, waiting to be read by the application. This gives incoming queue, waiting to be read by the application. This gives
the receiver an indication of the flow control conditions within the receiver an indication of the flow control conditions within
the sender. the sender.
The message header is always followed by the data field. If there is The message header is always followed by the data field. If there is
skipping to change at page 24, line 37 skipping to change at page 24, line 37
received datagrams which have not been acknowledged, and received datagrams which have not been acknowledged, and
2) sending the next datagram with RES bit set in the Flags field. 2) sending the next datagram with RES bit set in the Flags field.
3) A sending endpoint should always reset it sequence counter before 3) A sending endpoint should always reset it sequence counter before
the counter reaches 0x7fffffff. When the counter reaches this the counter reaches 0x7fffffff. When the counter reaches this
value the sending endpoint is required to reset its sequence value the sending endpoint is required to reset its sequence
counter. counter.
4) A sending endpoint should never reset its sequence counter until 4) A sending endpoint should never reset its sequence counter until
after reaching 0x7ff05ff. after reaching 0x7fff05ff.
Note: This section will be obsoleted in a future version of the Note: This section will be obsoleted in a future version of the
draft and be replaced by a deterministic rollover algorithm. draft and be replaced by a deterministic rollover algorithm.
The following example illustrates the sequence number reset procedure The following example illustrates the sequence number reset procedure
(assume that Endpoint A opts to do a reset when the data sequence (assume that Endpoint A opts to do a reset when the data sequence
number becomes greater than 0x7fffff000). number becomes greater than 0x7fffff000).
Endpoint A Endpoint Z Endpoint A Endpoint Z
skipping to change at page 27, line 154 skipping to change at page 27, line 154
Part=0,Of=1,Size=100 Part=0,Of=1,Size=100
Seen=401,Send=1 Seen=401,Send=1
{data of 100 octets} {data of 100 octets}
Time-Int1=x Time-Int1=x
Time-Int2=y] Time-Int2=y]
5.10 Heart Beat Ack 5.10 Heart Beat Ack
At request by the application, the user may wish a Heart Beat acknowledgement At request by the application, the user may wish a Heart Beat acknowledgement
sent. The Heart Beat should only be allowed to be enabled if the senders sent. The Heart Beat should only be allowed to be enabled if the senders
Mod is Gar (reliable delivery). Once enabled when no datagrams are being Mod is Gar (reliable delivery) and version is 2. Once enabled when no
datagrams are being
transmitted, a T5-Heart Beat timer should be started. When the transmitted, a T5-Heart Beat timer should be started. When the
T5 timer expires a ACK should be sent using the next available link, following T5 timer expires a ACK should be sent using the next available link, following
the link rotation procedure outlined in "4.5 Link Rotation". After sending the link rotation procedure outlined in "4.5 Link Rotation". After sending
the Ack another T5-Heart Beat timer should be started. If, before the the Ack another T5-Heart Beat timer should be started. If, before the
expiration of T5-Heart Beat, a datagram is transmitted or recieved, the expiration of T5-Heart Beat, a datagram is transmitted or recieved, the
T5 timer should be stopped and the appropriate T2-T4 timer should be started. T5 timer should be stopped and the appropriate T2-T4 timer should be started.
The T5 timer has the lowest precedence of all timers. The T5 timer has the lowest precedence of all timers.
When sending a Heart Beat Ack, the format should be identical to that of When sending a Heart Beat Ack, the format should be that of a RTT time test.
a standard ACK with the exception that the NOB bit should be set. The reciever This will require the reciever to respond on the network. If the sender
should use the case of the NOB bit being set to NOT calculate any changes does not get a response on the network the heartbeat arrived on by the
to its sending window, but still treat the value has a ACK freeing up time a next heartbeat is to be sent, then the network that the last
window space if applicable. heartbeat was sent upon should be counted as a transmission failure has
described in section "5.5 Retransmission on Multiple Networks", and
should counted against the 'retran.count' and protocol parameter 'Max.Retransmit'.
6. Unreliable Transfer Mode 6. Unreliable Transfer Mode
The unreliable transfer mode allows two endpoints to send to each The unreliable transfer mode allows two endpoints to send to each
other without acknowledging the receiving. This can usually achieve other without acknowledging the receiving. This can usually achieve
higher data throughput than the reliable transfer mode. To indicate the higher data throughput than the reliable transfer mode. To indicate the
unreliable transfer mode the sender of a datagram simply sets the UNR unreliable transfer mode the sender of a datagram simply sets the UNR
in the mode field. The following sequence illustrates unreliable data in the mode field. The following sequence illustrates unreliable data
transfer. transfer.
 End of changes. 

This html diff was produced by rfcdiff 1.23, available from http://www.levkowetz.com/ietf/tools/rfcdiff/