Re: [v6ops] Updating RFC 7084 - alternate logic

[Olorunloba Olopade <[e-mail]>]

Hello Ted,

Would you mind sharing your solution for 2 routers on the same link?

Thanks.

Loba

From: v6ops <[e-mail]> On Behalf Of Ted Lemon
Sent: 02 December 2022 14:24
To: Ole Troan <otroan=[e-mail]>
Cc: IPv6 Operations <[e-mail]>
Subject: Re: [v6ops] Updating RFC 7084 - alternate logic

Sorry, autocorrect was “helping”. I meant non-tree topologies. :)

Op vr 2 dec. 2022 om 09:23 schreef Ted Lemon <[e-mail]<mailto:[e-mail]>>
Op vr 2 dec. 2022 om 08:48 schreef Ole Troan <otroan=[e-mail]<mailto:[e-mail]>>,
Regarding the comment below. If two routers are attached to the same link, they will both request a prefix for the link. That’s not what you want.

We have a solution for this for stub router which would work generally.

Regarding relaying, as you say that will work when there are multiple upstream routers. You just need to know where to relay to. Don’t think we can assume site-wide multicast.

In order for relay to be an option, the router that would act as a relay must already have done DHCPv6 pd to number the link to which the subsidiary requesting router is attached. So there is no need for site-wide multicast here.

Regarding multihoming. MPMH is unlikely to ever work well, so I am also (unhappily) accepting to drop that.

Not ready to give up on this yet, but I agree that it is out of scope.

BTW, regarding Jon-tree topologies, from the perspective of a requesting router, there will always be a direct path to the delegating router. If there are two paths, the same prefix will be assigned over both paths. I think this means that a loop can’t happen and you don’t need spanking tree, but we’d need to think about it. Again out of scope for this document, though—this document is about address allocation, not routing.
Save Paper - Do you really need to print this e-mail?

This email contains information from Virgin Media and/or Telefonica UK Limited (O2) and may be confidential and legally privileged. Statements and opinions expressed in this email or any attachment may not represent either those of Virgin Media or Telefonica UK Limited. Any representations or commitments in this email or any attachment are subject to contract.  The information in this email is intended solely for the attention of the addressee(s) and if you are not the intended recipient please delete it (including any attachment) from your system, and be aware that any disclosure, copying distribution or use of any of this information is not permitted.

If you are in receipt of a suspicious email or you have received an email in error from Virgin Media, please report it to www.virginmedia.com/netreport, or for Telefonica UK Limited (O2), please report it to www.o2.co.uk/help/safety-and-security. 

 Registered offices:

 Virgin Media Limited, 500 Brook Drive, Reading, RG2 6UU. Registered in England and Wales: 2591237

 Telefonica UK Limited, 260 Bath Road, Slough, Berkshire SL1 4DX. Registered in England and Wales: 1743099

 VMED O2 UK Limited, Griffin House, 161 Hammersmith Road, London, United Kingdom, W6 8BS. Registered in England and Wales: 12580944