Re: [Detnet] L2/L3 model?

"Norman Finn (nfinn)" <nfinn@cisco.com> Wed, 19 November 2014 00:15 UTC

Return-Path: <nfinn@cisco.com>
X-Original-To: detnet@ietfa.amsl.com
Delivered-To: detnet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 554E31A82E2 for <detnet@ietfa.amsl.com>; Tue, 18 Nov 2014 16:15:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.095
X-Spam-Level:
X-Spam-Status: No, score=-15.095 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, RP_MATCHES_RCVD=-0.594, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 0yNi6ju1rXKj for <detnet@ietfa.amsl.com>; Tue, 18 Nov 2014 16:15:38 -0800 (PST)
Received: from rcdn-iport-8.cisco.com (rcdn-iport-8.cisco.com [173.37.86.79]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 51C7E1A802F for <detnet@ietf.org>; Tue, 18 Nov 2014 16:15:38 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3712; q=dns/txt; s=iport; t=1416356138; x=1417565738; h=from:to:subject:date:message-id:references:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=1/dqaFziFHLONTaOcHVljVXJb+iJXDlMzCyXp/RU4J4=; b=ZNN7/Gw45kszlA7swaUl1cpXtNjfmB6TrSe0JpPGQ6M+L+/wQCeoTKFj 6kQAsSUd4hyR/ktN3bGhUdPfFrMtI7sxkpf5sMwA20CIKk22mjnAHGYlO FYc9CoxZJcBncJNpDG6L9t2gnucJBWSNHYlq9EItxUAcDN93ecMQTTkv9 Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgYHAK/fa1StJV2b/2dsb2JhbABagmsjVVkEgwLJGAqGdFUCHHAWAQEBAQF9hAIBAQEEAQEBIBE6FwQCAQgRAwECAwImAgICJQsVCAgCBAESiEEBDLsjlwABAQEBAQEBAQEBAQEBAQEBAQEBFQSBLY8oOgaCcYFUBZAngiiMB5Z5g3ttgUiBAwEBAQ
X-IronPort-AV: E=Sophos;i="5.07,413,1413244800"; d="scan'208";a="373351705"
Received: from rcdn-core-4.cisco.com ([173.37.93.155]) by rcdn-iport-8.cisco.com with ESMTP; 19 Nov 2014 00:15:37 +0000
Received: from xhc-aln-x05.cisco.com (xhc-aln-x05.cisco.com [173.36.12.79]) by rcdn-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id sAJ0Fa1S019930 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 19 Nov 2014 00:15:36 GMT
Received: from xmb-aln-x02.cisco.com ([fe80::8c1c:7b85:56de:ffd1]) by xhc-aln-x05.cisco.com ([173.36.12.79]) with mapi id 14.03.0195.001; Tue, 18 Nov 2014 18:15:36 -0600
From: "Norman Finn (nfinn)" <nfinn@cisco.com>
To: Erik Nordmark <nordmark@acm.org>, "detnet@ietf.org" <detnet@ietf.org>
Thread-Topic: [Detnet] L2/L3 model?
Thread-Index: AQHQApHutQdyv9S27UablPIlvm6opJxm85wA
Date: Wed, 19 Nov 2014 00:15:36 +0000
Message-ID: <D0911B51.35150%nfinn@cisco.com>
References: <546A3A37.7070205@acm.org>
In-Reply-To: <546A3A37.7070205@acm.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.4.3.140616
x-originating-ip: [10.21.114.110]
Content-Type: text/plain; charset="utf-8"
Content-ID: <953A9E84D07F5B47B3ACEDC3BD004245@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/detnet/D3IYnAF0QCXC-fHH3vTSvrddCI8
Subject: Re: [Detnet] L2/L3 model?
X-BeenThere: detnet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Discussions on Deterministic Networking, characterized by 1\) resource reservation; 2\) 0 congestion loss and guaranteed latency; 3\) over L2-only and mixed L2 and L3 networks; and 5\) 1+1 replication/deletion." <detnet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/detnet>, <mailto:detnet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/detnet/>
List-Post: <mailto:detnet@ietf.org>
List-Help: <mailto:detnet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/detnet>, <mailto:detnet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Nov 2014 00:15:40 -0000

Catching up on my email.

I agree most definitely that we want to explore arbitrary combinations of
L2/L3, with paths including any combination of routers and bridges.

Without going too deep into MPLS/Pseudo-wire topics, let me point out that
what the bridges need is a pair {VLAN, multicast destination MAC address}
that uniquely identifies the flow to which the Ethernet frame belongs (at
least among the packets seen by that bridge).  The bridges don’t care
whether MPLS is present in the frame or not.  So, if the routers can apply
a {VLAN, MAC address} to the packet that will be handled by a bridge, then
the routers can switch on the MPLS labels and the bridges on the Ethernet
stuff.

Note that MPLS labels can go end-to-end, or as close to the ends as you
want them to go, as is normal for MPLS; you don’t need to get rid of MPLS
when going through the bridges.

How close this gets to the Talker and Listener is another matter, and we
can talk about that in another message.

— Norm

-----Original Message-----
From: Erik Nordmark <nordmark@acm.org>
Date: Monday, November 17, 2014 at 10:11 AM
To: "detnet@ietf.org" <detnet@ietf.org>
Subject: [Detnet] L2/L3 model?

>
>After the BoF I realized there was one thing we didn't talk about which
>is what combined L2 and L3 topologies that folks have in mind.
>It is true that from a packet forwarding perspective both L2 and L3 have
>queues and clocks, but the interaction with the control plane and the
>approach might be different for different forms of combinations.
>
>First of all we have 6TISCH which is an L3-only network.
>
>But in combined L2/L3 networks we could have at least
>  - interconnecting L2 islands using L3
>  - arbitrary topologies with mixtures of L2 and L3 forwarding devices
>
>A suggestion (at the mike during the BoF) was to consider pseudo-wires.
>That might make sense when interconnecting L2 islands.
>But with arbitrary topologies one could end with with a path that as a
>mixture of bridges and routers e.g.
>
>      Sender - B1 - B2 - R1 - B3 - B4 - B5 - R2 - R3 - Listener
>
>Are there use cases that result in such topologies/paths?
>
>Would one need one controller which is aware of both the L2 and L3
>devices and can pick paths (with resources) that include both?
>(Typically we separate the layers thus we might have a PCE which sees
>the L3 topology but not the L2 devices in between the routers.)
>
>I think it would be good to explore the combined L2/L3 use cases and
>models in more detail.
>
>    Erik
>
>_______________________________________________
>detnet mailing list
>detnet@ietf.org
>https://www.ietf.org/mailman/listinfo/detnet