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

"Rahman, Akbar" <Akbar.Rahman@InterDigital.com> Mon, 12 March 2012 19:41 UTC

Return-Path: <Akbar.Rahman@InterDigital.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 B2FEA21E8090 for <core@ietfa.amsl.com>; Mon, 12 Mar 2012 12:41:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.171
X-Spam-Level:
X-Spam-Status: No, score=-2.171 tagged_above=-999 required=5 tests=[AWL=0.428, BAYES_00=-2.599]
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 gd6nIxur11MW for <core@ietfa.amsl.com>; Mon, 12 Mar 2012 12:41:44 -0700 (PDT)
Received: from idcout.InterDigital.com (smtp-out1.interdigital.com [64.208.228.135]) by ietfa.amsl.com (Postfix) with ESMTP id B509221E805C for <core@ietf.org>; Mon, 12 Mar 2012 12:41:44 -0700 (PDT)
Received: from SAM.InterDigital.com ([10.30.2.11]) by idcout.InterDigital.com with Microsoft SMTPSVC(6.0.3790.4675); Mon, 12 Mar 2012 15:41:43 -0400
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
X-MimeOLE: Produced By Microsoft Exchange V6.5
Date: Mon, 12 Mar 2012 15:41:43 -0400
Message-ID: <D60519DB022FFA48974A25955FFEC08C046085F8@SAM.InterDigital.com>
In-Reply-To: <AABA9EFA-250D-4D9B-8949-EE89FE1F8457@sensinode.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [core] #177: Response suppression for multicast not defined
Thread-Index: Ac0Ahv055FqR9pvuT5ivsq9FGMaUawAANcmA
References: <051.f2c70308ab0d71f7798afa515a549f6b@trac.tools.ietf.org> <066.924a528dfa41671c33a7c32467afea34@trac.tools.ietf.org> <D60519DB022FFA48974A25955FFEC08C046085D1@SAM.InterDigital.com> <AABA9EFA-250D-4D9B-8949-EE89FE1F8457@sensinode.com>
From: "Rahman, Akbar" <Akbar.Rahman@InterDigital.com>
To: Zach Shelby <zach@sensinode.com>
X-OriginalArrivalTime: 12 Mar 2012 19:41:43.0705 (UTC) FILETIME=[27368890:01CD0088]
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: Mon, 12 Mar 2012 19:41:45 -0000

Thanks, Zach.  I will then make sure to read the updated I-D after you
submit it tonight.  Esko and I have some text in our Groupcomm I-D for
multicast support (on the topic of multicast response handling) that we
want to make sure is well coordinated with the coap-09 I-D.


Akbar



-----Original Message-----
From: Zach Shelby [mailto:zach@sensinode.com] 
Sent: Monday, March 12, 2012 3:33 PM
To: Rahman, Akbar
Cc: core issue tracker; core WG
Subject: Re: [core] #177: Response suppression for multicast not defined

Hi Akbar,

These changes are being checked into the SVN as they are closed, and
will show up in the coap-09 submission tonight. By the way, the SVN is
accessible by anyone if you are ever interested in changes as we close
tickets on WG documents:

http://trac.tools.ietf.org/wg/core/trac/browser

Zach

On Mar 12, 2012, at 8:40 PM, Rahman, Akbar wrote:

> Hi Carsten,
> 
> 
> Could you please clarify exactly what change was incorporated into
http://tools.ietf.org/html/draft-ietf-core-coap-08?
> 
> When I look at the Fix #177 cited below 
> 
> http://www.ietf.org/mail-archive/web/core/current/msg02382.html
> 
> it refers to 
> 
> 	"So yes, I think there should be new text in 4.4 that says the
reliability
> 	layer does indicate to the r/r layer that this was a multicast."
> 
> 
> I did not see this type of text in section 4.4 however.  But maybe I a
m missing something?
> 
> 
> 
> Thanks,
> 
> 
> Akbar
> 
> 
> 
> -----Original Message-----
> From: core-bounces@ietf.org [mailto:core-bounces@ietf.org] On Behalf
Of core issue tracker
> Sent: Monday, March 12, 2012 12:25 PM
> To: draft-ietf-core-coap@tools.ietf.org; cabo@tzi.org
> Cc: core@ietf.org
> Subject: Re: [core] #177: Response suppression for multicast not
defined
> 
> #177: Response suppression for multicast not defined
> 
> Changes (by cabo@...):
> 
> * status:  new => closed
> * resolution:   => fixed
> 
> 
> Comment:
> 
> Fixed in [524]:
> 
> Fix #177
> 
> -- 
> --------------------------------+-------------------------------------
> Reporter:  cabo@...              |       Owner:
draft-ietf-core-coap@...
>     Type:  protocol defect     |      Status:  closed
> Priority:  major               |   Milestone:
> Component:  coap                |     Version:
> Severity:  Active WG Document  |  Resolution:  fixed
> Keywords:                      |
> --------------------------------+-------------------------------------
> 
> Ticket URL: </ticket/177#comment:1>
> core <http://tools.ietf.org/core/>
> 
> _______________________________________________
> core mailing list
> core@ietf.org
> https://www.ietf.org/mailman/listinfo/core
> _______________________________________________
> core mailing list
> core@ietf.org
> https://www.ietf.org/mailman/listinfo/core

-- 
Zach Shelby, Chief Nerd, Sensinode Ltd.
http://www.sensinode.com
http://zachshelby.org  - My blog "On the Internet of Things"
http://6lowpan.net - My book "6LoWPAN: The Wireless Embedded Internet"
Mobile: +358 40 7796297