
From bernie@ietf.hoeneisen.ch  Thu Jun  3 13:02:02 2010
Return-Path: <bernie@ietf.hoeneisen.ch>
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 B2C7C3A6A13; Thu,  3 Jun 2010 13:02:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.126
X-Spam-Level: 
X-Spam-Status: No, score=-2.126 tagged_above=-999 required=5 tests=[AWL=1.873,  BAYES_50=0.001, GB_I_INVITATION=-2, GB_I_LETTER=-2]
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 9GifzDgXdNsP; Thu,  3 Jun 2010 13:02:01 -0700 (PDT)
Received: from softronics.hoeneisen.ch (softronics.hoeneisen.ch [62.2.86.178]) by core3.amsl.com (Postfix) with ESMTP id E0D5F3A67E9; Thu,  3 Jun 2010 13:02:00 -0700 (PDT)
Received: from localhost ([127.0.0.1]) by softronics.hoeneisen.ch with esmtp (Exim 4.69) (envelope-from <bernie@ietf.hoeneisen.ch>) id 1OKGbp-0003dW-Hh; Thu, 03 Jun 2010 22:01:45 +0200
Date: Thu, 3 Jun 2010 22:01:45 +0200 (CEST)
From: Bernie Hoeneisen <bernie@ietf.hoeneisen.ch>
X-X-Sender: bhoeneis@softronics.hoeneisen.ch
To: IETF ENUM list <enum@ietf.org>,  "E.164 To MetaData BOF discussion list" <e2md@ietf.org>
Message-ID: <alpine.DEB.2.00.1006032159410.10684@softronics.hoeneisen.ch>
User-Agent: Alpine 2.00 (DEB 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
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] IETF 78 - Meeting and Sponsorship Information (fwd)
X-BeenThere: enum@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Enum Discussion List <enum.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/enum>, <mailto:enum-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Thu, 03 Jun 2010 20:02:02 -0000

FYI

---------- Forwarded message ----------
78th IETF Meeting
Maastricht, Netherlands
July 25-30, 2010

1. Sponsorship Opportunities
2. Registration Types
3. Visas and Letters of Invitation
4. Accommodations & Breakfast Information
5. IETF 79 (Beijing) Visa Information

1) Sponsorship Opportunities
There are still sponsorship opportunities and benefits for high profile
company/organizational exposure at the upcoming IETF meeting in
Maastricht, Netherlands from July 25-30, 2010.  All sponsorship fees go
directly to fund the operations of the IETF.  See the options at:
http://www.ietf.org/meeting/78/index.html ?Sponsorship Opportunities?
under ?General?.  Each of the sponsorship options provide extended and
repeat exposure at this weeklong meeting.

Please contact Drew Dvorshak, dvorshak@isoc.org, with any questions
and/or to reserve your organization?s spot.  Thanks in advance for
supporting the critical work of the IETF!

2) Register online at:  http://www.ietf.org/meetings/78/

3) Letters of Invitation and Visas
Letters of Invitation
After you complete the meeting registration process, you will be given the
option to request a letter of invitation. You can request the Letter of
Invitation as soon as you finish registration, or at a later time by
following the link provided in the confirmation email.

Visas
Please check the Netherlands Ministry of Foreign Affairs site
(http://www.minbuza.nl/en/Services/Consular_Services/Visa) for list of
countries with visa exemptions.

We recommend you give yourself at least one month to complete the visa
process.

4) Accommodations & Breakfast Information
http://www.ietf.org/meeting/78/hotel.html

5) If you want to start planning for your trip to IETF 79 in Beijing, we
have visa information online here:
http://www.ietf.org/meeting/79/visa.html

Only 52 days until IETF 78!


