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

Leeyoung <leeyoung@huawei.com> Tue, 25 September 2018 21:57 UTC

Return-Path: <leeyoung@huawei.com>
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 EE7FD130DD0; Tue, 25 Sep 2018 14:57:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.888
X-Spam-Level:
X-Spam-Status: No, score=-1.888 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HK_RANDOM_ENVFROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01, URIBL_BLOCKED=0.001] autolearn=no 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 4idLjAoDNhQ1; Tue, 25 Sep 2018 14:57:53 -0700 (PDT)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (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 89666130DD3; Tue, 25 Sep 2018 14:57:51 -0700 (PDT)
Received: from LHREML713-CAH.china.huawei.com (unknown [172.18.7.107]) by Forcepoint Email with ESMTP id 31B205D51DE5C; Tue, 25 Sep 2018 22:57:46 +0100 (IST)
Received: from SJCEML702-CHM.china.huawei.com (10.208.112.38) by LHREML713-CAH.china.huawei.com (10.201.108.36) with Microsoft SMTP Server (TLS) id 14.3.399.0; Tue, 25 Sep 2018 22:57:47 +0100
Received: from SJCEML521-MBX.china.huawei.com ([169.254.1.47]) by SJCEML702-CHM.china.huawei.com ([169.254.4.89]) with mapi id 14.03.0415.000; Tue, 25 Sep 2018 14:57:41 -0700
From: Leeyoung <leeyoung@huawei.com>
To: Lou Berger <lberger@labn.net>, "draft-lee-teas-te-service-mapping-yang@ietf.org" <draft-lee-teas-te-service-mapping-yang@ietf.org>, "teas@ietf.org" <teas@ietf.org>
Thread-Topic: [Teas] FW: New Version Notification for draft-lee-teas-te-service-mapping-yang-11.txt
Thread-Index: AQHUT4DvIUUaEm799ECmIgSutRIW7KT2YvqwgAuRAAD//6AjsA==
Date: Tue, 25 Sep 2018 21:57:40 +0000
Message-ID: <7AEB3D6833318045B4AE71C2C87E8E173D064FCE@sjceml521-mbx.china.huawei.com>
References: <153729682108.8569.6079760050660778983.idtracker@ietfa.amsl.com> <7AEB3D6833318045B4AE71C2C87E8E173D063DF0@sjceml521-mbx.china.huawei.com> <5d16d8f4-156f-4c6a-5832-08664417aea3@labn.net>
In-Reply-To: <5d16d8f4-156f-4c6a-5832-08664417aea3@labn.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-originating-ip: [10.47.149.52]
Content-Type: multipart/mixed; boundary="_003_7AEB3D6833318045B4AE71C2C87E8E173D064FCEsjceml521mbxchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/H7N5tPuHyD69o5WMLlSm8wWK7Ec>
Subject: Re: [Teas] FW: New Version Notification for draft-lee-teas-te-service-mapping-yang-11.txt
X-BeenThere: teas@ietf.org
X-Mailman-Version: 2.1.29
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, 25 Sep 2018 21:57:57 -0000

Hi Lou,

I think this has been discussed in the mailing list when you asked the opinion on this issue. Please see the attachment. 

Please also refer to the IETF 102 slides (in particular page 3) for further information on this model and why the co-authors think it is beneficial to have a separate model than augmenting three separate service models. 

Thanks.
Young

-----Original Message-----
From: Teas [mailto:teas-bounces@ietf.org] On Behalf Of Lou Berger
Sent: Tuesday, September 25, 2018 3:32 PM
To: draft-lee-teas-te-service-mapping-yang@ietf.org; teas@ietf.org
Subject: Re: [Teas] FW: New Version Notification for draft-lee-teas-te-service-mapping-yang-11.txt

Hi Young/authors,

     Thanks for the update.  I remain a bit confused/concerned that this document adds a new standalone model rather than taking the simpler approach of just augmenting the existing service/connectivity modules with the pointers to the TE/VN/tunnel information (perhaps using
groupings?)

Can you elaborate on your thinking here?

Thanks,
Lou

On 9/18/2018 2:55 PM, Leeyoung wrote:
> Hi,
>
> The revision is to fix YANG errors caused by the L1CSM YANG update. No content changes.
>
> Thanks.
> Young
>
> -----Original Message-----
> From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org]
> Sent: Tuesday, September 18, 2018 1:54 PM
> To: Daniele Ceccarelli <daniele.ceccarelli@ericsson.com>om>; Giuseppe 
> Fioccola <giuseppe.fioccola@telecomitalia.it>it>; Dhruv Dhody 
> <dhruv.ietf@gmail.com>om>; Jeff Tantsura <jefftant@gmail.com>om>; Leeyoung 
> <leeyoung@huawei.com>om>; Qin Wu <bill.wu@huawei.com>
> Subject: New Version Notification for 
> draft-lee-teas-te-service-mapping-yang-11.txt
>
>
> A new version of I-D, draft-lee-teas-te-service-mapping-yang-11.txt
> has been successfully submitted by Young Lee and posted to the IETF repository.
>
> Name:		draft-lee-teas-te-service-mapping-yang
> Revision:	11
> Title:		Traffic Engineering and Service Mapping Yang Model
> Document date:	2018-09-18
> Group:		Individual Submission
> Pages:		22
> URL:            https://www.ietf.org/internet-drafts/draft-lee-teas-te-service-mapping-yang-11.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-11
> 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-11
>
> Abstract:
>     This document provides a YANG data model to map customer service
>     models (e.g., the L3VPM Service Model) to Traffic Engineering (TE)
>     models (e.g., the TE Tunnel or the Abstraction and Control of
>     Traffic Engineered Networks Virtual Network model). This model is
>     referred to as TE Service Mapping Model and is applicable to the
>     operator's need for seamless control and management of their VPN
>     services with TE tunnel support.
>
>     The model is principally used to allow monitoring and diagnostics of
>     the management systems to show how the service requests are mapped
>     onto underlying network resource and TE models.
>
>                                                                                    
>
>
> 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
>
> _______________________________________________
> Teas mailing list
> Teas@ietf.org
> https://www.ietf.org/mailman/listinfo/teas
>

