Re: [mpls] Extended Working Gorup Last Call and IPR Poll on draft-ietf-mpls-spring-inter-domain-oam-06

Dhruv Dhody <dhruv.ietf@gmail.com> Fri, 26 January 2024 07:26 UTC

Return-Path: <dhruv.ietf@gmail.com>
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 0FC7EC14F73E for <mpls@ietfa.amsl.com>; Thu, 25 Jan 2024 23:26:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.005
X-Spam-Level:
X-Spam-Status: No, score=-2.005 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_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=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 ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kSS-HI9bwvO8 for <mpls@ietfa.amsl.com>; Thu, 25 Jan 2024 23:26:17 -0800 (PST)
Received: from mail-oi1-x233.google.com (mail-oi1-x233.google.com [IPv6:2607:f8b0:4864:20::233]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F3718C14F74A for <mpls@ietf.org>; Thu, 25 Jan 2024 23:26:16 -0800 (PST)
Received: by mail-oi1-x233.google.com with SMTP id 5614622812f47-3bbbc6e51d0so47302b6e.3 for <mpls@ietf.org>; Thu, 25 Jan 2024 23:26:16 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1706253976; x=1706858776; darn=ietf.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=oeyHPxwSHrbBNvHxJsyLgmoZUtqhPb1oMENeTtKWryA=; b=k7Tyhm1hpYHerBS4I1lfcg4o18oQ35owDa7CFUeVGJtUQy2I+guxpFgXH3rY1HJRkP WUvAla7JS8N8olG6L0fDDZnNQuq36gjSmFR+lOr6HtruRF1+lzJQacD88LUzX6BS421S ffWCAkvy8Nki8hVx3ZYavaKP1vHn3Qg3jvKfNVqP1nYLm+3NQGxY5fLshsiyBDG7tFAq 9m8pWvwvGOedS6/KdbqKJbCpCWY/bdE9IyJVBpHNwgibARVshWS54glJSvgS++ywD5Ih +MFN0w70yYi4FYUKgEe7rVrX8t6AP5yTgRbd5vcBVBWnzdvAOAPn69TcGGiRaZwJbuUr vCzg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1706253976; x=1706858776; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=oeyHPxwSHrbBNvHxJsyLgmoZUtqhPb1oMENeTtKWryA=; b=COF6kBeJEaJC0C09hNCNgAOUF7975pWYeZduID0zqjC+vUUALKAuTPwa+3m7Z3vxLp QciRdKSyU8en1dqXwqF4DxwuTi9GdKe474CqLgF9B1Mz8Uj4bm0hSVHE/JBAjMT3k6nZ qTfJmeBetoBaiiOnO3qcuaMeSM4qCRCFdqUJD1zjOffbm0dcU+IHX08yziHLQ7BtrjBD SGMO4BKJEH/PxXAihkOp8zv8jiq5x0ixpSknAudNAWEr84g1icuFQzFbbmlE6MPKWmxo kEwyvgE/asZSTXbyJ2J1xO9XQA03ScamC7bWw/+dt0hFYFMuKuKMPGMgkasZK6vjs9oe RiEA==
X-Gm-Message-State: AOJu0YzLiT5tk01N/Iu6hHam55wAeql3HVX8D8NAH/54akJ2yK/WRJVi 261fieaVcbvSPkiZTNs/K/GFe78GD+5IkUpI7LHWUjc1O8xGR0SccAJjGCnMIclnPcdmZZ9svCT 3JxOMgHprn8X4a9MkFPyYKfMgtZH2YVJVI+Y=
X-Google-Smtp-Source: AGHT+IF+luOui3Y7IEnuGggfhGd3s7HL2xDZ4cbvnZq2f/xqOXBjHfrY1WO1/N5SIUaUQJsgCzqTyIjaHc5QnI10KfM=
X-Received: by 2002:a05:6808:23d0:b0:3bd:e427:cf3e with SMTP id bq16-20020a05680823d000b003bde427cf3emr553329oib.9.1706253975652; Thu, 25 Jan 2024 23:26:15 -0800 (PST)
MIME-Version: 1.0
References: <02a101da31ed$ef5164f0$cdf42ed0$@olddog.co.uk> <02b401da31f3$50400dc0$f0c02940$@olddog.co.uk> <052d01da432d$3a6de1c0$af49a540$@olddog.co.uk> <CAB75xn4PByHAvth-yU2-5rWQk1u+6H_1eoPrZkagLg-xJxXu9Q@mail.gmail.com> <CO1PR05MB83140716D2A23A934942D943D57A2@CO1PR05MB8314.namprd05.prod.outlook.com>
In-Reply-To: <CO1PR05MB83140716D2A23A934942D943D57A2@CO1PR05MB8314.namprd05.prod.outlook.com>
From: Dhruv Dhody <dhruv.ietf@gmail.com>
Date: Fri, 26 Jan 2024 12:55:39 +0530
Message-ID: <CAB75xn71Atne2o-rLQ+6aA3o2Asw+5aw3yL-sfR9iKq+XRXhwA@mail.gmail.com>
To: Shraddha Hegde <shraddha@juniper.net>
Cc: "adrian@olddog.co.uk" <adrian@olddog.co.uk>, "mpls@ietf.org" <mpls@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000001d8e74060fd43661"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mpls/M2QthJBq2dq8g6-Xg9HeUQyYxxc>
Subject: Re: [mpls] Extended Working Gorup Last Call and IPR Poll on draft-ietf-mpls-spring-inter-domain-oam-06
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mpls/>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Jan 2024 07:26:21 -0000

Hi Shraddha,

Snipping to open points...

>
> * You should add a reference to how EPE SIDs are handled, as your examples
> use them. Any issue adding text and reference to
> https://datatracker.ietf.org/doc/draft-ietf-mpls-sr-epe-oam/
> <https://urldefense.com/v3/__https:/datatracker.ietf.org/doc/draft-ietf-mpls-sr-epe-oam/__;!!NEt6yMaO-gk!DwN3BBepkygqgUdOp3H4S-t2LoMtwUuEzFn_V_TL4Yk7UG4FwVzOPTiUEuGNFjHzcVpjgrmec-QpkHhVnw0y$>
> ?
>
> <SH> https://datatracker.ietf.org/doc/draft-ietf-mpls-sr-epe-oam is for
> defining FEC for verifying the EPE-SIDs themselves. In this draft EPE-SIDs
> are being used to construct reverse paths. The two topics are quite
> independent and I don’t see the need to reference the epe-oam draft and
> create unnecessary reference to another
>
> WG document.
>
>
>
Dhruv: You are correct. But then what would be the best reference for EPE
SIDs? Note that RFC 9087 uses different terms. In the example what you call
EPE SID should it be called PeerAdj SID? Or am I missing something....



>
> * Suggest to follow the RFC7942 template for section 12.1
>
> <SH> Its not clear what template to be followed. An example would help.
>
>
Dhruv: Template is defined at
https://datatracker.ietf.org/doc/html/rfc7942#section-2
Example would be:
https://www.ietf.org/archive/id/draft-ietf-pce-local-protection-enforcement-11.html#section-6

--

Looking at the IANA section, just one more suggestion -

- Section 10.1, Reference should be "this document" of "Section X of this
document", just "Section X" would be incorrect! Also better to say in text
that the below allocation should be via standard action range of 0-16383
instead of putting it in the table, where it can cause confusion.
- Section 10.3, Same comment as above.

Thanks!
Dhruv