Re: [I2nsf] IETF 114 I2NSF agenda uploaded

"Mr. Jaehoon Paul Jeong" <jaehoon.paul@gmail.com> Wed, 20 July 2022 22:35 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 06CE3C13493F for <i2nsf@ietfa.amsl.com>; Wed, 20 Jul 2022 15:35:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.993
X-Spam-Level:
X-Spam-Status: No, score=-1.993 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_DNSWL_BLOCKED=0.001, 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 mCNHbTK7mmeM for <i2nsf@ietfa.amsl.com>; Wed, 20 Jul 2022 15:35:08 -0700 (PDT)
Received: from mail-io1-xd2b.google.com (mail-io1-xd2b.google.com [IPv6:2607:f8b0:4864:20::d2b]) (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 D250CC14CF09 for <i2nsf@ietf.org>; Wed, 20 Jul 2022 15:35:08 -0700 (PDT)
Received: by mail-io1-xd2b.google.com with SMTP id h145so25404iof.9 for <i2nsf@ietf.org>; Wed, 20 Jul 2022 15:35:08 -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=Qf4qiJozFcCWpHYSdR02TjEkvDMSfGWZsJigBh44rhE=; b=eJSc9pmmrYYrR9xX92t1C0iMkkTlqzLqYRSfzC7dgvKcFIqPDA+N1av9IPeWcg8bjI 5Kw8LVL9gpopFp7qEB1s/Z08/GKbLiK7K8D8w4g77vwSjjefSLbpXhZ5vk4tpkWOrkIl mXTIESthwM5HFvM/6v8Mb6jy6UYRmh725lhQGj6h6v63tiO2ksxbEEizyYdFjNSAvNit CGV0op41rsQ2+UPV/Jgf5R1GUHxrUSYv8Mf5oCLk6Cb5HCUBN1YhFQRAMRsOr6tOxn3B VySSdTmniqvE//LjyKIVHTCKRfwvwqmIdG4Hs4uirUkZDRwm/KgPOKqwLnr9isB8qaPT Y2+w==
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=Qf4qiJozFcCWpHYSdR02TjEkvDMSfGWZsJigBh44rhE=; b=DX6xSUgGtC4XbAUCAcOsxHqt6uyf//E1UM8xKPWmsQTYgQGYvnVx1CzjKCsP/xiXsp MUVyZ4eeLm/CxJo9afORDFeHmboThFoQdhSpDfB+jGa/dPj1D+OqvLE3b9J9Sw0TSLbc bRZZC3U0qKOs/W9bojKLtjK5BLFy3j9KoWmHZPcVq+hOqknhH923z7VuqxfwOWzGRLK4 uJdlMvpBVtinqCeXGITFXPen2xcfKK9mUMs8vsj7W1eVAaqaZeBxGVd2uQ0MU8/KM7hD 158jv9HZ2lHTJQuAGd23KZyxKdEE4ux26fMZEtJP9xS5mYPqBhjEUIoogTYSfZJLFeTa w1RA==
X-Gm-Message-State: AJIora94j4Yabahi9EnxE8jC/TdJ3qjEc02HCFpRho40+IQvldwn16aM UXjPnocjuD0IHhpGlg6hewpyVge1EXk/x+CsHOo=
X-Google-Smtp-Source: AGRyM1uQ55GKLJTpGRziVOjdo9mIBznIvXkVh+sp9Zify9R/ntO175eQnOluGxaBaulH79H46mIi8p6hBjp+c2b+HSE=
X-Received: by 2002:a05:6602:3cc:b0:679:61e7:3928 with SMTP id g12-20020a05660203cc00b0067961e73928mr19184413iov.217.1658356507763; Wed, 20 Jul 2022 15:35:07 -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> <CAPK2Dex2zkoNxr7F9vvbTm6r9OvAmtUcmY=Fd279Xaq_uCWcsA@mail.gmail.com> <FE34E26E-8243-4FD1-BA77-FE7BBC565F41@telefonica.com> <BYAPR08MB4872524536D072AFCE1B1AC3B38E9@BYAPR08MB4872.namprd08.prod.outlook.com>
In-Reply-To: <BYAPR08MB4872524536D072AFCE1B1AC3B38E9@BYAPR08MB4872.namprd08.prod.outlook.com>
From: "Mr. Jaehoon Paul Jeong" <jaehoon.paul@gmail.com>
Date: Thu, 21 Jul 2022 07:34:56 +0900
Message-ID: <CAPK2Dey5PyeHgFyZavibpD27+QeJK6c0nYaqDLC-nnYyJCko1w@mail.gmail.com>
To: Susan Hares <shares@ndzh.com>
Cc: "Diego R. Lopez" <diego.r.lopez@telefonica.com>, Linda Dunbar <linda.dunbar@futurewei.com>, "Mr. Jaehoon Paul Jeong" <jaehoon.paul@gmail.com>, "i2nsf@ietf.org" <i2nsf@ietf.org>, skku-iotlab-members <skku-iotlab-members@googlegroups.com>
Content-Type: multipart/alternative; boundary="0000000000008e69f205e44436ab"
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2nsf/odYr9mXnI1jtKx95Onw1Cw2e7kM>
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 22:35:13 -0000

Sue,
I will attend the IETF 114 on site, so I will be available
for the meeting with your BGP authors.
Please let me know the time and place for our meeting.

Thanks.

Best Regards,
Paul

2022년 7월 21일 (목) 오전 7:23, Susan Hares <shares@ndzh.com>님이 작성:

> Paul and Diego:
>
>
>
> Let me know if you have time to chat.  If you are attending IETF in
> person, we can chat in-person.  The 4 authors for the BGP will be at
> IETF-14 in person (Mahesh, Sue, Keyur, Jeff).
>
>
>
> If you are not attending in person, we’ll set-up a teleconference (zoom,
> etc.. )
>
>
>
> Linda – We may be able to take this off the agenda.
>
>
>
> Sue
>
>
>
> *From:* Diego R. Lopez <diego.r.lopez@telefonica.com>
> *Sent:* Wednesday, July 20, 2022 11:48 AM
> *To:* Mr. Jaehoon Paul Jeong <jaehoon.paul@gmail.com>; Susan Hares <
> shares@ndzh.com>
> *Cc:* Linda Dunbar <linda.dunbar@futurewei.com>; i2nsf@ietf.org;
> skku-iotlab-members <skku-iotlab-members@googlegroups.com>
> *Subject:* Re: [I2nsf] IETF 114 I2NSF agenda uploaded
>
>
>
>
>
> Hi,
>
>
>
> I totally concur with Paul here. We have some experience in applying RFC
> 9061 in different scenarios and would be more than happy to explore its
> applicability in this case as well.
>
>
>
> Be goode,
>
>
>
> --
>
> "Esta vez no fallaremos, Doctor Infierno"
>
>
>
> Dr Diego R. Lopez
>
> Telefonica I+D
>
> https://www.linkedin.com/in/dr2lopez/
>
>
>
> e-mail: diego.r.lopez@telefonica.com
>
> Mobile:  +34 682 051 091
>
> ----------------------------------
>
>
>
> On 20/7/22, 17:38, "I2nsf on behalf of Mr. Jaehoon Paul Jeong" <
> i2nsf-bounces@ietf.org on behalf of jaehoon.paul@gmail.com> wrote:
>
>
>
> 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
>
>
> ------------------------------
>
>
> Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario,
> puede contener información privilegiada o confidencial y es para uso
> exclusivo de la persona o entidad de destino. Si no es usted. el
> destinatario indicado, queda notificado de que la lectura, utilización,
> divulgación y/o copia sin autorización puede estar prohibida en virtud de
> la legislación vigente. Si ha recibido este mensaje por error, le rogamos
> que nos lo comunique inmediatamente por esta misma vía y proceda a su
> destrucción.
>
> The information contained in this transmission is confidential and
> privileged information intended only for the use of the individual or
> entity named above. If the reader of this message is not the intended
> recipient, you are hereby notified that any dissemination, distribution or
> copying of this communication is strictly prohibited. If you have received
> this transmission in error, do not read it. Please immediately reply to the
> sender that you have received this communication in error and then delete
> it.
>
> Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinatário,
> pode conter informação privilegiada ou confidencial e é para uso exclusivo
> da pessoa ou entidade de destino. Se não é vossa senhoria o destinatário
> indicado, fica notificado de que a leitura, utilização, divulgação e/ou
> cópia sem autorização pode estar proibida em virtude da legislação vigente.
> Se recebeu esta mensagem por erro, rogamos-lhe que nos o comunique
> imediatamente por esta mesma via e proceda a sua destruição
>
-- 
===========================
Mr. Jaehoon (Paul) Jeong, Ph.D.
Associate Professor
Department Head
Department of Computer Science and Engineering
Sungkyunkwan University
Office: +82-31-299-4957
Email: pauljeong@skku.edu, jaehoon.paul@gmail.com
Personal Homepage: http://iotlab.skku.edu/people-jaehoon-jeong.php
<http://cpslab.skku.edu/people-jaehoon-jeong.php>