From: Dave Taht <dave.taht@gmail.com>
To: Markus Stenberg <markus.stenberg@iki.fi>
Cc: homenet@ietf.org, cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] [homenet] pushing the bird faster
Date: Wed, 8 May 2013 03:22:36 -0700 [thread overview]
Message-ID: <CAA93jw7spujE9TTe0SE6u-8Q4sxGv82+JaniCQxNUO_twG3WLg@mail.gmail.com> (raw)
In-Reply-To: <B58EE4A0-D170-475A-A974-988D1DAF25F7@iki.fi>
[-- Attachment #1: Type: text/plain, Size: 1471 bytes --]
On Wed, May 8, 2013 at 2:27 AM, Markus Stenberg <markus.stenberg@iki.fi>wrote:
> 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.
>
I have few problems with IOS setting a default standard, open source
following it, and the IANA blessing it later. :) That said, what is the
status of the IANA application? Link?
--
Dave Täht
Fixing bufferbloat with cerowrt:
http://www.teklibre.com/cerowrt/subscribe.html
[-- Attachment #2: Type: text/html, Size: 1971 bytes --]
next prev parent reply other threads:[~2013-05-08 10:22 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
2013-05-08 9:32 ` Steven Barth
2013-05-08 10:22 ` Dave Taht [this message]
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=CAA93jw7spujE9TTe0SE6u-8Q4sxGv82+JaniCQxNUO_twG3WLg@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=homenet@ietf.org \
--cc=markus.stenberg@iki.fi \
/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