
From D.Malas@cablelabs.com  Thu Jan  7 08:55:34 2010
Return-Path: <D.Malas@cablelabs.com>
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 04E3C3A6809 for <speermint@core3.amsl.com>; Thu,  7 Jan 2010 08:55:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.463
X-Spam-Level: 
X-Spam-Status: No, score=-0.463 tagged_above=-999 required=5 tests=[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 OqcrHqUoj-mO for <speermint@core3.amsl.com>; Thu,  7 Jan 2010 08:55:33 -0800 (PST)
Received: from ondar.cablelabs.com (ondar.cablelabs.com [192.160.73.61]) by core3.amsl.com (Postfix) with ESMTP id 359993A63C9 for <speermint@ietf.org>; Thu,  7 Jan 2010 08:55:33 -0800 (PST)
Received: from kyzyl.cablelabs.com (kyzyl [10.253.0.7]) by ondar.cablelabs.com (8.14.3/8.14.3) with SMTP id o07GtPwo028499; Thu, 7 Jan 2010 09:55:26 -0700
Received: from srvxchg3.cablelabs.com (10.5.0.25) by kyzyl.cablelabs.com (F-Secure/fsigk_smtp/303/kyzyl.cablelabs.com); Thu, 7 Jan 2010 09:55:26 -0700 (MST)
X-Virus-Status: clean(F-Secure/fsigk_smtp/303/kyzyl.cablelabs.com)
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: Thu, 7 Jan 2010 09:55:26 -0700
Message-ID: <160DE07A1C4F8E4AA2715DEC577DA4910119108D@srvxchg3.cablelabs.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Speermint] **Last Call** on the Speermint Peering Architecture draft
Thread-Index: AcqPujZ1COYZ76qwS0GixqlM0TUH4A==
From: "Daryl Malas" <D.Malas@cablelabs.com>
To: <speermint@ietf.org>
X-Approved: ondar
Subject: [Speermint] **Last Call** on the Speermint Peering Architecture draft
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: Thu, 07 Jan 2010 16:55:34 -0000

All,
=20
We discussed this during our last meeting, but I wanted to officially
note it on the mailing list.  Please provide any final comments on the
Speermint Peering Architecture draft.  This last call will last
approximately 1 week and end on January 15th.

Here is a link to the draft:
http://tools.ietf.org/html/draft-ietf-speermint-architecture-09

Adam,

Please review and begin correction of the nits here:
http://tools.ietf.org/idnits?url=3Dhttp://tools.ietf.org/id/draft-ietf-sp=
e
ermint-architecture-09.txt.

We would like to wrap up this draft quickly, so everyone's effort to
review and provide and final feedback is greatly appreciated.

Regards,

Daryl

From D.Malas@cablelabs.com  Fri Jan  8 08:47:24 2010
Return-Path: <D.Malas@cablelabs.com>
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 EB7BC3A677C for <speermint@core3.amsl.com>; Fri,  8 Jan 2010 08:47:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.837
X-Spam-Level: 
X-Spam-Status: No, score=0.837 tagged_above=-999 required=5 tests=[AWL=-1.300,  BAYES_50=0.001, 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 72-rnQKD+asr for <speermint@core3.amsl.com>; Fri,  8 Jan 2010 08:47:24 -0800 (PST)
Received: from ondar.cablelabs.com (ondar.cablelabs.com [192.160.73.61]) by core3.amsl.com (Postfix) with ESMTP id 1CAB83A6810 for <speermint@ietf.org>; Fri,  8 Jan 2010 08:47:24 -0800 (PST)
Received: from kyzyl.cablelabs.com (kyzyl [10.253.0.7]) by ondar.cablelabs.com (8.14.3/8.14.3) with SMTP id o08GlLSI018488 for <speermint@ietf.org>; Fri, 8 Jan 2010 09:47:21 -0700
Received: from srvxchg3.cablelabs.com (10.5.0.25) by kyzyl.cablelabs.com (F-Secure/fsigk_smtp/303/kyzyl.cablelabs.com); Fri, 8 Jan 2010 09:47:21 -0700 (MST)
X-Virus-Status: clean(F-Secure/fsigk_smtp/303/kyzyl.cablelabs.com)
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: Fri, 8 Jan 2010 09:47:22 -0700
Message-ID: <160DE07A1C4F8E4AA2715DEC577DA491011910AC@srvxchg3.cablelabs.com>
In-Reply-To: <160DE07A1C4F8E4AA2715DEC577DA4910119108D@srvxchg3.cablelabs.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Speermint] RE:**Last Call** on the Speermint Peering Architecture draft
Thread-Index: AcqPujZ1COYZ76qwS0GixqlM0TUH4AAx8lVA
References: <160DE07A1C4F8E4AA2715DEC577DA4910119108D@srvxchg3.cablelabs.com>
From: "Daryl Malas" <D.Malas@cablelabs.com>
To: <speermint@ietf.org>
X-Approved: ondar
Subject: [Speermint] RE:**Last Call** on the Speermint Peering Architecture draft
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: Fri, 08 Jan 2010 16:47:25 -0000

All,

With the understanding it may be challenging for some to schedule the
time to review and provide comments in 1 week, the "Last Call" is
extended to January 22nd.

Regards,

Daryl

-----Original Message-----
From: speermint-bounces@ietf.org [mailto:speermint-bounces@ietf.org] On
Behalf Of Daryl Malas
Sent: Thursday, January 07, 2010 9:55 AM
To: speermint@ietf.org
Subject: [Speermint] **Last Call** on the Speermint Peering
Architecturedraft

All,
=20
We discussed this during our last meeting, but I wanted to officially
note it on the mailing list.  Please provide any final comments on the
Speermint Peering Architecture draft.  This last call will last
approximately 1 week and end on January 15th.

Here is a link to the draft:
http://tools.ietf.org/html/draft-ietf-speermint-architecture-09

Adam,

Please review and begin correction of the nits here:
http://tools.ietf.org/idnits?url=3Dhttp://tools.ietf.org/id/draft-ietf-sp=
e
ermint-architecture-09.txt.

We would like to wrap up this draft quickly, so everyone's effort to
review and provide and final feedback is greatly appreciated.

Regards,

Daryl
_______________________________________________
Speermint mailing list
Speermint@ietf.org
https://www.ietf.org/mailman/listinfo/speermint

