From: Markus Stenberg <markus.stenberg@iki.fi>
To: Steven Barth <cyrus@openwrt.org>
Cc: homenet@ietf.org, Markus Stenberg <markus.stenberg@iki.fi>,
cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] [homenet] pushing the bird faster
Date: Wed, 8 May 2013 12:27:46 +0300 [thread overview]
Message-ID: <B58EE4A0-D170-475A-A974-988D1DAF25F7@iki.fi> (raw)
In-Reply-To: <518A18FA.4030600@openwrt.org>
On 8.5.2013, at 12.20, Steven Barth <cyrus@openwrt.org> wrote:
> On 08.05.2013 11:07, Dave Taht wrote:
>> Unless you wish to maintain these modifications forever, it is helpful
>> to seek consensus with the mainline developers of these tools to push
>> your patches in a mutually acceptible form. I would suspect that dnsmasq
>> and odhcp6c devs would be amiable to a discussion at the very least.
> Speaking for odhcp6c I have looked into the homenet changes yesterday and I don't see it as a big hassle to merge these features into the main branch at some point once they have an official IANA number and the specs are somewhat stable.
>
> Also feel free to contact me if you are thinking about getting anything IPv6-related upstream to OpenWrt and we can discuss that or you can of course also use the official channels, mailing lists and so on.
That's underlying problem with both dnsmasq and odhcp6c forked changes - we use IOS-specific prefix class option # that is NOT from IANA, and I'd rather not see it in wide use for obvious reasons.
And as a general point on odhcp6c front, I think a better method of expressing 'extra prefix-specificoptions' should be found than just adding more entries to the CSV list of ENV_PREFIXES. In my experience, long lists of CSV-style entries become rather awkward to handle if you want to be futureproof; key=value within (or something else) is much better.
Cheers,
-Markus
next prev parent reply other threads:[~2013-05-08 9:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAA93jw7Tz49OQ884k3ZRWk66iNqoPpYSpDj9Oy_9ztZutz-RKA@mail.gmail.com>
[not found] ` <loom.20130507T131132-321@post.gmane.org>
2013-05-08 9:07 ` Dave Taht
2013-05-08 9:20 ` Steven Barth
2013-05-08 9:23 ` Dave Taht
2013-05-08 9:27 ` Markus Stenberg [this message]
2013-05-08 9:32 ` Steven Barth
2013-05-08 10:22 ` Dave Taht
2013-05-08 10:28 ` Markus Stenberg
2013-05-08 10:34 ` Lorenzo Colitti
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=B58EE4A0-D170-475A-A974-988D1DAF25F7@iki.fi \
--to=markus.stenberg@iki.fi \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=cyrus@openwrt.org \
--cc=homenet@ietf.org \
/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