I've been "terminated" (without cause) from about half the jobs I've worked and I've never been given any notice. Faceless bean counters make decisions without regards to the consequences of their decisions. Security best practices never allow for an employee to know that they are getting terminated ahead of time. One place I worked at, Andrew Corporation, had my personal items boxed up over the weekend so when I came in Monday morning, they were all ready to walk me out. If you do leave and give notice, never tell your former employer about your new job. I worked at Platinum DB for four years, decided it was time to move on and took a job. Platinum DB contacted my new employer and made a lot of baseless accusations that sabotaged my new job completely. So word to the wise, never update your "linked-in" right away with your job information. With that, no one can ever say it is "professional" to give two weeks notice and do so with a straight face. Your individual relationships and contacts are much more important than your relationship with any one company, that's where you get your references for future jobs. If companies were loyal, you wouldn't see so many H1B visas getting trained as cheap labor replacements. I've kept myself relevant so I've always been able to find work, but IT wages are dropping because of H1B visas. Like my title says, there is no such thing as company loyalty anymore, almost all companies could care less.

In your scenario where Company A buys Company B, all you need to do is identify resources that require two-way tcp communication and NAT private-to-private IP space. This is actually what Cisco recommends on their website as one of the practical applications for NAT. Problem solved, you don't need unique IPv4 space to make this happen, all you need is NAT. In the perfect world, we would have longer address space to start, but who could have ever imagined the proliferation of IP. Like Vincent Cerf's T-shirt he sells that says "IP on everything" is really the truth these days. With that said, we should do our best to conserve IPv4 space where it is practical to do so. 95% of a business day-to-day activities don't require workstations to have public IP addresses. The few that do, legitimate exceptions can be made. If everyone followed the rules in RFC2050, we wouldn't be in this mess today. This is simply the reality. No need to flame war -- it is what it is. The question is, how are we going to react to the situation to improve it for everyone?

I got shit canned by University of Chicago Hospitals for threatening to report their network manager, Tony Rubino to ARIN for misuse of their multiple class B address space. As the SOP, they use public address space on workstations that do not have internet access. RFC1918 address space would have been more appropriate here. Their utilization, as seen by the outside internet, is less than 1%. Last laugh will be on them when they are effectively forced to deploy IPv6 (or RFC1918 space for that matter) in the future. It's great, as a network engineer, to be able to say, "I TOLD YOU SO!" Many of these large companies, like Ford and IBM do the same thing as U of C Hospitals. I've worked for Ford and IBM as well in the past and the mindset is all ego based. One Ford engineer told me "We're too big to have ARIN take back space." Push is coming to shove and in 2011 I expect ARIN to be auditing and scrutinizing companies a lot closer on their RFC2050 compliance as outlined in the ARIN IP usage/utilization agreement. Just my two cents worth.