From speermint-bounces@ietf.org  Thu Jun  5 12:44:25 2008
Return-Path: <speermint-bounces@ietf.org>
X-Original-To: speermint-archive@megatron.ietf.org
Delivered-To: ietfarch-speermint-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 2F5EF3A69CD;
	Thu,  5 Jun 2008 12:44:25 -0700 (PDT)
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 0E9B73A6B62
	for <speermint@core3.amsl.com>; Thu,  5 Jun 2008 12:44:24 -0700 (PDT)
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 irIW4qFTVrVA for <speermint@core3.amsl.com>;
	Thu,  5 Jun 2008 12:44:23 -0700 (PDT)
Received: from paoakoavas09.cable.comcast.com (paoakoavas09.cable.comcast.com
	[208.17.35.58]) by core3.amsl.com (Postfix) with ESMTP id B400A3A6A04
	for <speermint@ietf.org>; Thu,  5 Jun 2008 12:44:22 -0700 (PDT)
Received: from ([10.52.116.30])
	by paoakoavas09.cable.comcast.com with ESMTP  id KP-NTF18.56156711;
	Thu, 05 Jun 2008 15:44:06 -0400
Received: from PACDCEXCMB04.cable.comcast.com ([24.40.15.86]) by
	PAOAKEXCSMTP01.cable.comcast.com with Microsoft
	SMTPSVC(6.0.3790.3959); Thu, 5 Jun 2008 15:44:06 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Thu, 5 Jun 2008 15:44:06 -0400
Message-ID: <45AEC6EF95942140888406588E1A660204FE25FA@PACDCEXCMB04.cable.comcast.com>
In-Reply-To: <20080502180002.05E533A6C10@core3.amsl.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Any More Comments /
	Changes:draft-ietf-speermint-architecture-06.txt
Thread-Index: Acisfm30V4AzWGgDSv+5EYHgCsjLPAaxce8g
References: <20080502180002.05E533A6C10@core3.amsl.com>
From: "Livingood, Jason" <Jason_Livingood@cable.comcast.com>
To: <speermint@ietf.org>
X-OriginalArrivalTime: 05 Jun 2008 19:44:06.0497 (UTC)
	FILETIME=[83EADD10:01C8C744]
Subject: [Speermint] Any More Comments /
	Changes:draft-ietf-speermint-architecture-06.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/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: speermint-bounces@ietf.org
Errors-To: speermint-bounces@ietf.org

All --

We have not received many comments on this draft and we'd like to
continue to make progress with it.  Comments in the next couple of weeks
are appreciated so that we can review a very stable document at IETF-72.

Thanks
Jason 

> -----Original Message-----
> From: speermint-bounces@ietf.org 
> [mailto:speermint-bounces@ietf.org] On Behalf Of 
> Internet-Drafts@ietf.org
> Sent: Friday, May 02, 2008 2:00 PM
> To: i-d-announce@ietf.org
> Cc: speermint@ietf.org
> Subject: [Speermint] I-D 
> ACTION:draft-ietf-speermint-architecture-06.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		: SPEERMINT Peering Architecture
> 	Author(s)	: R. Penno
> 	Filename	: draft-ietf-speermint-architecture-06.txt
> 	Pages		: 21
> 	Date		: 2008-5-2
> 	
> This document defines the SPEERMINT peering architecture, its
>   functional components and peering interface functions. It also 
>   describes the steps taken to establish a session between 
> two peering   
>   domains in the context of the functions defined.
> 
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-speermint-archi
> tecture-06.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


From speermint-bounces@ietf.org  Thu Jun  5 12:52:06 2008
Return-Path: <speermint-bounces@ietf.org>
X-Original-To: speermint-archive@megatron.ietf.org
Delivered-To: ietfarch-speermint-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 0C2B23A6CDC;
	Thu,  5 Jun 2008 12:52:06 -0700 (PDT)
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 E29CA3A6CC9
	for <speermint@core3.amsl.com>; Thu,  5 Jun 2008 12:52:04 -0700 (PDT)
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 29vi-KpnhUyZ for <speermint@core3.amsl.com>;
	Thu,  5 Jun 2008 12:52:01 -0700 (PDT)
Received: from paoakoavas10.cable.comcast.com (paoakoavas10.cable.comcast.com
	[208.17.35.59]) by core3.amsl.com (Postfix) with ESMTP id A93E83A693B
	for <speermint@ietf.org>; Thu,  5 Jun 2008 12:52:00 -0700 (PDT)
Received: from ([10.52.116.31])
	by paoakoavas10.cable.comcast.com with ESMTP  id KP-TDCH7.46547421;
	Thu, 05 Jun 2008 15:51:45 -0400
Received: from PACDCEXCMB04.cable.comcast.com ([24.40.15.86]) by
	PAOAKEXCSMTP02.cable.comcast.com with Microsoft
	SMTPSVC(6.0.3790.3959); Thu, 5 Jun 2008 15:51:44 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Thu, 5 Jun 2008 15:51:44 -0400
Message-ID: <45AEC6EF95942140888406588E1A660204FE2603@PACDCEXCMB04.cable.comcast.com>
In-Reply-To: <20080530013001.A2A5928C0E4@core3.amsl.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: WGLC #2: draft-ietf-speermint-voip-consolidated-usecases-08.txt
Thread-Index: AcjB9MC8SHUzVMTnTuqEC0MuWzIEeQFT/Vwg
References: <20080530013001.A2A5928C0E4@core3.amsl.com>
From: "Livingood, Jason" <Jason_Livingood@cable.comcast.com>
To: <speermint@ietf.org>
X-OriginalArrivalTime: 05 Jun 2008 19:51:44.0808 (UTC)
	FILETIME=[95179280:01C8C745]
Subject: [Speermint] WGLC #2:
	draft-ietf-speermint-voip-consolidated-usecases-08.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/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: speermint-bounces@ietf.org
Errors-To: speermint-bounces@ietf.org

There were a few changes made from -07 so I would like to extend last
call a bit longer.

The intent of the last call is to solicit comments before submitting the
ID to the IESG.

The purpose of a working group last call is in the style of "speak now
or forever hold your peace" in case there are fundamental objections
which have not gotten previous or adequate discussion, or minor errors
which need correction.

The extended working group last call will extend for 1 week from today,
5 June 2008, until 13 June 2008.

Please post any comments in reply to the list, as well as to the
editor(s) of this draft.

Regards,

Jason  

> -----Original Message-----
> From: speermint-bounces@ietf.org 
> [mailto:speermint-bounces@ietf.org] On Behalf Of 
> Internet-Drafts@ietf.org
> Sent: Thursday, May 29, 2008 9:30 PM
> To: i-d-announce@ietf.org
> Cc: speermint@ietf.org
> Subject: [Speermint] I-D 
> Action:draft-ietf-speermint-voip-consolidated-usecases-08.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-08.txt
> 	Pages           : 26
> 	Date            : 2008-05-29
> 
> This document depicts many common VoIP use case for 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.  This document captures 
> them to provide a reference.
> 
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-speermint-voip-
> consolidated-usecases-08.txt
> 
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
> 
> Below is the data which will enable a MIME compliant mail 
> reader implementation to automatically retrieve the ASCII 
> version of the Internet-Draft.
> 
_______________________________________________
Speermint mailing list
Speermint@ietf.org
https://www.ietf.org/mailman/listinfo/speermint


From speermint-bounces@ietf.org  Mon Jun 16 08:08:29 2008
Return-Path: <speermint-bounces@ietf.org>
X-Original-To: speermint-archive@megatron.ietf.org
Delivered-To: ietfarch-speermint-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 0BFB93A68CF;
	Mon, 16 Jun 2008 08:08:29 -0700 (PDT)
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 8EB6A3A68CF
	for <speermint@core3.amsl.com>; Mon, 16 Jun 2008 08:08:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 0zx3ZCCUejbS for <speermint@core3.amsl.com>;
	Mon, 16 Jun 2008 08:08:27 -0700 (PDT)
Received: from kahua.nona.net (pahula.nona.net [193.80.224.123])
	by core3.amsl.com (Postfix) with ESMTP id 994C73A682A
	for <speermint@ietf.org>; Mon, 16 Jun 2008 08:08:25 -0700 (PDT)
Received: from [10.10.0.112] ([::ffff:83.136.33.3])
	(AUTH: PLAIN axelm, TLS: TLSv1/SSLv3,256bits,AES256-SHA)
	by pahula with esmtp; Mon, 16 Jun 2008 17:08:58 +0200
	id 00014026.4856820B.00001A0E
Message-ID: <485681FC.9020203@enum.at>
Date: Mon, 16 Jun 2008 17:08:44 +0200
From: Alexander Mayrhofer <alexander.mayrhofer@enum.at>
Organization: enum.at GmbH
User-Agent: Thunderbird 2.0.0.14 (Windows/20080421)
MIME-Version: 1.0
To: speermint@ietf.org
Subject: [Speermint] NITS (and beyond) review of
	draft-ietf-speermint-voip-consolidated-usecases-08
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/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: speermint-bounces@ietf.org
Errors-To: speermint-bounces@ietf.org

Hi,

i did a review of the consolidated usecases draft, comments as follows:

