IETF Logo Mail Archive

Re: [L3sm] [l3sm] #17 (draft-ltsd-l3sm-l3vpn-service-model): "same-bearer" Diversity Constraint Augmentation Suggestion

<stephane.litkowski@orange.com> Thu, 01 September 2016 14:13 UTC

Return-Path: <stephane.litkowski@orange.com>
X-Original-To: l3sm@ietfa.amsl.com
Delivered-To: l3sm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9354112D9AC for <l3sm@ietfa.amsl.com>; Thu, 1 Sep 2016 07:13:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.619
X-Spam-Level:
X-Spam-Status: No, score=-2.619 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham autolearn_force=no
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 53G-rs8TTz6F for <l3sm@ietfa.amsl.com>; Thu, 1 Sep 2016 07:13:09 -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 412031288B8 for <l3sm@ietf.org>; Thu, 1 Sep 2016 07:05:33 -0700 (PDT)
Received: from omfedm08.si.francetelecom.fr (unknown [xx.xx.xx.4]) by omfedm11.si.francetelecom.fr (ESMTP service) with ESMTP id 828673B43DF; Thu, 1 Sep 2016 16:05:31 +0200 (CEST)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [10.114.31.43]) by omfedm08.si.francetelecom.fr (ESMTP service) with ESMTP id 5350E23808A; Thu, 1 Sep 2016 16:05:31 +0200 (CEST)
Received: from OPEXCLILMA4.corporate.adroot.infra.ftgroup ([fe80::65de:2f08:41e6:ebbe]) by OPEXCLILM5F.corporate.adroot.infra.ftgroup ([fe80::e172:f13e:8be6:71cc%18]) with mapi id 14.03.0301.000; Thu, 1 Sep 2016 16:05:30 +0200
From: stephane.litkowski@orange.com
To: l3sm issue tracker <trac+l3sm@tools.ietf.org>, "draft-ltsd-l3sm-l3vpn-service-model@tools.ietf.org" <draft-ltsd-l3sm-l3vpn-service-model@tools.ietf.org>, "jplandry@bell.ca" <jplandry@bell.ca>
Thread-Topic: [l3sm] #17 (draft-ltsd-l3sm-l3vpn-service-model): "same-bearer" Diversity Constraint Augmentation Suggestion
Thread-Index: AQHSA8dUIC6ZLOI1u0S0SZPsBYAXL6Bkq+uw
Date: Thu, 01 Sep 2016 14:05:29 +0000
Message-ID: <21329_1472738731_57C835AB_21329_102_1_9E32478DFA9976438E7A22F69B08FF921BD64363@OPEXCLILMA4.corporate.adroot.infra.ftgroup>
References: <056.0784c93ab4676c4c5c11e72be433440a@tools.ietf.org>
In-Reply-To: <056.0784c93ab4676c4c5c11e72be433440a@tools.ietf.org>
Accept-Language: fr-FR, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.168.234.1]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-PMX-Version: 6.2.1.2478543, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2016.6.17.114517
Archived-At: <https://mailarchive.ietf.org/arch/msg/l3sm/F57tSWY2VohaOHHk49qKUv4KXo8>
Cc: "l3sm@ietf.org" <l3sm@ietf.org>
Subject: Re: [L3sm] [l3sm] #17 (draft-ltsd-l3sm-l3vpn-service-model): "same-bearer" Diversity Constraint Augmentation Suggestion
X-BeenThere: l3sm@ietf.org
X-Mailman-Version: 2.1.17
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, 01 Sep 2016 14:13:16 -0000

Hi,

Having parallel links attached with different bearers to the same PE is achievable using "same-pe" constraint. It is detailed in 5.5.5.3.
Does it fit your requirement ?

Brgds,

Stephane

-----Original Message-----
From: l3sm issue tracker [mailto:trac+l3sm@tools.ietf.org] 
Sent: Wednesday, August 31, 2016 22:36
To: draft-ltsd-l3sm-l3vpn-service-model@tools.ietf.org; jplandry@bell.ca
Cc: l3sm@ietf.org
Subject: [l3sm] #17 (draft-ltsd-l3sm-l3vpn-service-model): "same-bearer" Diversity Constraint Augmentation Suggestion

#17: "same-bearer"  Diversity Constraint  Augmentation Suggestion

 Assuming "same-bearer" diversity constraint is meant for making sure that  logical interfaces (such as sub-interfaces, TDM channels, Vlans, PVCs,  etc. ) can be consolidated on a common physical (bearer) access (cost  saving measure), it would also be logical to allow diverse bearer  specification considering these logical access are often meant to be used  in Primary/Backup arrangements. Recommending to add bearer-diverse  constraint.

-- 
-------------------------------------+----------------------------------
-------------------------------------+---
 Reporter:  jplandry@bell.ca         |      Owner:  draft-ltsd-l3sm-l3vpn-
     Type:  enhancement              |  service-model@tools.ietf.org
 Priority:  minor                    |     Status:  new
Component:  draft-ltsd-l3sm-l3vpn-   |  Milestone:
  service-model                      |    Version:
 Severity:  -                        |   Keywords:
-------------------------------------+----------------------------------
-------------------------------------+---

Ticket URL: <https://trac.tools.ietf.org/wg/l3sm/trac/ticket/17>
l3sm <https://tools.ietf.org/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.

v2.23.0 | Report a Bug | By Email