From gonzalo.camarillo@ericsson.com  Fri Jun  4 01:32:27 2010
Return-Path: <gonzalo.camarillo@ericsson.com>
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 88C2728C136 for <enum@core3.amsl.com>; Fri,  4 Jun 2010 01:32:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.387
X-Spam-Level: 
X-Spam-Status: No, score=-102.387 tagged_above=-999 required=5 tests=[AWL=1.612, BAYES_50=0.001, 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 XFHIdn9LRhJf for <enum@core3.amsl.com>; Fri,  4 Jun 2010 01:31:53 -0700 (PDT)
Received: from mailgw10.se.ericsson.net (mailgw10.se.ericsson.net [193.180.251.61]) by core3.amsl.com (Postfix) with ESMTP id 957B33A6814 for <enum@ietf.org>; Fri,  4 Jun 2010 01:31:03 -0700 (PDT)
X-AuditID: c1b4fb3d-b7b13ae0000071b2-c8-4c08b9ac7345
Received: from esealmw126.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw10.se.ericsson.net (Symantec Mail Security) with SMTP id 77.44.29106.CA9B80C4; Fri,  4 Jun 2010 10:30:36 +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, 4 Jun 2010 10:30:07 +0200
Received: from [131.160.37.44] ([131.160.37.44]) by esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.3959);  Fri, 4 Jun 2010 10:30:07 +0200
Message-ID: <4C08B98F.5010507@ericsson.com>
Date: Fri, 04 Jun 2010 11:30:07 +0300
From: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1.9) Gecko/20100317 Thunderbird/3.0.4
MIME-Version: 1.0
To: Lawrence Conroy <lconroy@insensate.co.uk>
References: <328AFAAB-D292-42A7-865F-604F4002D468@insensate.co.uk> <4C039D12.8080208@ericsson.com>
In-Reply-To: <4C039D12.8080208@ericsson.com>
X-Enigmail-Version: 1.0.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 04 Jun 2010 08:30:07.0813 (UTC) FILETIME=[23B91F50:01CB03C0]
X-Brightmail-Tracker: AAAAAA==
Cc: IETF ENUM list <enum@ietf.org>
Subject: Re: [Enum] About RFC 3761bis-07
X-BeenThere: enum@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Enum Discussion List <enum.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/enum>, <mailto:enum-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 04 Jun 2010 08:32:27 -0000

Hi Lawrence,

I have just had a look at this new revision. Thanks for addressing the
comments you received. I ran the ID nits tool on the draft and got the
following warnings:

  == Unused Reference: 'RFC3824' is defined on line 904, but no explicit
     reference was found in the text

  -- Obsolete informational reference (is this intentional?): RFC 2915
     (Obsoleted by RFC 3401, RFC 3402, RFC 3403, RFC 3404)

  -- Obsolete informational reference (is this intentional?): RFC 2916
     (Obsoleted by RFC 3761)

Additionally, Section 1.2, which is a subsection of the Introduction,
contains normative statements. I do not think introductions should
contain normative statements. We could convert Section 1.2 into a new
Section 2.

As next steps, the earliest we can get the whole IESG to review these
documents is in two weeks (the next IESG telechat). If you can revise
the draft real quick to address the nits above, that would be great.
Otherwise, I can add these comments to the ID tracker so that you
address them together with any additional comments from the IESG after
its IESG evaluation... it's your call. Let me know how you want to
process and I will take care of all the practicals.

Thanks,

Gonzalo


