
From nobody Fri Aug 15 06:19:15 2014
Return-Path: <rstruik.ext@gmail.com>
X-Original-To: dtls-iot@ietfa.amsl.com
Delivered-To: dtls-iot@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1261E1A0AA8; Fri, 15 Aug 2014 06:19:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ThF10638_KmJ; Fri, 15 Aug 2014 06:19:08 -0700 (PDT)
Received: from mail-ig0-x22f.google.com (mail-ig0-x22f.google.com [IPv6:2607:f8b0:4001:c05::22f]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5AAF81A0AA9; Fri, 15 Aug 2014 06:19:08 -0700 (PDT)
Received: by mail-ig0-f175.google.com with SMTP id uq10so1861648igb.14 for <multiple recipients>; Fri, 15 Aug 2014 06:19:07 -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:content-type; bh=npBzq5uNPhOXfyurEGDa8Md2s9CSRe8bnKzA1r50+q8=; b=tkduAIV/gbHBJNfcv3LtiIxGyQChzdzfIMOhO6AG49d6l+X6fCkjwjA0mDSOjz1Mfu nKQiNwUJbl//ueujatFPvavbXVhYfiIcwPcyi7sjSmX8vS6zaE7I1bIj6aT3eSOfIC7o EvbRaA6jG7dDzKxm4Nx57d2eazkar2DmTzca8OjhDDvRvRSFsVfOEhAu0hbXHiuW0E1L Jaxi3u1WRZbBnRFKcM+FjFkLk9AzSG5lYxzH6V7dIc9HpPZAoliMIwsaxD4DFbS+jigM MexDS/V86J/zpqh3h28w9dAXISZyOX7CVY01K8Lh2UUkNu79dPY98eELv1Rfiz7eA0oC Qnog==
X-Received: by 10.50.153.83 with SMTP id ve19mr5203360igb.4.1408108747610; Fri, 15 Aug 2014 06:19:07 -0700 (PDT)
Received: from [192.168.0.10] (CPE7cb21b2cb904-CM7cb21b2cb901.cpe.net.cable.rogers.com. [99.231.118.107]) by mx.google.com with ESMTPSA id hu5sm7865430igb.16.2014.08.15.06.19.06 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 15 Aug 2014 06:19:07 -0700 (PDT)
Message-ID: <53EE08B9.8000406@gmail.com>
Date: Fri, 15 Aug 2014 09:18:49 -0400
From: Rene Struik <rstruik.ext@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: "Hedanping (Ana)" <ana.hedanping@huawei.com>,  "Kumar, Sandeep" <sandeep.kumar@philips.com>, "ace@ietf.org" <ace@ietf.org>
References: <77FA386512F0D748BC7C02C36EB1106D8D4164@szxeml557-mbs.china.huawei.com> <BE6D13F6A4554947952B39008B0DC0153E809F78@DBXPRD9003MB059.MGDPHG.emi.philips.com> <77FA386512F0D748BC7C02C36EB1106D8D4220@szxeml557-mbs.china.huawei.com> <BE6D13F6A4554947952B39008B0DC0153E80A5FE@DBXPRD9003MB059.MGDPHG.emi.philips.com> <77FA386512F0D748BC7C02C36EB1106D8D473D@szxeml557-mbs.china.huawei.com>
In-Reply-To: <77FA386512F0D748BC7C02C36EB1106D8D473D@szxeml557-mbs.china.huawei.com>
Content-Type: multipart/alternative; boundary="------------080706060506000506040402"
Archived-At: http://mailarchive.ietf.org/arch/msg/dtls-iot/Qnxvy1M1Yp_9eej-gJij0alEMeQ
Cc: "dtls-iot@ietf.org" <dtls-iot@ietf.org>
Subject: Re: [Dtls-iot] [Ace] About secure relay of authentication and authroization messages
X-BeenThere: dtls-iot@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: DTLS for IoT discussion list <dtls-iot.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dtls-iot>, <mailto:dtls-iot-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dtls-iot/>
List-Post: <mailto:dtls-iot@ietf.org>
List-Help: <mailto:dtls-iot-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dtls-iot>, <mailto:dtls-iot-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 15 Aug 2014 13:19:12 -0000

This is a multi-part message in MIME format.
--------------080706060506000506040402
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Dear colleagues:

FYI - You may wish to have a look at the discussion on the IETF DICE 
mailing list end of May (messages 240-253; May 27-30, 2014) related to 
this, see, e.g., 
http://www.ietf.org/mail-archive/web/dtls-iot/current/msg00241.html. 
This discussion was triggered by some questions I had re suggestions in 
the security considerations section of draft-kumar-dice-dtls-relay-01 
aimed at countering Denial of Service attacks.

Best regards, Rene

On 8/14/2014 11:35 PM, Hedanping (Ana) wrote:
>
> Hi Sandeep,
>
> According to your solution "The first RE in the path checks whether C 
> holds a valid certificate or a pre-shared relay key" which itself is 
> an authentication/authorization decision. Infact it sounds more like 
> an AA decision to first access the one-hop relay and then an AA 
> decision to access the RS.
>
> [Danping] Your understanding is right.  In unconstraint environment, 
> Relay Elements simply relay the packets to destination. And as we 
> know,  the REs are likely to be constraint devices in constraint 
> environment such as ad hoc WSNs, thus the battery resource and packet 
> buffer will be consumed due to relaying packet for C. In other words, 
> to request resources over a RS that is multiple hops away 
> intrinsically hints a request of the resource over REs along the hops. 
>  Therefore I believe the a light AA is desired for the first-hop relay 
> to protect itself and other REs along the route.
>
> Would it not be simple to consider the relay to be an RS which is 
> one-hop away and use the not-yet-designed ACE solution for the 
> first-hop too.
>
> [Danping] It would be better to design a mechanism which allows AM/AS 
> issuing a permission for C to access the first-hop RE, the permission 
> might be transmitted separately or piggybacked with the first AA 
> message between C and RS. The not-yet-designed ACE solution might be 
> used too, but it is unnecessary to exchange key to secure the relay 
> message and the message flow would be different.  What do you think?
>
> Regards,
>
> Danping
>
> *From:*Kumar, Sandeep [mailto:sandeep.kumar@philips.com]
> *Sent:* Wednesday, August 13, 2014 3:24 PM
> *To:* Hedanping (Ana); ace@ietf.org
> *Subject:* RE: [Ace] About secure relay of authentication and 
> authroization messages
>
> HI Danping
>
> According to your solution "The first RE in the path checks whether C 
> holds a valid certificate or a pre-shared relay key" which itself is 
> an authentication/authorization decision. Infact it sounds more like 
> an AA decision to first access the one-hop relay and then an AA 
> decision to access the RS. Would it not be simple to consider the 
> relay to be an RS which is one-hop away and use the not-yet-designed 
> ACE solution for the first-hop too.
>
> Regards
>
> Sandeep
>
> *From:*Hedanping (Ana) [mailto:ana.hedanping@huawei.com]
> *Sent:* Wednesday, August 13, 2014 2:58 AM
> *To:* Kumar, Sandeep; ace@ietf.org <mailto:ace@ietf.org>
> *Subject:* RE: [Ace] About secure relay of authentication and 
> authroization messages
>
> Hi Sandeep,
>
> Thanks for the information and also thank you for showing interest in 
> this issue.
>
> The assumption is that, during the AA procedure, there are AA messages 
> exchanged between the C and RS, which are not directly connected. To 
> solve DOS attack, I roughly have a solution in mind:
>
> A relay key/certificate is needed. There might exist more than one RE 
> along the path between C and RS. The first RE in the path checks 
> whether C holds a valid certificate or a pre-shared relay key. If 
> verified, the AA messages from C are relayed normally. Otherwise, the 
> AA messages from C are ignored.
>
> Regards,
>
> Danping
>
> *From:*Kumar, Sandeep [mailto:sandeep.kumar@philips.com]
> *Sent:* Tuesday, August 12, 2014 4:21 PM
> *To:* Hedanping (Ana); ace@ietf.org <mailto:ace@ietf.org>
> *Subject:* RE: [Ace] About secure relay of authentication and 
> authroization messages
>
> Hi Danping
>
> I think ACE is at a very early stage that it is better to first solve 
> the problem without the relay path. At a later stage, the relay path 
> can be added for scenarios that might need them and ofcourse DoS 
> protection will be an important issue to consider then. Do you have 
> any specific solutions to solve the problem? If the DoS protection 
> solution depends heavily on the AA data then imho it should be solved 
> in ACE.
>
> Regards
>
> Sandeep
>
> *From:*Ace [mailto:ace-bounces@ietf.org] *On Behalf Of *Hedanping (Ana)
> *Sent:* Tuesday, August 12, 2014 5:50 AM
> *To:* ace@ietf.org <mailto:ace@ietf.org>
> *Subject:* [Ace] About secure relay of authentication and 
> authroization messages
>
> Hi,
>
> There is an issue that I am not sure whether it is suitable for a 
> draft: should we consider secure relay of the Authentication and 
> authorization (AA) messages to protect relay elements along the relay 
> path?
>
> DTLS relay and PANA relay have been proposed, however the relay 
> elements simply relays the AA messages to the server. To avoid DOS 
> attack, the they limit the frequency and maximum number of times to 
> relay the AA requests.
>
> In constraint environment, the relay elements might be energy 
> constrained devices. If a malicious client intends to exhaust the 
> relay elements' power by frequently sending AA requests with forged 
> IPs or IDs, is there any countermeasure to this issue? Do we need to 
> consider this issue in ACE WG?
>
> Regards,
>
> Danping
>
> ------------------------------------------------------------------------
>
> 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.
>
>
>
> _______________________________________________
> Ace mailing list
> Ace@ietf.org
> https://www.ietf.org/mailman/listinfo/ace


-- 
email: rstruik.ext@gmail.com | Skype: rstruik
cell: +1 (647) 867-5658 | US: +1 (415) 690-7363


--------------080706060506000506040402
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <div class="moz-cite-prefix">Dear colleagues:<br>
      <br>
      FYI - You may wish to have a look at the discussion on the IETF
      DICE mailing list end of May (messages 240-253; May 27-30, 2014)
      related to this, see, e.g.,&nbsp;
      <a class="moz-txt-link-freetext" href="http://www.ietf.org/mail-archive/web/dtls-iot/current/msg00241.html">http://www.ietf.org/mail-archive/web/dtls-iot/current/msg00241.html</a>.
      This discussion was triggered by some questions I had re
      suggestions in the security considerations section of
      draft-kumar-dice-dtls-relay-01 aimed at countering Denial of
      Service attacks.<br>
      <br>
      Best regards, Rene<br>
      <br>
      On 8/14/2014 11:35 PM, Hedanping (Ana) wrote:<br>
    </div>
    <blockquote
cite="mid:77FA386512F0D748BC7C02C36EB1106D8D473D@szxeml557-mbs.china.huawei.com"
      type="cite">
      <meta http-equiv="Content-Type" content="text/html;
        charset=ISO-8859-1">
      <meta name="Generator" content="Microsoft Word 12 (filtered
        medium)">
      <!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]-->
      <style><!--
