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.

Sign up for GitHub

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

Jump to bottom

clarify what it means to merge YANG #41

Open
mcr opened this issue Aug 27, 2023 · 1 comment · May be fixed by #61
Open

clarify what it means to merge YANG #41

mcr opened this issue Aug 27, 2023 · 1 comment · May be fixed by #61

Comments

@mcr
Copy link
Member

mcr commented Aug 27, 2023 

> 15) Line 427ff: As per comment #2, please state more clearly what you
> mean with "merge", as well as what happens to the other documents.  Are
> you expecting that what you "merge" here will "replace" stuff elsewhere
> - will [BRSKI] be updated to remove the voucher-request here; hat are
> the extensions from [cBRSKI], [CLOUD] and [PRM] and will those be
> updated; if the other documents are not updated, how are they expected
> to coexist?
@mcr
Copy link
Member Author

mcr commented Sep 10, 2024

already clarified in #61

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

change abstract and instroduction to explain merging better anima-wg/voucher
1 participant
@mcr