Clarify REGEXT out-of-scope

[jasdips]

The REGEXT working group is chartered to maintain and standardize extensions to EPP, therefore extensions or changes for EPP, including those added by RPP, are explicitly out of scope for the RPP working group.

Found "including those added by RPP" phrase confusing. What does that mean?

[pawel-kow]

Hi @jasdips,
the intention was to mention, that RPP group would not work on EPP extension for the counterparts of RPP functionality not existing in EPP.

Reading it again I also can share your confusion. Would this text work better for you:
The REGEXT working group is chartered to maintain and standardize extensions to EPP. Consequently, any extensions or changes to EPP, including those related to RPP functionality that do not exist in EPP, are explicitly out of scope for the RPP working group.

[jasdips]

Perfect.

[rpp-ietf]

Pawel, I don’t get the goal here. It still has not been determined what is included and not included in RPP based on what has been defined for EPP, including the EPP extensions. The goal of “RPP Overlap with EPP” should not include explicit out of scope items for the RPP working group in the charter as it related to EPP interoperability. Please remove this sentence from the charter.

…

-- JG ***@***.*** James Gould Fellow Engineer ***@***.******@***.***> 703-948-3271 12061 Bluemont Way Reston, VA 20190 Verisign.com<http://verisigninc.com/> From: Pawel Kowalik ***@***.***> Reply-To: SIDN/ietf-wg-rpp-charter ***@***.***> Date: Friday, November 15, 2024 at 12:31 PM To: SIDN/ietf-wg-rpp-charter ***@***.***> Cc: Subscribed ***@***.***> Subject: [EXTERNAL] [rpp] Re: [SIDN/ietf-wg-rpp-charter] Clarify REGEXT out-of-scope (Issue #36) 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. Hi @jasdips<https://secure-web.cisco.com/1mXDjtHI4poiW9Ezwfw2j5yL-YNvz0qOm5lDDai-pzD0GvKNgX1-vghfyOcIGANDLLOe_0KRBn8-TaHG6VCY5auxaDmDEdsA7z9bNbxpyHHw6eAKbj8ZKBmIglxlx-Ws-f-eZN_gKRbibhkvjT8OCQaoKPTZXbezWMgYLARkR3k-Mc5zn3U3BkWO36H7TfLk9XBaNFGDYWxML9uqWK_ow4nQ9RbiA8m4VN1_DChWcF7BjzFubthLgo6kRl-oF53fR5pwbJ5ZM3TCYr5ianDuxk9Y5zQxRH55HddcJUMRaX5o/https%3A%2F%2Fgithub.com%2Fjasdips>, the intention was to mention, that RPP group would not work on EPP extension for the counterparts of RPP functionality not existing in EPP. Reading it again I also can share your confusion. Would this text work better for you: The REGEXT working group is chartered to maintain and standardize extensions to EPP. Consequently, any extensions or changes to EPP, including those related to RPP functionality that do not exist in EPP, are explicitly out of scope for the RPP working group. — Reply to this email directly, view it on GitHub<https://secure-web.cisco.com/1jm507_RwECFJvknsQ2A6yH6a1uqrN4sZFdndavzJoXWlScEJmnDXbxu43MZDnqjkySMPkviuUoRMeUv91sopJzz8uzJOa2SkeSZSml8OZdom8KZ6rfc3PZMr5ESGnpJErp0HFWFnoy21c53KwwtzhwCA6GP8BsEbJhZkdC0bht9Zl0MtficTP6WJGM1bKeDIAM9Sc_nO_mH4S6tI2sfh9hsMbD60kaK__H9xEpHx7cw2yNV9_swJPR9xIMxYsu47Duta7sxIxWdQjVT_3uIzENZ2G7ySrzhujVrk5oNIOGg/https%3A%2F%2Fgithub.com%2FSIDN%2Fietf-wg-rpp-charter%2Fissues%2F36%23issuecomment-2479492263>, or unsubscribe<https://secure-web.cisco.com/1_4CuECJipedKOGmvAFhA3Ay6Ql1uv8pt2OSaR5qcGNFhWEcGz-TdTdA8HU7-Vk8rgtZoHEyOGLjcRB6VPOPV51ykBNNuG0f5PFxJDLcWh_xfEKysPbRx9iHyabsZkGQac6-_3EjbaZiF1cMWcO_jZTY6wNb3yBxlj-04eBA5ilbJ94zaoncv4ITw4NR_fCiiiXc2jM2ZNehE_JAO_aexTvX7CP9MRPbnthTTvlhUJ6U7xbfHWnwA6JYIij_yqP-cvB-4NueqEM2WlwA0a3xBX1Yx9WjGmXJ_zuqDj87z7fU/https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FBM5CYNLA5RJOCZFNTTVRNTT2AYUURAVCNFSM6AAAAABR3RXPD6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINZZGQ4TEMRWGM>. You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[anewton1998]