/* Font Definitions */
@font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	text-align:justify;
	text-justify:inter-ideograph;
	font-size:10.5pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"\7EAF\6587\672C Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:10.5pt;
	font-family:"Calibri","sans-serif";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"\6279\6CE8\6846\6587\672C Char";
	margin:0cm;
	margin-bottom:.0001pt;
	text-align:justify;
	text-justify:inter-ideograph;
	font-size:10.5pt;
	font-family:"Calibri","sans-serif";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin:0cm;
	margin-bottom:.0001pt;
	text-align:justify;
	text-justify:inter-ideograph;
	text-indent:21.0pt;
	font-size:10.5pt;
	font-family:"Calibri","sans-serif";}
span.Char
	{mso-style-name:"\6279\6CE8\6846\6587\672C Char";
	mso-style-priority:99;
	mso-style-link:\6279\6CE8\6846\6587\672C;
	font-family:"Calibri","sans-serif";}
p.BalloonText, li.BalloonText, div.BalloonText
	{mso-style-name:"Balloon Text";
	mso-style-link:"Balloon Text Char";
	margin:0cm;
	margin-bottom:.0001pt;
	text-align:justify;
	text-justify:inter-ideograph;
	font-size:10.5pt;
	font-family:"Calibri","sans-serif";}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
span.EmailStyle22
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle23
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle24
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle25
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle26
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.Char0
	{mso-style-name:"\7EAF\6587\672C Char";
	mso-style-priority:99;
	mso-style-link:\7EAF\6587\672C;
	font-family:"Calibri","sans-serif";}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 90.0pt 72.0pt 90.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
      <div class="WordSection1">
        <p class="MsoNormal"><span style="color:#1F497D" lang="EN-US">Hi
            Sandeep,<o:p></o:p></span></p>
        <p class="MsoNormal"><span
            style="font-size:11.0pt;color:#1F497D" lang="EN-US">According
            to your solution &#8220;</span><span style="color:#1F497D"
            lang="EN-US">The first RE in the path checks whether C holds
            a valid certificate or a pre-shared relay key&#8221; which itself
            is an authentication/authorization decision. Infact it
            sounds more like an AA decision to first access the one-hop
            relay and then an AA decision to access the RS.
            <o:p></o:p></span></p>
        <p class="MsoPlainText"><span style="color:#943634" lang="EN-US">[Danping]
            Your understanding is right.&nbsp; In unconstraint environment,
            Relay Elements simply relay the packets to destination. And
            as we know, &nbsp;the REs are likely to be constraint devices in
            constraint environment such as ad hoc WSNs, thus the battery
            resource and packet buffer will be consumed due to relaying
            packet for C. In other words, to request resources over a RS
            that is multiple hops away intrinsically hints a request of
            the resource over REs along the hops. &nbsp;Therefore I believe
            the a light AA is desired for the first-hop relay to protect
            itself and other REs along the route.<o:p></o:p></span></p>
        <p class="MsoNormal"><span style="color:#1F497D" lang="EN-US"><o:p>&nbsp;</o:p></span></p>
        <p class="MsoNormal"><span style="color:#1F497D" lang="EN-US">Would
            it not be simple to consider the relay to be an RS which is
            one-hop away and use the not-yet-designed ACE solution for
            the first-hop too.<o:p></o:p></span></p>
        <p class="MsoPlainText"><span style="color:#943634" lang="EN-US">[Danping]
            It would be better to design a mechanism which allows AM/AS
            issuing a permission for C to access the first-hop RE, the
            permission might be transmitted separately or piggybacked
            with the first AA message between C and RS. The
            not-yet-designed ACE solution might be used too, but it is
            unnecessary to exchange key to secure the relay message and
            the message flow would be different. &nbsp;What do you think?<o:p></o:p></span></p>
        <p class="MsoPlainText"><span style="color:#943634" lang="EN-US"><o:p>&nbsp;</o:p></span></p>
        <p class="MsoPlainText"><span style="color:#1F497D" lang="EN-US">Regards,<o:p></o:p></span></p>
        <p class="MsoPlainText"><span style="color:#1F497D" lang="EN-US">Danping<o:p></o:p></span></p>
        <p class="MsoNormal"><span style="color:#1F497D" lang="EN-US"><o:p>&nbsp;</o:p></span></p>
        <p class="MsoNormal"><span style="color:#1F497D" lang="EN-US"><o:p>&nbsp;</o:p></span></p>
        <div>
          <div style="border:none;border-top:solid #B5C4DF
            1.0pt;padding:3.0pt 0cm 0cm 0cm">
            <p class="MsoNormal" style="text-align:left" align="left"><b><span
