This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
2_x:datamodel:subnet-blocks [2019/12/05 11:39] – [Tabs] cnaud | 2_x:datamodel:subnet-blocks [2019/12/05 12:03] – [Creating a new Subnet Block] cnaud | ||
---|---|---|---|
Line 36: | Line 36: | ||
{{ classlist_ipv4subnetblock.png }} | {{ classlist_ipv4subnetblock.png }} | ||
+ | |||
{{ classlist_ipv6subnetblock.png }} | {{ classlist_ipv6subnetblock.png }} | ||
Line 66: | Line 67: | ||
An implicit but intuitive set of rules must be followed when a subnet block is created: | An implicit but intuitive set of rules must be followed when a subnet block is created: | ||
* A subnet block belongs to a unique organization | * A subnet block belongs to a unique organization | ||
- | * A subnet block can be delegated from a given organization to an organization. Once done, the block will still appear in the parent organization but will be managed from the child organization. | ||
* A subnet block can be fully contained within another subnet block. We talk, then, about child block or parent block. | * A subnet block can be fully contained within another subnet block. We talk, then, about child block or parent block. | ||
* Two blocks cannot share the same name | * Two blocks cannot share the same name |