From zach@sensinode.com Fri Jun 1 00:26:07 2012 Return-Path: X-Original-To: core@ietfa.amsl.com Delivered-To: core@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BC6CC21F8598 for ; Fri, 1 Jun 2012 00:26:07 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.599 X-Spam-Level: X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1] 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 yuqvQsiEIZzi for ; Fri, 1 Jun 2012 00:26:06 -0700 (PDT) Received: from auth-smtp.nebula.fi (auth-smtp.nebula.fi [217.30.180.105]) by ietfa.amsl.com (Postfix) with ESMTP id 8DB2C21F8585 for ; Fri, 1 Jun 2012 00:26:05 -0700 (PDT) Received: from [172.20.10.4] (84-231-239-208.elisa-mobile.fi [84.231.239.208]) (authenticated bits=0) by auth-smtp.nebula.fi (8.13.8/8.13.4) with ESMTP id q517Q1aW032330; Fri, 1 Jun 2012 10:26:02 +0300 Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: text/plain; charset=us-ascii From: Zach Shelby In-Reply-To: Date: Fri, 1 Jun 2012 10:25:58 +0300 Content-Transfer-Encoding: quoted-printable Message-Id: <86CB220C-9E6A-4A38-9BDD-AC2FD074EEDB@sensinode.com> References: <20120523195759.5258.35843.idtracker@ietfa.amsl.com> <600FF474-AC9A-44FA-8A68-08A23EC511D6@tzi.org> To: "Rahman, Akbar" X-Mailer: Apple Mail (2.1084) Cc: core@ietf.org Subject: Re: [core] WG review period for: draft-ietf-core-link-format-13.txt X-BeenThere: core@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Jun 2012 07:26:07 -0000 On May 29, 2012, at 11:44 PM, Rahman, Akbar wrote: >> I reviewed -ietf-core-link-format-13.txt. I found it to be overall a = very well written and useful I-D, and support it's advancement in the = RFC process. I did however have the following three points as = questions/comments for you to consider: >>=20 >>=20 >> 1) Use of the term "CoRE" >> My understanding is that WG names (e.g. Section 1) should generally = NOT be included in RFC track I-Ds as the WG will end at some point while = the RFC document is permanent. But in this document you use the term = "CoRE" extensively. Did you consider using the term "CoAP" instead? >=20 > CoAP would not make sense in this case, as this Link Format is not = dependent on CoAP, it can be used equally as well over HTTP. I don't = consider "CoRE" to be just the name of this working group, but = "Constrained RESTful Environments" I consider to be a useful term to = define the environment are solutions are solving problems in. Thus the = term would live on regardless of the working group. >=20 >=20 > AKBAR: OKAY. BUT YOU SHOULD AT LEAST REMOVE THE REFERENCE TO THE = "WORKING GROUP" IN FIRST SENTENCE OF SECTION 1 (INTRODUCTION) AND = REFRAME THE PARAGRAPH AS YOU DESCRIBE ABOVE. OK. >> 2) In section 2.1, point (c), it is not clear to me what the = "document" is referring to in the sentence? >=20 > Right, for HTTP folks that means the representation returned to you as = a result of your request. So if I GET /.well-known/core the set of links = returned in the response is the "link format document". Maybe for our = readers we should; >=20 > s/document/representation?=20 >=20 >=20 > AKBAR: I WOULD PREFER "REPRESENTATION". I thought about this more, and "resource" is a better term. So c) would = read: Origin of the link format resource's base URI. >> 3) The use of the "hosts" relation type is missing in the examples = (section 5). It would be very useful to add an example using this = relation. Can you add one example that uses "hosts"? >=20 > "hosts" is the default relation type for this link format, thus every = link in the examples without an explicit rel=3D attribute is a "hosts" = link. Does that need to be said explicitly in the beginning of the = examples section maybe? >=20 >=20 > AKBAR: I THINK THE USAGE FOR HOSTS AND RULES FOR "HOSTS" HAS TO BE = MENTIONED EXPLICITLY IN SECTION 5 FOR CLARITY. ALSO IN PREVIOUS = VERSIONS OF THE I-D THERE WAS SOME USEFUL TEXT IN 7.2 WHICH IS NOW = DELETED (I.E. "..and by default the context of the links is the server = at coap://authority from which /.well-known/core was requested."). WHY = WAS THIS TEXT DELETED FROM SECTION 7.2? I added text in Section 5 explaining that, along with a note in Section = 7.2. Thanks for pointing out that wasn't clear. Zach --=20 Zach Shelby, Chief Nerd, Sensinode Ltd. http://www.sensinode.com http://zachshelby.org - My blog "On the Internet of Things" http://6lowpan.net - My book "6LoWPAN: The Wireless Embedded Internet" Mobile: +358 40 7796297 From zach@sensinode.com Fri Jun 1 00:49:36 2012 Return-Path: X-Original-To: core@ietfa.amsl.com Delivered-To: core@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C480421F862B for ; Fri, 1 Jun 2012 00:49:36 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.299 X-Spam-Level: X-Spam-Status: No, score=-3.299 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_28=0.6, RCVD_IN_DNSWL_LOW=-1] 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 T3h7-1WcSOwk for ; Fri, 1 Jun 2012 00:49:35 -0700 (PDT) Received: from auth-smtp.nebula.fi (auth-smtp.nebula.fi [217.30.180.105]) by ietfa.amsl.com (Postfix) with ESMTP id 5940E21F8627 for ; Fri, 1 Jun 2012 00:49:34 -0700 (PDT) Received: from [172.20.10.4] (84-231-239-208.elisa-mobile.fi [84.231.239.208]) (authenticated bits=0) by auth-smtp.nebula.fi (8.13.8/8.13.4) with ESMTP id q517nRo2004911; Fri, 1 Jun 2012 10:49:30 +0300 Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: text/plain; charset=iso-8859-1 From: Zach Shelby In-Reply-To: <031DD135F9160444ABBE3B0C36CED6180D8D77@011-DB3MPN1-013.MGDPHG.emi.philips.com> Date: Fri, 1 Jun 2012 10:49:25 +0300 Content-Transfer-Encoding: quoted-printable Message-Id: <9A32AF96-1E94-4635-ABF4-EF9CC9553731@sensinode.com> References: <20120523195759.5258.35843.idtracker@ietfa.amsl.com> <600FF474-AC9A-44FA-8A68-08A23EC511D6@tzi.org> <031DD135F9160444ABBE3B0C36CED6180D8CC5@011-DB3MPN1-013.MGDPHG.emi.philips.com> <031DD135F9160444ABBE3B0C36CED6180D8D77@011-DB3MPN1-013.MGDPHG.emi.philips.com> To: "Dijk, Esko" X-Mailer: Apple Mail (2.1084) Cc: "core@ietf.org WG" Subject: Re: [core] draft-ietf-core-link-format-13: querying in multi-valued attribute cases X-BeenThere: core@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Jun 2012 07:49:36 -0000 Esko, On May 29, 2012, at 4:44 PM, Dijk, Esko wrote: > Thanks Zach, clear to me. I agree the text needs to be updated to = reflect this functionality. >=20 > E.g. an implementer may be surprised about his CoAP client queries GET = /.well-known/core?if=3Dmysensor and gets back=20 > = ;rt=3D"temperature-c";if=3D"http://www.example.org/myapp.wadl#senso= r mysensor" > where the "if" string is *not* bitwise identical to the query value. I agree an example would help here. I have now added the following = example to illustrate that this could happen: Note that relation-type attributes like rt=3D, if=3D and rel=3D can = have multiple values separated by spaces. A query filter parameter can match any one of those values, as in this example: REQ: GET /.well-known/core?rt=3Dlight-lux RES: 2.05 Content ;rt=3D"light-lux core.sen-light";if=3D"sensor" >=20 > Also the text=20 > "any target attributes notated as quoted-string are interpreted as = defined in > section 2.2 of [RFC2616]. After these steps, a Complete Value = String > matches a target attribute if it is bitwise identical." > is not correct then it seems. = if=3D"http://www.example.org/myapp.wadl#sensor mysensor" is a = quoted-string, so should be interpreted as one entity according to = RFC2616 unless I'm wrong. I checked through the specification in Section 4.1 and it is actually = correct. The text you are referring to only pertains to target = attributes of quoted-string type, which are title or possible future = link-extensions. The target attributes that can have multiple values are = relation-type, and when Section 4.1 refers to "target attribute" each of = the values contained in an rt=3D, if=3D or rel=3D is a target attribute.=20= To further clarify this point, I added the following sentence to Section = 4.1: "Note that relation-type target attributes can contain multiple values, = each value MUST be treated as a separate target attribute when = matching." Zach >=20 > Esko >=20 > -----Original Message----- > From: Zach Shelby [mailto:zach@sensinode.com]=20 > Sent: Tuesday 29 May 2012 14:42 > To: Dijk, Esko > Cc: Carsten Bormann; core@ietf.org WG > Subject: Re: draft-ietf-core-link-format-13: querying in multi-valued = attribute cases >=20 > Esko, >=20 > On May 29, 2012, at 2:29 PM, Dijk, Esko wrote: >=20 >> Dear Carsten, Zach, >>=20 >> I see one main issue in the draft. An attribute can have multiple = values e.g. >> REQ: GET /.well-known/core >> RES: 2.05 Content >> = ;rt=3D"temperature-c";if=3D"http://www.example.org/myapp.wadl#senso= r mysensor" >>=20 >> If I query this server for a "mysensor" interface as follows: >> REQ: GET /.well-known/core?if=3Dmysensor >>=20 >> I won't get the expected /temp resource in the result, because value = matching is done bitwise identical to the "if" string value between the = double quotes. Or is my argument wrong here? It seems this needs more = explanation in the draft - e.g. if using multiple values is reserved for = some special cases where querying is not used. >=20 > Good question. When multiple values are included in rel=3D, rt=3D or = if=3D attributes (regardless of the attribute), those are treated as = separate values logically. So your /temp link above has two separate if=3D= attribute values, "http://www.example.org/myapp.wadl#sensor" and = "mysensor". When a query is made for if=3Dmysensor then that is compared = against each value of if=3D associated with your links, and in this case = it would match the link.=20 >=20 > Seems that was not clear, so I agree we need to add some clarification = text to the Query Filter section. I will make a ticket and propose some = text. >=20 > Zach >=20 >> regards, >> Esko >>=20 >> -----Original Message----- >> From: core-bounces@ietf.org [mailto:core-bounces@ietf.org] On Behalf = Of Carsten Bormann >> Sent: Thursday 24 May 2012 0:39 >> To: core@ietf.org WG >> Subject: [core] WG review period for: = draft-ietf-core-link-format-13.txt >>=20 >> The recently submitted draft-ietf-core-link-format-13.txt is intended = to reflect IETF last call and in particular the IESG comments. >>=20 >> Drafts resulting from such a process have often been simply been = published as RFCs without consulting the WG again. >> However, the responsible AD and the chairs all believe it is a good = idea to give the WG one more round to look at the result. >>=20 >> We are therefore announcing a one-week "WG review period" for the = updated draft: >>=20 >> http://tools.ietf.org/html/draft-ietf-core-link-format-13 >>=20 >> Some additional resources: >>=20 >> 1) >> = http://datatracker.ietf.org/doc/draft-ietf-core-link-format/history/ >>=20 >> gives you some visibility into what happened in the IETF/IESG = process, and what the DISCUSSes and COMMENTs were that the IESG = provided. >>=20 >> 2) >> = http://tools.ietf.org/rfcdiff?url2=3Ddraft-ietf-core-link-format-13&url1=3D= draft-ietf-core-link-format-11 >>=20 >> shows what changed between the version we submitted to the IESG and = the result of this process. >> As you can see, what mostly changed apart form editorial = clarification was the selection of informal and formal description = techniques that are in use for the format and for the query syntax. >> Fortunately, some nice recently published documents like the = definition of Origin (RFC6454) and URI templates (RFC 6570) made this = job a bit more pleasant. >>=20 >> So, please do have a look, and tell the mailing list until >>=20 >> 2012-05-31, 12:59 UTC >>=20 >> whether there are remaining or new problems. >> (Please also do send a quick notice if you had a look and didn't find = any problems.) >>=20 >> Gr=FC=DFe, Carsten >>=20 >> _______________________________________________ >> core mailing list >> core@ietf.org >> https://www.ietf.org/mailman/listinfo/core >>=20 >> ________________________________ >> The information contained in this message may be confidential and = legally protected under applicable law. The message is intended solely = for the addressee(s). If you are not the intended recipient, you are = hereby notified that any use, forwarding, dissemination, or reproduction = of this message is strictly prohibited and may be unlawful. If you are = not the intended recipient, please contact the sender by return e-mail = and destroy all copies of the original message. >>=20 >=20 > --=20 > Zach Shelby, Chief Nerd, Sensinode Ltd. > http://www.sensinode.com > http://zachshelby.org - My blog "On the Internet of Things" > http://6lowpan.net - My book "6LoWPAN: The Wireless Embedded Internet" > Mobile: +358 40 7796297 >=20 >=20 --=20 Zach Shelby, Chief Nerd, Sensinode Ltd. http://www.sensinode.com http://zachshelby.org - My blog "On the Internet of Things" http://6lowpan.net - My book "6LoWPAN: The Wireless Embedded Internet" Mobile: +358 40 7796297 From internet-drafts@ietf.org Fri Jun 1 00:55:09 2012 Return-Path: X-Original-To: core@ietfa.amsl.com Delivered-To: core@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 48D8C21F8555; Fri, 1 Jun 2012 00:55:09 -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 EVXGGGTV0MLN; Fri, 1 Jun 2012 00:55:08 -0700 (PDT) Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C304321F854B; Fri, 1 Jun 2012 00:55:08 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable From: internet-drafts@ietf.org To: i-d-announce@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 4.02 Message-ID: <20120601075508.25183.95758.idtracker@ietfa.amsl.com> Date: Fri, 01 Jun 2012 00:55:08 -0700 Cc: core@ietf.org Subject: [core] I-D Action: draft-ietf-core-link-format-14.txt X-BeenThere: core@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Jun 2012 07:55:09 -0000 A New Internet-Draft is available from the on-line Internet-Drafts director= ies. This draft is a work item of the Constrained RESTful Environments Work= ing Group of the IETF. Title : CoRE Link Format Author(s) : Zach Shelby Filename : draft-ietf-core-link-format-14.txt Pages : 25 Date : 2012-06-01 This specification defines Web Linking using a link format for use by constrained web servers to describe hosted resources, their attributes and other relationships between links. Based on the HTTP Link Header field defined in RFC5988, the CoRE Link Format is carried as a payload and is assigned an Internet media type. A well-known URI is defined as a default entry-point for requesting the links hosted by a server. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-core-link-format-14.txt Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ This Internet-Draft can be retrieved at: ftp://ftp.ietf.org/internet-drafts/draft-ietf-core-link-format-14.txt The IETF datatracker page for this Internet-Draft is: https://datatracker.ietf.org/doc/draft-ietf-core-link-format/ From zach@sensinode.com Fri Jun 1 00:59:45 2012 Return-Path: X-Original-To: core@ietfa.amsl.com Delivered-To: core@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 170E521F8665 for ; Fri, 1 Jun 2012 00:59:45 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.499 X-Spam-Level: X-Spam-Status: No, score=-3.499 tagged_above=-999 required=5 tests=[AWL=0.100, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1] 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 f2g2BCmPlOWC for ; Fri, 1 Jun 2012 00:59:44 -0700 (PDT) Received: from auth-smtp.nebula.fi (auth-smtp.nebula.fi [217.30.180.105]) by ietfa.amsl.com (Postfix) with ESMTP id 34EDD21F8550 for ; Fri, 1 Jun 2012 00:59:44 -0700 (PDT) Received: from [172.20.10.4] (84-231-239-208.elisa-mobile.fi [84.231.239.208]) (authenticated bits=0) by auth-smtp.nebula.fi (8.13.8/8.13.4) with ESMTP id q517xgxd007524 for ; Fri, 1 Jun 2012 10:59:43 +0300 Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Apple Message framework v1084) From: Zach Shelby In-Reply-To: <20120601075508.25183.95758.idtracker@ietfa.amsl.com> Date: Fri, 1 Jun 2012 10:59:42 +0300 Content-Transfer-Encoding: quoted-printable Message-Id: <1B825FF1-B562-49DF-93BA-2D617B297E1D@sensinode.com> References: <20120601075508.25183.95758.idtracker@ietfa.amsl.com> To: "core@ietf.org WG" X-Mailer: Apple Mail (2.1084) Subject: Re: [core] I-D Action: draft-ietf-core-link-format-14.txt X-BeenThere: core@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Jun 2012 07:59:45 -0000 This new version takes into account the comments Akbar and Esko provided = in the WG review period that ended yesterday. Thanks guys for the = comments! Zach On Jun 1, 2012, at 10:55 AM, Internet-Drafts@ietf.org wrote: >=20 > A New Internet-Draft is available from the on-line Internet-Drafts = directories. This draft is a work item of the Constrained RESTful = Environments Working Group of the IETF. >=20 > Title : CoRE Link Format > Author(s) : Zach Shelby > Filename : draft-ietf-core-link-format-14.txt > Pages : 25 > Date : 2012-06-01 >=20 > This specification defines Web Linking using a link format for use = by > constrained web servers to describe hosted resources, their > attributes and other relationships between links. Based on the HTTP > Link Header field defined in RFC5988, the CoRE Link Format is = carried > as a payload and is assigned an Internet media type. A well-known > URI is defined as a default entry-point for requesting the links > hosted by a server. >=20 >=20 > A URL for this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-ietf-core-link-format-14.txt >=20 > Internet-Drafts are also available by anonymous FTP at: > ftp://ftp.ietf.org/internet-drafts/ >=20 > This Internet-Draft can be retrieved at: > ftp://ftp.ietf.org/internet-drafts/draft-ietf-core-link-format-14.txt >=20 > The IETF datatracker page for this Internet-Draft is: > https://datatracker.ietf.org/doc/draft-ietf-core-link-format/ >=20 > _______________________________________________ > core mailing list > core@ietf.org > https://www.ietf.org/mailman/listinfo/core --=20 Zach Shelby, Chief Nerd, Sensinode Ltd. http://www.sensinode.com http://zachshelby.org - My blog "On the Internet of Things" http://6lowpan.net - My book "6LoWPAN: The Wireless Embedded Internet" Mobile: +358 40 7796297 From esko.dijk@philips.com Fri Jun 1 01:17:43 2012 Return-Path: X-Original-To: core@ietfa.amsl.com Delivered-To: core@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7EC4C21F866B for ; Fri, 1 Jun 2012 01:17:42 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.479 X-Spam-Level: X-Spam-Status: No, score=-3.479 tagged_above=-999 required=5 tests=[AWL=-0.480, BAYES_00=-2.599, J_CHICKENPOX_28=0.6, RCVD_IN_DNSWL_LOW=-1] 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 mP2nXojLdils for ; Fri, 1 Jun 2012 01:17:37 -0700 (PDT) Received: from va3outboundpool.messaging.microsoft.com (va3ehsobe001.messaging.microsoft.com [216.32.180.11]) by ietfa.amsl.com (Postfix) with ESMTP id 369A521F864B for ; Fri, 1 Jun 2012 01:17:36 -0700 (PDT) Received: from mail83-va3-R.bigfish.com (10.7.14.253) by VA3EHSOBE007.bigfish.com (10.7.40.11) with Microsoft SMTP Server id 14.1.225.23; Fri, 1 Jun 2012 08:17:04 +0000 Received: from mail83-va3 (localhost [127.0.0.1]) by mail83-va3-R.bigfish.com (Postfix) with ESMTP id B3F7F1E0233; Fri, 1 Jun 2012 08:17:04 +0000 (UTC) X-Forefront-Antispam-Report: CIP:157.55.7.222; KIP:(null); UIP:(null); IPV:NLI; H:mail.philips.com; RD:none; EFVD:NLI X-SpamScore: -51 X-BigFish: VPS-51(zz217bL15d6O9371I9251Jc89bh936eK542M1432N98dKzz1202hzz8275ch1033IL8275bh8275dhz2dh2a8h668h839hd25hf0ah) Received: from mail83-va3 (localhost.localdomain [127.0.0.1]) by mail83-va3 (MessageSwitch) id 1338538622174735_24172; Fri, 1 Jun 2012 08:17:02 +0000 (UTC) Received: from VA3EHSMHS010.bigfish.com (unknown [10.7.14.240]) by mail83-va3.bigfish.com (Postfix) with ESMTP id 1D114360050; Fri, 1 Jun 2012 08:17:02 +0000 (UTC) Received: from mail.philips.com (157.55.7.222) by VA3EHSMHS010.bigfish.com (10.7.99.20) with Microsoft SMTP Server (TLS) id 14.1.225.23; Fri, 1 Jun 2012 08:16:59 +0000 Received: from 011-DB3MPN1-013.MGDPHG.emi.philips.com ([169.254.3.141]) by 011-DB3MMR1-001.MGDPHG.emi.philips.com ([10.128.28.51]) with mapi id 14.01.0355.003; Fri, 1 Jun 2012 09:17:28 +0100 From: "Dijk, Esko" To: Zach Shelby Thread-Topic: draft-ietf-core-link-format-13: querying in multi-valued attribute cases Thread-Index: AQHNPY7CDCRrjnJo5Eyn2X8ZxKz+yZbgpQ2AgAAe+kCABEY4gIAAE0+g Date: Fri, 1 Jun 2012 08:17:27 +0000 Message-ID: <031DD135F9160444ABBE3B0C36CED6180D9309@011-DB3MPN1-013.MGDPHG.emi.philips.com> References: <20120523195759.5258.35843.idtracker@ietfa.amsl.com> <600FF474-AC9A-44FA-8A68-08A23EC511D6@tzi.org> <031DD135F9160444ABBE3B0C36CED6180D8CC5@011-DB3MPN1-013.MGDPHG.emi.philips.com> <031DD135F9160444ABBE3B0C36CED6180D8D77@011-DB3MPN1-013.MGDPHG.emi.philips.com> <9A32AF96-1E94-4635-ABF4-EF9CC9553731@sensinode.com> In-Reply-To: <9A32AF96-1E94-4635-ABF4-EF9CC9553731@sensinode.com> Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [194.171.252.101] Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-OriginatorOrg: philips.com Cc: "core@ietf.org WG" Subject: Re: [core] draft-ietf-core-link-format-13: querying in multi-valued attribute cases X-BeenThere: core@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Jun 2012 08:17:43 -0000 Ok, thanks. > I checked through the specification in Section 4.1 and it is actually cor= rect. The text you are referring to=20 > only pertains to target attributes of quoted-string type, which are title= or possible future link-extensions.=20 > The target attributes that can have multiple values are relation-type, an= d when Section 4.1 refers to "target=20 > attribute" each of the values contained in an rt=3D, if=3D or rel=3D is a= target attribute. Agree. It seems my confusion here comes from having a quoted string paramet= er value that is not a quoted-string. > "Note that relation-type target attributes can contain multiple values, e= ach value MUST be treated as a separate > target attribute when matching." Ok. It should be "Note that relation-types target attributes..." with extra= "s" at the end of relation-type.=20 Esko -----Original Message----- From: Zach Shelby [mailto:zach@sensinode.com]=20 Sent: Friday 1 June 2012 9:49 To: Dijk, Esko Cc: Carsten Bormann; core@ietf.org WG Subject: Re: draft-ietf-core-link-format-13: querying in multi-valued attri= bute cases Esko, On May 29, 2012, at 4:44 PM, Dijk, Esko wrote: > Thanks Zach, clear to me. I agree the text needs to be updated to reflec= t this functionality. >=20 > E.g. an implementer may be surprised about his CoAP client queries GET /.= well-known/core?if=3Dmysensor and gets back=20 > ;rt=3D"temperature-c";if=3D"http://www.example.org/myapp.wadl#sen= sor mysensor" > where the "if" string is *not* bitwise identical to the query value. I agree an example would help here. I have now added the following example = to illustrate that this could happen: Note that relation-type attributes like rt=3D, if=3D and rel=3D can have multiple values separated by spaces. A query filter parameter can match any one of those values, as in this example: REQ: GET /.well-known/core?rt=3Dlight-lux RES: 2.05 Content ;rt=3D"light-lux core.sen-light";if=3D"sensor" >=20 > Also the text=20 > "any target attributes notated as quoted-string are interpreted as defin= ed in > section 2.2 of [RFC2616]. After these steps, a Complete Value String > matches a target attribute if it is bitwise identical." > is not correct then it seems. if=3D"http://www.example.org/myapp.wadl#sen= sor mysensor" is a quoted-string, so should be interpreted as one entity ac= cording to RFC2616 unless I'm wrong. I checked through the specification in Section 4.1 and it is actually corre= ct. The text you are referring to only pertains to target attributes of quo= ted-string type, which are title or possible future link-extensions. The ta= rget attributes that can have multiple values are relation-type, and when S= ection 4.1 refers to "target attribute" each of the values contained in an = rt=3D, if=3D or rel=3D is a target attribute.=20 To further clarify this point, I added the following sentence to Section 4.= 1: "Note that relation-type target attributes can contain multiple values, eac= h value MUST be treated as a separate target attribute when matching." Zach >=20 > Esko >=20 > -----Original Message----- > From: Zach Shelby [mailto:zach@sensinode.com]=20 > Sent: Tuesday 29 May 2012 14:42 > To: Dijk, Esko > Cc: Carsten Bormann; core@ietf.org WG > Subject: Re: draft-ietf-core-link-format-13: querying in multi-valued att= ribute cases >=20 > Esko, >=20 > On May 29, 2012, at 2:29 PM, Dijk, Esko wrote: >=20 >> Dear Carsten, Zach, >>=20 >> I see one main issue in the draft. An attribute can have multiple values= e.g. >> REQ: GET /.well-known/core >> RES: 2.05 Content >> ;rt=3D"temperature-c";if=3D"http://www.example.org/myapp.wadl#se= nsor mysensor" >>=20 >> If I query this server for a "mysensor" interface as follows: >> REQ: GET /.well-known/core?if=3Dmysensor >>=20 >> I won't get the expected /temp resource in the result, because value mat= ching is done bitwise identical to the "if" string value between the double= quotes. Or is my argument wrong here? It seems this needs more explanation= in the draft - e.g. if using multiple values is reserved for some special = cases where querying is not used. >=20 > Good question. When multiple values are included in rel=3D, rt=3D or if= =3D attributes (regardless of the attribute), those are treated as separate= values logically. So your /temp link above has two separate if=3D attribut= e values, "http://www.example.org/myapp.wadl#sensor" and "mysensor". When a= query is made for if=3Dmysensor then that is compared against each value o= f if=3D associated with your links, and in this case it would match the lin= k.=20 >=20 > Seems that was not clear, so I agree we need to add some clarification te= xt to the Query Filter section. I will make a ticket and propose some text. >=20 > Zach >=20 >> regards, >> Esko >>=20 >> -----Original Message----- >> From: core-bounces@ietf.org [mailto:core-bounces@ietf.org] On Behalf Of = Carsten Bormann >> Sent: Thursday 24 May 2012 0:39 >> To: core@ietf.org WG >> Subject: [core] WG review period for: draft-ietf-core-link-format-13.txt >>=20 >> The recently submitted draft-ietf-core-link-format-13.txt is intended to= reflect IETF last call and in particular the IESG comments. >>=20 >> Drafts resulting from such a process have often been simply been publish= ed as RFCs without consulting the WG again. >> However, the responsible AD and the chairs all believe it is a good idea= to give the WG one more round to look at the result. >>=20 >> We are therefore announcing a one-week "WG review period" for the update= d draft: >>=20 >> http://tools.ietf.org/html/draft-ietf-core-link-format-13 >>=20 >> Some additional resources: >>=20 >> 1) >> http://datatracker.ietf.org/doc/draft-ietf-core-link-format/histor= y/ >>=20 >> gives you some visibility into what happened in the IETF/IESG process, a= nd what the DISCUSSes and COMMENTs were that the IESG provided. >>=20 >> 2) >> http://tools.ietf.org/rfcdiff?url2=3Ddraft-ietf-core-link-format-1= 3&url1=3Ddraft-ietf-core-link-format-11 >>=20 >> shows what changed between the version we submitted to the IESG and the = result of this process. >> As you can see, what mostly changed apart form editorial clarification w= as the selection of informal and formal description techniques that are in = use for the format and for the query syntax. >> Fortunately, some nice recently published documents like the definition = of Origin (RFC6454) and URI templates (RFC 6570) made this job a bit more p= leasant. >>=20 >> So, please do have a look, and tell the mailing list until >>=20 >> 2012-05-31, 12:59 UTC >>=20 >> whether there are remaining or new problems. >> (Please also do send a quick notice if you had a look and didn't find an= y problems.) >>=20 >> Gr=FC=DFe, Carsten >>=20 >> _______________________________________________ >> core mailing list >> core@ietf.org >> https://www.ietf.org/mailman/listinfo/core >>=20 >> ________________________________ >> The information contained in this message may be confidential and legall= y protected under applicable law. The message is intended solely for the ad= dressee(s). If you are not the intended recipient, you are hereby notified = that any use, forwarding, dissemination, or reproduction of this message is= strictly prohibited and may be unlawful. If you are not the intended recip= ient, please contact the sender by return e-mail and destroy all copies of = the original message. >>=20 >=20 > --=20 > Zach Shelby, Chief Nerd, Sensinode Ltd. > http://www.sensinode.com > http://zachshelby.org - My blog "On the Internet of Things" > http://6lowpan.net - My book "6LoWPAN: The Wireless Embedded Internet" > Mobile: +358 40 7796297 >=20 >=20 --=20 Zach Shelby, Chief Nerd, Sensinode Ltd. http://www.sensinode.com http://zachshelby.org - My blog "On the Internet of Things" http://6lowpan.net - My book "6LoWPAN: The Wireless Embedded Internet" Mobile: +358 40 7796297 From esko.dijk@philips.com Fri Jun 1 01:26:43 2012 Return-Path: X-Original-To: core@ietfa.amsl.com Delivered-To: core@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DC8E821F8528 for ; Fri, 1 Jun 2012 01:26:43 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.698 X-Spam-Level: X-Spam-Status: No, score=-3.698 tagged_above=-999 required=5 tests=[AWL=-0.100, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1] 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 dPlBFAAlxziW for ; Fri, 1 Jun 2012 01:26:42 -0700 (PDT) Received: from am1outboundpool.messaging.microsoft.com (am1ehsobe002.messaging.microsoft.com [213.199.154.205]) by ietfa.amsl.com (Postfix) with ESMTP id 2787221F851B for ; Fri, 1 Jun 2012 01:26:42 -0700 (PDT) Received: from mail76-am1-R.bigfish.com (10.3.201.239) by AM1EHSOBE001.bigfish.com (10.3.204.21) with Microsoft SMTP Server id 14.1.225.23; Fri, 1 Jun 2012 08:26:10 +0000 Received: from mail76-am1 (localhost [127.0.0.1]) by mail76-am1-R.bigfish.com (Postfix) with ESMTP id 83A1CC009C; Fri, 1 Jun 2012 08:26:10 +0000 (UTC) X-Forefront-Antispam-Report: CIP:157.55.7.222; KIP:(null); UIP:(null); IPV:NLI; H:mail.philips.com; RD:none; EFVD:NLI X-SpamScore: -33 X-BigFish: VPS-33(zz217bL15d6O9251Jc85fhzz1202hzz1033IL8275dhz2dh2a8h668h839hd25hf0ah) Received: from mail76-am1 (localhost.localdomain [127.0.0.1]) by mail76-am1 (MessageSwitch) id 1338539166758038_24368; Fri, 1 Jun 2012 08:26:06 +0000 (UTC) Received: from AM1EHSMHS011.bigfish.com (unknown [10.3.201.227]) by mail76-am1.bigfish.com (Postfix) with ESMTP id B65DB2E0046; Fri, 1 Jun 2012 08:26:06 +0000 (UTC) Received: from mail.philips.com (157.55.7.222) by AM1EHSMHS011.bigfish.com (10.3.207.111) with Microsoft SMTP Server (TLS) id 14.1.225.23; Fri, 1 Jun 2012 08:26:05 +0000 Received: from 011-DB3MPN1-013.MGDPHG.emi.philips.com ([169.254.3.141]) by 011-DB3MMR1-003.MGDPHG.emi.philips.com ([10.128.28.53]) with mapi id 14.01.0355.003; Fri, 1 Jun 2012 09:29:25 +0100 From: "Dijk, Esko" To: "core@ietf.org WG" , Zach Shelby Thread-Topic: draft-ietf-core-link-format-13: limitations to multiple values in single attribute removed? Thread-Index: Ac0/0CjuBMJeSGyaT9iTxmUX5w1ZAg== Date: Fri, 1 Jun 2012 08:25:54 +0000 Message-ID: <031DD135F9160444ABBE3B0C36CED6180D9320@011-DB3MPN1-013.MGDPHG.emi.philips.com> Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [194.171.252.101] Content-Type: multipart/alternative; boundary="_000_031DD135F9160444ABBE3B0C36CED6180D9320011DB3MPN1013MGDP_" MIME-Version: 1.0 X-OriginatorOrg: philips.com Subject: [core] draft-ietf-core-link-format-13: limitations to multiple values in single attribute removed? X-BeenThere: core@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Jun 2012 08:26:44 -0000 --_000_031DD135F9160444ABBE3B0C36CED6180D9320011DB3MPN1013MGDP_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable An additional point: we had ticket #178 (http://trac.tools.ietf.org/wg/core= /trac/ticket/178 ) to impose SHOULD NOT for use of multiple values in a sin= gle attribute. Later we had #199 (http://trac.tools.ietf.org/wg/core/trac/t= icket/199 ) to align better with RFC5988 in case multiple values is needed = despite the SHOULD NOT. However it seems that the "SHOULD NOT" was dropped = without discussion in writing the new text. I'm ok with the newest solution, though it implies a bit more parsing compl= exity on constrained devices. I did not find clear reasons/discussion for t= his change of mind though. Esko ________________________________ The information contained in this message may be confidential and legally p= rotected under applicable law. The message is intended solely for the addre= ssee(s). If you are not the intended recipient, you are hereby notified tha= t any use, forwarding, dissemination, or reproduction of this message is st= rictly prohibited and may be unlawful. If you are not the intended recipien= t, please contact the sender by return e-mail and destroy all copies of the= original message. --_000_031DD135F9160444ABBE3B0C36CED6180D9320011DB3MPN1013MGDP_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

An additional point: we had ticket #178 (http://trac.tools.i= etf.org/wg/core/trac/ticket/178 ) to impose SHOULD NOT for use of multi= ple values in a single attribute. Later we had #199 (http://trac.tools.ietf.org/wg/core/trac/ticket/199 ) to align better = with RFC5988 in case multiple values is needed despite the SHOULD NOT. Howe= ver it seems that the "SHOULD NOT" was dropped without discussion in writing the new text.

 

I’m ok with the newest solution, though it = implies a bit more parsing complexity on constrained devices. I did not fin= d clear reasons/discussion for this change of mind though.

 

Esko


The information contained in= this message may be confidential and legally protected under applicable la= w. The message is intended solely for the addressee(s). If you are not the = intended recipient, you are hereby notified that any use, forwarding, dissemination, or reproduction of this message i= s strictly prohibited and may be unlawful. If you are not the intended reci= pient, please contact the sender by return e-mail and destroy all copies of= the original message.
 --_000_031DD135F9160444ABBE3B0C36CED6180D9320011DB3MPN1013MGDP_-- From zach@sensinode.com Fri Jun 1 03:39:53 2012 Return-Path: X-Original-To: core@ietfa.amsl.com Delivered-To: core@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4867E21F8551 for ; Fri, 1 Jun 2012 03:39:53 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.599 X-Spam-Level: X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1] 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 DJGddXmUdD0x for ; Fri, 1 Jun 2012 03:39:52 -0700 (PDT) Received: from auth-smtp.nebula.fi (auth-smtp.nebula.fi [217.30.180.105]) by ietfa.amsl.com (Postfix) with ESMTP id C6F2021F8518 for ; Fri, 1 Jun 2012 03:39:50 -0700 (PDT) Received: from [192.168.1.102] (87-95-96-180.bb.dnainternet.fi [87.95.96.180]) (authenticated bits=0) by auth-smtp.nebula.fi (8.13.8/8.13.4) with ESMTP id q51Adlhx009262; Fri, 1 Jun 2012 13:39:48 +0300 Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: text/plain; charset=windows-1252 From: Zach Shelby In-Reply-To: <031DD135F9160444ABBE3B0C36CED6180D9320@011-DB3MPN1-013.MGDPHG.emi.philips.com> Date: Fri, 1 Jun 2012 13:39:46 +0300 Content-Transfer-Encoding: quoted-printable Message-Id: <71D28791-CB99-4677-8677-2A0226926BC2@sensinode.com> References: <031DD135F9160444ABBE3B0C36CED6180D9320@011-DB3MPN1-013.MGDPHG.emi.philips.com> To: "Dijk, Esko" X-Mailer: Apple Mail (2.1084) Cc: "core@ietf.org WG" Subject: Re: [core] draft-ietf-core-link-format-13: limitations to multiple values in single attribute removed? X-BeenThere: core@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Jun 2012 10:39:53 -0000 Esko, On Jun 1, 2012, at 11:25 AM, Dijk, Esko wrote: > An additional point: we had ticket #178 = (http://trac.tools.ietf.org/wg/core/trac/ticket/178 ) to impose SHOULD = NOT for use of multiple values in a single attribute. Later we had #199 = (http://trac.tools.ietf.org/wg/core/trac/ticket/199 ) to align better = with RFC5988 in case multiple values is needed despite the SHOULD NOT. = However it seems that the "SHOULD NOT" was dropped without discussion in = writing the new text. This was the result of two changes that we made due to IETF LC and IESG = reviews (there were discussions and tickets, but this was an easy point = to miss): 1. Due to the new CoRE Parameters registries, the rt=3D and if=3D = attributes became relation-types, just like rel=3D. Thus they inherited = the same properties. 2. In the past, we have allowed multiple rt=3D or if=3D attributes to be = included in a link, e.g.: ;rt=3D"temperature";rt=3D"outdoor-temperature" However in order to be compatible with RFC5988 and rel=3D, we were asked = to no longer allow multiple attributes (no other RFC5988 parameters do), = but instead allow multiple values in the attribute: ;rt=3D"temperature outdoor-temperature" The result of 1. and 2. is that we went from multiple attributes to = multiple values in an attribute. This achieves the same thing in the = end, and now all the relation-types attributes can be handled the same = way.=20 > I=92m ok with the newest solution, though it implies a bit more = parsing complexity on constrained devices. I did not find clear = reasons/discussion for this change of mind though. A constrained node is not forced to understand/store multiple values for = an attribute if its application has no such need. Also since each value = in a relation-type can not contain spaces, it is easy to parse that in = my experience.=20 Hopefully the explanation above clarifies the reasoning? Zach > =20 > Esko >=20 > The information contained in this message may be confidential and = legally protected under applicable law. The message is intended solely = for the addressee(s). If you are not the intended recipient, you are = hereby notified that any use, forwarding, dissemination, or reproduction = of this message is strictly prohibited and may be unlawful. If you are = not the intended recipient, please contact the sender by return e-mail = and destroy all copies of the original message. --=20 Zach Shelby, Chief Nerd, Sensinode Ltd. http://www.sensinode.com http://zachshelby.org - My blog "On the Internet of Things" http://6lowpan.net - My book "6LoWPAN: The Wireless Embedded Internet" Mobile: +358 40 7796297 From esko.dijk@philips.com Fri Jun 1 04:14:41 2012 Return-Path: X-Original-To: core@ietfa.amsl.com Delivered-To: core@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C0FB521F865B for ; Fri, 1 Jun 2012 04:14:41 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.685 X-Spam-Level: X-Spam-Status: No, score=-3.685 tagged_above=-999 required=5 tests=[AWL=-0.086, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1] 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 CGs6GNHZTa8n for ; Fri, 1 Jun 2012 04:14:40 -0700 (PDT) Received: from db3outboundpool.messaging.microsoft.com (db3ehsobe006.messaging.microsoft.com [213.199.154.144]) by ietfa.amsl.com (Postfix) with ESMTP id 6A41A21F8658 for ; Fri, 1 Jun 2012 04:14:40 -0700 (PDT) Received: from mail55-db3-R.bigfish.com (10.3.81.238) by DB3EHSOBE006.bigfish.com (10.3.84.26) with Microsoft SMTP Server id 14.1.225.23; Fri, 1 Jun 2012 11:14:09 +0000 Received: from mail55-db3 (localhost [127.0.0.1]) by mail55-db3-R.bigfish.com (Postfix) with ESMTP id C4E602C045D; Fri, 1 Jun 2012 11:14:08 +0000 (UTC) X-Forefront-Antispam-Report: CIP:157.55.7.222; KIP:(null); UIP:(null); IPV:NLI; H:mail.philips.com; RD:none; EFVD:NLI X-SpamScore: -48 X-BigFish: VPS-48(zz217bL15d6O9371I9251J542M1432N98dKzz1202hzz8275ch1033IL8275bh8275dhz2dh2a8h668h839h944hd25hf0ah) Received: from mail55-db3 (localhost.localdomain [127.0.0.1]) by mail55-db3 (MessageSwitch) id 1338549246634951_30304; Fri, 1 Jun 2012 11:14:06 +0000 (UTC) Received: from DB3EHSMHS009.bigfish.com (unknown [10.3.81.228]) by mail55-db3.bigfish.com (Postfix) with ESMTP id 8F90A3C0045; Fri, 1 Jun 2012 11:14:06 +0000 (UTC) Received: from mail.philips.com (157.55.7.222) by DB3EHSMHS009.bigfish.com (10.3.87.109) with Microsoft SMTP Server (TLS) id 14.1.225.23; Fri, 1 Jun 2012 11:14:05 +0000 Received: from 011-DB3MMR1-022.MGDPHG.emi.philips.com (10.128.28.105) by 011-DB3MMR1-008.MGDPHG.emi.philips.com (10.128.28.47) with Microsoft SMTP Server (TLS) id 14.1.355.3; Fri, 1 Jun 2012 12:14:35 +0100 Received: from 011-DB3MPN1-013.MGDPHG.emi.philips.com ([169.254.3.141]) by 011-DB3MMR1-022.MGDPHG.emi.philips.com ([fe80::1113:17d7:70dc:6faa%11]) with mapi id 14.01.0355.003; Fri, 1 Jun 2012 12:14:35 +0100 From: "Dijk, Esko" To: Zach Shelby Thread-Topic: draft-ietf-core-link-format-13: limitations to multiple values in single attribute removed? Thread-Index: Ac0/0CjuBMJeSGyaT9iTxmUX5w1ZAgAClHoAAANKDGA= Date: Fri, 1 Jun 2012 11:14:34 +0000 Message-ID: <031DD135F9160444ABBE3B0C36CED6180D93A2@011-DB3MPN1-013.MGDPHG.emi.philips.com> References: <031DD135F9160444ABBE3B0C36CED6180D9320@011-DB3MPN1-013.MGDPHG.emi.philips.com> <71D28791-CB99-4677-8677-2A0226926BC2@sensinode.com> In-Reply-To: <71D28791-CB99-4677-8677-2A0226926BC2@sensinode.com> Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [194.171.252.101] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-OriginatorOrg: philips.com Cc: "core@ietf.org WG" Subject: Re: [core] draft-ietf-core-link-format-13: limitations to multiple values in single attribute removed? X-BeenThere: core@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Jun 2012 11:14:41 -0000 Yes, clear for me thanks Esko -----Original Message----- From: Zach Shelby [mailto:zach@sensinode.com]=20 Sent: Friday 1 June 2012 12:40 To: Dijk, Esko Cc: core@ietf.org WG Subject: Re: draft-ietf-core-link-format-13: limitations to multiple values= in single attribute removed? Esko, On Jun 1, 2012, at 11:25 AM, Dijk, Esko wrote: > An additional point: we had ticket #178 (http://trac.tools.ietf.org/wg/co= re/trac/ticket/178 ) to impose SHOULD NOT for use of multiple values in a s= ingle attribute. Later we had #199 (http://trac.tools.ietf.org/wg/core/trac= /ticket/199 ) to align better with RFC5988 in case multiple values is neede= d despite the SHOULD NOT. However it seems that the "SHOULD NOT" was droppe= d without discussion in writing the new text. This was the result of two changes that we made due to IETF LC and IESG rev= iews (there were discussions and tickets, but this was an easy point to mis= s): 1. Due to the new CoRE Parameters registries, the rt=3D and if=3D attribute= s became relation-types, just like rel=3D. Thus they inherited the same pro= perties. 2. In the past, we have allowed multiple rt=3D or if=3D attributes to be in= cluded in a link, e.g.: ;rt=3D"temperature";rt=3D"outdoor-temperature" However in order to be compatible with RFC5988 and rel=3D, we were asked to= no longer allow multiple attributes (no other RFC5988 parameters do), but = instead allow multiple values in the attribute: ;rt=3D"temperature outdoor-temperature" The result of 1. and 2. is that we went from multiple attributes to multipl= e values in an attribute. This achieves the same thing in the end, and now = all the relation-types attributes can be handled the same way.=20 > I'm ok with the newest solution, though it implies a bit more parsing com= plexity on constrained devices. I did not find clear reasons/discussion for= this change of mind though. A constrained node is not forced to understand/store multiple values for an= attribute if its application has no such need. Also since each value in a = relation-type can not contain spaces, it is easy to parse that in my experi= ence.=20 Hopefully the explanation above clarifies the reasoning? Zach > =20 > Esko >=20 > The information contained in this message may be confidential and legally= protected under applicable law. The message is intended solely for the add= ressee(s). If you are not the intended recipient, you are hereby notified t= hat any use, forwarding, dissemination, or reproduction of this message is = strictly prohibited and may be unlawful. If you are not the intended recipi= ent, please contact the sender by return e-mail and destroy all copies of t= he original message. --=20 Zach Shelby, Chief Nerd, Sensinode Ltd. http://www.sensinode.com http://zachshelby.org - My blog "On the Internet of Things" http://6lowpan.net - My book "6LoWPAN: The Wireless Embedded Internet" Mobile: +358 40 7796297 From iesg-secretary@ietf.org Fri Jun 1 06:51:25 2012 Return-Path: X-Original-To: core@ietfa.amsl.com Delivered-To: core@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B989C11E8085; Fri, 1 Jun 2012 06:51:25 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.503 X-Spam-Level: X-Spam-Status: No, score=-102.503 tagged_above=-999 required=5 tests=[AWL=0.096, 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 WGe55JLbiV5y; Fri, 1 Jun 2012 06:51:25 -0700 (PDT) Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C1E3F11E8237; Fri, 1 Jun 2012 06:51:24 -0700 (PDT) Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: The IESG To: IETF-Announce X-Test-IDTracker: no X-IETF-IDTracker: 4.02 Message-ID: <20120601135124.1909.30497.idtracker@ietfa.amsl.com> Date: Fri, 01 Jun 2012 06:51:24 -0700 Cc: core chair , core mailing list , RFC Editor Subject: [core] Protocol Action: 'CoRE Link Format' to Proposed Standard (draft-ietf-core-link-format-14.txt) X-BeenThere: core@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Jun 2012 13:51:26 -0000 The IESG has approved the following document: - 'CoRE Link Format' (draft-ietf-core-link-format-14.txt) as Proposed Standard This document is the product of the Constrained RESTful Environments Working Group. The IESG contact persons are Barry Leiba and Pete Resnick. A URL of this Internet Draft is: http://datatracker.ietf.org/doc/draft-ietf-core-link-format/ Technical Summary To enable machine-to-machine communication using REST-style protocols, a standard way to do resource discovery is needed. The present document defines a link format to enable Web Linking by constrained web servers for describing hosted resources, their attributes and other relationships between links. A small variation of the HTTP Link Header format defined in RFC5988, the CoRE Link Format is carried as a payload and is assigned an Internet media type. A well-known URI is defined as a default entry-point for requesting the links to resources hosted by a server. Working Group Summary This document represents the consensus of the CoRE WG. There were no significant issues of contention regarding this specification. The principal content of the document has been technically stable for nearly a year, during which certain fringe cases were identified by reviewers and implementers, and addressed in minor updates to the specification. A list of the issues tracked and closed with regard to this document can be found here: http://trac.tools.ietf.org/wg/core/trac/query?component=link-format Document Quality The document is a product of the CoRE working group and has been reviewed in detail by a number of CoRE working group members, as well as by SecDir, GEN-ART, and AppsDir reviewers. The specification has been implemented widely in the CoRE community and has been used as a central element of the CoRE informal interoperability testing events. From kovatsch@inf.ethz.ch Sun Jun 3 00:26:43 2012 Return-Path: X-Original-To: core@ietfa.amsl.com Delivered-To: core@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F0C3C21F85F4 for ; Sun, 3 Jun 2012 00:26:43 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -7.999 X-Spam-Level: X-Spam-Status: No, score=-7.999 tagged_above=-999 required=5 tests=[BAYES_50=0.001, 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 teVb1YnCfsRR for ; Sun, 3 Jun 2012 00:26:43 -0700 (PDT) Received: from edge20.ethz.ch (edge20.ethz.ch [82.130.99.26]) by ietfa.amsl.com (Postfix) with ESMTP id CC55D21F85EF for ; Sun, 3 Jun 2012 00:26:41 -0700 (PDT) Received: from CAS21.d.ethz.ch (172.31.51.111) by edge20.ethz.ch (82.130.99.26) with Microsoft SMTP Server (TLS) id 14.2.298.4; Sun, 3 Jun 2012 09:26:13 +0200 Received: from MBX10.d.ethz.ch ([169.254.1.16]) by CAS21.d.ethz.ch ([fe80::55ba:c4a5:d8a7:ab62%10]) with mapi id 14.02.0298.004; Sun, 3 Jun 2012 09:26:13 +0200 From: "Kovatsch Matthias" To: "core@ietf.org WG" Thread-Topic: Observe-misc: concepts and terminology Thread-Index: AQHNQVonLHmp+VVBEE6i3W2knrvBtg== Date: Sun, 3 Jun 2012 07:26:12 +0000 Message-ID: In-Reply-To: <88AB1D5F-8EA5-47D4-AEDC-A969D1A8DBA8@tzi.org> Accept-Language: en-US, de-CH Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.2.2.120421 x-originating-ip: [178.83.15.45] Content-Type: text/plain; charset="iso-2022-jp" Content-ID: <14283BB3BED13B4FA220DEC048E37B2B@intern.ethz.ch> Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: Klaus Hartke Subject: [core] Observe-misc: concepts and terminology X-BeenThere: core@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Jun 2012 07:26:44 -0000 Dear List Apologies for being "last minute," but there have been some unforeseen occu= rrences=1B$B!D=1B(B Klaus and I worked on the concepts and terminology for Observe. Here is a q= uick summary that might help for the discussion. Klaus is working on a draf= t version "observe-misc" and will publish more details there. Note that this summary was not approved by Klaus, yet. The summary is also available here: https://docs.google.com/document/d/1FiYu5g7346YXj1gUrlxXD547rGr7mVVWVX-mBQb= Has0 Ciao Matthias Concepts Concept Definition Encoding Relationship Request Observe option in request Relationship Acceptance When a response has the Observe option set, it beco= mes a notification. Notifications have slightly different semantics than responses, in particul= ar for the meaning of Max-Age. Notifications can still be stored in caches, but all previous representatio= ns for the request URI become stale when a new new notification arrives. = Observe option in response =1B$B"*=1B(B notification Keep-Alive At least one of the notifications sent within a 24 hour tim= e frame MUST be confirmable. Implementation note: A server may send a redundant CON notification at a ce= rtain time of day (subject to congestion control) rather than keeping track= of the last confirmable notification it sent for each client and resource. Implementation note: A server may send a redundant CON notification at any = time to free an observer slot that might be blocked by a potentially dead c= lient. Protocol constant Relationship Refresh A client requests an Observe relationship although = it already received an Observe Acceptance. Observe option in request Earliest Notification The server knows that the resource cannot change it= s state within a certain time span (e.g., because of a sampling rate). (This is not Max-Age!) Min-Age option? Latest Notification The server says when it will send a new notificatio= n at latest, even when the resource state did not change, to refresh the re= presentation and observe relationship at the client. Clients optimistically assume the resource state did not change before Late= st Notification expires, but MAY perform a Relationship Refresh. When Latest Notification is reached, a CON notification is sent by the serv= er. Pledge option! non-negative integer that is added to the Cache Control value Default: use Max-Age value (does not work in some cases) Cache Control (Observe) A value for caches to calculate Max-Age when creati= ng a response from a stored notification. Max-Age option in notification= ! Polling Control A polling policy for clients to not poll again before the v= alue timed out. Similar to Latest Notification with Observe. Pledge option! Age The age of the resource representation in the cache Date Option= ? Payload? Freshness A freshness estimation during which a cached representation= can be used. On expiry, the information becomes stale and caches MUST NOT = return it. For Observe, the information can be assumed fresh until a new notification = arrives. The freshness estimation and notification intervals might differ c= onsiderably, though. Thus, Latest Notification is a different concept. M= ax-Age Option in response Authoritative information The information comes from the authoritativ= e source, i.e. the origin server Response code? Authoritative response bit? Non-authoritative information The information comes from a non-authoritat= ive source, e.g., proxy cache. (An intermediary cannot not have a cache, but the cache may have a very agg= ressive cache eviction policy.) Response code? Non-authoritative response bit? Refresh The client tells intermediaries along the path that it needs author= itative information and not a response from a cache. =1B$B!H=1B(BCache-cont= rol: no-cache=1B$B!I=1B(B Option? Problems Problem Effect Solution Mechanism Message latency and loss Max-Age might become zero Client might assume server problem Latest Notification might expire Eventual consistency Latest Notification backoff Message duplication MID / (same as Message reordering) Message reordering Sequence number/timestamp in each notificat= ion Client loses state Server wastes resources RST by client Keep-Alive Client temporarily goes away (sleeps) " Quality of implementation: = Sleepy clients should not initiate observe relationships. Client permanently goes away " Keep-Alive Server loses state Latest Notification expires Relationship Refres= h Server permanently goes away Latest Notification expires Relationship Refresh will ultimately fail Client gives up (Reasonable time for a retry?) From kovatsch@inf.ethz.ch Sun Jun 3 00:30:20 2012 Return-Path: X-Original-To: core@ietfa.amsl.com Delivered-To: core@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 35D8721F85EE for ; Sun, 3 Jun 2012 00:30:20 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -9.299 X-Spam-Level: X-Spam-Status: No, score=-9.299 tagged_above=-999 required=5 tests=[AWL=1.300, 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 j6e9EPHwy2oH for ; Sun, 3 Jun 2012 00:30:18 -0700 (PDT) Received: from edge20.ethz.ch (edge20.ethz.ch [82.130.99.26]) by ietfa.amsl.com (Postfix) with ESMTP id 5E7CD21F8535 for ; Sun, 3 Jun 2012 00:30:17 -0700 (PDT) Received: from CAS12.d.ethz.ch (172.31.38.212) by edge20.ethz.ch (82.130.99.26) with Microsoft SMTP Server (TLS) id 14.2.298.4; Sun, 3 Jun 2012 09:29:55 +0200 Received: from MBX10.d.ethz.ch ([169.254.1.16]) by CAS12.d.ethz.ch ([fe80::7861:4ecb:7c42:cad4%10]) with mapi id 14.02.0298.004; Sun, 3 Jun 2012 09:29:55 +0200 From: "Kovatsch Matthias" To: "core@ietf.org WG" Thread-Topic: [core] Observe-misc: concepts and terminology Thread-Index: AQHNQVonLHmp+VVBEE6i3W2knrvBtpboMqIA Date: Sun, 3 Jun 2012 07:29:55 +0000 Message-ID: In-Reply-To: Accept-Language: en-US, de-CH Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.2.2.120421 x-originating-ip: [178.83.15.45] Content-Type: text/plain; charset="Windows-1252" Content-ID: Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: Klaus Hartke Subject: Re: [core] Observe-misc: concepts and terminology X-BeenThere: core@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Jun 2012 07:30:20 -0000 Okay, no HTML allowed=8A Please use the link: https://docs.google.com/document/d/1zFbW6DqsozLE81sdwZy_IrNy4bkFd01TqWb98Rq rems/edit From jara@um.es Sun Jun 3 02:23:27 2012 Return-Path: X-Original-To: core@ietfa.amsl.com Delivered-To: core@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 351CA21F865D for ; Sun, 3 Jun 2012 02:23:27 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.477 X-Spam-Level: X-Spam-Status: No, score=-4.477 tagged_above=-999 required=5 tests=[AWL=-1.500, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1] 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 4fTIF+deNv3G for ; Sun, 3 Jun 2012 02:23:26 -0700 (PDT) Received: from xenon13.um.es (xenon13.um.es [155.54.212.167]) by ietfa.amsl.com (Postfix) with ESMTP id 9057221F865C for ; Sun, 3 Jun 2012 02:23:26 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by xenon13.um.es (Postfix) with ESMTP id 14DB15D533 for ; Sun, 3 Jun 2012 11:23:25 +0200 (CEST) X-Virus-Scanned: by antispam in UMU at xenon13.um.es Received: from xenon13.um.es ([127.0.0.1]) by localhost (xenon13.um.es [127.0.0.1]) (amavisd-new, port 10024) with LMTP id krCMJBOCKNQC for ; Sun, 3 Jun 2012 11:23:24 +0200 (CEST) Received: from mail-lpp01m010-f44.google.com (mail-lpp01m010-f44.google.com [209.85.215.44]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: jara) by xenon13.um.es (Postfix) with ESMTPSA id A5D1C5D519 for ; Sun, 3 Jun 2012 11:23:21 +0200 (CEST) Received: by lagv3 with SMTP id v3so2581188lag.31 for ; Sun, 03 Jun 2012 02:23:20 -0700 (PDT) Received: by 10.152.48.6 with SMTP id h6mr8682588lan.30.1338715400750; Sun, 03 Jun 2012 02:23:20 -0700 (PDT) MIME-Version: 1.0 Received: by 10.112.30.163 with HTTP; Sun, 3 Jun 2012 02:22:40 -0700 (PDT) In-Reply-To: References: From: Antonio Jara Date: Sun, 3 Jun 2012 11:22:40 +0200 Message-ID: To: Kovatsch Matthias Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: Klaus Hartke , "core@ietf.org WG" Subject: Re: [core] Observe-misc: concepts and terminology X-BeenThere: core@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Jun 2012 09:23:27 -0000 Dear Matthias, The link to google doc continues without working. Best regards, Antonio J. Jara On Sun, Jun 3, 2012 at 9:29 AM, Kovatsch Matthias w= rote: > Okay, no HTML allowed=C5=A0 > > Please use the link: > https://docs.google.com/document/d/1zFbW6DqsozLE81sdwZy_IrNy4bkFd01TqWb98= Rq > rems/edit > > > _______________________________________________ > core mailing list > core@ietf.org > https://www.ietf.org/mailman/listinfo/core From kovatsch@inf.ethz.ch Sun Jun 3 03:17:27 2012 Return-Path: X-Original-To: core@ietfa.amsl.com Delivered-To: core@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1316C21F8653 for ; Sun, 3 Jun 2012 03:17:27 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -9.949 X-Spam-Level: X-Spam-Status: No, score=-9.949 tagged_above=-999 required=5 tests=[AWL=0.650, 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 aM4CH+RS43-G for ; Sun, 3 Jun 2012 03:17:26 -0700 (PDT) Received: from edge20.ethz.ch (edge20.ethz.ch [82.130.99.26]) by ietfa.amsl.com (Postfix) with ESMTP id C5DA321F8655 for ; Sun, 3 Jun 2012 03:17:24 -0700 (PDT) Received: from CAS10.d.ethz.ch (172.31.38.210) by edge20.ethz.ch (82.130.99.26) with Microsoft SMTP Server (TLS) id 14.2.298.4; Sun, 3 Jun 2012 12:17:23 +0200 Received: from MBX10.d.ethz.ch ([169.254.1.16]) by CAS10.d.ethz.ch ([fe80::cce:fc66:7b56:a06a%10]) with mapi id 14.02.0298.004; Sun, 3 Jun 2012 12:17:23 +0200 From: "Kovatsch Matthias" To: Antonio Jara Thread-Topic: [core] Observe-misc: concepts and terminology Thread-Index: AQHNQVonLHmp+VVBEE6i3W2knrvBtpboMqIA///9+gCAADAZcA== Date: Sun, 3 Jun 2012 10:17:22 +0000 Message-ID: <55877B3AFB359744BA0F2140E36F52B5139D0170@MBX10.d.ethz.ch> References: In-Reply-To: Accept-Language: en-US, de-CH Content-Language: de-DE X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [178.83.15.45] Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 MIME-Version: 1.0 Cc: Klaus Hartke , "core@ietf.org WG" Subject: Re: [core] Observe-misc: concepts and terminology X-BeenThere: core@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Jun 2012 10:17:27 -0000 SSBhbSBzb3JyeSwgdGhlcmUgd2FzIGEgbWl4LXVwIHdpdGggdGhlIGhhc2ggdmFsdWUgVVJJcy4u Lg0KDQpUaGlzIGlzIHRoZSBjb3JyZWN0IGxpbmsgdG8gdGhlIHByZWxpbWluYXJ5IHN1bW1hcnk6 DQpodHRwczovL2RvY3MuZ29vZ2xlLmNvbS9kb2N1bWVudC9kLzFGaVl1NWc3MzQ2WVhqMWdVcmx4 WEQ1NDdyR3I3bVZWV1ZYLW1CUWJIYXMwL2VkaXQNCg0KQ2lhbw0KTWF0dGhpYXMNCg0KPiAtLS0t LVVyc3Byw7xuZ2xpY2hlIE5hY2hyaWNodC0tLS0tDQo+IFZvbjogQW50b25pbyBKYXJhIFttYWls dG86amFyYUB1bS5lc10NCj4gR2VzZW5kZXQ6IFNvbm50YWcsIDMuIEp1bmkgMjAxMiAxMToyMw0K PiBBbjogS292YXRzY2ggTWF0dGhpYXMNCj4gQ2M6IGNvcmVAaWV0Zi5vcmcgV0c7IEtsYXVzIEhh cnRrZQ0KPiBCZXRyZWZmOiBSZTogW2NvcmVdIE9ic2VydmUtbWlzYzogY29uY2VwdHMgYW5kIHRl cm1pbm9sb2d5DQo+IA0KPiBEZWFyIE1hdHRoaWFzLA0KPiANCj4gVGhlIGxpbmsgdG8gZ29vZ2xl IGRvYyBjb250aW51ZXMgd2l0aG91dCB3b3JraW5nLg0KPiANCj4gQmVzdCByZWdhcmRzLA0KPiBB bnRvbmlvIEouIEphcmENCj4gDQo+IE9uIFN1biwgSnVuIDMsIDIwMTIgYXQgOToyOSBBTSwgS292 YXRzY2ggIE1hdHRoaWFzIDxrb3ZhdHNjaEBpbmYuZXRoei5jaD4NCj4gd3JvdGU6DQo+ID4gT2th eSwgbm8gSFRNTCBhbGxvd2VkxaANCj4gPg0KPiA+IFBsZWFzZSB1c2UgdGhlIGxpbms6DQo+ID4N Cj4gaHR0cHM6Ly9kb2NzLmdvb2dsZS5jb20vZG9jdW1lbnQvZC8xekZiVzZEcXNvekxFODFzZHda eV9Jck55NGJrRmQwMVRxDQo+IFdiOThScQ0KPiA+IHJlbXMvZWRpdA0KPiA+DQo+ID4NCj4gPiBf X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KPiA+IGNvcmUg bWFpbGluZyBsaXN0DQo+ID4gY29yZUBpZXRmLm9yZw0KPiA+IGh0dHBzOi8vd3d3LmlldGYub3Jn L21haWxtYW4vbGlzdGluZm8vY29yZQ0K From kovatsch@inf.ethz.ch Sun Jun 3 05:57:20 2012 Return-Path: X-Original-To: core@ietfa.amsl.com Delivered-To: core@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 21BE921F8693 for ; Sun, 3 Jun 2012 05:57:20 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.166 X-Spam-Level: X-Spam-Status: No, score=-8.166 tagged_above=-999 required=5 tests=[AWL=-1.567, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4] 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 jRZFyQPXVbkT for ; Sun, 3 Jun 2012 05:57:19 -0700 (PDT) Received: from edge10.ethz.ch (edge10.ethz.ch [82.130.75.186]) by ietfa.amsl.com (Postfix) with ESMTP id 4115121F8692 for ; Sun, 3 Jun 2012 05:57:18 -0700 (PDT) Received: from CAS20.d.ethz.ch (172.31.51.110) by edge10.ethz.ch (82.130.75.186) with Microsoft SMTP Server (TLS) id 14.2.298.4; Sun, 3 Jun 2012 14:57:13 +0200 Received: from MBX10.d.ethz.ch ([169.254.1.16]) by CAS20.d.ethz.ch ([fe80::2cd8:4907:7776:c56d%10]) with mapi id 14.02.0298.004; Sun, 3 Jun 2012 14:57:17 +0200 From: "Kovatsch Matthias" To: "core@ietf.org WG" Thread-Topic: [core] Observe-misc: concepts and terminology Thread-Index: AQHNQVonLHmp+VVBEE6i3W2knrvBtpboMqIA///9+gCAADAZcIAALAqQ Date: Sun, 3 Jun 2012 12:57:16 +0000 Message-ID: <55877B3AFB359744BA0F2140E36F52B5139D027F@MBX10.d.ethz.ch> References: <55877B3AFB359744BA0F2140E36F52B5139D0170@MBX10.d.ethz.ch> In-Reply-To: <55877B3AFB359744BA0F2140E36F52B5139D0170@MBX10.d.ethz.ch> Accept-Language: en-US, de-CH Content-Language: de-DE X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [178.83.15.45] Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 MIME-Version: 1.0 Cc: "Klaus Hartke \(hartke@tzi.org\)" Subject: Re: [core] Observe-misc: concepts and terminology X-BeenThere: core@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Jun 2012 12:57:20 -0000 T2theSwgSSByZW1vdmVkIHRoZSBzdW1tYXJ5IGFnYWluLCBhcyB0aGUgT2JzZXJ2ZSBhY3Rpb24g aXRlbSB3YXMgbm90IGludGVuZGVkIHRvIGJlIGR1ZSB0b21vcnJvdy4NCldlIG5lZWQgbW9yZSB0 aW1lIHRvIGFncmVlIG9uIHRoZSBjb25jZXB0cyBhbmQgS2xhdXMgd2FudHMgdG8gYXZvaWQgbWlz aW50ZXJwcmV0YXRpb24gYW5kIHVubmVjZXNzYXJ5IGRpc2N1c3Npb24uDQoNClNvcnJ5IGFnYWlu IGZvciB0aGUgY29uZnVzaW9uIQ0KTWF0dGhpYXMNCg0KPiAtLS0tLVVyc3Byw7xuZ2xpY2hlIE5h Y2hyaWNodC0tLS0tDQo+IFZvbjogY29yZS1ib3VuY2VzQGlldGYub3JnIFttYWlsdG86Y29yZS1i b3VuY2VzQGlldGYub3JnXSBJbSBBdWZ0cmFnIHZvbg0KPiBLb3ZhdHNjaCBNYXR0aGlhcw0KPiBH ZXNlbmRldDogU29ubnRhZywgMy4gSnVuaSAyMDEyIDEyOjE3DQo+IEFuOiBBbnRvbmlvIEphcmEN Cj4gQ2M6IEtsYXVzIEhhcnRrZTsgY29yZUBpZXRmLm9yZyBXRw0KPiBCZXRyZWZmOiBSZTogW2Nv cmVdIE9ic2VydmUtbWlzYzogY29uY2VwdHMgYW5kIHRlcm1pbm9sb2d5DQo+IA0KPiBJIGFtIHNv cnJ5LCB0aGVyZSB3YXMgYSBtaXgtdXAgd2l0aCB0aGUgaGFzaCB2YWx1ZSBVUklzLi4uDQo+IA0K PiBUaGlzIGlzIHRoZSBjb3JyZWN0IGxpbmsgdG8gdGhlIHByZWxpbWluYXJ5IHN1bW1hcnk6DQo+ IGh0dHBzOi8vZG9jcy5nb29nbGUuY29tL2RvY3VtZW50L2QvMUZpWXU1ZzczNDZZWGoxZ1VybHhY RDU0N3JHcjdtVlZXDQo+IFZYLW1CUWJIYXMwL2VkaXQNCj4gDQo+IENpYW8NCj4gTWF0dGhpYXMN Cg== From zach@sensinode.com Mon Jun 4 01:49:22 2012 Return-Path: X-Original-To: core@ietfa.amsl.com Delivered-To: core@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 52A4521F87CB for ; Mon, 4 Jun 2012 01:49:22 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.599 X-Spam-Level: X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1] 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 FO31QL+dqwRn for ; Mon, 4 Jun 2012 01:49:21 -0700 (PDT) Received: from auth-smtp.nebula.fi (auth-smtp.nebula.fi [217.30.180.105]) by ietfa.amsl.com (Postfix) with ESMTP id 20D7221F8758 for ; Mon, 4 Jun 2012 01:49:20 -0700 (PDT) Received: from [172.20.10.4] (81-197-78-92.elisa-mobile.fi [81.197.78.92]) (authenticated bits=0) by auth-smtp.nebula.fi (8.13.8/8.13.4) with ESMTP id q548mkjv007391; Mon, 4 Jun 2012 11:48:57 +0300 Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: text/plain; charset=windows-1252 From: Zach Shelby In-Reply-To: <066.271de48b5e1ccd188c97e3dadc857964@trac.tools.ietf.org> Date: Mon, 4 Jun 2012 11:48:44 +0300 Content-Transfer-Encoding: quoted-printable Message-Id: <17F7A831-818A-40E1-8B72-71B9504C6202@sensinode.com> References: <051.e7fbc0f0f5736d305a309a9e8d0cd924@trac.tools.ietf.org> <066.271de48b5e1ccd188c97e3dadc857964@trac.tools.ietf.org> To: trac+core@gamay.tools.ietf.org X-Mailer: Apple Mail (2.1084) Cc: draft-ietf-core-coap@tools.ietf.org, core@ietf.org Subject: Re: [core] #202: Remove the 270 byte artificial limit X-BeenThere: core@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Jun 2012 08:49:22 -0000 Thanks Carsten. This is in alignment with what we agreed in the last = interop PhC. You also have a chance to comments on the list, but = otherwise I plan on integrating this change as proposed in misc-17 = Section 2.1.=20 Zach On May 26, 2012, at 3:38 PM, core issue tracker wrote: > #202: Remove the 270 byte artificial limit >=20 >=20 > Comment (by cabo@=85): >=20 > Some more detailed considerations are now in section 2.1 of > http://tools.ietf.org/html/draft-bormann-coap-misc-17#section-2.1 -- = these > are the result of the discussions in the interim. Actual text can be > generated when we have agreed (by review of this on the list, not just = on > the phone) on the principles. >=20 > --=20 > -----------------------------+------------------------------------- > Reporter: cabo@=85 | Owner: draft-ietf-core-coap@=85 > Type: protocol defect | Status: new > Priority: minor | Milestone: > Component: coap | Version: > Severity: In WG Last Call | Resolution: > Keywords: | > -----------------------------+------------------------------------- >=20 > Ticket URL: = > core >=20 > _______________________________________________ > core mailing list > core@ietf.org > https://www.ietf.org/mailman/listinfo/core --=20 Zach Shelby, Chief Nerd, Sensinode Ltd. http://www.sensinode.com http://zachshelby.org - My blog "On the Internet of Things" http://6lowpan.net - My book "6LoWPAN: The Wireless Embedded Internet" Mobile: +358 40 7796297 From trac+core@trac.tools.ietf.org Mon Jun 4 01:55:50 2012 Return-Path: X-Original-To: core@ietfa.amsl.com Delivered-To: core@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2811721F87D0 for ; Mon, 4 Jun 2012 01:55:50 -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 I4fLaZlrLT81 for ; Mon, 4 Jun 2012 01:55:49 -0700 (PDT) Received: from gamay.tools.ietf.org (gamay.tools.ietf.org [208.66.40.242]) by ietfa.amsl.com (Postfix) with ESMTP id 74BD321F8613 for ; Mon, 4 Jun 2012 01:55:48 -0700 (PDT) Received: from localhost ([::1] helo=gamay.tools.ietf.org) by gamay.tools.ietf.org with esmtp (Exim 4.77) (envelope-from ) id 1SbT4Y-0007dL-HQ; Mon, 04 Jun 2012 04:55:34 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit From: "core issue tracker" X-Trac-Version: 0.12.2 Precedence: bulk Auto-Submitted: auto-generated X-Mailer: Trac 0.12.2, by Edgewall Software To: draft-ietf-core-coap@tools.ietf.org, cabo@tzi.org, zach@sensinode.com X-Trac-Project: core Date: Mon, 04 Jun 2012 08:55:34 -0000 X-URL: http://tools.ietf.org/core/ X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/core/trac/ticket/232#comment:2 Message-ID: <068.d2e4c154b91be0e1f45249e9045492ee@trac.tools.ietf.org> References: <053.8004f0cc0b270920cdf2b55b6caf2b79@trac.tools.ietf.org> X-Trac-Ticket-ID: 232 In-Reply-To: <053.8004f0cc0b270920cdf2b55b6caf2b79@trac.tools.ietf.org> X-SA-Exim-Connect-IP: ::1 X-SA-Exim-Rcpt-To: draft-ietf-core-coap@tools.ietf.org, cabo@tzi.org, zach@sensinode.com, core@ietf.org X-SA-Exim-Mail-From: trac+core@trac.tools.ietf.org X-SA-Exim-Scanned: No (on gamay.tools.ietf.org); SAEximRunCond expanded to false Resent-To: Resent-Message-Id: <20120604085549.74BD321F8613@ietfa.amsl.com> Resent-Date: Mon, 4 Jun 2012 01:55:48 -0700 (PDT) Resent-From: trac+core@trac.tools.ietf.org Cc: core@ietf.org Subject: Re: [core] #232: Clarify inclusion of Location options in a 2.01 (Created) response X-BeenThere: core@ietf.org X-Mailman-Version: 2.1.12 Reply-To: trac+core@trac.tools.ietf.org List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Jun 2012 08:55:50 -0000 #232: Clarify inclusion of Location options in a 2.01 (Created) response Comment (by zach@…): Agreement in the May 16th interim meeting: MAY send a 2.01 Created response, aligning 5.10.8 and 5.8.2. -- -----------------------------+------------------------------------- Reporter: hartke@… | Owner: draft-ietf-core-coap@… Type: editorial | Status: new Priority: minor | Milestone: post-WGLC-1 Component: coap | Version: coap-09 Severity: In WG Last Call | Resolution: Keywords: | -----------------------------+------------------------------------- Ticket URL: core From trac+core@trac.tools.ietf.org Mon Jun 4 02:10:47 2012 Return-Path: X-Original-To: core@ietfa.amsl.com Delivered-To: core@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9BA6E21F87C9 for ; Mon, 4 Jun 2012 02:10:47 -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 Oy-5a2qZ7IZM for ; Mon, 4 Jun 2012 02:10:47 -0700 (PDT) Received: from gamay.tools.ietf.org (gamay.tools.ietf.org [208.66.40.242]) by ietfa.amsl.com (Postfix) with ESMTP id 27C5821F87A8 for ; Mon, 4 Jun 2012 02:10:46 -0700 (PDT) Received: from localhost ([::1] helo=gamay.tools.ietf.org) by gamay.tools.ietf.org with esmtp (Exim 4.77) (envelope-from ) id 1SbTJ4-0005rQ-Ou; Mon, 04 Jun 2012 05:10:35 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit From: "core issue tracker" X-Trac-Version: 0.12.2 Precedence: bulk Auto-Submitted: auto-generated X-Mailer: Trac 0.12.2, by Edgewall Software To: draft-ietf-core-coap@tools.ietf.org, cabo@tzi.org, zach@sensinode.com X-Trac-Project: core Date: Mon, 04 Jun 2012 09:10:34 -0000 X-URL: http://tools.ietf.org/core/ X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/core/trac/ticket/230#comment:2 Message-ID: <068.88cae224da461eb46451700b2516a0de@trac.tools.ietf.org> References: <053.8673136dcb3a579ebc337cc52e97888a@trac.tools.ietf.org> X-Trac-Ticket-ID: 230 In-Reply-To: <053.8673136dcb3a579ebc337cc52e97888a@trac.tools.ietf.org> X-SA-Exim-Connect-IP: ::1 X-SA-Exim-Rcpt-To: draft-ietf-core-coap@tools.ietf.org, cabo@tzi.org, zach@sensinode.com, core@ietf.org X-SA-Exim-Mail-From: trac+core@trac.tools.ietf.org X-SA-Exim-Scanned: No (on gamay.tools.ietf.org); SAEximRunCond expanded to false Resent-To: Resent-Message-Id: <20120604091047.27C5821F87A8@ietfa.amsl.com> Resent-Date: Mon, 4 Jun 2012 02:10:46 -0700 (PDT) Resent-From: trac+core@trac.tools.ietf.org Cc: core@ietf.org Subject: Re: [core] #230: Multiple Location options need to be processed as a unit X-BeenThere: core@ietf.org X-Mailman-Version: 2.1.12 Reply-To: trac+core@trac.tools.ietf.org List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Jun 2012 09:10:47 -0000 #230: Multiple Location options need to be processed as a unit Comment (by zach@…): Proposed solution in http://tools.ietf.org/html/draft-bormann-coap- misc-17#section-6 -- -----------------------------+------------------------------------- Reporter: hartke@… | Owner: draft-ietf-core-coap@… Type: protocol defect | Status: new Priority: minor | Milestone: post-WGLC-1 Component: coap | Version: coap-09 Severity: In WG Last Call | Resolution: Keywords: | -----------------------------+------------------------------------- Ticket URL: core From trac+core@trac.tools.ietf.org Mon Jun 4 02:16:23 2012 Return-Path: X-Original-To: core@ietfa.amsl.com Delivered-To: core@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4C65A21F87DF for ; Mon, 4 Jun 2012 02:16:23 -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=[AWL=0.000, 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 tyZYdlzJn20u for ; Mon, 4 Jun 2012 02:16:22 -0700 (PDT) Received: from gamay.tools.ietf.org (gamay.tools.ietf.org [208.66.40.242]) by ietfa.amsl.com (Postfix) with ESMTP id 7488021F87A7 for ; Mon, 4 Jun 2012 02:16:22 -0700 (PDT) Received: from localhost ([::1] helo=gamay.tools.ietf.org) by gamay.tools.ietf.org with esmtp (Exim 4.77) (envelope-from ) id 1SbTOX-00080e-6V; Mon, 04 Jun 2012 05:16:13 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit From: "core issue tracker" X-Trac-Version: 0.12.2 Precedence: bulk Auto-Submitted: auto-generated X-Mailer: Trac 0.12.2, by Edgewall Software To: draft-ietf-core-coap@tools.ietf.org, zach@sensinode.com X-Trac-Project: core Date: Mon, 04 Jun 2012 09:16:13 -0000 X-URL: http://tools.ietf.org/core/ X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/core/trac/ticket/238#comment:1 Message-ID: <066.9dacd3d4d91485d7fd5bf36c80748797@trac.tools.ietf.org> References: <051.6e14fd2778cd6bb461ee0489bd1726db@trac.tools.ietf.org> X-Trac-Ticket-ID: 238 In-Reply-To: <051.6e14fd2778cd6bb461ee0489bd1726db@trac.tools.ietf.org> X-SA-Exim-Connect-IP: ::1 X-SA-Exim-Rcpt-To: draft-ietf-core-coap@tools.ietf.org, zach@sensinode.com, core@ietf.org X-SA-Exim-Mail-From: trac+core@trac.tools.ietf.org X-SA-Exim-Scanned: No (on gamay.tools.ietf.org); SAEximRunCond expanded to false Resent-To: Resent-Message-Id: <20120604091622.7488021F87A7@ietfa.amsl.com> Resent-Date: Mon, 4 Jun 2012 02:16:22 -0700 (PDT) Resent-From: trac+core@trac.tools.ietf.org Cc: core@ietf.org Subject: Re: [core] #238: Proxy terminology X-BeenThere: core@ietf.org X-Mailman-Version: 2.1.12 Reply-To: trac+core@trac.tools.ietf.org List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Jun 2012 09:16:23 -0000 #238: Proxy terminology Comment (by zach@…): I would propose "translating proxy" -- -----------------------------+------------------------------------- Reporter: cabo@… | Owner: draft-ietf-core-coap@… Type: editorial | Status: new Priority: minor | Milestone: post-WGLC-1 Component: coap | Version: coap-09 Severity: In WG Last Call | Resolution: Keywords: | -----------------------------+------------------------------------- Ticket URL: core From zach@sensinode.com Mon Jun 4 02:35:16 2012 Return-Path: X-Original-To: core@ietfa.amsl.com Delivered-To: core@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B2A6D21F8620 for ; Mon, 4 Jun 2012 02:35:16 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.599 X-Spam-Level: X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1] 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 orete0taYoD3 for ; Mon, 4 Jun 2012 02:35:15 -0700 (PDT) Received: from auth-smtp.nebula.fi (auth-smtp.nebula.fi [217.30.180.105]) by ietfa.amsl.com (Postfix) with ESMTP id 54B3921F862A for ; Mon, 4 Jun 2012 02:35:15 -0700 (PDT) Received: from [172.20.10.4] (81-197-78-92.elisa-mobile.fi [81.197.78.92]) (authenticated bits=0) by auth-smtp.nebula.fi (8.13.8/8.13.4) with ESMTP id q549ZCl5017119 for ; Mon, 4 Jun 2012 12:35:13 +0300 From: Zach Shelby Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Date: Mon, 4 Jun 2012 12:35:11 +0300 Message-Id: <8B0C436E-267F-407E-8F0F-ACBC92B66446@sensinode.com> To: "core@ietf.org WG" Mime-Version: 1.0 (Apple Message framework v1084) X-Mailer: Apple Mail (2.1084) Subject: [core] Agenda for today's interim X-BeenThere: core@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Jun 2012 09:35:16 -0000 We have a CoRE interim meeting today at 15 CET (6 PST). I put together a = proposed agenda below. Assuming that Cullen will send around WebEx = information just before the meeting, so keep your eyes on the list for = that. CoRE Virtual Interim 2012-06-04 * Call to order (10 min) -- Notetakers etc. -- Agenda bashing * CoAP (59 min) -- check defined resolution and go ahead #230 Multiple Location options need to be processed as a unit new = protocol defect minor - Proposed solution in Section 6 of coap-misc-17 #201 Clarify use of retransmission window for duplicate detection new = editorial minor - Are we OK with Carsten's proposed solution in Section 7 of = coap-misc-17? #238 Proxy terminology new editorial minor - Zach proposes "translating proxy" -- discuss #214 Adopt vendor-defined option into core-coap new protocol = enhancement minor - Cullen had some push-back on this in the last interim meeting. = Felt it was better to=20 make the registration more permissible instead. Needs more = discussion. =20 #215 editorial issues around Congestion Control new editorial = major - Carsten has an open AP to propose changes in the ticket -- tickets with a clear solution (not planning to discuss) #202 Remove the 270 byte artificial limit new protocol defect = minor #207 Add advice on default values for critical options new = editorial minor #212 Option numbers 14, 28, 42, ... reserved but usable new = editorial minor #213 Path/Query options minimum length new protocol defect = minor #216 IANA: get Multicast addresses new other technical major #218 Mostly obvious section 5.10.8 fixes new hartke@tzi.org other = technical minor #222 RawPublicKey identifier new zach@sensinode.com protocol = enhancement minor #224 Clarify the concept of end-point new editorial major #226 Clarify which language addresses intermediaries in general vs. = forward proxies specifically new other technical major #228 Proxying of multicast requests new protocol enhancement = minor #229 Move sections 10-10.2. out of the "Security Considerations" new = editorial minor #231 Splitting/combining Location options new other technical = minor #232 Clarify inclusion of Location options in a 2.01 (Created) #response new editorial minor #233 Response codes with payload inconsistency new editorial = trivial #239 Always reserve option delta 15 new other technical minor * Observe (59 min) -- check defined resolution and go ahead #204 Introduce a minimal version of Pledge new protocol = enhancement major - Max-Age is OK as is - Proposal for Pledge in Section 4.3 of coap-misc-17 #221 Occasionally sending CON is not just a security consideration = new protocol defect minor - Cullen proposed that we define a constant of at least once a = day for this. OK? =09 -- discuss #217 how fast must the observe clock be able to go? new protocol = enhancement major - Need to agree on how long a packet can be in the network = (conclusion from last interim meeting notes) -- tickets with a clear way forward (not planning to discuss) #219 Clarify that observe is about eventual consistency new = editorial minor #223 Fix reordering detection condition description new = editorial minor #225 Explain why it is not always possible to react to a RST that is in = reply to a NON new editorial minor #227 Make aborting the previous transaction optional new = protocol enhancement minor - Proposed changing into a quality of implementation note #234 Editorial updates to -observe examples new hartke@tzi.org = editorial minor #235 Avoid extending the base standard retransmission rules new = other technical minor #236 Clarify the semantics of the "obs" link target attribute new = other technical minor #237 Multicast -> reference groupcomm draft new editorial = minor =20 --=20 Zach Shelby, Chief Nerd, Sensinode Ltd. http://www.sensinode.com http://zachshelby.org - My blog "On the Internet of Things" http://6lowpan.net - My book "6LoWPAN: The Wireless Embedded Internet" Mobile: +358 40 7796297 From fluffy@cisco.com Mon Jun 4 05:57:01 2012 Return-Path: X-Original-To: core@ietfa.amsl.com Delivered-To: core@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B33CD21F86A5 for ; Mon, 4 Jun 2012 05:57:01 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -112.598 X-Spam-Level: X-Spam-Status: No, score=-112.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, GB_I_INVITATION=-2, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8, 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 8zoDM6Bop-dh for ; Mon, 4 Jun 2012 05:57:00 -0700 (PDT) Received: from mtv-iport-4.cisco.com (mtv-iport-4.cisco.com [173.36.130.15]) by ietfa.amsl.com (Postfix) with ESMTP id C2F3521F8742 for ; Mon, 4 Jun 2012 05:57:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=fluffy@cisco.com; l=8369; q=dns/txt; s=iport; t=1338814620; x=1340024220; h=subject:mime-version:from:date:cc:message-id:references: to; bh=XWUjgPLsUSzstAGDx+RQW9YQAnOxX0r1PKD1HZrwWS4=; b=btrvNop2vGVYqGSuO8Q1Fiy0HzgGYDcizzIDCY4vOkMx5jq9gulM1MfY 08za2MUW2fOaW2oYLGTG19LTdGgqV8HSooUJgyhfTxMrvb6VDbzBZj0b3 o5QhFU09ndPqeaajAzTjHz1T0eB2Pu/D3HoteyKc6+SUiqpXHq4NmCflJ Y=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AjwFAI+vzE+rRDoI/2dsb2JhbAAqFwODHbEJgQeCGAEBAQMBEgEcNxMFCwUXAwECFQQMCkYJBwEDAxMih2QEDCmWTJEZjhOLESWCUAeCNGADiECMW4EPhEGIQIFmghZpgUA X-IronPort-AV: E=Sophos;i="4.75,712,1330905600"; d="scan'208,217";a="47485052" Received: from mtv-core-3.cisco.com ([171.68.58.8]) by mtv-iport-4.cisco.com with ESMTP; 04 Jun 2012 12:57:00 +0000 Received: from [192.168.4.100] (sjc-fluffy-8916.cisco.com [10.20.249.167]) by mtv-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id q54CuxuX007011; Mon, 4 Jun 2012 12:56:59 GMT Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: multipart/alternative; boundary=Apple-Mail-1--269833136 From: Cullen Jennings X-Priority: 1 Date: Mon, 4 Jun 2012 06:56:59 -0600 Message-Id: References: <1231638035.3268.1338814537776.JavaMail.nobody@jsj6tc001.webex.com> To: "core@ietf.org WG" X-Mailer: Apple Mail (2.1084) Subject: [core] WebEx for Call today. X-BeenThere: core@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Jun 2012 12:57:01 -0000 --Apple-Mail-1--269833136 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii > From: Cullen Jennings > Date: June 4, 2012 6:55:37 AM MDT > To: fluffy@cisco.com > Subject: (Forward to attendees) Please join now, meeting in progress: = CORE WG > Reply-To: fluffy@cisco.com >=20 > **** You can forward this email invitation to attendees ****=20 >=20 > Hello ,=20 >=20 > Please join my meeting that is currently in progress.=20 >=20 > Topic: CORE WG=20 > Date: Monday, June 4, 2012=20 > Time: 5:55 am, Pacific Daylight Time (San Francisco, GMT-07:00)=20 > Meeting Number: 209 571 862=20 > Meeting Password: ietf=20 >=20 >=20 > -------------------------------------------------------=20 > To join the online meeting (Now from mobile devices!)=20 > -------------------------------------------------------=20 > 1. Go to = https://cisco.webex.com/ciscosales/e.php?AT=3DMI&EventID=3D196453522&UID=3D= 0&PW=3DNOWU0ZTYzNmFj&RT=3DMiM0=20 > 2. Enter your name and email address.=20 > 3. Enter the meeting password: ietf=20 > 4. Click "Join Now".=20 > 5. Follow the instructions that appear on your screen.=20 >=20 > To view in other time zones or languages, please click the link:=20 > = https://cisco.webex.com/ciscosales/e.php?AT=3DMI&EventID=3D196453522&UID=3D= 0&PW=3DNOWU0ZTYzNmFj&ORT=3DMiM0=20 >=20 > ----------------------------------------------------------------=20 > ALERT:Toll-Free Dial Restrictions for (408) and (919) Area Codes=20 > ----------------------------------------------------------------=20 >=20 > The affected toll free numbers are: (866) 432-9903 for the San = Jose/Milpitas area and (866) 349-3520 for the RTP area.=20 >=20 > Please dial the local access number for your area from the list below:=20= > - San Jose/Milpitas (408) area: 525-6800=20 > - RTP (919) area: 392-3330=20 >=20 > -------------------------------------------------------=20 > To join the teleconference only=20 > -------------------------------------------------------=20 > 1. Dial into Cisco WebEx (view all Global Access Numbers at=20 > http://cisco.com/en/US/about/doing_business/conferencing/index.html=20 > 2. Follow the prompts to enter the Meeting Number (listed above) or = Access Code followed by the # sign.=20 >=20 > San Jose, CA: +1.408.525.6800 RTP: +1.919.392.3330=20 >=20 > US/Canada: +1.866.432.9903 United Kingdom: +44.20.8824.0117=20 >=20 > India: +91.80.4350.1111 Germany: +49.619.6773.9002=20 >=20 > Japan: +81.3.5763.9394 China: +86.10.8515.5666=20 >=20 > -------------------------------------------------------=20 > For assistance=20 > -------------------------------------------------------=20 > 1. Go to https://cisco.webex.com/ciscosales/mc=20 > 2. On the left navigation bar, click "Support".=20 >=20 > You can contact me at:=20 > fluffy@cisco.com=20 > 1-408-902 3341=20 >=20 >=20 --Apple-Mail-1--269833136 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii
From: Cullen Jennings <messenger@webex.com>
=
Date: June 4, 2012 = 6:55:37 AM MDT
Subject: (Forward to = attendees) Please join now, meeting in progress: CORE = WG

= **** You can forward this email invitation to attendees **** =

Hello ,

Please join my meeting that is currently in = progress.

Topic: CORE WG
Date: Monday, June 4, 2012
= Time: 5:55 am, Pacific Daylight Time (San Francisco, GMT-07:00)
= Meeting Number: 209 571 862
Meeting Password: ietf


= -------------------------------------------------------
To join the = online meeting (Now from mobile devices!)
= -------------------------------------------------------
1. Go to https://cisco.webex.com/ciscosales/e.php?AT=3DMI&Eve= ntID=3D196453522&UID=3D0&PW=3DNOWU0ZTYzNmFj&RT=3DMiM0 =
2. Enter your name and email address.
3. Enter the meeting = password: ietf
4. Click "Join Now".
5. Follow the instructions = that appear on your screen.

To view in other time zones or = languages, please click the link:
https://cisco.webex.com/ciscosales/e.php?AT=3DMI&Eve= ntID=3D196453522&UID=3D0&PW=3DNOWU0ZTYzNmFj&ORT=3DMiM0 =

= ----------------------------------------------------------------
= ALERT:Toll-Free Dial Restrictions for (408) and (919) Area Codes
= ----------------------------------------------------------------
=
The affected toll free numbers are: (866) 432-9903 for the San = Jose/Milpitas area and (866) 349-3520 for the RTP area.

Please = dial the local access number for your area from the list below:
- = San Jose/Milpitas (408) area: 525-6800
- RTP (919) area: 392-3330 =

-------------------------------------------------------
= To join the teleconference only
= -------------------------------------------------------
1. Dial = into Cisco WebEx (view all Global Access Numbers at
http://cisco.com/en/US/about/doing_business/conferencing= /index.html
2. Follow the prompts to enter the Meeting Number = (listed above) or Access Code followed by the # sign.

San = Jose, CA: +1.408.525.6800 RTP: +1.919.392.3330

US/Canada: = +1.866.432.9903 United Kingdom: +44.20.8824.0117

India: = +91.80.4350.1111 Germany: +49.619.6773.9002

Japan: = +81.3.5763.9394 China: +86.10.8515.5666

= -------------------------------------------------------
For = assistance
------------------------------------------------------- =
1. Go to https://cisco.webex.com/ciscosales/mc
2. On = the left navigation bar, click "Support".

You can contact me = at:
fluffy@cisco.com
= 1-408-902 3341

=

= --Apple-Mail-1--269833136-- From trac+core@trac.tools.ietf.org Mon Jun 4 06:44:47 2012 Return-Path: X-Original-To: core@ietfa.amsl.com Delivered-To: core@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F219721F87C4 for ; Mon, 4 Jun 2012 06:44:46 -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=[AWL=0.000, 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 o3oWNvyz8gvh for ; Mon, 4 Jun 2012 06:44:46 -0700 (PDT) Received: from gamay.tools.ietf.org (gamay.tools.ietf.org [208.66.40.242]) by ietfa.amsl.com (Postfix) with ESMTP id 0FBC921F86EC for ; Mon, 4 Jun 2012 06:44:45 -0700 (PDT) Received: from localhost ([::1] helo=gamay.tools.ietf.org) by gamay.tools.ietf.org with esmtp (Exim 4.77) (envelope-from ) id 1SbXa1-0000oc-Mq; Mon, 04 Jun 2012 09:44:21 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit From: "core issue tracker" X-Trac-Version: 0.12.2 Precedence: bulk Auto-Submitted: auto-generated X-Mailer: Trac 0.12.2, by Edgewall Software To: draft-ietf-core-coap@tools.ietf.org, cabo@tzi.org, angelo@castellani.net X-Trac-Project: core Date: Mon, 04 Jun 2012 13:44:20 -0000 X-URL: http://tools.ietf.org/core/ X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/core/trac/ticket/201#comment:5 Message-ID: <066.6904c04e7cd121d92730aedcf9ab88bd@trac.tools.ietf.org> References: <051.b90ea2a4caf57d34ab6abdaf3603301a@trac.tools.ietf.org> X-Trac-Ticket-ID: 201 In-Reply-To: <051.b90ea2a4caf57d34ab6abdaf3603301a@trac.tools.ietf.org> X-SA-Exim-Connect-IP: ::1 X-SA-Exim-Rcpt-To: draft-ietf-core-coap@tools.ietf.org, cabo@tzi.org, angelo@castellani.net, core@ietf.org X-SA-Exim-Mail-From: trac+core@trac.tools.ietf.org X-SA-Exim-Scanned: No (on gamay.tools.ietf.org); SAEximRunCond expanded to false Resent-To: Resent-Message-Id: <20120604134446.0FBC921F86EC@ietfa.amsl.com> Resent-Date: Mon, 4 Jun 2012 06:44:45 -0700 (PDT) Resent-From: trac+core@trac.tools.ietf.org Cc: core@ietf.org Subject: Re: [core] #201: Clarify use of retransmission window for duplicate detection X-BeenThere: core@ietf.org X-Mailman-Version: 2.1.12 Reply-To: trac+core@trac.tools.ietf.org List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Jun 2012 13:44:47 -0000 #201: Clarify use of retransmission window for duplicate detection Comment (by angelo@…): from msg03376: Question 1) MAX_RETRANSMIT_WAIT has been defined assuming that after the last retransmission, the endpoint should wait RESPONSE_TIMEOUT * (2 ** MAX_RETRANSMIT) * RESPONSE_RANDOM_FACTOR seconds before giving up definitely receiving a response. Is it right? ########################################################################### ########################################################################### ########################################################################### Question 1.1) What is the rationale behind having a lot of definitions such as MAX_LATENCY, MAX_RTT, PROCESSING_DELAY, EXCHANGE_LIFETIME? More clearly, why do we define later that the effective time that a node should wait to satisfy the defined worst case network conditions should be: PROCESSING_DELAY + (2 * MAX_LATENCY) This conflicts with MAX_RETRANSMIT_WAIT... Or am I missing something? ########################################################################### ########################################################################### ########################################################################### Question 2) It is not clear to me why do we define a simplified EXCHANGE_LIFETIME to: (RESPONSE_TIMEOUT * (2 ** MAX_RETRANSMIT) * RESPONSE_RANDOM_FACTOR) + (2 * MAX_LATENCY) Shouldn't be PROCESSING_DELAY + (2 * MAX_LATENCY) when we use NON messages, and MAX_RETRANSMIT_SPAN + PROCESSING_DELAY + (2 * MAX_LATENCY) when we use CON messages? -- -----------------------------+------------------------------------- Reporter: cabo@… | Owner: draft-ietf-core-coap@… Type: editorial | Status: new Priority: minor | Milestone: Component: coap | Version: Severity: In WG Last Call | Resolution: Keywords: | -----------------------------+------------------------------------- Ticket URL: core From trac+core@trac.tools.ietf.org Mon Jun 4 06:47:19 2012 Return-Path: X-Original-To: core@ietfa.amsl.com Delivered-To: core@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 94DAF21F86DB for ; Mon, 4 Jun 2012 06:47:19 -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=[AWL=0.000, 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 podZAy-ngZeU for ; Mon, 4 Jun 2012 06:47:19 -0700 (PDT) Received: from gamay.tools.ietf.org (gamay.tools.ietf.org [208.66.40.242]) by ietfa.amsl.com (Postfix) with ESMTP id EE92A21F8542 for ; Mon, 4 Jun 2012 06:47:18 -0700 (PDT) Received: from localhost ([::1] helo=gamay.tools.ietf.org) by gamay.tools.ietf.org with esmtp (Exim 4.77) (envelope-from ) id 1SbXcg-00020X-65; Mon, 04 Jun 2012 09:47:06 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit From: "core issue tracker" X-Trac-Version: 0.12.2 Precedence: bulk Auto-Submitted: auto-generated X-Mailer: Trac 0.12.2, by Edgewall Software To: draft-ietf-core-coap@tools.ietf.org, cabo@tzi.org, zach@sensinode.com, fluffy@cisco.com X-Trac-Project: core Date: Mon, 04 Jun 2012 13:47:06 -0000 X-URL: http://tools.ietf.org/core/ X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/core/trac/ticket/230#comment:3 Message-ID: <068.38e8a46abaa3cd563b6db224988b31d1@trac.tools.ietf.org> References: <053.8673136dcb3a579ebc337cc52e97888a@trac.tools.ietf.org> X-Trac-Ticket-ID: 230 In-Reply-To: <053.8673136dcb3a579ebc337cc52e97888a@trac.tools.ietf.org> X-SA-Exim-Connect-IP: ::1 X-SA-Exim-Rcpt-To: draft-ietf-core-coap@tools.ietf.org, cabo@tzi.org, zach@sensinode.com, fluffy@cisco.com, core@ietf.org X-SA-Exim-Mail-From: trac+core@trac.tools.ietf.org X-SA-Exim-Scanned: No (on gamay.tools.ietf.org); SAEximRunCond expanded to false Resent-To: Resent-Message-Id: <20120604134718.EE92A21F8542@ietfa.amsl.com> Resent-Date: Mon, 4 Jun 2012 06:47:18 -0700 (PDT) Resent-From: trac+core@trac.tools.ietf.org Cc: core@ietf.org Subject: Re: [core] #230: Multiple Location options need to be processed as a unit X-BeenThere: core@ietf.org X-Mailman-Version: 2.1.12 Reply-To: trac+core@trac.tools.ietf.org List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Jun 2012 13:47:19 -0000 #230: Multiple Location options need to be processed as a unit Comment (by fluffy@…): summary of call Would not add envelope now - might add later. In addition we allocate a few reserved number for use be later specs in the URI that have to be understood. Could use for port, host, etc later. Proposal made that we have a rule that “safe to forward without understanding options” have a number of something like option number mod 7 = 5. (of course more thought on 7 and 5 but you get the idea) -- -----------------------------+------------------------------------- Reporter: hartke@… | Owner: draft-ietf-core-coap@… Type: protocol defect | Status: new Priority: minor | Milestone: post-WGLC-1 Component: coap | Version: coap-09 Severity: In WG Last Call | Resolution: Keywords: | -----------------------------+------------------------------------- Ticket URL: core From trac+core@trac.tools.ietf.org Mon Jun 4 07:15:07 2012 Return-Path: X-Original-To: core@ietfa.amsl.com Delivered-To: core@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BED9E21F86E1 for ; Mon, 4 Jun 2012 07:15:07 -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=[AWL=0.000, 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 IKPtxE-jBqFQ for ; Mon, 4 Jun 2012 07:15:06 -0700 (PDT) Received: from gamay.tools.ietf.org (gamay.tools.ietf.org [208.66.40.242]) by ietfa.amsl.com (Postfix) with ESMTP id 88EB021F86DE for ; Mon, 4 Jun 2012 07:15:06 -0700 (PDT) Received: from localhost ([::1] helo=gamay.tools.ietf.org) by gamay.tools.ietf.org with esmtp (Exim 4.77) (envelope-from ) id 1SbY3Y-0000lS-2U; Mon, 04 Jun 2012 10:14:52 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit From: "core issue tracker" X-Trac-Version: 0.12.2 Precedence: bulk Auto-Submitted: auto-generated X-Mailer: Trac 0.12.2, by Edgewall Software To: draft-ietf-core-coap@tools.ietf.org, zach@sensinode.com, angelo@castellani.net X-Trac-Project: core Date: Mon, 04 Jun 2012 14:14:52 -0000 X-URL: http://tools.ietf.org/core/ X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/core/trac/ticket/238#comment:2 Message-ID: <066.0677dd1f5778274ba127aed08949ea94@trac.tools.ietf.org> References: <051.6e14fd2778cd6bb461ee0489bd1726db@trac.tools.ietf.org> X-Trac-Ticket-ID: 238 In-Reply-To: <051.6e14fd2778cd6bb461ee0489bd1726db@trac.tools.ietf.org> X-SA-Exim-Connect-IP: ::1 X-SA-Exim-Rcpt-To: draft-ietf-core-coap@tools.ietf.org, zach@sensinode.com, angelo@castellani.net, core@ietf.org X-SA-Exim-Mail-From: trac+core@trac.tools.ietf.org X-SA-Exim-Scanned: No (on gamay.tools.ietf.org); SAEximRunCond expanded to false Resent-To: Resent-Message-Id: <20120604141506.88EB021F86DE@ietfa.amsl.com> Resent-Date: Mon, 4 Jun 2012 07:15:06 -0700 (PDT) Resent-From: trac+core@trac.tools.ietf.org Cc: core@ietf.org Subject: Re: [core] #238: Proxy terminology X-BeenThere: core@ietf.org X-Mailman-Version: 2.1.12 Reply-To: trac+core@trac.tools.ietf.org List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Jun 2012 14:15:08 -0000 #238: Proxy terminology Comment (by angelo@…): from core-http-mapping-04: 2. Terminology A device providing cross-protocol HTTP-CoAP mapping is called an HTTP-CoAP cross-protocol proxy (HC proxy). -- -----------------------------+------------------------------------- Reporter: cabo@… | Owner: draft-ietf-core-coap@… Type: editorial | Status: new Priority: minor | Milestone: post-WGLC-1 Component: coap | Version: coap-09 Severity: In WG Last Call | Resolution: Keywords: | -----------------------------+------------------------------------- Ticket URL: core From trac+core@trac.tools.ietf.org Mon Jun 4 07:30:06 2012 Return-Path: X-Original-To: core@ietfa.amsl.com Delivered-To: core@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0E40F21F86FD for ; Mon, 4 Jun 2012 07:30:06 -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=[AWL=0.000, 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 dM6ih-OQbK5N for ; Mon, 4 Jun 2012 07:30:05 -0700 (PDT) Received: from gamay.tools.ietf.org (gamay.tools.ietf.org [208.66.40.242]) by ietfa.amsl.com (Postfix) with ESMTP id 85EC221F86F5 for ; Mon, 4 Jun 2012 07:30:05 -0700 (PDT) Received: from localhost ([::1] helo=gamay.tools.ietf.org) by gamay.tools.ietf.org with esmtp (Exim 4.77) (envelope-from ) id 1SbYI7-00021M-Oo; Mon, 04 Jun 2012 10:29:55 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit From: "core issue tracker" X-Trac-Version: 0.12.2 Precedence: bulk Auto-Submitted: auto-generated X-Mailer: Trac 0.12.2, by Edgewall Software To: draft-ietf-core-coap@tools.ietf.org, fluffy@cisco.com X-Trac-Project: core Date: Mon, 04 Jun 2012 14:29:55 -0000 X-URL: http://tools.ietf.org/core/ X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/core/trac/ticket/214#comment:1 Message-ID: <066.9aac0386d5613726e64ba09f36068695@trac.tools.ietf.org> References: <051.09186ada57b912f27c3147c188e4fd71@trac.tools.ietf.org> X-Trac-Ticket-ID: 214 In-Reply-To: <051.09186ada57b912f27c3147c188e4fd71@trac.tools.ietf.org> X-SA-Exim-Connect-IP: ::1 X-SA-Exim-Rcpt-To: draft-ietf-core-coap@tools.ietf.org, fluffy@cisco.com, core@ietf.org X-SA-Exim-Mail-From: trac+core@trac.tools.ietf.org X-SA-Exim-Scanned: No (on gamay.tools.ietf.org); SAEximRunCond expanded to false Resent-To: Resent-Message-Id: <20120604143005.85EC221F86F5@ietfa.amsl.com> Resent-Date: Mon, 4 Jun 2012 07:30:05 -0700 (PDT) Resent-From: trac+core@trac.tools.ietf.org Cc: core@ietf.org Subject: Re: [core] #214: Adopt vendor-defined option into core-coap X-BeenThere: core@ietf.org X-Mailman-Version: 2.1.12 Reply-To: trac+core@trac.tools.ietf.org List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Jun 2012 14:30:06 -0000 #214: Adopt vendor-defined option into core-coap Comment (by fluffy@…): Carsten proposal: reserved a option number that first 2 bytes of data is an code point that is allocated by IANA. reserver another options for 3 bytes, 1 byte, etc. Need two sets of these numbers - one for critical and one for elective. Action: Carsten will write up in COAP misc. -- ----------------------------------+------------------------------------- Reporter: cabo@… | Owner: draft-ietf-core-coap@… Type: protocol enhancement | Status: new Priority: minor | Milestone: post-WGLC-1 Component: coap | Version: coap-09 Severity: In WG Last Call | Resolution: Keywords: | ----------------------------------+------------------------------------- Ticket URL: core From trac+core@trac.tools.ietf.org Mon Jun 4 07:41:04 2012 Return-Path: X-Original-To: core@ietfa.amsl.com Delivered-To: core@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A31F321F87D0 for ; Mon, 4 Jun 2012 07:41:03 -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 4l4KAWZmPLvX for ; Mon, 4 Jun 2012 07:41:01 -0700 (PDT) Received: from gamay.tools.ietf.org (gamay.tools.ietf.org [208.66.40.242]) by ietfa.amsl.com (Postfix) with ESMTP id 6594721F87BF for ; Mon, 4 Jun 2012 07:41:01 -0700 (PDT) Received: from localhost ([::1] helo=gamay.tools.ietf.org) by gamay.tools.ietf.org with esmtp (Exim 4.77) (envelope-from ) id 1SbYSq-0004oM-CU; Mon, 04 Jun 2012 10:41:00 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit From: "core issue tracker" X-Trac-Version: 0.12.2 Precedence: bulk Auto-Submitted: auto-generated X-Mailer: Trac 0.12.2, by Edgewall Software To: draft-ietf-core-observe@tools.ietf.org, fluffy@cisco.com X-Trac-Project: core Date: Mon, 04 Jun 2012 14:41:00 -0000 X-URL: http://tools.ietf.org/core/ X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/core/trac/ticket/221#comment:1 Message-ID: <066.6f69592c4f5ae0e6d167123606fbcc4b@trac.tools.ietf.org> References: <051.96050ca332dbb50866094e054b75514d@trac.tools.ietf.org> X-Trac-Ticket-ID: 221 In-Reply-To: <051.96050ca332dbb50866094e054b75514d@trac.tools.ietf.org> X-SA-Exim-Connect-IP: ::1 X-SA-Exim-Rcpt-To: draft-ietf-core-observe@tools.ietf.org, fluffy@cisco.com, core@ietf.org X-SA-Exim-Mail-From: trac+core@trac.tools.ietf.org X-SA-Exim-Scanned: No (on gamay.tools.ietf.org); SAEximRunCond expanded to false Resent-To: Resent-Message-Id: <20120604144101.6594721F87BF@ietfa.amsl.com> Resent-Date: Mon, 4 Jun 2012 07:41:01 -0700 (PDT) Resent-From: trac+core@trac.tools.ietf.org Cc: core@ietf.org Subject: Re: [core] #221: Occasionally sending CON is not just a security consideration X-BeenThere: core@ietf.org X-Mailman-Version: 2.1.12 Reply-To: trac+core@trac.tools.ietf.org List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Jun 2012 14:41:04 -0000 #221: Occasionally sending CON is not just a security consideration Comment (by fluffy@…): Point out this may be too often - for example sensors that wake up once a week. Point made many applications need to do it much more frequently. Conclusion: People seemed OK with this. Move forward with this change. -- -----------------------------+---------------------------------------- Reporter: cabo@… | Owner: draft-ietf-core-observe@… Type: protocol defect | Status: new Priority: minor | Milestone: post-WGLC-1 Component: observe | Version: observe-05 Severity: In WG Last Call | Resolution: Keywords: | -----------------------------+---------------------------------------- Ticket URL: core From zach@sensinode.com Mon Jun 4 08:08:29 2012 Return-Path: X-Original-To: core@ietfa.amsl.com Delivered-To: core@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2CC0321F88A1 for ; Mon, 4 Jun 2012 08:08:29 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.599 X-Spam-Level: X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1] 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 VZHD4pHpHcPk for ; Mon, 4 Jun 2012 08:08:28 -0700 (PDT) Received: from auth-smtp.nebula.fi (auth-smtp.nebula.fi [217.30.180.105]) by ietfa.amsl.com (Postfix) with ESMTP id 1FCF621F8883 for ; Mon, 4 Jun 2012 08:08:27 -0700 (PDT) Received: from [172.20.10.4] (81-197-78-92.elisa-mobile.fi [81.197.78.92]) (authenticated bits=0) by auth-smtp.nebula.fi (8.13.8/8.13.4) with ESMTP id q54F8NwM016907 for ; Mon, 4 Jun 2012 18:08:25 +0300 From: Zach Shelby Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Date: Mon, 4 Jun 2012 18:08:17 +0300 References: <20120604141804.23098.42455.idtracker@ietfa.amsl.com> To: "core@ietf.org WG" Message-Id: Mime-Version: 1.0 (Apple Message framework v1084) X-Mailer: Apple Mail (2.1084) Subject: [core] Fwd: Last Call: (Naming Things with Hashes) to Proposed Standard X-BeenThere: core@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Jun 2012 15:08:29 -0000 FYI - this is a draft that we have a dependency on in CoAP for our = public key identity hash. Great to see it making progress.=20 Zach Begin forwarded message: > From: The IESG > Date: June 4, 2012 5:18:04 PM GMT+03:00 > To: IETF-Announce > Subject: Last Call: (Naming Things = with Hashes) to Proposed Standard > Reply-To: ietf@ietf.org >=20 >=20 > The IESG has received a request from an individual submitter to = consider > the following document: > - 'Naming Things with Hashes' > as Proposed Standard >=20 > 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 2012-07-02. 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. >=20 > Abstract >=20 >=20 > This document defines a set of ways to identify a thing using the > output from a hash function, specifying URI, URL, binary and human > "speakable" formats for these names. The various formats are > designed to support, but not require, a strong link to the = referenced > object such that the referenced object may be authenticated to the > same degree as the reference to it. >=20 >=20 >=20 >=20 > The file can be obtained via > http://datatracker.ietf.org/doc/draft-farrell-decade-ni/ >=20 > IESG discussion can be tracked via > http://datatracker.ietf.org/doc/draft-farrell-decade-ni/ballot/ >=20 >=20 > The following IPR Declarations may be related to this I-D: >=20 > http://datatracker.ietf.org/ipr/1773/ > http://datatracker.ietf.org/ipr/1775/ >=20 >=20 >=20 --=20 Zach Shelby, Chief Nerd, Sensinode Ltd. http://www.sensinode.com http://zachshelby.org - My blog "On the Internet of Things" http://6lowpan.net - My book "6LoWPAN: The Wireless Embedded Internet" Mobile: +358 40 7796297 From stephen.farrell@cs.tcd.ie Mon Jun 4 08:13:25 2012 Return-Path: X-Original-To: core@ietfa.amsl.com Delivered-To: core@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E6CDD21F8890 for ; Mon, 4 Jun 2012 08:13:25 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -103.906 X-Spam-Level: X-Spam-Status: No, score=-103.906 tagged_above=-999 required=5 tests=[AWL=-1.307, 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 qnQCt0Arc22e for ; Mon, 4 Jun 2012 08:13:25 -0700 (PDT) Received: from scss.tcd.ie (hermes.scss.tcd.ie [IPv6:2001:770:10:200:889f:cdff:fe8d:ccd2]) by ietfa.amsl.com (Postfix) with ESMTP id DF5D321F8864 for ; Mon, 4 Jun 2012 08:13:24 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by hermes.scss.tcd.ie (Postfix) with ESMTP id 1DB361714E6; Mon, 4 Jun 2012 16:13:22 +0100 (IST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; h= content-transfer-encoding:content-type:in-reply-to:references :subject:mime-version:user-agent:from:date:message-id:received :received:x-virus-scanned; s=cs; t=1338822800; bh=9EFnap+RnO4p7b mNUk2zO9k6j82i0kt4RYdbtTG3I9M=; b=IPn8XK5dFSIYdKv5Tkp8CbtMzfh0AR 9E2d0xWnI7aL4Pz7vYC2cRWl20mvtq/DNIjKx7SvTrfAR+6KWJB0EsJHSeYTzOU5 flBSZnozUipxnWtiVnFDD8y9uG8KH00bl/p9+Jn5kMCLVRMrTRIOwJDgyMXeLpre 5M9HWzEb3/Lfuaz7czLPH9P3VtwQVt9Od7Hv/Haniejtn6nsordRLL+GTPwBEOo6 XhIDYUny/wAZ/g7GWB/Y6oqBlnE7vT4ieKW1UMAFmrlwaDtJQMQK161UWJbFjiuA 7WxNDscIYvWIykA2of089EWj6eAQJNlliWLrGnFJG/XIimCjnoAcKqMw== X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie Received: from scss.tcd.ie ([127.0.0.1]) by localhost (scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10027) with ESMTP id lDunnZYt64-N; Mon, 4 Jun 2012 16:13:20 +0100 (IST) Received: from [10.87.48.8] (unknown [86.41.6.142]) by smtp.scss.tcd.ie (Postfix) with ESMTPSA id A03B11714DC; Mon, 4 Jun 2012 16:13:20 +0100 (IST) Message-ID: <4FCCD090.1020109@cs.tcd.ie> Date: Mon, 04 Jun 2012 16:13:20 +0100 From: Stephen Farrell User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:12.0) Gecko/20120430 Thunderbird/12.0.1 MIME-Version: 1.0 To: Zach Shelby References: <20120604141804.23098.42455.idtracker@ietfa.amsl.com> In-Reply-To: X-Enigmail-Version: 1.4.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: "core@ietf.org WG" Subject: Re: [core] Fwd: Last Call: (Naming Things with Hashes) to Proposed Standard X-BeenThere: core@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Jun 2012 15:13:26 -0000 On 06/04/2012 04:08 PM, Zach Shelby wrote: > FYI - this is a draft that we have a dependency on in CoAP for our public key identity hash. Great to see it making progress. It is:-) We've also updated the code for it [1] if that's useful for anyone. Ultimately that code is intended for other things, but its apache licensed so folks can grab what they find useful from the c, python, ruby or clojure libraries that are up to date wrt -07. Other bits of the code are more work in progress, but the stuff you guys care about should be usable. Cheers, S. [1] http://sourceforge.net/projects/netinf/ > Zach > > Begin forwarded message: > >> From: The IESG >> Date: June 4, 2012 5:18:04 PM GMT+03:00 >> To: IETF-Announce >> Subject: Last Call: (Naming Things with Hashes) to Proposed Standard >> Reply-To: ietf@ietf.org >> >> >> The IESG has received a request from an individual submitter to consider >> the following document: >> - 'Naming Things with Hashes' >> 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 2012-07-02. 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 set of ways to identify a thing using the >> output from a hash function, specifying URI, URL, binary and human >> "speakable" formats for these names. The various formats are >> designed to support, but not require, a strong link to the referenced >> object such that the referenced object may be authenticated to the >> same degree as the reference to it. >> >> >> >> >> The file can be obtained via >> http://datatracker.ietf.org/doc/draft-farrell-decade-ni/ >> >> IESG discussion can be tracked via >> http://datatracker.ietf.org/doc/draft-farrell-decade-ni/ballot/ >> >> >> The following IPR Declarations may be related to this I-D: >> >> http://datatracker.ietf.org/ipr/1773/ >> http://datatracker.ietf.org/ipr/1775/ >> >> >> > From fluffy@cisco.com Mon Jun 4 08:13:50 2012 Return-Path: X-Original-To: core@ietfa.amsl.com Delivered-To: core@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 52E7F21F88BA for ; Mon, 4 Jun 2012 08:13:50 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -111.599 X-Spam-Level: X-Spam-Status: No, score=-111.599 tagged_above=-999 required=5 tests=[AWL=-1.000, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, 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 5fOOljponj4T for ; Mon, 4 Jun 2012 08:13:48 -0700 (PDT) Received: from mtv-iport-2.cisco.com (mtv-iport-2.cisco.com [173.36.130.13]) by ietfa.amsl.com (Postfix) with ESMTP id F1F9221F8864 for ; Mon, 4 Jun 2012 08:13:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=fluffy@cisco.com; l=7336; q=dns/txt; s=iport; t=1338822828; x=1340032428; h=from:content-transfer-encoding:subject:date:message-id: to:mime-version; bh=G8dRSfRsAEdUgpRUfgtsM0UKi38/VpAATihjUDxMKA0=; b=JenLo+48n0ekzlA16aLEZiLOF9tuJBLIgxYXdQNTgAbwhIKeSx5usGoD Wd+btxZuC0ivYvaLLcEQVGFMp3er2/BEqK9ctB2+Nz6740sCMTPfMZYtt X1bYbU8Fhf+YDhLJ4X4WshF0MarowPWvQ+Ur5uF769oUUWNHN2yqreHQL o=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AicFAKDPzE+rRDoH/2dsb2JhbABEgx2xD4EHghoBBQEBDwGBbjYuBAOHaAyVaYEonysEiyYPhQxgA4hAjFuFUIhAgWaCf4E4CA X-IronPort-AV: E=Sophos;i="4.75,713,1330905600"; d="scan'208";a="47584245" Received: from mtv-core-2.cisco.com ([171.68.58.7]) by mtv-iport-2.cisco.com with ESMTP; 04 Jun 2012 15:13:47 +0000 Received: from [192.168.4.100] (sjc-fluffy-8916.cisco.com [10.20.249.167]) by mtv-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id q54FDlv0021352 for ; Mon, 4 Jun 2012 15:13:47 GMT From: Cullen Jennings Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Date: Mon, 4 Jun 2012 09:13:47 -0600 Message-Id: <0E8162DB-0525-4A12-BAAD-9006CCE9539E@cisco.com> To: "core@ietf.org WG" Mime-Version: 1.0 (Apple Message framework v1084) X-Mailer: Apple Mail (2.1084) Subject: [core] Draft minutes from CORE WG interim call on June 4 X-BeenThere: core@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Jun 2012 15:13:50 -0000 CoRE Virtual Interim 2012-06-04 People on call: Akbar, Angelo, Bert G, Carsten, Cullen, Dan Romascanu, Esko Dijk, Giri = Mandyam, Guido, Kepeng, Klaus, Matthias, Salvatore, Zach=20 * CoAP (59 min) #230 Multiple Location options need to be processed as a unit new = protocol defect minor - Proposed solution in Section 6 of coap-misc-17 Long discussion on trade off between places we put complexity. Two uses = brought up our location URI and grouping up set of options a proxy need = to understand.=20 Few people in favor of doing this, few people in favor of not doing it.=20= Bert made the point made to resist the urge to introduce new = functionality into the protocol that is only to deal with corner cases = that perhaps a constrained protocol just does not need to do. We don=92t = need to do every corner case.=20 Klaus: Made point that we can=92t add end to end options that don=92t = need to be understood by intermediaries.=20 Klaus: Other issue is that to process something like a Location part = options, you have to process all of them or none of them.=20 Proposal made to complete all the options we need to fully define an URI = so we don=92t have to add things later.=20 Proposal made that we have a rule that =93safe to forward without = understanding options=94 have a number of something like option number = mod 7 =3D 5. (of course more thought on 7 and 5 but you get the idea) Proposal made to complete all the options we need to fully define an URI = so we don=92t have to add things later.=20 Action going forward: Would not add envelope now - might add later.=20 In addition we allocate a few reserved number for use be later specs in = the URI that have to be understood. Could use for port, host, etc later.=20= Proposal made that we have a rule that =93safe to forward without = understanding options=94 have a number of something like option number = mod 7 =3D 5. (of course more thought on 7 and 5 but you get the idea) #201 Clarify use of retransmission window for duplicate detection new = editorial minor - Are we OK with Carsten's proposed solution in Section 7 of = coap-misc-17? People seemed ok with a MAX_TRANSMIT_WAIT of 93 seconds. The key use of the EXCHANGE_LIFETIME is that after that time you can = re-use a MSID=20 Zach proposed we just use that number for when to timeout both cases.=20 Point made that a large value will limit the speed and response of = system.=20 On previous call think number should be between 60 and 256 seconds. TCP = is 120 seconds? Kerry & Angelo pointed out - The larger we make this value, the more = state we need to keep.=20 Point made these calculations are different for confirmable and non = confirmable messages.=20 Matthias made point: If you have channel check time of 5 seconds and 20 = hops, you need a long time. Base draft does not need to deal with this - = it=92s a case where you will onfigure devices with different values than = default.=20 Carsten: this is trade off between points Kerry & Angelo made and = working in networks with larger latency Proposal for draft: We agree that range is 45 to 256 seconds. But the default should be - we = need to choose one of ( 45, 93, 120, 248, other ) Draft will have the guidance for implementers and not try to take on all = theory of how to pick this.=20 Draft will point out lower number for NON messages. #238 Proxy terminology new editorial minor - Zach proposes "translating proxy" Another proposal =93cross protocol proxy=94, =93translating proxy=94, = =93mapping proxy=94, =93coap-http proxy=94, =93cross proxy=94 Carsten made point like to know what it is translating.=20 Conclusion: Go with term =93cross proxy=94 #214 Adopt vendor-defined option into core-coap new protocol = enhancement minor - Cullen had some push-back on this in the last interim meeting. = Felt it was better to=20 make the registration more permissible instead. Needs more = discussion. =20 Carsten proposal: reserved a option number that first 2 bytes of data = is an code point that is allocated by IANA. reserver another options for = 3 bytes, 1 byte, etc. Need two sets of these numbers - one for critical = and one for elective.=20 Action: Carsten will write up in COAP misc.=20 #215 editorial issues around Congestion Control new editorial = major - Carsten has an open AP to propose changes in the ticket -- tickets with a clear solution (not planning to discuss) Action: Carsten is going to write up a proposal of text to fix this Main issue is what is the rules around when you can start another = discussion between two devices.=20 Carsten view is that HTTP has gone to you can have any number of = connections between two devices and it is a policy issue.=20 * Observe (59 min) -- check defined resolution and go ahead #204 Introduce a minimal version of Pledge new protocol = enhancement major - Max-Age is OK as is - Proposal for Pledge in Section 4.3 of coap-misc-17 A few key contributors are still working on this and will send out their = suggestion to list Real Soon Now.=20 Zach: Max Age seems pretty good - don=92t mess with it much. Also, = pledge is pretty good so tweak it but don=92t totally change.=20 Action: Klaus will write up proposal and put in misc.=20 #221 Occasionally sending CON is not just a security consideration = new protocol defect minor - Cullen proposed that we define a constant of at least once a = day for this. OK? =09 Point out this may be too often - for example sensors that wake up once = a week.=20 Point made many applications need to do it much more frequently.=20 Conclusion: People seemed OK with this. Move forward with this change.=20 #217 how fast must the observe clock be able to go? new protocol = enhancement major - Need to agree on how long a packet can be in the network = (conclusion from last interim meeting notes) Carsten: issue here is reordering - so one packet has latency 100 s and = next is 1 second.=20 Matthias: has to do with wrap around counter on observations.=20 One proposal to use variable length counters and never have them wrap - = just reset when the observation refreshes? Matthias has a proposal in email. Also issue of if one has a per device counter or per resource counter.=20= One issue with Matthias proposal is need quiet period to reset the = counter.=20 Plan moving forward: we need people to write up a few proposal and send = to list.=20 Please send as a reply to the ticket on the list by next monday.=20 Matthias send email to list=20 ------------- Dan R introduced COMA list. https://www.ietf.org/mailman/listinfo/coma Congrats to all on Link Format getting approved.=20 Next revision of CoAP out on June 12 - will get as much as we can in by = then but won=92t be everything. Will do another version of drafts close to IETF deadline (July 16) Carsten and Cullen to send email to list and consider another interim = meeting on June 27 From cabo@tzi.org Mon Jun 4 09:36:39 2012 Return-Path: X-Original-To: core@ietfa.amsl.com Delivered-To: core@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BD7D211E8087 for ; Mon, 4 Jun 2012 09:36:39 -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=[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 YPOiMFHVDbmg for ; Mon, 4 Jun 2012 09:36:39 -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 DC8AB11E8086 for ; Mon, 4 Jun 2012 09:36:38 -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.3/8.14.3) with ESMTP id q54GaVDI025833 for ; Mon, 4 Jun 2012 18:36:31 +0200 (CEST) Received: from [192.168.217.105] (p5489A354.dip.t-dialin.net [84.137.163.84]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id 79EF0E13; Mon, 4 Jun 2012 18:36:27 +0200 (CEST) From: Carsten Bormann Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Date: Mon, 4 Jun 2012 18:36:15 +0200 To: "core@ietf.org WG" Message-Id: <7A537315-D988-4EB7-B1DA-C200B4C2CE04@tzi.org> Mime-Version: 1.0 (Apple Message framework v1278) X-Mailer: Apple Mail (2.1278) Subject: [core] Next CoRE WG virtual interim: June 27, 1400Z? X-BeenThere: core@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Jun 2012 16:36:39 -0000 During today's CoRE virtual interim, we envisioned the following timing = from now: June 12: publish core-coap-10, which should cover the bulk of, but not = necessarily all, the WGLC comments (we didn't put dates on them, but I'd expect the other WGLC drafts to = follow within a week or so) June 27 1400Z..1600Z: have the next virtual interim (planning for 2 = hours right now) Around this meeting have another respin or two of the drafts July 16: publish core-coap-12? (by IETF-84 Internet Draft final = submission cut-off), with all comments handled July 30..August 3: meet in Vancouver In the call, nobody had a problem with the June 27 date. Please speak up if you do. Gr=FC=DFe, Carsten From barryleiba.mailing.lists@gmail.com Tue Jun 5 02:30:05 2012 Return-Path: X-Original-To: core@ietfa.amsl.com Delivered-To: core@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B5FBC21F8655 for ; Tue, 5 Jun 2012 02:30:05 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.99 X-Spam-Level: X-Spam-Status: No, score=-102.99 tagged_above=-999 required=5 tests=[AWL=-0.014, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, 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 mNfV0mbzXACw for ; Tue, 5 Jun 2012 02:30:04 -0700 (PDT) Received: from mail-lpp01m010-f44.google.com (mail-lpp01m010-f44.google.com [209.85.215.44]) by ietfa.amsl.com (Postfix) with ESMTP id 6116A21F8643 for ; Tue, 5 Jun 2012 02:30:04 -0700 (PDT) Received: by lagv3 with SMTP id v3so3961535lag.31 for ; Tue, 05 Jun 2012 02:30:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=5P9sBjQOoVeR5J1agPv17yckVEjmIYiyfHe4nPU1Osc=; b=RXXdVLGxbcI901GCTN26OtalZbe28ydOeDmyOmBMa8NRzoXRGttIlaMf9Sl4YQG3zm W5I191LFKZVWaYXBL/BYlBRwuSq93lNuq9pwDiqFFhj/icw+/sVYTJZVT1hlqeHol4Qa U9alwwQTrFWvsNPG9eqQ8GnFzXmudEVI4Gs5pQUcOLUzpDLskJx4RoYZnELuCVA+Xpoj 6UgA/Q7b+Hdi19DoDvlYVoy9yCyAV5BszuadlUuxLuRA0WqEYbURirbFDQvZ9vRKJVwD H/wSyTFnzkev9j9ZrSzCfqlyGSnCSsqgzQyqSYzMNXR5EZHPvBkoI+P/6kmPsVrvY9k6 XgSg== MIME-Version: 1.0 Received: by 10.152.103.11 with SMTP id fs11mr15919122lab.23.1338888603200; Tue, 05 Jun 2012 02:30:03 -0700 (PDT) Sender: barryleiba.mailing.lists@gmail.com Received: by 10.112.48.104 with HTTP; Tue, 5 Jun 2012 02:30:03 -0700 (PDT) In-Reply-To: <0E8162DB-0525-4A12-BAAD-9006CCE9539E@cisco.com> References: <0E8162DB-0525-4A12-BAAD-9006CCE9539E@cisco.com> Date: Tue, 5 Jun 2012 05:30:03 -0400 X-Google-Sender-Auth: ZGJzJRXtjntAqzxDrt8lOdhMYis Message-ID: From: Barry Leiba To: Cullen Jennings Content-Type: multipart/alternative; boundary=f46d040715c5966c1404c1b64bd8 Cc: "core@ietf.org WG" Subject: Re: [core] Draft minutes from CORE WG interim call on June 4 X-BeenThere: core@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Jun 2012 09:30:05 -0000 --f46d040715c5966c1404c1b64bd8 Content-Type: text/plain; charset=ISO-8859-1 Thanks very much for getting these posted tout de suite! Barry, whose AD job is easier when this happens --f46d040715c5966c1404c1b64bd8 Content-Type: text/html; charset=ISO-8859-1 Thanks very much for getting these posted tout de suite!

Barry, whose AD job is easier when this happens
--f46d040715c5966c1404c1b64bd8-- From fluffy@cisco.com Thu Jun 7 13:54:55 2012 Return-Path: X-Original-To: core@ietfa.amsl.com Delivered-To: core@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 14E1F11E8119 for ; Thu, 7 Jun 2012 13:54:55 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -110.599 X-Spam-Level: X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, 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 lZ5gW+-PP1o0 for ; Thu, 7 Jun 2012 13:54:54 -0700 (PDT) Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) by ietfa.amsl.com (Postfix) with ESMTP id 4AB6821F863B for ; Thu, 7 Jun 2012 13:54:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2184; q=dns/txt; s=iport; t=1339102491; x=1340312091; h=subject:mime-version:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to; bh=beSu80nA2UmYu8s40o/WuL+K7q/IY5o0H862SBW7i78=; b=etYmMyFwWYC8JmUhp8Ffg19reNbVdM53BMFwnlZRyaKCkTf2+TomUVt/ OyvgeZoE8eIfboORyKUhbKjxScya3zk7FeMsso8eneACQl5DFhnekdJ4E hkjG9/olJuaP0ELjIU1nGCck1akWsKPldKoMrcI3bmH0hGJeeaNTY0GY9 Q=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Av0EAOsT0U+tJXG//2dsb2JhbABFtE2BB4IZAQEEAQEBDwEURwsQC0YnMAYTIodpC5kun3GLHSSEfGADiECMXYEShEGFLoMTgWaDAA X-IronPort-AV: E=Sophos;i="4.75,732,1330905600"; d="scan'208";a="87533717" Received: from rcdn-core2-4.cisco.com ([173.37.113.191]) by rcdn-iport-9.cisco.com with ESMTP; 07 Jun 2012 20:54:51 +0000 Received: from [10.86.255.41] ([10.86.255.41]) by rcdn-core2-4.cisco.com (8.14.5/8.14.5) with ESMTP id q57Kskp3005184; Thu, 7 Jun 2012 20:54:47 GMT Mime-Version: 1.0 (Apple Message framework v1278) Content-Type: text/plain; charset=windows-1252 From: Cullen Jennings In-Reply-To: <051.9ec4e5813aa29f30a67cab16c3a9ea51@trac.tools.ietf.org> Date: Thu, 7 Jun 2012 11:09:31 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: References: <051.9ec4e5813aa29f30a67cab16c3a9ea51@trac.tools.ietf.org> To: core WG X-Mailer: Apple Mail (2.1278) Cc: trac+core@trac.tools.ietf.org Subject: Re: [core] #217: how fast must the observe clock be able to go? X-BeenThere: core@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Jun 2012 20:54:55 -0000 After the last call, I'd like to propose one of things we consider is = the following: 1) use a 3 byte id value - the application can set it however it wants = subject to the following constrains 2) each value must be larger than previous value modulo 2^24 ( it is = allowed to wrap )=20 3) value must not be re-used for at least 256 seconds after first use Note using a local clock in seconds or mili seconds would be fine. So = would an per resources counter.=20 First of all, does this sound like it would work? and second, pros / = cons vs other approaches? Cullen On Apr 19, 2012, at 11:50 , core issue tracker wrote: > #217: how fast must the observe clock be able to go? >=20 > Cullen Jennings notes (msg03073g): >=20 > Section 4.4 - I'm confused about the algorithm here. Does this mandate > that the resource can ever changes more than once per second ? For = many > applications I want way faster updates than this. I don't think this > works. >=20 > -> >=20 > The client-side algorithm is specified in 3.4. The current "MUST NOT > reuse" in 4.4 is very conservative, reflecting a very simple > implementation strategy. > We could come up with alternative, more elaborate server-side = requirements > that enable faster updates. > How fast is fast enough? How much are we willing to assume about > reordering and delivery probabilities (distributions, actually)? >=20 > --=20 > = ----------------------------------+---------------------------------------= > Reporter: cabo@=85 | Owner: = draft-ietf-core-observe@=85 > Type: protocol enhancement | Status: new > Priority: major | Milestone: post-WGLC-1 > Component: observe | Version: observe-05 > Severity: In WG Last Call | Keywords: > = ----------------------------------+---------------------------------------= >=20 > Ticket URL: > core >=20 > _______________________________________________ > core mailing list > core@ietf.org > https://www.ietf.org/mailman/listinfo/core From lishitao@huawei.com Fri Jun 8 00:59:43 2012 Return-Path: X-Original-To: core@ietfa.amsl.com Delivered-To: core@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 98EC821F88C0 for ; Fri, 8 Jun 2012 00:59:43 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.947 X-Spam-Level: X-Spam-Status: No, score=-4.947 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_53=0.6, J_CHICKENPOX_82=0.6, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4, SARE_SUB_ENC_UTF8=0.152] 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 kWpBqbwQC2MU for ; Fri, 8 Jun 2012 00:59:43 -0700 (PDT) Received: from dfwrgout.huawei.com (dfwrgout.huawei.com [206.16.17.72]) by ietfa.amsl.com (Postfix) with ESMTP id CFA2E21F88A7 for ; Fri, 8 Jun 2012 00:59:42 -0700 (PDT) Received: from 172.18.9.243 (EHLO dfweml201-edg.china.huawei.com) ([172.18.9.243]) by dfwrg01-dlp.huawei.com (MOS 4.2.3-GA FastPath) with ESMTP id AGY89143; Fri, 08 Jun 2012 03:59:42 -0400 (EDT) Received: from DFWEML407-HUB.china.huawei.com (10.193.5.132) by dfweml201-edg.china.huawei.com (172.18.9.107) with Microsoft SMTP Server (TLS) id 14.1.323.3; Fri, 8 Jun 2012 00:55:52 -0700 Received: from SZXEML410-HUB.china.huawei.com (10.82.67.137) by dfweml407-hub.china.huawei.com (10.193.5.132) with Microsoft SMTP Server (TLS) id 14.1.323.3; Fri, 8 Jun 2012 00:55:58 -0700 Received: from SZXEML534-MBX.china.huawei.com ([169.254.2.45]) by szxeml410-hub.china.huawei.com ([10.82.67.137]) with mapi id 14.01.0323.003; Fri, 8 Jun 2012 15:55:51 +0800 From: Lishitao To: core WG Thread-Topic: New Version Notification for draft-li-core-conditional-observe-02.txt Thread-Index: AQHNRUXVXaFJGsEn4kewi0Cd6BMa8JbwBQCQ Date: Fri, 8 Jun 2012 07:55:50 +0000 Message-ID: Accept-Language: zh-CN, en-US Content-Language: zh-CN X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.138.73.39] Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 MIME-Version: 1.0 X-CFilter-Loop: Reflected Subject: [core] =?utf-8?b?6L2s5Y+ROiBOZXcgVmVyc2lvbiBOb3RpZmljYXRpb24gZm9y?= =?utf-8?q?_draft-li-core-conditional-observe-02=2Etxt?= X-BeenThere: core@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Jun 2012 07:59:43 -0000 SGkgYWxsDQoNCkkgaGF2ZSBzdWJtaXR0ZWQgYSBuZXcgdmVyc2lvbiBvZiBkcmFmdC1saS1jb3Jl LWNvbmRpdGlvbmFsLW9ic2VydmUtMDIgZm9yIGNvbmRpdGlvbmFsIG9ic2VydmUuIA0KVGhlIHVy bCBjYW4gYmUgZmluZCBhdCBodHRwOi8vZGF0YXRyYWNrZXIuaWV0Zi5vcmcvZG9jL2RyYWZ0LWxp LWNvcmUtY29uZGl0aW9uYWwtb2JzZXJ2ZS8NCg0KVGhlIG1haW4gY2hhbmdlIGZvciB0aGlzIHZl cnNpb24gaXMgYWJvdXQgOg0KDQoxLCBjaGFuZ2luZyB0aGUgc3RydWN0dXJlIG9mIHRoZSBDb25k aXRpb24gb3B0aW9uLCBhZGRpbmcgdHdvIGZsYWcgaW4gdGhpcyBvcHRpb24sIG9uZSBmb3IgcmVs aWFiaWxpdHkgY29udHJvbCwgb25lIGZvciBpbmRpY2F0aW5nIHZhbHVlIHR5cGUNCg0KMiwgYWRk aW5nIG1vcmUgY29uZGl0aW9uIHR5cGVzDQoNCjMsIGluZGljYXRpbmcgYSBuZXcgbWVjaGFuaXNt IGZvciBjYW5jZWxsYXRpb24NCg0KNCwgaW50cm9kdWNpbmcgYSBuZXcgb3B0aW9uIGtlZXAtYWxp dmUsIHdoZW4gc2VydmVyIHVzaW5nIE5PTiBtZXNzYWdlIGZvciBub3RpZmljYXRpb24sIHRoZSBz ZXJ2ZXIgd2lsbCBub3Qga25vdyB3aGV0aGVyIHRoZSBjbGllbnQgaXMgc3RpbGwgYW4gb2JzZXJ2 ZXIoaW4gY2FzZSB0aGUgY2xpZW50IHN1ZmZlciBzb21lIHRyYWZmaWMgcHJvYmxlbSksIGFuZCBQ bGVkZ2Ugb3B0aW9uIGRlZmluZWQgaW4gYm9ybWFubi1jb2FwLW1pc2MgY2Fubm90IGhhbmRsZSB0 aGlzLCBzbyBhIG5ldyBrZWVwLWFsaXZlIG9wdGlvbiBpcyBzdWdnZXN0ZWQgZm9yIGEgY2xpZW50 IHRvIHVzZSBjYW4gbGV0IHRoZSBzZXJ2ZXIgdG8gY29uZmlybSB3aGV0aGVyIGl0IGlzIHN0aWxs IGFuIG9ic2VydmVyDQoNCjUsIGluIHRoZSBhbm5leCwgYWxzbyBzdWdnZXN0cyBzb21lIG90aGVy IG1lY2hhbmlzbXMgdGhhdCB3b3VsZCBiZSBoZWxwZnVsIGZvciBpbXBsZW1lbnRpbmcgQ09BUCwg b25lIGlzIHRoZSBjYW5jZWxsYXRpb24gZmxhZywgYW5vdGhlciBvbmUgaXMgbG9naWMgZmxhZy4g Q2FuY2VsbGF0aW9uIGZsYWcgaXMgYW5vdGhlciB3YXkgdGhhdCBjYW4gYmUgdXNlZCB0byByZW1v dmUgb25lIG9mIHRoZSBleGlzdGluZyBjb25kaXRpb24gZnJvbSB0aGUgb2JzZXJ2ZSByZWxhdGlv bnNoaXAuIExvZ2ljIGZsYWcgY2FuIGJlIHVzZWQgdG8gZGVmaW5lIHRoZSBsb2dpYyhBTkQgb3Ig T1IpIGJldHdlZW4gZGlmZmVyZW50IGNvbmRpdGlvbnMgdGhhdCBzaG93cyBpbiBvbmUgb2JzZXJ2 ZSByZXF1ZXN0LiBBbnlvbmUgaW50ZXJlc3RlZCBpbiB0aGlzIHBhcnRzIGNhbiBzZWUgdGhlIGRl dGFpbCBpbiB0aGUgZHJhZnQuIA0KDQpBbnkgY29tbWVudHMgYXJlIGhlbHBmdWwhIA0KDQpSZWdh cmRzDQpzaGl0YW8NCi0tLS0t6YKu5Lu25Y6f5Lu2LS0tLS0NCuWPkeS7tuS6ujogaW50ZXJuZXQt ZHJhZnRzQGlldGYub3JnIFttYWlsdG86aW50ZXJuZXQtZHJhZnRzQGlldGYub3JnXSANCuWPkemA geaXtumXtDogMjAxMuW5tDbmnIg45pelIDE1OjExDQrmlLbku7bkuro6IExpc2hpdGFvDQrmioTp gIE6IGplcm9lbi5ob2ViZWtlQGludGVjLnVnZW50LmJlOyBqYXJhQHVtLmVzDQrkuLvpopg6IE5l dyBWZXJzaW9uIE5vdGlmaWNhdGlvbiBmb3IgZHJhZnQtbGktY29yZS1jb25kaXRpb25hbC1vYnNl cnZlLTAyLnR4dA0KDQpBIG5ldyB2ZXJzaW9uIG9mIEktRCwgZHJhZnQtbGktY29yZS1jb25kaXRp b25hbC1vYnNlcnZlLTAyLnR4dCBoYXMgYmVlbiBzdWNjZXNzZnVsbHkgc3VibWl0dGVkIGJ5IFNo aXRhbyBMaSBhbmQgcG9zdGVkIHRvIHRoZSBJRVRGIHJlcG9zaXRvcnkuDQoNCkZpbGVuYW1lOgkg ZHJhZnQtbGktY29yZS1jb25kaXRpb25hbC1vYnNlcnZlDQpSZXZpc2lvbjoJIDAyDQpUaXRsZToJ CSBDb25kaXRpb25hbCBvYnNlcnZlIGluIENvQVANCkNyZWF0aW9uIGRhdGU6CSAyMDEyLTA2LTA4 DQpXRyBJRDoJCSBJbmRpdmlkdWFsIFN1Ym1pc3Npb24NCk51bWJlciBvZiBwYWdlczogMjMNCg0K QWJzdHJhY3Q6DQogICBDb0FQIGlzIGEgUkVTVGZ1bCBhcHBsaWNhdGlvbiBwcm90b2NvbCBmb3Ig Y29uc3RyYWluZWQgbm9kZXMgYW5kDQogICBuZXR3b3Jrcy4gIFRocm91Z2ggdGhlIE9ic2VydmUg b3B0aW9uLCBjbGllbnRzIGNhbiBvYnNlcnZlIGNoYW5nZXMgaW4NCiAgIHRoZSBzdGF0ZSBvZiBy ZXNvdXJjZXMgYW5kIG9idGFpbiBhIGN1cnJlbnQgcmVwcmVzZW50YXRpb24gb2YgdGhlDQogICBs YXN0IHJlc291cmNlIHN0YXRlLiAgVGhpcyBkb2N1bWVudCBkZWZpbmVzIGEgbmV3IG1lY2hhbmlz bSBpbiBDb0FQDQogICBPYnNlcnZlIHNvIHRoYXQgYSBDb0FQIGNsaWVudCBjYW4gY29uZGl0aW9u YWxseSBvYnNlcnZlIGEgcmVzb3VyY2Ugb24NCiAgIGEgQ29BUCBzZXJ2ZXIsIG9ubHkgYmVpbmcg aW5mb3JtZWQgYWJvdXQgc3RhdGUgY2hhbmdlcyBtZWV0aW5nIGENCiAgIHNwZWNpZmljIGNvbmRp dGlvbiBvciBzZXQgb2YgY29uZGl0aW9ucy4gIFRoaXMgb2ZmZXJzIHBvc3NpYmlsaXRpZXMNCiAg IHRvIGV4dGVuZCBuZXR3b3JrIGludGVsbGlnZW5jZSwgZW5oYW5jZSBzY2FsYWJpbGl0eSwgYW5k IG9wdGltaXplIHRoZQ0KICAgbGlmZXRpbWUgYW5kIHBlcmZvcm1hbmNlIGluIG9yZGVyIHRvIGFk ZHJlc3MgdGhlIHJlcXVpcmVtZW50cyBmcm9tDQogICB0aGUgQ29uc3RyYWluZWQgTm9kZXMgYW5k IE5ldHdvcmtzLg0KDQogICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgDQoNCg0KVGhlIElFVEYgU2Vj cmV0YXJpYXQNCg== From kovatsch@inf.ethz.ch Fri Jun 8 01:22:39 2012 Return-Path: X-Original-To: core@ietfa.amsl.com Delivered-To: core@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3F42821F8887 for ; Fri, 8 Jun 2012 01:22:39 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -10.599 X-Spam-Level: X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[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 KMLzz6ZIEao7 for ; Fri, 8 Jun 2012 01:22:38 -0700 (PDT) Received: from edge20.ethz.ch (edge20.ethz.ch [82.130.99.26]) by ietfa.amsl.com (Postfix) with ESMTP id D8A3621F8550 for ; Fri, 8 Jun 2012 01:22:33 -0700 (PDT) Received: from CAS20.d.ethz.ch (172.31.51.110) by edge20.ethz.ch (82.130.99.26) with Microsoft SMTP Server (TLS) id 14.2.298.4; Fri, 8 Jun 2012 10:22:32 +0200 Received: from MBX10.d.ethz.ch ([169.254.1.16]) by CAS20.d.ethz.ch ([fe80::2cd8:4907:7776:c56d%10]) with mapi id 14.02.0298.004; Fri, 8 Jun 2012 10:22:32 +0200 From: "Kovatsch Matthias" To: Cullen Jennings , core WG Thread-Topic: [core] #217: how fast must the observe clock be able to go? Thread-Index: AQHNRO/aqOh52/FKbkSmJ9rsHNwKipbwDOWg Date: Fri, 8 Jun 2012 08:22:31 +0000 Message-ID: <55877B3AFB359744BA0F2140E36F52B5139D2BDF@MBX10.d.ethz.ch> References: <051.9ec4e5813aa29f30a67cab16c3a9ea51@trac.tools.ietf.org> In-Reply-To: Accept-Language: en-US, de-CH Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [129.132.130.253] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: "trac+core@trac.tools.ietf.org" Subject: Re: [core] #217: how fast must the observe clock be able to go? X-BeenThere: core@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Jun 2012 08:22:39 -0000 This is the direction I was thinking. The variable length logical clock I had in mind (which would remove the rat= e limitation) turned out to be very complicated for deciding "larger than,"= though. So this is where my proposal is currently stuck or got a lot of me= ssy rules. With a fixed length it is much easier, I must admit. And 65kHz should be en= ough for resource changes... Are these 256s a constant of its own or will they be replaced with our MAX_= LATENCY (our equivalent to TCP's MSL) or at least derived from that value, = like 2*MAX_LATENCY? Would be nice not to have too many constants of that kind... Ciao Matthias > -----Original Message----- > From: core-bounces@ietf.org [mailto:core-bounces@ietf.org] On Behalf Of > Cullen Jennings > Sent: Donnerstag, 7. Juni 2012 20:10 > To: core WG > Cc: trac+core@trac.tools.ietf.org > Subject: Re: [core] #217: how fast must the observe clock be able to go? >=20 >=20 > After the last call, I'd like to propose one of things we consider is the > following: >=20 > 1) use a 3 byte id value - the application can set it however it wants s= ubject > to the following constrains >=20 > 2) each value must be larger than previous value modulo 2^24 ( it is allo= wed > to wrap ) >=20 > 3) value must not be re-used for at least 256 seconds after first use >=20 > Note using a local clock in seconds or mili seconds would be fine. So wou= ld an > per resources counter. >=20 > First of all, does this sound like it would work? and second, pros / cons= vs > other approaches? >=20 > Cullen >=20 >=20 >=20 >=20 > On Apr 19, 2012, at 11:50 , core issue tracker wrote: >=20 > > #217: how fast must the observe clock be able to go? > > > > Cullen Jennings notes (msg03073g): > > > > Section 4.4 - I'm confused about the algorithm here. Does this mandate > > that the resource can ever changes more than once per second ? For > > many applications I want way faster updates than this. I don't think > > this works. > > > > -> > > > > The client-side algorithm is specified in 3.4. The current "MUST NOT > > reuse" in 4.4 is very conservative, reflecting a very simple > > implementation strategy. > > We could come up with alternative, more elaborate server-side > > requirements that enable faster updates. > > How fast is fast enough? How much are we willing to assume about > > reordering and delivery probabilities (distributions, actually)? > > > > -- > > ----------------------------------+----------------------------------- > > ----------------------------------+---- > > Reporter: cabo@... | Owner: draft-ietf-core-obser= ve@... > > Type: protocol enhancement | Status: new > > Priority: major | Milestone: post-WGLC-1 > > Component: observe | Version: observe-05 > > Severity: In WG Last Call | Keywords: > > ----------------------------------+----------------------------------- > > ----------------------------------+---- > > > > Ticket URL: > > core > > > > _______________________________________________ > > core mailing list > > core@ietf.org > > https://www.ietf.org/mailman/listinfo/core >=20 > _______________________________________________ > core mailing list > core@ietf.org > https://www.ietf.org/mailman/listinfo/core From kovatsch@inf.ethz.ch Fri Jun 8 01:29:20 2012 Return-Path: X-Original-To: core@ietfa.amsl.com Delivered-To: core@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 064ED21F88EC for ; Fri, 8 Jun 2012 01:29:20 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -10.599 X-Spam-Level: X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[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 BLU5CsKpaxeB for ; Fri, 8 Jun 2012 01:29:19 -0700 (PDT) Received: from edge20.ethz.ch (edge20.ethz.ch [82.130.99.26]) by ietfa.amsl.com (Postfix) with ESMTP id 00A0A21F88A0 for ; Fri, 8 Jun 2012 01:29:18 -0700 (PDT) Received: from CAS20.d.ethz.ch (172.31.51.110) by edge20.ethz.ch (82.130.99.26) with Microsoft SMTP Server (TLS) id 14.2.298.4; Fri, 8 Jun 2012 10:29:17 +0200 Received: from MBX10.d.ethz.ch ([169.254.1.16]) by CAS20.d.ethz.ch ([fe80::2cd8:4907:7776:c56d%10]) with mapi id 14.02.0298.004; Fri, 8 Jun 2012 10:29:17 +0200 From: "Kovatsch Matthias" To: Cullen Jennings , core WG Thread-Topic: [core] #217: how fast must the observe clock be able to go? Thread-Index: AQHNRO/aqOh52/FKbkSmJ9rsHNwKipbwDOWggAAKqSA= Date: Fri, 8 Jun 2012 08:29:16 +0000 Message-ID: <55877B3AFB359744BA0F2140E36F52B5139D2C0A@MBX10.d.ethz.ch> References: <051.9ec4e5813aa29f30a67cab16c3a9ea51@trac.tools.ietf.org> <55877B3AFB359744BA0F2140E36F52B5139D2BDF@MBX10.d.ethz.ch> In-Reply-To: <55877B3AFB359744BA0F2140E36F52B5139D2BDF@MBX10.d.ethz.ch> Accept-Language: en-US, de-CH Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [129.132.130.253] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: "trac+core@trac.tools.ietf.org" Subject: Re: [core] #217: how fast must the observe clock be able to go? X-BeenThere: core@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Jun 2012 08:29:20 -0000 > Are these 256s a constant of its own or will they be replaced with our > MAX_LATENCY (our equivalent to TCP's MSL) or at least derived from that > value, like 2*MAX_LATENCY? > Would be nice not to have too many constants of that kind... Okay, I got confused with all these MSL-like values. I am talking about thi= s value between 45 and 256 seconds, which is considered a safe time to reus= e a sequence number. We definitely must clean this up! From wehner@htw-dresden.de Fri Jun 8 01:54:39 2012 Return-Path: X-Original-To: core@ietfa.amsl.com Delivered-To: core@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 38FCA21F88EE for ; Fri, 8 Jun 2012 01:54:39 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.249 X-Spam-Level: X-Spam-Status: No, score=-2.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35] 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 MEHMK5lnGdxk for ; Fri, 8 Jun 2012 01:54:38 -0700 (PDT) Received: from rmr1.rz.htw-dresden.de (rmr1.rz.htw-dresden.de [141.56.16.131]) by ietfa.amsl.com (Postfix) with ESMTP id 0020621F8889 for ; Fri, 8 Jun 2012 01:54:37 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by rmr1.rz.htw-dresden.de (Postfix) with ESMTP id A1B1C1016E; Fri, 8 Jun 2012 10:54:36 +0200 (CEST) X-HTW-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on rmr1.rz.htw-dresden.de X-HTW-Virus-Scanned: Debian amavisd-new at rmr1.rz.htw-dresden.de Received: from rmr1.rz.htw-dresden.de ([127.0.0.1]) by localhost (rmr1.rz.htw-dresden.de [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RVMLKa5FnzZk; Fri, 8 Jun 2012 10:54:30 +0200 (CEST) Received: from rlux45.rz.htw-dresden.de (rlux45.rz.htw-dresden.de [141.56.16.45]) by rmr1.rz.htw-dresden.de (Postfix) with ESMTP id 3BC6710166; Fri, 8 Jun 2012 10:54:30 +0200 (CEST) Received: from [141.56.111.34] (etpc34.et.htw-dresden.de [141.56.111.34]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by rlux45.rz.htw-dresden.de (Postfix) with ESMTPSA id 388F02200F; Fri, 8 Jun 2012 10:54:30 +0200 (CEST) Message-ID: <4FD1BDC7.5060203@htw-dresden.de> Date: Fri, 08 Jun 2012 10:54:31 +0200 From: Markus Wehner User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:13.0) Gecko/20120604 Thunderbird/13.0 MIME-Version: 1.0 To: sye.loong.keoh@philips.com References: <20120326215140.20793.73440.idtracker@ietfa.amsl.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: core@ietf.org Subject: Re: [core] New Version Notification for draft-garcia-core-security-04.txt X-BeenThere: core@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Jun 2012 08:54:39 -0000 Dear Sye, I like this document, it is written well and very clear. Some comments from my side regarding the draft: 1. Difficulties with E2E security not only occur for protocol translation but also for aggregation (or in-network processing in general) of data. Especially in industrial scenarios, aggregation of huge amounts of data may be performed at dedicated intermediate aggregating devices and sent to the application afterwards for efficiency reasons. Also in a home environment it is a privacy reason that for example not any single device can be monitored by a certain user (end user, power supplier) but aggregated information is needed. Here, besides the solutions you mentioned for protocol translation, also homomorphic encryption may play a role which allows performing aggregation on encrypted payload on the cost of computational complexity. 2. Multi owner (resp. multi domain) use cases also raise security issues in the IoT world, i.e. data separation, resources sharing and in this scope trustworthiness, fairness, QoS restrictions... . Co-located networks that do not belong to the same domain which work in a cooperative way, i.e. for routing/energy efficiency, are part of that. Also, if a mobile node moves between different networks, besides reauthentication and so on, the trustworthiness is an important thing to consider here. 3. Especially in IoT world, nodes often know about their context which could enhance security. For example a network which knows locations of its nodes and is able to measure them could improve against physical replacement. The other way, only nodes within a certain area, i.e. an office room, could be allowed to have access to the rest of the network (automatically). Unfortunately this raises new security issues. Best regards, Markus ----- Original Message ----- From: Keoh, Sye Loong Sent: Mon, 26 Mar 2012 22:08:38 +0000 To: core@ietf.org Cc: Subject: [core] New Version Notification for draft-garcia-core-security-04.txt --- Original Nachricht --- Absender: Keoh, Sye Loong Datum: 27.03.2012 00:08 > Dear all, > > In this new version, we have updated the conclusions section to reflect the status of current security technologies and the missing bits with regards to the security requirements we identified in the document. > > Since the WG advised that we should continue working on this draft in Taipei, we are continuously improving the draft so that it serves its purpose to provide an overview of the security requirements for IoT. Therefore, we would greatly appreciate feedback and comments from WG members on this document. > > Many thanks > Sye Loong > > -----Original Message----- > From:internet-drafts@ietf.org [mailto:internet-drafts@ietf.org] > Sent: maandag 26 maart 2012 23:52 > To: Keoh, Sye Loong > Cc:rstruik.ext@gmail.com; Kumar, Sandeep;rene.hummen@cs.rwth-aachen.de; Garcia Morchon, Oscar > Subject: New Version Notification for draft-garcia-core-security-04.txt > > A new version of I-D, draft-garcia-core-security-04.txt has been successfully submitted by Sye Loong Keoh and posted to the IETF repository. > > Filename: draft-garcia-core-security > Revision: 04 > Title: Security Considerations in the IP-based Internet of Things > Creation date: 2012-03-26 > WG ID: Individual Submission > Number of pages: 45 > > Abstract: > A direct interpretation of the Internet of Things concept refers to > the usage of standard Internet protocols to allow for human-to-thing > or thing-to-thing communication. Although the security needs are > well-recognized, it is still not fully clear how existing IP-based > security protocols can be applied to this new setting. This > Internet-Draft first provides an overview of security architecture, > its deployment model and general security needs in the context of the > lifecycle of a thing. Then, it presents challenges and requirements > for the successful roll-out of new applications and usage of standard > IP-based security protocols when applied to get a functional Internet > of Things. > > > > > The IETF Secretariat > > ________________________________ > The information contained in this message may be confidential and legally protected under applicable law. The message is intended solely for the addressee(s). If you are not the intended recipient, you are hereby notified that any use, forwarding, dissemination, or reproduction of this message is strictly prohibited and may be unlawful. If you are not the intended recipient, please contact the sender by return e-mail and destroy all copies of the original message. > _______________________________________________ > core mailing list > core@ietf.org > https://www.ietf.org/mailman/listinfo/core > -- --------------------------------------- Dipl.-Ing. Markus Wehner on behalf of TWISNet project University of Applied Sciences Department of Electrical Engineering Friedrich-List-Platz 1 D-01069 Dresden Germany http://www.htw-dresden.de phone : +49 351 462 2465 email :wehner@htw-dresden.de --------------------------------------- From kovatsch@inf.ethz.ch Fri Jun 8 02:17:00 2012 Return-Path: X-Original-To: core@ietfa.amsl.com Delivered-To: core@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1858321F889A for ; Fri, 8 Jun 2012 02:17:00 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.599 X-Spam-Level: X-Spam-Status: No, score=-8.599 tagged_above=-999 required=5 tests=[AWL=-2.000, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4] 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 qQ5NpIvSvhPV for ; Fri, 8 Jun 2012 02:16:59 -0700 (PDT) Received: from edge10.ethz.ch (edge10.ethz.ch [82.130.75.186]) by ietfa.amsl.com (Postfix) with ESMTP id E830F21F8685 for ; Fri, 8 Jun 2012 02:16:56 -0700 (PDT) Received: from CAS10.d.ethz.ch (172.31.38.210) by edge10.ethz.ch (82.130.75.186) with Microsoft SMTP Server (TLS) id 14.2.298.4; Fri, 8 Jun 2012 11:16:53 +0200 Received: from MBX10.d.ethz.ch ([169.254.1.16]) by CAS10.d.ethz.ch ([fe80::cce:fc66:7b56:a06a%10]) with mapi id 14.02.0298.004; Fri, 8 Jun 2012 11:16:55 +0200 From: "Kovatsch Matthias" To: "trac+core@trac.tools.ietf.org" , "draft-ietf-core-coap@tools.ietf.org" , "cabo@tzi.org" , "angelo@castellani.net" Thread-Topic: [core] #201: Clarify use of retransmission window for duplicate detection Thread-Index: AQHNDM5pJ8w+Z4q9HU2NL94rOGxR+pbqdSUAgAYTBtA= Date: Fri, 8 Jun 2012 09:16:54 +0000 Message-ID: <55877B3AFB359744BA0F2140E36F52B5139D2C5B@MBX10.d.ethz.ch> References: <051.b90ea2a4caf57d34ab6abdaf3603301a@trac.tools.ietf.org> <066.6904c04e7cd121d92730aedcf9ab88bd@trac.tools.ietf.org> In-Reply-To: <066.6904c04e7cd121d92730aedcf9ab88bd@trac.tools.ietf.org> Accept-Language: en-US, de-CH Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [129.132.130.253] Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 MIME-Version: 1.0 Cc: "core@ietf.org" Subject: Re: [core] #201: Clarify use of retransmission window for duplicate detection X-BeenThere: core@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Jun 2012 09:17:00 -0000 SGF2aW5nIGEgbG9vayBhdCB0aGUgIERUTFMgMS4yIFJGQywgSSBzYXcgdGhhdCB0aGV5IHVzZSBU Q1AncyAxMjAgc2Vjb25kcyBhcyBjb25zdGFudCBmb3IgcmV1c2luZyB0aGUgZXBvY2ggdmFsdWUu DQpXb3VsZCBpdCBtYWtlIHNlbnNlIHRvIGhhcm1vbml6ZSBvdXIgIklEIGxpZmV0aW1lIHZhbHVl IiB3aXRoIHRoaXMsIGFzIERUTFMgaXMgZXhwZWN0ZWQgdG8gYmUgdXNlZCBhIGxvdCB0b2dldGhl ciB3aXRoIENvQVA/DQoNCkhhdmluZyB0aG91Z2h0IG1vcmUgYWJvdXQgdGhpcyBJRCByZXVzZSBp c3N1ZSwgSSBhbHNvIHRoaW5rIENhcnN0ZW4ncyBjYWxjdWxhdGlvbiBpcyBhIGdvb2QgZXN0aW1h dGlvbiBmb3IgYW4gdXBwZXIgYm91bmQ6DQoNCglNQVhfUkVUUkFOU01JVF9TUEFOICsgUFJPQ0VT U0lOR19ERUxBWSArICgyICogTUFYX0xBVEVOQ1kpCSg9IDI0OHMpDQoNCkJ1dCBJTUhPLCBNQVhf UkVUUkFOU01JVF9TUEFOIGFuZCBNQVhfTEFURU5DWSBhcmUgY29ycmVsYXRlZCBhbmQgaGF2aW5n IGRpZmZlcmVudCB2YWx1ZXMgZm9yIENPTnMsIE5PTnMsIGFuZCBhbHNvIHRoZSBvYnNlcnZlIGNs b2NrIG1ha2VzIHRoaXMgbW9yZSBjb21wbGljYXRlZCB0aGFuIGl0IGlzLg0KDQpUaHVzLCBteSB2 b3RlIGlzIGZvciAxMjAgc2Vjb25kcyB0byBzaW1wbGlmeSBhbmQgaGFybW9uaXplIHdpdGggRFRM Uy4NCkEgY2xpZW50IGdpdmVzIHVwIGFmdGVyIDkzcyAoZHVlIHRvIDQgcmV0cmFuc21pc3Npb24g YW5kIGFuIGV4cG9uZW50aWFsIHRpbWVvdXQpLiBTbyB3ZSBkbyBub3QgZXhwZWN0IGFueSBtZXNz YWdlIHdpdGggdGhlIHVzZWQgSUQgYWZ0ZXIgdGhpcyB0aW1lc3Bhbi4gQWRkaXRpb25hbCAyN3Mg bWFrZSBhIGdvb2QsIHF1aXRlIGNvbnNlcnZhdGl2ZSBzYWZldHkgbWFyZ2luIGZvciAic3RyYW5n ZSBlZmZlY3RzIiBpbiBhIG11bHRpLWhvcCBsb3ctcG93ZXIgbmV0d29yay4NCg0KQmVzdCByZWdh cmRzDQpNYXR0aGlhcw0KDQo= From cabo@tzi.org Fri Jun 8 04:19:20 2012 Return-Path: X-Original-To: core@ietfa.amsl.com Delivered-To: core@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 94D6021F889A for ; Fri, 8 Jun 2012 04:19: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 uwU4PycPS7dm for ; Fri, 8 Jun 2012 04:19:20 -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 CACA721F8873 for ; Fri, 8 Jun 2012 04:19:19 -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.3/8.14.3) with ESMTP id q58BIrSn005098; Fri, 8 Jun 2012 13:18:53 +0200 (CEST) Received: from [192.168.217.117] (p548995C0.dip.t-dialin.net [84.137.149.192]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id 4BA755DC; Fri, 8 Jun 2012 13:18:45 +0200 (CEST) Mime-Version: 1.0 (Apple Message framework v1278) Content-Type: text/plain; charset=iso-8859-1 From: Carsten Bormann In-Reply-To: <55877B3AFB359744BA0F2140E36F52B5139D2C5B@MBX10.d.ethz.ch> Date: Fri, 8 Jun 2012 13:18:35 +0200 Content-Transfer-Encoding: quoted-printable Message-Id: References: <051.b90ea2a4caf57d34ab6abdaf3603301a@trac.tools.ietf.org> <066.6904c04e7cd121d92730aedcf9ab88bd@trac.tools.ietf.org> <55877B3AFB359744BA0F2140E36F52B5139D2C5B@MBX10.d.ethz.ch> To: "Kovatsch Matthias" X-Mailer: Apple Mail (2.1278) Cc: "draft-ietf-core-coap@tools.ietf.org" , "trac+core@trac.tools.ietf.org" , "core@ietf.org" Subject: Re: [core] #201: Clarify use of retransmission window for duplicate detection X-BeenThere: core@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Jun 2012 11:19:20 -0000 On Jun 8, 2012, at 11:16, Kovatsch Matthias wrote: > DTLS 1.2 RFC, I saw that they use TCP's 120 seconds RFC 6347, 4.1 (p. 9): ...MAY choose to retain keying material from previous epochs for up to the default MSL specified for TCP [TCP] to allow for packet reordering This is the maximum expected reordering, i.e. something that would apply = to our NON usage, not a CON situation -- the value equivalent to our = MAX_LATENCY. It also is about the time when state is discarded the lack = of which simply causes a protocol operation to detectably fail, as = opposed to the protocol potentially acting confused. So I think this is good input for our choice of MAX_LATENCY (another = argument for choosing 120 s instead of the 100 s I proposed). It is not = helping us to decide when MID-related state can be discarded for CON = exchanges. I still think that the text in coap-misc-17 here is correct. = We just need to add a discussion of NON state lifetime, and that will = be closer to the DTLS discussion. Gr=FC=DFe, Carsten PS.: The language (that is, in so many words, circuitously trying to = avoid spelling out the "120 s" that it simply means) suggests to me that = choosing this value was a struggle when DTLS was defined, too. Note also the text: In addition, for at least twice the default MSL defined for [TCP], when in the FINISHED state, the node that transmits the last flight (the server in an ordinary handshake or the client in a resumed handshake) MUST respond to a retransmit of the peer's last flight Rescorla & Modadugu Standards Track [Page 23] RFC 6347 DTLS January 2012 with a retransmit of the last flight. This avoids deadlock conditions if the last flight gets lost. which is closer to our CON considerations. So this MUST here would be = 2*MAX_LATENCY, but without an allowance for MAX_TRANSMIT_SPAN. From fluffy@cisco.com Fri Jun 8 04:46:56 2012 Return-Path: X-Original-To: core@ietfa.amsl.com Delivered-To: core@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 95A6321F88FC for ; Fri, 8 Jun 2012 04:46:56 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -110.599 X-Spam-Level: X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, 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 XqV8jNWvORs3 for ; Fri, 8 Jun 2012 04:46:56 -0700 (PDT) Received: from rcdn-iport-5.cisco.com (rcdn-iport-5.cisco.com [173.37.86.76]) by ietfa.amsl.com (Postfix) with ESMTP id BDFBE21F87C6 for ; Fri, 8 Jun 2012 04:46:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=fluffy@cisco.com; l=645; q=dns/txt; s=iport; t=1339156003; x=1340365603; h=subject:mime-version:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to; bh=+UE6E6YHtP/XHWzUyzSvM/4h3rHxClM7ZlO/n4UuF7I=; b=jV+a14CWIm6vIa9NcrxGPHNskxS0YR5wsaKcOa0T1SSIRR+CIxvRAA6I 5hAGYgCIrCDOue6m+ojGRWKzgdhTA1NEqs5lBCnBhxsvuGTQPK/FwiVEn LIEa9cr8R1V4Si2VZ5Jx5Iz0hifxBLh1J5JdNXFm+gQO/nuScsaBDFFyO I=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Av0EAPLk0U+tJXHB/2dsb2JhbABFtE6BB4IYAQEBAwESAWYQC0ZXBjWHZAWZK59ziyaFIGADlR6FU4hCgWaCfA X-IronPort-AV: E=Sophos;i="4.75,737,1330905600"; d="scan'208";a="90707129" Received: from rcdn-core2-6.cisco.com ([173.37.113.193]) by rcdn-iport-5.cisco.com with ESMTP; 08 Jun 2012 11:46:43 +0000 Received: from [10.86.244.114] ([10.86.244.114]) by rcdn-core2-6.cisco.com (8.14.5/8.14.5) with ESMTP id q58BkgiS017273; Fri, 8 Jun 2012 11:46:42 GMT Mime-Version: 1.0 (Apple Message framework v1278) Content-Type: text/plain; charset=iso-8859-1 From: Cullen Jennings In-Reply-To: <55877B3AFB359744BA0F2140E36F52B5139D2C0A@MBX10.d.ethz.ch> Date: Fri, 8 Jun 2012 07:46:42 -0400 Content-Transfer-Encoding: quoted-printable Message-Id: References: <051.9ec4e5813aa29f30a67cab16c3a9ea51@trac.tools.ietf.org> <55877B3AFB359744BA0F2140E36F52B5139D2BDF@MBX10.d.ethz.ch> <55877B3AFB359744BA0F2140E36F52B5139D2C0A@MBX10.d.ethz.ch> To: "Kovatsch Matthias" X-Mailer: Apple Mail (2.1278) Cc: trac+core@trac.tools.ietf.org, core WG Subject: Re: [core] #217: how fast must the observe clock be able to go? X-BeenThere: core@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Jun 2012 11:46:56 -0000 On Jun 8, 2012, at 4:29 , Kovatsch Matthias wrote: > > Are these 256s a constant of its own or will they be replaced with = our > > MAX_LATENCY (our equivalent to TCP's MSL) or at least derived from = that > > value, like 2*MAX_LATENCY? > > Would be nice not to have too many constants of that kind... >=20 > Okay, I got confused with all these MSL-like values. I am talking = about this value between 45 and 256 seconds, which is considered a safe = time to reuse a sequence number. > We definitely must clean this up! >=20 >=20 +1 - yah, I think you are right, it needs to be that number, whatever it = is we call it :-) From trac+core@trac.tools.ietf.org Mon Jun 11 01:08:27 2012 Return-Path: X-Original-To: core@ietfa.amsl.com Delivered-To: core@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A189121F850C for ; Mon, 11 Jun 2012 01:08:27 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -99.91 X-Spam-Level: X-Spam-Status: No, score=-99.91 tagged_above=-999 required=5 tests=[BAYES_05=-1.11, J_CHICKENPOX_63=0.6, J_CHICKENPOX_66=0.6, 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 fzaspxT8THMW for ; Mon, 11 Jun 2012 01:08:27 -0700 (PDT) Received: from grenache.tools.ietf.org (grenache.tools.ietf.org [77.72.230.30]) by ietfa.amsl.com (Postfix) with ESMTP id 15C9321F8443 for ; Mon, 11 Jun 2012 01:08:27 -0700 (PDT) Received: from localhost ([127.0.0.1]:51203 helo=grenache.tools.ietf.org ident=www-data) by grenache.tools.ietf.org with esmtp (Exim 4.77) (envelope-from ) id 1Sdzfb-0005Dg-56; Mon, 11 Jun 2012 10:08:15 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit From: "core issue tracker" X-Trac-Version: 0.12.2 Precedence: bulk Auto-Submitted: auto-generated X-Mailer: Trac 0.12.2, by Edgewall Software To: zach@sensinode.com X-Trac-Project: core Date: Mon, 11 Jun 2012 08:08:15 -0000 X-URL: http://tools.ietf.org/core/ X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/core/trac/ticket/241 Message-ID: <057.c44e32d1c6663d3d7f4c960815a6fce2@trac.tools.ietf.org> X-Trac-Ticket-ID: 241 X-SA-Exim-Connect-IP: 127.0.0.1 X-SA-Exim-Rcpt-To: zach@sensinode.com, core@ietf.org X-SA-Exim-Mail-From: trac+core@trac.tools.ietf.org X-SA-Exim-Scanned: No (on grenache.tools.ietf.org); SAEximRunCond expanded to false Cc: core@ietf.org Subject: [core] #241: Proxy safe to forward options X-BeenThere: core@ietf.org X-Mailman-Version: 2.1.12 Reply-To: trac+core@trac.tools.ietf.org List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Jun 2012 08:08:27 -0000 #241: Proxy safe to forward options #choose ticket.new #when True As a conclusion to the Ticket #230 discussion in the June 4th interim call, we decided to solve the identification of options that a proxy can safely forward even if not understood. Proposal made that we have a rule that “safe to forward without understanding options” have a number of something like option number mod 7 = 5. (of course more thought on 7 and 5 but you get the idea) #end #otherwise #if changes_body Changes (by ): #end #if changes_descr #if not changes_body and not change.comment and change.author Description changed by : #end -- #end #if change.comment Comment(by undefined): #end #end #end -- ----------------------------------+-------------------- Reporter: zach@… | Owner: zach@… Type: protocol enhancement | Status: new Priority: minor | Milestone: Component: coap | Version: Severity: - | Keywords: ----------------------------------+-------------------- Ticket URL: core From trac+core@trac.tools.ietf.org Mon Jun 11 01:09:22 2012 Return-Path: X-Original-To: core@ietfa.amsl.com Delivered-To: core@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5B3DD21F850C for ; Mon, 11 Jun 2012 01:09:22 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -99.448 X-Spam-Level: X-Spam-Status: No, score=-99.448 tagged_above=-999 required=5 tests=[AWL=-0.462, BAYES_40=-0.185, J_CHICKENPOX_63=0.6, J_CHICKENPOX_66=0.6, 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 d12ZZFB++Qt2 for ; Mon, 11 Jun 2012 01:09:22 -0700 (PDT) Received: from grenache.tools.ietf.org (grenache.tools.ietf.org [77.72.230.30]) by ietfa.amsl.com (Postfix) with ESMTP id C5EF621F8443 for ; Mon, 11 Jun 2012 01:09:21 -0700 (PDT) Received: from localhost ([127.0.0.1]:51227 helo=grenache.tools.ietf.org ident=www-data) by grenache.tools.ietf.org with esmtp (Exim 4.77) (envelope-from ) id 1SdzgY-0000F1-Dk; Mon, 11 Jun 2012 10:09:14 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit From: "core issue tracker" X-Trac-Version: 0.12.2 Precedence: bulk Auto-Submitted: auto-generated X-Mailer: Trac 0.12.2, by Edgewall Software To: draft-ietf-core-coap@tools.ietf.org, cabo@tzi.org, zach@sensinode.com, fluffy@cisco.com X-Trac-Project: core Date: Mon, 11 Jun 2012 08:09:14 -0000 X-URL: http://tools.ietf.org/core/ X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/core/trac/ticket/230#comment:4 Message-ID: <068.9b74137ffcb0012c155a1f15dc2b45c3@trac.tools.ietf.org> References: <053.8673136dcb3a579ebc337cc52e97888a@trac.tools.ietf.org> X-Trac-Ticket-ID: 230 In-Reply-To: <053.8673136dcb3a579ebc337cc52e97888a@trac.tools.ietf.org> X-SA-Exim-Connect-IP: 127.0.0.1 X-SA-Exim-Rcpt-To: draft-ietf-core-coap@tools.ietf.org, cabo@tzi.org, zach@sensinode.com, fluffy@cisco.com, core@ietf.org X-SA-Exim-Mail-From: trac+core@trac.tools.ietf.org X-SA-Exim-Scanned: No (on grenache.tools.ietf.org); SAEximRunCond expanded to false Resent-To: Resent-Message-Id: <20120611080921.C5EF621F8443@ietfa.amsl.com> Resent-Date: Mon, 11 Jun 2012 01:09:21 -0700 (PDT) Resent-From: trac+core@trac.tools.ietf.org Cc: core@ietf.org Subject: Re: [core] #230: Multiple Location options need to be processed as a unit X-BeenThere: core@ietf.org X-Mailman-Version: 2.1.12 Reply-To: trac+core@trac.tools.ietf.org List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Jun 2012 08:09:22 -0000 #230: Multiple Location options need to be processed as a unit #choose ticket.new #when True Before the location in a response was split into multiple options, there was only one Location Option which was defined to be "elective". This worked well, because a client that doesn't recognize the option could ignore it without harm. However, with the Location-Path and Location-Query options (and possible future Location-Host and Location-Port options), the client must either understand or ignore all of them. Expressing such interdependencies is currently not possible in CoAP. -> Solution to be defined. Focus on the problem right now. (One solution would be to use an envelope "Location" option to contain all Location-* options, so they are ignored or used as a whole. Reserve space in the envelope option so possible future Location-Host and Location-Port options appear before Location-Path and Location-Query options in a message.) #end #otherwise #if changes_body Changes (by zach@…): #end #if changes_descr #if not changes_body and not change.comment and change.author Description changed by zach@…: #end -- #end #if change.comment Comment(by zach@…): The proxy forwarding issue now has its own ticket: http://tools.ietf.org/wg/core/trac/ticket/241 #end #end #end -- -----------------------------+------------------------------------- Reporter: hartke@… | Owner: draft-ietf-core-coap@… Type: protocol defect | Status: new Priority: minor | Milestone: post-WGLC-1 Component: coap | Version: coap-09 Severity: In WG Last Call | Resolution: Keywords: | -----------------------------+------------------------------------- Ticket URL: core From trac+core@trac.tools.ietf.org Mon Jun 11 01:55:43 2012 Return-Path: X-Original-To: core@ietfa.amsl.com Delivered-To: core@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1068621F850B for ; Mon, 11 Jun 2012 01:55:43 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -99.494 X-Spam-Level: X-Spam-Status: No, score=-99.494 tagged_above=-999 required=5 tests=[AWL=0.046, BAYES_20=-0.74, J_CHICKENPOX_63=0.6, J_CHICKENPOX_66=0.6, 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 1gZIdJEY+Vqt for ; Mon, 11 Jun 2012 01:55:42 -0700 (PDT) Received: from grenache.tools.ietf.org (grenache.tools.ietf.org [77.72.230.30]) by ietfa.amsl.com (Postfix) with ESMTP id 7B44021F8505 for ; Mon, 11 Jun 2012 01:55:42 -0700 (PDT) Received: from localhost ([127.0.0.1]:53827 helo=grenache.tools.ietf.org ident=www-data) by grenache.tools.ietf.org with esmtp (Exim 4.77) (envelope-from ) id 1Se0PK-0007Cb-Tm; Mon, 11 Jun 2012 10:55:30 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit From: "core issue tracker" X-Trac-Version: 0.12.2 Precedence: bulk Auto-Submitted: auto-generated X-Mailer: Trac 0.12.2, by Edgewall Software To: zach@sensinode.com X-Trac-Project: core Date: Mon, 11 Jun 2012 08:55:30 -0000 X-URL: http://tools.ietf.org/core/ X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/core/trac/ticket/241#comment:1 Message-ID: <072.db3453f0b16edd4ff1766ff551196436@trac.tools.ietf.org> References: <057.c44e32d1c6663d3d7f4c960815a6fce2@trac.tools.ietf.org> X-Trac-Ticket-ID: 241 In-Reply-To: <057.c44e32d1c6663d3d7f4c960815a6fce2@trac.tools.ietf.org> X-SA-Exim-Connect-IP: 127.0.0.1 X-SA-Exim-Rcpt-To: zach@sensinode.com, core@ietf.org X-SA-Exim-Mail-From: trac+core@trac.tools.ietf.org X-SA-Exim-Scanned: No (on grenache.tools.ietf.org); SAEximRunCond expanded to false Cc: core@ietf.org Subject: Re: [core] #241: Proxy safe to forward options X-BeenThere: core@ietf.org X-Mailman-Version: 2.1.12 Reply-To: trac+core@trac.tools.ietf.org List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Jun 2012 08:55:43 -0000 #241: Proxy safe to forward options #choose ticket.new #when True As a conclusion to the Ticket #230 discussion in the June 4th interim call, we decided to solve the identification of options that a proxy can safely forward even if not understood. Proposal made that we have a rule that “safe to forward without understanding options” have a number of something like option number mod 7 = 5. (of course more thought on 7 and 5 but you get the idea) #end #otherwise #if changes_body Changes (by zach@…): #end #if changes_descr #if not changes_body and not change.comment and change.author Description changed by zach@…: #end -- #end #if change.comment Comment(by zach@…): Text for a new Proxy-Elective class added to r685. Defined Proxy-Elective in the terminology, the Options section and the Proxy section. Left the formula for determining Proxy-Elective options TBD for now. As they are elective it would make sense for them to be even. Question: Can we identify any existing Proxy-Elective options already defined in the CoAP draft? #end #end #end -- ----------------------------------+--------------------- Reporter: zach@… | Owner: zach@… Type: protocol enhancement | Status: new Priority: minor | Milestone: Component: coap | Version: Severity: - | Resolution: Keywords: | ----------------------------------+--------------------- Ticket URL: core From hartke@tzi.org Mon Jun 11 01:56:45 2012 Return-Path: X-Original-To: core@ietfa.amsl.com Delivered-To: core@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3A6AE21F8543 for ; Mon, 11 Jun 2012 01:56:45 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.627 X-Spam-Level: X-Spam-Status: No, score=-5.627 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-4] 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 8sgke2zXJbRs for ; Mon, 11 Jun 2012 01:56:44 -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 3965321F8505 for ; Mon, 11 Jun 2012 01:56:43 -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.3/8.14.3) with ESMTP id q5B8uZbY011762 for ; Mon, 11 Jun 2012 10:56:35 +0200 (CEST) Received: from mail-pb0-f44.google.com (mail-pb0-f44.google.com [209.85.160.44]) (using TLSv1 with cipher DES-CBC3-SHA (168/168 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id 0E6C1C29 for ; Mon, 11 Jun 2012 10:56:34 +0200 (CEST) Received: by pbcwy7 with SMTP id wy7so5251293pbc.31 for ; Mon, 11 Jun 2012 01:56:33 -0700 (PDT) MIME-Version: 1.0 Received: by 10.68.225.6 with SMTP id rg6mr24491182pbc.100.1339404993120; Mon, 11 Jun 2012 01:56:33 -0700 (PDT) Received: by 10.68.130.163 with HTTP; Mon, 11 Jun 2012 01:56:33 -0700 (PDT) In-Reply-To: <057.c44e32d1c6663d3d7f4c960815a6fce2@trac.tools.ietf.org> References: <057.c44e32d1c6663d3d7f4c960815a6fce2@trac.tools.ietf.org> Date: Mon, 11 Jun 2012 10:56:33 +0200 Message-ID: From: Klaus Hartke To: core@ietf.org Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Subject: Re: [core] #241: Proxy safe to forward options X-BeenThere: core@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Jun 2012 08:56:45 -0000 > #241: Proxy safe to forward options > > =A0As a conclusion to the Ticket #230 discussion in the June 4th interim > =A0call, we decided to solve the identification of options that a proxy c= an > =A0safely forward even if not understood. > > =A0Proposal made that we have a rule that =93safe to forward without > =A0understanding options=94 have a number of something like option number= mod 7 > =A0=3D 5. (of course more thought on 7 and 5 but you get the idea) This leads us seamlessly to the next problem of what options constitute the cache key. [1] Without "safe to forward without=A0understanding" options, all options that a cache has to deal with are understood, because any unrecognised option is removed or rejected before it reaches the cache. This allows us to specify whether the option is part of the cache key or not in the specification. With "safe to forward without=A0understanding" options, caches have to deal with options they don't recognize. This means we have to to specify whether the option is part of the cache key or not in the message (e.g., option number mod 5 =3D 3). Klaus [1] see discussion in thread From trac+core@trac.tools.ietf.org Mon Jun 11 01:59:56 2012 Return-Path: X-Original-To: core@ietfa.amsl.com Delivered-To: core@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E8BE421F854E for ; Mon, 11 Jun 2012 01:59:56 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -99.139 X-Spam-Level: X-Spam-Status: No, score=-99.139 tagged_above=-999 required=5 tests=[AWL=-0.340, BAYES_50=0.001, J_CHICKENPOX_63=0.6, J_CHICKENPOX_66=0.6, 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 LxyyubvRoOWU for ; Mon, 11 Jun 2012 01:59:56 -0700 (PDT) Received: from grenache.tools.ietf.org (grenache.tools.ietf.org [77.72.230.30]) by ietfa.amsl.com (Postfix) with ESMTP id 44F3A21F854C for ; Mon, 11 Jun 2012 01:59:56 -0700 (PDT) Received: from localhost ([127.0.0.1]:54178 helo=grenache.tools.ietf.org ident=www-data) by grenache.tools.ietf.org with esmtp (Exim 4.77) (envelope-from ) id 1Se0TT-0008Dk-GB; Mon, 11 Jun 2012 10:59:47 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit From: "core issue tracker" X-Trac-Version: 0.12.2 Precedence: bulk Auto-Submitted: auto-generated X-Mailer: Trac 0.12.2, by Edgewall Software To: draft-ietf-core-coap@tools.ietf.org, cabo@tzi.org, zach@sensinode.com, fluffy@cisco.com X-Trac-Project: core Date: Mon, 11 Jun 2012 08:59:47 -0000 X-URL: http://tools.ietf.org/core/ X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/core/trac/ticket/230#comment:5 Message-ID: <068.df10204a008a9b13d8dca96ca4e4ccd8@trac.tools.ietf.org> References: <053.8673136dcb3a579ebc337cc52e97888a@trac.tools.ietf.org> X-Trac-Ticket-ID: 230 In-Reply-To: <053.8673136dcb3a579ebc337cc52e97888a@trac.tools.ietf.org> X-SA-Exim-Connect-IP: 127.0.0.1 X-SA-Exim-Rcpt-To: draft-ietf-core-coap@tools.ietf.org, cabo@tzi.org, zach@sensinode.com, fluffy@cisco.com, core@ietf.org X-SA-Exim-Mail-From: trac+core@trac.tools.ietf.org X-SA-Exim-Scanned: No (on grenache.tools.ietf.org); SAEximRunCond expanded to false Resent-To: Resent-Message-Id: <20120611085956.44F3A21F854C@ietfa.amsl.com> Resent-Date: Mon, 11 Jun 2012 01:59:56 -0700 (PDT) Resent-From: trac+core@trac.tools.ietf.org Cc: core@ietf.org Subject: Re: [core] #230: Multiple Location options need to be processed as a unit X-BeenThere: core@ietf.org X-Mailman-Version: 2.1.12 Reply-To: trac+core@trac.tools.ietf.org List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Jun 2012 08:59:57 -0000 #230: Multiple Location options need to be processed as a unit #choose ticket.new #when True Before the location in a response was split into multiple options, there was only one Location Option which was defined to be "elective". This worked well, because a client that doesn't recognize the option could ignore it without harm. However, with the Location-Path and Location-Query options (and possible future Location-Host and Location-Port options), the client must either understand or ignore all of them. Expressing such interdependencies is currently not possible in CoAP. -> Solution to be defined. Focus on the problem right now. (One solution would be to use an envelope "Location" option to contain all Location-* options, so they are ignored or used as a whole. Reserve space in the envelope option so possible future Location-Host and Location-Port options appear before Location-Path and Location-Query options in a message.) #end #otherwise #if changes_body Changes (by zach@…): #end #if changes_descr #if not changes_body and not change.comment and change.author Description changed by zach@…: #end -- #end #if change.comment Comment(by zach@…): Initial fix to this ticket included in r685. Reserved the option numbers 44, 46, and 48 for future Location-* use, and defined in Section 5.10.8 that a 4.02 must be returned if any of those reserved options are not understood in the presence of Location-Path and/or Location-Query. Question: Are 44, 46 and 48 suitable options to reserve? Do we need to worry about the ordering of these? If so, it would mean moving Location- Path and Location-Query after these reserved values. In that case they could be moved lower into the 20s for example. #end #end #end -- -----------------------------+------------------------------------- Reporter: hartke@… | Owner: draft-ietf-core-coap@… Type: protocol defect | Status: new Priority: minor | Milestone: post-WGLC-1 Component: coap | Version: coap-09 Severity: In WG Last Call | Resolution: Keywords: | -----------------------------+------------------------------------- Ticket URL: core From hartke@tzi.org Mon Jun 11 02:06:25 2012 Return-Path: X-Original-To: core@ietfa.amsl.com Delivered-To: core@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 01BF221F8554 for ; Mon, 11 Jun 2012 02:06:25 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.627 X-Spam-Level: X-Spam-Status: No, score=-5.627 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-4] 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 YgmDKWxxPSZY for ; Mon, 11 Jun 2012 02:06:24 -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 CBA0721F8564 for ; Mon, 11 Jun 2012 02:06:23 -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.3/8.14.3) with ESMTP id q5B96KDG016498 for ; Mon, 11 Jun 2012 11:06:20 +0200 (CEST) Received: from mail-pz0-f44.google.com (mail-pz0-f44.google.com [209.85.210.44]) (using TLSv1 with cipher DES-CBC3-SHA (168/168 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id D7474C3F for ; Mon, 11 Jun 2012 11:06:19 +0200 (CEST) Received: by dacx6 with SMTP id x6so5085679dac.31 for ; Mon, 11 Jun 2012 02:06:17 -0700 (PDT) MIME-Version: 1.0 Received: by 10.68.233.201 with SMTP id ty9mr24346751pbc.34.1339405577925; Mon, 11 Jun 2012 02:06:17 -0700 (PDT) Received: by 10.68.130.163 with HTTP; Mon, 11 Jun 2012 02:06:17 -0700 (PDT) In-Reply-To: <072.db3453f0b16edd4ff1766ff551196436@trac.tools.ietf.org> References: <057.c44e32d1c6663d3d7f4c960815a6fce2@trac.tools.ietf.org> <072.db3453f0b16edd4ff1766ff551196436@trac.tools.ietf.org> Date: Mon, 11 Jun 2012 11:06:17 +0200 Message-ID: From: Klaus Hartke To: zach@sensinode.com Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: core@ietf.org Subject: Re: [core] #241: Proxy safe to forward options X-BeenThere: core@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Jun 2012 09:06:25 -0000 > =A0Text for a new Proxy-Elective class added to r685. > =A0- Options fall into one of two classes: "critical" or "elective". > =A0- The difference between these is how an option unrecognized by an > =A0- end-point is handled: > =A0+ Options fall into one of three classes: "critical", "elective" or > =A0+ "proxy-elective". The difference between these is how an option > =A0+ unrecognized by an end-point or intermediate is handled: Uhm, no. "critical"/"elective" and "safe to forward without understanding"/"not safe to forward without understanding" are orthogonal. So there are four classes: - critical, not safe to forward without understanding - elective, not safe to forward without understanding - critical, safe to forward without understanding - elective, safe to forward without understanding Klaus From hartke@tzi.org Mon Jun 11 02:11:49 2012 Return-Path: X-Original-To: core@ietfa.amsl.com Delivered-To: core@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 46C7F21F854E for ; Mon, 11 Jun 2012 02:11:49 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.627 X-Spam-Level: X-Spam-Status: No, score=-5.627 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-4] 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 lrzzenvxQfyd for ; Mon, 11 Jun 2012 02:11:48 -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 4ABDA21F8535 for ; Mon, 11 Jun 2012 02:11:48 -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.3/8.14.3) with ESMTP id q5B9BfdX019420 for ; Mon, 11 Jun 2012 11:11:41 +0200 (CEST) Received: from mail-pz0-f44.google.com (mail-pz0-f44.google.com [209.85.210.44]) (using TLSv1 with cipher DES-CBC3-SHA (168/168 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id 145CEC46 for ; Mon, 11 Jun 2012 11:11:40 +0200 (CEST) Received: by dacx6 with SMTP id x6so5092244dac.31 for ; Mon, 11 Jun 2012 02:11:39 -0700 (PDT) MIME-Version: 1.0 Received: by 10.68.233.201 with SMTP id ty9mr24396523pbc.34.1339405898347; Mon, 11 Jun 2012 02:11:38 -0700 (PDT) Received: by 10.68.130.163 with HTTP; Mon, 11 Jun 2012 02:11:38 -0700 (PDT) In-Reply-To: References: <057.c44e32d1c6663d3d7f4c960815a6fce2@trac.tools.ietf.org> <072.db3453f0b16edd4ff1766ff551196436@trac.tools.ietf.org> Date: Mon, 11 Jun 2012 11:11:38 +0200 Message-ID: From: Klaus Hartke To: zach@sensinode.com Content-Type: text/plain; charset=ISO-8859-1 Cc: core@ietf.org Subject: Re: [core] #241: Proxy safe to forward options X-BeenThere: core@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Jun 2012 09:11:49 -0000 Klaus Hartke wrote: > "critical"/"elective" and "safe to forward without > understanding"/"not safe to forward without understanding" are > orthogonal. That's at least what I thought so far. Does the "critical", "safe to forward without understanding" combination not make sense or do we just have no option that falls in this class at this time? Klaus From zach@sensinode.com Mon Jun 11 02:15:39 2012 Return-Path: X-Original-To: core@ietfa.amsl.com Delivered-To: core@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E1E6321F854E for ; Mon, 11 Jun 2012 02:15:39 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.599 X-Spam-Level: X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1] 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 PAafTyjAJ181 for ; Mon, 11 Jun 2012 02:15:39 -0700 (PDT) Received: from auth-smtp.nebula.fi (auth-smtp.nebula.fi [217.30.180.105]) by ietfa.amsl.com (Postfix) with ESMTP id 109C321F854C for ; Mon, 11 Jun 2012 02:15:35 -0700 (PDT) Received: from [172.20.10.4] (85-156-197-8.elisa-mobile.fi [85.156.197.8]) (authenticated bits=0) by auth-smtp.nebula.fi (8.13.8/8.13.4) with ESMTP id q5B9FRMB011535; Mon, 11 Jun 2012 12:15:31 +0300 Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: text/plain; charset=us-ascii From: Zach Shelby In-Reply-To: Date: Mon, 11 Jun 2012 12:15:25 +0300 Content-Transfer-Encoding: quoted-printable Message-Id: <13AA37BE-EAFB-4D15-85FA-71E5DB525057@sensinode.com> References: <057.c44e32d1c6663d3d7f4c960815a6fce2@trac.tools.ietf.org> <072.db3453f0b16edd4ff1766ff551196436@trac.tools.ietf.org> To: Klaus Hartke X-Mailer: Apple Mail (2.1084) Cc: core@ietf.org Subject: Re: [core] #241: Proxy safe to forward options X-BeenThere: core@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Jun 2012 09:15:40 -0000 On Jun 11, 2012, at 12:06 PM, Klaus Hartke wrote: >> Text for a new Proxy-Elective class added to r685. >=20 >> - Options fall into one of two classes: "critical" or "elective". >> - The difference between these is how an option unrecognized by an >> - end-point is handled: >> + Options fall into one of three classes: "critical", "elective" = or >> + "proxy-elective". The difference between these is how an option >> + unrecognized by an end-point or intermediate is handled: >=20 > Uhm, no. "critical"/"elective" and "safe to forward without > understanding"/"not safe to forward without understanding" are > orthogonal. >=20 > So there are four classes: >=20 > - critical, not safe to forward without understanding > - elective, not safe to forward without understanding > - critical, safe to forward without understanding > - elective, safe to forward without understanding I think you are right. So instead of a third class, we could just call = this thing "Proxy-Safe" which is something an Option can be in addition = to being Critical or Elective.=20 An exercise that would help us thinking through this change. What = existing options would be considered: 1. Critical and Proxy-Safe 2. Elective and Proxy-Safe Zach --=20 Zach Shelby, Chief Nerd, Sensinode Ltd. http://www.sensinode.com http://zachshelby.org - My blog "On the Internet of Things" http://6lowpan.net - My book "6LoWPAN: The Wireless Embedded Internet" Mobile: +358 40 7796297 From trac+core@trac.tools.ietf.org Mon Jun 11 02:22:21 2012 Return-Path: X-Original-To: core@ietfa.amsl.com Delivered-To: core@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6578821F8566 for ; Mon, 11 Jun 2012 02:22:21 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -99.609 X-Spam-Level: X-Spam-Status: No, score=-99.609 tagged_above=-999 required=5 tests=[AWL=0.301, BAYES_05=-1.11, J_CHICKENPOX_63=0.6, J_CHICKENPOX_66=0.6, 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 srEcsmnuTGGW for ; Mon, 11 Jun 2012 02:22:21 -0700 (PDT) Received: from grenache.tools.ietf.org (grenache.tools.ietf.org [77.72.230.30]) by ietfa.amsl.com (Postfix) with ESMTP id DA45E21F8518 for ; Mon, 11 Jun 2012 02:22:20 -0700 (PDT) Received: from localhost ([127.0.0.1]:55446 helo=grenache.tools.ietf.org ident=www-data) by grenache.tools.ietf.org with esmtp (Exim 4.77) (envelope-from ) id 1Se0p8-0000nr-Ef; Mon, 11 Jun 2012 11:22:10 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit From: "core issue tracker" X-Trac-Version: 0.12.2 Precedence: bulk Auto-Submitted: auto-generated X-Mailer: Trac 0.12.2, by Edgewall Software To: draft-ietf-core-coap@tools.ietf.org, zach@sensinode.com, angelo@castellani.net X-Trac-Project: core Date: Mon, 11 Jun 2012 09:22:10 -0000 X-URL: http://tools.ietf.org/core/ X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/core/trac/ticket/238#comment:3 Message-ID: <066.8822123851737a6941ce59f490db7c46@trac.tools.ietf.org> References: <051.6e14fd2778cd6bb461ee0489bd1726db@trac.tools.ietf.org> X-Trac-Ticket-ID: 238 In-Reply-To: <051.6e14fd2778cd6bb461ee0489bd1726db@trac.tools.ietf.org> X-SA-Exim-Connect-IP: 127.0.0.1 X-SA-Exim-Rcpt-To: draft-ietf-core-coap@tools.ietf.org, zach@sensinode.com, angelo@castellani.net, core@ietf.org X-SA-Exim-Mail-From: trac+core@trac.tools.ietf.org X-SA-Exim-Scanned: No (on grenache.tools.ietf.org); SAEximRunCond expanded to false Resent-To: Resent-Message-Id: <20120611092220.DA45E21F8518@ietfa.amsl.com> Resent-Date: Mon, 11 Jun 2012 02:22:20 -0700 (PDT) Resent-From: trac+core@trac.tools.ietf.org Cc: core@ietf.org Subject: Re: [core] #238: Proxy terminology X-BeenThere: core@ietf.org X-Mailman-Version: 2.1.12 Reply-To: trac+core@trac.tools.ietf.org List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Jun 2012 09:22:21 -0000 #238: Proxy terminology #choose ticket.new #when True Cullen Jennings notes (msg03072e): Section 1.2 We have two very different types of proxies - one only speaks COAP and the other type translates between CoAP and HTTP. I would prefer a different terms for the translating type. Perhaps "translator" or "translator proxy". I understand people don't want to use gateway but it is what many people would call a gateway. -> Agree on terminology and go through the 113 occurrences of "proxy" #end #otherwise #if changes_body Changes (by zach@…): #end #if changes_descr #if not changes_body and not change.comment and change.author Description changed by zach@…: #end -- #end #if change.comment Comment(by zach@…): In the June 4th interim meeting we settled on "Cross Proxy". #end #end #end -- -----------------------------+------------------------------------- Reporter: cabo@… | Owner: draft-ietf-core-coap@… Type: editorial | Status: new Priority: minor | Milestone: post-WGLC-1 Component: coap | Version: coap-09 Severity: In WG Last Call | Resolution: Keywords: | -----------------------------+------------------------------------- Ticket URL: core From trac+core@trac.tools.ietf.org Mon Jun 11 02:23:44 2012 Return-Path: X-Original-To: core@ietfa.amsl.com Delivered-To: core@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E954821F8567 for ; Mon, 11 Jun 2012 02:23:44 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -99.669 X-Spam-Level: X-Spam-Status: No, score=-99.669 tagged_above=-999 required=5 tests=[AWL=0.241, BAYES_05=-1.11, J_CHICKENPOX_63=0.6, J_CHICKENPOX_66=0.6, 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 q3DSLr7yV2+c for ; Mon, 11 Jun 2012 02:23:44 -0700 (PDT) Received: from grenache.tools.ietf.org (grenache.tools.ietf.org [77.72.230.30]) by ietfa.amsl.com (Postfix) with ESMTP id 6A4CC21F8460 for ; Mon, 11 Jun 2012 02:23:44 -0700 (PDT) Received: from localhost ([127.0.0.1]:55501 helo=grenache.tools.ietf.org ident=www-data) by grenache.tools.ietf.org with esmtp (Exim 4.77) (envelope-from ) id 1Se0qZ-0000Mg-CZ; Mon, 11 Jun 2012 11:23:39 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit From: "core issue tracker" X-Trac-Version: 0.12.2 Precedence: bulk Auto-Submitted: auto-generated X-Mailer: Trac 0.12.2, by Edgewall Software To: hartke@tzi.org, zach@sensinode.com, angelo@castellani.net X-Trac-Project: core Date: Mon, 11 Jun 2012 09:23:39 -0000 X-URL: http://tools.ietf.org/core/ X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/core/trac/ticket/238#comment:4 Message-ID: <066.6a7483ecc2a706d98f77ef59ed14bc1a@trac.tools.ietf.org> References: <051.6e14fd2778cd6bb461ee0489bd1726db@trac.tools.ietf.org> X-Trac-Ticket-ID: 238 In-Reply-To: <051.6e14fd2778cd6bb461ee0489bd1726db@trac.tools.ietf.org> X-SA-Exim-Connect-IP: 127.0.0.1 X-SA-Exim-Rcpt-To: hartke@tzi.org, zach@sensinode.com, angelo@castellani.net, core@ietf.org X-SA-Exim-Mail-From: trac+core@trac.tools.ietf.org X-SA-Exim-Scanned: No (on grenache.tools.ietf.org); SAEximRunCond expanded to false Cc: core@ietf.org Subject: Re: [core] #238: Proxy terminology X-BeenThere: core@ietf.org X-Mailman-Version: 2.1.12 Reply-To: trac+core@trac.tools.ietf.org List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Jun 2012 09:23:45 -0000 #238: Proxy terminology #choose ticket.new #when True Cullen Jennings notes (msg03072e): Section 1.2 We have two very different types of proxies - one only speaks COAP and the other type translates between CoAP and HTTP. I would prefer a different terms for the translating type. Perhaps "translator" or "translator proxy". I understand people don't want to use gateway but it is what many people would call a gateway. -> Agree on terminology and go through the 113 occurrences of "proxy" #end #otherwise #if changes_body Changes (by zach@…): * owner: draft-ietf-core-coap@… => hartke@… #end #if changes_descr #if not changes_body and not change.comment and change.author Description changed by zach@…: #end -- #end #if change.comment Comment: #end #end #end -- -----------------------------+-------------------------- Reporter: cabo@… | Owner: hartke@… Type: editorial | Status: new Priority: minor | Milestone: post-WGLC-1 Component: coap | Version: coap-09 Severity: In WG Last Call | Resolution: Keywords: | -----------------------------+-------------------------- Ticket URL: core From hartke@tzi.org Mon Jun 11 02:34:08 2012 Return-Path: X-Original-To: core@ietfa.amsl.com Delivered-To: core@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8FC9021F8552 for ; Mon, 11 Jun 2012 02:34:08 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.627 X-Spam-Level: X-Spam-Status: No, score=-5.627 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-4] 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 k3ceEyVyk+lU for ; Mon, 11 Jun 2012 02:34: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 C7F8121F847D for ; Mon, 11 Jun 2012 02:34:07 -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.3/8.14.3) with ESMTP id q5B9Y0v9002106 for ; Mon, 11 Jun 2012 11:34:00 +0200 (CEST) Received: from mail-pb0-f44.google.com (mail-pb0-f44.google.com [209.85.160.44]) (using TLSv1 with cipher DES-CBC3-SHA (168/168 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id E9C5FC82 for ; Mon, 11 Jun 2012 11:33:59 +0200 (CEST) Received: by pbcwy7 with SMTP id wy7so5296242pbc.31 for ; Mon, 11 Jun 2012 02:33:58 -0700 (PDT) MIME-Version: 1.0 Received: by 10.68.225.6 with SMTP id rg6mr24830494pbc.100.1339407238040; Mon, 11 Jun 2012 02:33:58 -0700 (PDT) Received: by 10.68.130.163 with HTTP; Mon, 11 Jun 2012 02:33:58 -0700 (PDT) In-Reply-To: <13AA37BE-EAFB-4D15-85FA-71E5DB525057@sensinode.com> References: <057.c44e32d1c6663d3d7f4c960815a6fce2@trac.tools.ietf.org> <072.db3453f0b16edd4ff1766ff551196436@trac.tools.ietf.org> <13AA37BE-EAFB-4D15-85FA-71E5DB525057@sensinode.com> Date: Mon, 11 Jun 2012 11:33:58 +0200 Message-ID: From: Klaus Hartke To: Zach Shelby Content-Type: text/plain; charset=ISO-8859-1 Cc: core@ietf.org Subject: Re: [core] #241: Proxy safe to forward options X-BeenThere: core@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Jun 2012 09:34:08 -0000 Zach Shelby wrote: > An exercise that would help us thinking through this change. What existing options would be considered: > > 1. Critical and Proxy-Safe > > 2. Elective and Proxy-Safe Here's a quick compilation (not necessarily completely accurate): +-------+--------+-----+----+--------+-------------+ |Request|Response|Cache|Safe|Critical|Name | +-------+--------+-----+----+--------+-------------+ | - | X | - | X | X |Content-Type | | - | X | - | - | - |Max-Age | | X | - | X | - | X |Proxy-Uri | | X | X | X | X | - |ETag | | X | - | X | X | X |Uri-* | | - | X | - | X | - |Location-* | | X | X | - | - | - |Observe | | X | X | - | - | X |Token | | X | - | X | X | - |Accept | | X | - | X | X | X |If-Match | | X | X | - | X | - |Vendor | | X | X | - | - | X |Block2 | | X | X | - | X | - |Size | | X | X | - | - | X |Block1 | | X | - | X | X | X |If-None-Match| +-------+--------+-----+----+--------+-------------+ Klaus From trac+core@trac.tools.ietf.org Mon Jun 11 02:35:33 2012 Return-Path: X-Original-To: core@ietfa.amsl.com Delivered-To: core@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5F3D721F8559 for ; Mon, 11 Jun 2012 02:35:33 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -99.525 X-Spam-Level: X-Spam-Status: No, score=-99.525 tagged_above=-999 required=5 tests=[AWL=0.015, BAYES_20=-0.74, J_CHICKENPOX_63=0.6, J_CHICKENPOX_66=0.6, 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 zioC7kRPMuck for ; Mon, 11 Jun 2012 02:35:32 -0700 (PDT) Received: from grenache.tools.ietf.org (grenache.tools.ietf.org [77.72.230.30]) by ietfa.amsl.com (Postfix) with ESMTP id C0ADC21F8554 for ; Mon, 11 Jun 2012 02:35:32 -0700 (PDT) Received: from localhost ([127.0.0.1]:55872 helo=grenache.tools.ietf.org ident=www-data) by grenache.tools.ietf.org with esmtp (Exim 4.77) (envelope-from ) id 1Se11o-0004hU-WE; Mon, 11 Jun 2012 11:35:17 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit From: "core issue tracker" X-Trac-Version: 0.12.2 Precedence: bulk Auto-Submitted: auto-generated X-Mailer: Trac 0.12.2, by Edgewall Software To: draft-ietf-core-coap@tools.ietf.org, zach@sensinode.com X-Trac-Project: core Date: Mon, 11 Jun 2012 09:35:16 -0000 X-URL: http://tools.ietf.org/core/ X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/core/trac/ticket/207#comment:1 Message-ID: <068.77212de9fad66455e98c86f6c5974162@trac.tools.ietf.org> References: <053.d889c7b2b45ce344b85654e528a4b801@trac.tools.ietf.org> X-Trac-Ticket-ID: 207 In-Reply-To: <053.d889c7b2b45ce344b85654e528a4b801@trac.tools.ietf.org> X-SA-Exim-Connect-IP: 127.0.0.1 X-SA-Exim-Rcpt-To: draft-ietf-core-coap@tools.ietf.org, zach@sensinode.com, core@ietf.org X-SA-Exim-Mail-From: trac+core@trac.tools.ietf.org X-SA-Exim-Scanned: No (on grenache.tools.ietf.org); SAEximRunCond expanded to false Resent-To: Resent-Message-Id: <20120611093532.C0ADC21F8554@ietfa.amsl.com> Resent-Date: Mon, 11 Jun 2012 02:35:32 -0700 (PDT) Resent-From: trac+core@trac.tools.ietf.org Cc: core@ietf.org Subject: Re: [core] #207: Add advice on default values for critical options X-BeenThere: core@ietf.org X-Mailman-Version: 2.1.12 Reply-To: trac+core@trac.tools.ietf.org List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Jun 2012 09:35:33 -0000 #207: Add advice on default values for critical options #choose ticket.new #when True Klaus Hartke points out that the guidelines for registration of new options could include a check for an essential property of any default values for new critical options. in 11.2, a change for the registration information could be: o The default value, if any. -> o The default value, if any. For a critical option with a default value, a discussion how the default value enables processing by implementations not implementing the critical option (Section 5.4.3). In 5.4.3, add at the end: Where a critical option has a default value, this is chosen in such a way that the absence of the option in a message can be processed properly both by implementations unaware of the critical option and by implementations that interpret this absence as the presence of the default value for the option. Some wordsmithing may be required. #end #otherwise #if changes_body Changes (by zach@…): * status: new => closed * resolution: => fixed #end #if changes_descr #if not changes_body and not change.comment and change.author Description changed by zach@…: #end -- #end #if change.comment Comment: Change made in r686. #end #end #end -- -----------------------------+------------------------------------- Reporter: hartke@… | Owner: draft-ietf-core-coap@… Type: editorial | Status: closed Priority: minor | Milestone: post-WGLC-1 Component: coap | Version: Severity: In WG Last Call | Resolution: fixed Keywords: | -----------------------------+------------------------------------- Ticket URL: core From trac+core@trac.tools.ietf.org Mon Jun 11 04:08:59 2012 Return-Path: X-Original-To: core@ietfa.amsl.com Delivered-To: core@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5806B21F8597 for ; Mon, 11 Jun 2012 04:08:59 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -100.456 X-Spam-Level: X-Spam-Status: No, score=-100.456 tagged_above=-999 required=5 tests=[AWL=0.943, BAYES_00=-2.599, J_CHICKENPOX_63=0.6, J_CHICKENPOX_66=0.6, 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 tJ4llOYIUeV5 for ; Mon, 11 Jun 2012 04:08:58 -0700 (PDT) Received: from grenache.tools.ietf.org (grenache.tools.ietf.org [77.72.230.30]) by ietfa.amsl.com (Postfix) with ESMTP id C1EFF21F858A for ; Mon, 11 Jun 2012 04:08:58 -0700 (PDT) Received: from localhost ([127.0.0.1]:60482 helo=grenache.tools.ietf.org ident=www-data) by grenache.tools.ietf.org with esmtp (Exim 4.77) (envelope-from ) id 1Se2UL-0002zk-6W; Mon, 11 Jun 2012 13:08:49 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit From: "core issue tracker" X-Trac-Version: 0.12.2 Precedence: bulk Auto-Submitted: auto-generated X-Mailer: Trac 0.12.2, by Edgewall Software To: draft-ietf-core-coap@tools.ietf.org, zach@sensinode.com X-Trac-Project: core Date: Mon, 11 Jun 2012 11:08:49 -0000 X-URL: http://tools.ietf.org/core/ X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/core/trac/ticket/212#comment:2 Message-ID: <066.3e324fcb52f8d11c937f9cd4c4a8493a@trac.tools.ietf.org> References: <051.4e6cdfc507a23a9b28c6274a5b955113@trac.tools.ietf.org> X-Trac-Ticket-ID: 212 In-Reply-To: <051.4e6cdfc507a23a9b28c6274a5b955113@trac.tools.ietf.org> X-SA-Exim-Connect-IP: 127.0.0.1 X-SA-Exim-Rcpt-To: draft-ietf-core-coap@tools.ietf.org, zach@sensinode.com, core@ietf.org X-SA-Exim-Mail-From: trac+core@trac.tools.ietf.org X-SA-Exim-Scanned: No (on grenache.tools.ietf.org); SAEximRunCond expanded to false Resent-To: Resent-Message-Id: <20120611110858.C1EFF21F858A@ietfa.amsl.com> Resent-Date: Mon, 11 Jun 2012 04:08:58 -0700 (PDT) Resent-From: trac+core@trac.tools.ietf.org Cc: core@ietf.org Subject: Re: [core] #212: Option numbers 14, 28, 42, ... reserved but usable X-BeenThere: core@ietf.org X-Mailman-Version: 2.1.12 Reply-To: trac+core@trac.tools.ietf.org List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Jun 2012 11:08:59 -0000 #212: Option numbers 14, 28, 42, ... reserved but usable #choose ticket.new #when True Section 5.4.5. (Option Numbers) states that "the numbers 14, 28, 42, ... are reserved for 'fenceposting'". It is actually not necessary to reserve them for this; options with those numbers just need to have a default value that is encoded with zero bytes. The Vendor option in -misc already takes advantage of this. -> Clarify that while the positive option numbers divisible by 14 are indeed reserved, they still are available for allocation as long as a zero-length option with each of these numbers remains available as a no-operation option for fenceposting. (msg03034a, also covers msg03072cc) #end #otherwise #if changes_body Changes (by zach@…): * status: new => closed * resolution: => fixed #end #if changes_descr #if not changes_body and not change.comment and change.author Description changed by zach@…: #end -- #end #if change.comment Comment: #end #end #end -- -----------------------------+------------------------------------- Reporter: cabo@… | Owner: draft-ietf-core-coap@… Type: editorial | Status: closed Priority: minor | Milestone: post-WGLC-1 Component: coap | Version: coap-09 Severity: In WG Last Call | Resolution: fixed Keywords: | -----------------------------+------------------------------------- Ticket URL: core From trac+core@trac.tools.ietf.org Mon Jun 11 04:08:59 2012 Return-Path: X-Original-To: core@ietfa.amsl.com Delivered-To: core@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9520321F8599 for ; Mon, 11 Jun 2012 04:08:59 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -100.574 X-Spam-Level: X-Spam-Status: No, score=-100.574 tagged_above=-999 required=5 tests=[AWL=0.825, BAYES_00=-2.599, J_CHICKENPOX_63=0.6, J_CHICKENPOX_66=0.6, 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 PO7NzCPT79dJ for ; Mon, 11 Jun 2012 04:08:59 -0700 (PDT) Received: from grenache.tools.ietf.org (grenache.tools.ietf.org [77.72.230.30]) by ietfa.amsl.com (Postfix) with ESMTP id D118A21F8596 for ; Mon, 11 Jun 2012 04:08:58 -0700 (PDT) Received: from localhost ([127.0.0.1]:60481 helo=grenache.tools.ietf.org ident=www-data) by grenache.tools.ietf.org with esmtp (Exim 4.77) (envelope-from ) id 1Se2UE-0000cu-9K; Mon, 11 Jun 2012 13:08:42 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit From: "core issue tracker" X-Trac-Version: 0.12.2 Precedence: bulk Auto-Submitted: auto-generated X-Mailer: Trac 0.12.2, by Edgewall Software To: draft-ietf-core-coap@tools.ietf.org, zach@sensinode.com X-Trac-Project: core Date: Mon, 11 Jun 2012 11:08:42 -0000 X-URL: http://tools.ietf.org/core/ X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/core/trac/ticket/212#comment:1 Message-ID: <066.c5662d2812b84c6351b5de2c5108b774@trac.tools.ietf.org> References: <051.4e6cdfc507a23a9b28c6274a5b955113@trac.tools.ietf.org> X-Trac-Ticket-ID: 212 In-Reply-To: <051.4e6cdfc507a23a9b28c6274a5b955113@trac.tools.ietf.org> X-SA-Exim-Connect-IP: 127.0.0.1 X-SA-Exim-Rcpt-To: draft-ietf-core-coap@tools.ietf.org, zach@sensinode.com, core@ietf.org X-SA-Exim-Mail-From: trac+core@trac.tools.ietf.org X-SA-Exim-Scanned: No (on grenache.tools.ietf.org); SAEximRunCond expanded to false Resent-To: Resent-Message-Id: <20120611110858.D118A21F8596@ietfa.amsl.com> Resent-Date: Mon, 11 Jun 2012 04:08:58 -0700 (PDT) Resent-From: trac+core@trac.tools.ietf.org Cc: core@ietf.org Subject: Re: [core] #212: Option numbers 14, 28, 42, ... reserved but usable X-BeenThere: core@ietf.org X-Mailman-Version: 2.1.12 Reply-To: trac+core@trac.tools.ietf.org List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Jun 2012 11:08:59 -0000 #212: Option numbers 14, 28, 42, ... reserved but usable #choose ticket.new #when True Section 5.4.5. (Option Numbers) states that "the numbers 14, 28, 42, ... are reserved for 'fenceposting'". It is actually not necessary to reserve them for this; options with those numbers just need to have a default value that is encoded with zero bytes. The Vendor option in -misc already takes advantage of this. -> Clarify that while the positive option numbers divisible by 14 are indeed reserved, they still are available for allocation as long as a zero-length option with each of these numbers remains available as a no-operation option for fenceposting. (msg03034a, also covers msg03072cc) #end #otherwise #if changes_body Changes (by zach@…): #end #if changes_descr #if not changes_body and not change.comment and change.author Description changed by zach@…: #end -- #end #if change.comment Comment(by zach@…): Done in r687. #end #end #end -- -----------------------------+------------------------------------- Reporter: cabo@… | Owner: draft-ietf-core-coap@… Type: editorial | Status: new Priority: minor | Milestone: post-WGLC-1 Component: coap | Version: coap-09 Severity: In WG Last Call | Resolution: Keywords: | -----------------------------+------------------------------------- Ticket URL: core From trac+core@trac.tools.ietf.org Mon Jun 11 04:47:34 2012 Return-Path: X-Original-To: core@ietfa.amsl.com Delivered-To: core@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C41AC21F8497 for ; Mon, 11 Jun 2012 04:47:34 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -100.666 X-Spam-Level: X-Spam-Status: No, score=-100.666 tagged_above=-999 required=5 tests=[AWL=0.733, BAYES_00=-2.599, J_CHICKENPOX_63=0.6, J_CHICKENPOX_66=0.6, 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 mlY9vkoz+8DD for ; Mon, 11 Jun 2012 04:47:34 -0700 (PDT) Received: from grenache.tools.ietf.org (grenache.tools.ietf.org [77.72.230.30]) by ietfa.amsl.com (Postfix) with ESMTP id 49D0421F8491 for ; Mon, 11 Jun 2012 04:47:34 -0700 (PDT) Received: from localhost ([127.0.0.1]:34130 helo=grenache.tools.ietf.org ident=www-data) by grenache.tools.ietf.org with esmtp (Exim 4.77) (envelope-from ) id 1Se35Z-0002I4-B4; Mon, 11 Jun 2012 13:47:17 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit From: "core issue tracker" X-Trac-Version: 0.12.2 Precedence: bulk Auto-Submitted: auto-generated X-Mailer: Trac 0.12.2, by Edgewall Software To: zach@sensinode.com X-Trac-Project: core Date: Mon, 11 Jun 2012 11:47:17 -0000 X-URL: http://tools.ietf.org/core/ X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/core/trac/ticket/241#comment:2 Message-ID: <072.4a5de8d141dccd965c0ba68257d7767f@trac.tools.ietf.org> References: <057.c44e32d1c6663d3d7f4c960815a6fce2@trac.tools.ietf.org> X-Trac-Ticket-ID: 241 In-Reply-To: <057.c44e32d1c6663d3d7f4c960815a6fce2@trac.tools.ietf.org> X-SA-Exim-Connect-IP: 127.0.0.1 X-SA-Exim-Rcpt-To: zach@sensinode.com, core@ietf.org X-SA-Exim-Mail-From: trac+core@trac.tools.ietf.org X-SA-Exim-Scanned: No (on grenache.tools.ietf.org); SAEximRunCond expanded to false Cc: core@ietf.org Subject: Re: [core] #241: Proxy Safe & Cache Key indication for options (was: Proxy safe to forward options) X-BeenThere: core@ietf.org X-Mailman-Version: 2.1.12 Reply-To: trac+core@trac.tools.ietf.org List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Jun 2012 11:47:34 -0000 #241: Proxy Safe & Cache Key indication for options #choose ticket.new #when True As a conclusion to the Ticket #230 discussion in the June 4th interim call, we decided to solve the identification of options that a proxy can safely forward even if not understood. Proposal made that we have a rule that “safe to forward without understanding options” have a number of something like option number mod 7 = 5. (of course more thought on 7 and 5 but you get the idea) #end #otherwise #if changes_body Changes (by zach@…): #end #if changes_descr #if not changes_body and not change.comment and change.author Description changed by zach@…: #end -- #end #if change.comment Comment(by zach@…): #end #end #end -- ----------------------------------+--------------------- Reporter: zach@… | Owner: zach@… Type: protocol enhancement | Status: new Priority: minor | Milestone: Component: coap | Version: Severity: - | Resolution: Keywords: | ----------------------------------+--------------------- Ticket URL: core From trac+core@trac.tools.ietf.org Mon Jun 11 05:00:18 2012 Return-Path: X-Original-To: core@ietfa.amsl.com Delivered-To: core@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5CD7A21F8566 for ; Mon, 11 Jun 2012 05:00:18 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -100.739 X-Spam-Level: X-Spam-Status: No, score=-100.739 tagged_above=-999 required=5 tests=[AWL=0.660, BAYES_00=-2.599, J_CHICKENPOX_63=0.6, J_CHICKENPOX_66=0.6, 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 VtAdHSXigDdU for ; Mon, 11 Jun 2012 05:00:17 -0700 (PDT) Received: from grenache.tools.ietf.org (grenache.tools.ietf.org [77.72.230.30]) by ietfa.amsl.com (Postfix) with ESMTP id BBC3821F8564 for ; Mon, 11 Jun 2012 05:00:17 -0700 (PDT) Received: from localhost ([127.0.0.1]:35012 helo=grenache.tools.ietf.org ident=www-data) by grenache.tools.ietf.org with esmtp (Exim 4.77) (envelope-from ) id 1Se3I8-0005th-7P; Mon, 11 Jun 2012 14:00:16 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit From: "core issue tracker" X-Trac-Version: 0.12.2 Precedence: bulk Auto-Submitted: auto-generated X-Mailer: Trac 0.12.2, by Edgewall Software To: zach@sensinode.com X-Trac-Project: core Date: Mon, 11 Jun 2012 12:00:16 -0000 X-URL: http://tools.ietf.org/core/ X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/core/trac/ticket/241#comment:3 Message-ID: <072.609c24e1f174832758cb6278437d7c95@trac.tools.ietf.org> References: <057.c44e32d1c6663d3d7f4c960815a6fce2@trac.tools.ietf.org> X-Trac-Ticket-ID: 241 In-Reply-To: <057.c44e32d1c6663d3d7f4c960815a6fce2@trac.tools.ietf.org> X-SA-Exim-Connect-IP: 127.0.0.1 X-SA-Exim-Rcpt-To: zach@sensinode.com, core@ietf.org X-SA-Exim-Mail-From: trac+core@trac.tools.ietf.org X-SA-Exim-Scanned: No (on grenache.tools.ietf.org); SAEximRunCond expanded to false Cc: core@ietf.org Subject: Re: [core] #241: Proxy Safe & Cache Key indication for options X-BeenThere: core@ietf.org X-Mailman-Version: 2.1.12 Reply-To: trac+core@trac.tools.ietf.org List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Jun 2012 12:00:18 -0000 #241: Proxy Safe & Cache Key indication for options #choose ticket.new #when True As a conclusion to the Ticket #230 discussion in the June 4th interim call, we decided to solve the identification of options that a proxy can safely forward even if not understood. Proposal made that we have a rule that “safe to forward without understanding options” have a number of something like option number mod 7 = 5. (of course more thought on 7 and 5 but you get the idea) #end #otherwise #if changes_body Changes (by zach@…): #end #if changes_descr #if not changes_body and not change.comment and change.author Description changed by zach@…: #end -- #end #if change.comment Comment(by zach@…): Klaus pointed out that in addition to the proxy safe to forward, an indication of inclusion in the cache key would be needed. In addition, it was pointed out the this "Proxy Safe" indication is needed for both elective and critical options. This means we would have to deal with three pieces of information: * Critial / Elective * Proxy Safe * Cache Key We propose that these can be handled using the last 3 LSB bits of the option number (not the delta), where Critical/Elective is masked on the first LSB (as it is now), Proxy Safe on the second LSB (every other two options), and Cache Key on the third LSB (every other four options). On initial indication of which current options might be Proxy Safe or Cache Key was compiled by Klaus (needs to be double-checked): {{{ +-------+--------+-----+----+--------+-------------+ |Request|Response|Cache|Safe|Critical|Name | +-------+--------+-----+----+--------+-------------+ | - | X | - | X | X |Content-Type | | - | X | - | - | - |Max-Age | | X | - | X | - | X |Proxy-Uri | | X | X | X | X | - |ETag | | X | - | X | X | X |Uri-* | | - | X | - | X | - |Location-* | | X | X | - | - | - |Observe | | X | X | - | - | X |Token | | X | - | X | X | - |Accept | | X | - | X | X | X |If-Match | | X | X | - | X | - |Vendor | | X | X | - | - | X |Block2 | | X | X | - | X | - |Size | | X | X | - | - | X |Block1 | | X | - | X | X | X |If-None-Match| +-------+--------+-----+----+--------+-------------+ }}} If we implement this ticket, it has two consequences: 1. Most options numbers will be re-assigned to match the masks 2. Ticket #230 (http://trac.tools.ietf.org/wg/core/trac/ticket/230) should be re-thought as with all Uri-* and Location-* options the new masks require option #s into the 50s. If the Uri and Location URIs would require a single option, we are only into the 20s as now. See a proposed solution in Ticket #230. #end #end #end -- ----------------------------------+--------------------- Reporter: zach@… | Owner: zach@… Type: protocol enhancement | Status: new Priority: minor | Milestone: Component: coap | Version: Severity: - | Resolution: Keywords: | ----------------------------------+--------------------- Ticket URL: core From cabo@tzi.org Mon Jun 11 05:41:51 2012 Return-Path: X-Original-To: core@ietfa.amsl.com Delivered-To: core@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0FDF321F85AA for ; Mon, 11 Jun 2012 05:41:51 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -105.649 X-Spam-Level: X-Spam-Status: No, score=-105.649 tagged_above=-999 required=5 tests=[AWL=0.600, 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 wmk1GIJJXd-O for ; Mon, 11 Jun 2012 05:41:50 -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 C65CE21F8497 for ; Mon, 11 Jun 2012 05:41:49 -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.3/8.14.3) with ESMTP id q5BCffKB020323; Mon, 11 Jun 2012 14:41:41 +0200 (CEST) Received: from [192.168.217.105] (p54899670.dip.t-dialin.net [84.137.150.112]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id EC9B9E5A; Mon, 11 Jun 2012 14:41:40 +0200 (CEST) Mime-Version: 1.0 (Apple Message framework v1278) Content-Type: text/plain; charset=iso-8859-1 From: Carsten Bormann In-Reply-To: Date: Mon, 11 Jun 2012 14:41:40 +0200 Content-Transfer-Encoding: quoted-printable Message-Id: <00083183-746F-4AC0-90BF-A7E7E5002ED4@tzi.org> References: <057.c44e32d1c6663d3d7f4c960815a6fce2@trac.tools.ietf.org> <072.db3453f0b16edd4ff1766ff551196436@trac.tools.ietf.org> <13AA37BE-EAFB-4D15-85FA-71E5DB525057@sensinode.com> To: Klaus Hartke X-Mailer: Apple Mail (2.1278) Cc: core@ietf.org Subject: Re: [core] #241: Proxy safe to forward options X-BeenThere: core@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Jun 2012 12:41:51 -0000 On Jun 11, 2012, at 11:33, Klaus Hartke wrote: >=20 > +-------+--------+-----+----+--------+-------------+ > |Request|Response|Cache|Safe|Critical|Name | > +-------+--------+-----+----+--------+-------------+ > | - | X | - | X | X |Content-Type | > | - | X | - | - | - |Max-Age | > | X | - | X | - | X |Proxy-Uri | > | X | X | X | X | - |ETag | > | X | - | X | X | X |Uri-* | > | - | X | - | X | - |Location-* | > | X | X | - | - | - |Observe | > | X | X | - | - | X |Token | > | X | - | X | X | - |Accept | > | X | - | X | X | X |If-Match | > | X | X | - | X | - |Vendor | > | X | X | - | - | X |Block2 | > | X | X | - | X | - |Size | > | X | X | - | - | X |Block1 | > | X | - | X | X | X |If-None-Match| > +-------+--------+-----+----+--------+-------------+ I think we need to discuss the meaningful combinations here. For instance, for a critical, = non-safe-to-be-forwarded-without-knowing-it option, it is simply not = necessary to indicate in the option number whether it is a cache key or = not (everybody handling this option knows that), so we are free to use = the bit at will. The cache key property is only relevant for requests, anyway? I don't understand what "Cache" means for repeatable options (e.g., = Accept). We don't have a Cache-key/non-safe/elective combination. Just luck? I'm not sure I understand the difference between the bits of Uri* and = *Uri. It may be necessary to rip apart options where the request usage has = different semantics from the response usage. We may need vendor options for all meaningful combinations of bits. I would prefer to have a set bit for "unsafe" instead of "safe" (if we = have a bit for "critical" instead of "elective"). If we go this route, we probably should look at all options proposed so = far (see the registry table in the SVN) and guess what combinations are = how likely. That will enable us to come up with a good encoding. Gr=FC=DFe, Carsten From trac+core@trac.tools.ietf.org Mon Jun 11 06:26:20 2012 Return-Path: X-Original-To: core@ietfa.amsl.com Delivered-To: core@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A401D21F8587 for ; Mon, 11 Jun 2012 06:26:20 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -100.799 X-Spam-Level: X-Spam-Status: No, score=-100.799 tagged_above=-999 required=5 tests=[AWL=0.600, BAYES_00=-2.599, J_CHICKENPOX_63=0.6, J_CHICKENPOX_66=0.6, 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 qK0wJ1WGjVRG for ; Mon, 11 Jun 2012 06:26:20 -0700 (PDT) Received: from grenache.tools.ietf.org (grenache.tools.ietf.org [77.72.230.30]) by ietfa.amsl.com (Postfix) with ESMTP id 155C121F851A for ; Mon, 11 Jun 2012 06:26:20 -0700 (PDT) Received: from localhost ([127.0.0.1]:39504 helo=grenache.tools.ietf.org ident=www-data) by grenache.tools.ietf.org with esmtp (Exim 4.77) (envelope-from ) id 1Se4dD-0006wL-1z; Mon, 11 Jun 2012 15:26:07 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit From: "core issue tracker" X-Trac-Version: 0.12.2 Precedence: bulk Auto-Submitted: auto-generated X-Mailer: Trac 0.12.2, by Edgewall Software To: zach@sensinode.com X-Trac-Project: core Date: Mon, 11 Jun 2012 13:26:07 -0000 X-URL: http://tools.ietf.org/core/ X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/core/trac/ticket/241#comment:4 Message-ID: <072.12044a29967c19007d91c892c7c6a489@trac.tools.ietf.org> References: <057.c44e32d1c6663d3d7f4c960815a6fce2@trac.tools.ietf.org> X-Trac-Ticket-ID: 241 In-Reply-To: <057.c44e32d1c6663d3d7f4c960815a6fce2@trac.tools.ietf.org> X-SA-Exim-Connect-IP: 127.0.0.1 X-SA-Exim-Rcpt-To: zach@sensinode.com, core@ietf.org X-SA-Exim-Mail-From: trac+core@trac.tools.ietf.org X-SA-Exim-Scanned: No (on grenache.tools.ietf.org); SAEximRunCond expanded to false Cc: core@ietf.org Subject: Re: [core] #241: Proxy Safe & Cache Key indication for options X-BeenThere: core@ietf.org X-Mailman-Version: 2.1.12 Reply-To: trac+core@trac.tools.ietf.org List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Jun 2012 13:26:20 -0000 #241: Proxy Safe & Cache Key indication for options #choose ticket.new #when True As a conclusion to the Ticket #230 discussion in the June 4th interim call, we decided to solve the identification of options that a proxy can safely forward even if not understood. Proposal made that we have a rule that “safe to forward without understanding options” have a number of something like option number mod 7 = 5. (of course more thought on 7 and 5 but you get the idea) #end #otherwise #if changes_body Changes (by zach@…): #end #if changes_descr #if not changes_body and not change.comment and change.author Description changed by zach@…: #end -- #end #if change.comment Comment(by zach@…): Comment from Carsten: I think we need to discuss the meaningful combinations here. For instance, for a critical, non-safe-to-be-forwarded-without-knowing-it option, it is simply not necessary to indicate in the option number whether it is a cache key or not (everybody handling this option knows that), so we are free to use the bit at will. The cache key property is only relevant for requests, anyway? I don't understand what "Cache" means for repeatable options (e.g., Accept). We don't have a Cache-key/non-safe/elective combination. Just luck? I'm not sure I understand the difference between the bits of Uri* and *Uri. It may be necessary to rip apart options where the request usage has different semantics from the response usage. We may need vendor options for all meaningful combinations of bits. I would prefer to have a set bit for "unsafe" instead of "safe" (if we have a bit for "critical" instead of "elective"). If we go this route, we probably should look at all options proposed so far (see the registry table in the SVN) and guess what combinations are how likely. That will enable us to come up with a good encoding. #end #end #end -- ----------------------------------+--------------------- Reporter: zach@… | Owner: zach@… Type: protocol enhancement | Status: new Priority: minor | Milestone: Component: coap | Version: Severity: - | Resolution: Keywords: | ----------------------------------+--------------------- Ticket URL: core From trac+core@trac.tools.ietf.org Mon Jun 11 06:46:51 2012 Return-Path: X-Original-To: core@ietfa.amsl.com Delivered-To: core@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 20DE821F859A for ; Mon, 11 Jun 2012 06:46:51 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -100.849 X-Spam-Level: X-Spam-Status: No, score=-100.849 tagged_above=-999 required=5 tests=[AWL=0.550, BAYES_00=-2.599, J_CHICKENPOX_63=0.6, J_CHICKENPOX_66=0.6, 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 jJ3mkAS9rsIo for ; Mon, 11 Jun 2012 06:46:50 -0700 (PDT) Received: from grenache.tools.ietf.org (grenache.tools.ietf.org [77.72.230.30]) by ietfa.amsl.com (Postfix) with ESMTP id 7A36B21F8599 for ; Mon, 11 Jun 2012 06:46:50 -0700 (PDT) Received: from localhost ([127.0.0.1]:40259 helo=grenache.tools.ietf.org ident=www-data) by grenache.tools.ietf.org with esmtp (Exim 4.77) (envelope-from ) id 1Se4x9-0003AN-Md; Mon, 11 Jun 2012 15:46:43 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit From: "core issue tracker" X-Trac-Version: 0.12.2 Precedence: bulk Auto-Submitted: auto-generated X-Mailer: Trac 0.12.2, by Edgewall Software To: draft-ietf-core-coap@tools.ietf.org, zach@sensinode.com X-Trac-Project: core Date: Mon, 11 Jun 2012 13:46:43 -0000 X-URL: http://tools.ietf.org/core/ X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/core/trac/ticket/213#comment:1 Message-ID: <066.195553014df07d697fa48082bd3761bd@trac.tools.ietf.org> References: <051.f64d92d9c3856bce4b514a7bba1d49af@trac.tools.ietf.org> X-Trac-Ticket-ID: 213 In-Reply-To: <051.f64d92d9c3856bce4b514a7bba1d49af@trac.tools.ietf.org> X-SA-Exim-Connect-IP: 127.0.0.1 X-SA-Exim-Rcpt-To: draft-ietf-core-coap@tools.ietf.org, zach@sensinode.com, core@ietf.org X-SA-Exim-Mail-From: trac+core@trac.tools.ietf.org X-SA-Exim-Scanned: No (on grenache.tools.ietf.org); SAEximRunCond expanded to false Resent-To: Resent-Message-Id: <20120611134650.7A36B21F8599@ietfa.amsl.com> Resent-Date: Mon, 11 Jun 2012 06:46:50 -0700 (PDT) Resent-From: trac+core@trac.tools.ietf.org Cc: core@ietf.org Subject: Re: [core] #213: Path/Query options minimum length X-BeenThere: core@ietf.org X-Mailman-Version: 2.1.12 Reply-To: trac+core@trac.tools.ietf.org List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Jun 2012 13:46:51 -0000 #213: Path/Query options minimum length #choose ticket.new #when True Section 5.10. (Option Definitions) defines the Uri-Path, Uri-Query, Location-Path and Location-Query options to have a minimum length of 1 byte. This is a remnant of the time when each option could be included only at most once instead of for each path segment/query argument individually. Segments and arguments can have a length of zero characters. (RFC 3986 is quite clear that segment = *pchar i.e., a segment can have zero or more pchars. For example, a zero-length path segment is needed to differentiate coap://example.com/a/ from coap://example.com/a ) #end #otherwise #if changes_body Changes (by zach@…): * status: new => closed * resolution: => fixed #end #if changes_descr #if not changes_body and not change.comment and change.author Description changed by zach@…: #end -- #end #if change.comment Comment: Fixed in r688. #end #end #end -- -----------------------------+------------------------------------- Reporter: cabo@… | Owner: draft-ietf-core-coap@… Type: protocol defect | Status: closed Priority: minor | Milestone: post-WGLC-1 Component: coap | Version: coap-09 Severity: In WG Last Call | Resolution: fixed Keywords: | -----------------------------+------------------------------------- Ticket URL: core From trac+core@trac.tools.ietf.org Mon Jun 11 06:47:32 2012 Return-Path: X-Original-To: core@ietfa.amsl.com Delivered-To: core@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 79EAA21F8483 for ; Mon, 11 Jun 2012 06:47:32 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -100.891 X-Spam-Level: X-Spam-Status: No, score=-100.891 tagged_above=-999 required=5 tests=[AWL=0.508, BAYES_00=-2.599, J_CHICKENPOX_63=0.6, J_CHICKENPOX_66=0.6, 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 Hm1vuu259tRR for ; Mon, 11 Jun 2012 06:47:32 -0700 (PDT) Received: from grenache.tools.ietf.org (grenache.tools.ietf.org [77.72.230.30]) by ietfa.amsl.com (Postfix) with ESMTP id C6BAC21F845B for ; Mon, 11 Jun 2012 06:47:31 -0700 (PDT) Received: from localhost ([127.0.0.1]:40323 helo=grenache.tools.ietf.org ident=www-data) by grenache.tools.ietf.org with esmtp (Exim 4.77) (envelope-from ) id 1Se4xt-0001y6-Qj; Mon, 11 Jun 2012 15:47:29 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit From: "core issue tracker" X-Trac-Version: 0.12.2 Precedence: bulk Auto-Submitted: auto-generated X-Mailer: Trac 0.12.2, by Edgewall Software To: hartke@tzi.org, zach@sensinode.com X-Trac-Project: core Date: Mon, 11 Jun 2012 13:47:29 -0000 X-URL: http://tools.ietf.org/core/ X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/core/trac/ticket/226#comment:1 Message-ID: <066.218261c2994efa8d59fe46956c02f495@trac.tools.ietf.org> References: <051.6d1a8fefd2f87314224527d7678c8be2@trac.tools.ietf.org> X-Trac-Ticket-ID: 226 In-Reply-To: <051.6d1a8fefd2f87314224527d7678c8be2@trac.tools.ietf.org> X-SA-Exim-Connect-IP: 127.0.0.1 X-SA-Exim-Rcpt-To: hartke@tzi.org, zach@sensinode.com, core@ietf.org X-SA-Exim-Mail-From: trac+core@trac.tools.ietf.org X-SA-Exim-Scanned: No (on grenache.tools.ietf.org); SAEximRunCond expanded to false Cc: core@ietf.org Subject: Re: [core] #226: Clarify which language addresses intermediaries in general vs. forward proxies specifically X-BeenThere: core@ietf.org X-Mailman-Version: 2.1.12 Reply-To: trac+core@trac.tools.ietf.org List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Jun 2012 13:47:32 -0000 #226: Clarify which language addresses intermediaries in general vs. forward proxies specifically #choose ticket.new #when True Peter van der Stok notes: In section 5.7 paragraph 2 mentions that coap requests to proxies specify the request URI in a different way. I assume that “reverse proxies excepted” needs to be added. -> We need to make a run through the document to find which language is specific e.g. to the use of Proxy-Uri, which language addresses intermediaries in general (and maybe differentiate between CoAP-CoAP intermediaries and protocol mappers), and where specifically CoAP forward proxies (in the sense Fielding uses for proxies) are meant. This is mostly editorial work, but may raise technical points. #end #otherwise #if changes_body Changes (by zach@…): * owner: draft-ietf-core-coap@… => hartke@… #end #if changes_descr #if not changes_body and not change.comment and change.author Description changed by zach@…: #end -- #end #if change.comment Comment: #end #end #end -- -----------------------------+-------------------------- Reporter: cabo@… | Owner: hartke@… Type: other technical | Status: new Priority: major | Milestone: post-WGLC-1 Component: coap | Version: coap-09 Severity: In WG Last Call | Resolution: Keywords: | -----------------------------+-------------------------- Ticket URL: core From trac+core@trac.tools.ietf.org Mon Jun 11 06:48:00 2012 Return-Path: X-Original-To: core@ietfa.amsl.com Delivered-To: core@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D42AD21F859A for ; Mon, 11 Jun 2012 06:48:00 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -100.928 X-Spam-Level: X-Spam-Status: No, score=-100.928 tagged_above=-999 required=5 tests=[AWL=0.471, BAYES_00=-2.599, J_CHICKENPOX_63=0.6, J_CHICKENPOX_66=0.6, 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 7hp7ViQqUKB1 for ; Mon, 11 Jun 2012 06:48:00 -0700 (PDT) Received: from grenache.tools.ietf.org (grenache.tools.ietf.org [77.72.230.30]) by ietfa.amsl.com (Postfix) with ESMTP id 22D1A21F8599 for ; Mon, 11 Jun 2012 06:48:00 -0700 (PDT) Received: from localhost ([127.0.0.1]:40335 helo=grenache.tools.ietf.org ident=www-data) by grenache.tools.ietf.org with esmtp (Exim 4.77) (envelope-from ) id 1Se4yL-0003kH-A6; Mon, 11 Jun 2012 15:47:57 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit From: "core issue tracker" X-Trac-Version: 0.12.2 Precedence: bulk Auto-Submitted: auto-generated X-Mailer: Trac 0.12.2, by Edgewall Software To: cabo@tzi.org, zach@sensinode.com X-Trac-Project: core Date: Mon, 11 Jun 2012 13:47:57 -0000 X-URL: http://tools.ietf.org/core/ X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/core/trac/ticket/215#comment:2 Message-ID: <066.76373a4413a75d64f3553391e8a1be85@trac.tools.ietf.org> References: <051.45ee7476d5dde81710e3ef0e9dc7fb7f@trac.tools.ietf.org> X-Trac-Ticket-ID: 215 In-Reply-To: <051.45ee7476d5dde81710e3ef0e9dc7fb7f@trac.tools.ietf.org> X-SA-Exim-Connect-IP: 127.0.0.1 X-SA-Exim-Rcpt-To: cabo@tzi.org, zach@sensinode.com, core@ietf.org X-SA-Exim-Mail-From: trac+core@trac.tools.ietf.org X-SA-Exim-Scanned: No (on grenache.tools.ietf.org); SAEximRunCond expanded to false Cc: core@ietf.org Subject: Re: [core] #215: editorial issues around Congestion Control X-BeenThere: core@ietf.org X-Mailman-Version: 2.1.12 Reply-To: trac+core@trac.tools.ietf.org List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Jun 2012 13:48:00 -0000 #215: editorial issues around Congestion Control #choose ticket.new #when True Salvatore Loreto notes (http://www.ietf.org/mail- archive/web/core/current/msg03042.html): The section 4.6. Congestion Control needs some editorial work as at moment it talks at the same time of the network congestion control issue and of a mechanism to avoid to overloading a server (suggesting for the latter a similar mechanism to the one used by HTTP). -> The section is indeed entirely about congestion control and not about server load control at all. It may need to be improved to reduce the potential for misunderstanding here. Cullen Jennings (msg03072s, t, u,v) makes a couple of technical points (e.g., he argues that CoAP needs to be more strict about the number of concurrent requests than HTTP is). These are technical issue that need further discussion. Also, Salvatore notes (msg03039) that the reference to draft-eggert-core- congestion-control in 4.5 would point to an expired draft. As 4.5 now has expanded discussion of multicast congestion control, maybe the reference is no longer necessary. It could also be replaced by a copy of the first two paragraphs in section 3.4 of draft-eggert-core-congestion-control (the third paragraph is now covered by material in 4.5 that was not available at the time 3.4 was written). #end #otherwise #if changes_body Changes (by zach@…): * owner: draft-ietf-core-coap@… => cabo@… #end #if changes_descr #if not changes_body and not change.comment and change.author Description changed by zach@…: #end -- #end #if change.comment Comment: #end #end #end -- -----------------------------+-------------------------- Reporter: cabo@… | Owner: cabo@… Type: editorial | Status: new Priority: major | Milestone: post-WGLC-1 Component: coap | Version: coap-09 Severity: In WG Last Call | Resolution: Keywords: | -----------------------------+-------------------------- Ticket URL: core From trac+core@trac.tools.ietf.org Mon Jun 11 06:48:28 2012 Return-Path: X-Original-To: core@ietfa.amsl.com Delivered-To: core@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5EB6121F84FB for ; Mon, 11 Jun 2012 06:48:28 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -100.959 X-Spam-Level: X-Spam-Status: No, score=-100.959 tagged_above=-999 required=5 tests=[AWL=0.440, BAYES_00=-2.599, J_CHICKENPOX_63=0.6, J_CHICKENPOX_66=0.6, 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 hCDd+TA6YWhP for ; Mon, 11 Jun 2012 06:48:28 -0700 (PDT) Received: from grenache.tools.ietf.org (grenache.tools.ietf.org [77.72.230.30]) by ietfa.amsl.com (Postfix) with ESMTP id CE38F21F8599 for ; Mon, 11 Jun 2012 06:48:27 -0700 (PDT) Received: from localhost ([127.0.0.1]:40355 helo=grenache.tools.ietf.org ident=www-data) by grenache.tools.ietf.org with esmtp (Exim 4.77) (envelope-from ) id 1Se4yl-0006HL-9f; Mon, 11 Jun 2012 15:48:23 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit From: "core issue tracker" X-Trac-Version: 0.12.2 Precedence: bulk Auto-Submitted: auto-generated X-Mailer: Trac 0.12.2, by Edgewall Software To: cabo@tzi.org, angelo@castellani.net, zach@sensinode.com X-Trac-Project: core Date: Mon, 11 Jun 2012 13:48:23 -0000 X-URL: http://tools.ietf.org/core/ X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/core/trac/ticket/201#comment:6 Message-ID: <066.052f8435310144389f53dbe1e12a5e3c@trac.tools.ietf.org> References: <051.b90ea2a4caf57d34ab6abdaf3603301a@trac.tools.ietf.org> X-Trac-Ticket-ID: 201 In-Reply-To: <051.b90ea2a4caf57d34ab6abdaf3603301a@trac.tools.ietf.org> X-SA-Exim-Connect-IP: 127.0.0.1 X-SA-Exim-Rcpt-To: cabo@tzi.org, angelo@castellani.net, zach@sensinode.com, core@ietf.org X-SA-Exim-Mail-From: trac+core@trac.tools.ietf.org X-SA-Exim-Scanned: No (on grenache.tools.ietf.org); SAEximRunCond expanded to false Cc: core@ietf.org Subject: Re: [core] #201: Clarify use of retransmission window for duplicate detection X-BeenThere: core@ietf.org X-Mailman-Version: 2.1.12 Reply-To: trac+core@trac.tools.ietf.org List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Jun 2012 13:48:28 -0000 #201: Clarify use of retransmission window for duplicate detection #choose ticket.new #when True A recipient MUST be prepared to receive the same confirmable message (as indicated by the Message ID and additional address information of the corresponding end-point as described in Section 4.3) multiple times, for example, when its acknowledgement went missing or didn't reach the original sender before the first timeout. The recipient Question 2: Should be specified that "the recipient MUST be prepared to receive the same confirmable message *within the potential retransmission window*" as well? #end #otherwise #if changes_body Changes (by zach@…): * owner: draft-ietf-core-coap@… => cabo@… #end #if changes_descr #if not changes_body and not change.comment and change.author Description changed by zach@…: #end -- #end #if change.comment Comment: #end #end #end -- -----------------------------+--------------------- Reporter: cabo@… | Owner: cabo@… Type: editorial | Status: new Priority: minor | Milestone: Component: coap | Version: Severity: In WG Last Call | Resolution: Keywords: | -----------------------------+--------------------- Ticket URL: core From trac+core@trac.tools.ietf.org Mon Jun 11 06:49:07 2012 Return-Path: X-Original-To: core@ietfa.amsl.com Delivered-To: core@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C5BC821F859E for ; Mon, 11 Jun 2012 06:49:07 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -100.987 X-Spam-Level: X-Spam-Status: No, score=-100.987 tagged_above=-999 required=5 tests=[AWL=0.412, BAYES_00=-2.599, J_CHICKENPOX_63=0.6, J_CHICKENPOX_66=0.6, 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 581T6kcKbtwq for ; Mon, 11 Jun 2012 06:49:07 -0700 (PDT) Received: from grenache.tools.ietf.org (grenache.tools.ietf.org [77.72.230.30]) by ietfa.amsl.com (Postfix) with ESMTP id 3063621F848F for ; Mon, 11 Jun 2012 06:49:07 -0700 (PDT) Received: from localhost ([127.0.0.1]:40368 helo=grenache.tools.ietf.org ident=www-data) by grenache.tools.ietf.org with esmtp (Exim 4.77) (envelope-from ) id 1Se4zR-0007vW-Ba; Mon, 11 Jun 2012 15:49:05 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit From: "core issue tracker" X-Trac-Version: 0.12.2 Precedence: bulk Auto-Submitted: auto-generated X-Mailer: Trac 0.12.2, by Edgewall Software To: cabo@tzi.org, zach@sensinode.com X-Trac-Project: core Date: Mon, 11 Jun 2012 13:49:05 -0000 X-URL: http://tools.ietf.org/core/ X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/core/trac/ticket/202#comment:2 Message-ID: <066.94945247bcac2571c3514ff886a47f18@trac.tools.ietf.org> References: <051.e7fbc0f0f5736d305a309a9e8d0cd924@trac.tools.ietf.org> X-Trac-Ticket-ID: 202 In-Reply-To: <051.e7fbc0f0f5736d305a309a9e8d0cd924@trac.tools.ietf.org> X-SA-Exim-Connect-IP: 127.0.0.1 X-SA-Exim-Rcpt-To: cabo@tzi.org, zach@sensinode.com, core@ietf.org X-SA-Exim-Mail-From: trac+core@trac.tools.ietf.org X-SA-Exim-Scanned: No (on grenache.tools.ietf.org); SAEximRunCond expanded to false Cc: core@ietf.org Subject: Re: [core] #202: Remove the 270 byte artificial limit X-BeenThere: core@ietf.org X-Mailman-Version: 2.1.12 Reply-To: trac+core@trac.tools.ietf.org List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Jun 2012 13:49:07 -0000 #202: Remove the 270 byte artificial limit #choose ticket.new #when True For a while, it seemed we had consensus to leave in the artificial limit of 270 bytes for the option length. However, this left a scar on Uri- Proxy, which needed special handling for the rare case where this creates a problem. Matthias Kovatsch has now proposed a simple way to remove the artificial limitation, which is documented in section 2.1 of http://tools.ietf.org/html/draft-bormann-coap-misc-14#section-2.1 This change will also enable the reverting of Uri-Proxy to its natural state of a non-repeatable option. #end #otherwise #if changes_body Changes (by zach@…): * owner: draft-ietf-core-coap@… => cabo@… #end #if changes_descr #if not changes_body and not change.comment and change.author Description changed by zach@…: #end -- #end #if change.comment Comment: #end #end #end -- -----------------------------+--------------------- Reporter: cabo@… | Owner: cabo@… Type: protocol defect | Status: new Priority: minor | Milestone: Component: coap | Version: Severity: In WG Last Call | Resolution: Keywords: | -----------------------------+--------------------- Ticket URL: core From trac+core@trac.tools.ietf.org Mon Jun 11 06:55:59 2012 Return-Path: X-Original-To: core@ietfa.amsl.com Delivered-To: core@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2FD8721F84A0 for ; Mon, 11 Jun 2012 06:55:59 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -101.011 X-Spam-Level: X-Spam-Status: No, score=-101.011 tagged_above=-999 required=5 tests=[AWL=0.388, BAYES_00=-2.599, J_CHICKENPOX_63=0.6, J_CHICKENPOX_66=0.6, 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 G+r8CT4+fjot for ; Mon, 11 Jun 2012 06:55:58 -0700 (PDT) Received: from grenache.tools.ietf.org (grenache.tools.ietf.org [77.72.230.30]) by ietfa.amsl.com (Postfix) with ESMTP id 90C7021F85BD for ; Mon, 11 Jun 2012 06:55:58 -0700 (PDT) Received: from localhost ([127.0.0.1]:40849 helo=grenache.tools.ietf.org ident=www-data) by grenache.tools.ietf.org with esmtp (Exim 4.77) (envelope-from ) id 1Se564-0004FF-Jy; Mon, 11 Jun 2012 15:55:56 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit From: "core issue tracker" X-Trac-Version: 0.12.2 Precedence: bulk Auto-Submitted: auto-generated X-Mailer: Trac 0.12.2, by Edgewall Software To: hartke@tzi.org, cabo@tzi.org, zach@sensinode.com X-Trac-Project: core Date: Mon, 11 Jun 2012 13:55:56 -0000 X-URL: http://tools.ietf.org/core/ X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/core/trac/ticket/218#comment:2 Message-ID: <066.60514d0daad81df1b9194a37c562d420@trac.tools.ietf.org> References: <051.7d815a68bfc98553d3a253f599448da9@trac.tools.ietf.org> X-Trac-Ticket-ID: 218 In-Reply-To: <051.7d815a68bfc98553d3a253f599448da9@trac.tools.ietf.org> X-SA-Exim-Connect-IP: 127.0.0.1 X-SA-Exim-Rcpt-To: hartke@tzi.org, cabo@tzi.org, zach@sensinode.com, core@ietf.org X-SA-Exim-Mail-From: trac+core@trac.tools.ietf.org X-SA-Exim-Scanned: No (on grenache.tools.ietf.org); SAEximRunCond expanded to false Cc: core@ietf.org Subject: Re: [core] #218: Mostly obvious section 5.10.8 fixes X-BeenThere: core@ietf.org X-Mailman-Version: 2.1.12 Reply-To: trac+core@trac.tools.ietf.org List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Jun 2012 13:55:59 -0000 #218: Mostly obvious section 5.10.8 fixes #choose ticket.new #when True Klaus Hartke (msg03034d): Section 5.10.8. (Location-Path and Location-Query) state that the Location-* options describe an "absolute path URI". But if there is only a Location-Query option, there is no path. The section should say that the Location-* options describe a relative URI that consists either of an absolute path, a query string or both, and that is resolved relative to the request target URI. Also: Esko Dijk (msg03057m): Section 5.10.8 “The two options MAY be included in a response to indicate the location of a new resource created with POST.” “the two options MAY” -> this sounds like they have to be included as a pair, which is not the case. Also: Klaus Hartke (msg03034e): Section 5.10.8. (Location-Path and Location-Query) should define that "the value of a Location-Path Option MUST NOT be '.' or '..'." Also: Make sure it is obvious that all the options together indicate *one* Location. (cf. msg03072ba) Also: (Fix grammar of sentence 1 in the process.) #end #otherwise #if changes_body Changes (by zach@…): * status: new => closed * resolution: => fixed #end #if changes_descr #if not changes_body and not change.comment and change.author Description changed by zach@…: #end -- #end #if change.comment Comment: The following fix to r689 was made: {{{ 5.10.8. Location-Path and Location-Query The Location-Path and Location-Query Options together indicate a relative URI Location that consists either of an absolute path, a query string or both, and that is resolved relative to the request target URI. The Location-Path Option is similar to the Uri-Path Option, and the Location-Query Option similar to the Uri-Query Option. The value of a Location-Path Option MUST NOT be '.' or '..'. Any combination of these options MAY be included in a response to indicate the location of a new resource created with POST. If a response with one or more Location-Path and/or Location-Query Options passes through a cache and the implied URI identifies one or more currently stored responses, those entries SHOULD be marked as not fresh. More Location-* options may be defined in the future, and have been reserved option numbers 44, 46 and 48. If any of these reserved option numbers occurs in addition to Location-Path and/or Location- Query and are not supported, then a 4.02 (Bad Option) error MUST be returned. Both options are "elective" and MAY occur one or more times. }}} #end #end #end -- -----------------------------+-------------------------- Reporter: cabo@… | Owner: hartke@… Type: other technical | Status: closed Priority: minor | Milestone: post-WGLC-1 Component: coap | Version: coap-09 Severity: In WG Last Call | Resolution: fixed Keywords: | -----------------------------+-------------------------- Ticket URL: core From trac+core@trac.tools.ietf.org Mon Jun 11 07:12:32 2012 Return-Path: X-Original-To: core@ietfa.amsl.com Delivered-To: core@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E902321F84AF for ; Mon, 11 Jun 2012 07:12:32 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -101.032 X-Spam-Level: X-Spam-Status: No, score=-101.032 tagged_above=-999 required=5 tests=[AWL=0.367, BAYES_00=-2.599, J_CHICKENPOX_63=0.6, J_CHICKENPOX_66=0.6, 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 bVzeHl-hKajy for ; Mon, 11 Jun 2012 07:12:32 -0700 (PDT) Received: from grenache.tools.ietf.org (grenache.tools.ietf.org [77.72.230.30]) by ietfa.amsl.com (Postfix) with ESMTP id 4D21521F84AC for ; Mon, 11 Jun 2012 07:12:32 -0700 (PDT) Received: from localhost ([127.0.0.1]:41699 helo=grenache.tools.ietf.org ident=www-data) by grenache.tools.ietf.org with esmtp (Exim 4.77) (envelope-from ) id 1Se5Lw-0007Oq-Lp; Mon, 11 Jun 2012 16:12:20 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit From: "core issue tracker" X-Trac-Version: 0.12.2 Precedence: bulk Auto-Submitted: auto-generated X-Mailer: Trac 0.12.2, by Edgewall Software To: zach@sensinode.com X-Trac-Project: core Date: Mon, 11 Jun 2012 14:12:20 -0000 X-URL: http://tools.ietf.org/core/ X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/core/trac/ticket/222#comment:1 Message-ID: <072.5c15f1eb583565f73a961f8acff50c7d@trac.tools.ietf.org> References: <057.f44297cd39b3b1ff3294035adc0e7f16@trac.tools.ietf.org> X-Trac-Ticket-ID: 222 In-Reply-To: <057.f44297cd39b3b1ff3294035adc0e7f16@trac.tools.ietf.org> X-SA-Exim-Connect-IP: 127.0.0.1 X-SA-Exim-Rcpt-To: zach@sensinode.com, core@ietf.org X-SA-Exim-Mail-From: trac+core@trac.tools.ietf.org X-SA-Exim-Scanned: No (on grenache.tools.ietf.org); SAEximRunCond expanded to false Cc: core@ietf.org Subject: Re: [core] #222: RawPublicKey identifier X-BeenThere: core@ietf.org X-Mailman-Version: 2.1.12 Reply-To: trac+core@trac.tools.ietf.org List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Jun 2012 14:12:33 -0000 #222: RawPublicKey identifier #choose ticket.new #when True During the IETF-83 CoRE meeting a slide was presented on how to close the RawPublicKey identifier issue in the draft. Out of the three options presented (just use the public key, define it in the CoAP draft, define it in some other draft), there was room consensus to define this in a separate draft. Ari Keränen took an action point to work on this draft with other security people, which has been completed and published here: http://tools.ietf.org/html/draft-farrell-decade-ni-03 This ticket proposes the following changes: 1. Remove Appendix D 2. Add the following text to Section 10.1.2 (contributed by Ari, thanks!): Provisioning in RawPublicKey Mode The RawPublicKey mode was designed to be easily provisioned in M2M deployments. It is assumed that each device has an appropriate asymmetric public key pair installed. An identifier is calculated from the public key as described in Section 2 of [draft-ni]. All implementations that support checking RawPublicKey identities MUST support at least the sha-256-120 mode (SHA-256 truncated to 120 bits). Implementations SHOULD support also longer length identifiers and MAY support shorter lengths. Note that the shorter lengths provide less security against attacks and their use is NOT RECOMMENDED. Depending on how identifiers are given to the system that verifies them, support for URI, binary, and/or human-readable format [draft-ni] needs to be implemented. All implementations SHOULD support the binary mode and implementations that have a user interface SHOULD also support the human-readable format. During provisioning, the identifier of each node is collected, for example by reading a barcode on the outside of the device or by obtaining a pre-compiled list of the identifiers. These identifiers are then installed in the corresponding end-point, for example an M2M data collection server. The identifier is used for two purposes, to associate the end-point with further device information and to perform access control. During provisioning, an access control list of identifiers the device may start DTLS sessions with SHOULD also be installed. #end #otherwise #if changes_body Changes (by zach@…): #end #if changes_descr #if not changes_body and not change.comment and change.author Description changed by zach@…: #end -- #end #if change.comment Comment(by zach@…): Done in r690. #end #end #end -- ----------------------------------+--------------------- Reporter: zach@… | Owner: zach@… Type: protocol enhancement | Status: new Priority: minor | Milestone: Component: coap | Version: Severity: - | Resolution: Keywords: | ----------------------------------+--------------------- Ticket URL: core From trac+core@trac.tools.ietf.org Mon Jun 11 07:12:34 2012 Return-Path: X-Original-To: core@ietfa.amsl.com Delivered-To: core@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5B54B21F84AC for ; Mon, 11 Jun 2012 07:12:34 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -101.052 X-Spam-Level: X-Spam-Status: No, score=-101.052 tagged_above=-999 required=5 tests=[AWL=0.347, BAYES_00=-2.599, J_CHICKENPOX_63=0.6, J_CHICKENPOX_66=0.6, 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 DXf+nukUq-5p for ; Mon, 11 Jun 2012 07:12:33 -0700 (PDT) Received: from grenache.tools.ietf.org (grenache.tools.ietf.org [77.72.230.30]) by ietfa.amsl.com (Postfix) with ESMTP id A2AAF21F8493 for ; Mon, 11 Jun 2012 07:12:33 -0700 (PDT) Received: from localhost ([127.0.0.1]:41704 helo=grenache.tools.ietf.org ident=www-data) by grenache.tools.ietf.org with esmtp (Exim 4.77) (envelope-from ) id 1Se5M3-00011A-2K; Mon, 11 Jun 2012 16:12:27 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit From: "core issue tracker" X-Trac-Version: 0.12.2 Precedence: bulk Auto-Submitted: auto-generated X-Mailer: Trac 0.12.2, by Edgewall Software To: zach@sensinode.com X-Trac-Project: core Date: Mon, 11 Jun 2012 14:12:27 -0000 X-URL: http://tools.ietf.org/core/ X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/core/trac/ticket/222#comment:2 Message-ID: <072.426c6dda93961573d9f7639d914d6786@trac.tools.ietf.org> References: <057.f44297cd39b3b1ff3294035adc0e7f16@trac.tools.ietf.org> X-Trac-Ticket-ID: 222 In-Reply-To: <057.f44297cd39b3b1ff3294035adc0e7f16@trac.tools.ietf.org> X-SA-Exim-Connect-IP: 127.0.0.1 X-SA-Exim-Rcpt-To: zach@sensinode.com, core@ietf.org X-SA-Exim-Mail-From: trac+core@trac.tools.ietf.org X-SA-Exim-Scanned: No (on grenache.tools.ietf.org); SAEximRunCond expanded to false Cc: core@ietf.org Subject: Re: [core] #222: RawPublicKey identifier X-BeenThere: core@ietf.org X-Mailman-Version: 2.1.12 Reply-To: trac+core@trac.tools.ietf.org List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Jun 2012 14:12:34 -0000 #222: RawPublicKey identifier #choose ticket.new #when True During the IETF-83 CoRE meeting a slide was presented on how to close the RawPublicKey identifier issue in the draft. Out of the three options presented (just use the public key, define it in the CoAP draft, define it in some other draft), there was room consensus to define this in a separate draft. Ari Keränen took an action point to work on this draft with other security people, which has been completed and published here: http://tools.ietf.org/html/draft-farrell-decade-ni-03 This ticket proposes the following changes: 1. Remove Appendix D 2. Add the following text to Section 10.1.2 (contributed by Ari, thanks!): Provisioning in RawPublicKey Mode The RawPublicKey mode was designed to be easily provisioned in M2M deployments. It is assumed that each device has an appropriate asymmetric public key pair installed. An identifier is calculated from the public key as described in Section 2 of [draft-ni]. All implementations that support checking RawPublicKey identities MUST support at least the sha-256-120 mode (SHA-256 truncated to 120 bits). Implementations SHOULD support also longer length identifiers and MAY support shorter lengths. Note that the shorter lengths provide less security against attacks and their use is NOT RECOMMENDED. Depending on how identifiers are given to the system that verifies them, support for URI, binary, and/or human-readable format [draft-ni] needs to be implemented. All implementations SHOULD support the binary mode and implementations that have a user interface SHOULD also support the human-readable format. During provisioning, the identifier of each node is collected, for example by reading a barcode on the outside of the device or by obtaining a pre-compiled list of the identifiers. These identifiers are then installed in the corresponding end-point, for example an M2M data collection server. The identifier is used for two purposes, to associate the end-point with further device information and to perform access control. During provisioning, an access control list of identifiers the device may start DTLS sessions with SHOULD also be installed. #end #otherwise #if changes_body Changes (by zach@…): * status: new => closed * resolution: => fixed #end #if changes_descr #if not changes_body and not change.comment and change.author Description changed by zach@…: #end -- #end #if change.comment Comment: #end #end #end -- ----------------------------------+--------------------- Reporter: zach@… | Owner: zach@… Type: protocol enhancement | Status: closed Priority: minor | Milestone: Component: coap | Version: Severity: - | Resolution: fixed Keywords: | ----------------------------------+--------------------- Ticket URL: core From trac+core@trac.tools.ietf.org Mon Jun 11 07:14:03 2012 Return-Path: X-Original-To: core@ietfa.amsl.com Delivered-To: core@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E81FD21F85C0 for ; Mon, 11 Jun 2012 07:14:02 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -101.069 X-Spam-Level: X-Spam-Status: No, score=-101.069 tagged_above=-999 required=5 tests=[AWL=0.330, BAYES_00=-2.599, J_CHICKENPOX_63=0.6, J_CHICKENPOX_66=0.6, 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 TQS5b3oOCCNk for ; Mon, 11 Jun 2012 07:14:02 -0700 (PDT) Received: from grenache.tools.ietf.org (grenache.tools.ietf.org [77.72.230.30]) by ietfa.amsl.com (Postfix) with ESMTP id 0FAD721F84AC for ; Mon, 11 Jun 2012 07:14:02 -0700 (PDT) Received: from localhost ([127.0.0.1]:41731 helo=grenache.tools.ietf.org ident=www-data) by grenache.tools.ietf.org with esmtp (Exim 4.77) (envelope-from ) id 1Se5NY-0007eJ-08; Mon, 11 Jun 2012 16:14:00 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit From: "core issue tracker" X-Trac-Version: 0.12.2 Precedence: bulk Auto-Submitted: auto-generated X-Mailer: Trac 0.12.2, by Edgewall Software To: hartke@tzi.org, zach@sensinode.com X-Trac-Project: core Date: Mon, 11 Jun 2012 14:13:59 -0000 X-URL: http://tools.ietf.org/core/ X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/core/trac/ticket/228#comment:1 Message-ID: <068.c42a8f8d3011c2aa3873b169e0c24d6f@trac.tools.ietf.org> References: <053.14c1896b5eae7fbbc5ad1a8f77d383ce@trac.tools.ietf.org> X-Trac-Ticket-ID: 228 In-Reply-To: <053.14c1896b5eae7fbbc5ad1a8f77d383ce@trac.tools.ietf.org> X-SA-Exim-Connect-IP: 127.0.0.1 X-SA-Exim-Rcpt-To: hartke@tzi.org, zach@sensinode.com, core@ietf.org X-SA-Exim-Mail-From: trac+core@trac.tools.ietf.org X-SA-Exim-Scanned: No (on grenache.tools.ietf.org); SAEximRunCond expanded to false Cc: core@ietf.org Subject: Re: [core] #228: Proxying of multicast requests X-BeenThere: core@ietf.org X-Mailman-Version: 2.1.12 Reply-To: trac+core@trac.tools.ietf.org List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Jun 2012 14:14:03 -0000 #228: Proxying of multicast requests #choose ticket.new #when True Esko Dijk notes (msg03065): In Section 5.7 (Proxying) the possibility of a multicast request in the Proxy-Uri is not explicitly considered. Should we mention this possibility? (If yes, do we need to update/adapt our caching text to include the multicast case?) -> Create a multicast section, between section 9 and 10 with the existing content of section 4.5 and the following additional rules: * When a new Proxy-Uri multicast request comes in, the proxy always makes a new request to the multicast group (since there may be new group members that joined meanwhile or ones that did not get the previous request). It MAY update the cache with the received responses. Then it sends all responses (both cached-still-fresh and 'new') back to the original client. * A response received in reply to a GET request to a multicast group MAY be used to satisfy a subsequent request on the related unicast request URI. [Only for the AllCoapServers multicast group?] The unicast request URI is obtained by replacing the authority part of the request URI with the transport layer source address of the response message. [Overridden by a Content-Location option?] * A cache MAY revalidate a response by making a GET request on the related unicast request URI. * A GET request to a multicast group MUST NOT contain an ETag option. ---- Carsten Bormann notes (msg03272): One thing we are missing to make this more useful is a way to suppress responses the client already has. For unicast, we do some of this with ETags, but these are in a namespace made up by each server, so they don't mean anything for a multicast group as a whole. For multicast, we'd have to list pairs of authorities and ETags. Obviously, these lists can become big quickly. -> Add a note that this spec does not yet define a suppression mechanism ("left for further study" would be the CCITT term :-). #end #otherwise #if changes_body Changes (by zach@…): * owner: draft-ietf-core-coap@… => hartke@… #end #if changes_descr #if not changes_body and not change.comment and change.author Description changed by zach@…: #end -- #end #if change.comment Comment: #end #end #end -- ----------------------------------+-------------------------- Reporter: hartke@… | Owner: hartke@… Type: protocol enhancement | Status: new Priority: minor | Milestone: post-WGLC-1 Component: coap | Version: coap-09 Severity: In WG Last Call | Resolution: Keywords: | ----------------------------------+-------------------------- Ticket URL: core From trac+core@trac.tools.ietf.org Mon Jun 11 07:32:18 2012 Return-Path: X-Original-To: core@ietfa.amsl.com Delivered-To: core@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CA7B821F848B for ; Mon, 11 Jun 2012 07:32:18 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -101.085 X-Spam-Level: X-Spam-Status: No, score=-101.085 tagged_above=-999 required=5 tests=[AWL=0.314, BAYES_00=-2.599, J_CHICKENPOX_63=0.6, J_CHICKENPOX_66=0.6, 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 bhxSXI0jonfk for ; Mon, 11 Jun 2012 07:32:18 -0700 (PDT) Received: from grenache.tools.ietf.org (grenache.tools.ietf.org [77.72.230.30]) by ietfa.amsl.com (Postfix) with ESMTP id 4849121F8480 for ; Mon, 11 Jun 2012 07:32:18 -0700 (PDT) Received: from localhost ([127.0.0.1]:42683 helo=grenache.tools.ietf.org ident=www-data) by grenache.tools.ietf.org with esmtp (Exim 4.77) (envelope-from ) id 1Se5f3-00072J-T4; Mon, 11 Jun 2012 16:32:05 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit From: "core issue tracker" X-Trac-Version: 0.12.2 Precedence: bulk Auto-Submitted: auto-generated X-Mailer: Trac 0.12.2, by Edgewall Software To: draft-ietf-core-coap@tools.ietf.org, zach@sensinode.com X-Trac-Project: core Date: Mon, 11 Jun 2012 14:32:05 -0000 X-URL: http://tools.ietf.org/core/ X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/core/trac/ticket/229#comment:1 Message-ID: <068.9b1351ae636f1e35ded1443a5cc3de14@trac.tools.ietf.org> References: <053.ce983dd14dc89fbf38d56d60d83000f0@trac.tools.ietf.org> X-Trac-Ticket-ID: 229 In-Reply-To: <053.ce983dd14dc89fbf38d56d60d83000f0@trac.tools.ietf.org> X-SA-Exim-Connect-IP: 127.0.0.1 X-SA-Exim-Rcpt-To: draft-ietf-core-coap@tools.ietf.org, zach@sensinode.com, core@ietf.org X-SA-Exim-Mail-From: trac+core@trac.tools.ietf.org X-SA-Exim-Scanned: No (on grenache.tools.ietf.org); SAEximRunCond expanded to false Resent-To: Resent-Message-Id: <20120611143218.4849121F8480@ietfa.amsl.com> Resent-Date: Mon, 11 Jun 2012 07:32:18 -0700 (PDT) Resent-From: trac+core@trac.tools.ietf.org Cc: core@ietf.org Subject: Re: [core] #229: Move sections 10-10.2. out of the "Security Considerations" X-BeenThere: core@ietf.org X-Mailman-Version: 2.1.12 Reply-To: trac+core@trac.tools.ietf.org List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Jun 2012 14:32:18 -0000 #229: Move sections 10-10.2. out of the "Security Considerations" #choose ticket.new #when True Ari Keränen notes (msg03157p): I'd consider moving sections 10-10.2. out of the "Security Considerations" and into a section of their own (called something like "Securing CoAP") and make just the section 10.3. the Security Considerations. The text in 10-10.2. looks like "regular specification text" whereas 10.3. is what I'd expect to see in Security Considerations. #end #otherwise #if changes_body Changes (by zach@…): * status: new => closed * resolution: => fixed #end #if changes_descr #if not changes_body and not change.comment and change.author Description changed by zach@…: #end -- #end #if change.comment Comment: Done in r691. #end #end #end -- -----------------------------+------------------------------------- Reporter: hartke@… | Owner: draft-ietf-core-coap@… Type: editorial | Status: closed Priority: minor | Milestone: post-WGLC-1 Component: coap | Version: coap-09 Severity: In WG Last Call | Resolution: fixed Keywords: | -----------------------------+------------------------------------- Ticket URL: core From trac+core@trac.tools.ietf.org Mon Jun 11 07:36:41 2012 Return-Path: X-Original-To: core@ietfa.amsl.com Delivered-To: core@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 89C7021F8655 for ; Mon, 11 Jun 2012 07:36:41 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -101.099 X-Spam-Level: X-Spam-Status: No, score=-101.099 tagged_above=-999 required=5 tests=[AWL=0.300, BAYES_00=-2.599, J_CHICKENPOX_63=0.6, J_CHICKENPOX_66=0.6, 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 72zqmVJi2mP3 for ; Mon, 11 Jun 2012 07:36:40 -0700 (PDT) Received: from grenache.tools.ietf.org (grenache.tools.ietf.org [77.72.230.30]) by ietfa.amsl.com (Postfix) with ESMTP id 8C63321F8658 for ; Mon, 11 Jun 2012 07:36:40 -0700 (PDT) Received: from localhost ([127.0.0.1]:42845 helo=grenache.tools.ietf.org ident=www-data) by grenache.tools.ietf.org with esmtp (Exim 4.77) (envelope-from ) id 1Se5jQ-0006Yi-Bo; Mon, 11 Jun 2012 16:36:36 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit From: "core issue tracker" X-Trac-Version: 0.12.2 Precedence: bulk Auto-Submitted: auto-generated X-Mailer: Trac 0.12.2, by Edgewall Software To: hartke@tzi.org, zach@sensinode.com X-Trac-Project: core Date: Mon, 11 Jun 2012 14:36:36 -0000 X-URL: http://tools.ietf.org/core/ X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/core/trac/ticket/231#comment:1 Message-ID: <068.899e864a5cd86d050c98535bb6d8b8bb@trac.tools.ietf.org> References: <053.23dacbfaca0136062ef666c59397aee9@trac.tools.ietf.org> X-Trac-Ticket-ID: 231 In-Reply-To: <053.23dacbfaca0136062ef666c59397aee9@trac.tools.ietf.org> X-SA-Exim-Connect-IP: 127.0.0.1 X-SA-Exim-Rcpt-To: hartke@tzi.org, zach@sensinode.com, core@ietf.org X-SA-Exim-Mail-From: trac+core@trac.tools.ietf.org X-SA-Exim-Scanned: No (on grenache.tools.ietf.org); SAEximRunCond expanded to false Cc: core@ietf.org Subject: Re: [core] #231: Splitting/combining Location options X-BeenThere: core@ietf.org X-Mailman-Version: 2.1.12 Reply-To: trac+core@trac.tools.ietf.org List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Jun 2012 14:36:41 -0000 #231: Splitting/combining Location options #choose ticket.new #when True Klaus Hartke asks (msg03034f): Should there be text on combining the Location-* options into a relative URI, and splitting an URI into Location-* options? Sections 6.4 and 6.5 currently do not apply, and the steps are slightly different (the Location-* options describe a relative URI, not an absolute URI like the Uri-* options). #end #otherwise #if changes_body Changes (by zach@…): * owner: draft-ietf-core-coap@… => hartke@… #end #if changes_descr #if not changes_body and not change.comment and change.author Description changed by zach@…: #end -- #end #if change.comment Comment: #end #end #end -- -----------------------------+-------------------------- Reporter: hartke@… | Owner: hartke@… Type: other technical | Status: new Priority: minor | Milestone: post-WGLC-1 Component: coap | Version: coap-09 Severity: In WG Last Call | Resolution: Keywords: | -----------------------------+-------------------------- Ticket URL: core From trac+core@trac.tools.ietf.org Mon Jun 11 07:47:07 2012 Return-Path: X-Original-To: core@ietfa.amsl.com Delivered-To: core@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3D76221F8629 for ; Mon, 11 Jun 2012 07:47:07 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -101.112 X-Spam-Level: X-Spam-Status: No, score=-101.112 tagged_above=-999 required=5 tests=[AWL=0.287, BAYES_00=-2.599, J_CHICKENPOX_63=0.6, J_CHICKENPOX_66=0.6, 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 eyhsD4BAm9ik for ; Mon, 11 Jun 2012 07:47:06 -0700 (PDT) Received: from grenache.tools.ietf.org (grenache.tools.ietf.org [77.72.230.30]) by ietfa.amsl.com (Postfix) with ESMTP id 91EC721F861D for ; Mon, 11 Jun 2012 07:47:06 -0700 (PDT) Received: from localhost ([127.0.0.1]:43180 helo=grenache.tools.ietf.org ident=www-data) by grenache.tools.ietf.org with esmtp (Exim 4.77) (envelope-from ) id 1Se5tL-0006R6-IT; Mon, 11 Jun 2012 16:46:51 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit From: "core issue tracker" X-Trac-Version: 0.12.2 Precedence: bulk Auto-Submitted: auto-generated X-Mailer: Trac 0.12.2, by Edgewall Software To: draft-ietf-core-coap@tools.ietf.org, cabo@tzi.org, zach@sensinode.com X-Trac-Project: core Date: Mon, 11 Jun 2012 14:46:51 -0000 X-URL: http://tools.ietf.org/core/ X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/core/trac/ticket/232#comment:3 Message-ID: <068.15cfa94c5a47b1e83b40e00488c42883@trac.tools.ietf.org> References: <053.8004f0cc0b270920cdf2b55b6caf2b79@trac.tools.ietf.org> X-Trac-Ticket-ID: 232 In-Reply-To: <053.8004f0cc0b270920cdf2b55b6caf2b79@trac.tools.ietf.org> X-SA-Exim-Connect-IP: 127.0.0.1 X-SA-Exim-Rcpt-To: draft-ietf-core-coap@tools.ietf.org, cabo@tzi.org, zach@sensinode.com, core@ietf.org X-SA-Exim-Mail-From: trac+core@trac.tools.ietf.org X-SA-Exim-Scanned: No (on grenache.tools.ietf.org); SAEximRunCond expanded to false Resent-To: Resent-Message-Id: <20120611144706.91EC721F861D@ietfa.amsl.com> Resent-Date: Mon, 11 Jun 2012 07:47:06 -0700 (PDT) Resent-From: trac+core@trac.tools.ietf.org Cc: core@ietf.org Subject: Re: [core] #232: Clarify inclusion of Location options in a 2.01 (Created) response X-BeenThere: core@ietf.org X-Mailman-Version: 2.1.12 Reply-To: trac+core@trac.tools.ietf.org List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Jun 2012 14:47:07 -0000 #232: Clarify inclusion of Location options in a 2.01 (Created) response #choose ticket.new #when True Esko Dijk notes (msg03057l): Section 5.8.2. If a resource has been created on the server, a 2.01 (Created) response that includes the URI of the new resource in a sequence of one or more Location-Path and/or Location-Query Options SHOULD be returned. While section 5.10.8 defines this optional: The two options MAY be included in a response to indicate the location of a new resource created with POST. Should 5.8.2. refer to 5.10.8 to define the right behaviour (to avoid double definitions) ? #end #otherwise #if changes_body Changes (by zach@…): * status: new => closed * resolution: => fixed #end #if changes_descr #if not changes_body and not change.comment and change.author Description changed by zach@…: #end -- #end #if change.comment Comment: Done in r692. 5.8.2 now reads: {{{ 5.8.2. POST The POST method requests that the representation enclosed in the request be processed. The actual function performed by the POST method is determined by the origin server and dependent on the target resource. It usually results in a new resource being created or the target resource being updated. If a resource has been created on the server, a 2.01 (Created) response MAY be returned, which may include the URI of the new resource in a sequence of one or more Location-Path and/or Location- Query Options (Section 5.9.1.1 and Section 5.10.8). If the POST succeeds but does not result in a new resource being created on the server, a 2.04 (Changed) response SHOULD be returned. If the POST succeeds and results in the target resource being deleted, a 2.02 (Deleted) response SHOULD be returned. POST is neither safe nor idempotent. }}} #end #end #end -- -----------------------------+------------------------------------- Reporter: hartke@… | Owner: draft-ietf-core-coap@… Type: editorial | Status: closed Priority: minor | Milestone: post-WGLC-1 Component: coap | Version: coap-09 Severity: In WG Last Call | Resolution: fixed Keywords: | -----------------------------+------------------------------------- Ticket URL: core From trac+core@trac.tools.ietf.org Mon Jun 11 07:47:55 2012 Return-Path: X-Original-To: core@ietfa.amsl.com Delivered-To: core@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 637B421F8611 for ; Mon, 11 Jun 2012 07:47:55 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -101.124 X-Spam-Level: X-Spam-Status: No, score=-101.124 tagged_above=-999 required=5 tests=[AWL=0.275, BAYES_00=-2.599, J_CHICKENPOX_63=0.6, J_CHICKENPOX_66=0.6, 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 I2VPs8V4EUlD for ; Mon, 11 Jun 2012 07:47:54 -0700 (PDT) Received: from grenache.tools.ietf.org (grenache.tools.ietf.org [77.72.230.30]) by ietfa.amsl.com (Postfix) with ESMTP id 6D8EF21F855D for ; Mon, 11 Jun 2012 07:47:54 -0700 (PDT) Received: from localhost ([127.0.0.1]:43238 helo=grenache.tools.ietf.org ident=www-data) by grenache.tools.ietf.org with esmtp (Exim 4.77) (envelope-from ) id 1Se5uJ-0002Z5-1J; Mon, 11 Jun 2012 16:47:51 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit From: "core issue tracker" X-Trac-Version: 0.12.2 Precedence: bulk Auto-Submitted: auto-generated X-Mailer: Trac 0.12.2, by Edgewall Software To: cabo@tzi.org, zach@sensinode.com X-Trac-Project: core Date: Mon, 11 Jun 2012 14:47:51 -0000 X-URL: http://tools.ietf.org/core/ X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/core/trac/ticket/239#comment:1 Message-ID: <066.f29cb900a8c288de16c19f334fc474b9@trac.tools.ietf.org> References: <051.0d383e737d0490ef1635d6073da7c1c7@trac.tools.ietf.org> X-Trac-Ticket-ID: 239 In-Reply-To: <051.0d383e737d0490ef1635d6073da7c1c7@trac.tools.ietf.org> X-SA-Exim-Connect-IP: 127.0.0.1 X-SA-Exim-Rcpt-To: cabo@tzi.org, zach@sensinode.com, core@ietf.org X-SA-Exim-Mail-From: trac+core@trac.tools.ietf.org X-SA-Exim-Scanned: No (on grenache.tools.ietf.org); SAEximRunCond expanded to false Cc: core@ietf.org Subject: Re: [core] #239: Always reserve option delta 15 X-BeenThere: core@ietf.org X-Mailman-Version: 2.1.12 Reply-To: trac+core@trac.tools.ietf.org List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Jun 2012 14:47:55 -0000 #239: Always reserve option delta 15 #choose ticket.new #when True Cullen Jennings notes (msg03072j): Section 3.1 Having the a option delta of 15 mean different things based on if the Option Count Field is 0 or not just seems it adds complexity and bugs not worth the small compression gain. -> (substitute 15 for 0 in the above) For simplicity, we should always only use option deltas from 0 to 14, independent of whether we need the option terminator or not. #end #otherwise #if changes_body Changes (by zach@…): * owner: draft-ietf-core-coap@… => cabo@… #end #if changes_descr #if not changes_body and not change.comment and change.author Description changed by zach@…: #end -- #end #if change.comment Comment: #end #end #end -- -----------------------------+-------------------------- Reporter: cabo@… | Owner: cabo@… Type: other technical | Status: new Priority: minor | Milestone: post-WGLC-1 Component: coap | Version: coap-09 Severity: In WG Last Call | Resolution: Keywords: | -----------------------------+-------------------------- Ticket URL: core From trac+core@trac.tools.ietf.org Mon Jun 11 07:53:54 2012 Return-Path: X-Original-To: core@ietfa.amsl.com Delivered-To: core@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2A36221F8582 for ; Mon, 11 Jun 2012 07:53:54 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -101.135 X-Spam-Level: X-Spam-Status: No, score=-101.135 tagged_above=-999 required=5 tests=[AWL=0.264, BAYES_00=-2.599, J_CHICKENPOX_63=0.6, J_CHICKENPOX_66=0.6, 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 pGdBnOi74Gea for ; Mon, 11 Jun 2012 07:53:53 -0700 (PDT) Received: from grenache.tools.ietf.org (grenache.tools.ietf.org [77.72.230.30]) by ietfa.amsl.com (Postfix) with ESMTP id 8578821F8573 for ; Mon, 11 Jun 2012 07:53:53 -0700 (PDT) Received: from localhost ([127.0.0.1]:43505 helo=grenache.tools.ietf.org ident=www-data) by grenache.tools.ietf.org with esmtp (Exim 4.77) (envelope-from ) id 1Se5zz-0008K0-NN; Mon, 11 Jun 2012 16:53:43 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit From: "core issue tracker" X-Trac-Version: 0.12.2 Precedence: bulk Auto-Submitted: auto-generated X-Mailer: Trac 0.12.2, by Edgewall Software To: draft-ietf-core-coap@tools.ietf.org, zach@sensinode.com X-Trac-Project: core Date: Mon, 11 Jun 2012 14:53:43 -0000 X-URL: http://tools.ietf.org/core/ X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/core/trac/ticket/233#comment:1 Message-ID: <068.e2bc2c04db89134f12dbacf724e9c2f1@trac.tools.ietf.org> References: <053.d09b6a2d0cd19cbc2c7c40c535bc4077@trac.tools.ietf.org> X-Trac-Ticket-ID: 233 In-Reply-To: <053.d09b6a2d0cd19cbc2c7c40c535bc4077@trac.tools.ietf.org> X-SA-Exim-Connect-IP: 127.0.0.1 X-SA-Exim-Rcpt-To: draft-ietf-core-coap@tools.ietf.org, zach@sensinode.com, core@ietf.org X-SA-Exim-Mail-From: trac+core@trac.tools.ietf.org X-SA-Exim-Scanned: No (on grenache.tools.ietf.org); SAEximRunCond expanded to false Resent-To: Resent-Message-Id: <20120611145353.8578821F8573@ietfa.amsl.com> Resent-Date: Mon, 11 Jun 2012 07:53:53 -0700 (PDT) Resent-From: trac+core@trac.tools.ietf.org Cc: core@ietf.org Subject: Re: [core] #233: Response codes with payload inconsistency X-BeenThere: core@ietf.org X-Mailman-Version: 2.1.12 Reply-To: trac+core@trac.tools.ietf.org List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Jun 2012 14:53:54 -0000 #233: Response codes with payload inconsistency #choose ticket.new #when True Section 5.5, first paragraph: The response codes with payload are 2.05 (Content) and the error codes. But a few paragraphs later: 2.01 (Created), 2.02 (Deleted), 2.04 (Changed) MAY include payload -> The first paragraph needs to be fixed. ---- Ari Keränen notes: 2.01 (Created), 2.02 (Deleted), 2.04 (Changed) MAY include payload Change to "Responses with code [...]" #end #otherwise #if changes_body Changes (by zach@…): * status: new => closed * resolution: => fixed #end #if changes_descr #if not changes_body and not change.comment and change.author Description changed by zach@…: #end -- #end #if change.comment Comment: Done in r693. #end #end #end -- -----------------------------+------------------------------------- Reporter: hartke@… | Owner: draft-ietf-core-coap@… Type: editorial | Status: closed Priority: trivial | Milestone: post-WGLC-1 Component: coap | Version: coap-09 Severity: In WG Last Call | Resolution: fixed Keywords: | -----------------------------+------------------------------------- Ticket URL: core From hartke@tzi.org Mon Jun 11 08:07:14 2012 Return-Path: X-Original-To: core@ietfa.amsl.com Delivered-To: core@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E728821F864E for ; Mon, 11 Jun 2012 08:07:14 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.627 X-Spam-Level: X-Spam-Status: No, score=-5.627 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-4] 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 pln6v6D4vuoF for ; Mon, 11 Jun 2012 08:07:14 -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 309F321F8630 for ; Mon, 11 Jun 2012 08:07:14 -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.3/8.14.3) with ESMTP id q5BF7725006308 for ; Mon, 11 Jun 2012 17:07:07 +0200 (CEST) Received: from mail-vc0-f172.google.com (mail-vc0-f172.google.com [209.85.220.172]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id E9FE9FA5 for ; Mon, 11 Jun 2012 17:07:06 +0200 (CEST) Received: by vcqp1 with SMTP id p1so2623622vcq.31 for ; Mon, 11 Jun 2012 08:07:05 -0700 (PDT) MIME-Version: 1.0 Received: by 10.220.154.130 with SMTP id o2mr12732113vcw.57.1339427225596; Mon, 11 Jun 2012 08:07:05 -0700 (PDT) Received: by 10.220.223.12 with HTTP; Mon, 11 Jun 2012 08:07:05 -0700 (PDT) In-Reply-To: <068.e2bc2c04db89134f12dbacf724e9c2f1@trac.tools.ietf.org> References: <053.d09b6a2d0cd19cbc2c7c40c535bc4077@trac.tools.ietf.org> <068.e2bc2c04db89134f12dbacf724e9c2f1@trac.tools.ietf.org> Date: Mon, 11 Jun 2012 17:07:05 +0200 Message-ID: From: Klaus Hartke To: zach@sensinode.com Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: core@ietf.org Subject: Re: [core] #233: Response codes with payload inconsistency X-BeenThere: core@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Jun 2012 15:07:15 -0000 > =A0Done in r693. > - POST, and the response codes with payload are 2.05 (Content) and the er= ror > - codes. > + POST, and the response codes with payload are 2.01 (Created), 2.02 > + (Deleted), 2.04 (Changed) and the error codes. 2.05 (Content) can have payload as well. Klaus From hartke@tzi.org Mon Jun 11 08:08:01 2012 Return-Path: X-Original-To: core@ietfa.amsl.com Delivered-To: core@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D596B21F8565 for ; Mon, 11 Jun 2012 08:08:01 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.627 X-Spam-Level: X-Spam-Status: No, score=-5.627 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-4] 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 DhBda18wrhUV for ; Mon, 11 Jun 2012 08:08:01 -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 2F92A21F8522 for ; Mon, 11 Jun 2012 08:08:01 -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.3/8.14.3) with ESMTP id q5BF7sPj006947 for ; Mon, 11 Jun 2012 17:07:54 +0200 (CEST) Received: from mail-vc0-f172.google.com (mail-vc0-f172.google.com [209.85.220.172]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id F3C2BFA8 for ; Mon, 11 Jun 2012 17:07:53 +0200 (CEST) Received: by vcqp1 with SMTP id p1so2624348vcq.31 for ; Mon, 11 Jun 2012 08:07:52 -0700 (PDT) MIME-Version: 1.0 Received: by 10.52.100.4 with SMTP id eu4mr10734075vdb.66.1339427272789; Mon, 11 Jun 2012 08:07:52 -0700 (PDT) Received: by 10.220.223.12 with HTTP; Mon, 11 Jun 2012 08:07:52 -0700 (PDT) In-Reply-To: <066.c5662d2812b84c6351b5de2c5108b774@trac.tools.ietf.org> References: <051.4e6cdfc507a23a9b28c6274a5b955113@trac.tools.ietf.org> <066.c5662d2812b84c6351b5de2c5108b774@trac.tools.ietf.org> Date: Mon, 11 Jun 2012 17:07:52 +0200 Message-ID: From: Klaus Hartke To: zach@sensinode.com Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: core@ietf.org Subject: Re: [core] #212: Option numbers 14, 28, 42, ... reserved but usable X-BeenThere: core@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Jun 2012 15:08:01 -0000 > =A0Done in r687. > - Option Numbers 14, 28, 42, ... are reserved for no-op options > - when they are sent with an empty value (they are ignored) > - and can be used as "fenceposts" if > + Option Numbers 14, 28, 42, ... are reserved > + for no-op options when they are sent with an empty value > + (they are ignored) and can be used as "fenceposts" if The point is that these options are not reserved at all. There are just some constraints in their definition. Klaus From sye.loong.keoh@philips.com Mon Jun 11 09:12:39 2012 Return-Path: X-Original-To: core@ietfa.amsl.com Delivered-To: core@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E036221F855E for ; Mon, 11 Jun 2012 09:12:39 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.599 X-Spam-Level: X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1] 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 yM24tDJYB6Ss for ; Mon, 11 Jun 2012 09:12:39 -0700 (PDT) Received: from ch1outboundpool.messaging.microsoft.com (ch1ehsobe003.messaging.microsoft.com [216.32.181.183]) by ietfa.amsl.com (Postfix) with ESMTP id C201121F859A for ; Mon, 11 Jun 2012 09:12:38 -0700 (PDT) Received: from mail71-ch1-R.bigfish.com (10.43.68.227) by CH1EHSOBE009.bigfish.com (10.43.70.59) with Microsoft SMTP Server id 14.1.225.23; Mon, 11 Jun 2012 16:11:38 +0000 Received: from mail71-ch1 (localhost [127.0.0.1]) by mail71-ch1-R.bigfish.com (Postfix) with ESMTP id 66B6D2C0275; Mon, 11 Jun 2012 16:11:38 +0000 (UTC) X-Forefront-Antispam-Report: CIP:157.55.7.222; KIP:(null); UIP:(null); IPV:NLI; H:mail.philips.com; RD:none; EFVD:NLI X-SpamScore: -54 X-BigFish: VPS-54(zz217bL15d6O9251J2174M936eI1be0I542M1432I1a09J11f6Nzz1202hzz1033IL8275bh8275dhz2dh2a8h668h839h944hd25hf0ah) Received: from mail71-ch1 (localhost.localdomain [127.0.0.1]) by mail71-ch1 (MessageSwitch) id 1339431096858769_15094; Mon, 11 Jun 2012 16:11:36 +0000 (UTC) Received: from CH1EHSMHS015.bigfish.com (snatpool2.int.messaging.microsoft.com [10.43.68.231]) by mail71-ch1.bigfish.com (Postfix) with ESMTP id CD62F4C01CF; Mon, 11 Jun 2012 16:11:36 +0000 (UTC) Received: from mail.philips.com (157.55.7.222) by CH1EHSMHS015.bigfish.com (10.43.70.15) with Microsoft SMTP Server (TLS) id 14.1.225.23; Mon, 11 Jun 2012 16:11:36 +0000 Received: from 011-DB3MPN1-032.MGDPHG.emi.philips.com ([169.254.2.75]) by 011-DB3MMR1-009.MGDPHG.emi.philips.com ([10.128.28.48]) with mapi id 14.01.0355.003; Mon, 11 Jun 2012 17:16:15 +0100 From: "Keoh, Sye Loong" To: Markus Wehner Thread-Topic: [core] New Version Notification for draft-garcia-core-security-04.txt Thread-Index: AQHNC5r0EwDett+O70KiTbE6KGnT95Z9HiywgHNifYCABT0JcA== Date: Mon, 11 Jun 2012 16:12:32 +0000 Message-ID: References: <20120326215140.20793.73440.idtracker@ietfa.amsl.com> <4FD1BDC7.5060203@htw-dresden.de> In-Reply-To: <4FD1BDC7.5060203@htw-dresden.de> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [194.171.252.102] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-OriginatorOrg: philips.com Cc: "core@ietf.org" , "Kumar, Sandeep" Subject: Re: [core] New Version Notification for draft-garcia-core-security-04.txt X-BeenThere: core@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Jun 2012 16:12:40 -0000 Dear Markus, Thank you very much for your comments. Yes, you are absolutely right, that aggregation of data also breaks E2E sec= urity. Unfortunately, this is a very difficult problem in the area, and we = have not seen any good solution that can address E2E security issues effect= ively. As you said, the use of homomorphic encryption scheme requires compl= ex computation, and we think it may not be feasible on constrained devices,= although it's worth mentioning and considering. I have the impression that trustworthiness is something very difficult to q= uantify, there are people who are skeptical about interaction between devi= ces (running different applications) from multiple domains, and how trust c= an be established between them when they interact is typically unknown or u= nspecified. If you have some use cases that you think we should consider, w= e would be glad to hear them :) Thanks and kind regards, Sye Loong -----Original Message----- From: Markus Wehner [mailto:wehner@htw-dresden.de]=20 Sent: vrijdag 8 juni 2012 10:55 To: Keoh, Sye Loong Cc: core@ietf.org Subject: Re: [core] New Version Notification for draft-garcia-core-security= -04.txt Dear Sye, I like this document, it is written well and very clear. Some comments from my side regarding the draft: 1. Difficulties with E2E security not only occur for protocol translation b= ut also for aggregation (or in-network processing in general) of data. Especially in industrial scenarios, aggregation of huge amounts of data may= be performed at dedicated intermediate aggregating devices and sent to the= application afterwards for efficiency reasons. Also in a home environment = it is a privacy reason that for example not any single device can be monito= red by a certain user (end user, power supplier) but aggregated information= is needed. Here, besides the solutions you mentioned for protocol translation, also ho= momorphic encryption may play a role which allows performing aggregation on= encrypted payload on the cost of computational complexity. 2. Multi owner (resp. multi domain) use cases also raise security issues in= the IoT world, i.e. data separation, resources sharing and in this scope t= rustworthiness, fairness, QoS restrictions... . Co-located networks that do= not belong to the same domain which work in a cooperative way, i.e. for ro= uting/energy efficiency, are part of that. Also, if a mobile node moves bet= ween different networks, besides reauthentication and so on, the trustworth= iness is an important thing to consider here. 3. Especially in IoT world, nodes often know about their context which coul= d enhance security. For example a network which knows locations of its node= s and is able to measure them could improve against physical replacement. T= he other way, only nodes within a certain area, i.e. an office room, could = be allowed to have access to the rest of the network (automatically). Unfor= tunately this raises new security issues. Best regards, Markus ----- Original Message ----- From: Keoh, Sye Loong Sent: Mon, 26 Mar 2012 22:08:38 +0000 To: core@ietf.org Cc: Subject: [core] New Version Notification for draft-garcia-core-security-04.= txt --- Original Nachricht --- Absender: Keoh, Sye Loong Datum: 27.03.2012 00:08 > Dear all, > > In this new version, we have updated the conclusions section to reflect t= he status of current security technologies and the missing bits with regard= s to the security requirements we identified in the document. > > Since the WG advised that we should continue working on this draft in Ta= ipei, we are continuously improving the draft so that it serves its purpose= to provide an overview of the security requirements for IoT. Therefore, we= would greatly appreciate feedback and comments from WG members on this doc= ument. > > Many thanks > Sye Loong > > -----Original Message----- > From:internet-drafts@ietf.org [mailto:internet-drafts@ietf.org] > Sent: maandag 26 maart 2012 23:52 > To: Keoh, Sye Loong > Cc:rstruik.ext@gmail.com; Kumar, Sandeep;rene.hummen@cs.rwth-aachen.de; G= arcia Morchon, Oscar > Subject: New Version Notification for draft-garcia-core-security-04.txt > > A new version of I-D, draft-garcia-core-security-04.txt has been successf= ully submitted by Sye Loong Keoh and posted to the IETF repository. > > Filename: draft-garcia-core-security > Revision: 04 > Title: Security Considerations in the IP-based Internet of Thin= gs > Creation date: 2012-03-26 > WG ID: Individual Submission > Number of pages: 45 > > Abstract: > A direct interpretation of the Internet of Things concept refers to > the usage of standard Internet protocols to allow for human-to-thing > or thing-to-thing communication. Although the security needs are > well-recognized, it is still not fully clear how existing IP-based > security protocols can be applied to this new setting. This > Internet-Draft first provides an overview of security architecture, > its deployment model and general security needs in the context of the > lifecycle of a thing. Then, it presents challenges and requirements > for the successful roll-out of new applications and usage of standard > IP-based security protocols when applied to get a functional Internet > of Things. > > > > > The IETF Secretariat > > ________________________________ > The information contained in this message may be confidential and legally= protected under applicable law. The message is intended solely for the add= ressee(s). If you are not the intended recipient, you are hereby notified t= hat any use, forwarding, dissemination, or reproduction of this message is = strictly prohibited and may be unlawful. If you are not the intended recipi= ent, please contact the sender by return e-mail and destroy all copies of t= he original message. > _______________________________________________ > core mailing list > core@ietf.org > https://www.ietf.org/mailman/listinfo/core > --=20 --------------------------------------- Dipl.-Ing. Markus Wehner on behalf of TWISNet project University of Applied Sciences Department of Electrical Engineering Friedrich-List-Platz 1 D-01069 Dresden Germany http://www.htw-dresden.de phone : +49 351 462 2465 email :wehner@htw-dresden.de --------------------------------------- From rstruik.ext@gmail.com Mon Jun 11 09:29:53 2012 Return-Path: X-Original-To: core@ietfa.amsl.com Delivered-To: core@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8EA3B21F85F6 for ; Mon, 11 Jun 2012 09:29:53 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.599 X-Spam-Level: X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1] 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 CaHyWmClavXT for ; Mon, 11 Jun 2012 09:29:52 -0700 (PDT) Received: from mail-vb0-f44.google.com (mail-vb0-f44.google.com [209.85.212.44]) by ietfa.amsl.com (Postfix) with ESMTP id 01D9821F85CC for ; Mon, 11 Jun 2012 09:29:51 -0700 (PDT) Received: by vbbez10 with SMTP id ez10so2759356vbb.31 for ; Mon, 11 Jun 2012 09:29:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:x-enigmail-version:content-type; bh=t5uJWyGKxsuSRzsPvJsX7enhjZiiqx0TB0E9A8K6cPM=; b=pUCqIB81jY82vFcmLbTsIXS63+z2r9MdShm3ghL77z7/aU+fL8MPHPd+mbaJRuHiPt 74w8FbZ3a20g6x4FqPwEOg9kDOnO++hHir5fZYtHNfKNshAqfmT3tp+ZvdZsSsKJuzDW VmxZlD3tzZKNoIqZnN4/uUoHMeYAzxAuROZ4B6jlVFhmWM7cvjnkgqXzTaQVLZw8R3cp /7lFb+MdvHw3PuvZgaJHEG8sa5pUb07SzGFQR0snvvNytJ4grJ4SodLIatz2KckePNeu NV2xwvtk2zbMAEBi4hAzfOujS6z77lIKEEltN+8+Ql+StK3VuwoUUHI/WOMKXDF2WCV/ r6zw== Received: by 10.220.8.17 with SMTP id f17mr12977093vcf.11.1339432191394; Mon, 11 Jun 2012 09:29:51 -0700 (PDT) Received: from [192.168.1.103] (CPE0013100e2c51-CM001cea35caa6.cpe.net.cable.rogers.com. [72.138.34.10]) by mx.google.com with ESMTPS id ek5sm20730047vdb.5.2012.06.11.09.29.40 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 11 Jun 2012 09:29:48 -0700 (PDT) Message-ID: <4FD61CEC.6010307@gmail.com> Date: Mon, 11 Jun 2012 12:29:32 -0400 From: Rene Struik User-Agent: Mozilla/5.0 (Windows NT 6.0; WOW64; rv:12.0) Gecko/20120428 Thunderbird/12.0.1 MIME-Version: 1.0 To: "Keoh, Sye Loong" References: <20120326215140.20793.73440.idtracker@ietfa.amsl.com> <4FD1BDC7.5060203@htw-dresden.de> In-Reply-To: X-Enigmail-Version: 1.4.2 Content-Type: multipart/mixed; boundary="------------030405030102000606080507" Cc: core , "Kumar, Sandeep" Subject: Re: [core] New Version Notification for draft-garcia-core-security-04.txt X-BeenThere: core@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Jun 2012 16:29:53 -0000 This is a multi-part message in MIME format. --------------030405030102000606080507 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Dear Sye Loong, Markus: Secure aggregation is indeed a difficult problem. Even if one has a secure "end to end" aggregation mechanism, this would usually relate to the communication subsystems of devices and not necessarily to the sensing applications themselves (imagine lighting a match next to a temperature sensor, which is connected to a "perfectly secure" end-to-end security system). In those cases, one has to do some more analysis on the devices, e.g., regarding consistency of data over time/location, etc. End-to-end security usually only deals with communication security and not with security of the inputs (or outputs) of this process. When adequately addressed, it does reduce the size of remaining security/robustness/reliability issues. I attached a paper by David Wagner (2004) that may be of interest here (paper in Postscript format). Best regards, Rene On 11/06/2012 12:12 PM, Keoh, Sye Loong wrote: > Dear Markus, > > Thank you very much for your comments. > > Yes, you are absolutely right, that aggregation of data also breaks E2E security. Unfortunately, this is a very difficult problem in the area, and we have not seen any good solution that can address E2E security issues effectively. As you said, the use of homomorphic encryption scheme requires complex computation, and we think it may not be feasible on constrained devices, although it's worth mentioning and considering. > > I have the impression that trustworthiness is something very difficult to quantify, there are people who are skeptical about interaction between devices (running different applications) from multiple domains, and how trust can be established between them when they interact is typically unknown or unspecified. If you have some use cases that you think we should consider, we would be glad to hear them :) > > Thanks and kind regards, > Sye Loong > > -----Original Message----- > From: Markus Wehner [mailto:wehner@htw-dresden.de] > Sent: vrijdag 8 juni 2012 10:55 > To: Keoh, Sye Loong > Cc: core@ietf.org > Subject: Re: [core] New Version Notification for draft-garcia-core-security-04.txt > > Dear Sye, > > I like this document, it is written well and very clear. > Some comments from my side regarding the draft: > > 1. Difficulties with E2E security not only occur for protocol translation but also for aggregation (or in-network processing in general) of data. > Especially in industrial scenarios, aggregation of huge amounts of data may be performed at dedicated intermediate aggregating devices and sent to the application afterwards for efficiency reasons. Also in a home environment it is a privacy reason that for example not any single device can be monitored by a certain user (end user, power supplier) but aggregated information is needed. > Here, besides the solutions you mentioned for protocol translation, also homomorphic encryption may play a role which allows performing aggregation on encrypted payload on the cost of computational complexity. > > 2. Multi owner (resp. multi domain) use cases also raise security issues in the IoT world, i.e. data separation, resources sharing and in this scope trustworthiness, fairness, QoS restrictions... . Co-located networks that do not belong to the same domain which work in a cooperative way, i.e. for routing/energy efficiency, are part of that. Also, if a mobile node moves between different networks, besides reauthentication and so on, the trustworthiness is an important thing to consider here. > > 3. Especially in IoT world, nodes often know about their context which could enhance security. For example a network which knows locations of its nodes and is able to measure them could improve against physical replacement. The other way, only nodes within a certain area, i.e. an office room, could be allowed to have access to the rest of the network (automatically). Unfortunately this raises new security issues. > > Best regards, > Markus > > > ----- Original Message ----- > From: Keoh, Sye Loong > Sent: Mon, 26 Mar 2012 22:08:38 +0000 > To: core@ietf.org > Cc: > Subject: [core] New Version Notification for draft-garcia-core-security-04.txt > --- Original Nachricht --- > Absender: Keoh, Sye Loong > Datum: 27.03.2012 00:08 >> Dear all, >> >> In this new version, we have updated the conclusions section to reflect the status of current security technologies and the missing bits with regards to the security requirements we identified in the document. >> >> Since the WG advised that we should continue working on this draft in Taipei, we are continuously improving the draft so that it serves its purpose to provide an overview of the security requirements for IoT. Therefore, we would greatly appreciate feedback and comments from WG members on this document. >> >> Many thanks >> Sye Loong >> >> -----Original Message----- >> From:internet-drafts@ietf.org [mailto:internet-drafts@ietf.org] >> Sent: maandag 26 maart 2012 23:52 >> To: Keoh, Sye Loong >> Cc:rstruik.ext@gmail.com; Kumar, Sandeep;rene.hummen@cs.rwth-aachen.de; Garcia Morchon, Oscar >> Subject: New Version Notification for draft-garcia-core-security-04.txt >> >> A new version of I-D, draft-garcia-core-security-04.txt has been successfully submitted by Sye Loong Keoh and posted to the IETF repository. >> >> Filename: draft-garcia-core-security >> Revision: 04 >> Title: Security Considerations in the IP-based Internet of Things >> Creation date: 2012-03-26 >> WG ID: Individual Submission >> Number of pages: 45 >> >> Abstract: >> A direct interpretation of the Internet of Things concept refers to >> the usage of standard Internet protocols to allow for human-to-thing >> or thing-to-thing communication. Although the security needs are >> well-recognized, it is still not fully clear how existing IP-based >> security protocols can be applied to this new setting. This >> Internet-Draft first provides an overview of security architecture, >> its deployment model and general security needs in the context of the >> lifecycle of a thing. Then, it presents challenges and requirements >> for the successful roll-out of new applications and usage of standard >> IP-based security protocols when applied to get a functional Internet >> of Things. >> >> >> >> >> The IETF Secretariat >> >> ________________________________ >> The information contained in this message may be confidential and legally protected under applicable law. The message is intended solely for the addressee(s). If you are not the intended recipient, you are hereby notified that any use, forwarding, dissemination, or reproduction of this message is strictly prohibited and may be unlawful. If you are not the intended recipient, please contact the sender by return e-mail and destroy all copies of the original message. >> _______________________________________________ >> core mailing list >> core@ietf.org >> https://www.ietf.org/mailman/listinfo/core >> > > > -- email: rstruik.ext@gmail.com Skype: rstruik cell: +1 (647) 867-5658 USA Google voice: +1 (415) 690-7363 --------------030405030102000606080507 Content-Type: application/postscript; name="Sensor Security - Resilient Aggregation (David Wagner, SASN 2004).ps" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename*0="Sensor Security - Resilient Aggregation (David Wagner, SASN "; filename*1="2004).ps" %!PS-Adobe-2.0 %%Creator: dvips(k) 5.86 Copyright 1999 Radical Eye Software %%Title: a.dvi %%Pages: 10 %%PageOrder: Ascend %%BoundingBox: 0 0 612 792 %%DocumentFonts: Helvetica-Bold Helvetica Times-Bold Times-Roman %%+ Times-Italic %%EndComments %DVIPSWebPage: (www.radicaleye.com) %DVIPSCommandLine: dvips -t letter a.dvi -o a.ps %DVIPSParameters: dpi=600, compressed %DVIPSSource: TeX output 2004.09.08:2237 %%BeginProcSet: texc.pro %! /TeXDict 300 dict def TeXDict begin/N{def}def/B{bind def}N/S{exch}N/X{S N}B/A{dup}B/TR{translate}N/isls false N/vsize 11 72 mul N/hsize 8.5 72 mul N/landplus90{false}def/@rigin{isls{[0 landplus90{1 -1}{-1 1}ifelse 0 0 0]concat}if 72 Resolution div 72 VResolution div neg scale isls{ landplus90{VResolution 72 div vsize mul 0 exch}{Resolution -72 div hsize mul 0}ifelse TR}if Resolution VResolution vsize -72 div 1 add mul TR[ matrix currentmatrix{A A round sub abs 0.00001 lt{round}if}forall round exch round exch]setmatrix}N/@landscape{/isls true N}B/@manualfeed{ statusdict/manualfeed true put}B/@copies{/#copies X}B/FMat[1 0 0 -1 0 0] N/FBB[0 0 0 0]N/nn 0 N/IEn 0 N/ctr 0 N/df-tail{/nn 8 dict N nn begin /FontType 3 N/FontMatrix fntrx N/FontBBox FBB N string/base X array /BitMaps X/BuildChar{CharBuilder}N/Encoding IEn N end A{/foo setfont}2 array copy cvx N load 0 nn put/ctr 0 N[}B/sf 0 N/df{/sf 1 N/fntrx FMat N df-tail}B/dfs{div/sf X/fntrx[sf 0 0 sf neg 0 0]N df-tail}B/E{pop nn A definefont setfont}B/Cw{Cd A length 5 sub get}B/Ch{Cd A length 4 sub get }B/Cx{128 Cd A length 3 sub get sub}B/Cy{Cd A length 2 sub get 127 sub} B/Cdx{Cd A length 1 sub get}B/Ci{Cd A type/stringtype ne{ctr get/ctr ctr 1 add N}if}B/id 0 N/rw 0 N/rc 0 N/gp 0 N/cp 0 N/G 0 N/CharBuilder{save 3 1 roll S A/base get 2 index get S/BitMaps get S get/Cd X pop/ctr 0 N Cdx 0 Cx Cy Ch sub Cx Cw add Cy setcachedevice Cw Ch true[1 0 0 -1 -.1 Cx sub Cy .1 sub]/id Ci N/rw Cw 7 add 8 idiv string N/rc 0 N/gp 0 N/cp 0 N{ rc 0 ne{rc 1 sub/rc X rw}{G}ifelse}imagemask restore}B/G{{id gp get/gp gp 1 add N A 18 mod S 18 idiv pl S get exec}loop}B/adv{cp add/cp X}B /chg{rw cp id gp 4 index getinterval putinterval A gp add/gp X adv}B/nd{ /cp 0 N rw exit}B/lsh{rw cp 2 copy get A 0 eq{pop 1}{A 255 eq{pop 254}{ A A add 255 and S 1 and or}ifelse}ifelse put 1 adv}B/rsh{rw cp 2 copy get A 0 eq{pop 128}{A 255 eq{pop 127}{A 2 idiv S 128 and or}ifelse} ifelse put 1 adv}B/clr{rw cp 2 index string putinterval adv}B/set{rw cp fillstr 0 4 index getinterval putinterval adv}B/fillstr 18 string 0 1 17 {2 copy 255 put pop}for N/pl[{adv 1 chg}{adv 1 chg nd}{1 add chg}{1 add chg nd}{adv lsh}{adv lsh nd}{adv rsh}{adv rsh nd}{1 add adv}{/rc X nd}{ 1 add set}{1 add clr}{adv 2 chg}{adv 2 chg nd}{pop nd}]A{bind pop} forall N/D{/cc X A type/stringtype ne{]}if nn/base get cc ctr put nn /BitMaps get S ctr S sf 1 ne{A A length 1 sub A 2 index S get sf div put }if put/ctr ctr 1 add N}B/I{cc 1 add D}B/bop{userdict/bop-hook known{ bop-hook}if/SI save N @rigin 0 0 moveto/V matrix currentmatrix A 1 get A mul exch 0 get A mul add .99 lt{/QV}{/RV}ifelse load def pop pop}N/eop{ SI restore userdict/eop-hook known{eop-hook}if showpage}N/@start{ userdict/start-hook known{start-hook}if pop/VResolution X/Resolution X 1000 div/DVImag X/IEn 256 array N 2 string 0 1 255{IEn S A 360 add 36 4 index cvrs cvn put}for pop 65781.76 div/vsize X 65781.76 div/hsize X}N /p{show}N/RMat[1 0 0 -1 0 0]N/BDot 260 string N/Rx 0 N/Ry 0 N/V{}B/RV/v{ /Ry X/Rx X V}B statusdict begin/product where{pop false[(Display)(NeXT) (LaserWriter 16/600)]{A length product length le{A length product exch 0 exch getinterval eq{pop true exit}if}{pop}ifelse}forall}{false}ifelse end{{gsave TR -.1 .1 TR 1 1 scale Rx Ry false RMat{BDot}imagemask grestore}}{{gsave TR -.1 .1 TR Rx Ry scale 1 1 false RMat{BDot} imagemask grestore}}ifelse B/QV{gsave newpath transform round exch round exch itransform moveto Rx 0 rlineto 0 Ry neg rlineto Rx neg 0 rlineto fill grestore}B/a{moveto}B/delta 0 N/tail{A/delta X 0 rmoveto}B/M{S p delta add tail}B/b{S p tail}B/c{-4 M}B/d{-3 M}B/e{-2 M}B/f{-1 M}B/g{0 M} B/h{1 M}B/i{2 M}B/j{3 M}B/k{4 M}B/w{0 rmoveto}B/l{p -4 w}B/m{p -3 w}B/n{ p -2 w}B/o{p -1 w}B/q{p 1 w}B/r{p 2 w}B/s{p 3 w}B/t{p 4 w}B/x{0 S rmoveto}B/y{3 2 roll p a}B/bos{/SS save N}B/eos{SS restore}B end %%EndProcSet %%BeginProcSet: 8r.enc % @@psencodingfile@{ % author = "S. Rahtz, P. MacKay, Alan Jeffrey, B. Horn, K. Berry", % version = "0.6", % date = "22 June 1996", % filename = "8r.enc", % email = "kb@@mail.tug.org", % address = "135 Center Hill Rd. // Plymouth, MA 02360", % codetable = "ISO/ASCII", % checksum = "119 662 4424", % docstring = "Encoding for TrueType or Type 1 fonts to be used with TeX." % @} % % Idea is to have all the characters normally included in Type 1 fonts % available for typesetting. This is effectively the characters in Adobe % Standard Encoding + ISO Latin 1 + extra characters from Lucida. % % Character code assignments were made as follows: % % (1) the Windows ANSI characters are almost all in their Windows ANSI % positions, because some Windows users cannot easily reencode the % fonts, and it makes no difference on other systems. The only Windows % ANSI characters not available are those that make no sense for % typesetting -- rubout (127 decimal), nobreakspace (160), softhyphen % (173). quotesingle and grave are moved just because it's such an % irritation not having them in TeX positions. % % (2) Remaining characters are assigned arbitrarily to the lower part % of the range, avoiding 0, 10 and 13 in case we meet dumb software. % % (3) Y&Y Lucida Bright includes some extra text characters; in the % hopes that other PostScript fonts, perhaps created for public % consumption, will include them, they are included starting at 0x12. % % (4) Remaining positions left undefined are for use in (hopefully) % upward-compatible revisions, if someday more characters are generally % available. % % (5) hyphen appears twice for compatibility with both ASCII and Windows. % /TeXBase1Encoding [ % 0x00 (encoded characters from Adobe Standard not in Windows 3.1) /.notdef /dotaccent /fi /fl /fraction /hungarumlaut /Lslash /lslash /ogonek /ring /.notdef /breve /minus /.notdef % These are the only two remaining unencoded characters, so may as % well include them. /Zcaron /zcaron % 0x10 /caron /dotlessi % (unusual TeX characters available in, e.g., Lucida Bright) /dotlessj /ff /ffi /ffl /.notdef /.notdef /.notdef /.notdef /.notdef /.notdef /.notdef /.notdef % very contentious; it's so painful not having quoteleft and quoteright % at 96 and 145 that we move the things normally found there down to here. /grave /quotesingle % 0x20 (ASCII begins) /space /exclam /quotedbl /numbersign /dollar /percent /ampersand /quoteright /parenleft /parenright /asterisk /plus /comma /hyphen /period /slash % 0x30 /zero /one /two /three /four /five /six /seven /eight /nine /colon /semicolon /less /equal /greater /question % 0x40 /at /A /B /C /D /E /F /G /H /I /J /K /L /M /N /O % 0x50 /P /Q /R /S /T /U /V /W /X /Y /Z /bracketleft /backslash /bracketright /asciicircum /underscore % 0x60 /quoteleft /a /b /c /d /e /f /g /h /i /j /k /l /m /n /o % 0x70 /p /q /r /s /t /u /v /w /x /y /z /braceleft /bar /braceright /asciitilde /.notdef % rubout; ASCII ends % 0x80 /.notdef /.notdef /quotesinglbase /florin /quotedblbase /ellipsis /dagger /daggerdbl /circumflex /perthousand /Scaron /guilsinglleft /OE /.notdef /.notdef /.notdef % 0x90 /.notdef /.notdef /.notdef /quotedblleft /quotedblright /bullet /endash /emdash /tilde /trademark /scaron /guilsinglright /oe /.notdef /.notdef /Ydieresis % 0xA0 /.notdef % nobreakspace /exclamdown /cent /sterling /currency /yen /brokenbar /section /dieresis /copyright /ordfeminine /guillemotleft /logicalnot /hyphen % Y&Y (also at 45); Windows' softhyphen /registered /macron % 0xD0 /degree /plusminus /twosuperior /threesuperior /acute /mu /paragraph /periodcentered /cedilla /onesuperior /ordmasculine /guillemotright /onequarter /onehalf /threequarters /questiondown % 0xC0 /Agrave /Aacute /Acircumflex /Atilde /Adieresis /Aring /AE /Ccedilla /Egrave /Eacute /Ecircumflex /Edieresis /Igrave /Iacute /Icircumflex /Idieresis % 0xD0 /Eth /Ntilde /Ograve /Oacute /Ocircumflex /Otilde /Odieresis /multiply /Oslash /Ugrave /Uacute /Ucircumflex /Udieresis /Yacute /Thorn /germandbls % 0xE0 /agrave /aacute /acircumflex /atilde /adieresis /aring /ae /ccedilla /egrave /eacute /ecircumflex /edieresis /igrave /iacute /icircumflex /idieresis % 0xF0 /eth /ntilde /ograve /oacute /ocircumflex /otilde /odieresis /divide /oslash /ugrave /uacute /ucircumflex /udieresis /yacute /thorn /ydieresis ] def %%EndProcSet %%BeginProcSet: texps.pro %! TeXDict begin/rf{findfont dup length 1 add dict begin{1 index/FID ne 2 index/UniqueID ne and{def}{pop pop}ifelse}forall[1 index 0 6 -1 roll exec 0 exch 5 -1 roll VResolution Resolution div mul neg 0 0]/Metrics exch def dict begin Encoding{exch dup type/integertype ne{pop pop 1 sub dup 0 le{pop}{[}ifelse}{FontMatrix 0 get div Metrics 0 get div def} ifelse}forall Metrics/Metrics currentdict end def[2 index currentdict end definefont 3 -1 roll makefont/setfont cvx]cvx def}def/ObliqueSlant{ dup sin S cos div neg}B/SlantFont{4 index mul add}def/ExtendFont{3 -1 roll mul exch}def/ReEncodeFont{CharStrings rcheck{/Encoding false def dup[exch{dup CharStrings exch known not{pop/.notdef/Encoding true def} if}forall Encoding{]exch pop}{cleartomark}ifelse}if/Encoding exch def} def end %%EndProcSet %%BeginProcSet: special.pro %! TeXDict begin/SDict 200 dict N SDict begin/@SpecialDefaults{/hs 612 N /vs 792 N/ho 0 N/vo 0 N/hsc 1 N/vsc 1 N/ang 0 N/CLIP 0 N/rwiSeen false N /rhiSeen false N/letter{}N/note{}N/a4{}N/legal{}N}B/@scaleunit 100 N /@hscale{@scaleunit div/hsc X}B/@vscale{@scaleunit div/vsc X}B/@hsize{ /hs X/CLIP 1 N}B/@vsize{/vs X/CLIP 1 N}B/@clip{/CLIP 2 N}B/@hoffset{/ho X}B/@voffset{/vo X}B/@angle{/ang X}B/@rwi{10 div/rwi X/rwiSeen true N}B /@rhi{10 div/rhi X/rhiSeen true N}B/@llx{/llx X}B/@lly{/lly X}B/@urx{ /urx X}B/@ury{/ury X}B/magscale true def end/@MacSetUp{userdict/md known {userdict/md get type/dicttype eq{userdict begin md length 10 add md maxlength ge{/md md dup length 20 add dict copy def}if end md begin /letter{}N/note{}N/legal{}N/od{txpose 1 0 mtx defaultmatrix dtransform S atan/pa X newpath clippath mark{transform{itransform moveto}}{transform{ itransform lineto}}{6 -2 roll transform 6 -2 roll transform 6 -2 roll transform{itransform 6 2 roll itransform 6 2 roll itransform 6 2 roll curveto}}{{closepath}}pathforall newpath counttomark array astore/gc xdf pop ct 39 0 put 10 fz 0 fs 2 F/|______Courier fnt invertflag{PaintBlack} if}N/txpose{pxs pys scale ppr aload pop por{noflips{pop S neg S TR pop 1 -1 scale}if xflip yflip and{pop S neg S TR 180 rotate 1 -1 scale ppr 3 get ppr 1 get neg sub neg ppr 2 get ppr 0 get neg sub neg TR}if xflip yflip not and{pop S neg S TR pop 180 rotate ppr 3 get ppr 1 get neg sub neg 0 TR}if yflip xflip not and{ppr 1 get neg ppr 0 get neg TR}if}{ noflips{TR pop pop 270 rotate 1 -1 scale}if xflip yflip and{TR pop pop 90 rotate 1 -1 scale ppr 3 get ppr 1 get neg sub neg ppr 2 get ppr 0 get neg sub neg TR}if xflip yflip not and{TR pop pop 90 rotate ppr 3 get ppr 1 get neg sub neg 0 TR}if yflip xflip not and{TR pop pop 270 rotate ppr 2 get ppr 0 get neg sub neg 0 S TR}if}ifelse scaleby96{ppr aload pop 4 -1 roll add 2 div 3 1 roll add 2 div 2 copy TR .96 dup scale neg S neg S TR}if}N/cp{pop pop showpage pm restore}N end}if}if}N/normalscale{ Resolution 72 div VResolution 72 div neg scale magscale{DVImag dup scale }if 0 setgray}N/psfts{S 65781.76 div N}N/startTexFig{/psf$SavedState save N userdict maxlength dict begin/magscale true def normalscale currentpoint TR/psf$ury psfts/psf$urx psfts/psf$lly psfts/psf$llx psfts /psf$y psfts/psf$x psfts currentpoint/psf$cy X/psf$cx X/psf$sx psf$x psf$urx psf$llx sub div N/psf$sy psf$y psf$ury psf$lly sub div N psf$sx psf$sy scale psf$cx psf$sx div psf$llx sub psf$cy psf$sy div psf$ury sub TR/showpage{}N/erasepage{}N/copypage{}N/p 3 def @MacSetUp}N/doclip{ psf$llx psf$lly psf$urx psf$ury currentpoint 6 2 roll newpath 4 copy 4 2 roll moveto 6 -1 roll S lineto S lineto S lineto closepath clip newpath moveto}N/endTexFig{end psf$SavedState restore}N/@beginspecial{SDict begin/SpecialSave save N gsave normalscale currentpoint TR @SpecialDefaults count/ocount X/dcount countdictstack N}N/@setspecial{ CLIP 1 eq{newpath 0 0 moveto hs 0 rlineto 0 vs rlineto hs neg 0 rlineto closepath clip}if ho vo TR hsc vsc scale ang rotate rwiSeen{rwi urx llx sub div rhiSeen{rhi ury lly sub div}{dup}ifelse scale llx neg lly neg TR }{rhiSeen{rhi ury lly sub div dup scale llx neg lly neg TR}if}ifelse CLIP 2 eq{newpath llx lly moveto urx lly lineto urx ury lineto llx ury lineto closepath clip}if/showpage{}N/erasepage{}N/copypage{}N newpath}N /@endspecial{count ocount sub{pop}repeat countdictstack dcount sub{end} repeat grestore SpecialSave restore end}N/@defspecial{SDict begin}N /@fedspecial{end}B/li{lineto}B/rl{rlineto}B/rc{rcurveto}B/np{/SaveX currentpoint/SaveY X N 1 setlinecap newpath}N/st{stroke SaveX SaveY moveto}N/fil{fill SaveX SaveY moveto}N/ellipse{/endangle X/startangle X /yrad X/xrad X/savematrix matrix currentmatrix N TR xrad yrad scale 0 0 1 startangle endangle arc savematrix setmatrix}N end %%EndProcSet TeXDict begin 40258431 52099146 1000 600 600 (a.dvi) @start %DVIPSBitmapFont: Fa cmex9 9 5 /Fa 5 115 df<163C167C16F8ED01F0ED03E0ED07C0ED0F80ED1F00153E157E5D4A5A5D 14034A5A4A5A5D141F4AC7FCA2147E5CA2495AA2495AA2495AA2495AA2495AA2133F91C8 FC5B137EA213FE5BA212015BA21203A25B1207A25BA2120FA35B121FA45B123FA590C9FC 5AA912FEB3AA127FA97E7FA5121F7FA4120F7FA31207A27FA212037FA21201A27F1200A2 7F137EA2137F7F80131FA26D7EA26D7EA26D7EA26D7EA26D7EA2147E80A26E7E140F816E 7E6E7E1401816E7E157E153E81ED0F80ED07C0ED03E0ED01F0ED00F8167C163C26B27082 39>18 D<12F07E127C7E7E6C7E6C7E6C7E6C7E7F6C7E137E133E133F6D7E6D7E1307806D 7EA26D7E6D7EA2147EA280A26E7EA26E7EA26E7EA2811403811401A2811400A281157EA2 157FA2811680A2151FA216C0A3150F16E0A4150716F0A5150316F8A9ED01FCB3AAED03F8 A916F01507A516E0150FA416C0151FA31680A2153FA216005DA2157EA215FE5DA214015D A214035D14075DA24A5AA24A5AA24AC7FCA2147EA25CA2495A495AA2495A5C130F495A49 C8FC133E137E5B485A5B485A485A485A48C9FC123E5A5A5A26B27E8239>I82 D<1A0C1A1E1A3EA21A7CA21AF8A2F101F0A2F103E0A2F107C0A2F10F80A2F11F00A2193E A261A261A24E5AA24E5AA24E5AA24E5AA24EC7FCA2183EA260A260A24D5AA24D5AA24D5A A201305E0170150F13F800034CC8FC487E000F163EEA3CFE00705E12E0D8407F5D12006D 6C495AA26D6C495AA24C5A6D7E4C5A6D7E4CC9FC6D7E163EA26D6C5BA26D6C5BA291387F 01F0A24B5AEC3F83ED87C0EC1FC7EDCF80EC0FEF03FFCAFCA26E5AA26E5AA25D14015D6E 5A475B78834D>112 D<1A0C1A1EA21A3EA21A3CA21A7CA21A78A21AF8A21AF0A21901A2 1AE0A21903A21AC0A31907A21A80A2190FA21A00A261A2191EA2193EA2193CA2197CA219 78A219F8A261A21801A261A21803A261A21807A261A2180FA296C7FCA260A2181EA3183E A2183CA2187CA21878A218F8A260A21701A260A21703A260A2170713106013300170150F A201F893C8FC12015F1203486C151EA2000D163E121D0019163CEA30FE0070167C126000 C01678EA407F000016F8A25FA26D7E1601A25FA26D6C1303A25FA26D6C1307A25FA2160F 6D7E94C9FCA25EA26D6C131EA2163EA26D6C133CA2167CA216786D7E16F8A25E147F1501 A25EA2EC3F83A25EA21587EC1FC75EA3EC0FEFA293CAFCA215FF805DA314035DA46E5AA4 5D14005D47B478834D>114 D E %EndDVIPSBitmapFont %DVIPSBitmapFont: Fb cmcsc10 9 18 /Fb 18 118 df<14C0EB0180EB030013065B5B13385B5BA2485A12035B120790C7FC5AA2 120E121EA2121C123CA35AA612F85AAD7E1278A67EA3121C121EA2120E120FA27E7F1203 7F12016C7EA213707F13187F7F7FEB0180EB00C0124B77B721>40 D<12C012607E7E7E7E12076C7E6C7EA26C7E7F137013781338133CA2131C131EA2130E13 0FA3EB0780A614C01303AD13071480A6EB0F00A3130E131EA2131C133CA2133813781370 13F05B485AA2485A48C7FC12065A5A5A5A5A124B7BB721>I<123C127E12FFA4127E123C 0808788718>46 D68 D73 D80 D<1418143CA3147EA214FFA39038019F80A201037F140FA201067F1407 A2496C7EA2011C7FEB1801A2496C7EA201707FEB7FFFA29038C0003FA20001158049131F A2000315C090C7120F486C14E0120F486CEB1FF0D8FFF090B5FCA228277EA62E>97 D101 DI105 D108 DII<49B4FC010F13E09038 3F01F890387C007C4848133FD803E0EB0F80000715C04848EB07E0491303001F15F048C7 EA01F8A24815FCA2007E1400A200FE15FEA9007FEC01FCA36C15F86D1303001F15F06D13 07000F15E06C6CEB0FC06C6CEB1F806C6CEB3F006C6C137E90383F01F890380FFFE00101 90C7FC27287DA62F>I114 DI<007FB612F8A2397E00FC010078 EC00780070153800601518A200E0151C48150CA5C71400B3A4497E90387FFFF8A226267E A52C>II E %EndDVIPSBitmapFont %DVIPSBitmapFont: Fc cmr5 5 4 /Fc 4 103 df50 D100 DI<131FEBFF803801E7C0EA03C7 138738078380EB8000A5EAFFFCA2EA0780AEEA3FF8A2121D7F9C12>I E %EndDVIPSBitmapFont %DVIPSBitmapFont: Fd msbm9 9 2 /Fd 2 83 df<007FB712E0B8FC7E3A03C0F003FC00019038E0007E161F160716031601A2 16001680ED01C0176017001503A31507150F151F157FECFFFD15F115F915FDECE03F150F 1507A21503A21501A392C8FC1706170EA2171EA2173C177C17FC1603EE0FDCEE3FBC0003 9039F003FE38007FB712F8B8FC7E2F337FB226>69 D<007FB6FCB712F06C15FE3B03C078 0FFF800001D9F0037F9139E000E3E0EEF0F0EE707883EE781CEE381E170EA7171E171CEE 783CEE7078EEF0F0923801E7E0923807FFC002E3B55A91B500FCC7FC16E0ED83C0ECE3C1 9138E1E1E09138E0F0F0ED7078ED7838ED3C3C6F7E6F7E6F6C7E1683923803C3C06F6C7E 923800E0F0EEF078EE783C707EEE1C0F93381E078000036D90380F03C0007FB539C007FF F8B67F6C81353380B233>82 D E %EndDVIPSBitmapFont %DVIPSBitmapFont: Fe cmsy6 6 6 /Fe 6 113 df0 D<136013701360A20040132000E0137038F861 F0387E67E0381FFF803807FE00EA00F0EA07FE381FFF80387E67E038F861F038E0607000 40132000001300A21370136014157B9620>3 D20 D48 D<01FEEC0FE02603FFC0EB3FF8000F01F0EBFE3E3B1F0FF8 01F0073C3C01FC07C003803B3000FE0F00010070D93F1EEB00C00060EB1F9C00E0D90FF8 1460485C14076E7E6E7E81020315E00060D9073F14C091390F1F80016C90261E0FE01380 003890397C07F0073C1C01F003FE1F003B0F8FE001FFFE3B03FF80007FF8C648C7EA0FE0 33177C953D>I<170C171C173C1738177817F017E0160117C0160317801607EE0F00160E 161E161C163C163816785E5E15015E15034B5AD8038091C7FC00075CD81FC0130E003F14 1ED8F3E0131C0043143CD801F05B15706C6C13F05DEB7C015DEB3E034A5A011F90C8FC5C EB0F8E149EEB07DC14FC6D5A5C13015C13002E327C8232>112 D E %EndDVIPSBitmapFont %DVIPSBitmapFont: Ff cmr6 6 11 /Ff 11 94 df<130C1338137013E0EA01C0EA038013005A120EA25AA25AA312781270A3 12F0AB1270A312781238A37EA27EA27E7E1380EA01C0EA00E013701338130C0E317AA418 >40 D<12C012707E7E7E7E7E1380EA01C0A2EA00E0A21370A313781338A3133CAB1338A3 13781370A313E0A2EA01C0A2EA038013005A120E5A5A5A12C00E317CA418>I<1438B2B7 12FEA3C70038C7FCB227277C9F2F>43 D<13FF000313C0380781E0380F00F0001E137848 133CA248131EA400F8131FAD0078131EA2007C133E003C133CA26C13786C13F0380781E0 3803FFC0C6130018227DA01E>48 D<13E01201120712FF12F91201B3A7487EB512C0A212 217AA01E>II<13FF000313C0380F03E0381C 00F014F8003E13FC147CA2001E13FC120CC712F8A2EB01F0EB03E0EB0FC03801FF00A238 0003E0EB00F01478147C143E143F1230127812FCA2143E48137E0060137C003813F8381E 03F0380FFFC00001130018227DA01E>I<00101330381E01F0381FFFE014C01480EBFE00 EA1BF00018C7FCA513FE381BFF80381F03C0381C01E0381800F014F8C71278A2147CA212 30127812F8A214784813F8006013F0387001E01238381E07803807FF00EA01F816227CA0 1E>53 D<13FE3803FFC0380781E0380E0070481378003C133848133CA200F8131EA3141F A40078133FA26C137F121C380F01DF3807FF9F3803FE1EC7FCA2143E143C001C1338003E 13781470003C13E0381801C0381C0780380FFE00EA03F818227DA01E>57 D91 D93 D E %EndDVIPSBitmapFont /Fg 82[30 51[41 41 61 41 46 25 36 36 1[46 46 46 66 25 41 1[25 46 46 25 41 46 41 46 46 9[76 2[51 46 56 1[56 66 9[56 66 61 56 56 18[23 46[{TeXBase1Encoding ReEncodeFont}36 91.3242 /Times-Italic rf %DVIPSBitmapFont: Fh cmmi6 6 17 /Fh 17 121 df<0003B512FC120F5A4814F8397818180000E01338EAC03000001330A213 701360EBE070A21478EA01C0A21203EB807C0007133C143E380F003C000613181E167D94 24>25 DI<127812FCA4127806067A8513>58 D<127812FCA212FEA2127E1206 A3120CA2121C121812301260124007107A8513>II<140C141C143C1438A21478147014F014 E0130114C0A21303148013071400A25B130E131E131CA2133C13381378137013F05BA212 015B12035BA2120790C7FC5A120EA2121E121C123C123812781270A212F05AA216317CA4 20>I<151815381578157C15FC1401A2EC037C14071406EC0C7EEC1C3E14181430A21460 ECC03FA249487EEB0300A213065B010FB512805B903838000F13305B13E05B484814C000 03140790C7FCD80F80130FD8FFE0EBFFFE16FC27247DA32E>65 D<1338137CA213781370 1300A7EA0780EA1FC0EA38E01230EA60F0EAC1E0A3EA03C0A3EA0780A2EA0F0013041306 EA1E0CA21318121CEA1E70EA0FE0EA07800F237DA116>105 D<1418143C147CA2143814 00A7EB0780EB1FE01338EB60F013C0A2EA0180A2380001E0A4EB03C0A4EB0780A4EB0F00 A4131EA21238EA783CEAF8381378EA70F0EA7FC0001FC7FC162D81A119>I<13F8EA0FF0 A21200A2485AA4485AA43807801E147FEB81C3EB8387380F060F495A1318EB700E4848C7 FCA213FCEA1E7EEA3C0F80EB0781158039780F0300A21402EB070600F0138CEB03F83860 00F019247CA221>II<000F017E13FC3A1F81 FF83FF3B31C383C707803A61EE03CC039026EC01F813C0D8C1F813F013F001E013E00003 903903C0078013C0A2EE0F003907800780A2EE1E041706270F000F00130C163C1718A200 1E011EEB1C70EE1FE0000C010CEB07802F177D9536>I<000F13FC381FC3FF3931C70780 3861EC0301F813C0EAC1F0A213E03903C00780A3EC0F00EA0780A2EC1E041506D80F0013 0C143C15181538001EEB1C70EC1FE0000CEB07801F177D9526>I<3801E01F3903F07FC0 390639C1E0390C3F80F0EB3E00001814F8013C137815F8C65AA49038F001F0A3EC03E0D8 01E013C0EBF00715809038F80F003803DC3CEBCFF8EBC7E001C0C7FC485AA448C8FCA2EA 7FF012FF1D20809520>112 D<380F01F0381FC7F83831CE1CEA61F8EBF03C00C1137C13 E014383803C000A4485AA448C7FCA4121EA2120C16177D951D>114 D117 D<3801F01E3907FC7F80390E1CE1C038180F8100301383007013071260EC0380D8 001EC7FCA45BA21580003014C0397878018012F8EC030038F0FC0638E19C1C387F0FF838 1E03E01A177D9523>120 D E %EndDVIPSBitmapFont %DVIPSBitmapFont: Fi cmmi9 9 39 /Fi 39 123 df<147F903803FFE090380FC0F890383F007C017C017E1360497F484815E0 484890381F80C0120748481481EEC1804848130F003F15C390C7140016C74815C6007E15 CE16DC16D816F8485D5E5E127CA3151F6C143F037713C06C903801E7E03A0F800783E13B 07C07E03E3803B01FFF801FF003A007F80007C2B227EA031>11 D14 D<903801FF80130F013F130001FFC7FC EA01F8485A485A485A485A48C8FCA2127E387FFFF880B5FC00FCC8FCA9127CA27EA26C13 07380F800E3803E07C3801FFF038003F8019217D9F1F>I18 D<1307D90FC01338011F147C16FC5CA2013F1301A202005BA249 1303A2017E5CA201FE1307A2495CA20001140FA2495C17800003021F13C016C149EC8180 A20007EC3F836D017F130016034B5A3A0FFC03CF869039FE070F8E9039DFFE07FC9039C3 F801F0D81FC0C9FCA25BA2123FA290CAFCA25AA2127EA212FEA25A12382A327FA02E>22 D<013FB6128090B712C01203481680481600271F00C018C7FC001C1438EA380100701430 00601380EAE00300001470A2EB0700A25B15F0130E131EA2013E7F133C137CA213FC497F A2000180A2485A157EA2D801C013382A217E9F2C>25 DI<91B6FC01031580130F013F1500495C2701FF03FCC7FC 3803F80048487F49137E485A121F49133E48C7127EA25A127EA215FE00FE5C5AA24A5AA2 4A5A007C5C14074A5A6C495A4AC8FC6C137C380F81F83803FFE0C66CC9FC29217E9F2C> I<017FB512F048B612F85A5A4815E0261F0070C7FC123C1238485B126012E0EA0001A349 5AA31307A25C130FA3131FA291C8FC5BA35BA2137E133C25217E9F22>I39 D<123C127E12FFA4127E123C08087A8715 >58 D<123C127EB4FCA21380A2127F123D1201A412031300A25A1206120E120C121C5A5A 126009177A8715>I<171C177EEE01FEEE07FCEE1FF0EE7FC0923801FF00ED07FCED1FF0 ED7FC04A48C7FCEC07FCEC1FF0EC7FC04948C8FCEB07FCEB1FF0EB7FC04848C9FCEA07FC EA1FF0EA7FC048CAFCA2EA7FC0EA1FF0EA07FCEA01FF38007FC0EB1FF0EB07FCEB01FF90 38007FC0EC1FF0EC07FCEC01FF9138007FC0ED1FF0ED07FCED01FF9238007FC0EE1FF0EE 07FCEE01FEEE007E171C2F2E7AA93C>I<1530157815F8A215F01401A215E01403A215C0 1407A21580140FA215005CA2143EA2143C147CA2147814F8A25C1301A25C1303A25C1307 A2495AA291C7FC5BA2131E133EA2133C137CA2137813F8A25B1201A25B1203A2485AA25B 120FA290C8FC5AA2121E123EA2123C127CA2127812F8A25A12601D4B7CB726>I<127012 FCB4FCEA7FC0EA1FF0EA07FCEA01FF38007FC0EB1FF0EB07FCEB01FF9038007FC0EC1FF0 EC07FCEC01FF9138007FC0ED1FF0ED07FCED01FF9238007FC0EE1FF0EE07FCEE01FEA2EE 07FCEE1FF0EE7FC0923801FF00ED07FCED1FF0ED7FC04A48C7FCEC07FCEC1FF0EC7FC049 48C8FCEB07FCEB1FF0EB7FC04848C9FCEA07FCEA1FF0EA7FC048CAFC12FC12702F2E7AA9 3C>I<16035E5EA24C7EA2163F167FA216FFA2ED01BFED033F831506161F150C1518A215 301570156015C083EC01800203130F15001406A25C141C14184A80A2027FB5FC91B6FCA2 903901800007A249C7FC1306835B16035B5B1370136013E01201D807F04A7EB549B512F0 A25B34367DB53A>65 D<010FB612F817FF18C0903B003FC0003FE0EF0FF0EF03F84B6D7E 717E027F157F8492C81380A24A151F19C05CA21301A25CA21303183F5CA2130719804A15 7FA2130F19004A5D60011F1501605C4D5A013F5E17074A4A5A60017F4B5A4DC7FC91C812 7E4C5A494A5AEE0FF049EC3FC000014AB4C8FCB712FC16F093C9FC3A337DB23F>68 D79 D<03FF13180207EBE038021FEBF87891397F00FCF802FCEB1FF0D901F0130F4948130749 481303494814E0A249C71201A2013E15C0A3137E1780A2017F91C7FC8080EB3FF014FF15 F06D13FE6D6D7E6D806D80010080020F7F1400150F6F7E150315011500A2120CA2001C5D 1218A2150100385D003C14035E4B5A007E4A5A007F141F6D49C7FCD87BE0137C39F9FC03 F839F07FFFE0D8E01F138026C003FEC8FC2D377CB42F>83 D<0103B539C007FFFC5BA290 26000FFCC713804BECFC00020715F0606E6C495A4D5A02014AC7FC6F130E5F6E6C5B5F92 387F80605F92383F818004C3C8FC16C6ED1FEC16F86F5AA2150782A282150FED1DFE1539 15704B7E4A5A4A486C7E150002066D7E5C4A131F4A805C4A6D7E495A49C76C7E1306010E 1403013C81137CD803FE4A7EB500C090387FFFFCA2603E337EB23F>88 D97 D<147F903803FFC090380FC0F090383F0038137C4913F83801F0013803E003 1207EA0FC090388001F0001F90C7FC123F90C8FCA25A127EA45AA3127C150C151C15386C 147015E06CEB03C0390F800F003807C07E3801FFF038007F801E227EA021>99 D I<14FE903807FF8090381F03C090387C01E03801F800485A485A485A485A1401D83F0013 C01403007EEB0F80ECFE00387FFFF8B5128000FCC8FCA45AA415186C1438007C147015E0 003CEB01C0003EEB07806CEB1E00380F80FC3803FFE0C690C7FC1D227DA024>III< EB01C0EB07E014F0130F14E01307EB038090C7FCAA13F0EA03FCEA071EEA0E1F121C1238 00301380EB3F00127012605BEAE07EEA40FE12005B12015BA212035B12071420EBE07000 0F136013C014E014C0EA1F80EA0F81EB8380EB8700EA078EEA03FCEA00F014337EB11A> 105 D107 DII I<011F131F90397FC07FE09039E3E1E0F09039C3E380783A01C1F7007CD981FE133CD983 FC133E00035BEB03F0163FEA0707120600025B1200010F147F167E5CA2011F14FE16FC5C A2013FEB01F8A291380003F016E0491307ED0FC002801380ED1F009038FFC03E9038FEE0 F89038FC7FE0EC1F80000190C8FCA25BA21203A25BA21207A25BB57EA3283083A027> 112 D<3903E003E0390FF81FF8391C7C3C1C0018EB703E39383EE0FE38303FC0EB7F8000 70EB00FCEA607E157000E01400EAC0FEEA40FC1200A212015BA312035BA312075BA3120F 5BA3121F5B0007C8FC1F227EA023>114 D116 D<13F8D803FEEB01C0D8070FEB03E0000EEB8007121C001813C0003814 0FEA301F0070018013C01260013F131F00E0130000401580C65A017E133F13FE491400A2 5D120149137E1602EDFE0716064913FCA2160E0201130C9039F803F81C1618000090380F 7C38D97C1C137090393FF81FE0903907E0078028227EA02C>I<01F01507D803FC903903 800F80D8071E903907C01FC0D80E1F130F121C00380180140F0030021F1307013FEC8003 007013000060160149133FD8E07E168000401500EA00FE494913030001170049137EA203 FE5B00031606495B170E170CA24B131C4915186D15384A6C5B17600001010314E03B00F8 077E01C0903A7C0E3F078090273FFC0FFEC7FC903907F001F832227EA037>119 D<90391F801F8090397FE07FE09039E0F0E0703A01C0F9C0F83903807D833807007F000E 1403000C15F0001C137E0018EC01C002FEC7FC00385B1210C7FC13015CA31303A25C1640 010714E016C0001C5B007E1401010F148000FE1403011FEB0700011B130E39F839F01C39 7070F878393FE07FE0390F801F8025227EA02C>I<13F0D803FCEB01C0D8071EEB03E0D8 0E1F1307121C003813800030140F013F14C000701300126049131FD8E07E14801240EA00 FE49133F000115005BA25D0003147E5BA215FE5D5BA214015DEBF00314070001130F3900 F83FF0EB3FFBEB0FC3EB00075DA20007130FD81F805B003F495AA24AC7FCEB007E003E13 7C00385B381803F0381E07C0D807FFC8FCEA01F823317EA026>I<903807800390381FE0 0790383FF00690387FF80E9038FFFC1C48EBFE789038E03FF03803800190C712E0EC01C0 C7EA0380EC0700140E143C14705C495A495A49C7FC130E133C0170130C49131C48481318 4848133848C71278D80EC013F0380FFE03391F3FFFE0D8381F13C0486C1380D860071300 38E003FE38C000F020227DA024>I E %EndDVIPSBitmapFont %DVIPSBitmapFont: Fj cmti9 9 54 /Fj 54 123 df13 D<1560EC01E0EC03C0EC0700140E5C143C5C5C495A495A13075C49C7FC 5B131E5B137C137813F85B12015B12035B1207A25B120FA290C8FC5AA2121E123EA3123C 127CA31278A212F8A35AAF12701278A21238A2123C121CA27EA27E6C7E12011B4A75B71F >40 D<14301438A28080A2140F801580A2140315C0A4140115E0A81403A415C0A31407A3 1580140FA315005CA3141E143EA2143C147CA25CA25C13015C13035C13075C130F91C7FC 131E133E133C5B5B485AA2485A485A48C8FC121E5A12705A5A1B4A7EB71F>I44 DI<121C127F12FFA412FE12380808778718>I< EC1FC0EC7FF0903801E0F8903807C03CEB0F00011E131E133E013C131F5B13F85B1201A2 485AA20007143F5BA2120F153E49137E121FA348C712FCA4007EEB01F8A4007CEB03F012 FCA2EC07E0A24814C0A2EC0F80A2EC1F00A2141E5C0078137C5C387C01F0383C03E0381F 0F80D80FFEC7FCEA03F8203477B127>48 DIII<1370EA01FC1203A413F8EA00E01300B0121C127F5AA45A12380E20779F18> 58 D<161C163CA2167C16FCA21501821503A2ED077E150F150E151CA21538A2157015F0 15E0EC01C0A2913803807F82EC0700A2140E141E141C5CA25CA25C49B6FCA25B91388000 3F49C7EA1F80A2130E131E131C133C13385B13F05B12011203D80FF0EC3FC0D8FFFE9038 07FFFEA32F367BB539>65 D<0107B612C04915F017FC903A003F8000FE177FEF3F8092C7 121FA24A15C0A2147EA214FE18804A143FA20101ED7F00177E4A5C16010103EC03F04C5A 4AEB1FC091B6C7FC495C9139F0007F804AEB0FC0707E010F6E7E834A1301A2011F81A25C A2133F5F91C71203A2494A5AA2017E4A5A4C5A01FE4A5A4CC7FC49EB01FE0001EC07FC00 7FB612F0B712C04BC8FC32337BB236>II<0107B612C04915F017FC903A003F8001FEEE007FEF1F8092C7EA0FC0EF07E05CEF03 F0147E170102FE15F8A25CA21301A25CA2130317035CA2130718F04A1407A2130F18E04A 140F18C0011F151F18805CEF3F00133F177E91C85AA2494A5A4C5A017E4A5A4C5A01FE4A 5A047EC7FC49495A0001EC0FF8007FB612E0B7C8FC15F835337BB23A>I<0107B712F05B 18E0903A003F80001F1707170392C7FC17015C18C0147EA214FEA24A130EA20101EC1E03 041C13804A91C7FC163C13035E9138F001F891B5FC5B5EECE0011500130F5E5C1707011F 01015BEEC00E0280141E92C7121C133F173C91C812381778495DA2017E14014C5A01FE14 074C5A49141F00014AB45A007FB7FCB8FC94C7FC34337CB234>I<0107B712E05B18C090 3A003F80003F170F170792C7FC17035C1880147EA214FEA25C161C0101EC3C0704381300 4A91C7FCA20103147816704A13F0150349B5FCA25EECE003130F6F5A14C0A2011F13035E 1480A2013F90C9FCA291CAFCA25BA2137EA213FEA25B1201387FFFFCB5FCA233337CB232 >I<0107B548B512C0495CA2903C003FC0000FF0004B5CA292C75BA24A141F60147EA202 FE143F95C7FC5CA201015D177E5CA2010315FE5F5C91B6FC5B5F9138E00001A2010F1403 5F5CA2011F14075F5CA2013F140F5F91C7FCA249141F5F137EA201FE143F94C8FC5B0001 5D3B7FFFF01FFFFCB55BA23A337BB239>72 D<010FB51280A216009038003FC05DA292C7 FCA25CA2147EA214FEA25CA21301A25CA21303A25CA21307A25CA2130FA25CA2131FA25C A2133FA291C8FCA25BA2137EA213FEA25B1201B512F8A25C21337BB21E>I<0107B512C0 5BA29026003FC0C7FC5DA292C8FCA25CA2147EA214FEA25CA21301A25CA21303A25CA213 07A25CA2130FA25C17E0011F140117C05C1603013F1580160791C7FCEE0F005B5E017E14 3EA201FE5CED01FC4913030001EC1FF8007FB6FCB7FC5E2B337CB230>76 D<902607FFC0ED7FFC4917FF81D9003F4B1300611803023BED077CA2027BED0EFC610273 151C1838DAF1F01439F071F014E118E10101ED01C36102C1EC0383EF070301031607050E 5BEC80F8171C0107ED380F6102001470A249EDE01FDC01C090C7FC130EEE0380011E017C 5C933807003E011C140EA2013C4A137E187C01385C5E017816FC6F485B1370ED3FC001F0 EC80016000011500D807F81503277FFF803E90B512C0B5EB3C01151C46337BB245>I<90 2607FF8090383FFFC0496D5BA2D9001F913803F8004A6C6D5A6060EC3BF0027B140360EC 71F8A202F11407DAF0FC91C7FC14E0A20101017E5B170E14C0810103151EEE801CEC801F A20107ECC03C030F1338140016E049010713781770010E14F01503011E15F0705A011C13 01A2013C14FD03005B133816FF0178147F5F0170143FA213F070C8FC1201EA07F8267FFF 807FB5140EA23A337BB239>II<0107B6 12C04915F883903A003F8001FEEE003FEF1F8092C713C0170F5C18E0147EA214FEEF1FC0 5CA201011680173F4A1500177E010315FE5F4AEB03F8EE07E00107EC3FC091B6C7FC16F8 02E0C9FC130FA25CA2131FA25CA2133FA291CAFCA25BA2137EA213FEA25B1201387FFFF0 B5FCA233337CB234>II<0107B512FE49ECFFC017F0903A003F8007F8EE01FCEE00 7E92C7127F835C1880147EA214FEEF7F005CA2010115FE5F4A13015F01034A5AEE0FC04A 495A04FEC7FC49B512F016C09138E003E0ED01F8010F6D7E167C4A137EA2131FA25CA201 3F14FEA291C7FCA24913015E137EEF01C001FE150318805B00011607277FFFF0001400B5 ECFE0EEE7E1CC9EA1FF8EE07E032357BB238>I<913901FC018091380FFF03023F13C791 387E07EF903A01F801FF0049487E4A7F495A4948133E131F91C7FC5B013E143CA3137E16 38A293C7FC137FA26D7E14E014FE90381FFFC06D13F86D7F01017F6D6C7E020F7F140015 3F6F7E150FA4120EA2001E5D121CA2151F003C92C7FCA2003E143E5D127E007F5C6D485A 9038C007E039F3F80FC000F0B5C8FC38E03FFC38C00FF029377AB42B>I<0003B812C05A 1880903AF800FC003F260FC001141F0180150F01005B001EEE07001403121C003C4A5BA2 00380107140E127800705CA2020F141E00F0161CC74990C7FCA2141FA25DA2143FA292C9 FCA25CA2147EA214FEA25CA21301A25CA21303A25CA21307A25C497E001FB512F05AA232 3374B237>I87 D97 D<137EEA0FFE121F5B1200A35BA212 01A25BA21203A25BA21207A2EBC3E0EBCFF8380FDC3EEBF81F497E01E01380EA1FC01380 15C013005AA2123EA2007E131F1580127CA2143F00FC14005AA2147EA25CA2387801F85C 495A6C485A495A6C48C7FCEA0FFCEA03F01A3578B323>I<14FCEB07FF90381F07809038 3E03C0EBFC013801F8033803F0073807E00F13C0120F391F80070091C7FC48C8FCA35A12 7EA312FE5AA4007C14C0EC01E0A2EC03C06CEB0F80EC1F006C137C380F81F03803FFC0C6 48C7FC1B2278A023>III<15 1FED7FC0EDF0E0020113F0EC03E3A2EC07C316E0EDC1C091380FC0005DA4141F92C7FCA4 5C143E90381FFFFEA3D9007EC7FC147CA414FC5CA513015CA413035CA413075CA3130FA2 5CA3131F91C8FCA35B133E1238EA7E3CA2EAFE7812FC485AEA78E0EA3FC0000FC9FC2445 82B418>I<143FECFF80903803E1E6903807C0FF90380F807FEB1F00133E017E133F4913 3EA24848137EA24848137CA215FC12074913F8A21401A2D80FC013F0A21403120715E014 07140F141F3903E03FC00001137FEBF0FF38007FCF90381F0F801300141FA21500A25C14 3E1238007E137E5C00FE5B48485A387803E0387C0F80D81FFFC7FCEA07F820317CA023> III107 D<133FEA07FF5A13FEEA007EA3137CA213FCA213F8 A21201A213F0A21203A213E0A21207A213C0A2120FA21380A2121FA21300A25AA2123EA2 127EA2127C1318EAFC1C133CEAF838A21378137012F013F0EAF8E01279EA3FC0EA0F0010 3579B314>I<2703C003F8137F3C0FF00FFE01FFC03C1E783C1F07C1E03C1C7CF00F8F01 F03B3C3DE0079E0026383FC001FC7FD97F805B007001005B5E137ED8F0FC90380FC00100 E05FD860F8148012000001021F130360491400A200034A13076049013E130FF081800007 027EEC83C0051F138049017C1403A2000F02FC1407053E130049495CEF1E0E001F01015D 183C010049EB0FF0000E6D48EB03E03A227AA03F>I<3903C007F0390FF01FFC391E787C 1E391C7CF01F393C3DE00F26383FC01380EB7F8000781300EA707EA2D8F0FC131F00E015 00EA60F8120000015C153E5BA20003147E157C4913FCEDF8180007153C0201133801C013 F0A2000F1578EDE070018014F016E0001FECE1C015E390C7EAFF00000E143E26227AA02B >I<14FCEB07FF90381F07C090383E03E09038FC01F0EA01F83903F000F8485A5B120F48 4813FCA248C7FCA214014814F8127EA2140300FE14F05AA2EC07E0A2007CEB0FC0158014 1FEC3F006C137E5C381F01F0380F83E03803FF80D800FCC7FC1E2278A027>I<011E137C 90387F81FF9039F3C387C09039E3EF03E03901E1FE01D9C1FC13F0EBC3F8000313F00183 14F814E0EA07871307000313C01200010F130316F01480A2011F130716E01400A249EB0F C0A2013EEB1F80A2017EEB3F00017F133E5D5D9038FF81F09038FDC3E09038F8FF80027E C7FC000190C8FCA25BA21203A25BA21207A25BB5FCA325307FA027>I<903803F0189038 0FF83890383E1C7890387C0EF89038F807F0EA01F0EA03E000071303D80FC013E0A2EA1F 801407D83F0013C0A348130F007E1480A300FE131F481400A35C143E147E127C14FE495A EA3C03EA3E07EA1F0E3807FCF8EA01F0C7FC13015CA313035CA21307A25C48B5FCA25C1D 3078A023>I<3903C00FC0390FF03FF0391E78F078391C7DE03C393C3FC0FC00381380EB 7F00007814F8D8707E13701500EAF0FC12E0EA60F812001201A25BA21203A25BA21207A2 5BA2120FA25BA2121FA290C8FC120E1E227AA020>II<1303EB0F80A3131FA21400A25BA2133EA2137EA2137C387FFF F8A2B5FC3800F800A21201A25BA21203A25BA21207A25BA2120FA25B1460001F13F014E0 1300130114C01303001E1380EB07005BEA0F1EEA07F8EA01E015307AAE19>II<01F01338D803FC13FCEA0F1E120E121C123C0038147CEA783E0070143CA2 137ED8F07C1338EA60FCC65A1578000114705BA215F0000314E05BA2EC01C0A2EBC00315 8014071500EBE00EA26C6C5A3800F878EB7FE0EB1F801E227AA023>II<011F137C90387FC1FF3A01E1E787 803A03C0F703C0903880FE0FEA07004813FC000E1580001E9038F80700001C91C7FC1301 003C5B1218120013035CA31307A25C1506010F130F150E14800038141ED87C1F131C00FC 143C1538013F5B39F07FC0E03970F3C3C0393FE1FF80260F807EC7FC22227CA023>I<13 F0D803FC1307D80F1E130F000E141F121C123C0038143FD8783E133E1270A2017E137ED8 F07C137CEA60FCC65A15FC000114F85BA21401000314F013E0A2140315E0EA07C0A20003 130715C0EBE00F141F0001133F9038F07F8038007FEFEB1F8FEB001F1500A25C003E133E 007E137E147C5C007C5BEA7001495A38380780D83C1FC7FCEA0FFCEA07F020317AA025> I<903807801C90381FE03C90383FF038017F13789038FFF8F03901F07CE0EBE01F3903C0 03C09038800780EC0F00C7121E141C143C5C5C495AEB07C0495A011EC7FC5B5B49137049 13F0000114E0485A38078001390FC003C0381FF80790383E0F80393C1FFF00127838700F FE38F007F838E001E01E227CA01F>I E %EndDVIPSBitmapFont /Fk 172[33 4[44 12[41 12[33 3[33 3[17 4[22 39[{ TeXBase1Encoding ReEncodeFont}7 66.4176 /Times-Italic rf /Fl 82[22 51[33 1[48 33 33 18 26 22 33 33 33 33 52 18 33 1[18 33 33 22 29 33 29 33 29 9[63 1[48 41 37 2[37 48 1[59 8[48 44 1[48 7[33 33 33 1[33 33 33 33 33 33 18 17 1[17 41[37 2[{TeXBase1Encoding ReEncodeFont}47 66.4176 /Times-Roman rf %DVIPSBitmapFont: Fm cmbx9 9 40 /Fm 40 122 df<017F160E2601FFC0151F000701F05D260FE1F85D261FC07E15FE273F80 7F80EB03FCDA3FE0EB0FF8007FD91FFE137F9026001E7FB55ADA1F1FEBF7E048D90F01EB 8FC092C7485A173F4DC7FC177E5F4C5A16034C5A5F6C49495A021E495A0180143F003F01 3E49C8FC4A137E261FC0785B3A0FE1F801F83907FFF00300019038C007F026007F005B90 C7484813FE923A1F8003FF80033F010F13E0923A7F001FC3F0037EEB3F804B90387F00F8 4A48157C02034A133C4A485B4B153E91260FC001141EEC1F80143FEC7F00147E5C495A13 03495A5C49480100143E4948163C013F8149C86C137C017E17F84992383F80F04848ED1F C394380FFFE049030313806C48923800FE003F3C7BB74A>37 D<147014F0EB03E0EB07C0 EB0F80131FEB3F00133E137E5B485AA2485AA212075B120FA2485AA3485AA3127FA390C7 FCA35AAF7EA37FA3123FA36C7EA36C7EA212077F1203A26C7EA26C7E137E133E133FEB1F 80130FEB07C0EB03E0EB00F01470144B78B722>40 D<12E07E127C7E7E7F6C7E12077F6C 7E6C7EA26C7EA27F137E137FA2EB3F80A3EB1FC0A314E0A3130FA314F0AF14E0A3131FA3 14C0A3EB3F80A3EB7F00A2137E13FE5BA2485AA2485A485A5B120F485A90C7FC123E5A12 F05A144B7BB722>I<120FEA3FC0EA7FE0EAFFF0A213F8A4127F123FEA0F3812001378A2 1370A213F013E01201EA03C0A2EA0780EA0F00121E5A12180D1B7A8B19>44 DI<120FEA3FC0EA7FE0EAFFF0A6EA7FE0EA3FC0EA0F000C0C7A 8B19>I<147814F81303131FEA03FFB5FCA3EAFC1F1200B3B2007FB512FEA41F317AB02C> 49 D<000C140ED80FE013FE90B5FC5D5D5D5D5D92C7FC14FC14F091C8FC1380A6EB87FE 9038BFFFC090B512F09038FC0FF89038E003FE01C07F497E01001480000E6D13C0C8FCA2 16E0A3121FEA7F807F487EA316C05B5CD87F801480D87C0014006C5B393F8007FE391FE0 1FFC0007B512F06C14C0C691C7FCEB1FF823327CB02C>53 D<120FEA3FC0EA7FE0EAFFF0 A6EA7FE0EA3FC0EA0F00C7FCA9120FEA3FC0EA7FE0EAFFF0A6EA7FE0EA3FC0EA0F000C21 7AA019>58 D65 D70 D73 D78 D<913803FF80027F13FC49B6FC0107010113 C0903A1FF8003FF0D93FE0EB0FF8D9FFC0EB07FE48496D7E4890C76C13804980000717C0 4848ED7FE0A24848ED3FF0A2003F17F8A2007F17FC49151FA300FF17FEAB007F17FCA26D 153FA2003F17F8A36C6CED7FF0A26C6CEDFFE0000717C06D5C6C17806C6D4913006C6D49 5AD97FF0EB1FFCD91FF8EB3FF0903A07FF01FFC0010190B5C7FC6D6C13FC020713C03735 7BB342>I83 D<003FB812F8A4D9F003EB801FD87F80ED03FC01001501007E1600007C177CA20078173C A400F8173E48171EA4C71600B3A9011FB612F0A437327DB13E>I87 D97 DI<903807FF80013F13F090B512FC3903FE01FE4848487EEA0FF8EA1FF0EA3FE0 A2007F6D5A496C5A153000FF91C7FCA9127F7FA2003FEC07807F6C6C130F000FEC1F00D8 07FE133E3903FF80FCC6EBFFF8013F13E0010790C7FC21217DA027>II<903803FF80013F13F090B512FC48EB 03FE3907FC007F4848EB3F804848EB1FC05B003FEC0FE0127F5B16F012FF150790B6FCA3 01C0C8FCA4127F7F123F16F06C7E000F14016C6CEB03E0D803FEEB0FC03A01FF807F806C 6CB51200011F13FC010313E024217EA029>II<16F890390FFC07FE90387FFF9F48B6127F3907FC0FFC380F F003001F14FED9E001133E003FECFF1C1600A6001F5CEBF003000F5C3907FC0FF890B512 E0486C1380D90FFCC7FC48C9FCA37F7F90B512F015FE6CECFF8016E06C15F06C15F84815 FC121F393F80001F48C7EA03FE481401481400A46C14016C6CEB03FC6C6CEB07F86C6CEB 0FF0D80FFCEB7FE00003B61280C6ECFE00010F13E028327EA12C>III107 DI<2703F803FEEB03FE00 FF903B1FFFC01FFFC0027FD9E07F7F913BF81FF0F81FF0903CF9E00FF9E00FF8260FFBC0 EBFBC06CB4486CB4486C7E02001400495CA3495CB2B500E0B500E0B512E0A443217CA04A >I<3901F803FF00FF010F13C0023F13F09138FC0FF89039F9E007FC380FFBC06CB4486C 7E1400A25BA25BB2B539E07FFFF0A42C217DA031>I<903803FF80011F13F090B512FE48 EB01FF3A07FC007FC0D80FF0EB1FE0001F15F049130F003F15F8491307007F15FCA300FF 15FEA8007F15FCA26D130F003F15F8001F15F06D131F6C6CEB3FE06C6CEB7FC03A01FF01 FF006CEBFFFE013F13F80103138027217EA02C>I<3901FC07FC00FF90387FFF8001FDB5 12E09039FFF01FF89138C007FC000F90380003FE6C4880496D1380A26F13C0A3EE7FE0A9 EEFFC0A34B1380A26D4913006D495A9138C00FFC9138F03FF801FDB512E0D9FC7F1380DA 0FF8C7FC91C9FCABB512E0A42B307EA031>II<3901F81F8000FFEB7FF0ECFFF89038F9E3FC9038FBC7FE380F FF876C1307A213FEEC03FCEC01F8EC0060491300B1B512F0A41F217EA024>I<9038FFE1 C0000713FF5A383F803F387E000F14075A14037EA26C6CC7FC13FCEBFFE06C13FC806CEB FF80000F14C06C14E0C6FC010F13F0EB007F140F00F0130714037EA26C14E06C13076CEB 0FC09038C01F8090B5120000F913FC38E03FE01C217DA023>I<133CA5137CA313FCA212 01A212031207001FB51280B6FCA3D807FCC7FCB0EC03C0A79038FE078012033901FF0F00 6C13FEEB3FFCEB0FF01A2F7EAE22>II< B539C007FFC0A4D807FEC7EAF80000035D6D13016C5D14806C4A5AA2ECC007017F5CECE0 0F013F91C7FC6E5A011F131EECF83E010F133CECFC7C01071378ECFEF801035B14FF6D5B A26D5BA26E5AA26EC8FCA2141E2A217EA02F>II< B539C007FFC0A4D807FEC7EAF80000035D6D13016C5D14806C4A5AA2ECC007017F5CECE0 0F013F91C7FC6E5A011F131EECF83E010F133CECFC7C01071378ECFEF801035B14FF6D5B A26D5BA26E5AA26EC8FCA2141EA25CA2147C003E1378007F13F8486C5A1381EB83E0EB87 C0495AD87F3FC9FCEA3FFEEA1FF8EA07E02A307EA02F>121 D E %EndDVIPSBitmapFont %DVIPSBitmapFont: Fn cmr9 9 90 /Fn 90 125 df2 D<011FB512F0A39026001FF0C7FC6E5AA7EC7FF80107B57E90393FCFEFF0 9039FE0FE1FCD803F8EBE07FD807E0EC1F80D80FC0EC0FC0001F16E0D83F80EC07F0007F 16F8010014034816FCA76C16F801801407003F16F0D81FC0EC0FE0000F16C0D807E0EC1F 80D803F8EC7F00D800FEEBE1FC90393FCFEFF00107B512809026007FF8C7FCEC0FE0A74A 7E011FB512F0A32E337CB237>8 D<91393FE00FE0903A01FFF83FF8903A07E01EF83C90 3A1F800FF07E903A3F001FE0FE017E133F4914C0485A1738484890381F8000ACB812C0A3 3B03F0001F8000B3A7486C497EB50083B5FCA32F357FB42D>11 DIII<003C13F0387E01F838FF03FCA2EB83FEA2EA7F81383D80F6000113 06A40003130EEB000CA248131C00061318000E1338000C1330001C13704813E0387001C0 0060138017177EB326>34 D<1307A3EB1FE0EBFFFC00037F3907E71F80390F8703C0391E 0701E0003C1300157000781430153800F014F814011403A312F8EC01F000FC90C7FCA212 7EEA7F87EA3FE713FF6C13E06C13F86C13FE6C7FC61480013F13C0010713E0143FEC0FF0 14071403EC01F81400127C12FE1578A312FC12F800E014F012601270EC01E00038EB03C0 001C1307001FEB0F80390FC73F003803FFFCC613F0EB3FC00107C7FCA31D3C7CB726>36 D<017C1503D803FEED078026078780140F260F01C0141F261E00E0EC3F00003E01F8147E 003C017CEB01FE007C90397F8007FC913933FFFEF800789038307FF900F89039380001F0 0218495A16075F4C5A161F4CC7FC163E5E023813FC007801305B007C4A5AEC7003003C01 605B003E9038E007C0001EEBC00FD80F015C270787801FC8FC3903FE003FD8007C133E90 C748131F03FCEBFF809239F801E1E0913A01F003C07002039038078030DBE00F1338DA07 C0EB0018020F49131C0380140C91381F001E4A013E130E023E15065C14FC495A5C495A13 075C4948150E011F021E130C91C7121F013E161C017E6E1318017CED8038490207133000 01923803C07049913801E1E049913800FF806C48ED1F00373C7CB740>I<147CEB01FEEB 07C790380F8380EB1F0181EB3E00A2137EA2137C137EA214015D140392C9FC5C140E6D5A 1418143802F090380FFFF05C6D5A04011300EE00FC6D6C1470011F1560013F15E0D977F0 495AD9E3F85CD801C31403260381FC91C7FC00075D48C66C130E486D130C486D131C003E 6D6C5A007EECC03091381FE07000FE010F5B6F5AEC07F96EB45A6C6D90C712306E5A157F 6C6C6D6C13604B6C13E03A3FC001EFE03C1FE003C7F803C03C0FF01F83FE0F802707FFFE 00B51200000101F8EB3FFE26003FC0EB07F034387DB53C>I<123C127EB4FCA21380A212 7F123D1201A412031300A25A1206120E120C121C5A5A126009177AB315>I<14C01301EB 0380EB0F00130E5B133C5B5BA2485A485AA212075B120F90C7FC5AA2121E123EA3123C12 7CA55AB0127CA5123C123EA3121E121FA27E7F12077F1203A26C7E6C7EA213787F131C7F 130FEB0380EB01C01300124A79B71E>I<12C07E1270123C121C7E120F6C7E6C7EA26C7E 6C7EA27F1378137C133C133EA2131E131FA37F1480A5EB07C0B0EB0F80A514005BA3131E 133EA2133C137C137813F85BA2485A485AA2485A48C7FC120E5A123C12705A5A124A7CB7 1E>I<156015F0B3A4007FB812C0B912E0A26C17C0C800F0C8FCB3A4156033327CAB3C> 43 D<123C127EB4FCA21380A2127F123D1201A412031300A25A1206120E120C121C5A5A 126009177A8715>II<123C127E12FFA4127E123C08087A8715> I<1530157815F8A215F01401A215E01403A215C01407A21580140FA215005CA2143EA214 3C147CA2147814F8A25C1301A25C1303A25C1307A2495AA291C7FC5BA2131E133EA2133C 137CA2137813F8A25B1201A25B1203A2485AA25B120FA290C8FC5AA2121E123EA2123C12 7CA2127812F8A25A12601D4B7CB726>II<13075B5B137FEA07FFB5FC13BFEAF83F1200B3B3A2497E007FB51280A3 19327AB126>IIII<000C14C0380FC00F90B5128015005C5C14F014C0D80C18 C7FC90C8FCA9EB0FC0EB7FF8EBF07C380FC03F9038001F80EC0FC0120E000CEB07E0A2C7 13F01403A215F8A41218127E12FEA315F0140712F8006014E01270EC0FC06C131F003C14 806CEB7F00380F80FE3807FFF8000113E038003F801D347CB126>I<14FE903807FF8001 1F13E090383F00F0017C13703901F801F8EBF003EA03E01207EA0FC0EC01F04848C7FCA2 48C8FCA35A127EEB07F0EB1FFC38FE381F9038700F809038E007C039FFC003E0018013F0 EC01F8130015FC1400A24814FEA5127EA4127F6C14FCA26C1301018013F8000F14F0EBC0 030007EB07E03903E00FC03901F81F806CB51200EB3FFCEB0FE01F347DB126>I<123012 3C003FB6FCA34814FEA215FC0070C7123800601430157015E04814C01401EC0380C7EA07 001406140E5C141814385CA25CA2495A1303A3495AA2130FA3131F91C7FCA25BA55BA913 1C20347CB126>III<123C127E12FFA4127E123C1200B0123C127E12FFA4127E123C08207A 9F15>I<123C127E12FFA4127E123C1200B0123C127E12FE12FFA3127F123F1203A41207 1206A3120E120C121C1238123012701260082F7A9F15>I<007FB812C0B912E0A26C17C0 CCFCAC007FB812C0B912E0A26C17C033147C9C3C>61 D63 DI<15E0A34A 7EA24A7EA34A7EA3EC0DFE140CA2EC187FA34A6C7EA202707FEC601FA202E07FECC00FA2 D901807F1507A249486C7EA301066D7EA2010E80010FB5FCA249800118C77EA24981163F A2496E7EA3496E7EA20001821607487ED81FF04A7ED8FFFE49B512E0A333367DB53A>I< B7FC16E016F83A03FC0003FE0001EC00FFEE7F80EE3FC0161F17E0160F17F0A617E0161F 17C0EE3F80EE7F0016FEED03FC90B612F05E9039FC0007FCED00FEEE3F80EE1FC0EE0FE0 17F0160717F8160317FCA617F81607A2EE0FF0EE1FE0163FEE7FC00003913803FF00B75A 16F816C02E337DB236>IIIIIII< B512FEA3000113006C5AB3B3A7487EB512FEA317337EB21C>I<017FB5FCA39038003FE0 EC1FC0B3B1127EB4FCA4EC3F805A0060140000705B6C13FE6C485A380F03F03803FFC0C6 90C7FC20357DB227>IIIIIIIII<90381FE00390387FFC0748B5FC3907F01FCF390F 8003FF48C7FC003E80814880A200788000F880A46C80A27E92C7FC127F13C0EA3FF013FF 6C13F06C13FF6C14C06C14F0C680013F7F01037F9038003FFF140302001380157F153FED 1FC0150F12C0A21507A37EA26CEC0F80A26C15006C5C6C143E6C147E01C05B39F1FC03F8 00E0B512E0011F138026C003FEC7FC22377CB42B>I<007FB712FEA390398007F001D87C 00EC003E0078161E0070160EA20060160600E01607A3481603A6C71500B3AB4A7E011FB5 12FCA330337DB237>IIII89 D<003FB612FCA39039F80007F813C090C7EA0FF0003EEC1FE0123C0038EC3FC00078EC7F 801270EDFF004A5AA20060495AA24A5A4A5AC7FC4A5A4A5AA24A5A4AC7FCA2495A495AA2 495A495AA24948130C495AA2495A49C7FCA24848141CA2485A485A1638485A4848147816 F84848130148481307153FB7FCA326337CB22F>II<0003130C48131C000E133848137000181360003813E0003013C0EA7001 00601380A2EAE00300C01300A400DE137800FF13FCEB83FEA2EA7F81A2383F00FC001E13 78171774B326>II<1320137013F8487EEA 03DEEA078F380F0780381E03C0383C01E0387800F000E0133800401310150C78B326>I< EB7F803803FFF0380F80FC381C003E003F133F6D6C7E6E7EA26E7EEA1F00C7FCA4EB01FF 131FEBFF873803FC07EA0FF0EA1FC0EA3F80127F13004815C05AA3140FA26C131F6C133B 3A3F8071F180391FC1E1FF2607FFC013003900FE003C22237DA126>97 DII<153FEC0FFFA3EC007F81AEEB07F0EB3FFCEBFC0F3901F003BF39 07E001FF48487E48487F8148C7FCA25A127E12FEAA127E127FA27E6C6C5BA26C6C5B6C6C 4813803A03F007BFFC3900F81E3FEB3FFCD90FE0130026357DB32B>III<151F90391FC07F809039FFF8E3C03901F07FC73907E03F033A0FC01F8380 9039800F8000001F80EB00074880A66C5CEB800F000F5CEBC01F6C6C48C7FCEBF07C380E FFF8380C1FC0001CC9FCA3121EA2121F380FFFFEECFFC06C14F06C14FC4880381F000100 3EEB007F4880ED1F8048140FA56C141F007C15006C143E6C5C390FC001F83903F007E0C6 B51280D91FFCC7FC22337EA126>IIIIII<2703F01FE013FF00FF90267FF80313C0903BF1E07C0F03E0 903BF3803E1C01F02807F7003F387FD803FE1470496D486C7EA2495CA2495CB3486C496C 487EB53BC7FFFE3FFFF0A33C217EA041>I<3903F01FC000FFEB7FF09038F1E0FC9038F3 807C3907F7007EEA03FE497FA25BA25BB3486CEB7F80B538C7FFFCA326217EA02B>II<3903F03F8000FFEBFFE09038 F3C0F89038F7007ED807FE7F6C48EB1F804914C049130F16E0ED07F0A3ED03F8A9150716 F0A216E0150F16C06D131F6DEB3F80160001FF13FC9038F381F89038F1FFE0D9F07FC7FC 91C8FCAA487EB512C0A325307EA02B>I<903807F00390383FFC07EBFC0F3901F8038F38 07E001000F14DF48486CB4FC497F123F90C77E5AA25A5AA9127FA36C6C5B121F6D5B000F 5B3907E003BF3903F0073F3800F81EEB3FF8EB0FE090C7FCAAED7F8091380FFFFCA32630 7DA029>I<3803E07C38FFE1FF9038E38F809038E71FC0EA07EEEA03ECA29038FC0F8049 C7FCA35BB2487EB512E0A31A217FA01E>II<1330A51370A313F0A21201A212031207381FFFFEB5FCA23803F000AF1403 A814073801F806A23800FC0EEB7E1CEB1FF8EB07E0182F7FAD1E>IIIII<3A7FFF807FF8A33A07F8001FC00003EC0F800001EC070015066C6C5BA26D131C017E 1318A26D5BA2EC8070011F1360ECC0E0010F5BA2903807E180A214F3010390C7FC14FBEB 01FEA26D5AA31478A21430A25CA214E05CA2495A1278D8FC03C8FCA21306130EEA701CEA 7838EA1FF0EA0FC025307F9F29>I<003FB512F0A2EB000F003C14E00038EB1FC00030EB 3F800070137F1500006013FE495A13035CC6485A495AA2495A495A49C7FC153013FE485A 12035B48481370485A001F14604913E0485A387F000348130F90B5FCA21C207E9F22>I< B712F8A22502809426>II E %EndDVIPSBitmapFont /Fo 134[50 1[72 1[55 33 39 44 1[55 50 55 83 28 55 33 28 1[50 1[44 55 44 55 50 7[72 72 1[72 72 66 55 72 1[61 78 72 94 66 78 1[39 78 78 61 66 72 72 66 72 7[50 50 50 50 50 50 50 50 50 50 1[25 46[{TeXBase1Encoding ReEncodeFont}53 99.6264 /Times-Bold rf /Fp 134[42 2[42 1[23 42 28 2[46 46 1[18 42 1[18 2[23 46 3[46 11[60 17[60 55 66[{ TeXBase1Encoding ReEncodeFont}16 83.022 /Helvetica rf %DVIPSBitmapFont: Fq cmsy9 9 21 /Fq 21 113 df<007FB712FCB812FEA26C16FC2F047A943C>0 D<123C127E12FFA4127E 123C08087A9615>I<130E131FA639700E01C000F8EB03E000FE130F00FF131F397F8E3F C0391FEEFF003803FFF8C613E0EB3F80A2EBFFE0000313F8381FEEFF397F8E3FC039FF0E 1FE000FE130F00F813030070EB01C0D8001FC7FCA6130E1B207BA226>3 D<15E081B3A4007FB812C0B912E0A26C17C0C800F0C8FCB3007FB812C0B912E0A26C17C0 33327CB13C>6 D15 D<023FB512FC49B612FE1307011F15FCD93FE0C8FC01FFC9FCEA01FCEA03F0485A485A5B 48CAFC5A123E5AA21278A212F8A25AA67EA21278A2127CA27E123F7E6C7E7F6C7E6C7EEA 01FC6CB4FCEB3FE06DB612FC010715FE1301D9003F14FC91C9FCAC001FB712FC4816FEA2 6C16FC2F3E7AB03C>18 D<171C177EEE01FEEE07FCEE1FF0EE7FC0923801FF00ED07FCED 1FF0ED7FC04A48C7FCEC07FCEC1FF0EC7FC04948C8FCEB07FCEB1FF0EB7FC04848C9FCEA 07FCEA1FF0EA7FC048CAFCA2EA7FC0EA1FF0EA07FCEA01FF38007FC0EB1FF0EB07FCEB01 FF9038007FC0EC1FF0EC07FCEC01FF9138007FC0ED1FF0ED07FCED01FF9238007FC0EE1F F0EE07FCEE01FEEE007E171C1700AC007FB712FCB812FEA26C16FC2F3E7AB03C>20 D<127012FCB4FCEA7FC0EA1FF0EA07FCEA01FF38007FC0EB1FF0EB07FCEB01FF9038007F C0EC1FF0EC07FCEC01FF9138007FC0ED1FF0ED07FCED01FF9238007FC0EE1FF0EE07FCEE 01FEA2EE07FCEE1FF0EE7FC0923801FF00ED07FCED1FF0ED7FC04A48C7FCEC07FCEC1FF0 EC7FC04948C8FCEB07FCEB1FF0EB7FC04848C9FCEA07FCEA1FF0EA7FC048CAFC12FC1270 CBFCAC007FB712FCB812FEA26C16FC2F3E7AB03C>I<013F16402601FFE015E04813F848 7F4813FF4880D83FC06D1301273E001FE014C048D907F8130300786D6C13070070D900FF EB0F8000F091387FE07F486EB512006F5B03075B6F5B03005B0040ED1F8033127C9B3C> 24 DI<05101420057814 F0DC01F813030407140F4C48EB1FE0DC3FC0EB7F80933AFF0001FE00DB03FCEB07F84B48 495ADB1FE0EB3FC0DB7F8001FFC7FC913A01FE0003FC4A48495ADA0FF0EB1FE0DA3FC0EB 7F809127FF0001FEC8FC4948495AD907F8EB0FF0D91FE0EB3FC0D97F8001FFC9FC494848 5AD803FCEB07F8D80FF0EB1FE0D83FC0EB7F80484849CAFC39FE0001FCA2397F8000FF6C 6C6D7ED80FF0EB1FE0D803FCEB07F8C6B4EB01FE6D6C6C7ED91FE0EB3FC0D907F8EB0FF0 D901FEEB03FC6D6C6D7E913A3FC0007F80DA0FF0EB1FE0DA03FCEB07F86E6C6D7E913A00 7F8000FFDB1FE0EB3FC0DB07F8EB0FF06F6C6D7EDB00FFEB01FE933A3FC0007F80DC0FF0 EB1FE0706CEB0FF004011403DC0078130044337CAC4D>28 D<00408000F0EB01E000FC14 F8B414FE6C6C6C7ED81FE0EB3FC0D807F8EB0FF0D801FEEB03FC6C6C6D7E903A3FC0007F 80D90FF0EB1FE0D903FCEB07F86D6C6D7E903A007F8000FFDA1FE0EB3FC0DA07F8EB0FF0 6E6C6D7EDA00FFEB01FE923A3FC0007F80DB0FF0EB1FE06F6C6D7EDB01FEEB03FC923A00 7F8000FFDC1FE0EB3FC0706CEB1FE0DC03F8EB07F0A2DC0FF0EB1FE04C48EB3FC0DC7F80 EBFF00923A01FE0003FCDB07F8EB0FF04B48495ADB3FC0EB7F809227FF0001FEC7FCDA03 FCEB07F84A48495ADA1FE0EB3FC0DA7F8001FFC8FC903A01FE0003FC4948495AD90FF0EB 1FE0D93FC0EB7F809027FF0001FEC9FC4848495AD807F8EB0FF0D81FE0EB3FC0D87F8001 FFCAFC4848485A00FC14F800F014E044337CAC4D>I<187018F0A2841878A2187C183C18 3E84A2727E727E85727E727E727E197F007FBA12C0BB12F0A26C19C0CCEA7F0019FC4E5A 4E5A4E5A614E5A4EC7FCA2183E183C187C1878A218F860A2187044287CA64D>33 D49 D<91383FFFF849B512FC1307011F14F8D93FE0C7FC01FFC8FCEA01FCEA03 F0485A485A5B48C9FC5A123E5AA21278A212F8A25AB712F816FCA216F800F0C9FC7EA212 78A2127CA27E123F7E6C7E7F6C7E6C7EEA01FC6CB4FCEB3FE06DB512F8010714FC1301D9 003F13F8262E7AA933>I<1630167816F8A2ED01F0A2ED03E0A2ED07C0A2ED0F80A2ED1F 00A2153EA25DA25DA24A5AA24A5AA24A5AA24A5AA24AC7FCA2143EA25CA25CA2495AA249 5AA2495AA2495AA249C8FCA2133EA25BA25BA2485AA2485AA2485AA2485AA248C9FCA212 3EA25AA25AA25A1260254675B500>54 D78 D102 D<12FCEAFFC0EA07F0EA01FC6C7E137F7F80131FB3A580130F6D7E6D7EEB01FC9038007F C0EC1FE0EC7FC0903801FC00EB03F0495A495A131F5CB3A5133F91C7FC5B13FE485AEA07 F0EAFFC000FCC8FC1B4B7BB726>I<126012F0B3B3B3B31260044B78B715>106 D<1930197819F8A2F001F0A2F003E0A2F007C0A2F00F80A2F01F00A2183EA260A260A24D 5AA24D5AA24D5AA24D5AA24DC7FCA2173EA25FA25FA24C5A13C000014B5AEA07E0000F4B 5AEA3FF000734B5AEAE3F800C14BC8FCEA01FC0000153E7F017E5C137F6D5CA26E485A13 1F6E485A130F6E485A13076E485A13036E48C9FC1301153E14FC01005B14FEEC7EF8147F 6E5AA26E5AA26E5AA26E5A92CAFC3D4C7B8340>112 D E %EndDVIPSBitmapFont /Fr 137[50 3[33 3[55 4[22 1[55 1[55 55 2[55 9[94 18[72 68[{TeXBase1Encoding ReEncodeFont}10 99.6264 /Helvetica rf /Fs 136[116 2[50 83 58 2[91 91 1[42 83 1[42 1[91 1[83 3[83 13[100 108 3[108 12[108 65[{TeXBase1Encoding ReEncodeFont}16 149.44 /Helvetica-Bold rf end %%EndProlog %%BeginSetup %%Feature: *Resolution 600dpi TeXDict begin %%BeginPaperSize: Letter letter %%EndPaperSize %%EndSetup %%Page: 1 1 1 0 bop 452 108 a Fs(Resilient)41 b(Ag)o(gregation)h(in)f(Sensor)h (Netw)m(orks)1595 510 y Fr(Da)n(vid)28 b(W)l(agner)2218 436 y Fq(\003)1308 598 y Fp(Univ)n(ersity)23 b(of)g(Calif)n(or)r(nia)h (at)g(Ber)q(k)n(ele)n(y)-152 1202 y Fo(ABSTRA)-5 b(CT)-152 1322 y Fn(This)34 b(pap)r(er)e(studies)h(securit)n(y)g(for)g(data)g (aggregation)i(in)e(sensor)-152 1409 y(net)n(w)n(orks.)h(Curren)n(t)21 b(aggregation)k(sc)n(hemes)c(w)n(ere)i(designed)f(with-)-152 1496 y(out)c(securit)n(y)f(in)h(mind)e(and)h(there)g(are)h(easy)g (attac)n(ks)g(against)h(them.)-152 1583 y(W)-6 b(e)32 b(examine)f(sev)n(eral)i(approac)n(hes)g(for)g(making)e(these)h (aggrega-)-152 1671 y(tion)c(sc)n(hemes)f(more)h(resilien)n(t)g (against)h(certain)f(attac)n(ks,)h(and)e(w)n(e)-152 1758 y(prop)r(ose)j(a)f(mathematical)g(framew)n(ork)g(for)h(formally)f(ev)l (aluating)-152 1845 y(their)d(securit)n(y)-6 b(.)-152 2040 y Fo(Categories)25 b(and)g(Subject)i(Descriptors)-152 2161 y Fn(D.4.6)g([)p Fm(Op)r(erating)32 b(Systems)p Fn(]:)i(Securit)n(y)25 b(and)g(Protection)-152 2356 y Fo(General)g(T)-9 b(erms)-152 2476 y Fn(Securit)n(y)-152 2671 y Fo(K)n(eyw)o(ords)-152 2792 y Fn(aggregation,)40 b(sensor)35 b(net)n(w)n(orks,)i(no)r(de)e(capture)f(attac)n(k,)j(m)n (ulti-)-152 2879 y(part)n(y)20 b(computation,)g(robust)g(statistics,)j (a)n(v)n(erage,)f(mean,)f(median)-152 3074 y Fo(1.)100 b(INTR)m(ODUCTION)-77 3182 y Fn(The)32 b(goal)h(of)g(this)f(pap)r(er)g (is)g(to)g(examine)f(secure)i(data)f(aggre-)-152 3269 y(gation)d(in)f(sensor)h(net)n(w)n(orks.)41 b(Sensor)28 b(net)n(w)n(orks)g(ha)n(v)n(e)g(b)r(een)f(pro-)-152 3356 y(p)r(osed)i(for)g(scien)n(ti\014c)f(data)h(collection,)i(en)n (vironmen)n(tal)c(monitor-)-152 3443 y(ing,)g(building)e(health)h (monitoring,)g(burglar)g(and)g(\014re)f(alarm)h(sys-)-152 3531 y(tems,)e(and)g(man)n(y)f(other)h(applications)i(in)n(v)n(olving)e (distributed)f(in-)-152 3618 y(teraction)i(with)f(the)g(ph)n(ysical)g (en)n(vironmen)n(t.)32 b(Man)n(y)24 b(of)h(these)f(ap-)-152 3705 y(plications)36 b(in)n(v)n(olv)n(e)e(a)h(distributed)f(system)g (of)h(sensors)h(measur-)-152 3792 y(ing)h(the)g(en)n(vironmen)n(t)e (from)h(man)n(y)f(v)l(an)n(tage)i(p)r(oin)n(ts)g(and)f(then)-152 3879 y(someho)n(w)h(aggregating)i(the)e(collected)h(data)f(to)g(form)f (a)h(global)-152 3967 y(summary)24 b(view)i(that)f(can)h(b)r(e)f(acted) h(up)r(on.)34 b(Consequen)n(tly)-6 b(,)25 b(data)-152 4054 y(aggregation)34 b(can)d(b)r(e)f(view)n(ed)h(as)h(an)f(imp)r (ortan)n(t)f(building)h(blo)r(c)n(k)-152 4141 y(in)22 b(sensor)g(net)n(w)n(orks.)33 b(Unfortunately)-6 b(,)22 b(ev)n(en)e(though)h(securit)n(y)g(has)-152 4228 y(b)r(een)27 b(iden)n(ti\014ed)f(as)h(a)h(ma)t(jor)f(c)n(hallenge)h(for)f(sensor)h (net)n(w)n(orks)f([2,)-152 4315 y(11],)36 b(curren)n(t)c(prop)r(osals)i (for)g(data)f(aggregation)i(proto)r(cols)f(ha)n(v)n(e)p -152 4375 797 4 v -152 4432 a Fq(\003)-113 4465 y Fn(da)n(w@cs.b)r(erk) n(eley)-6 b(.edu.)57 b(Supp)r(orted)32 b(b)n(y)g(D)n(ARP)-6 b(A)31 b(NEST)i(con-)-152 4540 y(tract)26 b(F33615-01-C-1895.)-152 4873 y Fl(Permission)g(to)f(mak)o(e)h(digital)i(or)d(hard)g(copies)i (of)e(all)h(or)f(part)g(of)g(this)h(w)o(ork)f(for)-152 4948 y(personal)f(or)f(classroom)g(use)f(is)g(granted)j(without)e(fee)h (pro)o(vided)g(that)f(copies)h(are)-152 5022 y(not)c(made)f(or)g (distrib)o(uted)i(for)e(pro\002t)g(or)g(commercial)i(adv)n(antage)h (and)d(that)h(copies)-152 5097 y(bear)e(this)f(notice)i(and)e(the)g (full)h(citation)h(on)e(the)g(\002rst)g(page.)25 b(T)-5 b(o)15 b(cop)o(y)j(otherwise,)g(to)-152 5172 y(republish,)g(to)e(post)f (on)h(serv)o(ers)g(or)g(to)g(redistrib)o(ute)i(to)e(lists,)g(requires)i (prior)e(speci\002c)-152 5246 y(permission)i(and/or)h(a)e(fee.)-152 5321 y Fk(SASN'04,)g Fl(October)i(25,)e(2004,)g(W)-5 b(ashington,)17 b(DC,)g(USA.)-152 5396 y(Cop)o(yright)j(2004)d(A)m(CM)g (1\25558113\255972\2551/04/0010)22 b(...)p Fn($)p Fl(5.00.)2040 1202 y Fn(not)28 b(b)r(een)f(designed)h(with)f(securit)n(y)h(in)f (mind,)g(and)g(consequen)n(tly)2040 1289 y(they)i(are)i(vulnerable)f (to)g(easy)g(attac)n(ks.)48 b(In)30 b(this)g(pap)r(er,)h(w)n(e)g(un-) 2040 1376 y(dertak)n(e)f(an)h(in-depth)e(study)g(of)j(securit)n(y)e (for)h(data)g(aggregation)2040 1463 y(in)26 b(sensor)g(net)n(w)n(orks.) 2115 1550 y(First,)33 b(w)n(e)e(sho)n(w)g(that)f(existing)h(prop)r (osals)i(for)e(data)g(aggrega-)2040 1637 y(tion)23 b(are)g(sub)t(ject)g (to)g(attac)n(k)g(\(Sections)g(3)g(and)f(4\).)34 b(When)21 b(a)i(single)2040 1725 y(sensor)29 b(no)r(de)g(can)g(b)r(e)f(captured,) h(compromised,)g(or)g(sp)r(o)r(ofed,)i(an)2040 1812 y(attac)n(k)n(er)26 b(can)h(often)g(manipulate)f(the)f(result)i(of)g(the)f(aggregation)2040 1899 y(op)r(eration)32 b(without)e(limit,)i(gaining)g(complete)e(con)n (trol)i(o)n(v)n(er)e(the)2040 1986 y(computed)d(aggregate.)44 b(This)29 b(is)g(undesirable.)42 b(F)-6 b(or)29 b(instance,)g(w)n(e) 2040 2073 y(sho)n(w)38 b(that)f(an)n(y)f(proto)r(col)j(that)d(computes) h(the)f(a)n(v)n(erage,)41 b(sum,)2040 2160 y(minim)n(um,)34 b(or)i(maxim)n(um)31 b(function)k(is)h(insecure)f(against)h(mali-)2040 2248 y(cious)27 b(data,)f(no)f(matter)g(ho)n(w)h(these)g(functions)g (are)g(computed.)2115 2335 y(In)16 b(resp)r(onse)i(to)f(this)h(threat,) h(w)n(e)e(in)n(tro)r(duce)g(a)h(theoretical)g(frame-)2040 2422 y(w)n(ork)34 b(for)h(mo)r(deling)f(the)f(securit)n(y)h(of)g(data)g (aggregation.)62 b(This)2040 2509 y(mo)r(del)21 b(insists)g(that)g(the) f(aggregation)k(function)c(m)n(ust)g(b)r(e)h(resilien)n(t)2040 2596 y(in)g(the)g(presence)g(of)h(arbitrary)f(c)n(hanges)h(to)f(a)h (small)f(subset)g(of)h(sen-)2040 2684 y(sor)27 b(observ)l(ations,)g (and)f(th)n(us)g(w)n(e)g(coin)h(the)f(term)f Fj(r)l(esilient)k(aggr)l (e-)2040 2771 y(gation)39 b Fn(to)32 b(refer)g(to)g(sc)n(hemes)f(that)h (satisfy)h(this)f(condition.)53 b(W)-6 b(e)2040 2858 y(formalize)38 b(this)f(condition)g(precisely)g(\(Section)g(5\))g(and)f (c)n(harac-)2040 2945 y(terize)26 b(whic)n(h)g(functions)h(ac)n(hiev)n (e)e(the)h(resilience)h(condition)f(\(Sec-)2040 3032 y(tion)32 b(6\).)51 b(F)-6 b(or)31 b(instance,)j(w)n(e)e(sho)n(w)f (that)g(the)g(median)g(is)g(a)h(more)2040 3119 y(robust)c(alternativ)n (e)g(to)g(the)g(a)n(v)n(erage.)41 b(Man)n(y)28 b(of)g(our)g (conclusions)2040 3207 y(are)c(consisten)n(t)h(with)f(in)n(tuition;)h (the)e(v)l(alue)h(of)g(our)g(mathematical)2040 3294 y(framew)n(ork)19 b(is)g(that)g(one)g(can)g(place)g(this)g(in)n(tuition)g(on)f(a)h (\014rm)f(foun-)2040 3381 y(dation,)31 b(and)f(one)f(can)h(analyze)g (systems)f(that)h(are)g(to)r(o)g(complex)2040 3468 y(for)d(in)n (tuition)e(to)h(pro)n(vide)f(su\016cien)n(t)h(guidance.)2115 3555 y(Finally)-6 b(,)23 b(w)n(e)f(in)n(tro)r(duce)f(sev)n(eral)h(tec)n (hniques)f(and)g(principles)h(for)2040 3642 y(ac)n(hieving)i(resilien)n (t)h(aggregation)h(in)d(new)h(proto)r(cols)h(\(Section)f(7\).)2040 3730 y(F)-6 b(or)33 b(instance,)h(w)n(e)f(sho)n(w)g(that)f(outlier)h (elimination)g(\(trimming\))2040 3817 y(is)e(a)g(p)r(o)n(w)n(erful)h (aggregation)h(tec)n(hnique)c(that)i(pro)n(vides)f(inheren)n(t)2040 3904 y(robustness)c(against)h(attac)n(k.)2115 3991 y(This)f(pap)r(er)g (mak)n(es)f(three)g(scien)n(ti\014c)h(con)n(tributions:)2151 4131 y Fq(\017)38 b Fn(The)30 b(pap)r(er)f(describ)r(es)i(attac)n(ks)f (on)f(standard)h(sc)n(hemes)f(for)2227 4219 y(data)23 b(aggregation)i(and)e(in)n(tro)r(duces)g(the)f(problem)g(of)i(secur-) 2227 4306 y(ing)d(aggregation)i(in)e(the)f(presence)h(of)h(malicious)f (or)g(sp)r(o)r(ofed)2227 4393 y(data.)71 b(The)38 b(attac)n(ks)h(are)f (quite)f(ob)n(vious,)42 b(but)37 b(the)g(crisp)2227 4480 y(problem)27 b(statemen)n(t)h(w)n(e)g(giv)n(e)h(has)f(not)h(app)r (eared)f(in)g(prin)n(t)2227 4567 y(b)r(efore.)2151 4711 y Fq(\017)38 b Fn(The)f(pap)r(er)f(prop)r(oses)i(a)e(mathematical)g (theory)g(of)i(secu-)2227 4798 y(rit)n(y)31 b(for)i(aggregation.)54 b(This)33 b(theory)e(lets)h(us)f(quan)n(tify)-6 b(,)33 b(in)2227 4885 y(a)24 b(principled)h(w)n(a)n(y)-6 b(,)24 b(the)g(robustness)g(of)h(an)f(aggregation)j(op-)2227 4972 y(erator)g(against)h(malicious)f(data.)36 b(The)27 b(pap)r(er)f(dra)n(ws)h(no)n(v)n(el)2227 5060 y(connections)c(to)g (statistical)i(estimation)e(theory)g(and)f(to)h(the)2227 5147 y(\014eld)i(of)i(robust)e(statistics.)2151 5290 y Fq(\017)38 b Fn(The)e(pap)r(er)g(iden)n(ti\014es)g(tec)n(hniques)f (for)i(aggregation)h(that)2227 5378 y(pro)n(vide)23 b(robustness)h (against)h(attac)n(k.)34 b(The)24 b(tec)n(hniques)f(are)p eop %%Page: 2 2 2 1 bop -55 621 a @beginspecial 153 @llx 514 @lly 507 @urx 666 @ury 2160 @rwi @setspecial %%BeginDocument: arch3.eps %!PS-Adobe-2.0 EPSF-2.0 %%Creator: dvips(k) 5.86 Copyright 1999 Radical Eye Software %%Title: arch3.dvi %%BoundingBox: 153 514 507 666 %%EndComments %DVIPSWebPage: (www.radicaleye.com) %DVIPSCommandLine: dvips -E -o arch3.eps arch3 %DVIPSParameters: dpi=600, compressed %DVIPSSource: TeX output 2003.05.10:2309 %%BeginProcSet: texc.pro %! /TeXDict 300 dict def TeXDict begin/N{def}def/B{bind def}N/S{exch}N/X{S N}B/A{dup}B/TR{translate}N/isls false N/vsize 11 72 mul N/hsize 8.5 72 mul N/landplus90{false}def/@rigin{isls{[0 landplus90{1 -1}{-1 1}ifelse 0 0 0]concat}if 72 Resolution div 72 VResolution div neg scale isls{ landplus90{VResolution 72 div vsize mul 0 exch}{Resolution -72 div hsize mul 0}ifelse TR}if Resolution VResolution vsize -72 div 1 add mul TR[ matrix currentmatrix{A A round sub abs 0.00001 lt{round}if}forall round exch round exch]setmatrix}N/@landscape{/isls true N}B/@manualfeed{ statusdict/manualfeed true put}B/@copies{/#copies X}B/FMat[1 0 0 -1 0 0] N/FBB[0 0 0 0]N/nn 0 N/IEn 0 N/ctr 0 N/df-tail{/nn 8 dict N nn begin /FontType 3 N/FontMatrix fntrx N/FontBBox FBB N string/base X array /BitMaps X/BuildChar{CharBuilder}N/Encoding IEn N end A{/foo setfont}2 array copy cvx N load 0 nn put/ctr 0 N[}B/sf 0 N/df{/sf 1 N/fntrx FMat N df-tail}B/dfs{div/sf X/fntrx[sf 0 0 sf neg 0 0]N df-tail}B/E{pop nn A definefont setfont}B/Cw{Cd A length 5 sub get}B/Ch{Cd A length 4 sub get }B/Cx{128 Cd A length 3 sub get sub}B/Cy{Cd A length 2 sub get 127 sub} B/Cdx{Cd A length 1 sub get}B/Ci{Cd A type/stringtype ne{ctr get/ctr ctr 1 add N}if}B/id 0 N/rw 0 N/rc 0 N/gp 0 N/cp 0 N/G 0 N/CharBuilder{save 3 1 roll S A/base get 2 index get S/BitMaps get S get/Cd X pop/ctr 0 N Cdx 0 Cx Cy Ch sub Cx Cw add Cy setcachedevice Cw Ch true[1 0 0 -1 -.1 Cx sub Cy .1 sub]/id Ci N/rw Cw 7 add 8 idiv string N/rc 0 N/gp 0 N/cp 0 N{ rc 0 ne{rc 1 sub/rc X rw}{G}ifelse}imagemask restore}B/G{{id gp get/gp gp 1 add N A 18 mod S 18 idiv pl S get exec}loop}B/adv{cp add/cp X}B /chg{rw cp id gp 4 index getinterval putinterval A gp add/gp X adv}B/nd{ /cp 0 N rw exit}B/lsh{rw cp 2 copy get A 0 eq{pop 1}{A 255 eq{pop 254}{ A A add 255 and S 1 and or}ifelse}ifelse put 1 adv}B/rsh{rw cp 2 copy get A 0 eq{pop 128}{A 255 eq{pop 127}{A 2 idiv S 128 and or}ifelse} ifelse put 1 adv}B/clr{rw cp 2 index string putinterval adv}B/set{rw cp fillstr 0 4 index getinterval putinterval adv}B/fillstr 18 string 0 1 17 {2 copy 255 put pop}for N/pl[{adv 1 chg}{adv 1 chg nd}{1 add chg}{1 add chg nd}{adv lsh}{adv lsh nd}{adv rsh}{adv rsh nd}{1 add adv}{/rc X nd}{ 1 add set}{1 add clr}{adv 2 chg}{adv 2 chg nd}{pop nd}]A{bind pop} forall N/D{/cc X A type/stringtype ne{]}if nn/base get cc ctr put nn /BitMaps get S ctr S sf 1 ne{A A length 1 sub A 2 index S get sf div put }if put/ctr ctr 1 add N}B/I{cc 1 add D}B/bop{userdict/bop-hook known{ bop-hook}if/SI save N @rigin 0 0 moveto/V matrix currentmatrix A 1 get A mul exch 0 get A mul add .99 lt{/QV}{/RV}ifelse load def pop pop}N/eop{ SI restore userdict/eop-hook known{eop-hook}if showpage}N/@start{ userdict/start-hook known{start-hook}if pop/VResolution X/Resolution X 1000 div/DVImag X/IEn 256 array N 2 string 0 1 255{IEn S A 360 add 36 4 index cvrs cvn put}for pop 65781.76 div/vsize X 65781.76 div/hsize X}N /p{show}N/RMat[1 0 0 -1 0 0]N/BDot 260 string N/Rx 0 N/Ry 0 N/V{}B/RV/v{ /Ry X/Rx X V}B statusdict begin/product where{pop false[(Display)(NeXT) (LaserWriter 16/600)]{A length product length le{A length product exch 0 exch getinterval eq{pop true exit}if}{pop}ifelse}forall}{false}ifelse end{{gsave TR -.1 .1 TR 1 1 scale Rx Ry false RMat{BDot}imagemask grestore}}{{gsave TR -.1 .1 TR Rx Ry scale 1 1 false RMat{BDot} imagemask grestore}}ifelse B/QV{gsave newpath transform round exch round exch itransform moveto Rx 0 rlineto 0 Ry neg rlineto Rx neg 0 rlineto fill grestore}B/a{moveto}B/delta 0 N/tail{A/delta X 0 rmoveto}B/M{S p delta add tail}B/b{S p tail}B/c{-4 M}B/d{-3 M}B/e{-2 M}B/f{-1 M}B/g{0 M} B/h{1 M}B/i{2 M}B/j{3 M}B/k{4 M}B/w{0 rmoveto}B/l{p -4 w}B/m{p -3 w}B/n{ p -2 w}B/o{p -1 w}B/q{p 1 w}B/r{p 2 w}B/s{p 3 w}B/t{p 4 w}B/x{0 S rmoveto}B/y{3 2 roll p a}B/bos{/SS save N}B/eos{SS restore}B end %%EndProcSet %%BeginProcSet: special.pro %! TeXDict begin/SDict 200 dict N SDict begin/@SpecialDefaults{/hs 612 N /vs 792 N/ho 0 N/vo 0 N/hsc 1 N/vsc 1 N/ang 0 N/CLIP 0 N/rwiSeen false N /rhiSeen false N/letter{}N/note{}N/a4{}N/legal{}N}B/@scaleunit 100 N /@hscale{@scaleunit div/hsc X}B/@vscale{@scaleunit div/vsc X}B/@hsize{ /hs X/CLIP 1 N}B/@vsize{/vs X/CLIP 1 N}B/@clip{/CLIP 2 N}B/@hoffset{/ho X}B/@voffset{/vo X}B/@angle{/ang X}B/@rwi{10 div/rwi X/rwiSeen true N}B /@rhi{10 div/rhi X/rhiSeen true N}B/@llx{/llx X}B/@lly{/lly X}B/@urx{ /urx X}B/@ury{/ury X}B/magscale true def end/@MacSetUp{userdict/md known {userdict/md get type/dicttype eq{userdict begin md length 10 add md maxlength ge{/md md dup length 20 add dict copy def}if end md begin /letter{}N/note{}N/legal{}N/od{txpose 1 0 mtx defaultmatrix dtransform S atan/pa X newpath clippath mark{transform{itransform moveto}}{transform{ itransform lineto}}{6 -2 roll transform 6 -2 roll transform 6 -2 roll transform{itransform 6 2 roll itransform 6 2 roll itransform 6 2 roll curveto}}{{closepath}}pathforall newpath counttomark array astore/gc xdf pop ct 39 0 put 10 fz 0 fs 2 F/|______Courier fnt invertflag{PaintBlack} if}N/txpose{pxs pys scale ppr aload pop por{noflips{pop S neg S TR pop 1 -1 scale}if xflip yflip and{pop S neg S TR 180 rotate 1 -1 scale ppr 3 get ppr 1 get neg sub neg ppr 2 get ppr 0 get neg sub neg TR}if xflip yflip not and{pop S neg S TR pop 180 rotate ppr 3 get ppr 1 get neg sub neg 0 TR}if yflip xflip not and{ppr 1 get neg ppr 0 get neg TR}if}{ noflips{TR pop pop 270 rotate 1 -1 scale}if xflip yflip and{TR pop pop 90 rotate 1 -1 scale ppr 3 get ppr 1 get neg sub neg ppr 2 get ppr 0 get neg sub neg TR}if xflip yflip not and{TR pop pop 90 rotate ppr 3 get ppr 1 get neg sub neg 0 TR}if yflip xflip not and{TR pop pop 270 rotate ppr 2 get ppr 0 get neg sub neg 0 S TR}if}ifelse scaleby96{ppr aload pop 4 -1 roll add 2 div 3 1 roll add 2 div 2 copy TR .96 dup scale neg S neg S TR}if}N/cp{pop pop showpage pm restore}N end}if}if}N/normalscale{ Resolution 72 div VResolution 72 div neg scale magscale{DVImag dup scale }if 0 setgray}N/psfts{S 65781.76 div N}N/startTexFig{/psf$SavedState save N userdict maxlength dict begin/magscale true def normalscale currentpoint TR/psf$ury psfts/psf$urx psfts/psf$lly psfts/psf$llx psfts /psf$y psfts/psf$x psfts currentpoint/psf$cy X/psf$cx X/psf$sx psf$x psf$urx psf$llx sub div N/psf$sy psf$y psf$ury psf$lly sub div N psf$sx psf$sy scale psf$cx psf$sx div psf$llx sub psf$cy psf$sy div psf$ury sub TR/showpage{}N/erasepage{}N/copypage{}N/p 3 def @MacSetUp}N/doclip{ psf$llx psf$lly psf$urx psf$ury currentpoint 6 2 roll newpath 4 copy 4 2 roll moveto 6 -1 roll S lineto S lineto S lineto closepath clip newpath moveto}N/endTexFig{end psf$SavedState restore}N/@beginspecial{SDict begin/SpecialSave save N gsave normalscale currentpoint TR @SpecialDefaults count/ocount X/dcount countdictstack N}N/@setspecial{ CLIP 1 eq{newpath 0 0 moveto hs 0 rlineto 0 vs rlineto hs neg 0 rlineto closepath clip}if ho vo TR hsc vsc scale ang rotate rwiSeen{rwi urx llx sub div rhiSeen{rhi ury lly sub div}{dup}ifelse scale llx neg lly neg TR }{rhiSeen{rhi ury lly sub div dup scale llx neg lly neg TR}if}ifelse CLIP 2 eq{newpath llx lly moveto urx lly lineto urx ury lineto llx ury lineto closepath clip}if/showpage{}N/erasepage{}N/copypage{}N newpath}N /@endspecial{count ocount sub{pop}repeat countdictstack dcount sub{end} repeat grestore SpecialSave restore end}N/@defspecial{SDict begin}N /@fedspecial{end}B/li{lineto}B/rl{rlineto}B/rc{rcurveto}B/np{/SaveX currentpoint/SaveY X N 1 setlinecap newpath}N/st{stroke SaveX SaveY moveto}N/fil{fill SaveX SaveY moveto}N/ellipse{/endangle X/startangle X /yrad X/xrad X/savematrix matrix currentmatrix N TR xrad yrad scale 0 0 1 startangle endangle arc savematrix setmatrix}N end %%EndProcSet TeXDict begin 40258437 52099154 1000 600 600 (arch3.dvi) @start %DVIPSBitmapFont: Fa cmr17 20.74 3 /Fa 3 62 df[<1638167816F0ED01E0ED03C0ED0780ED0F00151E153E5D5D4A5A4A5AA2 4A5A4A5A141F92C7FC143E147E147C14FC495AA2495AA2495AA2495AA2495AA2133F91C8 FC5B137EA213FE5B1201A25B1203A3485AA4485AA4485AA5123F5BA5127FA390C9FCA65A B3A87EA67FA3123FA57F121FA56C7EA46C7EA46C7EA312017FA212007F137EA2137F7F80 131FA26D7EA26D7EA26D7EA26D7EA26D7E147C147E143E8081140F6E7E6E7EA26E7E6E7E 157C81151E81ED0780ED03C0ED01E0ED00F016781638>37 172 113 256 61 40 D[<12E07E12787E7E7E6C7E6C7E7F6C7E6C7E137C7FA27F6D7E8013076D7E 801301806D7EA2147EA280A26E7EA26E7EA2811407811403A281140181A2140081A3157F A4ED3F80A4ED1FC0A516E0150FA516F0A31507A616F8B3A816F0A6150FA316E0A5151F16 C0A5ED3F80A4ED7F00A415FEA35D1401A25D14035DA214075D140F5DA24A5AA24AC7FCA2 147EA25CA2495A5C13035C495A130F5C49C8FC133EA25B5B485A485A5B485A48C9FC121E 5A5A5A5A>37 172 120 256 61 I<007FBF12C0C012E0A4003F1EC0D3FCB3A8003FBF12 C0C012E0A46C1EC06B2678BD7C>61 D E %EndDVIPSBitmapFont %DVIPSBitmapFont: Fb cmr12 14.4 9 /Fb 9 58 df<14075C5C147F5C1307133F000FB5FCB6FC13F913C1EAF0011200B3B3B3A7 497F010F13E0B712FEA4274F75CE3B>49 DII<160F5EA25E5EA25E5DA25D5DA25D151E151C153C5D15 7015F04A5A5D14035D4A5A5C140E5C143C14385C14F05C495A13035C130749C7FC130E13 1E5B133813785B5B1201485A5B120748C8FC120E121E5A123812785AB912F0A4C8000190 C7FCAF4B7F4B7F020FB612E0A434507DCF3B>I<000316C001C0140301F8141F903AFFC0 03FF8091B612005E5E5E16E016804BC7FC019F13F8018113800180C9FCB0EC0FF0ECFFFE 01836D7E903987F01FE090399F0007F801BE6D7E01F86D7E496D7E49EC7F805BEE3FC049 15E0C9121F17F0A317F8160FA317FCA5120EEA3F80487E12FF7FA217F85B161F5B48C813 F012700078ED3FE0A26C16C0167F6CEDFF80001F16006C6C495A6C6C13036C6CEB07F8D8 01F8EB1FF06CB4EB7FE06DB51280011F49C7FC010713F8010013C02E517ACE3B>II<121EA2121F13F090B812C0A4481780A218005FA200 3CC9123C00385E0078167017F000704B5A5F16034C5A94C7FC485D161E5EC9123816785E 5E15014B5A5E15074BC8FCA2151E153E153C157C157815F8A24A5AA21403A25D1407A214 0FA25D141FA3143FA3147F5DA414FFA65BAC6D90C9FC143C32537AD03B>III E %EndDVIPSBitmapFont %DVIPSBitmapFont: Fc cmmi12 20.74 5 /Fc 5 122 df58 DI102 D120 DI E %EndDVIPSBitmapFont end %%EndProlog %%BeginSetup %%Feature: *Resolution 600dpi TeXDict begin %%EndSetup 1 0 bop 0 setgray 3 setlinewidth np 1366 1456 25 0.00 360.00 arc fil 0 setgray np 1366 1456 25 0.00 360.00 arc st 3 setlinewidth np 1366 1456 25 0.00 360.00 arc st 0 setgray 3 setlinewidth np 1668 1456 25 0.00 360.00 arc fil 0 setgray np 1668 1456 25 0.00 360.00 arc st 3 setlinewidth np 1668 1456 25 0.00 360.00 arc st 0 setgray 3 setlinewidth np 1970 1456 25 0.00 360.00 arc fil 0 setgray np 1970 1456 25 0.00 360.00 arc st 3 setlinewidth np 1970 1456 25 0.00 360.00 arc st 0 setgray 3 setlinewidth np 2272 1456 25 0.00 360.00 arc fil 0 setgray np 2272 1456 25 0.00 360.00 arc st 3 setlinewidth np 2272 1456 25 0.00 360.00 arc st 0 setgray 3 setlinewidth np 2574 1456 25 0.00 360.00 arc fil 0 setgray np 2574 1456 25 0.00 360.00 arc st 3 setlinewidth np 2574 1456 25 0.00 360.00 arc st 0 setgray 3 setlinewidth np 1064 1456 25 0.00 360.00 arc fil 0 setgray np 1064 1456 25 0.00 360.00 arc st 3 setlinewidth np 1064 1456 25 0.00 360.00 arc st 0 setgray 3 setlinewidth np 2876 1456 25 0.00 360.00 arc fil 0 setgray np 2876 1456 25 0.00 360.00 arc st 3 setlinewidth np 2876 1456 25 0.00 360.00 arc st 0 setgray 3 setlinewidth np 762 1456 25 0.00 360.00 arc fil 0 setgray np 762 1456 25 0.00 360.00 arc st 3 setlinewidth np 762 1456 25 0.00 360.00 arc st 0 setgray 3 setlinewidth np 3178 1456 25 0.00 360.00 arc fil 0 setgray np 3178 1456 25 0.00 360.00 arc st 3 setlinewidth np 3178 1456 25 0.00 360.00 arc st 0 setgray 3 setlinewidth np 1894 475 a 2045 475 li 2045 626 li 1894 626 li closepath fil 0 setgray np 1894 475 a 2045 475 li 2045 626 li 1894 626 li closepath st 3 setlinewidth np 1894 475 a 2045 475 li 2045 626 li 1894 626 li closepath st 3 setlinewidth np 1063 1457 a 1894 626 li st 3 setlinewidth np 1862 680 a 1894 626 li 1841 658 li st 3 setlinewidth np 1667 1457 a 1932 626 li st 3 setlinewidth np 1928 688 a 1932 626 li 1899 679 li st 3 setlinewidth np 2271 1419 a 2007 626 li st 3 setlinewidth np 2040 678 a 2007 626 li 2012 688 li st 3 setlinewidth np 2574 1457 a 2007 626 li st 3 setlinewidth np 2054 668 a 2007 626 li 2029 684 li st 3 setlinewidth np 2876 1457 a 2045 626 li st 3 setlinewidth np 2099 658 a 2045 626 li 2077 680 li st 3 setlinewidth np 761 1457 a 1894 626 li st 3 setlinewidth np 1854 674 a 1894 626 li 1836 650 li st 3 setlinewidth np 1970 1457 a 1970 626 li st 3 setlinewidth np 1985 687 a 1970 626 li 1955 687 li st 3 setlinewidth np 1365 1457 a 1932 626 li st 3 setlinewidth np 1910 684 a 1932 626 li 1885 668 li st 3 setlinewidth np 3178 1457 a 2045 626 li st 3 setlinewidth np 2103 650 a 2045 626 li 2085 674 li st 686 1683 a Fc(x)782 1708 y Fb(1)988 1683 y Fc(x)1084 1708 y Fb(2)1290 1683 y Fc(x)1386 1708 y Fb(3)2159 588 y Fc(y)54 b Fa(=)48 b Fc(f)18 b Fa(\()p Fc(x)2725 613 y Fb(1)2788 588 y Fc(;)28 b(x)2959 613 y Fb(2)3022 588 y Fc(;)g(:)h(:)f(:)h(;)f(x)3495 613 y Fb(9)3558 588 y Fa(\))1592 1683 y Fc(x)1688 1708 y Fb(4)1895 1683 y Fc(x)1991 1708 y Fb(5)2197 1683 y Fc(x)2293 1708 y Fb(6)2499 1683 y Fc(x)2595 1708 y Fb(7)2801 1683 y Fc(x)2897 1708 y Fb(8)3103 1683 y Fc(x)3199 1708 y Fb(9)p eop %%Trailer end userdict /end-hook known{end-hook}if %%EOF %%EndDocument @endspecial -152 868 a Fm(Figure)33 b(1:)43 b(An)32 b(abstract)h(sensor)f(net)n(w)n(ork)g(arc)n(hitecture,)-152 955 y(with)39 b(inessen)n(tial)g(underlying)g(ph)n(ysical)g(structures) g(ab-)-152 1042 y(stracted)e(a)n(w)n(a)n(y)-7 b(.)56 b(W)-7 b(e)35 b(ha)n(v)n(e)g Fi(n)h Fm(sensor)g(no)r(des)g(\(the)g (small)-152 1129 y(circles\),)46 b(eac)n(h)41 b(with)h(a)f(separate)g (secure)g(c)n(hannel)h(to)g(a)-152 1216 y(single)34 b(trusted)g(base)e (station)i(\(the)g(large)f(solid)h(square\).)-152 1304 y(The)41 b Fi(i)p Fm(th)h(sensor)f(sends)g(measuremen)n(t)e Fi(x)1321 1312 y Fh(i)1388 1304 y Fm(to)j(the)f(base)-152 1391 y(station,)33 b(and)f(the)f(base)g(station)h(uses)f(the)h (function)h Fi(f)39 b Fm(to)-152 1478 y(compute)30 b(the)g(aggregate)g Fi(y)s Fm(.)38 b(In)30 b(this)g(picture,)h Fi(n)22 b Fn(=)f(9)p Fm(.)35 1722 y Fn(not)g(no)n(v)n(el,)i(but)d(the)h(analysis) i(of)f(their)g(p)r(erformance)f(in)h(this)35 1809 y(setting)e(is)g (new.)33 b(This)20 b(should)f(pro)n(vide)g(helpful)h(guidance)g(to)35 1896 y(sensor)30 b(net)n(w)n(ork)e(implemen)n(tors)g(in)g(selecting)i (appropriate)35 1983 y(aggregation)e(op)r(erators.)-152 2181 y Fo(2.)100 b(B)m(A)-5 b(CKGR)m(OUND)-152 2389 y Fg(The)34 b(ar)m(c)o(hitectur)m(e)o(.)k Fn(A)33 b(sensor)i(net)n(w)n (ork)f(is)h(a)f(distributed)g(sys-)-152 2476 y(tem)23 b(designed)g(for)h(in)n(teracting)g(with)g(the)f(ph)n(ysical)g(en)n (vironmen)n(t.)-152 2563 y(A)31 b(sensor)h(net)n(w)n(ork)f(migh)n(t)f (con)n(tain)i(h)n(undreds)d(or)j(thousands)f(of)-152 2650 y(tin)n(y)-6 b(,)28 b(lo)n(w-cost,)h(lo)n(w-p)r(o)n(w)n(er)g (sensor)f(no)r(des.)41 b(Man)n(y)27 b(arc)n(hitectures)-152 2737 y(also)35 b(use)f(more)f(p)r(o)n(w)n(erful)h(base)g(stations,)j (whic)n(h)d(are)g(in)f(a)h(one-)-152 2825 y(to-man)n(y)f(asso)r (ciation)k(with)e(sensor)g(no)r(des.)62 b(Often,)37 b(one)e(forms)-152 2912 y(a)c(tree)f(with)g(a)h(base)f(station)h(at)f(the)g(ro)r(ot)h(and) e(sensor)i(no)r(des)g(at)-152 2999 y(the)22 b(lea)n(v)n(es.)33 b(An)21 b(aggregation)j(transaction)f(b)r(egins)f(b)n(y)e(broadcast-) -152 3086 y(ing)34 b(the)g(query)e(do)n(wn)i(the)f(tree)h(from)f(the)h (base)g(station)g(to)g(the)-152 3173 y(lea)n(v)n(es.)49 b(Then,)31 b(the)f(sensor)h(no)r(des)g(measure)e(their)i(en)n(vironmen) n(t)-152 3261 y(and)h(send)h(their)f(measuremen)n(t)f(bac)n(k)h(up)g (the)g(tree)g(to)h(the)f(base)-152 3348 y(station.)53 b(Finally)-6 b(,)34 b(the)d(base)h(station)g(p)r(erforms)g(an)f (aggregation)-152 3435 y(computation)h(to)h(obtain)h(the)e(aggregate.) 58 b(Th)n(us,)35 b(sensor)f(no)r(des)-152 3522 y(act)26 b(as)h(data)f(sources,)g(and)g(the)f(base)h(station)h(acts)f(as)g(a)g (sink.)-152 3709 y Fg(An)31 b(abstr)o(act)e(model.)41 b Fn(In)31 b(this)g(pap)r(er,)i(w)n(e)f(will)h(abstract)f(a)n(w)n(a)n (y)-152 3796 y(some)j(inessen)n(tial)g(features.)62 b(W)-6 b(e)34 b(consider)i(only)e(a)h(single)g(base)-152 3883 y(station)27 b(and)e Fi(n)h Fn(asso)r(ciated)h(sensor)g(no)r(des.)35 b(A)n(t)24 b(some)i(p)r(oin)n(t,)g(eac)n(h)-152 3970 y(sensor)i(no)r(de)f(tak)n(es)g(a)h(measuremen)n(t)d(and)i(rep)r(orts)g (the)g(observ)n(ed)-152 4058 y(v)l(alue)k Fi(x)96 4066 y Fh(i)153 4058 y Fn(to)g(the)g(base)h(station.)51 b(The)31 b(base)h(station's)g(goal)h(is)f(to)-152 4145 y(compute)e(an)i (aggregate)h(v)l(alue)e Fi(y)j Fn(that)d(summarizes)f(the)h(sensor)-152 4232 y(readings)f Fi(x)199 4240 y Ff(1)233 4232 y Fi(;)13 b(:)g(:)h(:)f(;)g(x)448 4240 y Fh(n)519 4232 y Fn(using)29 b(the)f(aggregation)j(function)e Fi(f)8 b Fn(;)31 b(th)n(us,)-152 4319 y Fi(y)d Fn(=)e Fi(f)8 b Fn(\()p Fi(x)119 4327 y Ff(1)153 4319 y Fi(;)13 b(:)h(:)f(:)g(;)g(x)368 4327 y Fh(n)410 4319 y Fn(\).)42 b(Our)28 b(attac)n(ks)g(and)g(defenses)h (ignore)g(the)f(in-)-152 4406 y(ner)23 b(w)n(orkings)g(of)h(the)e(sp)r (eci\014c)i(aggregation)h(and)d(comm)n(unication)-152 4493 y(proto)r(cols)e(used,)g(suc)n(h)e(as)h(ho)n(w)g(data)f(is)h (routed.)32 b(Instead,)20 b(w)n(e)f(fo)r(cus)-152 4581 y(only)26 b(on)g(the)f(function)h Fi(f)34 b Fn(computed)24 b(b)n(y)h(the)g(base)h(station.)36 b(Con-)-152 4668 y(sequen)n(tly)-6 b(,)22 b(w)n(e)h(ignore)g(the)f(structure)f(of)i(the)f(m)n(ulti-hop)f (net)n(w)n(ork,)-152 4755 y(assuming)27 b(only)f(that)h(eac)n(h)g (sensor)g(no)r(de)g(has)g(a)g(separate)g(link)g(to)-152 4842 y(the)h(base)h(station.)43 b(W)-6 b(e)28 b(depict)f(this)i (abstracted)f(arc)n(hitecture)h(in)-152 4929 y(Figure)e(1.)-152 5116 y Fg(Thr)m(eat)g(model.)40 b Fn(W)-6 b(e)29 b(will)i(assume)e (that)g(eac)n(h)h(sensor)g(no)r(de)f(has)-152 5203 y(a)c(secure)f(c)n (hannel)g(bac)n(k)f(to)h(the)g(base)g(station)h(for)g(rep)r(orting)g (data)-152 5290 y(measuremen)n(ts.)39 b(Moreo)n(v)n(er,)29 b(w)n(e)f(assume)f(these)h(secure)g(c)n(hannels)-152 5378 y(are)c(indep)r(enden)n(t:)32 b(capture)24 b(of)g(one)f(sensor)i (no)r(de)e(migh)n(t)g(compro-)2040 -69 y(mise)f(the)f(con)n(ten)n(ts)h (of)g(that)g(no)r(de's)g(c)n(hannel)g(to)g(the)f(base)h(station,)2040 19 y(but)i(it)g(will)i(not)e(rev)n(eal)h(an)n(ything)e(ab)r(out)i (other)f(no)r(des')h(c)n(hannels.)2040 106 y(F)-6 b(or)30 b(instance,)i(eac)n(h)f(sensor)f(migh)n(t)g(share)g(a)h(p)r(er-no)r(de) e(symmet-)2040 193 y(ric)34 b(k)n(ey)f(with)h(the)g(base)g(station)h (and)e(use)h(this)g(k)n(ey)f(to)h(encrypt)2040 280 y(its)26 b(data.)35 b(As)25 b(a)g(consequence)h(of)g(these)f(assumptions,)h(w)n (e)f(do)h(not)2040 367 y(need)19 b(to)h(w)n(orry)g(ab)r(out)g(sp)r(o)r (o\014ng)h(or)f(in)n(terception)g(of)g(data)g(in)g(tran-)2040 454 y(sit.)39 b(This)28 b(lea)n(v)n(es)f(only)g(the)g(question)g(of)g (whether)g(the)g(endp)r(oin)n(ts)2040 542 y(are)f(trust)n(w)n(orth)n(y) f(or)h(not.)2115 629 y(The)20 b(main)f(threat)g(w)n(e)i(will)g (consider)f(is)g(that)g(of)g(malicious)h(data.)2040 716 y(One)e(w)n(a)n(y)g(that)g(malicious)h(data)f(can)h(b)r(e)f(injected)g (is)h(through)f(no)r(de)2040 803 y(compromise)37 b(or)g(no)r(de)g (capture)g(attac)n(ks:)58 b(if)38 b(a)f(sensor)h(no)r(de)f(is)2040 890 y(captured,)27 b(rev)n(erse-engineered,)g(or)g(otherwise)h(comes)e (under)g(ad-)2040 977 y(v)n(ersarial)k(con)n(trol,)g(w)n(e)f(can)g(no)g (longer)g(trust)g(its)g(measuremen)n(ts.)2040 1065 y(Alternativ)n(ely) -6 b(,)19 b(if)g(an)f(adv)n(ersary)g(is)h(able)g(to)f(fo)r(ol)i(the)e (sensor's)h(mea-)2040 1152 y(suring)f(elemen)n(t|p)r(erhaps)f(b)n(y)g (sub)t(jecting)h(it)g(to)g(un)n(usual)f(temp)r(er-)2040 1239 y(ature,)32 b(ligh)n(ting,)h(or)d(other)h(sp)r(o)r(ofed)g(en)n (vironmen)n(tal)f(conditions,)2040 1326 y(for)j(instance|then)e(the)g (sensor)h(no)r(de's)h(measuremen)n(t)c(is)k(com-)2040 1413 y(promised.)49 b(Th)n(us,)32 b(measuremen)n(ts)d(can)h(often)h(b)r (e)g(compromised)2040 1500 y(ev)n(en)25 b(if)h(no)r(des)g(are)h (protected)e(b)n(y)g(tamp)r(er-resistan)n(t)g(pac)n(k)l(aging.)2115 1588 y(W)-6 b(e)22 b(will)i(use)f(a)g(Byzan)n(tine)g(fault)g(mo)r(del,) g(where)g(the)g(adv)n(ersary)2040 1675 y(can)36 b(inject)f(arbitrarily) i(c)n(hosen)e(malicious)h(data)g(readings)g(at)f(a)2040 1762 y(few)30 b(sensors.)44 b(Of)28 b(course,)i(compromised)e(no)r(des) h(ma)n(y)e(b)r(eha)n(v)n(e)h(in)2040 1849 y(arbitrarily)c(malicious)g (w)n(a)n(ys,)g(whic)n(h)f(means)f(that)h(measuremen)n(ts)2040 1936 y(from)j(compromised)g(no)r(des)h(are)g(under)e(the)h(complete)h (con)n(trol)g(of)2040 2023 y(the)k(adv)n(ersary)-6 b(.)50 b(W)-6 b(e)31 b(conserv)l(ativ)n(ely)g(assume)g(that)f(all)i(compro-) 2040 2111 y(mised)24 b(no)r(des)h(collude,)g(or)g(are)g(under)f(the)g (con)n(trol)h(of)g(a)g(single)h(at-)2040 2198 y(tac)n(k)n(er.)35 b(An)24 b(arc)n(het)n(ypical)i(attac)n(k)g(in)n(v)n(olv)n(es)g (compromised)e(no)r(des)2040 2285 y(rep)r(orting)34 b(b)r(ogus)g (measuremen)n(ts)f(in)g(an)h(attempt)e(to)i(sk)n(ew)g(the)2040 2372 y(computed)24 b(aggregate.)2115 2459 y(Compromise)d(of)i(sensor)f (no)r(des)g(is)g(indeed)g(a)g(real)g(threat)g(in)g(real)2040 2547 y(sensor)35 b(net)n(w)n(orks.)62 b(Because)35 b(sensor)h(no)r(des) e(m)n(ust)g(b)r(e)g(lo)n(w-cost,)2040 2634 y(w)n(e)23 b(often)g(cannot)f(a\013ord)g(to)h(moun)n(t)e(them)f(in)j(ph)n(ysical)f (pac)n(k)l(aging)2040 2721 y(that)e(pro)n(vides)f(a)i(high)e(lev)n(el)h (of)h(tamp)r(er)e(resistance.)34 b(Because)21 b(sen-)2040 2808 y(sor)g(no)r(des)f(m)n(ust)e(b)r(e)i(deplo)n(y)n(ed)f(in)n(to)h (the)g(en)n(vironmen)n(t,)f(w)n(e)i(cannot)2040 2895 y(pro)n(vide)d(ph)n(ysical)h(securit)n(y)g(or)g(con)n(trol)h(access)g (to)f(them.)31 b(And,)19 b(b)r(e-)2040 2982 y(cause)28 b(sensor)f(no)r(des)g(m)n(ust)f(b)r(e)h(deplo)n(y)n(ed)f(in)h(large)h (n)n(um)n(b)r(ers,)e(the)2040 3070 y(adv)n(ersary)k(is)h(a\013orded)g (man)n(y)e(opp)r(ortunities)i(to)f(compromise)g(a)2040 3157 y(sensor)d(no)r(de.)2115 3244 y(Of)g(course,)i(the)e(adv)n (ersary's)h(capabilities)h(are)f(not)f(unlimited.)2040 3331 y(Some)20 b(cost)h(or)h(luc)n(k)e(will)i(b)r(e)f(required)f(for)h (eac)n(h)g(no)r(de)g(that)g(the)f(ad-)2040 3418 y(v)n(ersary)h(wishes)h (to)g(compromise.)32 b(Therefore,)24 b(w)n(e)e(should)f(assume)2040 3505 y(that)30 b(the)f(adv)n(ersary)h(can)g(compromise)g(only)g(a)g (limited)g(n)n(um)n(b)r(er)2040 3593 y(of)g(sensor)g(no)r(des:)42 b(p)r(erhaps)29 b(one)h(or)g(t)n(w)n(o)f(or)h(three,)g(but)f(not)g (half)2040 3680 y(of)d(the)f(net)n(w)n(ork.)34 b(W)-6 b(e)25 b(require)g(that)g(securit)n(y)g(degrade)g(gracefully)2040 3767 y(as)d(the)g(n)n(um)n(b)r(er)d(of)k(compromised)e(no)r(des)g(gro)n (ws.)35 b(In)21 b(this)h(resp)r(ect,)2040 3854 y(our)k(main)e(hop)r(e)i (is)g(for)g(\\safet)n(y)h(in)e(n)n(um)n(b)r(ers":)33 b(if)27 b(w)n(e)e(can)h(build)f(a)2040 3941 y(net)n(w)n(ork)g(that)f (is)i(robust)e(in)h(the)g(presence)g(of)g(a)h(few)g(malicious)f(or)2040 4028 y(captured)g(sensor)i(no)r(des,)f(w)n(e)g(will)h(b)r(e)f(in)f (great)i(shap)r(e.)2115 4116 y(In)40 b(this)g(pap)r(er,)45 b(our)40 b(analysis)i(will)g(assume)e(that)h(base)f(sta-)2040 4203 y(tions)20 b(remain)f(trust)n(w)n(orth)n(y)g(and)g(unassailable.) 34 b(This)20 b(assumption)2040 4290 y(seems)31 b(plausible:)47 b(base)32 b(stations)h(are)f(rarer)g(and)f(hence)g(w)n(e)h(can)2040 4377 y(sp)r(end)27 b(more)g(on)g(them,)f(so)i(it)f(ma)n(y)f(b)r(e)h (feasible)i(to)f(enclose)g(them)2040 4464 y(in)23 b(high-qualit)n(y)f (tamp)r(er)g(resistan)n(t)i(enclosures)g(or)f(to)g(place)h(them)2040 4552 y(in)i(ph)n(ysically)f(secure,)i(access-con)n(trolled)g(lo)r (cations.)2040 4738 y Fg(Security)14 b(goals.)38 b Fn(W)-6 b(e)17 b(fo)r(cus)h(on)f Fj(inte)l(grity)p Fn(.)33 b(The)18 b(adv)n(ersary)f(should)2040 4825 y(not)23 b(b)r(e)f(able)h(to)g (a\013ect)g(the)f(result)h(of)g(the)f(aggregation)j(op)r(eration,)2040 4913 y(as)31 b(computed)d(at)j(the)e(base)i(station.)48 b(This)31 b(should)f(remain)g(true)2040 5000 y(ev)n(en)25 b(in)h(the)f(presence)h(of)g(a)g(few)h(compromised)e(sensor)h(no)r (des.)2115 5087 y(Unfortunately)-6 b(,)33 b(p)r(erfect)g(in)n(tegrit)n (y)f(is)h(rarely)g(attainable.)56 b(By)2040 5174 y(manipulating)17 b(the)g(readings)h(at)f(a)g(few)i(compromised)d(sensor)i(no)r(des,)2040 5261 y(the)h(attac)n(k)n(er)g(can)h(usually)f(a\013ect)h(the)f (computed)e(aggregate,)23 b(ev)n(en)2040 5349 y(if)g(only)e(negligibly) -6 b(,)24 b(no)e(matter)f(ho)n(w)h(clev)n(er)g(the)g(proto)r(col.)35 b(There-)p eop %%Page: 3 3 3 2 bop -152 -69 a Fn(fore,)46 b(w)n(e)41 b(relax)h(our)e(goal)j(sligh) n(tly)e(and)f(ask)h(for)h Fj(appr)l(oximate)-152 19 y(inte)l(grity)7 b Fn(:)54 b(the)35 b(adv)n(ersary)g(should)g(ha)n(v)n(e)f(only)h(a)g (limited)g(in\015u-)-152 106 y(ence)24 b(on)g(the)g(result)g(of)h(the)f (aggregation)i(computation.)33 b(In)24 b(other)-152 193 y(w)n(ords,)29 b(if)g Fi(y)h Fn(denotes)d(the)g(result)h(in)g(the)f (absence)h(of)g(an)g(attac)n(k)n(er)-152 280 y(and)d Fi(y)38 248 y Fe(\003)98 280 y Fn(the)f(result)h(after)g(an)g(attac)n (k)n(er)f(in)n(terv)n(enes,)h(then)f(w)n(e)h(wish)-152 367 y Fq(j)p Fi(y)-90 335 y Fe(\003)-42 367 y Fq(\000)12 b Fi(y)s Fq(j)22 b Fn(to)h(b)r(e)g(b)r(ounded,)g(preferably)g(b)n(y)f (some)h(small)g(v)l(alue.)33 b(No-)-152 454 y(tice)h(that)f(if)i Fq(j)p Fi(y)316 423 y Fe(\003)374 454 y Fq(\000)22 b Fi(y)s Fq(j)33 b Fn(is)h(negligible)h(compared)e(to)h(the)f(random)-152 542 y(noise)27 b(in)g Fi(y)s Fn(,)f(the)g(attac)n(k)n(er)g(has)h (gained)g(little.)37 b(Because)28 b(measure-)-152 629 y(men)n(ts)d(of)j(the)e(ph)n(ysical)g(w)n(orld)h(are)g(inheren)n(tly)f (noisy)-6 b(,)26 b(w)n(e)h(exp)r(ect)-152 716 y(appro)n(ximate)d(in)n (tegrit)n(y)g(to)h(form)f(an)h(adequate)f(securit)n(y)g(goal)i(for)-152 803 y(most)f(applications.)-77 890 y(W)-6 b(e)23 b(separate)g(the)g(sp) r(eci\014cation)h(of)g(desired)f(aggregation)i(func-)-152 977 y(tionalit)n(y)38 b(from)e(the)h(proto)r(col)h(used)e(to)h (implemen)n(t)e(or)i(ac)n(hiev)n(e)-152 1065 y(this)30 b(functionalit)n(y)-6 b(.)48 b(W)-6 b(e)29 b(assume)h(the)f (functionalit)n(y)i(is)f(giv)n(en)g(as)-152 1152 y(a)j(function)f Fi(f)8 b Fn(;)35 b(giv)n(en)d(sensor)h(readings)g Fi(x)1126 1160 y Ff(1)1160 1152 y Fi(;)13 b(:)g(:)g(:)h(;)f(x)1375 1160 y Fh(n)1417 1152 y Fn(,)34 b(w)n(e)e(wish)h(to)-152 1239 y(compute)g(the)g(aggregate)j Fi(y)h Fn(=)e Fi(f)8 b Fn(\()p Fi(x)951 1247 y Ff(1)985 1239 y Fi(;)13 b(:)g(:)g(:)h(;)f(x) 1200 1247 y Fh(n)1242 1239 y Fn(\).)58 b(A)33 b(v)l(alid)h(proto-)-152 1326 y(col)f(migh)n(t)e(use)h(an)n(y)g(mec)n(hanism)f(whatso)r(ev)n(er) i(to)f(compute)f(this)-152 1413 y(aggregate.)37 b(See)26 b(Figure)g(1)g(for)g(an)g(abstract)g(view.)-77 1500 y(The)g(cen)n(tral) g(question)f(for)i(secure)f(aggregation)i(is)e(as)h(follo)n(ws:)p -91 1565 1871 4 v -91 1851 4 286 v -39 1640 a Fj(Question.)61 b Fn(Whic)n(h)35 b(aggregation)i(functionalities)f(can)f(b)r(e)-39 1727 y(securely)28 b(and)g(meaningfully)g(computed,)f(in)h(the)g (presence)-39 1814 y(of)e(a)g(few)h(compromised)e(no)r(des?)p 1776 1851 V -91 1854 1871 4 v -152 1953 a(The)e(follo)n(wing)h (sections)g(are)e(directed)g(at)h(answ)n(ering)g(this)f(cen)n(tral)-152 2040 y(question.)-152 2227 y Fg(Caveats.)40 b Fn(W)-6 b(e)19 b(do)h(not)g(consider)g(con\014den)n(tialit)n(y)-6 b(,)21 b(a)n(v)l(ailabilit)n(y)-6 b(,)21 b(or)-152 2314 y(p)r(erformance)30 b(in)f(this)g(pap)r(er.)46 b(W)-6 b(e)29 b(do)g(not)g(consider)h(in-net)n(w)n(ork)-152 2401 y(aggregation;)25 b(in)20 b(our)h(mo)r(del,)g(trusted)f(base)h (stations)g(are)g(the)f(only)-152 2488 y(aggregation)28 b(p)r(oin)n(ts.)-152 2675 y Fg(Connections)39 b(to)j(secur)m(e)c (multi\255party)k(computation.)e Fn(The)-152 2762 y(cen)n(tral)24 b(question)f(for)h(secure)f(aggregation)j(carries)e(some)f(connec-)-152 2850 y(tion)36 b(to)f(the)f(area)i(of)g(secure)g(m)n(ulti-part)n(y)d (computation.)62 b(It)34 b(is)-152 2937 y(kno)n(wn)19 b(that)g(an)n(y)f(functionalit)n(y)i(that)e(can)h(b)r(e)g(computed)f (with)h(the)-152 3024 y(help)26 b(of)g(a)g(trusted)f(third)g(part)n(y)g (can)g(also)i(b)r(e)f(computed)e(without)-152 3111 y(it,)31 b(using)f(generic)g(m)n(ulti-part)n(y)e(computation.)45 b(The)29 b(connection)-152 3198 y(to)e(sensor)h(net)n(w)n(orks)e(is)i (natural:)37 b(w)n(e)27 b(ma)n(y)e(think)h(of)h(aggregation)-152 3285 y(in)k(sensor)g(net)n(w)n(orks)f(as)h(an)g(instance)g(of)g(m)n (ulti-part)n(y)d(computa-)-152 3373 y(tion)33 b Fj(with)39 b Fn(a)33 b(trusted)g(third)f(part)n(y)-6 b(,)34 b(where)f(the)g (functionalit)n(y)g(is)-152 3460 y(giv)n(en)23 b(b)n(y)e(the)h (aggregation)j(function)e Fi(f)31 b Fn(and)22 b(where)h(the)f(base)h (sta-)-152 3547 y(tion)j(pla)n(ys)g(the)f(role)i(of)f(the)f(trusted)h (third)f(part)n(y)-6 b(.)-77 3634 y(The)19 b(question)g(of)g(whic)n(h)g (aggregation)i(functionalities)g Fi(f)27 b Fn(can)19 b(b)r(e)-152 3721 y(meaningfully)k(computed)e(in)i(sensor)g(net)n(w)n (orks)g(no)n(w)g(corresp)r(onds)-152 3808 y(to)37 b(the)f(follo)n(wing) k(question)c(ab)r(out)h(m)n(ulti-part)n(y)d(computation:)-152 3896 y(Whic)n(h)e(functionalities)h Fi(f)41 b Fn(can)32 b(b)r(e)g(meaningfully)f(computed)g(b)n(y)-152 3983 y(a)g(proto)r(col)h (for)f(secure)g(m)n(ulti-part)n(y)d(computation,)k(when)e(some)-152 4070 y(parties)35 b(migh)n(t)f(b)r(eha)n(v)n(e)f(maliciously)i(b)n(y)e (submitting)h(b)r(ogus)g(in-)-152 4157 y(puts?)53 b(In)32 b(the)f(general)j(case,)g(this)f(question)e(do)r(es)i(not)f(seem)g(to) -152 4244 y(ha)n(v)n(e)19 b(b)r(een)g(considered)h(in)f(the)g (literature)h(on)g(generic)g(m)n(ulti-part)n(y)-152 4332 y(computation.)41 b(The)29 b(literature)g(has)f(fo)r(cused)h(on)f (demonstrating)-152 4419 y(that)33 b(an)n(ything)g(that)g(can)h(b)r(e)f (computed)f(with)i(a)f(trusted)g(third)-152 4506 y(part)n(y)23 b(can)g(b)r(e)g(computed)e(without)i(a)g(trusted)g(third)f(part)n(y)-6 b(.)33 b(Ho)n(w-)-152 4593 y(ev)n(er,)23 b(whether)e(or)g(not)h(w)n(e)f (assume)g(that)g(w)n(e)h(ha)n(v)n(e)f(a)h(trusted)e(third)-152 4680 y(part)n(y)-6 b(,)25 b(there)h(is)g(no)g(guaran)n(tee)g(that)g (what)g(w)n(e)g(w)n(an)n(t)g(to)g(compute)-152 4767 y(is)g(meaningful)g (in)f(the)g(presence)h(of)g(malicious)h(participan)n(ts.)35 b(F)-6 b(or)-152 4855 y(instance,)30 b(if)e(a)g(group)g(of)h (cryptographers)f(wishes)h(to)f(learn)h(their)-152 4942 y(a)n(v)n(erage)34 b(salary)g(without)f(disclosing)i(an)n(ything)e (else,)j(there)d(is)g(a)-152 5029 y(p)r(oten)n(tial)h(problem:)48 b(whether)33 b(or)g(not)g(w)n(e)h(use)f(a)g(trusted)f(third)-152 5116 y(part)n(y)-6 b(,)28 b(a)g(single)i(malicious)e(cryptographer)g (can)g(cause)h(the)f(com-)-152 5203 y(puted)18 b(result)h(to)g(deviate) g(tremendously)e(from)h(the)h(correct)g(result.)-77 5290 y(T)-6 b(o)24 b(put)e(another)h(w)n(a)n(y)-6 b(,)24 b(the)e (di\013erence)i(b)r(et)n(w)n(een)f(this)g(w)n(ork)g(and)-152 5378 y(previous)h(researc)n(h)f(on)h(generic)g(m)n(ulti-part)n(y)d (computation)h(is)i(the)2040 -69 y(di\013erence)k(b)r(et)n(w)n(een)g (sp)r(eci\014cation)h(and)e(implemen)n(tation.)40 b(Prior)2040 19 y(w)n(ork)26 b(has)g(sho)n(wn)f(that)h(an)n(y)f(functionalit)n(y)h (y)n(ou)e(can)i(sp)r(ecify)-6 b(,)26 b(y)n(ou)2040 106 y(can)c(implemen)n(t;)f(w)n(e)g(fo)r(cus)i(on)e(asking)h(whether)f(a)h (sp)r(eci\014ed)f(func-)2040 193 y(tionalit)n(y)26 b(is)h(meaningful)e (in)h(its)g(o)n(wn)g(righ)n(t.)2040 380 y Fg(Applications)h(to)h (system)f(r)l(ob)n(ustness.)38 b Fn(Ev)n(en)29 b(in)g(the)g(absence) 2040 467 y(of)38 b(an)f(adv)n(ersary)-6 b(,)40 b(resilien)n(t)e (aggregation)i(functions)d(ma)n(y)f(ha)n(v)n(e)2040 554 y(utilit)n(y)f(in)g(impro)n(ving)g(robustness)h(against)g(random)f (faults.)64 b(A)2040 641 y(single)26 b(corrupted)e(measuremen)n(t)g (should)g(not)h(cause)h(large)g(errors)2040 728 y(in)33 b(the)g(computed)e(aggregate.)59 b(Standard)33 b(aggregates,)k(suc)n(h) c(as)2040 816 y(the)19 b(a)n(v)n(erage,)j(cannot)e(ac)n(hiev)n(e)g (this)f(goal)i(\(see)g(Section)e(3\);)j(a)e(single)2040 903 y(malfunctioning)38 b(sensor)g(returning)g(random)e(results)j(can)e (sk)n(ew)2040 990 y(the)25 b(a)n(v)n(erage)i(b)n(y)d(an)i(un)n(b)r (ounded)e(amoun)n(t.)2115 1077 y(Of)c(course,)h(an)n(y)e(aggregate)j (that)d(is)h(resilien)n(t)h(against)g(malicious)2040 1164 y(attac)n(k)32 b(will)h(also)g(b)r(e)e(resilien)n(t)i(against)g (random)d(failures.)55 b(Con-)2040 1251 y(sequen)n(tly)-6 b(,)27 b(resilien)n(t)h(aggregation)i(ma)n(y)c(also)j(b)r(e)f(of)g (indep)r(enden)n(t)2040 1339 y(in)n(terest)e(for)g(its)h(use)e(in)h (impro)n(ving)f(o)n(v)n(erall)h(system)f(reliabilit)n(y)-6 b(.)2040 1554 y Fo(3.)99 b(A)-9 b(TT)g(A)k(CKS)15 b(ON)g(EXISTING)g(A) -5 b(GGREGA)c(TION)2214 1671 y(PRIMITIVES)2040 1878 y Fg(An)21 b(e)n(xample)o(.)39 b Fn(T)-6 b(o)24 b(giv)n(e)h(the)e(\015a)n (v)n(or)h(of)h(the)e(kind)g(of)i(attac)n(k)f(p)r(ossi-)2040 1965 y(ble)j(on)g(naiv)n(e)g(aggregation)j(proto)r(cols,)f(let)e(us)g (consider)h(a)g(whim-)2040 2053 y(sical)h(example.)39 b(Imagine)27 b(a)g(large)i(building)e(with)h(a)f(con)n(trol)h(net-)2040 2140 y(w)n(ork)33 b(that)f(regulates)h(inside)g(temp)r(eratures)e(b)n (y)h(measuring)g(the)2040 2227 y(temp)r(erature)22 b(in)h(eac)n(h)g(ro) r(om,)g(computing)f(the)g(building-wide)h(a)n(v-)2040 2314 y(erage,)j(and)f(deciding)f(whether)h(to)g(turn)f(on)g(the)g(air)i (conditioning)2040 2401 y(or)36 b(not)g(according)h(to)f(whether)g(the) g(a)n(v)n(erage)g(temp)r(erature)f(ex-)2040 2488 y(ceeds)26 b(some)g(threshold.)2115 2576 y(No)n(w)37 b(imagine)g(a)h(building)f(o) r(ccupan)n(t)g(who)g(prefers)h(climates)2040 2663 y(m)n(uc)n(h)25 b(co)r(oler)k(than)e(the)g(system)f(is)i(programmed)e(to)h(pro)n(vide.) 39 b(It)2040 2750 y(is)32 b(easy)g(to)f(see)h(that)f(she)h(can)f (manipulate)g(the)g(system,)h(simply)2040 2837 y(b)n(y)25 b(holding)i(her)f(cigarette)i(ligh)n(ter)e(under)g(a)g(single)i (sensor.)37 b(Wh)n(y)2040 2924 y(do)r(es)32 b(this)g(w)n(ork?)53 b(The)33 b(k)n(ey)d(observ)l(ation)j(is)f(that)f(she)h(has)g(arti-)2040 3011 y(\014cially)c(increased)g(this)g(sensor's)g(temp)r(erature)f (reading)h(b)n(y)e(h)n(un-)2040 3099 y(dreds)i(of)h(degrees,)i(whic)n (h)d(will)i(often)f(ha)n(v)n(e)f(the)g(e\013ect)g(of)h(raising)2040 3186 y(the)23 b(building-wide)h(a)n(v)n(erage)g(temp)r(erature)e(ab)r (o)n(v)n(e)h(the)g(threshold,)2040 3273 y(b)r(ecause)31 b(h)n(uge)g(c)n(hanges)g(to)g(a)g(single)h(sensor)g(reading)f(can)g (cause)2040 3360 y(noticeable)d(c)n(hanges)f(to)f(the)g(a)n(v)n(erage.) 38 b(This)27 b(maliciously-sk)n(ew)n(ed)2040 3447 y(a)n(v)n(erage)35 b(can)g(thereb)n(y)f(trigger)h(the)g(air)g(conditioning)g(unit)g(in)n (to)2040 3534 y(turning)25 b(on)h(when)g(it)f(otherwise)i(w)n(ould)f (not)g(ha)n(v)n(e.)2115 3622 y(W)-6 b(e)29 b(see)i(that)f(a)g(single)h (attac)n(k)n(er)f(has)g(succeeded)g(in)g(hijac)n(king)2040 3709 y(con)n(trol)g(of)h(the)e(building's)h(climate)g(merely)e(b)n(y)h (fo)r(oling)j(a)d(single)2040 3796 y(sensor.)60 b(This)35 b(means)e(that)h(our)g(h)n(yp)r(othetical)g(climate)g(con)n(trol)2040 3883 y(net)n(w)n(ork)26 b(is)h(fragile)h(against)g(malicious)f(attac)n (k.)36 b(Ev)n(en)26 b(though)g(in)2040 3970 y(this)34 b(example)g(the)g(op)r(eration)h(of)g(the)f(air)h(conditioning)g(unit)f (is)2040 4058 y(probably)27 b(not)g(particularly)h(securit)n (y-critical,)h(this)e(illustrates)i(a)2040 4145 y(general)23 b(problem)f(that)g(can)g(ha)n(v)n(e)f(more)h(serious)h(consequences)g (in)2040 4232 y(some)34 b(real)g(systems.)59 b(This)34 b(is)g(a)g(failure)h(mo)r(de)f(that)f(w)n(e)h(w)n(ould)2040 4319 y(prefer)26 b(to)g(a)n(v)n(oid.)2040 4506 y Fg(Some)14 b(functionalities)h(ar)m(e)f(inher)m(ently)f(insecur)m(e)o(.)38 b Fn(Earlier,)22 b(w)n(e)2040 4593 y(suggested)j(separating)f(the)g(c)n (hoice)g(of)g(aggregation)i(functionalit)n(y)2040 4680 y(\(sp)r(eci\014ed)20 b(b)n(y)f(the)h(function)g Fi(f)8 b Fn(\))20 b(from)g(the)f(w)n(a)n(y)h(our)g(proto)r(col)i(com-)2040 4767 y(putes)31 b(this)g(aggregate.)53 b(F)-6 b(or)31 b(instance,)j(in)d(the)f(building-con)n(trol)2040 4855 y(example)f(ab)r(o)n(v)n(e,)i(w)n(e)f(had)f Fi(f)8 b Fn(\()p Fi(x)2978 4863 y Ff(1)3013 4855 y Fi(;)13 b(:)g(:)g(:)g(;)g(x) 3227 4863 y Fh(n)3269 4855 y Fn(\))28 b(=)g(\()p Fi(x)3489 4863 y Ff(1)3542 4855 y Fn(+)20 b Fq(\001)13 b(\001)g(\001)20 b Fn(+)g Fi(x)3855 4863 y Fh(n)3897 4855 y Fn(\))p Fi(=n)p Fn(.)2040 4942 y(Notice)27 b(that)g(our)g(example)f(attac)n(k)h(did)g (not)f(dep)r(end)g(in)h(an)n(y)g(w)n(a)n(y)2040 5029 y(on)g(ho)n(w)h(w)n(e)g(compute)e(this)h(function.)40 b(In)27 b(other)g(w)n(ords,)i(it)e(is)h(the)2040 5116 y(sp)r(eci\014cation)37 b(itself)g(that)e(w)n(as)h(fundamen)n(tally)f (fault)n(y)-6 b(,)38 b(not)d(the)2040 5203 y(implemen)n(tation.)2115 5290 y(This)28 b(is)f(a)h(p)r(oin)n(t)f(of)h(suc)n(h)f(general)h (applicabilit)n(y)g(that)f(it)g(b)r(ears)2040 5378 y(rep)r(eating.)49 b(Some)29 b(functions)i(simply)e(cannot)i(b)r(e)f(computed)f(se-)p eop %%Page: 4 4 4 3 bop -152 -69 a Fn(curely)39 b(in)g(the)g(presence)g(of)h (compromised)e(no)r(des,)43 b(no)d(matter)-152 19 y(what)23 b(proto)r(col)i(w)n(e)e(use.)34 b(Because)24 b(a)f(single)h(no)r(de)e (can)h(exert)g(total)-152 106 y(con)n(trol)i(o)n(v)n(er)f(the)g (building-wide)h(a)n(v)n(erage)g(temp)r(erature,)f(the)f(a)n(v-)-152 193 y(erage)i(temp)r(erature)e(is)h(not)f(a)h(meaningful)g(quan)n(tit)n (y)e(when)i(no)r(des)-152 280 y(are)j(compromised.)-77 367 y(In)j(the)g(remainder)h(of)g(this)g(section,)i(w)n(e)e(will)h (presen)n(t)f(attac)n(ks)-152 454 y(on)24 b(sev)n(eral)g(p)r(opular)f (aggregation)j(functions.)34 b(These)24 b(attac)n(ks)f(are)-152 542 y(straigh)n(tforw)n(ard)29 b(and)d(ob)n(vious)g(up)r(on)g(insp)r (ection,)h(once)f(one)h(rec-)-152 629 y(ognizes)32 b(the)d(imp)r (ortance)h(of)g(resilience;)k(ho)n(w)n(ev)n(er,)d(w)n(e)g(ha)n(v)n(e)e (not)-152 716 y(seen)35 b(these)g(attac)n(ks)g(describ)r(ed)g(b)r (efore)h(in)f(the)f(sensor)i(net)n(w)n(ork)-152 803 y(literature.)-152 990 y Fg(The)g(aver)o(a)o(g)o(e)d(is)j(insecur)m(e)o(.)i Fn(W)-6 b(e)35 b(sa)n(w)h(earlier)h(that)e(the)f(a)n(v)n(er-)-152 1077 y(age,)47 b(giv)n(en)42 b(b)n(y)f Fi(f)8 b Fn(\()p Fi(x)485 1085 y Ff(1)519 1077 y Fi(;)13 b(:)g(:)h(:)f(;)g(x)734 1085 y Fh(n)776 1077 y Fn(\))48 b(=)g(\()p Fi(x)1036 1085 y Ff(1)1098 1077 y Fn(+)27 b Fq(\001)13 b(\001)h(\001)28 b Fn(+)f Fi(x)1434 1085 y Fh(n)1476 1077 y Fn(\))p Fi(=n)p Fn(,)47 b(is)42 b(in-)-152 1164 y(secure)d(in)g(the)f(presence)h(of)g (a)g(single)h(malicious)f(sensor)g(no)r(de.)-152 1251 y(Sa)n(y)34 b(that)g(sensor)i(no)r(de)e(1)h(is)g(compromised.)60 b(Then)35 b(b)n(y)e(substi-)-152 1339 y(tuting)39 b(the)g(fak)n(e)h (reading)g Fi(x)743 1307 y Fe(\003)743 1352 y Ff(1)818 1339 y Fn(in)f(place)h(of)g(the)f(real)i(measure-)-152 1426 y(men)n(t)c Fi(x)99 1434 y Ff(1)133 1426 y Fn(,)k(the)c(a)n(v)n (erage)h(is)h(c)n(hanged)e(from)h Fi(y)44 b Fn(=)d Fi(f)8 b Fn(\()p Fi(x)1520 1434 y Ff(1)1554 1426 y Fi(;)13 b(:)h(:)f(:)g(;)g (x)1769 1434 y Fh(n)1811 1426 y Fn(\))-152 1513 y(to)32 b Fi(y)-11 1481 y Fe(\003)56 1513 y Fn(=)f Fi(f)8 b Fn(\()p Fi(x)266 1481 y Fe(\003)266 1526 y Ff(1)302 1513 y Fi(;)13 b(x)380 1521 y Ff(2)414 1513 y Fi(;)g(:)g(:)g(:)g(;)g(n)p Fn(\))32 b(=)f Fi(y)23 b Fn(+)e(\()p Fi(x)999 1481 y Fe(\003)999 1526 y Ff(1)1056 1513 y Fq(\000)f Fi(x)1180 1521 y Ff(1)1214 1513 y Fn(\))p Fi(=n)p Fn(.)53 b(Since)32 b(the)f(at-)-152 1600 y(tac)n(k)n(er)24 b(can)h(c)n(ho)r(ose)g Fi(x)501 1568 y Fe(\003)501 1613 y Ff(1)561 1600 y Fn(freely)-6 b(,)25 b(the)f(attac)n(k)n(er)g(can)g(exert)g(complete)-152 1687 y(con)n(trol)30 b(o)n(v)n(er)g(the)f(result.)46 b(F)-6 b(or)30 b(instance,)h(if)g(the)e(attac)n(k)n(er)g(w)n(an)n(ts) -152 1774 y(to)i(arti\014cially)i(add)d(a)h(bias)h Fi(\016)i Fn(to)d(the)f(a)n(v)n(erage,)k(then)c(he)g(can)i(set)-152 1862 y Fi(x)-108 1830 y Fe(\003)-108 1875 y Ff(1)-42 1862 y Fn(=)d Fi(x)91 1870 y Ff(1)146 1862 y Fn(+)20 b Fi(\016)s(n)p Fn(,)32 b(and)f(the)f(a)n(v)n(erage)i(will)g(b)r(e)e (successfully)i(altered)-152 1949 y(from)g Fi(y)i Fn(to)e Fi(y)249 1917 y Fe(\003)315 1949 y Fn(=)f Fi(y)24 b Fn(+)d Fi(\016)s Fn(.)52 b(Consequen)n(tly)-6 b(,)32 b(the)f(a)n(v)n(erage)i (is)f(not)f(a)-152 2036 y(meaningful)d(aggregate)i(in)e(the)g(presence) g(of)g(ev)n(en)g(a)g(single)h(com-)-152 2123 y(promised)c(no)r(de.)-152 2310 y Fg(The)30 b(sum)g(is)h(insecur)m(e.)38 b Fn(Similarly)-6 b(,)33 b(the)d(sum)h Fi(f)8 b Fn(\()p Fi(x)1430 2318 y Ff(1)1464 2310 y Fi(;)13 b(:)g(:)g(:)g(;)h(x)1679 2318 y Fh(n)1721 2310 y Fn(\))30 b(=)-152 2397 y Fi(x)-108 2405 y Ff(1)-51 2397 y Fn(+)22 b Fq(\001)13 b(\001)g(\001)22 b Fn(+)g Fi(x)268 2405 y Fh(n)344 2397 y Fn(is)34 b(not)f(meaningful)h (in)f(the)g(presence)h(of)g(one)f(or)-152 2484 y(more)28 b(compromised)e(no)r(des.)42 b(The)28 b(attac)n(k)n(er)f(can)h(freely)h (increase)-152 2571 y(or)d(decrease)h(this)f(v)l(alue)f(without)h (limit.)-152 2758 y Fg(The)44 b(count)f(can)g(be)h(secur)m(ed.)38 b Fn(A)i(related)h(primitiv)n(e)f(is)h(the)-152 2845 y(coun)n(t,)d(whic)n(h)d(is)h(lik)n(e)f(the)g(sum,)h(except)f(that)g (eac)n(h)g(no)r(de)g(con-)-152 2933 y(tributes)23 b(0)g(or)g(1)f(to)h (the)f(total.)35 b(If)22 b(an)h(incautious)g(implemen)n(tation)-152 3020 y(forgets)31 b(to)e(c)n(hec)n(k)g(that)g(eac)n(h)g(no)r(de's)h(v)l (alue)f(is)g(in)h(the)e(set)i Fq(f)p Fn(0)p Fi(;)14 b Fn(1)p Fq(g)p Fn(,)-152 3107 y(then)31 b(it)h(will)h(b)r(e)e (susceptible)h(to)g(the)f(same)g(attac)n(k)g(as)h(the)g(sum.)-152 3194 y(Ho)n(w)n(ev)n(er,)37 b(if)e(prop)r(erly)f(implemen)n(ted,)h(w)n (e)f(kno)n(w)g(of)h(no)g(serious)-152 3281 y(attac)n(ks)26 b(on)f(the)g(coun)n(t.)34 b(An)25 b(attac)n(k)n(er)g(with)h(con)n(trol) g(o)n(v)n(er)f Fi(k)j Fn(com-)-152 3368 y(promised)20 b(no)r(des)g(can)g(only)g(c)n(hange)g(the)g(coun)n(t)g(b)n(y)f(at)h (most)g Fi(k)r Fn(,)h(and)-152 3456 y(hence)31 b(if)g(the)f(n)n(um)n(b) r(er)e(of)k(compromised)d(no)r(des)i(is)g(limited,)h(this)-152 3543 y(ma)n(y)25 b(b)r(e)g(acceptable.)-152 3730 y Fg(The)f(minimum)h (is)f(insecur)m(e)o(.)38 b Fn(Consider)28 b(computing)e(the)h(mini-) -152 3817 y(m)n(um)15 b(of)j(the)f(sensor)g(readings,)k Fi(f)8 b Fn(\()p Fi(x)897 3825 y Ff(1)931 3817 y Fi(;)13 b(:)g(:)g(:)g(;)h(x)1146 3825 y Fh(n)1188 3817 y Fn(\))21 b(=)g(min)o(\()p Fi(x)1522 3825 y Ff(1)1556 3817 y Fi(;)13 b(:)g(:)g(:)g(;)g(x)1770 3825 y Fh(n)1813 3817 y Fn(\),)-152 3904 y(and)35 b(supp)r(ose)g(that)f(sensor)i(1)f(is)g(compromised.)61 b(The)35 b(attac)n(k)n(er)-152 3991 y(can)f(only)g(increase)h(the)f (minim)n(um)c(if)35 b Fi(x)1088 3999 y Ff(1)1156 3991 y Fn(is)f(the)g(unique)f(small-)-152 4078 y(est)24 b(sensor)h(reading,) g(and)f(ev)n(en)f(then,)h(the)f(minim)n(um)e(is)j(raised)h(to)-152 4165 y(min)o(\()p Fi(x)50 4134 y Fe(\003)50 4179 y Ff(1)86 4165 y Fi(;)13 b(x)164 4173 y Ff(2)198 4165 y Fi(;)g(:)g(:)g(:)g(;)h(x) 413 4173 y Fh(n)455 4165 y Fn(\),)40 b(whic)n(h)d(cannot)g(exceed)g (min)o(\()p Fi(x)1499 4173 y Ff(2)1533 4165 y Fi(;)13 b(:)g(:)g(:)g(;)h(x)1748 4173 y Fh(n)1790 4165 y Fn(\).)-152 4253 y(Th)n(us,)32 b(the)e(attac)n(k)n(er)h(has)g(little)g(capacit)n(y) g(to)g(increase)h(the)e(com-)-152 4340 y(puted)j(aggregate.)60 b(Ho)n(w)n(ev)n(er,)35 b(the)e(attac)n(k)n(er)h(can)f(freely)h(reduce) -152 4427 y(the)19 b(computed)f(minim)n(um)e(v)l(alue,)k(simply)f(b)n (y)f(c)n(ho)r(osing)i Fi(x)1562 4395 y Fe(\003)1562 4440 y Ff(1)1617 4427 y Fn(to)f(b)r(e)g(a)-152 4514 y(v)n(ery)g(small)g (\(or)h(ev)n(en)e(negativ)n(e\))i(v)l(alue.)32 b(So)19 b(long)h(as)g(the)f(attac)n(k)n(er's)-152 4601 y(desired)j(outcome)e (is)i(smaller)f(than)g(the)g(correct)g(outcome,)h(the)f(at-)-152 4689 y(tac)n(k)n(er)f(has)g(complete)g(con)n(trol.)33 b(Therefore,)23 b(w)n(e)e(consider)f(that)g(the)-152 4776 y(minim)n(um)c(is)j(not)f(resilien)n(t)i(against)g(false)g(sensor) f(readings.)33 b(In)18 b(the)-152 4863 y(presence)24 b(of)h(a)f(single)h(compromised)d(no)r(de,)j(the)e(minim)n(um)e(is)j (not)-152 4950 y(a)i(meaningful)g(aggregate)i(to)e(compute.)-152 5137 y Fg(The)17 b(maximum)f(is)h(insecur)m(e.)39 b Fn(By)20 b(symmetry)-6 b(,)19 b(the)h(maxim)n(um)d(is)-152 5224 y(also)25 b(not)e(meaningful)h(in)f(the)g(presence)g(of)h(a)g (compromised)e(no)r(de.)2040 -69 y Fo(4.)99 b(VULNERABILITIES)27 b(OF)e(EXISTING)2214 48 y(SYSTEMS)2115 156 y Fn(Man)n(y)32 b(of)h(to)r(da)n(y's)g(sensor)g(net)n(w)n(ork)f(systems)g(are)h (susceptible)2040 243 y(to)d(the)g(attac)n(ks)h(describ)r(ed)f(ab)r(o)n (v)n(e.)48 b(A)30 b(few)h(examples)e(should)h(to)2040 330 y(serv)n(e)c(to)g(illustrate)g(the)g(p)r(oin)n(t.)2040 517 y Fg(T)-5 b(inyDB.)41 b Fn(Tin)n(yDB)30 b(is)h(a)g(database-cen)n (tric)g(in)n(terface)h(to)f(sensor)2040 604 y(net)n(w)n(orks,)26 b(where)g(data)g(aggregation)j(is)d(expressed)g(with)g(a)g(SQL-)2040 691 y(lik)n(e)f(query)g(language)h([8,)g(5].)35 b(The)26 b(database)g(consists)g(of)g(a)g(table,)2040 778 y(where)k(eac)n(h)g (sensor)h(pro)n(vides)f(one)g(ro)n(w)g(in)g(the)f(table,)j(and)d(eac)n (h)2040 865 y(ro)n(w)21 b(pro)n(vides)f(v)l(alues)g(for)h(sev)n(eral)g (attributes)g(\(e.g.,)h(temp)r(erature,)2040 953 y(h)n(umidit)n(y)-6 b(,)34 b(ligh)n(t,)i(acceleration\).)61 b(Queries)34 b(compute)f(an)h(aggre-)2040 1040 y(gate)27 b(of)f(the)g(listed)g (attribute,)h(or)f(of)h(a)f(simple)f(b)r(o)r(olean)i(or)g(arith-)2040 1127 y(metic)21 b(expression)g(of)h(a)g(single)g(attribute.)33 b(Tin)n(yDB)21 b(supp)r(orts)g(\014v)n(e)2040 1214 y(con)n(v)n(en)n (tional)k(aggregates:)36 b(the)24 b(minim)n(um,)e(maxim)n(um,)f(a)n(v)n (erage,)2040 1301 y(coun)n(t,)36 b(and)e(sum.)59 b(Also,)37 b(Tin)n(yDB)d(supp)r(orts)h(temp)r(oral)f(aggre-)2040 1388 y(gates:)j(a)27 b(sliding)g(windo)n(w)g(of)g(previous)g(sensor)g (readings)g(is)g(k)n(ept,)2040 1476 y(and)i(then)f(the)h(minim)n(um,)e (maxim)n(um,)g(a)n(v)n(erage,)k(coun)n(t,)f(or)g(sum)2040 1563 y(can)c(b)r(e)f(applied)h(to)g(this)g(recen)n(t)f(history)-6 b(.)2115 1650 y(Based)37 b(on)g(the)g(ab)r(o)n(v)n(e)f(discussion,)41 b(w)n(e)d(see)f(that)f(Tin)n(yDB)h(is)2040 1737 y(insecure)h(in)f(the)f (presence)i(of)g(compromised)e(no)r(des)h(when)g(the)2040 1824 y(minim)n(um,)29 b(maxim)n(um,)f(a)n(v)n(erage,)33 b(or)e(sum)e(aggregates)k(\(or)e(their)2040 1911 y(corresp)r(onding)21 b(temp)r(oral)g(aggregation)i(v)l(arian)n(ts\))d(are)h(used.)32 b(The)2040 1999 y(coun)n(t)22 b(\(or)h(sliding)g(windo)n(w)h(coun)n (t\))e(is)h(the)f(only)g(primitiv)n(e)g(that)g(is)2040 2086 y(resilien)n(t)27 b(to)f(malicious)g(data.)2040 2273 y Fg(Other)38 b(systems.)h Fn(Tin)n(yDB)d(is)i(not)e(alone.)68 b(F)-6 b(or)37 b(example,)i(the)2040 2360 y(Cougar)d(sensor)f(database) g(system)f(supp)r(orts)g(SQL-lik)n(e)f(queries)2040 2447 y(with)f(aggregation)j(op)r(erators,)g(m)n(uc)n(h)30 b(lik)n(e)i(Tin)n(yDB)f([15].)55 b(Lik)n(e-)2040 2534 y(wise,)35 b(the)c(SensorW)-6 b(are)32 b(pro)t(ject)h(prop)r(oses)f (e\016cien)n(t)g(algorithms)2040 2621 y(for)20 b(computing)d(the)i(a)n (v)n(erage,)i(maxim)n(um,)c(and)h(minim)n(um,)f(as)i(w)n(ell)2040 2708 y(as)26 b(for)g(building)f(appro)n(ximate)f(con)n(tour)h(maps)g ([1].)35 b(These)26 b(exam-)2040 2796 y(ples)36 b(are)f(represen)n (tativ)n(e)g(of)h(the)f(w)n(ork)g(in)g(the)g(\014eld)g([16].)64 b(The)2040 2883 y(p)r(opularit)n(y)25 b(of)g(aggregates)i(lik)n(e)e (the)g(a)n(v)n(erage)g(and)f(the)h(maxim)n(um)2040 2970 y(is)h(no)g(acciden)n(t:)35 b(they)24 b(are)j(b)r(oth)e(useful)h(and)f (easy)h(to)g(compute.)2115 3057 y(W)-6 b(e)22 b(emphasize)h(that)g(our) g(attac)n(ks)g(are)g(not)g(in)n(tended)f(as)h(a)h(crit-)2040 3144 y(icism)29 b(of)h(these)e(systems,)i(as)f(these)g(systems)f(w)n (ere)i(not)e(designed)2040 3231 y(for)k(securit)n(y)f(against)i (compromised)d(no)r(des.)51 b(Nonetheless,)33 b(this)2040 3319 y(motiv)l(ates)27 b(the)g(searc)n(h)g(for)h(aggregation)i (primitiv)n(es)c(with)i(b)r(etter)2040 3406 y(securit)n(y)e(prop)r (erties.)2040 3626 y Fo(5.)99 b(A)25 b(THEOR)m(Y)f(OF)h(RESILIENT)2214 3742 y(A)-5 b(GGREGA)c(TION)2115 3850 y Fn(After)30 b(these)g(attac)n (ks)g(on)h(certain)f(aggregation)j(op)r(erations,)f(it)2040 3937 y(is)j(natural)f(to)g(ask)g(for)h(a)f(w)n(a)n(y)g(to)g(reason)h (ab)r(out)f(secure)h(aggre-)2040 4024 y(gation.)43 b(W)-6 b(e)27 b(dev)n(elop)h(suc)n(h)f(a)i(framew)n(ork)f(in)g(this)g (section.)42 b(Tw)n(o)2040 4111 y(k)n(ey)20 b(landmarks)h(are)h(w)n (orth)f(w)n(atc)n(hing)h(for)g(in)f(the)g(exp)r(osition)h(that)2040 4198 y(follo)n(ws:)2130 4356 y(1.)38 b(W)-6 b(e)29 b(prop)r(ose)h(that) e(aggregation)k(primitiv)n(es)d(b)r(e)g(view)n(ed)g(as)2227 4443 y(nothing)f(more)g(than)g(statistical)i(estimators.)44 b(This)29 b(allo)n(ws)2227 4530 y(us)g(to)g(exploit)h(the)f(p)r(o)n(w)n (er)g(of)h(statistics)h(and)e(build)g(on)g(the)2227 4617 y(existing)d(literature)h(on)e(statistical)j(estimation)e(theory)-6 b(.)2130 4785 y(2.)38 b(W)-6 b(e)28 b(argue)i(that)f(the)f(resilien)n (t)i(aggregration)h(problem)d(has)2227 4872 y(close)21 b(connections)f(to)f(the)g(\014eld)g(of)i(robust)e(statistics,)k(whic)n (h)2227 4959 y(w)n(as)d(dev)n(elop)r(ed)f(to)h(deal)g(with)g(noisy)f (and)g(error-prone)h(data.)2227 5046 y(This)35 b(corresp)r(ondence)f (lo)r(oks)h(fruitful,)i(b)r(ecause)d(it)h(allo)n(ws)2227 5133 y(us)25 b(to)h(b)r(orro)n(w)g(clev)n(er)g(ideas)g(that)f(ha)n(v)n (e)g(b)r(een)g(dev)n(elop)r(ed)g(in)2227 5220 y(that)g(\014eld)h(and)f (adapt)h(them)e(to)i(solv)n(e)g(our)g(problems.)2040 5378 y(Before)j(w)n(e)e(w)n(ork)h(out)f(the)f(details,)j(it)e(will)i(b) r(e)e(helpful)g(to)g(digress)p eop %%Page: 5 5 5 4 bop -152 -69 a Fn(for)40 b(a)f(momen)n(t)d(to)j(giv)n(e)f(some)h (essen)n(tial)h(mathematical)e(bac)n(k-)-152 19 y(ground)26 b(on)f(the)h(classical)i(estimation)e(theory)-6 b(.)-152 205 y Fg(Estimation)23 b(theory.)40 b Fn(Succin)n(tly)24 b(put,)h(the)h(estimation)g(problem)-152 292 y(is)36 b(this:)55 b(Giv)n(en)35 b(a)h(sequence)f(of)h(observ)l(ations)h Fi(x)1359 300 y Ff(1)1393 292 y Fi(;)13 b(:)g(:)g(:)g(;)g(x)1607 300 y Fh(n)1685 292 y Fn(from)-152 380 y(a)31 b(kno)n(wn)e (parameterized)h(distribution)g Fi(p)p Fn(\()p Fi(X)k Fq(j)29 b Fi(\022)r Fn(\),)i(where)f Fi(\022)i Fn(is)e(a)-152 467 y(hidden)23 b(parameter,)i(the)e(goal)j(is)e(to)g(estimate)g Fi(\022)i Fn(as)f(accurately)f(as)-152 554 y(p)r(ossible.)-77 641 y(In)i(more)g(detail,)h(let)g Fi(\022)h Fn(denote)f(a)f(parameter,) h(whose)g(distribu-)-152 728 y(tion)g(is)g(not)f(sp)r(eci\014ed.)38 b(A)26 b(parameterized)g(distribution)g Fi(p)p Fn(\()p Fi(X)j Fq(j)23 b Fi(\022)r Fn(\))-152 816 y(is)j(a)f(family)g(of)h (distributions,)g(one)f(for)h(eac)n(h)f(p)r(ossible)i(v)l(alue)e(of)g Fi(\022)r Fn(.)-152 903 y(F)-6 b(or)27 b(instance,)h Fq(N)11 b Fn(\()p Fi(\022)r(;)i Fn(1\),)28 b(the)e(Gaussian)i (distribution)f(with)g(mean)-152 990 y Fi(\022)h Fn(and)d(v)l(ariance)h (1,)h(is)f(a)g(distribution)g(with)f(parameter)h Fi(\022)r Fn(.)-77 1077 y(Next,)g(let)i Fi(X)309 1085 y Ff(1)344 1077 y Fi(;)13 b(:)g(:)g(:)g(;)g(X)577 1085 y Fh(n)647 1077 y Fn(denote)26 b Fi(n)h Fn(random)f(v)l(ariables)i(that)e(are)-152 1164 y(distributed)34 b(according)g(to)g Fi(p)p Fn(\()p Fi(X)41 b Fq(j)35 b Fi(\022)r Fn(\))f(and)f(that)h(are)g(condition-) -152 1251 y(ally)j(indep)r(enden)n(t)d(giv)n(en)i Fi(\022)r Fn(.)65 b(In)35 b(other)h(w)n(ords,)j(imagine)d(a)h(ref-)-152 1339 y(eree)23 b(secretly)f(c)n(ho)r(osing)h(a)g(v)l(alue)e Fi(\022)r Fn(,)i(then)f(making)f Fi(n)h Fn(indep)r(enden)n(t)-152 1426 y(dra)n(ws)j(from)e(the)h(distribution)f(with)h(this)g(\014xed)f (v)l(alue)g(of)i Fi(\022)h Fn(as)e(the)-152 1513 y(common)18 b(parameter)i(and)f(letting)h Fi(X)954 1521 y Ff(1)989 1513 y Fi(;)13 b(:)g(:)g(:)g(;)h(X)1223 1521 y Fh(n)1285 1513 y Fn(denote)19 b(the)g(result)-152 1600 y(from)26 b(the)f Fi(n)h Fn(dra)n(ws.)-77 1687 y(An)16 b(estimator)i(is)f(an)h (algorithm)f Fi(f)30 b Fn(:)21 b Fd(R)1042 1656 y Fh(n)1109 1687 y Fq(!)g Fd(R)p Fn(,)h(where)c Fi(f)8 b Fn(\()p Fi(x)1634 1695 y Ff(1)1668 1687 y Fi(;)14 b(:)f(:)g(:)g(;)g(x)1883 1695 y Fh(n)1925 1687 y Fn(\))-152 1774 y(is)24 b(in)n(tended)e(as)i (an)f(estimate)g(of)h(some)f(real-v)l(alued)g(function)g(of)h Fi(\022)r Fn(.)-152 1862 y(F)-6 b(or)26 b(simplicit)n(y)f(of)h(exp)r (osition,)g(in)f(what)h(follo)n(ws)i(w)n(e)d(will)i(assume)-152 1949 y(that)j Fi(\022)h Fn(is)f(real-v)l(alued)g(and)f(that)h(w)n(e)g (wish)g(to)g(estimate)f Fi(\022)j Fn(itself.)-152 2036 y(Next,)i(w)n(e)f(de\014ne)f(the)h(random)f(v)l(ariable)1150 2017 y(^)1139 2036 y(\002)1232 1993 y Fc(def)1239 2036 y Fn(=)41 b Fi(f)8 b Fn(\()p Fi(X)1478 2044 y Ff(1)1513 2036 y Fi(;)13 b(:)g(:)g(:)h(;)f(X)1747 2044 y Fh(n)1790 2036 y Fn(\).)-152 2123 y(Then,)26 b(for)h(our)e(purp)r(oses)617 2091 y Ff(1)652 2123 y Fn(,)h(the)g(relev)l(an)n(t)f(\014gure)g(of)i (merit)e(is)152 2262 y(ro)r(ot-mean-square)g(\(r.m.s.\))34 b(error)26 b(\(at)g Fi(\022)r Fn(\):)613 2368 y(rms)o(\()p Fi(f)8 b Fn(\))864 2325 y Fc(def)871 2368 y Fn(=)29 b Fd(E)5 b Fn([)q(\()1066 2349 y(^)1055 2368 y(\002)22 b Fq(\000)17 b Fi(\022)r Fn(\))1282 2336 y Ff(2)1338 2368 y Fq(j)22 b Fi(\022)r Fn(])1440 2336 y Ff(1)p Fh(=)p Ff(2)-152 2514 y Fn(Note)28 b(that)f(rms)o(\()p Fi(f)8 b Fn(\))28 b(is)f(a)h(function)g(of)g Fi(\022)r Fn(,)g(the)f (underlying)g(param-)-152 2601 y(eter;)42 b(w)n(e)37 b(compare)f(functions)g(p)r(oin)n(t)n(wise.)67 b(Also,)40 b(an)c(un)n(biased)-152 2688 y(estimator)26 b(is)g(one)g(for)h(whic)n (h)f Fd(E)5 b Fn([)822 2669 y(^)811 2688 y(\002)27 b Fq(j)21 b Fi(\022)r Fn(])h(=)f Fi(\022)28 b Fn(for)e(all)h Fi(\022)r Fn(.)-77 2775 y(The)32 b(r.m.s.)g(error)g(is)g(a)g(go)r(o)r (d)h(measure)e(of)h(the)f(inaccuracy)h(or)-152 2863 y(\\spread")25 b(of)f(our)g(estimator,)g(and)f(a)h(reasonable)h(in)n(tuition)e(w)n (ould)-152 2950 y(b)r(e)33 b(to)h(think)e(of)i(the)e(r.m.s.)i(error)f (as)h(represen)n(ting)f(a)h(\\t)n(ypical")-152 3037 y(v)l(alue)27 b(of)g(the)f(error)i(term)d Fq(j)675 3018 y Fn(^)664 3037 y(\002)18 b Fq(\000)g Fi(\022)r Fq(j)p Fn(.)37 b(F)-6 b(or)27 b(an)g(un)n(biased)f(estimator,)-152 3124 y(the)d(r.m.s.)g (error)g(is)h(exactly)f(the)f(standard)h(deviation)g(of)h(the)e(ran-) -152 3211 y(dom)h(v)l(ariable)314 3192 y(^)303 3211 y(\002,)h(so)g(our) g(usual)g(in)n(tuitions)f(ab)r(out)h(Gaussian)h(dis-)-152 3299 y(tributions)i(will)g(often)g(b)r(e)f(helpful)h(in)f(thinking)f (ab)r(out)i(the)f(r.m.s.)-152 3386 y(error)i(metric.)37 b(W)-6 b(e)26 b(usually)h(rely)f(on)h(the)f(r.m.s.)h(error)h(to)f(c)n (harac-)-152 3473 y(terize)19 b(the)e(qualit)n(y)g(of)i(our)f (estimator,)i(and)d(w)n(e)h(often)h(appro)n(ximate)-152 3560 y(the)26 b(r.m.s.)g(error)g(b)n(y)e(its)j(asymptotic)e(b)r(eha)n (vior)g(as)i Fi(n)21 b Fq(!)g(1)p Fn(.)p -152 3631 797 4 v -148 3685 a Ff(1)-113 3716 y Fn(The)g(relation)h(to)e(standard)h (estimation)g(theory)f(is)i(as)f(follo)n(ws.)35 b(In)-152 3791 y(classical)22 b(estimation)e(theory)-6 b(,)20 b(there)g(are)g (three)f(standard)h(metrics:)-60 3952 y(mean)k(square)i(error)g(at)g Fi(\022)r Fn(:)154 b(MSE)q(\()p Fi(f)8 b Fn(\))1173 3910 y Fc(def)1180 3952 y Fn(=)29 b Fd(E)6 b Fn([\()1375 3934 y(^)1364 3952 y(\002)23 b Fq(\000)17 b Fi(\022)r Fn(\))1592 3921 y Ff(2)1647 3952 y Fq(j)22 b Fi(\022)r Fn(])273 4055 y(v)l(ariance)k(at)g Fi(\022)r Fn(:)154 b(V\()p Fi(f)8 b Fn(\))1065 4012 y Fc(def)1073 4055 y Fn(=)28 b(V)-6 b(ar[)1313 4036 y(^)1302 4055 y(\002)21 b Fq(j)h Fi(\022)r Fn(])416 4157 y(bias)k(at)g Fi(\022)r Fn(:)154 b(Bias)r(\()p Fi(f)8 b Fn(\))1152 4114 y Fc(def)1160 4157 y Fn(=)28 b Fd(E)6 b Fn([)1324 4138 y(^)1313 4157 y(\002)27 b Fq(j)22 b Fi(\022)r Fn(])17 b Fq(\000)g Fi(\022)-152 4298 y Fn(A)50 b(minimal-v)l(ariance)g(un)n(biased)g(estimator)h(is)g (an)g(estimator)-152 4373 y(where)35 b(MSE\()p Fi(f)8 b Fn(\))34 b(is)h(minimal)e(among)g(all)i(un)n(biased)f(estimators.) -152 4448 y(Note)29 b(that)f(MSE)q(\()p Fi(f)8 b Fn(\),)30 b(and)e(the)g(other)h(metrics,)h(are)f(functions)g(of)-152 4522 y Fi(\022)r Fn(.)48 b(W)-6 b(e)30 b(compare)f(functions)i(p)r(oin) n(t)n(wise)g(when)f(testing)g(for)h(mini-)-152 4597 y(malit)n(y)-6 b(,)31 b(i.e.,)h Fi(m)d Fq(\024)f Fi(m)511 4565 y Fe(0)563 4597 y Fn(i\013)i Fi(m)p Fn(\()p Fi(\022)r Fn(\))e Fq(\024)h Fi(m)1010 4565 y Fe(0)1032 4597 y Fn(\()p Fi(\022)r Fn(\))h(for)g(all)i Fi(\022)r Fn(.)47 b(The)31 b(name)-152 4672 y(\\minimal-v)l(ariance)37 b(un)n(biased)h(estimator")g(is)h(justi\014ed)e(b)n(y)g(the)-152 4758 y(follo)n(wing)31 b(basic)e(iden)n(tit)n(y:)39 b(MSE)q(\()p Fi(f)8 b Fn(\))25 b(=)h(V\()p Fi(f)8 b Fn(\))19 b(+)f(Bias)r(\()p Fi(f)8 b Fn(\))1581 4727 y Ff(2)1615 4758 y Fn(.)43 b(Con-)-152 4833 y(sequen)n(tly)-6 b(,)28 b(the)g(un)n(biased)g(estimator)h(with)f (minimal)g(v)l(ariance)g(is)-152 4908 y(also)23 b(the)d(un)n(biased)h (estimator)g(with)h(minimal)e(mean)g(square)h(error)-152 4983 y(\(or)26 b(r.m.s.)g(error,)h(for)f(that)g(matter\).)-152 5079 y(Notice)41 b(that)g(rms)o(\()p Fi(f)8 b Fn(\))47 b(=)f(MSE\()p Fi(f)8 b Fn(\))938 5047 y Ff(1)p Fh(=)p Ff(2)1035 5079 y Fn(,)45 b(so)c(the)f(r.m.s.)h(error)g(is)-152 5153 y(closely)19 b(connected)f(to)g(the)f(mean)g(square)g(error.)33 b(In)17 b(this)h(pap)r(er,)h(w)n(e)-152 5228 y(in)n(tro)r(duced)24 b(the)f(r.m.s.)h(metric)g(b)r(ecause)g(it)g(is)h(in)n(tuitiv)n(e,)f (its)g(units)-152 5303 y(are)h(more)e(con)n(v)n(enien)n(t,)h(and)g(it)g (summarizes)f(in)h(one)h(quan)n(tit)n(y)d(the)-152 5378 y(\014gure)k(of)g(merit)f(w)n(e)h(care)h(most)e(ab)r(out.)2040 -69 y Fg(Application)f(to)g(a)o(g)o(gr)m(e)l(gation.)39 b Fn(As)27 b(others)g(ha)n(v)n(e)f(noted)h(b)r(efore)2040 19 y([10,)40 b(9],)f(statistical)f(estimation)e(theory)f(is)i(a)f(p)r (o)n(w)n(erful)h(w)n(a)n(y)e(to)2040 106 y(think)e(ab)r(out)i(data)f (aggregation.)62 b(One)34 b(ma)n(y)f(think)g(of)i(the)f(pa-)2040 193 y(rameter)23 b Fi(\022)i Fn(as)e(re\015ecting)g(some)g(in)n (teresting)h(underlying)e(quan)n(tit)n(y)2040 280 y(in)k(the)f(ph)n (ysical)g(en)n(vironmen)n(t.)33 b(Ho)n(w)n(ev)n(er,)26 b Fi(\022)h Fn(cannot)f(b)r(e)g(directly)2040 367 y(observ)n(ed.)53 b(Instead,)34 b(our)e(only)g(w)n(a)n(y)g(to)g(gain)h(information)g(on)f Fi(\022)2040 454 y Fn(is)26 b(b)n(y)e(taking)h Fi(n)g Fn(sensor)g(measuremen)n(ts,)f(whic)n(h)h(are)h(mo)r(delled)f(b)n(y) 2040 542 y(the)d(random)g(v)l(ariables)h Fi(X)2826 550 y Ff(1)2861 542 y Fi(;)13 b(:)g(:)g(:)h(;)f(X)3095 550 y Fh(n)3138 542 y Fn(.)33 b(The)23 b(aggregation)h(function)2040 629 y Fi(f)34 b Fn(can)26 b(then)f(b)r(e)g(view)n(ed)h(as)g(an)g (estimator)g(of)h Fi(\022)r Fn(.)2115 716 y(F)-6 b(or)29 b(instance,)i Fi(\022)g Fn(migh)n(t)d(represen)n(t)h(the)g(a)n(v)n (erage)g(temp)r(erature)2040 803 y(across)37 b(the)d(New)h(Y)-6 b(ork)34 b(Cit)n(y)h(metrop)r(olitan)g(area,)k(and)34 b Fi(X)3864 811 y Fh(i)3926 803 y Fn(the)2040 890 y(temp)r(erature)g (reading)h(at)g(the)f Fi(i)p Fn(th)h(sensor.)62 b(It)35 b(is)g(natural)g(that)2040 977 y Fi(\022)h Fn(is)e(a)g(parameter)f (\(since)h(the)f(a)n(v)n(erage)h(temp)r(erature)f(can)g(v)l(ary)2040 1065 y(from)27 b(da)n(y)f(to)h(da)n(y\))g(and)f(that)h Fi(X)3022 1073 y Fh(i)3075 1065 y Fn(is)h(random)e(but)g(dep)r(enden)n (t)g(on)2040 1152 y Fi(\022)j Fn(\(since)e(sensor)g(readings)g(are)g (noisy)-6 b(,)27 b(but)f(correlated)h(to)g Fi(\022)r Fn(\).)37 b(W)-6 b(e)2040 1259 y(migh)n(t)29 b(tak)n(e)g Fi(f)8 b Fn(\()p Fi(x)2553 1267 y Ff(1)2588 1259 y Fi(;)13 b(:)g(:)g(:)g(;)g(x)2802 1267 y Fh(n)2844 1259 y Fn(\))2902 1216 y Fc(def)2909 1259 y Fn(=)36 b(\()p Fi(x)3079 1267 y Ff(1)3132 1259 y Fn(+)20 b Fq(\001)13 b(\001)g(\001)20 b Fn(+)f Fi(x)3444 1267 y Fh(n)3486 1259 y Fn(\))p Fi(=n)p Fn(,)32 b(so)e(that)g(our)2040 1346 y(estimator)e(is)h(the)e(a)n(v)n (erage)i(of)f(all)h(sensor)g(readings.)42 b(Then,)29 b(if)f(w)n(e)2040 1433 y(ha)n(v)n(e)f(a)g(mo)r(del)g(of)h(the)f (distribution)g Fi(p)p Fn(\()p Fi(X)3289 1441 y Fh(i)3340 1433 y Fq(j)d Fi(\022)r Fn(\),)k(w)n(e)g(can)f(measure)2040 1520 y(the)38 b(qualit)n(y)f(of)i(the)e(a)n(v)n(erage)i(as)f(an)g (aggregation)j(function)d(b)n(y)2040 1607 y(calculating)30 b(the)e(r.m.s.)h(error)g(of)h Fi(f)37 b Fn(as)29 b(an)f(estimator)h(of) h Fi(\022)r Fn(.)43 b(This)2040 1695 y(seems)36 b(lik)n(e)g(a)h (reasonable)g(view;)42 b(when)36 b(the)g(user)g(asks)h(for)g(the)2040 1782 y(a)n(v)n(erage)24 b(of)f(sensor)h(readings,)g(usually)f(it)g(is)g (not)g(that)f(the)h(a)n(v)n(erage)2040 1869 y(is)29 b(of)g(an)n(y)f (inheren)n(t)g(in)n(terest)h(of)g(its)g(o)n(wn)g(righ)n(t,)h(but)d (rather)i(that)2040 1956 y(this)g(aggregate)j(is)e(an)f(in)n(tuitiv)n (e)f(w)n(a)n(y)i(to)f(estimate)g(some)g(hidden)2040 2043 y(parameter)c(of)i(in)n(terest.)2040 2230 y Fg(Resilient)14 b(estimator)o(s)g(and)g(r)m(esilient)g(a)o(g)o(gr)m(e)l(gation.)35 b Fn(A)17 b Fi(k)r Fn(-no)r(de)2040 2317 y(attac)n(k)28 b Fi(A)g Fn(is)h(an)f(algorithm)g(that)g(is)h(allo)n(w)n(ed)g(to)f(c)n (hange)h(up)e(to)h Fi(k)2040 2404 y Fn(of)e(the)e(v)l(alues)h Fi(X)2549 2412 y Ff(1)2584 2404 y Fi(;)13 b(:)g(:)g(:)g(;)h(X)2818 2412 y Fh(n)2885 2404 y Fn(b)r(efore)26 b(the)e(estimator)i(is)f (applied.)34 b(In)2040 2492 y(particular,)24 b(the)d(attac)n(k)h Fi(A)f Fn(is)h(sp)r(eci\014ed)g(b)n(y)f(a)h(function)g Fi(\034)3724 2500 y Fh(A)3795 2492 y Fn(:)g Fd(R)3889 2460 y Fh(n)3956 2492 y Fq(!)2040 2579 y Fd(R)2091 2547 y Fh(n)2170 2579 y Fn(with)34 b(the)f(prop)r(ert)n(y)g(that)g(the)g(v)n (ectors)h Fi(x)f Fn(and)g Fi(\034)3666 2587 y Fh(A)3716 2579 y Fn(\()p Fi(x)p Fn(\))g(nev)n(er)2040 2666 y(di\013er)26 b(at)g(more)f(than)g Fi(k)j Fn(p)r(ositions.)2115 2753 y(W)-6 b(e)25 b(can)h(de\014ne)f(the)g(r.m.s.)h(error)g(asso)r(ciated)i (with)e Fi(A)f Fn(b)n(y)2420 2908 y(rms)2544 2876 y Fe(\003)2580 2908 y Fn(\()p Fi(f)t(;)13 b(A)p Fn(\))2794 2865 y Fc(def)2801 2908 y Fn(=)29 b Fd(E)6 b Fn([\()2996 2889 y(^)2985 2908 y(\002)3045 2876 y Fe(\003)3104 2908 y Fq(\000)16 b Fi(\022)r Fn(\))3248 2876 y Ff(2)3304 2908 y Fq(j)22 b Fi(\022)r Fn(])3406 2876 y Ff(1)p Fh(=)p Ff(2)2573 3014 y Fn(where)2806 2995 y(^)2795 3014 y(\002)2855 2982 y Fe(\003)2912 2971 y Fc(def)2920 3014 y Fn(=)28 b Fi(f)8 b Fn(\()p Fi(\034)3117 3022 y Fh(A)3168 3014 y Fn(\()p Fi(X)3261 3022 y Ff(1)3295 3014 y Fi(;)14 b(:)f(:)g(:)g(;)g(X)3529 3022 y Fh(n)3572 3014 y Fn(\)\))p Fi(:)2040 3171 y Fn(T)-6 b(o)26 b(explain,)2451 3152 y(^)2440 3171 y(\002)2500 3139 y Fe(\003)2561 3171 y Fn(is)g(a)g(random)e(v)l(ariable)i(that)f(represen)n(ts)g(the)g(ag-) 2040 3258 y(gregate)g(calculated)g(at)g(the)e(base)i(station)f(in)g (the)g(presence)g(of)h(the)2040 3345 y Fi(k)r Fn(-no)r(de)30 b(attac)n(k)h Fi(A)p Fn(,)g(and)g(rms)2927 3313 y Fe(\003)2963 3345 y Fn(\()p Fi(f)t(;)13 b(A)p Fn(\))30 b(is)h(a)g(measure)f(of)h (the)g(inac-)2040 3432 y(curacy)24 b(of)g(the)f(aggregate)j(after)e Fi(A)p Fn('s)g(in)n(trusion.)34 b(If)24 b(rms)3706 3400 y Fe(\003)3742 3432 y Fn(\()p Fi(f)t(;)13 b(A)p Fn(\))21 b Fq(\035)2040 3519 y Fn(rms)o(\()p Fi(f)8 b Fn(\),)20 b(then)e(the)f(attac)n(k)h(has)h(succeeded)f(in)f(noticeably)i (a\013ecting)2040 3607 y(the)g(op)r(eration)h(of)h(the)e(sensor)h(net)n (w)n(ork.)32 b(If)20 b(rms)3451 3575 y Fe(\003)3487 3607 y Fn(\()p Fi(f)t(;)13 b(A)p Fn(\))21 b Fq(\031)g Fn(rms)o(\()p Fi(f)8 b Fn(\),)2040 3694 y(the)25 b(attac)n(k)h(has)g(had)f(little)i (or)f(no)f(e\013ect.)35 b(W)-6 b(e)25 b(de\014ne)2137 3833 y(rms)2261 3797 y Fe(\003)2297 3833 y Fn(\()p Fi(f)t(;)13 b(k)r Fn(\))2495 3790 y Fc(def)2503 3833 y Fn(=)28 b(max)o Fq(f)p Fn(rms)2897 3797 y Fe(\003)2933 3833 y Fn(\()p Fi(f)t(;)13 b(A)p Fn(\))21 b(:)h Fi(A)j Fn(is)h(a)g Fi(k)r Fn(-no)r(de)f(attac)n(k)p Fq(g)p Fi(;)2040 3972 y Fn(so)g(that)f(rms) 2422 3940 y Fe(\003)2458 3972 y Fn(\()p Fi(f)t(;)14 b(k)r Fn(\))24 b(denotes)g(the)g(r.m.s.)h(error)g(of)g(the)f(most)g(p)r(o)n (w-)2040 4059 y(erful)d Fi(k)r Fn(-no)r(de)e(attac)n(k)h(p)r(ossible.) 34 b(Note)20 b(that)g(rms)3470 4027 y Fe(\003)3506 4059 y Fn(\()p Fi(f)t(;)13 b Fn(0\))22 b(=)f(rms)o(\()p Fi(f)8 b Fn(\).)2115 4146 y(Roughly)35 b(sp)r(eaking,)40 b(w)n(e)c(think)f(of) i(an)f(aggregation)i(function)2040 4233 y Fi(f)47 b Fn(as)39 b(an)g(instance)g(of)g(the)g Fj(r)l(esilient)h(aggr)l(e)l(gation)46 b Fn(paradigm)39 b(if)2040 4320 y(rms)2164 4289 y Fe(\003)2200 4320 y Fn(\()p Fi(f)t(;)14 b(k)r Fn(\))25 b(gro)n(ws)i(slo)n(wly)g(as)f (a)g(function)g(of)h Fi(k)r Fn(.)34 b(More)27 b(precisely:)2123 4469 y Fb(Definition)40 b Fn(1.)e Fj(We)28 b(say)h(that)g(an)f(aggr)l (e)l(gation)i(function)f Fi(f)36 b Fj(is)2040 4557 y Fn(\()p Fi(k)r(;)13 b(\013)p Fn(\))p Fj(-r)l(esilient)31 b(\(with)e(r)l(esp)l(e)l(ct)j(to)e(a)f(p)l(ar)l(ameterize)l(d)j (distribution)2040 4644 y Fi(p)p Fn(\()p Fi(X)2172 4652 y Fh(i)2220 4644 y Fq(j)21 b Fi(\022)r Fn(\))p Fj(\))28 b(if)f(rms)2590 4612 y Fe(\003)2626 4644 y Fn(\()p Fi(f)t(;)13 b(k)r Fn(\))21 b Fq(\024)h Fi(\013)17 b Fq(\001)g Fj(rms)q Fn(\()p Fi(f)8 b Fn(\))27 b Fj(for)h(the)g(estimator)h Fi(f)8 b Fj(.)2040 4793 y Fn(The)26 b(in)n(tuition)g(is)g(that)f(the)h (\()p Fi(k)r(;)13 b(\013)p Fn(\)-resilien)n(t)26 b(functions,)h(for)f (small)2040 4880 y(v)l(alues)21 b(of)g Fi(\013)p Fn(,)i(are)e(the)f (ones)i(that)e(can)h(b)r(e)f(computed)g(meaningfully)2040 4967 y(and)38 b(securely)h(in)f(the)g(presence)g(of)h(up)f(to)g Fi(k)j Fn(compromised)c(or)2040 5054 y(malicious)27 b(no)r(des.)34 b(This)27 b(is)f(justi\014ed)g(b)n(y)e(the)i(follo)n(wing)i(result.) 2123 5203 y Fb(Inf)n(ormal)h(resul)-5 b(t)42 b Fn(1.)c Fj(L)l(et)21 b Fi(f)28 b Fj(b)l(e)20 b(an)g(unbiase)l(d)h(estimator,)h (i.e.,)2040 5290 y(an)30 b(aggr)l(e)l(gation)i(function)e(satisfying)g Fd(E)5 b Fn([)q Fi(f)j Fn(\()p Fi(X)3407 5298 y Ff(1)3448 5290 y Fi(;)13 b(:)g(:)g(:)h(;)f(X)3682 5298 y Fh(n)3725 5290 y Fn(\))24 b Fq(j)i Fi(\022)r Fn(])f(=)g Fi(\022)2040 5378 y Fj(for)20 b(al)t(l)f Fi(\022)r Fj(.)32 b(L)l(et)21 b Fi(\033)h Fj(denote)f(the)g(standar)l(d)g(deviation)g(of)e Fi(f)8 b Fn(\()p Fi(X)3747 5386 y Ff(1)3782 5378 y Fi(;)14 b(:)f(:)g(:)g(;)g(X)4016 5386 y Fh(n)4059 5378 y Fn(\))p eop %%Page: 6 6 6 5 bop -152 -69 a Fj(in)23 b(the)i(absenc)l(e)g(of)e(c)l(ompr)l(omise) l(d)i(no)l(des.)34 b(If)23 b Fi(f)32 b Fj(is)23 b Fn(\()p Fi(k)r(;)13 b(\013)p Fn(\))p Fj(-r)l(esilient,)-152 19 y(then)24 b(it)e(c)l(an)i(b)l(e)f(c)l(ompute)l(d)h(at)f(a)g(b)l(ase)g (station)h(with)f(bias)g(on)f(the)i(or-)-152 106 y(der)j(of)e Fq(\006)p Fi(\013)12 b Fq(\001)h Fi(\033)28 b Fj(or)e(less.)35 b(Conversely,)27 b(if)e Fi(f)33 b Fj(is)26 b(not)g Fn(\()p Fi(k)r(;)13 b(\013)p Fn(\))p Fj(-r)l(esilient,)-152 193 y(then)31 b(no)f(matter)h(how)f Fi(f)38 b Fj(is)29 b(c)l(ompute)l(d,)i (the)g(adversary)h(c)l(an)e(skew)-152 280 y(the)f(r)l(esult)g(by)e(mor) l(e)i(than)f Fq(\006)p Fi(\013)17 b Fq(\001)g Fi(\033)31 b Fj(at)d(le)l(ast)g(some)g(of)f(the)i(time.)-69 410 y Fb(Pr)n(oof)h(\(inf)n(ormal\).)37 b Fn(Since)18 b Fi(f)27 b Fn(is)19 b(an)f(un)n(biased)g(estimator,)i(w)n(e)-152 497 y(ha)n(v)n(e)29 633 y(rms\()p Fi(f)8 b Fn(\))21 b(=)g Fd(E)6 b Fn([\()467 614 y(^)456 633 y(\002)23 b Fq(\000)17 b Fi(\022)r Fn(\))684 597 y Ff(2)740 633 y Fq(j)k Fi(\022)r Fn(])841 597 y Ff(1)p Fh(=)p Ff(2)960 633 y Fn(=)g(StdDev)n([)1321 614 y(^)1310 633 y(\002)h Fq(j)f Fi(\022)r Fn(])h(=)f Fi(\033)n(:)-152 769 y Fn(If)28 b Fi(f)35 b Fn(is)28 b(\()p Fi(k)r(;)13 b(\013)p Fn(\)-resilien)n(t,)29 b(then)d(rms)902 737 y Fe(\003)938 769 y Fn(\()p Fi(f)t(;)13 b(k)r Fn(\))24 b Fq(\024)f Fi(\013)c Fq(\001)f Fn(rms)o(\()p Fi(f)8 b Fn(\))24 b(=)g Fi(\013)18 b Fq(\001)h Fi(\033)s Fn(.)-152 856 y(In)28 b(this)g(case,)i(the)e(standard)g(deviation)h(of)g(the)f (aggregate)i(\(after)-152 943 y(b)r(eing)c(disturb)r(ed)f(b)n(y)f (compromised)h(no)r(des\))g(is)h(at)g(most)f Fi(\013)17 b Fq(\001)g Fi(\033)s Fn(,)25 b(so)-152 1030 y(the)e(\\t)n(ypical")i (error)f(term)e(is)i(on)g(the)f(order)g(of)h Fi(\013)13 b Fq(\001)g Fi(\033)s Fn(.)34 b(Con)n(v)n(ersely)-6 b(,)-152 1117 y(if)32 b Fi(f)39 b Fn(is)31 b(not)g(\()p Fi(k)r(;)13 b(\013)p Fn(\)-resilien)n(t,)34 b(then)c(there)g(is)i(a)f Fi(k)r Fn(-no)r(de)f(attac)n(k)h Fi(A)-152 1205 y Fn(so)24 b(that)f(rms)229 1173 y Fe(\003)265 1205 y Fn(\()p Fi(f)t(;)13 b(A)p Fn(\))21 b Fi(>)g(\013)12 b Fq(\001)g Fi(\033)s Fn(.)34 b(F)-6 b(or)24 b(reasonable)h(distributions,)f(the)-152 1292 y(magnitude)c(of)h(the)g(actual)g(observ)n(ed)f(error)h(is)h(at)e (least)i(rms)1612 1260 y Fe(\003)1648 1292 y Fn(\()p Fi(f)t(;)13 b(A)p Fn(\))-152 1379 y(some)38 b(non-negligible)h (fraction)g(of)g(the)f(time,)i(from)e(whic)n(h)g(the)-152 1466 y(informal)27 b(result)e(follo)n(ws.)p 695 1416 57 4 v 695 1466 4 50 v 748 1466 V 695 1469 57 4 v -77 1625 a(With)k(the)f(ab)r(o)n(v)n(e)h(results,)h(w)n(e)f(are)h(no)n(w)f (ready)f(to)h(prop)r(ose)h(an)-152 1712 y(answ)n(er)23 b(to)f(the)g(cen)n(tral)g(question)g(of)h(secure)f(aggregation:)35 b(Whic)n(h)-152 1799 y(functionalities)d(can)f(b)r(e)f(meaningfully)g (computed,)g(in)g(the)g(pres-)-152 1886 y(ence)c(of)g(compromised)f(no) r(des?)p -91 1968 1871 4 v -91 2345 4 377 v -39 2042 a Fj(A)n(nswer.)47 b Fn(The)29 b(aggregation)j(functionalities)g(that)d (can)h(b)r(e)-39 2129 y(securely)e(and)g(meaningfully)g(computed,)f(in) h(the)g(presence)-39 2217 y(of)18 b Fi(k)i Fn(compromised)d(no)r(des,)j (are)e(exactly)g(the)f(functions)h(that)-39 2304 y(are)26 b(\()p Fi(k)r(;)13 b(\013)p Fn(\)-resilien)n(t)26 b(for)h(some)e Fi(\013)h Fn(that)g(is)g(not)f(to)r(o)i(large.)p 1776 2345 V -91 2348 1871 4 v -152 2574 a Fg(Attac)n(k)c(models.)40 b Fn(The)27 b(ab)r(o)n(v)n(e)f(de\014nitions)g(are)h(framed)e(in)h (terms)-152 2661 y(of)18 b(what)g(one)f(migh)n(t)f(call)i Fj(omniscient)25 b Fn(attac)n(ks,)20 b(i.e.,)g(attac)n(ks)d(where)-152 2748 y(the)g(adv)n(ersary)g(\014rst)g(observ)n(es)g(all)i Fi(n)e Fn(sensor)h(readings,)i(then)c(c)n(ho)r(oses)-152 2835 y Fi(k)27 b Fn(sensors)f(to)f(corrupt)g(and)f(pic)n(ks)h Fi(k)i Fn(b)r(ogus)e(v)l(alues)g(for)g(these)g(sen-)-152 2922 y(sors)h(to)f(rep)r(ort)g(in)g(place)g(of)h(their)f(actual)g (measuremen)n(ts.)33 b(Hence)-152 3009 y(omniscien)n(t)24 b(attac)n(k)n(ers)h(are)g(limited)f(only)g(b)n(y)f(the)h(n)n(um)n(b)r (er)e(of)j(sen-)-152 3097 y(sor)k(readings)f(they)f(can)g(c)n(hange.)41 b(In)27 b(particular,)i(omniscien)n(t)e(at-)-152 3184 y(tac)n(k)n(ers)19 b(can)g(dynamically)g(c)n(ho)r(ose)g(whic)n(h)g (sensors)h(to)f(corrupt)g(and)-152 3271 y(can)38 b(ea)n(v)n(esdrop)g (or)h(predict)e(all)i(other)f(sensor)h(readings.)72 b(This)-152 3358 y(seems)26 b(lik)n(e)g(an)f(impractical)i(threat)e(mo)r(del.)-77 3445 y(It)40 b(w)n(ould)h(b)r(e)f(more)g(realistic)i(to)f(consider)g Fj(myopic)g(attacks)p Fn(,)-152 3532 y(where)33 b(the)e(adv)n(ersary)h (can)h(only)e(observ)n(e)i(and)e(a\013ect)i(measure-)-152 3620 y(men)n(ts)20 b(from)h(some)f(set)h(of)h Fi(k)h Fn(sensors.)34 b(In)20 b(an)g(adaptiv)n(e)h(attac)n(k,)h(the)-152 3707 y(attac)n(k)n(er)g(can)g(c)n(ho)r(ose)h(a)f(sensor)g(to)g (corrupt,)h(learn)f(the)f(reading)i(at)-152 3794 y(that)i(sensor,)i(c)n (ho)r(ose)f(a)g(replacemen)n(t)e(v)l(alue)h(based)h(on)f(his)h(obser-) -152 3881 y(v)l(ation,)f(and)f(then)g(c)n(ho)r(ose)i(another)e(sensor)h (to)g(corrupt)f(\(p)r(ossibly)-152 3968 y(based)k(on)g(what)h(he)f(has) g(learned)g(up)g(to)g(this)g(p)r(oin)n(t\))g(and)f(rep)r(eat)-152 4055 y(this)h(up)f(to)g Fi(k)j Fn(times.)40 b(A)27 b(w)n(eak)n(er)h (threat)f(mo)r(del)g(is)h(the)g(static)g(at-)-152 4143 y(tac)n(k,)j(where)e(the)g(attac)n(k)n(er)h(m)n(ust)e(c)n(ho)r(ose)i Fi(k)h Fn(sensors)g(in)e(adv)l(ance)-152 4230 y(to)35 b(corrupt;)j(then)c(the)g(attac)n(k)n(er)g(learns)h(those)g Fi(k)h Fn(readings)f(and)-152 4317 y(subsequen)n(tly)21 b(can)h(c)n(ho)r(ose)h Fi(k)h Fn(replacemen)n(ts)d(v)l(alues)h(based)g (on)g(the)-152 4404 y(observ)n(ed)29 b(v)l(alues.)46 b(Of)30 b(course,)h(in)e(all)i(cases)f(w)n(e)g(assume)f(the)g(pa-)-152 4491 y(rameterized)18 b(distribution)g Fi(p)p Fn(\()p Fi(X)802 4499 y Fh(i)849 4491 y Fq(j)k Fi(\022)r Fn(\))c(is)g(kno)n(wn) f(in)h(adv)l(ance)f(to)h(the)-152 4578 y(adv)n(ersary)-6 b(.)47 b(W)-6 b(e)29 b(could)h(also)i(consider)e(man)n(y)e(other)i (re\014nemen)n(ts)-152 4666 y(to)c(the)f(de\014nition.)-77 4753 y(My)n(opic)19 b(attac)n(k)n(ers)h(are)f(a)h(more)e(reasonable)j (threat)e(mo)r(del)f(than)-152 4840 y(omniscien)n(t)30 b(attac)n(k)n(ers,)i(and)e(m)n(y)n(opic)e(attac)n(ks)j(corresp)r(ond)f (more)-152 4927 y(closely)e(to)g(standard)e(threat)h(mo)r(dels)g(used,) g(for)h(instance,)g(in)f(the)-152 5014 y(cryptographic)22 b(literature)f(on)h(secure)f(m)n(ulti-part)n(y)e(computation.)-152 5102 y(Ho)n(w)n(ev)n(er,)h(in)f(all)g(the)f(examples)g(treated)g(in)h (this)f(pap)r(er,)i(the)e(di\013er-)-152 5189 y(ence)23 b(in)g(p)r(o)n(w)n(er)g(b)r(et)n(w)n(een)g(omniscien)n(t)f(and)h(m)n(y) n(opic)e(attac)n(ks)i(turns)-152 5276 y(out)39 b(to)h(b)r(e)f (negligible.)76 b(Because)41 b(omniscien)n(t)d(attac)n(ks)i(p)r(ermit) -152 5363 y(cleaner)27 b(de\014nitions,)f(for)g(simplicit)n(y)-6 b(,)25 b(w)n(e)i(will)g(stic)n(k)e(with)h(them.)2040 -69 y Fg(Rob)n(ust)14 b(statistics.)40 b Fn(Robust)17 b(statistics)i(is)f(the)f(study)g(of)h(statistics)2040 19 y(when)35 b(data)f(is)h(noisy)g(or)g(error-prone.)61 b(Some)34 b(authors)h(suggest)2040 106 y(that)26 b(robust)g(statistics) i(is)f(generally)h(concerned)e(with)g(t)n(w)n(o)h(kinds)2040 193 y(of)g(robustness:)2130 347 y(1.)38 b(T)-6 b(olerating)31 b(small)e(errors)h(in)f(a)h(large)g(fraction)h(of)f(observ)l(a-)2227 435 y(tions.)40 b(F)-6 b(or)28 b(instance,)h(p)r(erhaps)e(man)n(y)f (devices)h(ha)n(v)n(e)g(small)2227 522 y(calibration)g(errors)g(or)f (are)g(otherwise)h(sligh)n(tly)f(noisy)-6 b(.)2130 684 y(2.)38 b(T)-6 b(olerating)31 b(large)f(errors)g(in)f(a)h(small)f (fraction)i(of)f(observ)l(a-)2227 771 y(tions.)52 b(F)-6 b(or)32 b(instance,)i(if)e(w)n(e)g(imagine)g(a)f(scien)n(tist)i (writing)2227 858 y(do)n(wn)e(observ)n(ed)f(v)l(alues)h(b)n(y)f(hand,)i (o)r(ccasionally)h(she)e(ma)n(y)2227 946 y(misplace)36 b(the)f(decimal)h(p)r(oin)n(t.)65 b(A)35 b(few)i(gross)g(errors)f(lik)n (e)2227 1033 y(this)20 b(should)h(not)f(render)g(our)g(statistical)j (estimator)d(useless.)2227 1120 y(Th)n(us,)33 b(a)f(classic)h(task)f (of)g(robust)g(statistics)h(is)f(to)g(dev)n(elop)2227 1207 y(estimators)27 b(that)f(tolerate)h(a)g(small)g(fraction)g(of)h (arbitrarily)2227 1294 y(con)n(taminated)d(observ)l(ations.)2040 1449 y(Resilien)n(t)f(aggregation)i(is)e(concerned)f(with)h(the)f (latter)h(c)n(hallenge;)2040 1536 y(w)n(e)j(wish)h(to)e(build)h (aggregation)i(op)r(erators)f(that)e(cannot)h(b)r(e)g(ma-)2040 1623 y(nipulated)17 b(to)r(o)h(m)n(uc)n(h)d(b)n(y)h(a)i(few)g (malicious)g(or)f(compromised)f(no)r(des.)2115 1710 y(There)27 b(is)f(a)h(health)n(y)f(literature)h(on)f(the)g(\014eld)g(of)h(robust)f (statis-)2040 1798 y(tics)39 b([6,)j(3,)g(13,)g(14].)73 b(F)-6 b(or)38 b(instance,)43 b(it)38 b(is)g(w)n(ell-kno)n(wn)h(in)f (the)2040 1885 y(literature)26 b(that)f(the)f(median)g(is)i(a)f(more)g (robust)f(replacemen)n(t)h(for)2040 1972 y(the)30 b(a)n(v)n(erage.)49 b(Our)30 b(w)n(ork)h(has)f(b)r(een)g(greatly)h(inspired)g(b)n(y)e(man)n (y)2040 2059 y(classic)f(results)e(in)f(robust)h(statistics.)2115 2146 y(One)20 b(useful)h(concept)g(from)f(robust)h(statistics)h(is)f (the)g Fj(br)l(e)l(akdown)2040 2233 y(p)l(oint)p Fn(,)27 b(de\014ned)d(as)2586 2202 y Ff(2)2484 2394 y Fi(\017)2515 2358 y Fe(\003)2572 2351 y Fc(def)2579 2394 y Fn(=)29 b(sup)p Fq(f)p Fi(k)r(=n)22 b Fn(:)g(rms)3137 2358 y Fe(\003)3173 2394 y Fn(\()p Fi(f)t(;)13 b(k)r Fn(\))22 b Fi(<)f Fq(1g)p Fi(:)2040 2538 y Fn(Strictly)26 b(sp)r(eaking,)h(this) g(de\014nition)f(giv)n(es)h(the)f(breakdo)n(wn)g(p)r(oin)n(t)2040 2626 y Fi(\017)2071 2594 y Fe(\003)2107 2626 y Fn(\()p Fi(n)p Fn(\))f(at)g Fi(n)p Fn(,)g(but)f(in)h(practice)g(w)n(e)h (usually)e(tak)n(e)h(the)f(limit)h(as)g Fi(n)d Fq(!)2040 2713 y(1)p Fn(.)47 b(One)29 b(small)h(w)n(ord)g(of)h(caution)f(is)h(in) e(order:)43 b(the)30 b(breakdo)n(wn)2040 2800 y(p)r(oin)n(t)25 b(is)g(only)g(informativ)n(e)g(when)g(the)f(estimator)i(is)f(un)n(b)r (ounded.)2115 2887 y(The)g(relev)l(ance)h(of)g(the)f(breakdo)n(wn)g(p)r (oin)n(t)h(to)f(sensor)h(net)n(w)n(orks)2040 2974 y(is)18 b(that)g(the)f(breakdo)n(wn)h(p)r(oin)n(t)f(indicates)i(the)e(fraction) i Fi(\017)3709 2942 y Fe(\003)3763 2974 y Fn(of)f(no)r(des)2040 3061 y(that)36 b(can)g(b)r(e)f(captured)h(b)r(efore)g(securit)n(y)g (breaks)g(do)n(wn.)65 b(If)36 b(an)2040 3149 y Fi(\017)2071 3117 y Fe(\003)2134 3149 y Fn(fraction)29 b(of)f(no)r(des)f(are)h (compromised,)e(then)h(the)g(r.m.s.)g(error)2040 3236 y(b)r(ecomes)19 b(un)n(b)r(ounded,)g(and)f(the)h(adv)n(ersary)f(can)i (driv)n(e)e(the)h(output)2040 3323 y(of)27 b(the)f(aggregation)i(op)r (eration)f(to)f(tak)n(e)g(on)g(an)n(y)g(v)l(alue)f(he)h(w)n(ould)2040 3410 y(lik)n(e.)35 b(F)-6 b(or)25 b(instance,)i(w)n(e)f(can)f(easily)i (v)n(erify)e(that)h(the)f(a)n(v)n(erage)h(has)2040 3497 y(breakdo)n(wn)32 b(p)r(oin)n(t)h Fi(\017)2674 3466 y Fe(\003)2743 3497 y Fn(=)f(0,)j(b)r(ecause)e(an)n(y)f(single)i (compromised)2040 3584 y(no)r(de)18 b(can)g(b)r(e)f(used)h(to)g(sk)n (ew)g(the)f(a)n(v)n(erage)i(b)n(y)d(an)n(y)h(desired)h(amoun)n(t.)2040 3672 y(Consequen)n(tly)-6 b(,)36 b(the)d(breakdo)n(wn)h(p)r(oin)n(t)g (is)g(one)h(measure)e(of)i(the)2040 3759 y(securit)n(y)i(of)h(an)f (aggregation)i(function)e(against)i(data)e(sp)r(o)r(o\014ng)2040 3846 y(attac)n(ks.)2040 4061 y Fo(6.)99 b(SA)-9 b(TISF)g(A)k(CT)n(OR)m (Y)15 b(AND)g(UNSA)-9 b(TISF)g(A)k(CT)n(OR)m(Y)2214 4177 y(A)g(GGREGA)c(TION)23 b(FUNCTIONS)2115 4285 y Fn(W)-6 b(e)26 b(next)h(apply)f(the)h(theoretical)h(framew)n(ork)f(sk)n(etc)n (hed)g(ab)r(o)n(v)n(e)2040 4372 y(to)d(analyze)h(the)f(resilience)h(of) g(a)g(n)n(um)n(b)r(er)d(of)j(natural)f(aggregation)2040 4459 y(functions.)34 b(See)23 b(T)-6 b(able)24 b(1)g(for)g(a)g(concise) g(summary)d(of)j(our)g(results.)2040 4646 y Fg(Data)44 b(model.)c Fn(Unfortunately)-6 b(,)44 b(the)c(resilience)i(of)g(a)e (function)2040 4733 y Fi(f)48 b Fn(dep)r(ends)38 b(not)h(only)g(on)g (the)g(c)n(hoice)g(of)h Fi(f)8 b Fn(,)43 b(but)38 b(also)j(on)e(the) 2040 4820 y(parametrized)e(distribution)h Fi(p)p Fn(\()p Fi(X)3080 4828 y Fh(i)3147 4820 y Fq(j)j Fi(\022)r Fn(\).)70 b(In)37 b(other)h(w)n(ords,)j(w)n(e)2040 4907 y(will)30 b(need)f(some)g(mo)r(del)f(for)i(ho)n(w)f(the)g(data)g(from)g(the)f (sensors)i(is)2040 4995 y(distributed.)65 b(In)36 b(practice,)k(the)35 b(exact)h(distribution)h(ma)n(y)d(v)l(ary)2040 5082 y(from)g (application)i(to)e(application,)k(but)c(to)g(mak)n(e)f(the)h(analysis) p 2040 5143 797 4 v 2044 5196 a Ff(2)2078 5228 y Fn(Note:)39 b(If)28 b Fi(S)h Fq(\022)c Fd(R)30 b Fn(is)f(a)f(set,)h(sup)12 b Fi(S)32 b Fn(is)c(the)g(smallest)g(real)h(n)n(um)n(b)r(er)2040 5303 y(larger)34 b(than)f(or)g(equal)g(to)g(ev)n(ery)f(elemen)n(t)g(of) i Fi(S)t Fn(.)56 b(If)33 b Fi(S)k Fn(is)d(\014nite,)2040 5378 y(sup)13 b Fi(S)29 b Fn(is)d(just)g(the)g(largest)h(elemen)n(t)e (in)g Fi(S)t Fn(.)p eop %%Page: 7 7 7 6 bop 309 -58 3264 4 v 307 29 4 88 v 353 3 a Fn(aggregate)28 b(\()p Fi(f)8 b Fn(\))p 1189 29 V 482 w(error)26 b(\(rms\()p Fi(f)8 b Fn(\)\))p 1807 29 V 574 w(resilience)27 b(\()p Fi(\013)p Fn(\))p 2819 29 V 94 w(\()p Fi(\017)2931 -29 y Fe(\003)2967 3 y Fn(\))p 3045 29 V 95 w(securit)n(y)e(lev)n(el)p 3571 29 V 309 32 3264 4 v 309 47 V 307 134 4 88 v 353 108 a(minim)n(um)p 1189 134 V 1013 w(|)p 1807 134 V 935 w Fq(1)p 2819 134 V 139 w Fn(0)p 3045 134 V 222 w(insecure)p 3571 134 V 307 221 V 353 195 a(maxim)n(um)p 1189 221 V 998 w(|)p 1807 221 V 935 w Fq(1)p 2819 221 V 139 w Fn(0)p 3045 221 V 222 w(insecure)p 3571 221 V 307 309 V 353 282 a(sum)p 1189 309 V 1551 229 a Fq(p)p 1615 229 47 4 v 53 x Fi(n)18 b Fq(\001)f Fi(\033)p 1807 309 4 88 v 938 w Fq(1)p 2819 309 V 139 w Fn(0)p 3045 309 V 222 w(insecure)p 3571 309 V 307 396 V 353 370 a(a)n(v)n(erage)p 1189 396 V 966 w Fi(\033)s(=)1653 316 y Fq(p)p 1717 316 47 4 v 54 x Fi(n)p 1807 396 4 88 v 936 w Fq(1)p 2819 396 V 139 w Fn(0)p 3045 396 V 222 w(insecure)p 3571 396 V 307 483 V 353 457 a([)p Fi(l)q(;)d(u)p Fn(]-truncated)25 b(a)n(v)n(erage)p 1189 483 V 133 w Fi(\033)s(=)1341 403 y Fq(p)p 1405 403 47 4 v 54 x Fi(n)h Fn(or)g(larger)p 1807 483 4 88 v 328 w(1)18 b(+)f(\()p Fi(u)g Fq(\000)f Fi(l)q Fn(\))p Fi(=\033)21 b Fq(\001)c Fi(k)r(=)2665 403 y Fq(p)p 2730 403 47 4 v 2730 457 a Fi(n)p 2819 483 4 88 v 119 w Fn(|)p 3045 483 V 139 w(problematic)p 3571 483 V 307 570 V 353 544 a(5\045-trimmed)24 b(a)n(v)n(erage)p 1189 570 V 248 w(\(1)17 b(+)g Fi(\017)p Fn(\))g Fq(\001)g Fi(\033)s(=)1653 490 y Fq(p)p 1717 490 47 4 v 54 x Fi(n)p 1807 570 4 88 v 104 w Fn(if)27 b Fi(k)c(<)e Fn(0)p Fi(:)p Fn(05)p Fi(n)p Fn(:)45 b(1)17 b(+)g(6)p Fi(:)p Fn(278)e Fi(k)r(=n)p 2819 570 V 90 w Fn(0)p Fi(:)p Fn(05)p 3045 570 V 208 w(b)r(etter)p 3571 570 V 307 657 V 1189 657 V 1807 657 V 1853 631 a(if)27 b Fi(k)c(>)e Fn(0)p Fi(:)p Fn(05)p Fi(n)p Fn(:)429 b Fq(1)p 2819 657 V 3045 657 V 3571 657 V 307 751 4 94 v 353 725 a Fn(median)p 1189 751 V 796 w(1)p Fi(:)p Fn(253)p Fi(\033)s(=)1651 671 y Fq(p)p 1717 671 47 4 v 1717 725 a Fi(n)p 1807 751 4 94 v 90 w Fn(if)27 b Fi(k)c(<)e(n=)p Fn(2:)36 b Fq(\030)2328 664 y(p)p 2392 664 384 4 v 61 x Fn(1)17 b(+)g(0)p Fi(:)p Fn(101)p Fi(k)2739 703 y Ff(2)p 2819 751 4 94 v 2885 725 a Fn(0)p Fi(:)p Fn(5)p 3045 751 V 124 w(m)n(uc)n(h)24 b(b)r(etter)p 3571 751 V 307 838 4 88 v 1189 838 V 1807 838 V 1853 812 a(if)j Fi(k)c(>)e(n=)p Fn(2:)488 b Fq(1)p 2819 838 V 3045 838 V 3571 838 V 307 934 4 97 v 353 908 a Fn(coun)n(t)p 1189 934 V 1372 844 a Fa(p)p 1449 844 315 4 v 64 x Fi(n\022)r Fn(\(1)18 b Fq(\000)f Fi(\022)r Fn(\))p 1807 934 4 97 v 568 w(1)h(+)f Fi(O)r Fn(\()p Fi(k)r(=)2635 854 y Fq(p)p 2700 854 47 4 v 2700 908 a Fi(n)p Fn(\))p 2819 934 4 97 v 119 w(|)p 3045 934 V 163 w(acceptable)p 3571 934 V 309 938 3264 4 v -152 1157 a Fm(T)-7 b(able)24 b(1:)36 b(Summary)24 b(of)g(results.)38 b(This)24 b(table)h(sho)n(ws)f(sev)n(eral)f(p)r(ossible)i(aggregation)h (functions,)h(their)e(ro)r(ot-mean-square)-152 1244 y(error)33 b(term)e(in)h(the)f(absence)g(of)h(attac)n(ks,)f(their)h(resilience)h (against)f Fi(k)r Fm(-no)r(de)g(attac)n(k,)g(and)f(their)i(breakdo)n (wn)e(p)r(oin)n(t)h(\()p Fi(\017)3937 1213 y Fe(\003)3974 1244 y Fm(\).)-152 1332 y(The)h(smaller)i(the)f(resilience)h Fi(\013)f Fm(is,)g(the)g(greater)h(the)f(securit)n(y)-7 b(.)51 b(Note)34 b(that)h(the)f(5\045-trimmed)h(a)n(v)n(erage)d(p)r (erforms)j(w)n(ell)-152 1419 y(as)d(long)g(as)f Fi(k)c(<)d Fn(0)p Fi(:)p Fn(05)p Fi(n)p Fm(,)33 b(and)f(the)f(median)h(is)f(ev)n (en)f(b)r(etter:)44 b(it)32 b(degrades)g(gracefully)h(for)f Fi(k)26 b(<)e Fn(0)p Fi(:)p Fn(5)p Fi(n)p Fm(.)46 b(The)31 b(other)h(functions)-152 1506 y(p)r(erform)f(less)e(w)n(ell.)-152 1753 y Fn(tractable,)c(it)e(seems)g(reasonable)h(to)f(fo)r(cus)h(on)f (t)n(w)n(o)h(canonical)g(dis-)-152 1840 y(tributions.)-41 1972 y Fq(\017)38 b Fn(F)-6 b(or)19 b(con)n(tin)n(uous)g(data,)i(w)n(e) f(assume)f(that)g(the)f Fi(X)1449 1980 y Fh(i)1495 1972 y Fn(come)h(from)35 2059 y Fi(n)27 b Fn(indep)r(enden)n(t)e(and)g(iden) n(tically)i(distributed)f(\(i.i.d.\))37 b(ran-)35 2146 y(dom)20 b(v)l(ariables)i(with)g(the)f(Gaussian)h(distribution)g Fq(N)11 b Fn(\()p Fi(\022)r(;)i(\033)1777 2115 y Ff(2)1811 2146 y Fn(\))35 2234 y(of)37 b(mean)e Fi(\022)k Fn(and)c(v)l(ariance)i Fi(\033)941 2202 y Ff(2)975 2234 y Fn(,)i(where)e Fi(\033)h Fn(is)f(\014xed)e(in)h(ad-)35 2321 y(v)l(ance)h(and)h Fi(\022)h Fn(represen)n(ts)f(the)f(hidden)g(parameter)g(to)h(b)r(e)35 2408 y(estimated.)e(It)26 b(will)h(b)r(e)g(useful)f(to)h(let)f Fi(')h Fn(and)e(\010)i(denote)f(the)35 2495 y(probabilit)n(y)35 b(densit)n(y)g(and)f(cum)n(ulativ)n(e)g(probabilit)n(y)h(func-)35 2582 y(tions)20 b(for)g(the)f(standard)g(normal)g(distribution)h Fq(N)11 b Fn(\(0)p Fi(;)i Fn(1\),)21 b(i.e.,)35 2689 y Fi(')p Fn(\()p Fi(x)p Fn(\))g(=)345 2658 y Ff(1)p 301 2672 119 4 v 301 2680 a Fe(p)p 351 2680 69 3 v 41 x Ff(2)p Fh(\031)429 2689 y Fi(e)465 2657 y Fe(\000)p Fh(x)548 2636 y Fc(2)580 2657 y Fh(=)p Ff(2)672 2689 y Fn(and)k(\010\()p Fi(x)p Fn(\))c(=)1082 2628 y Fa(R)1134 2649 y Fh(x)1119 2716 y Fe(\0001)1244 2689 y Fi(')p Fn(\()p Fi(t)p Fn(\))13 b Fi(dt)p Fn(.)-41 2844 y Fq(\017)38 b Fn(F)-6 b(or)29 b(0/1-v)l(alued)g(data,)i(let)e(us)g(assume)f(that)h(the)g Fi(X)1615 2852 y Fh(i)1670 2844 y Fn(come)35 2931 y(from)23 b Fi(n)g Fn(i.i.d.)34 b(r.v.'s)24 b(with)f(the)g(Bernoulli)h (distribution,)f(i.e.,)35 3018 y Fi(X)98 3026 y Fh(i)147 3018 y Fq(\030)f Fn(Bernoulli)q(\()p Fi(\022)r Fn(\),)k(or)h(equiv)l (alen)n(tly)-6 b(,)25 b(Pr[)p Fi(X)1383 3026 y Fh(i)1432 3018 y Fn(=)d(1)h Fq(j)f Fi(\022)r Fn(])h(=)e Fi(\022)r Fn(,)35 3105 y(where)30 b(again)g Fi(\022)i Fn(represen)n(ts)d(the)g (hidden)f(parameter)h(to)h(b)r(e)35 3192 y(estimated.)-152 3324 y(It)h(seems)h(reasonable)g(to)g(exp)r(ect)f(that)g(these)h(t)n(w) n(o)f(distributions)-152 3411 y(will)39 b(form)e(a)g(reasonable)h(mo)r (del)f(of)h(sensor)g(readings)f(in)g(man)n(y)-152 3499 y(practical)27 b(applications.)-152 3685 y Fg(Estimator)o(s)14 b(of)g(location.)41 b Fn(In)17 b(practice,)j(the)e(most)f(common)f (goal)-152 3773 y(of)33 b(aggregation)i(is)d(to)h(build)f(an)g (estimate)g(of)h(lo)r(cation,)i(suc)n(h)d(as)-152 3860 y(the)c(mean)f(or)i(mo)r(de)e(or)i(median.)40 b(A)28 b(go)r(o)r(d)h(estimate)f(of)h(lo)r(cation)-152 3947 y Fi(f)45 b Fn(should)36 b(satisfy)i(sev)n(eral)f(prop)r(erties.)67 b(It)36 b(should)g(b)r(e)g Fj(lo)l(c)l(ation)-152 4034 y(e)l(quivariant)p Fn(,)28 b(so)f(that)e Fi(f)8 b Fn(\()p Fi(x)645 4042 y Ff(1)697 4034 y Fn(+)17 b Fi(c;)c(:)g(:)g(:)g(;)h(x) 1022 4042 y Fh(n)1081 4034 y Fn(+)j Fi(c)p Fn(\))22 b(=)f Fi(f)8 b Fn(\()p Fi(x)1443 4042 y Ff(1)1477 4034 y Fi(;)13 b(:)h(:)f(:)g(;)g(x)1692 4042 y Fh(n)1734 4034 y Fn(\))k(+)-152 4121 y Fi(c)40 b Fn(for)h(an)n(y)e(constan)n(t)h Fi(c)p Fn(.)77 b(It)39 b(should)h(b)r(e)g Fj(sc)l(ale)h(e)l(quivariant)p Fn(,)k(so)-152 4208 y(that)29 b Fi(f)8 b Fn(\()p Fi(cx)170 4216 y Ff(1)205 4208 y Fi(;)13 b(:)g(:)g(:)h(;)f(cx)453 4216 y Fh(n)495 4208 y Fn(\))27 b(=)h Fi(c)20 b Fq(\001)f Fi(f)8 b Fn(\()p Fi(x)852 4216 y Ff(1)887 4208 y Fi(;)13 b(:)g(:)g(:)g(;)h(x)1102 4216 y Fh(n)1144 4208 y Fn(\))29 b(for)h(an)n(y)f(constan)n(t)g Fi(c)p Fn(.)-152 4296 y(Also,)40 b(it)d(should)f(ha)n(v)n(e)g(p)r(erm)n(utation)g(symmetry)-6 b(,)36 b(so)h(that)f(p)r(er-)-152 4383 y(m)n(uting)i(the)g(inputs)g(to) h Fi(f)48 b Fn(do)r(es)39 b(not)g(c)n(hange)g(its)g(output,)i(i.e.,) -152 4470 y Fi(f)8 b Fn(\()p Fi(x)-33 4482 y Fh(\031)r Ff(\(1\))88 4470 y Fi(;)13 b(:)g(:)g(:)g(;)g(x)302 4482 y Fh(\031)r Ff(\()p Fh(n)p Ff(\))430 4470 y Fn(\))38 b(=)f Fi(f)8 b Fn(\()p Fi(x)714 4478 y Ff(1)749 4470 y Fi(;)13 b(:)g(:)g(:)g(;)g(x)963 4478 y Fh(n)1005 4470 y Fn(\))36 b(for)g(all)g(p)r(erm)n(utations)f Fi(\031)-152 4557 y Fn(on)c Fq(f)p Fn(1)p Fi(;)14 b(:)f(:)g(:)g(;)g(n)p Fq(g)p Fn(.)50 b(Finally)-6 b(,)32 b(it)f(should)f(b)r(e)h(robust.)49 b(W)-6 b(e)30 b(will)i(study)-152 4644 y(the)26 b(robustness)g(of)g (sev)n(eral)g(p)r(opular)g(estimates)g(of)h(lo)r(cation.)-152 4831 y Fg(The)32 b(aver)o(a)o(g)o(e)d(and)i(sum.)41 b Fn(It)32 b(is)h(easy)f(to)h(v)n(erify)f(that)g(the)g(sum)-152 4918 y Fi(f)8 b Fn(\()p Fi(x)-33 4926 y Ff(1)2 4918 y Fi(;)13 b(:)g(:)g(:)g(;)g(x)216 4926 y Fh(n)258 4918 y Fn(\))27 b(=)g Fi(x)446 4926 y Ff(1)499 4918 y Fn(+)19 b Fq(\001)13 b(\001)g(\001)20 b Fn(+)f Fi(x)810 4926 y Fh(n)881 4918 y Fn(is)30 b(not)e(\(1)p Fi(;)14 b(\013)p Fn(\)-resilien)n(t)30 b(for)f(an)n(y)-152 5005 y(constan)n(t)24 b Fi(\013)p Fn(.)35 b(F)-6 b(or)24 b(instance,)h(for)g(an)n(y)e (\014xed)g Fi(\013)p Fn(,)i(w)n(e)g(can)f(consider)g(a)-152 5093 y(1-no)r(de)19 b(attac)n(k)300 5061 y Ff(3)353 5093 y Fi(A)f Fn(that)h(replaces)h(the)e(\014rst)g(reading)i Fi(x)1460 5101 y Ff(1)1512 5093 y Fn(with)f Fi(x)1724 5061 y Fe(\003)1724 5106 y Ff(1)1781 5093 y Fn(=)p -152 5131 797 4 v -148 5184 a Ff(3)-113 5216 y Fn(These)25 b(attac)n(ks)g(actually)h(do)f(not)f(require)h(the)g(assumption)f(that) -152 5303 y Fi(X)-89 5311 y Fh(i)-37 5303 y Fq(\030)g(N)11 b Fn(\()p Fi(\022)r(;)i(\033)270 5271 y Ff(2)305 5303 y Fn(\);)28 b(in)g(general,)i(it)d(su\016ces)i(merely)e(that)g(rms)o (\()p Fi(f)8 b Fn(\))25 b Fi(<)-152 5378 y Fq(1)p Fn(,)h(e.g.,)h(that)f Fi(f)8 b Fn(\()p Fi(X)439 5386 y Ff(1)474 5378 y Fi(;)13 b(:)g(:)g(:)g(;)h(X)708 5386 y Fh(n)750 5378 y Fn(\))26 b(has)g(\014nite)f(v)l(ariance)h(and)f(bias.)2040 1753 y Fi(x)2084 1761 y Ff(1)2126 1753 y Fn(+)8 b(2)p Fi(\013)g Fq(\001)g Fn(rms)o(\()p Fi(f)g Fn(\);)23 b(this)e(attac)n(k)g(has)g (error)h(term)e(rms)3585 1721 y Fe(\003)3621 1753 y Fn(\()p Fi(f)t(;)13 b(A)p Fn(\))21 b(=)g(2)p Fi(\013)8 b Fq(\001)2040 1840 y Fn(rms)o(\()p Fi(f)g Fn(\),)23 b(hence)e Fi(f)29 b Fn(is)22 b(not)f(\(1)p Fi(;)13 b(\013)p Fn(\)-resilien)n(t.)34 b(Similarly)-6 b(,)22 b(the)f(a)n(v)n(erage)2040 1927 y(is)29 b(not)f(\(1)p Fi(;)13 b(\013)p Fn(\)-resilien)n(t)29 b(for)h(an)n(y)d(constan)n(t)i Fi(\013)p Fn(.)42 b(Put)28 b(another)h(w)n(a)n(y)-6 b(,)2040 2014 y(the)29 b(a)n(v)n(erage)h(and)f (sum)f(ha)n(v)n(e)g(breakdo)n(wn)h(p)r(oin)n(t)g Fi(\017)3581 1983 y Fe(\003)3645 2014 y Fn(=)d(0.)46 b(These)2040 2102 y(p)r(oin)n(ts)32 b(justify)h(our)f(claim)g(in)g(Section)g(3)g (that)g(the)f(a)n(v)n(erage)i(and)2040 2189 y(sum)25 b(cannot)i(b)r(e)f(meaningfully)h(computed)e(in)h(the)g(presence)h(of)g (a)2040 2276 y(malicious)g(sensor)f(no)r(de.)2040 2463 y Fg(The)18 b(minimum)h(and)f(maximum.)40 b Fn(One)22 b(can)g(also)h(sho)n(w)g(that)f(the)2040 2550 y(minim)n(um)27 b(is)k(not)f(\(1)p Fi(;)14 b(\013)p Fn(\)-resilien)n(t)31 b(for)g(an)n(y)f(constan)n(t)g Fi(\013)p Fn(:)44 b(simply)2040 2637 y(consider)27 b(the)e(1-no)r(de)h(attac)n(k)g(that)g(replaces)h Fi(x)3459 2645 y Ff(1)3519 2637 y Fn(with)f Fi(x)3738 2605 y Fe(\003)3738 2650 y Ff(1)3796 2637 y Fn(=)21 b Fi(x)3921 2645 y Ff(1)3973 2637 y Fq(\000)2040 2724 y Fn(2)p Fi(\013)12 b Fq(\001)g Fn(rms)q(\(min)n(\).)34 b(Lik)n(ewise,)25 b(the)e(maxim)n(um)d(is)j(not)g(\(1)p Fi(;)14 b(\013)p Fn(\)-resilien)n(t)2040 2811 y(for)27 b(an)n(y)e Fi(\013)p Fn(.)2040 2998 y Fg(The)39 b(count.)h Fn(In)d(con)n(trast,)42 b(the)37 b(coun)n(t)g(b)r(eha)n(v)n(es)h(m)n (uc)n(h)d(b)r(etter.)2040 3085 y(T)-6 b(ak)n(e)33 b Fi(f)8 b Fn(\()p Fi(x)2352 3093 y Ff(1)2386 3085 y Fi(;)13 b(:)g(:)g(:)g(;)h (x)2601 3093 y Fh(n)2643 3085 y Fn(\))32 b(=)g Fi(x)2841 3093 y Ff(1)2897 3085 y Fn(+)21 b Fq(\001)14 b(\001)f(\001)22 b Fn(+)f Fi(x)3215 3093 y Fh(n)3289 3085 y Fn(for)34 b Fi(X)3477 3093 y Fh(i)3536 3085 y Fq(\030)f Fn(Bernoulli)q(\()p Fi(\022)r Fn(\))2040 3183 y(\(i.i.d.)38 b(r.v.'s\).)f(W)-6 b(e)26 b(ha)n(v)n(e)g(rms)o(\()p Fi(f)8 b Fn(\))23 b(=)3153 3119 y Fa(p)p 3230 3119 315 4 v 64 x Fi(n\022)r Fn(\(1)17 b Fq(\000)g Fi(\022)r Fn(\).)37 b(F)-6 b(or)26 b(a)h Fi(k)r Fn(-no)r(de)2040 3284 y(attac)n(k,)f(a)g(simple)f(argumen)n(t)g (sho)n(ws)h(that)g Fq(j)3362 3265 y Fn(^)3351 3284 y(\002)3411 3253 y Fe(\003)3463 3284 y Fq(\000)3551 3265 y Fn(^)3540 3284 y(\002)p Fq(j)21 b(\024)g Fi(k)28 b Fn(alw)n(a)n(ys,)2040 3382 y(so)e(rms)2259 3350 y Fe(\003)2295 3382 y Fn(\()p Fi(f)t(;)13 b(k)r Fn(\))21 b Fq(\024)2574 3318 y Fa(p)p 2651 3318 435 4 v 64 x Fi(k)2693 3360 y Ff(2)2745 3382 y Fn(+)c(rms)o(\()p Fi(f)8 b Fn(\))3051 3360 y Ff(2)3107 3382 y Fq(\024)21 b Fi(k)e Fn(+)e(rms)o(\()p Fi(f)8 b Fn(\).)2115 3469 y(Consequen)n(tly)-6 b(,)28 b(the)f(coun)n(t)g(is)i (\()p Fi(k)r(;)13 b(\013)p Fn(\)-resilien)n(t)28 b(for)h Fi(\013)c Fn(=)g(1)18 b(+)h Fi(k)h Fq(\001)2040 3565 y Fn(\()p Fi(n\022)r Fn(\(1)h Fq(\000)f Fi(\022)r Fn(\)\))2421 3533 y Fe(\000)p Ff(1)p Fh(=)p Ff(2)2566 3565 y Fn(.)49 b(This)31 b(is)g(a)g(rather)g(slo)n(w-gro)n(wing)i(function)e(of)2040 3652 y Fi(k)r Fn(,)d(so)g(for)h(large)f Fi(n)p Fn(,)h(the)e(coun)n(t)g (app)r(ears)h(to)g(ha)n(v)n(e)f(go)r(o)r(d)h(resilience)2040 3739 y(against)38 b Fi(k)r Fn(-no)r(de)e(attac)n(ks.)67 b(In)35 b(other)i(w)n(ords,)j(the)c(la)n(w)h(of)g(large)2040 3826 y(n)n(um)n(b)r(ers)d(comes)i(to)g(our)g(rescue:)56 b(if)37 b(w)n(e)f(ha)n(v)n(e)f(a)i(large)g(\014eld)f(of)2040 3913 y(sensors)23 b(and)e(w)n(e)h(use)f(the)g(coun)n(t)g(as)h(our)f (aggregate,)k(w)n(e)d(can)g(easily)2040 4001 y(tolerate)27 b(a)f(small)g(n)n(um)n(b)r(er)e(of)i(compromised)f(no)r(des.)2040 4187 y Fg(The)38 b(median.)i Fn(The)e(median)e(is)i(a)f(safer)i (replacemen)n(t)d(for)i(the)2040 4275 y(a)n(v)n(erage.)k(On)27 b(inputs)h Fi(x)2764 4283 y Ff(1)2798 4275 y Fi(;)13 b(:)g(:)g(:)g(;)h(x)3013 4283 y Fh(n)3055 4275 y Fn(,)28 b(let)h Fi(x)3262 4287 y Ff(\(1\))3344 4275 y Fi(;)13 b(:)g(:)g(:)g(;)g(x)3558 4287 y Ff(\()p Fh(n)p Ff(\))3676 4275 y Fn(denote)28 b(the)2040 4362 y Fi(x)2084 4370 y Fh(i)2110 4362 y Fn(-v)l(alues)i(placed)i(in)e(sorted)h(order.)51 b(If)31 b Fi(i)g Fn(is)g(not)g(an)f(in)n(teger,)j(let)2040 4449 y Fi(x)2084 4461 y Ff(\()p Fh(i)p Ff(\))2188 4449 y Fn(b)r(e)d(short-hand)f(for)2821 4418 y Ff(1)p 2821 4432 31 4 v 2821 4474 a(2)2862 4449 y Fi(x)2906 4461 y Ff(\()p Fh(i)p Fe(\000)p Ff(0)p Fh(:)p Ff(5\))3127 4449 y Fn(+)3217 4418 y Ff(1)p 3217 4432 V 3217 4474 a(2)3257 4449 y Fi(x)3301 4461 y Ff(\()p Fh(i)p Ff(+0)p Fh(:)p Ff(5\))3502 4449 y Fn(.)47 b(Then)30 b(w)n(e)g(ma)n(y)2040 4536 y(de\014ne)j(the)h(median)f(as)i Fi(f)8 b Fn(\()p Fi(x)2910 4544 y Ff(1)2944 4536 y Fi(;)14 b(:)f(:)g(:)g(;)g(x)3159 4544 y Fh(n)3201 4536 y Fn(\))35 b(=)g(med)3502 4545 y Ff(1)p Fe(\024)p Fh(i)p Fe(\024)p Fh(n)3706 4536 y Fi(x)3750 4544 y Fh(i)3811 4536 y Fn(=)g Fi(x)3950 4548 y Ff(\()p Fh(r)r Ff(\))2040 4623 y Fn(where)26 b Fi(r)d Fn(=)e(\()p Fi(n)d Fn(+)e(1\))p Fi(=)p Fn(2.)2115 4710 y(Note)34 b(that)g(a)h(1-no)r(de)f(attac)n(k)h(can)f(only)h(c)n(hange)f (the)g(median)2040 4798 y(to)24 b(something)f(b)r(et)n(w)n(een)h Fi(x)2836 4810 y Ff(\()p Fh(r)r Fe(\000)p Ff(1\))3020 4798 y Fn(and)g Fi(x)3212 4810 y Ff(\()p Fh(r)r Ff(+1\))3371 4798 y Fn(.)34 b(If)23 b(w)n(e)i(ha)n(v)n(e)e(at)h(least)2040 4885 y(three)c(readings,)j(these)e(t)n(w)n(o)g(endp)r(oin)n(ts)f(are)h (sensor)g(readings)h(from)2040 4972 y(uncompromised)33 b(no)r(des.)62 b(In)34 b(general,)39 b(after)d(a)f Fi(k)r Fn(-no)r(de)f(attac)n(k,)2040 5059 y(the)23 b(median)g(will)h(b)r(e)g (in)f(the)g(in)n(terv)l(al)g([)p Fi(x)3239 5071 y Ff(\()p Fh(r)r Fe(\000)p Fh(k)q Ff(\))3403 5059 y Fi(;)14 b(x)3482 5071 y Ff(\()p Fh(r)r Ff(+)p Fh(k)q Ff(\))3644 5059 y Fn(],)25 b(and)e(when)2040 5146 y Fi(n)41 b(>)f Fn(2)p Fi(k)r Fn(,)g(the)d(endp)r(oin)n(ts)g(of)g(this)g(in)n(terv)l(al)g(are) h(readings)g(from)2040 5234 y(uncompromised)16 b(no)r(des.)32 b(In)17 b(summary)-6 b(,)17 b(w)n(e)h(see)g(that)f(the)h(attac)n(k)n (er)2040 5321 y(is)37 b(not)e(able)i(to)f(freely)h(dictate)f(the)g (result)g(of)h(the)e(aggregation)p eop %%Page: 8 8 8 7 bop -152 -69 a Fn(op)r(eration,)36 b(but)31 b(is)i(constrained)g (ab)r(out)g(ho)n(w)g(he)f(can)g(a\013ect)h(the)-152 19 y(computed)24 b(median.)-77 106 y(This)33 b(in)n(tuition)f(can)g(b)r(e) g(quan)n(ti\014ed.)52 b(F)-6 b(or)32 b Fi(X)1297 114 y Fh(i)1356 106 y Fq(\030)g(N)11 b Fn(\()p Fi(\022)r(;)i(\033)1671 74 y Ff(2)1705 106 y Fn(\),)34 b(it)-152 193 y(is)h(w)n(ell-kno)n(wn)g (that)e(rms\()p Fi(f)8 b Fn(\))36 b Fq(\031)f Fn(1)p Fi(:)p Fn(253)24 b Fq(\001)g Fi(\033)s(=)1204 139 y Fq(p)p 1268 139 47 4 v 54 x Fi(n)p Fn(.)60 b(W)-6 b(e)34 b(ha)n(v)n(e)f(cal-) -152 280 y(culated)39 b(that,)i(for)e Fi(k)44 b Fq(\034)e Fi(n)p Fn(,)f(rms)899 248 y Fe(\003)935 280 y Fn(\()p Fi(f)t(;)13 b(k)r Fn(\))42 b(=)g Fi(\013)25 b Fq(\001)h Fn(rms)o(\()p Fi(f)8 b Fn(\))38 b(where)-152 367 y Fi(\013)26 b Fq(\031)9 306 y(p)p 73 306 384 4 v 61 x Fn(1)17 b(+)g(0)p Fi(:)p Fn(101)p Fi(k)420 346 y Ff(2)457 367 y Fn(.)42 b(Th)n(us,)30 b Fi(f)36 b Fn(is)29 b(\()p Fi(k)r(;)13 b(\013)p Fn(\)-resilien)n(t)29 b(for)h(this)e(v)l(alue)-152 454 y(of)j Fi(\013)p Fn(.)47 b(See)29 b(the)g(app)r(endix)g(for)i(a)f (justi\014cation.)47 b(The)30 b(in)n(terpreta-)-152 542 y(tion)h(is)f(that,)i(in)e(the)f(presence)i(of)g(an)f(adv)n(ersary)-6 b(,)31 b(compromised)-152 629 y(no)r(des)37 b(pro)r(duce)f(only)f(a)i (gradual)g(increase)g(in)f(the)g(error)g(term.)-152 716 y(These)c(\014gures)g(also)g(sho)n(w)g(that)f(the)g(\\price)h(of)h (securit)n(y")e(is)h(not)-152 803 y(to)r(o)h(high:)48 b(in)33 b(the)f(absence)g(of)h(attac)n(k,)i(the)d(error)h(term)e(for)i (the)-152 890 y(median)22 b(is)h(only)g(sligh)n(tly)g(larger)h(\(b)n(y) d(a)i(factor)h(of)g(1)p Fi(:)p Fn(253\))g(than)e(the)-152 977 y(error)27 b(term)d(for)j(the)e(a)n(v)n(erage.)-77 1065 y(Also,)41 b(the)36 b(breakdo)n(wn)h(p)r(oin)n(t)g(of)g(the)g (median)f(is)h Fi(\017)1528 1033 y Fe(\003)1605 1065 y Fn(=)i(1)p Fi(=)p Fn(2,)-152 1152 y(meaning)22 b(that)g(up)g(to)g(ab) r(out)h(half)g(of)g(the)f(no)r(des)g(ma)n(y)f(b)r(e)i(compro-)-152 1239 y(mised)i(without)h(a)g(total)h(breakdo)n(wn)e(of)i(securit)n(y)-6 b(.)-152 1460 y Fo(7.)100 b(T)n(OOLS)48 b(FOR)f(A)-5 b(CHIEVING)45 b(RESILIENT)23 1576 y(A)-5 b(GGREGA)c(TION)-77 1684 y Fn(Next,)23 b(w)n(e)g(explore)g(sev)n(eral)h(general)g(tec)n (hniques)e(for)i(impro)n(ving)-152 1771 y(the)j(resilience)i(of)f(our)g (aggregation)i(functions.)40 b(The)27 b(fo)r(cus)i(is)f(on)-152 1858 y(generalit)n(y:)34 b(the)23 b(ideas)g(presen)n(ted)g(here)f(will) j(b)r(e)d(broadly)h(applica-)-152 1945 y(ble)i(in)f(man)n(y)e (settings,)k(and)e(w)n(e)h(c)n(haracterize)g(their)f(b)r(ene\014ts)g (and)-152 2032 y(limitations.)-152 2219 y Fg(T)-5 b(runcation.)40 b Fn(One)28 b(naiv)n(e)h(w)n(a)n(y)h(to)f(mak)n(e)f(an)i(aggregation)h (func-)-152 2306 y(tion)24 b(more)f(robust)h(against)h(sp)r(o)r(ofed)f (sensor)h(readings)f(is)g(to)g(place)-152 2394 y(upp)r(er)f(and)f(lo)n (w)n(er)j(b)r(ounds)d(on)h(the)g(acceptable)h(range)g(of)g(a)f(sensor) -152 2481 y(reading.)35 b(F)-6 b(or)24 b(instance,)h(if)g(w)n(e)f(kno)n (w)g(that)f(v)l(alid)h(sensor)h(readings)-152 2568 y(will)35 b(usually)e(b)r(e)h(in)f(the)g(in)n(terv)l(al)g([)p Fi(l)q(;)13 b(u)p Fn(],)36 b(then)d(w)n(e)h(can)f(truncate)-152 2655 y(ev)n(ery)22 b(input)g(to)h(b)r(e)f(within)h(this)g(range.)34 b(Note,)24 b(for)f(instance,)h(that)-152 2742 y(the)j(coun)n(t)f(can)g (b)r(e)h(view)n(ed)g(as)g(a)g([0)p Fi(;)14 b Fn(1]-truncated)26 b(v)n(ersion)h(of)g(the)-152 2829 y(sum.)52 b(In)31 b(general,)j(giv)n (en)e(an)n(y)f(base)h(aggregate)i Fi(g)s Fn(,)e(w)n(e)g(can)g(con-)-152 2917 y(struct)19 b(a)g(truncated)g(aggregator)i(b)n(y)d(applying)h Fi(g)j Fn(to)d(the)f(truncated)-152 3004 y(data)26 b(v)l(alues.)-77 3091 y(More)21 b(formally)-6 b(,)22 b(let)e(trunc)715 3103 y Ff([)p Fh(l;u)p Ff(])830 3091 y Fn(\()p Fi(x)p Fn(\))f(b)r(e)h Fi(l)i Fn(if)e Fi(x)h(<)g(l)q Fn(,)h Fi(x)e Fn(if)h Fi(l)h Fq(\024)f Fi(x)g Fq(\024)g Fi(u)p Fn(,)-152 3178 y(and)28 b Fi(u)g Fn(if)h Fi(x)c(>)h(u)p Fn(.)42 b(T)-6 b(o)28 b(obtain)h(a)f(truncated)g(replacemen)n(t)f(for)i (the)-152 3265 y(ra)n(w)e(a)n(v)n(erage,)f(set)-22 3459 y Fi(f)8 b Fn(\()p Fi(x)97 3467 y Ff(1)132 3459 y Fi(;)13 b(:)g(:)g(:)g(;)g(x)346 3467 y Fh(n)388 3459 y Fn(\))21 b(=)530 3405 y(trunc)710 3417 y Ff([)p Fh(l;u)p Ff(])825 3405 y Fn(\()p Fi(x)899 3413 y Ff(1)933 3405 y Fn(\))c(+)f Fq(\001)d(\001)h(\001)j Fn(+)g(trunc)1419 3417 y Ff([)p Fh(l;u)p Ff(])1534 3405 y Fn(\()p Fi(x)1608 3413 y Fh(n)1650 3405 y Fn(\))p 530 3441 1150 4 v 1082 3509 a Fi(n)1690 3459 y(:)-152 3634 y Fn(W)-6 b(e)18 b(ha)n(v)n(e)f(calculated)i(that)e (the)h([)p Fi(l)q(;)c(u)p Fn(]-truncated)j(a)n(v)n(erage)i(is)f(\()p Fi(k)r(;)13 b(\013)p Fn(\)-)-152 3721 y(resilien)n(t)29 b(for)g Fi(\013)d Fq(\031)f Fn(1)19 b(+)g(\()p Fi(u)f Fq(\000)h Fi(l)q Fn(\))p Fi(k)r(=)p Fn(\()p Fi(\033)937 3667 y Fq(p)p 1001 3667 47 4 v 54 x Fi(n)p Fn(\).)42 b(See)28 b(the)g(app)r(endix)f(for)-152 3808 y(details.)-77 3896 y(The)d(truncated)e(aggregate)k(is)e(an)f(impro)n(v)n(emen)n(t)e (o)n(v)n(er)i(the)g(con-)-152 3983 y(v)n(en)n(tional)37 b(aggregate,)43 b(but)36 b(it)h(is)h(not)f(an)g(en)n(tirely)g (satisfactory)-152 4070 y(solution.)60 b(Wide)34 b(in)n(terv)l(als)g (giv)n(e)g(the)g(attac)n(k)n(er)g(a)g(great)h(deal)f(of)-152 4157 y(p)r(o)n(w)n(er,)c(while)f(narro)n(w)f(in)n(terv)l(als)h(reduce)e (the)h(utilit)n(y)g(of)h(the)e(sen-)-152 4244 y(sor)k(net)n(w)n(ork.)48 b(W)-6 b(e)30 b(can)g(quan)n(tify)f(this)i(using)f(the)g(notion)g(of)h (the)-152 4332 y Fj(dynamic)39 b(r)l(ange)44 b Fi(D)c Fn(of)e(an)f(aggregate,)43 b(de\014ned)36 b(as)i Fi(D)44 b Fn(=)c(\()p Fi(u)25 b Fq(\000)-152 4419 y Fi(l)q Fn(\))p Fi(=)p Fn(rms\()p Fi(f)8 b Fn(\).)36 b(In)26 b(the)f(absence)i(of)g (attac)n(ks,)g Fi(D)h Fn(measures)e(the)g(n)n(um-)-152 4506 y(b)r(er)e(of)g(p)r(ossible)g(outputs)f(after)h(aggregation)i (that)d(can)g(b)r(e)g(distin-)-152 4593 y(guished)g(from)g(eac)n(h)f (other.)34 b(Th)n(us,)24 b(the)e(observ)n(ed)g(aggregate)j(con-)-152 4680 y(v)n(eys)i(roughly)h(lg)15 b Fi(D)30 b Fn(bits)e(of)h (information)f(ab)r(out)g(the)f(underlying)-152 4767 y(parameter)19 b(to)g(b)r(e)g(estimated.)32 b(Also,)21 b(let)f Fi(D)1131 4736 y Fe(\003)1188 4767 y Fn(=)i(\()p Fi(u)t Fq(\000)t Fi(l)q Fn(\))p Fi(=)p Fn(rms)1628 4736 y Fe(\003)1664 4767 y Fn(\()p Fi(f)t(;)13 b(k)r Fn(\))-152 4855 y(b)r(e)26 b(the)f(dynamic)f(range)j(in)e(the)h(presence)f(of)i Fi(k)r Fn(-no)r(de)e(attac)n(ks.)-77 4942 y(F)-6 b(or)21 b(the)g(truncated)g(mean,)g(w)n(e)h(ha)n(v)n(e)f Fi(D)i Fq(\031)e Fn(\()p Fi(u)8 b Fq(\000)g Fi(l)q Fn(\))1405 4888 y Fq(p)p 1470 4888 V 1470 4942 a Fi(n=\033)s Fn(,)22 b(so)g(the)-152 5029 y(truncated)d(a)n(v)n(erage)h(is)g(\()p Fi(k)r(;)13 b(\013)p Fn(\)-resilien)n(t)21 b(for)f Fi(\013)h Fq(\031)g Fn(1)5 b(+)g Fi(D)i Fq(\001)e Fi(k)r(=n)p Fn(.)33 b(Also,)-152 5116 y Fi(D)-87 5084 y Fe(\003)-29 5116 y Fq(\031)21 b Fi(D)r(=)p Fn(\(1)s(+)s Fi(D)5 b Fq(\001)s Fi(k)r(=n)p Fn(\).)36 b(Notice)19 b(that)f(when)h Fi(D)i Fn(is)e(large)h(compared)-152 5203 y(to)h Fi(n=k)r Fn(,)i Fi(D)172 5171 y Fe(\003)229 5203 y Fn(is)f(considerably)f(smaller)g (\(indicating)h(p)r(o)r(or)f(dynamic)-152 5290 y(range)k(under)e(attac) n(k\))g(and)h Fi(\013)g Fn(is)g(large)h(\(indicating)f(p)r(o)r(or)h (securit)n(y)-152 5378 y(under)c(attac)n(k\).)33 b(When)21 b Fi(D)j Fn(is)e(small,)h(the)e(dynamic)f(range)j(is)f(p)r(o)r(or,)2040 -69 y(meaning)i(that)g(the)g(aggregate)j(do)r(es)e(not)g(con)n(v)n(ey)e (m)n(uc)n(h)g(informa-)2040 19 y(tion)j(ev)n(en)f(in)h(the)f(absence)h (of)g(attac)n(k.)2115 106 y(No)n(w)j(w)n(e)f(are)h(pinned)f(b)r(et)n(w) n(een)g(a)h(ro)r(c)n(k)g(and)f(a)g(hard)h(place:)40 b(to)2040 193 y(deriv)n(e)24 b(as)h(m)n(uc)n(h)d(information)i(as)h(p)r(ossible)g (from)f(our)g(sensor)h(net-)2040 280 y(w)n(ork)k(in)f(the)g(absence)g (of)i(attac)n(ks,)f(w)n(e)g(need)f Fi(D)i Fn(to)f(b)r(e)f(large;)j(y)n (et)2040 367 y(to)26 b(mak)n(e)f(the)h(truncated)g(a)n(v)n(erage)h(as)f (meaningful)h(as)f(p)r(ossible)i(in)2040 454 y(the)g(presence)g(of)h (attac)n(ks,)h(w)n(e)e(need)g Fi(D)21 b Fq(\001)e Fi(k)r(=n)29 b Fn(to)g(b)r(e)f(small.)42 b(This)2040 542 y(giv)n(es)30 b(an)g(una)n(v)n(oidable)g(tradeo\013)g(b)r(et)n(w)n(een)f(the)h (resilience)h Fi(\013)f Fn(and)2040 629 y(the)23 b(dynamic)g(range)h Fi(D)r Fn(.)34 b(This)24 b(tension)g(suggests)h(that)f(w)n(e)g(should) 2040 716 y(k)n(eep)h(lo)r(oking)i(for)f(b)r(etter)g(tec)n(hniques.)2040 903 y Fg(T)-5 b(rimming.)41 b Fn(A)23 b(b)r(etter)g(c)n(hoice)i(is)f (to)g(ignore)h(the)e(highest)h(5\045)g(and)2040 990 y(lo)n(w)n(est)36 b(5\045)f(\(for)g(instance\))g(of)g(the)g(sensor)g(readings,)j(and)c (then)2040 1077 y(compute)g(the)g(aggregate)j(on)e(the)g(remaining)f (90\045)i(of)g(readings)2040 1164 y(in)30 b(the)g(middle.)47 b(This)31 b(is)f(kno)n(wn)g(as)h(the)f Fj(trimme)l(d)h(me)l(an)37 b Fn(in)30 b(the)2040 1251 y(statistical)c(literature.)35 b(In)n(tuitiv)n(ely)-6 b(,)23 b(w)n(e)h(migh)n(t)f(exp)r(ect)h(this)g (to)g(b)r(e)2040 1339 y(fairly)e(robust)e(to)g(compromised)g(no)r(des,) i(so)f(long)g(as)g(no)f(more)g(than)2040 1426 y(5\045)26 b(of)h(the)e(sensors)i(are)f(compromised.)2115 1513 y(Let's)j(w)n(ork)g (out)g(the)g(details.)45 b(On)28 b(inputs)g Fi(x)3470 1521 y Ff(1)3504 1513 y Fi(;)13 b(:)g(:)h(:)f(;)g(x)3719 1521 y Fh(n)3761 1513 y Fn(,)30 b(let)f(the)2040 1600 y(sym)n(b)r(ols)i Fi(x)2383 1612 y Ff(\(1\))2465 1600 y Fi(;)13 b(:)g(:)g(:)h(;)f(x)2680 1612 y Ff(\()p Fh(n)p Ff(\))2801 1600 y Fn(represen)n(t)31 b(the)g Fi(x)3320 1608 y Fh(i)3346 1600 y Fn(-v)l(alues)g(in)h(sorted)g(or-)2040 1687 y(der.)g(Fix)19 b(a)g(securit)n(y)g(parameter)f Fi(\032)p Fn(.)32 b(Let)19 b Fi(g)i Fn(denote)e(the)f(underlying)2040 1774 y(aggregation)28 b(function.)34 b(W)-6 b(e)25 b(construct)h(a)f (more)g(resilien)n(t)h(v)n(ersion)2040 1862 y(of)h Fi(g)g Fn(b)n(y)e(de\014ning)2220 1996 y Fi(f)2257 2004 y Fh(\032)2293 1996 y Fn(\()p Fi(x)2367 2004 y Ff(1)2401 1996 y Fi(;)13 b(:)g(:)g(:)h(;)f(x)2616 2004 y Fh(n)2658 1996 y Fn(\))21 b(=)g Fi(g)s Fn(\()p Fi(x)2904 2008 y Ff(\()p Fh(\032n)p Ff(\))3025 1996 y Fi(;)13 b(x)3103 2008 y Ff(\()p Fh(\032n)p Ff(+1\))3302 1996 y Fi(;)g(:)g(:)g(:)g(;)h(x)3517 2008 y Ff(\()p Fh(n)p Ff(+1)p Fe(\000)p Fh(\032n)p Ff(\))3802 1996 y Fn(\))p Fi(:)2040 2131 y Fn(T)-6 b(rimming)21 b(can)i(b)r(e)g(view)n(ed)g(as)g(a)g(principled,)g(automated)f(form)h (of)2040 2218 y(outlier)k(elimination,)f(where)g(w)n(e)g(alw)n(a)n(ys)h (thro)n(w)f(a)n(w)n(a)n(y)g(the)g(small-)2040 2305 y(est)k(and)f (largest)i Fi(\032n)e Fn(observ)l(ations,)j(on)d(the)g(principle)h (that)f(they)2040 2392 y(migh)n(t)e(b)r(e)h(outliers.)43 b(Assuming)27 b(that)h Fi(k)f(<)e(\032n)p Fn(,)k(all)g(an)f(adv)n (ersary)2040 2480 y(can)18 b(do)g(is)g(a\013ect)h(whic)n(h)f(subset)f (of)i(legitimate)g(sensor)f(readings)h(are)2040 2567 y(used)28 b(as)h(inputs)f(to)h Fi(g)s Fn(;)g(ho)n(w)n(ev)n(er,)g(the)f (adv)n(ersary)g(cannot)h(con)n(trol)2040 2654 y(in)d(an)n(y)g(other)h (w)n(a)n(y)f(the)g(inputs)g(to)g Fi(g)s Fn(.)36 b(In)n(terestingly)-6 b(,)26 b(the)g(median)2040 2741 y(is)f(a)f(sp)r(ecial)h(case)g(of)g (the)e(ab)r(o)n(v)n(e)h(construction,)h(obtained)f(b)n(y)f(tak-)2040 2828 y(ing)35 b(the)f(limit)g(as)h Fi(\032)h Fq(!)f Fn(1)p Fi(=)p Fn(2)h(from)e(b)r(elo)n(w.)62 b(F)-6 b(or)35 b(these)f(reasons,) 2040 2915 y(trimming)24 b(lo)r(oks)j(in)n(tuitiv)n(ely)e(promising.) 2115 3003 y(The)j(securit)n(y)g(argumen)n(t)f(can)i(b)r(e)f(formalized) h(more)f(carefully)-6 b(.)2040 3090 y(W)g(e)17 b(will)h(analyze)g(the)f (case)h(where)f Fi(g)j Fn(is)d(the)g(a)n(v)n(erage,)j Fi(g)s Fn(\()p Fi(w)3722 3098 y Ff(1)3756 3090 y Fi(;)13 b(:)g(:)g(:)g(;)h(w)3982 3098 y Fh(m)4040 3090 y Fn(\))21 b(=)2040 3177 y(\()p Fi(w)2125 3185 y Ff(1)2179 3177 y Fn(+)e Fq(\001)13 b(\001)g(\001)19 b Fn(+)g Fi(w)2500 3185 y Fh(m)2559 3177 y Fn(\))p Fi(=m)p Fn(.)43 b(It)29 b(turns)f(out)h(that)f(rms)o(\()p Fi(f)3550 3185 y Fh(\032)3586 3177 y Fn(\))f Fq(\031)f Fn(\(1)19 b(+)g Fi(\017)3926 3185 y Fh(\032)3962 3177 y Fn(\))g Fq(\001)2040 3264 y Fi(\033)s(=)2125 3210 y Fq(p)p 2189 3210 V 54 x Fi(n)p Fn(,)36 b(for)e(some)e(constan)n(t)i(0)g Fq(\024)f Fi(\017)3130 3272 y Fh(\032)3200 3264 y Fq(\024)h Fn(0)p Fi(:)p Fn(253.)58 b(W)-6 b(e)33 b(ha)n(v)n(e)g(com-)2040 3351 y(puted)23 b(rms)2380 3319 y Fe(\003)2416 3351 y Fn(\()p Fi(f)2483 3359 y Fh(\032)2519 3351 y Fi(;)13 b(k)r Fn(\))24 b(for)g(the)g(case)g Fi(k)g Fq(\034)d Fi(\013n)p Fn(,)k(where)f Fi(\032)f Fn(is)h(arbitrary)-6 b(.)2040 3438 y(See)26 b(the)f(app)r(endix)g(for)h (details)h(and)e(for)i(the)e(general)i(expression.)2040 3526 y(F)-6 b(or)23 b(instance,)i(when)e Fi(\013)f Fn(=)f(0)p Fi(:)p Fn(05,)k(rms)o(\()p Fi(f)3216 3534 y Ff(0)p Fh(:)p Ff(05)3331 3526 y Fn(\))c Fq(\031)g Fn(\(1)12 b(+)g Fi(\017)p Fn(\))g Fq(\001)g Fi(\033)s(=)3806 3472 y Fq(p)p 3871 3472 V 3871 3526 a Fi(n)24 b Fn(for)2040 3613 y(some)i(small)g Fi(\017)p Fn(,)h(and)e Fi(f)2699 3621 y Ff(0)p Fh(:)p Ff(05)2840 3613 y Fn(is)i(appro)n(ximately)e(\()p Fi(k)r(;)13 b Fn(1)18 b(+)f(6)p Fi(:)p Fn(278)d Fi(k)r(=n)p Fn(\)-)2040 3700 y(resilien)n(t)27 b(for)f Fi(k)e(<)d Fn(0)p Fi(:)p Fn(05)p Fi(n)27 b Fn(and)f(\()p Fi(k)r(;)13 b Fq(1)p Fn(\)-resilien)n(t)26 b(for)g Fi(k)e Fq(\025)d Fn(0)p Fi(:)p Fn(05)p Fi(n)p Fn(.)2115 3787 y(In)28 b(practice,)i(the)f (5\045-trimmed)d(a)n(v)n(erage)k(only)e(b)r(ecomes)h(more)2040 3874 y(accurate)h(than)f(the)f(median)g(for)i(large)h Fi(n)e Fn(\(sa)n(y)-6 b(,)30 b Fi(n)d(>)g Fn(100)j(or)g(so\).)2040 3961 y(Therefore,)37 b(in)d(practice)g(the)f(5\045-trimmed)e(a)n(v)n (erage)j(is)g(unlik)n(ely)2040 4049 y(to)k(b)r(e)f(an)n(y)g(b)r(etter)g (than)g(the)g(median.)69 b(Ho)n(w)n(ev)n(er,)41 b(one)d(of)g(the)2040 4136 y(attractions)c(of)g(trimming)e(is)i(that)f(it)g(can)h(b)r(e)f (applied)g(to)h(other)2040 4223 y(aggregates)29 b(as)d(w)n(ell;)i(for)e (instance,)h(the)f(5\045-trimmed)e(maxim)n(um)2040 4310 y(migh)n(t)h(b)r(e)g(a)h(sensible)h(replacemen)n(t)e(for)h(the)g(maxim) n(um.)2040 4497 y Fg(Other)19 b(estimates)g(of)h(location.)41 b Fn(Man)n(y)23 b(other)g(lo)r(cation)i(estima-)2040 4584 y(tors)31 b(ha)n(v)n(e)f(b)r(een)g(prop)r(osed)g(in)g(the)g (robust)h(statistics)g(literature.)2040 4671 y(Here)26 b(w)n(e)g(list)g(a)g(few)h(that)e(ma)n(y)g(b)r(e)g(of)i(in)n(terest.) 2115 4758 y(The)35 b Fj(shorth)43 b Fn(is)36 b(de\014ned)e(as)i(the)f (mean)g(of)h(the)f(shortest)g(sub-)2040 4846 y(sample)28 b(of)h Fi(x)2433 4854 y Ff(1)2467 4846 y Fi(;)13 b(:)g(:)g(:)g(;)g(x) 2681 4854 y Fh(n)2751 4846 y Fn(that)28 b(con)n(tains)g Fi(n=)p Fn(2)h(of)g(the)f(observ)l(ations;)2040 4933 y(its)20 b(breakdo)n(wn)f(p)r(oin)n(t)g(is)h Fi(\017)2819 4901 y Fe(\003)2876 4933 y Fn(=)h(1)p Fi(=)p Fn(2.)34 b(The)19 b Fj(le)l(ast)k(me)l(dian)e(of)h(squar)l(es)2040 5020 y Fn(\(LMS\))17 b(is)h(de\014ned)e(as)h(the)g(v)l(alue)g Fi(y)j Fn(that)c(minimizes)h(med)3709 5029 y Ff(1)p Fe(\024)p Fh(i)p Fe(\024)p Fh(n)3900 5020 y Fn(\()p Fi(x)3974 5028 y Fh(i)3999 5020 y Fq(\000)2040 5107 y Fi(y)s Fn(\))2111 5075 y Ff(2)2145 5107 y Fn(;)24 b(it)f(happ)r(ens)g(to)g(b)r(e)g(the)f (same)h(as)g(the)g(midp)r(oin)n(t)f(of)h(the)g(short-)2040 5194 y(est)34 b(subsample)g(con)n(taining)g Fi(n=)p Fn(2)h(of)g(the)f (observ)l(ations,)j(and)c(its)2040 5282 y(breakdo)n(wn)23 b(p)r(oin)n(t)g(is)h Fi(\017)2730 5250 y Fe(\003)2788 5282 y Fn(=)d(1)p Fi(=)p Fn(2.)35 b(Both)23 b(the)g(shorth)h(and)f(the) g(LMS)2040 5378 y(con)n(v)n(erge)18 b(at)f(a)h(rate)f(lik)n(e)h Fi(n)2815 5346 y Fe(\000)p Ff(1)p Fh(=)p Ff(3)2960 5378 y Fn(,)h(whic)n(h)f(is)f(abnormally)g(slo)n(w:)32 b(most)p eop %%Page: 9 9 9 8 bop -152 -69 a Fn(other)25 b(estimates,)h(suc)n(h)e(as)h(the)g(a)n (v)n(erage,)h(con)n(v)n(erge)f(at)f(a)i(rate)f(lik)n(e)-152 19 y Fi(n)-106 -13 y Fe(\000)p Ff(1)p Fh(=)p Ff(2)39 19 y Fn(.)-77 106 y(The)17 b Fj(Ho)l(dges-L)l(ehmann)23 b(estimator)j Fn(is)18 b(giv)n(en)f(b)n(y)f Fi(f)8 b Fn(\()p Fi(x)1477 114 y Ff(1)1512 106 y Fi(;)13 b(:)g(:)g(:)g(;)g(x) 1726 114 y Fh(n)1768 106 y Fn(\))22 b(=)-152 193 y(med)-11 202 y Ff(1)p Fe(\024)p Fh(i Second comment: > > In 3.5. Cancellation =A0I have an issue with: > > "or when it performs a GET request without an Observe Option for a > currently observed resource, the server will remove the client from > the list of observers for this resource." > > Unless I am missing something the above logic will force the server for > every request for a resource to check whether or not the requestor is > actively observing the resource. Right. >=A0This seems highly inefficient right? It adds a small overhead when processing a GET request, but I don't think this overhead is very high. It's usually just a lookup in a hash table or in a short linked list. Do you have a specific scenario where the overhead becomes unacceptable? Klaus From hartke@tzi.org Fri Jun 15 02:10:00 2012 Return-Path: X-Original-To: core@ietfa.amsl.com Delivered-To: core@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5628721F85A2 for ; Fri, 15 Jun 2012 02:10:00 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.627 X-Spam-Level: X-Spam-Status: No, score=-5.627 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-4] 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 3Wq7JfKE1WQk for ; Fri, 15 Jun 2012 02:09:59 -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 804CC21F858A for ; Fri, 15 Jun 2012 02:09:59 -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.3/8.14.3) with ESMTP id q5F99ql1016684 for ; Fri, 15 Jun 2012 11:09:52 +0200 (CEST) Received: from mail-pb0-f44.google.com (mail-pb0-f44.google.com [209.85.160.44]) (using TLSv1 with cipher DES-CBC3-SHA (168/168 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id 103D64E3 for ; Fri, 15 Jun 2012 11:09:51 +0200 (CEST) Received: by pbcwy7 with SMTP id wy7so5053173pbc.31 for ; Fri, 15 Jun 2012 02:09:50 -0700 (PDT) MIME-Version: 1.0 Received: by 10.68.236.131 with SMTP id uu3mr17904206pbc.96.1339751390237; Fri, 15 Jun 2012 02:09:50 -0700 (PDT) Received: by 10.68.31.199 with HTTP; Fri, 15 Jun 2012 02:09:49 -0700 (PDT) In-Reply-To: References: Date: Fri, 15 Jun 2012 11:09:49 +0200 Message-ID: From: Klaus Hartke To: core@ietf.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Subject: Re: [core] Comment on draft-ietf-core-coap-09 X-BeenThere: core@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Jun 2012 09:10:00 -0000 Avi Lior wrote: > In section 5.4.2 it states > > "If the length of an option value=A0in a request is outside the defined r= ange, > that option MUST be > treated like an unrecognized option (see Section 5.4.1)." > > I am assuming that this range is what appears in table 1 in section 5.10. > > Now looking at the definition of Token in that table it states that token= is > 1-8. =A0Therefore a length of zero for token is not allowed by 5.4.2. > > Then reading 5.10.1 it states > > Thus when the token value is empty, thenToken Option SHOULD be elided for > efficiency. > > That statement must be wrong right? =A0based on the logic above you must = never > send a Token Option with length 0. Right? Conceptually, each request and each response has a token. There are 18519084246547628289 possible tokens. These tokens are encoded as a byte sequence, with a length depending on the token between 0 and 8 bytes. When the length is 0, the Token Option is elided in the message; when the length is 1 to 8, the Token Option with the token as option value is included. So both the table and the text in 5.10.1 are correct: a token can be encoded as a byte sequence of length 0, but the Token Option never contains a token of length 0. Do you have a suggestion for improving the text to make this more clear? Klaus From avi.ietf@lior.org Fri Jun 15 03:23:23 2012 Return-Path: X-Original-To: core@ietfa.amsl.com Delivered-To: core@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DB02F21F850C for ; Fri, 15 Jun 2012 03:23:23 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.599 X-Spam-Level: X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1] 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 dWvQobPMWhlJ for ; Fri, 15 Jun 2012 03:23:23 -0700 (PDT) Received: from mail-gh0-f172.google.com (mail-gh0-f172.google.com [209.85.160.172]) by ietfa.amsl.com (Postfix) with ESMTP id 3774721F84FD for ; Fri, 15 Jun 2012 03:23:17 -0700 (PDT) Received: by ghbg16 with SMTP id g16so2357365ghb.31 for ; Fri, 15 Jun 2012 03:23:16 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer :x-gm-message-state; bh=FRJFBPcQfS8KpCe1r4YmKrLLI1/90f1H8tSiTcXELmw=; b=GxzLGqSqMa2qgPpVi04VMzWZoRaMVH69qM9hg25Bjdj7C0S+JeG7J1aGagWo6NBAMZ dC7XSd9XdxUAcWBKkGvqPPumO2imgbU2KpAQL1zYldWMmG7U5fcNoWUbb9zUPDlH76m7 AwUXHv2XC6GZpxiGWI+ipCF4imcKlkZXioPhT4qpSE759S9ezimvrPipx/O7PyWeQoSU QD/8KDC9rbLibeI5WrrELOzhqHWEWAXKqAoqzXRcRP77G3gUvIpK9p0DBwhI197gj2GI vkYOnZi97rdJ0g+11GRLAvPFUXL0Ysrv68ZUe1tjbRKBQxL9dHqOIfZRPzAtFOinti5a T3bg== Received: by 10.50.169.73 with SMTP id ac9mr1130247igc.29.1339755796371; Fri, 15 Jun 2012 03:23:16 -0700 (PDT) Received: from [172.17.17.120] (CPEbcaec5c320b6-CM602ad089cf9c.cpe.net.cable.rogers.com. [99.224.173.26]) by mx.google.com with ESMTPS id if4sm885620igc.10.2012.06.15.03.23.13 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 15 Jun 2012 03:23:15 -0700 (PDT) Mime-Version: 1.0 (Apple Message framework v1278) Content-Type: text/plain; charset=iso-8859-1 From: Avi Lior In-Reply-To: Date: Fri, 15 Jun 2012 06:23:12 -0400 Content-Transfer-Encoding: quoted-printable Message-Id: References: <3860667E-BCBB-4A4C-A7C1-EC93F44A21F8@lior.org> To: Klaus Hartke X-Mailer: Apple Mail (2.1278) X-Gm-Message-State: ALoCoQnltiFaasuhII1A9xulZYui6336nQ4fTwBafBcqhqeIVzsFYMDwCGdlwiJD9PSmeig2k4hv Cc: core@ietf.org Subject: Re: [core] Comments on draft-ietf-core-observer-05 X-BeenThere: core@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Jun 2012 10:23:24 -0000 Hi Klaus, Please see below. On 2012-06-15, at 4:46 , Klaus Hartke wrote: > Avi Lior wrote: >> First comment: >> Figure 2 shows Observe to have a value of 0 (during registration) but = later >> in the document it is stated that Observe should have no value. If = that is >> true you need to correct the figure. >=20 > A 'uint' value of 0 is usually encoded with 0 bytes, so the result is > the same as having no value. >=20 > It could be clarified that the value of 0 MUST be encoded with 0 bytes > (the 'uint' type also allows other ways), and the two places in the > document should be made consistent. AL] I think it should be clarified. >=20 >> Second comment: >>=20 >> In 3.5. Cancellation I have an issue with: >>=20 >> "or when it performs a GET request without an Observe Option for a >> currently observed resource, the server will remove the client from >> the list of observers for this resource." >>=20 >> Unless I am missing something the above logic will force the server = for >> every request for a resource to check whether or not the requestor is >> actively observing the resource. >=20 > Right. >=20 >> This seems highly inefficient right? >=20 > It adds a small overhead when processing a GET request, but I don't > think this overhead is very high. It's usually just a lookup in a hash > table or in a short linked list. >=20 > Do you have a specific scenario where the overhead becomes = unacceptable? AL] I don't have a specific scenario. But nevertheless it is sloppy. = If it was the only way you could do it then perhaps, but you are = offering two ways of cancelling. Is there any harm in remove this = behaviour and sticking with the more explicit method? >=20 >=20 > Klaus > _______________________________________________ > core mailing list > core@ietf.org > https://www.ietf.org/mailman/listinfo/core From hartke@tzi.org Fri Jun 15 03:38:33 2012 Return-Path: X-Original-To: core@ietfa.amsl.com Delivered-To: core@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1794D21F85A1 for ; Fri, 15 Jun 2012 03:38:33 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.627 X-Spam-Level: X-Spam-Status: No, score=-5.627 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-4] 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 LfPxhpDcS4qY for ; Fri, 15 Jun 2012 03:38:32 -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 2F2F321F849A for ; Fri, 15 Jun 2012 03:38:32 -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.3/8.14.3) with ESMTP id q5FAcOHk010595 for ; Fri, 15 Jun 2012 12:38:24 +0200 (CEST) Received: from mail-pz0-f44.google.com (mail-pz0-f44.google.com [209.85.210.44]) (using TLSv1 with cipher DES-CBC3-SHA (168/168 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id 3857D59E for ; Fri, 15 Jun 2012 12:38:24 +0200 (CEST) Received: by dacx6 with SMTP id x6so3875365dac.31 for ; Fri, 15 Jun 2012 03:38:22 -0700 (PDT) MIME-Version: 1.0 Received: by 10.68.217.234 with SMTP id pb10mr19152328pbc.79.1339756702358; Fri, 15 Jun 2012 03:38:22 -0700 (PDT) Received: by 10.68.31.199 with HTTP; Fri, 15 Jun 2012 03:38:22 -0700 (PDT) In-Reply-To: References: <3860667E-BCBB-4A4C-A7C1-EC93F44A21F8@lior.org> Date: Fri, 15 Jun 2012 12:38:22 +0200 Message-ID: From: Klaus Hartke To: core@ietf.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Subject: Re: [core] Comments on draft-ietf-core-observer-05 X-BeenThere: core@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Jun 2012 10:38:33 -0000 Avi Lior wrote: >>> In 3.5. Cancellation =A0I have an issue with: >>> >>> "or when it performs a GET request without an Observe Option for a >>> currently observed resource, the server will remove the client from >>> the list of observers for this resource." >>> >>> Unless I am missing something the above logic will force the server for >>> every request for a resource to check whether or not the requestor is >>> actively observing the resource. >> >> Right. >> >>> =A0This seems highly inefficient right? >> >> It adds a small overhead when processing a GET request, but I don't >> think this overhead is very high. It's usually just a lookup in a hash >> table or in a short linked list. >> >> Do you have a specific scenario where the overhead becomes unacceptable? > > AL] =A0I don't have a specific scenario. But nevertheless it is sloppy. = =A0If it was the only way you could do it then perhaps, but you are offerin= g two ways of cancelling. =A0Is there any harm in remove this behaviour and= sticking with the more explicit method? What should be the behaviour when the server promised the client to notify it when the resource state changes, and the client asks for the resource state? There are two options: (a) The server tells the client the current resource state and continues to notify the client of state changes, or (b) the server tells the client the current resource state and stops notifying the client of state changes. -observe eliminates any ambiguity by specifying that a GET request with an Observe Option always causes (a), and a GET request without an Observe Option always causes (b). I wouldn't want to see a GET request without an Observe sometimes cause (a) and sometimes cause (b) depending on some server state the client cannot see. Klaus From avi.ietf@lior.org Fri Jun 15 03:48:30 2012 Return-Path: X-Original-To: core@ietfa.amsl.com Delivered-To: core@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4F66D21F854D for ; Fri, 15 Jun 2012 03:48:30 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.599 X-Spam-Level: X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1] 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 EiIKKTOcevyp for ; Fri, 15 Jun 2012 03:48:29 -0700 (PDT) Received: from mail-yx0-f172.google.com (mail-yx0-f172.google.com [209.85.213.172]) by ietfa.amsl.com (Postfix) with ESMTP id 8E9AA21F853D for ; Fri, 15 Jun 2012 03:48:29 -0700 (PDT) Received: by yenq13 with SMTP id q13so2495530yen.31 for ; Fri, 15 Jun 2012 03:48:29 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer :x-gm-message-state; bh=ANsInDtqD2RSAaL63MTpleKlFzaVd18aYvV2bVOauZg=; b=XgYmdunaEzVBgVQ93vWtWVIrLwod0LWWCSLlZl2eJ7LR/TWMJlGO7Q3unuSyWHwaMs C5lOUtKUa0iBBFV0B4s2ioc2vpi3v6194VG1mc6pmUuBHnmFoEUTCwrOqAnAb8oNgNkQ 7ayrc6feF2CTZdBFAdDmGe6CtMpvKQFqeoNTUfDWvXWgK+8SLSbXKhkZm99BtowFgmAA dwRJv1DFe529rKVswe9uUc/5j+Ojcz6kvE0HHPBhchL6mrfZeJCahWUR8kWPEayFAklO nCWzk44BjqIs3ZqAMl9OM+R9tHmqlqNbCF2fslhp9BwGmLWU/8DMmzIEfEhlqIxEXdqG aIoA== Received: by 10.50.189.135 with SMTP id gi7mr1197458igc.8.1339757308883; Fri, 15 Jun 2012 03:48:28 -0700 (PDT) Received: from [172.17.17.120] (CPEbcaec5c320b6-CM602ad089cf9c.cpe.net.cable.rogers.com. [99.224.173.26]) by mx.google.com with ESMTPS id qo3sm1615551igc.8.2012.06.15.03.48.26 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 15 Jun 2012 03:48:27 -0700 (PDT) Mime-Version: 1.0 (Apple Message framework v1278) Content-Type: text/plain; charset=windows-1252 From: Avi Lior In-Reply-To: Date: Fri, 15 Jun 2012 06:48:25 -0400 Content-Transfer-Encoding: quoted-printable Message-Id: References: To: Klaus Hartke X-Mailer: Apple Mail (2.1278) X-Gm-Message-State: ALoCoQn01mo3NbIMbrPqEBrIXA1qcBWa3AH5wZUXrxQzHxsNgjTcPUNFuHUKn32oamdChoKNpm7r Cc: core@ietf.org Subject: Re: [core] Comment on draft-ietf-core-coap-09 X-BeenThere: core@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Jun 2012 10:48:30 -0000 Hi Klaus, On 2012-06-15, at 5:09 , Klaus Hartke wrote: > Avi Lior wrote: >> In section 5.4.2 it states >>=20 >> "If the length of an option value in a request is outside the defined = range, >> that option MUST be >> treated like an unrecognized option (see Section 5.4.1)." >>=20 >> I am assuming that this range is what appears in table 1 in section = 5.10. >>=20 >> Now looking at the definition of Token in that table it states that = token is >> 1-8. Therefore a length of zero for token is not allowed by 5.4.2. >>=20 >> Then reading 5.10.1 it states >>=20 >> Thus when the token value is empty, thenToken Option SHOULD be elided = for >> efficiency. >>=20 >> That statement must be wrong right? based on the logic above you = must never >> send a Token Option with length 0. Right? >=20 > snip=85.. When the length is 0, the Token Option is elided [AL] not always. Read 10.5.1 its a SHOULD not a MUST. > in the > message; when the length is 1 to 8, the Token Option with the token as > option value is included. [AL] The text in 10.5.1 does not make it mandatory to elide the a zero = length Token Option - its a SHOULD. Therefore, the table is wrong. If = you like the table to be correct then change the SHOULD in 10.5.1 to a = MUST be elided. As long as you allow an Token Option with zero length = then that table has to have 0-8 B. Right? >=20 > So both the table and the text in 5.10.1 are correct: a token can be > encoded as a byte sequence of length 0, but the Token Option never > contains a token of length 0. [AL] I still don't think so. But I could still be missing something. >=20 > Do you have a suggestion for improving the text to make this more = clear? >=20 >=20 > Klaus > _______________________________________________ > core mailing list > core@ietf.org > https://www.ietf.org/mailman/listinfo/core From hartke@tzi.org Fri Jun 15 03:53:52 2012 Return-Path: X-Original-To: core@ietfa.amsl.com Delivered-To: core@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 825A821F85C9 for ; Fri, 15 Jun 2012 03:53:52 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.627 X-Spam-Level: X-Spam-Status: No, score=-5.627 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-4] 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 2uBOsdAudHFL for ; Fri, 15 Jun 2012 03:53:52 -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 A752321F85D1 for ; Fri, 15 Jun 2012 03:53:51 -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.3/8.14.3) with ESMTP id q5FAri5J021392 for ; Fri, 15 Jun 2012 12:53:44 +0200 (CEST) Received: from mail-pb0-f44.google.com (mail-pb0-f44.google.com [209.85.160.44]) (using TLSv1 with cipher DES-CBC3-SHA (168/168 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id BCF6F5BC for ; Fri, 15 Jun 2012 12:53:43 +0200 (CEST) Received: by pbcwy7 with SMTP id wy7so5171488pbc.31 for ; Fri, 15 Jun 2012 03:53:41 -0700 (PDT) MIME-Version: 1.0 Received: by 10.68.219.41 with SMTP id pl9mr18945035pbc.61.1339757621915; Fri, 15 Jun 2012 03:53:41 -0700 (PDT) Received: by 10.68.31.199 with HTTP; Fri, 15 Jun 2012 03:53:41 -0700 (PDT) In-Reply-To: References: Date: Fri, 15 Jun 2012 12:53:41 +0200 Message-ID: From: Klaus Hartke To: core@ietf.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Subject: Re: [core] Comment on draft-ietf-core-coap-09 X-BeenThere: core@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Jun 2012 10:53:52 -0000 Avi Lior wrote: > The text in 10.5.1 does not make it mandatory to elide the a zero length = Token Option - its a SHOULD. =A0Therefore, the table is wrong. =A0If you li= ke the table to be correct then change the SHOULD in 10.5.1 to a MUST be el= ided. =A0As long as you allow an Token Option with zero length then that ta= ble has to have 0-8 B. =A0Right? It's a "the sender MUST elide the Token Option if the token has a zero length" and "the recipient MUST be prepared to receive a Token Option with a zero length token". Text and table should be updated to say that. Klaus From hartke@tzi.org Fri Jun 15 03:58:03 2012 Return-Path: X-Original-To: core@ietfa.amsl.com Delivered-To: core@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EEC6F21F85C9 for ; Fri, 15 Jun 2012 03:58:03 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.627 X-Spam-Level: X-Spam-Status: No, score=-5.627 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-4] 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 ZCgDuwDma5n4 for ; Fri, 15 Jun 2012 03:58:03 -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 2659421F85C5 for ; Fri, 15 Jun 2012 03:58:02 -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.3/8.14.3) with ESMTP id q5FAvtoa022954 for ; Fri, 15 Jun 2012 12:57:55 +0200 (CEST) Received: from mail-pz0-f44.google.com (mail-pz0-f44.google.com [209.85.210.44]) (using TLSv1 with cipher DES-CBC3-SHA (168/168 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id 563375C2 for ; Fri, 15 Jun 2012 12:57:55 +0200 (CEST) Received: by dacx6 with SMTP id x6so3896342dac.31 for ; Fri, 15 Jun 2012 03:57:53 -0700 (PDT) MIME-Version: 1.0 Received: by 10.68.236.131 with SMTP id uu3mr18926056pbc.96.1339757873509; Fri, 15 Jun 2012 03:57:53 -0700 (PDT) Received: by 10.68.31.199 with HTTP; Fri, 15 Jun 2012 03:57:53 -0700 (PDT) In-Reply-To: References: Date: Fri, 15 Jun 2012 12:57:53 +0200 Message-ID: From: Klaus Hartke To: core@ietf.org Content-Type: text/plain; charset=ISO-8859-1 Subject: Re: [core] Comment on draft-ietf-core-coap-09 X-BeenThere: core@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Jun 2012 10:58:04 -0000 Klaus Hartke wrote: > "the sender MUST elide the Token Option if the token has a zero > length" Actually it's more like "the sender MAY elide the Token Option if the token has a zero length; as a matter of implementation quality, an implementation is generally expected to do this" and "the recipient MUST be prepared to receive a Token Option with a zero length token". I don't have a strong opinion on whether the first requirement should be a MAY with implementation note or a MUST (or a SHOULD). Klaus From avi.ietf@lior.org Fri Jun 15 04:23:15 2012 Return-Path: X-Original-To: core@ietfa.amsl.com Delivered-To: core@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6266421F8618 for ; Fri, 15 Jun 2012 04:23:15 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.599 X-Spam-Level: X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1] 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 ML0ryEkJHERD for ; Fri, 15 Jun 2012 04:23:14 -0700 (PDT) Received: from mail-gh0-f172.google.com (mail-gh0-f172.google.com [209.85.160.172]) by ietfa.amsl.com (Postfix) with ESMTP id C521121F85C3 for ; Fri, 15 Jun 2012 04:23:14 -0700 (PDT) Received: by ghbg16 with SMTP id g16so2397529ghb.31 for ; Fri, 15 Jun 2012 04:23:14 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer :x-gm-message-state; bh=G6isyU8gyh0vxhMP30s/g01ijggs1EStbpY1vp6FSPs=; b=mQN57kvv2VunbVyea3SY3RKdI+9YdTHcNHdZk59kyTt8UJrCABIDHtX0iq33+48J2+ d2NT6RwlQprntxQEbmAJyVogmsyMerF+iCQ1Zw5qlH0A3cz+RwNNhVBoPul0T7mi65cw pgHL6OKAoTr2TAMh5ri1bC+Xc7IU8qYbcRMewn+DcjrcFeuABnTvF1QvIj7f+MNpAsgP LzkiMu47FvPOXywnl1StcsQZVjeuy8FzITz1z9PgYNxrtBmcrWYA7FUImxFkAMKumRK0 J0NuChsXXzQvSlAMrXwCRWqyEm0ZelvbF5OWJgiDmk0wnS/IwYEpcj/UdgPSbzv3AmfK Xr8A== Received: by 10.50.169.73 with SMTP id ac9mr1311715igc.29.1339759394105; Fri, 15 Jun 2012 04:23:14 -0700 (PDT) Received: from [172.17.17.120] (CPEbcaec5c320b6-CM602ad089cf9c.cpe.net.cable.rogers.com. [99.224.173.26]) by mx.google.com with ESMTPS id bp8sm1708764igb.12.2012.06.15.04.23.11 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 15 Jun 2012 04:23:13 -0700 (PDT) Mime-Version: 1.0 (Apple Message framework v1278) Content-Type: text/plain; charset=iso-8859-1 From: Avi Lior In-Reply-To: Date: Fri, 15 Jun 2012 07:23:11 -0400 Content-Transfer-Encoding: quoted-printable Message-Id: <9D7B7D35-9C03-41E2-99DA-307493B52047@lior.org> References: To: Klaus Hartke X-Mailer: Apple Mail (2.1278) X-Gm-Message-State: ALoCoQkZ5WKBPEVbKTqRXvEPKspWX9YjwsxSe0cJ24tdhTqBIgaadhgeigAZyBse+9+slnC979P0 Cc: core@ietf.org Subject: Re: [core] Comment on draft-ietf-core-coap-09 X-BeenThere: core@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Jun 2012 11:23:15 -0000 On 2012-06-15, at 6:53 , Klaus Hartke wrote: > Avi Lior wrote: >> The text in 10.5.1 does not make it mandatory to elide the a zero = length Token Option - its a SHOULD. Therefore, the table is wrong. If = you like the table to be correct then change the SHOULD in 10.5.1 to a = MUST be elided. As long as you allow an Token Option with zero length = then that table has to have 0-8 B. Right? >=20 > It's a "the sender MUST elide the Token Option if the token has a zero > length" and "the recipient MUST be prepared to receive a Token Option > with a zero length token". Text and table should be updated to say > that. Okay. Amongst other wording you may add, does that mean you are going = to change the range in the table from 1-8 to 0-8? >=20 >=20 > Klaus > _______________________________________________ > core mailing list > core@ietf.org > https://www.ietf.org/mailman/listinfo/core From wehner@htw-dresden.de Fri Jun 15 04:40:43 2012 Return-Path: X-Original-To: core@ietfa.amsl.com Delivered-To: core@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F278521F8615 for ; Fri, 15 Jun 2012 04:40:42 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.249 X-Spam-Level: X-Spam-Status: No, score=-2.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35] 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 8dnF82hRtNZD for ; Fri, 15 Jun 2012 04:40:41 -0700 (PDT) Received: from rmr1.rz.htw-dresden.de (rmr1.rz.htw-dresden.de [141.56.16.131]) by ietfa.amsl.com (Postfix) with ESMTP id 6BFAD21F85C5 for ; Fri, 15 Jun 2012 04:40:40 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by rmr1.rz.htw-dresden.de (Postfix) with ESMTP id 5F52C102D3; Fri, 15 Jun 2012 13:40:39 +0200 (CEST) X-HTW-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on rmr1.rz.htw-dresden.de X-HTW-Virus-Scanned: Debian amavisd-new at rmr1.rz.htw-dresden.de Received: from rmr1.rz.htw-dresden.de ([127.0.0.1]) by localhost (rmr1.rz.htw-dresden.de [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BY06hpEhJgz8; Fri, 15 Jun 2012 13:40:32 +0200 (CEST) Received: from rlux45.rz.htw-dresden.de (rlux45.rz.htw-dresden.de [141.56.16.45]) by rmr1.rz.htw-dresden.de (Postfix) with ESMTP id 6C2B1102D0; Fri, 15 Jun 2012 13:40:32 +0200 (CEST) Received: from [141.56.111.34] (etpc34.et.htw-dresden.de [141.56.111.34]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by rlux45.rz.htw-dresden.de (Postfix) with ESMTPSA id 62E94128576; Fri, 15 Jun 2012 13:40:32 +0200 (CEST) Message-ID: <4FDB1F1C.70307@htw-dresden.de> Date: Fri, 15 Jun 2012 13:40:12 +0200 From: Markus Wehner User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:13.0) Gecko/20120604 Thunderbird/13.0 MIME-Version: 1.0 To: Rene Struik , "Keoh, Sye Loong" References: <20120326215140.20793.73440.idtracker@ietfa.amsl.com> <4FD1BDC7.5060203@htw-dresden.de> <4FD61CEC.6010307@gmail.com> In-Reply-To: <4FD61CEC.6010307@gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Cc: core , "Kumar, Sandeep" Subject: Re: [core] New Version Notification for draft-garcia-core-security-04.txt X-BeenThere: core@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Jun 2012 11:40:43 -0000 Dear Sye Loong, Rene, I agree to your comments and also do not see a simple solution. The scenario Rene described refers to what I mean with context awareness = of the nodes but this is not only a problem of aggregation but of reliabi= lity/trustworthiness of sensed data in general. Of course using informati= on from other nodes an aggregator could point on faulty measurements as d= escribed in the paper Rene sent. In case a single node or the aggregator = is aware of its context (environmental model, location, ...) a priori it = may be possible that this node is able to evaluate the data on its own ba= sed on these reliability models and inform the network of possible securi= ty attacks. Yes, trustworthiness (of devices/services/users) is difficult to quantify= , especially in multi-owner networks. Normally it is a binary service dep= endent decision based on authentication and authorization. A simple use case covering mutliple domains is a household scenario inclu= ding Smart Metering. Imagine to have several devices in the household whi= ch are connected to the IoT world. Not all devices need to be owned by th= e end user himself, i.e. a thermostat device offered by the heating suppl= ier for monitoring and controling purposes, accessed by the end user and = the supplier. There are several interested parties which may have access = to the same devices for same or different purposes or integrate their own= devices into the network. Services/Devices of the energy/heating/water s= uppliers (Smart Metering), communication provider, the user itself, other= commercial services from third parties have to be trusted/authorized to = obtain or share data. For example, the end user wants the air conditioner= and thermostat communicating with each other, so they may be in the same= PAN (as the rest of the IoT devices in one household), but the heating s= upplier is allowed to use monitored data=20 of the thermostat only or maybe aggregated data from all thermostats of y= our household. In his domain, the supplier should see aggregates from dif= ferent households (or repeatedly aggregated data according to his needs, = i.e. of a city) only, that the end user is not allowed to see on the othe= r side. I do not know if this is a meaningful enough example to be considered but= what I want to say is that this kind of multi-owner security is needed a= lso in not too specialized use cases. Best regards, Markus --- Original Nachricht --- Absender: Rene Struik Datum: 11.06.2012 18:29 > Dear Sye Loong, Markus: > > Secure aggregation is indeed a difficult problem. Even if one has a > secure "end to end" aggregation mechanism, this would usually relate to= > the communication subsystems of devices and not necessarily to the > sensing applications themselves (imagine lighting a match next to a > temperature sensor, which is connected to a "perfectly secure" > end-to-end security system). In those cases, one has to do some more > analysis on the devices, e.g., regarding consistency of data over > time/location, etc. End-to-end security usually only deals with > communication security and not with security of the inputs (or outputs)= > of this process. When adequately addressed, it does reduce the size of > remaining security/robustness/reliability issues. > > I attached a paper by David Wagner (2004) that may be of interest here > (paper in Postscript format). > > Best regards, Rene > > > > On 11/06/2012 12:12 PM, Keoh, Sye Loong wrote: >> Dear Markus, >> >> Thank you very much for your comments. >> >> Yes, you are absolutely right, that aggregation of data also breaks E2= E security. Unfortunately, this is a very difficult problem in the area, = and we have not seen any good solution that can address E2E security issu= es effectively. As you said, the use of homomorphic encryption scheme req= uires complex computation, and we think it may not be feasible on constra= ined devices, although it's worth mentioning and considering. >> >> I have the impression that trustworthiness is something very difficult= to quantify, there are people who are skeptical about interaction betwe= en devices (running different applications) from multiple domains, and ho= w trust can be established between them when they interact is typically u= nknown or unspecified. If you have some use cases that you think we shoul= d consider, we would be glad to hear them :) >> >> Thanks and kind regards, >> Sye Loong >> >> -----Original Message----- >> From: Markus Wehner [mailto:wehner@htw-dresden.de] >> Sent: vrijdag 8 juni 2012 10:55 >> To: Keoh, Sye Loong >> Cc:core@ietf.org >> Subject: Re: [core] New Version Notification for draft-garcia-core-sec= urity-04.txt >> >> Dear Sye, >> >> I like this document, it is written well and very clear. >> Some comments from my side regarding the draft: >> >> 1. Difficulties with E2E security not only occur for protocol translat= ion but also for aggregation (or in-network processing in general) of dat= a. >> Especially in industrial scenarios, aggregation of huge amounts of dat= a may be performed at dedicated intermediate aggregating devices and sent= to the application afterwards for efficiency reasons. Also in a home env= ironment it is a privacy reason that for example not any single device ca= n be monitored by a certain user (end user, power supplier) but aggregate= d information is needed. >> Here, besides the solutions you mentioned for protocol translation, al= so homomorphic encryption may play a role which allows performing aggrega= tion on encrypted payload on the cost of computational complexity. >> >> 2. Multi owner (resp. multi domain) use cases also raise security issu= es in the IoT world, i.e. data separation, resources sharing and in this = scope trustworthiness, fairness, QoS restrictions... . Co-located network= s that do not belong to the same domain which work in a cooperative way, = i.e. for routing/energy efficiency, are part of that. Also, if a mobile n= ode moves between different networks, besides reauthentication and so on,= the trustworthiness is an important thing to consider here. >> >> 3. Especially in IoT world, nodes often know about their context which= could enhance security. For example a network which knows locations of i= ts nodes and is able to measure them could improve against physical repla= cement. The other way, only nodes within a certain area, i.e. an office r= oom, could be allowed to have access to the rest of the network (automati= cally). Unfortunately this raises new security issues. >> >> Best regards, >> Markus >> >> >> ----- Original Message ----- >> From: Keoh, Sye Loong >> Sent: Mon, 26 Mar 2012 22:08:38 +0000 >> To:core@ietf.org >> Cc: >> Subject: [core] New Version Notification for draft-garcia-core-securit= y-04.txt >> --- Original Nachricht --- >> Absender: Keoh, Sye Loong >> Datum: 27.03.2012 00:08 >>> Dear all, >>> >>> In this new version, we have updated the conclusions section to refle= ct the status of current security technologies and the missing bits with = regards to the security requirements we identified in the document. >>> >>> Since the WG advised that we should continue working on this draft i= n Taipei, we are continuously improving the draft so that it serves its p= urpose to provide an overview of the security requirements for IoT. There= fore, we would greatly appreciate feedback and comments from WG members o= n this document. >>> >>> Many thanks >>> Sye Loong >>> >>> -----Original Message----- >>> From:internet-drafts@ietf.org [mailto:internet-drafts@ietf.org] >>> Sent: maandag 26 maart 2012 23:52 >>> To: Keoh, Sye Loong >>> Cc:rstruik.ext@gmail.com; Kumar,Sandeep;rene.hummen@cs.rwth-aachen.de= ; Garcia Morchon, Oscar >>> Subject: New Version Notification for draft-garcia-core-security-04.t= xt >>> >>> A new version of I-D, draft-garcia-core-security-04.txt has been succ= essfully submitted by Sye Loong Keoh and posted to the IETF repository. >>> >>> Filename: draft-garcia-core-security >>> Revision: 04 >>> Title: Security Considerations in the IP-based Internet of = Things >>> Creation date: 2012-03-26 >>> WG ID: Individual Submission >>> Number of pages: 45 >>> >>> Abstract: >>> A direct interpretation of the Internet of Things concept refers= to >>> the usage of standard Internet protocols to allow for human-to-t= hing >>> or thing-to-thing communication. Although the security needs ar= e >>> well-recognized, it is still not fully clear how existing IP-bas= ed >>> security protocols can be applied to this new setting. This >>> Internet-Draft first provides an overview of security architectu= re, >>> its deployment model and general security needs in the context o= f the >>> lifecycle of a thing. Then, it presents challenges and requirem= ents >>> for the successful roll-out of new applications and usage of sta= ndard >>> IP-based security protocols when applied to get a functional Int= ernet >>> of Things. >>> >>> >>> >>> >>> The IETF Secretariat >>> >>> ________________________________ >>> The information contained in this message may be confidential and leg= ally protected under applicable law. The message is intended solely for t= he addressee(s). If you are not the intended recipient, you are hereby no= tified that any use, forwarding, dissemination, or reproduction of this m= essage is strictly prohibited and may be unlawful. If you are not the int= ended recipient, please contact the sender by return e-mail and destroy a= ll copies of the original message. >>> _______________________________________________ >>> core mailing list >>> core@ietf.org >>> https://www.ietf.org/mailman/listinfo/core >>> --=20 --------------------------------------- Dipl.-Ing. Markus Wehner on behalf of TWISNet project University of Applied Sciences Department of Electrical Engineering Friedrich-List-Platz 1 D-01069 Dresden Germany http://www.htw-dresden.de phone : +49 351 462 2465 email :wehner@htw-dresden.de --------------------------------------- From hartke@tzi.org Fri Jun 15 10:14:51 2012 Return-Path: X-Original-To: core@ietfa.amsl.com Delivered-To: core@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DCF3E21F8645 for ; Fri, 15 Jun 2012 10:14:51 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.627 X-Spam-Level: X-Spam-Status: No, score=-5.627 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-4] 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 jPcx-pLjhN73 for ; Fri, 15 Jun 2012 10:14:51 -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 ECD5421F85C4 for ; Fri, 15 Jun 2012 10:14:50 -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.3/8.14.3) with ESMTP id q5FHEhiH007217 for ; Fri, 15 Jun 2012 19:14:43 +0200 (CEST) Received: from mail-pz0-f44.google.com (mail-pz0-f44.google.com [209.85.210.44]) (using TLSv1 with cipher DES-CBC3-SHA (168/168 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id 2254D781 for ; Fri, 15 Jun 2012 19:14:42 +0200 (CEST) Received: by dacx6 with SMTP id x6so4313716dac.31 for ; Fri, 15 Jun 2012 10:14:41 -0700 (PDT) MIME-Version: 1.0 Received: by 10.68.219.41 with SMTP id pl9mr22192313pbc.61.1339780481068; Fri, 15 Jun 2012 10:14:41 -0700 (PDT) Received: by 10.68.31.199 with HTTP; Fri, 15 Jun 2012 10:14:41 -0700 (PDT) In-Reply-To: <9D7B7D35-9C03-41E2-99DA-307493B52047@lior.org> References: <9D7B7D35-9C03-41E2-99DA-307493B52047@lior.org> Date: Fri, 15 Jun 2012 19:14:41 +0200 Message-ID: From: Klaus Hartke To: core@ietf.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Subject: Re: [core] Comment on draft-ietf-core-coap-09 X-BeenThere: core@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Jun 2012 17:14:52 -0000 Avi Lior wrote: >> It's a "the sender MUST elide the Token Option if the token has a zero >> length" and "the recipient MUST be prepared to receive a Token Option >> with a zero length token". Text and table should be updated to say >> that. > > Okay. =A0Amongst other wording you may add, does that mean you are going = to change the range in the table from 1-8 to 0-8? Yes, it looks like we need to change this so a recipient does not treat a Token Option with a zero length token as unrecognised option. This should also end the confusion between the length of a token and the length of the Token Option value. Klaus From cabo@tzi.org Fri Jun 15 11:13:25 2012 Return-Path: X-Original-To: core@ietfa.amsl.com Delivered-To: core@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D221621F8593 for ; Fri, 15 Jun 2012 11:13:25 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -106.699 X-Spam-Level: X-Spam-Status: No, score=-106.699 tagged_above=-999 required=5 tests=[AWL=-0.450, 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 QeBnKjYjxPk0 for ; Fri, 15 Jun 2012 11:13:25 -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 F096621F85DF for ; Fri, 15 Jun 2012 11:13:24 -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.3/8.14.3) with ESMTP id q5FIDHN0029344 for ; Fri, 15 Jun 2012 20:13:17 +0200 (CEST) Received: from [192.168.217.105] (p54894D16.dip.t-dialin.net [84.137.77.22]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id 5DFF87A4; Fri, 15 Jun 2012 20:13:17 +0200 (CEST) Mime-Version: 1.0 (Apple Message framework v1278) Content-Type: text/plain; charset=iso-8859-1 From: Carsten Bormann In-Reply-To: Date: Fri, 15 Jun 2012 20:13:17 +0200 Content-Transfer-Encoding: quoted-printable Message-Id: References: <9D7B7D35-9C03-41E2-99DA-307493B52047@lior.org> To: Klaus Hartke X-Mailer: Apple Mail (2.1278) Cc: core@ietf.org Subject: Re: [core] Comment on draft-ietf-core-coap-09 X-BeenThere: core@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Jun 2012 18:13:26 -0000 On Jun 15, 2012, at 19:14, Klaus Hartke wrote: > Yes, it looks like we need to change this so a recipient does not > treat a Token Option with a zero length token as unrecognised option. I think that's the wrong direction to resolve this. The right way is to = make sure that senders that want to send a 0 as a Token never send an = option at all. Gr=FC=DFe, Carsten From avi.ietf@lior.org Fri Jun 15 16:03:22 2012 Return-Path: X-Original-To: core@ietfa.amsl.com Delivered-To: core@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 50ECD11E80FD for ; Fri, 15 Jun 2012 16:03:22 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.901 X-Spam-Level: X-Spam-Status: No, score=-2.901 tagged_above=-999 required=5 tests=[AWL=-0.698, BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396, RCVD_IN_DNSWL_LOW=-1] 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 G+gtqpERzBFB for ; Fri, 15 Jun 2012 16:03:21 -0700 (PDT) Received: from mail-gh0-f172.google.com (mail-gh0-f172.google.com [209.85.160.172]) by ietfa.amsl.com (Postfix) with ESMTP id C92E511E80CE for ; Fri, 15 Jun 2012 16:03:21 -0700 (PDT) Received: by ghbg16 with SMTP id g16so3044955ghb.31 for ; Fri, 15 Jun 2012 16:03:21 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=references:in-reply-to:mime-version:content-transfer-encoding :content-type:message-id:cc:x-mailer:from:subject:date:to :x-gm-message-state; bh=ds1U4OyIFE6j3w7wwvzfj4loLGbqqTigjqqa0qCNtZY=; b=Td54jOx0C7O1HrFT/N0SJoYqxngE+LR8agNUaInwGhRam2YaitBYk96R58R/R2ABMk LKc2DdNDpFsh281Xi20mlt+X+olF1IPsp33nWErDH1DkXtTLz6bDrYi1sh1NMkL/utwl 846VMwBo9mgLEtTXRBgAZqicPwjiylZXJgF1B5eeYOa4WTQQ013L15r1mda6Hhk+q/ME jTbQEH5mTyNeFaWDw9+8oCKlnzGeS28/C0A/TIkeZDClqinU7Ejob+YYPD/ex2j3dLJl QxHBoVeciSUHNBULHXDGFw10Yh/Q5FS8nShGGnDN7uL5Wj5RYXvw5nARCNTcAww1PWxr IzeQ== Received: by 10.42.148.196 with SMTP id s4mr768096icv.19.1339801400945; Fri, 15 Jun 2012 16:03:20 -0700 (PDT) Received: from [172.17.17.163] (CPEbcaec5c320b6-CM602ad089cf9c.cpe.net.cable.rogers.com. [99.224.173.26]) by mx.google.com with ESMTPS id ai6sm3998688igc.0.2012.06.15.16.03.17 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 15 Jun 2012 16:03:19 -0700 (PDT) References: <9D7B7D35-9C03-41E2-99DA-307493B52047@lior.org> In-Reply-To: Mime-Version: 1.0 (1.0) Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 Message-Id: X-Mailer: iPad Mail (9B206) From: Avi Lior Date: Fri, 15 Jun 2012 19:03:16 -0400 To: Carsten Bormann X-Gm-Message-State: ALoCoQnzAAf3lLUFMLP0yFqTlkJha6GB0QX0DRFnXOVFlsxUuPEhroKQ2FMgzn1/u1r3YA4qB3QP Cc: "core@ietf.org" , Klaus Hartke Subject: Re: [core] Comment on draft-ietf-core-coap-09 X-BeenThere: core@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Jun 2012 23:03:22 -0000 Hi, At the moment I don't have an opinion on how to solve it. I was pointing ou= t that it is busted. =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Avi Lior H: +1 613.831.9031 M: +1 613.355.7112 On 2012-06-15, at 2:13 PM, Carsten Bormann wrote: > On Jun 15, 2012, at 19:14, Klaus Hartke wrote: >=20 >> Yes, it looks like we need to change this so a recipient does not >> treat a Token Option with a zero length token as unrecognised option. >=20 > I think that's the wrong direction to resolve this. The right way is to m= ake sure that senders that want to send a 0 as a Token never send an option a= t all. >=20 > Gr=C3=BC=C3=9Fe, Carsten >=20 > _______________________________________________ > core mailing list > core@ietf.org > https://www.ietf.org/mailman/listinfo/core From lishitao@huawei.com Sun Jun 17 18:44:39 2012 Return-Path: X-Original-To: core@ietfa.amsl.com Delivered-To: core@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 737D321F857F for ; Sun, 17 Jun 2012 18:44:39 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 2.072 X-Spam-Level: ** X-Spam-Status: No, score=2.072 tagged_above=-999 required=5 tests=[AWL=-2.205, BAYES_05=-1.11, CHARSET_FARAWAY_HEADER=3.2, CN_BODY_35=0.339, MIME_8BIT_HEADER=0.3, MIME_BASE64_TEXT=1.753, MIME_CHARSET_FARAWAY=2.45, RCVD_IN_DNSWL_MED=-4, SARE_SUB_ENC_GB2312=1.345] 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 36skjirCPmXw for ; Sun, 17 Jun 2012 18:44:39 -0700 (PDT) Received: from dfwrgout.huawei.com (dfwrgout.huawei.com [206.16.17.72]) by ietfa.amsl.com (Postfix) with ESMTP id BB12121F8567 for ; Sun, 17 Jun 2012 18:44:38 -0700 (PDT) Received: from 172.18.9.243 (EHLO dfweml202-edg.china.huawei.com) ([172.18.9.243]) by dfwrg01-dlp.huawei.com (MOS 4.2.3-GA FastPath) with ESMTP id AHH01443; Sun, 17 Jun 2012 21:44:38 -0400 (EDT) Received: from DFWEML403-HUB.china.huawei.com (10.193.5.151) by dfweml202-edg.china.huawei.com (172.18.9.108) with Microsoft SMTP Server (TLS) id 14.1.323.3; Sun, 17 Jun 2012 18:43:53 -0700 Received: from SZXEML435-HUB.china.huawei.com (10.72.61.63) by dfweml403-hub.china.huawei.com (10.193.5.151) with Microsoft SMTP Server (TLS) id 14.1.323.3; Sun, 17 Jun 2012 18:43:53 -0700 Received: from SZXEML534-MBX.china.huawei.com ([169.254.2.36]) by szxeml435-hub.china.huawei.com ([::1]) with mapi id 14.01.0323.003; Mon, 18 Jun 2012 09:43:48 +0800 From: Lishitao To: Avi Lior Thread-Topic: [core] Comments on draft-ietf-core-observer-05 Thread-Index: AQHNSqKioSbutw4cdEidhrGP9lspQpb6i2EAgAAa+QCABKlMQA== Date: Mon, 18 Jun 2012 01:43:47 +0000 Message-ID: References: <3860667E-BCBB-4A4C-A7C1-EC93F44A21F8@lior.org> In-Reply-To: Accept-Language: zh-CN, en-US Content-Language: zh-CN X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.138.73.39] Content-Type: text/plain; charset="gb2312" Content-Transfer-Encoding: base64 MIME-Version: 1.0 X-CFilter-Loop: Reflected Cc: "core@ietf.org" Subject: [core] =?gb2312?b?tPC4tDogIENvbW1lbnRzIG9uIGRyYWZ0LWlldGYtY29y?= =?gb2312?b?ZS1vYnNlcnZlci0wNQ==?= X-BeenThere: core@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Jun 2012 01:44:39 -0000 aGkgIEF2aQ0KDQpJZiB5b3Ugc2VlIG15IGxhdGVzdCBkcmFmdCBmb3IgZHJhZnQtbGktY29yZS1j b25kaXRpb25hbC1vYnNlcnZlLTAyLCB0aGUgdXJsIGlzIGh0dHA6Ly9kYXRhdHJhY2tlci5pZXRm Lm9yZy9kb2MvZHJhZnQtbGktY29yZS1jb25kaXRpb25hbC1vYnNlcnZlLw0KaW4gdGhpcyBkcmFm dCBpdCBkZWZpbmVkIGFuIGV4cGxpY2l0IG1ldGhvZCBmb3IgY2FuY2VsbGF0aW9uLiBBY3R1YWxs eSBpdCBoYXMgdHdvIGFsdGVybmF0aXZlcyB0aGF0IGRlZmluZWQgaW4gdGhpcyBkcmFmdC4gT25l IHdheSBpcyB0byB1c2UgY29uZGl0aW9uIHR5cGUgICJDYW5jZWxsYXRpb24iIHRvIGNhbmNlbCBh biBleGlzdGluZyBvYnNlcnZlIHJlbGF0aW9uc2hpcCB0aGF0IGlzIGluIDYuMS4gDQphbm90aGVy IHdheSBpcyBkZWZpbmVkIGluIGFubmV4IEEuMSwgYnkgdXNpbmcgY2FuY2VsbGF0aW9uIGZsYWcg dGhhdCBkZWZpbmVkIGluIENvbmRpdGlvbiBvcHRpb24uIA0KIEhvcGUgdGhhdCBmaXQgeW91ciBy ZXF1aXJlbWVudHMuDQoNClJlZ2FyZHMNCnNoaXRhbw0KDQotLS0tLdPKvP7Urbz+LS0tLS0NCrei vP7IyzogY29yZS1ib3VuY2VzQGlldGYub3JnIFttYWlsdG86Y29yZS1ib3VuY2VzQGlldGYub3Jn XSC0+rHtIEF2aSBMaW9yDQq3osvNyrG85DogMjAxMsTqNtTCMTXI1SAxODoyMw0KytW8/sjLOiBL bGF1cyBIYXJ0a2UNCrOty806IGNvcmVAaWV0Zi5vcmcNCtb3zOI6IFJlOiBbY29yZV0gQ29tbWVu dHMgb24gZHJhZnQtaWV0Zi1jb3JlLW9ic2VydmVyLTA1DQoNCkhpIEtsYXVzLA0KDQpQbGVhc2Ug c2VlIGJlbG93Lg0KDQpPbiAyMDEyLTA2LTE1LCBhdCA0OjQ2ICwgS2xhdXMgSGFydGtlIHdyb3Rl Og0KDQo+IEF2aSBMaW9yIHdyb3RlOg0KPj4gRmlyc3QgY29tbWVudDoNCj4+IEZpZ3VyZSAyIHNo b3dzIE9ic2VydmUgdG8gaGF2ZSBhIHZhbHVlIG9mIDAgKGR1cmluZyByZWdpc3RyYXRpb24pIGJ1 dCBsYXRlcg0KPj4gaW4gdGhlIGRvY3VtZW50IGl0IGlzIHN0YXRlZCB0aGF0IE9ic2VydmUgc2hv dWxkIGhhdmUgbm8gdmFsdWUuIElmIHRoYXQgaXMNCj4+IHRydWUgeW91IG5lZWQgdG8gY29ycmVj dCB0aGUgZmlndXJlLg0KPiANCj4gQSAndWludCcgdmFsdWUgb2YgMCBpcyB1c3VhbGx5IGVuY29k ZWQgd2l0aCAwIGJ5dGVzLCBzbyB0aGUgcmVzdWx0IGlzDQo+IHRoZSBzYW1lIGFzIGhhdmluZyBu byB2YWx1ZS4NCj4gDQo+IEl0IGNvdWxkIGJlIGNsYXJpZmllZCB0aGF0IHRoZSB2YWx1ZSBvZiAw IE1VU1QgYmUgZW5jb2RlZCB3aXRoIDAgYnl0ZXMNCj4gKHRoZSAndWludCcgdHlwZSBhbHNvIGFs bG93cyBvdGhlciB3YXlzKSwgYW5kIHRoZSB0d28gcGxhY2VzIGluIHRoZQ0KPiBkb2N1bWVudCBz aG91bGQgYmUgbWFkZSBjb25zaXN0ZW50Lg0KDQpBTF0gIEkgdGhpbmsgaXQgc2hvdWxkIGJlIGNs YXJpZmllZC4NCj4gDQo+PiBTZWNvbmQgY29tbWVudDoNCj4+IA0KPj4gSW4gMy41LiBDYW5jZWxs YXRpb24gIEkgaGF2ZSBhbiBpc3N1ZSB3aXRoOg0KPj4gDQo+PiAib3Igd2hlbiBpdCBwZXJmb3Jt cyBhIEdFVCByZXF1ZXN0IHdpdGhvdXQgYW4gT2JzZXJ2ZSBPcHRpb24gZm9yIGENCj4+IGN1cnJl bnRseSBvYnNlcnZlZCByZXNvdXJjZSwgdGhlIHNlcnZlciB3aWxsIHJlbW92ZSB0aGUgY2xpZW50 IGZyb20NCj4+IHRoZSBsaXN0IG9mIG9ic2VydmVycyBmb3IgdGhpcyByZXNvdXJjZS4iDQo+PiAN Cj4+IFVubGVzcyBJIGFtIG1pc3Npbmcgc29tZXRoaW5nIHRoZSBhYm92ZSBsb2dpYyB3aWxsIGZv cmNlIHRoZSBzZXJ2ZXIgZm9yDQo+PiBldmVyeSByZXF1ZXN0IGZvciBhIHJlc291cmNlIHRvIGNo ZWNrIHdoZXRoZXIgb3Igbm90IHRoZSByZXF1ZXN0b3IgaXMNCj4+IGFjdGl2ZWx5IG9ic2Vydmlu ZyB0aGUgcmVzb3VyY2UuDQo+IA0KPiBSaWdodC4NCj4gDQo+PiAgVGhpcyBzZWVtcyBoaWdobHkg aW5lZmZpY2llbnQgcmlnaHQ/DQo+IA0KPiBJdCBhZGRzIGEgc21hbGwgb3ZlcmhlYWQgd2hlbiBw cm9jZXNzaW5nIGEgR0VUIHJlcXVlc3QsIGJ1dCBJIGRvbid0DQo+IHRoaW5rIHRoaXMgb3Zlcmhl YWQgaXMgdmVyeSBoaWdoLiBJdCdzIHVzdWFsbHkganVzdCBhIGxvb2t1cCBpbiBhIGhhc2gNCj4g dGFibGUgb3IgaW4gYSBzaG9ydCBsaW5rZWQgbGlzdC4NCj4gDQo+IERvIHlvdSBoYXZlIGEgc3Bl Y2lmaWMgc2NlbmFyaW8gd2hlcmUgdGhlIG92ZXJoZWFkIGJlY29tZXMgdW5hY2NlcHRhYmxlPw0K DQpBTF0gIEkgZG9uJ3QgaGF2ZSBhIHNwZWNpZmljIHNjZW5hcmlvLiBCdXQgbmV2ZXJ0aGVsZXNz IGl0IGlzIHNsb3BweS4gIElmIGl0IHdhcyB0aGUgb25seSB3YXkgeW91IGNvdWxkIGRvIGl0IHRo ZW4gcGVyaGFwcywgYnV0IHlvdSBhcmUgb2ZmZXJpbmcgdHdvIHdheXMgb2YgY2FuY2VsbGluZy4g IElzIHRoZXJlIGFueSBoYXJtIGluIHJlbW92ZSB0aGlzIGJlaGF2aW91ciBhbmQgc3RpY2tpbmcg d2l0aCB0aGUgbW9yZSBleHBsaWNpdCBtZXRob2Q/DQoNCg0KPiANCj4gDQo+IEtsYXVzDQo+IF9f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQo+IGNvcmUgbWFp bGluZyBsaXN0DQo+IGNvcmVAaWV0Zi5vcmcNCj4gaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1h bi9saXN0aW5mby9jb3JlDQoNCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fDQpjb3JlIG1haWxpbmcgbGlzdA0KY29yZUBpZXRmLm9yZw0KaHR0cHM6Ly93d3cu aWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9jb3JlDQo= From trac+core@trac.tools.ietf.org Mon Jun 18 03:44:51 2012 Return-Path: X-Original-To: core@ietfa.amsl.com Delivered-To: core@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8FE2C21F8564 for ; Mon, 18 Jun 2012 03:44:51 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -101.755 X-Spam-Level: X-Spam-Status: No, score=-101.755 tagged_above=-999 required=5 tests=[AWL=0.844, 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 G-v-6dArC4fL for ; Mon, 18 Jun 2012 03:44:51 -0700 (PDT) Received: from grenache.tools.ietf.org (grenache.tools.ietf.org [77.72.230.30]) by ietfa.amsl.com (Postfix) with ESMTP id E572821F8552 for ; Mon, 18 Jun 2012 03:44:50 -0700 (PDT) Received: from localhost ([127.0.0.1]:59749 helo=grenache.tools.ietf.org ident=www-data) by grenache.tools.ietf.org with esmtp (Exim 4.77) (envelope-from ) id 1SgZRe-0001JA-8u; Mon, 18 Jun 2012 12:44:30 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit From: "core issue tracker" X-Trac-Version: 0.12.2 Precedence: bulk Auto-Submitted: auto-generated X-Mailer: Trac 0.12.2, by Edgewall Software To: draft-ietf-core-coap@tools.ietf.org, cabo@tzi.org, zach@sensinode.com, esko.dijk@philips.com X-Trac-Project: core Date: Mon, 18 Jun 2012 10:44:30 -0000 X-URL: http://tools.ietf.org/core/ X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/core/trac/ticket/232#comment:4 Message-ID: <068.d64d100e03ec5405ddc6d6852d03a668@trac.tools.ietf.org> References: <053.8004f0cc0b270920cdf2b55b6caf2b79@trac.tools.ietf.org> X-Trac-Ticket-ID: 232 In-Reply-To: <053.8004f0cc0b270920cdf2b55b6caf2b79@trac.tools.ietf.org> X-SA-Exim-Connect-IP: 127.0.0.1 X-SA-Exim-Rcpt-To: draft-ietf-core-coap@tools.ietf.org, cabo@tzi.org, zach@sensinode.com, esko.dijk@philips.com, core@ietf.org X-SA-Exim-Mail-From: trac+core@trac.tools.ietf.org X-SA-Exim-Scanned: No (on grenache.tools.ietf.org); SAEximRunCond expanded to false Resent-To: Resent-Message-Id: <20120618104450.E572821F8552@ietfa.amsl.com> Resent-Date: Mon, 18 Jun 2012 03:44:50 -0700 (PDT) Resent-From: trac+core@trac.tools.ietf.org Cc: core@ietf.org Subject: Re: [core] #232: Clarify inclusion of Location options in a 2.01 (Created) response X-BeenThere: core@ietf.org X-Mailman-Version: 2.1.12 Reply-To: trac+core@trac.tools.ietf.org List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Jun 2012 10:44:51 -0000 #232: Clarify inclusion of Location options in a 2.01 (Created) response Comment (by esko.dijk@…): Comment on the new text: If a resource has been created on the server, a 2.01 (Created) response MAY be returned, which may include the URI of the new resource in a sequence of one or more Location-Path and/or Location- Query Options (Section 5.9.1.1 and Section 5.10.8). If the POST the "may" in "may include the URI of the new" -> why not MAY ? -- -----------------------------+------------------------------------- Reporter: hartke@… | Owner: draft-ietf-core-coap@… Type: editorial | Status: closed Priority: minor | Milestone: post-WGLC-1 Component: coap | Version: coap-09 Severity: In WG Last Call | Resolution: fixed Keywords: | -----------------------------+------------------------------------- Ticket URL: core From hartke@tzi.org Mon Jun 18 04:01:26 2012 Return-Path: X-Original-To: core@ietfa.amsl.com Delivered-To: core@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AC16121F8589 for ; Mon, 18 Jun 2012 04:01:26 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.627 X-Spam-Level: X-Spam-Status: No, score=-5.627 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-4] 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 cna9vqEYBPSd for ; Mon, 18 Jun 2012 04:01:26 -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 3388921F8564 for ; Mon, 18 Jun 2012 04:01:12 -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.3/8.14.3) with ESMTP id q5IB14De003345 for ; Mon, 18 Jun 2012 13:01:04 +0200 (CEST) Received: from mail-pz0-f44.google.com (mail-pz0-f44.google.com [209.85.210.44]) (using TLSv1 with cipher DES-CBC3-SHA (168/168 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id 51CC2DB1 for ; Mon, 18 Jun 2012 13:01:04 +0200 (CEST) Received: by dacx6 with SMTP id x6so6835839dac.31 for ; Mon, 18 Jun 2012 04:01:02 -0700 (PDT) MIME-Version: 1.0 Received: by 10.68.244.100 with SMTP id xf4mr50348761pbc.147.1340017261467; Mon, 18 Jun 2012 04:01:01 -0700 (PDT) Received: by 10.68.16.42 with HTTP; Mon, 18 Jun 2012 04:01:01 -0700 (PDT) In-Reply-To: <068.d64d100e03ec5405ddc6d6852d03a668@trac.tools.ietf.org> References: <053.8004f0cc0b270920cdf2b55b6caf2b79@trac.tools.ietf.org> <068.d64d100e03ec5405ddc6d6852d03a668@trac.tools.ietf.org> Date: Mon, 18 Jun 2012 13:01:01 +0200 Message-ID: From: Klaus Hartke To: core@ietf.org Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Subject: Re: [core] #232: Clarify inclusion of Location options in a 2.01 (Created) response X-BeenThere: core@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Jun 2012 11:01:26 -0000 Esko Dijk wrote: > #232: Clarify inclusion of Location options in a 2.01 (Created) response > > Comment (by esko.dijk@=85): > > =A0Comment on the new text: > > =A0If a resource has been created on the server, a 2.01 (Created) > =A0 =A0response MAY be returned, which may include the URI of the new > =A0 =A0resource in a sequence of one or more Location-Path and/or Locatio= n- > =A0 =A0Query Options (Section 5.9.1.1 and Section 5.10.8). =A0If the POST > > =A0the "may" in "may include the URI of the new" -> why not MAY ? Probably because the authoritative MAY is in 5.10.8. Or because RFC2119 actually doesn't require the keywords to be capitalized. But I see no harm in replacing the "may" with a MAY. I'm more worried about the first MAY; it sounds a bit like it's optional to return a response at all... Klaus From esko.dijk@philips.com Mon Jun 18 04:29:10 2012 Return-Path: X-Original-To: core@ietfa.amsl.com Delivered-To: core@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2B14121F8595 for ; Mon, 18 Jun 2012 04:29:10 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.599 X-Spam-Level: X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4] 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 XQZ5YwZk7nLF for ; Mon, 18 Jun 2012 04:29:09 -0700 (PDT) Received: from tx2outboundpool.messaging.microsoft.com (tx2ehsobe005.messaging.microsoft.com [65.55.88.15]) by ietfa.amsl.com (Postfix) with ESMTP id 5FB3D21F84CF for ; Mon, 18 Jun 2012 04:29:09 -0700 (PDT) Received: from mail11-tx2-R.bigfish.com (10.9.14.245) by TX2EHSOBE004.bigfish.com (10.9.40.24) with Microsoft SMTP Server id 14.1.225.23; Mon, 18 Jun 2012 11:27:50 +0000 Received: from mail11-tx2 (localhost [127.0.0.1]) by mail11-tx2-R.bigfish.com (Postfix) with ESMTP id 899363200A6; Mon, 18 Jun 2012 11:27:50 +0000 (UTC) X-Forefront-Antispam-Report: CIP:157.55.7.222; KIP:(null); UIP:(null); IPV:NLI; H:mail.philips.com; RD:none; EFVD:NLI X-SpamScore: -40 X-BigFish: VPS-40(zz217bL98dI15d6O9251J542M1432Izz1202hzz1033IL8275dhz2dh2a8h668h839hd25hf0ah) Received: from mail11-tx2 (localhost.localdomain [127.0.0.1]) by mail11-tx2 (MessageSwitch) id 1340018869515347_24464; Mon, 18 Jun 2012 11:27:49 +0000 (UTC) Received: from TX2EHSMHS031.bigfish.com (unknown [10.9.14.237]) by mail11-tx2.bigfish.com (Postfix) with ESMTP id 70B0A20003F; Mon, 18 Jun 2012 11:27:49 +0000 (UTC) Received: from mail.philips.com (157.55.7.222) by TX2EHSMHS031.bigfish.com (10.9.99.131) with Microsoft SMTP Server (TLS) id 14.1.225.23; Mon, 18 Jun 2012 11:27:48 +0000 Received: from 011-DB3MMR1-021.MGDPHG.emi.philips.com (10.128.28.103) by 011-DB3MMR1-008.MGDPHG.emi.philips.com (10.128.28.47) with Microsoft SMTP Server (TLS) id 14.1.355.3; Mon, 18 Jun 2012 12:32:46 +0100 Received: from 011-DB3MPN2-081.MGDPHG.emi.philips.com ([169.254.1.197]) by 011-DB3MMR1-021.MGDPHG.emi.philips.com ([fe80::f066:9203:e7da:3658%11]) with mapi id 14.01.0355.003; Mon, 18 Jun 2012 12:32:44 +0100 From: "Dijk, Esko" To: Klaus Hartke , "core@ietf.org" Thread-Topic: [core] #232: Clarify inclusion of Location options in a 2.01 (Created) response Thread-Index: AQHNJ4Saya1KCqI6sESR7xtAwGAp+ZcAHuEAgAAEnYCAABegsA== Date: Mon, 18 Jun 2012 11:28:55 +0000 Message-ID: <031DD135F9160444ABBE3B0C36CED618A9323F@011-DB3MPN2-081.MGDPHG.emi.philips.com> References: <053.8004f0cc0b270920cdf2b55b6caf2b79@trac.tools.ietf.org> <068.d64d100e03ec5405ddc6d6852d03a668@trac.tools.ietf.org> In-Reply-To: Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [86.94.216.29] Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-OriginatorOrg: philips.com Subject: Re: [core] #232: Clarify inclusion of Location options in a 2.01 (Created) response X-BeenThere: core@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Jun 2012 11:29:10 -0000 > RFC2119 actually doesn't require the keywords to be capitalized. Well, but core-coap section 1.2 defines them capitalized so ... :) > I'm more worried about the first MAY; it sounds a bit like it's > optional to return a response at all... My feel here was that a server could typically respond 2.04 in this case, i= nstead of 2.01. Esko -----Original Message----- From: core-bounces@ietf.org [mailto:core-bounces@ietf.org] On Behalf Of Kla= us Hartke Sent: Monday 18 June 2012 13:01 To: core@ietf.org Subject: Re: [core] #232: Clarify inclusion of Location options in a 2.01 (= Created) response Esko Dijk wrote: > #232: Clarify inclusion of Location options in a 2.01 (Created) response > > Comment (by esko.dijk@...): > > Comment on the new text: > > If a resource has been created on the server, a 2.01 (Created) > response MAY be returned, which may include the URI of the new > resource in a sequence of one or more Location-Path and/or Location- > Query Options (Section 5.9.1.1 and Section 5.10.8). If the POST > > the "may" in "may include the URI of the new" -> why not MAY ? Probably because the authoritative MAY is in 5.10.8. Or because RFC2119 actually doesn't require the keywords to be capitalized. But I see no harm in replacing the "may" with a MAY. I'm more worried about the first MAY; it sounds a bit like it's optional to return a response at all... Klaus _______________________________________________ core mailing list core@ietf.org https://www.ietf.org/mailman/listinfo/core ________________________________ The information contained in this message may be confidential and legally p= rotected under applicable law. The message is intended solely for the addre= ssee(s). If you are not the intended recipient, you are hereby notified tha= t any use, forwarding, dissemination, or reproduction of this message is st= rictly prohibited and may be unlawful. If you are not the intended recipien= t, please contact the sender by return e-mail and destroy all copies of the= original message. From cabo@tzi.org Mon Jun 18 04:53:51 2012 Return-Path: X-Original-To: core@ietfa.amsl.com Delivered-To: core@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0364C21F855E for ; Mon, 18 Jun 2012 04:53:51 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -106.576 X-Spam-Level: X-Spam-Status: No, score=-106.576 tagged_above=-999 required=5 tests=[AWL=-0.327, 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 KMaEMbNxi6-G for ; Mon, 18 Jun 2012 04:53:50 -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 4030D21F854F for ; Mon, 18 Jun 2012 04:53:50 -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.3/8.14.3) with ESMTP id q5IBrhTh025042 for ; Mon, 18 Jun 2012 13:53:43 +0200 (CEST) Received: from [192.168.217.105] (p54894F25.dip.t-dialin.net [84.137.79.37]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id E7E95E36; Mon, 18 Jun 2012 13:53:42 +0200 (CEST) Mime-Version: 1.0 (Apple Message framework v1278) Content-Type: text/plain; charset=windows-1252 From: Carsten Bormann In-Reply-To: Date: Mon, 18 Jun 2012 13:53:41 +0200 Content-Transfer-Encoding: quoted-printable Message-Id: <4386D1B9-4BB4-4078-8252-0EFA4D293D80@tzi.org> References: <053.8004f0cc0b270920cdf2b55b6caf2b79@trac.tools.ietf.org> <068.d64d100e03ec5405ddc6d6852d03a668@trac.tools.ietf.org> To: Klaus Hartke X-Mailer: Apple Mail (2.1278) Cc: core@ietf.org Subject: Re: [core] #232: Clarify inclusion of Location options in a 2.01 (Created) response X-BeenThere: core@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Jun 2012 11:53:51 -0000 On Jun 18, 2012, at 13:01, Klaus Hartke wrote: > Or because > RFC2119 actually doesn't require the keywords to be capitalized.=20 Fixed that part (not the whole ticket) in [716]. Gr=FC=DFe, Carsten From hartke@tzi.org Mon Jun 18 05:00:24 2012 Return-Path: X-Original-To: core@ietfa.amsl.com Delivered-To: core@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BD73B21F85D9 for ; Mon, 18 Jun 2012 05:00:24 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.627 X-Spam-Level: X-Spam-Status: No, score=-5.627 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-4] 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 w0u5d2Yg66dQ for ; Mon, 18 Jun 2012 05:00:24 -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 DBC4721F85D4 for ; Mon, 18 Jun 2012 05:00:23 -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.3/8.14.3) with ESMTP id q5IC0F7x028798 for ; Mon, 18 Jun 2012 14:00:15 +0200 (CEST) Received: from mail-pb0-f44.google.com (mail-pb0-f44.google.com [209.85.160.44]) (using TLSv1 with cipher DES-CBC3-SHA (168/168 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id DB56CE3E for ; Mon, 18 Jun 2012 14:00:14 +0200 (CEST) Received: by pbcwy7 with SMTP id wy7so8179299pbc.31 for ; Mon, 18 Jun 2012 05:00:13 -0700 (PDT) MIME-Version: 1.0 Received: by 10.68.217.234 with SMTP id pb10mr51569751pbc.79.1340020813014; Mon, 18 Jun 2012 05:00:13 -0700 (PDT) Received: by 10.68.16.42 with HTTP; Mon, 18 Jun 2012 05:00:12 -0700 (PDT) In-Reply-To: <031DD135F9160444ABBE3B0C36CED618A9323F@011-DB3MPN2-081.MGDPHG.emi.philips.com> References: <053.8004f0cc0b270920cdf2b55b6caf2b79@trac.tools.ietf.org> <068.d64d100e03ec5405ddc6d6852d03a668@trac.tools.ietf.org> <031DD135F9160444ABBE3B0C36CED618A9323F@011-DB3MPN2-081.MGDPHG.emi.philips.com> Date: Mon, 18 Jun 2012 14:00:12 +0200 Message-ID: From: Klaus Hartke To: "core@ietf.org" Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Subject: Re: [core] #232: Clarify inclusion of Location options in a 2.01 (Created) response X-BeenThere: core@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Jun 2012 12:00:24 -0000 Esko Dijk wrote: >>> =A0If a resource has been created on the server, a 2.01 (Created) >>> =A0response MAY be returned, which may include the URI of the new >>> =A0resource in a sequence of one or more Location-Path and/or Location- >>> =A0Query Options (Section 5.9.1.1 and Section 5.10.8). =A0If the POST >> >> I'm more worried about the first MAY; it sounds a bit like it's >> optional to return a response at all... > > My feel here was that a server could typically respond 2.04 in this case,= instead of 2.01. For comparison, this is what httpbis [1] says: The action performed by the POST method might not result in a resource that can be identified by a URI. In this case, either 200 (OK) or 204 (No Content) is the appropriate response status code, depending on whether or not the response includes a representation that describes the result. If a resource has been created on the origin server, the response SHOULD be 201 (Created) and contain a representation which describes the status of the request and refers to the new resource, and a Location header field (see Section 10.5). So translated to CoAP, this would mean that *if* a resource is created, there MUST be a response, the response code SHOULD be 2.01 (Created), there SHOULD be a payload, and there SHOULD be a Location Option. If the POST succeeds but does *not* result in a new resource, there MUST be response, the response code SHOULD be 2.04 (Changed) and there MAY be a payload. I'm not sure why we should do this very differently... Klaus [1] http://tools.ietf.org/html/draft-ietf-httpbis-p2-semantics-19#section-6= .5 From esko.dijk@philips.com Mon Jun 18 06:19:25 2012 Return-Path: X-Original-To: core@ietfa.amsl.com Delivered-To: core@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F034621F85F8 for ; Mon, 18 Jun 2012 06:19:25 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.099 X-Spam-Level: X-Spam-Status: No, score=-5.099 tagged_above=-999 required=5 tests=[AWL=-1.500, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1] 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 wReFwJmJntHy for ; Mon, 18 Jun 2012 06:19:25 -0700 (PDT) Received: from va3outboundpool.messaging.microsoft.com (va3ehsobe004.messaging.microsoft.com [216.32.180.14]) by ietfa.amsl.com (Postfix) with ESMTP id 109B921F85C7 for ; Mon, 18 Jun 2012 06:19:24 -0700 (PDT) Received: from mail113-va3-R.bigfish.com (10.7.14.246) by VA3EHSOBE010.bigfish.com (10.7.40.12) with Microsoft SMTP Server id 14.1.225.22; Mon, 18 Jun 2012 13:18:06 +0000 Received: from mail113-va3 (localhost [127.0.0.1]) by mail113-va3-R.bigfish.com (Postfix) with ESMTP id ACFB01804A3; Mon, 18 Jun 2012 13:18:05 +0000 (UTC) X-Forefront-Antispam-Report: CIP:157.55.7.222; KIP:(null); UIP:(null); IPV:NLI; H:mail.philips.com; RD:none; EFVD:NLI X-SpamScore: -40 X-BigFish: VPS-40(zz217bL98dI15d6O9251J542M1432Izz1202hzz1033IL8275dhz2dh2a8h668h839hd25hf0ah) Received: from mail113-va3 (localhost.localdomain [127.0.0.1]) by mail113-va3 (MessageSwitch) id 134002546769899_20661; Mon, 18 Jun 2012 13:17:47 +0000 (UTC) Received: from VA3EHSMHS028.bigfish.com (unknown [10.7.14.254]) by mail113-va3.bigfish.com (Postfix) with ESMTP id 35406360069; Mon, 18 Jun 2012 13:17:30 +0000 (UTC) Received: from mail.philips.com (157.55.7.222) by VA3EHSMHS028.bigfish.com (10.7.99.38) with Microsoft SMTP Server (TLS) id 14.1.225.23; Mon, 18 Jun 2012 13:17:29 +0000 Received: from 011-DB3MMR1-020.MGDPHG.emi.philips.com (10.128.28.101) by 011-DB3MMR1-007.MGDPHG.emi.philips.com (10.128.28.57) with Microsoft SMTP Server (TLS) id 14.1.355.3; Mon, 18 Jun 2012 14:22:25 +0100 Received: from 011-DB3MPN2-081.MGDPHG.emi.philips.com ([169.254.1.197]) by 011-DB3MMR1-020.MGDPHG.emi.philips.com ([fe80::65e7:4d4c:4c67:daa9%11]) with mapi id 14.01.0355.003; Mon, 18 Jun 2012 14:22:26 +0100 From: "Dijk, Esko" To: Klaus Hartke , "core@ietf.org" Thread-Topic: [core] #232: Clarify inclusion of Location options in a 2.01 (Created) response Thread-Index: AQHNJ4Saya1KCqI6sESR7xtAwGAp+ZcAHuEAgAAEnYCAABegsP//+OkAgAAlY2A= Date: Mon, 18 Jun 2012 13:18:36 +0000 Message-ID: <031DD135F9160444ABBE3B0C36CED618A932AE@011-DB3MPN2-081.MGDPHG.emi.philips.com> References: <053.8004f0cc0b270920cdf2b55b6caf2b79@trac.tools.ietf.org> <068.d64d100e03ec5405ddc6d6852d03a668@trac.tools.ietf.org> <031DD135F9160444ABBE3B0C36CED618A9323F@011-DB3MPN2-081.MGDPHG.emi.philips.com> In-Reply-To: Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [86.94.216.29] Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-OriginatorOrg: philips.com Subject: Re: [core] #232: Clarify inclusion of Location options in a 2.01 (Created) response X-BeenThere: core@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Jun 2012 13:19:26 -0000 > I'm not sure why we should do this very differently... Me neither, though there could be some resource-constraint reasons for not = sending back the Location-* options. But a SHOULD on returning 2.01 for created resources seems logical. The core interim discussion record for #232: Change is ok. Discussion on the level of the requirement SHOULD, MAY or M= UST. Carsten: Quality of Implementation SHOULD? Cullen: HTTP servers often don't return the location. -> MAY seems best for sending 2.01 Esko -----Original Message----- From: core-bounces@ietf.org [mailto:core-bounces@ietf.org] On Behalf Of Kla= us Hartke Sent: Monday 18 June 2012 14:00 To: core@ietf.org Subject: Re: [core] #232: Clarify inclusion of Location options in a 2.01 (= Created) response Esko Dijk wrote: >>> If a resource has been created on the server, a 2.01 (Created) >>> response MAY be returned, which may include the URI of the new >>> resource in a sequence of one or more Location-Path and/or Location- >>> Query Options (Section 5.9.1.1 and Section 5.10.8). If the POST >> >> I'm more worried about the first MAY; it sounds a bit like it's >> optional to return a response at all... > > My feel here was that a server could typically respond 2.04 in this case,= instead of 2.01. For comparison, this is what httpbis [1] says: The action performed by the POST method might not result in a resource that can be identified by a URI. In this case, either 200 (OK) or 204 (No Content) is the appropriate response status code, depending on whether or not the response includes a representation that describes the result. If a resource has been created on the origin server, the response SHOULD be 201 (Created) and contain a representation which describes the status of the request and refers to the new resource, and a Location header field (see Section 10.5). So translated to CoAP, this would mean that *if* a resource is created, there MUST be a response, the response code SHOULD be 2.01 (Created), there SHOULD be a payload, and there SHOULD be a Location Option. If the POST succeeds but does *not* result in a new resource, there MUST be response, the response code SHOULD be 2.04 (Changed) and there MAY be a payload. I'm not sure why we should do this very differently... Klaus [1] http://tools.ietf.org/html/draft-ietf-httpbis-p2-semantics-19#section-6= .5 _______________________________________________ core mailing list core@ietf.org https://www.ietf.org/mailman/listinfo/core ________________________________ The information contained in this message may be confidential and legally p= rotected under applicable law. The message is intended solely for the addre= ssee(s). If you are not the intended recipient, you are hereby notified tha= t any use, forwarding, dissemination, or reproduction of this message is st= rictly prohibited and may be unlawful. If you are not the intended recipien= t, please contact the sender by return e-mail and destroy all copies of the= original message. From hartke@tzi.org Mon Jun 18 07:30:36 2012 Return-Path: X-Original-To: core@ietfa.amsl.com Delivered-To: core@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2BF7A21F8658 for ; Mon, 18 Jun 2012 07:30:36 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.627 X-Spam-Level: X-Spam-Status: No, score=-5.627 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-4] 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 M7KWFlOH8a2S for ; Mon, 18 Jun 2012 07:30:35 -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 3D12121F85EA for ; Mon, 18 Jun 2012 07:30:35 -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.3/8.14.3) with ESMTP id q5IEUR8k029265 for ; Mon, 18 Jun 2012 16:30:27 +0200 (CEST) Received: from mail-pb0-f44.google.com (mail-pb0-f44.google.com [209.85.160.44]) (using TLSv1 with cipher DES-CBC3-SHA (168/168 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id 7C1A0F8B for ; Mon, 18 Jun 2012 16:30:27 +0200 (CEST) Received: by pbcwy7 with SMTP id wy7so8353006pbc.31 for ; Mon, 18 Jun 2012 07:30:25 -0700 (PDT) MIME-Version: 1.0 Received: by 10.68.244.100 with SMTP id xf4mr52153784pbc.147.1340029825682; Mon, 18 Jun 2012 07:30:25 -0700 (PDT) Received: by 10.68.16.42 with HTTP; Mon, 18 Jun 2012 07:30:25 -0700 (PDT) In-Reply-To: <031DD135F9160444ABBE3B0C36CED618A932AE@011-DB3MPN2-081.MGDPHG.emi.philips.com> References: <053.8004f0cc0b270920cdf2b55b6caf2b79@trac.tools.ietf.org> <068.d64d100e03ec5405ddc6d6852d03a668@trac.tools.ietf.org> <031DD135F9160444ABBE3B0C36CED618A9323F@011-DB3MPN2-081.MGDPHG.emi.philips.com> <031DD135F9160444ABBE3B0C36CED618A932AE@011-DB3MPN2-081.MGDPHG.emi.philips.com> Date: Mon, 18 Jun 2012 16:30:25 +0200 Message-ID: From: Klaus Hartke To: "core@ietf.org" Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Subject: Re: [core] #232: Clarify inclusion of Location options in a 2.01 (Created) response X-BeenThere: core@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Jun 2012 14:30:36 -0000 Esko Dijk wrote: >> I'm not sure why we should do this very differently... > Me neither, though there could be some resource-constraint reasons for no= t sending back the Location-* options. > But a SHOULD on returning 2.01 for created resources seems logical. Then a SHOULD for the inclusion of a location in a 2.01 (Created) response seems appropriate: there could be some resource-constraint reasons, but the implication that the client won't be able to discover the location of the created resource must be understood and carefully weighed before omitting the options. > The core interim discussion record for #232: > > =A0Change is ok. Discussion on the level of the requirement SHOULD, MAY o= r MUST. > =A0Carsten: Quality of Implementation SHOULD? > =A0Cullen: HTTP servers often don't return the location. > =A0-> MAY seems best for sending 2.01 So it seems the discussion was about whether the inclusion of the Location-* Options in a 2.01 (Created) response should be a SHOULD, MAY or MUST, but the decision made was about whether the response code for a new resource being a 2.01 (Created) should be a SHOULD, MAY or MUST. I think we should undo the decision for MAY here. If a new resource was created, the response SHOULD have a 2.01 (Created) response code. Klaus From trac+core@trac.tools.ietf.org Mon Jun 18 11:41:06 2012 Return-Path: X-Original-To: core@ietfa.amsl.com Delivered-To: core@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6137E21F86D1 for ; Mon, 18 Jun 2012 11:41:06 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -101.785 X-Spam-Level: X-Spam-Status: No, score=-101.785 tagged_above=-999 required=5 tests=[AWL=0.814, 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 fKJQvTBk0nR9 for ; Mon, 18 Jun 2012 11:41:06 -0700 (PDT) Received: from grenache.tools.ietf.org (grenache.tools.ietf.org [77.72.230.30]) by ietfa.amsl.com (Postfix) with ESMTP id C695621F86CF for ; Mon, 18 Jun 2012 11:41:05 -0700 (PDT) Received: from localhost ([127.0.0.1]:55208 helo=grenache.tools.ietf.org ident=www-data) by grenache.tools.ietf.org with esmtp (Exim 4.77) (envelope-from ) id 1SggsU-0004D5-97; Mon, 18 Jun 2012 20:40:42 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit From: "core issue tracker" X-Trac-Version: 0.12.2 Precedence: bulk Auto-Submitted: auto-generated X-Mailer: Trac 0.12.2, by Edgewall Software To: draft-ietf-core-coap@tools.ietf.org, cabo@tzi.org, zach@sensinode.com, esko.dijk@philips.com, hartke@tzi.org X-Trac-Project: core Date: Mon, 18 Jun 2012 18:40:42 -0000 X-URL: http://tools.ietf.org/core/ X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/core/trac/ticket/232#comment:5 Message-ID: <068.9bbf09299262f361b24de3b2aa6f982e@trac.tools.ietf.org> References: <053.8004f0cc0b270920cdf2b55b6caf2b79@trac.tools.ietf.org> X-Trac-Ticket-ID: 232 In-Reply-To: <053.8004f0cc0b270920cdf2b55b6caf2b79@trac.tools.ietf.org> X-SA-Exim-Connect-IP: 127.0.0.1 X-SA-Exim-Rcpt-To: draft-ietf-core-coap@tools.ietf.org, cabo@tzi.org, zach@sensinode.com, esko.dijk@philips.com, hartke@tzi.org, core@ietf.org X-SA-Exim-Mail-From: trac+core@trac.tools.ietf.org X-SA-Exim-Scanned: No (on grenache.tools.ietf.org); SAEximRunCond expanded to false Resent-To: Resent-Message-Id: <20120618184105.C695621F86CF@ietfa.amsl.com> Resent-Date: Mon, 18 Jun 2012 11:41:05 -0700 (PDT) Resent-From: trac+core@trac.tools.ietf.org Cc: core@ietf.org Subject: Re: [core] #232: Clarify inclusion of Location options in a 2.01 (Created) response X-BeenThere: core@ietf.org X-Mailman-Version: 2.1.12 Reply-To: trac+core@trac.tools.ietf.org List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Jun 2012 18:41:06 -0000 #232: Clarify inclusion of Location options in a 2.01 (Created) response Changes (by hartke@…): * status: closed => reopened * resolution: fixed => Comment: This ticket is about whether the inclusion of the Location-* Options in a 2.01 (Created) response should be a SHOULD (as stated in coap-09 section 5.8.2.) or a MAY (as stated in coap-09 section 5.10.8.). This is also what was discussed at the interim, but for some reason it seems that the discussion concluded with the decision to make the return of a 2.01 (Created) response a MAY. I've reverted the changes made in r692 for now. -- -----------------------------+------------------------------------- Reporter: hartke@… | Owner: draft-ietf-core-coap@… Type: editorial | Status: reopened Priority: minor | Milestone: post-WGLC-1 Component: coap | Version: coap-09 Severity: In WG Last Call | Resolution: Keywords: | -----------------------------+------------------------------------- Ticket URL: core From ari.keranen@nomadiclab.com Wed Jun 20 06:42:46 2012 Return-Path: X-Original-To: core@ietfa.amsl.com Delivered-To: core@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3477B21F86C3 for ; Wed, 20 Jun 2012 06:42:46 -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 W3N-mY7oLWU4 for ; Wed, 20 Jun 2012 06:42:45 -0700 (PDT) Received: from gw.nomadiclab.com (unknown [IPv6:2001:14b8:400:101::2]) by ietfa.amsl.com (Postfix) with ESMTP id 753AD21F86CA for ; Wed, 20 Jun 2012 06:42:45 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by gw.nomadiclab.com (Postfix) with ESMTP id D630E4E6EB; Wed, 20 Jun 2012 16:42:44 +0300 (EEST) X-Virus-Scanned: amavisd-new at nomadiclab.com Received: from gw.nomadiclab.com ([127.0.0.1]) by localhost (inside.nomadiclab.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QBYkOsr_DpO3; Wed, 20 Jun 2012 16:42:44 +0300 (EEST) Received: from n212.nomadiclab.com (localhost [IPv6:::1]) by gw.nomadiclab.com (Postfix) with ESMTPSA id 25F114E6E9; Wed, 20 Jun 2012 16:42:44 +0300 (EEST) Message-ID: <4FE1D353.7020109@nomadiclab.com> Date: Wed, 20 Jun 2012 16:42:43 +0300 From: Ari Keranen User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:13.0) Gecko/20120614 Thunderbird/13.0.1 MIME-Version: 1.0 To: Zach Shelby References: <057.f44297cd39b3b1ff3294035adc0e7f16@trac.tools.ietf.org> <072.5c15f1eb583565f73a961f8acff50c7d@trac.tools.ietf.org> In-Reply-To: <072.5c15f1eb583565f73a961f8acff50c7d@trac.tools.ietf.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: core@ietf.org Subject: Re: [core] #222: RawPublicKey identifier X-BeenThere: core@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Jun 2012 13:42:46 -0000 FYI: based on the feedback we've got on the naming draft so far, the "human-readable format" has been renamed in to "human-speakable format". Cheers, Ari On 6/11/12 5:12 PM, core issue tracker wrote: > Depending on how identifiers are given to the system that verifies > them, support for URI, binary, and/or human-readable format > [draft-ni] needs to be implemented. All implementations SHOULD > support the binary mode and implementations that have a user > interface SHOULD also support the human-readable format. From trac+core@trac.tools.ietf.org Wed Jun 20 15:10:21 2012 Return-Path: X-Original-To: core@ietfa.amsl.com Delivered-To: core@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 54C1A11E80C8 for ; Wed, 20 Jun 2012 15:10:21 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -101.813 X-Spam-Level: X-Spam-Status: No, score=-101.813 tagged_above=-999 required=5 tests=[AWL=0.786, 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 Uj0d+GgUhPVH for ; Wed, 20 Jun 2012 15:10:20 -0700 (PDT) Received: from grenache.tools.ietf.org (grenache.tools.ietf.org [77.72.230.30]) by ietfa.amsl.com (Postfix) with ESMTP id A207F11E80CB for ; Wed, 20 Jun 2012 15:10:20 -0700 (PDT) Received: from localhost ([127.0.0.1]:46821 helo=grenache.tools.ietf.org ident=www-data) by grenache.tools.ietf.org with esmtp (Exim 4.77) (envelope-from ) id 1ShT6C-0003fj-BE; Thu, 21 Jun 2012 00:10:04 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit From: "core issue tracker" X-Trac-Version: 0.12.2 Precedence: bulk Auto-Submitted: auto-generated X-Mailer: Trac 0.12.2, by Edgewall Software To: hartke@tzi.org, zach@sensinode.com X-Trac-Project: core Date: Wed, 20 Jun 2012 22:10:04 -0000 X-URL: http://tools.ietf.org/core/ X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/core/trac/ticket/231#comment:2 Message-ID: <068.068e983c63eccc944d9c650cf6643f8a@trac.tools.ietf.org> References: <053.23dacbfaca0136062ef666c59397aee9@trac.tools.ietf.org> X-Trac-Ticket-ID: 231 In-Reply-To: <053.23dacbfaca0136062ef666c59397aee9@trac.tools.ietf.org> X-SA-Exim-Connect-IP: 127.0.0.1 X-SA-Exim-Rcpt-To: hartke@tzi.org, zach@sensinode.com, core@ietf.org X-SA-Exim-Mail-From: trac+core@trac.tools.ietf.org X-SA-Exim-Scanned: No (on grenache.tools.ietf.org); SAEximRunCond expanded to false Cc: core@ietf.org Subject: Re: [core] #231: Splitting/combining Location options X-BeenThere: core@ietf.org X-Mailman-Version: 2.1.12 Reply-To: trac+core@trac.tools.ietf.org List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Jun 2012 22:10:21 -0000 #231: Splitting/combining Location options Changes (by hartke@…): * status: new => closed * resolution: => fixed Comment: The following text was added to section 5.10.8 in r738: {{{ The steps for constructing the location URI from the options are analogously to Section 6.5, except that the first five steps are skipped and the result is a relative URI-reference. }}} -- -----------------------------+-------------------------- Reporter: hartke@… | Owner: hartke@… Type: other technical | Status: closed Priority: minor | Milestone: post-WGLC-1 Component: coap | Version: coap-09 Severity: In WG Last Call | Resolution: fixed Keywords: | -----------------------------+-------------------------- Ticket URL: core From trac+core@trac.tools.ietf.org Fri Jun 22 12:06:00 2012 Return-Path: X-Original-To: core@ietfa.amsl.com Delivered-To: core@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 343B821F8754 for ; Fri, 22 Jun 2012 12:06:00 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -101.839 X-Spam-Level: X-Spam-Status: No, score=-101.839 tagged_above=-999 required=5 tests=[AWL=0.760, 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 s1o-IvvViZNr for ; Fri, 22 Jun 2012 12:05:59 -0700 (PDT) Received: from grenache.tools.ietf.org (grenache.tools.ietf.org [77.72.230.30]) by ietfa.amsl.com (Postfix) with ESMTP id 4D33F21F86C4 for ; Fri, 22 Jun 2012 12:05:59 -0700 (PDT) Received: from localhost ([127.0.0.1]:33172 helo=grenache.tools.ietf.org ident=www-data) by grenache.tools.ietf.org with esmtp (Exim 4.77) (envelope-from ) id 1Si9Ao-0007EM-Nb; Fri, 22 Jun 2012 21:05:38 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit From: "core issue tracker" X-Trac-Version: 0.12.2 Precedence: bulk Auto-Submitted: auto-generated X-Mailer: Trac 0.12.2, by Edgewall Software To: draft-ietf-core-coap@tools.ietf.org, cabo@tzi.org, zach@sensinode.com, esko.dijk@philips.com, hartke@tzi.org X-Trac-Project: core Date: Fri, 22 Jun 2012 19:05:38 -0000 X-URL: http://tools.ietf.org/core/ X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/core/trac/ticket/232#comment:6 Message-ID: <068.b41c15eaa202a2238dfd4b11deb892b7@trac.tools.ietf.org> References: <053.8004f0cc0b270920cdf2b55b6caf2b79@trac.tools.ietf.org> X-Trac-Ticket-ID: 232 In-Reply-To: <053.8004f0cc0b270920cdf2b55b6caf2b79@trac.tools.ietf.org> X-SA-Exim-Connect-IP: 127.0.0.1 X-SA-Exim-Rcpt-To: draft-ietf-core-coap@tools.ietf.org, cabo@tzi.org, zach@sensinode.com, esko.dijk@philips.com, hartke@tzi.org, core@ietf.org X-SA-Exim-Mail-From: trac+core@trac.tools.ietf.org X-SA-Exim-Scanned: No (on grenache.tools.ietf.org); SAEximRunCond expanded to false Resent-To: Resent-Message-Id: <20120622190559.4D33F21F86C4@ietfa.amsl.com> Resent-Date: Fri, 22 Jun 2012 12:05:59 -0700 (PDT) Resent-From: trac+core@trac.tools.ietf.org Cc: core@ietf.org Subject: Re: [core] #232: Clarify inclusion of Location options in a 2.01 (Created) response X-BeenThere: core@ietf.org X-Mailman-Version: 2.1.12 Reply-To: trac+core@trac.tools.ietf.org List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 Jun 2012 19:06:00 -0000 #232: Clarify inclusion of Location options in a 2.01 (Created) response Changes (by hartke@…): * status: reopened => closed * resolution: => fixed Comment: Section 5.10.8 references Section 5.8.2 now. -- -----------------------------+------------------------------------- Reporter: hartke@… | Owner: draft-ietf-core-coap@… Type: editorial | Status: closed Priority: minor | Milestone: post-WGLC-1 Component: coap | Version: coap-09 Severity: In WG Last Call | Resolution: fixed Keywords: | -----------------------------+------------------------------------- Ticket URL: core From trac+core@trac.tools.ietf.org Fri Jun 22 12:16:51 2012 Return-Path: X-Original-To: core@ietfa.amsl.com Delivered-To: core@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 82CCC11E809B for ; Fri, 22 Jun 2012 12:16:51 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -101.864 X-Spam-Level: X-Spam-Status: No, score=-101.864 tagged_above=-999 required=5 tests=[AWL=0.735, 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 BHgYAhRztcVq for ; Fri, 22 Jun 2012 12:16:51 -0700 (PDT) Received: from grenache.tools.ietf.org (grenache.tools.ietf.org [77.72.230.30]) by ietfa.amsl.com (Postfix) with ESMTP id DAA5611E807F for ; Fri, 22 Jun 2012 12:16:50 -0700 (PDT) Received: from localhost ([127.0.0.1]:33724 helo=grenache.tools.ietf.org ident=www-data) by grenache.tools.ietf.org with esmtp (Exim 4.77) (envelope-from ) id 1Si9La-0001RV-6l; Fri, 22 Jun 2012 21:16:46 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit From: "core issue tracker" X-Trac-Version: 0.12.2 Precedence: bulk Auto-Submitted: auto-generated X-Mailer: Trac 0.12.2, by Edgewall Software To: draft-ietf-core-observe@tools.ietf.org, cabo@tzi.org, hartke@tzi.org X-Trac-Project: core Date: Fri, 22 Jun 2012 19:16:46 -0000 X-URL: http://tools.ietf.org/core/ X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/core/trac/ticket/224#comment:3 Message-ID: <066.33ac13bfb60c35c2d6231853372284b2@trac.tools.ietf.org> References: <051.7d125c7c9032a5950eb61f480c23f91a@trac.tools.ietf.org> X-Trac-Ticket-ID: 224 In-Reply-To: <051.7d125c7c9032a5950eb61f480c23f91a@trac.tools.ietf.org> X-SA-Exim-Connect-IP: 127.0.0.1 X-SA-Exim-Rcpt-To: draft-ietf-core-observe@tools.ietf.org, cabo@tzi.org, hartke@tzi.org, core@ietf.org X-SA-Exim-Mail-From: trac+core@trac.tools.ietf.org X-SA-Exim-Scanned: No (on grenache.tools.ietf.org); SAEximRunCond expanded to false Resent-To: Resent-Message-Id: <20120622191650.DAA5611E807F@ietfa.amsl.com> Resent-Date: Fri, 22 Jun 2012 12:16:50 -0700 (PDT) Resent-From: trac+core@trac.tools.ietf.org Cc: core@ietf.org Subject: Re: [core] #224: Clarify the concept of end-point X-BeenThere: core@ietf.org X-Mailman-Version: 2.1.12 Reply-To: trac+core@trac.tools.ietf.org List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 Jun 2012 19:16:51 -0000 #224: Clarify the concept of end-point Changes (by hartke@…): * owner: draft-ietf-core-coap@… => draft-ietf-core-observe@… * priority: major => minor * version: coap-09 => observe-05 * component: coap => observe Comment: Done in -coap-10. The remaining action items relate to -observe. -- -----------------------------+---------------------------------------- Reporter: cabo@… | Owner: draft-ietf-core-observe@… Type: editorial | Status: new Priority: minor | Milestone: post-WGLC-1 Component: observe | Version: observe-05 Severity: In WG Last Call | Resolution: Keywords: | -----------------------------+---------------------------------------- Ticket URL: core From trac+core@trac.tools.ietf.org Fri Jun 22 12:22:32 2012 Return-Path: X-Original-To: core@ietfa.amsl.com Delivered-To: core@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0A07C21F8604 for ; Fri, 22 Jun 2012 12:22:32 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -101.887 X-Spam-Level: X-Spam-Status: No, score=-101.887 tagged_above=-999 required=5 tests=[AWL=0.712, 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 c8CLjtOcXoqK for ; Fri, 22 Jun 2012 12:22:31 -0700 (PDT) Received: from grenache.tools.ietf.org (grenache.tools.ietf.org [77.72.230.30]) by ietfa.amsl.com (Postfix) with ESMTP id 73D0721F8602 for ; Fri, 22 Jun 2012 12:22:31 -0700 (PDT) Received: from localhost ([127.0.0.1]:34235 helo=grenache.tools.ietf.org ident=www-data) by grenache.tools.ietf.org with esmtp (Exim 4.77) (envelope-from ) id 1Si9R5-00066P-2o; Fri, 22 Jun 2012 21:22:27 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit From: "core issue tracker" X-Trac-Version: 0.12.2 Precedence: bulk Auto-Submitted: auto-generated X-Mailer: Trac 0.12.2, by Edgewall Software To: hartke@tzi.org, zach@sensinode.com X-Trac-Project: core Date: Fri, 22 Jun 2012 19:22:26 -0000 X-URL: http://tools.ietf.org/core/ X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/core/trac/ticket/228#comment:2 Message-ID: <068.0327b8b0217619a7b391337915b3cb45@trac.tools.ietf.org> References: <053.14c1896b5eae7fbbc5ad1a8f77d383ce@trac.tools.ietf.org> X-Trac-Ticket-ID: 228 In-Reply-To: <053.14c1896b5eae7fbbc5ad1a8f77d383ce@trac.tools.ietf.org> X-SA-Exim-Connect-IP: 127.0.0.1 X-SA-Exim-Rcpt-To: hartke@tzi.org, zach@sensinode.com, core@ietf.org X-SA-Exim-Mail-From: trac+core@trac.tools.ietf.org X-SA-Exim-Scanned: No (on grenache.tools.ietf.org); SAEximRunCond expanded to false Cc: core@ietf.org Subject: Re: [core] #228: Proxying of multicast requests X-BeenThere: core@ietf.org X-Mailman-Version: 2.1.12 Reply-To: trac+core@trac.tools.ietf.org List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 Jun 2012 19:22:32 -0000 #228: Proxying of multicast requests Changes (by hartke@…): * status: new => closed * resolution: => fixed Comment: Done in coap-10. -- ----------------------------------+-------------------------- Reporter: hartke@… | Owner: hartke@… Type: protocol enhancement | Status: closed Priority: minor | Milestone: post-WGLC-1 Component: coap | Version: coap-09 Severity: In WG Last Call | Resolution: fixed Keywords: | ----------------------------------+-------------------------- Ticket URL: core From trac+core@trac.tools.ietf.org Fri Jun 22 12:27:35 2012 Return-Path: X-Original-To: core@ietfa.amsl.com Delivered-To: core@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0FA7B21F8666 for ; Fri, 22 Jun 2012 12:27:35 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -101.908 X-Spam-Level: X-Spam-Status: No, score=-101.908 tagged_above=-999 required=5 tests=[AWL=0.691, 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 DvdOFxq9bjkD for ; Fri, 22 Jun 2012 12:27:34 -0700 (PDT) Received: from grenache.tools.ietf.org (grenache.tools.ietf.org [77.72.230.30]) by ietfa.amsl.com (Postfix) with ESMTP id 52AEB21F8655 for ; Fri, 22 Jun 2012 12:27:34 -0700 (PDT) Received: from localhost ([127.0.0.1]:34396 helo=grenache.tools.ietf.org ident=www-data) by grenache.tools.ietf.org with esmtp (Exim 4.77) (envelope-from ) id 1Si9Vw-00066a-G0; Fri, 22 Jun 2012 21:27:28 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit From: "core issue tracker" X-Trac-Version: 0.12.2 Precedence: bulk Auto-Submitted: auto-generated X-Mailer: Trac 0.12.2, by Edgewall Software To: draft-ietf-core-coap@tools.ietf.org, cabo@tzi.org, zach@sensinode.com, fluffy@cisco.com, hartke@tzi.org X-Trac-Project: core Date: Fri, 22 Jun 2012 19:27:28 -0000 X-URL: http://tools.ietf.org/core/ X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/core/trac/ticket/230#comment:6 Message-ID: <068.c5a9c73538201d701933bc93ab671418@trac.tools.ietf.org> References: <053.8673136dcb3a579ebc337cc52e97888a@trac.tools.ietf.org> X-Trac-Ticket-ID: 230 In-Reply-To: <053.8673136dcb3a579ebc337cc52e97888a@trac.tools.ietf.org> X-SA-Exim-Connect-IP: 127.0.0.1 X-SA-Exim-Rcpt-To: draft-ietf-core-coap@tools.ietf.org, cabo@tzi.org, zach@sensinode.com, fluffy@cisco.com, hartke@tzi.org, core@ietf.org X-SA-Exim-Mail-From: trac+core@trac.tools.ietf.org X-SA-Exim-Scanned: No (on grenache.tools.ietf.org); SAEximRunCond expanded to false Resent-To: Resent-Message-Id: <20120622192734.52AEB21F8655@ietfa.amsl.com> Resent-Date: Fri, 22 Jun 2012 12:27:34 -0700 (PDT) Resent-From: trac+core@trac.tools.ietf.org Cc: core@ietf.org Subject: Re: [core] #230: Multiple Location options need to be processed as a unit X-BeenThere: core@ietf.org X-Mailman-Version: 2.1.12 Reply-To: trac+core@trac.tools.ietf.org List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 Jun 2012 19:27:35 -0000 #230: Multiple Location options need to be processed as a unit Comment (by hartke@…): I think the option numbers reserved for future Location-* use should be less than the options numbers of Location-Path and Location-Query. Otherwise an implementation needs to perform two passes over the list of options to interpret the indicated location URI. -- -----------------------------+------------------------------------- Reporter: hartke@… | Owner: draft-ietf-core-coap@… Type: protocol defect | Status: new Priority: minor | Milestone: post-WGLC-1 Component: coap | Version: coap-09 Severity: In WG Last Call | Resolution: Keywords: | -----------------------------+------------------------------------- Ticket URL: core From trac+core@trac.tools.ietf.org Mon Jun 25 10:09:14 2012 Return-Path: X-Original-To: core@ietfa.amsl.com Delivered-To: core@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 029EC21F84C8 for ; Mon, 25 Jun 2012 10:09:14 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -101.928 X-Spam-Level: X-Spam-Status: No, score=-101.928 tagged_above=-999 required=5 tests=[AWL=0.671, 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 DS6UNZQFx-NE for ; Mon, 25 Jun 2012 10:09:13 -0700 (PDT) Received: from grenache.tools.ietf.org (grenache.tools.ietf.org [77.72.230.30]) by ietfa.amsl.com (Postfix) with ESMTP id 5998E21F84B2 for ; Mon, 25 Jun 2012 10:09:13 -0700 (PDT) Received: from localhost ([127.0.0.1]:51172 helo=grenache.tools.ietf.org ident=www-data) by grenache.tools.ietf.org with esmtp (Exim 4.77) (envelope-from ) id 1SjCmW-0008C5-NX; Mon, 25 Jun 2012 19:08:56 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit From: "core issue tracker" X-Trac-Version: 0.12.2 Precedence: bulk Auto-Submitted: auto-generated X-Mailer: Trac 0.12.2, by Edgewall Software To: cabo@tzi.org, angelo@castellani.net, zach@sensinode.com X-Trac-Project: core Date: Mon, 25 Jun 2012 17:08:56 -0000 X-URL: http://tools.ietf.org/core/ X-Trac-Ticket-URL: http://tools.ietf.org/wg/core/trac/ticket/201#comment:7 Message-ID: <066.69b8ddc68ac08b1d395a1df0d10dfc05@trac.tools.ietf.org> References: <051.b90ea2a4caf57d34ab6abdaf3603301a@trac.tools.ietf.org> X-Trac-Ticket-ID: 201 In-Reply-To: <051.b90ea2a4caf57d34ab6abdaf3603301a@trac.tools.ietf.org> X-SA-Exim-Connect-IP: 127.0.0.1 X-SA-Exim-Rcpt-To: cabo@tzi.org, angelo@castellani.net, zach@sensinode.com, core@ietf.org X-SA-Exim-Mail-From: trac+core@trac.tools.ietf.org X-SA-Exim-Scanned: No (on grenache.tools.ietf.org); SAEximRunCond expanded to false Cc: core@ietf.org Subject: Re: [core] #201: Clarify use of retransmission window for duplicate detection X-BeenThere: core@ietf.org X-Mailman-Version: 2.1.12 Reply-To: trac+core@trac.tools.ietf.org List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Jun 2012 17:09:14 -0000 #201: Clarify use of retransmission window for duplicate detection Comment (by cabo@…): Text in section 6 of coap-misc-18, to be moved over to core-coap. -- -----------------------------+--------------------- Reporter: cabo@… | Owner: cabo@… Type: editorial | Status: new Priority: minor | Milestone: Component: coap | Version: Severity: In WG Last Call | Resolution: Keywords: | -----------------------------+--------------------- Ticket URL: core From trac+core@trac.tools.ietf.org Mon Jun 25 10:10:12 2012 Return-Path: X-Original-To: core@ietfa.amsl.com Delivered-To: core@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5D13821F84E1 for ; Mon, 25 Jun 2012 10:10:12 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -101.948 X-Spam-Level: X-Spam-Status: No, score=-101.948 tagged_above=-999 required=5 tests=[AWL=0.651, 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 t1OVQiujEq06 for ; Mon, 25 Jun 2012 10:10:12 -0700 (PDT) Received: from grenache.tools.ietf.org (grenache.tools.ietf.org [77.72.230.30]) by ietfa.amsl.com (Postfix) with ESMTP id CC93021F84DF for ; Mon, 25 Jun 2012 10:10:11 -0700 (PDT) Received: from localhost ([127.0.0.1]:51282 helo=grenache.tools.ietf.org ident=www-data) by grenache.tools.ietf.org with esmtp (Exim 4.77) (envelope-from ) id 1SjCnh-0007oL-Ky; Mon, 25 Jun 2012 19:10:09 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit From: "core issue tracker" X-Trac-Version: 0.12.2 Precedence: bulk Auto-Submitted: auto-generated X-Mailer: Trac 0.12.2, by Edgewall Software To: cabo@tzi.org, zach@sensinode.com X-Trac-Project: core Date: Mon, 25 Jun 2012 17:10:09 -0000 X-URL: http://tools.ietf.org/core/ X-Trac-Ticket-URL: http://tools.ietf.org/wg/core/trac/ticket/202#comment:3 Message-ID: <066.f84f9bea488d2c27c48d93c18e668747@trac.tools.ietf.org> References: <051.e7fbc0f0f5736d305a309a9e8d0cd924@trac.tools.ietf.org> X-Trac-Ticket-ID: 202 In-Reply-To: <051.e7fbc0f0f5736d305a309a9e8d0cd924@trac.tools.ietf.org> X-SA-Exim-Connect-IP: 127.0.0.1 X-SA-Exim-Rcpt-To: cabo@tzi.org, zach@sensinode.com, core@ietf.org X-SA-Exim-Mail-From: trac+core@trac.tools.ietf.org X-SA-Exim-Scanned: No (on grenache.tools.ietf.org); SAEximRunCond expanded to false Cc: core@ietf.org Subject: Re: [core] #202: Remove the 270 byte artificial limit X-BeenThere: core@ietf.org X-Mailman-Version: 2.1.12 Reply-To: trac+core@trac.tools.ietf.org List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Jun 2012 17:10:12 -0000 #202: Remove the 270 byte artificial limit Comment (by cabo@…): Text in section 2.1 of coap-misc-18, to be moved over to core-coap. -- -----------------------------+--------------------- Reporter: cabo@… | Owner: cabo@… Type: protocol defect | Status: new Priority: minor | Milestone: Component: coap | Version: Severity: In WG Last Call | Resolution: Keywords: | -----------------------------+--------------------- Ticket URL: core From trac+core@trac.tools.ietf.org Mon Jun 25 10:11:10 2012 Return-Path: X-Original-To: core@ietfa.amsl.com Delivered-To: core@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6898721F84DF for ; Mon, 25 Jun 2012 10:11:10 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -101.966 X-Spam-Level: X-Spam-Status: No, score=-101.966 tagged_above=-999 required=5 tests=[AWL=0.633, 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 CerAJ4z2q49p for ; Mon, 25 Jun 2012 10:11:09 -0700 (PDT) Received: from grenache.tools.ietf.org (grenache.tools.ietf.org [77.72.230.30]) by ietfa.amsl.com (Postfix) with ESMTP id C423621F84B3 for ; Mon, 25 Jun 2012 10:11:09 -0700 (PDT) Received: from localhost ([127.0.0.1]:51362 helo=grenache.tools.ietf.org ident=www-data) by grenache.tools.ietf.org with esmtp (Exim 4.77) (envelope-from ) id 1SjCoZ-0008Hh-1H; Mon, 25 Jun 2012 19:11:03 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit From: "core issue tracker" X-Trac-Version: 0.12.2 Precedence: bulk Auto-Submitted: auto-generated X-Mailer: Trac 0.12.2, by Edgewall Software To: draft-ietf-core-coap@tools.ietf.org, fluffy@cisco.com, hartke@tzi.org, cabo@tzi.org X-Trac-Project: core Date: Mon, 25 Jun 2012 17:11:03 -0000 X-URL: http://tools.ietf.org/core/ X-Trac-Ticket-URL: http://tools.ietf.org/wg/core/trac/ticket/214#comment:3 Message-ID: <066.93865ad429b44d3d6fe3c2020b3149ee@trac.tools.ietf.org> References: <051.09186ada57b912f27c3147c188e4fd71@trac.tools.ietf.org> X-Trac-Ticket-ID: 214 In-Reply-To: <051.09186ada57b912f27c3147c188e4fd71@trac.tools.ietf.org> X-SA-Exim-Connect-IP: 127.0.0.1 X-SA-Exim-Rcpt-To: draft-ietf-core-coap@tools.ietf.org, fluffy@cisco.com, hartke@tzi.org, cabo@tzi.org, core@ietf.org X-SA-Exim-Mail-From: trac+core@trac.tools.ietf.org X-SA-Exim-Scanned: No (on grenache.tools.ietf.org); SAEximRunCond expanded to false Resent-To: Resent-Message-Id: <20120625171109.C423621F84B3@ietfa.amsl.com> Resent-Date: Mon, 25 Jun 2012 10:11:09 -0700 (PDT) Resent-From: trac+core@trac.tools.ietf.org Cc: core@ietf.org Subject: Re: [core] #214: Adopt vendor-defined option into core-coap X-BeenThere: core@ietf.org X-Mailman-Version: 2.1.12 Reply-To: trac+core@trac.tools.ietf.org List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Jun 2012 17:11:10 -0000 #214: Adopt vendor-defined option into core-coap Comment (by cabo@…): Text in section 3 of coap-misc-18, to be moved over to core-coap. -- ----------------------------------+------------------------------------- Reporter: cabo@… | Owner: draft-ietf-core-coap@… Type: protocol enhancement | Status: new Priority: minor | Milestone: post-WGLC-1 Component: coap | Version: coap-09 Severity: In WG Last Call | Resolution: Keywords: | ----------------------------------+------------------------------------- Ticket URL: core From trac+core@trac.tools.ietf.org Mon Jun 25 10:14:18 2012 Return-Path: X-Original-To: core@ietfa.amsl.com Delivered-To: core@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 686CF21F8549 for ; Mon, 25 Jun 2012 10:14:18 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -101.983 X-Spam-Level: X-Spam-Status: No, score=-101.983 tagged_above=-999 required=5 tests=[AWL=0.616, 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 BMfUvYi6Kfgx for ; Mon, 25 Jun 2012 10:14:18 -0700 (PDT) Received: from grenache.tools.ietf.org (grenache.tools.ietf.org [77.72.230.30]) by ietfa.amsl.com (Postfix) with ESMTP id B560421F8483 for ; Mon, 25 Jun 2012 10:14:17 -0700 (PDT) Received: from localhost ([127.0.0.1]:51424 helo=grenache.tools.ietf.org ident=www-data) by grenache.tools.ietf.org with esmtp (Exim 4.77) (envelope-from ) id 1SjCre-0006IU-Pn; Mon, 25 Jun 2012 19:14:14 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit From: "core issue tracker" X-Trac-Version: 0.12.2 Precedence: bulk Auto-Submitted: auto-generated X-Mailer: Trac 0.12.2, by Edgewall Software To: hartke@tzi.org, zach@sensinode.com, angelo@castellani.net, cabo@tzi.org X-Trac-Project: core Date: Mon, 25 Jun 2012 17:14:14 -0000 X-URL: http://tools.ietf.org/core/ X-Trac-Ticket-URL: http://tools.ietf.org/wg/core/trac/ticket/238#comment:5 Message-ID: <066.713baff6d63498803a9378c553be3c5d@trac.tools.ietf.org> References: <051.6e14fd2778cd6bb461ee0489bd1726db@trac.tools.ietf.org> X-Trac-Ticket-ID: 238 In-Reply-To: <051.6e14fd2778cd6bb461ee0489bd1726db@trac.tools.ietf.org> X-SA-Exim-Connect-IP: 127.0.0.1 X-SA-Exim-Rcpt-To: hartke@tzi.org, zach@sensinode.com, angelo@castellani.net, cabo@tzi.org, core@ietf.org X-SA-Exim-Mail-From: trac+core@trac.tools.ietf.org X-SA-Exim-Scanned: No (on grenache.tools.ietf.org); SAEximRunCond expanded to false Cc: core@ietf.org Subject: Re: [core] #238: Proxy terminology X-BeenThere: core@ietf.org X-Mailman-Version: 2.1.12 Reply-To: trac+core@trac.tools.ietf.org List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Jun 2012 17:14:18 -0000 #238: Proxy terminology Comment (by cabo@…): Section 10 now (coap-10) has a single instance pf "cross-protocol proxying" (plus one in the heading). Hence, the abbreviation is not introduced. Fine? -- -----------------------------+-------------------------- Reporter: cabo@… | Owner: hartke@… Type: editorial | Status: new Priority: minor | Milestone: post-WGLC-1 Component: coap | Version: coap-09 Severity: In WG Last Call | Resolution: Keywords: | -----------------------------+-------------------------- Ticket URL: core From trac+core@trac.tools.ietf.org Mon Jun 25 10:27:32 2012 Return-Path: X-Original-To: core@ietfa.amsl.com Delivered-To: core@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5434221F845F for ; Mon, 25 Jun 2012 10:27:32 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -101.999 X-Spam-Level: X-Spam-Status: No, score=-101.999 tagged_above=-999 required=5 tests=[AWL=0.600, 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 z8dEQbUFAUX5 for ; Mon, 25 Jun 2012 10:27:30 -0700 (PDT) Received: from grenache.tools.ietf.org (grenache.tools.ietf.org [77.72.230.30]) by ietfa.amsl.com (Postfix) with ESMTP id 4B87021F845D for ; Mon, 25 Jun 2012 10:27:30 -0700 (PDT) Received: from localhost ([127.0.0.1]:52259 helo=grenache.tools.ietf.org ident=www-data) by grenache.tools.ietf.org with esmtp (Exim 4.77) (envelope-from ) id 1SjD4P-0007rm-DK; Mon, 25 Jun 2012 19:27:25 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit From: "core issue tracker" X-Trac-Version: 0.12.2 Precedence: bulk Auto-Submitted: auto-generated X-Mailer: Trac 0.12.2, by Edgewall Software To: cabo@tzi.org, zach@sensinode.com X-Trac-Project: core Date: Mon, 25 Jun 2012 17:27:25 -0000 X-URL: http://tools.ietf.org/core/ X-Trac-Ticket-URL: /ticket/239#comment:2 Message-ID: <066.49de685654cbe6e2cdb630742f977d4d@trac.tools.ietf.org> References: <051.0d383e737d0490ef1635d6073da7c1c7@trac.tools.ietf.org> X-Trac-Ticket-ID: 239 In-Reply-To: <051.0d383e737d0490ef1635d6073da7c1c7@trac.tools.ietf.org> X-SA-Exim-Connect-IP: 127.0.0.1 X-SA-Exim-Rcpt-To: cabo@tzi.org, zach@sensinode.com, core@ietf.org X-SA-Exim-Mail-From: trac+core@trac.tools.ietf.org X-SA-Exim-Scanned: No (on grenache.tools.ietf.org); SAEximRunCond expanded to false Cc: core@ietf.org Subject: Re: [core] #239: Always reserve option delta 15 X-BeenThere: core@ietf.org X-Mailman-Version: 2.1.12 Reply-To: trac+core@trac.tools.ietf.org List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Jun 2012 17:27:32 -0000 #239: Always reserve option delta 15 Changes (by cabo@…): * status: new => closed * resolution: => fixed Comment: Fixed in [814]: Fix #239 -- -----------------------------+-------------------------- Reporter: cabo@… | Owner: cabo@… Type: other technical | Status: closed Priority: minor | Milestone: post-WGLC-1 Component: coap | Version: coap-09 Severity: In WG Last Call | Resolution: fixed Keywords: | -----------------------------+-------------------------- Ticket URL: core From internet-drafts@ietf.org Mon Jun 25 10:56:07 2012 Return-Path: X-Original-To: core@ietfa.amsl.com Delivered-To: core@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C4F8211E8085; Mon, 25 Jun 2012 10:56:07 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.508 X-Spam-Level: X-Spam-Status: No, score=-102.508 tagged_above=-999 required=5 tests=[AWL=0.091, 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 jVH8kQkKllrw; Mon, 25 Jun 2012 10:56:06 -0700 (PDT) Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E442021F8518; Mon, 25 Jun 2012 10:56:02 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable From: internet-drafts@ietf.org To: i-d-announce@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 4.21 Message-ID: <20120625175602.28573.63347.idtracker@ietfa.amsl.com> Date: Mon, 25 Jun 2012 10:56:02 -0700 Cc: core@ietf.org Subject: [core] I-D Action: draft-ietf-core-coap-10.txt X-BeenThere: core@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Jun 2012 17:56:08 -0000 A New Internet-Draft is available from the on-line Internet-Drafts director= ies. This draft is a work item of the Constrained RESTful Environments Working = Group of the IETF. Title : Constrained Application Protocol (CoAP) Author(s) : Zach Shelby Klaus Hartke Carsten Bormann Brian Frank Filename : draft-ietf-core-coap-10.txt Pages : 95 Date : 2012-06-25 Abstract: The Constrained Application Protocol (CoAP) is a specialized web transfer protocol for use with constrained nodes and constrained (e.g., low-power, lossy) networks. The nodes often have 8-bit microcontrollers with small amounts of ROM and RAM, while constrained networks such as 6LoWPAN often have high packet error rates and a typical throughput of 10s of kbit/s. The protocol is designed for machine-to-machine (M2M) applications such as smart energy and building automation. CoAP provides a request/response interaction model between application end-points, supports built-in discovery of services and resources, and includes key concepts of the Web such as URIs and Internet media types. CoAP easily interfaces with HTTP for integration with the Web while meeting specialized requirements such as multicast support, very low overhead and simplicity for constrained environments. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-core-coap There's also a htmlized version available at: http://tools.ietf.org/html/draft-ietf-core-coap-10 A diff from previous version is available at: http://tools.ietf.org/rfcdiff?url2=3Ddraft-ietf-core-coap-10 Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From cabo@tzi.org Mon Jun 25 11:00:22 2012 Return-Path: X-Original-To: core@ietfa.amsl.com Delivered-To: core@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2847A11E8079 for ; Mon, 25 Jun 2012 11:00:22 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -106.461 X-Spam-Level: X-Spam-Status: No, score=-106.461 tagged_above=-999 required=5 tests=[AWL=-0.212, 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 JmMcadgEqNw5 for ; Mon, 25 Jun 2012 11:00:21 -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 AAF3921F851C for ; Mon, 25 Jun 2012 11:00: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.3/8.14.3) with ESMTP id q5PI07J3012968 for ; Mon, 25 Jun 2012 20:00:07 +0200 (CEST) Received: from [192.168.217.117] (p54894D11.dip.t-dialin.net [84.137.77.17]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id 518A71F; Mon, 25 Jun 2012 20:00:07 +0200 (CEST) From: Carsten Bormann Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Date: Mon, 25 Jun 2012 20:00:06 +0200 To: "core@ietf.org WG" Message-Id: <8906C11D-58DA-46AA-8152-F70583543B81@tzi.org> Mime-Version: 1.0 (Apple Message framework v1278) X-Mailer: Apple Mail (2.1278) Subject: [core] core-coap-10, coap-misc-18, and a new draft on congestion control principles X-BeenThere: core@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Jun 2012 18:00:22 -0000 draft-ietf-core-coap-10, draft-bormann-coap-misc-18, and a new draft-bormann-core-congestion-control-00 havee been posted. This is a milestone on the road to fully resolving the WGLC comments. Still to do are: - Check coap-misc 2.1 (resolving #202), 3 (#214), and 6 (#201) and, if = we like them, integrate all this text (and the appropriate parts of 7) into core-coap. - Check core-congestion-control-00 and, if we like it, perform the changes indicated in the drafy in core-coap and try to resolve #215 in the process. - #241: We need to come to a conclusion as to what we do about the proxy-elective class of options, and if we need the additional bit for cache key indication. - (authors:) complete more editorial comments. Other discussion points: - #230: Are we done with this one? (Last 2 comments on ticket.) - #216 -- which scopes do we actually want to recommend to use? Do we expect all CoAP nodes to listen to all scopes? - Does core-congestion-control stay its own draft or do we integrate it as a "congestion considerations" section into core-coap? [This author would be happier to make this a stand-alone = informational.] - any work remaining on the packet size text? - block, observe... The usual delta URIs: http://tools.ietf.org/rfcdiff?url2=3Ddraft-ietf-core-coap-10.txt http://tools.ietf.org/rfcdiff?url2=3Ddraft-bormann-coap-misc-18.txt New: http://tools.ietf.org/html/draft-bormann-core-congestion-control-00 Gr=FC=DFe, Carsten From trac+core@trac.tools.ietf.org Mon Jun 25 13:11:22 2012 Return-Path: X-Original-To: core@ietfa.amsl.com Delivered-To: core@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E8E9711E80A0 for ; Mon, 25 Jun 2012 13:11:22 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.014 X-Spam-Level: X-Spam-Status: No, score=-102.014 tagged_above=-999 required=5 tests=[AWL=0.585, 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 IGCwvwEwcZyP for ; Mon, 25 Jun 2012 13:11:17 -0700 (PDT) Received: from grenache.tools.ietf.org (grenache.tools.ietf.org [77.72.230.30]) by ietfa.amsl.com (Postfix) with ESMTP id 3221A11E808C for ; Mon, 25 Jun 2012 13:11:17 -0700 (PDT) Received: from localhost ([127.0.0.1]:34884 helo=grenache.tools.ietf.org ident=www-data) by grenache.tools.ietf.org with esmtp (Exim 4.77) (envelope-from ) id 1SjFcd-0001Jx-Gf; Mon, 25 Jun 2012 22:10:55 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit From: "core issue tracker" X-Trac-Version: 0.12.2 Precedence: bulk Auto-Submitted: auto-generated X-Mailer: Trac 0.12.2, by Edgewall Software To: cabo@tzi.org, angelo@castellani.net, zach@sensinode.com, hartke@tzi.org X-Trac-Project: core Date: Mon, 25 Jun 2012 20:10:55 -0000 X-URL: http://tools.ietf.org/core/ X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/core/trac/ticket/201#comment:8 Message-ID: <066.3e8bbf94da1cc538cfb8052c8c3822d9@trac.tools.ietf.org> References: <051.b90ea2a4caf57d34ab6abdaf3603301a@trac.tools.ietf.org> X-Trac-Ticket-ID: 201 In-Reply-To: <051.b90ea2a4caf57d34ab6abdaf3603301a@trac.tools.ietf.org> X-SA-Exim-Connect-IP: 127.0.0.1 X-SA-Exim-Rcpt-To: cabo@tzi.org, angelo@castellani.net, zach@sensinode.com, hartke@tzi.org, core@ietf.org X-SA-Exim-Mail-From: trac+core@trac.tools.ietf.org X-SA-Exim-Scanned: No (on grenache.tools.ietf.org); SAEximRunCond expanded to false Cc: core@ietf.org Subject: Re: [core] #201: Clarify use of retransmission window for duplicate detection X-BeenThere: core@ietf.org X-Mailman-Version: 2.1.12 Reply-To: trac+core@trac.tools.ietf.org List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Jun 2012 20:11:23 -0000 #201: Clarify use of retransmission window for duplicate detection Changes (by hartke@…): * version: => coap-09 * milestone: => post-WGLC-1 -- -----------------------------+-------------------------- Reporter: cabo@… | Owner: cabo@… Type: editorial | Status: new Priority: minor | Milestone: post-WGLC-1 Component: coap | Version: coap-09 Severity: In WG Last Call | Resolution: Keywords: | -----------------------------+-------------------------- Ticket URL: core From trac+core@trac.tools.ietf.org Mon Jun 25 13:11:23 2012 Return-Path: X-Original-To: core@ietfa.amsl.com Delivered-To: core@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 00BDE11E808C for ; Mon, 25 Jun 2012 13:11:23 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.029 X-Spam-Level: X-Spam-Status: No, score=-102.029 tagged_above=-999 required=5 tests=[AWL=0.570, 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 joWSe2V34rJU for ; Mon, 25 Jun 2012 13:11:19 -0700 (PDT) Received: from grenache.tools.ietf.org (grenache.tools.ietf.org [77.72.230.30]) by ietfa.amsl.com (Postfix) with ESMTP id CF37511E8093 for ; Mon, 25 Jun 2012 13:11:18 -0700 (PDT) Received: from localhost ([127.0.0.1]:34897 helo=grenache.tools.ietf.org ident=www-data) by grenache.tools.ietf.org with esmtp (Exim 4.77) (envelope-from ) id 1SjFcy-0008HU-TJ; Mon, 25 Jun 2012 22:11:16 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit From: "core issue tracker" X-Trac-Version: 0.12.2 Precedence: bulk Auto-Submitted: auto-generated X-Mailer: Trac 0.12.2, by Edgewall Software To: cabo@tzi.org, zach@sensinode.com, hartke@tzi.org X-Trac-Project: core Date: Mon, 25 Jun 2012 20:11:16 -0000 X-URL: http://tools.ietf.org/core/ X-Trac-Ticket-URL: http://tools.ietf.org/wg/core/trac/ticket/202#comment:4 Message-ID: <066.943ecd92aa425ba96d2c85cf75db2637@trac.tools.ietf.org> References: <051.e7fbc0f0f5736d305a309a9e8d0cd924@trac.tools.ietf.org> X-Trac-Ticket-ID: 202 In-Reply-To: <051.e7fbc0f0f5736d305a309a9e8d0cd924@trac.tools.ietf.org> X-SA-Exim-Connect-IP: 127.0.0.1 X-SA-Exim-Rcpt-To: cabo@tzi.org, zach@sensinode.com, hartke@tzi.org, core@ietf.org X-SA-Exim-Mail-From: trac+core@trac.tools.ietf.org X-SA-Exim-Scanned: No (on grenache.tools.ietf.org); SAEximRunCond expanded to false Cc: core@ietf.org Subject: Re: [core] #202: Remove the 270 byte artificial limit X-BeenThere: core@ietf.org X-Mailman-Version: 2.1.12 Reply-To: trac+core@trac.tools.ietf.org List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Jun 2012 20:11:23 -0000 #202: Remove the 270 byte artificial limit Changes (by hartke@…): * version: => coap-09 * milestone: => post-WGLC-1 -- -----------------------------+-------------------------- Reporter: cabo@… | Owner: cabo@… Type: protocol defect | Status: new Priority: minor | Milestone: post-WGLC-1 Component: coap | Version: coap-09 Severity: In WG Last Call | Resolution: Keywords: | -----------------------------+-------------------------- Ticket URL: core From trac+core@trac.tools.ietf.org Mon Jun 25 13:45:15 2012 Return-Path: X-Original-To: core@ietfa.amsl.com Delivered-To: core@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 56AB511E8093 for ; Mon, 25 Jun 2012 13:45:15 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.043 X-Spam-Level: X-Spam-Status: No, score=-102.043 tagged_above=-999 required=5 tests=[AWL=0.556, 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 mFSUvnvO8wqj for ; Mon, 25 Jun 2012 13:45:14 -0700 (PDT) Received: from grenache.tools.ietf.org (grenache.tools.ietf.org [77.72.230.30]) by ietfa.amsl.com (Postfix) with ESMTP id C373611E808E for ; Mon, 25 Jun 2012 13:45:14 -0700 (PDT) Received: from localhost ([127.0.0.1]:34911 helo=grenache.tools.ietf.org ident=www-data) by grenache.tools.ietf.org with esmtp (Exim 4.77) (envelope-from ) id 1SjFdJ-0006q5-Kj; Mon, 25 Jun 2012 22:11:37 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit From: "core issue tracker" X-Trac-Version: 0.12.2 Precedence: bulk Auto-Submitted: auto-generated X-Mailer: Trac 0.12.2, by Edgewall Software To: draft-ietf-core-observe@tools.ietf.org, cabo@tzi.org, hartke@tzi.org X-Trac-Project: core Date: Mon, 25 Jun 2012 20:11:37 -0000 X-URL: http://tools.ietf.org/core/ X-Trac-Ticket-URL: http://tools.ietf.org/wg/core/trac/ticket/204#comment:3 Message-ID: <066.2a0f6abc569d1158b7bf1b77e0102ce4@trac.tools.ietf.org> References: <051.7d477dcf63d5a27be6104f253d5fe611@trac.tools.ietf.org> X-Trac-Ticket-ID: 204 In-Reply-To: <051.7d477dcf63d5a27be6104f253d5fe611@trac.tools.ietf.org> X-SA-Exim-Connect-IP: 127.0.0.1 X-SA-Exim-Rcpt-To: draft-ietf-core-observe@tools.ietf.org, cabo@tzi.org, hartke@tzi.org, core@ietf.org X-SA-Exim-Mail-From: trac+core@trac.tools.ietf.org X-SA-Exim-Scanned: No (on grenache.tools.ietf.org); SAEximRunCond expanded to false Resent-To: Resent-To: Resent-Message-Id: <20120625204514.C373611E808E@ietfa.amsl.com> Resent-Date: Mon, 25 Jun 2012 13:45:14 -0700 (PDT) Resent-From: trac+core@trac.tools.ietf.org Cc: core@ietf.org Subject: Re: [core] #204: Introduce a minimal version of Pledge X-BeenThere: core@ietf.org X-Mailman-Version: 2.1.12 Reply-To: trac+core@trac.tools.ietf.org List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Jun 2012 20:45:15 -0000 #204: Introduce a minimal version of Pledge Changes (by hartke@…): * version: => observe-05 * milestone: => post-WGLC-1 -- ----------------------------------+---------------------------------------- Reporter: cabo@… | Owner: draft-ietf-core-observe@… Type: protocol enhancement | Status: new Priority: major | Milestone: post-WGLC-1 Component: observe | Version: observe-05 Severity: In WG Last Call | Resolution: Keywords: | ----------------------------------+---------------------------------------- Ticket URL: core From trac+core@trac.tools.ietf.org Mon Jun 25 14:15:06 2012 Return-Path: X-Original-To: core@ietfa.amsl.com Delivered-To: core@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4036221F8589 for ; Mon, 25 Jun 2012 14:15:06 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.056 X-Spam-Level: X-Spam-Status: No, score=-102.056 tagged_above=-999 required=5 tests=[AWL=0.543, 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 vxgjCAqtTxxr for ; Mon, 25 Jun 2012 14:15:05 -0700 (PDT) Received: from grenache.tools.ietf.org (grenache.tools.ietf.org [77.72.230.30]) by ietfa.amsl.com (Postfix) with ESMTP id 9FD9C21F8585 for ; Mon, 25 Jun 2012 14:15:04 -0700 (PDT) Received: from localhost ([127.0.0.1]:34996 helo=grenache.tools.ietf.org ident=www-data) by grenache.tools.ietf.org with esmtp (Exim 4.77) (envelope-from ) id 1SjFej-0003ch-Tm; Mon, 25 Jun 2012 22:13:05 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit From: "core issue tracker" X-Trac-Version: 0.12.2 Precedence: bulk Auto-Submitted: auto-generated X-Mailer: Trac 0.12.2, by Edgewall Software To: draft-ietf-core-block@tools.ietf.org, hartke@tzi.org X-Trac-Project: core Date: Mon, 25 Jun 2012 20:13:05 -0000 X-URL: http://tools.ietf.org/core/ X-Trac-Ticket-URL: http://tools.ietf.org/wg/core/trac/ticket/210#comment:1 Message-ID: <066.a7a4aa04f213dabf31e0ebe07e57a561@trac.tools.ietf.org> References: <051.d904ee0bea6c59be24fc5a28e7e8cf18@trac.tools.ietf.org> X-Trac-Ticket-ID: 210 In-Reply-To: <051.d904ee0bea6c59be24fc5a28e7e8cf18@trac.tools.ietf.org> X-SA-Exim-Connect-IP: 127.0.0.1 X-SA-Exim-Rcpt-To: draft-ietf-core-block@tools.ietf.org, hartke@tzi.org, core@ietf.org X-SA-Exim-Mail-From: trac+core@trac.tools.ietf.org X-SA-Exim-Scanned: No (on grenache.tools.ietf.org); SAEximRunCond expanded to false Resent-To: Resent-To: Resent-Message-Id: <20120625211504.9FD9C21F8585@ietfa.amsl.com> Resent-Date: Mon, 25 Jun 2012 14:15:04 -0700 (PDT) Resent-From: trac+core@trac.tools.ietf.org Cc: core@ietf.org Subject: Re: [core] #210: Disentangle Block and Token X-BeenThere: core@ietf.org X-Mailman-Version: 2.1.12 Reply-To: trac+core@trac.tools.ietf.org List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Jun 2012 21:15:06 -0000 #210: Disentangle Block and Token Changes (by hartke@…): * version: => block-08 -- -----------------------------+-------------------------------------- Reporter: cabo@… | Owner: draft-ietf-core-block@… Type: protocol defect | Status: new Priority: major | Milestone: post-WGLC-1 Component: block | Version: block-08 Severity: In WG Last Call | Resolution: Keywords: | -----------------------------+-------------------------------------- Ticket URL: core From trac+core@trac.tools.ietf.org Mon Jun 25 14:45:14 2012 Return-Path: X-Original-To: core@ietfa.amsl.com Delivered-To: core@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B97C111E808E for ; Mon, 25 Jun 2012 14:45:14 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.069 X-Spam-Level: X-Spam-Status: No, score=-102.069 tagged_above=-999 required=5 tests=[AWL=0.530, 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 mSet8uNQcs62 for ; Mon, 25 Jun 2012 14:45:14 -0700 (PDT) Received: from grenache.tools.ietf.org (grenache.tools.ietf.org [77.72.230.30]) by ietfa.amsl.com (Postfix) with ESMTP id 2A16511E808C for ; Mon, 25 Jun 2012 14:45:14 -0700 (PDT) Received: from localhost ([127.0.0.1]:35017 helo=grenache.tools.ietf.org ident=www-data) by grenache.tools.ietf.org with esmtp (Exim 4.77) (envelope-from ) id 1SjFey-0000U6-Me; Mon, 25 Jun 2012 22:13:20 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit From: "core issue tracker" X-Trac-Version: 0.12.2 Precedence: bulk Auto-Submitted: auto-generated X-Mailer: Trac 0.12.2, by Edgewall Software To: draft-ietf-core-block@tools.ietf.org, hartke@tzi.org X-Trac-Project: core Date: Mon, 25 Jun 2012 20:13:20 -0000 X-URL: http://tools.ietf.org/core/ X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/core/trac/ticket/211#comment:1 Message-ID: <066.3db39c38afdfb363a0ce0b193dcb0ff6@trac.tools.ietf.org> References: <051.1e6287ce725552ffe1353c663f4c2d17@trac.tools.ietf.org> X-Trac-Ticket-ID: 211 In-Reply-To: <051.1e6287ce725552ffe1353c663f4c2d17@trac.tools.ietf.org> X-SA-Exim-Connect-IP: 127.0.0.1 X-SA-Exim-Rcpt-To: draft-ietf-core-block@tools.ietf.org, hartke@tzi.org, core@ietf.org X-SA-Exim-Mail-From: trac+core@trac.tools.ietf.org X-SA-Exim-Scanned: No (on grenache.tools.ietf.org); SAEximRunCond expanded to false Resent-To: Resent-To: Resent-Message-Id: <20120625214514.2A16511E808C@ietfa.amsl.com> Resent-Date: Mon, 25 Jun 2012 14:45:14 -0700 (PDT) Resent-From: trac+core@trac.tools.ietf.org Cc: core@ietf.org Subject: Re: [core] #211: Signal provisional responses (atomic Block1) in the response code X-BeenThere: core@ietf.org X-Mailman-Version: 2.1.12 Reply-To: trac+core@trac.tools.ietf.org List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Jun 2012 21:45:14 -0000 #211: Signal provisional responses (atomic Block1) in the response code Changes (by hartke@…): * version: => block-08 * milestone: => post-WGLC-1 -- -----------------------------+-------------------------------------- Reporter: cabo@… | Owner: draft-ietf-core-block@… Type: protocol defect | Status: new Priority: major | Milestone: post-WGLC-1 Component: block | Version: block-08 Severity: In WG Last Call | Resolution: Keywords: | -----------------------------+-------------------------------------- Ticket URL: core From trac+core@trac.tools.ietf.org Mon Jun 25 15:15:06 2012 Return-Path: X-Original-To: core@ietfa.amsl.com Delivered-To: core@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 35FCA21F8546 for ; Mon, 25 Jun 2012 15:15:06 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.081 X-Spam-Level: X-Spam-Status: No, score=-102.081 tagged_above=-999 required=5 tests=[AWL=0.518, 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 CqBdAN7EpoX2 for ; Mon, 25 Jun 2012 15:15:05 -0700 (PDT) Received: from grenache.tools.ietf.org (grenache.tools.ietf.org [77.72.230.30]) by ietfa.amsl.com (Postfix) with ESMTP id 6C9A921F853F for ; Mon, 25 Jun 2012 15:15:05 -0700 (PDT) Received: from localhost ([127.0.0.1]:34960 helo=grenache.tools.ietf.org ident=www-data) by grenache.tools.ietf.org with esmtp (Exim 4.77) (envelope-from ) id 1SjFe6-0006Qw-23; Mon, 25 Jun 2012 22:12:26 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit From: "core issue tracker" X-Trac-Version: 0.12.2 Precedence: bulk Auto-Submitted: auto-generated X-Mailer: Trac 0.12.2, by Edgewall Software To: draft-ietf-core-coap@tools.ietf.org, cabo@tzi.org, hartke@tzi.org X-Trac-Project: core Date: Mon, 25 Jun 2012 20:12:26 -0000 X-URL: http://tools.ietf.org/core/ X-Trac-Ticket-URL: http://tools.ietf.org/wg/core/trac/ticket/208#comment:2 Message-ID: <066.8fa1b493ba0e400a4b5bbdbe1239f749@trac.tools.ietf.org> References: <051.84365211a7b3ff2c11cb254d636ac5ca@trac.tools.ietf.org> X-Trac-Ticket-ID: 208 In-Reply-To: <051.84365211a7b3ff2c11cb254d636ac5ca@trac.tools.ietf.org> X-SA-Exim-Connect-IP: 127.0.0.1 X-SA-Exim-Rcpt-To: draft-ietf-core-coap@tools.ietf.org, cabo@tzi.org, hartke@tzi.org, core@ietf.org X-SA-Exim-Mail-From: trac+core@trac.tools.ietf.org X-SA-Exim-Scanned: No (on grenache.tools.ietf.org); SAEximRunCond expanded to false Resent-To: Resent-To: Resent-Message-Id: <20120625221505.6C9A921F853F@ietfa.amsl.com> Resent-Date: Mon, 25 Jun 2012 15:15:05 -0700 (PDT) Resent-From: trac+core@trac.tools.ietf.org Cc: core@ietf.org Subject: Re: [core] #208: Fix editing error in 5.10.2 X-BeenThere: core@ietf.org X-Mailman-Version: 2.1.12 Reply-To: trac+core@trac.tools.ietf.org List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Jun 2012 22:15:06 -0000 #208: Fix editing error in 5.10.2 Changes (by hartke@…): * version: => coap-09 -- -----------------------------+------------------------------------- Reporter: cabo@… | Owner: draft-ietf-core-coap@… Type: editorial | Status: closed Priority: minor | Milestone: post-WGLC-1 Component: coap | Version: coap-09 Severity: In WG Last Call | Resolution: fixed Keywords: | -----------------------------+------------------------------------- Ticket URL: core From trac+core@trac.tools.ietf.org Mon Jun 25 16:24:16 2012 Return-Path: X-Original-To: core@ietfa.amsl.com Delivered-To: core@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5B61911E80C9 for ; Mon, 25 Jun 2012 16:24:16 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.092 X-Spam-Level: X-Spam-Status: No, score=-102.092 tagged_above=-999 required=5 tests=[AWL=0.507, 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 UVyKSse0dVfn for ; Mon, 25 Jun 2012 16:24:15 -0700 (PDT) Received: from grenache.tools.ietf.org (grenache.tools.ietf.org [77.72.230.30]) by ietfa.amsl.com (Postfix) with ESMTP id BCEA211E80C1 for ; Mon, 25 Jun 2012 16:24:15 -0700 (PDT) Received: from localhost ([127.0.0.1]:34931 helo=grenache.tools.ietf.org ident=www-data) by grenache.tools.ietf.org with esmtp (Exim 4.77) (envelope-from ) id 1SjFdl-0007gC-3P; Mon, 25 Jun 2012 22:12:05 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit From: "core issue tracker" X-Trac-Version: 0.12.2 Precedence: bulk Auto-Submitted: auto-generated X-Mailer: Trac 0.12.2, by Edgewall Software To: draft-ietf-core-block@tools.ietf.org, hartke@tzi.org X-Trac-Project: core Date: Mon, 25 Jun 2012 20:12:05 -0000 X-URL: http://tools.ietf.org/core/ X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/core/trac/ticket/206#comment:1 Message-ID: <066.e69758586ff6c84699bee11d289c4f6b@trac.tools.ietf.org> References: <051.965a95dc46e1afb12f7d1a12aed61bdf@trac.tools.ietf.org> X-Trac-Ticket-ID: 206 In-Reply-To: <051.965a95dc46e1afb12f7d1a12aed61bdf@trac.tools.ietf.org> X-SA-Exim-Connect-IP: 127.0.0.1 X-SA-Exim-Rcpt-To: draft-ietf-core-block@tools.ietf.org, hartke@tzi.org, core@ietf.org X-SA-Exim-Mail-From: trac+core@trac.tools.ietf.org X-SA-Exim-Scanned: No (on grenache.tools.ietf.org); SAEximRunCond expanded to false Resent-To: Resent-To: Resent-Message-Id: <20120625232415.BCEA211E80C1@ietfa.amsl.com> Resent-Date: Mon, 25 Jun 2012 16:24:15 -0700 (PDT) Resent-From: trac+core@trac.tools.ietf.org Cc: core@ietf.org Subject: Re: [core] #206: Clarify that atomic Block1 transfers match per token *and* endpoint X-BeenThere: core@ietf.org X-Mailman-Version: 2.1.12 Reply-To: trac+core@trac.tools.ietf.org List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Jun 2012 23:24:16 -0000 #206: Clarify that atomic Block1 transfers match per token *and* endpoint Changes (by hartke@…): * version: => block-08 -- -----------------------------+-------------------------------------- Reporter: cabo@… | Owner: draft-ietf-core-block@… Type: editorial | Status: new Priority: major | Milestone: post-WGLC-1 Component: block | Version: block-08 Severity: In WG Last Call | Resolution: Keywords: | -----------------------------+-------------------------------------- Ticket URL: core From trac+core@trac.tools.ietf.org Mon Jun 25 16:24:16 2012 Return-Path: X-Original-To: core@ietfa.amsl.com Delivered-To: core@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A337B11E80C1 for ; Mon, 25 Jun 2012 16:24:16 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.103 X-Spam-Level: X-Spam-Status: No, score=-102.103 tagged_above=-999 required=5 tests=[AWL=0.496, 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 jDcoxI5l-0bk for ; Mon, 25 Jun 2012 16:24:16 -0700 (PDT) Received: from grenache.tools.ietf.org (grenache.tools.ietf.org [77.72.230.30]) by ietfa.amsl.com (Postfix) with ESMTP id 21FC511E80C0 for ; Mon, 25 Jun 2012 16:24:16 -0700 (PDT) Received: from localhost ([127.0.0.1]:34923 helo=grenache.tools.ietf.org ident=www-data) by grenache.tools.ietf.org with esmtp (Exim 4.77) (envelope-from ) id 1SjFda-0003xF-2T; Mon, 25 Jun 2012 22:11:54 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit From: "core issue tracker" X-Trac-Version: 0.12.2 Precedence: bulk Auto-Submitted: auto-generated X-Mailer: Trac 0.12.2, by Edgewall Software To: draft-ietf-core-block@tools.ietf.org, hartke@tzi.org X-Trac-Project: core Date: Mon, 25 Jun 2012 20:11:54 -0000 X-URL: http://tools.ietf.org/core/ X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/core/trac/ticket/205#comment:1 Message-ID: <066.227bbe5debf2e9edc362e8b2c369ca97@trac.tools.ietf.org> References: <051.9b5708494f8201a3ec752fc23da47723@trac.tools.ietf.org> X-Trac-Ticket-ID: 205 In-Reply-To: <051.9b5708494f8201a3ec752fc23da47723@trac.tools.ietf.org> X-SA-Exim-Connect-IP: 127.0.0.1 X-SA-Exim-Rcpt-To: draft-ietf-core-block@tools.ietf.org, hartke@tzi.org, core@ietf.org X-SA-Exim-Mail-From: trac+core@trac.tools.ietf.org X-SA-Exim-Scanned: No (on grenache.tools.ietf.org); SAEximRunCond expanded to false Resent-To: Resent-To: Resent-Message-Id: <20120625232416.21FC511E80C0@ietfa.amsl.com> Resent-Date: Mon, 25 Jun 2012 16:24:16 -0700 (PDT) Resent-From: trac+core@trac.tools.ietf.org Cc: core@ietf.org Subject: Re: [core] #205: Clarify that Size does not modify the request semantics beyond adding the size information X-BeenThere: core@ietf.org X-Mailman-Version: 2.1.12 Reply-To: trac+core@trac.tools.ietf.org List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Jun 2012 23:24:16 -0000 #205: Clarify that Size does not modify the request semantics beyond adding the size information Changes (by hartke@…): * version: => block-08 * milestone: => post-WGLC-1 -- -----------------------------+-------------------------------------- Reporter: cabo@… | Owner: draft-ietf-core-block@… Type: editorial | Status: new Priority: minor | Milestone: post-WGLC-1 Component: block | Version: block-08 Severity: In WG Last Call | Resolution: Keywords: | -----------------------------+-------------------------------------- Ticket URL: core From trac+core@trac.tools.ietf.org Mon Jun 25 16:45:04 2012 Return-Path: X-Original-To: core@ietfa.amsl.com Delivered-To: core@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CFCB111E80BB for ; Mon, 25 Jun 2012 16:45:04 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.092 X-Spam-Level: X-Spam-Status: No, score=-102.092 tagged_above=-999 required=5 tests=[AWL=0.463, BAYES_00=-2.599, DATE_IN_PAST_03_06=0.044, 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 7fcvvIr0ITHc for ; Mon, 25 Jun 2012 16:45:04 -0700 (PDT) Received: from grenache.tools.ietf.org (grenache.tools.ietf.org [77.72.230.30]) by ietfa.amsl.com (Postfix) with ESMTP id 4C0E911E808C for ; Mon, 25 Jun 2012 16:45:04 -0700 (PDT) Received: from localhost ([127.0.0.1]:35038 helo=grenache.tools.ietf.org ident=www-data) by grenache.tools.ietf.org with esmtp (Exim 4.77) (envelope-from ) id 1SjFfE-0006DD-Tu; Mon, 25 Jun 2012 22:13:36 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit From: "core issue tracker" X-Trac-Version: 0.12.2 Precedence: bulk Auto-Submitted: auto-generated X-Mailer: Trac 0.12.2, by Edgewall Software To: zach@sensinode.com, hartke@tzi.org X-Trac-Project: core Date: Mon, 25 Jun 2012 20:13:36 -0000 X-URL: http://tools.ietf.org/core/ X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/core/trac/ticket/241#comment:5 Message-ID: <072.3534367eb1c38aac2bb263442a67ccb3@trac.tools.ietf.org> References: <057.c44e32d1c6663d3d7f4c960815a6fce2@trac.tools.ietf.org> X-Trac-Ticket-ID: 241 In-Reply-To: <057.c44e32d1c6663d3d7f4c960815a6fce2@trac.tools.ietf.org> X-SA-Exim-Connect-IP: 127.0.0.1 X-SA-Exim-Rcpt-To: zach@sensinode.com, hartke@tzi.org, core@ietf.org X-SA-Exim-Mail-From: trac+core@trac.tools.ietf.org X-SA-Exim-Scanned: No (on grenache.tools.ietf.org); SAEximRunCond expanded to false Cc: core@ietf.org Subject: Re: [core] #241: Proxy Safe & Cache Key indication for options X-BeenThere: core@ietf.org X-Mailman-Version: 2.1.12 Reply-To: trac+core@trac.tools.ietf.org List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Jun 2012 23:45:04 -0000 #241: Proxy Safe & Cache Key indication for options Changes (by hartke@…): * version: => coap-09 * milestone: => post-WGLC-1 -- ----------------------------------+-------------------------- Reporter: zach@… | Owner: zach@… Type: protocol enhancement | Status: new Priority: minor | Milestone: post-WGLC-1 Component: coap | Version: coap-09 Severity: - | Resolution: Keywords: | ----------------------------------+-------------------------- Ticket URL: core From trac+core@trac.tools.ietf.org Mon Jun 25 18:15:15 2012 Return-Path: X-Original-To: core@ietfa.amsl.com Delivered-To: core@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2998E11E808F for ; Mon, 25 Jun 2012 18:15:15 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.124 X-Spam-Level: X-Spam-Status: No, score=-102.124 tagged_above=-999 required=5 tests=[AWL=0.475, 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 UWv0aOpTJACV for ; Mon, 25 Jun 2012 18:15:14 -0700 (PDT) Received: from grenache.tools.ietf.org (grenache.tools.ietf.org [77.72.230.30]) by ietfa.amsl.com (Postfix) with ESMTP id 6590411E8073 for ; Mon, 25 Jun 2012 18:15:14 -0700 (PDT) Received: from localhost ([127.0.0.1]:34974 helo=grenache.tools.ietf.org ident=www-data) by grenache.tools.ietf.org with esmtp (Exim 4.77) (envelope-from ) id 1SjFeS-0005Rk-62; Mon, 25 Jun 2012 22:12:48 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit From: "core issue tracker" X-Trac-Version: 0.12.2 Precedence: bulk Auto-Submitted: auto-generated X-Mailer: Trac 0.12.2, by Edgewall Software To: draft-ietf-core-block@tools.ietf.org, hartke@tzi.org X-Trac-Project: core Date: Mon, 25 Jun 2012 20:12:48 -0000 X-URL: http://tools.ietf.org/core/ X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/core/trac/ticket/209#comment:1 Message-ID: <066.d0e7ccd126a265328ad61283e90410f2@trac.tools.ietf.org> References: <051.51f78e9af0ddc8ee31f86b5cb9ac3c19@trac.tools.ietf.org> X-Trac-Ticket-ID: 209 In-Reply-To: <051.51f78e9af0ddc8ee31f86b5cb9ac3c19@trac.tools.ietf.org> X-SA-Exim-Connect-IP: 127.0.0.1 X-SA-Exim-Rcpt-To: draft-ietf-core-block@tools.ietf.org, hartke@tzi.org, core@ietf.org X-SA-Exim-Mail-From: trac+core@trac.tools.ietf.org X-SA-Exim-Scanned: No (on grenache.tools.ietf.org); SAEximRunCond expanded to false Resent-To: Resent-To: Resent-Message-Id: <20120626011514.6590411E8073@ietfa.amsl.com> Resent-Date: Mon, 25 Jun 2012 18:15:14 -0700 (PDT) Resent-From: trac+core@trac.tools.ietf.org Cc: core@ietf.org Subject: Re: [core] #209: Add potential attacks to security considerations X-BeenThere: core@ietf.org X-Mailman-Version: 2.1.12 Reply-To: trac+core@trac.tools.ietf.org List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Jun 2012 01:15:15 -0000 #209: Add potential attacks to security considerations Changes (by hartke@…): * version: => block-08 -- -----------------------------+-------------------------------------- Reporter: cabo@… | Owner: draft-ietf-core-block@… Type: editorial | Status: new Priority: minor | Milestone: post-WGLC-1 Component: block | Version: block-08 Severity: In WG Last Call | Resolution: Keywords: | -----------------------------+-------------------------------------- Ticket URL: core From trac+core@trac.tools.ietf.org Mon Jun 25 20:15:15 2012 Return-Path: X-Original-To: core@ietfa.amsl.com Delivered-To: core@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 547F011E80AA for ; Mon, 25 Jun 2012 20:15:15 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.133 X-Spam-Level: X-Spam-Status: No, score=-102.133 tagged_above=-999 required=5 tests=[AWL=0.466, 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 RtSwY77MpfUa for ; Mon, 25 Jun 2012 20:15:14 -0700 (PDT) Received: from grenache.tools.ietf.org (grenache.tools.ietf.org [77.72.230.30]) by ietfa.amsl.com (Postfix) with ESMTP id 8179C11E8080 for ; Mon, 25 Jun 2012 20:15:14 -0700 (PDT) Received: from localhost ([127.0.0.1]:34951 helo=grenache.tools.ietf.org ident=www-data) by grenache.tools.ietf.org with esmtp (Exim 4.77) (envelope-from ) id 1SjFdw-0003FT-IC; Mon, 25 Jun 2012 22:12:16 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit From: "core issue tracker" X-Trac-Version: 0.12.2 Precedence: bulk Auto-Submitted: auto-generated X-Mailer: Trac 0.12.2, by Edgewall Software To: draft-ietf-core-coap@tools.ietf.org, zach@sensinode.com, hartke@tzi.org X-Trac-Project: core Date: Mon, 25 Jun 2012 20:12:16 -0000 X-URL: http://tools.ietf.org/core/ X-Trac-Ticket-URL: http://tools.ietf.org/wg/core/trac/ticket/207#comment:2 Message-ID: <068.341834112eb20d4001e85aacd6b32a11@trac.tools.ietf.org> References: <053.d889c7b2b45ce344b85654e528a4b801@trac.tools.ietf.org> X-Trac-Ticket-ID: 207 In-Reply-To: <053.d889c7b2b45ce344b85654e528a4b801@trac.tools.ietf.org> X-SA-Exim-Connect-IP: 127.0.0.1 X-SA-Exim-Rcpt-To: draft-ietf-core-coap@tools.ietf.org, zach@sensinode.com, hartke@tzi.org, core@ietf.org X-SA-Exim-Mail-From: trac+core@trac.tools.ietf.org X-SA-Exim-Scanned: No (on grenache.tools.ietf.org); SAEximRunCond expanded to false Resent-To: Resent-To: Resent-Message-Id: <20120626031514.8179C11E8080@ietfa.amsl.com> Resent-Date: Mon, 25 Jun 2012 20:15:14 -0700 (PDT) Resent-From: trac+core@trac.tools.ietf.org Cc: core@ietf.org Subject: Re: [core] #207: Add advice on default values for critical options X-BeenThere: core@ietf.org X-Mailman-Version: 2.1.12 Reply-To: trac+core@trac.tools.ietf.org List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Jun 2012 03:15:15 -0000 #207: Add advice on default values for critical options Changes (by hartke@…): * version: => coap-09 -- -----------------------------+------------------------------------- Reporter: hartke@… | Owner: draft-ietf-core-coap@… Type: editorial | Status: closed Priority: minor | Milestone: post-WGLC-1 Component: coap | Version: coap-09 Severity: In WG Last Call | Resolution: fixed Keywords: | -----------------------------+------------------------------------- Ticket URL: core From T.A.Butt@lboro.ac.uk Tue Jun 26 10:58:17 2012 Return-Path: X-Original-To: core@ietfa.amsl.com Delivered-To: core@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8779C11E808A for ; Tue, 26 Jun 2012 10:58:17 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.599 X-Spam-Level: X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4] 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 qRm7n3DdLmpB for ; Tue, 26 Jun 2012 10:58:17 -0700 (PDT) Received: from weed.lut.ac.uk (mailhost.lut.ac.uk [158.125.1.226]) by ietfa.amsl.com (Postfix) with ESMTP id CB5E711E8088 for ; Tue, 26 Jun 2012 10:58:16 -0700 (PDT) Received: from [158.125.4.16] (helo=ITSCASH-2.lunet.lboro.ac.uk) by weed.lut.ac.uk with esmtps (TLSv1:AES128-SHA:128) (Exim 4.77) id 1Sja1n-0008GQ-Bt for core@ietf.org; Tue, 26 Jun 2012 18:58:16 +0100 Received: from staffmbx-1.lunet.lboro.ac.uk ([169.254.1.99]) by ITSCASH-2.lunet.lboro.ac.uk ([158.125.4.16]) with mapi; Tue, 26 Jun 2012 18:58:15 +0100 From: Talal Butt To: "core@ietf.org" Date: Tue, 26 Jun 2012 18:57:56 +0100 Thread-Topic: Paper related to CoRE Resource directory for service discovery Thread-Index: AQHNU8S2MRHp1J5YsEmSKB5Nm+bCBZcM4uVE Message-ID: <08F47B9518FE3B44840A1D88402C56D216963FABB6@STAFFMBX-1.lunet.lboro.ac.uk> References: <08F47B9518FE3B44840A1D88402C56D216963FABB5@STAFFMBX-1.lunet.lboro.ac.uk> In-Reply-To: <08F47B9518FE3B44840A1D88402C56D216963FABB5@STAFFMBX-1.lunet.lboro.ac.uk> Accept-Language: en-US, en-GB Content-Language: en-GB X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US, en-GB Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Scan-Signature: e2e7fc0f42b9210caba2a390c9923550 X-Lboro-Filtered: weed.lut.ac.uk, Tue, 26 Jun 2012 18:58:16 +0100 Subject: [core] Paper related to CoRE Resource directory for service discovery X-BeenThere: core@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Jun 2012 17:58:17 -0000 Hello all, Below is the link of our paper and presentation at WoT (web of things) 2012= , which uses the idea of CoRE Resource directory for service discovery. It= also offers a grouping framework (still being enhanced) for service compos= ition and a timer to reduce the overhead of status maintenance. We have use= d Contiki OS and two implementations of CoAP (C and JAVA based) to run the = experiments. Paper: http://www.webofthings.org/wot/2012/papers/Pervasive_WoT2012_Paper4.= pdf Presentation: http://slidesha.re/NkHtZB Regards, Talal Ashraf Butt Research Student Loughborough University From cabo@tzi.org Wed Jun 27 01:46:08 2012 Return-Path: X-Original-To: core@ietfa.amsl.com Delivered-To: core@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 69A8F21F8646 for ; Wed, 27 Jun 2012 01:46:08 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -104.949 X-Spam-Level: X-Spam-Status: No, score=-104.949 tagged_above=-999 required=5 tests=[AWL=-1.300, BAYES_50=0.001, 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 SltsAm8PDPTJ for ; Wed, 27 Jun 2012 01:46:07 -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 2EBDC21F85F2 for ; Wed, 27 Jun 2012 01:46:06 -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.3/8.14.3) with ESMTP id q5R8jwgI012860 for ; Wed, 27 Jun 2012 10:45:58 +0200 (CEST) Received: from eduroam-pool6-0130.wlan.uni-bremen.de (eduroam-pool6-0130.wlan.uni-bremen.de [134.102.24.130]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id 5B608813; Wed, 27 Jun 2012 10:45:58 +0200 (CEST) Content-Type: text/plain; charset=iso-8859-1 Mime-Version: 1.0 (Apple Message framework v1278) From: Carsten Bormann Date: Wed, 27 Jun 2012 10:45:57 +0200 Content-Transfer-Encoding: quoted-printable Message-Id: <99E9327A-1011-497C-84D8-9010A216D96C@tzi.org> References: To: "core@ietf.org WG" X-Mailer: Apple Mail (2.1278) Subject: [core] Today: Authors' Phone Conference, open to WG members X-BeenThere: core@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Jun 2012 08:46:08 -0000 On June 4, I said: > June 27 1400Z..1600Z: have the next virtual interim (planning for 2 = hours right now) > Around this meeting have another respin or two of the drafts Well, we do have the respin of core-coap-10. I neglected organizing the Interim, though, and some technical problems = prevented the WG chairs from fixing this in time. So we won't have an official Virtual Interim today. However, we will be using the time slot we reserved for that for an = Authors' Phone Conference, which will be open for interested WG members. (So in practice not much has changed from the original plan, except that = we have less overhead and won't make decisions "as a WG" in the phone = conference -- but, of course, we can still try to find good technical = solutions with whoever is present.) Below please find the dial-in instructions. The time is 1400Z-1600Z, i.e. 1600-1800 CEST, 0700-0900 PDT, 1000-1200 = EDT, 2200-2400 China, 2300-0100 Japan/Korea, 0000-0200 Sydney (sorry = about that...). > 1. Go to: > https://www4.gotomeeting.com/join/960105999 >=20 > 2. Use your microphone and speakers (VoIP) - a headset is = recommended. Or, call in using your telephone. >=20 > Austria: +43 (0) 7 2088 0034 > Belgium: +32 (0) 28 08 9321 > Canada: +1 (647) 977-5956 > Denmark: +45 (0) 69 91 80 05 > Finland: +358 (0) 931 58 1746 > France: +33 (0) 182 880 780 > Germany: +49 (0) 811 8899 6900 > Ireland: +353 (0) 15 290 180 > Italy: +39 0 699 26 68 58 > Netherlands: +31 (0) 208 908 267 > Norway: +47 21 54 32 44 > Spain: +34 911 23 0850 > Sweden: +46 (0) 852 500 612 > Switzerland: +41 (0) 435 0006 96 > United Kingdom: +44 (0) 207 151 1850 > United States: +1 (773) 945-1031 > Access Code: 960-105-999 > Audio PIN: Shown after joining the meeting >=20 > Meeting ID: 960-105-999 Gr=FC=DFe, Carsten From trac+core@trac.tools.ietf.org Wed Jun 27 05:12:27 2012 Return-Path: X-Original-To: core@ietfa.amsl.com Delivered-To: core@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 622CA21F85E5 for ; Wed, 27 Jun 2012 05:12:27 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.143 X-Spam-Level: X-Spam-Status: No, score=-102.143 tagged_above=-999 required=5 tests=[AWL=0.456, 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 eNicBe9k+kh7 for ; Wed, 27 Jun 2012 05:12:26 -0700 (PDT) Received: from grenache.tools.ietf.org (grenache.tools.ietf.org [77.72.230.30]) by ietfa.amsl.com (Postfix) with ESMTP id BC67021F85D3 for ; Wed, 27 Jun 2012 05:12:26 -0700 (PDT) Received: from localhost ([127.0.0.1]:45071 helo=grenache.tools.ietf.org ident=www-data) by grenache.tools.ietf.org with esmtp (Exim 4.77) (envelope-from ) id 1Sjr6N-0002SV-GL; Wed, 27 Jun 2012 14:12:07 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit From: "core issue tracker" X-Trac-Version: 0.12.2 Precedence: bulk Auto-Submitted: auto-generated X-Mailer: Trac 0.12.2, by Edgewall Software To: zach@sensinode.com, hartke@tzi.org, esko.dijk@philips.com X-Trac-Project: core Date: Wed, 27 Jun 2012 12:12:07 -0000 X-URL: http://tools.ietf.org/core/ X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/core/trac/ticket/241#comment:6 Message-ID: <072.bafddb2dc7b3e1fe693960fb92486019@trac.tools.ietf.org> References: <057.c44e32d1c6663d3d7f4c960815a6fce2@trac.tools.ietf.org> X-Trac-Ticket-ID: 241 In-Reply-To: <057.c44e32d1c6663d3d7f4c960815a6fce2@trac.tools.ietf.org> X-SA-Exim-Connect-IP: 127.0.0.1 X-SA-Exim-Rcpt-To: zach@sensinode.com, hartke@tzi.org, esko.dijk@philips.com, core@ietf.org X-SA-Exim-Mail-From: trac+core@trac.tools.ietf.org X-SA-Exim-Scanned: No (on grenache.tools.ietf.org); SAEximRunCond expanded to false Cc: core@ietf.org Subject: Re: [core] #241: Proxy Safe & Cache Key indication for options X-BeenThere: core@ietf.org X-Mailman-Version: 2.1.12 Reply-To: trac+core@trac.tools.ietf.org List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Jun 2012 12:12:27 -0000 #241: Proxy Safe & Cache Key indication for options Comment (by esko.dijk@…): Maybe already indicated by Carsten above; but here goes: In my view there's no Safe/Unsafe bit needed in the encoding for critical options. An intermediary already has to understand all criticial options before processing a request, so it can have hardcoded knowledge which ones are Safe/Unsafe. No need to use encoding bits in that case. -- ----------------------------------+-------------------------- Reporter: zach@… | Owner: zach@… Type: protocol enhancement | Status: new Priority: minor | Milestone: post-WGLC-1 Component: coap | Version: coap-09 Severity: - | Resolution: Keywords: | ----------------------------------+-------------------------- Ticket URL: core From cabo@tzi.org Wed Jun 27 06:53:50 2012 Return-Path: X-Original-To: core@ietfa.amsl.com Delivered-To: core@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CD8A421F8766 for ; Wed, 27 Jun 2012 06:53:50 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -105.816 X-Spam-Level: X-Spam-Status: No, score=-105.816 tagged_above=-999 required=5 tests=[AWL=0.433, 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 Qv8ZFZTlAs5j for ; Wed, 27 Jun 2012 06:53:49 -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 6337F21F874A for ; Wed, 27 Jun 2012 06:53:49 -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.3/8.14.3) with ESMTP id q5RDrelg027757 for ; Wed, 27 Jun 2012 15:53:40 +0200 (CEST) Received: from [10.0.1.3] (reingewinn.informatik.uni-bremen.de [134.102.218.123]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id EDA5EAAA; Wed, 27 Jun 2012 15:53:40 +0200 (CEST) Mime-Version: 1.0 (Apple Message framework v1278) Content-Type: text/plain; charset=iso-8859-1 From: Carsten Bormann In-Reply-To: <8906C11D-58DA-46AA-8152-F70583543B81@tzi.org> Date: Wed, 27 Jun 2012 15:53:40 +0200 Content-Transfer-Encoding: quoted-printable Message-Id: References: <8906C11D-58DA-46AA-8152-F70583543B81@tzi.org> To: "core@ietf.org WG" X-Mailer: Apple Mail (2.1278) Subject: [core] Authors' Phone Call (Re: core-coap-10, coap-misc-18, and a new draft on congestion control principles) X-BeenThere: core@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Jun 2012 13:53:51 -0000 Here is something of an agenda for the APC today: 1) Quick document check: > - Check coap-misc 2.1 (resolving #202), 3 (#214), and 6 (#201) and, if = we > like them, integrate all this text (and the appropriate parts of 7) > into core-coap. >=20 > - Check core-congestion-control-00 and, if we like it, perform the > changes indicated in the drafy in core-coap and try to resolve #215 > in the process. > - Does core-congestion-control stay its own draft or do we integrate > it as a "congestion considerations" section into core-coap? > [This author would be happier to make this a stand-alone = informational.] 2) How do we get progress on this one? > - #241: We need to come to a conclusion as to what we do about the > proxy-elective class of options, and if we need the additional bit > for cache key indication. We cannot really discuss this potential change productively without an = input document that shows at least one solution. So how do we get that? 3) Other discussion points: > - #230: Are we done with this one? (Last 2 comments on ticket.) >=20 > - #216 -- which scopes do we actually want to recommend to use? Do we > expect all CoAP nodes to listen to all scopes? See also http://tools.ietf.org/html/rfc4291#section-2.7 > - any work remaining on the packet size text? This is just one example of the ~ 90 unprocessed items. Gr=FC=DFe, Carsten From cabo@tzi.org Wed Jun 27 08:23:05 2012 Return-Path: X-Original-To: core@ietfa.amsl.com Delivered-To: core@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E251221F8700 for ; Wed, 27 Jun 2012 08:23:03 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -105.924 X-Spam-Level: X-Spam-Status: No, score=-105.924 tagged_above=-999 required=5 tests=[AWL=0.325, 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 dJG7LY3+V0Hm for ; Wed, 27 Jun 2012 08:23:03 -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 77B0821F8683 for ; Wed, 27 Jun 2012 08:23:02 -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.3/8.14.3) with ESMTP id q5RFMsmS015168 for ; Wed, 27 Jun 2012 17:22:54 +0200 (CEST) Received: from [10.0.1.3] (reingewinn.informatik.uni-bremen.de [134.102.218.123]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id 2B9CCBEC; Wed, 27 Jun 2012 17:22:54 +0200 (CEST) Mime-Version: 1.0 (Apple Message framework v1278) Content-Type: text/plain; charset=iso-8859-1 From: Carsten Bormann In-Reply-To: Date: Wed, 27 Jun 2012 17:22:51 +0200 Content-Transfer-Encoding: quoted-printable Message-Id: <9B7661CB-E394-4829-AAC0-FF4AFE6A5664@tzi.org> References: <8906C11D-58DA-46AA-8152-F70583543B81@tzi.org> To: "core@ietf.org WG" X-Mailer: Apple Mail (2.1278) Subject: Re: [core] Authors' Phone Call (Re: core-coap-10, coap-misc-18, and a new draft on congestion control principles) X-BeenThere: core@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Jun 2012 15:23:05 -0000 We had a pretty focused and productive discussion, leading to some = action points for the authors, which still need to be written up (e.g., = in the tickets). For your planning: We are planning to do the next call 1000Z-1200Z on = Thu, July 5th (just a little bit friendlier time for the Chinese = participants...). Gr=FC=DFe, Carsten From cabo@tzi.org Thu Jun 28 17:13:41 2012 Return-Path: X-Original-To: core@ietfa.amsl.com Delivered-To: core@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CD0F011E80EC for ; Thu, 28 Jun 2012 17:13:41 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -106.413 X-Spam-Level: X-Spam-Status: No, score=-106.413 tagged_above=-999 required=5 tests=[AWL=-0.164, 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 nnk1ywM0tqB2 for ; Thu, 28 Jun 2012 17:13:41 -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 EDB0811E80C2 for ; Thu, 28 Jun 2012 17:13:40 -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.3/8.14.3) with ESMTP id q5T0DYTp020440 for ; Fri, 29 Jun 2012 02:13:34 +0200 (CEST) Received: from [192.168.217.105] (p54894C40.dip.t-dialin.net [84.137.76.64]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id EE95D2F6; Fri, 29 Jun 2012 02:13:33 +0200 (CEST) Content-Type: text/plain; charset=iso-8859-1 Mime-Version: 1.0 (Apple Message framework v1278) From: Carsten Bormann Date: Fri, 29 Jun 2012 02:13:32 +0200 Content-Transfer-Encoding: quoted-printable Message-Id: <23C49D18-53E3-4770-8693-BDE199BDF71F@tzi.org> References: <20120628234902.25282.5708.idtracker@ietfa.amsl.com> To: "core@ietf.org WG" X-Mailer: Apple Mail (2.1278) Subject: [core] Fwd: core - Requested sessions have been scheduled for IETF 84 X-BeenThere: core@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Jun 2012 00:13:42 -0000 We now have TENTATIVE dates for the CoRE slots. Please note that there is some potential for confusion: 1) The session 2 below says that it ends at 1220. That doesn't add up; = the session takes the next 1-hour slot, too. 2) If you look at the tentative agenda in the data tracker, you will see = that the second half of that second slot overlaps LWIG. This will be = fixed, by rescheduling one (or both!) slots. 3) As you can see, there is still a lot of rescheduling going on, so = please don't plan your flights around this TENTATIVE schedule. Other = slots relevant for you might include TSVAREA (Monday), HTTPBIS = (Tuesday/Thursday), APPAREA (Monday), SAAG (Thursday), the RMCAT BOF = (Thursday), HOMENET (Monday). And, of course, as usual a lot of work = will be done during the entire week outside the slots in the hallways. Gr=FC=DFe, Carsten > core Session 1 (2:00:00) > Wednesday, Afternoon Session II 1510-1710 > Room Name: Regency C > --------------------------------------------- > core Session 2 (2:00:00) > Friday, Afternoon Session I 1120-1220 [NO, REALLY 1330] > Room Name: Regency F > ---------------------------------------------