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

fix: remove a form/tool specific sentence. #29

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

fix: remove a form/tool specific sentence. #29

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
4 changes: 1 addition & 3 deletions draft-kuehlewind-iab-rfc4053bis.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -203,9 +203,7 @@ liaison statements. There are no requirements from the IETF on the format
of the actual liaison statement, however, we require
the metadata (address information and purpose) as indicated in the previous
section to be recorded explicitly. As such when receiving statement from other organisation
these metadata should be extracted. If the content of the
statement is not sent in plain text, the plain text body field may
be empty and the received laision statement is uploaded as an attachment.
these metadata should be extracted.

For statements sent from the IETF, it is recommended to provide the content
in plain text but also provide an attachment following the formatting requirements
Expand Down