IETF Logo Mail Archive

RE: Connection Establishment

Bob Braden <braden@ISI.EDU> Wed, 06 February 2002 20:01 UTC

From: Bob Braden <braden@ISI.EDU>
Date: Wed, 6 Feb 2002 20:01:18 GMT
Message-Id: <200202062001.UAA20927@gra.isi.edu>
To: tcp-impl@grc.nasa.gov, jgh@uk.sun.com
Subject: RE: Connection Establishment
X-Sun-Charset: US-ASCII
Sender: owner-tcp-impl@grc.nasa.gov
Precedence: bulk
Status: RO
Content-Length: 1117
Lines: 30

  *> From owner-tcp-impl@grc.nasa.gov  Wed Feb  6 10:35:39 2002
  *> Date: Wed, 6 Feb 2002 18:23:23 +0000 (GMT)
  *> From: Jeremy Harris - Network Service Providers Division <jgh@uk.sun.com>
  *> Subject: RE: Connection Establishment
  *> To: tcp-impl@grc.nasa.gov
  *> Cc: jgh@uk.sun.com
  *> MIME-Version: 1.0
  *> Content-MD5: rDSuqNHi4wDEZ/GSrGfi8w==
  *> X-AntiVirus: scanned by AMaViS 0.2.1
  *> 
  *> Venkata.Naidu@Marconi.com said:
  *> >   As per TCP standard (not w.r.t. any API implementations, 
  *> >   like sockets)
  *> > 
  *> >   Machine A initiates a connection to machine B.
  *> >   A sends a segment with ISN x, chosen according
  *> >   A's clock, and with SYN bit set to 1, this is the
  *> >   connection request message.
  *> > 	- the ACK flag is set to 0
  *> > 	- this segment is still a regular TCP segment; it
  *> > 	  can carry data too (piggyback 1)
  *> 
  *> I have implemented this; it works nicely.   However, the question
  *> arises: how much data may be piggybacked on a SYN?  What window may
  *> the sender assume?
  *> 

Please see RFC 1644 on T/TCP (July 1994)/

Bob Braden

v2.8.7 | Report a Bug | By Email