
From nobody Mon Mar  2 01:11:32 2015
Return-Path: <ludwig@sics.se>
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 AB3BF1A700D for <dtls-iot@ietfa.amsl.com>; Mon,  2 Mar 2015 01:11:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.361
X-Spam-Level: 
X-Spam-Status: No, score=-0.361 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_LOW=-0.7, T_RP_MATCHES_RCVD=-0.01] 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 gnQBuUkp8Ntm for <dtls-iot@ietfa.amsl.com>; Mon,  2 Mar 2015 01:11:28 -0800 (PST)
Received: from outbox.sics.se (outbox.sics.se [193.10.64.137]) by ietfa.amsl.com (Postfix) with ESMTP id 724221A7008 for <dtls-iot@ietf.org>; Mon,  2 Mar 2015 01:11:27 -0800 (PST)
Received: from e-mailfilter01.sunet.se (e-mailfilter01.sunet.se [192.36.171.201]) by outbox.sics.se (Postfix) with ESMTPS id AD09D20 for <dtls-iot@ietf.org>; Mon,  2 Mar 2015 10:11:26 +0100 (CET)
Received: from norm.sics.se (norm.sics.se [193.10.64.192]) by e-mailfilter01.sunet.se (8.14.4/8.14.4/Debian-4) with ESMTP id t229BQYV026467 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for <dtls-iot@ietf.org>; Mon, 2 Mar 2015 10:11:26 +0100
Received: from [192.168.0.108] (unknown [85.235.11.178]) by norm.sics.se (Postfix) with ESMTPSA id 1D51B2F7 for <dtls-iot@ietf.org>; Mon,  2 Mar 2015 10:11:26 +0100 (CET)
Message-ID: <54F42928.4070409@sics.se>
Date: Mon, 02 Mar 2015 10:11:04 +0100
From: Ludwig Seitz <ludwig@sics.se>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
MIME-Version: 1.0
To: dtls-iot@ietf.org
References: <258751E5-69DB-4787-A7EE-B6C955225AA4@arm.com>
In-Reply-To: <258751E5-69DB-4787-A7EE-B6C955225AA4@arm.com>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="------------ms060204090008010704020106"
X-Bayes-Prob: 0.5 (Score 0, tokens from: outbound, outbound-sics-se:default, sics-se:default, base:default, @@RPTN)
X-p0f-Info: os=Linux 2.2.x-3.x, link=Ethernet or modem
X-CanIt-Geo: =?UTF-8?Q?ip=3D85.235.11.178; _country=3DSE; _region=3DSk=C3=A5ne; _city=3DLund; _latitude=3D55.7028; _longitude=3D13.1927; _http://maps.google.com/maps=3Fq=3D55.7028,13.1927&z=3D6?=
X-CanItPRO-Stream: outbound-sics-se:outbound (inherits from outbound-sics-se:default, sics-se:default, base:default)
X-Canit-Stats-ID: 09NWxbqMU - e77364139e3c - 20150302
X-Antispam-Training-Forget: https://canit.sunet.se/canit/b.php?i=09NWxbqMU&m=e77364139e3c&t=20150302&c=f
X-Antispam-Training-Nonspam: https://canit.sunet.se/canit/b.php?i=09NWxbqMU&m=e77364139e3c&t=20150302&c=n
X-Antispam-Training-Spam: https://canit.sunet.se/canit/b.php?i=09NWxbqMU&m=e77364139e3c&t=20150302&c=s
X-CanIt-Archive-Cluster: PfMRe/vJWMiXwM2YIH5BVExnUnw
Received-SPF: neutral (e-mailfilter01.sunet.se: 85.235.11.178 is neither permitted nor denied by domain ludwig@sics.se) receiver=e-mailfilter01.sunet.se; client-ip=85.235.11.178; envelope-from=<ludwig@sics.se>; helo=norm.sics.se; identity=mailfrom
X-Scanned-By: CanIt (www . roaringpenguin . com) on 192.36.171.201
Archived-At: <http://mailarchive.ietf.org/arch/msg/dtls-iot/sio4_uEKu72KAn4zlgzdL-mlLjA>
Subject: Re: [Dtls-iot] 2nd WGLC on draft-ietf-dice-profile, ending Feb 6th
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: Mon, 02 Mar 2015 09:11:31 -0000

This is a cryptographically signed message in MIME format.

--------------ms060204090008010704020106
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: quoted-printable

On 01/26/2015 02:28 PM, Zach Shelby wrote:
> This mail kicks off a 2nd WGLC for our DTLS profile draft:
>
> https://tools.ietf.org/html/draft-ietf-dice-profile-09
>
> This WGLC will end of Friday, Feb 6th, 2015. Please send your reviews t=
o
> this mailing list. The authors have identified some key reviewers, in
> addition to those that volunteered in Honolulu.
>
> Thanks!
> Zach & Dorothy
>

Hello list,

although the WGLC has ended, I have been asked to provide an additional=20
review by Hannes Tschofenig, which I hereby do.

I have divided my findings into "issues", "typos" and "nits":


Issues (3):

Section 4.1.1.2. CoAP-based Data Exchange Example

I'm not sure that the Resource Directory is intended to relay requests.=20
To my knowledge it is just intended as a lookup service to find out=20
metadata about available resources. It would be good to check this with=20
e.g. Zach or Carsten.

---
Section 6

Is it intentional that section 6 mandates that a device that wants to=20
comply with this profile MUST implement ALL OF 6.1, 6.2 and 6.3?

So a device just implementing DTLS PSK mode with the guidance from 6.1=20
would not be considered compliant?

If the answer is yes, this seems to place quite a code-size burden
on constrained devices.

---
Section 9. Session Resumption

Note that the TLS WG discussed dropping session resumption for
TLS 1.3 during IETF 89, see slide 4 in
http://www.ietf.org/proceedings/89/slides/slides-89-tls-5.pdf.
We should check the status of this before we produce RFCs that rely on=20
this mechanism.

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
Typos (6):

3.  TLS/DTLS Protocol Overview, second bullet

"is exclusive-ORed with an dentical amount"

Should read "identical"
---
"Figure 2: Network Access Architecture.."

Remove last period.
---
Figure 6  Local Discovery and Resouce Access.

The "Configure ..." arrow is missing its arrowhead.
---
5. The TLS/DTLS Ciphersuite Concept, 5th bullet

"(e.g., HMAC with the SHA-256)"

delete "the"
---
8.  Error Handling

"Those include decryption_failed_RESERVED, no_certificate_RESERVE, and=20
export_restriction_RESERVED."

should read "no_certificate_RESERVED" (give us a 'D'!)
---
14.  Random Number Generation
"Since many IoT devices do not have access to a real-time clock this=20
recommendation it is RECOMMENDED to follow the guidance outlined in ..."

delete "this recommendation"
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
Nits (10):

Abstract:
This gives the impression that we are only dealing with devices=20
providing data in form of e.g. sensor readings. An equally common=20
pattern would be an actuator that controls some physical system, like a=20
valve, a thermostat or a smart light bulb.

---

3.  TLS/DTLS Protocol Overview, first paragraph

"The protocol is composed of two layers: the Record Protocol and the=20
Handshake Protocol."

There are actually two other protocols in TLS/DTLS, the change cipher
spec protocol and the alert protocol, although they are subsumed=20
together with the handshake protocol as the "handshaking protocols" in=20
the RFC.

---
3.  TLS/DTLS Protocol Overview, last bullet

"Furthermore, the handshake message format has been extended to deal=20
with message loss, reordering, and fragmentation.  Retransmission timers =

have been included to deal with message loss."

This sounds weird due to the repetition of "message loss". Does the=20
message format really have any role in dealing with message loss?

---
4.1.1.1.  Network Access Authentication Example, second paragraph

"To route EAP messages ..., name RADIUS or Diameter."

A citation of the rfcs would be appropriate here
[RFC2865] and [RFC6733].

---
4.1.1.1.  Network Access Authentication Example, pages 7-8

"The EAP-TLS exchange is shown in Figure 3 where it is worthwhile to=20
point out that in EAP the client / server roles are reversed but with=20
the use of EAP-TLS the IoT device acts as a TLS client.

This last sentence is unclear, reversed with respect to what? Does the
TLS client become the EAP server?
---
4.1.1.2.  CoAP-based Data Exchange Example, second paragraph

"Figure 4 shows a sensor starting with a DTLS exchange with a resource
    directory to register available resources."

I'd remove the first "with"
---
6.3.  Certificates, page 22

"Note that the Service Name ... to convey EUI-64 identifiers."

The citation [EUI64] appearing later in the text should be here instead.
---
8. Error Handling
"TLS/DTLS uses the Alert protocol to convey error messages and=20
specifies a longer list of errors."

Longer than what?
---
14.  Random Number Generation
"Special care has to be paid when generating random numbers ..."

"pay attention" but "take care", I'd say "Special care has to be
taken..."
---
14.  Random Number Generation

followed by a random sequence of 28 random bytes

delete the first "random"

--=20
Ludwig Seitz, PhD
SICS Swedish ICT AB
Ideon Science Park
Building Beta 2
Scheelev=E4gen 17
SE-223 70 Lund

Phone +46(0)70-349 92 51
http://www.sics.se


--------------ms060204090008010704020106
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIMVDCC
BhgwggUAoAMCAQICAwyGmDANBgkqhkiG9w0BAQUFADCBjDELMAkGA1UEBhMCSUwxFjAUBgNV
BAoTDVN0YXJ0Q29tIEx0ZC4xKzApBgNVBAsTIlNlY3VyZSBEaWdpdGFsIENlcnRpZmljYXRl
IFNpZ25pbmcxODA2BgNVBAMTL1N0YXJ0Q29tIENsYXNzIDEgUHJpbWFyeSBJbnRlcm1lZGlh
dGUgQ2xpZW50IENBMB4XDTE1MDEwODA4MzkwNloXDTE2MDEwOTIyNDEzMFowODEXMBUGA1UE
AwwObHVkd2lnQHNpY3Muc2UxHTAbBgkqhkiG9w0BCQEWDmx1ZHdpZ0BzaWNzLnNlMIIBIjAN
BgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAxUHisC6rgXFsBHHBGo8ulz/cLX3gX5Ufhcwo
rp+7djzMMuKPM1KOHq0bjWhmFe8ly8CzWdk2NS600t7IEBQWJiHLsdc12UqmNswQUpD7oqkR
1nRGT6leAHYTWapkR+nczZ2NxD+H7u4ZWVIZg0DFiTqtY8ghYHHYYy8BBoc/jHG78X4+JJAg
s5XOa0gVl7W38vDvVpo14xhWEBGjzPk9WxWirqAF66PF+JEu2JD9LzFbpEq829SRXJMFB9wp
oQNlH0UQ01/2sWCIBxPpHuEjxEF/V3Z/F2VsNTy4zvYrd+/MYO3w30F+bWQNZsMHEkTW1pEh
iz7rQPWTBXoO8Fv0wQIDAQABo4IC1DCCAtAwCQYDVR0TBAIwADALBgNVHQ8EBAMCBLAwHQYD
VR0lBBYwFAYIKwYBBQUHAwIGCCsGAQUFBwMEMB0GA1UdDgQWBBTqvKspqEm0E4R1sgsABYKk
6xDJqDAfBgNVHSMEGDAWgBRTcu2SnODaywFcfH6WNU7y1LhRgjAZBgNVHREEEjAQgQ5sdWR3
aWdAc2ljcy5zZTCCAUwGA1UdIASCAUMwggE/MIIBOwYLKwYBBAGBtTcBAgMwggEqMC4GCCsG
AQUFBwIBFiJodHRwOi8vd3d3LnN0YXJ0c3NsLmNvbS9wb2xpY3kucGRmMIH3BggrBgEFBQcC
AjCB6jAnFiBTdGFydENvbSBDZXJ0aWZpY2F0aW9uIEF1dGhvcml0eTADAgEBGoG+VGhpcyBj
ZXJ0aWZpY2F0ZSB3YXMgaXNzdWVkIGFjY29yZGluZyB0byB0aGUgQ2xhc3MgMSBWYWxpZGF0
aW9uIHJlcXVpcmVtZW50cyBvZiB0aGUgU3RhcnRDb20gQ0EgcG9saWN5LCByZWxpYW5jZSBv
bmx5IGZvciB0aGUgaW50ZW5kZWQgcHVycG9zZSBpbiBjb21wbGlhbmNlIG9mIHRoZSByZWx5
aW5nIHBhcnR5IG9ibGlnYXRpb25zLjA2BgNVHR8ELzAtMCugKaAnhiVodHRwOi8vY3JsLnN0
YXJ0c3NsLmNvbS9jcnR1MS1jcmwuY3JsMIGOBggrBgEFBQcBAQSBgTB/MDkGCCsGAQUFBzAB
hi1odHRwOi8vb2NzcC5zdGFydHNzbC5jb20vc3ViL2NsYXNzMS9jbGllbnQvY2EwQgYIKwYB
BQUHMAKGNmh0dHA6Ly9haWEuc3RhcnRzc2wuY29tL2NlcnRzL3N1Yi5jbGFzczEuY2xpZW50
LmNhLmNydDAjBgNVHRIEHDAahhhodHRwOi8vd3d3LnN0YXJ0c3NsLmNvbS8wDQYJKoZIhvcN
AQEFBQADggEBAGXwFsbSfv4mMWqIk64CoxuR6ozo7J37igca7d9tpKIzVIp6xp7Zt+a+J9X3
1r4zgMRFnZJWQ5hy82W/fVDeG9i3NGMM6p7DNUrGjTbVHd11BQtbUOG9MSlyWKQbmt3Q1ElC
f4SRLAQot5SPryLR2FTxQuFkMOrcDzVxNxnMgatOM2fAO8KS0H+wX+I7gC3pEnbg/eMqNgU+
Ktbc2y9naDNmLNLN65s8TT9xZyoQEn9S1oU8Xnh596OMu49Eccws8Ny+vAGESIHG4bqhMSjj
rmDilL1Wj9nQahmBnID5oZD5g9s9KyqxiZIGNnowYYOpCrSeITZ1b7wg50dC8ySojnYwggY0
MIIEHKADAgECAgEeMA0GCSqGSIb3DQEBBQUAMH0xCzAJBgNVBAYTAklMMRYwFAYDVQQKEw1T
dGFydENvbSBMdGQuMSswKQYDVQQLEyJTZWN1cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWdu
aW5nMSkwJwYDVQQDEyBTdGFydENvbSBDZXJ0aWZpY2F0aW9uIEF1dGhvcml0eTAeFw0wNzEw
MjQyMTAxNTVaFw0xNzEwMjQyMTAxNTVaMIGMMQswCQYDVQQGEwJJTDEWMBQGA1UEChMNU3Rh
cnRDb20gTHRkLjErMCkGA1UECxMiU2VjdXJlIERpZ2l0YWwgQ2VydGlmaWNhdGUgU2lnbmlu
ZzE4MDYGA1UEAxMvU3RhcnRDb20gQ2xhc3MgMSBQcmltYXJ5IEludGVybWVkaWF0ZSBDbGll
bnQgQ0EwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQDHCYPMzi3YGrEppC4Tq5a+
ijKDjKaIQZZVR63UbxIP6uq/I0fhCu+cQhoUfE6ERKKnu8zPf1Jwuk0tsvVCk6U9b+0UjM0d
Lep3ZdE1gblK/1FwYT5Pipsu2yOMluLqwvsuz9/9f1+1PKHG/FaR/wpbfuIqu54qzHDYeqiU
fsYzoVflR80DAC7hmJ+SmZnNTWyUGHJbBpA8Q89lGxahNvuryGaC/o2/ceD2uYDX9U8Eg5Dp
IpGQdcbQeGarV04WgAUjjXX5r/2dabmtxWMZwhZna//jdiSyrrSMTGKkDiXm6/3/4ebfeZuC
YKzN2P8O2F/Xe2AC/Y7zeEsnR7FOp+uXAgMBAAGjggGtMIIBqTAPBgNVHRMBAf8EBTADAQH/
MA4GA1UdDwEB/wQEAwIBBjAdBgNVHQ4EFgQUU3Ltkpzg2ssBXHx+ljVO8tS4UYIwHwYDVR0j
BBgwFoAUTgvvGqRAW6UXaYcwyjRoQ9BBrvIwZgYIKwYBBQUHAQEEWjBYMCcGCCsGAQUFBzAB
hhtodHRwOi8vb2NzcC5zdGFydHNzbC5jb20vY2EwLQYIKwYBBQUHMAKGIWh0dHA6Ly93d3cu
c3RhcnRzc2wuY29tL3Nmc2NhLmNydDBbBgNVHR8EVDBSMCegJaAjhiFodHRwOi8vd3d3LnN0
YXJ0c3NsLmNvbS9zZnNjYS5jcmwwJ6AloCOGIWh0dHA6Ly9jcmwuc3RhcnRzc2wuY29tL3Nm
c2NhLmNybDCBgAYDVR0gBHkwdzB1BgsrBgEEAYG1NwECATBmMC4GCCsGAQUFBwIBFiJodHRw
Oi8vd3d3LnN0YXJ0c3NsLmNvbS9wb2xpY3kucGRmMDQGCCsGAQUFBwIBFihodHRwOi8vd3d3
LnN0YXJ0c3NsLmNvbS9pbnRlcm1lZGlhdGUucGRmMA0GCSqGSIb3DQEBBQUAA4ICAQAKgwh9
eKssBly4Y4xerhy5I3dNoXHYfYa8PlVLL/qtXnkFgdtY1o95CfegFJTwqBBmf8pyTUnFsukD
FUI22zF5bVHzuJ+GxhnSqN2sD1qetbYwBYK2iyYA5Pg7Er1A+hKMIzEzcduRkIMmCeUTyMyi
kfbUFvIBivtvkR8ZFAk22BZy+pJfAoedO61HTz4qSfQoCRcLN5A0t4DkuVhTMXIzuQ8Cnykh
ExD6x4e6ebIbrjZLb7L+ocR0y4YjCl/Pd4MXU91y0vTipgr/O75CDUHDRHCCKBVmz/Rzkc/b
970MEeHt5LC3NiWTgBSvrLEuVzBKM586YoRD9Dy3OHQgWI270g+5MYA8GfgI/EPT5G7xPbCD
z+zjdH89PeR3U4So4lSXur6H6vp+m9TQXPF3a0LwZrp8MQ+Z77U1uL7TelWO5lApsbAonrqA
SfTpaprFVkL4nyGH+NHST2ZJPWIBk81i6Vw0ny0qZW2Niy/QvVNKbb43A43ny076khXO7cNb
BIRdJ/6qQNq9Bqb5C0Q5nEsFcj75oxQRqlKf6TcvGbjxkJh8BYtv9ePsXklAxtm8J7GCUBth
HSQgepbkOexhJ0wP8imUkyiPHQ0GvEnd83129fZjoEhdGwXV27ioRKbj/cIq7JRXun0NbeY+
UdMYu9jGfIpDLtUUGSgsg2zMGs5R4jGCA90wggPZAgEBMIGUMIGMMQswCQYDVQQGEwJJTDEW
MBQGA1UEChMNU3RhcnRDb20gTHRkLjErMCkGA1UECxMiU2VjdXJlIERpZ2l0YWwgQ2VydGlm
aWNhdGUgU2lnbmluZzE4MDYGA1UEAxMvU3RhcnRDb20gQ2xhc3MgMSBQcmltYXJ5IEludGVy
bWVkaWF0ZSBDbGllbnQgQ0ECAwyGmDAJBgUrDgMCGgUAoIICHTAYBgkqhkiG9w0BCQMxCwYJ
KoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0xNTAzMDIwOTExMDRaMCMGCSqGSIb3DQEJBDEW
BBS4mniEZ3kNBwf3VxKWur8Pf/z7EjBsBgkqhkiG9w0BCQ8xXzBdMAsGCWCGSAFlAwQBKjAL
BglghkgBZQMEAQIwCgYIKoZIhvcNAwcwDgYIKoZIhvcNAwICAgCAMA0GCCqGSIb3DQMCAgFA
MAcGBSsOAwIHMA0GCCqGSIb3DQMCAgEoMIGlBgkrBgEEAYI3EAQxgZcwgZQwgYwxCzAJBgNV
BAYTAklMMRYwFAYDVQQKEw1TdGFydENvbSBMdGQuMSswKQYDVQQLEyJTZWN1cmUgRGlnaXRh
bCBDZXJ0aWZpY2F0ZSBTaWduaW5nMTgwNgYDVQQDEy9TdGFydENvbSBDbGFzcyAxIFByaW1h
cnkgSW50ZXJtZWRpYXRlIENsaWVudCBDQQIDDIaYMIGnBgsqhkiG9w0BCRACCzGBl6CBlDCB
jDELMAkGA1UEBhMCSUwxFjAUBgNVBAoTDVN0YXJ0Q29tIEx0ZC4xKzApBgNVBAsTIlNlY3Vy
ZSBEaWdpdGFsIENlcnRpZmljYXRlIFNpZ25pbmcxODA2BgNVBAMTL1N0YXJ0Q29tIENsYXNz
IDEgUHJpbWFyeSBJbnRlcm1lZGlhdGUgQ2xpZW50IENBAgMMhpgwDQYJKoZIhvcNAQEBBQAE
ggEAIFahAHk+C8u3KZ0KVxmAbp/EY+2B5FG2a73o+KqKLF4dh4sfJ+n6ypUZa2s/fx2sQX4O
hT0Hf5pIMy3xUWabyYVTJLvh4dHilPGow2bMsg8uQMuXeR++qhrxbMzmckFxVgMZsmSBbWZ8
SsYwEEhxOwAvbWZXtjD+VWW9BQ8++bYdMm2SxHFrIFLo6AZO1CFoN/VoqW+liL0mSfm1sPMm
yzOjP4lAyV0sKqhkrgeHGkvew0nr7TI0elmLZJHNj8AGSc6B3nH//UjpC+FO0uK3uz63ksgZ
c/yjPFIqhCrXaxuccSVvaxLQAd9lhBjrcXAXl19Bpo0GzKSlWzd7wWSHjwAAAAAAAA==
--------------ms060204090008010704020106--


From nobody Thu Mar  5 04:58:50 2015
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 8BDAC1B2C77 for <dtls-iot@ietfa.amsl.com>; Thu,  5 Mar 2015 04:58:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 Dj3sn39wbt9L for <dtls-iot@ietfa.amsl.com>; Thu,  5 Mar 2015 04:58:46 -0800 (PST)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.21]) (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 7255A1A01A9 for <dtls-iot@ietf.org>; Thu,  5 Mar 2015 04:58:46 -0800 (PST)
Received: from [192.168.131.142] ([80.92.121.102]) by mail.gmx.com (mrgmx103) with ESMTPSA (Nemesis) id 0MMTZa-1YOY5S078I-008Jh0; Thu, 05 Mar 2015 13:58:44 +0100
Message-ID: <54F85302.5030702@gmx.net>
Date: Thu, 05 Mar 2015 13:58:42 +0100
From: Hannes Tschofenig <hannes.tschofenig@gmx.net>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
MIME-Version: 1.0
To: "Rahman, Akbar" <Akbar.Rahman@InterDigital.com>,  "dtls-iot@ietf.org" <dtls-iot@ietf.org>
References: <36F5869FE31AB24485E5E3222C288E1F0BA3C6@NABESITE.InterDigital.com>
In-Reply-To: <36F5869FE31AB24485E5E3222C288E1F0BA3C6@NABESITE.InterDigital.com>
OpenPGP: id=4D776BC9
Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="2HxIuimE19HgFgTkl31xPUQam9HlENCO3"
X-Provags-ID: V03:K0:4z0dAsjjwktn7+mLaU0EDXUgsGonIK/DE1MfD8qLgz6/M3TRKql I6NeiTgq2bFrRCnp6VS5FXrKo6MQincsUbpf/7iL9uKUcHQvl6kpdsv7fN1sHpuahdPaN2L OtACjHzCCztuelYpcL+ZQpq0G9u5tHrmzP2gbHLifqq+zDycpEInwlodtxgH7VrEy1p6y00 uVStPrrLJmRuKqVFEyeiw==
X-UI-Out-Filterresults: notjunk:1;
Archived-At: <http://mailarchive.ietf.org/arch/msg/dtls-iot/M_0SM9skhZaDlKp3Xx_vI2HNsnM>
Subject: Re: [Dtls-iot] 2nd WGLC on draft-ietf-dice-profile, ending Feb 6th
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: Thu, 05 Mar 2015 12:58:49 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--2HxIuimE19HgFgTkl31xPUQam9HlENCO3
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

Hi Akbar,

thanks for your review comments.

On 02/03/2015 11:13 PM, Rahman, Akbar wrote:
> Hi,
>=20
> =20
>=20
> =20
>=20
> Thanks to the authors for the good work.  I reviewed the latest draft
> and support progressing it.  I only had a few minor comments:
>=20
> =20
>=20
> =20
>=20
> 1)      The phrase =93TLS/DTLS 1.2=94 is used in various forms in the
> draft.  However, it makes for awkward reading in some places, especiall=
y
> in the title of the draft.  Specifically, do we need to refer to versio=
n
> =931.2=94 in the title?

I removed the version number from the title.

Whenever the text was applicable to both versions (DTLS and TLS) I
indicated it with TLS/DTLS. If the text was only applicable to TLS or
DTLS I used TLS and DTLS, respectively.

Hence, I prefer to keep the TLS/DTLS indication to make the difference
clear in the text.
>=20
> =20
>=20
> 2)      There is a reference to a CoAP endpoint =93URL=94 in section 4.=
1.=20
>  However, in CoAP [RFC 7252] itself the term =93URI=94 is used in this
> context.  Was there a reason to change the terminology in this draft?
>=20

I changed the sentence and referred to the URI rather to a URL

>=20
> 3)       If Appendix A information is normative (as it indicates), what=

> was the specific reason for parking this info in an Appendix which is
> usually meant for optional/less-important material?  Also, has running
> DTLS over SMS been successfully implemented anywhere that the authors
> know of?
I put the text into the appendix since it appears to be relevant only to
smaller audience (compared to the rest of the document). Note that it is
not uncommon to put normative text into the appendix.

Part of it was implemented (namely the PSK version) but not the public
key-based variants. Note that the generic recommendations derived from
the SMS experience as a transport (particularly the timeout aspects) are
included in the main part of the document.

Ciao
Hannes

>=20
> =20
>=20
> =20
>=20
> Best Regards,
>=20
> =20
>=20
> =20
>=20
> Akbar
>=20
> =20
>=20
> -----------------------------------------------------------------------=
-
>=20
>   * /From/: Zach Shelby <Zach.Shelby at arm.com
>     <mailto:Zach.Shelby@DOMAIN.HIDDEN>>
>   * /To/: "dtls-iot at ietf.org <mailto:dtls-iot@DOMAIN.HIDDEN>"
>     <dtls-iot at ietf.org <mailto:dtls-iot@DOMAIN.HIDDEN>>
>   * /Date/: Mon, 26 Jan 2015 05:28:12 -0800
>   * /List-id/: DTLS for IoT discussion list <dtls-iot.ietf.org>
>=20
> -----------------------------------------------------------------------=
-
>=20
> This mail kicks off a 2nd WGLC for our DTLS profile draft:
>=20
> =20
>=20
> https://tools.ietf.org/html/draft-ietf-dice-profile-09=20
>=20
> =20
>=20
> This WGLC will end of Friday, Feb 6th, 2015. Please send your reviews t=
o
> this mailing list. The authors have identified some key reviewers, in
> addition to those that volunteered in Honolulu.
>=20
> =20
>=20
> Thanks!
>=20
> Zach & Dorothy
>=20
> =20
>=20
>=20
>=20
> -- IMPORTANT NOTICE: The contents of this email and any attachments are=

> confidential and may also be privileged. If you are not the intended
> recipient, please notify the sender immediately and do not disclose the=

> contents to any other person, use it for any purpose, or store or copy
> the information in any medium. Thank you.
>=20
> ARM Limited, Registered office 110 Fulbourn Road, Cambridge CB1 9NJ,
> Registered in England & Wales, Company No: 2557590
> ARM Holdings plc, Registered office 110 Fulbourn Road, Cambridge CB1
> 9NJ, Registered in England & Wales, Company No: 2548782
>=20
> -----------------------------------------------------------------------=
-
>=20
> =20
>=20
>=20
>=20
> _______________________________________________
> dtls-iot mailing list
> dtls-iot@ietf.org
> https://www.ietf.org/mailman/listinfo/dtls-iot
>=20


--2HxIuimE19HgFgTkl31xPUQam9HlENCO3
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

iQEcBAEBCgAGBQJU+FMCAAoJEGhJURNOOiAtcv0IAJJHhAjiI9JjJ6cis9oxbYe/
ULPrGJdE0KHoZWi2ke6XN2RnhC507KjDpEg/cLBVEDDSUAzjLdktdyAgOl29ZtxZ
/OlSm/5NTMjqQXFhZeltbmUQsmv83RPLm6muVbyueyXduHRWcPsGDzEUE1Ou656j
lLKtGCls+HJHqgo86Q309YoJThjXEzrLUX6FUrPmhJOBeceUUF0bJXtGk6vKoQqu
vkzZuK0dXqDQUyLfyKU7l849fJcLzt1HdXJpU0cyW6YX8LgX9kZKvnOZzH4WaHPx
0JTghzQW1hxLvYqaJG7ko3VjS5UVYHFgqRnnytPhKfI0RiYnBDodCruBI7+JoC4=
=d3/i
-----END PGP SIGNATURE-----

--2HxIuimE19HgFgTkl31xPUQam9HlENCO3--


From nobody Thu Mar  5 06:26:44 2015
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 EBFBA1A016B for <dtls-iot@ietfa.amsl.com>; Thu,  5 Mar 2015 06:26:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 DF_azS3VZmIX for <dtls-iot@ietfa.amsl.com>; Thu,  5 Mar 2015 06:26:38 -0800 (PST)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.21]) (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 132431A0687 for <dtls-iot@ietf.org>; Thu,  5 Mar 2015 06:20:26 -0800 (PST)
Received: from [192.168.131.142] ([80.92.121.102]) by mail.gmx.com (mrgmx102) with ESMTPSA (Nemesis) id 0MV30j-1Xxp1z2oFZ-00YV8Q; Thu, 05 Mar 2015 15:20:18 +0100
Message-ID: <54F86621.3000705@gmx.net>
Date: Thu, 05 Mar 2015 15:20:17 +0100
From: Hannes Tschofenig <hannes.tschofenig@gmx.net>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: Kovatsch Matthias <kovatsch@inf.ethz.ch>,  "dtls-iot@ietf.org" <dtls-iot@ietf.org>
References: <36F5869FE31AB24485E5E3222C288E1F0BA3C6@NABESITE.InterDigital.com> <55877B3AFB359744BA0F2140E36F52B53543FAC4@MBX110.d.ethz.ch>
In-Reply-To: <55877B3AFB359744BA0F2140E36F52B53543FAC4@MBX110.d.ethz.ch>
OpenPGP: id=4D776BC9
Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="7jKekxP1rEfOhut7vCE0XTeGUtIb804sJ"
X-Provags-ID: V03:K0:jfIahfkjOpDwIXXpYzeFgr3ANSfXipOX7jfqAoIVvqpIQUsPpzV Osg+ecm4x2uxSIHh1jBZOsHWcsjCfELfpyLr40icr0qv5GzAtl7q5PNAMJ3VE+aLFCr6ltS gIN/66VJQh6cQTWGDSwsyWdQtwe+mWW2sFk9SiIP8zv//Tvj8S7+FHO2mDQLmRQ18WNpHQY 3FDZkQdEcPzh/dChtLvNg==
X-UI-Out-Filterresults: notjunk:1;
Archived-At: <http://mailarchive.ietf.org/arch/msg/dtls-iot/dY6Yp7rHpic7V9DYVD6p_wP9Kk4>
Subject: Re: [Dtls-iot] 2nd WGLC on draft-ietf-dice-profile, ending Feb 6th
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: Thu, 05 Mar 2015 14:26:43 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--7jKekxP1rEfOhut7vCE0XTeGUtIb804sJ
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

Hi Matthias,

thanks for the review. Remarks inline:

On 02/06/2015 06:10 PM, Kovatsch Matthias wrote:> Dear authors,
>
> dear group
>
>
>
> I really like this document since it gives a great overview of what
> developers should know about (D)TLS. Most of my comments are of
> editorial nature:
>
>
>
> Page 4: =93with an dentical amount=94 =E0missing =91i=92
>

Fixed.

>
>
> Page 5 (4.1):
>
> -        URL =E0URI
Fixed.

>
> -        =93the CoAP needs to register and publish to=94 =E0=93to which=
 CoAP
> needs to register and publish=94

Changed to:

"
Before a client can initiate the TLS/DTLS handshake it needs to know the
IP address of that server and what credentials to use. Application layer
protocols, such as CoAP, which is conveyed on top of DTLS, may be
configured with URIs of the endpoints to which CoAP needs to register
and publish data.
"

>
> -        For the public key crypto, I am missing the private key of the=

> client. I think the bullet list and Figure one should mention it someho=
w
> to make developers aware that using client authentication is the defaul=
t
> in the IoT.

Good point.

>
>
>
> Page 7 (4.1.1.1): =93protocol mechanism, name RADIUS or Diameter=94 =E0=
=93namely=94
>
>

Fixed.


>
> Page 10 (4.1.1.2):
>
> -        It would be clearer to point out that the IoT device changes
> roles after initiating the DTLS handshake with an initial CoAP request
> (e.g., RD registration).

I looked at the message exchange again and it does not look too bad.
Ultimately, the document is about TLS/DTLS rather than a detailed
description about CoAP.


>
> -        There are a lot of references to the RD draft; maybe we can
> remove the second occurrence.

Removed some of them.


>
> -        By default, the RD is not a proxy. The model described in
> 4.1.1.2 comes from OMA LWM2M! Since this specification is referenced in=

> Section 25 anyway, I would use it here as well for the use case.
>

Good point. I added the reference and adjusted the sentences.

>
>
> Page 14 (4.2): When the multicast discovery uses CoAP without DTLS, but=

> the other resources provide CoAPS, I would expect an absolute URI with
> the =91coaps=92 scheme in the CoRE Link Format. URIs with the same auth=
ority
> and URI path but different schemes refer to different resources. Only b=
y
> =93coincidence=94 they usually end up at the same document (HTTP(S)) or=
 data
> point.

Good that you raised this point.

What would I put in these coaps URIs? The problem is that I have to
compare the content of the certificate with the URI.

>
>
>
> Page 15 (4.2): I am missing the RD under =93Discovery and Reachability.=
=94
> As stated above, the RD is usually not a proxy and client endpoints can=

> discover links there, but then access them directly. How this is done i=
s
> out of scope in this document (see ACE work).
>

Added.

>
>
> Page 20 (6.1): =93In general, servers SHOULD NOT send the PSK identity
> hint [..] and client MUST ignore the message.=94 =E0I find this confusi=
ng,
> mostly because of =93in general.=94 There are cases where this feature =
is
> required, but this could lead to many clients (worse implementations)
> that always ignore the hint. It should be more specific that this text
> only applies when the feature is explicitly not required. Editorial:
> =93clients=94 is missing the =91s=92
>

I removed the "in general".


The reason we put that statement in there is that we couldn't figure out
how to use it in an IoT context.



>
>
> Page 21 (6.2):
>
> -        OMA LWM2M provides bootstrapping mechanisms to install new
> keying material. This does not require a full firmware update. I am
> expecting more solutions that provide such a feature.

I agree.

>
> -        =93This ciphersuite make use=94 =E0makes

fixed.

>
>
>
> Page 27 (8): I still believe it is much more helpful to have the list o=
f
> applicable error messages in the document instead of those not applicab=
le.

The problem is that those might get out of date fairly quickly when new
error messages are added with extensions.

>
>
>
> Page 31 (13): =93and twice the value=94 =E0knowing CoAP I assume the va=
lue is
> doubled each time, but the word =93twice=94 (or short sentence) does no=
t
> clearly say that in my opinion.
>

Ack

>
> Page 37 (21): =93to an the=94 =E0only =93the=94
>
>
Ack.

>
> Page 27 (22):
>
> -        =93and a 233 bit ECC keys=94 =E0=93a 233-bit key=94 (or plural=
 in all
cases)
>
Ack.

> -        =93The use 80-bit=94 =E0=93The 80-bit encryption used=94 ?

Changed it to
"
The authors of [ENISA-Report2013] add that a 80-bit symmetric key is
sufficient for legacy applications for the coming years, but a 128-bit
symmetric key is the minimum requirement for new systems being deployed.
The authors further note that one needs to also take into account the
length of time data needs to be kept secure for. The use of 80-bit
symmetric keys for transactional data may be acceptable for the near
future while one has to insist on 128-bit symmetric keys for long lived
data.
"


Ciao
Hannes


>
>
>
> Best regards
>
> Matthias
>
>
>
>
>
>
>
> *From:* dtls-iot [mailto:dtls-iot-bounces@ietf.org] *On Behalf Of
> *Rahman, Akbar
> *Sent:* Tuesday, 3 February 2015 23:14
> *To:* dtls-iot@ietf.org
> *Subject:* [Dtls-iot] 2nd WGLC on draft-ietf-dice-profile, ending Feb 6=
th
>
>
>
> Hi,
>
>
>
>
>
> Thanks to the authors for the good work.  I reviewed the latest draft
> and support progressing it.  I only had a few minor comments:
>
>
>
>
>
> 1)      The phrase =93TLS/DTLS 1.2=94 is used in various forms in the
> draft.  However, it makes for awkward reading in some places, especiall=
y
> in the title of the draft.  Specifically, do we need to refer to versio=
n
> =931.2=94 in the title?
>
>
>
> 2)      There is a reference to a CoAP endpoint =93URL=94 in section 4.=
1.
>  However, in CoAP [RFC 7252] itself the term =93URI=94 is used in this
> context.  Was there a reason to change the terminology in this draft?
>
>
>
> 3)       If Appendix A information is normative (as it indicates), what=

> was the specific reason for parking this info in an Appendix which is
> usually meant for optional/less-important material?  Also, has running
> DTLS over SMS been successfully implemented anywhere that the authors
> know of?
>
>
>
>
>
> Best Regards,
>
>
>
>
>
> Akbar
>
>
>
> -----------------------------------------------------------------------=
-
>
>   * /From/: Zach Shelby <Zach.Shelby at arm.com
>     <mailto:Zach.Shelby@DOMAIN.HIDDEN>>
>   * /To/: "dtls-iot at ietf.org <mailto:dtls-iot@DOMAIN.HIDDEN>"
>     <dtls-iot at ietf.org <mailto:dtls-iot@DOMAIN.HIDDEN>>
>   * /Date/: Mon, 26 Jan 2015 05:28:12 -0800
>   * /List-id/: DTLS for IoT discussion list <dtls-iot.ietf.org>
>
> -----------------------------------------------------------------------=
-
>
> This mail kicks off a 2nd WGLC for our DTLS profile draft:
>
>
>
> https://tools.ietf.org/html/draft-ietf-dice-profile-09
>
>
>
> This WGLC will end of Friday, Feb 6th, 2015. Please send your reviews t=
o
> this mailing list. The authors have identified some key reviewers, in
> addition to those that volunteered in Honolulu.
>
>
>
> Thanks!
>
> Zach & Dorothy
>
>
>
>
>
> -- IMPORTANT NOTICE: The contents of this email and any attachments are=

> confidential and may also be privileged. If you are not the intended
> recipient, please notify the sender immediately and do not disclose the=

> contents to any other person, use it for any purpose, or store or copy
> the information in any medium. Thank you.
>
> ARM Limited, Registered office 110 Fulbourn Road, Cambridge CB1 9NJ,
> Registered in England & Wales, Company No: 2557590
> ARM Holdings plc, Registered office 110 Fulbourn Road, Cambridge CB1
> 9NJ, Registered in England & Wales, Company No: 2548782
>
> -----------------------------------------------------------------------=
-
>
>
>
>
>
> _______________________________________________
> dtls-iot mailing list
> dtls-iot@ietf.org
> https://www.ietf.org/mailman/listinfo/dtls-iot
>


--7jKekxP1rEfOhut7vCE0XTeGUtIb804sJ
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

iQEcBAEBCgAGBQJU+GYhAAoJEGhJURNOOiAtSZEIAIKKwsEo87LAKRC/S8iJjAZT
5ROeDFTPOzUpX4n9inb12bwtClMtjRHMddJ6Ddn4d2/U3SQSAmhOUYNc8pClxVsa
Nge32+0MdTKeWKWlnTjYtiarPNyfUO1HoHh79Pn0DmNyR618sFSCMcW9tdKsdqkY
R8zipImeB9OMtQfneRi9G/1UVSQFj8SF1OdF16WdWwqnerrxxh4LPr5/qtIbtriI
1lmpVh4BRPSw7w2lId/IhP8k7dZjXaoUDxMaQMgZhg88v+9ZQKWB/3tqHkfoAAiG
RRpkEoVJLIDnYAIRG855e5g1GefsPBKpngEOKeAV56at9puLnY9DuElAMtM93ZY=
=UuCe
-----END PGP SIGNATURE-----

--7jKekxP1rEfOhut7vCE0XTeGUtIb804sJ--


From nobody Thu Mar  5 07:21:20 2015
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 B7E1F1A1A79 for <dtls-iot@ietfa.amsl.com>; Thu,  5 Mar 2015 07:21:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 VE5M3_5D-ZS7 for <dtls-iot@ietfa.amsl.com>; Thu,  5 Mar 2015 07:21:13 -0800 (PST)
Received: from mout.gmx.net (mout.gmx.net [212.227.15.15]) (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 04D481A00F1 for <dtls-iot@ietf.org>; Thu,  5 Mar 2015 07:18:38 -0800 (PST)
Received: from [192.168.131.142] ([80.92.121.102]) by mail.gmx.com (mrgmx001) with ESMTPSA (Nemesis) id 0M39zL-1Xejm83ccJ-00szFM; Thu, 05 Mar 2015 16:18:36 +0100
Message-ID: <54F873CA.3040301@gmx.net>
Date: Thu, 05 Mar 2015 16:18:34 +0100
From: Hannes Tschofenig <hannes.tschofenig@gmx.net>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: Olaf Bergmann <bergmann@tzi.org>, Zach Shelby <Zach.Shelby@arm.com>
References: <258751E5-69DB-4787-A7EE-B6C955225AA4@arm.com> <87y4oamwtj.fsf@tzi.org>
In-Reply-To: <87y4oamwtj.fsf@tzi.org>
OpenPGP: id=4D776BC9
Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="Da7bCF6vTokbhUolqpodukWammwmFshLj"
X-Provags-ID: V03:K0:vUmyRo7gqBSkKv3G344t8hwxMI9QkVDzsWJ6hHfITEROfHjOLY7 TpSqq76eC2dDg4yDJ1njIVjq5xPGnN2M/U/xTOtNL14PhR3UF30TfwzGDkjoHqBeePOdrst As8rIvbdBt9zAw01aZc7umUejI4jIcJrI59f5IvbLdgKKOEnRjyj83lzEGYZH8aWwxL490m 07jxHOkbmAgNX7wopoPlA==
X-UI-Out-Filterresults: notjunk:1;
Archived-At: <http://mailarchive.ietf.org/arch/msg/dtls-iot/KLaiyLh3s1xpfQ0J8X3IACjnNh0>
Cc: "dtls-iot@ietf.org" <dtls-iot@ietf.org>
Subject: Re: [Dtls-iot] 2nd WGLC on draft-ietf-dice-profile, ending Feb 6th
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: Thu, 05 Mar 2015 15:21:15 -0000

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

Hi Olaf,

thanks for the review.



On 02/07/2015 12:42 AM, Olaf Bergmann wrote:
> Zach Shelby <Zach.Shelby@arm.com> writes:
>=20
>> This mail kicks off a 2nd WGLC for our DTLS profile draft:
>>
>> https://tools.ietf.org/html/draft-ietf-dice-profile-09=20
>=20
> Zach, Hannes, Thomas,
>=20
> sorry for being very late with my review. This I-D is a very good read
> with substantial information (not repeating here the usual caveat that
> you will most likely have the four-party scenario with multiple AA
> servers instead of only three; for this profile document, I am ok with
> the simplistic view of Section 4.1).

;-)


>=20
> Some minor remarks:
>=20
> Section 5 talks about the length of the authentication tag and refers t=
o
> "_8" as possibly being used in constrained networks.  Maybe it would be=

> good to mention that shortening the tag has impact on the collision
> probability?

I included a reference to the CCM specification, which discusses these
aspects.


>=20
> In the last paragraph of Section 5, you could add that SHA-256 is the
> recommended default PRF.
>=20
Done.

> In Section 6.1, I am also not sure that 'servers SHOULD NOT send the
> "PSK identity hint" in the ServerKeyExchange message and client MUST
> ignore the message.' I do not see why this recommendation is needed.
> (The client may ignore it anyway, and the server cannot assume that a
> client reacts on the identity hint the server sends.)

Do you see use of the "PSK identity hint" or do you suggest to change
the sentence to: "Clients MUST ignore the message.'?


>=20
> "Implementations in compliance with this profile MAY use PSK identities=

> up to 128 octets in length, and arbitrary PSKs up to 64 octets in
> length." -- This is a contradiction to RFC 4279 which states that
> implementations MUST support these lengths but MAY support longer
> psk_identities and keys. Although it does not always make sense and is
> not recommended to use psk_identities longer than 128 octets and keys
> that are longer than 64 octets _in the IoT environment_, we must not
> restrict implementations in this regard.

I believe we are OK not following that recommendation since it was given
in a different context, namely with regards to the ability for the
browser to accept certain type of identities from the user. In our case,
we are defining a profile for a different deployment environment.


>=20
> The second paragraph in Section 9 starts with "Constrained clients MUST=

> implement session resumption to improve the performance of the
> handshake."  This is correct, and there is no problem with it but it
> made me stumble when reading it for the first time. Maybe you could add=

> a note that a client that is not capable of storing the state (e.g.,
> during reboot) can always decide to send an empty session_id.


Added text.


>=20
> I am not sure I understand what the following paragraph from Section 14=

> actually recommends:
>=20
>    "[...] for the ServerHello.Random structure it is RECOMMENDED to
>    maintain the existing structure with gmt_unix_time followed by a
>    random sequence of 28 random bytes since the client can use the
>    received time information to securely obtain time information.  For
>    constrained servers it cannot be assumed that they maintain accurate=

>    time information; these devices MUST include time information in the=

>    Server.Random structure when they actually obtain accurate time
>    information that can be utilized by clients.  Clients MUST only use
>    time information obtained from servers they trust."
>=20
> Now, how can the client tell whether or not the first 4 bytes of
> ServerHello.Random contains accurate time information? Is this knowledg=
e
> obtained out-of-band as the last sentence ("trust") might indicate?

I added a note that this has to be agreed out-of-band between the client
and the server. This is not ideal but on the other hand the client must
not trust a random server to provide time information.


>=20
> The last sentence of Section 15 about truncated MAC says "RFC 6066 MUST=

> not be implemented", whereas the last sentence of the following Section=

> 16 on SNI starts with "This specification RECOMMENDs the implementation=

> of RFC 6066". This could be misleading and should probably qualified by=

> specifying which part of RFC 6066 is referred to.

Fixed.

>=20
> A few editorial nits (besides Mathias's):
>=20
>  * in Section 4.2, 2nd para: s/endpointas/endpoints/
Fixed.

>  * The doubled reference to RFC 7390 in the 2nd paragraph
>    of "Discovery and Reachability" ("RFC 7390 [RFC7390] describes")
>    is a bit weird. (Same for RFC 6655 in the 2nd paragraph in
>    Section 5, RFC 6090 in Section 6.2, RFC 6125, 6066 in Section 6.3)

Fixed.



>  * In Section 6.2, the subtitle of Figure 8 denotes that the Cookie
>    Exchange is shown, which is not.
Fixed.

>=20
>  * References
>    [ACE-WG] is dated "Jan 2015". Do you mean 2014?

I used the date when I retrieved the page rather than when it was formed.=


>    s/Tripple-HS/Triple-HS/  (Referenced in Section 18)

Fixed.

Ciao
Hannes

>=20
>=20
> Gr=C3=BC=C3=9Fe
> Olaf
>=20
> _______________________________________________
> dtls-iot mailing list
> dtls-iot@ietf.org
> https://www.ietf.org/mailman/listinfo/dtls-iot
>=20


--Da7bCF6vTokbhUolqpodukWammwmFshLj
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

iQEcBAEBCgAGBQJU+HPKAAoJEGhJURNOOiAtWmkH/1V4a7IPwK1nuane0g22CZL9
0KK896albqB6BxuiDWD7HXGSc3yCWrr46jHX8/l8rhagKMYlcDufDIK9xB6Hr7Gc
6m3M1/C1PlG3j23o6JbNTc9+2NM1dDqDXqNO9vRyZhDNwv0CXRb1j69475CF0F3v
bz5irxklLENGf4TPJ0D6bbNAbABbWjGVP911BtQI7voT3YonE8nDqPY/kTFPIJ2Z
JDvem9aLbqHiP5EbGHc8w3tWoDzOZL3nJbf/mQFxpA/EIRqVJ6iYE+bN71CcRq27
RLOA9Fg2xhMjKMZQ+3MlFkROC3lRRIEAVHEtomwQyBXP9PXidFmgGFSVU1f2igU=
=RMvV
-----END PGP SIGNATURE-----

--Da7bCF6vTokbhUolqpodukWammwmFshLj--


From nobody Thu Mar  5 07:21:38 2015
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 DAE111A00FE for <dtls-iot@ietfa.amsl.com>; Thu,  5 Mar 2015 07:21:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 CnJ9S_u5VL3j for <dtls-iot@ietfa.amsl.com>; Thu,  5 Mar 2015 07:21:24 -0800 (PST)
Received: from mout.gmx.net (mout.gmx.net [212.227.15.15]) (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 580491A0277 for <dtls-iot@ietf.org>; Thu,  5 Mar 2015 07:18:52 -0800 (PST)
Received: from [192.168.131.142] ([80.92.121.102]) by mail.gmx.com (mrgmx001) with ESMTPSA (Nemesis) id 0MIMUZ-1YTH5n0f5r-004Bsg; Thu, 05 Mar 2015 16:18:36 +0100
Message-ID: <54F873CA.4090902@gmx.net>
Date: Thu, 05 Mar 2015 16:18:34 +0100
From: Hannes Tschofenig <hannes.tschofenig@gmx.net>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: Olaf Bergmann <bergmann@tzi.org>, Zach Shelby <Zach.Shelby@arm.com>
References: <258751E5-69DB-4787-A7EE-B6C955225AA4@arm.com> <87y4oamwtj.fsf@tzi.org>
In-Reply-To: <87y4oamwtj.fsf@tzi.org>
OpenPGP: id=4D776BC9
Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="TDtR4GUNfU5ScDjtlfB7QOhKcdFTpIMe4"
X-Provags-ID: V03:K0:XeeGoNRMSFC9PgVaU6OhEAbQHBj/OtQOYVohst5uuW/L4gq7JsF IdoFW9jCqL4bYlMo0N2D3mX9HjZQSXIyaMW8pQEaxw1S2gDSkKats9vqiiRAEe4+yV5Z8f/ FBMXYfBFsE1AO2i6Zgasp+msf2eB+5QTGtnew0F7xAB4i8490ZdvXnTNWDiM4KA/2XY2LHF JORioZzd8CIvTyJpnvrog==
X-UI-Out-Filterresults: notjunk:1;
Archived-At: <http://mailarchive.ietf.org/arch/msg/dtls-iot/u-snStZk72VsL5VU4RqH4fup9-4>
Cc: "dtls-iot@ietf.org" <dtls-iot@ietf.org>
Subject: Re: [Dtls-iot] 2nd WGLC on draft-ietf-dice-profile, ending Feb 6th
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: Thu, 05 Mar 2015 15:21:27 -0000

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

Hi Olaf,

thanks for the review.



On 02/07/2015 12:42 AM, Olaf Bergmann wrote:
> Zach Shelby <Zach.Shelby@arm.com> writes:
>=20
>> This mail kicks off a 2nd WGLC for our DTLS profile draft:
>>
>> https://tools.ietf.org/html/draft-ietf-dice-profile-09=20
>=20
> Zach, Hannes, Thomas,
>=20
> sorry for being very late with my review. This I-D is a very good read
> with substantial information (not repeating here the usual caveat that
> you will most likely have the four-party scenario with multiple AA
> servers instead of only three; for this profile document, I am ok with
> the simplistic view of Section 4.1).

;-)


>=20
> Some minor remarks:
>=20
> Section 5 talks about the length of the authentication tag and refers t=
o
> "_8" as possibly being used in constrained networks.  Maybe it would be=

> good to mention that shortening the tag has impact on the collision
> probability?

I included a reference to the CCM specification, which discusses these
aspects.


>=20
> In the last paragraph of Section 5, you could add that SHA-256 is the
> recommended default PRF.
>=20
Done.

> In Section 6.1, I am also not sure that 'servers SHOULD NOT send the
> "PSK identity hint" in the ServerKeyExchange message and client MUST
> ignore the message.' I do not see why this recommendation is needed.
> (The client may ignore it anyway, and the server cannot assume that a
> client reacts on the identity hint the server sends.)

Do you see use of the "PSK identity hint" or do you suggest to change
the sentence to: "Clients MUST ignore the message.'?


>=20
> "Implementations in compliance with this profile MAY use PSK identities=

> up to 128 octets in length, and arbitrary PSKs up to 64 octets in
> length." -- This is a contradiction to RFC 4279 which states that
> implementations MUST support these lengths but MAY support longer
> psk_identities and keys. Although it does not always make sense and is
> not recommended to use psk_identities longer than 128 octets and keys
> that are longer than 64 octets _in the IoT environment_, we must not
> restrict implementations in this regard.

I believe we are OK not following that recommendation since it was given
in a different context, namely with regards to the ability for the
browser to accept certain type of identities from the user. In our case,
we are defining a profile for a different deployment environment.


>=20
> The second paragraph in Section 9 starts with "Constrained clients MUST=

> implement session resumption to improve the performance of the
> handshake."  This is correct, and there is no problem with it but it
> made me stumble when reading it for the first time. Maybe you could add=

> a note that a client that is not capable of storing the state (e.g.,
> during reboot) can always decide to send an empty session_id.


Added text.


>=20
> I am not sure I understand what the following paragraph from Section 14=

> actually recommends:
>=20
>    "[...] for the ServerHello.Random structure it is RECOMMENDED to
>    maintain the existing structure with gmt_unix_time followed by a
>    random sequence of 28 random bytes since the client can use the
>    received time information to securely obtain time information.  For
>    constrained servers it cannot be assumed that they maintain accurate=

>    time information; these devices MUST include time information in the=

>    Server.Random structure when they actually obtain accurate time
>    information that can be utilized by clients.  Clients MUST only use
>    time information obtained from servers they trust."
>=20
> Now, how can the client tell whether or not the first 4 bytes of
> ServerHello.Random contains accurate time information? Is this knowledg=
e
> obtained out-of-band as the last sentence ("trust") might indicate?

I added a note that this has to be agreed out-of-band between the client
and the server. This is not ideal but on the other hand the client must
not trust a random server to provide time information.


>=20
> The last sentence of Section 15 about truncated MAC says "RFC 6066 MUST=

> not be implemented", whereas the last sentence of the following Section=

> 16 on SNI starts with "This specification RECOMMENDs the implementation=

> of RFC 6066". This could be misleading and should probably qualified by=

> specifying which part of RFC 6066 is referred to.

Fixed.

>=20
> A few editorial nits (besides Mathias's):
>=20
>  * in Section 4.2, 2nd para: s/endpointas/endpoints/
Fixed.

>  * The doubled reference to RFC 7390 in the 2nd paragraph
>    of "Discovery and Reachability" ("RFC 7390 [RFC7390] describes")
>    is a bit weird. (Same for RFC 6655 in the 2nd paragraph in
>    Section 5, RFC 6090 in Section 6.2, RFC 6125, 6066 in Section 6.3)

Fixed.



>  * In Section 6.2, the subtitle of Figure 8 denotes that the Cookie
>    Exchange is shown, which is not.
Fixed.

>=20
>  * References
>    [ACE-WG] is dated "Jan 2015". Do you mean 2014?

I used the date when I retrieved the page rather than when it was formed.=


>    s/Tripple-HS/Triple-HS/  (Referenced in Section 18)

Fixed.

Ciao
Hannes

>=20
>=20
> Gr=C3=BC=C3=9Fe
> Olaf
>=20
> _______________________________________________
> dtls-iot mailing list
> dtls-iot@ietf.org
> https://www.ietf.org/mailman/listinfo/dtls-iot
>=20


--TDtR4GUNfU5ScDjtlfB7QOhKcdFTpIMe4
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

iQEcBAEBCgAGBQJU+HPKAAoJEGhJURNOOiAtWmkH/1V4a7IPwK1nuane0g22CZL9
0KK896albqB6BxuiDWD7HXGSc3yCWrr46jHX8/l8rhagKMYlcDufDIK9xB6Hr7Gc
6m3M1/C1PlG3j23o6JbNTc9+2NM1dDqDXqNO9vRyZhDNwv0CXRb1j69475CF0F3v
bz5irxklLENGf4TPJ0D6bbNAbABbWjGVP911BtQI7voT3YonE8nDqPY/kTFPIJ2Z
JDvem9aLbqHiP5EbGHc8w3tWoDzOZL3nJbf/mQFxpA/EIRqVJ6iYE+bN71CcRq27
RLOA9Fg2xhMjKMZQ+3MlFkROC3lRRIEAVHEtomwQyBXP9PXidFmgGFSVU1f2igU=
=RMvV
-----END PGP SIGNATURE-----

--TDtR4GUNfU5ScDjtlfB7QOhKcdFTpIMe4--


From nobody Thu Mar  5 09:19:58 2015
Return-Path: <bergmann@tzi.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 8848D1A1EEC for <dtls-iot@ietfa.amsl.com>; Thu,  5 Mar 2015 09:19:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.55
X-Spam-Level: 
X-Spam-Status: No, score=-1.55 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jf98KjITNqcB for <dtls-iot@ietfa.amsl.com>; Thu,  5 Mar 2015 09:19:55 -0800 (PST)
Received: from mailhost.informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1B52D1A1BF8 for <dtls-iot@ietf.org>; Thu,  5 Mar 2015 09:14:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from submithost.informatik.uni-bremen.de (submithost.informatik.uni-bremen.de [134.102.201.11]) by mailhost.informatik.uni-bremen.de (8.14.5/8.14.5) with ESMTP id t25HEJr3027473; Thu, 5 Mar 2015 18:14:19 +0100 (CET)
Received: from aung.tzi.org (unknown [IPv6:2001:638:708:30da:3564:655b:7d8:ff09]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by submithost.informatik.uni-bremen.de (Postfix) with ESMTPSA id 3kydwV6cHJz2kb6; Thu,  5 Mar 2015 18:14:18 +0100 (CET)
From: Olaf Bergmann <bergmann@tzi.org>
To: Hannes Tschofenig <hannes.tschofenig@gmx.net>
References: <258751E5-69DB-4787-A7EE-B6C955225AA4@arm.com> <87y4oamwtj.fsf@tzi.org> <54F873CA.4090902@gmx.net>
Date: Thu, 05 Mar 2015 18:14:18 +0100
In-Reply-To: <54F873CA.4090902@gmx.net> (Hannes Tschofenig's message of "Thu,  05 Mar 2015 16:18:34 +0100")
Message-ID: <877fuvgydx.fsf@tzi.org>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.4 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/dtls-iot/pPBrrJ5IqbzDApzj7tKGpWjrp_w>
Cc: "dtls-iot@ietf.org" <dtls-iot@ietf.org>
Subject: Re: [Dtls-iot] 2nd WGLC on draft-ietf-dice-profile, ending Feb 6th
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: Thu, 05 Mar 2015 17:19:56 -0000

Hi Hannes,

Hannes Tschofenig <hannes.tschofenig@gmx.net> writes:

> Do you see use of the "PSK identity hint" or do you suggest to change
> the sentence to: "Clients MUST ignore the message.'?

I envision that the identity hint is used exactly the same in the IoT as
in the rest of the world. I see no reason why this should be different
in constrained environments.

Gr=C3=BC=C3=9Fe
Olaf


From nobody Thu Mar  5 10:37:53 2015
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 144B41A6FEE for <dtls-iot@ietfa.amsl.com>; Thu,  5 Mar 2015 10:37:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 MpPN9wSMvzZl for <dtls-iot@ietfa.amsl.com>; Thu,  5 Mar 2015 10:37:44 -0800 (PST)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.21]) (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 8B2C41A1A59 for <dtls-iot@ietf.org>; Thu,  5 Mar 2015 10:37:44 -0800 (PST)
Received: from [192.168.131.142] ([80.92.121.102]) by mail.gmx.com (mrgmx101) with ESMTPSA (Nemesis) id 0LlYrb-1XwBRR1Bl1-00bJ7D; Thu, 05 Mar 2015 19:37:42 +0100
Message-ID: <54F8A275.2040602@gmx.net>
Date: Thu, 05 Mar 2015 19:37:41 +0100
From: Hannes Tschofenig <hannes.tschofenig@gmx.net>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: Olaf Bergmann <bergmann@tzi.org>
References: <258751E5-69DB-4787-A7EE-B6C955225AA4@arm.com>	<87y4oamwtj.fsf@tzi.org> <54F873CA.4090902@gmx.net> <877fuvgydx.fsf@tzi.org>
In-Reply-To: <877fuvgydx.fsf@tzi.org>
OpenPGP: id=4D776BC9
Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="5j07a0pwbwRL9cOUmduAcFWNu7Qkote7c"
X-Provags-ID: V03:K0:mQDPN/H3uMAZBKT6Nk6Genuhx/bwY3WLBr9O5ogFek7TsxwZubE S5AX4Y3pO3qClBakxrZAXJeyKrCB1b60gHKXleC6joMB2cWH1bxoza7GcY/YT+HQOvaMSzI YwDoV9uFyk3zUozCyDOVGsHdO8ILcmo69h0CK/RcdJjcvc5PchyaVRriYLyf+d1cHARNNyH jb4jjnPt6KaCmQuZA4ZIA==
X-UI-Out-Filterresults: notjunk:1;
Archived-At: <http://mailarchive.ietf.org/arch/msg/dtls-iot/K-Cxp8mIpNoGCwtcG4XSugbf4kM>
Cc: "dtls-iot@ietf.org" <dtls-iot@ietf.org>
Subject: Re: [Dtls-iot] 2nd WGLC on draft-ietf-dice-profile, ending Feb 6th
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: Thu, 05 Mar 2015 18:37:47 -0000

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

Hi Olaf,

the original reason why Pasi and I added the "PSK identity hint" to the
TLS-PSK specification was the desire to interwork with the 3GPP Generic
Bootstrapping Architecture. The GBA was the key management protocol used
to distribute the PSK to the server-side.

I don't think anyone is planning to use this stuff anymore today.

Ciao
Hannes

On 03/05/2015 06:14 PM, Olaf Bergmann wrote:
> Hi Hannes,
>=20
> Hannes Tschofenig <hannes.tschofenig@gmx.net> writes:
>=20
>> Do you see use of the "PSK identity hint" or do you suggest to change
>> the sentence to: "Clients MUST ignore the message.'?
>=20
> I envision that the identity hint is used exactly the same in the IoT a=
s
> in the rest of the world. I see no reason why this should be different
> in constrained environments.
>=20
> Gr=C3=BC=C3=9Fe
> Olaf
>=20


--5j07a0pwbwRL9cOUmduAcFWNu7Qkote7c
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

iQEcBAEBCgAGBQJU+KJ1AAoJEGhJURNOOiAthWEH/R133xUbN6ij3UxcobWHsxOw
7a2pwXvLG44FofZKt5BM2W9vvdBJFoufQv4QZjqQyvGrT75H9AnthV2rbd6MMTzq
on38zXtaScVSoLDyuc86/0Zvv0fRjFTYImWigYjH3IJVaQyxog6gaXydSWeU7WLi
PTUZVpprTnNd7ahzsFFbHe3XXLQvfiGUhl7ejscN0+RddrJdGN0ux+l4R7pMHkl5
VuwFzV19Zvjke0qthCN/xWiIB+2fLnjWdjzh0GDW1/Ud7wIIlV6XZaD2LD5kaWlE
99jtMZhKQKTtMaCyzyh4kSOKM7A/biqeDN+8fwVAYTBIh8Nv2veYw/i0996wlOA=
=YKoV
-----END PGP SIGNATURE-----

--5j07a0pwbwRL9cOUmduAcFWNu7Qkote7c--


From nobody Thu Mar  5 11:55:10 2015
Return-Path: <bergmann@tzi.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 CE5DF1A88F5 for <dtls-iot@ietfa.amsl.com>; Thu,  5 Mar 2015 11:55:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.55
X-Spam-Level: 
X-Spam-Status: No, score=-1.55 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7wcHz4maZRJx for <dtls-iot@ietfa.amsl.com>; Thu,  5 Mar 2015 11:55:07 -0800 (PST)
Received: from mailhost.informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D69361A88F7 for <dtls-iot@ietf.org>; Thu,  5 Mar 2015 11:55:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from submithost.informatik.uni-bremen.de (submithost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::b]) by mailhost.informatik.uni-bremen.de (8.14.5/8.14.5) with ESMTP id t25Jt3lQ000030; Thu, 5 Mar 2015 20:55:03 +0100 (CET)
Received: from aung.tzi.org (p57A63DDF.dip0.t-ipconnect.de [87.166.61.223]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by submithost.informatik.uni-bremen.de (Postfix) with ESMTPSA id 3kyjTz3Myqz2kfD; Thu,  5 Mar 2015 20:55:03 +0100 (CET)
From: Olaf Bergmann <bergmann@tzi.org>
To: Hannes Tschofenig <hannes.tschofenig@gmx.net>
References: <258751E5-69DB-4787-A7EE-B6C955225AA4@arm.com> <87y4oamwtj.fsf@tzi.org> <54F873CA.4090902@gmx.net> <877fuvgydx.fsf@tzi.org> <54F8A275.2040602@gmx.net>
Date: Thu, 05 Mar 2015 20:55:02 +0100
In-Reply-To: <54F8A275.2040602@gmx.net> (Hannes Tschofenig's message of "Thu,  05 Mar 2015 19:37:41 +0100")
Message-ID: <87twxzfcdl.fsf@tzi.org>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.4 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/dtls-iot/qf86-ipxOkxVfO1oonqy_ou_42g>
Cc: "dtls-iot@ietf.org" <dtls-iot@ietf.org>
Subject: Re: [Dtls-iot] 2nd WGLC on draft-ietf-dice-profile, ending Feb 6th
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: Thu, 05 Mar 2015 19:55:08 -0000

Hannes Tschofenig <hannes.tschofenig@gmx.net> writes:

> Hi Olaf,
>
> the original reason why Pasi and I added the "PSK identity hint" to the
> TLS-PSK specification was the desire to interwork with the 3GPP Generic
> Bootstrapping Architecture. The GBA was the key management protocol used
> to distribute the PSK to the server-side.

Oh, I see. Until now, my reading was that this is used as a sort of
realm indicator. If your assessment is correct that nobody uses it,
I would be in favor of the "client MUST ignore" version.

Gr=C3=BC=C3=9Fe
Olaf


From nobody Thu Mar  5 12:04:35 2015
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 C11861A8951 for <dtls-iot@ietfa.amsl.com>; Thu,  5 Mar 2015 12:04:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 x11TFMG2ivmB for <dtls-iot@ietfa.amsl.com>; Thu,  5 Mar 2015 12:04:33 -0800 (PST)
Received: from mout.gmx.net (mout.gmx.net [212.227.15.15]) (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 1FB7A1A8963 for <dtls-iot@ietf.org>; Thu,  5 Mar 2015 12:04:10 -0800 (PST)
Received: from [192.168.131.142] ([80.92.121.102]) by mail.gmx.com (mrgmx003) with ESMTPSA (Nemesis) id 0MSutp-1Y4cUX1pyP-00Rtxl; Thu, 05 Mar 2015 21:04:08 +0100
Message-ID: <54F8B6B6.50103@gmx.net>
Date: Thu, 05 Mar 2015 21:04:06 +0100
From: Hannes Tschofenig <hannes.tschofenig@gmx.net>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: Olaf Bergmann <bergmann@tzi.org>
References: <258751E5-69DB-4787-A7EE-B6C955225AA4@arm.com>	<87y4oamwtj.fsf@tzi.org> <54F873CA.4090902@gmx.net>	<877fuvgydx.fsf@tzi.org> <54F8A275.2040602@gmx.net> <87twxzfcdl.fsf@tzi.org>
In-Reply-To: <87twxzfcdl.fsf@tzi.org>
OpenPGP: id=4D776BC9
Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="AtctL8NPp85HB92FeC7gEqlFpqd35DQTQ"
X-Provags-ID: V03:K0:tz2o9RmSzTYzyDjFy7qZqo6+hLIS4UycHYFjBE1rQlyc/esLQKw NKtWawN4jPw2+Hp+eaGQ9DE98DgRb3pjMdy71Qd264p07EgF9Ihz/cnt1PxInaCXahCdVsG lwVwi3bAyMY11rsn34EdYqnnutIx0BT64dA4xryM7grnus7IY97SDJMt4/tIKxj4ygehpdc OZOYpmJxXwpvGiAb26JpA==
X-UI-Out-Filterresults: notjunk:1;
Archived-At: <http://mailarchive.ietf.org/arch/msg/dtls-iot/fDfJZn1e2ADqNyOc1NjW8BQ24TI>
Cc: "dtls-iot@ietf.org" <dtls-iot@ietf.org>
Subject: Re: [Dtls-iot] 2nd WGLC on draft-ietf-dice-profile, ending Feb 6th
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: Thu, 05 Mar 2015 20:04:34 -0000

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

You could use it as a realm-indicator as well but in the meanwhile the
SNI stuff had been defined that allows the client to indicate what
server it wants to choose (in a hosting solution). While this is not
exactly the same I am not sure anyone has used the PSK identity hint in
a realm-selection scenario.

It would be good to know whether anyone has seen a need for it in the
IoT context. If so, we could change the text and add some motivation for
where to use it.

Ciao
Hannes


On 03/05/2015 08:55 PM, Olaf Bergmann wrote:
> Hannes Tschofenig <hannes.tschofenig@gmx.net> writes:
>=20
>> Hi Olaf,
>>
>> the original reason why Pasi and I added the "PSK identity hint" to th=
e
>> TLS-PSK specification was the desire to interwork with the 3GPP Generi=
c
>> Bootstrapping Architecture. The GBA was the key management protocol us=
ed
>> to distribute the PSK to the server-side.
>=20
> Oh, I see. Until now, my reading was that this is used as a sort of
> realm indicator. If your assessment is correct that nobody uses it,
> I would be in favor of the "client MUST ignore" version.
>=20
> Gr=C3=BC=C3=9Fe
> Olaf
>=20


--AtctL8NPp85HB92FeC7gEqlFpqd35DQTQ
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

iQEcBAEBCgAGBQJU+La3AAoJEGhJURNOOiAtMeYIAKGdaNuGN/ZynWgY6NNYMlta
z7gTBMRttbNksd7Q/QTGWyfIQyARUAaDzWnw2hoFJqlJwit44YZyjFBAfgV+BzDg
WcaVbYUHtq+vSjZO6MTrWGiwBNz7YF4uwyyIh7DnMsCRiLaFjZTtKZHkhJPi5ei2
rlG8i8ljqnpZ6TXOTXK219ub1ffokTKnrhD1VxYkmXUAXW98J6nJgR1m/2nhaQV9
eBDfNo41+SEI5RcuSGtmKummAKRom7ZYXBpG+0e4v5k0r3wM+b5zhg2IUajg9I2E
tJBw7YZDVnEMZ05Vw9M8L/CvjXt+uSLvbg7aJ2nnBbpaE8TN1ub90jLaG0O0vaY=
=VD8B
-----END PGP SIGNATURE-----

--AtctL8NPp85HB92FeC7gEqlFpqd35DQTQ--


From nobody Fri Mar  6 03:25:11 2015
Return-Path: <bergmann@tzi.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 03E431ACD72 for <dtls-iot@ietfa.amsl.com>; Fri,  6 Mar 2015 03:25:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.55
X-Spam-Level: 
X-Spam-Status: No, score=-1.55 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rh8l8bo_tMVd for <dtls-iot@ietfa.amsl.com>; Fri,  6 Mar 2015 03:25:08 -0800 (PST)
Received: from mailhost.informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AEBCD1ACD6C for <dtls-iot@ietf.org>; Fri,  6 Mar 2015 03:25:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from submithost.informatik.uni-bremen.de (submithost.informatik.uni-bremen.de [134.102.201.11]) by mailhost.informatik.uni-bremen.de (8.14.5/8.14.5) with ESMTP id t26BP4vt013005; Fri, 6 Mar 2015 12:25:04 +0100 (CET)
Received: from aung.tzi.org (eduroam-pool3-287.wlan.uni-bremen.de [134.102.233.31]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by submithost.informatik.uni-bremen.de (Postfix) with ESMTPSA id 3kz6741q9rz2l3W; Fri,  6 Mar 2015 12:25:04 +0100 (CET)
From: Olaf Bergmann <bergmann@tzi.org>
To: Hannes Tschofenig <hannes.tschofenig@gmx.net>
References: <258751E5-69DB-4787-A7EE-B6C955225AA4@arm.com> <87y4oamwtj.fsf@tzi.org> <54F873CA.4090902@gmx.net> <877fuvgydx.fsf@tzi.org> <54F8A275.2040602@gmx.net> <87twxzfcdl.fsf@tzi.org> <54F8B6B6.50103@gmx.net>
Date: Fri, 06 Mar 2015 12:25:03 +0100
In-Reply-To: <54F8B6B6.50103@gmx.net> (Hannes Tschofenig's message of "Thu, 05 Mar 2015 21:04:06 +0100")
Message-ID: <87wq2ue5bk.fsf@tzi.org>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.4 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/dtls-iot/uAl5AXXJKyD9YREcCf4_Jn2gGNs>
Cc: "dtls-iot@ietf.org" <dtls-iot@ietf.org>
Subject: Re: [Dtls-iot] 2nd WGLC on draft-ietf-dice-profile, ending Feb 6th
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, 06 Mar 2015 11:25:10 -0000

Hi Hannes,

Hannes Tschofenig <hannes.tschofenig@gmx.net> writes:

> You could use it as a realm-indicator as well but in the meanwhile the
> SNI stuff had been defined that allows the client to indicate what
> server it wants to choose (in a hosting solution). While this is not
> exactly the same I am not sure anyone has used the PSK identity hint in
> a realm-selection scenario.
>
> It would be good to know whether anyone has seen a need for it in the
> IoT context. If so, we could change the text and add some motivation for
> where to use it.

FWIW: I have added support for the PSK identity hint to tinydtls a while
ago on explicit request. I'd see this as a weak indicator that it is
used at least by someone.

Gr=C3=BC=C3=9Fe
Olaf


From nobody Fri Mar  6 03:53:15 2015
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 99A381ACDA3 for <dtls-iot@ietfa.amsl.com>; Fri,  6 Mar 2015 03:53:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 hvr_YrAkskAI for <dtls-iot@ietfa.amsl.com>; Fri,  6 Mar 2015 03:53:11 -0800 (PST)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.21]) (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 340471ACDA9 for <dtls-iot@ietf.org>; Fri,  6 Mar 2015 03:53:11 -0800 (PST)
Received: from [192.168.131.143] ([80.92.121.102]) by mail.gmx.com (mrgmx103) with ESMTPSA (Nemesis) id 0M8MyE-1XZ7b91fTm-00vxwh; Fri, 06 Mar 2015 12:53:05 +0100
Message-ID: <54F99520.9080203@gmx.net>
Date: Fri, 06 Mar 2015 12:53:04 +0100
From: Hannes Tschofenig <hannes.tschofenig@gmx.net>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: "dtls-iot@ietf.org" <dtls-iot@ietf.org>, SLemay@zebra.com
References: <F01D8B85CFF58440B2A13965FBA90CA4CE7B9A19C6@GEORGE.Emea.Arm.com>
In-Reply-To: <F01D8B85CFF58440B2A13965FBA90CA4CE7B9A19C6@GEORGE.Emea.Arm.com>
OpenPGP: id=4D776BC9
X-Forwarded-Message-Id: <F01D8B85CFF58440B2A13965FBA90CA4CE7B9A19C6@GEORGE.Emea.Arm.com>
Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="MTS5ire927cE87xR9xA18WmCWC89dMU4T"
X-Provags-ID: V03:K0:s24ZdxAJYJF7LAFAPNnPESLa+gqiLDbhVv7QI4XvZFuUVRQ/mEg A1z9B0+WNJ/hWFycIrcEnwlx+C6O5iPxum4OMd07Ezv7CRkphgVW6La/GfNuSh5qbtO1cwL qE2GptLO04PPnzjbC+f8HUuEtsSAGFMFK2RA4JBh729vtpzHhkIORpTCukGHWnLmfvVJHeZ yoz9mi8r4jvvzd9hc8uTw==
X-UI-Out-Filterresults: notjunk:1;
Archived-At: <http://mailarchive.ietf.org/arch/msg/dtls-iot/5HfS90PUPcVDElNNRmD13lQMHqc>
Subject: [Dtls-iot] Fwd: Review of the DTLS/TLS Profile Draft
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, 06 Mar 2015 11:53:14 -0000

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

Hi Simon,

thanks for your review and for doing an editorial pass of the document
(which got incorporated directly into Github).

Your question about the keep-alive section made me re-read it again and
I noticed that I haven't described the actual problem that is supposed
to be solved.

For that reason I change the section and here is the new version:

-----


12.  Keep-Alive

   Application layer communication may create state at the endpoints and
   this state my expire at some time.  For this reason, applications
   define ways to refresh state, if necessary.  While the application
   layer exchanges are largely outside the scope of the underlying TLS/
   DTLS exchange similar state considerations also play a role at the
   level of TLS/DTLS.  While TLS/DTLS also creates state in form of a
   security context (see the security parameter described in Appendix A6
   in RFC 5246) at the client and the server this state information does
   not expire.  However, network intermediaries may also allocate state
   and require this state to be kept alive.  Failure to keep state alive
   at a stateful packet filtering firewall or at a NAT may result in the
   inability for one node to reach the other since packets will get
   blocked by these middleboxes.  Periodic keep-alive messages exchanged
   between the TLS/DTLS client and server keep state at these
   middleboxes alive.  According to measurements described in
   [HomeGateway] there is some variance in state management practices
   used in residential gateways but the timeouts are heavily impacted by
   the choice of the transport layer protocol: timeouts for UDP are
   typically much shorter than those for TCP.

   RFC 6520 [RFC6520] defines a heartbeat mechanism to test whether the
   other peer is still alive.  As an additional feature, the same
   mechanism can also be used to perform Path Maximum Transmission Unit
   (MTU) Discovery.

   A recommendation about the use of RFC 6520 depends on the type of
   message exchange an IoT device performs and the number of messages
   the application needs to exchange as part of their application
   functionality.  There are three types of exchanges that need to be
   analysed:

   Client-Initiated, One-Shot Messages

      This is a common communication pattern where IoT devices upload
      data to a server on the Internet on an irregular basis.  The
      communication may be triggered by specific events, such as opening
      a door.

      Since the upload happens on an irregular and unpredictable basis
      and due to renumbering and Network Address Translation (NAT) the
      DTLS handshake may need to be re-started (ideally using session
      resumption, if possible).

      In this case there is no use for a keep-alive extension for this
      scenario.

   Client-Initiated, Regular Data Uploads

      This is a variation of the previous case whereby data gets
      uploaded on a regular basis, for example, based on frequent
      temperature readings.  If neither NAT bindings nor IP address
      changes occurred then the record layer will not notice any
      changes.  For the case where the IP address and port number
      changes, it is necessary to re-create the record layer using
      session resumption.

      In this scenario there is no use for a keep-alive extension.  It
      is also very likely that the device will enter a sleep cycle in
      between data transmissions to keep power consumption low.

   Server-Initiated Messages

      In the two previous scenarios the client initiated the protocol
      interaction and maintains it.  Since messages to the client may
      get blocked by middleboxes the initial connection setup is
      triggered by the client and then kept alive by the server.

      For this message exchange pattern the use of DTLS heartbeat
      messages is quite useful but may have to be coordinated with
      application exchanges (for example when the CoAP resource
      directory is used) to avoid redundant keep-alive message
      exchanges.  The MTU discovery mechanism, which is also part of
      [RFC6520], is less likely to be relevant since for many IoT
      deployments the most constrained link is the wireless interface
      between the IoT device and the network itself (rather than some
      links along the end-to-end path).  Only in more complex network
      topologies, such as multi-hop mesh networks, path MTU discovery
      might be appropriate.  It also has to be noted that DTLS itself
      already provides a basic path discovery mechanism (see
      Section 4.1.1.1 of RFC 6347 by using the fragmentation capability
      of the handshake protocol).

   For server-initiated messages the heartbeat extension is RECOMMENDED.


-----

Is this new text an improvement that answers your question?

Ciao
Hannes



-------- Forwarded Message --------

*From:*Lemay, Simon [mailto:SLemay@zebra.com]
*Sent:* 05 February 2015 21:27
*To:* Hannes Tschofenig
*Subject:* Re: Review of the DTLS/TLS Profile Draft



Hey hannes, how are you



I Skyped you a message but then i figure that email would probably be
better for this



I finished reviewing the document, it looks really good,



I had one question, in section 12 - keep-alive, there is talk of keep
alive in different scenarios and re-creating the record layer depending
on the sporadicity of the message transmission.  Is the suggestion to
re-create the layers after each message or is there a tolerance metric
that should be kept (this might be out of scope for this document or
implementation specific)?



I also made  a few markup (mostly syntaxe and reformulation) if you want
i can fork your repo, make the markup there and pull request it to see
if you like the changes (the changes would not affect content or meat of
the work)



Cheers and good work, that was a good read :D .



Simon


--MTS5ire927cE87xR9xA18WmCWC89dMU4T
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

iQEcBAEBCgAGBQJU+ZUgAAoJEGhJURNOOiAtmP0H/07xanNIUKcJzASith4j2FgH
UnSVQmM4xKl5TW86Z4v+aMOaQe8bwKVSQe1lCQLzaXTfeMIMnTqkrg0tb8gc1Q4M
l9Klie28QmaWYCT48yHvhJsy1IjcbXqTOCJTDIcaLfztrUs+0mWjMzin5gtjlo0E
NAgwNxx1u1+KPEmSOULne+OdAGc+Wa/3ugxKGrnPPnPN2jkwCJ/Nmga+R92GdlY7
3fPmyOkxdaL8fasqzHLxfL6jzB01USV8IDbSjyJk05O+/8gqJcwXv2rnarCSHhkc
IqPgU7ITaPqgyAO+rELcCLlVbF9l2RAijzARxXqanNZo8ZdNLgp4L7ckiySVCTc=
=rjWw
-----END PGP SIGNATURE-----

--MTS5ire927cE87xR9xA18WmCWC89dMU4T--


From nobody Fri Mar  6 03:55:35 2015
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 6D4C41ACDA9 for <dtls-iot@ietfa.amsl.com>; Fri,  6 Mar 2015 03:55:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 24vq9knUQO6V for <dtls-iot@ietfa.amsl.com>; Fri,  6 Mar 2015 03:55:32 -0800 (PST)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.22]) (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 B48181ACDA2 for <dtls-iot@ietf.org>; Fri,  6 Mar 2015 03:55:31 -0800 (PST)
Received: from [192.168.131.143] ([80.92.121.102]) by mail.gmx.com (mrgmx102) with ESMTPSA (Nemesis) id 0Luajs-1XUDjl44C8-00zqGQ; Fri, 06 Mar 2015 12:55:22 +0100
Message-ID: <54F995A9.5030602@gmx.net>
Date: Fri, 06 Mar 2015 12:55:21 +0100
From: Hannes Tschofenig <hannes.tschofenig@gmx.net>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: Olaf Bergmann <bergmann@tzi.org>
References: <258751E5-69DB-4787-A7EE-B6C955225AA4@arm.com>	<87y4oamwtj.fsf@tzi.org> <54F873CA.4090902@gmx.net>	<877fuvgydx.fsf@tzi.org> <54F8A275.2040602@gmx.net>	<87twxzfcdl.fsf@tzi.org> <54F8B6B6.50103@gmx.net> <87wq2ue5bk.fsf@tzi.org>
In-Reply-To: <87wq2ue5bk.fsf@tzi.org>
OpenPGP: id=4D776BC9
Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="tTSTIF0rA1chGu13iAJmmQULRhgsAuprs"
X-Provags-ID: V03:K0:QtojzhD5oTy786fQna6aHNcR36h7E1K71Tmf3EDi5N5LC3f2CWo ccfuEtqT7pi/CBxWv21PyUSZfDAlksd4in47IQKTr01d2znB+3rkiRNylAhK8x/2AxBNCps G3XxLYIM/PoV0oxDxOAHX4+XK2Zl5HAVF2JGYmOh7BhbUqoB3FD800aMD8GVkunJWGP5qYQ 4qZHNirQklG+21ls/h9oQ==
X-UI-Out-Filterresults: notjunk:1;
Archived-At: <http://mailarchive.ietf.org/arch/msg/dtls-iot/JvyeNHO2OLfMvre0OMChKJmnAss>
Cc: "dtls-iot@ietf.org" <dtls-iot@ietf.org>
Subject: [Dtls-iot] PSK identity hint .... Re: 2nd WGLC on draft-ietf-dice-profile, ending Feb 6th
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, 06 Mar 2015 11:55:33 -0000

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

Olaf, that's interesting.

Do you remember what the use case of the person asking for the support
of the PSK identity hint was?

Has someone else in the working group encountered the need for the PSK
identity hint?

I am happy to add support back into the spec for it.

Ciao
Hannes

On 03/06/2015 12:25 PM, Olaf Bergmann wrote:
> Hi Hannes,
>=20
> Hannes Tschofenig <hannes.tschofenig@gmx.net> writes:
>=20
>> You could use it as a realm-indicator as well but in the meanwhile the=

>> SNI stuff had been defined that allows the client to indicate what
>> server it wants to choose (in a hosting solution). While this is not
>> exactly the same I am not sure anyone has used the PSK identity hint i=
n
>> a realm-selection scenario.
>>
>> It would be good to know whether anyone has seen a need for it in the
>> IoT context. If so, we could change the text and add some motivation f=
or
>> where to use it.
>=20
> FWIW: I have added support for the PSK identity hint to tinydtls a whil=
e
> ago on explicit request. I'd see this as a weak indicator that it is
> used at least by someone.
>=20
> Gr=C3=BC=C3=9Fe
> Olaf
>=20


--tTSTIF0rA1chGu13iAJmmQULRhgsAuprs
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

iQEcBAEBCgAGBQJU+ZWpAAoJEGhJURNOOiAtFn8H/i6ZVvr7PBORnAQgtqSph1vt
OIumP5eDiJfHPuce9VzA1sQAVT/6yVR0N647QLmmBbsvnjSgN2aVaYNJpjJR4BwM
q4i8S7pxHhhPMrrzxQc6HKGHwEW4Lq9VBMmxqrEZspWFzwnsaQQanZpQnsgXXx+P
uVeae09a3SiyoLYmj8AdM7jAmB/IWzrT/v8Gz9JGw7Wf57aiN0TkTXaW8CNPvEzK
QFcPgrIs1JHJesg50pwC4o5KZY2AeDEY+Sp2KFgX8ej6By8V2zNC6SSe4RNyxIrJ
bQqSuVblDTNfDGhHlBmlV+1oNxWZBWW4vc61qAV6majpV2DxrOii1zjNbn6aHu4=
=x1zD
-----END PGP SIGNATURE-----

--tTSTIF0rA1chGu13iAJmmQULRhgsAuprs--


From nobody Fri Mar  6 06:53:30 2015
Return-Path: <bergmann@tzi.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 6FFC01ACE69 for <dtls-iot@ietfa.amsl.com>; Fri,  6 Mar 2015 06:53:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.55
X-Spam-Level: 
X-Spam-Status: No, score=-1.55 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id N3DPTRxOcSmw for <dtls-iot@ietfa.amsl.com>; Fri,  6 Mar 2015 06:53:27 -0800 (PST)
Received: from mailhost.informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BD5341AD09F for <dtls-iot@ietf.org>; Fri,  6 Mar 2015 06:47:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from submithost.informatik.uni-bremen.de (submithost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::b]) by mailhost.informatik.uni-bremen.de (8.14.5/8.14.5) with ESMTP id t26Elqm3020005; Fri, 6 Mar 2015 15:47:52 +0100 (CET)
Received: from aung.tzi.org (eduroam-pool3-287.wlan.uni-bremen.de [134.102.233.31]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by submithost.informatik.uni-bremen.de (Postfix) with ESMTPSA id 3kzBd42P18z2lH7; Fri,  6 Mar 2015 15:47:52 +0100 (CET)
From: Olaf Bergmann <bergmann@tzi.org>
To: Hannes Tschofenig <hannes.tschofenig@gmx.net>
References: <258751E5-69DB-4787-A7EE-B6C955225AA4@arm.com> <87y4oamwtj.fsf@tzi.org> <54F873CA.4090902@gmx.net> <877fuvgydx.fsf@tzi.org> <54F8A275.2040602@gmx.net> <87twxzfcdl.fsf@tzi.org> <54F8B6B6.50103@gmx.net> <87wq2ue5bk.fsf@tzi.org> <54F995A9.5030602@gmx.net>
Date: Fri, 06 Mar 2015 15:47:51 +0100
In-Reply-To: <54F995A9.5030602@gmx.net> (Hannes Tschofenig's message of "Fri,  06 Mar 2015 12:55:21 +0100")
Message-ID: <87egp2chd4.fsf@tzi.org>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.4 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/dtls-iot/gE4XyBGLjj0Bj-TyBg6B4X_gVkY>
Cc: "dtls-iot@ietf.org" <dtls-iot@ietf.org>
Subject: Re: [Dtls-iot] PSK identity hint .... Re: 2nd WGLC on draft-ietf-dice-profile, ending Feb 6th
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, 06 Mar 2015 14:53:28 -0000

Hannes Tschofenig <hannes.tschofenig@gmx.net> writes:

> Olaf, that's interesting.
>
> Do you remember what the use case of the person asking for the support
> of the PSK identity hint was?

Not really. From my old emails, I cannot tell if there was a real use
case behind that request. Maybe not.

Gr=C3=BC=C3=9Fe
Olaf


From nobody Fri Mar  6 09:45:20 2015
Return-Path: <Rene.Hummen@comsys.rwth-aachen.de>
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 C0B4F1A0151 for <dtls-iot@ietfa.amsl.com>; Fri,  6 Mar 2015 09:45:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.86
X-Spam-Level: 
X-Spam-Status: No, score=-3.86 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-2.3, T_RP_MATCHES_RCVD=-0.01] 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 cbLUT6rcGLi4 for <dtls-iot@ietfa.amsl.com>; Fri,  6 Mar 2015 09:45:14 -0800 (PST)
Received: from mx-out-2.rwth-aachen.de (mx-out-2.rwth-aachen.de [134.130.5.187]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B34EC1A1A00 for <dtls-iot@ietf.org>; Fri,  6 Mar 2015 09:45:12 -0800 (PST)
X-IronPort-AV: E=Sophos;i="5.11,354,1422918000";  d="p7s'?scan'208";a="288527019"
Received: from mail-i4.nets.rwth-aachen.de ([137.226.12.21]) by mx-2.rz.rwth-aachen.de with ESMTP; 06 Mar 2015 18:45:11 +0100
Received: from messenger.nets.rwth-aachen.de (messenger.nets.rwth-aachen.de [137.226.13.40]) by mail-i4.nets.rwth-aachen.de (Postfix) with ESMTP id B124E13DA44; Fri,  6 Mar 2015 18:45:10 +0100 (CET)
Received: from MESSENGER.nets.rwth-aachen.de ([fe80::d4e:bb9d:9e0:bfee]) by MESSENGER.nets.rwth-aachen.de ([fe80::d4e:bb9d:9e0:bfee%12]) with mapi id 14.01.0218.012; Fri, 6 Mar 2015 18:45:10 +0100
From: Rene Hummen <Rene.Hummen@comsys.rwth-aachen.de>
To: Hannes Tschofenig <hannes.tschofenig@gmx.net>
Thread-Topic: Review of draft-ietf-dice-profile-10
Thread-Index: AQHQWDVKr6UOQaogEkakjPnECZZkaA==
Date: Fri, 6 Mar 2015 17:45:09 +0000
Message-ID: <04D4A5C6-540E-4080-A762-EA7097445FE1@comsys.rwth-aachen.de>
Accept-Language: en-US, de-DE
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [137.226.12.36]
Content-Type: multipart/signed; boundary="Apple-Mail=_E506658D-0F02-4522-B11F-F58D89014593"; protocol="application/pkcs7-signature"; micalg=sha1
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/dtls-iot/eTlQuuM9UUiHQU2-V8m5_QJ_W08>
Cc: "dtls-iot@ietf.org" <dtls-iot@ietf.org>
Subject: [Dtls-iot] Review of draft-ietf-dice-profile-10
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, 06 Mar 2015 17:45:19 -0000

--Apple-Mail=_E506658D-0F02-4522-B11F-F58D89014593
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252

Hi Hannes, Thomas, list,

sorry for the late feedback. Since you already revised parts of =
draft-ietf-dice-profile-09, I decided to read draft-ietf-dice-profile-10 =
instead ([1] from GitHub). I am especially glad to see constrained =
servers to be included this time around. These are my remaining =
comments:

1) As a general comment that applies to the whole document: Would it =
make sense to replace the =93is envisioned=94 / =93is not envisioned=94 =
and =93are not applicable=94 with SHOULDs and MUSTs (NOT)?=20

2) Figure 1 should also mention the client=92s private key (or simply =
call it a public/private key-pair).

3) Section 4.2 (starting from line 689)

"In this section we look at cases where constrained devices run TLS/
   DTLS servers to secure access to application layer services running
   on top of CoAP, HTTP or other protocols.  Running server
   functionality on a constrained node is typically more demanding since
   servers have to wait for incoming requests.  Therefore, they will
   have fewer possibilities to enter sleep-cycles.  Nevertheless, there
   are legitimate reasons for deploying servers as constrained devices.=94=


Is there a need to educate the reader about the advantages/disadvantages =
of constrained servers? I suggest to replace the above text with the =
following:

"In this section, we assume a scenario where constrained devices run =
TLS/
   DTLS servers to secure access to application layer services running
   on top of CoAP, HTTP or other protocols.=94

Moreover, first introducing the example and then outlining the challenge =
seems to be the inverted order. Why not outline the challenges first and =
then describe the example as one possible way to solve them?

In the example, why do you assume that reading the temperature sensor =
does not require authentication? The temperature information is the =
basis for the subsequent decision to turn on the fan, which in the =
example requires protection. An adversary could then still control the =
fan via the thermostat by injecting forged temperature information. =
IMHO, all communication in this scenario should be protected to give a =
clear message that network security is important for the entire system. =20=


Minor nits:

"Below we explain how these challenges have been solved
   with CoAP, as an example.=94

should be

"Below we explain how these challenges __can be__ solved
   with CoAP, as an example.=94


"Since RD is
      usually not a proxy clients can discover links registered with the
      RD and then access them directly."

should be

"Since RD is
      usually not a proxy__,__ clients can discover links registered =
with the
      RD and then access them directly.=94



4) Section 5 (line 1025)

"SHA-256 is
   the recommended default PRF.=94

In which document? The DTLS profile or the (D)TLS specification?



5) Section 6 (line 1033)

"Note that
   shared secrets are not passwords.=94

should be

"Note that
   shared secrets are not passwords, but binary blobs of random data.=94



6) Section 6.1 (line 1116)

The paragraph about the PSK identity hint is still unclear. Does this =
paragraph argue for or against using the hint? I guess, the strange =
thing about this paragraph is that it first introduces the hint as =
something that one actually might want to use. Then, however, recommends =
_against_ doing so=85twice:

=93If [=85] the server then servers SHOULD NOT send the "PSK identity
   hint" in the ServerKeyExchange message.  Servers SHOULD NOT send the
   "PSK identity hint" in the ServerKeyExchange message and clients MUST
   ignore the message.=94

Plus, directly afterwards, there is a recommendation on how the SNI =
value can be used to help select the hint.=20


Would it make sense to add a recommendation about a minimum PSK length =
following this text in the current specification?

=93Implementations
   in compliance with this profile MAY use PSK identities up to 128
   octets in length, and arbitrary PSKs up to 64 octets in length.  The
   use of shorter PSK identities and shorter PSKs is RECOMMENDED.=94



7) Section 6.3 (line 1249 and below)

"The use of the Trust Anchor
   Management Protocol (TAMP) [RFC5934] is, however, not envisioned.
   Instead IoT devices using this profile MUST use a software update
   mechanism to populate the trust anchor store.=94

Is it really necessary to be so strict in how the trust anchor store is =
populated? Doesn=92t it suffice to say:

"The Trust Anchor
   Management Protocol (TAMP) [RFC5934], however, SHOULD NOT be used.
   Instead, IoT devices using this profile SHOULD use a software update
   mechanism to populate the trust anchor store.=94


I guess, this is a typo =93dNSName".



8) Section 6.3.2 (line 1482)

"Since the server does not necessarily know what trust
   anchors the client has stored it includes intermediate CA certs in
   the certificate payload as well to facilitate with certification path
   construction and path validation."

should be

"Since the server does not necessarily know what trust
   anchors the client has stored and to facilitate certification path
   construction as well as path validation, it includes intermediate CA =
certs in
   the certificate payload.=94



9) Section 13 (line 1836)

"Choosing appropriate timeout values is difficult with infrequent data
   transmissions, changing network conditions, and large variance in
   latency.=94

The "infrequent data transmissions=94 was confusing as I had the DTLS =
handshake in mind and, at first, didn=92t relate it to the preceding =
note about the round-trip time estimator. This is nit-picking, but would =
it make sense to simply remove "infrequent data transmissions=94 from =
this enumeration?



10) Section 17 (line 1972)

"Ultimately, the main benefit of this extension is it to
   allows client implementations to lower their [=85]=94

Remove the =93it=94.



11) Section 21 (line 2089 and below)

"Ongoing discussions regarding the choice of specific
   ECC curves will also likely to impact implementations.=94

Remove the =93to=94.


"Offer access to building blocks in addition (or as an alternative)
      to the complete functionality.  For example, a chip manufacturer
      who gives developers access to the AES crypto function can use it
      to build an efficient AES-GCM implementations.  Another example is
      to make a special instruction available that increases the speed
      of speed-up carryless multiplications.=94

Why not use ECB as a basic example of a building block?



12) Appendix A (line 2673 and below)

In contrast to the remaining profile, this (obviously) is very link =
layer specific normative text. Why not move this to a short separate =
document?



BR,
Ren=E9


[1] =
https://github.com/hannestschofenig/tschofenig-ids/commit/37d0cfa130904dcb=
a6c2d470f286bdb98b81e41d


--
Dipl.-Inform. Rene Hummen, Ph.D. Student
Chair of Communication and Distributed Systems
RWTH Aachen University, Germany
tel: +49 241 80 21426
web: http://www.comsys.rwth-aachen.de/team/rene-hummen/


--Apple-Mail=_E506658D-0F02-4522-B11F-F58D89014593
Content-Disposition: attachment; filename="smime.p7s"
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIOGzCCBCEw
ggMJoAMCAQICAgDHMA0GCSqGSIb3DQEBBQUAMHExCzAJBgNVBAYTAkRFMRwwGgYDVQQKExNEZXV0
c2NoZSBUZWxla29tIEFHMR8wHQYDVQQLExZULVRlbGVTZWMgVHJ1c3QgQ2VudGVyMSMwIQYDVQQD
ExpEZXV0c2NoZSBUZWxla29tIFJvb3QgQ0EgMjAeFw0wNjEyMTkxMDI5MDBaFw0xOTA2MzAyMzU5
MDBaMFoxCzAJBgNVBAYTAkRFMRMwEQYDVQQKEwpERk4tVmVyZWluMRAwDgYDVQQLEwdERk4tUEtJ
MSQwIgYDVQQDExtERk4tVmVyZWluIFBDQSBHbG9iYWwgLSBHMDEwggEiMA0GCSqGSIb3DQEBAQUA
A4IBDwAwggEKAoIBAQDpm8NnhfkNrvWNVMOWUDU9YuluTO2U1wBblSJ01CDrNI/W7MAxBAuZgeKm
FNJSoCgjhIt0iQReW+DieMF4yxbLKDU5ey2QRdDtoAB6fL9KDhsAw4bpXCsxEXsM84IkQ4wcOItq
aACa7txPeKvSxhObdq3u3ibo7wGvdA/BCaL2a869080UME/15eOkyGKbghoDJzANAmVgTe3RCSMq
ljVYJ9N2xnG2kB3E7f81hn1vM7PbD8URwoqDoZRdQWvY0hD1TP3KUazZve+Sg7va64sWVlZDz+HV
Ez2mHycwzUlU28kTNJpxdcVs6qcLmPkhnSevPqM5OUhqjK3JmfvDEvK9AgMBAAGjgdkwgdYwcAYD
VR0fBGkwZzBloGOgYYZfaHR0cDovL3BraS50ZWxlc2VjLmRlL2NnaS1iaW4vc2VydmljZS9hZl9E
b3dubG9hZEFSTC5jcmw/LWNybF9mb3JtYXQ9WF81MDkmLWlzc3Vlcj1EVF9ST09UX0NBXzIwHQYD
VR0OBBYEFEm3xs/oPR9/6kR7Eyn38QpwPt5kMB8GA1UdIwQYMBaAFDHDeRu69VPXF+CJei0XbAqz
K50zMA4GA1UdDwEB/wQEAwIBBjASBgNVHRMBAf8ECDAGAQH/AgECMA0GCSqGSIb3DQEBBQUAA4IB
AQA74Vp3wEgX3KkY7IGvWonwvSiSpspZGBJw7Cjy565/lizn8l0ZMfYTK3S9vYCyufdnyTmieTvh
ERHua3iRM347XyYndVNljjNj7s9zw7CSI0khUHUjoR8Y4pSFPT8z6XcgjaK95qGFKUD2P3MyWA0J
a6bahWzAP7uNZmRWJE6uDT8yNQFb6YyC2XJZT7GGhfF0hVblw/hc843uR7NTBXDn5U2KaYMo4RMJ
hp5eyOpYHgwf+aTUWgRo/Sg+iwK2WLX2oSw3VwBnqyNojWOl75lrXP1LVvarQIc01BGSbOyHxQoL
BzNytG8MHVQs2FHHzL8w00Ny8TK/jM5JY6gA9/IcMIIE6DCCA9CgAwIBAgIECfJ04DANBgkqhkiG
9w0BAQUFADBaMQswCQYDVQQGEwJERTETMBEGA1UEChMKREZOLVZlcmVpbjEQMA4GA1UECxMHREZO
LVBLSTEkMCIGA1UEAxMbREZOLVZlcmVpbiBQQ0EgR2xvYmFsIC0gRzAxMB4XDTA3MDIxNDExNDkz
OFoXDTE5MDIxMzAwMDAwMFowXjELMAkGA1UEBhMCREUxFDASBgNVBAoTC1JXVEggQWFjaGVuMRcw
FQYDVQQDEw5SV1RIIEFhY2hlbiBDQTEgMB4GCSqGSIb3DQEJARYRY2FAcnd0aC1hYWNoZW4uZGUw
ggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQC4MAhk48jcelLfNUI5kvMv+CF54xJnL4x/
cJQnN2NId6CJ3fqs0siO2exIACfzdjxOUpQ6ZFOn5pdTvTi7stnk8WAaP/d9LFd8k9Gbxjh7xh3L
+0a3ac+/tHJcX564ntUxGtVGMuShEoUaZUT5fw97TL36UJ8OqXLrqpdAKcFKaJ+pgRp2gTLj4MNU
MPjA4GlstpjoLnT++qFm7t/ZS92/E3OqNJUwHH6C35vSroVscmg+a7XxT6U4JO99MYxNcTIMzhPS
9Ytp+302w7i51daBjr0hFGPK0nLSV6gv77zBSFJ7AVGJJxBSUzDn0xkDLYvZwqaeYkj8kDB2oSeR
yfGjAgMBAAGjggGwMIIBrDAPBgNVHRMBAf8EBTADAQH/MAsGA1UdDwQEAwIBBjAdBgNVHQ4EFgQU
btU+wBwvcck8v0lO72pVSOzR8jgwHwYDVR0jBBgwFoAUSbfGz+g9H3/qRHsTKffxCnA+3mQwHAYD
VR0RBBUwE4ERY2FAcnd0aC1hYWNoZW4uZGUwgYgGA1UdHwSBgDB+MD2gO6A5hjdodHRwOi8vY2Rw
MS5wY2EuZGZuLmRlL2dsb2JhbC1yb290LWNhL3B1Yi9jcmwvY2FjcmwuY3JsMD2gO6A5hjdodHRw
Oi8vY2RwMi5wY2EuZGZuLmRlL2dsb2JhbC1yb290LWNhL3B1Yi9jcmwvY2FjcmwuY3JsMIGiBggr
BgEFBQcBAQSBlTCBkjBHBggrBgEFBQcwAoY7aHR0cDovL2NkcDEucGNhLmRmbi5kZS9nbG9iYWwt
cm9vdC1jYS9wdWIvY2FjZXJ0L2NhY2VydC5jcnQwRwYIKwYBBQUHMAKGO2h0dHA6Ly9jZHAyLnBj
YS5kZm4uZGUvZ2xvYmFsLXJvb3QtY2EvcHViL2NhY2VydC9jYWNlcnQuY3J0MA0GCSqGSIb3DQEB
BQUAA4IBAQAXh37GLAscIHrVqQYrG5P/dYULxAseU6xuXKnSpVTnMWVFf1TtN/p2D+8XTKtl/A4W
lYa9np+ONblWcS1nJsuYf7N9wrO4zCEcVBNLIAHCY3ZXG+IoNHwgXqSYqXHzrAQZjkSJr1RfbFE4
njUy0nNhtC51HX0ongWfqODc6z7aF9we20615Mh8Kk8uox4XgjLLV/UjPVlwRAnuYIeF0wycvQ6j
z/PJMuOrXShpqejpaiRXqKx8oPXAlCcnoqRLlQc1L0iwQHBn0Em6tDmMHcahbf9SBOWiZ8+O0av4
ly8CQ95okz9hto9UErXUIzNea2AQXBtlIyLLKgVuYPf4i3IyMIIFBjCCA+6gAwIBAgIHFHkMp6Zz
lDANBgkqhkiG9w0BAQUFADBeMQswCQYDVQQGEwJERTEUMBIGA1UEChMLUldUSCBBYWNoZW4xFzAV
BgNVBAMTDlJXVEggQWFjaGVuIENBMSAwHgYJKoZIhvcNAQkBFhFjYUByd3RoLWFhY2hlbi5kZTAe
Fw0xMjA5MTkwOTIzMzVaFw0xNTA5MTkwOTIzMzVaMDkxCzAJBgNVBAYTAkRFMRQwEgYDVQQKEwtS
V1RIIEFhY2hlbjEUMBIGA1UEAxMLUmVuZSBIdW1tZW4wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAw
ggEKAoIBAQDDoo52P1ghFxnZmWNVnv7+qDKjyif4AoLkJrs7CVV34cRm/PhuW8WzLqOES0B0ENWE
eDUez2Dc4inRNXdF5zMy36rLuKsK5MuznnXTzqYGMeGQAU7MkUvSZdMIWDpMdVc5nKzP81leStBY
c3t6T2PNFHbeQEoHqjUNMQc9wfFWVQHTnQt9+kejn8NDMHqzKjJ+bnXm3byZCEs09CnmGli1irfJ
cR6Fo4KcRMHKVrAHUG8NB+QyPv9RzEawbxwZgyDot5G/A4iRnX0aZ7OjB6ohkepKniBZqSMeOIu1
/Y7p6zYwqiLLywX1VtDQz067R4pkrT5h/IO/VcEGXukXqPA/AgMBAAGjggHsMIIB6DAvBgNVHSAE
KDAmMBEGDysGAQQBga0hgiwBAQQCAzARBg8rBgEEAYGtIYIsAgEEAgMwCQYDVR0TBAIwADALBgNV
HQ8EBAMCBeAwHQYDVR0lBBYwFAYIKwYBBQUHAwIGCCsGAQUFBwMEMB0GA1UdDgQWBBTAJpMHhUGI
9hiu0k6Ccd8MggDivTAfBgNVHSMEGDAWgBRu1T7AHC9xyTy/SU7valVI7NHyODAsBgNVHREEJTAj
gSFyZW5lLmh1bW1lbkBjb21zeXMucnd0aC1hYWNoZW4uZGUweQYDVR0fBHIwcDA2oDSgMoYwaHR0
cDovL2NkcDEucGNhLmRmbi5kZS9yd3RoLWNhL3B1Yi9jcmwvY2FjcmwuY3JsMDagNKAyhjBodHRw
Oi8vY2RwMi5wY2EuZGZuLmRlL3J3dGgtY2EvcHViL2NybC9jYWNybC5jcmwwgZQGCCsGAQUFBwEB
BIGHMIGEMEAGCCsGAQUFBzAChjRodHRwOi8vY2RwMS5wY2EuZGZuLmRlL3J3dGgtY2EvcHViL2Nh
Y2VydC9jYWNlcnQuY3J0MEAGCCsGAQUFBzAChjRodHRwOi8vY2RwMi5wY2EuZGZuLmRlL3J3dGgt
Y2EvcHViL2NhY2VydC9jYWNlcnQuY3J0MA0GCSqGSIb3DQEBBQUAA4IBAQCA/Plhm3Cxu6mOs3O3
Wsl/9Ow7rbANrMvB2zxZW4yGJGu5FKaib+ir66xbpMAbmN4gqQmwuDMW+oWC7U+m9IfFG+T482Rz
AvsYEOZUmq3Y0KFx87MEJdgaWtJ7PnlUaGtgQjdMso0pvAboZnp2pfxazq46lHXDgTCJsd7MUHb6
MzV9JpDzq0qnXeM2d+WxpOckuo11SAtXod+zuI9Udm7oUVIGeI8yFQrtHhtfESOmi57zSTseEYNS
meInQtPv1ARHwuFRBcG5SkHDqbFZIw+2QVK2qq23NlTeBB/JfitX13NYdYNMgymz30iHXvxmB1nN
fmJ9RDejQ4SVonYR7pLLMYIC5zCCAuMCAQEwaTBeMQswCQYDVQQGEwJERTEUMBIGA1UEChMLUldU
SCBBYWNoZW4xFzAVBgNVBAMTDlJXVEggQWFjaGVuIENBMSAwHgYJKoZIhvcNAQkBFhFjYUByd3Ro
LWFhY2hlbi5kZQIHFHkMp6ZzlDAJBgUrDgMCGgUAoIIBUzAYBgkqhkiG9w0BCQMxCwYJKoZIhvcN
AQcBMBwGCSqGSIb3DQEJBTEPFw0xNTAzMDYxNzQ1MDhaMCMGCSqGSIb3DQEJBDEWBBRPwVty82nb
hOk8gbA6v1R/e+nfWDB4BgkrBgEEAYI3EAQxazBpMF4xCzAJBgNVBAYTAkRFMRQwEgYDVQQKEwtS
V1RIIEFhY2hlbjEXMBUGA1UEAxMOUldUSCBBYWNoZW4gQ0ExIDAeBgkqhkiG9w0BCQEWEWNhQHJ3
dGgtYWFjaGVuLmRlAgcUeQynpnOUMHoGCyqGSIb3DQEJEAILMWugaTBeMQswCQYDVQQGEwJERTEU
MBIGA1UEChMLUldUSCBBYWNoZW4xFzAVBgNVBAMTDlJXVEggQWFjaGVuIENBMSAwHgYJKoZIhvcN
AQkBFhFjYUByd3RoLWFhY2hlbi5kZQIHFHkMp6ZzlDANBgkqhkiG9w0BAQEFAASCAQBD6KLb/VMi
ZWG5cJCInxbSeh20J7SGbhk/pYmjvrSH8+4Z+iGrttWlEMoC+pdxfJtUztpxPSVSlSwtg6PX+NUR
vv7RCMRNDnIYqgaBIJLwsu+fvnofdnlIaTxcR2ernXFTMJoQ2tuQee+IACH+hTTAMMPspg0Tu7sz
edfBh7dkpH7JBsJJPkAGaEb+gUax+snYcNCLswXJb2ri7g/IMW+dLYmUse1HLtHEGUSWxPs7Rx1z
rWQxcxgXSz6IVeP8ByFq8THohWoJdyx43vWGp0qGEZW4lqCLXuc4xE/VNGKxhrxDChak3mQQHDt+
sO6hmfVZVqIhMXw360izcJ+132U/AAAAAAAA

--Apple-Mail=_E506658D-0F02-4522-B11F-F58D89014593--


From nobody Fri Mar  6 10:55:37 2015
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 61F5E1A1B6D for <dtls-iot@ietfa.amsl.com>; Fri,  6 Mar 2015 10:55:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 uCcKHm9c10kE for <dtls-iot@ietfa.amsl.com>; Fri,  6 Mar 2015 10:55:32 -0800 (PST)
Received: from mout.gmx.net (mout.gmx.net [212.227.15.15]) (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 AEBBB1A1BE4 for <dtls-iot@ietf.org>; Fri,  6 Mar 2015 10:55:31 -0800 (PST)
Received: from [192.168.131.143] ([80.92.121.102]) by mail.gmx.com (mrgmx001) with ESMTPSA (Nemesis) id 0LdpcB-1Xm4DM0PDP-00iyP5; Fri, 06 Mar 2015 19:55:27 +0100
Message-ID: <54F9F81E.3080205@gmx.net>
Date: Fri, 06 Mar 2015 19:55:26 +0100
From: Hannes Tschofenig <hannes.tschofenig@gmx.net>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: Ludwig Seitz <ludwig@sics.se>, dtls-iot@ietf.org
References: <258751E5-69DB-4787-A7EE-B6C955225AA4@arm.com> <54F42928.4070409@sics.se>
In-Reply-To: <54F42928.4070409@sics.se>
OpenPGP: id=4D776BC9
Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="X7OnKrJQEk626D7Gu5j4bQKlIrRmfPc2l"
X-Provags-ID: V03:K0:W+TYGZwc2pLwNH+ncOU97H4oboij4Ba2wPK8GBat+ehzH7cyIMy cmeKuuIAKtg9Ncyt6s1hfuYXP6GHl/TTqpErCq8owYTjJWFdraXeVxZxDO6I+g1guLezpYb qLTcK7tIo08797wpPqReKgze/8Q8MZk7qMYBb0vsu80JSNxAjDf18X04BzcDrjiaOF++kCW AQBywddy8rHi0IIhhnHHg==
X-UI-Out-Filterresults: notjunk:1;
Archived-At: <http://mailarchive.ietf.org/arch/msg/dtls-iot/-niRo1f3zm8-DIGjPqL_u-6Fc7A>
Subject: Re: [Dtls-iot] 2nd WGLC on draft-ietf-dice-profile, ending Feb 6th
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, 06 Mar 2015 18:55:35 -0000

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

Hi Ludwig,

thanks for your very detailed review.

I have addressed all your review comments, as you can see below.

On 03/02/2015 10:11 AM, Ludwig Seitz wrote:
> On 01/26/2015 02:28 PM, Zach Shelby wrote:
>> This mail kicks off a 2nd WGLC for our DTLS profile draft:
>>
>> https://tools.ietf.org/html/draft-ietf-dice-profile-09
>>
>> This WGLC will end of Friday, Feb 6th, 2015. Please send your reviews =
to
>> this mailing list. The authors have identified some key reviewers, in
>> addition to those that volunteered in Honolulu.
>>
>> Thanks!
>> Zach & Dorothy
>>
>=20
> Hello list,
>=20
> although the WGLC has ended, I have been asked to provide an additional=

> review by Hannes Tschofenig, which I hereby do.
>=20
> I have divided my findings into "issues", "typos" and "nits":
>=20
>=20
> Issues (3):
>=20
> Section 4.1.1.2. CoAP-based Data Exchange Example
>=20
> I'm not sure that the Resource Directory is intended to relay requests.=

> To my knowledge it is just intended as a lookup service to find out
> metadata about available resources. It would be good to check this with=

> e.g. Zach or Carsten.

I added a note that the description shows OMA LWM2M, which uses RD.

>=20
> ---
> Section 6
>=20
> Is it intentional that section 6 mandates that a device that wants to
> comply with this profile MUST implement ALL OF 6.1, 6.2 and 6.3
>=20
> So a device just implementing DTLS PSK mode with the guidance from 6.1
> would not be considered compliant?
>=20
> If the answer is yes, this seems to place quite a code-size burden
> on constrained devices.

I added a note that clarifies this aspect. Of course, a device that only
uses PSK-based credential only has to implement the recommendations
outlined in Section 6.1.

>=20
> ---
> Section 9. Session Resumption
>=20
> Note that the TLS WG discussed dropping session resumption for
> TLS 1.3 during IETF 89, see slide 4 in
> http://www.ietf.org/proceedings/89/slides/slides-89-tls-5.pdf.
> We should check the status of this before we produce RFCs that rely on
> this mechanism.

I understand the concern but we definitely do not to wait until the work
on TLS 1.3 is finalized.

>=20
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> Typos (6):
>=20
> 3.  TLS/DTLS Protocol Overview, second bullet
>=20
> "is exclusive-ORed with an dentical amount"
>=20
> Should read "identical"
Fixed.

> ---
> "Figure 2: Network Access Architecture.."
>=20
> Remove last period.

Fixed.

> ---
> Figure 6  Local Discovery and Resouce Access.
>=20
> The "Configure ..." arrow is missing its arrowhead.

Fixed.

> ---
> 5. The TLS/DTLS Ciphersuite Concept, 5th bullet
>=20
> "(e.g., HMAC with the SHA-256)"
>=20
> delete "the"

Fixed.

> ---
> 8.  Error Handling
>=20
> "Those include decryption_failed_RESERVED, no_certificate_RESERVE, and
> export_restriction_RESERVED."
>=20
> should read "no_certificate_RESERVED" (give us a 'D'!)
> ---

Fixed.

> 14.  Random Number Generation
> "Since many IoT devices do not have access to a real-time clock this
> recommendation it is RECOMMENDED to follow the guidance outlined in ...=
"
>=20
> delete "this recommendation"

Fixed.

> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> Nits (10):
>=20
> Abstract:
> This gives the impression that we are only dealing with devices
> providing data in form of e.g. sensor readings. An equally common
> pattern would be an actuator that controls some physical system, like a=

> valve, a thermostat or a smart light bulb.


Fixed.

>=20
> ---
>=20
> 3.  TLS/DTLS Protocol Overview, first paragraph
>=20
> "The protocol is composed of two layers: the Record Protocol and the
> Handshake Protocol."
>=20
> There are actually two other protocols in TLS/DTLS, the change cipher
> spec protocol and the alert protocol, although they are subsumed
> together with the handshake protocol as the "handshaking protocols" in
> the RFC.

That's correct. I updated the description but I wanted to keep it as
simple as possible. The problem is that the TLS terminology isn't all
that great and the design is somewhat chaotic.
>=20
> ---
> 3.  TLS/DTLS Protocol Overview, last bullet
>=20
> "Furthermore, the handshake message format has been extended to deal
> with message loss, reordering, and fragmentation.  Retransmission timer=
s
> have been included to deal with message loss."
>=20
> This sounds weird due to the repetition of "message loss". Does the
> message format really have any role in dealing with message loss?

Fixed.

>=20
> ---
> 4.1.1.1.  Network Access Authentication Example, second paragraph
>=20
> "To route EAP messages ..., name RADIUS or Diameter."
>=20
> A citation of the rfcs would be appropriate here
> [RFC2865] and [RFC6733].
>=20

Added.

> ---
> 4.1.1.1.  Network Access Authentication Example, pages 7-8
>=20
> "The EAP-TLS exchange is shown in Figure 3 where it is worthwhile to
> point out that in EAP the client / server roles are reversed but with
> the use of EAP-TLS the IoT device acts as a TLS client.
>=20
> This last sentence is unclear, reversed with respect to what? Does the
> TLS client become the EAP server?

Clarified it. I believe the role change between the client and the
server in EAP and the EAP method is not that relevant for this document.

> ---
> 4.1.1.2.  CoAP-based Data Exchange Example, second paragraph
>=20
> "Figure 4 shows a sensor starting with a DTLS exchange with a resource
>    directory to register available resources."
>=20
> I'd remove the first "with"

Fixed.

> ---
> 6.3.  Certificates, page 22
>=20
> "Note that the Service Name ... to convey EUI-64 identifiers."
>=20
> The citation [EUI64] appearing later in the text should be here instead=
=2E

Fixed.

> ---
> 8. Error Handling
> "TLS/DTLS uses the Alert protocol to convey error messages and specifie=
s
> a longer list of errors."
>=20
> Longer than what?

Fixed.

> ---
> 14.  Random Number Generation
> "Special care has to be paid when generating random numbers ..."
>=20
> "pay attention" but "take care", I'd say "Special care has to be
> taken..."

Fixed.

> ---
> 14.  Random Number Generation
>=20
> followed by a random sequence of 28 random bytes
>=20
> delete the first "random"
>=20
Fixed.


Ciao
Hannes

>=20
>=20
> _______________________________________________
> dtls-iot mailing list
> dtls-iot@ietf.org
> https://www.ietf.org/mailman/listinfo/dtls-iot
>=20


--X7OnKrJQEk626D7Gu5j4bQKlIrRmfPc2l
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

iQEcBAEBCgAGBQJU+fgeAAoJEGhJURNOOiAtEfsH/i8eV5qyiiQESZ+VO2tM4JGq
Bn5Kl4ExqKtDpF1YMfEFImg196JT3TAkM+s794zb+jpRG/UgEKMrEzjY8oBEQdpw
zqBwzGtvivIRf1sho90qdKq73FsLZIZm+S7JZsbAvJ8bdcf+Y+tSQfSCVYrjEdt8
bRr2SiEeQtZiLwu38o3l8w14HxfDABNu9rnmINKWmVnsaUzfuhNppPACdOw0jvak
0XJjM+8dJ4HJGV7y9CsA+B/ZeYKiriyxa9M/lUQ3ZPZx69V9hXq6Xg5JwDwta/8J
YXEYYtPYBP/i0Z2yOpmRRq3W41FlyMfFT33iRGZ45BXULszBVhgLszKL+EbkxX0=
=gCHe
-----END PGP SIGNATURE-----

--X7OnKrJQEk626D7Gu5j4bQKlIrRmfPc2l--


From nobody Fri Mar  6 11:36:00 2015
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 D1EB01A6F05 for <dtls-iot@ietfa.amsl.com>; Fri,  6 Mar 2015 11:35:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 XUpjcvdC6S12 for <dtls-iot@ietfa.amsl.com>; Fri,  6 Mar 2015 11:35:56 -0800 (PST)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.21]) (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 C988C1A6F28 for <dtls-iot@ietf.org>; Fri,  6 Mar 2015 11:35:50 -0800 (PST)
Received: from [192.168.131.143] ([80.92.121.102]) by mail.gmx.com (mrgmx102) with ESMTPSA (Nemesis) id 0LcVOE-1XmhL03IYw-00joqa for <dtls-iot@ietf.org>; Fri, 06 Mar 2015 20:35:49 +0100
Message-ID: <54FA0194.3010604@gmx.net>
Date: Fri, 06 Mar 2015 20:35:48 +0100
From: Hannes Tschofenig <hannes.tschofenig@gmx.net>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: "dtls-iot@ietf.org" <dtls-iot@ietf.org>
References: <D11E4487.23F8C%thomas.fossati@alcatel-lucent.com> <F01D8B85CFF58440B2A13965FBA90CA4CE7B9A1921@GEORGE.Emea.Arm.com>
In-Reply-To: <F01D8B85CFF58440B2A13965FBA90CA4CE7B9A1921@GEORGE.Emea.Arm.com>
OpenPGP: id=4D776BC9
Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="54VCRCjtsOWtscCha2GAQSK66hJvsC4iP"
X-Provags-ID: V03:K0:GDf/HgJrosrAyQfaKGIU/Vkl8xrgHHd+0qMj6Q77sW58/puA/Pb lvrKHmP0ftobLi/QDTAtZYXILoNKAnde/Tq4GQHBrQpPVBE5ygFzVpqjeX+vJ1w6O2RxJhR 11paSfHWXHsZYj6K2gY5EkNY6SCXWEQjK4BTVCrK2OlalN48ELMdVDHBr63YM2FhjhLr/Ht zTBLnsEg8YARViF2dwnaA==
X-UI-Out-Filterresults: notjunk:1;
Archived-At: <http://mailarchive.ietf.org/arch/msg/dtls-iot/vL5xv6wcQen99JiXx2CKfjBpeLM>
Subject: Re: [Dtls-iot] review up to section 4
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, 06 Mar 2015 19:35:59 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--54VCRCjtsOWtscCha2GAQSK66hJvsC4iP
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

Hi Thomas,

thanks for proofreading. All comments addressed but a few questions below=
=2E

> *From:*FOSSATI, Thomas (Thomas) [mailto:thomas.fossati@alcatel-lucent.c=
om]
> *Sent:* 05 March 2015 18:38
> *To:* Hannes Tschofenig
> *Subject:* review up to section 4
>=20
> =20
>=20
> Hi Hannes, a first batch of comments.  Will continue later tonight.
>=20
> Cheers, t
>=20
> =3D-=3D-=3D-=3D-=3D-=3D
>=20
> *Abstract (restructured)*
>=20
> =20
>=20
> A typical design pattern in Internet of Things (IoT) deployments sees a=

> constrained device (i.e. sensor/actuator) making its resources availabl=
e
> to other networked agents.
>=20
> =20
>=20
> This document defines a Transport Layer Security (TLS) and Datagram TLS=

> (DTLS) 1.2 profile specifically targeted to constrained devices that ca=
n
> be used to prevent eavesdropping, tampering, and message forgery of the=

> exchanged data.
>=20

[Hannes] I changed the intro based on earlier comments already to:

"
Abstract

   A common design pattern in Internet of Things (IoT) deployments is
   the use of a constrained device that collects data via sensor or
   controls actuators for use in home automation, industrial control
   systems, smart cities and other IoT deployments.

   This document defines a Transport Layer Security (TLS) and Datagram
   TLS (DTLS) 1.2 profile that offers communications security for this
   data exchange thereby preventing eavesdropping, tampering, and
   message forgery.  The lack of communication security is a common
   vulnerability in Internet of Things products that can easily be
   solved by using these well-researched and widely deployed Internet
   security protocols.
"

Would this work for you as well?


> =20
>=20
> *Introduction*
>=20
> =20
>=20
> s/to make data available/to exchange data
>=20
Changed.

> s/To make Internet protocols fit constrained devices/Fitting internet
> protocols into constrained devices

Fixed.

/
>=20
> s/this document is inspired by the desire/the main goal for this
> document is/

Fixed.

>=20
> s/the guidance in this document/the information contained in the
> following sections/

Fixed.

>=20
> s/offers communication security for IoT applications/offers
> communication security services for generic IoT applications/
>=20
Fixed.

> s/any new TLS/DTLS extensions/any new TLS/DTLS extension/
Fixed.

>=20
> s/Internet of Things product development./Internet of Things product./
>=20

Fixed.

> =20
>=20
> *Terminology*
>=20
> =20
>=20
> s/which are small devices/which are made of small devices/
>=20
> =20
Fixed.

>=20
> *TLS/DTLS Protocol Overview (partially restructured)*
>=20
> The TLS protocol [RFC5246] provides authenticated, confidentiality- and=

> integrity-protected communication between two endpoints.  The
> protocol is composed of two layers: the Record protocol, which sits on
> top of a reliable transport (e.g. TCP) and provides the basic framing
> and cryptographic processing to a number of higher layer protocols
> (Handshake, Alert, Application, Heartbeat, ChangeCipherSpec) each of
> which implements a different function. In particular, the Handshake
> protocol is run at the beginning of every TLS session and allows server=

> and client to authenticate each other and negotiate the cryptographic
> keys and algorithms used throughout the session.
>=20
> =20


I now have two versions, namely the version Ludwig suggested and the
version you suggest. Tell me which one to use.

Version 1:

   The TLS protocol [RFC5246] provides authenticated, confidentiality-
   and integrity-protected communication between two endpoints.  The
   protocol is composed of two layers: the Record protocol, which sits
   on top of a reliable transport (e.g., TCP) and provides the basic
   framing and cryptographic processing to a number of higher layer
   protocols (Handshake, Alert, Application, Heartbeat,
   ChangeCipherSpec) each of which implements a different function.  In
   particular, the Handshake protocol is run at the beginning of every
   TLS session and allows server and client to authenticate each other
   and negotiate the cryptographic keys and algorithms used throughout
   the session.

Version 2:

   The TLS protocol [RFC5246] provides authenticated, confidentiality-
   and integrity-protected communication between two endpoints.  The
   protocol is composed of two layers: the Record Protocol and the
   Handshaking Protocols.  At the lowest level, layered on top of a
   reliable transport protocol (e.g., TCP), is the Record Protocol.  It
   provides connection security by using symmetric cryptography for
   confidentiality, data origin authentication, and integrity
   protection.  The Record Protocol is used for encapsulation of various
   higher-level protocols.  The handshaking protocols consist of three
   sub-protocols, namely the handshake protocol, the change cipher spec
   protocol and the alert protocol.  The handshake protocol allows the
   server and client to authenticate each other and to negotiate an
   encryption algorithm and cryptographic keys before the application
   protocol transmits or receives data.

>=20
> The design of DTLS [...]
>=20
> =20
>=20
> s/Since DTLS operates on top of an unreliable datagram transport a few
> enhancements to the TLS structure are, however necessary./However, sinc=
e
> DTLS operates on top of an unreliable datagram transport, it must
> explicitly cope with the reliable and ordered delivery assumptions made=

> by TLS./
>=20
Fixed.

> =20
>=20
> s/Section 4.7 of RFC 5246 defines stream ciphers in TLS as follows.  In=

> stream.../Section 4.7 of RFC 5246 defines stream ciphers in TLS as
> follows: in stream.../
>=20
>=20
Fixed.

Ciao
Hannes


--54VCRCjtsOWtscCha2GAQSK66hJvsC4iP
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

iQEcBAEBCgAGBQJU+gGUAAoJEGhJURNOOiAt2WAH/iAA4nFbgUqsIPl+lveup5pn
UrVE4+xs+juCuhynd0cIj2OkrsQ0CJgcVr9OJIG1RM28BgCcS0klPoOmBTdQv7bB
iAYmR0q885g8ZOEzjgBzyv7Wk/RQkfcoxzkpRClYzTD+14lNwPUGR/E5O4BIROu4
oPr6Qt3ZgsIWpMt0U6t0jiRqD+dnihPnTOSfFCSqiDMy7X3wQ2EYlx4Z/pG+cJBc
YsepXXC+ZKn/5ZYG+uCOkfwaU6d/njjOIF6vDujbPZuBIt0+uKWJh6b7w1za/dht
USCs8cn0SKCTeF8mG8Vm/WZAYho0VskDbYyDwYBTmAAqtoAdQq3BIQfksxevqFM=
=xlyZ
-----END PGP SIGNATURE-----

--54VCRCjtsOWtscCha2GAQSK66hJvsC4iP--


From nobody Fri Mar  6 11:36:31 2015
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 3A87D1A6F3A for <dtls-iot@ietfa.amsl.com>; Fri,  6 Mar 2015 11:36:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 kpXyrryxnmoX for <dtls-iot@ietfa.amsl.com>; Fri,  6 Mar 2015 11:36:28 -0800 (PST)
Received: from mout.gmx.net (mout.gmx.net [212.227.15.18]) (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 630E51A6F28 for <dtls-iot@ietf.org>; Fri,  6 Mar 2015 11:36:28 -0800 (PST)
Received: from [192.168.131.143] ([80.92.121.102]) by mail.gmx.com (mrgmx003) with ESMTPSA (Nemesis) id 0MO7ee-1YQgms0ysG-005Vj3 for <dtls-iot@ietf.org>; Fri, 06 Mar 2015 20:36:26 +0100
Message-ID: <54FA01BA.20509@gmx.net>
Date: Fri, 06 Mar 2015 20:36:26 +0100
From: Hannes Tschofenig <hannes.tschofenig@gmx.net>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: "dtls-iot@ietf.org" <dtls-iot@ietf.org>
References: <F01D8B85CFF58440B2A13965FBA90CA4CE7B9A19C3@GEORGE.Emea.Arm.com>
In-Reply-To: <F01D8B85CFF58440B2A13965FBA90CA4CE7B9A19C3@GEORGE.Emea.Arm.com>
OpenPGP: id=4D776BC9
X-Forwarded-Message-Id: <F01D8B85CFF58440B2A13965FBA90CA4CE7B9A19C3@GEORGE.Emea.Arm.com>
Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="bxj0NumuWbp1SnO10x27cNPFhF1NvgjNd"
X-Provags-ID: V03:K0:kr23Bzxrd8e8cH9gXocKKRQwIP6TdCcgnGIOU1zkoAS6dwgHNpO monGWkbUp4PV4i90Au00mo6N0VfzN89+C72/JU9rhSJIvDn7TsmtPLl15bxsRAFHkW9Cpr5 m8JKGa4ppVPDsqpFnv+kLcyi/asfQZmykFwe9QfY6uk13z1DeH94ymixvnErKx86DUDMWfV H8hb+JoQA1TLSSX8DEtTQ==
X-UI-Out-Filterresults: notjunk:1;
Archived-At: <http://mailarchive.ietf.org/arch/msg/dtls-iot/BIzkij4nWCgyTzVcn6Zv8fMxFh8>
Subject: Re: [Dtls-iot] review part 2/2
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, 06 Mar 2015 19:36:30 -0000

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

Hi Thomas,

thanks for doing another proofreading.

I addressed all your comments except for one (see below).

-----------------------------------------------------------------

*From:*FOSSATI, Thomas (Thomas) [mailto:thomas.fossati@alcatel-lucent.com=
]
*Sent:* 06 March 2015 08:05
*To:* Hannes Tschofenig
*Subject:* review part 2/2



Hi Hannes, the last batch of my review comments.



(Today I'll be out of office and my connectivity could be spotty.)



Cheers, t



=3D-=3D-=3D-=3D-=3D-=3D-=3D



*Communication Models*



s/./: one for constrained clients (Section 4.1), and another for
constrained servers (Section 4.2).



[hannes] Fixed with one of the earlier reviews.


*Network Access Authentication Example*



s/Phyiscal layer like IEEE 802.11/802.15.4/Physical layer, e.g. IEEE
802.11/802.15.4/

[hannes] Fixed.



*Constrained TLS/DTLS Servers*



s/The entire process is likely to be controlled by a third party, the
authentication and authorisation server/The entire process is likely,
but not necessarily, controlled by a third party, the authentication and
authorisation server/

[hannes] Fixed.


  * Stray comma in the "Configuration" table

[hannes] Fixed.


s/A client must first and formost/A client must first and foremost/

[hannes] Fixed.

s/Since RD is not a proxy clients/Since RD is not a proxy, clients/

[hannes] Fixed with one of the earlier reviews.


*Appendix A.3*



Note that The source and destination ports MUST be encoded using the
Application port addressing scheme Information Element in the User Data
Header.

[hannes] Not quite sure to which paragraph this refers to.




s/The total overhead cost for encoding the WDP source and
destination ports is 7 bytes out of the total available for the SMS
content./The total overhead cost for encoding the WDP source and
destination ports is either 5 or 7 bytes out of the total available for
the SMS content depending on if 1-byte or 2-byte port identifiers are
used (see below)./

* Application port addressing scheme, 8 bit address:

0        1        2        3        4
+--------+--------+--------+--------+--------+
| ...    | 0x04   | 2      | ...    | ...    |
+--------+--------+--------+--------+--------+
  UDH      IEI      IE       Dest     Source
  Length            Length   Port     Port



* Application port addressing scheme, 16 bit address:

0        1        2        3        4        5        6
+--------+--------+--------+--------+--------+--------+--------+
| ...    | 0x05   | 4      |       ...       |       ...       |
+--------+--------+--------+--------+--------+--------+--------+
  UDH      IEI      IE       Dest              Source
  Length            Length   Port              Port


[hannes] Fixed text and added diagrams. It is useful to show this
graphically.



*Appendix C*



s/However, when the handshake is carried over a narrow-band radio
technology/However, an handshake that is carried over a narrow-band
radio technology/

s/can put a cost/can place a cost/

[hannes] Fixed.


Ciao
Hannes


--bxj0NumuWbp1SnO10x27cNPFhF1NvgjNd
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

iQEcBAEBCgAGBQJU+gG6AAoJEGhJURNOOiAttoUH/i8Q9hlNfORpuVdRznHzth8/
H949c18UE6BE+pacfx4bkSZUeXXx3Oj3OcmrCBFtn+FV1c97sIJlYF9zV5fS4LhQ
d6S2Oq5j+zIkMiW77RI/ASqPg2jO1hDLHGtw9u9ehCpZDL08FPUR6pA9V+CHF7Wg
/4bYmcugW8VeKqTHLcF/UY1WxKPTsh5YCB7La/mgS9brRyor/DaN2BR7cNOugYfR
vbwb3U+gbX2IfwVfFR+k+U3jI2qayRCI7Oet1fUFn48SW5/vijLsdte5e7yB+1Cf
BSqTf0YaoA0N9bOe2tjeUsRy4OJhHrtGpmkjP9jpZuAoGcimrY1qu12axmlcKZQ=
=cbul
-----END PGP SIGNATURE-----

--bxj0NumuWbp1SnO10x27cNPFhF1NvgjNd--


From nobody Fri Mar  6 13:31:48 2015
Return-Path: <thomas.fossati@alcatel-lucent.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 E32181A1A8A for <dtls-iot@ietfa.amsl.com>; Fri,  6 Mar 2015 13:31:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.91
X-Spam-Level: 
X-Spam-Status: No, score=-6.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, T_RP_MATCHES_RCVD=-0.01] 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 ohflhU7VTL4L for <dtls-iot@ietfa.amsl.com>; Fri,  6 Mar 2015 13:31:45 -0800 (PST)
Received: from smtp-fr.alcatel-lucent.com (fr-hpida-esg-02.alcatel-lucent.com [135.245.210.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7F0701A044D for <dtls-iot@ietf.org>; Fri,  6 Mar 2015 13:31:44 -0800 (PST)
Received: from fr712usmtp2.zeu.alcatel-lucent.com (unknown [135.239.2.42]) by Websense Email Security Gateway with ESMTPS id 6BA9A8D81AEDB; Fri,  6 Mar 2015 21:31:38 +0000 (GMT)
Received: from FR711WXCHHUB01.zeu.alcatel-lucent.com (fr711wxchhub01.zeu.alcatel-lucent.com [135.239.2.111]) by fr712usmtp2.zeu.alcatel-lucent.com (GMO) with ESMTP id t26LVfTd032519 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 6 Mar 2015 22:31:41 +0100
Received: from FR711WXCHMBA08.zeu.alcatel-lucent.com ([169.254.4.234]) by FR711WXCHHUB01.zeu.alcatel-lucent.com ([135.239.2.111]) with mapi id 14.03.0195.001; Fri, 6 Mar 2015 22:31:41 +0100
From: "FOSSATI, Thomas (Thomas)" <thomas.fossati@alcatel-lucent.com>
To: Hannes Tschofenig <hannes.tschofenig@gmx.net>, "dtls-iot@ietf.org" <dtls-iot@ietf.org>
Thread-Topic: [Dtls-iot] review up to section 4
Thread-Index: AQHQV2sijPPHnF5F40295YwwWQaG4p0P2r4vgAAPgoA=
Date: Fri, 6 Mar 2015 21:31:41 +0000
Message-ID: <D11FCACB.24095%thomas.fossati@alcatel-lucent.com>
References: <D11E4487.23F8C%thomas.fossati@alcatel-lucent.com> <F01D8B85CFF58440B2A13965FBA90CA4CE7B9A1921@GEORGE.Emea.Arm.com> <54FA0194.3010604@gmx.net>
In-Reply-To: <54FA0194.3010604@gmx.net>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.4.8.150116
x-originating-ip: [135.239.27.41]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <589C0BD921BA8E49923BCCE89309D0AB@exchange.lucent.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/dtls-iot/m3mxmNpwbjqrz-v--xbB1R1-6TY>
Subject: Re: [Dtls-iot] review up to section 4
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, 06 Mar 2015 21:31:47 -0000

On 06/03/2015 19:35, "Hannes Tschofenig" <hannes.tschofenig@gmx.net> wrote:
>[Hannes] I changed the intro based on earlier comments already to:
>
>"
>Abstract
>
>   A common design pattern in Internet of Things (IoT) deployments is
>   the use of a constrained device that collects data via sensor or
>   controls actuators for use in home automation, industrial control
>   systems, smart cities and other IoT deployments.
>
>   This document defines a Transport Layer Security (TLS) and Datagram
>   TLS (DTLS) 1.2 profile that offers communications security for this
>   data exchange thereby preventing eavesdropping, tampering, and
>   message forgery.  The lack of communication security is a common
>   vulnerability in Internet of Things products that can easily be
>   solved by using these well-researched and widely deployed Internet
>   security protocols.
>"
>
>Would this work for you as well?

Yes it will, thanks.


From nobody Fri Mar  6 13:31:57 2015
Return-Path: <thomas.fossati@alcatel-lucent.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 38B8E1A8732 for <dtls-iot@ietfa.amsl.com>; Fri,  6 Mar 2015 13:31:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.91
X-Spam-Level: 
X-Spam-Status: No, score=-6.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, T_RP_MATCHES_RCVD=-0.01] 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 looldQtnb4ZJ for <dtls-iot@ietfa.amsl.com>; Fri,  6 Mar 2015 13:31:49 -0800 (PST)
Received: from smtp-fr.alcatel-lucent.com (fr-hpgre-esg-01.alcatel-lucent.com [135.245.210.22]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A6C681A8730 for <dtls-iot@ietf.org>; Fri,  6 Mar 2015 13:31:49 -0800 (PST)
Received: from fr711usmtp1.zeu.alcatel-lucent.com (unknown [135.239.2.122]) by Websense Email Security Gateway with ESMTPS id B3B41388E137A; Fri,  6 Mar 2015 21:31:44 +0000 (GMT)
Received: from FR712WXCHHUB03.zeu.alcatel-lucent.com (fr712wxchhub03.zeu.alcatel-lucent.com [135.239.2.74]) by fr711usmtp1.zeu.alcatel-lucent.com (GMO) with ESMTP id t26LVlEp019215 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 6 Mar 2015 22:31:48 +0100
Received: from FR711WXCHMBA08.zeu.alcatel-lucent.com ([169.254.4.234]) by FR712WXCHHUB03.zeu.alcatel-lucent.com ([135.239.2.74]) with mapi id 14.03.0195.001; Fri, 6 Mar 2015 22:31:47 +0100
From: "FOSSATI, Thomas (Thomas)" <thomas.fossati@alcatel-lucent.com>
To: Hannes Tschofenig <hannes.tschofenig@gmx.net>, "dtls-iot@ietf.org" <dtls-iot@ietf.org>
Thread-Topic: [Dtls-iot] review part 2/2
Thread-Index: AQHQWETdH062wwINhUGr0qzYamyuM50P6JAA
Date: Fri, 6 Mar 2015 21:31:47 +0000
Message-ID: <D11FCA3C.24091%thomas.fossati@alcatel-lucent.com>
References: <F01D8B85CFF58440B2A13965FBA90CA4CE7B9A19C3@GEORGE.Emea.Arm.com> <54FA01BA.20509@gmx.net>
In-Reply-To: <54FA01BA.20509@gmx.net>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.4.8.150116
x-originating-ip: [135.239.27.41]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <4DFBC0D2ECE1EC4C8E219C3BCDEE12A0@exchange.lucent.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/dtls-iot/I2S9wXgvjqb9CX51ytrK6Rfb7SE>
Subject: Re: [Dtls-iot] review part 2/2
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, 06 Mar 2015 21:31:54 -0000

Hi Hannes,

On 06/03/2015 19:36, "Hannes Tschofenig" <hannes.tschofenig@gmx.net> wrote:
>I addressed all your comments except for one (see below).
>
>[...]
>
>Note that The source and destination ports MUST be encoded using the
>Application port addressing scheme Information Element in the User Data
>Header.
>
>[hannes] Not quite sure to which paragraph this refers to.

Sorry this was just a note to self, you can safely ignore it.

Cheers and thanks.


From nobody Fri Mar  6 13:36:32 2015
Return-Path: <thomas.fossati@alcatel-lucent.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 958991A86EE for <dtls-iot@ietfa.amsl.com>; Fri,  6 Mar 2015 13:36:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.91
X-Spam-Level: 
X-Spam-Status: No, score=-6.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, T_RP_MATCHES_RCVD=-0.01] 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 E_DVPBsASb0T for <dtls-iot@ietfa.amsl.com>; Fri,  6 Mar 2015 13:36:29 -0800 (PST)
Received: from smtp-fr.alcatel-lucent.com (fr-hpgre-esg-01.alcatel-lucent.com [135.245.210.22]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D1E1E1A86FB for <dtls-iot@ietf.org>; Fri,  6 Mar 2015 13:36:28 -0800 (PST)
Received: from fr711usmtp1.zeu.alcatel-lucent.com (unknown [135.239.2.122]) by Websense Email Security Gateway with ESMTPS id 181EAAE33020B; Fri,  6 Mar 2015 21:36:24 +0000 (GMT)
Received: from FR711WXCHHUB01.zeu.alcatel-lucent.com (fr711wxchhub01.zeu.alcatel-lucent.com [135.239.2.111]) by fr711usmtp1.zeu.alcatel-lucent.com (GMO) with ESMTP id t26LaQIQ022284 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 6 Mar 2015 22:36:27 +0100
Received: from FR711WXCHMBA08.zeu.alcatel-lucent.com ([169.254.4.234]) by FR711WXCHHUB01.zeu.alcatel-lucent.com ([135.239.2.111]) with mapi id 14.03.0195.001; Fri, 6 Mar 2015 22:36:26 +0100
From: "FOSSATI, Thomas (Thomas)" <thomas.fossati@alcatel-lucent.com>
To: Rene Hummen <Rene.Hummen@comsys.rwth-aachen.de>, Hannes Tschofenig <hannes.tschofenig@gmx.net>
Thread-Topic: [Dtls-iot] Review of draft-ietf-dice-profile-10
Thread-Index: AQHQWFWZY+AToFxN/kWenf3HQsbfnQ==
Date: Fri, 6 Mar 2015 21:36:26 +0000
Message-ID: <D11FCD68.240A6%thomas.fossati@alcatel-lucent.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.4.8.150116
x-originating-ip: [135.239.27.38]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <EE4923527E4D1C49AC88A50594D6C887@exchange.lucent.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/dtls-iot/wav975uvRGJNJst1VzWjGfl4daw>
Cc: "dtls-iot@ietf.org" <dtls-iot@ietf.org>
Subject: Re: [Dtls-iot] Review of draft-ietf-dice-profile-10
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, 06 Mar 2015 21:36:31 -0000

Hi Rene, thanks for you review.

On 06/03/2015 17:45, "Rene Hummen" <Rene.Hummen@comsys.rwth-aachen.de>
wrote:
>12) Appendix A (line 2673 and below)
>
>In contrast to the remaining profile, this (obviously) is very link layer
>specific normative text. Why not move this to a short separate document?

Initially this was in fact a separate I-D:
https://datatracker.ietf.org/doc/draft-fossati-dtls-over-gsm-sms/

It has been incorporated into the DICE profile with
http://trac.tools.ietf.org/wg/dice/trac/ticket/15

Cheers, t


From nobody Sat Mar  7 02:08:15 2015
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 B3CD81A8A89 for <dtls-iot@ietfa.amsl.com>; Sat,  7 Mar 2015 02:08:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 xwoZdU1s-yCc for <dtls-iot@ietfa.amsl.com>; Sat,  7 Mar 2015 02:08:11 -0800 (PST)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.22]) (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 A40F31A8A91 for <dtls-iot@ietf.org>; Sat,  7 Mar 2015 02:08:10 -0800 (PST)
Received: from [192.168.131.144] ([80.92.121.102]) by mail.gmx.com (mrgmx102) with ESMTPSA (Nemesis) id 0LhCDT-1XiWZc3xix-00oVkU; Sat, 07 Mar 2015 11:08:08 +0100
Message-ID: <54FACE06.50506@gmx.net>
Date: Sat, 07 Mar 2015 11:08:06 +0100
From: Hannes Tschofenig <hannes.tschofenig@gmx.net>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: Rene Hummen <Rene.Hummen@comsys.rwth-aachen.de>
References: <04D4A5C6-540E-4080-A762-EA7097445FE1@comsys.rwth-aachen.de>
In-Reply-To: <04D4A5C6-540E-4080-A762-EA7097445FE1@comsys.rwth-aachen.de>
OpenPGP: id=4D776BC9
Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="w079gXO9fw2Kw0C03eQlGTmdAiQI9Ga9L"
X-Provags-ID: V03:K0:lF6K96oJGkywSUdJtDmE0xtTcipaqXtOGgcIWi7lShpZ6kb/5Pu 4RRwV1JP0n9wmqlOE5trFKTxieS3i/4wFShmbNqeAjB7fpLcuWiEMHCe5LkLOvG/lVf6X5h 5+hhvXzQ9HNdi7CkmNRYZiTmi3Ts7kNBQP6meWNdyeuDUu8og34MXiWPWtSD+kDBcavYu7Y CUFkbo4nO2EyMM+LpXExw==
X-UI-Out-Filterresults: notjunk:1;
Archived-At: <http://mailarchive.ietf.org/arch/msg/dtls-iot/BbQqnUwX4ofBvNgkM2asL96mdko>
Cc: "dtls-iot@ietf.org" <dtls-iot@ietf.org>
Subject: Re: [Dtls-iot] Review of draft-ietf-dice-profile-10
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: Sat, 07 Mar 2015 10:08:13 -0000

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

Hi Rene,

thanks for your timely review.

On 03/06/2015 06:45 PM, Rene Hummen wrote:
> Hi Hannes, Thomas, list,
>=20
> sorry for the late feedback. Since you already revised parts of
> draft-ietf-dice-profile-09, I decided to read
> draft-ietf-dice-profile-10 instead ([1] from GitHub). I am especially
> glad to see constrained servers to be included this time around.

It was definitely a good idea to look at the latest snapshot since I
have in the meanwhile incorporated various WGLC review comments into the
document.


> These are my remaining comments:
>=20
> 1) As a general comment that applies to the whole document: Would it
> make sense to replace the =93is envisioned=94 / =93is not envisioned=94=
 and
> =93are not applicable=94 with SHOULDs and MUSTs (NOT)?

I changed text where relevant. In some cases the words 'not applicable'
seems more appropriate. I use the word in a context where it does not
make sense to use a certain feature.

>=20
> 2) Figure 1 should also mention the client=92s private key (or simply
> call it a public/private key-pair).

Fixed.

>=20
> 3) Section 4.2 (starting from line 689)
>=20
> "In this section we look at cases where constrained devices run TLS/=20
> DTLS servers to secure access to application layer services running=20
> on top of CoAP, HTTP or other protocols.  Running server=20
> functionality on a constrained node is typically more demanding
> since servers have to wait for incoming requests.  Therefore, they
> will have fewer possibilities to enter sleep-cycles.  Nevertheless,
> there are legitimate reasons for deploying servers as constrained
> devices.=94
>=20
> Is there a need to educate the reader about the
> advantages/disadvantages of constrained servers? I suggest to replace
> the above text with the following:
>=20
> "In this section, we assume a scenario where constrained devices run
> TLS/ DTLS servers to secure access to application layer services
> running on top of CoAP, HTTP or other protocols.=94

I thought the reader may not know that.

I put your proposal in there although I am not 100% sure whether it
actually makes the text better to remove this additional background
information.

>=20
> Moreover, first introducing the example and then outlining the
> challenge seems to be the inverted order. Why not outline the
> challenges first and then describe the example as one possible way to
> solve them?

Good point. I reversed the order.

>=20
> In the example, why do you assume that reading the temperature sensor
> does not require authentication? The temperature information is the
> basis for the subsequent decision to turn on the fan, which in the
> example requires protection. An adversary could then still control
> the fan via the thermostat by injecting forged temperature
> information. IMHO, all communication in this scenario should be
> protected to give a clear message that network security is important
> for the entire system.

Certainly correct. I changed the example.

>=20
> Minor nits:
>=20
> "Below we explain how these challenges have been solved with CoAP, as
> an example.=94
>=20
> should be
>=20
> "Below we explain how these challenges __can be__ solved with CoAP,
> as an example.=94

Fixed.

>=20
>=20
> "Since RD is usually not a proxy clients can discover links
> registered with the RD and then access them directly."
>=20
> should be
>=20
> "Since RD is usually not a proxy__,__ clients can discover links
> registered with the RD and then access them directly.=94
>=20

Fixed.

>=20
>=20
> 4) Section 5 (line 1025)
>=20
> "SHA-256 is the recommended default PRF.=94
>=20
> In which document? The DTLS profile or the (D)TLS specification?
>=20

Actually, the story is a bit more complex since the PRF is part of the
ciphersuite definition and while the TLS 1.2 spec says that new
ciphersuites should use the SHA-256 based construction it also allows a
ciphersuite to define else. I added extra text to the 'The Ciphersuite
Concept' section.


>=20
>=20
> 5) Section 6 (line 1033)
>=20
> "Note that shared secrets are not passwords.=94
>=20
> should be
>=20
> "Note that shared secrets are not passwords, but binary blobs of
> random data.=94
>=20
>=20

I changed the text to make the message clearer:

"
When using pre-shared key, a critical consideration is how to assure the
randomness of these secrets.  The best practice is to ensure that any
pre-shared key contains as much randomness as possible. Deriving a
shared secret from a password, name, or other low-entropy source is not
secure. A low-entropy secret, or password, is subject to dictionary attac=
ks.
"

>=20
> 6) Section 6.1 (line 1116)
>=20
> The paragraph about the PSK identity hint is still unclear. Does this
> paragraph argue for or against using the hint? I guess, the strange
> thing about this paragraph is that it first introduces the hint as
> something that one actually might want to use. Then, however,
> recommends _against_ doing so=85twice:
>=20
> =93If [=85] the server then servers SHOULD NOT send the "PSK identity=20
> hint" in the ServerKeyExchange message.  Servers SHOULD NOT send the=20
> "PSK identity hint" in the ServerKeyExchange message and clients
> MUST ignore the message.=94
>=20
> Plus, directly afterwards, there is a recommendation on how the SNI
> value can be used to help select the hint.

Given all this uncertainty about the PSK identity hint I removed the
paragraph.
>=20
>=20
> Would it make sense to add a recommendation about a minimum PSK
> length following this text in the current specification?
>=20
> =93Implementations in compliance with this profile MAY use PSK
> identities up to 128 octets in length, and arbitrary PSKs up to 64
> octets in length.  The use of shorter PSK identities and shorter PSKs
> is RECOMMENDED.=94
>=20

The problem is that we do not know what guidance to give since it
depends on a variety of factors.

>=20
>=20
> 7) Section 6.3 (line 1249 and below)
>=20
> "The use of the Trust Anchor Management Protocol (TAMP) [RFC5934] is,
> however, not envisioned. Instead IoT devices using this profile MUST
> use a software update mechanism to populate the trust anchor store.=94
>=20
> Is it really necessary to be so strict in how the trust anchor store
> is populated? Doesn=92t it suffice to say:
>=20
> "The Trust Anchor Management Protocol (TAMP) [RFC5934], however,
> SHOULD NOT be used. Instead, IoT devices using this profile SHOULD
> use a software update mechanism to populate the trust anchor store.=94
>=20

In a variety of places we say that we need a software update mechanism
and, hence, it makes little sense to be vague about the intentions.


>=20
> I guess, this is a typo =93dNSName".
>=20
>=20
Nope. This is how RFC 5280 calls it.

I added a reference.

>=20
> 8) Section 6.3.2 (line 1482)
>=20
> "Since the server does not necessarily know what trust anchors the
> client has stored it includes intermediate CA certs in the
> certificate payload as well to facilitate with certification path=20
> construction and path validation."
>=20
> should be
>=20
> "Since the server does not necessarily know what trust anchors the
> client has stored and to facilitate certification path construction
> as well as path validation, it includes intermediate CA certs in the
> certificate payload.=94
>=20
Fixed.

>=20
>=20
> 9) Section 13 (line 1836)
>=20
> "Choosing appropriate timeout values is difficult with infrequent
> data transmissions, changing network conditions, and large variance
> in latency.=94
>=20
> The "infrequent data transmissions=94 was confusing as I had the DTLS
> handshake in mind and, at first, didn=92t relate it to the preceding
> note about the round-trip time estimator. This is nit-picking, but
> would it make sense to simply remove "infrequent data transmissions=94
> from this enumeration?
>=20
>=20
Fixed.

>=20
> 10) Section 17 (line 1972)
>=20
> "Ultimately, the main benefit of this extension is it to allows
> client implementations to lower their [=85]=94
>=20
> Remove the =93it=94.
>=20
Fixed.

>=20
>=20
> 11) Section 21 (line 2089 and below)
>=20
> "Ongoing discussions regarding the choice of specific ECC curves will
> also likely to impact implementations.=94
>=20
> Remove the =93to=94.
>=20
Fixed.

>=20
> "Offer access to building blocks in addition (or as an alternative)=20
> to the complete functionality.  For example, a chip manufacturer who
> gives developers access to the AES crypto function can use it to
> build an efficient AES-GCM implementations.  Another example is to
> make a special instruction available that increases the speed of
> speed-up carryless multiplications.=94
>=20
> Why not use ECB as a basic example of a building block?
>=20
I didn't want to go too far with the recommendation about what should be
done in hardware but rather state high-level principles.

>=20
>=20
> 12) Appendix A (line 2673 and below)
>=20
> In contrast to the remaining profile, this (obviously) is very link
> layer specific normative text. Why not move this to a short separate
> document?
>=20

As Thomas noted the content of the appendix was actually in a separate
document. When we presented it the recommendation was made to include it
in here since the underlying message about the timeout values is
applicable also to other radio technologies.

I also believe that the text in the appendix does not disrupt
readability for others who do not care about this type of usage.

Ciao
Hannes

>=20
>=20
> BR, Ren=E9
>=20
>=20
> [1]
> https://github.com/hannestschofenig/tschofenig-ids/commit/37d0cfa130904=
dcba6c2d470f286bdb98b81e41d
>
>=20
>=20
> -- Dipl.-Inform. Rene Hummen, Ph.D. Student Chair of Communication
> and Distributed Systems RWTH Aachen University, Germany tel: +49 241
> 80 21426 web: http://www.comsys.rwth-aachen.de/team/rene-hummen/
>=20
>=20
>=20
> _______________________________________________ dtls-iot mailing
> list dtls-iot@ietf.org=20
> https://www.ietf.org/mailman/listinfo/dtls-iot
>=20


--w079gXO9fw2Kw0C03eQlGTmdAiQI9Ga9L
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

iQEcBAEBCgAGBQJU+s4HAAoJEGhJURNOOiAtAP0H/0UI2vyKR7AM5pUjTN2u9yr6
o2rZwhYWmXQh4w9sIQXqDIB41Lc3vchgfmHgapj2bgz+0KLhbaWaOVn+mbPzo7vX
llLtjMM0hisRg/Y2pctSyLBtQcEy8Hs7YF+aXPQg1+ckiCfKGUPt87ijup40valg
khSubg26O4NPDpgQkjb7ktVBYfPUGJZDjgbzv1Hb1QZn3x4UAQ1ByZ6/N/72M6Qo
5HEAP8h7W3Dq2VDX90Q607BbB8dCyIKJGjihCs/+XY0NX/AmhAAeJwx4s4JeOaTR
qMNCchyHE04Hj1xQMFj6Kuc7hePVzBaBynnUYr2l30IX+MW3x2Y1sjY3XVMmOyA=
=jjmE
-----END PGP SIGNATURE-----

--w079gXO9fw2Kw0C03eQlGTmdAiQI9Ga9L--


From nobody Sat Mar  7 02:38:16 2015
Return-Path: <sandeep.kumar@philips.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 54A871A1A62 for <dtls-iot@ietfa.amsl.com>; Sat,  7 Mar 2015 02:38:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.919
X-Spam-Level: 
X-Spam-Status: No, score=-0.919 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_FONT_FACE_BAD=0.981, HTML_MESSAGE=0.001, SPF_HELO_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 77hlyP1kZAe7 for <dtls-iot@ietfa.amsl.com>; Sat,  7 Mar 2015 02:38:10 -0800 (PST)
Received: from emea01-am1-obe.outbound.protection.outlook.com (mail-am1on0781.outbound.protection.outlook.com [IPv6:2a01:111:f400:fe00::781]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 029121A004E for <dtls-iot@ietf.org>; Sat,  7 Mar 2015 02:38:09 -0800 (PST)
Received: from VI1PR04CA0040.eurprd04.prod.outlook.com (25.163.3.50) by DB3PR04MB060.eurprd04.prod.outlook.com (10.242.136.149) with Microsoft SMTP Server (TLS) id 15.1.106.15; Sat, 7 Mar 2015 10:37:51 +0000
Received: from AM1FFO11FD001.protection.gbl (2a01:111:f400:7e00::196) by VI1PR04CA0040.outlook.office365.com (2a01:111:e400:58e9::50) with Microsoft SMTP Server (TLS) id 15.1.106.15 via Frontend Transport; Sat, 7 Mar 2015 10:37:50 +0000
Received: from mail.philips.com (206.191.240.52) by AM1FFO11FD001.mail.protection.outlook.com (10.174.64.83) with Microsoft SMTP Server (TLS) id 15.1.112.13 via Frontend Transport; Sat, 7 Mar 2015 10:37:48 +0000
Received: from DBXPRD9003MB059.MGDPHG.emi.philips.com ([169.254.7.249]) by DBXPRD9003HT003.MGDPHG.emi.philips.com ([141.251.25.208]) with mapi id 14.16.0478.000; Sat, 7 Mar 2015 10:37:48 +0000
From: "Kumar, Sandeep" <sandeep.kumar@philips.com>
To: Hannes Tschofenig <hannes.tschofenig@gmx.net>, Olaf Bergmann <bergmann@tzi.org>
Thread-Topic: [Dtls-iot] 2nd WGLC on draft-ietf-dice-profile, ending Feb 6th
Thread-Index: AdA5a+8tM72XhEoEQqO7kFSQa2axNwI+q3MABTxCEQAABD7gXwACtV6AAAK2CAoAAE6YAABQziVq
Date: Sat, 7 Mar 2015 10:37:48 +0000
Message-ID: <BE6D13F6A4554947952B39008B0DC0153ED0089A@DBXPRD9003MB059.MGDPHG.emi.philips.com>
References: <258751E5-69DB-4787-A7EE-B6C955225AA4@arm.com> <87y4oamwtj.fsf@tzi.org> <54F873CA.4090902@gmx.net>	<877fuvgydx.fsf@tzi.org> <54F8A275.2040602@gmx.net> <87twxzfcdl.fsf@tzi.org>,<54F8B6B6.50103@gmx.net>
In-Reply-To: <54F8B6B6.50103@gmx.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: multipart/alternative; boundary="_000_BE6D13F6A4554947952B39008B0DC0153ED0089ADBXPRD9003MB059_"
MIME-Version: 1.0
X-EOPAttributedMessage: 0
Received-SPF: None (protection.outlook.com: philips.com does not designate permitted sender hosts)
Authentication-Results: spf=none (sender IP is 206.191.240.52) smtp.mailfrom=sandeep.kumar@philips.com; gmx.net; dkim=none (message not signed) header.d=none;
X-Forefront-Antispam-Report: CIP:206.191.240.52; CTRY:US; IPV:NLI; EFV:NLI; BMV:1; SFV:NSPM; SFS:(10019020)(428002)(24454002)(377454003)(374574003)(199003)(479174004)(85714005)(189002)(101416001)(2656002)(16236675004)(19617315012)(50986999)(54356999)(86362001)(55846006)(19580405001)(87936001)(512874002)(33656002)(19580395003)(230783001)(105586002)(84326002)(102836002)(6806004)(77156002)(2950100001)(62966003)(2920100001)(2900100001)(106466001)(93886004)(15975445007)(92566002)(46102003)(76176999)(19625215002)(567094001)(19607625011); DIR:OUT; SFP:1102; SCL:1; SRVR:DB3PR04MB060; H:mail.philips.com; FPR:; SPF:None; MLV:sfv; A:1; MX:1; LANG:en; 
X-Microsoft-Antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:DB3PR04MB060;
X-Microsoft-Antispam-PRVS: <DB3PR04MB060E01C9B579D5074B7E0C4E41D0@DB3PR04MB060.eurprd04.prod.outlook.com>
X-Exchange-Antispam-Report-Test: UriScan:;
X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(601004)(5005006)(5002009); SRVR:DB3PR04MB060; BCL:0; PCL:0; RULEID:; SRVR:DB3PR04MB060; 
X-Forefront-PRVS: 05087F0C24
X-OriginatorOrg: philips.com
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 07 Mar 2015 10:37:48.8438 (UTC)
X-MS-Exchange-CrossTenant-Id: 1a407a2d-7675-4d17-8692-b3ac285306e4
X-MS-Exchange-CrossTenant-OriginalAttributedTenantConnectingIp: TenantId=1a407a2d-7675-4d17-8692-b3ac285306e4; Ip=[206.191.240.52];  Helo=[mail.philips.com]
X-MS-Exchange-CrossTenant-FromEntityHeader: HybridOnPrem
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DB3PR04MB060
Archived-At: <http://mailarchive.ietf.org/arch/msg/dtls-iot/lTO99FZwdsHQ1ljm50G73R4RGvA>
Cc: "dtls-iot@ietf.org" <dtls-iot@ietf.org>
Subject: Re: [Dtls-iot] 2nd WGLC on draft-ietf-dice-profile, ending Feb 6th
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: Sat, 07 Mar 2015 10:38:13 -0000

--_000_BE6D13F6A4554947952B39008B0DC0153ED0089ADBXPRD9003MB059_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

SGkgSGFubmVzDQoNClRoZXJlIGFyZSBzaXR1YXRpb25zIHdoZXJlIHRoZSBQU0sgSWRlbnRpdHkg
aGludCBpcyBzdGlsbCB1c2VmdWwuDQpJbiBjZXJ0YWluIHBlcnNvbmFsaXphdGlvbiBjb250ZXh0
cyAobGlrZSBpbiBTSU0gY2FyZHMgb3IgSFNNcykgYSBsYXJnZSBibG9jayBvZiBkYXRhIGlzIHNl
Y3VyZWx5IHByb3Zpc2lvbmVkIHRvIHRoZSBkZXZpY2UgYXQgb25jZSBmcm9tIHdoaWNoIGRpZmZl
cmVudCBwb3J0aW9ucyBvZiB0aGlzIGRhdGEgYmxvY2sgYXJlIHVzZWQgYXMga2V5cyBkdXJpbmcg
ZGlmZmVyZW50IGxpZmVjeWNsZSBzdGFnZXMuIFRoZSBQU0sgaWRlbnRpdHkgaGludCBjb3VsZCBi
ZSB1c2VkIGFzIGFuIG9mZnNldCB0byBpbmRpY2F0ZSB3aGljaCBwYXJ0IG9mIHRoZSBrZXktYmxv
Y2sgaXMgaW4gdXNlIGZvciBhIHBhcnRpY3VsYXIgRFRMUyBoYW5kc2hha2UuDQoNClRoZSBvdGhl
ciBjYXNlIGlzIHJlbGF0ZWQgdG8gdXNlIG9mIERUTFMgd2l0aCBwb2x5bm9taWFsIGJhc2VkIGlk
ZW50aXR5IGJhc2VkIGNyeXB0b3N5c3RlbXMgWzFdIFsyXSB3aGVyZSB0aGUgUFNLIElkZW50aXR5
IGhpbnQgY2FuIGJlIHVzZWQgdG8gZGVyaXZlIHRoZSBtdXR1YWwgUFNLIGtleSB0aGF0IHNob3Vs
ZCBiZSB1c2VkIGJldHdlZW4gdGhlIGNsaWVudCBhbmQgc2VydmVyLg0KDQpTaW5jZSBQU0sgaWRl
bnRpdHkgaGludCBpcyBhbHJlYWR5IG9wdGlvbmFsIGluIHRoZSBmaXJzdCBjYXNlLCBrZWVwaW5n
IGl0IGluIHRoZSBwcm9maWxlIHRoYXQgd2F5IHdvdWxkIG5vdCBsZWFkIHRvIGFkZGl0aW9uYWwg
b3ZlcmhlYWQgYW5kIGNhbiBiZSBzdGlsbCB1c2VkIGZvciBkZXBsb3ltZW50cyB0aGF0IG1heSBm
aW5kIGl0IHVzZWZ1bC4NCg0KDQpyZWdhcmRzDQpTYW5kZWVwDQoNClsxXUJsdW5kbywgQy4sIERl
IFNhbnRpcywgQS4sIEhlcnpiZXJnLCBBLiwgS3V0dGVuLCBTLiwgVmFjY2FybywgVS4sIGFuZCBZ
dW5nLCBNLiAiUGVyZmVjdGx5LVNlY3VyZSBLZXkgRGlzdHJpYnV0aW9uIGZvciBEeW5hbWljIENv
bmZlcmVuY2VzIiwgQWR2YW5jZXMgaW4gQ3J5cHRvbG9neSAoQ1JZUFRPJzkyKSwgMTk5My4NClsy
XU9zY2FyIEdhcmNpYS1Nb3JjaG9uIGFuZCBSb25hbGQgUmlldG1hbiBhbmQgU2FoaWwgU2hhcm1h
IGFuZCBMdWRvIFRvbGh1aXplbiBhbmQgSm9zZSBMdWlzIFRvcnJlLUFyY2UsIERUTFMtSElNTU86
IEVmZmljaWVudGx5IFNlY3VyaW5nIGEgUG9zdC1RdWFudHVtIFdvcmxkIHdpdGggYSBGdWxseS1D
b2xsdXNpb24gUmVzaXN0YW50IEtQUyBodHRwczovL2VwcmludC5pYWNyLm9yZy8yMDE0LzEwMDgN
Cg0KU2VudCBmcm9tIFdpbmRvd3MgTWFpbA0KDQpGcm9tOiBIYW5uZXMgVHNjaG9mZW5pZzxtYWls
dG86aGFubmVzLnRzY2hvZmVuaWdAZ214Lm5ldD4NClNlbnQ6IOKAjlRodXJzZGF54oCOLCDigI5N
YXJjaOKAjiDigI414oCOLCDigI4yMDE1IOKAjjnigI464oCOMDTigI4g4oCOUE0NClRvOiBPbGFm
IEJlcmdtYW5uPG1haWx0bzpiZXJnbWFubkB0emkub3JnPg0KQ2M6IGR0bHMtaW90QGlldGYub3Jn
PG1haWx0bzpkdGxzLWlvdEBpZXRmLm9yZz4NCg0KWW91IGNvdWxkIHVzZSBpdCBhcyBhIHJlYWxt
LWluZGljYXRvciBhcyB3ZWxsIGJ1dCBpbiB0aGUgbWVhbndoaWxlIHRoZQ0KU05JIHN0dWZmIGhh
ZCBiZWVuIGRlZmluZWQgdGhhdCBhbGxvd3MgdGhlIGNsaWVudCB0byBpbmRpY2F0ZSB3aGF0DQpz
ZXJ2ZXIgaXQgd2FudHMgdG8gY2hvb3NlIChpbiBhIGhvc3Rpbmcgc29sdXRpb24pLiBXaGlsZSB0
aGlzIGlzIG5vdA0KZXhhY3RseSB0aGUgc2FtZSBJIGFtIG5vdCBzdXJlIGFueW9uZSBoYXMgdXNl
ZCB0aGUgUFNLIGlkZW50aXR5IGhpbnQgaW4NCmEgcmVhbG0tc2VsZWN0aW9uIHNjZW5hcmlvLg0K
DQpJdCB3b3VsZCBiZSBnb29kIHRvIGtub3cgd2hldGhlciBhbnlvbmUgaGFzIHNlZW4gYSBuZWVk
IGZvciBpdCBpbiB0aGUNCklvVCBjb250ZXh0LiBJZiBzbywgd2UgY291bGQgY2hhbmdlIHRoZSB0
ZXh0IGFuZCBhZGQgc29tZSBtb3RpdmF0aW9uIGZvcg0Kd2hlcmUgdG8gdXNlIGl0Lg0KDQpDaWFv
DQpIYW5uZXMNCg0KDQpPbiAwMy8wNS8yMDE1IDA4OjU1IFBNLCBPbGFmIEJlcmdtYW5uIHdyb3Rl
Og0KPiBIYW5uZXMgVHNjaG9mZW5pZyA8aGFubmVzLnRzY2hvZmVuaWdAZ214Lm5ldD4gd3JpdGVz
Og0KPg0KPj4gSGkgT2xhZiwNCj4+DQo+PiB0aGUgb3JpZ2luYWwgcmVhc29uIHdoeSBQYXNpIGFu
ZCBJIGFkZGVkIHRoZSAiUFNLIGlkZW50aXR5IGhpbnQiIHRvIHRoZQ0KPj4gVExTLVBTSyBzcGVj
aWZpY2F0aW9uIHdhcyB0aGUgZGVzaXJlIHRvIGludGVyd29yayB3aXRoIHRoZSAzR1BQIEdlbmVy
aWMNCj4+IEJvb3RzdHJhcHBpbmcgQXJjaGl0ZWN0dXJlLiBUaGUgR0JBIHdhcyB0aGUga2V5IG1h
bmFnZW1lbnQgcHJvdG9jb2wgdXNlZA0KPj4gdG8gZGlzdHJpYnV0ZSB0aGUgUFNLIHRvIHRoZSBz
ZXJ2ZXItc2lkZS4NCj4NCj4gT2gsIEkgc2VlLiBVbnRpbCBub3csIG15IHJlYWRpbmcgd2FzIHRo
YXQgdGhpcyBpcyB1c2VkIGFzIGEgc29ydCBvZg0KPiByZWFsbSBpbmRpY2F0b3IuIElmIHlvdXIg
YXNzZXNzbWVudCBpcyBjb3JyZWN0IHRoYXQgbm9ib2R5IHVzZXMgaXQsDQo+IEkgd291bGQgYmUg
aW4gZmF2b3Igb2YgdGhlICJjbGllbnQgTVVTVCBpZ25vcmUiIHZlcnNpb24uDQo+DQo+IEdyw7zD
n2UNCj4gT2xhZg0KPg0KDQoNCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQpUaGUg
aW5mb3JtYXRpb24gY29udGFpbmVkIGluIHRoaXMgbWVzc2FnZSBtYXkgYmUgY29uZmlkZW50aWFs
IGFuZCBsZWdhbGx5IHByb3RlY3RlZCB1bmRlciBhcHBsaWNhYmxlIGxhdy4gVGhlIG1lc3NhZ2Ug
aXMgaW50ZW5kZWQgc29sZWx5IGZvciB0aGUgYWRkcmVzc2VlKHMpLiBJZiB5b3UgYXJlIG5vdCB0
aGUgaW50ZW5kZWQgcmVjaXBpZW50LCB5b3UgYXJlIGhlcmVieSBub3RpZmllZCB0aGF0IGFueSB1
c2UsIGZvcndhcmRpbmcsIGRpc3NlbWluYXRpb24sIG9yIHJlcHJvZHVjdGlvbiBvZiB0aGlzIG1l
c3NhZ2UgaXMgc3RyaWN0bHkgcHJvaGliaXRlZCBhbmQgbWF5IGJlIHVubGF3ZnVsLiBJZiB5b3Ug
YXJlIG5vdCB0aGUgaW50ZW5kZWQgcmVjaXBpZW50LCBwbGVhc2UgY29udGFjdCB0aGUgc2VuZGVy
IGJ5IHJldHVybiBlLW1haWwgYW5kIGRlc3Ryb3kgYWxsIGNvcGllcyBvZiB0aGUgb3JpZ2luYWwg
bWVzc2FnZS4NCg==

--_000_BE6D13F6A4554947952B39008B0DC0153ED0089ADBXPRD9003MB059_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PGh0bWw+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIgY29udGVudD0i
dGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9ImdlbmVyYXRvciIgY29udGVu
dD0iV2luZG93cyBNYWlsIDE3LjUuOTYwMC4yMDY4OSI+DQo8c3R5bGUgdHlwZT0idGV4dC9jc3Mi
PjwhLS1odG1sIHsgZm9udC1mYW1pbHk6ICJDb2xvciBFbW9qaSIsICJDYWxpYnJpIiwgIlNlZ29l
IFVJIiwgIk1laXJ5byIsICJNaWNyb3NvZnQgWWFIZWkgVUkiLCAiTWljcm9zb2Z0IEpoZW5nSGVp
IFVJIiwgIk1hbGd1biBHb3RoaWMiLCAic2Fucy1zZXJpZiI7IH0tLT48L3N0eWxlPjxzdHlsZSBk
YXRhLWV4dGVybmFsc3R5bGU9InRydWUiPjwhLS0KcC5Nc29MaXN0UGFyYWdyYXBoLCBsaS5Nc29M
aXN0UGFyYWdyYXBoLCBkaXYuTXNvTGlzdFBhcmFncmFwaCB7Cm1hcmdpbi10b3A6MGluOwptYXJn
aW4tcmlnaHQ6MGluOwptYXJnaW4tYm90dG9tOjBpbjsKbWFyZ2luLWxlZnQ6LjVpbjsKbWFyZ2lu
LWJvdHRvbTouMDAwMXB0Owp9CnAuTXNvTm9ybWFsLCBsaS5Nc29Ob3JtYWwsIGRpdi5Nc29Ob3Jt
YWwgewptYXJnaW46MGluOwptYXJnaW4tYm90dG9tOi4wMDAxcHQ7Cn0KcC5Nc29MaXN0UGFyYWdy
YXBoQ3hTcEZpcnN0LCBsaS5Nc29MaXN0UGFyYWdyYXBoQ3hTcEZpcnN0LCBkaXYuTXNvTGlzdFBh
cmFncmFwaEN4U3BGaXJzdCwgCnAuTXNvTGlzdFBhcmFncmFwaEN4U3BNaWRkbGUsIGxpLk1zb0xp
c3RQYXJhZ3JhcGhDeFNwTWlkZGxlLCBkaXYuTXNvTGlzdFBhcmFncmFwaEN4U3BNaWRkbGUsIApw
Lk1zb0xpc3RQYXJhZ3JhcGhDeFNwTGFzdCwgbGkuTXNvTGlzdFBhcmFncmFwaEN4U3BMYXN0LCBk
aXYuTXNvTGlzdFBhcmFncmFwaEN4U3BMYXN0IHsKbWFyZ2luLXRvcDowaW47Cm1hcmdpbi1yaWdo
dDowaW47Cm1hcmdpbi1ib3R0b206MGluOwptYXJnaW4tbGVmdDouNWluOwptYXJnaW4tYm90dG9t
Oi4wMDAxcHQ7CmxpbmUtaGVpZ2h0OjExNSU7Cn0KLS0+PC9zdHlsZT4NCjwvaGVhZD4NCjxib2R5
IGRpcj0ibHRyIj4NCjxkaXYgZGF0YS1leHRlcm5hbHN0eWxlPSJmYWxzZSIgZGlyPSJsdHIiIHN0
eWxlPSJmb250LWZhbWlseTogJ0NhbGlicmknLCAnU2Vnb2UgVUknLCAnTWVpcnlvJywgJ01pY3Jv
c29mdCBZYUhlaSBVSScsICdNaWNyb3NvZnQgSmhlbmdIZWkgVUknLCAnTWFsZ3VuIEdvdGhpYycs
ICdzYW5zLXNlcmlmJztmb250LXNpemU6MTJwdDsiPg0KPGRpdj5IaSBIYW5uZXM8L2Rpdj4NCjxk
aXY+PGJyPg0KPC9kaXY+DQo8ZGl2PlRoZXJlIGFyZSBzaXR1YXRpb25zIHdoZXJlIHRoZSBQU0sg
SWRlbnRpdHkgaGludCBpcyBzdGlsbCB1c2VmdWwuIDwvZGl2Pg0KPGRpdj5JbiBjZXJ0YWluIHBl
cnNvbmFsaXphdGlvbiBjb250ZXh0cyAobGlrZSBpbiBTSU0gY2FyZHMgb3IgSFNNcykgYSBsYXJn
ZSBibG9jayBvZiBkYXRhIGlzIHNlY3VyZWx5IHByb3Zpc2lvbmVkIHRvIHRoZSBkZXZpY2UgYXQg
b25jZSBmcm9tIHdoaWNoIGRpZmZlcmVudCBwb3J0aW9ucyBvZiB0aGlzIGRhdGEgYmxvY2sgYXJl
IHVzZWQgYXMga2V5cyBkdXJpbmcgZGlmZmVyZW50IGxpZmVjeWNsZSBzdGFnZXMuIFRoZSBQU0sg
aWRlbnRpdHkgaGludA0KIGNvdWxkIGJlIHVzZWQgYXMgYW4gb2Zmc2V0IHRvIGluZGljYXRlIHdo
aWNoIHBhcnQgb2YgdGhlIGtleS1ibG9jayZuYnNwO2lzIGluJm5ic3A7dXNlJm5ic3A7Zm9yJm5i
c3A7YSBwYXJ0aWN1bGFyIERUTFMmbmJzcDtoYW5kc2hha2UuPC9kaXY+DQo8ZGl2Pjxicj4NCjwv
ZGl2Pg0KPGRpdj5UaGUgb3RoZXIgY2FzZSBpcyByZWxhdGVkIHRvIHVzZSBvZiBEVExTIHdpdGgg
cG9seW5vbWlhbCBiYXNlZCBpZGVudGl0eSBiYXNlZCBjcnlwdG9zeXN0ZW1zIFsxXSZuYnNwO1sy
XSB3aGVyZSB0aGUgUFNLIElkZW50aXR5IGhpbnQgY2FuIGJlIHVzZWQgdG8mbmJzcDtkZXJpdmUg
dGhlIG11dHVhbCBQU0sga2V5Jm5ic3A7dGhhdCBzaG91bGQgYmUgdXNlZCBiZXR3ZWVuIHRoZSBj
bGllbnQgYW5kIHNlcnZlci48L2Rpdj4NCjxkaXY+PGJyPg0KPC9kaXY+DQo8ZGl2PlNpbmNlJm5i
c3A7UFNLIGlkZW50aXR5IGhpbnQmbmJzcDtpcyBhbHJlYWR5IG9wdGlvbmFsIGluIHRoZSBmaXJz
dCBjYXNlLCBrZWVwaW5nIGl0IGluIHRoZSBwcm9maWxlIHRoYXQgd2F5IHdvdWxkIG5vdCBsZWFk
IHRvIGFkZGl0aW9uYWwgb3ZlcmhlYWQmbmJzcDthbmQgY2FuIGJlIHN0aWxsIHVzZWQgZm9yIGRl
cGxveW1lbnRzIHRoYXQgbWF5IGZpbmQgaXQgdXNlZnVsLjwvZGl2Pg0KPGRpdj48YnI+DQo8L2Rp
dj4NCjxkaXY+PGJyPg0KPC9kaXY+DQo8ZGl2PnJlZ2FyZHM8L2Rpdj4NCjxkaXY+U2FuZGVlcDwv
ZGl2Pg0KPGRpdj48YnI+DQo8L2Rpdj4NCjxkaXY+WzFdPGZvbnQgZmFjZT0iQ2FsaWJyaSI+Qmx1
bmRvLCBDLiwgRGUgU2FudGlzLCBBLiwgSGVyemJlcmcsIEEuLCBLdXR0ZW4sIFMuLCBWYWNjYXJv
LCBVLiwgYW5kIFl1bmcsIE0uICZxdW90O1BlcmZlY3RseS1TZWN1cmUgS2V5IERpc3RyaWJ1dGlv
biBmb3IgRHluYW1pYyBDb25mZXJlbmNlcyZxdW90OywgQWR2YW5jZXMgaW4gQ3J5cHRvbG9neSAo
Q1JZUFRPJzkyKSwgMTk5My48L2ZvbnQ+PC9kaXY+DQo8ZGl2Pls8Zm9udCBmYWNlPSJDYWxpYnJp
Ij4yXTwvZm9udD48Zm9udCBmYWNlPSJDYWxpYnJpIj5Pc2NhciBHYXJjaWEtTW9yY2hvbiBhbmQg
Um9uYWxkIFJpZXRtYW4gYW5kIFNhaGlsIFNoYXJtYSBhbmQgTHVkbyBUb2xodWl6ZW4gYW5kIEpv
c2UgTHVpcyBUb3JyZS1BcmNlLA0KPC9mb250Pjxmb250IGZhY2U9IkNhbGlicmkiPkRUTFMtSElN
TU86IEVmZmljaWVudGx5IFNlY3VyaW5nIGEgUG9zdC1RdWFudHVtIFdvcmxkIHdpdGggYSBGdWxs
eS1Db2xsdXNpb24gUmVzaXN0YW50IEtQUw0KPC9mb250PjxhIGhyZWY9Imh0dHBzOi8vZXByaW50
LmlhY3Iub3JnLzIwMTQvMTAwOCIgdGFyZ2V0PSJfcGFyZW50Ij48Zm9udCBmYWNlPSJDYWxpYnJp
Ij5odHRwczovL2VwcmludC5pYWNyLm9yZy8yMDE0LzEwMDg8L2ZvbnQ+PC9hPjxmb250IGZhY2U9
IkNhbGlicmkiPiZuYnNwOzwvZm9udD48YnI+DQo8L2Rpdj4NCjxkaXYgZGF0YS1zaWduYXR1cmVi
bG9jaz0idHJ1ZSI+DQo8ZGl2Pjxicj4NCjwvZGl2Pg0KPGRpdj5TZW50IGZyb20gV2luZG93cyBN
YWlsPC9kaXY+DQo8ZGl2Pjxicj4NCjwvZGl2Pg0KPC9kaXY+DQo8ZGl2IHN0eWxlPSJwYWRkaW5n
LXRvcDogNXB4OyBib3JkZXItdG9wLWNvbG9yOiByZ2IoMjI5LCAyMjksIDIyOSk7IGJvcmRlci10
b3Atd2lkdGg6IDFweDsgYm9yZGVyLXRvcC1zdHlsZTogc29saWQ7Ij4NCjxkaXY+PGZvbnQgZmFj
ZT0iICdDYWxpYnJpJywgJ1NlZ29lIFVJJywgJ01laXJ5bycsICdNaWNyb3NvZnQgWWFIZWkgVUkn
LCAnTWljcm9zb2Z0IEpoZW5nSGVpIFVJJywgJ01hbGd1biBHb3RoaWMnLCAnc2Fucy1zZXJpZici
IHN0eWxlPSJsaW5lLWhlaWdodDogMTVwdDsgbGV0dGVyLXNwYWNpbmc6IDAuMDJlbTsgZm9udC1m
YW1pbHk6ICZxdW90O0NhbGlicmkmcXVvdDssICZxdW90O1NlZ29lIFVJJnF1b3Q7LCAmcXVvdDtN
ZWlyeW8mcXVvdDssICZxdW90O01pY3Jvc29mdCBZYUhlaSBVSSZxdW90OywgJnF1b3Q7TWljcm9z
b2Z0IEpoZW5nSGVpIFVJJnF1b3Q7LCAmcXVvdDtNYWxndW4gR290aGljJnF1b3Q7LCAmcXVvdDtz
YW5zLXNlcmlmJnF1b3Q7OyBmb250LXNpemU6IDEycHQ7Ij48Yj5Gcm9tOjwvYj4mbmJzcDs8YSBo
cmVmPSJtYWlsdG86aGFubmVzLnRzY2hvZmVuaWdAZ214Lm5ldCIgdGFyZ2V0PSJfcGFyZW50Ij5I
YW5uZXMNCiBUc2Nob2ZlbmlnPC9hPjxicj4NCjxiPlNlbnQ6PC9iPiZuYnNwO+KAjlRodXJzZGF5
4oCOLCDigI5NYXJjaOKAjiDigI414oCOLCDigI4yMDE1IOKAjjnigI464oCOMDTigI4g4oCOUE08
YnI+DQo8Yj5Ubzo8L2I+Jm5ic3A7PGEgaHJlZj0ibWFpbHRvOmJlcmdtYW5uQHR6aS5vcmciIHRh
cmdldD0iX3BhcmVudCI+T2xhZiBCZXJnbWFubjwvYT48YnI+DQo8Yj5DYzo8L2I+Jm5ic3A7PGEg
aHJlZj0ibWFpbHRvOmR0bHMtaW90QGlldGYub3JnIiB0YXJnZXQ9Il9wYXJlbnQiPmR0bHMtaW90
QGlldGYub3JnPC9hPjwvZm9udD48L2Rpdj4NCjwvZGl2Pg0KPGRpdj48YnI+DQo8L2Rpdj4NCjxk
aXYgZGlyPSIiPg0KPGRpdiBpZD0icmVhZGluZ1BhbmVCb2R5Q29udGVudCI+WW91IGNvdWxkIHVz
ZSBpdCBhcyBhIHJlYWxtLWluZGljYXRvciBhcyB3ZWxsIGJ1dCBpbiB0aGUgbWVhbndoaWxlIHRo
ZTxicj4NClNOSSBzdHVmZiBoYWQgYmVlbiBkZWZpbmVkIHRoYXQgYWxsb3dzIHRoZSBjbGllbnQg
dG8gaW5kaWNhdGUgd2hhdDxicj4NCnNlcnZlciBpdCB3YW50cyB0byBjaG9vc2UgKGluIGEgaG9z
dGluZyBzb2x1dGlvbikuIFdoaWxlIHRoaXMgaXMgbm90PGJyPg0KZXhhY3RseSB0aGUgc2FtZSBJ
IGFtIG5vdCBzdXJlIGFueW9uZSBoYXMgdXNlZCB0aGUgUFNLIGlkZW50aXR5IGhpbnQgaW48YnI+
DQphIHJlYWxtLXNlbGVjdGlvbiBzY2VuYXJpby48YnI+DQo8YnI+DQpJdCB3b3VsZCBiZSBnb29k
IHRvIGtub3cgd2hldGhlciBhbnlvbmUgaGFzIHNlZW4gYSBuZWVkIGZvciBpdCBpbiB0aGU8YnI+
DQpJb1QgY29udGV4dC4gSWYgc28sIHdlIGNvdWxkIGNoYW5nZSB0aGUgdGV4dCBhbmQgYWRkIHNv
bWUgbW90aXZhdGlvbiBmb3I8YnI+DQp3aGVyZSB0byB1c2UgaXQuPGJyPg0KPGJyPg0KQ2lhbzxi
cj4NCkhhbm5lczxicj4NCjxicj4NCjxicj4NCk9uIDAzLzA1LzIwMTUgMDg6NTUgUE0sIE9sYWYg
QmVyZ21hbm4gd3JvdGU6PGJyPg0KJmd0OyBIYW5uZXMgVHNjaG9mZW5pZyAmbHQ7aGFubmVzLnRz
Y2hvZmVuaWdAZ214Lm5ldCZndDsgd3JpdGVzOjxicj4NCiZndDsgPGJyPg0KJmd0OyZndDsgSGkg
T2xhZiw8YnI+DQomZ3Q7Jmd0Ozxicj4NCiZndDsmZ3Q7IHRoZSBvcmlnaW5hbCByZWFzb24gd2h5
IFBhc2kgYW5kIEkgYWRkZWQgdGhlICZxdW90O1BTSyBpZGVudGl0eSBoaW50JnF1b3Q7IHRvIHRo
ZTxicj4NCiZndDsmZ3Q7IFRMUy1QU0sgc3BlY2lmaWNhdGlvbiB3YXMgdGhlIGRlc2lyZSB0byBp
bnRlcndvcmsgd2l0aCB0aGUgM0dQUCBHZW5lcmljPGJyPg0KJmd0OyZndDsgQm9vdHN0cmFwcGlu
ZyBBcmNoaXRlY3R1cmUuIFRoZSBHQkEgd2FzIHRoZSBrZXkgbWFuYWdlbWVudCBwcm90b2NvbCB1
c2VkPGJyPg0KJmd0OyZndDsgdG8gZGlzdHJpYnV0ZSB0aGUgUFNLIHRvIHRoZSBzZXJ2ZXItc2lk
ZS48YnI+DQomZ3Q7IDxicj4NCiZndDsgT2gsIEkgc2VlLiBVbnRpbCBub3csIG15IHJlYWRpbmcg
d2FzIHRoYXQgdGhpcyBpcyB1c2VkIGFzIGEgc29ydCBvZjxicj4NCiZndDsgcmVhbG0gaW5kaWNh
dG9yLiBJZiB5b3VyIGFzc2Vzc21lbnQgaXMgY29ycmVjdCB0aGF0IG5vYm9keSB1c2VzIGl0LDxi
cj4NCiZndDsgSSB3b3VsZCBiZSBpbiBmYXZvciBvZiB0aGUgJnF1b3Q7Y2xpZW50IE1VU1QgaWdu
b3JlJnF1b3Q7IHZlcnNpb24uPGJyPg0KJmd0OyA8YnI+DQomZ3Q7IEdyw7zDn2U8YnI+DQomZ3Q7
IE9sYWY8YnI+DQomZ3Q7IDxicj4NCjxicj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjxicj4N
Cjxocj4NCjxmb250IGZhY2U9IkFyaWFsIiBjb2xvcj0iR3JheSIgc2l6ZT0iMSI+VGhlIGluZm9y
bWF0aW9uIGNvbnRhaW5lZCBpbiB0aGlzIG1lc3NhZ2UgbWF5IGJlIGNvbmZpZGVudGlhbCBhbmQg
bGVnYWxseSBwcm90ZWN0ZWQgdW5kZXIgYXBwbGljYWJsZSBsYXcuIFRoZSBtZXNzYWdlIGlzIGlu
dGVuZGVkIHNvbGVseSBmb3IgdGhlIGFkZHJlc3NlZShzKS4gSWYgeW91IGFyZSBub3QgdGhlIGlu
dGVuZGVkIHJlY2lwaWVudCwgeW91IGFyZSBoZXJlYnkgbm90aWZpZWQNCiB0aGF0IGFueSB1c2Us
IGZvcndhcmRpbmcsIGRpc3NlbWluYXRpb24sIG9yIHJlcHJvZHVjdGlvbiBvZiB0aGlzIG1lc3Nh
Z2UgaXMgc3RyaWN0bHkgcHJvaGliaXRlZCBhbmQgbWF5IGJlIHVubGF3ZnVsLiBJZiB5b3UgYXJl
IG5vdCB0aGUgaW50ZW5kZWQgcmVjaXBpZW50LCBwbGVhc2UgY29udGFjdCB0aGUgc2VuZGVyIGJ5
IHJldHVybiBlLW1haWwgYW5kIGRlc3Ryb3kgYWxsIGNvcGllcyBvZiB0aGUgb3JpZ2luYWwgbWVz
c2FnZS48YnI+DQo8L2ZvbnQ+DQo8L2JvZHk+DQo8L2h0bWw+DQo=

--_000_BE6D13F6A4554947952B39008B0DC0153ED0089ADBXPRD9003MB059_--


From nobody Sat Mar  7 03:58:46 2015
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 534371A896E for <dtls-iot@ietfa.amsl.com>; Sat,  7 Mar 2015 03:58:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 s5bG3o4m8K2y for <dtls-iot@ietfa.amsl.com>; Sat,  7 Mar 2015 03:58:43 -0800 (PST)
Received: from mout.gmx.net (mout.gmx.net [212.227.15.15]) (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 B862D1A8A72 for <dtls-iot@ietf.org>; Sat,  7 Mar 2015 03:58:42 -0800 (PST)
Received: from [192.168.131.144] ([80.92.121.102]) by mail.gmx.com (mrgmx003) with ESMTPSA (Nemesis) id 0Lk7fW-1Xs8Sz1NsY-00c6l9; Sat, 07 Mar 2015 12:58:39 +0100
Message-ID: <54FAE7EE.9000905@gmx.net>
Date: Sat, 07 Mar 2015 12:58:38 +0100
From: Hannes Tschofenig <hannes.tschofenig@gmx.net>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: "Kumar, Sandeep" <sandeep.kumar@philips.com>,  Olaf Bergmann <bergmann@tzi.org>
References: <258751E5-69DB-4787-A7EE-B6C955225AA4@arm.com>	<87y4oamwtj.fsf@tzi.org> <54F873CA.4090902@gmx.net>	<877fuvgydx.fsf@tzi.org> <54F8A275.2040602@gmx.net> <87twxzfcdl.fsf@tzi.org>, <54F8B6B6.50103@gmx.net> <BE6D13F6A4554947952B39008B0DC0153ED0089A@DBXPRD9003MB059.MGDPHG.emi.philips.com>
In-Reply-To: <BE6D13F6A4554947952B39008B0DC0153ED0089A@DBXPRD9003MB059.MGDPHG.emi.philips.com>
OpenPGP: id=4D776BC9
Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="nFPOCedgDGJOaAfONHxidHdnTtq60OxXT"
X-Provags-ID: V03:K0:uyjOmu7d0THk7VBjRiBnOQ7fd/ooBUznQSGUvQBBH0kW3UiVaHV z8xv7mmjwrB4GEp5X90Z21Aw9//yTd95xf9N3k3/aveURMUKQ0bkkbC3lRR+Wf0jD8vy3Nt pnZhqfJtdp2hNjfVeymN9LhiWpqDGofaziqj6fsCMWUqeIJsvfBrEI8BBYGCcC3xXS30VEU NCkydkBschX7hvgG1/jVw==
X-UI-Out-Filterresults: notjunk:1;
Archived-At: <http://mailarchive.ietf.org/arch/msg/dtls-iot/bVfuCFmv6FYwf3oc9UtLf73crNI>
Cc: "dtls-iot@ietf.org" <dtls-iot@ietf.org>
Subject: Re: [Dtls-iot] 2nd WGLC on draft-ietf-dice-profile, ending Feb 6th
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: Sat, 07 Mar 2015 11:58:45 -0000

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

Hi Sandeep,

here is a detailed description of how TLS-PSK was used with the GBA:
http://www.3gpp.org/ftp/tsg_sa/wg3_security/tsgs3_33_beijing/docs/pdf/s3-=
040337.pdf

As you can see the psk identity hint is needed since the PSK is selected
based on the BSF but the TLS client contacts the NAF.

This is IMHO a technical reason but, as mentioned earlier in the
discussion with Olaf, I believe GBA is dead and maybe I am wrong.

In the examples you mention below there is no enough detail to see
whether the psk identity hint is really needed.

I am a bit reluctant to just add functionality based on vague ideas
since this is the source of complexity in the IoT environment. There are
many places in the document where we could have added various other
features. In fact, I would encourage everyone to go through the document
to find out whether there is functionality we could avoid to reduce
complexity even further.

I have a fairly strong opinion about identity-based encryption. As I had
stated in other discussions (see, for example,
https://www.ietf.org/mail-archive/web/emu/current/msg01830.html), I
believe that identity-based encryption is a solution in search of a
problem.
It does not solve any of the problems we have in the IoT security space.

In general, I believe we are well advised to take a look at the Smart
Object workshop position paper from Carsten again since it relates to
this discussion:
https://www.iab.org/wp-content/IAB-uploads/2011/04/Bormann.pdf

But despite my resistance I am really just looking for someone who is
deploying the identity hints with PSK and could provides more details on
how they use it. In fact, with the recent review from Rene I have
removed the text about the identity hint from the profile document since
it was indeed inconsistent in the recommendation it provided. Better to
say nothing about it.

Ciao
Hannes


On 03/07/2015 11:37 AM, Kumar, Sandeep wrote:
> Hi Hannes
>=20
> There are situations where the PSK Identity hint is still useful.
> In certain personalization contexts (like in SIM cards or HSMs) a large=

> block of data is securely provisioned to the device at once from which
> different portions of this data block are used as keys during different=

> lifecycle stages. The PSK identity hint could be used as an offset to
> indicate which part of the key-block is in use for a particular
> DTLS handshake.
>=20
> The other case is related to use of DTLS with polynomial based identity=

> based cryptosystems [1] [2] where the PSK Identity hint can be used
> to derive the mutual PSK key that should be used between the client and=

> server.
>=20
> Since PSK identity hint is already optional in the first case, keeping
> it in the profile that way would not lead to additional overhead and ca=
n
> be still used for deployments that may find it useful.
>=20
>=20
> regards
> Sandeep
>=20
> [1]Blundo, C., De Santis, A., Herzberg, A., Kutten, S., Vaccaro, U., an=
d
> Yung, M. "Perfectly-Secure Key Distribution for Dynamic Conferences",
> Advances in Cryptology (CRYPTO'92), 1993.
> [2]Oscar Garcia-Morchon and Ronald Rietman and Sahil Sharma and Ludo
> Tolhuizen and Jose Luis Torre-Arce, DTLS-HIMMO: Efficiently Securing a
> Post-Quantum World with a Fully-Collusion Resistant KPS
> https://eprint.iacr.org/2014/1008=20
>=20
> Sent from Windows Mail
>=20
> *From:* Hannes Tschofenig <mailto:hannes.tschofenig@gmx.net>
> *Sent:* =E2=80=8EThursday=E2=80=8E, =E2=80=8EMarch=E2=80=8E =E2=80=8E5=E2=
=80=8E, =E2=80=8E2015 =E2=80=8E9=E2=80=8E:=E2=80=8E04=E2=80=8E =E2=80=8EP=
M
> *To:* Olaf Bergmann <mailto:bergmann@tzi.org>
> *Cc:* dtls-iot@ietf.org <mailto:dtls-iot@ietf.org>
>=20
> You could use it as a realm-indicator as well but in the meanwhile the
> SNI stuff had been defined that allows the client to indicate what
> server it wants to choose (in a hosting solution). While this is not
> exactly the same I am not sure anyone has used the PSK identity hint in=

> a realm-selection scenario.
>=20
> It would be good to know whether anyone has seen a need for it in the
> IoT context. If so, we could change the text and add some motivation fo=
r
> where to use it.
>=20
> Ciao
> Hannes
>=20
>=20
> On 03/05/2015 08:55 PM, Olaf Bergmann wrote:
>> Hannes Tschofenig <hannes.tschofenig@gmx.net> writes:
>>
>>> Hi Olaf,
>>>
>>> the original reason why Pasi and I added the "PSK identity hint" to t=
he
>>> TLS-PSK specification was the desire to interwork with the 3GPP Gener=
ic
>>> Bootstrapping Architecture. The GBA was the key management protocol u=
sed
>>> to distribute the PSK to the server-side.
>>
>> Oh, I see. Until now, my reading was that this is used as a sort of
>> realm indicator. If your assessment is correct that nobody uses it,
>> I would be in favor of the "client MUST ignore" version.
>>
>> Gr=C3=BC=C3=9Fe
>> Olaf
>>
>=20
>=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 reproductio=
n
> 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.


--nFPOCedgDGJOaAfONHxidHdnTtq60OxXT
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

iQEcBAEBCgAGBQJU+ufuAAoJEGhJURNOOiAtvboH/1N0Xa8ibyf/QD9ahkkI7+L3
SX0OHgpOZ4p88osWoHK7PxsYVQQEuYDOWDiAs3caFzFSFmSMY+VGVeLAfUKwpYV3
eI3d4p/0EzhbZHmPHMCStI/l/sbRTajg4lUg76WZ+bHieNDsd+0tmGr+TBaQX/e6
mNG3ovi8rn0Jm0y7uq003q6vnEM98ems/TLF2P1ez7Y0Xr76cHkjbB7V3CYDD65z
UHTHXA/F14ac+EvS2iMqOtYEyfKKSbXa6PnoaXAwf2YQP0Jp2yKKGmhI8BBVXVBN
cAEFwakCSUV3Lfq0EzSamRHDwe6HGohYD9JZrVq9W/sbff5rSlaHDj5p0Nw6FfQ=
=1dNJ
-----END PGP SIGNATURE-----

--nFPOCedgDGJOaAfONHxidHdnTtq60OxXT--


From nobody Sun Mar  8 16:38:50 2015
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 C33961A0277; Sun,  8 Mar 2015 16:38: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 hWGdafJ-Ilwc; Sun,  8 Mar 2015 16:38:44 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 729051A0204; Sun,  8 Mar 2015 16:38: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.12.0.p3
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150308233844.9061.55010.idtracker@ietfa.amsl.com>
Date: Sun, 08 Mar 2015 16:38:44 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/dtls-iot/3H51CaGfYIV3jewCoEIr7NFoBRQ>
Cc: dtls-iot@ietf.org
Subject: [Dtls-iot] I-D Action: draft-ietf-dice-profile-10.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, 08 Mar 2015 23:38: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 TLS/DTLS Profile for the Internet of Things
        Authors         : Hannes Tschofenig
                          Thomas Fossati
	Filename        : draft-ietf-dice-profile-10.txt
	Pages           : 54
	Date            : 2015-03-08

Abstract:
   A common design pattern in Internet of Things (IoT) deployments is
   the use of a constrained device that collects data via sensor or
   controls actuators for use in home automation, industrial control
   systems, smart cities and other IoT deployments.

   This document defines a Transport Layer Security (TLS) and Datagram
   TLS (DTLS) 1.2 profile that offers communications security for this
   data exchange thereby preventing eavesdropping, tampering, and
   message forgery.  The lack of communication security is a common
   vulnerability in Internet of Things products that can easily be
   solved by using these well-researched and widely deployed Internet
   security protocols.


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-10

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


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 Mar  8 16:42:59 2015
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 0306C1A0276 for <dtls-iot@ietfa.amsl.com>; Sun,  8 Mar 2015 16:42:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.514
X-Spam-Level: *
X-Spam-Status: No, score=1.514 tagged_above=-999 required=5 tests=[BAYES_50=0.8, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, MIME_HTML_ONLY=0.723, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Em1xhyZjfHQs for <dtls-iot@ietfa.amsl.com>; Sun,  8 Mar 2015 16:42:57 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.15.15]) (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 129631A0218 for <dtls-iot@ietf.org>; Sun,  8 Mar 2015 16:42:57 -0700 (PDT)
Received: from [217.140.96.140] by 3capp-gmx-bs34.server.lan (via HTTP); Mon, 9 Mar 2015 00:42:55 +0100
MIME-Version: 1.0
Message-ID: <trinity-078bdef2-9c8d-463d-a67b-08cf76b9987c-1425858175130@3capp-gmx-bs34>
From: "Hannes Tschofenig" <Hannes.Tschofenig@gmx.net>
To: dtls-iot@ietf.org
Content-Type: text/html; charset=UTF-8
Date: Mon, 9 Mar 2015 00:42:55 +0100
Importance: normal
Sensitivity: Normal
X-Priority: 3
X-Provags-ID: V03:K0:Fyswpwwwe49w8uUfAomhtcmo8qwjMDUN9Qm8sqzllgV 1li/Vhm++MNWTI8+HgnVkMIYgTZ0M43LIi/4CVIhzB7VmqatN6 I3xSY/4hYeRHKHbiB/SbYr0hWKPAKAaytJBnU0zuZuXHjXcqbV 3AWWJL35iZ+Wrz7uPOKV9dXEYx6YTLcPV+NFIaqFbpAEI2xxDs pFyKaTwl2HtQw+UusOOLdyowDVnH+zUFyHVv1ENBjZu8IhWAjY xAaLWQY2jOJlHIKzO8LE43VyJ/EEBXXz0vbvHcJzWD3RzVjXn0 3CQr4w=
X-UI-Out-Filterresults: notjunk:1;
Archived-At: <http://mailarchive.ietf.org/arch/msg/dtls-iot/oQrbfAol_0cU-tRsiKoVydyk4BY>
Subject: [Dtls-iot] draft-ietf-dice-profile-10
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, 08 Mar 2015 23:42:58 -0000

<html><head></head><body><div style="font-family: Verdana;font-size: 12.0px;"><div>Version -10 of the profile draft addresses the working group last call review comments.&nbsp;<span style="line-height: 1.6em;">I would still like to hear from the reviewers whether they are fine with the changes I have made in response to their feedback.&nbsp;</span></div>

<div>&nbsp;</div>

<div>Ciao</div>

<div>Hannes</div>

<div>&nbsp;</div></div></body></html>


From nobody Sun Mar  8 16:59:53 2015
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 EF98E1A0231 for <dtls-iot@ietfa.amsl.com>; Sun,  8 Mar 2015 16:59:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.186
X-Spam-Level: 
X-Spam-Status: No, score=-1.186 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, MIME_HTML_ONLY=0.723, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fEsATQlDpsoT for <dtls-iot@ietfa.amsl.com>; Sun,  8 Mar 2015 16:59:50 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.15.19]) (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 373EF1A0222 for <dtls-iot@ietf.org>; Sun,  8 Mar 2015 16:59:50 -0700 (PDT)
Received: from [217.140.96.140] by 3capp-gmx-bs34.server.lan (via HTTP); Mon, 9 Mar 2015 00:59:48 +0100
MIME-Version: 1.0
Message-ID: <trinity-c926df3a-b6f0-4b1a-8105-cc901d7685f8-1425859188321@3capp-gmx-bs34>
From: "Hannes Tschofenig" <Hannes.Tschofenig@gmx.net>
To: dtls-iot@ietf.org
Content-Type: text/html; charset=UTF-8
Date: Mon, 9 Mar 2015 00:59:48 +0100
Importance: normal
Sensitivity: Normal
X-Priority: 3
X-Provags-ID: V03:K0:E2MUKH7UC+1OM2MKbqSdkcj20ArBUOzbJQrEaw8azaW I2epyHxyiZigeupc0ccQMq84pLbWcLSY/CkVtsyNl/xX+885vV lHKtDEO7GkO/YFNxXtR/fcjtEAH/f4lwQKhRt9+hiXlxRFiNS7 D1FVTRBtY7zCFNFlSq1hoHP5TblnL4J0v/0ipf8D+3JMrg7jtP 3iZcV2mhts7XEYp62dbl0mGVqDNWFFF1W69Q0YzioG8uJt9GcL r3MZ7kafp18gs1uDSwnE19OKmY9acHFoqxFCtm7d1kWY6k+dbR hmqwKM=
X-UI-Out-Filterresults: notjunk:1;
Archived-At: <http://mailarchive.ietf.org/arch/msg/dtls-iot/XIYd-Jzakp-KdAWD1ONlZeohwC8>
Subject: [Dtls-iot] draft-ietf-tls-cached-info-18.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, 08 Mar 2015 23:59:52 -0000

<html><head></head><body><div style="font-family: Verdana;font-size: 12.0px;"><div>Hi all,&nbsp;</div>

<div>&nbsp;</div>

<div>I have submitted an updated version of the TLS Cached Info document. The spec defines an extension that allows large (mostly static) information to be omitted, such as the server-provided certificate chain. This obviously saves a lot of bandwidth, which can be seen from example in the appendix.&nbsp;</div>

<div>&nbsp;</div>

<div>End of January I asked for feedback regarding <span style="font-family: Verdana; font-size: 12px; line-height: 19.2000007629395px;">caching of client-provided certificates, see&nbsp;</span><span style="line-height: 1.6em;">http://www.ietf.org/mail-archive/web/dtls-iot/current/msg00550.html, I have not introduced this feature (yet).&nbsp;</span></div>

<div><span style="line-height: 1.6em;">I am planning to raise it to the attention to the TLS working group at the interim meeting.&nbsp;</span></div>

<div>&nbsp;</div>

<div>&nbsp;</div>

<div>Please have a look at the document; I believe it provides great performance improvements for TLS and those should be of interest to folks in this group. Here is the spec:&nbsp;</div>

<div>https://tools.ietf.org/html/draft-ietf-tls-cached-info-18</div>

<div>&nbsp;</div>

<div>Ciao<br/>
Hannes</div></div></body></html>


From nobody Mon Mar  9 01:37:27 2015
Return-Path: <zach.shelby@arm.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 393A21A1EFE for <dtls-iot@ietfa.amsl.com>; Mon,  9 Mar 2015 01:37:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.301
X-Spam-Level: 
X-Spam-Status: No, score=-2.301 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, 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 fzH_YlwLg_ni for <dtls-iot@ietfa.amsl.com>; Mon,  9 Mar 2015 01:37:22 -0700 (PDT)
Received: from service88.mimecast.com (service88.mimecast.com [195.130.217.12]) by ietfa.amsl.com (Postfix) with ESMTP id CA95B1A86E0 for <dtls-iot@ietf.org>; Mon,  9 Mar 2015 01:37:19 -0700 (PDT)
Received: from USA-SJC-GW1.usa.Arm.com (fw-tnat.snv.arm.com [217.140.100.22]) (Using TLS) by service88.mimecast.com; Mon, 09 Mar 2015 08:37:17 +0000
Received: from Spock.usa.Arm.com ([fe80::4116:859a:65b1:2f84]) by USA-SJC-GW1.usa.Arm.com ([::1]) with mapi; Mon, 9 Mar 2015 01:37:15 -0700
From: Zach Shelby <Zach.Shelby@arm.com>
To: Hannes Tschofenig <hannes.tschofenig@gmx.net>
Date: Mon, 9 Mar 2015 01:38:03 -0700
Thread-Topic: [Dtls-iot] draft-ietf-dice-profile-10
Thread-Index: AdBaRD43fIm4A7pxR+i8Tmj88qY9Lw==
Message-ID: <ED286F38-43EF-4CAC-AD95-D3AAC33EDB52@arm.com>
References: <trinity-078bdef2-9c8d-463d-a67b-08cf76b9987c-1425858175130@3capp-gmx-bs34>
In-Reply-To: <trinity-078bdef2-9c8d-463d-a67b-08cf76b9987c-1425858175130@3capp-gmx-bs34>
Accept-Language: en-US, en-GB
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-GB
MIME-Version: 1.0
X-MC-Unique: 115030908371807802
Content-Type: multipart/alternative; boundary="_000_ED286F3843EF4CACAD95D3AAC33EDB52armcom_"
Archived-At: <http://mailarchive.ietf.org/arch/msg/dtls-iot/47nGZTfCPrpd-uZRIpNqtwWQIrQ>
Cc: "dtls-iot@ietf.org" <dtls-iot@ietf.org>
Subject: Re: [Dtls-iot] draft-ietf-dice-profile-10
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: Mon, 09 Mar 2015 08:37:25 -0000

--_000_ED286F3843EF4CACAD95D3AAC33EDB52armcom_
Content-Type: text/plain; charset=WINDOWS-1252
Content-Transfer-Encoding: quoted-printable

Thanks to Matthias, Akbar, Rene and others for the WGLC comments. Please le=
t Hannes know if he has sufficiently taken them into account.

As the next step, I will be proceeding with the IESG write-up.

As many of you have probably noticed, DICE is not scheduled for a F2F meeti=
ng at the Dallas IETF. We did this on purpose, to be able to focus on finis=
hing the profile and getting it through the IESG. If you have any questions=
 on that don't hesitate to ask me directly.

Regards,
Zach

On Mar 9, 2015, at 1:42 AM, Hannes Tschofenig <hannes.tschofenig@gmx.net<ma=
ilto:hannes.tschofenig@gmx.net>> wrote:

Version -10 of the profile draft addresses the working group last call revi=
ew comments. I would still like to hear from the reviewers whether they are=
 fine with the changes I have made in response to their feedback.

Ciao
Hannes

_______________________________________________
dtls-iot mailing list
dtls-iot@ietf.org<mailto:dtls-iot@ietf.org>
https://www.ietf.org/mailman/listinfo/dtls-iot

Zach Shelby
Vice President, Marketing
ARM Internet of Things BU
www.arm.com<http://www.arm.com>
US: +1 (408) 203-9434
Finland: +358 407796297
Skype: zdshelby
LinkedIn: fi.linkedin.com/in/zachshelby/<http://fi.linkedin.com/in/zachshel=
by/>


-- IMPORTANT NOTICE: The contents of this email and any attachments are con=
fidential and may also be privileged. If you are not the intended recipient=
, please notify the sender immediately and do not disclose the contents to =
any other person, use it for any purpose, or store or copy the information =
in any medium. Thank you.

ARM Limited, Registered office 110 Fulbourn Road, Cambridge CB1 9NJ, Regist=
ered in England & Wales, Company No: 2557590
ARM Holdings plc, Registered office 110 Fulbourn Road, Cambridge CB1 9NJ, R=
egistered in England & Wales, Company No: 2548782
--_000_ED286F3843EF4CACAD95D3AAC33EDB52armcom_
Content-Type: text/html; charset=WINDOWS-1252
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space; ">
<div>Thanks to Matthias, Akbar, Rene and others for the WGLC comments. Plea=
se let Hannes know if he has sufficiently taken them into account.</div>
<div><br>
</div>
<div>As the next step, I will be proceeding with the IESG write-up.</div>
<div><br>
</div>
<div>As many of you have probably noticed, DICE is not scheduled for a F2F =
meeting at the Dallas IETF. We did this on purpose, to be able to focus on =
finishing the profile and getting it through the IESG. If you have any ques=
tions on that don't hesitate to
 ask me directly.</div>
<div><br>
</div>
<div>Regards,</div>
<div>Zach</div>
<br>
<div>
<div>On Mar 9, 2015, at 1:42 AM, Hannes Tschofenig &lt;<a href=3D"mailto:ha=
nnes.tschofenig@gmx.net">hannes.tschofenig@gmx.net</a>&gt; wrote:</div>
<br class=3D"Apple-interchange-newline">
<blockquote type=3D"cite">
<div>
<div style=3D"font-family: Verdana;font-size: 12.0px;">
<div>Version -10 of the profile draft addresses the working group last call=
 review comments.&nbsp;<span style=3D"line-height: 1.6em;">I would still li=
ke to hear from the reviewers whether they are fine with the changes I have=
 made in response to their feedback.&nbsp;</span></div>
<div>&nbsp;</div>
<div>Ciao</div>
<div>Hannes</div>
<div>&nbsp;</div>
</div>
</div>
_______________________________________________<br>
dtls-iot mailing list<br>
<a href=3D"mailto:dtls-iot@ietf.org">dtls-iot@ietf.org</a><br>
https://www.ietf.org/mailman/listinfo/dtls-iot</blockquote>
</div>
<br>
<div apple-content-edited=3D"true">
<div style=3D"color: rgb(0, 0, 0); font-family: Helvetica; font-size: mediu=
m; font-style: normal; font-variant: normal; font-weight: normal; letter-sp=
acing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; t=
ext-indent: 0px; text-transform: none; white-space: normal; widows: 2; word=
-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0=
px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: af=
ter-white-space; ">
<div style=3D"color: rgb(0, 0, 0); font-family: Helvetica; font-size: mediu=
m; font-style: normal; font-variant: normal; font-weight: normal; letter-sp=
acing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; t=
ext-indent: 0px; text-transform: none; white-space: normal; widows: 2; word=
-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0=
px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: af=
ter-white-space; ">
<div style=3D"color: rgb(0, 0, 0); font-family: Helvetica; font-size: mediu=
m; font-style: normal; font-variant: normal; font-weight: normal; letter-sp=
acing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; t=
ext-indent: 0px; text-transform: none; white-space: normal; widows: 2; word=
-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0=
px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: af=
ter-white-space; ">
<div style=3D"color: rgb(0, 0, 0); font-family: Helvetica; font-size: mediu=
m; font-style: normal; font-variant: normal; font-weight: normal; letter-sp=
acing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; t=
ext-indent: 0px; text-transform: none; white-space: normal; widows: 2; word=
-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0=
px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: af=
ter-white-space; ">
<div style=3D"color: rgb(0, 0, 0); font-family: Helvetica; font-size: mediu=
m; font-style: normal; font-variant: normal; font-weight: normal; letter-sp=
acing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; t=
ext-indent: 0px; text-transform: none; white-space: normal; widows: 2; word=
-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0=
px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: af=
ter-white-space; ">
<div style=3D"color: rgb(0, 0, 0); font-family: Helvetica; font-size: mediu=
m; font-style: normal; font-variant: normal; font-weight: normal; letter-sp=
acing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; t=
ext-indent: 0px; text-transform: none; white-space: normal; widows: 2; word=
-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0=
px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: af=
ter-white-space; ">
<div style=3D"color: rgb(0, 0, 0); font-family: Helvetica; font-size: mediu=
m; font-style: normal; font-variant: normal; font-weight: normal; letter-sp=
acing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; t=
ext-indent: 0px; text-transform: none; white-space: normal; widows: 2; word=
-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0=
px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: af=
ter-white-space; ">
<div style=3D"color: rgb(0, 0, 0); font-family: Helvetica; font-size: mediu=
m; font-style: normal; font-variant: normal; font-weight: normal; letter-sp=
acing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; t=
ext-indent: 0px; text-transform: none; white-space: normal; widows: 2; word=
-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0=
px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: af=
ter-white-space; ">
<div style=3D"color: rgb(0, 0, 0); font-family: Helvetica; font-size: mediu=
m; font-style: normal; font-variant: normal; font-weight: normal; letter-sp=
acing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; t=
ext-indent: 0px; text-transform: none; white-space: normal; widows: 2; word=
-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0=
px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: af=
ter-white-space; ">
<div>Zach Shelby</div>
<div>Vice President, Marketing</div>
<div>ARM Internet of Things BU</div>
<div><a href=3D"http://www.arm.com">www.arm.com</a></div>
<div>US:&nbsp;&#43;1 (408) 203-9434</div>
<div>Finland: &#43;358 407796297</div>
<div>Skype: zdshelby</div>
<div>LinkedIn:&nbsp;<a href=3D"http://fi.linkedin.com/in/zachshelby/" title=
=3D"View public profile" name=3D"webProfileURL">fi.linkedin.com/in/zachshel=
by/</a></div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<br>
<br>
<font face=3D"Arial" color=3D"Black" size=3D"2">-- IMPORTANT NOTICE: The co=
ntents of this email and any attachments are confidential and may also be p=
rivileged. If you are not the intended recipient, please notify the sender =
immediately and do not disclose the contents
 to any other person, use it for any purpose, or store or copy the informat=
ion in any medium. Thank you.<br>
<br>
ARM Limited, Registered office 110 Fulbourn Road, Cambridge CB1 9NJ, Regist=
ered in England &amp; Wales, Company No: 2557590<br>
ARM Holdings plc, Registered office 110 Fulbourn Road, Cambridge CB1 9NJ, R=
egistered in England &amp; Wales, Company No: 2548782<br>
</font>
</body>
</html>
--_000_ED286F3843EF4CACAD95D3AAC33EDB52armcom_--


From nobody Mon Mar  9 08:26:48 2015
Return-Path: <Rene.Hummen@comsys.rwth-aachen.de>
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 F05241A8ACD for <dtls-iot@ietfa.amsl.com>; Mon,  9 Mar 2015 08:26:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.86
X-Spam-Level: 
X-Spam-Status: No, score=-3.86 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-2.3, T_RP_MATCHES_RCVD=-0.01] 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 tc1thfjijH2v for <dtls-iot@ietfa.amsl.com>; Mon,  9 Mar 2015 08:26:44 -0700 (PDT)
Received: from mx-out-2.rwth-aachen.de (mx-out-2.rwth-aachen.de [134.130.5.187]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AC6C91A902E for <dtls-iot@ietf.org>; Mon,  9 Mar 2015 08:19:51 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="5.11,368,1422918000";  d="p7s'?scan'208";a="288846286"
Received: from mail-i4.nets.rwth-aachen.de ([137.226.12.21]) by mx-2.rz.rwth-aachen.de with ESMTP; 09 Mar 2015 16:19:50 +0100
Received: from messenger.nets.rwth-aachen.de (messenger.nets.rwth-aachen.de [137.226.13.40]) by mail-i4.nets.rwth-aachen.de (Postfix) with ESMTP id D703713DFD1; Mon,  9 Mar 2015 16:19:49 +0100 (CET)
Received: from MESSENGER.nets.rwth-aachen.de ([fe80::d4e:bb9d:9e0:bfee]) by MESSENGER.nets.rwth-aachen.de ([fe80::d4e:bb9d:9e0:bfee%12]) with mapi id 14.01.0218.012; Mon, 9 Mar 2015 16:19:49 +0100
From: Rene Hummen <Rene.Hummen@comsys.rwth-aachen.de>
To: Hannes Tschofenig <hannes.tschofenig@gmx.net>
Thread-Topic: [Dtls-iot] Review of draft-ietf-dice-profile-10
Thread-Index: AQHQWnx7r6UOQaogEkakjPnECZZkaA==
Date: Mon, 9 Mar 2015 15:19:49 +0000
Message-ID: <6246C1EC-5D70-4410-9D02-93CCC135E088@comsys.rwth-aachen.de>
Accept-Language: en-US, de-DE
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [137.226.12.37]
Content-Type: multipart/signed; boundary="Apple-Mail=_3F608864-EB44-4ADF-92A9-192746A5D325"; protocol="application/pkcs7-signature"; micalg=sha1
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/dtls-iot/W-KvBj57cdcVUHIL2Rz-psXdPIA>
Cc: "dtls-iot@ietf.org" <dtls-iot@ietf.org>
Subject: Re: [Dtls-iot] Review of draft-ietf-dice-profile-10
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: Mon, 09 Mar 2015 15:26:47 -0000

--Apple-Mail=_3F608864-EB44-4ADF-92A9-192746A5D325
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252

Hi Hannes,

On 07 Mar 2015, at 11:08, Hannes Tschofenig <hannes.tschofenig@gmx.net> =
wrote:
>> 4) Section 5 (line 1025)
>>=20
>> "SHA-256 is the recommended default PRF.=94
>>=20
>> In which document? The DTLS profile or the (D)TLS specification?
>>=20
>=20
> Actually, the story is a bit more complex since the PRF is part of the
> ciphersuite definition and while the TLS 1.2 spec says that new
> ciphersuites should use the SHA-256 based construction it also allows =
a
> ciphersuite to define else. I added extra text to the 'The Ciphersuite
> Concept' section.

This flexibility in PRF selection exactly was the reason for my comment. =
You now discuss the use of SHA-256 for Pre-Shared Secrets, but not in =
case of Raw Public Keys and Certificates. Is there a special need to =
highlight SHA-256 for Pre-Shared Secrets?

> 11) Section 21 (line 2089 and below)
>> "Offer access to building blocks in addition (or as an alternative)=20=

>> to the complete functionality.  For example, a chip manufacturer who
>> gives developers access to the AES crypto function can use it to
>> build an efficient AES-GCM implementations.  Another example is to
>> make a special instruction available that increases the speed of
>> speed-up carryless multiplications.=94
>>=20
>> Why not use ECB as a basic example of a building block?
>>=20
> I didn't want to go too far with the recommendation about what should =
be
> done in hardware but rather state high-level principles.

Ok, I just realized that re-phrasing "AES crypto function=94 to "AES =
block cipher=94 above would fix my comment.

>> 12) Appendix A (line 2673 and below)
>>=20
>> In contrast to the remaining profile, this (obviously) is very link
>> layer specific normative text. Why not move this to a short separate
>> document?
>>=20
>=20
> As Thomas noted the content of the appendix was actually in a separate
> document. When we presented it the recommendation was made to include =
it
> in here since the underlying message about the timeout values is
> applicable also to other radio technologies.

I completely agree about the integration of the timeout values. I just =
wonder about the rest (which now is the Appendix).

> I also believe that the text in the appendix does not disrupt
> readability for others who do not care about this type of usage.

That is true. I am not sure if the Appendix of the general IoT profile =
isn=92t hiding this SMS-related information for interested parties. To =
me, it makes more sense to have Appendix A as a separate document that =
references the IoT profile. If others believe the Appendix is the way to =
go forward, I won=92t stand in the way though.

Otherwise, I agree with your changes.

BR
Ren=E9


>=20
> Ciao
> Hannes
>=20
>>=20
>>=20
>> BR, Ren=E9
>>=20
>>=20
>> [1]
>> =
https://github.com/hannestschofenig/tschofenig-ids/commit/37d0cfa130904dcb=
a6c2d470f286bdb98b81e41d
>>=20
>>=20
>>=20
>> -- Dipl.-Inform. Rene Hummen, Ph.D. Student Chair of Communication
>> and Distributed Systems RWTH Aachen University, Germany tel: +49 241
>> 80 21426 web: http://www.comsys.rwth-aachen.de/team/rene-hummen/
>>=20
>>=20
>>=20
>> _______________________________________________ dtls-iot mailing
>> list dtls-iot@ietf.org=20
>> https://www.ietf.org/mailman/listinfo/dtls-iot


--
Dipl.-Inform. Rene Hummen, Ph.D. Student
Chair of Communication and Distributed Systems
RWTH Aachen University, Germany
tel: +49 241 80 21426
web: http://www.comsys.rwth-aachen.de/team/rene-hummen/


--Apple-Mail=_3F608864-EB44-4ADF-92A9-192746A5D325
Content-Disposition: attachment; filename="smime.p7s"
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIOGzCCBCEw
ggMJoAMCAQICAgDHMA0GCSqGSIb3DQEBBQUAMHExCzAJBgNVBAYTAkRFMRwwGgYDVQQKExNEZXV0
c2NoZSBUZWxla29tIEFHMR8wHQYDVQQLExZULVRlbGVTZWMgVHJ1c3QgQ2VudGVyMSMwIQYDVQQD
ExpEZXV0c2NoZSBUZWxla29tIFJvb3QgQ0EgMjAeFw0wNjEyMTkxMDI5MDBaFw0xOTA2MzAyMzU5
MDBaMFoxCzAJBgNVBAYTAkRFMRMwEQYDVQQKEwpERk4tVmVyZWluMRAwDgYDVQQLEwdERk4tUEtJ
MSQwIgYDVQQDExtERk4tVmVyZWluIFBDQSBHbG9iYWwgLSBHMDEwggEiMA0GCSqGSIb3DQEBAQUA
A4IBDwAwggEKAoIBAQDpm8NnhfkNrvWNVMOWUDU9YuluTO2U1wBblSJ01CDrNI/W7MAxBAuZgeKm
FNJSoCgjhIt0iQReW+DieMF4yxbLKDU5ey2QRdDtoAB6fL9KDhsAw4bpXCsxEXsM84IkQ4wcOItq
aACa7txPeKvSxhObdq3u3ibo7wGvdA/BCaL2a869080UME/15eOkyGKbghoDJzANAmVgTe3RCSMq
ljVYJ9N2xnG2kB3E7f81hn1vM7PbD8URwoqDoZRdQWvY0hD1TP3KUazZve+Sg7va64sWVlZDz+HV
Ez2mHycwzUlU28kTNJpxdcVs6qcLmPkhnSevPqM5OUhqjK3JmfvDEvK9AgMBAAGjgdkwgdYwcAYD
VR0fBGkwZzBloGOgYYZfaHR0cDovL3BraS50ZWxlc2VjLmRlL2NnaS1iaW4vc2VydmljZS9hZl9E
b3dubG9hZEFSTC5jcmw/LWNybF9mb3JtYXQ9WF81MDkmLWlzc3Vlcj1EVF9ST09UX0NBXzIwHQYD
VR0OBBYEFEm3xs/oPR9/6kR7Eyn38QpwPt5kMB8GA1UdIwQYMBaAFDHDeRu69VPXF+CJei0XbAqz
K50zMA4GA1UdDwEB/wQEAwIBBjASBgNVHRMBAf8ECDAGAQH/AgECMA0GCSqGSIb3DQEBBQUAA4IB
AQA74Vp3wEgX3KkY7IGvWonwvSiSpspZGBJw7Cjy565/lizn8l0ZMfYTK3S9vYCyufdnyTmieTvh
ERHua3iRM347XyYndVNljjNj7s9zw7CSI0khUHUjoR8Y4pSFPT8z6XcgjaK95qGFKUD2P3MyWA0J
a6bahWzAP7uNZmRWJE6uDT8yNQFb6YyC2XJZT7GGhfF0hVblw/hc843uR7NTBXDn5U2KaYMo4RMJ
hp5eyOpYHgwf+aTUWgRo/Sg+iwK2WLX2oSw3VwBnqyNojWOl75lrXP1LVvarQIc01BGSbOyHxQoL
BzNytG8MHVQs2FHHzL8w00Ny8TK/jM5JY6gA9/IcMIIE6DCCA9CgAwIBAgIECfJ04DANBgkqhkiG
9w0BAQUFADBaMQswCQYDVQQGEwJERTETMBEGA1UEChMKREZOLVZlcmVpbjEQMA4GA1UECxMHREZO
LVBLSTEkMCIGA1UEAxMbREZOLVZlcmVpbiBQQ0EgR2xvYmFsIC0gRzAxMB4XDTA3MDIxNDExNDkz
OFoXDTE5MDIxMzAwMDAwMFowXjELMAkGA1UEBhMCREUxFDASBgNVBAoTC1JXVEggQWFjaGVuMRcw
FQYDVQQDEw5SV1RIIEFhY2hlbiBDQTEgMB4GCSqGSIb3DQEJARYRY2FAcnd0aC1hYWNoZW4uZGUw
ggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQC4MAhk48jcelLfNUI5kvMv+CF54xJnL4x/
cJQnN2NId6CJ3fqs0siO2exIACfzdjxOUpQ6ZFOn5pdTvTi7stnk8WAaP/d9LFd8k9Gbxjh7xh3L
+0a3ac+/tHJcX564ntUxGtVGMuShEoUaZUT5fw97TL36UJ8OqXLrqpdAKcFKaJ+pgRp2gTLj4MNU
MPjA4GlstpjoLnT++qFm7t/ZS92/E3OqNJUwHH6C35vSroVscmg+a7XxT6U4JO99MYxNcTIMzhPS
9Ytp+302w7i51daBjr0hFGPK0nLSV6gv77zBSFJ7AVGJJxBSUzDn0xkDLYvZwqaeYkj8kDB2oSeR
yfGjAgMBAAGjggGwMIIBrDAPBgNVHRMBAf8EBTADAQH/MAsGA1UdDwQEAwIBBjAdBgNVHQ4EFgQU
btU+wBwvcck8v0lO72pVSOzR8jgwHwYDVR0jBBgwFoAUSbfGz+g9H3/qRHsTKffxCnA+3mQwHAYD
VR0RBBUwE4ERY2FAcnd0aC1hYWNoZW4uZGUwgYgGA1UdHwSBgDB+MD2gO6A5hjdodHRwOi8vY2Rw
MS5wY2EuZGZuLmRlL2dsb2JhbC1yb290LWNhL3B1Yi9jcmwvY2FjcmwuY3JsMD2gO6A5hjdodHRw
Oi8vY2RwMi5wY2EuZGZuLmRlL2dsb2JhbC1yb290LWNhL3B1Yi9jcmwvY2FjcmwuY3JsMIGiBggr
BgEFBQcBAQSBlTCBkjBHBggrBgEFBQcwAoY7aHR0cDovL2NkcDEucGNhLmRmbi5kZS9nbG9iYWwt
cm9vdC1jYS9wdWIvY2FjZXJ0L2NhY2VydC5jcnQwRwYIKwYBBQUHMAKGO2h0dHA6Ly9jZHAyLnBj
YS5kZm4uZGUvZ2xvYmFsLXJvb3QtY2EvcHViL2NhY2VydC9jYWNlcnQuY3J0MA0GCSqGSIb3DQEB
BQUAA4IBAQAXh37GLAscIHrVqQYrG5P/dYULxAseU6xuXKnSpVTnMWVFf1TtN/p2D+8XTKtl/A4W
lYa9np+ONblWcS1nJsuYf7N9wrO4zCEcVBNLIAHCY3ZXG+IoNHwgXqSYqXHzrAQZjkSJr1RfbFE4
njUy0nNhtC51HX0ongWfqODc6z7aF9we20615Mh8Kk8uox4XgjLLV/UjPVlwRAnuYIeF0wycvQ6j
z/PJMuOrXShpqejpaiRXqKx8oPXAlCcnoqRLlQc1L0iwQHBn0Em6tDmMHcahbf9SBOWiZ8+O0av4
ly8CQ95okz9hto9UErXUIzNea2AQXBtlIyLLKgVuYPf4i3IyMIIFBjCCA+6gAwIBAgIHFHkMp6Zz
lDANBgkqhkiG9w0BAQUFADBeMQswCQYDVQQGEwJERTEUMBIGA1UEChMLUldUSCBBYWNoZW4xFzAV
BgNVBAMTDlJXVEggQWFjaGVuIENBMSAwHgYJKoZIhvcNAQkBFhFjYUByd3RoLWFhY2hlbi5kZTAe
Fw0xMjA5MTkwOTIzMzVaFw0xNTA5MTkwOTIzMzVaMDkxCzAJBgNVBAYTAkRFMRQwEgYDVQQKEwtS
V1RIIEFhY2hlbjEUMBIGA1UEAxMLUmVuZSBIdW1tZW4wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAw
ggEKAoIBAQDDoo52P1ghFxnZmWNVnv7+qDKjyif4AoLkJrs7CVV34cRm/PhuW8WzLqOES0B0ENWE
eDUez2Dc4inRNXdF5zMy36rLuKsK5MuznnXTzqYGMeGQAU7MkUvSZdMIWDpMdVc5nKzP81leStBY
c3t6T2PNFHbeQEoHqjUNMQc9wfFWVQHTnQt9+kejn8NDMHqzKjJ+bnXm3byZCEs09CnmGli1irfJ
cR6Fo4KcRMHKVrAHUG8NB+QyPv9RzEawbxwZgyDot5G/A4iRnX0aZ7OjB6ohkepKniBZqSMeOIu1
/Y7p6zYwqiLLywX1VtDQz067R4pkrT5h/IO/VcEGXukXqPA/AgMBAAGjggHsMIIB6DAvBgNVHSAE
KDAmMBEGDysGAQQBga0hgiwBAQQCAzARBg8rBgEEAYGtIYIsAgEEAgMwCQYDVR0TBAIwADALBgNV
HQ8EBAMCBeAwHQYDVR0lBBYwFAYIKwYBBQUHAwIGCCsGAQUFBwMEMB0GA1UdDgQWBBTAJpMHhUGI
9hiu0k6Ccd8MggDivTAfBgNVHSMEGDAWgBRu1T7AHC9xyTy/SU7valVI7NHyODAsBgNVHREEJTAj
gSFyZW5lLmh1bW1lbkBjb21zeXMucnd0aC1hYWNoZW4uZGUweQYDVR0fBHIwcDA2oDSgMoYwaHR0
cDovL2NkcDEucGNhLmRmbi5kZS9yd3RoLWNhL3B1Yi9jcmwvY2FjcmwuY3JsMDagNKAyhjBodHRw
Oi8vY2RwMi5wY2EuZGZuLmRlL3J3dGgtY2EvcHViL2NybC9jYWNybC5jcmwwgZQGCCsGAQUFBwEB
BIGHMIGEMEAGCCsGAQUFBzAChjRodHRwOi8vY2RwMS5wY2EuZGZuLmRlL3J3dGgtY2EvcHViL2Nh
Y2VydC9jYWNlcnQuY3J0MEAGCCsGAQUFBzAChjRodHRwOi8vY2RwMi5wY2EuZGZuLmRlL3J3dGgt
Y2EvcHViL2NhY2VydC9jYWNlcnQuY3J0MA0GCSqGSIb3DQEBBQUAA4IBAQCA/Plhm3Cxu6mOs3O3
Wsl/9Ow7rbANrMvB2zxZW4yGJGu5FKaib+ir66xbpMAbmN4gqQmwuDMW+oWC7U+m9IfFG+T482Rz
AvsYEOZUmq3Y0KFx87MEJdgaWtJ7PnlUaGtgQjdMso0pvAboZnp2pfxazq46lHXDgTCJsd7MUHb6
MzV9JpDzq0qnXeM2d+WxpOckuo11SAtXod+zuI9Udm7oUVIGeI8yFQrtHhtfESOmi57zSTseEYNS
meInQtPv1ARHwuFRBcG5SkHDqbFZIw+2QVK2qq23NlTeBB/JfitX13NYdYNMgymz30iHXvxmB1nN
fmJ9RDejQ4SVonYR7pLLMYIC5zCCAuMCAQEwaTBeMQswCQYDVQQGEwJERTEUMBIGA1UEChMLUldU
SCBBYWNoZW4xFzAVBgNVBAMTDlJXVEggQWFjaGVuIENBMSAwHgYJKoZIhvcNAQkBFhFjYUByd3Ro
LWFhY2hlbi5kZQIHFHkMp6ZzlDAJBgUrDgMCGgUAoIIBUzAYBgkqhkiG9w0BCQMxCwYJKoZIhvcN
AQcBMBwGCSqGSIb3DQEJBTEPFw0xNTAzMDkxNTE5NDhaMCMGCSqGSIb3DQEJBDEWBBQeCqgtkBoH
mOLn1OjtyiHZhYZMIjB4BgkrBgEEAYI3EAQxazBpMF4xCzAJBgNVBAYTAkRFMRQwEgYDVQQKEwtS
V1RIIEFhY2hlbjEXMBUGA1UEAxMOUldUSCBBYWNoZW4gQ0ExIDAeBgkqhkiG9w0BCQEWEWNhQHJ3
dGgtYWFjaGVuLmRlAgcUeQynpnOUMHoGCyqGSIb3DQEJEAILMWugaTBeMQswCQYDVQQGEwJERTEU
MBIGA1UEChMLUldUSCBBYWNoZW4xFzAVBgNVBAMTDlJXVEggQWFjaGVuIENBMSAwHgYJKoZIhvcN
AQkBFhFjYUByd3RoLWFhY2hlbi5kZQIHFHkMp6ZzlDANBgkqhkiG9w0BAQEFAASCAQCmPuQUo7pj
ckVNKNLycm6yWf7oet7t+EZb0ChEorTZSH7ypamKah4W1NmWOsodmwCrcQvyUA7eMU4Si52ZrHi1
ZjRzr2Qd2vT8Tz512xtEvyVjpMCwLji05PNJSAYo9hYsAF8Ay/1dkXK0AQPSJ+ab2RBcrFh1Je6t
FHjxiDhzC2BjlUGWtvBYVCdNz3WtazKzm2tzgV5zLKXW8WL3AgDGmzpnMw/igNU4n8cD7a84wyWH
ZrYkHtQ7tKy6B0mUgIPE8WhIQXbnhOzWs1jN+361a7be5jVCikfT183KHBV/Zbi5f6V3864IVngE
GRSG3mnYind/76/VtA8VT8w8uCGjAAAAAAAA

--Apple-Mail=_3F608864-EB44-4ADF-92A9-192746A5D325--


From nobody Tue Mar 10 00:53:53 2015
Return-Path: <sandeep.kumar@philips.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 4D5191B2A24 for <dtls-iot@ietfa.amsl.com>; Tue, 10 Mar 2015 00:53:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_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 CJkTm_Z-1m58 for <dtls-iot@ietfa.amsl.com>; Tue, 10 Mar 2015 00:53:49 -0700 (PDT)
Received: from emea01-am1-obe.outbound.protection.outlook.com (mail-am1on0723.outbound.protection.outlook.com [IPv6:2a01:111:f400:fe00::723]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3EE761B2A20 for <dtls-iot@ietf.org>; Tue, 10 Mar 2015 00:53:48 -0700 (PDT)
Received: from AM3PR04MB481.eurprd04.prod.outlook.com (10.242.113.11) by AM3PR04MB369.eurprd04.prod.outlook.com (10.242.111.139) with Microsoft SMTP Server (TLS) id 15.1.106.15; Tue, 10 Mar 2015 07:36:08 +0000
Received: from VI1PR04CA0010.eurprd04.prod.outlook.com (25.163.3.20) by AM3PR04MB481.eurprd04.prod.outlook.com (10.242.113.11) with Microsoft SMTP Server (TLS) id 15.1.106.15; Tue, 10 Mar 2015 07:36:07 +0000
Received: from AM1FFO11FD043.protection.gbl (2a01:111:f400:7e00::113) by VI1PR04CA0010.outlook.office365.com (2a01:111:e400:58e9::20) with Microsoft SMTP Server (TLS) id 15.1.106.15 via Frontend Transport; Tue, 10 Mar 2015 07:36:07 +0000
Received: from mail.philips.com (206.191.240.52) by AM1FFO11FD043.mail.protection.outlook.com (10.174.64.232) with Microsoft SMTP Server (TLS) id 15.1.112.13 via Frontend Transport; Tue, 10 Mar 2015 07:36:01 +0000
Received: from DBXPRD9003MB059.MGDPHG.emi.philips.com ([169.254.7.249]) by DBXPRD9003HT003.MGDPHG.emi.philips.com ([141.251.25.208]) with mapi id 14.16.0478.000; Tue, 10 Mar 2015 07:35:57 +0000
From: "Kumar, Sandeep" <sandeep.kumar@philips.com>
To: "dtls-iot@ietf.org" <dtls-iot@ietf.org>
Thread-Topic: New Version Notification for draft-kumar-dice-multicast-security-00.txt
Thread-Index: AQHQWqGuiGU5t2nFqUGl7sksXcQCP50VU6+Q
Date: Tue, 10 Mar 2015 07:35:57 +0000
Message-ID: <BE6D13F6A4554947952B39008B0DC0153ED26F13@DBXPRD9003MB059.MGDPHG.emi.philips.com>
References: <20150309194552.11244.59357.idtracker@ietfa.amsl.com>
In-Reply-To: <20150309194552.11244.59357.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [85.150.192.178]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-EOPAttributedMessage: 0
Received-SPF: None (protection.outlook.com: philips.com does not designate permitted sender hosts)
Authentication-Results: spf=none (sender IP is 206.191.240.52) smtp.mailfrom=sandeep.kumar@philips.com; ietf.org; dkim=none (message not signed) header.d=none;
X-Forefront-Antispam-Report: CIP:206.191.240.52; CTRY:US; IPV:NLI; EFV:NLI; BMV:1; SFV:NSPM; SFS:(10019020)(6009001)(428002)(13464003)(374574003)(85714005)(377454003)(199003)(53754006)(189002)(377424004)(105586002)(87936001)(106116001)(2351001)(2656002)(86362001)(50466002)(19580395003)(101416001)(23676002)(2501003)(55846006)(54356999)(230783001)(33656002)(2900100001)(47776003)(102836002)(2420400003)(77156002)(15975445007)(6806004)(62966003)(19580405001)(66066001)(110136001)(2950100001)(76176999)(450100001)(107886001)(50986999)(106466001)(92566002)(2920100001)(46102003)(104016003)(1720100001)(567094001); DIR:OUT; SFP:1102; SCL:1; SRVR:AM3PR04MB481; H:mail.philips.com; FPR:; SPF:None; MLV:sfv; A:1; MX:1; LANG:en; 
X-Microsoft-Antispam: UriScan:; BCL:0; PCL:0; RULEID:; SRVR:AM3PR04MB481; UriScan:; BCL:0; PCL:0; RULEID:; SRVR:AM3PR04MB369; 
X-Microsoft-Antispam-PRVS: <AM3PR04MB481B2C5E0C78CC40849C734E4180@AM3PR04MB481.eurprd04.prod.outlook.com>
X-Exchange-Antispam-Report-Test: UriScan:;
X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(601004)(5005006)(5002009); SRVR:AM3PR04MB481; BCL:0; PCL:0; RULEID:; SRVR:AM3PR04MB481; 
X-Forefront-PRVS: 051158ECBB
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 10 Mar 2015 07:36:01.7268 (UTC)
X-MS-Exchange-CrossTenant-Id: 1a407a2d-7675-4d17-8692-b3ac285306e4
X-MS-Exchange-CrossTenant-OriginalAttributedTenantConnectingIp: TenantId=1a407a2d-7675-4d17-8692-b3ac285306e4; Ip=[206.191.240.52];  Helo=[mail.philips.com]
X-MS-Exchange-CrossTenant-FromEntityHeader: HybridOnPrem
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM3PR04MB481
X-OriginatorOrg: philips.com
Archived-At: <http://mailarchive.ietf.org/arch/msg/dtls-iot/D6Fdp9xvsAdYqkwiqc7dygO7pu4>
Subject: [Dtls-iot] FW: New Version Notification for draft-kumar-dice-multicast-security-00.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: Tue, 10 Mar 2015 07:53:52 -0000

SGkgYWxsDQoNCldlIHN1Ym1pdHRlZCBhIHByZWxpbWluYXJ5IHZlcnNpb24gb2YgdGhlIGdyb3Vw
IHNlY3VyaXR5IGRyYWZ0IGFzIGRpc2N1c3NlZCBhdCBJRVRGLTkxLiBNb3JlIGNoYW5nZXMgYXJl
IGV4cGVjdGVkIGJ1dCB0aGUgb3ZlcmFsbCB0aGUgc29sdXRpb24gZGlyZWN0aW9uIGNhbiBiZSBz
ZWVuIGluIHRoZSBkcmFmdC4NCkFsdGhvdWdoIHRoZSBncm91cCBpcyB2ZXJ5IGJ1c3kgd2l0aCBw
cm9maWxlIGRyYWZ0LCB3ZSB3b3VsZCBhcHByZWNpYXRlIGFueSBlYXJseSBjb21tZW50cyBvbiB0
aGUgZHJhZnQuDQoNClJlZ2FyZHMNClNhbmRlZXANCg0KLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0t
LS0NCkZyb206IGludGVybmV0LWRyYWZ0c0BpZXRmLm9yZyBbbWFpbHRvOmludGVybmV0LWRyYWZ0
c0BpZXRmLm9yZ10NClNlbnQ6IE1vbmRheSwgTWFyY2ggMDksIDIwMTUgODo0NiBQTQ0KVG86IFJl
bmUgU3RydWlrOyBSZW5lIFN0cnVpazsgU2FuZGVlcCBTLiBLdW1hcjsgU2FuZGVlcCBTLiBLdW1h
cg0KU3ViamVjdDogTmV3IFZlcnNpb24gTm90aWZpY2F0aW9uIGZvciBkcmFmdC1rdW1hci1kaWNl
LW11bHRpY2FzdC1zZWN1cml0eS0wMC50eHQNCg0KDQpBIG5ldyB2ZXJzaW9uIG9mIEktRCwgZHJh
ZnQta3VtYXItZGljZS1tdWx0aWNhc3Qtc2VjdXJpdHktMDAudHh0DQpoYXMgYmVlbiBzdWNjZXNz
ZnVsbHkgc3VibWl0dGVkIGJ5IFNhbmRlZXAgUy4gS3VtYXIgYW5kIHBvc3RlZCB0byB0aGUgSUVU
RiByZXBvc2l0b3J5Lg0KDQpOYW1lOiAgICAgICAgICAgZHJhZnQta3VtYXItZGljZS1tdWx0aWNh
c3Qtc2VjdXJpdHkNClJldmlzaW9uOiAgICAgICAwMA0KVGl0bGU6ICAgICAgICAgIFRyYW5zcG9y
dC1sYXllciBNdWx0aWNhc3QgU2VjdXJpdHkgZm9yIExvdy1Qb3dlciBhbmQgTG9zc3kgTmV0d29y
a3MgKExMTnMpDQpEb2N1bWVudCBkYXRlOiAgMjAxNS0wMy0wOQ0KR3JvdXA6ICAgICAgICAgIElu
ZGl2aWR1YWwgU3VibWlzc2lvbg0KUGFnZXM6ICAgICAgICAgIDE5DQpVUkw6ICAgICAgICAgICAg
aHR0cDovL3d3dy5pZXRmLm9yZy9pbnRlcm5ldC1kcmFmdHMvZHJhZnQta3VtYXItZGljZS1tdWx0
aWNhc3Qtc2VjdXJpdHktMDAudHh0DQpTdGF0dXM6ICAgICAgICAgaHR0cHM6Ly9kYXRhdHJhY2tl
ci5pZXRmLm9yZy9kb2MvZHJhZnQta3VtYXItZGljZS1tdWx0aWNhc3Qtc2VjdXJpdHkvDQpIdG1s
aXplZDogICAgICAgaHR0cDovL3Rvb2xzLmlldGYub3JnL2h0bWwvZHJhZnQta3VtYXItZGljZS1t
dWx0aWNhc3Qtc2VjdXJpdHktMDANCg0KDQpBYnN0cmFjdDoNCiAgIENvQVAgYW5kIDZMb1dQQU4g
YXJlIGZhc3QgZW1lcmdpbmcgYXMgdGhlIGRlLWZhY3RvIHByb3RvY29sIHN0YW5kYXJkcw0KICAg
aW4gdGhlIGFyZWEgb2YgcmVzb3VyY2UtY29uc3RyYWluZWQgZGV2aWNlcyBmb3JtaW5nIExvdy1w
b3dlciBhbmQNCiAgIExvc3N5IE5ldHdvcmtzIChMTE5zKS4gIFVuaWNhc3QgY29tbXVuaWNhdGlv
biBpbiBzdWNoIG5ldHdvcmtzIGFyZQ0KICAgc2VjdXJlZCBhdCB0aGUgdHJhbnNwb3J0IGxheWVy
IHVzaW5nIERUTFMsIGFzIG1hbmRhdGVkIGJ5IENvQVAuICBGb3INCiAgIHZhcmlvdXMgYXBwbGlj
YXRpb25zLCBJUCBtdWx0aWNhc3QtYmFzZWQgZ3JvdXAgY29tbXVuaWNhdGlvbnMgaW4gc3VjaA0K
ICAgbmV0d29ya3MgcHJvdmlkZSBjbGVhciBhZHZhbnRhZ2VzLiAgSG93ZXZlciwgYXQgdGhpcyBw
b2ludCwgQ29BUCBkb2VzDQogICBub3Qgc3BlY2lmeSBob3cgdG8gc2VjdXJlIGdyb3VwIGNvbW11
bmljYXRpb25zIGluIGFuIGludGVyb3BlcmFibGUNCiAgIHdheS4gIFRoaXMgZHJhZnQgc3BlY2lm
aWVzIHR3byBtZXRob2RzIGZvciBzZWN1cmluZyBDb0FQLWJhc2VkIGdyb3VwDQogICBjb21tdW5p
Y2F0aW9uIGF0IHRoZSB0cmFuc3BvcnQgbGF5ZXIgYW5kIHRhcmdldHMgZGVwbG95bWVudCBzY2Vu
YXJpb3MNCiAgIHRoYXQgbWF5IHJlcXVpcmUgZ3JvdXAgYXV0aGVudGljYXRpb24sIHJlc3BlY3Rp
dmVseSBzb3VyY2UNCiAgIGF1dGhlbnRpY2F0aW9uLiAgVGhlIHNwZWNpZmljYXRpb24gbGV2ZXJh
Z2VzIHRoZSBmYWN0IHRoYXQgRFRMUyBpcw0KICAgYWxyZWFkeSB1c2VkIGFzIHRoZSBtZWNoYW5p
c20gb2YgY2hvaWNlIHRvIHNlY3VyZSB1bmljYXN0DQogICBjb21tdW5pY2F0aW9ucyBhbmQgYWxs
b3dzIGdyb3VwIGNvbW11bmljYXRpb25zIHNlY3VyaXR5IHRvIGJlDQogICBpbXBsZW1lbnRlZCBh
cyBhbiBleHRlbnNpb24gb2YgRFRMUyByZWNvcmQgbGF5ZXIgcHJvY2Vzc2luZywgdGhlcmVieQ0K
ICAgbWluaW1pemluZyBpbmNyZW1lbnRhbCBpbXBsZW1lbnRhdGlvbiBjb3N0Lg0KDQoNCg0KDQpQ
bGVhc2Ugbm90ZSB0aGF0IGl0IG1heSB0YWtlIGEgY291cGxlIG9mIG1pbnV0ZXMgZnJvbSB0aGUg
dGltZSBvZiBzdWJtaXNzaW9uIHVudGlsIHRoZSBodG1saXplZCB2ZXJzaW9uIGFuZCBkaWZmIGFy
ZSBhdmFpbGFibGUgYXQgdG9vbHMuaWV0Zi5vcmcuDQoNClRoZSBJRVRGIFNlY3JldGFyaWF0DQoN
Cg0KX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NClRoZSBpbmZvcm1hdGlvbiBjb250
YWluZWQgaW4gdGhpcyBtZXNzYWdlIG1heSBiZSBjb25maWRlbnRpYWwgYW5kIGxlZ2FsbHkgcHJv
dGVjdGVkIHVuZGVyIGFwcGxpY2FibGUgbGF3LiBUaGUgbWVzc2FnZSBpcyBpbnRlbmRlZCBzb2xl
bHkgZm9yIHRoZSBhZGRyZXNzZWUocykuIElmIHlvdSBhcmUgbm90IHRoZSBpbnRlbmRlZCByZWNp
cGllbnQsIHlvdSBhcmUgaGVyZWJ5IG5vdGlmaWVkIHRoYXQgYW55IHVzZSwgZm9yd2FyZGluZywg
ZGlzc2VtaW5hdGlvbiwgb3IgcmVwcm9kdWN0aW9uIG9mIHRoaXMgbWVzc2FnZSBpcyBzdHJpY3Rs
eSBwcm9oaWJpdGVkIGFuZCBtYXkgYmUgdW5sYXdmdWwuIElmIHlvdSBhcmUgbm90IHRoZSBpbnRl
bmRlZCByZWNpcGllbnQsIHBsZWFzZSBjb250YWN0IHRoZSBzZW5kZXIgYnkgcmV0dXJuIGUtbWFp
bCBhbmQgZGVzdHJveSBhbGwgY29waWVzIG9mIHRoZSBvcmlnaW5hbCBtZXNzYWdlLg0K


From nobody Thu Mar 12 08:26:48 2015
Return-Path: <renzoefra@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 264CF1A886E for <dtls-iot@ietfa.amsl.com>; Thu, 12 Mar 2015 08:26:47 -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 OIor1bDuUzXF for <dtls-iot@ietfa.amsl.com>; Thu, 12 Mar 2015 08:26:44 -0700 (PDT)
Received: from mail-ie0-x230.google.com (mail-ie0-x230.google.com [IPv6:2607:f8b0:4001:c03::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 13DA11A7018 for <dtls-iot@ietf.org>; Thu, 12 Mar 2015 08:26:44 -0700 (PDT)
Received: by iecvj10 with SMTP id vj10so43352354iec.0 for <dtls-iot@ietf.org>; Thu, 12 Mar 2015 08:26:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=Yuuc1v/dt1wQGIyrl+teQpwxQ5udtA7F+5kkYfMPuww=; b=hpZh/HmRdRxd5q+J6aWHrfX8j4VUJ/rNoMHct0KZ+rY6HWxKd0fo3mpeaCZndVdnj4 PUqTEEKN1A9T/tm1w5T4QPlCoKSCu5ghKso6UewrdWFza0F7SkhA8V0Cuf+8kJGDLzQ4 5h9Do/X31lTe3KD2HnpfFs0a78NP8aGht9geHelrXq2K+BEG70CvnSdNGgjS5I3whDXA l6bytt1vhA6sZUa9Aay1Xx+SZBCULUAF9zFZeUcH16ROuscykCZk9mvUO+X/dRNCJBlI Y/DIKG3jP7baFMA/JKj0y9yEtmg2RaArTAfFrXZzlduNBv8uG0mF23flrwzM9xlAD+e8 O1wg==
X-Received: by 10.50.79.161 with SMTP id k1mr74769248igx.14.1426173993463; Thu, 12 Mar 2015 08:26:33 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.107.32.18 with HTTP; Thu, 12 Mar 2015 08:26:13 -0700 (PDT)
In-Reply-To: <6246C1EC-5D70-4410-9D02-93CCC135E088@comsys.rwth-aachen.de>
References: <6246C1EC-5D70-4410-9D02-93CCC135E088@comsys.rwth-aachen.de>
From: Renzo Navas <renzoefra@gmail.com>
Date: Thu, 12 Mar 2015 16:26:13 +0100
Message-ID: <CAD2CPUGtGsMe1HG4gW_T-VyV4gjd6tEHn0iz3h3iHieaJ4i0TA@mail.gmail.com>
To: Rene Hummen <Rene.Hummen@comsys.rwth-aachen.de>
Content-Type: multipart/alternative; boundary=089e01183c3644d622051119029d
Archived-At: <http://mailarchive.ietf.org/arch/msg/dtls-iot/0pIdnKEBG1UJei1QBF76wXRh5Sc>
Cc: Hannes Tschofenig <hannes.tschofenig@gmx.net>, "dtls-iot@ietf.org" <dtls-iot@ietf.org>
Subject: Re: [Dtls-iot] Review of draft-ietf-dice-profile-10
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: Thu, 12 Mar 2015 15:26:47 -0000

--089e01183c3644d622051119029d
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Good Evening,

This is my first message on this mailing list, I am a novice on the IETF
world.
Just my humble opinion as a reader about the SMS-appendix:

>> I also believe that the text in the appendix does not disrupt
>> readability for others who do not care about this type of usage.
>
>That is true. I am not sure if the Appendix of the general IoT profile
isn=E2=80=99t hiding this SMS-related information for interested parties.
>To me, it makes more sense to have Appendix A as a separate document that
references the IoT profile. If others believe the Appendix is the way to go
forward, I won=E2=80=99t stand in the way though.


For me it was very useful to have this information in the appendix
of draft-ietf-dice-profile-10.txt , otherwise I doubt I will have read
(draft-fossati-dtls-over-gsm-sms-01)  it anytime soon, thought the
information there was very relevant to me (my goal is to implement dtls on
a non-udp datagram transport -non-ip neither-).

Thank you for all your effort on this WG.

Renzo NAVAS



On Mon, Mar 9, 2015 at 4:19 PM, Rene Hummen <
Rene.Hummen@comsys.rwth-aachen.de> wrote:

> Hi Hannes,
>
> On 07 Mar 2015, at 11:08, Hannes Tschofenig <hannes.tschofenig@gmx.net>
> wrote:
> >> 4) Section 5 (line 1025)
> >>
> >> "SHA-256 is the recommended default PRF.=E2=80=9D
> >>
> >> In which document? The DTLS profile or the (D)TLS specification?
> >>
> >
> > Actually, the story is a bit more complex since the PRF is part of the
> > ciphersuite definition and while the TLS 1.2 spec says that new
> > ciphersuites should use the SHA-256 based construction it also allows a
> > ciphersuite to define else. I added extra text to the 'The Ciphersuite
> > Concept' section.
>
> This flexibility in PRF selection exactly was the reason for my comment.
> You now discuss the use of SHA-256 for Pre-Shared Secrets, but not in cas=
e
> of Raw Public Keys and Certificates. Is there a special need to highlight
> SHA-256 for Pre-Shared Secrets?
>
> > 11) Section 21 (line 2089 and below)
> >> "Offer access to building blocks in addition (or as an alternative)
> >> to the complete functionality.  For example, a chip manufacturer who
> >> gives developers access to the AES crypto function can use it to
> >> build an efficient AES-GCM implementations.  Another example is to
> >> make a special instruction available that increases the speed of
> >> speed-up carryless multiplications.=E2=80=9D
> >>
> >> Why not use ECB as a basic example of a building block?
> >>
> > I didn't want to go too far with the recommendation about what should b=
e
> > done in hardware but rather state high-level principles.
>
> Ok, I just realized that re-phrasing "AES crypto function=E2=80=9D to "AE=
S block
> cipher=E2=80=9D above would fix my comment.
>
> >> 12) Appendix A (line 2673 and below)
> >>
> >> In contrast to the remaining profile, this (obviously) is very link
> >> layer specific normative text. Why not move this to a short separate
> >> document?
> >>
> >
> > As Thomas noted the content of the appendix was actually in a separate
> > document. When we presented it the recommendation was made to include i=
t
> > in here since the underlying message about the timeout values is
> > applicable also to other radio technologies.
>
> I completely agree about the integration of the timeout values. I just
> wonder about the rest (which now is the Appendix).
>
> > I also believe that the text in the appendix does not disrupt
> > readability for others who do not care about this type of usage.
>
> That is true. I am not sure if the Appendix of the general IoT profile
> isn=E2=80=99t hiding this SMS-related information for interested parties.=
 To me, it
> makes more sense to have Appendix A as a separate document that reference=
s
> the IoT profile. If others believe the Appendix is the way to go forward,=
 I
> won=E2=80=99t stand in the way though.
>
> Otherwise, I agree with your changes.
>
> BR
> Ren=C3=A9
>
>
> >
> > Ciao
> > Hannes
> >
> >>
> >>
> >> BR, Ren=C3=A9
> >>
> >>
> >> [1]
> >>
> https://github.com/hannestschofenig/tschofenig-ids/commit/37d0cfa130904dc=
ba6c2d470f286bdb98b81e41d
> >>
> >>
> >>
> >> -- Dipl.-Inform. Rene Hummen, Ph.D. Student Chair of Communication
> >> and Distributed Systems RWTH Aachen University, Germany tel: +49 241
> >> 80 21426 web: http://www.comsys.rwth-aachen.de/team/rene-hummen/
> >>
> >>
> >>
> >> _______________________________________________ dtls-iot mailing
> >> list dtls-iot@ietf.org
> >> https://www.ietf.org/mailman/listinfo/dtls-iot
>
>
> --
> Dipl.-Inform. Rene Hummen, Ph.D. Student
> Chair of Communication and Distributed Systems
> RWTH Aachen University, Germany
> tel: +49 241 80 21426
> web: http://www.comsys.rwth-aachen.de/team/rene-hummen/
>
>
> _______________________________________________
> dtls-iot mailing list
> dtls-iot@ietf.org
> https://www.ietf.org/mailman/listinfo/dtls-iot
>
>

--089e01183c3644d622051119029d
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Good Evening,<div><br></div><div>This is my first message =
on this mailing list, I am a novice on the IETF world.</div><div>Just my hu=
mble opinion as a reader about the SMS-appendix:<br><div><br></div><div><sp=
an class=3D"im" style=3D"font-size:12.8000001907349px">&gt;&gt; I also beli=
eve that the text in the appendix does not disrupt<br>&gt;&gt; readability =
for others who do not care about this type of usage.<br><span style=3D"font=
-size:12.8000001907349px">&gt;</span><br></span><span style=3D"color:rgb(80=
,0,80);font-size:12.8000001907349px">&gt;</span><span style=3D"font-size:12=
.8000001907349px">That is true. I am not sure if the Appendix of the genera=
l IoT profile isn=E2=80=99t hiding this SMS-related information for interes=
ted parties.</span></div><div><span style=3D"color:rgb(80,0,80);font-size:1=
2.8000001907349px">&gt;</span><span style=3D"font-size:12.8000001907349px">=
To me, it makes more sense to have Appendix A as a separate document that r=
eferences the IoT profile. If others believe the Appendix is the way to go =
forward, I won=E2=80=99t stand in the way though.</span><br></div></div><di=
v><span style=3D"font-size:12.8000001907349px"><br></span></div><div><span =
style=3D"font-size:12.8000001907349px"><br></span></div><div><span style=3D=
"font-size:12.8000001907349px">For me it was very useful to have this infor=
mation in the appendix of=C2=A0draft-ietf-dice-profile-10.txt , otherwise I=
 doubt I will have read (draft-fossati-dtls-over-gsm-sms-01) =C2=A0it anyti=
me soon, thought the information there was very relevant to me=C2=A0</span>=
<span style=3D"font-size:12.8000001907349px">(my goal is to implement dtls =
on a non-udp datagram transport -non-ip neither-).</span></div><div><span s=
tyle=3D"font-size:12.8000001907349px"><br></span></div><div><span style=3D"=
font-size:12.8000001907349px">Thank you for all your effort on this WG.</sp=
an></div><div><span style=3D"font-size:12.8000001907349px"><br></span></div=
><div><span style=3D"font-size:12.8000001907349px">Renzo NAVAS</span></div>=
<div><br></div><div><span style=3D"font-size:12.8000001907349px"><br></span=
></div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Mon, Ma=
r 9, 2015 at 4:19 PM, Rene Hummen <span dir=3D"ltr">&lt;<a href=3D"mailto:R=
ene.Hummen@comsys.rwth-aachen.de" target=3D"_blank">Rene.Hummen@comsys.rwth=
-aachen.de</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=
=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(20=
4,204,204);border-left-style:solid;padding-left:1ex">Hi Hannes,<br>
<span class=3D""><br>
On 07 Mar 2015, at 11:08, Hannes Tschofenig &lt;<a href=3D"mailto:hannes.ts=
chofenig@gmx.net">hannes.tschofenig@gmx.net</a>&gt; wrote:<br>
&gt;&gt; 4) Section 5 (line 1025)<br>
&gt;&gt;<br>
&gt;&gt; &quot;SHA-256 is the recommended default PRF.=E2=80=9D<br>
&gt;&gt;<br>
&gt;&gt; In which document? The DTLS profile or the (D)TLS specification?<b=
r>
&gt;&gt;<br>
&gt;<br>
&gt; Actually, the story is a bit more complex since the PRF is part of the=
<br>
&gt; ciphersuite definition and while the TLS 1.2 spec says that new<br>
&gt; ciphersuites should use the SHA-256 based construction it also allows =
a<br>
&gt; ciphersuite to define else. I added extra text to the &#39;The Ciphers=
uite<br>
&gt; Concept&#39; section.<br>
<br>
</span>This flexibility in PRF selection exactly was the reason for my comm=
ent. You now discuss the use of SHA-256 for Pre-Shared Secrets, but not in =
case of Raw Public Keys and Certificates. Is there a special need to highli=
ght SHA-256 for Pre-Shared Secrets?<br>
<span class=3D""><br>
&gt; 11) Section 21 (line 2089 and below)<br>
</span><span class=3D"">&gt;&gt; &quot;Offer access to building blocks in a=
ddition (or as an alternative)<br>
&gt;&gt; to the complete functionality.=C2=A0 For example, a chip manufactu=
rer who<br>
&gt;&gt; gives developers access to the AES crypto function can use it to<b=
r>
&gt;&gt; build an efficient AES-GCM implementations.=C2=A0 Another example =
is to<br>
&gt;&gt; make a special instruction available that increases the speed of<b=
r>
&gt;&gt; speed-up carryless multiplications.=E2=80=9D<br>
&gt;&gt;<br>
&gt;&gt; Why not use ECB as a basic example of a building block?<br>
&gt;&gt;<br>
&gt; I didn&#39;t want to go too far with the recommendation about what sho=
uld be<br>
&gt; done in hardware but rather state high-level principles.<br>
<br>
</span>Ok, I just realized that re-phrasing &quot;AES crypto function=E2=80=
=9D to &quot;AES block cipher=E2=80=9D above would fix my comment.<br>
<span class=3D""><br>
&gt;&gt; 12) Appendix A (line 2673 and below)<br>
&gt;&gt;<br>
&gt;&gt; In contrast to the remaining profile, this (obviously) is very lin=
k<br>
&gt;&gt; layer specific normative text. Why not move this to a short separa=
te<br>
&gt;&gt; document?<br>
&gt;&gt;<br>
&gt;<br>
&gt; As Thomas noted the content of the appendix was actually in a separate=
<br>
&gt; document. When we presented it the recommendation was made to include =
it<br>
&gt; in here since the underlying message about the timeout values is<br>
&gt; applicable also to other radio technologies.<br>
<br>
</span>I completely agree about the integration of the timeout values. I ju=
st wonder about the rest (which now is the Appendix).<br>
<span class=3D""><br>
&gt; I also believe that the text in the appendix does not disrupt<br>
&gt; readability for others who do not care about this type of usage.<br>
<br>
</span>That is true. I am not sure if the Appendix of the general IoT profi=
le isn=E2=80=99t hiding this SMS-related information for interested parties=
. To me, it makes more sense to have Appendix A as a separate document that=
 references the IoT profile. If others believe the Appendix is the way to g=
o forward, I won=E2=80=99t stand in the way though.<br>
<br>
Otherwise, I agree with your changes.<br>
<br>
BR<br>
Ren=C3=A9<br>
<div class=3D""><div class=3D"h5"><br>
<br>
&gt;<br>
&gt; Ciao<br>
&gt; Hannes<br>
&gt;<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt; BR, Ren=C3=A9<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt; [1]<br>
&gt;&gt; <a href=3D"https://github.com/hannestschofenig/tschofenig-ids/comm=
it/37d0cfa130904dcba6c2d470f286bdb98b81e41d" target=3D"_blank">https://gith=
ub.com/hannestschofenig/tschofenig-ids/commit/37d0cfa130904dcba6c2d470f286b=
db98b81e41d</a><br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt; -- Dipl.-Inform. Rene Hummen, Ph.D. Student Chair of Communication=
<br>
&gt;&gt; and Distributed Systems RWTH Aachen University, Germany tel: +49 2=
41<br>
&gt;&gt; 80 21426 web: <a href=3D"http://www.comsys.rwth-aachen.de/team/ren=
e-hummen/" target=3D"_blank">http://www.comsys.rwth-aachen.de/team/rene-hum=
men/</a><br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt; _______________________________________________ dtls-iot mailing<b=
r>
&gt;&gt; list <a href=3D"mailto:dtls-iot@ietf.org">dtls-iot@ietf.org</a><br=
>
&gt;&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/dtls-iot" target=
=3D"_blank">https://www.ietf.org/mailman/listinfo/dtls-iot</a><br>
<br>
<br>
--<br>
Dipl.-Inform. Rene Hummen, Ph.D. Student<br>
Chair of Communication and Distributed Systems<br>
RWTH Aachen University, Germany<br>
tel: <a href=3D"tel:%2B49%20241%2080%2021426" value=3D"+492418021426">+49 2=
41 80 21426</a><br>
web: <a href=3D"http://www.comsys.rwth-aachen.de/team/rene-hummen/" target=
=3D"_blank">http://www.comsys.rwth-aachen.de/team/rene-hummen/</a><br>
<br>
</div></div><br>_______________________________________________<br>
dtls-iot mailing list<br>
<a href=3D"mailto:dtls-iot@ietf.org">dtls-iot@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/dtls-iot" target=3D"_blank=
">https://www.ietf.org/mailman/listinfo/dtls-iot</a><br>
<br></blockquote></div><br></div></div>

--089e01183c3644d622051119029d--


From nobody Sun Mar 15 12:51:41 2015
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 CE1DC1A0302; Sun, 15 Mar 2015 12:51:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 tNAMFMZd-2u8; Sun, 15 Mar 2015 12:51:37 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.22]) (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 135E01A017E; Sun, 15 Mar 2015 12:51:36 -0700 (PDT)
Received: from [192.168.131.144] ([80.92.121.102]) by mail.gmx.com (mrgmx103) with ESMTPSA (Nemesis) id 0LaGfK-1ZGifw0ElK-00m015; Sun, 15 Mar 2015 20:51:34 +0100
Message-ID: <5505E2C3.8080806@gmx.net>
Date: Sun, 15 Mar 2015 20:51:31 +0100
From: Hannes Tschofenig <hannes.tschofenig@gmx.net>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: "dtls-iot@ietf.org" <dtls-iot@ietf.org>,  "core@ietf.org WG" <core@ietf.org>
OpenPGP: id=4D776BC9
Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="w3SM3EPcHRWqmATiMrpkaaBku4tlwUa9x"
X-Provags-ID: V03:K0:Rs+fioj1ZBVbk5n14YbMjSU3OA/RUjDCL5ksE595mI+6uVfYUFG 1MHnzKUq2Wv29+PfqgmZCeM89F1Hq/APceS7fQACzMRB/14vEu7WLmJiibRIq77+oe5tbsr 2p72C9PvXA8ShUGBf9FfEag4OZwXO53g92PHlrkyX4+VRZv2FkKk4PgLeu7GJxyIIcS/3i0 cZZeQMwHdJitJ856P/+9w==
X-UI-Out-Filterresults: notjunk:1;
Archived-At: <http://mailarchive.ietf.org/arch/msg/dtls-iot/OkMgcV_70OQQ5oQDCCCy1XiGWA8>
Cc: "FOSSATI, Thomas \(Thomas\)" <thomas.fossati@alcatel-lucent.com>
Subject: [Dtls-iot] draft-fossati-core-certmode-rd-names-00
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, 15 Mar 2015 19:51:39 -0000

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

Hi all,

when Thomas and I worked on the "DTLS/TLS profile for IoT" document in
the DICE working group we ran into an issue that concerned the use of
constrained servers.

When constrained servers use the DNS and the FQDN is included in the
certificate then there is no problem. This is then pretty much how
existing Web servers work.

However, what happens if these constrained servers don't use the DNS
(which is not unlikely) then it turns out that there are various gaps in
our specification landscape.

Have a look at our write-up and let us know what you think:
https://tools.ietf.org/html/draft-fossati-core-certmode-rd-names-00

Either we were confused when we wrote the document or there is indeed a
problem.

Ciao
Hannes

PS: I am addressing the mail to DICE because the issue surfaced in the
context of the profile draft and to CORE since this is the group where
the work most likely belongs to.


--w3SM3EPcHRWqmATiMrpkaaBku4tlwUa9x
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

iQEcBAEBCgAGBQJVBeLEAAoJEGhJURNOOiAttBIH/1vAW6y1By/vmKe/+SRlVK1K
p3qGEuUtu/HepfOgV2VbLrMMPHY8QIiGBNkXwOq7nHYeUr29cu24gVj9KzVkn4pz
IWHxqPuOlMqRXdszvalYUGW354BSmlcqGraFXOGj2gxiW9oDTauMiyQPl+MHx+Ym
+B1RAjia4GbPwM0aytV4PKPYbxTP4ZeoMlnDp148GV2WT3MWYtuhFdwXq5fyHGL/
H9qSPajp4n4bH2j4OIE1nJr/Be8LcXACaXFVFDT26hteHfMDXG6UbDM8NcQopV/G
lfGroEsnQZsPAKw78C5D/J0/wDP8Xn0jd+JDO9GrxI/mdCdYwowzadueYccwDKE=
=zS+6
-----END PGP SIGNATURE-----

--w3SM3EPcHRWqmATiMrpkaaBku4tlwUa9x--


From nobody Thu Mar 26 22:11:06 2015
Return-Path: <Akbar.Rahman@interdigital.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 1B0A51A8AF3 for <dtls-iot@ietfa.amsl.com>; Thu, 26 Mar 2015 22:11:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.243
X-Spam-Level: 
X-Spam-Status: No, score=-1.243 tagged_above=-999 required=5 tests=[AC_DIV_BONANZA=0.001, BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_SOFTFAIL=0.665, T_RP_MATCHES_RCVD=-0.01] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XnhUiM8oLgwN for <dtls-iot@ietfa.amsl.com>; Thu, 26 Mar 2015 22:11:03 -0700 (PDT)
Received: from smtp-in1.interdigital.com (smtp-in1.interdigital.com [64.208.228.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 261921A8ABB for <dtls-iot@ietf.org>; Thu, 26 Mar 2015 22:11:03 -0700 (PDT)
X-ASG-Debug-ID: 1427433061-06daaa14a02f4a90001-roOjxa
Received: from KYANITE.InterDigital.com (kyanite.interdigital.com [10.1.64.253]) by smtp-in1.interdigital.com with ESMTP id 0SxpeYxB3CAZxKw5 (version=TLSv1 cipher=AES128-SHA bits=128 verify=NO); Fri, 27 Mar 2015 01:11:01 -0400 (EDT)
X-Barracuda-Envelope-From: Akbar.Rahman@InterDigital.com
Received: from KAMACITE.InterDigital.com ([fe80::9d59:a73c:8da:eb0a]) by KYANITE.InterDigital.com ([::1]) with mapi id 14.03.0210.002; Fri, 27 Mar 2015 01:11:01 -0400
From: "Rahman, Akbar" <Akbar.Rahman@InterDigital.com>
To: Zach Shelby <Zach.Shelby@arm.com>, Hannes Tschofenig <hannes.tschofenig@gmx.net>
Thread-Topic: [Dtls-iot] draft-ietf-dice-profile-10
X-ASG-Orig-Subj: RE: [Dtls-iot] draft-ietf-dice-profile-10
Thread-Index: AQHQWfmeq5jTyPP1VUSO/FHlaYmq4p0UF9GAgBvMg1A=
Date: Fri, 27 Mar 2015 05:11:00 +0000
Message-ID: <36F5869FE31AB24485E5E3222C288E1F0BB0FB2E@KAMACITE.InterDigital.com>
References: <trinity-078bdef2-9c8d-463d-a67b-08cf76b9987c-1425858175130@3capp-gmx-bs34> <ED286F38-43EF-4CAC-AD95-D3AAC33EDB52@arm.com>
In-Reply-To: <ED286F38-43EF-4CAC-AD95-D3AAC33EDB52@arm.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.1.247.3]
x-exclaimer-md-config: bb79a19d-f711-475c-a0f9-4d93b71c94dd
Content-Type: multipart/alternative; boundary="_000_36F5869FE31AB24485E5E3222C288E1F0BB0FB2EKAMACITEInterDi_"
MIME-Version: 1.0
X-Barracuda-Connect: kyanite.interdigital.com[10.1.64.253]
X-Barracuda-Start-Time: 1427433061
X-Barracuda-Encrypted: AES128-SHA
X-Barracuda-URL: https://10.1.245.3:443/cgi-mod/mark.cgi
X-Virus-Scanned: by bsmtpd at interdigital.com
X-Barracuda-BRTS-Status: 1
X-Barracuda-Spam-Score: 0.00
X-Barracuda-Spam-Status: No, SCORE=0.00 using global scores of TAG_LEVEL=1000.0 QUARANTINE_LEVEL=1000.0 KILL_LEVEL=9.0 tests=HTML_MESSAGE
X-Barracuda-Spam-Report: Code version 3.2, rules version 3.2.3.17218 Rule breakdown below pts rule name              description ---- ---------------------- -------------------------------------------------- 0.00 HTML_MESSAGE           BODY: HTML included in message
Archived-At: <http://mailarchive.ietf.org/arch/msg/dtls-iot/4S7I6pzDERhqYCodOXgDokWGIAg>
Cc: "dtls-iot@ietf.org" <dtls-iot@ietf.org>
Subject: Re: [Dtls-iot] draft-ietf-dice-profile-10
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, 27 Mar 2015 05:11:05 -0000

--_000_36F5869FE31AB24485E5E3222C288E1F0BB0FB2EKAMACITEInterDi_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

SGkgWmFjaC9IYW5uZXMsDQoNCg0KSSByZXZpZXdlZCB0aGUgbGF0ZXN0IHZlcnNpb24gb2YgdGhl
IHByb2ZpbGUgZHJhZnQgYW5kIGFsbCBteSBjb21tZW50cyBoYXZlIGJlZW4gZnVsbHkgYWRkcmVz
c2VkLiAgRnJvbSBteSBwZXJzcGVjdGl2ZSB0aGUgZG9jdW1lbnQgaXMgcmVhZHkgdG8gcHJvZ3Jl
c3MuICBUaGFua3MgZm9yIHRoZSBnb29kIHdvcmssIEhhbm5lcy4NCg0KDQpCZXN0IFJlZ2FyZHMs
DQoNCg0KQWtiYXINCg0KRnJvbTogZHRscy1pb3QgW21haWx0bzpkdGxzLWlvdC1ib3VuY2VzQGll
dGYub3JnXSBPbiBCZWhhbGYgT2YgWmFjaCBTaGVsYnkNClNlbnQ6IE1vbmRheSwgTWFyY2ggMDks
IDIwMTUgNDozOCBBTQ0KVG86IEhhbm5lcyBUc2Nob2ZlbmlnDQpDYzogZHRscy1pb3RAaWV0Zi5v
cmcNClN1YmplY3Q6IFJlOiBbRHRscy1pb3RdIGRyYWZ0LWlldGYtZGljZS1wcm9maWxlLTEwDQoN
ClRoYW5rcyB0byBNYXR0aGlhcywgQWtiYXIsIFJlbmUgYW5kIG90aGVycyBmb3IgdGhlIFdHTEMg
Y29tbWVudHMuIFBsZWFzZSBsZXQgSGFubmVzIGtub3cgaWYgaGUgaGFzIHN1ZmZpY2llbnRseSB0
YWtlbiB0aGVtIGludG8gYWNjb3VudC4NCg0KQXMgdGhlIG5leHQgc3RlcCwgSSB3aWxsIGJlIHBy
b2NlZWRpbmcgd2l0aCB0aGUgSUVTRyB3cml0ZS11cC4NCg0KQXMgbWFueSBvZiB5b3UgaGF2ZSBw
cm9iYWJseSBub3RpY2VkLCBESUNFIGlzIG5vdCBzY2hlZHVsZWQgZm9yIGEgRjJGIG1lZXRpbmcg
YXQgdGhlIERhbGxhcyBJRVRGLiBXZSBkaWQgdGhpcyBvbiBwdXJwb3NlLCB0byBiZSBhYmxlIHRv
IGZvY3VzIG9uIGZpbmlzaGluZyB0aGUgcHJvZmlsZSBhbmQgZ2V0dGluZyBpdCB0aHJvdWdoIHRo
ZSBJRVNHLiBJZiB5b3UgaGF2ZSBhbnkgcXVlc3Rpb25zIG9uIHRoYXQgZG9uJ3QgaGVzaXRhdGUg
dG8gYXNrIG1lIGRpcmVjdGx5Lg0KDQpSZWdhcmRzLA0KWmFjaA0KDQpPbiBNYXIgOSwgMjAxNSwg
YXQgMTo0MiBBTSwgSGFubmVzIFRzY2hvZmVuaWcgPGhhbm5lcy50c2Nob2ZlbmlnQGdteC5uZXQ8
bWFpbHRvOmhhbm5lcy50c2Nob2ZlbmlnQGdteC5uZXQ+PiB3cm90ZToNCg0KDQpWZXJzaW9uIC0x
MCBvZiB0aGUgcHJvZmlsZSBkcmFmdCBhZGRyZXNzZXMgdGhlIHdvcmtpbmcgZ3JvdXAgbGFzdCBj
YWxsIHJldmlldyBjb21tZW50cy4gSSB3b3VsZCBzdGlsbCBsaWtlIHRvIGhlYXIgZnJvbSB0aGUg
cmV2aWV3ZXJzIHdoZXRoZXIgdGhleSBhcmUgZmluZSB3aXRoIHRoZSBjaGFuZ2VzIEkgaGF2ZSBt
YWRlIGluIHJlc3BvbnNlIHRvIHRoZWlyIGZlZWRiYWNrLg0KDQpDaWFvDQpIYW5uZXMNCg0KX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCmR0bHMtaW90IG1h
aWxpbmcgbGlzdA0KZHRscy1pb3RAaWV0Zi5vcmc8bWFpbHRvOmR0bHMtaW90QGlldGYub3JnPg0K
aHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9kdGxzLWlvdA0KDQpaYWNoIFNo
ZWxieQ0KVmljZSBQcmVzaWRlbnQsIE1hcmtldGluZw0KQVJNIEludGVybmV0IG9mIFRoaW5ncyBC
VQ0Kd3d3LmFybS5jb208aHR0cDovL3d3dy5hcm0uY29tPg0KVVM6ICsxICg0MDgpIDIwMy05NDM0
DQpGaW5sYW5kOiArMzU4IDQwNzc5NjI5Nw0KU2t5cGU6IHpkc2hlbGJ5DQpMaW5rZWRJbjogZmku
bGlua2VkaW4uY29tL2luL3phY2hzaGVsYnkvPGh0dHA6Ly9maS5saW5rZWRpbi5jb20vaW4vemFj
aHNoZWxieS8+DQoNCg0KLS0gSU1QT1JUQU5UIE5PVElDRTogVGhlIGNvbnRlbnRzIG9mIHRoaXMg
ZW1haWwgYW5kIGFueSBhdHRhY2htZW50cyBhcmUgY29uZmlkZW50aWFsIGFuZCBtYXkgYWxzbyBi
ZSBwcml2aWxlZ2VkLiBJZiB5b3UgYXJlIG5vdCB0aGUgaW50ZW5kZWQgcmVjaXBpZW50LCBwbGVh
c2Ugbm90aWZ5IHRoZSBzZW5kZXIgaW1tZWRpYXRlbHkgYW5kIGRvIG5vdCBkaXNjbG9zZSB0aGUg
Y29udGVudHMgdG8gYW55IG90aGVyIHBlcnNvbiwgdXNlIGl0IGZvciBhbnkgcHVycG9zZSwgb3Ig
c3RvcmUgb3IgY29weSB0aGUgaW5mb3JtYXRpb24gaW4gYW55IG1lZGl1bS4gVGhhbmsgeW91Lg0K
DQpBUk0gTGltaXRlZCwgUmVnaXN0ZXJlZCBvZmZpY2UgMTEwIEZ1bGJvdXJuIFJvYWQsIENhbWJy
aWRnZSBDQjEgOU5KLCBSZWdpc3RlcmVkIGluIEVuZ2xhbmQgJiBXYWxlcywgQ29tcGFueSBObzog
MjU1NzU5MA0KQVJNIEhvbGRpbmdzIHBsYywgUmVnaXN0ZXJlZCBvZmZpY2UgMTEwIEZ1bGJvdXJu
IFJvYWQsIENhbWJyaWRnZSBDQjEgOU5KLCBSZWdpc3RlcmVkIGluIEVuZ2xhbmQgJiBXYWxlcywg
Q29tcGFueSBObzogMjU0ODc4Mg0K

--_000_36F5869FE31AB24485E5E3222C288E1F0BB0FB2EKAMACITEInterDi_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjwhLS0gVGVtcGxhdGUgZ2VuZXJhdGVkIGJ5IEV4Y2xh
aW1lciBTaWduYXR1cmUgTWFuYWdlciBFeGNoYW5nZSBFZGl0aW9uIG9uIDAxOjExOjAxIEZyaWRh
eSwgMjcgTWFyY2ggMjAxNSAtLT4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIgY29u
dGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxzdHlsZSB0eXBlPSJ0ZXh0L2NzcyI+
UC5JbXByaW50VW5pcXVlSUQgew0KCU1BUkdJTjogMGNtIDBjbSAwcHQNCn0NCkxJLkltcHJpbnRV
bmlxdWVJRCB7DQoJTUFSR0lOOiAwY20gMGNtIDBwdA0KfQ0KRElWLkltcHJpbnRVbmlxdWVJRCB7
DQoJTUFSR0lOOiAwY20gMGNtIDBwdA0KfQ0KVEFCTEUuSW1wcmludFVuaXF1ZUlEVGFibGUgew0K
CU1BUkdJTjogMGNtIDBjbSAwcHQNCn0NCkRJVi5TZWN0aW9uMSB7DQoJcGFnZTogU2VjdGlvbjEN
Cn0NCjwvc3R5bGU+DQo8bWV0YSBuYW1lPSJHZW5lcmF0b3IiIGNvbnRlbnQ9Ik1pY3Jvc29mdCBX
b3JkIDE1IChmaWx0ZXJlZCBtZWRpdW0pIj4NCjxzdHlsZT48IS0tDQovKiBGb250IERlZmluaXRp
b25zICovDQpAZm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5OkhlbHZldGljYTsNCglwYW5vc2UtMToy
IDExIDYgNCAyIDIgMiAyIDIgNDt9DQpAZm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5OiJDYW1icmlh
IE1hdGgiOw0KCXBhbm9zZS0xOjIgNCA1IDMgNSA0IDYgMyAyIDQ7fQ0KQGZvbnQtZmFjZQ0KCXtm
b250LWZhbWlseTpDYWxpYnJpOw0KCXBhbm9zZS0xOjIgMTUgNSAyIDIgMiA0IDMgMiA0O30NCkBm
b250LWZhY2UNCgl7Zm9udC1mYW1pbHk6VmVyZGFuYTsNCglwYW5vc2UtMToyIDExIDYgNCAzIDUg
NCA0IDIgNDt9DQovKiBTdHlsZSBEZWZpbml0aW9ucyAqLw0KcC5Nc29Ob3JtYWwsIGxpLk1zb05v
cm1hbCwgZGl2Lk1zb05vcm1hbA0KCXttYXJnaW46MGluOw0KCW1hcmdpbi1ib3R0b206LjAwMDFw
dDsNCglmb250LXNpemU6MTIuMHB0Ow0KCWZvbnQtZmFtaWx5OiJUaW1lcyBOZXcgUm9tYW4iLHNl
cmlmO30NCmE6bGluaywgc3Bhbi5Nc29IeXBlcmxpbmsNCgl7bXNvLXN0eWxlLXByaW9yaXR5Ojk5
Ow0KCWNvbG9yOmJsdWU7DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVybGluZTt9DQphOnZpc2l0ZWQs
IHNwYW4uTXNvSHlwZXJsaW5rRm9sbG93ZWQNCgl7bXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0KCWNv
bG9yOnB1cnBsZTsNCgl0ZXh0LWRlY29yYXRpb246dW5kZXJsaW5lO30NCnNwYW4uRW1haWxTdHls
ZTE3DQoJe21zby1zdHlsZS10eXBlOnBlcnNvbmFsLXJlcGx5Ow0KCWZvbnQtZmFtaWx5OiJDYWxp
YnJpIixzYW5zLXNlcmlmOw0KCWNvbG9yOiMxRjQ5N0Q7fQ0KLk1zb0NocERlZmF1bHQNCgl7bXNv
LXN0eWxlLXR5cGU6ZXhwb3J0LW9ubHk7DQoJZm9udC1zaXplOjEwLjBwdDt9DQpAcGFnZSBXb3Jk
U2VjdGlvbjENCgl7c2l6ZTo4LjVpbiAxMS4waW47DQoJbWFyZ2luOjEuMGluIDEuMGluIDEuMGlu
IDEuMGluO30NCmRpdi5Xb3JkU2VjdGlvbjENCgl7cGFnZTpXb3JkU2VjdGlvbjE7fQ0KLS0+PC9z
dHlsZT48IS0tW2lmIGd0ZSBtc28gOV0+PHhtbD4NCjxvOnNoYXBlZGVmYXVsdHMgdjpleHQ9ImVk
aXQiIHNwaWRtYXg9IjEwMjYiIC8+DQo8L3htbD48IVtlbmRpZl0tLT48IS0tW2lmIGd0ZSBtc28g
OV0+PHhtbD4NCjxvOnNoYXBlbGF5b3V0IHY6ZXh0PSJlZGl0Ij4NCjxvOmlkbWFwIHY6ZXh0PSJl
ZGl0IiBkYXRhPSIxIiAvPg0KPC9vOnNoYXBlbGF5b3V0PjwveG1sPjwhW2VuZGlmXS0tPg0KPC9o
ZWFkPg0KPGJvZHkgbGFuZz0iRU4tVVMiIGxpbms9ImJsdWUiIHZsaW5rPSJwdXJwbGUiPg0KPHA+
PC9wPg0KPGRpdiBjbGFzcz0iV29yZFNlY3Rpb24xIj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxz
cGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVv
dDssc2Fucy1zZXJpZjtjb2xvcjojMUY0OTdEIj5IaSBaYWNoL0hhbm5lcyw8bzpwPjwvbzpwPjwv
c3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEx
LjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6IzFG
NDk3RCI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+
PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZx
dW90OyxzYW5zLXNlcmlmO2NvbG9yOiMxRjQ5N0QiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwv
cD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2Zv
bnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjojMUY0OTdEIj5J
IHJldmlld2VkIHRoZSBsYXRlc3QgdmVyc2lvbiBvZiB0aGUgcHJvZmlsZSBkcmFmdCBhbmQgYWxs
IG15IGNvbW1lbnRzIGhhdmUgYmVlbiBmdWxseSBhZGRyZXNzZWQuJm5ic3A7IEZyb20gbXkgcGVy
c3BlY3RpdmUgdGhlIGRvY3VtZW50IGlzIHJlYWR5IHRvIHByb2dyZXNzLiZuYnNwOyBUaGFua3MN
CiBmb3IgdGhlIGdvb2Qgd29yaywgSGFubmVzLjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5
OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjojMUY0OTdEIj48bzpwPiZuYnNw
OzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9u
dC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWY7
Y29sb3I6IzFGNDk3RCI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1z
b05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7
Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOiMxRjQ5N0QiPkJlc3QgUmVnYXJkcyw8bzpw
PjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9u
dC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWY7
Y29sb3I6IzFGNDk3RCI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1z
b05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7
Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOiMxRjQ5N0QiPjxvOnA+Jm5ic3A7PC9vOnA+
PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6
MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjoj
MUY0OTdEIj5Ba2JhcjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
PjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkm
cXVvdDssc2Fucy1zZXJpZjtjb2xvcjojMUY0OTdEIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48
L3A+DQo8ZGl2Pg0KPGRpdiBzdHlsZT0iYm9yZGVyOm5vbmU7Ym9yZGVyLXRvcDpzb2xpZCAjRTFF
MUUxIDEuMHB0O3BhZGRpbmc6My4wcHQgMGluIDBpbiAwaW4iPg0KPHAgY2xhc3M9Ik1zb05vcm1h
bCI+PGI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2Fs
aWJyaSZxdW90OyxzYW5zLXNlcmlmIj5Gcm9tOjwvc3Bhbj48L2I+PHNwYW4gc3R5bGU9ImZvbnQt
c2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmIj4g
ZHRscy1pb3QgW21haWx0bzpkdGxzLWlvdC1ib3VuY2VzQGlldGYub3JnXQ0KPGI+T24gQmVoYWxm
IE9mIDwvYj5aYWNoIFNoZWxieTxicj4NCjxiPlNlbnQ6PC9iPiBNb25kYXksIE1hcmNoIDA5LCAy
MDE1IDQ6MzggQU08YnI+DQo8Yj5Ubzo8L2I+IEhhbm5lcyBUc2Nob2ZlbmlnPGJyPg0KPGI+Q2M6
PC9iPiBkdGxzLWlvdEBpZXRmLm9yZzxicj4NCjxiPlN1YmplY3Q6PC9iPiBSZTogW0R0bHMtaW90
XSBkcmFmdC1pZXRmLWRpY2UtcHJvZmlsZS0xMDxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2
Pg0KPC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxk
aXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5UaGFua3MgdG8gTWF0dGhpYXMsIEFrYmFyLCBSZW5l
IGFuZCBvdGhlcnMgZm9yIHRoZSBXR0xDIGNvbW1lbnRzLiBQbGVhc2UgbGV0IEhhbm5lcyBrbm93
IGlmIGhlIGhhcyBzdWZmaWNpZW50bHkgdGFrZW4gdGhlbSBpbnRvIGFjY291bnQuPG86cD48L286
cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwv
bzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPkFzIHRoZSBuZXh0
IHN0ZXAsIEkgd2lsbCBiZSBwcm9jZWVkaW5nIHdpdGggdGhlIElFU0cgd3JpdGUtdXAuPG86cD48
L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNw
OzwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPkFzIG1hbnkg
b2YgeW91IGhhdmUgcHJvYmFibHkgbm90aWNlZCwgRElDRSBpcyBub3Qgc2NoZWR1bGVkIGZvciBh
IEYyRiBtZWV0aW5nIGF0IHRoZSBEYWxsYXMgSUVURi4gV2UgZGlkIHRoaXMgb24gcHVycG9zZSwg
dG8gYmUgYWJsZSB0byBmb2N1cyBvbiBmaW5pc2hpbmcgdGhlIHByb2ZpbGUgYW5kIGdldHRpbmcg
aXQgdGhyb3VnaCB0aGUgSUVTRy4gSWYgeW91IGhhdmUgYW55IHF1ZXN0aW9ucyBvbiB0aGF0IGRv
bid0DQogaGVzaXRhdGUgdG8gYXNrIG1lIGRpcmVjdGx5LjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+
DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rp
dj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5SZWdhcmRzLDxvOnA+PC9vOnA+PC9wPg0K
PC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+WmFjaDxvOnA+PC9vOnA+PC9wPg0K
PC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxkaXY+
DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+T24gTWFyIDksIDIwMTUsIGF0IDE6NDIgQU0s
IEhhbm5lcyBUc2Nob2ZlbmlnICZsdDs8YSBocmVmPSJtYWlsdG86aGFubmVzLnRzY2hvZmVuaWdA
Z214Lm5ldCI+aGFubmVzLnRzY2hvZmVuaWdAZ214Lm5ldDwvYT4mZ3Q7IHdyb3RlOjxvOnA+PC9v
OnA+PC9wPg0KPC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48YnI+DQo8YnI+DQo8bzpwPjwv
bzpwPjwvcD4NCjxibG9ja3F1b3RlIHN0eWxlPSJtYXJnaW4tdG9wOjUuMHB0O21hcmdpbi1ib3R0
b206NS4wcHQiPg0KPGRpdj4NCjxkaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNw
YW4gc3R5bGU9ImZvbnQtc2l6ZTo5LjBwdDtmb250LWZhbWlseTomcXVvdDtWZXJkYW5hJnF1b3Q7
LHNhbnMtc2VyaWYiPlZlcnNpb24gLTEwIG9mIHRoZSBwcm9maWxlIGRyYWZ0IGFkZHJlc3NlcyB0
aGUgd29ya2luZyBncm91cCBsYXN0IGNhbGwgcmV2aWV3IGNvbW1lbnRzLiZuYnNwO0kgd291bGQg
c3RpbGwgbGlrZSB0byBoZWFyIGZyb20gdGhlIHJldmlld2VycyB3aGV0aGVyIHRoZXkgYXJlIGZp
bmUgd2l0aCB0aGUgY2hhbmdlcw0KIEkgaGF2ZSBtYWRlIGluIHJlc3BvbnNlIHRvIHRoZWlyIGZl
ZWRiYWNrLiZuYnNwOzxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6OS4wcHQ7Zm9udC1mYW1pbHk6
JnF1b3Q7VmVyZGFuYSZxdW90OyxzYW5zLXNlcmlmIj4mbmJzcDs8bzpwPjwvbzpwPjwvc3Bhbj48
L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9u
dC1zaXplOjkuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O1ZlcmRhbmEmcXVvdDssc2Fucy1zZXJpZiI+
Q2lhbzxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29O
b3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6OS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7VmVy
ZGFuYSZxdW90OyxzYW5zLXNlcmlmIj5IYW5uZXM8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rp
dj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjku
MHB0O2ZvbnQtZmFtaWx5OiZxdW90O1ZlcmRhbmEmcXVvdDssc2Fucy1zZXJpZiI+Jm5ic3A7PG86
cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1z
b05vcm1hbCI+X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX188
YnI+DQpkdGxzLWlvdCBtYWlsaW5nIGxpc3Q8YnI+DQo8YSBocmVmPSJtYWlsdG86ZHRscy1pb3RA
aWV0Zi5vcmciPmR0bHMtaW90QGlldGYub3JnPC9hPjxicj4NCjxhIGhyZWY9Imh0dHBzOi8vd3d3
LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vZHRscy1pb3QiPmh0dHBzOi8vd3d3LmlldGYub3Jn
L21haWxtYW4vbGlzdGluZm8vZHRscy1pb3Q8L2E+PG86cD48L286cD48L3A+DQo8L2Jsb2NrcXVv
dGU+DQo8L2Rpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0K
PGRpdj4NCjxkaXY+DQo8ZGl2Pg0KPGRpdj4NCjxkaXY+DQo8ZGl2Pg0KPGRpdj4NCjxkaXY+DQo8
ZGl2Pg0KPGRpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9u
dC1zaXplOjEzLjVwdDtmb250LWZhbWlseTomcXVvdDtIZWx2ZXRpY2EmcXVvdDssc2Fucy1zZXJp
Zjtjb2xvcjpibGFjayI+WmFjaCBTaGVsYnk8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4N
CjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEzLjVw
dDtmb250LWZhbWlseTomcXVvdDtIZWx2ZXRpY2EmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjpibGFj
ayI+VmljZSBQcmVzaWRlbnQsIE1hcmtldGluZzxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2
Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTMu
NXB0O2ZvbnQtZmFtaWx5OiZxdW90O0hlbHZldGljYSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOmJs
YWNrIj5BUk0gSW50ZXJuZXQgb2YgVGhpbmdzIEJVPG86cD48L286cD48L3NwYW4+PC9wPg0KPC9k
aXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZTox
My41cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7SGVsdmV0aWNhJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6
YmxhY2siPjxhIGhyZWY9Imh0dHA6Ly93d3cuYXJtLmNvbSI+d3d3LmFybS5jb208L2E+PG86cD48
L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNw
YW4gc3R5bGU9ImZvbnQtc2l6ZToxMy41cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7SGVsdmV0aWNhJnF1
b3Q7LHNhbnMtc2VyaWY7Y29sb3I6YmxhY2siPlVTOiZuYnNwOyYjNDM7MSAoNDA4KSAyMDMtOTQz
NDxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3Jt
YWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTMuNXB0O2ZvbnQtZmFtaWx5OiZxdW90O0hlbHZl
dGljYSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOmJsYWNrIj5GaW5sYW5kOiAmIzQzOzM1OCA0MDc3
OTYyOTc8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEzLjVwdDtmb250LWZhbWlseTomcXVvdDtI
ZWx2ZXRpY2EmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjpibGFjayI+U2t5cGU6IHpkc2hlbGJ5PG86
cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+
PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMy41cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7SGVsdmV0aWNh
JnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6YmxhY2siPkxpbmtlZEluOiZuYnNwOzxhIG5hbWU9Indl
YlByb2ZpbGVVUkwiPjwvYT48YSBocmVmPSJodHRwOi8vZmkubGlua2VkaW4uY29tL2luL3phY2hz
aGVsYnkvIiB0aXRsZT0iVmlldyBwdWJsaWMgcHJvZmlsZSI+ZmkubGlua2VkaW4uY29tL2luL3ph
Y2hzaGVsYnkvPC9hPjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rp
dj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2
Pg0KPC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48YnI+DQo8YnI+DQo8c3BhbiBzdHlsZT0i
Zm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90OyxzYW5zLXNlcmlm
O2NvbG9yOmJsYWNrIj4tLSBJTVBPUlRBTlQgTk9USUNFOiBUaGUgY29udGVudHMgb2YgdGhpcyBl
bWFpbCBhbmQgYW55IGF0dGFjaG1lbnRzIGFyZSBjb25maWRlbnRpYWwgYW5kIG1heSBhbHNvIGJl
IHByaXZpbGVnZWQuIElmIHlvdSBhcmUgbm90IHRoZSBpbnRlbmRlZCByZWNpcGllbnQsIHBsZWFz
ZSBub3RpZnkgdGhlIHNlbmRlciBpbW1lZGlhdGVseQ0KIGFuZCBkbyBub3QgZGlzY2xvc2UgdGhl
IGNvbnRlbnRzIHRvIGFueSBvdGhlciBwZXJzb24sIHVzZSBpdCBmb3IgYW55IHB1cnBvc2UsIG9y
IHN0b3JlIG9yIGNvcHkgdGhlIGluZm9ybWF0aW9uIGluIGFueSBtZWRpdW0uIFRoYW5rIHlvdS48
YnI+DQo8YnI+DQpBUk0gTGltaXRlZCwgUmVnaXN0ZXJlZCBvZmZpY2UgMTEwIEZ1bGJvdXJuIFJv
YWQsIENhbWJyaWRnZSBDQjEgOU5KLCBSZWdpc3RlcmVkIGluIEVuZ2xhbmQgJmFtcDsgV2FsZXMs
IENvbXBhbnkgTm86IDI1NTc1OTA8YnI+DQpBUk0gSG9sZGluZ3MgcGxjLCBSZWdpc3RlcmVkIG9m
ZmljZSAxMTAgRnVsYm91cm4gUm9hZCwgQ2FtYnJpZGdlIENCMSA5TkosIFJlZ2lzdGVyZWQgaW4g
RW5nbGFuZCAmYW1wOyBXYWxlcywgQ29tcGFueSBObzogMjU0ODc4Mjwvc3Bhbj48bzpwPjwvbzpw
PjwvcD4NCjwvZGl2Pg0KPHA+PC9wPg0KPC9ib2R5Pg0KPC9odG1sPg0K

--_000_36F5869FE31AB24485E5E3222C288E1F0BB0FB2EKAMACITEInterDi_--


From nobody Fri Mar 27 09:41:23 2015
Return-Path: <sandeep.kumar@philips.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 D39D41A871F for <dtls-iot@ietfa.amsl.com>; Fri, 27 Mar 2015 09:41:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.001
X-Spam-Level: 
X-Spam-Status: No, score=-0.001 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, HTML_MESSAGE=0.001, SPF_HELO_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 yNIajwv-UYFX for <dtls-iot@ietfa.amsl.com>; Fri, 27 Mar 2015 09:41:13 -0700 (PDT)
Received: from emea01-am1-obe.outbound.protection.outlook.com (mail-am1on0738.outbound.protection.outlook.com [IPv6:2a01:111:f400:fe00::738]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5905F1A03B3 for <dtls-iot@ietf.org>; Fri, 27 Mar 2015 09:41:12 -0700 (PDT)
Received: from DB4PR04CA0035.eurprd04.prod.outlook.com (25.160.41.45) by DB4PR04MB316.eurprd04.prod.outlook.com (10.141.239.155) with Microsoft SMTP Server (TLS) id 15.1.125.19; Fri, 27 Mar 2015 16:40:53 +0000
Received: from AM1FFO11FD034.protection.gbl (2a01:111:f400:7e00::179) by DB4PR04CA0035.outlook.office365.com (2a01:111:e400:9852::45) with Microsoft SMTP Server (TLS) id 15.1.125.19 via Frontend Transport; Fri, 27 Mar 2015 16:40:53 +0000
Received: from mail.philips.com (206.191.240.52) by AM1FFO11FD034.mail.protection.outlook.com (10.174.64.223) with Microsoft SMTP Server (TLS) id 15.1.125.13 via Frontend Transport; Fri, 27 Mar 2015 16:40:51 +0000
Received: from DBXPRD9003MB059.MGDPHG.emi.philips.com ([169.254.7.249]) by DBXPRD9003HT001.MGDPHG.emi.philips.com ([141.251.25.206]) with mapi id 14.16.0478.000; Fri, 27 Mar 2015 16:40:50 +0000
From: "Kumar, Sandeep" <sandeep.kumar@philips.com>
To: "dtls-iot@ietf.org" <dtls-iot@ietf.org>
Thread-Topic: DTLS profle draft
Thread-Index: AdBorLS0hF64MofQTFG3djGz9Za+fg==
Date: Fri, 27 Mar 2015 16:40:50 +0000
Message-ID: <BE6D13F6A4554947952B39008B0DC0155202032F@DBXPRD9003MB059.MGDPHG.emi.philips.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [31.133.164.65]
Content-Type: multipart/alternative; boundary="_000_BE6D13F6A4554947952B39008B0DC0155202032FDBXPRD9003MB059_"
MIME-Version: 1.0
X-EOPAttributedMessage: 0
Received-SPF: None (protection.outlook.com: philips.com does not designate permitted sender hosts)
Authentication-Results: spf=none (sender IP is 206.191.240.52) smtp.mailfrom=sandeep.kumar@philips.com; ietf.org; dkim=none (message not signed) header.d=none;
X-Forefront-Antispam-Report: CIP:206.191.240.52; CTRY:US; IPV:NLI; EFV:NLI; BMV:1; SFV:NSPM; SFS:(10019020)(6009001)(428002)(189002)(51914003)(199003)(6806004)(84326002)(101416001)(110136001)(2351001)(16236675004)(54356999)(86362001)(229853001)(104016003)(19625215002)(105586002)(106466001)(19580395003)(15975445007)(33656002)(2656002)(46102003)(87936001)(66066001)(2930100002)(2501003)(19300405004)(2920100001)(2900100001)(55846006)(512954002)(77156002)(92566002)(62966003)(102836002)(50986999)(567094001); DIR:OUT; SFP:1102; SCL:1; SRVR:DB4PR04MB316; H:mail.philips.com; FPR:; SPF:None; MLV:sfv; MX:1; A:1; LANG:en; 
X-Microsoft-Antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:DB4PR04MB316;
X-Microsoft-Antispam-PRVS: <DB4PR04MB316307A63A3E2BF7AF6D822E4090@DB4PR04MB316.eurprd04.prod.outlook.com>
X-Exchange-Antispam-Report-Test: UriScan:;
X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(601004)(5005006)(5002010); SRVR:DB4PR04MB316; BCL:0; PCL:0; RULEID:; SRVR:DB4PR04MB316; 
X-Forefront-PRVS: 0528942FD8
X-OriginatorOrg: philips.com
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 27 Mar 2015 16:40:51.1730 (UTC)
X-MS-Exchange-CrossTenant-Id: 1a407a2d-7675-4d17-8692-b3ac285306e4
X-MS-Exchange-CrossTenant-OriginalAttributedTenantConnectingIp: TenantId=1a407a2d-7675-4d17-8692-b3ac285306e4; Ip=[206.191.240.52];  Helo=[mail.philips.com]
X-MS-Exchange-CrossTenant-FromEntityHeader: HybridOnPrem
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DB4PR04MB316
Archived-At: <http://mailarchive.ietf.org/arch/msg/dtls-iot/0NCBYqFnXJNDXwOGVN1J81XTyrY>
Cc: "Hannes Tschofenig \(Hannes.Tschofenig@gmx.net\)" <Hannes.Tschofenig@gmx.net>
Subject: [Dtls-iot] DTLS profle draft
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, 27 Mar 2015 16:41:20 -0000

--_000_BE6D13F6A4554947952B39008B0DC0155202032FDBXPRD9003MB059_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable


Hi Hannes and Thomas

Thanks for the well-written document and taking into consideration all the =
comments.

However would like one final clarification:
Sec 6 states: "TLS server MUST return the decryption_error error message
   instead of the unknown_psk_identity since the two mechanisms exist
   and provide the same functionality."

However Sec 2 of RFC4279 states: "Alternatively, if the
   server wishes to hide the fact that the PSK identity was not known,
   it MAY continue the protocol as if the PSK identity existed but the
   key was incorrect: that is, respond with a "decrypt_error" alert."

Is the assumption that the server MUST continue the handshake if the psk_id=
entity is not known and send the decryption_error on the Finished message?
Is that not opening up options for a DoS attacks on a constrained server?

----
Some other minor things that could be fixed:


-          The Fig4  client_certificate_type and server_certificate_type  c=
an be shown clearly as extensions similar to as in Fig 8.



-          In Sec 4.2 Discovery and Reachability:
".....  Once it as been discovered,...."
as -> has


-          In Sec 6.1 mentions client identity but I guess you are referrin=
g to the PSK identity



-          Sec 9: "For cases where the server is constrained (but not the c=
lient) the client MUST implement RFC 5077"

Wondering how useful the mandatory statement is since "constrained" itself =
is a vague term.


-          Figure 11: shows 128 symmetric  and  283 bit-length ECC, but I c=
ould not find this relationship in the ENISA-2014 document. I have only see=
n it mapped to 256-bits. Wondering if this is a typo.


Overall great work.

Regards
Sandeep

Dr. Sandeep S. Kumar
Senior Scientist,
Data Science department,
Philips Research,
HTC36.p.22 Eindhoven, The Netherlands.


________________________________
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_BE6D13F6A4554947952B39008B0DC0155202032FDBXPRD9003MB059_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	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.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.5in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:323969909;
	mso-list-type:hybrid;
	mso-list-template-ids:-1601400794 1769274458 67698691 67698693 67698689 67=
698691 67698693 67698689 67698691 67698693;}
@list l0:level1
	{mso-level-number-format:bullet;
	mso-level-text:-;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Calibri","sans-serif";
	mso-fareast-font-family:Calibri;}
@list l0:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l0:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l0:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l0:level5
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l0:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l0:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l0:level8
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l0:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Hi Hannes and Thomas<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Thanks for the well-written document and taking into=
 consideration all the comments.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">However would like one final clarification:<o:p></o:=
p></p>
<p class=3D"MsoNormal">Sec 6 states: &#8220;TLS server MUST return the decr=
yption_error error message<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp; instead of the unknown_psk_identity sin=
ce the two mechanisms exist<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp; and provide the same functionality.&#82=
21;<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">However Sec 2 of RFC4279 states: &#8220;Alternativel=
y, if the<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp; server wishes to hide the fact that the=
 PSK identity was not known,<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp; it MAY continue the protocol as if the =
PSK identity existed but the<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp; key was incorrect: that is, respond wit=
h a &quot;decrypt_error&quot; alert.&#8221;<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Is the assumption that the server MUST continue the =
handshake if the psk_identity is not known and send the decryption_error on=
 the Finished message?<o:p></o:p></p>
<p class=3D"MsoNormal">Is that not opening up options for a DoS attacks on =
a constrained server?<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">----<o:p></o:p></p>
<p class=3D"MsoNormal">Some other minor things that could be fixed: <o:p></=
o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l0 level=
1 lfo1"><![if !supportLists]><span style=3D"mso-list:Ignore">-<span style=
=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;
</span></span><![endif]>The Fig4 &nbsp;client_certificate_type and server_c=
ertificate_type &nbsp;can be shown clearly as extensions similar to as in F=
ig 8.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l0 level=
1 lfo1"><![if !supportLists]><span style=3D"mso-list:Ignore">-<span style=
=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;
</span></span><![endif]>In Sec 4.2 Discovery and Reachability:<o:p></o:p></=
p>
<p class=3D"MsoNormal" style=3D"text-indent:.5in">&#8220;&#8230;..&nbsp; On=
ce it as been discovered,&#8230;.&#8221;<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in">as -&gt; has<o:p></o:p></=
p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l0 level=
1 lfo1"><![if !supportLists]><span style=3D"mso-list:Ignore">-<span style=
=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;
</span></span><![endif]>In Sec 6.1 mentions client identity but I guess you=
 are referring to the PSK identity<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l0 level=
1 lfo1"><![if !supportLists]><span style=3D"mso-list:Ignore">-<span style=
=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;
</span></span><![endif]>Sec 9: &#8220;For cases where the server is constra=
ined (but not the client) the client MUST implement RFC 5077&#8221;<o:p></o=
:p></p>
<p class=3D"MsoListParagraph">Wondering how useful the mandatory statement =
is since &#8220;constrained&#8221; itself is a vague term.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l0 level=
1 lfo1"><![if !supportLists]><span style=3D"mso-list:Ignore">-<span style=
=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;
</span></span><![endif]>Figure 11: shows 128 symmetric&nbsp; and &nbsp;283 =
bit-length ECC, but I could not find this relationship in the ENISA-2014 do=
cument. I have only seen it mapped to 256-bits. Wondering if this is a typo=
.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Overall great work.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Regards<o:p></o:p></p>
<p class=3D"MsoNormal">Sandeep<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Dr. Sandeep S. Kumar<o:p></o:p></p>
<p class=3D"MsoNormal">Senior Scientist,<o:p></o:p></p>
<p class=3D"MsoNormal">Data Science department,<o:p></o:p></p>
<p class=3D"MsoNormal">Philips Research,<o:p></o:p></p>
<p class=3D"MsoNormal">HTC36.p.22 Eindhoven, The Netherlands.<o:p></o:p></p=
>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<br>
<hr>
<font face=3D"Arial" color=3D"Gray" size=3D"1">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.<br>
</font>
</body>
</html>

--_000_BE6D13F6A4554947952B39008B0DC0155202032FDBXPRD9003MB059_--


From nobody Mon Mar 30 08:04:57 2015
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 CFB551ACDDC for <dtls-iot@ietfa.amsl.com>; Mon, 30 Mar 2015 08:04:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 TicGC0iULwHg for <dtls-iot@ietfa.amsl.com>; Mon, 30 Mar 2015 08:04:54 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.22]) (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 BC24D1AC40E for <dtls-iot@ietf.org>; Mon, 30 Mar 2015 08:04:53 -0700 (PDT)
Received: from [192.168.131.145] ([80.92.114.249]) by mail.gmx.com (mrgmx103) with ESMTPSA (Nemesis) id 0MCtLD-1YldfU1Zq7-009cuD for <dtls-iot@ietf.org>; Mon, 30 Mar 2015 17:04:51 +0200
Message-ID: <55196612.9060004@gmx.net>
Date: Mon, 30 Mar 2015 17:04:50 +0200
From: Hannes Tschofenig <hannes.tschofenig@gmx.net>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: "dtls-iot@ietf.org" <dtls-iot@ietf.org>
OpenPGP: id=4D776BC9
Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="sItQdiJUgpbflSS30NaaiJiGgxDv8538f"
X-Provags-ID: V03:K0:31Y6fb0ovdJgE5/iBEtNIfbzrOvIWA/+3OO/Dvaso34AGaqkya+ UinHw/7Ldx/+vyV1ty7IH3QAoSEE4m+Mjau+fbuJPxzvjqRXKsPTuchyeUY/+mUFKdM2EGc mYJpFru16/wOEQxyKi+1HElWt4STA3G4WJBE2gVQTUXMh8Luy/CXK/SjBuEzMklJa85Z/8e xEpUwc247xtz64MleQqrg==
X-UI-Out-Filterresults: notjunk:1;
Archived-At: <http://mailarchive.ietf.org/arch/msg/dtls-iot/gp4vGFxn3r7MjmbvbsW0Xi7ujPM>
Subject: [Dtls-iot] Certificate Profiling
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: Mon, 30 Mar 2015 15:04:56 -0000

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

Hi all,

Section 6.3 of draft-ietf-dice-profile-10 discusses the recommendations
for use with certificates.
While the current text restricts the use of certificates quite a bit I
got feedback that the current text still leaves several aspects untouched=
=2E

Here is a proposal of further recommendations:

* TLS/DTLS offers a lot of freedom for using ECC curves. I would suggest
to restrict the use of RFC4492-defined ECC ciphersuites to named curves
only.

We could furthermore say that the current recommendation is to use
secp256r1 since this is also what is recommended in CoAP. Furthermore,
the CoAP specification recommends the use of uncompressed points.

We should note that standardization for Curve25519 (for ECDHE) is
ongoing (see draft-irtf-cfrg-curves-01) and support for it will likely
be required in the near future.

=46rom the content in Table 1 it should be obviously that the used ECDSA
keys in a certificate are signed with with an ECDSA and that's true not
only for the end-entity certificates but all other certificates in the
chain, including the CA certs have to have that property. There are
various types of algorithms that are used for digital certificates and
we make use of ECDSA for signing certificates. I believe it is
worthwhile to point this out again and make readers aware of this
circumstance since most CA certs today are actually signed with RSA or DS=
A.

* The algorithm for verifying the service identity, as described in RFC
6125, is essential for ensuring proper security when certificates are use=
d.

It basically says the following:

  1.  The client constructs a list of acceptable reference identifiers
      based on the source domain and, optionally, the type of service
      to which the client is connecting.

  2.  The server provides its identifiers in the form of a PKIX
      certificate.

  3.  The client checks each of its reference identifiers against the
      presented identifiers for the purpose of finding a match.

  4.  When checking a reference identifier against a presented
      identifier, the client matches the source domain of the
      identifiers and, optionally, their application service type.

I would like to stress the point that certificate usage without
comparing the reference identifier against the presented certificate
ruins the security.

It would be useful to state that this algorithm description and the text
in RFC 6125 assumes that fully qualified DNS domain names are used. This
would be the case for servers that are located in the cloud but not
necessarily true for servers located somewhere in the local network that
do not have their names in the DNS. It would also not be true for
devices that use EUI-64 names, as suggested for clients.

It might also be useful to say whether a DNS-ID, SRV-ID, URI-ID, or a
CN-ID is used. The preference is for DNS-IDs and URI-IDs and my
recommendation for the document would be:

 a) MUST NOT use CN-IDs
 b) MUST NOT contain wildcards
 c) MUST NOT include more than one DNS-ID

Regarding the use of DNS names we also have to support internationalized
domain names even though that is not stated anywhere.

Anything else that would be worthwhile to mention?

What are your thoughts?


Ciao
Hannes


--sItQdiJUgpbflSS30NaaiJiGgxDv8538f
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

iQEcBAEBCgAGBQJVGWYTAAoJEGhJURNOOiAtWP0H+gMfMf/L1BNSTWgkb5d3xNyx
kNd7mQ8WpkVSRtaAb2biJPay//pimxd0snB14Ri2pdW7wGEPNAVvu61RVzY561r6
VOXP+00trDdEXz35HKQzundKiJa0/FBB38UmKYQ+tiNPSM1CJUHbbXDr2nD5paPO
FLYoUe4s6pyt99yMJj3ybrvFlamE9MMZwJ4XeqUiBGubHa5eUwJtBc8nXR4BXaah
lwZYksi0JOAG9SaiPfjBM8d/LThheMoiKjQ85DA0yfsah/7vFE00AqRxvhaXgfKB
XRer0+ABvd9iFfOIqsmEydkDclRbuR/jFIHj976BuAZlowqIC4MyUf3E3gqvBIc=
=I2Wi
-----END PGP SIGNATURE-----

--sItQdiJUgpbflSS30NaaiJiGgxDv8538f--


From nobody Mon Mar 30 08:13:42 2015
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 E3EA31AC414 for <dtls-iot@ietfa.amsl.com>; Mon, 30 Mar 2015 08:13:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.011
X-Spam-Level: 
X-Spam-Status: No, score=-0.011 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 dUA9kEzJDG08 for <dtls-iot@ietfa.amsl.com>; Mon, 30 Mar 2015 08:13:39 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.22]) (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 AAAA31A87C3 for <dtls-iot@ietf.org>; Mon, 30 Mar 2015 08:13:38 -0700 (PDT)
Received: from [192.168.131.145] ([80.92.114.249]) by mail.gmx.com (mrgmx101) with ESMTPSA (Nemesis) id 0MB2G8-1YmTHf0iUm-00A0nh; Mon, 30 Mar 2015 17:13:35 +0200
Message-ID: <5519681E.7000606@gmx.net>
Date: Mon, 30 Mar 2015 17:13:34 +0200
From: Hannes Tschofenig <hannes.tschofenig@gmx.net>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: "Kumar, Sandeep" <sandeep.kumar@philips.com>,  "dtls-iot@ietf.org" <dtls-iot@ietf.org>
References: <BE6D13F6A4554947952B39008B0DC0155202032F@DBXPRD9003MB059.MGDPHG.emi.philips.com>
In-Reply-To: <BE6D13F6A4554947952B39008B0DC0155202032F@DBXPRD9003MB059.MGDPHG.emi.philips.com>
OpenPGP: id=4D776BC9
Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="8Ijw9OJo4ubJMCR2Ftjgkji9I6su3R0OV"
X-Provags-ID: V03:K0:DpGbXlukEpQsWorgj2UUYdzgjeBnYiBEmPxuWcZzQMNIy6BtKPO pnNGPsHZ8gC8tvgjeg+5C4uAZe+aKIJmIDRoXdDBLTvb0uUlI1Owrqqt1G9m6SaSXKMkeSi EvIWRN26B3FVEzd6pcnmJngHh+2Mcgl1ryG6rwooLpmG9XAoxf4Hpj0eBFQTP+IJstWAakv Y7nK8lyqywgRzqo4SwD/g==
X-UI-Out-Filterresults: notjunk:1;
Archived-At: <http://mailarchive.ietf.org/arch/msg/dtls-iot/xFgUTmS4J1K55yfdqjqHkGkr2XI>
Subject: Re: [Dtls-iot] DTLS profle draft
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: Mon, 30 Mar 2015 15:13:41 -0000

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

Hi Sandeep,

thanks for reviewing the draft again.

A few remarks below:

On 03/27/2015 05:40 PM, Kumar, Sandeep wrote:
> =20
>=20
> Hi Hannes and Thomas
>=20
> =20
>=20
> Thanks for the well-written document and taking into consideration all
> the comments.
>=20
> =20
>=20
> However would like one final clarification:
>=20
> Sec 6 states: =93TLS server MUST return the decryption_error error mess=
age
>=20
>    instead of the unknown_psk_identity since the two mechanisms exist
>=20
>    and provide the same functionality.=94
>=20
> =20
>=20
> However Sec 2 of RFC4279 states: =93Alternatively, if the
>=20
>    server wishes to hide the fact that the PSK identity was not known,
>=20
>    it MAY continue the protocol as if the PSK identity existed but the
>=20
>    key was incorrect: that is, respond with a "decrypt_error" alert.=94=

>=20
> =20
>=20
> Is the assumption that the server MUST continue the handshake if the
> psk_identity is not known and send the decryption_error on the Finished=

> message?
>=20
> Is that not opening up options for a DoS attacks on a constrained serve=
r?
>=20

Where do you see the DoS attack potential here?

> =20
>=20
> ----
>=20
> Some other minor things that could be fixed:
>=20
> =20
>=20
> -          The Fig4  client_certificate_type and server_certificate_typ=
e
>  can be shown clearly as extensions similar to as in Fig 8.

Good point!

>=20
> =20
>=20
> =20
>=20
> -          In Sec 4.2 Discovery and Reachability:
>=20
> =93=85..  Once it as been discovered,=85.=94
>=20
> as -> has
>=20
> =20

OK.

>=20
> -          In Sec 6.1 mentions client identity but I guess you are
> referring to the PSK identity

I should use the term PSK identity in the text.
Good catch!
>=20
> =20
>=20
> =20
>=20
> -          Sec 9: =93For cases where the server is constrained (but not=

> the client) the client MUST implement RFC 5077=94
>=20
> Wondering how useful the mandatory statement is since =93constrained=94=

> itself is a vague term.

It might make sense to expand this point a bit further.
I was thinking about the use of session resumption without server-side
state in the context of a constrained server that has to deal with a
number of clients and has limited amount of RAM / flash memory.

>=20
> =20
>=20
> -          Figure 11: shows 128 symmetric  and  283 bit-length ECC, but=

> I could not find this relationship in the ENISA-2014 document. I have
> only seen it mapped to 256-bits. Wondering if this is a typo.

The values of Figure 11 were copied from RFC 4492. I should make this
more explicit. The referenced ENISA document and other publications
recommend different values. For that reason I included those
publications by reference and point out that they roughly make the same
recommendations even though the details vary a bit.

What would, however, be useful to highlight is that these key lengths
refer to the long-term keys. The value of 128-bit symmetric (or the
equivalent for asymmetric crypto) is chosen conservatively under the
assumption that the lifetime of IoT devices is rather long.

This does, however, not necessarily mean that the key length of
Diffie-Hellman keys also needs to be as long as the long term keys. I
would say that this depends a bit on the data that is being protected. I
could imagine that shorter key length is acceptable given that leakage
of data that is several years old is less sensitive. Input on this issue
would, however, be appreciated. (I had a brief chat with Hugo about this
issue and will ask for his advice as well.)

>=20
> =20
>=20
> =20
>=20
> Overall great work.
>=20

Thanks.

Ciao
Hannes

> =20
>=20
> Regards
>=20
> Sandeep
>=20
> =20
>=20
> Dr. Sandeep S. Kumar
>=20
> Senior Scientist,
>=20
> Data Science department,
>=20
> Philips Research,
>=20
> HTC36.p.22 Eindhoven, The Netherlands.
>=20
> =20
>=20
>=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 reproductio=
n
> 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
> _______________________________________________
> dtls-iot mailing list
> dtls-iot@ietf.org
> https://www.ietf.org/mailman/listinfo/dtls-iot
>=20


--8Ijw9OJo4ubJMCR2Ftjgkji9I6su3R0OV
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

iQEcBAEBCgAGBQJVGWgeAAoJEGhJURNOOiAtCT0H/RY3yULlJReufQU4PLHuBiJC
b/h4KSNZEb4WjLJCp5c4kQ1H+WwLSa6NX0z2k4N9RngleDndliM644tkf+ojUoOn
2EjdHJpUZq7WYmhOIHkzxa6/ZiyZIfnmaf+kAElaxnNldaxB+bwhG4unxCI7umcZ
V0PBYFnUPbEXOcOAQtDg7pdaG+KRtGGjK+PBoFrmCXrAFP8uMGaL/FsUAFz95VZI
5qw3siqqNgEf8Toz/IxMQqIB5G4KczWR+699t1QGJs+osr+N3d++Dn+GSihaQRq3
DCjJuMVniMVf1DizSycjmWEvPusGi28S4DU8kpJqoK0q+uEW7i0vqsF8OsTZ19E=
=GnU/
-----END PGP SIGNATURE-----

--8Ijw9OJo4ubJMCR2Ftjgkji9I6su3R0OV--


From nobody Mon Mar 30 14:48:06 2015
Return-Path: <msj@nthpermutation.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 206751A0370 for <dtls-iot@ietfa.amsl.com>; Mon, 30 Mar 2015 14:48:05 -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=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TRFFUhAYdWOM for <dtls-iot@ietfa.amsl.com>; Mon, 30 Mar 2015 14:48:02 -0700 (PDT)
Received: from mail-pd0-f170.google.com (mail-pd0-f170.google.com [209.85.192.170]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B2B011A0368 for <dtls-iot@ietf.org>; Mon, 30 Mar 2015 14:48:02 -0700 (PDT)
Received: by pdbni2 with SMTP id ni2so188234409pdb.1 for <dtls-iot@ietf.org>; Mon, 30 Mar 2015 14:48:02 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :subject:references:in-reply-to:content-type; bh=flBCr59IEDF9VqJjv7EWlLWH0JI8rFe9cr2Gz2D8+Jg=; b=J5cxocn/CMOkyCguRMM54hKozkkpXvHQEmMbdqDtgKndpPZOdPQaqCh9y1Cbp5Ybf4 2T0i0+WbWfCuz0g5gzoYMvPNbAbNAFm5nWWctToRPs+xc4CuDOS7kJDR1T6DsYbDlJEz 6NgPGeNZM/Rq6HPtfoQxh5jpthYJqd03aTySXaORGVFF5ut21UD+dAfHWGwWOD/Vfrs0 pNU87jYcK0etROaYZIoxr7DpJDXTVdI9A59Uj8nTN4DBGftSafoDMyOWAtUHY35H5bEM yLMztdP9bHgdNfnoKv41pYifuyyHfEsP7eURZpBESK4Q8qzQGOS22ncWAOPLDhjgNp++ 1sQA==
X-Gm-Message-State: ALoCoQmQ8RfK8ec0rHfygyJBT9WleKHixarxikVbJ43rVPmWplKvZYY7lUQ89YhJwPtj7bkHmAs0
X-Received: by 10.69.0.163 with SMTP id az3mr61269363pbd.21.1427752082341; Mon, 30 Mar 2015 14:48:02 -0700 (PDT)
Received: from [10.90.197.172] (edge-gw-rwc.silverspringnet.com. [74.121.22.10]) by mx.google.com with ESMTPSA id y5sm1618072pdh.21.2015.03.30.14.48.01 for <dtls-iot@ietf.org> (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 30 Mar 2015 14:48:01 -0700 (PDT)
Message-ID: <5519C491.3050600@nthpermutation.com>
Date: Mon, 30 Mar 2015 17:48:01 -0400
From: Michael StJohns <msj@nthpermutation.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: dtls-iot@ietf.org
References: <55196612.9060004@gmx.net>
In-Reply-To: <55196612.9060004@gmx.net>
Content-Type: multipart/alternative; boundary="------------010409050802020906030405"
Archived-At: <http://mailarchive.ietf.org/arch/msg/dtls-iot/ATbTKhr8gFbBo333creXDpulx_8>
Subject: Re: [Dtls-iot] Certificate Profiling
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: Mon, 30 Mar 2015 21:48:05 -0000

This is a multi-part message in MIME format.
--------------010409050802020906030405
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit

On 3/30/2015 11:04 AM, Hannes Tschofenig wrote:
> Hi all,
>
> Section 6.3 of draft-ietf-dice-profile-10 discusses the recommendations
> for use with certificates.
> While the current text restricts the use of certificates quite a bit I
> got feedback that the current text still leaves several aspects untouched.
>
> Here is a proposal of further recommendations:
>
> * TLS/DTLS offers a lot of freedom for using ECC curves. I would suggest
> to restrict the use of RFC4492-defined ECC ciphersuites to named curves
> only.
rfc5480 effectively does this.

>
> We could furthermore say that the current recommendation is to use
> secp256r1 since this is also what is recommended in CoAP. Furthermore,
> the CoAP specification recommends the use of uncompressed points.

I think this is a good default and close to what's available or will be 
available hardware wise.

>
> We should note that standardization for Curve25519 (for ECDHE) is
> ongoing (see draft-irtf-cfrg-curves-01) and support for it will likely
> be required in the near future.

this may be a non-starter until there is also an ecdsa equivalent also 
standardized - unless you mean to use this only for ECDHE part of the 
key negotiation rather than something bound into a certificate?

More later.

Mike

>
>  From the content in Table 1 it should be obviously that the used ECDSA
> keys in a certificate are signed with with an ECDSA and that's true not
> only for the end-entity certificates but all other certificates in the
> chain, including the CA certs have to have that property. There are
> various types of algorithms that are used for digital certificates and
> we make use of ECDSA for signing certificates. I believe it is
> worthwhile to point this out again and make readers aware of this
> circumstance since most CA certs today are actually signed with RSA or DSA.
>
> * The algorithm for verifying the service identity, as described in RFC
> 6125, is essential for ensuring proper security when certificates are used.
>
> It basically says the following:
>
>    1.  The client constructs a list of acceptable reference identifiers
>        based on the source domain and, optionally, the type of service
>        to which the client is connecting.
>
>    2.  The server provides its identifiers in the form of a PKIX
>        certificate.
>
>    3.  The client checks each of its reference identifiers against the
>        presented identifiers for the purpose of finding a match.
>
>    4.  When checking a reference identifier against a presented
>        identifier, the client matches the source domain of the
>        identifiers and, optionally, their application service type.
>
> I would like to stress the point that certificate usage without
> comparing the reference identifier against the presented certificate
> ruins the security.
>
> It would be useful to state that this algorithm description and the text
> in RFC 6125 assumes that fully qualified DNS domain names are used. This
> would be the case for servers that are located in the cloud but not
> necessarily true for servers located somewhere in the local network that
> do not have their names in the DNS. It would also not be true for
> devices that use EUI-64 names, as suggested for clients.
>
> It might also be useful to say whether a DNS-ID, SRV-ID, URI-ID, or a
> CN-ID is used. The preference is for DNS-IDs and URI-IDs and my
> recommendation for the document would be:
>
>   a) MUST NOT use CN-IDs
>   b) MUST NOT contain wildcards
>   c) MUST NOT include more than one DNS-ID
>
> Regarding the use of DNS names we also have to support internationalized
> domain names even though that is not stated anywhere.
>
> Anything else that would be worthwhile to mention?
>
> What are your thoughts?
>
>
> Ciao
> Hannes
>
>
>
> _______________________________________________
> dtls-iot mailing list
> dtls-iot@ietf.org
> https://www.ietf.org/mailman/listinfo/dtls-iot


--------------010409050802020906030405
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta content="text/html; charset=windows-1252"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <div class="moz-cite-prefix">On 3/30/2015 11:04 AM, Hannes
      Tschofenig wrote:<br>
    </div>
    <blockquote cite="mid:55196612.9060004@gmx.net" type="cite">
      <pre wrap="">Hi all,

Section 6.3 of draft-ietf-dice-profile-10 discusses the recommendations
for use with certificates.
While the current text restricts the use of certificates quite a bit I
got feedback that the current text still leaves several aspects untouched.

Here is a proposal of further recommendations:

* TLS/DTLS offers a lot of freedom for using ECC curves. I would suggest
to restrict the use of RFC4492-defined ECC ciphersuites to named curves
only.</pre>
    </blockquote>
    rfc5480 effectively does this.  <br>
    <br>
    <blockquote cite="mid:55196612.9060004@gmx.net" type="cite">
      <pre wrap="">

We could furthermore say that the current recommendation is to use
secp256r1 since this is also what is recommended in CoAP. Furthermore,
the CoAP specification recommends the use of uncompressed points.</pre>
    </blockquote>
    <br>
    I think this is a good default and close to what's available or will
    be available hardware wise.  <br>
    <br>
    <blockquote cite="mid:55196612.9060004@gmx.net" type="cite">
      <pre wrap="">

We should note that standardization for Curve25519 (for ECDHE) is
ongoing (see draft-irtf-cfrg-curves-01) and support for it will likely
be required in the near future.</pre>
    </blockquote>
    <br>
    this may be a non-starter until there is also an ecdsa equivalent
    also standardized - unless you mean to use this only for ECDHE part
    of the key negotiation rather than something bound into a
    certificate?<br>
    <br>
    More later.<br>
    <br>
    Mike<br>
    <br>
    <blockquote cite="mid:55196612.9060004@gmx.net" type="cite">
      <pre wrap="">

>From the content in Table 1 it should be obviously that the used ECDSA
keys in a certificate are signed with with an ECDSA and that's true not
only for the end-entity certificates but all other certificates in the
chain, including the CA certs have to have that property. There are
various types of algorithms that are used for digital certificates and
we make use of ECDSA for signing certificates. I believe it is
worthwhile to point this out again and make readers aware of this
circumstance since most CA certs today are actually signed with RSA or DSA.

* The algorithm for verifying the service identity, as described in RFC
6125, is essential for ensuring proper security when certificates are used.

It basically says the following:

  1.  The client constructs a list of acceptable reference identifiers
      based on the source domain and, optionally, the type of service
      to which the client is connecting.

  2.  The server provides its identifiers in the form of a PKIX
      certificate.

  3.  The client checks each of its reference identifiers against the
      presented identifiers for the purpose of finding a match.

  4.  When checking a reference identifier against a presented
      identifier, the client matches the source domain of the
      identifiers and, optionally, their application service type.

I would like to stress the point that certificate usage without
comparing the reference identifier against the presented certificate
ruins the security.

It would be useful to state that this algorithm description and the text
in RFC 6125 assumes that fully qualified DNS domain names are used. This
would be the case for servers that are located in the cloud but not
necessarily true for servers located somewhere in the local network that
do not have their names in the DNS. It would also not be true for
devices that use EUI-64 names, as suggested for clients.

It might also be useful to say whether a DNS-ID, SRV-ID, URI-ID, or a
CN-ID is used. The preference is for DNS-IDs and URI-IDs and my
recommendation for the document would be:

 a) MUST NOT use CN-IDs
 b) MUST NOT contain wildcards
 c) MUST NOT include more than one DNS-ID

Regarding the use of DNS names we also have to support internationalized
domain names even though that is not stated anywhere.

Anything else that would be worthwhile to mention?

What are your thoughts?


Ciao
Hannes

</pre>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
dtls-iot mailing list
<a class="moz-txt-link-abbreviated" href="mailto:dtls-iot@ietf.org">dtls-iot@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/dtls-iot">https://www.ietf.org/mailman/listinfo/dtls-iot</a>
</pre>
    </blockquote>
    <br>
  </body>
</html>

--------------010409050802020906030405--


From nobody Tue Mar 31 05:14:22 2015
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 AA4E91A9120 for <dtls-iot@ietfa.amsl.com>; Tue, 31 Mar 2015 05:14:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 MpU09Y7HCGlN for <dtls-iot@ietfa.amsl.com>; Tue, 31 Mar 2015 05:14:19 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.15.19]) (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 140A01A9087 for <dtls-iot@ietf.org>; Tue, 31 Mar 2015 05:14:19 -0700 (PDT)
Received: from [192.168.131.145] ([80.92.114.249]) by mail.gmx.com (mrgmx002) with ESMTPSA (Nemesis) id 0LhfZR-1ZGhj72oWv-00mrP4; Tue, 31 Mar 2015 14:14:16 +0200
Message-ID: <551A8F97.2020007@gmx.net>
Date: Tue, 31 Mar 2015 14:14:15 +0200
From: Hannes Tschofenig <hannes.tschofenig@gmx.net>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: Michael StJohns <msj@nthpermutation.com>, dtls-iot@ietf.org
References: <55196612.9060004@gmx.net> <5519C491.3050600@nthpermutation.com>
In-Reply-To: <5519C491.3050600@nthpermutation.com>
OpenPGP: id=4D776BC9
Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="FJgasbN1IiJI0A21okrJBd2kUWhVABlw7"
X-Provags-ID: V03:K0:sKOgZ5LfpsOU1/lz26hXSMtNaaQWs3aZW7rpj/GLFTcXNnnb52V zFDS11LWGfhA5NPukIQPC3G/gl5nl7fWY7CW21Y8eFQyhRIgZGL78HONYHF3LPxUwIik385 1Op2DCwxOyMFeZAic0UxWm2WgbKXmZC7XbUvGTyCrPHPG16K8w60w6Z5bOI2HYyiBo03CEq DfSOQfFD/foKkeBvSbDnw==
X-UI-Out-Filterresults: notjunk:1;
Archived-At: <http://mailarchive.ietf.org/arch/msg/dtls-iot/7eie7uKSeP5qSFQOx5DlwU_Lz7Y>
Subject: Re: [Dtls-iot] Certificate Profiling
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: Tue, 31 Mar 2015 12:14:21 -0000

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

Hi Mike,

thanks for your quick response.


On 03/30/2015 11:48 PM, Michael StJohns wrote:
> On 3/30/2015 11:04 AM, Hannes Tschofenig wrote:
>> Hi all,
>>
>> Section 6.3 of draft-ietf-dice-profile-10 discusses the recommendation=
s
>> for use with certificates.
>> While the current text restricts the use of certificates quite a bit I=

>> got feedback that the current text still leaves several aspects untouc=
hed.
>>
>> Here is a proposal of further recommendations:
>>
>> * TLS/DTLS offers a lot of freedom for using ECC curves. I would sugge=
st
>> to restrict the use of RFC4492-defined ECC ciphersuites to named curve=
s
>> only.
> rfc5480 effectively does this.=20

Yes, saying that only named curves are used and then pointing to RFC
5480 (and to secp256r1 in particular).

>=20
>>
>> We could furthermore say that the current recommendation is to use
>> secp256r1 since this is also what is recommended in CoAP. Furthermore,=

>> the CoAP specification recommends the use of uncompressed points.
>=20
> I think this is a good default and close to what's available or will be=

> available hardware wise.=20

Good to hear.

>=20
>>
>> We should note that standardization for Curve25519 (for ECDHE) is
>> ongoing (see draft-irtf-cfrg-curves-01) and support for it will likely=

>> be required in the near future.
>=20
> this may be a non-starter until there is also an ecdsa equivalent also
> standardized - unless you mean to use this only for ECDHE part of the
> key negotiation rather than something bound into a certificate?

It would only be an informational reference to the ongoing work to give
an early warning to implementers that there is something coming.

The work on ed25519 is in progress as well but not as far along as
Curve25519.

Ciao
Hannes

>=20
> More later.
>=20
> Mike
>=20
>>
>> >From the content in Table 1 it should be obviously that the used ECDS=
A
>> keys in a certificate are signed with with an ECDSA and that's true no=
t
>> only for the end-entity certificates but all other certificates in the=

>> chain, including the CA certs have to have that property. There are
>> various types of algorithms that are used for digital certificates and=

>> we make use of ECDSA for signing certificates. I believe it is
>> worthwhile to point this out again and make readers aware of this
>> circumstance since most CA certs today are actually signed with RSA or=
 DSA.
>>
>> * The algorithm for verifying the service identity, as described in RF=
C
>> 6125, is essential for ensuring proper security when certificates are =
used.
>>
>> It basically says the following:
>>
>>   1.  The client constructs a list of acceptable reference identifiers=

>>       based on the source domain and, optionally, the type of service
>>       to which the client is connecting.
>>
>>   2.  The server provides its identifiers in the form of a PKIX
>>       certificate.
>>
>>   3.  The client checks each of its reference identifiers against the
>>       presented identifiers for the purpose of finding a match.
>>
>>   4.  When checking a reference identifier against a presented
>>       identifier, the client matches the source domain of the
>>       identifiers and, optionally, their application service type.
>>
>> I would like to stress the point that certificate usage without
>> comparing the reference identifier against the presented certificate
>> ruins the security.
>>
>> It would be useful to state that this algorithm description and the te=
xt
>> in RFC 6125 assumes that fully qualified DNS domain names are used. Th=
is
>> would be the case for servers that are located in the cloud but not
>> necessarily true for servers located somewhere in the local network th=
at
>> do not have their names in the DNS. It would also not be true for
>> devices that use EUI-64 names, as suggested for clients.
>>
>> It might also be useful to say whether a DNS-ID, SRV-ID, URI-ID, or a
>> CN-ID is used. The preference is for DNS-IDs and URI-IDs and my
>> recommendation for the document would be:
>>
>>  a) MUST NOT use CN-IDs
>>  b) MUST NOT contain wildcards
>>  c) MUST NOT include more than one DNS-ID
>>
>> Regarding the use of DNS names we also have to support internationaliz=
ed
>> domain names even though that is not stated anywhere.
>>
>> Anything else that would be worthwhile to mention?
>>
>> What are your thoughts?
>>
>>
>> Ciao
>> Hannes
>>
>>
>>
>> _______________________________________________
>> dtls-iot mailing list
>> dtls-iot@ietf.org
>> https://www.ietf.org/mailman/listinfo/dtls-iot
>=20
>=20
>=20
> _______________________________________________
> dtls-iot mailing list
> dtls-iot@ietf.org
> https://www.ietf.org/mailman/listinfo/dtls-iot
>=20


--FJgasbN1IiJI0A21okrJBd2kUWhVABlw7
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

iQEcBAEBCgAGBQJVGo+XAAoJEGhJURNOOiAtISMH/ieH1daQP5vkYkP9+tvlIA8O
SYOWUZmWauAyuRtV5uaNnFcbfMOmfGaTAdD/keuSttQeoBdGjpQ1E2vYGSTF57gy
7p8vfNLXzYHpHYj8BMWVVbQtpTbiAVJeabZRrnfdw7e2/ahNYw1DH8Sj7cOVxXQF
/bPsjc09Tp+fRI/ZBGZDcEImEap8rmtuZPVUjl379JARjql9vFG52ISzWHPDgMpD
TxuYouHf2w6JCh+JltUgP7iee/F3rPreS/3LHWBEJ1bSZZBmNaOqg/Qerm8Maulo
n2iNkHxWhboaNVkeH5hQzNK4hOr7agj5COV0Lr1geHsb8jnllFqtQbF1bMlXdMY=
=kQFD
-----END PGP SIGNATURE-----

--FJgasbN1IiJI0A21okrJBd2kUWhVABlw7--

