From dromasca@avaya.com Tue Oct 1 01:25:16 2013 Return-Path: X-Original-To: coman@ietfa.amsl.com Delivered-To: coman@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9990721F8FF5; Tue, 1 Oct 2013 01:25:14 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -103.313 X-Spam-Level: X-Spam-Status: No, score=-103.313 tagged_above=-999 required=5 tests=[AWL=0.286, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Rb4L5rYDrjxL; Tue, 1 Oct 2013 01:25:08 -0700 (PDT) Received: from de307622-de-outbound.net.avaya.com (de307622-de-outbound.net.avaya.com [198.152.71.100]) by ietfa.amsl.com (Postfix) with ESMTP id DED2821F9048; Tue, 1 Oct 2013 01:25:03 -0700 (PDT) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: ArIQAL+FSlLGmAcV/2dsb2JhbABagmYhOFKsNAeUR4EyFnSCJQEBAQEDEig/DAQCAQgNAQIBBAEBAQoUCQcyFAkIAgQOBQgTB4dkAQuff5x+jhiBCDEHBoMZgQMDlCKFDIUriyCBZoE+gXE5 X-IronPort-AV: E=Sophos;i="4.90,1012,1371096000"; d="scan'208";a="26041433" Received: from unknown (HELO co300216-co-erhwest-exch.avaya.com) ([198.152.7.21]) by de307622-de-outbound.net.avaya.com with ESMTP; 01 Oct 2013 04:25:01 -0400 Received: from unknown (HELO AZ-FFEXHC02.global.avaya.com) ([135.64.58.12]) by co300216-co-erhwest-out.avaya.com with ESMTP; 01 Oct 2013 04:21:13 -0400 Received: from AZ-FFEXMB04.global.avaya.com ([fe80::6db7:b0af:8480:c126]) by AZ-FFEXHC02.global.avaya.com ([135.64.58.12]) with mapi id 14.03.0146.000; Tue, 1 Oct 2013 10:24:35 +0200 From: "Romascanu, Dan (Dan)" To: Juergen Schoenwaelder Thread-Topic: [6lo] [coman] WG Review: IPv6 over Networks of Resource-constrained Nodes (6lo) Thread-Index: AQHOvdTOAEmpif1hakuifQIFMI1uLJnfgvhg Date: Tue, 1 Oct 2013 08:24:35 +0000 Message-ID: <9904FB1B0159DA42B0B887B7FA8119CA128EE229@AZ-FFEXMB04.global.avaya.com> References: <20130923180202.32168.94377.idtracker@ietfa.amsl.com> <9904FB1B0159DA42B0B887B7FA8119CA128E75E5@AZ-FFEXMB04.global.avaya.com> <52419692.7050903@cisco.com> <20130924134921.GA19673@elstar.local> <52419C92.9040807@cisco.com> <20130926132817.GB25326@elstar.local> <9904FB1B0159DA42B0B887B7FA8119CA128E9913@AZ-FFEXMB04.global.avaya.com> <20130926215221.GA26059@elstar.local> <9904FB1B0159DA42B0B887B7FA8119CA128E9DF0@AZ-FFEXMB04.global.avaya.com> <20130930120122.GC7925@elstar.local> In-Reply-To: <20130930120122.GC7925@elstar.local> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [135.64.58.45] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: Benoit Claise , "coman@ietf.org" , The IESG , 6lo WG <6lo@ietf.org> Subject: Re: [coman] [6lo] WG Review: IPv6 over Networks of Resource-constrained Nodes (6lo) X-BeenThere: coman@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Management of Constrained Networks and Devices List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Oct 2013 08:25:17 -0000 > -----Original Message----- > From: Juergen Schoenwaelder [mailto:j.schoenwaelder@jacobs- > university.de] > Sent: Monday, September 30, 2013 3:01 PM > To: Romascanu, Dan (Dan) > Cc: Benoit Claise; coman@ietf.org; The IESG; 6lo WG > Subject: Re: [6lo] [coman] WG Review: IPv6 over Networks of Resource- > constrained Nodes (6lo) >=20 > On Fri, Sep 27, 2013 at 02:37:57PM +0000, Romascanu, Dan (Dan) wrote: > > Hi Juergen, > > > > I believe that what would not be useful is to be vague in the charter > about what the WG must develop as part of its 'contract' with the IESG. > > > > My proposal was based on what you wrote in your previous mail: > > > > > One more time: The goal here is to define the number and the > > > semantics of the counters that need to implemented in the 6LoWPAN > > > layer in order to enable basic monitoring and troubleshooting. The > > > formalism we have (as a standard) for that are MIB modules. > > > > Are now saying that the goal of the WG is not to define only the > 'number and semantics of the counters' but actually the data model > itself? Then Let us say it. I suggest: > > > > - MIB module for the counters in the 6LoWPAN layer for basic > > monitoring and troubleshooting > > > > We should avoid just saying 'MIB module' because this is too vague, > and also we should not imply that this is necessarily the full > management solution because it seems that the discussion about what is > the management solution did not yet happen in the WG. > > >=20 > Apparently some prefer a more open ended charter while others prefer a > strict charter. It will at the end be the IESG's job to define what the > IESG prefers. >=20 > If a strict charter is called for, then replacing >=20 > Related MIB modules >=20 > with >=20 > MIB module for the counters in the 6LoWPAN layer for basic monitoring > and troubleshooting >=20 > is certainly fine with me. >=20 > For those interested in a YANG model or a way to transport SMIv2 MIB > defined counters over CoAP, please read Appendix A: >=20 > http://tools.ietf.org/html/draft-schoenw-6lowpan-mib-03#appendix-A >=20 > Following RFC 6643, a read-only MIB modules already translates into a > YANG module and this may lead to a JSON representation (although this > serialization of YANG defined data trees into JSON is at this point > unchartered work). >=20 > /js >=20 > PS: 6LoWPAN does not exist in isolation. There are further counters > devices should support such as basic interface in/out counters or > counters in the IPv6 layer. All these counters and their semantics > are defined today in SMIv2 MIB modules. Hence, it seems quite > reasonable to me to use the same formalism also for the 6LoWPAN > layer. >=20 [[DR]] I agree with the argument made by Juergen in the PS. My personal pre= ference is for a 'strict' charter wording for this WG for the development o= f the MIB module and a separate discussion (here or some place else) about = the broader aspects of management of resource-constrained nodes.=20 Regards, Dan From joelja@bogus.com Wed Oct 2 09:38:24 2013 Return-Path: X-Original-To: coman@ietfa.amsl.com Delivered-To: coman@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2548721F9E85; Wed, 2 Oct 2013 09:38:24 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.599 X-Spam-Level: X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7C5NFmkMg1wX; Wed, 2 Oct 2013 09:38:17 -0700 (PDT) Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id A982221F991F; Wed, 2 Oct 2013 09:36:48 -0700 (PDT) Received: from [10.101.216.53] ([199.48.105.4]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id r92GahNi027763 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Wed, 2 Oct 2013 16:36:44 GMT (envelope-from joelja@bogus.com) Content-Type: multipart/signed; boundary="Apple-Mail=_A33BAAE3-9FF5-44C3-8AFE-E1075D2D16BA"; protocol="application/pgp-signature"; micalg=pgp-sha1 Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\)) From: joel jaeggli In-Reply-To: <20130930120122.GC7925@elstar.local> Date: Wed, 2 Oct 2013 09:36:39 -0700 Message-Id: References: <20130923180202.32168.94377.idtracker@ietfa.amsl.com> <9904FB1B0159DA42B0B887B7FA8119CA128E75E5@AZ-FFEXMB04.global.avaya.com> <52419692.7050903@cisco.com> <20130924134921.GA19673@elstar.local> <52419C92.9040807@cisco.com> <20130926132817.GB25326@elstar.local> <9904FB1B0159DA42B0B887B7FA8119CA128E9913@AZ-FFEXMB04.global.avaya.com> <20130926215221.GA26059@elstar.local> <9904FB1B0159DA42B0B887B7FA8119CA128E9DF0@AZ-FFEXMB04.global.avaya.com> <20130930120122.GC7925@elstar.local> To: Juergen Schoenwaelder X-Mailer: Apple Mail (2.1510) X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (nagasaki.bogus.com [147.28.0.81]); Wed, 02 Oct 2013 16:36:44 +0000 (UTC) Cc: Benoit Claise , "Romascanu, Dan \(Dan\)" , "coman@ietf.org" , The IESG , 6lo WG <6lo@ietf.org> Subject: Re: [coman] [6lo] WG Review: IPv6 over Networks of Resource-constrained Nodes (6lo) X-BeenThere: coman@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Management of Constrained Networks and Devices List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Oct 2013 16:38:24 -0000 --Apple-Mail=_A33BAAE3-9FF5-44C3-8AFE-E1075D2D16BA Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii On Sep 30, 2013, at 5:01 AM, Juergen Schoenwaelder = wrote: > On Fri, Sep 27, 2013 at 02:37:57PM +0000, Romascanu, Dan (Dan) wrote: >> Hi Juergen, >>=20 >> I believe that what would not be useful is to be vague in the charter = about what the WG must develop as part of its 'contract' with the IESG.=20= >>=20 >> My proposal was based on what you wrote in your previous mail:=20 >>=20 >>> One more time: The goal here is to define the number and the = semantics=20 >>> of the counters that need to implemented in the 6LoWPAN layer in = order=20 >>> to enable basic monitoring and troubleshooting. The formalism we = have=20 >>> (as a standard) for that are MIB modules. >>=20 >> Are now saying that the goal of the WG is not to define only the = 'number and semantics of the counters' but actually the data model = itself? Then Let us say it. I suggest:=20 >>=20 >> - MIB module for the counters in the 6LoWPAN layer for basic = monitoring and troubleshooting >>=20 >> We should avoid just saying 'MIB module' because this is too vague, = and also we should not imply that this is necessarily the full = management solution because it seems that the discussion about what is = the management solution did not yet happen in the WG.=20 >>=20 >=20 > Apparently some prefer a more open ended charter while others prefer a > strict charter. It will at the end be the IESG's job to define what > the IESG prefers. >=20 > If a strict charter is called for, then replacing >=20 > Related MIB modules >=20 > with >=20 > MIB module for the counters in the 6LoWPAN layer for basic monitoring > and troubleshooting >=20 So, I'm of the opinion that the question isn't strict or open charter = but rather that most work in this space doesn't use snmp for = configuration, just instrumentation and that doesn't seem likely to = change. I like that text btw. > is certainly fine with me. >=20 > For those interested in a YANG model or a way to transport SMIv2 MIB > defined counters over CoAP, please read Appendix A: >=20 > http://tools.ietf.org/html/draft-schoenw-6lowpan-mib-03#appendix-A >=20 > Following RFC 6643, a read-only MIB modules already translates into a > YANG module and this may lead to a JSON representation (although this > serialization of YANG defined data trees into JSON is at this point > unchartered work). >=20 > /js >=20 > PS: 6LoWPAN does not exist in isolation. There are further counters > devices should support such as basic interface in/out counters or > counters in the IPv6 layer. All these counters and their semantics > are defined today in SMIv2 MIB modules. Hence, it seems quite > reasonable to me to use the same formalism also for the 6LoWPAN > layer. yes they are and imho it does as well. >=20 > --=20 > Juergen Schoenwaelder Jacobs University Bremen gGmbH > Phone: +49 421 200 3587 Campus Ring 1, 28759 Bremen, Germany > Fax: +49 421 200 3103 >=20 --Apple-Mail=_A33BAAE3-9FF5-44C3-8AFE-E1075D2D16BA Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Comment: GPGTools - http://gpgtools.org iEYEARECAAYFAlJMS5cACgkQ8AA1q7Z/VrL+4wCeNM7GpEDD4ONv4woCBw1fU/W+ RTQAn25tpBfVFytR941obyhvnqHaTYLu =R/0r -----END PGP SIGNATURE----- --Apple-Mail=_A33BAAE3-9FF5-44C3-8AFE-E1075D2D16BA-- From Randy.Turner@landisgyr.com Wed Oct 2 10:03:06 2013 Return-Path: X-Original-To: coman@ietfa.amsl.com Delivered-To: coman@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5658021F9D7E; Wed, 2 Oct 2013 10:03:06 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.599 X-Spam-Level: X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2pRZ-4VLHPmu; Wed, 2 Oct 2013 10:02:52 -0700 (PDT) Received: from emea01-db3-obe.outbound.protection.outlook.com (mail-db3lp0076.outbound.protection.outlook.com [213.199.154.76]) by ietfa.amsl.com (Postfix) with ESMTP id 9207C21F9DC9; Wed, 2 Oct 2013 09:59:58 -0700 (PDT) Received: from DB3PR01MB011.eurprd01.prod.exchangelabs.com (10.255.177.37) by DB3PR01MB012.eurprd01.prod.exchangelabs.com (10.255.177.38) with Microsoft SMTP Server (TLS) id 15.0.775.9; Wed, 2 Oct 2013 16:59:46 +0000 Received: from DB3PR01MB011.eurprd01.prod.exchangelabs.com ([169.254.5.34]) by DB3PR01MB011.eurprd01.prod.exchangelabs.com ([169.254.5.34]) with mapi id 15.00.0775.005; Wed, 2 Oct 2013 16:59:46 +0000 From: "Turner, Randy" To: "coman@ietf.org" , "6lo@ietf.org" <6lo@ietf.org> Thread-Topic: [coman] [6lo] WG Review: IPv6 over Networks of Resource-constrained Nodes (6lo) Thread-Index: AQHOv43lR2J+IunCkkqsk9wPZ8zbIZnhoNvA Date: Wed, 2 Oct 2013 16:59:45 +0000 Message-ID: References: <20130923180202.32168.94377.idtracker@ietfa.amsl.com> <9904FB1B0159DA42B0B887B7FA8119CA128E75E5@AZ-FFEXMB04.global.avaya.com> <52419692.7050903@cisco.com> <20130924134921.GA19673@elstar.local> <52419C92.9040807@cisco.com> <20130926132817.GB25326@elstar.local> <9904FB1B0159DA42B0B887B7FA8119CA128E9913@AZ-FFEXMB04.global.avaya.com> <20130926215221.GA26059@elstar.local> <9904FB1B0159DA42B0B887B7FA8119CA128E9DF0@AZ-FFEXMB04.global.avaya.com> <20130930120122.GC7925@elstar.local> In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [148.80.255.144] x-forefront-prvs: 0987ACA2E2 x-forefront-antispam-report: SFV:NSPM; SFS:(24454002)(377454003)(13464003)(51704005)(189002)(199002)(77096001)(76482001)(74316001)(31966008)(81542001)(56816003)(69226001)(76786001)(74706001)(66066001)(15975445006)(83072001)(74502001)(80022001)(47446002)(74366001)(80976001)(53806001)(74876001)(15202345003)(81816001)(81342001)(74662001)(54316002)(79102001)(4396001)(81686001)(54356001)(77982001)(59766001)(46102001)(561944002)(19580395003)(19580405001)(83322001)(65816001)(47976001)(51856001)(50986001)(63696002)(56776001)(76796001)(33646001)(49866001)(47736001)(85306001)(24736002); DIR:OUT; SFP:; SCL:1; SRVR:DB3PR01MB012; H:DB3PR01MB011.eurprd01.prod.exchangelabs.com; CLIP:148.80.255.144; FPR:; RD:InfoNoRecords; MX:1; A:1; LANG:en; Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-OriginatorOrg: landisgyr.com Subject: Re: [coman] [6lo] WG Review: IPv6 over Networks of Resource-constrained Nodes (6lo) X-BeenThere: coman@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Management of Constrained Networks and Devices List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Oct 2013 17:03:06 -0000 I agree with Juergen's earlier comments regarding the use of SMIv2 -- seems= like we would want to keep the same way of describing our data model. But= I would probably go a bit further. I would pursue SMIv2/SNMP as a management infrastructure, and later, if som= ething better comes along, someone can propose that. SNMP management inf= rastructures (management stations, etc) are likely to be what we run into f= or managed LLNs, it would be nice if we what we come up with can play in th= ose environments, without any loss of semantics or functionality. Randy -----Original Message----- From: coman-bounces@ietf.org [mailto:coman-bounces@ietf.org] On Behalf Of j= oel jaeggli Sent: Wednesday, October 02, 2013 12:37 PM To: Juergen Schoenwaelder Cc: Benoit Claise; Romascanu, Dan (Dan); coman@ietf.org; The IESG; 6lo WG Subject: Re: [coman] [6lo] WG Review: IPv6 over Networks of Resource-constr= ained Nodes (6lo) On Sep 30, 2013, at 5:01 AM, Juergen Schoenwaelder wrote: > On Fri, Sep 27, 2013 at 02:37:57PM +0000, Romascanu, Dan (Dan) wrote: >> Hi Juergen, >> >> I believe that what would not be useful is to be vague in the charter ab= out what the WG must develop as part of its 'contract' with the IESG. >> >> My proposal was based on what you wrote in your previous mail: >> >>> One more time: The goal here is to define the number and the >>> semantics of the counters that need to implemented in the 6LoWPAN >>> layer in order to enable basic monitoring and troubleshooting. The >>> formalism we have (as a standard) for that are MIB modules. >> >> Are now saying that the goal of the WG is not to define only the 'number= and semantics of the counters' but actually the data model itself? Then Le= t us say it. I suggest: >> >> - MIB module for the counters in the 6LoWPAN layer for basic >> monitoring and troubleshooting >> >> We should avoid just saying 'MIB module' because this is too vague, and = also we should not imply that this is necessarily the full management solut= ion because it seems that the discussion about what is the management solut= ion did not yet happen in the WG. >> > > Apparently some prefer a more open ended charter while others prefer a > strict charter. It will at the end be the IESG's job to define what > the IESG prefers. > > If a strict charter is called for, then replacing > > Related MIB modules > > with > > MIB module for the counters in the 6LoWPAN layer for basic monitoring > and troubleshooting > So, I'm of the opinion that the question isn't strict or open charter but r= ather that most work in this space doesn't use snmp for configuration, just= instrumentation and that doesn't seem likely to change. I like that text btw. > is certainly fine with me. > > For those interested in a YANG model or a way to transport SMIv2 MIB > defined counters over CoAP, please read Appendix A: > > http://tools.ietf.org/html/draft-schoenw-6lowpan-mib-03#appendix-A > > Following RFC 6643, a read-only MIB modules already translates into a > YANG module and this may lead to a JSON representation (although this > serialization of YANG defined data trees into JSON is at this point > unchartered work). > > /js > > PS: 6LoWPAN does not exist in isolation. There are further counters > devices should support such as basic interface in/out counters or > counters in the IPv6 layer. All these counters and their semantics > are defined today in SMIv2 MIB modules. Hence, it seems quite > reasonable to me to use the same formalism also for the 6LoWPAN > layer. yes they are and imho it does as well. > > -- > Juergen Schoenwaelder Jacobs University Bremen gGmbH > Phone: +49 421 200 3587 Campus Ring 1, 28759 Bremen, Germany > Fax: +49 421 200 3103 > P PLEASE CONSIDER OUR ENVIRONMENT BEFORE PRINTING THIS EMAIL. This e-mail (including any attachments) is confidential and may be legally = privileged. If you are not an intended recipient or an authorized represent= ative of an intended recipient, you are prohibited from using, copying or d= istributing the information in this e-mail or its attachments. If you have = received this e-mail in error, please notify the sender immediately by retu= rn e-mail and delete all copies of this message and any attachments. Thank = you. From bclaise@cisco.com Thu Oct 3 01:34:23 2013 Return-Path: X-Original-To: coman@ietfa.amsl.com Delivered-To: coman@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9780021F9D70; Thu, 3 Oct 2013 01:34:23 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -10.498 X-Spam-Level: X-Spam-Status: No, score=-10.498 tagged_above=-999 required=5 tests=[AWL=0.101, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kdEzN0sRieDO; Thu, 3 Oct 2013 01:34:13 -0700 (PDT) Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by ietfa.amsl.com (Postfix) with ESMTP id 9B39421F88DD; Thu, 3 Oct 2013 01:33:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=6083; q=dns/txt; s=iport; t=1380789200; x=1381998800; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=vgT7JkyV3AO5zJ0vo4gkzqOhsOwQ4TqkVWMXDZXHVcU=; b=hFCULjRRJ7DXkCdTXBTRTXlVB7EJ2l3qV2Wmxs3tA0RmhwMY4XvrzbuW QHGPu73cZeZMJE1CXediLJ7IpNR718nYWdy9Oc+H9BpD8+F46cALk9u22 63IvecucfQa0m86vtKvWi47RSeIHeTWlqJIuvK58ZATLnOa0dXiB/Tvsx s=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AgcFAJUqTVKQ/khL/2dsb2JhbABXA4MHOMIKgR8WdIIlAQEBAwEBAQE1NgoBBQcCAgsQAQQBAQEJFggHCQMCAQIBCQwfCQgGDQEFAgEBF4dlBgy9CgSOBBCBKQsFBwYLhBIDlCSDXYEvhQaLSoFmgUA6gTU X-IronPort-AV: E=Sophos;i="4.90,1024,1371081600"; d="scan'208";a="160284000" Received: from ams-core-2.cisco.com ([144.254.72.75]) by ams-iport-1.cisco.com with ESMTP; 03 Oct 2013 08:33:19 +0000 Received: from [10.60.67.85] (ams-bclaise-8914.cisco.com [10.60.67.85]) by ams-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id r938XFsr016579; Thu, 3 Oct 2013 08:33:16 GMT Message-ID: <524D2BCB.8020008@cisco.com> Date: Thu, 03 Oct 2013 10:33:15 +0200 From: Benoit Claise User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8 MIME-Version: 1.0 To: "Turner, Randy" References: <20130923180202.32168.94377.idtracker@ietfa.amsl.com> <9904FB1B0159DA42B0B887B7FA8119CA128E75E5@AZ-FFEXMB04.global.avaya.com> <52419692.7050903@cisco.com> <20130924134921.GA19673@elstar.local> <52419C92.9040807@cisco.com> <20130926132817.GB25326@elstar.local> <9904FB1B0159DA42B0B887B7FA8119CA128E9913@AZ-FFEXMB04.global.avaya.com> <20130926215221.GA26059@elstar.local> <9904FB1B0159DA42B0B887B7FA8119CA128E9DF0@AZ-FFEXMB04.global.avaya.com> <20130930120122.GC7925@elstar.local> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: "coman@ietf.org" , "6lo@ietf.org" <6lo@ietf.org> Subject: Re: [coman] [6lo] WG Review: IPv6 over Networks of Resource-constrained Nodes (6lo) X-BeenThere: coman@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Management of Constrained Networks and Devices List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Oct 2013 08:34:23 -0000 Dear all, Sorry for the delay in getting back to you. I took the last email in the email threat to summarize my thoughts. It seems that the latest proposal on the table is: OLD: Related MIB modules NEW: MIB module for the counters in the 6LoWPAN layer for basic monitoring and troubleshooting It goes in the right direction, but it's not enough. I would go for Information model for the counters in the 6LoWPAN layer for basic monitoring and troubleshooting, and a mapping to a data model (MIB module in this case) Why? - SNMP being the way to monitor counters on a constrained node now, I could buy that! However, just telling "MIB modules" in the charter might give the wrong impression that SNMP is the only way to manage a constrained node. We don't know the answer at this point in time (at least, I don't) - We really need to make the difference between information model and data model (RFC 3444) Mapping from an information model to a different data model/protocol is the right way to go Notes: - the distinction between information model and data model doesn't imply that we need to have two deliverables. - I'm in line with Dan regarding this comment "a separate discussion (here or some place else) about the broader aspects of management of resource-constrained nodes. " This discussion should happen sometime, somewhere. Regards, Benoit > I agree with Juergen's earlier comments regarding the use of SMIv2 -- seems like we would want to keep the same way of describing our data model. But I would probably go a bit further. > > I would pursue SMIv2/SNMP as a management infrastructure, and later, if something better comes along, someone can propose that. SNMP management infrastructures (management stations, etc) are likely to be what we run into for managed LLNs, it would be nice if we what we come up with can play in those environments, without any loss of semantics or functionality. > > Randy > > -----Original Message----- > From: coman-bounces@ietf.org [mailto:coman-bounces@ietf.org] On Behalf Of joel jaeggli > Sent: Wednesday, October 02, 2013 12:37 PM > To: Juergen Schoenwaelder > Cc: Benoit Claise; Romascanu, Dan (Dan); coman@ietf.org; The IESG; 6lo WG > Subject: Re: [coman] [6lo] WG Review: IPv6 over Networks of Resource-constrained Nodes (6lo) > > > On Sep 30, 2013, at 5:01 AM, Juergen Schoenwaelder wrote: > >> On Fri, Sep 27, 2013 at 02:37:57PM +0000, Romascanu, Dan (Dan) wrote: >>> Hi Juergen, >>> >>> I believe that what would not be useful is to be vague in the charter about what the WG must develop as part of its 'contract' with the IESG. >>> >>> My proposal was based on what you wrote in your previous mail: >>> >>>> One more time: The goal here is to define the number and the >>>> semantics of the counters that need to implemented in the 6LoWPAN >>>> layer in order to enable basic monitoring and troubleshooting. The >>>> formalism we have (as a standard) for that are MIB modules. >>> Are now saying that the goal of the WG is not to define only the 'number and semantics of the counters' but actually the data model itself? Then Let us say it. I suggest: >>> >>> - MIB module for the counters in the 6LoWPAN layer for basic >>> monitoring and troubleshooting >>> >>> We should avoid just saying 'MIB module' because this is too vague, and also we should not imply that this is necessarily the full management solution because it seems that the discussion about what is the management solution did not yet happen in the WG. >>> >> Apparently some prefer a more open ended charter while others prefer a >> strict charter. It will at the end be the IESG's job to define what >> the IESG prefers. >> >> If a strict charter is called for, then replacing >> >> Related MIB modules >> >> with >> >> MIB module for the counters in the 6LoWPAN layer for basic monitoring >> and troubleshooting >> > So, I'm of the opinion that the question isn't strict or open charter but rather that most work in this space doesn't use snmp for configuration, just instrumentation and that doesn't seem likely to change. > > I like that text btw. > >> is certainly fine with me. >> >> For those interested in a YANG model or a way to transport SMIv2 MIB >> defined counters over CoAP, please read Appendix A: >> >> http://tools.ietf.org/html/draft-schoenw-6lowpan-mib-03#appendix-A >> >> Following RFC 6643, a read-only MIB modules already translates into a >> YANG module and this may lead to a JSON representation (although this >> serialization of YANG defined data trees into JSON is at this point >> unchartered work). >> >> /js >> >> PS: 6LoWPAN does not exist in isolation. There are further counters >> devices should support such as basic interface in/out counters or >> counters in the IPv6 layer. All these counters and their semantics >> are defined today in SMIv2 MIB modules. Hence, it seems quite >> reasonable to me to use the same formalism also for the 6LoWPAN >> layer. > yes they are and imho it does as well. > >> -- >> Juergen Schoenwaelder Jacobs University Bremen gGmbH >> Phone: +49 421 200 3587 Campus Ring 1, 28759 Bremen, Germany >> Fax: +49 421 200 3103 >> > > P PLEASE CONSIDER OUR ENVIRONMENT BEFORE PRINTING THIS EMAIL. > > This e-mail (including any attachments) is confidential and may be legally privileged. If you are not an intended recipient or an authorized representative of an intended recipient, you are prohibited from using, copying or distributing the information in this e-mail or its attachments. If you have received this e-mail in error, please notify the sender immediately by return e-mail and delete all copies of this message and any attachments. Thank you. > _______________________________________________ > coman mailing list > coman@ietf.org > https://www.ietf.org/mailman/listinfo/coman > . > From j.schoenwaelder@jacobs-university.de Thu Oct 3 02:17:16 2013 Return-Path: X-Original-To: coman@ietfa.amsl.com Delivered-To: coman@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F18FB21F9FBC; Thu, 3 Oct 2013 02:17:15 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -103.249 X-Spam-Level: X-Spam-Status: No, score=-103.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HuyjmAiANj8B; Thu, 3 Oct 2013 02:16:54 -0700 (PDT) Received: from hermes.jacobs-university.de (hermes.jacobs-university.de [212.201.44.23]) by ietfa.amsl.com (Postfix) with ESMTP id 9BB1B11E80DE; Thu, 3 Oct 2013 02:16:21 -0700 (PDT) Received: from localhost (demetrius3.jacobs-university.de [212.201.44.48]) by hermes.jacobs-university.de (Postfix) with ESMTP id C04D120C1D; Thu, 3 Oct 2013 11:16:20 +0200 (CEST) X-Virus-Scanned: amavisd-new at jacobs-university.de Received: from hermes.jacobs-university.de ([212.201.44.23]) by localhost (demetrius3.jacobs-university.de [212.201.44.32]) (amavisd-new, port 10024) with ESMTP id Dfqm28xDlCEY; Thu, 3 Oct 2013 11:16:20 +0200 (CEST) Received: from elstar.local (elstar.jacobs.jacobs-university.de [10.50.231.133]) by hermes.jacobs-university.de (Postfix) with ESMTP id CFD6E20C1C; Thu, 3 Oct 2013 11:16:19 +0200 (CEST) Received: by elstar.local (Postfix, from userid 501) id 5F19F28AA16A; Thu, 3 Oct 2013 11:16:15 +0200 (CEST) Date: Thu, 3 Oct 2013 11:16:15 +0200 From: Juergen Schoenwaelder To: Benoit Claise Message-ID: <20131003091615.GA28542@elstar.local> Mail-Followup-To: Benoit Claise , "Turner, Randy" , "coman@ietf.org" , "6lo@ietf.org" <6lo@ietf.org> References: <20130924134921.GA19673@elstar.local> <52419C92.9040807@cisco.com> <20130926132817.GB25326@elstar.local> <9904FB1B0159DA42B0B887B7FA8119CA128E9913@AZ-FFEXMB04.global.avaya.com> <20130926215221.GA26059@elstar.local> <9904FB1B0159DA42B0B887B7FA8119CA128E9DF0@AZ-FFEXMB04.global.avaya.com> <20130930120122.GC7925@elstar.local> <524D2BCB.8020008@cisco.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <524D2BCB.8020008@cisco.com> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: "coman@ietf.org" , "Turner, Randy" , "6lo@ietf.org" <6lo@ietf.org> Subject: Re: [coman] [6lo] WG Review: IPv6 over Networks of Resource-constrained Nodes (6lo) X-BeenThere: coman@ietf.org X-Mailman-Version: 2.1.12 Precedence: list Reply-To: Juergen Schoenwaelder List-Id: Management of Constrained Networks and Devices List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Oct 2013 09:17:16 -0000 On Thu, Oct 03, 2013 at 10:33:15AM +0200, Benoit Claise wrote: > > Why? > - SNMP being the way to monitor counters on a constrained node now, > I could buy that! > However, just telling "MIB modules" in the charter might give the > wrong impression that SNMP is the only way to manage a constrained > node. We don't know the answer at this point in time (at least, I > don't) > > - We really need to make the difference between information model > and data model (RFC 3444) > Mapping from an information model to a different data model/protocol > is the right way to go > > Notes: > - the distinction between information model and data model doesn't > imply that we need to have two deliverables. > - I'm in line with Dan regarding this comment "a separate discussion > (here or some place else) about the broader aspects of management of > resource-constrained nodes. " This discussion should happen > sometime, somewhere. It might help to look at what we are talking about here. The 'information model' really is this Case Diagram: IPv6 layer ^ v InDelivers -+- -+- OutRequests | | InDiscards <--+ | | | InCompOKs .-->| |-->. OutCompReqds InCompFails <--| | | +--> OutCompFails InCompReqds `<--+ +<--' OutCompOKs | | | +-->. OutFragReqds InReasmOKs .-->| | +--> OutFragFails InReasmFails <--| | | -+- OutFragOKs InReasmReqds `<--+ +<--' OutFragCreates | | | | InMeshDelivers |<--. | InMeshForwds | |-->. | InMeshReceives +-->' | | | +--> | OutMeshHopLimitExceeds | +--> | OutMeshNoRoutes | | | | | .<--+ OutMeshRequests | `-->| | OutMeshForwds | `-->| OutMeshTransmits | | InHdrErrors <--+ +--> OutDiscards | | InReceives -+- -+- OutTransmits ^ v interface layer In the past, we simply recoded such things in MIB modules in the 'Overview' section and we were done. So is your proposal that we s/Overview/Information Model/ ? Well, if that is what is being called for... /js -- Juergen Schoenwaelder Jacobs University Bremen gGmbH Phone: +49 421 200 3587 Campus Ring 1, 28759 Bremen, Germany Fax: +49 421 200 3103 From bclaise@cisco.com Thu Oct 3 02:46:22 2013 Return-Path: X-Original-To: coman@ietfa.amsl.com Delivered-To: coman@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4692F21F85E0; Thu, 3 Oct 2013 02:46:22 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -10.505 X-Spam-Level: X-Spam-Status: No, score=-10.505 tagged_above=-999 required=5 tests=[AWL=0.094, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OWfMcYiY8XCJ; Thu, 3 Oct 2013 02:46:03 -0700 (PDT) Received: from ams-iport-3.cisco.com (ams-iport-3.cisco.com [144.254.224.146]) by ietfa.amsl.com (Postfix) with ESMTP id E6D4E21F8AF4; Thu, 3 Oct 2013 02:44:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3719; q=dns/txt; s=iport; t=1380793487; x=1382003087; h=message-id:date:from:mime-version:to:subject:references: in-reply-to:content-transfer-encoding; bh=18sLsCoDQj1nQhb2AHH9zdj3RWH/71K130JDeAx7XfE=; b=VZiJI30hEUgN24MFilhehcFnQnpQXav41wlkUM7ljwm5thL+5cASnci1 v9+iID6gtg2VtXwSKb9EjcW9UnvoJ6Fv3fw85ErJp9NGIoM7OE7N3B/hR IOoqvWTakEqzj0/4Qs3kQmf+1TxzIAptTZqINg4RGwhd1KHRusXqlb/Li 0=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AgUFADE8TVKQ/khN/2dsb2JhbABZgwfCQ4EgFnSCJQEBAQQnCwEFQBELGAkWDwkDAgECAUUGAQwIAQGIAr09j1iEIwOYAYY1i0qBZoFAOg X-IronPort-AV: E=Sophos;i="4.90,872,1371081600"; d="scan'208";a="18018255" Received: from ams-core-4.cisco.com ([144.254.72.77]) by ams-iport-3.cisco.com with ESMTP; 03 Oct 2013 09:44:45 +0000 Received: from [10.60.67.85] (ams-bclaise-8914.cisco.com [10.60.67.85]) by ams-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id r939ieev016134; Thu, 3 Oct 2013 09:44:42 GMT Message-ID: <524D3C88.3040701@cisco.com> Date: Thu, 03 Oct 2013 11:44:40 +0200 From: Benoit Claise User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8 MIME-Version: 1.0 To: "Turner, Randy" , "coman@ietf.org" , "6lo@ietf.org" <6lo@ietf.org> References: <20130924134921.GA19673@elstar.local> <52419C92.9040807@cisco.com> <20130926132817.GB25326@elstar.local> <9904FB1B0159DA42B0B887B7FA8119CA128E9913@AZ-FFEXMB04.global.avaya.com> <20130926215221.GA26059@elstar.local> <9904FB1B0159DA42B0B887B7FA8119CA128E9DF0@AZ-FFEXMB04.global.avaya.com> <20130930120122.GC7925@elstar.local> <524D2BCB.8020008@cisco.com> <20131003091615.GA28542@elstar.local> In-Reply-To: <20131003091615.GA28542@elstar.local> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Subject: Re: [coman] [6lo] WG Review: IPv6 over Networks of Resource-constrained Nodes (6lo) X-BeenThere: coman@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Management of Constrained Networks and Devices List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Oct 2013 09:46:22 -0000 Jürgen, > On Thu, Oct 03, 2013 at 10:33:15AM +0200, Benoit Claise wrote: >> Why? >> - SNMP being the way to monitor counters on a constrained node now, >> I could buy that! >> However, just telling "MIB modules" in the charter might give the >> wrong impression that SNMP is the only way to manage a constrained >> node. We don't know the answer at this point in time (at least, I >> don't) >> >> - We really need to make the difference between information model >> and data model (RFC 3444) >> Mapping from an information model to a different data model/protocol >> is the right way to go >> >> Notes: >> - the distinction between information model and data model doesn't >> imply that we need to have two deliverables. >> - I'm in line with Dan regarding this comment "a separate discussion >> (here or some place else) about the broader aspects of management of >> resource-constrained nodes. " This discussion should happen >> sometime, somewhere. > It might help to look at what we are talking about here. The 'information > model' really is this Case Diagram: > > IPv6 layer > ^ v > InDelivers -+- -+- OutRequests > | | > InDiscards <--+ | > | | > InCompOKs .-->| |-->. OutCompReqds > InCompFails <--| | | +--> OutCompFails > InCompReqds `<--+ +<--' OutCompOKs > | | > | +-->. OutFragReqds > InReasmOKs .-->| | +--> OutFragFails > InReasmFails <--| | | -+- OutFragOKs > InReasmReqds `<--+ +<--' OutFragCreates > | | > | | > InMeshDelivers |<--. | > InMeshForwds | |-->. | > InMeshReceives +-->' | | > | +--> | OutMeshHopLimitExceeds > | +--> | OutMeshNoRoutes > | | | > | | .<--+ OutMeshRequests > | `-->| | OutMeshForwds > | `-->| OutMeshTransmits > | | > InHdrErrors <--+ +--> OutDiscards > | | > InReceives -+- -+- OutTransmits > ^ v > interface layer > > In the past, we simply recoded such things in MIB modules in the > 'Overview' section and we were done. > > So is your proposal that we s/Overview/Information Model/ ? Well, > if that is what is being called for... I don't want to discuss the format or language for the information model here, but that would be a start. Yes. I know that you know all about SNMP/MIB, NETCONF/YANG, Information/Data Model, and more, and that all this is clear in your mind. And I guess that you have your views on how to manage constrained devices: fine. The issue I was trying to solve with, what could appear to be a trick to you (knowing your background), is sending the wrong message in a charter. And that message could/will be taken as granted by the rest of the pack. Glad that we converge. Regards, Benoit (OPS AD) > > /js > From cabo@tzi.org Thu Oct 3 02:54:22 2013 Return-Path: X-Original-To: coman@ietfa.amsl.com Delivered-To: coman@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9AD9E21F9E40; Thu, 3 Oct 2013 02:54:20 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -106.249 X-Spam-Level: X-Spam-Status: No, score=-106.249 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hyfNT58m3Lth; Thu, 3 Oct 2013 02:54:08 -0700 (PDT) Received: from informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) by ietfa.amsl.com (Postfix) with ESMTP id 141FE21F9DF7; Thu, 3 Oct 2013 02:53:16 -0700 (PDT) X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de Received: from smtp-fb3.informatik.uni-bremen.de (smtp-fb3.informatik.uni-bremen.de [134.102.224.120]) by informatik.uni-bremen.de (8.14.4/8.14.4) with ESMTP id r939rBlR009551; Thu, 3 Oct 2013 11:53:11 +0200 (CEST) Received: from [192.168.217.105] (p5489466A.dip0.t-ipconnect.de [84.137.70.106]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id 9EF1D6C2; Thu, 3 Oct 2013 11:53:10 +0200 (CEST) Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\)) Content-Type: text/plain; charset=iso-8859-1 From: Carsten Bormann In-Reply-To: <524D2BCB.8020008@cisco.com> Date: Thu, 3 Oct 2013 11:53:09 +0200 Content-Transfer-Encoding: quoted-printable Message-Id: References: <20130923180202.32168.94377.idtracker@ietfa.amsl.com> <9904FB1B0159DA42B0B887B7FA8119CA128E75E5@AZ-FFEXMB04.global.avaya.com> <52419692.7050903@cisco.com> <20130924134921.GA19673@elstar.local> <52419C92.9040807@cisco.com> <20130926132817.GB25326@elstar.local> <9904FB1B0159DA42B0B887B7FA8119CA128E9913@AZ-FFEXMB04.global.avaya.com> <20130926215221.GA26059@elstar.local> <9904FB1B0159DA42B0B887B7FA8119CA128E9DF0@AZ-FFEXMB04.global.avaya.com> <20130930120122.GC7925@elstar.local> <524D2BCB.8020008@cisco.com> To: Benoit Claise X-Mailer: Apple Mail (2.1510) Cc: "coman@ietf.org" , "Turner, Randy" , "6lo@ietf.org" <6lo@ietf.org> Subject: Re: [coman] [6lo] WG Review: IPv6 over Networks of Resource-constrained Nodes (6lo) X-BeenThere: coman@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Management of Constrained Networks and Devices List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Oct 2013 09:54:23 -0000 On Oct 3, 2013, at 10:33, Benoit Claise wrote: > Information model for the counters in the 6LoWPAN layer for basic = monitoring > and troubleshooting, and a mapping to a data model (MIB module in = this case) I still believe the parenthesis is a bit constraining (pun not = intended), not the least because over time we will have more than one = case. (We also have at least one thing that actually is not a counter.) = More importantly, new IP-over-foos may need new counters, so limiting = this to the 6LoWPAN layer means we'll need to recharter for a 6lobac MIB = module etc. For the ~ 10 % of work of the WG that is concerned with defining those = counters (and related bits of information), the WG will need to listen = for input from the management experts. I think the decision that the current one will be a MIB module should be = in the milestones, and the charter should say how we arrive at these = decisions. Gr=FC=DFe, Carsten From j.schoenwaelder@jacobs-university.de Thu Oct 3 04:29:09 2013 Return-Path: X-Original-To: coman@ietfa.amsl.com Delivered-To: coman@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4A5FE21F9926; Thu, 3 Oct 2013 04:29:09 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -103.249 X-Spam-Level: X-Spam-Status: No, score=-103.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gtPY7J16rSMS; Thu, 3 Oct 2013 04:28:58 -0700 (PDT) Received: from hermes.jacobs-university.de (hermes.jacobs-university.de [212.201.44.23]) by ietfa.amsl.com (Postfix) with ESMTP id D771D21F9D4C; Thu, 3 Oct 2013 04:24:33 -0700 (PDT) Received: from localhost (demetrius2.jacobs-university.de [212.201.44.47]) by hermes.jacobs-university.de (Postfix) with ESMTP id E050420C83; Thu, 3 Oct 2013 13:24:32 +0200 (CEST) X-Virus-Scanned: amavisd-new at jacobs-university.de Received: from hermes.jacobs-university.de ([212.201.44.23]) by localhost (demetrius2.jacobs-university.de [212.201.44.32]) (amavisd-new, port 10024) with ESMTP id rr48NaOcM6EC; Thu, 3 Oct 2013 13:24:32 +0200 (CEST) Received: from elstar.local (elstar.jacobs.jacobs-university.de [10.50.231.133]) by hermes.jacobs-university.de (Postfix) with ESMTP id 86B9420C82; Thu, 3 Oct 2013 13:24:32 +0200 (CEST) Received: by elstar.local (Postfix, from userid 501) id 7ADD628AA37B; Thu, 3 Oct 2013 13:24:27 +0200 (CEST) Date: Thu, 3 Oct 2013 13:24:27 +0200 From: Juergen Schoenwaelder To: Benoit Claise Message-ID: <20131003112427.GA28779@elstar.local> Mail-Followup-To: Benoit Claise , "Turner, Randy" , "coman@ietf.org" , "6lo@ietf.org" <6lo@ietf.org> References: <20130926132817.GB25326@elstar.local> <9904FB1B0159DA42B0B887B7FA8119CA128E9913@AZ-FFEXMB04.global.avaya.com> <20130926215221.GA26059@elstar.local> <9904FB1B0159DA42B0B887B7FA8119CA128E9DF0@AZ-FFEXMB04.global.avaya.com> <20130930120122.GC7925@elstar.local> <524D2BCB.8020008@cisco.com> <20131003091615.GA28542@elstar.local> <524D3C88.3040701@cisco.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <524D3C88.3040701@cisco.com> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: "coman@ietf.org" , "Turner, Randy" , "6lo@ietf.org" <6lo@ietf.org> Subject: Re: [coman] [6lo] WG Review: IPv6 over Networks of Resource-constrained Nodes (6lo) X-BeenThere: coman@ietf.org X-Mailman-Version: 2.1.12 Precedence: list Reply-To: Juergen Schoenwaelder List-Id: Management of Constrained Networks and Devices List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Oct 2013 11:29:09 -0000 On Thu, Oct 03, 2013 at 11:44:40AM +0200, Benoit Claise wrote: > I don't want to discuss the format or language for the information > model here, but that would be a start. Yes. > > I know that you know all about SNMP/MIB, NETCONF/YANG, > Information/Data Model, and more, and that all this is clear in your > mind. And I guess that you have your views on how to manage > constrained devices: fine. > > The issue I was trying to solve with, what could appear to be a > trick to you (knowing your background), is sending the wrong message > in a charter. And that message could/will be taken as granted by the > rest of the pack. My observation is that this protocol layer is rather simple and in the past we did not ask for explicit information models for things that are reasonably simple. But perhaps those times are over... /js -- Juergen Schoenwaelder Jacobs University Bremen gGmbH Phone: +49 421 200 3587 Campus Ring 1, 28759 Bremen, Germany Fax: +49 421 200 3103 From bclaise@cisco.com Thu Oct 3 05:04:50 2013 Return-Path: X-Original-To: coman@ietfa.amsl.com Delivered-To: coman@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 94CB621F98AC; Thu, 3 Oct 2013 05:04:50 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -10.51 X-Spam-Level: X-Spam-Status: No, score=-10.51 tagged_above=-999 required=5 tests=[AWL=0.089, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uFXecSPSb6pY; Thu, 3 Oct 2013 05:04:36 -0700 (PDT) Received: from ams-iport-4.cisco.com (ams-iport-4.cisco.com [144.254.224.147]) by ietfa.amsl.com (Postfix) with ESMTP id 5E0F921F8EDF; Thu, 3 Oct 2013 04:59:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=982; q=dns/txt; s=iport; t=1380801563; x=1382011163; h=message-id:date:from:mime-version:to:subject:references: in-reply-to:content-transfer-encoding; bh=xNxbzD8qMTsE8DOOag3XE+XGRwd9ryhdOFDUkNtM9x4=; b=mGKHC0HcROVuZfhHwheICYVOxS1v87NSg2HRPYDHCzK/qQbT+pbhOVoJ 3znG/mBeqePW5LpP/v6rDRssBoWcNqP7kPZKKswp88Ylzsl4msvwFAFGI bSSReNWQ3x2UgXiHeu44soZAgQkI2L+XwqY54wa0Fq/dvc4h9JgDnwhf0 0=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AhsFACZbTVKQ/khN/2dsb2JhbABZgwfCRoEgFnSCJQEBAQMBOEAGCwsYCRYPCQMCAQIBRQYBDAgBAYd8Brxtj1iEIwOYAYY1i0qBZoFAOg X-IronPort-AV: E=Sophos;i="4.90,1025,1371081600"; d="scan'208";a="18497642" Received: from ams-core-4.cisco.com ([144.254.72.77]) by ams-iport-4.cisco.com with ESMTP; 03 Oct 2013 11:59:19 +0000 Received: from [10.60.67.85] (ams-bclaise-8914.cisco.com [10.60.67.85]) by ams-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id r93BxEil018351; Thu, 3 Oct 2013 11:59:16 GMT Message-ID: <524D5C12.6040606@cisco.com> Date: Thu, 03 Oct 2013 13:59:14 +0200 From: Benoit Claise User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8 MIME-Version: 1.0 To: "Turner, Randy" , "coman@ietf.org" , "6lo@ietf.org" <6lo@ietf.org> References: <20130926132817.GB25326@elstar.local> <9904FB1B0159DA42B0B887B7FA8119CA128E9913@AZ-FFEXMB04.global.avaya.com> <20130926215221.GA26059@elstar.local> <9904FB1B0159DA42B0B887B7FA8119CA128E9DF0@AZ-FFEXMB04.global.avaya.com> <20130930120122.GC7925@elstar.local> <524D2BCB.8020008@cisco.com> <20131003091615.GA28542@elstar.local> <524D3C88.3040701@cisco.com> <20131003112427.GA28779@elstar.local> In-Reply-To: <20131003112427.GA28779@elstar.local> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [coman] [6lo] WG Review: IPv6 over Networks of Resource-constrained Nodes (6lo) X-BeenThere: coman@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Management of Constrained Networks and Devices List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Oct 2013 12:04:50 -0000 > On Thu, Oct 03, 2013 at 11:44:40AM +0200, Benoit Claise wrote: > >> I don't want to discuss the format or language for the information >> model here, but that would be a start. Yes. >> >> I know that you know all about SNMP/MIB, NETCONF/YANG, >> Information/Data Model, and more, and that all this is clear in your >> mind. And I guess that you have your views on how to manage >> constrained devices: fine. >> >> The issue I was trying to solve with, what could appear to be a >> trick to you (knowing your background), is sending the wrong message >> in a charter. And that message could/will be taken as granted by the >> rest of the pack. > My observation is that this protocol layer is rather simple and in the > past we did not ask for explicit information models for things that > are reasonably simple. But perhaps those times are over... It's not black or white. Constrained nodes are non traditional managed devices. Regards, Benoit > > /js > From ulrich@herberg.name Thu Oct 3 14:05:06 2013 Return-Path: X-Original-To: coman@ietfa.amsl.com Delivered-To: coman@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5410E1F0D37 for ; Thu, 3 Oct 2013 14:05:05 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.978 X-Spam-Level: X-Spam-Status: No, score=-1.978 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, NO_RELAYS=-0.001] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3UXHTwe5ikM8 for ; Thu, 3 Oct 2013 14:04:58 -0700 (PDT) Received: from mail-ve0-x22b.google.com (mail-ve0-x22b.google.com [IPv6:2607:f8b0:400c:c01::22b]) by ietfa.amsl.com (Postfix) with ESMTP id 04AC321F8FE5 for ; Thu, 3 Oct 2013 13:52:18 -0700 (PDT) Received: by mail-ve0-f171.google.com with SMTP id pa12so2012863veb.2 for ; Thu, 03 Oct 2013 13:52:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=herberg.name; s=dkim; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=T7/2SSr82Fn3A5B52bmeKi6YuyAWh93tjXgntsTdKCQ=; b=cpBhoOGdc/ElkBCQQ7Z1hPuaBWerkmmvrtDTzUKAu/BRHx5zMP23+4bIlR1XihIp68 wh1LDqnV1+OjAwpcefwPKUY/6EoBN2fLsu7zFPM9RBsn2BKoNGyZsjlS7JA1ZdSm6dQ0 Hg1gwUTREPiP69lNL6iWd7yNXd96GmpJGZg4M= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=T7/2SSr82Fn3A5B52bmeKi6YuyAWh93tjXgntsTdKCQ=; b=ikYZlRAsL3AKho7s0nDxiRj/djXDyX94yIW9nF7Bi4AmoXEGII2l81+CG62uhaBeha yTRo2xkNMIA0iy7pL1JQB0gp87o8mzzBqyLLFZ+ErN3LQdG4Tzf0W5QFN9uplqfA+Lzr XlpNyrifcnvh5vvoH0fu3DCckUL/McWS/cjhekaAEN/WvBZpmEsMl4nGrHpTt/039yu6 BoY1lQeM0RA/sSPGNLwYAyy3hLooCkp3kLy5XABlhZCMYZbHX0QExN3+9YNS2bNVssqo oLb0e+xKF8JSsILfWiz9K6jX+br/g7DgyWoaOQqBBlmkS/zK2PA0Xnvqn5soC+QOf482 xvpg== X-Gm-Message-State: ALoCoQkET825IbFkiSWYhJaJ50Op0EmCaNchE4EVTSdsoHslIZ0R+LkHcm1CWvxI+2Ek2YuHJE2G MIME-Version: 1.0 X-Received: by 10.58.152.193 with SMTP id va1mr9205968veb.10.1380833537908; Thu, 03 Oct 2013 13:52:17 -0700 (PDT) Received: by 10.220.168.8 with HTTP; Thu, 3 Oct 2013 13:52:17 -0700 (PDT) In-Reply-To: References: <20130923180202.32168.94377.idtracker@ietfa.amsl.com> <9904FB1B0159DA42B0B887B7FA8119CA128E75E5@AZ-FFEXMB04.global.avaya.com> <52419692.7050903@cisco.com> <20130924134921.GA19673@elstar.local> <52419C92.9040807@cisco.com> <20130926132817.GB25326@elstar.local> <9904FB1B0159DA42B0B887B7FA8119CA128E9913@AZ-FFEXMB04.global.avaya.com> <20130926215221.GA26059@elstar.local> <9904FB1B0159DA42B0B887B7FA8119CA128E9DF0@AZ-FFEXMB04.global.avaya.com> <20130930120122.GC7925@elstar.local> <524D2BCB.8020008@cisco.com> Date: Thu, 3 Oct 2013 13:52:17 -0700 Message-ID: From: Ulrich Herberg To: Carsten Bormann Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: Benoit Claise , "coman@ietf.org" , "Turner, Randy" , "6lo@ietf.org" <6lo@ietf.org> Subject: Re: [coman] [6lo] WG Review: IPv6 over Networks of Resource-constrained Nodes (6lo) X-BeenThere: coman@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Management of Constrained Networks and Devices List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Oct 2013 21:05:06 -0000 Carsten, On Thu, Oct 3, 2013 at 2:53 AM, Carsten Bormann wrote: > On Oct 3, 2013, at 10:33, Benoit Claise wrote: > >> Information model for the counters in the 6LoWPAN layer for basic monit= oring >> and troubleshooting, and a mapping to a data model (MIB module in this = case) > > I still believe the parenthesis is a bit constraining (pun not intended),= not the least because over time we will have more than one case. (We also= have at least one thing that actually is not a counter.) More importantly= , new IP-over-foos may need new counters, so limiting this to the 6LoWPAN l= ayer means we'll need to recharter for a 6lobac MIB module etc. I agree with you on this point. It appears to me that we narrow down the charter to a very small part of work, and we would end up rechartering very soon, for example if a "6lobac" module is proposed. Also, the proposed wording only includes counters; what about read-write objects such as flags to provision objects? Would we want to exclude that? > > For the ~ 10 % of work of the WG that is concerned with defining those co= unters (and related bits of information), the WG will need to listen for in= put from the management experts. > > I think the decision that the current one will be a MIB module should be = in the milestones, and the charter should say how we arrive at these decisi= ons. Yes. Regarding Benoit's proposal of separating information and data module, I am not sure whether this requires a separate deliverable; but as Benoit said, this is not necessarily related, and could be a section of, e.g., the 6lowpan MIB module. That could be part of the discussion how to structure this once the WG is formed. How about the following text: - Information and data models (e.g., MIB modules) for these adaptation layers for basic provisioning, monitoring and troubleshooting. Best regards Ulrich From cabo@tzi.org Thu Oct 3 14:45:42 2013 Return-Path: X-Original-To: coman@ietfa.amsl.com Delivered-To: coman@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 56FAA21F923D; Thu, 3 Oct 2013 14:45:42 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -106.249 X-Spam-Level: X-Spam-Status: No, score=-106.249 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wc+0qwrYN2Np; Thu, 3 Oct 2013 14:45:30 -0700 (PDT) Received: from informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) by ietfa.amsl.com (Postfix) with ESMTP id CC76221F9399; Thu, 3 Oct 2013 14:45:28 -0700 (PDT) X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de Received: from smtp-fb3.informatik.uni-bremen.de (smtp-fb3.informatik.uni-bremen.de [134.102.224.120]) by informatik.uni-bremen.de (8.14.4/8.14.4) with ESMTP id r93LjNND026965; Thu, 3 Oct 2013 23:45:23 +0200 (CEST) Received: from [192.168.217.100] (p5489466A.dip0.t-ipconnect.de [84.137.70.106]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id 05620808; Thu, 3 Oct 2013 23:45:23 +0200 (CEST) References: <20130923180202.32168.94377.idtracker@ietfa.amsl.com> <9904FB1B0159DA42B0B887B7FA8119CA128E75E5@AZ-FFEXMB04.global.avaya.com> <52419692.7050903@cisco.com> <20130924134921.GA19673@elstar.local> <52419C92.9040807@cisco.com> <20130926132817.GB25326@elstar.local> <9904FB1B0159DA42B0B887B7FA8119CA128E9913@AZ-FFEXMB04.global.avaya.com> <20130926215221.GA26059@elstar.local> <9904FB1B0159DA42B0B887B7FA8119CA128E9DF0@AZ-FFEXMB04.global.avaya.com> <20130930120122.GC7925@elstar.local> <524D2BCB.8020008@cisco.com> In-Reply-To: Mime-Version: 1.0 (1.0) Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 Message-Id: <4F05D5EB-8BE8-4A4E-93F6-D82EB35EE2E1@tzi.org> X-Mailer: iPad Mail (11A501) From: Carsten Bormann Date: Thu, 3 Oct 2013 23:45:23 +0200 To: Ulrich Herberg Cc: Benoit Claise , "coman@ietf.org" , "6lo@ietf.org" <6lo@ietf.org> Subject: Re: [coman] [6lo] WG Review: IPv6 over Networks of Resource-constrained Nodes (6lo) X-BeenThere: coman@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Management of Constrained Networks and Devices List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Oct 2013 21:45:42 -0000 > - Information and data models (e.g., MIB modules) for these adaptation > layers for basic provisioning, monitoring and troubleshooting. Strike provisioning; I don't think we know how to do this. Gr=C3=BC=C3=9Fe, Carsten From ulrich@herberg.name Thu Oct 3 16:32:57 2013 Return-Path: X-Original-To: coman@ietfa.amsl.com Delivered-To: coman@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9A20E21F8DA3 for ; Thu, 3 Oct 2013 16:32:57 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.978 X-Spam-Level: X-Spam-Status: No, score=-1.978 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, NO_RELAYS=-0.001] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Astzy4BvxkNa for ; Thu, 3 Oct 2013 16:32:45 -0700 (PDT) Received: from mail-ve0-x22a.google.com (mail-ve0-x22a.google.com [IPv6:2607:f8b0:400c:c01::22a]) by ietfa.amsl.com (Postfix) with ESMTP id BC61321F90AC for ; Thu, 3 Oct 2013 16:32:32 -0700 (PDT) Received: by mail-ve0-f170.google.com with SMTP id c14so2210318vea.29 for ; Thu, 03 Oct 2013 16:32:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=herberg.name; s=dkim; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=xyjm4eC9Sgng8hOqiMLpkA2+VcGThi7cDADUzlWate4=; b=P3dUg/pBJBS8CVD0HMIZALRNF9m0Zb9jTK0Wk+zq3XaQZP4KRfn7Xa1/cm2LdefbWs 4YwIVOuKesPjOwA031MbvWSvPvtKeV/+PMMKFh7zL5vrcTi6zYVkYwDGBhhLt26MMkdc ZowqcXMw/H/gj2ICRen00k0okxNqh6I2OjDDc= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=xyjm4eC9Sgng8hOqiMLpkA2+VcGThi7cDADUzlWate4=; b=bf/sevj1Iws4Rhwmo/dh9HLGE3OwnqcwR9Y8fnuMdl8czB3a77m2ift0NClSZIphKR q5Zb/18Tz7pErHAuZPJom6ET4ezHHA3CZHTAJkQAROkrdAlVZAP3+EofhoICkPGXAP71 QW9dfyvRIsDYkonevx0V3vfK853UJPCXXzk7L2xAfDqaku7O1TDnKCrIPprBMWcbc4C9 HB6mmY8HresUo3Yi0XM8EQbckX5zT3HogSu0b9yOgxdr7NBYSFSX3ftDLxBKlFGVvRlO gP9WzrXLTnREAd9Rjq+w8oDszAUbGbkIRR8pqP41HtQK7omr0GkFxYhy5Xnjo/quRoWi q6CA== X-Gm-Message-State: ALoCoQleUV8av/BQzK386LCps7P2u/ALrtUOZHSVpEx+cdI/bznCslfRzmUNCWYImPpfjUeRrpWw MIME-Version: 1.0 X-Received: by 10.52.119.228 with SMTP id kx4mr8116007vdb.12.1380843151934; Thu, 03 Oct 2013 16:32:31 -0700 (PDT) Received: by 10.220.168.8 with HTTP; Thu, 3 Oct 2013 16:32:31 -0700 (PDT) In-Reply-To: <4F05D5EB-8BE8-4A4E-93F6-D82EB35EE2E1@tzi.org> References: <20130923180202.32168.94377.idtracker@ietfa.amsl.com> <9904FB1B0159DA42B0B887B7FA8119CA128E75E5@AZ-FFEXMB04.global.avaya.com> <52419692.7050903@cisco.com> <20130924134921.GA19673@elstar.local> <52419C92.9040807@cisco.com> <20130926132817.GB25326@elstar.local> <9904FB1B0159DA42B0B887B7FA8119CA128E9913@AZ-FFEXMB04.global.avaya.com> <20130926215221.GA26059@elstar.local> <9904FB1B0159DA42B0B887B7FA8119CA128E9DF0@AZ-FFEXMB04.global.avaya.com> <20130930120122.GC7925@elstar.local> <524D2BCB.8020008@cisco.com> <4F05D5EB-8BE8-4A4E-93F6-D82EB35EE2E1@tzi.org> Date: Thu, 3 Oct 2013 16:32:31 -0700 Message-ID: From: Ulrich Herberg To: Carsten Bormann Content-Type: text/plain; charset=ISO-8859-1 Cc: Benoit Claise , "coman@ietf.org" , "6lo@ietf.org" <6lo@ietf.org> Subject: Re: [coman] [6lo] WG Review: IPv6 over Networks of Resource-constrained Nodes (6lo) X-BeenThere: coman@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Management of Constrained Networks and Devices List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Oct 2013 23:32:57 -0000 On Thu, Oct 3, 2013 at 2:45 PM, Carsten Bormann wrote: >> - Information and data models (e.g., MIB modules) for these adaptation >> layers for basic provisioning, monitoring and troubleshooting. > > Strike provisioning; I don't think we know how to do this. Maybe the term does not reflect what I meant. The previous proposal used the word "counters" and "monitoring", and I wondered if that would exclude "read-write" elements of a MIB module, such as for setting a flag or other parameter. Best regards Ulrich From bclaise@cisco.com Tue Oct 8 13:21:10 2013 Return-Path: X-Original-To: coman@ietfa.amsl.com Delivered-To: coman@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 10D1C21F9CE3; Tue, 8 Oct 2013 13:21:10 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -10.568 X-Spam-Level: X-Spam-Status: No, score=-10.568 tagged_above=-999 required=5 tests=[AWL=0.031, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IKLzBdeJYe6F; Tue, 8 Oct 2013 13:20:56 -0700 (PDT) Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by ietfa.amsl.com (Postfix) with ESMTP id D03F121F9ECA; Tue, 8 Oct 2013 13:20:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1065; q=dns/txt; s=iport; t=1381263653; x=1382473253; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=5b5Ps0kIEoc41ArCvEt40nDy0nT/qZj0OjoPodfa6XM=; b=ckXnxJ+T4MdieWqSH1wyB3A3hJbeQQZyXTqaM0TyrJ4SC32Chd1aoXVM WRPSru4r7GoCtNQcFkGef9aImP/Kv/6pFG821azhKc7Tu6Hn+va4SEbqY Dcy6GL4e0DP6M+mWaxQD0PxRvigGyAUHN7UPwrKRDImw2knDoLxGSh+J2 g=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AhwFAEpoVFKQ/khN/2dsb2JhbABZgwfCMYEjFnSCJQEBAQQyAQUzDQEQCw4KCRYPCQMCAQIBRQYNAQUCAQGIArpfj0IHhCMDmAGGNotKgWaBQDo X-IronPort-AV: E=Sophos;i="4.90,1058,1371081600"; d="scan'208";a="160463776" Received: from ams-core-4.cisco.com ([144.254.72.77]) by ams-iport-1.cisco.com with ESMTP; 08 Oct 2013 20:20:50 +0000 Received: from [10.60.67.85] (ams-bclaise-8914.cisco.com [10.60.67.85]) by ams-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id r98KKkV5012213; Tue, 8 Oct 2013 20:20:47 GMT Message-ID: <5254691E.1030007@cisco.com> Date: Tue, 08 Oct 2013 22:20:46 +0200 From: Benoit Claise User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8 MIME-Version: 1.0 To: Carsten Bormann References: <20130923180202.32168.94377.idtracker@ietfa.amsl.com> <9904FB1B0159DA42B0B887B7FA8119CA128E75E5@AZ-FFEXMB04.global.avaya.com> <52419692.7050903@cisco.com> <20130924134921.GA19673@elstar.local> <52419C92.9040807@cisco.com> <20130926132817.GB25326@elstar.local> <9904FB1B0159DA42B0B887B7FA8119CA128E9913@AZ-FFEXMB04.global.avaya.com> <20130926215221.GA26059@elstar.local> <9904FB1B0159DA42B0B887B7FA8119CA128E9DF0@AZ-FFEXMB04.global.avaya.com> <20130930120122.GC7925@elstar.local> <524D2BCB.8020008@cisco.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Cc: "coman@ietf.org" , "Turner, Randy" , "6lo@ietf.org" <6lo@ietf.org> Subject: Re: [coman] [6lo] WG Review: IPv6 over Networks of Resource-constrained Nodes (6lo) X-BeenThere: coman@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Management of Constrained Networks and Devices List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Oct 2013 20:21:10 -0000 On 3/10/2013 11:53, Carsten Bormann wrote: > On Oct 3, 2013, at 10:33, Benoit Claise wrote: > >> Information model for the counters in the 6LoWPAN layer for basic monitoring >> and troubleshooting, and a mapping to a data model (MIB module in this case) > I still believe the parenthesis is a bit constraining (pun not intended), not the least because over time we will have more than one case. (We also have at least one thing that actually is not a counter.) More importantly, new IP-over-foos may need new counters, so limiting this to the 6LoWPAN layer means we'll need to recharter for a 6lobac MIB module etc. > > For the ~ 10 % of work of the WG that is concerned with defining those counters (and related bits of information), the WG will need to listen for input from the management experts. > > I think the decision that the current one will be a MIB module should be in the milestones, and the charter should say how we arrive at these decisions. That makes sense to me. Regards, Benoit > > Grüße, Carsten > > From bclaise@cisco.com Tue Oct 8 13:40:02 2013 Return-Path: X-Original-To: coman@ietfa.amsl.com Delivered-To: coman@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E17E221F8CCB; Tue, 8 Oct 2013 13:40:02 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -10.568 X-Spam-Level: X-Spam-Status: No, score=-10.568 tagged_above=-999 required=5 tests=[AWL=0.031, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HiwPrj2OIcHs; Tue, 8 Oct 2013 13:39:56 -0700 (PDT) Received: from ams-iport-3.cisco.com (ams-iport-3.cisco.com [144.254.224.146]) by ietfa.amsl.com (Postfix) with ESMTP id ACD1521F9343; Tue, 8 Oct 2013 13:39:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=311; q=dns/txt; s=iport; t=1381264788; x=1382474388; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=eLewZOw6LHLEuWr4bBKjelhCE6CnONZWjdJP7VVTZ9g=; b=idRQyb+6hy9AgtA9D7lR7dFROu6ooG8m5G4eSdGwoOVM6qNpjLFBoeAY BFlR4Hyp63VvJeKNl2kE+OSZVdSZ5q5MNWmMTGiOsfLIMoVuhXCFG5DjQ BRC2WFOX5LZ5g49c9Fd24GhgqeE73s2BG8dNpdDY4l+Nr940xTEiFfTRe 4=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Ah8FAL1sVFKQ/khL/2dsb2JhbABZgweEMrsGgnmBIxZ0giUBAQEEIw8BBUABEAkCDgoCAgUWCwICCQMCAQIBRQYNAQcBAYgCjDObXJI9gSmOGQeCaoE5A5gBhjaLSoFmgUA6 X-IronPort-AV: E=Sophos;i="4.93,872,1378857600"; d="scan'208";a="18146353" Received: from ams-core-2.cisco.com ([144.254.72.75]) by ams-iport-3.cisco.com with ESMTP; 08 Oct 2013 20:39:47 +0000 Received: from [10.60.67.85] (ams-bclaise-8914.cisco.com [10.60.67.85]) by ams-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id r98KdeD6001691; Tue, 8 Oct 2013 20:39:41 GMT Message-ID: <52546D8C.1010307@cisco.com> Date: Tue, 08 Oct 2013 22:39:40 +0200 From: Benoit Claise User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8 MIME-Version: 1.0 To: Carsten Bormann References: <20130923180202.32168.94377.idtracker@ietfa.amsl.com> <9904FB1B0159DA42B0B887B7FA8119CA128E75E5@AZ-FFEXMB04.global.avaya.com> <52419692.7050903@cisco.com> <20130924134921.GA19673@elstar.local> <52419C92.9040807@cisco.com> <20130926132817.GB25326@elstar.local> <9904FB1B0159DA42B0B887B7FA8119CA128E9913@AZ-FFEXMB04.global.avaya.com> <20130926215221.GA26059@elstar.local> <9904FB1B0159DA42B0B887B7FA8119CA128E9DF0@AZ-FFEXMB04.global.avaya.com> <20130930120122.GC7925@elstar.local> <524D2BCB.8020008@cisco.com> <4F05D5EB-8BE8-4A4E-93F6-D82EB35EE2E1@tzi.org> In-Reply-To: <4F05D5EB-8BE8-4A4E-93F6-D82EB35EE2E1@tzi.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Cc: "coman@ietf.org" , Ulrich Herberg , "6lo@ietf.org" <6lo@ietf.org> Subject: Re: [coman] [6lo] WG Review: IPv6 over Networks of Resource-constrained Nodes (6lo) X-BeenThere: coman@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Management of Constrained Networks and Devices List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Oct 2013 20:40:03 -0000 On 3/10/2013 23:45, Carsten Bormann wrote: >> - Information and data models (e.g., MIB modules) for these adaptation >> layers for basic provisioning, monitoring and troubleshooting. > Strike provisioning; I don't think we know how to do this. Works for me. Regards, Benoit > > Grüße, Carsten > > From samita.chakrabarti@ericsson.com Wed Oct 9 19:15:02 2013 Return-Path: X-Original-To: coman@ietfa.amsl.com Delivered-To: coman@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0229D21E8267; Wed, 9 Oct 2013 19:15:02 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.299 X-Spam-Level: X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5 tests=[AWL=0.300, BAYES_00=-2.599] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kHH67FGP2ioJ; Wed, 9 Oct 2013 19:14:47 -0700 (PDT) Received: from usevmg20.ericsson.net (usevmg20.ericsson.net [198.24.6.45]) by ietfa.amsl.com (Postfix) with ESMTP id 5921F21E8263; Wed, 9 Oct 2013 19:14:44 -0700 (PDT) X-AuditID: c618062d-b7fda8e0000024c6-7f-52560d93f200 Received: from EUSAAHC001.ericsson.se (Unknown_Domain [147.117.188.75]) by usevmg20.ericsson.net (Symantec Mail Security) with SMTP id 47.DD.09414.49D06525; Thu, 10 Oct 2013 04:14:44 +0200 (CEST) Received: from EUSAAMB103.ericsson.se ([147.117.188.120]) by EUSAAHC001.ericsson.se ([147.117.188.75]) with mapi id 14.02.0328.009; Wed, 9 Oct 2013 22:14:43 -0400 From: Samita Chakrabarti To: Benoit Claise , Carsten Bormann Thread-Topic: [coman] [6lo] WG Review: IPv6 over Networks of Resource-constrained Nodes (6lo) Thread-Index: AQHOxGaC3+p79s5VCUqi9Jk3B/hgVpntM79A Date: Thu, 10 Oct 2013 02:14:43 +0000 Message-ID: References: <20130923180202.32168.94377.idtracker@ietfa.amsl.com> <9904FB1B0159DA42B0B887B7FA8119CA128E75E5@AZ-FFEXMB04.global.avaya.com> <52419692.7050903@cisco.com> <20130924134921.GA19673@elstar.local> <52419C92.9040807@cisco.com> <20130926132817.GB25326@elstar.local> <9904FB1B0159DA42B0B887B7FA8119CA128E9913@AZ-FFEXMB04.global.avaya.com> <20130926215221.GA26059@elstar.local> <9904FB1B0159DA42B0B887B7FA8119CA128E9DF0@AZ-FFEXMB04.global.avaya.com> <20130930120122.GC7925@elstar.local> <524D2BCB.8020008@cisco.com> <4F05D5EB-8BE8-4A4E-93F6-D82EB35EE2E1@tzi.org> <52546D8C.1010307@cisco.com> In-Reply-To: <52546D8C.1010307@cisco.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [147.117.188.134] Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 MIME-Version: 1.0 X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrPLMWRmVeSWpSXmKPExsUyuXSPt+4U3rAgg/ffxCyapwhYHH0sYXFk yl1Wi5s9u1ktrr6+wObA6jHl90ZWj2cvHjB5LFnyk8lj2qLMAJYoLpuU1JzMstQifbsEroxJ 51gLPnFUHDxm0cB4haOLkZNDQsBEYuPmK6wQtpjEhXvr2UBsIYGjjBLTu1S6GLmA7GWMEt8W z2YHSbAJWEl09O4Bs0UEXCVWnfjNAmIzC+RI/Hv3CiwuLBAncbOtlbmLkQOoJl7i4StbiHIj iZfv9oDNZxFQlfi2aTYziM0r4Cvx/c8WVohd99kk7rZ3gM3kFNCUWLtjL1gRI9Bx30+tYYLY JS5x68l8JoijBSSW7DnPDGGLSrx8/A/qGWWJJU/2s4DcwAw0Z/0ufYhWRYkp3Q/ZIfYKSpyc +YRlAqPYLCRTZyF0zELSMQtJxwJGllWMHKXFqWW56UYGmxiBkXRMgk13B+Oel5aHGKU5WJTE eb+8dQ4SEkhPLEnNTk0tSC2KLyrNSS0+xMjEwSnVwKg3Z+etOXmH2Wa7WJvHrX7GuOjQ2y/r xDxWbC08zi8Ss9l64uaIRY+3sQX617v07+Z+tea2oNFm5p07XWZYeYoVb9vEHezgd0voc6qc CMOPN6tuNMybZ9s76wfH+S7LqwsZOLssGzI9jwiUGyedafZ8ZcJitebafY34LXW+rVdObLW5 X1ClaKPEUpyRaKjFXFScCABEyDwxcgIAAA== Cc: "coman@ietf.org" , Ulrich Herberg , "6lo@ietf.org" <6lo@ietf.org> Subject: Re: [coman] [6lo] WG Review: IPv6 over Networks of Resource-constrained Nodes (6lo) X-BeenThere: coman@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Management of Constrained Networks and Devices List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Oct 2013 02:15:02 -0000 Q2hhcnRlciByZXZpc2lvbiAwNCAgcmVtb3ZlcyAicHJvdmlzaW9uaW5nIiAuDQoNCi1TYW1pdGEN Cg0KLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCkZyb206IGNvbWFuLWJvdW5jZXNAaWV0Zi5v cmcgW21haWx0bzpjb21hbi1ib3VuY2VzQGlldGYub3JnXSBPbiBCZWhhbGYgT2YgQmVub2l0IENs YWlzZQ0KU2VudDogVHVlc2RheSwgT2N0b2JlciAwOCwgMjAxMyAxOjQwIFBNDQpUbzogQ2Fyc3Rl biBCb3JtYW5uDQpDYzogY29tYW5AaWV0Zi5vcmc7IFVscmljaCBIZXJiZXJnOyA2bG9AaWV0Zi5v cmcNClN1YmplY3Q6IFJlOiBbY29tYW5dIFs2bG9dIFdHIFJldmlldzogSVB2NiBvdmVyIE5ldHdv cmtzIG9mIFJlc291cmNlLWNvbnN0cmFpbmVkIE5vZGVzICg2bG8pDQoNCk9uIDMvMTAvMjAxMyAy Mzo0NSwgQ2Fyc3RlbiBCb3JtYW5uIHdyb3RlOg0KPj4gLSBJbmZvcm1hdGlvbiBhbmQgZGF0YSBt b2RlbHMgKGUuZy4sIE1JQiBtb2R1bGVzKSBmb3IgdGhlc2UgDQo+PiBhZGFwdGF0aW9uIGxheWVy cyBmb3IgYmFzaWMgcHJvdmlzaW9uaW5nLCBtb25pdG9yaW5nIGFuZCB0cm91Ymxlc2hvb3Rpbmcu DQo+IFN0cmlrZSBwcm92aXNpb25pbmc7IEkgZG9uJ3QgdGhpbmsgd2Uga25vdyBob3cgdG8gZG8g dGhpcy4NCldvcmtzIGZvciBtZS4NCg0KUmVnYXJkcywgQmVub2l0DQo+DQo+IEdyw7zDn2UsIENh cnN0ZW4NCj4NCj4NCg0KX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX18NCmNvbWFuIG1haWxpbmcgbGlzdA0KY29tYW5AaWV0Zi5vcmcNCmh0dHBzOi8vd3d3Lmll dGYub3JnL21haWxtYW4vbGlzdGluZm8vY29tYW4NCg== From bclaise@cisco.com Thu Oct 10 00:21:25 2013 Return-Path: X-Original-To: coman@ietfa.amsl.com Delivered-To: coman@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 90EF021F9D12; Thu, 10 Oct 2013 00:21:23 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -10.569 X-Spam-Level: X-Spam-Status: No, score=-10.569 tagged_above=-999 required=5 tests=[AWL=0.030, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BgvydKiZVxOO; Thu, 10 Oct 2013 00:21:18 -0700 (PDT) Received: from ams-iport-3.cisco.com (ams-iport-3.cisco.com [144.254.224.146]) by ietfa.amsl.com (Postfix) with ESMTP id 65B6421F8E85; Thu, 10 Oct 2013 00:21:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=997; q=dns/txt; s=iport; t=1381389678; x=1382599278; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=nd9SqkXzAxY0JN+UOxZiI4QJJfwdRaEmizZ8yN0+jOQ=; b=IGwr4wmQPX29HyeGiPnabUsjUce0OznuHpT6ns3g6bj2sznHz/K+i8sD 1nfh8WEGFmWRqHkTZYNftTdA6j10QI5sUt4+FOyWpwYKyX97MdlEs76UH HR6Ut30NkrmzWu5GkRY2qokL2NJwk7vdhKvd9KS9rZpkrmU9tTYknbuZw w=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AisFAPBUVlKQ/khM/2dsb2JhbABagwc4g3q9eIEeFnSCJQEBAQQBAQEgDwEFNgoBDAQJAhEEAQEBAgIFFggDAgIJAwIBAgEVHwkIBg0BBQIBAYgCDIscm1ySOASBKY4eBwaCZIE5A5gFhjiLSoFmgUA6 X-IronPort-AV: E=Sophos;i="4.93,465,1378857600"; d="scan'208";a="18182862" Received: from ams-core-3.cisco.com ([144.254.72.76]) by ams-iport-3.cisco.com with ESMTP; 10 Oct 2013 07:21:17 +0000 Received: from [10.60.67.85] (ams-bclaise-8914.cisco.com [10.60.67.85]) by ams-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id r9A7LCK6012229; Thu, 10 Oct 2013 07:21:14 GMT Message-ID: <52565568.9090904@cisco.com> Date: Thu, 10 Oct 2013 09:21:12 +0200 From: Benoit Claise User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8 MIME-Version: 1.0 To: Samita Chakrabarti References: <20130923180202.32168.94377.idtracker@ietfa.amsl.com> <9904FB1B0159DA42B0B887B7FA8119CA128E75E5@AZ-FFEXMB04.global.avaya.com> <52419692.7050903@cisco.com> <20130924134921.GA19673@elstar.local> <52419C92.9040807@cisco.com> <20130926132817.GB25326@elstar.local> <9904FB1B0159DA42B0B887B7FA8119CA128E9913@AZ-FFEXMB04.global.avaya.com> <20130926215221.GA26059@elstar.local> <9904FB1B0159DA42B0B887B7FA8119CA128E9DF0@AZ-FFEXMB04.global.avaya.com> <20130930120122.GC7925@elstar.local> <524D2BCB.8020008@cisco.com> <4F05D5EB-8BE8-4A4E-93F6-D82EB35EE2E1@tzi.org> <52546D8C.1010307@cisco.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Cc: "coman@ietf.org" , Carsten Bormann , Ulrich Herberg , "6lo@ietf.org" <6lo@ietf.org> Subject: Re: [coman] [6lo] WG Review: IPv6 over Networks of Resource-constrained Nodes (6lo) X-BeenThere: coman@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Management of Constrained Networks and Devices List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Oct 2013 07:21:25 -0000 On 10/10/2013 04:14, Samita Chakrabarti wrote: > Charter revision 04 removes "provisioning" . Even better: MIB module and provisioning is not an obvious match. Regards, Benoit > > -Samita > > -----Original Message----- > From: coman-bounces@ietf.org [mailto:coman-bounces@ietf.org] On Behalf Of Benoit Claise > Sent: Tuesday, October 08, 2013 1:40 PM > To: Carsten Bormann > Cc: coman@ietf.org; Ulrich Herberg; 6lo@ietf.org > Subject: Re: [coman] [6lo] WG Review: IPv6 over Networks of Resource-constrained Nodes (6lo) > > On 3/10/2013 23:45, Carsten Bormann wrote: >>> - Information and data models (e.g., MIB modules) for these >>> adaptation layers for basic provisioning, monitoring and troubleshooting. >> Strike provisioning; I don't think we know how to do this. > Works for me. > > Regards, Benoit >> Grüße, Carsten >> >> > _______________________________________________ > coman mailing list > coman@ietf.org > https://www.ietf.org/mailman/listinfo/coman From dromasca@avaya.com Sun Oct 20 01:04:37 2013 Return-Path: X-Original-To: coman@ietfa.amsl.com Delivered-To: coman@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5D48611E8187 for ; Sun, 20 Oct 2013 01:04:37 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.799 X-Spam-Level: X-Spam-Status: No, score=-102.799 tagged_above=-999 required=5 tests=[AWL=-0.201, BAYES_00=-2.599, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id P6Z0frnCaw0g for ; Sun, 20 Oct 2013 01:04:31 -0700 (PDT) Received: from p-us1-iereast-outbound.us1.avaya.com (p-us1-iereast-outbound.us1.avaya.com [135.11.29.13]) by ietfa.amsl.com (Postfix) with ESMTP id 4A0DB11E8360 for ; Sun, 20 Oct 2013 01:04:31 -0700 (PDT) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AnkWAAuOY1KHCzI1/2dsb2JhbABagkMjIThUqTEbB4wTiAJLgSAWbQeCJQEBAQEDAQEBDxtBHQEIDQQDAQEBCx0JJQsUBwEBBQUEEwgBBRSHZAEMnyqESJwwF48rIA0KB4MZgQoDkC2BMIdbhTOFcYU0gWaBPoIq X-IronPort-AV: E=Sophos;i="4.93,532,1378872000"; d="txt'?scan'208,217";a="33233120" Received: from unknown (HELO p-us1-erheast.us1.avaya.com) ([135.11.50.53]) by p-us1-iereast-outbound.us1.avaya.com with ESMTP; 20 Oct 2013 04:04:30 -0400 Received: from unknown (HELO AZ-FFEXHC03.global.avaya.com) ([135.64.58.13]) by p-us1-erheast-out.us1.avaya.com with ESMTP; 20 Oct 2013 03:55:09 -0400 Received: from AZ-FFEXMB04.global.avaya.com ([fe80::6db7:b0af:8480:c126]) by AZ-FFEXHC03.global.avaya.com ([135.64.58.13]) with mapi id 14.03.0146.000; Sun, 20 Oct 2013 04:04:28 -0400 From: "Romascanu, Dan (Dan)" To: "coman@ietf.org" Thread-Topic: [Netconf] Fwd: I-D Action: draft-bierman-netconf-efficiency-extensions-00.txt Thread-Index: AQHOzPneMkfmYfvqG0ymHzYYgOeItpn9O9Yg Date: Sun, 20 Oct 2013 08:04:28 +0000 Message-ID: <9904FB1B0159DA42B0B887B7FA8119CA1290F452@AZ-FFEXMB04.global.avaya.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: yes X-MS-TNEF-Correlator: x-originating-ip: [135.64.58.45] Content-Type: multipart/mixed; boundary="_004_9904FB1B0159DA42B0B887B7FA8119CA1290F452AZFFEXMB04globa_" MIME-Version: 1.0 Subject: [coman] FW: [Netconf] Fwd: I-D Action: draft-bierman-netconf-efficiency-extensions-00.txt X-BeenThere: coman@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Management of Constrained Networks and Devices List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 20 Oct 2013 08:04:37 -0000 --_004_9904FB1B0159DA42B0B887B7FA8119CA1290F452AZFFEXMB04globa_ Content-Type: multipart/alternative; boundary="_000_9904FB1B0159DA42B0B887B7FA8119CA1290F452AZFFEXMB04globa_" --_000_9904FB1B0159DA42B0B887B7FA8119CA1290F452AZFFEXMB04globa_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable This I-D seems interesting also in the coman context. Comments should be ad= dressed to the netconf wg list, I guess. Regards, Dan From: netconf-bounces@ietf.org [mailto:netconf-bounces@ietf.org] On Behalf = Of Andy Bierman Sent: Saturday, October 19, 2013 9:34 PM To: Netconf Subject: [Netconf] Fwd: I-D Action: draft-bierman-netconf-efficiency-extens= ions-00.txt Hi, I have written a draft called NETCONF Efficiency Extensions (NETCONF-EX) to propose some optimizations designed to maintain or increase functionality but with significantly less network usage. The goal is to make NETCONF useful in deployments where network resources are severely constrained wrt/ bandwidth, stability, and/or latency. Andy ---------- Forwarded message ---------- From: > Date: Sat, Oct 19, 2013 at 11:26 AM Subject: I-D Action: draft-bierman-netconf-efficiency-extensions-00.txt To: i-d-announce@ietf.org A New Internet-Draft is available from the on-line Internet-Drafts director= ies. Title : NETCONF Efficiency Extensions Author(s) : Andy Bierman Filename : draft-bierman-netconf-efficiency-extensions-00.tx= t Pages : 76 Date : 2013-10-19 Abstract: This document describes protocol extensions to improve the efficiency of the Network Configuration Protocol (NETCONF). Protocol capabilities and operations are defined to reduce network usage and transaction complexity. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-bierman-netconf-efficiency-extension= s There's also a htmlized version available at: http://tools.ietf.org/html/draft-bierman-netconf-efficiency-extensions-00 Please note that it may take a couple of minutes from the time of submissio= n until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ _______________________________________________ I-D-Announce mailing list I-D-Announce@ietf.org https://www.ietf.org/mailman/listinfo/i-d-announce Internet-Draft directories: http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt --_000_9904FB1B0159DA42B0B887B7FA8119CA1290F452AZFFEXMB04globa_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

This I-D seems interestin= g also in the coman context. Comments should be addressed to the netconf wg= list, I guess.

 <= /p>

Regards,

 <= /p>

Dan

 <= /p>

 <= /p>

 <= /p>

From: netconf-bounces@ietf.org [mailto:netconf-bounces@ietf.or= g] On Behalf Of Andy Bierman
Sent: Saturday, October 19, 2013 9:34 PM
To: Netconf
Subject: [Netconf] Fwd: I-D Action: draft-bierman-netconf-efficiency= -extensions-00.txt

 

Hi,

 

I have written a draft ca= lled NETCONF Efficiency Extensions

(NETCONF-EX) to propose s= ome optimizations designed to

maintain or increase func= tionality but with significantly less

network usage.  The = goal is to make NETCONF useful

in deployments where netw= ork resources are severely constrained

wrt/ bandwidth, stability= , and/or latency.

 

 

Andy

 

---------- Forwarded mess= age ----------
From: <internet-drafts@ietf.= org>
Date: Sat, Oct 19, 2013 at 11:26 AM
Subject: I-D Action: draft-bierman-netconf-efficiency-extensions-00.txt
To: i-d-announce@ietf.org



A New Internet-Draft is available from the on-line Internet-Drafts director= ies.


        Title           : NETC= ONF Efficiency Extensions
        Author(s)       : Andy Bierman         Filename        : draft-bie= rman-netconf-efficiency-extensions-00.txt
        Pages           : 76         Date            := 2013-10-19

Abstract:
   This document describes protocol extensions to improve the eff= iciency
   of the Network Configuration Protocol (NETCONF).  Protoco= l
   capabilities and operations are defined to reduce network usag= e and
   transaction complexity.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-bier= man-netconf-efficiency-extensions

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-bierman-netco= nf-efficiency-extensions-00


Please note that it may take a couple of minutes from the time of submissio= n
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp= .ietf.org/internet-drafts/

_______________________________________________
I-D-Announce mailing list
I-D-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/i-d-announce
Internet-Draft directories: http://www.ietf.org/shadow.html
or = ftp://ftp.ietf.org/ietf/1shadow-sites.txt

 

--_000_9904FB1B0159DA42B0B887B7FA8119CA1290F452AZFFEXMB04globa_-- --_004_9904FB1B0159DA42B0B887B7FA8119CA1290F452AZFFEXMB04globa_ Content-Type: text/plain; name="ATT00001.txt" Content-Description: ATT00001.txt Content-Disposition: attachment; filename="ATT00001.txt"; size=136; creation-date="Sat, 19 Oct 2013 18:34:39 GMT"; modification-date="Sat, 19 Oct 2013 18:34:39 GMT" Content-ID: Content-Transfer-Encoding: base64 X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCk5ldGNvbmYg bWFpbGluZyBsaXN0DQpOZXRjb25mQGlldGYub3JnDQpodHRwczovL3d3dy5pZXRmLm9yZy9tYWls bWFuL2xpc3RpbmZvL25ldGNvbmYNCg== --_004_9904FB1B0159DA42B0B887B7FA8119CA1290F452AZFFEXMB04globa_-- From mehmet.ersue@nsn.com Sun Oct 20 03:18:17 2013 Return-Path: X-Original-To: coman@ietfa.amsl.com Delivered-To: coman@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 955D111E83A3 for ; Sun, 20 Oct 2013 03:18:17 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -106.021 X-Spam-Level: X-Spam-Status: No, score=-106.021 tagged_above=-999 required=5 tests=[AWL=0.577, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0LS7GTwBDxyN for ; Sun, 20 Oct 2013 03:18:13 -0700 (PDT) Received: from demumfd001.nsn-inter.net (demumfd001.nsn-inter.net [93.183.12.32]) by ietfa.amsl.com (Postfix) with ESMTP id BE8C411E819C for ; Sun, 20 Oct 2013 03:18:12 -0700 (PDT) Received: from demuprx016.emea.nsn-intra.net ([10.150.129.55]) by demumfd001.nsn-inter.net (8.12.11.20060308/8.12.11) with ESMTP id r9KAI8jw021367 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Sun, 20 Oct 2013 12:18:08 +0200 Received: from DEMUHTC001.nsn-intra.net ([10.159.42.32]) by demuprx016.emea.nsn-intra.net (8.12.11.20060308/8.12.11) with ESMTP id r9KAI6br026024 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Sun, 20 Oct 2013 12:18:07 +0200 Received: from DEMUHTC011.nsn-intra.net (10.159.42.42) by DEMUHTC001.nsn-intra.net (10.159.42.32) with Microsoft SMTP Server (TLS) id 14.3.123.3; Sun, 20 Oct 2013 12:18:06 +0200 Received: from DEMUMBX005.nsn-intra.net ([169.254.5.164]) by DEMUHTC011.nsn-intra.net ([10.159.42.42]) with mapi id 14.03.0123.003; Sun, 20 Oct 2013 12:18:06 +0200 From: "Ersue, Mehmet (NSN - DE/Munich)" To: "ext Romascanu, Dan (Dan)" , "coman@ietf.org" Thread-Topic: [coman] FW: [Netconf] Fwd: I-D Action: draft-bierman-netconf-efficiency-extensions-00.txt Thread-Index: AQHOzPneMkfmYfvqG0ymHzYYgOeItpn9O9YggAAlOJA= Date: Sun, 20 Oct 2013 10:18:05 +0000 Message-ID: References: <9904FB1B0159DA42B0B887B7FA8119CA1290F452@AZ-FFEXMB04.global.avaya.com> In-Reply-To: <9904FB1B0159DA42B0B887B7FA8119CA1290F452@AZ-FFEXMB04.global.avaya.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.159.42.123] Content-Type: multipart/alternative; boundary="_000_E4DE949E6CE3E34993A2FF8AE79131F81CD310DEMUMBX005nsnintr_" MIME-Version: 1.0 X-purgate-type: clean X-purgate-Ad: Categorized by eleven eXpurgate (R) http://www.eleven.de X-purgate: clean X-purgate: This mail is considered clean (visit http://www.eleven.de for further information) X-purgate-size: 13954 X-purgate-ID: 151667::1382264288-00004A43-09F01231/0-0/0-0 Subject: Re: [coman] FW: [Netconf] Fwd: I-D Action: draft-bierman-netconf-efficiency-extensions-00.txt X-BeenThere: coman@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Management of Constrained Networks and Devices List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 20 Oct 2013 10:18:17 -0000 --_000_E4DE949E6CE3E34993A2FF8AE79131F81CD310DEMUMBX005nsnintr_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Yes, it is on the Netconf agenda for IETF #88. Cheers, Mehmet From: coman-bounces@ietf.org [mailto:coman-bounces@ietf.org] On Behalf Of e= xt Romascanu, Dan (Dan) Sent: Sunday, October 20, 2013 10:04 AM To: coman@ietf.org Subject: [coman] FW: [Netconf] Fwd: I-D Action: draft-bierman-netconf-effic= iency-extensions-00.txt This I-D seems interesting also in the coman context. Comments should be ad= dressed to the netconf wg list, I guess. Regards, Dan From: netconf-bounces@ietf.org [mailto:net= conf-bounces@ietf.org] On Behalf Of Andy Bierman Sent: Saturday, October 19, 2013 9:34 PM To: Netconf Subject: [Netconf] Fwd: I-D Action: draft-bierman-netconf-efficiency-extens= ions-00.txt Hi, I have written a draft called NETCONF Efficiency Extensions (NETCONF-EX) to propose some optimizations designed to maintain or increase functionality but with significantly less network usage. The goal is to make NETCONF useful in deployments where network resources are severely constrained wrt/ bandwidth, stability, and/or latency. Andy ---------- Forwarded message ---------- From: > Date: Sat, Oct 19, 2013 at 11:26 AM Subject: I-D Action: draft-bierman-netconf-efficiency-extensions-00.txt To: i-d-announce@ietf.org A New Internet-Draft is available from the on-line Internet-Drafts director= ies. Title : NETCONF Efficiency Extensions Author(s) : Andy Bierman Filename : draft-bierman-netconf-efficiency-extensions-00.tx= t Pages : 76 Date : 2013-10-19 Abstract: This document describes protocol extensions to improve the efficiency of the Network Configuration Protocol (NETCONF). Protocol capabilities and operations are defined to reduce network usage and transaction complexity. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-bierman-netconf-efficiency-extension= s There's also a htmlized version available at: http://tools.ietf.org/html/draft-bierman-netconf-efficiency-extensions-00 Please note that it may take a couple of minutes from the time of submissio= n until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ _______________________________________________ I-D-Announce mailing list I-D-Announce@ietf.org https://www.ietf.org/mailman/listinfo/i-d-announce Internet-Draft directories: http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt --_000_E4DE949E6CE3E34993A2FF8AE79131F81CD310DEMUMBX005nsnintr_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Yes, it is on the Netconf ag= enda for IETF #88.

 

Cheers,
Mehmet

 

From: coman-bo= unces@ietf.org [mailto:coman-bounces@ietf.org] On Behalf Of ext Romascanu, Dan (Dan)
Sent: Sunday, October 20, 2013 10:04 AM
To: coman@ietf.org
Subject: [coman] FW: [Netconf] Fwd: I-D Action: draft-bierman-netcon= f-efficiency-extensions-00.txt

 

This I-D seems interestin= g also in the coman context. Comments should be addressed to the netconf wg= list, I guess.

 <= /p>

Regards,

 <= /p>

Dan

 <= /p>

 <= /p>

 <= /p>

From: netconf-bounces@ietf.org [<= a href=3D"mailto:netconf-bounces@ietf.org">mailto:netconf-bounces@ietf.org<= /a>] On Behalf Of Andy Bierman
Sent: Saturday, October 19, 2013 9:34 PM
To: Netconf
Subject: [Netconf] Fwd: I-D Action: draft-bierman-netconf-efficiency= -extensions-00.txt

 

Hi,

 

I have written a draft = called NETCONF Efficiency Extensions

(NETCONF-EX) to propose= some optimizations designed to

maintain or increase fu= nctionality but with significantly less

network usage.  Th= e goal is to make NETCONF useful

in deployments where ne= twork resources are severely constrained

wrt/ bandwidth, stabili= ty, and/or latency.

 

 

Andy

 

---------- Forwarded me= ssage ----------
From: <internet-drafts@ietf.= org>
Date: Sat, Oct 19, 2013 at 11:26 AM
Subject: I-D Action: draft-bierman-netconf-efficiency-extensions-00.txt
To: i-d-announce@ietf.org



A New Internet-Draft is available from the on-line Internet-Drafts director= ies.


        Title           : NETC= ONF Efficiency Extensions
        Author(s)       : Andy Bierman         Filename        : draft-bie= rman-netconf-efficiency-extensions-00.txt
        Pages           : 76         Date            := 2013-10-19

Abstract:
   This document describes protocol extensions to improve the eff= iciency
   of the Network Configuration Protocol (NETCONF).  Protoco= l
   capabilities and operations are defined to reduce network usag= e and
   transaction complexity.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-bier= man-netconf-efficiency-extensions

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-bierman-netco= nf-efficiency-extensions-00


Please note that it may take a couple of minutes from the time of submissio= n
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp= .ietf.org/internet-drafts/

_______________________________________________
I-D-Announce mailing list
I-D-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/i-d-announce
Internet-Draft directories: http://www.ietf.org/shadow.html
or = ftp://ftp.ietf.org/ietf/1shadow-sites.txt

 

--_000_E4DE949E6CE3E34993A2FF8AE79131F81CD310DEMUMBX005nsnintr_-- From mehmet.ersue@nsn.com Tue Oct 22 00:26:54 2013 Return-Path: X-Original-To: coman@ietfa.amsl.com Delivered-To: coman@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C3F3E11E8327; Tue, 22 Oct 2013 00:26:54 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -106.165 X-Spam-Level: X-Spam-Status: No, score=-106.165 tagged_above=-999 required=5 tests=[AWL=0.433, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HUaTdeotcy9c; Tue, 22 Oct 2013 00:26:50 -0700 (PDT) Received: from demumfd001.nsn-inter.net (demumfd001.nsn-inter.net [93.183.12.32]) by ietfa.amsl.com (Postfix) with ESMTP id 97B7A11E8355; Tue, 22 Oct 2013 00:26:49 -0700 (PDT) Received: from demuprx016.emea.nsn-intra.net ([10.150.129.55]) by demumfd001.nsn-inter.net (8.12.11.20060308/8.12.11) with ESMTP id r9M7Qlnl001188 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Tue, 22 Oct 2013 09:26:47 +0200 Received: from DEMUHTC003.nsn-intra.net ([10.159.42.34]) by demuprx016.emea.nsn-intra.net (8.12.11.20060308/8.12.11) with ESMTP id r9M7Qlw0020432 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 22 Oct 2013 09:26:47 +0200 Received: from DEMUHTC006.nsn-intra.net (10.159.42.37) by DEMUHTC003.nsn-intra.net (10.159.42.34) with Microsoft SMTP Server (TLS) id 14.3.123.3; Tue, 22 Oct 2013 09:26:47 +0200 Received: from DEMUMBX005.nsn-intra.net ([169.254.5.164]) by DEMUHTC006.nsn-intra.net ([10.159.42.37]) with mapi id 14.03.0123.003; Tue, 22 Oct 2013 09:26:46 +0200 From: "Ersue, Mehmet (NSN - DE/Munich)" To: "coman@ietf.org" , "lwip@ietf.org" , "core@ietf.org" , "6lo@ietf.org" <6lo@ietf.org> Thread-Topic: draft-opsawg-ersue-coman-*-00 Thread-Index: Ac7OlqYtF57/mMmbQ2uDVQpY5NHw2QAWxt+g Date: Tue, 22 Oct 2013 07:26:46 +0000 Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: yes X-MS-TNEF-Correlator: x-originating-ip: [10.159.42.99] Content-Type: multipart/mixed; boundary="_005_E4DE949E6CE3E34993A2FF8AE79131F81CFF9DDEMUMBX005nsnintr_" MIME-Version: 1.0 X-purgate-type: clean X-purgate-Ad: Categorized by eleven eXpurgate (R) http://www.eleven.de X-purgate: clean X-purgate: This mail is considered clean (visit http://www.eleven.de for further information) X-purgate-size: 20160 X-purgate-ID: 151667::1382426807-00004A43-A310E959/0-0/0-0 Subject: [coman] FW: draft-opsawg-ersue-coman-*-00 X-BeenThere: coman@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Management of Constrained Networks and Devices List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Oct 2013 07:26:54 -0000 --_005_E4DE949E6CE3E34993A2FF8AE79131F81CFF9DDEMUMBX005nsnintr_ Content-Type: multipart/alternative; boundary="_000_E4DE949E6CE3E34993A2FF8AE79131F81CFF9DDEMUMBX005nsnintr_" --_000_E4DE949E6CE3E34993A2FF8AE79131F81CFF9DDEMUMBX005nsnintr_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable FYI Mehmet From: ext Ersue, Mehmet (NSN - DE/Munich) [mailto:mehmet.ersue@nsn.com] Sent: Monday, October 21, 2013 9:49 PM To: opsawg@ietf.org Cc: ops-chairs@tools.ietf.org Subject: draft-opsawg-ersue-coman-*-00 Hi All, we submitted following two drafts by dividing the original Coman draft draf= t-ersue-constrained-mgmt-03 into two parts: Filename: draft-opsawg-ersue-coman-probstate-reqs Title: Management of Networks with Constrained Devices: Problem S= tatement and Requirements Htmlized: http://tools.ietf.org/html/draft-opsawg-ersue-coman-probst= ate-reqs-00 Filename: draft-opsawg-ersue-coman-use-cases Title: Management of Networks with Constrained Devices: Use Cases Htmlized: http://tools.ietf.org/html/draft-opsawg-ersue-coman-use-cas= es-00 We also asked OPSAWG chairs for a time slot to introduce the drafts and dis= cuss issues. We would appreciate your comments and a discussion on these drafts. Please send your comments to the OPSAWG maillist. Regards, Mehmet --_000_E4DE949E6CE3E34993A2FF8AE79131F81CFF9DDEMUMBX005nsnintr_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

FYI

 

Mehmet

 

From: ext Ersu= e, Mehmet (NSN - DE/Munich) [mailto:mehmet.ersue@nsn.com]
Sent: Monday, October 21, 2013 9:49 PM
To: opsawg@ietf.org
Cc: ops-chairs@tools.ietf.org
Subject: draft-opsawg-ersue-coman-*-00

 

Hi All,

 

we submitted following two drafts by di= viding the original Coman draft draft-ersue-constrained-mgm= t-03 into two parts:

 

Filename:     =    draft-opsawg-ersue-coman-probstate-reqs

Title:     &nb= sp;     Management of Networks with Constrained Devices= : Problem Statement and Requirements

 

Filename:     =    draft-opsawg-ersue-coman-use-cases

Title:     &nb= sp;     Management of Networks with Constrained Devices= : Use Cases

 

We also asked OPSAWG chairs for a time = slot to introduce the drafts and discuss issues.

 

We would appreciate your comments and a= discussion on these drafts.

Please send your comments to the OPSAWG= maillist.

 

Regards,
Mehmet

 

 

 

--_000_E4DE949E6CE3E34993A2FF8AE79131F81CFF9DDEMUMBX005nsnintr_-- --_005_E4DE949E6CE3E34993A2FF8AE79131F81CFF9DDEMUMBX005nsnintr_ Content-Type: message/rfc822 Content-Disposition: attachment; creation-date="Mon, 21 Oct 2013 19:49:27 GMT"; modification-date="Mon, 21 Oct 2013 19:49:27 GMT" Content-ID: Received: from DEMUHTC006.nsn-intra.net (10.159.42.37) by DEMUHTC007.nsn-intra.net (10.159.42.38) with Microsoft SMTP Server (TLS) id 14.3.123.3; Mon, 21 Oct 2013 20:54:17 +0200 Received: from demuprx016.emea.nsn-intra.net (10.159.42.124) by DEMUHTC006.nsn-intra.net (10.159.42.37) with Microsoft SMTP Server (TLS) id 14.3.123.3; Mon, 21 Oct 2013 20:54:16 +0200 Received: from mumrelp001.nsn-inter.net (mumrelp001.nsn-inter.net [93.183.13.135]) by demuprx016.emea.nsn-intra.net (8.12.11.20060308/8.12.11) with ESMTP id r9LIsGLt013181 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Mon, 21 Oct 2013 20:54:16 +0200 Received: from mail.ietf.org (mail.ietf.org [12.22.58.30]) by mumrelp001.nsn-inter.net (8.13.8/8.13.8) with ESMTP id r9LIsGtO015396 for ; Mon, 21 Oct 2013 20:54:16 +0200 Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 85EAB11E8238; Mon, 21 Oct 2013 11:54:15 -0700 (PDT) Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dF1g3msh2mBQ; Mon, 21 Oct 2013 11:54:13 -0700 (PDT) Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id E9DFD11E840D; Mon, 21 Oct 2013 11:54:08 -0700 (PDT) From: "ext internet-drafts@ietf.org" To: Dan Romascanu , Juergen Schoenwaelder , "Ersue, Mehmet (NSN - DE/Munich)" Subject: New Version Notification for draft-opsawg-ersue-coman-probstate-reqs-00.txt Thread-Topic: New Version Notification for draft-opsawg-ersue-coman-probstate-reqs-00.txt Thread-Index: AQHOzo7xgMDHISK6VE++bt9ABi2s3Q== Date: Mon, 21 Oct 2013 18:54:08 +0000 Message-ID: <20131021185408.32548.16277.idtracker@ietfa.amsl.com> Content-Language: en-US X-MS-Exchange-Organization-AuthAs: Anonymous X-MS-Exchange-Organization-AuthSource: DEMUHTC006.nsn-intra.net X-MS-Has-Attach: X-Auto-Response-Suppress: All X-MS-TNEF-Correlator: x-purgate-id: 151667::1382381656-00005789-530842F7/0-0/0-0 x-purgate-ad: Categorized by eleven eXpurgate (R) http://www.eleven.de x-purgate: This mail is considered clean (visit http://www.eleven.de for further information) x-purgate-size: 1175 x-purgate-type: clean x-virus-scanned: amavisd-new at amsl.com auto-submitted: auto-generated x-scanned-by: MIMEDefang 2.71 on 93.183.13.135 Content-Type: text/plain; charset="utf-8" Content-ID: <3F5AC62326FFE44697C3BD694A3B2368@internal.nsn.com> Content-Transfer-Encoding: base64 MIME-Version: 1.0 DQpBIG5ldyB2ZXJzaW9uIG9mIEktRCwgZHJhZnQtb3BzYXdnLWVyc3VlLWNvbWFuLXByb2JzdGF0 ZS1yZXFzLTAwLnR4dA0KaGFzIGJlZW4gc3VjY2Vzc2Z1bGx5IHN1Ym1pdHRlZCBieSBNZWhtZXQg RXJzdWUgYW5kIHBvc3RlZCB0byB0aGUNCklFVEYgcmVwb3NpdG9yeS4NCg0KRmlsZW5hbWU6ICAg ICAgICBkcmFmdC1vcHNhd2ctZXJzdWUtY29tYW4tcHJvYnN0YXRlLXJlcXMNClJldmlzaW9uOiAg ICAgICAgMDANClRpdGxlOiAgICAgICAgICAgTWFuYWdlbWVudCBvZiBOZXR3b3JrcyB3aXRoIENv bnN0cmFpbmVkIERldmljZXM6IFByb2JsZW0gU3RhdGVtZW50IGFuZCBSZXF1aXJlbWVudHMNCkNy ZWF0aW9uIGRhdGU6ICAgMjAxMy0xMC0yMQ0KR3JvdXA6ICAgICAgICAgICBJbmRpdmlkdWFsIFN1 Ym1pc3Npb24NCk51bWJlciBvZiBwYWdlczogNTYNClVSTDogICAgICAgICAgICAgaHR0cDovL3d3 dy5pZXRmLm9yZy9pbnRlcm5ldC1kcmFmdHMvZHJhZnQtb3BzYXdnLWVyc3VlLWNvbWFuLXByb2Jz dGF0ZS1yZXFzLTAwLnR4dA0KU3RhdHVzOiAgICAgICAgICBodHRwOi8vZGF0YXRyYWNrZXIuaWV0 Zi5vcmcvZG9jL2RyYWZ0LW9wc2F3Zy1lcnN1ZS1jb21hbi1wcm9ic3RhdGUtcmVxcw0KSHRtbGl6 ZWQ6ICAgICAgICBodHRwOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9kcmFmdC1vcHNhd2ctZXJzdWUt Y29tYW4tcHJvYnN0YXRlLXJlcXMtMDANCg0KDQpBYnN0cmFjdDoNCiAgIFRoaXMgZG9jdW1lbnQg cHJvdmlkZXMgYSBwcm9ibGVtIHN0YXRlbWVudCwgZGVwbG95bWVudCBhbmQgbWFuYWdlbWVudA0K ICAgdG9wb2xvZ3kgb3B0aW9ucyBhcyB3ZWxsIGFzIHRoZSByZXF1aXJlbWVudHMgZm9yIHRoZSBt YW5hZ2VtZW50IG9mDQogICBuZXR3b3JrcyB3aGVyZSBjb25zdHJhaW5lZCBkZXZpY2VzIGFyZSBp bnZvbHZlZC4NCg0KDQoNCg0KUGxlYXNlIG5vdGUgdGhhdCBpdCBtYXkgdGFrZSBhIGNvdXBsZSBv ZiBtaW51dGVzIGZyb20gdGhlIHRpbWUgb2Ygc3VibWlzc2lvbg0KdW50aWwgdGhlIGh0bWxpemVk IHZlcnNpb24gYW5kIGRpZmYgYXJlIGF2YWlsYWJsZSBhdCB0b29scy5pZXRmLm9yZy4NCg0KVGhl IElFVEYgU2VjcmV0YXJpYXQNCg0K --_005_E4DE949E6CE3E34993A2FF8AE79131F81CFF9DDEMUMBX005nsnintr_ Content-Type: message/rfc822 Content-Disposition: attachment; creation-date="Mon, 21 Oct 2013 19:49:28 GMT"; modification-date="Mon, 21 Oct 2013 19:49:28 GMT" Content-ID: <5BB3535A3401FE4D9F71C9FF967FB1E9@internal.nsn.com> Received: from DEMUHTC010.nsn-intra.net (10.159.42.41) by DEMUHTC007.nsn-intra.net (10.159.42.38) with Microsoft SMTP Server (TLS) id 14.3.123.3; Mon, 21 Oct 2013 20:55:41 +0200 Received: from demuprx017.emea.nsn-intra.net (10.159.42.97) by DEMUHTC010.nsn-intra.net (10.159.42.41) with Microsoft SMTP Server (TLS) id 14.3.123.3; Mon, 21 Oct 2013 20:55:41 +0200 Received: from demumfd002.nsn-inter.net (DEMUMFD002 [93.183.12.31]) by demuprx017.emea.nsn-intra.net (8.12.11.20060308/8.12.11) with ESMTP id r9LItfsZ005813 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Mon, 21 Oct 2013 20:55:41 +0200 Received: from mail.ietf.org (mail.ietf.org [12.22.58.30]) by demumfd002.nsn-inter.net (8.12.11.20060308/8.12.11) with ESMTP id r9LIteO0003660 for ; Mon, 21 Oct 2013 20:55:40 +0200 Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0974D11E861C; Mon, 21 Oct 2013 11:55:40 -0700 (PDT) Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wovqHH-a08U9; Mon, 21 Oct 2013 11:55:39 -0700 (PDT) Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 2DD7F11E856E; Mon, 21 Oct 2013 11:55:10 -0700 (PDT) From: "ext internet-drafts@ietf.org" To: Dan Romascanu , Juergen Schoenwaelder , "Ersue, Mehmet (NSN - DE/Munich)" Subject: New Version Notification for draft-opsawg-ersue-coman-use-cases-00.txt Thread-Topic: New Version Notification for draft-opsawg-ersue-coman-use-cases-00.txt Thread-Index: AQHOzo8jFGmhc5H0FkCR10dedIYG3Q== Date: Mon, 21 Oct 2013 18:55:10 +0000 Message-ID: <20131021185510.32482.68231.idtracker@ietfa.amsl.com> Content-Language: en-US X-MS-Exchange-Organization-AuthAs: Anonymous X-MS-Exchange-Organization-AuthSource: DEMUHTC010.nsn-intra.net X-MS-Has-Attach: X-Auto-Response-Suppress: All X-MS-TNEF-Correlator: x-purgate-id: 151667::1382381741-00005753-F1DC8E4D/0-0/0-0 x-purgate-ad: Categorized by eleven eXpurgate (R) http://www.eleven.de x-purgate: This mail is considered clean (visit http://www.eleven.de for further information) x-purgate-size: 1215 x-purgate-type: clean x-virus-scanned: amavisd-new at amsl.com auto-submitted: auto-generated Content-Type: text/plain; charset="utf-8" Content-ID: Content-Transfer-Encoding: base64 MIME-Version: 1.0 DQpBIG5ldyB2ZXJzaW9uIG9mIEktRCwgZHJhZnQtb3BzYXdnLWVyc3VlLWNvbWFuLXVzZS1jYXNl cy0wMC50eHQNCmhhcyBiZWVuIHN1Y2Nlc3NmdWxseSBzdWJtaXR0ZWQgYnkgTWVobWV0IEVyc3Vl IGFuZCBwb3N0ZWQgdG8gdGhlDQpJRVRGIHJlcG9zaXRvcnkuDQoNCkZpbGVuYW1lOiAgICAgICAg ZHJhZnQtb3BzYXdnLWVyc3VlLWNvbWFuLXVzZS1jYXNlcw0KUmV2aXNpb246ICAgICAgICAwMA0K VGl0bGU6ICAgICAgICAgICBNYW5hZ2VtZW50IG9mIE5ldHdvcmtzIHdpdGggQ29uc3RyYWluZWQg RGV2aWNlczogVXNlIENhc2VzDQpDcmVhdGlvbiBkYXRlOiAgIDIwMTMtMTAtMjENCkdyb3VwOiAg ICAgICAgICAgSW5kaXZpZHVhbCBTdWJtaXNzaW9uDQpOdW1iZXIgb2YgcGFnZXM6IDMzDQpVUkw6 ICAgICAgICAgICAgIGh0dHA6Ly93d3cuaWV0Zi5vcmcvaW50ZXJuZXQtZHJhZnRzL2RyYWZ0LW9w c2F3Zy1lcnN1ZS1jb21hbi11c2UtY2FzZXMtMDAudHh0DQpTdGF0dXM6ICAgICAgICAgIGh0dHA6 Ly9kYXRhdHJhY2tlci5pZXRmLm9yZy9kb2MvZHJhZnQtb3BzYXdnLWVyc3VlLWNvbWFuLXVzZS1j YXNlcw0KSHRtbGl6ZWQ6ICAgICAgICBodHRwOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9kcmFmdC1v cHNhd2ctZXJzdWUtY29tYW4tdXNlLWNhc2VzLTAwDQoNCg0KQWJzdHJhY3Q6DQogICBUaGlzIGRv Y3VtZW50IGRpc2N1c3NlcyB0aGUgdXNlIGNhc2VzIGNvbmNlcm5pbmcgdGhlIG1hbmFnZW1lbnQg b2YNCiAgIG5ldHdvcmtzLCB3aGVyZSBjb25zdHJhaW5lZCBkZXZpY2VzIGFyZSBpbnZvbHZlZC4g IEEgcHJvYmxlbQ0KICAgc3RhdGVtZW50LCBkZXBsb3ltZW50IG9wdGlvbnMgYW5kIHRoZSByZXF1 aXJlbWVudHMgb24gdGhlIG5ldHdvcmtzDQogICB3aXRoIGNvbnN0cmFpbmVkIGRldmljZXMgY2Fu IGJlIGZvdW5kIGluIHRoZSBjb21wYW5pb24gZG9jdW1lbnQgW0NPTS0NCiAgIFJFUV0uDQoNCg0K DQoNClBsZWFzZSBub3RlIHRoYXQgaXQgbWF5IHRha2UgYSBjb3VwbGUgb2YgbWludXRlcyBmcm9t IHRoZSB0aW1lIG9mIHN1Ym1pc3Npb24NCnVudGlsIHRoZSBodG1saXplZCB2ZXJzaW9uIGFuZCBk aWZmIGFyZSBhdmFpbGFibGUgYXQgdG9vbHMuaWV0Zi5vcmcuDQoNClRoZSBJRVRGIFNlY3JldGFy aWF0DQoNCg== --_005_E4DE949E6CE3E34993A2FF8AE79131F81CFF9DDEMUMBX005nsnintr_--