Re: RFC: Implementation of RFC 7217 [A Method for Generating Semantically Opaque Interface Identifiers, with IPv6 Stateless Address Autoconfiguration (SLAAC)]
- Reply: Guido Falsi : "Re: RFC: Implementation of RFC 7217 [A Method for Generating Semantically Opaque Interface Identifiers, with IPv6 Stateless Address Autoconfiguration (SLAAC)]"
- In reply to: Ronald Klop : "Re: RFC: Implementation of RFC 7217 [A Method for Generating Semantically Opaque Interface Identifiers, with IPv6 Stateless Address Autoconfiguration (SLAAC)]"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Wed, 09 Apr 2025 11:10:47 UTC
On 4/9/25 12:51, Ronald Klop wrote: > Hi, > > Next to hostuuid you could add a jailname in the mix. > > That is what ether_gen_addr(9) does to make it easier to prevent > collisions while copying jails around or run a jail on a readonly shared > base filesystem. The RFC is very clear on what should be used to derive the address, so I'm not very keen on adding things around. The UUID should be changed when copying jails that run in parallel, they ARE different machines. although I am also at fault here. But the jailname is the correct parameter? This would change the address if the name is changed, which could be ok I guess. I'd also add this parameter only if actually jailed, skipping it for the host. My real issue with this approach is, the RFC is quite detailed on hash parameters. Will the implementation still be conforming if adding local ones? -- Guido Falsi <madpilot@FreeBSD.org>