Technical Integration Guide - Afnic

More documents

Recommendations

Info

TECHNICAL INTEGRATION GUIDE – February 25th, 2013 12• The server only supports « the DS data interface » (),section 4.1 of RFC 5910, without information on the associated key (no element) ; the presence of information on the keywill generate a 2102 error code.• In the same way as for name servers, DNSSEC elements are onlyaccepted during an update[tech] operation. Their presence during acreate operation will generate a 2103 error code.• A domain name can have up to 6 associated DS records: the number ofelements present in the section during an update[tech] operation is therefore limited to have the domain'sfinal status with no more than 6 DS records.• The maxSigLife element is not supported, it presence inside a clientrequest will generate a 2102 error code.• The urgent attribute is not supported, it presence inside a client requestwill generate a 2102 error code.• During a transfer operation, the AFNIC extension frnic-1.2 mustnecessarily include a keepDS flag which is a boolean: if its value is 1,actual DS records for the domain name are maintained after the transfer ifalready present, if its value is 0 in case of a successful transfer anyexisting DS record will be deleted.• Trade and recover operations work the same way as the transferdescribed above.Association Française pour le Nommage Internet en Coopération | www.afnic.fr | contact@afnic.frTwitter : @AFNIC | Facebook : afnic.frTechnical Integration Guide- 12 -November 2009
TECHNICAL INTEGRATION GUIDE – February 25th, 2013 133.3. Implemented commands3.3.1. The The is not a command the client can send to the EPP server, but it isthe welcome banner it will send when a connexion is made. It is also the answersent in response to a command (this command is detailed in the nextsection).Why detail this banner if it is not a command ? Simply because the informationit gives out is important and necessary for the command.Even though the reproduced here is only given as an example andthe detail of its content can be found in the RFC 5730, two pieces of informationare of importance: the versions of the supported protocol ( element)and the accepted languages ( element). Only one choice, among thosevalues, will be accepted during the session establishment with the command. example that can be sent by the AFNIC EPP server:S:S:S: S: EPP PROD Server on nergal.nic.fr (V1.1.0)S: 2010-04-01T12:34:56.0ZS: S: 1.0S: enS: urn:ietf:params:xml:ns:contact-1.0S: urn:ietf:params:xml:ns:domain-1.0S: S: urn:ietf:params:xml:ns:rgp-1.0S: http://www.afnic.fr/xml/epp/frnic-1.2S: urn:ietf:params:xml:ns:secDNS-1.1S: S: S: S: S: S: S: S: S: S: S: S:Association Française pour le Nommage Internet en Coopération | www.afnic.fr | contact@afnic.frTwitter : @AFNIC | Facebook : afnic.frTechnical Integration Guide- 13 -November 2009
Page 1 and 2: TECHNICAL INTEGRATION GUIDE - Febru
Page 11: TECHNICAL INTEGRATION GUIDE - Febru
Page 62 and 63:
TECHNICAL INTEGRATION GUIDE - Febru
Page 64 and 65:
Page 66:
Page 69 and 70:
Page 71 and 72:
Page 73 and 74:
Page 75 and 76:
Page 77 and 78:
Page 79 and 80:
Page 81 and 82:
Page 83 and 84:
Page 85 and 86:
Page 87 and 88:
Page 89 and 90:
Page 91 and 92:
Page 93 and 94:
Page 95 and 96:
Page 97 and 98:
Page 99 and 100:
Page 101 and 102:
Page 103 and 104:
Page 105 and 106:
Page 107 and 108:
Page 109 and 110:
Page 111 and 112:
Page 113 and 114:
Page 115 and 116:
Page 117 and 118:
Page 119 and 120:
Page 121 and 122:
Page 123 and 124:
show all

Technical Integration Guide - Afnic

Create successful ePaper yourself

Delete template?

Save as template?