From: "Ole Trøan" <otroan@employees.org>
To: Dave Taht <dave.taht@gmail.com>
Cc: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] [homenet] Border Router Discovery Protocol
Date: Fri, 12 Oct 2012 09:26:01 +0200 [thread overview]
Message-ID: <D9BD8FEE-0204-43B3-9BBC-78243FC0DACE@employees.org> (raw)
In-Reply-To: <CAA93jw6bo+Og1qL9d3HO8qcuKmHc-K9EqamKvN+AFRGgtfGuAg@mail.gmail.com>
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
next prev parent reply other threads:[~2012-10-12 7:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5C56BF52-CB1B-44DE-B2A4-8EB3517B2C37@gmail.com>
[not found] ` <B75EF5A8-1067-4565-96B9-90DE158CE027@ecs.soton.ac.uk>
[not found] ` <EMEW3|90c7ad52bb14661bc8f0dc7907563b7bo9ACO603tjc|ecs.soton.ac.uk|B75EF5A8-1067-4565-96B9-90DE158CE027@ecs.soton.ac.uk>
[not found] ` <51059699-AA09-4C04-A7CB-2DCACA5587BA@cisco.com>
2012-10-11 22:20 ` [Cerowrt-devel] Fwd: " Dave Taht
2012-10-12 7:26 ` Ole Trøan [this message]
2012-10-12 14:05 ` Michael Richardson
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=D9BD8FEE-0204-43B3-9BBC-78243FC0DACE@employees.org \
--to=otroan@employees.org \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
/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