Dor Snapir - Israel | 7 Oct 2002 14:28
Favicon

TCP over geo stationary satellites

Hello all
Does any of you knows whether there ever been a research to compare TCP
(extended for satellite comm.)with spoofing mechanisms such as Flash
Networks Nettgain and why does this extended TCP was never actually
deployed?
Thanks
Dor
_______________________________________________
pilc mailing list
pilc <at> ietf.org
https://www1.ietf.org/mailman/listinfo/pilc
http://www.ietf.org/html.charters/pilc-charter.html
http://pilc.grc.nasa.gov/

William Ivancic | 8 Oct 2002 16:33
Picon
Favicon

RE: TCP over geo stationary satellites

Joe Ishac did some work related to generic PEPs and TCP.  I'm sure there 
are others.

http://roland.grc.nasa.gov/~jishac/papers/

Remember, buyer-beware.  PEPs are nice, but have limitations - particularly 
if encryption is done at the network layer prior to the PEP.  That is why 
so many are still researching better transport mechanisms - TCP Westwood, 
TCP swift-start, etc...

Will

At 03:55 PM 10/8/02 +0200, you wrote:
>This was exactly what I meant SACK, Large windows etc.) do you know of any
>comparison?
>
>
>What do you mean by "extended" TCP.  Do you mean TCP with large windows,
>time stamp options, SACK, protect against wrap around.  Or is "extended"
>TCP someone's proprietary implementation of TCP.
>
>Will
>
>
>    PM 10/7/02 +0200, you wrote:
> >Hello all
> >Does any of you knows whether there ever been a research to compare TCP
> >(extended for satellite comm.)with spoofing mechanisms such as Flash
> >Networks Nettgain and why does this extended TCP was never actually
> >deployed?
(Continue reading)

Tyler | 9 Oct 2002 19:04
Picon
Favicon

I found the best computer parts

Aaron Falk | 10 Oct 2002 19:23
Picon
Favicon

Protocol Action: TCP Performance Implications of Network Asymmetry to BCP

Congratulations to the authors.  Well done!

--aaron

----- Forwarded message from The IESG <iesg-secretary <at> ietf.org> -----

To: IETF-Announce: ;
Cc: RFC Editor <rfc-editor <at> ISI.EDU>, Internet Architecture Board <iab <at> iab.org>,
   pilc <at> grc.nasa.gov
From: The IESG <iesg-secretary <at> ietf.org>
Subject: Protocol Action: TCP Performance Implications of Network
	 Asymmetry to BCP
Date: Thu, 10 Oct 2002 12:56:52 -0400

The IESG has approved the Internet-Draft 'TCP Performance Implications
of Network Asymmetry' <draft-ietf-pilc-asym-08.txt> as a BCP.  This
document is the product of the Performance Implications of Link
Characteristics Working Group. The IESG contact persons are Allison
Mankin and Scott Bradner.

Technical Summary

  This document describes TCP performance problems that may arise if 
  network paths have asymmetric characteristics. These problems arise 
  in several access networks, including bandwidth-asymmetric networks 
  and packet radio subnetworks, for different underlying reasons. However, 
  the end result on TCP performance is the same in both cases: performance 
  often degrades significantly because of imperfection and variability in 
  the ACK feedback from the receiver to the sender.

  This document details several mitigations of these effects, which have
  either been proposed or evaluated in the literature, or are currently
  deployed in networks. These solutions use a combination of local 
  link-layer techniques, subnetwork, and end-to-end mechanisms, 
  consisting of: (i) techniques to manage the channel used for the 
  upstream bottleneck link carrying the ACKs, typically using header 
  compression or reducing the frequency of TCP ACKs, (ii) techniques to 
  handle this reduced ACK frequency to retain the TCP sender's 
  acknowledgment-triggered self-clocking and (iii) techniques to schedule 
  the data and ACK packets in the reverse direction to improve performance 
  in the presence of two-way traffic. Each technique is described, together 
  with known issues, and recommendations for when they should be used, and 
  recommendations of techniques that should not be used.

