-
Notifications
You must be signed in to change notification settings - Fork 1
Home
otroan edited this page Sep 13, 2010
·
16 revisions
Which transition mechanisms should be supported?
- 6rd
- ds-lite
- 6to4, ISATAP, softwires hub and spoke, configured tunnels, tunnel brokers, ipsec
Should any transition mechanism be enabled by default? Or should they be enabled by SP provisioning? What about automatic sunsetting when e.g native IPv6 is available, or ds-lite in the case of native IPv4?
Should we support two IPv6 CE routers in the home, each connected to separate SPs?
Should we support an IPv6 CE router with two connections to separate SPs?
Should we support multi-homing to non-congruent topologies aka walled-garden or VPN?
- NAT66
- DHCPv6 route option / RFC4191
- SAS/DAS policy in DHCP option
- Signalling to hosts to pick separate source address
- Automatic detection of other routers in the home
Should we handle the case where an SP changes the IPv6 prefix instantly. E.g IPv4 address changes for 6rd or fail-over causes instant renumbering with DHCPv6 PD.
- How to detect that a prefix has changed?
- Low lifetimes in RA / PD
- L2 state change
- CE advertise prefix with preferred lifetime of 0 when detecting a renumbering event
Should we handle a case with more than one router in the home?
- Hierarchical PD?
- Zero-conf routing?
- Multicast routing protocol
- MLD proxy
- Advanced security
- Firewall control protocols (PCP, UPnPIGD…)
- Service discovery for discovering the IPv6 CE router
- QoS. Default queueing policy
- DNS server or proxy.
- Handling of home reverse and forward zones. Dnssec, dynamic update?
- Use of BFD echo mode for BNG state maintenance.
- Unicast dynamic routing support. OSPF, RIPng