[manet] Re: Call for adoption: draft-templin-manet-inet-05 (Ends 2026-05-06)

--===============1496838943248198629==
Content-Type: multipart/alternative; boundary="000000000000dea45a0651245737"

--000000000000dea45a0651245737
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hi Don,

I agree with you, and I will add that usually informational drafts in IETF
are usually healthy for IETF WG to clarify issues and make discussions more
focused. This draft is an excellent new effort to open discussions and
analysis that need to be faced (open old discussions that were
closed/ignored). Also IMHO no manet_participant can guarantee to be knowing
what this WG agrees on or disagrees on (especially while holding old RFCs),
opinions change and technologies change, so the best for IETF WGs to make
adoption to new informational drafts to know what this old WG agrees on or
disagrees on.

best wishes,
AB

On Tue, Apr 28, 2026 at 3:16=E2=80=AFPM Don Fedyk <[email protected]> wrote:

> Hi all,
> We=E2=80=99ve seen only light responses to the current adoption call,  so=
 I wanted
> to briefly clarify what adoption means in this context.
> Adoption by the WG means that we, as a working group, agree to take on th=
e
> document and develop it in alignment with our charter=E2=80=94specificall=
y as an
> informational document. This would include describing the problem space
> around MANET internetworking, documenting existing approaches, and
> outlining proposed methods where appropriate.
> In the chairs view, this topic is within scope of our charter. However, I
> believe the document would benefit from a clearer comparison with existin=
g
> approaches that already address aspects of MANET internetworking. Example=
s
> include:
>
>    - NEMO (RFC 3963)
>    - LISP-based mobility and overlays
>    - HIP mobility
>    - DLEP-based MANET deployments with gatewaying
>    - Conventional tunneling / prefix delegation approaches
>    - OMNI-Aero
>
> The document is not there yet. That said, MANET internetworking has been
> the prominent topic in our recent meetings.
> The purpose of this adoption call is to determine whether there is a
> broader WG consensus to move forward with this work. It is therefore
> important to understand whether WG participants support and will contribu=
te
> reviews and feedback to this work.
> Please share your views before the call ends on 6 May.
> Thank you to those that have responded,
> Don
>
> _______________________________________________
> manet mailing list -- [email protected]
> To unsubscribe send an email to [email protected]
>

--000000000000dea45a0651245737
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi Don,<div><br></div><div>I agree with you, and I will ad=
d that usually informational drafts in IETF are usually healthy for IETF WG=
 to clarify issues and make discussions more focused. This draft is an exce=
llent new effort to open discussions and analysis that need to be faced (op=
en old discussions that were closed/ignored). Also IMHO no manet_participan=
t can guarantee=C2=A0to be knowing what this WG agrees on or disagrees on (=
especially while holding old RFCs), opinions change and technologies change=
, so the best for IETF WGs to make adoption to new informational drafts to =
know what this old WG agrees on or disagrees on.</div><div><br></div><div>b=
est wishes,</div><div>AB</div></div><br><div class=3D"gmail_quote gmail_quo=
te_container"><div dir=3D"ltr" class=3D"gmail_attr">On Tue, Apr 28, 2026 at=
 3:16=E2=80=AFPM Don Fedyk &lt;<a href=3D"mailto:[email protected]">dfedyk@la=
bn.net</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"m=
argin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left=
:1ex"><div class=3D"msg-4743030823055461990">




<div dir=3D"ltr">
<div style=3D"margin-top:1em;margin-bottom:1em;font-family:Aptos,Aptos_Embe=
ddedFont,Aptos_MSFontService,Calibri,Helvetica,sans-serif;font-size:11pt;co=
lor:rgb(0,0,0)">
Hi all,</div>
<div style=3D"margin-top:1em;margin-bottom:1em;font-family:Aptos,Aptos_Embe=
ddedFont,Aptos_MSFontService,Calibri,Helvetica,sans-serif;font-size:11pt;co=
lor:rgb(0,0,0)">
We=E2=80=99ve seen only light responses to the current adoption call, =C2=
=A0so I wanted to briefly clarify what adoption means in this context.</div=
>
<div style=3D"margin-top:1em;margin-bottom:1em;font-family:Aptos,Aptos_Embe=
ddedFont,Aptos_MSFontService,Calibri,Helvetica,sans-serif;font-size:11pt;co=
lor:rgb(0,0,0)">
Adoption by the WG means that we, as a working group, agree to take on the =
document and develop it in alignment with our charter=E2=80=94specifically =
as an informational document. This would include describing the problem spa=
ce around MANET internetworking, documenting
 existing approaches, and outlining proposed methods where appropriate.</di=