_______________________________________________
Teas mailing list
Teas@ietf.org
https://www.ietf.org/mailman/listinfo/teas
--- Begin Message ---
Hi Lou, Young,

This is an interesting point. The augmentation for LxSM is possible but, in this case, it could not be the right way because it is a less flexible approach. In addition te-topology-ids and te-tp-ids are probably only optional information for the interface between Customer and Service Provider. So, in my opinion, it would be convenient to have a Service Mapping Yang Model.



Thanks,



Giuseppe



Da: Lou Berger [mailto:lberger@labn.net]
Inviato: martedì 1 maggio 2018 15:05
A: Leeyoung; Vishnu Pavan Beeram; teas@ietf.org
Cc: Dhruv Dhody; Fioccola Giuseppe; Jeff Tantsura; Daniele Ceccarelli
Oggetto: Re: New Version Notification for draft-lee-teas-te-service-mapping-yang-07.txt



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> [mailto:internet-drafts@ietf.org]
Sent: Thursday, April 05, 2018 9:43 AM
To: Dhruv Dhody <dhruv.ietf@gmail.com><mailto:dhruv.ietf@gmail.com>; Giuseppe Fioccola <giuseppe.fioccola@telecomitalia.it><mailto:giuseppe.fioccola@telecomitalia.it>; Jeff Tantsura <jefftant@gmail.com><mailto:jefftant@gmail.com>; Daniele Ceccarelli <daniele.ceccarelli@ericsson.com><mailto:daniele.ceccarelli@ericsson.com>; Leeyoung <leeyoung@huawei.com><mailto: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





Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie.

This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks.

Rispetta l'ambiente. Non stampare questa mail se non è necessario.
--- End Message ---