Subject: [DMM] Support for MNIDs (draft-ietf-dmm-4283mnids-06)

From: "Bertz, Lyle T [CTO]" <[email-masked]>
Date: Wed, 28 Feb 2018 18:57:41 +0000

All,

I would like to express my support of getting this particular work out as standard.

As we are implementing networks that support IoT (be it 4G IoT or 5G), new Mobile Node Types identified in the specification are appearing in more than just device configurations, i.e. we see these identifiers starting to appear in signaling and application communication more often.   This is currently being tied back to an identifier that the core may understand, e.g. IMSI in 4G EPC, but that requires a mapping to a fake identifier.  We still have to track and support the original identifier.

The conclusion that I (and others in my organization) have come to is that the extra mapping to a MNID we could support with the standardization of this specification and still needing to support the new MNID type as some sort of non-standard one off is wasteful.

5G specifications are also becoming a bit more relaxed in this area as well as we see Layer 2 connectivity in the core (this is seen a bit in 4G IoT as well), room for more identifier types and abstraction of identifiers.  Not everything is an IMSI or E.164 MSISDN any more.

Lyle

________________________________

This e-mail may contain Sprint proprietary information intended for the sole use of the recipient(s). Any use by others is prohibited. If you are not the intended recipient, please contact the sender and delete all copies of the message.