[Emailcore] Ticket #14: G.7.8. Review different size limits

[Todd Herr <[e-mail]>]

Greetings.

I would like to start a discussion about ticket #14 -
https://trac.ietf.org/trac/emailcore/ticket/14

Section 4.5.3.1 of draft-ietf-emailcore-rfc5321bis reads:

4.5.3.1.  Size Limits and Minimums

   There are several objects that have required minimum/maximum sizes.
   Every implementation MUST be able to receive objects of at least
   these sizes.  Objects larger than these sizes SHOULD be avoided when
   possible.  However, some Internet mail constructs such as encoded
   X.400 addresses (RFC 2156 [26]) will often require larger objects.
   Clients MAY attempt to transmit these, but MUST be prepared for a
   server to reject them if they cannot be handled by it.  To the
   maximum extent possible, implementation techniques that impose no
   limits on the length of these objects should be used.
   Extensions to SMTP may involve the use of characters that occupy more
   than a single octet each.  This section therefore specifies lengths
   in octets where absolute lengths, rather than character counts, are
   intended.


and ticket 14 asks the question:

Given the controversy on the SMTP mailing list between 20191123 and now
about maximum lengths, is the above adequate or is further tuning of the
limit text below needed?


draft-ietf-emailcore-rfc5321bis then goes on to specify length limits in
octets, not characters, in each of the following sections:

4.5.3.1.1. Local-part
4.5.3.1.2. Domain
4.5.3.1.3. Path
4.5.3.1.4. Command Line
4.5.3.1.5. Reply Line
4.5.3.1.6. Text Line
4.5.3.1.7. Message Content
4.5.3.1.8. Recipient Buffer


Thoughts?

-- 

*Todd Herr* | Technical Director, Standards and Ecosystem
*e:* [e-mail]
*m:* 703.220.4153

This email and all data transmitted with it contains confidential and/or
proprietary information intended solely for the use of individual(s)
authorized to receive it. If you are not an intended and authorized
recipient you are hereby notified of any use, disclosure, copying or
distribution of the information included in this transmission is prohibited
and may be unlawful. Please immediately notify the sender by replying to
this email and then delete it from your system.