style="font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"
                  lang="EN-US">From:</span></b><span
style="font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"
                lang="EN-US"> Kumar, Sandeep
                [<a class="moz-txt-link-freetext" href="mailto:sandeep.kumar@philips.com">mailto:sandeep.kumar@philips.com</a>]
                <br>
                <b>Sent:</b> Wednesday, August 13, 2014 3:24 PM<br>
                <b>To:</b> Hedanping (Ana); <a class="moz-txt-link-abbreviated" href="mailto:ace@ietf.org">ace@ietf.org</a><br>
                <b>Subject:</b> RE: [Ace] About secure relay of
                authentication and authroization messages<o:p></o:p></span></p>
          </div>
        </div>
        <p class="MsoNormal" style="text-align:left" align="left"><span
            lang="EN-US"><o:p>&nbsp;</o:p></span></p>
        <p class="MsoNormal"><span
            style="font-size:11.0pt;color:#1F497D" lang="EN-US">HI
            Danping<o:p></o:p></span></p>
        <p class="MsoNormal"><span
            style="font-size:11.0pt;color:#1F497D" lang="EN-US"><o:p>&nbsp;</o:p></span></p>
        <p class="MsoNormal"><span
            style="font-size:11.0pt;color:#1F497D" lang="EN-US">According
            to your solution &#8220;</span><span style="color:#1F497D"
            lang="EN-US">The first RE in the path checks whether C holds
            a valid certificate or a pre-shared relay key&#8221; which itself
            is an authentication/authorization decision. Infact it
            sounds more like an AA decision to first access the one-hop
            relay and then an AA decision to access the RS. Would it not
            be simple to consider the relay to be an RS which is one-hop
            away and use the not-yet-designed ACE solution for the
            first-hop too.<o:p></o:p></span></p>
        <p class="MsoNormal"><span style="color:#1F497D" lang="EN-US"><o:p>&nbsp;</o:p></span></p>
        <p class="MsoNormal"><span style="color:#1F497D" lang="EN-US">Regards<o:p></o:p></span></p>
        <p class="MsoNormal"><span style="color:#1F497D" lang="EN-US">Sandeep</span><span
            style="font-size:11.0pt;color:#1F497D" lang="EN-US"><o:p></o:p></span></p>
        <p class="MsoNormal"><span
            style="font-size:11.0pt;color:#1F497D" lang="EN-US"><o:p>&nbsp;</o:p></span></p>
        <div>
          <div style="border:none;border-top:solid #B5C4DF
            1.0pt;padding:3.0pt 0cm 0cm 0cm">
            <p class="MsoNormal" style="text-align:left" align="left"><b><span
