IETF Logo Mail Archive

[Anima-bootstrap] CoAP mandatory?

"Liubing (Leo)" <leo.liubing@huawei.com> Wed, 04 January 2017 09:35 UTC

Return-Path: <leo.liubing@huawei.com>
X-Original-To: anima-bootstrap@ietfa.amsl.com
Delivered-To: anima-bootstrap@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 678C7129C79 for <anima-bootstrap@ietfa.amsl.com>; Wed, 4 Jan 2017 01:35:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.32
X-Spam-Level:
X-Spam-Status: No, score=-7.32 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-3.1, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 IOODYaiN1Coa for <anima-bootstrap@ietfa.amsl.com>; Wed, 4 Jan 2017 01:35:30 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id ECDE112995C for <anima-bootstrap@ietf.org>; Wed, 4 Jan 2017 01:35:29 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml703-cah.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id DDU69881; Wed, 04 Jan 2017 09:35:27 +0000 (GMT)
Received: from NKGEML413-HUB.china.huawei.com (10.98.56.74) by lhreml703-cah.china.huawei.com (10.201.5.104) with Microsoft SMTP Server (TLS) id 14.3.301.0; Wed, 4 Jan 2017 09:35:26 +0000
Received: from NKGEML514-MBX.china.huawei.com ([fe80::40a8:f0d:c0f3:2ca5]) by NKGEML413-HUB.china.huawei.com ([10.98.56.74]) with mapi id 14.03.0235.001; Wed, 4 Jan 2017 17:35:16 +0800
From: "Liubing (Leo)" <leo.liubing@huawei.com>
To: "anima-bootstrap@ietf.org" <anima-bootstrap@ietf.org>
Thread-Topic: CoAP mandatory?
Thread-Index: AQHSZm3bDBkyKdzxNEmKd2cHh6652A==
Date: Wed, 04 Jan 2017 09:35:16 +0000
Message-ID: <8AE0F17B87264D4CAC7DE0AA6C406F45C2E940C1@nkgeml514-mbx.china.huawei.com>
References: <6525c5f0b6e040b683ccd9c43b1c5e2f@VI1PR9003MB0237.MGDPHG.emi.philips.com> <14831.1481139454@obiwan.sandelman.ca> <d9aba3a07d14400f88f22329abc00128@XCH-ALN-010.cisco.com> <CAH51uSdK_BHgFKXzpp2XJ4H9fEqkkLynFLjV5PTn6Y8EHSFz-g@mail.gmail.com>
In-Reply-To: <CAH51uSdK_BHgFKXzpp2XJ4H9fEqkkLynFLjV5PTn6Y8EHSFz-g@mail.gmail.com>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.111.191.175]
Content-Type: multipart/alternative; boundary="_000_8AE0F17B87264D4CAC7DE0AA6C406F45C2E940C1nkgeml514mbxchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A020203.586CC1DF.0314, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0, ip=0.0.0.0, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: 53817f9c80016f33d1ffa5afa48619b2
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima-bootstrap/okZS2vNUzc0qQerfT1WBLYcyraE>
Subject: [Anima-bootstrap] CoAP mandatory?
X-BeenThere: anima-bootstrap@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Mailing list for the bootstrap design team of the ANIMA WG <anima-bootstrap.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/anima-bootstrap>, <mailto:anima-bootstrap-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/anima-bootstrap/>
List-Post: <mailto:anima-bootstrap@ietf.org>
List-Help: <mailto:anima-bootstrap-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/anima-bootstrap>, <mailto:anima-bootstrap-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 04 Jan 2017 09:35:32 -0000

Hi Dear all,

The 04 draft has an editor note:

“ [[EDNOTE: The
   choice of CoAP as the mandatory to implement protocol rather than
   HTTP maximizes code reuse on the smallest of devices.  Unfortunately
   this means this document will have to include the EST over CoAP
   details as additional sections.  The alternative is to make 'HTTPS
   proxy' method the mandatory to implement and provide a less friendly
   environment for the smallest of devices.  This is a decision we'll
   have to see addressed by the broader team.]]
”
Does this open question already have a final conclusion?
Thanks.

Best regards,
Bing

v2.14.0 | Report a Bug | By Email