Re: [Detnet-dp-dt] a quick look at the replication/discarding case for detnet flows

Jouni Korhonen <jouni.korhonen@broadcom.com> Mon, 23 January 2017 01:40 UTC

Return-Path: <jouni.korhonen@broadcom.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 B659A129556 for <detnet-dp-dt@ietfa.amsl.com>; Sun, 22 Jan 2017 17:40:20 -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 ygaNvOzNgFoD for <detnet-dp-dt@ietfa.amsl.com>; Sun, 22 Jan 2017 17:40:18 -0800 (PST)
Received: from mail-pf0-x234.google.com (mail-pf0-x234.google.com [IPv6:2607:f8b0:400e:c00::234]) (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 D534312954F for <detnet-dp-dt@ietf.org>; Sun, 22 Jan 2017 17:40:18 -0800 (PST)
Received: by mail-pf0-x234.google.com with SMTP id 189so36709661pfu.3 for <detnet-dp-dt@ietf.org>; Sun, 22 Jan 2017 17:40:18 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=broadcom.com; s=google; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=K6Gr5AI2iI0wlgZiZiNT6IG87Ko8g6+Kkw0mpocRV8I=; b=D3Ra0AMFFfsf5M9Ou0IGc+fli3xYkZqQKJB16MtR7/256R3pWyxE756u/8ClszRzw0 lpMssCUYNf+6betOg3F7rP8B2sDP0BPwNqSZ4tFEh5DcbSpckt2fTS+07FFfLzbFnjHg NfkX/Mi53yuepKFs+OWwx6hlfYEXU0HTPBZb0=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=K6Gr5AI2iI0wlgZiZiNT6IG87Ko8g6+Kkw0mpocRV8I=; b=b1yIaKVcPPg8Y5mfKCfsfLuUenBQIWs44y+uhXXOA8QQI7mwBw5UQUAtbz3pQl5vJc utKj4RE9V3B7OWJZZRcVbiYMtw/RLxo1pP7nukuce9esVZRZtd99bpNRbTUuqNebuZcp 9dfNVapTW82zfR5mp91kr1KXC5ZVHObXC72MEQLOf0Te6d3E4Azaqxho5tKVl/+lQCX3 s0bNX0I1HyYJXe+Qtn+ContTBcYxZiKX1skRdhF6kkBDkXVFzX7zUwAc+mnmZM/oDuoK 42zjigX4zjzFisgXc4KlgnzwKv8prf65pa982+awdyJ80oH63vArd1t2GfVzjXIkhEcU vSkA==
X-Gm-Message-State: AIkVDXLvRXsnz/3Bd0E9nQ1fE3RMy9QogOsGtAplk3sXDA6Nk2wrIiFPP/niFBWZTUxfpMYZ
X-Received: by 10.98.159.141 with SMTP id v13mr29544374pfk.50.1485135618078; Sun, 22 Jan 2017 17:40:18 -0800 (PST)
Received: from ?IPv6:2601:647:4200:e520:8583:f294:1c72:5b68? ([2601:647:4200:e520:8583:f294:1c72:5b68]) by smtp.gmail.com with ESMTPSA id u14sm32039828pfg.18.2017.01.22.17.40.16 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 22 Jan 2017 17:40:17 -0800 (PST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
From: Jouni Korhonen <jouni.korhonen@broadcom.com>
In-Reply-To: <36b41863-e0b3-a2f6-fd97-01499e9581b2@pi.nu>
Date: Sun, 22 Jan 2017 17:40:18 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <862A774A-8B3A-419D-9ECD-7F891A785307@broadcom.com>
References: <6ff03919-9584-0a48-da2e-7ded7d2aacbb@pi.nu> <5116AE7C-E0F3-473A-9FE7-B17A7FF82DA6@broadcom.com> <1470015091.61923.1485012103902@itx66.prod.google.com> <-4407507652711782750@unknownmsgid> <36b41863-e0b3-a2f6-fd97-01499e9581b2@pi.nu>
To: Loa Andersson <loa@pi.nu>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/detnet-dp-dt/OpJPJED7DbRaWUgHIQl5Uvy0SuU>
Cc: "detnet-dp-dt@ietf.org" <detnet-dp-dt@ietf.org>
Subject: Re: [Detnet-dp-dt] a quick look at the replication/discarding case for detnet flows
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: Mon, 23 Jan 2017 01:40:20 -0000

Loa,

It is just that the solution has to work even if php does not take place.

- JOuni


--
Jouni Korhonen, Broadcom Ltd.
M: +1-408-391-7160

> On Jan 21, 2017, at 9:26 PM, Loa Andersson <loa@pi.nu> wrote:
> 
> Jouni,
> 
> Depends on what you mean by " not always necessarily done", php is done by default but can be turned off. I see no reason to turn it of, at
> least not if we are concerned for the depth of the label stack.
> 
> /Loa
> 
> On 2017-01-22 00:27, Jouni Korhonen wrote:
>> Loa,
>> 
>> Ok. Thanks.  I think we also need to make clear that php is not always
>> necessarily done.
>> 
>> Jouni
>> 
>> Sent from a smart phone.. Mind the typos..
>> 
>>> On Jan 20, 2017, at 21:25, Loa Andersson <loa@pi.nu> wrote:
>>> 
>>> Jouni,
>>> 
>>> 
>>>> On 2017-01-21 10:47, Jouni Korhonen wrote:
>>>> Loa,
>>>> 
>>>> Thanks for the slides. The slide 9 is exactly what I was after with my e2e PW labels. Now the question: “I don’t know if there is currently enough capabilities in LDP to merge, unless we merge all traffic with the same FEC on the same outgoing outer label.” I cannot claim expertise in LDP
>>> 
>>> If you have the same forwarding class and destination (part of the FEC
>>> defintion) LDP will merge. This mean that all detnet traffic from one
>>> node will arrive at D on the same (transport) LSP. I think this is fine
>>> since the label for that LDP is php'ed.
>>> to be able to have any kind of educated view here. So if we are not
>>> going to be able to merge we would “waste” additional transport label
>>> between C->D?
>>> 
>>> Yes but that is a label that will be unique for a link, we are not
>>> running into problems until we start trying to use domaion wide unique
>>> labels.
>>> 
>>> Duplicated would have been eliminated, thus there is no bandwidth impact.
>>> 
>>> Correct!
>>> 
>>> I do not think that would be an issue. It is no optimal but works.
>>> 
>>> Well - I guess we could find some minor optimizations, but this wuth
>>> merging and php this is close to optimal.
>>> 
>>> /Loa
>>>> 
>>>> - Jouni
>>>> 
>>>> 
>>>> --
>>>> Jouni Korhonen, Broadcom Ltd.
>>>> M: +1-408-391-7160
>>>> 
>>>>> On Jan 13, 2017, at 8:28 PM, Loa Andersson <loa@pi.nu> wrote:
>>>>> 
>>>>> Folks,
>>>>> 
>>>>> I took a quick look at the replication / discarding case we talked about at the meeting this week.
>>>>> 
>>>>> Please remember that so far this is not a proposal, just a demonstration
>>>>> that there is at least one way of doing it.
>>>>> 
>>>>> What is there can bee revised, improved, changed or discarded if we
>>>>> find something better. Take a look a send comments.
>>>>> 
>>>>> /loa
>>>>> 
>>>>> Warning: I have a grave case of dyslexia, so any odd or inventive
>>>>> spelling is pure accident.
>>>>> --
>>>>> 
>>>>> 
>>>>> Loa Andersson                        email: loa@mail01.huawei.com
>>>>> Senior MPLS Expert                          loa@pi.nu
>>>>> Huawei Technologies (consultant)     phone: +46 739 81 21 64
>>>>> <detnet-replication.pptx>_______________________________________________
>>>>> Detnet-dp-dt mailing list
>>>>> Detnet-dp-dt@ietf.org
>>>>> https://www.ietf.org/mailman/listinfo/detnet-dp-dt
>>>> 
>>> 
>>> --
>>> 
>>> 
>>> Loa Andersson                        email: loa@mail01.huawei.com
>>> Senior MPLS Expert                          loa@pi.nu
>>> Huawei Technologies (consultant)     phone: +46 739 81 21 64
>> 
>> _______________________________________________
>> Detnet-dp-dt mailing list
>> Detnet-dp-dt@ietf.org
>> https://www.ietf.org/mailman/listinfo/detnet-dp-dt
>> 
> 
> -- 
> 
> 
> Loa Andersson                        email: loa@mail01.huawei.com
> Senior MPLS Expert                          loa@pi.nu
> Huawei Technologies (consultant)     phone: +46 739 81 21 64