[lisp] Martin Duke's Block on charter-ietf-lisp-04-06: (with BLOCK and COMMENT)

Martin Duke via Datatracker <noreply@ietf.org> Tue, 02 January 2024 19:50 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: lisp@ietf.org
Delivered-To: lisp@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 1BC11C151701; Tue, 2 Jan 2024 11:50:28 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Martin Duke via Datatracker <noreply@ietf.org>
To: The IESG <iesg@ietf.org>
Cc: lisp-chairs@ietf.org, lisp@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 12.1.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Martin Duke <martin.h.duke@gmail.com>
Message-ID: <170422502810.34367.16820980013126393868@ietfa.amsl.com>
Date: Tue, 02 Jan 2024 11:50:28 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/lisp/rgPNxvPZWjM4dCKA3HExLlfDluk>
Subject: [lisp] Martin Duke's Block on charter-ietf-lisp-04-06: (with BLOCK and COMMENT)
X-BeenThere: lisp@ietf.org
X-Mailman-Version: 2.1.39
List-Id: List for the discussion of the Locator/ID Separation Protocol <lisp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/lisp>, <mailto:lisp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/lisp/>
List-Post: <mailto:lisp@ietf.org>
List-Help: <mailto:lisp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lisp>, <mailto:lisp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Jan 2024 19:50:28 -0000

Martin Duke has entered the following ballot position for
charter-ietf-lisp-04-06: Block

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.)



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



----------------------------------------------------------------------
BLOCK:
----------------------------------------------------------------------

Is the NAT traversal work going to prioritize existing solutions (e.g. STUN,
TURN, ICE), or have all those already been determined to be inadequate? If the
latter, LISP should coordinate with TSVWG on its NAT traversal solution.


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

Is the reliable transport protocol required to be secure? (e.g., are you
looking at TCP/TLS, QUIC, and SCTP/DTLS, or just bare TCP/SCTP)