From daemon@optimus.ietf.org Fri Jun 7 13:10:34 2002 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA04309 for ; Fri, 7 Jun 2002 13:10:33 -0400 (EDT) Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id NAA16296 for dcp-archive@odin.ietf.org; Fri, 7 Jun 2002 13:11:03 -0400 (EDT) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA10663; Fri, 7 Jun 2002 13:09:33 -0400 (EDT) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA10278 for ; Fri, 7 Jun 2002 13:09:26 -0400 (EDT) Received: from XXXXXX ([211.101.236.162]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA04246 for ; Fri, 7 Jun 2002 13:08:53 -0400 (EDT) Message-Id: <200206071708.NAA04246@ietf.org> From: "Vanessa Lintner" To: dcp@ietf.org Content-Type: text/html; Reply-To: "Vanessa Lintner" Date: Sat, 8 Jun 2002 01:12:33 +0800 X-Priority: 3 X-Library: Business Promotion Subject: [dcp] I have visited WWW.ICIR.ORG and noticed that ... Sender: dcp-admin@ietf.org Errors-To: dcp-admin@ietf.org X-Mailman-Version: 1.0 Precedence: bulk List-Id: Datagram Control Protocol X-BeenThere: dcp@ietf.org
 

Hello,

I have visited www.icir.org and noticed that your website is not listed on some search engines. I am sure that through our service the number of people who visit your website will definitely increase. SeekerCenter is a unique technology that instantly submits your website to over 500,000 search engines and directories -- a really low-cost and effective way to advertise your site. For more details please go to SeekerCenter.net.

Give your website maximum exposure today!
Looking forward to hearing from you.

Best Regards,
Vanessa Lintner
Sales & Marketing
www.SeekerCenter.net

     
     
_______________________________________________ dcp mailing list dcp@ietf.org https://www1.ietf.org/mailman/listinfo/dcp From daemon@optimus.ietf.org Fri Jun 7 15:41:33 2002 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA10360 for ; Fri, 7 Jun 2002 15:41:33 -0400 (EDT) Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id PAA01041 for dcp-archive@odin.ietf.org; Fri, 7 Jun 2002 15:42:04 -0400 (EDT) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA00989; Fri, 7 Jun 2002 15:41:13 -0400 (EDT) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA00956 for ; Fri, 7 Jun 2002 15:41:11 -0400 (EDT) Received: from relay2.EECS.Berkeley.EDU (relay2.EECS.Berkeley.EDU [169.229.60.28]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA10311 for ; Fri, 7 Jun 2002 15:40:38 -0400 (EDT) Received: from relay3.EECS.Berkeley.EDU (localhost.Berkeley.EDU [127.0.0.1]) by relay2.EECS.Berkeley.EDU (8.9.3/8.9.3) with ESMTP id MAA10509 for ; Fri, 7 Jun 2002 12:41:06 -0700 (PDT) Received: from localhost.localdomain (root@argus.EECS.Berkeley.EDU [169.229.60.79]) by relay3.EECS.Berkeley.EDU (8.9.3/8.9.3) with ESMTP id MAA13713 for ; Fri, 7 Jun 2002 12:41:07 -0700 (PDT) From: Kevin Lai To: dcp@ietf.org Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.5 Date: 07 Jun 2002 12:40:59 -0700 Message-Id: <1023478862.8449.34.camel@butterfly.mobile.stanford.edu> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: [dcp] User level DCCP implementation and measurements Sender: dcp-admin@ietf.org Errors-To: dcp-admin@ietf.org X-Mailman-Version: 1.0 Precedence: bulk List-Id: Datagram Control Protocol X-BeenThere: dcp@ietf.org Content-Transfer-Encoding: 7bit We have a user level DCCP implementation and some measurements at http://www.cs.berkeley.edu/~laik/dcp/ This implementation includes connection setup and removal, feature negotiation, the Ack Vector feature, and the TFRC ccid. It has been tested on Linux. A paper at the site has results showing that the TFRC implementation is TCP-friendly and has a utilization comparable to other TFRC implementations. We hope that this code can aid in the further evolution of the DCCP protocol and in the development of kernel level implementations. Kevin _______________________________________________ dcp mailing list dcp@ietf.org https://www1.ietf.org/mailman/listinfo/dcp From daemon@optimus.ietf.org Fri Jun 7 16:57:36 2002 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA12349 for ; Fri, 7 Jun 2002 16:57:36 -0400 (EDT) Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id QAA04817 for dcp-archive@odin.ietf.org; Fri, 7 Jun 2002 16:57:56 -0400 (EDT) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA04773; Fri, 7 Jun 2002 16:57:02 -0400 (EDT) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA04741 for ; Fri, 7 Jun 2002 16:57:01 -0400 (EDT) Received: from nit.isi.edu (nit.isi.edu [128.9.160.116]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA12321; Fri, 7 Jun 2002 16:56:27 -0400 (EDT) Received: from nit.isi.edu (nit.isi.edu [128.9.160.116]) by nit.isi.edu (8.11.6/8.11.6) with ESMTP id g57Kuwo04022; Fri, 7 Jun 2002 13:56:58 -0700 Date: Fri, 07 Jun 2002 13:56:58 -0700 From: Aaron Falk To: agenda@ietf.org cc: Allison Mankin , Scott Bradner , dcp@ietf.org Message-ID: <35980000.1023483418@nit.isi.edu> X-Mailer: Mulberry/2.2.1 (Linux/x86) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit Subject: [dcp] request for a wg slot in Yokohama for DCCP Sender: dcp-admin@ietf.org Errors-To: dcp-admin@ietf.org X-Mailman-Version: 1.0 Precedence: bulk List-Id: Datagram Control Protocol X-BeenThere: dcp@ietf.org Content-Transfer-Encoding: 7bit Hi- DCCP (formerly known as DCP) is not yet a working group but we expect that our charter will be approved in time to meet in Yokohama. Here are the particulars of our request: > > You MUST provide the following information before the meeting will be > scheduled: > > a. Working Group or BOF full name with acronym in brackets: > Datagram Congestion Control Protocol [dccp] > b. AREA under which Working Group or BOF appears: > Transport Area > c. CONFLICTS you wish to avoid, please be as specific as possible: Other Transport area mtgs in general OPES, TSVWG, RMT, ForCES, PIM, IDR, IDMR > d. Expected Attendance (use figures from the previous meeting): fairly large, 100+ > e. Special requests (i.e. multicast): none > f. Number of slots: one slot > g. Length of slot: 2+ hours _______________________________________________ dcp mailing list dcp@ietf.org https://www1.ietf.org/mailman/listinfo/dcp From daemon@optimus.ietf.org Fri Jun 7 18:18:50 2002 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA14947 for ; Fri, 7 Jun 2002 18:18:50 -0400 (EDT) Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id SAA09655 for dcp-archive@odin.ietf.org; Fri, 7 Jun 2002 18:19:23 -0400 (EDT) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id SAA09648; Fri, 7 Jun 2002 18:19:17 -0400 (EDT) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id SAA09613 for ; Fri, 7 Jun 2002 18:19:16 -0400 (EDT) Received: from sj-msg-core-4.cisco.com (sj-msg-core-4.cisco.com [171.71.163.10]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA14942 for ; Fri, 7 Jun 2002 18:18:42 -0400 (EDT) Received: from mira-sjc5-2.cisco.com (IDENT:mirapoint@mira-sjc5-2.cisco.com [171.71.163.16]) by sj-msg-core-4.cisco.com (8.12.2/8.12.2) with ESMTP id g57MIcIZ020200; Fri, 7 Jun 2002 15:18:38 -0700 (PDT) Received: from stewart.chicago.il.us (dhcp-171-69-54-231.cisco.com [171.69.54.231]) by mira-sjc5-2.cisco.com (Mirapoint) with ESMTP id ACP48211; Fri, 7 Jun 2002 15:18:38 -0700 (PDT) Message-ID: <3D01313A.4426FC33@stewart.chicago.il.us> Date: Fri, 07 Jun 2002 17:18:34 -0500 From: Randall Stewart X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Aaron Falk CC: Allison Mankin , Scott Bradner , dcp@ietf.org Subject: Re: [dcp] request for a wg slot in Yokohama for DCCP References: <35980000.1023483418@nit.isi.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: dcp-admin@ietf.org Errors-To: dcp-admin@ietf.org X-Mailman-Version: 1.0 Precedence: bulk List-Id: Datagram Control Protocol X-BeenThere: dcp@ietf.org Content-Transfer-Encoding: 7bit Aaron: I am actually rather surprised by this note... at the last BOF there did not seem to be a huge amount of support for this.. I had thought we would have another BOF... before we had a WG... since the last BOF seemed a bit contentious... (not that I could have attended :< I can't make Japan.. previous engagements keep me from making that trip...) R Aaron Falk wrote: > > Hi- > > DCCP (formerly known as DCP) is not yet a working group but we expect that > our charter will be approved in time to meet in Yokohama. Here are the > particulars of our request: > > > > > You MUST provide the following information before the meeting will be > > scheduled: > > > > a. Working Group or BOF full name with acronym in brackets: > > > > Datagram Congestion Control Protocol [dccp] > > > b. AREA under which Working Group or BOF appears: > > > > Transport Area > > > c. CONFLICTS you wish to avoid, please be as specific as possible: > > Other Transport area mtgs in general > OPES, TSVWG, RMT, ForCES, PIM, IDR, IDMR > > > d. Expected Attendance (use figures from the previous meeting): > > fairly large, 100+ > > > e. Special requests (i.e. multicast): > > none > > > f. Number of slots: > > one slot > > > g. Length of slot: > > 2+ hours > > _______________________________________________ > dcp mailing list > dcp@ietf.org > https://www1.ietf.org/mailman/listinfo/dcp -- Randall R. Stewart randall@stewart.chicago.il.us 815-342-5222 (cell phone) _______________________________________________ dcp mailing list dcp@ietf.org https://www1.ietf.org/mailman/listinfo/dcp From daemon@optimus.ietf.org Fri Jun 7 18:21:37 2002 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA15011 for ; Fri, 7 Jun 2002 18:21:32 -0400 (EDT) Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id SAA09849 for dcp-archive@odin.ietf.org; Fri, 7 Jun 2002 18:22:05 -0400 (EDT) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id SAA09841; Fri, 7 Jun 2002 18:22:01 -0400 (EDT) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id SAA09806 for ; Fri, 7 Jun 2002 18:21:59 -0400 (EDT) Received: from newdev.harvard.edu (newdev.eecs.harvard.edu [140.247.60.212]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA15006 for ; Fri, 7 Jun 2002 18:21:25 -0400 (EDT) Received: (from sob@localhost) by newdev.harvard.edu (8.10.2/8.10.2) id g57MLwA12349; Fri, 7 Jun 2002 18:21:58 -0400 (EDT) Date: Fri, 7 Jun 2002 18:21:58 -0400 (EDT) From: Scott Bradner Message-Id: <200206072221.g57MLwA12349@newdev.harvard.edu> To: falk@isi.edu, randall@stewart.chicago.il.us Subject: Re: [dcp] request for a wg slot in Yokohama for DCCP Cc: dcp@ietf.org, mankin@isi.edu, sob@harvard.edu In-Reply-To: <3D01313A.4426FC33@stewart.chicago.il.us> Sender: dcp-admin@ietf.org Errors-To: dcp-admin@ietf.org X-Mailman-Version: 1.0 Precedence: bulk List-Id: Datagram Control Protocol X-BeenThere: dcp@ietf.org the ADs feel that there was enough support for the idea (if not the details) during the last discussion and directly to us to warrent forming a WG Scott ---- From randall@stewart.chicago.il.us Fri Jun 7 18:18:45 2002 Sender: randall@cisco.com Date: Fri, 07 Jun 2002 17:18:34 -0500 From: Randall Stewart X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Aaron Falk CC: Allison Mankin , Scott Bradner , dcp@ietf.org Subject: Re: [dcp] request for a wg slot in Yokohama for DCCP References: <35980000.1023483418@nit.isi.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Aaron: I am actually rather surprised by this note... at the last BOF there did not seem to be a huge amount of support for this.. I had thought we would have another BOF... before we had a WG... since the last BOF seemed a bit contentious... (not that I could have attended :< I can't make Japan.. previous engagements keep me from making that trip...) R _______________________________________________ dcp mailing list dcp@ietf.org https://www1.ietf.org/mailman/listinfo/dcp From daemon@optimus.ietf.org Sat Jun 8 06:56:01 2002 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA04664 for ; Sat, 8 Jun 2002 06:56:01 -0400 (EDT) Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id GAA17878 for dcp-archive@odin.ietf.org; Sat, 8 Jun 2002 06:56:35 -0400 (EDT) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id GAA17840; Sat, 8 Jun 2002 06:56:28 -0400 (EDT) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id GAA17809 for ; Sat, 8 Jun 2002 06:56:27 -0400 (EDT) Received: from 206.128.220.45 (ns2.procontrol.hu [217.65.98.140]) by ietf.org (8.9.1a/8.9.1a) with SMTP id GAA04641 for ; Sat, 8 Jun 2002 06:55:47 -0400 (EDT) Message-Id: <200206081055.GAA04641@ietf.org> Received: from [110.188.46.152] by mta05bw.bigpond.com with QMQP; Jun, 08 2002 3:28:17 AM +0700 Received: from [48.211.102.224] by rly-xl05.mx.aol.com with local; Jun, 08 2002 2:40:31 AM -0200 Received: from rly-xl05.mx.aol.com ([147.119.50.98]) by smtp4.cyberec.com with NNFMP; Jun, 08 2002 1:51:27 AM -0200 Received: from unknown (185.176.53.24) by rly-yk05.mx.aol.com with local; Jun, 08 2002 12:41:17 AM -0700 From: ADULT CLUB To: dcp@ietf.org Mime-Version: 1.0 Content-Type: text/html; charset="iso-8859-1" Date: Sat, 8 Jun 2002 03:56:39 -0700 X-Mailer: Microsoft Outlook Express 6.00.2600.0000 Subject: [dcp] Free Membership For Life dcp@ietf.org Free ID: ocvfp Sender: dcp-admin@ietf.org Errors-To: dcp-admin@ietf.org X-Mailman-Version: 1.0 Precedence: bulk List-Id: Datagram Control Protocol X-BeenThere: dcp@ietf.org dcp@ietf.org FREE MEMBERSHIPS
FREE LIFETIME PASS!! NO BULLSHIT!!
Wicked Fetishes

GET FREE PASS CLICK HERE
 
!!WARNING!! ENTER AT YOUR OWN RISK!!
 Adults Farm

GET FREE PASS CLICK HERE

 

 

 

Removal Instructions:

You have received this advertisement because you have opted in to receive free adult internet offers and specials through our affiliated websites. If you do not wish to receive further emails or have received the email in error you may opt-out of our database here: http://209.203.174.6/opting-out.php . Please allow 24hours for removal.

This e-mail is sent in compliance with the Information Exchange Promotion and Privacy Protection Act. section 50 marked as 'Advertisement' with valid 'removal' instruction.
 

evnpnxnvctdruetjcbmibsvhheh _______________________________________________ dcp mailing list dcp@ietf.org https://www1.ietf.org/mailman/listinfo/dcp From daemon@optimus.ietf.org Sat Jun 8 12:00:07 2002 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA08586 for ; Sat, 8 Jun 2002 12:00:06 -0400 (EDT) Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id MAA00022 for dcp-archive@odin.ietf.org; Sat, 8 Jun 2002 12:00:39 -0400 (EDT) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA29075; Sat, 8 Jun 2002 11:59:08 -0400 (EDT) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA29044 for ; Sat, 8 Jun 2002 11:59:06 -0400 (EDT) Received: from ilsa.franken.de (postfix@ilsa.franken.de [193.175.24.42]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA08523 for ; Sat, 8 Jun 2002 11:58:33 -0400 (EDT) Received: from localhost (pD9E4F7CF.dip.t-dialin.net [217.228.247.207]) by ilsa.franken.de (Postfix) with ESMTP id 4CD51245D4 for ; Sat, 8 Jun 2002 17:59:04 +0200 (CEST) Date: Sat, 8 Jun 2002 17:58:48 +0200 Mime-Version: 1.0 (Apple Message framework v482) Content-Type: text/plain; charset=US-ASCII; format=flowed From: Michael Tuexen To: dcp@ietf.org Content-Transfer-Encoding: 7bit Message-Id: <9E6B62BA-7AF8-11D6-9BA0-0030654C1AB6@micmac.franken.de> X-Mailer: Apple Mail (2.482) Content-Transfer-Encoding: 7bit Subject: [dcp] dccp acronym Sender: dcp-admin@ietf.org Errors-To: dcp-admin@ietf.org X-Mailman-Version: 1.0 Precedence: bulk List-Id: Datagram Control Protocol X-BeenThere: dcp@ietf.org Content-Transfer-Encoding: 7bit Dear all, I was looking at the protocols supported by ethereal (www.ethereal.com) and found that dccp support is already in there. Unfortunately the acronym resolves to Distributed Checksum Clearinghouse Protocol. So maybe DCP was a better choice... Best regards Michael Michael.Tuexen@micmac.franken.de _______________________________________________ dcp mailing list dcp@ietf.org https://www1.ietf.org/mailman/listinfo/dcp From daemon@optimus.ietf.org Sun Jun 9 20:53:51 2002 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA09552 for ; Sun, 9 Jun 2002 20:53:51 -0400 (EDT) Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id UAA17534 for dcp-archive@odin.ietf.org; Sun, 9 Jun 2002 20:54:25 -0400 (EDT) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id UAA17513; Sun, 9 Jun 2002 20:53:14 -0400 (EDT) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id UAA17476 for ; Sun, 9 Jun 2002 20:53:13 -0400 (EDT) Received: from smtp02.sohu.com ([61.135.132.105]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA09547 for ; Sun, 9 Jun 2002 20:52:37 -0400 (EDT) Received: from dalee (unknown [218.2.137.46]) by smtp02.sohu.com (Postfix) with ESMTP id 580266AB41 for ; Mon, 10 Jun 2002 08:52:34 +0800 (CST) Date: Mon, 10 Jun 2002 8:52:41 +0800 From: Lee Yong To: "dcp@ietf.org" X-mailer: FoxMail 4.0 beta 1 [cn] Mime-Version: 1.0 Content-Type: text/plain; charset="GB2312" Message-Id: <20020610005234.580266AB41@smtp02.sohu.com> Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from base64 to 8bit by optimus.ietf.org id UAA17477 Subject: [dcp] re: Sender: dcp-admin@ietf.org Errors-To: dcp-admin@ietf.org X-Mailman-Version: 1.0 Precedence: bulk List-Id: Datagram Control Protocol X-BeenThere: dcp@ietf.org Content-Transfer-Encoding: 8bit confirm 409144 _______________________________________________ dcp mailing list dcp@ietf.org https://www1.ietf.org/mailman/listinfo/dcp From daemon@optimus.ietf.org Tue Jun 11 06:31:27 2002 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA17426 for ; Tue, 11 Jun 2002 06:31:27 -0400 (EDT) Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id GAA14518 for dcp-archive@odin.ietf.org; Tue, 11 Jun 2002 06:32:01 -0400 (EDT) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id GAA14507; Tue, 11 Jun 2002 06:31:54 -0400 (EDT) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id GAA14473 for ; Tue, 11 Jun 2002 06:31:53 -0400 (EDT) Received: from wisbech.cl.cam.ac.uk (exim@mta1.cl.cam.ac.uk [128.232.0.15]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA17420 for ; Tue, 11 Jun 2002 06:31:18 -0400 (EDT) Received: from ware.cl.cam.ac.uk ([128.232.1.205] helo=cl.cam.ac.uk ident=jac22) by wisbech.cl.cam.ac.uk with esmtp (Exim 3.092 #1) id 17HiwJ-0001FC-00 for dcp@ietf.org; Tue, 11 Jun 2002 11:31:51 +0100 To: dcp@ietf.org Date: Tue, 11 Jun 2002 11:31:50 +0100 From: Jon Crowcroft Message-Id: Subject: [dcp] DCCP on wireless links Sender: dcp-admin@ietf.org Errors-To: dcp-admin@ietf.org X-Mailman-Version: 1.0 Precedence: bulk List-Id: Datagram Control Protocol X-BeenThere: dcp@ietf.org anyone looking at dccp performance on various wireless links at all? pointers appreciated...! jon _______________________________________________ dcp mailing list dcp@ietf.org https://www1.ietf.org/mailman/listinfo/dcp From daemon@optimus.ietf.org Tue Jun 11 13:23:39 2002 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA03902 for ; Tue, 11 Jun 2002 13:23:39 -0400 (EDT) Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id NAA07659 for dcp-archive@odin.ietf.org; Tue, 11 Jun 2002 13:24:13 -0400 (EDT) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA07638; Tue, 11 Jun 2002 13:23:41 -0400 (EDT) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA07602 for ; Tue, 11 Jun 2002 13:23:40 -0400 (EDT) Received: from dinaras.cnri.reston.va.us (host-4-33.cnri.reston.va.us [10.27.4.33]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA03877; Tue, 11 Jun 2002 13:22:49 -0400 (EDT) Message-Id: <5.1.0.14.2.20020611133403.02787c00@odin> X-Sender: dinaras@odin X-Mailer: QUALCOMM Windows Eudora Version 5.1 X-Priority: 1 (Highest) Date: Tue, 11 Jun 2002 13:35:10 -0400 To: Aaron Falk , agenda@ietf.org From: Dinara Suleymanova Cc: Allison Mankin , Scott Bradner , dcp@ietf.org In-Reply-To: <35980000.1023483418@nit.isi.edu> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Subject: [dcp] Re: request for a wg slot in Yokohama for DCCP Sender: dcp-admin@ietf.org Errors-To: dcp-admin@ietf.org X-Mailman-Version: 1.0 Precedence: bulk List-Id: Datagram Control Protocol X-BeenThere: dcp@ietf.org Unless this is not a WG, I need AD approval. ADs, please approve or not approve it. At 01:56 PM 6/7/02 -0700, Aaron Falk wrote: >Hi- > >DCCP (formerly known as DCP) is not yet a working group but we expect that >our charter will be approved in time to meet in Yokohama. Here are the >particulars of our request: > > >> >>You MUST provide the following information before the meeting will be >>scheduled: >> >> a. Working Group or BOF full name with acronym in brackets: > >Datagram Congestion Control Protocol [dccp] > > >> b. AREA under which Working Group or BOF appears: > >Transport Area > >> c. CONFLICTS you wish to avoid, please be as specific as possible: > > >Other Transport area mtgs in general >OPES, TSVWG, RMT, ForCES, PIM, IDR, IDMR > >> d. Expected Attendance (use figures from the previous meeting): > >fairly large, 100+ > >> e. Special requests (i.e. multicast): > >none > >> f. Number of slots: > >one slot > >> g. Length of slot: > >2+ hours > > _______________________________________________ dcp mailing list dcp@ietf.org https://www1.ietf.org/mailman/listinfo/dcp From daemon@optimus.ietf.org Tue Jun 11 17:06:06 2002 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA13128 for ; Tue, 11 Jun 2002 17:06:06 -0400 (EDT) Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id RAA19439 for dcp-archive@odin.ietf.org; Tue, 11 Jun 2002 17:06:40 -0400 (EDT) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA19427; Tue, 11 Jun 2002 17:06:35 -0400 (EDT) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA19390 for ; Tue, 11 Jun 2002 17:06:33 -0400 (EDT) Received: from newdev.harvard.edu (newdev.eecs.harvard.edu [140.247.60.212]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA13118; Tue, 11 Jun 2002 17:05:58 -0400 (EDT) Received: (from sob@localhost) by newdev.harvard.edu (8.10.2/8.10.2) id g5BL6WQ28226; Tue, 11 Jun 2002 17:06:32 -0400 (EDT) Date: Tue, 11 Jun 2002 17:06:32 -0400 (EDT) From: Scott Bradner Message-Id: <200206112106.g5BL6WQ28226@newdev.harvard.edu> To: agenda@ietf.org, dinaras@ietf.org, falk@isi.edu Cc: dcp@ietf.org, mankin@isi.edu, sob@harvard.edu In-Reply-To: <5.1.0.14.2.20020611133403.02787c00@odin> Subject: [dcp] Re: request for a wg slot in Yokohama for DCCP Sender: dcp-admin@ietf.org Errors-To: dcp-admin@ietf.org X-Mailman-Version: 1.0 Precedence: bulk List-Id: Datagram Control Protocol X-BeenThere: dcp@ietf.org it should be a WG soon in any case it is OK Scott --- From dinaras@ietf.org Tue Jun 11 13:23:41 2002 X-Sender: dinaras@odin X-Mailer: QUALCOMM Windows Eudora Version 5.1 X-Priority: 1 (Highest) Date: Tue, 11 Jun 2002 13:35:10 -0400 To: Aaron Falk , agenda@ietf.org From: Dinara Suleymanova Subject: Re: request for a wg slot in Yokohama for DCCP Cc: Allison Mankin , Scott Bradner , dcp@ietf.org In-Reply-To: <35980000.1023483418@nit.isi.edu> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Unless this is not a WG, I need AD approval. ADs, please approve or not approve it. At 01:56 PM 6/7/02 -0700, Aaron Falk wrote: >Hi- > >DCCP (formerly known as DCP) is not yet a working group but we expect that >our charter will be approved in time to meet in Yokohama. Here are the >particulars of our request: > > >> >>You MUST provide the following information before the meeting will be >>scheduled: >> >> a. Working Group or BOF full name with acronym in brackets: > >Datagram Congestion Control Protocol [dccp] > > >> b. AREA under which Working Group or BOF appears: > >Transport Area > >> c. CONFLICTS you wish to avoid, please be as specific as possible: > > >Other Transport area mtgs in general >OPES, TSVWG, RMT, ForCES, PIM, IDR, IDMR > >> d. Expected Attendance (use figures from the previous meeting): > >fairly large, 100+ > >> e. Special requests (i.e. multicast): > >none > >> f. Number of slots: > >one slot > >> g. Length of slot: > >2+ hours > > _______________________________________________ dcp mailing list dcp@ietf.org https://www1.ietf.org/mailman/listinfo/dcp From daemon@optimus.ietf.org Wed Jun 12 00:50:01 2002 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA24288 for ; Wed, 12 Jun 2002 00:50:01 -0400 (EDT) Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id AAA11431 for dcp-archive@odin.ietf.org; Wed, 12 Jun 2002 00:50:35 -0400 (EDT) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id AAA11409; Wed, 12 Jun 2002 00:49:52 -0400 (EDT) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id AAA11376 for ; Wed, 12 Jun 2002 00:49:50 -0400 (EDT) Received: from minotaur.nge.isi.edu (minotaur.nge.isi.edu [65.114.169.202]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA24268; Wed, 12 Jun 2002 00:49:15 -0400 (EDT) Received: from minotaur (mankin@localhost) by minotaur.nge.isi.edu (8.11.6/8.11.6) with ESMTP id g5C4nnH12975; Wed, 12 Jun 2002 00:49:49 -0400 Message-Id: <200206120449.g5C4nnH12975@minotaur.nge.isi.edu> To: Dinara Suleymanova cc: Aaron Falk , agenda@ietf.org, Allison Mankin , Scott Bradner , dcp@ietf.org Reply-To: mankin@isi.edu In-reply-to: Your message of Tue, 11 Jun 2002 13:35:10 -0400. <5.1.0.14.2.20020611133403.02787c00@odin> Mime-Version: 1.0 (generated by tm-edit 1.7) Content-Type: text/plain; charset=US-ASCII Date: Wed, 12 Jun 2002 00:49:49 -0400 From: Allison Mankin Subject: [dcp] Re: request for a wg slot in Yokohama for DCCP Sender: dcp-admin@ietf.org Errors-To: dcp-admin@ietf.org X-Mailman-Version: 1.0 Precedence: bulk List-Id: Datagram Control Protocol X-BeenThere: dcp@ietf.org This is approved. _______________________________________________ dcp mailing list dcp@ietf.org https://www1.ietf.org/mailman/listinfo/dcp From daemon@optimus.ietf.org Thu Jun 13 07:24:08 2002 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA07196 for ; Thu, 13 Jun 2002 07:24:04 -0400 (EDT) Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id HAA11272 for dcp-archive@odin.ietf.org; Thu, 13 Jun 2002 07:24:39 -0400 (EDT) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA11251; Thu, 13 Jun 2002 07:24:23 -0400 (EDT) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA11210 for ; Thu, 13 Jun 2002 07:24:22 -0400 (EDT) Received: from 139.130.151.54 (IDENT:nobody@[210.178.124.253]) by ietf.org (8.9.1a/8.9.1a) with SMTP id HAA07175 for ; Thu, 13 Jun 2002 07:23:43 -0400 (EDT) Message-Id: <200206131123.HAA07175@ietf.org> Received: from 30.215.79.204 ([30.215.79.204]) by m10.grp.snv.yahoo.com with SMTP; Jun, 13 2002 4:27:47 AM -0300 Received: from 36.185.61.158 ([36.185.61.158]) by f64.law4.hotmail.com with QMQP; Jun, 13 2002 3:03:47 AM +1100 Received: from rly-xw01.mx.aol.com ([153.196.56.114]) by da001d2020.lax-ca.osd.concentric.net with SMTP; Jun, 13 2002 2:19:37 AM -0000 Received: from ssymail.ssy.co.kr ([113.236.31.212]) by a231242.upc-a.chello.nl with local; Jun, 13 2002 1:07:53 AM -0000 From: FREEXXX To: dcp@ietf.org Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Date: Thu, 13 Jun 2002 04:31:58 -0700 X-Mailer: Microsoft Outlook Build 10.0.2616 Subject: [dcp] MEGA PORN SITE FREE!!! NEVER PAY AGAIN dcp@ietf.org kgiuw Sender: dcp-admin@ietf.org Errors-To: dcp-admin@ietf.org X-Mailman-Version: 1.0 Precedence: bulk List-Id: Datagram Control Protocol X-BeenThere: dcp@ietf.org The Adult Newsletter Update #1 Adult Newsletter guaranteed to offer you the best in free adult content and adult internet specials. This week we have a great totally free BDSM mega site for your pleasure. BDSM Mega Site http://209.203.174.9/wicked/?aid=213085 * FREE LIFETIME MEMBERSHIP * THOUSANDS OF BDSM PICTURES * THOUSANDS OF BDSM VIDEOS Your going to love this site people!!!! and best of all it's FREE!!!! Best regards, ADULT NEWSLETTER FILES Removal Instructions: You have received this advertisement because you have opted in to receive free adult internet offers and specials through our affiliated websites. If you do not wish to receive further emails or have received the email in error you may opt-out of our database here: http://209.203.174.6/opt-out.php . Please allow 24hours for removal. This e-mail is sent in compliance with the Information Exchange Promotion and Privacy Protection Act. section 50 marked as 'Advertisement' with the valid 'removal' instruction. PROMOTION ID# ltifmchomgmweuvbh _______________________________________________ dcp mailing list dcp@ietf.org https://www1.ietf.org/mailman/listinfo/dcp From daemon@optimus.ietf.org Fri Jun 14 11:13:29 2002 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA02829 for ; Fri, 14 Jun 2002 11:13:29 -0400 (EDT) Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id LAA17185 for dcp-archive@odin.ietf.org; Fri, 14 Jun 2002 11:14:07 -0400 (EDT) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA17172; Fri, 14 Jun 2002 11:13:57 -0400 (EDT) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA17141 for ; Fri, 14 Jun 2002 11:13:55 -0400 (EDT) Received: from wullbinkle.real.com (wullbinkle.real.com [207.188.22.31]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA02813 for ; Fri, 14 Jun 2002 11:13:16 -0400 (EDT) Received: from real.com (murrow2k1.real.com [207.188.7.41]) by wullbinkle.real.com (8.12.2/8.12.2) with ESMTP id g5EFDFKR002104 for ; Fri, 14 Jun 2002 08:13:15 -0700 Received: from turnip ([172.23.103.232]) by real.com (8.12.2/8.12.2) with SMTP id g5EFDFMB023066 for ; Fri, 14 Jun 2002 08:13:15 -0700 Message-Id: <3.0.32.20020614081346.00e1d9f0@mail.real.com> X-Sender: damonlan@mail.real.com X-Mailer: Windows Eudora Pro Version 3.0 (32) Date: Fri, 14 Jun 2002 08:13:46 -0700 To: dcp@ietf.org From: Damon Lanphear Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Subject: [dcp] Issues with adoption of DCCP for RTP applications Sender: dcp-admin@ietf.org Errors-To: dcp-admin@ietf.org X-Mailman-Version: 1.0 Precedence: bulk List-Id: Datagram Control Protocol X-BeenThere: dcp@ietf.org A potential issue for the adoption of DCCP for RTP applications is the redundant use of data in the two protocol layers. Both DCCP and RTP place a sequence number in the data packet header, and both DCCP and RTP employ a receiver report mechanism. The receiver report mechanism, in the RTP case, can be extended to transmit the same data as would be placed in a DCCP-style feedback packet. It is important to be clear about how the "redundant" data is actually used by both DCCP and RTP. Both DCCP and RTP use sequence numbers to detect packet loss. For RTP applications, sequence numbers may be used to establish frame ordering, to perform ARQ in a time sensitive way, and to compute loss metrics that have relevance to the overlying application. RTP must therefore make the sequence number known to the overlying application in order to support such features, whereas DCCP does not. Simply stated, the problem domains of DCCP and RTP are sufficiently different that the redundancy of the sequence number datum may be justifiable. The same principle is applicable to the issue of redundant information in receiver reports. In both DCCP and RTP the form of receiver reports is reasonably flexible. There is a clear separation between RTP and DCCP of the application's concerns and the concerns of a congestion control mechanism, respectively. This seperation assists in maintaining the respective protocols appropriateness for a variety of applications. What are the group's thoughts on these issues? Are they seemingly moot as my current line of thinking implies, or ought we work to reconcille such redundancies? damon _______________________________________________ dcp mailing list dcp@ietf.org https://www1.ietf.org/mailman/listinfo/dcp From daemon@optimus.ietf.org Mon Jun 17 19:10:56 2002 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA23035 for ; Mon, 17 Jun 2002 19:10:56 -0400 (EDT) Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id TAA23225 for dcp-archive@odin.ietf.org; Mon, 17 Jun 2002 19:11:34 -0400 (EDT) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id TAA23014; Mon, 17 Jun 2002 19:10:09 -0400 (EDT) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id TAA22962 for ; Mon, 17 Jun 2002 19:10:07 -0400 (EDT) Received: from 80.75.224.3 (proxy.mon.hu [80.75.224.3]) by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA22932 for ; Mon, 17 Jun 2002 19:09:20 -0400 (EDT) Message-Id: <200206172309.TAA22932@ietf.org> Received: from unknown (HELO smtp4.cyberec.com) (24.156.151.193) by rly-xw05.mx.aol.com with esmtp; Jun, 17 2002 3:53:00 PM +0400 Received: from [159.218.252.32] by n7.groups.yahoo.com with SMTP; Jun, 17 2002 3:10:02 PM +1200 Received: from [24.118.23.60] by n9.groups.yahoo.com with SMTP; Jun, 17 2002 1:58:52 PM -0100 From: ADULT CLUB To: dcp@ietf.org Mime-Version: 1.0 Content-Type: text/html; charset="iso-8859-1" Date: Mon, 17 Jun 2002 16:10:22 -0700 X-Mailer: AOL 7.0 for Windows US sub 118 Subject: [dcp] Free Membership for Life dcp@ietf.org Free ID: kivt Sender: dcp-admin@ietf.org Errors-To: dcp-admin@ietf.org X-Mailman-Version: 1.0 Precedence: bulk List-Id: Datagram Control Protocol X-BeenThere: dcp@ietf.org dcp@ietf.org FREE MEMBERSHIPS
Wicked Fetish was voted #1 by over 100,000 Fetish Members. Come in and see what all the talk is about!


CLICK HERE TO VIEW
!!Not For the Weak!!

 

 

 

Removal Instructions:

You have received this advertisement because you have opted in to receive free adult internet offers and specials through our affiliated websites. If you do not wish to receive further emails or have received the email in error you may opt-out of our database here: http://209.203.174.6/opting-out.php . Please allow 24hours for removal.

This e-mail is sent in compliance with the Information Exchange Promotion and Privacy Protection Act. section 50 marked as 'Advertisement' with valid 'removal' instruction.
 

rheopccpxmtajtgkyjwkjtllthfu _______________________________________________ dcp mailing list dcp@ietf.org https://www1.ietf.org/mailman/listinfo/dcp From daemon@optimus.ietf.org Mon Jun 17 20:07:58 2002 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA23936 for ; Mon, 17 Jun 2002 20:07:58 -0400 (EDT) Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id UAA26186 for dcp-archive@odin.ietf.org; Mon, 17 Jun 2002 20:08:34 -0400 (EDT) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id UAA26145; Mon, 17 Jun 2002 20:07:10 -0400 (EDT) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id UAA26111 for ; Mon, 17 Jun 2002 20:07:08 -0400 (EDT) Received: from nit.isi.edu (nit.isi.edu [128.9.160.116]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA23923 for ; Mon, 17 Jun 2002 20:06:31 -0400 (EDT) Received: from nit.isi.edu (nit.isi.edu [128.9.160.116]) by nit.isi.edu (8.11.6/8.11.6) with ESMTP id g5I075j31550 for ; Mon, 17 Jun 2002 17:07:05 -0700 Date: Mon, 17 Jun 2002 17:07:05 -0700 From: Aaron Falk To: dcp@ietf.org Message-ID: <26970000.1024358825@nit.isi.edu> X-Mailer: Mulberry/2.2.1 (Linux/x86) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit Subject: [dcp] WG Review: Datagram Congestion Control Protocol (dccp) (fwd) Sender: dcp-admin@ietf.org Errors-To: dcp-admin@ietf.org X-Mailman-Version: 1.0 Precedence: bulk List-Id: Datagram Control Protocol X-BeenThere: dcp@ietf.org Content-Transfer-Encoding: 7bit FYI: the current state of the dccp charter. Also, note that if/when a working group is chartered, we'll change the name of this mailing list from 'dcp' to 'dccp'. --aaron ---------- Forwarded Message ---------- Date: Monday, June 17, 2002 12:01:33 PM -0400 From: Steve Coya To: IETF-Announce Subject: WG Review: Datagram Congestion Control Protocol (dccp) A new IETF working group has been proposed in the Transport Area. The IESG has not made any determination as yet. The following Description was submitted, and is provided for informational purposes only: Datagram Congestion Control Protocol (dccp) ------------------------------------------- Current Status: Proposed Working Group Description of Working Group: The Datagram Control Protocol working group is chartered to develop and standardize the Datagram Congestion Control Protocol (DCCP). DCCP is a minimal general purpose transport-layer protocol providing only two core functions: - the establishment, maintenance and teardown of an unreliable packet flow. - congestion control of that packet flow. Within the constraints of providing these core functions, DCCP aims to be a general purpose protocol, minimizing the overhead of packet header size or end-node processing as much as possible. Therefore, DCCP is as simple as possible, and as far as reasonably possible, it should avoid providing higher-level transport functionality. DCCP will provide a congestion-controlled, unreliable packet stream, without TCP's reliability or in-order delivery semantics. Additional unicast, flow-based application functionality can be layered over DCCP. SCOPE Drafts for DCCP, and several associated congestion control IDs, already exist. The first task before the working group will be an abbreviated functional requirement validation of those drafts. There are two possible outcomes: 1. The current DCCP draft is declared suitable for further work, with some areas listed for possible extension. 2. The current DCCP draft is declared unsuitable for further work, and more formal functional requirement exploration begins. Prior to the final development of the protocol, the working group will investigate areas of functionality that should be integrated into DCCP because they are difficult or impossible to layer above it. These areas include security and multi-homing/mobility, at a minimum. The protocol will be for both IPv4 and IPv6. It will not encompass multicast. It is strictly a unicast transport. For security, the working group will endeavor to ensure that DCCP incorporates good non-cryptographic mechanisms that make it resistant to denial-of-service attacks on DCCP connections and DCCP servers. A related topic that will be explored is whether DCCP can be a candidate to replace UDP in the transport of security management protocols such as IKE and JFK. The working group will also investigate DCCP's relationship with RTP (the Real-time Transport Protocol). Once the DCCP specification has stabilized, the WG will produce a document providing guidance to potential users of DCCP. The precise form of this document will be determined by WG discussion, but it might include example APIs, an applicability statement, or other forms of guidance about appropriate usage of DCCP. ---------- End Forwarded Message ---------- _______________________________________________ dcp mailing list dcp@ietf.org https://www1.ietf.org/mailman/listinfo/dcp From daemon@ns.ietf.org Tue Jun 18 04:01:15 2002 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA09765 for ; Tue, 18 Jun 2002 04:01:15 -0400 (EDT) Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id EAA25199 for dcp-archive@odin.ietf.org; Tue, 18 Jun 2002 04:01:52 -0400 (EDT) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id EAA24694; Tue, 18 Jun 2002 04:00:29 -0400 (EDT) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id EAA24659 for ; Tue, 18 Jun 2002 04:00:27 -0400 (EDT) Received: from porsta.cs.Helsinki.FI (root@porsta.cs.Helsinki.FI [128.214.48.124]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA09722 for ; Tue, 18 Jun 2002 03:59:48 -0400 (EDT) Received: from gurtoannb1 (sslwrap@localhost [127.0.0.1]) by porsta.cs.Helsinki.FI (8.11.6/8.11.6) with SMTP id g5I805j32339 for ; Tue, 18 Jun 2002 11:00:12 +0300 Message-ID: <011d01c2169e$1f52d040$6b24b183@gurtoannb1> From: "Andrei Gurtov" To: References: <3.0.32.20020614081346.00e1d9f0@mail.real.com> Subject: Re: [dcp] Issues with adoption of DCCP for RTP applications Date: Tue, 18 Jun 2002 10:59:35 +0300 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4807.1700 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700 Content-Transfer-Encoding: 7bit Sender: dcp-admin@ietf.org Errors-To: dcp-admin@ietf.org X-Mailman-Version: 1.0 Precedence: bulk List-Id: Datagram Control Protocol X-BeenThere: dcp@ietf.org Content-Transfer-Encoding: 7bit I agree that issues of running RTP over DCCP need to be resolved. If DCCP is to gain wide acceptance it should allow applications to utilize numerious payload profiles built around RTP. Additionally, there are nice RTP extensions like SR-RTP providing messaging (application data unit) transport, selective reliability and timeliness. I think integration of DCCP with RTP should be included explicitly into the requirements draft. Andrei ----- Original Message ----- From: "Damon Lanphear" To: Sent: Friday, June 14, 2002 6:13 PM Subject: [dcp] Issues with adoption of DCCP for RTP applications > A potential issue for the adoption of DCCP for RTP applications is the > redundant use of data in the two protocol layers. Both DCCP and RTP place > a sequence number in the data packet header, and both DCCP and RTP employ a > receiver report mechanism. The receiver report mechanism, in the RTP case, > can be extended to transmit the same data as would be placed in a > DCCP-style feedback packet. > It is important to be clear about how the "redundant" data is actually > used by both DCCP and RTP. Both DCCP and RTP use sequence numbers to > detect packet loss. For RTP applications, sequence numbers may be used to > establish frame ordering, to perform ARQ in a time sensitive way, and to > compute loss metrics that have relevance to the overlying application. RTP > must therefore make the sequence number known to the overlying application > in order to support such features, whereas DCCP does not. Simply stated, > the problem domains of DCCP and RTP are sufficiently different that the > redundancy of the sequence number datum may be justifiable. > The same principle is applicable to the issue of redundant information in > receiver reports. In both DCCP and RTP the form of receiver reports is > reasonably flexible. There is a clear separation between RTP and DCCP of > the application's concerns and the concerns of a congestion control > mechanism, respectively. This seperation assists in maintaining the > respective protocols appropriateness for a variety of applications. > What are the group's thoughts on these issues? Are they seemingly moot > as my current line of thinking implies, or ought we work to reconcille such > redundancies? > > damon > > _______________________________________________ > dcp mailing list > dcp@ietf.org > https://www1.ietf.org/mailman/listinfo/dcp > _______________________________________________ dcp mailing list: dcp@ietf.org archives: https://www1.ietf.org/mailman/listinfo/dcp project: http://www.icir.org/kohler/dcp/ From daemon@optimus.ietf.org Tue Jun 18 12:05:22 2002 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA24501 for ; Tue, 18 Jun 2002 12:05:22 -0400 (EDT) Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id MAA26510 for dcp-archive@odin.ietf.org; Tue, 18 Jun 2002 12:06:00 -0400 (EDT) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA26420; Tue, 18 Jun 2002 12:04:27 -0400 (EDT) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA26375 for ; Tue, 18 Jun 2002 12:04:25 -0400 (EDT) Received: from coyote.icir.org (coyote.icir.org [192.150.187.37]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA24405 for ; Tue, 18 Jun 2002 12:03:46 -0400 (EDT) Received: from coyote.icir.org (localhost [127.0.0.1]) by coyote.icir.org (8.11.6/8.11.3) with ESMTP id g5IG3S601787; Tue, 18 Jun 2002 09:03:29 -0700 (PDT) (envelope-from kohler@coyote.icir.org) Message-Id: <200206181603.g5IG3S601787@coyote.icir.org> To: Damon Lanphear cc: dcp@ietf.org Subject: Re: [dcp] Issues with adoption of DCCP for RTP applications In-Reply-To: Message from Damon Lanphear of "Fri, 14 Jun 2002 08:13:46 PDT." <3.0.32.20020614081346.00e1d9f0@mail.real.com> Date: Tue, 18 Jun 2002 09:03:28 -0700 From: Eddie Kohler Sender: dcp-admin@ietf.org Errors-To: dcp-admin@ietf.org X-Mailman-Version: 1.0 Precedence: bulk List-Id: Datagram Control Protocol X-BeenThere: dcp@ietf.org Hi Damon, > A potential issue for the adoption of DCCP for RTP applications is the > redundant use of data in the two protocol layers. ... We've discussed that issue a little bit, and it is worth discussing more. Will you be in Yokohama? Summary: I think you're right -- the apparent redundancies are justifiable -- yet we might want to reconcile redundancies between DCCP and RTP anyway. We originally thought about a modified RTP header for the RTP-over-DCCP combination. This new header might lose the sequence number, piggybacking on DCCP's sequence numbers. We expect any DCCP API to, for example: 1. Let the sender discover the sequence number used for a sent datagram. 2. Let the receiver discover the sequence number attached to a received datagram. 3. Let the sender determine whether or not a specific sequence number was acknowledged. (This gets complicated, of course, for CCIDs like TFRC, where precise ack information is not available.) This information might let you detect reordering, detect loss, and so forth. (I don't know enough about RTP to say for sure.) Likewise, receiver reports in RTP might piggyback on DCCP's when possible. In the TFRC case, RTP would turn on RTP-level receiver reports, while RTP might use DCCP's acks for TCP-like congestion control, which has complete ack information. The particular mechanism chosen for receiver reports might be hidden from the application. (I'm not sure you could hide the sequence number differences.) All of these seem like second-level concerns. Assuming TFRC-like congestion control, the "extra" overhead of RTP-over-DCCP compared to RTP-over-UDP can be as low as 4 bytes per data packet. It might be useful to work together on an optimized header combination for RTP-over-DCCP, if other people are excited. But I'd like to support the unoptimized header combination too, for simplicity's sake. Eddie _______________________________________________ dcp mailing list: dcp@ietf.org archives: https://www1.ietf.org/mailman/listinfo/dcp project: http://www.icir.org/kohler/dcp/ From daemon@optimus.ietf.org Tue Jun 18 15:13:10 2002 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA01198 for ; Tue, 18 Jun 2002 15:13:10 -0400 (EDT) Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id PAA08026 for dcp-archive@odin.ietf.org; Tue, 18 Jun 2002 15:13:48 -0400 (EDT) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA07965; Tue, 18 Jun 2002 15:12:24 -0400 (EDT) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA07940 for ; Tue, 18 Jun 2002 15:12:23 -0400 (EDT) Received: from wullbinkle.real.com (wullbinkle.real.com [207.188.22.31]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA01145 for ; Tue, 18 Jun 2002 15:11:44 -0400 (EDT) Received: from real.com (murrow2k1.real.com [207.188.7.41]) by wullbinkle.real.com (8.12.2/8.12.2) with ESMTP id g5IJAMKR030158; Tue, 18 Jun 2002 12:10:22 -0700 Received: from turnip ([172.23.103.232]) by real.com (8.12.2/8.12.2) with SMTP id g5IJAUMB006198; Tue, 18 Jun 2002 12:10:31 -0700 Message-Id: <3.0.32.20020618121042.00dbbbd8@mail.real.com> X-Sender: damonlan@mail.real.com X-Mailer: Windows Eudora Pro Version 3.0 (32) Date: Tue, 18 Jun 2002 12:10:43 -0700 To: Eddie Kohler From: Damon Lanphear Subject: Re: [dcp] Issues with adoption of DCCP for RTP applications Cc: dcp@ietf.org Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: dcp-admin@ietf.org Errors-To: dcp-admin@ietf.org X-Mailman-Version: 1.0 Precedence: bulk List-Id: Datagram Control Protocol X-BeenThere: dcp@ietf.org Eddie, At 09:03 AM 6/18/2002 -0700, Eddie Kohler wrote: >Will you be in Yokohama? I will be in Yokohama. >Summary: I think you're right -- the apparent redundancies are justifiable >-- yet we might want to reconcile redundancies between DCCP and RTP anyway. ... >All of these seem like second-level concerns. Assuming TFRC-like congestion >control, the "extra" overhead of RTP-over-DCCP compared to RTP-over-UDP can >be as low as 4 bytes per data packet. It might be useful to work together >on an optimized header combination for RTP-over-DCCP, if other people are >excited. But I'd like to support the unoptimized header combination too, >for simplicity's sake. An umoptimized header combination will yeild a more elegant design. It would be nice not to have us end up with an API that requires an extra system call per packet on both the sender or receiver to optionally discover the packet's sequence number, or forces a special DCCP framing of data passed to/from userspace. I am curious to see what the RTP crowd thinks about trading a 4 byte overhead for a simplified API to DCCP. I'll see what kind of discussion I can drum up on the RTP/AVT list. >Likewise, receiver reports in RTP might piggyback on DCCP's when possible. >In the TFRC case, RTP would turn on RTP-level receiver reports, while RTP >might use DCCP's acks for TCP-like congestion control, which has complete >ack information. The particular mechanism chosen for receiver reports might >be hidden from the application. (I'm not sure you could hide the sequence >number differences.) My personal thoughts on this issue are such that the sampling and interpretation of data in RTCP RR's is highly specialized to a particular problem domain. This means that RTCP RR's would have to be extended to support something like TFRC, incurring more overhead by virtue of the increased frequency and size of RTCP RR's. It would be optimal to let TFRC under DCCP handle the receiver reporting required of TFRC, and let RTCP stay constrained to its problem space of real-time metric reporting. _______________________________________________ dcp mailing list: dcp@ietf.org archives: https://www1.ietf.org/mailman/listinfo/dcp project: http://www.icir.org/kohler/dcp/ From daemon@optimus.ietf.org Tue Jun 18 15:29:59 2002 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA01794 for ; Tue, 18 Jun 2002 15:29:59 -0400 (EDT) Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id PAA08770 for dcp-archive@odin.ietf.org; Tue, 18 Jun 2002 15:30:37 -0400 (EDT) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA08492; Tue, 18 Jun 2002 15:29:13 -0400 (EDT) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA08456 for ; Tue, 18 Jun 2002 15:29:11 -0400 (EDT) Received: from wullbinkle.real.com (wullbinkle.real.com [207.188.22.31]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA01743 for ; Tue, 18 Jun 2002 15:28:31 -0400 (EDT) Received: from real.com (murrow2k1.real.com [207.188.7.41]) by wullbinkle.real.com (8.12.2/8.12.2) with ESMTP id g5IJSTKR031740 for ; Tue, 18 Jun 2002 12:28:29 -0700 Received: from turnip ([172.23.103.232]) by real.com (8.12.2/8.12.2) with SMTP id g5IJScMB019182 for ; Tue, 18 Jun 2002 12:28:38 -0700 Message-Id: <3.0.32.20020618122851.00e1d9f0@mail.real.com> X-Sender: damonlan@mail.real.com X-Mailer: Windows Eudora Pro Version 3.0 (32) Date: Tue, 18 Jun 2002 12:28:51 -0700 To: dcp@ietf.org From: Damon Lanphear Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Subject: [dcp] Status of API for DCCP ? Sender: dcp-admin@ietf.org Errors-To: dcp-admin@ietf.org X-Mailman-Version: 1.0 Precedence: bulk List-Id: Datagram Control Protocol X-BeenThere: dcp@ietf.org Section 11 of draft-kohler-dcp-03.txt, which pertains to the abstract API, is still TBD. I would like to learn what directions, if any, the protocol designers have taken with the API so that we might begin to discuss API issues prior to Yokohama. thanks, damon _______________________________________________ dcp mailing list: dcp@ietf.org archives: https://www1.ietf.org/mailman/listinfo/dcp project: http://www.icir.org/kohler/dcp/ From daemon@optimus.ietf.org Tue Jun 18 15:57:54 2002 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA02718 for ; Tue, 18 Jun 2002 15:57:54 -0400 (EDT) Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id PAA09919 for dcp-archive@odin.ietf.org; Tue, 18 Jun 2002 15:58:33 -0400 (EDT) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA09875; Tue, 18 Jun 2002 15:56:32 -0400 (EDT) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA09845 for ; Tue, 18 Jun 2002 15:56:30 -0400 (EDT) Received: from coyote.icir.org (coyote.icir.org [192.150.187.37]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA02645 for ; Tue, 18 Jun 2002 15:55:50 -0400 (EDT) Received: from coyote.icir.org (localhost [127.0.0.1]) by coyote.icir.org (8.11.6/8.11.3) with ESMTP id g5IJu9603142; Tue, 18 Jun 2002 12:56:09 -0700 (PDT) (envelope-from kohler@coyote.icir.org) Message-Id: <200206181956.g5IJu9603142@coyote.icir.org> To: Michael Tuexen cc: dcp@ietf.org Subject: Re: [dcp] dccp acronym In-Reply-To: Message from Michael Tuexen of "Sat, 08 Jun 2002 17:58:48 +0200." <9E6B62BA-7AF8-11D6-9BA0-0030654C1AB6@micmac.franken.de> Date: Tue, 18 Jun 2002 12:56:09 -0700 From: Eddie Kohler Sender: dcp-admin@ietf.org Errors-To: dcp-admin@ietf.org X-Mailman-Version: 1.0 Precedence: bulk List-Id: Datagram Control Protocol X-BeenThere: dcp@ietf.org > Unfortunately the acronym resolves to > Distributed Checksum Clearinghouse Protocol. So maybe DCP was > a better choice... Arrgh... We might be OK here. People were pretty against DCP at one of our meetings, because of the semi-homonym with TCP. But searching on the Web for "Distributed Checksum Clearinghouse Protocol" doesn't turn up any results. Furthermore, the Distributed Checksum Clearinghouse pages refer to "the DCC protocol", never "DCCP". Eddie _______________________________________________ dcp mailing list: dcp@ietf.org archives: https://www1.ietf.org/mailman/listinfo/dcp project: http://www.icir.org/kohler/dcp/ From daemon@optimus.ietf.org Tue Jun 18 19:12:26 2002 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA08046 for ; Tue, 18 Jun 2002 19:12:26 -0400 (EDT) Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id TAA23264 for dcp-archive@odin.ietf.org; Tue, 18 Jun 2002 19:13:06 -0400 (EDT) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id TAA23148; Tue, 18 Jun 2002 19:11:41 -0400 (EDT) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id TAA23115 for ; Tue, 18 Jun 2002 19:11:39 -0400 (EDT) Received: from cougar.icir.org (cougar.icir.org [192.150.187.76]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA07970 for ; Tue, 18 Jun 2002 19:10:56 -0400 (EDT) Received: from cougar.icir.org (localhost [127.0.0.1]) by cougar.icir.org (8.11.6/8.11.3) with ESMTP id g5INBWB33214; Tue, 18 Jun 2002 16:11:32 -0700 (PDT) (envelope-from floyd@cougar.icir.org) Message-Id: <200206182311.g5INBWB33214@cougar.icir.org> To: Sara Karlberg cc: dcp@ietf.org From: Sally Floyd Subject: Re: [dcp] Window counter Date: Tue, 18 Jun 2002 16:11:32 -0700 Sender: dcp-admin@ietf.org Errors-To: dcp-admin@ietf.org X-Mailman-Version: 1.0 Precedence: bulk List-Id: Datagram Control Protocol X-BeenThere: dcp@ietf.org Sara - My apologies for the very late reply. >As I understand it the purpose of the window counter option >(CCID 3) is to replace the RTT estimate. Basically the receiver needs to >know the RTT in order to report the current receive rate and to know >when to send feedback among other things. My question is how the window >counter option is to be used for this. This use of a coarse-grained counter that increments every quarter RTT in CCID 3 is largely to determine when multiple losses or marks belong to the same loss event. This is discussed in Section 8 of draft-padhye-dcp-ccid3-03.txt, and is discussed briefly in Section 3.2.1 of draft-ietf-tsvwg-tfrc-04.txt. The TFRC draft states that the receiver requires either the timestamp along with the sender's estimate of the RTT, or the coarse-grained counter, to determine when multiple losses belong to the same loss event. The DCCP/CCID 3 draft was changed to use the coarse-grained counter instead of the timestamp and the sender's estimate of the RTT. You are right that the receiver also needs an RTT estimate to set the feedback timer. With the new version of DCCP/CCID 3, the receiver will have to use the info in the coarse-grained counter to set the feedback timer. We need to add this to the DCCP/CCID 3 draft. The receiver reports the received rate X_recv in pkts per second, so this does not require the RTT estimate. >By the way, is it still recommended that the sender increases the window >counter by 4 once it receives a report of a congestion event? The current draft draft-padhye-dcp-ccid3-03.ps recommends the following: "When the sender receives an acknowledgement acknowledging a data packet with window counter i, the sender can increase its window counter, if necessary, so that subsequent data packets are sent with window counter values of at least i+4." This is still recommended. Many thanks, - Sally http://www.icir.org/floyd/ _______________________________________________ dcp mailing list: dcp@ietf.org archives: https://www1.ietf.org/mailman/listinfo/dcp project: http://www.icir.org/kohler/dcp/ From daemon@optimus.ietf.org Wed Jun 19 02:33:22 2002 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA09055 for ; Wed, 19 Jun 2002 02:33:22 -0400 (EDT) Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id CAA03296 for dcp-archive@odin.ietf.org; Wed, 19 Jun 2002 02:33:51 -0400 (EDT) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id CAA03248; Wed, 19 Jun 2002 02:32:16 -0400 (EDT) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id CAA03220 for ; Wed, 19 Jun 2002 02:32:14 -0400 (EDT) Received: from port.net (wroc.praxis.pl [217.11.138.250]) by ietf.org (8.9.1a/8.9.1a) with SMTP id CAA09018 for ; Wed, 19 Jun 2002 02:31:31 -0400 (EDT) Message-Id: <200206190631.CAA09018@ietf.org> From: "Farmgirl23663" To: X-Priority: 3 X-Mailer: The Bat! (v1.53d) Date: Wed, 19 Jun 2002 10:35:23 +0400 Mime-Version: 1.0 Content-Type: text/html; charset="ISO-8859-2" Status: R X-Status: N X-Set: gfsClhwi1ruj@8060 Subject: [dcp] Real ZOO web site, welcome! ID Sender: dcp-admin@ietf.org Errors-To: dcp-admin@ietf.org X-Mailman-Version: 1.0 Precedence: bulk List-Id: Datagram Control Protocol X-BeenThere: dcp@ietf.org The BEST zoo site on the @net!
Sex With Dogs
Horse Blow Jobs.
Snake Fuck.
REAL ANIMAL FUCKING!
100% HARDCORE!
ww1.only-beasts.com
unsub
Good luck, .

_______________________________________________ dcp mailing list: dcp@ietf.org archives: https://www1.ietf.org/mailman/listinfo/dcp project: http://www.icir.org/kohler/dcp/ From daemon@optimus.ietf.org Wed Jun 19 07:23:44 2002 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA13301 for ; Wed, 19 Jun 2002 07:23:44 -0400 (EDT) Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id HAA18329 for dcp-archive@odin.ietf.org; Wed, 19 Jun 2002 07:24:24 -0400 (EDT) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA18292; Wed, 19 Jun 2002 07:24:04 -0400 (EDT) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA18263 for ; Wed, 19 Jun 2002 07:24:02 -0400 (EDT) Received: from gorilla.mchh.siemens.de (gorilla.mchh.siemens.de [194.138.158.18]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA13294 for ; Wed, 19 Jun 2002 07:23:21 -0400 (EDT) Received: from moody.mchh.siemens.de (mail2.mchh.siemens.de [194.138.158.226]) by gorilla.mchh.siemens.de (8.9.3/8.9.3) with ESMTP id NAA06072; Wed, 19 Jun 2002 13:23:57 +0200 (MET DST) Received: from mchh247e.demchh201e.icn.siemens.de ([139.21.200.57]) by moody.mchh.siemens.de (8.9.1/8.9.1) with ESMTP id NAA16852; Wed, 19 Jun 2002 13:23:58 +0200 (MET DST) Received: by MCHH247E with Internet Mail Service (5.5.2653.19) id ; Wed, 19 Jun 2002 13:23:38 +0200 Message-ID: From: Tuexen Michael To: "'Eddie Kohler'" Cc: dcp@ietf.org Subject: RE: [dcp] dccp acronym Date: Wed, 19 Jun 2002 13:23:36 +0200 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="ISO-8859-1" Sender: dcp-admin@ietf.org Errors-To: dcp-admin@ietf.org X-Mailman-Version: 1.0 Precedence: bulk List-Id: Datagram Control Protocol X-BeenThere: dcp@ietf.org Ok, then it is a problem only when you want DCCP to be integrated into Ethereal (under that name). Sorry, I did not search the web. Best regards Michael Michael Tuexen Tel.: +49 89 722 47210 Siemens AG Fax: +49 89 722 48212 ICN WN CC SE 7 e-Mail: Michael.Tuexen@icn.siemens.de > -----Original Message----- > From: Eddie Kohler [mailto:kohler@icir.org] > Sent: Tuesday, June 18, 2002 9:56 PM > To: Michael Tuexen > Cc: dcp@ietf.org > Subject: Re: [dcp] dccp acronym > > > > Unfortunately the acronym resolves to > > Distributed Checksum Clearinghouse Protocol. So maybe DCP was > > a better choice... > > Arrgh... > > We might be OK here. People were pretty against DCP at one of > our meetings, > because of the semi-homonym with TCP. But searching on the Web for > "Distributed Checksum Clearinghouse Protocol" doesn't turn up > any results. > Furthermore, the Distributed Checksum Clearinghouse pages > refer to "the DCC > protocol", never "DCCP". > > Eddie > > _______________________________________________ > dcp mailing list: dcp@ietf.org > archives: https://www1.ietf.org/mailman/listinfo/dcp > project: http://www.icir.org/kohler/dcp/ > _______________________________________________ dcp mailing list: dcp@ietf.org archives: https://www1.ietf.org/mailman/listinfo/dcp project: http://www.icir.org/kohler/dcp/ From daemon@optimus.ietf.org Thu Jun 20 15:10:51 2002 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA10901 for ; Thu, 20 Jun 2002 15:10:51 -0400 (EDT) Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id PAA14082 for dcp-archive@odin.ietf.org; Thu, 20 Jun 2002 15:11:32 -0400 (EDT) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA14066; Thu, 20 Jun 2002 15:11:27 -0400 (EDT) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA14035 for ; Thu, 20 Jun 2002 15:11:25 -0400 (EDT) Received: from auds952.usa.alcatel.com (auds952.usa.alcatel.com [143.209.238.7]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA10892 for ; Thu, 20 Jun 2002 15:10:43 -0400 (EDT) Received: from alcatel.com (localhost [127.0.0.1]) by auds952.usa.alcatel.com (8.10.2/8.10.2) with ESMTP id g5KJAkh07355; Thu, 20 Jun 2002 14:10:46 -0500 (CDT) Message-ID: <3D1228E1.A5816439@alcatel.com> Date: Thu, 20 Jun 2002 14:11:29 -0500 From: Alex Audu X-Mailer: Mozilla 4.72 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: Mark Handley , dcp@ietf.org References: <11341.1020877125@aardvark.icir.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Subject: [dcp] Protocol Version number Sender: dcp-admin@ietf.org Errors-To: dcp-admin@ietf.org X-Mailman-Version: 1.0 Precedence: bulk List-Id: Datagram Control Protocol X-BeenThere: dcp@ietf.org Content-Transfer-Encoding: 7bit Eddie, Mark and Sally, I noticed the DCP header portion is mising a protocol version field, though section 4.6 makes reference to "The version of DCCP". Can we add a version field in the protocol header? Regards, Alex. _______________________________________________ dcp mailing list: dcp@ietf.org archives: https://www1.ietf.org/mailman/listinfo/dcp project: http://www.icir.org/kohler/dcp/ From daemon@optimus.ietf.org Thu Jun 20 15:21:59 2002 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA11048 for ; Thu, 20 Jun 2002 15:21:59 -0400 (EDT) Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id PAA14517 for dcp-archive@odin.ietf.org; Thu, 20 Jun 2002 15:22:38 -0400 (EDT) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA14498; Thu, 20 Jun 2002 15:22:31 -0400 (EDT) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA14463 for ; Thu, 20 Jun 2002 15:22:29 -0400 (EDT) Received: from aardvark.icir.org (aardvark.icir.org [192.150.187.20]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA11042 for ; Thu, 20 Jun 2002 15:21:48 -0400 (EDT) Received: from aardvark.icir.org (localhost [127.0.0.1]) by aardvark.icir.org (8.11.6/8.11.3) with ESMTP id g5KJMPk82954; Thu, 20 Jun 2002 12:22:25 -0700 (PDT) (envelope-from mjh@aardvark.icir.org) From: Mark Handley X-Organisation: ICIR To: Alex Audu cc: dcp@ietf.org Subject: Re: [dcp] Protocol Version number In-reply-to: Your message of "Thu, 20 Jun 2002 14:11:29 CDT." <3D1228E1.A5816439@alcatel.com> Date: Thu, 20 Jun 2002 12:22:25 -0700 Message-ID: <82952.1024600945@aardvark.icir.org> Sender: dcp-admin@ietf.org Errors-To: dcp-admin@ietf.org X-Mailman-Version: 1.0 Precedence: bulk List-Id: Datagram Control Protocol X-BeenThere: dcp@ietf.org >I noticed the DCP header portion is mising a protocol version field, >though section 4.6 makes reference >to "The version of DCCP". Can we add a version field in the protocol >header? It seems to be a waste of bits. There are a number of ways to evolve protocols. - If the packet formats need to change enough so that receivers or middleboxes would be confused, then you might as well use a different IP protocol number. - If the change is minor, then it's most easily done in a backward compatible way by adding a feature that is negotiated. - If the change is not so minor, a non-negotiable feature could be sent in the DCP request. - Finally, there are four bits in the DCP common header that are marked as MUST BE ZERO for this version of DCP. If we decide at some future point that we really need a version number, between one and four of these bits can be designated as a version number field. Neither TCP nor UDP has a version field. I think time has shown this to be a reasonable decision. Cheers, Mark _______________________________________________ dcp mailing list: dcp@ietf.org archives: https://www1.ietf.org/mailman/listinfo/dcp project: http://www.icir.org/kohler/dcp/ From daemon@ns.ietf.org Sat Jun 22 21:34:58 2002 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA07505 for ; Sat, 22 Jun 2002 21:34:57 -0400 (EDT) Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id VAA11943 for dcp-archive@odin.ietf.org; Sat, 22 Jun 2002 21:35:39 -0400 (EDT) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id VAA11929; Sat, 22 Jun 2002 21:35:25 -0400 (EDT) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id VAA11900 for ; Sat, 22 Jun 2002 21:35:24 -0400 (EDT) Received: from localhost.com ([61.174.192.218]) by ietf.org (8.9.1a/8.9.1a) with SMTP id VAA07499 for ; Sat, 22 Jun 2002 21:34:35 -0400 (EDT) From: targetemailextractor@btamail.net.cn Message-Id: <200206230134.VAA07499@ietf.org> Reply-To: targetemailextractor@btamail.net.cn To: dcp@ietf.org Date: Sun, 23 Jun 2002 09:35:16 +0800 X-Mailer: QuickSender 1.05 MIME-Version: 1.0 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Content-Transfer-Encoding: quoted-printable Subject: [dcp] ADV: Direct email blaster, email addresses extractor, maillist verify, maillist manager........... Sender: dcp-admin@ietf.org Errors-To: dcp-admin@ietf.org X-Mailman-Version: 1.0 Precedence: bulk List-Id: Datagram Control Protocol X-BeenThere: dcp@ietf.org Content-Transfer-Encoding: quoted-printable =3CHTML=3E=3CHEAD=3E =3CSTYLE=3E=3C=2FSTYLE=3E =3C=2FHEAD=3E =3CBODY bgColor=3D#ffffff=3E =3CDIV=3E=3CFONT size=3D2=3E =3CDIV=3E=3CFONT face=3DArial=3E =3B=3C=2FFONT=3E =3C=2FDIV=3E =3CDIV=3E =3B=3C=2FDIV=3E =3CDIV=3E=3CSTRONG=3E=3CFONT color=3D#ff0080 face=3DArial size=3D4=3EDirect Email Blaster=3C=2FFONT=3E=3C=2FSTRONG=3E =3C=2FDIV=3E=3CFONT size=3D2=3E =3CP=3E=3CFONT face=3DArial=3E=3CB=3E=3CFONT color=3D#006600=3E=3CI=3EThe program will send mail at the rate of over 1=2C 000 e-mails per minute=2E =3B=3C=2FI=3E=3C=2FFONT=3E=3CBR=3ELegal and Fast sending bulk emails =3B=3CBR=3E=3CFONT color=3D#006600=3E=3CI=3EBuilt in SMTP server =3B=3C=2FI=3E=3C=2FFONT=3E=3CBR=3EHave Return Path =3B=3CBR=3ECan Check Mail Address =3B=3CBR=3E=3CFONT color=3D#006600=3E=3CI=3EMake Error Send Address List=28 Remove or Send Again=29 =3B=3C=2FI=3E=3C=2FFONT=3E=3CBR=3ESupport multi-threads=2E =3B=3CBR=3ESupport multi-smtp servers=2E =3B=3CBR=3EManages your opt-in E-Mail Lists =3B=3CBR=3EOffers an easy-to-use interface! =3B=3CBR=3EEasy to configure and use =3B=3C=2FB=3E=3C=2FFONT=3E=3C=2FP=3E =3CP=3E=3CFONT face=3DArial=3E=3CA href=3D=22http=3A=2F=2Fwww=2Ewldinfo=2Ecom=2Fbj=5Fdownload=2Fedeb=5Fset=2Ezip=22=3E=3CSTRONG=3EDownload Now=3C=2FSTRONG=3E=3C=2FA=3E=3C=2FFONT=3E=3C=2FP=3E =3CP=3E=3CSTRONG=3E=3CFONT color=3D#ff0080 face=3DArial size=3D4=3EMaillist Verify=3C=2FFONT=3E=3C=2FSTRONG=3E=3C=2FP=3E =3CP=3E=3CFONT face=3DArial=3EMaillist Verify is intended for e-mail addresses and mail lists verifying=2E The main task is to determine which of addresses in the mail list are dead=2E The program is oriented=2C basically=2C on programmers which have their own mail lists to inform their users about new versions of their programs=2E=3C=2FFONT=3E=3C=2FP=3E =3CP=3E=3CFONT face=3DArial=3EThe program works on the same algorithm as ISP mail systems do=2E Mail servers addresses for specified address are extracted from DNS=2E The program tries to connect with found SMTP-servers and simulates the sending of message=2E It does not come to the message =3CNOBR=3Esending ‿=3B=2FNOBR>=3B EMV disconnect as soon as mail server informs does this address exist or not=2E EMV can find=3C=2FNOBR=3E=3C=2FFONT=3E=3C=2FP=3E =3CP=3E=3CFONT face=3DArial=3E=3CNOBR=3E =3Babout 90% of dead addresses ‿=3B=2FNOBR>=3B some mail systems receive all messages and only then see their =3B=3C=2FNOBR=3E=3C=2FFONT=3E=3C=2FP=3E =3CP=3E=3CFONT face=3DArial=3E=3CNOBR=3Eaddresses and if the address is dead send the message back with remark about it=2E=3C=2FNOBR=3E=3C=2FFONT=3E=3C=2FP=3E=3CNOBR=3E =3CP=3E=3CA href=3D=22http=3A=2F=2Fwww=2Ewldinfo=2Ecom=2Fbj=5Fdownload=2Fbemv=5Fset=2Ezip=22=3E=3CSTRONG=3E=3CFONT face=3DArial size=3D3=3EDownload Now=3C=2FFONT=3E=3C=2FSTRONG=3E=3C=2FA=3E=3C=2FP=3E =3CP=3E=3CSTRONG=3E=3CFONT color=3D#ff0080 face=3DArial size=3D4=3EExpress Email Blaster =3B=3C=2FFONT=3E=3C=2FSTRONG=3E=3C=2FP=3E =3CP=3E=3CFONT face=3DArial=3EExpress Email Blaster =3B is a very fast=2C powerful yet simple to use email sender=2E Utilizing multiple threads=2Fconnections=3C=2FFONT=3E=3C=2FP=3E =3CP=3E=3CFONT face=3DArial=3E =3Band multiple SMTP servers your emails will be sent out fast and easily=2E There are User Information=2C Attach Files=2C =3B=3C=2FFONT=3E=3C=2FP=3E =3CP=3E=3CFONT face=3DArial=3EAddress and Mail Logs four tabbed area for the E-mails details for sending=2E About 25 SMTP servers come with the =3B=3C=2FFONT=3E=3C=2FP=3E =3CP=3E=3CFONT face=3DArial=3Edemo version=2C and users may Add and Delete SMTP servers=2E About =3CFONT color=3D#008000=3E=3CB=3E60=2C000=3C=2FB=3E=3C=2FFONT=3E E-mails will be sent out per hour=2E=22=3C=2FFONT=3E=3C=2FP=3E =3CP=3E=3CSTRONG=3E=3CA href=3D=22http=3A=2F=2Fwww=2Ewldinfo=2Ecom=2Fbj=5Fdownload=2Fbeeb=5Fset=2Ezip=22=3E=3CFONT face=3DArial size=3D3=3EDownload Now=3C=2FFONT=3E=3C=2FA=3E=3C=2FSTRONG=3E=3C=2FP=3E =3CP=3E=3CSTRONG=3E=3CFONT color=3D#ff0080 face=3DArial size=3D4=3EExpress Email Address Extractor=3C=2FFONT=3E=3C=2FSTRONG=3E=3C=2FP=3E=3CFONT size=3D4=3E =3CP=3E=3CFONT color=3D#008000 size=3D3=3EThis program is the most efficient=2C easy to use email address collector available on the =3C=2FFONT=3E=3C=2FP=3E =3CP=3E=3CFONT face=3DArial=3E=3CFONT color=3D#008000 size=3D3=3E =3Binternet! =3C=2FFONT=3E=3CFONT color=3D#000000 size=3D3=3EBeijing Express Email Address Extractor =28ExpressEAE=29 is designed to extract=3C=2FFONT=3E=3C=2FFONT=3E=3C=2FP=3E =3CP=3E=3CFONT color=3D#000000 size=3D3=3E =3Be-mail addresses from web-pages on the Internet =28using HTTP protocols=29 =2EExpressEAE=3C=2FFONT=3E=3C=2FP=3E =3CP=3E=3CFONT color=3D#000000 size=3D3=3E =3Bsupports operation through many proxy-server and works very fast=2C as it is able of =3B=3C=2FFONT=3E=3C=2FP=3E =3CP=3E=3CFONT color=3D#000000 size=3D3=3Eloading several pages simultaneously=2C and requires very few resources=2E=3C=2FFONT=3E=3C=2FP=3E =3CP=3E=3CFONT color=3D#000000 face=3DArial=3E=3CFONT size=3D3=3EWith it=2C you will be able to=3C=2FFONT=3E=3CFONT size=3D2=3E =3C=2FFONT=3E=3CFONT size=3D3=3Euse targeted searches to crawl the world wide web=2C extracting =3B=3C=2FFONT=3E=3C=2FFONT=3E =3CP=3E=3CFONT color=3D#000000 face=3DArial size=3D3=3Ethousands of clean=2C fresh email addresses=2E Ably Email address Extractor is unlike other =3B=3C=2FFONT=3E =3CP=3E=3CFONT color=3D#000000 face=3DArial size=3D3=3Eaddress collecting programs=2C which limit you to one or two search engines and are unable=3C=2FFONT=3E =3CP=3E=3CFONT color=3D#000000 face=3DArial size=3D3=3E =3Bto do auto searches HUGE address=2E Most of them collect a high percentage of incomplete=2C =3B=3C=2FFONT=3E =3CP=3E=3CFONT color=3D#000000 face=3DArial size=3D3=3Eunusable addresses which will cause you serious problems when using them in a mailing=2E =3B=3C=2FFONT=3E =3CUL=3E =3CLI=3E=3CFONT color=3D#008000 face=3DArial size=3D3=3EEasier to learn and use than any other email address collector program available=2E=3C=2FFONT=3E =3CLI=3E=3CFONT color=3D#008000 face=3DArial size=3D3=3EAccesses eight search engines =3B=3C=2FFONT=3E =3CLI=3E=3CFONT color=3D#008000 face=3DArial size=3D3=3EAdd your own URLs to the list to be searched=3C=2FFONT=3E =3CLI=3E=3CFONT face=3DArial size=3D3=3E=3CFONT color=3D#008000=3ESupports operation through =3C=2FFONT=3E=3CFONT color=3D#ff00ff=3Ea lot of=3C=2FFONT=3E=3CFONT color=3D#008000=3E proxy-server and works very fast =28HTTP Proxy=29=3C=2FFONT=3E=3C=2FFONT=3E =3CLI=3E=3CFONT color=3D#008000 face=3DArial size=3D3=3EAble of loading several pages simultaneously=3C=2FFONT=3E =3CLI=3E=3CFONT color=3D#008000 face=3DArial size=3D3=3ERequires very few resources=3C=2FFONT=3E =3CLI=3E=3CFONT color=3D#008000 face=3DArial size=3D3=3ETimeout feature allows user to limit the amount of time crawling in dead sites and traps=2E=3C=2FFONT=3E =3CLI=3E=3CFONT face=3DArial size=3D3=3E=3CFONT color=3D#008000=3EEasy to make =3C=2FFONT=3E=3CFONT color=3D#ff00ff=3EHuge=3C=2FFONT=3E=3CFONT color=3D#008000=3E address list=3C=2FFONT=3E=3C=2FFONT=3E =3CLI=3E=3CFONT color=3D#008000 face=3DArial size=3D3=3EPause=2Fcontinue extraction at any time=2E=3C=2FFONT=3E =3CLI=3E=3CFONT color=3D#008000 face=3DArial size=3D3=3EAuto connection to the Internet=3C=2FFONT=3E =3C=2FLI=3E=3C=2FUL=3E =3CDIV=3E=3CSTRONG=3E=3CA href=3D=22http=3A=2F=2Fwww=2Ewldinfo=2Ecom=2Fbj=5Fdownload=2Feeae=5Fset=2Ezip=22=3E=3CFONT color=3D#008000 face=3DArial size=3D3=3EDownload Now=3C=2FFONT=3E=3C=2FA=3E=3C=2FSTRONG=3E =3C=2FDIV=3E =3CDIV=3E=3CSTRONG=3E=3CFONT color=3D#ff0080 face=3DArial=3EExpress Email Address Downloader=3C=2FFONT=3E=3C=2FSTRONG=3E =3C=2FDIV=3E =3CUL=3E =3CLI=3E=3CFONT face=3DArial=3E=3CSTRONG=3E=3CFONT color=3D#006600 size=3D2=3EExpressEAD =3B =3C=2FFONT=3E=3CFONT color=3D#000000 size=3D2=3Eis a 32 bit Windows Program for e-mail marketing=2E It is intended for easy and convenient=3C=2FFONT=3E=3C=2FSTRONG=3E=3C=2FFONT=3E =3CLI=3E=3CFONT face=3DArial=3E=3CSTRONG=3E=3CFONT color=3D#000000 size=3D2=3E =3Bsearch large e-mail address lists from mail servers=2E The program can be operated on =3B=3C=2FFONT=3E=3C=2FSTRONG=3E=3C=2FFONT=3E =3CLI=3E=3CFONT face=3DArial=3E=3CSTRONG=3E=3CFONT color=3D#000000 size=3D2=3EWindows 95=2F98=2FME=2F2000 and NT=2E=3C=2FFONT=3E=3C=2FSTRONG=3E=3C=2FFONT=3E =3CLI=3E=3CFONT face=3DArial=3E=3CSTRONG=3E=3CFONT color=3D#006600 size=3D2=3EExpressEAD =3B =3C=2FFONT=3E=3CFONT color=3D#000000 size=3D2=3Esupport multi-threads =28up to 1024 connections=29=2E=3C=2FFONT=3E=3C=2FSTRONG=3E=3C=2FFONT=3E =3CLI=3E=3CFONT face=3DArial=3E=3CSTRONG=3E=3CFONT color=3D#006600 size=3D2=3EExpressEAD =3B =3C=2FFONT=3E=3CFONT color=3D#000000 size=3D2=3Ehas the ability =3B to reconnect to the mail server if the server has disconnected and =3B=3C=2FFONT=3E=3C=2FSTRONG=3E=3C=2FFONT=3E =3CLI=3E=3CFONT face=3DArial=3E=3CSTRONG=3E=3CFONT color=3D#000000 size=3D2=3Econtinue the searching at the point where it has been interrupted=2E=3C=2FFONT=3E=3C=2FSTRONG=3E=3C=2FFONT=3E =3CLI=3E=3CFONT face=3DArial=3E=3CSTRONG=3E=3CFONT color=3D#006600 size=3D2=3EExpressEAD =3B =3C=2FFONT=3E=3CFONT color=3D#000000 size=3D2=3Ehas an ergonomic interface that is easy to set up and simple to use=2E=3C=2FFONT=3E=3C=2FSTRONG=3E=3C=2FFONT=3E =3C=2FLI=3E=3C=2FUL=3E =3CDIV=3E=3CFONT face=3DArial=3E =3B=3C=2FFONT=3E =3C=2FDIV=3E =3CP=3E=3CFONT face=3DArial=3E=3CSTRONG=3E=3CFONT color=3D#008000 face=3DArial size=3D4=3EFeatures=3A=3C=2FFONT=3E=3C=2FSTRONG=3E=3C=2FFONT=3E =3CUL type=3Ddisc=3E =3CLI=3E=3CFONT face=3DArial=3E=3CSTRONG=3E=3CFONT face=3DArial size=3D2=3Esupport multi-threads=2E=3C=2FFONT=3E=3C=2FSTRONG=3E=3C=2FFONT=3E =3CLI=3E=3CFONT face=3DArial=3E=3CSTRONG=3E=3CFONT face=3DArial size=3D2=3Eauto get smtp server address=2Csupport multi-smtp servers=2E=3C=2FFONT=3E=3C=2FSTRONG=3E=3C=2FFONT=3E =3CLI=3E=3CFONT face=3DArial=3E=3CSTRONG=3E=3CFONT face=3DArial size=3D2=3Eauto save =3B E-Mail Lists=3C=2FFONT=3E=3C=2FSTRONG=3E=3C=2FFONT=3E =3CLI=3E=3CFONT face=3DArial=3E=3CSTRONG=3E=3CFONT face=3DArial size=3D2=3Eoffers an easy-to-use interface!=3C=2FFONT=3E=3C=2FSTRONG=3E=3C=2FFONT=3E =3C=2FLI=3E=3C=2FUL=3E =3CDIV=3E=3CSTRONG=3E=3CA href=3D=22http=3A=2F=2Fwww=2Ewldinfo=2Ecom=2Fbj=5Fdownload=2Feead=5Fset=2Ezip=22=3E=3CFONT color=3D#008000 face=3DArial size=3D3=3EDownload Now=3C=2FFONT=3E=3C=2FA=3E=3C=2FSTRONG=3E =3C=2FDIV=3E =3CDIV=3E=3CFONT face=3DArial=3E =3B=3C=2FFONT=3E =3C=2FDIV=3E =3CDIV=3E=3CSTRONG=3E=3CFONT color=3D#ff0080 face=3DArial=3EExpress Maillist Manager=3C=2FFONT=3E=3C=2FSTRONG=3E =3C=2FDIV=3E =3CDIV=3E=3CFONT face=3DArial=3E =3B=3C=2FFONT=3E =3C=2FDIV=3E =3CDIV=3E=3CFONT size=3D2=3E =3CP=3E=3CFONT face=3DArial=3E=3CFONT color=3Dblack size=3D3=3EThis program was designed to be a complement to the =3C=2FFONT=3E=3CFONT color=3D#800080 size=3D3=3EDirect Email Blaster =3B =3C=2FFONT=3E=3CFONT color=3Dblack size=3D3=3Eand =3C=2FFONT=3E=3CFONT color=3D#800080 size=3D3=3EEmail Blaster =3C=2FFONT=3E=3C=2FFONT=3E=3C=2FP=3E =3CP=3E=3CFONT face=3DArial=3E=3CFONT color=3Dblack size=3D3=3Esuite of bulk email software programs=2E Its purpose is to organize your email lists in order to be more =3B=3C=2FFONT=3E=3C=2FFONT=3E=3C=2FP=3E =3CP=3E=3CFONT face=3DArial=3E=3CFONT color=3Dblack size=3D3=3Eeffective with your email marketing campaign=2E Some of its features include=3A=3C=2FFONT=3E=3C=2FFONT=3E=3C=2FP=3E =3CP=3E=3CB=3E=3CFONT color=3D#008000 face=3DArial=3E=3CFONT size=3D3=3E‿=3BCombine several lists into one file=2E=3C=2FFONT=3E=3CBR=3E=3CFONT size=3D3=3E‿=3BSplit up larger lists to make them more manageable=2E=3C=2FFONT=3E=3CBR=3E=3CFONT size=3D3=3E‿=3BRemove addresses from file=2E=3C=2FFONT=3E=3CBR=3E=3CFONT size=3D3=3E‿=3BManual editing=2C adding=2C and deleting of addresses=2E=3C=2FFONT=3E=3CBR=3E=3CFONT size=3D3=3E‿=3BAbility to auto clean lists=2C that is=2C remove any duplicate or unwanted addresses=2E=3C=2FFONT=3E=3CBR=3E=3CFONT size=3D3=3E‿=3BMaintain all your address lists within the program so you no =3B longer need to keep all your=3C=2FFONT=3E=3C=2FFONT=3E=3C=2FB=3E=3C=2FP=3E =3CP=3E=3CB=3E=3CFONT color=3D#008000 face=3DArial size=3D3=3E =3Blists saved as separate text files=2E=3C=2FFONT=3E=3C=2FB=3E=3C=2FP=3E =3CP=3E=3CSTRONG=3E=3CA href=3D=22http=3A=2F=2Fwww=2Ewldinfo=2Ecom=2Fbj=5Fdownload=2Fbemm=5Fset=2Ezip=22=3E=3CFONT color=3D#008000 face=3DArial size=3D3=3EDownload Now=3C=2FFONT=3E=3C=2FA=3E=3C=2FSTRONG=3E=3C=2FP=3E =3CP=3E=3CFONT face=3DArial=3E =3B=3C=2FFONT=3E=3C=2FP=3E =3CP=3E =3B=3C=2FP=3E =3CDIV=3E=3CFONT face=3DArial=3Eif you want to remove your email=2C please send email to =3CA href=3D=22mailto=3Atargetemailremoval=40btamail=2Enet=2Ecn=22=3Etargetemailremoval=40btamail=2Enet=2Ecn=3C=2FA=3E=3C=2FFONT=3E =3C=2FDIV=3E =3CDIV=3E=3CFONT face=3DArial=3E =3B=3C=2FFONT=3E =3C=2FDIV=3E =3CDIV=3E=3CFONT face=3DArial=3E =3B=3C=2FFONT=3E =3C=2FDIV=3E =3CDIV=3E =3B=3C=2FDIV=3E=3C=2FFONT=3E=3C=2FDIV=3E=3C=2FFONT=3E=3C=2FNOBR=3E=3C=2FFONT=3E=3C=2FFONT=3E=3C=2FDIV=3E=3C=2FBODY=3E=3C=2FHTML=3E _______________________________________________ dcp mailing list: dcp@ietf.org archives: https://www1.ietf.org/mailman/listinfo/dcp project: http://www.icir.org/kohler/dcp/ From daemon@optimus.ietf.org Mon Jun 24 12:04:38 2002 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA14414 for ; Mon, 24 Jun 2002 12:04:38 -0400 (EDT) Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id MAA24883 for dcp-archive@odin.ietf.org; Mon, 24 Jun 2002 12:05:20 -0400 (EDT) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA24872; Mon, 24 Jun 2002 12:05:10 -0400 (EDT) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA24839 for ; Mon, 24 Jun 2002 12:05:03 -0400 (EDT) Received: from dinaras.cnri.reston.va.us (host-4-33.cnri.reston.va.us [10.27.4.33]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA14402; Mon, 24 Jun 2002 12:04:17 -0400 (EDT) Message-Id: <5.1.0.14.2.20020624121654.01fbfbc0@odin> X-Sender: dinaras@odin X-Mailer: QUALCOMM Windows Eudora Version 5.1 X-Priority: 1 (Highest) Date: Mon, 24 Jun 2002 12:17:13 -0400 To: Aaron Falk , agenda@ietf.org From: Dinara Suleymanova Cc: Allison Mankin , Scott Bradner , dcp@ietf.org In-Reply-To: <5.1.0.14.2.20020611133403.02787c00@odin> References: <35980000.1023483418@nit.isi.edu> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Subject: [dcp] Re: request for a wg slot in Yokohama for DCCP Sender: dcp-admin@ietf.org Errors-To: dcp-admin@ietf.org X-Mailman-Version: 1.0 Precedence: bulk List-Id: Datagram Control Protocol X-BeenThere: dcp@ietf.org Please provide the agenda of this group as soon as possible. At 01:35 PM 6/11/02 -0400, Dinara Suleymanova wrote: >Unless this is not a WG, I need AD approval. ADs, please approve or not >approve it. > >At 01:56 PM 6/7/02 -0700, Aaron Falk wrote: >>Hi- >> >>DCCP (formerly known as DCP) is not yet a working group but we expect >>that our charter will be approved in time to meet in Yokohama. Here are >>the particulars of our request: >> >> >>> >>>You MUST provide the following information before the meeting will be >>>scheduled: >>> >>> a. Working Group or BOF full name with acronym in brackets: >> >>Datagram Congestion Control Protocol [dccp] >> >> >>> b. AREA under which Working Group or BOF appears: >> >>Transport Area >> >>> c. CONFLICTS you wish to avoid, please be as specific as possible: >> >> >>Other Transport area mtgs in general >>OPES, TSVWG, RMT, ForCES, PIM, IDR, IDMR >> >>> d. Expected Attendance (use figures from the previous meeting): >> >>fairly large, 100+ >> >>> e. Special requests (i.e. multicast): >> >>none >> >>> f. Number of slots: >> >>one slot >> >>> g. Length of slot: >> >>2+ hours >> > > _______________________________________________ dcp mailing list: dcp@ietf.org archives: https://www1.ietf.org/mailman/listinfo/dcp project: http://www.icir.org/kohler/dcp/ From daemon@optimus.ietf.org Mon Jun 24 13:09:08 2002 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA18184 for ; Mon, 24 Jun 2002 13:09:08 -0400 (EDT) Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id NAA28313 for dcp-archive@odin.ietf.org; Mon, 24 Jun 2002 13:09:50 -0400 (EDT) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA28304; Mon, 24 Jun 2002 13:09:45 -0400 (EDT) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA28270 for ; Mon, 24 Jun 2002 13:09:43 -0400 (EDT) Received: from nit.isi.edu (nit.isi.edu [128.9.160.116]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA18161 for ; Mon, 24 Jun 2002 13:08:59 -0400 (EDT) Received: from nit.isi.edu (nit.isi.edu [128.9.160.116]) by nit.isi.edu (8.11.6/8.11.6) with ESMTP id g5OH9fo28454; Mon, 24 Jun 2002 10:09:41 -0700 Date: Mon, 24 Jun 2002 10:09:41 -0700 From: Aaron Falk To: dcp@ietf.org cc: Allison Mankin , Scott Bradner , Eddie Kohler Message-ID: <6550000.1024938581@nit.isi.edu> X-Mailer: Mulberry/2.2.1 (Linux/x86) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit Subject: [dcp] draft dccp agenda Sender: dcp-admin@ietf.org Errors-To: dcp-admin@ietf.org X-Mailman-Version: 1.0 Precedence: bulk List-Id: Datagram Control Protocol X-BeenThere: dcp@ietf.org Content-Transfer-Encoding: 7bit Here's what I have for an agenda to discuss in Yokohama. Have I missed anything? 0. agenda bashing (falk) 1. charter review (falk) 2. significant changes in spec (kohler) 3. open issues (kohler, summarizing from list) 4. implementation reports 5. adjourn Regarding 4., if you'd like some time to discuss your dccp implementation, you need to send a note with background to the mail list *first*. This way we can use the meeting time to discuss issues and problems, rather than introductory material. --aaron _______________________________________________ dcp mailing list: dcp@ietf.org archives: https://www1.ietf.org/mailman/listinfo/dcp project: http://www.icir.org/kohler/dcp/ From daemon@optimus.ietf.org Tue Jun 25 03:26:10 2002 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA25070 for ; Tue, 25 Jun 2002 03:26:10 -0400 (EDT) Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id DAA22080 for dcp-archive@odin.ietf.org; Tue, 25 Jun 2002 03:26:53 -0400 (EDT) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA22070; Tue, 25 Jun 2002 03:26:46 -0400 (EDT) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA22036 for ; Tue, 25 Jun 2002 03:26:44 -0400 (EDT) Received: from albatross.wise.edt.ericsson.se (albatross-ext.wise.edt.ericsson.se [193.180.251.49]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA25066 for ; Tue, 25 Jun 2002 03:26:01 -0400 (EDT) Received: from mbb5.ericsson.se (mbb5.ericsson.se [136.225.151.210]) by albatross.wise.edt.ericsson.se (8.12.1/8.12.1/WIREfire-1.4) with ESMTP id g5P7QhrU028441 for ; Tue, 25 Jun 2002 09:26:43 +0200 (MEST) Received: from era.ericsson.se (research-nnng7k.ki.sw.ericsson.se [147.214.34.108]) by mbb1.ericsson.se (PMDF V5.2-29 #39352) with ESMTP id <0GY90067I3CJDO@mbb1.ericsson.se> for dcp@ietf.org; Tue, 25 Jun 2002 09:26:43 +0200 (MET DST) Date: Tue, 25 Jun 2002 09:26:43 +0200 From: Magnus Westerlund Subject: Re: [dcp] draft dccp agenda To: Aaron Falk Cc: dcp@ietf.org, Allison Mankin , Scott Bradner , Eddie Kohler Message-id: <3D181B33.7030004@era.ericsson.se> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=us-ascii Content-transfer-encoding: 7bit User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.4) Gecko/20011128 Netscape6/6.2.1 X-Accept-Language: en-us References: <6550000.1024938581@nit.isi.edu> Content-Transfer-Encoding: 7bit Sender: dcp-admin@ietf.org Errors-To: dcp-admin@ietf.org X-Mailman-Version: 1.0 Precedence: bulk List-Id: Datagram Control Protocol X-BeenThere: dcp@ietf.org Content-Transfer-Encoding: 7bit Hi Aaron, Shouldn't there be some time for discussing requirements on DCCP? I would also like to see a presentation from Kohler about what requirements they have seen and address by the current proposal. Regards Magnus Aaron Falk wrote: > Here's what I have for an agenda to discuss in Yokohama. Have I > missed anything? > > > 0. agenda bashing (falk) > 1. charter review (falk) > 2. significant changes in spec (kohler) > 3. open issues (kohler, summarizing from list) > 4. implementation reports > 5. adjourn > > > Regarding 4., if you'd like some time to discuss your dccp > implementation, you need to send a note with background to the mail > list *first*. This way we can use the meeting time to discuss issues > and problems, rather than introductory material. > > --aaron > > _______________________________________________ > dcp mailing list: dcp@ietf.org > archives: https://www1.ietf.org/mailman/listinfo/dcp > project: http://www.icir.org/kohler/dcp/ > -- Magnus Westerlund Multimedia Technologies, Ericsson Research ERA/TVA/A ---------------------------------------------------------------------- Ericsson AB | Phone +46 8 4048287 Torshamsgatan 23 | Fax +46 8 7575550 S-164 80 Stockholm, Sweden | mailto: magnus.westerlund@era.ericsson.se _______________________________________________ dcp mailing list: dcp@ietf.org archives: https://www1.ietf.org/mailman/listinfo/dcp project: http://www.icir.org/kohler/dcp/ From daemon@ns.ietf.org Tue Jun 25 18:19:49 2002 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA01487 for ; Tue, 25 Jun 2002 18:19:48 -0400 (EDT) Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id SAA22088 for dcp-archive@odin.ietf.org; Tue, 25 Jun 2002 18:20:32 -0400 (EDT) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id SAA22080; Tue, 25 Jun 2002 18:20:24 -0400 (EDT) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id SAA22040 for ; Tue, 25 Jun 2002 18:20:22 -0400 (EDT) Received: from nit.isi.edu (nit.isi.edu [128.9.160.116]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA01475 for ; Tue, 25 Jun 2002 18:19:38 -0400 (EDT) Received: from nit.isi.edu (nit.isi.edu [128.9.160.116]) by nit.isi.edu (8.11.6/8.11.6) with ESMTP id g5PMJgo31595; Tue, 25 Jun 2002 15:19:42 -0700 Date: Tue, 25 Jun 2002 15:19:42 -0700 From: Aaron Falk To: Magnus Westerlund cc: dcp@ietf.org, Allison Mankin , Scott Bradner , Eddie Kohler Subject: Re: [dcp] draft dccp agenda Message-ID: <20960000.1025043582@nit.isi.edu> In-Reply-To: <3D181B33.7030004@era.ericsson.se> References: <6550000.1024938581@nit.isi.edu> <3D181B33.7030004@era.ericsson.se> X-Mailer: Mulberry/2.2.1 (Linux/x86) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit Sender: dcp-admin@ietf.org Errors-To: dcp-admin@ietf.org X-Mailman-Version: 1.0 Precedence: bulk List-Id: Datagram Control Protocol X-BeenThere: dcp@ietf.org Content-Transfer-Encoding: 7bit Magnus- The document draft-floyd-dcp-problem-00.txt has been submitted as an informal requirements summary. This document has been out since February and there has been very little, if any, discussion about changes to requirements. It's not a good use of valuable working group time to review a doc that's been out for a while. If you have some issues with the problem statement, let's surface them on the mail list first. --aaron --On Tuesday, June 25, 2002 09:26:43 AM +0200 Magnus Westerlund wrote: > Hi Aaron, > > Shouldn't there be some time for discussing requirements on DCCP? I would > also like to see a presentation from Kohler about what requirements they > have seen and address by the current proposal. > > Regards > > Magnus _______________________________________________ dcp mailing list: dcp@ietf.org archives: https://www1.ietf.org/mailman/listinfo/dcp project: http://www.icir.org/kohler/dcp/ From daemon@optimus.ietf.org Wed Jun 26 04:00:31 2002 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA07056 for ; Wed, 26 Jun 2002 04:00:31 -0400 (EDT) Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id EAA07702 for dcp-archive@odin.ietf.org; Wed, 26 Jun 2002 04:01:15 -0400 (EDT) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id EAA07684; Wed, 26 Jun 2002 04:01:08 -0400 (EDT) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id EAA07652 for ; Wed, 26 Jun 2002 04:01:05 -0400 (EDT) Received: from compuserve.com (casabritanica12.att.net.co [200.14.253.134]) by ietf.org (8.9.1a/8.9.1a) with SMTP id EAA07052 for ; Wed, 26 Jun 2002 04:00:19 -0400 (EDT) Date: Wed, 26 Jun 2002 04:00:19 -0400 (EDT) From: kristian_lb@WildEmail.com Message-Id: <200206260800.EAA07052@ietf.org> To: Dcp X-Mailer: OutLook Express 3.14159 MIME-Version: 1.0 Content-type: text/plain Content-Transfer-Encoding: 8bit Content-Transfer-Encoding: 8bit Subject: [dcp] Dcp, Check my private incest photos its kinda weird :) Sender: dcp-admin@ietf.org Errors-To: dcp-admin@ietf.org X-Mailman-Version: 1.0 Precedence: bulk List-Id: Datagram Control Protocol X-BeenThere: dcp@ietf.org Content-Transfer-Encoding: 8bit Hi Dcp ! We have incest of all kinds: Daddy - Daughter, Mommy - Son, Mommy - Daughter, Brother - Sister, Sister - Sister, Daddy - Son, Brother - Brother... Just take a free tour! http://shocking-incest.com/ Our content is absolutely real, no doubt (for 100%!!!): Shocking Family Photos, Black and White Retro Photos Content, HOT incest Movie Clips, Incest Family Stories and more. http://shocking-incest.com/ My Daddy is a real sexual monster... He can fuck me 5-6 times a day... And his crazy brother always draw me and my daddy. In the beginning I didn't like that, but then I felt myself pleased... _______________________________________________ dcp mailing list: dcp@ietf.org archives: https://www1.ietf.org/mailman/listinfo/dcp project: http://www.icir.org/kohler/dcp/