Re: [lisp] I-D Action: draft-barkai-lisp-nexagon-10.txt

"Victor Moreno (vimoreno)" <vimoreno@cisco.com> Thu, 19 September 2019 04:02 UTC

Return-Path: <vimoreno@cisco.com>
X-Original-To: lisp@ietfa.amsl.com
Delivered-To: lisp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C176E12012C for <lisp@ietfa.amsl.com>; Wed, 18 Sep 2019 21:02:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.5
X-Spam-Level:
X-Spam-Status: No, score=-14.5 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, 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 header.b=ObfCtVBw; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=X+IsBwQJ
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 oo9FAaXWkpTM for <lisp@ietfa.amsl.com>; Wed, 18 Sep 2019 21:02:01 -0700 (PDT)
Received: from alln-iport-5.cisco.com (alln-iport-5.cisco.com [173.37.142.92]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8F0C712006F for <lisp@ietf.org>; Wed, 18 Sep 2019 21:02:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1734; q=dns/txt; s=iport; t=1568865721; x=1570075321; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=ghJcc/rFdINxz9upvWXDTwjRgvhn5jbgDkkmHY9/eLk=; b=ObfCtVBwHEqQOj6aBiXNHpWetDJZC89njGAKBLGek80lf3Z1ulMKOKms Fvxxcx3esXxXo6d3hJukSjaGfInxz1OKrwS8Eanf317as07pQDT81ugVd 9CcX4D8n8u90a6UZTUCURT1Ki59QsmRYnpEv14F7VAOhdxFBWmHbGr25e I=;
IronPort-PHdr: 9a23:HbPQ5hfiVlFah29Bs7hPKPpYlGMj4e+mNxMJ6pchl7NFe7ii+JKnJkHE+PFxlwGQD57D5adCjOzb++D7VGoM7IzJkUhKcYcEFnpnwd4TgxRmBceEDUPhK/u/cS0/G95PUlhN9HCgOk8TE8H7NBXf
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0CwAAB8/IJd/4oNJK1lGgEBAQEBAgEBAQEHAgEBAQGBZ4FFUANtViAECyqEIoNHA4p7glyJZo4NglIDVAkBAQEMAQEYCwoCAQGEPwIXgmwjOBMCAwkBAQQBAQECAQUEbYUtDIVKAQEBAwEBARAREQwBASwLAQQLAgEIGAICGQ0CAgIfBgsVEAIEDgUZCYMAAYFqAw4PAQ6jLwKBOIhhc4Eygn0BAQWCSIJDDQuCFwMGgQwojAkYgUA/gREnH4JMPoIaRwEBgWGDCzKCJo9XnGxBCoIikQWEABuZIZgqjnMCBAIEBQIOAQEFgWkhgVhwFTsqAYJBUBAUgU6DcoUUhT9zgSmPTQEB
X-IronPort-AV: E=Sophos;i="5.64,522,1559520000"; d="scan'208";a="334418394"
Received: from alln-core-5.cisco.com ([173.36.13.138]) by alln-iport-5.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 19 Sep 2019 04:02:00 +0000
Received: from XCH-RCD-017.cisco.com (xch-rcd-017.cisco.com [173.37.102.27]) by alln-core-5.cisco.com (8.15.2/8.15.2) with ESMTPS id x8J420IF004143 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 19 Sep 2019 04:02:00 GMT
Received: from xhs-aln-003.cisco.com (173.37.135.120) by XCH-RCD-017.cisco.com (173.37.102.27) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Wed, 18 Sep 2019 23:01:59 -0500
Received: from xhs-rtp-003.cisco.com (64.101.210.230) by xhs-aln-003.cisco.com (173.37.135.120) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Wed, 18 Sep 2019 23:01:59 -0500
Received: from NAM05-DM3-obe.outbound.protection.outlook.com (64.101.32.56) by xhs-rtp-003.cisco.com (64.101.210.230) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Thu, 19 Sep 2019 00:01:59 -0400
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=YKLsjSkWAA2EhF7uKlI5Y69uu4Zqc40jdfyzR0BlWYrAHUueuarHgZoX0V5EYo2Qe/Gyvm0sdZ7aTf4ulZpEYKWNW+nwaBtWUjeNlDDncJx/z31siijrMP/68mC2qYBl5u82oFCGt913MpdnwI2NCFHV9uJ063QjPLE/v5P3TRUBPQ6at8O2FFRmp3KYZK8g40uktOMNOWLk1L5aqSjPwM03TBA0N5BvwDVUCiRUC5o0KKro4MxOn+/gP878HRORTunoLMxmD+gYxrlISjpFSvdluMpr32t1uqer4F0N7zpv8nq/1RPnI7CxN9cF1ktXg0+rXeXEhYEJbqtN2nt1og==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=ghJcc/rFdINxz9upvWXDTwjRgvhn5jbgDkkmHY9/eLk=; b=cZ1wIrI2DREY7iy3fmkZPXpqBrantzRJ9v1+4CiFKI5riKQ/58q5gd5zLhg7b1K/Bbr5wQIVcaf6ddXJMmG1hsmI+l762qOX5S9ZwbeL6+1uGJi5bzCSUPRGFZsphaXrNcc2chJe91Ys7YKPh8lRTW1O9X2lYhgsbDTkV6WZoUlceyfzjJO9vJwlz1+k/UE44yCIF39lKtCTSD5QnFkUfLKzzlAdjcamA8GOU3jViuJr9oXq7QqwaVJnMJSbxtaRsxdS1e0JghazrFLJtn5R5sDxWbJlh3DxpEdklWo2wBcKmDJh/2wFoXdxl5t35EvbgJ9IIstX1gscUEzdiygLOQ==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=cisco.com; dmarc=pass action=none header.from=cisco.com; dkim=pass header.d=cisco.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.onmicrosoft.com; s=selector2-cisco-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=ghJcc/rFdINxz9upvWXDTwjRgvhn5jbgDkkmHY9/eLk=; b=X+IsBwQJVXk7cSOAubFsHfhEg3GSmER3zz9+jpuSP1Hg1dLOH2E4Zh8jRcrkf0shb0hUKuPJjjv+l+E2sYvOYtDq3RQmllmIV7DGNjFJIoCY8IZPlx2eyV/Xdf7kuo1EOhgAOQXq5VVONYbZhtsb+ju67IsoxDgnHPwtgrOvelc=
Received: from CY4PR1101MB2086.namprd11.prod.outlook.com (10.172.78.9) by CY4PR1101MB2263.namprd11.prod.outlook.com (10.172.76.151) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2284.20; Thu, 19 Sep 2019 04:01:58 +0000
Received: from CY4PR1101MB2086.namprd11.prod.outlook.com ([fe80::59f6:a4aa:6717:b460]) by CY4PR1101MB2086.namprd11.prod.outlook.com ([fe80::59f6:a4aa:6717:b460%10]) with mapi id 15.20.2263.023; Thu, 19 Sep 2019 04:01:58 +0000
From: "Victor Moreno (vimoreno)" <vimoreno@cisco.com>
To: Dino Farinacci <farinacci@gmail.com>
CC: Joel Halpern <jmh@joelhalpern.com>, "lisp@ietf.org" <lisp@ietf.org>
Thread-Topic: [lisp] I-D Action: draft-barkai-lisp-nexagon-10.txt
Thread-Index: AQHVbiwfvSdHyxP+kkiTH7p3ckl22acxvoOAgACjG0Q=
Date: Thu, 19 Sep 2019 04:01:58 +0000
Message-ID: <B452A31E-150E-4AE4-A693-A18AA630AB87@cisco.com>
References: <156862357770.28196.6343819812576579929@ietfa.amsl.com> <d6358cfd-9c8f-3c27-28a5-d7ae20280ec8@joelhalpern.com>, <EE82B5CD-B2AC-4590-9F6C-8543E30A68FF@gmail.com>
In-Reply-To: <EE82B5CD-B2AC-4590-9F6C-8543E30A68FF@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=vimoreno@cisco.com;
x-originating-ip: [2001:420:c0c8:1004::9b]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: de9374cf-f501-45aa-438e-08d73cb61e22
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600167)(711020)(4605104)(1401327)(2017052603328)(7193020); SRVR:CY4PR1101MB2263;
x-ms-traffictypediagnostic: CY4PR1101MB2263:
x-ms-exchange-purlcount: 1
x-microsoft-antispam-prvs: <CY4PR1101MB2263E1E7D2FEEAE2C476A640CB890@CY4PR1101MB2263.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:7219;
x-forefront-prvs: 016572D96D
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(136003)(346002)(396003)(376002)(39860400002)(366004)(189003)(199004)(6306002)(966005)(478600001)(14454004)(4326008)(6486002)(6916009)(256004)(7736002)(6436002)(25786009)(36756003)(71200400001)(6246003)(71190400001)(305945005)(1411001)(6116002)(64756008)(66446008)(66476007)(76116006)(8936002)(446003)(2616005)(476003)(11346002)(46003)(33656002)(8676002)(81166006)(66556008)(66946007)(91956017)(102836004)(186003)(229853002)(6512007)(81156014)(86362001)(5660300002)(53546011)(6506007)(99286004)(76176011)(486006)(2906002)(54906003)(316002); DIR:OUT; SFP:1101; SCL:1; SRVR:CY4PR1101MB2263; H:CY4PR1101MB2086.namprd11.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None (protection.outlook.com: cisco.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: VqeCRZQCTRpkvmd+0k22iQL17/rhZ6/Ha2qmxOtAKoYpupDjpf4h2kF+Rbg+HqwO7MJODB+ZN7glgTKSTNr1UMQdfq6EQGF7kXWbI74O5RydJg51HBGNivV9iwlFGN5AEI5PHHL/ucaG/zZTsqwW/edHorXNKzdIsyQ2RnnSx4d7W/paYyDUO9A8DLxM6JXaRsogwpT6mVjvFhkVZPZ6cC5SuglcgiJVJwW2aYWD5uCv//vV/VM67RD4wCr1qfUWlHvd59IqdFqvwutLbAZFe4ALa9TuuTuxLmgxO6e16wfE73uOaGnWKl3H+ZcLWfMcTz18kzABolw3h9nVBa3Y4gdRl0W8lRfBPaNTwBcUw4lWdFX9SW40bJ5dEd/CrGzjPg1cqzfM+aokEJZpfIv9bx/KgG4vSG8zmVSMeq28ukw=
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: de9374cf-f501-45aa-438e-08d73cb61e22
X-MS-Exchange-CrossTenant-originalarrivaltime: 19 Sep 2019 04:01:58.1651 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5ae1af62-9505-4097-a69a-c1553ef7840e
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: bccXKl4YoA19RAJybg3WbXyHivrF/WQIUs0Kz8fsNOgPON0t/wgR7+trQrZYXv7ESdmepv7yA/FDhxi/BcDoHQ==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CY4PR1101MB2263
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.37.102.27, xch-rcd-017.cisco.com
X-Outbound-Node: alln-core-5.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/lisp/nj5YdduV008xSmD7_6fhxY5sxus>
Subject: Re: [lisp] I-D Action: draft-barkai-lisp-nexagon-10.txt
X-BeenThere: lisp@ietf.org
X-Mailman-Version: 2.1.29
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: <https://mailarchive.ietf.org/arch/browse/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: Thu, 19 Sep 2019 04:02:04 -0000

I think a thorough understanding of mobility requirements and dependencies and how LISP may or may not accommodate these scenarios is key. I would like to see us work on this and other mobility related drafts (e.g. Ground based LISP).

Victor

> On Sep 18, 2019, at 11:18 AM, Dino Farinacci <farinacci@gmail.com> wrote:
> 
> I’m a side author on this document and more of a reviewer. But I’ll answer your questions on behalf of a WG member.
> 
>> Before I get more privacy feedback (if I do) I want to know
>> 1) does the WG actually care about this?
> 
> I do. Because understanding in deep detail the use-cases, allows us to understand if LISP has the necessary protocol features.
> 
>> 2) Is it ready for more extensive review?
> 
> Yes.
> 
>> I realize we have not adopted this document.  Some of this feedback is to help the chairs judge what to do when the authors do ask for adoption.
> 
> We are at a point of the protocol’s life where working on use-cases allows more adoption. I am for making this a working group document (even though the authors have not formally requested).
> 
> Dino
> 
> _______________________________________________
> lisp mailing list
> lisp@ietf.org
> https://www.ietf.org/mailman/listinfo/lisp