Re: [Bier] BIER v6 requirements draft comments: draft-ietf-bier-ipv6-requirements ...

"Xiejingrong (Jingrong)" <xiejingrong@huawei.com> Fri, 22 November 2019 10:02 UTC

Return-Path: <xiejingrong@huawei.com>
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 85D62120907 for <bier@ietfa.amsl.com>; Fri, 22 Nov 2019 02:02:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable 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 Shw8ijoGsLYm for <bier@ietfa.amsl.com>; Fri, 22 Nov 2019 02:01:59 -0800 (PST)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E6A52120899 for <bier@ietf.org>; Fri, 22 Nov 2019 02:01:58 -0800 (PST)
Received: from lhreml704-cah.china.huawei.com (unknown [172.18.7.108]) by Forcepoint Email with ESMTP id E4CB39A40EDC4D5B7758; Fri, 22 Nov 2019 10:01:56 +0000 (GMT)
Received: from lhreml703-chm.china.huawei.com (10.201.108.52) by lhreml704-cah.china.huawei.com (10.201.108.45) with Microsoft SMTP Server (TLS) id 14.3.408.0; Fri, 22 Nov 2019 10:01:56 +0000
Received: from lhreml703-chm.china.huawei.com (10.201.108.52) by lhreml703-chm.china.huawei.com (10.201.108.52) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1713.5; Fri, 22 Nov 2019 10:01:56 +0000
Received: from NKGEML411-HUB.china.huawei.com (10.98.56.70) by lhreml703-chm.china.huawei.com (10.201.108.52) with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA_P256) id 15.1.1713.5 via Frontend Transport; Fri, 22 Nov 2019 10:01:55 +0000
Received: from NKGEML514-MBX.china.huawei.com ([fe80::40a8:f0d:c0f3:2ca5]) by nkgeml411-hub.china.huawei.com ([10.98.56.70]) with mapi id 14.03.0439.000; Fri, 22 Nov 2019 18:01:51 +0800
From: "Xiejingrong (Jingrong)" <xiejingrong@huawei.com>
To: "Rajiv Asati (rajiva)" <rajiva@cisco.com>, Mike McBride <mmcbride7@gmail.com>
CC: "bier@ietf.org" <bier@ietf.org>, Antoni Przygienda <prz=40juniper.net@dmarc.ietf.org>
Thread-Topic: [Bier] BIER v6 requirements draft comments: draft-ietf-bier-ipv6-requirements ...
Thread-Index: AQHVnp1Mgwwp4iu3RkeLcJpFC8FV+KeR7oaAgACTxACABHdyoA==
Date: Fri, 22 Nov 2019 10:01:50 +0000
Message-ID: <16253F7987E4F346823E305D08F9115AABA9D417@nkgeml514-mbx.china.huawei.com>
References: <24BB25FC-F19D-4CE2-B5AB-2BF1F844546E@juniper.net>, <CAL3FGfwFJDN6WK8UdLzOdDJDxeL9Bf5P_ncGAdNQw58HEd8UNw@mail.gmail.com> <07709F8A-51D2-4265-8DBF-7D1B71CB545E@cisco.com>
In-Reply-To: <07709F8A-51D2-4265-8DBF-7D1B71CB545E@cisco.com>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.52.40.236]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/bier/FvLy7bNwAQYMfViwSyuLCiEly0s>
Subject: Re: [Bier] BIER v6 requirements draft comments: draft-ietf-bier-ipv6-requirements ...
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: Fri, 22 Nov 2019 10:02:03 -0000

Hi all,

Thank you all for raising your concerns on the list and on the ietf106 mic. 
Have talked to you guys more after the session, and watched the video more, and I find I have understand your concerns. 
I'd like to continue this debating now, to avoid forgetting anything and avoid the discussion freezing.

The raised questions include, the L2.5 and L3, TTL, OAM, security. Req 4.2, 4.3 and 4.11, and so on.

I summarized as that, all the concerns come from the fact that, 12 requirements in the v6-requirements draft are target the IPv6 L3 BIER, and it can be shortened into one requirement: Requiring L3 BIER based on IPv6 !

And then, all the above concerns comes from the "L3 BIER" requirement, summarized as below:
1.Do we need it ? 
2.Does it breaks BIER architecture? 
3.Does it brings more security problems when deploying ? 
4.How should the solutions be, such as TTL/OAM /Multicast or unicast DA used/Multicast or unicast SA used/etc.

So maybe we can get this debating started on the first concern, Do we need it ? why do we need it ? why other solutions like L2.5/L4+ don't satisfy that?

I'd like to list my initial thoughts that, we really need a L3 BIER, for ease of BIER deployment in IPv6 network, within a larger BIER domain (which is beyond the normal BIER domain which is normally an IGP domain or IGP area/level), and leverages the reachability of IPv6 unicast address.

Your thoughts?

Best Regards,
Jingrong

-----Original Message-----
From: BIER [mailto:bier-bounces@ietf.org] On Behalf Of Rajiv Asati (rajiva)
Sent: Wednesday, November 20, 2019 5:47 AM
To: Mike McBride <mmcbride7@gmail.com>;
Cc: bier@ietf.org; Antoni Przygienda <prz=40juniper.net@dmarc.ietf.org>;
Subject: Re: [Bier] BIER v6 requirements draft comments: draft-ietf-bier-ipv6-requirements ...


Please see inline,

> MM: Unless my co-authors, or anyone else, disagrees, I say we simply 
> remove this section and any and all references to SRv6 if it's not 
> helpful. Focus should be on IPv6 related requirements.

