[smime] [Errata Held for Document Update] RFC4134 (7125)

RFC Errata System <rfc-editor@rfc-editor.org> Fri, 27 June 2025 16:50 UTC

Return-Path: <wwwrun@rfcpa.rfc-editor.org>
X-Original-To: smime@ietf.org
Delivered-To: smime@mail2.ietf.org
Received: from rfcpa.rfc-editor.org (unknown [167.172.21.234]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 2B4393A72475; Fri, 27 Jun 2025 09:50:55 -0700 (PDT)
Received: by rfcpa.rfc-editor.org (Postfix, from userid 461) id EABEA1D757D; Fri, 27 Jun 2025 09:50:54 -0700 (PDT)
To: dbaryshkov@gmail.com, phoffman@imc.org
From: RFC Errata System <rfc-editor@rfc-editor.org>
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20250627165054.EABEA1D757D@rfcpa.rfc-editor.org>
Date: Fri, 27 Jun 2025 09:50:54 -0700
Message-ID-Hash: T7VOTPXF4HAUAJ57QQNNWCGDKGEH3KRK
X-Message-ID-Hash: T7VOTPXF4HAUAJ57QQNNWCGDKGEH3KRK
X-MailFrom: wwwrun@rfcpa.rfc-editor.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-smime.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: debcooley1@gmail.com, iesg@ietf.org, smime@ietf.org, rfc-editor@rfc-editor.org
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [smime] [Errata Held for Document Update] RFC4134 (7125)
List-Id: SMIME Working Group <smime.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/smime/EcHTxUOZ1tG6SycPguYRC1E098Q>
List-Archive: <https://mailarchive.ietf.org/arch/browse/smime>
List-Help: <mailto:smime-request@ietf.org?subject=help>
List-Owner: <mailto:smime-owner@ietf.org>
List-Post: <mailto:smime@ietf.org>
List-Subscribe: <mailto:smime-join@ietf.org>
List-Unsubscribe: <mailto:smime-leave@ietf.org>

The following errata report has been held for document update 
for RFC4134, "Examples of S/MIME Messages". 

--------------------------------------
You may review the report below and at:
https://www.rfc-editor.org/errata/eid7125

--------------------------------------
Status: Held for Document Update
Type: Technical

Reported by: Dmitry Baryshkov <dbaryshkov@gmail.com>
Date Reported: 2022-09-11
Held by: Deb Cooley (IESG)

Section: B

Original Text
-------------
***5.2.bin***

|* Example 5.2.bin
|>5.2.bin
|MIIBZQYJKoZIhvcNAQcDoIIBVjCCAVICAQIxggEAMIG9AgEAMCYwEjEQMA4GA1UEAxMHQ2
|FybFJTQQIQRjRrx4AAVrwR024uzV1x0DANBgkqhkiG9w0BAQEFAASBgJQmQojGi7Z4IP+C
|VypBmNFoCDoEp87khtgyff2N4SmqD3RxPx+8hbLQt9i3YcMwcap+aiOkyqjMalT03VUC0X
|BOGv+HYI3HBZm/aFzxoq+YOXAWs5xlGerZwTOc9j6AYlK4qXvnztR5SQ8TBjlzytm4V7zg
|+TGrnGVNQBNw47Ewoj4CAQQwDQQLTWFpbExpc3RSQzIwEAYLKoZIhvcNAQkQAwcCAToEGH
|cUr5MSJ/g9HnJVHsQ6X56VcwYb+OfojTBJBgkqhkiG9w0BBwEwGgYIKoZIhvcNAwIwDgIC
|AKAECJwE0hkuKlWhgCBeKNXhojuej3org9Lt7n+wWxOhnky5V50vSpoYRfRRyw==
|<5.2.bin

Corrected Text
--------------
***5.2.bin***

|* Example 5.2.bin
|>5.2.bin
|MIIBIwYJKoZIhvcNAQcDoIIBFDCCARACAQAxgcAwgb0CAQAwJjASMRAwDgYDVQQDEwdDYX
|JsUlNBAhBGNGvHgABWvBHTbi7NXXHQMA0GCSqGSIb3DQEBAQUABIGAhUK+4wsu5Q8JqiTK
|3trB0wm4Jysly9Vx+8mc2/CybqCKXxydSu2YnRU5JgEaLmvwRDmJNzxvx0phCwsnd6r51J
|ek0iE/wj8g1NwQ6dY/ANucgkfWfpb/Em6HhKC67YEPVm2mHeurw7ehufhfi8wbSuUUNgZh
|0MdkX2lnkalQ7tgwSAYJKoZIhvcNAQcBMBkGCCqGSIb3DQMCMA0CAToECOhwgeLvxRVXgC
|AGUwp7jVwWDczVdtaLWdZFjBoaDOYe895DVgCbQIw4XQ==
|<5.2.bin

Notes
-----
The base64 encoding in the Appending B doesn't correspond to the data in the section 5.2. Provided base64 was generated using data in the section 5.2 instead.

--------------------------------------
RFC4134 (draft-ietf-smime-examples-15)
--------------------------------------
Title               : Examples of S/MIME Messages
Publication Date    : July 2005
Author(s)           : P. Hoffman, Ed.
Category            : INFORMATIONAL
Source              : S/MIME Mail Security
Stream              : IETF
Verifying Party     : IESG