Re: Asn.1 OER support

--0000000000007b9efa05dd019bc0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hi Kenneth,
No worries for the late reply, here a non exhaustive list of where OER
rules are used :

- NTCIP for traffic lights controllers and variable message signs :
https://www.ntcip.org/file/2021/03/1102v0115p.pdf
- V2x for security certificates format / PKI communication as described in
IEEE 1609.2 and ETSI 103.097 :
https://www.etsi.org/deliver/etsi_ts/103000_103099/103097/01.04.01_60/ts_10=
3097v010401p.pdf
- Also in the Interledger project :
https://github.com/interledger/rfcs/tree/master/asn1

Thibaud Rouill=C3=A9

Le mar. 12 avr. 2022 =C3=A0 10:11, Kenneth Lundin <[email protected]> a =
=C3=A9crit :

> Very late answer, but anyway.
>
> No we have no plans to support OER encoding rules. I did not even know
> about OER until I read this mail. Where is it used?
> If it would become used in a standard that is relevant for telecom or
> other communication than it might be interesting for us to support it. Bu=
t
> I don't think there are
> such cases right now.
>
> /Kenneth, Erlang/OTP, Ericsson
>
> On Wed, Nov 3, 2021 at 8:53 PM Thibaud Rouill=C3=A9 <thibaud.rouille@gmai=
l.com>
> wrote:
>
>> Hello!
>>
>> I am wondering if the Erlang Asn.1 compiler will get OER encoding rules
>> support. Does anyone know if OER support is planned on a future OTP rele=
ase
>> ?
>>
>>
>>

--0000000000007b9efa05dd019bc0
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Hi Kenneth,</div><div>No worries for the late reply, =
here a non exhaustive list of where OER rules are used :</div><div><br></di=
v><div>- NTCIP for traffic lights controllers and variable message signs : =
<a href=3D"https://www.ntcip.org/file/2021/03/1102v0115p.pdf">https://www.n=
tcip.org/file/2021/03/1102v0115p.pdf</a></div><div>- V2x for security certi=
ficates format / PKI communication as described in IEEE 1609.2 and ETSI 103=
.097 : <a href=3D"https://www.etsi.org/deliver/etsi_ts/103000_103099/103097=
/01.04.01_60/ts_103097v010401p.pdf">https://www.etsi.org/deliver/etsi_ts/10=
3000_103099/103097/01.04.01_60/ts_103097v010401p.pdf</a></div><div>- Also i=
n the Interledger project : <a href=3D"https://github.com/interledger/rfcs/=
tree/master/asn1">https://github.com/interledger/rfcs/tree/master/asn1</a><=
/div><div><br></div><div>Thibaud Rouill=C3=A9<br></div></div><br><div class=
=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">Le=C2=A0mar. 12 avr.=
 2022 =C3=A0=C2=A010:11, Kenneth Lundin &lt;<a href=3D"mailto:kenneth@erlan=
g.org">[email protected]</a>&gt; a =C3=A9crit=C2=A0:<br></div><blockquote =
class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px sol=
id rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr"><div>Very late answe=
r, but anyway.</div><div><br></div><div>No we have no plans to support OER =
encoding rules. I did not even know about OER until I read this mail. Where=
 is it used?</div><div>If it would become used in a standard that is releva=
nt for telecom or other communication than it might be interesting for us t=
o support it. But I don&#39;t think there are</div><div>such cases right no=
w.</div><div><br></div><div>/Kenneth, Erlang/OTP, Ericsson<br></div></div><=
br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Wed,=
 Nov 3, 2021 at 8:53 PM Thibaud Rouill=C3=A9 &lt;<a href=3D"mailto:thibaud.=
[email protected]" target=3D"_blank">[email protected]</a>&gt; wrot=
e:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0=
.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir=3D"l=
tr">Hello!<div><br></div><div>I am wondering if the Erlang Asn.1 compiler w=
ill get OER encoding rules support. Does anyone know if OER support is plan=
ned on a future OTP release ?</div><div><br></div><div><br></div></div>
</blockquote></div>
</blockquote></div>

--0000000000007b9efa05dd019bc0--