Re: [I2nsf] IETF 114 I2NSF agenda uploaded
Rafa Marín López <rafa@um.es> Fri, 22 July 2022 08:25 UTC
Return-Path: <rafa@um.es>
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 80E7AC13195C for <i2nsf@ietfa.amsl.com>; Fri, 22 Jul 2022 01:25:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 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, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=um.es
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 oiZlF4fPRNQ5 for <i2nsf@ietfa.amsl.com>; Fri, 22 Jul 2022 01:25:31 -0700 (PDT)
Received: from mx01.puc.rediris.es (outbound4mad.lav.puc.rediris.es [130.206.19.145]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 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 900E9C159482 for <i2nsf@ietf.org>; Fri, 22 Jul 2022 01:25:30 -0700 (PDT)
Authentication-Results: mx01.puc.rediris.es; spf=pass (rediris.es: domain of rafa@um.es designates 155.54.212.169 as permitted sender) smtp.mailfrom=rafa@um.es
Received: from xenon42.um.es (xenon42.um.es [155.54.212.169]) by mx01.puc.rediris.es with ESMTP id 26M8P8P3031505-26M8P8P4031505; Fri, 22 Jul 2022 10:25:08 +0200
Received: from localhost (localhost [127.0.0.1]) by xenon42.um.es (Postfix) with ESMTP id 83CB42171A; Fri, 22 Jul 2022 10:25:08 +0200 (CEST)
X-Virus-Scanned: by antispam in UMU at xenon42.um.es
Received: from xenon42.um.es ([127.0.0.1]) by localhost (xenon42.um.es [127.0.0.1]) (amavisd-new, port 10024) with LMTP id cZ-20PIbj5Wp; Fri, 22 Jul 2022 10:25:08 +0200 (CEST)
Received: from smtpclient.apple (inf-205-228.inf.um.es [155.54.205.228]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: rafa@um.es) by xenon42.um.es (Postfix) with ESMTPSA id A4DB121718; Fri, 22 Jul 2022 10:25:04 +0200 (CEST)
From: Rafa Marín López <rafa@um.es>
Message-Id: <D570EFE5-3FA1-4D33-96FE-56464192458B@um.es>
Content-Type: multipart/alternative; boundary="Apple-Mail=_5A1E0880-00C7-44CE-8678-CBBBF324B1B6"
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.120.0.1.13\))
Date: Fri, 22 Jul 2022 10:25:04 +0200
In-Reply-To: <0746A38E-1BA0-46C0-8460-D8C308BD6180@telefonica.com>
Cc: Rafa Marín López <rafa@um.es>, Susan Hares <shares@ndzh.com>, "Mr. Jaehoon Paul Jeong" <jaehoon.paul@gmail.com>, Linda Dunbar <linda.dunbar@futurewei.com>, "i2nsf@ietf.org" <i2nsf@ietf.org>, skku-iotlab-members <skku-iotlab-members@googlegroups.com>
To: "Diego R. Lopez" <diego.r.lopez@telefonica.com>
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> <CAPK2Dey5PyeHgFyZavibpD27+QeJK6c0nYaqDLC-nnYyJCko1w@mail.gmail.com> <BYAPR08MB4872C030D80DFA15B2D0148BB38E9@BYAPR08MB4872.namprd08.prod.outlook.com> <0746A38E-1BA0-46C0-8460-D8C308BD6180@telefonica.com>
X-Mailer: Apple Mail (2.3654.120.0.1.13)
X-FEAS-SPF: spf-result=pass, ip=155.54.212.169, helo=xenon42.um.es, mailFrom=rafa@um.es
X-FE-Policy-ID: 23:15:4:SYSTEM
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; d=um.es; s=DKIM; c=relaxed/relaxed; h=from:message-id:content-type:mime-version:subject:date:cc:to:references; bh=wSIkLP34tfrjfjUjl6WaryTfnYVnDvFWC3oZI11rhvU=; b=QZfe1w40WZO49jAlnn+wKl0UOJQdNKqlgz1vAPXVcG+peNtYwABr3UxGbSwEdeVjuup1m1PflpXu Bn5HyUR1p6JLpZZd3rZ9sRQJ6pfeG117KsW083mnFqKUQYwUKdkbfeMd8agXurZAiBn2XmM0cEme 0MUsKm+z3NooM6AbOWhXUg9HuQXJxyFJSkMrBk1MHKBsP4vtjhK2wb+viwrtMdMLZcLRYvUofBwz HGDrmpjBTeMOr5o5pJNgJqRaPJhvC9XxBCl9MYAMXj1TkGFeyYTXQ2OxPxyU7HAosB/5IEex0fnH WnOObn2AzdZv3rVcnFaczEVPT741Zr1MZZAi0Q==
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2nsf/Tl_Yh94uh9CBZqbfAJFrehWjAnQ>
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: Fri, 22 Jul 2022 08:25:35 -0000
Dear all: If it can be of any help, we would like to join this meeting so we could provide our view on this regard related to RFC 9061. In our case, we would have to connect online since we will not be there. Best Regards. > El 22 jul 2022, a las 0:08, Diego R. Lopez <diego.r.lopez@telefonica.com> escribió: > > Hi, > > I will be in Philadelphia as well, arriving this Friday evening and staying for the whole week. And happy to talk with you on the issue! > > Be goode, > > -- > "Esta vez no fallaremos, Doctor Infierno" > > Dr Diego R. Lopez > Telefonica I+D > https://www.linkedin.com/in/dr2lopez/ <https://www.linkedin.com/in/dr2lopez/> > > e-mail: diego.r.lopez@telefonica.com <mailto:diego.r.lopez@telefonica.com> > Mobile: +34 682 051 091 > ---------------------------------- > > On 21/7/22, 01:07, "Susan Hares" <shares@ndzh.com <mailto:shares@ndzh.com>> wrote: > > Paul: > > Thank you for the generous offer. Let me check with my co-authors. > > Sue > > From: Mr. Jaehoon Paul Jeong <jaehoon.paul@gmail.com <mailto:jaehoon.paul@gmail.com>> > Sent: Wednesday, July 20, 2022 6:35 PM > To: Susan Hares <shares@ndzh.com <mailto:shares@ndzh.com>> > Cc: Diego R. Lopez <diego.r.lopez@telefonica.com <mailto:diego.r.lopez@telefonica.com>>; Linda Dunbar <linda.dunbar@futurewei.com <mailto:linda.dunbar@futurewei.com>>; Mr. Jaehoon Paul Jeong <jaehoon.paul@gmail.com <mailto:jaehoon.paul@gmail.com>>; i2nsf@ietf.org <mailto:i2nsf@ietf.org>; skku-iotlab-members <skku-iotlab-members@googlegroups.com <mailto:skku-iotlab-members@googlegroups.com>> > Subject: Re: [I2nsf] IETF 114 I2NSF agenda uploaded > > > 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 <mailto: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 <mailto:diego.r.lopez@telefonica.com>> >> Sent: Wednesday, July 20, 2022 11:48 AM >> To: Mr. Jaehoon Paul Jeong <jaehoon.paul@gmail.com <mailto:jaehoon.paul@gmail.com>>; Susan Hares <shares@ndzh.com <mailto:shares@ndzh.com>> >> Cc: Linda Dunbar <linda.dunbar@futurewei.com <mailto:linda.dunbar@futurewei.com>>; i2nsf@ietf.org <mailto:i2nsf@ietf.org>; skku-iotlab-members <skku-iotlab-members@googlegroups.com <mailto: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/ <https://www.linkedin.com/in/dr2lopez/> >> >> e-mail: diego.r.lopez@telefonica.com <mailto: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 <mailto:i2nsf-bounces@ietf.org> on behalf of jaehoon.paul@gmail.com <mailto: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 <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 <mailto: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 <mailto:linda.dunbar@futurewei.com>> >>> Sent: Tuesday, July 19, 2022 6:09 PM >>> To: Susan Hares <shares@ndzh.com <mailto:shares@ndzh.com>>; i2nsf@ietf.org <mailto: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 <mailto:shares@ndzh.com>> >>> Sent: Tuesday, July 19, 2022 3:00 PM >>> To: Linda Dunbar <linda.dunbar@futurewei.com <mailto:linda.dunbar@futurewei.com>>; i2nsf@ietf.org <mailto: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 <mailto:i2nsf-bounces@ietf.org>> On Behalf Of Linda Dunbar >>> Sent: Tuesday, July 19, 2022 3:44 PM >>> To: i2nsf@ietf.org <mailto: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 <mailto:I2nsf@ietf.org> >>> https://www.ietf.org/mailman/listinfo/i2nsf <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 <mailto:pauljeong@skku.edu>, jaehoon.paul@gmail.com <mailto:jaehoon.paul@gmail.com> > Personal Homepage: http://iotlab.skku.edu/people-jaehoon-jeong.php <http://cpslab.skku.edu/people-jaehoon-jeong.php> > > 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 > _______________________________________________ > I2nsf mailing list > I2nsf@ietf.org <mailto:I2nsf@ietf.org> > https://www.ietf.org/mailman/listinfo/i2nsf <https://www.ietf.org/mailman/listinfo/i2nsf> ------------------------------------------------------ Rafa Marin-Lopez, PhD Dept. Information and Communications Engineering (DIIC) Faculty of Computer Science-University of Murcia 30100 Murcia - Spain Telf: +34868888501 Fax: +34868884151 e-mail: rafa@um.es -------------------------------------------------------
- [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