* Re: [Cerowrt-devel] [homenet] Border Router Discovery Protocol
2012-10-11 22:20 ` [Cerowrt-devel] Fwd: [homenet] Border Router Discovery Protocol Dave Taht
@ 2012-10-12 7:26 ` Ole Trøan
2012-10-12 14:05 ` [Cerowrt-devel] Fwd: " Michael Richardson
1 sibling, 0 replies; 3+ messages in thread
From: Ole Trøan @ 2012-10-12 7:26 UTC (permalink / raw)
To: Dave Taht; +Cc: cerowrt-devel
Dave et al,
in my view the most promising proposal for prefix assignment is here:
http://tools.ietf.org/html/draft-arkko-homenet-prefix-assignment-02
can quite easily be expanded to support IPv4 as well.
there are a couple of implementations underway, and a possibly interop event at the Atlanta IETF.
cheers,
Ole
> some activity on a needed standardization front...
>
> I would like to come up with ways, with ipv4, that will prevent
> double-or-worse nat from happening when multiple routers are plugged
> into together. With ipv6, to come up with good ways of distributing
> uniquely delegated ipv6 subnets out of an ISP's assigned prefixes.
>
>
> ---------- Forwarded message ----------
> From: Ole Trøan <ot@cisco.com>
> Date: Thu, Oct 11, 2012 at 4:50 AM
> Subject: Re: [homenet] Border Router Discovery Protocol
> To: Tim Chown <tjc@ecs.soton.ac.uk>
> Cc: "homenet@ietf.org Group" <homenet@ietf.org>
>
>
>>> PS: I'd also be quite happy to see BRDP go out as an
>>> Experimental status RFC initially, whether through
>>> the IETF track, IRTF Routing RG, or the ISE-track.
>>> BRDP seems very useful and useful protocols tend
>>> to self-deploy into environments where they are useful.
>>
>> We also have Eric Kline's draft in similar space: draft-kline-default-perimeter-00.
>>
>> Both can hopefully contribute to the solution for this problem space in homenet.
>
> I have read the BRDP framework document, but I failed to understand
> how BRDP solves the problem of how a border is discovered.
> it explains well how to act when a border has been established, but I
> don't understand how BRDP helps getting to that point. pointers?
>
> cheers,
> Ole
>
> _______________________________________________
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/mailman/listinfo/homenet
>
>
> --
> Dave Täht
>
> Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/subscribe.html
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [Cerowrt-devel] Fwd: [homenet] Border Router Discovery Protocol
2012-10-11 22:20 ` [Cerowrt-devel] Fwd: [homenet] Border Router Discovery Protocol Dave Taht
2012-10-12 7:26 ` [Cerowrt-devel] " Ole Trøan
@ 2012-10-12 14:05 ` Michael Richardson
1 sibling, 0 replies; 3+ messages in thread
From: Michael Richardson @ 2012-10-12 14:05 UTC (permalink / raw)
To: Dave Taht; +Cc: cerowrt-devel
>>>>> "Dave" == Dave Taht <dave.taht@gmail.com> writes:
Dave> some activity on a needed standardization front...
Dave> I would like to come up with ways, with ipv4, that will
Dave> prevent double-or-worse nat from happening when multiple
Dave> routers are plugged into together. With ipv6, to come up with
Dave> good ways of distributing uniquely delegated ipv6 subnets out
Dave> of an ISP's assigned prefixes.
I suggest from a specification point of view, that we first solve it for
IPv6, and then, in sunset4 (maybe?) extend this for IPv4 as appropriate.
From an implementation point of view, CeroWRT can pioneer any
not-yet-standardized protocol, and this would be valuable input to the
process.
--
] He who is tired of Weird Al is tired of life! | firewalls [
] Michael Richardson, Sandelman Software Works, Ottawa, ON |net architect[
] mcr@sandelman.ottawa.on.ca http://www.sandelman.ottawa.on.ca/ |device driver[
Kyoto Plus: watch the video <http://www.youtube.com/watch?v=kzx1ycLXQSE>
then sign the petition.
^ permalink raw reply [flat|nested] 3+ messages in thread