IETF Logo Mail Archive

Re: BIER in IPv6

Fernando Gont <fgont@si6networks.com> Mon, 23 March 2020 19:55 UTC

Return-Path: <fgont@si6networks.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 17A0C3A0D82 for <ipv6@ietfa.amsl.com>; Mon, 23 Mar 2020 12:55:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-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 go9M1PTo9L1g for <ipv6@ietfa.amsl.com>; Mon, 23 Mar 2020 12:55:46 -0700 (PDT)
Received: from fgont.go6lab.si (fgont.go6lab.si [91.239.96.14]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BBDE13A0D65 for <6man@ietf.org>; Mon, 23 Mar 2020 12:55:46 -0700 (PDT)
Received: from [192.168.0.10] (unknown [181.45.84.85]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by fgont.go6lab.si (Postfix) with ESMTPSA id 1F0C980F49; Mon, 23 Mar 2020 20:55:42 +0100 (CET)
Subject: Re: BIER in IPv6
To: Michael McBride <michael.mcbride@futurewei.com>, "6man@ietf.org" <6man@ietf.org>
References: <BYAPR13MB2807CD38CF0228855AC269EEF4F70@BYAPR13MB2807.namprd13.prod.outlook.com>
From: Fernando Gont <fgont@si6networks.com>
Message-ID: <69daa5c0-3254-dfd1-fa49-ad06958203dc@si6networks.com>
Date: Mon, 23 Mar 2020 16:46:10 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <BYAPR13MB2807CD38CF0228855AC269EEF4F70@BYAPR13MB2807.namprd13.prod.outlook.com>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/6Rzw4uzgMFXiLsHD3bswrJ6OYcU>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 23 Mar 2020 19:55:50 -0000

Hello, Michael,

On 18/3/20 01:19, Michael McBride wrote:
> Hello,
> 
> The bier wg could use your ipv6 recommendations. We’ve worked on various 
> solutions to transport a bier header in ipv6. We decided to pause and 
> create a requirements document (draft-ietf-bier-ipv6-requirements) to 
> help steer us towards the right solution(s). In that drafts appendix we 
> have a fairly good summary of the various solutions.
> 
> We’ve started to rally behind two solutions which meet the majority of 
> the requirements: draft-xie-bier-ipv6-encapsulation (bier header in ipv6 
> EH) and draft-zhang-bier-bierin6 (bier header as payload using ipv6 NH). 
> The bier chairs today asked to punt the bierv6 topic to 6man for advice 
> before adopting any of these solutions.
> 
> So here we are seeking your advice. The most simple approach would 
> probably be to give 
> https://datatracker.ietf.org/doc/draft-ietf-bier-ipv6-requirements/ a 
> look and scroll down to the appendix to see a summary of the various 
> solutions we’ve been considering.

Thanks a lot for the note! I'll read the documents and come back with 
comments/questions in the next few days.

Thanks!

Cheers,
-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492

v2.23.0 | Report a Bug | By Email