Dear authors,
Next to Thomas's points, here is another one.
I see:
5. Exception Templates
This section presents a list of templates for reporting exceptions
using newly proposed IEs in addition to few existing IEs.
I don't think it's a good idea to propose fixed templates in standards.
IPFIX has been created with flexible templates in mind.
In other words, we don't want to relay the message that, in order to be
compliant with the (future) RFC, we have to report the newly defined
IPFIX information elements IN THE EXACT proposed templates.
Regards, Benoit
On 3/12/2021 1:31 PM, [email protected] wrote:
Dear authors,
Speaking as a network operator, I welcome the effort in IPFIX to
improve the drop cause declaration better.
As described, IE89 forwardingStatus covers the following categories
forwarded
dropped
consumed
I understood that the motivation of the draft is to increase the
amount of code points for dropped from 6-bit (according to IANA, 16
code points currently used) to 32-bit and support the enterprise.
From my perspective, it makes sense to support an enterprise bit for
forwarded
dropped
consumed
However, I miss a clear reason of the increase of size. I would
appreciate if you could describe more drop causes which qualifies for
the increase to 32-bit.
I would also to consider to include the existing code points from IE89
in forwardingExceptionCode as well to support a migration path. So a
device does not need to export both.
Further please clarify the need of forwardingNexthopId over existing
entities
IE15 ipNextHopIPv4Address
IE18 bgpNextHopIPv4Address
IE62 ipNextHopIPv6Address
IE63 bgpNextHopIPv6Address
IE47 mplsTopLabelIPv4Address
Best wishes
Thomas
*From:*OPSAWG <[email protected]> *On Behalf Of *Venkata
Chaitanya Munukutla
*Sent:* Monday, February 22, 2021 9:38 PM
*To:* [email protected]
*Subject:* [OPSAWG] Requesting review & feedback -
draft-mvmd-opsawg-ipfix-fwd-exceptions-02
WG,
We recently published a new version of the draft (
https://tools.ietf.org/html/draft-mvmd-opsawg-ipfix-fwd-exceptions-02
<https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Ftools.ietf.org%2Fhtml%2Fdraft-mvmd-opsawg-ipfix-fwd-exceptions-02&data=04%7C01%7CThomas.Graf%40swisscom.com%7Ca4f03da8f61048936eca08d8d771d4fc%7C364e5b87c1c7420d9beec35d19b557a1%7C1%7C0%7C637496231201225710%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=qL61o9f4Px%2FeA1ffRXX1zwALEIlID6WDSy%2BlE2niDSY%3D&reserved=0>
) based on review comments & feedback from IETF 109.
Please do review this draft and let us know your feedback.
--
Title : IP Flow Information Export (IPFIX) Information
Elements Extension for Forwarding Exceptions.
Authors : Chaitanya Munukutla
Shivam Vaid
Aditya Mahale
Devang Patel
Filename : draft-mvmd-opsawg-ipfix-fwd-exceptions-02
Last updated: 2021-02-04
Abstract :
This draft proposes couple of new Forwarding exceptions related
Information Elements (IEs) and Templates for the IP Flow Information
Export (IPFIX) protocol. These new Information Elements and
Exception Template can be used to export information about any
forwarding errors in a network. This essential information is
adequate to correlate packet drops to any control plane entity and
map it to an impacted service. Once exceptions are correlated to a
particular entity, an action can be assigned to mitigate such
problems essentially enabling self-driving networks.
--
The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-mvmd-opsawg-ipfix-fwd-exceptions/
<https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fdraft-mvmd-opsawg-ipfix-fwd-exceptions%2F&data=04%7C01%7CThomas.Graf%40swisscom.com%7Ca4f03da8f61048936eca08d8d771d4fc%7C364e5b87c1c7420d9beec35d19b557a1%7C1%7C0%7C637496231201225710%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=RG68bfLtbxSLNRrVlSNft9%2BuEt%2FsADdKyYUU51GSbfM%3D&reserved=0>
Side-by-side diff from version 00 for this draft is available at:
https://www.ietf.org/rfcdiff?url1=draft-mvmd-opsawg-ipfix-fwd-exceptions-00&url2=draft-mvmd-opsawg-ipfix-fwd-exceptions-02
<https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ietf.org%2Frfcdiff%3Furl1%3Ddraft-mvmd-opsawg-ipfix-fwd-exceptions-00%26url2%3Ddraft-mvmd-opsawg-ipfix-fwd-exceptions-02&data=04%7C01%7CThomas.Graf%40swisscom.com%7Ca4f03da8f61048936eca08d8d771d4fc%7C364e5b87c1c7420d9beec35d19b557a1%7C1%7C0%7C637496231201235669%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=4XCq21S1oQ7B1%2FUgt1AO7FEEPCn3ID6oIC%2FnhwjUiB4%3D&reserved=0>
Regards,
Chaitanya.
Juniper Business Use Only
_______________________________________________
OPSAWG mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/opsawg
_______________________________________________
OPSAWG mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/opsawg
