RFC 905:ISO Transport Protocol Specification ...
RFC-Ref

requirement


Click on the red underlined text to get to the source

... 1.4 This International Standard also specifies conformance requirements for systems implementing these procedures. It does not contain tests which can be used to demonstrate this conformance. ...


... Transport Layer that is not subject to the requirements of this protocol. ...
... 3.2.16 invalid TPDU: A TPDU that does not comply with the requirements of this International Standard for structure and encoding. ...
... A reference that is not available for assignment to a connection because of the requirements of 6.18. 3.2.26 unassigned reference: ...


... a) select network service which best matches the requirement of the TS-user taking into account charges for various ...
... a) the TS-users' requirements expressed via T-CONNECT service primitives; ...
... network services in terms of quality with respect to error behavior in relation to user requirements; its main purpose is to provide a basis for the decision regarding which class of transport protocol ...


... created, the quality of service requested is a local matter, although it will normally be related to the requirements of transport connection(s) expected to be assigned to it. ...
... there are subsequent DT TPDUs in the sequence. 2. There is no requirement that the DT TPDUs shall be of the maximum length selected during connection establishment. ...
... NOTES 1) This requirement ensures that the transport entity is ...


... The window synchronization procedures (see 12.2.3.8) ensure that this requirement is met. NOTE - It is likely that the release procedure initiated due to ...


... A system claiming to implement the procedures specified in this standard shall comply with the requirements in 14.2 - 14.5. 14.2 ...
... 2) the maximum for which conformance is claimed. NOTE - This requirement indicates that TPDU sizes of 128 octets are always implemented. ...



Google
Web
RFC-Ref