many fixes

[anewton1998]

some final textual fixes and changes before conferring with the AD.

[rpp-ietf]

Andy, I believe that "will evaluate for possible inclusion of extensibility" and its subsequent obligation as a requirement for the working group. I don’t support softening this language. We have EPP that has benefited from the pre-defined set of features and forms of extensibility and we’re learning the lesson now with the lack of pre-defined forms of extensibility in RDAP. We need to evaluate the extensibility from the start. Thanks,

-- JG ***@***.*** James Gould Fellow Engineer ***@***.******@***.***> 703-948-3271 12061 Bluemont Way Reston, VA 20190 Verisign.com<http://verisigninc.com/> From: Andrew Newton ***@***.***> Reply-To: SIDN/ietf-wg-rpp-charter ***@***.***> Date: Monday, December 2, 2024 at 2:55 PM To: SIDN/ietf-wg-rpp-charter ***@***.***> Cc: Subscribed ***@***.***> Subject: [EXTERNAL] [rpp] Re: [SIDN/ietf-wg-rpp-charter] many fixes (PR #45) Caution: This email originated from outside the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe. @anewton1998 commented on this pull request.

________________________________ In rpp-charter.md<https://secure-web.cisco.com/1y8bpRW_taPGzYZPnLAXkIMKk98EC_5byOZX_XCverkQedTsHSTMH1La_V9swIKbOChukdQGak3ETREgL-abxojMnCK4thZLMDJlhVWDK9U_p5sPv3Yoidj2wBEouzELzT8ZjaE-2bmXiSarqeCjMZSLQixCXMQteRPUkJdr_8W3-3UifSwXdxRSrblgnfM9NNRKrlEoHe7OavmN1eGByQHWT0xcwLkfE_PILMb5AiWE4WBXVeWPbkmmVTRi5GNr0lw6XSs8TDwKLqJB1w6YU0Rpg5U4ga5d_KfVyyogo798/https%3A%2F%2Fgithub.com%2FSIDN%2Fietf-wg-rpp-charter%2Fpull%2F45%23discussion_r1866524109>:

These specifications will specifically target a REST architecture high on the Richardson Maturity Model

using HTTPS and JSON.

…

-The working group will evaluate for possible inclusion of extensibility considerations, allowing

-future use cases beyond the domain name provisioning as well as adding

-or extending operations and data models defined in the core set of protocol specifications. +In addition to use cases and scenarios for domain name registration, this working group will +consider features and extension mechanisms useful for other types of Internet registration areas "Internet registration areas" -> "registration areas" maybe future use cases may also include registration for non-Internet related resources? This is to purposefully limit the scope to the things the IETF concerns itself with. Any charter that is too broad is likely to be rejected. I think "Internet" is what stays in concern of IETF. I am more concerned about "will evaluate for possible inclusion of extensibility" changed to "will consider features and extension mechanisms". The previous one was for me more of obligation to evaluate, now is sounds like obligation to consider them. My preference would be to stay with the previous one or to change from will to may, especially that deliverables read "The working group may consider work for the provisioning of other types of Internet registries". "Will evaluate" does not obligate the working group to produce anything, and neither does the new wording. But both do say the working group will do something. The original wording was clunky IMHO. — Reply to this email directly, view it on GitHub<https://secure-web.cisco.com/1y8bpRW_taPGzYZPnLAXkIMKk98EC_5byOZX_XCverkQedTsHSTMH1La_V9swIKbOChukdQGak3ETREgL-abxojMnCK4thZLMDJlhVWDK9U_p5sPv3Yoidj2wBEouzELzT8ZjaE-2bmXiSarqeCjMZSLQixCXMQteRPUkJdr_8W3-3UifSwXdxRSrblgnfM9NNRKrlEoHe7OavmN1eGByQHWT0xcwLkfE_PILMb5AiWE4WBXVeWPbkmmVTRi5GNr0lw6XSs8TDwKLqJB1w6YU0Rpg5U4ga5d_KfVyyogo798/https%3A%2F%2Fgithub.com%2FSIDN%2Fietf-wg-rpp-charter%2Fpull%2F45%23discussion_r1866524109>, or unsubscribe<https://secure-web.cisco.com/1j3uvH4BkIXYfWXavv84KLDv0diDZAF08fhPEdxdNLhoWWGiGozqq6EmeMd31kifxGMwPRX2_R76VNf3GIonbm3Pn5CBTQZX_lu0IUSf9_oMs1o74sfXVNsffL9zW7gBaxR-Agfsy3n93vvq8ZmoCNY4EYWx5XvpCX_jVeQFS0LEjZWZkFY52r86_zsGiGyiQ4AH4L9PBkDWT7X-SBKufaj4CKX2M61KCWyuGRPXxSmKt0Tp8AMy986YOXz8We6Ijt25dDhxZCj-CbMzZE6SXb3mj2NJXQS3q1P2aI8R-5WU/https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FBM5CYNPSHOSKL2N52KRXRKD2DS3DPAVCNFSM6AAAAABSJ56SO2VHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMZDINZTG43TIMZYGU>. You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>