Re: [Detnet-dp-dt] One more comment - Re: Draft update in github

Loa Andersson <loa@pi.nu> Fri, 10 March 2017 11:08 UTC

Return-Path: <loa@pi.nu>
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 A6CC9129884 for <detnet-dp-dt@ietfa.amsl.com>; Fri, 10 Mar 2017 03:08:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-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 8FLA5XY-x7-z for <detnet-dp-dt@ietfa.amsl.com>; Fri, 10 Mar 2017 03:08:35 -0800 (PST)
Received: from pipi.pi.nu (pipi.pi.nu [83.168.239.141]) (using TLSv1.1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 29AA4129874 for <detnet-dp-dt@ietf.org>; Fri, 10 Mar 2017 03:08:35 -0800 (PST)
Received: from [192.168.1.11] (unknown [119.95.38.221]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: loa@pi.nu) by pipi.pi.nu (Postfix) with ESMTPSA id 6EE6318014F3 for <detnet-dp-dt@ietf.org>; Fri, 10 Mar 2017 12:08:32 +0100 (CET)
To: detnet-dp-dt@ietf.org
References: <88BD4A49-3A2C-44DD-A090-E7A3AAC8BF61@broadcom.com> <7e524d11-b2ef-f447-6742-ae40100f39fc@pi.nu> <daca8182-ff32-f150-1430-baf0bc724f8b@pi.nu> <DE95293F-9A73-42EC-999F-DD555B2F7897@broadcom.com>
From: Loa Andersson <loa@pi.nu>
Message-ID: <6ad1b140-cb39-b5ee-1438-f650dcd48366@pi.nu>
Date: Fri, 10 Mar 2017 19:08:26 +0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <DE95293F-9A73-42EC-999F-DD555B2F7897@broadcom.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/detnet-dp-dt/yXk2tylIgiFLpzWw7jbA47FbJ7g>
Subject: Re: [Detnet-dp-dt] One more comment - Re: Draft update in github
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: Fri, 10 Mar 2017 11:08:37 -0000

Jouni,

OK - let us know when you upload a new version. The improvements
version by version so far has been great. Did you look at my other
qustions?

/Loa

On 2017-03-10 16:58, Jouni Korhonen wrote:
> Loa,
>
> Correct. I kind of failed to say that :)
>
> - Jouni
>
>
>> On 09 Mar 2017, at 22:36, Loa Andersson <loa@pi.nu> wrote:
>>
>> Jouni,
>>
>> You say:
>>
>>   Depending on the network topology the "overlay label" may be part of
>>   the label stack.  This "L-label" has actually nothing specific to do
>>   with DetNet but can be used to build overlay topologies over the
>>   provider network in a same way virtual private networks (VPN) are
>>   built.
>>
>> What you sday about overlay topoöogies is correct, butthere is one more
>> characteristic of the L-label it guarantee that the PW-label is
>> unchanged from DA-x-PE to DA-x-PE, a tunnel that does not
>> expose the PW-label other than to the DA-S-PE or the DA-T-PE is not
>> optional, it must be there.
>>
>> /Loa
>>
>>
>> On 2017-03-10 13:58, Loa Andersson wrote:
>>> Jouni,
>>>
>>> I was working on reviewing the previous version, I see that
>>> you captured most of (very close to sll<9 of the comments I had.
>>>
>>> Questions:
>>>
>>> 1. IETF is mostly doing "on the wire" specifications, what is in the
>>> box is mostly viewed as implementation specific. Against this background
>>> why do we need "local-ID", isn't that implementation specific?
>>>
>>> 2. There are two sentences "In the context of this document DA-T-PE is
>>> referred as T-PE." and "In the context of this document DA-S-PE is
>>> referred as S-PE." Wouldn't it be better to actually use the new
>>> abbreviations, DA-T-PE and DA-S-PE?
>>>
>>> 3. Then I wonder if you got what is optional in the label stack
>>> and what is not; what needs to be there is one single tunnel, we have
>>> called that L-labels (PW architecture call it PSN Tunnel) all the rest
>>> of the T-Label tunnels are  optional.
>>>
>>> I wrote it down like this:
>>>
>>>   +-------------------------------+
>>>   |                               |
>>>   |          DetNet Flow          |
>>>   |            Payload            |  n octets
>>>   |                               |
>>>   +-------------------------------+
>>>   |      DetNet Flow Id           |  4 octets
>>>   +-------------------------------+
>>>   |      DetNet Control Word      |  4 octets
>>>   +-------------------------------+
>>>   |          MS-PW Label          |  4 octets
>>>   +-------------------------------+
>>>   |            L-Label            |  4 octets
>>>   +-------------------------------+
>>>   |   (optional) MPLS T-Label(s)  |  n*4 octets (four octets per label)
>>>   +-------------------------------+
>>>
>>>
>>> DetNet Flow Payload - n octets
>>> DetNet Flow Id      - 4 octets, part of the encapsualtion header,
>>>                      i.e. not in the label stack
>>> DetNet Control Word - 4 octets, the 16 least significant but are a
>>>                      a sequence number.
>>> MS-PW Label         - 4 octets, this label is unchanged between two
>>>                      DA-x-PEs, and at PW set up it is decided if
>>>                      the Native Service Processing includes DetNet
>>>                      FRER or not, the MS-PW Label is swapped at
>>>                      DA-S-PE.
>>> L-Label             - carries the MS-PW Label unchanged from one
>>>                      DA-x-PE to the next
>>> T-Label(s)          - are optional, and strictly not part of the
>>>                      DetNet encapsulation.
>>>
>>> I don't want you to change but maybe capture a few bits and pieces
>>> from this.
>>>
>>> Then I have one ridiculous concern, the DA-S-PE does not need to
>>> interface a CE, and does not necessarily sit on a domain border, and is
>>> tthus not necessary a "real" PE. If we ant to keep calling it a PE
>>> (I think we should), we should have some words around this.
>>>
>>>
>>> /Loa
>>>
>>>
>>> On 2017-03-10 12:55, Jouni Korhonen wrote:
>>>> Folks,
>>>>
>>>> I did quite a bit of updates to the draft. All in GitHub. I’ll
>>>> continue writing over the weekend etc..
>>>>
>>>> - Jouni
>>>>
>>>>
>>>
>>
>> --
>>
>>
>> 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
>
> _______________________________________________
> 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