[6tsch] Confirmation Messages?

Qin Wang <qinwang@berkeley.edu> Fri, 30 August 2013 17:47 UTC

Return-Path: <qinwang@berkeley.edu>
X-Original-To: 6tsch@ietfa.amsl.com
Delivered-To: 6tsch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E816111E80FA for <6tsch@ietfa.amsl.com>; Fri, 30 Aug 2013 10:47:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.901
X-Spam-Level:
X-Spam-Status: No, score=-2.901 tagged_above=-999 required=5 tests=[AWL=0.075, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
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 bckMd+f1C8fY for <6tsch@ietfa.amsl.com>; Fri, 30 Aug 2013 10:47:32 -0700 (PDT)
Received: from mail-vb0-f49.google.com (mail-vb0-f49.google.com [209.85.212.49]) by ietfa.amsl.com (Postfix) with ESMTP id 973CF11E8111 for <6tsch@ietf.org>; Fri, 30 Aug 2013 10:47:32 -0700 (PDT)
Received: by mail-vb0-f49.google.com with SMTP id w16so1496914vbb.8 for <6tsch@ietf.org>; Fri, 30 Aug 2013 10:47:32 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:date:message-id:subject:from:to :content-type; bh=XX0iR7dbjUibMrzxEkPquMFEAGZjDtmW8Kjb/vXWMvg=; b=aQJJe4q5Dekc7gzRxGat61yFydlv4lshpEr230ulKtoqkEhjJUX5zh8C+YxZ9JQWNH ujH5SibELeYkQiDW6EmrFPFffGB3lGfo4KWzv4Rj/a/nWl7ME/46kdhn1JIQ2qAEiX3H cmjW7D6xnroVg7O1enxF1/87jLz81cFwWD4x3UgXG9Ehged7yOvhWwusYRbkJaVlZ5we EsRh53T87ok4XTpRIrZMtuOy3hnqn8Q3NRpEznkkolIHE3QOVYlM5+DwFFHguGmSINwO Y2pNljkEpVHrP91Z6QGdHytZeM1IQMTElvwnKwPwasHLzGY3p0/EtxMV1cjZlqDzYupB xibA==
X-Gm-Message-State: ALoCoQnNyT08wdVu4RZRP9ZtM1DyoLdt04MZQchkDo8dUGMAMS6W9l+DePsTpNnobpf6MkmU7L2U
MIME-Version: 1.0
X-Received: by 10.220.181.136 with SMTP id by8mr9455062vcb.11.1377884852074; Fri, 30 Aug 2013 10:47:32 -0700 (PDT)
Received: by 10.220.116.135 with HTTP; Fri, 30 Aug 2013 10:47:32 -0700 (PDT)
Date: Sat, 31 Aug 2013 01:47:32 +0800
Message-ID: <CAAzoce768TLENEYM34OEasDdTTHWTN4DRmEaOOZHOf_gBR6smQ@mail.gmail.com>
From: Qin Wang <qinwang@berkeley.edu>
To: "6tsch@ietf.org" <6tsch@ietf.org>
Content-Type: multipart/alternative; boundary="047d7bf0f67a26794804e52dd143"
Subject: [6tsch] Confirmation Messages?
X-BeenThere: 6tsch@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Discuss link layer model for Deterministic IPv6 over the TSCH mode of IEEE 802.15.4e, and impacts on RPL and 6LoWPAN such as resource allocation" <6tsch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/6tsch>, <mailto:6tsch-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/6tsch>
List-Post: <mailto:6tsch@ietf.org>
List-Help: <mailto:6tsch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/6tsch>, <mailto:6tsch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Aug 2013 17:47:38 -0000

Hi all,

In this thread, we will continue the discussion about Confirmation message.
Here is some background information.

Context: e.g.
    - node sends a report and want to know if the report is accepted.,
    - ME sends a action request and want to know if/when the action taken.
Options:
   (1) Nothing
   (2) Rely on transport mechanism (e.g. confirmable CoAP message)
   (3) App-level ACK type
   (4) Use different flow (i.e. action flow)

IMHO, different control flow may have different requirement for
confirmation message.
    (1) Action Flow, needs a App-level confirmation, like Succ/Fail
    (2) Query Flow, automatically has the confirmation, i.e. the message
packet corresponding to a specific query.
    (3) Report Flow and Event Flow, option (1)-(3) are OK, but I prefer
option (1) and (3), i.e. the confirmation message is an option, but if a
confirmation message is needed, it should be App-level Ack, instead of
transport layer confirmation, which will give 6top more flexibility.

What do you think?

Thanks
Qin