On 31/05/2010 2:27 PM, Gonzalo Camarillo wrote:
> Hi Lawrence,
> 
> thanks for putting this new revision together. I will give the WG a few
> days to have a look at it in case somebody has comments (I will of
> course also review this new version). After that, I will advance the
> three documents in parallel.
> 
> Thanks,
> 
> Gonzalo
> 
> 
> On 28/05/2010 2:13 PM, Lawrence Conroy wrote:
>> Hi Folks,
>>  To explain why we've issued a new version of 3761bis ...
>> Gonzalo provided a detailed review of the current (-6) draft.
>>
>> I do not believe that we have made any changes to the formal text.
>> These changes are intended to clear up some of the text
>> to make it easier to understand (and make it shorter).
>>
>> In response, we produced this new version. 
>> - (very slightly) tweaked the text of 1 (intro) to reflect what ENUM
>>   does (or doesn't do). i.e. changed the statements that "ENUM stores
>>   E.164 numbers in DNS" to "providing storage in DNS associated with
>>   E.164 numbers".
>>  - changed the Abstract to reflect that.
>>  - tweaked the text of 1.2 to try to meet Gonzalo's review comment on it
>>    and to make it a bit clearer what is required for non-E.164 numbers
>>  - moved the arcane text that was paragraph 2 of section 2's introduction
>>    into its own sub-section at the *end* of section 2 ("Collision Avoidance").
>>  - removed some text copied from RFC 5483 and replaced with an informative
>>    reference to that RFC.
>>
>>  We've also:
>>  - swapped around a couple of the items so the ORDER/PREF ones are all
>>    together,
>>  - have tried to answer Gonzalo's question "why is ORDER/PREF a problem?"
>>    by splitting out the proposed default value as a separate item and
>>    putting the (expanded) rest into an indented explanation following that,
>>  - tagged on two items to nail down that you MUST sort using ORDER and
>>    PREF, and you SHOULD NOT discard NAPTRs before they have been considered
>>    (unless you have already selected one).
>>  - corrected an bad typo in one of the items on ORDER/PREF (c/highest/lowest/)
>>
>>
>> If there are any outstanding comments, please mail to the list (or the authors).
>>
>> all the best,
>>   Lawrence
>>
>> _______________________________________________
>> 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
> 


From root@core3.amsl.com  Fri Jun  4 07:45:04 2010
Return-Path: <root@core3.amsl.com>
X-Original-To: enum@ietf.org
Delivered-To: enum@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0) id 985EB3A69C9; Fri,  4 Jun 2010 07:45:02 -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: <20100604144504.985EB3A69C9@core3.amsl.com>
Date: Fri,  4 Jun 2010 07:45:02 -0700 (PDT)
Cc: enum@ietf.org
Subject: [Enum] I-D Action:draft-ietf-enum-3761bis-08.txt
X-BeenThere: enum@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Enum Discussion List <enum.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/enum>, <mailto:enum-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 04 Jun 2010 14:45:04 -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           : The E.164 to Uniform Resource Identifiers (URI) Dynamic Delegation Discovery System (DDDS) Application (ENUM)
	Author(s)       : S. Bradner, et al.
	Filename        : draft-ietf-enum-3761bis-08.txt
	Pages           : 22
	Date            : 2010-06-04

This document discusses the use of the Domain Name System (DNS) for
storage of data associated with E.164 numbers, and for resolving
those numbers into URIs that can be used (for example) in 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
obsoletes RFC3761.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-enum-3761bis-08.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-3761bis-08.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2010-06-04073419.I-D@ietf.org>


--NextPart--

From lconroy@insensate.co.uk  Fri Jun  4 07:59:42 2010
Return-Path: <lconroy@insensate.co.uk>
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 7CA773A685A for <enum@core3.amsl.com>; Fri,  4 Jun 2010 07:59:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.369
X-Spam-Level: 
X-Spam-Status: No, score=-0.369 tagged_above=-999 required=5 tests=[AWL=0.370,  BAYES_20=-0.74]
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 V3Tyc-7ee4Kv for <enum@core3.amsl.com>; Fri,  4 Jun 2010 07:59:41 -0700 (PDT)
Received: from insensate.co.uk (ghost.insensate.co.uk [213.152.49.121]) by core3.amsl.com (Postfix) with ESMTP id 580693A67CC for <enum@ietf.org>; Fri,  4 Jun 2010 07:59:41 -0700 (PDT)
Received: from [127.0.0.1] (localhost [127.0.0.1]) by insensate.co.uk (Postfix) with ESMTP id A20151A719B for <enum@ietf.org>; Fri,  4 Jun 2010 15:59:26 +0100 (BST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1078)
From: Lawrence Conroy <lconroy@insensate.co.uk>
In-Reply-To: <20100604144504.985EB3A69C9@core3.amsl.com>
Date: Fri, 4 Jun 2010 15:59:26 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <92B075F0-37BA-45EE-9BE2-39843996826F@insensate.co.uk>
References: <20100604144504.985EB3A69C9@core3.amsl.com>
To: IETF ENUM list <enum@ietf.org>
X-Mailer: Apple Mail (2.1078)
Subject: Re: [Enum] I-D Action:draft-ietf-enum-3761bis-08.txt
X-BeenThere: enum@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Enum Discussion List <enum.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/enum>, <mailto:enum-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 04 Jun 2010 14:59:42 -0000

Hi Folks,
 This version's change list is:
-  Renumbered sections to pull out the old section 1.2 as its own
  section 2.
-  Added at end of section 4.1/5.1 -- "The informational RFC3824
  recommended such support."
-  Changed phrasing of sentence in introduction paragraph 3 to be
  consistent with abstract and paragraph 1 -- added "an" & "for data".
-  Corrected spelling in Acknowledgements

all the best,
  Lawrence

