Static Ip is only nessesary... if you need it. If you plan on running a daemon that needs to hold onto a fixed address 24/7/52/365/ year after year then static is worth it. If you only need access to the daemon on occasionally (i.e. not critical) then you might be able to get away with a dynamic ip using Dyn DNS or something similar.
Case and point, I occasionally have enabled a few people access to a daemon on my server by simply giving them my current ip address + daemon port. Unless I shutdown my router for a few hours the dynamic ip lease (allocated via DHCP) stays the same for months on end (or unless I or Verizon changes it).
Every now and then it will get bounced and I'll get a new lease, but that happens maybe 1 or 2 times a year. Not enough to cause any noticeable problems. Then there is always Dynamic DNS.
Also, check your providers service. Often providers will block incoming traffic into standard ports on non-commercial accounts, (like port 80, 25, 110, etc.) For example Vz blocks incoming traffic on port 80. So, if I wanted to give someone access to Apache I'd have to put it on a nonstandard port. In some instances this may be a royal PITA. Also , as suggested above, check your TOS. Some providers may piss and moan if they suddenly see large amounts of incoming traffic on a non-commercial account.
Reply With Quote