rfc9422v3.txt | rfc9422.txt | |||
---|---|---|---|---|
skipping to change at line 365 ¶ | skipping to change at line 365 ¶ | |||
EHLO Keyword: LIMITS | EHLO Keyword: LIMITS | |||
Description: Server limits | Description: Server limits | |||
Reference: RFC 9422 | Reference: RFC 9422 | |||
Note: See "SMTP Server Limits" registry. | Note: See "SMTP Server Limits" registry. | |||
7.2. SMTP Server Limits Registry | 7.2. SMTP Server Limits Registry | |||
The IANA has created a new registry in the Mail Parameters group for | The IANA has created a new registry in the "MAIL Parameters" group | |||
SMTP server limits. The policy for this registry is "Specification | for SMTP server limits. The policy for this registry is | |||
Required". Registry entries consist of these required values: | "Specification Required". Registry entries consist of these required | |||
values: | ||||
1. The name of the limit. | 1. The name of the limit. | |||
2. The syntax of the limit value, if the limit has one. This syntax | 2. The syntax of the limit value, if the limit has one. This syntax | |||
MUST conform to the provisions of Section 3 above. In most | MUST conform to the provisions of Section 3 above. In most | |||
cases, the syntax will consist of a keyword designating the limit | cases, the syntax will consist of a keyword designating the limit | |||
type followed by a limit value, using a "name=value" form as | type followed by a limit value, using a "name=value" form as | |||
illustrated by the registrations created by this specification in | illustrated by the registrations created by this specification in | |||
Section 4 above. Use of ABNF [ABNF] is preferred but not | Section 4 above. Use of ABNF [ABNF] is preferred but not | |||
required. If there is no limit value, that should be explicit in | required. If there is no limit value, that should be explicit in | |||
End of changes. 1 change blocks. | ||||
3 lines changed or deleted | 4 lines changed or added | |||
This html diff was produced by rfcdiff 1.48. |