Re: [Bier] BIER IPv6 Requirement

Greg Shepherd <gjshep@gmail.com> Thu, 20 August 2020 19:55 UTC

Return-Path: <gjshep@gmail.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 BD0933A130E; Thu, 20 Aug 2020 12:55:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.086
X-Spam-Level:
X-Spam-Status: No, score=-2.086 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_REMOTE_IMAGE=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 KXR7xy_R99nG; Thu, 20 Aug 2020 12:55:13 -0700 (PDT)
Received: from mail-pj1-x102a.google.com (mail-pj1-x102a.google.com [IPv6:2607:f8b0:4864:20::102a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C5BE93A0D6E; Thu, 20 Aug 2020 12:55:13 -0700 (PDT)
Received: by mail-pj1-x102a.google.com with SMTP id t6so1453697pjr.0; Thu, 20 Aug 2020 12:55:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:content-transfer-encoding:mime-version:subject:date:message-id :references:cc:in-reply-to:to; bh=xTSTn7bvWiO0TOVcYD9DwYSyc+ywUWnPF5ReNdFinhI=; b=LyVZDSRFubDs4rDB59Csf8qjSkv4WLb2ZJuO2G1CpGiNM5PTANdtMxK5ilNRunCYJR u269IA2VOD2Oo5jxlCBrIAuSvBhilmvq8H/7fADnj5WsUjpNbvwQTv34qCG2fKHX2Pvu 0SJpJcR17okNd8gQtX/d/XewdZmUtWzJsZm+ezUiVyMkeFeiitj4vaEYIVFZuHVA7Zu8 C6irbBtgXX/wwH3wo6aUvhuARZ3G6tKQB8ni7D17utTQYQd7fjhnybWo/xoE2tLgKKKK lTAGKnMnYWSz/i3B13FhoGfG+cvM8KOzXnmhrqWr3aXi31RSbVgoPIuLddCWv7GuFF04 +Oyw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:content-transfer-encoding:mime-version :subject:date:message-id:references:cc:in-reply-to:to; bh=xTSTn7bvWiO0TOVcYD9DwYSyc+ywUWnPF5ReNdFinhI=; b=qPp7oswwe/SSBCAGR+kn3GPWJ92SSVvDU+RRTarBhvLA2Kuc3Vpr4+vhgkx0KrH2F6 bC2fyV8lzSk3S9ZK1OwtG7OScig6HNLAGym4uDIj+woOOAj93a6RcAfaDiSeRuL/bsxY YqyyhsazT9q77db5f4M1bJiionFgo/ZO1Z6A9LvH1NIvJwi7lQD2LPfE9sEYVzcMF79J 2/ABNUPrsTXLEGzdYEvFg5t1g/RyewZD1Zx+VHromO510sTgKcLO92MXMr59uwNm716g qhljZtkIbnQ0+mPiqhybWy/v6sif4MhLjc9w8+5lyJwW1n5zp3NnaZtMIC6zlWpVcMSR 5Wyw==
X-Gm-Message-State: AOAM530d7i5my99uOWAdirtzWkrlCVyPenZ1ZjPSowk+d5ATMRLAcczz IcYlrQUvz32pZVmYX+9SiiqUxsG4jOyvPQ==
X-Google-Smtp-Source: ABdhPJz1QvZr6OPBvfYTGjXNhLv1fH6cpQ/ZSqJ4tRm+mEd5iaJrplM3DtDjySmSsIuH+NizaOVrOQ==
X-Received: by 2002:a17:90a:fc98:: with SMTP id ci24mr211388pjb.101.1597953312945; Thu, 20 Aug 2020 12:55:12 -0700 (PDT)
Received: from [10.1.20.196] ([208.85.232.2]) by smtp.gmail.com with ESMTPSA id y135sm3925738pfg.148.2020.08.20.12.55.11 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 20 Aug 2020 12:55:12 -0700 (PDT)
From: Greg Shepherd <gjshep@gmail.com>
X-Google-Original-From: Greg Shepherd <GJShep@gmail.com>
Content-Type: multipart/alternative; boundary="Apple-Mail-B6B64FA6-AAC0-4415-8060-3EE9A2054D41"
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (1.0)
Date: Thu, 20 Aug 2020 12:55:11 -0700
Message-Id: <E767A087-5E55-491E-B2E6-B86344119F48@gmail.com>
References: <CABNhwV3ha_YHjKmG0vK29=qn_K5YOgkAPQ8baoKNDOaOSikVYg@mail.gmail.com>
Cc: "Gengxuesong (Geng Xuesong)" <gengxuesong@huawei.com>, "draft-ietf-bier-ipv6-requirements@ietf.org" <draft-ietf-bier-ipv6-requirements@ietf.org>, Mike McBride <mmcbride7@gmail.com>, "bier@ietf.org" <bier@ietf.org>
In-Reply-To: <CABNhwV3ha_YHjKmG0vK29=qn_K5YOgkAPQ8baoKNDOaOSikVYg@mail.gmail.com>
To: Gyan Mishra <hayabusagsm@gmail.com>
X-Mailer: iPhone Mail (17D50)
Archived-At: <https://mailarchive.ietf.org/arch/msg/bier/HPQ_AUtMtV9dNUaKhXPcnnK8dM4>
Subject: Re: [Bier] BIER IPv6 Requirement
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: Thu, 20 Aug 2020 19:55:16 -0000

I had comments from a previous thread that need to be considered as well. 

Shep

Sent from my iPhone

> On Aug 20, 2020, at 08:53, Gyan Mishra <hayabusagsm@gmail.com> wrote:
> 
> 
> Hi Xuesong 
> 
> I am working on an update I will be posting to GitHub using Mikes version.
> 
> The main item I am updating is clarifying the BIER layers definition In the drawing and verbiage with the three layers so it’s crystal clear that we discussed in our understanding discussion.
> 
> Their were some comments that Alvaro mentioned so I am trying to address some of those as well.
> 
> I will be completed tomorrow and then you can update the draft with comments.  
> 
> Mike has a -mm version that I am building on in GitHub link below.
> 
>  https://github.com/mmcbride7/bier-v6-requirements
> 
> Thanks 
> 
> Gyan
> 
> 
> 
>> On Thu, Aug 20, 2020 at 3:14 AM Gengxuesong (Geng Xuesong) <gengxuesong@huawei.com> wrote:
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> Hi Mike, authors and WG,
>> 
>> 
>> 
>>  
>> 
>> 
>> 
>> I have read through the existing version of draft-ietf-bier-ipv6-requirements and the comments in the mailing list..  The concerns for this document mainly comes from three aspects:
>> 
>> 
>> 
>> 
>> 
>> 1..      
>> 
>> The problem statement: why we need BIER IPv6 solution (which I think is straight forward: we need solution(s) to deploy BIER in an IPv6 domain)
>> 
>> 
>> 
>> 
>> 
>> 2..      
>> 
>> The conceptual model for BIER IPv6 encapsulation (the existing model classification seems to be roughly agreed in the WG but the descriptions should be modified based on the comments)
>> 
>> 
>> 
>> 
>> 
>> 3..      
>> 
>> The requirement items and classification
>> 
>> 
>> 
>> 
>>  
>> 
>> 
>> 
>> I think the previous two points mainly request editing work and a document with some my personal recommended text could be found in the attachment just for your reference.
>> 
>> 
>> 
>> For the third point, I list the requirement items based on the existing discussions in the WG as follows:
>> 
>> 
>> 
>> Mandatory:
>> 
>> 
>> 
>> 
>> 
>> Ÿ  
>> 
>> L2 Agnostic (may be removed)
>> 
>> 
>> 
>> 
>> 
>> Ÿ  
>> 
>> Align to BIER architecture defined in RFC8279 (may be removed)
>> 
>> 
>> 
>> 
>> 
>> Ÿ  
>> 
>> Support deployment with Non-BFR routers
>> 
>> 
>> 
>> 
>> 
>> Ÿ  
>> 
>> Support OAM
>> 
>> 
>> 
>> 
>> 
>> Ÿ  
>> 
>> Support overlay service, e.g., MVPN, EVPN
>> 
>> 
>> 
>> Optional:
>> 
>> 
>> 
>> 
>> 
>> Ÿ  
>> 
>> Support native IPv6 functions, e.g., IPSEC, Fragmentation
>> 
>> 
>> 
>> 
>> 
>> Ÿ  
>> 
>> Support inter-AS multicast deployment
>> 
>> 
>> 
>> 
>> 
>> Ÿ  
>> 
>> Provide necessary security methods (may be removed)
>> 
>> 
>> 
>>  
>> 
>> 
>> 
>> I suggest to discuss and confirm these items in WG first, including what should be included/excluded, which one should be mandatory etc., then we could work on the detailed explanations for each
>> 
>> item.
>> 
>> 
>> 
>>  
>> 
>> 
>> 
>> Best Regards
>> 
>> 
>> 
>> Xuesong
>> 
>> 
>> 
>>  
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> _______________________________________________
>> 
>> BIER mailing list
>> 
>> BIER@ietf.org
>> 
>> https://www.ietf.org/mailman/listinfo/bier
>> 
> -- 
> 
> 
> Gyan Mishra
> Network Solutions Architect 
> M 301 502-1347
> 13101 Columbia Pike 
> Silver Spring, MD
> 
> _______________________________________________
> BIER mailing list
> BIER@ietf.org
> https://www.ietf.org/mailman/listinfo/bier