From junglecat@orchidseed.org Sat Sep 5 01:18:17 2009 Return-Path: X-Original-To: p2psip@core3.amsl.com Delivered-To: p2psip@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A1FBD3A6850 for ; Sat, 5 Sep 2009 01:18:17 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.986 X-Spam-Level: X-Spam-Status: No, score=-1.986 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, SARE_SPEC_LEO_LINE03f=0.612] 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 GAj1r+FmZAig for ; Sat, 5 Sep 2009 01:18:17 -0700 (PDT) Received: from mail-yx0-f190.google.com (mail-yx0-f190.google.com [209.85.210.190]) by core3.amsl.com (Postfix) with ESMTP id DC44A3A6784 for ; Sat, 5 Sep 2009 01:18:16 -0700 (PDT) Received: by yxe28 with SMTP id 28so1628010yxe.19 for ; Sat, 05 Sep 2009 01:18:36 -0700 (PDT) Received: by 10.91.192.14 with SMTP id u14mr9042441agp.2.1252138716546; Sat, 05 Sep 2009 01:18:36 -0700 (PDT) Received: from ?10.0.1.8? (ip68-5-30-57.oc.oc.cox.net [68.5.30.57]) by mx.google.com with ESMTPS id 7sm1376954aga.27.2009.09.05.01.18.34 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sat, 05 Sep 2009 01:18:35 -0700 (PDT) From: jc Content-Type: multipart/alternative; boundary=Apple-Mail-1--1046394413 Date: Sat, 5 Sep 2009 01:18:32 -0700 Message-Id: To: p2psip WG Mime-Version: 1.0 (Apple Message framework v1075.2) X-Mailer: Apple Mail (2.1075.2) X-Mailman-Approved-At: Mon, 07 Sep 2009 09:39:23 -0700 Subject: [P2PSIP] 10.3. Credentials draft-ietf-p2psip-base.txt revision 3698 X-BeenThere: p2psip@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Peer-to-Peer SIP working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Sep 2009 08:18:17 -0000 --Apple-Mail-1--1046394413 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii; format=flowed I assume this is to say "the server generates and returns a"? 6312 the requested user name is acceptable, the server and returns a Julian --Apple-Mail-1--1046394413 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii I assume = this is to say "the server generates and returns a"? =

6312	the requested user name is acceptable, the server and returns = a

Julian

