From: james woodyatt <jhwoodyatt@mac.com>
To: The Trade <caml-list@inria.fr>
Subject: Re: [Caml-list] parsing and emitting Unix.inet_addr values
Date: Thu, 15 Nov 2001 13:26:19 -0800 [thread overview]
Message-ID: <692234CA-DA0F-11D5-832E-000502DB38F5@mac.com> (raw)
In-Reply-To: <000601c16e14$60bffa40$ca01a8c0@homebox>
On Thursday, November 15, 2001, at 12:30 , Francois Rouaix wrote:
>
> I guess that this proved that you can get any OCaml application IPv6
> enabled if you do the appropriate work in libunix. Maybe Francis still
> has a copy of that code BTW.
I had a conversation a couple days ago with a co-worker who is active in
several IETF activities, and we were commiserating about the sorry state
of industry efforts to transition away from IPv4 to IPv6. I've almost
convinced myself that it will never happen. He's not nearly so
pessimistic as me.
We agreed that one of things holding back development of IPv6
applications are the crufty interfaces that C language programmers have
as a result of extending the BSD sockets API in the way they did.
I'm very encouraged to see the Caml team taking appropriate steps to
avoid that pitfall. Very encouraged. I had been planning to leave open
support for AAAA or A6 resource records (whichever emerges as the
standard) in my stub resolver, and now I have a better reason for doing
the extra work.
--
j h woodyatt <jhw@wetware.com>
"...the antidote to misinformation is more information, not less."
--vinton cerf
-------------------
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
prev parent reply other threads:[~2001-11-15 21:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-15 3:53 james woodyatt
2001-11-15 9:48 ` Xavier Leroy
2001-11-15 20:13 ` james woodyatt
2001-11-15 20:30 ` Francois Rouaix
2001-11-15 21:26 ` james woodyatt [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=692234CA-DA0F-11D5-832E-000502DB38F5@mac.com \
--to=jhwoodyatt@mac.com \
--cc=caml-list@inria.fr \
--cc=jhw@wetware.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox