IETF Logo Mail Archive

Re: draft-ietf-bfd-vxlan IESG status

Alvaro Retana <aretana.ietf@gmail.com> Wed, 17 June 2020 19:59 UTC

Return-Path: <aretana.ietf@gmail.com>
X-Original-To: rtg-bfd@ietfa.amsl.com
Delivered-To: rtg-bfd@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BB2533A0D81; Wed, 17 Jun 2020 12:59:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.096
X-Spam-Level:
X-Spam-Status: No, score=-1.096 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, FREEMAIL_REPLY=1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=0.001] autolearn=no 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 8SBUBnCdhOqb; Wed, 17 Jun 2020 12:59:42 -0700 (PDT)
Received: from mail-wr1-x434.google.com (mail-wr1-x434.google.com [IPv6:2a00:1450:4864:20::434]) (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 0C2793A0D77; Wed, 17 Jun 2020 12:59:42 -0700 (PDT)
Received: by mail-wr1-x434.google.com with SMTP id h5so3686833wrc.7; Wed, 17 Jun 2020 12:59:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:in-reply-to:references:mime-version:date:message-id:subject:to :cc; bh=N77zIVoDfPuXlKtXiZKubuv8sE3bPX/TsAOyKLTKB5s=; b=AVz2gfVhbYB51DhX1DNri8qZ2VTReFYe516EZiHyS2qRyCf/kMigJbukn0MMI2I17S Vo0GILtcWolsWAeWn/HnbU1o3r/0yFj4dcU5UiUmvIFn9oCKd6VjWadH76+EF3bfpcXt a9HQc08i07U7D0dWFKCNyZeJwCf1GTfe+wwUTfKN2p8553dyEGN80R7whyhSEmGHMXaa fxzYAZeBVo3Aqmxo8NRSLGOYdlCnNSHtaFitq3VDw0ovf6UCBQvkFwLqgeyMY1pLsQWD GUzuIiip/F9wEh2WByM9zdtltP9cCQJM++RxcyrD6D3olnkGQq8IF9bjqzxasY+t+nnw rAOQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:in-reply-to:references:mime-version:date :message-id:subject:to:cc; bh=N77zIVoDfPuXlKtXiZKubuv8sE3bPX/TsAOyKLTKB5s=; b=EbpYYENmS48yGVbCH+PbTOJLp4wt+5vRr/2bbmG6biZKF5Si+a0qyzOkEcjF6i75U1 hk1PDwcTGN5aBvI+852LR0XjJG84m2sMdhkhLRvd4cc0eP6RF8vzez59AUblw2Dnc0Tg 9kNMh5uRNgn8tBDCDd/eIOv4I/ZCHpg/syU/XXZhCuPCoKBJaqQh1LuU2DQr6QQjrw6j 0a7Ty7Q0NAwwMUy0WpkmoNSHRg/wASY0Mi86nIK/QZpIdSS983VEIdNccjOYvXQ1DGOc c/r5324joE43abQxFCqAbib+TNh9rvHKjeJBhzoF7wn+dhlSFvzfjmRvwPIAzdYyhpMj +gxg==
X-Gm-Message-State: AOAM530tn9mnsGG1rUiuRfIaq1cI/6DSr/n4olL4+2tQOdujQwECuwuB 23JUIvhLG8X6BONSp+7qrZD2uNTjX3TiIhs6Olc=
X-Google-Smtp-Source: ABdhPJxfYBzMt6p4HSoTCOwLggGE4OPlEcx7UzAw1JwR1xTTfpasjzNS7fKkp/IuwzFv4BLIucO1ZjEOCAO+C6rS2Pw=
X-Received: by 2002:a5d:4cc4:: with SMTP id c4mr855590wrt.159.1592423980574; Wed, 17 Jun 2020 12:59:40 -0700 (PDT)
Received: from 1058052472880 named unknown by gmailapi.google.com with HTTPREST; Wed, 17 Jun 2020 12:59:39 -0700
From: Alvaro Retana <aretana.ietf@gmail.com>
In-Reply-To: <CA+RyBmWiw8HFFZfcPPb_D8EutEacbbkK9=btbj6MM4SKAnV9yg@mail.gmail.com>
References: <20200127221705.GB17622@pfrc.org> <20200616211057.GA21373@pfrc.org> <CAMMESsxsPKM+jnLESOh=C+xyrw8+iGySXuMDo3TFTdU2RgUkDg@mail.gmail.com> <CA+RyBmWiw8HFFZfcPPb_D8EutEacbbkK9=btbj6MM4SKAnV9yg@mail.gmail.com>
MIME-Version: 1.0
Date: Wed, 17 Jun 2020 12:59:39 -0700
Message-ID: <CAMMESsz+cCq7Jh9m-wvWsSDCG6QoOWv1XZpeMBkjt69Asbk5dw@mail.gmail.com>
Subject: Re: draft-ietf-bfd-vxlan IESG status
To: Greg Mirsky <gregimirsky@gmail.com>
Cc: bfd-chairs@ietf.org, draft-ietf-bfd-vxlan@ietf.org, The IESG <iesg@ietf.org>, Jeffrey Haas <jhaas@pfrc.org>, rtg-bfd WG <rtg-bfd@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000b1aa2a05a84d19ef"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtg-bfd/57zclDNeyCm0haQCYtkUYC8Hns4>
X-BeenThere: rtg-bfd@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "RTG Area: Bidirectional Forwarding Detection DT" <rtg-bfd.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtg-bfd>, <mailto:rtg-bfd-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtg-bfd/>
List-Post: <mailto:rtg-bfd@ietf.org>
List-Help: <mailto:rtg-bfd-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtg-bfd>, <mailto:rtg-bfd-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 17 Jun 2020 19:59:44 -0000

Greg:

Rfc5881 already specifies using GTSM…this document depends on rfc5881, so
the reference should be the BFD behavior.

Alvaro.

On June 17, 2020 at 2:40:52 PM, Greg Mirsky (gregimirsky@gmail.com) wrote:

Hi Alvaro,
thank you for the suggestion. I have a question. The current version
references RFC 5082:
         TTL or Hop Limit: MUST be set to 255 in accordance with the
         Generalized TTL Security Mechanism [RFC5082].
RFC 5881, while stating the requirement for the TTL or Hop Limit value,
refers to RFC 5082 as the text that explains the benefits of using 255 on a
single IP link. In both documents, RFC 5082 is listed as a normative
reference. Would using RFC 5082 be acceptable or you suggest changing it to
RFC 5881?

Regards,
Greg

On Wed, Jun 17, 2020 at 9:37 AM Alvaro Retana <aretana.ietf@gmail.com>
wrote:

> On June 16, 2020 at 5:01:57 PM, Jeffrey Haas wrote:
>
>
> Hi!
>
>
> ...
> > > Open Issue 1: Discussion on TTL/Hop Limit = 1
> > >
> > > Proposed Action: Greg has proposed text he will send to the working
> group
> > > suggesting GTSM procedures be utilized. The expected concern is how
> this
> > > impacts existing implementations.
> >
> > This issue is resolved.
>
> As I had mentioned before [1], the use of 255 should reference
> rfc5881: the requirement is one from the base spec, not a new one
> here.
>
> Suggestion>
>
>    TTL or Hop Limit: MUST be set to 255 in accordance with [RFC5881].
>
>
> I am clearing my DISCUSS.
>
>
> Thanks!!
>
> Alvaro.
>
> [1]
> https://mailarchive.ietf.org/arch/msg/rtg-bfd/aiJW3KjYevY83wEDwVj488FSVl0/
>

v2.28.0 | Report a Bug | By Email | System Status