On 4 Jun 2010, at 15:45, 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.
>=20
>=20
> 	Title           : The E.164 to Uniform Resource Identifiers =
(URI) Dynamic Delegation Discovery System (DDDS) Application (ENUM)
> 	Author(s)       : S. Bradner, et al.
> 	Filename        : draft-ietf-enum-3761bis-08.txt
> 	Pages           : 22
> 	Date            : 2010-06-04
>=20
> This document discusses the use of the Domain Name System (DNS) for
> storage of data associated with E.164 numbers, and for resolving
> those numbers into URIs that can be used (for example) in 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
> obsoletes RFC3761.
>=20
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-enum-3761bis-08.txt
>=20
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>=20
> Below is the data which will enable a MIME compliant mail reader
> implementation to automatically retrieve the ASCII version of the
> Internet-Draft.
> <Mail Attachment>_______________________________________________
> enum mailing list
> enum@ietf.org
> https://www.ietf.org/mailman/listinfo/enum


From gonzalo.camarillo@ericsson.com  Mon Jun  7 09:53:06 2010
Return-Path: <gonzalo.camarillo@ericsson.com>
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 3830428C3F9 for <enum@core3.amsl.com>; Mon,  7 Jun 2010 09:53:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.424
X-Spam-Level: 
X-Spam-Status: No, score=-101.424 tagged_above=-999 required=5 tests=[AWL=-1.425, BAYES_50=0.001, 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 Kk0u6VQihLJi for <enum@core3.amsl.com>; Mon,  7 Jun 2010 09:53:05 -0700 (PDT)
Received: from mailgw9.se.ericsson.net (mailgw9.se.ericsson.net [193.180.251.57]) by core3.amsl.com (Postfix) with ESMTP id 75CC43A70D4 for <enum@ietf.org>; Mon,  7 Jun 2010 01:36:21 -0700 (PDT)
X-AuditID: c1b4fb39-b7b80ae000001aa1-5a-4c0caf84ca49
Received: from esealmw126.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw9.se.ericsson.net (Symantec Mail Security) with SMTP id 68.45.06817.48FAC0C4; Mon,  7 Jun 2010 10:36:20 +0200 (CEST)
Received: from esealmw126.eemea.ericsson.se ([153.88.254.174]) by esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.3959);  Mon, 7 Jun 2010 10:36:20 +0200
Received: from [131.160.37.44] ([131.160.37.44]) by esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.3959);  Mon, 7 Jun 2010 10:36:20 +0200
Message-ID: <4C0CAF84.5000401@ericsson.com>
Date: Mon, 07 Jun 2010 11:36:20 +0300
From: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1.9) Gecko/20100317 Thunderbird/3.0.4
MIME-Version: 1.0
To: enum@ietf.org
X-Enigmail-Version: 1.0.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 07 Jun 2010 08:36:20.0320 (UTC) FILETIME=[80FE6E00:01CB061C]
X-Brightmail-Tracker: AAAAAA==
Subject: [Enum] Fwd: Re:  I-D Action:draft-ietf-enum-3761bis-08.txt
X-BeenThere: enum@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Enum Discussion List <enum.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/enum>, <mailto:enum-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Mon, 07 Jun 2010 16:53:06 -0000

Resending because the mailing list did not seem to be working this weekend.

-------- Original Message --------
Subject: Re: [Enum] I-D Action:draft-ietf-enum-3761bis-08.txt
Date: Sun, 06 Jun 2010 11:04:48 +0300
From: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
To: Lawrence Conroy <lconroy@insensate.co.uk>
CC: IETF ENUM list <enum@ietf.org>

Hi Lawrence,

thanks for your quick response. I will now go ahead add the ENUM trilogy
to the agenda of the next IESG telechat in a couple of weeks. This means
that the authors of the three drafts may get comments on the drafts from
IESG members. Being responsive when such comments arrive will be the
best way to help us progress the drafts.

Thanks,

Gonzalo

