draft-ietf-regext-unhandled-namespaces-02.txt   draft-ietf-regext-unhandled-namespaces-03.txt 
Network Working Group J. Gould Network Working Group J.G. Gould
Internet-Draft VeriSign, Inc. Internet-Draft VeriSign, Inc.
Intended status: Best Current Practice M. Casanova Intended status: Best Current Practice M.C. Casanova
Expires: February 1, 2021 SWITCH Expires: 12 March 2021 SWITCH
July 31, 2020 8 September 2020
Extensible Provisioning Protocol (EPP) Unhandled Namespaces Extensible Provisioning Protocol (EPP) Unhandled Namespaces
draft-ietf-regext-unhandled-namespaces-02 draft-ietf-regext-unhandled-namespaces-03
Abstract Abstract
The Extensible Provisioning Protocol (EPP), as defined in RFC 5730, The Extensible Provisioning Protocol (EPP), as defined in RFC 5730,
includes a method for the client and server to determine the objects includes a method for the client and server to determine the objects
to be managed during a session and the object extensions to be used to be managed during a session and the object extensions to be used
during a session. The services are identified using namespace URIs. during a session. The services are identified using namespace URIs.
How should the server handle service data that needs to be returned How should the server handle service data that needs to be returned
in the response when the client does not support the required service in the response when the client does not support the required service
namespace URI, which is referred to as an unhandled namespace? An namespace URI, which is referred to as an unhandled namespace? An
skipping to change at page 1, line 44 skipping to change at page 1, line 44
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on February 1, 2021. This Internet-Draft will expire on 12 March 2021.
Copyright Notice Copyright Notice
Copyright (c) 2020 IETF Trust and the persons identified as the Copyright (c) 2020 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents (https://trustee.ietf.org/
(https://trustee.ietf.org/license-info) in effect on the date of license-info) in effect on the date of publication of this document.
publication of this document. Please review these documents Please review these documents carefully, as they describe your rights
carefully, as they describe your rights and restrictions with respect and restrictions with respect to this document. Code Components
to this document. Code Components extracted from this document must extracted from this document must include Simplified BSD License text
include Simplified BSD License text as described in Section 4.e of as described in Section 4.e of the Trust Legal Provisions and are
the Trust Legal Provisions and are provided without warranty as provided without warranty as described in the Simplified BSD License.
described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Conventions Used in This Document . . . . . . . . . . . . 3 1.1. Conventions Used in This Document . . . . . . . . . . . . 3
2. Unhandled Namespaces . . . . . . . . . . . . . . . . . . . . 4 2. Unhandled Namespaces . . . . . . . . . . . . . . . . . . . . 4
3. Use of EPP <extValue> for Unhandled Namespace Data . . . . . 4 3. Use of EPP <extValue> for Unhandled Namespace Data . . . . . 4
3.1. Unhandled Object-Level Extension . . . . . . . . . . . . 5 3.1. Unhandled Object-Level Extension . . . . . . . . . . . . 5
3.2. Unhandled Command-Response Extension . . . . . . . . . . 7 3.2. Unhandled Command-Response Extension . . . . . . . . . . 7
4. Signaling Client and Server Support . . . . . . . . . . . . . 10 4. Signaling Client and Server Support . . . . . . . . . . . . . 10
5. Usage with General EPP Responses . . . . . . . . . . . . . . 10 5. Usage with General EPP Responses . . . . . . . . . . . . . . 10
6. Usage with Poll Message EPP Responses . . . . . . . . . . . . 12 6. Usage with Poll Message EPP Responses . . . . . . . . . . . . 12
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 15 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 15
7.1. XML Namespace . . . . . . . . . . . . . . . . . . . . . . 15 7.1. XML Namespace . . . . . . . . . . . . . . . . . . . . . . 15
7.2. EPP Extension Registry . . . . . . . . . . . . . . . . . 16 7.2. EPP Extension Registry . . . . . . . . . . . . . . . . . 16
8. Implementation Status . . . . . . . . . . . . . . . . . . . . 16 8. Implementation Status . . . . . . . . . . . . . . . . . . . . 16
8.1. Verisign EPP SDK . . . . . . . . . . . . . . . . . . . . 17 8.1. Verisign EPP SDK . . . . . . . . . . . . . . . . . . . . 17
8.2. SWITCH Automated DNSSEC Provisioning Process . . . . . . 17 8.2. SWITCH Automated DNSSEC Provisioning Process . . . . . . 17
9. Security Considerations . . . . . . . . . . . . . . . . . . . 18 9. Security Considerations . . . . . . . . . . . . . . . . . . . 17
10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 18 10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 18
11. Normative References . . . . . . . . . . . . . . . . . . . . 18 11. Normative References . . . . . . . . . . . . . . . . . . . . 18
Appendix A. Change History . . . . . . . . . . . . . . . . . . . 19 Appendix A. Change History . . . . . . . . . . . . . . . . . . . 19
A.1. Change from 00 to 01 . . . . . . . . . . . . . . . . . . 19 A.1. Change from 00 to 01 . . . . . . . . . . . . . . . . . . 19
A.2. Change from 01 to 02 . . . . . . . . . . . . . . . . . . 19 A.2. Change from 01 to 02 . . . . . . . . . . . . . . . . . . 19
A.3. Change from 02 to REGEXT 00 . . . . . . . . . . . . . . . 19 A.3. Change from 02 to REGEXT 00 . . . . . . . . . . . . . . . 19
A.4. Change from REGEXT 00 to REGEXT 01 . . . . . . . . . . . 20 A.4. Change from REGEXT 00 to REGEXT 01 . . . . . . . . . . . 19
A.5. Change from REGEXT 01 to REGEXT 02 . . . . . . . . . . . 20 A.5. Change from REGEXT 01 to REGEXT 02 . . . . . . . . . . . 19
A.6. Change from REGEXT 02 to REGEXT 03 . . . . . . . . . . . 20
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 20 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 20
1. Introduction 1. Introduction
The Extensible Provisioning Protocol (EPP), as defined in [RFC5730], The Extensible Provisioning Protocol (EPP), as defined in [RFC5730],
includes a method for the client and server to determine the objects includes a method for the client and server to determine the objects
to be managed during a session and the object extensions to be used to be managed during a session and the object extensions to be used
during a session. The services are identified using namespace URIs. during a session. The services are identified using namespace URIs.
How should the server handle service data that needs to be returned How should the server handle service data that needs to be returned
in the response when the client does not support the required service in the response when the client does not support the required service
skipping to change at page 13, line 5 skipping to change at page 12, line 46
poll messages that have been inserted by the server. The <poll> poll messages that have been inserted by the server. The <poll>
message response is an EPP response that includes the <msgQ> element message response is an EPP response that includes the <msgQ> element
that provides poll queue meta-data about the message. The unhandled that provides poll queue meta-data about the message. The unhandled
namespace approach, defined in Section 3, is used for an unhandled namespace approach, defined in Section 3, is used for an unhandled
object-level extension and for each of the unhandled command-response object-level extension and for each of the unhandled command-response
extensions attached to the <poll> message response. The resulting extensions attached to the <poll> message response. The resulting
EPP <poll> message response MAY have either or both the object-level EPP <poll> message response MAY have either or both the object-level
extension or command-response extensions moved to <extValue> extension or command-response extensions moved to <extValue>
elements, as defined in Section 3. elements, as defined in Section 3.
The Change Poll Message, as defined in [I-D.ietf-regext-change-poll], The Change Poll Message, as defined in [RFC8590], which is an
which is an extension of any EPP object, is an example of applying extension of any EPP object, is an example of applying the unhandled
the unhandled namespace approach for EPP <poll> message responses. namespace approach for EPP <poll> message responses. The object that
The object that will be used in the examples is a [RFC5731] domain will be used in the examples is a [RFC5731] domain name object.
name object.
[RFC5731] domain name <info> <poll> message response with the [RFC5731] domain name <info> <poll> message response with the
unhandled [I-D.ietf-regext-change-poll] <changePoll:changeData> unhandled [RFC8590] <changePoll:changeData> element included under an
element included under an <extValue> element: <extValue> element:
S:<?xml version="1.0" encoding="UTF-8" standalone="no"?> S:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
S:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0"> S:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
S: <response> S: <response>
S: <result code="1301"> S: <result code="1301">
S: <msg>Command completed successfully; ack to dequeue</msg> S: <msg>Command completed successfully; ack to dequeue</msg>
S: <extValue> S: <extValue>
S: <value> S: <value>
S: <changePoll:changeData S: <changePoll:changeData
S: xmlns:changePoll="urn:ietf:params:xml:ns:changePoll-1.0" S: xmlns:changePoll="urn:ietf:params:xml:ns:changePoll-1.0"
skipping to change at page 14, line 25 skipping to change at page 14, line 19
S: </domain:infData> S: </domain:infData>
S: </resData> S: </resData>
S: <trID> S: <trID>
S: <clTRID>ABC-12345</clTRID> S: <clTRID>ABC-12345</clTRID>
S: <svTRID>54322-XYZ</svTRID> S: <svTRID>54322-XYZ</svTRID>
S: </trID> S: </trID>
S: </response> S: </response>
S:</epp> S:</epp>
Unhandled [RFC5731] domain name <info> <poll> message response and Unhandled [RFC5731] domain name <info> <poll> message response and
the unhandled [I-D.ietf-regext-change-poll] <changePoll:changeData> the unhandled [RFC8590] <changePoll:changeData> element included
element included under an <extValue> element: under an <extValue> element:
S:<?xml version="1.0" encoding="UTF-8" standalone="no"?> S:<?xml version="1.0" encoding="UTF-8" standalone="no"?>
S:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0"> S:<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
S: <response> S: <response>
S: <result code="1301"> S: <result code="1301">
S: <msg>Command completed successfully; ack to dequeue</msg> S: <msg>Command completed successfully; ack to dequeue</msg>
S: <extValue> S: <extValue>
S: <value> S: <value>
S: <domain:infData S: <domain:infData
S: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"> S: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
skipping to change at page 18, line 15 skipping to change at page 18, line 8
9. Security Considerations 9. Security Considerations
The document do not provide any security services beyond those The document do not provide any security services beyond those
described by EPP [RFC5730] and protocol layers used by EPP. The described by EPP [RFC5730] and protocol layers used by EPP. The
security considerations described in these other specifications apply security considerations described in these other specifications apply
to this specification as well. to this specification as well.
10. Acknowledgements 10. Acknowledgements
The authors wish to thank the following persons for their feedback The authors wish to thank the following persons for their feedback
and suggestions: and suggestions: Scott Hollenbeck, Patrick Mevzek, and Marcel Parodi.
o Scott Hollenbeck
o Patrick Mevzek
o Marcel Parodi
11. Normative References 11. Normative References
[I-D.ietf-regext-change-poll]
Gould, J. and K. Feher, "Change Poll Extension for the
Extensible Provisioning Protocol (EPP)", draft-ietf-
regext-change-poll-12 (work in progress), January 2019.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997, DOI 10.17487/RFC2119, March 1997,
<https://www.rfc-editor.org/info/rfc2119>. <https://www.rfc-editor.org/info/rfc2119>.
[RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,
DOI 10.17487/RFC3688, January 2004, DOI 10.17487/RFC3688, January 2004,
<https://www.rfc-editor.org/info/rfc3688>. <https://www.rfc-editor.org/info/rfc3688>.
[RFC3735] Hollenbeck, S., "Guidelines for Extending the Extensible [RFC3735] Hollenbeck, S., "Guidelines for Extending the Extensible
skipping to change at page 19, line 29 skipping to change at page 19, line 14
[RFC7451] Hollenbeck, S., "Extension Registry for the Extensible [RFC7451] Hollenbeck, S., "Extension Registry for the Extensible
Provisioning Protocol", RFC 7451, DOI 10.17487/RFC7451, Provisioning Protocol", RFC 7451, DOI 10.17487/RFC7451,
February 2015, <https://www.rfc-editor.org/info/rfc7451>. February 2015, <https://www.rfc-editor.org/info/rfc7451>.
[RFC7942] Sheffer, Y. and A. Farrel, "Improving Awareness of Running [RFC7942] Sheffer, Y. and A. Farrel, "Improving Awareness of Running
Code: The Implementation Status Section", BCP 205, Code: The Implementation Status Section", BCP 205,
RFC 7942, DOI 10.17487/RFC7942, July 2016, RFC 7942, DOI 10.17487/RFC7942, July 2016,
<https://www.rfc-editor.org/info/rfc7942>. <https://www.rfc-editor.org/info/rfc7942>.
[RFC8590] Gould, J. and K. Feher, "Change Poll Extension for the
Extensible Provisioning Protocol (EPP)", RFC 8590,
DOI 10.17487/RFC8590, May 2019,
<https://www.rfc-editor.org/info/rfc8590>.
Appendix A. Change History Appendix A. Change History
A.1. Change from 00 to 01 A.1. Change from 00 to 01
1. Removed xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 1. Removed xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
reference from examples. reference from examples.
2. removed <extension></extension> block from example. 2. removed <extension></extension> block from example.
3. added SWITCH Automated DNSSEC Provisioning Process at 3. added SWITCH Automated DNSSEC Provisioning Process at
Implementation Status Implementation Status
skipping to change at page 20, line 18 skipping to change at page 20, line 4
describe the mechanism to signal support for the BCP by the describe the mechanism to signal support for the BCP by the
client and the server. client and the server.
2. Added the IANA Considerations section with the registration of 2. Added the IANA Considerations section with the registration of
the unhandled namespaces XML namespace and the registration of the unhandled namespaces XML namespace and the registration of
the EPP Best Current Practice (BCP) in the EPP Extension the EPP Best Current Practice (BCP) in the EPP Extension
Registry. Registry.
A.5. Change from REGEXT 01 to REGEXT 02 A.5. Change from REGEXT 01 to REGEXT 02
1. Filled in the acknowledgements section. 1. Filled in the acknowledgements section.
2. Changed the reference from RFC 5730 to RFC 5731 for the transfer 2. Changed the reference from RFC 5730 to RFC 5731 for the transfer
example in section 3.1 "Unhandled Object-Level" Extension. example in section 3.1 "Unhandled Object-Level" Extension.
3. Updated the XML namespace to 3. Updated the XML namespace to
urn:ietf:params:xml:ns:epp:unhandled-namespaces-1.0, which urn:ietf:params:xml:ns:epp:unhandled-namespaces-1.0, which
removed bcp from the namespace and bumped the version from 0.1 removed bcp from the namespace and bumped the version from 0.1
and 1.0. Inclusion of bcp in the XML namespace was discussed at and 1.0. Inclusion of bcp in the XML namespace was discussed at
the REGEXT interim meeting. the REGEXT interim meeting.
A.6. Change from REGEXT 02 to REGEXT 03
1. Converted from xml2rfc v2 to v3.
2. Updated Acknowledgements to match the approach taken by the RFC
Editor with draft-ietf-regext-login-security.
3. Changed reference of ietf-regext-change-poll to RFC 8590.
Authors' Addresses Authors' Addresses
James Gould James Gould
VeriSign, Inc. VeriSign, Inc.
12061 Bluemont Way 12061 Bluemont Way
Reston, VA 20190 Reston, VA 20190
US United States of America
Email: jgould@verisign.com Email: jgould@verisign.com
URI: http://www.verisigninc.com URI: http://www.verisigninc.com
Martin Casanova Martin Casanova
SWITCH SWITCH
P.O. Box P.O. Box
Zurich, ZH 8021 CH-8021 Zurich
CH Switzerland
Email: martin.casanova@switch.ch Email: martin.casanova@switch.ch
URI: http://www.switch.ch URI: http://www.switch.ch
 End of changes. 17 change blocks. 
40 lines changed or deleted 43 lines changed or added

This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/