Return-Path: X-Original-To: dmm@mail2.ietf.org Delivered-To: dmm@mail2.ietf.org Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 66E429041772 for ; Tue, 25 Nov 2025 06:06:28 -0800 (PST) X-Virus-Scanned: amavisd-new at ietf.org X-Spam-Flag: NO X-Spam-Score: -1.998 X-Spam-Level: X-Spam-Status: No, score=-1.998 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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TvYxOCfOVGqt for ; Tue, 25 Nov 2025 06:06:27 -0800 (PST) Received: from mail-wm1-x335.google.com (mail-wm1-x335.google.com [IPv6:2a00:1450:4864:20::335]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id AF385904132C for ; Tue, 25 Nov 2025 06:05:21 -0800 (PST) Received: by mail-wm1-x335.google.com with SMTP id 5b1f17b1804b1-477985aea2bso5441735e9.3 for ; Tue, 25 Nov 2025 06:05:21 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1764079514; x=1764684314; 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=8kjzb4GjmZr6QeCTDbXHaQUOlu3Ws2rPR4Q4hif9Qgg=; b=JfvZL7bjxG913KuxlpPOGILGqgqi0+4gPlCjs7TESiP65fjOcx13kat4AFQZyxMqAb vRj/nk/Rr9dpIKD+s7xWPSUNhnVU1OE05ZeotPytmeRANpT5xMcrdexdHnpAx7W/3/Lw 0yJIfZellX0sYQP0VII9sCiJkLKM/7b7FKiC8jPYHcgX5+AbzXz21ljsmZ1F5R8B20Tp pdBVWJy0J11oC0qdo0cD18qh+ZgwdLyZCSeWzHgjJi6JkoZb5iUzhtGe9u4mPtw9tHFW 9zvZheCMODrJezCGorLV8X1aZpNAIQJjNEFHOOecnoK3AwLTsqjxvf9rc0MJSV+XoYo9 KZXg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1764079514; x=1764684314; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-gg:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=8kjzb4GjmZr6QeCTDbXHaQUOlu3Ws2rPR4Q4hif9Qgg=; b=EYzF9jGjbt6VK14ogTQ06iU3yQXr6z5sIUzeFCRcyDe86a1dEaxb9DomCJhby+HExY jsRyIJyC6apaWGtAHnZAz5ReATKxtze+6jkv24+sGPXzanSG6LBvYRHwP33jCkXchENL qb9FCBbWl0QEFQ6E8UZ49xDC+hbe0gHURWNDLjYkS1jqGwNb50DuJC0svxUiF3UJMcOF /XqHw981aoVWavqMZfedsgDTjyfnSTjYlydz4cdxrUl9WKQy7yuYlnnQ9kHGjwhN3JfP Ec9hf/eAYl1sL3o2VT+frysyUB4v/vlPnAIqviU8iQ9ghtXeK2WguOrhsAybTq8CBvgN TzeQ== X-Forwarded-Encrypted: i=1; AJvYcCVUYJ5V4kjmkcu5qovCWB07ikUYH06u6ooKh6t6sEWD5TVlHG5qFTIkfxWiv43lStH4sZU=@ietf.org X-Gm-Message-State: AOJu0YxW9hXANUau/CmKCrjvTV+iH+ZK8lD8jAcng1bLAPotHmK8w+IE BkliPKanq5dKVat4jN1EaTaKhTPDVJT9jGNLxRTQPFCAoy2X+m2mfpFaJsav+RG9QeAwHSWmJ8Z owvlGBN0v6w2pZjH/q+Q7RabpxRkh+AI= X-Gm-Gg: ASbGncuuCJzGMDfvIIWqlIWGpRs0ap8x4A11NRMAFOuOgaMr+SbOQ52N7bICAX3xMbH oRnYrMdDFmJ0A095xi6rUaI4qhDmZejjaFWg0iJLIXSy0cnTAHKajdJZkABtDOkEBZIdgJ8mlK8 8SwFs4JWxOPZg7O0Mj9C02Ph/CXEsOHZIcW6x4XUilr5+BnpikYiwyTfBmncm+uPELVSglDCfbi HZBMxV7xxZMXdNk8hQjJZOBHlg85eQUnIcGsHw72Od4GvxSHHJeqsy9nE0yc4rLgwhIyh0itHL6 vd8kiw== X-Google-Smtp-Source: AGHT+IHr4/s2dOWkphMWfwix/aedun83Wb+yPCjJm5++yaIsOavFclSOipyj7xFZKX/Rx+qtoEJxRKvqgZA2HP2NShU= X-Received: by 2002:a05:600c:314f:b0:468:7a5a:14cc with SMTP id 5b1f17b1804b1-477c313f9e9mr83427035e9.3.1764079514298; Tue, 25 Nov 2025 06:05:14 -0800 (PST) MIME-Version: 1.0 References: <176061658528.1327520.11569553824543054590@dt-datatracker-84f8f646b-tg6mn> In-Reply-To: From: Satoru Matsushima Date: Tue, 25 Nov 2025 23:05:01 +0900 X-Gm-Features: AWmQ_bkJhZtnAJm4dYM7X21urbVAH5_cPPxT74fvKP3qHTajsuBs0Yjrmb83nD8 Message-ID: To: Kaippallimalil John Content-Type: multipart/alternative; boundary="000000000000ce2c9f06446bc488" Message-ID-Hash: A5YEAQBTB43NJZQBBUPHUEUJLN22U7DE X-Message-ID-Hash: A5YEAQBTB43NJZQBBUPHUEUJLN22U7DE X-MailFrom: satoru.matsushima@gmail.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-dmm.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header CC: "dmm-chairs@ietf.org" , "dmm@ietf.org" , "draft-ietf-dmm-tn-aware-mobility@ietf.org" X-Mailman-Version: 3.3.9rc6 Precedence: list Subject: =?utf-8?q?=5BDMM=5D_Re=3A_WG_Last_Call=3A_draft-ietf-dmm-tn-aware-mobility-2?= =?utf-8?q?2_=28Ends_2025-10-30=29?= List-Id: Distributed Mobility Management Working Group Archived-At: List-Archive: List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: --000000000000ce2c9f06446bc488 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi John, Could you please confirm if you plan to address the following specific comments from Xavier de Foy? - Section 3.1: Change /end-user (UE) sessions/PDU sessions/ and consider describing the meaning of "PDU session" at its first occurrence. - Change /to that signaled for the PDU session/to the S-NSSAI signaled for the PDU session/ I was unable to find the resolutions for these particular points in the latest diff and your slides in the last DMM meeting. Thanks, --satoru On Tue, Nov 4, 2025 at 11:22=E2=80=AFPM Kaippallimalil John < john.kaippallimalil@futurewei.com> wrote: > Hi Xavier, > > > Thank you for the comments and support. > > > > Please see the new revision that implements the suggested changes below. > > Link to diff: > > > https://nam11.safelinks.protection.outlook.com/?url=3Dhttps%3A%2F%2Fautho= r-tools.ietf.org%2Fiddiff%3Furl2%3Ddraft-ietf-dmm-tn-aware-mobility-23&data= =3D05%7C02%7Cjohn.kaippallimalil%40futurewei.com%7Ca53923a3718f4b44e9b608de= 1bad41bc%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C638978628121984873%7C= Unknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXa= W4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=3DrRuK6uT3gVgtpA= K0YvjXQ5IuG%2FC8YnGdGIZI1BQfvXg%3D&reserved=3D0 > > > > > Best Regards, > > John > > > > > > *From:* Xavier de Foy > *Sent:* Wednesday, October 29, 2025 11:35 AM > *To:* Satoru Matsushima ; dmm-chairs@ietf.or= g; > dmm@ietf.org; draft-ietf-dmm-tn-aware-mobility@ietf.org > *Subject:* Re: [DMM] Re: WG Last Call: > draft-ietf-dmm-tn-aware-mobility-22 (Ends 2025-10-30) > > > > I support the publication of draft-ietf-dmm-tn-aware-mobility and provide > a few minor comments below, for the authors' consideration. > > > > > > - #1: /map a 3GPP slice to a slice in an IP transport network provider/ma= p > a 3GPP slice to a slice in an IP transport network/ -OR- /map a 3GPP slic= e > to an IP transport network slice at a provider edge/ > > - #3.1: /end-user (UE) sessions/PDU sessions/, because the term PDU > session is used multiple times in the document already. > - Note: consider expanding the term UE as User Equipment in the first > occurence of the term in the draft. > - Note: consider describing the meaning of PDU session at the first > occurence of the term. > > - #3.3: consider adding text to define what EP_transport is. E.g., /3GPP > user plane nodes (gNB, UPF) are provisioned with GTP transport interface > information parameters in [TS.28.541-3GPP]./3GPP user plane nodes (gNB, > UPF) are provisioned with GTP end point transport (EP_transport) interfac= e > information parameters in [TS.28.541-3GPP]./ > - #3.3: a few sentences could be clarified a bit,I try illustrating below > a few points. > - "Each EP_Transport is configured with ATTACHMENT_CIRCUIT containing > UDP source port number/range for each of the slices (S-NSSAI) supported b= y > the 3GPP user plane node." Maybe: "Each EP_Transport is configured with a= n > ATTACHMENT_CIRCUIT containing UDP source port number/range corresponding = to > a slice (S-NSSAI) supported by the 3GPP user plane node." > - "This S-NSSAI in the user plane setup can be used to associate with > the previously configured EP_Transport information per S-NSSAI." Maybe: > "This S-NSSAI in the user plane setup can be associated with one of the > previously configured per-S-NSSAI EP_Transport information." > - /to that signaled for the PDU session/to the S-NSSAI signaled for the > PDU session/ > > - #4: About the paragraph "In some E2E scenarios, security is desired > granularly...", I was wondering if the text could cover something more > general than security, e.g., "In some E2E scenarios, additional path > characteristics may be desired in the underlying transport network, such = as > security characteristics.". The rest of the paragraph may be adapted > correspondingly, if you agree with this comment. One example of > non-security characteristic that comes to mind is regulatory/legal, e.g., > the physical location of the path (and this does not need to be spelled o= ut > in the text, this is just for illustrating where my comment comes from). > > - #6: /authenticaiton/authentication/ > > > > Best Regards, > > Xavier > > > > On Wed, Oct 29, 2025 at 7:23=E2=80=AFAM Kaippallimalil John < > john.kaippallimalil@futurewei.com> wrote: > > draft-ietf-dmm-tn-aware-mobility provides a solution to support the > capabilities offered by 5G slices across IP transport networks that > backhaul the traffic. > > As an author, I believe this draft is ready for publication. > > > > Best Regards, > > John > > > > *From:* Satoru Matsushima > *Sent:* Friday, October 24, 2025 4:52 PM > *To:* Satoru Matsushima > *Cc:* dmm-chairs@ietf.org; dmm@ietf.org; > draft-ietf-dmm-tn-aware-mobility@ietf.org > *Subject:* Re: WG Last Call: draft-ietf-dmm-tn-aware-mobility-22 (Ends > 2025-10-30) > > > > DMMer, > > > > Let me remind you that the mobility-aware transport draft is now in WGLC. > It will end on Oct. 30, so please review the draft. > > You can use this thread to send your feedback. > > > > Cheers, > > --satoru > > > > On Thu, Oct 16, 2025 at 9:09=E2=80=AFPM Satoru Matsushima via Datatracker= < > noreply@ietf.org> wrote: > > > Subject: WG Last Call: draft-ietf-dmm-tn-aware-mobility-22 (Ends > 2025-10-30) > > This message starts a 2-week WG Last Call for this document. > > Abstract: > Network slicing in 5G enables logical networks for communication > services of multiple 5G customers to be multiplexed over the same > infrastructure. While 5G slicing covers logical separation of > various aspects of 5G infrastructure and services, user's data plane > packets over the Radio Access Network (RAN) and Core Network (5GC) > use IP in many segments of an end-to-end 5G slice. When end-to-end > slices in a 5G System use network resources, they are mapped to > corresponding IP transport network slice(s) which in turn provide the > bandwidth, latency, isolation, and other criteria required for the > realization of a 5G slice. > > This document describes mapping of 5G slices to transport network > slices using UDP source port number of the GTP-U bearer when the IP > transport network (slice provider) is separated by an "attachment > circuit" from the networks in which the 5G network functions are > deployed, for example, 5G functions that are distributed across data > centers. The slice mapping defined here is supported transparently > when a 5G user device moves across 5G attachment points and session > anchors. > > File can be retrieved from: > https://datatracker.ietf.org/doc/draft-ietf-dmm-tn-aware-mobility/ > > Please review and indicate your support or objection to proceed with the > publication of this document by replying to this email keeping > dmm@ietf.org > in copy. Objections should be motivated and suggestions to resolve them a= re > highly appreciated. > > Authors, and WG participants in general, are reminded again of the > Intellectual Property Rights (IPR) disclosure obligations described in BC= P > 79 > [1]. Appropriate IPR disclosures required for full conformance with the > provisions of BCP 78 [1] and BCP 79 [2] must be filed, if you are aware o= f > any. Sanctions available for application to violators of IETF IPR Policy > can > be found at [3]. > > Thank you. > > [1] https://datatracker.ietf.org/doc/bcp78/ > [2] https://datatracker.ietf.org/doc/bcp79/ > [3] https://datatracker.ietf.org/doc/rfc6701/ > > _______________________________________________ > dmm mailing list -- dmm@ietf.org > To unsubscribe send an email to dmm-leave@ietf.org > > --000000000000ce2c9f06446bc488 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi John,

Could you please co= nfirm if you plan to address the following specific comments from Xavier de= Foy?

- Section 3.1: Change /end-user (UE) sessi= ons/PDU sessions/ and consider describing the meaning of "PDU session&= quot; at its first occurrence.
- Change /to that signaled for t= he PDU session/to the S-NSSAI signaled for the PDU session/

<= /div>
I was unable to find the resolutions for these particular points = in the latest diff and your slides in the last DMM meeting.

<= /div>
Thanks,
--satoru

On Tue, Nov= 4, 2025 at 11:22=E2=80=AFPM Kaippallimalil John <john.kaippallimalil@futurewei.com> wr= ote:

Hi Xavier,


Thank you for the comments and support.

=C2=A0

Please see the new revision that implements the sugg= ested changes below.

Link to diff:

https://nam11.safelinks.protection.outlook.com/?url=3Dhttps%3A%2F%2= Fauthor-tools.ietf.org%2Fiddiff%3Furl2%3Ddraft-ietf-dmm-tn-aware-mobility-2= 3&data=3D05%7C02%7Cjohn.kaippallimalil%40futurewei.com%7Ca53923a3718f4b= 44e9b608de1bad41bc%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C63897862812= 1984873%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCI= sIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=3D= rRuK6uT3gVgtpAK0YvjXQ5IuG%2FC8YnGdGIZI1BQfvXg%3D&reserved=3D0

=C2=A0

Best Regards,

John

=C2=A0

=C2=A0

From: Xavier de Foy <x.defoy.ietf@gmail.com>
Sent: Wednesday, October 29, 2025 11:35 AM
To: Satoru Matsushima <satoru.matsushima@gmail.com>; dmm-chairs@ietf.org; dmm@ietf.org; draft-ietf= -dmm-tn-aware-mobility@ietf.org
Subject: Re: [DMM] Re: WG Last Call: draft-ietf-dmm-tn-aware-mobilit= y-22 (Ends 2025-10-30)

=C2=A0

I support the publication of draft-ietf-dmm-tn-aware= -mobility and provide a few minor comments below, for the authors' cons= ideration. =C2=A0

=C2=A0

=C2=A0

- #1: /map a 3GPP slice= to a slice in an IP transport network provider/map a 3GPP slice to a slice= in an IP transport network/ -OR- /map a 3GPP slice to an=C2=A0 IP transpor= t network slice at a provider edge/

- #3.1: /end-user (UE) sessions/PDU sessions/, because the term PDU session= is used multiple times in the document already.
=C2=A0 - Note: consider expanding the term UE as User Equipment in the firs= t occurence of the term in the draft.
=C2=A0 - Note: consider describing the meaning of PDU session at the first = occurence of the term.
=C2=A0
- #3.3: consider adding text to define what EP_transport is. E.g., /3GPP us= er plane nodes (gNB, UPF) are provisioned with GTP transport interface info= rmation parameters in [TS.28.541-3GPP]./3GPP user plane nodes (gNB, UPF) ar= e provisioned with GTP end point transport (EP_transport) interface information parameters in [TS.28.541-3G= PP]./
- #3.3: a few sentences could be clarified a bit,I try illustrating below a= few points.
=C2=A0 - "Each EP_Transport is configured with ATTACHMENT_CIRCUIT cont= aining UDP source port number/range for each of the slices (S-NSSAI) suppor= ted by the 3GPP user plane node." Maybe: "Each EP_Transport is co= nfigured with an ATTACHMENT_CIRCUIT containing UDP source port number/range corresponding to a slice (S-NSSAI) supported by the 3GPP= user plane node."
=C2=A0 - "This S-NSSAI in the user plane setup can be used to associat= e with the previously configured EP_Transport information per S-NSSAI."= ; Maybe: "This S-NSSAI in the user plane setup can be associated with = one of the previously configured per-S-NSSAI EP_Transport information."
=C2=A0 - /to that signaled for the PDU session/to the S-NSSAI signaled for = the PDU session/

- #4: About the paragraph "In some E2E scenarios, security is desired = granularly...", I was wondering if the text could cover something more= general than security, e.g., "In some E2E scenarios, additional path = characteristics may be desired in the underlying transport network, such as security characteristics.". The rest of th= e paragraph may be adapted correspondingly, if you agree with this comment.= One example of non-security characteristic that comes to mind is regulator= y/legal, e.g., the physical location of the path (and this does not need to be spelled out in the text, this is= just for illustrating where my comment comes from).

- #6: /authenticaiton/authentication/<= /p>

=C2=A0

Best Regards,

Xavier

=C2=A0

On Wed, Oct 29, 2025 at 7:23=E2=80=AFAM Kaippallimalil John <john.kaippallim= alil@futurewei.com> wrote:

draft-ietf-dmm-tn-aware-mobility provides a solution= to support the capabilities offered by 5G slices across IP transport netwo= rks that backhaul the traffic.

As an author, I believe this draft is ready for publ= ication.

=C2=A0

Best Regards,

John

=C2=A0

From: Satoru Matsushima <satoru.matsushima@gmail.com>
Sent: Friday, October 24, 2025 4:52 PM
To: Satoru Matsushima <satoru.matsushima@gmail.com>
Cc: dmm-cha= irs@ietf.org; dmm@ietf.org; draft-ietf-dmm-tn-aware-mobility@ietf.org
Subject: Re: WG Last Call: draft-ietf-dmm-tn-aware-mobility-22 (Ends= 2025-10-30)

=C2=A0

DMMer,

=C2=A0

Let me remind you that the mobility-aware transport = draft is now in WGLC. It will end on Oct. 30, so please review=C2=A0the dra= ft.

You can use this thread to=C2=A0send your feedback.= =C2=A0

=C2=A0

Cheers,

--satoru

=C2=A0

On Thu, Oct 16, 2025 at 9:09=E2=80=AFPM Satoru Matsushima via Datatracker &= lt;noreply@ietf.org> wrote:


Subject: WG Last Call: draft-ietf-dmm-tn-aware-mobility-22 (Ends 2025-10-30= )

This message starts a 2-week WG Last Call for this document.

Abstract:
=C2=A0 =C2=A0Network slicing in 5G enables logical networks for communicati= on
=C2=A0 =C2=A0services of multiple 5G customers to be multiplexed over the s= ame
=C2=A0 =C2=A0infrastructure.=C2=A0 While 5G slicing covers logical separati= on of
=C2=A0 =C2=A0various aspects of 5G infrastructure and services, user's = data plane
=C2=A0 =C2=A0packets over the Radio Access Network (RAN) and Core Network (= 5GC)
=C2=A0 =C2=A0use IP in many segments of an end-to-end 5G slice.=C2=A0 When = end-to-end
=C2=A0 =C2=A0slices in a 5G System use network resources, they are mapped t= o
=C2=A0 =C2=A0corresponding IP transport network slice(s) which in turn prov= ide the
=C2=A0 =C2=A0bandwidth, latency, isolation, and other criteria required for= the
=C2=A0 =C2=A0realization of a 5G slice.

=C2=A0 =C2=A0This document describes mapping of 5G slices to transport netw= ork
=C2=A0 =C2=A0slices using UDP source port number of the GTP-U bearer when t= he IP
=C2=A0 =C2=A0transport network (slice provider) is separated by an "at= tachment
=C2=A0 =C2=A0circuit" from the networks in which the 5G network functi= ons are
=C2=A0 =C2=A0deployed, for example, 5G functions that are distributed acros= s data
=C2=A0 =C2=A0centers.=C2=A0 The slice mapping defined here is supported tra= nsparently
=C2=A0 =C2=A0when a 5G user device moves across 5G attachment points and se= ssion
=C2=A0 =C2=A0anchors.

File can be retrieved from:
https://datatracker.ietf.org/doc/draft-ietf-dmm-tn-aw= are-mobility/

Please review and indicate your support or objection to proceed with the publication of this document by replying to this email keeping dmm@ietf.org
in copy. Objections should be motivated and suggestions to resolve them are=
highly appreciated.

Authors, and WG participants in general, are reminded again of the
Intellectual Property Rights (IPR) disclosure obligations described in BCP = 79
[1]. Appropriate IPR disclosures required for full conformance with the
provisions of BCP 78 [1] and BCP 79 [2] must be filed, if you are aware of<= br> any. Sanctions available for application to violators of IETF IPR Policy ca= n
be found at [3].

Thank you.

[1] h= ttps://datatracker.ietf.org/doc/bcp78/
[2] h= ttps://datatracker.ietf.org/doc/bcp79/
[3] https://datatracker.ietf.org/doc/rfc6701/

_______________________________________________
dmm mailing list -- dmm@i= etf.org
To unsubscribe send an email to dmm-leave@ietf.org

--000000000000ce2c9f06446bc488--