idnits 2.17.1 draft-ietf-aft-username-password-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Cannot find the required boilerplate sections (Copyright, IPR, etc.) in this document. Expected boilerplate is as follows today (2024-04-26) according to https://trustee.ietf.org/license-info : IETF Trust Legal Provisions of 28-dec-2009, Section 6.a: This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 2: Copyright (c) 2024 IETF Trust and the persons identified as the document authors. All rights reserved. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 3: This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** Missing expiration date. The document expiration date should appear on the first and last page. ** The document seems to lack a 1id_guidelines paragraph about Internet-Drafts being working documents. ** The document seems to lack a 1id_guidelines paragraph about 6 months document validity. ** The document seems to lack a 1id_guidelines paragraph about the list of current Internet-Drafts. ** The document seems to lack a 1id_guidelines paragraph about the list of Shadow Directories. == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an Abstract section. ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** There is 1 instance of too long lines in the document, the longest one being 7 characters in excess of 72. ** The document seems to lack a both a reference to RFC 2119 and the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords. RFC 2119 keyword, line 66: '... tus, it MUST close the connection....' Miscellaneous warnings: ---------------------------------------------------------------------------- == The "Author's Address" (or "Authors' Addresses") section title is misspelled. -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- Couldn't find a document date in the document -- date freshness check skipped. Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) No issues found here. Summary: 10 errors (**), 0 flaws (~~), 2 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Username/Password Authentication for SOCKS V5 2 INTERNET-DRAFT 3 Expires: In Six Months M. Leech 4 6 Username/Password Authentication for SOCKS V5 8 Status of this Memo 10 This document is an Internet-Draft. Internet-Drafts are working 11 documents of the Internet Engineering Task Force (IETF), its areas, 12 and its working groups. Note that other groups may also distribute 13 working documents as Internet-Drafts. 15 Internet-Drafts are draft document valid for a maximum of six months 16 and may be updated, replaced or obsoleted by other documents at any 17 time. It is inappropriate to use Internet-Drafts as reference 18 material or to cite them other than as "work in progress". 20 To learn the current status of any Internet-Draft, please check the 21 "1id-abstracts.txt" listing contained in the Internet-Drafts Shadow 22 Directories on ds.internic.net (US East Coast), nic.nordu.net 23 (Europe), ftp.isi.edu (US West Coast), or munnari.oz.au (Pacific 24 Rim). 26 1. Introduction 28 The protocol specification for SOCKS Version 5 specifies a 29 generalized framework for the use of arbitrary authentication 30 protocols in the initial socks connection setup. This document 31 describes one of those protocols, as it fits into the SOCKS Version 5 32 authentication "subnegotiation". 34 2. Initial negotiation 36 Once the SOCKS V5 server has started, and the client has selected the 37 Username/Password Authentication protocol, the Username/Password 38 subnegotiation begins. This begins with the client producing a 39 Username/Password request: 41 +----+------+----------+------+----------+ 42 |VER | ULEN | UNAME | PLEN | PASSWD | 43 +----+------+----------+------+----------+ 44 | 1 | 1 | 1 to 255 | 1 | 1 to 255 | 45 +----+------+----------+------+----------+ 47 The VER field contains the current version of the subne- 48 gotiation, which is X'01'. The ULEN field contains the 49 length of the UNAME field that follows. The UNAME field 50 contains the username as known to the source operating 51 system. The PLEN field contains the length of the PASSWD 52 field that follows. The PASSWD field contains the pass- 53 word association with the given UNAME. 55 The server verifies the supplied UNAME and PASSWD, and 56 sends the following response: 58 +----+--------+ 59 |VER | STATUS | 60 +----+--------+ 61 | 1 | 1 | 62 +----+--------+ 64 A STATUS field of X'00' indicates success. If the server 65 returns a `failure' (STATUS value other than X'00') sta- 66 tus, it MUST close the connection. 68 3. Security Considerations 70 This document describes a subnegotiation that provides 71 authentication services to the SOCKS protocol. Since the 72 request carries the password in cleartext, this subnego- 73 tiation is not recommended for environments where "sniff- 74 ing" is possible and practical 76 4. Authors Address 78 Marcus Leech 79 Bell-Northern Research Ltd 80 P.O. Box 3511, Station C 81 Ottawa, ON 82 CANADA K1Y 4H7 84 +1 613 763 9145 86 Email: mleech@bnr.ca