style="font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"
                  lang="EN-US">From:</span></b><span
style="font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"
                lang="EN-US"> Hedanping (Ana) [<a moz-do-not-send="true"
                  href="mailto:ana.hedanping@huawei.com">mailto:ana.hedanping@huawei.com</a>]
                <br>
                <b>Sent:</b> Wednesday, August 13, 2014 2:58 AM<br>
                <b>To:</b> Kumar, Sandeep; <a moz-do-not-send="true"
                  href="mailto:ace@ietf.org">ace@ietf.org</a><br>
                <b>Subject:</b> RE: [Ace] About secure relay of
                authentication and authroization messages<o:p></o:p></span></p>
          </div>
        </div>
        <p class="MsoNormal" style="text-align:left" align="left"><span
            lang="EN-US"><o:p>&nbsp;</o:p></span></p>
        <p class="MsoNormal"><span style="color:#1F497D" lang="EN-US">Hi
            Sandeep,<o:p></o:p></span></p>
        <p class="MsoNormal"><span style="color:#1F497D" lang="EN-US">Thanks
            for the information and also thank you for showing interest
            in this issue.<o:p></o:p></span></p>
        <p class="MsoNormal"><span style="color:#1F497D" lang="EN-US">The
            assumption is that, during the AA procedure, there are AA
            messages exchanged between the C and RS, which are not
            directly connected. To solve DOS attack, I roughly have a
            solution in mind:<o:p></o:p></span></p>
        <p class="MsoListParagraph"
          style="margin-left:18.0pt;text-indent:0cm"><span
            style="color:#1F497D" lang="EN-US"><o:p>&nbsp;</o:p></span></p>
        <p class="MsoListParagraph"
          style="margin-left:18.0pt;text-indent:0cm"><span
            style="color:#1F497D" lang="EN-US">A relay key/certificate
            is needed. There might exist more than one RE along the path
            between C and RS. The first RE in the path checks whether C
            holds a valid certificate or a pre-shared relay key. If
            verified, the AA messages from C are relayed normally.
            Otherwise, the AA messages from C are ignored.<o:p></o:p></span></p>
        <p class="MsoListParagraph"
          style="margin-left:18.0pt;text-indent:0cm"><span
            style="color:#1F497D" lang="EN-US"><o:p>&nbsp;</o:p></span></p>
        <p class="MsoNormal"><span style="color:#1F497D" lang="EN-US">Regards,<o:p></o:p></span></p>
        <p class="MsoNormal"><span style="color:#1F497D" lang="EN-US">Danping<o:p></o:p></span></p>
        <div>
          <div style="border:none;border-top:solid #B5C4DF
            1.0pt;padding:3.0pt 0cm 0cm 0cm">
            <p class="MsoNormal" style="text-align:left" align="left"><b><span