- Generally, i'd appreciate if more eyes could check the draft. I think 
the language could be clearer, and there are also several (mostly small) 
technical issues. More reviewers would definitely help here (i suggest 
nominating at least one other formal reviewer for the document before we 
proceed)

Detailed comments follow:

- The automated idnits report doesn't yield any serious problems 
(complains about the spacing in some examples).

- Abstract: I think it should read "... many common VoIP use caseS .."

- ToC: Parts of the structure are inconsistent. For example, 5. "Use 
Cases" should probably be merged with 5.1 "Static Peering Use Cases", so 
that we have 5. "Static Peering Use Cases" and 6. "On-demand Peering Use 
Cases". Also, if "On-demand direct" is the only "on-demand" use case, a 
seperate section below that seems superflous (should have at least two 
sections at the same level, ihmo). Same for section 7 and 7.1

- There are numerous abbreviations that never get expanded in the draft. 
I do know that a lot of them are from the terminology draft, but that 
draft is not even referenced in the "Terminology" section. The 
abbreviations that are never expanded (i might have missed some, though) 
include: VoIP, (most of the SPEERMINT-Terms), ENUM, VLAN, SSPs, QoS, 
DSCP, URI, UAC, UAS, TN, R-URI, NAPTR, B2BUA, SBC/SBE, RTP, L5, BGP, 
TRIP, SPIT, DUNDi, TLS.

- RFC2119 Terminology is mentioned in the Terminology section, but the 
terms are never used. I strongly suggest referring to the SPEERMINT 
terminology here, though.

- Figure 1: "the elements defined are optional" should probably read 
"some elements..."

- In some of the figures, there is not just a "O-DBE" (oh-dbe), but also 
a "0-DBE" (zero-DBE). I guess it's a typo (if not, i'm curious about the 
purpose of this "element phishing" :)

- page 4, last sentence "sub-divided in .." should probably mean 
"sub-divided into.. " (warning - i'm not a native speaker).

- page 5 mentions a "step four", although the steps are not numbered. 
Maybe change the list into a numbered list.

- Section 5: "User cases" should probably read "Use cases". See more 
comments about the section structure above.

- The phone numbers used in the various SIP requests / ENUM records seem 
not to be from the IETF "good example number" list. Please use the drama 
numbers for the draft (+1 <area code> 555 <0100-0199>), see 
http://www.ietf.org/ID-Checklist.html

- "ENUM" is defined to use e164.arpa. So, any example using a different 
suffix is technically not "ENUM", but "ENUM-like technology". I know 
that might make it hard in some places of the document, but that's how 
it is defined...

- Most of the ENUM records are broken. For example, page 8 has a 
(broken?) backreference "\1", while the regular expression does not 
yield any data for the backreference - no parentheses around the ".*". 
I've a hard time with the term "inputted" below that example, too. Maybe 
"provisioned"? The ENUM records also miss the "replacement" element, 
which in most cases is empty, and therefore a "." at the end of the 
record. They also don't have the "IN" class, while other DNS record 
examples have.

- Typo in bullet 4 on this page - "exapmle.com". There should be a 
reference to the S-NAPTR logic somewhere.

- Bullet 5 - use "TCP as transport" is maybe better than "TCP for 
transport"? (might be a taste issue, though)

- Trailing dot after DNS examples? Most of them are missing that, could 
be a problem if someone decides to enter the records "as they are" into 
a zone.

- 5.1.1.1 "where exists" should probably read "where there is". Maybe 
change "sign a peer agreement which clearly states the peering 
policies... " to "sign a peering agreement which clearly states the 
policies..."

- last paragrahp of 5.1.1.2: "decide to deploy SBE." should probably be 
"decide to deply SBEs".

- last paragraph of 5.1.2: The case where media passes through the DBEs 
is not specific to the static-direct-assisted case - it could also 
happen in the static direct - maybe mention this in the draft..

- 5.1.3 maybe "lies within..." instead of "lies with..."?

- Figure 4 contains one of those "zero-DBE"s :)

- bullet 2 - the ENUM record is broken, there is neither content for the 
backreference, and additionally the regex will never match because there 
is a space after ".*". Missing the replacement component, too.

- Bullet 4: I think it would be good to specify which kind of "DNS 
Lookup", in that case a lookup for S-NAPTRs... same in bullet 6, where a 
DNS query for "A records" (What about AAAA?) is performed. It would also 
be good to reference to the SRV and S-NAPTR documentation somewhere.

- page 17: shouldn't there be "example.ORG" in the Via: header?

- paragraph below: "Note that if I-SSP" instead of "Note that I-SSP"..

- bullet 9: broken ENUM record.

- I'm missing information on when and when not S-NAPTR and SRV queries 
are performed. For example, between step 9. and 10. there is no SRV 
lookup. It is unclear in what cases those lookups are performed, and 
when they are not performed. Maybe they are optional in some scenarios.

- 5.1.3.1: It says that "once O-SSP queries the SED, LUF/LRF provider is 
out of the picture." - that was confusing to me because i don't see how 
the _SED_ itself can be queried ("queries _for_ the SED" instead?). 
Later in the paragraph, "before peering happened", should probably be 
changed to "before peering happens".

- 5.1.3.2: Refers to figure 5, shouldn't that be figure 4? Also, if 
there are no SBE/DBE employed here, wouldn't that make it an Static 
Direct Assisted use case, meaning that the very existance of SBE/DBE is 
the difference, and without them the use case would not be different 
from the other one?

- Figure 5 has the dreaded "zero-DBE" again :)

- 5.1.4.2 "common code" should probably mean "common codec". also, "list 
of codecs" instead of "list of codec".

- 6.1 "there is NOT" -> "there is no" ? I'm missing a reference to the 
Rohan's direct peering draft here...

- 6.1.2 - personally, i don't really like the biased statement about 
SPAM in open peering models. Even in closed models, users of Service 
providers can submit any amount of spam to any peer.

- 7: "concrete" -> "actual"?

- 7.1.1. What is an "LS"? SBCs are SBE's, or?


That's what i found - as i said, i'd definitely recommend that at least 
one other reviewer checks the draft before we proceed.

cheers

Alex







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


From speermint-bounces@ietf.org  Mon Jun 16 08:56:53 2008
Return-Path: <speermint-bounces@ietf.org>
X-Original-To: speermint-archive@megatron.ietf.org
Delivered-To: ietfarch-speermint-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 75E1E3A67DF;
	Mon, 16 Jun 2008 08:56:53 -0700 (PDT)
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 9EEDF3A67DF
	for <speermint@core3.amsl.com>; Mon, 16 Jun 2008 08:56:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id hVaEDHPvCwkf for <speermint@core3.amsl.com>;
	Mon, 16 Jun 2008 08:56:50 -0700 (PDT)
Received: from mailsrv.ams.gblxint.com (unknown-230-det.globalcrossing.com
	[64.208.159.230])
	by core3.amsl.com (Postfix) with ESMTP id D2BD53A676A
	for <speermint@ietf.org>; Mon, 16 Jun 2008 08:56:49 -0700 (PDT)
Received: from w3uspdy19.ams.gblxint.com (w3uspdy19.ams.gblxint.com
	[10.60.51.69])
	by mailsrv.ams.gblxint.com (Postfix) with ESMTP id 389FD9333;
	Mon, 16 Jun 2008 11:57:21 -0400 (EDT)
Received: from w3ussfj136.ams.gblxint.com ([10.10.63.29]) by
	w3uspdy19.ams.gblxint.com with Microsoft SMTPSVC(6.0.3790.3959);
	Mon, 16 Jun 2008 11:57:21 -0400
Received: from EVS10.ams.gblxint.com ([10.10.63.53]) by
	w3ussfj136.ams.gblxint.com ([10.10.63.29]) with mapi; Mon, 16 Jun 2008
	11:57:21 -0400
From: "Uzelac, Adam" <Adam.Uzelac@globalcrossing.com>
To: Alexander Mayrhofer <alexander.mayrhofer@enum.at>,
	"speermint@ietf.org" <speermint@ietf.org>
Date: Mon, 16 Jun 2008 11:57:17 -0400
Thread-Topic: [Speermint] NITS (and beyond) review of
	draft-ietf-speermint-voip-consolidated-usecases-08
Thread-Index: AcjPwvXvBRTZLMpeTy+WaYMsfR0I3AABm55A
Message-ID: <4DAE5E60BA49D8419D7C8832503F5FFC07218953CA@EVS10.ams.gblxint.com>
References: <485681FC.9020203@enum.at>
In-Reply-To: <485681FC.9020203@enum.at>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
MIME-Version: 1.0
X-OriginalArrivalTime: 16 Jun 2008 15:57:21.0060 (UTC)
	FILETIME=[A8FD2E40:01C8CFC9]
Subject: Re: [Speermint] NITS (and beyond) review
	of	draft-ietf-speermint-voip-consolidated-usecases-08
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/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: speermint-bounces@ietf.org
Errors-To: speermint-bounces@ietf.org

Alex - Thank you very much for providing the detail below.  Yiu and I (the editors) will be addressing your comments below in short order, but we will be holding off on submitting a new draft until such time that we have a formal reviewer assigned to the document and get feedback from that person - provided the Chairs want to go down that path.

Adam

