Re: [OPSAWG] New Version Notification for draft-shytyi-opsawg-vysm-01.txt

Dmytro Shytyi <ietf.dmytro@shytyi.net> Mon, 30 September 2019 21:17 UTC

Return-Path: <ietf.dmytro@shytyi.net>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BF7AA120866 for <opsawg@ietfa.amsl.com>; Mon, 30 Sep 2019 14:17:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=shytyi.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 eiXjnWwc7PjP for <opsawg@ietfa.amsl.com>; Mon, 30 Sep 2019 14:17:44 -0700 (PDT)
Received: from sender-of-o52.zoho.eu (sender-of-o52.zoho.eu [31.186.226.248]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D270D120820 for <opsawg@ietf.org>; Mon, 30 Sep 2019 14:17:43 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; t=1569878261; cv=none; d=zohomail.eu; s=zohoarc; b=SDY1KS2fbu7S2dkMANs87/RXRxfFVvUNmtmVVyAUW33zAY4ufm4QyyPWF902+qORMUI529JnBJIwXU+X4J9dKnx8vn2HZ4nMxIlBrHLB1jfZOr4FAYokGqxiFaUyPx13XG4BK8ufgZgxXerACPCz3kyZaaR7ADmDLhvGGunxfbw=
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=zohomail.eu; s=zohoarc; t=1569878261; h=Content-Type:Date:From:In-Reply-To:MIME-Version:Message-ID:References:Subject:To:ARC-Authentication-Results; bh=e1r5DnkVM2jtVmK1Xt2ScLXL0MsupKsCGNx3cHCyGqo=; b=XiVUO9KyVU2xsS47LVwwuB8H9vtdeT0jX0Qh/OBJvdo92sRP1hPGViCn0c7IY3WDhqJqB0YYt7lz90EjtXab0v/OZM4bF0BGcRdQgZPmsnS73y5UzQb5v+mZMARyorXYCQKli2No/2oQ2tu9DuSCGkv72XdFOQsC0LyMqh7Xgg8=
ARC-Authentication-Results: i=1; mx.zohomail.eu; dkim=pass header.i=shytyi.net; spf=pass smtp.mailfrom=ietf.dmytro@shytyi.net; dmarc=pass header.from=<ietf.dmytro@shytyi.net> header.from=<ietf.dmytro@shytyi.net>
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; t=1569878261; s=hs; d=shytyi.net; i=ietf.dmytro@shytyi.net; h=Date:From:To:Message-Id:In-Reply-To:References:Subject:MIME-Version:Content-Type; l=7194; bh=e1r5DnkVM2jtVmK1Xt2ScLXL0MsupKsCGNx3cHCyGqo=; b=GCxQEpog/bEyH0cQymohiem1L7VCo3Dt0+r89VNAp632MR+dx9Iz2qjE/TUWHOjs QYW/BH+9rsPcd/u/g4i0tEfUcfNOPvczLcx9GAdc81Ys+fky1hcZjjuNYVMvIt/dRDz M8+aiiBDK5OT1n9nzc/vgXZrz4b5rt7FyMNJyI2U=
Received: from sender11-op-o13.zoho.eu (172.26.23.78 [172.26.23.78]) by mx.zoho.eu with SMTPS id 1569878261016193.77500362674596; Mon, 30 Sep 2019 23:17:41 +0200 (CEST)
Received: from mail.zoho.eu by mx.zoho.eu with SMTP id 1569878260944603.9300991284823; Mon, 30 Sep 2019 23:17:40 +0200 (CEST)
Date: Mon, 30 Sep 2019 23:17:40 +0200
From: Dmytro Shytyi <ietf.dmytro@shytyi.net>
To: opsawg <opsawg@ietf.org>
Message-Id: <16d84093cce.ee0812ef90680.2305940374257745327@shytyi.net>
In-Reply-To: <156951367490.6064.12121507008039737808.idtracker@ietfa.amsl.com>
References: <156951367490.6064.12121507008039737808.idtracker@ietfa.amsl.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_Part_256699_1680275793.1569878260942"
X-Priority: Medium
User-Agent: Zoho Mail
X-Mailer: Zoho Mail
X-ZohoMailClient: External
Archived-At: <https://mailarchive.ietf.org/arch/msg/opsawg/ndquOXrcNI1rr_lw9iwrCxY4nyg>
Subject: Re: [OPSAWG] New Version Notification for draft-shytyi-opsawg-vysm-01.txt
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsawg/>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 30 Sep 2019 21:17:50 -0000

Dear members of opsawg,



Recently we uploaded a draft about uCPE management. 


You are invited to answer few questions regarding the draft https://www.ietf.org/internet-drafts/draft-shytyi-opsawg-vysm-01.txt.


Question1: Do you find a difinition of uCPE is well explained? If no what could be improved?

      You may answer: I agree with definition. OR I think it could be modified...

Question2: Do you think there is enough examples of internal uCPE service and usecases that are well depicted.

      You may answer: The examples and usecases are well explained. OR The usecases need improvements.


Question3: Do you find that yang model should stay unchanged regarding the phy interfaces. Maybe one may think about "ietf interface" instead of  "phyInterface". 

      You may answer: The yang model looks good for me. OR The yang model needs more improvements(which improvements).



______________

Best Regards,
Dmytro SHYTYI






---- On Thu, 26 Sep 2019 18:01:14 +0200  <internet-drafts@ietf.org> wrote ----




A new version of I-D, draft-shytyi-opsawg-vysm-01.txt 
has been successfully submitted by Dmytro Shytyi and posted to the 
IETF repository. 
 
Name:        draft-shytyi-opsawg-vysm 
Revision:    01 
Title:        A YANG Module for uCPE management. 
Document date:    2019-09-26 
Group:        Individual Submission 
Pages:        15 
URL: https://www.ietf.org/internet-drafts/draft-shytyi-opsawg-vysm-01.txt 
Status: https://datatracker.ietf.org/doc/draft-shytyi-opsawg-vysm/ 
Htmlized: https://tools.ietf.org/html/draft-shytyi-opsawg-vysm-01 
Htmlized: https://datatracker.ietf.org/doc/html/draft-shytyi-opsawg-vysm 
Diff: https://www.ietf.org/rfcdiff?url2=draft-shytyi-opsawg-vysm-01 
 
Abstract: 
 This document provides a YANG data model for uCPE management (VYSM) 
 and definition of the uCPE equipment.  The YANG Service Model serves 
 as a base framework for managing an universal Customer-Premises 
 Equipment (uCPE) subsystem.  The model can be used by a Network 
 Service Orchestrator. 
 
 
 
 
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