Re: [Teas] New Version Notification for draft-lee-teas-te-service-mapping-yang-07.txt

Lou Berger <lberger@labn.net> Tue, 01 May 2018 13:05 UTC

Return-Path: <lberger@labn.net>
X-Original-To: teas@ietfa.amsl.com
Delivered-To: teas@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 77C1412E8AC for <teas@ietfa.amsl.com>; Tue, 1 May 2018 06:05:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.89
X-Spam-Level:
X-Spam-Status: No, score=-1.89 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (768-bit key) header.d=labn.net
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 HHwYS86tYdoL for <teas@ietfa.amsl.com>; Tue, 1 May 2018 06:05:04 -0700 (PDT)
Received: from gproxy2-pub.mail.unifiedlayer.com (gproxy2-pub.mail.unifiedlayer.com [69.89.18.3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B598612E887 for <teas@ietf.org>; Tue, 1 May 2018 06:05:00 -0700 (PDT)
Received: from cmgw12.unifiedlayer.com (unknown [10.9.0.12]) by gproxy2.mail.unifiedlayer.com (Postfix) with ESMTP id 5B5541E0DF3 for <teas@ietf.org>; Tue, 1 May 2018 07:05:00 -0600 (MDT)
Received: from box313.bluehost.com ([69.89.31.113]) by cmsmtp with ESMTP id DUxbfysepogS3DUxbfXQrx; Tue, 01 May 2018 07:04:47 -0600
X-Authority-Reason: nr=8
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=labn.net; s=default; h=Content-Type:In-Reply-To:MIME-Version:Date:Message-ID:From: References:Cc:To:Subject:Sender:Reply-To:Content-Transfer-Encoding:Content-ID :Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To: Resent-Cc:Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe :List-Post:List-Owner:List-Archive; bh=dwolYtwm8sWrudD/w5r9xEi+ocW9ehYIemGSRrx65rg=; b=f2VvSaGk4uAwLcVClaTc0PFV0b 1+acxVPQdxmuN4XoMa51peHhlnAmlrA/1JEA1KybR02cfLRhirWFGJf00CSwTZTCc0ulOcDEZbmBB YjBhSb2K7DvBs9pz0shB4Ut77;
Received: from pool-100-15-86-101.washdc.fios.verizon.net ([100.15.86.101]:46172 helo=[IPv6:::1]) by box313.bluehost.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.89_1) (envelope-from <lberger@labn.net>) id 1fDUxn-001tuN-Uw; Tue, 01 May 2018 07:05:00 -0600
To: Leeyoung <leeyoung@huawei.com>, Vishnu Pavan Beeram <vbeeram@juniper.net>, "teas@ietf.org" <teas@ietf.org>
Cc: Dhruv Dhody <dhruv.ietf@gmail.com>, Giuseppe Fioccola <giuseppe.fioccola@telecomitalia.it>, Jeff Tantsura <jefftant@gmail.com>, Daniele Ceccarelli <daniele.ceccarelli@ericsson.com>
References: <152293940455.26004.8362854609783865293.idtracker@ietfa.amsl.com> <7AEB3D6833318045B4AE71C2C87E8E173CFCD33B@sjceml521-mbs.china.huawei.com>
From: Lou Berger <lberger@labn.net>
Message-ID: <96bad40b-c6af-c8b5-0340-d14947ba3c86@labn.net>
Date: Tue, 01 May 2018 09:04:56 -0400
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0
MIME-Version: 1.0
In-Reply-To: <7AEB3D6833318045B4AE71C2C87E8E173CFCD33B@sjceml521-mbs.china.huawei.com>
Content-Type: multipart/alternative; boundary="------------5C2ED62F9610D9117C3C1A3B"
Content-Language: en-US
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - box313.bluehost.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - labn.net
X-BWhitelist: no
X-Source-IP: 100.15.86.101
X-Exim-ID: 1fDUxn-001tuN-Uw
X-Source:
X-Source-Args:
X-Source-Dir:
X-Source-Sender: pool-100-15-86-101.washdc.fios.verizon.net ([IPv6:::1]) [100.15.86.101]:46172
X-Source-Auth: lberger@labn.net
X-Email-Count: 3
X-Source-Cap: bGFibm1vYmk7bGFibm1vYmk7Ym94MzEzLmJsdWVob3N0LmNvbQ==
X-Local-Domain: yes
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/g1LkYGkN2d3AnSRJswe-6gIukxc>
Subject: Re: [Teas] New Version Notification for draft-lee-teas-te-service-mapping-yang-07.txt
X-BeenThere: teas@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Traffic Engineering Architecture and Signaling working group discussion list <teas.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/teas>, <mailto:teas-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/teas/>
List-Post: <mailto:teas@ietf.org>
List-Help: <mailto:teas-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/teas>, <mailto:teas-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 May 2018 13:05:07 -0000

Hi Young,

see below.

On 4/5/2018 10:57 AM, Leeyoung wrote:
>
> Hi Pavan and Lou,
>
> We have updated the draft to incorporate Pavan's comment (during 
> London meeting) to generalize the model for TE.
>
> Regarding the mapping, we have added options for all three:
>
> -              VN (ACTN VN model)
>
> -              Single abstract node in TE topology (TE-topology model)
>
> -              List of tunnels (TE-tunnel model)
>
> See the changes as follows:
>
>          +---------+ +-------------+         +----------+
>
>          |  L3SM   | <------> | | <-----> | ACTN VN  |
>
>          +---------+          | |         |  Model   |
>
>                               | |         +----------+
>
>                               |             |
>
>          +---------+          | TE-Service |         +----------+
>
>          |  L2SM   | <------> |Mapping Model| <-----> | TE-Topo |
>
>          +---------+          | |         | Model |
>
>                               | |         +----------+
>
>                               |             |
>
>          +---------+          | |         +----------+
>
>          |  L1CSM  | <------> | | <-----> | TE-Tunnel|
>
>          +---------+          | |         | Model |
>
> +-------------+         +----------+
>
> Let us know what you think.
>

