IETF Logo Mail Archive

Re: [Bier] BIER rechartering

Jeff Tantsura <jefftant.ietf@gmail.com> Wed, 24 January 2018 05:04 UTC

Return-Path: <jefftant.ietf@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 B3D6512D958 for <bier@ietfa.amsl.com>; Tue, 23 Jan 2018 21:04:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-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 LP3vm9BrOT22 for <bier@ietfa.amsl.com>; Tue, 23 Jan 2018 21:04:13 -0800 (PST)
Received: from mail-pf0-x22d.google.com (mail-pf0-x22d.google.com [IPv6:2607:f8b0:400e:c00::22d]) (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 B04451275C5 for <bier@ietf.org>; Tue, 23 Jan 2018 21:04:13 -0800 (PST)
Received: by mail-pf0-x22d.google.com with SMTP id 23so2196749pfp.3 for <bier@ietf.org>; Tue, 23 Jan 2018 21:04:13 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=user-agent:date:subject:from:to:cc:message-id:thread-topic :references:in-reply-to:mime-version; bh=hYnOJGO4b0od0zbIvsRATWquoSXgZLeXWRym/XcSPIc=; b=eTf+BWvUpLEvxdbCBKrn7JHhvnrLsaT/tYtRwD9/UP8fWeW8Syn2TyTZWf8CMc7fop 6dz5TSIX6YoRjF5lW2ILVHUhU/aiHUo4m/I/l3jeZEYi2mLQVTTNDiSvKNzBHD+MstcJ uV+mT5Qhp3dtf6kdYswNP9UshZEkfC2aKzt9r4HwnrPSrXC7qkqJ475Bw6u5Tu7ShGT6 tF7UNbVbhMvIEgbgAYkyF4067jEoBAVep4LlxhCFNGee+sgiLCEXhBZgCDhgbfx00S6u gKU50IAVBMeCi7aV/qd/lC86+Tmh5419SLx4npwbSj1DIqAwveePa4zIycpjs5qUdzhb MsEA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:user-agent:date:subject:from:to:cc:message-id :thread-topic:references:in-reply-to:mime-version; bh=hYnOJGO4b0od0zbIvsRATWquoSXgZLeXWRym/XcSPIc=; b=Xc1WRALFcSmeRyto8+RWuQMO2ejpfmJlRdZGVjADpoxW2OpivPYi+PdV+2sFpdAiRl OHb7YsNNR65sRMtPaEkEYC72LKtmgTT+HnGtk9ucqfn5GXsNUq83t2jN10MBt1/LY0yL UwlFHTk2+bOFzc0jAWeq5jK/JFAOqRbANRQXEvuHG9brFqYKh6/8p4cAg7DV/5AieJBj iMYU1m4DBhSeHBytu/k2et/GKoSG0k5UN1I0csNDhTd7mveYSEgem05M5FVhH1QG4GmY 0+f1u6LjzMDub8MRUr43Jq/hLyXJff5AFuwID0DAV8xqLHFi+66t2Yy62tIDmoT0hPEP oPJA==
X-Gm-Message-State: AKwxytfoRia8g8UJnAM9cXK/ViifdXYfyRsgf7KSFy5zXsZjFcGvSJ65 aNMWEYYFgE5uLFIDICd0HmA=
X-Google-Smtp-Source: AH8x225d6Z6I9dpAwVO7M8KRZYTMi532wSEQkBFXeeQOpyWlrgJnlsMOsGh+rsFRD/d9UFcOYS+j8g==
X-Received: by 2002:a17:902:7716:: with SMTP id n22-v6mr7146507pll.388.1516770252560; Tue, 23 Jan 2018 21:04:12 -0800 (PST)
Received: from [192.168.1.25] ([76.126.247.72]) by smtp.gmail.com with ESMTPSA id l188sm9982429pgl.72.2018.01.23.21.04.11 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 23 Jan 2018 21:04:11 -0800 (PST)
User-Agent: Microsoft-MacOutlook/f.27.0.171010
Date: Tue, 23 Jan 2018 21:04:10 -0800
From: Jeff Tantsura <jefftant.ietf@gmail.com>
To: "Dolganow, Andrew (Nokia - SG/Singapore)" <andrew.dolganow@nokia.com>, Tony Przygienda <tonysietf@gmail.com>
CC: "bier@ietf.org" <bier@ietf.org>
Message-ID: <FBF2765D-194F-463F-9249-BA2F7F68A1EC@gmail.com>
Thread-Topic: [Bier] BIER rechartering
References: <CAG4d1rdCysU+qnb=9U9iaZ+UefudWYDmz=mNPSfhDPuWNQQHVw@mail.gmail.com> <B9800CBE-2810-46F9-B802-8823AE769699@nokia.com> <CA+wi2hO112XTHLZuJSsPxZzGhAY1A6RTGDBt-+n6XXc6WXodDw@mail.gmail.com> <20646310-FA88-4A6B-B14E-D2FDD834970A@nokia.com>
In-Reply-To: <20646310-FA88-4A6B-B14E-D2FDD834970A@nokia.com>
Mime-version: 1.0
Content-type: multipart/alternative; boundary="B_3599586251_575498211"
Archived-At: <https://mailarchive.ietf.org/arch/msg/bier/6nQnjRFpDt89O5_r2yQZKKzJ668>
Subject: Re: [Bier] BIER rechartering
X-BeenThere: bier@ietf.org
X-Mailman-Version: 2.1.22
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: Wed, 24 Jan 2018 05:04:16 -0000

+1

 

don’t see why we should limit ourselves 

 

Cheers,

Jeff

 

From: BIER <bier-bounces@ietf.org> on behalf of "Dolganow, Andrew (Nokia - SG/Singapore)" <andrew.dolganow@nokia.com>
Date: Tuesday, January 23, 2018 at 20:56
To: Tony Przygienda <tonysietf@gmail.com>
Cc: "bier@ietf.org" <bier@ietf.org>
Subject: Re: [Bier] BIER rechartering

 

Tony,

 

This is discussion on charter not individual draft. We did have some good discussion on the draft below as reflected by minutes. My comment is that the charter as proposed limits potential solutions unnecessarily. I propose we remove trhe limiting condition “Such functionality may focus on assuming software or slow-path support first” from the charter.

 

Andrew

 

From: Tony Przygienda <tonysietf@gmail.com>
Date: Wednesday, January 24, 2018 at 12:00 PM
To: Andrew Dolganow <andrew.dolganow@nokia.com>
Cc: Alia Atlas <akatlas@gmail.com>, "bier@ietf.org" <bier@ietf.org>
Subject: Re: [Bier] BIER rechartering

 

 

 

Ad> Can we say “in co-operation with IETF WGs chartered with IGP protocol ownership”  instead of “in cooperation with the LSR WG”. DO not want to re-charter in case we change/modify/merge/evolve other WGs.


The BIER-WG is additionally chartered to start Standards Track work on:
  7) BIER in IPv6 :  A mechanism to use BIER natively in IPv6 may be
     standardized if coordinated with the 6MAN WG and with understood
     applicability.  Such functionality may focus on assuming software or
     slow-path support first.

Ad> I do not think we should limit unnecessarily the solution or open doors for things that are possible (anything can be done in S/W) but potentially of little value. SO if someone brings a proposal for slow-path BIER we will evaluate on usefulness to use case being solved.

 

https://tools.ietf.org/html/draft-zhang-bier-bierin6-00

 

_______________________________________________ BIER mailing list BIER@ietf.org https://www.ietf.org/mailman/listinfo/bier

v2.23.0 | Report a Bug | By Email