Re: [L3sm] Comments on draft-ietf-l3sm-l3vpn-service-model

> > But some early, precautionary modularisation is not going to be a
> problem so long as we don't spend too long arguing about exactly what
> to modularise.
>
> Fully agree ..., some sections Kireeti was mentioning are evident to be
> as a reusable component so we can do it now, for more complex things,
> let's think about it after the module is (almost) finished.

There is great value in having a consistent model without complex external dependencies, and we should aim at publishing that model soon. This significantly simplifies implementation.

Michael 

> -----Original Message-----
> From: L3sm [mailto:l3sm-bounces@ietf.org] On Behalf Of Adrian Farrel
> Sent: Wednesday, July 22, 2015 14:28
> To: 'Kireeti Kompella'; l3sm@ietf.org
> Subject: Re: [L3sm] Comments on draft-ietf-l3sm-l3vpn-service-model
> 
> Hello Kireeti,
> 
> Welcome to the party.
> 
> > 1) At a high level, I would like to see services as compositions
> > (mash-ups) of service elements.  This is a generalization of the
> comments that Aijun made.
> > Here’s why.  As we (either the IETF or other bodies, or SPs on their
> > own) define other services, it would be very convenient to be able to
> > reuse these service elements.
> 
> I completely take your point, but...
> 
> When we started the L3SM work we were not certain (and some remain
> uncertain) that the problem could be addressed even for one of our most
> simple services (the L3VPN) let alone for a more generic concept of
> services. Therefore, the WG was explicitly tasked (read the charter) to
> work with focus and attention on L3VPN only and to exclude
> consideration of other services.
> 
> That, in itself, does not predicate against modularisation, but it does
> make it hard to consider which modules to have (since some aspects of
> modularisation must surely consider the other services that might use
> the modules).
> 
> Therefore, my expectation of progress is...
> 
> - Continue to progress L3SM towards completion
> - Publish an RFC (if it can be agreed and done)
> - Start work on another similar service model (e.g. L2SM)
>    - If there is energy
>    - If the IESG gives us permission
> - Look for commonalities and modularisations
>    - If they exist it may be necessary to revise L3SM
> 
> So, from some aspects this does not look optimal. Perhaps you could
> have made this comment during chartering.
> But from another perspective it enables some initial progress in a new
> subject space that the IETF has not previously attempted. If it is
> successful we can dig deeper.
> 
> Overall (setting aside the fact that we are anyway constrained by our
> charter) I have a fear of ocean-boiling. But some early, precautionary
> modularisation is not going to be a problem so long as we don't spend
> too long arguing about exactly what to modularise.
> 
> Adrian
> 
> 
> 
> _______________________________________________
> L3sm mailing list
> L3sm@ietf.org
> https://www.ietf.org/mailman/listinfo/l3sm
> 
> _______________________________________________________________________
> __________________________________________________
> 
> 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.
> 
> _______________________________________________
> L3sm mailing list
> L3sm@ietf.org
> https://www.ietf.org/mailman/listinfo/l3sm