IETF Logo Mail Archive

Re: [L3sm] [l3sm] #20 (draft-ltsd-l3sm-l3vpn-service-model): Placement of the management branch

"Ogaki, Kenichi" <ke-oogaki@kddi.com> Fri, 02 September 2016 04:48 UTC

Return-Path: <ke-oogaki@kddi.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 8905312D757 for <l3sm@ietfa.amsl.com>; Thu, 1 Sep 2016 21:48:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.769
X-Spam-Level:
X-Spam-Status: No, score=-4.769 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.548, SPF_PASS=-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 XYmQosBySVBr for <l3sm@ietfa.amsl.com>; Thu, 1 Sep 2016 21:48:52 -0700 (PDT)
Received: from post-send.kddi.com (athena3.kddi.com [27.90.165.196]) by ietfa.amsl.com (Postfix) with ESMTP id 76DED12D1BE for <l3sm@ietf.org>; Thu, 1 Sep 2016 21:48:51 -0700 (PDT)
Received: from LTMC2121.kddi.com (LTMC2121.kddi.com [10.206.0.61]) by post-send.kddi.com (KDDI Mail) with ESMTP id C36FEE006B; Fri, 2 Sep 2016 13:44:51 +0900 (JST)
Received: from LTMC2146.kddi.com ([10.206.0.236] [10.206.0.236]) by LTMC2121.kddi.com with ESMTP; Fri, 2 Sep 2016 13:44:51 +0900
Received: from LTMC2146.kddi.com (localhost [127.0.0.1]) by localhost.kddi.com (Postfix) with ESMTP id 9EDC330005D; Fri, 2 Sep 2016 13:44:51 +0900 (JST)
Received: from LTMC2152.kddi.com (post-incheck [10.206.0.239]) by LTMC2146.kddi.com (Postfix) with ESMTP id 93C43300050; Fri, 2 Sep 2016 13:44:51 +0900 (JST)
Received: from LTMC2152.kddi.com (localhost.localdomain [127.0.0.1]) by LTMC2152.kddi.com with ESMTP id u824ipJR017916; Fri, 2 Sep 2016 13:44:51 +0900
Received: from LTMC2152.kddi.com.mid_4039568 (localhost.localdomain [127.0.0.1]) by LTMC2152.kddi.com with ESMTP id u824YnD3006187; Fri, 2 Sep 2016 13:34:49 +0900
X-SA-MID: 4039568
Received: from KDDI1508PC0003 ([10.200.122.178] [10.200.122.178]) by post-smtp2.kddi.com with ESMTPA; Fri, 2 Sep 2016 13:34:49 +0900
From: "Ogaki, Kenichi" <ke-oogaki@kddi.com>
To: jplandry@bell.ca
References: <056.cd7c7d404d8e791f2e6d82b75ca1dc10@tools.ietf.org>
In-Reply-To: <056.cd7c7d404d8e791f2e6d82b75ca1dc10@tools.ietf.org>
Date: Fri, 02 Sep 2016 13:34:49 +0900
Message-ID: <01d801d204d3$57361b60$05a25220$@kddi.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQLb9mk1524rELOYNSfniPHDpgFv+55Rta3g
Content-Language: ja
X-TM-AS-MML: disable
Archived-At: <https://mailarchive.ietf.org/arch/msg/l3sm/YK58D1w3CmwVkTAfxV-jJfFgV1o>
Cc: l3sm@ietf.org
Subject: Re: [L3sm] [l3sm] #20 (draft-ltsd-l3sm-l3vpn-service-model): Placement of the management branch
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: Fri, 02 Sep 2016 04:48:53 -0000

Hi,

Same comment to issue#15.

All the best,
Kenichi

-----Original Message-----
From: L3sm [mailto:l3sm-bounces@ietf.org] On Behalf Of l3sm issue tracker
Sent: Thursday, September 01, 2016 7:16 AM
To: draft-ltsd-l3sm-l3vpn-service-model@tools.ietf.org; jplandry@bell.ca
Cc: l3sm@ietf.org
Subject: [L3sm] [l3sm] #20 (draft-ltsd-l3sm-l3vpn-service-model): Placement of the management branch

#20: Placement  of  the  management branch

 The following branch (for the CE management) is currently placed under the  site branch.

  +--rw management
  | +--rw type? identityref
  | +--rw management-transport? identityref
  | +--rw address? inet:ip-address

 This is problematic for multi CE multi homed sites.

 Recommending to move this branch under the site-network-access branch.

 While this has the potential to lead to redundant or conflicting data  accros multiple network accesses connected to the same CE, this is  necessary for multi-CE sites.

 Suggestion to avoid redundant or conflictual management info accross same  CE  network accesses would be to make the branch optional and impose on  the management solution to specify the management data on at least one of  the network access connected to any one CE (presumably the first network  access to be installed or the primary network access).

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

Ticket URL: <https://trac.tools.ietf.org/wg/l3sm/trac/ticket/20>
l3sm <https://tools.ietf.org/l3sm/>

_______________________________________________
L3sm mailing list
L3sm@ietf.org
https://www.ietf.org/mailman/listinfo/l3sm

v2.23.0 | Report a Bug | By Email