IETF Logo Mail Archive

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

<stephane.litkowski@orange.com> Thu, 09 July 2015 08:57 UTC

Return-Path: <stephane.litkowski@orange.com>
X-Original-To: l3sm@ietfa.amsl.com
Delivered-To: l3sm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AF5461ACE84 for <l3sm@ietfa.amsl.com>; Thu, 9 Jul 2015 01:57:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, J_CHICKENPOX_12=0.6, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yjnSI60EYX4X for <l3sm@ietfa.amsl.com>; Thu, 9 Jul 2015 01:57:28 -0700 (PDT)
Received: from relais-inet.francetelecom.com (relais-ias91.francetelecom.com [193.251.215.91]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 913771A03A0 for <l3sm@ietf.org>; Thu, 9 Jul 2015 01:57:27 -0700 (PDT)
Received: from omfedm06.si.francetelecom.fr (unknown [xx.xx.xx.2]) by omfedm09.si.francetelecom.fr (ESMTP service) with ESMTP id E16182DC963; Thu, 9 Jul 2015 10:57:25 +0200 (CEST)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [10.114.31.58]) by omfedm06.si.francetelecom.fr (ESMTP service) with ESMTP id BE88627C095; Thu, 9 Jul 2015 10:57:25 +0200 (CEST)
Received: from OPEXCLILMA4.corporate.adroot.infra.ftgroup ([fe80::65de:2f08:41e6:ebbe]) by OPEXCLILM33.corporate.adroot.infra.ftgroup ([fe80::3881:fc15:b4b2:9017%19]) with mapi id 14.03.0235.001; Thu, 9 Jul 2015 10:57:25 +0200
From: stephane.litkowski@orange.com
To: Benoit Claise <bclaise@cisco.com>, "l3sm@ietf.org" <l3sm@ietf.org>
Thread-Topic: [L3sm] draft-ietf-l3sm-l3vpn-service-model feedback
Thread-Index: AQHQt9zbJgN968FJ/Umo9vrv9Ib91J3S2bHQ
Date: Thu, 09 Jul 2015 08:57:24 +0000
Message-ID: <24850_1436432245_559E3775_24850_1614_13_9E32478DFA9976438E7A22F69B08FF921669DB9A@OPEXCLILMA4.corporate.adroot.infra.ftgroup>
References: <559A62ED.9060001@cisco.com>
In-Reply-To: <559A62ED.9060001@cisco.com>
Accept-Language: fr-FR, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.168.234.3]
Content-Type: multipart/alternative; boundary="_000_9E32478DFA9976438E7A22F69B08FF921669DB9AOPEXCLILMA4corp_"
MIME-Version: 1.0
X-PMX-Version: 6.2.1.2478543, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2015.7.2.125417
Archived-At: <http://mailarchive.ietf.org/arch/msg/l3sm/Ft23eXOl72CYQrXWySt9_7jEUT0>
Subject: Re: [L3sm] draft-ietf-l3sm-l3vpn-service-model feedback
X-BeenThere: l3sm@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: L3VPN Service YANG Model discussion group <l3sm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/l3sm>, <mailto:l3sm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/l3sm/>
List-Post: <mailto:l3sm@ietf.org>
List-Help: <mailto:l3sm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/l3sm>, <mailto:l3sm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Jul 2015 08:57:29 -0000

Hi Benoit,

Currently we know that the model maps correctly to a BGP PE-Based VPN, but not sure that it fills any VPN scenario like (CE to CE … ).
When we discussed at the beginning, we agreed to start with this VPN model and then see how it maps to others.

Best Regards,

Stephane


From: L3sm [mailto:l3sm-bounces@ietf.org] On Behalf Of Benoit Claise
Sent: Monday, July 06, 2015 13:14
To: l3sm@ietf.org
Subject: [L3sm] draft-ietf-l3sm-l3vpn-service-model feedback

Dear authors,

Thanks for posting draft-ietf-l3sm-l3vpn-service-model.
From the abstract, I see:

This document defines a YANG data model that can be used to deliver a

Layer 3 Provider Provisioned VPN service.  The document is limited to

the BGP PE-based VPNs as described in RFC4110<https://tools.ietf.org/html/rfc4110> and RFC4364<https://tools.ietf.org/html/rfc4364>.
I wonder:  What is specific to BGP PE-based VPNs in this YANG model?
From the L3SM charter, "Instead it contains the characteristics of the service, as discussed between the operators and their customers."
"Do you want a BGP PE-based VPNs", is this a typical question that operators ask to the customers?

Regards, Benoit

_________________________________________________________________________________________________________________________

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.

v2.23.0 | Report a Bug | By Email