Re: [Bier] WGLC: draft-ietf-bier-php

[Gyan Mishra <[e-mail]>]

Thanks Jingrong for the graphical depiction of BIERv6 PSP and how it would
work.

The pop/delete in MPLS or SR-MPLS construct with MPLS-BIER we have the BIER
 L2.5 shim to be popped so BIERin6 pop is similar to MPLS PHP as we have a
L2.5 shim to be popped similar to MPLS shim.

With BIERv6 native encoding in DOH was not sure how it would be popped.
Looking at it further the SRv6 construct its PSP POP/Delete very similar to
SRV6 SRH PSP pop.  Makes sense DOH PSP is similar to SRH PSP.

Yes I remember all the many threads on 6MAN and in flight eh insertion or
removal violation of RFC 8200 contentious debate.

I agree that PSP would be beneficial for supporting Non BFR capable PEs and
agree with the behavior makes sense that the entire DOH would get popped
removed.

Thanks

Gyan

On Mon, Aug 24, 2020 at 3:30 AM Xiejingrong (Jingrong) <
[e-mail]> wrote:

>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> Hi Gyan,
>
>
>
>
>
> Thanks for raising the PHP consideration in v6.
>
>
>
>
>
> There is a thorough discussion in IETF community, especially 6man,  about
> Penultimate Segment Pop (PSP) ---- to Pop an EH when an IPv6 packet with
>
> EH reaches the node identified in the destination address [RFC8200 section
> 4].
>
>
> This thorough discussion has led to a wide consensus among IETF community,
> and led to the progress of draft-ietf-spring-srv6-network-programming-17
>
> to IETF last call.
>
>
>
>
>
> So for BIERv6, I think the PSP can be very well supported to provide
> incremental deployment for Non-BIER-capable PEs.
>
>
>
>
>
>
> Note, the whole DoH (not only the BIER option data) is popped/deleted when
> the BIERv6 packet is sent to the ultimate PE. Here is a diagram:
>
>
>
>
>
> CE1----A----B----C----D----CE2
>
>
>
>
>
> A is BFIR, D is Non-BFR router but acting as a BFER requesting PSP
> (signaling defined in draft-ietf-bier-php), and both B and C are BFRs
> (could be
>
> BFERs at the same time).
>
>
>
>
>
> Packet from A to B: (IPv6 SA=A, DA=B) (DoH carrying BIER) (c-multicast
> packet).
>
>
> Packet from B to C: (IPv6 SA=A, DA=C) (DoH carrying BIER) (c-multicast
> packet).
>
>
> Packet from C to D: (IPv6 SA=A, DA=D) (c-multicast packet).
>
>
>
>
>
>
> Thanks
>
>
> Jingrong
>
>
>
>
>
> *From:* BIER [mailto:[e-mail]]
>
> *On Behalf Of *Gyan Mishra
>
>
> *Sent:* Saturday, August 22, 2020 5:21 AM
>
>
> *To:* Mankamana Mishra (mankamis) <mankamis=[e-mail]>
>
>
> *Cc:* IJsbrand Wijnands (iwijnand) <iwijnand=[e-mail]>;
> Greg Shepherd <[e-mail]>; [e-mail]
>
>
> *Subject:* Re: [Bier] WGLC: draft-ietf-bier-php
>
>
>
>
>
>
>
>
>
>
>
>
> I support advancing this critical draft forward.  I agree that the PHP
> feature traditionally used with MPLS and has been adopted by SR and now by
> BIER for similar reasons of being able to pop the BIER header similar to
>
> what is done with SR PHP concept and now extensible with BIER for Non-BRF
> capable PE's.
>
>
>
>
>
>
>
>
>
>
>
>
>
> BIER IPv6 is still being developed, however I think maybe BIERin6 could
> take advantage of  PHP by popping the encapsulated L2 1/2 BIER shim for
> "Non-BFR" capable PE.  I think for BIERv6 as the BIER header is encoded in
>
> DOH it may be difficult to support PHP.
>
>
>
>
>
>
>
>
>
>
>
>
>
> Thanks
>
>
>
>
>
>
>
>
>
>
>
>
>
> Gyan
>
>
>
>
>
>
>
>
>
>
>
>
>
> On Wed, Aug 19, 2020 at 2:01 PM Mankamana Mishra (mankamis) <mankamis=
> [e-mail]> wrote:
>
>
>
>
>
>
>
>
>
>
> Support moving this document forward.
>
>
>
>
>
>
>
>
>
>
> *From:*BIER <[e-mail]> on behalf of "IJsbrand Wijnands
> (iwijnand)" <iwijnand=[e-mail]>
>
>
> *Date: *Monday, August 17, 2020 at 11:56 AM
>
>
> *To: *Greg Shepherd <[e-mail]>
>
>
> *Cc: *"[e-mail]" <[e-mail]>
>
>
> *Subject: *Re: [Bier] WGLC: draft-ietf-bier-php
>
>
>
>
>
>
>
>
>
>
>
> In support moving this draft forward,
>
>
>
>
>
>
>
>
>
>
>
>
> Thx,
>
>
>
>
>
>
>
>
>
>
>
>
>
> Ice.
>
>
>
>
> Sent from my iPhone
>
>
>
>
>
>
>
>
>
>
>
> On 13 Aug 2020, at 05:31, Greg Shepherd <[e-mail]> wrote:
>
>
>
>
>
>
>
>
>
>
>
>
>
> Please read and respond to this thread. We had a WGLC for this draft
> previously, but had no response. Let’s do better.
>
>
>
>
>
>
>
>
>
>
>
>
> https://datatracker.ietf.org/doc/draft-ietf-bier-php/
>
>
>
>
>
>
>
>
>
>
>
>
>
> Start of short LC timer. Respond by Aug 19..
>
>
>
>
>
>
>
>
>
>
>
>
>
> - Shep
>
>
>
>
>
>
> (Chairs)
>
>
>
>
> _______________________________________________
>
>
> BIER mailing list
>
>
> [e-mail]
>
>
> https://www.ietf.org/mailman/listinfo/bier
>
>
>
>
>
>
>
>
>
>
>
>
> _______________________________________________
>
>
> BIER mailing list
>
>
> [e-mail]
>
>
> https://www.ietf.org/mailman/listinfo/bier
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> --
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> <https://www.google.com/maps/search/13101+Columbia+Pike+%0D%0A+Silver+Spring,+MD?entry=gmail&source=g>
>
>
>
>
> [image: 图像已被发件人删除。] <http://www.verizon.com/>
>
>
> *Gyan Mishra*
>
>
> *Network Solutions Architect *
>
>
>
>
>
>
>
>
> *M 301 502-134713101 Columbia Pike
> <https://www.google.com/maps/search/13101+Columbia+Pike+%0D%0A+Silver+Spring,+MD?entry=gmail&source=g> *Silver
> Spring, MD
> <https://www.google.com/maps/search/13101+Columbia+Pike+%0D%0A+Silver+Spring,+MD?entry=gmail&source=g>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> --

<http://www.verizon.com/>

*Gyan Mishra*

*Network Solutions A**rchitect *



*M 301 502-134713101 Columbia Pike *Silver Spring, MD