Re: [netmod] draft netmod charter update proposal

"Mehmet Ersue" <mersue@gmail.com> Mon, 27 February 2017 20:37 UTC

Return-Path: <mersue@gmail.com>
X-Original-To: netmod@ietfa.amsl.com
Delivered-To: netmod@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8D25F12A31E; Mon, 27 Feb 2017 12:37:34 -0800 (PST)
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, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 FUTd7HhdYOvb; Mon, 27 Feb 2017 12:37:32 -0800 (PST)
Received: from mail-wr0-x235.google.com (mail-wr0-x235.google.com [IPv6:2a00:1450:400c:c0c::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F14A112A329; Mon, 27 Feb 2017 12:37:31 -0800 (PST)
Received: by mail-wr0-x235.google.com with SMTP id l37so16309784wrc.1; Mon, 27 Feb 2017 12:37:31 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:to:cc:references:in-reply-to:subject:date:message-id :mime-version:content-transfer-encoding:thread-index :content-language; bh=/s0F+49qf8CR5TgdisVF5twp5CIcYxuYO15tuvNQaOk=; b=ZZNzFEmZvpxB4X4Cd67ue07Sm3C+4lw3lXEzKd4lPHepg0TGHhuezYWPExWNjqS7KY zxKtO6HTH0FVAcO3Vm43UEyyOlQnlB+LKLVyvZ8xCcm4tWUeEwYnxLArKSmcbB0pNXDz Gc5uwzb//MrW2zsw80uPUUz1E779H6P6TGopuQuzqRqpkFgrh59P+zBNz1+MvSuby9sQ +hnprHWSKxN/v9ToZCsT0iyZY0Y5FuPiyvvSkJ729QXQ8PtkAgNTw6t+7hRv7C9e3mbF XByX4pEmdAr7g1+9ISG6LRi51QB/z6Snj46Niof9veqAX+6Ib4HklJiDgnhjgDGd7RQb 303Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:references:in-reply-to:subject:date :message-id:mime-version:content-transfer-encoding:thread-index :content-language; bh=/s0F+49qf8CR5TgdisVF5twp5CIcYxuYO15tuvNQaOk=; b=umylsJ9J0SGnUwVIVWBvZY8TZharUQc3hb60jHZqf59xgpmSIxxCynIKKosBC1SbjE /R3lc2NQJBV92faqlvITtCif+p4UYvIKBt2klMStE0Us2z1/JC7470Ue1xPdfThWri0/ 5yhAuwhG2fr2f7NU7fVTT/GATfAbJTsr65SFTjtezdeEDbMROie7CXvDDoj3RFiHDC/P GskBFhmsgEgk54U6O/H615RqCToA6ubVO/6UdsX/GMHonGOWzGEW5OwGOwJDQFMHdeK3 zs0Fbwo3ELuitG+N+cSwc+WacuCtbH3NZ7MPYZZqNHVNCRtOJTjtAthds2HD37QqIbuY x5hw==
X-Gm-Message-State: AMke39k6ZPHT/IG2swIghW5dU/WzEhpCjLTFK3+s99tHiTnHdNTN0LZD+MOedOgR4QrQxA==
X-Received: by 10.223.145.193 with SMTP id 59mr16273363wri.82.1488227850307; Mon, 27 Feb 2017 12:37:30 -0800 (PST)
Received: from DESKTOPFLHJVQJ ([46.189.28.73]) by smtp.gmail.com with ESMTPSA id 65sm23644302wri.53.2017.02.27.12.37.28 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 27 Feb 2017 12:37:29 -0800 (PST)
From: Mehmet Ersue <mersue@gmail.com>
To: 'Kent Watsen' <kwatsen@juniper.net>, netmod@ietf.org
References: <B6359563-0649-453A-B29F-28375F2BD3A4@juniper.net>
In-Reply-To: <B6359563-0649-453A-B29F-28375F2BD3A4@juniper.net>
Date: Mon, 27 Feb 2017 21:37:25 +0100
Message-ID: <010b01d29139$4f93dee0$eebb9ca0$@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQH7oic/U5hpx/GFJ0RcyrWSlwEP7qErHE/A
Content-Language: de
X-AVK-Virus-Check: AVA 25.10096;BF82DA0
X-AVK-Spam-Check: 1; str=0001.0A0B0203.58B48E09.0099,ss=1,re=0.000,recu=0.000,reip=0.000,cl=1,cld=1,fgs=0; AE713
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/uw3FmubF_GJtnlSuYMLMUinNARA>
Cc: netmod-chairs@ietf.org
Subject: Re: [netmod] draft netmod charter update proposal
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: NETMOD WG list <netmod.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netmod>, <mailto:netmod-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netmod/>
List-Post: <mailto:netmod@ietf.org>
List-Help: <mailto:netmod-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netmod>, <mailto:netmod-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Feb 2017 20:37:34 -0000

Hi Kent, Lou,

>   c) Maintaining a conceptual framework in which YANG models are used.
>      This effort entails describing the context that network management
>      protocols (e.g., NETCONF, RESTCONF, CoAP, etc.) operate in, and
>      how certain YANG statements interact in that context.

The point above sounds a bit vague and can be interpreted wrongly.
What exactly is meant by "the context that network management protocols
operate in"?

Actually since 2002, NETCONF WG is responsible to specify the configuration
protocols and the context and framework where they operate in.
I assume you rather mean bringing YANG and the protocols using it into
relation or showing how YANG is used together with a protocol, or?
To make it more clear please elaborate what exactly is in-scope and what is
out-of-scope.

We were discussing to specify the YANG language as generic as possible to be
used by many protocols and with this to remove NETCONF specific details.
If this is still the aim, we should add a statement on this.

I have to admit I found the old charter format, where current and planned WG
items are described, as very purposeful.
IOW I am missing a short target description of WG items and how they map to
the high-level descriptions in a)-f).
The draft titles in Milestones are unfortunately not very descriptive.

