Re: 5 years since last message

This is an OpenPGP/MIME signed message (RFC 3156 and 4880).

--===============2547969826880667414==
Content-Type: multipart/signed;
 boundary="=_MailMate_C543949D-9118-46DA-B850-654221555131_=";
 micalg=pgp-sha1; protocol="application/pgp-signature"

This is an OpenPGP/MIME signed message (RFC 3156 and 4880).

--=_MailMate_C543949D-9118-46DA-B850-654221555131_=
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

Well, the standard is in use -- sort of -- with various modifications loc=
ally (like use of a different prefix than what is assigned here in IETF).=
 I heard last time last week people "just saying" this is what is and sho=
uld be used for routing of communication with E.164 numbers as destinatio=
n in time of emergency/stress where centralized IN systems can not be rea=
ched (but locally cached DNS can).

So the list is silent, but there is some kind of usage. Does this "some k=
ind of usage" imply something should be done?

I do not know.

I personally did conclude after the first couple of years of discussions =
that NAPTR is incredibly stupid. Designing things to have so large RRSets=
 is not very optimal, so other DNS types would be better. I suggested the=
 simple URI. But it itself got stuck in the IETF process of creation of n=
ew RRTypes, and when it finally was approved, the interest in deployment =
was sort of gone :-(

And people seems to have implemented NAPTR...

   Patrik

On 2 Jul 2019, at 2:41, Livingood, Jason wrote:

> So what needs to happen here? Seems indisputable that there's not much =
happening on the ENUM front...
>
> =EF=BB=BFOn 6/27/19, 9:48 AM, "enum on behalf of Olivier Guillard / AFN=
IC" <[email protected] on behalf of [email protected]> wrote:
>
>     pong :-)
>
>     le Tuesday 15 January =C3=A0 13 H 17 , Jaap Akkerhuis a =C3=A9crit =
:
>     >  Bernie Hoeneisen writes:
>     >
>     >  > Hi Jaap
>     >  >
>     >  > Well, there is a dependency on this list in RFC 6117...
>     >  >
>     >  > On the other hand, registering new ENUM services has not been =
that popular
>     >  > either for several years...
>     >  >
>     >  > cheers
>     >  >   Bernie (Designated Expert of the IESG and other list maintai=
ner)
>     >
>     > In that case, it would make sense that you take over the maintain=
ing
>     > of this list as well. Would you? If so, let's arrange that off-li=
st.
>     >
>     > 	jaap
>     >
>     > _______________________________________________
>     > enum mailing list
>     > [email protected]
>     > https://www.ietf.org/mailman/listinfo/enum
>
>     --
>     Olivier
>
>     _______________________________________________
>     enum mailing list
>     [email protected]
>     https://www.ietf.org/mailman/listinfo/enum
>
>
> _______________________________________________
> enum mailing list
> [email protected]
> https://www.ietf.org/mailman/listinfo/enum

--=_MailMate_C543949D-9118-46DA-B850-654221555131_=
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename=signature.asc
Content-Type: application/pgp-signature; name=signature.asc

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org

iG0EARECAC0WIQRUH/cJI8i4DDUU3qWsxpsaC4jXzQUCXRrvGA8ccGFmQGZyb2Ji
aXQuc2UACgkQrMabGguI182kqACcD5zrEB4oqlzXFScTCHC5esyK1HgAn3vOKNNd
sGyhr3NjVpKlXK4KyHlB
=5QrF
-----END PGP SIGNATURE-----

--=_MailMate_C543949D-9118-46DA-B850-654221555131_=--


--===============2547969826880667414==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
enum mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/enum

--===============2547969826880667414==--