>Then you probably already know what the solution is going to be. I don't.
It’s not that I know the exact solution. It’s that I see this approach
offering good options for graceful migration to an opstate compliant solution
(for which I’m on the design team alias), without incurring any mo
> > Apparently Section 6.4 refers to MEF 55. I wonder why the
> > specification MEF 55
is
> > not referenced. Also, I believe the terminology in Section 6.4 may
> > have to be reviewed. For instance, MEF apparently uses the term
> > reference points ("Management Interface Reference Point") inste
Hi Michael,
Thanks for the helpful email.
> In general, I believe that distinguishing between different terms for "service
> model" is useful.
>
> Actually, I would suggest to align the terminology in
draft-ietf-l3sm-l3vpn-service-
> model accordingly, e.g., by using the term "Customer Service M
Hi all,
In general, I believe that distinguishing between different terms for "service
model" is useful.
Actually, I would suggest to align the terminology in
draft-ietf-l3sm-l3vpn-service-model accordingly, e.g., by using the term
"Customer Service Model" in the L3SM WG. For instance, the tit
> -Original Message-
> From: netmod [mailto:netmod-boun...@ietf.org] On Behalf Of Ladislav
> Lhotka
> Sent: Wednesday, September 7, 2016 8:22 PM
> To: Vladimir Vassilev
> Cc: netmod@ietf.org
> Subject: Re: [netmod] Circular dependency in 'when'
>
>
> > On 07 Sep 2016, at 19:44, Vladimir
