C-439 H.248.50 (ex H.248.NATTT): Updates - draft-ietf-avt-app-rtp-keepalive

Christian, Tommy,

guess that it remains just a last dependency (-> draft-ietf-avt-app-rtp-keepalive) concerning the consent/approval of Draft H.248.50 (ex H.248.NATTT), if C-439 would be approved.

There seems to be still some "To Do's" when looking at:
https://datatracker.ietf.org/doc/draft-ietf-avt-app-rtp-keepalive/#ballot
https://datatracker.ietf.org/doc/draft-ietf-avt-app-rtp-keepalive/#history

However, the very majority of this material is pretty stable.
The impact of this IETF draft to the H.248 kar Package is primarily related to the Signal parameter kapt, where we got seven Keepalive Packet Types.

Would you agree to such a brief summary of Draft H.248.50 status?

If yes, I could imagine to consent/approve Draft H.248.50 already at this SG16, providing some "warning information" to specific kapt values ("if required at all").
There are already meaningful applications of such a kar v1 package in my opinion.

When the IETF published finally the RFC, we may cross-check again, and, if required, provide an IG item (or even a kar v2).

Any views?

Albrecht

_______________________________________________
Megaco mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/megaco