Re: [lisp] RFC6830bis and multiprotocol support

Dino Farinacci <farinacci@gmail.com> Thu, 30 November 2017 18:49 UTC

Return-Path: <farinacci@gmail.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 CDAA1127444 for <lisp@ietfa.amsl.com>; Thu, 30 Nov 2017 10:49:22 -0800 (PST)
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, 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 v-SaGbaT-C96 for <lisp@ietfa.amsl.com>; Thu, 30 Nov 2017 10:49:21 -0800 (PST)
Received: from mail-pf0-x232.google.com (mail-pf0-x232.google.com [IPv6:2607:f8b0:400e:c00::232]) (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 77DE6126CC4 for <lisp@ietf.org>; Thu, 30 Nov 2017 10:49:21 -0800 (PST)
Received: by mail-pf0-x232.google.com with SMTP id y89so3495377pfk.0 for <lisp@ietf.org>; Thu, 30 Nov 2017 10:49:21 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=9wNrkZ8FWB/uDyvJXXP+tjx8TetOtoaUnMQXMpj8qq4=; b=JDSLcyj0/se56zzpuUDmznLsgvFmViddYO/t7Va/U0cKCp8fW8k0kw/vECpHEEpuI6 UMBddvyqlSAtsuu3TSmqvdPbXF5xgp58H2cMrwIpfb6gM36qN9ViZDefQ9Yo9g3AcyUV IV2EIDv0h93b5VU1TIiQywC4Hd1lRljK4zsfNv/JfmYilMQEASC4mP1EJP4O0R5Trq6i xynHlKALt993/Dsn4+yjVXQBI5uR/6qAF3+xskjhvmRX17GT11YhPtsYA2UqaSze2zNs 8qOYLtSABy6W0Q1FhUYy0SMauKOhNJsKaIKyuNTm3HKfBz8PjtMvz12PgopRPTL9FBse JxUA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=9wNrkZ8FWB/uDyvJXXP+tjx8TetOtoaUnMQXMpj8qq4=; b=rE8VwzFyhDMI2Ty1c2inFoTA+6yXpViPCZX/e6Ja58qrzPenvTz1qonJUxQ9C9bLHu vqlvMhbVbUEpvyywuVMTUe0R6/VLpK+uCwbPFwH4tCH0lduWCnrl9r4KTq0tuGzDXKnN Wf+MYKoN3mC4QDN+ZPbyIAPHJkCdOUbfaQbAsDAoC40YGEzkNPLKKSZUUtV20ec+zouj QCCkmn6vfJ93Qx0Ra/4jlrkv2b4YBeQ8w7cxyx62ihlceV2DoQkit3SYa8bx1pV43AL5 U4WEu5YFNTF2vXEJ+Y6w6651EuU2XsghqSPu6qtU3XKnRuo5ucVJaOH8apQYPqjydTKp MrvA==
X-Gm-Message-State: AJaThX6LbV83qVJSM2s8u842teFt0HS09IPBrHdkI9Kv96lt+PUDoWoa sGjkgBo9yiHSdej9eXyTWTs=
X-Google-Smtp-Source: AGs4zMZ2XyMgw3YuzwRblgOuPrGSQSGUMKgTTzorlUpHgGV+0K41xZ622Jlekb1zl6Lh1dTolrIkRw==
X-Received: by 10.99.183.15 with SMTP id t15mr3379481pgf.128.1512067761020; Thu, 30 Nov 2017 10:49:21 -0800 (PST)
Received: from dino-macbook.wp.comcast.net (173-8-188-29-SFBA.hfc.comcastbusiness.net. [173.8.188.29]) by smtp.gmail.com with ESMTPSA id c73sm8224869pfd.181.2017.11.30.10.49.19 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 30 Nov 2017 10:49:19 -0800 (PST)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 11.0 \(3445.1.7\))
From: Dino Farinacci <farinacci@gmail.com>
In-Reply-To: <1cfc9b0d-854d-c249-d06f-eff58b3d4d93@cisco.com>
Date: Thu, 30 Nov 2017 10:49:18 -0800
Cc: lisp@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <6352C57B-27A4-4B33-8F86-1962A1A24A68@gmail.com>
References: <211ad1ba-b5fb-b0d5-7001-0f91e89691b7@cisco.com> <7cf2e668-ca68-8ae4-054e-02b9f4f5b644@cisco.com> <3be13180c987450a9b625e7143fe0225@XCH-RCD-008.cisco.com> <779AC172-FE1C-45B0-AA0C-35B8438CE787@gmail.com> <1cfc9b0d-854d-c249-d06f-eff58b3d4d93@cisco.com>
To: Fabio Maino <fmaino@cisco.com>
X-Mailer: Apple Mail (2.3445.1.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/lisp/o2G_ksGuO0onSBb3oKIxPErAMuc>
Subject: Re: [lisp] RFC6830bis and multiprotocol support
X-BeenThere: lisp@ietf.org
X-Mailman-Version: 2.1.22
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, 30 Nov 2017 18:49:23 -0000

> 100% agree Dino. 
> 
> The proposed changes to RFC6830bis, as discussed so far, are: 
> - allocate the last reserved bit in RFC6830bis as a P-bit, 
> - use the last 8-bit of the first word as nonce, and 

I think you mean the Next Protocol field and not the nonce.

> - use 16 bits only to allocate nonce and versioning fields (when used). 
> 
> LISP-GPE will reflect the KK bits and will be bit-aligned with RFC6830bis (including NLEV bits). This will mean that the OAM bit in LISP-GPE will not be there anymore. 
> 
> What Frank is saying is that this will enable the IOAM use case with LISP, because IOAM doesn't actually use the OAM bit, but relies only on the Next Protocol field. 

Agree. Ack.

Dino