<?xml version='1.0'?>
<!DOCTYPE rfc SYSTEM 'rfc2629.dtd'>
<rfc ipr='trust200902' docName='draft-learmonth-hackerspace-header-00'>
   <front>
       <title abbrev="Hackerspace: Internet Message Header">An Internet Message Header For Providing Hackerspace Affiliation Information</title>
       <author initials="I. R." surname="Learmonth" fullname="Iain R. Learmonth">
	       <organization abbrev="Uni. of Aberdeen">University of Aberdeen</organization><address>
         <postal>
   	   <street>School of Engineering</street>
   	   <street>Kings College</street>
   	   <city>Aberdeen</city>
   	   <code>AB24 3UE</code>
           <country>Scotland</country>
         </postal>
	 <email>irl@fsfe.org</email></address>
       </author> 
       <date month="August" year="2014" />
       <area>General</area>
       <abstract><t>This memo presents a new Internet message header that allows the sender
		       of Internet messages to provide hackerspace affiliation
		       information to the recipients. Recipients of Internet messages can use
                       this header to look up the hackerspace affiliation of the sender
                       of the message.</t></abstract>
   </front>
   <middle>
	   <section title="Introduction"><t>A hackerspace is a community-operated workspace where people with common interests, often in computers, machining, technology, science, digital art or electronic art, can meet, socialize and/or collaborate. Hackerspaces, like a lot of other Internet communities, perform a lot of their communication on Internet mailing lists. Some hackers may subscribe to the mailing lists of other hackerspaces, or communicate on Internet mailing lists for discussion between hackerspaces on a regional, national or global level. It can be helpful for hackers to identify to which hackerspace other hackers they are communicating with are affiliated.</t>
		   <t><xref target="RFC1036" /> defines an Organization: header which contains "a short phrase describing the organization to which the sender belongs". <xref target="RFC2076" /> notes that this header was never standardised for use in e-mail but only in USENET messages. Some MUAs still have implemented this header however.</t>
		   <t>If the Organization: header were to be used, it would be more suitable for it to contain a reference to the sender's employer or school than the sender's hackerspace. The header's text is also unstructured and does not lean itself to being read by machines.</t>
		   <t>This memo presents a new Internet message header that allows the sender of Internet messages to provide hackerspace affiliation information to the recipients of the message in a machine-readable format.</t>
	   </section>
	   <section title="Hackerspace: header">
	   <t>The header's text is built from the name of the hackerspace and the URL of the hackerspace's home page as described below.</t>
