Skip to main content

The Messaging Layer Security (MLS) Protocol
draft-ietf-mls-protocol-16

Revision differences

Document history

Date Rev. By Action
2022-12-01
16 Jean Mahoney Request closed, assignment withdrawn: Suhas Nandakumar Early GENART review
2022-12-01
16 Jean Mahoney Closed request for Early review by GENART with state 'Team Will not Review Version'
2022-09-29
16 Bo Wu Request for Early review by OPSDIR Completed: Has Nits. Reviewer: Bo Wu. Sent review to list.
2022-09-28
16 Sheng Jiang Assignment of request for Early review by INTDIR to Sheng Jiang was rejected
2022-09-28
16 Rich Salz Request for Early review by ARTART Completed: Ready with Nits. Reviewer: Rich Salz. Sent review to list.
2022-09-27
16 Carlos Bernardos Request for Early review by INTDIR is assigned to Sheng Jiang
2022-09-27
16 Carlos Bernardos Request for Early review by INTDIR is assigned to Sheng Jiang
2022-09-23
16 Tero Kivinen Request for Early review by SECDIR is assigned to Magnus Nystrom
2022-09-23
16 Tero Kivinen Request for Early review by SECDIR is assigned to Magnus Nystrom
2022-09-23
16 Gorry Fairhurst Request for Early review by TSVART Completed: On the Right Track. Reviewer: Gorry Fairhurst. Sent review to list.
2022-09-22
16 Magnus Westerlund Request for Early review by TSVART is assigned to Gorry Fairhurst
2022-09-22
16 Magnus Westerlund Request for Early review by TSVART is assigned to Gorry Fairhurst
2022-09-22
16 Barry Leiba Request for Early review by ARTART is assigned to Rich Salz
2022-09-22
16 Barry Leiba Request for Early review by ARTART is assigned to Rich Salz
2022-09-21
16 Jean Mahoney Request for Early review by GENART is assigned to Suhas Nandakumar
2022-09-21
16 Jean Mahoney Request for Early review by GENART is assigned to Suhas Nandakumar
2022-09-21
16 Gunter Van de Velde Request for Early review by OPSDIR is assigned to Bo Wu
2022-09-21
16 Gunter Van de Velde Request for Early review by OPSDIR is assigned to Bo Wu
2022-09-21
16 Paul Wouters Requested Early review by ARTART
2022-09-21
16 Paul Wouters Requested Early review by TSVART
2022-09-21
16 Paul Wouters Requested Early review by OPSDIR
2022-09-21
16 Paul Wouters Requested Early review by INTDIR
2022-09-21
16 Paul Wouters Requested Early review by GENART
2022-09-21
16 Paul Wouters Requested Early review by SECDIR
2022-09-08
16 Sean Turner
# Document Shepherd Write-Up for Group Documents

## Document History

1. Does the working group (WG) consensus represent the strong concurrence of a
  few …
# Document Shepherd Write-Up for Group Documents

## Document History

1. Does the working group (WG) consensus represent the strong concurrence of a
  few individuals, with others being silent, or did it reach broad agreement?

The WG consensus was broad. MLS is not the biggest WG, but there were enough
WG that were active participants during its development that agreed the I-D
was ready to proceed down the road to satisfy both chairs; many of the
participants are implementers. Additionally, some of WG participants are also
part of the security research community and they agreed that the protocol
was provably secure. Without this research, the chairs would not progress this
I-D.

2. Was there controversy about particular points, or were there decisions where
  the consensus was particularly rough?

Surprisingly, no. There was lots of back and forth as well as some frustration,
but generally speaking this development of this I-D was what I hope happens
for most I-Ds.

3. Has anyone threatened an appeal or otherwise indicated extreme discontent? If
  so, please summarize the areas of conflict in separate email messages to the
  responsible Area Director. (It should be in a separate email because this
  questionnaire is publicly available.)

No.

4. For protocol documents, are there existing implementations of the contents of
  the document? Have a significant number of potential implementers indicated
  plans to implement? Are any existing implementations reported somewhere,
  either in the document itself (as [RFC 7942][3] recommends) or elsewhere
  (where)?

We have a github implementation repo that can be found at:
https://github.com/mlswg/mls-implementations

But, a more accurate list of implementations is:

- MLSpp = open source, deployed in production
- OpenMLS = open source
- Wickr's implementation = closed source
- RingCentral's implementation = closed source, deployed in production
- Element's Typescript implementation = open source, only prototype-grade

## Additional Reviews

5. Do the contents of this document closely interact with technologies in other
  IETF working groups or external organizations, and would it therefore benefit
  from their review? Have those reviews occurred? If yes, describe which
  reviews took place.

MLS was intentionally written to be independent of the application layer. See
draft-ietf-mls-architecture for more information.

6. Describe how the document meets any required formal expert review criteria,
  such as the MIB Doctor, YANG Doctor, media type, and URI type reviews.

MLS uses the TLS presentation language. There is no formal expert review
criteria for the TLS presentation language.

There is a Media Type defined. IANA performed an early review and noted that
a few this needed to be addressed; a PR was created:
https://github.com/mlswg/mls-protocol/pull/730/files
The revised registration was shared with the media-types@ietf.org mailing
list.

7. If the document contains a YANG module, has the final version of the module
  been checked with any of the [recommended validation tools][4] for syntax and
  formatting validation? If there are any resulting errors or warnings, what is
  the justification for not fixing them at this time? Does the YANG module
  comply with the Network Management Datastore Architecture (NMDA) as specified
  in [RFC 8342][5]?

N/A

8. Describe reviews and automated checks performed to validate sections of the
  final version of the document written in a formal language, such as XML code,
  BNF rules, MIB definitions, CBOR's CDDL, etc.

N/A

## Document Shepherd Checks

9. Based on the shepherd's review of the document, is it their opinion that this
  document is needed, clearly written, complete, correctly designed, and ready
  to be handed off to the responsible Area Director?

Yes.

10. Several IETF Areas have assembled [lists of common issues that their
    reviewers encounter][6]. For which areas have such issues been identified
    and addressed? For which does this still need to happen in subsequent
    reviews?

After reviewing the list, it is not clear that most of the common issues apply
to this particular I-D. Remember, that there is also a companion archiecture
draft: draft-ietf-mls-architecture.

11. What type of RFC publication is being requested on the IETF stream ([Best
    Current Practice][12], [Proposed Standard, Internet Standard][13],
    [Informational, Experimental or Historic][14])? Why is this the proper type
    of RFC? Do all Datatracker state attributes correctly reflect this intent?

PS is the intended status. PS is the proper status for this on-the-wire
protocol. Yes, the datatracker state attributes correctly reflect PS.

12. Have reasonable efforts been made to remind all authors of the intellectual
    property rights (IPR) disclosure obligations described in [BCP 79][8]? To
    the best of your knowledge, have all required disclosures been filed? If
    not, explain why. If yes, summarize any relevant discussion, including links
    to publicly-available messages when applicable.

Yes, I have personally verified with the authors that they have met the IPR
disclosure obligations in [BCP79].

****
  NOTE: A 3rd party IPR disclosure was filed. Based on advice from Ben Kaduk,
  who was our AD at the time, I sent the following email during WGLC to
  determine how the WG wanted to handle the disclosure:
  https://mailarchive.ietf.org/arch/msg/mls/BB9WsfNDgLp_dEQ60Uw3S75qBmA/
  As you can see in the thread, the WG was comfortable progressing the I-D.
****

13. Has each author, editor, and contributor shown their willingness to be
    listed as such? If the total number of authors and editors on the front page
    is greater than five, please provide a justification.

I have personally verified that all authors are willing to be listed as such.

There are 6 authors listed and for a working group this size that might seem like
a lot, but each of the listed authors provided thrust at one point or another
to move this document along and I would be disinclined to remove one of them.

14. Document any remaining I-D nits in this document. Simply running the [idnits
    tool][8] is not enough; please review the ["Content Guidelines" on
    authors.ietf.org][15]. (Also note that the current idnits tool generates
    some incorrect warnings; a rewrite is underway.)

Lots of nits about lines too long. These seem to relate to the figures; SVG FTW.

Complaints about non-ascii text. These relate to authors' names.

