From 756bb1a2d223895eaecd1da5ad825d9d8ef88b05 Mon Sep 17 00:00:00 2001 From: mirjak Date: Sat, 1 Nov 2025 16:03:14 +0100 Subject: [PATCH 1/2] Merge "Speaking for the IETF" in to paragraph further up These two paragraph were both talking about speaking for the IETF or representing the IETF. As we don't have any other subsection anymore anywhere, I removed the subsection heading and merged the text into the existing paragraph a bit further up. --- draft-iab-rfc4052bis.md | 28 ++++++++++++++-------------- 1 file changed, 14 insertions(+), 14 deletions(-) diff --git a/draft-iab-rfc4052bis.md b/draft-iab-rfc4052bis.md index b9465a9..8a99844 100644 --- a/draft-iab-rfc4052bis.md +++ b/draft-iab-rfc4052bis.md @@ -246,12 +246,22 @@ This often includes: material information that is intended to be shared by the peer organization. Formal messages from the IETF to the peer organization are usually carried in liaison -statements. In certain situations, the liaison manager may carry additional messages for -providing further context. However, if these communications aim to "represent the IETF", -they must have consensus, e.g. by being based on an RFC or some other formal statement -by a group within the IETF. For such additional communication, liaison managers +statements. The liaison manager must not send liaison statements on their own initiative to a +liaised organization on behalf of IETF, or any of its areas and +working groups. + +In certain situations, the liaison manager may carry additional messages for +providing further context. For such additional communication, liaison managers may use any applicable businesslike approach, from private to public communications, and bring in other parties as needed. +However, the mandate for IETF liaison managers is strictly limited to +conveying IETF consensus to the liaised organization. +The liaison manager speaks on behalf of the IETF on +the subject matter of the liaison, but only after making sure that +the IETF consensus is understood. Specifically, +if these communications aim to "represent the IETF", +they must have consensus, e.g. by being based on an RFC or some other formal statement +by a group within the IETF. IETF liaison managers should also communicate and coordinate with other liaison managers where concerned technical activities overlap. @@ -261,16 +271,6 @@ if concerns regarding technical overlap or incorrectness are detected. However, given that most organizations are quite large, it is not expected that the liaison manager needs to have a complete overview of everything that is going on there. -## Speaking for the IETF - -The mandate for IETF liaison managers is strictly limited to -conveying IETF consensus to the liaised organization. The liaison -manager must not send liaison statements on their own initiative to a -liaised organization on behalf of IETF, or any of its areas and -working groups. The liaison manager speaks on behalf of the IETF on -the subject matter of the liaison, but only after making sure that -the IETF consensus is understood. - # Security Considerations The security of the Internet is enhanced by robust coordination between SDOs. From f8c57ca9037d62dfdb90610115821d31d94c2169 Mon Sep 17 00:00:00 2001 From: mirjak Date: Sat, 1 Nov 2025 16:38:50 +0100 Subject: [PATCH 2/2] Apply suggestions from code review --- draft-iab-rfc4052bis.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/draft-iab-rfc4052bis.md b/draft-iab-rfc4052bis.md index 8a99844..a31ffaf 100644 --- a/draft-iab-rfc4052bis.md +++ b/draft-iab-rfc4052bis.md @@ -255,13 +255,13 @@ providing further context. For such additional communication, liaison managers may use any applicable businesslike approach, from private to public communications, and bring in other parties as needed. However, the mandate for IETF liaison managers is strictly limited to -conveying IETF consensus to the liaised organization. +conveying IETF consensus to the liaised organization. The liaison manager speaks on behalf of the IETF on the subject matter of the liaison, but only after making sure that the IETF consensus is understood. Specifically, if these communications aim to "represent the IETF", they must have consensus, e.g. by being based on an RFC or some other formal statement -by a group within the IETF. +by a group within the IETF. IETF liaison managers should also communicate and coordinate with other liaison managers where concerned technical activities overlap.