[DMM] Re: Call for adoption: draft-jlu-dmm-udp-tunnel-acaa s-02 (Ends 2026-03-16)
Uma Chunduri <[email protected]> Wed, 11 Mar 2026 14:23:45 -0700
| Newsgroups | gmane.ietf.nemo |
|---|---|
| Message-ID | <CAF18ct5BFB1rWF8Uf00K3AmMW5FDPx5eKoM+nP_g1=7DgdLD0Q__36941.4639588044$1773264307$gmane$org@mail.gmail.com> |
--===============8187391796850134670== Content-Type: multipart/alternative; boundary="000000000000f8504c064cc640f1" --000000000000f8504c064cc640f1 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Support (co-author) On Mon, Mar 2, 2026 at 4:32=E2=80=AFAM Satoru Matsushima via Datatracker < [email protected]> wrote: > This message starts a dmm WG Call for Adoption of: > draft-jlu-dmm-udp-tunnel-acaas-02 > > This Working Group Call for Adoption ends on 2026-03-16 > > Abstract: > Delivery of network services over a Layer 3 tunnel assumes that the > appropriate setup is provisioned over links that connect the customer > termination points and provider network. The required setup to allow > successful data exchange over these links is referred to as an > attachment circuit (AC) while the underlying link for carrying > network services is referred to as "bearer", in this case a Layer 3 > UDP tunnel. > > This document specifies an extension for UDP tunnel as Layer 3 bearer > to the YANG service data model for AC. > > Please reply to this message and indicate whether or not you support > adoption > of this Internet-Draft by the dmm WG. Comments to explain your preference > are > greatly appreciated. Please reply to all recipients of this message and > include this message in your response. > > Authors, and WG participants in general, are reminded of the Intellectual > Property Rights (IPR) disclosure obligations described in BCP 79 [2]. > 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 any. > Sanctions available for application to violators of IETF IPR Policy can b= e > 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/ > > The IETF datatracker status page for this Internet-Draft is: > https://datatracker.ietf.org/doc/draft-jlu-dmm-udp-tunnel-acaas/ > > There is also an HTMLized version available at: > https://datatracker.ietf.org/doc/html/draft-jlu-dmm-udp-tunnel-acaas-02 > > A diff from the previous version is available at: > https://author-tools.ietf.org/iddiff?url2=3Ddraft-jlu-dmm-udp-tunnel-acaa= s-02 > --000000000000f8504c064cc640f1 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr">Support (co-author)</div><br><div class=3D"gmail_quote gma= il_quote_container"><div dir=3D"ltr" class=3D"gmail_attr">On Mon, Mar 2, 20= 26 at 4:32=E2=80=AFAM Satoru Matsushima via Datatracker <<a href=3D"mail= to:[email protected]">[email protected]</a>> wrote:<br></div><blockquote c= lass=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px soli= d rgb(204,204,204);padding-left:1ex">This message starts a dmm WG Call for = Adoption of:<br> draft-jlu-dmm-udp-tunnel-acaas-02<br> <br> This Working Group Call for Adoption ends on 2026-03-16<br> <br> Abstract:<br> =C2=A0 =C2=A0Delivery of network services over a Layer 3 tunnel assumes tha= t the<br> =C2=A0 =C2=A0appropriate setup is provisioned over links that connect the c= ustomer<br> =C2=A0 =C2=A0termination points and provider network.=C2=A0 The required se= tup to allow<br> =C2=A0 =C2=A0successful data exchange over these links is referred to as an= <br> =C2=A0 =C2=A0attachment circuit (AC) while the underlying link for carrying= <br> =C2=A0 =C2=A0network services is referred to as "bearer", in this= case a Layer 3<br> =C2=A0 =C2=A0UDP tunnel.<br> <br> =C2=A0 =C2=A0This document specifies an extension for UDP tunnel as Layer 3= bearer<br> =C2=A0 =C2=A0to the YANG service data model for AC.<br> <br> Please reply to this message and indicate whether or not you support adopti= on<br> of this Internet-Draft by the dmm WG. Comments to explain your preference a= re<br> greatly appreciated. Please reply to all recipients of this message and<br> include this message in your response.<br> <br> Authors, and WG participants in general, are reminded of the Intellectual<b= r> Property Rights (IPR) disclosure obligations described in BCP 79 [2].<br> Appropriate IPR disclosures required for full conformance with the provisio= ns<br> of BCP 78 [1] and BCP 79 [2] must be filed, if you are aware of any.<br> Sanctions available for application to violators of IETF IPR Policy can be<= br> found at [3].<br> <br> Thank you.<br> [1] <a href=3D"https://datatracker.ietf.org/doc/bcp78/" rel=3D"noreferrer" = target=3D"_blank">https://datatracker.ietf.org/doc/bcp78/</a><br> [2] <a href=3D"https://datatracker.ietf.org/doc/bcp79/" rel=3D"noreferrer" = target=3D"_blank">https://datatracker.ietf.org/doc/bcp79/</a><br> [3] <a href=3D"https://datatracker.ietf.org/doc/rfc6701/" rel=3D"noreferrer= " target=3D"_blank">https://datatracker.ietf.org/doc/rfc6701/</a><br> <br> The IETF datatracker status page for this Internet-Draft is:<br> <a href=3D"https://datatracker.ietf.org/doc/draft-jlu-dmm-udp-tunnel-acaas/= " rel=3D"noreferrer" target=3D"_blank">https://datatracker.ietf.org/doc/dra= ft-jlu-dmm-udp-tunnel-acaas/</a><br> <br> There is also an HTMLized version available at:<br> <a href=3D"https://datatracker.ietf.org/doc/html/draft-jlu-dmm-udp-tunnel-a= caas-02" rel=3D"noreferrer" target=3D"_blank">https://datatracker.ietf.org/= doc/html/draft-jlu-dmm-udp-tunnel-acaas-02</a><br> <br> A diff from the previous version is available at:<br> <a href=3D"https://author-tools.ietf.org/iddiff?url2=3Ddraft-jlu-dmm-udp-tu= nnel-acaas-02" rel=3D"noreferrer" target=3D"_blank">https://author-tools.ie= tf.org/iddiff?url2=3Ddraft-jlu-dmm-udp-tunnel-acaas-02</a><br> </blockquote></div> --000000000000f8504c064cc640f1-- --===============8187391796850134670== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZG1tIG1haWxp bmcgbGlzdCAtLSBkbW1AaWV0Zi5vcmcKVG8gdW5zdWJzY3JpYmUgc2VuZCBhbiBlbWFpbCB0byBk bW0tbGVhdmVAaWV0Zi5vcmcK --===============8187391796850134670==--