Agreed. 

> MM: This isn't a solutions document so whether it's a good idea or not 
> can be saved for that document to justify. We will move the solutions 
> overviews to an appendix.

Indeed. that helps to keep the focus on requirements. 

>> Last, major objection is that by opening any IPv6 destination address to receive BIER frames from multiple hops away we are opening a completely security nightmare and argumenting that whole BIER layer has to be IPSEC’ed to close that hole is simply going into a seriously wrong direction IMO.
> 
> MM: Which requirement are you referring to?


Perhaps, requirement 4.2 - DA modification !!!

If we continue with BIER being an L2.5 forwarding technology in IPv6 paradigm, then modifying v6 DA yields limited to no value. And tunneling would be the only sane way to accommodate non-BIER transit routers, if any. 

However, this means IPv6 being treated in a similar manner as IPv4. Just a payload. This should be debated.  

Cheers,
Rajiv  


> On Nov 19, 2019, at 8:57 PM, Mike McBride <mmcbride7@gmail.com>; wrote:
> 
> Hi Tony,
> 
>> On Mon, Nov 18, 2019 at 9:51 PM Antoni Przygienda 
>> <prz=40juniper.net@dmarc.ietf.org>; wrote:
>> 
>> Finally getting to fire off some comments on 
>> draft-ietf-bier-ipv6-requirements draft
> 
> MM: Yay! thank you, happy we are getting some feedback.
> 
>> 3.4: I see NO requirements to do anything with SR or SRv6 in BIER WG charter so I am not sure how it ended up so prominently in the draft. And BIER is a hop-by-hop technology, it already includes provisions to transition non-BIER nodes via correct algorithms so not sure how SRv6 is of any use or relevance here. Of course BIER could be tunneled with SRv6 but then a BIER frame should be carried natively inside a SRv6 frame.  Comingling two level layer 2.5 transport technologies into a single layer format as the draft seems to imply is unnecessary and a bad idea since there will be resulting cross-talk.
> 
> MM: Unless my co-authors, or anyone else, disagrees, I say we simply 
> remove this section and any and all references to SRv6 if it's not 
> helpful. Focus should be on IPv6 related requirements.
> 
>> 4.2: completely disagreed. BIER is a hop-by-hop layer 2.5 technology. Modifying IP options is arguably far more expensive than next-protocol frame.
> 
> MM: You completely disagree with requirement 4.2? You believe that the 
> solution _should_ require hop-by-hop modification of the IP source 
> address field? Or just disagree with our explanation of it? This 
> requirement came from Eric Rosen long ago. Please suggest new 
> requirement wording that makes you happy.
> 
>> 4.3:
>> 
>> fragmentation will only play in IPv6 case if the frame is longer than 
>> IPv6 max frame size - BML roughly. No matter _where_ we stick the 
>> mask we face the same problem until we start to do BIER fragmentation 
>> and reassembly
> 
> MM: So the requirement "should not require the BFRs to inspect layer 4 
> or require any changes to layer 4." is fine but you don't like the 
> fragmentation wording? Or do you not like the requirement period? We 
> can certainly re-word it or remove it if it causes heartache. Again 
> this was another Rosen requirement I believe. Fragmentation is 
> optional for BIER, but, from an IPv6 point of view, it is a basic 
> capability and we figured we should support it. Maybe we don't but 
> let's get the requirement down.
> 
>> Again, SRv6 is neither in the charter nor an issue since BIER is a 
>> L2.5 hop-by-hop technology and not, as the authors want it, all of a 
>> sudden an implicit tunneling or multi-hop technology
> 
> MM: Consider SRv6 gone from this draft since having it in there is 
> causing pain.
> 
>> 4.11: and again BIER is hop-by-hop and it will rely on higher layers to re-assemble just like MPLS does.
> 
> MM: and again IPv6 does provide the fragmentation/assembly capability, 
> so we figured BIER should inherit such capability but we could 
> certainly be wrong. Are you in favor then of removing the 4.11 
> requirement involving fragmentation? Or re-wording it?
> 
>> I-D.xie-bier-ipv6-encapsulatio: yes, IPv6 architecture has the 
>> loophole for in flight modification of hop-by-hop header options but 
>> it does not mean it’s a good idea
> 
> MM: This isn't a solutions document so whether it's a good idea or not 
> can be saved for that document to justify. We will move the solutions 
> overviews to an appendix.
> 
>> Last, major objection is that by opening any IPv6 destination address to receive BIER frames from multiple hops away we are opening a completely security nightmare and argumenting that whole BIER layer has to be IPSEC’ed to close that hole is simply going into a seriously wrong direction IMO.
> 
> MM: Which requirement are you referring to? Perhaps you are referring 
> to requirement 4.3 involving L4 Inspection where we mention IPsec? We 
> figured the IPSEC architecture should be inherited from IPv6 if we are 
> considering BIER in IPv6 but it looks like you don't agree. We are 
> happy to modify/add/remove any requirement just needs specifics.
> 
> thanks,
> mike
> 
>> 
>> 
>> --- tony
>> 
>> 
>> 
>> _______________________________________________
>> BIER mailing list
>> BIER@ietf.org
>> https://www.ietf.org/mailman/listinfo/bier
> 
> _______________________________________________
> BIER mailing list
> BIER@ietf.org
> https://www.ietf.org/mailman/listinfo/bier
_______________________________________________
BIER mailing list
BIER@ietf.org
https://www.ietf.org/mailman/listinfo/bier