[Roll] Semantics of DAO ACK

Joakim Eriksson <joakime@sics.se> Tue, 29 September 2015 19:44 UTC

Return-Path: <joakime@sics.se>
X-Original-To: roll@ietfa.amsl.com
Delivered-To: roll@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3013E1B2BDE for <roll@ietfa.amsl.com>; Tue, 29 Sep 2015 12:44:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham
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 yoqVpcKo15zg for <roll@ietfa.amsl.com>; Tue, 29 Sep 2015 12:44:57 -0700 (PDT)
Received: from mail-la0-f43.google.com (mail-la0-f43.google.com [209.85.215.43]) (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 4F24A1B2BBF for <roll@ietf.org>; Tue, 29 Sep 2015 12:44:57 -0700 (PDT)
Received: by laer8 with SMTP id r8so21411545lae.2 for <roll@ietf.org>; Tue, 29 Sep 2015 12:44:55 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:content-type:mime-version:subject:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to; bh=HuTcFwBvMwTGd2GMSdMiMxTbLX8mo//ZBeIZRnQgZB0=; b=WlluU6kpny7THSad+tHRgWk7iIhvmKW0Mwi8AFiIb1q69ht43+3W9k30u88V8YwA2K BLBE10dW4os3NcV5MrbP4RJbHwGQYxnSFUKE4MLttepJzY5/5oP6+qTaYW96Qag3x0s8 1dtH8rKet4Rb8YE7YAo2TPZYdNwXO7/qBLRDCchpLPsLmqOuucz3+ISWI+YYKbVLA85h L5+JgpB5aTrqUOZ7+WjcwnNPEiBxuIcTq+SK3I1+kom3bRmpCqZRwfTFuhrUAn8J3sG/ SX0R9/6qXvVFLIBMl4MVsm/fMJ8dbprY3EduvcRK14BVq28t7m3yKlkt9a0Syhio5Yb3 YfXQ==
X-Gm-Message-State: ALoCoQkjxSyfOfvkQO0BMhXyI4R5HFT48MNrBwa20q2GMXHJQQYvYD/fxeiqSRkRUwl4NepD3K4n
X-Received: by 10.25.151.65 with SMTP id z62mr5141747lfd.21.1443555895224; Tue, 29 Sep 2015 12:44:55 -0700 (PDT)
Received: from [192.168.1.102] (h31n15-sbg-a11.ias.bredband.telia.com. [195.67.245.31]) by smtp.gmail.com with ESMTPSA id x128sm2992309lfd.26.2015.09.29.12.44.54 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 29 Sep 2015 12:44:54 -0700 (PDT)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\))
From: Joakim Eriksson <joakime@sics.se>
In-Reply-To: <6d21d0f86ab14ae7a99ff9fe6873b1fd@XCH-RCD-001.cisco.com>
Date: Tue, 29 Sep 2015 21:44:53 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <C885EE62-D889-4229-9CCB-B3CB540F5692@sics.se>
References: <DB5PR01MB10807DAF503BBFF45787599C80420@DB5PR01MB1080.eurprd01.prod.exchangelabs.com> <6d21d0f86ab14ae7a99ff9fe6873b1fd@XCH-RCD-001.cisco.com>
To: Routing Over Low power and Lossy networks <roll@ietf.org>
X-Mailer: Apple Mail (2.2104)
Archived-At: <http://mailarchive.ietf.org/arch/msg/roll/cweuKlDczp11L5LmJgNR90_s14I>
Subject: [Roll] Semantics of DAO ACK
X-BeenThere: roll@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: Routing Over Low power and Lossy networks <roll@ietf.org>
List-Id: Routing Over Low power and Lossy networks <roll.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/roll>, <mailto:roll-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/roll/>
List-Post: <mailto:roll@ietf.org>
List-Help: <mailto:roll-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/roll>, <mailto:roll-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 29 Sep 2015 19:44:59 -0000

Hello All,

I have spend quite some time to get a more stable implementation of DAO handling
for Contiki RPL and I am currently looking into DAO aggregation. But I realised that
it is for me not 100% clear what a node that receives a DAO with several prefixes to
be registered but can only accept a sub-set of them. Should it be a DAO_NACK in
this case or is there any other way to handle that case?

If each would have been sent separately it is obvious that the receiving node can
do a NACK when the routing table is full and therefore it is possible to get fine-grained
answers. But with aggregation of DAOs this is not the case.

Any ideas?

Best regards,
— Joakim Eriksson, SICS