[ippm] Re: Joint BMWG/IPPM chartering - implementation polic y

Ruediger.Geib=40telekom.de-Tr9gZwTxerDR74oF6e/[email protected] Mon, 11 May 2026 11:00:10 +0000
Newsgroups gmane.ietf.ippm,gmane.ietf.bmwg
Message-ID <BEZP281MB200760AB3E02BCCED36B5F219C382@BEZP281MB2007.DEUP281.PROD.OUTLOOK.COM>
--===============8904524500475948475==
Content-Language: de-DE
Content-Type: multipart/alternative;
 boundary="_000_BEZP281MB200760AB3E02BCCED36B5F219C382BEZP281MB2007DEUP_"

--_000_BEZP281MB200760AB3E02BCCED36B5F219C382BEZP281MB2007DEUP_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Dear Marcus, Giuseppe, Sarah and Thomas,

I'd prefer option 1. A "SHOULD" requirement for an implementation to me wou=
ld be a clear expression of the WG intent and implicitly include/allow an e=
xception.

Regards,

Ruediger

Von: Thomas.Graf-Zc0CTiu5wcBWk0Htik3J/[email protected] <Thomas.Graf-Zc0CTiu5wcBWk0Htik3J/[email protected]>
Gesendet: Donnerstag, 7. Mai 2026 10:13
An: [email protected]; [email protected]
Cc: [email protected]; [email protected]; [email protected]=
m
Betreff: [ippm] Joint BMWG/IPPM chartering - implementation policy

Dear BMWG and IPPM,

We have with https://github.com/ietf-ippm/wg-charter/issues/4 a suggestion =
from Med to consider adding an implementation policy in the join charter pr=
oposal.

We chairs have been thinking how this could be addressed best in the charte=
r and came up with the 3 proposals:


  1.  The WG prioritizes documents with implementations.
  2.  The WG requires an implementation for standard track documents. In so=
me cases exceptions can be applied. Whenever such an exception applies, the=
 exception justification must be included in the specification document or =
its write-up.
  3.  The WG requires two implementations for standard track documents. In =
some cases exceptions can be applied. Whenever such an exception applies, t=
he exception justification must be included in the specification document o=
r its write-up.

The main differences between the choices are underlined.

We would like to have feedback from both working groups on


  *   wherever an implementation policy should be added or not
  *   wherever those choices make sense or not
  *   which would be the preferred choice and why

https://datatracker.ietf.org/doc/html/rfc7942 is a good quick read in regar=
ds to implementations and implementation status section. Rough consensus an=
d running code is part of the IETF DNA. Personally we think it is helpful f=
or the authors if the working group states what is expected in terms of imp=
lementations. There are good reasons for having implementations such as rai=
sing quality of the document and ensure interoperability. But there are als=
o reasons to progress quickly. For instance in case where there is only a s=
mall document update or a security fix.

Best wishes
Marcus, Giuseppe, Sarah and Thomas








--_000_BEZP281MB200760AB3E02BCCED36B5F219C382BEZP281MB2007DEUP_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-=
1">
<meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Aptos;}
@font-face
	{font-family:"Trebuchet MS";
	panose-1:2 11 6 3 2 2 2 2 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	font-size:12.0pt;
	font-family:"Aptos",sans-serif;
	mso-ligatures:standardcontextual;
	mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:#467886;
	text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0cm;
	margin-right:0cm;
	margin-bottom:0cm;
	margin-left:36.0pt;
	font-size:12.0pt;
	font-family:"Aptos",sans-serif;
	mso-ligatures:standardcontextual;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;
	mso-ligatures:none;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:70.85pt 70.85pt 2.0cm 70.85pt;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:800534661;
	mso-list-template-ids:1469875574;}
@list l0:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:36.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l0:level2
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:72.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l0:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:108.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l0:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:144.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l0:level5
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:180.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l0:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:216.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l0:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:252.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l0:level8
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:288.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l0:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:324.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l1
	{mso-list-id:975447377;
	mso-list-type:hybrid;
	mso-list-template-ids:1167606882 134676495 134676505 134676507 134676495 1=
34676505 134676507 134676495 134676505 134676507;}
@list l1:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l1:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l1:level3
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l1:level4
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l1:level5
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l1:level6
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l1:level7
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l1:level8
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l1:level9
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l2
	{mso-list-id:1638027413;
	mso-list-template-ids:1373424886;}
