Skip to content

Commit

Permalink
smaller edits to align updated text
Browse files Browse the repository at this point in the history
  • Loading branch information
mirjak authored Feb 21, 2025
1 parent b4856b7 commit 6caacd2
Showing 1 changed file with 5 additions and 6 deletions.
11 changes: 5 additions & 6 deletions draft-kuehlewind-iab-rfc4053bis.md
Original file line number Diff line number Diff line change
Expand Up @@ -247,17 +247,16 @@ from other organisations.
more or less important to the receiver depending on its contents and
the expertise of the sender. If the liaison statement seeks to
influence the direction of a WG's development, it should receive the
same consideration that any temporary document receives. The WG
chair may request the sender's contacts to make their case to the
same consideration that any input document receives. The WG
chair may request the sender to make their case to the
IETF WG in the same manner that an author of an internet draft makes
his or her case.

The urgency of a liaison statement is usually reflected in its
deadline. A liaison statement for informational purposes may have no
deadline. A liaison statement for informational purposes has no
deadline; in such a case, a courteous "thank you" liaison statement
is necessary to inform the sender that the liaison statement was
received. The WG may then inform itself of the contents and close
the document. A liaison statement specifying a deadline, however,
may be sent to inform the sender that the liaison statement was
received. A liaison statement specifying a deadline, however,
gives the receiver a finite opportunity to influence the activity of
another body; if it fails to react in a timely fashion, it may miss
the opportunity.
Expand Down

0 comments on commit 6caacd2

Please sign in to comment.