[babel] Erik Kline's No Objection on draft-ietf-babel-dtls-10: (with COMMENT)

Erik Kline via Datatracker <noreply@ietf.org> Mon, 17 August 2020 02:20 UTC

MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Erik Kline via Datatracker <noreply@ietf.org>
To: The IESG <iesg@ietf.org>
Cc: draft-ietf-babel-dtls@ietf.org, babel-chairs@ietf.org, babel@ietf.org, Donald Eastlake <d3e3e3@gmail.com>, d3e3e3@gmail.com
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Erik Kline <ek.ietf@gmail.com>
Message-ID: <159763082952.17304.922256301788860509@ietfa.amsl.com>
Date: Sun, 16 Aug 2020 19:20:29 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/babel/XXCUJ5Kd6868lm435f5sfH0FfYw>
Subject: [babel] Erik Kline's No Objection on draft-ietf-babel-dtls-10: (with COMMENT)

Erik Kline has entered the following ballot position for
draft-ietf-babel-dtls-10: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-babel-dtls/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

[[ comments ]]

[ section 5 ]

* The first sentence of the 3rd paragraphs reads to me like "while DTLS
  provides protection against replay attacks an attacker can still mount
  a replay attack".

  I don't have any constructive proposal to change this, but if it tickles
  something in your mind that might be more clear to those not super
  knowledgeable about DTLS, I'm sure that'll be great.

[babel] Erik Kline's No Objection on draft-ietf-b… Erik Kline via Datatracker