From rjsparks@nostrum.com  Fri Jan 15 14:06:17 2010
Return-Path: <rjsparks@nostrum.com>
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 BF8D23A6857 for <speermint@core3.amsl.com>; Fri, 15 Jan 2010 14:06:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.584
X-Spam-Level: 
X-Spam-Status: No, score=-2.584 tagged_above=-999 required=5 tests=[AWL=0.016,  BAYES_00=-2.599, SPF_PASS=-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 cKPJr7Xpn8lc for <speermint@core3.amsl.com>; Fri, 15 Jan 2010 14:06:16 -0800 (PST)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by core3.amsl.com (Postfix) with ESMTP id 5211C3A67FC for <speermint@ietf.org>; Fri, 15 Jan 2010 14:06:16 -0800 (PST)
Received: from [192.168.2.2] (pool-173-71-49-137.dllstx.fios.verizon.net [173.71.49.137]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id o0FM62g9059674 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 15 Jan 2010 16:06:02 -0600 (CST) (envelope-from rjsparks@nostrum.com)
Message-Id: <5F47E451-1635-49B2-8097-64DA24C3AD55@nostrum.com>
From: Robert Sparks <rjsparks@nostrum.com>
To: "Lee, Yiu" <Yiu_Lee@Cable.Comcast.com>
In-Reply-To: <C73D7213.1524A%yiu_lee@cable.comcast.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v936)
Date: Fri, 15 Jan 2010 16:06:01 -0600
References: <C73D7213.1524A%yiu_lee@cable.comcast.com>
X-Mailer: Apple Mail (2.936)
Received-SPF: pass (nostrum.com: 173.71.49.137 is authenticated by a trusted mechanism)
Cc: speermint@ietf.org
Subject: Re: [Speermint] I-D Action:draft-ietf-speermint-voip-consolidated-usecases-15.txt
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: Fri, 15 Jan 2010 22:06:17 -0000

Hi Yiu -

I only have one sticking point remaining. In interest in closing on it  
more quickly,
I'll propose text.

--------
OLD:

9.   T-SBE receives the NAPTR record and query DNS for the A record
         of domain "t-proxy.example.net.".  The DNS returns an A record:

           ;; DNS ANSWER
           t-proxy.example.net.   IN A   192.0.2.2

         Note that in this example the T-SBE receives an A record when
         querying "t-proxy.example.net".  But T-SBE should also prepare
         to receive a SRV record and follow the procedures defined in
         [RFC3263] to locate the next-hop.

NEW:

9.   T-SBE receives the NAPTR record and following the requirements
        in [RFC3263] queries DNS for the SRV records indicated by the
        NAPTR result. Not finding any, the T-SBE then queries DNS for
        the A record of domain "t-proxy.example.net.".
        The DNS returns an A record:

           ;; DNS ANSWER
           t-proxy.example.net.   IN A   192.0.2.2

-----------

If this works for the group, I can clear. We can probably handle this  
with
an RFC-Editor note instead of revising the document if you don't have
anything else to change.

RjS

On Dec 3, 2009, at 12:48 PM, Lee, Yiu wrote:

> This revision tries to address the comments from the AD reviews.  
> Please take
> time to review it.
>
> Thanks.
>
>
> On 12/3/09 1:45 PM, "Internet-Drafts@ietf.org" <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 Session PEERing for Multimedia  
>> INTerconnect
>> Working Group of the IETF.
>>
>>
>> Title           : VoIP SIP Peering Use Cases
>> Author(s)       : A. Uzelac, Y. Lee
>> Filename        : draft-ietf-speermint-voip-consolidated- 
>> usecases-15.txt
>> Pages           : 25
>> Date            : 2009-12-03
>>
>> This document depicts many common Voice over IP (VoIP) use cases for
>> Session Initiation Protocol (SIP) Peering.  These use cases are
>> categorized into static and on-demand, and then further sub-
>> categorized into direct and indirect.  These use cases are not an
>> exhaustive set, but rather the most common use cases deployed today.
>>
>> Status of this Memo
>>
>> This Internet-Draft is submitted to IETF in full conformance with the
>> provisions of BCP 78 and BCP 79.
>>
>> Internet-Drafts are working documents of the Internet Engineering
>> Task Force (IETF), its areas, and its working groups.  Note that
>> other groups may also distribute working documents as Internet-
>> Drafts.
>>
>> Internet-Drafts are draft documents valid for a maximum of six months
>> and may be updated, replaced, or obsoleted by other documents at any
>> time.  It is inappropriate to use Internet-Drafts as reference
>> material or to cite them other than as "work in progress."
>>
>> The list of current Internet-Drafts can be accessed at
>> http://www.ietf.org/ietf/1id-abstracts.txt.
>>
>> The list of Internet-Draft Shadow Directories can be accessed at
>> http://www.ietf.org/shadow.html.
>>
>> This Internet-Draft will expire on June 6, 2010.
>>
>> Copyright Notice
>>
>> Copyright (c) 2009 IETF Trust and the persons identified as the
>> document authors.  All rights reserved.
>>
>> This document is subject to BCP 78 and the IETF Trust's Legal
>> Provisions Relating to IETF Documents
>> (http://trustee.ietf.org/license-info) in effect on the date of
>> publication of this document.  Please review these documents
>> carefully, as they describe your rights and restrictions with respect
>> to this document.  Code Components extracted from this document must
>> include Simplified BSD License text as described in Section 4.e of
>> the Trust Legal Provisions and are provided without warranty as
>> described in the BSD License.
>>
>> A URL for this Internet-Draft is:
>> http://www.ietf.org/internet-drafts/draft-ietf-speermint-voip-consolidated-use
>> cases-15.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.
>> _______________________________________________
>> Speermint mailing list
>> Speermint@ietf.org
>> https://www.ietf.org/mailman/listinfo/speermint
> _______________________________________________
> Speermint mailing list
> Speermint@ietf.org
> https://www.ietf.org/mailman/listinfo/speermint


From yiu_lee@cable.comcast.com  Fri Jan 15 19:43:51 2010
Return-Path: <yiu_lee@cable.comcast.com>
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 AEDAE3A67CF for <speermint@core3.amsl.com>; Fri, 15 Jan 2010 19:43:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.604
X-Spam-Level: *
X-Spam-Status: No, score=1.604 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368, RCVD_NUMERIC_HELO=2.067]
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 D24Nv-wYMcN3 for <speermint@core3.amsl.com>; Fri, 15 Jan 2010 19:43:50 -0800 (PST)
Received: from paoakoavas10.cable.comcast.com (paoakoavas10.cable.comcast.com [208.17.35.59]) by core3.amsl.com (Postfix) with ESMTP id 8A9403A67FE for <speermint@ietf.org>; Fri, 15 Jan 2010 19:43:50 -0800 (PST)
Received: from ([10.52.116.31]) by paoakoavas10.cable.comcast.com with ESMTP  id KP-TDCH7.76304128; Fri, 15 Jan 2010 22:43:32 -0500
Received: from PACDCEXCMB04.cable.comcast.com ([24.40.15.86]) by PAOAKEXCSMTP02.cable.comcast.com with Microsoft SMTPSVC(6.0.3790.3959); Fri, 15 Jan 2010 22:43:32 -0500
x-mimeole: Produced By Microsoft Exchange V6.5
Received: from 72.79.68.108 ([72.79.68.108]) by PACDCEXCMB04.cable.comcast.com ([24.40.15.86]) via Exchange Front-End Server webmail.comcast.com ([24.40.8.153]) with Microsoft Exchange Server HTTP-DAV ; Sat, 16 Jan 2010 03:43:31 +0000
MIME-Version: 1.0
Content-class: urn:content-classes:message
Content-Type: multipart/signed; boundary="B_3346440208_6177358"; protocol="application/pkcs7-signature"; micalg=sha1
Date: Fri, 15 Jan 2010 22:43:28 -0500
Message-ID: <C776A010.1BA42%yiu_lee@cable.comcast.com>
In-Reply-To: <5F47E451-1635-49B2-8097-64DA24C3AD55@nostrum.com>
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
Thread-Topic: [Speermint] I-D Action:draft-ietf-speermint-voip-consolidated-usecases-15.txt
Thread-Index: AcqWXhBqmKuBT8wpmEimcCpRrcfX0g==
From: "Lee, Yiu" <Yiu_Lee@Cable.Comcast.com>
To: "Robert Sparks" <rjsparks@nostrum.com>
X-OriginalArrivalTime: 16 Jan 2010 03:43:32.0427 (UTC) FILETIME=[130E31B0:01CA965E]
Cc: speermint@ietf.org
Subject: Re: [Speermint] I-D Action:draft-ietf-speermint-voip-consolidated-usecases-15.txt
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: Sat, 16 Jan 2010 03:43:51 -0000

> This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

--B_3346440208_6177358
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit

Hi Robert,

I have no problem for it and I will modify the draft with your text if I
hear no objection from the mailing list.

Thanks,
Yiu


On 1/15/10 5:06 PM, "Robert Sparks" <rjsparks@nostrum.com> wrote:

> Hi Yiu -
> 
> I only have one sticking point remaining. In interest in closing on it
> more quickly,
> I'll propose text.
> 
> --------
> OLD:
> 
> 9.   T-SBE receives the NAPTR record and query DNS for the A record
>          of domain "t-proxy.example.net.".  The DNS returns an A record:
> 
>            ;; DNS ANSWER
>            t-proxy.example.net.   IN A   192.0.2.2
> 
>          Note that in this example the T-SBE receives an A record when
>          querying "t-proxy.example.net".  But T-SBE should also prepare
>          to receive a SRV record and follow the procedures defined in
>          [RFC3263] to locate the next-hop.
> 
> NEW:
> 
> 9.   T-SBE receives the NAPTR record and following the requirements
>         in [RFC3263] queries DNS for the SRV records indicated by the
>         NAPTR result. Not finding any, the T-SBE then queries DNS for
>         the A record of domain "t-proxy.example.net.".
>         The DNS returns an A record:
> 
>            ;; DNS ANSWER
>            t-proxy.example.net.   IN A   192.0.2.2
> 
> -----------
> 
> If this works for the group, I can clear. We can probably handle this
> with
> an RFC-Editor note instead of revising the document if you don't have
> anything else to change.
> 
> RjS
> 
> On Dec 3, 2009, at 12:48 PM, Lee, Yiu wrote:
> 
>> This revision tries to address the comments from the AD reviews.
>> Please take
>> time to review it.
>> 
>> Thanks.
>> 
>> 
>> On 12/3/09 1:45 PM, "Internet-Drafts@ietf.org" <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 Session PEERing for Multimedia
>>> INTerconnect
>>> Working Group of the IETF.
>>> 
>>> 
>>> Title           : VoIP SIP Peering Use Cases
>>> Author(s)       : A. Uzelac, Y. Lee
>>> Filename        : draft-ietf-speermint-voip-consolidated-
>>> usecases-15.txt
>>> Pages           : 25
>>> Date            : 2009-12-03
>>> 
>>> This document depicts many common Voice over IP (VoIP) use cases for
>>> Session Initiation Protocol (SIP) Peering.  These use cases are
>>> categorized into static and on-demand, and then further sub-
>>> categorized into direct and indirect.  These use cases are not an
>>> exhaustive set, but rather the most common use cases deployed today.
>>> 
>>> Status of this Memo
>>> 
>>> This Internet-Draft is submitted to IETF in full conformance with the
>>> provisions of BCP 78 and BCP 79.
>>> 
>>> Internet-Drafts are working documents of the Internet Engineering
>>> Task Force (IETF), its areas, and its working groups.  Note that
>>> other groups may also distribute working documents as Internet-
>>> Drafts.
>>> 
>>> Internet-Drafts are draft documents valid for a maximum of six months
>>> and may be updated, replaced, or obsoleted by other documents at any
>>> time.  It is inappropriate to use Internet-Drafts as reference
>>> material or to cite them other than as "work in progress."
>>> 
>>> The list of current Internet-Drafts can be accessed at
>>> http://www.ietf.org/ietf/1id-abstracts.txt.
>>> 
>>> The list of Internet-Draft Shadow Directories can be accessed at
>>> http://www.ietf.org/shadow.html.
>>> 
>>> This Internet-Draft will expire on June 6, 2010.
>>> 
>>> Copyright Notice
>>> 
>>> Copyright (c) 2009 IETF Trust and the persons identified as the
>>> document authors.  All rights reserved.
>>> 
>>> This document is subject to BCP 78 and the IETF Trust's Legal
>>> Provisions Relating to IETF Documents
>>> (http://trustee.ietf.org/license-info) in effect on the date of
>>> publication of this document.  Please review these documents
>>> carefully, as they describe your rights and restrictions with respect
>>> to this document.  Code Components extracted from this document must
>>> include Simplified BSD License text as described in Section 4.e of
>>> the Trust Legal Provisions and are provided without warranty as
>>> described in the BSD License.
>>> 
>>> A URL for this Internet-Draft is:
>>> http://www.ietf.org/internet-drafts/draft-ietf-speermint-voip-consolidated-u
>>> se
>>> cases-15.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.
>>> _______________________________________________
>>> Speermint mailing list
>>> Speermint@ietf.org
>>> https://www.ietf.org/mailman/listinfo/speermint
>> _______________________________________________
>> Speermint mailing list
>> Speermint@ietf.org
>> https://www.ietf.org/mailman/listinfo/speermint
> 

--B_3346440208_6177358
Content-type: application/pkcs7-signature; name="smime.p7s"
Content-transfer-encoding: base64
Content-disposition: attachment;
	filename="smime.p7s"

MIIN2AYJKoZIhvcNAQcCoIINyTCCDcUCAQExCzAJBgUrDgMCGgUAMAsGCSqGSIb3DQEHAaCC
C6QwggMPMIICeKADAgECAhBQgSObXgIsEiVC/GebCmGTMA0GCSqGSIb3DQEBBQUAMGIxCzAJ
BgNVBAYTAlpBMSUwIwYDVQQKExxUaGF3dGUgQ29uc3VsdGluZyAoUHR5KSBMdGQuMSwwKgYD
VQQDEyNUaGF3dGUgUGVyc29uYWwgRnJlZW1haWwgSXNzdWluZyBDQTAeFw0wOTA4MDgwODQw
MDJaFw0xMDA4MDgwODQwMDJaMEsxHzAdBgNVBAMTFlRoYXd0ZSBGcmVlbWFpbCBNZW1iZXIx
KDAmBgkqhkiG9w0BCQEWGXlpdV9sZWVAY2FibGUuY29tY2FzdC5jb20wggEiMA0GCSqGSIb3
DQEBAQUAA4IBDwAwggEKAoIBAQCscC6PT5lvsXUq4lOfCGh5DV7ZnHkaKTZrdclNBGwIUu1H
njC0937hsVMKSuyKXMiuGc2VS1sjvEzqtqcSiGBkX2ZhGszLppMjiNwb3McBc4slgNxK1OfX
Q+g/C/Fi/pZbg3KU/V50QGQQsM0yO1HOK7FGyvOH023fNvQ7E0syH6NAbkmf4mQoHLFUMkjD
mfdbtrnYeGvNjrX6hLMmUuo0Y6MAyJQdBDH8p+6V0/hjvYOA2yAW+ptxxEbPYGrm1/f2TYp2
o43bA9ri/P8Rtli6kaKQvC5HhReyNJLWWG2z8JjbqcQd1sP443WI1voiBbqOLNpu3KWnBRzC
3+n6eYhfAgMBAAGjWTBXMA4GA1UdDwEB/wQEAwID+DARBglghkgBhvhCAQEEBAMCBaAwJAYD
VR0RBB0wG4EZeWl1X2xlZUBjYWJsZS5jb21jYXN0LmNvbTAMBgNVHRMBAf8EAjAAMA0GCSqG
SIb3DQEBBQUAA4GBAF+NiG7zCDaZsRKq54bnGbGi1nFyzFa4sL72O+J2vRZoyVU8tFpl9Xz/
BnTMU+olVJ+Q4wmnwuSJZ6rTblLTlKRVnkd3PBcnWYYVYSvwhKuTTmTX99RZHvGSTGJomy7M
PuOLo/XqZgHgA/oZ38QQp76e9EPeM2nfFJHc9bTK0RlOMIIDPzCCAqigAwIBAgIBDTANBgkq
hkiG9w0BAQUFADCB0TELMAkGA1UEBhMCWkExFTATBgNVBAgTDFdlc3Rlcm4gQ2FwZTESMBAG
A1UEBxMJQ2FwZSBUb3duMRowGAYDVQQKExFUaGF3dGUgQ29uc3VsdGluZzEoMCYGA1UECxMf
Q2VydGlmaWNhdGlvbiBTZXJ2aWNlcyBEaXZpc2lvbjEkMCIGA1UEAxMbVGhhd3RlIFBlcnNv
bmFsIEZyZWVtYWlsIENBMSswKQYJKoZIhvcNAQkBFhxwZXJzb25hbC1mcmVlbWFpbEB0aGF3
dGUuY29tMB4XDTAzMDcxNzAwMDAwMFoXDTEzMDcxNjIzNTk1OVowYjELMAkGA1UEBhMCWkEx
JTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0
ZSBQZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBMIGfMA0GCSqGSIb3DQEBAQUAA4GNADCB
iQKBgQDEpjxVc1X7TrnKmVoeaMB1BHCd3+n/ox7svc31W/Iadr1/DDph8r9RzgHU5VAKMNcC
Y1osiRVwjt3J8CuFWqo/cVbLrzwLB+fxH5E2JCoTzyvV84J3PQO+K/67GD4Hv0CAAmTXp6a7
n2XRxSpUhQ9IBH+nttE8YQRAHmQZcmC3+wIDAQABo4GUMIGRMBIGA1UdEwEB/wQIMAYBAf8C
AQAwQwYDVR0fBDwwOjA4oDagNIYyaHR0cDovL2NybC50aGF3dGUuY29tL1RoYXd0ZVBlcnNv
bmFsRnJlZW1haWxDQS5jcmwwCwYDVR0PBAQDAgEGMCkGA1UdEQQiMCCkHjAcMRowGAYDVQQD
ExFQcml2YXRlTGFiZWwyLTEzODANBgkqhkiG9w0BAQUFAAOBgQBIjNFQg+oLLswNo2asZw9/
r6y+whehQ5aUnX9MIbj4Nh+qLZ82L8D0HFAgk3A8/a3hYWLD2ToZfoSxmRsAxRoLgnSeJVCU
YsfbJ3FXJY3dqZw5jowgT2Vfldr394fWxghOrvbqNOUQGls1TXfjViF4gtwhGTXeJLHTHUb/
XV9lTzCCBUowggQyoAMCAQICEEsVRXwTaRSoi7d3sapu92EwDQYJKoZIhvcNAQEFBQAwgd0x
CzAJBgNVBAYTAlVTMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNp
Z24gVHJ1c3QgTmV0d29yazE7MDkGA1UECxMyVGVybXMgb2YgdXNlIGF0IGh0dHBzOi8vd3d3
LnZlcmlzaWduLmNvbS9ycGEgKGMpMDUxHjAcBgNVBAsTFVBlcnNvbmEgTm90IFZhbGlkYXRl
ZDE3MDUGA1UEAxMuVmVyaVNpZ24gQ2xhc3MgMSBJbmRpdmlkdWFsIFN1YnNjcmliZXIgQ0Eg
LSBHMjAeFw0wOTExMDUwMDAwMDBaFw0xMDExMDUyMzU5NTlaMIIBEzEXMBUGA1UEChMOVmVy
aVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlTaWduIFRydXN0IE5ldHdvcmsxRjBEBgNVBAsT
PXd3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9yeS9SUEEgSW5jb3JwLiBieSBSZWYuLExJQUIu
TFREKGMpOTgxHjAcBgNVBAsTFVBlcnNvbmEgTm90IFZhbGlkYXRlZDEzMDEGA1UECxMqRGln
aXRhbCBJRCBDbGFzcyAxIC0gTmV0c2NhcGUgRnVsbCBTZXJ2aWNlMRAwDgYDVQQDFAdZaXUg
TGVlMSgwJgYJKoZIhvcNAQkBFhl5aXVfbGVlQGNhYmxlLmNvbWNhc3QuY29tMIIBIjANBgkq
hkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEArfUYyB1WddeTV1whaQNaHKstvQcFnloN37ZayFeM
H8D3vKzrImHg6WIFOm7+kA5GsW+cO5au9HNL5fKSf1jYb4/EMuaEITqBpBK41nBok7jP3FiD
KPt4TtsJsnqDRLaS2SS3YBSTZOzgdLU4mTjveMYmyFdeRbNsrO2v8bWkcQLE/zf5wSdGS6rF
nDF8MXw70BkHmZte1eY+EYoi694+0ukeg9eKw5JFlmBrYAoE1oDxMHXXIV2ju/zC9kpK5DZC
AVtofp+hL5A+pgnLxOsfPrRpcrkQeM1ryhujXCij/jdHMMdNS3+z97QSw8cNfG3PBF8KnBp6
67jVylTR/d3LCwIDAQABo4HMMIHJMAkGA1UdEwQCMAAwRAYDVR0gBD0wOzA5BgtghkgBhvhF
AQcXATAqMCgGCCsGAQUFBwIBFhxodHRwczovL3d3dy52ZXJpc2lnbi5jb20vcnBhMAsGA1Ud
DwQEAwIFoDAdBgNVHSUEFjAUBggrBgEFBQcDBAYIKwYBBQUHAwIwSgYDVR0fBEMwQTA/oD2g
O4Y5aHR0cDovL0luZEMxRGlnaXRhbElELWNybC52ZXJpc2lnbi5jb20vSW5kQzFEaWdpdGFs
SUQuY3JsMA0GCSqGSIb3DQEBBQUAA4IBAQAxhdnbwrUOuIrJBrZ+T2mMOJJOT8gJp9gvzwJP
HXevZ6DtqgrD0oNhI5bpXbgvIYjFHS9zgGi264F7qLxPYYwFF0qt0IQxUp3S72rrNtpTrBTS
FoPjfuKzfK/6zv5NEExfChalzDKxKUrdymfCT3/eRPkAGRMBaADDpb1RRrmpLHDU4RZkiX48
LwLlTDFz+Yot/DO7YZCNpV38IKHN6mNfYzOUKL6zoFnY8Dd1q4dTO8d4lRU2bZUQ/i36WsXH
pr9YsPKPd3dOsbO7EVIFUCZzUYPly1jZqG5Ns6KW5e26l/E2mMi5bkgq8ppqbjO0kpfZDcLO
IpVMJvkYPT/6Jqx5MYIB/DCCAfgCAQEwdjBiMQswCQYDVQQGEwJaQTElMCMGA1UEChMcVGhh
d3RlIENvbnN1bHRpbmcgKFB0eSkgTHRkLjEsMCoGA1UEAxMjVGhhd3RlIFBlcnNvbmFsIEZy
ZWVtYWlsIElzc3VpbmcgQ0ECEFCBI5teAiwSJUL8Z5sKYZMwCQYFKw4DAhoFAKBdMCMGCSqG
SIb3DQEJBDEWBBQlGdOUhBxQOY7YazlDhMz4q5kY6zAYBgkqhkiG9w0BCQMxCwYJKoZIhvcN
AQcBMBwGCSqGSIb3DQEJBTEPFw0xMDAxMTYwMzQzMjhaMA0GCSqGSIb3DQEBAQUABIIBAD7i
qJimE04A2+4XnJfp9+6uIKJApV1nbSPqHLLJO2Z+NMETw1v9DrLvJj0pCdFfZSH6aNn/CauY
Mw4SSCnOqtNPgeiUtJ/ECjR6zghApaiILMfHbdtmG53NZpDTsPfKzHyQlpEn5/eCONxYlk7p
jPNAJpgA1zmVxW5Q9X57DgaQPjdRfLq2xk5E+B0FC9Pf9/1VSDR/3rb0uDBvbRVNnlcBSloB
LPzDVagbp72tF9jnQCeHKtfw6C57xxJU9sAEwpKkcrZVrnKx08gLoEjJkfmDZKYUZKTkSYyx
bY330EXvy+spq7la4vXhCYHy7e10NCxlMoI/8RuVVWChXjkrkiI=

--B_3346440208_6177358--


From root@core3.amsl.com  Tue Jan 19 07:45:03 2010
Return-Path: <root@core3.amsl.com>
X-Original-To: speermint@ietf.org
Delivered-To: speermint@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0) id 10F433A6A22; Tue, 19 Jan 2010 07:45:02 -0800 (PST)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20100119154503.10F433A6A22@core3.amsl.com>
Date: Tue, 19 Jan 2010 07:45:02 -0800 (PST)
Cc: speermint@ietf.org
Subject: [Speermint] I-D Action:draft-ietf-speermint-voip-consolidated-usecases-16.txt
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, 19 Jan 2010 15:45:03 -0000

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Session PEERing for Multimedia INTerconnect Working Group of the IETF.


	Title           : VoIP SIP Peering Use Cases
	Author(s)       : A. Uzelac, Y. Lee
	Filename        : draft-ietf-speermint-voip-consolidated-usecases-16.txt
	Pages           : 25
	Date            : 2010-01-19

This document depicts many common Voice over IP (VoIP) use cases for
Session Initiation Protocol (SIP) Peering.  These use cases are
categorized into static and on-demand, and then further sub-
categorized into direct and indirect.  These use cases are not an
exhaustive set, but rather the most common use cases deployed today.

Status of this Memo

This Internet-Draft is submitted to IETF in full conformance with the
provisions of BCP 78 and BCP 79.

Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups.  Note that
other groups may also distribute working documents as Internet-
Drafts.

Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time.  It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."

The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt.

The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html.

This Internet-Draft will expire on July 23, 2010.

Copyright Notice

Copyright (c) 2010 IETF Trust and the persons identified as the
document authors.  All rights reserved.

This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document.  Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document.  Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the BSD License.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-speermint-voip-consolidated-usecases-16.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-speermint-voip-consolidated-usecases-16.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

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


--NextPart--

From D.Malas@cablelabs.com  Tue Jan 19 07:50:13 2010
Return-Path: <D.Malas@cablelabs.com>
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 73AEB3A6A1C for <speermint@core3.amsl.com>; Tue, 19 Jan 2010 07:50:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.187
X-Spam-Level: 
X-Spam-Status: No, score=0.187 tagged_above=-999 required=5 tests=[AWL=0.650,  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 ydCj6EvFpf-l for <speermint@core3.amsl.com>; Tue, 19 Jan 2010 07:50:12 -0800 (PST)
Received: from ondar.cablelabs.com (ondar.cablelabs.com [192.160.73.61]) by core3.amsl.com (Postfix) with ESMTP id 95C863A6818 for <speermint@ietf.org>; Tue, 19 Jan 2010 07:50:12 -0800 (PST)
Received: from kyzyl.cablelabs.com (kyzyl [10.253.0.7]) by ondar.cablelabs.com (8.14.3/8.14.3) with ESMTP id o0JFo626002193; Tue, 19 Jan 2010 08:50:06 -0700
Received: from srvxchg.cablelabs.com (10.5.0.15) by kyzyl.cablelabs.com (F-Secure/fsigk_smtp/303/kyzyl.cablelabs.com); Tue, 19 Jan 2010 08:50:07 -0700 (MST)
X-Virus-Status: clean(F-Secure/fsigk_smtp/303/kyzyl.cablelabs.com)
Received: from srvxchg.cablelabs.com ([::1]) by srvxchg.cablelabs.com ([::1]) with mapi; Tue, 19 Jan 2010 08:50:07 -0700
From: Daryl Malas <D.Malas@cablelabs.com>
To: "'yiu_lee@cable.comcast.com'" <yiu_lee@cable.comcast.com>
Date: Tue, 19 Jan 2010 08:50:07 -0700
Thread-Topic: [Speermint] RE: I-D Action:draft-ietf-speermint-voip-consolidated-usecases-16.txt
Thread-Index: AcqZHl62JoCyec7OQ+efiJTAh5iSNQAAIpqg
Message-ID: <114DAD31379DFA438C0A2E39B3B8AF5D011CBBA684@srvxchg.cablelabs.com>
References: <20100119154503.10F433A6A22@core3.amsl.com>
In-Reply-To: <20100119154503.10F433A6A22@core3.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Approved: ondar
Cc: "'speermint@ietf.org'" <speermint@ietf.org>
Subject: [Speermint] RE: I-D Action:draft-ietf-speermint-voip-consolidated-usecases-16.txt
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, 19 Jan 2010 15:50:13 -0000

Yiu,

Thank you for updating the draft quickly.

Regards,

Daryl

-----Original Message-----
From: speermint-bounces@ietf.org [mailto:speermint-bounces@ietf.org] On Beh=
alf Of Internet-Drafts@ietf.org
Sent: Tuesday, January 19, 2010 8:45 AM
To: i-d-announce@ietf.org
Cc: speermint@ietf.org
Subject: [Speermint] I-D Action:draft-ietf-speermint-voip-consolidated-usec=
ases-16.txt

A New Internet-Draft is available from the on-line Internet-Drafts director=
ies.
This draft is a work item of the Session PEERing for Multimedia INTerconnec=
t Working Group of the IETF.


	Title           : VoIP SIP Peering Use Cases
	Author(s)       : A. Uzelac, Y. Lee
	Filename        : draft-ietf-speermint-voip-consolidated-usecases-16.txt
	Pages           : 25
	Date            : 2010-01-19

This document depicts many common Voice over IP (VoIP) use cases for Sessio=
n Initiation Protocol (SIP) Peering.  These use cases are categorized into =
static and on-demand, and then further sub- categorized into direct and ind=
irect.  These use cases are not an exhaustive set, but rather the most comm=
on use cases deployed today.

Status of this Memo

This Internet-Draft is submitted to IETF in full conformance with the provi=
sions of BCP 78 and BCP 79.

Internet-Drafts are working documents of the Internet Engineering Task Forc=
e (IETF), its areas, and its working groups.  Note that other groups may al=
so distribute working documents as Internet- Drafts.

Internet-Drafts are draft documents valid for a maximum of six months and m=
ay be updated, replaced, or obsoleted by other documents at any time.  It i=
s inappropriate to use Internet-Drafts as reference material or to cite the=
m other than as "work in progress."

The list of current Internet-Drafts can be accessed at http://www.ietf.org/=
ietf/1id-abstracts.txt.

The list of Internet-Draft Shadow Directories can be accessed at http://www=
.ietf.org/shadow.html.

This Internet-Draft will expire on July 23, 2010.

Copyright Notice

Copyright (c) 2010 IETF Trust and the persons identified as the document au=
thors.  All rights reserved.

This document is subject to BCP 78 and the IETF Trust's Legal Provisions Re=
lating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of publication=
 of this document.  Please review these documents carefully, as they descri=
be your rights and restrictions with respect to this document.  Code Compon=
ents extracted from this document must include Simplified BSD License text =
as described in Section 4.e of the Trust Legal Provisions and are provided =
without warranty as described in the BSD License.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-speermint-voip-consolidated-=
usecases-16.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 implementa=
tion to automatically retrieve the ASCII version of the Internet-Draft.

From D.Malas@cablelabs.com  Tue Jan 19 07:54:20 2010
Return-Path: <D.Malas@cablelabs.com>
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 70C8A3A6A16 for <speermint@core3.amsl.com>; Tue, 19 Jan 2010 07:54:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.03
X-Spam-Level: 
X-Spam-Status: No, score=-0.03 tagged_above=-999 required=5 tests=[AWL=0.433,  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 nSohvPQspZSZ for <speermint@core3.amsl.com>; Tue, 19 Jan 2010 07:54:19 -0800 (PST)
Received: from ondar.cablelabs.com (ondar.cablelabs.com [192.160.73.61]) by core3.amsl.com (Postfix) with ESMTP id A55C53A694A for <speermint@ietf.org>; Tue, 19 Jan 2010 07:54:19 -0800 (PST)
Received: from kyzyl.cablelabs.com (kyzyl [10.253.0.7]) by ondar.cablelabs.com (8.14.3/8.14.3) with ESMTP id o0JFsF5c002507 for <speermint@ietf.org>; Tue, 19 Jan 2010 08:54:15 -0700
Received: from srvxchg.cablelabs.com (10.5.0.15) by kyzyl.cablelabs.com (F-Secure/fsigk_smtp/303/kyzyl.cablelabs.com); Tue, 19 Jan 2010 08:54:15 -0700 (MST)
X-Virus-Status: clean(F-Secure/fsigk_smtp/303/kyzyl.cablelabs.com)
Received: from srvxchg.cablelabs.com ([::1]) by srvxchg.cablelabs.com ([::1]) with mapi; Tue, 19 Jan 2010 08:54:15 -0700
From: Daryl Malas <D.Malas@cablelabs.com>
To: "speermint@ietf.org" <speermint@ietf.org>
Date: Tue, 19 Jan 2010 08:54:15 -0700
Thread-Topic: [Speermint] RE:**Last Call** on the Speermint Peering Architecturedraft
Thread-Index: AcqPujZ1COYZ76qwS0GixqlM0TUH4AAx8lVAAideTHA=
Message-ID: <114DAD31379DFA438C0A2E39B3B8AF5D011CBBA685@srvxchg.cablelabs.com>
References: <160DE07A1C4F8E4AA2715DEC577DA4910119108D@srvxchg3.cablelabs.com> <160DE07A1C4F8E4AA2715DEC577DA491011910AC@srvxchg3.cablelabs.com>
In-Reply-To: <160DE07A1C4F8E4AA2715DEC577DA491011910AC@srvxchg3.cablelabs.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Approved: ondar
Subject: [Speermint] RE:**Last Call** on the Speermint Peering Architecturedraft
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, 19 Jan 2010 15:54:20 -0000

All,

This is just a reminder the "Last Call" on the Speermint Peering Architectu=
re draft ends this Friday, January 22nd.  Please review and post comments t=
o the mailing list soon.

Regards,

Daryl
Speermint Chairs

-----Original Message-----
From: speermint-bounces@ietf.org [mailto:speermint-bounces@ietf.org] On Beh=
alf Of Daryl Malas
Sent: Friday, January 08, 2010 9:47 AM
To: speermint@ietf.org
Subject: [Speermint] RE:**Last Call** on the Speermint Peering Architecture=
draft

All,

With the understanding it may be challenging for some to schedule the time =
to review and provide comments in 1 week, the "Last Call" is extended to Ja=
nuary 22nd.

Regards,

Daryl

-----Original Message-----
From: speermint-bounces@ietf.org [mailto:speermint-bounces@ietf.org] On Beh=
alf Of Daryl Malas
Sent: Thursday, January 07, 2010 9:55 AM
To: speermint@ietf.org
Subject: [Speermint] **Last Call** on the Speermint Peering Architecturedra=
ft

All,
=20
We discussed this during our last meeting, but I wanted to officially note =
it on the mailing list.  Please provide any final comments on the Speermint=
 Peering Architecture draft.  This last call will last approximately 1 week=
 and end on January 15th.

Here is a link to the draft:
http://tools.ietf.org/html/draft-ietf-speermint-architecture-09

Adam,

Please review and begin correction of the nits here:
http://tools.ietf.org/idnits?url=3Dhttp://tools.ietf.org/id/draft-ietf-spe
ermint-architecture-09.txt.

We would like to wrap up this draft quickly, so everyone's effort to review=
 and provide and final feedback is greatly appreciated.

Regards,

Daryl
_______________________________________________
Speermint mailing list
Speermint@ietf.org
https://www.ietf.org/mailman/listinfo/speermint
_______________________________________________
Speermint mailing list
Speermint@ietf.org
https://www.ietf.org/mailman/listinfo/speermint

From yiu_lee@cable.comcast.com  Tue Jan 19 12:02:52 2010
Return-Path: <yiu_lee@cable.comcast.com>
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 6264B3A67A8 for <speermint@core3.amsl.com>; Tue, 19 Jan 2010 12:02:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.396
X-Spam-Level: 
X-Spam-Status: No, score=-6.396 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368, RCVD_IN_DNSWL_HI=-8, RCVD_NUMERIC_HELO=2.067]
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 N9jcUVyx4Yzt for <speermint@core3.amsl.com>; Tue, 19 Jan 2010 12:02:51 -0800 (PST)
Received: from pacdcimo01.cable.comcast.com (PacdcIMO01.cable.comcast.com [24.40.8.145]) by core3.amsl.com (Postfix) with ESMTP id 965923A65A6 for <speermint@ietf.org>; Tue, 19 Jan 2010 12:02:43 -0800 (PST)
Received: from ([24.40.15.92]) by pacdcimo01.cable.comcast.com with ESMTP  id 5503620.68232784; Tue, 19 Jan 2010 15:02:35 -0500
Received: from PACDCEXCMB04.cable.comcast.com ([24.40.15.86]) by PACDCEXCSMTP03.cable.comcast.com with Microsoft SMTPSVC(6.0.3790.3959); Tue, 19 Jan 2010 15:01:04 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: from 69.241.25.0 ([69.241.25.0]) by PACDCEXCMB04.cable.comcast.com ([24.40.15.86]) via Exchange Front-End Server webmail.comcast.com ([24.40.8.152]) with Microsoft Exchange Server HTTP-DAV ; Tue, 19 Jan 2010 20:01:03 +0000
MIME-Version: 1.0
Content-class: urn:content-classes:message
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="B_3346758060_1351671"
Date: Tue, 19 Jan 2010 15:01:00 -0500
Message-ID: <C77B79AC.1BB56%yiu_lee@cable.comcast.com>
In-Reply-To: <114DAD31379DFA438C0A2E39B3B8AF5D011CBBA684@srvxchg.cablelabs.com>
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
Thread-Topic: [Speermint] RE: I-D Action:draft-ietf-speermint-voip-consolidated-usecases-16.txt
Thread-Index: AcqZHl62JoCyec7OQ+efiJTAh5iSNQAAIpqgAAjNdqQ=
From: "Lee, Yiu" <Yiu_Lee@Cable.Comcast.com>
To: "Daryl Malas" <D.Malas@cablelabs.com>
X-OriginalArrivalTime: 19 Jan 2010 20:01:04.0121 (UTC) FILETIME=[216DB690:01CA9942]
Cc: speermint@ietf.org
Subject: Re: [Speermint] I-D Action:draft-ietf-speermint-voip-consolidated-usecases-16.txt
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, 19 Jan 2010 20:02:52 -0000

> This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

--B_3346758060_1351671
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit

It is now v16, I hope I won't need to submit v20 to go to the Editor Q ;-)


On 1/19/10 10:50 AM, "Daryl Malas" <D.Malas@cablelabs.com> wrote:

> Yiu,
> 
> Thank you for updating the draft quickly.
> 
> Regards,
> 
> Daryl
> 
> -----Original Message-----
> From: speermint-bounces@ietf.org [mailto:speermint-bounces@ietf.org] On Behalf
> Of Internet-Drafts@ietf.org
> Sent: Tuesday, January 19, 2010 8:45 AM
> To: i-d-announce@ietf.org
> Cc: speermint@ietf.org
> Subject: [Speermint] I-D
> Action:draft-ietf-speermint-voip-consolidated-usecases-16.txt
> 
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
> This draft is a work item of the Session PEERing for Multimedia INTerconnect
> Working Group of the IETF.
> 
> 
> Title           : VoIP SIP Peering Use Cases
> Author(s)       : A. Uzelac, Y. Lee
> Filename        : draft-ietf-speermint-voip-consolidated-usecases-16.txt
> Pages           : 25
> Date            : 2010-01-19
> 
> This document depicts many common Voice over IP (VoIP) use cases for Session
> Initiation Protocol (SIP) Peering.  These use cases are categorized into
> static and on-demand, and then further sub- categorized into direct and
> indirect.  These use cases are not an exhaustive set, but rather the most
> common use cases deployed today.
> 
> Status of this Memo
> 
> This Internet-Draft is submitted to IETF in full conformance with the
> provisions of BCP 78 and BCP 79.
> 
> Internet-Drafts are working documents of the Internet Engineering Task Force
> (IETF), its areas, and its working groups.  Note that other groups may also
> distribute working documents as Internet- Drafts.
> 
> Internet-Drafts are draft documents valid for a maximum of six months and may
> be updated, replaced, or obsoleted by other documents at any time.  It is
> inappropriate to use Internet-Drafts as reference material or to cite them
> other than as "work in progress."
> 
> The list of current Internet-Drafts can be accessed at
> http://www.ietf.org/ietf/1id-abstracts.txt.
> 
> The list of Internet-Draft Shadow Directories can be accessed at
> http://www.ietf.org/shadow.html.
> 
> This Internet-Draft will expire on July 23, 2010.
> 
> Copyright Notice
> 
> Copyright (c) 2010 IETF Trust and the persons identified as the document
> authors.  All rights reserved.
> 
> This document is subject to BCP 78 and the IETF Trust's Legal Provisions
> Relating to IETF Documents
> (http://trustee.ietf.org/license-info) in effect on the date of publication of
> this document.  Please review these documents carefully, as they describe your
> rights and restrictions with respect to this document.  Code Components
> extracted from this document must include Simplified BSD License text as
> described in Section 4.e of the Trust Legal Provisions and are provided
> without warranty as described in the BSD License.
> 
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-speermint-voip-consolidated-use
> cases-16.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.

--B_3346758060_1351671
Content-type: application/pkcs7-signature; name="smime.p7s"
Content-transfer-encoding: base64
Content-disposition: attachment;
	filename="smime.p7s"

MIIN2AYJKoZIhvcNAQcCoIINyTCCDcUCAQExCzAJBgUrDgMCGgUAMAsGCSqGSIb3DQEHAaCC
C6QwggMPMIICeKADAgECAhBQgSObXgIsEiVC/GebCmGTMA0GCSqGSIb3DQEBBQUAMGIxCzAJ
BgNVBAYTAlpBMSUwIwYDVQQKExxUaGF3dGUgQ29uc3VsdGluZyAoUHR5KSBMdGQuMSwwKgYD
VQQDEyNUaGF3dGUgUGVyc29uYWwgRnJlZW1haWwgSXNzdWluZyBDQTAeFw0wOTA4MDgwODQw
MDJaFw0xMDA4MDgwODQwMDJaMEsxHzAdBgNVBAMTFlRoYXd0ZSBGcmVlbWFpbCBNZW1iZXIx
KDAmBgkqhkiG9w0BCQEWGXlpdV9sZWVAY2FibGUuY29tY2FzdC5jb20wggEiMA0GCSqGSIb3
DQEBAQUAA4IBDwAwggEKAoIBAQCscC6PT5lvsXUq4lOfCGh5DV7ZnHkaKTZrdclNBGwIUu1H
njC0937hsVMKSuyKXMiuGc2VS1sjvEzqtqcSiGBkX2ZhGszLppMjiNwb3McBc4slgNxK1OfX
Q+g/C/Fi/pZbg3KU/V50QGQQsM0yO1HOK7FGyvOH023fNvQ7E0syH6NAbkmf4mQoHLFUMkjD
mfdbtrnYeGvNjrX6hLMmUuo0Y6MAyJQdBDH8p+6V0/hjvYOA2yAW+ptxxEbPYGrm1/f2TYp2
o43bA9ri/P8Rtli6kaKQvC5HhReyNJLWWG2z8JjbqcQd1sP443WI1voiBbqOLNpu3KWnBRzC
3+n6eYhfAgMBAAGjWTBXMA4GA1UdDwEB/wQEAwID+DARBglghkgBhvhCAQEEBAMCBaAwJAYD
VR0RBB0wG4EZeWl1X2xlZUBjYWJsZS5jb21jYXN0LmNvbTAMBgNVHRMBAf8EAjAAMA0GCSqG
SIb3DQEBBQUAA4GBAF+NiG7zCDaZsRKq54bnGbGi1nFyzFa4sL72O+J2vRZoyVU8tFpl9Xz/
BnTMU+olVJ+Q4wmnwuSJZ6rTblLTlKRVnkd3PBcnWYYVYSvwhKuTTmTX99RZHvGSTGJomy7M
PuOLo/XqZgHgA/oZ38QQp76e9EPeM2nfFJHc9bTK0RlOMIIDPzCCAqigAwIBAgIBDTANBgkq
hkiG9w0BAQUFADCB0TELMAkGA1UEBhMCWkExFTATBgNVBAgTDFdlc3Rlcm4gQ2FwZTESMBAG
A1UEBxMJQ2FwZSBUb3duMRowGAYDVQQKExFUaGF3dGUgQ29uc3VsdGluZzEoMCYGA1UECxMf
Q2VydGlmaWNhdGlvbiBTZXJ2aWNlcyBEaXZpc2lvbjEkMCIGA1UEAxMbVGhhd3RlIFBlcnNv
bmFsIEZyZWVtYWlsIENBMSswKQYJKoZIhvcNAQkBFhxwZXJzb25hbC1mcmVlbWFpbEB0aGF3
dGUuY29tMB4XDTAzMDcxNzAwMDAwMFoXDTEzMDcxNjIzNTk1OVowYjELMAkGA1UEBhMCWkEx
JTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0
ZSBQZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBMIGfMA0GCSqGSIb3DQEBAQUAA4GNADCB
iQKBgQDEpjxVc1X7TrnKmVoeaMB1BHCd3+n/ox7svc31W/Iadr1/DDph8r9RzgHU5VAKMNcC
Y1osiRVwjt3J8CuFWqo/cVbLrzwLB+fxH5E2JCoTzyvV84J3PQO+K/67GD4Hv0CAAmTXp6a7
n2XRxSpUhQ9IBH+nttE8YQRAHmQZcmC3+wIDAQABo4GUMIGRMBIGA1UdEwEB/wQIMAYBAf8C
AQAwQwYDVR0fBDwwOjA4oDagNIYyaHR0cDovL2NybC50aGF3dGUuY29tL1RoYXd0ZVBlcnNv
bmFsRnJlZW1haWxDQS5jcmwwCwYDVR0PBAQDAgEGMCkGA1UdEQQiMCCkHjAcMRowGAYDVQQD
ExFQcml2YXRlTGFiZWwyLTEzODANBgkqhkiG9w0BAQUFAAOBgQBIjNFQg+oLLswNo2asZw9/
r6y+whehQ5aUnX9MIbj4Nh+qLZ82L8D0HFAgk3A8/a3hYWLD2ToZfoSxmRsAxRoLgnSeJVCU
YsfbJ3FXJY3dqZw5jowgT2Vfldr394fWxghOrvbqNOUQGls1TXfjViF4gtwhGTXeJLHTHUb/
XV9lTzCCBUowggQyoAMCAQICEEsVRXwTaRSoi7d3sapu92EwDQYJKoZIhvcNAQEFBQAwgd0x
CzAJBgNVBAYTAlVTMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNp
Z24gVHJ1c3QgTmV0d29yazE7MDkGA1UECxMyVGVybXMgb2YgdXNlIGF0IGh0dHBzOi8vd3d3
LnZlcmlzaWduLmNvbS9ycGEgKGMpMDUxHjAcBgNVBAsTFVBlcnNvbmEgTm90IFZhbGlkYXRl
ZDE3MDUGA1UEAxMuVmVyaVNpZ24gQ2xhc3MgMSBJbmRpdmlkdWFsIFN1YnNjcmliZXIgQ0Eg
LSBHMjAeFw0wOTExMDUwMDAwMDBaFw0xMDExMDUyMzU5NTlaMIIBEzEXMBUGA1UEChMOVmVy
aVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlTaWduIFRydXN0IE5ldHdvcmsxRjBEBgNVBAsT
PXd3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9yeS9SUEEgSW5jb3JwLiBieSBSZWYuLExJQUIu
TFREKGMpOTgxHjAcBgNVBAsTFVBlcnNvbmEgTm90IFZhbGlkYXRlZDEzMDEGA1UECxMqRGln
aXRhbCBJRCBDbGFzcyAxIC0gTmV0c2NhcGUgRnVsbCBTZXJ2aWNlMRAwDgYDVQQDFAdZaXUg
TGVlMSgwJgYJKoZIhvcNAQkBFhl5aXVfbGVlQGNhYmxlLmNvbWNhc3QuY29tMIIBIjANBgkq
hkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEArfUYyB1WddeTV1whaQNaHKstvQcFnloN37ZayFeM
H8D3vKzrImHg6WIFOm7+kA5GsW+cO5au9HNL5fKSf1jYb4/EMuaEITqBpBK41nBok7jP3FiD
KPt4TtsJsnqDRLaS2SS3YBSTZOzgdLU4mTjveMYmyFdeRbNsrO2v8bWkcQLE/zf5wSdGS6rF
nDF8MXw70BkHmZte1eY+EYoi694+0ukeg9eKw5JFlmBrYAoE1oDxMHXXIV2ju/zC9kpK5DZC
AVtofp+hL5A+pgnLxOsfPrRpcrkQeM1ryhujXCij/jdHMMdNS3+z97QSw8cNfG3PBF8KnBp6
67jVylTR/d3LCwIDAQABo4HMMIHJMAkGA1UdEwQCMAAwRAYDVR0gBD0wOzA5BgtghkgBhvhF
AQcXATAqMCgGCCsGAQUFBwIBFhxodHRwczovL3d3dy52ZXJpc2lnbi5jb20vcnBhMAsGA1Ud
DwQEAwIFoDAdBgNVHSUEFjAUBggrBgEFBQcDBAYIKwYBBQUHAwIwSgYDVR0fBEMwQTA/oD2g
O4Y5aHR0cDovL0luZEMxRGlnaXRhbElELWNybC52ZXJpc2lnbi5jb20vSW5kQzFEaWdpdGFs
SUQuY3JsMA0GCSqGSIb3DQEBBQUAA4IBAQAxhdnbwrUOuIrJBrZ+T2mMOJJOT8gJp9gvzwJP
HXevZ6DtqgrD0oNhI5bpXbgvIYjFHS9zgGi264F7qLxPYYwFF0qt0IQxUp3S72rrNtpTrBTS
FoPjfuKzfK/6zv5NEExfChalzDKxKUrdymfCT3/eRPkAGRMBaADDpb1RRrmpLHDU4RZkiX48
LwLlTDFz+Yot/DO7YZCNpV38IKHN6mNfYzOUKL6zoFnY8Dd1q4dTO8d4lRU2bZUQ/i36WsXH
pr9YsPKPd3dOsbO7EVIFUCZzUYPly1jZqG5Ns6KW5e26l/E2mMi5bkgq8ppqbjO0kpfZDcLO
IpVMJvkYPT/6Jqx5MYIB/DCCAfgCAQEwdjBiMQswCQYDVQQGEwJaQTElMCMGA1UEChMcVGhh
d3RlIENvbnN1bHRpbmcgKFB0eSkgTHRkLjEsMCoGA1UEAxMjVGhhd3RlIFBlcnNvbmFsIEZy
ZWVtYWlsIElzc3VpbmcgQ0ECEFCBI5teAiwSJUL8Z5sKYZMwCQYFKw4DAhoFAKBdMCMGCSqG
SIb3DQEJBDEWBBQ7iIkimbsl8IkhAjl0fj5jmpWRTTAYBgkqhkiG9w0BCQMxCwYJKoZIhvcN
AQcBMBwGCSqGSIb3DQEJBTEPFw0xMDAxMTkyMDAxMDBaMA0GCSqGSIb3DQEBAQUABIIBAJ5P
KQSeYo0PLqc4eGoREU3MwDkDf5vb2jLH53JxtZF78qaIzsxSRdkyujhCAukI4IqaahbXOqnm
yR8XWF1IgwtMRFbfyX0NZfrwbCunjsKsOdK19rxdMuTyc3XkrheNxe8opCHKa/U/rveNE8MT
SszldHrBbtouSENaN81UOA5eWZIpZypt/PtwyA/MPxCG4AqNqf+kY4V3z96MRrHFeKC2797G
/onDOkBeFPYj9RTSojYoa7x2Xhd/Lzi8T+DfVQUXs3yHD9Gub4f+R4ljB604L98mOEfthLtD
03XToozP8HFLU9oBnLPto8x/rXphsGCzogkGYLfJfGm9bQDbht4=

--B_3346758060_1351671--


From john.elwell@siemens-enterprise.com  Wed Jan 20 01:17:36 2010
Return-Path: <john.elwell@siemens-enterprise.com>
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 B9B373A68C9 for <speermint@core3.amsl.com>; Wed, 20 Jan 2010 01:17:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.577
X-Spam-Level: 
X-Spam-Status: No, score=-2.577 tagged_above=-999 required=5 tests=[AWL=0.022,  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 na5jkijpYJ7P for <speermint@core3.amsl.com>; Wed, 20 Jan 2010 01:17:35 -0800 (PST)
Received: from ms03.m0019.fra.mmp.de.bt.com (m0019.fra.mmp.de.bt.com [62.180.227.30]) by core3.amsl.com (Postfix) with ESMTP id BFA7C3A68A9 for <speermint@ietf.org>; Wed, 20 Jan 2010 01:17:34 -0800 (PST)
Received: from senmx11-mx ([62.134.46.9] [62.134.46.9]) by ms03.m0020.fra.mmp.de.bt.com with ESMTP id BT-MMP-596774; Wed, 20 Jan 2010 10:17:29 +0100
Received: from MCHP064A.global-ad.net (unknown [172.29.37.63]) by senmx11-mx (Server) with ESMTP id C77EF1EB82B0; Wed, 20 Jan 2010 10:17:29 +0100 (CET)
Received: from MCHP058A.global-ad.net ([172.29.37.55]) by MCHP064A.global-ad.net ([172.29.37.63]) with mapi; Wed, 20 Jan 2010 10:17:29 +0100
From: "Elwell, John" <john.elwell@siemens-enterprise.com>
To: Daryl Malas <D.Malas@cablelabs.com>, "speermint@ietf.org" <speermint@ietf.org>
Date: Wed, 20 Jan 2010 10:15:24 +0100
Thread-Topic: [Speermint] RE:**Last Call** on the Speermint Peering Architecturedraft
Thread-Index: AcqPujZ1COYZ76qwS0GixqlM0TUH4AAx8lVAAideTHAAC1mzYA==
Message-ID: <A444A0F8084434499206E78C106220CA6A2339BD@MCHP058A.global-ad.net>
References: <160DE07A1C4F8E4AA2715DEC577DA4910119108D@srvxchg3.cablelabs.com> <160DE07A1C4F8E4AA2715DEC577DA491011910AC@srvxchg3.cablelabs.com> <114DAD31379DFA438C0A2E39B3B8AF5D011CBBA685@srvxchg.cablelabs.com>
In-Reply-To: <114DAD31379DFA438C0A2E39B3B8AF5D011CBBA685@srvxchg.cablelabs.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [Speermint] **Last Call** on the Speermint Peering Architecturedraft
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: Wed, 20 Jan 2010 09:17:36 -0000

I have reviewed the draft, and I have a number of concerns that collectivel=
y mean the document is not yet ready. In my opinion, as it stands, it does =
more to generate confusion than it does to shed light on the subject.

General concerns:

1. Figure 1 is reasonably clear. Yet later there is frequent mentioning of =
"SF", which is not shown in Figure 1. Also there is occasional mention of "=
MF", which is also not shown in figure 1. Although all these terms are defi=
ned in RFC 5486, I find unhelpful to use the terms without showing them in =
the architecture diagram.

In fact the figure shows SBE and DBE. My understanding is that SBE and DBE =
are considered physical entities, whereas SF and MF are functional entities=
. This would account for the idea that an SBE can contain an SF, for exampl=
e. In that case, figure 1 would appear to contain a mixture of functional e=
ntities (LUF and LRF) and physical entities (SBE and DBE). Would it not be =
better to show in the main architectural diagram only functional entities (=
with perhaps a second diagram showing an example of how these might map to =
physical entities)?


Related to this, I find section 3.1 very confusing.

Where it talks about obtaining the address of the SF of the target SSP, sho=
uld this be the address of the SBE of the target SSP?

2. The structure of the document is hard to figure out. Section 2 is clear,=
 but then we have section 3 on procedures and section 4 on recommended proc=
edures - how are these supposed to relate to one another.

Then section 4.1.1 is supposed to be procedures for the LUF - are these sup=
posed to be procedures for the LUF itself or for using the LUF? Probably th=
e latter, since section 4.1.1.1 talks about performing a LUF. Moreover, sec=
tion 4.1.1.1 goes beyond using the LUF but also mentions use of the LRF. Al=
so 4.1.1.1 fails to even mention discovery of the target domain, which is m=
eant to be the purpose of the LUF.

Then section 4.1.2.2 is supposed to be procedures for the LRF, but it seems=
 to be concerned with the case where you do not have a target domain. In ot=
her words, it uses an alternative target domain (one with a PSTN gateway). =
So isn't this more to do with LUF functionality (section 4.1.1) than LRF fu=
nctionality (4.1.2)?

Specific concerns:

3. RFC 2119 language. This Informational document refers to RFC 2119, yet t=
he only instances of RFC 2119 language I found were about 3 instances of "M=
AY". I don't think RFC 2119 language is appropriate.
Major concerns:

4. Figure 1 shows the target SSP having an LUF and LRF, yet I cannot find a=
ny procedures for these in section 4.2.

4. In section 3:
" The originating SSP would likely perform steps 1-4, and the target SSP wo=
uld
   likely perform steps 4-5."
Step 5 (ending the session) could equally be performed by either the origin=
ating SSP or the target SSP.

5. "In the case the target SSP changes, then steps 1-4 would be repeated."
What is meant by "target SSP changes" - is this something like a mid-call t=
ransfer, redirection, or what?

6. "This is
   reflected in Figure 2 that shows the target SSP with its own peering fun=
ctions."
I cannot find a Figure 2.

7. Section 4.1.1:
"Purpose is to determine the SF of the target domain of a given request and
   optionally develop Session Establishment Data."
This is not in line with the RFC 5486 definition of LUF (purpose is to dete=
rmine target domain).

8. The term "session establishment data", although defined in RFC 5486, is =
not used elsewhere in the architecture document so should not be introduced=
 here.

9. This section seems to mix up the terms "URI" and "address" - I think a l=
ot of the time when it is talking about "address" it really means "URI". Fo=
r example "If the target address does not represent..."

10. "If the target address does not represent a resource inside the origina=
ting
   SSP's administrative domain or federation of domains, then the originati=
ng SSP
   performs a Lookup Function (LUF) to determine a target address"
So it uses the target address to obtain the target address? Seems circular,=
 or am I missing something.

11. "If the highest priority
   supported URI scheme is sip: or sips: the originating SSP skips to SIP D=
NS
   resolution in Section 5.1.3. "
There is no 5.1.3. Also, we should make it clear that the highest priority =
URI scheme is a result the result of the procedures of [8].

12. "performs a Lookup Function (LUF) to determine a target address"
Again, this is not what a LUF does, according to RFC 5486.

13. "and then is
   resolves the call routing data by using the Location routing Function (L=
RF)"
Apart from the grammatical error, where does it get the call routing data f=
rom and what is the result of resolving that data?

14. In 4.1.2.2, what is "the routing table"? This term has not been previou=
sly introduced.

15. "If so, the originating SSP rewrites"
It is not clear what "If so" refers to.

16. "the originating SSP rewrites the Request-URI to address the gateway
   resource in the target SSP's domain"
Why are we advocating rewrite of the Request-URI, rather than use of the Ro=
ute header field?

17. In 4.1.2.3:
"LRF to LRF Routing"
and
"Communications between the LRF of two interconnecting SSPs may use DNS or
   statically provisioned IP Addresses for reachability."
This is the first hint of communications between the LRFs of two SSPs. It i=
s not apparent from figure 1, which seems to show the two LRFs each accessi=
ng the same ENUM database, but with no hint of communication between the tw=
o. Before talking about how we achieve communication between LRFs, we shoul=
d first explain why they need to communicate with each other. And if there =
is indeed communication between the two, something should be said in sectio=
n 4.2 too.

18. Section 4.1.3 has SBE in the title but immediately starts talking about=
 SF.

19. Section 4.1.3.1, on the originating SSP establishing a trust relationsh=
ip, mentions IPsec and collocation, but fails to mention TLS (yet in 4.2, f=
or the target SSP, TLS is mentioned, but not the other two).

20. Section 4.2.1.1
"The SF of the Target SSP verifies that the Identity header is valid,
   corresponds to the message, corresponds to the Identity-Info header, and=
 that
   the domain in the From header corresponds to one of the domains in the T=
LS
   client certificate."
First, it does not allow the possibility of the Identity header field being=
 absent. Second, if the Identity header field was inserted by a domain upst=
ream of the Originating SSP, the domain in the From header will be differen=
t from the domain in the TLS client certificate.

21. Concerning that same text, it is unclear whether the requirement to che=
ck the domain of the From header applies only if the SIP Identity header is=
 present or applies regardless. But as pointed out in the previous comment,=
 the requirement is wrong anyway.

22. As a further comment on that text, anything to do with contents of the =
SIP message should not be discussed in the section dealing with TLS establi=
shment, but would be more appropriate in 4.2.1.2.

23. In section 6:
"In order to maintain a consistent approach, unique and specialized securit=
y
   requirements common for the majority of peering relationships, should be
   standardized within the IETF."
Is this saying that the IETF should do some standardization work? If so, I =
don't think this is an appropriate statement for an RFC.
Or is it saying that SSPs should deploy security solutions that have been s=
tandardized by the IETF? If so, we could surely find better wording, or bet=
ter still, identify those solutions that should be used.

John

> -----Original Message-----
> From: speermint-bounces@ietf.org=20
> [mailto:speermint-bounces@ietf.org] On Behalf Of Daryl Malas
> Sent: 19 January 2010 15:54
> To: speermint@ietf.org
> Subject: [Speermint] RE:**Last Call** on the Speermint=20
> Peering Architecturedraft
>=20
> All,
>=20
> This is just a reminder the "Last Call" on the Speermint=20
> Peering Architecture draft ends this Friday, January 22nd. =20
> Please review and post comments to the mailing list soon.
>=20
> Regards,
>=20
> Daryl
> Speermint Chairs
>=20
> -----Original Message-----
> From: speermint-bounces@ietf.org=20
> [mailto:speermint-bounces@ietf.org] On Behalf Of Daryl Malas
> Sent: Friday, January 08, 2010 9:47 AM
> To: speermint@ietf.org
> Subject: [Speermint] RE:**Last Call** on the Speermint=20
> Peering Architecturedraft
>=20
> All,
>=20
> With the understanding it may be challenging for some to=20
> schedule the time to review and provide comments in 1 week,=20
> the "Last Call" is extended to January 22nd.
>=20
> Regards,
>=20
> Daryl
>=20
> -----Original Message-----
> From: speermint-bounces@ietf.org=20
> [mailto:speermint-bounces@ietf.org] On Behalf Of Daryl Malas
> Sent: Thursday, January 07, 2010 9:55 AM
> To: speermint@ietf.org
> Subject: [Speermint] **Last Call** on the Speermint Peering=20
> Architecturedraft
>=20
> All,
> =20
> We discussed this during our last meeting, but I wanted to=20
> officially note it on the mailing list.  Please provide any=20
> final comments on the Speermint Peering Architecture draft. =20
> This last call will last approximately 1 week and end on January 15th.
>=20
> Here is a link to the draft:
> http://tools.ietf.org/html/draft-ietf-speermint-architecture-09
>=20
> Adam,
>=20
> Please review and begin correction of the nits here:
> http://tools.ietf.org/idnits?url=3Dhttp://tools.ietf.org/id/draf
> t-ietf-spe
> ermint-architecture-09.txt.
>=20
> We would like to wrap up this draft quickly, so everyone's=20
> effort to review and provide and final feedback is greatly=20
> appreciated.
>=20
> Regards,
>=20
> Daryl
> _______________________________________________
> Speermint mailing list
> Speermint@ietf.org
> https://www.ietf.org/mailman/listinfo/speermint
> _______________________________________________
> Speermint mailing list
> Speermint@ietf.org
> https://www.ietf.org/mailman/listinfo/speermint
> _______________________________________________
> Speermint mailing list
> Speermint@ietf.org
> https://www.ietf.org/mailman/listinfo/speermint
> =

From alexander.mayrhofer@enum.at  Wed Jan 20 07:37:21 2010
Return-Path: <alexander.mayrhofer@enum.at>
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 D0CF93A68B3 for <speermint@core3.amsl.com>; Wed, 20 Jan 2010 07:37:20 -0800 (PST)
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 4apzdxlojE0r for <speermint@core3.amsl.com>; Wed, 20 Jan 2010 07:37:18 -0800 (PST)
Received: from na.nona.net (engine01.malakii.net [188.40.65.119]) by core3.amsl.com (Postfix) with ESMTP id 3465A3A6452 for <speermint@ietf.org>; Wed, 20 Jan 2010 07:37:14 -0800 (PST)
Received: from [10.10.0.133] ([::ffff:83.136.33.3]) (AUTH: PLAIN axelm, TLS: TLSv1/SSLv3,256bits,AES256-SHA) by kahua with esmtp; Wed, 20 Jan 2010 16:37:08 +0100 id 000000000015485A.000000004B572324.000070CE
Message-ID: <4B5722E1.4090101@enum.at>
Date: Wed, 20 Jan 2010 16:36:01 +0100
From: Alexander Mayrhofer <alexander.mayrhofer@enum.at>
Organization: enum.at GmbH
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
To: speermint@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: [Speermint] Review of architecture-09
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: Wed, 20 Jan 2010 15:37:21 -0000

In the light of the LC, i have reviewed
draft-ietf-speermint-architecture-09. Here are my comments:

Generally, i think that some of the issues i have listed below require
an additional revision before we progress the draft. I've found content
as well as editorial issues, and i suggest solving those before we
proceed the draft.

More details:

- The draft has a number of idnits - those should be solved:
http://tools.ietf.org/idnits?url=http://tools.ietf.org/id/draft-ietf-speermint-architecture-09.txt

Most obvious are the over-long lines, and the outdated references.

- nit: 3.1 is the only sub-secion of 3. - this is sometimes considered
misuse of sections...

- Acronyms are not expanded on first use - i've spotted "UA", "ENUM",
"SIP", "URI", "NAPTR", "SRV", "EvRC" (??)

- "Figure 2" is referenced a few times, eg. on page 4, even though
there's just "figure 1".

- Content: Page 5, first line: "intra-SSP" should probably be clarified
as "resource within the originating SSP"

- Typo: Page 5, bullet 4: "tec" is probably supposed to be "text"?

- Content: Page 5, "In case the target SSP changes..." What does that
mean? I thought the that "target SSP" would be the ultimate destination,
and hence the "target SSP" cannot "change" (except in cases like
porting...) If this is about a "transit" case, then we have a
terminology problem - that would then be the "next hop SSP"? The only
exception might be when a session gets redirected to a different SSP -
is that case meant here? Also, the reference to "figure 2" is pointing
nowhere..

- Typo: Page 5: "communicator" -> "communicate" in section 3.1

- Content: Section 3.1: there seems to be a confusion between "network
elements" and "functions". If i understand it correctly, then "elements"
implement "functions", hence "elements" can only communicate with other
"elements", but not with "functions", because the "functions" are
something abstract?

- Content: Section 4.4.1: The definition of "LUF" in RFC 5486 is
different from what is stated here. RFC 5486 says the LUF returns the
"target domain", and not the address of the SF or the target SSP...
Again, a terminology problem around the famous "no-man's land" between
LUF and LRF..

The draft itself says in 4.1.2 that the *LR* discovers the "next hop SF"
(page 6, bottom)

An option would be to state in 4.1.1 that "the LUF identifies the target
 SSP for a given request"?

- Content: Section 4.1.1.1 "performs a Lookup Function (LUF) to
determing the target address" should probably also be "... to determine
the target SSP"?

- Nit: page 7, line 3 "may be used" should read "need to be used"?

- Nit: "originating SSP" and other terminology should be written as
"Originating SSP", so that those terms are easier distinguished from
other "non-terminology" text. (for example, first line of 4.1.2.1 - in
4.1.2.2, "Originating SSP" is already capitalized)

- Content: 4.1.2.1 - What is an "receiving SSP"? Is that the "Target
SSP", or some intermediate SSP?

- Content: 4.1.2.1 says "when communicating with another SSP" might be
redundant, because intra-SSP communication is out of scope anyway?

- Nit: 4.1.2.3: "communicationS" -> "communication"

- Content: Page 8, first line: "a SF may perform"... I think that should
be "a SBE may perform", or "a SF of an SBE" (like a few lines down) -
not sure if this is intentional, though.

- Content: 4.1.3.1.1 - The sentence is a) completely broken and b)
contradicts the recommendation (?) to select TLS in 4.1.2.1

- Content: Section 5 "Peering must occur in a common IP address space" -
what is meant by this? The whole internet is a "common IP address space"
(or, actually two spaces, if you consider v4 and v6). I *think* i
understand what is meant here ("a broadcast domain"?), but the
definition is extremely vague...

- Content: Section 4.2.1.1, last sentence: My local SIP guru here says
that checking the "From" header against the client TLS certificate might
be dangerous in transit scenarios, because it might contain the domain
of the originating SSP, while the client certificate would be from the
intermediate SSP. Also, he notes that verifying both the Identity
headers *and* the From header might be too much of verification...

- Content: Section 6, Security Considerations are weak: An "optional
requirement" is somehow a contradiction, and not really convincing,
particularly in the field of Security.. Maybe change that to
"cryptography should be required unless physical security..." Also, i
don't see the work requested in the second paragraph happening anywhere...

- Nit: RFC2119 is referenced, but i don't see a single RFC2119-style
MAY, MUST etc. in the draft. It might be safe to remove the reference to
RFC2119.

tia,

Alex


From D.Malas@cablelabs.com  Thu Jan 21 08:52:46 2010
Return-Path: <D.Malas@cablelabs.com>
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 8B7313A68D9 for <speermint@core3.amsl.com>; Thu, 21 Jan 2010 08:52:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.138
X-Spam-Level: 
X-Spam-Status: No, score=-2.138 tagged_above=-999 required=5 tests=[AWL=2.325,  BAYES_00=-2.599, GB_I_INVITATION=-2, GB_I_LETTER=-2, 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 8AHZ8mRPJSZJ for <speermint@core3.amsl.com>; Thu, 21 Jan 2010 08:52:45 -0800 (PST)
Received: from ondar.cablelabs.com (ondar.cablelabs.com [192.160.73.61]) by core3.amsl.com (Postfix) with ESMTP id 349213A68B3 for <speermint@ietf.org>; Thu, 21 Jan 2010 08:52:45 -0800 (PST)
Received: from kyzyl.cablelabs.com (kyzyl [10.253.0.7]) by ondar.cablelabs.com (8.14.3/8.14.3) with ESMTP id o0LGqe5M012040 for <speermint@ietf.org>; Thu, 21 Jan 2010 09:52:40 -0700
Received: from srvxchg.cablelabs.com (10.5.0.15) by kyzyl.cablelabs.com (F-Secure/fsigk_smtp/303/kyzyl.cablelabs.com); Thu, 21 Jan 2010 09:52:40 -0700 (MST)
X-Virus-Status: clean(F-Secure/fsigk_smtp/303/kyzyl.cablelabs.com)
Received: from srvxchg.cablelabs.com ([10.5.0.15]) by srvxchg ([10.5.0.15]) with mapi; Thu, 21 Jan 2010 09:52:41 -0700
From: Daryl Malas <D.Malas@cablelabs.com>
To: "speermint@ietf.org" <speermint@ietf.org>
Date: Thu, 21 Jan 2010 09:52:41 -0700
Thread-Topic: [Speermint] FW: 77th IETF - Registration Information 
Thread-Index: AcqZXKnS6dJV17FfR7GPlnF1mmDU6gBXV3JQ
Message-ID: <114DAD31379DFA438C0A2E39B3B8AF5D011FE81D63@srvxchg>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Approved: ondar
Subject: [Speermint]  FW: 77th IETF - Registration Information
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: Thu, 21 Jan 2010 16:52:46 -0000

FYI...

-----Original Message-----
Subject: 77th IETF - Registration Information=20

77th IETF Meeting
Anaheim, CA, USA
March 21-26, 2010

Registration is now open!

Register online at: http://www.ietf.org/meetings/77/

1.  Registration Types
2.  Visas and Letters of Invitation
3.  Accommodations & Breakfast Information

1) Registration Types

A. Early-Bird Registration - USD 635.00
Register and pay before Friday, 12 March 2010 at 17:00 PST (24:00
UTC) for Early-Bird rate.

B. After Early-Bird cutoff - USD 785.00
=09
C. Full-time Student Registrations - USD 150.00 Full-time students with pro=
per ID are eligible to receive a special USD 150.00 student rate. Student r=
ate is not subject to any late-fees.
Students will also be able to register on-site at the special student rate.=
 Failure to provide valid student ID on-site will revoke the special studen=
t status.

D. One Day Pass Registration - USD 200.00 We are once again offering a one-=
day pass for $200. Benefits are:

1. Attend all sessions during any one day of the Meeting, and partake of th=
e food and beverage during the breaks 2. You select which day to attend whe=
n you show up onsite to check-in 3. Payments may be made onsite without a l=
ate fee 4. Pass can be upgraded to a full Meeting Registration, however, la=
te fee may apply if initial one-day payment not made before Early Bird dead=
line 5. Attend Sunday Tutorials at no additional charge 6. Attend Sunday We=
lcome Reception at no additional charge 7. Attend Wednesday and Thursday Pl=
enaries at no additional charge
=09
CANCELLATION
The cut-off for registration cancellation is Monday, 15 March 2010 at 17:00=
 PT (01:00 Tuesday, March 16 UTC). Cancellations are subject to a 10% (ten =
percent) cancellation fee.

Online Registration ends: Friday, 19 March, 2010 at 17:00 PT (24:00 UTC)

On-site Registration
You can register onsite at the meeting in Anaheim, CA, USA starting Sunday,=
 21 March 2010 at 12:00 noon PT.

Meeting Schedule: Start Monday morning and run through Friday at 15:15 loca=
l time. Most training sessions will take place on Sunday afternoon 21 March=
 2010. Participants should plan their travel accordingly.

2) Letters of Invitation and Visas

Letters of Invitation
After you complete the meeting registration process, you will be given the =
option to request an IETF letter of invitation.=20

Visas
We recommend you allocate at least one month to complete the visa process.
See here for more information on the visa application process:=20
https://esta.cbp.dhs.gov

The following countries participate in the Visa Waiver Program (as of Decem=
ber 30, 2008):
Andorra, Australia, Austria, Belgium, Brunei, Czech Republic, Denmark, Esto=
nia, Finland, France, Germany, Hungary, Iceland, Ireland, Italy, Japan, Lat=
via, Liechtenstein, Lithuania, Luxembourg, Malta, Monaco, the Netherlands, =
New Zealand, Norway, Portugal, San Marino, Singapore, Slovakia, Slovenia, S=
outh Korea, Spain, Sweden, Switzerland, and the United Kingdom

Applications may be submitted at any time prior to travel to the United Sta=
tes.  The Department of Homeland Security recommends that travel authorizat=
ion applications be submitted at least 72 hours prior to travel.
Unless revoked, travel authorizations are valid for two years from the date=
 of authorization, or until your passport expires, whichever comes first.

You can update the following information at https://esta.cbp.dhs.gov once y=
ou have received approval:
- Email address
- Telephone number
- Airline and flight number
- City where you are boarding
- Address while in the United States

3) Accommodations & Breakfast Information The IETF has a sleeping room bloc=
k at the main IETF 77 meeting venue: the Hilton Anaheim.  Room rate is $194=
 USD single and $214 USD double plus 15% per room per night and $1.15 USD p=
