Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion TUTORIAL.md
Original file line number Diff line number Diff line change
Expand Up @@ -105,7 +105,7 @@ internal.test. 86400 IN NS ins2.internal.test.

### Setup your IP Space - Containers

You manage your IP-Space in DIM with the following objects: `containers`, `pools` and `subnets`. For a minimal layer 2 Management you can tag your pools with `vlan` information.
You manage your IP-Space in DIM with the following objects: `containers`, `pools` and `subnets`. How these compare to the RFC and RIPE terms (aggregate, prefix, subnet, allocation, assignment) is described in [dim/doc/terminology.rst](dim/doc/terminology.rst). For a minimal layer 2 Management you can tag your pools with `vlan` information.

For an enterprise environment where you have several v4 /16 and v6 /32 aggregates to manage, you typically add these directly as containers.

Expand Down
3 changes: 3 additions & 0 deletions dim/doc/ip.rst
Original file line number Diff line number Diff line change
Expand Up @@ -11,6 +11,9 @@ individual node from this tree is called Ipblock (or simply block) and it
represents a CIDR-like block of IP addresses (ex: ``10.0.0.0/8``). The children
Ipblocks represent a subset of the parent address space.

How these terms relate to the RFC and RIPE vocabulary network engineers use
is described in :ref:`terminology`.

Each block can have a status value associated. The most interesting status
values are:

Expand Down
Loading
Loading