Re: [Lsr] Request a 10 minute slot at IETF110 LSR session to brief the draft-dunbar-lsr-5g-edge-compute-ospf-ext

Yingzhen Qu <yingzhen.ietf@gmail.com> Tue, 23 February 2021 22:51 UTC

Return-Path: <yingzhen.ietf@gmail.com>
X-Original-To: lsr@ietfa.amsl.com
Delivered-To: lsr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 682D13A0E73 for <lsr@ietfa.amsl.com>; Tue, 23 Feb 2021 14:51:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.997
X-Spam-Level:
X-Spam-Status: No, score=-1.997 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, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=0.1, 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 oBzmff01ijjx for <lsr@ietfa.amsl.com>; Tue, 23 Feb 2021 14:51:52 -0800 (PST)
Received: from mail-pf1-x435.google.com (mail-pf1-x435.google.com [IPv6:2607:f8b0:4864:20::435]) (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 2327F3A0E72 for <lsr@ietf.org>; Tue, 23 Feb 2021 14:51:52 -0800 (PST)
Received: by mail-pf1-x435.google.com with SMTP id v200so155pfc.0 for <lsr@ietf.org>; Tue, 23 Feb 2021 14:51:52 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=+eTPMbCjjuZ7ALlOXHvCHyMCa3rZ51xz6G7BZrJLtYo=; b=BeUow9gMl+BbCCs1Et0dc66HBOCMjxIsW2tfBkrlp+wOlmBdSRMP3cgHN1a+d0twzz BpQoLtL5iyNyrYwkKTNrcEVWdn/kpgY3gI05WTq7lf1erDa1OShny2zsS7Mewi7FkmPq hO6v6PfGP3ahaBfzewfMxUL73y4ZYRfioo4vcrKs6fuNlOiIAtNg0jXGcWeaT1REh6vD CDXiFL24cI94UBd7+zGOeySNBsMhD+UVBuM96lQEkRaNLL8m2u0DVUKhO0W8u9hB8+v3 8h9i1vAs0N6Kf4pkmlntbej9IaxIMVpTdFwTWoURCh4D/kotKBcccVWeZ0XtLnu3IhXk lW7w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=+eTPMbCjjuZ7ALlOXHvCHyMCa3rZ51xz6G7BZrJLtYo=; b=aPqcjKj1HZZ7dY0tfIiYWr33hracVFUlg2RnILDk3v3f0/tQpMwpOE48PZic6qtJd+ 1SoudG0V73NSAv0/9hzPuSnpykNznQvxsSwyE3cgK/t1gP4CGth97XI63hFFaNWoVcLc SnpXwo0KpbmashQwPRVuOKWbxsI1KsRsbGaseiWs5iWnPJwaPD+8QqPQ9dQbTgJzpvJP uWlaGgtHz1Nwccyv2iLHvap5YFV6TlLmWrGPT5AxkFelQ8VUgFRfds15wDO2f1Hl4mdj jWo2U8SAh1zWaYoKKL3yDEUUyzvJSahA3sJVCMwEN3vEIGNyztg/bflY/Bi1QJw3SkBw JOlQ==
X-Gm-Message-State: AOAM531nbUXfNL09mpZNOKGxFkX1xLyMBheW2QH+EO8AfIWd6Dgz7UEt qceOyuAxkkXUkmP2Canw4w==
X-Google-Smtp-Source: ABdhPJwRGixva7pmMH2aa+Y5LEpe7PgnZEPtEhsevrwR5jeEgQVjyV2B6tZPlIYnV3wj7OchqKG3Ug==
X-Received: by 2002:a63:c702:: with SMTP id n2mr25596286pgg.382.1614120711501; Tue, 23 Feb 2021 14:51:51 -0800 (PST)
Received: from ?IPv6:2601:646:9702:c61:c8b:7326:845a:e5f9? ([2601:646:9702:c61:c8b:7326:845a:e5f9]) by smtp.gmail.com with ESMTPSA id h3sm26528pgm.67.2021.02.23.14.51.50 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Tue, 23 Feb 2021 14:51:51 -0800 (PST)
From: Yingzhen Qu <yingzhen.ietf@gmail.com>
Message-Id: <126DD0AA-51E3-43E2-8EC0-93EBBD4476BC@gmail.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_CAE3D041-3E03-4687-9432-FDB924DF516B"
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.40.0.2.32\))
Date: Tue, 23 Feb 2021 14:51:49 -0800
In-Reply-To: <SN6PR13MB2334A418AB20A157F03A7A8585809@SN6PR13MB2334.namprd13.prod.outlook.com>
Cc: "lsr@ietf.org" <lsr@ietf.org>, "Acee Lindem (acee)" <acee@cisco.com>, Christian Hopps <chopps@chopps.org>
To: Linda Dunbar <linda.dunbar@futurewei.com>
References: <SN6PR13MB2334A418AB20A157F03A7A8585809@SN6PR13MB2334.namprd13.prod.outlook.com>
X-Mailer: Apple Mail (2.3654.40.0.2.32)
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/_-cg-EEzOPjYzzPJ2efgX88Z8nc>
Subject: Re: [Lsr] Request a 10 minute slot at IETF110 LSR session to brief the draft-dunbar-lsr-5g-edge-compute-ospf-ext
X-BeenThere: lsr@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Link State Routing Working Group <lsr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/lsr>, <mailto:lsr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/lsr/>
List-Post: <mailto:lsr@ietf.org>
List-Help: <mailto:lsr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lsr>, <mailto:lsr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Feb 2021 22:51:54 -0000