> -----Original Message-----
> From: speermint-bounces@ietf.org [mailto:speermint-bounces@ietf.org] On
> Behalf Of Alexander Mayrhofer
> Sent: Monday, June 16, 2008 11:09 AM
> To: speermint@ietf.org
> Subject: [Speermint] NITS (and beyond) review of draft-ietf-speermint-
> voip-consolidated-usecases-08
>
> Hi,
>
> i did a review of the consolidated usecases draft, comments as follows:
>
> - Generally, i'd appreciate if more eyes could check the draft. I think
> the language could be clearer, and there are also several (mostly
> small)
> technical issues. More reviewers would definitely help here (i suggest
> nominating at least one other formal reviewer for the document before
> we
> proceed)
>
> Detailed comments follow:
>
> - The automated idnits report doesn't yield any serious problems
> (complains about the spacing in some examples).
>
> - Abstract: I think it should read "... many common VoIP use caseS .."
>
> - ToC: Parts of the structure are inconsistent. For example, 5. "Use
> Cases" should probably be merged with 5.1 "Static Peering Use Cases",
> so
> that we have 5. "Static Peering Use Cases" and 6. "On-demand Peering
> Use
> Cases". Also, if "On-demand direct" is the only "on-demand" use case, a
> seperate section below that seems superflous (should have at least two
> sections at the same level, ihmo). Same for section 7 and 7.1
>
> - There are numerous abbreviations that never get expanded in the
> draft.
> I do know that a lot of them are from the terminology draft, but that
> draft is not even referenced in the "Terminology" section. The
> abbreviations that are never expanded (i might have missed some,
> though)
> include: VoIP, (most of the SPEERMINT-Terms), ENUM, VLAN, SSPs, QoS,
> DSCP, URI, UAC, UAS, TN, R-URI, NAPTR, B2BUA, SBC/SBE, RTP, L5, BGP,
> TRIP, SPIT, DUNDi, TLS.
>
> - RFC2119 Terminology is mentioned in the Terminology section, but the
> terms are never used. I strongly suggest referring to the SPEERMINT
> terminology here, though.
>
> - Figure 1: "the elements defined are optional" should probably read
> "some elements..."
>
> - In some of the figures, there is not just a "O-DBE" (oh-dbe), but
> also
> a "0-DBE" (zero-DBE). I guess it's a typo (if not, i'm curious about
> the
> purpose of this "element phishing" :)
>
> - page 4, last sentence "sub-divided in .." should probably mean
> "sub-divided into.. " (warning - i'm not a native speaker).
>
> - page 5 mentions a "step four", although the steps are not numbered.
> Maybe change the list into a numbered list.
>
> - Section 5: "User cases" should probably read "Use cases". See more
> comments about the section structure above.
>
> - The phone numbers used in the various SIP requests / ENUM records
> seem
> not to be from the IETF "good example number" list. Please use the
> drama
> numbers for the draft (+1 <area code> 555 <0100-0199>), see
> http://www.ietf.org/ID-Checklist.html
>
> - "ENUM" is defined to use e164.arpa. So, any example using a different
> suffix is technically not "ENUM", but "ENUM-like technology". I know
> that might make it hard in some places of the document, but that's how
> it is defined...
>
> - Most of the ENUM records are broken. For example, page 8 has a
> (broken?) backreference "\1", while the regular expression does not
> yield any data for the backreference - no parentheses around the ".*".
> I've a hard time with the term "inputted" below that example, too.
> Maybe
> "provisioned"? The ENUM records also miss the "replacement" element,
> which in most cases is empty, and therefore a "." at the end of the
> record. They also don't have the "IN" class, while other DNS record
> examples have.
>
> - Typo in bullet 4 on this page - "exapmle.com". There should be a
> reference to the S-NAPTR logic somewhere.
>
> - Bullet 5 - use "TCP as transport" is maybe better than "TCP for
> transport"? (might be a taste issue, though)
>
> - Trailing dot after DNS examples? Most of them are missing that, could
> be a problem if someone decides to enter the records "as they are" into
> a zone.
>
> - 5.1.1.1 "where exists" should probably read "where there is". Maybe
> change "sign a peer agreement which clearly states the peering
> policies... " to "sign a peering agreement which clearly states the
> policies..."
>
> - last paragrahp of 5.1.1.2: "decide to deploy SBE." should probably be
> "decide to deply SBEs".
>
> - last paragraph of 5.1.2: The case where media passes through the DBEs
> is not specific to the static-direct-assisted case - it could also
> happen in the static direct - maybe mention this in the draft..
>
> - 5.1.3 maybe "lies within..." instead of "lies with..."?
>
> - Figure 4 contains one of those "zero-DBE"s :)
>
> - bullet 2 - the ENUM record is broken, there is neither content for
> the
> backreference, and additionally the regex will never match because
> there
> is a space after ".*". Missing the replacement component, too.
>
> - Bullet 4: I think it would be good to specify which kind of "DNS
> Lookup", in that case a lookup for S-NAPTRs... same in bullet 6, where
> a
> DNS query for "A records" (What about AAAA?) is performed. It would
> also
> be good to reference to the SRV and S-NAPTR documentation somewhere.
>
> - page 17: shouldn't there be "example.ORG" in the Via: header?
>
> - paragraph below: "Note that if I-SSP" instead of "Note that I-SSP"..
>
> - bullet 9: broken ENUM record.
>
> - I'm missing information on when and when not S-NAPTR and SRV queries
> are performed. For example, between step 9. and 10. there is no SRV
> lookup. It is unclear in what cases those lookups are performed, and
> when they are not performed. Maybe they are optional in some scenarios.
>
> - 5.1.3.1: It says that "once O-SSP queries the SED, LUF/LRF provider
> is
> out of the picture." - that was confusing to me because i don't see how
> the _SED_ itself can be queried ("queries _for_ the SED" instead?).
> Later in the paragraph, "before peering happened", should probably be
> changed to "before peering happens".
>
> - 5.1.3.2: Refers to figure 5, shouldn't that be figure 4? Also, if
> there are no SBE/DBE employed here, wouldn't that make it an Static
> Direct Assisted use case, meaning that the very existance of SBE/DBE is
> the difference, and without them the use case would not be different
> from the other one?
>
> - Figure 5 has the dreaded "zero-DBE" again :)
>
> - 5.1.4.2 "common code" should probably mean "common codec". also,
> "list
> of codecs" instead of "list of codec".
>
> - 6.1 "there is NOT" -> "there is no" ? I'm missing a reference to the
> Rohan's direct peering draft here...
>
> - 6.1.2 - personally, i don't really like the biased statement about
> SPAM in open peering models. Even in closed models, users of Service
> providers can submit any amount of spam to any peer.
>
> - 7: "concrete" -> "actual"?
>
> - 7.1.1. What is an "LS"? SBCs are SBE's, or?
>
>
> That's what i found - as i said, i'd definitely recommend that at least
> one other reviewer checks the draft before we proceed.
>
> cheers
>
> Alex
>
>
>
>
>
>
>
> _______________________________________________
> 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 speermint-bounces@ietf.org  Wed Jun 18 05:29:42 2008
Return-Path: <speermint-bounces@ietf.org>
X-Original-To: speermint-archive@megatron.ietf.org
Delivered-To: ietfarch-speermint-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id EF7BB28C0EE;
	Wed, 18 Jun 2008 05:29:41 -0700 (PDT)
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 26B263A69A5
	for <speermint@core3.amsl.com>; Wed, 18 Jun 2008 05:29:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.043
