![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
Which is why *informative* protocols are much more robust than ones that perform queries.
What should be a major point in these discussions is that if the network admin "owns" the end host, then he should be able to configure it to send out the information needed when the machine connects to the network.
Ok, that makes sense as a starting point.
Any querying protocol is overkill, and adds nothing.
Then what does the network owner do with an unmanged host (one that is not owned by the network owner)? Something has to be done, what is the requirement? I don't know.
_______________________________________________ Nea mailing list Nea at ietf.org https://www1.ietf.org/mailman/listinfo/nea