From speermint-bounces@ietf.org Fri Mar 02 12:09:44 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HNBFY-0005yS-1l; Fri, 02 Mar 2007 12:08:56 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HNBFW-0005qy-HK for speermint@ietf.org; Fri, 02 Mar 2007 12:08:54 -0500 Received: from smtp0.netlab.nec.de ([195.37.70.40]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HNBFT-0002xu-Uq for speermint@ietf.org; Fri, 02 Mar 2007 12:08:54 -0500 Received: from localhost (atlas1.office [127.0.0.1]) by smtp0.netlab.nec.de (Postfix) with ESMTP id 9A7432004BFC for ; Fri, 2 Mar 2007 18:09:31 +0100 (CET) X-Virus-Scanned: Amavisd on Debian GNU/Linux (atlas1.office) Received: from smtp0.netlab.nec.de ([127.0.0.1]) by localhost (atlas1.office [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id k--2O+66bzGj for ; Fri, 2 Mar 2007 18:09:31 +0100 (CET) Received: from mx1.office (mx1.office [10.1.1.23]) by smtp0.netlab.nec.de (Postfix) with ESMTP id 78AA720001B6 for ; Fri, 2 Mar 2007 18:09:31 +0100 (CET) X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----_=_NextPart_001_01C75CED.7210F533" Date: Fri, 2 Mar 2007 18:08:47 +0100 Message-ID: <113091BD57179D4491C19DA7E10CD696BD9FAF@mx1.office> X-MS-Has-Attach: yes X-MS-TNEF-Correlator: Thread-Topic: I-D ACTION:draft-niccolini-speermint-voipthreats-01.txt Thread-Index: AcdcTSm8hFDLaep+T1+MpFWLaPUh0QAn5lRg From: "Saverio Niccolini" To: X-Spam-Score: 0.0 (/) X-Scan-Signature: a1852b4f554b02e7e4548cc7928acc1f Subject: [Speermint] FW: I-D ACTION:draft-niccolini-speermint-voipthreats-01.txt X-BeenThere: speermint@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mailing list for the speermint working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: speermint-bounces@ietf.org This is a multi-part message in MIME format. ------_=_NextPart_001_01C75CED.7210F533 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Dear all, I submitted a second version of the VoIP Security threats draft after doing a lot of work helped by Eric Chen (NTT). I would appreciate if you could find some time to discuss on the mailing list if you like the new approach we took and what are the problems/things you like. The major changes are: -- adaptation of the threats to the SPEERMINT architecture (LF, SF, MF) -- introduction of SPEERMINT specific threats We think this draft is now ready to have more discussion within the list and we would appreciate you to find some time for this. Cheers, Saverio =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Dr. Saverio Niccolini Senior Research Staff Member Network Laboratories, NEC Europe Ltd. Kurfuerstenanlage 36, D-69115 Heidelberg Tel. +49 (0)6221 4342-118 Fax: +49 (0)6221 4342-155 e-mail: saverio.niccolini@netlab.nec.de =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D NEC Europe Limited Registered Office: NEC House, 1 Victoria Road, London W3 6BL Registered in England 2832014 =20 > -----Original Message----- > From: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org]=20 > Sent: Thursday, March 01, 2007 9:50 PM > To: i-d-announce@ietf.org > Subject: I-D ACTION:draft-niccolini-speermint-voipthreats-01.txt=20 >=20 > A New Internet-Draft is available from the on-line Internet-Drafts=20 > directories. >=20 >=20 > Title : VoIP Security Threats relevant to SPEERMINT > Author(s) : E. Chen, S. Niccolini > Filename : draft-niccolini-speermint-voipthreats-01.txt > Pages : 19 > Date : 2007-3-1 > =09 > This memo presents the different security threats related to > SPEERMINT classifying them into threats to the Location=20 > Function, to > the Signaling Function and to the Media Function. The different > instances of the threats are briefly introduced inside the > classification. Finally the existing security solutions in SIP and > RTP/RTCP are presented to describe the countermeasures currently > available for such threats. The objective of this document is to > identify and enumerate the SPEERMINT-specific threat=20 > vectors in order > to specify security-related requirements. Once the=20 > requirements are > identified, methods and solutions how to achieve such requirements > can be selected. >=20 > A URL for this Internet-Draft is: > = http://www.ietf.org/internet-drafts/draft-niccolini-speermint-voipthreats= -01.txt >=20 > To remove yourself from the I-D Announcement list, send a message to=20 > i-d-announce-request@ietf.org with the word unsubscribe in=20 > the body of=20 > the message.=20 > You can also visit=20 > https://www1.ietf.org/mailman/listinfo/I-D-announce=20 > to change your subscription settings. >=20 > Internet-Drafts are also available by anonymous FTP. Login with the=20 > username "anonymous" and a password of your e-mail address. After=20 > logging in, type "cd internet-drafts" and then=20 > "get draft-niccolini-speermint-voipthreats-01.txt". >=20 > A list of Internet-Drafts directories can be found in > http://www.ietf.org/shadow.html=20 > or ftp://ftp.ietf.org/ietf/1shadow-sites.txt >=20 > Internet-Drafts can also be obtained by e-mail. >=20 > Send a message to: > mailserv@ietf.org. > In the body type: > "FILE=20 > /internet-drafts/draft-niccolini-speermint-voipthreats-01.txt". > =09 > NOTE: The mail server at ietf.org can return the document in > MIME-encoded form by using the "mpack" utility. To use this > feature, insert the command "ENCODING mime" before the "FILE" > command. To decode the response(s), you will need "munpack" or > a MIME-compliant mail reader. Different MIME-compliant=20 > mail readers > exhibit different behavior, especially when dealing with > "multipart" MIME messages (i.e. documents which have been split > up into multiple messages), so check your local documentation on > how to manipulate these messages. >=20 > Below is the data which will enable a MIME compliant mail reader > implementation to automatically retrieve the ASCII version of the > Internet-Draft. >=20 ------_=_NextPart_001_01C75CED.7210F533 Content-Type: application/octet-stream; name="draft-niccolini-speermint-voipthreats-01.URL" Content-Transfer-Encoding: base64 Content-Description: draft-niccolini-speermint-voipthreats-01.URL Content-Disposition: attachment; filename="draft-niccolini-speermint-voipthreats-01.URL" W0ludGVybmV0U2hvcnRjdXRdDQpVUkw9ZnRwOi8vZnRwLmlldGYub3JnL2ludGVybmV0LWRyYWZ0 cy9kcmFmdC1uaWNjb2xpbmktc3BlZXJtaW50LXZvaXB0aHJlYXRzLTAxLnR4dA0K ------_=_NextPart_001_01C75CED.7210F533 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://www1.ietf.org/mailman/listinfo/speermint ------_=_NextPart_001_01C75CED.7210F533-- From speermint-bounces@ietf.org Fri Mar 02 15:55:24 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HNEmD-0007AO-5R; Fri, 02 Mar 2007 15:54:53 -0500 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HNEi1-0001GM-83; Fri, 02 Mar 2007 15:50:33 -0500 Received: from ns4.neustar.com ([156.154.24.139]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1HNEi0-0003OX-Nt; Fri, 02 Mar 2007 15:50:33 -0500 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns4.neustar.com (Postfix) with ESMTP id A33812AD58; Fri, 2 Mar 2007 20:50:02 +0000 (GMT) Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1HNEhW-0002Vs-D1; Fri, 02 Mar 2007 15:50:02 -0500 Content-Type: Multipart/Mixed; Boundary="NextPart" Mime-Version: 1.0 To: i-d-announce@ietf.org From: Internet-Drafts@ietf.org Message-Id: Date: Fri, 02 Mar 2007 15:50:02 -0500 X-Spam-Score: -2.5 (--) X-Scan-Signature: 31247fb3be228bb596db9127becad0bc Cc: speermint@ietf.org Subject: [Speermint] I-D ACTION:draft-ietf-speermint-voip-consolidated-usecases-00.txt X-BeenThere: speermint@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mailing list for the speermint working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , 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 : VoIP SIP Peering Use Cases Author(s) : A. Uzelac, et al. Filename : draft-ietf-speermint-voip-consolidated-usecases-00.txt Pages : 21 Date : 2007-3-2 This document will capture the VoIP use case for SIP Peering. It is a consolidation of other Speermint use cases and will focus exclusively on VoIP. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-speermint-voip-consolidated-usecases-00.txt To remove yourself from the I-D Announcement list, send a message to i-d-announce-request@ietf.org with the word unsubscribe in the body of the message. You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce to change your subscription settings. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-speermint-voip-consolidated-usecases-00.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-speermint-voip-consolidated-usecases-00.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. 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: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2007-3-2105845.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-speermint-voip-consolidated-usecases-00.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-speermint-voip-consolidated-usecases-00.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2007-3-2105845.I-D@ietf.org> --OtherAccess-- --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://www1.ietf.org/mailman/listinfo/speermint --NextPart-- From speermint-bounces@ietf.org Sun Mar 11 23:21:20 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HQb59-0001S5-7z; Sun, 11 Mar 2007 23:20:19 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HQb57-0001Rz-LR for speermint@ietf.org; Sun, 11 Mar 2007 23:20:17 -0400 Received: from sj-iport-5.cisco.com ([171.68.10.87]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HQb54-0007ZU-C1 for speermint@ietf.org; Sun, 11 Mar 2007 23:20:17 -0400 Received: from sj-dkim-4.cisco.com ([171.71.179.196]) by sj-iport-5.cisco.com with ESMTP; 11 Mar 2007 20:20:15 -0700 X-IronPort-AV: i="4.14,271,1170662400"; d="scan'208"; a="400082586:sNHT41918728" Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254]) by sj-dkim-4.cisco.com (8.12.11/8.12.11) with ESMTP id l2C3KDVp012504 for ; Sun, 11 Mar 2007 20:20:13 -0700 Received: from [192.168.4.177] (sjc-fluffy-vpn1.cisco.com [10.25.236.82]) by sj-core-2.cisco.com (8.12.10/8.12.6) with SMTP id l2C3KC1U023542 for ; Mon, 12 Mar 2007 03:20:12 GMT Mime-Version: 1.0 (Apple Message framework v752.3) Content-Transfer-Encoding: 7bit Message-Id: <5BC9F4A7-8B4A-4D91-B4BA-D4D70559C16B@cisco.com> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed To: speermint@ietf.org From: Cullen Jennings Date: Sun, 11 Mar 2007 20:19:46 -0700 X-Mailer: Apple Mail (2.752.3) DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=950; t=1173669613; x=1174533613; c=relaxed/simple; s=sjdkim4002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=fluffy@cisco.com; z=From:=20Cullen=20Jennings=20 |Subject:=20Comments=20on=20draft-newton-peppermint-problem-statement-00= 20and=20draft-schwartz-peppermint-e164-provisioning-data-set-00 |Sender:=20; bh=tcmOPvcjsPlEczY9TyvjcRtTG3ZMHEpnr+T0F2GCYJY=; b=SK/4wqjEVutJmsMZYASR+To+c42IIguo2cockaLBArG9GXzTsUMuCh0JBt6gNzaOySIn3fh8 kHB4w4GkjL23k7Nm/WvnCgMZaEIB6cB/lgA7kNWPl3rrtRc6XiS2NzS1; Authentication-Results: sj-dkim-4; header.From=fluffy@cisco.com; dkim=pass ( sig from cisco.com/sjdkim4002 verified; ); X-Spam-Score: 1.1 (+) X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581 Subject: [Speermint] Comments on draft-newton-peppermint-problem-statement-00 and draft-schwartz-peppermint-e164-provisioning-data-set-00 X-BeenThere: speermint@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mailing list for the speermint working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: speermint-bounces@ietf.org Many of my questions about the newton doc where answered by the schwartz doc and visa versa - they are nicely synchronized. I hope there is some thought to just combining these. Stuff that was unclear to me revolved around who the different actors are and who is allowed to provision what - I trying to get at what the trust model is and who trusts what from who and why. The whole ownership concept seem to be imply a someone different model that I have seen in existing IETF work - similarly with the view/profile stuff. The document has some stuff about the bits needed and that is very helpful to understand, but would be nice to also have more on who the actors are and what information they can provide and receive in different views. Trivial note on time-zones - if you can avoid them and make all times in UTC or something like that, things will be easier. Cullen _______________________________________________ Speermint mailing list Speermint@ietf.org https://www1.ietf.org/mailman/listinfo/speermint From speermint-bounces@ietf.org Mon Mar 12 09:25:39 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HQkWX-0005oD-Ru; Mon, 12 Mar 2007 09:25:13 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HQkWW-0005o8-OB for speermint@ietf.org; Mon, 12 Mar 2007 09:25:12 -0400 Received: from mail120.messagelabs.com ([216.82.250.83]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1HQkUY-0000wJ-3H for speermint@ietf.org; Mon, 12 Mar 2007 09:23:11 -0400 X-VirusChecked: Checked X-Env-Sender: ppfautz@att.com X-Msg-Ref: server-7.tower-120.messagelabs.com!1173705788!20121112!1 X-StarScan-Version: 5.5.10.7.1; banners=-,-,- X-Originating-IP: [134.24.146.4] Received: (qmail 11362 invoked from network); 12 Mar 2007 13:23:08 -0000 Received: from unknown (HELO attrh0i.attrh.att.com) (134.24.146.4) by server-7.tower-120.messagelabs.com with SMTP; 12 Mar 2007 13:23:08 -0000 Received: from attrh.att.com (localhost [127.0.0.1]) by attrh0i.attrh.att.com (8.13.8/8.13.8) with ESMTP id l2CDN8xc023717; Mon, 12 Mar 2007 09:23:08 -0400 (EDT) Received: from ACCLUST02EVS1.ugd.att.com (acst04.ugd.att.com [135.37.16.9]) by attrh0i.attrh.att.com (8.13.8/8.13.8) with ESMTP id l2CDN32c023664; Mon, 12 Mar 2007 09:23:03 -0400 (EDT) X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: RE: [Speermint] Comments ondraft-newton-peppermint-problem-statement-00 anddraft-schwartz-peppermint-e164-provisioning-data-set-00 Date: Mon, 12 Mar 2007 09:23:02 -0400 Message-ID: <34DA635B184A644DA4588E260EC0A25A0EEAC93A@ACCLUST02EVS1.ugd.att.com> In-Reply-To: <5BC9F4A7-8B4A-4D91-B4BA-D4D70559C16B@cisco.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [Speermint] Comments ondraft-newton-peppermint-problem-statement-00 anddraft-schwartz-peppermint-e164-provisioning-data-set-00 Thread-Index: AcdkVc333h91ExSnTQuZZqrnh4guQgAUTaww From: "PFAUTZ, PENN L, ATTCORP" To: "Cullen Jennings" , X-Spam-Score: 1.1 (+) X-Scan-Signature: 538aad3a3c4f01d8b6a6477ca4248793 Cc: X-BeenThere: speermint@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mailing list for the speermint working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: speermint-bounces@ietf.org One problem with the Lewis draft and these other drafts is that they elide some of the larger context of work on ENUM. They clearly aren't speaking to user ENUM (RFC 3761). References to ownership of numbers suggests an Infrastructure ENUM focus, but it seems to be a private ENUM rather than a public one. It includes the suggestion of differential response but with the assumption that that will be handled in the Registry rather than somewhere else in the resolution chain. These issues and the choices about how to resolve them (no pun intended :-) are important but I would like to see them more clearly stated so as to encourage a real debate about the architecture model as opposed to a rush to picking an implementation. =20 Penn Pfautz AT&T Global Access Management +1-732-420-4962 -----Original Message----- From: Cullen Jennings [mailto:fluffy@cisco.com]=20 Sent: Sunday, March 11, 2007 11:20 PM To: speermint@ietf.org Subject: [Speermint] Comments ondraft-newton-peppermint-problem-statement-00 anddraft-schwartz-peppermint-e164-provisioning-data-set-00 Many of my questions about the newton doc where answered by the =20 schwartz doc and visa versa - they are nicely synchronized. I hope =20 there is some thought to just combining these. Stuff that was unclear to me revolved around who the different actors =20 are and who is allowed to provision what - I trying to get at what =20 the trust model is and who trusts what from who and why. The whole ownership concept seem to be imply a someone different =20 model that I have seen in existing IETF work - similarly with the =20 view/profile stuff. The document has some stuff about the bits needed =20 and that is very helpful to understand, but would be nice to also =20 have more on who the actors are and what information they can provide =20 and receive in different views. Trivial note on time-zones - if you can avoid them and make all times =20 in UTC or something like that, things will be easier. Cullen =09 _______________________________________________ Speermint mailing list Speermint@ietf.org https://www1.ietf.org/mailman/listinfo/speermint _______________________________________________ Speermint mailing list Speermint@ietf.org https://www1.ietf.org/mailman/listinfo/speermint From speermint-bounces@ietf.org Mon Mar 12 10:03:42 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HQl7R-0000N1-In; Mon, 12 Mar 2007 10:03:21 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HQl7Q-0000HH-9f for speermint@ietf.org; Mon, 12 Mar 2007 10:03:20 -0400 Received: from bzq-25-94-44.static.bezeqint.net ([212.25.94.44] helo=isr-jlm-mail.Kayote.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HQl7N-0003jF-MS for speermint@ietf.org; Mon, 12 Mar 2007 10:03:20 -0400 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: RE: [Speermint] Commentsondraft-newton-peppermint-problem-statement-00anddraft-schwartz-peppermint-e164-provisioning-data-set-00 Date: Mon, 12 Mar 2007 16:03:01 +0200 Message-ID: <1DDB0D3CC4E7F14FAE946361C0A606550249F904@isr-jlm-mail.Kayote.com> In-Reply-To: <34DA635B184A644DA4588E260EC0A25A0EEAC93A@ACCLUST02EVS1.ugd.att.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [Speermint] Commentsondraft-newton-peppermint-problem-statement-00anddraft-schwartz-peppermint-e164-provisioning-data-set-00 Thread-Index: AcdkVc333h91ExSnTQuZZqrnh4guQgAUTawwAAFqGLA= References: <5BC9F4A7-8B4A-4D91-B4BA-D4D70559C16B@cisco.com> <34DA635B184A644DA4588E260EC0A25A0EEAC93A@ACCLUST02EVS1.ugd.att.com> From: "David Schwartz" To: "PFAUTZ, PENN L, ATTCORP" , "Cullen Jennings" , X-Spam-Score: 1.2 (+) X-Scan-Signature: b5d20af10c334b36874c0264b10f59f1 Cc: X-BeenThere: speermint@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mailing list for the speermint working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: speermint-bounces@ietf.org Hi Penn. I reread the draft I wrote and found no mention of either private or infrastructure ENUM. The closest match was the following snippet... QueryType There are many protocols that can be used to perform the query. While ENUM is one of the more popular protocols there is no reason other protocols (e.g. SIP 302) cannot be used as well. Thus the Type of Query field indicates which protocol will be used for this profile. I am not even sure that ENUM can provide the flexibility required in practice (e.g. the differential response you allude to). The document I wrote is informational in nature and its purpose is merely to highlight some of the information that may need to be captured in a provisioning process. Included in that information is "ownership" as in some implementations (such as I-ENUM) this has value. The document does not get involved in the private Vs. Infrastructure Vs Public ENUM debate. Cheers, D. -----Original Message----- From: PFAUTZ, PENN L, ATTCORP [mailto:ppfautz@att.com]=20 Sent: Monday, March 12, 2007 3:23 PM To: Cullen Jennings; speermint@ietf.org Subject: RE: [Speermint] Commentsondraft-newton-peppermint-problem-statement-00anddraft-schwartz- peppermint-e164-provisioning-data-set-00 One problem with the Lewis draft and these other drafts is that they elide some of the larger context of work on ENUM. They clearly aren't speaking to user ENUM (RFC 3761). References to ownership of numbers suggests an Infrastructure ENUM focus, but it seems to be a private ENUM rather than a public one. It includes the suggestion of differential response but with the assumption that that will be handled in the Registry rather than somewhere else in the resolution chain. These issues and the choices about how to resolve them (no pun intended :-) are important but I would like to see them more clearly stated so as to encourage a real debate about the architecture model as opposed to a rush to picking an implementation. =20 Penn Pfautz AT&T Global Access Management +1-732-420-4962 -----Original Message----- From: Cullen Jennings [mailto:fluffy@cisco.com]=20 Sent: Sunday, March 11, 2007 11:20 PM To: speermint@ietf.org Subject: [Speermint] Comments ondraft-newton-peppermint-problem-statement-00 anddraft-schwartz-peppermint-e164-provisioning-data-set-00 Many of my questions about the newton doc where answered by the =20 schwartz doc and visa versa - they are nicely synchronized. I hope =20 there is some thought to just combining these. Stuff that was unclear to me revolved around who the different actors =20 are and who is allowed to provision what - I trying to get at what =20 the trust model is and who trusts what from who and why. The whole ownership concept seem to be imply a someone different =20 model that I have seen in existing IETF work - similarly with the =20 view/profile stuff. The document has some stuff about the bits needed =20 and that is very helpful to understand, but would be nice to also =20 have more on who the actors are and what information they can provide =20 and receive in different views. Trivial note on time-zones - if you can avoid them and make all times =20 in UTC or something like that, things will be easier. Cullen =09 _______________________________________________ Speermint mailing list Speermint@ietf.org https://www1.ietf.org/mailman/listinfo/speermint _______________________________________________ Speermint mailing list Speermint@ietf.org https://www1.ietf.org/mailman/listinfo/speermint _______________________________________________ Speermint mailing list Speermint@ietf.org https://www1.ietf.org/mailman/listinfo/speermint From speermint-bounces@ietf.org Mon Mar 12 12:37:24 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HQnW0-0005Sp-AX; Mon, 12 Mar 2007 12:36:52 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HQnVy-0005Qw-SE for speermint@ietf.org; Mon, 12 Mar 2007 12:36:50 -0400 Received: from zeke.hxr.us ([69.31.8.124] helo=zeke.ecotroph.net) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HQnVZ-0007MK-8X for speermint@ietf.org; Mon, 12 Mar 2007 12:36:50 -0400 Received: from [172.16.9.198] ([::ffff:208.50.38.5]) (AUTH: PLAIN anewton, SSL: TLSv1/SSLv3,128bits,AES128-SHA) by zeke.ecotroph.net with esmtp; Mon, 12 Mar 2007 12:33:36 -0400 id 01588123.45F580E0.000070E1 In-Reply-To: <34DA635B184A644DA4588E260EC0A25A0EEAC93A@ACCLUST02EVS1.ugd.att.com> References: <34DA635B184A644DA4588E260EC0A25A0EEAC93A@ACCLUST02EVS1.ugd.att.com> Mime-Version: 1.0 (Apple Message framework v752.3) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Andrew Newton Subject: Re: [Speermint] Comments ondraft-newton-peppermint-problem-statement-00 anddraft-schwartz-peppermint-e164-provisioning-data-set-00 Date: Mon, 12 Mar 2007 12:36:12 -0400 To: "PFAUTZ, PENN L, ATTCORP" X-Mailer: Apple Mail (2.752.3) X-Spam-Score: 1.2 (+) X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22 Cc: speermint@ietf.org X-BeenThere: speermint@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mailing list for the speermint working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: speermint-bounces@ietf.org On Mar 12, 2007, at 9:23 AM, PFAUTZ, PENN L, ATTCORP wrote: > One problem with the Lewis draft and these other drafts is that they > elide some of the larger context of work on ENUM. > They clearly aren't speaking to user ENUM (RFC 3761). References to > ownership of numbers suggests an Infrastructure ENUM focus, but it > seems > to be a private ENUM rather than a public one. It includes the > suggestion of differential response but with the assumption that that > will be handled in the Registry rather than somewhere else in the > resolution chain. > These issues and the choices about how to resolve them (no pun > intended > :-) are important but I would like to see them more clearly stated > so as > to encourage a real debate about the architecture model as opposed > to a > rush to picking an implementation. Penn, Is your objection that the draft(s) are not clear about the use of user ENUM vs infrastructure ENUM vs private ENUM? Or are you objecting to the work being usable and/or targeted against private ENUM trees? -andy _______________________________________________ Speermint mailing list Speermint@ietf.org https://www1.ietf.org/mailman/listinfo/speermint From speermint-bounces@ietf.org Mon Mar 12 12:48:43 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HQnhA-0006rb-A6; Mon, 12 Mar 2007 12:48:24 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HQnh8-0006rW-Kx for speermint@ietf.org; Mon, 12 Mar 2007 12:48:22 -0400 Received: from mail121.messagelabs.com ([216.82.241.195]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1HQnh7-0000gg-Cg for speermint@ietf.org; Mon, 12 Mar 2007 12:48:22 -0400 X-VirusChecked: Checked X-Env-Sender: ppfautz@att.com X-Msg-Ref: server-3.tower-121.messagelabs.com!1173718100!21765079!1 X-StarScan-Version: 5.5.10.7.1; banners=-,-,- X-Originating-IP: [134.24.146.4] Received: (qmail 8497 invoked from network); 12 Mar 2007 16:48:20 -0000 Received: from unknown (HELO attrh0i.attrh.att.com) (134.24.146.4) by server-3.tower-121.messagelabs.com with SMTP; 12 Mar 2007 16:48:20 -0000 Received: from attrh.att.com (localhost [127.0.0.1]) by attrh0i.attrh.att.com (8.13.8/8.13.8) with ESMTP id l2CGmKW0020421; Mon, 12 Mar 2007 12:48:20 -0400 (EDT) Received: from ACCLUST02EVS1.ugd.att.com (acst04.ugd.att.com [135.37.16.9]) by attrh0i.attrh.att.com (8.13.8/8.13.8) with ESMTP id l2CGmA32020334; Mon, 12 Mar 2007 12:48:10 -0400 (EDT) X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: RE: [Speermint] Comments ondraft-newton-peppermint-problem-statement-00 anddraft-schwartz-peppermint-e164-provisioning-data-set-00 Date: Mon, 12 Mar 2007 12:48:08 -0400 Message-ID: <34DA635B184A644DA4588E260EC0A25A0EEACD56@ACCLUST02EVS1.ugd.att.com> In-Reply-To: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [Speermint] Comments ondraft-newton-peppermint-problem-statement-00 anddraft-schwartz-peppermint-e164-provisioning-data-set-00 Thread-Index: AcdkxJLI9LRZKsoBSJ6xLyVApdCzIgAAIwiQ From: "PFAUTZ, PENN L, ATTCORP" To: "Andrew Newton" X-Spam-Score: 1.1 (+) X-Scan-Signature: 8b431ad66d60be2d47c7bfeb879db82c Cc: speermint@ietf.org X-BeenThere: speermint@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mailing list for the speermint working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: speermint-bounces@ietf.org Andy: Really just looking for a fuller definition of context and intended use. I have no desire to prohibit anything. I would like to see a discussion of merits and demerits of doing policy in the Registry, for example, versus through subsequent resolution of what is obtained from the Registry as this is an important technical issue that most of us will have to make a decision about.=20 Penn Penn Pfautz AT&T Global Access Management +1-732-420-4962 -----Original Message----- From: Andrew Newton [mailto:andy@hxr.us]=20 Sent: Monday, March 12, 2007 12:36 PM To: PFAUTZ, PENN L, ATTCORP Cc: Cullen Jennings; speermint@ietf.org Subject: Re: [Speermint] Comments ondraft-newton-peppermint-problem-statement-00 anddraft-schwartz-peppermint-e164-provisioning-data-set-00 On Mar 12, 2007, at 9:23 AM, PFAUTZ, PENN L, ATTCORP wrote: > One problem with the Lewis draft and these other drafts is that they > elide some of the larger context of work on ENUM. > They clearly aren't speaking to user ENUM (RFC 3761). References to > ownership of numbers suggests an Infrastructure ENUM focus, but it =20 > seems > to be a private ENUM rather than a public one. It includes the > suggestion of differential response but with the assumption that that > will be handled in the Registry rather than somewhere else in the > resolution chain. > These issues and the choices about how to resolve them (no pun =20 > intended > :-) are important but I would like to see them more clearly stated =20 > so as > to encourage a real debate about the architecture model as opposed =20 > to a > rush to picking an implementation. Penn, Is your objection that the draft(s) are not clear about the use of =20 user ENUM vs infrastructure ENUM vs private ENUM? Or are you =20 objecting to the work being usable and/or targeted against private =20 ENUM trees? -andy _______________________________________________ Speermint mailing list Speermint@ietf.org https://www1.ietf.org/mailman/listinfo/speermint From speermint-bounces@ietf.org Mon Mar 12 13:13:54 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HQo5P-0000JB-Ma; Mon, 12 Mar 2007 13:13:27 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HQo5O-0000J4-G9 for speermint@ietf.org; Mon, 12 Mar 2007 13:13:26 -0400 Received: from zeke.ecotroph.net ([69.31.8.124]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HQo5L-0003hK-B0 for speermint@ietf.org; Mon, 12 Mar 2007 13:13:26 -0400 Received: from [172.16.9.198] ([::ffff:208.50.38.5]) (AUTH: PLAIN anewton, SSL: TLSv1/SSLv3,128bits,AES128-SHA) by zeke.ecotroph.net with esmtp; Mon, 12 Mar 2007 13:10:44 -0400 id 01588135.45F58994.0000796A In-Reply-To: <34DA635B184A644DA4588E260EC0A25A0EEACD56@ACCLUST02EVS1.ugd.att.com> References: <34DA635B184A644DA4588E260EC0A25A0EEACD56@ACCLUST02EVS1.ugd.att.com> Mime-Version: 1.0 (Apple Message framework v752.3) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <750D30D6-375C-4A5B-AF93-9C0870E3F4A6@hxr.us> Content-Transfer-Encoding: 7bit From: Andrew Newton Subject: Re: [Speermint] Comments ondraft-newton-peppermint-problem-statement-00 anddraft-schwartz-peppermint-e164-provisioning-data-set-00 Date: Mon, 12 Mar 2007 13:13:20 -0400 To: "PFAUTZ, PENN L, ATTCORP" X-Mailer: Apple Mail (2.752.3) X-Spam-Score: 1.1 (+) X-Scan-Signature: f60d0f7806b0c40781eee6b9cd0b2135 Cc: speermint@ietf.org X-BeenThere: speermint@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mailing list for the speermint working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: speermint-bounces@ietf.org Penn, To answer your question with regard to how it works today, it works both ways in many cases. The registries apply policy on their side, and those querying the registry apply policy post-dip. However, neither change the actual query. With the policies that are applied on both sides for which I am aware, non change the query protocol. What technical issues are you concerned about? -andy On Mar 12, 2007, at 12:48 PM, PFAUTZ, PENN L, ATTCORP wrote: > Andy: > Really just looking for a fuller definition of context and intended > use. > I have no desire to prohibit anything. > I would like to see a discussion of merits and demerits of doing > policy > in the Registry, for example, versus through subsequent resolution of > what is obtained from the Registry as this is an important technical > issue that most of us will have to make a decision about. > > Penn > > Penn Pfautz > AT&T Global Access Management > +1-732-420-4962 > > -----Original Message----- > From: Andrew Newton [mailto:andy@hxr.us] > Sent: Monday, March 12, 2007 12:36 PM > To: PFAUTZ, PENN L, ATTCORP > Cc: Cullen Jennings; speermint@ietf.org > Subject: Re: [Speermint] Comments > ondraft-newton-peppermint-problem-statement-00 > anddraft-schwartz-peppermint-e164-provisioning-data-set-00 > > > On Mar 12, 2007, at 9:23 AM, PFAUTZ, PENN L, ATTCORP wrote: > >> One problem with the Lewis draft and these other drafts is that they >> elide some of the larger context of work on ENUM. >> They clearly aren't speaking to user ENUM (RFC 3761). References to >> ownership of numbers suggests an Infrastructure ENUM focus, but it >> seems >> to be a private ENUM rather than a public one. It includes the >> suggestion of differential response but with the assumption that that >> will be handled in the Registry rather than somewhere else in the >> resolution chain. >> These issues and the choices about how to resolve them (no pun >> intended >> :-) are important but I would like to see them more clearly stated >> so as >> to encourage a real debate about the architecture model as opposed >> to a >> rush to picking an implementation. > > Penn, > > Is your objection that the draft(s) are not clear about the use of > user ENUM vs infrastructure ENUM vs private ENUM? Or are you > objecting to the work being usable and/or targeted against private > ENUM trees? > > -andy _______________________________________________ Speermint mailing list Speermint@ietf.org https://www1.ietf.org/mailman/listinfo/speermint From speermint-bounces@ietf.org Mon Mar 12 13:24:06 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HQoFP-00009d-HI; Mon, 12 Mar 2007 13:23:47 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HQoFO-00008p-L6; Mon, 12 Mar 2007 13:23:46 -0400 Received: from sb7.songbird.com ([208.184.79.137]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HQoFL-0005Qj-98; Mon, 12 Mar 2007 13:23:46 -0400 Received: from RSHOCKEYLTXP (neustargw.va.neustar.com [209.173.53.233]) by sb7.songbird.com (8.12.11.20060308/8.12.11) with ESMTP id l2CHNHZF028382; Mon, 12 Mar 2007 09:23:24 -0800 From: "Richard Shockey" To: "'PFAUTZ, PENN L, ATTCORP'" , "'Andrew Newton'" References: <34DA635B184A644DA4588E260EC0A25A0EEACD56@ACCLUST02EVS1.ugd.att.com> Subject: RE: [Speermint] Commentsondraft-newton-peppermint-problem-statement-00anddraft-schwartz-peppermint-e164-provisioning-data-set-00 Date: Mon, 12 Mar 2007 13:23:18 -0400 Message-ID: <030601c764cb$212d3ce0$84201f0a@cis.neustar.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028 Thread-Index: AcdkxJLI9LRZKsoBSJ6xLyVApdCzIgAAIwiQAAFyHZA= In-Reply-To: <34DA635B184A644DA4588E260EC0A25A0EEACD56@ACCLUST02EVS1.ugd.att.com> X-SongbirdInformation: support@songbird.com for more information X-Songbird: Clean X-Songbird-From: richard@shockey.us X-Spam-Score: 1.1 (+) X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228 Cc: speermint@ietf.org, peppermint@ietf.org X-BeenThere: speermint@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: richard@shockey.us List-Id: Mailing list for the speermint working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: speermint-bounces@ietf.org Which I hope I can take as your support for forming a PEPPERMINT BOF in Chicago? :-) > -----Original Message----- > From: PFAUTZ, PENN L, ATTCORP [mailto:ppfautz@att.com] > Sent: Monday, March 12, 2007 12:48 PM > To: Andrew Newton > Cc: speermint@ietf.org > Subject: RE: [Speermint] Commentsondraft-newton-peppermint-problem- > statement-00anddraft-schwartz-peppermint-e164-provisioning-data-set-00 > > Andy: > Really just looking for a fuller definition of context and intended use. > I have no desire to prohibit anything. > I would like to see a discussion of merits and demerits of doing policy > in the Registry, for example, versus through subsequent resolution of > what is obtained from the Registry as this is an important technical > issue that most of us will have to make a decision about. > > Penn > > Penn Pfautz > AT&T Global Access Management > +1-732-420-4962 > > _______________________________________________ > Speermint mailing list > Speermint@ietf.org > https://www1.ietf.org/mailman/listinfo/speermint _______________________________________________ Speermint mailing list Speermint@ietf.org https://www1.ietf.org/mailman/listinfo/speermint From speermint-bounces@ietf.org Tue Mar 13 11:15:08 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HR8hg-0002nK-Fh; Tue, 13 Mar 2007 11:14:20 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HR8hf-0002kV-21 for speermint@ietf.org; Tue, 13 Mar 2007 11:14:19 -0400 Received: from smtp0.netlab.nec.de ([195.37.70.40]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HR8hd-00008g-Em for speermint@ietf.org; Tue, 13 Mar 2007 11:14:19 -0400 Received: from localhost (atlas1.office [127.0.0.1]) by smtp0.netlab.nec.de (Postfix) with ESMTP id B24262009117; Tue, 13 Mar 2007 14:33:51 +0100 (CET) X-Virus-Scanned: Amavisd on Debian GNU/Linux (atlas1.office) Received: from smtp0.netlab.nec.de ([127.0.0.1]) by localhost (atlas1.office [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rc2i7F3Ye+pQ; Tue, 13 Mar 2007 14:33:51 +0100 (CET) Received: from mx1.office (chiba.netlab.nec.de [10.1.1.23]) by smtp0.netlab.nec.de (Postfix) with ESMTP id 90A9B200909C; Tue, 13 Mar 2007 14:33:36 +0100 (CET) Date: Tue, 13 Mar 2007 14:14:28 +0100 Message-ID: <113091BD57179D4491C19DA7E10CD696BDA9BA@mx1.office> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable In-Reply-To: <113091BD57179D4491C19DA7E10CD696BD9FAF@mx1.office> X-MS-Has-Attach: X-MS-TNEF-Correlator: Content-class: urn:content-classes:message Thread-Topic: draft-niccolini-speermint-voipthreats-01.txt X-MimeOLE: Produced By Microsoft Exchange V6.5 Thread-Index: AcdcTSm8hFDLaep+T1+MpFWLaPUh0QAn5lRgAiETYjA= References: <113091BD57179D4491C19DA7E10CD696BD9FAF@mx1.office> From: "Saverio Niccolini" To: X-Spam-Score: 0.1 (/) X-Scan-Signature: 3fbd9b434023f8abfcb1532abaec7a21 Cc: Eric , eric.chen@lab.ntt.co.jp Subject: [Speermint] draft-niccolini-speermint-voipthreats-01.txt X-BeenThere: speermint@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mailing list for the speermint working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: speermint-bounces@ietf.org Dear all, we (me and Eric) will be in Prague next week and even if our=20 draft is not in the agenda we would appreciate some of you to take some time to read it and to discuss with one of us feedbacks/ comments/suggestions for improvements. If you plan to be in Prague and want to have some discussion on this we would appreciate your time, just drop us an email Saverio Niccolini: saverio.niccolini@netlab.nec.de Eric Chen: dgtlsoul@yahoo.co.jp or eric.chen@lab.ntt.co.jp Cheers, Saverio =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Dr. Saverio Niccolini Senior Research Staff Member Network Laboratories, NEC Europe Ltd. Kurfuerstenanlage 36, D-69115 Heidelberg Tel. +49 (0)6221 4342-118 Fax: +49 (0)6221 4342-155 e-mail: saverio.niccolini@netlab.nec.de =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D NEC Europe Limited Registered Office: NEC House, 1 Victoria Road, London W3 6BL Registered in England 2832014 =20 > -----Original Message----- > From: Saverio Niccolini [mailto:Saverio.Niccolini@netlab.nec.de]=20 > Sent: Friday, March 02, 2007 6:09 PM > To: speermint@ietf.org > Subject: [Speermint] FW:=20 > I-DACTION:draft-niccolini-speermint-voipthreats-01.txt=20 >=20 > Dear all, >=20 > I submitted a second version of the VoIP Security threats draft > after doing a lot of work helped by Eric Chen (NTT). >=20 > I would appreciate if you could find some time to discuss on the > mailing list if you like the new approach we took and what are the > problems/things you like. >=20 > The major changes are: > -- adaptation of the threats to the SPEERMINT architecture=20 > (LF, SF, MF) > -- introduction of SPEERMINT specific threats >=20 > We think this draft is now ready to have more discussion within > the list and we would appreciate you to find some time for this. >=20 > Cheers, > Saverio >=20 > = =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > Dr. Saverio Niccolini > Senior Research Staff Member > Network Laboratories, NEC Europe Ltd. > Kurfuerstenanlage 36, D-69115 Heidelberg > Tel. +49 (0)6221 4342-118 > Fax: +49 (0)6221 4342-155 > e-mail: saverio.niccolini@netlab.nec.de > = =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > NEC Europe Limited > Registered Office: NEC House, 1 Victoria Road, London W3 6BL > Registered in England 2832014 > =20 >=20 > > -----Original Message----- > > From: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org]=20 > > Sent: Thursday, March 01, 2007 9:50 PM > > To: i-d-announce@ietf.org > > Subject: I-D ACTION:draft-niccolini-speermint-voipthreats-01.txt=20 > >=20 > > A New Internet-Draft is available from the on-line Internet-Drafts=20 > > directories. > >=20 > >=20 > > Title : VoIP Security Threats relevant to SPEERMINT > > Author(s) : E. Chen, S. Niccolini > > Filename : draft-niccolini-speermint-voipthreats-01.txt > > Pages : 19 > > Date : 2007-3-1 > > =09 > > This memo presents the different security threats related to > > SPEERMINT classifying them into threats to the Location=20 > > Function, to > > the Signaling Function and to the Media Function. The different > > instances of the threats are briefly introduced inside the > > classification. Finally the existing security solutions=20 > in SIP and > > RTP/RTCP are presented to describe the countermeasures currently > > available for such threats. The objective of this document is to > > identify and enumerate the SPEERMINT-specific threat=20 > > vectors in order > > to specify security-related requirements. Once the=20 > > requirements are > > identified, methods and solutions how to achieve such=20 > requirements > > can be selected. > >=20 > > A URL for this Internet-Draft is: > >=20 > http://www.ietf.org/internet-drafts/draft-niccolini-speermint- > voipthreats-01.txt > >=20 > > To remove yourself from the I-D Announcement list, send a=20 > message to=20 > > i-d-announce-request@ietf.org with the word unsubscribe in=20 > > the body of=20 > > the message.=20 > > You can also visit=20 > > https://www1.ietf.org/mailman/listinfo/I-D-announce=20 > > to change your subscription settings. > >=20 > > Internet-Drafts are also available by anonymous FTP. Login with the=20 > > username "anonymous" and a password of your e-mail address. After=20 > > logging in, type "cd internet-drafts" and then=20 > > "get draft-niccolini-speermint-voipthreats-01.txt". > >=20 > > A list of Internet-Drafts directories can be found in > > http://www.ietf.org/shadow.html=20 > > or ftp://ftp.ietf.org/ietf/1shadow-sites.txt > >=20 > > Internet-Drafts can also be obtained by e-mail. > >=20 > > Send a message to: > > mailserv@ietf.org. > > In the body type: > > "FILE=20 > > /internet-drafts/draft-niccolini-speermint-voipthreats-01.txt". > > =09 > > NOTE: The mail server at ietf.org can return the document in > > MIME-encoded form by using the "mpack" utility. To use this > > feature, insert the command "ENCODING mime" before the "FILE" > > command. To decode the response(s), you will need "munpack" or > > a MIME-compliant mail reader. Different MIME-compliant=20 > > mail readers > > exhibit different behavior, especially when dealing with > > "multipart" MIME messages (i.e. documents which have been split > > up into multiple messages), so check your local documentation on > > how to manipulate these messages. > >=20 > > Below is the data which will enable a MIME compliant mail reader > > implementation to automatically retrieve the ASCII version of the > > Internet-Draft. > >=20 >=20 _______________________________________________ Speermint mailing list Speermint@ietf.org https://www1.ietf.org/mailman/listinfo/speermint From speermint-bounces@ietf.org Sat Mar 17 11:28:27 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HSanT-0002O7-G6; Sat, 17 Mar 2007 11:26:19 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HSanS-0002Ns-6c; Sat, 17 Mar 2007 11:26:18 -0400 Received: from pahula.nona.net ([193.80.224.123] helo=kahua.nona.net) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HSanQ-00067y-TB; Sat, 17 Mar 2007 11:26:18 -0400 Received: from [192.168.190.45] (148.116.broadband4.iol.cz [::ffff:85.71.116.148]) (AUTH: PLAIN axelm, TLS: TLSv1/SSLv3,256bits,AES256-SHA) by pahula with esmtp; Sat, 17 Mar 2007 16:25:50 +0100 id 00008256.45FC087E.00000AA8 Message-ID: <45FC0871.9010409@enum.at> Date: Sat, 17 Mar 2007 16:25:37 +0100 From: Alexander Mayrhofer Organization: enum.at GmbH User-Agent: Thunderbird 1.5.0.10 (Windows/20070221) MIME-Version: 1.0 To: enum@ietf.org, speermint@ietf.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: 68c8cc8a64a9d0402e43b8eee9fc4199 Cc: Subject: [Speermint] Please send in your presentations for Prague X-BeenThere: speermint@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mailing list for the speermint working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: speermint-bounces@ietf.org If you're going to present during the ENUM or SPEERMINT sessions in Prague, please send me your presentations asap, so that i can upload them to the Meetings Material site. (Yes, can replace them with an updated version later, so no need to "keep it back") thanks, Alex _______________________________________________ Speermint mailing list Speermint@ietf.org https://www1.ietf.org/mailman/listinfo/speermint From speermint-bounces@ietf.org Sat Mar 17 17:58:06 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HSgsw-0000rz-N0; Sat, 17 Mar 2007 17:56:22 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HSgsv-0000n5-DI for speermint@ietf.org; Sat, 17 Mar 2007 17:56:21 -0400 Received: from paoakoavas10.cable.comcast.com ([208.17.35.59]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HSgss-0004eD-61 for speermint@ietf.org; Sat, 17 Mar 2007 17:56:21 -0400 Received: from ([24.40.15.118]) by paoakoavas10.cable.comcast.com with ESMTP id KP-TDCH7.30858658; Sat, 17 Mar 2007 17:55:58 -0400 Received: from PACDCEXCMB04.cable.comcast.com ([24.40.15.86]) by PACDCEXCSMTP04.cable.comcast.com with Microsoft SMTPSVC(6.0.3790.1830); Sat, 17 Mar 2007 17:55:58 -0400 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Sat, 17 Mar 2007 17:55:57 -0400 Message-ID: <45AEC6EF95942140888406588E1A6602FF7EC7@PACDCEXCMB04.cable.comcast.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Won't Be in Prague - Dave Will Handle WG Session Thread-Index: Acdo3wrZz1yJMgotTTi9OkT27UzMTg== From: "Livingood, Jason" To: X-OriginalArrivalTime: 17 Mar 2007 21:55:58.0858 (UTC) FILETIME=[0BD0D6A0:01C768DF] X-Spam-Score: 0.0 (/) X-Scan-Signature: 7bac9cb154eb5790ae3b2913587a40de Subject: [Speermint] Won't Be in Prague - Dave Will Handle WG Session X-BeenThere: speermint@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mailing list for the speermint working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: speermint-bounces@ietf.org For those of you heading to Prague for this coming Thursday's SPEERMINT session - I regret that I will not be there. I have cancelled due to illness and am staying home and continuing to recover. I am very bummed not to be in Prague!! :-( You will be in capable hands with Dave running the show solo in our WG session. See everyone next time! =20 Regards Jason=20 _______________________________________________ Speermint mailing list Speermint@ietf.org https://www1.ietf.org/mailman/listinfo/speermint From speermint-bounces@ietf.org Sun Mar 18 04:50:24 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HSr5C-0004jk-Fy; Sun, 18 Mar 2007 04:49:42 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HSr5B-0004ja-QC for speermint@ietf.org; Sun, 18 Mar 2007 04:49:41 -0400 Received: from m106.maoz.com ([205.167.76.9]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HSr5A-0005Iz-FA for speermint@ietf.org; Sun, 18 Mar 2007 04:49:41 -0400 Received: from m106.maoz.com (localhost.localdomain [127.0.0.1]) by m106.maoz.com (8.13.8/8.13.8) with ESMTP id l2I8nKfc015918; Sun, 18 Mar 2007 00:49:20 -0800 Received: (from dmm@localhost) by m106.maoz.com (8.13.8/8.12.11/Submit) id l2I8nKwa015917; Sun, 18 Mar 2007 00:49:20 -0800 X-Authentication-Warning: m106.maoz.com: dmm set sender to dmm@1-4-5.net using -f Date: Sun, 18 Mar 2007 00:49:20 -0800 From: David Meyer To: speermint@ietf.org Subject: Re: [Speermint] Won't Be in Prague - Dave Will Handle WG Session Message-ID: <20070318084920.GA15893@1-4-5.net> References: <45AEC6EF95942140888406588E1A6602FF7EC7@PACDCEXCMB04.cable.comcast.com> Mime-Version: 1.0 In-Reply-To: <45AEC6EF95942140888406588E1A6602FF7EC7@PACDCEXCMB04.cable.comcast.com> User-Agent: Mutt/1.4.1i X-public-key: http://www.1-4-5.net/~dmm/public-key.asc X-gpg-fingerprint: 2409 8B50 B389 A307 BA5C 2A16 3918 03D6 A099 D8A7 X-philosophy: "I laugh and I cry, and I'm haunted by...Things I never meant nor wished to say" -- Bob Dylan, "When The Deal Goes Down" X-Spam-Score: 0.0 (/) X-Scan-Signature: 52e1467c2184c31006318542db5614d5 Cc: Jason_Livingood@cable.comcast.com, jon.peterson@neustar.biz X-BeenThere: speermint@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mailing list for the speermint working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1484792253==" Errors-To: speermint-bounces@ietf.org --===============1484792253== Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="lrZ03NoBR/3+SXJZ" Content-Disposition: inline --lrZ03NoBR/3+SXJZ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Mar 17, 2007 at 05:55:57PM -0400, Livingood, Jason wrote: > For those of you heading to Prague for this coming Thursday's SPEERMINT > session - I regret that I will not be there. I have cancelled due to > illness and am staying home and continuing to recover. I am very bummed > not to be in Prague!! :-( >=20 > You will be in capable hands with Dave running the show solo in our WG > session. See everyone next time! =20 So folks, now we have a problem. Speermint is scheduled for Thursday AM but due to my daughter getting married on Saturday, I have to leave on Thursday AM. I'm asking the secretariat if we can reschedule, but if that isn't possible, we'll have to cancel. --dmm --lrZ03NoBR/3+SXJZ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFF/P0QORgD1qCZ2KcRAsNxAJ9buyytAK7gYRuNzKdOnarQW7Te4gCfTX9v hQQwxEEv0Png8tv/ZM2pQ1w= =RlMc -----END PGP SIGNATURE----- --lrZ03NoBR/3+SXJZ-- --===============1484792253== 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://www1.ietf.org/mailman/listinfo/speermint --===============1484792253==-- From speermint-bounces@ietf.org Sun Mar 18 05:05:42 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HSrK2-0002Nn-T2; Sun, 18 Mar 2007 05:05:02 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HSrK0-0002Mc-Vr; Sun, 18 Mar 2007 05:05:00 -0400 Received: from sj-iport-5.cisco.com ([171.68.10.87]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HSrJz-0006XZ-OE; Sun, 18 Mar 2007 05:05:00 -0400 Received: from sj-dkim-6.cisco.com ([171.68.10.81]) by sj-iport-5.cisco.com with ESMTP; 18 Mar 2007 02:05:00 -0700 Received: from sj-core-3.cisco.com (sj-core-3.cisco.com [171.68.223.137]) by sj-dkim-6.cisco.com (8.12.11/8.12.11) with ESMTP id l2I94wKr023285; Sun, 18 Mar 2007 02:04:58 -0700 Received: from [130.129.20.115] (sjc-vpn6-128.cisco.com [10.21.120.128]) by sj-core-3.cisco.com (8.12.10/8.12.6) with ESMTP id l2I94vA8004127; Sun, 18 Mar 2007 09:04:58 GMT Mime-Version: 1.0 (Apple Message framework v752.3) Content-Transfer-Encoding: 7bit Message-Id: <263711A7-1B77-47E4-840B-40A429F7D028@cisco.com> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed To: speermint@ietf.org, geopriv@ietf.org From: Cullen Jennings Date: Sun, 18 Mar 2007 10:04:50 +0100 X-Mailer: Apple Mail (2.752.3) DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=411; t=1174208699; x=1175072699; c=relaxed/simple; s=sjdkim6002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=fluffy@cisco.com; z=From:=20Cullen=20Jennings=20 |Subject:=20IMPORTANT=20SCHEDULE=20CHANGE |Sender:=20; bh=vSpFuIGLllbqotLuQ6sJ3meBwZUi3JsrPgXTYT4c358=; b=J1RFIeExu+4lO3H2VbTGDWeebkpyKLfbibq1DiV2gBL08X6AVy9s3SiFhO/XOrtNquUvRER1 QWeVQyKlfQp72/ZqzuMzjiyGmBZBSr8VcqNz4Yv7gxNiieJbfALADblA; Authentication-Results: sj-dkim-6; header.From=fluffy@cisco.com; dkim=pass ( sig from cisco.com/sjdkim6002 verified; ); X-Spam-Score: 0.4 (/) X-Scan-Signature: 1ac7cc0a4cd376402b85bc1961a86ac2 Cc: Subject: [Speermint] IMPORTANT SCHEDULE CHANGE X-BeenThere: speermint@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mailing list for the speermint working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: speermint-bounces@ietf.org We are probably going to swap the time of the geopriv and spearmint meeting. This will result in spearmint being 9:00 Tuesday and geopriv being 9:00 Thursday. This is not confirmed yet but I wanted to give folks a early heads up that this was likely to happen. My apologies for the late notice on this but we have some issues around when we can get the chairs to be here. Thanks, Cullen _______________________________________________ Speermint mailing list Speermint@ietf.org https://www1.ietf.org/mailman/listinfo/speermint From speermint-bounces@ietf.org Sun Mar 18 11:26:13 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HSxGK-0004hc-9O; Sun, 18 Mar 2007 11:25:36 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HSxGI-0004eL-Cj; Sun, 18 Mar 2007 11:25:34 -0400 Received: from ams-iport-1.cisco.com ([144.254.224.140]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HSxGB-0000lS-OZ; Sun, 18 Mar 2007 11:25:33 -0400 Received: from ams-dkim-2.cisco.com ([144.254.224.139]) by ams-iport-1.cisco.com with ESMTP; 18 Mar 2007 16:25:28 +0100 Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150]) by ams-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id l2IFPRoV008468; Sun, 18 Mar 2007 16:25:27 +0100 Received: from [10.0.0.223] (ams3-vpn-dhcp4506.cisco.com [10.61.81.153]) by ams-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l2IFPQlZ008995; Sun, 18 Mar 2007 15:25:26 GMT Mime-Version: 1.0 (Apple Message framework v752.3) Content-Transfer-Encoding: 7bit Message-Id: <2A45522D-9D71-472B-8B82-8717FF14E65A@cisco.com> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed To: GEOPRIV , speermint@ietf.org From: Cullen Jennings Date: Sun, 18 Mar 2007 16:25:19 +0100 X-Mailer: Apple Mail (2.752.3) DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=362; t=1174231527; x=1175095527; c=relaxed/simple; s=amsdkim2001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=fluffy@cisco.com; z=From:=20Cullen=20Jennings=20 |Subject:=20Times=20of=20GEOPRIV=20and=20SPEERMINT=20meeting=20changed |Sender:=20; bh=seKqnifSIvIS2QKxBi9IIAjspjrzizU7m+CMV3rwSpQ=; b=Zs2h+t1VeVafNcrEW3w1ut4wUcoXrW8K2txQr65/SUwjlOPBf15kEHsAR4iQEoqV3ipiFdtl fMnJpDZ9WJjxmFYRFiYQs0P5qDEqm2RCDrnGBWbuK0Bk87F2FYrmw99/; Authentication-Results: ams-dkim-2; header.From=fluffy@cisco.com; dkim=pass ( sig from cisco.com/amsdkim2001 verified; ); X-Spam-Score: 0.0 (/) X-Scan-Signature: 68c8cc8a64a9d0402e43b8eee9fc4199 Cc: Subject: [Speermint] Times of GEOPRIV and SPEERMINT meeting changed X-BeenThere: speermint@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mailing list for the speermint working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: speermint-bounces@ietf.org The times of the GEOPRIV and SPEERMINT meetings have been changed. Geopriv is now thursday at 9:00 while SPEERMINT is now tuesday at 9:00. You can find them on agenda at https://datatracker.ietf.org/public/meeting_agenda_html.cgi? meeting_num=68 I know this causes some problems but it was the best plan could come up with. Thanks, Cullen _______________________________________________ Speermint mailing list Speermint@ietf.org https://www1.ietf.org/mailman/listinfo/speermint From speermint-bounces@ietf.org Sun Mar 18 14:06:04 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HSzkV-0004yZ-2N; Sun, 18 Mar 2007 14:04:55 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HSzkU-0004yU-1S for speermint@ietf.org; Sun, 18 Mar 2007 14:04:54 -0400 Received: from mtagate2.de.ibm.com ([195.212.29.151]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HSzkS-0004kM-6z for speermint@ietf.org; Sun, 18 Mar 2007 14:04:54 -0400 Received: from d12nrmr1607.megacenter.de.ibm.com (d12nrmr1607.megacenter.de.ibm.com [9.149.167.49]) by mtagate2.de.ibm.com (8.13.8/8.13.8) with ESMTP id l2II4ncQ118888 for ; Sun, 18 Mar 2007 18:04:49 GMT Received: from d12av04.megacenter.de.ibm.com (d12av04.megacenter.de.ibm.com [9.149.165.229]) by d12nrmr1607.megacenter.de.ibm.com (8.13.8/8.13.8/NCO v8.3) with ESMTP id l2II4nFP1872066 for ; Sun, 18 Mar 2007 19:04:49 +0100 Received: from d12av04.megacenter.de.ibm.com (loopback [127.0.0.1]) by d12av04.megacenter.de.ibm.com (8.12.11.20060308/8.13.3) with ESMTP id l2II4nrx010949 for ; Sun, 18 Mar 2007 19:04:49 +0100 Received: from d12ml102.megacenter.de.ibm.com (d12ml102.megacenter.de.ibm.com [9.149.166.138]) by d12av04.megacenter.de.ibm.com (8.12.11.20060308/8.12.11) with ESMTP id l2II4noT010943 for ; Sun, 18 Mar 2007 19:04:49 +0100 In-Reply-To: <2A45522D-9D71-472B-8B82-8717FF14E65A@cisco.com> To: Cullen Jennings Subject: Re: [Speermint] Times of GEOPRIV and SPEERMINT meeting changed MIME-Version: 1.0 X-Mailer: Lotus Notes Release 7.0 HF144 February 01, 2006 From: Avshalom Houri Message-ID: Date: Sun, 18 Mar 2007 20:04:46 +0200 X-MIMETrack: Serialize by Router on D12ML102/12/M/IBM(Release 7.0.2HF71 | November 3, 2006) at 18/03/2007 20:04:48, Serialize complete at 18/03/2007 20:04:48 X-Spam-Score: 0.1 (/) X-Scan-Signature: c83ccb5cc10e751496398f1233ca9c3a Cc: speermint@ietf.org X-BeenThere: speermint@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mailing list for the speermint working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1489193148==" Errors-To: speermint-bounces@ietf.org This is a multipart message in MIME format. --===============1489193148== Content-Type: multipart/alternative; boundary="=_alternative 0063783BC22572A2_=" This is a multipart message in MIME format. --=_alternative 0063783BC22572A2_= Content-Type: text/plain; charset="US-ASCII" I understand and accept the need for the switch but could not we switch SPEERMINT with P2P SIP on Wed morning? That way it was only one day shift? Thanks --Avshalom Cullen Jennings 18/03/2007 17:25 To GEOPRIV , speermint@ietf.org cc Subject [Speermint] Times of GEOPRIV and SPEERMINT meeting changed The times of the GEOPRIV and SPEERMINT meetings have been changed. Geopriv is now thursday at 9:00 while SPEERMINT is now tuesday at 9:00. You can find them on agenda at https://datatracker.ietf.org/public/meeting_agenda_html.cgi? meeting_num=68 I know this causes some problems but it was the best plan could come up with. Thanks, Cullen _______________________________________________ Speermint mailing list Speermint@ietf.org https://www1.ietf.org/mailman/listinfo/speermint --=_alternative 0063783BC22572A2_= Content-Type: text/html; charset="US-ASCII"
I understand and accept the need for the switch but could not we switch SPEERMINT with P2P SIP on Wed morning?
That way it was only one day shift?

Thanks
--Avshalom


Cullen Jennings <fluffy@cisco.com>

18/03/2007 17:25

To
GEOPRIV <geopriv@ietf.org>, speermint@ietf.org
cc
Subject
[Speermint] Times of GEOPRIV and SPEERMINT meeting changed






The times of the GEOPRIV and SPEERMINT meetings have been changed.  
Geopriv is now thursday at 9:00 while SPEERMINT is now tuesday at  
9:00. You can find them on agenda at

https://datatracker.ietf.org/public/meeting_agenda_html.cgi?
meeting_num=68

I know this causes some problems but it was the best plan could come  
up with.

Thanks, Cullen

_______________________________________________
Speermint mailing list
Speermint@ietf.org
https://www1.ietf.org/mailman/listinfo/speermint
--=_alternative 0063783BC22572A2_=-- --===============1489193148== 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://www1.ietf.org/mailman/listinfo/speermint --===============1489193148==-- From speermint-bounces@ietf.org Mon Mar 19 18:02:07 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HTPuB-0001Ut-TS; Mon, 19 Mar 2007 18:00:39 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HTPuA-0001Nb-QK for speermint@ietf.org; Mon, 19 Mar 2007 18:00:38 -0400 Received: from pahula.nona.net ([193.80.224.123] helo=kahua.nona.net) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HTPtj-0000EM-3Z for speermint@ietf.org; Mon, 19 Mar 2007 18:00:38 -0400 Received: from [213.175.39.20] (softdnserr [::ffff:213.175.39.20]) (AUTH: PLAIN axelm, TLS: TLSv1/SSLv3,256bits,AES256-SHA) by pahula with esmtp; Mon, 19 Mar 2007 23:00:00 +0100 id 0000825A.45FF07E0.000003DB Message-ID: <45FF07D2.9030304@enum.at> Date: Mon, 19 Mar 2007 22:59:46 +0100 From: Alexander Mayrhofer Organization: enum.at GmbH User-Agent: Thunderbird 1.5.0.10 (Windows/20070221) MIME-Version: 1.0 To: speermint Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: 30ac594df0e66ffa5a93eb4c48bcb014 Subject: [Speermint] presentations, please.... X-BeenThere: speermint@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mailing list for the speermint working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: speermint-bounces@ietf.org if you're going to present in tomorrow's SPEERMINT session - please mail me your slides, unless they are already uploaded at https://datatracker.ietf.org/public/meeting_materials.cgi?meeting_num=68 (If you don't find them there, please mail them, thanks) Alex _______________________________________________ Speermint mailing list Speermint@ietf.org https://www1.ietf.org/mailman/listinfo/speermint From speermint-bounces@ietf.org Tue Mar 20 11:30:08 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HTgHH-0001M8-7a; Tue, 20 Mar 2007 11:29:35 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HTgHF-0001Kx-KU for speermint@ietf.org; Tue, 20 Mar 2007 11:29:33 -0400 Received: from mtagate3.de.ibm.com ([195.212.29.152]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HTgHD-0005UG-22 for speermint@ietf.org; Tue, 20 Mar 2007 11:29:33 -0400 Received: from d12nrmr1607.megacenter.de.ibm.com (d12nrmr1607.megacenter.de.ibm.com [9.149.167.49]) by mtagate3.de.ibm.com (8.13.8/8.13.8) with ESMTP id l2KFTUwS070422 for ; Tue, 20 Mar 2007 15:29:30 GMT Received: from d12av02.megacenter.de.ibm.com (d12av02.megacenter.de.ibm.com [9.149.165.228]) by d12nrmr1607.megacenter.de.ibm.com (8.13.8/8.13.8/NCO v8.3) with ESMTP id l2KFTUMA2003098 for ; Tue, 20 Mar 2007 16:29:30 +0100 Received: from d12av02.megacenter.de.ibm.com (loopback [127.0.0.1]) by d12av02.megacenter.de.ibm.com (8.12.11.20060308/8.13.3) with ESMTP id l2KFTTAc006367 for ; Tue, 20 Mar 2007 16:29:29 +0100 Received: from d12ml102.megacenter.de.ibm.com (d12ml102.megacenter.de.ibm.com [9.149.166.138]) by d12av02.megacenter.de.ibm.com (8.12.11.20060308/8.12.11) with ESMTP id l2KFTTfs006364 for ; Tue, 20 Mar 2007 16:29:29 +0100 To: speermint@ietf.org MIME-Version: 1.0 X-Mailer: Lotus Notes Release 7.0 HF144 February 01, 2006 From: Avshalom Houri Message-ID: Date: Tue, 20 Mar 2007 17:29:28 +0200 X-MIMETrack: Serialize by Router on D12ML102/12/M/IBM(Release 7.0.2HF71 | November 3, 2006) at 20/03/2007 17:29:29, Serialize complete at 20/03/2007 17:29:29 X-Spam-Score: 0.1 (/) X-Scan-Signature: 0fa76816851382eb71b0a882ccdc29ac Subject: [Speermint] Clarification on RTC - Real Time Collaboration term X-BeenThere: speermint@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mailing list for the speermint working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0780136711==" Errors-To: speermint-bounces@ietf.org This is a multipart message in MIME format. --===============0780136711== Content-Type: multipart/alternative; boundary="=_alternative 00553A2CC22572A4_=" This is a multipart message in MIME format. --=_alternative 00553A2CC22572A4_= Content-Type: text/plain; charset="US-ASCII" The slides that were presented by Sriram this morning in SPEERMINT were prepared by me. Due to the last minute change of the SPEERMINT time and due to personal issue, I could not present the slides and asked Sriram who is a co-author of the draft to do so and he kindly agreed. The term RTC is mentioned in the draft and was used also in a similar set of slides that I presented in IETF 67th see: http://www3.ietf.org/proceedings/06nov/slides/speermint-6/sld1.htm The intention was to find a term that will find a terminology term not an architectural term that will be a collective name for services like presence, IM, app sharing etc. I understand now that the RTC term is not a good one and another term has to be found. Anyway, no marketing aspect was intended here. Sorry if there was any misunderstanding. Thanks --Avshalom --=_alternative 00553A2CC22572A4_= Content-Type: text/html; charset="US-ASCII"
The slides that were presented by Sriram this morning in
SPEERMINT were prepared by me.

Due to the last minute change of the SPEERMINT time and due
to personal issue,

I could not present the slides and asked Sriram who is a co-author
of the draft to do so and he kindly agreed.

The term RTC is mentioned in the draft and was used
also in a similar set of slides that  I presented in IETF 67th
see: http://www3.ietf.org/proceedings/06nov/slides/speermint-6/sld1.htm

The intention was to find a term that will find
a terminology term not an architectural term that will be
a collective name for services like presence, IM, app sharing etc.
I understand now that the RTC term is not a good one and
another term has to be found.

Anyway, no marketing aspect was intended here.

Sorry if there was any misunderstanding.

Thanks
--Avshalom


--=_alternative 00553A2CC22572A4_=-- --===============0780136711== 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://www1.ietf.org/mailman/listinfo/speermint --===============0780136711==-- From speermint-bounces@ietf.org Wed Mar 28 19:36:26 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HWhfq-0006So-ES; Wed, 28 Mar 2007 19:35:26 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HWhfp-0006Sj-JU for speermint@ietf.org; Wed, 28 Mar 2007 19:35:25 -0400 Received: from unknown-230-det.globalcrossing.com ([64.208.159.230] helo=mailsrv.ams.gblxint.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HWhfo-0002GD-Cf for speermint@ietf.org; Wed, 28 Mar 2007 19:35:25 -0400 Received: from w3uspdy20.ams.gblxint.com (w3uspdy20.ams.gblxint.com [10.60.51.55]) by mailsrv.ams.gblxint.com (Postfix) with ESMTP id 0907E97E9 for ; Wed, 28 Mar 2007 19:34:48 -0400 (EDT) Received: from EVS2.ams.gblxint.com ([10.60.51.59]) by w3uspdy20.ams.gblxint.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 28 Mar 2007 19:34:47 -0400 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Wed, 28 Mar 2007 18:34:46 -0500 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Differing Administration Categories Thread-Index: AcdxkauYYhiJqIP6TMqH/ldcmsGYpg== From: "Uzelac, Adam" To: X-OriginalArrivalTime: 28 Mar 2007 23:34:47.0782 (UTC) FILETIME=[AC461860:01C77191] X-Spam-Score: 0.1 (/) X-Scan-Signature: 79899194edc4f33a41f49410777972f8 Subject: [Speermint] Differing Administration Categories X-BeenThere: speermint@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mailing list for the speermint working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: speermint-bounces@ietf.org In Prague - their was a discussion around the distinctions between federations and other concepts. As the Consolidated VoIP use case draft sits today - indeed there is "fuzziness" around this. It's not clear and I would like make it so. =20 Removed from the use-case categorization definitions will be non-technical terms like "trust". With an entirely new section called 'Administration' or 'Peering Contexts' (anyone have a preference) where things like nuances in the use cases, like trust, non-E164 numbering plans, etc will be captured. Outside of Federations, should Enterprises, CLECs, MSOs, etc be categorized as 'Administration' or 'Peering Contexts'? Thoughts? Once we get a feel for this - I believe this also needs to be in the terminology draft. Adam Uzelac Director Converged Arch. Global Crossing 585-255-8916 _______________________________________________ Speermint mailing list Speermint@ietf.org https://www1.ietf.org/mailman/listinfo/speermint From speermint-bounces@ietf.org Thu Mar 29 16:18:03 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HX13W-0005qU-Me; Thu, 29 Mar 2007 16:17:10 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HX13V-0005o3-94 for speermint@ietf.org; Thu, 29 Mar 2007 16:17:09 -0400 Received: from smtp.denic.de ([81.91.161.3]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HX13U-0001JO-0u for speermint@ietf.org; Thu, 29 Mar 2007 16:17:09 -0400 Received: from notes.rz.denic.de ([192.168.0.77]) by smtp.denic.de with esmtp id 1HX13E-0002zw-Jb; Thu, 29 Mar 2007 22:16:52 +0200 From: Heike Schmidt-Hunkel/Denic To: speermint@ietf.org Message-ID: Date: Thu, 29 Mar 2007 22:01:13 +0200 X-MIMETrack: Serialize by Router on notes/Denic at 29.03.2007 22:16:51 MIME-Version: 1.0 Content-type: text/plain; charset=ISO-8859-1 Content-transfer-encoding: quoted-printable X-Spam-Score: 0.0 (/) X-Scan-Signature: 7aefe408d50e9c7c47615841cb314bed Subject: [Speermint] =?iso-8859-1?q?Heike_Schmidt-Hunkel_ist_au=DFer_Haus?= =?iso-8859-1?q?=2E?= X-BeenThere: speermint@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mailing list for the speermint working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: speermint-bounces@ietf.org Ich werde ab 23.03.2007 nicht im B=FCro sein. Ich kehre zur=FCck am 1= 0.04.2007. Ich werde Ihre Nachricht nach meiner R=FCckkehr beantworten.= _______________________________________________ Speermint mailing list Speermint@ietf.org https://www1.ietf.org/mailman/listinfo/speermint