Return-Path: <paf@frobbit.se>
X-Original-To: enum@ietfa.amsl.com
Delivered-To: enum@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1])
 by ietfa.amsl.com (Postfix) with ESMTP id B0B8112008D
 for <enum@ietfa.amsl.com>; Mon,  1 Jul 2019 22:44:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.698
X-Spam-Level: 
X-Spam-Status: No, score=-2.698 tagged_above=-999 required=5
 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1,
 DKIM_VALID_AU=-0.1, FROM_EXCESS_BASE64=0.001, RCVD_IN_DNSWL_LOW=-0.7,
 SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001]
 autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key)
 header.d=frobbit.se
Received: from mail.ietf.org ([4.31.198.44])
 by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id 9BbfeXCv2rNl for <enum@ietfa.amsl.com>;
 Mon,  1 Jul 2019 22:44:13 -0700 (PDT)
Received: from mail.frobbit.se (mail.frobbit.se [85.30.129.185])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by ietfa.amsl.com (Postfix) with ESMTPS id 43A4512004D
 for <enum@ietf.org>; Mon,  1 Jul 2019 22:44:12 -0700 (PDT)
Received: from [192.168.10.197]
 (c-41f8d954.24605-0-69706f6e6c79.bbcust.telenor.se [84.217.248.65])
 by mail.frobbit.se (Postfix) with ESMTPSA id 088F828393;
 Tue,  2 Jul 2019 07:44:03 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=frobbit.se; s=mail;
 t=1562046249; bh=8e/xyINirtglnMrJC7XJWJlAY/nAUiokm7cgwMdP18E=;
 h=From:To:Cc:Subject:Date:In-Reply-To:References:From;
 b=DxgyyFM3c/mVmjHB/8E3+2aHD4BG/xg4Wn2TDHyFPDFfs+af7a8sSU80cl/9UJ9Q3
 AJakzugvZIOvHMLY2Rma4vYIF5jiBMWdN4x+cXhfBnAZvacooIMuR4AFRjBp++WzeH
 XtDUHAyhjszp7+nso0uW+b82nGe0ky7NRIEulV0Q=
From: "Patrik =?utf-8?b?RsOkbHRzdHLDtm0=?=" <paf@frobbit.se>
To: "Livingood, Jason" <Jason_Livingood@comcast.com>
Cc: "Olivier Guillard / AFNIC" <Olivier.Guillard@nic.fr>,
 "Jaap Akkerhuis" <jaap@NLnetLabs.nl>, "IETF ENUM list" <enum@ietf.org>,
 "Bernie Hoeneisen" <bernie@ietf.hoeneisen.ch>
Date: Tue, 02 Jul 2019 07:43:52 +0200
X-Mailer: MailMate (1.12.5r5635)
Message-ID: <2249F1CB-D46E-40DE-88DC-4817D667A447@frobbit.se>
In-Reply-To: <B85F0E22-A837-43A4-A8B7-B271223F88DD@cable.comcast.com>
References: <201901141410.x0EEAegF082526@bela.nlnetlabs.nl>
 <alpine.DEB.2.20.1901141529160.28417@softronics.hoeneisen.ch>
 <201901151217.x0FCHoCj066558@bela.nlnetlabs.nl>
 <20190627134744.GA18924@civette.prive.nic.fr>
 <B85F0E22-A837-43A4-A8B7-B271223F88DD@cable.comcast.com>
MIME-Version: 1.0
Content-Type: multipart/signed;
 boundary="=_MailMate_C543949D-9118-46DA-B850-654221555131_=";
 micalg=pgp-sha1; protocol="application/pgp-signature"
Archived-At: <https://mailarchive.ietf.org/arch/msg/enum/Fbo-911ZPOfK1hZnkmbEUfReltc>
Subject: Re: [Enum] 5 years since last message
X-BeenThere: enum@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Enum Discussion List <enum.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/enum>,
 <mailto:enum-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/enum/>
List-Post: <mailto:enum@ietf.org>
List-Help: <mailto:enum-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/enum>,
 <mailto:enum-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Jul 2019 05:44:16 -0000

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" <enum-bounces@ietf.org on behalf of Olivier.Guillard@nic.fr> 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
>     > enum@ietf.org
>     > https://www.ietf.org/mailman/listinfo/enum
>
>     --
>     Olivier
>
>     _______________________________________________
>     enum mailing list
>     enum@ietf.org
>     https://www.ietf.org/mailman/listinfo/enum
>
>
> _______________________________________________
> enum mailing list
> enum@ietf.org
> 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_=--