er room per night tax. More information about the hotel can be found here:
http://www.ietf.org/meeting/77/hotel.html.
Breakfast will be provided as part of the on-site meeting services.

Only 61 days until IETF 77!


From pp3129@att.com  Thu Jan 21 13:14:08 2010
Return-Path: <pp3129@att.com>
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 231103A67AF for <speermint@core3.amsl.com>; Thu, 21 Jan 2010 13:14:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.935
X-Spam-Level: 
X-Spam-Status: No, score=-105.935 tagged_above=-999 required=5 tests=[AWL=0.664, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MdhJmJcOfaue for <speermint@core3.amsl.com>; Thu, 21 Jan 2010 13:13:59 -0800 (PST)
Received: from mail146.messagelabs.com (mail146.messagelabs.com [216.82.241.147]) by core3.amsl.com (Postfix) with ESMTP id 3B7293A68B2 for <speermint@ietf.org>; Thu, 21 Jan 2010 13:13:49 -0800 (PST)
X-VirusChecked: Checked
X-Env-Sender: pp3129@att.com
X-Msg-Ref: server-4.tower-146.messagelabs.com!1264108420!18167083!1
X-StarScan-Version: 6.2.4; banners=-,-,-
X-Originating-IP: [144.160.20.146]
Received: (qmail 30271 invoked from network); 21 Jan 2010 21:13:41 -0000
Received: from sbcsmtp7.sbc.com (HELO mlpd194.enaf.sfdc.sbc.com) (144.160.20.146) by server-4.tower-146.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 21 Jan 2010 21:13:41 -0000
Received: from enaf.sfdc.sbc.com (localhost.localdomain [127.0.0.1]) by mlpd194.enaf.sfdc.sbc.com (8.14.3/8.14.3) with ESMTP id o0LLDcti027450 for <speermint@ietf.org>; Thu, 21 Jan 2010 16:13:38 -0500
Received: from gaalpa1msgusr7a.ugd.att.com (gaalpa1msgusr7a.ugd.att.com [135.53.26.15]) by mlpd194.enaf.sfdc.sbc.com (8.14.3/8.14.3) with ESMTP id o0LLDWKs027375 for <speermint@ietf.org>; Thu, 21 Jan 2010 16:13:32 -0500
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: Thu, 21 Jan 2010 16:13:37 -0500
Message-ID: <35FE871E2B085542A35726420E29DA6B032CED2F@gaalpa1msgusr7a.ugd.att.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Speermint] Review of architecture-09
Thread-Index: AcqZ5nxHqIjcYwo9R/qmhsehs9q+ZwAshGJgABF7K9A=
References: <4B5722E1.4090101@enum.at> 
From: "PFAUTZ, PENN L (ATTCORP)" <pp3129@att.com>
To: <speermint@ietf.org>
Subject: Re: [Speermint] Review of architecture-09
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: Thu, 21 Jan 2010 21:14:08 -0000

