Skip to content

Conversation

@chrysn
Copy link
Member

@chrysn chrysn commented Feb 24, 2025

Closes: #17

This may need a bit of iteration (esp. w/rt the normative update text), but it's a starting point.

@cabo
Copy link
Member

cabo commented Feb 24, 2025

I like this initiative a lot, and the text looks good.
But is this something that can be done without an RFC, i.e., is corr-clar the right venue?
I'm almost thinking that we should have added this to groupcomm-bis, which we just pushed to the IESG.

@chrysn
Copy link
Member Author

chrysn commented Feb 24, 2025 via email

@chrysn chrysn force-pushed the bert-for-nonreliable branch from a3b1483 to 99ad389 Compare June 18, 2025 14:46
@chrysn
Copy link
Member Author

chrysn commented Jun 18, 2025

I've added a commit that contains pointers discussed in today's interim, namely, how the relevant reassembly size for OSCORE could be communicated.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

BERT for non-TCP/WS applications

2 participants