From nobody Fri May 1 08:39:13 2015 Return-Path: X-Original-To: p2psip@ietfa.amsl.com Delivered-To: p2psip@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2395D1A1B1C for ; Fri, 1 May 2015 08:39:13 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -14.511 X-Spam-Level: X-Spam-Status: No, score=-14.511 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hIymEEfqBP9q for ; Fri, 1 May 2015 08:39:11 -0700 (PDT) Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 913D81A01CB for ; Fri, 1 May 2015 08:39:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2005; q=dns/txt; s=iport; t=1430494751; x=1431704351; h=from:to:subject:date:message-id:references:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=eF2tLnb5/a5vrrTFBaLDnOxDkx23lXc68qYUmSdS0zk=; b=O8D5jiB25xXapnbtdawlvBtwPt7iaf1OGDN3kGj8jrUAEDHm94g6glRM Iv7qYBRxhf6jM/BBsNq79uXcN1Y1Fm1iYpOzdUcwtcneiVdFZxOYL/iyN bmeuOjLub7zzeaT34Ek+n41selzSx52Ekpc2X/bko16VcFt3dJchj9Lbu 4=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: A0AQBQAWnUNV/5NdJa1cFoJ2U1wFx0AKhTZOAoFaTAEBAQEBAYELhCEBAQQBAQE3NBsCAQgkEgkHJwsUBwEGAwIEExSIFw3HEwEBAQEBAQQBAQEBAQEBARqLOIUMhC0FkW+ECoZAgSM9gw6JYYNeg1AjYIMUbwGBQ4EBAQEB X-IronPort-AV: E=Sophos;i="5.13,350,1427760000"; d="scan'208";a="413225697" Received: from rcdn-core-11.cisco.com ([173.37.93.147]) by rcdn-iport-9.cisco.com with ESMTP; 01 May 2015 15:39:10 +0000 Received: from xhc-aln-x10.cisco.com (xhc-aln-x10.cisco.com [173.36.12.84]) by rcdn-core-11.cisco.com (8.14.5/8.14.5) with ESMTP id t41FdAel028921 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for ; Fri, 1 May 2015 15:39:10 GMT Received: from xmb-aln-x08.cisco.com ([169.254.3.36]) by xhc-aln-x10.cisco.com ([173.36.12.84]) with mapi id 14.03.0195.001; Fri, 1 May 2015 10:39:10 -0500 From: "Charles Eckel (eckelcu)" To: "p2psip@ietf.org" Thread-Topic: [hackathon] RIOT@IETF 93 Hackathon Thread-Index: AQHQg4nsg0J+QYGuz0eQ9YK+5mvqPZ1nIVEA Date: Fri, 1 May 2015 15:39:10 +0000 Message-ID: References: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.4.9.150325 x-originating-ip: [10.24.81.226] Content-Type: text/plain; charset="us-ascii" Content-ID: Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Archived-At: Subject: [P2PSIP] FW: [hackathon] RIOT@IETF 93 Hackathon X-BeenThere: p2psip@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Peer-to-Peer SIP working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 May 2015 15:39:13 -0000 FYI, There will be an IETF Hackathon in Prague, July 18-19. We are in the process of determining the set of technologies included and are using hackathon@ietf.org for all discussions related to the hackathon. I thought this working group might be interested to work with RIOT and related technologies at the hackathon. If so, please subscribe the list (https://www.ietf.org/mailman/listinfo/hackathon) and participate in the discussions there. Cheers, Charles On 4/30/15, 1:02 PM, "Matthias Waehlisch" wrote: >Hi Charles, all, > > several people from the RIOT community (http://www.riot-os.org) will >attend the upcoming IETF meeting and are pleased to work on IETF-related >topics during the Hackathon. We plan to give an introduction to RIOT >such that non-RIOTers can easily start with implementing their own ideas >on this operating system for constrained devices. > > So far we have the following champions assigned to topics: > > (1) Lotte Steenbrink: update of AODVv2 (see draft-ietf-manet-aodvv2) > =20 > (2) Hauke Petersen: CoAP for service discovery in the IoT (see >draft-jimenez-p2psip-coap-reload) > > (3) Martine Lenders: general IoT network stack and boarder gateway >between the IoT and current Internet > > (4) Kaspar Schleiser: ICN > > > Anybody who is interested in working on these topics is more than >welcome to join! If you have your own topic and want to implement this >on RIOT, let us know in advance and we will tailor introduction etc. > > > >Thanks > matthias > >--=20 >Matthias Waehlisch >. Freie Universitaet Berlin, Inst. fuer Informatik, AG CST >. Takustr. 9, D-14195 Berlin, Germany >.. mailto:waehlisch@ieee.org .. http://www.inf.fu-berlin.de/~waehl >:. Also: http://inet.cpt.haw-hamburg.de .. http://www.link-lab.net > >_______________________________________________ >hackathon mailing list >hackathon@ietf.org >https://www.ietf.org/mailman/listinfo/hackathon From nobody Fri May 8 13:50:11 2015 Return-Path: X-Original-To: p2psip@ietfa.amsl.com Delivered-To: p2psip@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E156D1A88E7; Fri, 8 May 2015 13:50:07 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.9 X-Spam-Level: X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9MLrzrVZydH9; Fri, 8 May 2015 13:50:06 -0700 (PDT) Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id B33361A885E; Fri, 8 May 2015 13:50:06 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: internet-drafts@ietf.org To: X-Test-IDTracker: no X-IETF-IDTracker: 6.0.2.p2 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <20150508205006.28576.56409.idtracker@ietfa.amsl.com> Date: Fri, 08 May 2015 13:50:06 -0700 Archived-At: Cc: p2psip@ietf.org Subject: [P2PSIP] I-D Action: draft-ietf-p2psip-concepts-07.txt X-BeenThere: p2psip@ietf.org X-Mailman-Version: 2.1.15 List-Id: Peer-to-Peer SIP working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 May 2015 20:50:08 -0000 A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Peer-to-Peer Session Initiation Protocol Working Group of the IETF. Title : Concepts and Terminology for Peer to Peer SIP Authors : David A. Bryan Philip Matthews Eunsoo Shim Dean Willis Spencer Dawkins Filename : draft-ietf-p2psip-concepts-07.txt Pages : 20 Date : 2015-05-08 Abstract: This document defines concepts and terminology for the use of the Session Initiation Protocol in a peer-to-peer environment where the traditional proxy-registrar and message routing functions are replaced by a distributed mechanism. These mechanisms may be implemented using a distributed hash table or other distributed data mechanism with similar external properties. This document includes a high-level view of the functional relationships between the network elements defined herein, a conceptual model of operations, and an outline of the related problems addressed by the P2PSIP working group and the RELOAD protocol and SIP usage ([RFC6940], [I-D.ietf-p2psip-sip]) defined by the working group. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-p2psip-concepts/ There's also a htmlized version available at: https://tools.ietf.org/html/draft-ietf-p2psip-concepts-07 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-p2psip-concepts-07 Please note that it may take a couple of minutes from the time of submission 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/ From nobody Mon May 11 10:36:57 2015 Return-Path: X-Original-To: p2psip@ietfa.amsl.com Delivered-To: p2psip@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 76D2D1ACE44 for ; Mon, 11 May 2015 10:36:56 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0 X-Spam-Level: X-Spam-Status: No, score=0 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TfasxKbRDUk5 for ; Mon, 11 May 2015 10:36:54 -0700 (PDT) Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B408D1ACE3F for ; Mon, 11 May 2015 10:36:48 -0700 (PDT) Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.nyi.internal (Postfix) with ESMTP id 2CE8520B48 for ; Mon, 11 May 2015 13:36:48 -0400 (EDT) Received: from frontend2 ([10.202.2.161]) by compute5.internal (MEProxy); Mon, 11 May 2015 13:36:48 -0400 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=cooperw.in; h=cc :content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-sasl-enc :x-sasl-enc; s=mesmtp; bh=sKdWiYNR7oARrhecrR2axDASJaU=; b=T+rOer K++BwBh3fckm9Zwq5cHTDPZyzCpvN9WLoQQlYkVcmOhAc36V/X65h6AKBdm9MuMg W6R8TAcEQMMVevqhdevz07pnfCfIlHvQBzJcIb1cta7qVxWOtGolq6dp+VYd+FGs y+E+xZ/PiSfZQg4nLBKwWbswkOnvNoGvkIw8g= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-sasl-enc:x-sasl-enc; s=smtpout; bh=sKdWiYNR7oARrhe crR2axDASJaU=; b=lUPdcS6sSfslswjH7ITjzod9YNTX9y1uLDUmfszr98yl+4W fCSygbGyOjxPSOPkUnJp0M5g8wJ/WWKWEFKVX8ypOAFiIcjBwwvgNoARB+xDvi6E l71aF9gfvOPMQGcSz5ete+iGhRHxOBLnus3by23xMLZsg55o1Bzb13PNSjXM= X-Sasl-enc: m42YsMTSsHGb/mdhtF4h1z5Z3v7qhMLjwByu3wLGBnY6 1431365807 Received: from sjc-alcoop-8817.cisco.com (unknown [128.107.241.181]) by mail.messagingengine.com (Postfix) with ESMTPA id 171C468017A; Mon, 11 May 2015 13:36:46 -0400 (EDT) Content-Type: text/plain; charset=windows-1252 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Alissa Cooper In-Reply-To: <5538C4D6.1030007@haw-hamburg.de> Date: Mon, 11 May 2015 10:36:38 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: <87DDD77E-EBFF-4870-9A2D-A902A35770DA@cooperw.in> References: <0dbe3c40f2784076b961e730dd1f17d4@HUB01.mailcluster.haw-hamburg.de> <5538C4D6.1030007@haw-hamburg.de> To: "Thomas C. Schmidt" X-Mailer: Apple Mail (2.1878.6) Archived-At: Cc: p2psip Subject: Re: [P2PSIP] WGLC for draft-ietf-p2psip-share-04 X-BeenThere: p2psip@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Peer-to-Peer SIP working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 May 2015 17:36:56 -0000 Hi Thomas, What is the status of this update? Thanks, Alissa On Apr 23, 2015, at 3:09 AM, Thomas C. Schmidt = wrote: > Hi Emmanuel, >=20 > many thanks! >=20 > We'll fix the issues and resubmit during the next few days. >=20 > Best wishes, >=20 > thomas >=20 > On 23.04.2015 12:03, Emmanuel Baccelli wrote: >> Hi Alissa, Hi WG, >>=20 >> I have reviewed draft-ietf-p2psip-share-05, and here are my comments. >>=20 >>=20 >> General comments: >> in my opinion the draft is in good shape and reads well. I have a few >> nits and editorial suggestions detailed below. I believe these can be >> addressed quite easily with a quick resubmission and my impression is >> the doc is ready to go. >>=20 >>=20 >> Detailed comments: >>=20 >> in Section 1: refer to RFC6940 (and which section, if applicable) the >> first time specific terms are used such as "RELOAD Usage" or "RELOAD >> security model". Spoiler: I will have a lot of such comments below ;) >>=20 >> in Section 2: for reader convenience, I suggest listing the key terms >> (without recalling their definitions) imported from RFC6940, and the >> p2psip-concepts draft in the paragraph right after the 2119 = boilerplate. >>=20 >> in Section 3.1: in step 3, I suggest being explicit that the 8bit = part >> is a suffix (least significant bits) >>=20 >> in Section 4.1: >> - "...Alice is also granted (limited) write access..." >> Either explain what "limited" means here, or remove this adjective. >>=20 >> - "Note that overwriting existing items in an Access Control List = that >> reference a different Kind-ID..." >> Clarify: different from what? I suppose you mean that the overwrite >> results in changing the Kind-ID >>=20 >> - "The Resource Owner is allowed to overwrite any existing ACL item, = but >> should be aware of its consequences." >> Either quickly explain / give examples of consequences or remove this >> sentence. >>=20 >> in Section 5.1: "The specifications in this document scheme adhere = to >> this paradigm...". >> add reference to RFC6940 (and the exact section). It will help = readers >> grasp quicker what draft-ietf-p2psip-share specification adds here. >>=20 >> in Section 6.1: >> - first sentence "Write access ... solely be issued by the Resource = Owner." >> rephrase needed (confusing as readers already know that delegation is >> possible). >>=20 >> - "... stored in the numerical order... starting with the index of = the >> root item...". >> I have a (stupid) question: What if the Node-ID of the an authorized >> peer with ad=3D1 has a node-ID that is numerically smaller that that = of >> the owner? >> I suggest rephrasing in order to clarify this corner case, just to = make >> sure no one is confused? >>=20 >> in Section 6.5: Step 1. reference "as per RFC 6940 Section X.Y." >>=20 >> in Section 6.6: Because it is possible here, I would have preferred = to >> see the last 2 paragraphs written in steps + pseudo-code style >> if...else..else. But that's a matter of taste. >>=20 >>=20 >> Best, >>=20 >> Emmanuel >>=20 >>=20 >>=20 >>=20 >> On Tue, Apr 21, 2015 at 9:08 PM, Alissa Cooper > > wrote: >>=20 >> Yes, that=92s fine, thanks. >> Alissa >>=20 >> On Apr 21, 2015, at 1:40 AM, Emmanuel Baccelli >> > = wrote: >>=20 >> > >> > Hi Alissa, >> > >> > if it is not too late: I am currently reviewing the document. = ETA early next week. >> > Sorry for the delay. Is that alright with you? >> > >> > Best, >> > >> > Emmanuel >> > >> > >> > >> > >> > >> > _______________________________________________ >> > P2PSIP mailing list >> >P2PSIP@ietf.org >> >https://www.ietf.org/mailman/listinfo/p2psip >>=20 >>=20 >=20 > --=20 >=20 > Prof. Dr. Thomas C. Schmidt > =B0 Hamburg University of Applied Sciences Berliner = Tor 7 =B0 > =B0 Dept. Informatik, Internet Technologies Group 20099 Hamburg, = Germany =B0 > =B0 http://www.haw-hamburg.de/inet Fon: = +49-40-42875-8452 =B0 > =B0 http://www.informatik.haw-hamburg.de/~schmidt Fax: = +49-40-42875-8409 =B0 >=20 > _______________________________________________ > P2PSIP mailing list > P2PSIP@ietf.org > https://www.ietf.org/mailman/listinfo/p2psip From nobody Mon May 11 11:09:23 2015 Return-Path: X-Original-To: p2psip@ietfa.amsl.com Delivered-To: p2psip@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9E58E1ACE51 for ; Mon, 11 May 2015 11:09:22 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.56 X-Spam-Level: X-Spam-Status: No, score=-1.56 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, T_RP_MATCHES_RCVD=-0.01] autolearn=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TY1r9s7CsO4P for ; Mon, 11 May 2015 11:09:20 -0700 (PDT) Received: from mx6.haw-public.haw-hamburg.de (mx6.haw-public.haw-hamburg.de [141.22.6.3]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EEAF01ACE8B for ; Mon, 11 May 2015 11:09:19 -0700 (PDT) X-IronPort-AV: E=Sophos;i="5.13,409,1427752800"; d="scan'208";a="26802569" Received: from post.haw-hamburg.de (HELO HUB02.mailcluster.haw-hamburg.de) ([141.22.24.51]) by mail6.is.haw-hamburg.de with ESMTP/TLS/AES128-SHA; 11 May 2015 20:09:18 +0200 Received: from CAS01.mailcluster.haw-hamburg.de (2002:8d16:183c::8d16:183c) by HUB02.mailcluster.haw-hamburg.de (2002:8d16:1833::8d16:1833) with Microsoft SMTP Server (TLS) id 14.3.174.1; Mon, 11 May 2015 20:09:17 +0200 Received: from [192.168.178.101] (141.22.200.50) by haw-mailer.haw-hamburg.de (141.22.24.60) with Microsoft SMTP Server (TLS) id 14.3.174.1; Mon, 11 May 2015 20:09:17 +0200 Message-ID: <5550F04B.6030401@haw-hamburg.de> Date: Mon, 11 May 2015 20:09:15 +0200 From: "Thomas C. Schmidt" User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.6.0 MIME-Version: 1.0 To: Alissa Cooper References: <0dbe3c40f2784076b961e730dd1f17d4@HUB01.mailcluster.haw-hamburg.de> <5538C4D6.1030007@haw-hamburg.de> <454a62af9d0f466c9351c64ac36f1b7e@HUB01.mailcluster.haw-hamburg.de> In-Reply-To: <454a62af9d0f466c9351c64ac36f1b7e@HUB01.mailcluster.haw-hamburg.de> Content-Type: text/plain; charset="windows-1252"; format=flowed Content-Transfer-Encoding: 8bit Archived-At: Cc: p2psip Subject: Re: [P2PSIP] WGLC for draft-ietf-p2psip-share-04 X-BeenThere: p2psip@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Peer-to-Peer SIP working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 May 2015 18:09:22 -0000 Hi Alissa, it's coming ASAP. I was blocked by paper deadlines ... Thanks, Thomas On 11.05.2015 19:36, Alissa Cooper wrote: > Hi Thomas, > > What is the status of this update? > > Thanks, > Alissa > > On Apr 23, 2015, at 3:09 AM, Thomas C. Schmidt wrote: > >> Hi Emmanuel, >> >> many thanks! >> >> We'll fix the issues and resubmit during the next few days. >> >> Best wishes, >> >> thomas >> >> On 23.04.2015 12:03, Emmanuel Baccelli wrote: >>> Hi Alissa, Hi WG, >>> >>> I have reviewed draft-ietf-p2psip-share-05, and here are my comments. >>> >>> >>> General comments: >>> in my opinion the draft is in good shape and reads well. I have a few >>> nits and editorial suggestions detailed below. I believe these can be >>> addressed quite easily with a quick resubmission and my impression is >>> the doc is ready to go. >>> >>> >>> Detailed comments: >>> >>> in Section 1: refer to RFC6940 (and which section, if applicable) the >>> first time specific terms are used such as "RELOAD Usage" or "RELOAD >>> security model". Spoiler: I will have a lot of such comments below ;) >>> >>> in Section 2: for reader convenience, I suggest listing the key terms >>> (without recalling their definitions) imported from RFC6940, and the >>> p2psip-concepts draft in the paragraph right after the 2119 boilerplate. >>> >>> in Section 3.1: in step 3, I suggest being explicit that the 8bit part >>> is a suffix (least significant bits) >>> >>> in Section 4.1: >>> - "...Alice is also granted (limited) write access..." >>> Either explain what "limited" means here, or remove this adjective. >>> >>> - "Note that overwriting existing items in an Access Control List that >>> reference a different Kind-ID..." >>> Clarify: different from what? I suppose you mean that the overwrite >>> results in changing the Kind-ID >>> >>> - "The Resource Owner is allowed to overwrite any existing ACL item, but >>> should be aware of its consequences." >>> Either quickly explain / give examples of consequences or remove this >>> sentence. >>> >>> in Section 5.1: "The specifications in this document scheme adhere to >>> this paradigm...". >>> add reference to RFC6940 (and the exact section). It will help readers >>> grasp quicker what draft-ietf-p2psip-share specification adds here. >>> >>> in Section 6.1: >>> - first sentence "Write access ... solely be issued by the Resource Owner." >>> rephrase needed (confusing as readers already know that delegation is >>> possible). >>> >>> - "... stored in the numerical order... starting with the index of the >>> root item...". >>> I have a (stupid) question: What if the Node-ID of the an authorized >>> peer with ad=1 has a node-ID that is numerically smaller that that of >>> the owner? >>> I suggest rephrasing in order to clarify this corner case, just to make >>> sure no one is confused? >>> >>> in Section 6.5: Step 1. reference "as per RFC 6940 Section X.Y." >>> >>> in Section 6.6: Because it is possible here, I would have preferred to >>> see the last 2 paragraphs written in steps + pseudo-code style >>> if...else..else. But that's a matter of taste. >>> >>> >>> Best, >>> >>> Emmanuel >>> >>> >>> >>> >>> On Tue, Apr 21, 2015 at 9:08 PM, Alissa Cooper >> > wrote: >>> >>> Yes, that’s fine, thanks. >>> Alissa >>> >>> On Apr 21, 2015, at 1:40 AM, Emmanuel Baccelli >>> > wrote: >>> >>> > >>> > Hi Alissa, >>> > >>> > if it is not too late: I am currently reviewing the document. ETA early next week. >>> > Sorry for the delay. Is that alright with you? >>> > >>> > Best, >>> > >>> > Emmanuel >>> > >>> > >>> > >>> > >>> > >>> > _______________________________________________ >>> > P2PSIP mailing list >>> >P2PSIP@ietf.org >>> >https://www.ietf.org/mailman/listinfo/p2psip >>> >>> >> >> -- >> >> Prof. Dr. Thomas C. Schmidt >> ° Hamburg University of Applied Sciences Berliner Tor 7 ° >> ° Dept. Informatik, Internet Technologies Group 20099 Hamburg, Germany ° >> ° http://www.haw-hamburg.de/inet Fon: +49-40-42875-8452 ° >> ° http://www.informatik.haw-hamburg.de/~schmidt Fax: +49-40-42875-8409 ° >> >> _______________________________________________ >> P2PSIP mailing list >> P2PSIP@ietf.org >> https://www.ietf.org/mailman/listinfo/p2psip -- Prof. Dr. Thomas C. Schmidt ° Hamburg University of Applied Sciences Berliner Tor 7 ° ° Dept. Informatik, Internet Technologies Group 20099 Hamburg, Germany ° ° http://www.haw-hamburg.de/inet Fon: +49-40-42875-8452 ° ° http://www.informatik.haw-hamburg.de/~schmidt Fax: +49-40-42875-8409 ° From nobody Tue May 19 14:41:20 2015 Return-Path: X-Original-To: p2psip@ietfa.amsl.com Delivered-To: p2psip@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ACBF51B3349 for ; Tue, 19 May 2015 14:41:19 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.301 X-Spam-Level: X-Spam-Status: No, score=-2.301 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qWFLt_rTFpJG for ; Tue, 19 May 2015 14:41:17 -0700 (PDT) Received: from mail-wg0-f51.google.com (mail-wg0-f51.google.com [74.125.82.51]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6739F1B33C4 for ; Tue, 19 May 2015 14:41:13 -0700 (PDT) Received: by wgbgq6 with SMTP id gq6so32620439wgb.3 for ; Tue, 19 May 2015 14:41:12 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:subject:from:reply-to:to:date :organization:content-type:mime-version; bh=iwED8FO2RBF2iJmetZAeWwRzSd9n7hDXc8aDf2aRRYU=; b=CfQcubpcTN9Ea4dASluBJCSE/MlbPCoxLwO/82DNZHpqevTt7PLsF73hAxswtLvO/v McU9L/L7RHijRm8SImOSx3zhzFe6B05ZEjILJ7e+p6O3GVeoSeQ1vLxg/+5Z4V4F7Tie nCDAHlaP5Az+WLpfW11E10avgq0fyvSFQRgjA63zsX6r6TBzYalkbAAH9zBsuAM3x3bw GB4AN1jRTC6HzaW/4YIIMLV34MAxScB952qVq2R4vX0/+xg+TFirmHiWCYV1r9WoSLBr SyeKzGFil7/cUMSBWRH0mYj70xIoO4WH89OsK/W4LMbsB54yhuvSHul4xxAJ7saaXZo6 t8cQ== X-Gm-Message-State: ALoCoQkvuumDp493FG8IyqDQSEV+Td9183PS3TtUcO65E2TnZgX6HElSCTmdQych7sTR11KAJOOl X-Received: by 10.194.57.109 with SMTP id h13mr56359565wjq.67.1432071672151; Tue, 19 May 2015 14:41:12 -0700 (PDT) Received: from acorde (82.158.203.25.dyn.user.ono.com. [82.158.203.25]) by mx.google.com with ESMTPSA id ch2sm214732wib.18.2015.05.19.14.41.11 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 19 May 2015 14:41:11 -0700 (PDT) Message-ID: <1432071670.2266.34.camel@it.uc3m.es> From: Carlos =?ISO-8859-1?Q?Jes=FAs?= Bernardos Cano To: p2psip@ietf.org Date: Tue, 19 May 2015 23:41:10 +0200 Organization: Universidad Carlos III de Madrid Content-Type: multipart/mixed; boundary="=-KzBe961gw37fDujgXukg" X-Mailer: Evolution 3.12.9-1+b1 Mime-Version: 1.0 Archived-At: Subject: [P2PSIP] [Fwd: Last Call: (A Constrained Application Protocol (CoAP) Usage for REsource LOcation And Discovery (RELOAD)) to Proposed Standard] X-BeenThere: p2psip@ietf.org X-Mailman-Version: 2.1.15 Precedence: list Reply-To: cjbc@it.uc3m.es List-Id: Peer-to-Peer SIP working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 May 2015 21:41:19 -0000 --=-KzBe961gw37fDujgXukg Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit Hi, Just forwarding for those not subscribed to IETF announce. Regards, Carlos --=-KzBe961gw37fDujgXukg Content-Disposition: inline Content-Description: Forwarded message - Last Call: (A Constrained Application Protocol (CoAP) Usage for REsource LOcation And Discovery (RELOAD)) to Proposed Standard Content-Type: message/rfc822 Delivered-To: cjbc@it.uc3m.es Received: by 10.28.225.213 with SMTP id y204csp2804767wmg; Wed, 15 Apr 2015 14:28:07 -0700 (PDT) X-Received: by 10.66.140.101 with SMTP id rf5mr50891450pab.50.1429133285988; Wed, 15 Apr 2015 14:28:05 -0700 (PDT) Return-Path: Received: from mail.ietf.org (mail.ietf.org. [2001:1900:3001:11::2c]) by mx.google.com with ESMTPS id px4si8873807pdb.78.2015.04.15.14.28.05 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 15 Apr 2015 14:28:05 -0700 (PDT) Received-SPF: pass (google.com: domain of ietf-announce-bounces@ietf.org designates 2001:1900:3001:11::2c as permitted sender) client-ip=2001:1900:3001:11::2c; Authentication-Results: mx.google.com; spf=pass (google.com: domain of ietf-announce-bounces@ietf.org designates 2001:1900:3001:11::2c as permitted sender) smtp.mail=ietf-announce-bounces@ietf.org; dkim=pass header.i=@ietf.org Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 5897D1A9096; Wed, 15 Apr 2015 14:27:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1429133246; bh=i62oPa2wBZA21kdT25cs15VPXV4EBXTtKFJqaq2iyT0=; h=Content-Type:MIME-Version:Content-Transfer-Encoding:From:To: Subject:Message-ID:Date:Reply-To:List-Id:List-Unsubscribe: List-Archive:List-Post:List-Help:List-Subscribe:Sender; b=qL6WCc6YDdEcH6d1tYaqrJqnbP12zHmnn/9ybWZx8L3RZOCcVRiH35AlmT5b/qEQX ztAA0vbhMVYZtfT4htk2QvyBWPZvkZfKWijOq12IjU46yRnIXe8wjuEu+8bdJJ6JAQ wJZupy53oetr5bY2tGiYcD95zW4HDQZNXJ60Je7E= X-Original-To: ietf-announce@ietfa.amsl.com Delivered-To: ietf-announce@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 93A991A908E for ; Wed, 15 Apr 2015 14:27:22 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -101.9 X-Spam-Level: X-Spam-Status: No, score=-101.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, USER_IN_WHITELIST=-100] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2aRjw6IDJ-ZP for ; Wed, 15 Apr 2015 14:27:21 -0700 (PDT) Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 21B931A9080 for ; Wed, 15 Apr 2015 14:27:21 -0700 (PDT) Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 From: The IESG To: "IETF-Announce" Subject: Last Call: (A Constrained Application Protocol (CoAP) Usage for REsource LOcation And Discovery (RELOAD)) to Proposed Standard X-Test-IDTracker: no X-IETF-IDTracker: 6.0.1 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <20150415212721.10934.83802.idtracker@ietfa.amsl.com> Date: Wed, 15 Apr 2015 14:27:21 -0700 Archived-At: X-BeenThere: ietf-announce@ietf.org X-Mailman-Version: 2.1.15 Reply-To: ietf@ietf.org List-Id: "IETF announcement list. No discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: ietf-announce-bounces@ietf.org Sender: "IETF-Announce" Content-Transfer-Encoding: quoted-printable The IESG has received a request from an individual submitter to consider the following document: - 'A Constrained Application Protocol (CoAP) Usage for REsource LOcation And Discovery (RELOAD)' as Proposed Standard The IESG plans to make a decision in the next few weeks, and solicits final comments on this action. Please send substantive comments to the ietf@ietf.org mailing lists by 2015-05-13. Exceptionally, comments may be sent to iesg@ietf.org instead. In either case, please retain the beginning of the Subject line to allow automated sorting. Abstract This document defines a Constrained Application Protocol (CoAP) Usage for REsource LOcation And Discovery (RELOAD). The CoAP Usage provides the functionality to federate Wireless Sensor Networks (WSN) in a peer-to-peer fashion. The CoAP Usage for RELOAD allows CoAP nodes to store resources in a RELOAD peer-to-peer overlay, provides a lookup service, and enables the use of RELOAD overlay as a cache for sensor data. This functionality is implemented in the RELOAD overlay itself, without the use of centralized servers. The RELOAD AppAttach method is used to establish a direct connection between nodes through which CoAP messages are exchanged. The file can be obtained via http://datatracker.ietf.org/doc/draft-jimenez-p2psip-coap-reload/ IESG discussion can be tracked via http://datatracker.ietf.org/doc/draft-jimenez-p2psip-coap-reload/ballot/ The following IPR Declarations may be related to this I-D: http://datatracker.ietf.org/ipr/1783/ --=-KzBe961gw37fDujgXukg--