There are two warnings related to references:

Outdated reference: draft-ietf-mls-architecture will likely always be out of
synch or the reference to this I-D in draft-ietf-mls-architecture to this I-D
will be out of synch.

Obsolete informational reference: RFC 7540 - this draft references HTTP/2 so
7540 is the correct reference. Also, review the text and you will note leaving
this alone is fine, i.e., the I-D does not need to update the reference to HTTP/3.

15. Should any informative references be normative or vice-versa? See the [IESG
    Statement on Normative and Informative References][16].

I think the references are fine. Richard wanted me to note that during WGLC
we did move one normative reference to informative.

16. List any normative references that are not freely available to anyone. Did
    the community have sufficient access to review any such normative
    references?

All normative references are to RFCs.

17. Are there any normative downward references (see [RFC 3967][9] and [BCP
    97
][10]) that are not already listed in the [DOWNREF registry][17]? If so,
    list them.

No.

18. Are there normative references to documents that are not ready to be
    submitted to the IESG for publication or are otherwise in an unclear state?
    If so, what is the plan for their completion?

No.

19. Will publication of this document change the status of any existing RFCs? If
    so, does the Datatracker metadata correctly reflect this and are those RFCs
    listed on the title page, in the abstract, and discussed in the
    introduction? If not, explain why and point to the part of the document
    where the relationship of this document to these other RFCs is discussed.

No.

20. Describe the document shepherd's review of the IANA considerations section,
    especially with regard to its consistency with the body of the document.
    Confirm that all aspects of the document requiring IANA assignments are
    associated with the appropriate reservations in IANA registries. Confirm
    that any referenced IANA registries have been clearly identified. Confirm
    that each newly created IANA registry specifies its initial contents,
    allocations procedures, and a reasonable name (see [RFC 8126][11]).

The Shepherd reviewed the assignment for consistency with the body of the I-D.

The Shepherd confirmed the following:
- All aspects of the document requiring IANA assignments are
  associated with the appropriate reservations in IANA registries.
- Any referenced IANA registries have been clearly identified.
- Each newly created IANA registry specifies its initial contents,
  allocations procedures, and a reasonable name (see [RFC 8126][11]).

NOTE: Submitted an issue to expand the definition of the Recommended column
to include a "D" for discouraged; the consensus for RFC 8447bis at saag was
to add this new value to the registry.

21. List any new IANA registries that require Designated Expert Review for
    future allocations. Are the instructions to the Designated Expert clear?
    Please include suggestions of designated experts, if appropriate.

There are four registry created by this I-D and all require DEs. Section
17.5 includes text for the DEs. Note that this text is based on the DE
text in RFC 8447.

[1]: https://www.ietf.org/about/groups/iesg/
[2]: https://www.rfc-editor.org/rfc/rfc4858.html
[3]: https://www.rfc-editor.org/rfc/rfc7942.html
[4]: https://trac.ietf.org/trac/ops/wiki/yang-review-tools
[5]: https://www.rfc-editor.org/rfc/rfc8342.html
[6]: https://trac.ietf.org/trac/iesg/wiki/ExpertTopics
[7]: https://www.rfc-editor.org/info/bcp79
[8]: https://www.ietf.org/tools/idnits/
[9]: https://www.rfc-editor.org/rfc/rfc3967.html
[10]: https://www.rfc-editor.org/info/bcp97
[11]: https://www.rfc-editor.org/rfc/rfc8126.html
[12]: https://www.rfc-editor.org/rfc/rfc2026.html#section-5
[13]: https://www.rfc-editor.org/rfc/rfc2026.html#section-4.1
[14]: https://www.rfc-editor.org/rfc/rfc2026.html#section-4.2
[15]: https://authors.ietf.org/en/content-guidelines-overview
[16]: https://www.ietf.org/about/groups/iesg/statements/normative-informative-references/
[17]: https://datatracker.ietf.org/doc/downref/

2022-09-08
16 Sean Turner Responsible AD changed to Paul Wouters
2022-09-08
16 Sean Turner IETF WG state changed to Submitted to IESG for Publication from WG Consensus: Waiting for Write-Up
2022-09-08
16 Sean Turner IESG state changed to Publication Requested from I-D Exists
2022-09-08
16 Sean Turner IESG process started in state Publication Requested
2022-08-26
16 Sean Turner
# Document Shepherd Write-Up for Group Documents

## Document History

1. Does the working group (WG) consensus represent the strong concurrence of a
  few …
# Document Shepherd Write-Up for Group Documents

## Document History

1. Does the working group (WG) consensus represent the strong concurrence of a
  few individuals, with others being silent, or did it reach broad agreement?

The WG consensus was broad. MLS is not the biggest WG, but there were enough
WG that were active participants during its development that agreed the I-D
was ready to proceed down the road to satisfy both chairs; many of the
participants are implementers. Additionally, some of WG participants are also
part of the security research community and they agreed that the protocol
was provably secure. Without this research, the chairs would not progress this
I-D.

2. Was there controversy about particular points, or were there decisions where
  the consensus was particularly rough?

Surprisingly, no. There was lots of back and forth as well as some frustration,
but generally speaking this development of this I-D was what I hope happens
for most I-Ds.

3. Has anyone threatened an appeal or otherwise indicated extreme discontent? If
  so, please summarize the areas of conflict in separate email messages to the
  responsible Area Director. (It should be in a separate email because this
  questionnaire is publicly available.)

No.

4. For protocol documents, are there existing implementations of the contents of
  the document? Have a significant number of potential implementers indicated
  plans to implement? Are any existing implementations reported somewhere,
  either in the document itself (as [RFC 7942][3] recommends) or elsewhere
  (where)?

We have a github implementation repo that can be found at:
https://github.com/mlswg/mls-implementations

But, a more accurate list of implementations is:

- MLSpp = open source, deployed in production
- OpenMLS = open source
- Wickr's implementation = closed source
- RingCentral's implementation = closed source, deployed in production
- Element's Typescript implementation = open source, only prototype-grade

## Additional Reviews

5. Do the contents of this document closely interact with technologies in other
  IETF working groups or external organizations, and would it therefore benefit
  from their review? Have those reviews occurred? If yes, describe which
  reviews took place.

MLS was intentionally written to be independent of the application layer. See
draft-ietf-mls-architecture for more information.

6. Describe how the document meets any required formal expert review criteria,
  such as the MIB Doctor, YANG Doctor, media type, and URI type reviews.

MLS uses the TLS presentation language. There is no formal expert review
criteria for the TLS presentation language.

There is a Media Type defined. IANA performed an early review and noted that
a few this needed to be addressed; a PR was created:
https://github.com/mlswg/mls-protocol/pull/730/files
The revised registration was shared with the media-types@ietf.org mailing
list.

7. If the document contains a YANG module, has the final version of the module
  been checked with any of the [recommended validation tools][4] for syntax and
  formatting validation? If there are any resulting errors or warnings, what is
  the justification for not fixing them at this time? Does the YANG module
  comply with the Network Management Datastore Architecture (NMDA) as specified
  in [RFC 8342][5]?

N/A

8. Describe reviews and automated checks performed to validate sections of the
  final version of the document written in a formal language, such as XML code,
  BNF rules, MIB definitions, CBOR's CDDL, etc.

N/A

## Document Shepherd Checks

9. Based on the shepherd's review of the document, is it their opinion that this
  document is needed, clearly written, complete, correctly designed, and ready
  to be handed off to the responsible Area Director?

Yes.

10. Several IETF Areas have assembled [lists of common issues that their
    reviewers encounter][6]. For which areas have such issues been identified
    and addressed? For which does this still need to happen in subsequent
    reviews?

After reviewing the list, it is not clear that most of the common issues apply
to this particular I-D. Remember, that there is also a companion archiecture
draft: draft-ietf-mls-architecture.

11. What type of RFC publication is being requested on the IETF stream ([Best
    Current Practice][12], [Proposed Standard, Internet Standard][13],
    [Informational, Experimental or Historic][14])? Why is this the proper type
    of RFC? Do all Datatracker state attributes correctly reflect this intent?

PS is the intended status. PS is the proper status for this on-the-wire
protocol. Yes, the datatracker state attributes correctly reflect PS.