Hi Linda,

I've noted down your request, and the agenda will be arranged based on all the requests received. Please pay attention to the agenda when posted.

Thanks,
Yingzhen

> On Feb 23, 2021, at 8:03 AM, Linda Dunbar <linda.dunbar@futurewei.com> wrote:
> 
> Acee, Christian, and YingZhen, 
>  
> Can we have a 10-minutes slot at the IETF 110 LSR session to brief thehttps://datatracker.ietf.org/doc/draft-dunbar-lsr-5g-edge-compute-ospf-ext/ <https://datatracker.ietf.org/doc/draft-dunbar-lsr-5g-edge-compute-ospf-ext/> ?
>  
>  
> Based on the mailing list discussion, we have revised the https://datatracker.ietf.org/doc/draft-dunbar-lsr-5g-edge-compute-ospf-ext/ <https://datatracker.ietf.org/doc/draft-dunbar-lsr-5g-edge-compute-ospf-ext/>. 
>  
> In particular, 
> For App Servers using IPv6, the OSPFv3 Extended LSA with the Intra-Area-Prefix Address TLV specified by the Section 3.7 of RFC8362 can be used to carry the App-Metrics for the attached App Servers.  
>   0                   1                   2                   3
>   0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
>  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> |7 (IPv6 Local-Local Address)   |               Length          |
> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> |            IPv6 AppServer (ANYCAST) address                   |
> ~                                                               ~
> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> |            Load measurement sub-TLV                            <>|
> ~                                                               ~
> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> |            Capability sub-TLV                                 |
> ~                                                               ~
> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> |             Preference sub-TLV                                |
> ~                                                               ~
> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>        Figure 3:  <>IPv6 App Server App-Metrics Encoding
>  
> For App Servers using IPv4 addresses, the OSPFv2 Extended Prefix Opaque LSA with the extended Prefix TLV can be used to carry the App Metrics sub-TLVs, as specified by the Section 2.1 [RFC7684].
>  
> Here is the proposed encoding:
>  
> 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> | Type                          | Length                        |
> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> | Route Type    | Prefix Length | AF            | Flags         |
> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> | Address Prefix (variable)                                     |
> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 
> | Load Measurement Sub-TLV                                      |
> ~                                                               ~
> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 
> | capacity Index Sub-TLV                                        |
> ~                                                               ~
> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 
> | Site Preference Sub-TLV                                       |
> ~                                                               ~ 
> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 
>  
>  
> Your comments and suggestions are greatly appreciated. 
>  
> Linda Dunbar
>  
> From: Acee Lindem (acee) <acee@cisco.com <mailto:acee@cisco.com>> 
> Sent: Tuesday, November 3, 2020 1:38 PM
> To: Linda Dunbar <linda.dunbar@futurewei.com <mailto:linda.dunbar@futurewei.com>>; Yingzhen Qu <yingzhen.ietf@gmail.com <mailto:yingzhen.ietf@gmail.com>>;lsr@ietf.org <mailto:lsr@ietf.org>; lsr-chairs@ietf.org <mailto:lsr-chairs@ietf.org>
> Subject: Re: Need 10 minute slot to discuss OSPF extension for 5G Edge Computing (was RE: [Lsr] IETF 109 LSR Presentation Slot Requests
>  
> We have a pretty full schedule and we add you as optional. I took a look at the draft and it is all over the place right now with standardization requested for one solution but 3 separate solutions partially specified. It could benefit from some WG mailing list discussion prior to a 10 minute presentation where we wouldn’t have time to discuss the many issues.
>  
> One major issue is that you should be extending RFC 7684 rather than RFC 3630 and it seems you these app-server selection metrics should be associated with a prefix and NOT a stub link (i.e., the application server address).
>  
> I’ll try to read it in more depth before IETF 109. 
>  
> Thanks,
> Acee
>  
> From: Linda Dunbar <linda.dunbar@futurewei.com <mailto:linda.dunbar@futurewei.com>>
> Date: Monday, November 2, 2020 at 10:12 PM
> To: Yingzhen Qu <yingzhen.ietf@gmail.com <mailto:yingzhen.ietf@gmail.com>>, "lsr@ietf.org <mailto:lsr@ietf.org>" <lsr@ietf.org <mailto:lsr@ietf.org>>, "lsr-chairs@ietf.org <mailto:lsr-chairs@ietf.org>" <lsr-chairs@ietf.org <mailto:lsr-chairs@ietf.org>>
> Subject: Need 10 minute slot to discuss OSPF extension for 5G Edge Computing (was RE: [Lsr] IETF 109 LSR Presentation Slot Requests
> Resent-From: <alias-bounces@ietf.org <mailto:alias-bounces@ietf.org>>
> Resent-To: Yingzhen Qu <yingzhen.ietf@gmail.com <mailto:yingzhen.ietf@gmail.com>>, Acee Lindem <acee@cisco.com <mailto:acee@cisco.com>>, Christian Hopps <chopps@chopps.org <mailto:chopps@chopps.org>>
> Resent-Date: Monday, November 2, 2020 at 10:12 PM
>  
> LSR Chairs, YingZhen, 
>  
> Can you give us 10 minute slot to present this new draft:
> https://datatracker.ietf.org/doc/draft-dunbar-lsr-5g-edge-compute-ospf-ext/ <https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fdraft-dunbar-lsr-5g-edge-compute-ospf-ext%2F&data=04%7C01%7Clinda.dunbar%40futurewei.com%7C83f990f38fe14407efe208d880300245%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C637400290992237706%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=CooHUjUYe%2BePz9rwBZe0orzPqku%2BoSL%2FrMVVa%2Fl2uIc%3D&reserved=0>
>  
> This draft describes an OSPF extension that can distribute the 5G Edge Computing App running status and environment, so that other routers in the 5G Local Data Network can make intelligent decision on optimizing forwarding of flows from UEs. The goal is to improve latency and performance for 5G Edge Computing services. <>
>  
> Thank you very much, 
>  
> Linda Dunbar
>  
> From: Lsr <lsr-bounces@ietf.org <mailto:lsr-bounces@ietf.org>> On Behalf Of Yingzhen Qu
> Sent: Monday, October 19, 2020 3:52 PM
> To: lsr@ietf.org <mailto:lsr@ietf.org>; lsr-chairs@ietf.org <mailto:lsr-chairs@ietf.org>
> Subject: [Lsr] IETF 109 LSR Presentation Slot Requests
>  
> Hi all, 
>  
> We're now accepting agenda requests for the LSR Working Grouping meeting IETF 109. Please send your requests to lsr-chairs@ietf.org <mailto:lsr-chairs@ietf.org> indicating draft name, speaker, and desired duration (covering presentation and discussion). 
>  
> LSR session is scheduled on Monday, Nov 16, 12:00-14:00 ICT.
>  
> Thanks,
> Yingzhen