Ident finally published; WG action complete
Stephen D Crocker <crocker@tis.com> Thu, 04 February 1993 18:19 UTC
Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa08148; 4 Feb 93 13:19 EST
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa08144; 4 Feb 93 13:19 EST
Received: from ietf.cnri.reston.va.us by CNRI.Reston.VA.US id aa15188; 4 Feb 93 13:19 EST
Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa08118; 4 Feb 93 13:19 EST
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa08114; 4 Feb 93 13:18 EST
Received: from TIS.COM by CNRI.Reston.VA.US id aa15170; 4 Feb 93 13:18 EST
Received: from TIS.COM by TIS.COM (4.1/SUN-5.64) id AA28274; Thu, 4 Feb 93 13:18:55 EST
Message-Id: <9302041818.AA28274@TIS.COM>
To: ident@CNRI.Reston.VA.US
Cc: crocker@tis.com, iesg@CNRI.Reston.VA.US, iab@isi.edu
Subject: Ident finally published; WG action complete
Date: Thu, 04 Feb 1993 13:18:38 -0500
X-Orig-Sender: ident-request@IETF.CNRI.Reston.VA.US
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Stephen D Crocker <crocker@tis.com>
-----BEGIN PRIVACY-ENHANCED MESSAGE----- Proc-Type: 4,MIC-CLEAR Content-Domain: RFC822 Originator-ID-Asymmetric: MEYxCzAJBgNVBAYTAlVTMSQwIgYDVQQKExtUcnV zdGVkIEluZm9ybWF0aW9uIFN5c3RlbXMxETAPBgNVBAsTCEdsZW53b29k,0F MIC-Info: RSA-MD5,RSA,GenRApvSxzTYu3XS7tmXE9QPsrNYeK12LtSfYmVy5Re HW2f/3Azr8Kse4gzOgVIM+Ou6e4X/4JwDnfCIxnkN4g== Folks, The Ident specification and MIB have finally been published. Slightly abbreviated copies of the RFC announcements are attached. (These were sent to the IETF mailing list.) It took a little longer to publish these RFCs than is usual; apparently there was some editing work to be done to get them into the right format. Although this is fairly simple protocol, it's been an arduous course. I want to thank everyone who has participated, and most particularly Mike St. Johns who has chaired this effort over the last several months. The next step is advancement to Draft Standard, which requires a stable specification, multiple interoperable implementations, and at least six months since advancement to Proposed Standard. If these criteria are met and there aren't any strong issues, it is not necessary for the Working Group to reconvene. If issues do arise, then it usually is necessary for the Working Group to reconvene. At present, it looks like the Working Group has completed its work and we can declare a success. Unless there is a move to the contrary, this brings the Working Group to a close, and I congratulate everyone involved. Steve Crocker Area Director for Security Internet Engineering Task Force - ------- Forwarded Messages To: IETF-Announce:;@IETF.CNRI.Reston.VA.US Subject: RFC1413 on Identification Protocol Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" Date: Wed, 03 Feb 93 14:10:26 PST Sender: ietf-announce-request@IETF.CNRI.Reston.VA.US From: "Joyce K. Reynolds" <jkrey@isi.edu> - - --NextPart A new Request for Comments is now available in online RFC libraries. RFC 1413: Title: Identification Protocol Author: M. St. Johns Mailbox: stjohns@DARPA.MIL Pages: 8 Characters: 16,291 Obsoletes: RFC 931 The Identification Protocol (a.k.a., "ident", a.k.a., "the Ident Protocol") provides a means to determine the identity of a user of a particular TCP connection. Given a TCP port number pair, it returns a character string which identifies the owner of that connection on the server's system. The Identification Protocol was formerly called the Authentication Server Protocol. It has been renamed to better reflect its function. This document is a product of the TCP Client Identity Protocol Working Group of the Internet Engineering Task Force (IETF). This is now a Proposed Standard Protocol. This RFC specifies an IAB standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "IAB Official Protocol Standards" for the standardization state and status of this protocol. Distribution of this memo is unlimited. <Standard material past this point on RFCs deleted for brevity> ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. - - --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" - - --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mail-server@nisc.sri.com" Content-Type: text/plain SEND rfc1413.txt - - --OtherAccess Content-Type: Message/External-body; name="rfc1413.txt"; site="nic.ddn.mil"; access-type="anon-ftp"; directory="rfc" Content-Type: text/plain - - --OtherAccess-- - - --NextPart-- - ------- Message 2 To: IETF-Announce:;@IETF.CNRI.Reston.VA.US Subject: RFC1414 on Identification MIB Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" Date: Wed, 03 Feb 93 14:10:52 PST Sender: ietf-announce-request@IETF.CNRI.Reston.VA.US From: "Joyce K. Reynolds" <jkrey@isi.edu> - - --NextPart A new Request for Comments is now available in online RFC libraries. RFC 1414: Title: Identification MIB Author: M. St. Johns & M. Rose Mailbox: stjohns@DARPA.MIL, mrose@dbc.mtview.ca.us Pages: 7 Characters: 14,165 Updates/Obsoletes: none This memo defines a MIB for use with identifying the users associated with TCP connections. It provides functionality approximately equivalent to that provided by the protocol defined in RFC 1413. This document is a product of the TCP Client Identity Protocol Working Group of the Internet Engineering Task Force (IETF). This is now a Proposed Standard Protocol. This RFC specifies an IAB standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "IAB Official Protocol Standards" for the standardization state and status of this protocol. Distribution of this memo is unlimited. <Standard material past this point on RFCs deleted for brevity> ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. - - --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" - - --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mail-server@nisc.sri.com" Content-Type: text/plain SEND rfc1414.txt - - --OtherAccess Content-Type: Message/External-body; name="rfc1414.txt"; site="nic.ddn.mil"; access-type="anon-ftp"; directory="rfc" Content-Type: text/plain - - --OtherAccess-- - - --NextPart-- - ------- End of Forwarded Messages -----END PRIVACY-ENHANCED MESSAGE-----
- Ident finally published; WG action complete Stephen D Crocker