[DMM] review comment to SRv6-mobile-uplane draft

["Flinck, Hannu (Nokia - FI/Espoo)" <[e-mail]>]

Hello all

Here are my promised review comments to SRv6-mobile-uplane draft.

Best regards
Hannu
-------------------------------

Abstract

"This document describes the SRv6 mobile user plane behavior and defines the SID functions for that.
It also provides a mechanism for end-to-end network slicing."

I didn't find any particular mechanism for slicing that is introduced in this document, but instead section 8 that discusses considerations and makes references to other documents. I suggest to remove this statement about slicing in the abstract.


Section 5.1.1 Packet flow - Uplink

How is the 1-to-1 mapping done or replicated as was mentioned in 5.1?
("This 1-for-1 mapping is replicated here to replace GTP encapsulation with the SRv6 encapsulation, while not changing anything else. ")

What is  "a specific table" where the look up is to be done? Does this mean that to support mobile uplane there needs to be an additional look up table?

Section 5.1.2 packet flow - Downlink

In this case you probably need an additional look up table to map the destination address of the UE with address/SID of the gNB.

What is UE session? Can UE have multiple UE sessions (i.e. multi-homing)? How is the mapping to radio bearer done?

Section 5.1.3
You should qualify how much lower the overhead is.

Section 5.2 Enhanced Mode
How much overhead does the use of multiple SIDs introduce? And what is the impact to header compression?

Not sure I understand this sentence:
"Note that the SIDs MAY use the arguments Args.Mob.Session if required by the UPFs."

When it is required to use Args.Mob.Session? Please note that this is the first time you mention Args.Mob.Session and therefore you should introduce it. In section 6.1 it is said that the Args.Mob.Session provides per-session information. When would a SID need this information and what it would be? And shouldn't it be UPF rather than SID that needs this information?


Section 5.2.1 Packet flow - Uplink

Should show here how Args.Mob.Session is used.

"gNB's control plane associates that session from the UE(A) with the IPv6
address B and GTP TEID T.  gNB's control plane does a lookup on B to
find the related SID list <S1, C1, U2::1>."

What is address B? Shouldn't it be address Z? How is TEID used in this case?

Section 5.3.1 Interworking with IPv6 GTP
How does the SRGW learn SID list to a DA? This must be per-session doesn't it?

Section 5.3.1.1 Packet flow  - Uplink
"There is one instance of the End.M.GTP6.D SID per PDU type." How is the PDU type learnt? By use of TEID?

Section 5.3.1.2 Packet flow - Downlink
"When a packet destined to A arrives at the UPF2, the UPF2 performs a lookup in the table associated to A ..."

How is this table populated? By  the mobility signaling?


Section 5.3.1.3 Scalability
TEID is scoped by the gNB and UPF2, same TEID may appear for different gNBs.

How would GTP echo work for these cases?

Section 6.1 Args.Mob.Session

Seems that this is only for 5G networks (because of use of QFI and R).

Can you please elaborate this a bit more: "Since the SRv6 function is likely NOT to be instantiated per PDU session, Args.Mob.Session helps the UPF to perform the functions which require per QFI and/or per PDU Session granularity."

And explain its relationship with the section 7.

Section 6.2 End.MAP

Is the mapping table used at step 1 mobile user plane specific or is it general for any SRv6?
If only for mobile user plane how is this populated?

Section 6.7 End.Limit
"If the j bit length is zero..." or do you mean j bits are zero?

Section 7 SRv6 supported 3GPP PDU session types

End.DT2M and End.DX2 not defined?

----- end of comments ------