<figure>
<artwork>
hackerspace = "Hackerspace" ":" SP space-name SP "&lt;" space-url "&gt;"
space-name = string
space-url = http_URL
</artwork>
</figure>
<t>http_URL is defined in <xref target="RFC2616" />.</t>
<t>The Hackerspace: header MAY be added to Internet messages by those affiliated with a hackerspace. MUAs MAY optionally only add the header when sending messages to hackerspace-related recipients.</t>
	   </section>
	   <section title="IANA Considerations">
		   <t>A new entry is requested in the Permanent Message Header Field Names [TO BE REMOVED: This registry can be found at: http://www.iana.org/assignments/message-headers/message-headers.xhtml] registry maintained by IANA. The header field name requested is "Hackerspace" and it is applicable to the protocol "mail".</t>
	   </section>
	   <section title="Security Considerations">
		   <t>Privacy issues may arise as, being a header, most encryption schemes for Internet mail will not encrypt the text.</t>
		   <t>When a message is recieved with a Hackerspace: header, it should not be implicitly trusted as it may have been incorrectly defined by the sender.</t>
	   </section>
   </middle>
   <back>
	   <references>
		   <reference anchor='RFC1036'>
			   <front>
				   <title abbrev='Standard for USENET Messages'>Standard for interchange of USENET messages</title>
				   <author initials='M.' surname='Horton' fullname='M. Horton'>
					   <organization>AT&amp;T Bell Laboratories</organization></author>
				   <author initials='R.' surname='Adams' fullname='R. Adams'>
					   <organization>Center for Seismic Studies</organization></author>
				   <date year='1987' day='1' month='December' /></front>

			   <seriesInfo name='RFC' value='1036' />
			   <format type='TXT' octets='46891' target='http://www.rfc-editor.org/rfc/rfc1036.txt' />
		   </reference>
		   <reference anchor='RFC2076'>

			   <front>
				   <title abbrev='Internet Message Headers'>Common Internet Message Headers</title>
				   <author initials='J.' surname='Palme' fullname='Jacob Palme'>
					   <organization>Stockholm University/KTH</organization>
					   <address>
						   <postal>
							   <street>Electrum 230</street>
							   <street>S-164 40 Kista</street>
							   <country>SE</country></postal>
						   <phone>+46 8 161667</phone>
						   <facsimile>+46 8 7830829</facsimile>
						   <email>jpalme@dsv.su.se</email></address></author>
				   <date year='1997' month='February' />
				   <abstract>
					   <t>This memo contains a table of commonly occurring headers in headings of e-mail messages. The document compiles information from other RFCs such as RFC 822, RFC 1036, RFC 1123, RFC 1327, RFC 1496, RFC 1521, RFC 1766, RFC 1806, RFC 1864 and RFC 1911. A few commonly occurring headers which are not defined in RFCs are also included. For each header, the memo gives a short description and a reference to the RFC in which the header is defined.</t></abstract></front>

			   <seriesInfo name='RFC' value='2076' />
			   <format type='TXT' octets='47639' target='http://www.rfc-editor.org/rfc/rfc2076.txt' />
		   </reference>
		   <reference anchor='RFC2616'>

			   <front>
				   <title abbrev='HTTP/1.1'>Hypertext Transfer Protocol -- HTTP/1.1</title>
				   <author initials='R.' surname='Fielding' fullname='Roy T. Fielding'>
					   <organization abbrev='UC Irvine'>Department of Information and Computer Science</organization>
					   <address>
						   <postal>
							   <street>University of California, Irvine</street>
							   <city>Irvine</city>
							   <region>CA</region>
							   <code>92697-3425</code></postal>
						   <facsimile>+1(949)824-1715</facsimile>
						   <email>fielding@ics.uci.edu</email></address></author>
				   <author initials='J.' surname='Gettys' fullname='James Gettys'>
					   <organization abbrev='Compaq/W3C'>World Wide Web Consortium</organization>
					   <address>
						   <postal>
							   <street>MIT Laboratory for Computer Science, NE43-356</street>
							   <street>545 Technology Square</street>
							   <city>Cambridge</city>
							   <region>MA</region>
							   <code>02139</code></postal>
						   <facsimile>+1(617)258-8682</facsimile>
						   <email>jg@w3.org</email></address></author>
				   <author initials='J.' surname='Mogul' fullname='Jeffrey C. Mogul'>
					   <organization abbrev='Compaq'>Compaq Computer Corporation</organization>
					   <address>
						   <postal>
							   <street>Western Research Laboratory</street>
							   <street>250 University Avenue</street>
							   <city>Palo Alto</city>
							   <region>CA</region>
							   <code>94305</code></postal>
						   <email>mogul@wrl.dec.com</email></address></author>
				   <author initials='H.' surname='Frystyk' fullname='Henrik Frystyk Nielsen'>
					   <organization abbrev='W3C/MIT'>World Wide Web Consortium</organization>
					   <address>
						   <postal>
							   <street>MIT Laboratory for Computer Science, NE43-356</street>
							   <street>545 Technology Square</street>
							   <city>Cambridge</city>
							   <region>MA</region>
							   <code>02139</code></postal>
						   <facsimile>+1(617)258-8682</facsimile>
						   <email>frystyk@w3.org</email></address></author>
				   <author initials='L.' surname='Masinter' fullname='Larry Masinter'>
					   <organization abbrev='Xerox'>Xerox Corporation</organization>
					   <address>
						   <postal>
							   <street>MIT Laboratory for Computer Science, NE43-356</street>
							   <street>3333 Coyote Hill Road</street>
							   <city>Palo Alto</city>
							   <region>CA</region>
							   <code>94034</code></postal>
						   <email>masinter@parc.xerox.com</email></address></author>
				   <author initials='P.' surname='Leach' fullname='Paul J. Leach'>
					   <organization abbrev='Microsoft'>Microsoft Corporation</organization>
					   <address>
						   <postal>
							   <street>1 Microsoft Way</street>
							   <city>Redmond</city>
							   <region>WA</region>
							   <code>98052</code></postal>
						   <email>paulle@microsoft.com</email></address></author>
				   <author initials='T.' surname='Berners-Lee' fullname='Tim Berners-Lee'>
					   <organization abbrev='W3C/MIT'>World Wide Web Consortium</organization>
					   <address>
						   <postal>
							   <street>MIT Laboratory for Computer Science, NE43-356</street>
							   <street>545 Technology Square</street>
							   <city>Cambridge</city>
							   <region>MA</region>
							   <code>02139</code></postal>
						   <facsimile>+1(617)258-8682</facsimile>
						   <email>timbl@w3.org</email></address></author>
				   <date year='1999' month='June' />
				   <abstract>
					   <t>
						      The Hypertext Transfer Protocol (HTTP) is an application-level
						         protocol for distributed, collaborative, hypermedia information
							    systems. It is a generic, stateless, protocol which can be used for
							       many tasks beyond its use for hypertext, such as name servers and
							          distributed object management systems, through extension of its
								     request methods, error codes and headers . A feature of HTTP is
								        the typing and negotiation of data representation, allowing systems
									   to be built independently of the data being transferred.
								   </t>
								   <t>
									      HTTP has been in use by the World-Wide Web global information
									         initiative since 1990. This specification defines the protocol
										    referred to as "HTTP/1.1", and is an update to RFC 2068 .
							    </t></abstract></front>

							    <seriesInfo name='RFC' value='2616' />
							    <format type='TXT' octets='422317' target='http://www.rfc-editor.org/rfc/rfc2616.txt' />
							    <format type='PS' octets='5529857' target='http://www.rfc-editor.org/rfc/rfc2616.ps' />
							    <format type='PDF' octets='550558' target='http://www.rfc-editor.org/rfc/rfc2616.pdf' />
							    <format type='HTML' octets='637302' target='http://xml.resource.org/public/rfc/html/rfc2616.html' />
							    <format type='XML' octets='493420' target='http://xml.resource.org/public/rfc/xml/rfc2616.xml' />
						    </reference>

					    </references>
					    <section title="Example usage with mutt">
						    <t>The first of the following .muttrc statements will add a Hackerspace: header to outgoing mails showing an affiliation with 57North Hacklab and the second statement will unhide the Hackerspace: header when viewing emails in the mutt pager.</t>
<figure>
	<artwork>
my_hdr Hackerspace: 57North Hacklab &lt;http://57north.co/&gt;
unignore hackerspace
</artwork>
</figure>
</section>
   </back>
</rfc>
