Re: [Detnet] Regarding the model for Active OAM packet

Loa Andersson <loa@pi.nu> Thu, 20 September 2018 07:21 UTC

Return-Path: <loa@pi.nu>
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 5503C130E52; Thu, 20 Sep 2018 00:21:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 CMgMZYjNx0fj; Thu, 20 Sep 2018 00:21:30 -0700 (PDT)
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 4D740130DD1; Thu, 20 Sep 2018 00:21:30 -0700 (PDT)
Received: from [192.168.1.20] (unknown [119.94.164.184]) (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 439C0180121E; Thu, 20 Sep 2018 09:21:24 +0200 (CEST)
To: Mach Chen <mach.chen@huawei.com>, Greg Mirsky <gregimirsky@gmail.com>
Cc: DetNet WG <detnet@ietf.org>, János Farkas <Janos.Farkas@ericsson.com>, "detnet-chairs@ietf.org" <detnet-chairs@ietf.org>
References: <F73A3CB31E8BE34FA1BBE3C8F0CB2AE29267092D@dggeml530-mbs.china.huawei.com> <CA+RyBmX29+Q9y3dXM-PqYm-Nu8KtjYZDs6a-fh_rW5hacSpyRg@mail.gmail.com> <F73A3CB31E8BE34FA1BBE3C8F0CB2AE292672CBB@dggeml530-mbs.china.huawei.com>
From: Loa Andersson <loa@pi.nu>
Message-ID: <d4e45e7d-1001-be64-9ff0-f9ea9a882b77@pi.nu>
Date: Thu, 20 Sep 2018 15:21:20 +0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1
MIME-Version: 1.0
In-Reply-To: <F73A3CB31E8BE34FA1BBE3C8F0CB2AE292672CBB@dggeml530-mbs.china.huawei.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/detnet/HRI_MeLYAPJHDV2w_4wVGFpvgxE>
Subject: Re: [Detnet] Regarding the model for Active OAM packet
X-BeenThere: detnet@ietf.org
X-Mailman-Version: 2.1.29
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, 20 Sep 2018 07:21:33 -0000

Mach,

If I understand you correctly this is for an LSP in an MPLS network,
can you help me understand why GAL does not enough. Given that there
might be some minor extensions to GAL because of replication and
elimination.

/Loa

On 2018-09-19 14:31, Mach Chen wrote:
> Hi Greg,
> 
> Indeed, there is no DetNet Associated Channel defined in 
> draft-ietf-detnet-dp-sol-mpls for now, I think there should be.  I also 
> assume that PW ACH will be used for DetNet OAM.
> 
> Assume that PW ACH will be used for DetNet OAM and the reserved filed of 
> the PW ACH will be used to carry sequence number for OAM packet. But 
>   for PREF, a tricky way is to treat the “Version”+ “Reserved” + 
> ”Channel type” as the Sequence number, the replication or elimination 
> nodes do not need to differentiate whether it is a d-CW or  a PW ACH . 
> This way, OAM can be supported without additional processing and states.
> 
>         0                   1                   2                   3
> 
>         0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
> 
>        +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> 
>        |0 0 0 1|Verion |    Reserved   |         Channel Type          |
> 
>        +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> 
> Regarding sequence number, there are two ways to generate the sequence 
> number IMHO:  1) generated by the edge node, but it may need to 
> configure the start number, or 2) copied from the application-flow (if 
> there is). If the WG agree with this, the model can be updated reflect 
> this.
> 
> Best regards,
> 
> Mach
> 
> *From:*Greg Mirsky [mailto:gregimirsky@gmail.com]
> *Sent:* Wednesday, September 19, 2018 11:29 AM
> *To:* Mach Chen <mach.chen@huawei.com>
> *Cc:* János Farkas <Janos.Farkas@ericsson.com>; DetNet WG 
> <detnet@ietf.org>; detnet-chairs@ietf.org
> *Subject:* Re: Regarding the model for Active OAM packet
> 
> Hi Mach,
> 
> thank you for your attention to my comment and the most expedient response.
> 
> I don't find the DetNet Associated Channel defined in 
> draft-ietf-detnet-dp-sol-mpls and thus I assumed that OAM packets that 
> follow the data packet encapsulation defined in that draft use PW ACH as 
> defined in section 5 RFC 4385: True, it includes 8 bits-long Reserved 
> field that may be defined as OAM Sequence Number but that had not been 
> discussed. One is certain, existing nodes do not check the Reserved 
> field. And without a field to hold the sequence number, PREF will not 
> handle the OAM packets. Another question, additional processing and 
> amount of state introduced in the fast path by the fact that OAM's 
> Sequence Number will have different length and location in d-CW 
> (differentiating cases by the first nibble).
> 
> Now, if we step back from DetnNet in MPLS data plane encapsulation, why 
> the control-word, as I understand, is configurable? I think that the 
> Sequence Number is not configurable, nor the first nibble. What do you 
> think?
> 
> Regards,
> 
> Greg
> 
> On Tue, Sep 18, 2018 at 7:48 PM Mach Chen <mach.chen@huawei.com 
> <mailto:mach.chen@huawei.com>> wrote:
> 
>     Hi Greg,
> 
>     The MPLS DetNet header is defined as below:
> 
>     grouping mpls-detnet-header {
>          description
>              "The MPLS DetNet encapsulation header information.";
>          leaf service-label {
>            type uint32;
>            mandatory true;
>            description
>              "The service label of the DetNet header.";
>          }
>          leaf control-word {
>            type uint32;
>            mandatory true;
>            description
>              "The control word of the DetNet header.";
>          }
>        }
> 
>     Although do not consider Active OAM when design the above
>     mpls-denet-header,  seems that it can cover Active OAM case as well.
>     No matter a normal DetNet packet or an Active OAM packet, there
>     should be a CW field, just as defined above.
> 
>     For normal DetNet packets, the CW is the d-CW as defined in the
>     draft-ietf-detnet-dp-sol-mpls.
> 
>     For OAM packets, the CW is the "DetNet Associated Channel".
> 
>     Best regards,
>     Mach
> 
> 
>     > -----Original Message-----
>     > From: detnet [mailto:detnet-bounces@ietf.org <mailto:detnet-bounces@ietf.org>] On Behalf
>     Of Greg Mirsky
>     > Sent: Wednesday, September 19, 2018 3:17 AM
>     > To: János Farkas <Janos.Farkas@ericsson.com <mailto:Janos.Farkas@ericsson.com>>
>     > Cc: DetNet WG <detnet@ietf.org <mailto:detnet@ietf.org>>; detnet-chairs@ietf.org
>     <mailto:detnet-chairs@ietf.org>
>     > Subject: Re: [Detnet] WG adoption poll draft-geng-detnet-conf-yang
>     > 
>     > Hi Janos, et. al,
>     > the mpls-detnet-header container is based on the solution described in
>     > draft-ietf-detnet-dp-sol-mpls. Analysis of active SFC OAM in the proposed
>     > MPLS data plane solution in draft-mirsky-detnet-oam points to the potential
>     > problem as result the fact that OAM packet doesn't include d-CW. I believe
>     > that this question should be discussed and, if we agree on the problem
>     > statement, properly resolved. Until then, I do not support the adoption of
>     > the model that may not be capable to support active OAM.
>     > 
>     > Regards,
>     > Greg
>     > On Tue, Sep 18, 2018 at 12:03 PM Janos Farkas <Janos.Farkas@ericsson.com <mailto:Janos.Farkas@ericsson.com>>
>     > wrote:
>     > >
>     > > Dear all,
>     > >
>     > > This is start of a two week poll on making
>     > > draft-geng-detnet-conf-yang-04 a working group document. Please send
>     > > email to the list indicating "yes/support" or "no/do not support".  If
>     > > indicating no, please state your reservations with the document.  If
>     > > yes, please also feel free to provide comments you'd like to see
>     > > addressed once the document is a WG document.
>     > >
>     > > The poll ends Oct 3.
>     > >
>     > > Thanks,
>     > > János and Lou
>     > >
>     > > _______________________________________________
>     > > detnet mailing list
>     > > detnet@ietf.org <mailto:detnet@ietf.org>
>     > > https://www.ietf.org/mailman/listinfo/detnet
>     > 
>     > _______________________________________________
>     > detnet mailing list
>     > detnet@ietf.org <mailto:detnet@ietf.org>
>     > https://www.ietf.org/mailman/listinfo/detnet
> 
> 
> 
> _______________________________________________
> detnet mailing list
> detnet@ietf.org
> https://www.ietf.org/mailman/listinfo/detnet
> 

-- 


Loa Andersson                        email: loa@pi.nu
Senior MPLS Expert
Bronze Dragon Consulting             phone: +46 739 81 21 64