Repository navigation
docs: clarify first-hop parent_hop and draft-03 citations - #45
Draft
asiridalugoda wants to merge 1 commit into
Draft
asiridalugoda wants to merge 1 commit into
asiridalugoda wants to merge 1 commit into
Conversation
Explain that parent_hop 0 is the root authorization, and correct the verifyToken step count and hop_signature section reference to match draft-03. Co-authored-by: Siri <asiridalugoda@users.noreply.github.com>
This branch has not been deployed
This file contains hidden or 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
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.
Documentation-only. Callers can see that the first hop uses
parent_hop: 0for the root authorization, and two comments now cite the draft-03 sections that actually define those rules. Validation behaviour is unchanged.docs/streaming-sessions.mdnote thatparent_hop: 0means the root (human) authorization. Draft-03 Section 3.4 definesparent_hop0 as that root authorization, and Section 4.3 Rule 3 requires it to reference 0 or theseqof a prior hop.extendChainstill rejects a missing or out-of-rangeparent_hopon the same checks. The chain-integrity message now says that 0 denotes the root authorization (Section 3.4 and Section 4.3 Rule 3).verifyTokendocuments five ordered integrity steps. Draft-03 Section 5 requires those five steps, in order, after Section 3 input validation.hop_signaturecomment cites Section 4.3 Rule 6, which requires the field on every hop. Draft-03 has no Section 6.3; Section 6 is Superseding Records.Test plan
npm test(26 files, 139 tests passed)