From 6caacd218548c2fe7270c51f251523b0217cb24e Mon Sep 17 00:00:00 2001 From: mirjak Date: Fri, 21 Feb 2025 17:12:08 +0100 Subject: [PATCH] smaller edits to align updated text --- draft-kuehlewind-iab-rfc4053bis.md | 11 +++++------ 1 file changed, 5 insertions(+), 6 deletions(-) diff --git a/draft-kuehlewind-iab-rfc4053bis.md b/draft-kuehlewind-iab-rfc4053bis.md index eb35e22..b18a494 100644 --- a/draft-kuehlewind-iab-rfc4053bis.md +++ b/draft-kuehlewind-iab-rfc4053bis.md @@ -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.