idnits 2.17.00 (12 Aug 2021) /tmp/idnits55101/draft-learmonth-hackerspace-header-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- == 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 separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. ** 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 90: '...kerspace: header MAY be added to Inter...' RFC 2119 keyword, line 91: '...ckerspace. MUAs MAY optionally only a...' Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (August 11, 2014) is 2840 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) ** Obsolete normative reference: RFC 1036 (Obsoleted by RFC 5536, RFC 5537) ** Downref: Normative reference to an Informational RFC: RFC 2076 ** Obsolete normative reference: RFC 2616 (Obsoleted by RFC 7230, RFC 7231, RFC 7232, RFC 7233, RFC 7234, RFC 7235) Summary: 5 errors (**), 0 flaws (~~), 2 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group I. Learmonth 3 Internet-Draft Uni. of Aberdeen 4 Expires: February 12, 2015 August 11, 2014 6 An Internet Message Header For Providing Hackerspace Affiliation 7 Information 8 draft-learmonth-hackerspace-header-00 10 Abstract 12 This memo presents a new Internet message header that allows the 13 sender of Internet messages to provide hackerspace affiliation 14 information to the recipients. Recipients of Internet messages can 15 use this header to look up the hackerspace affiliation of the sender 16 of the message. 18 Status of This Memo 20 This Internet-Draft is submitted in full conformance with the 21 provisions of BCP 78 and BCP 79. 23 Internet-Drafts are working documents of the Internet Engineering 24 Task Force (IETF). Note that other groups may also distribute 25 working documents as Internet-Drafts. The list of current Internet- 26 Drafts is at http://datatracker.ietf.org/drafts/current/. 28 Internet-Drafts are draft documents valid for a maximum of six months 29 and may be updated, replaced, or obsoleted by other documents at any 30 time. It is inappropriate to use Internet-Drafts as reference 31 material or to cite them other than as "work in progress." 33 This Internet-Draft will expire on February 12, 2015. 35 Copyright Notice 37 Copyright (c) 2014 IETF Trust and the persons identified as the 38 document authors. All rights reserved. 40 This document is subject to BCP 78 and the IETF Trust's Legal 41 Provisions Relating to IETF Documents 42 (http://trustee.ietf.org/license-info) in effect on the date of 43 publication of this document. Please review these documents 44 carefully, as they describe your rights and restrictions with respect 45 to this document. Code Components extracted from this document must 46 include Simplified BSD License text as described in Section 4.e of 47 the Trust Legal Provisions and are provided without warranty as 48 described in the Simplified BSD License. 50 1. Introduction 52 A hackerspace is a community-operated workspace where people with 53 common interests, often in computers, machining, technology, science, 54 digital art or electronic art, can meet, socialize and/or 55 collaborate. Hackerspaces, like a lot of other Internet communities, 56 perform a lot of their communication on Internet mailing lists. Some 57 hackers may subscribe to the mailing lists of other hackerspaces, or 58 communicate on Internet mailing lists for discussion between 59 hackerspaces on a regional, national or global level. It can be 60 helpful for hackers to identify to which hackerspace other hackers 61 they are communicating with are affiliated. 63 [RFC1036] defines an Organization: header which contains "a short 64 phrase describing the organization to which the sender belongs". 65 [RFC2076] notes that this header was never standardised for use in 66 e-mail but only in USENET messages. Some MUAs still have implemented 67 this header however. 69 If the Organization: header were to be used, it would be more 70 suitable for it to contain a reference to the sender's employer or 71 school than the sender's hackerspace. The header's text is also 72 unstructured and does not lean itself to being read by machines. 74 This memo presents a new Internet message header that allows the 75 sender of Internet messages to provide hackerspace affiliation 76 information to the recipients of the message in a machine-readable 77 format. 79 2. Hackerspace: header 81 The header's text is built from the name of the hackerspace and the 82 URL of the hackerspace's home page as described below. 84 hackerspace = "Hackerspace" ":" SP space-name SP "<" space-url ">" 85 space-name = string 86 space-url = http_URL 88 http_URL is defined in [RFC2616]. 90 The Hackerspace: header MAY be added to Internet messages by those 91 affiliated with a hackerspace. MUAs MAY optionally only add the 92 header when sending messages to hackerspace-related recipients. 94 3. IANA Considerations 96 A new entry is requested in the Permanent Message Header Field Names 97 [TO BE REMOVED: This registry can be found at: http://www.iana.org/ 98 assignments/message-headers/message-headers.xhtml] registry 99 maintained by IANA. The header field name requested is "Hackerspace" 100 and it is applicable to the protocol "mail". 102 4. Security Considerations 104 Privacy issues may arise as, being a header, most encryption schemes 105 for Internet mail will not encrypt the text. 107 When a message is recieved with a Hackerspace: header, it should not 108 be implicitly trusted as it may have been incorrectly defined by the 109 sender. 111 5. References 113 [RFC1036] Horton, M. and R. Adams, "Standard for interchange of 114 USENET messages", RFC 1036, December 1987. 116 [RFC2076] Palme, J., "Common Internet Message Headers", RFC 2076, 117 February 1997. 119 [RFC2616] Fielding, R., Gettys, J., Mogul, J., Frystyk, H., 120 Masinter, L., Leach, P., and T. Berners-Lee, "Hypertext 121 Transfer Protocol -- HTTP/1.1", RFC 2616, June 1999. 123 Appendix A. Example usage with mutt 125 The first of the following .muttrc statements will add a Hackerspace: 126 header to outgoing mails showing an affiliation with 57North Hacklab 127 and the second statement will unhide the Hackerspace: header when 128 viewing emails in the mutt pager. 130 my_hdr Hackerspace: 57North Hacklab 131 unignore hackerspace 133 Author's Address 134 Iain R. Learmonth 135 University of Aberdeen 136 School of Engineering 137 Kings College 138 Aberdeen AB24 3UE 139 Scotland 141 Email: irl@fsfe.org