On 12-03-03 4:15 PM, "Brian E Carpenter" <brian.e.carpen...@gmail.com> wrote: > >I noticed that there is no section discussing operations and management >as a topic on its own. It seems to me that this is needed, even if what >it says is that the architecture must ensure that manual operations and >management are either not needed at all, or are absolutely minimal, >or are remotely accessible to specialists.
I would fully agree with Brian's comments here. This is topic often left out but is important for real network deployments. > >A couple of days ago I had no IP connectivity at home. The conversation >with the ISP help desk responder included her asking me which model >of D-Link I have, and talking me through its menus. Of course I'd >done all that before I called, but it struck me as ridiculous that >any help desk would ask a domestic customer to do that. It will only >be worse for real homenets. This is a real issue today and mechanisms to deal with this in a more effective matter is important. Having CS reps walk people through config menus/pages is problematic (since reps will not be able to learn and/or keep with all the device variants). Brian's comments do exemplify an issue which will become extremely problematic in the future when Home Net complexity increases. Just adding in IPv6 (to IPv4) connectivity to this mix has highlighted challenges in traditional troubleshooting methods. Part of this was due to the added complexity of IPv6 (since few customers/support reps had experience in this area) and the other was that troubleshooting tools for IPv6 were not as readily availble. My comment was not to focus on IPv6 specifically- but that of new functionality. I think a discussion (at minimum) would be warranted here to see what opportunities we have to address this (soon to be) issue. Regards, Victor K > > Brian > _______________________________________________ homenet mailing list homenet@ietf.org https://www.ietf.org/mailman/listinfo/homenet