I have a problem with Section 4.1.1.2 which implies that an ENUM look up
is necessarily of a public End User ENUM record. This was not originally
the case and I'm not sure what the rationale is for eliminating other
options. This is particularly so since the Public End User tree is
pretty sparse at this point (to say the least) while various parties are
already using private trees and several efforts are underway to
construct potentially wide ranging infrastructure ENUM trees.=20

I suggest rewriting the first sentence to read

If an external E.164 address is the target, the originating SSP consults
an ENUM registry, which could be the
   public "User ENUM" rooted at e164.arpa, according to the procedures
described
   in RFC 3761. Alternatively, the originating SSP may consult an
infrastructure ENUM registry (see RFC 5067) or a private registry to
identify to the=20
   carrier of record.

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



From D.Malas@cablelabs.com  Fri Jan 22 10:11:24 2010
Return-Path: <D.Malas@cablelabs.com>
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 9B3EF28C0EE for <speermint@core3.amsl.com>; Fri, 22 Jan 2010 10:11:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.603
X-Spam-Level: 
X-Spam-Status: No, score=-0.603 tagged_above=-999 required=5 tests=[AWL=-0.140, 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 d1bh9keCg-FK for <speermint@core3.amsl.com>; Fri, 22 Jan 2010 10:11:23 -0800 (PST)
Received: from ondar.cablelabs.com (ondar.cablelabs.com [192.160.73.61]) by core3.amsl.com (Postfix) with ESMTP id 93A4928C129 for <speermint@ietf.org>; Fri, 22 Jan 2010 10:10:53 -0800 (PST)
Received: from kyzyl.cablelabs.com (kyzyl [10.253.0.7]) by ondar.cablelabs.com (8.14.3/8.14.3) with ESMTP id o0MIAmKR015999 for <speermint@ietf.org>; Fri, 22 Jan 2010 11:10:48 -0700
Received: from srvxchg.cablelabs.com (10.5.0.15) by kyzyl.cablelabs.com (F-Secure/fsigk_smtp/303/kyzyl.cablelabs.com); Fri, 22 Jan 2010 11:10:48 -0700 (MST)
X-Virus-Status: clean(F-Secure/fsigk_smtp/303/kyzyl.cablelabs.com)
Received: from srvxchg.cablelabs.com ([10.5.0.15]) by srvxchg ([10.5.0.15]) with mapi; Fri, 22 Jan 2010 11:10:48 -0700
From: Daryl Malas <D.Malas@cablelabs.com>
To: "speermint@ietf.org" <speermint@ietf.org>
Date: Fri, 22 Jan 2010 11:10:47 -0700
Thread-Topic: [Speermint] RE:**Last Call** on the Speermint Peering Architecturedraft
Thread-Index: AcqPujZ1COYZ76qwS0GixqlM0TUH4AAx8lVAAideTHAAm5uqMA==
Message-ID: <114DAD31379DFA438C0A2E39B3B8AF5D011FE81D78@srvxchg>
References: <160DE07A1C4F8E4AA2715DEC577DA4910119108D@srvxchg3.cablelabs.com> <160DE07A1C4F8E4AA2715DEC577DA491011910AC@srvxchg3.cablelabs.com> <114DAD31379DFA438C0A2E39B3B8AF5D011CBBA685@srvxchg.cablelabs.com>
In-Reply-To: <114DAD31379DFA438C0A2E39B3B8AF5D011CBBA685@srvxchg.cablelabs.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Approved: ondar
Subject: [Speermint] RE:**Last Call** on the Speermint Peering Architecturedraft
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: Fri, 22 Jan 2010 18:11:25 -0000

All,

As a final reminder, the "Last Call" on the Speermint Peering Architecture =
draft ends today.  Thank you to those who have already submitted feedback o=
n the draft, as this greatly helps the authors in improving it.  Once we re=
ceive any additional comments today, we will begin working to update the dr=
aft.

Best Regards,

Daryl

-----Original Message-----
From: speermint-bounces@ietf.org [mailto:speermint-bounces@ietf.org] On Beh=
alf Of Daryl Malas
Sent: Tuesday, January 19, 2010 8:54 AM
To: speermint@ietf.org
Subject: [Speermint] RE:**Last Call** on the Speermint Peering Architecture=
draft

All,

This is just a reminder the "Last Call" on the Speermint Peering Architectu=
re draft ends this Friday, January 22nd.  Please review and post comments t=
o the mailing list soon.

Regards,

Daryl
Speermint Chairs

-----Original Message-----
From: speermint-bounces@ietf.org [mailto:speermint-bounces@ietf.org] On Beh=
alf Of Daryl Malas
Sent: Friday, January 08, 2010 9:47 AM
To: speermint@ietf.org
Subject: [Speermint] RE:**Last Call** on the Speermint Peering Architecture=
draft

All,

With the understanding it may be challenging for some to schedule the time =
to review and provide comments in 1 week, the "Last Call" is extended to Ja=
nuary 22nd.

Regards,

Daryl

-----Original Message-----
From: speermint-bounces@ietf.org [mailto:speermint-bounces@ietf.org] On Beh=
alf Of Daryl Malas
Sent: Thursday, January 07, 2010 9:55 AM
To: speermint@ietf.org
Subject: [Speermint] **Last Call** on the Speermint Peering Architecturedra=
ft

All,
=20
We discussed this during our last meeting, but I wanted to officially note =
it on the mailing list.  Please provide any final comments on the Speermint=
 Peering Architecture draft.  This last call will last approximately 1 week=
 and end on January 15th.

Here is a link to the draft:
http://tools.ietf.org/html/draft-ietf-speermint-architecture-09

Adam,

Please review and begin correction of the nits here:
http://tools.ietf.org/idnits?url=3Dhttp://tools.ietf.org/id/draft-ietf-spe
ermint-architecture-09.txt.

We would like to wrap up this draft quickly, so everyone's effort to review=
 and provide and final feedback is greatly appreciated.

Regards,

Daryl
_______________________________________________
Speermint mailing list
Speermint@ietf.org
https://www.ietf.org/mailman/listinfo/speermint
_______________________________________________
Speermint mailing list
Speermint@ietf.org
https://www.ietf.org/mailman/listinfo/speermint
_______________________________________________
Speermint mailing list
Speermint@ietf.org
https://www.ietf.org/mailman/listinfo/speermint

From hmmr@cisco.com  Fri Jan 22 12:47:42 2010
Return-Path: <hmmr@cisco.com>
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 1653A3A67EE for <speermint@core3.amsl.com>; Fri, 22 Jan 2010 12:47:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 QtU42UZNmhuf for <speermint@core3.amsl.com>; Fri, 22 Jan 2010 12:47:41 -0800 (PST)
Received: from sj-iport-5.cisco.com (sj-iport-5.cisco.com [171.68.10.87]) by core3.amsl.com (Postfix) with ESMTP id F40A83A685D for <speermint@ietf.org>; Fri, 22 Jan 2010 12:47:40 -0800 (PST)
Authentication-Results: sj-iport-5.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ApoEAM+dWUurRN+K/2dsb2JhbADCKJY1hDwE
X-IronPort-AV: E=Sophos;i="4.49,326,1262563200"; d="scan'208";a="138363354"
Received: from sj-core-4.cisco.com ([171.68.223.138]) by sj-iport-5.cisco.com with ESMTP; 22 Jan 2010 20:47:37 +0000
Received: from xbh-rcd-101.cisco.com (xbh-rcd-101.cisco.com [72.163.62.138]) by sj-core-4.cisco.com (8.13.8/8.14.3) with ESMTP id o0MKlaW0009104; Fri, 22 Jan 2010 20:47:36 GMT
Received: from xmb-rcd-111.cisco.com ([72.163.62.153]) by xbh-rcd-101.cisco.com with Microsoft SMTPSVC(6.0.3790.3959);  Fri, 22 Jan 2010 14:47:36 -0600
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: Fri, 22 Jan 2010 14:47:34 -0600
Message-ID: <C4064AF1C9EC1F40868C033DB94958C7A3186F@XMB-RCD-111.cisco.com>
In-Reply-To: <114DAD31379DFA438C0A2E39B3B8AF5D011FE81D78@srvxchg>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Speermint] RE:**Last Call** on the Speermint Peering Architecturedraft
Thread-Index: AcqPujZ1COYZ76qwS0GixqlM0TUH4AAx8lVAAideTHAAm5uqMAAEtWkg
References: <160DE07A1C4F8E4AA2715DEC577DA4910119108D@srvxchg3.cablelabs.com><160DE07A1C4F8E4AA2715DEC577DA491011910AC@srvxchg3.cablelabs.com><114DAD31379DFA438C0A2E39B3B8AF5D011CBBA685@srvxchg.cablelabs.com> <114DAD31379DFA438C0A2E39B3B8AF5D011FE81D78@srvxchg>
From: "Mike Hammer (hmmr)" <hmmr@cisco.com>
To: "Daryl Malas" <D.Malas@cablelabs.com>, <speermint@ietf.org>
X-OriginalArrivalTime: 22 Jan 2010 20:47:36.0802 (UTC) FILETIME=[213C4420:01CA9BA4]
Subject: Re: [Speermint] **Last Call** on the Speermint Peering Architecturedraft
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: Fri, 22 Jan 2010 20:47:42 -0000

