Re: [Speermint] shutting down and the arch doc

"Jan Seedorf" <Jan.Seedorf@neclab.eu> Tue, 08 June 2010 08:04 UTC

Return-Path: <Jan.Seedorf@neclab.eu>
X-Original-To: speermint@core3.amsl.com
Delivered-To: speermint@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AF3A128C0FA for <speermint@core3.amsl.com>; Tue, 8 Jun 2010 01:04:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.557
X-Spam-Level:
X-Spam-Status: No, score=-0.557 tagged_above=-999 required=5 tests=[AWL=-0.558, 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 Df2ei-ANMONr for <speermint@core3.amsl.com>; Tue, 8 Jun 2010 01:04:13 -0700 (PDT)
Received: from smtp0.neclab.eu (smtp0.neclab.eu [195.37.70.41]) by core3.amsl.com (Postfix) with ESMTP id 3E5FC28C0E1 for <speermint@ietf.org>; Tue, 8 Jun 2010 01:04:13 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp0.neclab.eu (Postfix) with ESMTP id D66162C000C08; Tue, 8 Jun 2010 10:04:13 +0200 (CEST)
X-Virus-Scanned: Amavisd on Debian GNU/Linux (atlas2.office)
Received: from smtp0.neclab.eu ([127.0.0.1]) by localhost (atlas2.office [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bwA-zXDb0IoU; Tue, 8 Jun 2010 10:04:13 +0200 (CEST)
Received: from VENUS.office (mx2.office [192.168.24.15]) by smtp0.neclab.eu (Postfix) with ESMTP id B71F32C000C07; Tue, 8 Jun 2010 10:03:48 +0200 (CEST)
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 08 Jun 2010 10:03:47 +0200
Message-ID: <B94940C43117794C9432FF5FF0CCB50601434E32@VENUS.office>
In-Reply-To: <9E1B4F4BA637A44BAD5E18CF09EAFB90047AFA88@mse14be2.mse14.exchange.ms>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [Speermint] shutting down and the arch doc
Thread-Index: Acr9zWp60wKwPsoCM0iMEyCTYZ/liQFb/f+dAAFRMeAAABLzUADndZ6Q
References: <C8240CEB.3EA2F%jon.peterson@neustar.biz><C82D3A51.C76A%d.malas@cablelabs.com><C4064AF1C9EC1F40868C033DB94958C701CDA08F@XMB-RCD-111.cisco.com> <9E1B4F4BA637A44BAD5E18CF09EAFB90047AFA88@mse14be2.mse14.exchange.ms>
From: Jan Seedorf <Jan.Seedorf@neclab.eu>
To: Terry Martin <tmartin@timedatacorp.com>, "Mike Hammer (hmmr)" <hmmr@cisco.com>, Daryl Malas <D.Malas@cablelabs.com>, "Peterson, Jon" <jon.peterson@neustar.biz>, speermint@ietf.org
Subject: Re: [Speermint] shutting down and the arch doc
X-BeenThere: speermint@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Mailing list for the speermint working group <speermint.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/speermint>, <mailto:speermint-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/speermint>
List-Post: <mailto:speermint@ietf.org>
List-Help: <mailto:speermint-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/speermint>, <mailto:speermint-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Jun 2010 08:04:14 -0000

Dear Terry,

> I will review the last set of documents and will send my comments.. They may
> not be as technical but they come from an operation perspective.
Excellent, we are looking forward to your comments and would appreciate any feedback you have for our draft:

- SPEERMINT Security Threats and Suggested Countermeasures
(http://tools.ietf.org/html/draft-ietf-speermint-voipthreats-02)

 - Jan

> -----Original Message-----
> From: speermint-bounces@ietf.org [mailto:speermint-bounces@ietf.org] On Behalf
> Of Terry Martin
> Sent: Donnerstag, 3. Juni 2010 19:36
> To: Mike Hammer (hmmr); Daryl Malas; Peterson, Jon; speermint@ietf.org
> Subject: Re: [Speermint] shutting down and the arch doc
> 
> I have been following this from the beginning and I work with a lot of
> telephone companies and VoIP provides and feel what your working is key to how
> islands of carriers are going to be communicating.
> 
> 
> 
> I will review the last set of documents and will send my comments.. They may
> not be as technical but they come from an operation perspective.
> 
> 
> 
> Thanks for your work
> 
> 
> 
> Terry
> 
> 
> 
> From: speermint-bounces@ietf.org [mailto:speermint-bounces@ietf.org] On Behalf
> Of Mike Hammer (hmmr)
> Sent: Thursday, June 03, 2010 10:32 AM
> To: Daryl Malas; Peterson, Jon; speermint@ietf.org
> Subject: Re: [Speermint] shutting down and the arch doc
> 
> 
> 
> Agree with that approach.
> 
> 
> 
> Mike
> 
> 
> 
> 
> 
> From: speermint-bounces@ietf.org [mailto:speermint-bounces@ietf.org] On Behalf
> Of Daryl Malas
> Sent: Thursday, June 03, 2010 12:54 PM
> To: Peterson, Jon; speermint@ietf.org
> Subject: Re: [Speermint] shutting down and the arch doc
> 
> 
> 
> Jon et. al,
> 
> I agree we should finish the architecture document.  If members of this
> mailing list and the working group think it requires greater definition around
> certain functions, then please contribute.  I would like to suggest we focus
> on two drafts to wrap up in Maastricht:
> 
> Architecture
> Security
> 
> After completing these two drafts, we shut down the working group by Beijing.
> 
> Thoughts?
> 
> Regards,
> 
> Daryl
> 
> 
> 
> On 5/27/10 12:50 PM, "Peterson, Jon" <jon.peterson@neustar.biz> wrote:
> 
> 
> While all IETF working groups look forward to the day they can close their
> doors, I'm not sure I'd be happy to see SPEERMINT make its final bow without
> completing the architecture document.
> 
> I believe that in the LUF/LRF distinction, the SPEERMINT group has captured an
> idea that is valuable, and moreover one which, as the original charter of this
> group intended, identifies a reality of deployments that the standards
> community had previously ignored. It explodes the conceit that a one-step
> resolution process, just transforming a telephone number into a "global" URI,
> will address the needs of the sort of peering communities this group examines.
> While the distinction between LUF and LRF is not a precise one, and has never
> been immensely well understood, I contend that it is valuable nonetheless, and
> that if confusion about the idea prompts us to discard the work in SPEERMINT,
> I have no reason to expect anything different to happen in DRINKS or any other
> group that must operate on these same architectures. I don't think the
> sketches in the terminology draft suffice as a foundation for that work.
> 
> Finishing the architecture document is not solving world hunger. While
> everything in the IETF takes much longer than you'd imagine, I don't think
> this has to be one or two years out - I think it would be reasonable to make a
> final push to clear up the snags in the document, and just set a deadline by
> which this group will emit it as an Informational. It doesn't have to be
> perfect, it just has to be able to serve as the framework for the subsequent
> discussions in DRINKS and other future arenas. I think this is an an
> achievable, and relatively honorable, way to round up the work that the
> SPEERMINT charter originally laid out.
> 
> If there is enough energy here for one last jaunt, I'd be happy to assist that
> effort in any capacity.
> 
> Jon Peterson
> NeuStar, Inc.