Re: [ippm] [sfc] WGLC for https://datatracker.ietf.org/doc/draft-ietf-sfc-ioam-nsh/

Greg Mirsky <gregimirsky@gmail.com> Thu, 14 April 2022 13:11 UTC

Return-Path: <gregimirsky@gmail.com>
X-Original-To: ippm@ietfa.amsl.com
Delivered-To: ippm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C06C93A18FC; Thu, 14 Apr 2022 06:11:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.006
X-Spam-Level:
X-Spam-Status: No, score=-2.006 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, HTTPS_HTTP_MISMATCH=0.1, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, 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 scFSaPbnEOv4; Thu, 14 Apr 2022 06:11:37 -0700 (PDT)
Received: from mail-lj1-x236.google.com (mail-lj1-x236.google.com [IPv6:2a00:1450:4864:20::236]) (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 9D7D23A18F2; Thu, 14 Apr 2022 06:11:36 -0700 (PDT)
Received: by mail-lj1-x236.google.com with SMTP id m8so5954448ljc.7; Thu, 14 Apr 2022 06:11:36 -0700 (PDT)
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=ndM05SpE7R5lWYlOkUlDX9kAzvqLStA+K9O7RJ0NVe8=; b=QffXRRCliABIep5F+MY07/tFHx4jY+sN7wOIcYwINaQ5GcJjq5eIOrucHpvPhatqQJ wc3WkXgNnNIEKVVe9c0Mx0OyfTI9sByRCHtSWoB3OJGfKS0GkAP1Ruw3VNZ5UhxISNpl KBer0dREHy7IdEo5YR5jsta9vGn3XV+2r29csicMBySXMszl84KAS+pZzpY8mR0ppJNP J8hE40NHkACKSLyk2nPhVJPCVc2dA3fA0o15/h31uEzDGCU6PrWSVasUrVIlFWR4+Ffs MWeJ/7+vu5ZpRT4o4uoYvNGaRdlp4If3Ighq0ePHo05+DasmjvOu0Ykx5j2jt+5XFwDg Nd8Q==
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=ndM05SpE7R5lWYlOkUlDX9kAzvqLStA+K9O7RJ0NVe8=; b=AJuUh0jUbOoZ5VX7khVBQvITjz5CnVxLSl8KtNOTzxt4EXX2vYZkJxXSa1Wl6TRkWH QEHdt3mvWv5Z2IFDUWjIZHvQfH4QllUlJZXW4TaFzLKAsCiqEIdx4ejqhMwX4Q8ylsVq tu+b6JJWLwAlDP5gZ14r+JMDFvNcuydAMfbSXOqUnQi+JGHaCBpF8BF+hHM7RAUGj7P7 kEhHr/O6mToqGJEE9F9k+sPOfUR+ND6t7hcPJkAirkvzgFCiOVDtEa8nMIyJ0gI/Et5k iJN48AxrFdn5/QFDw/Z4ZIVkK99vnvtaQfyyPEDwArsX8S2JcCWTiet6KVzmLKxYa4fK Co6A==
X-Gm-Message-State: AOAM530Hqxf259cYIVtKWqPJ08oY01c0OZR83/K6YPg1vy5VHm+pJehb vHvBQN/MSjFak4pgtbc7SpAT5EO400eppPHtJFI=
X-Google-Smtp-Source: ABdhPJzjaOGQrcKB8l9gydfTLZr6FncBo7NCRQtlI3NGnJ4iTPjhDQS7Ezm4G0z7EHxdmqZB+QkUB9VRCwh0Ss0Tm98=
X-Received: by 2002:a2e:b94b:0:b0:249:6181:468a with SMTP id 11-20020a2eb94b000000b002496181468amr1587133ljs.113.1649941894390; Thu, 14 Apr 2022 06:11:34 -0700 (PDT)
MIME-Version: 1.0
References: <MN2PR13MB4206C91446BA5FBBDA69E233D2FF9@MN2PR13MB4206.namprd13.prod.outlook.com> <CA+RyBmVSrdCaO77P4=1vZ2LmxtR65OmspN_wozyGPNwtM5Uv3A@mail.gmail.com> <CAMFZu3PaLQrHcBULzsxbdnTJyr-bVDVs1WpnFwLuSkR7DbntuQ@mail.gmail.com> <CA+RyBmWeUiTsA7-CvpXSBViB00Y-tmAuSr-P=Vf3vB61zfn6bg@mail.gmail.com> <CAMFZu3P45x9Mt5-MUpGO1Puqz57DPcGE4aBsPNxczW-pw9n=AA@mail.gmail.com> <MN2PR13MB42066C22CA66B0E1F0FC3FFFD2269@MN2PR13MB4206.namprd13.prod.outlook.com> <CAMFZu3NO6J-MM_a7TZm+wTzxbKzY5t0OkW8QNLk0673Fkr16RQ@mail.gmail.com> <CA+RyBmVVWdvLZdANV_whtcwwMKVfVpM8VL7BYMM7NTnmooUpcQ@mail.gmail.com> <CAMFZu3PEmrarcsp4tXQsx4eKvai8+UvzKSFxfcakX4LUAcayJA@mail.gmail.com> <MN2PR13MB420615DA403388EA0144A9C1D22F9@MN2PR13MB4206.namprd13.prod.outlook.com> <CAMFZu3MUmuBEDEzdafw2UHEvsTE+7sQ=E1kik5TuQ=_NznFF9w@mail.gmail.com> <CA+RyBmW=ZT0EUmSYYfZJjcapBZ5-pg93um5t287LreONLOVnJQ@mail.gmail.com> <CAMFZu3NCCmj4u75taEzBiMmkMQ0YrmK5KsUToSOKfwX1yBxePA@mail.gmail.com> <26916_1649050778_624A849A_26916_245_1_aa5a0049026247d9980f4ebbc8c5ac0b@orange.com> <CY4PR11MB1672FCF27DA2A4822C6E1B40DAED9@CY4PR11MB1672.namprd11.prod.outlook.com> <11111_1649774342_62558F05_11111_493_4_a734de5265ca498bbabf9805a6eaf91d@orange.com> <CAMFZu3N03E-nWYJNik91e+X=gr3s2TVF03ZCM8i02ru4_Q82og@mail.gmail.com> <CA+RyBmWUZcUN2jnpUuyhTmkNpwvh=2prBZDGinWe2v-b3n8+MQ@mail.gmail.com> <CAMFZu3N5+GdFk13oWbi8F1qhgRNsKpSFwza61SG2oeMW9TvaLQ@mail.gmail.com> <525_1649935673_62580539_525_487_2_d0a4949b3d9c4424a0261012c7ce6188@orange.com>
In-Reply-To: <525_1649935673_62580539_525_487_2_d0a4949b3d9c4424a0261012c7ce6188@orange.com>
From: Greg Mirsky <gregimirsky@gmail.com>
Date: Thu, 14 Apr 2022 06:11:21 -0700
Message-ID: <CA+RyBmX3MdqVX5=hEsO+9SMbpXw+enwnm_qb4+-6smqbsTPPwg@mail.gmail.com>
To: Med Boucadair <mohamed.boucadair@orange.com>
Cc: Shwetha Bhandari <shwetha.bhandari@thoughtspot.com>, "Frank Brockners (fbrockne)" <fbrockne=40cisco.com@dmarc.ietf.org>, "sfc-chairs@ietf.org" <sfc-chairs@ietf.org>, "sfc@ietf.org" <sfc@ietf.org>, "ippm@ietf.org" <ippm@ietf.org>, James Guichard <james.n.guichard@futurewei.com>, Tal Mizrahi <tal.mizrahi.phd@gmail.com>, "draft-ietf-sfc-ioam-nsh@ietf.org" <draft-ietf-sfc-ioam-nsh@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000083e96e05dc9d082f"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ippm/9qOHywYaS-pFgxD4DtLefuxPicw>
Subject: Re: [ippm] [sfc] WGLC for https://datatracker.ietf.org/doc/draft-ietf-sfc-ioam-nsh/
X-BeenThere: ippm@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF IP Performance Metrics Working Group <ippm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ippm>, <mailto:ippm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ippm/>
List-Post: <mailto:ippm@ietf.org>
List-Help: <mailto:ippm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ippm>, <mailto:ippm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Apr 2022 13:11:42 -0000

Hi Shwetha,
thank you for the proposed resolution. I agree with Med, direct normative
reference to I-D.ietf-sfc-oam-packet seems like the logical conclusion of
our discussion of the use of the NSH O bit. Please note that we're
referring to I-D.ietf-sfc-oam-packet in the Active SFC OAM draft, e.g.,:

The O bit in NSH MUST be set, according to [I-D.ietf-sfc-oam-packet].


Regards,
Greg

On Thu, Apr 14, 2022 at 4:27 AM <mohamed.boucadair@orange.com> wrote:

> Hi Shwetha,
>
>
>
> I prefer we go for an explicit reference to I-D.ietf-sfc-oam-packet rather
> than “any update to RFC8300”. This is consistent with the usage in the
> other OAM draft.
>
>
>
> Thank you.
>
>
>
> Cheers,
>
> Med
>
>
>
> *De :* Shwetha Bhandari <shwetha.bhandari@thoughtspot.com>
> *Envoyé :* jeudi 14 avril 2022 12:06
> *À :* Greg Mirsky <gregimirsky@gmail.com>
> *Cc :* BOUCADAIR Mohamed INNOV/NET <mohamed.boucadair@orange.com>om>; Frank
> Brockners (fbrockne) <fbrockne=40cisco.com@dmarc.ietf.org>rg>;
> sfc-chairs@ietf.org; sfc@ietf.org; ippm@ietf.org; James Guichard <
> james.n.guichard@futurewei.com>gt;; Tal Mizrahi <tal.mizrahi.phd@gmail.com>om>;
> draft-ietf-sfc-ioam-nsh@ietf.org
> *Objet :* Re: [sfc] WGLC for
> https://datatracker.ietf.org/doc/draft-ietf-sfc-ioam-nsh/
>
>
>
> Hi Med, Greg,
>
>
>
> How about this text :
>
>
>
> “The O-bit MUST be handled following the rules in and any updates
> to [RFC8300] ."
>
>
>
> Given that I-D.ietf-sfc-oam-packet  will update RF8300 and there could be
> others in future?
>
>
>
> Thanks,
>
> Shwetha
>
>
>
> On Tue, Apr 12, 2022 at 9:24 PM Greg Mirsky <gregimirsky@gmail.com> wrote:
>
> Hi Shwetha,
>
> I believe that the text you've quoted is helpful. I would suggest changing
> references from [RFC8300] to [I-D.ietf-sfc-oam-packet] throughout that
> paragraph.
>
>
>
> Regards,
>
> Greg
>
>
>
> On Tue, Apr 12, 2022 at 7:56 AM Shwetha Bhandari <
> shwetha.bhandari@thoughtspot.com> wrote:
>
> Med,
>
>
>
> Thanks for the details: this is exactly what we had before the latest
> revision:
>
> *4.2 <https://urldefense.com/v3/__https:/datatracker.ietf.org/doc/html/draft-ietf-sfc-ioam-nsh-06*section-4.2__;Iw!!MZ3Fw45to5uY!NBsrzhHEf0Y_-Sindy74K4QDA6EWJjx35STSH-UxEi3eYIX0GVli9Sn1azrOPJVcI2qUzWfezK_1D2RpyFB_FOIpJPfzrvI$>.  IOAM and the use of the NSH O-bit*
>
>
>
>    [RFC8300] defines an "O bit" for OAM packets.  Per [RFC8300 <https://urldefense.com/v3/__https:/datatracker.ietf.org/doc/html/rfc8300__;!!MZ3Fw45to5uY!NBsrzhHEf0Y_-Sindy74K4QDA6EWJjx35STSH-UxEi3eYIX0GVli9Sn1azrOPJVcI2qUzWfezK_1D2RpyFB_FOIpEB5AbbE$>] the O
>
>    bit must be set for OAM packets and must not be set for non-OAM
>
>    packets.  Packets with IOAM data included MUST follow this
>
>    definition, i.e. the O bit MUST NOT be set for regular customer
>
>    traffic which also carries IOAM data and the O bit MUST be set for
>
>    OAM packets which carry only IOAM data without any regular data
>
>    payload.
>
>
>
> This was removed as per the discussion in this thread. Please check
> https://mailarchive.ietf.org/arch/msg/sfc/srMit5zE8UseNOhxknAw_dqvj6M/
> <https://urldefense.com/v3/__https:/mailarchive.ietf.org/arch/msg/sfc/srMit5zE8UseNOhxknAw_dqvj6M/__;!!MZ3Fw45to5uY!NBsrzhHEf0Y_-Sindy74K4QDA6EWJjx35STSH-UxEi3eYIX0GVli9Sn1azrOPJVcI2qUzWfezK_1D2RpyFB_FOIp-CeLfeA$>
>
> It looks like we are going in a loop here. This definition of SFC OAM
> packet to include the OAM data that comes in inner packets via the next
> protocol header chain is introduced in draft-ietf-sfc-oam-packet to update
> the RFC8300.
>
> Jim, What are you thoughts on this? Should we reintroduce the above text ?
>
> Thanks,
> Shwetha
>
>
>
> _________________________________________________________________________________________________________________________
>
> Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
> pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
> a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
> Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.
>
> This message and its attachments may contain confidential or privileged information that may be protected by law;
> they should not be distributed, used or copied without authorisation.
> If you have received this email in error, please notify the sender and delete this message and its attachments.
> As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
> Thank you.
>
>