Re: SIP API spec

Noel Chiappa <jnc@ginger.lcs.mit.edu> Thu, 28 January 1993 02:40 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa08324; 27 Jan 93 21:40 EST
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa08320; 27 Jan 93 21:40 EST
Received: from Sun.COM by CNRI.Reston.VA.US id aa10606; 27 Jan 93 21:42 EST
Received: from Eng.Sun.COM (zigzag-bb.Corp.Sun.COM) by Sun.COM (4.1/SMI-4.1) id AA12478; Wed, 27 Jan 93 18:39:51 PST
Received: from sunroof.Eng.Sun.COM by Eng.Sun.COM (4.1/SMI-4.1) id AA15868; Wed, 27 Jan 93 18:41:07 PST
Received: from Eng.Sun.COM (engmail1) by sunroof.Eng.Sun.COM (4.1/SMI-4.1) id AA20639; Wed, 27 Jan 93 18:39:35 PST
Received: from Sun.COM (sun-barr) by Eng.Sun.COM (4.1/SMI-4.1) id AA02465; Wed, 27 Jan 93 18:41:07 PST
Received: from ginger.lcs.mit.edu by Sun.COM (4.1/SMI-4.1) id AA12448; Wed, 27 Jan 93 18:39:33 PST
Received: by ginger.lcs.mit.edu id AA00601; Wed, 27 Jan 93 21:39:26 -0500
Date: Wed, 27 Jan 93 21:39:26 -0500
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Noel Chiappa <jnc@ginger.lcs.mit.edu>
Message-Id: <9301280239.AA00601@ginger.lcs.mit.edu>
To: Bob.Gilligan@eng.sun.com, ip-encaps@sunroof.eng.sun.com, sip@caldera.usc.edu
Subject: Re: SIP API spec
Cc: jnc@ginger.lcs.mit.edu
Content-Length: 552

    > I am getting the feeling that this specification is being thrown together
    > in a real hurry in an attempt to 'win' some competition. I can't help but
    > feel that this is the wrong road to take to produce a great design....

    Actually, we felt the need to write up the API spec because we were
    approaching the point where we would have two independent SIP
    implementations based on BSD unix and we didn't want the two
    implementors to pick different APIs.

Ah, I was referring to SIP as a whole, not just the API spec.

	Noel