IPP Mail Archive: IPP> TES: binary files

IPP> TES: binary files

Carl Kugler (kugler@us.ibm.com)
Mon, 15 Dec 1997 13:34:28 -0700

This is a multi-part message in MIME format.

------=_NextPart_000_0007_01BD095E.420EE490
Content-Type: text/plain;
charset="utf-8"
Content-Transfer-Encoding: quoted-printable

Steve Gebert and I have put up=20

ftp://ftp.pwg.org/pub/pwg/ipp/new_TES/Traces/00012A00.trc

and=20

ftp://ftp.pwg.org/pub/pwg/ipp/new_TES/Traces/00012B00.trc

with Peter's help. These are a Print-Job request and response.

Here is a dump of 00012A00.trc:
50 4F 53 54 20 2F 73 65 72 76 6C 65 74 2F 49 50 POST /se rvlet/IP
50 53 65 72 76 6C 65 74 20 48 54 54 50 2F 31 2E PServlet HTTP/1.
31 0D 0A 48 6F 73 74 3A 20 6C 6F 63 61 6C 68 6F 1..Host: localho
73 74 0D 0A 41 63 63 65 70 74 3A 20 61 70 70 6C st..Acce pt: appl
69 63 61 74 69 6F 6E 2F 69 70 70 20 0D 0A 43 6F ication/ ipp ..Co
6E 74 65 6E 74 2D 74 79 70 65 3A 20 61 70 70 6C ntent-ty pe: appl
69 63 61 74 69 6F 6E 2F 69 70 70 0D 0A 43 6F 6E ication/ ipp..Con
74 65 6E 74 2D 6C 65 6E 67 74 68 3A 20 32 32 34 tent-len gth: 224
0D 0A 0D 0A 01 00 00 02 01 47 00 12 61 74 74 72 ....=E2=98=BA =
=E2=98=BB =E2=98=BAG =E2=86=95attr
69 62 75 74 65 73 2D 63 68 61 72 73 65 74 00 08 ibutes-c harset .
55 53 2D 41 53 43 49 49 48 00 1B 61 74 74 72 69 US-ASCII H =
=E2=86=90attri
62 75 74 65 73 2D 6E 61 74 75 72 61 6C 2D 6C 61 butes-na tural-la
6E 67 75 61 67 65 00 05 65 6E 2D 55 53 42 00 08 nguage =E2=99=A3 =
en-USB .
6A 6F 62 2D 6E 61 6D 65 00 04 6A 6F 62 31 22 00 job-name =
=E2=99=A6job1"
16 69 70 70 2D 61 74 74 72 69 62 75 74 65 2D 66 =E2=96=ACipp-att =
ribute-f
69 64 65 6C 69 74 79 00 01 00 42 00 14 72 65 71 idelity =
=E2=98=BA B =C2=B6req
75 65 73 74 69 6E 67 2D 75 73 65 72 2D 6E 61 6D uesting- user-nam
65 00 05 73 74 65 76 65 42 00 0D 64 6F 63 75 6D e =E2=99=A3steve =
B .docum
65 6E 74 2D 6E 61 6D 65 00 09 64 6F 63 75 6D 65 ent-name .docume
6E 74 31 02 21 00 06 63 6F 70 69 65 73 00 01 01 nt1=E2=98=BB! =
=E2=99=A0c opies =E2=98=BA=E2=98=BA
21 00 0C 6A 6F 62 2D 70 72 69 6F 72 69 74 79 00 ! =E2=99=80job-p =
riority
01 01 42 00 08 4A 6F 62 2D 6E 61 6D 65 00 02 79 =
=E2=98=BA=E2=98=BAB .Job -name =E2=98=BBy
6F 03 31 31 o=E2=99=A511

