Re: [Detnet] Implementing the discussion at IETF 97 on architecture doc
Jouni Korhonen <jouni.korhonen@broadcom.com> Wed, 08 March 2017 20:36 UTC
Return-Path: <jouni.korhonen@broadcom.com>
X-Original-To: detnet@ietfa.amsl.com
Delivered-To: detnet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C582A12946F for <detnet@ietfa.amsl.com>; Wed, 8 Mar 2017 12:36:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level:
X-Spam-Status: No, score=-2.701 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_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=broadcom.com
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 jCZe-Ez94emf for <detnet@ietfa.amsl.com>; Wed, 8 Mar 2017 12:36:48 -0800 (PST)
Received: from mail-qk0-x22d.google.com (mail-qk0-x22d.google.com [IPv6:2607:f8b0:400d:c09::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 045BD129410 for <detnet@ietf.org>; Wed, 8 Mar 2017 12:36:48 -0800 (PST)
Received: by mail-qk0-x22d.google.com with SMTP id 1so86025915qkl.3 for <detnet@ietf.org>; Wed, 08 Mar 2017 12:36:47 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=broadcom.com; s=google; h=reply-to:subject:references:to:cc:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=GIu3PgR7IgWu4EEhtt3xFonWKkeIyNeQLJRaCcQqq/8=; b=c+1AZyF5qGP2Dio70WM9AoCojVTBSb3ONH6dazA9VRa8fHmA0cDSpJpAPbBLFHfppD TghsSn0eGArjlVDrPF+qDCFz2173wTlO93lof8FZgh/7nWMKCmIVf0j3y8yV7bC7q6uT pw4X1RoWhlMxM+74HM7r8kMe3v+nUwzuNnAVs=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:reply-to:subject:references:to:cc:from :message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding; bh=GIu3PgR7IgWu4EEhtt3xFonWKkeIyNeQLJRaCcQqq/8=; b=OExMmPSxxFXEnnKGCDEtmM0kGZIkQY6MYMjTGpZ7ZH3Pi/mtDLxO34mIViSnMun9d8 +NhR/RfcSojcq4Baig6AyKwYIb1KWLoDHC6AIFYiDU2GdQdi2bn5MEy6SDTV8cfFesej 0XMSr16XCcfUADMPTZ9VBrvDwKQCJVzZYUzqQ9JsZg3lC/1loYCpxDt1TFBM9okK4sSr U+zG+7QPb74kWXvCI30KJDug1YwZUUttKlnhUszxFoMIQ90aiJSKIpSPMF1hhGZVkjy8 1BJ7UDvNAsOw4uwA4AsluaNoAVa1zKMUD8sG/yVZdKmVvRX2NobO5KYcDsIDQgj3iPvW BKog==
X-Gm-Message-State: AMke39m0n003bvFN1I0k9TQrYsnQzA5h/6t3WmIHkoAQb00+cMth1ZgvOARhN5P5Tgdt9ofM
X-Received: by 10.200.55.152 with SMTP id d24mr9819436qtc.1.1489005406763; Wed, 08 Mar 2017 12:36:46 -0800 (PST)
Received: from [192.168.88.100] ([216.31.219.19]) by smtp.gmail.com with ESMTPSA id q145sm2837562qke.39.2017.03.08.12.36.45 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 08 Mar 2017 12:36:46 -0800 (PST)
References: <772d53cbc39549a889d356f5be511c12@XCH-RCD-001.cisco.com>
To: "Pascal Thubert (pthubert)" <pthubert@cisco.com>, "detnet@ietf.org" <detnet@ietf.org>
From: Jouni Korhonen <jouni.korhonen@broadcom.com>
Message-ID: <6d8ec0b1-581a-9cbf-2dc9-bd1f3fcc6864@broadcom.com>
Date: Wed, 08 Mar 2017 12:36:44 -0800
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <772d53cbc39549a889d356f5be511c12@XCH-RCD-001.cisco.com>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/detnet/KAEqhSwC2-lGn2QF3OTZS3MSz54>
Cc: "draft-ietf-detnet-architecture-all@tools.ietf.org" <draft-ietf-detnet-architecture-all@tools.ietf.org>
Subject: Re: [Detnet] Implementing the discussion at IETF 97 on architecture doc
X-BeenThere: detnet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: jouni.korhonen@broadcom.com
List-Id: Discussions on Deterministic Networking BoF and Proposed WG <detnet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/detnet>, <mailto:detnet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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, 08 Mar 2017 20:36:50 -0000
Hi, [snip] > 4.9.2. Flow attribute mapping between layers > > > Transport of DetNet flows over multiple technology domains may > require that lower layers are aware of specific flows of higher > layers. Such an "exporting of flow identification" is needed each > time when the forwarding paradigm is changed on the transport path > (e.g., two LSRs are interconnected by a L2 bridged domain, etc.). > The three main forwarding methods considered for deterministic > networking are: > > o IP routing > > o MPLS label switching > > o Ethernet bridging > > The simplest solution for generalized flow identification could be to > define a unique Flow-ID triplet per DetNet flow (e.g., [IP: "IPv6- > flow-label"+"IPv6-address"; MPLS: "PW-label"+"LSP-label"; Ethernet: The discussion on this part has not yet completed in DP design team. I am a bit worried writing this specific part down before we actually know how we are going to implement on the data plane. The above is not, as far as I understand, aligned with the DT progress. To get around the chicken-egg thing here either defer documenting for now or emphasize more that the above is an example. - Jouni > "VLAN-ID"+"MAC-address"). This triplet can be used by the DetNet > encoding function of technology border nodes (where forwarding > paradigm changes) to adapt to capabilities of the next hop node. It > means that a packet may contain multiple (forwarding paradigm > specific) Flow-IDs during its transport. Technology border nodes may > add / remove a (forwarding paradigm specific) Flow-ID. [snap] > What do you think? > > > > Pascal and Norm > > > > _______________________________________________ > detnet mailing list > detnet@ietf.org > https://www.ietf.org/mailman/listinfo/detnet >
- [Detnet] Implementing the discussion at IETF 97 o… Pascal Thubert (pthubert)
- Re: [Detnet] Implementing the discussion at IETF … Jouni Korhonen
- Re: [Detnet] Implementing the discussion at IETF … Pascal Thubert (pthubert)
- Re: [Detnet] Implementing the discussion at IETF … Lou Berger
- Re: [Detnet] Implementing the discussion at IETF … Pascal Thubert (pthubert)
- Re: [Detnet] Implementing the discussion at IETF … Lou Berger
- Re: [Detnet] Implementing the discussion at IETF … Jouni Korhonen
- Re: [Detnet] Implementing the discussion at IETF … gengxuesong
- Re: [Detnet] Implementing the discussion at IETF … Pascal Thubert (pthubert)