style="font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"
                  lang="EN-US">From:</span></b><span
style="font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"
                lang="EN-US"> Kumar, Sandeep [<a moz-do-not-send="true"
                  href="mailto:sandeep.kumar@philips.com">mailto:sandeep.kumar@philips.com</a>]
                <br>
                <b>Sent:</b> Tuesday, August 12, 2014 4:21 PM<br>
                <b>To:</b> Hedanping (Ana); <a moz-do-not-send="true"
                  href="mailto:ace@ietf.org">ace@ietf.org</a><br>
                <b>Subject:</b> RE: [Ace] About secure relay of
                authentication and authroization messages<o:p></o:p></span></p>
          </div>
        </div>
        <p class="MsoNormal" style="text-align:left" align="left"><span
            lang="EN-US"><o:p>&nbsp;</o:p></span></p>
        <p class="MsoNormal"><span
            style="font-size:11.0pt;color:#1F497D" lang="EN-US">Hi
            Danping<o:p></o:p></span></p>
        <p class="MsoNormal"><span
            style="font-size:11.0pt;color:#1F497D" lang="EN-US"><o:p>&nbsp;</o:p></span></p>
        <p class="MsoNormal"><span
            style="font-size:11.0pt;color:#1F497D" lang="EN-US">I think
            ACE is at a very early stage that it is better to first
            solve the problem without the relay path. At a later stage,
            the relay path can be added for scenarios that might need
            them and ofcourse DoS protection will be an important issue
            to consider then. Do you have any specific solutions to
            solve the problem? If the DoS protection solution depends
            heavily on the AA data then imho it should be solved in ACE.
            <o:p></o:p></span></p>
        <p class="MsoNormal"><span
            style="font-size:11.0pt;color:#1F497D" lang="EN-US"><o:p>&nbsp;</o:p></span></p>
        <p class="MsoNormal"><span
            style="font-size:11.0pt;color:#1F497D" lang="EN-US">Regards<o:p></o:p></span></p>
        <p class="MsoNormal"><span
            style="font-size:11.0pt;color:#1F497D" lang="EN-US">Sandeep
            &nbsp;<o:p></o:p></span></p>
        <p class="MsoNormal"><span
            style="font-size:11.0pt;color:#1F497D" lang="EN-US"><o:p>&nbsp;</o:p></span></p>
        <div>
          <div style="border:none;border-top:solid #B5C4DF
            1.0pt;padding:3.0pt 0cm 0cm 0cm">
            <p class="MsoNormal" style="text-align:left" align="left"><b><span