Working Group Summary

  The working group supported the advancement of the document.

 
Protocol Quality

  This document was reviewed for the IESG by Allison Mankin.

----- End forwarded message -----
_______________________________________________
pilc mailing list
pilc <at> ietf.org
https://www1.ietf.org/mailman/listinfo/pilc
http://www.ietf.org/html.charters/pilc-charter.html
http://pilc.grc.nasa.gov/

Sundeep Singatwaria | 17 Oct 2002 19:38

performance comparsion of transport layers


Could someone provide me a link to the work done on performance comparsion of tranport layer protocols mainly TCP, UDP, Reliable UDP.

Thanks.
Sundeep

Sundeep Singatwaria | 17 Oct 2002 19:40

FW: performance comparsion of transport layers


Sorry for the spam..

Please CC to my email address as I'm not subscribed on this mailing list.

Thanks again.
Sundeep

-----Original Message-----
From: Singatwaria, Sundeep [SC100:370:EXCH]
Sent: Thursday, October 17, 2002 10:39 AM
To: 'pilc <at> ietf.org'
Subject: performance comparsion of transport layers



Could someone provide me a link to the work done on performance comparsion of tranport layer protocols mainly TCP, UDP, Reliable UDP.

Thanks.
Sundeep

JinHyeock Choi | 21 Oct 2002 09:17
Picon

Will there be L2 trigger BoF in Atlanta?

Hi

I wonder there will be L2 trigger BoF in Atlanta. I heard someone is 
planning BoF called IP trigger Interface Protocol (IPTrIP). If anyone 
knows more about it, kindly let us know. 

Best Regards

JinHyeock Choi
_______________________________________________
pilc mailing list
pilc <at> ietf.org
https://www1.ietf.org/mailman/listinfo/pilc
http://www.ietf.org/html.charters/pilc-charter.html
http://pilc.grc.nasa.gov/

Aaron Falk | 23 Oct 2002 03:11
Picon
Favicon

Re: Will there be L2 trigger BoF in Atlanta?

JinHyeock Choi wrote:
>  
> I wonder there will be L2 trigger BoF in Atlanta. I heard someone is 
> planning BoF called IP trigger Interface Protocol (IPTrIP). If anyone 
> knows more about it, kindly let us know. 

I'm unaware of any such BoF, nor have I seen it on any of the draft
agendas.  Of course, this isn't authoritative since BoF scheduling
often occurs at the last minute.

--aaron
_______________________________________________
pilc mailing list
pilc <at> ietf.org
https://www1.ietf.org/mailman/listinfo/pilc
http://www.ietf.org/html.charters/pilc-charter.html
http://pilc.grc.nasa.gov/

Spencer Dawkins | 31 Oct 2002 00:11

New BOF and Mailing List for "Triggers for Transport" - TRIGTRAN

Just to let people know -

Carl Williams and I are hosting a BOF on "Triggers for Transport" ("TRIGTRAN") 
at IETF 55 in Atlanta next month.

The problem space is somewhat similar to, but distinct from, discussions 
about L2Triggers on the PILC mailing list over the past year.

The goal here is to understand whether subnetworks really do know things 
that are valuable to transport implementations, and can communicate this 
knowledge in a reasonable way.

The BOF agenda and description are at http://www.ietf.org/ietf/02nov/trigtran.txt.

A strawman problem description is at 
http://www.ietf.org/internet-drafts/draft-dawkins-trigtran-probstmt-00.txt.

The mailing list information is at 
https://www1.ietf.org/mailman/listinfo/trigtran.

The mailing list archives are at 
http://www.ietf.org/mail-archive/working-groups/trigtran/current/maillist.html.

Please followup on the TRIGTRAN mailing list, at trigtran <at> ietf.org.

Thanks,

Spencer, for Spencer and Carl
_______________________________________________
pilc mailing list
pilc <at> ietf.org
https://www1.ietf.org/mailman/listinfo/pilc
http://www.ietf.org/html.charters/pilc-charter.html
http://pilc.grc.nasa.gov/


Gmane