Re: [Cats] Next steps with CATS framework

[Dirk Trossen <[e-mail]>]

Med, all,

There needs to be a consistent discussion of this issue with what a 'service instance' actually is. 

Looking at the framework draft, it defines a service instance as 
"   Service instance:  A run-time environment (e.g., a server or a process on a server) that makes a service instance available  (i.e., up and running).  One service can be accessed through
      multiple instances running at the same or different locations."

I've never seen this definition limited to mean ONE service instance that literally provides one incoming request with a suitable response, but having a notion of multi-homing of services, even recursiveness (e.g., locally dispatching through K8S or similar environments). 

To make this more explicit, one could refine that definition as 
"   Service instance:  A run-time environment (e.g., a server or a process on a server) that makes AT LEAST ONE service instance available  (i.e., up and running).  One service can be accessed through multiple instances running at the same or different locations." (marking the change in capital, not meant to actually write it in capital in the draft).

With that a 'service instance ID' or 'service instance address' (if one wants to make the 'locator' notion more explicit, while 'ID' is more generic) suffices in my view since we are not capturing a true E2E relationship but are only concerned with the traffic steering at the CATS (overlay) level, aren't we?

Best,

Dirk

-----Original Message-----
From: [e-mail] <[e-mail]> 
Sent: 19 April 2023 08:52
To: Linda Dunbar <[e-mail]>; Dirk Trossen <[e-mail]>; Luigi Iannone <[e-mail]>
Cc: [e-mail]; [e-mail]; [e-mail]
Subject: RE: [Cats] Next steps with CATS framework

Hi Linda, 

As we are in early stages of the arch discussion, we need to be careful about the terms we are using as this may imply some arch assumptions. For example, "instance id" may be interpreted as if it always conveys the identity of the exact instance that will provide the service and won't be used/useful for the recursive mode where another dispatcher level will be on path (and which will be responsible for determining the exact instance). For example, many service-specific dispatchers can be hosted in the same node, supplying an id that will identify the dispatcher for a given request would avoid requiring an extra classification operation in the service site edge. 

Till that arch discussion happens, I prefer we have a more neutral term that covers both the direct and recursive mode. 

Please note that the current definition of the term we are discussing is as follows: 

   CATS Binding ID (CB-ID):  An identifier of a single service instance
      or location of a given service instance (CS-ID).  See Section 3.2.

Cheers,
Med

