# Re: finger, again

Jared_Rhine@hmc.edu
Mon, 6 Mar 1995 12:45:23 -0500

- Messages sorted by: [ date ][ thread ][ subject ][ author ]
- Next message: Larry Masinter: "URNs don't provide permanence"
- Previous message: Jared_Rhine@hmc.edu: "finger, again"
- Maybe in reply to: Jared_Rhine@hmc.edu: "finger, again"

    Date: Mon, 6 Mar 1995 12:45:23 -0500

    Message-Id: <199503061745.MAA21148@aslan.math.hmc.edu>

    From: Jared_Rhine@hmc.edu

    To: ietf-lists@proper.com (Paul Hoffman)

    Subject: Re: finger, again

PH == Paul Hoffman <ietf-lists@proper.com>

PH> The current (and future) draft says: "Clients should not decode CR and
PH> LF characters in a URL."

This could be interpreted to mean: Do not decode "%0[adAD]" in a request
string. It might be better to say that any request with that string fails,
since otherwise implementors will have to put together a special decoding
routine for just this scheme.

JRhine> Speaking of end-of-lines, does your finger proposal specify how
JRhine> the <request> is terminated?

PH> No, because...

JRhine> Does the finger protocol spec?

PH> Yes, it does: a CRLF.

I haven't read the finger draft in a while. Does it say, "The sending of
the request to the host shall be peformed as per the finger protocol spec"
or does it say, "The client shall send the request string to the host, port
79, in 7-bit ASCII" (basically duplicating the finger spec information). If
implementors require the finger protocol spec to properly implement the
finger scheme spec, that must be made very clear in the finger scheme draft.

    --
    Jared_Rhine@hmc.edu | Harvey Mudd College | http://www.hmc.edu/~jared/home.html

    "Remember, only users lose drugs." -- from Richard Stueven

- Next message: Larry Masinter: "URNs don't provide permanence"
- Previous message: Jared_Rhine@hmc.edu: "finger, again"
- Maybe in reply to: Jared_Rhine@hmc.edu: "finger, again"