| 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: | SCTP in KAME / Re: Removing T/TCP and replacing it withsomething simpler | |
|---|---|---|
| From: | SUZUKI Shinsuke (su...@kame.net) | |
| Date: | Oct 25, 2004 10:18:46 pm | |
| List: | org.freebsd.freebsd-arch | |
On Fri, 22 Oct 2004 19:58:32 -0500 pete...@ieee.org(Peter Lei) said:
While the SCTP API hasn't gone through last call, it's fairly stable and we have both "converted" many applications from TCP to SCTP using the sockets API, as well as had portability between the KAME SCTP stack and the linux stack for some test applications used at the last interop event (except for the standard sockets issues that one runs into even for TCP like no sin_length field in the sockaddr struct). I'm not aware of any KAME SNAP compilation failures w/and w/o SCTP. The major changes to our SCTP code when it gets committed into KAME has been that of code format/style.
What I found was the following two issues. Although these two are technically quite trivial, what I was fearing was a lack of report to KAME, since this may mean a lack of KAME-SCTP users.
- inconsistency between KAME specific kernel code and SCTP leads to an kernel compilation error. Of course, it's a technically trivial bug and our own bug.
- including SCTP in getaddrinfo() causes 'configure' script error
in many ports applications.
This is also a trivial problem, and maybe specific to KAME SCTP.
And some of such ports are already fixed when I encounter this
problem.
(e.g.
http://www.freebsd.org/cgi/cvsweb.cgi/ports/lang/python/files/patch-configure.diff?r1=1.7&r2=1.8)
But now I understand that lack of report does not mean a lack of testing users (since SCTP-lovers seems communicating directly to your team). So I can be much more optimistic now, and don't object to merging it into -current, since such trivial bugs can be fixed easily in -current. (I myself haven't tested SCTP very well, so I cannot comment on its stability itself. But at least, SCTP does not seem to affect the behavior of other protocols)
Thanks and sorry if you feel my previous comments were insulting...
---- SUZUKI, Shinsuke @ KAME Project





