|
1.
|
Clear description of the referenced document:
|
|
|
|
|
2.
|
Status of approval:
|
|
|
Specification approved at 2008-10.
|
|
3.
|
Justification for the specific reference:
|
|
|
The Simple Mail Transfer Protocol (SMTP) Protocol, is needed to allow the HIS Sender to send the ZIP package (created using the HIS Sender – Indirect communication capability class) using email.
|
|
4.
|
Current information, if any, about IPR issues:
|
|
|
Information on IPR issues regarding RFCs is available at: https://datatracker.ietf.org/ipr/search/. Specifically: https://datatracker.ietf.org/ipr/search/?option=rfc_search&rfc_search=5231
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
Specification approved at 2008-10 and many devices implementing this version of the specification exist.
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
Specification approved at 2012-10.
|
|
7.
|
Relationship with other existing or emerging documents:
|
|
|
Specification approved at 2012-10.
|
|
8.
|
Any explicit references within that referenced document should also be listed:
|
|
|
[1] Postel, J., "Simple Mail Transfer Protocol", STD 10, RFC 821,August 1982./
[2] Mockapetris, P., "Domain names - implementation and specification", STD 13, RFC 1035, November 1987./
[3] Braden, R., "Requirements for Internet Hosts - Application and Support", STD 3, RFC 1123, October 1989./
[4] Resnick, P., "Internet Message Format", RFC 5322, October 2008./
[5] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997./
[6] American National Standards Institute (formerly United States of America Standards Institute), "USA Code for Information Interchange", ANSI X3.4-1968, 1968./
[7] Crocker, D. and P. Overell, "Augmented BNF for Syntax Specifications: ABNF", STD 68, RFC 5234, January 2008./
[8] Hinden, R. and S. Deering, "IP Version 6 Addressing Architecture", RFC 4291, February 2006./
[9] Newman, C., "ESMTP and LMTP Transmission Types Registration", RFC 3848, July 2004./
[10] Klensin, J., Freed, N., and K. Moore, "SMTP Service Extension for Message Size Declaration", STD 10, RFC 1870, November 1995./
[11] Klyne, G., Nottingham, M., and J. Mogul, "Registration Procedures for Message Header Fields", BCP 90, RFC 3864,September 2004.
|
|
9.
|
Qualification of
ISOC/IETF:
|
|
|
9.1-9.6 Decisions of ITU Council to admit ISOC to participate in the work of the Sector (June 1995 and June 1996).
9.7 The Internet Engineering Steering Group (IESG) is responsible for ongoing maintenance of the RFCs when the need arises. Comments on RFCs and corresponding changes are accommodated through the existing standardization process.
9.8 Each revision of a given RFC has a different RFC number, so no confusion is possible. All RFCs always remain available on-line. An index of RFCs and their status may be found in the IETF archives at http://www.rfc-editor.org/rfc.html.
|
|
10.
|
Other (for any supplementary information):
|
|
|
None
|
|
