Re: [6lo] Draft applicability for 6775bis

"Pascal Thubert (pthubert)" <pthubert@cisco.com> Wed, 29 March 2017 23:20 UTC

Return-Path: <pthubert@cisco.com>
X-Original-To: 6lo@ietfa.amsl.com
Delivered-To: 6lo@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 76DF01294A6 for <6lo@ietfa.amsl.com>; Wed, 29 Mar 2017 16:20:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.522
X-Spam-Level:
X-Spam-Status: No, score=-14.522 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, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, 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 55vH3ZO8yRfP for <6lo@ietfa.amsl.com>; Wed, 29 Mar 2017 16:20:58 -0700 (PDT)
Received: from rcdn-iport-3.cisco.com (rcdn-iport-3.cisco.com [173.37.86.74]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3005E12946D for <6lo@ietf.org>; Wed, 29 Mar 2017 16:20:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1254; q=dns/txt; s=iport; t=1490829658; x=1492039258; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=b2wBWLUlYzLqhOvS6gdiI8cslHQjzQS4nN0VTQ6gxyQ=; b=gy/rOvqk1Qm2yR3OvDrSYPk7A60LeRftFXeAL1Por98C2phZXCEzdwuN KY1JQ0FKLpe5gCVz50wgAUlwUJxKk3gr7r8WYQl9+hCLYMHRRPG7HgPn1 d7Xa/DBb8I8AqwC9rJYmp7AByQUjKRn35l2tUM0N5+/s4bWPU6bzvLMkJ Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0A3AwALQNxY/4YNJK1eGgEBAQECAQEBAQgBAQEBg1WBbJ9El12GIgKDQ0MUAQIBAQEBAQEBayiFFgEEAXkFCwIBCEYyJQIEDgWKAgiwNIpYAQEBAQEBAQEBAQEBAQEBAQEBAQEBHYZOggWCaoRUgzSCMQWQIoVuhlABkk8KkSmTaQE2IYEEWRVSAYZGdYk2AQEB
X-IronPort-AV: E=Sophos;i="5.36,243,1486425600"; d="scan'208";a="216048549"
Received: from alln-core-12.cisco.com ([173.36.13.134]) by rcdn-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 29 Mar 2017 23:20:57 +0000
Received: from XCH-ALN-003.cisco.com (xch-aln-003.cisco.com [173.36.7.13]) by alln-core-12.cisco.com (8.14.5/8.14.5) with ESMTP id v2TNKvlF001947 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 29 Mar 2017 23:20:57 GMT
Received: from xch-rcd-001.cisco.com (173.37.102.11) by XCH-ALN-003.cisco.com (173.36.7.13) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Wed, 29 Mar 2017 18:20:56 -0500
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.1210.000; Wed, 29 Mar 2017 18:20:56 -0500
From: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
To: Erik Nordmark <nordmark@sonic.net>
CC: Lorenzo Colitti <lorenzo@google.com>, Christian Huitema <huitema@huitema.net>, "6lo@ietf.org" <6lo@ietf.org>
Thread-Topic: [6lo] Draft applicability for 6775bis
Thread-Index: AQHSqKQbWHolHsHaNE+4D4LSYGcLkqGsdPS4
Date: Wed, 29 Mar 2017 23:20:56 +0000
Message-ID: <E106117D-74DA-457B-94F9-3082082371E1@cisco.com>
References: <0d33195c-d828-1d5b-6a49-ca23d9d4a793@sonic.net>
In-Reply-To: <0d33195c-d828-1d5b-6a49-ca23d9d4a793@sonic.net>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
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/6lo/r7inTS58F8b2ilREnUFrjCb-fVg>
Subject: Re: [6lo] Draft applicability for 6775bis
X-BeenThere: 6lo@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Mailing list for the 6lo WG for Internet Area issues in IPv6 over constrained node networks." <6lo.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/6lo>, <mailto:6lo-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/6lo/>
List-Post: <mailto:6lo@ietf.org>
List-Help: <mailto:6lo-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/6lo>, <mailto:6lo-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Mar 2017 23:20:59 -0000

Hello Erik 
Superb!

On this particular sentence 

"
 Example are the router having run out of space, the host having a stale sequence number, or the host is using an address which does not match the prefix(es) for the link. In such cases the host will receive an error to help diagnose the issue and retry.
"

 I'd suggest:
" Examples are the router having run out of space, a registration bearing a stale sequence number (e.g. denoting a movement of the host after this registration was placed), a host misbehaving and attempting to register an invalid address such as the UNSPECIFIED addresses, or the host using an address which is not topologically correct on that link. In such cases the host will receive an error to help diagnose the issue and may retry, possibly with a different address, and possibly via a different 6LR.

"


Regards,

Pascal

> Le 29 mars 2017 à 10:49, Erik Nordmark <nordmark@sonic.net> a écrit :
> 
> Example are the router having run out of space, the host having a stale sequence number, or the host is using an address which does not match the prefix(es) for the link. In such cases the host will receive an error to help diagnose the issue and retry.