@@ -162,12 +162,11 @@ Such an informal relationship simply exists by defacto when members of both orga
162162cross-collaborate and participate in the groups with overlapping
163163interest.
164164
165- Note that formal communications in the form of liaison statements, if needed,
166- can be used without establishing a formal liaison relationship.
167- In this case, since a formal liaison manager
168- does not exist, the IAB itself will be responsible for ensuring
169- liaison statements are handled appropriately, as further explained in
170- {{?I-D.kuehlewind-iab-rfc4053bis}}.
165+ There is no set process or form for establishing a formal liaison relationship;
166+ the IETF participants and the peer organization can initiate a conversation with
167+ the IAB, and after discussion may come to an agreement to form the relationship.
168+ In some cases, the intended scope and guidelines for the collaboration are documented
169+ specifically (e.g., see {{?RFC3113}}, {{?RFC3131}}, and {{?RFC3356}}).
171170
172171From the IETF's perspective a formal relationship is needed only when required for specific
173172purposes, such as :
@@ -187,12 +186,6 @@ b) The peer organization of the IETF may require a more formal communication str
187186 - Ability to participate and contribute directly in the peer organization's groups and forums.
188187 - Ability to participate in and contribute to the ongoing work of the peer organization.
189188
190- There is no set process or form for establishing a formal liaison relationship;
191- the IETF participants and the peer organization can initiate a conversation with
192- the IAB, and after discussion may come to an agreement to form the relationship.
193- In some cases, the intended scope and guidelines for the collaboration are documented
194- specifically (e.g., see {{?RFC3113}}, {{?RFC3131}}, and {{?RFC3356}}).
195-
196189In setting up a formal liaison relationship, the IAB expects that there will be a
197190mutual exchange of views and discussion of the best approach for
198191undertaking new standardization work items. Any work items resulting
@@ -204,8 +197,7 @@ There is an expectation that both organizations will use the relationship
204197appropriately, allowing sufficient time for the requests they make on
205198the other organization to be processed.
206199
207-
208- # Liaison Communications {#communication}
200+ # # Liaison Communications {#communication}
209201
210202Communications between organizations use a variety of formal and informal
211203channels irrespective of established liaison relationships. The stated
@@ -220,6 +212,13 @@ procedures of many organizations use a form known as a "liaison statement" (LS).
220212Procedures for sending, managing, and responding to liaison statements are
221213discussed in {{?I-D.iab-rfc4053bis}}.
222214
215+ Formal communications in the form of liaison statements, if needed,
216+ can be used without establishing a formal liaison relationship.
217+ In this case, since a formal liaison manager
218+ does not exist, the IAB itself will be responsible for ensuring
219+ liaison statements are handled appropriately, as also further explained in
220+ {{?I-D.iab-rfc4053bis}}.
221+
223222Note that communications between organizations have no impact on
224223any other IETF contributions, and should follow the same IETF process and
225224policies and should be open to everyone for inputs and contributions, e.g.,
0 commit comments