Daryl,

Two problems:

1)  The SBE to SF, LUF, and LRF relationship is convoluted and circular
(can iterate endlessly).
2)  You reference the SF throughout, but do not show it in the diagram.

My proposal is to change the figure 1 as follows.
Note, you can collapse the inner boundary of SBE, DBE, and SSP to be a
single edge if you want.

             +----------------+
+---------------+
            /                  \                       /
\
           |   +-----SBE---+   |                      |    +---SBE-----+
|
           |  /             \  |                      |   /
\ |
           | |     +--LUF-+ |  |       +------+       |   | +--LUF-+
| |
           | |  |->|      | |  |       | ENUM |       |   | |      |<-|
| |
           | |  |  |      +----------->| TN DB|<------------+      |  |
| |
           | |  |  |      | |  |       +------+       |   | |      |  |
| |
           | |  |  +------+ |  |                      |   | +------+  |
| |
           | |  |           |  |                      |   |           |
| |
           | |  |  +--LRF-+ |  |      +--------+      |   | +--LRF-+  |
| |
           | |  |->|      | |  |      | DNS    |      |   | |      |<-|
| |
           | |  |  |      +---------->|IP Addrs|<-----------+      |  |
| |
           | |  |  |      | |  |      +--------+      |   | |      |  |
| |
           | |  |  +------+ |  |                      |   | +------+  |
