draft-ietf-regext-bundling-registration-07.txt   draft-ietf-regext-bundling-registration-08.txt 
Internet Engineering Task Force N. Kong Internet Engineering Task Force N. Kong
Internet-Draft Consultant Internet-Draft Consultant
Intended status: Informational J. Yao, Ed. Intended status: Informational J. Yao, Ed.
Expires: May 21, 2019 L. Zhou Expires: May 22, 2019 L. Zhou
CNNIC CNNIC
W. Tan W. Tan
Cloud Registry Cloud Registry
J. Xie J. Xie
November 17, 2018 November 18, 2018
Extensible Provisioning Protocol (EPP) Domain Name Mapping Extension for Extensible Provisioning Protocol (EPP) Domain Name Mapping Extension for
Strict Bundling Registration Strict Bundling Registration
draft-ietf-regext-bundling-registration-07 draft-ietf-regext-bundling-registration-08
Abstract Abstract
This document describes an extension of Extensible Provisioning This document describes an extension of Extensible Provisioning
Protocol (EPP) domain name mapping for the provisioning and Protocol (EPP) domain name mapping for the provisioning and
management of strict bundling registration of domain names. management of strict bundling registration of domain names.
Specified in XML, this mapping extends the EPP domain name mapping to Specified in XML, this mapping extends the EPP domain name mapping to
provide additional features required for the provisioning of bundled provide additional features required for the provisioning of bundled
domain names. domain names.
skipping to change at page 1, line 41 skipping to change at page 1, line 41
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 May 21, 2019. This Internet-Draft will expire on May 22, 2019.
Copyright Notice Copyright Notice
Copyright (c) 2018 IETF Trust and the persons identified as the Copyright (c) 2018 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/license-info) in effect on the date of (https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 13, line 10 skipping to change at page 13, line 10
elements are defined for the <delete> response. elements are defined for the <delete> response.
When a <delete> command has been processed successfully, the EPP When a <delete> command has been processed successfully, the EPP
<delData> element MUST contain child elements as described in the EPP <delData> element MUST contain child elements as described in the EPP
domain mapping [RFC5731]. In addition, the EPP <extension> element domain mapping [RFC5731]. In addition, the EPP <extension> element
SHOULD contain a child <b-dn:delData> element that identifies the SHOULD contain a child <b-dn:delData> element that identifies the
extension namespace if the domain object has data associated with extension namespace if the domain object has data associated with
this extension and based on its service policy. The <b-dn:delData> this extension and based on its service policy. The <b-dn:delData>
element SHOULD contain the <b-dn:bundle> element. element SHOULD contain the <b-dn:bundle> element.
Example <delete> response: Example <delete> response:
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="1000"> S: <result code="1000">
S: <msg>Command completed successfully</msg> S: <msg>Command completed successfully</msg>
S: </result> S: </result>
S: <extension> S: <extension>
S: <b-dn:delData S: <b-dn:delData
S: xmlns:b-dn="urn:ietf:params:xml:ns:epp:b-dn-1.0"> S: xmlns:b-dn="urn:ietf:params:xml:ns:epp:b-dn-1.0">
S: <b-dn:bundle> S: <b-dn:bundle>
S: <b-dn:rdn uLabel="U+5B9E""U+4F8B".example>xn--fsq270a.example</b-dn:rdn> S: <b-dn:rdn uLabel="U+5B9E""U+4F8B".example>
S: <b-dn:bdn uLabel="U+5BE6""U+4F8B".example>xn--fsqz41a.example</b-dn:bdn> xn--fsq270a.example</b-dn:rdn>
S: </b-dn:bundle> S: <b-dn:bdn uLabel="U+5BE6""U+4F8B".example>
S: </b-dn:delData> xn--fsqz41a.example</b-dn:bdn>
S: </extension> S: </b-dn:bundle>
S: <trID> S: </b-dn:delData>
S: <clTRID>ABC-12345</clTRID> S: </extension>
S: <svTRID>54321-XYZ</svTRID> S: <trID>
S: </trID> S: <clTRID>ABC-12345</clTRID>
S: </response> S: <svTRID>54321-XYZ</svTRID>
S:</epp> S: </trID>
S: </response>
S:</epp>
An EPP error response MUST be returned if a <delete> command cannot An EPP error response MUST be returned if a <delete> command cannot
be processed for any reason. be processed for any reason.
7.2.3. EPP <renew> Command 7.2.3. EPP <renew> Command
This extension does not add any element to the EPP <renew> command This extension does not add any element to the EPP <renew> command
described in the EPP domain name mapping [RFC5731]. However, when described in the EPP domain name mapping [RFC5731]. However, when
either RDN or BDN is sent for renew, response SHOULD contain both RDN either RDN or BDN is sent for renew, response SHOULD contain both RDN
and BDN information. When the command has been processed and BDN information. When the command has been processed
skipping to change at page 24, line 12 skipping to change at page 24, line 12
DOI 10.17487/RFC4290, December 2005, DOI 10.17487/RFC4290, December 2005,
<https://www.rfc-editor.org/info/rfc4290>. <https://www.rfc-editor.org/info/rfc4290>.
Authors' Addresses Authors' Addresses
Ning Kong Ning Kong
Consultant Consultant
Email: ietfing@gmail.com Email: ietfing@gmail.com
Jiankang Yao Jiankang Yao (editor)
CNNIC CNNIC
4 South 4th Street,Zhongguancun,Haidian District 4 South 4th Street,Zhongguancun,Haidian District
Beijing, Beijing 100190 Beijing, Beijing 100190
China China
Phone: +86 10 5881 3007 Phone: +86 10 5881 3007
Email: yaojk@cnnic.cn Email: yaojk@cnnic.cn
Linlin Zhou Linlin Zhou
CNNIC CNNIC
 End of changes. 7 change blocks. 
28 lines changed or deleted 30 lines changed or added

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