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