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

Loa Andersson <loa@pi.nu> Sat, 22 August 2020 05:57 UTC

Return-Path: <loa@pi.nu>
X-Original-To: bier@ietfa.amsl.com
Delivered-To: bier@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AA9F53A0DC8 for <bier@ietfa.amsl.com>; Fri, 21 Aug 2020 22:57:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.846
X-Spam-Level:
X-Spam-Status: No, score=-2.846 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.949, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id R_bAQAPEbige for <bier@ietfa.amsl.com>; Fri, 21 Aug 2020 22:57:35 -0700 (PDT)
Received: from pipi.pi.nu (pipi.pi.nu [83.168.239.141]) (using TLSv1.1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 636643A0DC1 for <bier@ietf.org>; Fri, 21 Aug 2020 22:57:34 -0700 (PDT)
Received: from [192.168.1.19] (unknown [122.2.101.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: loa@pi.nu) by pipi.pi.nu (Postfix) with ESMTPSA id 384513279B5; Sat, 22 Aug 2020 07:57:16 +0200 (CEST)
To: Gyan Mishra <hayabusagsm@gmail.com>, "Mankamana Mishra (mankamis)" <mankamis=40cisco.com@dmarc.ietf.org>
Cc: "IJsbrand Wijnands (iwijnand)" <iwijnand=40cisco.com@dmarc.ietf.org>, Greg Shepherd <gjshep@gmail.com>, "bier@ietf.org" <bier@ietf.org>
References: <1E057E92-424E-4456-936C-F8C842340ADB@gmail.com> <9300613D-A740-476E-BC8F-3B0D25C8E883@cisco.com> <223C9348-563A-43DC-B9E3-DE978CA7FA68@cisco.com> <CABNhwV0SGV2nE430f9SeVOe1XSq83ZM5CbwcifPuhFBye-Tj+g@mail.gmail.com>
From: Loa Andersson <loa@pi.nu>
Message-ID: <fe49cb0e-09e4-3274-b374-bf861e132518@pi.nu>
Date: Sat, 22 Aug 2020 13:57:03 +0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.11.0
MIME-Version: 1.0
In-Reply-To: <CABNhwV0SGV2nE430f9SeVOe1XSq83ZM5CbwcifPuhFBye-Tj+g@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/bier/P2Vl8WcvgxT_46N2DV-6LWe3K3U>
Subject: Re: [Bier] WGLC: draft-ietf-bier-php
X-BeenThere: bier@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "\"Bit Indexed Explicit Replication discussion list\"" <bier.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/bier>, <mailto:bier-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/bier/>
List-Post: <mailto:bier@ietf.org>
List-Help: <mailto:bier-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bier>, <mailto:bier-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 22 Aug 2020 05:57:38 -0000

Working Group,

I've had time to read the draft a bit more in detail.

I'm convinced that this will work, and support progressing the draft.

I still think there are some minor description details that could be
improved.

The draft says:

    One way to solve this problem is to use Penultimate Hop Popping (PHP)
    so that the upstream BFR can pop the BIER header and send the payload
    "natively" (note that the upstream BFR can be connected directly or
    indirectly via any type of tunnel to the PE).  This is similar to
    Multi-Protocol Label Switching (MPLS) PHP though it is the BIER
    header that is popped.

This indicate that this is a "per node" decision, while in MPLS it is a
per LSP decision.

I would think that it is possible for one node to be the penultimate
node for some traffic but not for other traffic, even though the traffic 
is sent to the same node, which can be both ultimate node, pen-ultimate
node or transit node.


      +-------+              +-------+          +-------+
      |       |              |       |          |       |
-a,b-+   A   +-----a',b-----+   B   +----a'----+  CPE1 |
      |       |              |       |          |       |
      +-------+              +---+---+          +-------+
                                 |
                                 b'
                                 |
                             +---+---+          +-------+
                             |       |          |       |
                             +   C   +----b'----+  CPE2 |
                             |       |          |       |
                             +---+---+          +-------+


Two streams comes in to A from the left (a and b).

A is the penultimate node for traffic to to CPE1 (a) so the BIER header
is popped.

A is not the  penultimate node for traffic to to CPE2 (b) so the BIER
header is popped.

Both a' and b is sent to B.

B forward a' natively to CPE1.

B is the penultimate node for traffic to to CPE2 (b) so the BIER header
is popped.

b' is forwarded to C and onto CPE2

Works just fine.

Question: If the PHP is a "per node decision" how is A stopped from 
doing PHP for b?

/Loa



On 22/08/2020 05:20, Gyan Mishra wrote:
> 
> 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=40cisco.com@dmarc.ietf.org 
> <mailto:40cisco.com@dmarc.ietf.org>> wrote:
> 
>     Support moving this document forward. ____
> 
>     __ __
> 
>     *From: *BIER <bier-bounces@ietf.org <mailto:bier-bounces@ietf.org>>
>     on behalf of "IJsbrand Wijnands (iwijnand)"
>     <iwijnand=40cisco.com@dmarc.ietf.org
>     <mailto:40cisco.com@dmarc.ietf.org>>
>     *Date: *Monday, August 17, 2020 at 11:56 AM
>     *To: *Greg Shepherd <gjshep@gmail.com <mailto:gjshep@gmail.com>>
>     *Cc: *"bier@ietf.org <mailto:bier@ietf.org>" <bier@ietf.org
>     <mailto:bier@ietf.org>>
>     *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 <gjshep@gmail.com
>         <mailto:gjshep@gmail.com>> 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
>         BIER@ietf.org <mailto:BIER@ietf.org>
>         https://www.ietf.org/mailman/listinfo/bier____
> 
>     _______________________________________________
>     BIER mailing list
>     BIER@ietf.org <mailto:BIER@ietf.org>
>     https://www.ietf.org/mailman/listinfo/bier
> 
> 
> 
> -- 
> 
> <http://www.verizon.com/>
> 
> *Gyan Mishra*
> 
> /Network Solutions A//rchitect /
> 
> /M 301 502-1347
> 13101 Columbia Pike
> /Silver Spring, MD
> 
> 
> 
> _______________________________________________
> BIER mailing list
> BIER@ietf.org
> https://www.ietf.org/mailman/listinfo/bier
> 

-- 

Loa Andersson                        email: loa@pi.nu
Senior MPLS Expert                          loa.pi.nu@gmail.com
Bronze Dragon Consulting             phone: +46 739 81 21 64