Re: [netmod] WG Last Call: draft-ietf-netmod-intf-ext-yang-07

Vladimir Vassilev <vladimir@transpacket.com> Mon, 12 August 2019 08:25 UTC

Return-Path: <vladimir@transpacket.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 29D6E120A2F for <netmod@ietfa.amsl.com>; Mon, 12 Aug 2019 01:25:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 jSm9kTMkiRYF for <netmod@ietfa.amsl.com>; Mon, 12 Aug 2019 01:24:19 -0700 (PDT)
Received: from mail.transpacket.com (s91205186171.blix.com [91.205.186.171]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 853ED120E57 for <netmod@ietf.org>; Sun, 11 Aug 2019 10:56:00 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail.transpacket.com (Postfix) with ESMTP id 3BCC648035CE; Sun, 11 Aug 2019 19:55:58 +0200 (CEST)
Received: from mail.transpacket.com ([127.0.0.1]) by localhost (mail.transpacket.com [127.0.0.1]) (amavisd-new, port 10032) with ESMTP id Omk62S_Dt2ZS; Sun, 11 Aug 2019 19:55:58 +0200 (CEST)
Received: from localhost (localhost [127.0.0.1]) by mail.transpacket.com (Postfix) with ESMTP id 0BCB948035C0; Sun, 11 Aug 2019 19:55:58 +0200 (CEST)
Received: from mail.transpacket.com ([127.0.0.1]) by localhost (mail.transpacket.com [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id nwjMJnn34GhG; Sun, 11 Aug 2019 19:55:57 +0200 (CEST)
Received: from [192.168.0.21] (cm-84.209.19.126.getinternet.no [84.209.19.126]) by mail.transpacket.com (Postfix) with ESMTPSA id CBC614803564; Sun, 11 Aug 2019 19:55:57 +0200 (CEST)
To: "Rob Wilton (rwilton)" <rwilton@cisco.com>, "Acee Lindem (acee)" <acee@cisco.com>, Kent Watsen <kent+ietf@watsen.net>, "netmod@ietf.org" <netmod@ietf.org>, Lou Berger <lberger@labn.net>
References: <0100016bd93bfe12-b7c7407d-7c5f-4d61-a714-3aa38b0d1da7-000000@email.amazonses.com> <80F2E6D2-8F6A-4EF4-9838-45AC48BE84E5@cisco.com> <BYAPR11MB2631CAAA7837907190FF7786B5C90@BYAPR11MB2631.namprd11.prod.outlook.com> <897E77D0-5EB6-4C05-BED2-F1DB3D26948B@cisco.com> <BYAPR11MB2631371D0987EA2B11A18807B5D40@BYAPR11MB2631.namprd11.prod.outlook.com> <f6d60abc-dc0f-8243-f006-a97fa958a495@transpacket.com> <MN2PR11MB4366CC6D801801E9B7F5E10AB5D00@MN2PR11MB4366.namprd11.prod.outlook.com>
From: Vladimir Vassilev <vladimir@transpacket.com>
Message-ID: <c9406407-1053-1ede-0867-343e58eb2cd1@transpacket.com>
Date: Sun, 11 Aug 2019 19:55:57 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0
MIME-Version: 1.0
In-Reply-To: <MN2PR11MB4366CC6D801801E9B7F5E10AB5D00@MN2PR11MB4366.namprd11.prod.outlook.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/pXpXj6XYyhcZtoF761c6B7XiOP4>
Subject: Re: [netmod] WG Last Call: draft-ietf-netmod-intf-ext-yang-07
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: Mon, 12 Aug 2019 08:25:21 -0000

On 11/08/2019 13.50, Rob Wilton (rwilton) wrote:

> Hi Vladimir,
>
> Thanks for the comments.
>
> Regarding increasing the L2 MTU if 802.1Q tags are present, this is because of how IEEE 802.3 defines the MTU of an Ethernet interface (at least for a single 802.1Q tag).
Where does IEEE 802.3 define "MTU of an Ethernet interface" (me being 
positive IEEE 802.3 or 802.1Q do not use MTU definition at all)?
>
> If you have a mix of single and double tagged sub-intefaces, it also means that the IP MTU for all of those sub-interfaces can be the same.
>
> E.g. if you set the L2 MTU of a physical interface to 1514 (excluding FCS bytes) then the IP MTU for each of the sub-interfaces would be 1500 bytes regardless of whether they are configured to match single or double VLAN tags.
>
> Conversely, if you have a strict L2 MTU that doesn't have this flexibility then a single tagged sub-interface would end up with an IP MTU of 1496, and a double tagged sub-interface would end up with an IP MTU of 1492, complicating L3 configuration.

The problem can become very complicated  if we introduce new definition 
of MTU (I still do not agree L2 MTU is a thing).

Why the ifMtu object from IF-MIB is not mapped to config false 
/ietf-interfaces:interfaces/interface/ietf-interfaces-common:mtu in 
ietf-intefaces-common.yang and instead we need something else?

 From RFC 2863:

  ifMtu OBJECT-TYPE
     SYNTAX      Integer32
     MAX-ACCESS  read-only
     STATUS      current
     DESCRIPTION
             "The size of the largest packet which can be sent/received
             on the interface, specified in octets.  For interfaces that
             are used for transmitting network datagrams, this is the
             size of the largest network datagram that can be sent on the
             interface."
     ::= { ifEntry 4 }
IMO this sounds as useful today as it did before.

 From RFC 8343 "4.  Relationship to the IF-MIB":

    The ifMtu object from the IF-MIB is not mapped to the
    "ietf-interfaces" module.  It is expected that interface-type-
    specific YANG modules provide interface-type-specific MTU leafs by
    augmenting the "ietf-interfaces" model.

I am aware of that text too but I do not agree mapping ifMtu which is 
interface type independent to /interfaces/interface/mtu is not necessay 
and can be replaced by introducing "interface-type-specific MTU leafs".

Vladimir

>
> BTW, I'll be on PTO for a week, so please expect a delay in response.
>
> Thanks,
> Rob
>