Thank you for your efforts,
Mehmet

> -----Original Message-----
> From: netmod [mailto:netmod-bounces@ietf.org] On Behalf Of Kent Watsen
> Sent: Thursday, February 23, 2017 1:25 AM
> To: netmod@ietf.org
> Cc: netmod-chairs@ietf.org
> Subject: [netmod] draft netmod charter update proposal
> 
> 
> Hi NETMOD WG,
> 
> Please find below the draft charter update which we provided to our AD for
> review.  Comments are welcomed.  Authors, please note the milestone
> dates.
> 
> Kent (and Lou)
> 
> 
> 
> 
> Network Modeling (NETMOD)
> -------------------------
> 
> Charter
> 
> Current Status: Active
> 
> Chairs:
>    Lou Berger <lberger@labn.net>
>    Kent Watsen <kwatsen@juniper.net>
> 
> Operations and Management Area Directors:
>    Benoit Claise <bclaise@cisco.com>
>    Joel Jaeggli <joelja@bogus.com>
> 
> Operations and Management Area Advisor:
>    Benoit Claise <bclaise@cisco.com>
> 
> Secretary:
>    Zitao (Michael) Wang <wangzitao@huawei.com>
> 
> Mailing Lists:
>    General Discussion: netmod@ietf.org
>    To Subscribe:       https://www.ietf.org/mailman/listinfo/netmod
>    Archive:            https://mailarchive.ietf.org/arch/browse/netmod/
> 
> Description of Working Group:
> 
>    The Network Modeling (NETMOD) working group is responsible for the
> YANG
>    data modeling language, and guidelines for developing YANG models.  The
>    NETMOD working group addresses general topics related to the use of the
>    YANG language and YANG models, for example, the mapping of YANG
> modeled
>    data into various encodings.  Finally, the NETMOD working group also
>    defines core YANG models used as basic YANG building blocks, and YANG
>    models that do not otherwise fall under the charter of any other IETF
>    working group.
> 
> The NETMOD WG is responsible for:
> 
>    a) Maintaining the data modeling language YANG.  This effort entails
>       periodically updating the specification to address new requirements
>       as they arise.
> 
>    b) Maintaining the guidelines for developing YANG models.  This effort
>       is primarily driven by updates made to the YANG specification.
> 
>    c) Maintaining a conceptual framework in which YANG models are used.
>       This effort entails describing the context that network management
>       protocols (e.g., NETCONF, RESTCONF, CoAP, etc.) operate in, and
>       how certain YANG statements interact in that context.
> 
>    d) Maintaining encodings for YANG modeled data.  This effort entails
>       updating encodings already defined by the NETMOD working (XML and
>       JSON) to accommodate changes to the YANG specification, and defining
>       new encodings that are needed and yet do not fall under the charter
>       of any other active IETF working group.
> 
>    e) Maintaining YANG models used as basic YANG building blocks.  This
>       effort entails updating existing YANG models (ietf-yang-types and
>       ietf-inet-types) as needed, as well as defining additional core YANG
>       data models when necessary.
> 
>    f) Defining and maintaining YANG models that do not fall under the
>       charter of any other active IETF working group.
> 
>    The NETMOD working group consults with the NETCONF working group to
>    ensure that new requirements are and understood and can be met by
>    the protocols developed within that working group (e.g., NETCONF
>    and RESTCONF).  The NETMOD working group coordinates with other
>    working groups on possible extensions to YANG to address new modeling
>    requirements and, when needed, which group will run the process on a
>    specific model.
> 
>    The NETMOD working group does not serve as a review team for YANG
>    modules developed by other working groups. Instead, the YANG doctors,
>    as organized by the OPS area director responsible for network
>    management, will act as advisors for other working groups and provide
>    YANG reviews for the OPS area directors.
> 
> Milestones:
> 
>    Done     - Submit draft-ietf-netmod-rfc6087bis to IESG for publication
>    Mar 2016 - Submit draft-ietf-netmod-yang-model-classification to IESG
>               for publication
>    Mar 2016 - Submit draft-ietf-netmod-syslog-model to IESG for
publication
>    Mar 2016 - Submit draft-ietf-netmod-acl-model to IESG for publication
>    Mar 2017 - Submit draft-ietf-netmod-entity to IESG for publication
>    Oct 2017 - Submit draft-ietf-netmod-intf-ext-yang to IESG for
>               publication
>    Oct 2017 - Submit draft-ietf-netmod-schema-mount to IESG for
publication
>    Oct 2017 - Submit draft-ietf-netmod-revised-datastores to IESG for
>               publication
>    Dec 2017 - Submit draft-ietf-netmod-sub-intf-vlan-yang to IESG for
>               publication
> 
> 
> 
> _______________________________________________
> netmod mailing list
> netmod@ietf.org
> https://www.ietf.org/mailman/listinfo/netmod