<= /html>= --Apple-Mail-1--1046394413-- From neil.young@freenet.de Tue Sep 8 10:43:52 2009 Return-Path: X-Original-To: p2psip@core3.amsl.com Delivered-To: p2psip@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B07B828C2AD for ; Tue, 8 Sep 2009 10:43:52 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.002 X-Spam-Level: X-Spam-Status: No, score=0.002 tagged_above=-999 required=5 tests=[BAYES_50=0.001, HTML_MESSAGE=0.001] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ajmkNTzBR6t3 for ; Tue, 8 Sep 2009 10:43:51 -0700 (PDT) Received: from mout4.freenet.de (mout4.freenet.de [IPv6:2001:748:100:40::2:6]) by core3.amsl.com (Postfix) with ESMTP id DAD6528C1F8 for ; Tue, 8 Sep 2009 10:43:50 -0700 (PDT) Received: from [195.4.92.11] (helo=1.mx.freenet.de) by mout4.freenet.de with esmtpa (ID roland.klabunde@freenet.de) (port 25) (Exim 4.69 #92) id 1Ml4jr-0001uW-MM for p2psip@ietf.org; Tue, 08 Sep 2009 19:44:19 +0200 Received: from p54bd982b.dip0.t-ipconnect.de ([84.189.152.43]:55118 helo=[192.168.178.38]) by 1.mx.freenet.de with esmtpa (ID roland.klabunde@freenet.de) (port 25) (Exim 4.69 #94) id 1Ml4jr-0004BW-Gj for p2psip@ietf.org; Tue, 08 Sep 2009 19:44:19 +0200 Message-ID: <4AA697F5.1000803@freenet.de> Date: Tue, 08 Sep 2009 19:44:21 +0200 From: "neil.young" User-Agent: Thunderbird 2.0.0.23 (Windows/20090812) MIME-Version: 1.0 To: p2psip@ietf.org Content-Type: multipart/alternative; boundary="------------090509040602050708040004" Subject: [P2PSIP] What is the state of RELOAD? X-BeenThere: p2psip@ietf.org X-Mailman-Version: 2.1.9 Precedence: list Reply-To: neil.young@freenet.de List-Id: Peer-to-Peer SIP working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Sep 2009 17:45:11 -0000 This is a multi-part message in MIME format. --------------090509040602050708040004 Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit Hello group, could anybody give me a brief info about the status of RELOAD? Is there already any commercial/open source implementation out? Kind regards --------------090509040602050708040004 Content-Type: text/html; charset=ISO-8859-15 Content-Transfer-Encoding: 7bit Hello group,

could anybody give me a brief info about the status of RELOAD? Is there already any commercial/open source implementation out?

Kind regards

--------------090509040602050708040004-- From neil.young@freenet.de Wed Sep 9 05:42:51 2009 Return-Path: X-Original-To: p2psip@core3.amsl.com Delivered-To: p2psip@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 309BF28C428 for ; Wed, 9 Sep 2009 05:42:51 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.204 X-Spam-Level: X-Spam-Status: No, score=-1.204 tagged_above=-999 required=5 tests=[AWL=-0.095, BAYES_05=-1.11, HTML_MESSAGE=0.001] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gKLV4k+JAor1 for ; Wed, 9 Sep 2009 05:42:50 -0700 (PDT) Received: from mout1.freenet.de (mout1.freenet.de [IPv6:2001:748:100:40::2:3]) by core3.amsl.com (Postfix) with ESMTP id 3A27D28C433 for ; Wed, 9 Sep 2009 05:42:46 -0700 (PDT) Received: from [195.4.92.10] (helo=0.mx.freenet.de) by mout1.freenet.de with esmtpa (ID roland.klabunde@freenet.de) (port 25) (Exim 4.69 #92) id 1MlMW5-0006KI-0U for p2psip@ietf.org; Wed, 09 Sep 2009 14:43:17 +0200 Received: from p54bd9a8e.dip0.t-ipconnect.de ([84.189.154.142]:57330 helo=[192.168.178.38]) by 0.mx.freenet.de with esmtpa (ID roland.klabunde@freenet.de) (port 25) (Exim 4.69 #94) id 1MlMW4-0005bI-1C for p2psip@ietf.org; Wed, 09 Sep 2009 14:43:16 +0200 Message-ID: <4AA7A2E6.3030005@freenet.de> Date: Wed, 09 Sep 2009 14:43:18 +0200 From: "neil.young" User-Agent: Thunderbird 2.0.0.23 (Windows/20090812) MIME-Version: 1.0 To: p2psip@ietf.org References: <4AA697F5.1000803@freenet.de> <15A45571-A5BD-4C25-A049-F6269E1C0B66@orchidseed.org> In-Reply-To: <15A45571-A5BD-4C25-A049-F6269E1C0B66@orchidseed.org> Content-Type: multipart/alternative; boundary="------------040509060001090208040908" Subject: Re: [P2PSIP] What is the state of RELOAD? X-BeenThere: p2psip@ietf.org X-Mailman-Version: 2.1.9 Precedence: list Reply-To: neil.young@freenet.de List-Id: Peer-to-Peer SIP working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Sep 2009 12:42:51 -0000 This is a multi-part message in MIME format. --------------040509060001090208040908 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit OK. Really, that many responses... Pessimistic view: RELOAD is dead Optimistic view: Thousands of people are working in the dark, hiding their results from each other. What might be the truth? I don't want to bet on a dead horse, that's for sure... Regards >> Hello group, >> >> could anybody give me a brief info about the status of RELOAD? Is >> there already any commercial/open source implementation out? >> >> Kind regards >> >> _______________________________________________ >> P2PSIP mailing list >> P2PSIP@ietf.org >> https://www.ietf.org/mailman/listinfo/p2psip --------------040509060001090208040908 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit OK. Really, that many responses...

Pessimistic view: RELOAD is dead
Optimistic view: Thousands of people are working in the dark, hiding their results from each other.

What might be the truth? I don't want to bet on a dead horse, that's for sure...

Regards

Hello group,

could anybody give me a brief info about the status of RELOAD? Is there already any commercial/open source implementation out?

Kind regards

_______________________________________________
P2PSIP mailing list
P2PSIP@ietf.org
https://www.ietf.org/mailman/listinfo/p2psip

--------------040509060001090208040908-- From br@brianrosen.net Wed Sep 9 08:25:29 2009 Return-Path: X-Original-To: p2psip@core3.amsl.com Delivered-To: p2psip@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6A5923A6960 for ; Wed, 9 Sep 2009 08:25:29 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.434 X-Spam-Level: X-Spam-Status: No, score=-2.434 tagged_above=-999 required=5 tests=[AWL=0.165, 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 oOFO0VbbVxX5 for ; Wed, 9 Sep 2009 08:25:28 -0700 (PDT) Received: from ebru.winwebhosting.com (ebru.winwebhosting.com [74.55.202.130]) by core3.amsl.com (Postfix) with ESMTP id 16FF33A68F3 for ; Wed, 9 Sep 2009 08:25:28 -0700 (PDT) Received: from neustargw.va.neustar.com ([209.173.53.233] helo=[10.31.201.57]) by ebru.winwebhosting.com with esmtpa (Exim 4.69) (envelope-from ) id 1MlP3Q-0006Vc-Pe for p2psip@ietf.org; Wed, 09 Sep 2009 10:25:52 -0500 User-Agent: Microsoft-Entourage/12.20.0.090605 Date: Wed, 09 Sep 2009 11:25:57 -0400 From: Brian Rosen To: Message-ID: Thread-Topic: Nomcom 2009-10: Important Reminder: Call for Nominations, Local Office hours, Nominee Questionnaires available Thread-Index: AcoxYdPjeopQfO4tWkOviuicNgywNg== In-Reply-To: <20090909143800.E2CD928C13E@core3.amsl.com> Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - ebru.winwebhosting.com X-AntiAbuse: Original Domain - ietf.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - brianrosen.net X-Source: X-Source-Args: X-Source-Dir: Subject: [P2PSIP] FW: Nomcom 2009-10: Important Reminder: Call for Nominations, Local Office hours, Nominee Questionnaires available X-BeenThere: p2psip@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Peer-to-Peer SIP working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Sep 2009 15:25:29 -0000 Please consider the following, it's important Brian ------ Forwarded Message From: Mary Barnes Date: Wed, 9 Sep 2009 07:37:59 -0700 (PDT) To: IETF Announcement list Cc: Subject: Nomcom 2009-10: Important Reminder: Call for Nominations, Local Office hours, Nominee Questionnaires available Hi all, This is a 2nd reminder of the Call for Nominations that is underway. We *really* need more nominations in order to properly execute the task of selecting candidates for the open positions. At this time, the number of nominations for all the positions is about 1/2 of what is necessary for the Nomcom to do a conscientious job of evaluating the nominees and we are over 2/3 of the way through the nominations period. Nomcom cannot do their job without this important input from the community. So, please consider making nominations for the open positions - it takes just a few minutes of your time - the details are below. Right now, we just need the names/email addresses for the nominees - we'll be soliciting feedback later. Also, consider that over 1/2 the nominees are not able to accept the nominations for a variety of reasons - e.g., lack of funding, lack of sponsor support, etc. Thus, please consider nominating more than one individual for each of the positions. As well as the reminder for the call for nominations, this email also serves as a reminder for: 2) Local Office Hours 3) Questionnaires available for nominees Best Regards, Mary Barnes nomcom-chair@ietf.org mary.h.barnes@gmail.com mary.barnes@nortel.com ========================================================================= 1) Call for Nominations ------------------------ The nomination period ends in less than 2 weeks on Sept. 18th, 2009. We appreciate the folks that have taken the time to make nominations thus far. But, we do need more nominations. Please use the online tool to nominate - it's fast, easy and secure: https://wiki.tools.ietf.org/group/nomcom/09/nominate Details on the open positions, as well as other details and options for making nominations are available on the Nomcom homepage: https://wiki.tools.ietf.org/group/nomcom/09/ Please consider that the sooner you make the nominations, the more time your nominee(s) will have to complete the necessary questionnaire (item 3 below). As well, please consider nominating more than one person for a particular position. You will have the opportunity to provide additional feedback later and it's important to consider that not all nominees will be able to accept the nomination. 2) Local office hours ----------------------- In order facilitate additional feedback, the Nomcom has decided to make themselves available for office areas at various geographic locations for 3 weeks in September, starting on the 8th. Below please find the list of locations where Nomcom members will be available for these f2f meetings . Unless dates are identified below, the Nomcom member is generally available for part of the day during the weeks of Sept 8-11, Sept 14-18 and Sept 21-25. Also, languages other than English in which the Nomcom member is fluent are identfied. Please contact a Nomcom member in a specific geographic location to arrange a convenient meeting time and place. Most Nomcom members are flexible as to meeting locations - i.e., we can travel to your office, meet at our offices or somewhere in between. As a reminder folks can always contact any Nomcom member to provide feedback at anytime - i.e., you don't need to participate in these f2f sessions to provide feedback. Belgium: Dimitri Papadimitriou - dimitri.papadimitriou@alcatel-lucent.be (Sept 21-25) (Languages: French) Boston, Mass, USA: Stephen Kent - kent@bbn.com (Sept 16-18) Boulder, CO, USA: Wassim Haddad - wmhaddad@gmail.com (Sept 14-18) Dallas/Ft. Worth, TX, USA: Mary Barnes - mary.h.barnes@gmail.com Lucy Yong - lucyyong@huawei.com (Languages: Chinese) Helsinki, Finland: Simo Veikkolainen - simo.veikkolainen@nokia.com (Languages: Finnish) Ithaca, NY, USA: Scott Brim - scott.brim@gmail.com Montevideo, Uruguay: Roque Gagliano - roque@lacnic.net (Sept 14-18, 21-25) (Languages: Spanish, Portuguese) Montreal, Quebec, Canada Wassim Haddad - wmhaddad@gmail.com (Sept 8-11) -- Can also be available in Ottawa if folks are interested Paris, France: Dimitri Papadimitriou - dimitri.papadimitriou@alcatel-lucent.be (Sept 15-18) (Languages: French) San Diego, CA, USA: Randall Gellens - rg+ietf@qualcomm.com Dave Crocker - dcrocker@bbiw.net (Sept 16-18) Silicon Valley/SF Bay, CA, USA: Dave Crocker - dcrocker@bbiw.net (Sept 8-11, Sept 14-15, Sept 21-25) Dorothy Gellert - Dorothy.gellert@gmail.com 3) Questionnaires available for nominees: For folks that have been notified that they have been nominated for any of the positions, the questionnaires are now available on the Nomcom09 tools website: https://wiki.tools.ietf.org/group/nomcom/09/iab-questionnaire https://wiki.tools.ietf.org/group/nomcom/09/iaoc-questionnaire https://wiki.tools.ietf.org/group/nomcom/09/iesg-questionnaire If you have any questions, please let me know. I will be contacting everyone individually, as well as sending reminders. _______________________________________________ IETF-Announce mailing list IETF-Announce@ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce ------ End of Forwarded Message From julian@orchidseed.org Thu Sep 10 03:53:59 2009 Return-Path: X-Original-To: p2psip@core3.amsl.com Delivered-To: p2psip@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A53463A6830 for ; Thu, 10 Sep 2009 03:53:59 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.492 X-Spam-Level: X-Spam-Status: No, score=-2.492 tagged_above=-999 required=5 tests=[AWL=0.106, BAYES_00=-2.599, HTML_MESSAGE=0.001] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Y9JtF3kvU56J for ; Thu, 10 Sep 2009 03:53:58 -0700 (PDT) Received: from n12.c05.mtsvc.net (n12.c05.mtsvc.net [70.32.68.12]) by core3.amsl.com (Postfix) with ESMTP id D347A3A6A17 for ; Thu, 10 Sep 2009 03:53:58 -0700 (PDT) Received: from ip68-5-30-57.oc.oc.cox.net ([68.5.30.57]:39840 helo=[10.0.1.8]) by n12.c05.mtsvc.net with esmtpsa (TLS-1.0:RSA_AES_128_CBC_SHA:16) (Exim 4.63) (envelope-from ) id 1MlhIN-0007so-Mv for p2psip@ietf.org; Thu, 10 Sep 2009 03:54:33 -0700 From: jc Content-Type: multipart/alternative; boundary=Apple-Mail-6--605035541 Date: Thu, 10 Sep 2009 03:54:31 -0700 Message-Id: <1A87218C-3C7F-4D84-AD8B-A009615A083C@orchidseed.org> To: p2psip WG Mime-Version: 1.0 (Apple Message framework v1075.2) X-Mailer: Apple Mail (2.1075.2) X-Authenticated-User: 72798 julian@orchidseed.org Subject: [P2PSIP] Section 3.5.2 and 10.5 Discrepancies X-BeenThere: p2psip@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Peer-to-Peer SIP working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Sep 2009 10:53:59 -0000 --Apple-Mail-6--605035541 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes Hi, From subversion(04) draft: 3.5.2. Joining, Leaving, and Maintenance Overview The first thing the peer needs to do is form a connection to some "bootstrap node". 10.5. Contacting a Bootstrap Peer When contacting a bootstrap peer, the joining peer sends a Ping request to the bootstrap peer's known IP address with the destination Node-ID set to the joining peer's Node-ID When the requester peer finally does receive a response from some responding peer, it can note the Node-ID in the response and use this Node-ID to start sending requests to join the Overlay Instance as described in There are two problems here, the first is simply terminology. 3.5.2 uses "bootstrap node" 10.5 uses "bootstrap peer" The second, 10.5 does not mention forming a connection and looks as if it was based on a UDP bootstrap mechanism or the multicast bootstrap (10.4). Am I correct that 10.5 is attempting to refer to 3.5.2 and that 10.5 should clear up the fact that your forming a connection to a bootstrap peer and not simply sending a datagram to bootstrap nodes and waiting for responses? REgaRDs, Julian --Apple-Mail-6--605035541 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii

