This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/ipv6-wg@ripe.net/
[ipv6-wg] netboot and RAs (was: WG Last Call on draft-ietf-v6ops-cpe-slaac-renum)
- Previous message (by thread): [ipv6-wg] Fwd: [v6ops] WG Last Call on draft-ietf-v6ops-cpe-slaac-renum
- Next message (by thread): [ipv6-wg] Fwd: [v6ops] WG Last Call on draft-ietf-v6ops-cpe-slaac-renum
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Wolfgang Zenker
zenker at punkt.de
Fri Apr 3 15:22:39 CEST 2020
Hi, On Fri, Apr 03, 2020 at 02:33:23PM +0200, Nico Schottelius wrote: > [..] > in this light I am wondering two things: > - Why did the essential netboot related information (filename / server) > never made it into the router advertisements? (I know they exist in > dhcpv6) I think this is related to the main conceptual difference: RAs are periodically multicasted to all nodes on a link, while DHCP(v6) sends tailored information to individual nodes, and only on request. > - Would this be the right platform to discuss an extension to router > advertisements to include a "boot-url" instead of the legacy server + > filename format? It might at least be a place to connect with others interested in working on that, before moving over to the IETF. Wolfgang
- Previous message (by thread): [ipv6-wg] Fwd: [v6ops] WG Last Call on draft-ietf-v6ops-cpe-slaac-renum
- Next message (by thread): [ipv6-wg] Fwd: [v6ops] WG Last Call on draft-ietf-v6ops-cpe-slaac-renum
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ ipv6-wg Archives ]