FusiondirectoryIPAM.md

@@ -16,35 +16,38 @@ The demand was
 
 ##### General info
 
-* Organisation
-* Name
-* State (active/non active)
-* Type
-* Note
-* applicant
-* Allocation date
-* Release date 
+* Organisation   (link, could link to the company branch)
+* Name         (text, name of this subnet for identification)
+* State (bolean, but show in text to the user active/non active)
+* Type (text, use  type, ex: lan, wifi, wan etc)
+* Description (text, can be anything we want to say about this entry)
+* applicant (text, person who asked for it)
+* Allocation date ( ldap format date, date of creation)
+* Release date    (ldap format date, date of release)
 
 ##### IP Informations
 
-* Subnet IP : 10.246.24.0
+* Subnet IP : 10.246.24.0 
 * Netmask : 255.255.252.0/22
 * Gateway ip: 10.246.27.254
 * IP de broadcast: 10.246.27.255
 
+all are ip adress object type
+
+
 #### Vlan attributes
 
 VLAN objects contain a name, an inner VLAN ID (0-4094), and an optional metro QinQ VLAN ID (0-4094) for the outer tag. The VLAN IDs don't need to be interpreted by anything in Fusion Directory, they're purely for our use/use by dynamic networking services. FreeRADIUS can dynamically assign VLANs (both tagged an untagged) to devices as they complete Mac-Auth or 802.1X, and that's what we'll be using the VLAN IDs for. 
 
 ##### General info
 
-* Organisation
-* Name
-* Inner VLAN ID
-* QinQ VLAN ID
-* State
-* Description
-* Applicant for the VLAN
+* Organisation   (link, could link to the company branch)
+* Name         (text, name of this subnet for identification)
+* Inner VLAN ID (integer, from 1 to 4096)
+* QinQ VLAN ID (integer, form 1 to 4096)
+* State (bolean, but show in text to the user active/non active)
+* Description (text, can be anything we want to say about this entry)
+* Applicant for the VLAN ((text, person who asked for it)
 
 ### system plugin