Sitelet https://github.com/transparency-dev/formats/pull/25
Skip to content

Add dns_name recommendations for the Origin - #25

Merged
phbnf merged 5 commits into
transparency-dev:mainfrom
phbnf:dns_name
May 9, 2023
Merged

phbnf merged 5 commits into
transparency-dev:mainfrom
phbnf:dns_name

Conversation

@phbnf

@phbnf phbnf commented Apr 27, 2023 •

Copy link
Copy Markdown
Contributor

See #22 for further context.

@phbnf
phbnf requested a review from a team as a code owner April 27, 2023 12:50
@phbnf
phbnf requested review from jiggoha and mhutchinson April 27, 2023 12:50
@codecov

codecov Bot commented Apr 27, 2023 •

Copy link
Copy Markdown

Codecov Report

Patch and project coverage have no change.

Comparison is base (7a6ef70) 100.00% compared to head (695016b) 100.00%.

Additional details and impacted files
@@            Coverage Diff            @@
##              main       #25   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files            3         3           
  Lines           57        57           
=========================================
  Hits            57        57           

☔ View full report in Codecov by Sentry.
📢 Do you have feedback about the report comment? Let us know in this issue.

@phbnf phbnf changed the title Add dns_name recommendations Add dns_name recommendations for the Origin Apr 27, 2023
Comment thread log/README.md Outdated
The exact format of this is left undefined, but best practice is to have a scheme-less URI-like
prefix that will be globally unique, and give some idea of the log location/operator,
e.g. `example.com/log42`.
The exact format of this is left undefined, but best practice is to use a URI-like strucutre like

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
The exact format of this is left undefined, but best practice is to use a URI-like strucutre like
The exact format of this is left undefined, but best practice is to use a URI-like structure like

Comment thread log/README.md Outdated
Comment thread log/README.md Outdated
phbnf and others added 2 commits April 27, 2023 16:44
Co-authored-by: Martin Hutchinson <mhutchinson@gmail.com>
Comment thread log/README.md Outdated
The exact format of this is left undefined, but best practice is to have a scheme-less URI-like
prefix that will be globally unique, and give some idea of the log location/operator,
e.g. `example.com/log42`.
The exact format of this is left undefined, but best practice is to use a URI-like strucutre like

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could you use https://www.ietf.org/rfc/rfc2119.txt language, like "The format SHOULD be a URI-like structure. Clients MUST NOT assume that the origin is a URI"?

Comment thread log/README.md Outdated
This structure reduces the likelihood of origin collision,
and gives clues to humans about the log operator and what is in the log. The suffix is optional
and can be anything. It is used to disambiguate logs owned under the same prefix.
The format SHOULD be a URI-like strucutre like `<dns_name>[/<suffix>]`, where the log operator

@AlCutter AlCutter May 2, 2023 •

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Were you working on an old commit? The "strucuture" typo and "With a globally unique..." line below came back :)

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oops, thanks!

@phbnf
phbnf merged commit bd46273 into transparency-dev:main May 9, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants