Skip to content

Commit 58b3701

Browse files
committed
Fixed typo
1 parent 8d82ea8 commit 58b3701

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

IETF-RFC.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -224,9 +224,9 @@ At the start of the process, the Discovering Server has either an OCM Address, o
224224

225225
Step 1: In case it has an OCM Address, it should first extract `<fqdn>` from it (the part after the `@` sign).
226226
Step 2: The Discovering Server SHOULD attempt OCM API discovery a HTTP GET request to `https://<fqdn>/.well-known/ocm`.
227-
Step 3: If that results in a valid HTTP response with a valid JSON response body within reasonable time, go to step 8.
227+
Step 3: If that results in a valid HTTP response with a valid JSON response body within reasonable time, go to step 7.
228228
Step 4: If not, try a HTTP GET with `https://<fqdn>/ocm-provider` as the URL instead.
229-
Step 5: If that results in a valid HTTP response with a valid JSON response body within reasonable time, go to step 8.
229+
Step 5: If that results in a valid HTTP response with a valid JSON response body within reasonable time, go to step 7.
230230
Step 6: If not, fail.
231231
Step 7: The JSON response body is the data that was discovered.
232232

0 commit comments

Comments
 (0)