Big O Object Specs

Under construction
2/03/00 Created by SY
4/21/00 Reviewed by Rob
12/19/00 Last modified

Table of Contents

General Requirements

The Big O pages are the main user interface. They cover most of NetDB's functionality- adding, modifying, deleting all the Big O objects (domain, group, user, admin team, network, node). They do not include the Little O pages. Little O pages allow access to management functions that are not included in the current NetDB2 telnet interface. Little O's include objects like make, model, dhcp options, etc.

Input Requirements

This section describes the different types of field types. All input fields should escape html characters properly. Also, double quotes are not allowed in text input data except for DHCP options

Field Types- Summary

  1. DNS Name field- must obey DNS naming rules
  2. Non-DNS name, no spaces
  3. Non-DNS names, spaces allowed
  4. String- any characters allowed
  5. People input fields
  6. Select box- allow multiple selections
  7. Dropdown box- single choice from short list
  8. Date fields
  9. Integer
  10. Radio buttons
  11. Checkboxes
  12. IP Address fields

Field Types- elaborated

  1. DNS Name field

    Just a recap of all the types of DNS names in NetDB: 

    Name		Node Type	# allowed		Comment
Host		All		1 unless Adv		A record
Alias		All 		many			CNAME record
MX		All		many			MX record
Interface	Adv		1			A record
IP Address	Adv		1			A record
IPC Addr	IPC		1			A record
Dyn Addr	Network		1			A record

    DNS names must obey the following rules:

    • Only include letters, digits or hyphens
    • Case insensitive
    • Must be unique (name.domain.type)
    • Cannot begin or end with hyphen
    • Must contain one letter
    • Max 64 characters for name
    • Max 255 char for fully qualified name
    • Cannot be on reserved name list

    Reserved names

    • must be unique among DNS names and reserved names
    • must follow DNS naming rules
    • Case insensitive

  2. Non-DNS name, no spaces

    • No spaces allowed
    • Any printable character except "<" and ">" (to avoid html problems)

  3. Non-DNS names, spaces allowed

    • Spaces are allowed within name
    • Leading and trailing spaces trimmed
    • Any printable character except "<" and ">" (to avoid html problems) and double quotes (except in DHCP options). Doublequotes are not allowed because they are used as separators in full search.

  4. String field

  5. People Input Fields (User name, Node administrator, Node user, Admin Team members
    • Enter as any valid directory search string
    • Multiple names can be entered, separated by carriage return
    • If a name matches one name, it will be listed with a checked checkbox.
    • If a name matches multiple names, they will be listed with unchecked checkboxes.
    • Wildcard * supported

  6. Select Boxes

    Used when multiple selections are allowed

  7. Dropdown box

    Used when short list and only single selection allowed

  8. Date Fields

    Allowable date formats are:

    • m/d/yyyy, m/dd/yyyy, mm/d/yyyy, mm/dd/yyyy
    • m/d/yy, m/dd/yy, mm/d/yy, mm/dd/yy
    • m-d-yyyy, m-dd-yyyy, mm-d-yyyy, mm-dd-yyyy
    • m-d-yy, m-dd-yy, mm-d-yy, mm-dd-yy

  9. Integers

    Must not be negative number. Zero is ok

  10. Radio Buttons

  11. Checkboxes

  12. IP Address Field
    • IP Address Space Input Format
      • w.x.y.z/n - existing address space with prefix
        e.g. 171.64.20.0/24
      • w.x.y/n - existing address space without trailing zeroes
        e.g. 171.64.20/24
      • w.x.y.z - existing address space without prefix
        e.g. 171.64.20.0
    • IP Address Input Format
      • Must be in form x.y.y.y where x and y are numbers from 0-255.

Table of Objects, Fields and Field Types

Output Requirements

  1. People Display Format

Object Particulars

This section covers oddities for each object type.

  1. Object Names

    Object names must be unique within that object.

    Object Type Name Field Type
    Group Non-DNS name, spaces
    Domain DNS
    User People name- valid kerb principal
    Admin Team Non-DNS name, spaces
    Network DNS Name
    Node DNS Name

  2. Group Object

    Used for security. Associated with all objects and address spaces.

  3. Domain Object

  4. User Object

  5. Admin Team Object

    New object which can be used in place of SUNet ID as a node administrator. In the node administrator field, admin teams are indicated by a semicolon after the name. Members do not have to be netdb users but must be in registry. Unidentified node administrators will be migrate as Admin Teams.

  6. Network Object

  7. Node Object

Different pages

Miscellaneous

THE END