Re: [ieee-ietf-coord] [Detnet] Fwd: New Version Notification for draft-vassilev-netmod-network-bridge-00.txt
Vladimir Vassilev <vladimir@transpacket.com> Tue, 07 August 2018 15:17 UTC
Return-Path: <vladimir@transpacket.com>
X-Original-To: ieee-ietf-coord@ietfa.amsl.com
Delivered-To: ieee-ietf-coord@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C88FF130E47; Tue, 7 Aug 2018 08:17:37 -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_PASS=-0.001, URIBL_BLOCKED=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 qUUPdy1e_v6U; Tue, 7 Aug 2018 08:17:34 -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 E9F6E130E54; Tue, 7 Aug 2018 08:17:33 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail.transpacket.com (Postfix) with ESMTP id 4C5E61561735; Tue, 7 Aug 2018 17:17:31 +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 Srwd0ETsFbP8; Tue, 7 Aug 2018 17:17:31 +0200 (CEST)
Received: from localhost (localhost [127.0.0.1]) by mail.transpacket.com (Postfix) with ESMTP id 1E0E61561733; Tue, 7 Aug 2018 17:17:31 +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 NGkk4FihiVw3; Tue, 7 Aug 2018 17:17:31 +0200 (CEST)
Received: from [192.168.209.122] (s1853520235.blix.com [185.35.202.35]) by mail.transpacket.com (Postfix) with ESMTPSA id E54A21561730; Tue, 7 Aug 2018 17:17:30 +0200 (CEST)
To: János Farkas <janos.farkas@ericsson.com>
Cc: "netmod@ietf.org" <netmod@ietf.org>, detnet@ietf.org, "ieee-ietf-coord@ietf.org" <ieee-ietf-coord@ietf.org>
References: <153163104655.12797.4549822574205791661.idtracker@ietfa.amsl.com> <1671ad91-5627-fedf-ef1c-9a2a790accd4@transpacket.com> <bb04cb6f-5940-f883-ba80-ad110d192eb2@ericsson.com>
From: Vladimir Vassilev <vladimir@transpacket.com>
Message-ID: <ef0e9999-e1f7-bc15-3335-f3f49d869ca7@transpacket.com>
Date: Tue, 07 Aug 2018 17:17:30 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0
MIME-Version: 1.0
In-Reply-To: <bb04cb6f-5940-f883-ba80-ad110d192eb2@ericsson.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/ieee-ietf-coord/BGlmoZZUPpzt7w4vsfL9AFvODuI>
Subject: Re: [ieee-ietf-coord] [Detnet] Fwd: New Version Notification for draft-vassilev-netmod-network-bridge-00.txt
X-BeenThere: ieee-ietf-coord@ietf.org
X-Mailman-Version: 2.1.27
Precedence: list
List-Id: Management-level discussions between IEEE and IETF on topics of interest to both SDOs <ieee-ietf-coord.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ieee-ietf-coord>, <mailto:ieee-ietf-coord-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ieee-ietf-coord/>
List-Post: <mailto:ieee-ietf-coord@ietf.org>
List-Help: <mailto:ieee-ietf-coord-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ieee-ietf-coord>, <mailto:ieee-ietf-coord-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Aug 2018 15:17:38 -0000
Hi Janos, The concept defined in this draft goes outside the scope of 802.1Q. Taking a subset of the OpenFlow 1.0 spec and defining corresponding node-side YANG model with transactional flow table (/flows) and optional support for controller introducing single RPC (transmit-packet) and notification (packet-received) corresponding to OFPT_PACKET_OUT and OFPT_PACKET_IN messages seemed like a natural evolution of the SDN concept for the specification of alternative to OpenFlow southbound protocol (e.g. over NETCONF). With OpenFlow-derived flow model addressing 1. forwarding (switching) and adding a 2. flexible scheduler model referencing the flows a complete bridge model is presented. It can be implemented seamlessly on all OpenFlow 1.0 and above supporting hardware and more importantly extensions (to flow forwarding or scheduling) to the OpenFlow spec can be specified in YANG. A device implementing this model can implement the 802.1Q family of models with proper controller software (STP, LLDP etc. which is readily available) but it is not limited to that. We have been following closely the models developed by the IEEE TSN and we have both reused terminology and ensured all of those standard solutions can be represented with the generic scheduler model part of this draft. The IEEE YANG model is great reference but is not suitable for all applications especially when more flexibility is required and being able to augment a module to document our vendor specific extensions. The 802.1Q are limited in certain ways to 802.1Q (for example fixed to 8 traffic classes either priority or time slots). Attempts to make 802.1Q configuration more generic and a subset to a more generic forwarding configuration mechanism are not unprecedented (see https://datatracker.ietf.org/doc/draft-ietf-netmod-sub-intf-vlan-model/ ). Here virtual interfaces instead of flows are introduced. IMO a standard flows model is needed starting from something with running software and trying to find consensus. I see this goal is already part of the detnet focus https://tools.ietf.org/html/draft-ietf-detnet-flow-information-model and https://datatracker.ietf.org/doc/draft-geng-detnet-conf-yang Requesting comments on the ietf netmod list seemed like a good place to start to allow for open discussion and if we manage to identify anything that falls into the scope of IEEE 802.1Q except the name "bridge" I would be glad to contribute there. Same goes for the detnet WG. Vladimir On 08/03/2018 05:59 PM, János Farkas wrote: > Hi Vladimir, > > Bridging including bridge management belong to IEEE 802.1: > https://1.ieee802.org/. You may consider contributing to IEEE 802.1. > The next Interim is hosed by your company in Oslo: > https://1.ieee802.org/meetings. > > IEEE 802.1Qcp is the basic bridge management specification, which is > an approved draft standard to be published soon: > http://standards.ieee.org/findstds/standard/802.1Qcp-2018.html. (The > archived web page of the finished project: > https://1.ieee802.org/tsn/802-1qcp.) > > The pages of the ongoing projects are available via the TSN page: > https://1.ieee802.org/tsn/#Ongoing_TSN_Projects, including P802.1Qcw > (https://1.ieee802.org/tsn/802-1qcw/), which specifies YANG for > various bridge scheduling mechanisms. > > Best regards, > Janos > > > On 7/17/2018 4:26 PM, Vladimir Vassilev wrote: >> Hi, >> >> I have submitted a draft >> https://datatracker.ietf.org/doc/draft-vassilev-netmod-network-bridge/ >> that proposes a model for network bridge management based on the >> concept of flows. The model has 2 components 1. Forwarding based on >> flows. 2. Scheduling/QoS based on gate controller topologies that >> provide a new and very generic way of modeling and managing the >> actual scheduler design and map the flows to scheduler topology inputs. >> >> There is similar work on the flow based forwarding in detnet however >> I am not sure detnet is the right workgroup to be defining the flow >> model. I think the flow concept is important and general. It is as >> significant as the concept of interfaces and is not only relevant to >> detnet. Let me know what is your opinion of the draft and the >> proposed network bridge concept. >> >> Vladimir >> >> -------- Forwarded Message -------- >> Subject: New Version Notification for >> draft-vassilev-netmod-network-bridge-00.txt >> Date: Sat, 14 Jul 2018 22:04:06 -0700 >> From: internet-drafts@ietf.org >> To: Vladimir Vassilev <vladimir@transpacket.com> >> >> >> >> A new version of I-D, draft-vassilev-netmod-network-bridge-00.txt >> has been successfully submitted by Vladimir Vassilev and posted to the >> IETF repository. >> >> Name: draft-vassilev-netmod-network-bridge >> Revision: 00 >> Title: A YANG Data Model for Network Bridge Management >> Document date: 2018-07-14 >> Group: Individual Submission >> Pages: 44 >> URL: >> https://www.ietf.org/internet-drafts/draft-vassilev-netmod-network-bridge-00.txt >> Status: >> https://datatracker.ietf.org/doc/draft-vassilev-netmod-network-bridge/ >> Htmlized: >> https://tools.ietf.org/html/draft-vassilev-netmod-network-bridge-00 >> Htmlized: >> https://datatracker.ietf.org/doc/html/draft-vassilev-netmod-network-bridge >> >> >> Abstract: >> This document introduces new YANG model of a network bridge. >> >> >> >> Please note that it may take a couple of minutes from the time of >> submission >> until the htmlized version and diff are available at tools.ietf.org. >> >> The IETF Secretariat >> >> _______________________________________________ >> detnet mailing list >> detnet@ietf.org >> https://www.ietf.org/mailman/listinfo/detnet >
- Re: [ieee-ietf-coord] [Detnet] Fwd: New Version N… János Farkas
- Re: [ieee-ietf-coord] [Detnet] Fwd: New Version N… Vladimir Vassilev