Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:127657
Precedence: bulk
MIME-Version: 1.0
References: <CAOV5rgYu8Z+Nqifavvg9O3t=153zpa_3FXR3e=-b9qvKdXT=CQ@mail.gmail.com>
In-Reply-To: <CAOV5rgYu8Z+Nqifavvg9O3t=153zpa_3FXR3e=-b9qvKdXT=CQ@mail.gmail.com>
Date: Thu, 12 Jun 2025 19:22:46 +0200
Message-ID: <CAJmy8YE4F3QwnWqeW2+VBnBV8=nj2zJcD8x=Bamzf2JSwB2cpQ@mail.gmail.com>
Subject: Re: [PHP-DEV] Proposal: Support for RFC4648 in PHP
To: ignace nyamagana butera <nyamsprod@gmail.com>
Cc: PHP Internals List <internals@lists.php.net>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
From: divinity76@gmail.com (Hans Henrik Bergan)

On Thu, 12 Jun 2025 at 18:53, ignace nyamagana butera
<nyamsprod@gmail.com> wrote:
>
> Greetings,
>
> I have been playing around with an RFC proposal for some time and recentl=
y 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 d=
ata 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 `bih2=
hex` and `hex2bin` but those functions only provide a partial support for R=
FC4648.
> In my RFC proposal I would like to introduce, instead, a new namespace `E=
ncoding` that will host an all new and improved API which will cover the co=
mplete RFC,
> will be consistent and easily extendable for future data encoding algorit=
hms addition.
>
> For reference, this is not a new topic, the issue with the current implem=
entation is well documented in the mailing list as well as a past attempt t=
o
> 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 t=
he draft RFC.
>
> Best regards,
> Ignace Nyamagana Butera


Why do it in core?
Is userland base16/base32 performance unsatisfactory?