12. Have reasonable efforts been made to remind all authors of the intellectual
    property rights (IPR) disclosure obligations described in [BCP 79][8]? To
    the best of your knowledge, have all required disclosures been filed? If
    not, explain why. If yes, summarize any relevant discussion, including links
    to publicly-available messages when applicable.

Yes, I have personally verified with the authors that they have met the IPR
disclosure obligations in [BCP79].

****
  NOTE: A 3rd party IPR disclosure was filed. Based on advice from Ben Kaduk,
  who was our AD at the time, I sent the following email during WGLC to
  determine how the WG wanted to handle the disclosure:
  https://mailarchive.ietf.org/arch/msg/mls/BB9WsfNDgLp_dEQ60Uw3S75qBmA/
  As you can see in the thread, the WG was comfortable progressing the I-D.
****

13. Has each author, editor, and contributor shown their willingness to be
    listed as such? If the total number of authors and editors on the front page
    is greater than five, please provide a justification.

I have personally verified that all authors are willing to be listed as such.

There are 6 authors listed and for a working group this size that might seem like
a lot, but each of the listed authors provided thrust at one point or another
to move this document along and I would be disinclined to remove one of them.

14. Document any remaining I-D nits in this document. Simply running the [idnits
    tool][8] is not enough; please review the ["Content Guidelines" on
    authors.ietf.org][15]. (Also note that the current idnits tool generates
    some incorrect warnings; a rewrite is underway.)

Lots of nits about lines too long. These seem to relate to the figures; SVG FTW.

Complaints about non-ascii text. These relate to authors' names.

There are two warnings related to references:

Outdated reference: draft-ietf-mls-architecture will likely always be out of
synch or the reference to this I-D in draft-ietf-mls-architecture to this I-D
will be out of synch.

Obsolete informational reference: RFC 7540 - this draft references HTTP/2 so
7540 is the correct reference. Also, review the text and you will note leaving
this alone is fine, i.e., the I-D does not need to update the reference to HTTP/3.

15. Should any informative references be normative or vice-versa? See the [IESG
    Statement on Normative and Informative References][16].

I think the references are fine. Richard wanted me to note that during WGLC
we did move one normative reference to informative.

16. List any normative references that are not freely available to anyone. Did
    the community have sufficient access to review any such normative
    references?

All normative references are to RFCs.

17. Are there any normative downward references (see [RFC 3967][9] and [BCP
    97
][10]) that are not already listed in the [DOWNREF registry][17]? If so,
    list them.

No.

18. Are there normative references to documents that are not ready to be
    submitted to the IESG for publication or are otherwise in an unclear state?
    If so, what is the plan for their completion?

No.

19. Will publication of this document change the status of any existing RFCs? If
    so, does the Datatracker metadata correctly reflect this and are those RFCs
    listed on the title page, in the abstract, and discussed in the
    introduction? If not, explain why and point to the part of the document
    where the relationship of this document to these other RFCs is discussed.

No.

20. Describe the document shepherd's review of the IANA considerations section,
    especially with regard to its consistency with the body of the document.
    Confirm that all aspects of the document requiring IANA assignments are
    associated with the appropriate reservations in IANA registries. Confirm
    that any referenced IANA registries have been clearly identified. Confirm
    that each newly created IANA registry specifies its initial contents,
    allocations procedures, and a reasonable name (see [RFC 8126][11]).

The Shepherd reviewed the assignment for consistency with the body of the I-D.

The Shepherd confirmed the following:
- All aspects of the document requiring IANA assignments are
  associated with the appropriate reservations in IANA registries.
- Any referenced IANA registries have been clearly identified.
- Each newly created IANA registry specifies its initial contents,
  allocations procedures, and a reasonable name (see [RFC 8126][11]).

NOTE: Submitted an issue to expand the definition of the Recommended column
to include a "D" for discouraged; the consensus for RFC 8447bis at saag was
to add this new value to the registry.

21. List any new IANA registries that require Designated Expert Review for
    future allocations. Are the instructions to the Designated Expert clear?
    Please include suggestions of designated experts, if appropriate.

There are four registry created by this I-D and all require DEs. Section
17.5 includes text for the DEs. Note that this text is based on the DE
text in RFC 8447.

[1]: https://www.ietf.org/about/groups/iesg/
[2]: https://www.rfc-editor.org/rfc/rfc4858.html
[3]: https://www.rfc-editor.org/rfc/rfc7942.html
[4]: https://trac.ietf.org/trac/ops/wiki/yang-review-tools
[5]: https://www.rfc-editor.org/rfc/rfc8342.html
[6]: https://trac.ietf.org/trac/iesg/wiki/ExpertTopics
[7]: https://www.rfc-editor.org/info/bcp79
[8]: https://www.ietf.org/tools/idnits/
[9]: https://www.rfc-editor.org/rfc/rfc3967.html
[10]: https://www.rfc-editor.org/info/bcp97
[11]: https://www.rfc-editor.org/rfc/rfc8126.html
[12]: https://www.rfc-editor.org/rfc/rfc2026.html#section-5
[13]: https://www.rfc-editor.org/rfc/rfc2026.html#section-4.1
[14]: https://www.rfc-editor.org/rfc/rfc2026.html#section-4.2
[15]: https://authors.ietf.org/en/content-guidelines-overview
[16]: https://www.ietf.org/about/groups/iesg/statements/normative-informative-references/
[17]: https://datatracker.ietf.org/doc/downref/

2022-08-26
16 Sean Turner
# Document Shepherd Write-Up for Group Documents

## Document History

1. Does the working group (WG) consensus represent the strong concurrence of a
  few …
# Document Shepherd Write-Up for Group Documents

## Document History

1. Does the working group (WG) consensus represent the strong concurrence of a
  few individuals, with others being silent, or did it reach broad agreement?

The WG consensus was broad. MLS is not the biggest WG, but there were enough
WG that were active participants during its development that agreed the I-D
was ready to proceed down the road to satisfy both chairs; many of the
participants are implementers. Additionally, some of WG participants are also
part of the security research community and they agreed that the protocol
was provably secure. Without this research, the chairs would not progress this
I-D.

2. Was there controversy about particular points, or were there decisions where
  the consensus was particularly rough?

Surprisingly, no. There was lots of back and forth as well as some frustration,
but generally speaking this development of this I-D was what I hope happens
for most I-Ds.

3. Has anyone threatened an appeal or otherwise indicated extreme discontent? If
  so, please summarize the areas of conflict in separate email messages to the
  responsible Area Director. (It should be in a separate email because this
  questionnaire is publicly available.)

No.

4. For protocol documents, are there existing implementations of the contents of
  the document? Have a significant number of potential implementers indicated
  plans to implement? Are any existing implementations reported somewhere,
  either in the document itself (as [RFC 7942][3] recommends) or elsewhere
  (where)?

We have a github implementation repo that can be found at:
https://github.com/mlswg/mls-implementations

But, a more accurate list of implementations is:

- MLSpp = open source, deployed in production
- OpenMLS = open source
- Wickr's implementation = closed source
- RingCentral's implementation = closed source, deployed in production
- Element's Typescript implementation = open source, only prototype-grade

## Additional Reviews

5. Do the contents of this document closely interact with technologies in other
  IETF working groups or external organizations, and would it therefore benefit
  from their review? Have those reviews occurred? If yes, describe which
  reviews took place.

MLS was intentionally written to be independent of the application layer. See
draft-ietf-mls-architecture for more information.

6. Describe how the document meets any required formal expert review criteria,
  such as the MIB Doctor, YANG Doctor, media type, and URI type reviews.

MLS uses the TLS presentation language. There is no formal expert review
criteria for the TLS presentation language.

There is a Media Type defined. IANA performed an early review and noted that
a few this needed to be addressed; a PR was created:
https://github.com/mlswg/mls-protocol/pull/730/files
The revised registration was shared with the media-types@ietf.org mailing
list.

7. If the document contains a YANG module, has the final version of the module
  been checked with any of the [recommended validation tools][4] for syntax and
  formatting validation? If there are any resulting errors or warnings, what is
  the justification for not fixing them at this time? Does the YANG module
  comply with the Network Management Datastore Architecture (NMDA) as specified
  in [RFC 8342][5]?

N/A

