Re: SIP API spec

Craig Partridge <> Tue, 26 January 1993 17:48 UTC

Received: from by IETF.CNRI.Reston.VA.US id aa06129; 26 Jan 93 12:48 EST
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa06125; 26 Jan 93 12:48 EST
Received: from Sun.COM by CNRI.Reston.VA.US id aa17446; 26 Jan 93 12:50 EST
Received: from Eng.Sun.COM (zigzag-bb.Corp.Sun.COM) by Sun.COM (4.1/SMI-4.1) id AA01518; Tue, 26 Jan 93 09:46:52 PST
Received: from sunroof.Eng.Sun.COM by Eng.Sun.COM (4.1/SMI-4.1) id AA06313; Tue, 26 Jan 93 09:47:03 PST
Received: from Eng.Sun.COM (engmail1) by sunroof.Eng.Sun.COM (4.1/SMI-4.1) id AA03034; Tue, 26 Jan 93 09:45:46 PST
Received: from Sun.COM (sun-barr) by Eng.Sun.COM (4.1/SMI-4.1) id AA12097; Tue, 26 Jan 93 09:47:00 PST
Received: from BBN.COM by Sun.COM (4.1/SMI-4.1) id AA01366; Tue, 26 Jan 93 09:45:39 PST
Received: from by BBN.COM id aa19441; 26 Jan 93 12:41 EST
Received: by (4.1/3.1.090690-BBN) id AA12205; Tue, 26 Jan 93 09:39:40 PST
Message-Id: <>
To: Steve Deering <>
Subject: Re: SIP API spec
In-Reply-To: Your message of Tue, 26 Jan 93 09:30:35 -0800. <>
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Craig Partridge <>
Date: Tue, 26 Jan 93 09:39:40 -0800
Content-Length: 657

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

    Good point.  Thanks.

    It raised a question in my mind.

    What happens if two different applications try to use the same Flow ID?
    If we use well-known Flow IDs (say, "this is telnet") then presumably
    this is OK.  But for specially negotiated flows, presumably the flow ID
    is unique (or is it?).

    In other words, will setsockopt() of the FLOW ID ever return EADDRINUSE?

    If we have well-known flow ids, does this mean that calls to use them
    need to be privileged?