List of TODO entries

Todo

• Split off in to appendix and create diagram.
• Describe zone signing keys and key siging key.
• Puppet module.

(The original entry is located in /home/kanarip/devel/src/kolab/ref-arch.git/source/appendices/perimeter-network-services-guidelines.rst, line 42.)

Todo

Rant on DNSSEC support on most CEs / in other environments. Rant on MiM attack vectors such as transparent proxies.

(The original entry is located in /home/kanarip/devel/src/kolab/ref-arch.git/source/appendices/perimeter-network-services-guidelines.rst, line 73.)

Todo

Articulate the necessity using the simplest example.

(The original entry is located in /home/kanarip/devel/src/kolab/ref-arch.git/source/appendices/split-dns-horizon.rst, line 7.)

Todo

Articulate the methodology to avoid problems.

(The original entry is located in /home/kanarip/devel/src/kolab/ref-arch.git/source/appendices/split-dns-horizon.rst, line 11.)

Todo

Articulate the need to use internally, extensively.

(The original entry is located in /home/kanarip/devel/src/kolab/ref-arch.git/source/appendices/split-dns-horizon.rst, line 15.)

Todo

Explain.

(The original entry is located in /home/kanarip/devel/src/kolab/ref-arch.git/source/glossary.rst, line 11.)

Todo

Perhaps explain what a load-balancer is/does.

(The original entry is located in /home/kanarip/devel/src/kolab/ref-arch.git/source/glossary.rst, line 96.)

Todo

Explain

(The original entry is located in /home/kanarip/devel/src/kolab/ref-arch.git/source/glossary.rst, line 102.)

Todo

Explain.

(The original entry is located in /home/kanarip/devel/src/kolab/ref-arch.git/source/glossary.rst, line 176.)

Todo

Explain.

(The original entry is located in /home/kanarip/devel/src/kolab/ref-arch.git/source/glossary.rst, line 182.)

Todo

Explain.

(The original entry is located in /home/kanarip/devel/src/kolab/ref-arch.git/source/glossary.rst, line 188.)

Todo

Explain what a transparent forward proxy is.

(The original entry is located in /home/kanarip/devel/src/kolab/ref-arch.git/source/glossary.rst, line 194.)

Todo

Explain how this terminology is misleading.

(The original entry is located in /home/kanarip/devel/src/kolab/ref-arch.git/source/glossary.rst, line 204.)

Todo

Explain what a transparent reverse proxy is.

(The original entry is located in /home/kanarip/devel/src/kolab/ref-arch.git/source/glossary.rst, line 210.)

Todo

Provide some short text here, because this is the front page for the entire thing.

(The original entry is located in /home/kanarip/devel/src/kolab/ref-arch.git/source/index.rst, line 7.)

Todo

• Considerations for Corporate Infrastructure
  • No public registration,
  • No invoicing, albeit there may need to be accounting (–> PACK)
• Considerations for Hosted Infrastructure (ASP/ISP)
  • Could be with or without public registration
  • Likely involves invoicing (–> PACK)
  • May need to integrate with existing services (–> PACK)
• Considerations for Co-located Infrastructure
  • Dedicated customer infrastructure, but many-many of them (–> PACK)

(The original entry is located in /home/kanarip/devel/src/kolab/ref-arch.git/source/index.rst, line 12.)

Todo

This graphic only expresses inbound traffic. It isn’t structured properly. Outbound traffic should be taken in to account. Discretionary, non-transparent proxies should be used for selected systems. Mandatory transparent proxies should be used for all nodes.

(The original entry is located in /home/kanarip/devel/src/kolab/ref-arch.git/source/infrastructure/network-topology-overview.rst, line 35.)