Re: [Last-Call] Last Call: <draft-ietf-dmm-srv6-mobile-uplane-21.txt> (Segment Routing IPv6 for Mobile User Plane) to Proposed Standard

Joel Halpern <[email protected]>
Newsgroups gmane.ietf.nemo
Message-ID <[email protected]>
The draft explicitly (in sections 5.1 and 5.2) modifies the behavior of 
gNodeBs and UPF over the N3 and N9 interface.  That is coverd by 3GPP 
standards.  Having the IETF promulgate a standard that modifies another 
SDos work seems wrong.  Particularly so when the SDO has evaluated and 
rejected the work.  If 3GPP wants to change its mind, that is their 
business.

As far as I can tell, this draft could be published as an Informational 
RFC.  While an odd thing for us to do, it would at least avoid the IETF 
claiming to standardize modification to some other SDOs work.

Yours,

Joel

On 11/21/2022 11:33 AM, Keyur Patel wrote:
>
> Hi Folks,
>
> I like to respectfully disagree with Joel’s comments. IMHO this 
> proposal does not alter any 3GPP standards. Furthermore, there are 
> multiple implementations of this standard. I suggest we consider 
> progressing the draft on the standards track.
>
> Best Regards,
>
> Keyur
>
> *From: *last-call <[email protected]> on behalf of Joel 
> Halpern <[email protected]>
> *Date: *Wednesday, November 2, 2022 at 6:47 PM
> *To: *[email protected] <[email protected]>
> *Cc: *[email protected] <[email protected]>, 
> [email protected] 
> <[email protected]>, [email protected] <[email protected]>
> *Subject: *Re: [Last-Call] [DMM] Last Call: 
> <draft-ietf-dmm-srv6-mobile-uplane-21.txt> (Segment Routing IPv6 for 
> Mobile User Plane) to Proposed Standard
>
> True, my concern is not new.  However, this is now the IETF last call, 
> so I need to raise it to the larger community.
>
> Yours,
>
> Joel
>
> On 11/2/2022 6:29 PM, Behcet Sarikaya wrote:
>
>     On Wed, Nov 2, 2022 at 12:08 PM Joel Halpern <[email protected]>
>     wrote:
>
>         This document appears to be technically internally consistent.
>         However,
>         it appears to redefine the 3GPP architecture.  Which seems
>         inappropriate
>         for an IETF Proposed Standard.  if another SDO started
>         redefining the IP
>         architecture we would be (and have been) understandably
>         upset.  The
>         Traditional mode significantly modifies a defined standard
>         encapsulation
>         from 3GPP.  The Enhanced Mode goes further, and redefines the
>         3GPP
>         architecture for delivering services.
>
>         These may be good ideas.  if so, they should be discussed and
>         adopted by
>         the SDO which owns the architecture.  The fact that these were
>         brought
>         to 3GPP and preliminary versions of these ideas were turned down
>         emphasis the point that we should not be stepping on other
>         people's work.
>
>     This is nothing new, it has been the dmm story in recent years,
>     and you know it well.
>
>     Behcet
>
>         Yours,
>
>         Joel
>
>         On 11/2/2022 10:22 AM, The IESG wrote:
>         > The IESG has received a request from the Distributed
>         Mobility Management WG
>         > (dmm) to consider the following document: - 'Segment Routing
>         IPv6 for Mobile
>         > User Plane'
>         > <draft-ietf-dmm-srv6-mobile-uplane-21.txt> as Proposed Standard
>         >
>         > The IESG plans to make a decision in the next few weeks, and
>         solicits final
>         > comments on this action. Please send substantive comments to the
>         > [email protected] mailing lists by 2022-11-23.
>         Exceptionally, comments may
>         > be sent to [email protected] instead. In either case, please
>         retain the beginning
>         > of the Subject line to allow automated sorting.
>         >
>         > Abstract
>         >
>         >
>         >     This document specifies the applicability of SRv6
>         (Segment Routing
>         >     IPv6) to the user-plane of mobile networks. The network
>         programming
>         >     nature of SRv6 accomplishes mobile user-plane functions
>         in a simple
>         >     manner.  The statelessness of SRv6 and its ability to
>         control both
>         >     service layer path and underlying transport can be
>         beneficial to the
>         >     mobile user-plane, providing flexibility, end-to-end
>         network slicing,
>         >     and SLA control for various applications.
>         >
>         >
>         >
>         >
>         > The file can be obtained via
>         >
>         https://datatracker.ietf.org/doc/draft-ietf-dmm-srv6-mobile-uplane/
>         >
>         >
>         > The following IPR Declarations may be related to this I-D:
>         >
>         > https://datatracker.ietf.org/ipr/3891/
>         > https://datatracker.ietf.org/ipr/3979/
>         > https://datatracker.ietf.org/ipr/3950/
>         >
>         >
>         >
>         >
>         >
>         >
>         > _______________________________________________
>         > IETF-Announce mailing list
>         > [email protected]
>         > https://www.ietf.org/mailman/listinfo/ietf-announce
>
>         _______________________________________________
>         dmm mailing list
>         [email protected]
>         https://www.ietf.org/mailman/listinfo/dmm
>

_______________________________________________
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.