Internet Relay Chat: Client-to-Client Protocol (CTCP)
draft-oakley-irc-ctcp-02

Document Type Active Internet-Draft (individual)
Last updated 2018-01-14 (latest revision 2018-01-09)
Stream ISE
Intended RFC status Informational
Formats plain text xml pdf html bibtex
Stream ISE state Finding Reviewers
Consensus Boilerplate Unknown
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                       M. Mikulenas
Internet-Draft                                               Independent
Updates: 1459, 2812 (if approved)                              D. Oakley
Intended status: Informational                                   ircdocs
Expires: July 13, 2018                                  January 09, 2018

         Internet Relay Chat: Client-to-Client Protocol (CTCP)
                        draft-oakley-irc-ctcp-02

Abstract

   This document describes the Client-to-Client Protocol (CTCP), which
   lets Internet Relay Chat (IRC) clients send each other messages that
   get displayed or responded to in special ways.  CTCP has been widely
   implemented, with most clients supporting it natively.  This document
   outlines how to implement CTCP and the most common messages used.

   It updates RFC 1459 and RFC 2812.

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."

   This Internet-Draft will expire on July 13, 2018.

Copyright Notice

   Copyright (c) 2018 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.

Mikulenas & Oakley        Expires July 13, 2018                 [Page 1]
Internet-Draft        IRC Client-to-Client Protocol         January 2018

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Message Syntax  . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Message Types . . . . . . . . . . . . . . . . . . . . . . . .   3
     3.1.  Extended formatting . . . . . . . . . . . . . . . . . . .   4
     3.2.  Metadata Query  . . . . . . . . . . . . . . . . . . . . .   4
     3.3.  Extended Query  . . . . . . . . . . . . . . . . . . . . .   4
   4.  Messages  . . . . . . . . . . . . . . . . . . . . . . . . . .   5
   5.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   5
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   5
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   6
   8.  Normative References  . . . . . . . . . . . . . . . . . . . .   6
   Appendix A.  Message List . . . . . . . . . . . . . . . . . . . .   6
     A.1.  ACTION  . . . . . . . . . . . . . . . . . . . . . . . . .   6
     A.2.  CLIENTINFO  . . . . . . . . . . . . . . . . . . . . . . .   7
     A.3.  DCC . . . . . . . . . . . . . . . . . . . . . . . . . . .   7
     A.4.  FINGER  . . . . . . . . . . . . . . . . . . . . . . . . .   8
     A.5.  PING  . . . . . . . . . . . . . . . . . . . . . . . . . .   8
     A.6.  SOURCE  . . . . . . . . . . . . . . . . . . . . . . . . .   8
     A.7.  TIME  . . . . . . . . . . . . . . . . . . . . . . . . . .   9
     A.8.  VERSION . . . . . . . . . . . . . . . . . . . . . . . . .   9
     A.9.  USERINFO  . . . . . . . . . . . . . . . . . . . . . . . .  10
   Appendix B.  Change History [RFC Editor: Please remove this
                section] . . . . . . . . . . . . . . . . . . . . . .  10
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  10

1.  Introduction

   The core Internet Relay Chat (IRC) protocol as described in [RFC1459]
   and [RFC2812] only has a single command for regular user messages,
   and does not provide a way for clients to exchange information
   directly.  Client-to-Client Protocol (CTCP) messages let clients
   exchange messages that get displayed or responded to in special ways.
   Some examples of how CTCP is used is to request special formatting on
   messages, query other clients for metadata, and help initiate file
   transfers with other clients.

   This document goes over the subset of CTCP which is commonly
   implemented, and is compatible with clients implementing CTCP as
   described by older documents.

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in [RFC2119].

Mikulenas & Oakley        Expires July 13, 2018                 [Page 2]
Internet-Draft        IRC Client-to-Client Protocol         January 2018
Show full document text