[6lo] rgding 6775-update/EARO
Rahul Jadhav <rahul.ietf@gmail.com> Wed, 19 July 2017 14:22 UTC
Return-Path: <rahul.ietf@gmail.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 69A35131D6F for <6lo@ietfa.amsl.com>; Wed, 19 Jul 2017 07:22:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 0s78fMlwLed7 for <6lo@ietfa.amsl.com>; Wed, 19 Jul 2017 07:21:49 -0700 (PDT)
Received: from mail-ua0-x22a.google.com (mail-ua0-x22a.google.com [IPv6:2607:f8b0:400c:c08::22a]) (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 88665131D0C for <6lo@ietf.org>; Wed, 19 Jul 2017 07:21:49 -0700 (PDT)
Received: by mail-ua0-x22a.google.com with SMTP id 35so1035573uax.3 for <6lo@ietf.org>; Wed, 19 Jul 2017 07:21:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=1HOkVviKDr1rvUQq8gHVQcNOrwJRV4w/C6UW71tiWWU=; b=QEMisl1a/1cELWdoT15OBqx9PtyZTfAEm8188zC5naD3iwE8SDb2B75JL7rRkgZioj EN2JuSfkiq6aoaiebQkeH3nKZpA+the6dl9FCoJehlifZj8me1SCoOxUBr/3ZUZPYlZD kuH8enpf2CQ0vc/NG8NCh1VQhqzuoYRhTDwfNmZzbr4FE3HMw2tFFfJg+xgogIBYK9sc nIx+AvjaCtq1uosXxweYCenaq7kr0P2YCgFFYCFnX0HXyrOkUNHrgC2+fNMdv4oi9ZgD GOlZrzlIhvnV2qWXKv+ICCh5CfqmcuvsMw86ztTrF9xXFqYfDEavnLP+9SZ8X983Bg61 Rs3w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=1HOkVviKDr1rvUQq8gHVQcNOrwJRV4w/C6UW71tiWWU=; b=fAdyzf+9BRCB2h6h8FtBO/cDa+j8bgWvG51+hpFhUOBbdEUbs1ZoEcEodw/AqYUP0f DTfcIFfk1skv4Kuo3eSEvGqd7fxYyQrOU2ZCzlFLgsnRnde+r76CXvz1Z4P5KXC3CjyT nVToQz/RVWWPKEyMEabxWS08FdpKOMnFdOFrZ+DeTYD08UhmXjcdUhILtr8yIlPaQMe9 6bEvDpey4tap3ZQD9u+LRtGBM3UuwL1NGkfTEp+AkkpUxO6p2ANN4Htxb1GoCulXPFkp dV+105+grf5IqCPWpneh8OXYKFYfHM4JUx+E1KZC4DO+huuA4HznejLMZfd7uT/uEP+b ZkAA==
X-Gm-Message-State: AIVw113M/bmzt3zaG7LUasyt4/YLhUGjFuNUd0iW7D25sCjoymjk66Do ACkpc8vEw2cRlPgLLZYC/srHhdkhZA==
X-Received: by 10.159.60.111 with SMTP id w47mr134256uah.207.1500474108493; Wed, 19 Jul 2017 07:21:48 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.103.90.71 with HTTP; Wed, 19 Jul 2017 07:21:48 -0700 (PDT)
From: Rahul Jadhav <rahul.ietf@gmail.com>
Date: Wed, 19 Jul 2017 16:21:48 +0200
Message-ID: <CAO0Djp3w=4Gz6Dthh7DsEGGHvu_Tha0CLav1_vRqk1169VsB1A@mail.gmail.com>
To: lo <6lo@ietf.org>
Content-Type: multipart/alternative; boundary="f403043649d43b45b80554ac5ace"
Archived-At: <https://mailarchive.ietf.org/arch/msg/6lo/QkdL6TuXB41wOwe7gmRA5YMEGlQ>
Subject: [6lo] rgding 6775-update/EARO
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, 19 Jul 2017 14:22:02 -0000
Hello Pascal, This is the same query as what i raised during the 6lo session. Like it was pointed out, better to take it on ML. The new mechanism described in the draft allows a proxy registration on behalf of the "target node" using EARO. My question is: Will de-registration be possible for such targets, especially considering that state information (in the form of TID) is maintained for such registrations? It will be helpful to clarify in the document. Thanks, Rahul
- [6lo] rgding 6775-update/EARO Rahul Jadhav
- Re: [6lo] rgding 6775-update/EARO Pascal Thubert (pthubert)
- Re: [6lo] rgding 6775-update/EARO Pascal Thubert (pthubert)