Re: [6tisch] Attracting your attention on a charter text update

Tom Phinney <tom.phinney@cox.net> Mon, 01 February 2016 15:03 UTC

Return-Path: <tom.phinney@cox.net>
X-Original-To: 6tisch@ietfa.amsl.com
Delivered-To: 6tisch@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 35F481AC3AE for <6tisch@ietfa.amsl.com>; Mon, 1 Feb 2016 07:03:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.878
X-Spam-Level:
X-Spam-Status: No, score=-1.878 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, MIME_HTML_ONLY=0.723, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-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 PAUukkiSrk00 for <6tisch@ietfa.amsl.com>; Mon, 1 Feb 2016 07:03:21 -0800 (PST)
Received: from fed1rmfepo101.cox.net (fed1rmfepo101.cox.net [68.230.241.143]) by ietfa.amsl.com (Postfix) with ESMTP id 001441AC3A7 for <6tisch@ietf.org>; Mon, 1 Feb 2016 07:03:20 -0800 (PST)
Received: from fed1rmimpo210 ([68.230.241.161]) by fed1rmfepo101.cox.net (InterMail vM.8.01.05.15 201-2260-151-145-20131218) with ESMTP id <20160201150320.EHZD331.fed1rmfepo101.cox.net@fed1rmimpo210> for <6tisch@ietf.org>; Mon, 1 Feb 2016 10:03:20 -0500
Received: from [192.168.1.140] ([24.251.82.107]) by fed1rmimpo210 with cox id D33K1s00A2Jw6lk0133K5M; Mon, 01 Feb 2016 10:03:20 -0500
X-CT-Class: Clean
X-CT-Score: 0.00
X-CT-RefID: str=0001.0A020201.56AF73B8.018F,ss=1,re=0.000,fgs=0
X-CT-Spam: 0
X-Authority-Analysis: v=2.0 cv=Hq2o7TvS c=1 sm=1 a=e/RTOH2zQeMkHS+PznmwkA==:17 a=AUd_NHdVAAAA:8 a=48vgC7mUAAAA:8 a=CjxXgO3LAAAA:8 a=wnRk2I__AAAA:8 a=lqxPwJEcJnEOvgBnQfQA:9 a=QEXdDO2ut3YA:10 a=UiCQ7L4-1S4A:10 a=hTZeC7Yk6K0A:10 a=_W_S_7VecoQA:10 a=frz4AuCg-hUA:10 a=nO-W61_XIZ4vfVyg:21 a=XOtUEAfuyqCQ2YWG:21 a=e/RTOH2zQeMkHS+PznmwkA==:117
X-CM-Score: 0.00
Authentication-Results: cox.net; auth=pass (PLAIN) smtp.auth=tom.phinney@cox.net
References: <aaef70cf6bca4fc19ef8b3a20c356e6c@XCH-RCD-001.cisco.com>
To: 6tisch@ietf.org
From: Tom Phinney <tom.phinney@cox.net>
Message-ID: <56AF73B4.6050308@cox.net>
Date: Mon, 1 Feb 2016 08:03:16 -0700
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:38.0) Gecko/20100101 Thunderbird/38.5.1
MIME-Version: 1.0
In-Reply-To: <aaef70cf6bca4fc19ef8b3a20c356e6c@XCH-RCD-001.cisco.com>
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/6tisch/BReuiUi5u4-GRfwLPxtvo1k2m50>
Subject: Re: [6tisch] Attracting your attention on a charter text update
X-BeenThere: 6tisch@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: Tom Phinney <tom.phinney@cox.net>
List-Id: "Discuss link layer model for Deterministic IPv6 over the TSCH mode of IEEE 802.15.4e, and impacts on RPL and 6LoWPAN such as resource allocation" <6tisch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/6tisch>, <mailto:6tisch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/6tisch/>
List-Post: <mailto:6tisch@ietf.org>
List-Help: <mailto:6tisch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/6tisch>, <mailto:6tisch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Feb 2016 15:03:23 -0000

+1
===
On 2016.02.01 07:58, Pascal Thubert (pthubert) wrote:

Dear all:

 

I did not get any comment on the proposed change (below).

I’m willing to assume it’s good news. If you disagree please let it be known now.

Thomas and I will meet this week and conclude.

 

“Produce an Information Model containing the management requirements

