Re: [Lsvr] Kicking off the LSVR (Link State Vector Routing) charter discussion

Alia Atlas <akatlas@gmail.com> Thu, 18 January 2018 23:32 UTC

Return-Path: <akatlas@gmail.com>
X-Original-To: lsvr@ietfa.amsl.com
Delivered-To: lsvr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 61EE8120713 for <lsvr@ietfa.amsl.com>; Thu, 18 Jan 2018 15:32:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 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, RCVD_IN_DNSWL_LOW=-0.7, 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 vxuzrGtBbPsf for <lsvr@ietfa.amsl.com>; Thu, 18 Jan 2018 15:32:05 -0800 (PST)
Received: from mail-oi0-x230.google.com (mail-oi0-x230.google.com [IPv6:2607:f8b0:4003:c06::230]) (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 8883212D77C for <Lsvr@ietf.org>; Thu, 18 Jan 2018 15:32:04 -0800 (PST)
Received: by mail-oi0-x230.google.com with SMTP id t16so16916075oif.10 for <Lsvr@ietf.org>; Thu, 18 Jan 2018 15:32:04 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=X28LXaZIuiZXVgRnSIhDu/6b+PeI4ZovsPmuRysAghs=; b=nJx2urNsyHJSI+1VH4AQSj5qYFsvRrki9+PVFuHokCL9SyWgf80ATAAoqhURdIfrhA Dl6K1HOJjd55WUijjrO3K3gcF5BtIhSagDlJw7yMNMGhmgOaOY7yLSAP2bnjgL9pYNgf zVTycN4/nIEwQ9edcy6AWAH6Gztlye7cbepET9Gt/oCCG0aSw0myqBeQD8rSsL4bTnFQ zSkdAkmt7Xb41Eg6UCAWx7KQsg99KbYfdw3Dw05dWZNKk1sEllhC9LEvfIBjmr2Z7o62 WajBmlc2hJuuykYmr+aa7ZGQtXcMk+zzsnAsjMeUSVtyVOqbfmsiHBJVEPc01pcU4dcT GlEQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=X28LXaZIuiZXVgRnSIhDu/6b+PeI4ZovsPmuRysAghs=; b=sKTiVAtBd0L9wCrmhppeN0ksTCy/pJradwjzzfP8e4S85fFxXUsRP2Gmbls9aA7kwP /sm68jRdSguTnjLFOofZvV7Fh6NJg10USh0updlXGg5PX19xqB1Y9wm9qrHed6DOecdn Fz9nZxFfPeC5r8xprH888FaYdwhEtN82/VZJaVAUzWdWoyDcquLz6Vh0UDujy6y7QGSY Qh5y2rW2hzKohOaWodGORpu6XIriyTiC8Ns/3+j9rQFHJBO6T64DcgyrZPcMR7hQfEJP YuAbDqnylb8PPtzIxnCYgGzuDCLw2OCTuLNoGYXQlSzWFHNI0tD2yjUKEuwXGONpPTMJ l3+w==
X-Gm-Message-State: AKwxytc5RrZCDTrWLkbjlbzKJb/V0W8QqShAvPXwFceYKnz9MOGBUz09 PLgd7kOFsP1MMjN1jYRqtrDXinzdxrgchzzVDU4=
X-Google-Smtp-Source: ACJfBouRwkHJ2amh+6kXlQDqs6+HhU4LPgmNFFtjmXvnPKFzasfa9i9TKSz3+r4Cf+VBszNqS4xx0nKMUQTH5xT1XRU=
X-Received: by 10.202.48.76 with SMTP id w73mr3956009oiw.185.1516318323809; Thu, 18 Jan 2018 15:32:03 -0800 (PST)
MIME-Version: 1.0
Received: by 10.157.67.47 with HTTP; Thu, 18 Jan 2018 15:32:03 -0800 (PST)
In-Reply-To: <CA+b+ERn2xCd0Q-4YR3JWFSPCdHO=8SorErSquQXkWxNMvLbWfw@mail.gmail.com>
References: <CAJc3aaO8-OdJDNwNmofsadVWVdWdhk45p3Qs1DKjCvN1R_0vPA@mail.gmail.com> <D59B7ABE-F423-4F67-8DB3-2A177C6BD567@gmail.com> <F7708676-BE03-424D-8BBB-10AB0D1D3854@gmail.com> <m2inbystfc.wl-randy@psg.com> <71703812-2113-40A1-B299-251B9961E3A4@gmail.com> <CA+b+ER=4q8cfnQkk8zMBgUauaHvjyWDLvGG9P11UZ+Ndyt77kw@mail.gmail.com> <42C11665-5A01-4473-A9B3-0FE1F7B0D201@tony.li> <CA+b+ERn2xCd0Q-4YR3JWFSPCdHO=8SorErSquQXkWxNMvLbWfw@mail.gmail.com>
From: Alia Atlas <akatlas@gmail.com>
Date: Thu, 18 Jan 2018 18:32:03 -0500
Message-ID: <CAG4d1reT0tEKMFVZnE2gstgL116UTm8He+tLMckvWSdPg=sJpA@mail.gmail.com>
To: Robert Raszuk <robert@raszuk.net>
Cc: Tony Li <tony.li@tony.li>, Randy Bush <randy@psg.com>, victor@jvknet.com, Lsvr@ietf.org, Gaurav Dawra <gdawra.ietf@gmail.com>, "Van De Velde, Gunter (Nokia - BE)" <gunter.van_de_velde@nokia.com>
Content-Type: multipart/alternative; boundary="001a113cdf4c0ea45d0563155fb7"
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsvr/k5m9yGLw8JirAt5UFHPzeF0Mx0A>
Subject: Re: [Lsvr] Kicking off the LSVR (Link State Vector Routing) charter discussion
X-BeenThere: lsvr@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Link State Vector Routing <lsvr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/lsvr>, <mailto:lsvr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/lsvr/>
List-Post: <mailto:lsvr@ietf.org>
List-Help: <mailto:lsvr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lsvr>, <mailto:lsvr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 18 Jan 2018 23:32:07 -0000

On Thu, Jan 18, 2018 at 6:15 PM, Robert Raszuk <robert@raszuk.net> wrote:

> Well to the best of my understanding each AFI/SAFI as defined today
> carries different address class.
>
> With spf bgp we have a bit of a conflict as safi 1/1 or 2/1 may carry the
> exact same prefix as new fancy bgp spf.
>
> Clearly the authors of the latter need to differentiate how new SAFI is
> going to interwork with existing eBGP in any hypothetical deployment.
>
> - - -
>
> Completely agreed on "rationale" part as far as forming WG. I was more
> commenting on misleading community by setting up non wg forming bof just to
> see it has suddenly resulted in forming two working groups.
>

To clarify, the IESG has been having more non-wg forming BoFs which doesn't
actually judge whether a WG will form.  At a WG forming BoF, the
conversation is frequently around the charter and whether it has captured
the work items and scope appropriately.  At a non-WG forming BoF,
conversation is more around the technical problem and possible solutions.
I don't recall off-hand whether bier or babel had WG-forming BoFs.

This is all part of trying to get new work moving along more quickly (see
IETF relevance).

Regards,
Alia


> I am wishing them all the best !
>
> R.
>
>
>
> On Jan 19, 2018 00:02, "Tony Li" <tony.li@tony.li> wrote:
>
>
>
> Robert,
>
> There are some questions on how bgp spf would select routes when executed
> concurrently with "standard" bgp.
>
> The answer by some is to run it in parallel and just call it bgp as
> otherwise it will not sell ;)
>
>
>
> And I believe that’s why there’s already an AFI/SAFI mechanism
> incorporated: to de-multiplex information with alternate semantics.
> Therefore, we do not need another mechanism.
>
>
> Outside of all of this Alia and Alvaro are setting working groups for both
> rift and bgp-spf based on their own judgements.
>
> In Singapore we had a non wg forming bof on dc routing. How did that
> result in creation of two new wg is unknown.
>
> Is this how now IETF working groups get formed ? Behind the scene and
> without even single document spelling out what is wrong with current
> protocols ?
>
>
>
> The creation of WGs has always been at the discretion of the Area
> Directors.  Please see RFC 2418.  This RFC does NOT use the word
> ‘rationale’.
>
> Tony
>
>
>
>
> _______________________________________________
> Lsvr mailing list
> Lsvr@ietf.org
> https://www.ietf.org/mailman/listinfo/lsvr
>
>