Re: sockets APIs extensions for Host Identity Protocol

der Mouse <mouse@Rodents.Montreal.QC.CA> Wed, 16 May 2007 17:24 UTC

Return-path: <discuss-bounces@apps.ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HoNEv-0001fL-3P; Wed, 16 May 2007 13:24:41 -0400
Received: from discuss by megatron.ietf.org with local (Exim 4.43) id 1HoNEt-0001fD-G4 for discuss-confirm+ok@megatron.ietf.org; Wed, 16 May 2007 13:24:39 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HoNEt-0001eo-63 for discuss@apps.ietf.org; Wed, 16 May 2007 13:24:39 -0400
Received: from sparkle.rodents.montreal.qc.ca ([216.46.5.7]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HoNEr-0003C5-Nl for discuss@apps.ietf.org; Wed, 16 May 2007 13:24:39 -0400
Received: (from mouse@localhost) by Sparkle.Rodents.Montreal.QC.CA (8.8.8/8.8.8) id NAA03539; Wed, 16 May 2007 13:24:35 -0400 (EDT)
From: der Mouse <mouse@Rodents.Montreal.QC.CA>
Message-Id: <200705161724.NAA03539@Sparkle.Rodents.Montreal.QC.CA>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
X-Erik-Conspiracy: There is no Conspiracy - and if there were I wouldn't be part of it anyway.
X-Message-Flag: Microsoft: the company who gave us the botnet zombies.
Date: Wed, 16 May 2007 13:21:23 -0400 (EDT)
To: discuss@apps.ietf.org
Subject: Re: sockets APIs extensions for Host Identity Protocol
In-Reply-To: <Pine.LNX.4.64.0705141727240.26169@hermes-1.csi.cam.ac.uk>
References: <Pine.SOL.4.64.0705041801060.14418@kekkonen.cs.hut.fi> <31BC7A8C1A51004A84E08DEF@[10.1.110.5]> <200705072216.SAA06179@Sparkle.Rodents.Montreal.QC.CA> <Pine.SOL.4.64.0705090046320.18946@kekkonen.cs.hut.fi> <200705141552.LAA02624@Sparkle.Rodents.Montreal.QC.CA> <Pine.LNX.4.64.0705141727240.26169@hermes-1.csi.cam.ac.uk>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581
X-BeenThere: discuss@apps.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: general discussion of application-layer protocols <discuss.apps.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/discuss>, <mailto:discuss-request@apps.ietf.org?subject=unsubscribe>
List-Post: <mailto:discuss@apps.ietf.org>
List-Help: <mailto:discuss-request@apps.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/discuss>, <mailto:discuss-request@apps.ietf.org?subject=subscribe>
Errors-To: discuss-bounces@apps.ietf.org

>> The major annoyance [getaddrinfo] has for me is the requirement
>> that, to quote the manpage for the version I use, "[i]n this hints
>> structure all members other than ai_flags, ai_family, ai_socktype,
>> and ai_protocol must be zero or a NULL pointer".
> You should be able to just memset() it to 0.  (I believe POSIX gives
> you more guarantees than C in this respect.)

POSIX requires nil pointers to be all-bits-zero?  That's..bizarre.
Must be rather crippling for anyone trying to work with oddball
architectures.

I'd also recommend against depending on it when designing interfaces;
these interfaces get used in not-quite-POSIX and sometimes even
not-even-close-to-POSIX systems, and I think it would be good if they
didn't depend on POSIX features unnecessarily - and I see this as a
totally unnecessary dependency.

/~\ The ASCII				der Mouse
\ / Ribbon Campaign
 X  Against HTML	       mouse@rodents.montreal.qc.ca
/ \ Email!	     7D C8 61 52 5D E7 2D 39  4E F1 31 3E E8 B3 27 4B