Re: [Idr] [Dyncast] Adoption call for draft-dunbar-idr-5g-edge-compute-app-meta-data-09.txt (7/29/2022 to 8/12/2022)

Jeff Tantsura <jefftant.ietf@gmail.com> Mon, 08 August 2022 22:58 UTC

Return-Path: <jefftant.ietf@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 5A2BAC15C502; Mon, 8 Aug 2022 15:58:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.107
X-Spam-Level:
X-Spam-Status: No, score=-2.107 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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=unavailable 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 cOgQN2fTTg-m; Mon, 8 Aug 2022 15:58:49 -0700 (PDT)
Received: from mail-pg1-x52c.google.com (mail-pg1-x52c.google.com [IPv6:2607:f8b0:4864:20::52c]) (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 90CE0C15C505; Mon, 8 Aug 2022 15:58:25 -0700 (PDT)
Received: by mail-pg1-x52c.google.com with SMTP id d7so9835405pgc.13; Mon, 08 Aug 2022 15:58:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=to:in-reply-to:cc:references:message-id:date:subject:mime-version :from:content-transfer-encoding:from:to:cc; bh=+juyirCr/HBQwk9pw6JXufYXAGb5BHS5w1HXgxujB8s=; b=mLM4mmp22PqXCqgEks7Ijp/8NJt7AU++myLFNSpEvzuZBEAnK6jlBiENMVXWw1KYyv XWHz8E+Lr148wzBaA/41kpgcQEt8cxkgyXmy08K0xBYrpim7lNnBogQwAUh7Zun/zkXJ aOqYZP8K+OVdCkMm7NX0GNz/4CQ0Bhs97ICvj8/gpoSpDEXDy9196WIgkzaZ06BEHF81 jstsjdnYrMfNg8mfElbJ5EeozY6WtGzF/lU5Rs7Thyy3YpYaveCK8Hj3McfBB5auqX0y +KWpn0E4ETX397U27qeGHFj2i4na6OCsKafZKH7S8Pbka4SDpDSFNi/paUYjCskUU/0M Rd/Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=to:in-reply-to:cc:references:message-id:date:subject:mime-version :from:content-transfer-encoding:x-gm-message-state:from:to:cc; bh=+juyirCr/HBQwk9pw6JXufYXAGb5BHS5w1HXgxujB8s=; b=X3w8uzJLe994b7LVxKZUzO1ELhvssrWwRYoFux2TkxpNQAq/FTEs7wbjiP1qPXpxUM k3iVf562fxerJNKAIKEdEGvfuCqkpwOjW50gcm7EFv9WWPw2X1SLKVqnrIIBxwetZhf6 DLSaIOvEzcY3Avq3iOURSxTJOnY3mMq1FRKMjteK9+pG3RHIAA4GJzLmhEPE4dgyvrKa jPvXHBsR/M50I19K8NGEWtee6/WVEHq3vcqlw1FU8WBUq0/nlBMq8ztCRPhj1Z688Cuo 2q07loR+FKoO504oxRoFqJFzyg5cTedHUc/2O5ub5NLhF9PqAkt8bHXlarpWQbSP/VIk KEJw==
X-Gm-Message-State: ACgBeo1oheIkagIJeXUt5+st+fRCme1+TGmG1Orx86Z2NtoHF6m+eGgs DjIVnZLjgid8DqkdtqsfNkrQ9jeI+CE=
X-Google-Smtp-Source: AA6agR4LEQRRUiSwBgd9b5/Rjn+U3O0Fmgt0Dk4S9FWo24o/A4F9hhPm/cdyN2RiuTcuZbQhRFeIIQ==
X-Received: by 2002:a63:6b06:0:b0:41b:79c9:7313 with SMTP id g6-20020a636b06000000b0041b79c97313mr17084119pgc.409.1659999503624; Mon, 08 Aug 2022 15:58:23 -0700 (PDT)
Received: from smtpclient.apple (174-087-194-110.res.spectrum.com. [174.87.194.110]) by smtp.gmail.com with ESMTPSA id i30-20020a056a00005e00b0052d8d7269d7sm9199064pfk.53.2022.08.08.15.58.22 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 08 Aug 2022 15:58:23 -0700 (PDT)
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
From: Jeff Tantsura <jefftant.ietf@gmail.com>
Mime-Version: 1.0 (1.0)
Date: Mon, 8 Aug 2022 15:58:21 -0700
Message-Id: <2EA8132B-6E4B-41BF-8B22-23FD3DD9CEC9@gmail.com>
References: <DBE9A86B-2C85-4030-A424-1D4984F5916A@cisco.com>
Cc: "Jeffrey (Zhaohui) Zhang" <zzhang=40juniper.net@dmarc.ietf.org>, Susan Hares <shares@ndzh.com>, idr@ietf.org, dyncast@ietf.org
In-Reply-To: <DBE9A86B-2C85-4030-A424-1D4984F5916A@cisco.com>
To: "Acee Lindem (acee)" <acee=40cisco.com@dmarc.ietf.org>
X-Mailer: iPhone Mail (19G71)
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/e4FE8uh-yzh5I1Vh41ACQUljMSw>
Subject: Re: [Idr] [Dyncast] Adoption call for draft-dunbar-idr-5g-edge-compute-app-meta-data-09.txt (7/29/2022 to 8/12/2022)
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: Mon, 08 Aug 2022 22:58:54 -0000

+1

Cheers,
Jeff

> On Aug 8, 2022, at 06:19, Acee Lindem (acee) <acee=40cisco.com@dmarc.ietf.org> wrote:
> 
> I agree with Jeffrey. Given that the selection of endpoints at the application layer is already at an advanced level, the draft is predicated on a subset of this selection process being done with anycast addresses at the routing layer. 
> 
> Thanks,
> Acee
> 
> On 8/4/22, 1:51 PM, "Dyncast on behalf of Jeffrey (Zhaohui) Zhang" <dyncast-bounces@ietf.org on behalf of zzhang=40juniper.net@dmarc.ietf.org> wrote:
> 
>    Hi,
> 
>    There was a CAN BOF in IETF113:
> 
>    https://datatracker.ietf.org/doc/bofreq-liu-computing-aware-networking-can/
>    https://www.youtube.com/watch?v=_0uanSBJz5c&ab_channel=IETF-InternetEngineeringTaskForce
> 
>    There have been extensive and on-going discussions on whether we should solve the problem in routing. There were two presentations on the follow-up in IETF114 as well. My understandings are:
> 
>    - It is not decided yet if/where there will be a CAN WG and whether we should standardize a routing-based solution
>    - This draft is a routing-based solution for the use case
> 
>    Based on above, I do not think we should rush to adopt it - it should be deferred to until CAN is decided.
> 
>    I am copying the CAN mailing list (dyncast@ietf.org).
> 
>    Thanks.
>    Jeffrey
> 
> 
>    Juniper Business Use Only
> 
>    -----Original Message-----
>    From: Idr <idr-bounces@ietf.org> On Behalf Of Susan Hares
>    Sent: Friday, July 29, 2022 6:23 AM
>    To: idr@ietf.org
>    Subject: [Idr] Adoption call for draft-dunbar-idr-5g-edge-compute-app-meta-data-09.txt (7/29/2022 to 8/12/2022)
> 
>    [External Email. Be cautious of content]
> 
> 
>    This begins a 3 week WG Adoption call for draft-dunbar-idr-5g-edge-compute-app-meta-data-09.txt
>    https://urldefense.com/v3/__https://datatracker.ietf.org/doc/draft-dunbar-idr-5g-edge-compute-app-meta-data/__;!!NEt6yMaO-gk!FUoaLlWqdv8TPFCwzEtE2-8x6PRa-AsjklFfcIuNSadWVhqdf7uktC31Ynli5-IYysRSNv_WVVS6-sg$
> 
>    This draft proposes a new SubTLV (AppMetaData) for the BGP Tunnel Encapsulation Attribute [RFC9012] that indicates the running status and environment of directly attached 5G Edge Computing (EC) instances.
> 
>    The AppMetaData can be used by routers in the 5G Local Data Network to make path selection not only based on the routing distance but also the running environment of the destinations. The goal is to improve latency and performance for 5G EC services.
> 
>    In your discussion of this adoption call, please consider these questions:
> 
>    1) The addition of this type of information to tunnels is useful for inter-domain routing within 5G networks?
> 
>    2) What type of additional load this data to Basic Tunnel encapsulation [RFC9012]?
> 
>    For example is the load placed by this draft equal or Less than the SR routing additions from such as draft-ietf-idr-segment-routing-te-policy?
> 
>    3) Will the addition of this information aid Routing in 5G networks?
> 
>    Cheers, Sue Hares
> 
>    _______________________________________________
>    Idr mailing list
>    Idr@ietf.org
>    https://urldefense.com/v3/__https://www.ietf.org/mailman/listinfo/idr__;!!NEt6yMaO-gk!FUoaLlWqdv8TPFCwzEtE2-8x6PRa-AsjklFfcIuNSadWVhqdf7uktC31Ynli5-IYysRSNv_W1s6-HKo$
> 
>    -- 
>    Dyncast mailing list
>    Dyncast@ietf.org
>    https://www.ietf.org/mailman/listinfo/dyncast
> 
> _______________________________________________
> Idr mailing list
> Idr@ietf.org
> https://www.ietf.org/mailman/listinfo/idr