Re: SIP API spec

Steve Deering <deering@parc.xerox.com> Tue, 26 January 1993 17:39 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa05974; 26 Jan 93 12:39 EST
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa05964; 26 Jan 93 12:39 EST
Received: from Sun.COM by CNRI.Reston.VA.US id aa17145; 26 Jan 93 12:41 EST
Received: from Eng.Sun.COM (zigzag-bb.Corp.Sun.COM) by Sun.COM (4.1/SMI-4.1) id AA29812; Tue, 26 Jan 93 09:34:08 PST
Received: from sunroof.Eng.Sun.COM by Eng.Sun.COM (4.1/SMI-4.1) id AA04945; Tue, 26 Jan 93 09:34:36 PST
Received: from Eng.Sun.COM (engmail1) by sunroof.Eng.Sun.COM (4.1/SMI-4.1) id AA02999; Tue, 26 Jan 93 09:33:22 PST
Received: from Sun.COM (sun-barr) by Eng.Sun.COM (4.1/SMI-4.1) id AA11525; Tue, 26 Jan 93 09:34:36 PST
Received: from alpha.xerox.com by Sun.COM (4.1/SMI-4.1) id AA29698; Tue, 26 Jan 93 09:33:11 PST
Received: from skylark.parc.xerox.com ([13.2.116.7]) by alpha.xerox.com with SMTP id <11828>; Tue, 26 Jan 1993 09:30:56 PST
Received: from localhost by skylark.parc.xerox.com with SMTP id <12171>; Tue, 26 Jan 1993 09:30:49 -0800
To: Craig Partridge <craig@aland.bbn.com>
Cc: ip-encaps@sunroof.eng.sun.com, sip@caldera.usc.edu
Subject: Re: SIP API spec
In-Reply-To: Your message of "Tue, 26 Jan 93 09:01:24 PST." <9301261701.AA12090@aland.bbn.com>
Date: Tue, 26 Jan 1993 09:30:35 PST
X-Orig-Sender: Steve Deering <deering@parc.xerox.com>
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Steve Deering <deering@parc.xerox.com>
Message-Id: <93Jan26.093049pst.12171@skylark.parc.xerox.com>
Content-Length: 262

> Why would an application ever want to set the FLOWID?  I've assumed that
> this is something that is done by the kernel.

Craig,

I can certainly imagine UDP-based applications, such as vat and nv, wanting
to set the Flow ID in their outgoing packets.

Steve