From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from ams-iport-2.cisco.com (ams-iport-2.cisco.com [144.254.224.141]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "ams-iport-2.cisco.com", Issuer "Cisco SSCA2" (verified OK)) by huchra.bufferbloat.net (Postfix) with ESMTPS id 9ABFB21F16F for ; Fri, 12 Oct 2012 00:26:04 -0700 (PDT) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Av8EAMTEd1CQ/khL/2dsb2JhbABEv1qBCIIgAQEBBAEBAQ8BWwsQCxEDAQINIicBJwgGDwQbB4diC5lToBeLUIVdYAOTQINCjTCBa4Jv X-IronPort-AV: E=Sophos;i="4.80,576,1344211200"; d="scan'208";a="77415300" Received: from ams-core-2.cisco.com ([144.254.72.75]) by ams-iport-2.cisco.com with ESMTP; 12 Oct 2012 07:26:01 +0000 Received: from dhcp-lys01-vla250-10-147-112-212.cisco.com (dhcp-lys01-vla250-10-147-112-212.cisco.com [10.147.112.212]) by ams-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id q9C7Q0KJ029816 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 12 Oct 2012 07:26:01 GMT Content-Type: text/plain; charset=iso-8859-1 Mime-Version: 1.0 (Mac OS X Mail 6.1 \(1498\)) From: =?iso-8859-1?Q?Ole_Tr=F8an?= In-Reply-To: Date: Fri, 12 Oct 2012 09:26:01 +0200 Content-Transfer-Encoding: quoted-printable Message-Id: References: <5C56BF52-CB1B-44DE-B2A4-8EB3517B2C37@gmail.com> <51059699-AA09-4C04-A7CB-2DCACA5587BA@cisco.com> To: Dave Taht X-Mailer: Apple Mail (2.1498) Cc: cerowrt-devel@lists.bufferbloat.net Subject: Re: [Cerowrt-devel] [homenet] Border Router Discovery Protocol X-BeenThere: cerowrt-devel@lists.bufferbloat.net X-Mailman-Version: 2.1.13 Precedence: list List-Id: Development issues regarding the cerowrt test router project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Oct 2012 07:26:05 -0000 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... >=20 > 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. >=20 >=20 > ---------- Forwarded message ---------- > From: Ole Tr=F8an > Date: Thu, Oct 11, 2012 at 4:50 AM > Subject: Re: [homenet] Border Router Discovery Protocol > To: Tim Chown > Cc: "homenet@ietf.org Group" >=20 >=20 >>> 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. >>=20 >> We also have Eric Kline's draft in similar space: = draft-kline-default-perimeter-00. >>=20 >> Both can hopefully contribute to the solution for this problem space = in homenet. >=20 > 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? >=20 > cheers, > Ole >=20 > _______________________________________________ > homenet mailing list > homenet@ietf.org > https://www.ietf.org/mailman/listinfo/homenet >=20 >=20 > --=20 > Dave T=E4ht >=20 > 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