On Mon, Jun 2, 2014 at 12:36 PM, Markus Stenberg <[email protected]> wrote: > On 2.6.2014, at 22.11, Dave Taht <[email protected]> wrote: >> On Mon, Jun 2, 2014 at 11:44 AM, Steven Barth <[email protected]> wrote: >>> I prepared the first few changes for the upcoming HNCP draft version 01. >>> Most of this is derived from features we already added to our reference >>> implementation. >> I confess to being more interested in a status update on the implementation. >> ? > > I guess we’ll present on the topic in Toronto along the draft update(s), but > highlights since London so far: > > - arbitrary prefix length handling in prefix assignment
selfishly I'm interested right now in hauling a few prefixes an my edge gateway 6 hops to my lab. Stable enough to try that? The documentation was rather lacking the last time I pulled the git tree so it was kind of a mystery to configure in that case... (for those that aren't tracking the work, the git tree can be had via a git clone [email protected]:sbyx/hnetd.git ) /me pulls git tree Wow, ton of updates! cool! > - ad-hoc/guest mode for interfaces (as specified by Steven’s diff to the -00 > draft) > > - support for giving PDs to downstream non-HNCP routers > > - implemented (and also somewhat tested) 6rd, dslite, map, lw4o6 transition > mechanisms > > - SA-aware PCP proxy/server (v4 NAT + v6 FW pinholes) on top of miniupnpd + > new proxy Saw the ipv6 pcp stuff land the other day. Cool. I guess. > > and of course > > - a lot of bugfixes / performance optimizations (notably, Pierre’s PA code > has btries and much better alg both in terms of pseudorandom allocation, as > well as handling the ‘fragmentation’ of prefix space with different sized > allocations) In my case I only have a couple comcast /60s (multiple gateways), and 50 interfaces to configure, so it's a bit much for a home scenario, but a good test of how to break the code... at the moment, though, I'd settle for getting one /61 to the lab somehow. > > We’re working on: > > - improving configuration/management (more knobs that you can turn if you > feel like, and similarly better view of what’s going on; some of this is > already done, but more work is pending) > > - security > > And at some point it would be nice to have also: > > - multicast (sitelocal) > > - UPnP (IGD perhaps via proxy, rest via multicast and/or proxy) > > However, this brings to my mind a thing I’ve been meaning to ask the list for > a while now. > > What is the take on hncp-00 draft format? Should the strictly optional things > (such as SD TLVs) be moved elsewhere? > If so, how about the somewhat more required parts such as PA or border > discovery? > > Cheers, > > -Markus -- Dave Täht NSFW: https://w2.eff.org/Censorship/Internet_censorship_bills/russell_0296_indecent.article _______________________________________________ homenet mailing list [email protected] https://www.ietf.org/mailman/listinfo/homenet
