5.4.3. Info nsset

A nsset info command is used to view details of an nsset.

The nsset info command is an info element in the nsset namespace (http://www.nic.cz/xml/epp/nsset-1.2).

The command must be contained in the <info> command type. Command element structure

The <nsset:info> element must declare the nsset namespace and schema and it must contain the following child element:

<?xml version="1.0" encoding="utf-8" standalone="no"?>
<epp xmlns="urn:ietf:params:xml:ns:epp-1.0"
 xsi:schemaLocation="urn:ietf:params:xml:ns:epp-1.0 epp-1.0.xsd">
      <nsset:info xmlns:nsset="http://www.nic.cz/xml/epp/nsset-1.2"
       xsi:schemaLocation="http://www.nic.cz/xml/epp/nsset-1.2 nsset-1.2.2.xsd">
FRED-client equivalent
> info_nsset NID-MYNSSET MyPassword Response element structure

The response from the FRED EPP server contains the result, response data, and transaction identification.

See also Success or failure of a command.

The response data element (<resData>) contains a single child element <nsset:infData> which declares the nsset namespace and schema and it contains the following child elements:

  • <nsset:id> (1) – the nsset handle as fredcom:objIDType,

  • <nsset:roid> (1) – the nsset repository identifier as eppcom:roidType,

  • <nsset:status> (1..n) – the nsset object state(s):
    • @s (R) – the state name as one of values:
      • ok

      • linked

      • serverDeleteProhibited

      • serverTransferProhibited

      • serverUpdateProhibited

      • deleteCandidate

    • @lang – the language of the state description as a xs:language (default: en),

    • element content: the state description as a xs:normalizedString,

  • <nsset:clID> (1) – the designated registrar’s handle as eppcom:clIDType,

  • <nsset:crID> (0..1) – the handle of the registrar who created this nsset as eppcom:clIDType,

  • <nsset:crDate> (0..1) – the timestamp of creation as xs:dateTime,

  • <nsset:upID> (0..1) – the handle of the registrar who was the last to update this nsset as eppcom:clIDType,

  • <nsset:upDate> (0..1) – the timestamp of the last update as xs:dateTime,

  • <nsset:trDate> (0..1) – the timestamp of the last transfer as xs:dateTime,

  • <nsset:authInfo> (0..1) – the authorization information (AuthInfo) as fredcom:authInfoType,

  • <nsset:ns> (0..10) – a nameserver given by:
  • <nsset:tech> (1..n) – a technical contact handle as fredcom:objIDType,

  • <nsset:reportlevel> (1) – the report level of technical checks as nsset:reportlevelType.

<?xml version="1.0" encoding="UTF-8"?>
<epp xmlns="urn:ietf:params:xml:ns:epp-1.0"
 xsi:schemaLocation="urn:ietf:params:xml:ns:epp-1.0 epp-1.0.xsd">
   <result code="1000">
      <msg>Command completed successfully</msg>
      <nsset:infData xmlns:nsset="http://www.nic.cz/xml/epp/nsset-1.2"
       xsi:schemaLocation="http://www.nic.cz/xml/epp/nsset-1.2 nsset-1.2.2.xsd">
         <nsset:status s="linked">Has relation to other records in the registry</nsset:status>