8. Describe reviews and automated checks performed to validate sections of the
  final version of the document written in a formal language, such as XML code,
  BNF rules, MIB definitions, CBOR's CDDL, etc.

N/A

## Document Shepherd Checks

9. Based on the shepherd's review of the document, is it their opinion that this
  document is needed, clearly written, complete, correctly designed, and ready
  to be handed off to the responsible Area Director?

Yes.

10. Several IETF Areas have assembled [lists of common issues that their
    reviewers encounter][6]. For which areas have such issues been identified
    and addressed? For which does this still need to happen in subsequent
    reviews?

After reviewing the list, it is not clear that most of the common issues apply
to this particular I-D. Remember, that there is also a companion archiecture
draft: draft-ietf-mls-architecture.

11. What type of RFC publication is being requested on the IETF stream ([Best
    Current Practice][12], [Proposed Standard, Internet Standard][13],
    [Informational, Experimental or Historic][14])? Why is this the proper type
    of RFC? Do all Datatracker state attributes correctly reflect this intent?

PS is the intended status. PS is the proper status for this on-the-wire
protocol. Yes, the datatracker state attributes correctly reflect PS.

12. Have reasonable efforts been made to remind all authors of the intellectual
    property rights (IPR) disclosure obligations described in [BCP 79][8]? To
    the best of your knowledge, have all required disclosures been filed? If
    not, explain why. If yes, summarize any relevant discussion, including links
    to publicly-available messages when applicable.

Yes, I have personally verified with the 5 authors that they have met the IPR
disclosure obligations in [BCP79].

****
  NOTE: A 3rd party IPR disclosure was filed. Based on advice from Ben Kaduk,
  who was our AD at the time, I sent the following email during WGLC to
  determine how the WG wanted to handle the disclosure:
  https://mailarchive.ietf.org/arch/msg/mls/BB9WsfNDgLp_dEQ60Uw3S75qBmA/
  As you can see in the thread, the WG was comfortable progressing the I-D.
****

13. Has each author, editor, and contributor shown their willingness to be
    listed as such? If the total number of authors and editors on the front page
    is greater than five, please provide a justification.

I have personally verified that all authors are willing to be listed as such.

There are 6 authors listed and for a working group this size that might seem like
a lot, but each of the listed authors provided thrust at one point or another
to move this document along and I would be disinclined to remove one of them.

14. Document any remaining I-D nits in this document. Simply running the [idnits
    tool][8] is not enough; please review the ["Content Guidelines" on
    authors.ietf.org][15]. (Also note that the current idnits tool generates
    some incorrect warnings; a rewrite is underway.)

Lots of nits about lines too long. These seem to relate to the figures; SVG FTW.

Complaints about non-ascii text. These relate to authors' names.

There are two warnings related to references:

Outdated reference: draft-ietf-mls-architecture will likely always be out of
synch or the reference to this I-D in draft-ietf-mls-architecture to this I-D
will be out of synch.

Obsolete informational reference: RFC 7540 - this draft references HTTP/2 so
7540 is the correct reference. Also, review the text and you will note leaving
this alone is fine, i.e., the I-D does not need to update the reference to HTTP/3.

15. Should any informative references be normative or vice-versa? See the [IESG
    Statement on Normative and Informative References][16].

I think the references are fine. Richard wanted me to note that during WGLC
we did move one normative reference to informative.

16. List any normative references that are not freely available to anyone. Did
    the community have sufficient access to review any such normative
    references?

All normative references are to RFCs.

17. Are there any normative downward references (see [RFC 3967][9] and [BCP
    97
][10]) that are not already listed in the [DOWNREF registry][17]? If so,
    list them.

No.

18. Are there normative references to documents that are not ready to be
    submitted to the IESG for publication or are otherwise in an unclear state?
    If so, what is the plan for their completion?

No.

19. Will publication of this document change the status of any existing RFCs? If
    so, does the Datatracker metadata correctly reflect this and are those RFCs
    listed on the title page, in the abstract, and discussed in the
    introduction? If not, explain why and point to the part of the document
    where the relationship of this document to these other RFCs is discussed.

No.

20. Describe the document shepherd's review of the IANA considerations section,
    especially with regard to its consistency with the body of the document.
    Confirm that all aspects of the document requiring IANA assignments are
    associated with the appropriate reservations in IANA registries. Confirm
    that any referenced IANA registries have been clearly identified. Confirm
    that each newly created IANA registry specifies its initial contents,
    allocations procedures, and a reasonable name (see [RFC 8126][11]).

The Shepherd reviewed the assignment for consistency with the body of the I-D.

The Shepherd confirmed the following:
- All aspects of the document requiring IANA assignments are
  associated with the appropriate reservations in IANA registries.
- Any referenced IANA registries have been clearly identified.
- Each newly created IANA registry specifies its initial contents,
  allocations procedures, and a reasonable name (see [RFC 8126][11]).

NOTE: Submitted an issue to expand the definition of the Recommended column
to include a "D" for discouraged; the consensus for RFC 8447bis at saag was
to add this new value to the registry.

21. List any new IANA registries that require Designated Expert Review for
    future allocations. Are the instructions to the Designated Expert clear?
    Please include suggestions of designated experts, if appropriate.

There are four registry created by this I-D and all require DEs. Section
17.5 includes text for the DEs. Note that this text is based on the DE
text in RFC 8447.

[1]: https://www.ietf.org/about/groups/iesg/
[2]: https://www.rfc-editor.org/rfc/rfc4858.html
[3]: https://www.rfc-editor.org/rfc/rfc7942.html
[4]: https://trac.ietf.org/trac/ops/wiki/yang-review-tools
[5]: https://www.rfc-editor.org/rfc/rfc8342.html
[6]: https://trac.ietf.org/trac/iesg/wiki/ExpertTopics
[7]: https://www.rfc-editor.org/info/bcp79
[8]: https://www.ietf.org/tools/idnits/
[9]: https://www.rfc-editor.org/rfc/rfc3967.html
[10]: https://www.rfc-editor.org/info/bcp97
[11]: https://www.rfc-editor.org/rfc/rfc8126.html
[12]: https://www.rfc-editor.org/rfc/rfc2026.html#section-5
[13]: https://www.rfc-editor.org/rfc/rfc2026.html#section-4.1
[14]: https://www.rfc-editor.org/rfc/rfc2026.html#section-4.2
[15]: https://authors.ietf.org/en/content-guidelines-overview
[16]: https://www.ietf.org/about/groups/iesg/statements/normative-informative-references/
[17]: https://datatracker.ietf.org/doc/downref/

2022-08-25
16 Sean Turner
# Document Shepherd Write-Up for Group Documents

## Document History

1. Does the working group (WG) consensus represent the strong concurrence of a
  few …
# Document Shepherd Write-Up for Group Documents

## Document History

1. Does the working group (WG) consensus represent the strong concurrence of a
  few individuals, with others being silent, or did it reach broad agreement?

The WG reach broad agreement. MLS is not the biggest WG, but there were enough
WG that were active participants during its development that agreed the I-D
was ready to proceed down the road to satisfy both chairs. Additionally, some
of WG participants are also part of the security research community and the
chair did not want to progress this I-D until we heard from enough of them
to make the chairs comfortable that analysis has completed.

2. Was there controversy about particular points, or were there decisions where
  the consensus was particularly rough?

Surprisingly, no. There was lots of back and forth as well as some frustration,
but generally speaking this development of this I-D was what I hope happens
for most I-Ds.

3. Has anyone threatened an appeal or otherwise indicated extreme discontent? If
  so, please summarize the areas of conflict in separate email messages to the
  responsible Area Director. (It should be in a separate email because this
  questionnaire is publicly available.)

No.

4. For protocol documents, are there existing implementations of the contents of
  the document? Have a significant number of potential implementers indicated
  plans to implement? Are any existing implementations reported somewhere,
  either in the document itself (as [RFC 7942][3] recommends) or elsewhere
  (where)?

There are existing implementations; by my count 4 (possibly 5). One of these
is an open source project.

We have a github implementation repo that can be found at:
https://github.com/mlswg/mls-implementations

## Additional Reviews

