IETF Logo Mail Archive

Re: [netmod] Question regarding RFC 8344

"Rob Wilton (rwilton)" <rwilton@cisco.com> Fri, 19 July 2019 10:23 UTC

Return-Path: <rwilton@cisco.com>
X-Original-To: netmod@ietfa.amsl.com
Delivered-To: netmod@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AEE191200B6; Fri, 19 Jul 2019 03:23:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.501
X-Spam-Level:
X-Spam-Status: No, score=-14.501 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, 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=CQwwwIPl; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=t1JZgiOT
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 NHuXy8wQQxEO; Fri, 19 Jul 2019 03:23:26 -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 60A59120020; Fri, 19 Jul 2019 03:23:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2432; q=dns/txt; s=iport; t=1563531806; x=1564741406; h=from:to:subject:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version; bh=ZJMyxTUCKmI/GoSbwoTHljf6+X66E5sy8yIrXPvo3xA=; b=CQwwwIPlOOZU4pW8RPjqeI8ILCX3EV7bO7zNuX5cHdlg/2ZkFgBZhBi8 z4wUDMSdj4T1tGQt6P/qPUkfGrqwijjvPxF0t0BoDa+0Rw8dSbe/J/ZEF dJ/mYEQ7rxJ2RPV4bhtnVuJWZ4UCb8LH0ZYac8hEo43bsoYMMKedwrh6W M=;
IronPort-PHdr: 9a23:pPuJ1h0QimpLHjLSsmDT+zVfbzU7u7jyIg8e44YmjLQLaKm44pD+JxKHt+51ggrPWoPWo7JfhuzavrqoeFRI4I3J8RVgOIdJSwdDjMwXmwI6B8vQE1L6KOLtaQQxHd9JUxlu+HToeUU=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0BIAADGmDFd/4gNJK1mHAEBAQQBAQcEAQGBUwcBAQsBgUNQA21VIAQLKgqEE4NHA4RSiShMgg+XUIEugSQDVAkBAQEMAQEjCgIBAYRAAheCNSM0CQ4BAwEBBAEBAgEFbYU8DIVKAQEBAQMSEREMAQE4CwQCAQgRBAEBAQICJgICAjAVCAgCBAESCBqDAYFqAx0BAgygKwKBOIhgcYEygnkBAQWFARiCEwMGgQwoAYteF4FAP4ERRoJMPoEEgV0BAQIBgTgoBRAjglEygiaOeJtvCQKCGYZYjU+YCo01h0iQCAIEAgQFAg4BAQWBUDgqgS5wFYMngkEJGoNOhRSFP3IBgSiLaoEwAYEgAQE
X-IronPort-AV: E=Sophos;i="5.64,282,1559520000"; d="scan'208";a="299256698"
Received: from alln-core-3.cisco.com ([173.36.13.136]) by alln-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 19 Jul 2019 10:23:24 +0000
Received: from XCH-ALN-014.cisco.com (xch-aln-014.cisco.com [173.36.7.24]) by alln-core-3.cisco.com (8.15.2/8.15.2) with ESMTPS id x6JANNe5002790 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Fri, 19 Jul 2019 10:23:23 GMT
Received: from xhs-rtp-002.cisco.com (64.101.210.229) by XCH-ALN-014.cisco.com (173.36.7.24) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Fri, 19 Jul 2019 05:23:23 -0500
Received: from xhs-rtp-003.cisco.com (64.101.210.230) by xhs-rtp-002.cisco.com (64.101.210.229) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Fri, 19 Jul 2019 06:23:22 -0400
Received: from NAM02-BL2-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; Fri, 19 Jul 2019 06:23:22 -0400
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=n7jIU9aYe4rDa8VRX3aIlFceICIT0ZTeEGjDIEO/Vjki4CIZoHva7NJTg79Ds3VtYgdBfuyBBWEpnhmt8fegypYFc3EiN/nXXGq+G9X3CAeWLei7WJAE980FyIph2uQxDgMR73bNkGAiiLSc+rEZYKP5sSuNZb00VINWvA8LKiUMzkqvASVRqBXMTH+4BfbSwOrcV5eojVOOwLqV8nlwPYremRssAm6AvS8p2oQrmuvpmtdNZh0VYlosbg+GqFUcLYY3hxk6cuLPoe7ln9EgxTIlybI0riPOkhlcCy+lG/hxCcbywu+VrC2+4PBmE/RKzLamOtlgs9choh92RtN2HQ==
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=ZJMyxTUCKmI/GoSbwoTHljf6+X66E5sy8yIrXPvo3xA=; b=EKsRAVBLF2Fxg9xuqCx5HpqJZ8q47PYa6wPcZDAG4QWE9Oqqnv2KXnB6OL2jiDDW9ofwN1kPuOKXyNb0kf09EHfJyX1JRgQJfA4jtE/mvGVrA24gW3EbSUT7iacCul3w0ZN6HRK88Y8enQfPDKl2Z4KLfcWhxm4K4gVELWONueeQ/+YgVa225QWq5Js8Gs6N8tR2fAOj+ufP2UBUo5wUZAEw0xsnLW1Lq9P57GUGYslZUjwYR+hmMc+nn/J72HC51F3h+WAnDdsMlXqZ9erxhjp2wQgL2+IgZxcwYNWnKCcIsAgoXsENA8ituwVsJEGVaSk21OzH+MF9nRbv8XD+yQ==
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=ZJMyxTUCKmI/GoSbwoTHljf6+X66E5sy8yIrXPvo3xA=; b=t1JZgiOT056tmbVWuQ5XFWCIp++PcFkd0buhV88yCr58AGDUDwIl4uBgxdOCVVWEwzR+qD4ZyCN9RYHfiekk7ZYbv+1P0s0y9Vv16Us4FRGHpTMfrjZGFjfWvvSFDHW6PXSjaj3UWmuXiNpp9VI99VJTDGmcbkds/AHDRRmeYAI=
Received: from BYAPR11MB2631.namprd11.prod.outlook.com (52.135.227.28) by BYAPR11MB2982.namprd11.prod.outlook.com (20.177.224.138) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2073.14; Fri, 19 Jul 2019 10:23:21 +0000
Received: from BYAPR11MB2631.namprd11.prod.outlook.com ([fe80::91da:1669:aaf0:d428]) by BYAPR11MB2631.namprd11.prod.outlook.com ([fe80::91da:1669:aaf0:d428%4]) with mapi id 15.20.2094.013; Fri, 19 Jul 2019 10:23:20 +0000
From: "Rob Wilton (rwilton)" <rwilton@cisco.com>
To: Vladimir Vassilev <vladimir@transpacket.com>, Peter Schneider <Peter.Schneider@kontron.com>, "netmod@ietf.org" <netmod@ietf.org>, "draft-ietf-netmod-intf-ext-yang@ietf.org" <draft-ietf-netmod-intf-ext-yang@ietf.org>
Thread-Topic: [netmod] Question regarding RFC 8344
Thread-Index: AQHVOAqxOQ2eErtrGE+3EQjS430EUKbKwXuAgAcFbLA=
Date: Fri, 19 Jul 2019 10:23:20 +0000
Message-ID: <BYAPR11MB2631AE944FB57D4AE416ADD5B5CB0@BYAPR11MB2631.namprd11.prod.outlook.com>
References: <fa13ed97-bd27-7d8e-921b-567521f5e739@kontron.com> <40226c76-0f5a-2680-fd92-0ebfbdd5a8b8@transpacket.com>
In-Reply-To: <40226c76-0f5a-2680-fd92-0ebfbdd5a8b8@transpacket.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=rwilton@cisco.com;
x-originating-ip: [173.38.220.36]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 7df99470-e0e8-4a8d-3910-08d70c331fa1
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(5600148)(711020)(4605104)(1401327)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(2017052603328)(7193020); SRVR:BYAPR11MB2982;
x-ms-traffictypediagnostic: BYAPR11MB2982:
x-ms-exchange-purlcount: 1
x-microsoft-antispam-prvs: <BYAPR11MB2982D226200CE29FCBD96BECB5CB0@BYAPR11MB2982.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 01039C93E4
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(376002)(136003)(366004)(39860400002)(346002)(396003)(13464003)(199004)(189003)(55016002)(7736002)(66066001)(81156014)(81166006)(2201001)(8676002)(52536014)(71190400001)(476003)(71200400001)(2501003)(5660300002)(6506007)(446003)(11346002)(229853002)(6436002)(53546011)(486006)(33656002)(102836004)(68736007)(99286004)(305945005)(7696005)(86362001)(256004)(14444005)(110136005)(76116006)(66476007)(66556008)(64756008)(6246003)(66446008)(66946007)(26005)(478600001)(76176011)(74316002)(316002)(6116002)(2906002)(3846002)(186003)(14454004)(25786009)(6306002)(53936002)(8936002)(9686003); DIR:OUT; SFP:1101; SCL:1; SRVR:BYAPR11MB2982; H:BYAPR11MB2631.namprd11.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX: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: dH7gj/u9PcE2JTl71eVmY2urhCgR5U9R0GBMyfxcdeq+W1OSlE25rU1VhUTknCMxbhvbBTqa8/Gyk0DZBiyVLFQgHyUJRpxeeIiwjL5oFaUC9uoKXFNSNdtRLD25WNGRU/M+n58uU2wkFy+Bwtjt5SAwRTcaQBCwPcev9cOPQbFX2lzjMGvI87+4qb7tw3I9AYGGbriavnL0VakbSEO8kN/kPFkdzrRKrGD82m+03nTFFhQlWPJiOEXx9dvOv9Ny0quqF7PQg7WWMwdFkqcGz8xW8oleBJKrLHC5U9mM6mLw4ETgXse10CuyntjUoHhlj2BjsDtAyT/pQE/3dmBARkIpEDZuXWqqLpPh0LilkAUuBC/Y8WmjxduvPS+6yFRQefK7hiPQ77I8azDzf6Gyn6kWRHDAwlZ6B54Uk+iqhTs=
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 7df99470-e0e8-4a8d-3910-08d70c331fa1
X-MS-Exchange-CrossTenant-originalarrivaltime: 19 Jul 2019 10:23:20.7310 (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: rwilton@cisco.com
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BYAPR11MB2982
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.36.7.24, xch-aln-014.cisco.com
X-Outbound-Node: alln-core-3.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/75YLMW3qTPuh1_JzrW60z-sTCNg>
Subject: Re: [netmod] Question regarding RFC 8344
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: NETMOD WG list <netmod.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netmod>, <mailto:netmod-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netmod/>
List-Post: <mailto:netmod@ietf.org>
List-Help: <mailto:netmod-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netmod>, <mailto:netmod-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Jul 2019 10:23:29 -0000

Hi,

draft-ietf-netmod-intf-ext-yang-07, in WGLC, defines just such an MTU config item (called l2-mtu).

This is currently defined as a uint16, but perhaps this could/should be defined as uint32 instead.

Thanks,
Rob


-----Original Message-----
From: Vladimir Vassilev <vladimir@transpacket.com> 
Sent: 15 July 2019 00:07
To: Peter Schneider <Peter.Schneider@kontron.com>; netmod@ietf.org; draft-ietf-netmod-intf-ext-yang@ietf.org
Subject: Re: [netmod] Question regarding RFC 8344

On 7/11/19 7:04 PM, Peter Schneider wrote:
> Hi,
>
> I stumbled on an incompatibility between the IP Management YANG Module 
> and the real world:
> In the 'container ipv4', the leaf 'mtu' is declared as uint16 in the 
> range 68..max, which is effective the range 68..65535, as noted in rfc
> 7950 <https://tools.ietf.org/html/rfc7950#section-9.2> .
> On the other side, the default MTU size of the loopback interface in 
> Linux is 65536 since several years.

I don't think there is a problem with RFC 8344 since the ipv4 protocol MTU can not exceed 65535 bytes (RFC 791). The maximum payload supported by an interface which is the case with the default value of the lo interface MTU on your Linux distribution (seems this can be configured to up to 2147483647 octets at least on mine) has to be greater then the MTUs of all protocols (ipv4,ipv6 etc.) supported on that interface but they do not need to be equal. It is indeed recommended that the maximum "length of the data field of a packet" is used as defined in RFC 894 e.g. 1500 for ethernet but you can choose or be constrained (like in this case) to not do so.

Currently there is no IETF RFC module that has data definition for control of the interface MTU used as an upper limit for all protocol MTUs

v2.23.0 | Report a Bug | By Email