User:Howard C. Berkowitz/ToDo

Yes, I know I should use the workgroup status system. It hates me. I can write articles faster than put them into a plan.

Computers

Meta-articles

I see a need for a set of capstone/core/meta-articles that are below the level of "Computers", although they perhaps do belong on the Workgroup page. These go under the heading "Networking". I'm debating whether other than IP networking is still relevant; my thought is that some PSTN and probably SS7 material is appropriate.

There is "transmission stuff" that needs to be in there, which, with GMPLS, constrained link state routing for optical networks, etc., perhaps needs a meta-article talking about recovery frameworks, starting with MPLS and SONET-NGS, and branching from there. A good cellular person could help, as well as someone more RF-expert.

DNS

• Go back into Domain Name System and update as required by http://www.ietf.org/rfc/rfc2181.txt.
• Keep working on Domain Name System security, which is bound to generate more about public key infrastructure and Internet Protocol security architecture. Find someone that understands the place of the older KEY, SIG, etc., better than I do. Is it that they are secret key?
• Really need someone who knows the subject to write intellectual property.

Security

• Flesh out communications security, although decide if it should be information security or information assurance before committing the metadata and any substantial links to it.
• Capstone on Internet security
  • Internet firewall
  • Transport layer security
  • Public key infrastructure
  • Intrusion detection
  • Domain Name System security

IPv6

Continue work on Internet Protocol version 6, which also interlaces with the preceding three subjects. Create articles, or at least stubs, where I have expertise; try to recruit authors to work on gaps, or just to offload.

Routing

• Continue on link state routing and OSPF, the latter including Version 2 and Version 3 (for IPv6). Check up on traffic engineering extensions for V6.
• Get some reasonable content into distance vector routing and routing information protocol; try to get someone to write about diffusing update routing and Enhanced Interior Gateway Routing Protocol.
• More about path vector routing, Internet routing policy, etc.

Health sciences and healing arts

• Create/update articles defining medical specialties and subspecialties. Avoid lots of repetition separate articles for the more interdisciplinary subspecialties, such as hospice and palliative medicine (as a subset of the hospice movement), sleep medicine, etc., which can be reached through different pathways. In some cases, where topic articles exist, as in critical care and pain, either add short section on training/certification or at least create stub for critical care medicine and and pain medicine. pain management is an interdisciplinary superset that includes pain management, but also nonphysician practitioners.

Catalog, perhaps, of interdisciplinary medical subspecialties?

• • Anesthesiology
  • Pathology; stub done. Thinking about the best way to organize the tests in clinical pathology.
  • Preventive medicine
  • Internal medicine
    • Cardiology
    • Infectious disease
• Pain seems to have had pain physiology cloned, but not removed from the main article. General cleanup there; the lead of pain comes across as more philosophical than scientific. Both are needed, but pain is one of the most undertreated or inappropriately treated real medical conditions. Started chronic widespread pain and need to back up to chronic pain. Not sure where appropriate long-term opioid therapy for non-terminal pain should go, but it needs to be here somewhere.
• Suggest, in appropriate places, the health sciences/healing arts split is dysfunctional. The National Institutes of Health manages not to fall apart with the National Center for Complementary and Alternative Medicine present, and, while there are questions about the rationality of the rules, the Food and Drug Administration has oversight (and opinions) about homeopathic remedies.

Military

Military skills/branches/operational techniques/major platforms

The U.S. Army is getting remarkably silly about security. I can find detailed operating manuals for tanks, but every formal definition of the Armor Branch (i.e., responsible for tanks and other such vehicles) is behind a security portal.

• Armor
• Combat engineer
• Cavalry
• Ocean escort
• Convoy

Military History

• write Operation LINEBACKER II; replace existing text in Vietnam War
• continue Vietnam War improvement
• Think more about WWII air war
• Think about getting the multiple coverage of the sub-battles of the Battle of Leyte Gulf straightened out, so it's possible, for example, to have a consistent wikilink to the best coverage of the Battle of Surigao Strait or the Action off Samar/Battle of San Bernadino Strait (and get a standard name for it)
• Try to recruit a Canadian for Battle of Vimy Ridge, but at least link the Vimy counterbattery material (also tie to C-RAM Counter-Rocket, Artillery and Mortar Forum question about naming convention into First World War, and be sure it's linked into Artillery
• Again, try to recruit Commonwealth person, but Battle of Gallipoli (Gallipoli campaign?) under Dardanelles campaign (as well as equivalent "battle" subarticle for naval attempt to force the straits)

Canadiana category

• Battle of Vimy Ridge
• Arthur Currie
• Andrew McNaughton
• Dieppe raid (Operation JUBILEE)
• Harry Crerar
• Romeo Dallaire (might have a Topic Informant)