From peppermint-bounces@ietf.org Thu Jun 5 06:46:35 2008 Return-Path: X-Original-To: peppermint-archive@optimus.ietf.org Delivered-To: ietfarch-peppermint-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3487E3A6B45; Thu, 5 Jun 2008 06:46:35 -0700 (PDT) X-Original-To: peppermint@core3.amsl.com Delivered-To: peppermint@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8F81B3A6B45 for ; Thu, 5 Jun 2008 06:46:34 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.002 X-Spam-Level: X-Spam-Status: No, score=0.002 tagged_above=-999 required=5 tests=[BAYES_50=0.001, HTML_MESSAGE=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 BWZwSmpbja1w for ; Thu, 5 Jun 2008 06:46:32 -0700 (PDT) Received: from dnsmx2pya.telcordia.com (dnsmx2pya.telcordia.com [128.96.20.32]) by core3.amsl.com (Postfix) with ESMTP id CED863A685D for ; Thu, 5 Jun 2008 06:46:31 -0700 (PDT) Received: from rrc-dte-ieg01.cc.telcordia.com (rrc-dte-ieg01.cc.telcordia.com [128.96.20.22]) by dnsmx2pya.telcordia.com (8.11.7+Sun/8.9.3) with SMTP id m55DkaF16528 for ; Thu, 5 Jun 2008 09:46:36 -0400 (EDT) Received: from pya-dte-exhb1.dte.telcordia.com ([128.96.20.11]) by rrc-dte-ieg01.cc.telcordia.com (SMSSMTP 4.1.9.35) with SMTP id M2008060509463314319 for ; Thu, 05 Jun 2008 09:46:33 -0400 Received: from rrc-dte-exmb2.dte.telcordia.com ([128.96.180.27]) by pya-dte-exhb1.dte.telcordia.com ([128.96.20.11]) with mapi; Thu, 5 Jun 2008 09:46:33 -0400 From: "Guyton, Deborah A" To: "peppermint@ietf.org" Date: Thu, 5 Jun 2008 09:46:32 -0400 Thread-Topic: agenda item Thread-Index: AcjHEo/6n3QJADNpQPaa3xM4JkpwjQ== Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US MIME-Version: 1.0 Subject: [PEPPERMINT] agenda item X-BeenThere: peppermint@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Provisioning Extensions in Peering Registries for Multimedia INTerconnection List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1741077881==" Sender: peppermint-bounces@ietf.org Errors-To: peppermint-bounces@ietf.org --===============1741077881== Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_AE85DAD2723E724EAB2A704148DE15AC278DF32FE3rrcdteexmb2dt_" --_000_AE85DAD2723E724EAB2A704148DE15AC278DF32FE3rrcdteexmb2dt_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Richard, I'm planning to send in a contribution for a provisioning interface for a R= egistry database and request a presentation slot to present a summary overv= iew. Debbie Guyton --_000_AE85DAD2723E724EAB2A704148DE15AC278DF32FE3rrcdteexmb2dt_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Richard,

I’m planning to send in a contribution for a provisioning interface for a Registry database and request a presentation s= lot to present a summary overview.

Debbie Guyton

--_000_AE85DAD2723E724EAB2A704148DE15AC278DF32FE3rrcdteexmb2dt_-- --===============1741077881== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ PEPPERMINT mailing list PEPPERMINT@ietf.org https://www.ietf.org/mailman/listinfo/peppermint --===============1741077881==-- From peppermint-bounces@ietf.org Thu Jun 5 09:03:45 2008 Return-Path: X-Original-To: peppermint-archive@optimus.ietf.org Delivered-To: ietfarch-peppermint-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B7E243A6C2A; Thu, 5 Jun 2008 09:03:45 -0700 (PDT) X-Original-To: peppermint@core3.amsl.com Delivered-To: peppermint@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id EF3F73A685D for ; Thu, 5 Jun 2008 09:03:44 -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=[AWL=-0.001, BAYES_00=-2.599, HTML_MESSAGE=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 3+f-eEa7xcSv for ; Thu, 5 Jun 2008 09:03:41 -0700 (PDT) Received: from mail.songbird.com (unknown [IPv6:2001:470:1:76:2c0:9fff:fe3e:4009]) by core3.amsl.com (Postfix) with ESMTP id A28EC3A6C2D for ; Thu, 5 Jun 2008 09:01:32 -0700 (PDT) Received: from rshockeyPC (neustargw.va.neustar.com [209.173.53.233]) (authenticated bits=0) by mail.songbird.com (8.12.11.20060308/8.12.11) with ESMTP id m55G0KhJ016024 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 5 Jun 2008 09:00:21 -0700 From: "Richard Shockey" To: "'Guyton, Deborah A'" , References: In-Reply-To: Date: Thu, 5 Jun 2008 12:01:18 -0400 Message-ID: <143501c8c725$65893f70$309bbe50$@us> MIME-Version: 1.0 X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: AcjHEo/6n3QJADNpQPaa3xM4JkpwjQAEs2yA Content-Language: en-us X-SongbirdInformation: support@songbird.com for more information X-Songbird: Clean X-Songbird-From: richard@shockey.us Subject: Re: [PEPPERMINT] agenda item X-BeenThere: peppermint@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Provisioning Extensions in Peering Registries for Multimedia INTerconnection List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0401959439==" Sender: peppermint-bounces@ietf.org Errors-To: peppermint-bounces@ietf.org This is a multipart message in MIME format. --===============0401959439== Content-Type: multipart/alternative; boundary="----=_NextPart_000_1436_01C8C703.DE779F70" Content-Language: en-us This is a multipart message in MIME format. ------=_NextPart_000_1436_01C8C703.DE779F70 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Will do .thanks. From: peppermint-bounces@ietf.org [mailto:peppermint-bounces@ietf.org] On Behalf Of Guyton, Deborah A Sent: Thursday, June 05, 2008 9:47 AM To: peppermint@ietf.org Subject: [PEPPERMINT] agenda item Richard, I'm planning to send in a contribution for a provisioning interface for a Registry database and request a presentation slot to present a summary overview. Debbie Guyton ------=_NextPart_000_1436_01C8C703.DE779F70 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Will do …thanks.

From:= peppermint-bounces@ietf.org [mailto:peppermint-bounces@ietf.org] On = Behalf Of Guyton, Deborah A
Sent: Thursday, June 05, 2008 9:47 AM
To: peppermint@ietf.org
Subject: [PEPPERMINT] agenda item

Richard,=

I’m planning to send in a contribution for a provisioning interface for a = Registry database and request a presentation slot to present a summary = overview.

Debbie Guyton

------=_NextPart_000_1436_01C8C703.DE779F70-- --===============0401959439== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ PEPPERMINT mailing list PEPPERMINT@ietf.org https://www.ietf.org/mailman/listinfo/peppermint --===============0401959439==-- From peppermint-bounces@ietf.org Mon Jun 16 08:17:11 2008 Return-Path: X-Original-To: peppermint-archive@optimus.ietf.org Delivered-To: ietfarch-peppermint-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9A8FC3A6927; Mon, 16 Jun 2008 08:17:11 -0700 (PDT) X-Original-To: peppermint@ietf.org Delivered-To: peppermint@core3.amsl.com Received: by core3.amsl.com (Postfix, from userid 0) id 3224D3A6908; Fri, 13 Jun 2008 14:00:01 -0700 (PDT) From: The IESG To: ietf-announce@ietf.org Mime-Version: 1.0 Message-Id: <20080613210002.3224D3A6908@core3.amsl.com> Date: Fri, 13 Jun 2008 14:00:02 -0700 (PDT) X-Mailman-Approved-At: Mon, 16 Jun 2008 08:17:10 -0700 Cc: peppermint@ietf.org, rich.shockey@neustar.biz Subject: [PEPPERMINT] WG Action: Data for Reachability of Inter/tra-NetworK SIP (drinks) X-BeenThere: peppermint@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Provisioning Extensions in Peering Registries for Multimedia INTerconnection List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: peppermint-bounces@ietf.org Errors-To: peppermint-bounces@ietf.org A new IETF working group has been formed in the Real-Time Applications and Infrastructure Area. For additional information, please contact the Area Directors or the WG Chairs. Data for Reachability of Inter/tra-NetworK SIP (drinks) --------------------------------------------- Last Modified: 13 June 2008 Current Status: Active Working Group Chairs: Richard Shockey (rich.shockey@neustar.biz) Alexander Mayrhofer (alexander.mayrhofer@enum.at) Area Directorate: Real Time Applications (RAI) RAI Director(s): Jon Peterson (jon.peterson@neustar.biz) Cullen Jennings (fluffy@cisco.com) RAI Area Advisor: Jon Peterson (jon.peterson@neustar.biz) Mailing Lists: peppermint@ietf.org General information about the mailing list is at: https://www1.ietf.org/mailman/listinfo/peppermint Working Group Description: The IETF has been working on various aspects of SIP-enabled Multimedia administrative domains among SIP Service Providers (SSP's). SSP's are entities that provide session services utilizing SIP signaling to their customers. In addition, the IETF has done significant work on data exchanges among various network elements. The DRINKS working group is chartered with a scope that is orthogonal to SPEERMINT and ENUM. The protocol work of DRINKS will be designed to build from the work of SPEERMINT and ENUM to identify and define the data structures and data exchange protocol(s) among SIP based Multimedia administrative domains. The ENUM working group is specifically chartered to develop protocols that involve the translation of E.164 numbers to URIs. While the SPEERMINT working group has been chartered to develop requirements and best current practices among real-time application SSPs and to describe how such services may best interconnect across administrative boundaries. These administrative domains may be of any practical size and could be any type of SSP, such as recognized telephony carriers, enterprises, end-user groups, or Federations. Data exchanges among these administrative domains may be bi-lateral or multi-lateral in nature, and could include bulk updates and/or more granular real-time updates. Administrative domains may exchange data through the use of an external registry to aggregate data from multiple administrative domains or multiple data providers into a single view. The DRINKS WG will provide details of how Session Establishment Data (SED) is collected, what comprises SED, how SED should be used to properly identify an optimal path to a destination SIP user agent (UA),either internally or externally to the SSP. In addition DRINKS will insure that the SED and the SIP session data is securely exchanged between the peering functions. Typical SED data might include: + Routes - Destination SIP/SIPS/TEL URI Egress and Ingress Routes - Relevant route names, identifiers, and services - Attributes affecting route selection - PSTN database information + Targets - Individual, ranges, or groups of user-agent identifiers - Target aggregation entities (e.g. service areas) and target-to-aggregate associations + Treatment Profiles - Priority - Location Potential SED Data types not in scope will be session rating or other billing or pricing information between SSP's The working group will draw upon expert advice and on-going consultation from the ENUM and SPEERMINT working groups, and also the XML Directorate. The working group will consider the reuse of elements of RFC 4114. The final work product(s) from this working group will utilize and be based on XML documents and XML document exchanges. GOALS AND MILESTONES Requirements for Session Establishment Data (SED) data exchanges. -- Sept 08 Exchanging of Session Establishment Data (SED) from data providers to registries or between bi/multi-lateral partners. -- Nov 08 Exchange of Session Establishment Data (SED) from registries to Location Routing Function databases. --- Feb 09 _______________________________________________ PEPPERMINT mailing list PEPPERMINT@ietf.org https://www.ietf.org/mailman/listinfo/peppermint From peppermint-bounces@ietf.org Mon Jun 16 18:59:21 2008 Return-Path: X-Original-To: peppermint-archive@optimus.ietf.org Delivered-To: ietfarch-peppermint-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1FB5928C16D; Mon, 16 Jun 2008 18:59:21 -0700 (PDT) X-Original-To: peppermint@core3.amsl.com Delivered-To: peppermint@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B923E3A68AC for ; Mon, 16 Jun 2008 18:59:20 -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=[AWL=0.000, 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 1xfodq+OogWn for ; Mon, 16 Jun 2008 18:59:19 -0700 (PDT) Received: from mail.songbird.com (sbh176.songbird.com [72.52.113.176]) by core3.amsl.com (Postfix) with ESMTP id AA5103A68A8 for ; Mon, 16 Jun 2008 18:59:19 -0700 (PDT) Received: from rshockeyPC (neustargw.va.neustar.com [209.173.53.233]) (authenticated bits=0) by mail.songbird.com (8.12.11.20060308/8.12.11) with ESMTP id m5GEiOKC029722 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for ; Mon, 16 Jun 2008 07:44:41 -0700 From: "Richard Shockey" To: References: <20080613210002.3224D3A6908@core3.amsl.com> In-Reply-To: <20080613210002.3224D3A6908@core3.amsl.com> Date: Mon, 16 Jun 2008 10:44:58 -0400 Message-ID: <114901c8cfbf$9fd37e00$df7a7a00$@us> MIME-Version: 1.0 X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: AcjNmIiRT4fddf/UTJio8fQVYcSjPACJrIzQ Content-Language: en-us X-SongbirdInformation: support@songbird.com for more information X-Songbird: Clean X-Songbird-From: richard@shockey.us Subject: Re: [PEPPERMINT] WG Action: Data for Reachability of Inter/tra-NetworK SIP (drinks) X-BeenThere: peppermint@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Provisioning Extensions in Peering Registries for Multimedia INTerconnection List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: peppermint-bounces@ietf.org Errors-To: peppermint-bounces@ietf.org You have all seen this by now .. we have a one hour slot ready so that should show up on the draft agenda shortly. I will arrange this week for the change of mail address from peppermint@ietf.org to drinks@ietf.org The Secretariat should be able to enroll the current list pretty automatically. Needless to say we need to begin Agenda discussions, I have one request so far. > -----Original Message----- > From: The IESG [mailto:iesg@ietf.org] > Sent: Friday, June 13, 2008 5:00 PM > To: ietf-announce@ietf.org > Cc: alexander.mayrhofer@enum.at; rich.shockey@neustar.biz; > peppermint@ietf.org > Subject: WG Action: Data for Reachability of Inter/tra-NetworK SIP > (drinks) > > A new IETF working group has been formed in the Real-Time Applications > and > Infrastructure Area. For additional information, please contact the > Area > Directors or the WG Chairs. > > Data for Reachability of Inter/tra-NetworK SIP (drinks) > --------------------------------------------- > Last Modified: 13 June 2008 > > Current Status: Active Working Group > > Chairs: > > Richard Shockey (rich.shockey@neustar.biz) > Alexander Mayrhofer (alexander.mayrhofer@enum.at) > > Area Directorate: Real Time Applications (RAI) > > RAI Director(s): > > Jon Peterson (jon.peterson@neustar.biz) > Cullen Jennings (fluffy@cisco.com) > > RAI Area Advisor: > > Jon Peterson (jon.peterson@neustar.biz) > > Mailing Lists: peppermint@ietf.org > General information about the mailing list is at: > https://www1.ietf.org/mailman/listinfo/peppermint > > Working Group Description: > > The IETF has been working on various aspects of SIP-enabled Multimedia > administrative domains among SIP Service Providers (SSP's). SSP's are > entities that provide session services utilizing SIP signaling to > their > customers. In addition, the IETF has done significant work on data > exchanges among various network elements. > > The DRINKS working group is chartered with a scope that is orthogonal > to > SPEERMINT and ENUM. The protocol work of DRINKS will be designed to > build from the work of SPEERMINT and ENUM to identify and define the > data structures and data exchange protocol(s) among SIP based > Multimedia > administrative domains. > > The ENUM working group is specifically chartered to develop protocols > that involve the translation of E.164 numbers to URIs. While the > SPEERMINT working group has been chartered to develop requirements and > best current practices among real-time application SSPs and to > describe > how such services may best interconnect across administrative > boundaries. > > These administrative domains may be of any practical size and could be > any type of SSP, such as recognized telephony carriers, enterprises, > end-user groups, or Federations. Data exchanges among these > administrative domains may be bi-lateral or multi-lateral in nature, > and > could include bulk updates and/or more granular real-time updates. > > Administrative domains may exchange data through the use of an > external > registry to aggregate data from multiple administrative domains or > multiple data providers into a single view. > > The DRINKS WG will provide details of how Session Establishment Data > (SED) is collected, what comprises SED, how SED should be used to > properly identify an optimal path to a destination SIP user agent > (UA),either internally or externally to the SSP. In addition DRINKS > will > insure that the SED and the SIP session data is securely exchanged > between the peering functions. > > Typical SED data might include: > > + Routes > - Destination SIP/SIPS/TEL URI Egress and Ingress Routes > - Relevant route names, identifiers, and services > - Attributes affecting route selection > - PSTN database information > > + Targets > - Individual, ranges, or groups of user-agent identifiers > - Target aggregation entities (e.g. service areas) and > target-to-aggregate associations > > + Treatment Profiles > - Priority > - Location > > Potential SED Data types not in scope will be session rating or other > billing or pricing information between SSP's > > The working group will draw upon expert advice and on-going > consultation > from the ENUM and SPEERMINT working groups, and also the XML > Directorate. > The working group will consider the reuse of elements of RFC 4114. > > The final work product(s) from this working group will utilize and be > based on XML documents and XML document exchanges. > > > GOALS AND MILESTONES > > Requirements for Session Establishment Data (SED) data exchanges. -- > Sept 08 > > Exchanging of Session Establishment Data (SED) from data providers to > registries or between bi/multi-lateral partners. -- Nov 08 > > Exchange of Session Establishment Data (SED) from registries to > Location > Routing Function databases. --- Feb 09 _______________________________________________ PEPPERMINT mailing list PEPPERMINT@ietf.org https://www.ietf.org/mailman/listinfo/peppermint From peppermint-bounces@ietf.org Thu Jun 19 08:40:51 2008 Return-Path: X-Original-To: peppermint-archive@optimus.ietf.org Delivered-To: ietfarch-peppermint-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0577E3A6A45; Thu, 19 Jun 2008 08:40:51 -0700 (PDT) X-Original-To: peppermint@core3.amsl.com Delivered-To: peppermint@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DDA0228C0E9 for ; Wed, 18 Jun 2008 10:15:05 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.598 X-Spam-Level: X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 apFSRXa6aTU8 for ; Wed, 18 Jun 2008 10:15:04 -0700 (PDT) Received: from mail201.messagelabs.com (mail201.messagelabs.com [216.82.254.211]) by core3.amsl.com (Postfix) with ESMTP id 96F2F28C1CE for ; Wed, 18 Jun 2008 10:15:04 -0700 (PDT) X-VirusChecked: Checked X-Env-Sender: djaff@csc.com X-Msg-Ref: server-12.tower-201.messagelabs.com!1213808936!5493230!5 X-StarScan-Version: 5.5.12.14.2; banners=-,-,- X-Originating-IP: [20.137.2.88] Received: (qmail 1926 invoked from network); 18 Jun 2008 17:09:00 -0000 Received: from amer-mta102.csc.com (HELO amer-mta102.csc.com) (20.137.2.88) by server-12.tower-201.messagelabs.com with AES256-SHA encrypted SMTP; 18 Jun 2008 17:09:00 -0000 Received: from amer-gw09.amer.csc.com (amer-gw09.amer.csc.com [20.6.39.245]) by amer-mta102.csc.com (Switch-3.3.2mp/Switch-3.3.0) with ESMTP id m5IH95S2004922 for ; Wed, 18 Jun 2008 13:09:10 -0400 To: peppermint@ietf.org MIME-Version: 1.0 X-Mailer: Lotus Notes 652HF83 November 04, 2004 From: Dana Jaff Message-ID: Date: Wed, 18 Jun 2008 13:09:06 -0400 X-MIMETrack: Serialize by Router on AMER-GW09/SRV/CSC(Release 8.0.1|February 07, 2008) at 06/18/2008 01:12:07 PM, Serialize complete at 06/18/2008 01:12:07 PM X-Mailman-Approved-At: Thu, 19 Jun 2008 08:40:49 -0700 Subject: [PEPPERMINT] Subscribe X-BeenThere: peppermint@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Provisioning Extensions in Peering Registries for Multimedia INTerconnection List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1078213233==" Sender: peppermint-bounces@ietf.org Errors-To: peppermint-bounces@ietf.org This is a multipart message in MIME format. --===============1078213233== Content-Type: multipart/alternative; boundary="=_alternative 005D6D868525746C_=" This is a multipart message in MIME format. --=_alternative 005D6D868525746C_= Content-Type: text/plain; charset="US-ASCII" Hi, I am interested in being added to your mailing list and discussions. Please let me know if you need further information. Thanks Dana Jaff GETS/WPS IC Program Computer Sciences Corporation (CSC) Office: 703-818- 4135 Computer Sciences Corporation Registered Office: 3170 Fairview Park Drive, Falls Church, Virginia 22042, USA Registered in Nevada, USA No: C-489-59 ------------------------------------------------------------------------------------------------------------------------------------------------------------------------- This is a PRIVATE message. If you are not the intended recipient, please delete without copying and kindly advise us by e-mail of the mistake in delivery. NOTE: Regardless of content, this e-mail shall not operate to bind CSC to any order or other contract unless pursuant to explicit written agreement or government initiative expressly permitting the use of e-mail for such purpose. ------------------------------------------------------------------------------------------------------------------------------------------------------------------------- --=_alternative 005D6D868525746C_= Content-Type: text/html; charset="US-ASCII"
Hi,

I am interested in being added to your mailing list and discussions. Please let me know if you need further information.

Thanks

Dana Jaff
GETS/WPS IC Program
Computer Sciences Corporation (CSC)
Office: 703-818- 4135

Computer Sciences Corporation
Registered Office: 3170 Fairview Park Drive, Falls Church, Virginia 22042, USA
Registered in Nevada, USA No: C-489-59

-------------------------------------------------------------------------------------------------------------------------------------------------------------------------
This is a PRIVATE message. If you are not the intended recipient, please delete without copying and kindly advise us by e-mail of the mistake in delivery.
NOTE: Regardless of content, this e-mail shall not operate to bind CSC to any order or other contract unless pursuant to explicit written agreement or government initiative expressly permitting the use of e-mail for such purpose.
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------
--=_alternative 005D6D868525746C_=-- --===============1078213233== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ PEPPERMINT mailing list PEPPERMINT@ietf.org https://www.ietf.org/mailman/listinfo/peppermint --===============1078213233==-- From peppermint-bounces@ietf.org Thu Jun 19 09:55:20 2008 Return-Path: X-Original-To: peppermint-archive@optimus.ietf.org Delivered-To: ietfarch-peppermint-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 171583A698E; Thu, 19 Jun 2008 09:55:20 -0700 (PDT) X-Original-To: peppermint@core3.amsl.com Delivered-To: peppermint@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 447BA3A6A4D for ; Thu, 19 Jun 2008 08:43:43 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.826 X-Spam-Level: X-Spam-Status: No, score=-4.826 tagged_above=-999 required=5 tests=[AWL=-0.202, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_EQ_AT=0.424, RCVD_IN_DNSWL_MED=-4, RDNS_NONE=0.1] 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 RbmMpOVZDjAX for ; Thu, 19 Jun 2008 08:43:42 -0700 (PDT) Received: from mail.sbg.nic.at (unknown [192.174.68.200]) by core3.amsl.com (Postfix) with ESMTP id EE11F3A690A for ; Thu, 19 Jun 2008 08:43:41 -0700 (PDT) Received: from localhost [127.0.0.1] by mail.sbg.nic.at with XWall v3.42 ; Thu, 19 Jun 2008 17:44:29 +0200 Content-class: urn:content-classes:message MIME-Version: 1.0 X-MimeOLE: Produced By Microsoft Exchange V6.5 Date: Thu, 19 Jun 2008 17:44:28 +0200 Message-ID: <8BC845943058D844ABFC73D2220D4665076BEC5E@nics-mail.sbg.nic.at> In-Reply-To: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [PEPPERMINT] Subscribe Thread-Index: AcjSIwCcb5e8Dok+TYaHroeSm+2AWwAAEZVA References: From: "Alexander Mayrhofer" To: "Dana Jaff" , X-Mailman-Approved-At: Thu, 19 Jun 2008 09:55:19 -0700 Subject: Re: [PEPPERMINT] Subscribe X-BeenThere: peppermint@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Provisioning Extensions in Peering Registries for Multimedia INTerconnection List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: peppermint-bounces@ietf.org Errors-To: peppermint-bounces@ietf.org > I am interested in being added to your mailing list and > discussions. Please let me know if you need further information. Dana, please see https://www1.ietf.org/mailman/listinfo/peppermint for information how to subscribe to the list. There is also a list archive. thanks, Alex _______________________________________________ PEPPERMINT mailing list PEPPERMINT@ietf.org https://www.ietf.org/mailman/listinfo/peppermint From peppermint-bounces@ietf.org Thu Jun 26 07:35:57 2008 Return-Path: X-Original-To: peppermint-archive@optimus.ietf.org Delivered-To: ietfarch-peppermint-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 70CBA3A6A6D; Thu, 26 Jun 2008 07:35:57 -0700 (PDT) X-Original-To: peppermint@core3.amsl.com Delivered-To: peppermint@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7007C3A691A for ; Thu, 26 Jun 2008 07:35:56 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.28 X-Spam-Level: X-Spam-Status: No, score=0.28 tagged_above=-999 required=5 tests=[AWL=0.743, BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368] 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 is4z2zSlhAOB for ; Thu, 26 Jun 2008 07:35:52 -0700 (PDT) Received: from ondar.cablelabs.com (ondar.cablelabs.com [192.160.73.61]) by core3.amsl.com (Postfix) with ESMTP id A653D3A68C9 for ; Thu, 26 Jun 2008 07:35:52 -0700 (PDT) Received: from kyzyl.cablelabs.com (kyzyl [10.253.0.7]) by ondar.cablelabs.com (8.14.2/8.14.2) with ESMTP id m5QEZoxY014733 for ; Thu, 26 Jun 2008 08:35:55 -0600 Received: from srvxchg3.cablelabs.com (10.5.0.25) by kyzyl.cablelabs.com (F-Secure/fsigk_smtp/511/kyzyl.cablelabs.com); Thu, 26 Jun 2008 08:35:50 -0700 (MST) X-Virus-Status: clean(F-Secure/fsigk_smtp/511/kyzyl.cablelabs.com) X-Mimeole: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Thu, 26 Jun 2008 08:35:00 -0600 Message-ID: <9AAEDF491EF7CA48AB587781B8F5D7C601216A72@srvxchg3.cablelabs.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Data model for "reachability data" and naming/terminology for group of addresses Thread-Index: AcjXmdAKPy4BOYG1TWidIwgmNrLgPg== From: "Jean-Francois Mule" To: X-Approved: ondar Subject: [PEPPERMINT] Data model for "reachability data" and naming/terminology for group of addresses X-BeenThere: peppermint@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Provisioning Extensions in Peering Registries for Multimedia INTerconnection List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: peppermint-bounces@ietf.org Errors-To: peppermint-bounces@ietf.org In draft-mule-peppermint-espp-protocol-01.txt, a data model is proposed Figure 3. Otmar and a number of folks have commented on the list that the 'bottom' part of data model (the grouping of user addresses, PSTN prefixes, or anything that be logically attached to a SIP route/domain) seems to make some sense for some use cases. The upper part is where folks see different solutions. We're updating the draft to integrate comments received from the list and fix a few issues we found. 1) We're changing LRNs (US, PSTN centric to Penn and Otmar's point) to use prefix. David et al. have chosen prefix in their problem statement draft and this describes something that's close to LRNs, yet more generally applicable. 2) We're also renaming "Service Areas" to "AddressGroup" for a lack of a better term Comments welcome. You should also see some responses in the coming weeks on the other threads re: espp comments. Jean-Francois. _______________________________________________ PEPPERMINT mailing list PEPPERMINT@ietf.org https://www.ietf.org/mailman/listinfo/peppermint From peppermint-bounces@ietf.org Thu Jun 26 07:49:00 2008 Return-Path: X-Original-To: peppermint-archive@optimus.ietf.org Delivered-To: ietfarch-peppermint-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3440D3A69C1; Thu, 26 Jun 2008 07:49:00 -0700 (PDT) X-Original-To: peppermint@core3.amsl.com Delivered-To: peppermint@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id ABDE13A69C1 for ; Thu, 26 Jun 2008 07:48:59 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.599 X-Spam-Level: X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 YdLjML9JBV6p for ; Thu, 26 Jun 2008 07:48:58 -0700 (PDT) Received: from mx3.nominet.org.uk (mx3.nominet.org.uk [213.248.199.23]) by core3.amsl.com (Postfix) with ESMTP id 6077128C126 for ; Thu, 26 Jun 2008 07:48:54 -0700 (PDT) DomainKey-Signature: s=main.dk.nominet.selector; d=nominet.org.uk; c=nofws; q=dns; h=X-IronPort-AV:Received:In-Reply-To:References:To:Cc: Subject:MIME-Version:X-Mailer:Message-ID:From:Date: X-MIMETrack:Content-Type; b=A1753dfrTqroZJ/WqptXjYFotiR2i167Z2iiVNeGEVjdaBSpueny1Clq bIImVKwbMRHMYMpwJ71QT6fPSssUILx1LOHztK5Oz1DXzm3NSDXaDSigR zqA07gDKH11LjYN; DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nominet.org.uk; i=Ray.Bellis@nominet.org.uk; q=dns/txt; s=main.dkim.nominet.selector; t=1214491739; x=1246027739; h=from:sender:reply-to:subject:date:message-id:to:cc: mime-version:content-transfer-encoding:content-id: content-description:resent-date:resent-from:resent-sender: resent-to:resent-cc:resent-message-id:in-reply-to: references:list-id:list-help:list-unsubscribe: list-subscribe:list-post:list-owner:list-archive; z=From:=20Ray.Bellis@nominet.org.uk|Subject:=20Re:=20[PEPP ERMINT]=20Data=20model=20for=20"reachability=20data"=20an d=09naming/terminology=0D=0A=20for=20group=20of=20address es|Date:=20Thu,=2026=20Jun=202008=2015:48:55=20+0100 |Message-ID:=20|To:=20"Jean-Francois=20M ule"=20|Cc:=20peppermint@ietf.org |MIME-Version:=201.0|In-Reply-To:=20<9AAEDF491EF7CA48AB58 7781B8F5D7C601216A72@srvxchg3.cablelabs.com>|References: =20<9AAEDF491EF7CA48AB587781B8F5D7C601216A72@srvxchg3.cab lelabs.com>; bh=fKYOGVCCmng2NlxGh76aDeQi2eBHWqKoSVhJOGvKOgA=; b=Zp8x0sKOH0gUVWcwBjXZnd3ie/HxYMEtr8UvWo1tx/qwkvBKigwt/7JB sIWG4KrkdUC47dNxhkVHeMgWCZMBeq1wTvMGfH84q8MtaMSZpWorJuQMS 4FSExvlVYMxzaxm; X-IronPort-AV: E=Sophos;i="4.27,708,1204502400"; d="scan'208";a="3853642" Received: from notes1.nominet.org.uk ([213.248.197.128]) by mx3.nominet.org.uk with ESMTP; 26 Jun 2008 15:48:57 +0100 In-Reply-To: <9AAEDF491EF7CA48AB587781B8F5D7C601216A72@srvxchg3.cablelabs.com> References: <9AAEDF491EF7CA48AB587781B8F5D7C601216A72@srvxchg3.cablelabs.com> To: "Jean-Francois Mule" MIME-Version: 1.0 X-Mailer: Lotus Notes Build VMac_Beta85_20080115_MM2 January 15, 2008 Message-ID: From: Ray.Bellis@nominet.org.uk Date: Thu, 26 Jun 2008 15:48:55 +0100 X-MIMETrack: Serialize by Router on notes1/Nominet(Release 7.0.1FP1 | May 25, 2006) at 26/06/2008 03:48:56 PM, Serialize complete at 26/06/2008 03:48:56 PM Cc: peppermint@ietf.org Subject: Re: [PEPPERMINT] Data model for "reachability data" and naming/terminology for group of addresses X-BeenThere: peppermint@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Provisioning Extensions in Peering Registries for Multimedia INTerconnection List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: peppermint-bounces@ietf.org Errors-To: peppermint-bounces@ietf.org > We're updating the draft to integrate comments received from the list > and fix a few issues we found. > 1) We're changing LRNs (US, PSTN centric to Penn and Otmar's point) to > use prefix. > David et al. have chosen prefix in their problem statement draft and > this describes something that's close to LRNs, yet more generally > applicable. > 2) We're also renaming "Service Areas" to "AddressGroup" for a lack of a > better term Jean-Francois, Can you elaborate on what a "Service Area" / "Address Group" actually is? In the UK for our Central Numbering Database we've developed a concept of a "Destination Group" - that being all those numbers (or destinations) which are supposed to be routed identically. Is that the same thing? Note however that this does not mean that every originating carrier has to route them to the same place as every other carrier. For example if Carrier A (a terminating carrier) has: DG1 = (a, b) DG2 = (c, d) then originating Carrier B routes destinations in DG1 to a particular interconnect, and routes DG2 to some other interconnect. However Carrier C might have completely different interconnects with Carrier A. In the UK model the actual interconnect addresses are private information bilaterally agreed between carriers. kind regards, Ray _______________________________________________ PEPPERMINT mailing list PEPPERMINT@ietf.org https://www.ietf.org/mailman/listinfo/peppermint From peppermint-bounces@ietf.org Mon Jun 30 00:50:39 2008 Return-Path: X-Original-To: peppermint-archive@optimus.ietf.org Delivered-To: ietfarch-peppermint-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 16A613A6AA8; Mon, 30 Jun 2008 00:50:39 -0700 (PDT) X-Original-To: peppermint@core3.amsl.com Delivered-To: peppermint@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E0A3328C116 for ; Mon, 30 Jun 2008 00:50:37 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.098 X-Spam-Level: X-Spam-Status: No, score=-4.098 tagged_above=-999 required=5 tests=[AWL=0.526, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_EQ_AT=0.424, RCVD_IN_DNSWL_MED=-4, RDNS_NONE=0.1] 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 YAWU-e8mpORE for ; Mon, 30 Jun 2008 00:50:37 -0700 (PDT) Received: from mail.sbg.nic.at (unknown [192.174.68.200]) by core3.amsl.com (Postfix) with ESMTP id A35F03A6AA5 for ; Mon, 30 Jun 2008 00:50:33 -0700 (PDT) Received: from localhost [127.0.0.1] by mail.sbg.nic.at with XWall v3.42 ; Mon, 30 Jun 2008 09:50:44 +0200 Content-class: urn:content-classes:message MIME-Version: 1.0 X-MimeOLE: Produced By Microsoft Exchange V6.5 Date: Mon, 30 Jun 2008 09:50:41 +0200 Message-ID: <8BC845943058D844ABFC73D2220D4665076BF045@nics-mail.sbg.nic.at> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: test - please ignore... Thread-Index: Acjahf6NnnxqaX/1TO6y7LM/hlCYNw== From: "Alexander Mayrhofer" To: Subject: [PEPPERMINT] test - please ignore... X-BeenThere: peppermint@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Provisioning Extensions in Peering Registries for Multimedia INTerconnection List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: peppermint-bounces@ietf.org Errors-To: peppermint-bounces@ietf.org another test after the list migration. alex _______________________________________________ PEPPERMINT mailing list PEPPERMINT@ietf.org https://www.ietf.org/mailman/listinfo/peppermint From peppermint-bounces@ietf.org Mon Jun 30 12:08:19 2008 Return-Path: X-Original-To: peppermint-archive@optimus.ietf.org Delivered-To: ietfarch-peppermint-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 62F553A6932; Mon, 30 Jun 2008 12:08:19 -0700 (PDT) X-Original-To: peppermint@core3.amsl.com Delivered-To: peppermint@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A4BDF3A6932; Mon, 30 Jun 2008 12:08:17 -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 FliUulUV7W3y; Mon, 30 Jun 2008 12:08:16 -0700 (PDT) Received: from ogud.com (hlid.ogud.com [66.92.146.160]) by core3.amsl.com (Postfix) with ESMTP id 849433A6903; Mon, 30 Jun 2008 12:08:16 -0700 (PDT) Received: from [10.31.200.209] (mail.md.ogud.com [10.20.30.6]) by ogud.com (8.13.1/8.13.1) with ESMTP id m5UJ8IeI068941; Mon, 30 Jun 2008 15:08:19 -0400 (EDT) (envelope-from Ed.Lewis@neustar.biz) Mime-Version: 1.0 Message-Id: Date: Mon, 30 Jun 2008 15:08:15 -0400 To: peppermint@ietf.org, drinks@ietf.org From: Edward Lewis X-Scanned-By: MIMEDefang 2.63 on 10.20.30.6 Subject: [PEPPERMINT] Comparison of Requirements Documents X-BeenThere: peppermint@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Provisioning Extensions in Peering Registries for Multimedia INTerconnection List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: peppermint-bounces@ietf.org Errors-To: peppermint-bounces@ietf.org I've been taking a look at two requirements documents, the ESPP Requirements and the Consolidated Provisioning Statement. I realize (or have been told) that a new set of ESPP documents is coming out, so I'll avoid getting into specifics. The goal is to have a "Unified" (we've already used "Consolidated") requirements document for the WG. BTW, the documents I'm comparing are these: http://tools.ietf.org/html/draft-mule-peppermint-espp-requirements-00 http://tools.ietf.org/html/draft-schwartz-peppermint-consolidated-provisioning-problem-statement-00 This comparison list is not very detailed, I wanted to identify the topics that included in both and where the two requirements had different emphasis. I don't think there is any outright contradiction between the two. Both documents describe a protocol running over SOAP/XML, WDSL, TLS and HTTP and being easily integrated into the current provisioning systems. Both recognize that there a telephone number (E164) to URI mapping happening, with NAPTR as a major vehicle (but not sole vehicle). Both mention a need to make the transactions auditable, including logs. Consolidated mentions multiple kinds of sources of data, ESPP refers to multiple clients. This could be interpreted as an equivalent statement. ESPP explicitly states that operation is based on files (as opposed to records). (I'd question the file name requirements based on this, as well as a hard coded limit on the size limit.) ESPP describes designing an efficient protocol, i.e., being able to apply one set of data to many numbers. (But when I boiled the requirements down, I didn't see this idea - maybe it was in the protocol.) ESPP has a specific data model in mind (which is being discussed in recent mail), and a capacity of the order of the size of the PSTN number range(s). ESPP includes some protocol maintenance stuff (versioning numbers). Consolidated has requirements on the database being addressable (any element). Consolidated explicitly includes prefixs (for ranges) and min/max lengths. Consolidated explicitly mentions numbers being reassigned and the impact of that on database entries and responses. Consolidated requires dip indications, temporal validity, number "ownership" and other ancillary data. Consolidated requires a catchall record, a \1 shorthand. Consolidated has requirements on the transport as being end-to-end only (no caching) and having flow control. It's obvious that the two teams that developed the documents had different emphasis on what to include in a list or requirements. Even with the ESPP requirements document being rather mature (as well as being accompanied by a protocol specification), there is a need to combine the two documents. I don't believe that the result will be radically different from either, just more complete. -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Edward Lewis +1-571-434-5468 NeuStar Never confuse activity with progress. Activity pays more. -- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Edward Lewis +1-571-434-5468 NeuStar Never confuse activity with progress. Activity pays more. _______________________________________________ PEPPERMINT mailing list PEPPERMINT@ietf.org https://www.ietf.org/mailman/listinfo/peppermint