[lisp] Zaheduzzaman Sarker's No Objection on draft-ietf-lisp-name-encoding-12: (with COMMENT)

Zaheduzzaman Sarker via Datatracker <noreply@ietf.org> Thu, 08 August 2024 10:40 UTC

MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Zaheduzzaman Sarker via Datatracker <noreply@ietf.org>
To: The IESG <iesg@ietf.org>
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <172311361714.88609.9512381024767145331@dt-datatracker-6df4c9dcf5-t2x2k>
Date: Thu, 08 Aug 2024 03:40:17 -0700
Message-ID-Hash: XYW5ESAJNVX4CJPQ4F6X4OZWQINGEA3L
CC: draft-ietf-lisp-name-encoding@ietf.org, lisp-chairs@ietf.org, lisp@ietf.org
Reply-To: Zaheduzzaman Sarker <zahed.sarker.ietf@gmail.com>
Subject: [lisp] Zaheduzzaman Sarker's No Objection on draft-ietf-lisp-name-encoding-12: (with COMMENT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/lisp/7jF4U-aJG9wnpXSwXYtDSvQwUFU>

Zaheduzzaman Sarker has entered the following ballot position for
draft-ietf-lisp-name-encoding-12: 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/about/groups/iesg/statements/handling-ballot-positions/ 
for more information about how to handle DISCUSS and COMMENT positions.


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



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

Thanks for working on this specification. I will support Paul's discuss on
security considerations. I would like to understand why there is no security
considerations, is this already considered somewhere else ?

[lisp] Zaheduzzaman Sarker's No Objection on draf… Zaheduzzaman Sarker via Datatracker