Re-,
Please see inline.
Cheers,
Med
De : Aitken, Paul <pait...@ciena.com>
Envoyé : mardi 23 janvier 2024 11:26
À : BOUCADAIR Mohamed INNOV/NET <mohamed.boucad...@orange.com>; Joe Clarke
(jclarke) <jcla...@cisco.com>; opsawg@ietf.org
Cc : t...@ietf.org; ts...@ietf.org; 6...@ietf.org; ip...@ietf.org
Objet : Re: [**EXTERNAL**] RE: [IPFIX] WG LC: IPFIX documents
Med,
The following drawing indicates
the position of each bit in the encoding of the Information
Element.
No, not any more - so this should be removed.
[Med] It is useful as it indicates the bit position that is then referred to in
the new IANA registry. Updated the figure to make that clearer.
The previous drawing indicated the positions of specific bits. The new drawing
does not indicate the position of any of the bits:
0 1 2 3 4 5 6 7
+-----+-----+-----+-----+-----+-----+-----+-----+
| IPv6 extension header bits | ...
+-----+-----+-----+-----+-----+-----+-----+-----+
[Med] Please see the new drawing at
https://boucadair.github.io/simple-ipfix-fixes/draft-ietf-opsawg-ipfix-fixes.html
This IE is used only when the observed extension headers are in
the 0-31 range.
Consider deprecating this IE in favour of ipv6ExtensionHeadersFull.
[Med] Seems reasonable, but would like to hear more from the WG.
It would be worth proposing the deprecations in a separate email thread,
because I can't imagine anyone else is following in sufficient detail.
[Med] Fair enough.
4.3. forwardingStatus
In particular, the registered Abstract
Data Type is unsigned8, while it must be unsigned32.
Why must it be?
[Med] As per the definition in RFC7270.
I've opened an errata for that: https://www.rfc-editor.org/errata/eid7775
[Med] I don' think an erratum applies here because the intent of 7270 is
clearly unsigned32:
Description:
This Information Element describes the forwarding status of the
flow and any attached reasons. The reduced-size encoding rules as
per [RFC7011<https://www.rfc-editor.org/rfc/rfc7011>] apply.
The basic encoding is 8 bits. The future extensions
could add one or three bytes. The layout of the basic
encoding is as follows:
6.10. natType
Please take the opportunity to add the missing description, eg "This element
identifies the type of NAT applied to packets of the flow."
[Med] Thanks. Went for: « This Information Element identifies the NAT type
applied to packets of the Flow.".
Thanks; that looks good.
P.
____________________________________________________________________________________________________________
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
