Re: [Anima-signaling] GRASP and renumbering: suggestions

Jéferson Campos Nobre <jcnobre@inf.ufrgs.br> Fri, 27 May 2016 01:01 UTC

Return-Path: <jeferson.nobre@gmail.com>
X-Original-To: anima-signaling@ietfa.amsl.com
Delivered-To: anima-signaling@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 980CB12D784 for <anima-signaling@ietfa.amsl.com>; Thu, 26 May 2016 18:01:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.401
X-Spam-Level:
X-Spam-Status: No, score=-2.401 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.198, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 qRxMHXUaUVEt for <anima-signaling@ietfa.amsl.com>; Thu, 26 May 2016 18:01:26 -0700 (PDT)
Received: from mail-io0-f178.google.com (mail-io0-f178.google.com [209.85.223.178]) (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 4F0A612D17D for <anima-signaling@ietf.org>; Thu, 26 May 2016 18:01:26 -0700 (PDT)
Received: by mail-io0-f178.google.com with SMTP id 190so63566269iow.1 for <anima-signaling@ietf.org>; Thu, 26 May 2016 18:01:26 -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:references:in-reply-to:from:date :message-id:subject:to; bh=U23VMfRVdrpz12nZNalr+klXymvBEwC/asRHW0njWgo=; b=Hw2iPuOWkiWwylzEMcS7qfpOpOUXH6vPQtDVWELdWQ+ZL098FVDFrSsDt0Oy/BA7R+ bRW+wF3oXS9RxiD3P9hXt96ogZIV0YJ0iIRos/yD4mV8u1J3QkZeRTeeVDRa7Dyb2IsE /d3hoaP+LAiybdhzF0upcGbfjhYgLpInwsf9hwmj1nU08twXKgeePji/EPyZO2GfWyS7 3lVowyhpfDbt6I1LOldRvGY+DSw75OXIr9tgoa66OeKL6Q3XjTcJ7Do0CW8TrJE7BkY6 YRn+bLZRMPsmMACQh1MBIocZKtNt212uc0aJmhSMC84bnrnijl///br5KT6n9cufF2qT hh2Q==
X-Gm-Message-State: ALyK8tIEw6pkC8nPoFJ64bqrFHncmOIYWFlRGEpMyTgHpfK7JGcBXJ5GSL9CW3Fxp482FFr0nW9uu8aPH75hNw==
X-Received: by 10.107.133.205 with SMTP id p74mr13108020ioi.71.1464310885573; Thu, 26 May 2016 18:01:25 -0700 (PDT)
MIME-Version: 1.0
References: <36393312-d3e2-4d78-588d-d22c4f6766c2@gmail.com>
In-Reply-To: <36393312-d3e2-4d78-588d-d22c4f6766c2@gmail.com>
From: =?UTF-8?Q?J=C3=A9ferson_Campos_Nobre?= <jcnobre@inf.ufrgs.br>
Date: Fri, 27 May 2016 01:01:16 +0000
Message-ID: <CABv6xLsw7y1hCgB9YBRYj9AA5cSQ=mgrwNW-FH5bXG3ZSa2CMw@mail.gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, Anima signaling DT <anima-signaling@ietf.org>
Content-Type: multipart/alternative; boundary=001a113ed1ec2cec450533c872f0
Archived-At: <http://mailarchive.ietf.org/arch/msg/anima-signaling/7J06v2AqVhorlUxRHxMuTYUqDQY>
Subject: Re: [Anima-signaling] GRASP and renumbering: suggestions
X-BeenThere: anima-signaling@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Mailing list for the signaling design team of the ANIMA WG <anima-signaling.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/anima-signaling>, <mailto:anima-signaling-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/anima-signaling/>
List-Post: <mailto:anima-signaling@ietf.org>
List-Help: <mailto:anima-signaling-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/anima-signaling>, <mailto:anima-signaling-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 27 May 2016 01:01:29 -0000

Hi Brian.
Comments below.
Best.
Jéferson

Em qui, 26 de mai de 2016 às 20:46, Brian E Carpenter <
brian.e.carpenter@gmail.com> escreveu:

> Hi design team. I expect you saw the recent messages about renumbering,
> and you may have seen the big discussion in 6man about stable addresses.
>
> I have two suggestions for GRASP.
>
> 1) In the description of discovery, we say this:
>
>  After a GRASP device successfully discovers a Discovery
>  Responder supporting a specific objective, it MUST cache this
>  information.  This cache record MAY be used for future
>  negotiation or synchronization, and SHOULD be passed on when
>  appropriate as a Divert option to another Discovery Initiator.
>  The cache lifetime is an implementation choice that MAY be
>  modified by network Intent.
>
> I suggest adding something more here:
>
>  In some environments, unexpected address renumbering might occur.
>  In such cases, the cache lifetime SHOULD be short compared to
>  the expected address lifetime and a mechanism to flush the
>  discovery cache SHOULD be implemented.
>

I'm not an english native speaker, but I would expect MUSTs instead of
SHOULDs. Or maybe this is related to the "some environments" restriction...


> 2) And in the API, I suggest that the 'discover' function
> needs an optional 'flush' parameter, to specify that previously
> discovered locators must be flushed first.
>
> I am reluctant to add a TTL to discovery responses. It's a complication,
> and experience with DNS is that resolvers often ignore the TTL.
>

I believe most discovery protocols work use TTL, thus I would favor using
also. However, I'm not sure how this would impact the signaling protocol
and, consequently, the current implementations.


> Comments?
>
>    Brian
>
> _______________________________________________
> Anima-signaling mailing list
> Anima-signaling@ietf.org
> https://www.ietf.org/mailman/listinfo/anima-signaling
>