Hi all, 

This draft is triggered by the discussion with Thomas and Benoît and my review 
of draft-tgraf-opsawg-ipfix-srv6-srh. I'm ccing the authors of RFC7125, FWIW. I 
mistakenly set the track to std instead of info (to be consistent with 7125). 

I hope we won't repeat the same issues in the currently discussed draft in 
OPSAWG. 

Cheers,
Med

-----Message d'origine-----
De : internet-dra...@ietf.org <internet-dra...@ietf.org> 
Envoyé : mardi 20 septembre 2022 10:25
À : BOUCADAIR Mohamed INNOV/NET <mohamed.boucad...@orange.com>
Objet : New Version Notification for 
draft-boucadair-opsawg-rfc7125-update-00.txt


A new version of I-D, draft-boucadair-opsawg-rfc7125-update-00.txt
has been successfully submitted by Mohamed Boucadair and posted to the IETF 
repository.

Name:           draft-boucadair-opsawg-rfc7125-update
Revision:       00
Title:          An Update to the tcpControlBits IP Flow Information Export 
(IPFIX) Information Element
Document date:  2022-09-20
Group:          Individual Submission
Pages:          6
URL:            
https://www.ietf.org/archive/id/draft-boucadair-opsawg-rfc7125-update-00.txt
Status:         
https://datatracker.ietf.org/doc/draft-boucadair-opsawg-rfc7125-update/
Htmlized:       
https://datatracker.ietf.org/doc/html/draft-boucadair-opsawg-rfc7125-update


Abstract:
   RFC 7125 revised the tcpControlBits IP Flow Information Export
   (IPFIX) Information Element that was originally defined in RFC 5102
   to reflect changes to the TCP Flags header field since RFC 793.
   However, that update is still problematic for interoperability
   because some values were deprecated since then.

   This document updates RFC 7125 by removing stale information from the
   IPFIX registry and avoiding conflicts with the authoritative TCP
   registry.

                                                                                
  


The IETF Secretariat



_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations 
confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce 
message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou 
falsifie. Merci.

This message and its attachments may contain confidential or privileged 
information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete 
this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been 
modified, changed or falsified.
Thank you.

_______________________________________________
OPSAWG mailing list
OPSAWG@ietf.org
https://www.ietf.org/mailman/listinfo/opsawg

Reply via email to