1.1 --- a/client protocol.txt	
     1.2 +++ b/client protocol.txt	
     1.3 @@ -146,6 +146,14 @@ Some other parameter syntaxes are:
     1.4    targetmask =  "$" 1*( %x01-09 / %x0B-0C / %x0E-1F / %x21-2B / %x2D-FF )
     1.5                    ; syntax of the latter part undefined
     1.6    directedmsg = user [ "%" host ] "@" servername
     1.7 +  isupport   = [ ":" servername SPACE ] "005" SPACE nick SPACE
     1.8 +                        1*13( token SPACE ) ":are supported by this server"
     1.9 +                  ; RPL_ISUPPORT numeric, entire line
    1.10 +  tokens     = 1*13( token SPACE )
    1.11 +  token      = *1"-" isupportparam / isupportparam *1( "=" isupportvalue )
    1.12 +                  ; For RPL_ISUPPORT numeric
    1.13 +  isupportparam = 1*20( letter / digit )
    1.14 +  isupportvalue = *( letter / digit / punct )
    1.15    target     = 1*( letter / digit / special / "-" / "." / "*" / "?")
    1.16                    ; nickname or servername with wildcards (see section 3.4)
    1.17    letter     =  %x41-5A / %x61-7A       ; A-Z / a-z
    1.18 @@ -153,6 +161,7 @@ Some other parameter syntaxes are:
    1.19    hexdigit   =  digit / "A" / "B" / "C" / "D" / "E" / "F"
    1.20    special    =  %x5B-60 / %x7B-7D
    1.21                     ; "[", "]", "\", "`", "_", "^", "{", "|", "}"
    1.22 +  punct      = %d33-47 / %d58-64 / %d91-96 / %d123-126
    1.23  
    1.24  2.4 Numeric replies
    1.25  Most of the messages sent to the server generate a reply of some sort.  The most common reply is the numeric reply, used for both errors and normal replies.  The numeric reply MUST be sent as one message consisting of the sender prefix, the numeric, and the target of the reply.  A numeric reply is not allowed to originate from a client. In all other respects, a numeric reply is just like a normal message, except that the keyword is made up exclusively of digits rather than a string of letters.  A list of different replies is supplied in section 5 (Replies).
    1.26 @@ -1392,7 +1401,7 @@ Numerics in the range from 001 to 099 ar
    1.27    successful registration.
    1.28  
    1.29   005 RPL_ISUPPORT
    1.30 -  "<tokens> :are supported by this server"
    1.31 +  see isupport in BNF
    1.32  
    1.33  - Sent upon successful registration, somewhere after
    1.34    RPL_MYINFO, and possibly when the information changes.
    1.35 @@ -2225,6 +2234,12 @@ This document makes heavy reference to R
    1.36  Craig Edwards
    1.37  Jilles Tjoelker
    1.38  Carsten V. Munk
    1.39 +
    1.40 +Some RPL_ISUPPORT information has been taken from a draft by:
    1.41 +Lee Hardy
    1.42 +Edward Brocklesby
    1.43 +Kevin L. Mitchell
    1.44 +
    1.45  10. References
    1.46  [KEYWORDS]Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997.
    1.47  [ABNF] Crocker, D. and P. Overell, "Augmented BNF for Syntax Specifications: ABNF", RFC 2234, November 1997.