v>
<div style=3D"margin-top:1em;margin-bottom:1em;font-family:Aptos,Aptos_Embe=
ddedFont,Aptos_MSFontService,Calibri,Helvetica,sans-serif;font-size:11pt;co=
lor:rgb(0,0,0)">
In the chairs view, this topic is within scope of our charter. However, I b=
elieve the document would benefit from a clearer comparison with existing a=
pproaches that already address aspects of MANET internetworking. Examples i=
nclude:</div>
<ul>
<li style=3D"font-family:Aptos,Aptos_EmbeddedFont,Aptos_MSFontService,Calib=
ri,Helvetica,sans-serif;font-size:11pt;color:rgb(0,0,0)">
NEMO (RFC 3963)</li><li style=3D"font-family:Aptos,Aptos_EmbeddedFont,Aptos=
_MSFontService,Calibri,Helvetica,sans-serif;font-size:11pt;color:rgb(0,0,0)=
">
LISP-based mobility and overlays</li><li style=3D"font-family:Aptos,Aptos_E=
mbeddedFont,Aptos_MSFontService,Calibri,Helvetica,sans-serif;font-size:11pt=
;color:rgb(0,0,0)">
HIP mobility</li><li style=3D"font-family:Aptos,Aptos_EmbeddedFont,Aptos_MS=
FontService,Calibri,Helvetica,sans-serif;font-size:11pt;color:rgb(0,0,0)">
DLEP-based MANET deployments with gatewaying</li><li style=3D"font-family:A=
ptos,Aptos_EmbeddedFont,Aptos_MSFontService,Calibri,Helvetica,sans-serif;fo=
nt-size:11pt;color:rgb(0,0,0)">
Conventional tunneling / prefix delegation approaches</li><li style=3D"font=
-family:Aptos,Aptos_EmbeddedFont,Aptos_MSFontService,Calibri,Helvetica,sans=
-serif;font-size:11pt;color:rgb(0,0,0)">
OMNI-Aero</li></ul>
<div style=3D"margin-top:1em;margin-bottom:1em;font-family:Aptos,Aptos_Embe=
ddedFont,Aptos_MSFontService,Calibri,Helvetica,sans-serif;font-size:11pt;co=
lor:rgb(0,0,0)">
The document is not there yet. That said, MANET internetworking has been th=
e prominent topic in our recent meetings.</div>
<div style=3D"margin-top:1em;margin-bottom:1em;font-family:Aptos,Aptos_Embe=
ddedFont,Aptos_MSFontService,Calibri,Helvetica,sans-serif;font-size:11pt;co=
lor:rgb(0,0,0)">
The purpose of this adoption call is to determine whether there is a broade=
r WG consensus to move forward with this work. It is therefore important to=
 understand whether WG participants support and will contribute reviews and=
 feedback to this work.=C2=A0</div>
<div style=3D"margin-top:1em;margin-bottom:1em;font-family:Aptos,Aptos_Embe=
ddedFont,Aptos_MSFontService,Calibri,Helvetica,sans-serif;font-size:11pt;co=
lor:rgb(0,0,0)">
Please share your views before the call ends on 6 May.=C2=A0</div>
<div style=3D"margin-top:1em;margin-bottom:1em;font-family:Aptos,Aptos_Embe=
ddedFont,Aptos_MSFontService,Calibri,Helvetica,sans-serif;font-size:11pt;co=
lor:rgb(0,0,0)">
Thank you to those that have responded,<br>
Don</div>
<span style=3D"font-size:11pt"><br>
</span>
</div>

_______________________________________________<br>
manet mailing list -- <a href=3D"mailto:[email protected]" target=3D"_blank">m=
[email protected]</a><br>
To unsubscribe send an email to <a href=3D"mailto:[email protected]" tar=
get=3D"_blank">[email protected]</a><br>
</div></blockquote></div>

--000000000000dea45a0651245737--


--===============1496838943248198629==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64
Content-Disposition: inline

X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KbWFuZXQgbWFp
bGluZyBsaXN0IC0tIG1hbmV0QGlldGYub3JnClRvIHVuc3Vic2NyaWJlIHNlbmQgYW4gZW1haWwg
dG8gbWFuZXQtbGVhdmVAaWV0Zi5vcmcK

--===============1496838943248198629==--