5. Do the contents of this document closely interact with technologies in other
  IETF working groups or external organizations, and would it therefore benefit
  from their review? Have those reviews occurred? If yes, describe which
  reviews took place.

MLS was intentionally written to be independent of the application layer. See
draft-ietf-mls-architecture for more information.

6. Describe how the document meets any required formal expert review criteria,
  such as the MIB Doctor, YANG Doctor, media type, and URI type reviews.

MLS uses the TLS presentation language. There is no formal expert review
criteria for the TLS presentation language.

There is a Media Type defined. IANA performed an early review and noted that
a few this needed to be addressed; a PR was created:
https://github.com/mlswg/mls-protocol/pull/730/files
The revised registration was shared with the media-types@ietf.org mailing
list.

7. If the document contains a YANG module, has the final version of the module
  been checked with any of the [recommended validation tools][4] for syntax and
  formatting validation? If there are any resulting errors or warnings, what is
  the justification for not fixing them at this time? Does the YANG module
  comply with the Network Management Datastore Architecture (NMDA) as specified
  in [RFC 8342][5]?

N/A

8. Describe reviews and automated checks performed to validate sections of the
  final version of the document written in a formal language, such as XML code,
  BNF rules, MIB definitions, CBOR's CDDL, etc.

N/A

## Document Shepherd Checks

9. Based on the shepherd's review of the document, is it their opinion that this
  document is needed, clearly written, complete, correctly designed, and ready
  to be handed off to the responsible Area Director?

Yes.

10. Several IETF Areas have assembled [lists of common issues that their
    reviewers encounter][6]. For which areas have such issues been identified
    and addressed? For which does this still need to happen in subsequent
    reviews?

After reviewing the list, it is not clear that most of the common issues apply
to this particular I-D. Remember, that there is also a companion archiecture
draft: draft-ietf-mls-architecture.

11. What type of RFC publication is being requested on the IETF stream ([Best
    Current Practice][12], [Proposed Standard, Internet Standard][13],
    [Informational, Experimental or Historic][14])? Why is this the proper type
    of RFC? Do all Datatracker state attributes correctly reflect this intent?

PS is the intended status. PS is the proper status for this on-the-wire
protocol. Yes, the datatracker state attributes correctly reflect PS.

12. Have reasonable efforts been made to remind all authors of the intellectual
    property rights (IPR) disclosure obligations described in [BCP 79][8]? To
    the best of your knowledge, have all required disclosures been filed? If
    not, explain why. If yes, summarize any relevant discussion, including links
    to publicly-available messages when applicable.

Yes, I have personally verified with the 5 authors that they have met the IPR
disclosure obligations in [BCP79].

****
  NOTE: A 3rd party IPR disclosure was filed. Based on advice from Ben Kaduk,
  who was our AD at the time, I sent the following email during WGLC to
  determine how the WG wanted to handle the disclosure:
  https://mailarchive.ietf.org/arch/msg/mls/BB9WsfNDgLp_dEQ60Uw3S75qBmA/
  As you can see in the thread, the WG was comfortable progressing the I-D.
****

13. Has each author, editor, and contributor shown their willingness to be
    listed as such? If the total number of authors and editors on the front page
    is greater than five, please provide a justification.

I have personally verified that all authors are willing to be listed as such.

14. Document any remaining I-D nits in this document. Simply running the [idnits
    tool][8] is not enough; please review the ["Content Guidelines" on
    authors.ietf.org][15]. (Also note that the current idnits tool generates
    some incorrect warnings; a rewrite is underway.)

Lots of nits about lines too long. These seem to relate to the figures; SVG FTW.

Complaints about non-ascii text. These relate to authors' names.

There are two warnings releated to references:

Outdated reference: draft-ietf-mls-architecture will likely always be out of
synch or the reference to this I-D in draft-ietf-mls-architecture to this I-D
will be out of synch.

Obsolete informational reference: RFC 7540 - this draft references HTTP/2 so
7540 is the correct reference. Also, review the text and you will note leaving
this alone is fine, i.e., the I-D does not need to update the reference to HTTP/3.

15. Should any informative references be normative or vice-versa? See the [IESG
    Statement on Normative and Informative References][16].

I think the references are fine.

16. List any normative references that are not freely available to anyone. Did
    the community have sufficient access to review any such normative
    references?

All normative references are to RFCs.

17. Are there any normative downward references (see [RFC 3967][9] and [BCP
    97
][10]) that are not already listed in the [DOWNREF registry][17]? If so,
    list them.

No.

18. Are there normative references to documents that are not ready to be
    submitted to the IESG for publication or are otherwise in an unclear state?
    If so, what is the plan for their completion?

No.

19. Will publication of this document change the status of any existing RFCs? If
    so, does the Datatracker metadata correctly reflect this and are those RFCs
    listed on the title page, in the abstract, and discussed in the
    introduction? If not, explain why and point to the part of the document
    where the relationship of this document to these other RFCs is discussed.

No.

20. Describe the document shepherd's review of the IANA considerations section,
    especially with regard to its consistency with the body of the document.
    Confirm that all aspects of the document requiring IANA assignments are
    associated with the appropriate reservations in IANA registries. Confirm
    that any referenced IANA registries have been clearly identified. Confirm
    that each newly created IANA registry specifies its initial contents,
    allocations procedures, and a reasonable name (see [RFC 8126][11]).

The Shepherd reviewed the assignment for consistency with the body of the I-D.

The Shepherd confirmed the following:
- All aspects of the document requiring IANA assignments are
  associated with the appropriate reservations in IANA registries.
- Any referenced IANA registries have been clearly identified.
- Each newly created IANA registry specifies its initial contents,
  allocations procedures, and a reasonable name (see [RFC 8126][11]).

NOTE: Submitted an issue to expand the definition of the Recommended column
to include a "D" for discouraged; the consensus for RFC 8447bis at saag was
to add this new value to the registry.

21. List any new IANA registries that require Designated Expert Review for
    future allocations. Are the instructions to the Designated Expert clear?
    Please include suggestions of designated experts, if appropriate.

There are four registry created by this I-D and all require DEs. Section
17.5 includes text for the DEs. Note that this text is based on the DE
text in RFC 8447.

[1]: https://www.ietf.org/about/groups/iesg/
[2]: https://www.rfc-editor.org/rfc/rfc4858.html
[3]: https://www.rfc-editor.org/rfc/rfc7942.html
[4]: https://trac.ietf.org/trac/ops/wiki/yang-review-tools
[5]: https://www.rfc-editor.org/rfc/rfc8342.html
[6]: https://trac.ietf.org/trac/iesg/wiki/ExpertTopics
[7]: https://www.rfc-editor.org/info/bcp79
[8]: https://www.ietf.org/tools/idnits/
[9]: https://www.rfc-editor.org/rfc/rfc3967.html
[10]: https://www.rfc-editor.org/info/bcp97
[11]: https://www.rfc-editor.org/rfc/rfc8126.html
[12]: https://www.rfc-editor.org/rfc/rfc2026.html#section-5
[13]: https://www.rfc-editor.org/rfc/rfc2026.html#section-4.1
[14]: https://www.rfc-editor.org/rfc/rfc2026.html#section-4.2
[15]: https://authors.ietf.org/en/content-guidelines-overview
[16]: https://www.ietf.org/about/groups/iesg/statements/normative-informative-references/
[17]: https://datatracker.ietf.org/doc/downref/

2022-08-25
16 Sean Turner
# Document Shepherd Write-Up for Group Documents

## Document History

1. Does the working group (WG) consensus represent the strong concurrence of a
  few …
# Document Shepherd Write-Up for Group Documents

## Document History

1. Does the working group (WG) consensus represent the strong concurrence of a
  few individuals, with others being silent, or did it reach broad agreement?

The WG reach broad agreement. MLS is not the biggest WG, but there were enough
WG that were active participants during its development that agreed the I-D
was ready to proceed down the road to satisfy both chairs. Additionally, some
of WG participants are also part of the security research community and the
chair did not want to progress this I-D until we heard from enough of them
to make the chairs comfortable that analysis has completed.

2. Was there controversy about particular points, or were there decisions where
  the consensus was particularly rough?

Surprisingly, no. There was lots of back and forth as well as some frustration,
but generally speaking this development of this I-D was what I hope happens
for most I-Ds.

