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

Is Caps optional to be supported by nodes? #1

Closed
nyrahul opened this issue Aug 25, 2019 · 1 comment
Closed

Is Caps optional to be supported by nodes? #1

nyrahul opened this issue Aug 25, 2019 · 1 comment
Labels
needs draft-update Requires draft to specify the behavior explicitly in the context.

Comments

@nyrahul
Copy link
Collaborator

nyrahul commented Aug 25, 2019

  1. Is it needed that all the nodes support caps for it to work?
    a. can it be optional for 6LNs? ... seems it can be optional for 6LNs
    b. can it optional for 6LRs? ... This is tricky and needs to consider both NS-MOP and storing MOP.

In NS-MOP since the DAO directly goes to the root, the intermediate 6LRs are not responsible for handling it and can be made optional. But how will this work with storing MOP where every 6LR, in turn, generates the DAO on behalf of its downstream (sub)child.

Michael's mail in the context

@mcr

@nyrahul nyrahul added the needs draft-update Requires draft to specify the behavior explicitly in the context. label Aug 25, 2019
@nyrahul
Copy link
Collaborator Author

nyrahul commented Nov 21, 2019

We have added a bit which says the capabilities could be ignored or whether a node needs to mandatorily handle it based on 'J' flag in the cap option.

The draft is updated for this.

@nyrahul nyrahul closed this as completed May 16, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs draft-update Requires draft to specify the behavior explicitly in the context.
Projects
None yet
Development

No branches or pull requests

1 participant