Changes between Version 9 and Version 10 of GeniApiIdentifiers
- Timestamp:
- 01/15/14 13:10:54 (10 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
GeniApiIdentifiers
v9 v10 101 101 `vlan` 102 102 A shared VLAN, that may cross slices. This VLAN may or may not cross aggregates, as in the GENI openflow mesoscale. VLAN URNs should name the VLAN, not identify the specific VLAN tag, as that may vary across aggregates and switches. 103 `tool` 104 A GENI tool (i.e. a hosted experimenter tool like [https://portal.geni.net the GENI Portal]). The `toplevelauthority` indicates the authority certifying that the holder of a certificate naming this URN operates a tool with the given name. 103 105 104 106 Additional types may be defined in the future. … … 130 132 - User URNs (which contain the authority name and the username) are required to be temporally and globally unique. 131 133 134 '''Tool''': 135 - Tool names are case-insensitive internally, though they may be case-sensitive in display. 136 - EG !JohnSmth as a display name is johnsmth internally, and there cannot also be a user `JOHNSMTH`. 137 - Tool names should begin with a letter and be alphanumeric or underscore, hyphen, at sign or period: ('^[a-zA-Z][a-ZA-Z0-9\-_@\.]{0,63}$'). 138 - Tool names are limited to 64 characters. 139 - Tool URNs (which contain the authority name and the tool instance name) are required to be temporally and globally unique. 140 - Tool names should encode both the tool type and instance. For example `portal-gpo` or `genidesktop-uky`. 141 132 142 {{{ 133 143 #!comment