X-Spam-Level: 
X-Spam-Status: No, score=0.043 tagged_above=-999 required=5 tests=[AWL=0.506, 
	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 fqXSgKNNvNIN for <speermint@core3.amsl.com>;
	Wed, 18 Jun 2008 05:29:39 -0700 (PDT)
Received: from pacdcimo01.cable.comcast.com (PacdcIMO01.cable.comcast.com
	[24.40.8.145]) by core3.amsl.com (Postfix) with ESMTP id 3C8573A67AA
	for <speermint@ietf.org>; Wed, 18 Jun 2008 05:29:39 -0700 (PDT)
Received: from ([10.195.246.152])
	by pacdcimo01.cable.comcast.com with ESMTP  id 5503620.5729210;
	Wed, 18 Jun 2008 08:30:03 -0400
Received: from PACDCEXCMB04.cable.comcast.com ([24.40.15.86]) by
	NJMDCEXCRLY01.cable.comcast.com with Microsoft
	SMTPSVC(6.0.3790.3959); Wed, 18 Jun 2008 08:30:03 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Wed, 18 Jun 2008 08:30:02 -0400
Message-ID: <45AEC6EF95942140888406588E1A66020522D5C7@PACDCEXCMB04.cable.comcast.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: SPEERMINT - Requested session has been scheduled for IETF 72 
Thread-Index: AcjMzxGM9jdGhm2+SjWXWElxS3Jd5gEbdnGw
From: "Livingood, Jason" <Jason_Livingood@cable.comcast.com>
To: <speermint@ietf.org>
X-OriginalArrivalTime: 18 Jun 2008 12:30:03.0249 (UTC)
	FILETIME=[084D5610:01C8D13F]
Subject: [Speermint] FW: SPEERMINT - Requested session has been scheduled
	for IETF 72
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/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: speermint-bounces@ietf.org
Errors-To: speermint-bounces@ietf.org

Looks like we are TENTATIVELY scheduled for Monday afternoon in
Dublin... 

-----Original Message-----
From: IETF Secretariat [mailto:agenda@ietf.org] 

SPEERMINT Session 1 (2 hours)
Monday, Afternoon Session I 1300-1500
Room Name: Convention 3
_______________________________________________
Speermint mailing list
Speermint@ietf.org
https://www.ietf.org/mailman/listinfo/speermint


From speermint-bounces@ietf.org  Tue Jun 24 13:13:41 2008
Return-Path: <speermint-bounces@ietf.org>
X-Original-To: speermint-archive@megatron.ietf.org
Delivered-To: ietfarch-speermint-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id F13643A6A87;
	Tue, 24 Jun 2008 13:13:40 -0700 (PDT)
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 D22743A6A86
	for <speermint@core3.amsl.com>; Tue, 24 Jun 2008 13:13:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.689
X-Spam-Level: 
X-Spam-Status: No, score=-2.689 tagged_above=-999 required=5
	tests=[AWL=-0.091, BAYES_00=-2.599, NORMAL_HTTP_TO_IP=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 40Pl9UgudBkf for <speermint@core3.amsl.com>;
	Tue, 24 Jun 2008 13:13:38 -0700 (PDT)
Received: from mailgate.siemenscomms.co.uk (mailgate.siemenscomms.co.uk
	[195.171.110.225])
	by core3.amsl.com (Postfix) with ESMTP id 891C03A6A0B
	for <speermint@ietf.org>; Tue, 24 Jun 2008 13:13:38 -0700 (PDT)
Received: from GBNTHT12009MSX.gb002.siemens.net ([137.223.219.235])
	by siemenscomms.co.uk (PMDF V6.3-x14 #31430)
	with ESMTP id <0K2Z0063NHEBQA@siemenscomms.co.uk> for
	speermint@ietf.org; Tue, 24 Jun 2008 21:10:59 +0100 (BST)
Date: Tue, 24 Jun 2008 21:10:58 +0100
From: "Elwell, John" <john.elwell@siemens.com>
To: speermint@ietf.org
Message-id: <0D5F89FAC29E2C41B98A6A762007F5D0D6E429@GBNTHT12009MSX.gb002.siemens.net>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft Exchange V6.5
Thread-Topic: Partial review of draft-ietf-speermint-consolidated-usecases-08
Thread-Index: AcjWNmpf8DUIQNM3Q9ePQl6Q2YVPvw==
Content-class: urn:content-classes:message
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Subject: [Speermint] Partial review of
	draft-ietf-speermint-consolidated-usecases-08
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/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: speermint-bounces@ietf.org
Errors-To: speermint-bounces@ietf.org

This is not a full review, because of lack of time. Also I will not
re-iterate the many points that Alexander Mayrhofer has already raised:
http://www.ietf.org/mail-archive/web/speermint/current/msg02396.html

In general, I think the document assumes too much prior knowledge from
the reader.

1. Figure 1 is not self-explanatory. Even if all the acronyms are
defined (as Alexander requested), what is the relationship between the
three domains (are they all peers of each other)? What is the meaning of
the lines connecting some of the inner boxes together, and what is to
the meaning when inner boxes are not interconnected (as within the
middle domain)? In particular there is no line between O-SBE and O-LRF,
yet the first example shows O-SBE querying O-LRF. Indeed there is a line
between those two entities in figure 2. What is the meaning of "LUF/LRF
Provider Domain Indirect SSP Domain" - should there be an "and" or an
"or" here?

2. "Each use-case must specify a
   basic set of required operations to be performed by each member when
   peering."
Is this supposed to be saying that this document specifies a basic set
of required operations....for each use case? If so, then these are hard
to find in the different use cases later in the document. For example, I
cannot find anywhere later in the document that mentions "peer
discovery" or "location determination" or "next hop determination"....

3. " Peer Discovery - Peer discovery via a Look-Up Function (LUF) to
      determine the administrative domain of the target.

   o  Location Determination - A location determination process serves
      to create the Session Establishment Data (SED).  Examples: Public
      User-ENUM, public Infrastructure ENUM, private ENUM tree, SIP
      Redirect, DUNDi."
The LUF determines the domain of the target, and therefore the various
ENUM possibilities seems to be part of "Peer Discovery", not "Location
Determination".

4. " Next Hop Determination - A next hop determination based on the SED
      is then completed. "
I thought once you had the SED you had already determined the next hop,
i.e., information on the next hop is part of the SED.

5. "If Location Routing Function (LRF) query did
      not return an URI of the form sip:user@IP-address"
There is no previous mention of an LRF query.

6. "federation private DNS" and "split-DNS" - do we have references for
these?

7. "P2P SIP". I am not sure this needs to be mentioned, particularly as
we don't have anything we can reference yet.

8. "For instance, the receiving side
      border elements need to determine whether the INVITE it just
      received really came from a member of the federation,"
This is the first time federation is assumed. The involvement of a
federation should be explained at an early stage.

9. "The peers may exchange interconnection parameters
   such as DSCP policies, subscriber SIP-URI and proxy location prior to
   establishing the interconnection."
How can the "subscriber SIP-URI" be known in advance of a particular
call set-up?

10. Figure 2 lacks the DBE functions in figure 1.

11. "So, O-Proxy queries LUF for SED information from a routing
        database."
I thought the LUF just identifies the domain, and a further LRF query is
needed to get the SED.

12. "O-Proxy examines the SED and discover the domain is external."
Again I didn't think an ENUM look-up (in the previous step) gave us the
SED.

13. The draft seems to talk about LUF and LRF, and also about DNS
(NAPTR, A records, etc.) LUF and LRF are shown in the figures, DNS is
not. It is not always clear how DNS relates to LUF/LRF, i.e., is DNS a
means of realising LUF and/or LRF?

14. "$ORIGIN 3.3.3.3.2.2.2.7.1.9.1.example.com
          NAPTR 10 100 "u" "E2U+SIP"
           "!^.*!sip:\1@t-sbe.example.net!""
Isn't it more likely that it will yield example.net, rather than
t-sbe.example.net? Then an SRV look-up might yield t-sbe.example.net. So
routing from O-Proxy to O-SBE would contain:
INVITE sip:+19172223333@example.net SIP/2.0
Route: sip:o-sbe1.example.com;lr
O-SBE would then use RFC 3263 to find the server in example.net.

15. "INVITE sip:+19172223333@i-sbe1.example.org;user=phone SIP/2.0"
Isn't this more likely to be of the form:
INVITE sip:+19172223333@example.net;user=phone SIP/2.0
Route: sip:i-sbe1.example.org;lr
In other words, the terminating domain is kept in the Request-URI, with
loose routing to get you to the intermediate domain.

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


From speermint-bounces@ietf.org  Tue Jun 24 13:47:49 2008
Return-Path: <speermint-bounces@ietf.org>
X-Original-To: speermint-archive@megatron.ietf.org
Delivered-To: ietfarch-speermint-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 4512C3A69FE;
	Tue, 24 Jun 2008 13:47:49 -0700 (PDT)
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 C8DD23A69FE
	for <speermint@core3.amsl.com>; Tue, 24 Jun 2008 13:47:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.462
X-Spam-Level: 
X-Spam-Status: No, score=-0.462 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768,
	HOST_EQ_MODEMCABLE=1.368, NORMAL_HTTP_TO_IP=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 kCxMJgZeP7Mf for <speermint@core3.amsl.com>;
	Tue, 24 Jun 2008 13:47:46 -0700 (PDT)
Received: from paoakoavas10.cable.comcast.com (paoakoavas10.cable.comcast.com
	[208.17.35.59]) by core3.amsl.com (Postfix) with ESMTP id 44D3B3A69EC
	for <speermint@ietf.org>; Tue, 24 Jun 2008 13:47:46 -0700 (PDT)
Received: from ([10.195.246.152])
	by paoakoavas10.cable.comcast.com with ESMTP  id KP-TDCH7.47293824;
	Tue, 24 Jun 2008 16:47:31 -0400
Received: from PACDCEXCMB04.cable.comcast.com ([24.40.15.86]) by
	NJMDCEXCRLY01.cable.comcast.com with Microsoft
	SMTPSVC(6.0.3790.3959); Tue, 24 Jun 2008 16:47:31 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 24 Jun 2008 16:47:28 -0400
Message-ID: <45AEC6EF95942140888406588E1A6602097E7B@PACDCEXCMB04.cable.comcast.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Partial review of draft-ietf-speermint-consolidated-usecases-08
Thread-Index: AcjWNmpf8DUIQNM3Q9ePQl6Q2YVPvwABRl2j
From: "Lee, Yiu" <Yiu_Lee@Cable.Comcast.com>
To: <john.elwell@siemens.com>,
	<speermint@ietf.org>
X-OriginalArrivalTime: 24 Jun 2008 20:47:31.0213 (UTC)
	FILETIME=[858DB3D0:01C8D63B]
Subject: Re: [Speermint] Partial review
	ofdraft-ietf-speermint-consolidated-usecases-08
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/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: speermint-bounces@ietf.org
Errors-To: speermint-bounces@ietf.org

Alex and John,

Thanks for taking the time to review the draft. The comments are great. Adam and I will address your comments and target to release a new version next week.

Thanks,
Yiu



----- Original Message -----
From: speermint-bounces@ietf.org <speermint-bounces@ietf.org>
To: speermint@ietf.org <speermint@ietf.org>
Sent: Tue Jun 24 16:10:58 2008
Subject: [Speermint] Partial review ofdraft-ietf-speermint-consolidated-usecases-08

This is not a full review, because of lack of time. Also I will not
re-iterate the many points that Alexander Mayrhofer has already raised:
http://www.ietf.org/mail-archive/web/speermint/current/msg02396.html

In general, I think the document assumes too much prior knowledge from
the reader.

1. Figure 1 is not self-explanatory. Even if all the acronyms are
defined (as Alexander requested), what is the relationship between the
three domains (are they all peers of each other)? What is the meaning of
the lines connecting some of the inner boxes together, and what is to
the meaning when inner boxes are not interconnected (as within the
middle domain)? In particular there is no line between O-SBE and O-LRF,
yet the first example shows O-SBE querying O-LRF. Indeed there is a line
between those two entities in figure 2. What is the meaning of "LUF/LRF
Provider Domain Indirect SSP Domain" - should there be an "and" or an
"or" here?

2. "Each use-case must specify a
   basic set of required operations to be performed by each member when
   peering."
Is this supposed to be saying that this document specifies a basic set
of required operations....for each use case? If so, then these are hard
to find in the different use cases later in the document. For example, I
cannot find anywhere later in the document that mentions "peer
discovery" or "location determination" or "next hop determination"....

3. " Peer Discovery - Peer discovery via a Look-Up Function (LUF) to
      determine the administrative domain of the target.

   o  Location Determination - A location determination process serves
      to create the Session Establishment Data (SED).  Examples: Public
      User-ENUM, public Infrastructure ENUM, private ENUM tree, SIP
      Redirect, DUNDi."
The LUF determines the domain of the target, and therefore the various
ENUM possibilities seems to be part of "Peer Discovery", not "Location
Determination".

4. " Next Hop Determination - A next hop determination based on the SED
      is then completed. "
I thought once you had the SED you had already determined the next hop,
i.e., information on the next hop is part of the SED.

5. "If Location Routing Function (LRF) query did
      not return an URI of the form sip:user@IP-address"
There is no previous mention of an LRF query.

6. "federation private DNS" and "split-DNS" - do we have references for
these?

7. "P2P SIP". I am not sure this needs to be mentioned, particularly as
we don't have anything we can reference yet.

8. "For instance, the receiving side
      border elements need to determine whether the INVITE it just
      received really came from a member of the federation,"
This is the first time federation is assumed. The involvement of a
federation should be explained at an early stage.

9. "The peers may exchange interconnection parameters
   such as DSCP policies, subscriber SIP-URI and proxy location prior to
   establishing the interconnection."
How can the "subscriber SIP-URI" be known in advance of a particular
call set-up?

10. Figure 2 lacks the DBE functions in figure 1.

11. "So, O-Proxy queries LUF for SED information from a routing
        database."
I thought the LUF just identifies the domain, and a further LRF query is
needed to get the SED.

12. "O-Proxy examines the SED and discover the domain is external."
Again I didn't think an ENUM look-up (in the previous step) gave us the
SED.

13. The draft seems to talk about LUF and LRF, and also about DNS
(NAPTR, A records, etc.) LUF and LRF are shown in the figures, DNS is
not. It is not always clear how DNS relates to LUF/LRF, i.e., is DNS a
means of realising LUF and/or LRF?

14. "$ORIGIN 3.3.3.3.2.2.2.7.1.9.1.example.com
          NAPTR 10 100 "u" "E2U+SIP"
           "!^.*!sip:\1@t-sbe.example.net!""
Isn't it more likely that it will yield example.net, rather than
t-sbe.example.net? Then an SRV look-up might yield t-sbe.example.net. So
routing from O-Proxy to O-SBE would contain:
INVITE sip:+19172223333@example.net SIP/2.0
Route: sip:o-sbe1.example.com;lr
O-SBE would then use RFC 3263 to find the server in example.net.

15. "INVITE sip:+19172223333@i-sbe1.example.org;user=phone SIP/2.0"
Isn't this more likely to be of the form:
INVITE sip:+19172223333@example.net;user=phone SIP/2.0
Route: sip:i-sbe1.example.org;lr
In other words, the terminating domain is kept in the Request-URI, with
loose routing to get you to the intermediate domain.

John
_______________________________________________
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 speermint-bounces@ietf.org  Fri Jun 27 03:23:07 2008
Return-Path: <speermint-bounces@ietf.org>
X-Original-To: speermint-archive@megatron.ietf.org
Delivered-To: ietfarch-speermint-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 8666D3A6B54;
	Fri, 27 Jun 2008 03:23:07 -0700 (PDT)
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 951593A6C6F
	for <speermint@core3.amsl.com>; Fri, 27 Jun 2008 03:18:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.094
X-Spam-Level: 
X-Spam-Status: No, score=0.094 tagged_above=-999 required=5 tests=[AWL=0.557, 
	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 Ys+6LoAnUL9Z for <speermint@core3.amsl.com>;
	Fri, 27 Jun 2008 03:18:34 -0700 (PDT)
Received: from ondar.cablelabs.com (ondar.cablelabs.com [192.160.73.61])
	by core3.amsl.com (Postfix) with ESMTP id D52EE28C328
	for <speermint@ietf.org>; Fri, 27 Jun 2008 02:19:09 -0700 (PDT)
Received: from kyzyl.cablelabs.com (kyzyl [10.253.0.7])
	by ondar.cablelabs.com (8.14.2/8.14.2) with ESMTP id m5R9IwIA019773;
	Fri, 27 Jun 2008 03:18:59 -0600
Received: from srvxchg3.cablelabs.com (10.5.0.25)
	by kyzyl.cablelabs.com (F-Secure/fsigk_smtp/511/kyzyl.cablelabs.com);
	Fri, 27 Jun 2008 03:18:58 -0700 (MST)
X-Virus-Status: clean(F-Secure/fsigk_smtp/511/kyzyl.cablelabs.com)
X-Mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Fri, 27 Jun 2008 03:18:18 -0600
Message-ID: <9AAEDF491EF7CA48AB587781B8F5D7C60128FAE8@srvxchg3.cablelabs.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Comments on draft-ietf-speermint-voip-consolidated-usecases-08
Thread-Index: AcjYNrxrGJi2/t77SJiqLkAy5yPGQA==
From: "Jean-Francois Mule" <jf.mule@cablelabs.com>
To: <speermint@ietf.org>, <adam.uzelac@globalcrossing.com>,
	<yiu_lee@cable.comcast.com>
X-Approved: ondar
Subject: [Speermint] Comments on
	draft-ietf-speermint-voip-consolidated-usecases-08
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/pipermail/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>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: speermint-bounces@ietf.org
Errors-To: speermint-bounces@ietf.org

Hi Adam and Yiu Lee,

   Here are some comments based on the draft-08 revision.

Jean-Fran=E7ois

1. Technical comments

- page 5, Next Hop Determination:
  s/IP-address/hostname
Hopefully, the result of a query to the Location Routing Function is a sip =
uri with either a hostname or domain name, not an IP address.  If some folk=
s prefer to use IP, it's their problem but the document must use hostnames =
(the DNS resolver on the originating host should do the domain/hostname->IP=
 add resolution).

- page 5: "[RFC3263] in a federation private DNS."
This is just an example but it is contrary to the conclusion we had with Pa=
trick Falstrom in the beginning of the wg terminology document.  The issue =
is "private DNS" in this sentence: it tends to leak the "private" boundarie=
s and is difficult to manage to avoid conflicts.  You can achieve the same =
results by registering domain names to have them in the public DNS, yet the=
 resolution of the DNS name give you DNS records that are only meaningful i=
n the federation (e.g. IP address not publicly routable).
s/[RFC3263] in a federation private DNS/[RFC3263] in a private federation (=
where DNS names may be registered but the accessibility of the DNS response=
s may be restricted to federation members)

-  p18, 5.1.4. Static Indirect Peering Use Case:
This section should be updated to keep the text in scope of speermint, clea=
r from any considerations around provisioning or IP/telephony routing consi=
derations. Specifically, in this paragraph:
"The challenge for O-SSP is to decide which I-SSP should be
 used to reach T-SSP.  O-SSP could manually enter I-SSP information in
 the routing database.  However, when O-SSP peers to multiple I-SSP,
 O-SSP may have multiple routes to reach the same T-SSP.  If we
 further consider that an I-SSP may use another I-SSP to reach T-SSP,
 the permutation can grow exponentially.  This is similar to the IP
 routing problem eventually solved by BGP [RFC4271].  TRIP [RFC3219]
 is a candidate to solve this problem.  However, market has yet to
 deploy TRIP in large scale."

New proposed text:
"The O-SSP determines the appropriate I-SSP intermediary to reach the termi=
nating peer based on the routing database linked with its LUF/LRF.  Note th=
at there could be multiple I-SSPs and multiple SIP routes to reach the same=
 T-SSP; this is out of scope of speermint and has become a focus in the dri=
nks working group."

Or something like that.  In other words, I am not sure it helps the reader =
to throw protocol names like BGP or TRIP and then spell doubts on the deplo=
yability of a protocol in large scale.


- p19, section 5.1.4.1. Administrative characteristics
This section does not bring much to speermint and is all about building wal=
led gardens for SIP and media.  This is certainly a valid use case based on=
 some SSP deployments but I fail to see what is different in this use case =
on message flows (4,5,6, and 7) compared to the direct peering case.  Is th=
e difference in the responses in (2)?  =


- p22, Central SIP Proxy Federations
This whole section should be removed.  I got serious issues with this secti=
on and its content.
It's title says it all: it is about SIP proxy and out of scope of speermint=
.  The first 2 paragraphs are pure 'federation' marketing and do imply that=
 a firewall is the single solution to solving the SIP identity and building=
 an on-demand trust relationship with an unknown peer.  Hopefully there is =
much more than that.


2. Editorial comments
As you get the doc ready for publication, you may want to consider the foll=
owing:
- page 3, section 1, and page 13, 5.1.2.2.:
   is it necessary to keep references to early drafts that have not progres=
sed and are using different terminology?  I don't think we want to carry th=
e original speermint problem statement draft in an RFC.
- page 3, section 2:  consider referencing the terminology draft here, some=
thing like:
  "This document also reuses the terminology defined in [I-D.ietf-speermint=
-terminology]."
- s/operator/SIP Service Provider (globally)


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


From speermint-bounces@ietf.org  Fri Jun 27 04:53:33 2008
Return-Path: <speermint-bounces@ietf.org>
X-Original-To: speermint-archive@megatron.ietf.org
Delivered-To: ietfarch-speermint-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 99A463A6B73;
	Fri, 27 Jun 2008 04:53:33 -0700 (PDT)
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 7BE263A6B75
	for <speermint@core3.amsl.com>; Fri, 27 Jun 2008 04:53:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.43
X-Spam-Level: 
X-Spam-Status: No, score=-2.43 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, HELO_EQ_AT=0.424, HOST_EQ_AT=0.745,
	RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id woaLzHJTzAcr for <speermint@core3.amsl.com>;
	Fri, 27 Jun 2008 04:53:30 -0700 (PDT)
Received: from mail.bofh.priv.at (fardach.bofh.priv.at [88.198.34.164])
	by core3.amsl.com (Postfix) with ESMTP id 73B3E3A6B4E
	for <speermint@ietf.org>; Fri, 27 Jun 2008 04:53:29 -0700 (PDT)
Received: from [10.10.0.107] (nat.labs.nic.at [83.136.33.3])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by mail.bofh.priv.at (Postfix) with ESMTP id B63A94CC86;
	Fri, 27 Jun 2008 13:53:29 +0200 (CEST)
Message-ID: <4864D4D8.50706@nic.at>
Date: Fri, 27 Jun 2008 13:54:00 +0200
From: Otmar Lendl <lendl@nic.at>
User-Agent: Thunderbird 2.0.0.14 (Windows/20080421)
MIME-Version: 1.0
To: Jean-Francois Mule <jf.mule@cablelabs.com>
References: <9AAEDF491EF7CA48AB587781B8F5D7C60128FAE8@srvxchg3.cablelabs.com>
In-Reply-To: <9AAEDF491EF7CA48AB587781B8F5D7C60128FAE8@srvxchg3.cablelabs.com>
Cc: speermint@ietf.org
Subject: Re: [Speermint] Comments
	on	draft-ietf-speermint-voip-consolidated-usecases-08
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/pipermail/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>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: speermint-bounces@ietf.org
Errors-To: speermint-bounces@ietf.org

Jean-Francois Mule wrote:
>    Here are some comments based on the draft-08 revision.
 >
> 1. Technical comments
> 

Jean-Francois,

Your comments question the technical soundness of some the scenarios 
described in this document. That's a valid point, if this were a document 
which describes how speermint envisions peerings to happen in the future.

As I see the purpose of this document (see Abstract), it is just supposed 
to just document what's out there, including warts, kludges and stupidities.

Thus: whatever conclusions we reached with paf (concerning private DNS) 
doesn't affect what's deployed right now and that's what this document is 
about.

So if I'm not mistaken about the purpose of this document, then we don't 
need reviews saying "this is a stupid way to peer", but "nobody is doing
it this way today."

/ol
-- 
// Otmar Lendl <lendl@nic.at>, T: +43 1 5056416 - 33, F: - 933 //
_______________________________________________
Speermint mailing list
Speermint@ietf.org
https://www.ietf.org/mailman/listinfo/speermint


From speermint-bounces@ietf.org  Fri Jun 27 05:19:57 2008
Return-Path: <speermint-bounces@ietf.org>
X-Original-To: speermint-archive@megatron.ietf.org
Delivered-To: ietfarch-speermint-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 841F93A6B7E;
	Fri, 27 Jun 2008 05:19:57 -0700 (PDT)
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 229A23A6B7E
	for <speermint@core3.amsl.com>; Fri, 27 Jun 2008 05:19:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.017
X-Spam-Level: 
X-Spam-Status: No, score=-0.017 tagged_above=-999 required=5 tests=[AWL=0.446, 
	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 LeD0w+iDhzt9 for <speermint@core3.amsl.com>;
	Fri, 27 Jun 2008 05:19:55 -0700 (PDT)
Received: from ondar.cablelabs.com (ondar.cablelabs.com [192.160.73.61])
	by core3.amsl.com (Postfix) with ESMTP id 2A5253A6B81
	for <speermint@ietf.org>; Fri, 27 Jun 2008 05:19:55 -0700 (PDT)
Received: from kyzyl.cablelabs.com (kyzyl [10.253.0.7])
	by ondar.cablelabs.com (8.14.2/8.14.2) with ESMTP id m5RCJrP4029447;
	Fri, 27 Jun 2008 06:19:53 -0600
Received: from srvxchg3.cablelabs.com (10.5.0.25)
	by kyzyl.cablelabs.com (F-Secure/fsigk_smtp/511/kyzyl.cablelabs.com);
	Fri, 27 Jun 2008 06:19:53 -0700 (MST)
X-Virus-Status: clean(F-Secure/fsigk_smtp/511/kyzyl.cablelabs.com)
X-Mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Fri, 27 Jun 2008 06:19:14 -0600
Message-ID: <9AAEDF491EF7CA48AB587781B8F5D7C60128FAEC@srvxchg3.cablelabs.com>
In-Reply-To: <4864D4D8.50706@nic.at>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Speermint] Comments
	on	draft-ietf-speermint-voip-consolidated-usecases-08
Thread-Index: AcjYTG1ODT7lQOSPRCa0/w+L0UkO9wAAiNgw
References: <9AAEDF491EF7CA48AB587781B8F5D7C60128FAE8@srvxchg3.cablelabs.com>
	<4864D4D8.50706@nic.at>
From: "Jean-Francois Mule" <jf.mule@cablelabs.com>
To: "Otmar Lendl" <lendl@nic.at>
X-Approved: ondar
Cc: speermint@ietf.org
Subject: Re: [Speermint] Comments
	on	draft-ietf-speermint-voip-consolidated-usecases-08
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/pipermail/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>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: speermint-bounces@ietf.org
Errors-To: speermint-bounces@ietf.org

Otmar wrote:

> -----Original Message-----
> From: Otmar Lendl [mailto:lendl@nic.at]
> Sent: Friday, June 27, 2008 5:54 AM
> To: Jean-Francois Mule
> Cc: speermint@ietf.org; adam.uzelac@globalcrossing.com;
> yiu_lee@cable.comcast.com
> Subject: Re: [Speermint] Comments on draft-ietf-speermint-voip-
> consolidated-usecases-08
> =

> Jean-Francois Mule wrote:
> >    Here are some comments based on the draft-08 revision.
>  >
> > 1. Technical comments
> >
> =

> Jean-Francois,
> =

> Your comments question the technical soundness of some the
> scenarios
> described in this document. That's a valid point, if this were a
> document
> which describes how speermint envisions peerings to happen in the
> future.
> =

> As I see the purpose of this document (see Abstract), it is just
> supposed
> to just document what's out there, including warts, kludges and
> stupidities.
I read the abstract and got that part fine.  So I would be ok as long as it=
 is worded as such in the text.
What concerns me is this:
In abstract: =

	"This document captures them to provide a reference."
	=3D> what kind of reference?

Then in the intro:
     "These use cases will assist in identifying requirements and future wo=
rks for VoIP Peering using SIP."
 	=3D> that is where I get concerns.

On the one hand, the document says: this is what's deployed today in abstra=
ct.  On the other hand, the next paragraphs say: this is going to be used t=
o derive requirements. If we are all ok documenting what's in use today, in=
cluding kludges, then let's not say that this is a reference for requiremen=
ts.

> Thus: whatever conclusions we reached with paf (concerning private
> DNS)
> doesn't affect what's deployed right now and that's what this
> document is about.

It does not hurt to then put the right context around such examples and say=
 that while this is deployed, it is preferable to do <this>, where <this> i=
s something more sound.


> So if I'm not mistaken about the purpose of this document, then we
  Well, as I stated above, you and I have followed the work of working grou=
p to some extent and yet, we both read different things.  Think about this =
document being an RFC, and being read by folks trying to figure out how the=
y could do session peering.  This is where we got to be careful.

> don't
> need reviews saying "this is a stupid way to peer", but "nobody is
> doing it this way today."

Your quotes implied I said this.  I may not recall what I said already but =
I did not word it that way and folks who have done this that way probably a=
ren't stupid.

Jean-Fran=E7ois
> =

> /ol
> --
> // Otmar Lendl <lendl@nic.at>, T: +43 1 5056416 - 33, F: - 933 //
_______________________________________________
Speermint mailing list
Speermint@ietf.org
https://www.ietf.org/mailman/listinfo/speermint


From speermint-bounces@ietf.org  Fri Jun 27 07:50:30 2008
Return-Path: <speermint-bounces@ietf.org>
X-Original-To: speermint-archive@megatron.ietf.org
Delivered-To: ietfarch-speermint-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id AF41F3A6B1C;
	Fri, 27 Jun 2008 07:50:30 -0700 (PDT)
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 83CE93A6B1C
	for <speermint@core3.amsl.com>; Fri, 27 Jun 2008 07:50:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.622
X-Spam-Level: 
X-Spam-Status: No, score=-2.622 tagged_above=-999 required=5
	tests=[AWL=-0.023, 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 epq0fQbY0M8P for <speermint@core3.amsl.com>;
	Fri, 27 Jun 2008 07:50:28 -0700 (PDT)
Received: from mailgate.siemenscomms.co.uk (mailgate.siemenscomms.co.uk
	[195.171.110.225])
	by core3.amsl.com (Postfix) with ESMTP id 9605C3A6B19
	for <speermint@ietf.org>; Fri, 27 Jun 2008 07:50:28 -0700 (PDT)
Received: from GBNTHT12009MSX.gb002.siemens.net ([137.223.219.235])
	by siemenscomms.co.uk (PMDF V6.3-x14 #31430)
	with ESMTP id <0K3400D8SMK3QG@siemenscomms.co.uk> for
	speermint@ietf.org; Fri, 27 Jun 2008 15:50:33 +0100 (BST)
Date: Fri, 27 Jun 2008 15:50:04 +0100
From: "Elwell, John" <john.elwell@siemens.com>
In-reply-to: <4864D4D8.50706@nic.at>
To: Otmar Lendl <lendl@nic.at>, Jean-Francois Mule <jf.mule@cablelabs.com>
Message-id: <0D5F89FAC29E2C41B98A6A762007F5D0D9ECD1@GBNTHT12009MSX.gb002.siemens.net>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft Exchange V6.5
Thread-Topic: [Speermint] Comments
	ondraft-ietf-speermint-voip-consolidated-usecases-08
Thread-Index: AcjYYRIiexO6rKELS2q594/7pqcZWgAAwAQQ
Content-class: urn:content-classes:message
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
References: <9AAEDF491EF7CA48AB587781B8F5D7C60128FAE8@srvxchg3.cablelabs.com>
	<4864D4D8.50706@nic.at>
Cc: speermint@ietf.org
Subject: Re: [Speermint]
	Comments	ondraft-ietf-speermint-voip-consolidated-usecases-08
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/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: speermint-bounces@ietf.org
Errors-To: speermint-bounces@ietf.org

Otmar, 

> -----Original Message-----
> From: speermint-bounces@ietf.org 
> [mailto:speermint-bounces@ietf.org] On Behalf Of Otmar Lendl
> Sent: 27 June 2008 12:54
> To: Jean-Francois Mule
> Cc: speermint@ietf.org
> Subject: Re: [Speermint] Comments 
> ondraft-ietf-speermint-voip-consolidated-usecases-08
> 
> Jean-Francois Mule wrote:
> >    Here are some comments based on the draft-08 revision.
>  >
> > 1. Technical comments
> > 
> 
> Jean-Francois,
> 
> Your comments question the technical soundness of some the scenarios 
> described in this document. That's a valid point, if this 
> were a document 
> which describes how speermint envisions peerings to happen in 
> the future.
> 
> As I see the purpose of this document (see Abstract), it is 
> just supposed 
> to just document what's out there, including warts, kludges 
> and stupidities.
[JRE] Your are correct - that is what the abstract says. But thinking
about it, is this really what SPEERMINT wants to publish as an RFC?
Normally a use cases RFC (or a use cases section in an RFC) describes
use cases that need to be catered for in a solution. Based on these use
cases and other factors, requirements can be derived. A use cases RFC
does not normally describe in detail how such use cases are already
realised (if indeed they are already realised), but just outlines of
what should happen from a user perspective.

If SPEERMINT really is just trying to document existing practice in this
draft, I would no necessarily object, but we may need to find a more
appropriate title, e.g., current practices.

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


From speermint-bounces@ietf.org  Fri Jun 27 08:35:20 2008
Return-Path: <speermint-bounces@ietf.org>
X-Original-To: speermint-archive@megatron.ietf.org
Delivered-To: ietfarch-speermint-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id DDF953A69BB;
	Fri, 27 Jun 2008 08:35:20 -0700 (PDT)
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 F2A123A69B2
	for <speermint@core3.amsl.com>; Fri, 27 Jun 2008 08:35:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 3.001
X-Spam-Level: ***
X-Spam-Status: No, score=3.001 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768,
	HOST_EQ_MODEMCABLE=1.368, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=1.396, 
	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 GAPmLbuuhE5K for <speermint@core3.amsl.com>;
	Fri, 27 Jun 2008 08:35:07 -0700 (PDT)
Received: from pacdcimo01.cable.comcast.com (PacdcIMO01.cable.comcast.com
	[24.40.8.145]) by core3.amsl.com (Postfix) with ESMTP id 1C8823A67FA
	for <speermint@ietf.org>; Fri, 27 Jun 2008 08:35:06 -0700 (PDT)
Received: from ([24.40.15.118])
	by pacdcimo01.cable.comcast.com with ESMTP  id 5503620.6663708;
	Fri, 27 Jun 2008 11:34:45 -0400
Received: from PACDCEXCMB04.cable.comcast.com ([24.40.15.86]) by
	PACDCEXCSMTP04.cable.comcast.com with Microsoft
	SMTPSVC(6.0.3790.3959); Fri, 27 Jun 2008 11:34:46 -0400
Received: from 68.239.242.4 ([68.239.242.4]) 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 ; Fri, 27 Jun 2008 15:34:43 +0000
User-Agent: Microsoft-Entourage/12.11.0.080522
Date: Fri, 27 Jun 2008 11:34:41 -0400
From: "Yiu L. Lee" <yiu_lee@cable.comcast.com>
To: Jean-Francois Mule <jf.mule@cablelabs.com>,
	Otmar Lendl <lendl@nic.at>
Message-ID: <C48A80D1.648%yiu_lee@cable.comcast.com>
Thread-Topic: [Speermint] Comments on
	draft-ietf-speermint-voip-consolidated-usecases-08
Thread-Index: AcjYTG1ODT7lQOSPRCa0/w+L0UkO9wAAiNgwAAcwDK8=
In-Reply-To: <9AAEDF491EF7CA48AB587781B8F5D7C60128FAEC@srvxchg3.cablelabs.com>
Mime-version: 1.0
X-OriginalArrivalTime: 27 Jun 2008 15:34:46.0360 (UTC)
	FILETIME=[54119D80:01C8D86B]
Cc: speermint@ietf.org
Subject: Re: [Speermint] Comments on
 draft-ietf-speermint-voip-consolidated-usecases-08
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/pipermail/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>
Content-Type: multipart/mixed; boundary="===============1611904934=="
Sender: speermint-bounces@ietf.org
Errors-To: speermint-bounces@ietf.org

> 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.

--===============1611904934==
Content-type: multipart/alternative;
	boundary="B_3297411282_621506"

> 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_3297411282_621506
Content-type: text/plain;
	charset="ISO-8859-1"
Content-transfer-encoding: quoted-printable

Hi Jean-Francois,

I got a comment. See in-line.

Thanks.

On 6/27/08 8:19 AM, "Jean-Francois Mule" <jf.mule@cablelabs.com> wrote:

> Otmar wrote:
>=20
>> > -----Original Message-----
>> > From: Otmar Lendl [mailto:lendl@nic.at]
>> > Sent: Friday, June 27, 2008 5:54 AM
>> > To: Jean-Francois Mule
>> > Cc: speermint@ietf.org; adam.uzelac@globalcrossing.com;
>> > yiu_lee@cable.comcast.com
>> > Subject: Re: [Speermint] Comments on draft-ietf-speermint-voip-
>> > consolidated-usecases-08
>> >
>> > Jean-Francois Mule wrote:
>>> > >    Here are some comments based on the draft-08 revision.
>>> >  >
>>> > > 1. Technical comments
>>> > >
>> >
>> > Jean-Francois,
>> >
>> > Your comments question the technical soundness of some the
>> > scenarios
>> > described in this document. That's a valid point, if this were a
>> > document
>> > which describes how speermint envisions peerings to happen in the
>> > future.
>> >
>> > As I see the purpose of this document (see Abstract), it is just
>> > supposed
>> > to just document what's out there, including warts, kludges and
>> > stupidities.
> I read the abstract and got that part fine.  So I would be ok as long as =
it is
> worded as such in the text.
> What concerns me is this:
> In abstract:
>         "This document captures them to provide a reference."
>         =3D> what kind of reference?
>=20
> Then in the intro:
>      "These use cases will assist in identifying requirements and future =
works
> for VoIP Peering using SIP."
>         =3D> that is where I get concerns.
>=20
> On the one hand, the document says: this is what's deployed today in abst=
ract.
> On the other hand, the next paragraphs say: this is going to be used to d=
erive
> requirements. If we are all ok documenting what's in use today, including
> kludges, then let's not say that this is a reference for requirements.
>=20
> [YL] We want to capture what we have today (current practices) in the mar=
ket
> for references. IMHO, what we capture here is to tell what is happening t=
oday.
> We are not defining the requirements because this will be done by require=
ment
> draft. We hope that by showing what we have today can help to identify th=
e
> requirements. I believe that we didn=B9t say this is a reference for
> requirements. We said =B3These use cases will assist in identifying require=
ments
> and future words for VoIP Peering using SIP=B2.  Do you think we should re-=
word
> this sentence to make it more clear? Do you have any good suggestion?
>=20
>> > Thus: whatever conclusions we reached with paf (concerning private
>> > DNS)
>> > doesn't affect what's deployed right now and that's what this
>> > document is about.
>=20
> It does not hurt to then put the right context around such examples and s=
ay
> that while this is deployed, it is preferable to do <this>, where <this> =
is
> something more sound.
>=20
> [YL] Ok, let=B9s work on this in the next draft.
>=20
>=20
>> > So if I'm not mistaken about the purpose of this document, then we
>   Well, as I stated above, you and I have followed the work of working gr=
oup
> to some extent and yet, we both read different things.  Think about this
> document being an RFC, and being read by folks trying to figure out how t=
hey
> could do session peering.  This is where we got to be careful.
>=20
>> > don't
>> > need reviews saying "this is a stupid way to peer", but "nobody is
>> > doing it this way today."
>=20
> Your quotes implied I said this.  I may not recall what I said already bu=
t I
> did not word it that way and folks who have done this that way probably a=
ren't
> stupid.
>=20
> Jean-Fran=E7ois
>> >
>> > /ol
>> > --
>> > // Otmar Lendl <lendl@nic.at>, T: +43 1 5056416 - 33, F: - 933 //
>=20


--B_3297411282_621506
Content-type: text/html;
	charset="ISO-8859-1"
Content-transfer-encoding: quoted-printable

<HTML>
<HEAD>
<TITLE>Re: [Speermint] Comments on draft-ietf-speermint-voip-consolidated-u=
secases-08</TITLE>
</HEAD>
<BODY>
<FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"><SPAN STYLE=3D'font-size:11pt=
'>Hi Jean-Francois,<BR>
<BR>
I got a comment. See in-line.<BR>
<BR>
Thanks.<BR>
<BR>
On 6/27/08 8:19 AM, &quot;Jean-Francois Mule&quot; &lt;<a href=3D"jf.mule@cab=
lelabs.com">jf.mule@cablelabs.com</a>&gt; wrote:<BR>
<BR>
</SPAN></FONT><BLOCKQUOTE><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"><=
SPAN STYLE=3D'font-size:11pt'>Otmar wrote:<BR>
<BR>
&gt; -----Original Message-----<BR>
&gt; From: Otmar Lendl [<a href=3D"mailto:lendl@nic.at">mailto:lendl@nic.at</=
a>]<BR>
&gt; Sent: Friday, June 27, 2008 5:54 AM<BR>
&gt; To: Jean-Francois Mule<BR>
&gt; Cc: <a href=3D"speermint@ietf.org">speermint@ietf.org</a>; <a href=3D"adam=
.uzelac@globalcrossing.com">adam.uzelac@globalcrossing.com</a>;<BR>
&gt; <a href=3D"yiu_lee@cable.comcast.com">yiu_lee@cable.comcast.com</a><BR>
&gt; Subject: Re: [Speermint] Comments on draft-ietf-speermint-voip-<BR>
&gt; consolidated-usecases-08<BR>
&gt;<BR>
&gt; Jean-Francois Mule wrote:<BR>
&gt; &gt; &nbsp;&nbsp;&nbsp;Here are some comments based on the draft-08 re=
vision.<BR>
&gt; &nbsp;&gt;<BR>
&gt; &gt; 1. Technical comments<BR>
&gt; &gt;<BR>
&gt;<BR>
&gt; Jean-Francois,<BR>
&gt;<BR>
&gt; Your comments question the technical soundness of some the<BR>
&gt; scenarios<BR>
&gt; described in this document. That's a valid point, if this were a<BR>
&gt; document<BR>
&gt; which describes how speermint envisions peerings to happen in the<BR>
&gt; future.<BR>
&gt;<BR>
&gt; As I see the purpose of this document (see Abstract), it is just<BR>
&gt; supposed<BR>
&gt; to just document what's out there, including warts, kludges and<BR>
&gt; stupidities.<BR>
I read the abstract and got that part fine. &nbsp;So I would be ok as long =
as it is worded as such in the text.<BR>
What concerns me is this:<BR>
In abstract:<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&quot;This document capture=
s them to provide a reference.&quot;<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=3D&gt; what kind of referenc=
e?<BR>
<BR>
Then in the intro:<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&quot;These use cases will assist in identify=
ing requirements and future works for VoIP Peering using SIP.&quot;<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=3D&gt; that is where I get c=
oncerns.<BR>
<BR>
On the one hand, the document says: this is what's deployed today in abstra=
ct. &nbsp;On the other hand, the next paragraphs say: this is going to be us=
ed to derive requirements. If we are all ok documenting what's in use today,=
 including kludges, then let's not say that this is a reference for requirem=
ents.<BR>
<BR>
<FONT COLOR=3D"#0000FF">[YL] We want to capture what we have today (current p=
ractices) in the market for references. IMHO, what we capture here is to tel=
l what is happening today. We are not defining the requirements because this=
 will be done by requirement draft. We hope that by showing what we have tod=
ay can help to identify the requirements. I believe that we didn&#8217;t say=
 this is a reference for requirements. We said &#8220;These use cases will a=
ssist in identifying requirements and future words for VoIP Peering using SI=
P&#8221;. &nbsp;Do you think we should re-word this sentence to make it more=
 clear? Do you have any good suggestion?<BR>
</FONT><BR>
&gt; Thus: whatever conclusions we reached with paf (concerning private<BR>
&gt; DNS)<BR>
&gt; doesn't affect what's deployed right now and that's what this<BR>
&gt; document is about.<BR>
<BR>
It does not hurt to then put the right context around such examples and say=
 that while this is deployed, it is preferable to do &lt;this&gt;, where &lt=
;this&gt; is something more sound.<BR>
<BR>
<FONT COLOR=3D"#0000FF">[YL] Ok, let&#8217;s work on this in the next draft.<=
BR>
</FONT><BR>
<BR>
&gt; So if I'm not mistaken about the purpose of this document, then we<BR>
&nbsp;&nbsp;Well, as I stated above, you and I have followed the work of wo=
rking group to some extent and yet, we both read different things. &nbsp;Thi=
nk about this document being an RFC, and being read by folks trying to figur=
e out how they could do session peering. &nbsp;This is where we got to be ca=
reful.<BR>
<BR>
&gt; don't<BR>
&gt; need reviews saying &quot;this is a stupid way to peer&quot;, but &quo=
t;nobody is<BR>
&gt; doing it this way today.&quot;<BR>
<BR>
Your quotes implied I said this. &nbsp;I may not recall what I said already=
 but I did not word it that way and folks who have done this that way probab=
ly aren't stupid.<BR>
<BR>
Jean-Fran&ccedil;ois<BR>
&gt;<BR>
&gt; /ol<BR>
&gt; --<BR>
&gt; // Otmar Lendl &lt;<a href=3D"lendl@nic.at">lendl@nic.at</a>&gt;, T: +43=
 1 5056416 - 33, F: - 933 //<BR>
<BR>
</SPAN></FONT></BLOCKQUOTE>
</BODY>
</HTML>


--B_3297411282_621506--


--===============1611904934==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--===============1611904934==--



From speermint-bounces@ietf.org  Fri Jun 27 13:45:13 2008
Return-Path: <speermint-bounces@ietf.org>
X-Original-To: speermint-archive@megatron.ietf.org
Delivered-To: ietfarch-speermint-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 2C6663A6B63;
	Fri, 27 Jun 2008 13:45:13 -0700 (PDT)
X-Original-To: speermint@ietf.org
Delivered-To: speermint@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0)
	id 4B3BF3A6AB9; Fri, 27 Jun 2008 13:45:01 -0700 (PDT)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20080627204502.4B3BF3A6AB9@core3.amsl.com>
Date: Fri, 27 Jun 2008 13:45:02 -0700 (PDT)
Cc: speermint@ietf.org
Subject: [Speermint] I-D Action:draft-ietf-speermint-requirements-05.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/pipermail/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>
Sender: speermint-bounces@ietf.org
Errors-To: speermint-bounces@ietf.org


--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           : SPEERMINT Requirements for SIP-based Session Peering
	Author(s)       : J. Mule
	Filename        : draft-ietf-speermint-requirements-05.txt
	Pages           : 26
	Date            : 2008-06-27

This memo captures protocol requirements identified for enabling
session peering of voice, presence, instant messaging and other types
of multimedia traffic.  It is an informational document linking the
session peering use cases to protocol solutions.

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

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


--NextPart
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--NextPart--


