Re: Two concerns

To: Tim Bass (IETF) <ietf at linux.silkroad.com>, adrian.hooke at jpl.nasa.gov (Adrian J. Hooke)
Subject: Re: Two concerns
From: "Eric A. Bobinsky" <eric_bobinsky at terasphere.com>
Date: Mon, 30 Mar 1998 13:57:42 -0500
Cc: Tim at linux.silkroad.com, Bass at linux.silkroad.com, <ietf at linux.silkroad.com>, travis at clark.net, Daniel.R.Glover at lerc.nasa.gov, adrian.hooke at jpl.nasa.gov, tcp-over-satellite at achtung.sp.trw.com
Delivery-date: Mon, 30 Mar 1998 15:30:14 -0500
In-reply-to: <199803301753.MAA07435@linux.silkroad.com>
References: <3.0.1.32.19980330093454.00e6e8bc@pop.jpl.nasa.gov>
Sender: owner-tcp-over-satellite at achtung.sp.trw.com

At 12:53 PM 3/30/98 -0500, IETF wrote:
>
>
>At least, miminal BER numbers should be specified as 'best estimates'
>to give all professionals in the field a vector to steer toward,
>and a common frame of reference of discussion.
>
>

As I stated earlier, satellite BER and availability is in fact *already*
mandated by the ITU.  All "public" international carriers and most private
ones already adhere to the specs.  The question that needs to be addressed
is, are they good enough for TCP/IP?

Eric

---------------------------------------------------------------------
Eric Bobinsky
Terasphere Corp.

Telephone (440) 243-2992                343 W. Bagley Road, Suite 405
Facsimile/Telecopie (440) 243-2934      Post Office Box 10
International +1 440 243 2992/2934      Berea, Ohio  44017
eric at terasphere.com                     USA
Alternate: eric.bobinsky at itu.ch
---------------------------------------------------------------------

References:
- Re: Two concerns
  - From: Adrian J. Hooke
- Re: Two concerns
  - From: IETF

Prev by Date: Re: Two concerns
Next by Date: RFC 2321 on RITA
Previous by thread: Re: Two concerns
Next by thread: RFC 2321 on RITA
Index(es):
- Date
- Thread

Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.

Re: Two concerns

Note: Messages sent to this list are the opinions of the senders and do not imply endorsement by the IETF.