IETF Logo Mail Archive

Re: [stir] "rcdi" vs MIME Content-Encoding

Ben Campbell <ben@nostrum.com> Wed, 03 April 2024 00:37 UTC

Return-Path: <ben@nostrum.com>
X-Original-To: stir@ietfa.amsl.com
Delivered-To: stir@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EAD7FC15106B; Tue, 2 Apr 2024 17:37:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.866
X-Spam-Level:
X-Spam-Status: No, score=-4.866 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_DISCARD=1.8, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, T_MIME_MALF=0.01, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=nostrum.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nxzGjK7HNwEP; Tue, 2 Apr 2024 17:37:39 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DB54FC14F689; Tue, 2 Apr 2024 17:37:39 -0700 (PDT)
Received: from smtpclient.apple (070-120-133-087.res.spectrum.com [70.120.133.87]) (authenticated bits=0) by nostrum.com (8.18.1/8.18.1) with ESMTPSA id 4330aq9q050565 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Tue, 2 Apr 2024 19:37:38 -0500 (CDT) (envelope-from ben@nostrum.com)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nostrum.com; s=default; t=1712104659; bh=B3TTAFLb4CGgyJMviCasjpmXVNdVFZWSquN++8lr7a0=; h=From:Subject:Date:In-Reply-To:Cc:To:References; b=f10Lg18bTBAFvS9o3j3LsXcpq9+PZyPLGqJR2yOeiMO9jmPpG0ZDy2tzsqFk3nrO7 AUtetqt7wmwM6eeNpRU5kDeqKJsDlQlsk47raOcbTao5/QzLWgplMxm/OChJnRraNG 7Tguuqew5znie8xbxLT5mC23vd2q65yqKKgKGtE0=
X-Authentication-Warning: raven.nostrum.com: Host 070-120-133-087.res.spectrum.com [70.120.133.87] claimed to be smtpclient.apple
From: Ben Campbell <ben@nostrum.com>
Message-Id: <718E2AB3-FF57-493D-AA92-7298818D9281@nostrum.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_2B45B23F-3E8E-4D15-B883-F9FF9AF04764"; protocol="application/pgp-signature"; micalg="pgp-sha512"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3774.500.171.1.1\))
Date: Tue, 02 Apr 2024 19:37:38 -0500
In-Reply-To: <CAN8C-_Lnfrw3Sk0pY3oE--kP1BLbYynBOMAVT=WWxK3gVD9yGw@mail.gmail.com>
Cc: Alec Fenichel <alec.fenichel=40transnexus.com@dmarc.ietf.org>, IETF STIR Mail List <stir@ietf.org>, "Peterson, Jon" <jon.peterson@transunion.com>, Chris Wendt <cwendt@somos.com>
To: Orie Steele <orie@transmute.industries>
References: <E7B3FBBB-672B-4CC2-AB32-B13C7759D861@nostrum.com> <SJ2PR11MB84027F8DE9935943D8652002993F2@SJ2PR11MB8402.namprd11.prod.outlook.com> <A158B773-4100-4AB6-BB67-EB369303266F@nostrum.com> <SJ2PR11MB84028DB1EC1A6B11F1E0CEC6993F2@SJ2PR11MB8402.namprd11.prod.outlook.com> <CAN8C-_Lnfrw3Sk0pY3oE--kP1BLbYynBOMAVT=WWxK3gVD9yGw@mail.gmail.com>
X-Mailer: Apple Mail (2.3774.500.171.1.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/stir/8V7tQBwcmfFKTbb0Qbqe5NIMqLk>
Subject: Re: [stir] "rcdi" vs MIME Content-Encoding
X-BeenThere: stir@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Secure Telephone Identity Revisited <stir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/stir>, <mailto:stir-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/stir/>
List-Post: <mailto:stir@ietf.org>
List-Help: <mailto:stir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/stir>, <mailto:stir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Apr 2024 00:37:44 -0000

Thanks, that’s the reference that started me down this path :-)

Ben.

