Re: [Rift] WGLC, IPR and Implementation polling for draft-ietf-rift-rift-08

Ilya Vershkov <vershkov.ml@gmail.com> Thu, 03 October 2019 13:39 UTC

Return-Path: <vershkov.ml@gmail.com>
X-Original-To: rift@ietfa.amsl.com
Delivered-To: rift@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 54D321208E4; Thu, 3 Oct 2019 06:39:09 -0700 (PDT)
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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, 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 EmDOMBuNA8l0; Thu, 3 Oct 2019 06:39:07 -0700 (PDT)
Received: from mail-wm1-x333.google.com (mail-wm1-x333.google.com [IPv6:2a00:1450:4864:20::333]) (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 143E012006B; Thu, 3 Oct 2019 06:39:07 -0700 (PDT)
Received: by mail-wm1-x333.google.com with SMTP id r17so7273296wme.0; Thu, 03 Oct 2019 06:39:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=dqI2AcxcnJNm7PkWVoDRk+5pqv4tiZymkJtCzCo6bv8=; b=A87vrWVxFkUfq7mkYDiM1WS5cIxk+O15wzrTMo3gDPKVQUPsPm3O9jbQVIhzCo9zoS K9Ou0eWxchW5IJCtRq2pBSSJRBhMtCBlbL6h3OrrnG/PO2oyJq5KYuiD0WxBv76P2dUV YfaY4xmeAreIcOwohwxNuoJpiXdAHzDCxyZ7CEHbEqggCqkvkPGDWsP799mvHC9xqTff KSW7PR7JULstgIwwJZee2fsc/VowNN1Rf/5VGj3qEXjvbVrt1xWfTtYOYnuc1BM+fxFB LFCNA/izXTZ903PLpZl7R4S/opiwiycKbgUbcjxp30sa0AY7gm9wMRDE7amhPOInYLZl SvMQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=dqI2AcxcnJNm7PkWVoDRk+5pqv4tiZymkJtCzCo6bv8=; b=kuK9JkO5EersvY5BKqGsE3sEze4AfOvre8RGv8C95A4BEstB4sZA/5PntxbFTj/xh6 o8sOX19ul2lHxvOMVGFb5ORvP7rbbPYq6ajh7kIYWmTzTQByOL4YQeMeXqV2gpinHGKH OhiXXBDYvGNXCOVPDjwSlFzy0r6kwFfvZpNSVEzNpFxXEVnw7hyUGd/3PbbiE9HTp/+T 2x7nE0zh6H/eu5mKdrE3MxP6AbCymVDaS02fRzoAtD9WPYdyv4WjwhWQ2c9ItKK9QuZE /5RS1p1lm5JyrB8J9vgigdhhBel8lf24cp1DxS51RYjBMTkkCFlrI0Hl93Z08Pr99LX1 TSow==
X-Gm-Message-State: APjAAAXQyReD1+yz0eiG6t+K12pTcngjr2JE5c7Ja+KTWSY1iwDWoD5T 7xvOPIgVBzhItT7Bi0zBfO74Dhg8qgM8VHaEkrY=
X-Google-Smtp-Source: APXvYqzxDQOJFW5WG1khH2CXbNbEicHyGWPHMrqNQ2TbtlL7aNlxxxzLsbebd7Ng1NB2W7PDrYcbc8/YXtjbacAWf+k=
X-Received: by 2002:a05:600c:48b:: with SMTP id d11mr2117533wme.153.1570109945475; Thu, 03 Oct 2019 06:39:05 -0700 (PDT)
MIME-Version: 1.0
References: <DM5PR05MB35489E9A98D0A9508C9158CAD4B30@DM5PR05MB3548.namprd05.prod.outlook.com>
In-Reply-To: <DM5PR05MB35489E9A98D0A9508C9158CAD4B30@DM5PR05MB3548.namprd05.prod.outlook.com>
From: Ilya Vershkov <vershkov.ml@gmail.com>
Date: Thu, 3 Oct 2019 16:38:53 +0300
Message-ID: <CA+HftMz8vJdk78UrXv2+C2obLq69Vb8BObh9vmbHEwOFDyVmCA@mail.gmail.com>
To: "Jeffrey (Zhaohui) Zhang" <zzhang=40juniper.net@dmarc.ietf.org>
Cc: Jeff Tantsura <jefftant.ietf@gmail.com>, "rift@ietf.org" <rift@ietf.org>, "rift-chairs@ietf.org" <rift-chairs@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000008ef873059401b5d9"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rift/B4QZu9NXH92jof8bejEYJ1OSNgc>
Subject: Re: [Rift] WGLC, IPR and Implementation polling for draft-ietf-rift-rift-08
X-BeenThere: rift@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Discussion of Routing in Fat Trees <rift.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rift>, <mailto:rift-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rift/>
List-Post: <mailto:rift@ietf.org>
List-Help: <mailto:rift-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rift>, <mailto:rift-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Oct 2019 13:39:10 -0000

+1



not aware of any undisclosed IPR


Ilya

On Fri, 13 Sep 2019 at 22:40, Jeffrey (Zhaohui) Zhang <zzhang=
40juniper.net@dmarc.ietf.org>; wrote:

> Hi RIFTers,
>
> This email starts WG Last Call, IPR and implementation polling  for our
> base spec draft-ietf-rift-rift-08. It ends on 9/27.
>
> Please thoroughly review the document and voice your support/objection.
>
> If you’re a co-author/contributor, please explicitly respond to this email
> and indicate whether or not you are aware of any relevant undisclosed IPR.
> The Document won't progress without answers from all the Authors and
> Contributors.
>
> If you're not a co-author/contributor, you need to respond only if you are
> aware of any relevant IPR not yet disclosed in conformance with IETF rules.
>
> Currently disclosed IPRs can be found here:
> https://datatracker.ietf.org/ipr/search/?submit=draft&id=draft-ietf-rift-rift
> .
>
> We are also polling for any existing implementation.
>
> Thanks!
> Jeff and Jeffrey
>
> -------------------------------
>
> From: RIFT <rift-bounces@ietf.org>; On Behalf Of Tony Przygienda
> Sent: Monday, September 9, 2019 3:06 AM
> To: rift@ietf.org
> Subject: [Rift] LC version -08
>
> LC ready version -08 has been posted
>
> Last few small changes based on input of people playing with both
> implementations in different scenarios
>
> * A new prefix tie type has been added
> PositiveExternalDisaggregationPrefixTIEType since it is necessary to
> distinguish between normal prefix and external prefix being disaggregated
> to preserve priorities in complex redistribution scenarios. BTW, negative
> prefixes are always least preferred and hence they don't need to
> differentiate.
> * Link pair carries now indication whether BFD is up 9on the link. This
> allows at the top of the fabric not only see links that are secured and
> outer keys but also whether link is BFD protected/BFD is up
> * NodeCapabilities are required now and minor protocol version is carried
> since there was no possiblity on adjacency building to check which minor
> verswion the peer speaks (major is carried in the envelope). Major version
> compatibility allows to aways decode the model but minor could be used in
> the future to understand minor schema variations
>
> thanks
>
> --- tony
> _______________________________________________
> RIFT mailing list
> RIFT@ietf.org
> https://www.ietf.org/mailman/listinfo/rift
>