RFC 1045:VMTP: VERSATILE MESSAGE TRANSACTION PROTO...
RFC-Ref

security


Click on the red underlined text to get to the source

... VMTP handles the error detection, retransmission, duplicate suppression and, optionally, security required for transport-level end-to-end ...
... In addition, TCP provides no security and reliability guarantees on the dynamically allocated names. In particular, other than well-known ports ...
... multicast, real-time datagrams or security. In fact, it only supports pair-wise, long-term, streamed reliable interchanges. Yet, multicast ...
... transport level is a powerful asset for real-time and parallel applications. Finally, security is a basic requirement in an increasing number of environments. We note that security ...
... security is a basic requirement in an increasing number of environments. We note that security is natural to implement at the transport level to provide end-to-end security ...
... security is natural to implement at the transport level to provide end-to-end security (as opposed to (inter)network level security ...
... end-to-end security (as opposed to (inter)network level security). Without security at the transport level, a ...
... opposed to (inter)network level security). Without security at the transport level, a transport level protocol cannot guarantee the ...
... multicast, real-time datagrams and security, addressing precisely these weaknesses. ...
... , flow control, streaming, real-time, security, byte-ordering and management. Chapter 3 describes the VMTP ...


... address-independent naming with provision for multiple forms of names for endpoints as well as associated (security) principals. (See Sections 2.1, 2.2, 3.1 and Appendix IV ...
... lock conflict between these entities. The principal associated with an entity specifies the permissions, security and accounting designation associated with the entity ...
... VMTP solely to make these values available to VMTP users with the security and efficiency provided by VMTP. Only the entity ...
... represents the same logical communication entity and principal (in the security sense) over the time that it is valid. For example, if an entity ...
... name space. Domains can also serve to separate entities of different security levels. For instance, allocation of a unclassified entity identifier cannot conflict with secret level ...
... than per installation. For example, the Internet is expected to use one domain per security level, resulting in at most 8 different domains. Cluster-based internetwork ...
... only when there is a host-to-host error detection mechanism and the VMTP security facility is not being used. For example, one could rely on the Ethernet CRC ...
... Security ...
... VMTP provides an (optional) secure mode that protects against the usual security threats of peeking, impostoring, message tampering and replays. Secure VMTP must be used to guarantee any of the transport-level ...
... higher level protocol. corresponding security/performance trade-offs. (See Appendix V.) A separate key distribution ...
... and can closely follow the Birrell design as well. Security is optional in the sense that messages may be secure or non-secure, even between consecutive message transactions from the same ...
... fail to communicate with a Server if the Server insists on secure communication and the Client does not implement security or vice versa. However, a failure to communicate in this case is necessary from a security standpoint. ...
... does not implement security or vice versa. However, a failure to communicate in this case is necessary from a security standpoint. ...


... bit is used by higher-level protocols. For instance, servers may take extra security and protection measures with aliases. ...


... if not Multicast(p) then NotifyClient(NULL, p, SECURITY_NOT_SUPPORTED ) return endif ...
... if not Multicast(p) then NotifyClient(NULL,p,SECURITY_NOT_SUPPORTED) return endif ...


... return endif if security required by server then NotifyClient(csr, p, SECURITY_REQUIRED ) ...
... if security required by server then NotifyClient(csr, p, SECURITY_REQUIRED ) return endif ...


... 15 RESPONSE_DISCARDED 16 SECURITY_NOT_SUPPORTED 17 BAD_REPLY_SEGMENT ...
... SEGMENT 18 SECURITY_REQUIRED 19 STREAMED_RESPONSE ...


... known. 4 SECURITY_REQUIRED - Request must be encrypted or else reject. ...
... transactions. SECURITY_NOT_SUPPORTED The Request was secure and this Server does not support security ...
... SECURITY_NOT_SUPPORTED The Request was secure and this Server does not support security. SECURITY ...
... security. SECURITY_REQUIRED The Server is refusing the Request because it was not encrypted ...


... with the Client, if not known. SECURITY_REQUIRED Request must be encrypted or else reject. ...
... The implementation experience to date includes a partial implementation (minus the streaming and full security) in the V kernel plus a similar preliminary implementation in the 4.3 BSD Unix kernel. In the V kernel ...



Google
Web
RFC-Ref