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

Qin Wu <> Tue, 18 August 2015 10:37 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 49EAD1B335B for <>; Tue, 18 Aug 2015 03:37:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -3.61
X-Spam-Status: No, score=-3.61 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, J_CHICKENPOX_12=0.6, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id ks29R9ddgRDm for <>; Tue, 18 Aug 2015 03:37:38 -0700 (PDT)
Received: from ( []) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 480C91B3321 for <>; Tue, 18 Aug 2015 03:37:37 -0700 (PDT)
Received: from (EHLO ([]) by (MOS 4.3.7-GA FastPath queued) with ESMTP id BWJ66107; Tue, 18 Aug 2015 10:37:35 +0000 (GMT)
Received: from ( by ( with Microsoft SMTP Server (TLS) id; Tue, 18 Aug 2015 11:37:34 +0100
Received: from ([]) by ([]) with mapi id 14.03.0235.001; Tue, 18 Aug 2015 18:37:26 +0800
From: Qin Wu <>
To: "Scharf, Michael (Michael)" <>, Rob Shakir <>, 'Kireeti Kompella' <>, "" <>, "" <>, "" <>
Thread-Topic: [L3sm] Comments on draft-ietf-l3sm-l3vpn-service-model
Date: Tue, 18 Aug 2015 10:37:25 +0000
Message-ID: <>
References: <> <029d01d0c479$dc07ccd0$94176670$> <10361_1437568788_55AF8F14_10361_7312_1_9E32478DFA9976438E7A22F69B08FF92166A3977@OPEXCLILMA4.corporate.adroot.infra.ftgroup> <> <etPan.55b0bfb1.9ebecdf.17e@corretto.local> <>
In-Reply-To: <>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
x-originating-ip: []
Content-Type: multipart/alternative; boundary="_000_B8F9A780D330094D99AF023C5877DABA8480F550nkgeml501mbschi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <>
Subject: Re: [L3sm] Comments on draft-ietf-l3sm-l3vpn-service-model
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: L3VPN Service YANG Model discussion group <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 18 Aug 2015 10:37:41 -0000

Not from operators, my take on this is modularization approach is really important for service automation, service agility.
Based on the L3SM prototype demonstrated in Prague Bits-N-Bytes, modular approach enables faster service creation, modification, e.g., we can use site template to create site more quickly,
I am happy to see the new version of draft-ietf-l3sm-l3vpn-service-model get in line with this idea.
In addition, modularization approach can help us to develop other new service model more quickly by reusing common components defined in the existing service model.

发件人: L3sm [] 代表 Scharf, Michael (Michael)
发送时间: 2015年7月23日 18:40
收件人: Rob Shakir; 'Kireeti Kompella';;;
主题: Re: [L3sm] Comments on draft-ietf-l3sm-l3vpn-service-model

Hi Rob,

My understanding is that the abstract L3SM model would be offered by a network management system software. Being in R&D, I mean the software “implementation” of the L3SM model.

I fully agree that deploying a corresponding NMS solution is not trivial, in particular if the network operator’s services change. But I don’t really understand why a more modular abstract service model in L3SM would simplify these challenges. But for these type of questions we would really appreciate input from network service providers.



From: Rob Shakir []
Sent: Thursday, July 23, 2015 12:19 PM
To: 'Kireeti Kompella'; Scharf, Michael (Michael);<>;<>;<>
Subject: Re: [L3sm] Comments on draft-ietf-l3sm-l3vpn-service-model

On 23 July 2015 at 11:15:26, Scharf, Michael (Michael) (<>) wrote:
> > 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.

Can you clarify which implementation you mean here, please? IMHO — there is a set of one off implementation effort to support the model in a network mgmt system - but there is the implementation of changes across a set of services offered by an operator. I expect that more changes happen within the operator’s services (new hardware, new constraints from suppliers or external network dependencies being removed, new customer requirements) than happen for the NMS needing to support different model features (from what I see today), hence, it’d be good to have a debate as to which implementations we want to simplify.

An approach that makes changes to services hard or costly to implement for operators will result in any models produced in the IETF being unusable, or not helping with the current complexities we have.