Re: [Teas] [CCAMP] Decision point on scope of draft-ietf-teas-ietf-network-slices

[Igor Bryskin <[e-mail]>]

Hi Adrian,

In response to Igor’s series of emails:
   
   - If a 5G RAN is supported over an OTN then the concept of an e2e slice requires that there is something that can be called a transport network slice supported by the OTN.
IB:. I think to achieve this it would take basic OTN service delivering non-IP client over p2p links, something OTN has been doing for decades.
   
   - If the IETF Network Slicing Service YANG module is agnostic of the underlay network, then it should be possible for any network technology to have a go at supporting it.
IB: This includes not just OTN, of course,  but also flexE. microwave, OCh, physical fiber, lease line, PW and pretty much anything else that can deliver bits from A to B. To paraphrase my favorite Gert's question: what is not a transport slice according to the framework?
   
   - If a vendor does not want to implement or an operator does not want to support slicing over an OTN, that is a free choice.
IB: of course.
   
   - If the concept of slicing an OTN is no different from building a VN or a set of LSPs in that network, why is this whole thing a big deal?
IB: As one Austrian guy said  "sometimes a cigar is just a cigar" and should be called cigar, rather than, say, tobaco slice );Yes, it is not big deal if we stick to VNs, which normally are bottom up network building constructs. But it could become a rather big deal if one tries to engage OTN directly in the top down netwrk slicing process by, for example, creating VNs on the fly.
Cheers,Igor
 

Sent from Yahoo Mail on Android 
 
  On Wed, Mar 9, 2022 at 12:01 PM, Adrian Farrel<[e-mail]> wrote:   _______________________________________________
CCAMP mailing list
[e-mail]
https://www.ietf.org/mailman/listinfo/ccamp