Re: [Detnet] The new d-ACH format
Greg Mirsky <gregimirsky@gmail.com> Wed, 17 November 2021 23:54 UTC
Return-Path: <gregimirsky@gmail.com>
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 CF5273A0115; Wed, 17 Nov 2021 15:54:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 qb-n18SvKfIz; Wed, 17 Nov 2021 15:54:29 -0800 (PST)
Received: from mail-ed1-x529.google.com (mail-ed1-x529.google.com [IPv6:2a00:1450:4864:20::529]) (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 EE38A3A0101; Wed, 17 Nov 2021 15:54:28 -0800 (PST)
Received: by mail-ed1-x529.google.com with SMTP id r11so18499065edd.9; Wed, 17 Nov 2021 15:54:28 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=xBdkClCA2vVzM9ymAIRo4qKHfAHBH7xmOe7n9mc6Q0U=; b=E9gMIcUEmfH3G7LCS+MXWuY6s2ptLL96Nw8wtf7nIHAcyWHW87Cfg/YBWo1OsFainV jmlOx0dVLZytTkkbCaNFUvtcVrKXkcnVleIjegH3LD+lJOFqRWIo/Q9wNfpbQ3qia6/4 gE+1a1vUYtLFG4/sSWtdW9vp6U1+bPb0jo+ccEfbcOn0XELvhpT4JxMHpjeukyyDkqEZ JFQqEFVvHaf2BelTRoSoLORHU+hZ53vmyt7mRSDh+QFyiqSZ7bSZF4+dLboFQMjR1aGZ fCXzSpDUHK22vpXdwdUiE/b8SfYtP+SoxR2pLukAvvtJqM5yPtyA6+jWV0N+K7dMjivk aqDA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=xBdkClCA2vVzM9ymAIRo4qKHfAHBH7xmOe7n9mc6Q0U=; b=KiZ8S4RKyk++4f1bDDbjWvaQqT05o19zhdNIbMcSvij4kGpS6QQn4jJKLs37+nOFIc Fr7aw3wkJM/hR++tBjGrnbHcwgk6zwYbn41mxooGi1N+x/Z+m/6t+ltx/5rPYhuF3OPz e5n1WCFXMwT+fvERfv6UkOTQAiaSYwZn9bU4cdoxI8biCGB0U1gDxSsM/2UCKAc3HcOW xT/vSPj74Nuj7mHIOtlZNyEq+QkEXHhOKayl0qjusDDykKB5VwBDBqLXlMzKcIz83c2v K+My8p2+D8d9pjNqHrzbMpxQ94rO3YRR8rXvKNEq12oOXi1mRqJgAUzKBEV6FFHtt1mm X/8A==
X-Gm-Message-State: AOAM532kNELLa9agJ2NrEQHiivy4ZsqGlgKCmD59yCp/7j6KVgBFum9H mmpPtY8enFg1nXW/EZqkpf5OmwpbEa1SiNUWs1wiaNUz
X-Google-Smtp-Source: ABdhPJxXQBykdRSbsUBCNHeoxKJkeus8KyU/Uu4lG2YT5aXqirMWIzQY3BUNw32VXMuyGpmecKCsSiTxhX8kzklf7ro=
X-Received: by 2002:a17:906:399a:: with SMTP id h26mr27050866eje.131.1637193265671; Wed, 17 Nov 2021 15:54:25 -0800 (PST)
MIME-Version: 1.0
References: <CA+RyBmWQC9cDZOS7sowcU5ZJsYmJpeUjsaCeCbuxhtD2jS4nGg@mail.gmail.com> <CA+RyBmXmZriCtWZGRdYFBx7yK_NnSvOmDVbE5wo0FT0FryLcVQ@mail.gmail.com> <ff2311755057431e9f4ddd1fb65db660@huawei.com>
In-Reply-To: <ff2311755057431e9f4ddd1fb65db660@huawei.com>
From: Greg Mirsky <gregimirsky@gmail.com>
Date: Wed, 17 Nov 2021 15:54:14 -0800
Message-ID: <CA+RyBmWyA=1LYfATt49F2PcdYUPj6aepvMqeL3EaHBcQcZ9iKw@mail.gmail.com>
To: "Yangfan(Fan,IP Standards)" <shirley.yangfan@huawei.com>
Cc: DetNet WG <detnet@ietf.org>, DetNet Chairs <detnet-chairs@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000076f9a05d104c358"
Archived-At: <https://mailarchive.ietf.org/arch/msg/detnet/KEQqOqHoCk0HmjSkmuVGFsvLmRY>
Subject: Re: [Detnet] The new d-ACH format
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: Wed, 17 Nov 2021 23:54:34 -0000
Hi Fan, thank you for your comments and questions. Please find my notes in-lined below tagged GIM>>, Regards, Greg On Wed, Nov 17, 2021 at 2:26 AM Yangfan(Fan,IP Standards) < shirley.yangfan@huawei.com> wrote: > Hi Greg, > > > > Regarding the new d-ACH format, I have a few questions to share, hopefully > trigger more discussions. > > 1) I feel we need more specifications of Node ID. Using 20 bits to > indicate a Node in MPLS data plane, can I deduce it is an MPLS label? In > any MPLS data planes except SR-MPLS, there is no definition to use a label > to identify a node. If we want a format generic for all MPLS data planes, I > wonder whether node id is a good indicator? Whether 20 bits is enough? > GIM>> I agree that the DetNet WG will have more discussions on the definition of the Node ID field. I am looking forward to your participation in these discussions. > 2) I also noticed there is a session ID, but is only 4 bit length, > which I believe is way too short. Moreover, whether originator node ID and > session ID are duplicated here to identify an OAM session. To dig deeper, > DetNet OAM should be stateless or stateful? > GIM>> Session ID field is only a tentative name. Would it help if we mark it Reserved? > 3) if we plans to take advantages of CFM y.1731 mechanisms, level > and flags are necessary but the length also needs further considerations. > GIM>> It is not clear if DetNet OAM could benefit from re-using some principles of Y.1731/CFM as the latter doesn't provide special support for the Service sub-layer. > > > Looking forward to further discussions. > > > > Regards, > > Fan > > > > > > > > > > *From:* detnet [mailto:detnet-bounces@ietf.org] *On Behalf Of *Greg Mirsky > *Sent:* Wednesday, November 17, 2021 4:55 AM > *To:* DetNet WG <detnet@ietf.org> > *Cc:* DetNet Chairs <detnet-chairs@ietf.org> > *Subject:* Re: [Detnet] The new d-ACH format > > > > Dear All, > > I hope you've recovered from the IETF-112 (timing on the West Coast was > brutal). > > Please share your thoughts, comments, and questions about the proposed new > format of d-ACH and whether you support including it and updating > draft-ietf-detnet-mpls-oam. > > > > Regards, > > Greg > > > > On Wed, Nov 10, 2021 at 5:14 AM Greg Mirsky <gregimirsky@gmail.com> wrote: > > Dear All, > > Bala'zs has presented the new d-ACH (DetNet Associated Channel Header) > format at the DetNet WG meeting. Earlier this week, the new d-ACH format > was presented at joint PALS, MPLS, and DetNet meeting and received several > positive comments. At the DetNet WG meeting, it was proposed to integrate > the technical part, the new format of d-ACH > <https://datatracker.ietf.org/doc/html/draft-varga-detnet-service-sub-layer-oam-01#page-6> into > the draft-ietf-detnet-mpls-oam > <https://datatracker.ietf.org/doc/draft-ietf-detnet-mpls-oam/>. > > Please, respond with the indication of your support or no support for the > proposed update of the WG document. > > > > Regards, > > Greg (as the Editor of draft-ietf-detnet-mpls-oam) > >
- [Detnet] The new d-ACH format Greg Mirsky
- Re: [Detnet] The new d-ACH format Greg Mirsky
- Re: [Detnet] The new d-ACH format Yangfan(Fan,IP Standards)
- Re: [Detnet] The new d-ACH format Greg Mirsky
- Re: [Detnet] The new d-ACH format Yangfan(Fan,IP Standards)
- Re: [Detnet] The new d-ACH format Greg Mirsky
- Re: [Detnet] The new d-ACH format Gyan Mishra