Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clarify non-HTTPS example #124

Open
bemasc opened this issue Mar 10, 2020 · 0 comments
Open

Clarify non-HTTPS example #124

bemasc opened this issue Mar 10, 2020 · 0 comments

Comments

@bemasc
Copy link
Collaborator

@bemasc bemasc commented Mar 10, 2020

This example currently fuses two different zone files. We can make it clearer that they are separate by adding a comment line above each RR.

"""
 As an example:

   _8443._foo.api.example.com. 7200 IN SVCB 0 svc4.example.net.
   svc4..example.net.  7200  IN SVCB 3 ( svc4.example.net. alpn="bar"
                                      port="8004" esniconfig="..." )
"""

While many examples are useful for the understanding, they often provide the
impression RRsets are in the same zone file. I am wondering if that would not
be clarifying to show and mention zone files are different. Note this is just a
feed back and your ar efree to ignore it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant
You can’t perform that action at this time.