AUTH SSL Message Handling The client can send an AUTH SSL message when used with instead of AUTH TLS. It MUST assume that the server will process it identically to an AUTH TLS message. FEAT Message Handling The handling of a FEAT message on the client is not affected by this protocol. AUTH Message Handling The client SHOULD NOT send AUTH TLS or AUTH SSL messages over the connection. These messages will always be rejected by the server because the implicit AUTH TLS command has already been processed and additional messages sent over the already encrypted session are not allowed. Timer Events None. Other Local Events None. Server Role Details Abstract Data Model No new abstract data model is introduced beyond the existing underlying protocol. Timers None. Initialization To implement the support, the server SHOULD listen on the default port 990, as assigned by IANA. The server MAY choose to listen on a custom port. Higher-Layer Triggered Events None. Message Processing Events and Sequencing Rules Control Connection Negotiation with Implicit FTPS When a client connects to the TCP port dedicated for , the server MUST NOT send the connection greeting message immediately. Instead, the server MUST assume that the AUTH TLS message was sent by the client. The server MUST do internal processing identical to handling an AUTH TLS message without sending a positive reply to the client. The client MUST assume that a positive reply was sent in response to the implicit AUTH TLS message. TLS session negotiation will follow as specified in .
AUTH SSL Message Handling The client can send an AUTH SSL message when used with instead of AUTH TLS. It MUST assume that the server will process it identically to an AUTH TLS message. FEAT Message Handling The handling of a FEAT message on the client is not affected by this protocol. AUTH Message Handling The client SHOULD NOT send AUTH TLS or AUTH SSL messages over the connection. These messages will always be rejected by the server because the implicit AUTH TLS command has already been processed and additional messages sent over the already encrypted session are not allowed. Timer Events None. Other Local Events None. Server Role Details Abstract Data Model No new abstract data model is introduced beyond the existing underlying protocol. Timers None. Initialization To implement the support, the server SHOULD listen on the default port 990, as assigned by IANA. The server MAY choose to listen on a custom port. Higher-Layer Triggered Events None. Message Processing Events and Sequencing Rules Control Connection Negotiation with Implicit FTPS When a client connects to the TCP port dedicated for , the server MUST NOT send the connection greeting message immediately. Instead, the server MUST assume that the AUTH TLS message was sent by the client. The server MUST do internal processing identical to handling an AUTH TLS message without sending a positive reply to the client. The client MUST assume that a positive reply was sent in response to the implicit AUTH TLS message. TLS session negotiation will follow as specified in .
%5BMS-FTPS%5D-170915.docx