IETF Logo Mail Archive

Re: [6tisch] [Roll] Fwd: New Version Notification for draft-thubert-roll-unaware-leaves-02.txt

"Pascal Thubert (pthubert)" <pthubert@cisco.com> Mon, 26 February 2018 17:10 UTC

Return-Path: <pthubert@cisco.com>
X-Original-To: 6tisch@ietfa.amsl.com
Delivered-To: 6tisch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4F4C3124BFA; Mon, 26 Feb 2018 09:10:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.531
X-Spam-Level:
X-Spam-Status: No, score=-14.531 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
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 ecWDBv3PXBhv; Mon, 26 Feb 2018 09:10:30 -0800 (PST)
Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 22BDD1205F0; Mon, 26 Feb 2018 09:10:30 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1462; q=dns/txt; s=iport; t=1519665030; x=1520874630; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=eqa/g6vbsbTWFMVxNekt5JNkzDlqYrFw0si77vd4WOY=; b=gQnJTqjkrqyGonF5uml9JdrL2FzN6sp0XaMOO9SSHCOsmTq1h6tWMfId Dl0VgomZGlegxT01gmJ9SY1XGagnV3fNS+G2NHKmKMEl0m5aV4yLJMRrG G6Aww+BBMlTXBQIFvrJ5wODWhUy8TWrMAQrhgfXevoSfq1Scrq0L31p7C k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AqAQB1PpRa/5tdJa1dGQEBAQEBAQEBAQEBAQcBAQEBAYNPgVYoCo1sjX6CAoEWlgWCFgqCAYMyAoJFVBgBAgEBAQEBAQJrKIUjAQEBAQN3AgwEAgEIEQQBAQEnBzIUCQgCBA4FCIUIrVuIbIIUAQEBAQEBAQEBAQEBAQEBAQEBAQEBHYdCgVeBZoMthQWGDgWReI9pCQKUFYIPkFqJZ4thAhEZAYEuAR44gVFwFYJ9gkMcFoFld4tEgRcBAQE
X-IronPort-AV: E=Sophos;i="5.47,397,1515456000"; d="scan'208";a="360623218"
Received: from rcdn-core-4.cisco.com ([173.37.93.155]) by rcdn-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 26 Feb 2018 17:10:29 +0000
Received: from XCH-ALN-002.cisco.com (xch-aln-002.cisco.com [173.36.7.12]) by rcdn-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id w1QHATYM022052 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Mon, 26 Feb 2018 17:10:29 GMT
Received: from xch-rcd-001.cisco.com (173.37.102.11) by XCH-ALN-002.cisco.com (173.36.7.12) with Microsoft SMTP Server (TLS) id 15.0.1320.4; Mon, 26 Feb 2018 11:10:28 -0600
Received: from xch-rcd-001.cisco.com ([173.37.102.11]) by XCH-RCD-001.cisco.com ([173.37.102.11]) with mapi id 15.00.1320.000; Mon, 26 Feb 2018 11:10:28 -0600
From: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
To: Michael Richardson <mcr+ietf@sandelman.ca>
CC: Routing Over Low power and Lossy networks <roll@ietf.org>, "6tisch@ietf.org" <6tisch@ietf.org>
Thread-Topic: [6tisch] [Roll] Fwd: New Version Notification for draft-thubert-roll-unaware-leaves-02.txt
Thread-Index: AQHTqvUqiyrunT5oXUuWaZlTwS084qOulacfgAFHRoCAAd4mgIABA3OAgAQ0OmA=
Date: Mon, 26 Feb 2018 17:09:58 +0000
Deferred-Delivery: Mon, 26 Feb 2018 17:09:29 +0000
Message-ID: <ff2dab9e1acf467ab99a1e73b8e452a4@XCH-RCD-001.cisco.com>
References: <151920480372.9603.17635052466831884104.idtracker@ietfa.amsl.com> <0507EB1B-3B42-4108-A511-EEE413CF0FE4@cisco.com> <10405.1519253755@obiwan.sandelman.ca> <aeca79527d934ed181b3498c83a03843@XCH-RCD-001.cisco.com> <13406.1519412153@obiwan.sandelman.ca>
In-Reply-To: <13406.1519412153@obiwan.sandelman.ca>
Accept-Language: fr-FR, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.61.212.148]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/6tisch/emLXWvWr9xZ-NMwfHkLpeg0qFX0>
Subject: Re: [6tisch] [Roll] Fwd: New Version Notification for draft-thubert-roll-unaware-leaves-02.txt
X-BeenThere: 6tisch@ietf.org
X-Mailman-Version: 2.1.22
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" <6tisch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/6tisch>, <mailto:6tisch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/6tisch/>
List-Post: <mailto:6tisch@ietf.org>
List-Help: <mailto:6tisch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/6tisch>, <mailto:6tisch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Feb 2018 17:10:31 -0000

That's true too Michael, but it is not ours pec, just the normal ND over transit links.
Cheers,
Pascal

> -----Original Message-----
> From: Michael Richardson [mailto:mcr+ietf@sandelman.ca]
> Sent: vendredi 23 février 2018 19:56
> To: Pascal Thubert (pthubert) <pthubert@cisco.com>
> Cc: Routing Over Low power and Lossy networks <roll@ietf.org>;
> 6tisch@ietf.org
> Subject: Re: [6tisch] [Roll] Fwd: New Version Notification for draft-thubert-
> roll-unaware-leaves-02.txt
> 
> 
> Pascal Thubert (pthubert) <pthubert@cisco.com> wrote:
>     > If the 'R' flag is not set, then the Registering Node is expected to be a RPL
>     > router that handles the reachability of the Registered Address by itself.
>     > This document also specifies a keep-alive EDAR message that the RPL
> Root may
>     > use to maintain an existing state in the 6LBR upon receiving DAO
> messages.
>     > The EDAR message may only act as a refresher and can only update the
> Lifetime
>     > and the TID of the state in the 6LBR.  A RPL router SHOULD NOT set the
> 'R' flag.
> 
> Can we also say that a 6LR, upon seeing a ND *without* the EARO option,
> should assume it's like the R flag is set?  Or is such a node just non-operable?
> (Clearly, such a node can't move from DODAG to DODAG...)
> 
> --
> Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
> -= IPv6 IoT consulting =-
> 
>

v2.23.0 | Report a Bug | By Email