I’m sensing a very similar issue here to what is happening in APN and 6gip.
We should be able to consider alternative architectures and protocols at a theoretical level across any network technology and that should include the ability to suggest new/different architectures. The problem with all of these groups seems to be that we are starting off at a very low-level and then trying to build up – it would be much better to define the outcome we wish to achieve at a strategic/architectural level and then generate WGs to fulfil the needs of that architecture. Personally, I think we need to consider how various related groups – can, dmm, 6gip and apn all come to mind – could help us deliver against the service goals of the next-gen Internet however that is defined. I think that needs to be carried out as a group outside of the narrow charter of a set of IETF WGs and possibly an IRTF RG is a much better place to land these pieces. David From: dmm <[email protected]> on behalf of Joel Halpern <[email protected]> Date: Wednesday, 2 November 2022 at 22:48 To: [email protected] <[email protected]> Cc: [email protected] <[email protected]>, [email protected] <[email protected]>, [email protected] <[email protected]> Subject: Re: [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]<mailto:[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]<mailto:[email protected]> mailing lists by 2022-11-23. > Exceptionally, comments may > be sent to [email protected]<mailto:[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/<https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fdraft-ietf-dmm-srv6-mobile-uplane%2F&data=05%7C01%7Cd.lake%40surrey.ac.uk%7Cc8936ea4f2e44385a4fc08dabd24532a%7C6b902693107440aa9e21d89446a2ebb5%7C0%7C0%7C638030260971255499%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=ZGocxap5EI3JwzXO7G2uCWt4sMYLPprTqndbZU0rNiM%3D&reserved=0> > > > The following IPR Declarations may be related to this I-D: > > > https://datatracker.ietf.org/ipr/3891/<https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatatracker.ietf.org%2Fipr%2F3891%2F&data=05%7C01%7Cd.lake%40surrey.ac.uk%7Cc8936ea4f2e44385a4fc08dabd24532a%7C6b902693107440aa9e21d89446a2ebb5%7C0%7C0%7C638030260971411699%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=cn9HYK8pgDtoCfTOCb2L%2BoLNRXYeHSVhhzEyiigBQ6A%3D&reserved=0> > > https://datatracker.ietf.org/ipr/3979/<https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatatracker.ietf.org%2Fipr%2F3979%2F&data=05%7C01%7Cd.lake%40surrey.ac.uk%7Cc8936ea4f2e44385a4fc08dabd24532a%7C6b902693107440aa9e21d89446a2ebb5%7C0%7C0%7C638030260971411699%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=vltlx6vlA04qUGJuOzGVBezFBTA58thwgh58eahOmSU%3D&reserved=0> > > https://datatracker.ietf.org/ipr/3950/<https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatatracker.ietf.org%2Fipr%2F3950%2F&data=05%7C01%7Cd.lake%40surrey.ac.uk%7Cc8936ea4f2e44385a4fc08dabd24532a%7C6b902693107440aa9e21d89446a2ebb5%7C0%7C0%7C638030260971411699%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=z4Evtk0SqGI3qbfc0SigxHILtBSx5ndnCUKVPGX%2FxNM%3D&reserved=0> > > > > > > > _______________________________________________ > IETF-Announce mailing list > [email protected]<mailto:[email protected]> > https://www.ietf.org/mailman/listinfo/ietf-announce<https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Fietf-announce&data=05%7C01%7Cd.lake%40surrey.ac.uk%7Cc8936ea4f2e44385a4fc08dabd24532a%7C6b902693107440aa9e21d89446a2ebb5%7C0%7C0%7C638030260971411699%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=qQviGHwa36YlkCjvIWOJffvKGVjrEhsBvSiSgwfBAxk%3D&reserved=0> _______________________________________________ dmm mailing list [email protected]<mailto:[email protected]> https://www.ietf.org/mailman/listinfo/dmm<https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Fdmm&data=05%7C01%7Cd.lake%40surrey.ac.uk%7Cc8936ea4f2e44385a4fc08dabd24532a%7C6b902693107440aa9e21d89446a2ebb5%7C0%7C0%7C638030260971411699%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=hPZoq7xZoMkBv4fT%2Bm9ecBgyBTcV9B476SQYkPEjJV0%3D&reserved=0>
_______________________________________________ dmm mailing list [email protected] https://www.ietf.org/mailman/listinfo/dmm
