Re: Additional questions/comments on draft-ietf-dmm-srv6-mobile-uplane-13

"Pablo Camarillo \(pcamaril\)" <[email protected]>
Newsgroups gmane.ietf.nemo
Message-ID <DM8PR11MB5719BFD5B34A5710CDEC7F2DC9E99@DM8PR11MB5719.namprd11.prod.outlook.com>
Hi Dave,

Many thanks for your comments. Inline with PC.

Cheers,
Pablo.

-----Original Message-----
From: dmm <[email protected]> On Behalf Of David Allan I
Sent: viernes, 23 de julio de 2021 19:51
To: [email protected]
Subject: Re: [DMM] Additional questions/comments on draft-ietf-dmm-srv6-mobile-uplane-13

Hi:

Looking over this draft it strikes me that IF you are discussing a GTP replacement, there are a few unaddressed gaps...or at least I see no mention of them.

-  adding X2 to the list of interfaces to be supported
[PC] Do you think there is any new mechanism to be added to the currently defined ones?

-  support for end-marker for handoff stream synchronization (probably could fit the unused bit in Args.Mob.Session but frankly I have not studied this in detail)
[PC] User Plane Message encoding is out of the scope of this draft. However, draft-murakami-dmm-user-plane-message-encoding-03 proposes a mechanism to encode the Echo Request, Echo Reply, Error Indication, and End Marker.

-  support for QMP (quality measurement protocol), which I believe needs to also extend across the radio interface so is not simply local to the GTP domain and can be "stunt doubled"
[PC] Excellent point. Seems we missed this one in draft-murakami! We can add in there the QoS Monitoring Packet indicator, as well as the encoding for the timestamps and average DL/UL delays.

-  support for paging policy presence/indication
[PC] Same as previous. Many thanks. 

[PC], By the way, I've posted an updated revision as the reference to draft-murakami was missing.

If this has come up elsewhere, let me know

Cheers
Dave


_______________________________________________
dmm mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/dmm
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.