Re: [e2md] 4th e2md conference call, Tue 29 June 2010, 17:00 UT

"PFAUTZ, PENN L (ATTCORP)" <pp3129@att.com> Tue, 29 June 2010 17:58 UTC

Return-Path: <pp3129@att.com>
X-Original-To: e2md@core3.amsl.com
Delivered-To: e2md@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0F8693A6C19 for <e2md@core3.amsl.com>; Tue, 29 Jun 2010 10:58:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.185
X-Spam-Level:
X-Spam-Status: No, score=-104.185 tagged_above=-999 required=5 tests=[BAYES_40=-0.185, 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 LDIlWuSaBEDC for <e2md@core3.amsl.com>; Tue, 29 Jun 2010 10:58:02 -0700 (PDT)
Received: from mail167.messagelabs.com (mail167.messagelabs.com [216.82.253.179]) by core3.amsl.com (Postfix) with ESMTP id 6FF573A6A7B for <e2md@ietf.org>; Tue, 29 Jun 2010 10:58:02 -0700 (PDT)
X-VirusChecked: Checked
X-Env-Sender: pp3129@att.com
X-Msg-Ref: server-5.tower-167.messagelabs.com!1277834291!21499446!1
X-StarScan-Version: 6.2.4; banners=-,-,-
X-Originating-IP: [144.160.20.146]
Received: (qmail 7036 invoked from network); 29 Jun 2010 17:58:12 -0000
Received: from sbcsmtp7.sbc.com (HELO mlpd194.enaf.sfdc.sbc.com) (144.160.20.146) by server-5.tower-167.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 29 Jun 2010 17:58:12 -0000
Received: from enaf.sfdc.sbc.com (localhost.localdomain [127.0.0.1]) by mlpd194.enaf.sfdc.sbc.com (8.14.4/8.14.4) with ESMTP id o5THvkju024842 for <e2md@ietf.org>; Tue, 29 Jun 2010 13:57:48 -0400
Received: from gaalpa1msgusr7a.ugd.att.com (gaalpa1msgusr7a.ugd.att.com [135.53.26.15]) by mlpd194.enaf.sfdc.sbc.com (8.14.4/8.14.4) with ESMTP id o5THvh6f024603 for <e2md@ietf.org>; Tue, 29 Jun 2010 13:57:43 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="----_=_NextPart_001_01CB17B4.A0A771DD"
Date: Tue, 29 Jun 2010 13:58:05 -0400
Message-ID: <35FE871E2B085542A35726420E29DA6B0444E4A0@gaalpa1msgusr7a.ugd.att.com>
In-Reply-To: <alpine.DEB.2.00.1006250856450.21879@softronics.hoeneisen.ch>
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
Thread-Topic: [e2md] 4th e2md conference call, Tue 29 June 2010, 17:00 UT
Thread-Index: AcsUM9puwoXVCrwrT/qdlT9LaxutYwDgKmww
References: <alpine.DEB.2.00.1006242126490.2458@softronics.hoeneisen.ch><FC94FE98-9AE1-44A0-A49A-F022E29184FA@softarmor.com> <alpine.DEB.2.00.1006250856450.21879@softronics.hoeneisen.ch>
From: "PFAUTZ, PENN L (ATTCORP)" <pp3129@att.com>
To: Bernie Hoeneisen <bernie@ietf.hoeneisen.ch>, Dean Willis <dean.willis@softarmor.com>
Cc: "E.164 To MetaData BOF discussion list" <e2md@ietf.org>
Subject: Re: [e2md] 4th e2md conference call, Tue 29 June 2010, 17:00 UT
X-BeenThere: e2md@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "E.164 To MetaData \(E2MD\) BOF discussion list" <e2md.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/e2md>, <mailto:e2md-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/e2md>
List-Post: <mailto:e2md@ietf.org>
List-Help: <mailto:e2md-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/e2md>, <mailto:e2md-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 29 Jun 2010 17:58:04 -0000

My notes of the meeting...



Penn Pfautz
AT&T Access Management
+1-732-420-4962

-----Original Message-----
From: e2md-bounces@ietf.org [mailto:e2md-bounces@ietf.org] On Behalf Of
Bernie Hoeneisen
Sent: Friday, June 25, 2010 2:59 AM
To: Dean Willis
Cc: E.164 To MetaData BOF discussion list
Subject: Re: [e2md] 4th e2md conference call, Tue 29 June 2010, 17:00 UT

Ouuupss...thanks for reporting this.

   I meant _Tuesday_, 29th of June.

Sorry about that.

cheers,
  Bernie

--

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


On Thu, 24 Jun 2010, Dean Willis wrote:

>
> Thursday and 29 June are mutually exclusive according to my calendar.
Which 
> did you have in mind?
>
> On Jun 24, 2010, at 2:33 PM, Bernie Hoeneisen wrote:
>
>> Dear e2md:ers,
>> 
>> Please find the details of the 4th e2md conference call below:
>> 
>> 
>> * Date/Time:
>> 
>> Thursday, 29 June 2010, 17:00 UT (18:00 BST, 19:00 CEST, 13:00 EDT)
>> Duration: 60 min
>> 
>> 
>> * Dial-In:
>> 
>> - SIP:   sip:60@mcu-hd.switch.ch --> Conference ID: 60 #
>> - H.323: h323:60@mcu-hd.switch.ch --> Conference ID: 60 #
>> - PSTN:  +41 44 250 96 60
>> 
>> 
>> * Collaboration Tool:
>> 
>> http://collab.switch.ch/ietf-e2md
>> (as usual we will use this during the call)
>> 
>> 
>> * Goal
>> 
>> Preparation E2MD (ENUM WG) session for Maastricht, and
>> decide on who does what by when.
>> 
>> 
>> * Agenda (draft):
>> 
>> 1) Welcome / Roll-Call / Scribe
>> 
>> 2) Gathering Input for making a charter proposal
>>
>>    Background:
>>
>>    - We decided to go for the following approach:
>>      - Narrow down the problem space to E2MD services for:
>>        - g-spid, cnam, service capabilities, (unused, and send-n)
>>      - For each E2MD service
>>        - document the requirements, and
>>        - develop an individual solution as PS
>>      - Longer term requirements are out-of-scope for this approach
>>
>>    - See also:
>>      http://trac.tools.ietf.org/bof/e2md/trac/wiki
>> 
>>
>>  3) Decide how does what by when
>>
>>     Deadlines:
http://www.ietf.org/meeting/cutoff-dates-2010.html#IETF78
>>
>>     a) Write I-Ds on the E2MD services containing a concise
>>        problem statement, requirments use cases, etc.
>>        (avoid a particular solution at this point in time,
>>        as any solution almost certainly triggers nasty objections.)
>>
>>        - g-spid (Penn)
>>        - cnam (Rich?)
>>        - service capabilities (...?)
>>        - unused (Lawrence?)
>>        - send-n (Ray?)
>>
>>     b) Work out charter proposal to be discussed in Maastricht
(Dave?)
>>
>>     Note: 3a) is a precondition for 3b)
>> 
>>
>>  4) AOB
>> 
>> 
>> 
>> Note: The discussion was rather fuzzy in some recent conf calls.
>>     If during this call there is a need to structure the discussion
>>     and give also the less "dominant" participants  a chance to
speak,
>>     we will use the collaboration tool to maintain a speakers list,
>>     which has a built-in "Raise hand" function.
>> 
>> 
>> cheers,
>> Bernie
>> 
>> --
>> 
>> http://ucom.ch/
>> Tech Consulting for Internet Standardization
>> 
>> _______________________________________________
>> e2md mailing list
>> e2md@ietf.org
>> https://www.ietf.org/mailman/listinfo/e2md
>> 
>
_______________________________________________
e2md mailing list
e2md@ietf.org
https://www.ietf.org/mailman/listinfo/e2md