I think having a way to map from the LxSMs to  te topology makes a lot 
of sense.  Although, personally I would have looked at augmenting the 
existing models with te-topology-ids and te-tp-ids before defining a new 
module.  This said, what's really important is the opinion of WG 
contributors.  So I'd be more interested in hearing what others think of 
the approach.

Lou

> Best regards,
>
> Young & Dhruv
>
> -----------------------------------------------------------------------------------------------
>
> 4. YANG Data Tree
>
> module: ietf-te-service-mapping
>
>     +--rw te-service-mapping
>
>        +--rw service-mapping
>
>        |  +--rw mapping-list* [map-id]
>
>        |     +--rw map-id uint32
>
>        |     +--rw map-type? map-type
>
>        |     +--rw (service)?
>
>        |     |  +--:(l3vpn)
>
>        |     |  |  +--rw l3vpn-ref?        -> 
> /l3:l3vpn-svc/vpn-services/vpn-
>
> service/vpn-id
>
>        |     |  +--:(l2vpn)
>
>        |     |  |  +--rw l2vpn-ref?        -> 
> /l2:l2vpn-svc/vpn-services/vpn-
>
> service/vpn-id
>
>        |     |  +--:(l1vpn)
>
>        |     |     +--rw l1vpn-ref?        -> /l1:l1cs/service/service-
>
> list/subscriber-l1vc-id
>
>        |     +--rw (te)?
>
>        |        +--:(actn-vn)
>
>        |        |  +--rw actn-vn-ref?      -> /vn:actn/vn/vn-list/vn-id
>
>        |        +--:(te-topo)
>
>        |        |  +--rw vn-topology-id?   te-types:te-topology-id
>
>        |        |  +--rw abstract-node?    -> 
> /nw:networks/network/node/node-
>
> id
>
>        |        +--:(te-tunnel)
>
>        |           +--rw te-tunnel-list*   te:tunnel-ref
>
>        +--rw site-mapping
>
>           +--rw mapping-list* [map-id]
>
>              +--rw map-id         uint32
>
>              +--rw (service)?
>
>              |  +--:(l3vpn)
>
>              |  |  +--rw l3vpn-ref? -> /l3:l3vpn-svc/sites/site/site-id
>
>              |  +--:(l2vpn)
>
>              |  |  +--rw l2vpn-ref? -> /l2:l2vpn-svc/sites/site/site-id
>
>              |  +--:(l1vpn)
>
>              |     +--rw l1vpn-ref? -> /l1:l1cs/access/uni-list/UNI-ID
>
>              +--rw (te)?
>
>                 +--:(actn-vn)
>
>                 |  +--rw actn-vn-ref? -> /vn:actn/ap/access-point-
>
> list/access-point-id
>
>                 +--:(te)
>
>                    +--rw ltp?           te-types:te-tp-id
>
> -----Original Message-----
> From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org]
> Sent: Thursday, April 05, 2018 9:43 AM
> To: Dhruv Dhody <dhruv.ietf@gmail.com>; Giuseppe Fioccola 
> <giuseppe.fioccola@telecomitalia.it>; Jeff Tantsura 
> <jefftant@gmail.com>; Daniele Ceccarelli 
> <daniele.ceccarelli@ericsson.com>; Leeyoung <leeyoung@huawei.com>
> Subject: New Version Notification for 
> draft-lee-teas-te-service-mapping-yang-07.txt
>
> A new version of I-D, draft-lee-teas-te-service-mapping-yang-07.txt
>
> has been successfully submitted by Young Lee and posted to the IETF 
> repository.
>
> Name: draft-lee-teas-te-service-mapping-yang
>
> Revision:              07
>
> Title:                     Traffic Engineering and Service Mapping 
> Yang Model
>
> Document date: 2018-04-05
>
> Group:                  Individual Submission
>
> Pages:                  19
>
> URL: 
> https://www.ietf.org/internet-drafts/draft-lee-teas-te-service-mapping-yang-07.txt
>
> Status: 
> https://datatracker.ietf.org/doc/draft-lee-teas-te-service-mapping-yang/
>
> Htmlized: 
> https://tools.ietf.org/html/draft-lee-teas-te-service-mapping-yang-07
>
> Htmlized: 
> https://datatracker.ietf.org/doc/html/draft-lee-teas-te-service-mapping-yang
>
> Diff: 
> https://www.ietf.org/rfcdiff?url2=draft-lee-teas-te-service-mapping-yang-07
>
> Abstract:
>
>    This document provides a YANG data model to map service model (e.g.,
>
>    L3SM) and Traffic Engineering model (e.g., TE Tunnel or ACTN VN
>
>    model). This model is referred to as TE service Mapping Model. This
>
>    model is applicable to the operation's need for a seamless control
>
>    and management of their VPN services with TE tunnel support.
>
> Please note that it may take a couple of minutes from the time of 
> submission until the htmlized version and diff are available at 
> tools.ietf.org.
>
> The IETF Secretariat
>