Re: [I2nsf] draft-ietf-i2nsf-capability-05 is officially removed from I2NSF WG ( was RE: Is there any objection of sunset the I2NSF Capabilities Information Model Draft and merge the relevant information to the I2NSF Capability Data model draft?

Linda Dunbar <dunbar.ll@gmail.com> Sat, 24 October 2020 21:57 UTC

Return-Path: <dunbar.ll@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 6EACF3A0BFE for <i2nsf@ietfa.amsl.com>; Sat, 24 Oct 2020 14:57:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.464
X-Spam-Level:
X-Spam-Status: No, score=-0.464 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, LH_URI_DOM_IN_PATH=1.533, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 TdgyTCvr6oPK for <i2nsf@ietfa.amsl.com>; Sat, 24 Oct 2020 14:57:31 -0700 (PDT)
Received: from mail-ed1-x52a.google.com (mail-ed1-x52a.google.com [IPv6:2a00:1450:4864:20::52a]) (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 126023A0B2D for <i2nsf@ietf.org>; Sat, 24 Oct 2020 14:57:30 -0700 (PDT)
Received: by mail-ed1-x52a.google.com with SMTP id a6so3963823edx.6 for <i2nsf@ietf.org>; Sat, 24 Oct 2020 14:57:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=1u+1/bPQV+0BcoGoXfNfTuDbxePNf0C+NEvwtTtXwnM=; b=fG5mh6RkCzY3BdnVN62UOuTuEF4mxLiCZ2+DO+tuK3f8FRzt03nUdotcVov+MVov9g Y9/7VG0AS4g7IAK9n0jVzC8Df1tZ6WgjOX5SFWbhod6ME2WMUaUM4yvzBh6/dJZnofVH 1ls9MIaxoSN4bwKx7YNSJy9xxamtx8+ejzwyCxaRB2ZmXAblV4EJZmhlMiI0W88qMjr2 r0U4j7xwLn0+ULRV9PcnSToVXJ7wKV4rIz1h4hPr9D39TOFdxNKvb949rZDWQbgL4sh5 BEJo5SetxeD88CjPQEpSMjomKHi1bZRLk9nEvC9fd2fKF/EarNTu0A4XRHAyi1kHzWLq MI1A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=1u+1/bPQV+0BcoGoXfNfTuDbxePNf0C+NEvwtTtXwnM=; b=gjA4CoJ4cV/0P5KKgiZIPSMYTT6iDiorB81vSQTSZQM9N5FPosS43wa2CWy6TSw3Sp vrIJpDXMgkOttiQYYijcxQJ2rT9DoaYpb6HCLGW79SxrsB0WsOzTP88+U/gQqto8cOfh r54BvLpGlabbHwDKz2CH1pjtNDzPsjMCi0x/LI0gE4UiFfSvod5D1p+v3fFjT6TwxcEp EuXGRrlVsC/8KR6eoyowb923+PNtaulqkdUu+Vkca0Xlok9tpZy9YPrEhlneP+fqtJ0b BlZj9cCPf1Xym91JaGHZyeXuZTiHcio3ePflkMSUpcfv00xeyAk4fxjFnck7Wxqwf3o1 mkbg==
X-Gm-Message-State: AOAM5336tyTHjvI3Lu3cYSTT2/Dx6hXUgh6yaDWKFmL5JJ3Nx4WjhJMw 09Kj69hLUzb6AuTIWZh4+vSPqhtXOjykYvCDtzc=
X-Google-Smtp-Source: ABdhPJyChXdZVs+6qpu+TFX1Ay1BTFyFcHSTcAcRo28hpedeMehplUI47EAusC5wXZ/VX+jrqzC6TBJvFuyHvOyEVYw=
X-Received: by 2002:a50:dac1:: with SMTP id s1mr8891005edj.74.1603576649305; Sat, 24 Oct 2020 14:57:29 -0700 (PDT)
MIME-Version: 1.0
References: <CAPK2DewMACWfR50824XEvfjMQPF7jcyTKAN7npiXnFvPHGT7OA@mail.gmail.com> <6DBEDEEF-2EE4-49AF-A7F0-A257499C34F8@gmail.com> <CAPK2DexF7qwLCYh_mCFiHVBPaT=ccX1TBTeRUt+w8sDNauGfPQ@mail.gmail.com> <CAPK2DezD84CwB1E6tNgrn7AEPiypnYRtBRdZcCvVR1CWEMK6sA@mail.gmail.com>
In-Reply-To: <CAPK2DezD84CwB1E6tNgrn7AEPiypnYRtBRdZcCvVR1CWEMK6sA@mail.gmail.com>
From: Linda Dunbar <dunbar.ll@gmail.com>
Date: Sat, 24 Oct 2020 16:57:18 -0500
Message-ID: <CAP_bo1YtBL0ns=02shB77KSoY=VGLODbc9NLYNi7q9gnUJPo_Q@mail.gmail.com>
To: "Mr. Jaehoon Paul Jeong" <jaehoon.paul@gmail.com>
Cc: Yoav Nir <ynir.ietf@gmail.com>, "i2nsf@ietf.org" <i2nsf@ietf.org>, skku-iotlab-members <skku-iotlab-members@googlegroups.com>
Content-Type: multipart/alternative; boundary="0000000000008d562c05b271c87f"
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2nsf/d2i1Agu6emMcg-9ABTi_0__c2xA>
Subject: Re: [I2nsf] draft-ietf-i2nsf-capability-05 is officially removed from I2NSF WG ( was RE: Is there any objection of sunset the I2NSF Capabilities Information Model Draft and merge the relevant information to the I2NSF Capability Data model draft?
X-BeenThere: i2nsf@ietf.org
X-Mailman-Version: 2.1.29
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: Sat, 24 Oct 2020 21:57:36 -0000

Paul,

Thank you very much for the update.

Linda

On Fri, Oct 23, 2020 at 9:29 PM Mr. Jaehoon Paul Jeong <
jaehoon.paul@gmail.com> wrote:

> Hi Linda and Yoav,
> I need more time to merge the information model and data model for
> draft-ietf-i2nsf-capability-data-model along with the reflection of the
> IESG's comments:
> https://datatracker.ietf.org/doc/draft-ietf-i2nsf-capability-data-model/
>
> I will try to do the merging and the reflection of the comments of the
> IESG by IETF-109 I-D due (11/02/2020).
>
> Thanks.
>
> Best Regards,
> Paul
>
>
> On Sat, Oct 10, 2020 at 10:33 AM Mr. Jaehoon Paul Jeong <
> jaehoon.paul@gmail.com> wrote:
>
>> Linda,
>> I see.
>>
>> I will do the merging.
>>
>> Thanks.
>>
>> Best Regards,
>> Paul
>>
>> 2020년 10월 10일 (토) 오전 10:20, Linda <dunbar.ll@gmail.com>님이 작성:
>>
>>> Yes
>>> Linda
>>>
>>> Sent from my iPhone
>>>
>>> On Oct 9, 2020, at 7:55 PM, Mr. Jaehoon Paul Jeong <
>>> jaehoon.paul@gmail.com> wrote:
>>>
>>> 
>>> Hi Linda,
>>> As I understand, I need to merge the relevant contents of the NSFs
>>> Capability Information Model Draft into the I2NSF NSF Capability Data Model
>>> Draft.
>>>
>>> Is it correct?
>>>
>>> Thanks.
>>>
>>> Best Regards,
>>> Paul
>>>
>>> 2020년 10월 9일 (금) 오후 11:58, Linda Dunbar <linda.dunbar@futurewei.com>님이
>>> 작성:
>>>
>>>> I2NSF WG,
>>>>
>>>>
>>>>
>>>> Correction:
>>>>
>>>>
>>>>
>>>> There has been NO object to the Author’s request for sunsetting the
>>>> draft-ietf-i2nsf-capability-5.
>>>>
>>>>
>>>>
>>>> We have marked the draft as “DEAD” in the WG status.
>>>>
>>>>
>>>>
>>>> Many thanks to the authors for putting the effort in this draft for
>>>> kickstarting all the data models in I2NSF WG.
>>>>
>>>>
>>>>
>>>> Linda & Yoav
>>>>
>>>>
>>>>
>>>> *From:* Linda Dunbar
>>>> *Sent:* Thursday, October 8, 2020 4:36 PM
>>>> *To:* i2nsf@ietf.org
>>>> *Subject:* draft-ietf-i2nsf-capability-05 is officially removed from
>>>> I2NSF WG ( was RE: Is there any objection of sunset the I2NSF Capabilities
>>>> Information Model Draft and merge the relevant information to the I2NSF
>>>> Capability Data model draft?
>>>>
>>>>
>>>>
>>>> I2nsf WG,
>>>>
>>>>
>>>>
>>>> There has been any objection to the Author’s request for sunsetting the
>>>>  draft-ietf-i2nsf-capability-05.
>>>>
>>>>
>>>>
>>>> Authors of the draft-ietf-i2nsf-capability-data-model: please remove
>>>> the reference to the Capability Information Model and upload a new draft.
>>>> We can ask IESG to re-review it.
>>>>
>>>>
>>>>
>>>> Thank you very much.
>>>>
>>>>
>>>>
>>>> Linda & Yoav.
>>>>
>>>>
>>>>
>>>> *From:* Linda Dunbar
>>>> *Sent:* Monday, September 28, 2020 11:00 AM
>>>> *To:* i2nsf@ietf.org
>>>> *Subject:* Is there any objection of sunset the I2NSF Capabilities
>>>> Information Model Draft and merge the relevant information to the I2NSF
>>>> Capability Data model draft?
>>>>
>>>>
>>>>
>>>> I2NSF WG,
>>>>
>>>>
>>>>
>>>> As Diego has expressed that the original I2NSF capability information
>>>> model was based on a policy expression calculus suitable for manipulating
>>>> high-level policy expressions.  The capability data model has been evolving
>>>> in a quite reasonable and pragmatic way, including running code at the
>>>> hackathons.
>>>>
>>>>
>>>>
>>>> The I2NSF Capability Information Model has fulfilled its purpose of
>>>> kickstarting and guiding the data model, and the authors believe that it is
>>>> better to let the capability information model to be withdrawn. For the
>>>> content in the information model still relevant to I2NSF Capability Data
>>>> Model, they should be merged into the Capability Data Model.
>>>>
>>>>
>>>>
>>>> Is there any objection from the WG?  If we don’t hear any objection by
>>>> Oct 5, we will change the status of the draft.
>>>>
>>>>
>>>>
>>>> Cheers,
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> Linda & Yoav
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> *From:* Diego R. Lopez <diego.r.lopez@telefonica.com>
>>>> *Sent:* Tuesday, September 22, 2020 5:35 PM
>>>> *To:* Linda Dunbar <linda.dunbar@futurewei.com>; Mr. Jaehoon Paul
>>>> Jeong <jaehoon.paul@gmail.com>
>>>> *Cc:* Xialiang (Frank) <frank.xialiang@huawei.com>; Yoav Nir <
>>>> ynir.ietf@gmail.com>; John Strassner <John.sc.Strassner@huawei.com>;
>>>> Aldo Basile <cataldo.basile@polito.it>; Roman Danyliw <rdd@cert.org>
>>>> *Subject:* Re: Offer for Revision Help for I2NSF NSFs Capabilities
>>>> Information Model Draft
>>>>
>>>>
>>>>
>>>> Hi Linda,
>>>>
>>>>
>>>>
>>>> I’d prefer the second option, as it seems more straightforward and
>>>> natural to me, and in parallel would like you to consider the idea of an
>>>> I2NSF extension allowing us to reuse the capability model for
>>>> policy-control transformation, and to incorporate the attestation matters
>>>> you know I was so much interested in.
>>>>
>>>>
>>>>
>>>> Be goode,
>>>>
>>>>
>>>>
>>>> --
>>>>
>>>> "Esta vez no fallaremos, Doctor Infierno"
>>>>
>>>>
>>>>
>>>> Dr Diego R. Lopez
>>>>
>>>> Telefonica I+D
>>>>
>>>> https://www.linkedin.com/in/dr2lopez/
>>>> <https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.linkedin.com%2Fin%2Fdr2lopez%2F&data=02%7C01%7Clinda.dunbar%40futurewei.com%7C08a48858d7bd4d843a6e08d85f47b438%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C637364108864949633&sdata=ROR4%2FyD1WqWDb1rCbJx3ERqTiMCQ92ibkyz26kYZdD8%3D&reserved=0>
>>>>
>>>>
>>>>
>>>>
>>>> e-mail: diego.r.lopez@telefonica.com
>>>>
>>>> Tel:         +34 913 129 041
>>>>
>>>> Mobile:  +34 682 051 091
>>>>
>>>> ----------------------------------
>>>>
>>>>
>>>>
>>>> On 22/09/2020, 18:01, "Linda Dunbar" <linda.dunbar@futurewei.com>
>>>> wrote:
>>>>
>>>>
>>>>
>>>> Diego:
>>>>
>>>>
>>>>
>>>> Thank you very much for the reflection of the Capabilities Information
>>>> Model Draft. Agree with your statement that “the capability data model was
>>>> evolving in a quite reasonable and pragmatic way, including running code at
>>>> the hackathons”.
>>>>
>>>>
>>>>
>>>> Looks like Eric Vyncke still wants the information model to be fixed to
>>>> clear his “DISCUSS” ballot.
>>>>
>>>> How about the following steps:
>>>>
>>>> -          Ask Roman’s advice if we can simplify the Information Model
>>>> mainly to reflect what has been in the Data Model.
>>>>
>>>> -          Or, drop the Information model draft and remove the refence
>>>> to the draft, but Roman has to convince Eric to agree not having the
>>>> information model.
>>>>
>>>>
>>>>
>>>> What do you think?
>>>>
>>>>
>>>>
>>>> Linda
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> *From:* Diego R. Lopez <diego.r.lopez@telefonica.com>
>>>> *Sent:* Tuesday, September 22, 2020 9:50 AM
>>>> *To:* Mr. Jaehoon Paul Jeong <jaehoon.paul@gmail.com>; Linda Dunbar <
>>>> linda.dunbar@futurewei.com>
>>>> *Cc:* Xialiang (Frank) <frank.xialiang@huawei.com>; Yoav Nir <
>>>> ynir.ietf@gmail.com>; John Strassner <John.sc.Strassner@huawei.com>;
>>>> Aldo Basile <cataldo.basile@polito.it>; Roman Danyliw <rdd@cert.org>
>>>> *Subject:* Re: Offer for Revision Help for I2NSF NSFs Capabilities
>>>> Information Model Draft
>>>>
>>>>
>>>>
>>>> Hi Paul,
>>>>
>>>>
>>>>
>>>> Before you go for it, let me share with you some reflections on the
>>>> state of the draft, in the spirit of what I replied to Eric Vyncke.
>>>>
>>>>
>>>>
>>>> I must confess there has been a combination of events that made me
>>>> think the best solution was to leave this draft to fade away. First, I was
>>>> not (have not been yet) able to find a solution to most of Roman’s comments
>>>> without totally rewriting most, if not all, of the document.  Second, the
>>>> fact that the capability data model was evolving in a quite reasonable and
>>>> pragmatic way, including running code at the hackathons, following the
>>>> spirit of the initial work in the information model, but not attempting to
>>>> align with its most recent evolution. If I have not shared this position
>>>> before is because I have been looking for a way to make the idea of
>>>> bridging capability declarations and security policy statements at the
>>>> I2NSF controller viable, and I was hoping to find such a way by reusing
>>>> part of the capability info model draft.
>>>>
>>>>
>>>>
>>>> As I told Eric, I believe the current capability model has a powerful
>>>> (though probably not yet complete) calculus for policy description and
>>>> validation, but not directly related to the management mechanisms addressed
>>>> in the capability data model and the other data models produced in I2NSF. I
>>>> believe there is an opportunity for accomplishing policy-capability
>>>> bridging, using as foundation the current capability model, though it seems
>>>> to me that this task would require some time to consolidate and therefore
>>>> imply an extension of the I2NSF lifetime. I would like to know your
>>>> position(*) about such an extension,  that could also become an opportunity
>>>> to work in other matters related to attestation (in the light of the work
>>>> in RATS and the MUD initiative within the Ops Area) and accounting.
>>>>
>>>>
>>>>
>>>> Be goode,
>>>>
>>>>
>>>>
>>>> (*) I assume you are in favor, Paul. But I’d like to get Linda’s,
>>>> Yoav’s and Roman’s ideas, as well as the availability to work on this from
>>>> Frank, John and Aldo.
>>>>
>>>>
>>>>
>>>> --
>>>>
>>>> "Esta vez no fallaremos, Doctor Infierno"
>>>>
>>>>
>>>>
>>>> Dr Diego R. Lopez
>>>>
>>>> Telefonica I+D
>>>>
>>>> https://www.linkedin.com/in/dr2lopez/
>>>> <https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.linkedin.com%2Fin%2Fdr2lopez%2F&data=02%7C01%7Clinda.dunbar%40futurewei.com%7C08a48858d7bd4d843a6e08d85f47b438%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C637364108864949633&sdata=ROR4%2FyD1WqWDb1rCbJx3ERqTiMCQ92ibkyz26kYZdD8%3D&reserved=0>
>>>>
>>>>
>>>>
>>>>
>>>> e-mail: diego.r.lopez@telefonica.com
>>>>
>>>> Tel:         +34 913 129 041
>>>>
>>>> Mobile:  +34 682 051 091
>>>>
>>>> ----------------------------------
>>>>
>>>>
>>>>
>>>> On 17/09/2020, 01:42, "Mr. Jaehoon Paul Jeong" <jaehoon.paul@gmail.com>
>>>> wrote:
>>>>
>>>>
>>>>
>>>> Hi Linda,
>>>>
>>>> I will address our AD Roman's comments on this NSFs capabilities
>>>> information draft as the 2nd editor through the collaboration with Frank
>>>> (the 1st editor) and the other authors.
>>>>
>>>>
>>>>
>>>> I CC our AD Roman and the other authors, such as John and Cataldo.
>>>>
>>>>
>>>>
>>>> Thanks for your support and guidance.
>>>>
>>>>
>>>>
>>>> Best Regards,
>>>>
>>>> Paul
>>>>
>>>>
>>>>
>>>> 2020년 9월 17일 (목) 오전 3:44, Linda Dunbar <linda.dunbar@futurewei.com>님이
>>>> 작성:
>>>>
>>>> Paul,
>>>>
>>>>
>>>>
>>>> Thank you very much for offering to address the AD comments to this
>>>> draft. Looks like the current authors are too busy to address those
>>>> comments. It has been over a year since the AD comments were given.  We
>>>> need to move the draft forward. Therefore, I2NSF chairs have authorized you
>>>> to be one of the editors to address the AD comments and revise the draft.
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> Thank you very much.
>>>>
>>>>
>>>>
>>>> Linda & Yoav
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> *From:* Mr. Jaehoon Paul Jeong <jaehoon.paul@gmail.com>
>>>> *Sent:* Sunday, September 13, 2020 10:09 AM
>>>> *To:* Xialiang (Frank) <frank.xialiang@huawei.com>
>>>> *Cc:* Linda Dunbar <linda.dunbar@futurewei.com>; Yoav Nir <
>>>> ynir.ietf@gmail.com>; DIEGO LOPEZ GARCIA <diego.r.lopez@telefonica.com>;
>>>> Jaehoon Jeong <jaehoon.paul@gmail.com>
>>>> *Subject:* Offer for Revision Help for I2NSF NSFs Capabilities
>>>> Information Model Draft
>>>>
>>>>
>>>>
>>>> Hi Frank,
>>>>
>>>> Could I help you to revise your information model draft for our AD
>>>> Roman Danyliw's review comments  as a co-editor?
>>>>
>>>>
>>>> https://datatracker.ietf.org/doc/draft-ietf-i2nsf-capability/?include_text=1
>>>> <https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fdraft-ietf-i2nsf-capability%2F%3Finclude_text%3D1&data=02%7C01%7Clinda.dunbar%40futurewei.com%7C08a48858d7bd4d843a6e08d85f47b438%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C637364108864959626&sdata=GUrbaYu2Q4N1YNUUet2oVRPqbynA78cSBTf%2FBeSCY44%3D&reserved=0>
>>>>
>>>>
>>>>
>>>> As you know, I have finished our I2NSF data model drafts.
>>>>
>>>>
>>>>
>>>> I am happy to work on the revision with you in order to complete our
>>>> I2NSF deliverables.
>>>>
>>>>
>>>>
>>>> Thanks.
>>>>
>>>>
>>>>
>>>> Best Regards,
>>>>
>>>> Paul
>>>>
>>>>
>>>> ------------------------------
>>>>
>>>>
>>>> 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 privileged and
>>>> confidential 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
>>>>
>>>>
>>>> ------------------------------
>>>>
>>>>
>>>> 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 privileged and
>>>> confidential 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
>>>> https://www.ietf.org/mailman/listinfo/i2nsf
>>>>
>>> _______________________________________________
>>> I2nsf mailing list
>>> I2nsf@ietf.org
>>> https://www.ietf.org/mailman/listinfo/i2nsf
>>>
>>>
>