[{"author": "Lou Berger", "text": "

@meetecho can you show the speaker

", "time": "2023-07-28T16:35:32Z"}, {"author": "Lou Berger", "text": "

thank you!

", "time": "2023-07-28T16:35:55Z"}, {"author": "Lorenzo Miniero", "text": "

Done!

", "time": "2023-07-28T16:35:55Z"}, {"author": "Oscar de Dios", "text": "

srihari, we cannot hear you

", "time": "2023-07-28T16:54:44Z"}, {"author": "Lou Berger", "text": "

@srihari we can't hear you, can you type your question

", "time": "2023-07-28T16:54:51Z"}, {"author": "Srihari Sangli", "text": "

I'l post the question here. My connection is bad. There is a statement about the number of filter topologies. And since its not a high number the SPF run will not burden the routers. Will there be a guidance on how many filtered topologies is recommended ?

", "time": "2023-07-28T16:56:02Z"}, {"author": "Jie Dong", "text": "

@Srihari to me there is no specific number so far, but the expectation is the number of filtered topology would be much less than that of the NRPs

", "time": "2023-07-28T17:00:02Z"}, {"author": "Srihari Sangli", "text": "

@Jie since this was a design consideration, hence my question was on providing guidance.

", "time": "2023-07-28T17:08:25Z"}, {"author": "Daniel King", "text": "

There is non-ACTN content in this I-D.

", "time": "2023-07-28T17:10:59Z"}, {"author": "Daniel King", "text": "

The ACTN applicability document is very specific to the ACTN architecture and as just mentioned, possible models.

", "time": "2023-07-28T17:11:37Z"}, {"author": "Daniel King", "text": "

To include the full ACTN applicability text in draft-barguil-teas-network-slices-instantiation would swamp all of the other material, while putting non-ACTN in the ACTN applicability draft would not be good.

", "time": "2023-07-28T17:12:03Z"}, {"author": "Daniel King", "text": "

^^ As author of both this I-D and ACTN Applicability to Network Slicing.

", "time": "2023-07-28T17:12:30Z"}, {"author": "Daniel King", "text": "

I think this I-D should reference the ACTN applicability document, and it should, maybe, include a short subsection listing ACTN models.

", "time": "2023-07-28T17:12:58Z"}, {"author": "Jie Dong", "text": "

@Srihari undertood, hope the WG can work out something on the guidance for filtered topology

", "time": "2023-07-28T17:14:31Z"}, {"author": "Dhruv Dhody", "text": "

+1 to what Dan said

", "time": "2023-07-28T17:14:37Z"}, {"author": "Dhruv Dhody", "text": "

change in title makes sense

", "time": "2023-07-28T17:14:57Z"}, {"author": "Daniel King", "text": "

^^ good suggestion.

", "time": "2023-07-28T17:15:15Z"}, {"author": "Dhruv Dhody", "text": "

Would this be the smallest font we have seen?

", "time": "2023-07-28T17:23:25Z"}, {"author": "Lou Berger", "text": "

I always download locally for this reason....

", "time": "2023-07-28T17:24:37Z"}, {"author": "Jie Dong", "text": "

:)

", "time": "2023-07-28T17:24:41Z"}, {"author": "Oscar de Dios", "text": "

I have to take off my glasses to read the font

", "time": "2023-07-28T17:25:03Z"}, {"author": "Daniele Ceccarelli", "text": "

it's done on purpose...to force you to listen instead of reading :D

", "time": "2023-07-28T17:25:30Z"}, {"author": "Dhruv Dhody", "text": "

:exploding_head:

", "time": "2023-07-28T17:25:51Z"}, {"author": "Italo Busi", "text": "

It is the customer intent to have a topology

", "time": "2023-07-28T17:30:32Z"}, {"author": "Dhruv Dhody", "text": "

https://datatracker.ietf.org/doc/html/rfc8795#section-4.2

", "time": "2023-07-28T17:30:35Z"}, {"author": "Dhruv Dhody", "text": "

Yup! The name needs changing

", "time": "2023-07-28T17:30:44Z"}, {"author": "Italo Busi", "text": "

Customer intent topology?

", "time": "2023-07-28T17:31:26Z"}, {"author": "Dhruv Dhody", "text": "

I think the key difference would this I-D tries to define a network type called \"network-slice\" where as VN was an independent YANG model

", "time": "2023-07-28T17:41:20Z"}, {"author": "Italo Busi", "text": "

The semantic of the current reference is not clear and confusing

", "time": "2023-07-28T17:41:53Z"}, {"author": "Dhruv Dhody", "text": "

I am unsure why we need a new network type - is there a clear need or just a matter of taste?

", "time": "2023-07-28T17:43:01Z"}, {"author": "Oscar de Dios", "text": "

Is the intention to be technolgy agnostic in the requested (intented) topology , or it is the intentation to go into detailed technology specific topology (e.g. ask for dedicated OTN channels)

", "time": "2023-07-28T17:43:03Z"}, {"author": "Oscar de Dios", "text": "

?

", "time": "2023-07-28T17:43:05Z"}, {"author": "Aihua Guo", "text": "

For this draft the intention is to make a technology agnostic model for building \u201cintended\u201d topologies and it can be augmented with a technology specific model for e.g. OTN network slicing

", "time": "2023-07-28T17:51:21Z"}, {"author": "Aihua Guo", "text": "

A customized topology has SLO/SLE specifications associated with the topological elements. Not all topology models may be used for this purpose. Therefore the intention is to define a specific type for network slicing and use it

", "time": "2023-07-28T17:55:13Z"}, {"author": "Vishnu Beeram", "text": "

I don't believe the LS from O-Ran requested a reply..

", "time": "2023-07-28T17:57:18Z"}, {"author": "Oscar de Dios", "text": "

it did (I think)

", "time": "2023-07-28T17:57:34Z"}, {"author": "Vishnu Beeram", "text": "

okay..thx for confirming

", "time": "2023-07-28T17:59:02Z"}, {"author": "Oscar de Dios", "text": "

they ask to provide feedback

", "time": "2023-07-28T17:59:02Z"}, {"author": "Dhruv Dhody", "text": "

It is called DC aware TE topology model but there is no TE topology here

", "time": "2023-07-28T18:08:49Z"}, {"author": "Dhruv Dhody", "text": "

And then is TEAS even the the right home?

", "time": "2023-07-28T18:10:43Z"}, {"author": "Dhruv Dhody", "text": "

Is Refinements == Update?

", "time": "2023-07-28T18:14:44Z"}, {"author": "Luis Contreras", "text": "

@Dhruv, tahnks for the comment. Ceratinly we need to complement the draft with the TE stuff. In any case waht I do foresee is to follow same way as in draft-ietf-teas-sf-aware-topo-model, even though it could be the case of simply highlighting deltas with respect that draft focusing on the DC resources/capabilities

", "time": "2023-07-28T18:19:01Z"}, {"author": "Dhruv Dhody", "text": "

@Luis - thanks! looking forward to the update

", "time": "2023-07-28T18:23:15Z"}]