> -----Message d'origine-----
> De : Cats <[e-mail]> De la part de Linda Dunbar Envoyé : 
> mardi 18 avril 2023 16:58 À : BOUCADAIR Mohamed INNOV/NET 
> <[e-mail]>; Dirk Trossen 
> <[e-mail]>; Luigi Iannone <[e-mail]> Cc : 
> [e-mail]; [e-mail];
> [e-mail]
> Objet : Re: [Cats] Next steps with CATS framework
> 
> Med,
> 
> Then Instance ID [InstID]? Everyone in the industry understands it 
> well.
> 
> I think adding the  "Location ID" [ILID] to the name just adds more 
> complication & confusion as it needs so much more explanation.
> 
> we might incorporate the ILA [Identify Location Address]
> (https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2
> Fdatatracker.ietf.org%2Fdoc%2Fdraft-herbert-ila-
> mobile%2F&data=05%7C01%7Cmohamed.boucadair%40orange.com%7C83ea0826
> a8f649194d4508db401d4ab5%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0%7C
> 0%7C638174266779200632%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDA
> iLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sd
> ata=87Q%2BiZ1qk4%2FIWeZptST6ixr2zDN1aWjBnyGKOrpR8lI%3D&reserved=0
> ), which was proposed by Facebook a few years ago, into the structure 
> of the Instance ID.
> 
> Linda
> 
> -----Original Message-----
> From: [e-mail] <[e-mail]>
> Sent: Tuesday, April 18, 2023 9:37 AM
> To: Linda Dunbar <[e-mail]>; Dirk Trossen 
> <[e-mail]>; Luigi Iannone <[e-mail]>
> Cc: [e-mail]; [e-mail];
> [e-mail]
> Subject: RE: [Cats] Next steps with CATS framework
> 
> Hi Linda,
> 
> We do already have a service ID. What we are discussing is the actual 
> instance that will provide the requested service. This can be a 
> specific service instance or a site that hosts the instance.
> 
> Cheers,
> Med
> 
> > -----Message d'origine-----
> > De : Cats <[e-mail]> De la part de Linda Dunbar
> Envoyé :
> > mardi 18 avril 2023 16:31 À : BOUCADAIR Mohamed INNOV/NET 
> > <[e-mail]>; Dirk Trossen 
> > <[e-mail]>; Luigi Iannone <[e-mail]> Cc :
> > [e-mail]; [e-mail];
> > [e-mail]
> > Objet : Re: [Cats] Next steps with CATS framework
> >
> > > How about EID - endpoint ID
> >
> > I'm afraid this is too generic and will be interpreted as if the 
> > entity having the EID will terminate the connection and process
> the
> > request, while this is not always the case.
> >
> > [Linda] Why not call it "Service ID"?
> > Linda
> >
> > -----Original Message-----
> > From: Cats <[e-mail]> On Behalf Of 
> > [e-mail]
> > Sent: Tuesday, April 18, 2023 9:21 AM
> > To: Dirk Trossen <[e-mail]>; Luigi Iannone 
> > <[e-mail]>
> > Cc: [e-mail]; [e-mail];
> > [e-mail]
> > Subject: Re: [Cats] Next steps with CATS framework
> >
> > Hi Dirk, Luigi,
> >
> > > May it's a nit, but what about
> > > "Instance/Location ID - ILID"
> >
> > Would be OK as well.
> >
> > > How about EID - endpoint ID
> >
> > I'm afraid this is too generic and will be interpreted as if the 
> > entity having the EID will terminate the connection and process
> the
> > request, while this is not always the case. Thanks.
> >
> > Cheers,
> > Med
> >
> > > -----Message d'origine-----
> > > De : Dirk Trossen <[e-mail]> Envoyé : mardi 18
> > avril
> > > 2023 16:01 À : Luigi Iannone <[e-mail]>; BOUCADAIR
> Mohamed
> > > INNOV/NET <[e-mail]> Cc :
> > [e-mail];
> > > [e-mail];
> > > [e-mail]
> > > Objet : RE: [Cats] Next steps with CATS framework
> > >
> > > How about EID - endpoint ID - given that it is about an
> endpoint
> > > identifier rather than a service identifier? Whether the
> > endpoint is a
> > > site (then further dispatching an incoming request) or an
> > instance
> > > itself is subject to deployment.
> > >
> > > Best,
> > >
> > > Dirk
> > >
> > > -----Original Message-----
> > > From: Cats <[e-mail]> On Behalf Of Luigi Iannone
> > > Sent: 18 April 2023 15:49
> > > To: <[e-mail]>
> > <[e-mail]>
> > > Cc: [e-mail]; [e-mail];
> > > [e-mail]
> > > Subject: Re: [Cats] Next steps with CATS framework
> > >
> > >
> > >
> > > > On 18 Apr 2023, at 10:32, [e-mail]
> wrote:
> > > >> -  Possibly rename "Binding ID" to "Instance ID" (Could
> > simply make
> > > >> this change unless someone has an issue with it)
> > > >
> > > > [Med] The proposed change does not cover well the case where
> > the
> > > selection output is a site, not the instance itself. "Instance 
> > > Location ID" would be OK.
> > >
> > > May it's a nit, but what about
> > > "Instance/Location ID - ILID"
> > > Or
> > > "Location/Instance ID - LIID"
> > >  to better capture that it can be either a service instance or
> > its
> > > location..
> > >
> > > Ciao
> > >
> > > L.
> > >
> > > --
> > > Cats mailing list
> > > [e-mail]
> > > https://eur0/
> > >
> >
> 3.safelinks.protection.outlook.com%2F%3Furl%3Dhttps%253A%252F%252F
> > &dat
> > >
> >
> a=05%7C01%7Clinda.dunbar%40futurewei.com%7C7c674e6dc1e34b03618b08d
> > b401
> > >
> >
> 81dcb%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C1%7C638174244584938
> > 342%
> > >
> >
> 7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTi
> > I6Ik
> > >
> >
> 1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=yX2Ns3VkU4W4StMAlz%2F07
> > IilS
> > > r8XPRKI%2BcwbNohvUgE%3D&reserved=0
> > >
> > http://w/
> >
> data=05%7C01%7Clinda.dunbar%40futurewei.com%7C0d2d0ca72bad417b14d8
> 08db
> >
> 401a63fe%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C638174254330
> 7393
> >
> 72%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJ
> BTiI
> >
> 6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=iUoBEvYEcxESQiecRuG3
> dTQd
> > 9xZ4PgaB%2FrPprBrMnNs%3D&reserved=0
> > ww.i
> > >
> >
> %2F&data=05%7C01%7Cmohamed.boucadair%40orange.com%7C34bf80062ff64d
> > 9ba9
> > >
> >
> cd08db40198413%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0%7C0%7C638174
> > 2505
> > >
> >
> 58244534%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luM
> > zIiL
> > >
> >
> CJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=j8vuqiYEJ4Xl9M
> > nqAl
> > > pUUS7USEgQ7%2BhL98iWH2JPVZ0%3D&reserved=0
> > >
> >
> etf.org%2F&data=05%7C01%7Clinda.dunbar%40futurewei.com%7C7c674e6dc
> > 1e34
> > >
> >
> b03618b08db40181dcb%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C1%7C6
> > 3817
> > >
> >
> 4244584938342%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoi
> > V2lu
> > >
> >
> MzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=rl28XWtCb
> > ZIJN
> > >
> >
> HC76wPWcXc86Dbkz5yAStwg%2Fo3eOL8%3D&reserved=0%2Fmailman%2Flistinf
> > o%2F
> > > cats&data=05%7C01%7Cmohamed.bo
> > >
> >
> ucadair%40orange.com%7Ce57daf6328f3419ab77a08db40156201%7C90c7a20a
> > >
> >
> f34b40bfbc48b9253b6f5d20%7C0%7C0%7C638174232801019249%7CUnknown%7C
> > >
> >
> TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLC
> > >
> >
> JXVCI6Mn0%3D%7C2000%7C%7C%7C&sdata=q1ydjEfbx2l0SOQt%2BsKPohk2f86Gu
> > > 131mWlon5floPA%3D&reserved=0
> >
> >
> __________________________________________________________________
> > _______________________________________________________
> >
> > Ce message et ses pieces jointes peuvent contenir des
> informations
> > confidentielles ou privilegiees et ne doivent donc pas etre
> diffuses,
> > exploites ou copies sans autorisation. Si vous avez recu ce
> message
> > par erreur, veuillez le signaler a l'expediteur et le detruire
> ainsi
> > que les pieces jointes. Les messages electroniques etant
> susceptibles
> > d'alteration, Orange decline toute responsabilite si ce message
> a ete
> > altere, deforme ou falsifie.
> > Merci.
> >
> > This message and its attachments may contain confidential or 
> > privileged information that may be protected by law; they should
> not
> > be distributed, used or copied without authorisation.
> > If you have received this email in error, please notify the
> sender and
> > delete this message and its attachments.
> > As emails may be altered, Orange is not liable for messages that
> have
> > been modified, changed or falsified.
> > Thank you.
> >
> > --
> > Cats mailing list
> > [e-mail]
> > https://eur0/
> >
> 3.safelinks.protection.outlook.com%2F%3Furl%3Dhttps%253A%252F%252F
> &dat
> >
> a=05%7C01%7Clinda.dunbar%40futurewei.com%7C0d2d0ca72bad417b14d808d
> b401
> >
> a63fe%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C638174254330739
> 372%
> >
> 7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTi
> I6Ik
> >
> 1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=sKujzIP3Rum%2FC5Yust2AN
> 1Jqq
> > prKvYS1OtkadFvuuNw%3D&reserved=0
> >
> https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fw
> ww.i
> >
> %2F&data=05%7C01%7Cmohamed.boucadair%40orange.com%7C83ea0826a8f649
> 194d
> >
> 4508db401d4ab5%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0%7C0%7C638174
> 2667
> >
> 79200632%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luM
> zIiL
> >
> CJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=cqRGmQFHjaLqnh
> 96zD
> > 2jOEVHdmK6odJbi10Qb2G14Xw%3D&reserved=0
> >
> etf.org%2F&data=05%7C01%7Clinda.dunbar%40futurewei.com%7C0d2d0ca72
> bad4
> >
> 17b14d808db401a63fe%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C6
> 3817
> >
> 4254330739372%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoi
> V2lu
> >
> MzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=EgVdFktHh
> 0igZ
> >
> STshnhOuTB8h%2FlIYZWLYYfLuYp3eHo%3D&reserved=0%2Fmailman%2Flistinf
> o%2F
> > cats&data=05%7C01%7Cmohamed.bo
> >
> ucadair%40orange.com%7C34bf80062ff64d9ba9cd08db40198413%7C90c7a20a
> >
> f34b40bfbc48b9253b6f5d20%7C0%7C0%7C638174250558244534%7CUnknown%7C
> >
> TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLC
> >
> JXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=YFsPSlAUjGklp71OLbOfRNKLQlYB9Bp
> > AVGrlNrDjLaI%3D&reserved=0
> >
> > --
> > Cats mailing list
> > [e-mail]
> > https://eur0/
> >
> 3.safelinks.protection.outlook.com%2F%3Furl%3Dhttps%253A%252F%252F
> &dat
> >
> a=05%7C01%7Clinda.dunbar%40futurewei.com%7C0d2d0ca72bad417b14d808d
> b401
> >
> a63fe%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C638174254330739
> 372%
> >
> 7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTi
> I6Ik
> >
> 1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=sKujzIP3Rum%2FC5Yust2AN
> 1Jqq
> > prKvYS1OtkadFvuuNw%3D&reserved=0
> >
> https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fw
> ww.i
> >
> %2F&data=05%7C01%7Cmohamed.boucadair%40orange.com%7C83ea0826a8f649
> 194d
> >
> 4508db401d4ab5%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0%7C0%7C638174
> 2667
> >
> 79200632%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luM
> zIiL
> >
> CJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=cqRGmQFHjaLqnh
> 96zD
> > 2jOEVHdmK6odJbi10Qb2G14Xw%3D&reserved=0
> >
> etf.org%2F&data=05%7C01%7Clinda.dunbar%40futurewei.com%7C0d2d0ca72
> bad4
> >
> 17b14d808db401a63fe%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C6
> 3817
> >
> 4254330739372%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoi
> V2lu
> >
> MzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=EgVdFktHh
> 0igZ
> >
> STshnhOuTB8h%2FlIYZWLYYfLuYp3eHo%3D&reserved=0%2Fmailman%2Flistinf
> o%2F
> > cats&data=05%7C01%7Cmohamed.bo
> >
> ucadair%40orange.com%7C34bf80062ff64d9ba9cd08db40198413%7C90c7a20a
> >
> f34b40bfbc48b9253b6f5d20%7C0%7C0%7C638174250558244534%7CUnknown%7C
> >
> TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLC
> >
> JXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=YFsPSlAUjGklp71OLbOfRNKLQlYB9Bp
> > AVGrlNrDjLaI%3D&reserved=0
> 
> __________________________________________________________________
> _______________________________________________________
> 
> Ce message et ses pieces jointes peuvent contenir des informations 
> confidentielles ou privilegiees et ne doivent donc pas etre diffuses, 
> exploites ou copies sans autorisation. Si vous avez recu ce message 
> par erreur, veuillez le signaler a l'expediteur et le detruire ainsi 
> que les pieces jointes. Les messages electroniques etant susceptibles 
> d'alteration, Orange decline toute responsabilite si ce message a ete 
> altere, deforme ou falsifie.
> Merci.
> 
> This message and its attachments may contain confidential or 
> privileged information that may be protected by law; they should not 
> be distributed, used or copied without authorisation.
> If you have received this email in error, please notify the sender and 
> delete this message and its attachments.
> As emails may be altered, Orange is not liable for messages that have 
> been modified, changed or falsified.
> Thank you.
> 
> --
> Cats mailing list
> [e-mail]
> https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2F
> www.ietf.org%2Fmailman%2Flistinfo%2Fcats&data=05%7C01%7Cmohamed.bo
> ucadair%40orange.com%7C83ea0826a8f649194d4508db401d4ab5%7C90c7a20a
> f34b40bfbc48b9253b6f5d20%7C0%7C0%7C638174266779200632%7CUnknown%7C
> TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLC
> JXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=iL74b0J%2FHwTVuvg6Qp%2Bkc5sQOSS
> MNB%2FR2PgCRxJlHcs%3D&reserved=0

_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.