In traditional MVVM, what do you guys consider your model(ie your networking layer) ?

I consider everything after domain (inclusive)

To be specific, I consider my repository/useCase class and everything it encapsulates (ie DAO, webservices/networking etc)

what is traditional MVVM, is it MVVM without clean architecture, D.I?

Without clean architecture. im guessing.

so in some cases, or some projects, we just need traditional MVVM?

I think MVVM, doesn't need clean architecture to be honest. The usecase model is cool and all , but its not needed to accomplish mvvm

In MVVM the model is everything that isn't the UI, bit different definition than what most things mean when they say model