Re: [Enum] ENUM Query

Bernie Hoeneisen <bernie@ietf.hoeneisen.ch> Fri, 13 March 2020 20:21 UTC

Return-Path: <bernie@ietf.hoeneisen.ch>
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 E93F63A0E05 for <enum@ietfa.amsl.com>; Fri, 13 Mar 2020 13:21:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 LoB6WSbAJi0q for <enum@ietfa.amsl.com>; Fri, 13 Mar 2020 13:21:05 -0700 (PDT)
Received: from softronics.hoeneisen.ch (softronics.hoeneisen.ch [62.2.86.178]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8DB273A0DD1 for <enum@ietf.org>; Fri, 13 Mar 2020 13:21:04 -0700 (PDT)
Received: from localhost ([127.0.0.1]) by softronics.hoeneisen.ch with esmtp (Exim 4.86_2) (envelope-from <bernie@ietf.hoeneisen.ch>) id 1jCqnk-00065E-Qh; Fri, 13 Mar 2020 21:21:00 +0100
Date: Fri, 13 Mar 2020 21:21:00 +0100 (CET)
From: Bernie Hoeneisen <bernie@ietf.hoeneisen.ch>
X-X-Sender: bhoeneis@softronics.hoeneisen.ch
To: Brian Rosen <br@brianrosen.net>
cc: IETF ENUM WG <enum@ietf.org>
In-Reply-To: <0482B082-5F82-47C8-BA23-41F027FDBA18@brianrosen.net>
Message-ID: <alpine.DEB.2.20.2003132049460.23158@softronics.hoeneisen.ch>
References: =?utf-8?q?=3CDB7PR04MB54183341C4145762B969A0B1C3E40=40DB7PR04MB5?= =?utf-8?q?418=2Eeurprd04=2Eprod=2Eoutlook=2Ecom=3E_=3CDB7PR04MB54186234B942?= =?utf-8?q?64FEA913888EC3E50=40DB7PR04MB5418=2Eeurprd04=2Eprod=2Eoutlook=2Ec?= =?utf-8?q?om=3E?= =?utf-8?q?=3Calpine=2EDEB=2E2=2E20=2E2003071103230=2E19506=40softronics=2Eh?= =?utf-8?q?oeneisen=2Ech=3E_=3CDB7PR04MB5418E392AD73AF330044E0F2C3FE0=40DB7P?= =?utf-8?q?R04MB5418=2Eeurprd04=2Eprod=2Eoutlook=2Ecom=3E?= <alpine.DEB.2.20.2003091520500.23510@softronics.hoeneisen.ch> =?utf-8?q?=3CA7704953-E79C-4835-9AE1-A97A567E37FC=40brianrosen=2Enet=3E_=3C?= =?utf-8?q?DB7PR04MB5418B9E732C770A3BC0788FBC3FA0=40DB7PR04MB5418=2Eeurprd04?= =?utf-8?q?=2Eprod=2Eoutlook=2Ecom=3E?= =?utf-8?q?=3CCAOPrzE14Sabbc3TEBm6n2ApPkQPTU2NyVkszuDCcGQzNPE4uYg=40mail=2Eg?= =?utf-8?q?mail=2Ecom=3E_=3CDB7PR04MB541844CC8809562BC5EB407AC3FA0=40DB7PR04?= =?utf-8?q?MB5418=2Eeurprd04=2Eprod=2Eoutlook=2Ecom=3E?= <CAOPrzE3zxuM3Ltfpr9Q_VhOKbLFVXRvtZgexG104Yw+Ed-BGHA@mail.gmail.com> <FD701EE7-989E-4478-A579-42FA40627AF4@shockey.us> <CAOPrzE1OehHB3aG4OQ2ShdYqztOQ5LCuNLOKKfHuRL=4u10gcA@mail.gmail.com> <1E380AD3-F462-4BE0-B22E-818B1C355A3B@rfc1035.com> <0482B082-5F82-47C8-BA23-41F027FDBA18@brianrosen.net>
User-Agent: Alpine 2.20 (DEB 67 2015-01-07)
MIME-Version: 1.0
Content-Type: multipart/mixed; BOUNDARY="37663318-1651444003-1584129119=:23158"
Content-ID: <alpine.DEB.2.20.2003132052050.23158@softronics.hoeneisen.ch>
X-SA-Exim-Connect-IP: 127.0.0.1
X-SA-Exim-Mail-From: bernie@ietf.hoeneisen.ch
X-SA-Exim-Scanned: No (on softronics.hoeneisen.ch); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/enum/71SFyjk4Wbfdv0jEH66Z2rYlFHs>
Subject: Re: [Enum] ENUM Query
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: Fri, 13 Mar 2020 20:21:08 -0000

Brian,

As you likely know, I am the Designated Expert for ENUM appointed by the 
IESG and my tasks is to sort out questions like this. The process as 
defined in RFC 6117 includes community review and I will ensure this is 
happening. In fact my first action was to point Wayne to this list (after 
I was contacted by IANA acting as a relay), so that the community can 
engage.

Which people/groups beyond the community subscribed to this ENUM list you 
believe are essential to engage in this case?

YMMV, but I can't see a point to run this through the whole IETF process, 
as the know-how on ENUM beyond this list is rather limited, i.e. we gain 
almost nothing if we did. On the other hand, we increase the workload of 
many people, most having little clue on what ENUM is about.

As a member of the current NomCom I learned that IESG workload related to 
document review is a major challenge its members, so let's not add even 
more to their pile, if there is little to gain.

cheers,
  Bernie




--

http://ucom.ch/
Modern Telephony Solutions and Tech Consulting for Internet Technology


On Fri, 13 Mar 2020, Brian Rosen wrote:

> Because it’s somewhat of a change of what we previously thought of as an 
> enumservice.  I do think it’s the right thing to do, but I would want 
> the community to review that.
> 
> “We” = IETF.  I can’t speak for the community, this is just my personal 
> opinion.
>
> In the end, the IESG would decide if they object to independent stream, 
> assuming that it’s done that way.
>
> Not worth a lot of argument, IMO.
>
> Brian
>
>
>> On Mar 13, 2020, at 12:14 PM, Jim Reid <jim@rfc1035.com> wrote:
>> 
>> 
>> 
>>> On 13 Mar 2020, at 16:00, Brian Rosen <br@brianrosen.net> wrote:
>>> 
>>> I think we want the full review that AD sponsored gets.  Independent stream just gets the “We don’t object” review. 
>>> 
>>> In this case I think we want the full review. 
>> 
>> Why? Could you define “we” too?
>> 
>> What’s the problem with just defining a new enumservice and being done with it?
>> 
>> New DNS RRtypes don’t need AD review and I think that should apply to new enumservices too.
>> 
>
> _______________________________________________
> enum mailing list
> enum@ietf.org
> https://www.ietf.org/mailman/listinfo/enum