Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Juliusz Chroboczek <jch@pps.jussieu.fr>
To: dpreed@reed.com
Cc: bloat-devel <bloat-devel@lists.bufferbloat.net>,
	cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] cerowrt-next plans
Date: Tue, 08 Jan 2013 06:18:03 +0100	[thread overview]
Message-ID: <87mwwkz20k.wl%jch@pps.univ-paris-diderot.fr> (raw)
In-Reply-To: <1353713218.198812384@apps.rackspace.com>

Sorry for the extremely late reply (it's been over a month!), but I'm
only slowly recovering from a massive mail backlog.

>>> it occurs to me that AHCP might be a better choice than the
>>> alternatives for use in Amateur Radio internet environments with IPv6.

>> Why do you need IPV6 for HAM use

> Two reasons come to mind - I'm sure there are more.

Another reason is that a number of things are much easier to implement
in IPv6.  This is especially true of link-local stuff, which is highly
non-portable in IPv4, and quite reasonable in IPv4.

That's the main reason why I never bothered defining AHCP over IPv4 --
the current implementation of AHCP is almost completely portable POSIX
code, while a typical DHCPv4 implementation needs to manually craft IP
packets and push them through a raw socket.  (The Babel protocol is
defined over both IPv4 and IPv6, has it's only ever been implemented
over link-local IPv6.  Note that that it can advertise IPv4 routes, it
just happens to carry them over IPv6.)

In short -- IPv6 helps keeping the developers sane.  And that's
hopefully worth a few wasted bits here and there.

-- Juliusz

  reply	other threads:[~2013-01-08  5:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-23 17:27 Dave Taht
2012-11-23 21:26 ` dpreed
2012-11-23 22:41   ` David Lang
2012-11-23 23:26     ` dpreed
2013-01-08  5:18       ` Juliusz Chroboczek [this message]
2012-11-23 21:29 ` Outback Dingo
2012-12-23 17:44 ` Guillaume Fortaine

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

  List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87mwwkz20k.wl%jch@pps.univ-paris-diderot.fr \
    --to=jch@pps.jussieu.fr \
    --cc=bloat-devel@lists.bufferbloat.net \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=dpreed@reed.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