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/[email protected]/
[ipv6-wg] Fwd: [v6ops] WG Last Call on draft-ietf-v6ops-cpe-slaac-renum
- Previous message (by thread): [ipv6-wg] netboot and RAs (was: WG Last Call on draft-ietf-v6ops-cpe-slaac-renum)
- Next message (by thread): [ipv6-wg] RIPE80 Call for Presentations
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Fernando Gont
fgont at si6networks.com
Sat Apr 4 22:28:37 CEST 2020
Hello, Nico,
On 3/4/20 09:33, Nico Schottelius wrote:
>
> Good morning everyone,
>
> 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)
The reason (other than probably that nobody proposed it) is that in
theory SLAAC is used for basic network configuration. And that for other
stuff, DHCPv6 is used ("M" bit set in RA messages).
> - 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?
This should be done in 6man, rathen than v6ops, since this woudl be a
protocol extension/update.
Thanks,
--
Fernando Gont
SI6 Networks
e-mail: fgont at si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492
- Previous message (by thread): [ipv6-wg] netboot and RAs (was: WG Last Call on draft-ietf-v6ops-cpe-slaac-renum)
- Next message (by thread): [ipv6-wg] RIPE80 Call for Presentations
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ ipv6-wg Archives ]