> On Apr 2, 2024, at 6:12 PM, Orie Steele <orie@transmute.industries> wrote:
> 
> Is this reference helpful?
> 
> https://datatracker.ietf.org/doc/html/rfc9399#section-7
> 
> If you believe you have a use case for multiple suffixes, like this example, I would like to understand it.
> 
> Regards,
> 
> OS
> 
> On Mon, Apr 1, 2024, 4:17 PM Alec Fenichel <alec.fenichel=40transnexus.com@dmarc.ietf.org <mailto:40transnexus.com@dmarc.ietf.org>> wrote:
>> Ben,
>> 
>>  
>> 
>> I had not thought about this until you sent this email and this is an important point, so I think it should be clarified.
>> 
>>  
>> 
>> Sincerely,
>> 
>>  
>> 
>> Alec Fenichel
>> 
>> Chief Technology Officer
>> 
>> TransNexus <https://transnexus.com/>
>> alec.fenichel@transnexus.com <mailto:alec.fenichel@transnexus.com>
>> +1 (404) 369-2407 <tel:+14043692407>
>>  
>> 
>> From: Ben Campbell <ben@nostrum.com <mailto:ben@nostrum.com>>
>> Date: Monday, April 1, 2024 at 17:09
>> To: Alec Fenichel <alec.fenichel@transnexus.com <mailto:alec.fenichel@transnexus.com>>
>> Cc: IETF STIR Mail List <stir@ietf.org <mailto:stir@ietf.org>>, Peterson, Jon <jon.peterson@transunion.com <mailto:jon.peterson@transunion.com>>, Chris Wendt <cwendt@somos.com <mailto:cwendt@somos.com>>
>> Subject: Re: [stir] "rcdi" vs MIME Content-Encoding
>> 
>> Yeah, I was just thinking that after sending the question.
>> 
>>  
>> 
>> Does draft-ietf-stir-passport-rcd need to say something about Content-Encoding? Or is that sufficiently understood by everyone (other than myself)?
>> 
>>  
>> 
>>  
>> 
>> On Apr 1, 2024, at 3:29 PM, Alec Fenichel <alec.fenichel@transnexus.com <mailto:alec.fenichel@transnexus.com>> wrote:
>> 
>>  
>> 
>> It needs to be the decoded data. At the time the rcdi is sent, the content encoding is not necessarily known. A web server may support multiple content encodings and return the best encoding supported by the client (indicated by the Accept-Encoding header).
>> 
>>  
>> 
>> Sincerely,
>> 
>>  
>> 
>> Alec Fenichel
>> 
>> Chief Technology Officer
>> 
>> TransNexus <https://transnexus.com/>
>> alec.fenichel@transnexus.com <mailto:alec.fenichel@transnexus.com>
>> +1 (404) 369-2407 <tel:+14043692407>
>>  
>> 
>> From: stir <stir-bounces@ietf.org <mailto:stir-bounces@ietf.org>> on behalf of Ben Campbell <ben@nostrum.com <mailto:ben@nostrum.com>>
>> Date: Monday, April 1, 2024 at 16:21
>> To: IETF STIR Mail List <stir@ietf.org <mailto:stir@ietf.org>>
>> Cc: Peterson, Jon <jon.peterson@transunion.com <mailto:jon.peterson@transunion.com>>, Chris Wendt <cwendt@somos.com <mailto:cwendt@somos.com>>
>> Subject: [stir] "rcdi" vs MIME Content-Encoding
>> 
>> Hi,
>> 
>>  
>> 
>> In thinking about the “rcdi” hashes and  RCD “icn” keys:
>> 
>>  
>> 
>> What if the target has Content-Encoding? Would the “rcdi” hash be over the raw or decoded data?
>> 
>>  
>> 
>> For example, lets say that I get the following headers when dereferencing the “icn” key:
>> 
>>  
>> 
>> Content-Type: image/svg+xml
>> Content-Encoding: gzip
>>  
>> 
>> Should the “rcdi” hash be over the compressed or uncompressed version of the data? I assume since draft-ietf-stir-passport-rcd-26 does not mention content-encoding, that the hash would be over the actual octets we get back on the wire prior to decoding. 
>> 
>>  
>> 
>> But I see that RFC 9399 (Certificate Logotypes), which seems like a similar-if-not-identical application, says the opposite for this specific example:
>> 
>>  
>> 
>> Whether the SVG image is GZIP-compressed or uncompressed, the hash value for the SVG image is calculated over the uncompressed SVG content with canonicalized EOL characters, as specified above.
>> 
>>  
>> 
>> Thoughts?
>> 
>>  
>> 
>> Thanks!
>> 
>>  
>> 
>> Ben.
>> 
>>  
>> 
>> _______________________________________________
>> stir mailing list
>> stir@ietf.org <mailto:stir@ietf.org>
>> https://www.ietf.org/mailman/listinfo/stir

v2.23.0 | Report a Bug | By Email