3. Has anyone threatened an appeal or otherwise indicated extreme discontent? If
  so, please summarize the areas of conflict in separate email messages to the
  responsible Area Director. (It should be in a separate email because this
  questionnaire is publicly available.)

No.

4. For protocol documents, are there existing implementations of the contents of
  the document? Have a significant number of potential implementers indicated
  plans to implement? Are any existing implementations reported somewhere,
  either in the document itself (as [RFC 7942][3] recommends) or elsewhere
  (where)?

There are existing implementations; by my count 4 (possibly 5). One of these
is an open source project.

We have a github implementation repo that can be found at:
https://github.com/mlswg/mls-implementations

## Additional Reviews

5. Do the contents of this document closely interact with technologies in other
  IETF working groups or external organizations, and would it therefore benefit
  from their review? Have those reviews occurred? If yes, describe which
  reviews took place.

MLS was intentionally written to be independent of the application layer. See
draft-ietf-mls-architecture for more information.

6. Describe how the document meets any required formal expert review criteria,
  such as the MIB Doctor, YANG Doctor, media type, and URI type reviews.

MLS uses the TLS presentation language. There is no formal expert review
criteria for the TLS presentation language.

7. If the document contains a YANG module, has the final version of the module
  been checked with any of the [recommended validation tools][4] for syntax and
  formatting validation? If there are any resulting errors or warnings, what is
  the justification for not fixing them at this time? Does the YANG module
  comply with the Network Management Datastore Architecture (NMDA) as specified
  in [RFC 8342][5]?

N/A

8. Describe reviews and automated checks performed to validate sections of the
  final version of the document written in a formal language, such as XML code,
  BNF rules, MIB definitions, CBOR's CDDL, etc.

N/A

## Document Shepherd Checks

9. Based on the shepherd's review of the document, is it their opinion that this
  document is needed, clearly written, complete, correctly designed, and ready
  to be handed off to the responsible Area Director?

Yes.

10. Several IETF Areas have assembled [lists of common issues that their
    reviewers encounter][6]. For which areas have such issues been identified
    and addressed? For which does this still need to happen in subsequent
    reviews?

After reviewing the list, it is not clear that most of the common issues apply
to this particular I-D. Remember, that there is also a companion archiecture
draft: draft-ietf-mls-architecture.

11. What type of RFC publication is being requested on the IETF stream ([Best
    Current Practice][12], [Proposed Standard, Internet Standard][13],
    [Informational, Experimental or Historic][14])? Why is this the proper type
    of RFC? Do all Datatracker state attributes correctly reflect this intent?

This I-D intended for PS. PS is the proper status for this on-the-wire protocol.
Yes the datatracker state attributes correctly reflect this intent.

12. Have reasonable efforts been made to remind all authors of the intellectual
    property rights (IPR) disclosure obligations described in [BCP 79][8]? To
    the best of your knowledge, have all required disclosures been filed? If
    not, explain why. If yes, summarize any relevant discussion, including links
    to publicly-available messages when applicable.

Yes, I have personally verified with the 5 authors that they have followed the
IPR disclosure obligations in [BCP79].

****
  NOTE: A 3rd party IPR disclosure was filed. Based on advice from Ben Kaduk,
  who was our AD at the time, I sent the following email during WGLC to
  determine how the WG wanted to handle the disclosure:
  https://mailarchive.ietf.org/arch/msg/mls/BB9WsfNDgLp_dEQ60Uw3S75qBmA/
  As you can see in the thread the WG was comfortable progressing the I-D.
****

13. Has each author, editor, and contributor shown their willingness to be
    listed as such? If the total number of authors and editors on the front page
    is greater than five, please provide a justification.

Yes, I have personally verified that all authors are willing to be listed as such.

14. Document any remaining I-D nits in this document. Simply running the [idnits
    tool][8] is not enough; please review the ["Content Guidelines" on
    authors.ietf.org][15]. (Also note that the current idnits tool generates
    some incorrect warnings; a rewrite is underway.)

Lots of nits about lines too long. These seem to relate to the figures; SVG FTW.

Complaints about non-ascii text. These relate to authors' names.

There are two warnings releated to references:

Outdated reference: draft-ietf-mls-architecture will likely always be out of
synch or the reference to this I-D in draft-ietf-mls-architecture to this I-D
will be out of synch.

Obsolete informational reference: RFC 7540 - this draft references HTTP/2 so
7540 is the correct reference. Also, review the text and you will note leaving
this alone is fine, i.e., the I-D does not need to update the reference to HTTP/3.

15. Should any informative references be normative or vice-versa? See the [IESG
    Statement on Normative and Informative References][16].

I think the references are fine.

16. List any normative references that are not freely available to anyone. Did
    the community have sufficient access to review any such normative
    references?

All normative references are to RFCs.

17. Are there any normative downward references (see [RFC 3967][9] and [BCP
    97
][10]) that are not already listed in the [DOWNREF registry][17]? If so,
    list them.

No.

18. Are there normative references to documents that are not ready to be
    submitted to the IESG for publication or are otherwise in an unclear state?
    If so, what is the plan for their completion?

No.

19. Will publication of this document change the status of any existing RFCs? If
    so, does the Datatracker metadata correctly reflect this and are those RFCs
    listed on the title page, in the abstract, and discussed in the
    introduction? If not, explain why and point to the part of the document
    where the relationship of this document to these other RFCs is discussed.

No.

20. Describe the document shepherd's review of the IANA considerations section,
    especially with regard to its consistency with the body of the document.
    Confirm that all aspects of the document requiring IANA assignments are
    associated with the appropriate reservations in IANA registries. Confirm
    that any referenced IANA registries have been clearly identified. Confirm
    that each newly created IANA registry specifies its initial contents,
    allocations procedures, and a reasonable name (see [RFC 8126][11]).

To be completed.

21. List any new IANA registries that require Designated Expert Review for
    future allocations. Are the instructions to the Designated Expert clear?
    Please include suggestions of designated experts, if appropriate.

There are four registry created by this I-D and all require DEs. Section
17.5 includes text for the DEs. Note that this text is based on the DE
text in RFC 8447.

[1]: https://www.ietf.org/about/groups/iesg/
[2]: https://www.rfc-editor.org/rfc/rfc4858.html
[3]: https://www.rfc-editor.org/rfc/rfc7942.html
[4]: https://trac.ietf.org/trac/ops/wiki/yang-review-tools
[5]: https://www.rfc-editor.org/rfc/rfc8342.html
[6]: https://trac.ietf.org/trac/iesg/wiki/ExpertTopics
[7]: https://www.rfc-editor.org/info/bcp79
[8]: https://www.ietf.org/tools/idnits/
[9]: https://www.rfc-editor.org/rfc/rfc3967.html
[10]: https://www.rfc-editor.org/info/bcp97
[11]: https://www.rfc-editor.org/rfc/rfc8126.html
[12]: https://www.rfc-editor.org/rfc/rfc2026.html#section-5
[13]: https://www.rfc-editor.org/rfc/rfc2026.html#section-4.1
[14]: https://www.rfc-editor.org/rfc/rfc2026.html#section-4.2
[15]: https://authors.ietf.org/en/content-guidelines-overview
[16]: https://www.ietf.org/about/groups/iesg/statements/normative-informative-references/
[17]: https://datatracker.ietf.org/doc/downref/

2022-08-25
16 Sean Turner
# Document Shepherd Write-Up for Group Documents

## Document History

1. Does the working group (WG) consensus represent the strong concurrence of a
  few …
# Document Shepherd Write-Up for Group Documents

## Document History

1. Does the working group (WG) consensus represent the strong concurrence of a
  few individuals, with others being silent, or did it reach broad agreement?

The WG reach broad agreement. MLS is not the biggest WG, but there were enough
WG that were active participants during its development that agreed the I-D
was ready to proceed down the road to satisfy both chairs. Additionally, some
of WG participants are also part of the security research community and the
chair did not want to progress this I-D until we heard from enough of them
to make the chairs comfortable that analysis has completed.

2. Was there controversy about particular points, or were there decisions where
  the consensus was particularly rough?

Surprisingly, no. There was lots of back and forth as well as some frustration,
but generally speaking this development of this I-D was what I hope happens
for most I-Ds.

