[L3sm] [l3sm] #21 (draft-ltsd-l3sm-l3vpn-service-model): Site-Network-Access bandwidth configuration inheritance challenge
"l3sm issue tracker" <trac+l3sm@tools.ietf.org> Thu, 01 September 2016 02:33 UTC
Return-Path: <trac+l3sm@tools.ietf.org>
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 4C5E812D7B0 for <l3sm@ietfa.amsl.com>; Wed, 31 Aug 2016 19:33:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.448
X-Spam-Level:
X-Spam-Status: No, score=-2.448 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.548] 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 a1tyGA8N78VS for <l3sm@ietfa.amsl.com>; Wed, 31 Aug 2016 19:33:10 -0700 (PDT)
Received: from durif.tools.ietf.org (durif.tools.ietf.org [IPv6:2001:1900:3001:11::3d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CA54D12D513 for <l3sm@ietf.org>; Wed, 31 Aug 2016 19:33:10 -0700 (PDT)
Received: from localhost ([::1]:32931 helo=durif.tools.ietf.org) by durif.tools.ietf.org with esmtp (Exim 4.82_1-5b7a7c0-XX) (envelope-from <trac+l3sm@tools.ietf.org>) id 1bfHoT-0007fL-9Q; Wed, 31 Aug 2016 19:33:09 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: l3sm issue tracker <trac+l3sm@tools.ietf.org>
X-Trac-Version: 0.12.5
Precedence: bulk
Auto-Submitted: auto-generated
X-Mailer: Trac 0.12.5, by Edgewall Software
To: draft-ltsd-l3sm-l3vpn-service-model@tools.ietf.org, jplandry@bell.ca
X-Trac-Project: l3sm
Date: Thu, 01 Sep 2016 02:33:09 -0000
X-URL: https://tools.ietf.org/l3sm/
X-Trac-Ticket-URL: https://trac.tools.ietf.org/wg/l3sm/trac/ticket/21
Message-ID: <056.d450f61ad4842d7e9c5ba7e3a78bc7dc@tools.ietf.org>
X-Trac-Ticket-ID: 21
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: draft-ltsd-l3sm-l3vpn-service-model@tools.ietf.org, jplandry@bell.ca, l3sm@ietf.org
X-SA-Exim-Mail-From: trac+l3sm@tools.ietf.org
X-SA-Exim-Scanned: No (on durif.tools.ietf.org); SAEximRunCond expanded to false
Resent-To: draft-ltsd-l3sm-l3vpn-service-model@ietf.org
Resent-Message-Id: <20160901023310.CA54D12D513@ietfa.amsl.com>
Resent-Date: Wed, 31 Aug 2016 19:33:10 -0700
Resent-From: trac+l3sm@tools.ietf.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/l3sm/yAwiv5YS5tiOS0BUGwGK7iwDyCc>
Cc: l3sm@ietf.org
Subject: [L3sm] [l3sm] #21 (draft-ltsd-l3sm-l3vpn-service-model): Site-Network-Access bandwidth configuration inheritance challenge
X-BeenThere: l3sm@ietf.org
X-Mailman-Version: 2.1.17
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 02:33:12 -0000
#21: Site-Network-Access bandwidth configuration inheritance challenge Section 5.2.1 titled “Site network accesses” stipulates the following: “Some parameters from the site can be configured also at the site- network-access level like : routing, services, security ... Defining parameters only at site level will provide inheritance. If a parameter is configured at both site and access level, the access level parameter MUST override the site level parameter” While this inheritance principle can be desirable for some types of configuration branches (such as security), it can become problematic for configuration parameters such as bandwidth where the properties can be cumulative across multiple accesses. For instance, not specifying bandwidth of a new site network accesses would result in the inheritance principle replicating site level bandwidth specifications for it. This is fine as long as there is only one site network access but it creates ambiguity when there are several ones. In load sharing configurations replicating the site bandwidth specifications like this would acts as a bandwidth multiplier and overturn the likely intent of whoever specified the site bandwidth in the first place. There are also Primary/backup arrangement for which the Primary network access may be capable of handling the full bandwidth specified for the site but for which the backup access is only capable of a fraction of this performance. In all cases, this renders the site network access level override for bandwidth mandatory and the site level bandwidth specifications misleading at best. In a nut shell site to network access inheritance will hardly ever be applicable in multi-access configurations and brings little additional value in single access configurations. Recommendation would be to deprecate site level bandwidth configuration branch and set expectation that management system will be responsible to control explicitly what bandwidth parameter should be enacted for each site network accesses individually and in consideration of the chosen primary/backup or load sharing/balancing scheme. This is a minor point since the capability to override site level settings at the network access level is already present in the model but deprecation of site level bandwidth specification is still recommended because of the ambiguity (confusion) it will generate in multi network access configurations. -- -------------------------------------+------------------------------------- Reporter: jplandry@bell.ca | Owner: draft-ltsd-l3sm-l3vpn- Type: defect | 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/21> l3sm <https://tools.ietf.org/l3sm/>
- [L3sm] [l3sm] #21 (draft-ltsd-l3sm-l3vpn-service-… l3sm issue tracker
- Re: [L3sm] [l3sm] #21 (draft-ltsd-l3sm-l3vpn-serv… stephane.litkowski
- Re: [L3sm] [l3sm] #21 (draft-ltsd-l3sm-l3vpn-serv… Tomotaki, Luis M
- Re: [L3sm] [l3sm] #21 (draft-ltsd-l3sm-l3vpn-serv… Ogaki, Kenichi