On Thu, Apr 4, 2024 at 7:06 PM Tim Chown <Tim.Chown@xxxxxxxxxx> wrote: > > The thing is that the host behaviour is explicitly (and intentionally) > > out of scope. For me, as a network administrator, it doesn't matter > > how exactly the client configures that address: my network > > design/topology would be the same. The client can be a RFC7084-type > > router (that's what happens when someone plugs a CPE to an access > > port), or use smth like rfc7278 - or smth else. Up to the client, the > > network routes thet whole prefix to that device, do whatever you want > > with it. > > OK, so maybe make it clearer that it is out of scope, as I was expecting to find some comment about it, and I could not. The last paragraph of the Introduction states that: "This document focuses on the behaviour of the network. Host behaviour is not defined in this document." Do you think we need to make it more clear? > we do frequently have campus admins asking how they get host entries into the DNS with SLAAC, so it’s a FAQ. Yes, I agree it's a problem to solve, but I think it might be more in scope for my 6MOPS draft...What do you think? -- Cheers, Jen Linkova -- last-call mailing list last-call@xxxxxxxx https://www.ietf.org/mailman/listinfo/last-call
