From nobody Fri Aug 6 07:01:03 2021 Return-Path: X-Original-To: mpls@ietfa.amsl.com Delivered-To: mpls@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 75CA33A2E3A; Fri, 6 Aug 2021 07:01:00 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.097 X-Spam-Level: X-Spam-Status: No, score=-1.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, FREEMAIL_REPLY=1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 dl8mtuOFD-Sx; Fri, 6 Aug 2021 07:00:56 -0700 (PDT) Received: from mail-lf1-x132.google.com (mail-lf1-x132.google.com [IPv6:2a00:1450:4864:20::132]) (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 198C03A2E48; Fri, 6 Aug 2021 07:00:55 -0700 (PDT) Received: by mail-lf1-x132.google.com with SMTP id b6so1784726lff.10; Fri, 06 Aug 2021 07:00:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=guSfqIctlIIK0Fr6GtKwsp75odPVB3wtZy/N0ywhvaE=; b=tNaoWzH06mvWFmTu06y3/5gB7ZO+KZklTab0rectskfO3IBmd8EKEBJ421P6cxeklX /NN7Igyo6XqH3CAnq3APtcr2cyb+uhdO+JWBt/YCiXVCFoEMtb6Zd4unMdHqJ/balBxi YW7mDq5QmvEaEZfM1lVwroPqBMhEu11dRp2mDOYmYm/KaxEIAvLM48b7/kr89/jVKs2i f/AJ4rtGMvdiXh+DEbq4YYAOpG98EZoM6ynaj3sV7iDvR3xVHDJwRNUQX4BCM8pGpxYe iXKSzj7BZojJoxVmQYhe4Ye6sMdJdfP/UVXyhz1nrrNHkbJhbw+4NMvSxiQ5rRFFuhsr A0hg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=guSfqIctlIIK0Fr6GtKwsp75odPVB3wtZy/N0ywhvaE=; b=gmAU/yT+h99zAsgRc9RObkcL8otAxsqO1/W/R9N9ABBanL8oi9GJoWO685AZSvRhpI 0+Erzv/5QrpUP0O5xhKNdLJetWLVIijiWCvXp3rJLR4A9IhMdAB8hK0okxjckmyatRW8 aGnNDEwSeUePYKv+trgxsMsHAKuRVz4NzjWcX3l/B7Y0A2vkfgsEZHaI4mcapXjdYGPf QtsATnQq+c2/SwGsB5XamBmBOVkQ5aXgA7Oa4hOZfK1UiQ6BPVwhhxIDW4xoChH8CLPR y9zAy33ZAuRC1VhaiFKOObZEQJ9/xf23bJ6tcxQawwNWNVNRZoq84hr8TzvDYZv/nuWW JvSw== X-Gm-Message-State: AOAM532aMZYOEGOk1TmOpVpc0oOpM2GN3G3Dt8Hb0GrgLnPSxAH7JMS1 MvzS2kAneY74Q2TUnU7h80EfccS9oqZSTgXHnA== X-Google-Smtp-Source: ABdhPJzcz/2V97XdihLV17xpKePBsdMpG2NDu4LiVwT2gOCIyWjL7ncQKwEaK8Ep0T7nfrkRHskeCqwBRLEyKLD8z1s= X-Received: by 2002:a05:6512:3f24:: with SMTP id y36mr7861293lfa.611.1628258451447; Fri, 06 Aug 2021 07:00:51 -0700 (PDT) MIME-Version: 1.0 References: <1cfaeafc-7d2c-7e04-c6e2-767feb6e8364@pi.nu> In-Reply-To: <1cfaeafc-7d2c-7e04-c6e2-767feb6e8364@pi.nu> From: Rakesh Gandhi Date: Fri, 6 Aug 2021 10:00:40 -0400 Message-ID: To: Loa Andersson Cc: "mpls@ietf.org" , "pals-chairs@ietf.org" , "mpls-chairs@ietf.org" , DetNet Chairs Content-Type: multipart/alternative; boundary="00000000000099e18f05c8e4768c" Archived-At: Subject: Re: [mpls] Review and Consensus call on text from the MPLS Open DT on in-stack indicators X-BeenThere: mpls@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Multi-Protocol Label Switching WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Aug 2021 14:01:01 -0000 --00000000000099e18f05c8e4768c Content-Type: text/plain; charset="UTF-8" Hi WG, One comment on the following text with : - We have a standardized associated channel, the GAL/GACH. We are not going to change the associated channel in anyway that breaks existing implementations. The ACH is found immediately after the label carrying the Bottom of Stack (BoS) bit. Currently, there is no defined method to carry multiple ACHs in the same MPLS packet. *GAL/GACH will only be an OAM or instrumentation tool and will not be used to carry meta-data with user-traffic. * The last sentence needs some clarification. The packet with GAL is punted out of the fast path in forwarding, so user-traffic does not carry it, so it makes sense. However, packets could carry GACH without GAL. The user-traffic could also carry a GACH without GAL if use-case makes sense. I am not sure we are ready to add this restriction just yet. Thanks, Rakesh On Thu, Aug 5, 2021 at 10:52 AM Loa Andersson wrote: > Working Group, MPLS Open DT, > > The week before IETF 111 the Open DT met and agreed upon a text on > "indicators". The terminology we use is that somewhere in the label > stack there is an indicator tell the processing node that a specific > packet needs a certain set of Forwarding Actions, for example some iOAM > action might be required. To support the forwarding action there is > often ancillary data with the packet. > > The text the DT produced is about the indicators, a companion text on > ancillary data will follow. > > The text was discussed in the Joint meeting and reported to the MPLS > working group at IETF 111. The Open DT itself can only propose, the text > is therefore now sent out to the working group for review and consensus > call. > > The proposed text is found at: > https://trac.ietf.org/trac/mpls/wiki/2021-07-22-agenda > > Please review the proposed text and comment on the MPLS wg mailing list > (mpls@ietf.org). > > We plan to keep the consensus call open until 2021-08-20. > > /Loa > Open DT Co-ordinator / MPLS wg co-chair > > > -- > > Loa Andersson email: loa@pi.nu > Senior MPLS Expert loa.pi.nu@gmail.com > Bronze Dragon Consulting phone: +46 739 81 21 64 > > _______________________________________________ > mpls mailing list > mpls@ietf.org > https://www.ietf.org/mailman/listinfo/mpls > --00000000000099e18f05c8e4768c Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi WG,

One comment on the fo= llowing text with <RG>:
  • We have a standardized = associated channel, the GAL/GACH. We are not going to change the associated channel in anyway that breaks existing implementations. The ACH is found immediately after the label carrying the Bottom of Stack (BoS) bit. Currently, there is no defined method to carry multiple ACHs in the same MPLS packet. GAL/GACH will only be an OAM or instrumentation tool and will not be use= d to carry meta-data with user-traffic.
<RG> The last sentence needs some clarification. T= he packet with GAL is punted out of the fast path in forwarding, so user-tr= affic does not carry it, so it makes sense. However, packets could carry GA= CH without GAL. The user-traffic could also carry a GACH without GAL if use= -case makes sense. I am not sure we are ready to add this restriction just = yet.

Thanks,
Rakesh

=




On Thu, A= ug 5, 2021 at 10:52 AM Loa Andersson <loa@p= i.nu> wrote:
Working Group, MPLS Open DT,

The week before IETF 111 the Open DT met and agreed upon a text on
"indicators". The terminology we use is that somewhere in the lab= el
stack there is an indicator tell the processing node that a specific
packet needs a certain set of Forwarding Actions, for example some iOAM action might be required. To support the forwarding action there is
often ancillary data with the packet.

The text the DT produced is about the indicators, a companion text on
ancillary data will follow.

The text was discussed in the Joint meeting and reported to the MPLS
working group at IETF 111. The Open DT itself can only propose, the text is therefore now sent out to the working group for review and consensus call.

The proposed text is found at:
https://trac.ietf.org/trac/mpls/wiki/2021-07-2= 2-agenda

Please review the proposed text and comment on the MPLS wg mailing list (mpls@ietf.org).

We plan to keep the consensus call open until 2021-08-20.

/Loa
Open DT Co-ordinator / MPLS wg co-chair


--

Loa Andersson=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0= =C2=A0 =C2=A0 =C2=A0 email: loa@pi.nu
Senior MPLS Expert=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 loa.pi.nu@gmail.com
Bronze Dragon Consulting=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0pho= ne: +46 739 81 21 64

_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls
--00000000000099e18f05c8e4768c--