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

Explain that liaisons have no special place in the IETF processes #4

Open
sureshkrishnan opened this issue Nov 3, 2024 · 1 comment
Open

Explain that liaisons have no special place in the IETF processes #4

sureshkrishnan opened this issue Nov 3, 2024 · 1 comment
Assignees
@sureshkrishnan
Labels
-01

Comments

@sureshkrishnan
Copy link
Contributor

There needs to be text in the document that everyone is open to participate in the IETF: all the documents are freely available to everyone and any input/output going through the liaisons is really going through the same WG/IETF process as any other participants.
@mirjak mirjak added the -00 label Feb 12, 2025
@billwuqin
Copy link
Contributor

It seems to me there is gray area whether this issue should be addressed in RFC4052bis or RFC4053bis?

@billwuqin billwuqin mentioned this issue Feb 18, 2025
Merged
@sureshkrishnan sureshkrishnan added -01 and removed -00 labels Feb 20, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@sureshkrishnan sureshkrishnan

Labels
-01
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@sureshkrishnan @mirjak @billwuqin