This message summarizes the Last Call on draft-yevstifeyev-tn3270-uri (http://tools.ietf.org/id/draft-yevstifeyev-tn3270-uri-13.txt).
Firstly, some statistical information. The Last Call was requested by Peter Saint-Andre on 4 January, 2011 and was announced on 4 January, 2011. The Last Call ends on 1 February, 2011. The LC announcement has been sent out to IETF Discussion, uri-review and [hidden email] mailing lists. A number of comments have been received during the Last Call. The most current version - 13 - I have just uploaded is believed to resolve them. Moreover, a number of improvements have been made to improve the document quality.
Secondly, here is the exhaustive list of differences between the 12 version and 13 version.
Intended status - did not change: Informational;
Title - changed. Was The 'tn3270' Uniform Resource Identifier Scheme and now is The 'tn3270' Uniform Resource Identifier (URI) Scheme. I'm asking Peter to change the write0up in accordance to this.
Abstract - did not change;
Introduction - changed. Added the RFC 2119 boilerplate (now used throughout the document); added the reference to IANA registry; clarified the purpose of the document; some other minor changes.
Scheme definition - changed. Splitted the designated service into Telnet 3270 and Telnet 3270 Enchanted, added the reference to IBM Publication GA23-0059, related to 3270 data stream; added the reference to RFC 3049, related to TN3270E; clarified the URI syntax, as follows. Was:
The 'tn3270' URI takes the following form (given in ABNF, as described in RFC 5234 [RFC5234]): tn3270uri = "tn3270:" hier-part hier-part = "//" authority ["/"] ;the URI takes the form ;<a class="moz-txt-link-freetext" href="tn3270://">tn3270://<user>:<password>@<host>:<port>/ ;that is formally defined via the 'authority' The 'authority' rule is specified in RFC 3986 [RFC3986]. If 'port' (in the 'authority' part) is omitted, it SHALL default to 21. The final character "/" MAY be omitted.
Security Considerations - changed. Clarified why there are no other security considerations for 'tn3270' scheme other than the 'telnet' one has.
IANA Considerations - changed. added the reference to RFC 4395; changed the description of protocol, that uses the scheme in accordance with Section 2; changed the Contact and author to IESG and IETF, respectively.
References - RFC 4395 is now Informative; added the references to RFC 3049, IANA registry and IBM Publication GA23-0059.
Acknowledgments - corrected the typographical mistake in the last name of Alfred Hoenes.
Author's addresses - changed, clarified the address.
Lastly, during the LC the document was reviewed by IANA, GenART and OPS-DIR Review Team. I'm citing their reviews.
IANA understands that, upon approval of this document, there is a single
I am the assigned Gen-ART reviewer for this draft. For background on
The most current version is believed to resolve all the comments received.
No changes are intended to be made up to the end of the LC. This message is to allow the IESG to preliminarily review the doc.
Looking forward for the decision of IESG,
|Free forum by Nabble||Edit this page|