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

Carsten Bormann <cabo@tzi.org> Tue, 09 April 2013 10:39 UTC

Return-Path: <cabo@tzi.org>
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 E44E021F89D3 for <core@ietfa.amsl.com>; Tue, 9 Apr 2013 03:39:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.14
X-Spam-Level:
X-Spam-Status: No, score=-106.14 tagged_above=-999 required=5 tests=[AWL=0.109, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 adjzsMRfqj2b for <core@ietfa.amsl.com>; Tue, 9 Apr 2013 03:39:17 -0700 (PDT)
Received: from informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) by ietfa.amsl.com (Postfix) with ESMTP id 5AF0E21F8546 for <core@ietf.org>; Tue, 9 Apr 2013 03:39:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from smtp-fb3.informatik.uni-bremen.de (smtp-fb3.informatik.uni-bremen.de [134.102.224.120]) by informatik.uni-bremen.de (8.14.4/8.14.4) with ESMTP id r39Ad6Fu026670; Tue, 9 Apr 2013 12:39:06 +0200 (CEST)
Received: from [192.168.217.105] (p54891CAB.dip.t-dialin.net [84.137.28.171]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id E038D3829; Tue, 9 Apr 2013 12:39:05 +0200 (CEST)
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Content-Type: text/plain; charset="windows-1252"
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <031DD135F9160444ABBE3B0C36CED618BFE2BA@011-DB3MPN2-082.MGDPHG.emi.philips.com>
Date: Tue, 09 Apr 2013 12:39:05 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <9957A4C5-1B36-49D2-AADD-35481C1F7894@tzi.org>
References: <031DD135F9160444ABBE3B0C36CED618BFE2BA@011-DB3MPN2-082.MGDPHG.emi.philips.com>
To: "Dijk, Esko" <esko.dijk@philips.com>
X-Mailer: Apple Mail (2.1503)
Cc: "core (core@ietf.org)" <core@ietf.org>
Subject: Re: [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:39:19 -0000

On Apr 9, 2013, at 12:12, "Dijk, Esko" <esko.dijk@philips.com> wrote:

> 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].

Oh.  This is so obvious that I just made that change in the SVN right away [1275].
(This hasn't been done before because I was expecting a future version of http-mapping to have a "replaces" relationship to the cross-reverse-convention draft -- that hasn't happened yet, but it is sure the intention, and we should make this intention visible now.)

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

I would think that referencing groupcomm is a good idea.  I'm not quite sure where and how, so let's discuss this:

I'd probably add a sentence of the form 

   A more general discussion of group communication with CoAP is in [I-D.ietf-core-groupcomm].

at the end of the first paragraph of section 8.

I'd also insert a reference to groupcomm before the reference to coap-misc in 8.2.2, like this:

   Proxying multicast requests is discussed in more detail in [I-D.ietf-core-groupcomm]; a
   proposal to address the base URI issue can be found in section 3 of
   [I-D.bormann-coap-misc].

Grüße, Carsten