IETF Logo Mail Archive

Re: [Idr] One Administrative Domain using BGP (Fwd: I-D Action: draft-uttaro-idr-bgp-oad-00.txt)

Gyan Mishra <hayabusagsm@gmail.com> Wed, 10 May 2023 23:09 UTC

Return-Path: <hayabusagsm@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 B80C0C1D25BE; Wed, 10 May 2023 16:09:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.084
X-Spam-Level:
X-Spam-Status: No, score=-1.084 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, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_REMOTE_IMAGE=0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=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 ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id g0PYLPGQ2gG5; Wed, 10 May 2023 16:09:14 -0700 (PDT)
Received: from mail-qt1-x835.google.com (mail-qt1-x835.google.com [IPv6:2607:f8b0:4864:20::835]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 901C9C1CCCAC; Wed, 10 May 2023 16:09:14 -0700 (PDT)
Received: by mail-qt1-x835.google.com with SMTP id d75a77b69052e-3f3a287ecceso10509521cf.0; Wed, 10 May 2023 16:09:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1683760153; x=1686352153; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=nWBJ7aWIV1YGjatG92I7VKldnrVoy2kLg9iLB+VDhpc=; b=kstW0UcA2UZJ9UQ4WyekRC27WeX1bqzzac0udq66madG+QBg2s+IzgpYzoksS1RrsO phUSB8UuAC/q42AzrNyC3hkC+zWMD4Oje7pU2HWUIycW0hv+Fnp+kPoRcgAmS62Gxacv Mhn8xHDSQwLIHNYQu1wM4tGtN9wbpBTCNMom2mFkIGnRIDjazZgN1Rmr1I1CKkTFVlUu k7wmEM+KpWUnyEb7StdHLMIHKo7Z5Asx4+gD4grs2ycQQ6csNMhjDKMvP008y5WfIWY+ JgBjhwax6UYuKagOovGUtRmFClR7hz0PovelFPidfXqzjbVjzko8Tyvo3e1bSkSPszH2 LeWw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1683760153; x=1686352153; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=nWBJ7aWIV1YGjatG92I7VKldnrVoy2kLg9iLB+VDhpc=; b=H8Nfb74jcBt06q9gDH3TZczACvsgxbPQ7L0g8If+CwrmTrZ7XGH0iyuWBSdw7FZ1Ov 7dztX60vcAhE7e8/VJ+WuROYgAmnuftv6Zk7S3xZw4gMIQSYfC7tuzkLRTL6IQ9Fy6oM 6fvjpFdhiNzcj9/S0KLHOmKGeEnbWu2mhn0J5lrWjaKoKvMVHkLCXCvKmDHzAvRFASIJ ki+2OkNpMosQ1kl7uqmRcvzRKSMybM5RX4feWH4w+5WpVuCfAL5Hghft/Hl/QrRK/nGB i2i2ryVtFs9S0hCSmX550h2wUtN192WTL+fZ5PWLWPI1hwPr6NXK16grquSpsv28lhl7 AJLg==
X-Gm-Message-State: AC+VfDzGvk27maI5IL90N/yvx3elCrlzCJE3+s3ij8IdRTEzbXhe1C3/ kvdYgZil1oLRV/5EvWwflSV+y0fzCpGsj3RHVO8=
X-Google-Smtp-Source: ACHHUZ52boa0aIeZsnpOGgSpN+f3xz/CvhAlLIzF4v+IvFCrMzzpMzBJY+teaejD7EUw8ADsIZnJ9O5wgdviLgL7W0k=
X-Received: by 2002:ac8:5c91:0:b0:3ef:5ba0:7038 with SMTP id r17-20020ac85c91000000b003ef5ba07038mr31883471qta.21.1683760153409; Wed, 10 May 2023 16:09:13 -0700 (PDT)
MIME-Version: 1.0
References: <etPan.640f456e.1281d5e1.245@futurewei.com> <BYAPR11MB32075FB5B3A0B9FF529A19ADC0BF9@BYAPR11MB3207.namprd11.prod.outlook.com> <SJ0PR02MB774487AA8915D597BD6D9914C6BF9@SJ0PR02MB7744.namprd02.prod.outlook.com> <AB52F4C3-053E-4837-AE62-C25719E6BFE8@cisco.com> <SJ0PR02MB7744E0C6101C9162BE224B03C6BF9@SJ0PR02MB7744.namprd02.prod.outlook.com> <CAOj+MMEgixrY9JsKzn8Ab33kfzNpRrFwHLWU7MO-D6YbBrrM=g@mail.gmail.com> <b86f19f5-7f32-353b-f181-dc1f26d09618@foobar.org> <CAOj+MMHV_MR+gxn6rnkrEP-e_oCr7qXBME=DHJAP6N-xgBE=0A@mail.gmail.com> <a0a678f8-6c1c-6612-7e75-dfe35769596e@foobar.org> <CAPF+HwWxXt5Ly9d=DHjk4d1DUh4wC8qifm5dwuTiJ=uO5uENuA@mail.gmail.com> <4B99F20B-2E4C-4881-8B76-DBAA9DB67FFC@pfrc.org> <CAPF+HwU9J6r71iCs5U7e+AcT5uu4OF1V-7Qw=7rU0kG196XY=A@mail.gmail.com> <etPan.645502b4.2b7e94d7.b220@futurewei.com> <CAPF+HwVR4bJ_BHEgEN8R4B5tVyS--XKn345NHyzS7-HmGvq4fQ@mail.gmail.com> <etPan.645bd3e1.6dde3a1e.ad5c@futurewei.com> <CAPF+HwVDJ5B9bOy+LDFHHRZP4GBKcC2LiGoM8C4eKLbJNx0Ybw@mail.gmail.com>
In-Reply-To: <CAPF+HwVDJ5B9bOy+LDFHHRZP4GBKcC2LiGoM8C4eKLbJNx0Ybw@mail.gmail.com>
From: Gyan Mishra <hayabusagsm@gmail.com>
Date: Wed, 10 May 2023 19:09:02 -0400
Message-ID: <CABNhwV0+n2s1gtUSOkT=h86DPvFLdryNF6deAizv8xue0bzqEA@mail.gmail.com>
To: Donatas Abraitis <donatas.abraitis@gmail.com>
Cc: Alvaro Retana <alvaro.retana@futurewei.com>, Robert Raszuk <robert@raszuk.net>, "UTTARO, JAMES" <ju1738@att.com>, "draft-uttaro-idr-bgp-oad@ietf.org" <draft-uttaro-idr-bgp-oad@ietf.org>, "idr@ietf.org" <idr@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000d4bcbf05fb5ef572"
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/KUzCYJdnblVBFF2Qb5IusQgR5QI>
Subject: Re: [Idr] One Administrative Domain using BGP (Fwd: I-D Action: draft-uttaro-idr-bgp-oad-00.txt)
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.39
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: Wed, 10 May 2023 23:09:18 -0000

I like the EBGP-OAD peering concept as it solves issue with non transitive
path attributes can now be transitive within the same admin domain and with
proliferation of BGP Only  domains RFC 7938 can be even more problematic
and needs a solution like this to resolve.

Good work by the authors proposing this solution!

On Wed, May 10, 2023 at 1:54 PM Donatas Abraitis <donatas.abraitis@gmail.com>
wrote:

> Yeah, a table would be great, without guessing to miss something (who
> implements that) :)
>
> On Wed, May 10, 2023 at 8:27 PM Alvaro Retana <alvaro.retana@futurewei.com>
> wrote:
>
>> Hi!
>>
>> Large Communities are transitive, so there’s no “special” handling needed
>> for EBGP-OAD.
>>
>> Having said that, we’re planning to include a list of all the attributes
>> in the next version, with a table, etc.  :-)
>>
>> Thanks!
>>
>> Alvaro.
>>
>> On May 9, 2023 at 11:38:16 AM, Donatas Abraitis (
>> donatas.abraitis@gmail.com) wrote:
>>
>> Also, I see that COMMUNITY/EXTCOMMUNITY attribute is defined on how to
>> handle them for BGP-AOD sessions, but not for LARGE-COMMUNITY. Or am I
>> missing something?
>>
>>
>
> --
> Donatas
> _______________________________________________
> Idr mailing list
> Idr@ietf.org
> https://www.ietf.org/mailman/listinfo/idr
>
-- 

<http://www.verizon.com/>

*Gyan Mishra*

*Network Solutions A**rchitect *

*Email gyan.s.mishra@verizon.com <gyan.s.mishra@verizon.com>*



*M 301 502-1347*

v2.23.0 | Report a Bug | By Email