Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:127656
Precedence: bulk
MIME-Version: 1.0
Date: Thu, 12 Jun 2025 18:50:32 +0200
Message-ID: <CAOV5rgYu8Z+Nqifavvg9O3t=153zpa_3FXR3e=-b9qvKdXT=CQ@mail.gmail.com>
Subject: [PHP-DEV] Proposal: Support for RFC4648 in PHP
To: PHP Internals List <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="000000000000028a14063762bb8f"
From: nyamsprod@gmail.com (ignace nyamagana butera)

--000000000000028a14063762bb8f
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Greetings,

I have been playing around with an RFC proposal for some time and recently
after discussing it with Tim D=C3=BCsterhus he has volunteered
to do the implementation so I would like to submit to you an RFC around
data encoding in PHP. The goal of the RFC is to fully implement
RFC4648 (base16 , base32, base64).

I know that PHP already has `base64_encode` and `base64_decode` and
`bih2hex` and `hex2bin` but those functions only provide a partial support
for RFC4648.
In my RFC proposal I would like to introduce, instead, a new namespace
`Encoding` that will host an all new and improved API which will cover the
complete RFC,
will be consistent and easily extendable for future data encoding
algorithms addition.

For reference, this is not a new topic, the issue with the current
implementation is well documented in the mailing list as well as a past
attempt to
add RFC4648 to the language.

- base64_encode without padding https://externals.io/message/122630
- base64 url format https://externals.io/message/119243
- [RFC] RFC4648 encoding https://externals.io/message/91858#91964

If people are interested I will proceed with a karma request and create the
draft RFC.

Best regards,
Ignace Nyamagana Butera

--000000000000028a14063762bb8f
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Greetings,<br><br>I have been playing around with an RFC p=
roposal for some time and recently after discussing it with Tim D=C3=BCster=
hus he has volunteered<br>to do the implementation so I would like to submi=
t to you an RFC around data encoding in PHP. The goal of the RFC is to full=
y implement <br>RFC4648 (base16 , base32, base64).<br><br>I know that PHP a=
lready has `base64_encode` and `base64_decode` and `bih2hex` and `hex2bin` =
but those functions only provide a partial support for RFC4648.<div>In my R=
FC proposal I would like to=C2=A0introduce, instead, a new namespace `Encod=
ing` that will host an all new and improved API which=C2=A0will cover the c=
omplete RFC,</div><div>will be consistent and easily extendable for future =
data encoding algorithms addition.</div><div><div><br>For reference, this i=
s not a new topic, the issue with the current implementation is well docume=
nted in the mailing list as well as a past attempt to <br>add RFC4648 to th=
e language.<br><br>- base64_encode without padding <a href=3D"https://exter=
nals.io/message/122630">https://externals.io/message/122630</a> <br>- base6=
4 url format <a href=3D"https://externals.io/message/119243">https://extern=
als.io/message/119243</a><br>- [RFC] RFC4648 encoding <a href=3D"https://ex=
ternals.io/message/91858#91964">https://externals.io/message/91858#91964</a=
><br><br>If people are interested I will proceed with a karma request and c=
reate the draft RFC.</div></div><div><br></div><div>Best regards,</div><div=
>Ignace Nyamagana Butera</div></div>

--000000000000028a14063762bb8f--