and here of 00012B00.trc
48 54 54 50 2F 31 2E 30 20 32 30 30 20 4F 4B 0D HTTP/1.0 200 OK.
0A 53 65 72 76 65 72 3A 20 53 65 72 76 6C 65 74 .Server: Servlet
53 65 72 76 65 72 2F 31 2E 30 0D 0A 43 6F 6E 74 Server/1 .0..Cont
65 6E 74 2D 54 79 70 65 3A 20 61 70 70 6C 69 63 ent-Type : applic
61 74 69 6F 6E 2F 69 70 70 0D 0A 44 61 74 65 3A ation/ip p..Date:
20 4D 6F 6E 2C 20 30 38 20 44 65 63 20 31 39 39 Mon, 08 Dec 199
37 20 31 37 3A 35 30 3A 32 38 20 47 4D 54 0D 0A 7 17:50: 28 GMT..
0D 0A 01 00 00 00 02 42 00 08 6A 6F 62 2D 6E 61 ..=E2=98=BA =
=E2=98=BBB .job-na
6D 65 00 04 4A 6F 62 31 42 00 09 6A 6F 62 2D 73 me =E2=99=A6Job1 =
B .job-s
74 61 74 65 00 04 4A 6F 62 31 42 00 00 00 04 4A tate =E2=99=A6Jo =
b1B =E2=99=A6J
6F 62 32 42 00 11 6A 6F 62 2D 73 74 61 74 65 2D ob2B =E2=97=84jo =
b-state-
72 65 61 73 6F 6E 73 00 04 4A 6F 62 31 42 00 11 reasons =
=E2=99=A6Job1B =E2=97=84
6A 6F 62 2D 73 74 61 74 65 2D 6D 65 73 73 61 67 job-stat e-messag
65 00 02 59 4F 05 41 00 05 73 69 64 65 73 00 0B e =
=E2=98=BBYO=E2=99=A3A =E2=99=A3sides =E2=99=82
75 6E 73 75 70 70 6F 72 74 65 64 03 unsuppor =
ted=E2=99=A5

IPP> RE: TES:binary files
Zehler,Peter (pzehler@channels.mc.xerox.com)
Tue, 9 Dec 1997 06:35:41 PST=20

a.. Messages sorted by: [ date ][ thread ][ subject ][ author ]=20
b.. Next message: Jay Martin: "Re: IPP> A free IPP test suite to be =
available!"=20
c.. Previous message: Carl-Uno Manros: "RE: IPP> Re: Area Directors' =
comments on IPP"=20
Steve,
Even when we test across the internet we will still need to capture
the results. I am all for anything that will help us move along.=20
I have created a directory called "Traces" under the new_TES
directory for the time being. We can decide on a directory structure at
a later time. I assume that we will capture traces in more than one
form.=20
We need to decide on a naming convention. For this purpose I assume
that we will limit each trace file to a single request or response. The
naming convention should provide for the pairing of the request to its
response. The naming convention should facilitate the capturing of an
extended IPP conversation. A conversation is a sequence of IPP
operations on an IPP printer.=20
We need to designate the session, operation, request|response, and
sequence in the conversation. A suggestion would be "SSSSOR##.trc"
where
SSSS: an arbitrary unique sequence identifier. The identifier=20
would be unique within the "Traces" directory.
O: The operation of the request/response. This is the=20
hexadecimal value of the IPP operation enum.
R: Designates request or response. A=3Drequest
B=3Dresponse.
##: sequence number of the operation in the IPP conversation.
We will also need to catalogue the contents of the directory. This
can be accomplished by a pdf file containing a table with relevant
information. I can keep this up to date if contributors send me the
information. I think some concise description of the objective/purpose
of the IPP conversation would be appropriate.=20

I found that putting up an IPP emulator through an ISV is trivial. The
emulator is the front end of my IPP printer. I have this anyway since
small printers do not have very rich debug environments.

I think we need to know if there is any interest in pursuing binary
trace files. Do any other individuals have any feelings on this?

What do you think?
Pete
__________________________________=20
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
__________________________________=20
"I always wanted to be somebody,=20
but I should have been more specific."=20
Lily Tomlin
__________________________________=20

> -----Original Message-----
> From: Steve Gebert [SMTP:stevegeb@us.ibm.com]
> Sent: Monday, December 08, 1997 3:39 PM
> To: ipp@pwg.org
> Subject:=20
>=20
> For interoperability testing, we were wondering if people were
> interested in
> exchanging binary files
> corresponding to IPP Requests and Responses. The parties using these
> files
> would simply need to
> construct a simple program to feed the file data into their server
> or client
> and read data from their
> server or client into a file.
>=20
> These files could be sent as email attachments and for the near term
> help
> with interoperability testing
> prior to people setting up machines outside filewalls. Perhaps we
> could even
> catalog the files and
> make them available for download so that there would be a common
> test
> baseline for early testing.
>=20
> We could make some example files available if there is any
> interest. What do
> you think Peter?
>=20
>=20
> Steve Gebert