On 04/06/2010 5:59 PM, Lawrence Conroy wrote:
> Hi Folks,
>  This version's change list is:
> -  Renumbered sections to pull out the old section 1.2 as its own
>   section 2.
> -  Added at end of section 4.1/5.1 -- "The informational RFC3824
>   recommended such support."
> -  Changed phrasing of sentence in introduction paragraph 3 to be
>   consistent with abstract and paragraph 1 -- added "an" & "for data".
> -  Corrected spelling in Acknowledgements
> 
> all the best,
>   Lawrence
> 
> On 4 Jun 2010, at 15:45, 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           : The E.164 to Uniform Resource Identifiers (URI) Dynamic Delegation Discovery System (DDDS) Application (ENUM)
>> 	Author(s)       : S. Bradner, et al.
>> 	Filename        : draft-ietf-enum-3761bis-08.txt
>> 	Pages           : 22
>> 	Date            : 2010-06-04
>>
>> This document discusses the use of the Domain Name System (DNS) for
>> storage of data associated with E.164 numbers, and for resolving
>> those numbers into URIs that can be used (for example) in 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
>> obsoletes RFC3761.
>>
>> A URL for this Internet-Draft is:
>> http://www.ietf.org/internet-drafts/draft-ietf-enum-3761bis-08.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.
>> <Mail Attachment>_______________________________________________
>> 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
> 


From root@core3.amsl.com  Wed Jun 23 14:30:20 2010
Return-Path: <root@core3.amsl.com>
X-Original-To: enum@ietf.org
Delivered-To: enum@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0) id 4CFF13A69D2; Wed, 23 Jun 2010 14:30:04 -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: <20100623213017.4CFF13A69D2@core3.amsl.com>
Date: Wed, 23 Jun 2010 14:30:04 -0700 (PDT)
Cc: enum@ietf.org
Subject: [Enum] I-D Action:draft-ietf-enum-3761bis-09.txt
X-BeenThere: enum@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Enum Discussion List <enum.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/enum>, <mailto:enum-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Wed, 23 Jun 2010 21:30:21 -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           : The E.164 to Uniform Resource Identifiers (URI) Dynamic Delegation Discovery System (DDDS) Application (ENUM)
	Author(s)       : S. Bradner, et al.
	Filename        : draft-ietf-enum-3761bis-09.txt
	Pages           : 23
	Date            : 2010-06-23

This document discusses the use of the Domain Name System (DNS) for
storage of data associated with E.164 numbers, and for resolving
those numbers into URIs that can be used (for example) in 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
obsoletes RFC3761.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-enum-3761bis-09.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-3761bis-09.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2010-06-23142822.I-D@ietf.org>


--NextPart--