| |
           | |  |           |  |                      |   |           |
| |
           | |  |  +------+ |  |                      |   | +------+  |
| |
           | |  |->|      | |  |                      |   | |      |<-|
| |
           | |     |  SF  |<------------------------------->|  SF  |
| |
           | |     |      | |  |                      |   | |      |
| |
           | |     +------+ |  |                      |   | +------+
| |
           |  \       |     /  |                      |    \    |      /
|
           |   +------|----+   |                      |     +---|-----+
|
           |      +-------+    |                      |     +-------+
|
           |      |       |    |                      |     |       |
|
           | SSP1 |  DBE  |<------------------------------->|  DBE  |
SSP2|
           |      |       |    |                      |     |       |
|
           |      +-------+    |                      |     +-------+
|
            \                 /                        \
/
             +---------------+
+---------------+
                  Figure 1: Reference SPEERMINT Architecture

Thanks,
Mike




> -----Original Message-----
> From: speermint-bounces@ietf.org [mailto:speermint-bounces@ietf.org]
On
> Behalf Of Daryl Malas
> Sent: Friday, January 22, 2010 1:11 PM
> To: speermint@ietf.org
> Subject: [Speermint] RE:**Last Call** on the Speermint Peering
> Architecturedraft
>=20
> All,
>=20
> As a final reminder, the "Last Call" on the Speermint Peering
Architecture
> draft ends today.  Thank you to those who have already submitted
feedback
> on the draft, as this greatly helps the authors in improving it.  Once
we
> receive any additional comments today, we will begin working to update
the
> draft.
>=20
> Best Regards,
>=20
> Daryl
>=20
> -----Original Message-----
> From: speermint-bounces@ietf.org [mailto:speermint-bounces@ietf.org]
On
> Behalf Of Daryl Malas
> Sent: Tuesday, January 19, 2010 8:54 AM
> To: speermint@ietf.org
> Subject: [Speermint] RE:**Last Call** on the Speermint Peering
> Architecturedraft
>=20
> All,
>=20
> This is just a reminder the "Last Call" on the Speermint Peering
> Architecture draft ends this Friday, January 22nd.  Please review and
post
> comments to the mailing list soon.
>=20
> Regards,
>=20
> Daryl
> Speermint Chairs
>=20
> -----Original Message-----
> From: speermint-bounces@ietf.org [mailto:speermint-bounces@ietf.org]
On
> Behalf Of Daryl Malas
> Sent: Friday, January 08, 2010 9:47 AM
> To: speermint@ietf.org
> Subject: [Speermint] RE:**Last Call** on the Speermint Peering
> Architecturedraft
>=20
> All,
>=20
> With the understanding it may be challenging for some to schedule the
time
> to review and provide comments in 1 week, the "Last Call" is extended
to
> January 22nd.
>=20
> Regards,
>=20
> Daryl
>=20
> -----Original Message-----
> From: speermint-bounces@ietf.org [mailto:speermint-bounces@ietf.org]
On
> Behalf Of Daryl Malas
> Sent: Thursday, January 07, 2010 9:55 AM
> To: speermint@ietf.org
> Subject: [Speermint] **Last Call** on the Speermint Peering
> Architecturedraft
>=20
> All,
>=20
> We discussed this during our last meeting, but I wanted to officially
note
> it on the mailing list.  Please provide any final comments on the
> Speermint Peering Architecture draft.  This last call will last
> approximately 1 week and end on January 15th.
>=20
> Here is a link to the draft:
> http://tools.ietf.org/html/draft-ietf-speermint-architecture-09
>=20
> Adam,
>=20
> Please review and begin correction of the nits here:
>
http://tools.ietf.org/idnits?url=3Dhttp://tools.ietf.org/id/draft-ietf-sp=
e
> ermint-architecture-09.txt.
>=20
> We would like to wrap up this draft quickly, so everyone's effort to
> review and provide and final feedback is greatly appreciated.
>=20
> Regards,
>=20
> Daryl
> _______________________________________________
> Speermint mailing list
> Speermint@ietf.org
> https://www.ietf.org/mailman/listinfo/speermint
> _______________________________________________
> Speermint mailing list
> Speermint@ietf.org
> https://www.ietf.org/mailman/listinfo/speermint
> _______________________________________________
> Speermint mailing list
> Speermint@ietf.org
> https://www.ietf.org/mailman/listinfo/speermint
> _______________________________________________
> Speermint mailing list
> Speermint@ietf.org
> https://www.ietf.org/mailman/listinfo/speermint

