ietf-smtp
[Top] [All Lists]

[ietf-smtp] [IANA #811598] Last Call: <draft-klensin-smtp-521code-05.txt> (SMTP 521 and 556 Reply Codes) to Proposed Standard

2015-04-01 13:24:46
(BEGIN IANA LAST CALL COMMENTS)

IESG/Authors/WG Chairs:

IANA has reviewed draft-klensin-smtp-521code-05.  Please report any 
inaccuracies and respond to the question below as soon as possible.

IANA's reviewer has the following comments and questions:

QUESTION: In the IANA Considerations section, should "X.10.1" actually be 
"X.1.10," or is the document referring to an entry that will be registered by 
another document?

IANA understands that, upon approval of this document, there is a single action 
which IANA must complete.

In the Enumerated Status Codes subregistry of the Simple Mail Transfer Protocol 
(SMTP) Enhanced Status Codes Registry located at:

https://www.iana.org/assignments/smtp-enhanced-status-codes/

521 will be added to the list of codes associated with the enhanced code entry 
for X.3.2. A reference to [ RFC-to-be ] will be added to this registration.

and

556 will be added to the list of codes associated with the enhanced code entry 
for (X.1.10, or an unregistered X.10.1?). A reference to [ RFC-to-be ] will be 
added to this registration.

As this document requests registrations in an Expert Review or Specification 
Required (see RFC 5226) registry, we will initiate the required Expert Review 
via a separate ticket when we have a response to the question above. 

NOTE: IANA requests that the URL referenced in footnote 3 of the document be 
shortened to:

https://www.iana.org/assignments/smtp-enhanced-status-codes/

The actions requested in this document will not be completed until the document 
has been approved for publication as an RFC. This message is only to confirm 
what actions will be performed.  

Thanks,

Amanda Baber
IANA Request Specialist
ICANN

(END IANA LAST CALL COMMENTS)



On Thu Mar 05 20:03:04 2015, iesg-secretary(_at_)ietf(_dot_)org wrote:

The IESG has received a request from an individual submitter to consider
the following document:
- 'SMTP 521 and 556 Reply Codes'
  <draft-klensin-smtp-521code-05.txt> as Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action. Please send substantive comments to the
ietf(_at_)ietf(_dot_)org mailing lists by 2015-04-02. Exceptionally, comments 
may be
sent to iesg(_at_)ietf(_dot_)org instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.

Abstract


   This memo defines two Simple Mail Transfer Protocol (SMTP) reply
   codes, 521 and 556.  The 521 code was originally described in an
   Experimental RFC in 1995 and is in wide use, but has not previously
   been formally incorporated into SMTP.  The 556 code was created for
   RFC-nullMX.  These codes are used to indicate that an Internet host
   does not accept incoming mail at all (not just under particular
   circumstances).




The file can be obtained via
http://datatracker.ietf.org/doc/draft-klensin-smtp-521code/

IESG discussion can be tracked via
http://datatracker.ietf.org/doc/draft-klensin-smtp-521code/ballot/


No IPR declarations have been submitted directly on this I-D.





_______________________________________________
ietf-smtp mailing list
ietf-smtp(_at_)ietf(_dot_)org
https://www.ietf.org/mailman/listinfo/ietf-smtp

<Prev in Thread] Current Thread [Next in Thread>
  • [ietf-smtp] [IANA #811598] Last Call: <draft-klensin-smtp-521code-05.txt> (SMTP 521 and 556 Reply Codes) to Proposed Standard, Amanda Baber via RT <=