Re: [IPP] Weird coomand IPP
Paul Santangelo via ipp <ipp@pwg.org> Tue, 19 November 2019 02:51 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 C14E4120288 for <ietfarch-ipp-archive@ietfa.amsl.com>; Mon, 18 Nov 2019 18:51:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, MAILING_LIST_MULTI=-1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (2048-bit key) reason="fail (message has been altered)" header.d=kmbs-konicaminolta-us.20150623.gappssmtp.com
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 NKjWZvVJZFKM for <ietfarch-ipp-archive@ietfa.amsl.com>; Mon, 18 Nov 2019 18:51:41 -0800 (PST)
Received: from mail.pwg.org (mail.pwg.org [50.116.7.199]) by ietfa.amsl.com (Postfix) with ESMTP id 91321120236 for <ipp-archive2@ietf.org>; Mon, 18 Nov 2019 18:51:41 -0800 (PST)
Received: by mail.pwg.org (Postfix, from userid 1002) id 6671F3AD4; Tue, 19 Nov 2019 02:51:41 +0000 (UTC)
Received: from mail.pwg.org (localhost [IPv6:::1]) by mail.pwg.org (Postfix) with ESMTP id 98DFF3AD5; Tue, 19 Nov 2019 02:51:39 +0000 (UTC)
X-Original-To: ipp@pwg.org
Delivered-To: ipp@pwg.org
Received: by mail.pwg.org (Postfix, from userid 1002) id 6BC343D59; Tue, 19 Nov 2019 02:51:38 +0000 (UTC)
Received: from mail-qt1-x836.google.com (mail-qt1-x836.google.com [IPv6:2607:f8b0:4864:20::836]) by mail.pwg.org (Postfix) with ESMTPS id 87F183AB9 for <ipp@pwg.org>; Tue, 19 Nov 2019 02:51:37 +0000 (UTC)
Received: by mail-qt1-x836.google.com with SMTP id g50so22884429qtb.4 for <ipp@pwg.org>; Mon, 18 Nov 2019 18:51:37 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kmbs-konicaminolta-us.20150623.gappssmtp.com; s=20150623; h=content-transfer-encoding:from:mime-version:subject:date:message-id :references:cc:in-reply-to:to; bh=/mtCg9MFbt+uveCJUL3+VbQRiThm4PiA4gaUogAWvl4=; b=GroYVHsQoKkuuQBnKXzBQXoHsXqQJoFv3Xx371b7eb/XbvLGujwQin11qupZEBLWEx IcXUxTab+AYD4ltalGjBMVykEr6V3+kOUhSQ1s7Kw2g53skWSl2LaqBEsV78zC6wX9n3 e2KyCHIG+kGecrdI2N1AV4iQo6bg6mS9K4hAfMeLZs3Hs1JW0wrTdKzjWBlel/HKUDrH nBgBuTnlzIB2z1xcIgu5lK2pXz9JNSHhspeuEML3OPF94BCA10yvK3PC/fFHGbqjJ3/3 71AwDcJHR1VIrm3/rRHpVisR2OMA1Qm2wNSnJbQeblKstiEVO6QNHz5CIX/UoxY6aewg JYZw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:content-transfer-encoding:from:mime-version :subject:date:message-id:references:cc:in-reply-to:to; bh=/mtCg9MFbt+uveCJUL3+VbQRiThm4PiA4gaUogAWvl4=; b=DGh5YCaqwKhOwNOj+/l6nk43eXjiE+BpIYDKe7uoKpH3rR/Uy2xRPMnpUJrRBPjkVa AoZFwY3nYECX4MKRDoY2Fyb42mD9bB7IIpHhAD4FXKPpQalW1H/48Ndd48/Ylo1TYwBq w792PHuFMUqySaqicFj+GQzbyxFRbu4/KFvuEeXlTSEcqYDMfHfhVlhySK4NokS76niM SZygmZXZ11ULsj4AWTM5Pq9JHINJMS2qr4d2M4J65FoENnSUaZKYWlqUq+eaHQG4ZYlx uD8hKspLRlNUQaHeoBcsxgWUhw56rAiBqv7WSqzBhsAxKIfa3IpiXYepiGotU2GNMic2 IXYA==
X-Gm-Message-State: APjAAAWN/ey8T25qmZWjkKXN6YrygFU+WQpEumdRqp7X4bMemm77g/21 lOHOSz9BUlvQ+xoJXsx3weNK//+uhpE=
X-Google-Smtp-Source: APXvYqyNeJMKJTa17Y3nuOTUFRUSTl8eV2Ppw8hSDJGUUIBgTXLEhX14BKk9RJAL2HYA/DmotKxVDw==
X-Received: by 2002:aed:2799:: with SMTP id a25mr31035050qtd.226.1574131896212; Mon, 18 Nov 2019 18:51:36 -0800 (PST)
Received: from ?IPv6:2600:380:bc47:3da6:f11e:1c21:f419:577b? ([2600:380:bc47:3da6:f11e:1c21:f419:577b]) by smtp.gmail.com with ESMTPSA id v186sm9625113qkb.42.2019.11.18.18.51.35 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 18 Nov 2019 18:51:35 -0800 (PST)
Mime-Version: 1.0 (1.0)
Date: Mon, 18 Nov 2019 21:51:34 -0500
Message-Id: <BAE2BB22-A9AC-4EEA-94EE-575A16D19AA1@kmbs.konicaminolta.us>
References: <7A38E8CD-B977-4558-972F-1C1059F2CCEA@msweet.org>
In-Reply-To: <7A38E8CD-B977-4558-972F-1C1059F2CCEA@msweet.org>
To: Michael Sweet <msweet@msweet.org>
X-Mailer: iPhone Mail (17A878)
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: Paul Santangelo via ipp <ipp@pwg.org>
Reply-To: Paul Santangelo <paul.santangelo@kmbs.konicaminolta.us>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Errors-To: ipp-bounces@pwg.org
Sender: ipp <ipp-bounces@pwg.org>
Thank you Michael. Sent from my iPhone > On Nov 18, 2019, at 9:49 PM, Michael Sweet <msweet@msweet.org> wrote: > > 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