could anyone point me to where TCP/IP version 6 is fully described in a "final release"?

i avoided upgradeing from ipv4 to ipv6 because ipv6 was never finalized or documented "by rule of law". different isp and OS used it differently - and you didn't know if ipv6 software would change your local routes or not given any "bit settings in addresses or payload" which scared me, the discovery and such.

i'd like to run ipv6 but i dont want to hire an IT team to get it to run like ipv4

and how do i get a "static address". they promised with ipv6 32bit people could easily get a static IP. but as far as i can tell it's been a lie so far: they cost money and isp's block use of them: see [[signal jamming]]

RECAP: ipv6 has so many new features and options having nothing to do with "normal traffic" i'm unsure an individual can set it up "safely" without missing important things (ie, like whether ipv6 code allows local route changes: and how to block it if it does, or like if ipv6 allows discovery by anonymous/foreigners of local LAN networks, and etc, important things like that)

can ipv6 be "almost as easy as ipv4" ? and if so ... where is the manuals / docs to read ? last time i read "linux documentation project" they said ipv6 is experimental, isp support it differently, and software has unguessable features. is ipv6 in stone and IEEE finalized yet?

where is an "easy guide" that shows how to use ipv6 safely like the "Linux documentation project" NAG (network administrator's guide) did for ipv4 ?

(an advance issue about ipv6 tcp/ip is: i saw on www.wikipedia.org that ipv6 does not respect packet protocol layer barries in frame relay or tcp/ip either, meaning it stores requests to run stored functions outside of its boundry (in ipv4/frame not allowed). that the new cell carrier phones all require boundary breakage and code interpretation by towers "to work". the article doesn't explain why they could not use the boundaries as it is certainly EASILY possible they could follow rules/boundaries and choose to break every rule instead. for example: in ipv6 and or cell is possible that options in transport layer store bits that enact code in other layer to bypass or alter, say, software delivery layer to call back a different layer, and so on)

are these "programs stored and run outside of their supposed physical boundaries" a virus issue for home routers or cell towers or even a web browser ?