[ippm] R: R: [EXT] WG adoption call for RFC8321bis and 8889bis

[Cociglio Mauro <[e-mail]>]

Hi Zhenqiang.
Sorry for the late answer but I was away for the Easter holidays.
There isn't much public documentation about Telecom Italia/TIM Alternate Marking implementations.
In this paper there is chapter about our"home-made"solution:
https://ieeexplore.ieee.org/document/8782889.
For the more advanced aspects of our implementations, on the other hand, the only public documents are the theses of the Polytechnic of Turin carried out on behalf of our company.
Here are some of the most significant:
https://webthesis.biblio.polito.it/14519/
https://webthesis.biblio.polito.it/16732/
https://webthesis.biblio.polito.it/20417/
https://webthesis.biblio.polito.it/21241/
Best regards.
Mauro






TIM - Uso Interno - Tutti i diritti riservati.
Da: [e-mail] <[e-mail]>
Inviato: venerdì 15 aprile 2022 13:01
A: Cociglio Mauro <[e-mail]>; Tommy Pauly <[e-mail]>; ippm <[e-mail]>
Oggetto: Re: [ippm] R: [EXT] WG adoption call for RFC8321bis and 8889bis

Hello Mauro,

I am Zhenqiang Li from China Mobile. I'm interested in the solutions and considering if it is possible to test them in our network. Could you please give more information about your application including the network situation, metrics monitered in your network, the methods used and the results etc. Thank you very much.


________________________________
Best Regards,
Zhenqiang Li

[e-mail]<mailto:[e-mail]>

From: Cociglio Mauro<mailto:mauro.cociglio=[e-mail]>
Date: 2022-04-12 16:54
To: Tommy Pauly<mailto:tpauly=[e-mail]>; IETF IPPM WG<mailto:[e-mail]>
Subject: [ippm] R: [EXT] WG adoption call for RFC8321bis and 8889bis
Hello IPPM.
I support as coauthor these drafts.
Telecom Italia/TIM uses these performance monitoring techniques within its networks.
BR.
Mauro
_____________________
Mauro Cociglio
Telecom Italia/TIM
Via G. Reiss Romoli, 274
10148 - Torino (Italy)
Tel.: [phone]
Mobile: [phone]
_____________________




TIM - Uso Interno - Tutti i diritti riservati.
Da: ippm <[e-mail]<mailto:[e-mail]>> Per conto di Tommy Pauly
Inviato: venerdì 8 aprile 2022 02:04
A: IETF IPPM WG <[e-mail]<mailto:[e-mail]>>
Oggetto: [EXT] [ippm] WG adoption call for RFC8321bis and 8889bis

Hello IPPM,

This email starts an adoption call for draft-fioccola-rfc8321bis and draft-fioccola-rfc8889bis. Please see Martin's emails below for details - the main idea here is that we're moving two IPPM RFCs from Experimental to Proposed Standard.

The chairs would like to have a short amount of time spent in the WG processing these documents. If we adopt, we'd plan to very shortly thereafter do a working group last call.

Please reply to this email by Thursday, April 21 and indicate if you support adopting this document.

Best,
Tommy & Marcus

On Apr 7, 2022, at 1:16 PM, Martin Duke <[e-mail]<mailto:[e-mail]>> wrote:

Hello IPPM,

You may recall that there was a need to progress RFC8321 and RFC8889 from Experimental to Proposed Standard. There was a feeling that the update would be trivial and we could therefore do it as an AD sponsored document.

I've done 3 rounds of AD review and I've seen the need to substantially adjust the scope of these documents and tweak the design in places. The changes are not revolutionary, but I'm a non-practitioner and have driven some design changes with minimal review. At this point I think it's important to get good IPPM review; if we're going to do that anyway, we might as well do the (expedited) working group process so that there's no confusion as to why IPPM didn't formally review an update to its own documents.

So, as first step, I invite the working group to adopt these two drafts:
https://datatracker.ietf.org/doc/draft-fioccola-rfc8321bis/
https://datatracker.ietf.org/doc/draft-fioccola-rfc8889bis/
Any objections to adoption, as always, should be to the value of doing the work at all, and the general direction of the drafts. I hope to follow up the adoption call with an immediate WGLC to shake out any detailed objections, though we will take as long as we need to address concerns that people have.

I invite you to consult the changelogs on both of these documents, which are not long, to get a sense of what we've done.

For those of you who like diffs, there was a big reorganization between draft-02 and -03 that is hard to follow in a diff. So here is a set of diffs that exclude the -02 to -03 transition:
https://www.ietf.org/rfcdiff?url1=rfc8321.txt&url2=draft-fioccola-rfc8321bis-02.txt
https://www.ietf.org/rfcdiff?url1=draft-fioccola-rfc8321bis-03.txt&url2=draft-fioccola-rfc8321bis-04.txt

https://www.ietf.org/rfcdiff?url1=rfc8889.txt&url2=draft-fioccola-rfc8889bis-02.txt
https://www.ietf.org/rfcdiff?url1=draft-fioccola-rfc8889bis-03.txt&url2=draft-fioccola-rfc8889bis-04.txt

I believe it's up to the chairs to start the adoption call. If people are good about reading the document during WGLC, I would like to think we could be done before IETF 114.

Your friendly Area Director,
Martin

_______________________________________________
ippm mailing list
[e-mail]<mailto:[e-mail]>
https://www.ietf.org/mailman/listinfo/ippm


________________________________
[https://risorse.tim.it/content/dam/flytoco-areapubblica-aemfe/tim_it/dem-assets/email_footer/banner-mail-tim-magnifica-mobile.png]<https://on.tim.it/banner-mail-dip>
Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie.



This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks.



Rispetta l'ambiente. Non stampare questa mail se non è necessario.