| From | Sent On | Attachments |
|---|---|---|
| Andre Oppermann | Oct 21, 2004 7:33 am | |
| Poul-Henning Kamp | Oct 21, 2004 7:41 am | |
| Andre Oppermann | Oct 21, 2004 7:46 am | |
| Richard Wendland | Oct 21, 2004 7:59 am | |
| Mike Silbersack | Oct 21, 2004 8:23 am | |
| Andre Oppermann | Oct 21, 2004 8:37 am | |
| Bruce M Simpson | Oct 21, 2004 8:40 am | |
| Andre Oppermann | Oct 21, 2004 9:23 am | |
| Garrett Wollman | Oct 21, 2004 9:27 am | |
| Mark Allman | Oct 21, 2004 10:31 am | |
| Andre Oppermann | Oct 21, 2004 10:56 am | |
| Matt Emmerton | Oct 21, 2004 11:31 am | |
| Sean Chittenden | Oct 21, 2004 11:31 am | |
| Mark Allman | Oct 21, 2004 11:32 am | |
| David O'Brien | Oct 21, 2004 11:51 am | |
| Andre Oppermann | Oct 21, 2004 11:56 am | |
| Julian Elischer | Oct 21, 2004 11:59 am | |
| Garrett Wollman | Oct 21, 2004 12:02 pm | |
| Andre Oppermann | Oct 21, 2004 12:02 pm | |
| Andre Oppermann | Oct 21, 2004 12:04 pm | |
| Sean Chittenden | Oct 21, 2004 12:24 pm | |
| Marco Molteni | Oct 21, 2004 12:34 pm | |
| Igor Sysoev | Oct 21, 2004 12:41 pm | |
| Craig Rodrigues | Oct 21, 2004 6:46 pm | |
| Russell L. Carter | Oct 21, 2004 7:02 pm | |
| Julian Elischer | Oct 21, 2004 8:24 pm | |
| SUZUKI Shinsuke | Oct 22, 2004 12:47 am | |
| Dag-Erling Smørgrav | Oct 22, 2004 5:06 am | |
| Dag-Erling Smørgrav | Oct 22, 2004 5:47 am | |
| Andre Oppermann | Oct 22, 2004 8:14 am | |
| Andre Oppermann | Oct 22, 2004 8:17 am | |
| Brian Fundakowski Feldman | Oct 22, 2004 8:44 am | |
| Andre Oppermann | Oct 22, 2004 8:55 am | |
| Mark Allman | Oct 22, 2004 11:24 am | |
| Peter Lei | Oct 22, 2004 5:59 pm | |
| Randall Stewart | Oct 23, 2004 6:07 am | |
| Randall Stewart | Oct 23, 2004 6:16 am | |
| Randall Stewart | Oct 23, 2004 6:17 am | |
| Randall Stewart | Oct 23, 2004 6:20 am | |
| Andre Oppermann | Oct 23, 2004 7:16 am | |
| Randy Bush | Oct 23, 2004 9:01 am | |
| SUZUKI Shinsuke | Oct 25, 2004 10:18 pm | |
| Randall Stewart | Oct 26, 2004 3:41 am | |
| Peter Lei | Oct 26, 2004 7:44 am | |
| Karim Fodil-Lemelin | Nov 4, 2004 9:52 am | |
| Andre Oppermann | Nov 4, 2004 10:50 am | |
| Julian Elischer | Nov 4, 2004 12:52 pm | |
| Matt Sealey | Nov 4, 2004 12:58 pm | |
| Karim Fodil-Lemelin | Nov 5, 2004 8:08 am | |
| Karim Fodil-Lemelin | Nov 5, 2004 8:39 am | |
| Andre Oppermann | Nov 5, 2004 8:45 am | |
| Karim Fodil-Lemelin | Nov 5, 2004 9:12 am | |
| Andre Oppermann | Nov 5, 2004 9:31 am | |
| Karim Fodil-Lemelin | Nov 5, 2004 1:45 pm | |
| Andre Oppermann | Nov 5, 2004 2:16 pm | |
| Mark Allman | Nov 8, 2004 8:08 pm | |
| Andre Oppermann | Jul 3, 2005 12:08 am | |
| Andre Oppermann | Jul 3, 2005 11:43 am | |
| Randall Stewart | Jul 3, 2005 11:44 am |
| Subject: | Removing T/TCP and replacing it with something simpler | |
|---|---|---|
| From: | Andre Oppermann (and...@freebsd.org) | |
| Date: | Oct 21, 2004 12:02:56 pm | |
| List: | org.freebsd.freebsd-arch | |
David O'Brien wrote:
On Thu, Oct 21, 2004 at 04:33:17PM +0200, Andre Oppermann wrote:
Thus after the removal of T/TCP for the reasons above I want to provide a work-alike replacement for T/TCP's functionality: .. This different implementation will be disabled by default and clearly marked EXPERIMENTAL in a protocol sense. It will allow the only known user of T/TCP to keep the same functionality with a very small change to his application. It allows interesting new uses primarily in Intranet environment where many short connections are openend in rapid succession (LDAP servers, SQL servers, etc.). The modifications to those programs to use the new option is minimal and requires only the setting of the socket option, one setsockopt() call.
I'm not so happy with a FreeBSD-only "proprietary" thing. Is there any proposed RFC work that provides the qualities you want? The advantage with T/TCP is that there was a published standard.
Not for TCP. There are plenty of proposed or approved replacements for TCP though. Implementing or importing them is a lot harder and applications wanting to use it have to be extensively modified.
The nice thing of my proposed replacement is its simplicity. Submitting an RFC draft for that is not hard and I'm going to do it based on the feedback I've got so far. I think we can enough drive behind this to make it an actual published RFC standard.
Don't worry. I don't want to remove one intrusive piece of code just to replace it with another one.
-- Andre





