[IPFIX]Re: [Editorial Errata Reported] RFC7011 (8313)

[[e-mail]]

Hi all,

Interesting example, Andrew.

Putting aside the use of PEN as a hack, the approach in 5103 does not change the rules set in 7011 for picking ids. Of course, there is a 1:1 mapping convention set in 5103 but that is specific to that PEN.

More importantly, RFC 5103 is explicit that:

   The allocation of enterprise-specific Information Elements for IPFIX
   is left to the discretion of the organization allocating them.

Cheers,
Med

> -----Message d'origine-----
> De : Andrew Feren <[e-mail]>
> Envoyé : mercredi 26 février 2025 01:49
> À : Benoit Claise <benoit.claise=[e-mail]>
> Cc : Errata System RFC <[e-mail]>; BOUCADAIR Mohamed
> INNOV/NET <[e-mail]>; [e-mail];
> [e-mail]; [e-mail]; [e-mail]
> Objet : Re: [IPFIX]Re: [Editorial Errata Reported] RFC7011 (8313)
> 
> 
> What about RFC 5103 IEs?
> 
> -Andrew
> 
> > On Feb 25, 2025, at 07:37, Benoit Claise
> <benoit.claise=[e-mail]> wrote:
> >
> > [EXTERNAL] CAUTION: This email originated from outside of the
> organization. Do not click links or open attachments unless you
> recognize the sender and know the content is safe.
> >
> >
> > Dear all,
> >
> > Med is right in his thinking. We could have more precise with the
> > specifications.
> >
> > Whether this errata is Verified or Hold for Document Update, I
> > personally don't believe it's important as IMO this was never an
> issue
> > in collector implementations.
> >
> > Regards, Benoit
> >
> >
> >> On 2/25/2025 2:13 PM, RFC Errata System wrote:
> >> The following errata report has been submitted for RFC7011,
> >> "Specification of the IP Flow Information Export (IPFIX) Protocol
> for the Exchange of Flow Information".
> >>
> >> --------------------------------------
> >> You may review the report below and at:
> >>
> https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww
> >> .rfc-
> editor.org%2Ferrata%2Feid8313&data=05%7C02%7Cmohamed.boucadair%4
> >>
> 0orange.com%7C33f2dce3ac3940559c3b08dd55ff5961%7C90c7a20af34b40bfbc48
> >>
> b9253b6f5d20%7C0%7C0%7C638761277394861702%7CUnknown%7CTWFpbGZsb3d8eyJ
> >>
> FbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFp
> >>
> bCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=uj7n6bfyU6kxSke3LXDmTNzcS2mqp
> >> 1kgPXkXKZU423g%3D&reserved=0
> >>
> >> --------------------------------------
> >> Type: Editorial
> >> Reported by: Mohamed Boucadair <[e-mail]>
> >>
> >> Section: 3.2
> >>
> >> Original Text
> >> -------------
> >>    E
> >>
> >>       Enterprise bit.  This is the first bit of the Field
> Specifier.  If
> >>       this bit is zero, the Information Element identifier
> identifies an
> >>       Information Element in [IANA-IPFIX], and the four-octet
> Enterprise
> >>       Number field MUST NOT be present.  If this bit is one, the
> >>       Information Element identifier identifies an enterprise-
> specific
> >>       Information Element, and the Enterprise Number field MUST be
> >>       present.
> >>
> >>    Information Element identifier
> >>
> >>       A numeric value that represents the Information Element.
> Refer to
> >>       [IANA-IPFIX].
> >>
> >> Corrected Text
> >> --------------
> >>    E
> >>
> >>       Enterprise bit.  This is the first bit of the Field
> Specifier.  If
> >>       this bit is zero, the Information Element identifier
> identifies an
> >>       Information Element in [IANA-IPFIX], and the four-octet
> Enterprise
> >>       Number field MUST NOT be present.  If this bit is one, the
> >>       Information Element identifier identifies an enterprise-
> specific
> >>       Information Element, and the Enterprise Number field MUST be
> >>       present.
> >>
> >>    Information Element identifier
> >>
> >>       A numeric value that represents the Information Element. This
> field
> >>       takes a value in [IANA-IPFIX] when the E bit is set to zero.
> >>
> >> Notes
> >> -----
> >> Makes it explicit that the values in [IANA-IPFIX] only applies when
> the is E-bit is unset.
> >>
> >> An alternative would be to simply delete "Refer to [IANA-IPFIX]."
> as the exact behavior is already mentioned under the E bit
> description.
> >>
> >> Instructions:
> >> -------------
> >> This erratum is currently posted as "Reported". (If it is spam, it
> >> will be removed shortly by the RFC Production Center.) Please use
> >> "Reply All" to discuss whether it should be verified or rejected.
> >> When a decision is reached, the verifying party will log in to
> change
> >> the status and edit the report, if necessary.
> >>
> >> --------------------------------------
> >> RFC7011 (draft-ietf-ipfix-protocol-rfc5101bis-10)
> >> --------------------------------------
> >> Title               : Specification of the IP Flow Information
> Export (IPFIX) Protocol for the Exchange of Flow Information
> >> Publication Date    : September 2013
> >> Author(s)           : B. Claise, Ed., B. Trammell, Ed., P. Aitken
> >> Category            : INTERNET STANDARD
> >> Source              : IP Flow Information Export
> >> Stream              : IETF
> >> Verifying Party     : IESG
> >>
> >> _______________________________________________
> >> IPFIX mailing list -- [e-mail]
> >> To unsubscribe send an email to [e-mail]
> >
> > _______________________________________________
> > IPFIX mailing list -- [e-mail]
> > To unsubscribe send an email to [e-mail]
> This email message and any attachments are confidential. If you are
> not the intended recipient, please immediately reply to the sender and
> delete the message from your email system. Thank you.
____________________________________________________________________________________________________________
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.