[core] ietf-cool YANG module
Andy Bierman <andy@yumaworks.com> Thu, 17 December 2015 02:37 UTC
Return-Path: <andy@yumaworks.com>
X-Original-To: core@ietfa.amsl.com
Delivered-To: core@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CB5C61A0248 for <core@ietfa.amsl.com>; Wed, 16 Dec 2015 18:37:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.278
X-Spam-Level:
X-Spam-Status: No, score=-1.278 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=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 0c9NifHhy4Tm for <core@ietfa.amsl.com>; Wed, 16 Dec 2015 18:37:37 -0800 (PST)
Received: from mail-lf0-x235.google.com (mail-lf0-x235.google.com [IPv6:2a00:1450:4010:c07::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 0148D1A0199 for <core@ietf.org>; Wed, 16 Dec 2015 18:37:36 -0800 (PST)
Received: by mail-lf0-x235.google.com with SMTP id l133so42344271lfd.2 for <core@ietf.org>; Wed, 16 Dec 2015 18:37:36 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yumaworks-com.20150623.gappssmtp.com; s=20150623; h=mime-version:date:message-id:subject:from:to:content-type; bh=XxXZjwbXmKmwkb/4Qu81Ktlh1DokqidXlg9lyf/Nl00=; b=kY0lzqTNpyDLw+T5uEm7eHuJ/B52O6n0e7aG++7eEpQLqURFjVl034RgXNNQfv7urI wqirZFJyXvDpvUJRHek2/VcZk/HzUibZ94t91+d4BdezosUDbAu+MbVVVowQiDcyJT/Q O6MBICFyslz3+0vfzq91tIkm2LXmVeppQ2GquMp0gl6XlvOIQSdBcg2AO+yASQvRVbYa mjfpK6HIH+5gEFy2S6rx86qT0whpEtbewn6FWk0xkXDYtnQccXILlSyvy8bxipKG1Yx0 RcBoJ/mHay3wFGfutYzTruJWfZkcvTJ2MH5WEn4QIRIJPkF+sh0s9s4vH9O75JnX44PX d56Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:date:message-id:subject:from:to :content-type; bh=XxXZjwbXmKmwkb/4Qu81Ktlh1DokqidXlg9lyf/Nl00=; b=Qvr5Tn0QizcEdK07MVQOEiZpJiQ4+vxeWqEkZ5wzsQAnZ7HX3xdAVQJXSm6lHizC28 Wil4YYWCFuqWBKvuzgNIcDAeX0MOW6r9Zs3CyC6jLiCVD0jw4M2ziYBuTv9i7t1k009K kweSmvUs3AaJU3gxdT56rXhxOXYq+a0FfNO7mNxWHlnH3Fban250d353pbzF6FjRQR5E S92C/8Wq1UXDHnMuBygx2g0UlfYuKFiJKTcLqU3LWwcKDlh4zhumSxAqCyvw+8OT6EHL E8gn9T2+kvsrWY2V9oel9u522gy8vhw/CxtArgUdMmxLy7Hg138Jv8daoo0zSu+EJwwe ieJQ==
X-Gm-Message-State: ALoCoQnvRo2oVpaYrl/aVwHnsW+JPqVYPKf+jBbWJfUSF5y+qPGWzF/CWDMUzOPWoIaTttJeTT87WTxFHbSSwC5XPG8uQ/v2TA==
MIME-Version: 1.0
X-Received: by 10.25.155.136 with SMTP id d130mr15677583lfe.54.1450319855082; Wed, 16 Dec 2015 18:37:35 -0800 (PST)
Received: by 10.112.144.36 with HTTP; Wed, 16 Dec 2015 18:37:35 -0800 (PST)
Date: Wed, 16 Dec 2015 18:37:35 -0800
Message-ID: <CABCOCHQN2s7RbNon4kyTfXG8QCFyT+GJZ3CLtm60WCJCCsL2dQ@mail.gmail.com>
From: Andy Bierman <andy@yumaworks.com>
To: Core <core@ietf.org>
Content-Type: multipart/alternative; boundary="001a1140223ec5f9bf05270ee709"
Archived-At: <http://mailarchive.ietf.org/arch/msg/core/LAdKzVYSj66Hg428xtioE4Sr2xM>
Subject: [core] ietf-cool YANG module
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" <core.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/core>, <mailto:core-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/core/>
List-Post: <mailto:core@ietf.org>
List-Help: <mailto:core-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/core>, <mailto:core-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Dec 2015 02:37:39 -0000
Hi, I noticed in this YANG module in draft-veillette-core-cool-00, there are YANG extensions to put the module-id and object IDs in the YANG module. If the numbering comes from these extensions, what is to prevent 2 different modules from assigning the same module-id? I see there is a patch-request and patch-response that look rather similar to the ietf-yang-patch module being developed by the NETCONF WG. There is also an ietf-cool-library module that looks rather similar to the ietf-yang-library module being developed by the NETCONF WG. Neither of these drafts are mentioned anywhere, such as the reference section. Andy
- [core] ietf-cool YANG module Andy Bierman
- Re: [core] ietf-cool YANG module Michel Veillette