Michael,
Is there some reason that the flooding mechanism can't distribute the
list of edge CPE routers, and then DHCPv6 can be used in unicast
request/reply to ask those CPE routers for things.
(I would even wonder if the CPE routers shouldn't be identified by their
ULA rather than
Ted,
If we do it another way, whether ZOSPF's or some other way, we have the same
problem in the sense that there will be multiple sources of subnet prefixes.
Yes. This becomes an even uglier problem as you progress into the network,
because while at the edge you can tell that you are
On Nov 16, 2011, at 4:12 PM, Ole Troan o...@cisco.com wrote:
that's exactly reasons why we have started looking at flooding type protocols
in homenet as opposed to request/reply protocols.
it isn't only multiple sources and service discovery that is problematic with
a request/reply protocol,
Sure you should cascade the IA_PD timers into the ND RA prefix
information option lifetime timers. Doh. Wasn't that obvious? Just
because people got it wrong once doesn't mean we should make things even
more complex. In fact, that's all the more reason that Homenet should
address
Is there some reason that the flooding mechanism can't distribute the
list of edge CPE routers, and then DHCPv6 can be used in unicast
request/reply to ask those CPE routers for things.
(I would even wonder if the CPE routers shouldn't be identified by their
ULA rather than self-identifying by
Right now clients don't pick the best one--they just pick one pretty much at
random. But yes, if you have two DHCP servers providing different
information, you need to resolve that. We would have to write a spec to
handle this—it's not handled in the existing protocol.
We need to be
On Nov 16, 2011, at 11:18 AM, Russ White ru...@riw.us wrote:
We need to be aware that not every network may be able to reach the
Internet... So you might need to have an address from every available
DHCP server, not just the best, one, or even a random, one.
Yes, this is part of a problem
We need to be aware that not every network may be able to reach the
Internet... So you might need to have an address from every available
DHCP server, not just the best, one, or even a random, one.
Yes, this is part of a problem space of which I have become keenly aware over
the course of
do we need to?
in a self organizing unmanaged home; if we were to do a combination of a
network wide flooding mechanism and RAs. would we need DHCP in the network
at all?
I am not claiming that we do. However, the problem exists whether we do DHCP
in homenet or not.
yes, indeed.
On Nov 16, 2011, at 1:52 PM, Ole Troan wrote:
We need to be aware that not every network may be able to reach the
Internet... So you might need to have an address from every available
DHCP server, not just the best, one, or even a random, one.
Yes, this is part of a problem space of which
Fred,
We need to be aware that not every network may be able to reach the
Internet... So you might need to have an address from every available
DHCP server, not just the best, one, or even a random, one.
Yes, this is part of a problem space of which I have become keenly aware
over the
I don't much care whose charter it's in. I do think that if we have an idea
that an ISP will allocate an IA_PD to a directly attached router and that
router will then, in some way, sub-allocate subnet prefixes to subnets in the
home, then there is a case in which there are multiple ISPs that
On Nov 16, 2011, at 3:41 PM, Fred Baker f...@cisco.com wrote:
If we do it another way, whether ZOSPF's or some other way, we have the same
problem in the sense that there will be multiple sources of subnet prefixes.
Yes. This becomes an even uglier problem as you progress into the network,
Fred,
The mic line was too long to bring this up:
You suggest using RFC 3633. How about RFC 2894 (Router renumbering) too?
Typo: the draft actually cites RFC 3363, which is not what you intended...
--
Regards
Brian Carpenter
___
homenet mailing
On Nov 15, 2011, at 10:44 AM 11/15/11, Brian E Carpenter wrote:
Fred,
The mic line was too long to bring this up:
You suggest using RFC 3633. How about RFC 2894 (Router renumbering) too?
What device controls the use of RFC 2894? RFC 3633 triggers assignment from
the routers that
On Nov 15, 2011, at 10:44 AM, Brian E Carpenter brian.e.carpen...@gmail.com
wrote:
The mic line was too long to bring this up:
You suggest using RFC 3633. How about RFC 2894 (Router renumbering) too?
Typo: the draft actually cites RFC 3363, which is not what you intended...
Ditto on the mic
On Nov 15, 2011, at 11:17 AM, Ole Troan o...@cisco.com wrote:
- how do you discovery the DHCP server? do you require a hard-wired upstream
port for this to work?
Multicast will reach the DHCP server. Otherwise yes, the hard-wired upstream
port allows this to work.
- what do you do with
17 matches
Mail list logo