The wording means that work on EPP is out of scope for the RPP working group, including creation of EPP extensions that are functional equivalents of RPP.

[rpp-ietf]

How about simplifying this to read? “Creation of EPP extensions is out of scope for the RRP working group.” We don’t need to specify why the EPP extensions are being created, but that all EPP extension work is out-of-scope for the RRP working group.

…

-- 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: Friday, November 15, 2024 at 2:50 PM To: SIDN/ietf-wg-rpp-charter ***@***.***> Cc: rpp-ietf ***@***.***>, Comment ***@***.***> Subject: [EXTERNAL] [rpp] Re: [SIDN/ietf-wg-rpp-charter] Clarify REGEXT out-of-scope (Issue #36) 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. The wording means that work on EPP is out of scope for the RPP working group, including creation of EPP extensions that are functional equivalents of RPP. — Reply to this email directly, view it on GitHub<https://secure-web.cisco.com/1IHjTslC-ZDDhXZfUnhYQBpQLK0egZ3l4e_uazlNkynxogwyw3Wtb8fGjlLHNowFpIZ0a5w9uAnkkY50nTR8UgQm0lbMtU4Sd337ZP2kOCevTyFrGbEAOoo8qnme1UplC1lrDnXnFnLQUsrIQKP7mnzbh-ZVXD1Dw7p7Qef-Cdjch618CRWxUjM9vbFVqmMYvHdr8uhPX-hJ6HIzSimgXlcU7B5flK6qf6aOwJA5z5EFvsfhqz-f8xJlQODKQj53JUJAorp6YV_st5RAXNEp6uZNS2UogNTU144wvM_x_nRc/https%3A%2F%2Fgithub.com%2FSIDN%2Fietf-wg-rpp-charter%2Fissues%2F36%23issuecomment-2479811976>, or unsubscribe<https://secure-web.cisco.com/1eIo1SFxyc8KViTJW4qg4P9hNWBgXaeJRl4nZWh4u91i4_NCC-1kYBYSmLax8P3Wl9kfwxl2FMEFfH8tgCfoZJx4dEelCnZJd7QlZi97ccjuQloL8SWRNQb3YXisHsDpsESGXE32AnUK0qqMfDG3miql8Wgp8-EifeYeKQhHm61ymwWweLKQuEXgHX5I9YayWh0EqqMvMnoqfgNmlkIe0lTRRCZYOyS6zv0j_gl7I8JHsZxBCe9GlSrAdLfkiX-yEK4cp7TWS2a8HLrEhKBwQmzGRyw05nitbR0nUsrLEXKo/https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FBM5CYNJYBQP6F2KM2BUF3VL2AZGANAVCNFSM6AAAAABR3RXPD6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINZZHAYTCOJXGY>. You are receiving this because you commented.Message ID: ***@***.***>

[mwullink]

+1 - Maarten How about simplifying this to read? “Creation of EPP extensions is out of scope for the RRP working group.” We don’t need to specify why the EPP extensions are being created, but that all EPP extension work is out-of-scope for the RRP working group.

…

-- 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: Friday, November 15, 2024 at 2:50 PM To: SIDN/ietf-wg-rpp-charter ***@***.***> Cc: rpp-ietf ***@***.***>, Comment ***@***.***> Subject: [EXTERNAL] [rpp] Re: [SIDN/ietf-wg-rpp-charter] Clarify REGEXT out-of-scope (Issue #36) 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. The wording means that work on EPP is out of scope for the RPP working group, including creation of EPP extensions that are functional equivalents of RPP. — Reply to this email directly, view it on GitHub<https://secure-web.cisco.com/1IHjTslC-ZDDhXZfUnhYQBpQLK0egZ3l4e_uazlNkynxogwyw3Wtb8fGjlLHNowFpIZ0a5w9uAnkkY50nTR8UgQm0lbMtU4Sd337ZP2kOCevTyFrGbEAOoo8qnme1UplC1lrDnXnFnLQUsrIQKP7mnzbh-ZVXD1Dw7p7Qef-Cdjch618CRWxUjM9vbFVqmMYvHdr8uhPX-hJ6HIzSimgXlcU7B5flK6qf6aOwJA5z5EFvsfhqz-f8xJlQODKQj53JUJAorp6YV_st5RAXNEp6uZNS2UogNTU144wvM_x_nRc/https%3A%2F%2Fgithub.com%2FSIDN%2Fietf-wg-rpp-charter%2Fissues%2F36%23issuecomment-2479811976>, or unsubscribe<https://secure-web.cisco.com/1eIo1SFxyc8KViTJW4qg4P9hNWBgXaeJRl4nZWh4u91i4_NCC-1kYBYSmLax8P3Wl9kfwxl2FMEFfH8tgCfoZJx4dEelCnZJd7QlZi97ccjuQloL8SWRNQb3YXisHsDpsESGXE32AnUK0qqMfDG3miql8Wgp8-EifeYeKQhHm61ymwWweLKQuEXgHX5I9YayWh0EqqMvMnoqfgNmlkIe0lTRRCZYOyS6zv0j_gl7I8JHsZxBCe9GlSrAdLfkiX-yEK4cp7TWS2a8HLrEhKBwQmzGRyw05nitbR0nUsrLEXKo/https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FBM5CYNJYBQP6F2KM2BUF3VL2AZGANAVCNFSM6AAAAABR3RXPD6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINZZHAYTCOJXGY>. You are receiving this because you commented.Message ID: ***@***.***> — Reply to this email directly, view it on GitHub<#36 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AALSFIEME2FNMEAK6RKP4JT2AZICFAVCNFSM6AAAAABR3RXPD6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINZZHAZTOMZUGY>. You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[pawel-kow]

Addition to the text was aimed to address #20. I'm ok to go with simple text as well.

[anewton1998]

The current text says:

The REGEXT working group is chartered to maintain and standardize extensions to EPP. Consequently, any extensions or changes to EPP, including those related to RPP functionality that do not exist in EPP, are explicitly out of scope for the RPP working group.

"any extensions or changes to EPP" covers the creation of EPP extensions. It seems to me and additional sentence of "Creation of EPP extensions is out of scope..." is both unnecessary and more wordy. I am inclined to close this issue absent a compelling reason not do so.

[rpp-ietf]

Andy, My proposal was to replace: “The REGEXT working group is chartered to maintain and standardize extensions to EPP. Consequently, any extensions or changes to EPP, including those related to RPP functionality that do not exist in EPP, are explicitly out of scope for the RPP working group.” With: “Creation of EPP extensions is out of scope.” Or “Creation of EPP extensions or updates to EPP extensions is out of scope.” We don’t need to repeat the purpose of REGEXT or project the reasons why EPP extension work is out-of-scope. 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: Wednesday, November 20, 2024 at 3:50 PM To: SIDN/ietf-wg-rpp-charter ***@***.***> Cc: rpp-ietf ***@***.***>, Comment ***@***.***> Subject: [EXTERNAL] [rpp] Re: [SIDN/ietf-wg-rpp-charter] Clarify REGEXT out-of-scope (Issue #36) 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. The current text says: The REGEXT working group is chartered to maintain and standardize extensions to EPP. Consequently, any extensions or changes to EPP, including those related to RPP functionality that do not exist in EPP, are explicitly out of scope for the RPP working group. "any extensions or changes to EPP" covers the creation of EPP extensions. It seems to me and additional sentence of "Creation of EPP extensions is out of scope..." is both unnecessary and more wordy. I am inclined to close this issue absent a compelling reason not do so. — Reply to this email directly, view it on GitHub<https://secure-web.cisco.com/1fSK_McQfTHquQw2DY2g2Vh-zp26QSfHA7uGwggIVHi92WHjjXkr7BKFcYRyQTLbaHQIrWIWsNwQMjpLbvexCrbeGhU-qNK88l02Sw1x2maqruzIgtB8DZ1NOZ1IbbMC-u6MfZvwWzTj_F1MFLi3vrtIg5Cubg40REjAi0j0mo0uWeEvVHfr4rpTVd8jUvLOUWK-2mL9rUYDJyHRI9D8LMO5f6xVv7zadIgkI-R4jXJAOgWmrbMlTV-Umibf6IEsNAKlt_D_H8JBKFqRUkxG2gTWXcS8bVB0OOlZ_O-3WvxE/https%3A%2F%2Fgithub.com%2FSIDN%2Fietf-wg-rpp-charter%2Fissues%2F36%23issuecomment-2489515394>, or unsubscribe<https://secure-web.cisco.com/18VjSMZ-wnPqcZG2IionzU8baPygbtkbe271vkWQjOarALPPVwpleQM7TBHtgko78Lvi72uHpA13iWQcL7YNY_V9fWeSndGgZ1-h4esEZoAwRJrihAU9iUAim32F4Ew6gK42Mhk2WiloiwEO2xRi79Spt8b8ngwuorHija5Jfmd6HuoboIaenjxX-Cwo3-PdIdYi8oFrazXCkh5-pLGKm0crk8lZLCnstlFV44iOBPsYdcsC-2gZabYKUTWIZq2STWKCWV0Xeh1yodlgMbVycVXiTe1Ksl1vU3xJ2N-1e4RY/https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FBM5CYNNXWPSSUAATKWFY6JD2BTYUPAVCNFSM6AAAAABR3RXPD6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOBZGUYTKMZZGQ>. You are receiving this because you commented.Message ID: ***@***.***>

[jasdips]

TBH, I find the current paragraph more contextual. But, no strong opinion here if we go with James' suggestion.

[anewton1998]

We don’t need to repeat the purpose of REGEXT or project the reasons why EPP extension work is out-of-scope.

The concern regarding the interplay between EPP and RPP has been brought up multiple times, so I'd prefer to keep the context. I'll let the AD determine if context needs to be removed.