From gonzalo.camarillo@ericsson.com Fri Sep 10 05:55:36 2010 Return-Path: X-Original-To: enum@core3.amsl.com Delivered-To: enum@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B0B393A6A48 for ; Fri, 10 Sep 2010 05:55:36 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -105.823 X-Spam-Level: X-Spam-Status: No, score=-105.823 tagged_above=-999 required=5 tests=[AWL=0.776, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nOdlgFW1Iwbc for ; Fri, 10 Sep 2010 05:55:36 -0700 (PDT) Received: from mailgw10.se.ericsson.net (mailgw10.se.ericsson.net [193.180.251.61]) by core3.amsl.com (Postfix) with ESMTP id 9F3D93A685A for ; Fri, 10 Sep 2010 05:55:35 -0700 (PDT) X-AuditID: c1b4fb3d-b7b90ae00000278d-09-4c8a2ae26ca6 Received: from esealmw126.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw10.se.ericsson.net (Symantec Mail Security) with SMTP id C5.4A.10125.2EA2A8C4; Fri, 10 Sep 2010 14:56:02 +0200 (CEST) Received: from esealmw126.eemea.ericsson.se ([153.88.254.174]) by esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.3959); Fri, 10 Sep 2010 14:56:01 +0200 Received: from [131.160.37.44] ([131.160.37.44]) by esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.3959); Fri, 10 Sep 2010 14:56:01 +0200 Message-ID: <4C8A2AE1.105@ericsson.com> Date: Fri, 10 Sep 2010 15:56:01 +0300 From: Gonzalo Camarillo User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.2.8) Gecko/20100802 Thunderbird/3.1.2 MIME-Version: 1.0 To: enum@ietf.org X-Enigmail-Version: 1.1.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 10 Sep 2010 12:56:01.0842 (UTC) FILETIME=[858C4120:01CB50E7] X-Brightmail-Tracker: AAAAAA== Subject: [Enum] Way forward after the ENUM trilogy X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Enum Discussion List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Sep 2010 12:55:36 -0000 Hi, as you know, we are currently focusing on getting the ENUM trilogy approved. In addition to the ENUM trilogy, there are a number of ENUM drafts. This is how we intend to handle them: draft-ietf-enum-edns0-00 This draft will be abandoned because a DNSEXT document already provides the same functionality. draft-ietf-enum-iax-05 This draft will be updated to comply with enumservices-guide as soon as enumservices-guide is approved. draft-ietf-enum-cnam-08 draft-ietf-enum-unused-04 The ENUM WG will not work on these drafts any longer because the issues these drafts deal with are being discussed in a wider context within the E2MD initiative. We would like to update the milestones in the charter according to this plan. Your input on this plan is very welcome. Thanks, Gonzalo From bernie@ietf.hoeneisen.ch Fri Sep 10 06:33:50 2010 Return-Path: X-Original-To: enum@core3.amsl.com Delivered-To: enum@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3AAD83A6A4B for ; Fri, 10 Sep 2010 06:33:50 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.968 X-Spam-Level: X-Spam-Status: No, score=-102.968 tagged_above=-999 required=5 tests=[AWL=-0.369, BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IKRyozDnh9PO for ; Fri, 10 Sep 2010 06:33:45 -0700 (PDT) Received: from softronics.hoeneisen.ch (softronics.hoeneisen.ch [62.2.86.178]) by core3.amsl.com (Postfix) with ESMTP id 246A83A68B6 for ; Fri, 10 Sep 2010 06:33:43 -0700 (PDT) Received: from localhost ([127.0.0.1]) by softronics.hoeneisen.ch with esmtp (Exim 4.69) (envelope-from ) id 1Ou3k1-00069Z-HQ for enum@ietf.org; Fri, 10 Sep 2010 15:34:09 +0200 Date: Fri, 10 Sep 2010 15:34:09 +0200 (CEST) From: Bernie Hoeneisen X-X-Sender: bhoeneis@softronics.hoeneisen.ch To: IETF ENUM list Message-ID: User-Agent: Alpine 2.00 (DEB 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII 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 Subject: [Enum] Feedback by 2010-09-24 (was: Way forward after the ENUM trilogy) X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Enum Discussion List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Sep 2010 13:33:50 -0000 Dear ENUM WG members Our shephering AD has just made a proposal on how to proceed with the ENUM WG documents that are residing in the publication queue after the 3 main ENUM WG documents (the ENUM Trilogy) will have been approved (see below). Any feedback concerning this proposal is expected to . by Fri, 24th of September 2010 After this deadline, the final decision will be made concerning these documents. All the best, Bernie, co-chair of the ENUM WG -- http://ucom.ch/ Tech Consulting for Internet Standardization ---------- Forwarded message ---------- Date: Fri, 10 Sep 2010 14:56:01 From: Gonzalo Camarillo To: enum@ietf.org Subject: [Enum] Way forward after the ENUM trilogy Hi, as you know, we are currently focusing on getting the ENUM trilogy approved. In addition to the ENUM trilogy, there are a number of ENUM drafts. This is how we intend to handle them: draft-ietf-enum-edns0-00 This draft will be abandoned because a DNSEXT document already provides the same functionality. draft-ietf-enum-iax-05 This draft will be updated to comply with enumservices-guide as soon as enumservices-guide is approved. draft-ietf-enum-cnam-08 draft-ietf-enum-unused-04 The ENUM WG will not work on these drafts any longer because the issues these drafts deal with are being discussed in a wider context within the E2MD initiative. We would like to update the milestones in the charter according to this plan. Your input on this plan is very welcome. Thanks, Gonzalo _______________________________________________ enum mailing list enum@ietf.org https://www.ietf.org/mailman/listinfo/enum From richard@shockey.us Fri Sep 10 08:10:30 2010 Return-Path: X-Original-To: enum@core3.amsl.com Delivered-To: enum@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 240AB3A68D9 for ; Fri, 10 Sep 2010 08:10:29 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -101.539 X-Spam-Level: X-Spam-Status: No, score=-101.539 tagged_above=-999 required=5 tests=[AWL=-0.763, BAYES_05=-1.11, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bhpuJ0GWNnvA for ; Fri, 10 Sep 2010 08:10:25 -0700 (PDT) Received: from oproxy3-pub.bluehost.com (oproxy3-pub.bluehost.com [69.89.21.8]) by core3.amsl.com (Postfix) with SMTP id 3EC253A68DB for ; Fri, 10 Sep 2010 08:10:23 -0700 (PDT) Received: (qmail 23595 invoked by uid 0); 10 Sep 2010 15:10:44 -0000 Received: from unknown (HELO box462.bluehost.com) (74.220.219.62) by oproxy3.bluehost.com with SMTP; 10 Sep 2010 15:10:44 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=shockey.us; h=Received:From:To:References:In-Reply-To:Subject:Date:Message-ID:MIME-Version:Content-Type:Content-Transfer-Encoding:X-Mailer:Content-language:Thread-index:X-Identified-User; b=NbHrGwH6spXkZcNXfAayI9R4IidrnO+WsV+2ZGDpa6x/6bfH56x72//JeFw5ZowuMR1c4Hx0EmZlLlwoDaSrww90EM82h5rskNDvsTx6y1J7js7N6na+gtMhfaMyYODB; Received: from pool-173-79-200-247.washdc.fios.verizon.net ([173.79.200.247] helo=RSHOCKEYPC) by box462.bluehost.com with esmtpa (Exim 4.69) (envelope-from ) id 1Ou5FT-0000Vd-Tm; Fri, 10 Sep 2010 09:10:44 -0600 From: "Richard Shockey" To: "'Gonzalo Camarillo'" , References: <4C8A2AE1.105@ericsson.com> In-Reply-To: <4C8A2AE1.105@ericsson.com> Date: Fri, 10 Sep 2010 11:10:40 -0400 Message-ID: <00b101cb50fa$556a0a50$003e1ef0$@us> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 12.0 Content-language: en-us Thread-index: ActQ54duX7XDrGR1Tt+G+T4N99FNzwAErraA X-Identified-User: {3286:box462.bluehost.com:shockeyu:shockey.us} {sentby:smtp auth 173.79.200.247 authed with richard@shockey.us} Subject: Re: [Enum] Way forward after the ENUM trilogy X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Enum Discussion List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Sep 2010 15:10:32 -0000 +1 This is a sensible plan and I have no objections to it. -----Original Message----- From: enum-bounces@ietf.org [mailto:enum-bounces@ietf.org] On Behalf Of Gonzalo Camarillo Sent: Friday, September 10, 2010 8:56 AM To: enum@ietf.org Subject: [Enum] Way forward after the ENUM trilogy Hi, as you know, we are currently focusing on getting the ENUM trilogy approved. In addition to the ENUM trilogy, there are a number of ENUM drafts. This is how we intend to handle them: draft-ietf-enum-edns0-00 This draft will be abandoned because a DNSEXT document already provides the same functionality. draft-ietf-enum-iax-05 This draft will be updated to comply with enumservices-guide as soon as enumservices-guide is approved. draft-ietf-enum-cnam-08 draft-ietf-enum-unused-04 The ENUM WG will not work on these drafts any longer because the issues these drafts deal with are being discussed in a wider context within the E2MD initiative. We would like to update the milestones in the charter according to this plan. Your input on this plan is very welcome. Thanks, Gonzalo _______________________________________________ enum mailing list enum@ietf.org https://www.ietf.org/mailman/listinfo/enum From peter@denic.de Fri Sep 10 10:56:52 2010 Return-Path: X-Original-To: enum@core3.amsl.com Delivered-To: enum@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id F25F33A68CD for ; Fri, 10 Sep 2010 10:56:51 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.911 X-Spam-Level: X-Spam-Status: No, score=-5.911 tagged_above=-999 required=5 tests=[AWL=0.338, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-4] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xtwrAFDioHPP for ; Fri, 10 Sep 2010 10:56:51 -0700 (PDT) Received: from office.denic.de (gw-office.denic.de [81.91.160.182]) by core3.amsl.com (Postfix) with ESMTP id 075873A67EB for ; Fri, 10 Sep 2010 10:56:50 -0700 (PDT) Received: from x27.adm.denic.de ([10.122.64.128]) by office.denic.de with esmtp id 1Ou7qe-000079-FQ; Fri, 10 Sep 2010 19:57:16 +0200 Received: from localhost by x27.adm.denic.de with local id 1Ou7qe-0003Xp-BL; Fri, 10 Sep 2010 19:57:16 +0200 Date: Fri, 10 Sep 2010 19:57:16 +0200 From: Peter Koch To: Bernie Hoeneisen Message-ID: <20100910175716.GJ28543@x27.adm.denic.de> Mail-Followup-To: Bernie Hoeneisen , IETF ENUM list References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.3i Sender: Peter Koch Cc: IETF ENUM list Subject: Re: [Enum] Feedback by 2010-09-24 (was: Way forward after the ENUM trilogy) X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Enum Discussion List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Sep 2010 17:56:52 -0000 Bernie, WG, On Fri, Sep 10, 2010 at 03:34:09PM +0200, Bernie Hoeneisen wrote: > Our shephering AD has just made a proposal on how to proceed with the ENUM > WG documents that are residing in the publication queue after the 3 main > ENUM WG documents (the ENUM Trilogy) will have been approved (see below). Gonzalo> We would like to update the milestones in the charter according to this Gonzalo> plan. Your input on this plan is very welcome. isn't this a lot of prose to describe the empty set? In other words, can we expect the WG to be closed after victory will have been declared? > draft-ietf-enum-iax-05 > This draft will be updated to comply with enumservices-guide as soon > as enumservices-guide is approved. No objection to any part of the plan, just to remark that with the new registration guidelines there's no real need for a WG document anymore. That is, this one does not have to extend the wg's lifetime, even if it gets published later. We can now start talking about an ENUM Operations WG. -Peter (only half kidding) From richard@shockey.us Fri Sep 10 11:26:25 2010 Return-Path: X-Original-To: enum@core3.amsl.com Delivered-To: enum@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7282E3A68FE for ; Fri, 10 Sep 2010 11:26:25 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.22 X-Spam-Level: X-Spam-Status: No, score=-102.22 tagged_above=-999 required=5 tests=[AWL=0.045, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AtHHA5VNbSaB for ; Fri, 10 Sep 2010 11:26:24 -0700 (PDT) Received: from oproxy3-pub.bluehost.com (oproxy3-pub.bluehost.com [69.89.21.8]) by core3.amsl.com (Postfix) with SMTP id 5CB8B3A68D2 for ; Fri, 10 Sep 2010 11:26:24 -0700 (PDT) Received: (qmail 9859 invoked by uid 0); 10 Sep 2010 18:26:51 -0000 Received: from unknown (HELO box462.bluehost.com) (74.220.219.62) by oproxy3.bluehost.com with SMTP; 10 Sep 2010 18:26:51 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=shockey.us; h=Received:From:To:Cc:References:In-Reply-To:Subject:Date:Message-ID:MIME-Version:Content-Type:Content-Transfer-Encoding:X-Mailer:Content-language:Thread-index:X-Identified-User; b=nC12AXvAP+oqbuQQbLpfo/Si5idilyvK/pYibfksjDBuTxv8iyKO9w5yiiNx+tuDIOtpJAZnZQ5BwzcWks1MO7fbqwg/4x+xHx7eZIuZEYel29MExax6Xv6XHCJZYtKd; Received: from pool-173-79-200-247.washdc.fios.verizon.net ([173.79.200.247] helo=RSHOCKEYPC) by box462.bluehost.com with esmtpa (Exim 4.69) (envelope-from ) id 1Ou8JH-0008M4-6p; Fri, 10 Sep 2010 12:26:51 -0600 From: "Richard Shockey" To: "'Peter Koch'" , "'Bernie Hoeneisen'" References: <20100910175716.GJ28543@x27.adm.denic.de> In-Reply-To: <20100910175716.GJ28543@x27.adm.denic.de> Date: Fri, 10 Sep 2010 14:26:47 -0400 Message-ID: <010f01cb5115$bb431590$31c940b0$@us> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 12.0 Content-language: en-us Thread-index: ActREZ2Qjy+zIlUsQ36pk1bJIly4UwAA6VBQ X-Identified-User: {3286:box462.bluehost.com:shockeyu:shockey.us} {sentby:smtp auth 173.79.200.247 authed with richard@shockey.us} Cc: 'IETF ENUM list' Subject: Re: [Enum] Feedback by 2010-09-24 (was: Way forward after the ENUM trilogy) X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Enum Discussion List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Sep 2010 18:26:25 -0000 -----Original Message----- From: enum-bounces@ietf.org [mailto:enum-bounces@ietf.org] On Behalf Of Peter Koch Sent: Friday, September 10, 2010 1:57 PM To: Bernie Hoeneisen Cc: IETF ENUM list Subject: Re: [Enum] Feedback by 2010-09-24 (was: Way forward after the ENUM trilogy) Bernie, WG, On Fri, Sep 10, 2010 at 03:34:09PM +0200, Bernie Hoeneisen wrote: > Our shephering AD has just made a proposal on how to proceed with the ENUM > WG documents that are residing in the publication queue after the 3 main > ENUM WG documents (the ENUM Trilogy) will have been approved (see below). Gonzalo> We would like to update the milestones in the charter according to this Gonzalo> plan. Your input on this plan is very welcome. isn't this a lot of prose to describe the empty set? In other words, can we expect the WG to be closed after victory will have been declared? RS> I certainly hope so .. I see no reason why the WG should remain open after the trilogy is approved by the IESG. We're done . > draft-ietf-enum-iax-05 > This draft will be updated to comply with enumservices-guide as soon > as enumservices-guide is approved. No objection to any part of the plan, just to remark that with the new registration guidelines there's no real need for a WG document anymore. That is, this one does not have to extend the wg's lifetime, even if it gets published later. We can now start talking about an ENUM Operations WG. -Peter (only half kidding) RS> Well there are enough private ENUM systems out there to almost justify it ... ( only half kidding as well) From bernie@ietf.hoeneisen.ch Sun Sep 12 02:09:09 2010 Return-Path: X-Original-To: enum@core3.amsl.com Delivered-To: enum@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 64E083A684F for ; Sun, 12 Sep 2010 02:09:09 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.952 X-Spam-Level: X-Spam-Status: No, score=-102.952 tagged_above=-999 required=5 tests=[AWL=-0.353, BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eEWso2yPIFLx for ; Sun, 12 Sep 2010 02:09:08 -0700 (PDT) Received: from softronics.hoeneisen.ch (softronics.hoeneisen.ch [62.2.86.178]) by core3.amsl.com (Postfix) with ESMTP id 6DFD43A6846 for ; Sun, 12 Sep 2010 02:09:08 -0700 (PDT) Received: from localhost ([127.0.0.1]) by softronics.hoeneisen.ch with esmtp (Exim 4.69) (envelope-from ) id 1OuiZ2-0007xt-M3; Sun, 12 Sep 2010 11:09:32 +0200 Date: Sun, 12 Sep 2010 11:09:32 +0200 (CEST) From: Bernie Hoeneisen X-X-Sender: bhoeneis@softronics.hoeneisen.ch To: Peter Koch In-Reply-To: <20100910175716.GJ28543@x27.adm.denic.de> Message-ID: References: <20100910175716.GJ28543@x27.adm.denic.de> User-Agent: Alpine 2.00 (DEB 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII 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 Cc: IETF ENUM list , draft-ietf-enum-iax@tools.ietf.org Subject: [Enum] draft-ietf-enum-iax (was: Feedback by 2010-09-24 (was: Way forward after the ENUM trilogy)) X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Enum Discussion List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 12 Sep 2010 09:09:09 -0000 Hi Peter et al. On Fri, 10 Sep 2010, Peter Koch wrote: >> draft-ietf-enum-iax-05 >> This draft will be updated to comply with enumservices-guide as soon >> as enumservices-guide is approved. > > No objection to any part of the plan, just to remark that with the new > registration guidelines there's no real need for a WG document anymore. > That is, this one does not have to extend the wg's lifetime, even if it gets > published later. To mitigate potential confusion: We do not intend to change the publication process for draft-ietf-enum-iax, i.e. it will be processed as ENUM WG Document via the ENUM publication queue. draft-ietf-enum-iax is straight-forward, not controversial and currently awaiting the ENUM Triology. After we are set with the ENUM Trilogy, draft-ietf-enum-iax is to be updated to comply with the new rules (according to draft-ietf-enum-enumservices-guide) and published as (Informational) RFC. [IMHO, looking for a new home for draft-ietf-enum-iax, just for the sake of shutting down the ENUM WG a little bit earlier does not justify the increased management effort.] cheers, Bernie, ENUM WG co-chair From root@core3.amsl.com Mon Sep 13 08:30:03 2010 Return-Path: X-Original-To: enum@ietf.org Delivered-To: enum@core3.amsl.com Received: by core3.amsl.com (Postfix, from userid 0) id 16FD63A69F5; Mon, 13 Sep 2010 08:30:01 -0700 (PDT) From: Internet-Drafts@ietf.org To: i-d-announce@ietf.org Content-Type: Multipart/Mixed; Boundary="NextPart" Mime-Version: 1.0 Message-Id: <20100913153003.16FD63A69F5@core3.amsl.com> Date: Mon, 13 Sep 2010 08:30:01 -0700 (PDT) Cc: enum@ietf.org Subject: [Enum] I-D Action:draft-ietf-enum-enumservices-guide-21.txt X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Enum Discussion List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Sep 2010 15:30:03 -0000 --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Telephone Number Mapping Working Group of the IETF. Title : IANA Registration of Enumservices: Guide, Template and IANA Considerations Author(s) : B. Hoeneisen, et al. Filename : draft-ietf-enum-enumservices-guide-21.txt Pages : 49 Date : 2010-09-13 This document specifies a revision of the IANA Registration Guidelines for Enumservices, describes corresponding registration procedures, and provides a guideline for creating Enumservice Specifications. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-enum-enumservices-guide-21.txt Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Message/External-body; name="draft-ietf-enum-enumservices-guide-21.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2010-09-13082101.I-D@ietf.org> --NextPart-- From bernie@ietf.hoeneisen.ch Mon Sep 13 08:49:44 2010 Return-Path: X-Original-To: enum@core3.amsl.com Delivered-To: enum@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 58E803A6A01 for ; Mon, 13 Sep 2010 08:49:44 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.937 X-Spam-Level: X-Spam-Status: No, score=-102.937 tagged_above=-999 required=5 tests=[AWL=-0.338, BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ikz5R10-raFr for ; Mon, 13 Sep 2010 08:49:40 -0700 (PDT) Received: from softronics.hoeneisen.ch (softronics.hoeneisen.ch [62.2.86.178]) by core3.amsl.com (Postfix) with ESMTP id 7CAB93A69E2 for ; Mon, 13 Sep 2010 08:49:39 -0700 (PDT) Received: from localhost ([127.0.0.1]) by softronics.hoeneisen.ch with esmtp (Exim 4.69) (envelope-from ) id 1OvBIB-0004QB-DY; Mon, 13 Sep 2010 17:50:03 +0200 Date: Mon, 13 Sep 2010 17:50:03 +0200 (CEST) From: Bernie Hoeneisen X-X-Sender: bhoeneis@softronics.hoeneisen.ch To: IETF ENUM list In-Reply-To: <20100913153003.16FD63A69F5@core3.amsl.com> Message-ID: References: <20100913153003.16FD63A69F5@core3.amsl.com> User-Agent: Alpine 2.00 (DEB 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII 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 Cc: Gonzalo Camarillo Subject: Re: [Enum] I-D Action:draft-ietf-enum-enumservices-guide-21.txt X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Enum Discussion List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Sep 2010 15:49:44 -0000 Status-Update draft-ietf-enum-enumservices-guide: We just published an interim revision (actually the state we were to publish already during IETF-78). It fully addresses all DISCUSSes, except David Harrington's, which needed clarification. In the meantime David clarified his DISCUSS and we are currently working on it. We aim to resolve this last DISCUSS soon. Looking forward to -22! cheers, Bernie, Alex and Jason On Mon, 13 Sep 2010, Internet-Drafts@ietf.org wrote: > A New Internet-Draft is available from the on-line Internet-Drafts directories. > This draft is a work item of the Telephone Number Mapping Working Group of the IETF. > > > Title : IANA Registration of Enumservices: Guide, Template and IANA Considerations > Author(s) : B. Hoeneisen, et al. > Filename : draft-ietf-enum-enumservices-guide-21.txt > Pages : 49 > Date : 2010-09-13 > > This document specifies a revision of the IANA Registration > Guidelines for Enumservices, describes corresponding registration > procedures, and provides a guideline for creating Enumservice > Specifications. > > A URL for this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-ietf-enum-enumservices-guide-21.txt > > Internet-Drafts are also available by anonymous FTP at: > ftp://ftp.ietf.org/internet-drafts/ > > Below is the data which will enable a MIME compliant mail reader > implementation to automatically retrieve the ASCII version of the > Internet-Draft. > From peter@denic.de Mon Sep 13 10:17:59 2010 Return-Path: X-Original-To: enum@core3.amsl.com Delivered-To: enum@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 80B4C3A693E for ; Mon, 13 Sep 2010 10:17:59 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.922 X-Spam-Level: X-Spam-Status: No, score=-5.922 tagged_above=-999 required=5 tests=[AWL=0.327, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-4] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BROXE6J5eYWx for ; Mon, 13 Sep 2010 10:17:56 -0700 (PDT) Received: from office.denic.de (gw-office.denic.de [81.91.160.182]) by core3.amsl.com (Postfix) with ESMTP id D20F03A6A6B for ; Mon, 13 Sep 2010 10:17:55 -0700 (PDT) Received: from x27.adm.denic.de ([10.122.64.128]) by office.denic.de with esmtp id 1OvCfa-0004Sx-1o; Mon, 13 Sep 2010 19:18:18 +0200 Received: from localhost by x27.adm.denic.de with local id 1OvCfZ-0001M7-U6; Mon, 13 Sep 2010 19:18:17 +0200 Date: Mon, 13 Sep 2010 19:18:17 +0200 From: Peter Koch To: Bernie Hoeneisen Message-ID: <20100913171817.GG29256@x27.adm.denic.de> Mail-Followup-To: Bernie Hoeneisen , IETF ENUM list , Gonzalo Camarillo References: <20100913153003.16FD63A69F5@core3.amsl.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.3i Sender: Peter Koch Cc: IETF ENUM list , Gonzalo Camarillo Subject: Re: [Enum] I-D Action:draft-ietf-enum-enumservices-guide-21.txt X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Enum Discussion List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Sep 2010 17:17:59 -0000 On Mon, Sep 13, 2010 at 05:50:03PM +0200, Bernie Hoeneisen wrote: > We just published an interim revision (actually the state we were to thanks, Bernie et al. > publish already during IETF-78). It fully addresses all DISCUSSes, except > David Harrington's, which needed clarification. In the meantime David > clarified his DISCUSS and we are currently working on it. We aim to > resolve this last DISCUSS soon. there's basicly two changes I could spot from the diff: 1) The draft now aims at "Standards Track" instead of BCP. This appears at least "interesting" for a process document. What is the motivation behind this? 2) The expert review process was carefully designed to give guidance to both the expert and the requester. The updated draft version now declares this non-normative, making it harder for the expert to insist on certain elements. I understand from partially following the discussion in the tracker that there were concerns redefining or overruling RFC 5226, but there is precedent for this sort of mandatory review guidelines and it is also appropriate to maintain a level of quality and interoperable specifications that fit the architecture. Several changes in the normative language seem acceptable or even appropriate, but the general relax clause is a step too far. See Section 3.2 of RFC 5226: "Ideally, the designated expert follows specific review criteria as documented with the protocol that creates or uses the namespace." -Peter From bernie@ietf.hoeneisen.ch Tue Sep 14 04:39:48 2010 Return-Path: X-Original-To: enum@core3.amsl.com Delivered-To: enum@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6D3443A6909 for ; Tue, 14 Sep 2010 04:39:39 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.915 X-Spam-Level: X-Spam-Status: No, score=-102.915 tagged_above=-999 required=5 tests=[AWL=-0.316, BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wJQNkipPFyyp for ; Tue, 14 Sep 2010 04:39:36 -0700 (PDT) Received: from softronics.hoeneisen.ch (softronics.hoeneisen.ch [62.2.86.178]) by core3.amsl.com (Postfix) with ESMTP id 0DB213A68E8 for ; Tue, 14 Sep 2010 04:39:35 -0700 (PDT) Received: from localhost ([127.0.0.1]) by softronics.hoeneisen.ch with esmtp (Exim 4.69) (envelope-from ) id 1OvTrh-0000eL-8j; Tue, 14 Sep 2010 13:39:57 +0200 Date: Tue, 14 Sep 2010 13:39:56 +0200 (CEST) From: Bernie Hoeneisen X-X-Sender: bhoeneis@softronics.hoeneisen.ch To: Peter Koch In-Reply-To: <20100913171817.GG29256@x27.adm.denic.de> Message-ID: References: <20100913153003.16FD63A69F5@core3.amsl.com> <20100913171817.GG29256@x27.adm.denic.de> User-Agent: Alpine 2.00 (DEB 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII 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 Cc: IETF ENUM list , David Harrington , Gonzalo Camarillo Subject: Re: [Enum] I-D Action:draft-ietf-enum-enumservices-guide-21.txt X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Enum Discussion List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Sep 2010 11:39:48 -0000 Hi Peter Thanks for your feedback. On Mon, 13 Sep 2010, Peter Koch wrote: > 1) The draft now aims at "Standards Track" instead of BCP. This appears > at least "interesting" for a process document. What is the motivation > behind this? We updated this on request from the IESG. I actually don't know what's the reasoning behind. @Gonzalo: Could you please clarify on this? > 2) The expert review process was carefully designed to give guidance to > both the expert and the requester. The updated draft version now > declares this non-normative, making it harder for the expert to > insist on certain elements. I understand from partially following > the discussion in the tracker that there were concerns redefining > or overruling RFC 5226, but there is precedent for this sort > of mandatory review guidelines and it is also appropriate to maintain > a level of quality and interoperable specifications that fit the > architecture. Several changes in the normative language seem > acceptable or even appropriate, but the general relax clause is > a step too far. See Section 3.2 of RFC 5226: "Ideally, the designated > expert follows specific review criteria as documented with the protocol > that creates or uses the namespace." We updated this based on the DISCUSS of Dave Harrington. I included Dave into this thread. @Dave: Could you please explain your concerns wtr. to the ENUM community? cheers, Bernie From gonzalo.camarillo@ericsson.com Tue Sep 14 05:18:44 2010 Return-Path: X-Original-To: enum@core3.amsl.com Delivered-To: enum@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A2EB03A6988 for ; Tue, 14 Sep 2010 05:18:44 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -106.032 X-Spam-Level: X-Spam-Status: No, score=-106.032 tagged_above=-999 required=5 tests=[AWL=0.567, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JfcDjb0pAvyl for ; Tue, 14 Sep 2010 05:18:43 -0700 (PDT) Received: from mailgw9.se.ericsson.net (mailgw9.se.ericsson.net [193.180.251.57]) by core3.amsl.com (Postfix) with ESMTP id 7635F3A6965 for ; Tue, 14 Sep 2010 05:18:43 -0700 (PDT) X-AuditID: c1b4fb39-b7b91ae000001aef-1b-4c8f683c0f32 Received: from esealmw126.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw9.se.ericsson.net (Symantec Mail Security) with SMTP id 4C.C8.06895.C386F8C4; Tue, 14 Sep 2010 14:19:08 +0200 (CEST) Received: from esealmw128.eemea.ericsson.se ([153.88.254.172]) by esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.3959); Tue, 14 Sep 2010 14:19:07 +0200 Received: from [131.160.37.44] ([131.160.37.44]) by esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.3959); Tue, 14 Sep 2010 14:19:07 +0200 Message-ID: <4C8F683B.1040403@ericsson.com> Date: Tue, 14 Sep 2010 15:19:07 +0300 From: Gonzalo Camarillo User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.2.8) Gecko/20100802 Thunderbird/3.1.2 MIME-Version: 1.0 To: Bernie Hoeneisen References: <20100913153003.16FD63A69F5@core3.amsl.com> <20100913171817.GG29256@x27.adm.denic.de> In-Reply-To: X-Enigmail-Version: 1.1.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 14 Sep 2010 12:19:07.0794 (UTC) FILETIME=[07865720:01CB5407] X-Brightmail-Tracker: AAAAAA== Cc: IETF ENUM list , Peter Koch , David Harrington Subject: Re: [Enum] I-D Action:draft-ietf-enum-enumservices-guide-21.txt X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Enum Discussion List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Sep 2010 12:18:44 -0000 Hi, >> 1) The draft now aims at "Standards Track" instead of BCP. This appears >> at least "interesting" for a process document. What is the motivation >> behind this? > > We updated this on request from the IESG. I actually don't know what's the > reasoning behind. > > @Gonzalo: Could you please clarify on this? the tracker's field contained PS but the document said BCP. The chairs (Richard) said that the plan had always been to go for PS and not for BCP, and the IESG did not have any problem with that. Cheers, Gonzalo From richard@shockey.us Tue Sep 14 05:52:27 2010 Return-Path: X-Original-To: enum@core3.amsl.com Delivered-To: enum@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0E3153A6958 for ; Tue, 14 Sep 2010 05:52:27 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.223 X-Spam-Level: X-Spam-Status: No, score=-102.223 tagged_above=-999 required=5 tests=[AWL=0.042, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UtT2bQXoanWp for ; Tue, 14 Sep 2010 05:52:26 -0700 (PDT) Received: from oproxy3-pub.bluehost.com (oproxy3-pub.bluehost.com [69.89.21.8]) by core3.amsl.com (Postfix) with SMTP id D58C33A695D for ; Tue, 14 Sep 2010 05:52:25 -0700 (PDT) Received: (qmail 10333 invoked by uid 0); 14 Sep 2010 12:52:51 -0000 Received: from unknown (HELO box462.bluehost.com) (74.220.219.62) by oproxy3.bluehost.com with SMTP; 14 Sep 2010 12:52:51 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=shockey.us; h=Received:From:To:Cc:References:In-Reply-To:Subject:Date:Message-ID:MIME-Version:Content-Type:Content-Transfer-Encoding:X-Mailer:Thread-Index:Content-Language:X-Identified-User; b=RxOEqRcyxgArAWwWbTPZe16JR9WhQcZ3uPNzKXSiiiqqX0kRHvakdEh0g6c3o9FjqKWC95I/uXHu5PQTR54wS0r1reziTMNiMOJ1chefQGe+trUHiTkDuTgKTUNYd9z0; Received: from pool-173-79-200-247.washdc.fios.verizon.net ([173.79.200.247] helo=RSHOCKEYPC) by box462.bluehost.com with esmtpa (Exim 4.69) (envelope-from ) id 1OvV0F-00083w-0G; Tue, 14 Sep 2010 06:52:51 -0600 From: "Richard Shockey" To: "'Gonzalo Camarillo'" , "'Bernie Hoeneisen'" References: <20100913153003.16FD63A69F5@core3.amsl.com> <20100913171817.GG29256@x27.adm.denic.de> <4C8F683B.1040403@ericsson.com> In-Reply-To: <4C8F683B.1040403@ericsson.com> Date: Tue, 14 Sep 2010 08:52:48 -0400 Message-ID: <025801cb540b$bcfa12f0$36ee38d0$@us> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: ActUBwoIRT+Wo+hLS26jWinBrgScUwABHFaA Content-Language: en-us X-Identified-User: {3286:box462.bluehost.com:shockeyu:shockey.us} {sentby:smtp auth 173.79.200.247 authed with richard@shockey.us} Cc: 'IETF ENUM list' , 'Peter Koch' , 'David Harrington' Subject: Re: [Enum] I-D Action:draft-ietf-enum-enumservices-guide-21.txt X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Enum Discussion List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Sep 2010 12:52:27 -0000 Gonzalo is correct. Fat thumb error. No conspiracy intended. Logically given the subject matter it's a PS. -----Original Message----- From: enum-bounces@ietf.org [mailto:enum-bounces@ietf.org] On Behalf Of Gonzalo Camarillo Sent: Tuesday, September 14, 2010 8:19 AM To: Bernie Hoeneisen Cc: IETF ENUM list; Peter Koch; David Harrington Subject: Re: [Enum] I-D Action:draft-ietf-enum-enumservices-guide-21.txt Hi, >> 1) The draft now aims at "Standards Track" instead of BCP. This appears >> at least "interesting" for a process document. What is the motivation >> behind this? > > We updated this on request from the IESG. I actually don't know what's the > reasoning behind. > > @Gonzalo: Could you please clarify on this? the tracker's field contained PS but the document said BCP. The chairs (Richard) said that the plan had always been to go for PS and not for BCP, and the IESG did not have any problem with that. Cheers, Gonzalo _______________________________________________ enum mailing list enum@ietf.org https://www.ietf.org/mailman/listinfo/enum From jim@rfc1035.com Tue Sep 14 07:41:23 2010 Return-Path: X-Original-To: enum@core3.amsl.com Delivered-To: enum@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8F6353A697D for ; Tue, 14 Sep 2010 07:41:23 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.599 X-Spam-Level: X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vEj9aUacMXDO for ; Tue, 14 Sep 2010 07:41:21 -0700 (PDT) Received: from hutch.rfc1035.com (router.rfc1035.com [195.54.233.65]) by core3.amsl.com (Postfix) with ESMTP id 694733A69A5 for ; Tue, 14 Sep 2010 07:41:21 -0700 (PDT) Received: from gromit.rfc1035.com (gromit.rfc1035.com [195.54.233.69]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: jim) by hutch.rfc1035.com (Postfix) with ESMTPSA id 83C29154202E for ; Tue, 14 Sep 2010 15:41:45 +0100 (BST) Message-Id: <458E89D6-9525-4633-B194-52F1AE8E427B@rfc1035.com> From: Jim Reid To: IETF ENUM list In-Reply-To: Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v936) Date: Tue, 14 Sep 2010 15:41:45 +0100 References: X-Mailer: Apple Mail (2.936) Subject: Re: [Enum] Way forward for the ENUM trilogy X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Enum Discussion List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Sep 2010 14:41:23 -0000 Hi Bernie. I'm long past caring about what happens with the two drafts I co-authored. Lawrence and Richard will probably share that opinion. Though they can speak for themselves. Although it is fine by me to give draft-ietf-enum-unused-04 a mercy killing, the reason given is a little misleading. The E2MD discussions don't really apply to the use cases that this draft was aimed at. [Mind you, there is an overlap.] However it's not worth making a fuss about that. It would be nice if there was a more accurate explanation for killing that draft. Lack of progress/interest following an AD review would be a more diplomatic way to put things. You might not want the death of this draft to pollute the future of E2MD. From peter@denic.de Tue Sep 14 15:09:05 2010 Return-Path: X-Original-To: enum@core3.amsl.com Delivered-To: enum@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1694C3A6AA8 for ; Tue, 14 Sep 2010 15:09:05 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.933 X-Spam-Level: X-Spam-Status: No, score=-5.933 tagged_above=-999 required=5 tests=[AWL=0.316, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-4] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Mb1404qDmLE9 for ; Tue, 14 Sep 2010 15:09:04 -0700 (PDT) Received: from office.denic.de (gw-office.denic.de [81.91.160.182]) by core3.amsl.com (Postfix) with ESMTP id E06863A69A1 for ; Tue, 14 Sep 2010 15:09:03 -0700 (PDT) Received: from x27.adm.denic.de ([10.122.64.128]) by office.denic.de with esmtp id 1Ovdgt-0006xj-RH; Wed, 15 Sep 2010 00:09:27 +0200 Received: from localhost by x27.adm.denic.de with local id 1Ovdgt-00079u-NT; Wed, 15 Sep 2010 00:09:27 +0200 Date: Wed, 15 Sep 2010 00:09:27 +0200 From: Peter Koch To: IETF ENUM WG Message-ID: <20100914220927.GB22824@x27.adm.denic.de> Mail-Followup-To: IETF ENUM WG , 'Gonzalo Camarillo' , 'David Harrington' References: <20100913153003.16FD63A69F5@core3.amsl.com> <20100913171817.GG29256@x27.adm.denic.de> <4C8F683B.1040403@ericsson.com> <025801cb540b$bcfa12f0$36ee38d0$@us> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <025801cb540b$bcfa12f0$36ee38d0$@us> User-Agent: Mutt/1.4.2.3i Sender: Peter Koch Cc: 'David Harrington' , 'Gonzalo Camarillo' Subject: Re: [Enum] I-D Action:draft-ietf-enum-enumservices-guide-21.txt X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Enum Discussion List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Sep 2010 22:09:05 -0000 On Tue, Sep 14, 2010 at 08:52:48AM -0400, Richard Shockey wrote: > Gonzalo is correct. Fat thumb error. No conspiracy intended. Logically > given the subject matter it's a PS. assuming that _this_ was now exactly that type of error :-), I'd like to point to and surrounding messages. In that discussion we concluded BCP was the appropriate status. Please understand, PS would not provide "more value" than BCP, but both categories just have different functions. Best regards, Peter From gonzalo.camarillo@ericsson.com Wed Sep 15 00:19:45 2010 Return-Path: X-Original-To: enum@core3.amsl.com Delivered-To: enum@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4863A3A6AAA for ; Wed, 15 Sep 2010 00:19:45 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -106.105 X-Spam-Level: X-Spam-Status: No, score=-106.105 tagged_above=-999 required=5 tests=[AWL=0.494, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 94DyaLJdDomY for ; Wed, 15 Sep 2010 00:19:44 -0700 (PDT) Received: from mailgw9.se.ericsson.net (mailgw9.se.ericsson.net [193.180.251.57]) by core3.amsl.com (Postfix) with ESMTP id BCDFC3A6830 for ; Wed, 15 Sep 2010 00:19:43 -0700 (PDT) X-AuditID: c1b4fb39-b7b91ae000001aef-31-4c9073a8fc94 Received: from esealmw127.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw9.se.ericsson.net (Symantec Mail Security) with SMTP id F5.B6.06895.8A3709C4; Wed, 15 Sep 2010 09:20:08 +0200 (CEST) Received: from esealmw129.eemea.ericsson.se ([153.88.254.177]) by esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.3959); Wed, 15 Sep 2010 09:20:08 +0200 Received: from [131.160.126.132] ([131.160.126.132]) by esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.3959); Wed, 15 Sep 2010 09:20:07 +0200 Message-ID: <4C9073A7.9030308@ericsson.com> Date: Wed, 15 Sep 2010 10:20:07 +0300 From: Gonzalo Camarillo User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.2.8) Gecko/20100802 Thunderbird/3.1.2 MIME-Version: 1.0 To: IETF ENUM WG , 'David Harrington' References: <20100913153003.16FD63A69F5@core3.amsl.com> <20100913171817.GG29256@x27.adm.denic.de> <4C8F683B.1040403@ericsson.com> <025801cb540b$bcfa12f0$36ee38d0$@us> <20100914220927.GB22824@x27.adm.denic.de> In-Reply-To: <20100914220927.GB22824@x27.adm.denic.de> X-Enigmail-Version: 1.1.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 15 Sep 2010 07:20:07.0833 (UTC) FILETIME=[6CE34890:01CB54A6] X-Brightmail-Tracker: AAAAAA== Subject: Re: [Enum] I-D Action:draft-ietf-enum-enumservices-guide-21.txt X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Enum Discussion List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Sep 2010 07:19:45 -0000 Hi, I will discuss this with the IESG and let you know how to proceed. Thanks, Gonzalo On 15/09/2010 1:09 AM, Peter Koch wrote: > On Tue, Sep 14, 2010 at 08:52:48AM -0400, Richard Shockey wrote: >> Gonzalo is correct. Fat thumb error. No conspiracy intended. Logically >> given the subject matter it's a PS. > > assuming that _this_ was now exactly that type of error :-), I'd like to > point to > and surrounding messages. In that discussion we concluded BCP was the > appropriate status. Please understand, PS would not provide "more value" > than BCP, but both categories just have different functions. > > Best regards, > Peter From bernie@ietf.hoeneisen.ch Sun Sep 19 00:37:36 2010 Return-Path: X-Original-To: enum@core3.amsl.com Delivered-To: enum@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 77B013A699D; Sun, 19 Sep 2010 00:37:36 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.903 X-Spam-Level: X-Spam-Status: No, score=-102.903 tagged_above=-999 required=5 tests=[AWL=-0.304, BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Z2sJZaMXpTTq; Sun, 19 Sep 2010 00:37:34 -0700 (PDT) Received: from softronics.hoeneisen.ch (softronics.hoeneisen.ch [62.2.86.178]) by core3.amsl.com (Postfix) with ESMTP id BF4593A6A20; Sun, 19 Sep 2010 00:37:28 -0700 (PDT) Received: from localhost ([127.0.0.1]) by softronics.hoeneisen.ch with esmtp (Exim 4.69) (envelope-from ) id 1OxET8-00031q-5o; Sun, 19 Sep 2010 09:37:50 +0200 Date: Sun, 19 Sep 2010 09:37:50 +0200 (CEST) From: Bernie Hoeneisen X-X-Sender: bhoeneis@softronics.hoeneisen.ch To: IETF ENUM list Message-ID: User-Agent: Alpine 2.00 (DEB 1167 2008-08-23) MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="37663318-1232430644-1284881273=:11500" Content-ID: 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 Cc: "E.164 To MetaData BOF discussion list" Subject: [Enum] NomCom 2010-2011: Call for More Nominations (fwd) X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Enum Discussion List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 19 Sep 2010 07:37:36 -0000 This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --37663318-1232430644-1284881273=:11500 Content-Type: TEXT/PLAIN; CHARSET=UTF-8; format=flowed Content-Transfer-Encoding: QUOTED-PRINTABLE Content-ID: Hi, The WG chairs have been asked by the IETF NomCom to forward the below=20 email to their WG mailing lists. [NomCom selects the managment positions in the IETF, i.e. IETF chair,=20 IESG, IAB and IAOC.] NomCom is in urgent need of further nominations. In particular for IESG=20 (INT, RAI, and RTG, and OPS) and IAOC, the number of nominees has been=20 reported to be too low. Please nominate anybody you believe would be a viable candidate for IESG=20 or IAOC (details below)! You can also nominate yourself. https://wiki.tools.ietf.org/group/nomcom/10/nominate As a previous voting member of the IETF NomCom I can just confirm how=20 important it is to have several nominees per position to be filled. The=20 task of the NomCom to select the ideal mix of skills and personalities=20 gets really difficult if there are not enough willing nominees. After all, who will be in the IESG / IAOC next year concerns everyone of=20 us! Have a nice weekend! cheers, Bernie, ENUM WG chair -- http://ucom.ch/ Tech Consulting for Internet Standardization ---------- Forwarded message ---------- From: NomCom Chair Date: Thu, Sep 16, 2010 at 6:26 PM Subject: NomCom 2010-2011: Call for More Nominations To: IETF Announcement list Hi Folks, Nominations have slowed down dramatically, so this update is to enlist the community in an effort to pick up the pace. We are very far behind in nominations for all the open positions but in particular we need nominations for the IESG and IAOC open positions. There have been no nominations received (other than for the incumbents) in INT, RAI, and RTG, and only 1 for OPS. =C2=A0Likewise, in IAOC there hav= e been no nominations submitted other than the incumbent. The acceptance rates of those nominated has also been very slow. In order to initiate the open list of willing nominees we are in need of a reasonable number of acceptances, and due to the low number of nominees and acceptances have delayed the start date for publishing the first open list to September 20. =C2=A0So if you have been nominated and are willing to serve, but have not yet confirmed this by email back to the NomCom, please do so as soon as possible. We need Community input and participation! We cannot properly execute the task of selecting the best candidates for these positions with so few nominations and acceptances. So, please consider making nominations for the open positions, in particular those for which we have so few nominations =E2=80=93 it takes just a few minutes of your time. Right now, we just need the names/email addresses. Why do we need more nominations? =C2=A0Well, even if you think a willing incumbent is doing a very good job and should be returned, his or her ability to serve again might be impacted by unforeseen circumstances between now and March. NomCom needs to consider multiple nominees to be prepared in the event one or more candidates is unable to serve come next March and to ensure we have chosen the best candidate. There are several ways you can help the IETF Nominating Committee. - You may nominate yourself. - You can nominate someone you know whom you think would do a good job. Do not worry about whether they might already be nominated. We would much prefer to receive the same nomination several times rather than miss a good person we should consider. How to submit Nominations: -------------------------- The list of positions we need to fill, and the provided Job Descriptions, and forms for nominations, can be found in the call for nominations at: https://datatracker.ietf.org/ann/nomcom/2468/ You may enter a nomination by going to the following URL https://wiki.tools.ietf.org/group/nomcom/10/nominate You may also nominate someone by sending an email to nomcom10@ietf.org and giving us their name, email address and the open position you are nominating them for. We will take care of the rest. If you are asked for a user name and password, use an existing ietf login and password. If you need a login and password, request one from the tools page at the following URL http://trac.tools.ietf.org/newlogin Open List: ---------- As you already know, NomCom 2010-2011 will follow the policy for "Open Disclosure of Willing Nominees" described in RFC 5680. Feedback Collection: -------------------- Once the open list is available, the entire community will be invited to provide feedback. I will send a further announcement requesting feedback on the nominees, describing how to submit feedback, and how to view the open list of nominees. Thank you, Thomas Walsh Chair, NomCom 2010-2011 nomcom-chair@ietf.org twalsh@juniper.net _______________________________________________ IETF-Announce mailing list IETF-Announce@ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce _______________________________________________ BOFCHAIRS mailing list BOFCHAIRS@ietf.org https://www.ietf.org/mailman/listinfo/bofchairs --37663318-1232430644-1284881273=:11500-- From gonzalo.camarillo@ericsson.com Thu Sep 23 00:43:04 2010 Return-Path: X-Original-To: enum@core3.amsl.com Delivered-To: enum@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5A07F3A69C2 for ; Thu, 23 Sep 2010 00:43:04 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -106.28 X-Spam-Level: X-Spam-Status: No, score=-106.28 tagged_above=-999 required=5 tests=[AWL=0.319, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0HYHp-4iVn5Z for ; Thu, 23 Sep 2010 00:43:03 -0700 (PDT) Received: from mailgw9.se.ericsson.net (mailgw9.se.ericsson.net [193.180.251.57]) by core3.amsl.com (Postfix) with ESMTP id 9BC3E3A6928 for ; Thu, 23 Sep 2010 00:43:02 -0700 (PDT) X-AuditID: c1b4fb39-b7b0bae000000f9a-07-4c9b0522a095 Received: from esealmw129.eemea.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw9.se.ericsson.net (Symantec Mail Security) with SMTP id 62.9B.03994.2250B9C4; Thu, 23 Sep 2010 09:43:30 +0200 (CEST) Received: from esealmw127.eemea.ericsson.se ([153.88.254.171]) by esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.3959); Thu, 23 Sep 2010 09:43:29 +0200 Received: from [131.160.126.159] ([131.160.126.159]) by esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.3959); Thu, 23 Sep 2010 09:43:29 +0200 Message-ID: <4C9B051E.8080409@ericsson.com> Date: Thu, 23 Sep 2010 10:43:26 +0300 From: Gonzalo Camarillo User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.2.8) Gecko/20100802 Thunderbird/3.1.2 MIME-Version: 1.0 To: IETF ENUM WG , 'David Harrington' References: <20100913153003.16FD63A69F5@core3.amsl.com> <20100913171817.GG29256@x27.adm.denic.de> <4C8F683B.1040403@ericsson.com> <025801cb540b$bcfa12f0$36ee38d0$@us> <20100914220927.GB22824@x27.adm.denic.de> In-Reply-To: <20100914220927.GB22824@x27.adm.denic.de> X-Enigmail-Version: 1.1.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 23 Sep 2010 07:43:29.0820 (UTC) FILETIME=[03D785C0:01CB5AF3] X-Brightmail-Tracker: AAAAAA== Subject: Re: [Enum] I-D Action:draft-ietf-enum-enumservices-guide-21.txt X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Enum Discussion List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Sep 2010 07:43:04 -0000 Hi Peter, as promised, I have discussed this issue (PS vs. BCP) within the IESG. Some ADs thought PS was more appropriate while other ADs (including myself) thought BCP would be better. However, we had consensus that this is a very minor issue; everybody seemed to be able to live with either PS or BCP. The thing is that the IETF LC (before I was in the IESG) was for PS: http://www.ietf.org/mail-archive/web/ietf-announce/current/msg06107.html Therefore, if we decided to make it a BCP now, we would need to run a second IETF LC. Therefore, my suggestion is to stick to PS (unless the WG strongly opposes this way forward). Thanks, Gonzalo On 15/09/2010 1:09 AM, Peter Koch wrote: > On Tue, Sep 14, 2010 at 08:52:48AM -0400, Richard Shockey wrote: >> Gonzalo is correct. Fat thumb error. No conspiracy intended. Logically >> given the subject matter it's a PS. > > assuming that _this_ was now exactly that type of error :-), I'd like to > point to > and surrounding messages. In that discussion we concluded BCP was the > appropriate status. Please understand, PS would not provide "more value" > than BCP, but both categories just have different functions. > > Best regards, > Peter > From gonzalo.camarillo@ericsson.com Mon Sep 27 11:43:59 2010 Return-Path: X-Original-To: enum@core3.amsl.com Delivered-To: enum@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5C2683A6D88 for ; Mon, 27 Sep 2010 11:43:59 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -106.337 X-Spam-Level: X-Spam-Status: No, score=-106.337 tagged_above=-999 required=5 tests=[AWL=0.262, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FC10F47jV9zF for ; Mon, 27 Sep 2010 11:43:39 -0700 (PDT) Received: from mailgw9.se.ericsson.net (mailgw9.se.ericsson.net [193.180.251.57]) by core3.amsl.com (Postfix) with ESMTP id 4ADD63A6D57 for ; Mon, 27 Sep 2010 11:43:12 -0700 (PDT) X-AuditID: c1b4fb39-b7c6dae000006ad7-75-4ca0e5e44b0b Received: from esealmw129.eemea.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw9.se.ericsson.net (Symantec Mail Security) with SMTP id AD.60.27351.4E5E0AC4; Mon, 27 Sep 2010 20:43:48 +0200 (CEST) Received: from esealmw129.eemea.ericsson.se ([153.88.254.177]) by esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.3959); Mon, 27 Sep 2010 20:43:48 +0200 Received: from [131.160.126.137] ([131.160.126.137]) by esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.3959); Mon, 27 Sep 2010 20:43:47 +0200 Message-ID: <4CA0E5E4.1080800@ericsson.com> Date: Mon, 27 Sep 2010 21:43:48 +0300 From: Gonzalo Camarillo User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.2.8) Gecko/20100802 Thunderbird/3.1.2 MIME-Version: 1.0 To: "enum@ietf.org" References: <4C8A2AE1.105@ericsson.com> In-Reply-To: <4C8A2AE1.105@ericsson.com> X-Enigmail-Version: 1.1.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 27 Sep 2010 18:43:48.0019 (UTC) FILETIME=[EBC7F030:01CB5E73] X-Brightmail-Tracker: AAAAAA== Subject: Re: [Enum] Way forward after the ENUM trilogy X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Enum Discussion List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Sep 2010 18:43:59 -0000 Hi, FYI: per the discussion below, I have just moved the edns0, cnam, and unused drafts to the "dead" state. Cheers, Gonzalo On 10/09/2010 3:56 PM, Gonzalo Camarillo wrote: > Hi, > > as you know, we are currently focusing on getting the ENUM trilogy > approved. In addition to the ENUM trilogy, there are a number of ENUM > drafts. This is how we intend to handle them: > > draft-ietf-enum-edns0-00 > This draft will be abandoned because a DNSEXT document already > provides the same functionality. > > draft-ietf-enum-iax-05 > This draft will be updated to comply with enumservices-guide as soon > as enumservices-guide is approved. > > draft-ietf-enum-cnam-08 > draft-ietf-enum-unused-04 > The ENUM WG will not work on these drafts any longer because the > issues these drafts deal with are being discussed in a wider context > within the E2MD initiative. > > > We would like to update the milestones in the charter according to this > plan. Your input on this plan is very welcome. > > Thanks, > > Gonzalo > > _______________________________________________ > enum mailing list > enum@ietf.org > https://www.ietf.org/mailman/listinfo/enum > From gonzalo.camarillo@ericsson.com Tue Sep 28 23:52:22 2010 Return-Path: X-Original-To: enum@core3.amsl.com Delivered-To: enum@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BC6983A6C25 for ; Tue, 28 Sep 2010 23:52:22 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -106.345 X-Spam-Level: X-Spam-Status: No, score=-106.345 tagged_above=-999 required=5 tests=[AWL=0.254, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SoAm-em1mP-a for ; Tue, 28 Sep 2010 23:52:22 -0700 (PDT) Received: from mailgw10.se.ericsson.net (mailgw10.se.ericsson.net [193.180.251.61]) by core3.amsl.com (Postfix) with ESMTP id B03FF3A6B52 for ; Tue, 28 Sep 2010 23:52:21 -0700 (PDT) X-AuditID: c1b4fb3d-b7cbfae00000264e-6a-4ca2e25028be Received: from esealmw129.eemea.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw10.se.ericsson.net (Symantec Mail Security) with SMTP id 23.1A.09806.052E2AC4; Wed, 29 Sep 2010 08:53:04 +0200 (CEST) Received: from esealmw129.eemea.ericsson.se ([153.88.254.177]) by esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.3959); Wed, 29 Sep 2010 08:53:00 +0200 Received: from [131.160.126.180] ([131.160.126.180]) by esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.3959); Wed, 29 Sep 2010 08:53:00 +0200 Message-ID: <4CA2E24C.30502@ericsson.com> Date: Wed, 29 Sep 2010 09:53:00 +0300 From: Gonzalo Camarillo User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.2.8) Gecko/20100802 Thunderbird/3.1.2 MIME-Version: 1.0 To: enum@ietf.org X-Enigmail-Version: 1.1.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 29 Sep 2010 06:53:00.0384 (UTC) FILETIME=[F4A2C600:01CB5FA2] X-Brightmail-Tracker: AAAAAA== Subject: [Enum] 3761bis and transition drafts have been approved X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Enum Discussion List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Sep 2010 06:52:22 -0000 Hi, I was hoping to approve the ENUM trilogy as a bundle but the guide document is taking a bit longer than expected (the authors and chairs are currently working on a new revision intended to address the last discuss on the document). Therefore, I have just requested the approval of the other two drafts. As a result, they will be sent to the RFC Editor shortly. Cheers, Gonzalo From wwwrun@core3.amsl.com Wed Sep 29 08:52:18 2010 Return-Path: X-Original-To: enum@ietf.org Delivered-To: enum@core3.amsl.com Received: by core3.amsl.com (Postfix, from userid 30) id D50723A6D34; Wed, 29 Sep 2010 08:52:18 -0700 (PDT) X-idtracker: yes From: The IESG To: IETF-Announce Message-Id: <20100929155218.D50723A6D34@core3.amsl.com> Date: Wed, 29 Sep 2010 08:52:18 -0700 (PDT) Cc: enum mailing list , enum chair , Internet Architecture Board , RFC Editor Subject: [Enum] Protocol Action: 'The E.164 to Uniform Resource Identifiers (URI) Dynamic Delegation Discovery System (DDDS) Application (ENUM)' to Proposed Standard X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Enum Discussion List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Sep 2010 15:52:19 -0000 The IESG has approved the following document: - 'The E.164 to Uniform Resource Identifiers (URI) Dynamic Delegation Discovery System (DDDS) Application (ENUM)' as a Proposed Standard This document is the product of the Telephone Number Mapping Working Group. The IESG contact persons are Gonzalo Camarillo and Robert Sparks. A URL of this Internet Draft is: https://datatracker.ietf.org/doc/draft-ietf-enum-3761bis/ 1 - Technical Summary This document discusses the use of the Domain Name System (DNS) for the storage of E.164 [E164] numbers, and for resolving them into URIs that can be used for (for example) telephony call setup. This document also describes how the DNS can be used to identify the services associated with an E.164 number. This document includes a Dynamic Delegation Discovery System (DDDS) Application specification, as detailed in the document series described in [RFC3401]. This document obsoletes [RFC3761]. 2 - Working Group Summary Was there anything in the discussion in the interested community that is worth noting? For example, was there controversy about particular points or were there decisions where the consensus was particularly rough? Was the document considered in any WG, and if so, why was it not adopted as a work item there? In general except where noted this document represents a excellent effort to update RFC 3761 on the basis of real operational experiences and represents the effort of the ENUM WG to close its charter and declare victory. 3 - Document Quality. Are there existing implementations of the protocol? Have a significant number of vendors indicated their plan to implement the specification? Are there any reviewers that merit special mention as having done a thorough review, e.g., one that resulted in important changes or a conclusion that the document had no substantive issues? If there was a MIB Doctor, Media Type or other expert review, what was its course (briefly)? In the case of a Media Type review, on what date was the request posted? As noted document reflects and updates RFC 3761 to reflect major operational issues discovered during deployment. RFC 3761 is in wide global deployment within e164.arpa as well in private instantiations within in global carrier networks. 4 – Personnel Document Shepherd: Richard Shockey Responsible AD: Gonzalo Camarillo From wwwrun@core3.amsl.com Wed Sep 29 08:53:40 2010 Return-Path: X-Original-To: enum@ietf.org Delivered-To: enum@core3.amsl.com Received: by core3.amsl.com (Postfix, from userid 30) id 073A73A6C36; Wed, 29 Sep 2010 08:53:39 -0700 (PDT) X-idtracker: yes From: The IESG To: IETF-Announce Message-Id: <20100929155340.073A73A6C36@core3.amsl.com> Date: Wed, 29 Sep 2010 08:53:40 -0700 (PDT) Cc: enum mailing list , enum chair , Internet Architecture Board , RFC Editor Subject: [Enum] Protocol Action: 'Update of legacy IANA Registrations of Enumservices' to Proposed Standard X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Enum Discussion List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Sep 2010 15:53:40 -0000 The IESG has approved the following document: - 'Update of legacy IANA Registrations of Enumservices ' as a Proposed Standard This document is the product of the Telephone Number Mapping Working Group. The IESG contact persons are Gonzalo Camarillo and Robert Sparks. A URL of this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-enum-enumservices-transition-06.txt 1 - Technical Summary New work by the ENUM WG has obsoleted the IANA registration section of [RFC3761]. Since the IANA Enumservice registry contains various Enumservices registered under the regime of RFC 3761, those registrations do not conform to the new guidelines as specified in [I-D.ietf-enum-enumservices-guide-16]. To ensure consistency among all Enumservice registrations at IANA, this document adds the missing elements to those existing registrations. Furthermore, all existing Enumservice registrations are converted to the new XML chunk format, and, where deemed necessary, minor editorial corrections are applied. 2 - Working Group Summary Non contentious document. 3 - Document Quality. Document further enhances the applicability of RFC 3761 and new templates for Enumservice registrations, simplifies the process by which protocol designers can create new services and properly the RFC 3761 IANA registry elements. 4 – Personnel Document Shepherd: Richard Shockey Responsible AD: Gonzalo Camarillo