Dear Russ, Section 3.2.4 has been updated to reflect the mandatory implementation of Key Type 0 for interoperability testing. In addition, the “Security Consideration” section now refers to the fallback procedure that follows an unsuccessful negotiation of the Key Type and also recommends not enabling Key Type 0 if security requirements do not allow it. See https://github.com/tsvwg/ietf-multipath-dccp/pull/379. In the meantime, Option Type 46 has been provisionally assigned by the IANA, as can now be seen at https://www.iana.org/assignments/dccp-parameters/dccp-parameters.xhtml#dccp-parameters-5. The Nits are addressed in https://github.com/tsvwg/ietf-multipath-dccp/pull/378. Br Markus > -----Ursprüngliche Nachricht----- > Von: Russ Housley via Datatracker <noreply@xxxxxxxx> > Gesendet: Montag, 27. Januar 2025 21:17 > An: art@xxxxxxxx > Cc: draft-ietf-tsvwg-multipath-dccp.all@xxxxxxxx; last-call@xxxxxxxx; > tsvwg@xxxxxxxx > Betreff: Artart telechat review of draft-ietf-tsvwg-multipath-dccp-20 > > Reviewer: Russ Housley > Review result: Almost Ready > > I am the assigned ART-ART reviewer for this draft. Please treat these > comments just like any other last call comments. > > > Document: draft-ietf-tsvwg-multipath-dccp-20 > Reviewer: Russ Housley > Review Date: 2025-01-27 > IETF LC End Date: 2024-10-17 > IESG Telechat date: 2025-04-03 > > Summary: Almost Ready > > Thank you for addressing my previous comments. > > > Major Concerns: > > Section 3.2.4: Since none of the Key Types is mandatory-to-implement, it > is possible that two implementations of this specification will not > interoperate. I realize that the Key Type have very different security > implications. Also, mandatory-to-implement does not make that Key Type > mandatory-to-use. Policy has a role too. > > Section 8: The IANA registry indicates that Feature Number 10 was given > a temporary assignment. I expected to see a similar temporary assignment > for Option Type 46. This document seems to depend on that value being > assigned by IANA. > > > Minor Concerns: > > None. > > > Nits: > > Section 3.11.2: Please add white space between the adjacent paragraphs. > > Section 8: s/Sect. Section 3.1 specifies/Section 3.1 specifies/ > > -- last-call mailing list -- last-call@xxxxxxxx To unsubscribe send an email to last-call-leave@xxxxxxxx
