Re: [6lowapp] Next rev of CoRE Charter
JP Vasseur <jvasseur@cisco.com> Thu, 04 February 2010 20:06 UTC
Return-Path: <jvasseur@cisco.com>
X-Original-To: 6lowapp@core3.amsl.com
Delivered-To: 6lowapp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8455E3A6E1A for <6lowapp@core3.amsl.com>; Thu, 4 Feb 2010 12:06:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.652
X-Spam-Level:
X-Spam-Status: No, score=-9.652 tagged_above=-999 required=5 tests=[AWL=0.946, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dEkhWrVfUZCJ for <6lowapp@core3.amsl.com>; Thu, 4 Feb 2010 12:06:48 -0800 (PST)
Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149]) by core3.amsl.com (Postfix) with ESMTP id D20533A6CD5 for <6lowapp@ietf.org>; Thu, 4 Feb 2010 12:06:47 -0800 (PST)
Authentication-Results: rtp-iport-2.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AloFAIe3aktAZnwM/2dsb2JhbACPVq9ymAOETAQ
X-IronPort-AV: E=Sophos; i="4.49,406,1262563200"; d="scan'208,217"; a="84093121"
Received: from rtp-core-1.cisco.com ([64.102.124.12]) by rtp-iport-2.cisco.com with ESMTP; 04 Feb 2010 20:07:34 +0000
Received: from xbh-ams-201.cisco.com (xbh-ams-201.cisco.com [144.254.75.7]) by rtp-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id o14K7YWU002334; Thu, 4 Feb 2010 20:07:34 GMT
Received: from xfe-ams-102.cisco.com ([144.254.231.94]) by xbh-ams-201.cisco.com with Microsoft SMTPSVC(6.0.3790.3959); Thu, 4 Feb 2010 21:07:34 +0100
Received: from ams-jvasseur-8712.cisco.com ([10.55.201.131]) by xfe-ams-102.cisco.com with Microsoft SMTPSVC(6.0.3790.3959); Thu, 4 Feb 2010 21:07:32 +0100
Message-Id: <A8F748EE-D394-4CD5-AD79-BF3CFB76B14E@cisco.com>
From: JP Vasseur <jvasseur@cisco.com>
To: Kerry Lynn <kerlyn2001@gmail.com>, Zach Shelby <zach@sensinode.com>
In-Reply-To: <3fe58b591002041127v680b1dfu487f5b2fdf503b26@mail.gmail.com>
Content-Type: multipart/alternative; boundary="Apple-Mail-514--755956805"
Mime-Version: 1.0 (Apple Message framework v936)
Date: Thu, 04 Feb 2010 21:07:31 +0100
References: <2A7B1CDC-5B99-47E8-9331-039D5997E1CC@cisco.com> <DFC50C8B-D84B-43E6-9691-503CC840ED5B@cisco.com> <EDB52132-2F9A-4201-BDB3-35B550428FEC@cisco.com> <A69482D3-B85B-4E28-A574-BCD9E17743B6@cisco.com> <48FC8D18-9377-41C0-A0EF-39B9D8B6F646@sensinode.com> <3fe58b591002040648j389b0090p93a69f7ae4f7f46e@mail.gmail.com> <D8912181-7D58-4892-9D7E-A3D1FD65F73A@sensinode.com> <3fe58b591002041127v680b1dfu487f5b2fdf503b26@mail.gmail.com>
X-Mailer: Apple Mail (2.936)
X-OriginalArrivalTime: 04 Feb 2010 20:07:32.0870 (UTC) FILETIME=[AFC01A60:01CAA5D5]
X-TM-AS-Product-Ver: SMEX-8.0.0.1181-6.000.1038-17174.001
X-TM-AS-Result: No--22.375900-8.000000-31
X-TM-AS-User-Approved-Sender: No
X-TM-AS-User-Blocked-Sender: No
Cc: 6lowapp@ietf.org
Subject: Re: [6lowapp] Next rev of CoRE Charter
X-BeenThere: 6lowapp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Application protocols for constrained nodes and networks <6lowapp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/6lowapp>, <mailto:6lowapp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/6lowapp>
List-Post: <mailto:6lowapp@ietf.org>
List-Help: <mailto:6lowapp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/6lowapp>, <mailto:6lowapp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Feb 2010 20:06:49 -0000
>> >>> So the >>> naming/discovery choice >>> should be one that is lightweight and purpose-built for service >>> discovery. >>> See draft-cheshire-dnsext-multicastdns-08.txt for an existence proof >>> and draft-cheshire-dnsext-dns-sd-05.txt, its complimentary >>> extension. >>> To get a feeling for what these drafts mean by "service", see the >>> list at >>> http://www.dns-sd.org/ServiceTypes.html >> >> Sure, if you need general service discovery there is nothing >> stopping you from using these (this was discussed in the BOF). In >> fact the charter already mentions that any naming for resources >> should be compatible with e.g. mDNS naming. >> >> What would make you happy here (yet still get us a WG)? We could of >> course include text saying that we will recommend a service >> discovery protocol that should be used in addition to CoAP, if such >> a step is needed. Cullen, do you think that is still compatible >> with the BOF? >> > KL> That language would make me happy :) > Me too. Cheers. JP. > Regards, -K- >> Zach >> >>> >>> Regards, -K- >>> >>> >>>> Zach >>>> >>>> >>>> -- >>>> http://www.sensinode.com >>>> http://zachshelby.org - My blog "On the Internet of Things" >>>> http://6lowpan.net - New book - "6LoWPAN: The Wireless Embedded >>>> Internet" >>>> Mobile: +358 40 7796297 >>>> >>>> Zach Shelby >>>> Head of Research >>>> Sensinode Ltd. >>>> Kidekuja 2 >>>> 88610 Vuokatti, FINLAND >>>> >>>> This e-mail and all attached material are confidential and may >>>> contain legally privileged information. If you are not the >>>> intended recipient, please contact the sender and delete the e- >>>> mail from your system without producing, distributing or >>>> retaining copies thereof. >>>> >>>> >>>> >>>> >>>> _______________________________________________ >>>> 6lowapp mailing list >>>> 6lowapp@ietf.org >>>> https://www.ietf.org/mailman/listinfo/6lowapp >>>> >> >> -- >> http://www.sensinode.com >> http://zachshelby.org - My blog "On the Internet of Things" >> http://6lowpan.net - New book - "6LoWPAN: The Wireless Embedded >> Internet" >> Mobile: +358 40 7796297 >> >> Zach Shelby >> Head of Research >> Sensinode Ltd. >> Kidekuja 2 >> 88610 Vuokatti, FINLAND >> >> This e-mail and all attached material are confidential and may >> contain legally privileged information. If you are not the intended >> recipient, please contact the sender and delete the e-mail from >> your system without producing, distributing or retaining copies >> thereof. >> >> >> >> >>
- [6lowapp] Next rev of CoRE Charter Cullen Jennings
- Re: [6lowapp] Next rev of CoRE Charter Behcet Sarikaya
- Re: [6lowapp] Next rev of CoRE Charter JP Vasseur
- Re: [6lowapp] Next rev of CoRE Charter Cullen Jennings
- Re: [6lowapp] Next rev of CoRE Charter Cullen Jennings
- Re: [6lowapp] Next rev of CoRE Charter Behcet Sarikaya
- Re: [6lowapp] Next rev of CoRE Charter Carsten Bormann
- Re: [6lowapp] Next rev of CoRE Charter JP Vasseur
- Re: [6lowapp] Next rev of CoRE Charter JP Vasseur
- Re: [6lowapp] Next rev of CoRE Charter Robert Cragie
- Re: [6lowapp] Next rev of CoRE Charter Robert Cragie
- Re: [6lowapp] Next rev of CoRE Charter Zach Shelby
- Re: [6lowapp] Next rev of CoRE Charter Kerry Lynn
- Re: [6lowapp] Next rev of CoRE Charter Zach Shelby
- Re: [6lowapp] Next rev of CoRE Charter Kerry Lynn
- Re: [6lowapp] Next rev of CoRE Charter JP Vasseur