Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!hao!boulder!sunybcs!rutgers!labrea!decwrl!ucbvax!A.ISI.EDU!CERF
From: CERF@A.ISI.EDU
Newsgroups: comp.protocols.tcp-ip
Subject: Re: user interface for urgent data.
Message-ID: <[A.ISI.EDU]15-Sep-87.09:42:55.CERF>
Date: Tue, 15-Sep-87 12:42:00 EDT
Article-I.D.: <[A.ISI.EDU]15-Sep-87.09:42:55.CERF>
Posted: Tue Sep 15 12:42:00 1987
Date-Received: Thu, 17-Sep-87 05:58:07 EDT
References: <8709141456.AA04409@umd5.UMD.EDU>
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 15

Joe,

In the urgent daa design, it was assumed that TCP should NOT
impose any kind of syntax on the data stream. Rather, the
flagging of urgen data meant, roughly, "start scanning the
data stream wherever you are now and go through at least
to the placed marked URGENT. Process appropriately whatever
you read, given that you know you are in URGENT mode until you
get to byte sequence number X."

It was assumed that the application using TCP would have
conventions for structuring of the TCP byte stream and
for interpreting what to do with urgent data indicator.

Vint Cerf