From owner-freebsd-arch  Sat Sep  8 13:38:12 2001
Delivered-To: freebsd-arch@freebsd.org
Received: from elvis.mu.org (elvis.mu.org [216.33.66.196])
	by hub.freebsd.org (Postfix) with ESMTP id 2BD7237B401
	for <arch@freebsd.org>; Sat,  8 Sep 2001 13:38:09 -0700 (PDT)
Received: by elvis.mu.org (Postfix, from userid 1192)
	id 0897E81D05; Sat,  8 Sep 2001 15:38:04 -0500 (CDT)
Date: Sat, 8 Sep 2001 15:38:04 -0500
From: Alfred Perlstein <bright@mu.org>
To: Bill Fenner <fenner@research.att.com>
Cc: jlemon@flugsvamp.com, arch@freebsd.org
Subject: Re: Causing <netinet/in.h> to depend on <sys/socket.h>
Message-ID: <20010908153803.I2965@elvis.mu.org>
References: <200109072125.OAA25298@windsor.research.att.com> <3B9A134D.3B31C443@mindspring.com> <200109081858.LAA12165@windsor.research.att.com> <20010908141005.R20137@prism.flugsvamp.com> <200109082022.NAA13321@windsor.research.att.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <200109082022.NAA13321@windsor.research.att.com>; from fenner@research.att.com on Sat, Sep 08, 2001 at 01:21:59PM -0700
Sender: owner-freebsd-arch@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-arch.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-arch>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-arch>
X-Loop: FreeBSD.ORG

* Bill Fenner <fenner@research.att.com> [010908 15:22] wrote:
> 
> >It seems that the real problem here is that sockaddr_storage is supposed
> >to be protocol-neutral (used for appletalk, IPX, etc), but what your 
> >code really wants is IP-specific sockaddr_storage.
> 
> Well, sockaddr_storage was introduced to support IPv6; it was defined
> to be "at least large enough to accommodate sockaddr_in and sockaddr_in6
> and possibly other protocol specific socket addresses too." [RFC 2553
> section 3.10].  I guess the "and possibly other..." part is what's not
> working out, especially since IEEE Std 1003.1-200x gets rid of the "possibly"
> part.
> 
> The advantage of sockaddr_storage is that it's already standard, in
> widespread use, and was defined for exactly this purpose.

I know hindsight is 20/20, and it was before my time, but...

I wish we (free unix) had adopted a form of TLI/XTI :( (of course
without the entire streams fiasco).

-- 
-Alfred Perlstein [alfred@freebsd.org]
'Instead of asking why a piece of software is using "1970s technology,"
start asking why software is ignoring 30 years of accumulated wisdom.'

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-arch" in the body of the message