Re: [IPP] Weird coomand IPP
Michael Sweet via ipp <ipp@pwg.org> Tue, 19 November 2019 02:50 UTC
Return-Path: <ipp-bounces@pwg.org>
X-Original-To: ietfarch-ipp-archive@ietfa.amsl.com
Delivered-To: ietfarch-ipp-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 701CA120236 for <ietfarch-ipp-archive@ietfa.amsl.com>; Mon, 18 Nov 2019 18:50:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.899
X-Spam-Level:
X-Spam-Status: No, score=-2.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MAILING_LIST_MULTI=-1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 45VFYq7-SDNw for <ietfarch-ipp-archive@ietfa.amsl.com>; Mon, 18 Nov 2019 18:49:59 -0800 (PST)
Received: from mail.pwg.org (mail.pwg.org [50.116.7.199]) by ietfa.amsl.com (Postfix) with ESMTP id 5EE5E120232 for <ipp-archive2@ietf.org>; Mon, 18 Nov 2019 18:49:59 -0800 (PST)
Received: by mail.pwg.org (Postfix, from userid 1002) id 2CBBCBDA8; Tue, 19 Nov 2019 02:49:58 +0000 (UTC)
Received: from mail.pwg.org (localhost [IPv6:::1]) by mail.pwg.org (Postfix) with ESMTP id AA7633AD5; Tue, 19 Nov 2019 02:49:55 +0000 (UTC)
X-Original-To: ipp@pwg.org
Delivered-To: ipp@pwg.org
Received: by mail.pwg.org (Postfix, from userid 1002) id A66463D59; Tue, 19 Nov 2019 02:49:54 +0000 (UTC)
Received: from mail.msweet.org (mail.msweet.org [173.255.209.91]) by mail.pwg.org (Postfix) with ESMTP id 473AF3AD4 for <ipp@pwg.org>; Tue, 19 Nov 2019 02:49:54 +0000 (UTC)
Received: from retina15x.lan (67-204-236-184.eastlink.ca [67.204.236.184]) by mail.msweet.org (Postfix) with ESMTPSA id 7842D803B7; Tue, 19 Nov 2019 02:49:53 +0000 (UTC)
Mime-Version: 1.0 (Mac OS X Mail 13.0 \(3601.0.10\))
In-Reply-To: <887180b9-45b1-4a0a-ab44-e7459cf196c2@kmbs.konicaminolta.us>
Date: Mon, 18 Nov 2019 21:49:51 -0500
Message-Id: <7A38E8CD-B977-4558-972F-1C1059F2CCEA@msweet.org>
References: <2f3144a7-b310-f175-b735-36c23261491a@kmbs.konicaminolta.us> <1B19CC36-32C5-447E-B2D8-0CBBA6BCD6DF@msweet.org> <887180b9-45b1-4a0a-ab44-e7459cf196c2@kmbs.konicaminolta.us>
To: paul.santangelo@kmbs.konicaminolta.us
X-Mailer: Apple Mail (2.3601.0.10)
Cc: PWG IPP Workgroup <ipp@pwg.org>
Subject: Re: [IPP] Weird coomand IPP
X-BeenThere: ipp@pwg.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: ISTO-PWG Internet Printing Protocol workgroup discussion forum <ipp.pwg.org>
List-Unsubscribe: <https://www.pwg.org/mailman/options/ipp>, <mailto:ipp-request@pwg.org?subject=unsubscribe>
List-Archive: <http://www.pwg.org/pipermail/ipp/>
List-Post: <mailto:ipp@pwg.org>
List-Help: <mailto:ipp-request@pwg.org?subject=help>
List-Subscribe: <https://www.pwg.org/mailman/listinfo/ipp>, <mailto:ipp-request@pwg.org?subject=subscribe>
From: Michael Sweet via ipp <ipp@pwg.org>
Reply-To: Michael Sweet <msweet@msweet.org>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Errors-To: ipp-bounces@pwg.org
Sender: ipp <ipp-bounces@pwg.org>
Paul, That's a part of the HTTP specifications; basically look for the Transfer-Encoding information (I think in RFC 7230 or 7231) which takes the place of Content-Length for data whose length is not known ahead of time. > On Nov 18, 2019, at 7:21 PM, Paul Santangelo <paul.santangelo@kmbs.konicaminolta.us> wrote: > > Perfect, Thank you. > > Would you be able to point me in a place that actually states that? > > I read the RFC's, well glazed over them quickly, I would like to know more about these. > > Thank you. > > Regards, > > > > PAUL SANTANGELO, CCNA, CNE > Escalation System Support (ESS) Integrator > Konica Minolta Business Solutions U.S.A., Inc. > 101 Williams Drive Ramsey, NJ 07446 > Office: 800-825-5664 > Visit us: Count on Konica Minolta > > Disclaimer > > > > On 11/18/2019 7:16 PM, Mike Sweet wrote: >> Paul, >> >> Those are the chunk lengths in hexadecimal. >> >> Sent from my iPhone >> >>> On Nov 18, 2019, at 6:59 PM, Paul Santangelo via ipp <ipp@pwg.org> wrote: >>> >>> Hi All: >>> >>> Trying to understand an IPP transmission capture from an AS/400. >>> >>> I got most of it down except for what seems to be a transmission size, but it doesn't correlate to anything I can identify. >>> >>> If you see the image below, there is an FCC before the print job starts in job A and a 594 before print job B starts. >>> >>> I am trying to identify what this means. Its not the size of the file being transmitted, because other print job traces has the FCC and the size of the transmission is different. I'm wondering if its more of a binary vs. ASCII transmission, but I am uncertain and can not find any documentation. >>> >>> Any clarification here would be greatly appreciated, thank you. >>> >>> >>> >>> >>> <hhcafmhockoomejo.png> >>> -- >>> >>> Regards, >>> >>> >>> >>> PAUL SANTANGELO, CCNA, CNE >>> Escalation System Support (ESS) Integrator >>> Konica Minolta Business Solutions U.S.A., Inc. >>> 101 Williams Drive Ramsey, NJ 07446 >>> Office: 800-825-5664 >>> Visit us: Count on Konica Minolta >>> >>> Disclaimer >>> >>> >>> >>> _______________________________________________ >>> ipp mailing list >>> ipp@pwg.org >>> https://www.pwg.org/mailman/listinfo/ipp > ________________________ Michael Sweet _______________________________________________ ipp mailing list ipp@pwg.org https://www.pwg.org/mailman/listinfo/ipp
- [IPP] Weird coomand IPP Paul Santangelo via ipp
- Re: [IPP] Weird coomand IPP Mike Sweet via ipp
- Re: [IPP] Weird coomand IPP Paul Santangelo via ipp
- Re: [IPP] Weird coomand IPP Michael Sweet via ipp
- Re: [IPP] Weird coomand IPP Paul Santangelo via ipp