Steven Barth <mailto:[email protected]>
3 June 2014 09:54
Am 03.06.2014 09:40, schrieb Ray Hunter:
Steven Barth <mailto:[email protected]>
3 June 2014 09:15
Well maybe it was worded a bit ambiguously. The main idea behind
this was that an HNCP router should provide "basic connectivity" in
the form of DHCPv4 and DHCPv6-PD to non-HNCP-routers. 7084 routers
should not do anything fancy and just work as legacy devices
believing the homenet is their ISP.
This should not mean you should be able to "tunnel" through 7084
routers or so.
Does that sound sane? And maybe what would be a better wording for
this idea?
It is a sane idea, and I applaud any manufacturer that can prevent
that a lot of 7084 routers are destined for the landfill sooner than
they should be.
I guess this would not only apply to 7084 routers but "current
IPv6-capable homerouters" in general in the end.
But it's still a can of worms and you should think very carefully
whether you want this as a SHOULD in HNCP. I humbly suggest MAY at most.
I guess I'm fine with that.
e.g. What about the topology:
Homenet router ----- Homenet Router
| |
| |
L2 switch e.g. Powerline Ethernet
|
|
7084 router
Which Homenet router acts as the Service Provider Router of 7084?
The behavior is essentially the same as with clients right now. One
homenet router per link is elected as DHCP / DHCPv6-server. The only
addition here is that this elected router now acts as PD-server as well.
That's even before considering the question, what do you do when the
7084 router is inserted between two Homenet routers?
This should be same as the current situation: If you are lucky that
7084 router gives you PD then you have essentially two separate
homenets, if not that homenet router behind the legacy one gets no
(IPv6)-connectivity and probably nasty IPv4 double-NATs. There is not
much you can do though except teach that router to speak homenet.
Homenet router --->PD--7084 router --> PD---- Homenet Router
| | |
| v PD |
| | |
---L2 switch e.g. Powerline Ethernet ------------
|
|
7084 router
PD loops? End users are creative.
In fairness I should declare that I was extremely skeptical about
publishing 7084, and whether it would be harmful for Homenet.
Well I guess it doesn't really do much in favor of homenet by
proclaiming: there is only the ISP on one side and clients on the
other side you need to care about. Well at least it defines some sane
requirements (and some less sane ones) regarding these 2 issues.
It was decided that any updates to 6204 for the WAN interface would be
out of scope for 7084 and that these would instead be deferred into Homenet.
--
Regards,
RayH
_______________________________________________
homenet mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/homenet
