Re: [Detnet-dp-dt] quick notes from call 2/14/15
Jiangyuanlong <jiangyuanlong@huawei.com> Sat, 25 February 2017 07:47 UTC
Return-Path: <jiangyuanlong@huawei.com>
X-Original-To: detnet-dp-dt@ietfa.amsl.com
Delivered-To: detnet-dp-dt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1])
by ietfa.amsl.com (Postfix) with ESMTP id 71C46129BDA
for <detnet-dp-dt@ietfa.amsl.com>; Fri, 24 Feb 2017 23:47:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level:
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5
tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01,
RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, 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 hopNZnxE0jVl for <detnet-dp-dt@ietfa.amsl.com>;
Fri, 24 Feb 2017 23:47:05 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17])
(using TLSv1 with cipher RC4-SHA (128/128 bits))
(No client certificate requested)
by ietfa.amsl.com (Postfix) with ESMTPS id 8E9C0129BD9
for <detnet-dp-dt@ietf.org>; Fri, 24 Feb 2017 23:47:04 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml707-cah.china.huawei.com)
([172.18.7.190])
by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued)
with ESMTP id DHS66853; Sat, 25 Feb 2017 07:47:02 +0000 (GMT)
Received: from SZXEMA412-HUB.china.huawei.com (10.82.72.71) by
lhreml707-cah.china.huawei.com (10.201.108.48) with Microsoft SMTP Server
(TLS) id 14.3.301.0; Sat, 25 Feb 2017 07:47:01 +0000
Received: from SZXEMA506-MBS.china.huawei.com ([169.254.4.67]) by
SZXEMA412-HUB.china.huawei.com ([10.82.72.71]) with mapi id 14.03.0235.001;
Sat, 25 Feb 2017 15:46:53 +0800
From: Jiangyuanlong <jiangyuanlong@huawei.com>
To: Jouni Korhonen <jouni.korhonen@broadcom.com>
Thread-Topic: [Detnet-dp-dt] quick notes from call 2/14/15
Thread-Index: AQHSh8L6xtkI2/QGN0uLR5/C/E+cXKF5WDXA
Date: Sat, 25 Feb 2017 07:46:52 +0000
Message-ID: <3B0A1BED22CAD649A1B3E97BE5DDD68BBAB150D6@szxema506-mbs.china.huawei.com>
References: <BDABA4E9-F3F5-4EA3-BB16-BE877A70F0B6@broadcom.com>
In-Reply-To: <BDABA4E9-F3F5-4EA3-BB16-BE877A70F0B6@broadcom.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.74.203.119]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0),
refid=str=0001.0A090204.58B13676.0071, ss=1, re=0.000, recu=0.000, reip=0.000,
cl=1, cld=1, fgs=0, ip=169.254.4.67,
so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: 7844260b22ad8ff8bb29619773406660
Archived-At: <https://mailarchive.ietf.org/arch/msg/detnet-dp-dt/zaRqE-bFOCL5xDnfj5VLkIHI8rs>
Cc: "detnet-dp-dt@ietf.org" <detnet-dp-dt@ietf.org>
Subject: Re: [Detnet-dp-dt] quick notes from call 2/14/15
X-BeenThere: detnet-dp-dt@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: DetNet WG Data Plane Design Team <detnet-dp-dt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/detnet-dp-dt>,
<mailto:detnet-dp-dt-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/detnet-dp-dt/>
List-Post: <mailto:detnet-dp-dt@ietf.org>
List-Help: <mailto:detnet-dp-dt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/detnet-dp-dt>,
<mailto:detnet-dp-dt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 25 Feb 2017 07:47:07 -0000
Hi Jouni, Some further comments based on our recent discussions. Thanks, Yuanlong From: Detnet-dp-dt [mailto:detnet-dp-dt-bounces@ietf.org] On Behalf Of Jouni Korhonen Sent: Thursday, February 16, 2017 3:37 AM To: detnet-dp-dt@ietf.org Subject: [Detnet-dp-dt] quick notes from call 2/14/15 Present: Jouni, Norm, Loa, Balazs, Janos, Carlos, Yuanlong. Agenda: - Was meant to be about CoS and QoS. However, we ended up discussion all time about proper layering and encapsulation of PW stack. Discussion: - Sequence number. We made a >>decision<< to settle down to 16 bits. This is the most “compatible” approach. At high speeds it has been argued 16 bits is not enough. In practical implementations even 16 bits of sequence number won’t be maintained. It is typically a much smaller window of the entire sequence number space (think about numbers.. 1M PWs times the seqnum bit vector etc..) [YJ] Good to be compatible with the generic CW. We need to be careful to avoid sequence number wrap up. 32Mbps detnet flow is enough to overflow the sequence in a second (if 64 bytes/packet is assumed). If the "eliminate first and then replicate" mechanism is used, detnet traffic from a S-PE may be looped back to itself, thus there is also a risk of sequence overrun. "replicate first and then eliminate" will be more safe IMO. - PWs and the label stack. See the latest slides from Loa and specifically the slide 9 (attached). I did add one slide to this deck, the slide 14. - T-labels are typically per hop. L-labels are between DetNet aware S/P-PEs and essentially form an overlay over the underlying network. d-pw labels are end to end (at the moment.. to be discussed) between the T-PEs or in general between the DetNet aware end point that understand the detnet data plane. [YJ] LSP is actually hop by hop allocated a label, though each hop can be overlaid in a tunnel itself. Thus T-labels and L-labels can be regarded as a single LSP label without loss of generality. PHP can be enabled optionally for this LSP. - currently all d-pw (detnet PW labels) experience FRER if that functionality is enabled. d-pw labels are tied to sequence numbers (the detnet CW). [YJ] Yes, d-pw label always go together with detnet CW. - L-labels seen beneficial allowing the autoconfiguration of FRER i.e., build the overlay over the network and do not care configuring the PWs. This mimics one 802.1CB feature (see .1CB sub-clause 7.11). [YJ] we don't need the L-label if MS-PW approach is taken, since each segment of PW can mimic the 802.1CB member stream. - L-labels also allow simple label swap in a detnet S-PE i.e., no FRER would be applied. [YJ] we don't need the L-label. PW swap is the only action if no FRER is applied, this is the traditional MS-PW mechanism. - This setup seems plausible. There was concerns overloading L-labels with some of the PW decision making in the fast path and thus possibly causing a lookup that needs to be done over two labels (L & d-pw). Essentially it is the L-label that signals whether the FRER gets applied. [YJ] Using an L-label to trigger an S-PE looking into the CW inside a PW will be less clean compared with using a PW label directly. - General consensus towards the PW instance “facing egress ports” in a detnet S-PE would do the elimination. This discussion needs to be completed. An interesting use case was described by Norm (see slide 14). An example: packet arrives from A towards B (flow X), it always gets replicated towards C, but towards D only if the same packet (from flow Y) has not earlier arrived from C. Whether this works ok with the current S-PE and PW instance doing elimination concepts needs to be verified. - Discussion to be completed whether there are cases where L-labels can be left out i.e., only use T-labels and d-pw labels. - Balazs said to provide a matrix/table of different permutations for labels & replications & eliminations. We’ll have a call next Tuesday 2/21/17. -- Jouni Korhonen, Broadcom Ltd. M: +1-408-391-7160 _______________________________________________ Detnet-dp-dt mailing list Detnet-dp-dt@ietf.org https://www.ietf.org/mailman/listinfo/detnet-dp-dt
- [Detnet-dp-dt] quick notes from call 2/14/15 Jouni Korhonen
- [Detnet-dp-dt] FRER example.. maybe a way forward… Jouni Korhonen
- Re: [Detnet-dp-dt] FRER example.. maybe a way for… Loa Andersson
- Re: [Detnet-dp-dt] FRER example.. maybe a way for… Jouni Korhonen
- Re: [Detnet-dp-dt] FRER example.. maybe a way for… Loa Andersson
- Re: [Detnet-dp-dt] FRER example.. maybe a way for… Jouni Korhonen
- Re: [Detnet-dp-dt] FRER example.. maybe a way for… Loa Andersson
- Re: [Detnet-dp-dt] FRER example.. maybe a way for… Jouni Korhonen
- Re: [Detnet-dp-dt] FRER example.. maybe a way for… Loa Andersson
- Re: [Detnet-dp-dt] FRER example.. maybe a way for… Jouni Korhonen
- Re: [Detnet-dp-dt] FRER example.. maybe a way for… Loa Andersson
- Re: [Detnet-dp-dt] FRER example.. maybe a way for… Jouni Korhonen
- Re: [Detnet-dp-dt] FRER example.. maybe a way for… Jouni Korhonen
- Re: [Detnet-dp-dt] FRER example.. maybe a way for… Loa Andersson
- [Detnet-dp-dt] An optional scheme that can suppor… Jiangyuanlong
- Re: [Detnet-dp-dt] An optional scheme that can su… Loa Andersson
- Re: [Detnet-dp-dt] An optional scheme that can su… Jouni Korhonen
- Re: [Detnet-dp-dt] An optional scheme that can su… Jiangyuanlong
- Re: [Detnet-dp-dt] An optional scheme that can su… Jiangyuanlong
- Re: [Detnet-dp-dt] FRER example.. maybe a way for… Jiangyuanlong
- Re: [Detnet-dp-dt] FRER example.. maybe a way for… Loa Andersson
- Re: [Detnet-dp-dt] FRER example.. maybe a way for… Jiangyuanlong
- Re: [Detnet-dp-dt] quick notes from call 2/14/15 Jiangyuanlong