3. Has anyone threatened an appeal or otherwise indicated extreme discontent? If
  so, please summarize the areas of conflict in separate email messages to the
  responsible Area Director. (It should be in a separate email because this
  questionnaire is publicly available.)

No.

4. For protocol documents, are there existing implementations of the contents of
  the document? Have a significant number of potential implementers indicated
  plans to implement? Are any existing implementations reported somewhere,
  either in the document itself (as [RFC 7942][3] recommends) or elsewhere
  (where)?

There are existing implementations; by my count 4 (possibly 5). One of these
is an open source project.

We have a github implementation repo that can be found at:
https://github.com/mlswg/mls-implementations

## Additional Reviews

5. Do the contents of this document closely interact with technologies in other
  IETF working groups or external organizations, and would it therefore benefit
  from their review? Have those reviews occurred? If yes, describe which
  reviews took place.

MLS was intentionally written to be independent of the application layer. See
draft-ietf-mls-architecture for more information.

6. Describe how the document meets any required formal expert review criteria,
  such as the MIB Doctor, YANG Doctor, media type, and URI type reviews.

MLS uses the TLS presentation language. There is no formal expert review
criteria for the TLS presentation language.

7. If the document contains a YANG module, has the final version of the module
  been checked with any of the [recommended validation tools][4] for syntax and
  formatting validation? If there are any resulting errors or warnings, what is
  the justification for not fixing them at this time? Does the YANG module
  comply with the Network Management Datastore Architecture (NMDA) as specified
  in [RFC 8342][5]?

N/A

8. Describe reviews and automated checks performed to validate sections of the
  final version of the document written in a formal language, such as XML code,
  BNF rules, MIB definitions, CBOR's CDDL, etc.

N/A

## Document Shepherd Checks

9. Based on the shepherd's review of the document, is it their opinion that this
  document is needed, clearly written, complete, correctly designed, and ready
  to be handed off to the responsible Area Director?

Yes.

10. Several IETF Areas have assembled [lists of common issues that their
    reviewers encounter][6]. For which areas have such issues been identified
    and addressed? For which does this still need to happen in subsequent
    reviews?

After reviewing the list, it is not clear that most of the common issues apply
to this particular I-D. Remember, that there is also a companion archiecture
draft: draft-ietf-mls-architecture.

11. What type of RFC publication is being requested on the IETF stream ([Best
    Current Practice][12], [Proposed Standard, Internet Standard][13],
    [Informational, Experimental or Historic][14])? Why is this the proper type
    of RFC? Do all Datatracker state attributes correctly reflect this intent?

This I-D intended for PS. PS is the proper status for this on-the-wire protocol.
Yes the datatracker state attributes correctly reflect this intent.

12. Have reasonable efforts been made to remind all authors of the intellectual
    property rights (IPR) disclosure obligations described in [BCP 79][8]? To
    the best of your knowledge, have all required disclosures been filed? If
    not, explain why. If yes, summarize any relevant discussion, including links
    to publicly-available messages when applicable.

Yes, I have personally verify that the 5 authors

13. Has each author, editor, and contributor shown their willingness to be
    listed as such? If the total number of authors and editors on the front page
    is greater than five, please provide a justification.

Yes, I have personally verified that all authors are willing to be listed as such.

14. Document any remaining I-D nits in this document. Simply running the [idnits
    tool][8] is not enough; please review the ["Content Guidelines" on
    authors.ietf.org][15]. (Also note that the current idnits tool generates
    some incorrect warnings; a rewrite is underway.)

Lots of nits about lines too long. These seem to relate to the figures; SVG FTW.

Complaints about non-ascii text. These relate to authors' names.

There are two warnings releated to references:

Outdated reference: draft-ietf-mls-architecture will likely always be out of
synch or the reference to this I-D in draft-ietf-mls-architecture to this I-D
will be out of synch.

Obsolete informational reference: RFC 7540 - this draft references HTTP/2 so
7540 is the correct reference. Also, review the text and you will note leaving
this alone is fine, i.e., the I-D does not need to update the reference to HTTP/3.

15. Should any informative references be normative or vice-versa? See the [IESG
    Statement on Normative and Informative References][16].

I think the references are fine.

16. List any normative references that are not freely available to anyone. Did
    the community have sufficient access to review any such normative
    references?

All normative references are to RFCs.

17. Are there any normative downward references (see [RFC 3967][9] and [BCP
    97
][10]) that are not already listed in the [DOWNREF registry][17]? If so,
    list them.

No.

18. Are there normative references to documents that are not ready to be
    submitted to the IESG for publication or are otherwise in an unclear state?
    If so, what is the plan for their completion?

No.

19. Will publication of this document change the status of any existing RFCs? If
    so, does the Datatracker metadata correctly reflect this and are those RFCs
    listed on the title page, in the abstract, and discussed in the
    introduction? If not, explain why and point to the part of the document
    where the relationship of this document to these other RFCs is discussed.

No.

20. Describe the document shepherd's review of the IANA considerations section,
    especially with regard to its consistency with the body of the document.
    Confirm that all aspects of the document requiring IANA assignments are
    associated with the appropriate reservations in IANA registries. Confirm
    that any referenced IANA registries have been clearly identified. Confirm
    that each newly created IANA registry specifies its initial contents,
    allocations procedures, and a reasonable name (see [RFC 8126][11]).

To be completed.

21. List any new IANA registries that require Designated Expert Review for
    future allocations. Are the instructions to the Designated Expert clear?
    Please include suggestions of designated experts, if appropriate.

There are four registry created by this I-D and all require DEs. Section
17.5 includes text for the DEs. Note that this text is based on the DE
text in RFC 8447.

[1]: https://www.ietf.org/about/groups/iesg/
[2]: https://www.rfc-editor.org/rfc/rfc4858.html
[3]: https://www.rfc-editor.org/rfc/rfc7942.html
[4]: https://trac.ietf.org/trac/ops/wiki/yang-review-tools
[5]: https://www.rfc-editor.org/rfc/rfc8342.html
[6]: https://trac.ietf.org/trac/iesg/wiki/ExpertTopics
[7]: https://www.rfc-editor.org/info/bcp79
[8]: https://www.ietf.org/tools/idnits/
[9]: https://www.rfc-editor.org/rfc/rfc3967.html
[10]: https://www.rfc-editor.org/info/bcp97
[11]: https://www.rfc-editor.org/rfc/rfc8126.html
[12]: https://www.rfc-editor.org/rfc/rfc2026.html#section-5
[13]: https://www.rfc-editor.org/rfc/rfc2026.html#section-4.1
[14]: https://www.rfc-editor.org/rfc/rfc2026.html#section-4.2
[15]: https://authors.ietf.org/en/content-guidelines-overview
[16]: https://www.ietf.org/about/groups/iesg/statements/normative-informative-references/
[17]: https://datatracker.ietf.org/doc/downref/

