IETF Logo Mail Archive

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

Ben Campbell <ben@nostrum.com> Mon, 01 April 2024 21:08 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 44308C151524 for <stir@ietfa.amsl.com>; Mon, 1 Apr 2024 14:08:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.183
X-Spam-Level:
X-Spam-Status: No, score=0.183 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, KHOP_HELO_FCRDNS=0.048, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, T_MIME_MALF=0.01, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=no 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 vOM7BvGqA9BN for <stir@ietfa.amsl.com>; Mon, 1 Apr 2024 14:08:55 -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 29E57C14F5F3 for <stir@ietf.org>; Mon, 1 Apr 2024 14:08:55 -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 431L8r12033355 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Mon, 1 Apr 2024 16:08:53 -0500 (CDT) (envelope-from ben@nostrum.com)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nostrum.com; s=default; t=1712005734; bh=dKlIY6SA0+r8C5cMr4MQIw+HffkqjL3Auqi951waJ0E=; h=From:Subject:Date:In-Reply-To:Cc:To:References; b=vwSVg5/rikpzKnduvBGDKHRJV1BweYHLuQ3lkD6CPZjUK93+QLTD8PnBPPe22zxkb J0j79W8QpXqqTcmosLNs/hAIA1s9xEH4XElrnto6DZuM9BiBQiU5s5338c/YG2u1ki zQwYSLW+dVMa0le13Xz44OZEPzq4RNEbtX++XSLA=
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: <A158B773-4100-4AB6-BB67-EB369303266F@nostrum.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_AEF14179-DADE-4146-B19E-CFFF1DE602BC"; protocol="application/pgp-signature"; micalg="pgp-sha512"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3774.500.171.1.1\))
Date: Mon, 01 Apr 2024 16:08:47 -0500
In-Reply-To: <SJ2PR11MB84027F8DE9935943D8652002993F2@SJ2PR11MB8402.namprd11.prod.outlook.com>
Cc: IETF STIR Mail List <stir@ietf.org>, "Peterson, Jon" <jon.peterson@transunion.com>, Chris Wendt <cwendt@somos.com>
To: Alec Fenichel <alec.fenichel@transnexus.com>
References: <E7B3FBBB-672B-4CC2-AB32-B13C7759D861@nostrum.com> <SJ2PR11MB84027F8DE9935943D8652002993F2@SJ2PR11MB8402.namprd11.prod.outlook.com>
X-Mailer: Apple Mail (2.3774.500.171.1.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/stir/zy4t8lPgT-QWR1McBO5gJP_7288>
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: Mon, 01 Apr 2024 21:08:59 -0000

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> 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.

v2.23.0 | Report a Bug | By Email