Re: [core] #177: Response suppression for multicast not defined

Carsten Bormann <cabo@tzi.org> Wed, 14 March 2012 19:07 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 5C1F621F8833 for <core@ietfa.amsl.com>; Wed, 14 Mar 2012 12:07:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.122
X-Spam-Level:
X-Spam-Status: No, score=-106.122 tagged_above=-999 required=5 tests=[AWL=0.127, 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 boWjOuySEOQh for <core@ietfa.amsl.com>; Wed, 14 Mar 2012 12:07:25 -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 86D9221F8821 for <core@ietf.org>; Wed, 14 Mar 2012 12:07:25 -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.3/8.14.3) with ESMTP id q2EJ75Ek000243; Wed, 14 Mar 2012 20:07:06 +0100 (CET)
Received: from [10.0.1.3] (reingewinn.informatik.uni-bremen.de [134.102.218.123]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id ADAE4A58; Wed, 14 Mar 2012 20:07:05 +0100 (CET)
Mime-Version: 1.0 (Apple Message framework v1257)
Content-Type: text/plain; charset="iso-8859-1"
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <D60519DB022FFA48974A25955FFEC08C046088BB@SAM.InterDigital.com>
Date: Wed, 14 Mar 2012 20:07:05 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <FB642636-078D-41A6-8525-5604EA125218@tzi.org>
References: <051.f2c70308ab0d71f7798afa515a549f6b@trac.tools.ietf.org><066.924a528dfa41671c33a7c32467afea34@trac.tools.ietf.org><D60519DB022FFA48974A25955FFEC08C046085D1@SAM.InterDigital.com><AABA9EFA-250D-4D9B-8949-EE89FE1F8457@sensinode.com> <D60519DB022FFA48974A25955FFEC08C046085F8@SAM.InterDigital.com> <D60519DB022FFA48974A25955FFEC08C046088BB@SAM.InterDigital.com>
To: "Rahman, Akbar" <Akbar.Rahman@InterDigital.com>
X-Mailer: Apple Mail (2.1257)
Cc: core issue tracker <trac+core@gamay.tools.ietf.org>, core WG <core@ietf.org>
Subject: Re: [core] #177: Response suppression for multicast not defined
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: Wed, 14 Mar 2012 19:07:26 -0000

> Thanks, I read coap-09 and saw the new text for multicast response
> handling in section 4.5.  One follow up question:
> 
> 
> - If the multicast message receivers (servers) do send back valid
> responses (e.g. successful Response to a GET), then the original sender
> (or some intermediate CoAP proxy) will receive multiple responses and
> will have to some method of filtering and processing the multiple
> responses.

That is the nature of multicast, so I would expect the need for that to be obvious.
We do not specify local processing, so what exactly the client does with the information is up to the implementer.

> - We show one possible use case in 
> 
> http://tools.ietf.org/html/draft-ietf-core-groupcomm-01#page-17

Indeed, but generally the core-coap draft is very sparse on use cases.

> - Should we have some text in coap-09 to cover this multiple response
> processing as well?

So, in summary, I do not see a need for additions to core-coap.

Grüße, Carsten