a.. Next message: Jay Martin: "Re: IPP> A free IPP test suite to be =
available!"=20
b.. Previous message: Carl-Uno Manros: "RE: IPP> Re: Area Directors' =
comments on IPP"=20

------=_NextPart_000_0007_01BD095E.420EE490
Content-Type: text/html;
charset="utf-8"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 HTML//EN">
IPP Mail Archive: IPP> RE: TES:binary = files

Steve Gebert and I have put up =
 
    ftp://= ftp.pwg.org/pub/pwg/ipp/new_TES/Traces/00012A00.trc
 
and
 
    ftp://= ftp.pwg.org/pub/pwg/ipp/new_TES/Traces/00012B00.trc
 
with Peter's help.  These are a Print-Job = request and=20 response.
 
Here is a dump of = 00012A00.trc:
50 4F 53 = 54 20 2F 73=20 65   72 76 6C 65 74 2F 49 50      = POST /se=20 rvlet/IP
50 53 65 72 76 6C 65 74   20 48 54 54 50 2F 31=20 2E      PServlet  HTTP/1.
31 0D 0A 48 = 6F 73 74=20 3A   20 6C 6F 63 61 6C 68 6F     =20 1..Host:  localho
73 74 0D 0A 41 63 63 65   70 74 3A = 20 61 70=20 70 6C      st..Acce pt: appl
69 63 61 74 69 = 6F 6E=20 2F   69 70 70 20 0D 0A 43 6F      = ication/=20 ipp ..Co
6E 74 65 6E 74 2D 74 79   70 65 3A 20 61 70 70=20 6C      ntent-ty pe: appl
69 63 61 74 69 6F = 6E=20 2F   69 70 70 0D 0A 43 6F 6E      = ication/=20 ipp..Con
74 65 6E 74 2D 6C 65 6E   67 74 68 3A 20 32 32=20 34      tent-len gth: 224
0D 0A 0D 0A 01 00 = 00=20 02   01 47 00 12 61 74 74 72      = ....☺ =20 ☻ ☺G ↕attr
69 62 75 74 65 73 2D 63   68 = 61 72 73 65 74 00=20 08      ibutes-c harset .
55 53 2D 41 53 43 = 49=20 49   48 00 1B 61 74 74 72 69      = US-ASCII H=20 ←attri
62 75 74 65 73 2D 6E 61   74 75 72 61 6C 2D 6C=20 61      butes-na tural-la
6E 67 75 61 67 65 = 00=20 05   65 6E 2D 55 53 42 00 08      = nguage=20 ♣ en-USB .
6A 6F 62 2D 6E 61 6D 65   00 04 6A 6F 62 = 31 22=20 00      job-name  ♦job1"
16 = 69 70 70=20 2D 61 74 74   72 69 62 75 74 65 2D = 66     =20 ▬ipp-att ribute-f
69 64 65 6C 69 74 79 00   01 00 42 = 00 14 72 65=20 71      idelity  ☺ B ¶req
75 = 65 73 74 69=20 6E 67 2D   75 73 65 72 2D 6E 61 = 6D     =20 uesting- user-nam
65 00 05 73 74 65 76 65   42 00 0D 64 6F = 63 75=20 6D      e ♣steve B .docum
65 6E 74 2D = 6E 61 6D=20 65   00 09 64 6F 63 75 6D 65     =20 ent-name  .docume
6E 74 31 02 21 00 06 63   6F 70 69 = 65 73 00=20 01 01      nt1☻! ♠c opies = ☺☺
21 00 0C 6A 6F=20 62 2D 70   72 69 6F 72 69 74 79 = 00      !=20 ♀job-p riority
01 01 42 00 08 4A 6F 62   2D 6E 61 6D = 65 00 02=20 79      ☺☺B .Job -name = ☻y
6F 03 31=20 31            = ;            =             &= nbsp;       =20 o♥11
 
 
and here of = 00012B00.trc
48 54 54 = 50 2F 31 2E=20 30   20 32 30 30 20 4F 4B 0D     =20 HTTP/1.0  200 OK.
0A 53 65 72 76 65 72 3A   20 53 65 = 72 76 6C=20 65 74      .Server:  Servlet
53 65 72 = 76 65 72=20 2F 31   2E 30 0D 0A 43 6F 6E 74      = Server/1=20 .0..Cont
65 6E 74 2D 54 79 70 65   3A 20 61 70 70 6C 69=20 63      ent-Type : applic
61 74 69 6F 6E 2F = 69=20 70   70 0D 0A 44 61 74 65 3A      = ation/ip=20 p..Date:
20 4D 6F 6E 2C 20 30 38   20 44 65 63 20 31 39=20 39       Mon, 08  Dec 199
37 20 31 = 37 3A=20 35 30 3A   32 38 20 47 4D 54 0D = 0A      7=20 17:50: 28 GMT..
0D 0A 01 00 00 00 02 42   00 08 6A 6F 62 2D = 6E=20 61      ..☺   ☻B  = .job-na
6D 65 00 04=20 4A 6F 62 31   42 00 09 6A 6F 62 2D = 73      me=20 ♦Job1 B .job-s
74 61 74 65 00 04 4A 6F   62 31 42 00 = 00 00 04=20 4A      tate ♦Jo b1B   = ♦J
6F=20 62 32 42 00 11 6A 6F   62 2D 73 74 61 74 65=20 2D      ob2B ◄jo b-state-
72 65 61 73 = 6F 6E 73=20 00   04 4A 6F 62 31 42 00 11     =20 reasons  ♦Job1B ◄
6A 6F 62 2D 73 74 61 = 74   65 2D 6D 65=20 73 73 61 67      job-stat e-messag
65 00 02 = 59 4F 05=20 41 00   05 73 69 64 65 73 00 0B      = e=20 ☻YO♣A  ♣sides ♂
75 6E 73 75 70 70 6F = 72   74 65 64=20 03            = ;     =20 unsuppor ted♥
 
 
 

