From safe-bounces@ietf.org Wed Jul 11 20:32:38 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1I8mbm-0006NT-NS; Wed, 11 Jul 2007 20:32:38 -0400 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1I8mbl-0006Gr-K6 for safe@ietf.org; Wed, 11 Jul 2007 20:32:37 -0400 Received: from sj-iport-6.cisco.com ([171.71.176.117]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I8mba-0005gU-6O for safe@ietf.org; Wed, 11 Jul 2007 20:32:37 -0400 Received: from sj-dkim-4.cisco.com ([171.71.179.196]) by sj-iport-6.cisco.com with ESMTP; 11 Jul 2007 17:32:17 -0700 X-IronPort-AV: i="unknown"; a="180561022:sNHT0" 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 l6C0WHl7017722 for ; Wed, 11 Jul 2007 17:32:17 -0700 Received: from dwingwxp ([10.32.240.195]) by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id l6C0WGmo014162 for ; Thu, 12 Jul 2007 00:32:17 GMT From: "Dan Wing" To: Date: Wed, 11 Jul 2007 17:32:16 -0700 Message-ID: <14a801c7c41c$19ae2500$c3f0200a@amer.cisco.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.3138 Thread-Index: AcfDHq/Y0SrXu2TfTRWh6vYn69OlqQA/TAzQ DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=3812; t=1184200337; x=1185064337; c=relaxed/simple; s=sjdkim4002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=dwing@cisco.com; z=From:=20=22Dan=20Wing=22=20 |Subject:=20nat-control-stun-usage-03 |Sender:=20; bh=zJUktt+pz2Eu9cEhbh0Fy16v4gPw7ks1Ee2afbx3hx4=; b=PSTnrDqdzDWImjvUO6kzqO2M9jpXYhJVPusbm5NxtBGYGlm008ivxMed6K5tO0BwyxtQc6NT PNgdYhndR0DCg3Q6ahPnvArDVVvSIPZPhRKRlWzCGUYGkXJVL0VTxi5W; Authentication-Results: sj-dkim-4; header.From=dwing@cisco.com; dkim=pass (s ig from cisco.com/sjdkim4002 verified; ); X-Spam-Score: 0.0 (/) X-Scan-Signature: 6e922792024732fb1bb6f346e63517e4 Subject: [SAFE] nat-control-stun-usage-03 X-BeenThere: safe@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Self-Address Fixing Evolution List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: safe-bounces@ietf.org FYI, a new version was posted yesterday. Changes between -03 and 02: o Removed TLS from normal STUN operation (as few use it, and ICE makes it unnecessary anyway) o BOOTNONCE attribute replaces STUN Control's previous use of TLS. o Added "MIP-capable" bit to TAG attribute o Removed "inside-out" discovery technique. Comments welcome. See you in Chicago. -d > -----Original Message----- > From: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org] > Sent: Tuesday, July 10, 2007 11:15 AM > To: i-d-announce@ietf.org > Subject: I-D ACTION:draft-wing-behave-nat-control-stun-usage-03.txt > > A New Internet-Draft is available from the on-line Internet-Drafts > directories. > > > Title : Discovering, Querying, and > Controlling Firewalls and NATs using STUN > Author(s) : D. Wing, et al. > Filename : > draft-wing-behave-nat-control-stun-usage-03.txt > Pages : 27 > Date : 2007-7-10 > > Simple Traversal Underneath NAT (STUN) is a mechanism for traversing > NATs. STUN requests are transmitted through a NAT to external STUN > servers. While this works very well, its two primary drawbacks are > the inability to modify the properties of a NAT binding > and the need > to query a public STUN server for every new NAT binding > (e.g., every > phone call). These drawbacks require frequent messages > which present a load on servers (like SIP servers and STUN > servers) and are bad for > low speed access networks, such as cellular access. > > This document describes two mechanisms to discover NATs > and firewalls > and a mechanism to query and control them. With these mechanisms, > binding discovery and keepalive traffic can be reduced to involve > only the necessary NATs or firewalls. At the same time, backwards > compatibility with NATs and firewalls that do not support this > document is retained, which allows for incremental deployment of > these mechanisms. > > A URL for this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-wing-behave-nat-cont > rol-stun-usage-03.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-wing-behave-nat-control-stun-usage-03.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-wing-behave-nat-control-stun-usage-03.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. > _______________________________________________ SAFE mailing list SAFE@ietf.org https://www1.ietf.org/mailman/listinfo/safe From safe-bounces@ietf.org Fri Jul 13 15:37:52 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1I9Qxc-0005sk-BN; Fri, 13 Jul 2007 15:37:52 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1I9Qxb-0005se-1V for safe@ietf.org; Fri, 13 Jul 2007 15:37:51 -0400 Received: from mail5.primus.ca ([216.254.141.172] helo=mail-07.primus.ca) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I9QxW-0004dO-IS for safe@ietf.org; Fri, 13 Jul 2007 15:37:51 -0400 Received: from [216.13.42.68] (helo=[10.10.80.124]) by mail-07.primus.ca with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.63) (envelope-from ) id 1I9QxW-0002nt-2o; Fri, 13 Jul 2007 15:37:47 -0400 In-Reply-To: <14a801c7c41c$19ae2500$c3f0200a@amer.cisco.com> References: <14a801c7c41c$19ae2500$c3f0200a@amer.cisco.com> Mime-Version: 1.0 (Apple Message framework v752.2) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Philip Matthews Subject: Re: [SAFE] nat-control-stun-usage-03 Date: Fri, 13 Jul 2007 15:37:43 -0400 To: Dan Wing X-Mailer: Apple Mail (2.752.2) X-Authenticated: philip_matthews - ([10.10.80.124]) [216.13.42.68] X-Spam-Score: 0.1 (/) X-Scan-Signature: b22590c27682ace61775ee7b453b40d3 Cc: safe@ietf.org X-BeenThere: safe@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Self-Address Fixing Evolution List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: safe-bounces@ietf.org Two comments on this document. 1) Why must the TAG attribute be placed as the last attribute in the message? There is a lot of competition for the "last attribute" spot these days: MESSAGE-INTEGRITY, then FINGERPRINT, and now TAG. What if the message contains both a FINGERPRINT and a TAG attribute? 2) We should probably recommend a default maximum refresh-interval. Perhaps 2 hours. That is, if a client requests 47 days, it only gets 2 hours. 47 days is pretty extreme. Also, I didn't see the "MIP-capable" bit mentioned below. - Philip On 11-Jul-07, at 20:32 , Dan Wing wrote: > FYI, a new version was posted yesterday. > > Changes between -03 and 02: > > o Removed TLS from normal STUN operation (as few use it, and ICE > makes it unnecessary anyway) > > o BOOTNONCE attribute replaces STUN Control's previous use of TLS. > > o Added "MIP-capable" bit to TAG attribute > > o Removed "inside-out" discovery technique. > > Comments welcome. See you in Chicago. > > -d > > >> -----Original Message----- >> From: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org] >> Sent: Tuesday, July 10, 2007 11:15 AM >> To: i-d-announce@ietf.org >> Subject: I-D ACTION:draft-wing-behave-nat-control-stun-usage-03.txt >> >> A New Internet-Draft is available from the on-line Internet-Drafts >> directories. >> >> >> Title : Discovering, Querying, and >> Controlling Firewalls and NATs using STUN >> Author(s) : D. Wing, et al. >> Filename : >> draft-wing-behave-nat-control-stun-usage-03.txt >> Pages : 27 >> Date : 2007-7-10 >> >> Simple Traversal Underneath NAT (STUN) is a mechanism for traversing >> NATs. STUN requests are transmitted through a NAT to external >> STUN >> servers. While this works very well, its two primary drawbacks >> are >> the inability to modify the properties of a NAT binding >> and the need >> to query a public STUN server for every new NAT binding >> (e.g., every >> phone call). These drawbacks require frequent messages >> which present a load on servers (like SIP servers and STUN >> servers) and are bad for >> low speed access networks, such as cellular access. >> >> This document describes two mechanisms to discover NATs >> and firewalls >> and a mechanism to query and control them. With these mechanisms, >> binding discovery and keepalive traffic can be reduced to involve >> only the necessary NATs or firewalls. At the same time, backwards >> compatibility with NATs and firewalls that do not support this >> document is retained, which allows for incremental deployment of >> these mechanisms. >> >> A URL for this Internet-Draft is: >> http://www.ietf.org/internet-drafts/draft-wing-behave-nat-cont >> rol-stun-usage-03.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-wing-behave-nat-control-stun-usage-03.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-wing-behave-nat-control-stun-usage-03.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. >> > > _______________________________________________ > SAFE mailing list > SAFE@ietf.org > https://www1.ietf.org/mailman/listinfo/safe _______________________________________________ SAFE mailing list SAFE@ietf.org https://www1.ietf.org/mailman/listinfo/safe From safe-bounces@ietf.org Fri Jul 13 15:48:52 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1I9R8G-0007jk-3e; Fri, 13 Jul 2007 15:48:52 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1I9R8E-0007av-9X for safe@ietf.org; Fri, 13 Jul 2007 15:48:50 -0400 Received: from sj-iport-6.cisco.com ([171.71.176.117]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I9R8A-00051k-LJ for safe@ietf.org; Fri, 13 Jul 2007 15:48:50 -0400 Received: from sj-dkim-3.cisco.com ([171.71.179.195]) by sj-iport-6.cisco.com with ESMTP; 13 Jul 2007 12:48:46 -0700 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Ao8CAJtzl0arR7PD/2dsb2JhbAA X-IronPort-AV: i="4.16,537,1175497200"; d="scan'208"; a="181789502:sNHT69262488" Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238]) by sj-dkim-3.cisco.com (8.12.11/8.12.11) with ESMTP id l6DJmjPm028407; Fri, 13 Jul 2007 12:48:46 -0700 Received: from dwingwxp (dhcp-171-70-208-227.cisco.com [171.70.208.227]) by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id l6DJmjka004278; Fri, 13 Jul 2007 19:48:46 GMT From: "Dan Wing" To: "'Philip Matthews'" Subject: RE: [SAFE] nat-control-stun-usage-03 Date: Fri, 13 Jul 2007 12:48:45 -0700 Message-ID: <030601c7c586$d2faa680$e3d046ab@amer.cisco.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.3138 In-Reply-To: Thread-Index: AcfFhUrSplWyns+WQ9+NaxWp+iNrxAAALdtw DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=5834; t=1184356126; x=1185220126; c=relaxed/simple; s=sjdkim3002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=dwing@cisco.com; z=From:=20=22Dan=20Wing=22=20 |Subject:=20RE=3A=20[SAFE]=20nat-control-stun-usage-03 |Sender:=20; bh=A/4w+6nqNDkCc2v9bXDYdujkJpcgw/h00gdApBSh12M=; b=dIk98A6mN+WZzy5huqJe5vjfoH2qXaiVSc596nSlWIWjqnhNLVOdsurO9g8DiyDx5EC2aWfS IFUVDkIe5Lv9lBA3gmKnj+3dv/RFsRxOXLLb60sihL3xjlJlFc/K88PA; Authentication-Results: sj-dkim-3; header.From=dwing@cisco.com; dkim=pass (s ig from cisco.com/sjdkim3002 verified; ); X-Spam-Score: 0.0 (/) X-Scan-Signature: 848ed35f2a4fc0638fa89629cb640f48 Cc: safe@ietf.org X-BeenThere: safe@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Self-Address Fixing Evolution List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: safe-bounces@ietf.org > -----Original Message----- > From: Philip Matthews [mailto:philip_matthews@magma.ca] > Sent: Friday, July 13, 2007 12:38 PM > To: Dan Wing > Cc: safe@ietf.org > Subject: Re: [SAFE] nat-control-stun-usage-03 > > Two comments on this document. Thanks for your review. > 1) Why must the TAG attribute be placed as the last attribute in the > message? It can't be before the MESSAGE-INTEGRITY, because that attribute protects all attributes before it, and the firewall doesn't know the secret used to build the Message-Integrity. > There is a lot of competition for the "last attribute" spot > these days: MESSAGE-INTEGRITY, then FINGERPRINT, and now TAG. > What if > the message contains both a FINGERPRINT and a TAG attribute? It wouldn't matter which went last -- what matters to TAG is that it doesn't get added before MESSAGE-INTEGRITY. I have adjusted the text in my working copy to read: ... MUST append this attribute after the MESSAGE-INTEGRITY attribute ... > 2) We should probably recommend a default maximum refresh-interval. > Perhaps 2 hours. That is, if a client requests 47 days, it only gets > 2 hours. 47 days is pretty extreme. Sure. > Also, I didn't see the "MIP-capable" bit mentioned below. Section 6.4: The one-bit M field indicates if this firewall permits Mobility Header packets to flow through it ([RFC3775]). I added "MIP" to that reference in my working copy. -d > - Philip > > > On 11-Jul-07, at 20:32 , Dan Wing wrote: > > > FYI, a new version was posted yesterday. > > > > Changes between -03 and 02: > > > > o Removed TLS from normal STUN operation (as few use it, and ICE > > makes it unnecessary anyway) > > > > o BOOTNONCE attribute replaces STUN Control's previous > use of TLS. > > > > o Added "MIP-capable" bit to TAG attribute > > > > o Removed "inside-out" discovery technique. > > > > Comments welcome. See you in Chicago. > > > > -d > > > > > >> -----Original Message----- > >> From: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org] > >> Sent: Tuesday, July 10, 2007 11:15 AM > >> To: i-d-announce@ietf.org > >> Subject: I-D ACTION:draft-wing-behave-nat-control-stun-usage-03.txt > >> > >> A New Internet-Draft is available from the on-line Internet-Drafts > >> directories. > >> > >> > >> Title : Discovering, Querying, and > >> Controlling Firewalls and NATs using STUN > >> Author(s) : D. Wing, et al. > >> Filename : > >> draft-wing-behave-nat-control-stun-usage-03.txt > >> Pages : 27 > >> Date : 2007-7-10 > >> > >> Simple Traversal Underneath NAT (STUN) is a mechanism for > traversing > >> NATs. STUN requests are transmitted through a NAT to external > >> STUN > >> servers. While this works very well, its two primary > drawbacks > >> are > >> the inability to modify the properties of a NAT binding > >> and the need > >> to query a public STUN server for every new NAT binding > >> (e.g., every > >> phone call). These drawbacks require frequent messages > >> which present a load on servers (like SIP servers and STUN > >> servers) and are bad for > >> low speed access networks, such as cellular access. > >> > >> This document describes two mechanisms to discover NATs > >> and firewalls > >> and a mechanism to query and control them. With these > mechanisms, > >> binding discovery and keepalive traffic can be reduced > to involve > >> only the necessary NATs or firewalls. At the same > time, backwards > >> compatibility with NATs and firewalls that do not support this > >> document is retained, which allows for incremental deployment of > >> these mechanisms. > >> > >> A URL for this Internet-Draft is: > >> http://www.ietf.org/internet-drafts/draft-wing-behave-nat-cont > >> rol-stun-usage-03.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-wing-behave-nat-control-stun-usage-03.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-wing-behave-nat-control-stun-usage-03.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. > >> > > > > _______________________________________________ > > SAFE mailing list > > SAFE@ietf.org > > https://www1.ietf.org/mailman/listinfo/safe _______________________________________________ SAFE mailing list SAFE@ietf.org https://www1.ietf.org/mailman/listinfo/safe From safe-bounces@ietf.org Fri Jul 13 16:00:55 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1I9RJv-0004B3-Fa; Fri, 13 Jul 2007 16:00:55 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1I9RJv-0004Aj-05 for safe@ietf.org; Fri, 13 Jul 2007 16:00:55 -0400 Received: from sj-iport-2-in.cisco.com ([171.71.176.71] helo=sj-iport-2.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I9RJq-0005M1-Lz for safe@ietf.org; Fri, 13 Jul 2007 16:00:54 -0400 Received: from sj-dkim-3.cisco.com ([171.71.179.195]) by sj-iport-2.cisco.com with ESMTP; 13 Jul 2007 13:00:50 -0700 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Ao8CAFN3l0arR7PD/2dsb2JhbAA X-IronPort-AV: i="4.16,537,1175497200"; d="scan'208"; a="385662814:sNHT37731996" Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254]) by sj-dkim-3.cisco.com (8.12.11/8.12.11) with ESMTP id l6DK0nRJ012572 for ; Fri, 13 Jul 2007 13:00:49 -0700 Received: from dwingwxp (dhcp-171-70-208-227.cisco.com [171.70.208.227]) by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id l6DK0nmo024331 for ; Fri, 13 Jul 2007 20:00:49 GMT From: "Dan Wing" To: Subject: RE: [SAFE] RE: SAFE bar BoF Date: Fri, 13 Jul 2007 13:00:49 -0700 Message-ID: <031301c7c588$827b95f0$e3d046ab@amer.cisco.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.3138 In-Reply-To: <060701c7b953$a6a95d90$dd93150a@amer.cisco.com> Thread-Index: AceuaaXPQ4y/HNUJRsam/N046TRQXwARsNtAAkCBrtAAaEd4QAMNAu/g DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=706; t=1184356849; x=1185220849; c=relaxed/simple; s=sjdkim3002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=dwing@cisco.com; z=From:=20=22Dan=20Wing=22=20 |Subject:=20RE=3A=20[SAFE]=20RE=3A=20SAFE=20bar=20BoF |Sender:=20; bh=+4D22f4CBj24tFEVOiXYC5GBuh2ChIKGFagdZI5FZWU=; b=lKhKTU9vrOaJUROvSLv/MLmveqFC9shZd8o+CaHXDAGjajTdiC0v8FPJ42fr92e9JHl/DOwd xpCBlrWcHPSxCvT4R+9BqnQouqJHxCbF/MmU0BMyC+wBAMJgVfhmPuKK; Authentication-Results: sj-dkim-3; header.From=dwing@cisco.com; dkim=pass (s ig from cisco.com/sjdkim3002 verified; ); X-Spam-Score: 0.0 (/) X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581 X-BeenThere: safe@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Self-Address Fixing Evolution List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: safe-bounces@ietf.org Safe people, There is a p2p-sip bar BoF being put together after dinner on Monday. To avoid that conflict, I propose we meet at 11pm on Monday, or meet over lunch. My lunches are currently wide open. Agenda for Tuesday morning is: Grand Ballroom APP httpbis HyperText Transport Protocol Bis BOF State Ballroom INT netlmm Network-based Localized Mobility Management WG Crystal INT 6lowpan IPv6 over Low power WPAN WG Salon 3 IRTF dtnrg Delay-Tolerant Networking Research Group Monroe OPS dnsop Domain Name System Operations WG Red Lacquer RAI sip Session Initiation Protocol WG Adams RTG ccamp Common Control and Measurement Plane WG Salon 2 TSV ippm IP Performance Metrics WG -d _______________________________________________ SAFE mailing list SAFE@ietf.org https://www1.ietf.org/mailman/listinfo/safe From safe-bounces@ietf.org Mon Jul 16 04:26: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 1IALuS-0006ox-6b; Mon, 16 Jul 2007 04:26:24 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IALuR-0006lM-BQ for safe@ietf.org; Mon, 16 Jul 2007 04:26:23 -0400 Received: from mailgw4.ericsson.se ([193.180.251.62]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IALuM-0002Xc-GK for safe@ietf.org; Mon, 16 Jul 2007 04:26:23 -0400 Received: from mailgw4.ericsson.se (unknown [127.0.0.1]) by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id D570A218E9; Mon, 16 Jul 2007 10:26:17 +0200 (CEST) X-AuditID: c1b4fb3e-ae831bb0000007e1-3a-469b2ba9809b Received: from esealmw129.eemea.ericsson.se (unknown [153.88.254.124]) by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id B0EBA214CA; Mon, 16 Jul 2007 10:26:17 +0200 (CEST) Received: from esealmw129.eemea.ericsson.se ([153.88.254.177]) by esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Mon, 16 Jul 2007 10:26:16 +0200 Received: from [147.214.30.247] ([147.214.30.247]) by esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Mon, 16 Jul 2007 10:26:15 +0200 Message-ID: <469B2BA8.7000301@ericsson.com> Date: Mon, 16 Jul 2007 10:26:16 +0200 From: Magnus Westerlund User-Agent: Thunderbird 2.0.0.4 (Windows/20070604) MIME-Version: 1.0 To: Dan Wing Subject: Re: [SAFE] RE: SAFE bar BoF References: <031301c7c588$827b95f0$e3d046ab@amer.cisco.com> In-Reply-To: <031301c7c588$827b95f0$e3d046ab@amer.cisco.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 16 Jul 2007 08:26:15.0933 (UTC) FILETIME=[FA1E8AD0:01C7C782] X-Brightmail-Tracker: AAAAAA== X-Spam-Score: 0.0 (/) X-Scan-Signature: 3e15cc4fdc61d7bce84032741d11c8e5 Cc: safe@ietf.org X-BeenThere: safe@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Self-Address Fixing Evolution List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: safe-bounces@ietf.org Hi, Monday at 11 seems to be a bad time, as NSIS WG has meeting at that time. NSIS is one of the WG that has "competing" solution. Lunch time does not work for me personaly, but that is the full AD calaender. Thus I would propose some other time. Tuesday at 10 or 10.30 actually works better for me. But we need to be finished by lunch time when there is the ICE tutorial. Cheers Magnus Dan Wing skrev: > Safe people, > > There is a p2p-sip bar BoF being put together after dinner on Monday. To > avoid that conflict, I propose we meet at 11pm on Monday, or meet over > lunch. My lunches are currently wide open. > > > Agenda for Tuesday morning is: > > Grand Ballroom APP httpbis HyperText Transport Protocol Bis BOF > State Ballroom INT netlmm Network-based Localized Mobility Management > WG > Crystal INT 6lowpan IPv6 over Low power WPAN WG > Salon 3 IRTF dtnrg Delay-Tolerant Networking Research Group > Monroe OPS dnsop Domain Name System Operations WG > Red Lacquer RAI sip Session Initiation Protocol WG > Adams RTG ccamp Common Control and Measurement Plane WG > Salon 2 TSV ippm IP Performance Metrics WG > > -d > > > _______________________________________________ > SAFE mailing list > SAFE@ietf.org > https://www1.ietf.org/mailman/listinfo/safe > -- Magnus Westerlund IETF Transport Area Director & TSVWG Chair ---------------------------------------------------------------------- Multimedia Technologies, Ericsson Research EAB/TVM/M ---------------------------------------------------------------------- Ericsson AB | Phone +46 8 4048287 Torshamsgatan 23 | Fax +46 8 7575550 S-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com ---------------------------------------------------------------------- _______________________________________________ SAFE mailing list SAFE@ietf.org https://www1.ietf.org/mailman/listinfo/safe From safe-bounces@ietf.org Mon Jul 16 04:34:11 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IAM1z-0006At-Js; Mon, 16 Jul 2007 04:34:11 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IAM1x-0006Al-W4 for safe@ietf.org; Mon, 16 Jul 2007 04:34:09 -0400 Received: from mailgw4.ericsson.se ([193.180.251.62]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IAM1t-0002h1-Ga for safe@ietf.org; Mon, 16 Jul 2007 04:34:09 -0400 Received: from mailgw4.ericsson.se (unknown [127.0.0.1]) by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id 06EE621DDE for ; Mon, 16 Jul 2007 10:33:30 +0200 (CEST) X-AuditID: c1b4fb3e-b2038bb0000007e1-61-469b2d5953c5 Received: from esealmw127.eemea.ericsson.se (unknown [153.88.254.122]) by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id C089321DE2 for ; Mon, 16 Jul 2007 10:33:29 +0200 (CEST) Received: from esealmw129.eemea.ericsson.se ([153.88.254.177]) by esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Mon, 16 Jul 2007 10:33:28 +0200 Received: from [147.214.30.247] ([147.214.30.247]) by esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Mon, 16 Jul 2007 10:33:28 +0200 Message-ID: <469B2D58.3000604@ericsson.com> Date: Mon, 16 Jul 2007 10:33:28 +0200 From: Magnus Westerlund User-Agent: Thunderbird 2.0.0.4 (Windows/20070604) MIME-Version: 1.0 To: safe@ietf.org Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 16 Jul 2007 08:33:28.0690 (UTC) FILETIME=[FC100520:01C7C783] X-Brightmail-Tracker: AAAAAA== X-Spam-Score: 0.0 (/) X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3 Subject: [SAFE] Clarification on status for Vancouver X-BeenThere: safe@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Self-Address Fixing Evolution List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: safe-bounces@ietf.org Hi, There has been some confusion on the discussion on what status SAFE has in regards to BOF in Vancouver. Therefore let me clarify: SAFE currenly has no official status. Which means I need to receive a request before the deadline. Also SAFE would need to fulfill the BOF criterias. I think most of them are fulfilled. As long as there are some continuing discussion and development of the related draft(s) then I think it is very likely that I would approve a request. And I do hope that I will be able to approve the BOF for Vancouver. But there is no automatic accept. Just for your knowledge. Cheers Magnus Westerlund IETF Transport Area Director & TSVWG Chair ---------------------------------------------------------------------- Multimedia Technologies, Ericsson Research EAB/TVM/M ---------------------------------------------------------------------- Ericsson AB | Phone +46 8 4048287 Torshamsgatan 23 | Fax +46 8 7575550 S-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com ---------------------------------------------------------------------- _______________________________________________ SAFE mailing list SAFE@ietf.org https://www1.ietf.org/mailman/listinfo/safe From safe-bounces@ietf.org Mon Jul 16 05:06:23 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IAMX9-0000DN-GC; Mon, 16 Jul 2007 05:06:23 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IAMX8-0000Ap-2a for safe@ietf.org; Mon, 16 Jul 2007 05:06:22 -0400 Received: from mail.gmx.net ([213.165.64.20]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1IAMX3-0003Kq-JL for safe@ietf.org; Mon, 16 Jul 2007 05:06:22 -0400 Received: (qmail invoked by alias); 16 Jul 2007 09:06:16 -0000 Received: from socks1.netz.sbs.de (EHLO [192.35.17.26]) [192.35.17.26] by mail.gmx.net (mp009) with SMTP; 16 Jul 2007 11:06:16 +0200 X-Authenticated: #29516787 X-Provags-ID: V01U2FsdGVkX1+a7ulmh4aacpvWbiAW8zPaLt4biG6/6zLqQZ8lUu sVVzmoOhKoQ/cT Message-ID: <469B3506.5090600@gmx.net> Date: Mon, 16 Jul 2007 11:06:14 +0200 From: Hannes Tschofenig User-Agent: Thunderbird 2.0.0.4 (Windows/20070604) MIME-Version: 1.0 To: Magnus Westerlund Subject: Re: [SAFE] RE: SAFE bar BoF References: <031301c7c588$827b95f0$e3d046ab@amer.cisco.com> <469B2BA8.7000301@ericsson.com> In-Reply-To: <469B2BA8.7000301@ericsson.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 X-Spam-Score: 0.0 (/) X-Scan-Signature: 538aad3a3c4f01d8b6a6477ca4248793 Cc: safe@ietf.org X-BeenThere: safe@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Self-Address Fixing Evolution List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: safe-bounces@ietf.org There is also another Bar-BOF on authority-to-individuals emergency services on Monday during the lunch break. Ciao Hannes Magnus Westerlund wrote: > Hi, > > Monday at 11 seems to be a bad time, as NSIS WG has meeting at that > time. NSIS is one of the WG that has "competing" solution. Lunch time > does not work for me personaly, but that is the full AD calaender. > Thus I would propose some other time. Tuesday at 10 or 10.30 actually > works better for me. But we need to be finished by lunch time when > there is the ICE tutorial. > > Cheers > > Magnus > > Dan Wing skrev: >> Safe people, >> >> There is a p2p-sip bar BoF being put together after dinner on >> Monday. To >> avoid that conflict, I propose we meet at 11pm on Monday, or meet over >> lunch. My lunches are currently wide open. >> >> >> Agenda for Tuesday morning is: >> >> Grand Ballroom APP httpbis HyperText Transport Protocol Bis BOF >> State Ballroom INT netlmm Network-based Localized Mobility >> Management >> WG >> Crystal INT 6lowpan IPv6 over Low power WPAN WG >> Salon 3 IRTF dtnrg Delay-Tolerant Networking Research Group >> Monroe OPS dnsop Domain Name System Operations WG >> Red Lacquer RAI sip Session Initiation Protocol WG >> Adams RTG ccamp Common Control and Measurement Plane WG >> Salon 2 TSV ippm IP Performance Metrics WG >> >> -d >> >> >> _______________________________________________ >> SAFE mailing list >> SAFE@ietf.org >> https://www1.ietf.org/mailman/listinfo/safe >> > > _______________________________________________ SAFE mailing list SAFE@ietf.org https://www1.ietf.org/mailman/listinfo/safe From safe-bounces@ietf.org Mon Jul 16 14:14:16 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IAV5M-00083k-3b; Mon, 16 Jul 2007 14:14:16 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IAV5L-00083f-23 for safe@ietf.org; Mon, 16 Jul 2007 14:14:15 -0400 Received: from sj-iport-6.cisco.com ([171.71.176.117]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IAV5G-00069L-L8 for safe@ietf.org; Mon, 16 Jul 2007 14:14:15 -0400 Received: from sj-dkim-3.cisco.com ([171.71.179.195]) by sj-iport-6.cisco.com with ESMTP; 16 Jul 2007 11:09:52 -0700 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Ao8CAAtSm0arR7PD/2dsb2JhbAA X-IronPort-AV: i="4.16,542,1175497200"; d="scan'208"; a="182961957:sNHT10972748457" Received: from sj-core-3.cisco.com (sj-core-3.cisco.com [171.68.223.137]) by sj-dkim-3.cisco.com (8.12.11/8.12.11) with ESMTP id l6GI9q88014244; Mon, 16 Jul 2007 11:09:52 -0700 Received: from dwingwxp ([10.32.240.196]) by sj-core-3.cisco.com (8.12.10/8.12.6) with ESMTP id l6GI9p4w029111; Mon, 16 Jul 2007 18:09:52 GMT From: "Dan Wing" To: "'Magnus Westerlund'" Subject: RE: [SAFE] RE: SAFE bar BoF Date: Mon, 16 Jul 2007 11:09:51 -0700 Message-ID: <029001c7c7d4$816320e0$c4f0200a@amer.cisco.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 In-Reply-To: <469B2BA8.7000301@ericsson.com> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3138 Thread-Index: AcfHgwC3Ayf8vqpXQhSL4bBxsdrmvwAUQ1EQ DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=2539; t=1184609392; x=1185473392; c=relaxed/simple; s=sjdkim3002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=dwing@cisco.com; z=From:=20=22Dan=20Wing=22=20 |Subject:=20RE=3A=20[SAFE]=20RE=3A=20SAFE=20bar=20BoF |Sender:=20; bh=MHUTl13YRu74P7TdsDQsNulBjMW6p0rEdRlQuzODk2E=; b=hmw7nUUhCqOPT/gDNjBzqPg9GmPtciKmz+kmA5gjNl3Nb2jHNpRsr+OBIIoRi+zRwQiUWNGt 9DlQv4Kx3alUcKE+nAMHa4W6gBbhxQMiyGmAacxt1G394Z0kKOgeUAfT; Authentication-Results: sj-dkim-3; header.From=dwing@cisco.com; dkim=pass (s ig from cisco.com/sjdkim3002 verified; ); X-Spam-Score: 0.0 (/) X-Scan-Signature: d185fa790257f526fedfd5d01ed9c976 Cc: safe@ietf.org X-BeenThere: safe@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Self-Address Fixing Evolution List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: safe-bounces@ietf.org I am last on the agenda for SIP on Tuesday at 11:15, http://www3.ietf.org/proceedings/07jul/agenda/sip.html but it's possible I might be bumped off if there isn't sufficient time. Only 4 people have mentioned an interest to meet in Chicago. I think it may be best to just meet in the hallways during the week, or pair up interested folks. -d > -----Original Message----- > From: Magnus Westerlund [mailto:magnus.westerlund@ericsson.com] > Sent: Monday, July 16, 2007 1:26 AM > To: Dan Wing > Cc: safe@ietf.org > Subject: Re: [SAFE] RE: SAFE bar BoF > > Hi, > > Monday at 11 seems to be a bad time, as NSIS WG has meeting at that > time. NSIS is one of the WG that has "competing" solution. Lunch time > does not work for me personaly, but that is the full AD > calaender. Thus > I would propose some other time. Tuesday at 10 or 10.30 > actually works > better for me. But we need to be finished by lunch time when there is > the ICE tutorial. > > Cheers > > Magnus > > Dan Wing skrev: > > Safe people, > > > > There is a p2p-sip bar BoF being put together after dinner > on Monday. To > > avoid that conflict, I propose we meet at 11pm on Monday, > or meet over > > lunch. My lunches are currently wide open. > > > > > > Agenda for Tuesday morning is: > > > > Grand Ballroom APP httpbis HyperText Transport > Protocol Bis BOF > > State Ballroom INT netlmm Network-based Localized > Mobility Management > > WG > > Crystal INT 6lowpan IPv6 over Low power WPAN WG > > Salon 3 IRTF dtnrg Delay-Tolerant Networking Research Group > > Monroe OPS dnsop Domain Name System Operations WG > > Red Lacquer RAI sip Session Initiation Protocol WG > > Adams RTG ccamp Common Control and Measurement Plane WG > > Salon 2 TSV ippm IP Performance Metrics WG > > > > -d > > > > > > _______________________________________________ > > SAFE mailing list > > SAFE@ietf.org > > https://www1.ietf.org/mailman/listinfo/safe > > > > > -- > > Magnus Westerlund > > IETF Transport Area Director & TSVWG Chair > ---------------------------------------------------------------------- > Multimedia Technologies, Ericsson Research EAB/TVM/M > ---------------------------------------------------------------------- > Ericsson AB | Phone +46 8 4048287 > Torshamsgatan 23 | Fax +46 8 7575550 > S-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com > -------------------------------------------------------------- > -------- _______________________________________________ SAFE mailing list SAFE@ietf.org https://www1.ietf.org/mailman/listinfo/safe From safe-bounces@ietf.org Tue Jul 17 17:15:45 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IAuOX-00079o-Kn; Tue, 17 Jul 2007 17:15:45 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IAuOW-00079G-Sw for safe@ietf.org; Tue, 17 Jul 2007 17:15:44 -0400 Received: from mail.gmx.net ([213.165.64.20]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1IAuOV-0007l3-Gm for safe@ietf.org; Tue, 17 Jul 2007 17:15:44 -0400 Received: (qmail invoked by alias); 17 Jul 2007 21:15:42 -0000 Received: from p54984CE1.dip.t-dialin.net (EHLO [192.168.1.4]) [84.152.76.225] by mail.gmx.net (mp047) with SMTP; 17 Jul 2007 23:15:42 +0200 X-Authenticated: #29516787 X-Provags-ID: V01U2FsdGVkX18GX2839a0GLy0+N1lYQD5GNOVwb8p1NsUWL0MKqB Sky5eFdwFifYtc Message-ID: <469D3176.3090007@gmx.net> Date: Tue, 17 Jul 2007 23:15:34 +0200 From: Hannes Tschofenig User-Agent: Thunderbird 2.0.0.4 (Windows/20070604) MIME-Version: 1.0 To: safe@ietf.org References: <029001c7c7d4$816320e0$c4f0200a@amer.cisco.com> In-Reply-To: <029001c7c7d4$816320e0$c4f0200a@amer.cisco.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 X-Spam-Score: 0.0 (/) X-Scan-Signature: 1ac7cc0a4cd376402b85bc1961a86ac2 Cc: Subject: [SAFE] Date for the SAFE Bar-BoF X-BeenThere: safe@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Self-Address Fixing Evolution List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: safe-bounces@ietf.org Hi all, I have spoken to Dan and we think that >>>SUNDAY, July 22, 2007, from 8pm to 9pm<<< is a good time to have a meeting to discuss the topic of STUN Control. You can find more information on this webpage: http://www.tschofenig.com/twiki/bin/view/MiddleboxTraversal/ Please let us know if you have time to participate. Ciao Hannes _______________________________________________ SAFE mailing list SAFE@ietf.org https://www1.ietf.org/mailman/listinfo/safe From safe-bounces@ietf.org Wed Jul 18 04:13:51 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IB4fP-0005iI-I2; Wed, 18 Jul 2007 04:13:51 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IB4fO-0005fy-8Y for safe@ietf.org; Wed, 18 Jul 2007 04:13:50 -0400 Received: from mailgw4.ericsson.se ([193.180.251.62]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IB4fN-0008N3-Rx for safe@ietf.org; Wed, 18 Jul 2007 04:13:50 -0400 Received: from mailgw4.ericsson.se (unknown [127.0.0.1]) by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id 40AE921614; Wed, 18 Jul 2007 10:13:49 +0200 (CEST) X-AuditID: c1b4fb3e-b1837bb0000007e1-f4-469dcbbd61b6 Received: from esealmw126.eemea.ericsson.se (unknown [153.88.254.123]) by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id 1405421485; Wed, 18 Jul 2007 10:13:49 +0200 (CEST) Received: from esealmw128.eemea.ericsson.se ([153.88.254.172]) by esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Wed, 18 Jul 2007 10:13:48 +0200 Received: from [147.214.30.247] ([147.214.30.247]) by esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Wed, 18 Jul 2007 10:13:48 +0200 Message-ID: <469DCBBC.5080702@ericsson.com> Date: Wed, 18 Jul 2007 10:13:48 +0200 From: Magnus Westerlund User-Agent: Thunderbird 2.0.0.4 (Windows/20070604) MIME-Version: 1.0 To: Hannes Tschofenig Subject: Re: [SAFE] Date for the SAFE Bar-BoF References: <029001c7c7d4$816320e0$c4f0200a@amer.cisco.com> <469D3176.3090007@gmx.net> In-Reply-To: <469D3176.3090007@gmx.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 18 Jul 2007 08:13:48.0368 (UTC) FILETIME=[915CAD00:01C7C913] X-Brightmail-Tracker: AAAAAA== X-Spam-Score: 0.0 (/) X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab Cc: safe@ietf.org X-BeenThere: safe@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Self-Address Fixing Evolution List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: safe-bounces@ietf.org Hannes Tschofenig skrev: > Hi all, > > I have spoken to Dan and we think that >>>SUNDAY, July 22, 2007, from > 8pm to 9pm<<< is a good time to have a meeting to discuss the topic of > STUN Control. > That should work for me. cheers Magnus Westerlund IETF Transport Area Director & TSVWG Chair ---------------------------------------------------------------------- Multimedia Technologies, Ericsson Research EAB/TVM/M ---------------------------------------------------------------------- Ericsson AB | Phone +46 8 4048287 Torshamsgatan 23 | Fax +46 8 7575550 S-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com ---------------------------------------------------------------------- _______________________________________________ SAFE mailing list SAFE@ietf.org https://www1.ietf.org/mailman/listinfo/safe From safe-bounces@ietf.org Mon Jul 23 15:01:12 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1ID39c-0007rJ-6e; Mon, 23 Jul 2007 15:01:12 -0400 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1ID39b-0007rE-JK for safe@ietf.org; Mon, 23 Jul 2007 15:01:11 -0400 Received: from sj-iport-1-in.cisco.com ([171.71.176.70] helo=sj-iport-1.cisco.com) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1ID39b-0006oy-8r for safe@ietf.org; Mon, 23 Jul 2007 15:01:11 -0400 Received: from sj-dkim-4.cisco.com ([171.71.179.196]) by sj-iport-1.cisco.com with ESMTP; 23 Jul 2007 12:01:10 -0700 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Ao8CAFKXpEarR7PE/2dsb2JhbAA X-IronPort-AV: i="4.16,571,1175497200"; d="scan'208"; a="9952330:sNHT13284234" Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238]) by sj-dkim-4.cisco.com (8.12.11/8.12.11) with ESMTP id l6NJ1A7X006750 for ; Mon, 23 Jul 2007 12:01:10 -0700 Received: from dwingwxp (sjc-vpn7-446.cisco.com [10.21.145.190]) by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id l6NJ19Sb017983 for ; Mon, 23 Jul 2007 19:01:09 GMT From: "Dan Wing" To: Date: Mon, 23 Jul 2007 14:01:09 -0500 Message-ID: <001501c7cd5b$d4c1b0d0$be91150a@amer.cisco.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 Thread-Index: AcfNW9RKpffQRt9GTNKYGM3RUezrnw== X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3138 DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=544; t=1185217270; x=1186081270; c=relaxed/simple; s=sjdkim4002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=dwing@cisco.com; z=From:=20=22Dan=20Wing=22=20 |Subject:=20Bar=20BoF |Sender:=20; bh=Cm6NyXHCbqRYS9QUrXb59rIKED5idk2S9IjGczimFqM=; b=AK+G7VBvRyGh78MOVVh7i13upSU30Y9KKghRWnT8P0aPQzki+9dKIM4iK0ifGqUxYXuEjjSg pRKxL75tr8ZjcaKapUEyBAwRG7/XHCvQWDJsatsWlClYHe7kNFM01W/h; Authentication-Results: sj-dkim-4; header.From=dwing@cisco.com; dkim=pass (s ig from cisco.com/sjdkim4002 verified; ); X-Spam-Score: 0.0 (/) X-Scan-Signature: de4f315c9369b71d7dd5909b42224370 Subject: [SAFE] Bar BoF X-BeenThere: safe@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Self-Address Fixing Evolution List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: safe-bounces@ietf.org Thanks to everyone that attended. I was surprised at the large turnout (24 people) and the level of interest -- this gives me the encouragement to continue pushing this work forward. Major action items I took from the bar BoF were: 1. "why will SAFE succeed where other IETF NAT protocols not succeeded" 2. charter text for Vancouver 3. Dan needs to describe the security attack that is avoided with BOOTNONCE If there are more, please pile on. And I'm sorry about the lack of a bar at the Bar BoF! -d _______________________________________________ SAFE mailing list SAFE@ietf.org https://www1.ietf.org/mailman/listinfo/safe From safe-bounces@ietf.org Mon Jul 23 15:06:35 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1ID3Ep-0000ma-41; Mon, 23 Jul 2007 15:06:35 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1ID3Eo-0000mV-1l for safe@ietf.org; Mon, 23 Jul 2007 15:06:34 -0400 Received: from sj-iport-3-in.cisco.com ([171.71.176.72] helo=sj-iport-3.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ID3En-00087R-NT for safe@ietf.org; Mon, 23 Jul 2007 15:06:34 -0400 Received: from sj-dkim-1.cisco.com ([171.71.179.21]) by sj-iport-3.cisco.com with ESMTP; 23 Jul 2007 12:06:33 -0700 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Ao8CAPaYpEarR7MV/2dsb2JhbAA X-IronPort-AV: i="4.16,571,1175497200"; d="scan'208"; a="506098443:sNHT30497652" Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237]) by sj-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id l6NJ6VCc024695 for ; Mon, 23 Jul 2007 12:06:31 -0700 Received: from dwingwxp (sjc-vpn7-446.cisco.com [10.21.145.190]) by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l6NJ6VA0029181 for ; Mon, 23 Jul 2007 19:06:31 GMT From: "Dan Wing" To: Subject: RE: [SAFE] Bar BoF Date: Mon, 23 Jul 2007 14:06:30 -0500 Message-ID: <002801c7cd5c$9446ed30$be91150a@amer.cisco.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 Thread-Index: AcfNW9RKpffQRt9GTNKYGM3RUezrnwAAJW8Q X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3138 In-Reply-To: <001501c7cd5b$d4c1b0d0$be91150a@amer.cisco.com> DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=341; t=1185217591; x=1186081591; c=relaxed/simple; s=sjdkim1004; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=dwing@cisco.com; z=From:=20=22Dan=20Wing=22=20 |Subject:=20RE=3A=20[SAFE]=20Bar=20BoF |Sender:=20; bh=MhozveAM7z7AjWEGAtmEqEmCkges8YuTNCzW7Gkp6mQ=; b=CyhvLI1k9K7z+4jOhjnBwALeRA60Oz68qd55L5GynfvSXY2V7pgFA3A4yIq6YsUI7lWgYve1 kPNU0VKnjpjWDV+PvEMNUVi7KYLTxQt6jWaQ7/mo/X7ifpuN09HSzn0gzVNhokhCAYvq5XsAZh +rt1rJDBU1VNfkI0SBMOJwH4M=; Authentication-Results: sj-dkim-1; header.From=dwing@cisco.com; dkim=pass (s ig from cisco.com/sjdkim1004 verified; ); X-Spam-Score: -4.0 (----) X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad X-BeenThere: safe@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Self-Address Fixing Evolution List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: safe-bounces@ietf.org > 1. "why will SAFE succeed where other IETF NAT > protocols not succeeded" > 2. charter text for Vancouver > 3. Dan needs to describe the security attack > that is avoided with BOOTNONCE > > If there are more, please pile on. I was reminded of another: 4. Implementation statements from NAT vendors. -d _______________________________________________ SAFE mailing list SAFE@ietf.org https://www1.ietf.org/mailman/listinfo/safe