Re: SIP now IPv6

Dave Crocker <dcrocker@mordor.stanford.edu> Thu, 24 December 1992 22:52 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa05104; 24 Dec 92 17:52 EST
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa05099; 24 Dec 92 17:52 EST
Received: from Sun.COM by CNRI.Reston.VA.US id aa20724; 24 Dec 92 17:55 EST
Received: from Eng.Sun.COM (zigzag-bb.Corp.Sun.COM) by Sun.COM (4.1/SMI-4.1) id AA15859; Thu, 24 Dec 92 14:54:07 PST
Received: from sunroof.Eng.Sun.COM by Eng.Sun.COM (4.1/SMI-4.1) id AA18091; Thu, 24 Dec 92 14:54:08 PST
Received: from Eng.Sun.COM (engmail1) by sunroof.Eng.Sun.COM (4.1/SMI-4.1) id AA09821; Thu, 24 Dec 92 14:53:53 PST
Received: from Sun.COM (sun-barr) by Eng.Sun.COM (4.1/SMI-4.1) id AA26341; Thu, 24 Dec 92 14:54:00 PST
Received: from Mordor.Stanford.EDU by Sun.COM (4.1/SMI-4.1) id AA15842; Thu, 24 Dec 92 14:53:53 PST
Received: from localhost by Mordor.Stanford.EDU (5.65/inc-1.0) id AA18353; Thu, 24 Dec 92 14:52:09 -0800
Message-Id: <9212242252.AA18353@Mordor.Stanford.EDU>
To: "Vinton G. Cerf" <vcerf@CNRI.Reston.VA.US>
Cc: Dave Katz <dkatz@cisco.com>, sip@caldera.usc.edu, ip-encaps@sunroof.eng.sun.com, iana@isi.edu, iab@isi.edu
Subject: Re: SIP now IPv6
Org: The Branch Office, Sunnyvale CA
Phone: +1 408 246 8253; fax: +1 408 249 6205
In-Reply-To: Your message of Thu, 24 Dec 92 13:40:55 -0500. <9212241341.aa04032@IETF.CNRI.Reston.VA.US>
Date: Thu, 24 Dec 1992 14:52:08 -0800
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Dave Crocker <dcrocker@mordor.stanford.edu>
X-Mts: smtp
Content-Length: 1112

HWB, et al.,

Always interesting to see straightforward engineering work become
politicized.

But since the discussion has finally gotten into the realm of technical
options, I'd like to suggest that the IP version field is _exactly_ the
right place to mark the difference, unless there is strong evidence that
it truly isn't viable, technically.  

The protocol is trying to run on top of all the existing IPv4 sub-network
support, e.g., Arp.  The protocol is, in fact, a technical delta of
v4.  The service interface to the upper layers is also a straight delta.

In other words, the damn thing really is a variant of IPv4.  So, use of
the IP version number field makes sense.

If this turns out to break existing implementations -- assuming that
SIP-as-IPv6 shows up in its pure, unencapsulated form at IPv4-only
systems -- then I agree this should be rethought.

But if we are attempting to develop a running system, then every
piece that is different from the intended final form leaves us open to
the charge of doing unrealistic testing or of creating problems that do
not apply to the final system.

Dave