Re: [core] message correlation on CoAP

"R.Vinob chander" <vinobchanderr@ssn.edu.in> Fri, 08 January 2016 15:37 UTC

Return-Path: <vinobchanderr@ssn.edu.in>
X-Original-To: core@ietfa.amsl.com
Delivered-To: core@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 416571A8A79 for <core@ietfa.amsl.com>; Fri, 8 Jan 2016 07:37:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.322
X-Spam-Level: *
X-Spam-Status: No, score=1.322 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oTUJkSGAcffI for <core@ietfa.amsl.com>; Fri, 8 Jan 2016 07:36:58 -0800 (PST)
Received: from mail-io0-x231.google.com (mail-io0-x231.google.com [IPv6:2607:f8b0:4001:c06::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6C4201A8A77 for <core@ietf.org>; Fri, 8 Jan 2016 07:36:58 -0800 (PST)
Received: by mail-io0-x231.google.com with SMTP id 1so242596449ion.1 for <core@ietf.org>; Fri, 08 Jan 2016 07:36:58 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ssn.edu.in; s=ssn; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=O+HWgoSWIgGzNtyVtMA7A0M1ro1mhhs5mUwTbbX5cMs=; b=o0+4vEQ52DMjhXiKacO0AGII0rcJoZngGfMkMtpx1zG41F0lNdNLnhiR9E4HXXOR6L HhhT05rbQPDLS6MUaPmZ+duJE0Y4mWZQeW+pZ5ORGmQ0QNnVBv258e8asnqW1ToHGiGY qzxfeamjDziRCU0Ls9y/Z3JOWB3ZDo9i/mUgA=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=O+HWgoSWIgGzNtyVtMA7A0M1ro1mhhs5mUwTbbX5cMs=; b=MzSjipoMppYNL8431ycS6WwhdVX15K/qyezoFVwqWnNenbA8gwN7O4z6BFlVS1PAA7 hCJ+pgZTTDKny0+96tgZtA5Vqqs1QyQpIlJiRUvVXn62etHUMSHbvY4ezJKhQ4yD6KcZ Mo4xYAbVTfJdfHeuyV3H5XgyNs07bvRO+mmj7qBNGWzPM/NJLkaPD9FDicGnxktRblq1 reKNxKVAxfdJ+xUL6xx0L1jXiy/k8QmRk0/Jk1rG7xgLcNvvXDbohr97Nwep4D3o2NU5 heRPyU4amLGeXa9sXxjSd6MQPpP7eAk1EgfVuDF3MeFfW5Um37jkK1NuodXl2W2nY5ff nkIA==
X-Gm-Message-State: ALoCoQnwF6NEFAgYr6E026qIM+AulAh5mny6jm8T8hi6w7IeC4QPPvmNlzTrdqs6ZBKQp0XuzHWQZ+ELJP+DB/3UeSeNDuHI6tO7mghQ/MEoRKHQceEmUXV6E67hl0UQo3T0RT+ONl/D0A8ZkMp+3qj2I0b0320V+A==
MIME-Version: 1.0
X-Received: by 10.107.3.71 with SMTP id 68mr59595543iod.48.1452267417544; Fri, 08 Jan 2016 07:36:57 -0800 (PST)
Received: by 10.79.13.147 with HTTP; Fri, 8 Jan 2016 07:36:57 -0800 (PST)
In-Reply-To: <CADrU+dKv6GhD3Rkw5S4EEqBFJu6YqxqUCmLZ74Tey8dT3fAy3A@mail.gmail.com>
References: <CAEgyW4r1w=5jdBa8Rxs40ee+2kf=qVgLT7mSa5LxwdKCeF4nPQ@mail.gmail.com> <CADrU+dKv6GhD3Rkw5S4EEqBFJu6YqxqUCmLZ74Tey8dT3fAy3A@mail.gmail.com>
Date: Fri, 08 Jan 2016 21:06:57 +0530
Message-ID: <CAEgyW4oLKrD4EMxsU7v+K0CjM8_KDUii5mRw9-1TiPjv4Et26A@mail.gmail.com>
From: "R.Vinob chander" <vinobchanderr@ssn.edu.in>
To: robert.cragie@gridmerge.com
Content-Type: multipart/alternative; boundary="001a113eb35c8ac36f0528d45bda"
Archived-At: <http://mailarchive.ietf.org/arch/msg/core/Eg0t1E-JQCtkK0BwnhrFNc_BX1U>
Cc: "core@ietf.org" <core@ietf.org>
Subject: Re: [core] message correlation on CoAP
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.15
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: <https://mailarchive.ietf.org/arch/browse/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: Fri, 08 Jan 2016 15:37:01 -0000

thank u... u r right.....but the a receiver may get multiple copies of
the same message if the ACK is lost in transit..(sec. 4.5). So in such
cases the same message ID is used within the EXCHANGE_LIFETIME.

Hence i think probably the sentence should be  "The same Message ID
MUST NOT be reused (in communicating with the same endpoint) within
the first timeout for CON and MAX_LATENCY for NON"

4.4.  Message Correlation

The same Message ID MUST NOT be reused (in communicating with the

   same endpoint) within the EXCHANGE_LIFETIME


4.5.  Message Deduplication

   A recipient might receive the same Confirmable message (as indicated
   by the Message ID and source endpoint) multiple times within the
   EXCHANGE_LIFETIME


4.8.2. 		

NON_LIFETIME is the time from sending a Non-confirmable message to
   the time its Message ID can be safely reused.  *If multiple
   transmission of a NON message is not used, its value is
   MAX_LATENCY, or 100 seconds*.  However, *a CoAP sender might send a
   NON message multiple times*, in particular for multicast
   applications.  While the period of reuse is not bounded by the
   specification, an expectation of reliable detection of duplication
   at the receiver is on the timescales of MAX_TRANSMIT_SPAN.
   Therefore, for this purpose, it is safer to use the value:

      MAX_TRANSMIT_SPAN + MAX_LATENCY



please clarify..


On Fri, Jan 8, 2016 at 3:45 PM, Robert Cragie <robert.cragie@gridmerge.com>
wrote:

> I think it is correct as written - the same ID must not be used within
> EXCHANGE_LIFETIME. You can add NON_LIFETIME as well. The message ID
> certainly can be reused beyond those lifetimes as the occurrence of the
> message ID for acknowledgement or duplication detection is no longer
> expected.
>
> Robert
>
> On 8 January 2016 at 03:58, R.Vinob chander <vinobchanderr@ssn.edu.in>
> wrote:
>
>> Hi All,
>>
>>   sec. 4.4 of RFC 7252 specifies
>>
>>   The same Message ID MUST NOT be reused (in communicating with the
>>    same endpoint) within the EXCHANGE_LIFETIME
>>
>>   I think the sentence is incorrect and should b,
>>
>>   The same Message ID MUST NOT be reused (in communicating with the
>>    same endpoint) *beyond* the EXCHANGE_LIFETIME/NON_LIFETIME
>>
>> Regards,
>> --
>> R. Vinob chander, B.E., M.E., (Ph.D)
>> Assistant Professor, Department of IT
>> SSN College of Engineering,
>> Old Mahabalipuram Road
>> Kalavakkam - 603 110
>> Tamil Nadu, India
>> www.ssn.edu.in
>>
>> Phone: +9144-27469700 , +91 44 27474844/45/46
>> Extn: 370
>> Mob: +91-9566101580
>>
>> ::DISCLAIMER::
>>
>> ---------------------------------------------------------------------
>> The contents of this e-mail and any attachment(s) are confidential and
>> intended for the named recipient(s) only. Views or opinions, if any,
>> presented in this email are solely those of the author and may not
>> necessarily reflect the views or opinions of SSN Institutions (SSN) or its
>> affiliates. Any form of reproduction, dissemination, copying, disclosure,
>> modification, distribution and / or publication of this message without the
>> prior written consent of authorized representative of SSN is strictly
>> prohibited. If you have received this email in error please delete it and
>> notify the sender immediately.
>> ---------------------------------------------------------------------
>> Header of this mail should have a valid DKIM signature for the domain ssn.edu.in <http://www.ssn.edu.in/>
>>
>>
>> _______________________________________________
>> core mailing list
>> core@ietf.org
>> https://www.ietf.org/mailman/listinfo/core
>>
>>
>


-- 
R. Vinob chander, B.E., M.E., (Ph.D)
Assistant Professor, Department of IT
SSN College of Engineering,
Old Mahabalipuram Road
Kalavakkam - 603 110
Tamil Nadu, India
www.ssn.edu.in

Phone: +9144-27469700 , +91 44 27474844/45/46
Extn: 370
Mob: +91-9566101580

-- 
::DISCLAIMER:: 

---------------------------------------------------------------------
The contents of this e-mail and any attachment(s) are confidential and
intended for the named recipient(s) only. Views or opinions, if any,
presented in this email are solely those of the author and may not
necessarily reflect the views or opinions of SSN Institutions (SSN) or its
affiliates. Any form of reproduction, dissemination, copying, disclosure,
modification, distribution and / or publication of this message without the
prior written consent of authorized representative of SSN is strictly
prohibited. If you have received this email in error please delete it and
notify the sender immediately.
---------------------------------------------------------------------
Header of this mail should have a valid DKIM signature for the domain ssn.edu.in <http://www.ssn.edu.in/>