From 9975884fde1f5407fe48d9505f597a9d3077ac58 Mon Sep 17 00:00:00 2001 From: Masaharu Hattori <112887632+Masa8106@users.noreply.github.com> Date: Tue, 23 Jun 2026 22:48:14 +0900 Subject: [PATCH 1/6] Update README.md --- README.md | 1 + 1 file changed, 1 insertion(+) diff --git a/README.md b/README.md index eebbc06..6c649ca 100644 --- a/README.md +++ b/README.md @@ -12,6 +12,7 @@ Sandbox API Repository to describe, develop, document, and test the NumberRecycling API within the [Know Your Customer (KYC)](https://lf-camaraproject.atlassian.net/wiki/x/I4DGB) Sub Project. * API Repository [wiki page](https://lf-camaraproject.atlassian.net/wiki/x/ggCaBQ) +* CAMARA Resoureces [whitepaper "CAMARA APIs: Functional Differences"](https://camaraproject.org/wp-content/uploads/sites/12/2026/06/CAMARA-wp_api_diff_060126a.pdf) ## Scope From 542f23bf805a518b5a503b8033497e665e6bc9cb Mon Sep 17 00:00:00 2001 From: Masaharu Hattori <112887632+Masa8106@users.noreply.github.com> Date: Tue, 23 Jun 2026 22:58:02 +0900 Subject: [PATCH 2/6] Update number-recycling.yaml --- code/API_definitions/number-recycling.yaml | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/code/API_definitions/number-recycling.yaml b/code/API_definitions/number-recycling.yaml index 2b3aa31..18b4205 100644 --- a/code/API_definitions/number-recycling.yaml +++ b/code/API_definitions/number-recycling.yaml @@ -23,6 +23,7 @@ info: Note: * When API receives a request with specified date on which a user signed a contract with MNO, the API respond sets to 'false'(e.g., 2023-10-09 in the Scenario 1 of the figure above). + * This Scenario 1 corresponds to the Line 0601 in Section 4.4 of the CAMARA whitepaper "CAMARA APIs: Functional Differences" (https://camaraproject.org/wp-content/uploads/sites/12/2026/06/CAMARA-wp_api_diff_060126a.pdf). * Scenario 2 * Pre-conditions @@ -40,7 +41,7 @@ info: Number_Recycling_scenario_2 Note: - * When the API receives a request with specified date during which there is no contract with MNO for the phone number, the API respond sets to 'true'(e.g., the period between 2024-02-25 and 2024-09-20 in the Scenario 2 of the figure above). + * This Scenario 2 corresponds to the Line 0607 in Section 4.4 of the CAMARA whitepaper "CAMARA APIs: Functional Differences" (https://camaraproject.org/wp-content/uploads/sites/12/2026/06/CAMARA-wp_api_diff_060126a.pdf). ##How to choose specifiedDate by ASP (API consumer) ASP should choose a date when the ASP established a trusted association between the user and the phone number, for example onboarding, phone number verification, or another validated point in the ASP's own trust process. A previous Number Recycling check that returned `false` may be used as an operational reference date, if this is consistent with the ASP's own trust model. From 5471d6e8b3560df528207bd17dd342e6a1cd1165 Mon Sep 17 00:00:00 2001 From: Masaharu Hattori <112887632+Masa8106@users.noreply.github.com> Date: Thu, 25 Jun 2026 02:30:02 +0900 Subject: [PATCH 3/6] Update README.md MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-authored-by: Pedro Díez García --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 6c649ca..6aca229 100644 --- a/README.md +++ b/README.md @@ -12,7 +12,7 @@ Sandbox API Repository to describe, develop, document, and test the NumberRecycling API within the [Know Your Customer (KYC)](https://lf-camaraproject.atlassian.net/wiki/x/I4DGB) Sub Project. * API Repository [wiki page](https://lf-camaraproject.atlassian.net/wiki/x/ggCaBQ) -* CAMARA Resoureces [whitepaper "CAMARA APIs: Functional Differences"](https://camaraproject.org/wp-content/uploads/sites/12/2026/06/CAMARA-wp_api_diff_060126a.pdf) +* CAMARA Resources [whitepaper "CAMARA APIs: Functional Differences"](https://camaraproject.org/wp-content/uploads/sites/12/2026/06/CAMARA-wp_api_diff_060126a.pdf) ## Scope From 440c09fab6c8e0a353654707533e9ff186890341 Mon Sep 17 00:00:00 2001 From: Masaharu Hattori <112887632+Masa8106@users.noreply.github.com> Date: Thu, 25 Jun 2026 02:32:27 +0900 Subject: [PATCH 4/6] Update code/API_definitions/number-recycling.yaml MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-authored-by: Pedro Díez García --- code/API_definitions/number-recycling.yaml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/code/API_definitions/number-recycling.yaml b/code/API_definitions/number-recycling.yaml index 18b4205..441cf49 100644 --- a/code/API_definitions/number-recycling.yaml +++ b/code/API_definitions/number-recycling.yaml @@ -41,7 +41,7 @@ info: Number_Recycling_scenario_2 Note: - * This Scenario 2 corresponds to the Line 0607 in Section 4.4 of the CAMARA whitepaper "CAMARA APIs: Functional Differences" (https://camaraproject.org/wp-content/uploads/sites/12/2026/06/CAMARA-wp_api_diff_060126a.pdf). + * This Scenario 2 corresponds to the [Line 0607 in Section 4.4 of the CAMARA whitepaper "CAMARA APIs: Functional Differences"](https://camaraproject.org/wp-content/uploads/sites/12/2026/06/CAMARA-wp_api_diff_060126a.pdf). ##How to choose specifiedDate by ASP (API consumer) ASP should choose a date when the ASP established a trusted association between the user and the phone number, for example onboarding, phone number verification, or another validated point in the ASP's own trust process. A previous Number Recycling check that returned `false` may be used as an operational reference date, if this is consistent with the ASP's own trust model. From 5d1eece5fa4c4efe142e3d3738e254ac8c0b87e3 Mon Sep 17 00:00:00 2001 From: Masaharu Hattori <112887632+Masa8106@users.noreply.github.com> Date: Thu, 25 Jun 2026 02:32:49 +0900 Subject: [PATCH 5/6] Update code/API_definitions/number-recycling.yaml MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-authored-by: Pedro Díez García --- code/API_definitions/number-recycling.yaml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/code/API_definitions/number-recycling.yaml b/code/API_definitions/number-recycling.yaml index 441cf49..82f150e 100644 --- a/code/API_definitions/number-recycling.yaml +++ b/code/API_definitions/number-recycling.yaml @@ -23,7 +23,7 @@ info: Note: * When API receives a request with specified date on which a user signed a contract with MNO, the API respond sets to 'false'(e.g., 2023-10-09 in the Scenario 1 of the figure above). - * This Scenario 1 corresponds to the Line 0601 in Section 4.4 of the CAMARA whitepaper "CAMARA APIs: Functional Differences" (https://camaraproject.org/wp-content/uploads/sites/12/2026/06/CAMARA-wp_api_diff_060126a.pdf). + * This Scenario 1 corresponds to the [Line 0601 in Section 4.4 of the CAMARA whitepaper "CAMARA APIs: Functional Differences"](https://camaraproject.org/wp-content/uploads/sites/12/2026/06/CAMARA-wp_api_diff_060126a.pdf). * Scenario 2 * Pre-conditions From 307fd676574b069703a7f2f66debe7c6492f7310 Mon Sep 17 00:00:00 2001 From: Masaharu Hattori <112887632+Masa8106@users.noreply.github.com> Date: Thu, 25 Jun 2026 02:35:20 +0900 Subject: [PATCH 6/6] Update number-recycling.yaml --- code/API_definitions/number-recycling.yaml | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/code/API_definitions/number-recycling.yaml b/code/API_definitions/number-recycling.yaml index 82f150e..fe9e7e7 100644 --- a/code/API_definitions/number-recycling.yaml +++ b/code/API_definitions/number-recycling.yaml @@ -43,7 +43,8 @@ info: Note: * This Scenario 2 corresponds to the [Line 0607 in Section 4.4 of the CAMARA whitepaper "CAMARA APIs: Functional Differences"](https://camaraproject.org/wp-content/uploads/sites/12/2026/06/CAMARA-wp_api_diff_060126a.pdf). - ##How to choose specifiedDate by ASP (API consumer) + ## How to choose specifiedDate by ASP (API consumer) + ASP should choose a date when the ASP established a trusted association between the user and the phone number, for example onboarding, phone number verification, or another validated point in the ASP's own trust process. A previous Number Recycling check that returned `false` may be used as an operational reference date, if this is consistent with the ASP's own trust model. However, a date that is trusted from the ASP perspective is not necessarily processable by every API provider. If `specifiedDate` is outside the API provider's supported/evaluable window and therefore cannot be processed as a valid reference date, the response should be `OUT_OF_RANGE` rather than a boolean result.