IPP Mail Archive: IPP> TES - sharing binary IPP trace files

IPP> TES - sharing binary IPP trace files

Zehler,Peter (pzehler@channels.mc.xerox.com)
Mon, 15 Dec 1997 12:35:56 PST

All,
For anyone wishing to share a trace of IPP requests and responses A
directory for that purpose has been created on the PWG server under
new_TES. the directory is called "traces". Catchy name eh?
Each file contains a single IPP request or response. The filename will
tie request to response and multiple request/responses into a
"conversation". Carl Kugler has uploaded a couple of files there so you
can see an example. When I get some time I will post an example of an
extended "conversation". If you have any problems uploading the file
send it to me and I will se it gets uploaded.

A catalogue of the files will be maintained. To facilitate this some
conventions:
1) The filename will be CCCCORSS.trc
a) CCCC is a unique "conversation" number. This is a sequence of
numbers and case insensitive characters. The conversation
number does not change through the duration of your trace.
That
is if you are showing an IPP Get_Jobs based on some specific
jobs, the request/responses for the multiple Print_Job and
subsequent
Get_Jobs would all share the same "conversation" number. The
next
three fields in the file name will differentiate the traces.
b) O is the hexadecimal number for the operation. The value can
be
determined by examining the operation field in the IPP request.
c) R is used to indicate a request or response. An 'A' indicates
a
request. A 'B' indicates a response.
d) SS is the sequence number. Each IPP request/response in a
conversation is uniquely sequenced by a monotonically
increasing
number. It does not matter if the number starts at 0 or 1.

2) The following information must be sent to me so I may update the
catalogue:
a. the person posting the trace file
b. contact information for that person(email address)
c. the unique sequence number for the conversation (CCCC)
d. the filenames
e. the name of the operation(s) (O)
f. which are requests and responses (R)
g. the date
h. a comment about the intent of the operation request
or response, such as "submitting a job with fidelity 'false'"
or
"intentional invalid request, expecting a
client-error-bad-request
rejection" or "rejection response of
'client-error-bad-request'".

Pete

__________________________________
Email: pzehler@channels.mc.xerox.com
US Mail: Peter Zehler
Xerox Corp.
800 Phillips Rd.
Webster NY, 14580-9701
Voice: (716) 265-8755
FAX: (716)265-8792
__________________________________
"I always wanted to be somebody,
but I should have been more specific."
Lily Tomlin
__________________________________