@list l3
	{mso-list-id:2084600692;
	mso-list-type:hybrid;
	mso-list-template-ids:-1489231030 -1834830122 134676483 134676485 13467648=
1 134676483 134676485 134676481 134676483 134676485;}
@list l3:level1
	{mso-level-start-at:3;
	mso-level-number-format:bullet;
	mso-level-text:\F0D8;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Wingdings;
	mso-fareast-font-family:Aptos;
	mso-bidi-font-family:"Times New Roman";}
@list l3:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:"Courier New";}
@list l3:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Wingdings;}
@list l3:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Symbol;}
@list l3:level5
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:"Courier New";}
@list l3:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Wingdings;}
@list l3:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Symbol;}
@list l3:level8
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:"Courier New";}
@list l3:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Wingdings;}
ol
	{margin-bottom:0cm;}
ul
	{margin-bottom:0cm;}
--></style>
</head>
<body lang=3D"DE" link=3D"#467886" vlink=3D"#96607D" style=3D"word-wrap:bre=
ak-word">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span lang=3D"EN-US">Dear Marcus, Giuseppe, Sarah an=
d Thomas,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">I&#8217;d prefer option 1. A &#=
8220;SHOULD&#8221; requirement for an implementation to me would be a clear=
 expression of the WG intent and implicitly include/allow an exception.
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Regards,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Ruediger<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<div>
<div style=3D"border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal"><b><span style=3D"font-size:11.0pt;font-family:&quot=
;Calibri&quot;,sans-serif;mso-ligatures:none;mso-fareast-language:DE">Von:<=
/span></b><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,s=
ans-serif;mso-ligatures:none;mso-fareast-language:DE"> Thomas.Graf@swisscom=
.com
 &lt;Thomas.Graf-Zc0CTiu5wcBWk0Htik3J/[email protected]&gt; <br>
