[core] Informative refs in core-coap: groupcomm / http-mapping ?

"Dijk, Esko" <esko.dijk@philips.com> Tue, 09 April 2013 10:12 UTC

Return-Path: <esko.dijk@philips.com>
X-Original-To: core@ietfa.amsl.com
Delivered-To: core@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1390D21F937D for <core@ietfa.amsl.com>; Tue, 9 Apr 2013 03:12:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.739
X-Spam-Level:
X-Spam-Status: No, score=-4.739 tagged_above=-999 required=5 tests=[BAYES_20=-0.74, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id O45vlM+pE0UX for <core@ietfa.amsl.com>; Tue, 9 Apr 2013 03:12:21 -0700 (PDT)
Received: from tx2outboundpool.messaging.microsoft.com (tx2ehsobe004.messaging.microsoft.com [65.55.88.14]) by ietfa.amsl.com (Postfix) with ESMTP id 9CD0221F937B for <core@ietf.org>; Tue, 9 Apr 2013 03:12:21 -0700 (PDT)
Received: from mail103-tx2-R.bigfish.com (10.9.14.228) by TX2EHSOBE009.bigfish.com (10.9.40.29) with Microsoft SMTP Server id 14.1.225.23; Tue, 9 Apr 2013 10:12:20 +0000
Received: from mail103-tx2 (localhost [127.0.0.1]) by mail103-tx2-R.bigfish.com (Postfix) with ESMTP id A9A713002E3 for <core@ietf.org>; Tue, 9 Apr 2013 10:12:20 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.55.7.222; KIP:(null); UIP:(null); IPV:NLI; H:mail.philips.com; RD:none; EFVD:NLI
X-SpamScore: -10
X-BigFish: VPS-10(zz15d6O9251Jc85fh217bIzz1f42h1fc6h1ee6h1de0h1fdah1202h1e76h1d1ah1d2ahzz18c673hz2dh2a8h668h839hd25hf0ah1288h12a5h12bdh137ah1441h1504h1537h153bh15d0h162dh1631h1758h18e1h1946h19b5h19ceh1ad9h1b0ah1bceh1155h)
Received: from mail103-tx2 (localhost.localdomain [127.0.0.1]) by mail103-tx2 (MessageSwitch) id 1365502338849747_20203; Tue, 9 Apr 2013 10:12:18 +0000 (UTC)
Received: from TX2EHSMHS015.bigfish.com (unknown [10.9.14.244]) by mail103-tx2.bigfish.com (Postfix) with ESMTP id CA17A2E0164 for <core@ietf.org>; Tue, 9 Apr 2013 10:12:18 +0000 (UTC)
Received: from mail.philips.com (157.55.7.222) by TX2EHSMHS015.bigfish.com (10.9.99.115) with Microsoft SMTP Server (TLS) id 14.1.225.23; Tue, 9 Apr 2013 10:12:17 +0000
Received: from 011-DB3MMR1-013.MGDPHG.emi.philips.com (10.128.28.97) by 011-DB3MMR1-006.MGDPHG.emi.philips.com (10.128.28.56) with Microsoft SMTP Server (TLS) id 14.2.328.11; Tue, 9 Apr 2013 10:12:15 +0000
Received: from 011-DB3MPN2-082.MGDPHG.emi.philips.com ([169.254.2.99]) by 011-DB3MMR1-013.MGDPHG.emi.philips.com ([10.128.28.97]) with mapi id 14.02.0328.011; Tue, 9 Apr 2013 10:12:15 +0000
From: "Dijk, Esko" <esko.dijk@philips.com>
To: "core (core@ietf.org)" <core@ietf.org>
Thread-Topic: Informative refs in core-coap: groupcomm / http-mapping ?
Thread-Index: Ac41ClTg+6BWDiH9Qu6C/Zf1AJDdpQ==
Date: Tue, 09 Apr 2013 10:12:14 +0000
Message-ID: <031DD135F9160444ABBE3B0C36CED618BFE2BA@011-DB3MPN2-082.MGDPHG.emi.philips.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [194.171.252.103]
Content-Type: multipart/alternative; boundary="_000_031DD135F9160444ABBE3B0C36CED618BFE2BA011DB3MPN2082MGDP_"
MIME-Version: 1.0
X-OriginatorOrg: philips.com
Subject: [core] Informative refs in core-coap: groupcomm / http-mapping ?
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" <core.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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: Tue, 09 Apr 2013 10:12:23 -0000

Dear all,

I was just looking at the informative references section of core-coap. Ideas for improving these references:

1)
We could replace reference to  [I-D.bormann-core-cross-reverse-convention] with [draft-castellani-core-http-mapping], where we plan to add a default URI convention for a reverse proxy in the next version, similar to the current content of [I-D.bormann-core-cross-reverse-convention].

2)
We could add a reference to [draft-ietf-core-groupcomm] to point to additional guiding text on these two aspects:

*         Multicast Request Acceptance and Response Suppression (section 3.6). This provides details to the core-coap rule that a "server MAY always pretend it did not receive the request"

*         A new section will be added for the next groupcomm version about Proxying of multicast requests; related to core-coap section 8.2.2. It explains in more detail the problems when doing this and a solution as well.

Would this be useful to have in core-coap - any opinions?

regards,

Esko Dijk

________________________________
The information contained in this message may be confidential and legally protected under applicable law. The message is intended solely for the addressee(s). If you are not the intended recipient, you are hereby notified that any use, forwarding, dissemination, or reproduction of this message is strictly prohibited and may be unlawful. If you are not the intended recipient, please contact the sender by return e-mail and destroy all copies of the original message.