Re: [Bier] A comment about draft-xzlnp-bier-ioam

Thank you for bringing this work to the discussion.
I have read the draft and got several comments:

   - the IOAM mechanism described in draft-ietf-ippm-ioam-data appears to
   be better suited for p2p flows. When applied in a multicast network, IOAM
   results in unnecessary replication of IOAM data recorded upstream. This can
   be avoided by separating the process of generating telemetry information on
   a node according to the profile in the IOAM header from transporting that
   information to a collector for processing. That can be achieved using the
   IOAM Direct Export mode of IOAM tracing
   <https://datatracker.ietf.org/doc/draft-ioamteam-ippm-ioam-direct-export/>
   , the Hybrid Two-step protocol
   <https://datatracker.ietf.org/doc/draft-mirsky-ippm-hybrid-two-step/>,
   or any other means of transportation.
   - I suggest updating Figure 1. As mentioned above, there are other
   methods of transporting IOAM data rather than in the trigger packet
   immediately following the IOAM Option header. I think that the right tag
   for the field would be "IOAM Option and Optional Data Space".
   Alternatively, the figure may display IOAM Option and IOAM Data Space
   fields separately, noting that the latter is optional.

Regards,
Greg

On Fri, Mar 18, 2022 at 5:56 AM Jeffrey (Zhaohui) Zhang <zzhang=
40juniper.net@dmarc.ietf.org> wrote:

> Hi,
>
> For IOAM data in BIER, I want to point out that we should use a generic
> header format that can be used for BIER/MPLS/IPv6. The same extension
> mechanism can be used for other purposes like fragmentation/security, etc..
>
> This was discussed in
> https://www.ietf.org/archive/id/draft-zzhang-intarea-generic-delivery-functions-02.txt,
> and was mentioned in slide #6 of
> https://datatracker.ietf.org/meeting/112/materials/slides-112-bier-03-bier-slicing-and-differentiation-00
> in IETF112 BIER session.
>
> Thanks.
>
> Jeffrey
>
> Juniper Business Use Only
>
> _______________________________________________
> BIER mailing list
> BIER@ietf.org
> https://www.ietf.org/mailman/listinfo/bier
>