<b>Gesendet:</b> Donnerstag, 7. Mai 2026 10:13<br>
<b>An:</b> [email protected]; [email protected]<br>
<b>Cc:</b> [email protected]; [email protected]; mohamed.boucadair@or=
ange.com<br>
<b>Betreff:</b> [ippm] Joint BMWG/IPPM chartering - implementation policy<o=
:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><span lang=3D"DE-CH" style=3D"font-size:10.0pt;font-=
family:&quot;Trebuchet MS&quot;,sans-serif">Dear BMWG and IPPM,<o:p></o:p><=
/span></p>
<p class=3D"MsoNormal"><span lang=3D"DE-CH" style=3D"font-size:10.0pt;font-=
family:&quot;Trebuchet MS&quot;,sans-serif"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Trebuchet MS&quot;,sans-serif">We have with
</span><span lang=3D"DE-CH" style=3D"font-size:10.0pt;font-family:&quot;Tre=
buchet MS&quot;,sans-serif"><a href=3D"https://github.com/ietf-ippm/wg-char=
ter/issues/4"><span lang=3D"EN-US">https://github.com/ietf-ippm/wg-charter/=
issues/4</span></a>
</span><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Tre=
buchet MS&quot;,sans-serif">a suggestion from Med to consider adding an imp=
lementation policy in the join charter proposal.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Trebuchet MS&quot;,sans-serif"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Trebuchet MS&quot;,sans-serif">We chairs have been thinking ho=
w this could be addressed best in the charter and came up with the 3 propos=
als:<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Trebuchet MS&quot;,sans-serif"><o:p>&nbsp;</o:p></span></p>
<ol style=3D"margin-top:0cm" start=3D"1" type=3D"1">
<li class=3D"MsoListParagraph" style=3D"margin-left:0cm;mso-list:l1 level1 =
lfo3"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Treb=
uchet MS&quot;,sans-serif">The WG
<u>prioritizes</u> documents with implementations.<o:p></o:p></span></li><l=
i class=3D"MsoListParagraph" style=3D"margin-left:0cm;mso-list:l1 level1 lf=
o3"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Trebuc=
het MS&quot;,sans-serif">The WG
<u>requires an</u> implementation for standard track documents. In some cas=
es exceptions can be applied. Whenever such an exception applies, the excep=
tion justification must be included in the specification document or its wr=
ite-up.<o:p></o:p></span></li><li class=3D"MsoListParagraph" style=3D"margi=
n-left:0cm;mso-list:l1 level1 lfo3"><span lang=3D"EN-US" style=3D"font-size=
:10.0pt;font-family:&quot;Trebuchet MS&quot;,sans-serif">The WG
<u>requires two</u> implementations for standard track documents. In some c=
ases exceptions can be applied. Whenever such an exception applies, the exc=
eption justification must be included in the specification document or its =
write-up.<o:p></o:p></span></li></ol>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Trebuchet MS&quot;,sans-serif"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Trebuchet MS&quot;,sans-serif">The main differences between th=
e choices are underlined.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Trebuchet MS&quot;,sans-serif"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Trebuchet MS&quot;,sans-serif">We would like to have feedback =
from both working groups on<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Trebuchet MS&quot;,sans-serif"><o:p>&nbsp;</o:p></span></p>
<ul style=3D"margin-top:0cm" type=3D"disc">
<li class=3D"MsoListParagraph" style=3D"margin-left:0cm;mso-list:l3 level1 =
lfo6"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Treb=
uchet MS&quot;,sans-serif">wherever an implementation policy should be adde=
d or not<o:p></o:p></span></li><li class=3D"MsoListParagraph" style=3D"marg=
in-left:0cm;mso-list:l3 level1 lfo6"><span lang=3D"EN-US" style=3D"font-siz=
e:10.0pt;font-family:&quot;Trebuchet MS&quot;,sans-serif">wherever those ch=
oices make sense or not<o:p></o:p></span></li><li class=3D"MsoListParagraph=
" style=3D"margin-left:0cm;mso-list:l3 level1 lfo6"><span lang=3D"EN-US" st=
yle=3D"font-size:10.0pt;font-family:&quot;Trebuchet MS&quot;,sans-serif">wh=
ich would be the preferred choice and why<o:p></o:p></span></li></ul>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Trebuchet MS&quot;,sans-serif"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Trebuchet MS&quot;,sans-serif"><a href=3D"https://datatracker.=
ietf.org/doc/html/rfc7942">https://datatracker.ietf.org/doc/html/rfc7942</a=
> is a good quick read in regards to implementations
 and implementation status section. Rough consensus and running code is par=
t of the IETF DNA. Personally we think it is helpful for the authors if the=
 working group states what is expected in terms of implementations. There a=
re good reasons for having implementations
 such as raising quality of the document and ensure interoperability. But t=
here are also reasons to progress quickly. For instance in case where there=
 is only a small document update or a security fix.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Trebuchet MS&quot;,sans-serif"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Trebuchet MS&quot;,sans-serif">Best wishes<o:p></o:p></span></=
p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Trebuchet MS&quot;,sans-serif">Marcus, Giuseppe, Sarah and Tho=
mas</span><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;=
Trebuchet MS&quot;,sans-serif;color:gray;mso-ligatures:none;mso-fareast-lan=
guage:DE-CH"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Trebuchet MS&quot;,sans-serif"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Trebuchet MS&quot;,sans-serif"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Trebuchet MS&quot;,sans-serif"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Trebuchet MS&quot;,sans-serif"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Trebuchet MS&quot;,sans-serif"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Trebuchet MS&quot;,sans-serif"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
</div>
</body>
</html>

--_000_BEZP281MB200760AB3E02BCCED36B5F219C382BEZP281MB2007DEUP_--


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

X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KaXBwbSBtYWls
aW5nIGxpc3QgLS0gaXBwbUBpZXRmLm9yZwpUbyB1bnN1YnNjcmliZSBzZW5kIGFuIGVtYWlsIHRv
IGlwcG0tbGVhdmVAaWV0Zi5vcmcK

--===============8904524500475948475==--