IETF Logo Mail Archive

Re: [core] CoAP requirements and HTTP iwf

"Stuber, Michael" <Michael.Stuber@itron.com> Fri, 26 March 2010 13:37 UTC

Return-Path: <Michael.Stuber@itron.com>
X-Original-To: core@core3.amsl.com
Delivered-To: core@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6A6D03A689D for <core@core3.amsl.com>; Fri, 26 Mar 2010 06:37:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.469
X-Spam-Level:
X-Spam-Status: No, score=-1.469 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jyNXpJQrZFUU for <core@core3.amsl.com>; Fri, 26 Mar 2010 06:37:10 -0700 (PDT)
Received: from mailer-1.itron.com (mailer-1.itron.com [198.182.8.121]) by core3.amsl.com (Postfix) with ESMTP id 5CFC63A67F0 for <core@ietf.org>; Fri, 26 Mar 2010 06:37:10 -0700 (PDT)
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 26 Mar 2010 06:37:33 -0700
Message-ID: <05C6A38D732F1144A8C4016BA4416BFE02A97D2B@SPO-EXVS-02.itron.com>
In-Reply-To: <0D212BD466921646B58854FB79092CEC0196C3BC@XMB-AMS-106.cisco.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [core] CoAP requirements and HTTP iwf
Thread-Index: AcrMxAgxob0ouQv0SS+I/WEtUZFC5QAJNvmw
References: <0D212BD466921646B58854FB79092CEC0196C3BC@XMB-AMS-106.cisco.com>
From: "Stuber, Michael" <Michael.Stuber@itron.com>
To: "Adriano Pezzuto (apezzuto)" <apezzuto@cisco.com>, core@ietf.org
Subject: Re: [core] CoAP requirements and HTTP iwf
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" <core.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/core>, <mailto:core-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/core>
List-Post: <mailto:core@ietf.org>
List-Help: <mailto:core-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/core>, <mailto:core-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Mar 2010 13:37:11 -0000

A well defined mapping between CoAP and HTTP is a core requirement.
>From a document structure standpoint, either way is fine, but I wouldn't
want to split it out only to have it languish.

-----Original Message-----
From: core-bounces@ietf.org [mailto:core-bounces@ietf.org] On Behalf Of
Adriano Pezzuto (apezzuto)
Sent: Friday, March 26, 2010 2:09 AM
To: core@ietf.org
Subject: [core] CoAP requirements and HTTP iwf


Hello,
a great session in Anaheim!

For what concerns CoAP and HTTP mapping (REQ7: of
draft-shelby-core-coap-req-00), I understood that there is not "the"
CoAP-HTTP mapping but more possible ways to do the mapping are possible.
Also, further mappings, e.g.  CoAP-XMPP,   CoAP-SIP, ..  might be
defined in the future, if required.

What about to split the CoAP specs from the  CoaP-*P mapping specs? I
mean to have different specs for CoAP core protocol, CoAP-HTTP mapping,
CoAP-XMPP mapping, CoAP-*P mapping and so on.

Not sure if this make sense ...

regards,
Adriano
_______________________________________________
core mailing list
core@ietf.org
https://www.ietf.org/mailman/listinfo/core

v2.23.0 | Report a Bug | By Email