Re: Removing T/TCP and replacing it with something simpler

From: Richard Wendland (richard_at_codeburst.co.uk)
Date: 10/21/04

  • Next message: Mike Silbersack: "Re: Removing T/TCP and replacing it with something simpler" 
    To: andre@freebsd.org (Andre Oppermann)
Date: Thu, 21 Oct 2004 15:59:22 +0100 (BST)

    > I intend to remove T/TCP (transactional TCP) support from our TCP
    > implementation for the following reasons:

    Good reasons & decision Andre.

    Another reason is that T/TCP (RFC1644) is listed as "deprecated" in the
    "Roadmap for TCP Specification Documents" I-D, almost certainly to become
    a RFC soon:

      http://www.ietf.org/internet-drafts/draft-ietf-tcpm-tcp-roadmap-00.txt

              Richard 

    -- 
Richard Wendland				richard@codeburst.co.uk
_______________________________________________
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org"
  • Next message: Mike Silbersack: "Re: Removing T/TCP and replacing it with something simpler"

    Relevant Pages

    • Re: Removing T/TCP and replacing it with something simpler
      ... > I intend to remove T/TCP support from our TCP ... Good reasons & decision Andre. ... Another reason is that T/TCP is listed as "deprecated" in the ...
      (freebsd-arch)
    • Re: Removing T/TCP and replacing it with something simpler
      ... > I intend to remove T/TCP support from our TCP ... > implementation for the following reasons: ... > If the server accepts it, then it returns a unique cookie generated from ... things about T/TCP - you must be the one misunderstanding things here! ...
      (freebsd-arch)
    • Re: Removing T/TCP and replacing it with something simpler
      ... > I intend to remove T/TCP support from our TCP ... > implementation for the following reasons: ... > If the server accepts it, then it returns a unique cookie generated from ... things about T/TCP - you must be the one misunderstanding things here! ...
      (freebsd-net)
    • Re: Threads, conditions, sockets, selects...
      ... but it's not reasonable from the TCP stack's perspective. ... When the sender gets the acknowledge, it will send the next chunk. ... flush the buffer, flush the buffer if it exceeds 2Kb, and flush it ... Sockets were chosen for a few reasons: ...
      (comp.unix.programmer)
    • Re: C# Async Socket timeouts
      ... I have many reasons for not getting a response, and TCP issues are not ... I am talking to embedded systems over cellular and ...
      (microsoft.public.dotnet.languages.csharp)