Re: [L3sm] [l3sm] #19 (draft-ltsd-l3sm-l3vpn-service-model): "site-entrance" and "pop-entrance" Diversity Constraint Augmentation Suggestion
"Ogaki, Kenichi" <ke-oogaki@kddi.com> Fri, 02 September 2016 04:56 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 C7C0C12B02D for <l3sm@ietfa.amsl.com>; Thu, 1 Sep 2016 21:56: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 ar4OifBu_FI9 for <l3sm@ietfa.amsl.com>; Thu, 1 Sep 2016 21:56:52 -0700 (PDT)
Received: from post-send.kddi.com (athena4.kddi.com [27.90.165.197]) by ietfa.amsl.com (Postfix) with ESMTP id 4A0BB128B44 for <l3sm@ietf.org>; Thu, 1 Sep 2016 21:56:52 -0700 (PDT)
Received: from LTMC2122.kddi.com (LTMC2122.kddi.com [10.206.0.63]) by post-send.kddi.com (KDDI Mail) with ESMTP id C4750120037; Fri, 2 Sep 2016 13:56:51 +0900 (JST)
Received: from LTMC2145.kddi.com ([10.206.0.236] [10.206.0.236]) by LTMC2122.kddi.com with ESMTP; Fri, 2 Sep 2016 13:56:51 +0900
Received: from LTMC2145.kddi.com (localhost [127.0.0.1]) by localhost.kddi.com (Postfix) with ESMTP id 9E8073A006B; Fri, 2 Sep 2016 13:56:51 +0900 (JST)
Received: from LTMC2152.kddi.com (post-incheck [10.206.0.239]) by LTMC2145.kddi.com (Postfix) with ESMTP id 937733A0065; Fri, 2 Sep 2016 13:56:51 +0900 (JST)
Received: from LTMC2152.kddi.com (localhost.localdomain [127.0.0.1]) by LTMC2152.kddi.com with ESMTP id u824upft031454; Fri, 2 Sep 2016 13:56:51 +0900
Received: from LTMC2152.kddi.com.mid_4040868 (localhost.localdomain [127.0.0.1]) by LTMC2152.kddi.com with ESMTP id u824kl6a020414; Fri, 2 Sep 2016 13:46:47 +0900
X-SA-MID: 4040868
Received: from KDDI1508PC0003 ([10.200.122.178] [10.200.122.178]) by post-smtp2.kddi.com with ESMTPA; Fri, 2 Sep 2016 13:46:47 +0900
From: "Ogaki, Kenichi" <ke-oogaki@kddi.com>
To: jplandry@bell.ca
References: <056.486ba857b0ae758cc37481d0f72f4105@tools.ietf.org>
In-Reply-To: <056.486ba857b0ae758cc37481d0f72f4105@tools.ietf.org>
Date: Fri, 02 Sep 2016 13:46:47 +0900
Message-ID: <01ea01d204d5$031971b0$094c5510$@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: AQGsrX9nfzSuGSXoD86cHR/lyo2LOKCwTsJQ
Content-Language: ja
X-TM-AS-MML: disable
Archived-At: <https://mailarchive.ietf.org/arch/msg/l3sm/CzqFePAT_ulzZrPAQ7CNg2IhC7Y>
Cc: l3sm@ietf.org
Subject: Re: [L3sm] [l3sm] #19 (draft-ltsd-l3sm-l3vpn-service-model): "site-entrance" and "pop-entrance" 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: Fri, 02 Sep 2016 04:56:54 -0000
Hi, Can this be covered by path diversity described in 5.12.2? I think customers just want to make sure multihomed paths are disjoint, but don't want to care how it is achieved. All the best, Kenichi -----Original Message----- From: L3sm [mailto:l3sm-bounces@ietf.org] On Behalf Of l3sm issue tracker Sent: Thursday, September 01, 2016 6:31 AM To: draft-ltsd-l3sm-l3vpn-service-model@tools.ietf.org; jplandry@bell.ca Cc: l3sm@ietf.org Subject: [L3sm] [l3sm] #19 (draft-ltsd-l3sm-l3vpn-service-model): "site-entrance" and "pop-entrance" Diversity Constraint Augmentation Suggestion #19: "site-entrance" and "pop-entrance" Diversity Constraint Augmentation Suggestion Offering building entrance diversity is a good way to avoid outside plant single point of failures associated to common cable conduits and common access facility routes. Site and POP entrance diversity options are therefore made available to sensitive IP.VPN customers. Recommending to add "site-entrance-diverse" and "pop-entrance-diverse" diversity constraints. -- -------------------------------------+---------------------------------- -------------------------------------+--- 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/19> l3sm <https://tools.ietf.org/l3sm/> _______________________________________________ L3sm mailing list L3sm@ietf.org https://www.ietf.org/mailman/listinfo/l3sm
- [L3sm] [l3sm] #19 (draft-ltsd-l3sm-l3vpn-service-… l3sm issue tracker
- Re: [L3sm] [l3sm] #19 (draft-ltsd-l3sm-l3vpn-serv… Ogaki, Kenichi