Subject: Re: [OPSAWG] New Version Notification for draft-wu-opsawg-service-model-explained-06.txt

From: Qin Wu <[email-masked]>
Date: Fri, 2 Jun 2017 00:26:01 +0000

Update is done, see the diff:
https://www.ietf.org/rfcdiff?url2=draft-wu-opsawg-service-model-explained-06
The main changes are to get aligned with draft-ietf-netmod-yang-model-classification.

-Qin (on behalf of authors)
-----邮件原件-----
发件人: [email-masked] [mailto:[email-masked]] 
发送时间: 2017年5月31日 14:43
收件人: Liushucheng (Will Liu); Liushucheng (Will Liu); Adrian Farrel; Qin Wu
主题: New Version Notification for draft-wu-opsawg-service-model-explained-06.txt

A new version of I-D, draft-wu-opsawg-service-model-explained-06.txt
has been successfully submitted by Adrian Farrel and posted to the IETF repository.

Name:		draft-wu-opsawg-service-model-explained
Revision:	06
Title:		Service Models Explained
Document date:	2017-05-30
Group:		Individual Submission
Pages:		21
URL:            https://www.ietf.org/internet-drafts/draft-wu-opsawg-service-model-explained-06.txt
Status:         https://datatracker.ietf.org/doc/draft-wu-opsawg-service-model-explained/
Htmlized:       https://tools.ietf.org/html/draft-wu-opsawg-service-model-explained-06
Htmlized:       https://datatracker.ietf.org/doc/html/draft-wu-opsawg-service-model-explained-06
Diff:           https://www.ietf.org/rfcdiff?url2=draft-wu-opsawg-service-model-explained-06

Abstract:
   The IETF has produced a considerable number of data modules in the
   YANG modelling language.  The majority of these modules are used to
   construct data models to model devices or monolithic functions and
   they allow access for configuration and to read operational status.

   A small number of YANG modules have been defined to model services
   (for example, the Layer Three Virtual Private Network Service Model
   produced by the L3SM working group and documented in RFC 8049).

   This document briefly sets out the scope of and purpose of an IETF
   service model, and it also shows where a service model might fit into
   a Software Defined Networking architecture.  Note that service models
   do not make any assumption of how a service is actually engineered
   and delivered for a customer; details of how network protocols and
   devices are engineered to deliver a service are captured in other
   models that are not exposed through the Customer-Provider Interface.

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