Re: [Detnet] Implementing the discussion at IETF 97 on architecture doc
Lou Berger <lberger@labn.net> Thu, 09 March 2017 16:23 UTC
Return-Path: <lberger@labn.net>
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 6679D1296A8 for <detnet@ietfa.amsl.com>; Thu, 9 Mar 2017 08:23:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.501
X-Spam-Level:
X-Spam-Status: No, score=-1.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_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, RCVD_IN_SORBS_SPAM=0.5, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (768-bit key) header.d=labn.net
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 oNUa1iJpq7jm for <detnet@ietfa.amsl.com>; Thu, 9 Mar 2017 08:23:49 -0800 (PST)
Received: from gproxy6-pub.mail.unifiedlayer.com (gproxy6-pub.mail.unifiedlayer.com [67.222.39.168]) by ietfa.amsl.com (Postfix) with SMTP id 5CE4712969F for <detnet@ietf.org>; Thu, 9 Mar 2017 08:23:49 -0800 (PST)
Received: (qmail 20943 invoked by uid 0); 9 Mar 2017 16:23:49 -0000
Received: from unknown (HELO cmgw3) (10.0.90.84) by gproxy6.mail.unifiedlayer.com with SMTP; 9 Mar 2017 16:23:49 -0000
Received: from box313.bluehost.com ([69.89.31.113]) by cmgw3 with id tsPd1u00G2SSUrH01sPgaK; Thu, 09 Mar 2017 09:23:40 -0700
X-Authority-Analysis: v=2.1 cv=WOnsABcR c=1 sm=1 tr=0 a=h1BC+oY+fLhyFmnTBx92Jg==:117 a=h1BC+oY+fLhyFmnTBx92Jg==:17 a=L9H7d07YOLsA:10 a=9cW_t1CCXrUA:10 a=s5jvgZ67dGcA:10 a=N659UExz7-8A:10 a=xqWC_Br6kY4A:10 a=6Iz7jQTuP9IA:10 a=NEAV23lmAAAA:8 a=wU2YTnxGAAAA:8 a=AUd_NHdVAAAA:8 a=Q-fNiiVtAAAA:8 a=48vgC7mUAAAA:8 a=j2Yptn8xsA1yUonQ3jwA:9 a=vLKbLIt5zTMZd_6L:21 a=59ZtSZg1g1BetuaX:21 a=pILNOxqGKmIA:10 a=Bn2pgwyD2vrAyMmN8A2t:22 a=Yz9wTY_ffGCQnEDHKrcv:22 a=TSZmLRzkpGLBZRr3r8m8:22 a=Fp8MccfUoT0GBdDC_Lng:22 a=w1C3t2QeGrPiZgrLijVG:22
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=labn.net; s=default; h=Content-Transfer-Encoding:Content-Type:In-Reply-To:MIME-Version :Date:Message-ID:From:Cc:References:To:Subject:Sender:Reply-To:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=KTRgmptpJBxmitid+CZhJ8+hSVDv0YkSEFNC4obTdQM=; b=kxHO4S6ZrPjk2pJDNPk9Br5qqG 9W4Wu+TDxWFyseD+WrZ+ke742SIyBHugERWhr6tNQbwmaxIPGvLk7Ma6kkinEX74V5OpOtCfaAll6 AxTtH+y3jsfxRrXSllKnEpM2C;
Received: from pool-100-15-85-191.washdc.fios.verizon.net ([100.15.85.191]:37438 helo=[IPv6:::1]) by box313.bluehost.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.87) (envelope-from <lberger@labn.net>) id 1cm0qm-0008U6-T3; Thu, 09 Mar 2017 09:23:36 -0700
To: "Pascal Thubert (pthubert)" <pthubert@cisco.com>, "jouni.korhonen@broadcom.com" <jouni.korhonen@broadcom.com>, "detnet@ietf.org" <detnet@ietf.org>
References: <772d53cbc39549a889d356f5be511c12@XCH-RCD-001.cisco.com> <6d8ec0b1-581a-9cbf-2dc9-bd1f3fcc6864@broadcom.com> <e9f6e0d2f3fe4c89b4ea9faba9187c73@XCH-RCD-001.cisco.com> <9496d000-cd69-f130-b7a0-aca404c5cb9f@labn.net> <7f06df491b014e6bb97608b6ca136a2a@XCH-RCD-001.cisco.com>
From: Lou Berger <lberger@labn.net>
Message-ID: <9e21bfc6-edfb-a7e0-3b53-588bfdff337e@labn.net>
Date: Thu, 09 Mar 2017 11:23:34 -0500
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <7f06df491b014e6bb97608b6ca136a2a@XCH-RCD-001.cisco.com>
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: 7bit
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - box313.bluehost.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - labn.net
X-BWhitelist: no
X-Source-IP: 100.15.85.191
X-Exim-ID: 1cm0qm-0008U6-T3
X-Source:
X-Source-Args:
X-Source-Dir:
X-Source-Sender: pool-100-15-85-191.washdc.fios.verizon.net ([IPv6:::1]) [100.15.85.191]:37438
X-Source-Auth: lberger@labn.net
X-Email-Count: 4
X-Source-Cap: bGFibm1vYmk7bGFibm1vYmk7Ym94MzEzLmJsdWVob3N0LmNvbQ==
Archived-At: <https://mailarchive.ietf.org/arch/msg/detnet/KNMCZFIQwEfF-1dxwsNuyykwTY8>
Cc: "draft-ietf-detnet-architecture@ietf.org" <draft-ietf-detnet-architecture@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
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: Thu, 09 Mar 2017 16:23:50 -0000
On 3/9/2017 11:11 AM, Pascal Thubert (pthubert) wrote: > Hello Lou: > > Did section 3 evolve since the publication in September? Not that I know of - but Jouni would know for sure. > Will there be an 01 of the dp alt draft before cutoff Monday? I don't expect on. Lou PS for source, see https://github.com/jounikor/draft-dt-detnet-dp-alt/blob/master/draft-ietf-detnet-dp-alt-00.xml > Take care, > > Pascal > > -----Original Message----- > From: Lou Berger [mailto:lberger@labn.net] > Sent: jeudi 9 mars 2017 15:13 > To: Pascal Thubert (pthubert) <pthubert@cisco.com>; jouni.korhonen@broadcom.com; detnet@ietf.org > Cc: draft-ietf-detnet-architecture@ietf.org > Subject: Re: [Detnet] Implementing the discussion at IETF 97 on architecture doc > > Pascal, > > Another thing to consider bringing into the Architecture document are some of the diagrams and related text from Section 3 of . I think the whole section, with the exception of the last two paragraphs on page 5, is good text to bring over. > > Lou > (as contributor, co-author of dp-alt) > > On 3/9/2017 3:06 AM, Pascal Thubert (pthubert) wrote: >> I agree, Jouni, >> >> we seem to be placing the horses before the cart. >> Let us comment out that text for now. >> >> Take care, >> >> Pascal >> >> -----Original Message----- >> From: Jouni Korhonen [mailto:jouni.korhonen@broadcom.com] >> Sent: mercredi 8 mars 2017 21:37 >> To: Pascal Thubert (pthubert) <pthubert@cisco.com>; detnet@ietf.org >> Cc: draft-ietf-detnet-architecture-all@tools.ietf.org >> Subject: Re: [Detnet] Implementing the discussion at IETF 97 on >> architecture doc >> >> 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 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)