IETF Logo Mail Archive

[core] CoAP requirements and HTTP iwf

"Adriano Pezzuto (apezzuto)" <apezzuto@cisco.com> Fri, 26 March 2010 09:09 UTC

Return-Path: <apezzuto@cisco.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 28BEC3A69E9 for <core@core3.amsl.com>; Fri, 26 Mar 2010 02:09:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.469
X-Spam-Level:
X-Spam-Status: No, score=-9.469 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13, RCVD_IN_DNSWL_HI=-8]
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 SYGIZ6RwsQhd for <core@core3.amsl.com>; Fri, 26 Mar 2010 02:09:08 -0700 (PDT)
Received: from sj-iport-3.cisco.com (sj-iport-3.cisco.com [171.71.176.72]) by core3.amsl.com (Postfix) with ESMTP id 0030E3A6896 for <core@ietf.org>; Fri, 26 Mar 2010 02:09:06 -0700 (PDT)
Authentication-Results: sj-iport-3.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAJUWrEurR7H+/2dsb2JhbACbK3OlGZkWhH4E
X-IronPort-AV: E=Sophos;i="4.51,313,1267401600"; d="scan'208";a="218025394"
Received: from sj-core-2.cisco.com ([171.71.177.254]) by sj-iport-3.cisco.com with ESMTP; 26 Mar 2010 09:09:30 +0000
Received: from xbh-ams-101.cisco.com (xbh-ams-101.cisco.com [144.254.74.71]) by sj-core-2.cisco.com (8.13.8/8.14.3) with ESMTP id o2Q99FSi025372 for <core@ietf.org>; Fri, 26 Mar 2010 09:09:30 GMT
Received: from xmb-ams-106.cisco.com ([144.254.74.81]) by xbh-ams-101.cisco.com with Microsoft SMTPSVC(6.0.3790.3959); Fri, 26 Mar 2010 10:09:28 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
x-cr-puzzleid: {64FBCC09-07E2-4322-8B79-AC01F6C7F929}
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
x-cr-hashedpuzzle: buk= AeBf Dbc5 D5rk ECTs ELQj Evbe FZTg F4MU GMfv GMvV HAWM HZAe H2Ii IwfE I/fM; 1; YwBvAHIAZQBAAGkAZQB0AGYALgBvAHIAZwA=; Sosha1_v1; 7; {64FBCC09-07E2-4322-8B79-AC01F6C7F929}; YQBwAGUAegB6AHUAdABvAEAAYwBpAHMAYwBvAC4AYwBvAG0A; Fri, 26 Mar 2010 09:09:25 GMT; QwBvAEEAUAAgAHIAZQBxAHUAaQByAGUAbQBlAG4AdABzACAAYQBuAGQAIABIAFQAVABQACAAaQB3AGYA
Content-class: urn:content-classes:message
Date: Fri, 26 Mar 2010 10:09:25 +0100
Message-ID: <0D212BD466921646B58854FB79092CEC0196C3BC@XMB-AMS-106.cisco.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: CoAP requirements and HTTP iwf
Thread-Index: AcrMxAgxob0ouQv0SS+I/WEtUZFC5Q==
From: "Adriano Pezzuto (apezzuto)" <apezzuto@cisco.com>
To: core@ietf.org
X-OriginalArrivalTime: 26 Mar 2010 09:09:28.0649 (UTC) FILETIME=[09F99B90:01CACCC4]
Subject: [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 09:09:09 -0000

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

v2.23.0 | Report a Bug | By Email