IPP> RE: TES:binary files

Zehler,Peter (pzehler@channels.mc.xerox.c= om)
Tue,=20 9 Dec 1997 06:35:41 PST=20

Steve,
Even when we test across the = internet=20 we will still need to capture
the results. I am all for anything that = will=20 help us move along.
I have created a directory called = "Traces"=20 under the new_TES
directory for the time being. We can decide on a = directory=20 structure at
a later time. I assume that we will capture traces in = more than=20 one
form.
We need to decide on a naming convention. For this = purpose I=20 assume
that we will limit each trace file to a single request or = response.=20 The
naming convention should provide for the pairing of the request = to=20 its
response. The naming convention should facilitate the capturing = of=20 an
extended IPP conversation. A conversation is a sequence of=20 IPP
operations on an IPP printer.
We need to designate the = session,=20 operation, request|response, and
sequence in the conversation. A = suggestion=20 would be "SSSSOR##.trc"
where
SSSS: an arbitrary unique = sequence=20 identifier. The identifier
would be unique within the = "Traces"=20 directory.
O: The operation of the request/response. This is the=20
hexadecimal value of the IPP operation enum.
R: Designates = request or=20 response. A=3Drequest
B=3Dresponse.
##: sequence number of the = operation in=20 the IPP conversation.
We will also need to catalogue the contents of = the=20 directory. This
can be accomplished by a pdf file containing a table = with=20 relevant
information. I can keep this up to date if contributors send = me=20 the
information. I think some concise description of the=20 objective/purpose
of the IPP conversation would be appropriate.

I found that putting up an IPP emulator through an ISV is trivial.=20 The
emulator is the front end of my IPP printer. I have this anyway=20 since
small printers do not have very rich debug environments.

I think we need to know if there is any interest in pursuing = binary
trace=20 files. Do any other individuals have any feelings on this?

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

> -----Original Message-----
> From: Steve Gebert=20 [SMTP:stevegeb@us.ibm.com]
> Sent: Monday, December 08, = 1997 3:39=20 PM
> To: ipp@pwg.org
> Subject: =
>=20
> For interoperability testing, we were wondering if = people=20 were
> interested in
> exchanging binary=20 files
> corresponding to IPP Requests and Responses. The = parties=20 using these
> files
> would simply need=20 to
> construct a simple program to feed the file data into = their=20 server
> or client
> and read data from=20 their
> server or client into a file.
>=20
> These files could be sent as email attachments and for = the near=20 term
> help
> with interoperability=20 testing
> prior to people setting up machines outside = filewalls.=20 Perhaps we
> could even
> catalog the files=20 and
> make them available for download so that there would = be a=20 common
> test
> baseline for early=20 testing.
>
> We could make some example files = available if there is any
> interest. What = do
> you=20 think Peter?
>
>
> Steve = Gebert

------=_NextPart_000_0007_01BD095E.420EE490--