When contacting a bootstrap = peer, the joining peer sends a Ping request to the bootstrap peer's = known IP address with the destination Node-ID set to the joining peer's = Node-ID

node"

10.5 uses = "bootstrap peer"

REgaRDs,

Julian

= --Apple-Mail-6--605035541-- From julian@orchidseed.org Thu Sep 10 04:03:44 2009 Return-Path: X-Original-To: p2psip@core3.amsl.com Delivered-To: p2psip@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 45A9F3A6A1E for ; Thu, 10 Sep 2009 04:03:44 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.506 X-Spam-Level: X-Spam-Status: No, score=-2.506 tagged_above=-999 required=5 tests=[AWL=0.093, 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 aPmsfDc6YPxF for ; Thu, 10 Sep 2009 04:03:43 -0700 (PDT) Received: from n20.c05.mtsvc.net (n20.c05.mtsvc.net [70.32.68.20]) by core3.amsl.com (Postfix) with ESMTP id A09983A69B7 for ; Thu, 10 Sep 2009 04:03:41 -0700 (PDT) Received: from ip68-5-30-57.oc.oc.cox.net ([68.5.30.57]:39759 helo=[10.0.1.8]) by n20.c05.mtsvc.net with esmtpsa (TLS-1.0:RSA_AES_128_CBC_SHA:16) (Exim 4.63) (envelope-from ) id 1MlhRm-0002rh-QB for p2psip@ietf.org; Thu, 10 Sep 2009 04:04:16 -0700 From: jc Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Date: Thu, 10 Sep 2009 04:04:14 -0700 Message-Id: <2EA3FE06-E2DF-4F55-9029-C2E91E98FA63@orchidseed.org> To: p2psip WG Mime-Version: 1.0 (Apple Message framework v1075.2) X-Mailer: Apple Mail (2.1075.2) X-Authenticated-User: 72798 julian@orchidseed.org Subject: [P2PSIP] 12.5.4. Residual Attacks && 12.6.5. Residual Attacks X-BeenThere: p2psip@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Peer-to-Peer SIP working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Sep 2009 11:03:44 -0000 Hi, There are two subsections in section 12 named "Residual Attacks". Julian From ekr@rtfm.com Thu Sep 10 06:45:49 2009 Return-Path: X-Original-To: p2psip@core3.amsl.com Delivered-To: p2psip@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 177603A6AC0 for ; Thu, 10 Sep 2009 06:45:49 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.581 X-Spam-Level: X-Spam-Status: No, score=-1.581 tagged_above=-999 required=5 tests=[AWL=0.395, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id z4oYdtfTUn4D for ; Thu, 10 Sep 2009 06:45:48 -0700 (PDT) Received: from an-out-0708.google.com (an-out-0708.google.com [209.85.132.251]) by core3.amsl.com (Postfix) with ESMTP id 3443F3A6A8C for ; Thu, 10 Sep 2009 06:45:48 -0700 (PDT) Received: by an-out-0708.google.com with SMTP id c5so38972anc.4 for ; Thu, 10 Sep 2009 06:46:20 -0700 (PDT) MIME-Version: 1.0 Received: by 10.100.234.26 with SMTP id g26mr1625541anh.54.1252590380507; Thu, 10 Sep 2009 06:46:20 -0700 (PDT) In-Reply-To: <2EA3FE06-E2DF-4F55-9029-C2E91E98FA63@orchidseed.org> References: <2EA3FE06-E2DF-4F55-9029-C2E91E98FA63@orchidseed.org> Date: Thu, 10 Sep 2009 06:46:20 -0700 Message-ID: From: Eric Rescorla To: jc Content-Type: multipart/alternative; boundary=001636b42ebdade2530473396c04 Cc: p2psip WG Subject: Re: [P2PSIP] 12.5.4. Residual Attacks && 12.6.5. Residual Attacks X-BeenThere: p2psip@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Peer-to-Peer SIP working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Sep 2009 13:45:49 -0000 --001636b42ebdade2530473396c04 Content-Type: text/plain; charset=ISO-8859-1 Yes, that's intentional. 12.5.4 is about routing security and 12.6.5 is aboutstorage security -Ekr On Thu, Sep 10, 2009 at 4:04 AM, jc wrote: > Hi, > There are two subsections in section 12 named "Residual Attacks". > > Julian > _______________________________________________ > P2PSIP mailing list > P2PSIP@ietf.org > https://www.ietf.org/mailman/listinfo/p2psip > --001636b42ebdade2530473396c04 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Yes, that's intentional. 12.5.4 is about routing security and 12.6.5 is= about

storage security

-Ekr

On Thu, Sep 10, 2009 at 4:04 AM, jc <julian@orchidseed.= org> wrote:

Hi,
There are two subsections in section 12 named "Residual Attacks".=

Julian
_______________________________________________
P2PSIP mailing list
P2PSIP@ietf.org = https://www.ietf.org/mailman/listinfo/p2psip

--001636b42ebdade2530473396c04-- From julian@orchidseed.org Fri Sep 11 17:51:02 2009 Return-Path: X-Original-To: p2psip@core3.amsl.com Delivered-To: p2psip@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 500BC3A6879 for ; Fri, 11 Sep 2009 17:51:02 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.066 X-Spam-Level: X-Spam-Status: No, score=-2.066 tagged_above=-999 required=5 tests=[AWL=-0.368, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_42=0.6, MIME_8BIT_HEADER=0.3] 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 2S45vL3imQsw for ; Fri, 11 Sep 2009 17:51:01 -0700 (PDT) Received: from n13.c05.mtsvc.net (n13.c05.mtsvc.net [70.32.68.13]) by core3.amsl.com (Postfix) with ESMTP id 9159A3A683F for ; Fri, 11 Sep 2009 17:51:01 -0700 (PDT) Received: from ip68-5-30-57.oc.oc.cox.net ([68.5.30.57]:46574 helo=[10.0.1.8]) by n13.c05.mtsvc.net with esmtpsa (TLS-1.0:RSA_AES_128_CBC_SHA:16) (Exim 4.63) (envelope-from ) id 1MmGq2-0007fF-6S for p2psip@ietf.org; Fri, 11 Sep 2009 17:51:39 -0700 From: jc Content-Type: multipart/alternative; boundary=Apple-Mail-1--468411159 Date: Fri, 11 Sep 2009 17:51:35 -0700 Message-Id: To: p2psip WG Mime-Version: 1.0 (Apple Message framework v1075.2) X-Mailer: Apple Mail (2.1075.2) X-Authenticated-User: 72798 julian@orchidseed.org Subject: [P2PSIP] =?iso-8859-1?q?10=2E1=2E=A0_Overlay_Configuration_-_draf?= =?iso-8859-1?q?t_version_04?= X-BeenThere: p2psip@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Peer-to-Peer SIP working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 12 Sep 2009 00:51:02 -0000 --Apple-Mail-1--468411159 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes Hi, "required-kinds This element indicates the kinds that members must support. It has three attributes:" This is incorrect and there are some attributes/elements missing. I have broken this down below: Attributes: kind.name - Not mentioned but in xml. kind.id - Not mentioned but in xml. Elements: kind-block - Not Mentioned but in xml. kind data-model max-count max-size kind-signature - Not mentioned but in xml. max-node-multiple - Not always used. access-control Also chord-reload-update-frequency && chord-reload-ping-frequency do not properly represent themselves within the xml. It is "chord:" when it should be at least IMHO "chord:reload:". Julian --Apple-Mail-1--468411159 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii

This = element indicates the kinds that members must support. It has three = attributes:"

This is incorrect and there = are some attributes/elements missing. I have broken this down = below:

Attributes:

kind.name - Not mentioned but in = xml.

kind.id - Not mentioned but in = xml.

Elements:

kind-block - Not = Mentioned but in = xml.

kind

data-model

max-count

max= -size

kind-signature - Not mentioned but in = xml.

max-node-multiple - Not always = used.

access-control

Also = chord-reload-update-frequency && chord-reload-ping-frequency do = not properly represent themselves within the xml. It is "chord:" = when it should be at least IMHO = "chord:reload:".

Julian

= --Apple-Mail-1--468411159-- From julian@orchidseed.org Fri Sep 11 22:15:24 2009 Return-Path: X-Original-To: p2psip@core3.amsl.com Delivered-To: p2psip@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CFAAD3A67EB for ; Fri, 11 Sep 2009 22:15:24 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.479 X-Spam-Level: X-Spam-Status: No, score=-2.479 tagged_above=-999 required=5 tests=[AWL=0.119, BAYES_00=-2.599, HTML_MESSAGE=0.001] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uCr8DA45xmLY for ; Fri, 11 Sep 2009 22:15:24 -0700 (PDT) Received: from n20.c05.mtsvc.net (n20.c05.mtsvc.net [70.32.68.20]) by core3.amsl.com (Postfix) with ESMTP id 046883A672E for ; Fri, 11 Sep 2009 22:15:23 -0700 (PDT) Received: from ip68-5-30-57.oc.oc.cox.net ([68.5.30.57]:46132 helo=[10.0.1.8]) by n20.c05.mtsvc.net with esmtpsa (TLS-1.0:RSA_AES_128_CBC_SHA:16) (Exim 4.63) (envelope-from ) id 1MmKxt-0003Uv-AB for p2psip@ietf.org; Fri, 11 Sep 2009 22:16:02 -0700 From: jc Content-Type: multipart/alternative; boundary=Apple-Mail-1--452551001 Date: Fri, 11 Sep 2009 22:15:55 -0700 Message-Id: <4BE1B9C2-2AD7-48D0-BA50-A3683E2E075E@orchidseed.org> To: p2psip WG Mime-Version: 1.0 (Apple Message framework v1075.2) X-Mailer: Apple Mail (2.1075.2) X-Authenticated-User: 72798 julian@orchidseed.org Subject: [P2PSIP] 10.4. Searching for a Bootstrap Peer X-BeenThere: p2psip@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Peer-to-Peer SIP working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 12 Sep 2009 05:15:25 -0000 --Apple-Mail-1--452551001 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes Hi, This section states: If no cached bootstrap peers are available and the config file has an broadcast-peers element ...however there is no "broadcast-peers" element. Also the draft doesn't mention anywhere that all nodes must subscribe to the multicast group "multicast-bootstrap" if it is found in the configuration file. I assume the later is the intended to be there but simply missing? Julian --Apple-Mail-1--452551001 Content-Transfer-Encoding: 7bit Content-Type: text/html; charset=us-ascii Hi,
This section states:

If no cached bootstrap peers are available and the config file has an broadcast-peers element

...however there is no "broadcast-peers" element. Also the draft doesn't mention anywhere that all nodes must subscribe to the multicast group "multicast-bootstrap"

if it is found in the configuration file. I assume the later is the intended to be there but simply missing?

Julian

--Apple-Mail-1--452551001-- From T.Kluge@gmx.com Wed Sep 16 02:34:57 2009 Return-Path: X-Original-To: p2psip@core3.amsl.com Delivered-To: p2psip@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 987413A67AB for ; Wed, 16 Sep 2009 02:34:57 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.002 X-Spam-Level: X-Spam-Status: No, score=0.002 tagged_above=-999 required=5 tests=[BAYES_50=0.001, STOX_REPLY_TYPE=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 PQXx3enwQ2lc for ; Wed, 16 Sep 2009 02:34:56 -0700 (PDT) Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by core3.amsl.com (Postfix) with SMTP id EFB943A67F3 for ; Wed, 16 Sep 2009 02:34:55 -0700 (PDT) Received: (qmail invoked by alias); 16 Sep 2009 09:35:43 -0000 Received: from unknown (EHLO Thomas) [141.39.41.76] by mail.gmx.net (mp064) with SMTP; 16 Sep 2009 11:35:43 +0200 X-Authenticated: #22022137 X-Provags-ID: V01U2FsdGVkX19yP11iWh9yW6EUHETbFeMhcz4CipTHNFXBAygWqL 7+T5zXjRfT1G8O Message-ID: <3BE49FFF2994498CA09906C42ED01CC5@Thomas> From: "Thomas Kluge" To: Date: Wed, 16 Sep 2009 11:35:55 +0200 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.5843 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579 X-Y-GMX-Trusted: 0 X-FuHaFi: 0.67 Subject: [P2PSIP] Successor via Ping? X-BeenThere: p2psip@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Peer-to-Peer SIP working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Sep 2009 09:38:36 -0000 Section 9.5. Joining states: "In order to populate its neighbor table, JP sends a Ping via the bootstrap node directed at Resource-ID n+1 (directly after its own Resource-ID). This allows it to discover its own successor." I have no idea how this could be accomplished. I would start from the Joining Peer side with a Forwarding Header filled with a Destination List containing the Resource-ID n+1, where I understand the ressource ID is my hashed node id +1. So far so good, I send that to the bootstrap- node. My intention would be to get the node id from my admitting peer (successor). But Ping will only return failure or a little PingAns struct with no information about the node id where it comes from. The Via lists would be empty as stated in 3.3. Routing. So I see no header information which could give me the needed information. What is my error in reasoning here? TIA Thomas From ekr@rtfm.com Wed Sep 16 05:12:45 2009 Return-Path: X-Original-To: p2psip@core3.amsl.com Delivered-To: p2psip@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9E60C3A69ED for ; Wed, 16 Sep 2009 05:12:45 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.661 X-Spam-Level: X-Spam-Status: No, score=-1.661 tagged_above=-999 required=5 tests=[AWL=0.316, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622] 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 BqIJfwn3Jh6a for ; Wed, 16 Sep 2009 05:12:45 -0700 (PDT) Received: from mail-yx0-f194.google.com (mail-yx0-f194.google.com [209.85.210.194]) by core3.amsl.com (Postfix) with ESMTP id DBCF13A697A for ; Wed, 16 Sep 2009 05:12:44 -0700 (PDT) Received: by yxe32 with SMTP id 32so949281yxe.5 for ; Wed, 16 Sep 2009 05:13:31 -0700 (PDT) MIME-Version: 1.0 Received: by 10.101.135.36 with SMTP id m36mr8978386ann.49.1253103211076; Wed, 16 Sep 2009 05:13:31 -0700 (PDT) In-Reply-To: <3BE49FFF2994498CA09906C42ED01CC5@Thomas> References: <3BE49FFF2994498CA09906C42ED01CC5@Thomas> Date: Wed, 16 Sep 2009 05:13:31 -0700 Message-ID: From: Eric Rescorla To: Thomas Kluge Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: p2psip@ietf.org Subject: Re: [P2PSIP] Successor via Ping? X-BeenThere: p2psip@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Peer-to-Peer SIP working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Sep 2009 12:12:45 -0000 All messages are signed and this includes the signer identity. -Ekr On Wed, Sep 16, 2009 at 2:35 AM, Thomas Kluge wrote: > > Section 9.5. Joining states: > "In order to populate its neighbor table, JP sends a Ping via the > =A0bootstrap node directed at Resource-ID n+1 (directly after its own > =A0Resource-ID). =A0This allows it to discover its own successor." > > > I have no idea how this could be accomplished. I would start from the > Joining Peer side with a Forwarding Header filled with a Destination List > containing the Resource-ID n+1, where I understand the ressource ID > is my hashed node id +1. So far so good, I send that to the bootstrap- > node. My intention would be to get the node id from my admitting peer > (successor). But Ping will only return failure or a little PingAns struct > with > no information about the node id where it comes from. The Via lists would > be empty as stated in 3.3. Routing. So I see no header information which > could give me the needed information. > > What is my error in reasoning here? > > TIA > Thomas > _______________________________________________ > P2PSIP mailing list > P2PSIP@ietf.org > https://www.ietf.org/mailman/listinfo/p2psip > From julian@orchidseed.org Wed Sep 16 22:29:54 2009 Return-Path: X-Original-To: p2psip@core3.amsl.com Delivered-To: p2psip@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9A8753A67A7 for ; Wed, 16 Sep 2009 22:29:54 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.49 X-Spam-Level: X-Spam-Status: No, score=-2.49 tagged_above=-999 required=5 tests=[AWL=0.109, 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 BxRHsZAq+NQj for ; Wed, 16 Sep 2009 22:29:53 -0700 (PDT) Received: from n12.c05.mtsvc.net (n12.c05.mtsvc.net [70.32.68.12]) by core3.amsl.com (Postfix) with ESMTP id E39133A6840 for ; Wed, 16 Sep 2009 22:29:53 -0700 (PDT) Received: from ip68-5-30-57.oc.oc.cox.net ([68.5.30.57]:34653 helo=[10.0.1.8]) by n12.c05.mtsvc.net with esmtpsa (TLS-1.0:RSA_AES_128_CBC_SHA:16) (Exim 4.63) (envelope-from ) id 1Mo9Zr-0001oR-9Q for p2psip@ietf.org; Wed, 16 Sep 2009 22:30:44 -0700 From: jc Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Date: Wed, 16 Sep 2009 22:30:39 -0700 Message-Id: <2DCCC1BB-32FB-4FAC-9D04-266AB8607D0B@orchidseed.org> To: p2psip WG Mime-Version: 1.0 (Apple Message framework v1076) X-Mailer: Apple Mail (2.1076) X-Authenticated-User: 72798 julian@orchidseed.org Subject: [P2PSIP] 10.3.1 Self-Generated Credentials X-BeenThere: p2psip@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Peer-to-Peer SIP working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Sep 2009 05:29:55 -0000 Hi, States "MAY contain any user name of the user choice", this is subjectAltName? Julian From julian@orchidseed.org Thu Sep 17 02:07:47 2009 Return-Path: X-Original-To: p2psip@core3.amsl.com Delivered-To: p2psip@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 78F1D28C174 for ; Thu, 17 Sep 2009 02:07:47 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.499 X-Spam-Level: X-Spam-Status: No, score=-2.499 tagged_above=-999 required=5 tests=[AWL=0.099, BAYES_00=-2.599, HTML_MESSAGE=0.001] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vu5bzxgCRlie for ; Thu, 17 Sep 2009 02:07:46 -0700 (PDT) Received: from n20.c05.mtsvc.net (n20.c05.mtsvc.net [70.32.68.20]) by core3.amsl.com (Postfix) with ESMTP id 9E38A28C0CE for ; Thu, 17 Sep 2009 02:07:46 -0700 (PDT) Received: from ip68-5-30-57.oc.oc.cox.net ([68.5.30.57]:38923 helo=[10.0.1.8]) by n20.c05.mtsvc.net with esmtpsa (TLS-1.0:RSA_AES_128_CBC_SHA:16) (Exim 4.63) (envelope-from ) id 1MoCyi-0007kc-Ab for p2psip@ietf.org; Thu, 17 Sep 2009 02:08:37 -0700 From: jc Mime-Version: 1.0 (Apple Message framework v1076) Content-Type: multipart/alternative; boundary=Apple-Mail-1--6598394 Date: Thu, 17 Sep 2009 02:08:28 -0700 In-Reply-To: <2DCCC1BB-32FB-4FAC-9D04-266AB8607D0B@orchidseed.org> To: p2psip WG References: <2DCCC1BB-32FB-4FAC-9D04-266AB8607D0B@orchidseed.org> Message-Id: X-Mailer: Apple Mail (2.1076) X-Authenticated-User: 72798 julian@orchidseed.org Subject: Re: [P2PSIP] 10.3.1 Self-Generated Credentials X-BeenThere: p2psip@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Peer-to-Peer SIP working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Sep 2009 09:07:47 -0000 --Apple-Mail-1--6598394 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes I looked at some other areas and the problem is the draft doesn't clearly state fields that X509 certificates MUST contain or misrepresents them case-wise. For instance: 7. Certificate Store Usage user name Node-ID 12.5.1. Authorization User name Node-ID Serial There are several other references as well. Since this is a string variable inside of an X509 certificate the names need to be case normalized. Julian On Sep 16, 2009, at 10:30 PM, jc wrote: > Hi, > States "MAY contain any user name of the user choice", this is > subjectAltName? User name or user name? > > Julian > _______________________________________________ > P2PSIP mailing list > P2PSIP@ietf.org > https://www.ietf.org/mailman/listinfo/p2psip --Apple-Mail-1--6598394 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii I looked at some other areas = and the problem is the draft doesn't clearly state fields that X509 = certificates MUST contain or misrepresents them case-wise.

For = instance:

7. Certificate Store Usage
user = name

Node-ID

12.5.1. Authorization
User = name
Node-ID
Serial

There are several other references as = well. Since this is a string variable inside of an X509 certificate the = names need to be case normalized.

Julian

On = Sep 16, 2009, at 10:30 PM, jc wrote:

Hi,
States "MAY contain any user name of the user = choice", this is = subjectAltName?

User name or user = name?

Julian
______________________________________________= _
P2PSIP mailing list
P2PSIP@ietf.org
https://www.ietf.or= g/mailman/listinfo/p2psip

= --Apple-Mail-1--6598394-- From ekr@rtfm.com Thu Sep 17 06:50:12 2009 Return-Path: X-Original-To: p2psip@core3.amsl.com Delivered-To: p2psip@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id EEFA43A69EC for ; Thu, 17 Sep 2009 06:50:12 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.689 X-Spam-Level: X-Spam-Status: No, score=-1.689 tagged_above=-999 required=5 tests=[AWL=0.288, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622] 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 t929UfduZnq6 for ; Thu, 17 Sep 2009 06:50:12 -0700 (PDT) Received: from an-out-0708.google.com (an-out-0708.google.com [209.85.132.242]) by core3.amsl.com (Postfix) with ESMTP id D710B3A692C for ; Thu, 17 Sep 2009 06:50:10 -0700 (PDT) Received: by an-out-0708.google.com with SMTP id c5so155174anc.4 for ; Thu, 17 Sep 2009 06:50:59 -0700 (PDT) MIME-Version: 1.0 Received: by 10.100.17.27 with SMTP id 27mr69681anq.199.1253195459499; Thu, 17 Sep 2009 06:50:59 -0700 (PDT) In-Reply-To: References: <2DCCC1BB-32FB-4FAC-9D04-266AB8607D0B@orchidseed.org> Date: Thu, 17 Sep 2009 06:50:59 -0700 Message-ID: From: Eric Rescorla To: jc Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: p2psip WG Subject: Re: [P2PSIP] 10.3.1 Self-Generated Credentials X-BeenThere: p2psip@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Peer-to-Peer SIP working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Sep 2009 13:50:13 -0000 These aren't fields in the certificate. The relevant field is either DN or subjectAltName (I don't have the draft in front of me to remember what we decided). -Ekr On Thu, Sep 17, 2009 at 2:08 AM, jc wrote: > I looked at some other areas and the problem is the draft doesn't clearly > state fields that X509 certificates MUST contain or misrepresents them > case-wise. > > For instance: > > 7. =A0Certificate Store Usage > user name > Node-ID > 12.5.1. Authorization > User name > Node-ID > Serial > > There are several other references as well. Since this is a string variab= le > inside of an X509 certificate the names need to be case normalized. > Julian > > On Sep 16, 2009, at 10:30 PM, jc wrote: > > Hi, > States "MAY contain any user name of the user choice", =A0this is > subjectAltName? > > User name or user name? > > Julian > _______________________________________________ > P2PSIP mailing list > P2PSIP@ietf.org > https://www.ietf.org/mailman/listinfo/p2psip > > > _______________________________________________ > P2PSIP mailing list > P2PSIP@ietf.org > https://www.ietf.org/mailman/listinfo/p2psip > > From julian@orchidseed.org Thu Sep 17 10:52:32 2009 Return-Path: X-Original-To: p2psip@core3.amsl.com Delivered-To: p2psip@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id ADBA33A6993 for ; Thu, 17 Sep 2009 10:52:32 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.507 X-Spam-Level: X-Spam-Status: No, score=-2.507 tagged_above=-999 required=5 tests=[AWL=0.092, 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 nrQJ+FrBgX79 for ; Thu, 17 Sep 2009 10:52:32 -0700 (PDT) Received: from n12.c05.mtsvc.net (n12.c05.mtsvc.net [70.32.68.12]) by core3.amsl.com (Postfix) with ESMTP id 10A713A6992 for ; Thu, 17 Sep 2009 10:52:31 -0700 (PDT) Received: from ip68-5-30-57.oc.oc.cox.net ([68.5.30.57]:33721 helo=[10.0.1.8]) by n12.c05.mtsvc.net with esmtpsa (TLS-1.0:RSA_AES_128_CBC_SHA:16) (Exim 4.63) (envelope-from ) id 1MoLAX-0000QQ-Kf for p2psip@ietf.org; Thu, 17 Sep 2009 10:53:23 -0700 From: jc Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Date: Thu, 17 Sep 2009 10:53:11 -0700 Message-Id: To: p2psip WG Mime-Version: 1.0 (Apple Message framework v1076) X-Mailer: Apple Mail (2.1076) X-Authenticated-User: 72798 julian@orchidseed.org Subject: [P2PSIP] 3.1 Security and Identification X-BeenThere: p2psip@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Peer-to-Peer SIP working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Sep 2009 17:52:32 -0000 "RELOAD supports two certificate issuance models." This should state "Three", central enrollment, self-signed and shared key. Julian From julian@orchidseed.org Thu Sep 17 14:07:22 2009 Return-Path: X-Original-To: p2psip@core3.amsl.com Delivered-To: p2psip@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8931D3A6902 for ; Thu, 17 Sep 2009 14:07:22 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.513 X-Spam-Level: X-Spam-Status: No, score=-2.513 tagged_above=-999 required=5 tests=[AWL=0.086, 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 UCy39taqBPUx for ; Thu, 17 Sep 2009 14:07:21 -0700 (PDT) Received: from n13.c05.mtsvc.net (n13.c05.mtsvc.net [70.32.68.13]) by core3.amsl.com (Postfix) with ESMTP id D611D3A6821 for ; Thu, 17 Sep 2009 14:07:21 -0700 (PDT) Received: from ip68-5-30-57.oc.oc.cox.net ([68.5.30.57]:44294 helo=[10.0.1.8]) by n13.c05.mtsvc.net with esmtpsa (TLS-1.0:RSA_AES_128_CBC_SHA:16) (Exim 4.63) (envelope-from ) id 1MoOD5-0001HS-Jm; Thu, 17 Sep 2009 14:08:14 -0700 Mime-Version: 1.0 (Apple Message framework v1076) Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes From: jc In-Reply-To: Date: Thu, 17 Sep 2009 14:08:07 -0700 Content-Transfer-Encoding: 7bit Message-Id: References: <2DCCC1BB-32FB-4FAC-9D04-266AB8607D0B@orchidseed.org> To: Eric Rescorla X-Mailer: Apple Mail (2.1076) X-Authenticated-User: 72798 julian@orchidseed.org Cc: p2psip WG Subject: Re: [P2PSIP] 10.3.1 Self-Generated Credentials X-BeenThere: p2psip@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Peer-to-Peer SIP working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Sep 2009 21:07:22 -0000 If it is simply subjectAltName then I guess the question is how is data stored here? It may hold multiple Node-ID's, a single user name, and other elements so it MUST be a dictionary or key/value pairs or some other storage. Julian On Sep 17, 2009, at 6:50 AM, Eric Rescorla wrote: > These aren't fields in the certificate. The relevant field is either > DN or > subjectAltName (I don't have the draft in front of me to remember what > we decided). > > -Ekr > From ekr@rtfm.com Thu Sep 17 14:09:09 2009 Return-Path: X-Original-To: p2psip@core3.amsl.com Delivered-To: p2psip@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B92113A6A38 for ; Thu, 17 Sep 2009 14:09:08 -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 7tV8eAW7dAI5 for ; Thu, 17 Sep 2009 14:09:07 -0700 (PDT) Received: from mail-px0-f173.google.com (mail-px0-f173.google.com [209.85.216.173]) by core3.amsl.com (Postfix) with ESMTP id 5C4CA3A6AB2 for ; Thu, 17 Sep 2009 14:08:53 -0700 (PDT) Received: by pxi3 with SMTP id 3so335128pxi.31 for ; Thu, 17 Sep 2009 14:09:40 -0700 (PDT) Received: by 10.114.164.4 with SMTP id m4mr808127wae.172.1253221780220; Thu, 17 Sep 2009 14:09:40 -0700 (PDT) Received: from ?10.156.93.236? ([166.205.134.45]) by mx.google.com with ESMTPS id 20sm506716pxi.0.2009.09.17.14.09.38 (version=TLSv1/SSLv3 cipher=RC4-MD5); Thu, 17 Sep 2009 14:09:39 -0700 (PDT) References: <2DCCC1BB-32FB-4FAC-9D04-266AB8607D0B@orchidseed.org>

Message-Id: From: Eric Rescorla To: jc In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit X-Mailer: iPhone Mail (7A400) Mime-Version: 1.0 (iPhone Mail 7A400) Date: Thu, 17 Sep 2009 14:09:29 -0700 Cc: p2psip WG Subject: Re: [P2PSIP] 10.3.1 Self-Generated Credentials X-BeenThere: p2psip@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Peer-to-Peer SIP working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Sep 2009 21:09:09 -0000 Certs can have multiple SAN fields Ek On Sep 17, 2009, at 2:08 PM, jc wrote: > If it is simply subjectAltName then I guess the question is how is > data stored here? It may hold multiple Node-ID's, a single user > name, and other elements so it MUST be a dictionary or key/value > pairs or some other storage. > > Julian > > On Sep 17, 2009, at 6:50 AM, Eric Rescorla wrote: > >> These aren't fields in the certificate. The relevant field is >> either DN or >> subjectAltName (I don't have the draft in front of me to remember >> what >> we decided). >> >> -Ekr >> > From julian@orchidseed.org Thu Sep 17 14:21:06 2009 Return-Path: X-Original-To: p2psip@core3.amsl.com Delivered-To: p2psip@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 76DD33A6941 for ; Thu, 17 Sep 2009 14:21:06 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.519 X-Spam-Level: X-Spam-Status: No, score=-2.519 tagged_above=-999 required=5 tests=[AWL=0.080, 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 qQwWFUTmVOkY for ; Thu, 17 Sep 2009 14:21:05 -0700 (PDT) Received: from n20.c05.mtsvc.net (n20.c05.mtsvc.net [70.32.68.20]) by core3.amsl.com (Postfix) with ESMTP id B724C3A68D5 for ; Thu, 17 Sep 2009 14:21:05 -0700 (PDT) Received: from ip68-5-30-57.oc.oc.cox.net ([68.5.30.57]:40056 helo=[10.0.1.8]) by n20.c05.mtsvc.net with esmtpsa (TLS-1.0:RSA_AES_128_CBC_SHA:16) (Exim 4.63) (envelope-from ) id 1MoOQO-0005te-Oy; Thu, 17 Sep 2009 14:21:58 -0700 Mime-Version: 1.0 (Apple Message framework v1076) Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes From: jc In-Reply-To: Date: Thu, 17 Sep 2009 14:21:55 -0700 Content-Transfer-Encoding: 7bit Message-Id: <3572A849-FAFC-43AE-A4B5-84417CC9E54B@orchidseed.org> References: <2DCCC1BB-32FB-4FAC-9D04-266AB8607D0B@orchidseed.org>

To: Eric Rescorla X-Mailer: Apple Mail (2.1076) X-Authenticated-User: 72798 julian@orchidseed.org Cc: p2psip WG Subject: Re: [P2PSIP] 10.3.1 Self-Generated Credentials X-BeenThere: p2psip@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Peer-to-Peer SIP working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Sep 2009 21:21:06 -0000 Right thanks, however these SAN fields aren't in the draft and MUST be for implementation. Certificate example: NID_subject_alt_name "node_id:0123456789" NID_subject_alt_name "node_id:0123456987" NID_subject_alt_name "user_name:foo@bar.com" Julian On Sep 17, 2009, at 2:09 PM, Eric Rescorla wrote: > Certs can have multiple SAN fields > > Ek > > On Sep 17, 2009, at 2:08 PM, jc wrote: > >> If it is simply subjectAltName then I guess the question is how is >> data stored here? It may hold multiple Node-ID's, a single user >> name, and other elements so it MUST be a dictionary or key/value >> pairs or some other storage. >> >> Julian >> >> On Sep 17, 2009, at 6:50 AM, Eric Rescorla wrote: >> >>> These aren't fields in the certificate. The relevant field is >>> either DN or >>> subjectAltName (I don't have the draft in front of me to remember >>> what >>> we decided). >>> >>> -Ekr >>> >> From ekr@rtfm.com Thu Sep 17 14:43:07 2009 Return-Path: X-Original-To: p2psip@core3.amsl.com Delivered-To: p2psip@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id EA7673A69B4 for ; Thu, 17 Sep 2009 14:43:06 -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 HhSHyT-FxP1Z for ; Thu, 17 Sep 2009 14:43:03 -0700 (PDT) Received: from mail-px0-f173.google.com (mail-px0-f173.google.com [209.85.216.173]) by core3.amsl.com (Postfix) with ESMTP id EB12E3A6A7E for ; Thu, 17 Sep 2009 14:42:55 -0700 (PDT) Received: by pxi3 with SMTP id 3so354643pxi.31 for ; Thu, 17 Sep 2009 14:43:29 -0700 (PDT) Received: by 10.115.114.7 with SMTP id r7mr915049wam.72.1253223809498; Thu, 17 Sep 2009 14:43:29 -0700 (PDT) Received: from ?10.156.93.236? ([166.205.134.45]) by mx.google.com with ESMTPS id 23sm520623pxi.9.2009.09.17.14.43.27 (version=TLSv1/SSLv3 cipher=RC4-MD5); Thu, 17 Sep 2009 14:43:28 -0700 (PDT) References: <2DCCC1BB-32FB-4FAC-9D04-266AB8607D0B@orchidseed.org>

<3572A849-FAFC-43AE-A4B5-84417CC9E54B@orchidseed.org> Message-Id: <6EDCBF46-37E0-4491-9103-5BC1FA3DBA0E@rtfm.com> From: Eric Rescorla To: jc In-Reply-To: <3572A849-FAFC-43AE-A4B5-84417CC9E54B@orchidseed.org> Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit X-Mailer: iPhone Mail (7A400) Mime-Version: 1.0 (iPhone Mail 7A400) Date: Thu, 17 Sep 2009 14:43:20 -0700 Cc: p2psip WG Subject: Re: [P2PSIP] 10.3.1 Self-Generated Credentials X-BeenThere: p2psip@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Peer-to-Peer SIP working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Sep 2009 21:43:07 -0000 It is in the draft in s 10.3. nodeids are expressed as Uris. User names are rfc822names Ekr On Sep 17, 2009, at 2:21 PM, jc wrote: > Right thanks, however these SAN fields aren't in the draft and MUST > be for implementation. > > Certificate example: > > NID_subject_alt_name "node_id:0123456789" > NID_subject_alt_name "node_id:0123456987" > NID_subject_alt_name "user_name:foo@bar.com" > > Julian > > On Sep 17, 2009, at 2:09 PM, Eric Rescorla wrote: > >> Certs can have multiple SAN fields >> >> Ek >> >> On Sep 17, 2009, at 2:08 PM, jc wrote: >> >>> If it is simply subjectAltName then I guess the question is how is >>> data stored here? It may hold multiple Node-ID's, a single user >>> name, and other elements so it MUST be a dictionary or key/value >>> pairs or some other storage. >>> >>> Julian >>> >>> On Sep 17, 2009, at 6:50 AM, Eric Rescorla wrote: >>> >>>> These aren't fields in the certificate. The relevant field is >>>> either DN or >>>> subjectAltName (I don't have the draft in front of me to remember >>>> what >>>> we decided). >>>> >>>> -Ekr >>>> >>> > From wwwrun@core3.amsl.com Thu Sep 17 09:26:16 2009 Return-Path: X-Original-To: p2psip@ietf.org Delivered-To: p2psip@core3.amsl.com Received: by core3.amsl.com (Postfix, from userid 30) id 674DD28C2BB; Thu, 17 Sep 2009 09:26:16 -0700 (PDT) To: even.roni@huawei.com, dbryan@ethernot.org, jiang.x.f@huawei.com, melodysong@huawei.com From: IETF Secretariat Message-Id: <20090917162616.674DD28C2BB@core3.amsl.com> Date: Thu, 17 Sep 2009 09:26:16 -0700 (PDT) X-Mailman-Approved-At: Fri, 18 Sep 2009 14:09:03 -0700 Cc: p2psip@ietf.org, ipr-announce@ietf.org Subject: [P2PSIP] Posting of IPR Disclosure related to HUAWEI TECHNOLOGIES CO., LTD 's Statement about IPR related to draft-ietf-p2psip-diagnostics-01 X-BeenThere: p2psip@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Peer-to-Peer SIP working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Sep 2009 16:26:16 -0000 Dear Roni Even, David Bryan, XingFeng Jiang, Song Yongchao: An IPR disclosure that pertains to your Internet-Draft entitled "P2PSIP Overlay Diagnostics" (draft-ietf-p2psip-diagnostics) was submitted to the IETF Secretariat on 2009-09-17 and has been posted on the "IETF Page of Intellectual Property Rights Disclosures" (https://datatracker.ietf.org/ipr/1190/). The title of the IPR disclosure is "HUAWEI TECHNOLOGIES CO.,LTD 's Statement about IPR related to draft-ietf-p2psip-diagnostics-01." The IETF Secretariat From wwwrun@core3.amsl.com Fri Sep 18 12:12:16 2009 Return-Path: X-Original-To: p2psip@ietf.org Delivered-To: p2psip@core3.amsl.com Received: by core3.amsl.com (Postfix, from userid 30) id 9528F3A6B73; Fri, 18 Sep 2009 12:12:16 -0700 (PDT) To: ekr@networkresonance.com, fluffy@cisco.com, salman@cs.columbia.edu, hgs@cs.columbia.edu, bbl@lowekamp.net From: IETF Secretariat Message-Id: <20090918191216.9528F3A6B73@core3.amsl.com> Date: Fri, 18 Sep 2009 12:12:16 -0700 (PDT) X-Mailman-Approved-At: Fri, 18 Sep 2009 14:09:04 -0700 Cc: p2psip@ietf.org, ipr-announce@ietf.org Subject: [P2PSIP] Posting of IPR Disclosure related to QUALCOMM Incorporated's Statement about IPR related to draft-ietf-p2psip-base-03 X-BeenThere: p2psip@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Peer-to-Peer SIP working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Sep 2009 19:12:16 -0000 Dear Eric Rescorla, Cullen Jennings, Salman Baset, Henning Schulzrinne, Bruce Lowekamp: An IPR disclosure that pertains to your Internet-Draft entitled "REsource LOcation And Discovery (RELOAD) Base Protocol" (draft-ietf-p2psip-base) was submitted to the IETF Secretariat on 2009-09-17 and has been posted on the "IETF Page of Intellectual Property Rights Disclosures" (https://datatracker.ietf.org/ipr/1191/). The title of the IPR disclosure is "QUALCOMM Incorporated's Statement about IPR related to draft-ietf-p2psip-base-03." The IETF Secretariat From julian@orchidseed.org Fri Sep 18 17:16:42 2009 Return-Path: X-Original-To: p2psip@core3.amsl.com Delivered-To: p2psip@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D79DB3A6A36 for ; Fri, 18 Sep 2009 17:16:42 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.524 X-Spam-Level: X-Spam-Status: No, score=-2.524 tagged_above=-999 required=5 tests=[AWL=0.075, 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 daMZ8A-ZRPbJ for ; Fri, 18 Sep 2009 17:16:42 -0700 (PDT) Received: from n12.c05.mtsvc.net (n12.c05.mtsvc.net [70.32.68.12]) by core3.amsl.com (Postfix) with ESMTP id 3621A3A63CB for ; Fri, 18 Sep 2009 17:16:42 -0700 (PDT) Received: from ip68-5-30-57.oc.oc.cox.net ([68.5.30.57]:39934 helo=[10.0.1.8]) by n12.c05.mtsvc.net with esmtpsa (TLS-1.0:RSA_AES_128_CBC_SHA:16) (Exim 4.63) (envelope-from ) id 1Mondv-0003HJ-RB for p2psip@ietf.org; Fri, 18 Sep 2009 17:17:37 -0700 From: jc Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Date: Fri, 18 Sep 2009 17:17:33 -0700 Message-Id: <6F780DD4-F04E-4C8D-B7FF-8ACA85729B76@orchidseed.org> To: p2psip WG Mime-Version: 1.0 (Apple Message framework v1076) X-Mailer: Apple Mail (2.1076) X-Authenticated-User: 72798 julian@orchidseed.org Subject: [P2PSIP] 10.3 Credentials - URL Paramaters Not Possible X-BeenThere: p2psip@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Peer-to-Peer SIP working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 19 Sep 2009 00:16:42 -0000 Hi, "If authentication is required, there is a URL parameter of "password" and..." It's not possible to send URL parameters with a POST with a content- type of application/pkix-cert. Julian From ekr@rtfm.com Fri Sep 18 17:30:33 2009 Return-Path: X-Original-To: p2psip@core3.amsl.com Delivered-To: p2psip@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 492EB3A6861 for ; Fri, 18 Sep 2009 17:30:33 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.713 X-Spam-Level: X-Spam-Status: No, score=-1.713 tagged_above=-999 required=5 tests=[AWL=0.264, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622] 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 7wE4+iCaaRjF for ; Fri, 18 Sep 2009 17:30:32 -0700 (PDT) Received: from mail-yx0-f192.google.com (mail-yx0-f192.google.com [209.85.210.192]) by core3.amsl.com (Postfix) with ESMTP id B41CC3A6855 for ; Fri, 18 Sep 2009 17:30:27 -0700 (PDT) Received: by yxe30 with SMTP id 30so1604953yxe.29 for ; Fri, 18 Sep 2009 17:31:10 -0700 (PDT) MIME-Version: 1.0 Received: by 10.90.8.10 with SMTP id 10mr1434310agh.114.1253320269803; Fri, 18 Sep 2009 17:31:09 -0700 (PDT) In-Reply-To: <6F780DD4-F04E-4C8D-B7FF-8ACA85729B76@orchidseed.org> References: <6F780DD4-F04E-4C8D-B7FF-8ACA85729B76@orchidseed.org> Date: Fri, 18 Sep 2009 17:31:09 -0700 Message-ID: From: Eric Rescorla To: jc Content-Type: text/plain; charset=ISO-8859-1 Cc: p2psip WG Subject: Re: [P2PSIP] 10.3 Credentials - URL Paramaters Not Possible X-BeenThere: p2psip@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Peer-to-Peer SIP working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 19 Sep 2009 00:30:33 -0000 Hmm... I'm not sure that's actually true. I just skimmed through the relevant sections of RFC 2616 and I actually don't see a prohibition on using query parameters with POST. What section do you believe prohibits this? -Ekr On Fri, Sep 18, 2009 at 5:17 PM, jc wrote: > Hi, > > "If authentication is required, there is a URL parameter of "password" > and..." > > It's not possible to send URL parameters with a POST with a content-type of > application/pkix-cert. > > Julian > _______________________________________________ > P2PSIP mailing list > P2PSIP@ietf.org > https://www.ietf.org/mailman/listinfo/p2psip > From theo@crazygreek.co.uk Fri Sep 18 17:37:16 2009 Return-Path: X-Original-To: p2psip@core3.amsl.com Delivered-To: p2psip@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4D9513A68C2 for ; Fri, 18 Sep 2009 17:37:16 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.677 X-Spam-Level: X-Spam-Status: No, score=-5.677 tagged_above=-999 required=5 tests=[AWL=0.300, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, 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 uLtCn5S8Yq-D for ; Fri, 18 Sep 2009 17:37:15 -0700 (PDT) Received: from exprod7og104.obsmtp.com (exprod7og104.obsmtp.com [64.18.2.161]) by core3.amsl.com (Postfix) with SMTP id E89383A6824 for ; Fri, 18 Sep 2009 17:37:14 -0700 (PDT) Received: from source ([209.85.218.219]) by exprod7ob104.postini.com ([64.18.6.12]) with SMTP ID DSNKSrQn8Q++BkoFL6YRWLmqBjmmC322xy2i@postini.com; Fri, 18 Sep 2009 17:38:11 PDT Received: by bwz19 with SMTP id 19so1137029bwz.35 for ; Fri, 18 Sep 2009 17:38:09 -0700 (PDT) MIME-Version: 1.0 Received: by 10.223.1.18 with SMTP id 18mr534334fad.90.1253320689082; Fri, 18 Sep 2009 17:38:09 -0700 (PDT) In-Reply-To: <6F780DD4-F04E-4C8D-B7FF-8ACA85729B76@orchidseed.org> References: <6F780DD4-F04E-4C8D-B7FF-8ACA85729B76@orchidseed.org> From: Theo Zourzouvillys Date: Fri, 18 Sep 2009 17:37:49 -0700 Message-ID: <167dfb9b0909181737x331fc2f3s5f668b2d3699051@mail.gmail.com> To: jc Content-Type: text/plain; charset=ISO-8859-1 Cc: p2psip WG Subject: Re: [P2PSIP] 10.3 Credentials - URL Paramaters Not Possible X-BeenThere: p2psip@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Peer-to-Peer SIP working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 19 Sep 2009 00:37:16 -0000 On Fri, Sep 18, 2009 at 5:17 PM, jc wrote: > It's not possible to send URL parameters with a POST with a content-type of > application/pkix-cert. Yes, it is possible - and a totally valid thing to do. ~ Theo From julian@orchidseed.org Fri Sep 18 17:52:16 2009 Return-Path: X-Original-To: p2psip@core3.amsl.com Delivered-To: p2psip@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AAF683A68B1 for ; Fri, 18 Sep 2009 17:52:16 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.529 X-Spam-Level: X-Spam-Status: No, score=-2.529 tagged_above=-999 required=5 tests=[AWL=0.070, 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 gqGaF2TYCbte for ; Fri, 18 Sep 2009 17:52:16 -0700 (PDT) Received: from n12.c05.mtsvc.net (n12.c05.mtsvc.net [70.32.68.12]) by core3.amsl.com (Postfix) with ESMTP id EEAAE3A67FB for ; Fri, 18 Sep 2009 17:52:15 -0700 (PDT) Received: from ip68-5-30-57.oc.oc.cox.net ([68.5.30.57]:40373 helo=[10.0.1.8]) by n12.c05.mtsvc.net with esmtpsa (TLS-1.0:RSA_AES_128_CBC_SHA:16) (Exim 4.63) (envelope-from ) id 1MooCI-00032l-Su; Fri, 18 Sep 2009 17:53:08 -0700 Mime-Version: 1.0 (Apple Message framework v1076) Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes From: jc