IETF Logo Mail Archive

Re: [nvo3] Shim header of vxlan-gpe

"Fabio Maino (fmaino)" <fmaino@cisco.com> Wed, 23 October 2019 22:14 UTC

Return-Path: <fmaino@cisco.com>
X-Original-To: nvo3@ietfa.amsl.com
Delivered-To: nvo3@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EA0A6120019; Wed, 23 Oct 2019 15:14:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.499
X-Spam-Level:
X-Spam-Status: No, score=-14.499 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, 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=XADXV20B; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=zHjBnqBv
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 XnjCMHVtNJ-H; Wed, 23 Oct 2019 15:14:38 -0700 (PDT)
Received: from alln-iport-2.cisco.com (alln-iport-2.cisco.com [173.37.142.89]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4ABBF12008D; Wed, 23 Oct 2019 15:14:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=12087; q=dns/txt; s=iport; t=1571868878; x=1573078478; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=qebNc4As2BxUXDcw0ffhfnaPY8QKM5xDKO2FKIvjIsM=; b=XADXV20B4pDm/QRsgIPnwFcokasNoWkcgHFbfZ/0y0N7lpH0gKd3iqfN IAbf8w8HsDMenCptkH1qU3dXfAtqmUDF+7lJMj+g46I22Iwr2rDz+FMQz ZFGgHydxCqkf8lWpmuovU4oR+/s/rkOiU57XXikLEuNaNgh9Xf31k47dg Q=;
IronPort-PHdr: 9a23:UYt/ZB+tusvaIv9uRHGN82YQeigqvan1NQcJ650hzqhDabmn44+/bR7E/fs4iljPUM2b8P9Ch+fM+4HYEW0bqdfk0jgZdYBUERoMiMEYhQslVcCAAEz9K9bhbjcxG4JJU1o2t3w=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0CQAAA10LBd/5RdJa1lGQEBAQEBAQEBAQEBAQEBAQEBEQEBAQEBAQEBAQEBgXuBHC9QBWxXIAQLKoQng0cDilyCOSWJb4kzhGGCUgNUCQEBAQwBAS0CAQGEQAIXgx0kOBMCAwkBAQQBAQECAQUEbYU3DIVQAQEBAQMSER0BATcBDwIBCA4DAwECKwICAh8RHQgCBAENBSKDAAGBeU0DLgECqCwCgTiIYXWBMoJ+AQEFhQwNC4IXCYE2jA8YgUA/gTgME4JMPoIbgkqCcDKCLI4ggViFOokzjj1BCoIkkRuEDBuCO5cVjjaBP4h4jxECBAIEBQIOAQEFgWkigVhwFWUBgkEJRxAUgwaDc4pTdIEpjyQBAQ
X-IronPort-AV: E=Sophos;i="5.68,222,1569283200"; d="scan'208,217";a="356995163"
Received: from rcdn-core-12.cisco.com ([173.37.93.148]) by alln-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 23 Oct 2019 22:14:37 +0000
Received: from XCH-ALN-005.cisco.com (xch-aln-005.cisco.com [173.36.7.15]) by rcdn-core-12.cisco.com (8.15.2/8.15.2) with ESMTPS id x9NMEbEu027731 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 23 Oct 2019 22:14:37 GMT
Received: from xhs-aln-001.cisco.com (173.37.135.118) by XCH-ALN-005.cisco.com (173.36.7.15) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Wed, 23 Oct 2019 17:14:36 -0500
Received: from xhs-aln-001.cisco.com (173.37.135.118) by xhs-aln-001.cisco.com (173.37.135.118) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Wed, 23 Oct 2019 17:14:35 -0500
Received: from NAM05-CO1-obe.outbound.protection.outlook.com (173.37.151.57) by xhs-aln-001.cisco.com (173.37.135.118) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Wed, 23 Oct 2019 17:14:35 -0500
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=AJhKT/pv+IAVCfAwOmhZ3/vc/yULOR7+zA0Ev02Ia2EFkK1NhV2MCBQUjslM3kDyidlUoS9DeGQbx8fpO0zxRHpulpenjPUNgRXmImktqOzicWvp4akLgBCKbA8OmGofJITls6nshTzfksBEa8AdXxwiPn0P4U1xH6+mHHi5Tusog3LjiHVK7EQ+GKftyPivO+h/Rm85iJZcaAMTIkORwUvJHHneZ0iHYwAc6HE5ZL/XPjKaZ2IeQC4gyDPx9jIGZutFsQDEWsqj6/cyG9l3rpxvKlrRAN70bkV+uD7q7wKGXBAjRXozCCWVU+rjytVxYnMvF+D8GqH0ko2U+LhV/w==
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=qebNc4As2BxUXDcw0ffhfnaPY8QKM5xDKO2FKIvjIsM=; b=gEAQwaxl8RDvUyJqwgyb8ndRwgEMFKhtyM1baduEj1qyI8UEfSIaIL4WxvckyYpgdxBnFUjEIbng0N8uRINkrvqXY80ovjaYJgkkEPl8yE/O72eysMEQ6NNybUW2V3xfdvo7q18AX7aGWo2q7QFALiR0uOukbKH4pxYWylgzxshbnCCCxrkVF3zEM+e/VrFMDvKR+mxq86/1sOsUJ+F0vrZIw1567s2w/au3BmK9r8QbinaTRCMwXUuFVoBS4Ez+IPDQKkAKngDZhfxjjLCybW/KhR1MC6yqsqHBKSKGdorSK8gCsXz7R11dfgLN9FXJAmDdoNvMDBjr8ShiSKwVJQ==
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=qebNc4As2BxUXDcw0ffhfnaPY8QKM5xDKO2FKIvjIsM=; b=zHjBnqBvyKJxGgi1KhjyWVB6xmuxHXr3bcZdYtEAb6+ENrgvAEjGrj2IB6mY0CigF56Gz5PPEkMOKMu+wDutjLodeFxwZaSm/QuVA9QyU8meAvp+EAk88//trF+laS3FsKIhwXOaD26vxbTo6055WJXCzNOkTe4oU2zEJJtQpYk=
Received: from BY5PR11MB4420.namprd11.prod.outlook.com (52.132.255.20) by BY5PR11MB4323.namprd11.prod.outlook.com (52.132.254.87) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2367.24; Wed, 23 Oct 2019 22:14:34 +0000
Received: from BY5PR11MB4420.namprd11.prod.outlook.com ([fe80::b9e3:dd7:b0a6:9780]) by BY5PR11MB4420.namprd11.prod.outlook.com ([fe80::b9e3:dd7:b0a6:9780%3]) with mapi id 15.20.2347.029; Wed, 23 Oct 2019 22:14:34 +0000
From: "Fabio Maino (fmaino)" <fmaino@cisco.com>
To: Lizhong Jin <lizho.jin@gmail.com>, "draft-ietf-nvo3-vxlan-gpe@ietf.org" <draft-ietf-nvo3-vxlan-gpe@ietf.org>
CC: "draft-lemon-vxlan-lisp-gpe-gbp@ietf.org" <draft-lemon-vxlan-lisp-gpe-gbp@ietf.org>, "nvo3@ietf.org" <nvo3@ietf.org>
Thread-Topic: Shim header of vxlan-gpe
Thread-Index: AQHVgW4UhBBQVWlcikqWt5JK+qqwR6doZkmA
Date: Wed, 23 Oct 2019 22:14:34 +0000
Message-ID: <4F44C944-C954-483A-9246-5356FF2F97DD@cisco.com>
References: <D78E94DA-9F61-4C72-A02C-4B0DA0396BC5@gmail.com>
In-Reply-To: <D78E94DA-9F61-4C72-A02C-4B0DA0396BC5@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/10.1e.0.191013
authentication-results: spf=none (sender IP is ) smtp.mailfrom=fmaino@cisco.com;
x-originating-ip: [2001:420:30a:4e05:ec2e:2bfd:a4bb:7fd7]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 5810a642-521b-46f6-6bfb-08d75806628a
x-ms-traffictypediagnostic: BY5PR11MB4323:
x-microsoft-antispam-prvs: <BY5PR11MB43231CD0AE59682BE57CEDF4C26B0@BY5PR11MB4323.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 019919A9E4
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(136003)(346002)(39860400002)(396003)(366004)(376002)(189003)(199004)(85654002)(8676002)(6486002)(8936002)(46003)(64756008)(229853002)(6116002)(6436002)(6512007)(6306002)(14444005)(54896002)(256004)(54906003)(58126008)(2616005)(66946007)(86362001)(11346002)(66556008)(446003)(81156014)(76116006)(110136005)(476003)(66446008)(66476007)(186003)(316002)(486006)(9326002)(81166006)(14454004)(478600001)(5660300002)(33656002)(25786009)(36756003)(2501003)(71190400001)(71200400001)(6246003)(2906002)(6506007)(76176011)(53546011)(4326008)(99286004)(7736002)(102836004); DIR:OUT; SFP:1101; SCL:1; SRVR:BY5PR11MB4323; H:BY5PR11MB4420.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: BCL:0;
x-microsoft-antispam-message-info: C3uZo7i/BHpgGNieX77GgA6JsiNpY/mDEsU9wyYbk/xEz3AZw79loBu6WFqEtWtmG1xF/e4QFcwWEQJyUTM0mnc4JMd8Z/NslewSjoJmLE+KWhHP/UVYmS1019G0aLuzMbNA7aTtffa4nGAxtREMbqEPQlul7bY1s3hta2BpBQ8/4lBTA+gWGyP0Spw6mw8l8rQuYjRafdnlSdEqT/pGVzCuorFC3pSRft5rWVAsQ+08SXUrOKjtMAefrrO0kcrVMsUQqETsRTa5r/rWbc0k0KUo0UZzL59UAvwRnkYhCMWOjULjHvK9QJhiZ2UnEW9ho9W+zst7RA7l90Ya4mSltAixsqdzBWS2nh0aAIZj9JY/5znJDwz3t6HjDbhnuQ5BewFGYBY9uyQc35NpGagKB1AOBZ/g/3zNmwx9vZ5v3X7JkwH30QLbiv/AzNn/JavWw9kAcx4fc91omhnzihKNIA==
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_4F44C944C954483A92465356FF2F97DDciscocom_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 5810a642-521b-46f6-6bfb-08d75806628a
X-MS-Exchange-CrossTenant-originalarrivaltime: 23 Oct 2019 22:14:34.1352 (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: qKeQPVIrcHUVEXqoUd6GtmXF/N4fQgVHm1aidqC6EJplc722UMN2vGWXehmcfQXDEOOrMVZ/4u4btWyK1PEeNQ==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BY5PR11MB4323
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.36.7.15, xch-aln-005.cisco.com
X-Outbound-Node: rcdn-core-12.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/nvo3/fKyKt--PDenLHxoROEhlzYPTPbI>
Subject: Re: [nvo3] Shim header of vxlan-gpe
X-BeenThere: nvo3@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Network Virtualization Overlays \(NVO3\) Working Group" <nvo3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/nvo3>, <mailto:nvo3-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/nvo3/>
List-Post: <mailto:nvo3@ietf.org>
List-Help: <mailto:nvo3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/nvo3>, <mailto:nvo3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 Oct 2019 22:14:41 -0000

Hi Lizhong,
Sorry for the delay.

Vxlan-gpe version 08 should now contain the appropriate reference to [I-D.lemon-vxlan-lisp-gpe-gbp]. Let me know if I’m missing anything.

I know designing ASICs with the added flexibility required by the shim headers comes at a cost. Ultimately implementations will have to choose which extensions to support, and how much buffer to dedicate for unsupported extensions. I don’t think there’s a general rule that can be applied. Do you have any suggestion? Restricting to control plane functions might be too much, even some of the OAM features might end up  being implemented in the dataplane.

Wrt GBP it’s a fairly well known  use case, but not universally deployed so we wanted to leave to implementors the decision to support or not that extension.

Thanks,
Fabio





From: Lizhong Jin <lizho.jin@gmail.com>
Date: Saturday, October 12, 2019 at 7:29 PM
To: "draft-ietf-nvo3-vxlan-gpe@ietf.org" <draft-ietf-nvo3-vxlan-gpe@ietf.org>
Cc: "draft-lemon-vxlan-lisp-gpe-gbp@ietf.org" <draft-lemon-vxlan-lisp-gpe-gbp@ietf.org>, "nvo3@ietf.org" <nvo3@ietf.org>
Subject: Shim header of vxlan-gpe
Resent-From: <alias-bounces@ietf.org>
Resent-To: Fabio Maino <fmaino@cisco.com>, Larry Kreeger <lkreeger@gmail.com>, <uri.elzur@intel.com>
Resent-Date: Saturday, October 12, 2019 at 7:29 PM


Hi GPE authors,
I recently review the GPE draft and the shim header design. I saw the "Next Protocol" assigned to GBP changed from 0x6 to 0x80, and the reference of [I-D.lemon-vxlan-lisp-gpe-gbp] should be updated from version 01 to version 02 which confused me in my first reading. I am not clear why GBP do such kind of update, do you have any design principles for the "Next Protocol" assignment for range from 0x80 to 0xFF? Some practical design principles in the document would benefit the industry.
And since shim header is a TLV style, I tend to ask if it would be practical to restrict the shim header to be used only for OAM and control purpose. That would greatly simplify the ASIC design.

Regards
Lizhong

v2.23.0 | Report a Bug | By Email