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

Submit `lightning:` as an IANA-recognized URI #534

wbobeirne opened this issue Dec 12, 2018 · 2 comments


Copy link

commented Dec 12, 2018

In order to get better browser adoption, the BOLT-11 lightning:...URIs should be added to the big list: This is important for things such as the allow lightning to be in the permitted URIs for registerProtocolHandler.

I'm not exactly sure how one takes the lead on doing this, or if it's already in the works.


This comment has been minimized.

Copy link

commented Mar 31, 2019

Someone wishing to register a new scheme MUST:

  1. Check the IANA "Uniform Resource Identifier (URI) Schemes"
    registry to see whether there is already an entry for the desired
    name. If there is already an entry under the name, choose a
    different scheme name or update the existing scheme

  2. Prepare a scheme registration request using the template
    specified in Section 7.4. The scheme registration request can be
    contained in an Internet-Draft, submitted alone, or as part of
    some other permanently available, stable, protocol specification.
    The scheme registration request can also be submitted in some
    other form (as part of another document or as a stand-alone
    document), but the scheme registration request will be treated as
    an "IETF Contribution" under the guidelines of [RFC5378].

  3. If the registration request is for a 'permanent' registration
    (or, optionally, for any other registration if desired):

    1. Review the requirements in Section 3.

    2. Send a copy of the scheme registration request or a pointer
      to the document containing the request (with specific
      reference to the section that requests the scheme
      registration) to the mailing list,
      requesting review. In addition, request review on other
      relevant mailing lists as appropriate. For example, general
      discussion of URI syntactical issues can be discussed on; schemes for a network protocol can be discussed
      on a mailing list for that protocol. Allow a reasonable time
      for discussion and comments. Four weeks is reasonable for a
      'permanent' registration request.

    3. Respond to review comments and make revisions to the proposed
      registration as needed to bring it into line with the
      guidelines given in this document.



This comment has been minimized.

Copy link

commented Oct 6, 2019

See also #206

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
3 participants
You can’t perform that action at this time.