I presented a scenario where Network Engineering allows certain classs C (192.168.5.0) traffic to be propogated, advertised, etc across a class A (10.0.0.0) network, which can be a problem when those addresses try to reach multi-homed machines that have truly private networks with 192.168.5.0 addresses. The consensus is, it's their network, they are in charge (and are responsible for just this type of thing), they are not violating anything (except perhaps common sense). (the feedback was "The RFC1918 is just an internet convention"). We sysadmins have to trust them to manage the network and not to forget about the private networks that they know about. If they don't forget, that's fine with me. They agreed/requested to meet and update their overall network diagram with our information (for what must be the third time). Thanks to "Todd A. Fiedler" <todd.a.fiedler@mail.sprint.com> Benjamin Ritcey <sunmanagers@ritcey.com> "Mortensen, Henrik" <henrik.mortensen@csfb.com> "Doug Floer" <dfloer@topsoft.ca> "Haywood, Steven" <shaywood@hurricaneseye.com> _______________________________________________ sunmanagers mailing list sunmanagers@sunmanagers.org http://www.sunmanagers.org/mailman/listinfo/sunmanagersReceived on Thu Nov 14 13:24:25 2002
This archive was generated by hypermail 2.1.8 : Thu Mar 03 2016 - 06:42:58 EST