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

"Rahman, Akbar" <> Thu, 15 March 2012 19:50 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 1769921F8587 for <>; Thu, 15 Mar 2012 12:50:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.313
X-Spam-Status: No, score=-2.313 tagged_above=-999 required=5 tests=[AWL=0.286, BAYES_00=-2.599]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id kRszCq6vkSiN for <>; Thu, 15 Mar 2012 12:50:12 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id 7833221F857F for <>; Thu, 15 Mar 2012 12:50:12 -0700 (PDT)
Received: from ([]) by with Microsoft SMTPSVC(6.0.3790.4675); Thu, 15 Mar 2012 15:50:11 -0400
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-MimeOLE: Produced By Microsoft Exchange V6.5
Date: Thu, 15 Mar 2012 15:50:10 -0400
Message-ID: <>
In-Reply-To: <>
Thread-Topic: [core] #177: Response suppression for multicast not defined
Thread-Index: Ac0CFbNEXbbMNBN1RmmmoOdaqqIAAQAzk4uw
References: <><><><> <> <> <>
From: "Rahman, Akbar" <>
To: "Carsten Bormann" <>
X-OriginalArrivalTime: 15 Mar 2012 19:50:11.0135 (UTC) FILETIME=[D4E774F0:01CD02E4]
Cc: core issue tracker <>, core WG <>
Subject: Re: [core] #177: Response suppression for multicast not defined
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 15 Mar 2012 19:50:13 -0000


Can you clarify what you mean by "We do not specify local processing ..."? 

I do not follow your logic.  For example, in coap-09 there is clearly specification language for local caching (  So what did you really mean?


-----Original Message-----
From: Carsten Bormann [] 
Sent: Wednesday, March 14, 2012 3:07 PM
To: Rahman, Akbar
Cc: Zach Shelby; core issue tracker; core WG
Subject: Re: [core] #177: Response suppression for multicast not defined

> 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 

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