IETF Logo Mail Archive

Re: [lisp] draft-ietf-lisp-introduction-05 - EID/RLOC Syntax

Dino Farinacci <farinacci@gmail.com> Mon, 13 October 2014 14:35 UTC

Return-Path: <farinacci@gmail.com>
X-Original-To: lisp@ietfa.amsl.com
Delivered-To: lisp@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 30C341A0154 for <lisp@ietfa.amsl.com>; Mon, 13 Oct 2014 07:35:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 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, SPF_PASS=-0.001] autolearn=ham
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 KHlT3Y8-YZKg for <lisp@ietfa.amsl.com>; Mon, 13 Oct 2014 07:35:08 -0700 (PDT)
Received: from mail-qa0-x235.google.com (mail-qa0-x235.google.com [IPv6:2607:f8b0:400d:c00::235]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2CA191A0144 for <lisp@ietf.org>; Mon, 13 Oct 2014 07:34:38 -0700 (PDT)
Received: by mail-qa0-f53.google.com with SMTP id v10so4416022qac.26 for <lisp@ietf.org>; Mon, 13 Oct 2014 07:34:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=dPNAD4Mqz8UjlDLDzOZ3XAPw5UB6Ui1kN/L/yTvbef0=; b=ZmaQEFC91NM4ofCbC3L8CxYHcxGM+SVQ5UJQnkzQ2jYEaaVK6U38Qx3P3pwEobIkdq ZdBJiXxuM2JKPcuWbLpIQDC8cct303WUGlIEOZv/ggO/AarD9e1qEPmhyyoi02yVOD6e jN9e+Elf2TKtcZkWfvIRV7bx4uow0cH5P4GwZu6iKNURx8b5XybCTFuToSavS0hS2ZOE uIJUVDDLMbnu1FycsqEYPYae4dv/zXoDl/iEKDOa0kLOLHzQsPtK/Lyl3/sQR3a3DlXC U9KNcOWjs80PS6uqkaUepn8OViNRr57NN0rZQ9bA0Rurs3g1ne1WCsILYC0j6G8aN15a Z0tQ==
X-Received: by 10.229.249.73 with SMTP id mj9mr28012943qcb.6.1413210877414; Mon, 13 Oct 2014 07:34:37 -0700 (PDT)
Received: from [192.168.1.31] (pool-72-92-14-140.phlapa.east.verizon.net. [72.92.14.140]) by mx.google.com with ESMTPSA id r12sm12931458qax.35.2014.10.13.07.34.36 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 13 Oct 2014 07:34:36 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (1.0)
From: Dino Farinacci <farinacci@gmail.com>
X-Mailer: iPhone Mail (12A405)
In-Reply-To: <114B6A5B-38EB-4236-8D97-3EF58098DD2C@gigix.net>
Date: Mon, 13 Oct 2014 10:34:36 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <942DDA1E-5663-4797-825D-D9455C914E9C@gmail.com>
References: <fddce201eb144632a895d6c2f27bd637@CO1PR05MB442.namprd05.prod.outlook.com> <5439BE86.20302@joelhalpern.com> <1ee88b789ea2413ca5ddd6eb00a47374@CO1PR05MB442.namprd05.prod.outlook.com> <8C11EEBA-6B1C-4ED2-81F8-09C563C4CB2E@gmail.com> <8f701cb0ef564355ab865a027f2043a0@CO1PR05MB442.namprd05.prod.outlook.com> <12DD0FED-3A7C-44B6-9AA8-3F04702E7A0D@gmail.com> <66048b82c60c48dfbd35efe9a5589126@CO1PR05MB442.namprd05.prod.outlook.com> <E318A549-303A-40A5-B072-54B763340503@gmail.com> <114B6A5B-38EB-4236-8D97-3EF58098DD2C@gigix.net>
To: Luigi Iannone <ggx@gigix.net>
Archived-At: http://mailarchive.ietf.org/arch/msg/lisp/3UDrCrsx87pxrq54TcfArLmTXwY
Cc: "lisp@ietf.org" <lisp@ietf.org>
Subject: Re: [lisp] draft-ietf-lisp-introduction-05 - EID/RLOC Syntax
X-BeenThere: lisp@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: List for the discussion of the Locator/ID Separation Protocol <lisp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/lisp>, <mailto:lisp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/lisp/>
List-Post: <mailto:lisp@ietf.org>
List-Help: <mailto:lisp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lisp>, <mailto:lisp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Oct 2014 14:35:14 -0000

> 
> On the other hand, may be the LCAF document should update the definition of EID and RLOC accordingly.

Do you mean to explain how new address types are introduced by LCAF encoding in that EIDs and RLOCs can be multi-tuple entities and may not be used for data transport?

Dino

v2.23.0 | Report a Bug | By Email