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

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

Merged
merged 1 commit into from
Feb 19, 2025
Merged

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

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions draft-krishnan-iab-rfc4052bis.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -168,6 +168,11 @@ organizations use a form known as a "liaison statement". Procedures
for sending, managing, and responding to liaison statements are
discussed in {{?RFC4053}}.

Note that communications between organizations have no difference to
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this needs to talk about this only from the IETF side because we do not know if this true from the other organizations' side

any other IETF contributions and should follow the same IETF process and
polices and should be open to everyone for inputs and contributions, e.g.,
input discussion in specific working group in the IETF.

# Summary of IETF Liaison Manager Responsibilities

While the requirements will certainly vary depending on the nature of
Expand Down