of a 6TiSCH node. A data model mapping for an existing protocol (such as Concise

Binary Object Representation (CBOR) over the Constrained Application …”

 

Would become

“Produce a Data Model expressed in YANG and enabling the management

of the 6top sublayer. A mapping for an existing protocol (such as Concise

Binary Object Representation (CBOR) over the Constrained Application …

 

Cheers,

 

Pascal

 

From: 6tisch [mailto:6tisch-bounces@ietf.org] On Behalf Of Pascal Thubert (pthubert)
Sent: vendredi 29 janvier 2016 17:50
To: Qin Wang <qinwang6top@yahoo.com>; Brian Haberman <brian@innovationslab.net>; 6tisch@ietf.org
Subject: Re: [6tisch] information model or data model in the new charter

 

I agree Qin;

 

“Produce an Information Model containing the management requirements

of a 6TiSCH node. A data model mapping for an existing protocol (such as Concise

Binary Object Representation (CBOR) over the Constrained Application …”

 

Would become

“Produce a Data Model expressed in Yand and enabling the management

of the 6top sublayer. A mapping for an existing protocol (such as Concise

Binary Object Representation (CBOR) over the Constrained Application …

 

Note that I reduced the scope of the data model to the 6ttop piece.

 

Is that what we want ?

 

Pascal

 

From: Qin Wang [mailto:qinwang6top@yahoo.com]
Sent: vendredi 29 janvier 2016 16:49
To: Brian Haberman <brian@innovationslab.net>; Pascal Thubert (pthubert) <pthubert@cisco.com>; 6tisch@ietf.org
Subject: Re: [6tisch] information model or data model in the new charter

 

Hi Brain, Pascal and all,

 

I think both what we actually did in the current 6top-interface draft, and what we are going to redo as Thomas and Xavi suggested in the last Webex, are Yang date model of 6top, instead of information model. Thus, I think we need to re-word the Charter accordingly. Make sense? 

 

In addition, the attached file presents clear definition on both interface model and Yang model.

 

Thanks

Qin

 

On Wednesday, January 27, 2016 2:48 PM, Brian Haberman <brian@innovationslab.net> wrote:

 

Hi Pascal,

On 1/27/16 2:38 PM, Pascal Thubert (pthubert) wrote:
> Hello Brian and Qin:
>
> We discussed that at the time of the first charter, using RFC 3444 as
> our reference; it is my understanding that we aimed the 6top
> interface document
> https://tools.ietf.org/html/draft-ietf-6tisch-6top-interface" target="_blank" rel="nofollow"> https://tools.ietf.org/html/draft-ietf-6tisch-6top-interface at
> providing a Yang Data model to manage the 6top layer in a device. It
> is my understanding that some form of information model in natural
> language would be present in the 6top draft, but my reading of the
> 6top interface is that there is some degree of information model
> there too, that explains the data model. If so, is that a problem?

I don't think the problem is in a *document*. Benoit is questioning the
wording of the proposed charter.  I would suggest reviewing his comments
in light of the current wording of the new charter text.

https://datatracker.ietf.org/doc/charter-ietf-6tisch/" target="_blank" rel="nofollow">https://datatracker.ietf.org/doc/charter-ietf-6tisch/
https://datatracker.ietf.org/doc/charter-ietf-6tisch/ballot/#benoit-claise" target="_blank" rel="nofollow">https://datatracker.ietf.org/doc/charter-ietf-6tisch/ballot/#benoit-claise

Regards,


Brian

>
> Cheers,
>
> Pascal
>
>> -----Original Message----- From: 6tisch
>> [mailto:6tisch-bounces@ietf.org] On Behalf Of Brian Haberman Sent:
>> lundi 25 janvier 2016 14:11 To: 6tisch@ietf.org Subject: Re:
>> [6tisch] information model or data model in the new charter
>>
>> Hi Qin,
>>
>> On 1/22/16 3:30 PM, Qin Wang wrote:
>>> Dear all, In today's Webex meeting, we were talking about the
>>> feedback from Bonoit about the new Charter, see [6tisch] Benoit
>>> Claise's No Objection on charter-ietf-6tisch-01-00: (with
>>> COMMENT), and want to continue the discussion in the ML. The
>>> question is what is exactly we want to do with Yang model, and
>>> how to make the paragraph about Yang model in the new Charter
>>> more accurate. Any comments and suggestion is welcome. ThanksQin
>>>
>>
>> This issue needs to get resolved before I will release the charter
>> for external review. Benoit's point illustrated an issue in the
>> charter where it is not clear as to whether the WG is interested in
>> an information model or a data model.
>>
>> Regards, Brian

 

_______________________________________________
6tisch mailing list
6tisch@ietf.org
https://www.ietf.org/mailman/listinfo/6tisch" target="_blank" rel="nofollow">https://www.ietf.org/mailman/listinfo/6tisch

 



_______________________________________________
6tisch mailing list
6tisch@ietf.org
https://www.ietf.org/mailman/listinfo/6tisch" rel="nofollow">https://www.ietf.org/mailman/listinfo/6tisch