From fluffy@cisco.com  Sat Jun 26 11:00:28 2010
Return-Path: <fluffy@cisco.com>
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 7878B3A695A for <enum@core3.amsl.com>; Sat, 26 Jun 2010 11:00:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.13
X-Spam-Level: 
X-Spam-Status: No, score=-110.13 tagged_above=-999 required=5 tests=[AWL=0.469, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, 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 orScsFICnJCg for <enum@core3.amsl.com>; Sat, 26 Jun 2010 11:00:27 -0700 (PDT)
Received: from sj-iport-1.cisco.com (sj-iport-1.cisco.com [171.71.176.70]) by core3.amsl.com (Postfix) with ESMTP id 9481A3A696A for <enum@ietf.org>; Sat, 26 Jun 2010 11:00:27 -0700 (PDT)
Authentication-Results: sj-iport-1.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AiAKAP/cJUyrR7H+/2dsb2JhbAAekl6ML3GmGpl4hSQEg2Y
X-IronPort-AV: E=Sophos;i="4.53,487,1272844800"; d="scan'208";a="338863430"
Received: from sj-core-2.cisco.com ([171.71.177.254]) by sj-iport-1.cisco.com with ESMTP; 26 Jun 2010 18:00:37 +0000
Received: from sjc-vpn7-99.cisco.com (sjc-vpn7-99.cisco.com [10.21.144.99]) by sj-core-2.cisco.com (8.13.8/8.14.3) with ESMTP id o5QI0bFm003191 for <enum@ietf.org>; Sat, 26 Jun 2010 18:00:37 GMT
From: Cullen Jennings <fluffy@cisco.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Date: Sat, 26 Jun 2010 11:00:36 -0700
Message-Id: <9A47EA3A-6FC9-40C1-B8DA-F658691E9E89@cisco.com>
To: enum@ietf.org
Mime-Version: 1.0 (Apple Message framework v1081)
X-Mailer: Apple Mail (2.1081)
Subject: [Enum] Topics for meeting?
X-BeenThere: enum@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Enum Discussion List <enum.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/enum>, <mailto:enum-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Sat, 26 Jun 2010 18:00:28 -0000

I was just sort of curios what the topics were for the upcoming meeting. 



From bernie@ietf.hoeneisen.ch  Sun Jun 27 13:54:03 2010
Return-Path: <bernie@ietf.hoeneisen.ch>
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 E62143A69F1 for <enum@core3.amsl.com>; Sun, 27 Jun 2010 13:54:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.394
X-Spam-Level: 
X-Spam-Status: No, score=-1.394 tagged_above=-999 required=5 tests=[AWL=-0.284, BAYES_05=-1.11]
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 rrLbjjq1EqKO for <enum@core3.amsl.com>; Sun, 27 Jun 2010 13:54:02 -0700 (PDT)
Received: from softronics.hoeneisen.ch (softronics.hoeneisen.ch [62.2.86.178]) by core3.amsl.com (Postfix) with ESMTP id C3E733A69E3 for <enum@ietf.org>; Sun, 27 Jun 2010 13:54:02 -0700 (PDT)
Received: from localhost ([127.0.0.1]) by softronics.hoeneisen.ch with esmtp (Exim 4.69) (envelope-from <bernie@ietf.hoeneisen.ch>) id 1OSyri-00021X-O8 for enum@ietf.org; Sun, 27 Jun 2010 22:54:10 +0200
Date: Sun, 27 Jun 2010 22:54:10 +0200 (CEST)
From: Bernie Hoeneisen <bernie@ietf.hoeneisen.ch>
X-X-Sender: bhoeneis@softronics.hoeneisen.ch
To: IETF ENUM list <enum@ietf.org>
Message-ID: <alpine.DEB.2.00.1006272236260.7595@softronics.hoeneisen.ch>
User-Agent: Alpine 2.00 (DEB 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
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] Proposed Agenda ENUM WG IETF-78
X-BeenThere: enum@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Enum Discussion List <enum.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/enum>, <mailto:enum-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Sun, 27 Jun 2010 20:54:04 -0000

Dear ENUM WG

As you might have noticed there will be an ENUM WG session in Maastricht. 
This meeting is dedicated to discuss the E2MD (E.164 To MetaData 
Mapping) matters:

   http://trac.tools.ietf.org/bof/e2md/trac/wiki
   http://www.ietf.org/mail-archive/web/e2md/current/msg00567.html


To avoid cross-posting, please DO NOT discuss any technical E2MD issues on
the ENUM Mailing list, rather send technical stuff to the E2MD list:

  e2md@ietf.org  /  https://www.ietf.org/mailman/listinfo/e2md


The ENUM list will be used for administrative stuff only, such as 
agenda bashing.



Proposed Agenda
---------------

1) Note well / Blue Sheets / Agenda Bashing (5')

2) Status Update of ENUM Drafts (5')
    (in particular results of ENUM Trilogy processing)

3) E2MD: Communicate boundary conditions set out by the AD (5')
    http://www.ietf.org/mail-archive/web/e2md/current/msg00567.html

4) E2MD: Explain E2MD and background (15')

5) E2MD: Present proposal on how to proceed with E2MD (15')
    (results of the E2MD conference calls)

6) E2MD: Presentation and discussion of
    Problem Statement / Use Cases / Revised Draft Charter

7) E2MD: Comments / issues / objections we got in Anaheim


Later in the week there is be a Bar-BoF planned, which means that 
6) or 7) will most likely (continued to) be discussed in the Bar-BOF.


cheers,
  Bernie, ENUM Co-chair

--

http://ucom.ch/
Tech Consulting for Internet Standardization


