Seven comments on whois++ architecture doc

Rickard Schoultz <> Mon, 02 August 1993 13:03 UTC

Received: from by IETF.CNRI.Reston.VA.US id aa29407; 2 Aug 93 9:03 EDT
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa29401; 2 Aug 93 9:03 EDT
Received: from by CNRI.Reston.VA.US id aa08777; 2 Aug 93 9:03 EDT
Received: by (4.1/UCD2.05) id AA26368; Mon, 2 Aug 93 05:50:03 PDT
Received: from by (4.1/UCD2.05) id AA26322; Mon, 2 Aug 93 05:48:46 PDT
Received: from by (5.61/UCD2.05) id AA21774; Mon, 2 Aug 93 05:43:50 -0700
Received: from by (5.65+bind 1.8+ida 1.4.2/4.0b) id AA21732; Mon, 2 Aug 93 14:44:10 +0200
Message-Id: <>
Subject: Seven comments on whois++ architecture doc
Date: Mon, 02 Aug 1993 14:44:09 +0200
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Rickard Schoultz <>

Hi all,

Here are some collected comments, proposals and questions on the whois++
architecture doc.

1.In the definition of ABRIDGED it says that the template type will be 
  the response:

    An ABRIDGED format response consists of a single set of responses,
    consisting of a single line excerpt of the template information from
    each matching record. The excerpt information shall include, as a
    minimum, the template type and handle of the record, as well as the
    portion of the information that caused the match.

  But the example later says:

    # ABRIDGED 3

     Peter Deutsch (PD45)
     Alan Emtage (AE1)
     World Wide Web (WWW1)     the world

    # END

2.It might also be hard to display the portion of the information that
  caused the match and still having it readable. If there is a mixed type
  of values when you have several matches, the information given in that
  field is probably not very useful(?). Better to have a defined view of
  what you are looking at.

3.It would be a good thing if you could use FORMAT,MAXHITS,IGNORE,INCLUDE
  as both local and global constraint and not restraining it to global

4.If you use HOLD as a global constraint, it should be defined how you 
  quit interaction with the server. Quit/exit/empty line/hold command 
  again or whatever. But it needs to be specified.

5.The START-DATA-TERMINATOR mechanism that is used will have the
  drawback that templates cannot use the name "END" without asking for 
  trouble... I can't see why anyone would do this, but it might be that 
  it should be mentioned in the document.

6.In table IV (required constraints) there is a note that says that 
  searches should be default case sensitive. Typo?

7.The FULL example in the appendix uses template USER. Wouldn't it be
  better to use the (iafa) INDIVIDUAL instead? 
  Just to avoid misinterpretation...