From pkyzivat@cisco.com Mon Aug 3 10:22:57 2009 Return-Path: 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 7D75628C195 for ; Mon, 3 Aug 2009 10:22:57 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.511 X-Spam-Level: X-Spam-Status: No, score=-6.511 tagged_above=-999 required=5 tests=[AWL=0.088, 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 vkK-q7pfKLHH for ; Mon, 3 Aug 2009 10:22:56 -0700 (PDT) Received: from rtp-iport-1.cisco.com (rtp-iport-1.cisco.com [64.102.122.148]) by core3.amsl.com (Postfix) with ESMTP id 4BCA828C1AB for ; Mon, 3 Aug 2009 10:22:56 -0700 (PDT) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: ApoEAEu6dkpAZnme/2dsb2JhbAC8K4gpjkkFhBg X-IronPort-AV: E=Sophos;i="4.43,315,1246838400"; d="scan'208";a="52720435" Received: from rtp-dkim-1.cisco.com ([64.102.121.158]) by rtp-iport-1.cisco.com with ESMTP; 03 Aug 2009 17:22:58 +0000 Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13]) by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id n73HMwHG015745; Mon, 3 Aug 2009 13:22:58 -0400 Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com [64.102.31.102]) by rtp-core-2.cisco.com (8.13.8/8.14.3) with ESMTP id n73HMwE4009648; Mon, 3 Aug 2009 17:22:58 GMT Received: from xfe-rtp-201.amer.cisco.com ([64.102.31.38]) by xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.3959); Mon, 3 Aug 2009 13:22:58 -0400 Received: from [161.44.174.156] ([161.44.174.156]) by xfe-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.3959); Mon, 3 Aug 2009 13:22:57 -0400 Message-ID: <4A771CF0.6050205@cisco.com> Date: Mon, 03 Aug 2009 13:22:56 -0400 From: Paul Kyzivat User-Agent: Thunderbird 2.0.0.22 (Windows/20090605) MIME-Version: 1.0 To: "Elwell, John" References: <0D5F89FAC29E2C41B98A6A762007F5D00233D618@GBNTHT12009MSX.gb002.siemens.net> In-Reply-To: <0D5F89FAC29E2C41B98A6A762007F5D00233D618@GBNTHT12009MSX.gb002.siemens.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 03 Aug 2009 17:22:57.0768 (UTC) FILETIME=[0B4F5E80:01CA145F] DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1392; t=1249320178; x=1250184178; c=relaxed/simple; s=rtpdkim1001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=pkyzivat@cisco.com; z=From:=20Paul=20Kyzivat=20 |Subject:=20Re=3A=20[Speermint]=20draft-hancock-sip-interco nnect-guideline=20-=20offerless=0A=20INVITE=20requests |Sender:=20 |To:=20=22Elwell,=20John=22=20; bh=3IfMP1Ibn7iNYgnZ53hOm8vrASsAaw1cbfaYM5d4y1c=; b=hYaVl1cwzBX0alUJn2DOKz5mia6jHFZb1NcrR7hfz7dZkvT0A43hYNzmTb G1WRZZgb6b6tDLG7zNokRYI8I1K0ZdmZSIf5pqosOvX8rRcvYXAsz/CT/WSM CGy1RrhqnY; Authentication-Results: rtp-dkim-1; header.From=pkyzivat@cisco.com; dkim=pass ( sig from cisco.com/rtpdkim1001 verified; ); Cc: speermint@ietf.org Subject: Re: [Speermint] draft-hancock-sip-interconnect-guideline - offerless INVITE requests X-BeenThere: speermint@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Mailing list for the speermint working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Aug 2009 17:22:57 -0000 +1 Elwell, John wrote: > One of the points mentioned during this afternoon's presentation was > restricting the scope to basic 2-way call establishment **not** using > 3PCC, which implies no support for offerless INVITE requests. I tried to > make a comment via Jabber, but it was not taken to the mic. > > This would be an unacceptable limitation of the scope. Enterprises make > substantial use of 3PCC techniques, including third party call > establishment. This necessitates an offerless INVITE request to one of > the parties. > > For example, I use my web browser to establish a call to you. The device > I wish to use is my cellphone, so it sends an offerless INVITE request > to, which will be routed to a PSTN gateway. The PSTN gateway returns an > SDP offer that can be used in the INVITE request towards you (who might > also be reachable via a PSTN gateway, or directly via SIP). If the > initial offerless INVITE request is carried inter-domain before reaching > the PSTN gateway, it needs to get through. > > Note that this concern applies not just to enterprise-to-enterprise (if > the scope of the document were to be extended to include this), but to > any interconnect interface. > > John > _______________________________________________ > Speermint mailing list > Speermint@ietf.org > https://www.ietf.org/mailman/listinfo/speermint > From root@core3.amsl.com Mon Aug 24 21:30:01 2009 Return-Path: X-Original-To: speermint@ietf.org Delivered-To: speermint@core3.amsl.com Received: by core3.amsl.com (Postfix, from userid 0) id C579C3A6B5D; Mon, 24 Aug 2009 21:30: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: <20090825043001.C579C3A6B5D@core3.amsl.com> Date: Mon, 24 Aug 2009 21:30:01 -0700 (PDT) Cc: speermint@ietf.org Subject: [Speermint] I-D Action:draft-ietf-speermint-voip-consolidated-usecases-14.txt X-BeenThere: speermint@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Mailing list for the speermint working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Aug 2009 04:30:01 -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-14.txt Pages : 24 Date : 2009-08-24 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. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-speermint-voip-consolidated-usecases-14.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-14.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2009-08-24211744.I-D@ietf.org> --NextPart--