2005
DOI: 10.17487/rfc4310
|View full text |Cite
|
Sign up to set email alerts
|

Domain Name System (DNS) Security Extensions Mapping for the Extensible Provisioning Protocol (EPP)

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
6
0

Year Published

2006
2006
2014
2014

Publication Types

Select...
5

Relationship

2
3

Authors

Journals

citations
Cited by 5 publications
(6 citation statements)
references
References 13 publications
0
6
0
Order By: Relevance
“…As this document deprecates RFC 4310 [RFC4310], if a server announces support for both secDNS-1.0 [RFC4310] and secDNS-1.1 in the EPP greeting, clients supporting both versions SHOULD prefer secDNS-1.1.…”
Section: Migrating From Rfc 4310mentioning
confidence: 99%
See 3 more Smart Citations
“…As this document deprecates RFC 4310 [RFC4310], if a server announces support for both secDNS-1.0 [RFC4310] and secDNS-1.1 in the EPP greeting, clients supporting both versions SHOULD prefer secDNS-1.1.…”
Section: Migrating From Rfc 4310mentioning
confidence: 99%
“…The authors would like to thank the following people who have provided significant contributions to the development of this document: This document replaces RFC 4310 [RFC4310]. Please see the Acknowledgements section in that RFC for additional acknowledgements.…”
Section: Acknowledgementsmentioning
confidence: 99%
See 2 more Smart Citations
“…RFC 4310 [RFC4310] defined the <secDNS:chg> element as a replacement for the DS data. This is inconsistent with RFC 5731 [RFC5731], where a <domain:chg> element is used to change the values of the domain attributes.…”
Section: Introductionmentioning
confidence: 99%