Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?


NIC Data Types


The NIC supports the data types that appear in the following list. You can qualify these data types by adding an identifier to:

  • Distinguish between different instances of a data type in a resolution scenario.

  • Provide information about a data type to clarify the use of that data type in a resolution.


  • Generic data type to represent the information that you want to collect.

  • Value—Alphanumeric characters

  • Guidelines—You can qualify this data type with an identifier to provide information about the type of data that AnyString represents.

  • Example—My(IP), My(Vr)


  • DN of an access.

  • Value—DN

  • Example—accessName=PrimaryAccess, enterpriseName=juniper, ou=Sunnyvale, retailerName=VPNprovider, o=Users, o=umc


  • Domain name.

  • Value—Name of a domain

  • Example—


  • DN of an enterprise.

  • Value—DN

  • Example—enterpriseName=juniper, ou=Sunnyvale, retailerName=VPNprovider, o=Users, o=umc


  • Name of router.

  • Value—Text string

  • Example—router1


  • Name of a router’s interface. Can include a virtual routing forwarding identifier VrfId). If a VrfId is present, the DSA passes it to the SAE in an assignedIp request. The SAE uses the VrfId to support IP addresses that may be the same across different VRFs.

  • Value—<interfaceName>/<ID>@<vrName>@ <routerName>


  • Example—FastEthernet4/1.0/4@boston@router1



  • Identifier of an interface.

  • Value—<intfIndex>@<routerName>

  • Example—4@router1


  • Subscriber’s IP address.

  • Value—IP address

  • Example—


  • IP address pool.

  • Value—Range of IP addresses enclosed in square brackets and parentheses

  • Guidelines—If you enter an IP address that includes a value greater than 255 in one octet of the address, that part of the address is masked to fit the eight bits.

  • Example—([])


  • SAE reference.

  • Value—CORBA interoperable object reference (IOR) for SAE

  • Example—IOR:000000000000002438444C3A736...


  • Name of the virtual router.

  • Value—<vrName>@<routerName>

  • Example—vr1@router1