Re: [OPSAWG] Fwd: [mpls] New Liaison Statement, "LS on the consent of draft Recommendation ITU-T Q.3962 (ex. Q.joint_tr) Requirements and Reference Model for optimized traceroute of joint Internet Protocol/Multi-Protocol Label Switching
Greg Mirsky <gregimirsky@gmail.com> Sat, 17 February 2024 05:07 UTC
Return-Path: <gregimirsky@gmail.com>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7903CC15155E; Fri, 16 Feb 2024 21:07:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.103
X-Spam-Level:
X-Spam-Status: No, score=-2.103 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, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, 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 D9svNR3B7WmW; Fri, 16 Feb 2024 21:07:33 -0800 (PST)
Received: from mail-yb1-xb2a.google.com (mail-yb1-xb2a.google.com [IPv6:2607:f8b0:4864:20::b2a]) (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 7AC80C15155A; Fri, 16 Feb 2024 21:07:33 -0800 (PST)
Received: by mail-yb1-xb2a.google.com with SMTP id 3f1490d57ef6-dccb1421bdeso2707882276.1; Fri, 16 Feb 2024 21:07:33 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1708146452; x=1708751252; 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=anYjazRWEHQK/NGaOHhkU6MiDQMog9ZJXbHoY2bPYBE=; b=kZkVc5PNIgYCDvwelTPpVMjMo9JaiK53sZ5oTslPzDb41ZUOegPTanUYF9JiD4zU5H DdklyTNihRQE6dCGlCFuYWtQJyYMYZlA0rUwPNKVI5ZyJAu9ml7W8pBGurTiw+c/Be62 7OeqF+3wO8chrflmZzgEiWjzipiCVYdFpFPFiS4W1EX3MfcJNqzyumhSpUnObFmQwl5I IY5cpNeVEwAfGP0pCW8An47/gqKZFH91GT/Q4BdZKIZY4bPlGn9iuIYk7Gq7Mz/bRAGf 2wbzApS46+2gIuBDC7U/DSsj8AeIpZXz0AC4yuXjTGvzGslo3t+5iP5T1AlsG5A37vDt S/zg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1708146452; x=1708751252; 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=anYjazRWEHQK/NGaOHhkU6MiDQMog9ZJXbHoY2bPYBE=; b=xFW3muN3uAFosHH4XYhefU7Dkisu3VtVfDa0W1pJRiRZl5rhrWZXo2+cHIdiOfq7pb 1CENBmGHz5yVmIfaKvqCOtPLAH6fSvFYPwzD9xQrwdXTKwQ+hIGx6zFOFa13ZY0Dy4IU 1SrPRvyJKemndHGEkL+wMmOks2UidgLTwnI4i70+3LQ4PP3CraDDpq8RS+9hklhwRUfV M+MRvFXeSpTDC2rRRtioPY/5XOYY5Oda4ev45e8hZzoLSpMfvz/BOMIg8x9MCoyi1/sa PV/c+DGWdi49U1VCCEwoNWfP2Nu231+93XSBjsBlWpxCYczpWN4v/HL7JCVkXr13O/mi sfCw==
X-Forwarded-Encrypted: i=1; AJvYcCViVNGV8wIxbumXY3phv6izZ868s6EscnftRGt19s8TwFim7MLvX7vfWX6ZtTVgTuBjIZWOKEf9fwxNf57B85U=
X-Gm-Message-State: AOJu0YyiI1WiAj0R5r+9CGFlPMIepDZaq0D9FOi5c30ld1yt7RVae+ph Uq/xiuxmz63agMxUeCPVlSSAXlZCFRTbn5P29+FfnyOhQMdOwWVWDCgD1zyx2H2H4eVGMmPJbck G++KsOpS/iB19QXJQ42o6FxCvVqQ=
X-Google-Smtp-Source: AGHT+IGXNt8VmEdts6DU2D/S5exzB9ZXJcb8GbLqngMcYSP8h0nKzU1eCyWl4WJNoKBp6aj9C9a5lpfuHuMc/bH+TXs=
X-Received: by 2002:a05:6902:2310:b0:dc7:6f13:61d1 with SMTP id do16-20020a056902231000b00dc76f1361d1mr9180319ybb.20.1708146452241; Fri, 16 Feb 2024 21:07:32 -0800 (PST)
MIME-Version: 1.0
References: <6429a98e605dfb7c134ca9741651fe13.squirrel@pi.nu>
In-Reply-To: <6429a98e605dfb7c134ca9741651fe13.squirrel@pi.nu>
From: Greg Mirsky <gregimirsky@gmail.com>
Date: Fri, 16 Feb 2024 21:07:21 -0800
Message-ID: <CA+RyBmVbXkarHogvDMF=pO5Y0LV37dEkD==_pB2+Y6UjKCwuKA@mail.gmail.com>
To: loa@pi.nu
Cc: mpls@ietf.org, opsawg@ietf.org, zhoutianran@huawei.com, tony.li@tony.li, adrian@olddog.co.uk, tsaad.net@gmail.com, n.leymann@telekom.de, scott.mansfield@ericsson.com
Content-Type: multipart/alternative; boundary="00000000000082a2eb06118cd613"
Archived-At: <https://mailarchive.ietf.org/arch/msg/opsawg/PzXWLVQK_1TNge0ll7cYfd6W4cE>
Subject: Re: [OPSAWG] Fwd: [mpls] New Liaison Statement, "LS on the consent of draft Recommendation ITU-T Q.3962 (ex. Q.joint_tr) Requirements and Reference Model for optimized traceroute of joint Internet Protocol/Multi-Protocol Label Switching
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsawg/>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 17 Feb 2024 05:07:37 -0000
Hi Loa, thank you for bringing to the discussion this liaison. I've looked through the prescribed processing and I have concerns about the scenario when an ICMP packet arrives at PE1 with the TTL=3. If I understand the process correctly, IP TTL is decremented and since it is non-zero, the ICMP packet is encapsulated in MPLS with MPLS TTL set to 2. If the MPLS network has more than one P node, that MPLS TTL expires at the second downstream P node. That node discovers the ICMP packet with TTL=2. And here I see two cases: - IP Dst is unknown to the P node - IP Dst is, somehow, known to the P node In the latter case, the P node will route the ICMP packet. In the former, as I understand it, will drop its ICMP Host unreachable. Either case is troublesome. Am I missing something in the process described in the liaison? Do you see a mistake in my thinking? Regards, Greg On Fri, Feb 16, 2024 at 2:08 AM <loa@pi.nu> wrote: > All, > > We have the liaison: > > "LS on the consent of draft Recommendation ITU-T Q.3962 (ex. Q.joint_tr) > Requirements and Reference Model for optimized traceroute of joint > Internet Protocol/Multi-Protocol Label Switching". > > I have tried to read the Recommendation, still have some concerns and > questions. > > The liaison was addressed to the OPSAWG, but Tianran (OPSAWG co-chair) > sent this to the MPLS WG that seem better fitted to respond if we want to. > > One questions for the OPSAWG is that if the MPLS WG decides to respond > would the OPSAWG want to join in on the response? > > My concerns at moment are (possible there will be more) are rather high > level. > > The consented document is about "IP/MPLS" traceroute. This is core IETF/IP > areas, and within the IETF design authority.. If the intention is to > align SG-11 protocols with IETF technology that is OK. > > If it is it is a bit odd that neither STD5 (which include ICMP) nor RFC > 8029 are mentioned. In fact a consented Recommendation on IETF core > technology does not mention a single RFC. > > If the intention is to create an ITU-T owned version of traceroute we are > back in the discussion on honoring design authorities. > > The terminology is not well aligned with the IETF RFC. There are > "MultiProtocol Label Switch" rather than "MultiProtocol Label Switching", > MPLS tags (sic!), CE is said to be expanded as "Customer Equipment", while > the common IETF usage is "Customer Edge", and there is more. > > Figure 6-1 deserves some scrutiny > > - the PEs seem to belong to both carrier and enterprise network > - half of the CE seem to belong to the enterprise network and the > other half to something undefined. > > Also figure 6-1, a normal MPLS network deployment would have IP > connectivity end to end and traceroute would just work over IP. > > Havin said that there is not always IP, e.g. MPLS-TP is built on the > assumption. that IP connectivity is not necessary. > > > I think we have good reason to respond even though the Liaison is "For > Information". > > I don't know where the responsibility for STD5/ICMP lies, but possibly > someone that know could forward. > > And I think it would be a good idea to call on Scott to coordinate a > response. > > /Loa > > > > <html><head><meta http-equiv="content-type" content="text/html; > > charset=utf-8"></head><body dir="auto"><br > > id="lineBreakAtBeginningOfSignature"><div dir="ltr">Sent from my > iPhone</div><div dir="ltr"><br>Begin forwarded > > message:<br><br></div><blockquote type="cite"><div > dir="ltr"><b>From:</b> > > Greg Mirsky <gregimirsky@gmail.com><br><b>Date:</b> 29 October > 2023 > > at 04:21:17 GMT+8<br><b>To:</b> Tony Li > > <tony.li@tony.li><br><b>Cc:</b> mpls@ietf.org, Henk Birkholz > <henk.birkholz@sit.fraunhofer.de>, liaison-coordination@iab.org, > Tianran Zhou <zhoutianran=40huawei.com@dmarc.ietf.org>, Warren > Kumari <warren@kumari.net>, Joe Clarke <jclarke@cisco.com>, > mpls-chairs@ietf.org, Robert Wilton <rwilton@cisco.com>, > > itu-t-liaison@iab.org, rtg-ads@ietf.org<br><b>Subject:</b> <b>Re: [mpls] > New Liaison Statement, "LS on the consent of draft Recommendation ITU-T > Q.3962 (ex. Q.joint_tr) “Requirements and Reference Model for > optimized > > traceroute of joint Internet Protocol/Multi-Protocol Label > > Switching”"</b><br><br></div></blockquote><blockquote type="cite"><div > dir="ltr"><div dir="ltr">Hi Tony,<div>it appears to me that what this > recommendations describes is Uniform tunneling model (<a > > href="https://datatracker.ietf.org/doc/html/rfc3443">RFC 3443</a>) for > treating ICMP over MPLS (not sure whether the proponents of the > recommendation argue for using the uniform model for subscriber traffic in > > > general).</div><div><br></div><div>Regards,</div><div>Greg</div></div><br><div > class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sat, Oct 28, 2023 > > at 10:35 AM Tony Li <<a > > href="mailto:tony.li@tony.li">tony.li@tony.li</a>> > > wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px > 0px > > 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><br> > Perhaps a pointer to IOAM-DEX and a “thanks, already done”?<br> <br> > > T<br> > > <br> > > <br> > > > On Oct 28, 2023, at 10:14 AM, Adrian Farrel <<a > > href="mailto:adrian@olddog.co.uk" > > target="_blank">adrian@olddog.co.uk</a>> wrote:<br> > > > <br> > > > Thanks Tianran,<br> > > > <br> > > > I think you're right that these requirements are something the MPLS > working group may want to look at.<br> > > > <br> > > > Working group: unless you have ITU-T internal access, look at the > copy of Q.3982 that was attached and can be seen at <a > > href=" > https://www.ietf.org/lib/dt/documents/LIAISON/liaison-2023-10-24-itu-t-sg-11-opsawg-ls-on-the-consent-of-draft-recommendation-itu-t-q3962-ex-qjoint_tr-requirements-and-reference-model-for-optim-attachment-1.pdf > " > rel="noreferrer" > > target="_blank"> > https://www.ietf.org/lib/dt/documents/LIAISON/liaison-2023-10-24-itu-t-sg-11-opsawg-ls-on-the-consent-of-draft-recommendation-itu-t-q3962-ex-qjoint_tr-requirements-and-reference-model-for-optim-attachment-1.pdf > </a> > Don't follow the URL in the liaison statement.<br> > > > <br> > > > The liaison is "for information", but we might want to look to see > whether there is anything we can learn from the requirements presented, > whether we think there are existing ways of solving the problem > presented, > > and whether there is any response we want to send.<br> > > > <br> > > > Thanks,<br> > > > Adrian<br> > > > <br> > > > -----Original Message-----<br> > > > From: mpls <<a href="mailto:mpls-bounces@ietf.org" > > target="_blank">mpls-bounces@ietf.org</a>> On Behalf Of Tianran > Zhou<br> > > > Sent: 28 October 2023 10:10<br> > > > To: Liaison Statement Management Tool <<a > > href="mailto:statements@ietf.org" > > target="_blank">statements@ietf.org</a>>; Henk Birkholz <<a > href="mailto:henk.birkholz@sit.fraunhofer.de" > > target="_blank">henk.birkholz@sit.fraunhofer.de</a>>; Joe Clarke > <<a > > href="mailto:jclarke@cisco.com" > target="_blank">jclarke@cisco.com</a>>; > > <a href="mailto:mpls@ietf.org" target="_blank">mpls@ietf.org</a>; <a > href="mailto:mpls-chairs@ietf.org" > > target="_blank">mpls-chairs@ietf.org</a><br> > > > Cc: Tatiana Kurakova <<a href="mailto:tatiana.kurakova@itu.int" > target="_blank">tatiana.kurakova@itu.int</a>>; Henk Birkholz <<a > href="mailto:henk.birkholz@sit.fraunhofer.de" > > target="_blank">henk.birkholz@sit.fraunhofer.de</a>>; <a > > href="mailto:liaison-coordination@iab.org" > > target="_blank">liaison-coordination@iab.org</a>; Robert Wilton <<a > href="mailto:rwilton@cisco.com" > target="_blank">rwilton@cisco.com</a>>; > > <a href="mailto:itu-t-liaison@iab.org" > > target="_blank">itu-t-liaison@iab.org</a>; Joe Clarke <<a > > href="mailto:jclarke@cisco.com" > target="_blank">jclarke@cisco.com</a>>; > > Operations and Management Area Working Group Discussion List <<a > href="mailto:opsawg@ietf.org" target="_blank">opsawg@ietf.org</a>>; > Warren Kumari <<a href="mailto:warren@kumari.net" > > target="_blank">warren@kumari.net</a>><br> > > > Subject: Re: [mpls] New Liaison Statement, "LS on the consent of > draft Recommendation ITU-T Q.3962 (ex. Q.joint_tr) “Requirements and > Reference Model for optimized traceroute of joint Internet > > Protocol/Multi-Protocol Label Switching”"<br> > > > <br> > > > Hi MPLS WG,<br> > > > <br> > > > I forward this LS to MPLS because I believe it not really belongs > to > > OPSAWG.<br> > > > I think MPLS WG should be the right place to receive.<br> > > > <br> > > > Best,<br> > > > Tianran<br> > > > <br> > > > <br> > > > -----Original Message-----<br> > > > From: Liaison Statement Management Tool [mailto:<a > > href="mailto:statements@ietf.org" > target="_blank">statements@ietf.org</a>] > > <br> > > > Sent: Tuesday, October 24, 2023 11:23 PM<br> > > > To: Henk Birkholz <<a > > href="mailto:henk.birkholz@sit.fraunhofer.de" > > target="_blank">henk.birkholz@sit.fraunhofer.de</a>>; Joe Clarke > <<a > > href="mailto:jclarke@cisco.com" > target="_blank">jclarke@cisco.com</a>>; > > Tianran Zhou <<a href="mailto:zhoutianran@huawei.com" > > target="_blank">zhoutianran@huawei.com</a>><br> > > > Cc: Henk Birkholz <<a > > href="mailto:henk.birkholz@sit.fraunhofer.de" > > target="_blank">henk.birkholz@sit.fraunhofer.de</a>>; Joe Clarke > <<a > > href="mailto:jclarke@cisco.com" > target="_blank">jclarke@cisco.com</a>>; > > Operations and Management Area Working Group Discussion List <<a > href="mailto:opsawg@ietf.org" target="_blank">opsawg@ietf.org</a>>; > Robert Wilton <<a href="mailto:rwilton@cisco.com" > > target="_blank">rwilton@cisco.com</a>>; Scott Mansfield > > <Scott.Mansfield@Ericsson.com>; Tatiana Kurakova <<a > > href="mailto:tatiana.kurakova@itu.int" > > target="_blank">tatiana.kurakova@itu.int</a>>; Tianran Zhou <<a > href="mailto:zhoutianran@huawei.com" > > target="_blank">zhoutianran@huawei.com</a>>; Warren Kumari <<a > href="mailto:warren@kumari.net" > target="_blank">warren@kumari.net</a>>; > > <a href="mailto:itu-t-liaison@iab.org" > > target="_blank">itu-t-liaison@iab.org</a>; <a > > href="mailto:liaison-coordination@iab.org" > > target="_blank">liaison-coordination@iab.org</a><br> > > > Subject: New Liaison Statement, "LS on the consent of draft > Recommendation ITU-T Q.3962 (ex. Q.joint_tr) “Requirements and > Reference > > Model for optimized traceroute of joint Internet Protocol/Multi-Protocol > Label Switching”"<br> > > > <br> > > > Title: LS on the consent of draft Recommendation ITU-T Q.3962 (ex. > Q.joint_tr) “Requirements and Reference Model for optimized traceroute > of joint Internet Protocol/Multi-Protocol Label Switching”<br> > > Submission Date: 2023-10-24<br> > > > URL of the IETF Web page: <a > > href="https://datatracker.ietf.org/liaison/1869/" rel="noreferrer" > target="_blank">https://datatracker.ietf.org/liaison/1869/</a><br> > > <br> > > > From: Denis ANDREEV <<a href="mailto:tsbsg11@itu.int" > > target="_blank">tsbsg11@itu.int</a>><br> > > > To: Henk Birkholz <<a > > href="mailto:henk.birkholz@sit.fraunhofer.de" > > target="_blank">henk.birkholz@sit.fraunhofer.de</a>>,Joe Clarke > <<a > > href="mailto:jclarke@cisco.com" > > target="_blank">jclarke@cisco.com</a>>,Tianran Zhou <<a > > href="mailto:zhoutianran@huawei.com" > > target="_blank">zhoutianran@huawei.com</a>><br> > > > Cc: Robert Wilton <<a href="mailto:rwilton@cisco.com" > > target="_blank">rwilton@cisco.com</a>>,Warren Kumari <<a > > href="mailto:warren@kumari.net" > > target="_blank">warren@kumari.net</a>>,<a > > href="mailto:itu-t-liaison@iab.org" > > target="_blank">itu-t-liaison@iab.org</a> <<a > > href="mailto:itu-t-liaison@iab.org" > > target="_blank">itu-t-liaison@iab.org</a>>,Joe Clarke <<a > > href="mailto:jclarke@cisco.com" > > target="_blank">jclarke@cisco.com</a>>,Scott Mansfield > > <Scott.Mansfield@Ericsson.com>,Operations and Management Area > Working Group Discussion List <<a href="mailto:opsawg@ietf.org" > target="_blank">opsawg@ietf.org</a>>,Henk Birkholz <<a > > href="mailto:henk.birkholz@sit.fraunhofer.de" > > target="_blank">henk.birkholz@sit.fraunhofer.de</a>>,Tianran Zhou > <<a href="mailto:zhoutianran@huawei.com" > > target="_blank">zhoutianran@huawei.com</a>> Response Contacts: > Tatiana > > Kurakova <<a href="mailto:tatiana.kurakova@itu.int" > > target="_blank">tatiana.kurakova@itu.int</a>> Technical Contacts: > <br> > > > Purpose: For information<br> > > > <br> > > > Body: This liaison statement provides information about the > consented > > item as a result of the ITU-T SG11 meeting (Geneva, 10-20 October > 2023).<br> > > > <br> > > > ITU-T SG11 would like to inform ITU-T Study Group 13 and IETF about > the draft new Recommendation ITU-T Q.3962 (ex. Q. joint_tr) > > “Requirements and Reference Model for optimized traceroute of joint > Internet Protocol/Multi-Protocol Label Switching” which was consented > during the ITU-T SG11 meeting (Geneva, 10-20 October 2023).<br> > > > <br> > > > The draft new Recommendation ITU-T Q. 3962 (ex. Q. joint_tr) > “Requirements and Reference Model for optimized traceroute of joint > Internet Protocol/Multi-Protocol Label Switching” is attached for your > convenience.<br> > > > ITU-T SG11 looks forward to collaborating with ITU-T Study Group 13 > and IETF on this matter.<br> > > > <br> > > > Attachment:<br> > > > SG11-TD747/GEN: Consent – draft Recommendation ITU-T Q.3962 (ex. > Q.joint_tr): Requirements and Reference Model for optimized traceroute of > > joint Internet Protocol/Multi-Protocol Label Switching (Geneva, 10-20 > October 2023)<br> > > > Attachments:<br> > > > <br> > > > SG11-LS108-Att-TD747<br> > > > <a > > href=" > https://www.ietf.org/lib/dt/documents/LIAISON/liaison-2023-10-24-itu-t-sg-11-opsawg-ls-on-the-consent-of-draft-recommendation-itu-t-q3962-ex-qjoint_tr-requirements-and-reference-model-for-optim-attachment-1.pdf > " > rel="noreferrer" > > target="_blank"> > https://www.ietf.org/lib/dt/documents/LIAISON/liaison-2023-10-24-itu-t-sg-11-opsawg-ls-on-the-consent-of-draft-recommendation-itu-t-q3962-ex-qjoint_tr-requirements-and-reference-model-for-optim-attachment-1.pdf > </a><br> > > <br> > > > SG11-LS108<br> > > > <a > > href=" > https://www.ietf.org/lib/dt/documents/LIAISON/liaison-2023-10-24-itu-t-sg-11-opsawg-ls-on-the-consent-of-draft-recommendation-itu-t-q3962-ex-qjoint_tr-requirements-and-reference-model-for-optim-attachment-2.docx > " > rel="noreferrer" > > target="_blank"> > https://www.ietf.org/lib/dt/documents/LIAISON/liaison-2023-10-24-itu-t-sg-11-opsawg-ls-on-the-consent-of-draft-recommendation-itu-t-q3962-ex-qjoint_tr-requirements-and-reference-model-for-optim-attachment-2.docx > </a><br> > > <br> > > > <br> > > > <br> > > > _______________________________________________<br> > > > mpls mailing list<br> > > > <a href="mailto:mpls@ietf.org" > target="_blank">mpls@ietf.org</a><br> > > > <a href="https://www.ietf.org/mailman/listinfo/mpls" > rel="noreferrer" > > target="_blank">https://www.ietf.org/mailman/listinfo/mpls</a><br> > > <br> > > > _______________________________________________<br> > > > mpls mailing list<br> > > > <a href="mailto:mpls@ietf.org" > target="_blank">mpls@ietf.org</a><br> > > > <a href="https://www.ietf.org/mailman/listinfo/mpls" > rel="noreferrer" > > target="_blank">https://www.ietf.org/mailman/listinfo/mpls</a><br> <br> > _______________________________________________<br> > > mpls mailing list<br> > > <a href="mailto:mpls@ietf.org" target="_blank">mpls@ietf.org</a><br> <a > href="https://www.ietf.org/mailman/listinfo/mpls" rel="noreferrer" > target="_blank">https://www.ietf.org/mailman/listinfo/mpls</a><br> > </blockquote></div> > > > <span>_______________________________________________</span><br><span>mpls > mailing > > list</span><br><span>mpls@ietf.org</span><br><span> > https://www.ietf.org/mailman/listinfo/mpls > </span><br></div></blockquote></body></html> > > > > > > > > > > > > > > >