[secdir] draft-ietf-rift-kv-tie-structure-and-processing-05 ietf last call Secdir review

Linda Dunbar via Datatracker <noreply@ietf.org> Tue, 11 November 2025 00:59 UTC

MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Linda Dunbar via Datatracker <noreply@ietf.org>
To: secdir@ietf.org
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <176282276721.2054673.8477110870353064546@dt-datatracker-5df8666cb-7l4w5>
Date: Mon, 10 Nov 2025 16:59:27 -0800
Message-ID-Hash: OLASTN5T5677UREPGSMPVBENDHMP7VGH
CC: draft-ietf-rift-kv-tie-structure-and-processing.all@ietf.org, last-call@ietf.org, rift@ietf.org
Reply-To: Linda Dunbar <linda.dunbar@futurewei.com>
Subject: [secdir] draft-ietf-rift-kv-tie-structure-and-processing-05 ietf last call Secdir review
Archived-At: <https://mailarchive.ietf.org/arch/msg/secdir/5Cmd18bBSVkXBZLn-XWMJpS76iU>

Document: draft-ietf-rift-kv-tie-structure-and-processing
Title: RIFT Key/Value TIE Structure and Processing
Reviewer: Linda Dunbar
Review result: Has Nits

Overall, the draft is safe but would benefit from a slightly expanded Security
Considerations section covering input validation, flooding risks, and
confidentiality hygiene. For example, the malicious or malformed KV-TIEs could
cause unnecessary churn or resource exhaustion. Implementations SHOULD validate
KV content, discard malformed entries, and log such events.

NITS:
 “permenent” -> “permanent”

 “publically” -> “publicly”

Warm Regards,
Linda Dunbar

[secdir] draft-ietf-rift-kv-tie-structure-and-pro… Linda Dunbar via Datatracker
[secdir] Re: draft-ietf-rift-kv-tie-structure-and… Christian Kuhtz
[secdir] Re: draft-ietf-rift-kv-tie-structure-and… Linda Dunbar
[secdir] Re: [Rift] draft-ietf-rift-kv-tie-struct… Head, Jordan