From hmmr@cisco.com  Fri Jan 22 12:52:35 2010
Return-Path: <hmmr@cisco.com>
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 6672A3A6782 for <speermint@core3.amsl.com>; Fri, 22 Jan 2010 12:52:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 P0cEm7jKJ8yA for <speermint@core3.amsl.com>; Fri, 22 Jan 2010 12:52:33 -0800 (PST)
Received: from sj-iport-5.cisco.com (sj-iport-5.cisco.com [171.68.10.87]) by core3.amsl.com (Postfix) with ESMTP id AB80A3A6778 for <speermint@ietf.org>; Fri, 22 Jan 2010 12:52:33 -0800 (PST)
Authentication-Results: sj-iport-5.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ApoEAAafWUurRN+J/2dsb2JhbADCLZY3hDwE
X-IronPort-AV: E=Sophos;i="4.49,326,1262563200"; d="scan'208";a="138367073"
Received: from sj-core-3.cisco.com ([171.68.223.137]) by sj-iport-5.cisco.com with ESMTP; 22 Jan 2010 20:52:23 +0000
Received: from xbh-rcd-202.cisco.com (xbh-rcd-202.cisco.com [72.163.62.201]) by sj-core-3.cisco.com (8.13.8/8.14.3) with ESMTP id o0MKqBG4016445; Fri, 22 Jan 2010 20:52:23 GMT
Received: from xmb-rcd-111.cisco.com ([72.163.62.153]) by xbh-rcd-202.cisco.com with Microsoft SMTPSVC(6.0.3790.3959);  Fri, 22 Jan 2010 14:52:11 -0600
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: Fri, 22 Jan 2010 14:52:10 -0600
Message-ID: <C4064AF1C9EC1F40868C033DB94958C7A31878@XMB-RCD-111.cisco.com>
In-Reply-To: <C4064AF1C9EC1F40868C033DB94958C7A3186F@XMB-RCD-111.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Speermint] **Last Call** on the Speermint PeeringArchitecturedraft
Thread-Index: AcqPujZ1COYZ76qwS0GixqlM0TUH4AAx8lVAAideTHAAm5uqMAAEtWkgAADuQIA=
References: <160DE07A1C4F8E4AA2715DEC577DA4910119108D@srvxchg3.cablelabs.com><160DE07A1C4F8E4AA2715DEC577DA491011910AC@srvxchg3.cablelabs.com><114DAD31379DFA438C0A2E39B3B8AF5D011CBBA685@srvxchg.cablelabs.com><114DAD31379DFA438C0A2E39B3B8AF5D011FE81D78@srvxchg> <C4064AF1C9EC1F40868C033DB94958C7A3186F@XMB-RCD-111.cisco.com>
From: "Mike Hammer (hmmr)" <hmmr@cisco.com>
To: "Mike Hammer (hmmr)" <hmmr@cisco.com>, "Daryl Malas" <D.Malas@cablelabs.com>, <speermint@ietf.org>
X-OriginalArrivalTime: 22 Jan 2010 20:52:11.0865 (UTC) FILETIME=[C52F8C90:01CA9BA4]
Subject: Re: [Speermint] **Last Call** on the Speermint PeeringArchitecturedraft
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: Fri, 22 Jan 2010 20:52:35 -0000

