Re: [I2nsf] IETF 114 I2NSF agenda uploaded
"Mr. Jaehoon Paul Jeong" <jaehoon.paul@gmail.com> Wed, 20 July 2022 15:38 UTC
Return-Path: <jaehoon.paul@gmail.com>
X-Original-To: i2nsf@ietfa.amsl.com
Delivered-To: i2nsf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 482FBC188719 for <i2nsf@ietfa.amsl.com>; Wed, 20 Jul 2022 08:38:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.994
X-Spam-Level:
X-Spam-Status: No, score=-1.994 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, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_HK_NAME_FM_MR_MRS=0.01, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=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 ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jjOJP0WrLmgT for <i2nsf@ietfa.amsl.com>; Wed, 20 Jul 2022 08:38:40 -0700 (PDT)
Received: from mail-io1-xd33.google.com (mail-io1-xd33.google.com [IPv6:2607:f8b0:4864:20::d33]) (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 75384C13C515 for <i2nsf@ietf.org>; Wed, 20 Jul 2022 08:38:40 -0700 (PDT)
Received: by mail-io1-xd33.google.com with SMTP id z132so14595467iof.0 for <i2nsf@ietf.org>; Wed, 20 Jul 2022 08:38:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=P06xyJee48sTz1YYKUmUpM8E57bCzhFT75UOR/59Dpg=; b=pFidyTF8sMKfJ86/Lvp8eTyWQEB1Qs3tAv70pEnASqshvgDl6/+BfoZZ/Kxsg5E7IA XSj+ucwYLb3Lrc9F61naoyWZoKFZQsPYThezMrL6UeZ9FMJi/xHn+FnP9Hz30uqZiCc5 c/PFzfnYxGMOG+PQmp1/D8UjV075vEB2EGxeUvd4P3UJ+2KnOqeo3KIXYWl1Ro7MEhwI 0pQFyZxTDFnNS9BJb98OcjurCqc+kbRjxgMIiWieh3fDN7XVWTkh0KODdF9hoZbBLGkD q7kf+doZyvn9rtFcLPYwLDCwTUWtog3795If3qkR6WNbNI6EKlLENiITWmEgav+J/78q p8nQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=P06xyJee48sTz1YYKUmUpM8E57bCzhFT75UOR/59Dpg=; b=xOJw0HQ/mzMN31r0fJRC17JX1cdIuPx64XCU5VT7pO++NvNXX9QSVAglGwG2DNQnf5 jjalLotSn2rQ4Fo/F1epWjm3v23Yb1Y6EJCDiC/v8D3HytHG04uyGzjywxGgwZkGiOjj pq8v5RMJZk31mtiFvd2YjDy7EO5dnqzmeC+Un1ktHKVvNnKH7cGteh/C4mShdkoAw97S tqyOBPMo0DF06omVZ0UrIdn9wEaInCY1DzdbmN8LbG6+8svK4g/QUUp1RMUeUjry+44o DchAGx7rgLBD4NnlcOb+E8o0fmpVnF02DZG2MwmUGdfwj6TNhRIuatQ5puVVsKSpztBd 8ltA==
X-Gm-Message-State: AJIora+nP0TzSroPourMvnlt8F+8ilGdQEY8jU6YWpJFn6rDdbdnR5qM Xk20OfN9IFXt51gdZuyICHaW8FRZGTuZNZ/I4B0=
X-Google-Smtp-Source: AGRyM1sKVtfjABWN9JuFndWeQcIzF9DT8uDs4v+gpm2bX/qen7M+0au273n+YBJ//NpY7gHy8o/adNThG9yTRSoZyus=
X-Received: by 2002:a05:6602:3cc:b0:679:61e7:3928 with SMTP id g12-20020a05660203cc00b0067961e73928mr18462094iov.217.1658331519695; Wed, 20 Jul 2022 08:38:39 -0700 (PDT)
MIME-Version: 1.0
References: <CO1PR13MB49205BB48AB81D9BE50E0E77858F9@CO1PR13MB4920.namprd13.prod.outlook.com> <BYAPR08MB4872301332C1854F7DA78AFFB38F9@BYAPR08MB4872.namprd08.prod.outlook.com> <CO1PR13MB4920200D70DC11FBF9DDA04E858F9@CO1PR13MB4920.namprd13.prod.outlook.com> <BYAPR08MB48722EA2CCAD37AC12960FEFB38E9@BYAPR08MB4872.namprd08.prod.outlook.com>
In-Reply-To: <BYAPR08MB48722EA2CCAD37AC12960FEFB38E9@BYAPR08MB4872.namprd08.prod.outlook.com>
From: "Mr. Jaehoon Paul Jeong" <jaehoon.paul@gmail.com>
Date: Thu, 21 Jul 2022 00:38:05 +0900
Message-ID: <CAPK2Dex2zkoNxr7F9vvbTm6r9OvAmtUcmY=Fd279Xaq_uCWcsA@mail.gmail.com>
To: Susan Hares <shares@ndzh.com>
Cc: Linda Dunbar <linda.dunbar@futurewei.com>, "i2nsf@ietf.org" <i2nsf@ietf.org>, skku-iotlab-members <skku-iotlab-members@googlegroups.com>, "Mr. Jaehoon Paul Jeong" <jaehoon.paul@gmail.com>
Content-Type: multipart/alternative; boundary="00000000000026c20d05e43e658d"
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2nsf/hqRy-zlfxKY4ZLAaFFDt2iYwb60>
Subject: Re: [I2nsf] IETF 114 I2NSF agenda uploaded
X-BeenThere: i2nsf@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "*I2NSF: Interface to Network Security Functions mailing list*" <i2nsf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/i2nsf>, <mailto:i2nsf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/i2nsf/>
List-Post: <mailto:i2nsf@ietf.org>
List-Help: <mailto:i2nsf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/i2nsf>, <mailto:i2nsf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Jul 2022 15:38:41 -0000
Hi Sue, I have much interest in your proposed item. I think the following RFC 9061 can be used for the IPsec interface for BGP over IPsec. - RFC 9061: A YANG Data Model for IPsec Flow Protection Based on Software-Defined Networking (SDN) https://datatracker.ietf.org/doc/html/rfc9061 We can regard BGP routers as NSFs, and we can run either IKE or IKE-less approach in RFC 9061. We can also extend the approach in RFC 9061 so that it can accommodate BGP message exchanges (e.g., AS-PATH and NEXT-HOP attributes). I will investigate RFC 9061 more to see whether my comments are correct or not. Thanks. Best Regards, Paul On Wed, Jul 20, 2022 at 8:55 PM Susan Hares <shares@ndzh.com> wrote: > Linda: > > > > I apologize for being unclear. We ran into a few problems with trying to > complete the BGP Yang model in the area of IPsec links. BGP runs over TCP > over IPsec links in some scenarios. When creating the modeling, it was > unclear which Yang modules were targeted to support this feature. > > > > What I need is advice from the I2NSF and the IPSECME on the place to ask > for work additions to support BGP peers. > > > > The scenario is between two BGP routers. The type of IPsec connections > between BGP routers can be: > > - within a trusted cloud (same administrative domain, same trust > cloud), > - across a physically secure private link, > - across the open Internet (where attacks happen). > > > > The key is we want to configure and monitor the IPsec link. > > > > As BGP co-authors looked at this, I did not understand which group to ask > help from. I volunteered to ask for help. > > > > If you or anyone can point me to where to go without taking valuable WG > time, it would be great. If you need me to explain more on email, I’d be > glad to. > > > > Rather than just pose this question from the Mike-line, I thought I’d ask > ahead of time. > > > > Cheers, sue > > > > *From:* Linda Dunbar <linda.dunbar@futurewei.com> > *Sent:* Tuesday, July 19, 2022 6:09 PM > *To:* Susan Hares <shares@ndzh.com>; i2nsf@ietf.org > *Subject:* RE: IETF 114 I2NSF agenda uploaded > > > > > > Sue, > > > > Are you talking about IPsec between two trusted nodes? > > Something different from the IPsecme WG? > > > > Linda > > > > *From:* Susan Hares <shares@ndzh.com> > *Sent:* Tuesday, July 19, 2022 3:00 PM > *To:* Linda Dunbar <linda.dunbar@futurewei.com>; i2nsf@ietf.org > *Subject:* RE: IETF 114 I2NSF agenda uploaded > > > > Linda: > > > > In the recharter discussion, is it appropriate to ask about specific items > such as additions to ipsec work in I2NSF? > > I do not have a draft for this work. > > > > Sue > > > > *From:* I2nsf <i2nsf-bounces@ietf.org> *On Behalf Of *Linda Dunbar > *Sent:* Tuesday, July 19, 2022 3:44 PM > *To:* i2nsf@ietf.org > *Subject:* [I2nsf] IETF 114 I2NSF agenda uploaded > > > > > > I2NSF WG, > > > > Here is the agenda for next week’s I2NSF session (Tuesday). > > > > https://datatracker.ietf.org/doc/agenda-114-i2nsf/ > <https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fagenda-114-i2nsf%2F&data=05%7C01%7Clinda.dunbar%40futurewei.com%7C8b5d4da98b89456a579d08da69c1548c%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C1%7C637938576342441642%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000%7C%7C%7C&sdata=N040a56pN%2BLVElz5IOt4jddwoHRH1pKTpTkAPMhd%2BD4%3D&reserved=0> > > > > Please let me know if I miss anything. > > > > Thank you. > > Linda > _______________________________________________ > I2nsf mailing list > I2nsf@ietf.org > https://www.ietf.org/mailman/listinfo/i2nsf >
- [I2nsf] IETF 114 I2NSF agenda uploaded Linda Dunbar
- Re: [I2nsf] IETF 114 I2NSF agenda uploaded Susan Hares
- Re: [I2nsf] IETF 114 I2NSF agenda uploaded Linda Dunbar
- Re: [I2nsf] IETF 114 I2NSF agenda uploaded Susan Hares
- Re: [I2nsf] IETF 114 I2NSF agenda uploaded Linda Dunbar
- Re: [I2nsf] IETF 114 I2NSF agenda uploaded Mr. Jaehoon Paul Jeong
- Re: [I2nsf] IETF 114 I2NSF agenda uploaded Diego R. Lopez
- Re: [I2nsf] IETF 114 I2NSF agenda uploaded Susan Hares
- Re: [I2nsf] IETF 114 I2NSF agenda uploaded Mr. Jaehoon Paul Jeong
- Re: [I2nsf] IETF 114 I2NSF agenda uploaded Susan Hares
- Re: [I2nsf] IETF 114 I2NSF agenda uploaded Diego R. Lopez
- Re: [I2nsf] IETF 114 I2NSF agenda uploaded Rafa Marín López
- Re: [I2nsf] IETF 114 I2NSF agenda uploaded Rafa Marín López
- Re: [I2nsf] IETF 114 I2NSF agenda uploaded Mr. Jaehoon Paul Jeong
- Re: [I2nsf] IETF 114 I2NSF agenda uploaded Rafa Marin-Lopez