Subject: [DMM] On Demand Mobility Management Socket Extensions - Issue Summary

From: "Sri Gundavelli (sgundave)" <[email-masked]>
Date: Wed, 5 Apr 2017 15:37:33 +0000

During the last f2f meeting, there were lots of good discussions on this topic and on the fundamental issue of using "setsockopt()" call for a totally different purpose than what it is intended for, or what the semantics support.

There was good feedback from Suresh, Erik, Lorenzo and others, with few proposed options on the table.  WG needs to understand the differences between those options and pick the right approach.

Danny/Authors: Can you please summarize the options and post it to the group and also on what the authors prefer. We also need feedback from the KAME or other developer group who has built socket lib. If you can reach out to them and get some inputs, it will greatly help. Feedback from Android/IoS/Microsoft dev groups will also greatly help.

--------

09:25       Title: On Demand Mobility Management Socket Extensions

                      Description: Update on changes to the draft since IETF 97

                      Time: 15 minutes

                      Presenter: Danny Moses

                      Draft Reference: draft-ietf-dmm-ondemand-mobility-10

Danny presents socket extension draft.

V07 had WG last call, went to IESG for review.

Last IETF decision to merge a related draft. Draft pulled back to WG.

Good comments received from WG.

Several changes made.