2022-08-25
16 Sean Turner Changed consensus to Yes from Unknown
2022-08-25
16 Sean Turner Intended Status changed to Proposed Standard from None
2022-08-25
16 Sean Turner
2022-08-25
16 Sean Turner Document shepherd changed to Sean Turner
2022-07-18
16 Sean Turner IETF WG state changed to WG Consensus: Waiting for Write-Up from In WG Last Call
2022-07-13
16 Sean Turner Added to session: IETF-114: mls  Fri-1230
2022-07-11
16 Richard Barnes New version available: draft-ietf-mls-protocol-16.txt
2022-07-11
16 (System) New version approved
2022-07-11
16 (System) Request for posting confirmation emailed to previous authors: Benjamin Beurdouche , Emad Omara , Jon Millican , Katriel Cohn-Gordon , Raphael Robert , Richard Barnes
2022-07-11
16 Richard Barnes Uploaded new revision
2022-06-16
15 Sean Turner
This is the 2nd WGLC for this I-D. A number of issues were raised during the WGLC and after. We held 4 virtual interim meetings …
This is the 2nd WGLC for this I-D. A number of issues were raised during the WGLC and after. We held 4 virtual interim meetings to quickly work through these. As of 16 July 2022 @ 1240, we are back again to no issues (and no comments that I am aware of) and no outstanding pull requests.
2022-06-16
15 Sean Turner IETF WG state changed to In WG Last Call from WG Document
2022-06-16
15 Sean Turner Tag Revised I-D Needed - Issue raised by WGLC cleared.
2022-06-16
15 Richard Barnes New version available: draft-ietf-mls-protocol-15.txt
2022-06-16
15 (System) New version approved
2022-06-16
15 (System) Request for posting confirmation emailed to previous authors: Benjamin Beurdouche , Emad Omara , Jon Millican , Katriel Cohn-Gordon , Raphael Robert , Richard Barnes
2022-06-16
15 Richard Barnes Uploaded new revision
2022-06-16
14 Sean Turner IETF WG state changed to WG Document from In WG Last Call
2022-06-16
14 Sean Turner Tag Revised I-D Needed - Issue raised by WGLC set.
2022-05-03
14 Sean Turner IETF WG state changed to In WG Last Call from WG Document
2022-05-03
14 Richard Barnes New version available: draft-ietf-mls-protocol-14.txt
2022-05-03
14 (System) New version approved
2022-05-03
14 (System) Request for posting confirmation emailed to previous authors: Benjamin Beurdouche , Emad Omara , Jon Millican , Katriel Cohn-Gordon , Raphael Robert , Richard Barnes
2022-05-03
14 Richard Barnes Uploaded new revision
2022-03-13
13 Sean Turner Added to session: IETF-113: mls  Wed-1300
2022-03-07
13 Richard Barnes New version available: draft-ietf-mls-protocol-13.txt
2022-03-07
13 (System) New version accepted (logged-in submitter: Richard Barnes)
2022-03-07
13 Richard Barnes Uploaded new revision
2021-10-11
12 Richard Barnes New version available: draft-ietf-mls-protocol-12.txt
2021-10-11
12 (System) New version approved
2021-10-11
12 (System)
Request for posting confirmation emailed to previous authors: Benjamin Beurdouche , Emad Omara , Jon Millican , Katriel Cohn-Gordon , Raphael Robert , Richard Barnes …
Request for posting confirmation emailed to previous authors: Benjamin Beurdouche , Emad Omara , Jon Millican , Katriel Cohn-Gordon , Raphael Robert , Richard Barnes , mls-chairs@ietf.org
2021-10-11
12 Richard Barnes Uploaded new revision
2021-06-25
11 (System) Document has expired
2021-03-07
11 Sean Turner Added to session: IETF-110: mls  Mon-1530
2020-12-22
11 Richard Barnes New version available: draft-ietf-mls-protocol-11.txt
2020-12-22
11 (System) New version accepted (logged-in submitter: Richard Barnes)
2020-12-22
11 Richard Barnes Uploaded new revision
2020-10-31
10 Richard Barnes New version available: draft-ietf-mls-protocol-10.txt
2020-10-31
10 (System) New version approved
2020-10-31
10 (System) Request for posting confirmation emailed to previous authors: Katriel Cohn-Gordon , Richard Barnes , Benjamin Beurdouche , Raphael Robert , Emad Omara , Jon Millican
2020-10-31
10 Richard Barnes Uploaded new revision
2020-09-07
09 (System) Document has expired
2020-07-27
09 Sean Turner Added to session: IETF-108: mls  Tue-1300
2020-03-06
09 Richard Barnes New version available: draft-ietf-mls-protocol-09.txt
2020-03-06
09 (System) New version approved
2020-03-06
09 (System) Request for posting confirmation emailed to previous authors: Richard Barnes , Benjamin Beurdouche , Katriel Cohn-Gordon , Jon Millican , Emad Omara , Raphael Robert
2020-03-06
09 Richard Barnes Uploaded new revision
2020-02-04
Jenny Bui Posted related IPR disclosure: Sean Turner's Statement about IPR related to draft-ietf-mls-protocol belonging to Qrypt Inc
2019-11-17
08 Richard Barnes New version available: draft-ietf-mls-protocol-08.txt
2019-11-17
08 (System) Forced post of submission
2019-11-17
08 (System) Request for posting confirmation emailed to previous authors: Benjamin Beurdouche , Raphael Robert , Emad Omara , Jon Millican , Richard Barnes , Katriel Cohn-Gordon
2019-11-17
08 Richard Barnes Uploaded new revision
2019-10-01
07 Sean Turner Added to session: interim-2019-mls-03
2019-10-01
07 Sean Turner Added to session: interim-2019-mls-03
2019-07-26
07 Sean Turner Added to session: IETF-105: mls  Fri-1000
2019-07-08
07 Richard Barnes New version available: draft-ietf-mls-protocol-07.txt
2019-07-08
07 (System) New version approved
2019-07-08
07 (System) Request for posting confirmation emailed to previous authors: mls-chairs@ietf.org, Raphael Robert , Emad Omara , Jon Millican , Richard Barnes , Katriel Cohn-Gordon
2019-07-08
07 Richard Barnes Uploaded new revision
2019-05-30
06 Richard Barnes New version available: draft-ietf-mls-protocol-06.txt
2019-05-30
06 (System) New version approved
2019-05-30
06 (System) Request for posting confirmation emailed to previous authors: Emad Omara , Raphael Robert , Richard Barnes , Katriel Cohn-Gordon , Jon Millican
2019-05-30
06 Richard Barnes Uploaded new revision
2019-05-02
05 Richard Barnes New version available: draft-ietf-mls-protocol-05.txt
2019-05-02
05 (System) New version approved
2019-05-02
05 (System) Request for posting confirmation emailed to previous authors: Emad Omara , Raphael Robert , Richard Barnes , Katriel Cohn-Gordon , Jon Millican
2019-05-02
05 Richard Barnes Uploaded new revision
2019-03-22
04 Cindy Morgan New version available: draft-ietf-mls-protocol-04.txt
2019-03-22
04 (System) Posted submission manually
2019-01-11
03 Richard Barnes New version available: draft-ietf-mls-protocol-03.txt
2019-01-11
03 (System) New version approved
2019-01-11
03 (System) Request for posting confirmation emailed to previous authors: Emad Omara , Raphael Robert , Richard Barnes , Katriel Cohn-Gordon , Jon Millican
2019-01-11
03 Richard Barnes Uploaded new revision
2018-10-22
02 Richard Barnes New version available: draft-ietf-mls-protocol-02.txt
2018-10-22
02 (System) New version approved
2018-10-22
02 (System) Request for posting confirmation emailed to previous authors: Emad Omara , Raphael Robert , Richard Barnes , Katriel Cohn-Gordon , Jon Millican
2018-10-22
02 Richard Barnes Uploaded new revision
2018-09-19
01 Richard Barnes New version available: draft-ietf-mls-protocol-01.txt
2018-09-19
01 (System) New version approved
2018-09-19
01 (System) Request for posting confirmation emailed to previous authors: Emad Omara , Raphael Robert , Richard Barnes , Katriel Cohn-Gordon , Jon Millican
2018-09-19
01 Richard Barnes Uploaded new revision
2018-09-19
00 Sean Turner
2018-09-19
00 Sean Turner
Notification list changed to Benjamin Beurdouche <benjamin.beurdouche@ens.fr>, Karthikeyan Bhargavan <karthikeyan.bhargavan@inria.fr>, Cas Cremers <cas.cremers@cs.ox.ac.uk>, Alan Duric <alan@wire.com>, Srinivas …
Notification list changed to Benjamin Beurdouche <benjamin.beurdouche@ens.fr>, Karthikeyan Bhargavan <karthikeyan.bhargavan@inria.fr>, Cas Cremers <cas.cremers@cs.ox.ac.uk>, Alan Duric <alan@wire.com>, Srinivas Inguva <singuva@twitter.com>, Albert Kwon <kwonal@mit.edu>
2018-09-19
00 Sean Turner This document now replaces draft-barnes-mls-protocol instead of None
2018-08-15
00 Richard Barnes New version available: draft-ietf-mls-protocol-00.txt
2018-08-15
00 (System) New version approved
2018-08-15
00 Richard Barnes Request for posting confirmation emailed  to submitter and authors: Emad Omara , Raphael Robert , Richard Barnes , Katriel Cohn-Gordon , Jon Millican
2018-08-15
00 Richard Barnes Uploaded new revision