style="font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"
                  lang="EN-US">From:</span></b><span
style="font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"
                lang="EN-US"> Ace [<a moz-do-not-send="true"
                  href="mailto:ace-bounces@ietf.org">mailto:ace-bounces@ietf.org</a>]
                <b>On Behalf Of </b>Hedanping (Ana)<br>
                <b>Sent:</b> Tuesday, August 12, 2014 5:50 AM<br>
                <b>To:</b> <a moz-do-not-send="true"
                  href="mailto:ace@ietf.org">ace@ietf.org</a><br>
                <b>Subject:</b> [Ace] About secure relay of
                authentication and authroization messages<o:p></o:p></span></p>
          </div>
        </div>
        <p class="MsoNormal" style="text-align:left" align="left"><span
            lang="EN-US"><o:p>&nbsp;</o:p></span></p>
        <p class="MsoNormal"><span lang="EN-US">Hi, <o:p></o:p></span></p>
        <p class="MsoNormal"><span lang="EN-US">There is an issue that I
            am not sure whether it is suitable for a draft: should we
            consider secure relay of the Authentication and
            authorization (AA) messages to protect relay elements along
            the relay path?<o:p></o:p></span></p>
        <p class="MsoNormal"><span lang="EN-US"><o:p>&nbsp;</o:p></span></p>
        <p class="MsoNormal"><span lang="EN-US">DTLS relay and PANA
            relay have been proposed, however the relay elements simply
            relays the AA messages to the server. To avoid DOS attack,
            the they limit the frequency and maximum number of times to
            relay the AA requests.<o:p></o:p></span></p>
        <p class="MsoNormal"><span lang="EN-US"><o:p>&nbsp;</o:p></span></p>
        <p class="MsoNormal"><span lang="EN-US">In constraint
            environment, the relay elements might be energy constrained
            devices. If a malicious client intends to exhaust the relay
            elements&#8217; power by frequently sending AA requests with
            forged IPs or IDs, is there any countermeasure to this
            issue? Do we need to consider this issue in ACE WG?<o:p></o:p></span></p>
        <p class="MsoNormal"><span lang="EN-US"><o:p>&nbsp;</o:p></span></p>
        <p class="MsoNormal"><span lang="EN-US">Regards,<o:p></o:p></span></p>
        <p class="MsoNormal"><span lang="EN-US">Danping<o:p></o:p></span></p>
        <p class="MsoNormal" style="text-align:left" align="left"><span
            style="font-size:12.0pt;font-family:&quot;Times New
            Roman&quot;,&quot;serif&quot;" lang="EN-US"><o:p>&nbsp;</o:p></span></p>
        <div class="MsoNormal" style="text-align:center" align="center"><span
            style="font-size:12.0pt;font-family:&quot;Times New
            Roman&quot;,&quot;serif&quot;" lang="EN-US">
            <hr align="center" size="2" width="100%">
          </span></div>
        <p class="MsoNormal" style="text-align:left" align="left"><span
