[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: ipsec error codes
> I think an important point is that reply codes for ftp/smtp are just
> that: *reply* codes. That is, they are sent in response to commands, and
> are meant to facilitate state machine processing. From RFC 959,
>
> Replies to File Transfer Protocol commands are devised to ensure
> the synchronization of requests and actions in the process of file
> transfer, and to guarantee that the user process always knows the
> state of the Server. Every command must generate at least one
> reply, although there may be more than one; in the latter case,
> the multiple replies must be easily distinguished. In addition,
> some commands occur in sequential groups, such as USER, PASS and
> ACCT, or RNFR and RNTO. The replies show the existence of an
> intermediate state if all preceding commands have been successful.
> A failure at any point in the sequence necessitates the repetition
> of the entire sequence from the beginning.
>
> The important point here is that they are defined with particular
> semantic goals, which may or may not encompass the requirements of our
> situation. This brings us to a question: what, exactly, are our
> requirements?
Good question.
At first glance, I don't see what problem is being solved. What on-the-wire
entity would issue these codes and messages?
Dan
Follow-Ups:
References: