IETF Logo Mail Archive

Re: [Idr] [Re: Idr] I-D Action: draft-ietf-idr-bgp-extended-messages-31.txt

Christopher Morrow <morrowc.lists@gmail.com> Tue, 02 July 2019 05:00 UTC

Return-Path: <christopher.morrow@gmail.com>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7E15A12008D for <idr@ietfa.amsl.com>; Mon, 1 Jul 2019 22:00:06 -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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, 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 KUOTwEAR_XoF for <idr@ietfa.amsl.com>; Mon, 1 Jul 2019 22:00:05 -0700 (PDT)
Received: from mail-qk1-x72b.google.com (mail-qk1-x72b.google.com [IPv6:2607:f8b0:4864:20::72b]) (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 E7BF612004D for <idr@ietf.org>; Mon, 1 Jul 2019 22:00:04 -0700 (PDT)
Received: by mail-qk1-x72b.google.com with SMTP id l128so12952681qke.2 for <idr@ietf.org>; Mon, 01 Jul 2019 22:00:04 -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:content-transfer-encoding; bh=yrIMSkXT8ulSSWJctZbTGddGH5v/pzn8uLaF6nRS+K0=; b=iQ7EtgIkyQx/ZbJ498QsnyHU/3bQgHIFlqCpOFWup6L0fQ7HDfv3UKAYw/5BH5Djik B454gJMWgCRjEEnGNKNlh95bqQSZMICsDV3zf33f6mQO2ykJp9WSGfpwj1YbLQVKWO25 XDzEuykMc9fAuSarqUCYCdkEfvvLLXnTCF7GQM/G4xzWp9FOyrNdE/YwJLNgtY1bi1P3 wD7F5RJDyoHj9HkAcIHXyWewbVlItJCNIuPX/WHjZVygMnqJuu7pexneanch2LfetF69 A+dejqG2FjGiqA4+4Zc+VoVwekH0MmPXJ9S5vL5T7GYezsK/gyrAMPLBQNMgQTHY1W+a xxvQ==
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:content-transfer-encoding; bh=yrIMSkXT8ulSSWJctZbTGddGH5v/pzn8uLaF6nRS+K0=; b=Y5IkZ8U+2ZrWZ19S3usBq3lmUUhYiSP2U6Kn04B2nwaGozb24XFKmhjvkVObS+iTj6 SdoVxjI8TQXgB9ovGceNrb99oEgDD5hrwRgXUhjBlxU4Omzv6q9hLkTmiEbU5gGSwmvC PI6gtR0dcWA6KNx48TZ+iG+pKmSbuBd3RPCaGum6gGqxBc3+e4I5prdf4aIGCQfY+8Z7 PG/FWhpHgKaFqTWvbbac6L0mS0x0q8JLugdQOUkYCYwoa8TuVpOmyBwcmc62soatkdQY SJG1yEw5t5BpXxHXJQeICwpCqlfnefuvOL9G8n5Xwa056lz1OOezt/rXO8vGO8uXQu9x YWkw==
X-Gm-Message-State: APjAAAWV30+BTwVeEOF03VpgexEyRZw59WB4HYkNcdH9ngtY88r6exck J72biIEY5EOwewjfER3QkaIkxsThTfG95XlU+/E=
X-Google-Smtp-Source: APXvYqxkzR1/75VntmxW66FDU1u+sGgPhbLxUYWcSVuja4A15V6001oY9fyEwAST+X8l1zMUcQGQ3m7Agm8kpS/H3MU=
X-Received: by 2002:a05:620a:102d:: with SMTP id a13mr23710335qkk.268.1562043603635; Mon, 01 Jul 2019 22:00:03 -0700 (PDT)
MIME-Version: 1.0
References: <FDAC847D-60A2-4571-99CF-50458AC0E159@cisco.com> <m21rz9xn46.wl-randy@psg.com> <CAL9jLaayGk7HuAepuy=fzoRv+HHOUQJSgauRkjBCPxgtXzGN3g@mail.gmail.com> <3E08630E-03F7-41F1-95C4-0007EBFBCC95@cisco.com>
In-Reply-To: <3E08630E-03F7-41F1-95C4-0007EBFBCC95@cisco.com>
From: Christopher Morrow <morrowc.lists@gmail.com>
Date: Tue, 02 Jul 2019 00:59:52 -0400
Message-ID: <CAL9jLaa8n7MS7ieF9Dp7+LUGS=P516LjSP9jM7dPdsw1dGS+qQ@mail.gmail.com>
To: "Enke Chen (enkechen)" <enkechen@cisco.com>
Cc: Randy Bush <randy@psg.com>, "idr@ietf.org" <idr@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/JFaxX9j0jvFBwRZso9c8PFRpEXI>
Subject: Re: [Idr] [Re: Idr] I-D Action: draft-ietf-idr-bgp-extended-messages-31.txt
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr/>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Jul 2019 05:00:07 -0000

On Mon, Jul 1, 2019 at 11:34 PM Enke Chen (enkechen) <enkechen@cisco.com> wrote:
>
> No, there is no such assumption.  Perhaps let me rephrase for clarify:

ah! ok, I misread your intent I think :(

> As long as Speaker A  is able and willing to receive large messages (by advertising
> the capability), its neighbor would be allowed to send such messages to Speaker A.
> Such behavior does not depend on whether Speaker A  is able / willing / need to
> send any large messages to its neighbors.

ok, makes sense to me. I believe I read it from the other direction:
"happy to send <nothing said about recieving>"
oops :)

>
> Regards,  -- Enke
>
> On 7/1/19, 7:01 PM, "Christopher Morrow" <morrowc.lists@gmail.com> wrote:
>
>     (from enke)
>     > > IMO the capability should be about “receiving” only. As long as a BGP
>     > > speaker is able and willing to receive large messages (by advertising
>     > > the capability), its neighbor would be allowed to send such messages
>     > > to the speaker. It really does not matter whether the speaker is able
>     > > / willing / need to send any large messages to its
>
>     is it a good idea to assume that you can send just because you can receive?
>     assuming seems a little dicey.
>
>

v2.23.0 | Report a Bug | By Email