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 <[email protected]> Date: Thu, Oct 11, 2012 at 4:50 AM Subject: Re: [homenet] Border Router Discovery Protocol To: Tim Chown <[email protected]> Cc: "[email protected] Group" <[email protected]> >> 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 [email protected] 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 [email protected] https://lists.bufferbloat.net/listinfo/cerowrt-devel