style="font-size:7.5pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;color:gray"
            lang="EN-US">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.</span><span
            style="font-size:12.0pt;font-family:&quot;Times New
            Roman&quot;,&quot;serif&quot;" lang="EN-US"><o:p></o:p></span></p>
      </div>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
Ace mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Ace@ietf.org">Ace@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/ace">https://www.ietf.org/mailman/listinfo/ace</a>
</pre>
    </blockquote>
    <br>
    <br>
    <pre class="moz-signature" cols="72">-- 
email: <a class="moz-txt-link-abbreviated" href="mailto:rstruik.ext@gmail.com">rstruik.ext@gmail.com</a> | Skype: rstruik
cell: +1 (647) 867-5658 | US: +1 (415) 690-7363</pre>
  </body>
</html>

--------------080706060506000506040402--


From nobody Sun Aug 31 07:49:48 2014
Return-Path: <internet-drafts@ietf.org>
X-Original-To: dtls-iot@ietfa.amsl.com
Delivered-To: dtls-iot@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 10F621A0316; Sun, 31 Aug 2014 07:49:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id suWCa840e81c; Sun, 31 Aug 2014 07:49:44 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 03AC31A028A; Sun, 31 Aug 2014 07:49:44 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 5.6.2.p5
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20140831144944.28247.22297.idtracker@ietfa.amsl.com>
Date: Sun, 31 Aug 2014 07:49:44 -0700
Archived-At: http://mailarchive.ietf.org/arch/msg/dtls-iot/v4MRnY6PESQGWfL12M8lmp8sXvg
Cc: dtls-iot@ietf.org
Subject: [Dtls-iot] I-D Action: draft-ietf-dice-profile-04.txt
X-BeenThere: dtls-iot@ietf.org
X-Mailman-Version: 2.1.15
List-Id: DTLS for IoT discussion list <dtls-iot.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dtls-iot>, <mailto:dtls-iot-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dtls-iot/>
List-Post: <mailto:dtls-iot@ietf.org>
List-Help: <mailto:dtls-iot-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dtls-iot>, <mailto:dtls-iot-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 31 Aug 2014 14:49:45 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
 This draft is a work item of the DTLS In Constrained Environments Working Group of the IETF.

        Title           : A Datagram Transport Layer Security (DTLS) 1.2 Profile for the Internet of Things
        Author          : Hannes Tschofenig
	Filename        : draft-ietf-dice-profile-04.txt
	Pages           : 24
	Date            : 2014-08-31

Abstract:
   This document defines a DTLS 1.2 profile that is suitable for
   Internet of Things applications and is reasonably implementable on
   many constrained devices.

   A common design pattern in IoT deployments is the use of a
   constrained device (typically providing sensor data) that interacts
   with the web infrastructure.  This document focuses on this
   particular pattern.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-dice-profile/

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-dice-profile-04

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-ietf-dice-profile-04


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

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


