addressing issue #26 (mapping RPP and EPP as deliverable) #40
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
mwullink
reviewed
Nov 21, 2024
rpp-charter.md
Outdated
| @@ -64,6 +64,7 @@ After finding consensus regarding requirements, the next documents to be deliver | |||
| by this working group will describe the core architecture and JSON mapping of RPP with regard to the | |||
| provisioning of domain names, followed by any specifications necessary | |||
| to implement the core architecture and the JSON mapping for the different objects to be provisioned. | |||
| These documents may then be followed by mappings between RPP and EPP. | |||
There was a problem hiding this comment.
I think the "mappings between RPP and EPP" document must be moved.
new proposal:
"this working group will describe the core architecture and JSON mapping of RPP with regard to the
provisioning of domain names. These documents are then followed by a document describing the mappings between RPP and EPP. Followed by any specifications necessary to implement the core architecture and the JSON mapping for the different objects to be provisioned."
Rationale:
It may take some time (if ever) before other objects (numbers? widgets?) are described in documents, implementers need a mapping between RPP and EPP after the core architecture and JSON mapping of RPP for domains names is completed.
There was a problem hiding this comment.
How does a mapping occur before any core specifications? It seems to me that if you want to map "blah": "foo" in JSON to <blah>foo</blah> in XML, you need concrete implementation specifications.
There was a problem hiding this comment.
no, i don't mean to say that the mapping from RPP to EPP comes first.
i think this is the correct order:
1: the core architecture and JSON mapping of RPP with regard to the provisioning of domain names
2: mappings between RPP and EPP.
3: any other (optional) object mapping, e.g. numbers.
because at the moment it is not clear that other object mapping (3) will ever happen and if it does how long this will take. Therefore, it's better to create the mappings between RPP and EPP (2) immediately after the core architecture and JSON mapping of RPP (1)
|
I believe the order is:
1. Analysis of the EPP extensions and the EPP extension points to identify what is desired and not desired in RPP
2. The core RPP architecture that includes the layers, the base set of features and the extension points
3. Define the RPP object mappings using the EPP object mappings and applicable EPP extensions as a baseline that will be built in RPP
* The RRP object mappings should be defined as extensions of RPP, just like the domain name, host, and contact object mappings are defined as extensions in EPP.
4. Define the RPP extensions that apply across many RPP objects based on applicable EPP extensions that are desired in RPP
We should leverage the good practices followed in EPP for RPP. I particular like everything being defined as an extension since it demonstrates the extensibility with the needed signaling and versioning support and provides a concrete example for future extensions.
--
JG
***@***.***
James Gould
Fellow Engineer
***@***.******@***.***>
703-948-3271
12061 Bluemont Way
Reston, VA 20190
Verisign.com<http://verisigninc.com/>
From: Maarten Wullink ***@***.***>
Reply-To: SIDN/ietf-wg-rpp-charter ***@***.***>
Date: Thursday, November 21, 2024 at 8:18 AM
To: SIDN/ietf-wg-rpp-charter ***@***.***>
Cc: Subscribed ***@***.***>
Subject: [EXTERNAL] [rpp] Re: [SIDN/ietf-wg-rpp-charter] addressing issue #26 (PR #40)
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.
@mwullink commented on this pull request.
________________________________
In rpp-charter.md<https://secure-web.cisco.com/1dXLKatr9FfFzWdinkGNgzT5dG2DdVozri-cvlaPySaih-1bFkdxjuTv7bl4cS73S40v0pvGuNikez3b0V1kPCrLhDfTYGvTJY6bUDYgNrbLlW6iIX_IeV0Uz1msqKf4q2B3AiYQ89cemReaoS1jAe4nRT1t2Bpre8YtwmV4j71txo6SX67uH5MRUia-9_BnU0dD71JqBXBp5jcFfwVbPwMEXbI8b17NSAaCn0MbYR9aQVepTReB5LRVsbzW2fFndyobG2AVJ18VKq0v39L_YBBLf1dPZgYKZ68qHn2CquQ4/https%3A%2F%2Fgithub.com%2FSIDN%2Fietf-wg-rpp-charter%2Fpull%2F40%23discussion_r1852047244>:
@@ -64,6 +64,7 @@ After finding consensus regarding requirements, the next documents to be deliver
by this working group will describe the core architecture and JSON mapping of RPP with regard to the
provisioning of domain names, followed by any specifications necessary
to implement the core architecture and the JSON mapping for the different objects to be provisioned.
+These documents may then be followed by mappings between RPP and EPP.
no, i don't mean to say that the mapping from RPP to EPP comes first.
i think this is the correct order:
1: the core architecture and JSON mapping of RPP with regard to the provisioning of domain names
2: mappings between RPP and EPP.
3: any other (optional) object mapping, e.g. numbers.
because at the moment it is not clear that other object mapping (3) will ever happen and if it does how long this will take. Therefore, it's better to create the mappings between RPP and EPP (2) immediately after the core architecture and JSON mapping of RPP (1)
—
Reply to this email directly, view it on GitHub<https://secure-web.cisco.com/1dXLKatr9FfFzWdinkGNgzT5dG2DdVozri-cvlaPySaih-1bFkdxjuTv7bl4cS73S40v0pvGuNikez3b0V1kPCrLhDfTYGvTJY6bUDYgNrbLlW6iIX_IeV0Uz1msqKf4q2B3AiYQ89cemReaoS1jAe4nRT1t2Bpre8YtwmV4j71txo6SX67uH5MRUia-9_BnU0dD71JqBXBp5jcFfwVbPwMEXbI8b17NSAaCn0MbYR9aQVepTReB5LRVsbzW2fFndyobG2AVJ18VKq0v39L_YBBLf1dPZgYKZ68qHn2CquQ4/https%3A%2F%2Fgithub.com%2FSIDN%2Fietf-wg-rpp-charter%2Fpull%2F40%23discussion_r1852047244>, or unsubscribe<https://secure-web.cisco.com/1nPXaEXl6G31F84I-qAWG_iSaxnPDsDUM-V4xL4tPKTSePnS3kpPMIHLPTP2IMo7tTMebV9zzQthKrxU14kwTDRYb2PdOKP0ZGu4d4NifESS4WmM9AMt0EcLAny_khXutHOmi_YEWDyZzxNyGJo88xDDMjgTujbih0NdlBnwpMB4UF4WfWXDAaFVNle15NbA_wGFUSXaRI70yvq1ghB46f8HxRXfXg__TKDFQBk0A1qR_iIMLSjWDgESPoeYj9ZmtWWP9ieL-s13E0mTZX8hr2ljteHHXbCyoobJYVi0BvvQ/https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FBM5CYNNTQF46FXBIBPITB4D2BXMRVAVCNFSM6AAAAABSFQQ3O6VHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMZDINJRGM2TQMRWHA>.
You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>
|
pawel-kow
changed the title
|
I think putting things in some order of dependencies is kind of void discussion when it comes to a charter. I would be in favour of adding such deliverable without determining the order of those now. |
|
The wg should deliver an RPP -> EPP mapping document but i agree with Pawel that removing the ordering from the text is a good idea. |
|
I updated this PR to remove the explicit order, instead making it an agreement with the chairs and the AD. I also moved around the paragraphs on requirements since they were intermingled with this one. |
jasdips
reviewed
Nov 21, 2024
| IESG documents addressing the following topics in an order determined through agreement | ||
| of the chairs with the responsible Area Director: | ||
| * core architecture | ||
| * specifications necessary to implement the core architecture |
There was a problem hiding this comment.
What's the difference between the "core architecture" and "specifications necessary to implement the core architecture" topics?
There was a problem hiding this comment.
core architecture could be block diagrams, etc... basically words that explain how things are put together, while specifications necessary to implement them would be "send "foo": "bar" using HTTP GET`.
pawel-kow
reviewed
Nov 21, 2024
rpp-charter.md
Outdated
Comment on lines
63
to
64
| Analysis of the functionality included and commonly used in core EPP for domain names, | ||
| hosts and contacts (RFC5730,5731,5732,5733) may be created as input material for the requirements. |
There was a problem hiding this comment.
I like the rearrangement but noticed the change from "will" to "may".
The discussion on the mailing list so far was rather going into direction that such analysis will be created as an input.
There was a problem hiding this comment.
If nobody is willing to do the analysis or there is no agreement on that analysis, the working group should not stall. This is an area of potential rabbit hole exploring. Thanks for noting this.
There was a problem hiding this comment.
If nobody is willing to do the analysis or there is no agreement on that analysis, the working group should not stall. This is an area of potential rabbit hole exploring. Thanks for noting this.
I think if nobody would be willing to, it would indicate other problems in the working group. The conclusion of the discussion so far was that without this input we may not be able to validate if requirements and architecture are actually correct and complete to fulfil other goals and deliverables.
The text does not mean that there must be only one or more, in which form and even not if there must be a consensus around the analysis. And this is meant like this. More perspectives are typically better on an early stage.
The requirements is where we will be looking after consensus. With analysis done we may expect better quality of requirements coming out of the process.
|
I don’t understand why there would be any debate related to the value of analyzing the features and extensions that exist in the current provisioning protocol for the creation of a new one. The analysis will be input into the requirements. The result should be a set of recommendations for elements in EPP to use, not use, and to redo based on practical experience. Volunteers need to be requested, and my hope is that the experienced EPP technologists will be happy to participate in this analysis. I certainly would like to be involved in the effort. This is a MUST and not a MAY in my opinion.
--
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: Thursday, November 21, 2024 at 5:04 PM
To: SIDN/ietf-wg-rpp-charter ***@***.***>
Cc: rpp-ietf ***@***.***>, Comment ***@***.***>
Subject: [EXTERNAL] [rpp] Re: [SIDN/ietf-wg-rpp-charter] addressing issue #26 (mapping RPP and EPP as deliverable) (PR #40)
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.
@pawel-kow commented on this pull request.
________________________________
In rpp-charter.md<https://secure-web.cisco.com/1BwGpsdn2N9zGq1_u77raDRMSSXyQucvougs687FD-fqyIDhahLbMhZowQpZxNdVPzaQwCsX9M5EQysmZcl22kaKyBkbuimIkyLmIJE6uZ6Xoj3C8o5cPG9qpccPvKvjmxKYj47tnU-RBHlYxd4DllLps-VgdNONlS-tTxJgm9JR1FfJTefh3oV8b1K17PeEqUUJvmmykMfTE45AjTPcc-s_DSsZ_Dzeg_jPWAJ4lzpzziEMIGDsljYa60WaoNLT_zuwVTIhosE2fGnYnkWEc-HILfSZwjRuq9MD5z32lc6w/https%3A%2F%2Fgithub.com%2FSIDN%2Fietf-wg-rpp-charter%2Fpull%2F40%23discussion_r1852969645>:
+Analysis of the functionality included and commonly used in core EPP for domain names,
+hosts and contacts (RFC5730,5731,5732,5733) may be created as input material for the requirements.
If nobody is willing to do the analysis or there is no agreement on that analysis, the working group should not stall. This is an area of potential rabbit hole exploring. Thanks for noting this.
I think if nobody would be willing to, it would indicate other problems in the working group. The conclusion of the discussion so far was that without this input we may not be able to validate if requirements and architecture are actually correct and complete to fulfil other goals and deliverables.
The text does not mean that there must be only one or more, in which form and even not if there must be a consensus around the analysis. And this is meant like this. More perspectives are typically better on an early stage.
The requirements is where we will be looking after consensus. With analysis done we may expect better quality of requirements coming out of the process.
—
Reply to this email directly, view it on GitHub<https://secure-web.cisco.com/1BwGpsdn2N9zGq1_u77raDRMSSXyQucvougs687FD-fqyIDhahLbMhZowQpZxNdVPzaQwCsX9M5EQysmZcl22kaKyBkbuimIkyLmIJE6uZ6Xoj3C8o5cPG9qpccPvKvjmxKYj47tnU-RBHlYxd4DllLps-VgdNONlS-tTxJgm9JR1FfJTefh3oV8b1K17PeEqUUJvmmykMfTE45AjTPcc-s_DSsZ_Dzeg_jPWAJ4lzpzziEMIGDsljYa60WaoNLT_zuwVTIhosE2fGnYnkWEc-HILfSZwjRuq9MD5z32lc6w/https%3A%2F%2Fgithub.com%2FSIDN%2Fietf-wg-rpp-charter%2Fpull%2F40%23discussion_r1852969645>, or unsubscribe<https://secure-web.cisco.com/12XBMiZH6hBkvcmNpDwrNIdawggx9_kznni8hp6CZhqc2-hqJVCWOIU628dhrG-PAFt2PqqcSPICE_59mUAO0QV_Bq0VUyjlPiUvmE_xGznmrY6vTl1YfPW1TnRT7z-_J9uY3DkXiewInl3T5quTIgYlADYxa-_vy1nWw_iRmP3jMuzkUY1tWmdYqX0I_NL_-mppMWX4qeX1dkg6tUqZLoFJPKF-ULiERyUlOUquLYYJsP-MoL0sqnrtR-8hEvhQqHaQh_Jphkf0EG-Ki5Z6sy7Z5qKebjuji1qNZo4AQ9pM/https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FBM5CYNOSJSTDJAS5I5AAU732BZKGHAVCNFSM6AAAAABSFQQ3O6VHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMZDINJSHA2DMNJZGM>.
You are receiving this because you commented.Message ID: ***@***.***>
|
|
I changed the wording to "is expected to be created". The concern is paralysis by analysis that could cause the working group to stall. |
|
Andy,
We can scope the analysis work. The EPP RFCs are well structured and clear with many implementations and there is a registered set of EPP extensions in the EPP extension registry to evaluate. My recommendation is if there are additional unregistered proprietary EPP extensions that should be considered, for the registries to ensure to get them registered in the EPP extension registry.
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: Friday, November 22, 2024 at 9:15 AM
To: SIDN/ietf-wg-rpp-charter ***@***.***>
Cc: rpp-ietf ***@***.***>, Comment ***@***.***>
Subject: [EXTERNAL] [rpp] Re: [SIDN/ietf-wg-rpp-charter] addressing issue #26 (mapping RPP and EPP as deliverable) (PR #40)
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.
I changed the wording to "is expected to be created". The concern is paralysis by analysis that could cause the working group to stall.
—
Reply to this email directly, view it on GitHub<https://secure-web.cisco.com/16iA6ea-VFjM1SUHfDv_-SlB3vAEYt1PhqmBDxzfXhnPXAeRd5XUvuQxRGpG61m2ZW5pk0Qh5pRDmwF918FC7pEg9v9aUr_HNtSXj1QuPHwCbf39eb2jHbRteceSO1qVYOkwCd1t55fYChDN_4-CkHKS4ls-fLiL367DyVvEJMRtu8x0DhEfpNpM5bR9BgBEaQzWekUHcXGJHWpl38huFSof0x-VBp2vHfaNvt4wxy_eb45JAHe-JavSFTxPTD4S4Gmb_bEl6BTGXh4x9g8ghurs-M8cnelbJGy5SXwtA6LU/https%3A%2F%2Fgithub.com%2FSIDN%2Fietf-wg-rpp-charter%2Fpull%2F40%23issuecomment-2493864351>, or unsubscribe<https://secure-web.cisco.com/1cYXZZGtoxH0H_PtGmTHQRsMDjwVnry0Z1BQpUEPw9K26p7BMUKAsR4xj9hmiTQmnMBIitOnQ5wHWZjRghwlREJKGoupD3ErdPKaj3RvBrHhkKZnq2_HApcIzJNNb91mojkrEhW3u_Kb9lVh4sesA8RAf4-tMItHgaStudHrVFDbRWMZu_4Se956qcJs2iB28GKeCeswNVinIFEzjnF0LYhlXUF3gZFKjTrOVHmr0nDBY6rz2gGMge85TgGh8-Yd0JgzWlH7P6V--QJklXflEssMPd67Yqt8tudx-cwfCtNw/https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FBM5CYNP6DWRPVFJ2366CC6T2B44BLAVCNFSM6AAAAABSFQQ3O6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOJTHA3DIMZVGE>.
You are receiving this because you commented.Message ID: ***@***.***>
|
If you mean this wording works better to avoid this risk it is for me a good way forward. Thank you. |
|
BTW: I also kind of volunteer for the analysis work. |
|
There is nothing stopping anybody from starting that work now. :) |
|
Nope, who are the volunteers? It sounds like we have two thus far with me and Pawel (“kind of”, which I take as a “yes”).
…--
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 22, 2024 at 10:07 AM
To: SIDN/ietf-wg-rpp-charter ***@***.***>
Cc: rpp-ietf ***@***.***>, Comment ***@***.***>
Subject: [EXTERNAL] [rpp] Re: [SIDN/ietf-wg-rpp-charter] addressing issue #26 (mapping RPP and EPP as deliverable) (PR #40)
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.
There is nothing stopping anybody from starting that work now. :)
—
Reply to this email directly, view it on GitHub<https://secure-web.cisco.com/1CADewsi1b41V40qnW__MVHSjgN8OI0a-QYLhlwpynAqRJjnmGODn4d9AaWFpHuSKPU_RnHiOQt_jVc8UCL_3bvOXMPtpi3m4H3JhSQA7_lNOD478ZBRZMASWY9MbaYb2G1rULX6wygG1QFkvmiuKWNJ9xuhdhcHAQnrbih4gXtCsMdnTP-9R2L2nezirQXzpe-CDo6XvqLg4IKZMCUMdnt1KihPSsNxiX-9BjNybqbjosYSVWk7JuSWJ8qsXgH7ffOoKvWtw2CZMAFxEwTpfjLtA3f0SkyQqCDKeQXQXCTg/https%3A%2F%2Fgithub.com%2FSIDN%2Fietf-wg-rpp-charter%2Fpull%2F40%23issuecomment-2493969790>, or unsubscribe<https://secure-web.cisco.com/1E91U-hhFhbfu7XqqauynyTJNWiJZnBjDyWk2hggFvD_RDXWbxLagUQuc45HVZmQOeJwoghoDMx3Aol0Fgpnu32oXGM1t5KFA7kt0nUXnvuw4a4qrn4jzCRIYMfcH8g__W6GJFhyG6dKA4H7zq2XsSWI3f1it9VgaCWcGkQOlBSirdRFoYvvIMbxZngk0cTkuiU9fNYQ95h3AxPImjVdYxxF8egUvShpD0IxbyfjuCEVpb13MwtVDWXmp8c7rL5ZSKSUSQSNM3v_LI79r0gJ1DlKx5YvZ-wcVSVNiKgE01GE/https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FBM5CYNOXTEWWATZ63DO5HV32B5CBRAVCNFSM6AAAAABSFQQ3O6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOJTHE3DSNZZGA>.
You are receiving this because you commented.Message ID: ***@***.***>
|
Closed
|
I can help out with this also.
Thanks,
Jody Kolker
319-329-9805 (mobile)
Please contact my direct supervisor Scott Courtney ***@***.******@***.***>) with any feedback.
This email message and any attachments hereto is intended for use only by the addressee(s) named herein and may contain confidential information. If you have received this email in error, please immediately notify the sender and permanently delete the original and any copy of this message and its attachments.
From: Gould, James ***@***.***>
Sent: Friday, November 22, 2024 10:52 AM
To: ***@***.***; ***@***.***
Cc: ***@***.***; ***@***.***
Subject: [rpp] Re: [SIDN/ietf-wg-rpp-charter] addressing issue #26 (mapping RPP and EPP as deliverable) (PR #40)
Nope, who are the volunteers? It sounds like we have two thus far with me and Pawel (“kind of”, which I take as a “yes”). -- JG James Gould Fellow Engineer jgould@ Verisign. com 703-948-3271 12061 Bluemont Way Reston, VA 20190 Verisign. com From:
ZjQcmQRYFpfptBannerStart
This Message Is From an External Sender
This message came from outside your organization.
ZjQcmQRYFpfptBannerEnd
Nope, who are the volunteers? It sounds like we have two thus far with me and Pawel (“kind of”, which I take as a “yes”).
…--
JG
***@***.***
James Gould
Fellow Engineer
***@***.******@***.***>
703-948-3271
12061 Bluemont Way
Reston, VA 20190
Verisign.com<https://urldefense.com/v3/__http:/verisigninc.com/__;!!Hj18uoVe_Lnx!qezaWBMKflaHLRuh8tcwI3itKgXMzPYbdF_eDCgpXVXisGv-jTVUoD6cOxNG9fqdom83MeQuhZcFhiYvXXSnFJvojASHy609$>
From: Andrew Newton ***@***.******@***.***>>
Reply-To: SIDN/ietf-wg-rpp-charter ***@***.******@***.***>>
Date: Friday, November 22, 2024 at 10:07 AM
To: SIDN/ietf-wg-rpp-charter ***@***.******@***.***>>
Cc: rpp-ietf ***@***.******@***.***>>, Comment ***@***.******@***.***>>
Subject: [EXTERNAL] [rpp] Re: [SIDN/ietf-wg-rpp-charter] addressing issue #26 (mapping RPP and EPP as deliverable) (PR #40)
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.
There is nothing stopping anybody from starting that work now. :)
—
Reply to this email directly, view it on GitHub<https://urldefense.com/v3/__https:/secure-web.cisco.com/1CADewsi1b41V40qnW__MVHSjgN8OI0a-QYLhlwpynAqRJjnmGODn4d9AaWFpHuSKPU_RnHiOQt_jVc8UCL_3bvOXMPtpi3m4H3JhSQA7_lNOD478ZBRZMASWY9MbaYb2G1rULX6wygG1QFkvmiuKWNJ9xuhdhcHAQnrbih4gXtCsMdnTP-9R2L2nezirQXzpe-CDo6XvqLg4IKZMCUMdnt1KihPSsNxiX-9BjNybqbjosYSVWk7JuSWJ8qsXgH7ffOoKvWtw2CZMAFxEwTpfjLtA3f0SkyQqCDKeQXQXCTg/https*3A*2F*2Fgithub.com*2FSIDN*2Fietf-wg-rpp-charter*2Fpull*2F40*23issuecomment-2493969790__;JSUlJSUlJSU!!Hj18uoVe_Lnx!qezaWBMKflaHLRuh8tcwI3itKgXMzPYbdF_eDCgpXVXisGv-jTVUoD6cOxNG9fqdom83MeQuhZcFhiYvXXSnFJvojCJKMPXG$>, or unsubscribe<https://urldefense.com/v3/__https:/secure-web.cisco.com/1E91U-hhFhbfu7XqqauynyTJNWiJZnBjDyWk2hggFvD_RDXWbxLagUQuc45HVZmQOeJwoghoDMx3Aol0Fgpnu32oXGM1t5KFA7kt0nUXnvuw4a4qrn4jzCRIYMfcH8g__W6GJFhyG6dKA4H7zq2XsSWI3f1it9VgaCWcGkQOlBSirdRFoYvvIMbxZngk0cTkuiU9fNYQ95h3AxPImjVdYxxF8egUvShpD0IxbyfjuCEVpb13MwtVDWXmp8c7rL5ZSKSUSQSNM3v_LI79r0gJ1DlKx5YvZ-wcVSVNiKgE01GE/https*3A*2F*2Fgithub.com*2Fnotifications*2Funsubscribe-auth*2FBM5CYNOXTEWWATZ63DO5HV32B5CBRAVCNFSM6AAAAABSFQQ3O6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOJTHE3DSNZZGA__;JSUlJSUl!!Hj18uoVe_Lnx!qezaWBMKflaHLRuh8tcwI3itKgXMzPYbdF_eDCgpXVXisGv-jTVUoD6cOxNG9fqdom83MeQuhZcFhiYvXXSnFJvojI0kttWD$>.
You are receiving this because you commented.Message ID: ***@***.******@***.***>>
|
|
Jody,
Thanks for volunteering! Any more volunteers? We currently have me, Pawel, and Jody on the tiger team to perform the EPP extensibility and extensions analysis. Once the tiger team is formed, I can setup a time for us to meet to discuss the analysis approach and the split out of the work. I believe the wiki is the best place to capture this. This work can be reflected as a deliverable in the charter. How about updating the start of the Deliverables section of the Charter to read?
This working group will publish on its wiki its operational practices,
including but not limited to, the adoption of work items, usage of
tools beyond the IETF’s datatracker, analysis of EPP extensibility and the existing EPP extensions,
and implementation requirements for the promotion of work to the IESG.
…--
JG
***@***.***
James Gould
Fellow Engineer
***@***.******@***.***>
703-948-3271
12061 Bluemont Way
Reston, VA 20190
Verisign.com<http://verisigninc.com/>
From: Jody Kolker ***@***.***>
Date: Wednesday, December 4, 2024 at 8:18 AM
To: James Gould ***@***.***>, ***@***.***" ***@***.***>, ***@***.***" ***@***.***>
Cc: ***@***.***" ***@***.***>, ***@***.***" ***@***.***>
Subject: [EXTERNAL] RE: [rpp] Re: [SIDN/ietf-wg-rpp-charter] addressing issue #26 (mapping RPP and EPP as deliverable) (PR #40)
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.
I can help out with this also.
Thanks,
Jody Kolker
319-329-9805 (mobile)
Please contact my direct supervisor Scott Courtney ***@***.******@***.***>) with any feedback.
This email message and any attachments hereto is intended for use only by the addressee(s) named herein and may contain confidential information. If you have received this email in error, please immediately notify the sender and permanently delete the original and any copy of this message and its attachments.
From: Gould, James ***@***.***>
Sent: Friday, November 22, 2024 10:52 AM
To: ***@***.***; ***@***.***
Cc: ***@***.***; ***@***.***
Subject: [rpp] Re: [SIDN/ietf-wg-rpp-charter] addressing issue #26 (mapping RPP and EPP as deliverable) (PR #40)
Nope, who are the volunteers? It sounds like we have two thus far with me and Pawel (“kind of”, which I take as a “yes”). -- JG James Gould Fellow Engineer jgould@ Verisign. com 703-948-3271 12061 Bluemont Way Reston, VA 20190 Verisign. com From:
ZjQcmQRYFpfptBannerStart
This Message Is From an External Sender
This message came from outside your organization.
ZjQcmQRYFpfptBannerEnd
Nope, who are the volunteers? It sounds like we have two thus far with me and Pawel (“kind of”, which I take as a “yes”).
--
JG
***@***.***
James Gould
Fellow Engineer
***@***.******@***.***>
703-948-3271
12061 Bluemont Way
Reston, VA 20190
Verisign.com<https://secure-web.cisco.com/1NkINdsoI0K9-fQz4EaOqiVWwn-COLYC4D7V4ng3ptlmpGIbI-qnxzLaXUvN8u6uscEDeiHHze5nNugzFB6jcR1meImNMYLtQMlefvz12sbMi185ASWy3Ozvk6mkT4vQqMTzv2voYPKWrCjlWcVqIAXMyZeEBAtPkWwedgVL2MLz26PPyNJxF1dSpD76GoI_QQiAf1FOQnM56up3bAWxac47RcqKjW2NW-l9vexXeDutLxhABYFdAYl1P6fDsrvuFeaP4ObraVHhOWOU3zXuuQjv5cp7LcC3MUkgmjrIJFpM/https%3A%2F%2Furldefense.com%2Fv3%2F__http%3A%2Fverisigninc.com%2F__%3B%21%21Hj18uoVe_Lnx%21qezaWBMKflaHLRuh8tcwI3itKgXMzPYbdF_eDCgpXVXisGv-jTVUoD6cOxNG9fqdom83MeQuhZcFhiYvXXSnFJvojASHy609%24>
From: Andrew Newton ***@***.******@***.***>>
Reply-To: SIDN/ietf-wg-rpp-charter ***@***.******@***.***>>
Date: Friday, November 22, 2024 at 10:07 AM
To: SIDN/ietf-wg-rpp-charter ***@***.******@***.***>>
Cc: rpp-ietf ***@***.******@***.***>>, Comment ***@***.******@***.***>>
Subject: [EXTERNAL] [rpp] Re: [SIDN/ietf-wg-rpp-charter] addressing issue #26 (mapping RPP and EPP as deliverable) (PR #40)
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.
There is nothing stopping anybody from starting that work now. :)
—
Reply to this email directly, view it on GitHub<https://secure-web.cisco.com/1dw8k-UH_XvJHqWtgnvDC554z9NAJut-S18I2incRn0SjWq_J4rzyTYmcxr30yFHehigHMXSs5aMKVZonskcFQ7H6YJ40L4JbbpdM9HkTTIq9p-IRsgohWEVAsZeWtQ-ONQDTg7woXfS3ALlXJAMt29MSRsK6PGr-FfhYuo1-9vtTfno2OmMBx4jCpNsBZEw0jLj3NzOKSEJA5AvGheu-n4WXgNlm9jCN-TSANMeDx1c63qlktrodm_jSVanhgM7wNvZi39qOmjp7cvf3TNmjJz-unQMf_9uk-bciJ1iIeaU/https%3A%2F%2Furldefense.com%2Fv3%2F__https%3A%2Fsecure-web.cisco.com%2F1CADewsi1b41V40qnW__MVHSjgN8OI0a-QYLhlwpynAqRJjnmGODn4d9AaWFpHuSKPU_RnHiOQt_jVc8UCL_3bvOXMPtpi3m4H3JhSQA7_lNOD478ZBRZMASWY9MbaYb2G1rULX6wygG1QFkvmiuKWNJ9xuhdhcHAQnrbih4gXtCsMdnTP-9R2L2nezirQXzpe-CDo6XvqLg4IKZMCUMdnt1KihPSsNxiX-9BjNybqbjosYSVWk7JuSWJ8qsXgH7ffOoKvWtw2CZMAFxEwTpfjLtA3f0SkyQqCDKeQXQXCTg%2Fhttps%2A3A%2A2F%2A2Fgithub.com%2A2FSIDN%2A2Fietf-wg-rpp-charter%2A2Fpull%2A2F40%2A23issuecomment-2493969790__%3BJSUlJSUlJSU%21%21Hj18uoVe_Lnx%21qezaWBMKflaHLRuh8tcwI3itKgXMzPYbdF_eDCgpXVXisGv-jTVUoD6cOxNG9fqdom83MeQuhZcFhiYvXXSnFJvojCJKMPXG%24>, or unsubscribe<https://secure-web.cisco.com/1KDIKWcOy1NDiAlGp7huq9NhgDYb7H7elqXpX6dO4E3mf4KQzDbXbzgzuY9qXwsfI0x0OY_cknyYQifVzCF8pd9GsUu9kntS7yHJJarr24sQrPZdb03bHHJgJS96vyPMo36LjhqHMvcDwGgGpSnbhU9qS6tBgh19vo9vZKnan0oL40EIBQ14i6g7ePuAqBz_BHaR16DZL7lNc01oOKvda7yVGhFxyUrqSJwiKFD06tNrM-GUtlwtRh48cDL0CowgUjnTynbrll_dMsu4p_XAwL-k9QD2r2wZT2lLMlMhBkOY/https%3A%2F%2Furldefense.com%2Fv3%2F__https%3A%2Fsecure-web.cisco.com%2F1E91U-hhFhbfu7XqqauynyTJNWiJZnBjDyWk2hggFvD_RDXWbxLagUQuc45HVZmQOeJwoghoDMx3Aol0Fgpnu32oXGM1t5KFA7kt0nUXnvuw4a4qrn4jzCRIYMfcH8g__W6GJFhyG6dKA4H7zq2XsSWI3f1it9VgaCWcGkQOlBSirdRFoYvvIMbxZngk0cTkuiU9fNYQ95h3AxPImjVdYxxF8egUvShpD0IxbyfjuCEVpb13MwtVDWXmp8c7rL5ZSKSUSQSNM3v_LI79r0gJ1DlKx5YvZ-wcVSVNiKgE01GE%2Fhttps%2A3A%2A2F%2A2Fgithub.com%2A2Fnotifications%2A2Funsubscribe-auth%2A2FBM5CYNOXTEWWATZ63DO5HV32B5CBRAVCNFSM6AAAAABSFQQ3O6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOJTHE3DSNZZGA__%3BJSUlJSUl%21%21Hj18uoVe_Lnx%21qezaWBMKflaHLRuh8tcwI3itKgXMzPYbdF_eDCgpXVXisGv-jTVUoD6cOxNG9fqdom83MeQuhZcFhiYvXXSnFJvojI0kttWD%24>.
You are receiving this because you commented.Message ID: ***@***.******@***.***>>
|
|
Count me in also.
-
Maarten
Op 4 dec 2024, om 14:36 heeft rpp-ietf ***@***.***> het volgende geschreven:
Jody,
Thanks for volunteering! Any more volunteers? We currently have me, Pawel, and Jody on the tiger team to perform the EPP extensibility and extensions analysis. Once the tiger team is formed, I can setup a time for us to meet to discuss the analysis approach and the split out of the work. I believe the wiki is the best place to capture this. This work can be reflected as a deliverable in the charter. How about updating the start of the Deliverables section of the Charter to read?
This working group will publish on its wiki its operational practices,
including but not limited to, the adoption of work items, usage of
tools beyond the IETF’s datatracker, analysis of EPP extensibility and the existing EPP extensions,
and implementation requirements for the promotion of work to the IESG.
…--
JG
***@***.***
James Gould
Fellow Engineer
***@***.******@***.***>
703-948-3271
12061 Bluemont Way
Reston, VA 20190
Verisign.com<http://verisigninc.com/>
From: Jody Kolker ***@***.***>
Date: Wednesday, December 4, 2024 at 8:18 AM
To: James Gould ***@***.***>, ***@***.***" ***@***.***>, ***@***.***" ***@***.***>
Cc: ***@***.***" ***@***.***>, ***@***.***" ***@***.***>
Subject: [EXTERNAL] RE: [rpp] Re: [SIDN/ietf-wg-rpp-charter] addressing issue #26 (mapping RPP and EPP as deliverable) (PR #40)
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.
I can help out with this also.
Thanks,
Jody Kolker
319-329-9805 (mobile)
Please contact my direct supervisor Scott Courtney ***@***.******@***.***>) with any feedback.
This email message and any attachments hereto is intended for use only by the addressee(s) named herein and may contain confidential information. If you have received this email in error, please immediately notify the sender and permanently delete the original and any copy of this message and its attachments.
From: Gould, James ***@***.***>
Sent: Friday, November 22, 2024 10:52 AM
To: ***@***.***; ***@***.***
Cc: ***@***.***; ***@***.***
Subject: [rpp] Re: [SIDN/ietf-wg-rpp-charter] addressing issue #26 (mapping RPP and EPP as deliverable) (PR #40)
Nope, who are the volunteers? It sounds like we have two thus far with me and Pawel (“kind of”, which I take as a “yes”). -- JG James Gould Fellow Engineer jgould@ Verisign. com 703-948-3271 12061 Bluemont Way Reston, VA 20190 Verisign. com From:
ZjQcmQRYFpfptBannerStart
This Message Is From an External Sender
This message came from outside your organization.
ZjQcmQRYFpfptBannerEnd
Nope, who are the volunteers? It sounds like we have two thus far with me and Pawel (“kind of”, which I take as a “yes”).
--
JG
***@***.***
James Gould
Fellow Engineer
***@***.******@***.***>
703-948-3271
12061 Bluemont Way
Reston, VA 20190
Verisign.com<https://secure-web.cisco.com/1NkINdsoI0K9-fQz4EaOqiVWwn-COLYC4D7V4ng3ptlmpGIbI-qnxzLaXUvN8u6uscEDeiHHze5nNugzFB6jcR1meImNMYLtQMlefvz12sbMi185ASWy3Ozvk6mkT4vQqMTzv2voYPKWrCjlWcVqIAXMyZeEBAtPkWwedgVL2MLz26PPyNJxF1dSpD76GoI_QQiAf1FOQnM56up3bAWxac47RcqKjW2NW-l9vexXeDutLxhABYFdAYl1P6fDsrvuFeaP4ObraVHhOWOU3zXuuQjv5cp7LcC3MUkgmjrIJFpM/https%3A%2F%2Furldefense.com%2Fv3%2F__http%3A%2Fverisigninc.com%2F__%3B%21%21Hj18uoVe_Lnx%21qezaWBMKflaHLRuh8tcwI3itKgXMzPYbdF_eDCgpXVXisGv-jTVUoD6cOxNG9fqdom83MeQuhZcFhiYvXXSnFJvojASHy609%24>
From: Andrew Newton ***@***.******@***.***>>
Reply-To: SIDN/ietf-wg-rpp-charter ***@***.******@***.***>>
Date: Friday, November 22, 2024 at 10:07 AM
To: SIDN/ietf-wg-rpp-charter ***@***.******@***.***>>
Cc: rpp-ietf ***@***.******@***.***>>, Comment ***@***.******@***.***>>
Subject: [EXTERNAL] [rpp] Re: [SIDN/ietf-wg-rpp-charter] addressing issue #26 (mapping RPP and EPP as deliverable) (PR #40)
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.
There is nothing stopping anybody from starting that work now. :)
—
Reply to this email directly, view it on GitHub<https://secure-web.cisco.com/1dw8k-UH_XvJHqWtgnvDC554z9NAJut-S18I2incRn0SjWq_J4rzyTYmcxr30yFHehigHMXSs5aMKVZonskcFQ7H6YJ40L4JbbpdM9HkTTIq9p-IRsgohWEVAsZeWtQ-ONQDTg7woXfS3ALlXJAMt29MSRsK6PGr-FfhYuo1-9vtTfno2OmMBx4jCpNsBZEw0jLj3NzOKSEJA5AvGheu-n4WXgNlm9jCN-TSANMeDx1c63qlktrodm_jSVanhgM7wNvZi39qOmjp7cvf3TNmjJz-unQMf_9uk-bciJ1iIeaU/https%3A%2F%2Furldefense.com%2Fv3%2F__https%3A%2Fsecure-web.cisco.com%2F1CADewsi1b41V40qnW__MVHSjgN8OI0a-QYLhlwpynAqRJjnmGODn4d9AaWFpHuSKPU_RnHiOQt_jVc8UCL_3bvOXMPtpi3m4H3JhSQA7_lNOD478ZBRZMASWY9MbaYb2G1rULX6wygG1QFkvmiuKWNJ9xuhdhcHAQnrbih4gXtCsMdnTP-9R2L2nezirQXzpe-CDo6XvqLg4IKZMCUMdnt1KihPSsNxiX-9BjNybqbjosYSVWk7JuSWJ8qsXgH7ffOoKvWtw2CZMAFxEwTpfjLtA3f0SkyQqCDKeQXQXCTg%2Fhttps%2A3A%2A2F%2A2Fgithub.com%2A2FSIDN%2A2Fietf-wg-rpp-charter%2A2Fpull%2A2F40%2A23issuecomment-2493969790__%3BJSUlJSUlJSU%21%21Hj18uoVe_Lnx%21qezaWBMKflaHLRuh8tcwI3itKgXMzPYbdF_eDCgpXVXisGv-jTVUoD6cOxNG9fqdom83MeQuhZcFhiYvXXSnFJvojCJKMPXG%24>, or unsubscribe<https://secure-web.cisco.com/1KDIKWcOy1NDiAlGp7huq9NhgDYb7H7elqXpX6dO4E3mf4KQzDbXbzgzuY9qXwsfI0x0OY_cknyYQifVzCF8pd9GsUu9kntS7yHJJarr24sQrPZdb03bHHJgJS96vyPMo36LjhqHMvcDwGgGpSnbhU9qS6tBgh19vo9vZKnan0oL40EIBQ14i6g7ePuAqBz_BHaR16DZL7lNc01oOKvda7yVGhFxyUrqSJwiKFD06tNrM-GUtlwtRh48cDL0CowgUjnTynbrll_dMsu4p_XAwL-k9QD2r2wZT2lLMlMhBkOY/https%3A%2F%2Furldefense.com%2Fv3%2F__https%3A%2Fsecure-web.cisco.com%2F1E91U-hhFhbfu7XqqauynyTJNWiJZnBjDyWk2hggFvD_RDXWbxLagUQuc45HVZmQOeJwoghoDMx3Aol0Fgpnu32oXGM1t5KFA7kt0nUXnvuw4a4qrn4jzCRIYMfcH8g__W6GJFhyG6dKA4H7zq2XsSWI3f1it9VgaCWcGkQOlBSirdRFoYvvIMbxZngk0cTkuiU9fNYQ95h3AxPImjVdYxxF8egUvShpD0IxbyfjuCEVpb13MwtVDWXmp8c7rL5ZSKSUSQSNM3v_LI79r0gJ1DlKx5YvZ-wcVSVNiKgE01GE%2Fhttps%2A3A%2A2F%2A2Fgithub.com%2A2Fnotifications%2A2Funsubscribe-auth%2A2FBM5CYNOXTEWWATZ63DO5HV32B5CBRAVCNFSM6AAAAABSFQQ3O6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOJTHE3DSNZZGA__%3BJSUlJSUl%21%21Hj18uoVe_Lnx%21qezaWBMKflaHLRuh8tcwI3itKgXMzPYbdF_eDCgpXVXisGv-jTVUoD6cOxNG9fqdom83MeQuhZcFhiYvXXSnFJvojI0kttWD%24>.
You are receiving this because you commented.Message ID: ***@***.******@***.***>>
—
Reply to this email directly, view it on GitHub<#40 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AALSFIG7MSRWFRW3GNGATG32D4APJAVCNFSM6AAAAABSFQQ3O6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMJXGQZDGMBVGE>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
|
Hi,
With AD hat on, how the working group wants to use wiki's / github is
certainly up to the chairs and the group after it's chartered.
I suggest not including text deferring process requirements to wiki's or
github in the charter text itself.
The text you have is fine for a readme, or a working group website like:
https://ietf-wg-spice.github.io
https://ietf-wg-wimse.github.io
But if you put "requirements for promotion of work to the IESG" in a wiki,
they can change without rechartering, and it will raise issues with the
charter text.
I encourage you to keep the charter concise, and rely on chairs and ADs
interpreting it with rough consensus from the group, to avoid having to
spell out every detail.
Regards,
OS, ART AD
…On Wed, Dec 4, 2024 at 7:38 AM Gould, James <jgould= ***@***.***> wrote:
Jody,
Thanks for volunteering! Any more volunteers? We currently have me,
Pawel, and Jody on the tiger team to perform the EPP extensibility and
extensions analysis. Once the tiger team is formed, I can setup a time for
us to meet to discuss the analysis approach and the split out of the work.
I believe the wiki is the best place to capture this. This work can be
reflected as a deliverable in the charter. How about updating the start of
the Deliverables section of the Charter to read?
This working group will publish on its wiki its operational practices,
including but not limited to, the adoption of work items, usage of
tools beyond the IETF’s datatracker, analysis of EPP extensibility and the
existing EPP extensions,
and implementation requirements for the promotion of work to the IESG.
--
JG
[image: ***@***.***
*James Gould *Fellow Engineer
***@***.***
703-948-3271
12061 Bluemont Way
Reston, VA 20190
Verisign.com <http://verisigninc.com/>
*From: *Jody Kolker ***@***.***>
*Date: *Wednesday, December 4, 2024 at 8:18 AM
*To: *James Gould ***@***.***>, "
***@***.***" <
***@***.***>, "
***@***.***" <
***@***.***>
*Cc: ***@***.***" ***@***.***>, ***@***.***" <
***@***.***>
*Subject: *[EXTERNAL] RE: [rpp] Re: [SIDN/ietf-wg-rpp-charter] addressing
issue #26 (mapping RPP and EPP as deliverable) (PR #40)
*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.
I can help out with this also.
Thanks,
Jody Kolker
319-329-9805 (mobile)
Please contact my direct supervisor Scott Courtney ***@***.***)
with any feedback.
This email message and any attachments hereto is intended for use only by
the addressee(s) named herein and may contain confidential information. If
you have received this email in error, please immediately notify the sender
and permanently delete the original and any copy of this message and its
attachments.
*From:* Gould, James ***@***.***>
*Sent:* Friday, November 22, 2024 10:52 AM
*To:* ***@***.***;
***@***.***
*Cc:* ***@***.***; ***@***.***
*Subject:* [rpp] Re: [SIDN/ietf-wg-rpp-charter] addressing issue #26
(mapping RPP and EPP as deliverable) (PR #40)
Nope, who are the volunteers? It sounds like we have two thus far with me
and Pawel (“kind of”, which I take as a “yes”). -- JG James Gould Fellow
Engineer jgould@ Verisign. com 703-948-3271 12061 Bluemont Way Reston, VA
20190 Verisign. com From:
ZjQcmQRYFpfptBannerStart
*This Message Is From an External Sender *
This message came from outside your organization.
ZjQcmQRYFpfptBannerEnd
Nope, who are the volunteers? It sounds like we have two thus far with me
and Pawel (“kind of”, which I take as a “yes”).
--
JG
[image: ***@***.***
*James Gould *Fellow Engineer
***@***.***
703-948-3271
12061 Bluemont Way
Reston, VA 20190
Verisign.com
<https://secure-web.cisco.com/1NkINdsoI0K9-fQz4EaOqiVWwn-COLYC4D7V4ng3ptlmpGIbI-qnxzLaXUvN8u6uscEDeiHHze5nNugzFB6jcR1meImNMYLtQMlefvz12sbMi185ASWy3Ozvk6mkT4vQqMTzv2voYPKWrCjlWcVqIAXMyZeEBAtPkWwedgVL2MLz26PPyNJxF1dSpD76GoI_QQiAf1FOQnM56up3bAWxac47RcqKjW2NW-l9vexXeDutLxhABYFdAYl1P6fDsrvuFeaP4ObraVHhOWOU3zXuuQjv5cp7LcC3MUkgmjrIJFpM/https%3A%2F%2Furldefense.com%2Fv3%2F__http%3A%2Fverisigninc.com%2F__%3B%21%21Hj18uoVe_Lnx%21qezaWBMKflaHLRuh8tcwI3itKgXMzPYbdF_eDCgpXVXisGv-jTVUoD6cOxNG9fqdom83MeQuhZcFhiYvXXSnFJvojASHy609%24>
*From: *Andrew Newton ***@***.***>
*Reply-To: *SIDN/ietf-wg-rpp-charter <
***@***.***>
*Date: *Friday, November 22, 2024 at 10:07 AM
*To: *SIDN/ietf-wg-rpp-charter ***@***.***>
*Cc: *rpp-ietf ***@***.***>, Comment ***@***.***>
*Subject: *[EXTERNAL] [rpp] Re: [SIDN/ietf-wg-rpp-charter] addressing
issue #26 (mapping RPP and EPP as deliverable) (PR #40)
*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.
There is nothing stopping anybody from starting that work now. :)
—
Reply to this email directly, view it on GitHub
<https://secure-web.cisco.com/1dw8k-UH_XvJHqWtgnvDC554z9NAJut-S18I2incRn0SjWq_J4rzyTYmcxr30yFHehigHMXSs5aMKVZonskcFQ7H6YJ40L4JbbpdM9HkTTIq9p-IRsgohWEVAsZeWtQ-ONQDTg7woXfS3ALlXJAMt29MSRsK6PGr-FfhYuo1-9vtTfno2OmMBx4jCpNsBZEw0jLj3NzOKSEJA5AvGheu-n4WXgNlm9jCN-TSANMeDx1c63qlktrodm_jSVanhgM7wNvZi39qOmjp7cvf3TNmjJz-unQMf_9uk-bciJ1iIeaU/https%3A%2F%2Furldefense.com%2Fv3%2F__https%3A%2Fsecure-web.cisco.com%2F1CADewsi1b41V40qnW__MVHSjgN8OI0a-QYLhlwpynAqRJjnmGODn4d9AaWFpHuSKPU_RnHiOQt_jVc8UCL_3bvOXMPtpi3m4H3JhSQA7_lNOD478ZBRZMASWY9MbaYb2G1rULX6wygG1QFkvmiuKWNJ9xuhdhcHAQnrbih4gXtCsMdnTP-9R2L2nezirQXzpe-CDo6XvqLg4IKZMCUMdnt1KihPSsNxiX-9BjNybqbjosYSVWk7JuSWJ8qsXgH7ffOoKvWtw2CZMAFxEwTpfjLtA3f0SkyQqCDKeQXQXCTg%2Fhttps%2A3A%2A2F%2A2Fgithub.com%2A2FSIDN%2A2Fietf-wg-rpp-charter%2A2Fpull%2A2F40%2A23issuecomment-2493969790__%3BJSUlJSUlJSU%21%21Hj18uoVe_Lnx%21qezaWBMKflaHLRuh8tcwI3itKgXMzPYbdF_eDCgpXVXisGv-jTVUoD6cOxNG9fqdom83MeQuhZcFhiYvXXSnFJvojCJKMPXG%24>,
or unsubscribe
<https://secure-web.cisco.com/1KDIKWcOy1NDiAlGp7huq9NhgDYb7H7elqXpX6dO4E3mf4KQzDbXbzgzuY9qXwsfI0x0OY_cknyYQifVzCF8pd9GsUu9kntS7yHJJarr24sQrPZdb03bHHJgJS96vyPMo36LjhqHMvcDwGgGpSnbhU9qS6tBgh19vo9vZKnan0oL40EIBQ14i6g7ePuAqBz_BHaR16DZL7lNc01oOKvda7yVGhFxyUrqSJwiKFD06tNrM-GUtlwtRh48cDL0CowgUjnTynbrll_dMsu4p_XAwL-k9QD2r2wZT2lLMlMhBkOY/https%3A%2F%2Furldefense.com%2Fv3%2F__https%3A%2Fsecure-web.cisco.com%2F1E91U-hhFhbfu7XqqauynyTJNWiJZnBjDyWk2hggFvD_RDXWbxLagUQuc45HVZmQOeJwoghoDMx3Aol0Fgpnu32oXGM1t5KFA7kt0nUXnvuw4a4qrn4jzCRIYMfcH8g__W6GJFhyG6dKA4H7zq2XsSWI3f1it9VgaCWcGkQOlBSirdRFoYvvIMbxZngk0cTkuiU9fNYQ95h3AxPImjVdYxxF8egUvShpD0IxbyfjuCEVpb13MwtVDWXmp8c7rL5ZSKSUSQSNM3v_LI79r0gJ1DlKx5YvZ-wcVSVNiKgE01GE%2Fhttps%2A3A%2A2F%2A2Fgithub.com%2A2Fnotifications%2A2Funsubscribe-auth%2A2FBM5CYNOXTEWWATZ63DO5HV32B5CBRAVCNFSM6AAAAABSFQQ3O6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOJTHE3DSNZZGA__%3BJSUlJSUl%21%21Hj18uoVe_Lnx%21qezaWBMKflaHLRuh8tcwI3itKgXMzPYbdF_eDCgpXVXisGv-jTVUoD6cOxNG9fqdom83MeQuhZcFhiYvXXSnFJvojI0kttWD%24>
.
You are receiving this because you commented.[image: Image removed by
sender.]Message ID: <
***@***.***>
_______________________________________________
rpp mailing list -- ***@***.***
To unsubscribe send an email to ***@***.***
--
ORIE STEELE
Chief Technology Officer
www.transmute.industries
<https://transmute.industries>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR is add mapping documents to the deliverables section. See Issue #26