IETF Logo Mail Archive

Re: [Anima-signaling] Signaling requirements

Brian E Carpenter <brian.e.carpenter@gmail.com> Mon, 11 May 2015 20:47 UTC

Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: anima-signaling@ietfa.amsl.com
Delivered-To: anima-signaling@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6C6071A9034 for <anima-signaling@ietfa.amsl.com>; Mon, 11 May 2015 13:47:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.7
X-Spam-Level:
X-Spam-Status: No, score=-1.7 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, MIME_8BIT_HEADER=0.3, SPF_PASS=-0.001] autolearn=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 OrergcQBD6bL for <anima-signaling@ietfa.amsl.com>; Mon, 11 May 2015 13:47:30 -0700 (PDT)
Received: from mail-pd0-x22c.google.com (mail-pd0-x22c.google.com [IPv6:2607:f8b0:400e:c02::22c]) (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 170ED1A70FE for <anima-signaling@ietf.org>; Mon, 11 May 2015 13:47:30 -0700 (PDT)
Received: by pdbqa5 with SMTP id qa5so152960021pdb.1 for <anima-signaling@ietf.org>; Mon, 11 May 2015 13:47:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=oJXUkkQlVWzUXVGtO0e1YftpFLatsrA9EwDed4fj3r8=; b=wQh268FP2iYL2w3No+ZglKju+g5vzaCIlwXTLKHv3eshkxv/AjZ70Bj/JTiYJedBME ewoAzcw+K58nBDrQJn0DPfPactKMM5ynYzLTypKM6m0QdgaK0f+fIXpFFjGNltND4vhP /AWMGub3+BAEbGK8mdiGqP7FDS0KMy7hEGjRLWA++gs2dsYDVfgUl+p+ei8l7p5YuvuI h+p2uQzO/LzatSA9bQ7pCo1HqwWNDOpWK9uUw/2n2bbFSOjxI3UkXlJa3Ea9KffjnSm+ esml3xTcRzfKP0Uaz+7rqlARg29vcbN8kp6AquAV0A9cmQ5WGs2iZNsHN/ZhjcZlUusE l4AQ==
X-Received: by 10.66.193.228 with SMTP id hr4mr22500125pac.48.1431377249736; Mon, 11 May 2015 13:47:29 -0700 (PDT)
Received: from ?IPv6:2406:e007:54d7:1:28cc:dc4c:9703:6781? ([2406:e007:54d7:1:28cc:dc4c:9703:6781]) by mx.google.com with ESMTPSA id mb4sm13977424pdb.63.2015.05.11.13.47.26 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 11 May 2015 13:47:28 -0700 (PDT)
Message-ID: <55511561.6000006@gmail.com>
Date: Tue, 12 May 2015 08:47:29 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.6.0
MIME-Version: 1.0
To: Jéferson Campos Nobre <jcnobre@inf.ufrgs.br>, anima-signaling@ietf.org
References: <CABv6xLt96VF3UeUtB2ftNT5j4PuX5gueTctE_WeZkS2D49bTeA@mail.gmail.com>
In-Reply-To: <CABv6xLt96VF3UeUtB2ftNT5j4PuX5gueTctE_WeZkS2D49bTeA@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/anima-signaling/G3vcCaFbjZ8pY6wKnZelay0Z26Y>
Subject: Re: [Anima-signaling] Signaling requirements
X-BeenThere: anima-signaling@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Mon, 11 May 2015 20:47:31 -0000

On 12/05/2015 05:56, Jéferson Campos Nobre wrote:
> Hi.
> Some comments about the signaling requirements.
> 
> * Discovery requirements
> 
> - "If an ASA supports multiple objectives, relevant peers may be
> different for different discovery objectives, so discovery needs to be
> repeated to find counterparts for each objective."
> 
> What "objectives" means here? Depending on the definition, the
> complexity of the discovery process can increase significantly.

There's a proposed definition at
https://tools.ietf.org/html/draft-carpenter-anima-gdn-protocol-03#section-3.1

If that isn't adequate, let's discuss it.

> Besides that, my understanding is that there will be multiple logical
> views, one for each objective. Is that right?

I assume so, but that is a question for the ASA designer, I think.

> 
> - "Two special cases exist: discovering a hierarchical superior (if
> there is one) and discovering the AN trust anchor."
> 
> In this item, what "hierarchical superior" means? A traditional
> management station or other components of ANIMA architecture? It seems
> confusing.

OK, there is also a brief discussion of that in the draft, but I am
not very happy with it myself ;-). It may just be nonsense. Please
search for 'hierarchical' at
https://tools.ietf.org/html/draft-carpenter-anima-gdn-protocol-03#page-3
and tell us what you think.

> 
> * Negotiation and Synchronization Requirements
> 
> - "Either an explicit information model describing protocol messages,
> or at least a flexible and extensible message format, is needed."
> 
> I think both are needed.

You realise how much work is involved in defining an information model,
I assume. I agree that it is probably needed, but probably later. It's
also linked to the issue that Toerless has raised (binary vs JSON).

Thanks
    Brian

> Best.
> 
> Jéferson Campos Nobre
> PhD Student
> Computer Networks Group -  Institute of Informatics
> Federal University of Rio Grande do Sul
> http://www.inf.ufrgs.br/~jcnobre
> 
> _______________________________________________
> Anima-signaling mailing list
> Anima-signaling@ietf.org
> https://www.ietf.org/mailman/listinfo/anima-signaling
>

v2.23.0 | Report a Bug | By Email