From lconroy@insensate.co.uk  Sun Jun 27 14:44:45 2010
Return-Path: <lconroy@insensate.co.uk>
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 C4EF63A6954 for <enum@core3.amsl.com>; Sun, 27 Jun 2010 14:44:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.561
X-Spam-Level: 
X-Spam-Status: No, score=-0.561 tagged_above=-999 required=5 tests=[AWL=-0.562, BAYES_50=0.001]
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 AatStDEwu+aX for <enum@core3.amsl.com>; Sun, 27 Jun 2010 14:44:44 -0700 (PDT)
Received: from insensate.co.uk (ghost.insensate.co.uk [213.152.49.121]) by core3.amsl.com (Postfix) with ESMTP id 466413A6800 for <enum@ietf.org>; Sun, 27 Jun 2010 14:44:44 -0700 (PDT)
Received: from [127.0.0.1] (localhost [127.0.0.1]) by insensate.co.uk (Postfix) with ESMTP id 6E328267D62; Sun, 27 Jun 2010 22:44:52 +0100 (BST)
Mime-Version: 1.0 (Apple Message framework v1078)
Content-Type: text/plain; charset=us-ascii
From: Lawrence Conroy <lconroy@insensate.co.uk>
In-Reply-To: <alpine.DEB.2.00.1006272236260.7595@softronics.hoeneisen.ch>
Date: Sun, 27 Jun 2010 22:44:52 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <C2994F77-51D3-473A-AE78-26E22EF6C126@insensate.co.uk>
References: <alpine.DEB.2.00.1006272236260.7595@softronics.hoeneisen.ch>
To: Bernie Hoeneisen <bernie@ietf.hoeneisen.ch>
X-Mailer: Apple Mail (2.1078)
Cc: IETF ENUM list <enum@ietf.org>
Subject: Re: [Enum] Proposed Agenda ENUM WG IETF-78
X-BeenThere: enum@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Enum Discussion List <enum.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/enum>, <mailto:enum-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Sun, 27 Jun 2010 21:44:45 -0000

Hi Bernie, folks,
  This depends on your definition of E2MD; item 2 is "pure" ENUM, even =
if
it forms a "known platform" on which E2MD can build.

I expect it will take a bit more than 5 minutes to give a fair summary =
of
the outcome of the ENUM troika. I believe it IS important to summarise =
where
we end up with these documents, if only for people who just want to =
create
Enumservices within that framework.

   Anaheim sure sounded like people denying that gravity existed even =
when
   apples had been falling all over the place FOR YEARS. Just like when =
Dean
   sat at the back of the hall in an IMPP meeting and exchanged messages =
with
   folk doing the presentation, and people still said that SIMPLE didn't =
work,
   or that this was unfair. Do not underestimate belief.

Let's not assume that everyone is on the same page (or get better =
bouncers :).
=3D> I suspect we'll need nearer 15 minutes than 5 to cover the three =
documents.

For the rest, speak on Tuesday.

all the best,
  Lawrence


On 27 Jun 2010, at 21:54, Bernie Hoeneisen wrote:
> Dear ENUM WG
>=20
> As you might have noticed there will be an ENUM WG session in =
Maastricht. This meeting is dedicated to discuss the E2MD (E.164 To =
MetaData Mapping) matters:
>=20
>  http://trac.tools.ietf.org/bof/e2md/trac/wiki
>  http://www.ietf.org/mail-archive/web/e2md/current/msg00567.html
>=20
>=20
> To avoid cross-posting, please DO NOT discuss any technical E2MD =
issues on
> the ENUM Mailing list, rather send technical stuff to the E2MD list:
>=20
> e2md@ietf.org  /  https://www.ietf.org/mailman/listinfo/e2md
>=20
>=20
> The ENUM list will be used for administrative stuff only, such as =
agenda bashing.
>=20
>=20
>=20
> Proposed Agenda
> ---------------
>=20
> 1) Note well / Blue Sheets / Agenda Bashing (5')
>=20
> 2) Status Update of ENUM Drafts (5')
>   (in particular results of ENUM Trilogy processing)
>=20
> 3) E2MD: Communicate boundary conditions set out by the AD (5')
>   http://www.ietf.org/mail-archive/web/e2md/current/msg00567.html
>=20
> 4) E2MD: Explain E2MD and background (15')
>=20
> 5) E2MD: Present proposal on how to proceed with E2MD (15')
>   (results of the E2MD conference calls)
>=20
> 6) E2MD: Presentation and discussion of
>   Problem Statement / Use Cases / Revised Draft Charter
>=20
> 7) E2MD: Comments / issues / objections we got in Anaheim
>=20
>=20
> Later in the week there is be a Bar-BoF planned, which means that 6) =
or 7) will most likely (continued to) be discussed in the Bar-BOF.
>=20
>=20
> cheers,
> Bernie, ENUM Co-chair
>=20
> --
>=20
> http://ucom.ch/
> Tech Consulting for Internet Standardization
>=20
> _______________________________________________
> enum mailing list
> enum@ietf.org
> https://www.ietf.org/mailman/listinfo/enum