From nobody Sun Aug 31 08:33:36 2014
Return-Path: <hannes.tschofenig@gmx.net>
X-Original-To: dtls-iot@ietfa.amsl.com
Delivered-To: dtls-iot@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AED4F1A033C for <dtls-iot@ietfa.amsl.com>; Sun, 31 Aug 2014 08:33:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.568
X-Spam-Level: 
X-Spam-Status: No, score=-2.568 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.668, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Nvt52YF-Dog8 for <dtls-iot@ietfa.amsl.com>; Sun, 31 Aug 2014 08:33:33 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.20]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A19061A0341 for <dtls-iot@ietf.org>; Sun, 31 Aug 2014 08:33:32 -0700 (PDT)
Received: from [172.16.254.100] ([80.92.119.104]) by mail.gmx.com (mrgmx101) with ESMTPSA (Nemesis) id 0MaW7Z-1XhZvH1APR-00K4yv for <dtls-iot@ietf.org>; Sun, 31 Aug 2014 17:33:30 +0200
Message-ID: <54034049.5090301@gmx.net>
Date: Sun, 31 Aug 2014 17:33:29 +0200
From: Hannes Tschofenig <hannes.tschofenig@gmx.net>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.0
MIME-Version: 1.0
To: dtls-iot@ietf.org
OpenPGP: id=4D776BC9
Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="nkoMPu7pp4b62HBBdWxUhEPTCwGOMfkm1"
X-Provags-ID: V03:K0:RjmWfdqTanLGyFpz4Fxboct85azORpb/Iu5tNEntgbaGKAMFoBo w/zrlG2Cdv8kv/RwUxCcG0bWdgFj5M0U9gjwnbcmVHMrMcnqgHQ7mF8XlAc3dfayuBZetbP 0iSypjKO7xbOjSMReNeQ1Qtkr5X4DZXwlaUkNR5mRyPkIfOHdMuxWtGb9f354DMgeZgxI5r o6AR56PwJ0gNSUN6zhSAQ==
X-UI-Out-Filterresults: notjunk:1;
Archived-At: http://mailarchive.ietf.org/arch/msg/dtls-iot/ofUIpHK1-b-HZfod6fmVf6jRZQ8
Subject: [Dtls-iot] draft-ietf-dice-profile-04.txt
X-BeenThere: dtls-iot@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: DTLS for IoT discussion list <dtls-iot.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dtls-iot>, <mailto:dtls-iot-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dtls-iot/>
List-Post: <mailto:dtls-iot@ietf.org>
List-Help: <mailto:dtls-iot-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dtls-iot>, <mailto:dtls-iot-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 31 Aug 2014 15:33:35 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--nkoMPu7pp4b62HBBdWxUhEPTCwGOMfkm1
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

Hi all,

I just submitted a new version of the DTLS profile draft.

I added text about the following issues:

 * recommendation regarding the depth of the certificate chain
 * use of gmt_unix_time in the ClientHello/ServerHello (based on
[I-D.mathewson-no-gmtunixtime])
 * remark about [I-D.ietf-tls-encrypt-then-mac] not being applicable to
this profiles
 * section about TLS session hash
 * removed a few unused references
 * re-grouped the authentication credential types into one section.

Here is the diff:
http://tools.ietf.org/rfcdiff?url2=3Ddraft-ietf-dice-profile-04.txt

Here is the document:
http://tools.ietf.org/html/draft-ietf-dice-profile-04

I believe the document is ready for a working group last call.

Ciao
Hannes


--nkoMPu7pp4b62HBBdWxUhEPTCwGOMfkm1
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
Comment: GPGTools - http://gpgtools.org

iQEcBAEBCgAGBQJUA0BKAAoJEGhJURNOOiAtzOYIAIpbOuywW8BWzXGnYjq7tkBH
MMZ8gK8sId2TMnzk7O00iLxY+UzpKCnjIF2kyHwTq6Lbi5PaHkpR1LxHzh4aeI36
dQ0gsqlQZwHk8bIRBN7iakmX9yS1VapySgqVuHJIBZOZpiLdSWbTcbg4jSoVSF/8
gOJIGoaOAAQMy8JnGQoKyuqh9NWfkdj51SkDyD2ZbiLH0D8VZSBI+awSNr9MNTFw
t4d/Tp+deC8nCvPMHINmW1aG5SRpxHeivEFe8b27dGAlq269P5zbPS8sKj0GEtpp
YPOn/35RTfMmPk5IpE3ALrcNDks7PZJHKS0n1scIhzZ3c+jBPDTveOR1gPdN3j8=
=rPLP
-----END PGP SIGNATURE-----

--nkoMPu7pp4b62HBBdWxUhEPTCwGOMfkm1--

