[Docs] [txt|pdf] [Tracker] [Email] [Diff1] [Diff2] [Nits]

Versions: 00 01 02 03 04 05 06 07 08 09 RFC 7194

Internet Draft                                          Richard Hartmann
Independent Submission
Intended status: Experimental
Expires: April 4, 2011
Updates: 1459, 2810, 2811, 2812, 2813
                                                         October 7, 2010

                    Default Port for IRC via TLS/SSL
         draft-hartmann-default-port-for-irc-via-tls-ssl-04.txt

Status of this Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF). Note that other groups may also distribute working
   documents as Internet-Drafts. The list of current Internet-Drafts is
   at http://datatracker.ietf.org/drafts/current.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time. It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

Copyright Notice

   Copyright (c) 2010 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://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.

Comments

   Comments are solicited and should be addressed to the author at
   richih.mailinglist@gmail.com.







Hartmann                                                        [Page 1]

Internet Draft      Default Port for IRC via TLS/SSL     October 7, 2010


Abstract

   This document describes the established best industry practice of
   listening on TCP port 6697 for incoming IRC connections encrypted via
   TLS/SSL.

   This document does not try to limit the use of lesser-used ports like
   7000 and 9999.

Table of Contents

   1. Rationale .....................................................  3
   2. Technical Details .............................................  3
   3. Security Considerations .......................................  3
   4. IANA Considerations ...........................................  3
   5. APPENDIX A: Supporting data ...................................  4
   5. Informative References ........................................  4
   6. Acknowledgements ..............................................  5

































Hartmann                                                        [Page 2]

Internet Draft      Default Port for IRC via TLS/SSL     October 7, 2010


1. Rationale

   Although system port assignments for both plain text (TCP port 194)
   and TLS/SSL encrypted (TCP port 994) IRC traffic exist [IANALIST], it
   is common practice amongst IRC networks not to use them for reasons
   of convenience and general availability on systems where no root
   access is granted or desired.

   IRC networks have defaulted to listening on TCP port 6667 for plain
   text connections for considerable time, now.  This is covered by the
   IRCU assignment of TCP/UDP ports 6665-6669.

   Similar consensus has been reached within the IRC community about
   listening on TCP port 6697 for incoming IRC connections encrypted via
   TLS/SSL.

2. Technical Details

   An IRC client connects to an IRC server.  Immediately after that, a
   normal TLS/SSL handshake takes place.  Once this connection has been
   established, a normal IRC connection is established via the tunnel.
   Optionally, the IRC server may set a specific umode for the client,
   marking it as using TLS/SSL.  Again optionally, an IRC server might
   offer the option to create channels in such a way that only clients
   connected via TLS/SSL may join.

3. Security Considerations

   The lack of a common, well established listening port for IRC via
   TLS/SSL could lead to end users being unaware of their IRC network of
   choice supporting TLS/SSL.  Thus, they might not use it even if they
   wanted to.

   It should be noted that this document merely describes client-to-
   server encryption.  There are still other attack vectors like mali-
   cious administrators, compromised servers, insecure server-to-server
   communication, channels that do not enforce encryption for all chan-
   nel members, malicious clients or comprised client machines on which
   logs are stored.

   Those attacks can not be addressed by client-to-server encryption.
   Additional safe-guards are needed if a user suspects any of the
   threats above.

4. IANA Considerations

   An assignment of TCP port 6697 for IRC via TLS/SSL will be requested.




Hartmann                                                        [Page 3]

Internet Draft      Default Port for IRC via TLS/SSL     October 7, 2010


5. APPENDIX A: Supporting data

   As of September 2010, out of the top twenty IRC networks
   [TOP100],[MAVERICK], ten support TLS/SSL.  Only one of those networks
   does not support TLS/SSL via port 6697 and has no plans to support
   it.  All others supported it already or are supporting it since being
   contacted by the author.  A more detailed analysis is available but
   does not fit within the scope of this document.


5. Informative References

   [IANALIST] http://www.iana.org/assignments/port-numbers , Sep 15,
              2010

   [TOP100] http://irc.netsplit.de/networks/top100.php , Sep 15, 2010

   [MAVERICK] http://irc.netsplit.de/networks/lists.php?query=maverick ,
              Sep 27, 2010
































Hartmann                                                        [Page 4]

Internet Draft      Default Port for IRC via TLS/SSL     October 7, 2010


6. Acknowledgements

   Thanks go to the IRC community at large for reaching a consensus.

   Special thanks go to the IRC operators who were eager to support port
   6697 on their respective networks.

Authors' Address

   Richard Hartmann
   Munich
   Germany
   Email: richih.mailinglist@gmail.com
   http://richardhartmann.de

Full Copyright Statement

   ALL DOCUMENTS AND THE INFORMATION CONTAINED THEREIN
   ARE PROVIDED ON AN "AS IS" BASIS AND THE CONTRIBUTOR, THE
   ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE
   INTERNET SOCIETY, THE IETF TRUST AND THE INTERNET ENGINEERING TASK
   FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT
   LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION THEREIN
   WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
   MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

   The IETF Trust takes no position regarding the validity or scope of
   any Intellectual Property Rights or other rights that might be
   claimed to pertain to the implementation or use of the technology
   described in any IETF Document or the extent to which any license
   under such rights might or might not be available; nor does it
   represent that it has made any independent effort to identify any
   such rights.

   Copies of Intellectual Property disclosures made to the IETF
   Secretariat and any assurances of licenses to be made available, or
   the result of an attempt made to obtain a general license or
   permission for the use of such proprietary rights by implementers
   or users of this specification can be obtained from the IETF
   on-line IPR repository at http://www.ietf.org/ipr.

   The IETF invites any interested party to bring to its attention any
   copyrights, patents or patent applications, or other proprietary
   rights that may cover technology that may be required to implement
   any standard or specification contained in an IETF Document. Please
   address the information to the IETF at ietf-ipr@ietf.org.

   The definitive version of an IETF Document is that published by, or



Hartmann                                                        [Page 5]

Internet Draft      Default Port for IRC via TLS/SSL     October 7, 2010


   under the auspices of, the IETF. Versions of IETF Documents that are
   published by third parties, including those that are translated into
   other languages, should not be considered to be definitive versions
   of IETF Documents. The definitive version of these Legal Provisions
   is that published by, or under the auspices of, the IETF. Versions of
   these Legal Provisions that are published by third parties, including
   those that are translated into other languages, should not be
   considered to be definitive versions of these Legal Provisions.

   For the avoidance of doubt, each Contributor to the IETF Standards
   Process licenses each Contribution that he or she makes as part of
   the IETF Standards Process to the IETF Trust pursuant to the
   provisions of RFC 5378. No language to the contrary, or terms,
   conditions or rights that differ from or are inconsistent with the
   rights and licenses granted under RFC 5378, shall have any effect
   and shall be null and void, whether published or posted by such
   Contributor, or included with or in such Contribution.


Version History

   00 - initial version

   01 - fixed [MAVERICK]

   02 - removed self-reference as RFC
        added reference to [RFC1700]

   03 - removed reference to RFC 1700 as per RFC 3232

   04 - added section "Technical Details"
        expanded section "Security Considerations"
        Changed "Intended status" to "Experimental" at RFC authors'
          suggestion

















Hartmann                                                        [Page 6]


Html markup produced by rfcmarkup 1.109, available from https://tools.ietf.org/tools/rfcmarkup/