RE: [BEHAVE] Re: removing application milestone
"Henry Sinnreich" <hsinnrei@adobe.com> Mon, 16 July 2007 17:16 UTC
Return-path: <behave-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IAUBT-0001OO-Ht; Mon, 16 Jul 2007 13:16:31 -0400
Received: from behave by megatron.ietf.org with local (Exim 4.43) id 1IAF4g-00052q-Qo for behave-confirm+ok@megatron.ietf.org; Sun, 15 Jul 2007 21:08:30 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IAF4g-00052i-Fs for behave@ietf.org; Sun, 15 Jul 2007 21:08:30 -0400
Received: from exprod6og55.obsmtp.com ([64.18.1.191]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IAF4R-0006i8-3e for behave@ietf.org; Sun, 15 Jul 2007 21:08:30 -0400
Received: from source ([192.150.11.134]) by exprod6ob55.postini.com ([64.18.5.12]) with SMTP; Sun, 15 Jul 2007 18:07:48 PDT
Received: from inner-relay-1.corp.adobe.com ([153.32.1.51]) by outbound-smtp-1.corp.adobe.com (8.12.10/8.12.10) with ESMTP id l6G16Tot014528; Sun, 15 Jul 2007 18:06:29 -0700 (PDT)
Received: from fe2.corp.adobe.com (fe2.corp.adobe.com [10.8.192.72]) by inner-relay-1.corp.adobe.com (8.12.10/8.12.10) with ESMTP id l6G15nI9016566; Sun, 15 Jul 2007 18:05:49 -0700 (PDT)
Received: from namail5.corp.adobe.com ([10.8.192.88]) by fe2.corp.adobe.com with Microsoft SMTPSVC(6.0.3790.1830); Sun, 15 Jul 2007 18:07:41 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [BEHAVE] Re: removing application milestone
Date: Sun, 15 Jul 2007 18:07:40 -0700
Message-ID: <24CCCC428EFEA2469BF046DB3C7A8D22AA9D5B@namail5.corp.adobe.com>
In-Reply-To: <887981.79844.qm@web33309.mail.mud.yahoo.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [BEHAVE] Re: removing application milestone
Thread-Index: AcfHPY8KxiowVIjfSd+OivP/BbhPqQAAvR4Q
References: <887981.79844.qm@web33309.mail.mud.yahoo.com>
From: Henry Sinnreich <hsinnrei@adobe.com>
To: behave@ietf.org
X-OriginalArrivalTime: 16 Jul 2007 01:07:41.0438 (UTC) FILETIME=[B57541E0:01C7C745]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9ed51c9d1356100bce94f1ae4ec616a9
X-Mailman-Approved-At: Mon, 16 Jul 2007 13:16:29 -0400
Cc: henrys@adobe.com, baford@mit.edu, Dan Wing <dwing@cisco.com>, dank@kegel.com
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/behave>, <mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/behave>
List-Post: <mailto:behave@ietf.org>
List-Help: <mailto:behave-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/behave>, <mailto:behave-request@ietf.org?subject=subscribe>
Errors-To: behave-bounces@ietf.org
Dan Wing wrote: > > At the BEHAVE meeting in Prague there was strong consensus to remove > the milestone: "Submit informational that discusses current NAT > traversal techniques used by applications" from our charter, and to not > adopt draft-ford-behave-app to meet that milestone. I must strongly disagree with this proposal for several reasons, besides the fact that majority consensus in a meeting has nothing to do with getting it right. The I-D ftp://ftp.rfc-editor.org/in-notes/internet-drafts/draft-ietf-behave-p2p- state-03.txt has the outstanding value compared to most other proposals, such as the over abundant literature for ICE: * A study based on real networks and the Internet, * The authors have created a tool for testing NAT traversal, * Many contributors have used the tool and reported results, * The results are published, see http://pdos.csail.mit.edu/papers/p2pnat.pdf This outstanding work is not only a model for the BEHAVE WG but also for most other IETF WGs, where concept I-D predominate unfortunately over proposals backed up by published research, running code and published performance. Given that ICE has now gained the status of a creed and maybe I have missed it: Are there any published results on the effectiveness of ICE, such as % of success in various NAT scenarios and call setup delay when used with SIP? I have seen one private report and it does not look that great. At any rate, <draft-ietf-behave-p2p-state-03.txt> must be the top BEHAVE WG item. Continuing this work should include identifying and measuring NAT types used by ISPs and also the multi-homed ISP network scenario. Updated test results such as in http://pdos.csail.mit.edu/papers/p2pnat.pdf would also be welcome. Thanks, Henry _______________________________________________ Behave mailing list Behave@ietf.org https://www1.ietf.org/mailman/listinfo/behave
- [BEHAVE] removing application milestone Dan Wing
- [BEHAVE] Re: removing application milestone Pyda Srisuresh
- RE: [BEHAVE] Re: removing application milestone Henry Sinnreich
- RE: [BEHAVE] Re: removing application milestone David Barrett
- RE: [BEHAVE] Re: removing application milestone Dan Wing
- RE: [BEHAVE] Re: removing application milestone David Barrett
- RE: [BEHAVE] Re: removing application milestone Dan Wing
- Re: [BEHAVE] Re: removing application milestone Rémi Denis-Courmont
- RE: [BEHAVE] Re: removing application milestone David Barrett
- RE: [BEHAVE] Re: removing application milestone David Barrett
- Re: [BEHAVE] Re: removing application milestone Rémi Denis-Courmont
- RE: [BEHAVE] Re: removing application milestone David Barrett
- Re: [BEHAVE] Re: removing application milestone Rémi Denis-Courmont
- RE: [BEHAVE] Re: removing application milestone David Barrett