[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: comments on new drafts
- To: "Mark Lottor" <mkl@xxxxxx>
- Subject: Re: comments on new drafts
- From: Dave Crocker <dcrocker@xxxxxxxxxxxxxxxxxxx>
- Date: Tue, 15 Sep 92 09:14:19 -0700
- Cc: ietf-smtp@xxxxxxxxxxxxxxxxxx
- In-reply-to: Your message of Tue, 15 Sep 92 00:53:12 -0800. <>
- Org: The Branch Office, Sunnyvale CA
- Phone: +1 408 246 8253; fax: +1 408 249 6205
Mark,
You say:
"...allow them to be exchanged reliably! Aren't you really just asking people
to implement SMTP servers that can handle very large messages? The AMSS
command itself certainly doesn't help this happen; in fact it could make
things worse if people put artificially low limits on their servers. Maybe..."
There are a _set_ of issues, here. One of them is the pure reality that
different servers implement different maximums. It seems unrealistic
to assume that we can force everyone to adopt any given size. For
example, this certainly hasn't happened down at the physical
layer or even at the IP layer. Hence, there is benefit in allowing a
receiver to tell a sender what the maximum aceptable frame/packet/message
is.
In general, Admin Max Msg Size looks, to me, very much like the TCP
Max Segment Size construct. It is part of the TCP/IP buffer/flow
management mechanism, but not all of it.
By the way, there appears to be a minor typo in the
spec. The spec name is "administrative maximum message
size" but the acronym is is "amss".
Dave