draft-bogdanovic-netmod-yang-model-classification-03

IETF 92 DallasNETMOD WG

B. Claise, C. Moberg, Cisco SystemsD. Bogdanovic Juniper Networks

Reasons for draft

• YANG becoming de facto standard language for modeling

• Used across the IETF, across SDOs, industry consortiums, open source projects

• Create common nomenclature for classifying models

• Stems from discussion with the YANG Model Coordination Group

First dimension – Layer Model option 1

Metro Ethernet Service(“Business VPN Gold”)

L3 VPN

iBGP MPLS Interface Routing options

Business Service Model(Customer Facing Service, in MEF)Not in YANG - Catalogues

Network Service YANG Model(Resource Facing Service, in MEF)

Configuration Models

Network Element YANG Model

Definitions

• Network Service YANG Model: an abstract view, in YANG, of a service deployed on one or multiple network elements.– Ex: the new L3SM (L3VPN Service Model) WG

• Network Element YANG Model: describe the configuration parameters, in YANG, of a specific device technology or feature.

• Note: in the newly posted v2. An oversight in v1

First dimension – Layer Model option 2

• 5 layer model Metro ethernet service

Pseudowire MPLS L2VPN

iBGP MPLS Interface Routing options

RoutingInstances

Business service model

Network service model

Config models

Pseudowire MPLS RSVP ServiceComponents

Service model

Vendor A Vendor B Vendor CVendor propmodels

Standardmodels

Second dimension – Model Type

Network element

Standard YANG Model

Proprietary extensionto std YANG model

Vendor configuration Model (CLI, YANG, etc)

Proprietary YANGmodel

Standard Extension

How does it fit together?OSS/BSS

Network element

Orchestrator

Service model

Standard YANG Model

Proprietary extto std YANG model

Vendor configuration model

Proprietary YANGmodel

Standard Extension

What’s new in v2

• Definitions addition• Integration of Jürgen S.’ feedback on the

netmod mailing list