All,

This txt art is messed up.  Seems like a lot of extra CR were injected.
But, hopefully you can see that the essence is:

SSP is composed of SBE and DBE.

SBE is composed of LUF, LRF, and SF.

Mike


> -----Original Message-----
> From: speermint-bounces@ietf.org [mailto:speermint-bounces@ietf.org]
On
> Behalf Of Mike Hammer (hmmr)
> Sent: Friday, January 22, 2010 3:48 PM
> To: Daryl Malas; speermint@ietf.org
> Subject: Re: [Speermint] **Last Call** on the Speermint
> PeeringArchitecturedraft
>=20
> Daryl,
>=20
> Two problems:
>=20
> 1)  The SBE to SF, LUF, and LRF relationship is convoluted and
circular
> (can iterate endlessly).
> 2)  You reference the SF throughout, but do not show it in the
diagram.
>=20
> My proposal is to change the figure 1 as follows.
> Note, you can collapse the inner boundary of SBE, DBE, and SSP to be a
> single edge if you want.
>=20
>              +----------------+
> +---------------+
>             /                  \                       /
> \
>            |   +-----SBE---+   |                      |
+---SBE-----+
> |
>            |  /             \  |                      |   /
> \ |
>            | |     +--LUF-+ |  |       +------+       |   | +--LUF-+
> | |
>            | |  |->|      | |  |       | ENUM |       |   | |
|<-|
> | |
>            | |  |  |      +----------->| TN DB|<------------+      |
|
> | |
>            | |  |  |      | |  |       +------+       |   | |      |
|
> | |
>            | |  |  +------+ |  |                      |   | +------+
|
> | |
>            | |  |           |  |                      |   |
|
> | |
>            | |  |  +--LRF-+ |  |      +--------+      |   | +--LRF-+
|
> | |
>            | |  |->|      | |  |      | DNS    |      |   | |
|<-|
> | |
>            | |  |  |      +---------->|IP Addrs|<-----------+      |
|
> | |
>            | |  |  |      | |  |      +--------+      |   | |      |
|
> | |
>            | |  |  +------+ |  |                      |   | +------+
|
> | |
>            | |  |           |  |                      |   |
|
> | |
>            | |  |  +------+ |  |                      |   | +------+
|
> | |
>            | |  |->|      | |  |                      |   | |
|<-|
> | |
>            | |     |  SF  |<------------------------------->|  SF  |
> | |
>            | |     |      | |  |                      |   | |      |
> | |
>            | |     +------+ |  |                      |   | +------+
> | |
>            |  \       |     /  |                      |    \    |
/
> |
>            |   +------|----+   |                      |
+---|-----+
> |
>            |      +-------+    |                      |     +-------+
> |
>            |      |       |    |                      |     |       |
> |
>            | SSP1 |  DBE  |<------------------------------->|  DBE  |
> SSP2|
>            |      |       |    |                      |     |       |
> |
>            |      +-------+    |                      |     +-------+
> |
>             \                 /                        \
> /
>              +---------------+
> +---------------+
>                   Figure 1: Reference SPEERMINT Architecture
>=20
> Thanks,
> Mike
>=20
>=20
>=20
>=20
> > -----Original Message-----
> > From: speermint-bounces@ietf.org [mailto:speermint-bounces@ietf.org]
> On
> > Behalf Of Daryl Malas
> > Sent: Friday, January 22, 2010 1:11 PM
> > To: speermint@ietf.org
> > Subject: [Speermint] RE:**Last Call** on the Speermint Peering
> > Architecturedraft
> >
> > All,
> >
> > As a final reminder, the "Last Call" on the Speermint Peering
> Architecture
> > draft ends today.  Thank you to those who have already submitted
> feedback
> > on the draft, as this greatly helps the authors in improving it.
Once
> we
> > receive any additional comments today, we will begin working to
update
> the
> > draft.
> >
> > Best Regards,
> >
> > Daryl
> >
> > -----Original Message-----
> > From: speermint-bounces@ietf.org [mailto:speermint-bounces@ietf.org]
> On
> > Behalf Of Daryl Malas
> > Sent: Tuesday, January 19, 2010 8:54 AM
> > To: speermint@ietf.org
> > Subject: [Speermint] RE:**Last Call** on the Speermint Peering
> > Architecturedraft
> >
> > All,
> >
> > This is just a reminder the "Last Call" on the Speermint Peering
> > Architecture draft ends this Friday, January 22nd.  Please review
and
> post
> > comments to the mailing list soon.
> >
> > Regards,
> >
> > Daryl
> > Speermint Chairs
> >
> > -----Original Message-----
> > From: speermint-bounces@ietf.org [mailto:speermint-bounces@ietf.org]
> On
> > Behalf Of Daryl Malas
> > Sent: Friday, January 08, 2010 9:47 AM
> > To: speermint@ietf.org
> > Subject: [Speermint] RE:**Last Call** on the Speermint Peering
> > Architecturedraft
> >
> > All,
> >
> > With the understanding it may be challenging for some to schedule
the
> time
> > to review and provide comments in 1 week, the "Last Call" is
extended
> to
> > January 22nd.
> >
> > Regards,
> >
> > Daryl
> >
> > -----Original Message-----
> > From: speermint-bounces@ietf.org [mailto:speermint-bounces@ietf.org]
> On
> > Behalf Of Daryl Malas
> > Sent: Thursday, January 07, 2010 9:55 AM
> > To: speermint@ietf.org
> > Subject: [Speermint] **Last Call** on the Speermint Peering
> > Architecturedraft
> >
> > All,
> >
> > We discussed this during our last meeting, but I wanted to
officially
> note
> > it on the mailing list.  Please provide any final comments on the
> > Speermint Peering Architecture draft.  This last call will last
> > approximately 1 week and end on January 15th.
> >
> > Here is a link to the draft:
> > http://tools.ietf.org/html/draft-ietf-speermint-architecture-09
> >
> > Adam,
> >
> > Please review and begin correction of the nits here:
> >
>
http://tools.ietf.org/idnits?url=3Dhttp://tools.ietf.org/id/draft-ietf-sp=
e
> > ermint-architecture-09.txt.
> >
> > We would like to wrap up this draft quickly, so everyone's effort to
> > review and provide and final feedback is greatly appreciated.
> >
> > Regards,
> >
> > Daryl
> > _______________________________________________
> > Speermint mailing list
> > Speermint@ietf.org
> > https://www.ietf.org/mailman/listinfo/speermint
> > _______________________________________________
> > Speermint mailing list
> > Speermint@ietf.org
> > https://www.ietf.org/mailman/listinfo/speermint
> > _______________________________________________
> > Speermint mailing list
> > Speermint@ietf.org
> > https://www.ietf.org/mailman/listinfo/speermint
> > _______________________________________________
> > Speermint mailing list
> > Speermint@ietf.org
> > https://www.ietf.org/mailman/listinfo/speermint
> _______________________________________________
> Speermint mailing list
> Speermint@ietf.org
> https://www.ietf.org/mailman/listinfo/speermint
