[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"detail-sidebar-cat-1-en-105":3,"doc-seo-237654-105":53,"doc-detail-237654-en":126},{"code":4,"msg":5,"data":6},0,"success",[7,14,19,24,29,34,39,44,49],{"id":8,"doc_module":9,"doc_module_name":10,"category_name":11,"show_sort_weight":12,"slug":13},11,1,"Template","Presentations",90,"presentations",{"id":15,"doc_module":9,"doc_module_name":10,"category_name":16,"show_sort_weight":17,"slug":18},12,"Resumes",80,"resumes",{"id":20,"doc_module":9,"doc_module_name":10,"category_name":21,"show_sort_weight":22,"slug":23},14,"Invoices",70,"invoices",{"id":25,"doc_module":9,"doc_module_name":10,"category_name":26,"show_sort_weight":27,"slug":28},15,"Posters",60,"posters",{"id":30,"doc_module":9,"doc_module_name":10,"category_name":31,"show_sort_weight":32,"slug":33},16,"Social Media",50,"social-media",{"id":35,"doc_module":9,"doc_module_name":10,"category_name":36,"show_sort_weight":37,"slug":38},17,"Forms",40,"forms",{"id":40,"doc_module":9,"doc_module_name":10,"category_name":41,"show_sort_weight":42,"slug":43},18,"Letters",30,"letters",{"id":45,"doc_module":9,"doc_module_name":10,"category_name":46,"show_sort_weight":47,"slug":48},21,"Paper Templates",5,"papers-templates",{"id":50,"doc_module":9,"doc_module_name":10,"category_name":51,"show_sort_weight":4,"slug":52},158,"General","general-158",{"code":4,"msg":54,"data":55},"ok",{"site_id":56,"language":57,"slug":58,"title":59,"keywords":60,"description":61,"schema_data":62,"social_meta":119,"head_meta":121,"extra_data":123,"updated_unix":125},105,"en","rpp-core-updates-version-00-mapping-to-epp-endpoints-and-update-operations","RPP - Core - Updates - Version-00 - Mapping to EPP, Endpoints, and Update Operations","","RPP - Core Updates - Version-00 consolidates key protocol changes for endpoint mapping, organizational modeling, and update semantics. It adopts the workgroup document, adds Organization and User endpoints based on RFC8544, and proposes multitenancy via organization typing. The slide deck defines detailed rules mapping data objects to URL endpoints and HTTP methods, including full vs partial updates (PUT vs PATCH) and extended process operations. It also clarifies the relationship to EPP, stating RPP is independent and reuses EPP-like elements without EPP prefixing, with mapping specified in a separate RFC.",{"@graph":63,"@context":118},[64,80,101],{"@type":65,"itemListElement":66},"BreadcrumbList",[67,71,74,77],{"item":68,"name":69,"@type":70,"position":9},"https://docshare.wps.com","Home","ListItem",{"item":72,"name":10,"@type":70,"position":73},"https://docshare.wps.com/template/",2,{"item":75,"name":11,"@type":70,"position":76},"https://docshare.wps.com/template/presentations/",3,{"item":78,"name":59,"@type":70,"position":79},"https://docshare.wps.com/template/rpp-core-updates-version-00-mapping-to-epp-endpoints-and-update-operations/237654/",4,{"url":78,"name":59,"@type":81,"image":82,"author":87,"headline":59,"publisher":90,"fileFormat":93,"inLanguage":57,"description":61,"dateModified":94,"datePublished":95,"encodingFormat":93,"isAccessibleForFree":96,"interactionStatistic":97},"DigitalDocument",{"url":83,"@type":84,"width":85,"height":86},"https://docshare.wps.com/thumbnails/rpp-core-updates-version-00-mapping-to-epp-endpoints-and-update-operations/237654.png","ImageObject",442,249,{"name":88,"@type":89},"\tJames","Person",{"url":68,"name":91,"@type":92},"DocShare","Organization","application/pdf","2026-10-22","2026-09-11",true,{"@type":98,"interactionType":99,"userInteractionCount":15},"InteractionCounter",{"@type":100},"ViewAction",{"@type":102,"mainEntity":103},"FAQPage",[104,110,114],{"name":105,"@type":106,"acceptedAnswer":107},"What is new in RPP Core Updates Version-00 regarding endpoints?","Question",{"text":108,"@type":109},"It adds Organization and User endpoints and extends the model to allow multiple user accounts per organization, supporting mapping to authorization mechanisms such as OAuth 2.0.","Answer",{"name":111,"@type":106,"acceptedAnswer":112},"How does the document define rules for mapping data objects to URL endpoints and HTTP methods?",{"text":113,"@type":109},"It introduces a set of endpoint mapping rules that map data object identifiers to collection path segments, map uniform interface operations to HTTP methods, define direct access to sub-resources, and specify extended process operations as POST.",{"name":115,"@type":106,"acceptedAnswer":116},"What clarification does the slide deck provide about the relationship between RPP and EPP?",{"text":117,"@type":109},"It adds a “Mapping to EPP” section stating RPP does not depend on EPP and does not require an EPP server; similar counterparts must not use an “EPP” prefix or postfix, and mapping is described in a separate RFC.","https://schema.org",{"og:url":78,"og:type":120,"og:title":59,"og:site_name":91,"og:description":61},"article",{"robots":122,"canonical":78},"index,follow",{"doc_id":124,"site_id":56},237654,1791125793,{"code":4,"msg":5,"data":127},{"doc_id":124,"user_id":128,"nickname":88,"user_avatar":129,"doc_module":9,"category_id":8,"category_name":11,"doc_title":59,"doc_description":61,"doc_content":130,"file_id":131,"file_url":132,"file_type":133,"file_size":134,"view_count":15,"is_deleted":4,"is_public":9,"is_downloadable":9,"audit_status":9,"page_count":135,"language":136,"language_code":57,"site_id":56,"html_lang":57,"table_of_contents":137,"faqs":138,"seo_title":139,"seo_description":61,"update_tm":140,"read_time":76},2336474466412,"https://ap-avatar.wpscdn.com/davatar_155a257f0dc6eb9ab79c44ca47cae57d","RPP – Core  \nMaarten Wullink-SIDN Labs Pawel Kowalik-DENIC IETF 126, Vienna, 2026  \nUpdates –Version-00  \n● Adopted as WG document  \n● Added Organisation and User endpoints  \n● Created rules for mapping a data object to an URL endpoint ● Described full and partial operations  \nRelationship to EPP  \nAdded “Mapping to EPP” section to explicitly clarify:  \n● RPP is not dependent on EPP and does not require an EPP server  \n● Any RPP elements with similar EPP counterpart must not use a “EPP” prefix or postfix  \n● Mapping of RPP to EPP is described in separate RFC  \nOrganizations and Users  \nAdded Organization model based on RFC8544  \n● Extended with User object to allow multiple user accounts per org  \n● User can be mapped to authorization mechanism used by server (e.g. OAuth 2.0)  \nWe propose to model the registry to also use the organization type, as a natural way to enable multitenancy.  \nEndpoint Mapping Rules  \nCreated set of rules used to map data objects to URL endpoints and [HTTP methods](HTTP methods)  \n[1](1) . Data Object identifier-> Collection path segment. ( e.g. /domainNames)  \n2. Uniform interface operation-> [HTTP method](HTTP method)  \n3. Direct access to sub-resources-> Collection path segment ( e.g. processes->/domainNames/test.example/processes/transferProcesses)  \n4. Process uniform interface operation-> [HTTP method](HTTP method)  \n[5](5) . Extended process operation-> always POST method  \n6. Process listing-> GET all processes collection or per process type collection (e.g. /collection/\u003Cid>/processes and /collection/\u003Cid>/processes/transferProcesses)  \n 5  \nUpdates: Full and Partial  \nFor updating the “update” operation is mapped to:  \nPUT: Complete replacement of a resource, the message body must contain a valid new representation  \nPATCH: Partial replacement of a resource, message body, must have valid  \nupdates for 1 or more specific properties  \nNew Process Link Relation  \nA uniform (CRUD) operation, may create a new process.  \nFor example, as a result of starting a Transfer:  \n● A Transfer Process is created, having it’s own identifier.  \n● The response of the Create Transfer request includes additional Link headers with the rpp-process relation type (IANA)  \nExample  \nLink: \u003C[https://rpp.example/rpp/v1/domainNames/foo.example/processes/createProcesses/latest](https://rpp.example/rpp/v1/domainNames/foo.example/processes/createProcesses/latest) >; rel=\"rpp-process\" process=\"createProcess\"; processId=\"XYZ-12345\";  \nNext steps  \n● Process all feedback received  \n● Map data object elements to [HTTP request parameters](HTTP request parameters)  \n● Ensure the core is compliant with the requirements of the [HTTP Directorate](HTTP Directorate)[ ](HTTP Directorate)● Remove the option for using a header for signaling profile (use media type)  \nExample of using Media Type for signaling RPP-profile  \nAccept: application/rpp+json; profile=\"urn:ietf:params:rpp:profile:example-profile\"; version=\"1.0\"  \nThankYou  \n[www.sidnlabs.nl | stats.sidnlabs.nl](www.sidnlabs.nl | stats.sidnlabs.nl)","cbCaibVz8KnciQXA","https://ap.wps.com/l/cbCaibVz8KnciQXA","pdf",226684,9,"English","# Updates\n## Adopted as WG document\n## Added organization and user endpoints\n## Endpoint mapping rules\n## Updates: Full and partial\n## New process link relation\n## Relationship to EPP\n## Next steps","[{\"question\":\"What is new in RPP Core Updates Version-00 regarding endpoints?\",\"answer\":\"It adds Organization and User endpoints and extends the model to allow multiple user accounts per organization, supporting mapping to authorization mechanisms such as OAuth 2.0.\"},{\"question\":\"How does the document define rules for mapping data objects to URL endpoints and HTTP methods?\",\"answer\":\"It introduces a set of endpoint mapping rules that map data object identifiers to collection path segments, map uniform interface operations to HTTP methods, define direct access to sub-resources, and specify extended process operations as POST.\"},{\"question\":\"What clarification does the slide deck provide about the relationship between RPP and EPP?\",\"answer\":\"It adds a “Mapping to EPP” section stating RPP does not depend on EPP and does not require an EPP server; similar counterparts must not use an “EPP” prefix or postfix, and mapping is described in a separate RFC.\"}]","RPP - Core - Updates - Version-00 - Mapping to EPP, Endpoints, and Update Operations | PDF",1789113993]