
From nobody Mon Oct  5 11:03:45 2020
Return-Path: <noreply@ietf.org>
X-Original-To: i2nsf@ietf.org
Delivered-To: i2nsf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id EA24C3A0B12; Mon,  5 Oct 2020 11:03:42 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Andy Bierman via Datatracker <noreply@ietf.org>
To: <yang-doctors@ietf.org>
Cc: i2nsf@ietf.org, draft-ietf-i2nsf-nsf-monitoring-data-model.all@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 7.19.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <160192102291.6633.15935674903085952087@ietfa.amsl.com>
Reply-To: Andy Bierman <andy@yumaworks.com>
Date: Mon, 05 Oct 2020 11:03:42 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2nsf/t0iHC_Xbgm6NaM4W83IHX6XjyHg>
Subject: [I2nsf] Yangdoctors early review of draft-ietf-i2nsf-nsf-monitoring-data-model-04
X-BeenThere: i2nsf@ietf.org
X-Mailman-Version: 2.1.29
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: Mon, 05 Oct 2020 18:03:43 -0000

Reviewer: Andy Bierman
Review result: Almost Ready



Major Issues:

 - None

Moderate Issues:

 - top-level 'counters' container does not follow naming conventions.
   Should start with 'i2nsf', probably 'i2nsf-state'

 - There do not seem to be any writable objects in the /counters
   subtree so this container should have a 'config false' statement

 - top-level typedef and grouping description-stmts are self-referential
   and not useful. Need to rewrite description-stmts and/or add
   reference-stmts as needed.

 - grouping common-monitoring-data/time-stamp
   Is this a different time stamp than the one in the NETCONF notification?
   The 'message generation time' sounds like the standard timestamp.
   Does this object represent the event detection time?

 - grouping i2nsf-system-alarm-type-content/usage
 - grouping i2nsf-system-alarm-type-content/threshold
   These are uint8 leafs with unclear descriptions.
   Not sure why uint8 is the appropriate type.
   Needs 1 or more of (reference, units, better description)

 - grouping traffic-rates
   Add a units statement to each leaf. Not sure what units to use
   but it should be consistent. (e.g, pps, bps used in descriptions
   should also be in a units-stmt)

 - grouping i2nsf-system-counter-type-content
   These counters should use the yang:counter32 type instead of uint32

 - container counters/system-interface
 - container counters/nsf-firewall
 - container counters/nsf-policy-hits
  The descriptions are too terse and confusing, and need a rewrite.

 -  container counters/nsf-firewall
 -  container counters/nsf-policy-hits
    - uses i2nsf-nsf-counters-type-content;
    Many of the fields expanded from this grouping all say
    they refer to 'the packet'. Why are they in this global
    container of counters? E.g. (src-ip, dst-ip, src-port, dst-port)
    Not clear at all how the server is supposed to apply this
    grouping to these containers.

 - many leafs use "uint32" type for a rate.
   Should add a units-stmt

 - leaf counters/nsf-policy-hits/hit-times
   The purpose and type are confusing and generic.
   If this is a counter then use counter32

 - cut-and-paste for notification-stmt content should be replaced
   with grouping/uses instead. Applies to the nsf-detection-*
   and the various logging notifications. Even a grouping that
   has 1 object in it is better than cut-and-paste 5+ times

Minor Issues:

 - top-level identifiers are too generic
   should have 'i2nsf-' prefix to be more reusable outside this module

 - quite a lot of identities that an implementation is required to support.
   If this set of identities might change a lot faster than the
   notifications and counter objects, then consider putting them
   in a separate module

 - leaf with same type named differently; both intrusion-attack-type
   - nsf-detection-intrusion/sub-attack-type
   - nsf-log-intrusion/attack-type

 - quite a lot of notification event types for a server to implement
   and a user to manage. All are mandatory (no if-feature statements).
   Some such as nsf-detection-* subset are very similar.
   A section or table would be useful that showed the YANG notification
   names and their purpose -- maybe a reference to another RFC
   with more details

 - there seems to be notifications for intrusion events and then
   again for the logging of those events.  This seems excessive
   but


 - grouping common-monitoring-data/time-stamp
   Is this a different time stamp than the one in the NETCONF notification?
   The 'message generation time' sounds like the standard timestamp.
   Is this event detection time?

 - grouping common-monitoring-data/module-name
   Is this a YANG module or some other type of module?

 - there is no way to configure which notifications should be generated
   or maybe how often.  YANG Push has its own dampening-period.
   Since these are event stream subscriptions, not datastore subscriptions,
   YANG-Push does not apply to this document at all.

   If there are a lot of notifications then a server implementation
   might drop some

 - grouping i2nsf-nsf-event-type-content-extend/src-zone
 - grouping i2nsf-nsf-event-type-content-extend/src-zone
   These use type 'string'. Consider using a typedef that constrains
   the string.  General comment where unconstrained string is used:
   The corner-case values such as empty string are often not allowed
   in implementations.


 - grouping i2nsf-nsf-event-type-content-extend/rule-id
 - grouping i2nsf-nsf-event-type-content-extend/rule-name
 - grouping i2nsf-nsf-event-type-content-extend/profile
   These objects seem to reference objects in another YANG module.
   If so, then leafref types might be more appropriate.

 - grouping i2nsf-nsf-event-type-content/rule-id
 - grouping i2nsf-nsf-event-type-content/rule-name
 - grouping i2nsf-nsf-event-type-content/profile
 - grouping i2nsf-nsf-event-type-content/raw-info
   These objects are cut-and-paste duplicates from
   grouping i2nsf-nsf-event-type-content. They should
   be in a separate grouping used by both. Also applies
   to some other sets of objects

 - limits issues (e.g. current-session, maximum-session
   The type is uint8. This is only OK it is impossible for any
   implementation to ever have or want more than 255 of them.
   If some other RFC really does limit the values where uint8
   is used, then that is OK. If so, a reference-stmt would help.




From nobody Mon Oct  5 19:30:50 2020
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 37FB13A0F58; Mon,  5 Oct 2020 19:30:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.086
X-Spam-Level: 
X-Spam-Status: No, score=-2.086 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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_HK_NAME_FM_MR_MRS=0.01, URIBL_BLOCKED=0.001, URI_DOTEDU=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 qyVlGjq_A0OI; Mon,  5 Oct 2020 19:30:46 -0700 (PDT)
Received: from mail-lf1-x134.google.com (mail-lf1-x134.google.com [IPv6:2a00:1450:4864:20::134]) (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 83A963A0F54; Mon,  5 Oct 2020 19:30:42 -0700 (PDT)
Received: by mail-lf1-x134.google.com with SMTP id 197so13247764lfo.11; Mon, 05 Oct 2020 19:30:42 -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=41cA6L1hPvCKpcd0k/4y+4CJxHXk/JUd32+zO5fOG4c=; b=KDuofRnR++kIygz/9X4cIrol4Z+UnIyC7IPBv5cCsedQjg24GiuuSmMg9BFlSmqIm6 rtZPxAjKEy94JOMzLLhzejE1QIssAX96aJXwl3rTt2Lp+vgBiaB7yPSNTVI0nfTUohWu /qx388Vp2efDn+axECm8ssN6kkyQY3bpknNLRuWEI7ZmLOMBevYCYk8dJe7sJdEI87vg 6KY3m78TBTnynJoM/1939A/Ox3xG3msObBZs/w2BswdHCdXIm6b7vOThjPLnU4oA5T5O jSjGUZmfwkcupqB3PpIk94xr95eySWAXmRgz8YGYdTDfmKVBuEYQFAzJO504eUcnOBb1 BVLQ==
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=41cA6L1hPvCKpcd0k/4y+4CJxHXk/JUd32+zO5fOG4c=; b=D0yp7A6y8lGLT8g6n000N3X1tO+NqoFBj1kue3iZ9hFSGDEaKnyd3bPfCJOEX81pyY Ct0DXIY+p5Fp4wFYfYmuFwdvlNffQwcduyjz8GatgIKLwyuBzxkwdmV1yBE42dJLqljy /jJChADd6M9EvovKCUMmOZlnAFGOZGOBklFA3FMd521PYO6E0Sf4t2hjzDZemmmDv2DB xKH4j+pY0XeSbWrqiQu4F5aNyWoHwzFEqxn0mbpqMGyh1hZ1pCjGXCzAF6BoKkJfNFKT SOCt72wifiAKufXcBiv5vu/1VwVwiWZUfzJl+YZO0D0JaziUsxtAw5kyYkdHG1nE+k6q 5oGw==
X-Gm-Message-State: AOAM533d1YcnkN0vHX3EbT2quTJx7va70u5qEmjc0i8xh+J0F5Gq39co obh5t+I6gsN6KyDJLMUz/EFLZ9gjNVldDjYT0+s=
X-Google-Smtp-Source: ABdhPJw/kauThX9FOm9gDrSgGCwxwOEV1lR1tWRseK1cV8bCtzYEfsqd0/e1yHCvt+HW6EFBxdQDUMYuZdain8SCOGk=
X-Received: by 2002:ac2:41d8:: with SMTP id d24mr661550lfi.458.1601951440442;  Mon, 05 Oct 2020 19:30:40 -0700 (PDT)
MIME-Version: 1.0
References: <160192102291.6633.15935674903085952087@ietfa.amsl.com>
In-Reply-To: <160192102291.6633.15935674903085952087@ietfa.amsl.com>
From: "Mr. Jaehoon Paul Jeong" <jaehoon.paul@gmail.com>
Date: Tue, 6 Oct 2020 11:30:07 +0900
Message-ID: <CAPK2DewOF7QcTD8UdFYdoGUvnJz_fxb53OOn-KmYQgNA38xLoA@mail.gmail.com>
To: Andy Bierman <andy@yumaworks.com>
Cc: YANG Doctors <yang-doctors@ietf.org>, "i2nsf@ietf.org" <i2nsf@ietf.org>,  draft-ietf-i2nsf-nsf-monitoring-data-model.all@ietf.org,  Patrick Lingga <patricklink888@gmail.com>,  "Mr. Jaehoon Paul Jeong" <jaehoon.paul@gmail.com>
Content-Type: multipart/alternative; boundary="0000000000008e1a4405b0f762ef"
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2nsf/hYWSJh7own2JXjwgDbMvpdd8ceg>
Subject: Re: [I2nsf] Yangdoctors early review of draft-ietf-i2nsf-nsf-monitoring-data-model-04
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: Tue, 06 Oct 2020 02:30:48 -0000

--0000000000008e1a4405b0f762ef
Content-Type: text/plain; charset="UTF-8"

Hi Andy,
Thanks for your valuable comments on our NSF Monitoring YANG Data Model
Draft.
We authors will reflect your comments on the revision and come back to you
with
the revised draft and revision letter.

Thanks.

Best Regards,
Paul


On Tue, Oct 6, 2020 at 3:03 AM Andy Bierman via Datatracker <
noreply@ietf.org> wrote:

> Reviewer: Andy Bierman
> Review result: Almost Ready
>
>
>
> Major Issues:
>
>  - None
>
> Moderate Issues:
>
>  - top-level 'counters' container does not follow naming conventions.
>    Should start with 'i2nsf', probably 'i2nsf-state'
>
>  - There do not seem to be any writable objects in the /counters
>    subtree so this container should have a 'config false' statement
>
>  - top-level typedef and grouping description-stmts are self-referential
>    and not useful. Need to rewrite description-stmts and/or add
>    reference-stmts as needed.
>
>  - grouping common-monitoring-data/time-stamp
>    Is this a different time stamp than the one in the NETCONF notification?
>    The 'message generation time' sounds like the standard timestamp.
>    Does this object represent the event detection time?
>
>  - grouping i2nsf-system-alarm-type-content/usage
>  - grouping i2nsf-system-alarm-type-content/threshold
>    These are uint8 leafs with unclear descriptions.
>    Not sure why uint8 is the appropriate type.
>    Needs 1 or more of (reference, units, better description)
>
>  - grouping traffic-rates
>    Add a units statement to each leaf. Not sure what units to use
>    but it should be consistent. (e.g, pps, bps used in descriptions
>    should also be in a units-stmt)
>
>  - grouping i2nsf-system-counter-type-content
>    These counters should use the yang:counter32 type instead of uint32
>
>  - container counters/system-interface
>  - container counters/nsf-firewall
>  - container counters/nsf-policy-hits
>   The descriptions are too terse and confusing, and need a rewrite.
>
>  -  container counters/nsf-firewall
>  -  container counters/nsf-policy-hits
>     - uses i2nsf-nsf-counters-type-content;
>     Many of the fields expanded from this grouping all say
>     they refer to 'the packet'. Why are they in this global
>     container of counters? E.g. (src-ip, dst-ip, src-port, dst-port)
>     Not clear at all how the server is supposed to apply this
>     grouping to these containers.
>
>  - many leafs use "uint32" type for a rate.
>    Should add a units-stmt
>
>  - leaf counters/nsf-policy-hits/hit-times
>    The purpose and type are confusing and generic.
>    If this is a counter then use counter32
>
>  - cut-and-paste for notification-stmt content should be replaced
>    with grouping/uses instead. Applies to the nsf-detection-*
>    and the various logging notifications. Even a grouping that
>    has 1 object in it is better than cut-and-paste 5+ times
>
> Minor Issues:
>
>  - top-level identifiers are too generic
>    should have 'i2nsf-' prefix to be more reusable outside this module
>
>  - quite a lot of identities that an implementation is required to support.
>    If this set of identities might change a lot faster than the
>    notifications and counter objects, then consider putting them
>    in a separate module
>
>  - leaf with same type named differently; both intrusion-attack-type
>    - nsf-detection-intrusion/sub-attack-type
>    - nsf-log-intrusion/attack-type
>
>  - quite a lot of notification event types for a server to implement
>    and a user to manage. All are mandatory (no if-feature statements).
>    Some such as nsf-detection-* subset are very similar.
>    A section or table would be useful that showed the YANG notification
>    names and their purpose -- maybe a reference to another RFC
>    with more details
>
>  - there seems to be notifications for intrusion events and then
>    again for the logging of those events.  This seems excessive
>    but
>
>
>  - grouping common-monitoring-data/time-stamp
>    Is this a different time stamp than the one in the NETCONF notification?
>    The 'message generation time' sounds like the standard timestamp.
>    Is this event detection time?
>
>  - grouping common-monitoring-data/module-name
>    Is this a YANG module or some other type of module?
>
>  - there is no way to configure which notifications should be generated
>    or maybe how often.  YANG Push has its own dampening-period.
>    Since these are event stream subscriptions, not datastore subscriptions,
>    YANG-Push does not apply to this document at all.
>
>    If there are a lot of notifications then a server implementation
>    might drop some
>
>  - grouping i2nsf-nsf-event-type-content-extend/src-zone
>  - grouping i2nsf-nsf-event-type-content-extend/src-zone
>    These use type 'string'. Consider using a typedef that constrains
>    the string.  General comment where unconstrained string is used:
>    The corner-case values such as empty string are often not allowed
>    in implementations.
>
>
>  - grouping i2nsf-nsf-event-type-content-extend/rule-id
>  - grouping i2nsf-nsf-event-type-content-extend/rule-name
>  - grouping i2nsf-nsf-event-type-content-extend/profile
>    These objects seem to reference objects in another YANG module.
>    If so, then leafref types might be more appropriate.
>
>  - grouping i2nsf-nsf-event-type-content/rule-id
>  - grouping i2nsf-nsf-event-type-content/rule-name
>  - grouping i2nsf-nsf-event-type-content/profile
>  - grouping i2nsf-nsf-event-type-content/raw-info
>    These objects are cut-and-paste duplicates from
>    grouping i2nsf-nsf-event-type-content. They should
>    be in a separate grouping used by both. Also applies
>    to some other sets of objects
>
>  - limits issues (e.g. current-session, maximum-session
>    The type is uint8. This is only OK it is impossible for any
>    implementation to ever have or want more than 255 of them.
>    If some other RFC really does limit the values where uint8
>    is used, then that is OK. If so, a reference-stmt would help.
>
>
>
> _______________________________________________
> I2nsf mailing list
> I2nsf@ietf.org
> https://www.ietf.org/mailman/listinfo/i2nsf
>


-- 
===========================
Mr. Jaehoon (Paul) Jeong, Ph.D.
Associate Professor
Department of Computer Science and Engineering
Sungkyunkwan University
Office: +82-31-299-4957
Email: jaehoon.paul@gmail.com, pauljeong@skku.edu
Personal Homepage: http://iotlab.skku.edu/people-jaehoon-jeong.php
<http://cpslab.skku.edu/people-jaehoon-jeong.php>

--0000000000008e1a4405b0f762ef
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi Andy,<div>Thanks for your valuable comments on our NSF =
Monitoring YANG Data Model Draft.</div><div>We authors will reflect your co=
mments on the revision and come back to you with</div><div>the revised draf=
t and revision letter.</div><div><br></div><div>Thanks.</div><div><br></div=
><div>Best Regards,</div><div>Paul</div><div><br></div></div><br><div class=
=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Tue, Oct 6, 2020 =
at 3:03 AM Andy Bierman via Datatracker &lt;<a href=3D"mailto:noreply@ietf.=
org">noreply@ietf.org</a>&gt; wrote:<br></div><blockquote class=3D"gmail_qu=
ote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,20=
4);padding-left:1ex">Reviewer: Andy Bierman<br>
Review result: Almost Ready<br>
<br>
<br>
<br>
Major Issues:<br>
<br>
=C2=A0- None<br>
<br>
Moderate Issues:<br>
<br>
=C2=A0- top-level &#39;counters&#39; container does not follow naming conve=
ntions.<br>
=C2=A0 =C2=A0Should start with &#39;i2nsf&#39;, probably &#39;i2nsf-state&#=
39;<br>
<br>
=C2=A0- There do not seem to be any writable objects in the /counters<br>
=C2=A0 =C2=A0subtree so this container should have a &#39;config false&#39;=
 statement<br>
<br>
=C2=A0- top-level typedef and grouping description-stmts are self-referenti=
al<br>
=C2=A0 =C2=A0and not useful. Need to rewrite description-stmts and/or add<b=
r>
=C2=A0 =C2=A0reference-stmts as needed.<br>
<br>
=C2=A0- grouping common-monitoring-data/time-stamp<br>
=C2=A0 =C2=A0Is this a different time stamp than the one in the NETCONF not=
ification?<br>
=C2=A0 =C2=A0The &#39;message generation time&#39; sounds like the standard=
 timestamp.<br>
=C2=A0 =C2=A0Does this object represent the event detection time?<br>
<br>
=C2=A0- grouping i2nsf-system-alarm-type-content/usage<br>
=C2=A0- grouping i2nsf-system-alarm-type-content/threshold<br>
=C2=A0 =C2=A0These are uint8 leafs with unclear descriptions.<br>
=C2=A0 =C2=A0Not sure why uint8 is the appropriate type.<br>
=C2=A0 =C2=A0Needs 1 or more of (reference, units, better description)<br>
<br>
=C2=A0- grouping traffic-rates<br>
=C2=A0 =C2=A0Add a units statement to each leaf. Not sure what units to use=
<br>
=C2=A0 =C2=A0but it should be consistent. (e.g, pps, bps used in descriptio=
ns<br>
=C2=A0 =C2=A0should also be in a units-stmt)<br>
<br>
=C2=A0- grouping i2nsf-system-counter-type-content<br>
=C2=A0 =C2=A0These counters should use the yang:counter32 type instead of u=
int32<br>
<br>
=C2=A0- container counters/system-interface<br>
=C2=A0- container counters/nsf-firewall<br>
=C2=A0- container counters/nsf-policy-hits<br>
=C2=A0 The descriptions are too terse and confusing, and need a rewrite.<br=
>
<br>
=C2=A0-=C2=A0 container counters/nsf-firewall<br>
=C2=A0-=C2=A0 container counters/nsf-policy-hits<br>
=C2=A0 =C2=A0 - uses i2nsf-nsf-counters-type-content;<br>
=C2=A0 =C2=A0 Many of the fields expanded from this grouping all say<br>
=C2=A0 =C2=A0 they refer to &#39;the packet&#39;. Why are they in this glob=
al<br>
=C2=A0 =C2=A0 container of counters? E.g. (src-ip, dst-ip, src-port, dst-po=
rt)<br>
=C2=A0 =C2=A0 Not clear at all how the server is supposed to apply this<br>
=C2=A0 =C2=A0 grouping to these containers.<br>
<br>
=C2=A0- many leafs use &quot;uint32&quot; type for a rate.<br>
=C2=A0 =C2=A0Should add a units-stmt<br>
<br>
=C2=A0- leaf counters/nsf-policy-hits/hit-times<br>
=C2=A0 =C2=A0The purpose and type are confusing and generic.<br>
=C2=A0 =C2=A0If this is a counter then use counter32<br>
<br>
=C2=A0- cut-and-paste for notification-stmt content should be replaced<br>
=C2=A0 =C2=A0with grouping/uses instead. Applies to the nsf-detection-*<br>
=C2=A0 =C2=A0and the various logging notifications. Even a grouping that<br=
>
=C2=A0 =C2=A0has 1 object in it is better than cut-and-paste 5+ times<br>
<br>
Minor Issues:<br>
<br>
=C2=A0- top-level identifiers are too generic<br>
=C2=A0 =C2=A0should have &#39;i2nsf-&#39; prefix to be more reusable outsid=
e this module<br>
<br>
=C2=A0- quite a lot of identities that an implementation is required to sup=
port.<br>
=C2=A0 =C2=A0If this set of identities might change a lot faster than the<b=
r>
=C2=A0 =C2=A0notifications and counter objects, then consider putting them<=
br>
=C2=A0 =C2=A0in a separate module<br>
<br>
=C2=A0- leaf with same type named differently; both intrusion-attack-type<b=
r>
=C2=A0 =C2=A0- nsf-detection-intrusion/sub-attack-type<br>
=C2=A0 =C2=A0- nsf-log-intrusion/attack-type<br>
<br>
=C2=A0- quite a lot of notification event types for a server to implement<b=
r>
=C2=A0 =C2=A0and a user to manage. All are mandatory (no if-feature stateme=
nts).<br>
=C2=A0 =C2=A0Some such as nsf-detection-* subset are very similar.<br>
=C2=A0 =C2=A0A section or table would be useful that showed the YANG notifi=
cation<br>
=C2=A0 =C2=A0names and their purpose -- maybe a reference to another RFC<br=
>
=C2=A0 =C2=A0with more details<br>
<br>
=C2=A0- there seems to be notifications for intrusion events and then<br>
=C2=A0 =C2=A0again for the logging of those events.=C2=A0 This seems excess=
ive<br>
=C2=A0 =C2=A0but<br>
<br>
<br>
=C2=A0- grouping common-monitoring-data/time-stamp<br>
=C2=A0 =C2=A0Is this a different time stamp than the one in the NETCONF not=
ification?<br>
=C2=A0 =C2=A0The &#39;message generation time&#39; sounds like the standard=
 timestamp.<br>
=C2=A0 =C2=A0Is this event detection time?<br>
<br>
=C2=A0- grouping common-monitoring-data/module-name<br>
=C2=A0 =C2=A0Is this a YANG module or some other type of module?<br>
<br>
=C2=A0- there is no way to configure which notifications should be generate=
d<br>
=C2=A0 =C2=A0or maybe how often.=C2=A0 YANG Push has its own dampening-peri=
od.<br>
=C2=A0 =C2=A0Since these are event stream subscriptions, not datastore subs=
criptions,<br>
=C2=A0 =C2=A0YANG-Push does not apply to this document at all.<br>
<br>
=C2=A0 =C2=A0If there are a lot of notifications then a server implementati=
on<br>
=C2=A0 =C2=A0might drop some<br>
<br>
=C2=A0- grouping i2nsf-nsf-event-type-content-extend/src-zone<br>
=C2=A0- grouping i2nsf-nsf-event-type-content-extend/src-zone<br>
=C2=A0 =C2=A0These use type &#39;string&#39;. Consider using a typedef that=
 constrains<br>
=C2=A0 =C2=A0the string.=C2=A0 General comment where unconstrained string i=
s used:<br>
=C2=A0 =C2=A0The corner-case values such as empty string are often not allo=
wed<br>
=C2=A0 =C2=A0in implementations.<br>
<br>
<br>
=C2=A0- grouping i2nsf-nsf-event-type-content-extend/rule-id<br>
=C2=A0- grouping i2nsf-nsf-event-type-content-extend/rule-name<br>
=C2=A0- grouping i2nsf-nsf-event-type-content-extend/profile<br>
=C2=A0 =C2=A0These objects seem to reference objects in another YANG module=
.<br>
=C2=A0 =C2=A0If so, then leafref types might be more appropriate.<br>
<br>
=C2=A0- grouping i2nsf-nsf-event-type-content/rule-id<br>
=C2=A0- grouping i2nsf-nsf-event-type-content/rule-name<br>
=C2=A0- grouping i2nsf-nsf-event-type-content/profile<br>
=C2=A0- grouping i2nsf-nsf-event-type-content/raw-info<br>
=C2=A0 =C2=A0These objects are cut-and-paste duplicates from<br>
=C2=A0 =C2=A0grouping i2nsf-nsf-event-type-content. They should<br>
=C2=A0 =C2=A0be in a separate grouping used by both. Also applies<br>
=C2=A0 =C2=A0to some other sets of objects<br>
<br>
=C2=A0- limits issues (e.g. current-session, maximum-session<br>
=C2=A0 =C2=A0The type is uint8. This is only OK it is impossible for any<br=
>
=C2=A0 =C2=A0implementation to ever have or want more than 255 of them.<br>
=C2=A0 =C2=A0If some other RFC really does limit the values where uint8<br>
=C2=A0 =C2=A0is used, then that is OK. If so, a reference-stmt would help.<=
br>
<br>
<br>
<br>
_______________________________________________<br>
I2nsf mailing list<br>
<a href=3D"mailto:I2nsf@ietf.org" target=3D"_blank">I2nsf@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/i2nsf" rel=3D"noreferrer" =
target=3D"_blank">https://www.ietf.org/mailman/listinfo/i2nsf</a><br>
</blockquote></div><br clear=3D"all"><div><br></div>-- <br><div dir=3D"ltr"=
 class=3D"gmail_signature"><div dir=3D"ltr"><div><div dir=3D"ltr"><div><div=
 dir=3D"ltr"><div><div dir=3D"ltr">=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br>Mr. Jaehoon (Paul) Jeong, Ph.=
D.<br>Associate Professor<br>Department of Computer Science and Engineering=
<br>Sungkyunkwan University<br>Office: +82-31-299-4957<br>Email: <a href=3D=
"mailto:jaehoon.paul@gmail.com" target=3D"_blank">jaehoon.paul@gmail.com</a=
>,=C2=A0<a href=3D"mailto:pauljeong@skku.edu" style=3D"font-size:12.8px" ta=
rget=3D"_blank">pauljeong@skku.edu</a><br>Personal Homepage: <a href=3D"htt=
p://cpslab.skku.edu/people-jaehoon-jeong.php" target=3D"_blank">http://iotl=
ab.skku.edu/people-jaehoon-jeong.php</a><br></div></div></div></div></div><=
/div></div></div>

--0000000000008e1a4405b0f762ef--


From nobody Mon Oct  5 20:31:02 2020
Return-Path: <andy@yumaworks.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 6D1D83A0FD7 for <i2nsf@ietfa.amsl.com>; Mon,  5 Oct 2020 20:31:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.886
X-Spam-Level: 
X-Spam-Status: No, score=-1.886 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001, URI_DOTEDU=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=yumaworks-com.20150623.gappssmtp.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 1HtwkRV7n3x9 for <i2nsf@ietfa.amsl.com>; Mon,  5 Oct 2020 20:30:58 -0700 (PDT)
Received: from mail-lj1-x231.google.com (mail-lj1-x231.google.com [IPv6:2a00:1450:4864:20::231]) (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 18FEA3A0FF1 for <i2nsf@ietf.org>; Mon,  5 Oct 2020 20:30:57 -0700 (PDT)
Received: by mail-lj1-x231.google.com with SMTP id h20so2557401lji.9 for <i2nsf@ietf.org>; Mon, 05 Oct 2020 20:30:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yumaworks-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=/A3Wo8h+9Wh87JktRUD9BejhfbTdOux0INpFHwmneSs=; b=qmaMerDCnB+Rd/EJr6GB4wLYyO/RXvzqHFGf7qdEmCPoIStstRP/UUr4FCWCn2M/Rb gHWeeOmvO5ZjlXGoM9EJ3kku91RwgSLasbczMpspK345opa2LaN6mKykOQ+9AqKzpCBY H9B/NX3fcHgSVeFp3ZDlwV7h4gZAtoqhdsOAwphhFr6Q5R3PhnPHXZtDEXhHUiGMpRHt 40hk8Puo7vqTvcppti30NtjNDiJ8HaatltEDaifotC+TmaCObtVOsg7Y8/a6S+KgFOO9 wkhKiTtH8sWkUKwbLzKNtMzQCK9wI03sdkgzNR2F85Ydvw/Q7QtminlFxa6PAhqXUEFF t7SA==
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=/A3Wo8h+9Wh87JktRUD9BejhfbTdOux0INpFHwmneSs=; b=fsDoUILHSwFtnx3VQrlcen/yhcUIGEDe9FGyBNNODu3ZTSp/IwrIFFvS2wbySElM/D rR42poI8EDg67bCqNXae3/iaM946Oe+ZFsi4IudxkfRTXLX78RqU9FOKinyz0DudXGCK KFWAn8QzuwU0q2V95W6/3CSypiNGMSIQpFiMSNA5+U3FpkfYSaBvOwLB5VP1DehuTNZg DUuC79FceXsLZmz/4TX+f7vBPRbhYY5MtYOLyhUHbWCbmOTBSdYagFMZEMr5+JnyTamg IRuGmc63ymWeTpELBha0x6gH301bbDErYgCbuW2OM6zGv19WcMUSGPJ06vHeJvm+fXd0 vs+g==
X-Gm-Message-State: AOAM532BHdJOeNgILGrtd5PI4xXAuVXyBYRcqyudGT32A+2jv8UhyYg2 hD+VwfwG5fetqFcTbbAzouqDKuFY2IHqeKGu60r5Kw==
X-Google-Smtp-Source: ABdhPJzB3kFKWhWrRvcTZN+UUR5AQUoWeSA64RZe32A12pzW69y3Jo3G/kBcOvWJlqvfaFQspiRSj5U/AkKE5ue1cOg=
X-Received: by 2002:a2e:4e01:: with SMTP id c1mr874727ljb.144.1601955055951; Mon, 05 Oct 2020 20:30:55 -0700 (PDT)
MIME-Version: 1.0
References: <160192102291.6633.15935674903085952087@ietfa.amsl.com> <CAPK2DewOF7QcTD8UdFYdoGUvnJz_fxb53OOn-KmYQgNA38xLoA@mail.gmail.com>
In-Reply-To: <CAPK2DewOF7QcTD8UdFYdoGUvnJz_fxb53OOn-KmYQgNA38xLoA@mail.gmail.com>
From: Andy Bierman <andy@yumaworks.com>
Date: Mon, 5 Oct 2020 20:30:45 -0700
Message-ID: <CABCOCHQsxFVNdBgL9fyZHV+Bevs1D8d5B=+KJAgoVBVekz+VtQ@mail.gmail.com>
To: "Mr. Jaehoon Paul Jeong" <jaehoon.paul@gmail.com>
Cc: YANG Doctors <yang-doctors@ietf.org>, "i2nsf@ietf.org" <i2nsf@ietf.org>,  draft-ietf-i2nsf-nsf-monitoring-data-model.all@ietf.org,  Patrick Lingga <patricklink888@gmail.com>
Content-Type: multipart/alternative; boundary="0000000000000e7b0205b0f83a6e"
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2nsf/42-g0oCdgPZpACOBmeQ5o2cfnwU>
Subject: Re: [I2nsf] Yangdoctors early review of draft-ietf-i2nsf-nsf-monitoring-data-model-04
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: Tue, 06 Oct 2020 03:31:00 -0000

--0000000000000e7b0205b0f83a6e
Content-Type: text/plain; charset="UTF-8"

On Mon, Oct 5, 2020 at 7:30 PM Mr. Jaehoon Paul Jeong <
jaehoon.paul@gmail.com> wrote:

> Hi Andy,
> Thanks for your valuable comments on our NSF Monitoring YANG Data Model
> Draft.
> We authors will reflect your comments on the revision and come back to you
> with
> the revised draft and revision letter.
>
>
I forgot 1 comment:

 - the draft is not that explicit about the event stream to use for these
notifications
   Perhaps a new standard event stream (I2NSF) would be better than the
standard (NETCONF)
   The draft should be more clear wrt/ the NETCONF stream.


Andy



> Thanks.
>
> Best Regards,
> Paul
>
>
> On Tue, Oct 6, 2020 at 3:03 AM Andy Bierman via Datatracker <
> noreply@ietf.org> wrote:
>
>> Reviewer: Andy Bierman
>> Review result: Almost Ready
>>
>>
>>
>> Major Issues:
>>
>>  - None
>>
>> Moderate Issues:
>>
>>  - top-level 'counters' container does not follow naming conventions.
>>    Should start with 'i2nsf', probably 'i2nsf-state'
>>
>>  - There do not seem to be any writable objects in the /counters
>>    subtree so this container should have a 'config false' statement
>>
>>  - top-level typedef and grouping description-stmts are self-referential
>>    and not useful. Need to rewrite description-stmts and/or add
>>    reference-stmts as needed.
>>
>>  - grouping common-monitoring-data/time-stamp
>>    Is this a different time stamp than the one in the NETCONF
>> notification?
>>    The 'message generation time' sounds like the standard timestamp.
>>    Does this object represent the event detection time?
>>
>>  - grouping i2nsf-system-alarm-type-content/usage
>>  - grouping i2nsf-system-alarm-type-content/threshold
>>    These are uint8 leafs with unclear descriptions.
>>    Not sure why uint8 is the appropriate type.
>>    Needs 1 or more of (reference, units, better description)
>>
>>  - grouping traffic-rates
>>    Add a units statement to each leaf. Not sure what units to use
>>    but it should be consistent. (e.g, pps, bps used in descriptions
>>    should also be in a units-stmt)
>>
>>  - grouping i2nsf-system-counter-type-content
>>    These counters should use the yang:counter32 type instead of uint32
>>
>>  - container counters/system-interface
>>  - container counters/nsf-firewall
>>  - container counters/nsf-policy-hits
>>   The descriptions are too terse and confusing, and need a rewrite.
>>
>>  -  container counters/nsf-firewall
>>  -  container counters/nsf-policy-hits
>>     - uses i2nsf-nsf-counters-type-content;
>>     Many of the fields expanded from this grouping all say
>>     they refer to 'the packet'. Why are they in this global
>>     container of counters? E.g. (src-ip, dst-ip, src-port, dst-port)
>>     Not clear at all how the server is supposed to apply this
>>     grouping to these containers.
>>
>>  - many leafs use "uint32" type for a rate.
>>    Should add a units-stmt
>>
>>  - leaf counters/nsf-policy-hits/hit-times
>>    The purpose and type are confusing and generic.
>>    If this is a counter then use counter32
>>
>>  - cut-and-paste for notification-stmt content should be replaced
>>    with grouping/uses instead. Applies to the nsf-detection-*
>>    and the various logging notifications. Even a grouping that
>>    has 1 object in it is better than cut-and-paste 5+ times
>>
>> Minor Issues:
>>
>>  - top-level identifiers are too generic
>>    should have 'i2nsf-' prefix to be more reusable outside this module
>>
>>  - quite a lot of identities that an implementation is required to
>> support.
>>    If this set of identities might change a lot faster than the
>>    notifications and counter objects, then consider putting them
>>    in a separate module
>>
>>  - leaf with same type named differently; both intrusion-attack-type
>>    - nsf-detection-intrusion/sub-attack-type
>>    - nsf-log-intrusion/attack-type
>>
>>  - quite a lot of notification event types for a server to implement
>>    and a user to manage. All are mandatory (no if-feature statements).
>>    Some such as nsf-detection-* subset are very similar.
>>    A section or table would be useful that showed the YANG notification
>>    names and their purpose -- maybe a reference to another RFC
>>    with more details
>>
>>  - there seems to be notifications for intrusion events and then
>>    again for the logging of those events.  This seems excessive
>>    but
>>
>>
>>  - grouping common-monitoring-data/time-stamp
>>    Is this a different time stamp than the one in the NETCONF
>> notification?
>>    The 'message generation time' sounds like the standard timestamp.
>>    Is this event detection time?
>>
>>  - grouping common-monitoring-data/module-name
>>    Is this a YANG module or some other type of module?
>>
>>  - there is no way to configure which notifications should be generated
>>    or maybe how often.  YANG Push has its own dampening-period.
>>    Since these are event stream subscriptions, not datastore
>> subscriptions,
>>    YANG-Push does not apply to this document at all.
>>
>>    If there are a lot of notifications then a server implementation
>>    might drop some
>>
>>  - grouping i2nsf-nsf-event-type-content-extend/src-zone
>>  - grouping i2nsf-nsf-event-type-content-extend/src-zone
>>    These use type 'string'. Consider using a typedef that constrains
>>    the string.  General comment where unconstrained string is used:
>>    The corner-case values such as empty string are often not allowed
>>    in implementations.
>>
>>
>>  - grouping i2nsf-nsf-event-type-content-extend/rule-id
>>  - grouping i2nsf-nsf-event-type-content-extend/rule-name
>>  - grouping i2nsf-nsf-event-type-content-extend/profile
>>    These objects seem to reference objects in another YANG module.
>>    If so, then leafref types might be more appropriate.
>>
>>  - grouping i2nsf-nsf-event-type-content/rule-id
>>  - grouping i2nsf-nsf-event-type-content/rule-name
>>  - grouping i2nsf-nsf-event-type-content/profile
>>  - grouping i2nsf-nsf-event-type-content/raw-info
>>    These objects are cut-and-paste duplicates from
>>    grouping i2nsf-nsf-event-type-content. They should
>>    be in a separate grouping used by both. Also applies
>>    to some other sets of objects
>>
>>  - limits issues (e.g. current-session, maximum-session
>>    The type is uint8. This is only OK it is impossible for any
>>    implementation to ever have or want more than 255 of them.
>>    If some other RFC really does limit the values where uint8
>>    is used, then that is OK. If so, a reference-stmt would help.
>>
>>
>>
>> _______________________________________________
>> I2nsf mailing list
>> I2nsf@ietf.org
>> https://www.ietf.org/mailman/listinfo/i2nsf
>>
>
>
> --
> ===========================
> Mr. Jaehoon (Paul) Jeong, Ph.D.
> Associate Professor
> Department of Computer Science and Engineering
> Sungkyunkwan University
> Office: +82-31-299-4957
> Email: jaehoon.paul@gmail.com, pauljeong@skku.edu
> Personal Homepage: http://iotlab.skku.edu/people-jaehoon-jeong.php
> <http://cpslab.skku.edu/people-jaehoon-jeong.php>
>

--0000000000000e7b0205b0f83a6e
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><br></div><br><div class=3D"gmail_quote">=
<div dir=3D"ltr" class=3D"gmail_attr">On Mon, Oct 5, 2020 at 7:30 PM Mr. Ja=
ehoon Paul Jeong &lt;<a href=3D"mailto:jaehoon.paul@gmail.com">jaehoon.paul=
@gmail.com</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=
=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding=
-left:1ex"><div dir=3D"ltr">Hi Andy,<div>Thanks for your valuable comments =
on our NSF Monitoring YANG Data Model Draft.</div><div>We authors will refl=
ect your comments on the revision and come back to you with</div><div>the r=
evised draft and revision letter.</div><div><br></div></div></blockquote><d=
iv><br></div><div>I forgot 1 comment:</div><div><br></div><div>=C2=A0- the =
draft is not that explicit about the event stream to use for these notifica=
tions</div><div>=C2=A0 =C2=A0Perhaps a new standard event stream (I2NSF) wo=
uld be better than the standard (NETCONF)</div><div>=C2=A0 =C2=A0The draft =
should be more clear wrt/ the NETCONF stream.</div><div><br></div><div><br>=
</div><div>Andy</div><div><br></div><div>=C2=A0=C2=A0</div><blockquote clas=
s=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid r=
gb(204,204,204);padding-left:1ex"><div dir=3D"ltr"><div></div><div>Thanks.<=
/div><div><br></div><div>Best Regards,</div><div>Paul</div><div><br></div><=
/div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">O=
n Tue, Oct 6, 2020 at 3:03 AM Andy Bierman via Datatracker &lt;<a href=3D"m=
ailto:noreply@ietf.org" target=3D"_blank">noreply@ietf.org</a>&gt; wrote:<b=
r></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex=
;border-left:1px solid rgb(204,204,204);padding-left:1ex">Reviewer: Andy Bi=
erman<br>
Review result: Almost Ready<br>
<br>
<br>
<br>
Major Issues:<br>
<br>
=C2=A0- None<br>
<br>
Moderate Issues:<br>
<br>
=C2=A0- top-level &#39;counters&#39; container does not follow naming conve=
ntions.<br>
=C2=A0 =C2=A0Should start with &#39;i2nsf&#39;, probably &#39;i2nsf-state&#=
39;<br>
<br>
=C2=A0- There do not seem to be any writable objects in the /counters<br>
=C2=A0 =C2=A0subtree so this container should have a &#39;config false&#39;=
 statement<br>
<br>
=C2=A0- top-level typedef and grouping description-stmts are self-referenti=
al<br>
=C2=A0 =C2=A0and not useful. Need to rewrite description-stmts and/or add<b=
r>
=C2=A0 =C2=A0reference-stmts as needed.<br>
<br>
=C2=A0- grouping common-monitoring-data/time-stamp<br>
=C2=A0 =C2=A0Is this a different time stamp than the one in the NETCONF not=
ification?<br>
=C2=A0 =C2=A0The &#39;message generation time&#39; sounds like the standard=
 timestamp.<br>
=C2=A0 =C2=A0Does this object represent the event detection time?<br>
<br>
=C2=A0- grouping i2nsf-system-alarm-type-content/usage<br>
=C2=A0- grouping i2nsf-system-alarm-type-content/threshold<br>
=C2=A0 =C2=A0These are uint8 leafs with unclear descriptions.<br>
=C2=A0 =C2=A0Not sure why uint8 is the appropriate type.<br>
=C2=A0 =C2=A0Needs 1 or more of (reference, units, better description)<br>
<br>
=C2=A0- grouping traffic-rates<br>
=C2=A0 =C2=A0Add a units statement to each leaf. Not sure what units to use=
<br>
=C2=A0 =C2=A0but it should be consistent. (e.g, pps, bps used in descriptio=
ns<br>
=C2=A0 =C2=A0should also be in a units-stmt)<br>
<br>
=C2=A0- grouping i2nsf-system-counter-type-content<br>
=C2=A0 =C2=A0These counters should use the yang:counter32 type instead of u=
int32<br>
<br>
=C2=A0- container counters/system-interface<br>
=C2=A0- container counters/nsf-firewall<br>
=C2=A0- container counters/nsf-policy-hits<br>
=C2=A0 The descriptions are too terse and confusing, and need a rewrite.<br=
>
<br>
=C2=A0-=C2=A0 container counters/nsf-firewall<br>
=C2=A0-=C2=A0 container counters/nsf-policy-hits<br>
=C2=A0 =C2=A0 - uses i2nsf-nsf-counters-type-content;<br>
=C2=A0 =C2=A0 Many of the fields expanded from this grouping all say<br>
=C2=A0 =C2=A0 they refer to &#39;the packet&#39;. Why are they in this glob=
al<br>
=C2=A0 =C2=A0 container of counters? E.g. (src-ip, dst-ip, src-port, dst-po=
rt)<br>
=C2=A0 =C2=A0 Not clear at all how the server is supposed to apply this<br>
=C2=A0 =C2=A0 grouping to these containers.<br>
<br>
=C2=A0- many leafs use &quot;uint32&quot; type for a rate.<br>
=C2=A0 =C2=A0Should add a units-stmt<br>
<br>
=C2=A0- leaf counters/nsf-policy-hits/hit-times<br>
=C2=A0 =C2=A0The purpose and type are confusing and generic.<br>
=C2=A0 =C2=A0If this is a counter then use counter32<br>
<br>
=C2=A0- cut-and-paste for notification-stmt content should be replaced<br>
=C2=A0 =C2=A0with grouping/uses instead. Applies to the nsf-detection-*<br>
=C2=A0 =C2=A0and the various logging notifications. Even a grouping that<br=
>
=C2=A0 =C2=A0has 1 object in it is better than cut-and-paste 5+ times<br>
<br>
Minor Issues:<br>
<br>
=C2=A0- top-level identifiers are too generic<br>
=C2=A0 =C2=A0should have &#39;i2nsf-&#39; prefix to be more reusable outsid=
e this module<br>
<br>
=C2=A0- quite a lot of identities that an implementation is required to sup=
port.<br>
=C2=A0 =C2=A0If this set of identities might change a lot faster than the<b=
r>
=C2=A0 =C2=A0notifications and counter objects, then consider putting them<=
br>
=C2=A0 =C2=A0in a separate module<br>
<br>
=C2=A0- leaf with same type named differently; both intrusion-attack-type<b=
r>
=C2=A0 =C2=A0- nsf-detection-intrusion/sub-attack-type<br>
=C2=A0 =C2=A0- nsf-log-intrusion/attack-type<br>
<br>
=C2=A0- quite a lot of notification event types for a server to implement<b=
r>
=C2=A0 =C2=A0and a user to manage. All are mandatory (no if-feature stateme=
nts).<br>
=C2=A0 =C2=A0Some such as nsf-detection-* subset are very similar.<br>
=C2=A0 =C2=A0A section or table would be useful that showed the YANG notifi=
cation<br>
=C2=A0 =C2=A0names and their purpose -- maybe a reference to another RFC<br=
>
=C2=A0 =C2=A0with more details<br>
<br>
=C2=A0- there seems to be notifications for intrusion events and then<br>
=C2=A0 =C2=A0again for the logging of those events.=C2=A0 This seems excess=
ive<br>
=C2=A0 =C2=A0but<br>
<br>
<br>
=C2=A0- grouping common-monitoring-data/time-stamp<br>
=C2=A0 =C2=A0Is this a different time stamp than the one in the NETCONF not=
ification?<br>
=C2=A0 =C2=A0The &#39;message generation time&#39; sounds like the standard=
 timestamp.<br>
=C2=A0 =C2=A0Is this event detection time?<br>
<br>
=C2=A0- grouping common-monitoring-data/module-name<br>
=C2=A0 =C2=A0Is this a YANG module or some other type of module?<br>
<br>
=C2=A0- there is no way to configure which notifications should be generate=
d<br>
=C2=A0 =C2=A0or maybe how often.=C2=A0 YANG Push has its own dampening-peri=
od.<br>
=C2=A0 =C2=A0Since these are event stream subscriptions, not datastore subs=
criptions,<br>
=C2=A0 =C2=A0YANG-Push does not apply to this document at all.<br>
<br>
=C2=A0 =C2=A0If there are a lot of notifications then a server implementati=
on<br>
=C2=A0 =C2=A0might drop some<br>
<br>
=C2=A0- grouping i2nsf-nsf-event-type-content-extend/src-zone<br>
=C2=A0- grouping i2nsf-nsf-event-type-content-extend/src-zone<br>
=C2=A0 =C2=A0These use type &#39;string&#39;. Consider using a typedef that=
 constrains<br>
=C2=A0 =C2=A0the string.=C2=A0 General comment where unconstrained string i=
s used:<br>
=C2=A0 =C2=A0The corner-case values such as empty string are often not allo=
wed<br>
=C2=A0 =C2=A0in implementations.<br>
<br>
<br>
=C2=A0- grouping i2nsf-nsf-event-type-content-extend/rule-id<br>
=C2=A0- grouping i2nsf-nsf-event-type-content-extend/rule-name<br>
=C2=A0- grouping i2nsf-nsf-event-type-content-extend/profile<br>
=C2=A0 =C2=A0These objects seem to reference objects in another YANG module=
.<br>
=C2=A0 =C2=A0If so, then leafref types might be more appropriate.<br>
<br>
=C2=A0- grouping i2nsf-nsf-event-type-content/rule-id<br>
=C2=A0- grouping i2nsf-nsf-event-type-content/rule-name<br>
=C2=A0- grouping i2nsf-nsf-event-type-content/profile<br>
=C2=A0- grouping i2nsf-nsf-event-type-content/raw-info<br>
=C2=A0 =C2=A0These objects are cut-and-paste duplicates from<br>
=C2=A0 =C2=A0grouping i2nsf-nsf-event-type-content. They should<br>
=C2=A0 =C2=A0be in a separate grouping used by both. Also applies<br>
=C2=A0 =C2=A0to some other sets of objects<br>
<br>
=C2=A0- limits issues (e.g. current-session, maximum-session<br>
=C2=A0 =C2=A0The type is uint8. This is only OK it is impossible for any<br=
>
=C2=A0 =C2=A0implementation to ever have or want more than 255 of them.<br>
=C2=A0 =C2=A0If some other RFC really does limit the values where uint8<br>
=C2=A0 =C2=A0is used, then that is OK. If so, a reference-stmt would help.<=
br>
<br>
<br>
<br>
_______________________________________________<br>
I2nsf mailing list<br>
<a href=3D"mailto:I2nsf@ietf.org" target=3D"_blank">I2nsf@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/i2nsf" rel=3D"noreferrer" =
target=3D"_blank">https://www.ietf.org/mailman/listinfo/i2nsf</a><br>
</blockquote></div><br clear=3D"all"><div><br></div>-- <br><div dir=3D"ltr"=
><div dir=3D"ltr"><div><div dir=3D"ltr"><div><div dir=3D"ltr"><div><div dir=
=3D"ltr">=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D<br>Mr. Jaehoon (Paul) Jeong, Ph.D.<br>Associate Professor<b=
r>Department of Computer Science and Engineering<br>Sungkyunkwan University=
<br>Office: +82-31-299-4957<br>Email: <a href=3D"mailto:jaehoon.paul@gmail.=
com" target=3D"_blank">jaehoon.paul@gmail.com</a>,=C2=A0<a href=3D"mailto:p=
auljeong@skku.edu" style=3D"font-size:12.8px" target=3D"_blank">pauljeong@s=
kku.edu</a><br>Personal Homepage: <a href=3D"http://cpslab.skku.edu/people-=
jaehoon-jeong.php" target=3D"_blank">http://iotlab.skku.edu/people-jaehoon-=
jeong.php</a><br></div></div></div></div></div></div></div></div>
</blockquote></div></div>

--0000000000000e7b0205b0f83a6e--


From nobody Mon Oct  5 21:05:53 2020
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 B54523A105B; Mon,  5 Oct 2020 21:05:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.086
X-Spam-Level: 
X-Spam-Status: No, score=-2.086 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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_HK_NAME_FM_MR_MRS=0.01, URIBL_BLOCKED=0.001, URI_DOTEDU=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 qwShRPpyGhna; Mon,  5 Oct 2020 21:05:50 -0700 (PDT)
Received: from mail-lj1-x22b.google.com (mail-lj1-x22b.google.com [IPv6:2a00:1450:4864:20::22b]) (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 E38C13A105A; Mon,  5 Oct 2020 21:05:49 -0700 (PDT)
Received: by mail-lj1-x22b.google.com with SMTP id m16so7217186ljo.6; Mon, 05 Oct 2020 21:05:49 -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=haOF5svoBuVGOx9uJLMmCUp4wfSOaG+1NabfAgUmlV8=; b=Lo7TMNGMIgBMng+ATqmhfzK4tKgv3vpjbODaKiGs9I0JVJqcdSnyOdhBR6qDYNcuHA okNBj6eNkWmwrAlohgWF/qGaabl+MrBY/A6Hh/INj+pGclviplTwM/DRpnJA6qcz0D1n hbknI89SvqVeyQGkYL7RNx987vzUgSrODO9SwuDoQfD60ywSOs7FR48VvxIOtSQ7OUKR C75J+us/PNq62ndF5roc7FSqPkCxOiES2N1jhl7hWBzR6jDmRqZtMc+DKQSe/LZd+y4X GSx+CkSSYgURoRiKhaqD9/inBd7r/nT+AxYx1AGnIac55w9rW9AoClnR/mjgL0NAuH/u WQFA==
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=haOF5svoBuVGOx9uJLMmCUp4wfSOaG+1NabfAgUmlV8=; b=CvzVJFTD6tp4BKq3CjBjp9mVeQOuwFyP8MKq4ihNQ/9bBupLDeccB7vY9bwkxyROqn +7fi2sThcneoqBbwKr1ujmzUMw8LQ8kzYfMwq3UZUHW/Y25i9q5tI4ZV7R+WxNUIRk3p myNnDaIezG9mb1C63aKsfVIZxnAn2Ps3ZdxYLwVJQo8kAdlYYv63ZZouw95uiAey62Xm wUgxzHpNLYJFfdkgaG40YB3eqNW17Mxd6Ff1L8UXAWkMz1S7TDXdCFqx8Ck80RFfLG5G knA5WRacqb38SAUJLOL92dYwwfRE6eKTviLUL7fdWccjSNwHxdwCVTBxo7RZqd4M2cpZ luhg==
X-Gm-Message-State: AOAM531m3bkOaJUrR2qUJ6GXeOcr4EVwzhO3nFyVji+dssA2Hz3Pxwgm k3IUJXJWWUobThY3gdoTUrgVZR5xuCQJk5pEtTU=
X-Google-Smtp-Source: ABdhPJw85ckii2wbDA0/w7UiT4ajxW9DpgS5ba4FY6xQtky2ywBTSAtb3abQdzxrOX39faYdgcvyXTlSljIA0ZH41Zc=
X-Received: by 2002:a2e:5c83:: with SMTP id q125mr896348ljb.387.1601957147869;  Mon, 05 Oct 2020 21:05:47 -0700 (PDT)
MIME-Version: 1.0
References: <160192102291.6633.15935674903085952087@ietfa.amsl.com> <CAPK2DewOF7QcTD8UdFYdoGUvnJz_fxb53OOn-KmYQgNA38xLoA@mail.gmail.com> <CABCOCHQsxFVNdBgL9fyZHV+Bevs1D8d5B=+KJAgoVBVekz+VtQ@mail.gmail.com>
In-Reply-To: <CABCOCHQsxFVNdBgL9fyZHV+Bevs1D8d5B=+KJAgoVBVekz+VtQ@mail.gmail.com>
From: "Mr. Jaehoon Paul Jeong" <jaehoon.paul@gmail.com>
Date: Tue, 6 Oct 2020 13:05:07 +0900
Message-ID: <CAPK2DewNDq2_DtZhtxitTsavHczwiSKur9+yQPLR+18UbV-QHg@mail.gmail.com>
To: Andy Bierman <andy@yumaworks.com>
Cc: YANG Doctors <yang-doctors@ietf.org>, "i2nsf@ietf.org" <i2nsf@ietf.org>,  draft-ietf-i2nsf-nsf-monitoring-data-model.all@ietf.org,  Patrick Lingga <patricklink888@gmail.com>,  "Mr. Jaehoon Paul Jeong" <jaehoon.paul@gmail.com>
Content-Type: multipart/alternative; boundary="000000000000be880105b0f8b6b2"
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2nsf/wvba_H6hDTnvBZEQHko92tskQLU>
Subject: Re: [I2nsf] Yangdoctors early review of draft-ietf-i2nsf-nsf-monitoring-data-model-04
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: Tue, 06 Oct 2020 04:05:53 -0000

--000000000000be880105b0f8b6b2
Content-Type: text/plain; charset="UTF-8"

Andy,
What do you mean by the event stream?

Actually, I am thinking that the NETCONF can deliver the monitoring data of
a system or an NSF in an XML file.

Do you think that we need another way to convey the monitoring data?

Thanks.

Best Regards,
Paul

On Tue, Oct 6, 2020 at 12:30 PM Andy Bierman <andy@yumaworks.com> wrote:

>
>
> On Mon, Oct 5, 2020 at 7:30 PM Mr. Jaehoon Paul Jeong <
> jaehoon.paul@gmail.com> wrote:
>
>> Hi Andy,
>> Thanks for your valuable comments on our NSF Monitoring YANG Data Model
>> Draft.
>> We authors will reflect your comments on the revision and come back to
>> you with
>> the revised draft and revision letter.
>>
>>
> I forgot 1 comment:
>
>  - the draft is not that explicit about the event stream to use for these
> notifications
>    Perhaps a new standard event stream (I2NSF) would be better than the
> standard (NETCONF)
>    The draft should be more clear wrt/ the NETCONF stream.
>
>
> Andy
>
>
>
>> Thanks.
>>
>> Best Regards,
>> Paul
>>
>>
>> On Tue, Oct 6, 2020 at 3:03 AM Andy Bierman via Datatracker <
>> noreply@ietf.org> wrote:
>>
>>> Reviewer: Andy Bierman
>>> Review result: Almost Ready
>>>
>>>
>>>
>>> Major Issues:
>>>
>>>  - None
>>>
>>> Moderate Issues:
>>>
>>>  - top-level 'counters' container does not follow naming conventions.
>>>    Should start with 'i2nsf', probably 'i2nsf-state'
>>>
>>>  - There do not seem to be any writable objects in the /counters
>>>    subtree so this container should have a 'config false' statement
>>>
>>>  - top-level typedef and grouping description-stmts are self-referential
>>>    and not useful. Need to rewrite description-stmts and/or add
>>>    reference-stmts as needed.
>>>
>>>  - grouping common-monitoring-data/time-stamp
>>>    Is this a different time stamp than the one in the NETCONF
>>> notification?
>>>    The 'message generation time' sounds like the standard timestamp.
>>>    Does this object represent the event detection time?
>>>
>>>  - grouping i2nsf-system-alarm-type-content/usage
>>>  - grouping i2nsf-system-alarm-type-content/threshold
>>>    These are uint8 leafs with unclear descriptions.
>>>    Not sure why uint8 is the appropriate type.
>>>    Needs 1 or more of (reference, units, better description)
>>>
>>>  - grouping traffic-rates
>>>    Add a units statement to each leaf. Not sure what units to use
>>>    but it should be consistent. (e.g, pps, bps used in descriptions
>>>    should also be in a units-stmt)
>>>
>>>  - grouping i2nsf-system-counter-type-content
>>>    These counters should use the yang:counter32 type instead of uint32
>>>
>>>  - container counters/system-interface
>>>  - container counters/nsf-firewall
>>>  - container counters/nsf-policy-hits
>>>   The descriptions are too terse and confusing, and need a rewrite.
>>>
>>>  -  container counters/nsf-firewall
>>>  -  container counters/nsf-policy-hits
>>>     - uses i2nsf-nsf-counters-type-content;
>>>     Many of the fields expanded from this grouping all say
>>>     they refer to 'the packet'. Why are they in this global
>>>     container of counters? E.g. (src-ip, dst-ip, src-port, dst-port)
>>>     Not clear at all how the server is supposed to apply this
>>>     grouping to these containers.
>>>
>>>  - many leafs use "uint32" type for a rate.
>>>    Should add a units-stmt
>>>
>>>  - leaf counters/nsf-policy-hits/hit-times
>>>    The purpose and type are confusing and generic.
>>>    If this is a counter then use counter32
>>>
>>>  - cut-and-paste for notification-stmt content should be replaced
>>>    with grouping/uses instead. Applies to the nsf-detection-*
>>>    and the various logging notifications. Even a grouping that
>>>    has 1 object in it is better than cut-and-paste 5+ times
>>>
>>> Minor Issues:
>>>
>>>  - top-level identifiers are too generic
>>>    should have 'i2nsf-' prefix to be more reusable outside this module
>>>
>>>  - quite a lot of identities that an implementation is required to
>>> support.
>>>    If this set of identities might change a lot faster than the
>>>    notifications and counter objects, then consider putting them
>>>    in a separate module
>>>
>>>  - leaf with same type named differently; both intrusion-attack-type
>>>    - nsf-detection-intrusion/sub-attack-type
>>>    - nsf-log-intrusion/attack-type
>>>
>>>  - quite a lot of notification event types for a server to implement
>>>    and a user to manage. All are mandatory (no if-feature statements).
>>>    Some such as nsf-detection-* subset are very similar.
>>>    A section or table would be useful that showed the YANG notification
>>>    names and their purpose -- maybe a reference to another RFC
>>>    with more details
>>>
>>>  - there seems to be notifications for intrusion events and then
>>>    again for the logging of those events.  This seems excessive
>>>    but
>>>
>>>
>>>  - grouping common-monitoring-data/time-stamp
>>>    Is this a different time stamp than the one in the NETCONF
>>> notification?
>>>    The 'message generation time' sounds like the standard timestamp.
>>>    Is this event detection time?
>>>
>>>  - grouping common-monitoring-data/module-name
>>>    Is this a YANG module or some other type of module?
>>>
>>>  - there is no way to configure which notifications should be generated
>>>    or maybe how often.  YANG Push has its own dampening-period.
>>>    Since these are event stream subscriptions, not datastore
>>> subscriptions,
>>>    YANG-Push does not apply to this document at all.
>>>
>>>    If there are a lot of notifications then a server implementation
>>>    might drop some
>>>
>>>  - grouping i2nsf-nsf-event-type-content-extend/src-zone
>>>  - grouping i2nsf-nsf-event-type-content-extend/src-zone
>>>    These use type 'string'. Consider using a typedef that constrains
>>>    the string.  General comment where unconstrained string is used:
>>>    The corner-case values such as empty string are often not allowed
>>>    in implementations.
>>>
>>>
>>>  - grouping i2nsf-nsf-event-type-content-extend/rule-id
>>>  - grouping i2nsf-nsf-event-type-content-extend/rule-name
>>>  - grouping i2nsf-nsf-event-type-content-extend/profile
>>>    These objects seem to reference objects in another YANG module.
>>>    If so, then leafref types might be more appropriate.
>>>
>>>  - grouping i2nsf-nsf-event-type-content/rule-id
>>>  - grouping i2nsf-nsf-event-type-content/rule-name
>>>  - grouping i2nsf-nsf-event-type-content/profile
>>>  - grouping i2nsf-nsf-event-type-content/raw-info
>>>    These objects are cut-and-paste duplicates from
>>>    grouping i2nsf-nsf-event-type-content. They should
>>>    be in a separate grouping used by both. Also applies
>>>    to some other sets of objects
>>>
>>>  - limits issues (e.g. current-session, maximum-session
>>>    The type is uint8. This is only OK it is impossible for any
>>>    implementation to ever have or want more than 255 of them.
>>>    If some other RFC really does limit the values where uint8
>>>    is used, then that is OK. If so, a reference-stmt would help.
>>>
>>>
>>>
>>> _______________________________________________
>>> I2nsf mailing list
>>> I2nsf@ietf.org
>>> https://www.ietf.org/mailman/listinfo/i2nsf
>>>
>>
>>
>> --
>> ===========================
>> Mr. Jaehoon (Paul) Jeong, Ph.D.
>> Associate Professor
>> Department of Computer Science and Engineering
>> Sungkyunkwan University
>> Office: +82-31-299-4957
>> Email: jaehoon.paul@gmail.com, pauljeong@skku.edu
>> Personal Homepage: http://iotlab.skku.edu/people-jaehoon-jeong.php
>> <http://cpslab.skku.edu/people-jaehoon-jeong.php>
>>
>

-- 
===========================
Mr. Jaehoon (Paul) Jeong, Ph.D.
Associate Professor
Department of Computer Science and Engineering
Sungkyunkwan University
Office: +82-31-299-4957
Email: jaehoon.paul@gmail.com, pauljeong@skku.edu
Personal Homepage: http://iotlab.skku.edu/people-jaehoon-jeong.php
<http://cpslab.skku.edu/people-jaehoon-jeong.php>

--000000000000be880105b0f8b6b2
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Andy,<div>What do you mean by the event stream?</div><div>=
<br></div><div>Actually, I am thinking that the NETCONF can deliver the mon=
itoring data of a system or an NSF in an XML file.</div><div><br></div><div=
>Do you think that we need another way to convey the monitoring data?</div>=
<div><br></div><div>Thanks.</div><div><br></div><div>Best Regards,</div><di=
v>Paul</div></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"=
gmail_attr">On Tue, Oct 6, 2020 at 12:30 PM Andy Bierman &lt;<a href=3D"mai=
lto:andy@yumaworks.com">andy@yumaworks.com</a>&gt; wrote:<br></div><blockqu=
ote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px=
 solid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr"><div dir=3D"ltr"=
><br></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_a=
ttr">On Mon, Oct 5, 2020 at 7:30 PM Mr. Jaehoon Paul Jeong &lt;<a href=3D"m=
ailto:jaehoon.paul@gmail.com" target=3D"_blank">jaehoon.paul@gmail.com</a>&=
gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0=
px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div =
dir=3D"ltr">Hi Andy,<div>Thanks for your valuable comments on our NSF Monit=
oring YANG Data Model Draft.</div><div>We authors will reflect your comment=
s on the revision and come back to you with</div><div>the revised draft and=
 revision letter.</div><div><br></div></div></blockquote><div><br></div><di=
v>I forgot 1 comment:</div><div><br></div><div>=C2=A0- the draft is not tha=
t explicit about the event stream to use for these notifications</div><div>=
=C2=A0 =C2=A0Perhaps a new standard event stream (I2NSF) would be better th=
an the standard (NETCONF)</div><div>=C2=A0 =C2=A0The draft should be more c=
lear wrt/ the NETCONF stream.</div><div><br></div><div><br></div><div>Andy<=
/div><div><br></div><div>=C2=A0=C2=A0</div><blockquote class=3D"gmail_quote=
" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);=
padding-left:1ex"><div dir=3D"ltr"><div></div><div>Thanks.</div><div><br></=
div><div>Best Regards,</div><div>Paul</div><div><br></div></div><br><div cl=
ass=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Tue, Oct 6, 20=
20 at 3:03 AM Andy Bierman via Datatracker &lt;<a href=3D"mailto:noreply@ie=
tf.org" target=3D"_blank">noreply@ietf.org</a>&gt; wrote:<br></div><blockqu=
ote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px=
 solid rgb(204,204,204);padding-left:1ex">Reviewer: Andy Bierman<br>
Review result: Almost Ready<br>
<br>
<br>
<br>
Major Issues:<br>
<br>
=C2=A0- None<br>
<br>
Moderate Issues:<br>
<br>
=C2=A0- top-level &#39;counters&#39; container does not follow naming conve=
ntions.<br>
=C2=A0 =C2=A0Should start with &#39;i2nsf&#39;, probably &#39;i2nsf-state&#=
39;<br>
<br>
=C2=A0- There do not seem to be any writable objects in the /counters<br>
=C2=A0 =C2=A0subtree so this container should have a &#39;config false&#39;=
 statement<br>
<br>
=C2=A0- top-level typedef and grouping description-stmts are self-referenti=
al<br>
=C2=A0 =C2=A0and not useful. Need to rewrite description-stmts and/or add<b=
r>
=C2=A0 =C2=A0reference-stmts as needed.<br>
<br>
=C2=A0- grouping common-monitoring-data/time-stamp<br>
=C2=A0 =C2=A0Is this a different time stamp than the one in the NETCONF not=
ification?<br>
=C2=A0 =C2=A0The &#39;message generation time&#39; sounds like the standard=
 timestamp.<br>
=C2=A0 =C2=A0Does this object represent the event detection time?<br>
<br>
=C2=A0- grouping i2nsf-system-alarm-type-content/usage<br>
=C2=A0- grouping i2nsf-system-alarm-type-content/threshold<br>
=C2=A0 =C2=A0These are uint8 leafs with unclear descriptions.<br>
=C2=A0 =C2=A0Not sure why uint8 is the appropriate type.<br>
=C2=A0 =C2=A0Needs 1 or more of (reference, units, better description)<br>
<br>
=C2=A0- grouping traffic-rates<br>
=C2=A0 =C2=A0Add a units statement to each leaf. Not sure what units to use=
<br>
=C2=A0 =C2=A0but it should be consistent. (e.g, pps, bps used in descriptio=
ns<br>
=C2=A0 =C2=A0should also be in a units-stmt)<br>
<br>
=C2=A0- grouping i2nsf-system-counter-type-content<br>
=C2=A0 =C2=A0These counters should use the yang:counter32 type instead of u=
int32<br>
<br>
=C2=A0- container counters/system-interface<br>
=C2=A0- container counters/nsf-firewall<br>
=C2=A0- container counters/nsf-policy-hits<br>
=C2=A0 The descriptions are too terse and confusing, and need a rewrite.<br=
>
<br>
=C2=A0-=C2=A0 container counters/nsf-firewall<br>
=C2=A0-=C2=A0 container counters/nsf-policy-hits<br>
=C2=A0 =C2=A0 - uses i2nsf-nsf-counters-type-content;<br>
=C2=A0 =C2=A0 Many of the fields expanded from this grouping all say<br>
=C2=A0 =C2=A0 they refer to &#39;the packet&#39;. Why are they in this glob=
al<br>
=C2=A0 =C2=A0 container of counters? E.g. (src-ip, dst-ip, src-port, dst-po=
rt)<br>
=C2=A0 =C2=A0 Not clear at all how the server is supposed to apply this<br>
=C2=A0 =C2=A0 grouping to these containers.<br>
<br>
=C2=A0- many leafs use &quot;uint32&quot; type for a rate.<br>
=C2=A0 =C2=A0Should add a units-stmt<br>
<br>
=C2=A0- leaf counters/nsf-policy-hits/hit-times<br>
=C2=A0 =C2=A0The purpose and type are confusing and generic.<br>
=C2=A0 =C2=A0If this is a counter then use counter32<br>
<br>
=C2=A0- cut-and-paste for notification-stmt content should be replaced<br>
=C2=A0 =C2=A0with grouping/uses instead. Applies to the nsf-detection-*<br>
=C2=A0 =C2=A0and the various logging notifications. Even a grouping that<br=
>
=C2=A0 =C2=A0has 1 object in it is better than cut-and-paste 5+ times<br>
<br>
Minor Issues:<br>
<br>
=C2=A0- top-level identifiers are too generic<br>
=C2=A0 =C2=A0should have &#39;i2nsf-&#39; prefix to be more reusable outsid=
e this module<br>
<br>
=C2=A0- quite a lot of identities that an implementation is required to sup=
port.<br>
=C2=A0 =C2=A0If this set of identities might change a lot faster than the<b=
r>
=C2=A0 =C2=A0notifications and counter objects, then consider putting them<=
br>
=C2=A0 =C2=A0in a separate module<br>
<br>
=C2=A0- leaf with same type named differently; both intrusion-attack-type<b=
r>
=C2=A0 =C2=A0- nsf-detection-intrusion/sub-attack-type<br>
=C2=A0 =C2=A0- nsf-log-intrusion/attack-type<br>
<br>
=C2=A0- quite a lot of notification event types for a server to implement<b=
r>
=C2=A0 =C2=A0and a user to manage. All are mandatory (no if-feature stateme=
nts).<br>
=C2=A0 =C2=A0Some such as nsf-detection-* subset are very similar.<br>
=C2=A0 =C2=A0A section or table would be useful that showed the YANG notifi=
cation<br>
=C2=A0 =C2=A0names and their purpose -- maybe a reference to another RFC<br=
>
=C2=A0 =C2=A0with more details<br>
<br>
=C2=A0- there seems to be notifications for intrusion events and then<br>
=C2=A0 =C2=A0again for the logging of those events.=C2=A0 This seems excess=
ive<br>
=C2=A0 =C2=A0but<br>
<br>
<br>
=C2=A0- grouping common-monitoring-data/time-stamp<br>
=C2=A0 =C2=A0Is this a different time stamp than the one in the NETCONF not=
ification?<br>
=C2=A0 =C2=A0The &#39;message generation time&#39; sounds like the standard=
 timestamp.<br>
=C2=A0 =C2=A0Is this event detection time?<br>
<br>
=C2=A0- grouping common-monitoring-data/module-name<br>
=C2=A0 =C2=A0Is this a YANG module or some other type of module?<br>
<br>
=C2=A0- there is no way to configure which notifications should be generate=
d<br>
=C2=A0 =C2=A0or maybe how often.=C2=A0 YANG Push has its own dampening-peri=
od.<br>
=C2=A0 =C2=A0Since these are event stream subscriptions, not datastore subs=
criptions,<br>
=C2=A0 =C2=A0YANG-Push does not apply to this document at all.<br>
<br>
=C2=A0 =C2=A0If there are a lot of notifications then a server implementati=
on<br>
=C2=A0 =C2=A0might drop some<br>
<br>
=C2=A0- grouping i2nsf-nsf-event-type-content-extend/src-zone<br>
=C2=A0- grouping i2nsf-nsf-event-type-content-extend/src-zone<br>
=C2=A0 =C2=A0These use type &#39;string&#39;. Consider using a typedef that=
 constrains<br>
=C2=A0 =C2=A0the string.=C2=A0 General comment where unconstrained string i=
s used:<br>
=C2=A0 =C2=A0The corner-case values such as empty string are often not allo=
wed<br>
=C2=A0 =C2=A0in implementations.<br>
<br>
<br>
=C2=A0- grouping i2nsf-nsf-event-type-content-extend/rule-id<br>
=C2=A0- grouping i2nsf-nsf-event-type-content-extend/rule-name<br>
=C2=A0- grouping i2nsf-nsf-event-type-content-extend/profile<br>
=C2=A0 =C2=A0These objects seem to reference objects in another YANG module=
.<br>
=C2=A0 =C2=A0If so, then leafref types might be more appropriate.<br>
<br>
=C2=A0- grouping i2nsf-nsf-event-type-content/rule-id<br>
=C2=A0- grouping i2nsf-nsf-event-type-content/rule-name<br>
=C2=A0- grouping i2nsf-nsf-event-type-content/profile<br>
=C2=A0- grouping i2nsf-nsf-event-type-content/raw-info<br>
=C2=A0 =C2=A0These objects are cut-and-paste duplicates from<br>
=C2=A0 =C2=A0grouping i2nsf-nsf-event-type-content. They should<br>
=C2=A0 =C2=A0be in a separate grouping used by both. Also applies<br>
=C2=A0 =C2=A0to some other sets of objects<br>
<br>
=C2=A0- limits issues (e.g. current-session, maximum-session<br>
=C2=A0 =C2=A0The type is uint8. This is only OK it is impossible for any<br=
>
=C2=A0 =C2=A0implementation to ever have or want more than 255 of them.<br>
=C2=A0 =C2=A0If some other RFC really does limit the values where uint8<br>
=C2=A0 =C2=A0is used, then that is OK. If so, a reference-stmt would help.<=
br>
<br>
<br>
<br>
_______________________________________________<br>
I2nsf mailing list<br>
<a href=3D"mailto:I2nsf@ietf.org" target=3D"_blank">I2nsf@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/i2nsf" rel=3D"noreferrer" =
target=3D"_blank">https://www.ietf.org/mailman/listinfo/i2nsf</a><br>
</blockquote></div><br clear=3D"all"><div><br></div>-- <br><div dir=3D"ltr"=
><div dir=3D"ltr"><div><div dir=3D"ltr"><div><div dir=3D"ltr"><div><div dir=
=3D"ltr">=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D<br>Mr. Jaehoon (Paul) Jeong, Ph.D.<br>Associate Professor<b=
r>Department of Computer Science and Engineering<br>Sungkyunkwan University=
<br>Office: +82-31-299-4957<br>Email: <a href=3D"mailto:jaehoon.paul@gmail.=
com" target=3D"_blank">jaehoon.paul@gmail.com</a>,=C2=A0<a href=3D"mailto:p=
auljeong@skku.edu" style=3D"font-size:12.8px" target=3D"_blank">pauljeong@s=
kku.edu</a><br>Personal Homepage: <a href=3D"http://cpslab.skku.edu/people-=
jaehoon-jeong.php" target=3D"_blank">http://iotlab.skku.edu/people-jaehoon-=
jeong.php</a><br></div></div></div></div></div></div></div></div>
</blockquote></div></div>
</blockquote></div><br clear=3D"all"><div><br></div>-- <br><div dir=3D"ltr"=
 class=3D"gmail_signature"><div dir=3D"ltr"><div><div dir=3D"ltr"><div><div=
 dir=3D"ltr"><div><div dir=3D"ltr">=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br>Mr. Jaehoon (Paul) Jeong, Ph.=
D.<br>Associate Professor<br>Department of Computer Science and Engineering=
<br>Sungkyunkwan University<br>Office: +82-31-299-4957<br>Email: <a href=3D=
"mailto:jaehoon.paul@gmail.com" target=3D"_blank">jaehoon.paul@gmail.com</a=
>,=C2=A0<a href=3D"mailto:pauljeong@skku.edu" style=3D"font-size:12.8px" ta=
rget=3D"_blank">pauljeong@skku.edu</a><br>Personal Homepage: <a href=3D"htt=
p://cpslab.skku.edu/people-jaehoon-jeong.php" target=3D"_blank">http://iotl=
ab.skku.edu/people-jaehoon-jeong.php</a><br></div></div></div></div></div><=
/div></div></div>

--000000000000be880105b0f8b6b2--


From nobody Mon Oct  5 21:51:14 2020
Return-Path: <andy@yumaworks.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 3E4C03A10FD for <i2nsf@ietfa.amsl.com>; Mon,  5 Oct 2020 21:51:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.886
X-Spam-Level: 
X-Spam-Status: No, score=-1.886 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001, URI_DOTEDU=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=yumaworks-com.20150623.gappssmtp.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 gAL0VoMZzdBj for <i2nsf@ietfa.amsl.com>; Mon,  5 Oct 2020 21:51:09 -0700 (PDT)
Received: from mail-lf1-x135.google.com (mail-lf1-x135.google.com [IPv6:2a00:1450:4864:20::135]) (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 C60963A10FB for <i2nsf@ietf.org>; Mon,  5 Oct 2020 21:51:08 -0700 (PDT)
Received: by mail-lf1-x135.google.com with SMTP id r127so8979887lff.12 for <i2nsf@ietf.org>; Mon, 05 Oct 2020 21:51:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yumaworks-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=nvikrnGk24AxQgPbLNqqFhZXnoIfj/BQ/SZLieKWo24=; b=uLPSWtNN4CymsSF96GE7X9AEZSUYLsru4NK2/bX807GZGWkdZ96fGEx0NlQSNxaSQ1 18Fwbh6HvjO/avhx3Qo+OHsTKpBzw7rQWZemPPC7lglG++5LAFQFuqhBCAY/07p9PdVx KkxBge/4dECgu2tabja/yhm4Qb/S51b1fN54ujCT7AusvJCrbmvkzySWDYV2Y9EhuY9B n1/zgU3mpEAGSXERAxirqw3Vd4p6HrSHYGeiGt70lnc8XzT9Je2bYMWmnKi2NQLUrUlS 486ZnPMJWCOp0i28Lva38Pe7BD/bJc4w3XYS5ekidihmKma3p7xk32XkqgMUDfkjLx/m n4Gg==
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=nvikrnGk24AxQgPbLNqqFhZXnoIfj/BQ/SZLieKWo24=; b=r0ScmTmUZ9upQZDnWYNagf/SkLcH/1XZH69T+rMh+Xk9NUaBogVLvkAhrWbesPe83g tINDMsYDi21tL7DRC8CpyDQmMZywqDcDgEe0qdFvvhpIoUTmZ3LsQlVJpMVL4I44U/eY Ocfiwj8wo34fG6swlw2R4j3zGW2TUHJVxCpqyyjImfxthTNbeBaYm8FNwLLqhDP1xmDf TAsj6Z6jln/iCM2iA09X+kd95wH1uNDET1QgYM5oiOGYNeH1Zqv3PHlWPnldpG3lHL/t yRU5PgNcZj8iJVF1YAmZxy71Z4+oQ4iN4qD1fRPrF1zZkWt5EMOGuFHyJzXFGx1A/jgc uR4g==
X-Gm-Message-State: AOAM531GB1ezwpHbjiKnwHBn1HFdQMwz/uzvBPzRG1yg22W5m3nSjDGz TPWXMhrownGMhjYukB/rtNl/tZKl7h0Rj6mbWFOTWQ==
X-Google-Smtp-Source: ABdhPJzEYEeJSIECNZBiic7C7pQ/le8rqlQYgG9UqweRX6GVxlt+IFLNirBCOsCM8/q0bN6BkNhqFjOz9I1Qsp4KHzE=
X-Received: by 2002:a19:e54:: with SMTP id 81mr944135lfo.178.1601959866692; Mon, 05 Oct 2020 21:51:06 -0700 (PDT)
MIME-Version: 1.0
References: <160192102291.6633.15935674903085952087@ietfa.amsl.com> <CAPK2DewOF7QcTD8UdFYdoGUvnJz_fxb53OOn-KmYQgNA38xLoA@mail.gmail.com> <CABCOCHQsxFVNdBgL9fyZHV+Bevs1D8d5B=+KJAgoVBVekz+VtQ@mail.gmail.com> <CAPK2DewNDq2_DtZhtxitTsavHczwiSKur9+yQPLR+18UbV-QHg@mail.gmail.com>
In-Reply-To: <CAPK2DewNDq2_DtZhtxitTsavHczwiSKur9+yQPLR+18UbV-QHg@mail.gmail.com>
From: Andy Bierman <andy@yumaworks.com>
Date: Mon, 5 Oct 2020 21:50:55 -0700
Message-ID: <CABCOCHT-0mKbYBDtZHnANRLqMtSsT1ijhoe1znoS2_pDHn4WNA@mail.gmail.com>
To: "Mr. Jaehoon Paul Jeong" <jaehoon.paul@gmail.com>
Cc: YANG Doctors <yang-doctors@ietf.org>, "i2nsf@ietf.org" <i2nsf@ietf.org>,  draft-ietf-i2nsf-nsf-monitoring-data-model.all@ietf.org,  Patrick Lingga <patricklink888@gmail.com>
Content-Type: multipart/alternative; boundary="000000000000cc91a905b0f9580d"
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2nsf/VkRQDLucG4ycO18guFYDBRbZ8hI>
Subject: Re: [I2nsf] Yangdoctors early review of draft-ietf-i2nsf-nsf-monitoring-data-model-04
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: Tue, 06 Oct 2020 04:51:11 -0000

--000000000000cc91a905b0f9580d
Content-Type: text/plain; charset="UTF-8"

On Mon, Oct 5, 2020 at 9:05 PM Mr. Jaehoon Paul Jeong <
jaehoon.paul@gmail.com> wrote:

> Andy,
> What do you mean by the event stream?
>
>
https://tools.ietf.org/html/rfc8639#section-2.1



> Actually, I am thinking that the NETCONF can deliver the monitoring data
> of a system or an NSF in an XML file.
>
> Do you think that we need another way to convey the monitoring data?
>
> Thanks.
>
> Best Regards,
> Paul
>
> On Tue, Oct 6, 2020 at 12:30 PM Andy Bierman <andy@yumaworks.com> wrote:
>
>>
>>
>> On Mon, Oct 5, 2020 at 7:30 PM Mr. Jaehoon Paul Jeong <
>> jaehoon.paul@gmail.com> wrote:
>>
>>> Hi Andy,
>>> Thanks for your valuable comments on our NSF Monitoring YANG Data Model
>>> Draft.
>>> We authors will reflect your comments on the revision and come back to
>>> you with
>>> the revised draft and revision letter.
>>>
>>>
>> I forgot 1 comment:
>>
>>  - the draft is not that explicit about the event stream to use for these
>> notifications
>>    Perhaps a new standard event stream (I2NSF) would be better than the
>> standard (NETCONF)
>>    The draft should be more clear wrt/ the NETCONF stream.
>>
>>
>> Andy
>>
>>
>>
>>> Thanks.
>>>
>>> Best Regards,
>>> Paul
>>>
>>>
>>> On Tue, Oct 6, 2020 at 3:03 AM Andy Bierman via Datatracker <
>>> noreply@ietf.org> wrote:
>>>
>>>> Reviewer: Andy Bierman
>>>> Review result: Almost Ready
>>>>
>>>>
>>>>
>>>> Major Issues:
>>>>
>>>>  - None
>>>>
>>>> Moderate Issues:
>>>>
>>>>  - top-level 'counters' container does not follow naming conventions.
>>>>    Should start with 'i2nsf', probably 'i2nsf-state'
>>>>
>>>>  - There do not seem to be any writable objects in the /counters
>>>>    subtree so this container should have a 'config false' statement
>>>>
>>>>  - top-level typedef and grouping description-stmts are self-referential
>>>>    and not useful. Need to rewrite description-stmts and/or add
>>>>    reference-stmts as needed.
>>>>
>>>>  - grouping common-monitoring-data/time-stamp
>>>>    Is this a different time stamp than the one in the NETCONF
>>>> notification?
>>>>    The 'message generation time' sounds like the standard timestamp.
>>>>    Does this object represent the event detection time?
>>>>
>>>>  - grouping i2nsf-system-alarm-type-content/usage
>>>>  - grouping i2nsf-system-alarm-type-content/threshold
>>>>    These are uint8 leafs with unclear descriptions.
>>>>    Not sure why uint8 is the appropriate type.
>>>>    Needs 1 or more of (reference, units, better description)
>>>>
>>>>  - grouping traffic-rates
>>>>    Add a units statement to each leaf. Not sure what units to use
>>>>    but it should be consistent. (e.g, pps, bps used in descriptions
>>>>    should also be in a units-stmt)
>>>>
>>>>  - grouping i2nsf-system-counter-type-content
>>>>    These counters should use the yang:counter32 type instead of uint32
>>>>
>>>>  - container counters/system-interface
>>>>  - container counters/nsf-firewall
>>>>  - container counters/nsf-policy-hits
>>>>   The descriptions are too terse and confusing, and need a rewrite.
>>>>
>>>>  -  container counters/nsf-firewall
>>>>  -  container counters/nsf-policy-hits
>>>>     - uses i2nsf-nsf-counters-type-content;
>>>>     Many of the fields expanded from this grouping all say
>>>>     they refer to 'the packet'. Why are they in this global
>>>>     container of counters? E.g. (src-ip, dst-ip, src-port, dst-port)
>>>>     Not clear at all how the server is supposed to apply this
>>>>     grouping to these containers.
>>>>
>>>>  - many leafs use "uint32" type for a rate.
>>>>    Should add a units-stmt
>>>>
>>>>  - leaf counters/nsf-policy-hits/hit-times
>>>>    The purpose and type are confusing and generic.
>>>>    If this is a counter then use counter32
>>>>
>>>>  - cut-and-paste for notification-stmt content should be replaced
>>>>    with grouping/uses instead. Applies to the nsf-detection-*
>>>>    and the various logging notifications. Even a grouping that
>>>>    has 1 object in it is better than cut-and-paste 5+ times
>>>>
>>>> Minor Issues:
>>>>
>>>>  - top-level identifiers are too generic
>>>>    should have 'i2nsf-' prefix to be more reusable outside this module
>>>>
>>>>  - quite a lot of identities that an implementation is required to
>>>> support.
>>>>    If this set of identities might change a lot faster than the
>>>>    notifications and counter objects, then consider putting them
>>>>    in a separate module
>>>>
>>>>  - leaf with same type named differently; both intrusion-attack-type
>>>>    - nsf-detection-intrusion/sub-attack-type
>>>>    - nsf-log-intrusion/attack-type
>>>>
>>>>  - quite a lot of notification event types for a server to implement
>>>>    and a user to manage. All are mandatory (no if-feature statements).
>>>>    Some such as nsf-detection-* subset are very similar.
>>>>    A section or table would be useful that showed the YANG notification
>>>>    names and their purpose -- maybe a reference to another RFC
>>>>    with more details
>>>>
>>>>  - there seems to be notifications for intrusion events and then
>>>>    again for the logging of those events.  This seems excessive
>>>>    but
>>>>
>>>>
>>>>  - grouping common-monitoring-data/time-stamp
>>>>    Is this a different time stamp than the one in the NETCONF
>>>> notification?
>>>>    The 'message generation time' sounds like the standard timestamp.
>>>>    Is this event detection time?
>>>>
>>>>  - grouping common-monitoring-data/module-name
>>>>    Is this a YANG module or some other type of module?
>>>>
>>>>  - there is no way to configure which notifications should be generated
>>>>    or maybe how often.  YANG Push has its own dampening-period.
>>>>    Since these are event stream subscriptions, not datastore
>>>> subscriptions,
>>>>    YANG-Push does not apply to this document at all.
>>>>
>>>>    If there are a lot of notifications then a server implementation
>>>>    might drop some
>>>>
>>>>  - grouping i2nsf-nsf-event-type-content-extend/src-zone
>>>>  - grouping i2nsf-nsf-event-type-content-extend/src-zone
>>>>    These use type 'string'. Consider using a typedef that constrains
>>>>    the string.  General comment where unconstrained string is used:
>>>>    The corner-case values such as empty string are often not allowed
>>>>    in implementations.
>>>>
>>>>
>>>>  - grouping i2nsf-nsf-event-type-content-extend/rule-id
>>>>  - grouping i2nsf-nsf-event-type-content-extend/rule-name
>>>>  - grouping i2nsf-nsf-event-type-content-extend/profile
>>>>    These objects seem to reference objects in another YANG module.
>>>>    If so, then leafref types might be more appropriate.
>>>>
>>>>  - grouping i2nsf-nsf-event-type-content/rule-id
>>>>  - grouping i2nsf-nsf-event-type-content/rule-name
>>>>  - grouping i2nsf-nsf-event-type-content/profile
>>>>  - grouping i2nsf-nsf-event-type-content/raw-info
>>>>    These objects are cut-and-paste duplicates from
>>>>    grouping i2nsf-nsf-event-type-content. They should
>>>>    be in a separate grouping used by both. Also applies
>>>>    to some other sets of objects
>>>>
>>>>  - limits issues (e.g. current-session, maximum-session
>>>>    The type is uint8. This is only OK it is impossible for any
>>>>    implementation to ever have or want more than 255 of them.
>>>>    If some other RFC really does limit the values where uint8
>>>>    is used, then that is OK. If so, a reference-stmt would help.
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> I2nsf mailing list
>>>> I2nsf@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/i2nsf
>>>>
>>>
>>>
>>> --
>>> ===========================
>>> Mr. Jaehoon (Paul) Jeong, Ph.D.
>>> Associate Professor
>>> Department of Computer Science and Engineering
>>> Sungkyunkwan University
>>> Office: +82-31-299-4957
>>> Email: jaehoon.paul@gmail.com, pauljeong@skku.edu
>>> Personal Homepage: http://iotlab.skku.edu/people-jaehoon-jeong.php
>>> <http://cpslab.skku.edu/people-jaehoon-jeong.php>
>>>
>>
>
> --
> ===========================
> Mr. Jaehoon (Paul) Jeong, Ph.D.
> Associate Professor
> Department of Computer Science and Engineering
> Sungkyunkwan University
> Office: +82-31-299-4957
> Email: jaehoon.paul@gmail.com, pauljeong@skku.edu
> Personal Homepage: http://iotlab.skku.edu/people-jaehoon-jeong.php
> <http://cpslab.skku.edu/people-jaehoon-jeong.php>
>

--000000000000cc91a905b0f9580d
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><br></div><br><div class=3D"gmail_quote">=
<div dir=3D"ltr" class=3D"gmail_attr">On Mon, Oct 5, 2020 at 9:05 PM Mr. Ja=
ehoon Paul Jeong &lt;<a href=3D"mailto:jaehoon.paul@gmail.com">jaehoon.paul=
@gmail.com</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=
=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding=
-left:1ex"><div dir=3D"ltr">Andy,<div>What do you mean by the event stream?=
</div><div><br></div></div></blockquote><div><br></div><div><a href=3D"http=
s://tools.ietf.org/html/rfc8639#section-2.1">https://tools.ietf.org/html/rf=
c8639#section-2.1</a></div><div><br></div><div>=C2=A0</div><blockquote clas=
s=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid r=
gb(204,204,204);padding-left:1ex"><div dir=3D"ltr"><div></div><div>Actually=
, I am thinking that the NETCONF can deliver the monitoring data of a syste=
m or an NSF in an XML file.</div><div><br></div><div>Do you think that we n=
eed another way to convey the monitoring data?</div><div><br></div><div>Tha=
nks.</div><div><br></div><div>Best Regards,</div><div>Paul</div></div><br><=
div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Tue, Oct=
 6, 2020 at 12:30 PM Andy Bierman &lt;<a href=3D"mailto:andy@yumaworks.com"=
 target=3D"_blank">andy@yumaworks.com</a>&gt; wrote:<br></div><blockquote c=
lass=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px soli=
d rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr"><div dir=3D"ltr"><br>=
</div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">=
On Mon, Oct 5, 2020 at 7:30 PM Mr. Jaehoon Paul Jeong &lt;<a href=3D"mailto=
:jaehoon.paul@gmail.com" target=3D"_blank">jaehoon.paul@gmail.com</a>&gt; w=
rote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0p=
x 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir=
=3D"ltr">Hi Andy,<div>Thanks for your valuable comments on our NSF Monitori=
ng YANG Data Model Draft.</div><div>We authors will reflect your comments o=
n the revision and come back to you with</div><div>the revised draft and re=
vision letter.</div><div><br></div></div></blockquote><div><br></div><div>I=
 forgot 1 comment:</div><div><br></div><div>=C2=A0- the draft is not that e=
xplicit about the event stream to use for these notifications</div><div>=C2=
=A0 =C2=A0Perhaps a new standard event stream (I2NSF) would be better than =
the standard (NETCONF)</div><div>=C2=A0 =C2=A0The draft should be more clea=
r wrt/ the NETCONF stream.</div><div><br></div><div><br></div><div>Andy</di=
v><div><br></div><div>=C2=A0=C2=A0</div><blockquote class=3D"gmail_quote" s=
tyle=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);pad=
ding-left:1ex"><div dir=3D"ltr"><div></div><div>Thanks.</div><div><br></div=
><div>Best Regards,</div><div>Paul</div><div><br></div></div><br><div class=
=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Tue, Oct 6, 2020 =
at 3:03 AM Andy Bierman via Datatracker &lt;<a href=3D"mailto:noreply@ietf.=
org" target=3D"_blank">noreply@ietf.org</a>&gt; wrote:<br></div><blockquote=
 class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px so=
lid rgb(204,204,204);padding-left:1ex">Reviewer: Andy Bierman<br>
Review result: Almost Ready<br>
<br>
<br>
<br>
Major Issues:<br>
<br>
=C2=A0- None<br>
<br>
Moderate Issues:<br>
<br>
=C2=A0- top-level &#39;counters&#39; container does not follow naming conve=
ntions.<br>
=C2=A0 =C2=A0Should start with &#39;i2nsf&#39;, probably &#39;i2nsf-state&#=
39;<br>
<br>
=C2=A0- There do not seem to be any writable objects in the /counters<br>
=C2=A0 =C2=A0subtree so this container should have a &#39;config false&#39;=
 statement<br>
<br>
=C2=A0- top-level typedef and grouping description-stmts are self-referenti=
al<br>
=C2=A0 =C2=A0and not useful. Need to rewrite description-stmts and/or add<b=
r>
=C2=A0 =C2=A0reference-stmts as needed.<br>
<br>
=C2=A0- grouping common-monitoring-data/time-stamp<br>
=C2=A0 =C2=A0Is this a different time stamp than the one in the NETCONF not=
ification?<br>
=C2=A0 =C2=A0The &#39;message generation time&#39; sounds like the standard=
 timestamp.<br>
=C2=A0 =C2=A0Does this object represent the event detection time?<br>
<br>
=C2=A0- grouping i2nsf-system-alarm-type-content/usage<br>
=C2=A0- grouping i2nsf-system-alarm-type-content/threshold<br>
=C2=A0 =C2=A0These are uint8 leafs with unclear descriptions.<br>
=C2=A0 =C2=A0Not sure why uint8 is the appropriate type.<br>
=C2=A0 =C2=A0Needs 1 or more of (reference, units, better description)<br>
<br>
=C2=A0- grouping traffic-rates<br>
=C2=A0 =C2=A0Add a units statement to each leaf. Not sure what units to use=
<br>
=C2=A0 =C2=A0but it should be consistent. (e.g, pps, bps used in descriptio=
ns<br>
=C2=A0 =C2=A0should also be in a units-stmt)<br>
<br>
=C2=A0- grouping i2nsf-system-counter-type-content<br>
=C2=A0 =C2=A0These counters should use the yang:counter32 type instead of u=
int32<br>
<br>
=C2=A0- container counters/system-interface<br>
=C2=A0- container counters/nsf-firewall<br>
=C2=A0- container counters/nsf-policy-hits<br>
=C2=A0 The descriptions are too terse and confusing, and need a rewrite.<br=
>
<br>
=C2=A0-=C2=A0 container counters/nsf-firewall<br>
=C2=A0-=C2=A0 container counters/nsf-policy-hits<br>
=C2=A0 =C2=A0 - uses i2nsf-nsf-counters-type-content;<br>
=C2=A0 =C2=A0 Many of the fields expanded from this grouping all say<br>
=C2=A0 =C2=A0 they refer to &#39;the packet&#39;. Why are they in this glob=
al<br>
=C2=A0 =C2=A0 container of counters? E.g. (src-ip, dst-ip, src-port, dst-po=
rt)<br>
=C2=A0 =C2=A0 Not clear at all how the server is supposed to apply this<br>
=C2=A0 =C2=A0 grouping to these containers.<br>
<br>
=C2=A0- many leafs use &quot;uint32&quot; type for a rate.<br>
=C2=A0 =C2=A0Should add a units-stmt<br>
<br>
=C2=A0- leaf counters/nsf-policy-hits/hit-times<br>
=C2=A0 =C2=A0The purpose and type are confusing and generic.<br>
=C2=A0 =C2=A0If this is a counter then use counter32<br>
<br>
=C2=A0- cut-and-paste for notification-stmt content should be replaced<br>
=C2=A0 =C2=A0with grouping/uses instead. Applies to the nsf-detection-*<br>
=C2=A0 =C2=A0and the various logging notifications. Even a grouping that<br=
>
=C2=A0 =C2=A0has 1 object in it is better than cut-and-paste 5+ times<br>
<br>
Minor Issues:<br>
<br>
=C2=A0- top-level identifiers are too generic<br>
=C2=A0 =C2=A0should have &#39;i2nsf-&#39; prefix to be more reusable outsid=
e this module<br>
<br>
=C2=A0- quite a lot of identities that an implementation is required to sup=
port.<br>
=C2=A0 =C2=A0If this set of identities might change a lot faster than the<b=
r>
=C2=A0 =C2=A0notifications and counter objects, then consider putting them<=
br>
=C2=A0 =C2=A0in a separate module<br>
<br>
=C2=A0- leaf with same type named differently; both intrusion-attack-type<b=
r>
=C2=A0 =C2=A0- nsf-detection-intrusion/sub-attack-type<br>
=C2=A0 =C2=A0- nsf-log-intrusion/attack-type<br>
<br>
=C2=A0- quite a lot of notification event types for a server to implement<b=
r>
=C2=A0 =C2=A0and a user to manage. All are mandatory (no if-feature stateme=
nts).<br>
=C2=A0 =C2=A0Some such as nsf-detection-* subset are very similar.<br>
=C2=A0 =C2=A0A section or table would be useful that showed the YANG notifi=
cation<br>
=C2=A0 =C2=A0names and their purpose -- maybe a reference to another RFC<br=
>
=C2=A0 =C2=A0with more details<br>
<br>
=C2=A0- there seems to be notifications for intrusion events and then<br>
=C2=A0 =C2=A0again for the logging of those events.=C2=A0 This seems excess=
ive<br>
=C2=A0 =C2=A0but<br>
<br>
<br>
=C2=A0- grouping common-monitoring-data/time-stamp<br>
=C2=A0 =C2=A0Is this a different time stamp than the one in the NETCONF not=
ification?<br>
=C2=A0 =C2=A0The &#39;message generation time&#39; sounds like the standard=
 timestamp.<br>
=C2=A0 =C2=A0Is this event detection time?<br>
<br>
=C2=A0- grouping common-monitoring-data/module-name<br>
=C2=A0 =C2=A0Is this a YANG module or some other type of module?<br>
<br>
=C2=A0- there is no way to configure which notifications should be generate=
d<br>
=C2=A0 =C2=A0or maybe how often.=C2=A0 YANG Push has its own dampening-peri=
od.<br>
=C2=A0 =C2=A0Since these are event stream subscriptions, not datastore subs=
criptions,<br>
=C2=A0 =C2=A0YANG-Push does not apply to this document at all.<br>
<br>
=C2=A0 =C2=A0If there are a lot of notifications then a server implementati=
on<br>
=C2=A0 =C2=A0might drop some<br>
<br>
=C2=A0- grouping i2nsf-nsf-event-type-content-extend/src-zone<br>
=C2=A0- grouping i2nsf-nsf-event-type-content-extend/src-zone<br>
=C2=A0 =C2=A0These use type &#39;string&#39;. Consider using a typedef that=
 constrains<br>
=C2=A0 =C2=A0the string.=C2=A0 General comment where unconstrained string i=
s used:<br>
=C2=A0 =C2=A0The corner-case values such as empty string are often not allo=
wed<br>
=C2=A0 =C2=A0in implementations.<br>
<br>
<br>
=C2=A0- grouping i2nsf-nsf-event-type-content-extend/rule-id<br>
=C2=A0- grouping i2nsf-nsf-event-type-content-extend/rule-name<br>
=C2=A0- grouping i2nsf-nsf-event-type-content-extend/profile<br>
=C2=A0 =C2=A0These objects seem to reference objects in another YANG module=
.<br>
=C2=A0 =C2=A0If so, then leafref types might be more appropriate.<br>
<br>
=C2=A0- grouping i2nsf-nsf-event-type-content/rule-id<br>
=C2=A0- grouping i2nsf-nsf-event-type-content/rule-name<br>
=C2=A0- grouping i2nsf-nsf-event-type-content/profile<br>
=C2=A0- grouping i2nsf-nsf-event-type-content/raw-info<br>
=C2=A0 =C2=A0These objects are cut-and-paste duplicates from<br>
=C2=A0 =C2=A0grouping i2nsf-nsf-event-type-content. They should<br>
=C2=A0 =C2=A0be in a separate grouping used by both. Also applies<br>
=C2=A0 =C2=A0to some other sets of objects<br>
<br>
=C2=A0- limits issues (e.g. current-session, maximum-session<br>
=C2=A0 =C2=A0The type is uint8. This is only OK it is impossible for any<br=
>
=C2=A0 =C2=A0implementation to ever have or want more than 255 of them.<br>
=C2=A0 =C2=A0If some other RFC really does limit the values where uint8<br>
=C2=A0 =C2=A0is used, then that is OK. If so, a reference-stmt would help.<=
br>
<br>
<br>
<br>
_______________________________________________<br>
I2nsf mailing list<br>
<a href=3D"mailto:I2nsf@ietf.org" target=3D"_blank">I2nsf@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/i2nsf" rel=3D"noreferrer" =
target=3D"_blank">https://www.ietf.org/mailman/listinfo/i2nsf</a><br>
</blockquote></div><br clear=3D"all"><div><br></div>-- <br><div dir=3D"ltr"=
><div dir=3D"ltr"><div><div dir=3D"ltr"><div><div dir=3D"ltr"><div><div dir=
=3D"ltr">=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D<br>Mr. Jaehoon (Paul) Jeong, Ph.D.<br>Associate Professor<b=
r>Department of Computer Science and Engineering<br>Sungkyunkwan University=
<br>Office: +82-31-299-4957<br>Email: <a href=3D"mailto:jaehoon.paul@gmail.=
com" target=3D"_blank">jaehoon.paul@gmail.com</a>,=C2=A0<a href=3D"mailto:p=
auljeong@skku.edu" style=3D"font-size:12.8px" target=3D"_blank">pauljeong@s=
kku.edu</a><br>Personal Homepage: <a href=3D"http://cpslab.skku.edu/people-=
jaehoon-jeong.php" target=3D"_blank">http://iotlab.skku.edu/people-jaehoon-=
jeong.php</a><br></div></div></div></div></div></div></div></div>
</blockquote></div></div>
</blockquote></div><br clear=3D"all"><div><br></div>-- <br><div dir=3D"ltr"=
><div dir=3D"ltr"><div><div dir=3D"ltr"><div><div dir=3D"ltr"><div><div dir=
=3D"ltr">=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D<br>Mr. Jaehoon (Paul) Jeong, Ph.D.<br>Associate Professor<b=
r>Department of Computer Science and Engineering<br>Sungkyunkwan University=
<br>Office: +82-31-299-4957<br>Email: <a href=3D"mailto:jaehoon.paul@gmail.=
com" target=3D"_blank">jaehoon.paul@gmail.com</a>,=C2=A0<a href=3D"mailto:p=
auljeong@skku.edu" style=3D"font-size:12.8px" target=3D"_blank">pauljeong@s=
kku.edu</a><br>Personal Homepage: <a href=3D"http://cpslab.skku.edu/people-=
jaehoon-jeong.php" target=3D"_blank">http://iotlab.skku.edu/people-jaehoon-=
jeong.php</a><br></div></div></div></div></div></div></div></div>
</blockquote></div></div>

--000000000000cc91a905b0f9580d--


From nobody Tue Oct  6 04:57:40 2020
Return-Path: <mohit.m.sethi@ericsson.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 E4B5B3A0853; Tue,  6 Oct 2020 04:57:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.513
X-Spam-Level: 
X-Spam-Status: No, score=-3.513 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-1.2, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.213, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.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 Nd3R1Y5RjMYC; Tue,  6 Oct 2020 04:57:32 -0700 (PDT)
Received: from EUR05-AM6-obe.outbound.protection.outlook.com (mail-am6eur05on2066.outbound.protection.outlook.com [40.107.22.66]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id ECB993A07DB; Tue,  6 Oct 2020 04:57:31 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=AL9BycId49N2dN6NkxHJXHzicorfVZ1pXFIsdT3hTueROLxEwog+8wuHDCTFehMA4ipT3Zx0/H2iDJZrVdeMNOnKM3JXiHmByJRYVAAxcifKgz1/i8JQdDaLK9uGuvZW7RDWS0BoFE/lF02FC4/3TNC1mzRDvFSytLttjiIfTYNhLQPT6SzK6MCNHQ3pXfjGV7Y/Vg3+oOJ3PwS3cZmHumCU8VV7jND/sLZROnaMXF+C0FubUSSJRuA3gZk+VLKRouX7fAUFVUo8O+AYkIU+7lXEfs9YpE0NYswDrrTyKs7GNeRQ/XmTuQ/9hJH/MYfG31Yc3kIa0zsz8zc3cxgD+g==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=4lz0MX1nCaDqUFlgBXOxWmSLkKVwBmPbozYYvshxW4M=; b=ZOwpGr70JygMgeOuTTO7ylegnDFh8mcHUpfeSI2p4+H21GrU9Gq98PkMYUzL+Gtu+06ZJgCAIEAKsd+iCw7OuZSxSw7lPWc4oMgnNj6iGtx+e/LR1/ehgUHFni8A3ApbZNeURIR0WNBzgeS+k1AG4oM0lgMzBPFDLb/Sh+WgRcTuuCaloNumQ7aUxtAR1Ysj5iLu/gSXRP9S53qUQmXboOGCb4azYH1kOBqJKgTO4c+V5oKc1EKqRUx8yykeRuukDfr8hYeFPNR2JUKN6IefSyEb79vD04EtZhfZohMlmlR0n6JoRlfAavgUb07BUOlAWtQTFx5BgTKecpxDTt/2MA==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=ericsson.com; dmarc=pass action=none header.from=ericsson.com; dkim=pass header.d=ericsson.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ericsson.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=4lz0MX1nCaDqUFlgBXOxWmSLkKVwBmPbozYYvshxW4M=; b=gUAyCGKwJw4Q7jVEkAtn2ggYll+DVJKWPxL8Hn0YUkPZapXikVXElxXGloFOcteLF7sTB49nEYwE2Qyuretr5VCuOVUwoR+UoJQvRVBcfwAQu0IUG+2tfCl+fZeHkPyPTQvKse3CEL/n7xAmFNmiTAGTxVzRZD/zTnU+kfV3Hro=
Received: from HE1PR07MB3209.eurprd07.prod.outlook.com (2603:10a6:7:32::14) by HE1PR07MB4284.eurprd07.prod.outlook.com (2603:10a6:7:9f::29) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3455.16; Tue, 6 Oct 2020 11:57:28 +0000
Received: from HE1PR07MB3209.eurprd07.prod.outlook.com ([fe80::1550:2d88:a5be:95ca]) by HE1PR07MB3209.eurprd07.prod.outlook.com ([fe80::1550:2d88:a5be:95ca%6]) with mapi id 15.20.3455.021; Tue, 6 Oct 2020 11:57:28 +0000
From: Mohit Sethi M <mohit.m.sethi@ericsson.com>
To: Rafa Marin-Lopez <rafa@um.es>, Mohit Sethi M <mohit.m.sethi@ericsson.com>
CC: "i2nsf@ietf.org" <i2nsf@ietf.org>, "last-call@ietf.org" <last-call@ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>, "draft-ietf-i2nsf-sdn-ipsec-flow-protection.all@ietf.org" <draft-ietf-i2nsf-sdn-ipsec-flow-protection.all@ietf.org>
Thread-Topic: [Last-Call] [I2nsf] Genart last call review of draft-ietf-i2nsf-sdn-ipsec-flow-protection-08
Thread-Index: AQHWkKt1tGKu7fnOmEKnrNDccEWBzqmKjmGA
Date: Tue, 6 Oct 2020 11:57:28 +0000
Message-ID: <486e2620-192a-e0c7-21c1-480cc1d5f69a@ericsson.com>
References: <159887332289.3841.15922213310506259874@ietfa.amsl.com> <F944D89A-BED3-4D6F-9A32-18E78E30ECCD@um.es>
In-Reply-To: <F944D89A-BED3-4D6F-9A32-18E78E30ECCD@um.es>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0
authentication-results: um.es; dkim=none (message not signed) header.d=none;um.es; dmarc=none action=none header.from=ericsson.com;
x-originating-ip: [2001:14bb:140:4727:d1cc:b05:e22c:8917]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: d833ade1-a1ef-4ef5-2cff-08d869eeffcf
x-ms-traffictypediagnostic: HE1PR07MB4284:
x-ms-exchange-transport-forked: True
x-microsoft-antispam-prvs: <HE1PR07MB42844188062F1D09D927A8A7D00D0@HE1PR07MB4284.eurprd07.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:6430;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: Zyd5XS3E/78Y3L7BZ7X1eKk0RVW77K6wXqTV5po57T577ifYmHQb6di1gARMcgLcUeDsAi0MmtoPVs7PRrwYSfjGSmEnuBxeQ3XhWAmZCG7PPKG1RCZMOG1Lrpztx+oDCnm3gimGckGTovPSp67nqDHMolS6XylUL+BF3V2YOCsf/oNW/QUv/5W+BmM38yKmhJ6/fEHP+KBEtzWdZJYMwZz7qvlFwe/X/Ou4smnozzOueaHC+Vq/to9m73K+dUJkgXNJArwPdWgEWZmFm0VAtr0SQ0CWjgpYdBDqY5P7L+R3CGa33WA5rgIs9l2QT8ftI1aR09Yg9wbsqbvpz8BQ98PqbO9cXYZcbG2CBtMep8QzhcUF71WebEn1G3ctPIZdhMrLQo/ODFwKNhmsszqOt4DYbfGT/+cAlmUNWx6rIPrxUu/xAfGgUsGdeXiwZOGD4Wdrn5azHPz1MYJIj/gYqQ==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;  IPV:NLI; SFV:NSPM; H:HE1PR07MB3209.eurprd07.prod.outlook.com; PTR:; CAT:NONE;  SFS:(4636009)(396003)(346002)(376002)(136003)(366004)(39860400002)(4326008)(2906002)(316002)(186003)(83380400001)(36756003)(6486002)(53546011)(2616005)(31686004)(76116006)(54906003)(71200400001)(5660300002)(66946007)(66556008)(64756008)(66476007)(66446008)(8676002)(166002)(966005)(478600001)(6506007)(31696002)(6512007)(86362001)(83080400001)(8936002)(110136005)(43740500002); DIR:OUT; SFP:1101; 
x-ms-exchange-antispam-messagedata: MFnG0EEln+xDa813h+VasXJQ+LkJTtq55go1EGgHwbTGg+T6r7QLh8yvkDW9WHQMDuhKwWrErCuqHzHwu2gxzD1Ps0ZwpqYgUdRXfVXDYYgfpHrdw/ZUjHYTtpka4pB97UO0DfD+Oz6B6ZaboD+bEy+NEjYx8WP0HG98lMh4IPCDojy88KAWS9wGadnKYDuuhij3Xhl+WtIAMHnYWqwGYrOQbO19XpGqWNQKFxrVAAp0UfnwTLSCjKxRntchuFZYBdom+8thRp12hFMTsyfmvkJscWKJnyKJVZNdENZSSgTcmKO6UMCCbnVL9acZAWFNtMJ5If0pGIIyPRA66NZEPz9cdzYhCAwb7qEwhZl0Bmkp6kmlQ5zlO1DomyfW03DHvxx1K6S8U9wBzYDzP8GnEejEeJDk3oRfktc8BWLLKMKYVsZGzZUGVDvyeYLKeTkniBy/XKBzk/Tni6uCwgLmcI9Q22pcL0+Yps9wzsHAWYDJznkfypqexO419l+DhxvX7ggeL8PXzqIx6yZDBfPXcrq6LyFilWvGy/JmRjHv87zpoLbuVhnuWuufvZ4A7Aj+X80n/im1lp7gtqorDUx1+BEX+SkW2/dkcIOc1+/Pvo3p2mvfeVj8HZ3jJXkSHBtQDxCGdZ9urWrUGcqcix3VxZpyjkZeS8IaWLtg6SPllVqwjKmcoaR/CvOxiHx994LVewDT01m9zLjA2Rj2KbXF1w==
Content-Type: multipart/alternative; boundary="_000_486e2620192ae0c721c1480cc1d5f69aericssoncom_"
MIME-Version: 1.0
X-OriginatorOrg: ericsson.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: HE1PR07MB3209.eurprd07.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: d833ade1-a1ef-4ef5-2cff-08d869eeffcf
X-MS-Exchange-CrossTenant-originalarrivaltime: 06 Oct 2020 11:57:28.6486 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 92e84ceb-fbfd-47ab-be52-080c6b87953f
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: HWu6NZ6SggRd9Ic2e11gt57V/hkUlzYQg/owALaXSTB88MdsuvRx+KE8XUHv6e7hnKHz39eZOadUOQIjQrrrGGy6rAbNNaBZo5aNQTbityk=
X-MS-Exchange-Transport-CrossTenantHeadersStamped: HE1PR07MB4284
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2nsf/vBqJCRq1Rwknv1oFypnj2rdfuic>
Subject: Re: [I2nsf] [Last-Call] Genart last call review of draft-ietf-i2nsf-sdn-ipsec-flow-protection-08
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: Tue, 06 Oct 2020 11:57:35 -0000

--_000_486e2620192ae0c721c1480cc1d5f69aericssoncom_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

SGkgUmFmYSwNCg0KVGhhbmtzIGZvciBhZGRyZXNzaW5nIG15IGNvbW1lbnRzLiBZb3VyIGNoYW5n
ZXMgYW5kIHVwZGF0ZXMgbG9vayBnb29kLg0KDQotLU1vaGl0DQoNCk9uIDkvMjIvMjAgOTo0MSBB
TSwgUmFmYSBNYXJpbi1Mb3BleiB3cm90ZToNCkRlYXIgTW9oaXQ6DQoNClRoYW5rIHlvdSB2ZXJ5
IG11Y2ggZm9yIHlvdXIgcmV2aWV3LiBXZSByZWFsbHkgYXBwcmVjaWF0ZSBpdC4gUGxlYXNlIHNl
ZSBvdXIgY29tbWVudHMgaW5saW5lOg0KDQpFbCAzMSBhZ28gMjAyMCwgYSBsYXMgMTM6MjgsIE1v
aGl0IFNldGhpIHZpYSBEYXRhdHJhY2tlciA8bm9yZXBseUBpZXRmLm9yZzxtYWlsdG86bm9yZXBs
eUBpZXRmLm9yZz4+IGVzY3JpYmnDszoNCg0KUmV2aWV3ZXI6IE1vaGl0IFNldGhpDQpSZXZpZXcg
cmVzdWx0OiBPbiB0aGUgUmlnaHQgVHJhY2sNCg0KSSBhbSB0aGUgYXNzaWduZWQgR2VuLUFSVCBy
ZXZpZXdlciBmb3IgdGhpcyBkcmFmdC4gVGhlIEdlbmVyYWwgQXJlYQ0KUmV2aWV3IFRlYW0gKEdl
bi1BUlQpIHJldmlld3MgYWxsIElFVEYgZG9jdW1lbnRzIGJlaW5nIHByb2Nlc3NlZA0KYnkgdGhl
IElFU0cgZm9yIHRoZSBJRVRGIENoYWlyLiAgUGxlYXNlIHRyZWF0IHRoZXNlIGNvbW1lbnRzIGp1
c3QNCmxpa2UgYW55IG90aGVyIGxhc3QgY2FsbCBjb21tZW50cy4NCg0KRm9yIG1vcmUgaW5mb3Jt
YXRpb24sIHBsZWFzZSBzZWUgdGhlIEZBUSBhdA0KDQo8aHR0cHM6Ly90cmFjLmlldGYub3JnL3Ry
YWMvZ2VuL3dpa2kvR2VuQXJ0ZmFxPi4NCg0KRG9jdW1lbnQ6IGRyYWZ0LWlldGYtaTJuc2Ytc2Ru
LWlwc2VjLWZsb3ctcHJvdGVjdGlvbi0wOA0KUmV2aWV3ZXI6IE1vaGl0IFNldGhpDQpSZXZpZXcg
RGF0ZTogMjAyMC0wOC0zMQ0KSUVURiBMQyBFbmQgRGF0ZTogMjAyMC0wOS0wNA0KSUVTRyBUZWxl
Y2hhdCBkYXRlOiBOb3Qgc2NoZWR1bGVkIGZvciBhIHRlbGVjaGF0DQoNClN1bW1hcnk6IFRoaXMg
ZG9jdW1lbnQgZGVzY3JpYmVzIGhvdyBJUHNlYyBTQXMgY2FuIGJlIHNldHVwIGZyb20gYSBjZW50
cmFsaXplZA0KSTJOU0YgY29udHJvbGxlci4gVGhlIGRvY3VtZW50IGlzICJPbiB0aGUgUmlnaHQg
VHJhY2siLg0KDQpNYWpvciBpc3N1ZXM6DQotIFRoZSBkb2N1bWVudCBzaG91bGQgaGlnaGxpZ2h0
IGluIHRoZSBhYnN0cmFjdCBhbmQgZWxzZXdoZXJlIHRoYXQgaXQgZG9lcyBub3QNCmRlZmluZSBh
IHByb3RvY29sIGJldHdlZW4gdGhlIEkyTlNGIGNvbnRyb2xsZXIgYW5kIHRoZSBOU0YuIEl0IG9u
bHkgc3BlY2lmaWVzDQp0aGUgWUFORyBtb2RlbC4gU2V2ZXJhbCBhcHBlbmRpY2VzIHJlZmVyIHRv
IG5vdGlmaWNhdGlvbiBtZXNzYWdlcy4gV2hlcmUgYXJlDQp0aGV5IGRlZmluZWQvc3BlY2lmaWVk
Pw0KDQpbQXV0aG9yc10gUmVnYXJkaW5nIHRoZSBhYnN0cmFjdCwgd2UgaGF2ZSBhcHBsaWVkIHlv
dXIgc3VnZ2VzdGlvbnMuIFdlIGNhbiBhbHNvIGluY2x1ZGUgYSBmZXcgd29yZHMgdG8gaGlnaGxp
Z2h0IHRoZSBhc3BlY3QgeW91IG1lbnRpb246IHdlIGRvIG5vdCBkZWZpbmUgYW55IG5ldyBwcm90
b2NvbCBidXQgYSBZQU5HIG1vZGVsLg0KDQpUaGlzIGRvY3VtZW50IGRlc2NyaWJlcyBob3cgdG8g
cHJvdmlkZSBJUHNlYy1iYXNlZCBmbG93IHByb3RlY3Rpb24gKGludGVncml0eQ0KYW5kIGNvbmZp
ZGVudGlhbGl0eSkgYnkgbWVhbnMgb2YgYW4gSW50ZXJmYWNlIHRvIE5ldHdvcmsgU2VjdXJpdHkg
RnVuY3Rpb24NCihJMk5TRikgY29udHJvbGxlci4gIEl0IGNvbnNpZGVycyB0d28gbWFpbiB3ZWxs
LWtub3duIHNjZW5hcmlvcyBpbiBJUHNlYzogKGkpDQpnYXRld2F5LXRvLWdhdGV3YXkgYW5kIChp
aSkgaG9zdC10by1ob3N0LiAgVGhlIHNlcnZpY2UgZGVzY3JpYmVkIGluIHRoaXMNCmRvY3VtZW50
IGFsbG93cyB0aGUgY29uZmlndXJhdGlvbiBhbmQgbW9uaXRvcmluZyBvZiBJUHNlYyBTZWN1cml0
eSBBc3NvY2lhdGlvbnMNCihTQXMpIGZyb20gYSBJMk5TRiBDb250cm9sbGVyIHRvIG9uZSBvciBz
ZXZlcmFsIGZsb3ctYmFzZWQgTmV0d29yayBTZWN1cml0eQ0KRnVuY3Rpb25zIChOU0ZzKSB0aGF0
IHJlbHkgb24gSVBzZWMgdG8gcHJvdGVjdCBkYXRhIHRyYWZmaWMuDQoNClRoZSBkb2N1bWVudCBm
b2N1c2VzIG9uIHRoZSBJMk5TRiBOU0YtZmFjaW5nIGludGVyZmFjZSBieSBwcm92aWRpbmcgWUFO
RyBkYXRhDQptb2RlbHMgZm9yIGNvbmZpZ3VyaW5nIHRoZSBJUHNlYyBkYXRhYmFzZXMgKFNQRCwg
U0FELCBQQUQpIGFuZCBJS0V2Mi4gVGhlcmVmb3JlLCBpdCBkb2VzIG5vdCBub3QgZGVmaW5lIGFu
eSBuZXcgcHJvdG9jb2wuIFRoaXMNCmFsbG93cyBJUHNlYyBTQSBlc3RhYmxpc2htZW50IHdpdGgg
bWluaW1hbCBpbnRlcnZlbnRpb24gYnkgdGhlIG5ldHdvcmsNCmFkbWluaXN0cmF0b3IuDQoNCg0K
V2l0aCByZXNwZWN0IHRvIG5vdGlmaWNhdGlvbnMsIHRoZXkgYXJlIGRlZmluZWQgaW4gTkVUQ09O
RiBpdHNlbGYgYnV0IHdlIGhhZCB0byBkZWZpbmUgdGhyb3VnaCB0aGUgWUFORyBtb2RlbCB0aGUg
aW5mb3JtYXRpb24gKG5vdGlmaWNhdGlvbiBkYXRhKSB0aGF0IHdpbGwgYmUgc2VudDoNCg0KRm9y
IGV4YW1wbGU6DQoNCiBub3RpZmljYXRpb25zOg0KICAgICArLS0tbiBzYWRiLWFjcXVpcmUNCiAg
ICAgfCAgKy0tcm8gaXBzZWMtcG9saWN5LW5hbWUgICAgICAgICAgc3RyaW5nDQogICAgIHwgICst
LXJvIHRyYWZmaWMtc2VsZWN0b3INCiAgICAgfCAgICAgKy0tcm8gbG9jYWwtc3VibmV0ICAgICAg
ICAgICAgaW5ldDppcC1wcmVmaXgNCiAgICAgfCAgICAgKy0tcm8gcmVtb3RlLXN1Ym5ldCAgICAg
ICAgICAgaW5ldDppcC1wcmVmaXgNCiAgICAgfCAgICAgKy0tcm8gaW5uZXItcHJvdG9jb2w/ICAg
ICAgICAgaXBzZWMtaW5uZXItcHJvdG9jb2wNCiAgICAgfCAgICAgKy0tcm8gbG9jYWwtcG9ydHMq
IFtzdGFydCBlbmRdDQogICAgIHwgICAgIHwgICstLXJvIHN0YXJ0ICAgICAgICAgICAgICAgIGlu
ZXQ6cG9ydC1udW1iZXINCiAgICAgfCAgICAgfCAgKy0tcm8gZW5kICAgICAgICAgICAgICAgICAg
aW5ldDpwb3J0LW51bWJlcg0KICAgICB8ICAgICArLS1ybyByZW1vdGUtcG9ydHMqIFtzdGFydCBl
bmRdDQogICAgIHwgICAgICAgICstLXJvIHN0YXJ0ICAgICAgICAgICAgICAgIGluZXQ6cG9ydC1u
dW1iZXINCiAgICAgfCAgICAgICAgKy0tcm8gZW5kICAgICAgICAgICAgICAgICAgaW5ldDpwb3J0
LW51bWJlcg0KICAgICArLS0tbiBzYWRiLWV4cGlyZQ0KICAgICB8ICArLS1ybyBpcHNlYy1zYS1u
YW1lICAgICAgICAgICBzdHJpbmcNCiAgICAgfCAgKy0tcm8gc29mdC1saWZldGltZS1leHBpcmU/
ICAgYm9vbGVhbg0KICAgICB8ICArLS1ybyBsaWZldGltZS1jdXJyZW50DQogICAgIHwgICAgICst
LXJvIHRpbWU/ICAgICAgICAgICAgICAgIHVpbnQzMg0KICAgICB8ICAgICArLS1ybyBieXRlcz8g
ICAgICAgICAgICAgICB1aW50MzINCiAgICAgfCAgICAgKy0tcm8gcGFja2V0cz8gICAgICAgICAg
ICAgdWludDMyDQogICAgIHwgICAgICstLXJvIGlkbGU/ICAgICAgICAgICAgICAgIHVpbnQzMg0K
ICAgICArLS0tbiBzYWRiLXNlcS1vdmVyZmxvdw0KICAgICB8ICArLS1ybyBpcHNlYy1zYS1uYW1l
ICAgICAgICAgICBzdHJpbmcNCiAgICAgKy0tLW4gc2FkYi1iYWQtc3BpDQogICAgICAgICstLXJv
IHNwaSAgICAgICAgICAgICAgICAgICAgIHVpbnQzMg0KDQpUaGVyZWZvcmUgV2UgZGVmaW5lIFlB
Tkcgbm90aWZpY2F0aW9ucyBmb3IgdGhlIGlrZWxlc3MgY2FzZSBtYWtpbmcgdXNlIG9mIHRoZSBu
b3RpZmljYXRpb24gbWVzc2FnZSBkZWZpbmVkIGJ5IE5FVENPTkYuDQoNCg0KLSBGb3IgdGhlIElL
RSBjYXNlLCBhIGxvdCB3b3VsZCBkZXBlbmQgb24gdGhlIGNyeXB0b2dyYXBoaWMgc3VpdGVzIGlt
cGxlbWVudGVkDQppbiB0aGUgTlNGLiBGb3IgZXhhbXBsZSwgd2hhdCBpZiB0aGUgSTJOU0YgaXNz
dWVzIGNlcnRpZmljYXRlcyBmb3IgY3VydmVzIG5vdA0KaW1wbGVtZW50ZWQuIFRoZSBkb2N1bWVu
dCBzaG91bGQgbWF5YmUgbWVudGlvbiB0aGF0IHRoZSBJMk5TRiBpcyBhd2FyZSBvZiB0aGUNCk5T
RiBhbmQgaXRzIElLRXYyIGltcGxlbWVudGF0aW9uL3ZlcnNpb24gZGV0YWlscyBiYXNlZCBvbiB3
aGljaCBpdCBpc3N1ZXMgdGhlDQpjcmVkZW50aWFscy4gVGhpcyByZWxhdGVzIHRvIHRoZSB0ZXh0
OiAiYW5kIGFwcGx5aW5nIG90aGVyIElLRXYyIGNvbmZpZ3VyYXRpb24NCnBhcmFtZXRlcnMgKGUu
Zy4gIGNyeXB0b2dyYXBoaWMgYWxnb3JpdGhtcyBmb3IgZXN0YWJsaXNoaW5nIGFuIElLRXYyIFNB
KSIuIFlvdQ0KY2FuJ3QgY29uZmlndXJlIHdoYXQgaXMgbm90IGltcGxlbWVudGVkPw0KDQpXZSB0
aGluayB0aGlzIGlzIGRpc2N1c3NlZCBpbiBTZWN0aW9uIDUuNCBOU0YgcmVnaXN0cmF0aW9uIGFu
ZCBkaXNjb3ZlcnkuIFdlIGFja25vd2xlZGdlZCB0aGF0IEkyTlNGIG11c3QgZGlzY292ZXIgTlNG
IGZlYXR1cmVzLiBIb3dldmVyIHRoaXMgaXMgYSBwcmV2aW91cyBzdGVwIHRvIHdoYXQgd2UgZGVm
aW5lIGluIHRoaXMgSS1ELiBPbmNlIHRoZSBOU0YgaXMgb3BlcmF0aXZlIGFuZCBJMk5TRiBjb250
cm9sbGVyIGhhcyBrbm93bGVkZ2Ugb2YgdGhlIE5TRiBhbmQgdGhlaXIgZmVhdHVyZXMsIHRoZSBJ
Mk5TRiBjb250cm9sbGVyIGNhbiBjb25maWd1cmUgcHJvcGVybHkuDQoNClNob3VsZCB3ZSBleHRl
bmQgdGhlIHNlY3Rpb24gNS40IHNvbWVob3c/IEFueSBzdWdnZXN0aW9uPw0KDQoNCg0KLSBEb2Vz
IHRoZSBzcGVjaWZpY2F0aW9uIGFsbG93IE5TRidzIHRvIGRlcml2ZSBtYW55IENISUxEIFNBcz8N
Cg0KSWYgeW91IGFyZSByZWZlcnJpbmcgdG8gSUtFIGNhc2UsIHRoZSBJS0UgaW1wbGVtZW50YXRp
b24gaW4gdGhlIE5TRiBtYXkgZGVyaXZlIHNldmVyYWwgY2hpbGQgU0FzIGJhc2VkIG9uIGEgcGFy
dGljdWxhciBwb2xpY3kuIEhvd2V2ZXIsIHVuZGVyIEkyTlNGIGNvbnRyb2xsZXIgc3RhbmRwb2lu
dC4NCg0KSW4gdGhlIElLRS1sZXNzIGNhc2UsIHRoZSBJMk5TRiBjb250cm9sbGVyIGNhbiBhcHBs
eSBtdWx0aXBsZSBJUHNlYyBTQXMgaW4gdGhlIE5TRi4NCg0KQmV5b25kIHRoZXNlIGNvbW1lbnRz
IGFsbCB0aGUgbWlub3IgaXNzdWVzIGJlbG93IGhhcyBiZWVuIGFscmVhZHkgZml4ZWQgaW4gdGhl
IHYwOSB3ZSBhcmUgcHJlcGFyaW5nLg0KDQpCZXN0IHJlZ2FyZHMgYW5kIHRoYW5rIHlvdSBzbyBt
dWNoIGFnYWluIQ0KDQoNCg0KTWlub3IgaXNzdWVzOg0KLSBUaGUgZG9jdW1lbnQgaGFzIHNldmVy
YWwgZ3JhbW1hdGljYWwgZXJyb3JzLiBJIGhhdmUgZml4ZWQgbWFueSBvZiB0aGVtIGluIG15DQpy
ZXZpZXcgYmVsb3cgYnV0IHN1cmVseSBub3QgYWxsLiBJIGhvcGUgdGhhdCBjaGFpcnMvQURzIGNv
dWxkIGRvIGFub3RoZXIgcGFzcw0KYmVmb3JlIHNlbmRpbmcgdGhpcyB0byB0aGUgUkZDIGVkaXRv
ci4NCg0KTml0cy9lZGl0b3JpYWwgY29tbWVudHM6DQotIFRoZSBkb2N1bWVudCB1c2VzIHRlcm1z
IHN1Y2ggYXMgTlNGIHNoaXBzL2ltcGxlbWVudHMgSUtFdjIuIFVzZSBjb25zaXN0ZW50DQp0ZXJt
aW5vbG9neS4NCg0KLSBBYnN0cmFjdDogVGhlcmUgd2VyZSB0b28gbWFueSBpc3N1ZXMgd2l0aCB0
aGUgYWJzdHJhY3QgdG8gaW5kaXZpZHVhbGx5IHBvaW50DQpvdXQuIEhlcmUgaXMgYW4gZWRpdGVk
IHZlcnNpb24gZm9yIHlvdSB0byBjb25zaWRlcjoNCg0KVGhpcyBkb2N1bWVudCBkZXNjcmliZXMg
aG93IHRvIHByb3ZpZGUgSVBzZWMtYmFzZWQgZmxvdyBwcm90ZWN0aW9uIChpbnRlZ3JpdHkNCmFu
ZCBjb25maWRlbnRpYWxpdHkpIGJ5IG1lYW5zIG9mIGFuIEludGVyZmFjZSB0byBOZXR3b3JrIFNl
Y3VyaXR5IEZ1bmN0aW9uDQooSTJOU0YpIGNvbnRyb2xsZXIuICBJdCBjb25zaWRlcnMgdHdvIG1h
aW4gd2VsbC1rbm93biBzY2VuYXJpb3MgaW4gSVBzZWM6IChpKQ0KZ2F0ZXdheS10by1nYXRld2F5
IGFuZCAoaWkpIGhvc3QtdG8taG9zdC4gIFRoZSBzZXJ2aWNlIGRlc2NyaWJlZCBpbiB0aGlzDQpk
b2N1bWVudCBhbGxvd3MgdGhlIGNvbmZpZ3VyYXRpb24gYW5kIG1vbml0b3Jpbmcgb2YgSVBzZWMg
U2VjdXJpdHkgQXNzb2NpYXRpb25zDQooU0FzKSBmcm9tIGEgSTJOU0YgQ29udHJvbGxlciB0byBv
bmUgb3Igc2V2ZXJhbCBmbG93LWJhc2VkIE5ldHdvcmsgU2VjdXJpdHkNCkZ1bmN0aW9ucyAoTlNG
cykgdGhhdCByZWx5IG9uIElQc2VjIHRvIHByb3RlY3QgZGF0YSB0cmFmZmljLg0KDQpUaGUgZG9j
dW1lbnQgZm9jdXNlcyBvbiB0aGUgSTJOU0YgTlNGLWZhY2luZyBpbnRlcmZhY2UgYnkgcHJvdmlk
aW5nIFlBTkcgZGF0YQ0KbW9kZWxzIGZvciBjb25maWd1cmluZyB0aGUgSVBzZWMgZGF0YWJhc2Vz
IChTUEQsIFNBRCwgUEFEKSBhbmQgSUtFdjIuIFRoaXMNCmFsbG93cyBJUHNlYyBTQSBlc3RhYmxp
c2htZW50IHdpdGggbWluaW1hbCBpbnRlcnZlbnRpb24gYnkgdGhlIG5ldHdvcmsNCmFkbWluaXN0
cmF0b3IuDQoNCi0gVGhlIFNETiBjb250cm9sbGVyIG1hbmFnZXMgYW5kIGNvbmZpZ3VyZXMgdGhl
IGRpc3RyaWJ1dGVkIG5ldHdvcmsgcmVzb3VyY2VzDQphbmQgcHJvdmlkZXMgYW4gYWJzdHJhY3Rl
ZCB2aWV3IG9mIHRoZSBuZXR3b3JrIHJlc291cmNlcyB0byB0aGUgU0RODQphcHBsaWNhdGlvbnMu
IC0+IEluY29ycmVjdCB1c2FnZSBvZiAidGhlIiBpbiBzZXZlcmFsIHBsYWNlcy4gQ29uc2lkZXIg
Y2hhbmdpbmcNCnRvOiAiU0ROIGNvbnRyb2xsZXJzIGNvbmZpZ3VyZSBhbmQgbWFuYWdlIGRpc3Ry
aWJ1dGVkIG5ldHdvcmsgcmVzb3VyY2VzIGFuZA0KcHJvdmlkZSBhbiBhYnN0cmFjdGVkIHZpZXcg
b2YgdGhlIG5ldHdvcmsgcmVzb3VyY2VzIHRvIFNETiBhcHBsaWNhdGlvbnMiDQoNCi0gVGhlIFNE
TiBhcHBsaWNhdGlvbiBjYW4gY3VzdG9taXplIGFuZCBhdXRvbWF0ZSB0aGUgb3BlcmF0aW9ucyAo
aW5jbHVkaW5nDQptYW5hZ2VtZW50KSBvZiB0aGUgYWJzdHJhY3RlZCBuZXR3b3JrIHJlc291cmNl
cyBpbiBhIHByb2dyYW1tYWJsZSBtYW5uZXIgdmlhDQp0aGlzIGludGVyZmFjZSBbUkZDNzE0OV0g
W0lUVS1ULlkuMzMwMF0gW09ORi1TRE4tQXJjaGl0ZWN0dXJlXSBbT05GLU9wZW5GbG93XS4NCi0+
IFJlbW92ZSBhcnRpY2xlIGZyb20gdGhlIGJlZ2lubmluZyBvZiB0aGUgc2VudGVuY2UgIlNETiBh
cHBsaWNhdGlvbnMgY2FuDQpjdXN0b21pemUgYW5kIGF1dG9tYXRlIHRoZSBvcGVyYXRpb25zIChp
bmNsdWRpbmcgbWFuYWdlbWVudCkgb2YgdGhlIGFic3RyYWN0ZWQNCm5ldHdvcmsgcmVzb3VyY2Vz
IGluIGEgcHJvZ3JhbW1hYmxlIG1hbm5lciB2aWEgdGhpcyBpbnRlcmZhY2UgW1JGQzcxNDldDQpb
SVRVLVQuWS4zMzAwXSBbT05GLVNETi1BcmNoaXRlY3R1cmVdIFtPTkYtT3BlbkZsb3ddLiINCg0K
LSBTZXZlcmFsIHNlbnRlbmNlcyBhcmUgd2F5IHRvbyBsb25nLiBIZXJlIGlzIGFuIGVkaXRlZCB2
ZXJzaW9uIG9mIHRoZSAybmQNCnBhcmFncmFwaCB0aGF0IHlvdSBjb3VsZCBjb25zaWRlcjogU2V2
ZXJhbCBuZXR3b3JrIHNjZW5hcmlvcyBub3cgZGVtYW5kIGENCmNlbnRyYWxpemVkIHdheSBvZiBt
YW5hZ2luZyBkaWZmZXJlbnQgc2VjdXJpdHkgYXNwZWN0cy4gIEZvciBleGFtcGxlLA0KU29mdHdh
cmUtRGVmaW5lZCBXQU5zIChTRC1XQU5zKS4gU0QtV0FOcyBhcmUgYW4gU0ROIGV4dGVuc2lvbiBw
cm92aWRpbmcgYQ0Kc29mdHdhcmUgYWJzdHJhY3Rpb24gdG8gY3JlYXRlIHNlY3VyZSBuZXR3b3Jr
IG92ZXJsYXlzIG92ZXIgdHJhZGl0aW9uYWwgV0FOIGFuZA0KYnJhbmNoIG5ldHdvcmtzLiAgU0Qt
V0FOcyB1dGlsaXplIElQc2VjIFtSRkM0MzAxXSBhcyBhbiB1bmRlcmx5aW5nIHNlY3VyaXR5DQpw
cm90b2NvbC4gVGhlIGdvYWwgb2YgU0QtV0FOcyBpcyB0byBwcm92aWRlIGZsZXhpYmxlIGFuZCBh
dXRvbWF0ZWQgZGVwbG95bWVudA0KZnJvbSBhIGNlbnRyYWxpemVkIHBvaW50IHRvIGVuYWJsZSBv
bi1kZW1hbmQgbmV0d29yayBzZWN1cml0eSBzZXJ2aWNlcyBzdWNoIGFzDQpJUHNlYyBTZWN1cml0
eSBBc3NvY2lhdGlvbiAoSVBzZWMgU0EpIG1hbmFnZW1lbnQuDQoNCkFkZGl0aW9uYWxseSwgU2Vj
dGlvbiA0LjMuMyBpbiBbUkZDODE5Ml0gZGVzY3JpYmVzIGFub3RoZXIgZXhhbXBsZSB1c2UgY2Fz
ZSBmb3INCkNsb3VkIERhdGEgQ2VudGVyIFNjZW5hcmlvIHRpdGxlZCAiQ2xpZW50LVNwZWNpZmlj
IFNlY3VyaXR5IFBvbGljeSBpbiBDbG91ZA0KVlBOcyIuIFRoZSB1c2UgY2FzZSBpbiBSRkMgODE5
MiBzdGF0ZXMgdGhhdCAiZHluYW1pYyBrZXkgbWFuYWdlbWVudCBpcyBjcml0aWNhbA0KZm9yIHNl
Y3VyaW5nIHRoZSBWUE4gYW5kIHRoZSBkaXN0cmlidXRpb24gb2YgcG9saWNpZXMiLiAgVGhlc2Ug
VlBOcyBjYW4gYmUNCmVzdGFibGlzaGVkIHVzaW5nIElQc2VjLiAgVGhlIG1hbmFnZW1lbnQgb2Yg
SVBzZWMgU0FzIGluIGRhdGEgY2VudGVycyB1c2luZyBhDQpjZW50cmFsaXplZCBlbnRpdHkgaXMg
YSBzY2VuYXJpbyB3aGVyZSB0aGUgY3VycmVudCBzcGVjaWZpY2F0aW9uIG1heWJlDQphcHBsaWNh
YmxlLg0KDQotIFRoaXMgdGV4dCBpcyByZXBlYXRlZCB0d2ljZTogIkluIHRoZSBJS0UgY2FzZSwg
SUtFdjIgYWxyZWFkeSBwcm92aWRlcyBhDQptZWNoYW5pc20gdG8gZGV0ZWN0IHdoZXRoZXIgLi4u
Ig0KDQotICJ2aWV3IGlzIGJ1aWx0IGVpdGhlciByZXF1ZXN0aW5nIGluZm9ybWF0aW9uIHRvIHRo
ZSBOU0ZzIHVuZGVyIGl0cyBjb250cm9sLA0Kb3IgYmVjYXVzZSB0aGVzZSBOU0ZzIGluZm9ybSB0
aGUgSTJOU0YgQ29udHJvbGxlci4iIC0+ICJ2aWV3IGlzIGJ1aWx0IGVpdGhlciBieQ0KcmVxdWVz
dGluZyBpbmZvcm1hdGlvbiBmcm9tIHRoZSBOU0ZzIHVuZGVyIGl0cyBjb250cm9sLCBvciBieSBp
bmZvcm1hdGlvbg0KcHVzaGVkIGZyb20gdGhlIE5TRnMgdG8gdGhlIEkyTlNGIENvbnRyb2xsZXIi
DQoNCi0gIkNvbWJpbmVkIGFsZ29yaXRobXMgaGFzIGJlZW4gcmVtb3ZlZCIgLT4gaGF2ZSBiZWVu
DQoNCi0gImFkbWl0IHRoZSBjb25maWd1cmF0aW9ucyBvZiB0aGVzZSB2YWx1ZXMuIiAtPiAiYWNj
ZXB0IGNvbmZpZ3VyYXRpb24gb2YgdGhlc2UNCnZhbHVlcyINCg0KLSAiQmVzaWRlLCBJYWFTIHNl
cnZpY2VzIHByb3ZpZGluZyB2aXJ0dWFsaXphdGlvbiBlbnZpcm9ubWVudHMgYXJlIGRlcGxveW1l
bnRzDQpzb2x1dGlvbnMgYmFzZWQgb24gSVBzZWMgdG8gcHJvdmlkZSIgLT4gIkJlc2lkZXMsIElh
YVMgc2VydmljZXMgcHJvdmlkaW5nDQp2aXJ0dWFsaXphdGlvbiBlbnZpcm9ubWVudHMgYXJlIGRl
cGxveW1lbnRzIHRoYXQgb2Z0ZW4gcmVseSBvbiBJUHNlYyB0byBwcm92aWRlIg0KDQotICJEZXNw
aXRlIHRoaXMgcHJvY2VkdXJlIG1heSBpbmNyZWFzZSB0aGUgbGF0ZW5jeSB0byBjb21wbGV0ZSB0
aGUgcHJvY2Vzcywgbm8NCnRyYWZmaWMgaXMgc2VudCBvdmVyIHRoZSBuZXR3b3JrIHVudGlsIHRo
ZSBJUHNlYyBTQXMgYXJlIGNvbXBsZXRlbHkgb3BlcmF0aXZlLiINCi0+ICJFdmVuIHRob3VnaCB0
aGlzIHByb2NlZHVyZSBtYXkgaW5jcmVhc2UiDQoNCi0gIklmIHNvbWUgb2YgdGhlIG9wZXJhdGlv
bnMgZGVzY3JpYmVkIGFib3ZlIGZhaWxzIiAtPiAiSWYgc29tZSBvZiB0aGUNCm9wZXJhdGlvbnMg
ZGVzY3JpYmVkIGFib3ZlIGZhaWwiDQoNCi0gIkluIHN1Y2ggYXMgcmVhY3RpdmUgbW9kZSwgdXBv
biByZWNlcHRpb24gb2YgdGhlIHNhZGItYWNxdWlyZSBub3RpZmljYXRpb24sDQp0aGUgSTJOU0Yg
Q29udHJvbGxlciBpbnN0YWxscyB0aGUgbmV3IElQc2VjIFNBcyBpbiBOU0YgQSBhbmQgQiAoZm9s
bG93aW5nIiAtPiAiIg0KDQotICJJZiB0aGlzIGlzIG5vdCBjcml0aWMgdGhlbiBpdCBpcyBhbiIg
LT4gdGhpcyBpcyBub3QgY3JpdGljYWwNCg0KDQpfX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fXw0KSTJuc2YgbWFpbGluZyBsaXN0DQpJMm5zZkBpZXRmLm9yZzxt
YWlsdG86STJuc2ZAaWV0Zi5vcmc+DQpodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3Rp
bmZvL2kybnNmDQoNCi0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0NClJhZmEgTWFyaW4tTG9wZXosIFBoRA0KRGVwdC4gSW5mb3JtYXRpb24gYW5k
IENvbW11bmljYXRpb25zIEVuZ2luZWVyaW5nIChESUlDKQ0KRmFjdWx0eSBvZiBDb21wdXRlciBT
Y2llbmNlLVVuaXZlcnNpdHkgb2YgTXVyY2lhDQozMDEwMCBNdXJjaWEgLSBTcGFpbg0KVGVsZjog
KzM0ODY4ODg4NTAxIEZheDogKzM0ODY4ODg0MTUxIGUtbWFpbDogcmFmYUB1bS5lczxtYWlsdG86
cmFmYUB1bS5lcz4NCi0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0NCg0KDQoNCg0KDQoNCg==

--_000_486e2620192ae0c721c1480cc1d5f69aericssoncom_
Content-Type: text/html; charset="utf-8"
Content-ID: <386A518F6E34834F8A291BFD9FE2AB73@eurprd07.prod.outlook.com>
Content-Transfer-Encoding: base64

PGh0bWw+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIgY29udGVudD0i
dGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjwvaGVhZD4NCjxib2R5Pg0KPHA+SGkgUmFmYSw8
L3A+DQo8cD5UaGFua3MgZm9yIGFkZHJlc3NpbmcgbXkgY29tbWVudHMuIFlvdXIgY2hhbmdlcyBh
bmQgdXBkYXRlcyBsb29rIGdvb2QuIDxicj4NCjwvcD4NCjxwPi0tTW9oaXQ8L3A+DQo8ZGl2IGNs
YXNzPSJtb3otY2l0ZS1wcmVmaXgiPk9uIDkvMjIvMjAgOTo0MSBBTSwgUmFmYSBNYXJpbi1Mb3Bl
eiB3cm90ZTo8YnI+DQo8L2Rpdj4NCjxibG9ja3F1b3RlIHR5cGU9ImNpdGUiIGNpdGU9Im1pZDpG
OTQ0RDg5QS1CRUQzLTRENkYtOUEzMi0xOEU3OEUzMEVDQ0RAdW0uZXMiPg0KPGRpdiBkaXI9ImF1
dG8iIHN0eWxlPSJ3b3JkLXdyYXA6IGJyZWFrLXdvcmQ7IC13ZWJraXQtbmJzcC1tb2RlOg0KICAg
ICAgICBzcGFjZTsgbGluZS1icmVhazogYWZ0ZXItd2hpdGUtc3BhY2U7IiBjbGFzcz0iIj4NCjxk
aXYgZGlyPSJhdXRvIiBzdHlsZT0id29yZC13cmFwOiBicmVhay13b3JkOyAtd2Via2l0LW5ic3At
bW9kZToNCiAgICAgICAgICBzcGFjZTsgbGluZS1icmVhazogYWZ0ZXItd2hpdGUtc3BhY2U7IiBj
bGFzcz0iIj4NCkRlYXIgTW9oaXQ6DQo8ZGl2IGNsYXNzPSIiPjxiciBjbGFzcz0iIj4NCjwvZGl2
Pg0KPGRpdiBjbGFzcz0iIj5UaGFuayB5b3UgdmVyeSBtdWNoIGZvciB5b3VyIHJldmlldy4gV2Ug
cmVhbGx5IGFwcHJlY2lhdGUgaXQuIFBsZWFzZSBzZWUgb3VyIGNvbW1lbnRzIGlubGluZTo8YnIg
Y2xhc3M9IiI+DQo8ZGl2PjxiciBjbGFzcz0iIj4NCjxibG9ja3F1b3RlIHR5cGU9ImNpdGUiIGNs
YXNzPSIiPg0KPGRpdiBjbGFzcz0iIj5FbCAzMSBhZ28gMjAyMCwgYSBsYXMgMTM6MjgsIE1vaGl0
IFNldGhpIHZpYSBEYXRhdHJhY2tlciAmbHQ7PGEgaHJlZj0ibWFpbHRvOm5vcmVwbHlAaWV0Zi5v
cmciIGNsYXNzPSIiIG1vei1kby1ub3Qtc2VuZD0idHJ1ZSI+bm9yZXBseUBpZXRmLm9yZzwvYT4m
Z3Q7IGVzY3JpYmnDszo8L2Rpdj4NCjxiciBjbGFzcz0iQXBwbGUtaW50ZXJjaGFuZ2UtbmV3bGlu
ZSI+DQo8ZGl2IGNsYXNzPSIiPg0KPGRpdiBjbGFzcz0iIj5SZXZpZXdlcjogTW9oaXQgU2V0aGk8
YnIgY2xhc3M9IiI+DQpSZXZpZXcgcmVzdWx0OiBPbiB0aGUgUmlnaHQgVHJhY2s8YnIgY2xhc3M9
IiI+DQo8YnIgY2xhc3M9IiI+DQpJIGFtIHRoZSBhc3NpZ25lZCBHZW4tQVJUIHJldmlld2VyIGZv
ciB0aGlzIGRyYWZ0LiBUaGUgR2VuZXJhbCBBcmVhPGJyIGNsYXNzPSIiPg0KUmV2aWV3IFRlYW0g
KEdlbi1BUlQpIHJldmlld3MgYWxsIElFVEYgZG9jdW1lbnRzIGJlaW5nIHByb2Nlc3NlZDxiciBj
bGFzcz0iIj4NCmJ5IHRoZSBJRVNHIGZvciB0aGUgSUVURiBDaGFpci4gJm5ic3A7UGxlYXNlIHRy
ZWF0IHRoZXNlIGNvbW1lbnRzIGp1c3Q8YnIgY2xhc3M9IiI+DQpsaWtlIGFueSBvdGhlciBsYXN0
IGNhbGwgY29tbWVudHMuPGJyIGNsYXNzPSIiPg0KPGJyIGNsYXNzPSIiPg0KRm9yIG1vcmUgaW5m
b3JtYXRpb24sIHBsZWFzZSBzZWUgdGhlIEZBUSBhdDxiciBjbGFzcz0iIj4NCjxiciBjbGFzcz0i
Ij4NCiZsdDs8YSBocmVmPSJodHRwczovL3RyYWMuaWV0Zi5vcmcvdHJhYy9nZW4vd2lraS9HZW5B
cnRmYXEiIGNsYXNzPSIiIG1vei1kby1ub3Qtc2VuZD0idHJ1ZSI+aHR0cHM6Ly90cmFjLmlldGYu
b3JnL3RyYWMvZ2VuL3dpa2kvR2VuQXJ0ZmFxPC9hPiZndDsuPGJyIGNsYXNzPSIiPg0KPGJyIGNs
YXNzPSIiPg0KRG9jdW1lbnQ6IGRyYWZ0LWlldGYtaTJuc2Ytc2RuLWlwc2VjLWZsb3ctcHJvdGVj
dGlvbi0wODxiciBjbGFzcz0iIj4NClJldmlld2VyOiBNb2hpdCBTZXRoaTxiciBjbGFzcz0iIj4N
ClJldmlldyBEYXRlOiAyMDIwLTA4LTMxPGJyIGNsYXNzPSIiPg0KSUVURiBMQyBFbmQgRGF0ZTog
MjAyMC0wOS0wNDxiciBjbGFzcz0iIj4NCklFU0cgVGVsZWNoYXQgZGF0ZTogTm90IHNjaGVkdWxl
ZCBmb3IgYSB0ZWxlY2hhdDxiciBjbGFzcz0iIj4NCjxiciBjbGFzcz0iIj4NClN1bW1hcnk6IFRo
aXMgZG9jdW1lbnQgZGVzY3JpYmVzIGhvdyBJUHNlYyBTQXMgY2FuIGJlIHNldHVwIGZyb20gYSBj
ZW50cmFsaXplZDxiciBjbGFzcz0iIj4NCkkyTlNGIGNvbnRyb2xsZXIuIFRoZSBkb2N1bWVudCBp
cyAmcXVvdDtPbiB0aGUgUmlnaHQgVHJhY2smcXVvdDsuPGJyIGNsYXNzPSIiPg0KPGJyIGNsYXNz
PSIiPg0KTWFqb3IgaXNzdWVzOjxiciBjbGFzcz0iIj4NCi0gVGhlIGRvY3VtZW50IHNob3VsZCBo
aWdobGlnaHQgaW4gdGhlIGFic3RyYWN0IGFuZCBlbHNld2hlcmUgdGhhdCBpdCBkb2VzIG5vdDxi
ciBjbGFzcz0iIj4NCmRlZmluZSBhIHByb3RvY29sIGJldHdlZW4gdGhlIEkyTlNGIGNvbnRyb2xs
ZXIgYW5kIHRoZSBOU0YuIEl0IG9ubHkgc3BlY2lmaWVzPGJyIGNsYXNzPSIiPg0KdGhlIFlBTkcg
bW9kZWwuIFNldmVyYWwgYXBwZW5kaWNlcyByZWZlciB0byBub3RpZmljYXRpb24gbWVzc2FnZXMu
IFdoZXJlIGFyZTxiciBjbGFzcz0iIj4NCnRoZXkgZGVmaW5lZC9zcGVjaWZpZWQ/PGJyIGNsYXNz
PSIiPg0KPC9kaXY+DQo8L2Rpdj4NCjwvYmxvY2txdW90ZT4NCjxkaXY+PGJyIGNsYXNzPSIiPg0K
PC9kaXY+DQo8ZGl2PltBdXRob3JzXSBSZWdhcmRpbmcgdGhlIGFic3RyYWN0LCB3ZSBoYXZlIGFw
cGxpZWQgeW91ciBzdWdnZXN0aW9ucy4gV2UgY2FuIGFsc28gaW5jbHVkZSBhIGZldyB3b3JkcyB0
byBoaWdobGlnaHQgdGhlIGFzcGVjdCB5b3UgbWVudGlvbjogd2UgZG8gbm90IGRlZmluZSBhbnkg
bmV3IHByb3RvY29sIGJ1dCBhIFlBTkcgbW9kZWwuPC9kaXY+DQo8ZGl2PjxiciBjbGFzcz0iIj4N
CjwvZGl2Pg0KPGRpdj4NCjxibG9ja3F1b3RlIHR5cGU9ImNpdGUiIGNsYXNzPSIiPlRoaXMgZG9j
dW1lbnQgZGVzY3JpYmVzIGhvdyB0byBwcm92aWRlIElQc2VjLWJhc2VkIGZsb3cgcHJvdGVjdGlv
biAoaW50ZWdyaXR5PGJyIGNsYXNzPSIiPg0KYW5kIGNvbmZpZGVudGlhbGl0eSkgYnkgbWVhbnMg
b2YgYW4gSW50ZXJmYWNlIHRvIE5ldHdvcmsgU2VjdXJpdHkgRnVuY3Rpb248YnIgY2xhc3M9IiI+
DQooSTJOU0YpIGNvbnRyb2xsZXIuICZuYnNwO0l0IGNvbnNpZGVycyB0d28gbWFpbiB3ZWxsLWtu
b3duIHNjZW5hcmlvcyBpbiBJUHNlYzogKGkpPGJyIGNsYXNzPSIiPg0KZ2F0ZXdheS10by1nYXRl
d2F5IGFuZCAoaWkpIGhvc3QtdG8taG9zdC4gJm5ic3A7VGhlIHNlcnZpY2UgZGVzY3JpYmVkIGlu
IHRoaXM8YnIgY2xhc3M9IiI+DQpkb2N1bWVudCBhbGxvd3MgdGhlIGNvbmZpZ3VyYXRpb24gYW5k
IG1vbml0b3Jpbmcgb2YgSVBzZWMgU2VjdXJpdHkgQXNzb2NpYXRpb25zPGJyIGNsYXNzPSIiPg0K
KFNBcykgZnJvbSBhIEkyTlNGIENvbnRyb2xsZXIgdG8gb25lIG9yIHNldmVyYWwgZmxvdy1iYXNl
ZCBOZXR3b3JrIFNlY3VyaXR5PGJyIGNsYXNzPSIiPg0KRnVuY3Rpb25zIChOU0ZzKSB0aGF0IHJl
bHkgb24gSVBzZWMgdG8gcHJvdGVjdCBkYXRhIHRyYWZmaWMuPGJyIGNsYXNzPSIiPg0KPGJyIGNs
YXNzPSIiPg0KVGhlIGRvY3VtZW50IGZvY3VzZXMgb24gdGhlIEkyTlNGIE5TRi1mYWNpbmcgaW50
ZXJmYWNlIGJ5IHByb3ZpZGluZyBZQU5HIGRhdGE8YnIgY2xhc3M9IiI+DQptb2RlbHMgZm9yIGNv
bmZpZ3VyaW5nIHRoZSBJUHNlYyBkYXRhYmFzZXMgKFNQRCwgU0FELCBQQUQpIGFuZCBJS0V2Mi4g
VGhlcmVmb3JlLCBpdCBkb2VzIG5vdCZuYnNwOzxiIGNsYXNzPSIiPm5vdCBkZWZpbmUgYW55IG5l
dyBwcm90b2NvbDwvYj4uIFRoaXM8YnIgY2xhc3M9IiI+DQphbGxvd3MgSVBzZWMgU0EgZXN0YWJs
aXNobWVudCB3aXRoIG1pbmltYWwgaW50ZXJ2ZW50aW9uIGJ5IHRoZSBuZXR3b3JrPGJyIGNsYXNz
PSIiPg0KYWRtaW5pc3RyYXRvci48L2Jsb2NrcXVvdGU+DQo8L2Rpdj4NCjxkaXY+PGJyIGNsYXNz
PSIiPg0KPC9kaXY+DQo8ZGl2PjxiciBjbGFzcz0iIj4NCjwvZGl2Pg0KPGRpdj5XaXRoIHJlc3Bl
Y3QgdG8gbm90aWZpY2F0aW9ucywgdGhleSBhcmUgZGVmaW5lZCBpbiBORVRDT05GIGl0c2VsZiBi
dXQgd2UgaGFkIHRvIGRlZmluZSB0aHJvdWdoIHRoZSBZQU5HIG1vZGVsIHRoZSBpbmZvcm1hdGlv
biAobm90aWZpY2F0aW9uIGRhdGEpIHRoYXQgd2lsbCBiZSBzZW50OjwvZGl2Pg0KPGRpdj48YnIg
Y2xhc3M9IiI+DQo8L2Rpdj4NCjxkaXY+Rm9yIGV4YW1wbGU6PC9kaXY+DQo8ZGl2PjxiciBjbGFz
cz0iIj4NCjwvZGl2Pg0KPGRpdj4NCjxkaXYgY2xhc3M9IiI+Jm5ic3A7bm90aWZpY2F0aW9uczo8
L2Rpdj4NCjxkaXYgY2xhc3M9IiI+Jm5ic3A7ICZuYnNwOyAmbmJzcDsrLS0tbiBzYWRiLWFjcXVp
cmU8L2Rpdj4NCjxkaXYgY2xhc3M9IiI+Jm5ic3A7ICZuYnNwOyAmbmJzcDt8ICZuYnNwOystLXJv
IGlwc2VjLXBvbGljeS1uYW1lICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDtzdHJp
bmc8L2Rpdj4NCjxkaXYgY2xhc3M9IiI+Jm5ic3A7ICZuYnNwOyAmbmJzcDt8ICZuYnNwOystLXJv
IHRyYWZmaWMtc2VsZWN0b3I8L2Rpdj4NCjxkaXYgY2xhc3M9IiI+Jm5ic3A7ICZuYnNwOyAmbmJz
cDt8ICZuYnNwOyAmbmJzcDsgKy0tcm8gbG9jYWwtc3VibmV0ICZuYnNwOyAmbmJzcDsgJm5ic3A7
ICZuYnNwOyAmbmJzcDsgJm5ic3A7aW5ldDppcC1wcmVmaXg8L2Rpdj4NCjxkaXYgY2xhc3M9IiI+
Jm5ic3A7ICZuYnNwOyAmbmJzcDt8ICZuYnNwOyAmbmJzcDsgKy0tcm8gcmVtb3RlLXN1Ym5ldCAm
bmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7IGluZXQ6aXAtcHJlZml4PC9kaXY+DQo8
ZGl2IGNsYXNzPSIiPiZuYnNwOyAmbmJzcDsgJm5ic3A7fCAmbmJzcDsgJm5ic3A7ICstLXJvIGlu
bmVyLXByb3RvY29sPyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgaXBzZWMtaW5uZXItcHJv
dG9jb2w8L2Rpdj4NCjxkaXYgY2xhc3M9IiI+Jm5ic3A7ICZuYnNwOyAmbmJzcDt8ICZuYnNwOyAm
bmJzcDsgKy0tcm8gbG9jYWwtcG9ydHMqIFtzdGFydCBlbmRdPC9kaXY+DQo8ZGl2IGNsYXNzPSIi
PiZuYnNwOyAmbmJzcDsgJm5ic3A7fCAmbmJzcDsgJm5ic3A7IHwgJm5ic3A7Ky0tcm8gc3RhcnQg
Jm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwO2lu
ZXQ6cG9ydC1udW1iZXI8L2Rpdj4NCjxkaXYgY2xhc3M9IiI+Jm5ic3A7ICZuYnNwOyAmbmJzcDt8
ICZuYnNwOyAmbmJzcDsgfCAmbmJzcDsrLS1ybyBlbmQgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5i
c3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDtpbmV0OnBvcnQtbnVtYmVyPC9k
aXY+DQo8ZGl2IGNsYXNzPSIiPiZuYnNwOyAmbmJzcDsgJm5ic3A7fCAmbmJzcDsgJm5ic3A7ICst
LXJvIHJlbW90ZS1wb3J0cyogW3N0YXJ0IGVuZF08L2Rpdj4NCjxkaXYgY2xhc3M9IiI+Jm5ic3A7
ICZuYnNwOyAmbmJzcDt8ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOystLXJvIHN0YXJ0ICZu
YnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDtpbmV0
OnBvcnQtbnVtYmVyPC9kaXY+DQo8ZGl2IGNsYXNzPSIiPiZuYnNwOyAmbmJzcDsgJm5ic3A7fCAm
bmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsrLS1ybyBlbmQgJm5ic3A7ICZuYnNwOyAmbmJzcDsg
Jm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDtpbmV0OnBvcnQtbnVtYmVy
PC9kaXY+DQo8ZGl2IGNsYXNzPSIiPiZuYnNwOyAmbmJzcDsgJm5ic3A7Ky0tLW4gc2FkYi1leHBp
cmU8L2Rpdj4NCjxkaXYgY2xhc3M9IiI+Jm5ic3A7ICZuYnNwOyAmbmJzcDt8ICZuYnNwOystLXJv
IGlwc2VjLXNhLW5hbWUgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyBzdHJpbmc8
L2Rpdj4NCjxkaXYgY2xhc3M9IiI+Jm5ic3A7ICZuYnNwOyAmbmJzcDt8ICZuYnNwOystLXJvIHNv
ZnQtbGlmZXRpbWUtZXhwaXJlPyAmbmJzcDsgYm9vbGVhbjwvZGl2Pg0KPGRpdiBjbGFzcz0iIj4m
bmJzcDsgJm5ic3A7ICZuYnNwO3wgJm5ic3A7Ky0tcm8gbGlmZXRpbWUtY3VycmVudDwvZGl2Pg0K
PGRpdiBjbGFzcz0iIj4mbmJzcDsgJm5ic3A7ICZuYnNwO3wgJm5ic3A7ICZuYnNwOyArLS1ybyB0
aW1lPyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5i
c3A7dWludDMyPC9kaXY+DQo8ZGl2IGNsYXNzPSIiPiZuYnNwOyAmbmJzcDsgJm5ic3A7fCAmbmJz
cDsgJm5ic3A7ICstLXJvIGJ5dGVzPyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7
ICZuYnNwOyAmbmJzcDsgdWludDMyPC9kaXY+DQo8ZGl2IGNsYXNzPSIiPiZuYnNwOyAmbmJzcDsg
Jm5ic3A7fCAmbmJzcDsgJm5ic3A7ICstLXJvIHBhY2tldHM/ICZuYnNwOyAmbmJzcDsgJm5ic3A7
ICZuYnNwOyAmbmJzcDsgJm5ic3A7IHVpbnQzMjwvZGl2Pg0KPGRpdiBjbGFzcz0iIj4mbmJzcDsg
Jm5ic3A7ICZuYnNwO3wgJm5ic3A7ICZuYnNwOyArLS1ybyBpZGxlPyAmbmJzcDsgJm5ic3A7ICZu
YnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7dWludDMyPC9kaXY+DQo8ZGl2
IGNsYXNzPSIiPiZuYnNwOyAmbmJzcDsgJm5ic3A7Ky0tLW4gc2FkYi1zZXEtb3ZlcmZsb3c8L2Rp
dj4NCjxkaXYgY2xhc3M9IiI+Jm5ic3A7ICZuYnNwOyAmbmJzcDt8ICZuYnNwOystLXJvIGlwc2Vj
LXNhLW5hbWUgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyBzdHJpbmc8L2Rpdj4N
CjxkaXYgY2xhc3M9IiI+Jm5ic3A7ICZuYnNwOyAmbmJzcDsrLS0tbiBzYWRiLWJhZC1zcGk8L2Rp
dj4NCjxkaXYgY2xhc3M9IiI+Jm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICstLXJvIHNwaSAm
bmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZu
YnNwOyAmbmJzcDsgdWludDMyPC9kaXY+DQo8YnIgY2xhc3M9IkFwcGxlLWludGVyY2hhbmdlLW5l
d2xpbmUiPg0KVGhlcmVmb3JlJm5ic3A7V2UgZGVmaW5lIFlBTkcgbm90aWZpY2F0aW9ucyBmb3Ig
dGhlIGlrZWxlc3MgY2FzZSBtYWtpbmcgdXNlIG9mIHRoZSBub3RpZmljYXRpb24gbWVzc2FnZSBk
ZWZpbmVkIGJ5IE5FVENPTkYuPC9kaXY+DQo8YnIgY2xhc3M9IiI+DQo8YmxvY2txdW90ZSB0eXBl
PSJjaXRlIiBjbGFzcz0iIj4NCjxkaXYgY2xhc3M9IiI+DQo8ZGl2IGNsYXNzPSIiPjxiciBjbGFz
cz0iIj4NCi0gRm9yIHRoZSBJS0UgY2FzZSwgYSBsb3Qgd291bGQgZGVwZW5kIG9uIHRoZSBjcnlw
dG9ncmFwaGljIHN1aXRlcyBpbXBsZW1lbnRlZDxiciBjbGFzcz0iIj4NCmluIHRoZSBOU0YuIEZv
ciBleGFtcGxlLCB3aGF0IGlmIHRoZSBJMk5TRiBpc3N1ZXMgY2VydGlmaWNhdGVzIGZvciBjdXJ2
ZXMgbm90PGJyIGNsYXNzPSIiPg0KaW1wbGVtZW50ZWQuIFRoZSBkb2N1bWVudCBzaG91bGQgbWF5
YmUgbWVudGlvbiB0aGF0IHRoZSBJMk5TRiBpcyBhd2FyZSBvZiB0aGU8YnIgY2xhc3M9IiI+DQpO
U0YgYW5kIGl0cyBJS0V2MiBpbXBsZW1lbnRhdGlvbi92ZXJzaW9uIGRldGFpbHMgYmFzZWQgb24g
d2hpY2ggaXQgaXNzdWVzIHRoZTxiciBjbGFzcz0iIj4NCmNyZWRlbnRpYWxzLiBUaGlzIHJlbGF0
ZXMgdG8gdGhlIHRleHQ6ICZxdW90O2FuZCBhcHBseWluZyBvdGhlciBJS0V2MiBjb25maWd1cmF0
aW9uPGJyIGNsYXNzPSIiPg0KcGFyYW1ldGVycyAoZS5nLiAmbmJzcDtjcnlwdG9ncmFwaGljIGFs
Z29yaXRobXMgZm9yIGVzdGFibGlzaGluZyBhbiBJS0V2MiBTQSkmcXVvdDsuIFlvdTxiciBjbGFz
cz0iIj4NCmNhbid0IGNvbmZpZ3VyZSB3aGF0IGlzIG5vdCBpbXBsZW1lbnRlZD88YnIgY2xhc3M9
IiI+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9ibG9ja3F1b3RlPg0KPGRpdj48YnIgY2xhc3M9IiI+DQo8
L2Rpdj4NCjxkaXY+V2UgdGhpbmsgdGhpcyBpcyBkaXNjdXNzZWQgaW4gU2VjdGlvbiA1LjQgTlNG
IHJlZ2lzdHJhdGlvbiBhbmQgZGlzY292ZXJ5LiBXZSBhY2tub3dsZWRnZWQgdGhhdCBJMk5TRiBt
dXN0IGRpc2NvdmVyIE5TRiBmZWF0dXJlcy4gSG93ZXZlciB0aGlzIGlzIGEgcHJldmlvdXMgc3Rl
cCB0byB3aGF0IHdlIGRlZmluZSBpbiB0aGlzIEktRC4gT25jZSB0aGUgTlNGIGlzIG9wZXJhdGl2
ZSBhbmQgSTJOU0YgY29udHJvbGxlciBoYXMga25vd2xlZGdlDQogb2YgdGhlIE5TRiBhbmQgdGhl
aXIgZmVhdHVyZXMsIHRoZSBJMk5TRiBjb250cm9sbGVyIGNhbiBjb25maWd1cmUgcHJvcGVybHku
PC9kaXY+DQo8ZGl2PjxiciBjbGFzcz0iIj4NCjwvZGl2Pg0KPGRpdj5TaG91bGQgd2UgZXh0ZW5k
IHRoZSBzZWN0aW9uIDUuNCBzb21laG93PyBBbnkgc3VnZ2VzdGlvbj88L2Rpdj4NCjxkaXY+PGJy
IGNsYXNzPSIiPg0KPC9kaXY+DQo8YnIgY2xhc3M9IiI+DQo8YmxvY2txdW90ZSB0eXBlPSJjaXRl
IiBjbGFzcz0iIj4NCjxkaXYgY2xhc3M9IiI+DQo8ZGl2IGNsYXNzPSIiPjxiciBjbGFzcz0iIj4N
Ci0gRG9lcyB0aGUgc3BlY2lmaWNhdGlvbiBhbGxvdyBOU0YncyB0byBkZXJpdmUgbWFueSBDSElM
RCBTQXM/PGJyIGNsYXNzPSIiPg0KPC9kaXY+DQo8L2Rpdj4NCjwvYmxvY2txdW90ZT4NCjxkaXY+
PGJyIGNsYXNzPSIiPg0KPC9kaXY+DQpJZiB5b3UgYXJlIHJlZmVycmluZyB0byBJS0UgY2FzZSwg
dGhlIElLRSBpbXBsZW1lbnRhdGlvbiBpbiB0aGUgTlNGIG1heSBkZXJpdmUgc2V2ZXJhbCBjaGls
ZCBTQXMgYmFzZWQgb24gYSBwYXJ0aWN1bGFyIHBvbGljeS4gSG93ZXZlciwgdW5kZXIgSTJOU0Yg
Y29udHJvbGxlciBzdGFuZHBvaW50LjwvZGl2Pg0KPGRpdj48YnIgY2xhc3M9IiI+DQo8L2Rpdj4N
CjxkaXY+SW4gdGhlIElLRS1sZXNzIGNhc2UsIHRoZSBJMk5TRiBjb250cm9sbGVyIGNhbiBhcHBs
eSBtdWx0aXBsZSBJUHNlYyBTQXMgaW4gdGhlIE5TRi48L2Rpdj4NCjxkaXY+PGJyIGNsYXNzPSIi
Pg0KPC9kaXY+DQo8ZGl2PkJleW9uZCB0aGVzZSBjb21tZW50cyBhbGwgdGhlIG1pbm9yIGlzc3Vl
cyBiZWxvdyBoYXMgYmVlbiBhbHJlYWR5IGZpeGVkIGluIHRoZSB2MDkgd2UgYXJlIHByZXBhcmlu
Zy4mbmJzcDs8L2Rpdj4NCjxkaXY+PGJyIGNsYXNzPSIiPg0KPC9kaXY+DQo8ZGl2PkJlc3QgcmVn
YXJkcyBhbmQgdGhhbmsgeW91IHNvIG11Y2ggYWdhaW4hPC9kaXY+DQo8ZGl2PjxiciBjbGFzcz0i
Ij4NCjwvZGl2Pg0KPGRpdj48YnIgY2xhc3M9IiI+DQo8YmxvY2txdW90ZSB0eXBlPSJjaXRlIiBj
bGFzcz0iIj4NCjxkaXYgY2xhc3M9IiI+DQo8ZGl2IGNsYXNzPSIiPjxiciBjbGFzcz0iIj4NCk1p
bm9yIGlzc3Vlczo8YnIgY2xhc3M9IiI+DQotIFRoZSBkb2N1bWVudCBoYXMgc2V2ZXJhbCBncmFt
bWF0aWNhbCBlcnJvcnMuIEkgaGF2ZSBmaXhlZCBtYW55IG9mIHRoZW0gaW4gbXk8YnIgY2xhc3M9
IiI+DQpyZXZpZXcgYmVsb3cgYnV0IHN1cmVseSBub3QgYWxsLiBJIGhvcGUgdGhhdCBjaGFpcnMv
QURzIGNvdWxkIGRvIGFub3RoZXIgcGFzczxiciBjbGFzcz0iIj4NCmJlZm9yZSBzZW5kaW5nIHRo
aXMgdG8gdGhlIFJGQyBlZGl0b3IuPGJyIGNsYXNzPSIiPg0KPGJyIGNsYXNzPSIiPg0KTml0cy9l
ZGl0b3JpYWwgY29tbWVudHM6PGJyIGNsYXNzPSIiPg0KLSBUaGUgZG9jdW1lbnQgdXNlcyB0ZXJt
cyBzdWNoIGFzIE5TRiBzaGlwcy9pbXBsZW1lbnRzIElLRXYyLiBVc2UgY29uc2lzdGVudDxiciBj
bGFzcz0iIj4NCnRlcm1pbm9sb2d5LjxiciBjbGFzcz0iIj4NCjxiciBjbGFzcz0iIj4NCi0gQWJz
dHJhY3Q6IFRoZXJlIHdlcmUgdG9vIG1hbnkgaXNzdWVzIHdpdGggdGhlIGFic3RyYWN0IHRvIGlu
ZGl2aWR1YWxseSBwb2ludDxiciBjbGFzcz0iIj4NCm91dC4gSGVyZSBpcyBhbiBlZGl0ZWQgdmVy
c2lvbiBmb3IgeW91IHRvIGNvbnNpZGVyOjxiciBjbGFzcz0iIj4NCjxiciBjbGFzcz0iIj4NClRo
aXMgZG9jdW1lbnQgZGVzY3JpYmVzIGhvdyB0byBwcm92aWRlIElQc2VjLWJhc2VkIGZsb3cgcHJv
dGVjdGlvbiAoaW50ZWdyaXR5PGJyIGNsYXNzPSIiPg0KYW5kIGNvbmZpZGVudGlhbGl0eSkgYnkg
bWVhbnMgb2YgYW4gSW50ZXJmYWNlIHRvIE5ldHdvcmsgU2VjdXJpdHkgRnVuY3Rpb248YnIgY2xh
c3M9IiI+DQooSTJOU0YpIGNvbnRyb2xsZXIuICZuYnNwO0l0IGNvbnNpZGVycyB0d28gbWFpbiB3
ZWxsLWtub3duIHNjZW5hcmlvcyBpbiBJUHNlYzogKGkpPGJyIGNsYXNzPSIiPg0KZ2F0ZXdheS10
by1nYXRld2F5IGFuZCAoaWkpIGhvc3QtdG8taG9zdC4gJm5ic3A7VGhlIHNlcnZpY2UgZGVzY3Jp
YmVkIGluIHRoaXM8YnIgY2xhc3M9IiI+DQpkb2N1bWVudCBhbGxvd3MgdGhlIGNvbmZpZ3VyYXRp
b24gYW5kIG1vbml0b3Jpbmcgb2YgSVBzZWMgU2VjdXJpdHkgQXNzb2NpYXRpb25zPGJyIGNsYXNz
PSIiPg0KKFNBcykgZnJvbSBhIEkyTlNGIENvbnRyb2xsZXIgdG8gb25lIG9yIHNldmVyYWwgZmxv
dy1iYXNlZCBOZXR3b3JrIFNlY3VyaXR5PGJyIGNsYXNzPSIiPg0KRnVuY3Rpb25zIChOU0ZzKSB0
aGF0IHJlbHkgb24gSVBzZWMgdG8gcHJvdGVjdCBkYXRhIHRyYWZmaWMuPGJyIGNsYXNzPSIiPg0K
PGJyIGNsYXNzPSIiPg0KVGhlIGRvY3VtZW50IGZvY3VzZXMgb24gdGhlIEkyTlNGIE5TRi1mYWNp
bmcgaW50ZXJmYWNlIGJ5IHByb3ZpZGluZyBZQU5HIGRhdGE8YnIgY2xhc3M9IiI+DQptb2RlbHMg
Zm9yIGNvbmZpZ3VyaW5nIHRoZSBJUHNlYyBkYXRhYmFzZXMgKFNQRCwgU0FELCBQQUQpIGFuZCBJ
S0V2Mi4gVGhpczxiciBjbGFzcz0iIj4NCmFsbG93cyBJUHNlYyBTQSBlc3RhYmxpc2htZW50IHdp
dGggbWluaW1hbCBpbnRlcnZlbnRpb24gYnkgdGhlIG5ldHdvcms8YnIgY2xhc3M9IiI+DQphZG1p
bmlzdHJhdG9yLjxiciBjbGFzcz0iIj4NCjxiciBjbGFzcz0iIj4NCi0gVGhlIFNETiBjb250cm9s
bGVyIG1hbmFnZXMgYW5kIGNvbmZpZ3VyZXMgdGhlIGRpc3RyaWJ1dGVkIG5ldHdvcmsgcmVzb3Vy
Y2VzPGJyIGNsYXNzPSIiPg0KYW5kIHByb3ZpZGVzIGFuIGFic3RyYWN0ZWQgdmlldyBvZiB0aGUg
bmV0d29yayByZXNvdXJjZXMgdG8gdGhlIFNETjxiciBjbGFzcz0iIj4NCmFwcGxpY2F0aW9ucy4g
LSZndDsgSW5jb3JyZWN0IHVzYWdlIG9mICZxdW90O3RoZSZxdW90OyBpbiBzZXZlcmFsIHBsYWNl
cy4gQ29uc2lkZXIgY2hhbmdpbmc8YnIgY2xhc3M9IiI+DQp0bzogJnF1b3Q7U0ROIGNvbnRyb2xs
ZXJzIGNvbmZpZ3VyZSBhbmQgbWFuYWdlIGRpc3RyaWJ1dGVkIG5ldHdvcmsgcmVzb3VyY2VzIGFu
ZDxiciBjbGFzcz0iIj4NCnByb3ZpZGUgYW4gYWJzdHJhY3RlZCB2aWV3IG9mIHRoZSBuZXR3b3Jr
IHJlc291cmNlcyB0byBTRE4gYXBwbGljYXRpb25zJnF1b3Q7PGJyIGNsYXNzPSIiPg0KPGJyIGNs
YXNzPSIiPg0KLSBUaGUgU0ROIGFwcGxpY2F0aW9uIGNhbiBjdXN0b21pemUgYW5kIGF1dG9tYXRl
IHRoZSBvcGVyYXRpb25zIChpbmNsdWRpbmc8YnIgY2xhc3M9IiI+DQptYW5hZ2VtZW50KSBvZiB0
aGUgYWJzdHJhY3RlZCBuZXR3b3JrIHJlc291cmNlcyBpbiBhIHByb2dyYW1tYWJsZSBtYW5uZXIg
dmlhPGJyIGNsYXNzPSIiPg0KdGhpcyBpbnRlcmZhY2UgW1JGQzcxNDldIFtJVFUtVC5ZLjMzMDBd
IFtPTkYtU0ROLUFyY2hpdGVjdHVyZV0gW09ORi1PcGVuRmxvd10uPGJyIGNsYXNzPSIiPg0KLSZn
dDsgUmVtb3ZlIGFydGljbGUgZnJvbSB0aGUgYmVnaW5uaW5nIG9mIHRoZSBzZW50ZW5jZSAmcXVv
dDtTRE4gYXBwbGljYXRpb25zIGNhbjxiciBjbGFzcz0iIj4NCmN1c3RvbWl6ZSBhbmQgYXV0b21h
dGUgdGhlIG9wZXJhdGlvbnMgKGluY2x1ZGluZyBtYW5hZ2VtZW50KSBvZiB0aGUgYWJzdHJhY3Rl
ZDxiciBjbGFzcz0iIj4NCm5ldHdvcmsgcmVzb3VyY2VzIGluIGEgcHJvZ3JhbW1hYmxlIG1hbm5l
ciB2aWEgdGhpcyBpbnRlcmZhY2UgW1JGQzcxNDldPGJyIGNsYXNzPSIiPg0KW0lUVS1ULlkuMzMw
MF0gW09ORi1TRE4tQXJjaGl0ZWN0dXJlXSBbT05GLU9wZW5GbG93XS4mcXVvdDs8YnIgY2xhc3M9
IiI+DQo8YnIgY2xhc3M9IiI+DQotIFNldmVyYWwgc2VudGVuY2VzIGFyZSB3YXkgdG9vIGxvbmcu
IEhlcmUgaXMgYW4gZWRpdGVkIHZlcnNpb24gb2YgdGhlIDJuZDxiciBjbGFzcz0iIj4NCnBhcmFn
cmFwaCB0aGF0IHlvdSBjb3VsZCBjb25zaWRlcjogU2V2ZXJhbCBuZXR3b3JrIHNjZW5hcmlvcyBu
b3cgZGVtYW5kIGE8YnIgY2xhc3M9IiI+DQpjZW50cmFsaXplZCB3YXkgb2YgbWFuYWdpbmcgZGlm
ZmVyZW50IHNlY3VyaXR5IGFzcGVjdHMuICZuYnNwO0ZvciBleGFtcGxlLDxiciBjbGFzcz0iIj4N
ClNvZnR3YXJlLURlZmluZWQgV0FOcyAoU0QtV0FOcykuIFNELVdBTnMgYXJlIGFuIFNETiBleHRl
bnNpb24gcHJvdmlkaW5nIGE8YnIgY2xhc3M9IiI+DQpzb2Z0d2FyZSBhYnN0cmFjdGlvbiB0byBj
cmVhdGUgc2VjdXJlIG5ldHdvcmsgb3ZlcmxheXMgb3ZlciB0cmFkaXRpb25hbCBXQU4gYW5kPGJy
IGNsYXNzPSIiPg0KYnJhbmNoIG5ldHdvcmtzLiAmbmJzcDtTRC1XQU5zIHV0aWxpemUgSVBzZWMg
W1JGQzQzMDFdIGFzIGFuIHVuZGVybHlpbmcgc2VjdXJpdHk8YnIgY2xhc3M9IiI+DQpwcm90b2Nv
bC4gVGhlIGdvYWwgb2YgU0QtV0FOcyBpcyB0byBwcm92aWRlIGZsZXhpYmxlIGFuZCBhdXRvbWF0
ZWQgZGVwbG95bWVudDxiciBjbGFzcz0iIj4NCmZyb20gYSBjZW50cmFsaXplZCBwb2ludCB0byBl
bmFibGUgb24tZGVtYW5kIG5ldHdvcmsgc2VjdXJpdHkgc2VydmljZXMgc3VjaCBhczxiciBjbGFz
cz0iIj4NCklQc2VjIFNlY3VyaXR5IEFzc29jaWF0aW9uIChJUHNlYyBTQSkgbWFuYWdlbWVudC48
YnIgY2xhc3M9IiI+DQo8YnIgY2xhc3M9IiI+DQpBZGRpdGlvbmFsbHksIFNlY3Rpb24gNC4zLjMg
aW4gW1JGQzgxOTJdIGRlc2NyaWJlcyBhbm90aGVyIGV4YW1wbGUgdXNlIGNhc2UgZm9yPGJyIGNs
YXNzPSIiPg0KQ2xvdWQgRGF0YSBDZW50ZXIgU2NlbmFyaW8gdGl0bGVkICZxdW90O0NsaWVudC1T
cGVjaWZpYyBTZWN1cml0eSBQb2xpY3kgaW4gQ2xvdWQ8YnIgY2xhc3M9IiI+DQpWUE5zJnF1b3Q7
LiBUaGUgdXNlIGNhc2UgaW4gUkZDIDgxOTIgc3RhdGVzIHRoYXQgJnF1b3Q7ZHluYW1pYyBrZXkg
bWFuYWdlbWVudCBpcyBjcml0aWNhbDxiciBjbGFzcz0iIj4NCmZvciBzZWN1cmluZyB0aGUgVlBO
IGFuZCB0aGUgZGlzdHJpYnV0aW9uIG9mIHBvbGljaWVzJnF1b3Q7LiAmbmJzcDtUaGVzZSBWUE5z
IGNhbiBiZTxiciBjbGFzcz0iIj4NCmVzdGFibGlzaGVkIHVzaW5nIElQc2VjLiAmbmJzcDtUaGUg
bWFuYWdlbWVudCBvZiBJUHNlYyBTQXMgaW4gZGF0YSBjZW50ZXJzIHVzaW5nIGE8YnIgY2xhc3M9
IiI+DQpjZW50cmFsaXplZCBlbnRpdHkgaXMgYSBzY2VuYXJpbyB3aGVyZSB0aGUgY3VycmVudCBz
cGVjaWZpY2F0aW9uIG1heWJlPGJyIGNsYXNzPSIiPg0KYXBwbGljYWJsZS48YnIgY2xhc3M9IiI+
DQo8YnIgY2xhc3M9IiI+DQotIFRoaXMgdGV4dCBpcyByZXBlYXRlZCB0d2ljZTogJnF1b3Q7SW4g
dGhlIElLRSBjYXNlLCBJS0V2MiBhbHJlYWR5IHByb3ZpZGVzIGE8YnIgY2xhc3M9IiI+DQptZWNo
YW5pc20gdG8gZGV0ZWN0IHdoZXRoZXIgLi4uJnF1b3Q7PGJyIGNsYXNzPSIiPg0KPGJyIGNsYXNz
PSIiPg0KLSAmcXVvdDt2aWV3IGlzIGJ1aWx0IGVpdGhlciByZXF1ZXN0aW5nIGluZm9ybWF0aW9u
IHRvIHRoZSBOU0ZzIHVuZGVyIGl0cyBjb250cm9sLDxiciBjbGFzcz0iIj4NCm9yIGJlY2F1c2Ug
dGhlc2UgTlNGcyBpbmZvcm0gdGhlIEkyTlNGIENvbnRyb2xsZXIuJnF1b3Q7IC0mZ3Q7ICZxdW90
O3ZpZXcgaXMgYnVpbHQgZWl0aGVyIGJ5PGJyIGNsYXNzPSIiPg0KcmVxdWVzdGluZyBpbmZvcm1h
dGlvbiBmcm9tIHRoZSBOU0ZzIHVuZGVyIGl0cyBjb250cm9sLCBvciBieSBpbmZvcm1hdGlvbjxi
ciBjbGFzcz0iIj4NCnB1c2hlZCBmcm9tIHRoZSBOU0ZzIHRvIHRoZSBJMk5TRiBDb250cm9sbGVy
JnF1b3Q7PGJyIGNsYXNzPSIiPg0KPGJyIGNsYXNzPSIiPg0KLSAmcXVvdDtDb21iaW5lZCBhbGdv
cml0aG1zIGhhcyBiZWVuIHJlbW92ZWQmcXVvdDsgLSZndDsgaGF2ZSBiZWVuPGJyIGNsYXNzPSIi
Pg0KPGJyIGNsYXNzPSIiPg0KLSAmcXVvdDthZG1pdCB0aGUgY29uZmlndXJhdGlvbnMgb2YgdGhl
c2UgdmFsdWVzLiZxdW90OyAtJmd0OyAmcXVvdDthY2NlcHQgY29uZmlndXJhdGlvbiBvZiB0aGVz
ZTxiciBjbGFzcz0iIj4NCnZhbHVlcyZxdW90OzxiciBjbGFzcz0iIj4NCjxiciBjbGFzcz0iIj4N
Ci0gJnF1b3Q7QmVzaWRlLCBJYWFTIHNlcnZpY2VzIHByb3ZpZGluZyB2aXJ0dWFsaXphdGlvbiBl
bnZpcm9ubWVudHMgYXJlIGRlcGxveW1lbnRzPGJyIGNsYXNzPSIiPg0Kc29sdXRpb25zIGJhc2Vk
IG9uIElQc2VjIHRvIHByb3ZpZGUmcXVvdDsgLSZndDsgJnF1b3Q7QmVzaWRlcywgSWFhUyBzZXJ2
aWNlcyBwcm92aWRpbmc8YnIgY2xhc3M9IiI+DQp2aXJ0dWFsaXphdGlvbiBlbnZpcm9ubWVudHMg
YXJlIGRlcGxveW1lbnRzIHRoYXQgb2Z0ZW4gcmVseSBvbiBJUHNlYyB0byBwcm92aWRlJnF1b3Q7
PGJyIGNsYXNzPSIiPg0KPGJyIGNsYXNzPSIiPg0KLSAmcXVvdDtEZXNwaXRlIHRoaXMgcHJvY2Vk
dXJlIG1heSBpbmNyZWFzZSB0aGUgbGF0ZW5jeSB0byBjb21wbGV0ZSB0aGUgcHJvY2Vzcywgbm88
YnIgY2xhc3M9IiI+DQp0cmFmZmljIGlzIHNlbnQgb3ZlciB0aGUgbmV0d29yayB1bnRpbCB0aGUg
SVBzZWMgU0FzIGFyZSBjb21wbGV0ZWx5IG9wZXJhdGl2ZS4mcXVvdDs8YnIgY2xhc3M9IiI+DQot
Jmd0OyAmcXVvdDtFdmVuIHRob3VnaCB0aGlzIHByb2NlZHVyZSBtYXkgaW5jcmVhc2UmcXVvdDs8
YnIgY2xhc3M9IiI+DQo8YnIgY2xhc3M9IiI+DQotICZxdW90O0lmIHNvbWUgb2YgdGhlIG9wZXJh
dGlvbnMgZGVzY3JpYmVkIGFib3ZlIGZhaWxzJnF1b3Q7IC0mZ3Q7ICZxdW90O0lmIHNvbWUgb2Yg
dGhlPGJyIGNsYXNzPSIiPg0Kb3BlcmF0aW9ucyBkZXNjcmliZWQgYWJvdmUgZmFpbCZxdW90Ozxi
ciBjbGFzcz0iIj4NCjxiciBjbGFzcz0iIj4NCi0gJnF1b3Q7SW4gc3VjaCBhcyByZWFjdGl2ZSBt
b2RlLCB1cG9uIHJlY2VwdGlvbiBvZiB0aGUgc2FkYi1hY3F1aXJlIG5vdGlmaWNhdGlvbiw8YnIg
Y2xhc3M9IiI+DQp0aGUgSTJOU0YgQ29udHJvbGxlciBpbnN0YWxscyB0aGUgbmV3IElQc2VjIFNB
cyBpbiBOU0YgQSBhbmQgQiAoZm9sbG93aW5nJnF1b3Q7IC0mZ3Q7ICZxdW90OyZxdW90OzxiciBj
bGFzcz0iIj4NCjxiciBjbGFzcz0iIj4NCi0gJnF1b3Q7SWYgdGhpcyBpcyBub3QgY3JpdGljIHRo
ZW4gaXQgaXMgYW4mcXVvdDsgLSZndDsgdGhpcyBpcyBub3QgY3JpdGljYWw8YnIgY2xhc3M9IiI+
DQo8YnIgY2xhc3M9IiI+DQo8YnIgY2xhc3M9IiI+DQpfX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fXzxiciBjbGFzcz0iIj4NCkkybnNmIG1haWxpbmcgbGlzdDxi
ciBjbGFzcz0iIj4NCjxhIGhyZWY9Im1haWx0bzpJMm5zZkBpZXRmLm9yZyIgY2xhc3M9IiIgbW96
LWRvLW5vdC1zZW5kPSJ0cnVlIj5JMm5zZkBpZXRmLm9yZzwvYT48YnIgY2xhc3M9IiI+DQo8YSBj
bGFzcz0ibW96LXR4dC1saW5rLWZyZWV0ZXh0IiBocmVmPSJodHRwczovL3d3dy5pZXRmLm9yZy9t
YWlsbWFuL2xpc3RpbmZvL2kybnNmIj5odHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3Rp
bmZvL2kybnNmPC9hPjxiciBjbGFzcz0iIj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Jsb2NrcXVvdGU+
DQo8L2Rpdj4NCjxiciBjbGFzcz0iIj4NCjxkaXYgY2xhc3M9IiI+DQo8ZGl2IHN0eWxlPSJ3b3Jk
LXdyYXA6IGJyZWFrLXdvcmQ7IC13ZWJraXQtbmJzcC1tb2RlOg0KICAgICAgICAgICAgICAgIHNw
YWNlOyAtd2Via2l0LWxpbmUtYnJlYWs6IGFmdGVyLXdoaXRlLXNwYWNlOyIgY2xhc3M9IiI+DQo8
ZGl2IHN0eWxlPSJjb2xvcjogcmdiKDAsIDAsIDApOyBmb250LWZhbWlseTogQ291cmllcjsNCiAg
ICAgICAgICAgICAgICAgIGZvbnQtc2l6ZTogMTZweDsgZm9udC1zdHlsZTogbm9ybWFsOw0KICAg
ICAgICAgICAgICAgICAgZm9udC12YXJpYW50LWNhcHM6IG5vcm1hbDsgZm9udC13ZWlnaHQ6IG5v
cm1hbDsNCiAgICAgICAgICAgICAgICAgIGxldHRlci1zcGFjaW5nOiBub3JtYWw7IG9ycGhhbnM6
IGF1dG87IHRleHQtYWxpZ246DQogICAgICAgICAgICAgICAgICBzdGFydDsgdGV4dC1pbmRlbnQ6
IDBweDsgdGV4dC10cmFuc2Zvcm06IG5vbmU7DQogICAgICAgICAgICAgICAgICB3aGl0ZS1zcGFj
ZTogbm9ybWFsOyB3aWRvd3M6IGF1dG87IHdvcmQtc3BhY2luZzogMHB4Ow0KICAgICAgICAgICAg
ICAgICAgLXdlYmtpdC10ZXh0LXN0cm9rZS13aWR0aDogMHB4OyI+DQotLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tPGJyIGNsYXNzPSIiPg0KUmFm
YSBNYXJpbi1Mb3BleiwgUGhEPGJyIGNsYXNzPSIiPg0KRGVwdC4gSW5mb3JtYXRpb24gYW5kJm5i
c3A7Q29tbXVuaWNhdGlvbnMmbmJzcDtFbmdpbmVlcmluZyAoRElJQyk8YnIgY2xhc3M9IiI+DQpG
YWN1bHR5IG9mIENvbXB1dGVyJm5ic3A7U2NpZW5jZS1Vbml2ZXJzaXR5IG9mJm5ic3A7TXVyY2lh
PGJyIGNsYXNzPSIiPg0KMzAxMDAgTXVyY2lhIC0gU3BhaW48YnIgY2xhc3M9IiI+DQpUZWxmOiAr
MzQ4Njg4ODg1MDEgRmF4OiZuYnNwOyszNDg2ODg4NDE1MSA8YSBocmVmPSJtYWlsdG86cmFmYUB1
bS5lcyIgY2xhc3M9IiIgbW96LWRvLW5vdC1zZW5kPSJ0cnVlIj4NCmUtbWFpbDombmJzcDtyYWZh
QHVtLmVzPC9hPjxiciBjbGFzcz0iIj4NCi0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS08L2Rpdj4NCjxkaXYgc3R5bGU9ImNvbG9yOiByZ2IoMCwg
MCwgMCk7IGZvbnQtZmFtaWx5OiBDb3VyaWVyOw0KICAgICAgICAgICAgICAgICAgZm9udC1zaXpl
OiAxNnB4OyBmb250LXN0eWxlOiBub3JtYWw7DQogICAgICAgICAgICAgICAgICBmb250LXZhcmlh
bnQtY2Fwczogbm9ybWFsOyBmb250LXdlaWdodDogbm9ybWFsOw0KICAgICAgICAgICAgICAgICAg
bGV0dGVyLXNwYWNpbmc6IG5vcm1hbDsgb3JwaGFuczogYXV0bzsgdGV4dC1hbGlnbjoNCiAgICAg
ICAgICAgICAgICAgIHN0YXJ0OyB0ZXh0LWluZGVudDogMHB4OyB0ZXh0LXRyYW5zZm9ybTogbm9u
ZTsNCiAgICAgICAgICAgICAgICAgIHdoaXRlLXNwYWNlOiBub3JtYWw7IHdpZG93czogYXV0bzsg
d29yZC1zcGFjaW5nOiAwcHg7DQogICAgICAgICAgICAgICAgICAtd2Via2l0LXRleHQtc3Ryb2tl
LXdpZHRoOiAwcHg7IiBjbGFzcz0iIj4NCjxiciBjbGFzcz0iIj4NCjwvZGl2Pg0KPGJyIGNsYXNz
PSJBcHBsZS1pbnRlcmNoYW5nZS1uZXdsaW5lIj4NCjwvZGl2Pg0KPGJyIGNsYXNzPSJBcHBsZS1p
bnRlcmNoYW5nZS1uZXdsaW5lIj4NCjwvZGl2Pg0KPGJyIGNsYXNzPSIiPg0KPC9kaXY+DQo8L2Rp
dj4NCjwvZGl2Pg0KPGJyPg0KPGZpZWxkc2V0IGNsYXNzPSJtaW1lQXR0YWNobWVudEhlYWRlciI+
PC9maWVsZHNldD4gPC9ibG9ja3F1b3RlPg0KPC9ib2R5Pg0KPC9odG1sPg0K

--_000_486e2620192ae0c721c1480cc1d5f69aericssoncom_--


From nobody Tue Oct  6 20:04:59 2020
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 406D63A15C8; Tue,  6 Oct 2020 20:04:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.086
X-Spam-Level: 
X-Spam-Status: No, score=-2.086 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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_HK_NAME_FM_MR_MRS=0.01, URIBL_BLOCKED=0.001, URI_DOTEDU=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 iy7bzinkp849; Tue,  6 Oct 2020 20:04:55 -0700 (PDT)
Received: from mail-lf1-x12d.google.com (mail-lf1-x12d.google.com [IPv6:2a00:1450:4864:20::12d]) (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 63B193A15C7; Tue,  6 Oct 2020 20:04:54 -0700 (PDT)
Received: by mail-lf1-x12d.google.com with SMTP id g2so558790lfr.10; Tue, 06 Oct 2020 20:04:54 -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=HKbC1NXKY7aOGlZc2iSAXCBW7lQ4n+Wb3WMQ/AyXnb8=; b=ZGDIA34UqY4NavFBJCf/hPzuwHE8ztqtiuQ2cnR1DJBu1CA3mGns7x0Uzz0HAAyDt4 za6kdJ4wN95kW/ar+qyisQM81Q9bu1BTV/oql7N/0gPOQw4RSPtt1dyOLm/E8cPXzcvk bLMe6vcOmKzpHbuZ1RG/tBleldggZMiavxWp8AfBogNw2gQS1YnRdd1ZqSMTbWmYy4mO 1D5aXtepeIL+sknbVsqIRjNO0eN3Xxpwz8oGc9lYZy7b+iJITyWJLI3YLMLpqyFgQObk 5ROBtipM+rHyTqHXwPmrxaMLkdNuYZfuB9e8JYarAKC1SSPsLq68L/Nu3QG/63dumMbF fJ7Q==
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=HKbC1NXKY7aOGlZc2iSAXCBW7lQ4n+Wb3WMQ/AyXnb8=; b=CE2DZbYtv3oIJmnypUb7fdX1E+AvYvlYIvmhX4cY1YGwJrGK2qF2649bBIIgxLvVFD pgIIAyr8K0YY3t/RGo2/aaUU7yl5jer0u+vUyRFzCW5ac1e15yQkya1wDtYiKLT0ENQN ZXTjp4HBWbuMcQ1nQrbdWiCxozYRfe+bwnYDjEofhT/ggBQPip8joX/L3gSvuoUvtqbX 4MYAcg8ELdn6LGrQUc9J9Ijm0LfdHW6j6i0NCntuxJcezhIgI2MQd+4gyavIHUenPP36 y5oIE5aGTeAYvXq2tCUB6Nd9e5XvCMkpSLiEoNHdc/UhLI4lBx5NpHdeBZrhl2iivxOc MPNQ==
X-Gm-Message-State: AOAM530DMmh9kScfXFSFjxg5t7GLy+u8wpU7OKxKE3m19WCuuvTiaOC+ qc7+68hRqggk1LwpnadtjexdAx//DJdq4n4reNo=
X-Google-Smtp-Source: ABdhPJwkfe7coiv2VQGFABGySpJNtgPn8dRdODTKzg9d28KJTLpVlDW0xxM2AGgiUhNsPykQ04kOfM07Vqvq4QD9ZYE=
X-Received: by 2002:a19:7108:: with SMTP id m8mr265972lfc.335.1602039892269; Tue, 06 Oct 2020 20:04:52 -0700 (PDT)
MIME-Version: 1.0
References: <160192102291.6633.15935674903085952087@ietfa.amsl.com> <CAPK2DewOF7QcTD8UdFYdoGUvnJz_fxb53OOn-KmYQgNA38xLoA@mail.gmail.com> <CABCOCHQsxFVNdBgL9fyZHV+Bevs1D8d5B=+KJAgoVBVekz+VtQ@mail.gmail.com> <CAPK2DewNDq2_DtZhtxitTsavHczwiSKur9+yQPLR+18UbV-QHg@mail.gmail.com> <CABCOCHT-0mKbYBDtZHnANRLqMtSsT1ijhoe1znoS2_pDHn4WNA@mail.gmail.com>
In-Reply-To: <CABCOCHT-0mKbYBDtZHnANRLqMtSsT1ijhoe1znoS2_pDHn4WNA@mail.gmail.com>
From: "Mr. Jaehoon Paul Jeong" <jaehoon.paul@gmail.com>
Date: Wed, 7 Oct 2020 12:04:15 +0900
Message-ID: <CAPK2Dexfpfgt730k5Zn3Aq34946Q5go4TuRrekA2hbbm_Wj_Jg@mail.gmail.com>
To: Andy Bierman <andy@yumaworks.com>
Cc: YANG Doctors <yang-doctors@ietf.org>, "i2nsf@ietf.org" <i2nsf@ietf.org>,  draft-ietf-i2nsf-nsf-monitoring-data-model.all@ietf.org,  Patrick Lingga <patricklink888@gmail.com>
Content-Type: multipart/alternative; boundary="000000000000b1dedb05b10bfad3"
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2nsf/V0jP4d5Clg7cmF5nQZxRUisSlK0>
Subject: Re: [I2nsf] Yangdoctors early review of draft-ietf-i2nsf-nsf-monitoring-data-model-04
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: Wed, 07 Oct 2020 03:04:57 -0000

--000000000000b1dedb05b10bfad3
Content-Type: text/plain; charset="UTF-8"

Hi Andy,
I will investigate the event stream with information you sent me below.

Thanks for your help and advice.

Best Regards,
Paul

On Tue, Oct 6, 2020 at 1:51 PM Andy Bierman <andy@yumaworks.com> wrote:

>
>
> On Mon, Oct 5, 2020 at 9:05 PM Mr. Jaehoon Paul Jeong <
> jaehoon.paul@gmail.com> wrote:
>
>> Andy,
>> What do you mean by the event stream?
>>
>>
> https://tools.ietf.org/html/rfc8639#section-2.1
>
>
>
>> Actually, I am thinking that the NETCONF can deliver the monitoring data
>> of a system or an NSF in an XML file.
>>
>> Do you think that we need another way to convey the monitoring data?
>>
>> Thanks.
>>
>> Best Regards,
>> Paul
>>
>> On Tue, Oct 6, 2020 at 12:30 PM Andy Bierman <andy@yumaworks.com> wrote:
>>
>>>
>>>
>>> On Mon, Oct 5, 2020 at 7:30 PM Mr. Jaehoon Paul Jeong <
>>> jaehoon.paul@gmail.com> wrote:
>>>
>>>> Hi Andy,
>>>> Thanks for your valuable comments on our NSF Monitoring YANG Data Model
>>>> Draft.
>>>> We authors will reflect your comments on the revision and come back to
>>>> you with
>>>> the revised draft and revision letter.
>>>>
>>>>
>>> I forgot 1 comment:
>>>
>>>  - the draft is not that explicit about the event stream to use for
>>> these notifications
>>>    Perhaps a new standard event stream (I2NSF) would be better than the
>>> standard (NETCONF)
>>>    The draft should be more clear wrt/ the NETCONF stream.
>>>
>>>
>>> Andy
>>>
>>>
>>>
>>>> Thanks.
>>>>
>>>> Best Regards,
>>>> Paul
>>>>
>>>>
>>>> On Tue, Oct 6, 2020 at 3:03 AM Andy Bierman via Datatracker <
>>>> noreply@ietf.org> wrote:
>>>>
>>>>> Reviewer: Andy Bierman
>>>>> Review result: Almost Ready
>>>>>
>>>>>
>>>>>
>>>>> Major Issues:
>>>>>
>>>>>  - None
>>>>>
>>>>> Moderate Issues:
>>>>>
>>>>>  - top-level 'counters' container does not follow naming conventions.
>>>>>    Should start with 'i2nsf', probably 'i2nsf-state'
>>>>>
>>>>>  - There do not seem to be any writable objects in the /counters
>>>>>    subtree so this container should have a 'config false' statement
>>>>>
>>>>>  - top-level typedef and grouping description-stmts are
>>>>> self-referential
>>>>>    and not useful. Need to rewrite description-stmts and/or add
>>>>>    reference-stmts as needed.
>>>>>
>>>>>  - grouping common-monitoring-data/time-stamp
>>>>>    Is this a different time stamp than the one in the NETCONF
>>>>> notification?
>>>>>    The 'message generation time' sounds like the standard timestamp.
>>>>>    Does this object represent the event detection time?
>>>>>
>>>>>  - grouping i2nsf-system-alarm-type-content/usage
>>>>>  - grouping i2nsf-system-alarm-type-content/threshold
>>>>>    These are uint8 leafs with unclear descriptions.
>>>>>    Not sure why uint8 is the appropriate type.
>>>>>    Needs 1 or more of (reference, units, better description)
>>>>>
>>>>>  - grouping traffic-rates
>>>>>    Add a units statement to each leaf. Not sure what units to use
>>>>>    but it should be consistent. (e.g, pps, bps used in descriptions
>>>>>    should also be in a units-stmt)
>>>>>
>>>>>  - grouping i2nsf-system-counter-type-content
>>>>>    These counters should use the yang:counter32 type instead of uint32
>>>>>
>>>>>  - container counters/system-interface
>>>>>  - container counters/nsf-firewall
>>>>>  - container counters/nsf-policy-hits
>>>>>   The descriptions are too terse and confusing, and need a rewrite.
>>>>>
>>>>>  -  container counters/nsf-firewall
>>>>>  -  container counters/nsf-policy-hits
>>>>>     - uses i2nsf-nsf-counters-type-content;
>>>>>     Many of the fields expanded from this grouping all say
>>>>>     they refer to 'the packet'. Why are they in this global
>>>>>     container of counters? E.g. (src-ip, dst-ip, src-port, dst-port)
>>>>>     Not clear at all how the server is supposed to apply this
>>>>>     grouping to these containers.
>>>>>
>>>>>  - many leafs use "uint32" type for a rate.
>>>>>    Should add a units-stmt
>>>>>
>>>>>  - leaf counters/nsf-policy-hits/hit-times
>>>>>    The purpose and type are confusing and generic.
>>>>>    If this is a counter then use counter32
>>>>>
>>>>>  - cut-and-paste for notification-stmt content should be replaced
>>>>>    with grouping/uses instead. Applies to the nsf-detection-*
>>>>>    and the various logging notifications. Even a grouping that
>>>>>    has 1 object in it is better than cut-and-paste 5+ times
>>>>>
>>>>> Minor Issues:
>>>>>
>>>>>  - top-level identifiers are too generic
>>>>>    should have 'i2nsf-' prefix to be more reusable outside this module
>>>>>
>>>>>  - quite a lot of identities that an implementation is required to
>>>>> support.
>>>>>    If this set of identities might change a lot faster than the
>>>>>    notifications and counter objects, then consider putting them
>>>>>    in a separate module
>>>>>
>>>>>  - leaf with same type named differently; both intrusion-attack-type
>>>>>    - nsf-detection-intrusion/sub-attack-type
>>>>>    - nsf-log-intrusion/attack-type
>>>>>
>>>>>  - quite a lot of notification event types for a server to implement
>>>>>    and a user to manage. All are mandatory (no if-feature statements).
>>>>>    Some such as nsf-detection-* subset are very similar.
>>>>>    A section or table would be useful that showed the YANG notification
>>>>>    names and their purpose -- maybe a reference to another RFC
>>>>>    with more details
>>>>>
>>>>>  - there seems to be notifications for intrusion events and then
>>>>>    again for the logging of those events.  This seems excessive
>>>>>    but
>>>>>
>>>>>
>>>>>  - grouping common-monitoring-data/time-stamp
>>>>>    Is this a different time stamp than the one in the NETCONF
>>>>> notification?
>>>>>    The 'message generation time' sounds like the standard timestamp.
>>>>>    Is this event detection time?
>>>>>
>>>>>  - grouping common-monitoring-data/module-name
>>>>>    Is this a YANG module or some other type of module?
>>>>>
>>>>>  - there is no way to configure which notifications should be generated
>>>>>    or maybe how often.  YANG Push has its own dampening-period.
>>>>>    Since these are event stream subscriptions, not datastore
>>>>> subscriptions,
>>>>>    YANG-Push does not apply to this document at all.
>>>>>
>>>>>    If there are a lot of notifications then a server implementation
>>>>>    might drop some
>>>>>
>>>>>  - grouping i2nsf-nsf-event-type-content-extend/src-zone
>>>>>  - grouping i2nsf-nsf-event-type-content-extend/src-zone
>>>>>    These use type 'string'. Consider using a typedef that constrains
>>>>>    the string.  General comment where unconstrained string is used:
>>>>>    The corner-case values such as empty string are often not allowed
>>>>>    in implementations.
>>>>>
>>>>>
>>>>>  - grouping i2nsf-nsf-event-type-content-extend/rule-id
>>>>>  - grouping i2nsf-nsf-event-type-content-extend/rule-name
>>>>>  - grouping i2nsf-nsf-event-type-content-extend/profile
>>>>>    These objects seem to reference objects in another YANG module.
>>>>>    If so, then leafref types might be more appropriate.
>>>>>
>>>>>  - grouping i2nsf-nsf-event-type-content/rule-id
>>>>>  - grouping i2nsf-nsf-event-type-content/rule-name
>>>>>  - grouping i2nsf-nsf-event-type-content/profile
>>>>>  - grouping i2nsf-nsf-event-type-content/raw-info
>>>>>    These objects are cut-and-paste duplicates from
>>>>>    grouping i2nsf-nsf-event-type-content. They should
>>>>>    be in a separate grouping used by both. Also applies
>>>>>    to some other sets of objects
>>>>>
>>>>>  - limits issues (e.g. current-session, maximum-session
>>>>>    The type is uint8. This is only OK it is impossible for any
>>>>>    implementation to ever have or want more than 255 of them.
>>>>>    If some other RFC really does limit the values where uint8
>>>>>    is used, then that is OK. If so, a reference-stmt would help.
>>>>>
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> I2nsf mailing list
>>>>> I2nsf@ietf.org
>>>>> https://www.ietf.org/mailman/listinfo/i2nsf
>>>>>
>>>>
>>>>
>>>> --
>>>> ===========================
>>>> Mr. Jaehoon (Paul) Jeong, Ph.D.
>>>> Associate Professor
>>>> Department of Computer Science and Engineering
>>>> Sungkyunkwan University
>>>> Office: +82-31-299-4957
>>>> Email: jaehoon.paul@gmail.com, pauljeong@skku.edu
>>>> Personal Homepage: http://iotlab.skku.edu/people-jaehoon-jeong.php
>>>> <http://cpslab.skku.edu/people-jaehoon-jeong.php>
>>>>
>>>
>>
>> --
>> ===========================
>> Mr. Jaehoon (Paul) Jeong, Ph.D.
>> Associate Professor
>> Department of Computer Science and Engineering
>> Sungkyunkwan University
>> Office: +82-31-299-4957
>> Email: jaehoon.paul@gmail.com, pauljeong@skku.edu
>> Personal Homepage: http://iotlab.skku.edu/people-jaehoon-jeong.php
>> <http://cpslab.skku.edu/people-jaehoon-jeong.php>
>>
>

-- 
===========================
Mr. Jaehoon (Paul) Jeong, Ph.D.
Associate Professor
Department of Computer Science and Engineering
Sungkyunkwan University
Office: +82-31-299-4957
Email: jaehoon.paul@gmail.com, pauljeong@skku.edu
Personal Homepage: http://iotlab.skku.edu/people-jaehoon-jeong.php
<http://cpslab.skku.edu/people-jaehoon-jeong.php>

--000000000000b1dedb05b10bfad3
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi Andy,<div>I will investigate the event stream with info=
rmation you sent me below.</div><div><br></div><div>Thanks for your=C2=A0he=
lp=C2=A0and advice.</div><div><br></div><div>Best Regards,</div><div>Paul</=
div></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_at=
tr">On Tue, Oct 6, 2020 at 1:51 PM Andy Bierman &lt;<a href=3D"mailto:andy@=
yumaworks.com">andy@yumaworks.com</a>&gt; wrote:<br></div><blockquote class=
=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rg=
b(204,204,204);padding-left:1ex"><div dir=3D"ltr"><div dir=3D"ltr"><br></di=
v><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On M=
on, Oct 5, 2020 at 9:05 PM Mr. Jaehoon Paul Jeong &lt;<a href=3D"mailto:jae=
hoon.paul@gmail.com" target=3D"_blank">jaehoon.paul@gmail.com</a>&gt; wrote=
:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.=
8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir=3D"lt=
r">Andy,<div>What do you mean by the event stream?</div><div><br></div></di=
v></blockquote><div><br></div><div><a href=3D"https://tools.ietf.org/html/r=
fc8639#section-2.1" target=3D"_blank">https://tools.ietf.org/html/rfc8639#s=
ection-2.1</a></div><div><br></div><div>=C2=A0</div><blockquote class=3D"gm=
ail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,=
204,204);padding-left:1ex"><div dir=3D"ltr"><div></div><div>Actually, I am =
thinking that the NETCONF can deliver the monitoring data of a system or an=
 NSF in an XML file.</div><div><br></div><div>Do you think that we need ano=
ther way to convey the monitoring data?</div><div><br></div><div>Thanks.</d=
iv><div><br></div><div>Best Regards,</div><div>Paul</div></div><br><div cla=
ss=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Tue, Oct 6, 202=
0 at 12:30 PM Andy Bierman &lt;<a href=3D"mailto:andy@yumaworks.com" target=
=3D"_blank">andy@yumaworks.com</a>&gt; wrote:<br></div><blockquote class=3D=
"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(2=
04,204,204);padding-left:1ex"><div dir=3D"ltr"><div dir=3D"ltr"><br></div><=
br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Mon,=
 Oct 5, 2020 at 7:30 PM Mr. Jaehoon Paul Jeong &lt;<a href=3D"mailto:jaehoo=
n.paul@gmail.com" target=3D"_blank">jaehoon.paul@gmail.com</a>&gt; wrote:<b=
r></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex=
;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr">=
Hi Andy,<div>Thanks for your valuable comments on our NSF Monitoring YANG D=
ata Model Draft.</div><div>We authors will reflect your comments on the rev=
ision and come back to you with</div><div>the revised draft and revision le=
tter.</div><div><br></div></div></blockquote><div><br></div><div>I forgot 1=
 comment:</div><div><br></div><div>=C2=A0- the draft is not that explicit a=
bout the event stream to use for these notifications</div><div>=C2=A0 =C2=
=A0Perhaps a new standard event stream (I2NSF) would be better than the sta=
ndard (NETCONF)</div><div>=C2=A0 =C2=A0The draft should be more clear wrt/ =
the NETCONF stream.</div><div><br></div><div><br></div><div>Andy</div><div>=
<br></div><div>=C2=A0=C2=A0</div><blockquote class=3D"gmail_quote" style=3D=
"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-le=
ft:1ex"><div dir=3D"ltr"><div></div><div>Thanks.</div><div><br></div><div>B=
est Regards,</div><div>Paul</div><div><br></div></div><br><div class=3D"gma=
il_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Tue, Oct 6, 2020 at 3:03=
 AM Andy Bierman via Datatracker &lt;<a href=3D"mailto:noreply@ietf.org" ta=
rget=3D"_blank">noreply@ietf.org</a>&gt; wrote:<br></div><blockquote class=
=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rg=
b(204,204,204);padding-left:1ex">Reviewer: Andy Bierman<br>
Review result: Almost Ready<br>
<br>
<br>
<br>
Major Issues:<br>
<br>
=C2=A0- None<br>
<br>
Moderate Issues:<br>
<br>
=C2=A0- top-level &#39;counters&#39; container does not follow naming conve=
ntions.<br>
=C2=A0 =C2=A0Should start with &#39;i2nsf&#39;, probably &#39;i2nsf-state&#=
39;<br>
<br>
=C2=A0- There do not seem to be any writable objects in the /counters<br>
=C2=A0 =C2=A0subtree so this container should have a &#39;config false&#39;=
 statement<br>
<br>
=C2=A0- top-level typedef and grouping description-stmts are self-referenti=
al<br>
=C2=A0 =C2=A0and not useful. Need to rewrite description-stmts and/or add<b=
r>
=C2=A0 =C2=A0reference-stmts as needed.<br>
<br>
=C2=A0- grouping common-monitoring-data/time-stamp<br>
=C2=A0 =C2=A0Is this a different time stamp than the one in the NETCONF not=
ification?<br>
=C2=A0 =C2=A0The &#39;message generation time&#39; sounds like the standard=
 timestamp.<br>
=C2=A0 =C2=A0Does this object represent the event detection time?<br>
<br>
=C2=A0- grouping i2nsf-system-alarm-type-content/usage<br>
=C2=A0- grouping i2nsf-system-alarm-type-content/threshold<br>
=C2=A0 =C2=A0These are uint8 leafs with unclear descriptions.<br>
=C2=A0 =C2=A0Not sure why uint8 is the appropriate type.<br>
=C2=A0 =C2=A0Needs 1 or more of (reference, units, better description)<br>
<br>
=C2=A0- grouping traffic-rates<br>
=C2=A0 =C2=A0Add a units statement to each leaf. Not sure what units to use=
<br>
=C2=A0 =C2=A0but it should be consistent. (e.g, pps, bps used in descriptio=
ns<br>
=C2=A0 =C2=A0should also be in a units-stmt)<br>
<br>
=C2=A0- grouping i2nsf-system-counter-type-content<br>
=C2=A0 =C2=A0These counters should use the yang:counter32 type instead of u=
int32<br>
<br>
=C2=A0- container counters/system-interface<br>
=C2=A0- container counters/nsf-firewall<br>
=C2=A0- container counters/nsf-policy-hits<br>
=C2=A0 The descriptions are too terse and confusing, and need a rewrite.<br=
>
<br>
=C2=A0-=C2=A0 container counters/nsf-firewall<br>
=C2=A0-=C2=A0 container counters/nsf-policy-hits<br>
=C2=A0 =C2=A0 - uses i2nsf-nsf-counters-type-content;<br>
=C2=A0 =C2=A0 Many of the fields expanded from this grouping all say<br>
=C2=A0 =C2=A0 they refer to &#39;the packet&#39;. Why are they in this glob=
al<br>
=C2=A0 =C2=A0 container of counters? E.g. (src-ip, dst-ip, src-port, dst-po=
rt)<br>
=C2=A0 =C2=A0 Not clear at all how the server is supposed to apply this<br>
=C2=A0 =C2=A0 grouping to these containers.<br>
<br>
=C2=A0- many leafs use &quot;uint32&quot; type for a rate.<br>
=C2=A0 =C2=A0Should add a units-stmt<br>
<br>
=C2=A0- leaf counters/nsf-policy-hits/hit-times<br>
=C2=A0 =C2=A0The purpose and type are confusing and generic.<br>
=C2=A0 =C2=A0If this is a counter then use counter32<br>
<br>
=C2=A0- cut-and-paste for notification-stmt content should be replaced<br>
=C2=A0 =C2=A0with grouping/uses instead. Applies to the nsf-detection-*<br>
=C2=A0 =C2=A0and the various logging notifications. Even a grouping that<br=
>
=C2=A0 =C2=A0has 1 object in it is better than cut-and-paste 5+ times<br>
<br>
Minor Issues:<br>
<br>
=C2=A0- top-level identifiers are too generic<br>
=C2=A0 =C2=A0should have &#39;i2nsf-&#39; prefix to be more reusable outsid=
e this module<br>
<br>
=C2=A0- quite a lot of identities that an implementation is required to sup=
port.<br>
=C2=A0 =C2=A0If this set of identities might change a lot faster than the<b=
r>
=C2=A0 =C2=A0notifications and counter objects, then consider putting them<=
br>
=C2=A0 =C2=A0in a separate module<br>
<br>
=C2=A0- leaf with same type named differently; both intrusion-attack-type<b=
r>
=C2=A0 =C2=A0- nsf-detection-intrusion/sub-attack-type<br>
=C2=A0 =C2=A0- nsf-log-intrusion/attack-type<br>
<br>
=C2=A0- quite a lot of notification event types for a server to implement<b=
r>
=C2=A0 =C2=A0and a user to manage. All are mandatory (no if-feature stateme=
nts).<br>
=C2=A0 =C2=A0Some such as nsf-detection-* subset are very similar.<br>
=C2=A0 =C2=A0A section or table would be useful that showed the YANG notifi=
cation<br>
=C2=A0 =C2=A0names and their purpose -- maybe a reference to another RFC<br=
>
=C2=A0 =C2=A0with more details<br>
<br>
=C2=A0- there seems to be notifications for intrusion events and then<br>
=C2=A0 =C2=A0again for the logging of those events.=C2=A0 This seems excess=
ive<br>
=C2=A0 =C2=A0but<br>
<br>
<br>
=C2=A0- grouping common-monitoring-data/time-stamp<br>
=C2=A0 =C2=A0Is this a different time stamp than the one in the NETCONF not=
ification?<br>
=C2=A0 =C2=A0The &#39;message generation time&#39; sounds like the standard=
 timestamp.<br>
=C2=A0 =C2=A0Is this event detection time?<br>
<br>
=C2=A0- grouping common-monitoring-data/module-name<br>
=C2=A0 =C2=A0Is this a YANG module or some other type of module?<br>
<br>
=C2=A0- there is no way to configure which notifications should be generate=
d<br>
=C2=A0 =C2=A0or maybe how often.=C2=A0 YANG Push has its own dampening-peri=
od.<br>
=C2=A0 =C2=A0Since these are event stream subscriptions, not datastore subs=
criptions,<br>
=C2=A0 =C2=A0YANG-Push does not apply to this document at all.<br>
<br>
=C2=A0 =C2=A0If there are a lot of notifications then a server implementati=
on<br>
=C2=A0 =C2=A0might drop some<br>
<br>
=C2=A0- grouping i2nsf-nsf-event-type-content-extend/src-zone<br>
=C2=A0- grouping i2nsf-nsf-event-type-content-extend/src-zone<br>
=C2=A0 =C2=A0These use type &#39;string&#39;. Consider using a typedef that=
 constrains<br>
=C2=A0 =C2=A0the string.=C2=A0 General comment where unconstrained string i=
s used:<br>
=C2=A0 =C2=A0The corner-case values such as empty string are often not allo=
wed<br>
=C2=A0 =C2=A0in implementations.<br>
<br>
<br>
=C2=A0- grouping i2nsf-nsf-event-type-content-extend/rule-id<br>
=C2=A0- grouping i2nsf-nsf-event-type-content-extend/rule-name<br>
=C2=A0- grouping i2nsf-nsf-event-type-content-extend/profile<br>
=C2=A0 =C2=A0These objects seem to reference objects in another YANG module=
.<br>
=C2=A0 =C2=A0If so, then leafref types might be more appropriate.<br>
<br>
=C2=A0- grouping i2nsf-nsf-event-type-content/rule-id<br>
=C2=A0- grouping i2nsf-nsf-event-type-content/rule-name<br>
=C2=A0- grouping i2nsf-nsf-event-type-content/profile<br>
=C2=A0- grouping i2nsf-nsf-event-type-content/raw-info<br>
=C2=A0 =C2=A0These objects are cut-and-paste duplicates from<br>
=C2=A0 =C2=A0grouping i2nsf-nsf-event-type-content. They should<br>
=C2=A0 =C2=A0be in a separate grouping used by both. Also applies<br>
=C2=A0 =C2=A0to some other sets of objects<br>
<br>
=C2=A0- limits issues (e.g. current-session, maximum-session<br>
=C2=A0 =C2=A0The type is uint8. This is only OK it is impossible for any<br=
>
=C2=A0 =C2=A0implementation to ever have or want more than 255 of them.<br>
=C2=A0 =C2=A0If some other RFC really does limit the values where uint8<br>
=C2=A0 =C2=A0is used, then that is OK. If so, a reference-stmt would help.<=
br>
<br>
<br>
<br>
_______________________________________________<br>
I2nsf mailing list<br>
<a href=3D"mailto:I2nsf@ietf.org" target=3D"_blank">I2nsf@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/i2nsf" rel=3D"noreferrer" =
target=3D"_blank">https://www.ietf.org/mailman/listinfo/i2nsf</a><br>
</blockquote></div><br clear=3D"all"><div><br></div>-- <br><div dir=3D"ltr"=
><div dir=3D"ltr"><div><div dir=3D"ltr"><div><div dir=3D"ltr"><div><div dir=
=3D"ltr">=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D<br>Mr. Jaehoon (Paul) Jeong, Ph.D.<br>Associate Professor<b=
r>Department of Computer Science and Engineering<br>Sungkyunkwan University=
<br>Office: +82-31-299-4957<br>Email: <a href=3D"mailto:jaehoon.paul@gmail.=
com" target=3D"_blank">jaehoon.paul@gmail.com</a>,=C2=A0<a href=3D"mailto:p=
auljeong@skku.edu" style=3D"font-size:12.8px" target=3D"_blank">pauljeong@s=
kku.edu</a><br>Personal Homepage: <a href=3D"http://cpslab.skku.edu/people-=
jaehoon-jeong.php" target=3D"_blank">http://iotlab.skku.edu/people-jaehoon-=
jeong.php</a><br></div></div></div></div></div></div></div></div>
</blockquote></div></div>
</blockquote></div><br clear=3D"all"><div><br></div>-- <br><div dir=3D"ltr"=
><div dir=3D"ltr"><div><div dir=3D"ltr"><div><div dir=3D"ltr"><div><div dir=
=3D"ltr">=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D<br>Mr. Jaehoon (Paul) Jeong, Ph.D.<br>Associate Professor<b=
r>Department of Computer Science and Engineering<br>Sungkyunkwan University=
<br>Office: +82-31-299-4957<br>Email: <a href=3D"mailto:jaehoon.paul@gmail.=
com" target=3D"_blank">jaehoon.paul@gmail.com</a>,=C2=A0<a href=3D"mailto:p=
auljeong@skku.edu" style=3D"font-size:12.8px" target=3D"_blank">pauljeong@s=
kku.edu</a><br>Personal Homepage: <a href=3D"http://cpslab.skku.edu/people-=
jaehoon-jeong.php" target=3D"_blank">http://iotlab.skku.edu/people-jaehoon-=
jeong.php</a><br></div></div></div></div></div></div></div></div>
</blockquote></div></div>
</blockquote></div><br clear=3D"all"><div><br></div>-- <br><div dir=3D"ltr"=
 class=3D"gmail_signature"><div dir=3D"ltr"><div><div dir=3D"ltr"><div><div=
 dir=3D"ltr"><div><div dir=3D"ltr">=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br>Mr. Jaehoon (Paul) Jeong, Ph.=
D.<br>Associate Professor<br>Department of Computer Science and Engineering=
<br>Sungkyunkwan University<br>Office: +82-31-299-4957<br>Email: <a href=3D=
"mailto:jaehoon.paul@gmail.com" target=3D"_blank">jaehoon.paul@gmail.com</a=
>,=C2=A0<a href=3D"mailto:pauljeong@skku.edu" style=3D"font-size:12.8px" ta=
rget=3D"_blank">pauljeong@skku.edu</a><br>Personal Homepage: <a href=3D"htt=
p://cpslab.skku.edu/people-jaehoon-jeong.php" target=3D"_blank">http://iotl=
ab.skku.edu/people-jaehoon-jeong.php</a><br></div></div></div></div></div><=
/div></div></div>

--000000000000b1dedb05b10bfad3--


From nobody Tue Oct  6 20:24:37 2020
Return-Path: <andy@yumaworks.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 3D45D3A15DF for <i2nsf@ietfa.amsl.com>; Tue,  6 Oct 2020 20:24:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.886
X-Spam-Level: 
X-Spam-Status: No, score=-1.886 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001, URI_DOTEDU=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=yumaworks-com.20150623.gappssmtp.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 bB-7o3hK4x3t for <i2nsf@ietfa.amsl.com>; Tue,  6 Oct 2020 20:24:32 -0700 (PDT)
Received: from mail-lf1-x132.google.com (mail-lf1-x132.google.com [IPv6:2a00:1450:4864:20::132]) (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 A4CCE3A15DA for <i2nsf@ietf.org>; Tue,  6 Oct 2020 20:24:31 -0700 (PDT)
Received: by mail-lf1-x132.google.com with SMTP id y11so617086lfl.5 for <i2nsf@ietf.org>; Tue, 06 Oct 2020 20:24:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yumaworks-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=TP1TvcFNzx2NMIFUASaOW7YIxoyja4WxjSVMDI1jASg=; b=lD26AeYjI5w1XAc9gKmXckl7cStbZPVc5tm5D8paBqIduFX6kVf1KXQr6s/oCPyjKW rbpMKsvBvCS8D2u3WuCPvYUxpIPvp0fvf8cXkTFOJE8uSmdZ5ATyadBm7QyKFruHimVA jC8Fn0ClNtO7x/Da1TZyLK7VFQufeFtQXoeSYyra4qqJyvUvqhgCe/JrvmGE4jnmzjS4 uZOfFnmGsZ+rBUwkiZ1wHR1FY0IL6mzeUby4O26OL0qCgLrEjMxDcLSK7ScMgGx1pztj /BVbjZ8KlkRMtKaAtObLGCqOmBXjWFimaK5+kbqmwQnGq+cBRXJHs4oFIL4VDJSo0Z57 CuLA==
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=TP1TvcFNzx2NMIFUASaOW7YIxoyja4WxjSVMDI1jASg=; b=Ddd51hSNGJcTWb7vN/wJr+VdTqGZ2wlTlVy2dw1RoTCuunnJs9XdI+a7MwG8pi/ccq iLnX4O4w6/QK4lGRQivh5D3yKA1zvZc2WUHnSsbzGHTOFtCt7bBHfoWvcuG6qX4WwYlX BoeBPNZ9yHTfzIFUEjRc92TrN0POvo+KwUx2s6ULc/24kElAoAYk0ygco91X5R3K7gMF fFzq+3aWRfANZWycS9ThfGfwlvjl3rIAHQLuUl8Kry4axciyfkCDo88je3G/e+SHjTG9 CvnJ2HGObug5oIWLUhKgVeFJZp8qoSGxU3fxnCsJzfbWwuIXWKNovu7ObIH49bjD98QN jMAQ==
X-Gm-Message-State: AOAM533XEXAq3pKqF8tPjoBV2eaIXmGdi6NHR54AR+Rk3Jh69P7xO3eT XNRzB1u7nHmUdPobvIOm+thnFB1z9HG3bdVf8NKqUw==
X-Google-Smtp-Source: ABdhPJwGPY6m4aze3YQLnIAqetkzYrN/++iA8yWnVDA/2uGx7SDvIcSDtz7OEf/+ch1MXxoy07fkiy/pyO6BfZRqyUg=
X-Received: by 2002:a19:6818:: with SMTP id d24mr240176lfc.107.1602041069549;  Tue, 06 Oct 2020 20:24:29 -0700 (PDT)
MIME-Version: 1.0
References: <160192102291.6633.15935674903085952087@ietfa.amsl.com> <CAPK2DewOF7QcTD8UdFYdoGUvnJz_fxb53OOn-KmYQgNA38xLoA@mail.gmail.com> <CABCOCHQsxFVNdBgL9fyZHV+Bevs1D8d5B=+KJAgoVBVekz+VtQ@mail.gmail.com> <CAPK2DewNDq2_DtZhtxitTsavHczwiSKur9+yQPLR+18UbV-QHg@mail.gmail.com> <CABCOCHT-0mKbYBDtZHnANRLqMtSsT1ijhoe1znoS2_pDHn4WNA@mail.gmail.com> <CAPK2Dexfpfgt730k5Zn3Aq34946Q5go4TuRrekA2hbbm_Wj_Jg@mail.gmail.com>
In-Reply-To: <CAPK2Dexfpfgt730k5Zn3Aq34946Q5go4TuRrekA2hbbm_Wj_Jg@mail.gmail.com>
From: Andy Bierman <andy@yumaworks.com>
Date: Tue, 6 Oct 2020 20:24:18 -0700
Message-ID: <CABCOCHQ3mCngcarHaL70KBEA4G7Wf4YSgf=UZTpYLESykn6Ckw@mail.gmail.com>
To: "Mr. Jaehoon Paul Jeong" <jaehoon.paul@gmail.com>
Cc: YANG Doctors <yang-doctors@ietf.org>, "i2nsf@ietf.org" <i2nsf@ietf.org>,  draft-ietf-i2nsf-nsf-monitoring-data-model.all@ietf.org,  Patrick Lingga <patricklink888@gmail.com>
Content-Type: multipart/alternative; boundary="000000000000ddd73205b10c407e"
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2nsf/DgiqTbEKLQx5Xw2lNLCdDOrndvo>
Subject: Re: [I2nsf] Yangdoctors early review of draft-ietf-i2nsf-nsf-monitoring-data-model-04
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: Wed, 07 Oct 2020 03:24:35 -0000

--000000000000ddd73205b10c407e
Content-Type: text/plain; charset="UTF-8"

On Tue, Oct 6, 2020 at 8:04 PM Mr. Jaehoon Paul Jeong <
jaehoon.paul@gmail.com> wrote:

> Hi Andy,
> I will investigate the event stream with information you sent me below.
>
>
The notification RFCs are a bit new.
An event stream is shared by all sessions that subscribe to that event
stream.
There is a default value that must be supported : "NETCONF"

You do not have to create a new event stream (e.g. "I2NSF")
You can use "NETCONF" if you want.
It is really up to the device vendor and operator to use proprietary
mechanisms
to configure the event streams.


Thanks for your help and advice.
>
> Best Regards,
> Paul
>

Andy


>
> On Tue, Oct 6, 2020 at 1:51 PM Andy Bierman <andy@yumaworks.com> wrote:
>
>>
>>
>> On Mon, Oct 5, 2020 at 9:05 PM Mr. Jaehoon Paul Jeong <
>> jaehoon.paul@gmail.com> wrote:
>>
>>> Andy,
>>> What do you mean by the event stream?
>>>
>>>
>> https://tools.ietf.org/html/rfc8639#section-2.1
>>
>>
>>
>>> Actually, I am thinking that the NETCONF can deliver the monitoring data
>>> of a system or an NSF in an XML file.
>>>
>>> Do you think that we need another way to convey the monitoring data?
>>>
>>> Thanks.
>>>
>>> Best Regards,
>>> Paul
>>>
>>> On Tue, Oct 6, 2020 at 12:30 PM Andy Bierman <andy@yumaworks.com> wrote:
>>>
>>>>
>>>>
>>>> On Mon, Oct 5, 2020 at 7:30 PM Mr. Jaehoon Paul Jeong <
>>>> jaehoon.paul@gmail.com> wrote:
>>>>
>>>>> Hi Andy,
>>>>> Thanks for your valuable comments on our NSF Monitoring YANG Data
>>>>> Model Draft.
>>>>> We authors will reflect your comments on the revision and come back to
>>>>> you with
>>>>> the revised draft and revision letter.
>>>>>
>>>>>
>>>> I forgot 1 comment:
>>>>
>>>>  - the draft is not that explicit about the event stream to use for
>>>> these notifications
>>>>    Perhaps a new standard event stream (I2NSF) would be better than the
>>>> standard (NETCONF)
>>>>    The draft should be more clear wrt/ the NETCONF stream.
>>>>
>>>>
>>>> Andy
>>>>
>>>>
>>>>
>>>>> Thanks.
>>>>>
>>>>> Best Regards,
>>>>> Paul
>>>>>
>>>>>
>>>>> On Tue, Oct 6, 2020 at 3:03 AM Andy Bierman via Datatracker <
>>>>> noreply@ietf.org> wrote:
>>>>>
>>>>>> Reviewer: Andy Bierman
>>>>>> Review result: Almost Ready
>>>>>>
>>>>>>
>>>>>>
>>>>>> Major Issues:
>>>>>>
>>>>>>  - None
>>>>>>
>>>>>> Moderate Issues:
>>>>>>
>>>>>>  - top-level 'counters' container does not follow naming conventions.
>>>>>>    Should start with 'i2nsf', probably 'i2nsf-state'
>>>>>>
>>>>>>  - There do not seem to be any writable objects in the /counters
>>>>>>    subtree so this container should have a 'config false' statement
>>>>>>
>>>>>>  - top-level typedef and grouping description-stmts are
>>>>>> self-referential
>>>>>>    and not useful. Need to rewrite description-stmts and/or add
>>>>>>    reference-stmts as needed.
>>>>>>
>>>>>>  - grouping common-monitoring-data/time-stamp
>>>>>>    Is this a different time stamp than the one in the NETCONF
>>>>>> notification?
>>>>>>    The 'message generation time' sounds like the standard timestamp.
>>>>>>    Does this object represent the event detection time?
>>>>>>
>>>>>>  - grouping i2nsf-system-alarm-type-content/usage
>>>>>>  - grouping i2nsf-system-alarm-type-content/threshold
>>>>>>    These are uint8 leafs with unclear descriptions.
>>>>>>    Not sure why uint8 is the appropriate type.
>>>>>>    Needs 1 or more of (reference, units, better description)
>>>>>>
>>>>>>  - grouping traffic-rates
>>>>>>    Add a units statement to each leaf. Not sure what units to use
>>>>>>    but it should be consistent. (e.g, pps, bps used in descriptions
>>>>>>    should also be in a units-stmt)
>>>>>>
>>>>>>  - grouping i2nsf-system-counter-type-content
>>>>>>    These counters should use the yang:counter32 type instead of uint32
>>>>>>
>>>>>>  - container counters/system-interface
>>>>>>  - container counters/nsf-firewall
>>>>>>  - container counters/nsf-policy-hits
>>>>>>   The descriptions are too terse and confusing, and need a rewrite.
>>>>>>
>>>>>>  -  container counters/nsf-firewall
>>>>>>  -  container counters/nsf-policy-hits
>>>>>>     - uses i2nsf-nsf-counters-type-content;
>>>>>>     Many of the fields expanded from this grouping all say
>>>>>>     they refer to 'the packet'. Why are they in this global
>>>>>>     container of counters? E.g. (src-ip, dst-ip, src-port, dst-port)
>>>>>>     Not clear at all how the server is supposed to apply this
>>>>>>     grouping to these containers.
>>>>>>
>>>>>>  - many leafs use "uint32" type for a rate.
>>>>>>    Should add a units-stmt
>>>>>>
>>>>>>  - leaf counters/nsf-policy-hits/hit-times
>>>>>>    The purpose and type are confusing and generic.
>>>>>>    If this is a counter then use counter32
>>>>>>
>>>>>>  - cut-and-paste for notification-stmt content should be replaced
>>>>>>    with grouping/uses instead. Applies to the nsf-detection-*
>>>>>>    and the various logging notifications. Even a grouping that
>>>>>>    has 1 object in it is better than cut-and-paste 5+ times
>>>>>>
>>>>>> Minor Issues:
>>>>>>
>>>>>>  - top-level identifiers are too generic
>>>>>>    should have 'i2nsf-' prefix to be more reusable outside this module
>>>>>>
>>>>>>  - quite a lot of identities that an implementation is required to
>>>>>> support.
>>>>>>    If this set of identities might change a lot faster than the
>>>>>>    notifications and counter objects, then consider putting them
>>>>>>    in a separate module
>>>>>>
>>>>>>  - leaf with same type named differently; both intrusion-attack-type
>>>>>>    - nsf-detection-intrusion/sub-attack-type
>>>>>>    - nsf-log-intrusion/attack-type
>>>>>>
>>>>>>  - quite a lot of notification event types for a server to implement
>>>>>>    and a user to manage. All are mandatory (no if-feature statements).
>>>>>>    Some such as nsf-detection-* subset are very similar.
>>>>>>    A section or table would be useful that showed the YANG
>>>>>> notification
>>>>>>    names and their purpose -- maybe a reference to another RFC
>>>>>>    with more details
>>>>>>
>>>>>>  - there seems to be notifications for intrusion events and then
>>>>>>    again for the logging of those events.  This seems excessive
>>>>>>    but
>>>>>>
>>>>>>
>>>>>>  - grouping common-monitoring-data/time-stamp
>>>>>>    Is this a different time stamp than the one in the NETCONF
>>>>>> notification?
>>>>>>    The 'message generation time' sounds like the standard timestamp.
>>>>>>    Is this event detection time?
>>>>>>
>>>>>>  - grouping common-monitoring-data/module-name
>>>>>>    Is this a YANG module or some other type of module?
>>>>>>
>>>>>>  - there is no way to configure which notifications should be
>>>>>> generated
>>>>>>    or maybe how often.  YANG Push has its own dampening-period.
>>>>>>    Since these are event stream subscriptions, not datastore
>>>>>> subscriptions,
>>>>>>    YANG-Push does not apply to this document at all.
>>>>>>
>>>>>>    If there are a lot of notifications then a server implementation
>>>>>>    might drop some
>>>>>>
>>>>>>  - grouping i2nsf-nsf-event-type-content-extend/src-zone
>>>>>>  - grouping i2nsf-nsf-event-type-content-extend/src-zone
>>>>>>    These use type 'string'. Consider using a typedef that constrains
>>>>>>    the string.  General comment where unconstrained string is used:
>>>>>>    The corner-case values such as empty string are often not allowed
>>>>>>    in implementations.
>>>>>>
>>>>>>
>>>>>>  - grouping i2nsf-nsf-event-type-content-extend/rule-id
>>>>>>  - grouping i2nsf-nsf-event-type-content-extend/rule-name
>>>>>>  - grouping i2nsf-nsf-event-type-content-extend/profile
>>>>>>    These objects seem to reference objects in another YANG module.
>>>>>>    If so, then leafref types might be more appropriate.
>>>>>>
>>>>>>  - grouping i2nsf-nsf-event-type-content/rule-id
>>>>>>  - grouping i2nsf-nsf-event-type-content/rule-name
>>>>>>  - grouping i2nsf-nsf-event-type-content/profile
>>>>>>  - grouping i2nsf-nsf-event-type-content/raw-info
>>>>>>    These objects are cut-and-paste duplicates from
>>>>>>    grouping i2nsf-nsf-event-type-content. They should
>>>>>>    be in a separate grouping used by both. Also applies
>>>>>>    to some other sets of objects
>>>>>>
>>>>>>  - limits issues (e.g. current-session, maximum-session
>>>>>>    The type is uint8. This is only OK it is impossible for any
>>>>>>    implementation to ever have or want more than 255 of them.
>>>>>>    If some other RFC really does limit the values where uint8
>>>>>>    is used, then that is OK. If so, a reference-stmt would help.
>>>>>>
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> I2nsf mailing list
>>>>>> I2nsf@ietf.org
>>>>>> https://www.ietf.org/mailman/listinfo/i2nsf
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> ===========================
>>>>> Mr. Jaehoon (Paul) Jeong, Ph.D.
>>>>> Associate Professor
>>>>> Department of Computer Science and Engineering
>>>>> Sungkyunkwan University
>>>>> Office: +82-31-299-4957
>>>>> Email: jaehoon.paul@gmail.com, pauljeong@skku.edu
>>>>> Personal Homepage: http://iotlab.skku.edu/people-jaehoon-jeong.php
>>>>> <http://cpslab.skku.edu/people-jaehoon-jeong.php>
>>>>>
>>>>
>>>
>>> --
>>> ===========================
>>> Mr. Jaehoon (Paul) Jeong, Ph.D.
>>> Associate Professor
>>> Department of Computer Science and Engineering
>>> Sungkyunkwan University
>>> Office: +82-31-299-4957
>>> Email: jaehoon.paul@gmail.com, pauljeong@skku.edu
>>> Personal Homepage: http://iotlab.skku.edu/people-jaehoon-jeong.php
>>> <http://cpslab.skku.edu/people-jaehoon-jeong.php>
>>>
>>
>
> --
> ===========================
> Mr. Jaehoon (Paul) Jeong, Ph.D.
> Associate Professor
> Department of Computer Science and Engineering
> Sungkyunkwan University
> Office: +82-31-299-4957
> Email: jaehoon.paul@gmail.com, pauljeong@skku.edu
> Personal Homepage: http://iotlab.skku.edu/people-jaehoon-jeong.php
> <http://cpslab.skku.edu/people-jaehoon-jeong.php>
>

--000000000000ddd73205b10c407e
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><br></div><br><div class=3D"gmail_quote">=
<div dir=3D"ltr" class=3D"gmail_attr">On Tue, Oct 6, 2020 at 8:04 PM Mr. Ja=
ehoon Paul Jeong &lt;<a href=3D"mailto:jaehoon.paul@gmail.com">jaehoon.paul=
@gmail.com</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=
=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding=
-left:1ex"><div dir=3D"ltr">Hi Andy,<div>I will investigate the event strea=
m with information you sent me below.</div><div><br></div></div></blockquot=
e><div><br></div><div>The notification RFCs are a bit new.</div><div>An eve=
nt stream is shared by all sessions that subscribe to that event stream.</d=
iv><div>There is a default value that must be supported : &quot;NETCONF&quo=
t;<br></div><div><br></div><div>You do not have to create a new event strea=
m (e.g. &quot;I2NSF&quot;)</div><div>You can use &quot;NETCONF&quot; if you=
 want.</div><div>It is really up to the device vendor and operator to use p=
roprietary mechanisms</div><div>to configure the event streams.</div><div><=
br></div><div><br></div><blockquote class=3D"gmail_quote" style=3D"margin:0=
px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><=
div dir=3D"ltr"><div></div><div>Thanks for your=C2=A0help=C2=A0and advice.<=
/div><div><br></div><div>Best Regards,</div><div>Paul</div></div></blockquo=
te><div><br></div><div>Andy</div><div>=C2=A0</div><blockquote class=3D"gmai=
l_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,20=
4,204);padding-left:1ex"><br><div class=3D"gmail_quote"><div dir=3D"ltr" cl=
ass=3D"gmail_attr">On Tue, Oct 6, 2020 at 1:51 PM Andy Bierman &lt;<a href=
=3D"mailto:andy@yumaworks.com" target=3D"_blank">andy@yumaworks.com</a>&gt;=
 wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px =
0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir=
=3D"ltr"><div dir=3D"ltr"><br></div><br><div class=3D"gmail_quote"><div dir=
=3D"ltr" class=3D"gmail_attr">On Mon, Oct 5, 2020 at 9:05 PM Mr. Jaehoon Pa=
ul Jeong &lt;<a href=3D"mailto:jaehoon.paul@gmail.com" target=3D"_blank">ja=
ehoon.paul@gmail.com</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quo=
te" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204=
);padding-left:1ex"><div dir=3D"ltr">Andy,<div>What do you mean by the even=
t stream?</div><div><br></div></div></blockquote><div><br></div><div><a hre=
f=3D"https://tools.ietf.org/html/rfc8639#section-2.1" target=3D"_blank">htt=
ps://tools.ietf.org/html/rfc8639#section-2.1</a></div><div><br></div><div>=
=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0=
.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir=3D"l=
tr"><div></div><div>Actually, I am thinking that the NETCONF can deliver th=
e monitoring data of a system or an NSF in an XML file.</div><div><br></div=
><div>Do you think that we need another way to convey the monitoring data?<=
/div><div><br></div><div>Thanks.</div><div><br></div><div>Best Regards,</di=
v><div>Paul</div></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" clas=
s=3D"gmail_attr">On Tue, Oct 6, 2020 at 12:30 PM Andy Bierman &lt;<a href=
=3D"mailto:andy@yumaworks.com" target=3D"_blank">andy@yumaworks.com</a>&gt;=
 wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px =
0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir=
=3D"ltr"><div dir=3D"ltr"><br></div><br><div class=3D"gmail_quote"><div dir=
=3D"ltr" class=3D"gmail_attr">On Mon, Oct 5, 2020 at 7:30 PM Mr. Jaehoon Pa=
ul Jeong &lt;<a href=3D"mailto:jaehoon.paul@gmail.com" target=3D"_blank">ja=
ehoon.paul@gmail.com</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quo=
te" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204=
);padding-left:1ex"><div dir=3D"ltr">Hi Andy,<div>Thanks for your valuable =
comments on our NSF Monitoring YANG Data Model Draft.</div><div>We authors =
will reflect your comments on the revision and come back to you with</div><=
div>the revised draft and revision letter.</div><div><br></div></div></bloc=
kquote><div><br></div><div>I forgot 1 comment:</div><div><br></div><div>=C2=
=A0- the draft is not that explicit about the event stream to use for these=
 notifications</div><div>=C2=A0 =C2=A0Perhaps a new standard event stream (=
I2NSF) would be better than the standard (NETCONF)</div><div>=C2=A0 =C2=A0T=
he draft should be more clear wrt/ the NETCONF stream.</div><div><br></div>=
<div><br></div><div>Andy</div><div><br></div><div>=C2=A0=C2=A0</div><blockq=
uote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1p=
x solid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr"><div></div><div=
>Thanks.</div><div><br></div><div>Best Regards,</div><div>Paul</div><div><b=
r></div></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmai=
l_attr">On Tue, Oct 6, 2020 at 3:03 AM Andy Bierman via Datatracker &lt;<a =
href=3D"mailto:noreply@ietf.org" target=3D"_blank">noreply@ietf.org</a>&gt;=
 wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px =
0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Reviewer=
: Andy Bierman<br>
Review result: Almost Ready<br>
<br>
<br>
<br>
Major Issues:<br>
<br>
=C2=A0- None<br>
<br>
Moderate Issues:<br>
<br>
=C2=A0- top-level &#39;counters&#39; container does not follow naming conve=
ntions.<br>
=C2=A0 =C2=A0Should start with &#39;i2nsf&#39;, probably &#39;i2nsf-state&#=
39;<br>
<br>
=C2=A0- There do not seem to be any writable objects in the /counters<br>
=C2=A0 =C2=A0subtree so this container should have a &#39;config false&#39;=
 statement<br>
<br>
=C2=A0- top-level typedef and grouping description-stmts are self-referenti=
al<br>
=C2=A0 =C2=A0and not useful. Need to rewrite description-stmts and/or add<b=
r>
=C2=A0 =C2=A0reference-stmts as needed.<br>
<br>
=C2=A0- grouping common-monitoring-data/time-stamp<br>
=C2=A0 =C2=A0Is this a different time stamp than the one in the NETCONF not=
ification?<br>
=C2=A0 =C2=A0The &#39;message generation time&#39; sounds like the standard=
 timestamp.<br>
=C2=A0 =C2=A0Does this object represent the event detection time?<br>
<br>
=C2=A0- grouping i2nsf-system-alarm-type-content/usage<br>
=C2=A0- grouping i2nsf-system-alarm-type-content/threshold<br>
=C2=A0 =C2=A0These are uint8 leafs with unclear descriptions.<br>
=C2=A0 =C2=A0Not sure why uint8 is the appropriate type.<br>
=C2=A0 =C2=A0Needs 1 or more of (reference, units, better description)<br>
<br>
=C2=A0- grouping traffic-rates<br>
=C2=A0 =C2=A0Add a units statement to each leaf. Not sure what units to use=
<br>
=C2=A0 =C2=A0but it should be consistent. (e.g, pps, bps used in descriptio=
ns<br>
=C2=A0 =C2=A0should also be in a units-stmt)<br>
<br>
=C2=A0- grouping i2nsf-system-counter-type-content<br>
=C2=A0 =C2=A0These counters should use the yang:counter32 type instead of u=
int32<br>
<br>
=C2=A0- container counters/system-interface<br>
=C2=A0- container counters/nsf-firewall<br>
=C2=A0- container counters/nsf-policy-hits<br>
=C2=A0 The descriptions are too terse and confusing, and need a rewrite.<br=
>
<br>
=C2=A0-=C2=A0 container counters/nsf-firewall<br>
=C2=A0-=C2=A0 container counters/nsf-policy-hits<br>
=C2=A0 =C2=A0 - uses i2nsf-nsf-counters-type-content;<br>
=C2=A0 =C2=A0 Many of the fields expanded from this grouping all say<br>
=C2=A0 =C2=A0 they refer to &#39;the packet&#39;. Why are they in this glob=
al<br>
=C2=A0 =C2=A0 container of counters? E.g. (src-ip, dst-ip, src-port, dst-po=
rt)<br>
=C2=A0 =C2=A0 Not clear at all how the server is supposed to apply this<br>
=C2=A0 =C2=A0 grouping to these containers.<br>
<br>
=C2=A0- many leafs use &quot;uint32&quot; type for a rate.<br>
=C2=A0 =C2=A0Should add a units-stmt<br>
<br>
=C2=A0- leaf counters/nsf-policy-hits/hit-times<br>
=C2=A0 =C2=A0The purpose and type are confusing and generic.<br>
=C2=A0 =C2=A0If this is a counter then use counter32<br>
<br>
=C2=A0- cut-and-paste for notification-stmt content should be replaced<br>
=C2=A0 =C2=A0with grouping/uses instead. Applies to the nsf-detection-*<br>
=C2=A0 =C2=A0and the various logging notifications. Even a grouping that<br=
>
=C2=A0 =C2=A0has 1 object in it is better than cut-and-paste 5+ times<br>
<br>
Minor Issues:<br>
<br>
=C2=A0- top-level identifiers are too generic<br>
=C2=A0 =C2=A0should have &#39;i2nsf-&#39; prefix to be more reusable outsid=
e this module<br>
<br>
=C2=A0- quite a lot of identities that an implementation is required to sup=
port.<br>
=C2=A0 =C2=A0If this set of identities might change a lot faster than the<b=
r>
=C2=A0 =C2=A0notifications and counter objects, then consider putting them<=
br>
=C2=A0 =C2=A0in a separate module<br>
<br>
=C2=A0- leaf with same type named differently; both intrusion-attack-type<b=
r>
=C2=A0 =C2=A0- nsf-detection-intrusion/sub-attack-type<br>
=C2=A0 =C2=A0- nsf-log-intrusion/attack-type<br>
<br>
=C2=A0- quite a lot of notification event types for a server to implement<b=
r>
=C2=A0 =C2=A0and a user to manage. All are mandatory (no if-feature stateme=
nts).<br>
=C2=A0 =C2=A0Some such as nsf-detection-* subset are very similar.<br>
=C2=A0 =C2=A0A section or table would be useful that showed the YANG notifi=
cation<br>
=C2=A0 =C2=A0names and their purpose -- maybe a reference to another RFC<br=
>
=C2=A0 =C2=A0with more details<br>
<br>
=C2=A0- there seems to be notifications for intrusion events and then<br>
=C2=A0 =C2=A0again for the logging of those events.=C2=A0 This seems excess=
ive<br>
=C2=A0 =C2=A0but<br>
<br>
<br>
=C2=A0- grouping common-monitoring-data/time-stamp<br>
=C2=A0 =C2=A0Is this a different time stamp than the one in the NETCONF not=
ification?<br>
=C2=A0 =C2=A0The &#39;message generation time&#39; sounds like the standard=
 timestamp.<br>
=C2=A0 =C2=A0Is this event detection time?<br>
<br>
=C2=A0- grouping common-monitoring-data/module-name<br>
=C2=A0 =C2=A0Is this a YANG module or some other type of module?<br>
<br>
=C2=A0- there is no way to configure which notifications should be generate=
d<br>
=C2=A0 =C2=A0or maybe how often.=C2=A0 YANG Push has its own dampening-peri=
od.<br>
=C2=A0 =C2=A0Since these are event stream subscriptions, not datastore subs=
criptions,<br>
=C2=A0 =C2=A0YANG-Push does not apply to this document at all.<br>
<br>
=C2=A0 =C2=A0If there are a lot of notifications then a server implementati=
on<br>
=C2=A0 =C2=A0might drop some<br>
<br>
=C2=A0- grouping i2nsf-nsf-event-type-content-extend/src-zone<br>
=C2=A0- grouping i2nsf-nsf-event-type-content-extend/src-zone<br>
=C2=A0 =C2=A0These use type &#39;string&#39;. Consider using a typedef that=
 constrains<br>
=C2=A0 =C2=A0the string.=C2=A0 General comment where unconstrained string i=
s used:<br>
=C2=A0 =C2=A0The corner-case values such as empty string are often not allo=
wed<br>
=C2=A0 =C2=A0in implementations.<br>
<br>
<br>
=C2=A0- grouping i2nsf-nsf-event-type-content-extend/rule-id<br>
=C2=A0- grouping i2nsf-nsf-event-type-content-extend/rule-name<br>
=C2=A0- grouping i2nsf-nsf-event-type-content-extend/profile<br>
=C2=A0 =C2=A0These objects seem to reference objects in another YANG module=
.<br>
=C2=A0 =C2=A0If so, then leafref types might be more appropriate.<br>
<br>
=C2=A0- grouping i2nsf-nsf-event-type-content/rule-id<br>
=C2=A0- grouping i2nsf-nsf-event-type-content/rule-name<br>
=C2=A0- grouping i2nsf-nsf-event-type-content/profile<br>
=C2=A0- grouping i2nsf-nsf-event-type-content/raw-info<br>
=C2=A0 =C2=A0These objects are cut-and-paste duplicates from<br>
=C2=A0 =C2=A0grouping i2nsf-nsf-event-type-content. They should<br>
=C2=A0 =C2=A0be in a separate grouping used by both. Also applies<br>
=C2=A0 =C2=A0to some other sets of objects<br>
<br>
=C2=A0- limits issues (e.g. current-session, maximum-session<br>
=C2=A0 =C2=A0The type is uint8. This is only OK it is impossible for any<br=
>
=C2=A0 =C2=A0implementation to ever have or want more than 255 of them.<br>
=C2=A0 =C2=A0If some other RFC really does limit the values where uint8<br>
=C2=A0 =C2=A0is used, then that is OK. If so, a reference-stmt would help.<=
br>
<br>
<br>
<br>
_______________________________________________<br>
I2nsf mailing list<br>
<a href=3D"mailto:I2nsf@ietf.org" target=3D"_blank">I2nsf@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/i2nsf" rel=3D"noreferrer" =
target=3D"_blank">https://www.ietf.org/mailman/listinfo/i2nsf</a><br>
</blockquote></div><br clear=3D"all"><div><br></div>-- <br><div dir=3D"ltr"=
><div dir=3D"ltr"><div><div dir=3D"ltr"><div><div dir=3D"ltr"><div><div dir=
=3D"ltr">=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D<br>Mr. Jaehoon (Paul) Jeong, Ph.D.<br>Associate Professor<b=
r>Department of Computer Science and Engineering<br>Sungkyunkwan University=
<br>Office: +82-31-299-4957<br>Email: <a href=3D"mailto:jaehoon.paul@gmail.=
com" target=3D"_blank">jaehoon.paul@gmail.com</a>,=C2=A0<a href=3D"mailto:p=
auljeong@skku.edu" style=3D"font-size:12.8px" target=3D"_blank">pauljeong@s=
kku.edu</a><br>Personal Homepage: <a href=3D"http://cpslab.skku.edu/people-=
jaehoon-jeong.php" target=3D"_blank">http://iotlab.skku.edu/people-jaehoon-=
jeong.php</a><br></div></div></div></div></div></div></div></div>
</blockquote></div></div>
</blockquote></div><br clear=3D"all"><div><br></div>-- <br><div dir=3D"ltr"=
><div dir=3D"ltr"><div><div dir=3D"ltr"><div><div dir=3D"ltr"><div><div dir=
=3D"ltr">=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D<br>Mr. Jaehoon (Paul) Jeong, Ph.D.<br>Associate Professor<b=
r>Department of Computer Science and Engineering<br>Sungkyunkwan University=
<br>Office: +82-31-299-4957<br>Email: <a href=3D"mailto:jaehoon.paul@gmail.=
com" target=3D"_blank">jaehoon.paul@gmail.com</a>,=C2=A0<a href=3D"mailto:p=
auljeong@skku.edu" style=3D"font-size:12.8px" target=3D"_blank">pauljeong@s=
kku.edu</a><br>Personal Homepage: <a href=3D"http://cpslab.skku.edu/people-=
jaehoon-jeong.php" target=3D"_blank">http://iotlab.skku.edu/people-jaehoon-=
jeong.php</a><br></div></div></div></div></div></div></div></div>
</blockquote></div></div>
</blockquote></div><br clear=3D"all"><div><br></div>-- <br><div dir=3D"ltr"=
><div dir=3D"ltr"><div><div dir=3D"ltr"><div><div dir=3D"ltr"><div><div dir=
=3D"ltr">=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D<br>Mr. Jaehoon (Paul) Jeong, Ph.D.<br>Associate Professor<b=
r>Department of Computer Science and Engineering<br>Sungkyunkwan University=
<br>Office: +82-31-299-4957<br>Email: <a href=3D"mailto:jaehoon.paul@gmail.=
com" target=3D"_blank">jaehoon.paul@gmail.com</a>,=C2=A0<a href=3D"mailto:p=
auljeong@skku.edu" style=3D"font-size:12.8px" target=3D"_blank">pauljeong@s=
kku.edu</a><br>Personal Homepage: <a href=3D"http://cpslab.skku.edu/people-=
jaehoon-jeong.php" target=3D"_blank">http://iotlab.skku.edu/people-jaehoon-=
jeong.php</a><br></div></div></div></div></div></div></div></div>
</blockquote></div></div>

--000000000000ddd73205b10c407e--


From nobody Thu Oct  8 14:35:51 2020
Return-Path: <linda.dunbar@futurewei.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 EB3F83A0E4B for <i2nsf@ietfa.amsl.com>; Thu,  8 Oct 2020 14:35:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.352
X-Spam-Level: 
X-Spam-Status: No, score=0.352 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, LH_URI_DOM_IN_PATH=2.331, RCVD_IN_MSPIKE_H2=-0.001, T_FILL_THIS_FORM_SHORT=0.01, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=futurewei.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 HxuDfEFeveav for <i2nsf@ietfa.amsl.com>; Thu,  8 Oct 2020 14:35:46 -0700 (PDT)
Received: from NAM04-SN1-obe.outbound.protection.outlook.com (mail-eopbgr700106.outbound.protection.outlook.com [40.107.70.106]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2B4A03A0E3B for <i2nsf@ietf.org>; Thu,  8 Oct 2020 14:35:45 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=Y/Jm93LOktpCfWKlSgAYuvJ7G3Muj2JnlKxUUUGwOF98+YdczgqMs74eI2r7TguYZovB6PtwlP5CajMEqnnw/9Yc66EjKSDuyxnT/pCLW+kVtCCIBrfkdejBPe49R3XBQ3hVo5lor9BLn4X1dOZj5hf+hCBE89jREc6wSnTPfU7XVVkEhLtVyVaaUzPu/uctdwIZ65oghuiRWxAuSWFaRKo0M/WVRmUWOKRaSf6MXXtIr8QPqBMGyBfXLkWlusX/+Gxtw6sUn5qUw57ijzi3PlsUWMGuBj7ILAm41xRvuSDXa+UxroJSlqV+q949F26gFAk+jEbstX4OmWVJYzUbHg==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=2r1DghCKXjgm/rQYkH9T/1+9YvfHq2hqMF7kiKZKVsQ=; b=LQnwlAM4ZDixUFfTDQiyCz+yC2iD1RN5QoykcSSKDIib3pl23g4a+O0LisXYBEA8IkHqRER1D3ZLzwurYTw+s3ejswsITPujy1OolRlnMPyGJHcsoXHuvvARAwSNkP3dExTDnRaU9juh/kelMnpnG5NaHytZDtFEKU+x8QtCRnxF0XhnAqvXyjbCgPXKnMAq3VxgWx2G6IOI0RkRI8BhZj13Ie88PJF8OOjWjUzLIQVut55XSrPy7Gxi7jnWZSI1s1hY/9z2t/DapbOy2buUHwuy47aykqBRaz0pFbG3rQ9CGZYNWkPpCUQgyVlAx5g0TM+b6npwU21CJx5Oul9Dxg==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=futurewei.com; dmarc=pass action=none header.from=futurewei.com; dkim=pass header.d=futurewei.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=Futurewei.com; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=2r1DghCKXjgm/rQYkH9T/1+9YvfHq2hqMF7kiKZKVsQ=; b=SjV8vXs2+XFMihXtkMdl4ZGbUm2ax/XEXSS5HcszVkdW0v0iw96UN6WPaRdFXD4EJoj94SSVBK70+qXVOZslkkJSwpKUuKQJMlawNWXXV5uTh4D6L7VJ3Mztiq7amEAE4b1uKSe+QgSBrubfexIQb8j4V6Ra2md9MNL2mtqUPy4=
Received: from SN6PR13MB2334.namprd13.prod.outlook.com (2603:10b6:805:55::16) by SN6PR13MB2527.namprd13.prod.outlook.com (2603:10b6:805:58::12) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3477.11; Thu, 8 Oct 2020 21:35:42 +0000
Received: from SN6PR13MB2334.namprd13.prod.outlook.com ([fe80::8c05:b4f5:cc16:eeb]) by SN6PR13MB2334.namprd13.prod.outlook.com ([fe80::8c05:b4f5:cc16:eeb%7]) with mapi id 15.20.3477.011; Thu, 8 Oct 2020 21:35:42 +0000
From: Linda Dunbar <linda.dunbar@futurewei.com>
To: "i2nsf@ietf.org" <i2nsf@ietf.org>
Thread-Topic: 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? 
Thread-Index: Adaduvh8zkKOxDGwSr68F8vVxkzqSw==
Date: Thu, 8 Oct 2020 21:35:42 +0000
Message-ID: <SN6PR13MB23343DE9392FA9EDDDA65651850B0@SN6PR13MB2334.namprd13.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=none action=none header.from=futurewei.com;
x-originating-ip: [72.180.73.64]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: e2971f23-1293-4987-65ff-08d86bd21bd9
x-ms-traffictypediagnostic: SN6PR13MB2527:
x-microsoft-antispam-prvs: <SN6PR13MB2527D5102CF135BE06ADF6B5850B0@SN6PR13MB2527.namprd13.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: MyoOc9grfCru4tcXevo5jpvaB7UjyuSfSEDl3DSgHCnaramIlMzvdSzQjNg9uejS2HFjIdWtVP8kjTTg8WHP7WNjFpQ3u/lux1mEB9OrmBdewyJBcqdl0foFaijzxjnJQ6tu5e4+M2rWlAc7+cSg5HJWHfhfDJqZ5jg7cP2I17YrhmN+Fug2zyEad04qaaXR9m0n6BqAtlNsjBlGN5hPNaBY5Gm/9uwLHLj9UtIash7OCZXVZ5A35HaCiXvm3kLRCJoy5cqNzqA+lkrDo/kQj+io9ComyH+Suhi86KaaDMPnBvW+lvJfawJS6dIxMTt1tMDILAVrZzGaPnj+o2yufy72aYDXhZWMwO5coxg7BH9E1PsnhBoxzamvGsDdpOVDvGBH5toAWa0BRLXQ2jzyjPYVSkDnUGdjgJm/K+f7YVep/LESXtsP3k9q4OJM31cEWp6bsOMrQUDFZZ75HnEETA==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;  IPV:NLI; SFV:NSPM; H:SN6PR13MB2334.namprd13.prod.outlook.com; PTR:; CAT:NONE;  SFS:(4636009)(366004)(396003)(376002)(39840400004)(346002)(136003)(45080400002)(30864003)(55016002)(7696005)(4743002)(8676002)(83080400001)(83730400001)(6916009)(66574015)(166002)(33656002)(52536014)(26005)(2906002)(83380400001)(71200400001)(5660300002)(316002)(44832011)(53546011)(66946007)(76116006)(86362001)(66476007)(64756008)(966005)(66556008)(8936002)(6506007)(66446008)(9686003)(478600001)(186003)(219693003); DIR:OUT; SFP:1102; 
x-ms-exchange-antispam-messagedata: 14NTmpFdcU+BzdKx6dbZvbbMVTp4QPMkAdrLhPsn2MoDdHzxtWA5xgHcAwCpmbBhadbINKvpdRW7EdLAoIgJLh+biGtv2raBUBTpf9DAjd/1Gq83QD62JHrYz5Njgee8wN+Tiv4fpnfoNNT3FvX0QHam97+pVukLICDfUoNNREdUDrjYqKpa0pgHZHiV14VGJeHgZEwio1N3TI02DRcuhbDAGNGGFBHmsft9dPuvGetAY8ZcIwCu/4KhRw4VBYTiM+11/YE6jerN9GcU+0DtbNOqXn5tIXgFjr4HZ79pFweiOPczsacY7uXDxuZF3ZFtswBKcS/+EqZXWTnXtzTVniX+V95eQS8fMtiwHkeWhFyyREU/V35U7ah8e4InC3iCB9/NY1h6Z/4bDphtEFObENZE4VPk5ERX+Q52Ivn2cA3qI/WRcB1ZNn+PJ0nj6Oa6sdSL9Tk1NZwfiJB2QTHVRf5V5ucJ+WTbb40JYYDiF5Mt7aObtJptga9wwAcvWUKoSVy45LkeZ2mCab5TLzndiu5DEJIs7oquPAcgesQUAKp4OekHxom8TlUDNRfFRL1eDSQE5eUNa09ZXp7Ri5Hcvx1XoKuzQt3bupD5NOIiPsWC+BTM8Yp13Z5qynOqfIqY8Stf3gKbp7LE+utFwmOOQQ==
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_SN6PR13MB23343DE9392FA9EDDDA65651850B0SN6PR13MB2334namp_"
MIME-Version: 1.0
X-OriginatorOrg: Futurewei.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: SN6PR13MB2334.namprd13.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: e2971f23-1293-4987-65ff-08d86bd21bd9
X-MS-Exchange-CrossTenant-originalarrivaltime: 08 Oct 2020 21:35:42.6212 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 0fee8ff2-a3b2-4018-9c75-3a1d5591fedc
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: D0SKM8MHH493LRDiauUCZfCGeh88KWk/nEUOoFsva5fdGZHqfYEPCyq4BoKcX+NqmNo/1ZkpPR1iykBeZgIlHw==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: SN6PR13MB2527
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2nsf/J-Ooh3ksYpEYBBLdI3NqPW0ufC8>
Subject: [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: Thu, 08 Oct 2020 21:35:49 -0000

--_000_SN6PR13MB23343DE9392FA9EDDDA65651850B0SN6PR13MB2334namp_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

STJuc2YgV0csDQoNClRoZXJlIGhhcyBiZWVuIGFueSBvYmplY3Rpb24gdG8gdGhlIEF1dGhvcuKA
mXMgcmVxdWVzdCBmb3Igc3Vuc2V0dGluZyB0aGUgIGRyYWZ0LWlldGYtaTJuc2YtY2FwYWJpbGl0
eS0wNS4NCg0KQXV0aG9ycyBvZiB0aGUgZHJhZnQtaWV0Zi1pMm5zZi1jYXBhYmlsaXR5LWRhdGEt
bW9kZWw6IHBsZWFzZSByZW1vdmUgdGhlIHJlZmVyZW5jZSB0byB0aGUgQ2FwYWJpbGl0eSBJbmZv
cm1hdGlvbiBNb2RlbCBhbmQgdXBsb2FkIGEgbmV3IGRyYWZ0LiBXZSBjYW4gYXNrIElFU0cgdG8g
cmUtcmV2aWV3IGl0Lg0KDQpUaGFuayB5b3UgdmVyeSBtdWNoLg0KDQpMaW5kYSAmIFlvYXYuDQoN
CkZyb206IExpbmRhIER1bmJhcg0KU2VudDogTW9uZGF5LCBTZXB0ZW1iZXIgMjgsIDIwMjAgMTE6
MDAgQU0NClRvOiBpMm5zZkBpZXRmLm9yZw0KU3ViamVjdDogSXMgdGhlcmUgYW55IG9iamVjdGlv
biBvZiBzdW5zZXQgdGhlIEkyTlNGIENhcGFiaWxpdGllcyBJbmZvcm1hdGlvbiBNb2RlbCBEcmFm
dCBhbmQgbWVyZ2UgdGhlIHJlbGV2YW50IGluZm9ybWF0aW9uIHRvIHRoZSBJMk5TRiBDYXBhYmls
aXR5IERhdGEgbW9kZWwgZHJhZnQ/DQoNCkkyTlNGIFdHLA0KDQpBcyBEaWVnbyBoYXMgZXhwcmVz
c2VkIHRoYXQgdGhlIG9yaWdpbmFsIEkyTlNGIGNhcGFiaWxpdHkgaW5mb3JtYXRpb24gbW9kZWwg
d2FzIGJhc2VkIG9uIGEgcG9saWN5IGV4cHJlc3Npb24gY2FsY3VsdXMgc3VpdGFibGUgZm9yIG1h
bmlwdWxhdGluZyBoaWdoLWxldmVsIHBvbGljeSBleHByZXNzaW9ucy4gIFRoZSBjYXBhYmlsaXR5
IGRhdGEgbW9kZWwgaGFzIGJlZW4gZXZvbHZpbmcgaW4gYSBxdWl0ZSByZWFzb25hYmxlIGFuZCBw
cmFnbWF0aWMgd2F5LCBpbmNsdWRpbmcgcnVubmluZyBjb2RlIGF0IHRoZSBoYWNrYXRob25zLg0K
DQpUaGUgSTJOU0YgQ2FwYWJpbGl0eSBJbmZvcm1hdGlvbiBNb2RlbCBoYXMgZnVsZmlsbGVkIGl0
cyBwdXJwb3NlIG9mIGtpY2tzdGFydGluZyBhbmQgZ3VpZGluZyB0aGUgZGF0YSBtb2RlbCwgYW5k
IHRoZSBhdXRob3JzIGJlbGlldmUgdGhhdCBpdCBpcyBiZXR0ZXIgdG8gbGV0IHRoZSBjYXBhYmls
aXR5IGluZm9ybWF0aW9uIG1vZGVsIHRvIGJlIHdpdGhkcmF3bi4gRm9yIHRoZSBjb250ZW50IGlu
IHRoZSBpbmZvcm1hdGlvbiBtb2RlbCBzdGlsbCByZWxldmFudCB0byBJMk5TRiBDYXBhYmlsaXR5
IERhdGEgTW9kZWwsIHRoZXkgc2hvdWxkIGJlIG1lcmdlZCBpbnRvIHRoZSBDYXBhYmlsaXR5IERh
dGEgTW9kZWwuDQoNCklzIHRoZXJlIGFueSBvYmplY3Rpb24gZnJvbSB0aGUgV0c/ICBJZiB3ZSBk
b27igJl0IGhlYXIgYW55IG9iamVjdGlvbiBieSBPY3QgNSwgd2Ugd2lsbCBjaGFuZ2UgdGhlIHN0
YXR1cyBvZiB0aGUgZHJhZnQuDQoNCkNoZWVycywNCg0KTGluZGEgJiBZb2F2DQoNCg0KDQpGcm9t
OiBEaWVnbyBSLiBMb3BleiA8ZGllZ28uci5sb3BlekB0ZWxlZm9uaWNhLmNvbTxtYWlsdG86ZGll
Z28uci5sb3BlekB0ZWxlZm9uaWNhLmNvbT4+DQpTZW50OiBUdWVzZGF5LCBTZXB0ZW1iZXIgMjIs
IDIwMjAgNTozNSBQTQ0KVG86IExpbmRhIER1bmJhciA8bGluZGEuZHVuYmFyQGZ1dHVyZXdlaS5j
b208bWFpbHRvOmxpbmRhLmR1bmJhckBmdXR1cmV3ZWkuY29tPj47IE1yLiBKYWVob29uIFBhdWwg
SmVvbmcgPGphZWhvb24ucGF1bEBnbWFpbC5jb208bWFpbHRvOmphZWhvb24ucGF1bEBnbWFpbC5j
b20+Pg0KQ2M6IFhpYWxpYW5nIChGcmFuaykgPGZyYW5rLnhpYWxpYW5nQGh1YXdlaS5jb208bWFp
bHRvOmZyYW5rLnhpYWxpYW5nQGh1YXdlaS5jb20+PjsgWW9hdiBOaXIgPHluaXIuaWV0ZkBnbWFp
bC5jb208bWFpbHRvOnluaXIuaWV0ZkBnbWFpbC5jb20+PjsgSm9obiBTdHJhc3NuZXIgPEpvaG4u
c2MuU3RyYXNzbmVyQGh1YXdlaS5jb208bWFpbHRvOkpvaG4uc2MuU3RyYXNzbmVyQGh1YXdlaS5j
b20+PjsgQWxkbyBCYXNpbGUgPGNhdGFsZG8uYmFzaWxlQHBvbGl0by5pdDxtYWlsdG86Y2F0YWxk
by5iYXNpbGVAcG9saXRvLml0Pj47IFJvbWFuIERhbnlsaXcgPHJkZEBjZXJ0Lm9yZzxtYWlsdG86
cmRkQGNlcnQub3JnPj4NClN1YmplY3Q6IFJlOiBPZmZlciBmb3IgUmV2aXNpb24gSGVscCBmb3Ig
STJOU0YgTlNGcyBDYXBhYmlsaXRpZXMgSW5mb3JtYXRpb24gTW9kZWwgRHJhZnQNCg0KSGkgTGlu
ZGEsDQoNCknigJlkIHByZWZlciB0aGUgc2Vjb25kIG9wdGlvbiwgYXMgaXQgc2VlbXMgbW9yZSBz
dHJhaWdodGZvcndhcmQgYW5kIG5hdHVyYWwgdG8gbWUsIGFuZCBpbiBwYXJhbGxlbCB3b3VsZCBs
aWtlIHlvdSB0byBjb25zaWRlciB0aGUgaWRlYSBvZiBhbiBJMk5TRiBleHRlbnNpb24gYWxsb3dp
bmcgdXMgdG8gcmV1c2UgdGhlIGNhcGFiaWxpdHkgbW9kZWwgZm9yIHBvbGljeS1jb250cm9sIHRy
YW5zZm9ybWF0aW9uLCBhbmQgdG8gaW5jb3Jwb3JhdGUgdGhlIGF0dGVzdGF0aW9uIG1hdHRlcnMg
eW91IGtub3cgSSB3YXMgc28gbXVjaCBpbnRlcmVzdGVkIGluLg0KDQpCZSBnb29kZSwNCg0KLS0N
CiJFc3RhIHZleiBubyBmYWxsYXJlbW9zLCBEb2N0b3IgSW5maWVybm8iDQoNCkRyIERpZWdvIFIu
IExvcGV6DQpUZWxlZm9uaWNhIEkrRA0KaHR0cHM6Ly93d3cubGlua2VkaW4uY29tL2luL2RyMmxv
cGV6LzxodHRwczovL25hbTExLnNhZmVsaW5rcy5wcm90ZWN0aW9uLm91dGxvb2suY29tLz91cmw9
aHR0cHMlM0ElMkYlMkZ3d3cubGlua2VkaW4uY29tJTJGaW4lMkZkcjJsb3BleiUyRiZkYXRhPTAy
JTdDMDElN0NsaW5kYS5kdW5iYXIlNDBmdXR1cmV3ZWkuY29tJTdDMDhhNDg4NThkN2JkNGQ4NDNh
NmUwOGQ4NWY0N2I0MzglN0MwZmVlOGZmMmEzYjI0MDE4OWM3NTNhMWQ1NTkxZmVkYyU3QzElN0Mw
JTdDNjM3MzY0MTA4ODY0OTQ5NjMzJnNkYXRhPVJPUjQlMkZ5RDFXcVdEYjFyQ2JKeDNFUnFUaU1D
UTkyaWJreXoyNmtZWmREOCUzRCZyZXNlcnZlZD0wPg0KDQplLW1haWw6IGRpZWdvLnIubG9wZXpA
dGVsZWZvbmljYS5jb208bWFpbHRvOmRpZWdvLnIubG9wZXpAdGVsZWZvbmljYS5jb20+DQpUZWw6
ICAgICAgICAgKzM0IDkxMyAxMjkgMDQxDQpNb2JpbGU6ICArMzQgNjgyIDA1MSAwOTENCi0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0NCg0KT24gMjIvMDkvMjAyMCwgMTg6MDEsICJM
aW5kYSBEdW5iYXIiIDxsaW5kYS5kdW5iYXJAZnV0dXJld2VpLmNvbTxtYWlsdG86bGluZGEuZHVu
YmFyQGZ1dHVyZXdlaS5jb20+PiB3cm90ZToNCg0KRGllZ286DQoNClRoYW5rIHlvdSB2ZXJ5IG11
Y2ggZm9yIHRoZSByZWZsZWN0aW9uIG9mIHRoZSBDYXBhYmlsaXRpZXMgSW5mb3JtYXRpb24gTW9k
ZWwgRHJhZnQuIEFncmVlIHdpdGggeW91ciBzdGF0ZW1lbnQgdGhhdCDigJx0aGUgY2FwYWJpbGl0
eSBkYXRhIG1vZGVsIHdhcyBldm9sdmluZyBpbiBhIHF1aXRlIHJlYXNvbmFibGUgYW5kIHByYWdt
YXRpYyB3YXksIGluY2x1ZGluZyBydW5uaW5nIGNvZGUgYXQgdGhlIGhhY2thdGhvbnPigJ0uDQoN
Ckxvb2tzIGxpa2UgRXJpYyBWeW5ja2Ugc3RpbGwgd2FudHMgdGhlIGluZm9ybWF0aW9uIG1vZGVs
IHRvIGJlIGZpeGVkIHRvIGNsZWFyIGhpcyDigJxESVNDVVNT4oCdIGJhbGxvdC4NCkhvdyBhYm91
dCB0aGUgZm9sbG93aW5nIHN0ZXBzOg0KDQotICAgICAgICAgIEFzayBSb21hbuKAmXMgYWR2aWNl
IGlmIHdlIGNhbiBzaW1wbGlmeSB0aGUgSW5mb3JtYXRpb24gTW9kZWwgbWFpbmx5IHRvIHJlZmxl
Y3Qgd2hhdCBoYXMgYmVlbiBpbiB0aGUgRGF0YSBNb2RlbC4NCg0KLSAgICAgICAgICBPciwgZHJv
cCB0aGUgSW5mb3JtYXRpb24gbW9kZWwgZHJhZnQgYW5kIHJlbW92ZSB0aGUgcmVmZW5jZSB0byB0
aGUgZHJhZnQsIGJ1dCBSb21hbiBoYXMgdG8gY29udmluY2UgRXJpYyB0byBhZ3JlZSBub3QgaGF2
aW5nIHRoZSBpbmZvcm1hdGlvbiBtb2RlbC4NCg0KV2hhdCBkbyB5b3UgdGhpbms/DQoNCkxpbmRh
DQoNCg0KRnJvbTogRGllZ28gUi4gTG9wZXogPGRpZWdvLnIubG9wZXpAdGVsZWZvbmljYS5jb208
bWFpbHRvOmRpZWdvLnIubG9wZXpAdGVsZWZvbmljYS5jb20+Pg0KU2VudDogVHVlc2RheSwgU2Vw
dGVtYmVyIDIyLCAyMDIwIDk6NTAgQU0NClRvOiBNci4gSmFlaG9vbiBQYXVsIEplb25nIDxqYWVo
b29uLnBhdWxAZ21haWwuY29tPG1haWx0bzpqYWVob29uLnBhdWxAZ21haWwuY29tPj47IExpbmRh
IER1bmJhciA8bGluZGEuZHVuYmFyQGZ1dHVyZXdlaS5jb208bWFpbHRvOmxpbmRhLmR1bmJhckBm
dXR1cmV3ZWkuY29tPj4NCkNjOiBYaWFsaWFuZyAoRnJhbmspIDxmcmFuay54aWFsaWFuZ0BodWF3
ZWkuY29tPG1haWx0bzpmcmFuay54aWFsaWFuZ0BodWF3ZWkuY29tPj47IFlvYXYgTmlyIDx5bmly
LmlldGZAZ21haWwuY29tPG1haWx0bzp5bmlyLmlldGZAZ21haWwuY29tPj47IEpvaG4gU3RyYXNz
bmVyIDxKb2huLnNjLlN0cmFzc25lckBodWF3ZWkuY29tPG1haWx0bzpKb2huLnNjLlN0cmFzc25l
ckBodWF3ZWkuY29tPj47IEFsZG8gQmFzaWxlIDxjYXRhbGRvLmJhc2lsZUBwb2xpdG8uaXQ8bWFp
bHRvOmNhdGFsZG8uYmFzaWxlQHBvbGl0by5pdD4+OyBSb21hbiBEYW55bGl3IDxyZGRAY2VydC5v
cmc8bWFpbHRvOnJkZEBjZXJ0Lm9yZz4+DQpTdWJqZWN0OiBSZTogT2ZmZXIgZm9yIFJldmlzaW9u
IEhlbHAgZm9yIEkyTlNGIE5TRnMgQ2FwYWJpbGl0aWVzIEluZm9ybWF0aW9uIE1vZGVsIERyYWZ0
DQoNCkhpIFBhdWwsDQoNCkJlZm9yZSB5b3UgZ28gZm9yIGl0LCBsZXQgbWUgc2hhcmUgd2l0aCB5
b3Ugc29tZSByZWZsZWN0aW9ucyBvbiB0aGUgc3RhdGUgb2YgdGhlIGRyYWZ0LCBpbiB0aGUgc3Bp
cml0IG9mIHdoYXQgSSByZXBsaWVkIHRvIEVyaWMgVnluY2tlLg0KDQpJIG11c3QgY29uZmVzcyB0
aGVyZSBoYXMgYmVlbiBhIGNvbWJpbmF0aW9uIG9mIGV2ZW50cyB0aGF0IG1hZGUgbWUgdGhpbmsg
dGhlIGJlc3Qgc29sdXRpb24gd2FzIHRvIGxlYXZlIHRoaXMgZHJhZnQgdG8gZmFkZSBhd2F5LiBG
aXJzdCwgSSB3YXMgbm90IChoYXZlIG5vdCBiZWVuIHlldCkgYWJsZSB0byBmaW5kIGEgc29sdXRp
b24gdG8gbW9zdCBvZiBSb21hbuKAmXMgY29tbWVudHMgd2l0aG91dCB0b3RhbGx5IHJld3JpdGlu
ZyBtb3N0LCBpZiBub3QgYWxsLCBvZiB0aGUgZG9jdW1lbnQuICBTZWNvbmQsIHRoZSBmYWN0IHRo
YXQgdGhlIGNhcGFiaWxpdHkgZGF0YSBtb2RlbCB3YXMgZXZvbHZpbmcgaW4gYSBxdWl0ZSByZWFz
b25hYmxlIGFuZCBwcmFnbWF0aWMgd2F5LCBpbmNsdWRpbmcgcnVubmluZyBjb2RlIGF0IHRoZSBo
YWNrYXRob25zLCBmb2xsb3dpbmcgdGhlIHNwaXJpdCBvZiB0aGUgaW5pdGlhbCB3b3JrIGluIHRo
ZSBpbmZvcm1hdGlvbiBtb2RlbCwgYnV0IG5vdCBhdHRlbXB0aW5nIHRvIGFsaWduIHdpdGggaXRz
IG1vc3QgcmVjZW50IGV2b2x1dGlvbi4gSWYgSSBoYXZlIG5vdCBzaGFyZWQgdGhpcyBwb3NpdGlv
biBiZWZvcmUgaXMgYmVjYXVzZSBJIGhhdmUgYmVlbiBsb29raW5nIGZvciBhIHdheSB0byBtYWtl
IHRoZSBpZGVhIG9mIGJyaWRnaW5nIGNhcGFiaWxpdHkgZGVjbGFyYXRpb25zIGFuZCBzZWN1cml0
eSBwb2xpY3kgc3RhdGVtZW50cyBhdCB0aGUgSTJOU0YgY29udHJvbGxlciB2aWFibGUsIGFuZCBJ
IHdhcyBob3BpbmcgdG8gZmluZCBzdWNoIGEgd2F5IGJ5IHJldXNpbmcgcGFydCBvZiB0aGUgY2Fw
YWJpbGl0eSBpbmZvIG1vZGVsIGRyYWZ0Lg0KDQpBcyBJIHRvbGQgRXJpYywgSSBiZWxpZXZlIHRo
ZSBjdXJyZW50IGNhcGFiaWxpdHkgbW9kZWwgaGFzIGEgcG93ZXJmdWwgKHRob3VnaCBwcm9iYWJs
eSBub3QgeWV0IGNvbXBsZXRlKSBjYWxjdWx1cyBmb3IgcG9saWN5IGRlc2NyaXB0aW9uIGFuZCB2
YWxpZGF0aW9uLCBidXQgbm90IGRpcmVjdGx5IHJlbGF0ZWQgdG8gdGhlIG1hbmFnZW1lbnQgbWVj
aGFuaXNtcyBhZGRyZXNzZWQgaW4gdGhlIGNhcGFiaWxpdHkgZGF0YSBtb2RlbCBhbmQgdGhlIG90
aGVyIGRhdGEgbW9kZWxzIHByb2R1Y2VkIGluIEkyTlNGLiBJIGJlbGlldmUgdGhlcmUgaXMgYW4g
b3Bwb3J0dW5pdHkgZm9yIGFjY29tcGxpc2hpbmcgcG9saWN5LWNhcGFiaWxpdHkgYnJpZGdpbmcs
IHVzaW5nIGFzIGZvdW5kYXRpb24gdGhlIGN1cnJlbnQgY2FwYWJpbGl0eSBtb2RlbCwgdGhvdWdo
IGl0IHNlZW1zIHRvIG1lIHRoYXQgdGhpcyB0YXNrIHdvdWxkIHJlcXVpcmUgc29tZSB0aW1lIHRv
IGNvbnNvbGlkYXRlIGFuZCB0aGVyZWZvcmUgaW1wbHkgYW4gZXh0ZW5zaW9uIG9mIHRoZSBJMk5T
RiBsaWZldGltZS4gSSB3b3VsZCBsaWtlIHRvIGtub3cgeW91ciBwb3NpdGlvbigqKSBhYm91dCBz
dWNoIGFuIGV4dGVuc2lvbiwgIHRoYXQgY291bGQgYWxzbyBiZWNvbWUgYW4gb3Bwb3J0dW5pdHkg
dG8gd29yayBpbiBvdGhlciBtYXR0ZXJzIHJlbGF0ZWQgdG8gYXR0ZXN0YXRpb24gKGluIHRoZSBs
aWdodCBvZiB0aGUgd29yayBpbiBSQVRTIGFuZCB0aGUgTVVEIGluaXRpYXRpdmUgd2l0aGluIHRo
ZSBPcHMgQXJlYSkgYW5kIGFjY291bnRpbmcuDQoNCkJlIGdvb2RlLA0KDQooKikgSSBhc3N1bWUg
eW91IGFyZSBpbiBmYXZvciwgUGF1bC4gQnV0IEnigJlkIGxpa2UgdG8gZ2V0IExpbmRh4oCZcywg
WW9hduKAmXMgYW5kIFJvbWFu4oCZcyBpZGVhcywgYXMgd2VsbCBhcyB0aGUgYXZhaWxhYmlsaXR5
IHRvIHdvcmsgb24gdGhpcyBmcm9tIEZyYW5rLCBKb2huIGFuZCBBbGRvLg0KDQotLQ0KIkVzdGEg
dmV6IG5vIGZhbGxhcmVtb3MsIERvY3RvciBJbmZpZXJubyINCg0KRHIgRGllZ28gUi4gTG9wZXoN
ClRlbGVmb25pY2EgSStEDQpodHRwczovL3d3dy5saW5rZWRpbi5jb20vaW4vZHIybG9wZXovPGh0
dHBzOi8vbmFtMTEuc2FmZWxpbmtzLnByb3RlY3Rpb24ub3V0bG9vay5jb20vP3VybD1odHRwcyUz
QSUyRiUyRnd3dy5saW5rZWRpbi5jb20lMkZpbiUyRmRyMmxvcGV6JTJGJmRhdGE9MDIlN0MwMSU3
Q2xpbmRhLmR1bmJhciU0MGZ1dHVyZXdlaS5jb20lN0MwOGE0ODg1OGQ3YmQ0ZDg0M2E2ZTA4ZDg1
ZjQ3YjQzOCU3QzBmZWU4ZmYyYTNiMjQwMTg5Yzc1M2ExZDU1OTFmZWRjJTdDMSU3QzAlN0M2Mzcz
NjQxMDg4NjQ5NDk2MzMmc2RhdGE9Uk9SNCUyRnlEMVdxV0RiMXJDYkp4M0VScVRpTUNROTJpYmt5
ejI2a1laZEQ4JTNEJnJlc2VydmVkPTA+DQoNCmUtbWFpbDogZGllZ28uci5sb3BlekB0ZWxlZm9u
aWNhLmNvbTxtYWlsdG86ZGllZ28uci5sb3BlekB0ZWxlZm9uaWNhLmNvbT4NClRlbDogICAgICAg
ICArMzQgOTEzIDEyOSAwNDENCk1vYmlsZTogICszNCA2ODIgMDUxIDA5MQ0KLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLQ0KDQpPbiAxNy8wOS8yMDIwLCAwMTo0MiwgIk1yLiBKYWVo
b29uIFBhdWwgSmVvbmciIDxqYWVob29uLnBhdWxAZ21haWwuY29tPG1haWx0bzpqYWVob29uLnBh
dWxAZ21haWwuY29tPj4gd3JvdGU6DQoNCkhpIExpbmRhLA0KSSB3aWxsIGFkZHJlc3Mgb3VyIEFE
IFJvbWFuJ3MgY29tbWVudHMgb24gdGhpcyBOU0ZzIGNhcGFiaWxpdGllcyBpbmZvcm1hdGlvbiBk
cmFmdCBhcyB0aGUgMm5kIGVkaXRvciB0aHJvdWdoIHRoZSBjb2xsYWJvcmF0aW9uIHdpdGggRnJh
bmsgKHRoZSAxc3QgZWRpdG9yKSBhbmQgdGhlIG90aGVyIGF1dGhvcnMuDQoNCkkgQ0Mgb3VyIEFE
IFJvbWFuIGFuZCB0aGUgb3RoZXIgYXV0aG9ycywgc3VjaCBhcyBKb2huIGFuZCBDYXRhbGRvLg0K
DQoNClRoYW5rcyBmb3IgeW91ciBzdXBwb3J0IGFuZCBndWlkYW5jZS4NCg0KQmVzdCBSZWdhcmRz
LA0KUGF1bA0KDQoyMDIw64WEIDnsm5QgMTfsnbwgKOuqqSkg7Jik7KCEIDM6NDQsIExpbmRhIER1
bmJhciA8bGluZGEuZHVuYmFyQGZ1dHVyZXdlaS5jb208bWFpbHRvOmxpbmRhLmR1bmJhckBmdXR1
cmV3ZWkuY29tPj7ri5jsnbQg7J6R7ISxOg0KUGF1bCwNCg0KVGhhbmsgeW91IHZlcnkgbXVjaCBm
b3Igb2ZmZXJpbmcgdG8gYWRkcmVzcyB0aGUgQUQgY29tbWVudHMgdG8gdGhpcyBkcmFmdC4gTG9v
a3MgbGlrZSB0aGUgY3VycmVudCBhdXRob3JzIGFyZSB0b28gYnVzeSB0byBhZGRyZXNzIHRob3Nl
IGNvbW1lbnRzLiBJdCBoYXMgYmVlbiBvdmVyIGEgeWVhciBzaW5jZSB0aGUgQUQgY29tbWVudHMg
d2VyZSBnaXZlbi4gIFdlIG5lZWQgdG8gbW92ZSB0aGUgZHJhZnQgZm9yd2FyZC4gVGhlcmVmb3Jl
LCBJMk5TRiBjaGFpcnMgaGF2ZSBhdXRob3JpemVkIHlvdSB0byBiZSBvbmUgb2YgdGhlIGVkaXRv
cnMgdG8gYWRkcmVzcyB0aGUgQUQgY29tbWVudHMgYW5kIHJldmlzZSB0aGUgZHJhZnQuDQoNCg0K
VGhhbmsgeW91IHZlcnkgbXVjaC4NCg0KTGluZGEgJiBZb2F2DQoNCg0KRnJvbTogTXIuIEphZWhv
b24gUGF1bCBKZW9uZyA8amFlaG9vbi5wYXVsQGdtYWlsLmNvbTxtYWlsdG86amFlaG9vbi5wYXVs
QGdtYWlsLmNvbT4+DQpTZW50OiBTdW5kYXksIFNlcHRlbWJlciAxMywgMjAyMCAxMDowOSBBTQ0K
VG86IFhpYWxpYW5nIChGcmFuaykgPGZyYW5rLnhpYWxpYW5nQGh1YXdlaS5jb208bWFpbHRvOmZy
YW5rLnhpYWxpYW5nQGh1YXdlaS5jb20+Pg0KQ2M6IExpbmRhIER1bmJhciA8bGluZGEuZHVuYmFy
QGZ1dHVyZXdlaS5jb208bWFpbHRvOmxpbmRhLmR1bmJhckBmdXR1cmV3ZWkuY29tPj47IFlvYXYg
TmlyIDx5bmlyLmlldGZAZ21haWwuY29tPG1haWx0bzp5bmlyLmlldGZAZ21haWwuY29tPj47IERJ
RUdPIExPUEVaIEdBUkNJQSA8ZGllZ28uci5sb3BlekB0ZWxlZm9uaWNhLmNvbTxtYWlsdG86ZGll
Z28uci5sb3BlekB0ZWxlZm9uaWNhLmNvbT4+OyBKYWVob29uIEplb25nIDxqYWVob29uLnBhdWxA
Z21haWwuY29tPG1haWx0bzpqYWVob29uLnBhdWxAZ21haWwuY29tPj4NClN1YmplY3Q6IE9mZmVy
IGZvciBSZXZpc2lvbiBIZWxwIGZvciBJMk5TRiBOU0ZzIENhcGFiaWxpdGllcyBJbmZvcm1hdGlv
biBNb2RlbCBEcmFmdA0KDQpIaSBGcmFuaywNCkNvdWxkIEkgaGVscCB5b3UgdG8gcmV2aXNlIHlv
dXIgaW5mb3JtYXRpb24gbW9kZWwgZHJhZnQgZm9yIG91ciBBRCBSb21hbiBEYW55bGl3J3MgcmV2
aWV3IGNvbW1lbnRzICBhcyBhIGNvLWVkaXRvcj8NCmh0dHBzOi8vZGF0YXRyYWNrZXIuaWV0Zi5v
cmcvZG9jL2RyYWZ0LWlldGYtaTJuc2YtY2FwYWJpbGl0eS8/aW5jbHVkZV90ZXh0PTE8aHR0cHM6
Ly9uYW0xMS5zYWZlbGlua3MucHJvdGVjdGlvbi5vdXRsb29rLmNvbS8/dXJsPWh0dHBzJTNBJTJG
JTJGZGF0YXRyYWNrZXIuaWV0Zi5vcmclMkZkb2MlMkZkcmFmdC1pZXRmLWkybnNmLWNhcGFiaWxp
dHklMkYlM0ZpbmNsdWRlX3RleHQlM0QxJmRhdGE9MDIlN0MwMSU3Q2xpbmRhLmR1bmJhciU0MGZ1
dHVyZXdlaS5jb20lN0MwOGE0ODg1OGQ3YmQ0ZDg0M2E2ZTA4ZDg1ZjQ3YjQzOCU3QzBmZWU4ZmYy
YTNiMjQwMTg5Yzc1M2ExZDU1OTFmZWRjJTdDMSU3QzAlN0M2MzczNjQxMDg4NjQ5NTk2MjYmc2Rh
dGE9R1VyYmFZdTJRNE4xWU5VVWV0Mm9WUlBxYnluQTc4Y1NCVGYlMkZCZVNDWTQ0JTNEJnJlc2Vy
dmVkPTA+DQoNCkFzIHlvdSBrbm93LCBJIGhhdmUgZmluaXNoZWQgb3VyIEkyTlNGIGRhdGEgbW9k
ZWwgZHJhZnRzLg0KDQpJIGFtIGhhcHB5IHRvIHdvcmsgb24gdGhlIHJldmlzaW9uIHdpdGggeW91
IGluIG9yZGVyIHRvIGNvbXBsZXRlIG91ciBJMk5TRiBkZWxpdmVyYWJsZXMuDQoNClRoYW5rcy4N
Cg0KQmVzdCBSZWdhcmRzLA0KUGF1bA0KDQpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
Xw0KDQpFc3RlIG1lbnNhamUgeSBzdXMgYWRqdW50b3Mgc2UgZGlyaWdlbiBleGNsdXNpdmFtZW50
ZSBhIHN1IGRlc3RpbmF0YXJpbywgcHVlZGUgY29udGVuZXIgaW5mb3JtYWNpw7NuIHByaXZpbGVn
aWFkYSBvIGNvbmZpZGVuY2lhbCB5IGVzIHBhcmEgdXNvIGV4Y2x1c2l2byBkZSBsYSBwZXJzb25h
IG8gZW50aWRhZCBkZSBkZXN0aW5vLiBTaSBubyBlcyB1c3RlZC4gZWwgZGVzdGluYXRhcmlvIGlu
ZGljYWRvLCBxdWVkYSBub3RpZmljYWRvIGRlIHF1ZSBsYSBsZWN0dXJhLCB1dGlsaXphY2nDs24s
IGRpdnVsZ2FjacOzbiB5L28gY29waWEgc2luIGF1dG9yaXphY2nDs24gcHVlZGUgZXN0YXIgcHJv
aGliaWRhIGVuIHZpcnR1ZCBkZSBsYSBsZWdpc2xhY2nDs24gdmlnZW50ZS4gU2kgaGEgcmVjaWJp
ZG8gZXN0ZSBtZW5zYWplIHBvciBlcnJvciwgbGUgcm9nYW1vcyBxdWUgbm9zIGxvIGNvbXVuaXF1
ZSBpbm1lZGlhdGFtZW50ZSBwb3IgZXN0YSBtaXNtYSB2w61hIHkgcHJvY2VkYSBhIHN1IGRlc3Ry
dWNjacOzbi4NCg0KVGhlIGluZm9ybWF0aW9uIGNvbnRhaW5lZCBpbiB0aGlzIHRyYW5zbWlzc2lv
biBpcyBwcml2aWxlZ2VkIGFuZCBjb25maWRlbnRpYWwgaW5mb3JtYXRpb24gaW50ZW5kZWQgb25s
eSBmb3IgdGhlIHVzZSBvZiB0aGUgaW5kaXZpZHVhbCBvciBlbnRpdHkgbmFtZWQgYWJvdmUuIElm
IHRoZSByZWFkZXIgb2YgdGhpcyBtZXNzYWdlIGlzIG5vdCB0aGUgaW50ZW5kZWQgcmVjaXBpZW50
LCB5b3UgYXJlIGhlcmVieSBub3RpZmllZCB0aGF0IGFueSBkaXNzZW1pbmF0aW9uLCBkaXN0cmli
dXRpb24gb3IgY29weWluZyBvZiB0aGlzIGNvbW11bmljYXRpb24gaXMgc3RyaWN0bHkgcHJvaGli
aXRlZC4gSWYgeW91IGhhdmUgcmVjZWl2ZWQgdGhpcyB0cmFuc21pc3Npb24gaW4gZXJyb3IsIGRv
IG5vdCByZWFkIGl0LiBQbGVhc2UgaW1tZWRpYXRlbHkgcmVwbHkgdG8gdGhlIHNlbmRlciB0aGF0
IHlvdSBoYXZlIHJlY2VpdmVkIHRoaXMgY29tbXVuaWNhdGlvbiBpbiBlcnJvciBhbmQgdGhlbiBk
ZWxldGUgaXQuDQoNCkVzdGEgbWVuc2FnZW0gZSBzZXVzIGFuZXhvcyBzZSBkaXJpZ2VtIGV4Y2x1
c2l2YW1lbnRlIGFvIHNldSBkZXN0aW5hdMOhcmlvLCBwb2RlIGNvbnRlciBpbmZvcm1hw6fDo28g
cHJpdmlsZWdpYWRhIG91IGNvbmZpZGVuY2lhbCBlIMOpIHBhcmEgdXNvIGV4Y2x1c2l2byBkYSBw
ZXNzb2Egb3UgZW50aWRhZGUgZGUgZGVzdGluby4gU2UgbsOjbyDDqSB2b3NzYSBzZW5ob3JpYSBv
IGRlc3RpbmF0w6FyaW8gaW5kaWNhZG8sIGZpY2Egbm90aWZpY2FkbyBkZSBxdWUgYSBsZWl0dXJh
LCB1dGlsaXphw6fDo28sIGRpdnVsZ2HDp8OjbyBlL291IGPDs3BpYSBzZW0gYXV0b3JpemHDp8Oj
byBwb2RlIGVzdGFyIHByb2liaWRhIGVtIHZpcnR1ZGUgZGEgbGVnaXNsYcOnw6NvIHZpZ2VudGUu
IFNlIHJlY2ViZXUgZXN0YSBtZW5zYWdlbSBwb3IgZXJybywgcm9nYW1vcy1saGUgcXVlIG5vcyBv
IGNvbXVuaXF1ZSBpbWVkaWF0YW1lbnRlIHBvciBlc3RhIG1lc21hIHZpYSBlIHByb2NlZGEgYSBz
dWEgZGVzdHJ1acOnw6NvDQoNCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQoNCkVz
dGUgbWVuc2FqZSB5IHN1cyBhZGp1bnRvcyBzZSBkaXJpZ2VuIGV4Y2x1c2l2YW1lbnRlIGEgc3Ug
ZGVzdGluYXRhcmlvLCBwdWVkZSBjb250ZW5lciBpbmZvcm1hY2nDs24gcHJpdmlsZWdpYWRhIG8g
Y29uZmlkZW5jaWFsIHkgZXMgcGFyYSB1c28gZXhjbHVzaXZvIGRlIGxhIHBlcnNvbmEgbyBlbnRp
ZGFkIGRlIGRlc3Rpbm8uIFNpIG5vIGVzIHVzdGVkLiBlbCBkZXN0aW5hdGFyaW8gaW5kaWNhZG8s
IHF1ZWRhIG5vdGlmaWNhZG8gZGUgcXVlIGxhIGxlY3R1cmEsIHV0aWxpemFjacOzbiwgZGl2dWxn
YWNpw7NuIHkvbyBjb3BpYSBzaW4gYXV0b3JpemFjacOzbiBwdWVkZSBlc3RhciBwcm9oaWJpZGEg
ZW4gdmlydHVkIGRlIGxhIGxlZ2lzbGFjacOzbiB2aWdlbnRlLiBTaSBoYSByZWNpYmlkbyBlc3Rl
IG1lbnNhamUgcG9yIGVycm9yLCBsZSByb2dhbW9zIHF1ZSBub3MgbG8gY29tdW5pcXVlIGlubWVk
aWF0YW1lbnRlIHBvciBlc3RhIG1pc21hIHbDrWEgeSBwcm9jZWRhIGEgc3UgZGVzdHJ1Y2Npw7Nu
Lg0KDQpUaGUgaW5mb3JtYXRpb24gY29udGFpbmVkIGluIHRoaXMgdHJhbnNtaXNzaW9uIGlzIHBy
aXZpbGVnZWQgYW5kIGNvbmZpZGVudGlhbCBpbmZvcm1hdGlvbiBpbnRlbmRlZCBvbmx5IGZvciB0
aGUgdXNlIG9mIHRoZSBpbmRpdmlkdWFsIG9yIGVudGl0eSBuYW1lZCBhYm92ZS4gSWYgdGhlIHJl
YWRlciBvZiB0aGlzIG1lc3NhZ2UgaXMgbm90IHRoZSBpbnRlbmRlZCByZWNpcGllbnQsIHlvdSBh
cmUgaGVyZWJ5IG5vdGlmaWVkIHRoYXQgYW55IGRpc3NlbWluYXRpb24sIGRpc3RyaWJ1dGlvbiBv
ciBjb3B5aW5nIG9mIHRoaXMgY29tbXVuaWNhdGlvbiBpcyBzdHJpY3RseSBwcm9oaWJpdGVkLiBJ
ZiB5b3UgaGF2ZSByZWNlaXZlZCB0aGlzIHRyYW5zbWlzc2lvbiBpbiBlcnJvciwgZG8gbm90IHJl
YWQgaXQuIFBsZWFzZSBpbW1lZGlhdGVseSByZXBseSB0byB0aGUgc2VuZGVyIHRoYXQgeW91IGhh
dmUgcmVjZWl2ZWQgdGhpcyBjb21tdW5pY2F0aW9uIGluIGVycm9yIGFuZCB0aGVuIGRlbGV0ZSBp
dC4NCg0KRXN0YSBtZW5zYWdlbSBlIHNldXMgYW5leG9zIHNlIGRpcmlnZW0gZXhjbHVzaXZhbWVu
dGUgYW8gc2V1IGRlc3RpbmF0w6FyaW8sIHBvZGUgY29udGVyIGluZm9ybWHDp8OjbyBwcml2aWxl
Z2lhZGEgb3UgY29uZmlkZW5jaWFsIGUgw6kgcGFyYSB1c28gZXhjbHVzaXZvIGRhIHBlc3NvYSBv
dSBlbnRpZGFkZSBkZSBkZXN0aW5vLiBTZSBuw6NvIMOpIHZvc3NhIHNlbmhvcmlhIG8gZGVzdGlu
YXTDoXJpbyBpbmRpY2FkbywgZmljYSBub3RpZmljYWRvIGRlIHF1ZSBhIGxlaXR1cmEsIHV0aWxp
emHDp8OjbywgZGl2dWxnYcOnw6NvIGUvb3UgY8OzcGlhIHNlbSBhdXRvcml6YcOnw6NvIHBvZGUg
ZXN0YXIgcHJvaWJpZGEgZW0gdmlydHVkZSBkYSBsZWdpc2xhw6fDo28gdmlnZW50ZS4gU2UgcmVj
ZWJldSBlc3RhIG1lbnNhZ2VtIHBvciBlcnJvLCByb2dhbW9zLWxoZSBxdWUgbm9zIG8gY29tdW5p
cXVlIGltZWRpYXRhbWVudGUgcG9yIGVzdGEgbWVzbWEgdmlhIGUgcHJvY2VkYSBhIHN1YSBkZXN0
cnVpw6fDo28NCg==

--_000_SN6PR13MB23343DE9392FA9EDDDA65651850B0SN6PR13MB2334namp_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTUgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPCEtLVtp
ZiAhbXNvXT48c3R5bGU+dlw6KiB7YmVoYXZpb3I6dXJsKCNkZWZhdWx0I1ZNTCk7fQ0Kb1w6KiB7
YmVoYXZpb3I6dXJsKCNkZWZhdWx0I1ZNTCk7fQ0Kd1w6KiB7YmVoYXZpb3I6dXJsKCNkZWZhdWx0
I1ZNTCk7fQ0KLnNoYXBlIHtiZWhhdmlvcjp1cmwoI2RlZmF1bHQjVk1MKTt9DQo8L3N0eWxlPjwh
W2VuZGlmXS0tPjxzdHlsZT48IS0tDQovKiBGb250IERlZmluaXRpb25zICovDQpAZm9udC1mYWNl
DQoJe2ZvbnQtZmFtaWx5OldpbmdkaW5nczsNCglwYW5vc2UtMTo1IDAgMCAwIDAgMCAwIDAgMCAw
O30NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6IkNhbWJyaWEgTWF0aCI7DQoJcGFub3NlLTE6
MiA0IDUgMyA1IDQgNiAzIDIgNDt9DQpAZm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5OkRlbmdYaWFu
Ow0KCXBhbm9zZS0xOjIgMSA2IDAgMyAxIDEgMSAxIDE7fQ0KQGZvbnQtZmFjZQ0KCXtmb250LWZh
bWlseTpDYWxpYnJpOw0KCXBhbm9zZS0xOjIgMTUgNSAyIDIgMiA0IDMgMiA0O30NCkBmb250LWZh
Y2UNCgl7Zm9udC1mYW1pbHk6IlxARGVuZ1hpYW4iOw0KCXBhbm9zZS0xOjIgMSA2IDAgMyAxIDEg
MSAxIDE7fQ0KQGZvbnQtZmFjZQ0KCXtmb250LWZhbWlseTpDb25zb2xhczsNCglwYW5vc2UtMToy
IDExIDYgOSAyIDIgNCAzIDIgNDt9DQpAZm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5OiJNYWxndW4g
R290aGljIjsNCglwYW5vc2UtMToyIDExIDUgMyAyIDAgMCAyIDAgNDt9DQpAZm9udC1mYWNlDQoJ
e2ZvbnQtZmFtaWx5OiJcQE1hbGd1biBHb3RoaWMiO30NCi8qIFN0eWxlIERlZmluaXRpb25zICov
DQpwLk1zb05vcm1hbCwgbGkuTXNvTm9ybWFsLCBkaXYuTXNvTm9ybWFsDQoJe21hcmdpbjowaW47
DQoJbWFyZ2luLWJvdHRvbTouMDAwMXB0Ow0KCWZvbnQtc2l6ZToxMS4wcHQ7DQoJZm9udC1mYW1p
bHk6IkNhbGlicmkiLHNhbnMtc2VyaWY7fQ0KYTpsaW5rLCBzcGFuLk1zb0h5cGVybGluaw0KCXtt
c28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJY29sb3I6Ymx1ZTsNCgl0ZXh0LWRlY29yYXRpb246dW5k
ZXJsaW5lO30NCnByZQ0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJbXNvLXN0eWxlLWxpbms6
IkhUTUwgUHJlZm9ybWF0dGVkIENoYXIiOw0KCW1hcmdpbjowaW47DQoJbWFyZ2luLWJvdHRvbTou
MDAwMXB0Ow0KCWZvbnQtc2l6ZToxMC4wcHQ7DQoJZm9udC1mYW1pbHk6IkNvdXJpZXIgTmV3Ijt9
DQpwLk1zb0xpc3RQYXJhZ3JhcGgsIGxpLk1zb0xpc3RQYXJhZ3JhcGgsIGRpdi5Nc29MaXN0UGFy
YWdyYXBoDQoJe21zby1zdHlsZS1wcmlvcml0eTozNDsNCgltYXJnaW4tdG9wOjBpbjsNCgltYXJn
aW4tcmlnaHQ6MGluOw0KCW1hcmdpbi1ib3R0b206MGluOw0KCW1hcmdpbi1sZWZ0Oi41aW47DQoJ
bWFyZ2luLWJvdHRvbTouMDAwMXB0Ow0KCWZvbnQtc2l6ZToxMS4wcHQ7DQoJZm9udC1mYW1pbHk6
IkNhbGlicmkiLHNhbnMtc2VyaWY7fQ0Kc3Bhbi5IVE1MUHJlZm9ybWF0dGVkQ2hhcg0KCXttc28t
c3R5bGUtbmFtZToiSFRNTCBQcmVmb3JtYXR0ZWQgQ2hhciI7DQoJbXNvLXN0eWxlLXByaW9yaXR5
Ojk5Ow0KCW1zby1zdHlsZS1saW5rOiJIVE1MIFByZWZvcm1hdHRlZCI7DQoJZm9udC1mYW1pbHk6
Q29uc29sYXM7fQ0Kc3Bhbi5FbWFpbFN0eWxlMjENCgl7bXNvLXN0eWxlLXR5cGU6cGVyc29uYWw7
DQoJZm9udC1mYW1pbHk6IkNhbGlicmkiLHNhbnMtc2VyaWY7DQoJY29sb3I6d2luZG93dGV4dDt9
DQpzcGFuLkVtYWlsU3R5bGUyNA0KCXttc28tc3R5bGUtdHlwZTpwZXJzb25hbC1yZXBseTsNCglm
b250LWZhbWlseToiQ2FsaWJyaSIsc2Fucy1zZXJpZjsNCgljb2xvcjp3aW5kb3d0ZXh0O30NCi5N
c29DaHBEZWZhdWx0DQoJe21zby1zdHlsZS10eXBlOmV4cG9ydC1vbmx5Ow0KCWZvbnQtc2l6ZTox
MC4wcHQ7fQ0KQHBhZ2UgV29yZFNlY3Rpb24xDQoJe3NpemU6OC41aW4gMTEuMGluOw0KCW1hcmdp
bjoxLjBpbiAxLjBpbiAxLjBpbiAxLjBpbjt9DQpkaXYuV29yZFNlY3Rpb24xDQoJe3BhZ2U6V29y
ZFNlY3Rpb24xO30NCi8qIExpc3QgRGVmaW5pdGlvbnMgKi8NCkBsaXN0IGwwDQoJe21zby1saXN0
LWlkOjg5MTU3NTU3ODsNCgltc28tbGlzdC10eXBlOmh5YnJpZDsNCgltc28tbGlzdC10ZW1wbGF0
ZS1pZHM6NTcxNDkxODc0IC0xOTE5Nzc5MDQ4IDY3Njk4NjkxIDY3Njk4NjkzIDY3Njk4Njg5IDY3
Njk4NjkxIDY3Njk4NjkzIDY3Njk4Njg5IDY3Njk4NjkxIDY3Njk4NjkzO30NCkBsaXN0IGwwOmxl
dmVsMQ0KCXttc28tbGV2ZWwtc3RhcnQtYXQ6MDsNCgltc28tbGV2ZWwtbnVtYmVyLWZvcm1hdDpi
dWxsZXQ7DQoJbXNvLWxldmVsLXRleHQ6LTsNCgltc28tbGV2ZWwtdGFiLXN0b3A6bm9uZTsNCglt
c28tbGV2ZWwtbnVtYmVyLXBvc2l0aW9uOmxlZnQ7DQoJdGV4dC1pbmRlbnQ6LS4yNWluOw0KCWZv
bnQtZmFtaWx5OiJDYWxpYnJpIixzYW5zLXNlcmlmOw0KCW1zby1mYXJlYXN0LWZvbnQtZmFtaWx5
OkRlbmdYaWFuO30NCkBsaXN0IGwwOmxldmVsMg0KCXttc28tbGV2ZWwtbnVtYmVyLWZvcm1hdDpi
dWxsZXQ7DQoJbXNvLWxldmVsLXRleHQ6bzsNCgltc28tbGV2ZWwtdGFiLXN0b3A6bm9uZTsNCglt
c28tbGV2ZWwtbnVtYmVyLXBvc2l0aW9uOmxlZnQ7DQoJdGV4dC1pbmRlbnQ6LS4yNWluOw0KCWZv
bnQtZmFtaWx5OiJDb3VyaWVyIE5ldyI7fQ0KQGxpc3QgbDA6bGV2ZWwzDQoJe21zby1sZXZlbC1u
dW1iZXItZm9ybWF0OmJ1bGxldDsNCgltc28tbGV2ZWwtdGV4dDrvgqc7DQoJbXNvLWxldmVsLXRh
Yi1zdG9wOm5vbmU7DQoJbXNvLWxldmVsLW51bWJlci1wb3NpdGlvbjpsZWZ0Ow0KCXRleHQtaW5k
ZW50Oi0uMjVpbjsNCglmb250LWZhbWlseTpXaW5nZGluZ3M7fQ0KQGxpc3QgbDA6bGV2ZWw0DQoJ
e21zby1sZXZlbC1udW1iZXItZm9ybWF0OmJ1bGxldDsNCgltc28tbGV2ZWwtdGV4dDrvgrc7DQoJ
bXNvLWxldmVsLXRhYi1zdG9wOm5vbmU7DQoJbXNvLWxldmVsLW51bWJlci1wb3NpdGlvbjpsZWZ0
Ow0KCXRleHQtaW5kZW50Oi0uMjVpbjsNCglmb250LWZhbWlseTpTeW1ib2w7fQ0KQGxpc3QgbDA6
bGV2ZWw1DQoJe21zby1sZXZlbC1udW1iZXItZm9ybWF0OmJ1bGxldDsNCgltc28tbGV2ZWwtdGV4
dDpvOw0KCW1zby1sZXZlbC10YWItc3RvcDpub25lOw0KCW1zby1sZXZlbC1udW1iZXItcG9zaXRp
b246bGVmdDsNCgl0ZXh0LWluZGVudDotLjI1aW47DQoJZm9udC1mYW1pbHk6IkNvdXJpZXIgTmV3
Ijt9DQpAbGlzdCBsMDpsZXZlbDYNCgl7bXNvLWxldmVsLW51bWJlci1mb3JtYXQ6YnVsbGV0Ow0K
CW1zby1sZXZlbC10ZXh0Ou+CpzsNCgltc28tbGV2ZWwtdGFiLXN0b3A6bm9uZTsNCgltc28tbGV2
ZWwtbnVtYmVyLXBvc2l0aW9uOmxlZnQ7DQoJdGV4dC1pbmRlbnQ6LS4yNWluOw0KCWZvbnQtZmFt
aWx5OldpbmdkaW5nczt9DQpAbGlzdCBsMDpsZXZlbDcNCgl7bXNvLWxldmVsLW51bWJlci1mb3Jt
YXQ6YnVsbGV0Ow0KCW1zby1sZXZlbC10ZXh0Ou+CtzsNCgltc28tbGV2ZWwtdGFiLXN0b3A6bm9u
ZTsNCgltc28tbGV2ZWwtbnVtYmVyLXBvc2l0aW9uOmxlZnQ7DQoJdGV4dC1pbmRlbnQ6LS4yNWlu
Ow0KCWZvbnQtZmFtaWx5OlN5bWJvbDt9DQpAbGlzdCBsMDpsZXZlbDgNCgl7bXNvLWxldmVsLW51
bWJlci1mb3JtYXQ6YnVsbGV0Ow0KCW1zby1sZXZlbC10ZXh0Om87DQoJbXNvLWxldmVsLXRhYi1z
dG9wOm5vbmU7DQoJbXNvLWxldmVsLW51bWJlci1wb3NpdGlvbjpsZWZ0Ow0KCXRleHQtaW5kZW50
Oi0uMjVpbjsNCglmb250LWZhbWlseToiQ291cmllciBOZXciO30NCkBsaXN0IGwwOmxldmVsOQ0K
CXttc28tbGV2ZWwtbnVtYmVyLWZvcm1hdDpidWxsZXQ7DQoJbXNvLWxldmVsLXRleHQ674KnOw0K
CW1zby1sZXZlbC10YWItc3RvcDpub25lOw0KCW1zby1sZXZlbC1udW1iZXItcG9zaXRpb246bGVm
dDsNCgl0ZXh0LWluZGVudDotLjI1aW47DQoJZm9udC1mYW1pbHk6V2luZ2RpbmdzO30NCm9sDQoJ
e21hcmdpbi1ib3R0b206MGluO30NCnVsDQoJe21hcmdpbi1ib3R0b206MGluO30NCi0tPjwvc3R5
bGU+PCEtLVtpZiBndGUgbXNvIDldPjx4bWw+DQo8bzpzaGFwZWRlZmF1bHRzIHY6ZXh0PSJlZGl0
IiBzcGlkbWF4PSIxMDI2IiAvPg0KPC94bWw+PCFbZW5kaWZdLS0+PCEtLVtpZiBndGUgbXNvIDld
Pjx4bWw+DQo8bzpzaGFwZWxheW91dCB2OmV4dD0iZWRpdCI+DQo8bzppZG1hcCB2OmV4dD0iZWRp
dCIgZGF0YT0iMSIgLz4NCjwvbzpzaGFwZWxheW91dD48L3htbD48IVtlbmRpZl0tLT4NCjwvaGVh
ZD4NCjxib2R5IGxhbmc9IkVOLVVTIiBsaW5rPSJibHVlIiB2bGluaz0icHVycGxlIj4NCjxkaXYg
Y2xhc3M9IldvcmRTZWN0aW9uMSI+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5JMm5zZiBXRywgPG86
cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiPlRoZXJlIGhhcyBiZWVuIGFueSBvYmplY3Rpb24gdG8gdGhl
IEF1dGhvcuKAmXMgcmVxdWVzdCBmb3Igc3Vuc2V0dGluZyB0aGUgJm5ic3A7ZHJhZnQtaWV0Zi1p
Mm5zZi1jYXBhYmlsaXR5LTA1Lg0KPG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPkF1dGhvcnMgb2Yg
dGhlIGRyYWZ0LWlldGYtaTJuc2YtY2FwYWJpbGl0eS1kYXRhLW1vZGVsOiBwbGVhc2UgcmVtb3Zl
IHRoZSByZWZlcmVuY2UgdG8gdGhlIENhcGFiaWxpdHkgSW5mb3JtYXRpb24gTW9kZWwgYW5kIHVw
bG9hZCBhIG5ldyBkcmFmdC4gV2UgY2FuIGFzayBJRVNHIHRvIHJlLXJldmlldyBpdC4NCjxvOnA+
PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIj5UaGFuayB5b3UgdmVyeSBtdWNoLiA8bzpwPjwvbzpwPjwvcD4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1z
b05vcm1hbCI+TGluZGEgJmFtcDsgWW9hdi4gPG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxkaXY+DQo8ZGl2IHN0eWxlPSJib3JkZXI6
bm9uZTtib3JkZXItdG9wOnNvbGlkICNFMUUxRTEgMS4wcHQ7cGFkZGluZzozLjBwdCAwaW4gMGlu
IDBpbiI+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48Yj5Gcm9tOjwvYj4gTGluZGEgRHVuYmFyIDxi
cj4NCjxiPlNlbnQ6PC9iPiBNb25kYXksIFNlcHRlbWJlciAyOCwgMjAyMCAxMTowMCBBTTxicj4N
CjxiPlRvOjwvYj4gaTJuc2ZAaWV0Zi5vcmc8YnI+DQo8Yj5TdWJqZWN0OjwvYj4gSXMgdGhlcmUg
YW55IG9iamVjdGlvbiBvZiBzdW5zZXQgdGhlIEkyTlNGIENhcGFiaWxpdGllcyBJbmZvcm1hdGlv
biBNb2RlbCBEcmFmdCBhbmQgbWVyZ2UgdGhlIHJlbGV2YW50IGluZm9ybWF0aW9uIHRvIHRoZSBJ
Mk5TRiBDYXBhYmlsaXR5IERhdGEgbW9kZWwgZHJhZnQ/DQo8bzpwPjwvbzpwPjwvcD4NCjwvZGl2
Pg0KPC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiPkkyTlNGIFdHLCA8bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+QXMg
RGllZ28gaGFzIGV4cHJlc3NlZCB0aGF0IHRoZSBvcmlnaW5hbCBJMk5TRiBjYXBhYmlsaXR5IGlu
Zm9ybWF0aW9uIG1vZGVsIHdhcyBiYXNlZCBvbiBhIHBvbGljeSBleHByZXNzaW9uIGNhbGN1bHVz
IHN1aXRhYmxlIGZvciBtYW5pcHVsYXRpbmcgaGlnaC1sZXZlbCBwb2xpY3kgZXhwcmVzc2lvbnMu
Jm5ic3A7IFRoZSBjYXBhYmlsaXR5IGRhdGEgbW9kZWwgaGFzIGJlZW4gZXZvbHZpbmcgaW4gYSBx
dWl0ZSByZWFzb25hYmxlDQogYW5kIHByYWdtYXRpYyB3YXksIGluY2x1ZGluZyBydW5uaW5nIGNv
ZGUgYXQgdGhlIGhhY2thdGhvbnMuPG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPlRoZSBJMk5TRiBD
YXBhYmlsaXR5IEluZm9ybWF0aW9uIE1vZGVsIGhhcyBmdWxmaWxsZWQgaXRzIHB1cnBvc2Ugb2Yg
a2lja3N0YXJ0aW5nIGFuZCBndWlkaW5nIHRoZSBkYXRhIG1vZGVsLCBhbmQgdGhlIGF1dGhvcnMg
YmVsaWV2ZSB0aGF0IGl0IGlzIGJldHRlciB0byBsZXQgdGhlIGNhcGFiaWxpdHkgaW5mb3JtYXRp
b24gbW9kZWwgdG8gYmUgd2l0aGRyYXduLiBGb3IgdGhlIGNvbnRlbnQgaW4gdGhlIGluZm9ybWF0
aW9uDQogbW9kZWwgc3RpbGwgcmVsZXZhbnQgdG8gSTJOU0YgQ2FwYWJpbGl0eSBEYXRhIE1vZGVs
LCB0aGV5IHNob3VsZCBiZSBtZXJnZWQgaW50byB0aGUgQ2FwYWJpbGl0eSBEYXRhIE1vZGVsLg0K
PG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwv
cD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPklzIHRoZXJlIGFueSBvYmplY3Rpb24gZnJvbSB0aGUg
V0c/ICZuYnNwO0lmIHdlIGRvbuKAmXQgaGVhciBhbnkgb2JqZWN0aW9uIGJ5IE9jdCA1LCB3ZSB3
aWxsIGNoYW5nZSB0aGUgc3RhdHVzIG9mIHRoZSBkcmFmdC4NCjxvOnA+PC9vOnA+PC9wPg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9y
bWFsIj5DaGVlcnMsICZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOw0KPG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZu
YnNwOzwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPkxpbmRhICZhbXA7IFlvYXY8bzpw
PjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxkaXY+DQo8ZGl2IHN0eWxlPSJib3JkZXI6
bm9uZTtib3JkZXItdG9wOnNvbGlkICNFMUUxRTEgMS4wcHQ7cGFkZGluZzozLjBwdCAwaW4gMGlu
IDBpbiI+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48Yj5Gcm9tOjwvYj4gRGllZ28gUi4gTG9wZXog
Jmx0OzxhIGhyZWY9Im1haWx0bzpkaWVnby5yLmxvcGV6QHRlbGVmb25pY2EuY29tIj5kaWVnby5y
LmxvcGV6QHRlbGVmb25pY2EuY29tPC9hPiZndDsNCjxicj4NCjxiPlNlbnQ6PC9iPiBUdWVzZGF5
LCBTZXB0ZW1iZXIgMjIsIDIwMjAgNTozNSBQTTxicj4NCjxiPlRvOjwvYj4gTGluZGEgRHVuYmFy
ICZsdDs8YSBocmVmPSJtYWlsdG86bGluZGEuZHVuYmFyQGZ1dHVyZXdlaS5jb20iPmxpbmRhLmR1
bmJhckBmdXR1cmV3ZWkuY29tPC9hPiZndDs7IE1yLiBKYWVob29uIFBhdWwgSmVvbmcgJmx0Ozxh
IGhyZWY9Im1haWx0bzpqYWVob29uLnBhdWxAZ21haWwuY29tIj5qYWVob29uLnBhdWxAZ21haWwu
Y29tPC9hPiZndDs8YnI+DQo8Yj5DYzo8L2I+IFhpYWxpYW5nIChGcmFuaykgJmx0OzxhIGhyZWY9
Im1haWx0bzpmcmFuay54aWFsaWFuZ0BodWF3ZWkuY29tIj5mcmFuay54aWFsaWFuZ0BodWF3ZWku
Y29tPC9hPiZndDs7IFlvYXYgTmlyICZsdDs8YSBocmVmPSJtYWlsdG86eW5pci5pZXRmQGdtYWls
LmNvbSI+eW5pci5pZXRmQGdtYWlsLmNvbTwvYT4mZ3Q7OyBKb2huIFN0cmFzc25lciAmbHQ7PGEg
aHJlZj0ibWFpbHRvOkpvaG4uc2MuU3RyYXNzbmVyQGh1YXdlaS5jb20iPkpvaG4uc2MuU3RyYXNz
bmVyQGh1YXdlaS5jb208L2E+Jmd0OzsNCiBBbGRvIEJhc2lsZSAmbHQ7PGEgaHJlZj0ibWFpbHRv
OmNhdGFsZG8uYmFzaWxlQHBvbGl0by5pdCI+Y2F0YWxkby5iYXNpbGVAcG9saXRvLml0PC9hPiZn
dDs7IFJvbWFuIERhbnlsaXcgJmx0OzxhIGhyZWY9Im1haWx0bzpyZGRAY2VydC5vcmciPnJkZEBj
ZXJ0Lm9yZzwvYT4mZ3Q7PGJyPg0KPGI+U3ViamVjdDo8L2I+IFJlOiBPZmZlciBmb3IgUmV2aXNp
b24gSGVscCBmb3IgSTJOU0YgTlNGcyBDYXBhYmlsaXRpZXMgSW5mb3JtYXRpb24gTW9kZWwgRHJh
ZnQ8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48
bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVT
IiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDttc28tZmFyZWFzdC1sYW5ndWFnZTpFTi1VUyI+SGkg
TGluZGEsPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4g
bGFuZz0iRVMiIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O21zby1mYXJlYXN0LWxhbmd1YWdlOkVO
LVVTIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48
c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDttc28tZmFyZWFzdC1sYW5ndWFnZTpFTi1VUyI+
SeKAmWQgcHJlZmVyIHRoZSBzZWNvbmQgb3B0aW9uLCBhcyBpdCBzZWVtcyBtb3JlIHN0cmFpZ2h0
Zm9yd2FyZCBhbmQgbmF0dXJhbCB0byBtZSwgYW5kIGluIHBhcmFsbGVsIHdvdWxkIGxpa2UgeW91
IHRvIGNvbnNpZGVyIHRoZSBpZGVhIG9mIGFuIEkyTlNGIGV4dGVuc2lvbiBhbGxvd2luZyB1cyB0
byByZXVzZSB0aGUNCiBjYXBhYmlsaXR5IG1vZGVsIGZvciBwb2xpY3ktY29udHJvbCB0cmFuc2Zv
cm1hdGlvbiwgYW5kIHRvIGluY29ycG9yYXRlIHRoZSBhdHRlc3RhdGlvbiBtYXR0ZXJzIHlvdSBr
bm93IEkgd2FzIHNvIG11Y2ggaW50ZXJlc3RlZCBpbi48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDttc28tZmFy
ZWFzdC1sYW5ndWFnZTpFTi1VUyI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7bXNvLWZhcmVhc3Qt
bGFuZ3VhZ2U6RU4tVVMiPkJlIGdvb2RlLDxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O21zby1mYXJlYXN0LWxh
bmd1YWdlOkVOLVVTIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8ZGl2Pg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRVMiIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O21z
by1mYXJlYXN0LWxhbmd1YWdlOkVOLVVTIj4tLTxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtt
c28tZmFyZWFzdC1sYW5ndWFnZTpFTi1VUyI+JnF1b3Q7RXN0YSB2ZXogbm8gZmFsbGFyZW1vcywg
RG9jdG9yIEluZmllcm5vJnF1b3Q7PG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1z
b05vcm1hbCI+PHNwYW4gbGFuZz0iRVMiIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O21zby1mYXJl
YXN0LWxhbmd1YWdlOkVOLVVTIj4mbmJzcDs8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFz
cz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFUyIgc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7bXNv
LWZhcmVhc3QtbGFuZ3VhZ2U6RU4tVVMiPkRyIERpZWdvIFIuIExvcGV6PG86cD48L286cD48L3Nw
YW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRVMiIHN0eWxlPSJmb250
LXNpemU6MTAuMHB0O21zby1mYXJlYXN0LWxhbmd1YWdlOkVOLVVTIj5UZWxlZm9uaWNhIEkrRDxv
OnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVT
IiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDttc28tZmFyZWFzdC1sYW5ndWFnZTpFTi1VUyI+PGEg
aHJlZj0iaHR0cHM6Ly9uYW0xMS5zYWZlbGlua3MucHJvdGVjdGlvbi5vdXRsb29rLmNvbS8/dXJs
PWh0dHBzJTNBJTJGJTJGd3d3LmxpbmtlZGluLmNvbSUyRmluJTJGZHIybG9wZXolMkYmYW1wO2Rh
dGE9MDIlN0MwMSU3Q2xpbmRhLmR1bmJhciU0MGZ1dHVyZXdlaS5jb20lN0MwOGE0ODg1OGQ3YmQ0
ZDg0M2E2ZTA4ZDg1ZjQ3YjQzOCU3QzBmZWU4ZmYyYTNiMjQwMTg5Yzc1M2ExZDU1OTFmZWRjJTdD
MSU3QzAlN0M2MzczNjQxMDg4NjQ5NDk2MzMmYW1wO3NkYXRhPVJPUjQlMkZ5RDFXcVdEYjFyQ2JK
eDNFUnFUaU1DUTkyaWJreXoyNmtZWmREOCUzRCZhbXA7cmVzZXJ2ZWQ9MCI+PHNwYW4gc3R5bGU9
ImNvbG9yOiMwNTYzQzEiPmh0dHBzOi8vd3d3LmxpbmtlZGluLmNvbS9pbi9kcjJsb3Blei88L3Nw
YW4+PC9hPiZuYnNwOzxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
PjxzcGFuIGxhbmc9IkVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDttc28tZmFyZWFzdC1sYW5n
dWFnZTpFTi1VUyI+Jm5ic3A7PG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCI+PHNwYW4gbGFuZz0iRVMiIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O21zby1mYXJlYXN0
LWxhbmd1YWdlOkVOLVVTIj5lLW1haWw6Jm5ic3A7PC9zcGFuPjxzcGFuIGxhbmc9IkVOLUdCIiBz
dHlsZT0iZm9udC1zaXplOjEwLjBwdDttc28tZmFyZWFzdC1sYW5ndWFnZTpFTi1VUyI+PGEgaHJl
Zj0ibWFpbHRvOmRpZWdvLnIubG9wZXpAdGVsZWZvbmljYS5jb20iPjxzcGFuIGxhbmc9IkVTIiBz
dHlsZT0iY29sb3I6IzA1NjNDMSI+ZGllZ28uci5sb3BlekB0ZWxlZm9uaWNhLmNvbTwvc3Bhbj48
L2E+PC9zcGFuPjxzcGFuIGxhbmc9IkVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDttc28tZmFy
ZWFzdC1sYW5ndWFnZTpFTi1VUyI+PG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1z
b05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tR0IiIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O21zby1m
YXJlYXN0LWxhbmd1YWdlOkVOLVVTIj5UZWw6Jm5ic3A7Jm5ic3A7Jm5ic3A7ICZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOyArMzQgOTEzIDEyOSAwNDE8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1HQiIgc3R5bGU9ImZvbnQtc2l6ZToxMC4w
cHQ7bXNvLWZhcmVhc3QtbGFuZ3VhZ2U6RU4tVVMiPk1vYmlsZTogJm5ic3A7KzM0IDY4MiAwNTEg
MDkxPG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48
c3BhbiBsYW5nPSJFTi1HQiIgc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7bXNvLWZhcmVhc3QtbGFu
Z3VhZ2U6RU4tVVMiPi0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS08L3NwYW4+PHNw
YW4gc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7bXNvLWZhcmVhc3QtbGFuZ3VhZ2U6RU4tVVMiPjxv
OnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJm
b250LXNpemU6MTAuMHB0O21zby1mYXJlYXN0LWxhbmd1YWdlOkVOLVVTIj48bzpwPiZuYnNwOzwv
bzpwPjwvc3Bhbj48L3A+DQo8ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxl
PSJtYXJnaW4tbGVmdDouNWluIj5PbiAyMi8wOS8yMDIwLCAxODowMSwgJnF1b3Q7TGluZGEgRHVu
YmFyJnF1b3Q7ICZsdDs8YSBocmVmPSJtYWlsdG86bGluZGEuZHVuYmFyQGZ1dHVyZXdlaS5jb20i
PmxpbmRhLmR1bmJhckBmdXR1cmV3ZWkuY29tPC9hPiZndDsgd3JvdGU6PG86cD48L286cD48L3A+
DQo8L2Rpdj4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJn
aW4tbGVmdDouNWluIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1z
b05vcm1hbCIgc3R5bGU9Im1hcmdpbi1sZWZ0Oi41aW4iPkRpZWdvOiA8bzpwPjwvbzpwPjwvcD4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJnaW4tbGVmdDouNWluIj4mbmJzcDs8bzpw
PjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJnaW4tbGVmdDouNWlu
Ij5UaGFuayB5b3UgdmVyeSBtdWNoIGZvciB0aGUgcmVmbGVjdGlvbiBvZiB0aGUgQ2FwYWJpbGl0
aWVzIEluZm9ybWF0aW9uIE1vZGVsIERyYWZ0LiBBZ3JlZSB3aXRoIHlvdXIgc3RhdGVtZW50IHRo
YXQg4oCcdGhlIGNhcGFiaWxpdHkgZGF0YSBtb2RlbCB3YXMgZXZvbHZpbmcgaW4gYSBxdWl0ZSBy
ZWFzb25hYmxlIGFuZCBwcmFnbWF0aWMgd2F5LCBpbmNsdWRpbmcgcnVubmluZw0KIGNvZGUgYXQg
dGhlIGhhY2thdGhvbnPigJ0uIDxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIg
c3R5bGU9Im1hcmdpbi1sZWZ0Oi41aW4iPiZuYnNwOzxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCIgc3R5bGU9Im1hcmdpbi1sZWZ0Oi41aW4iPkxvb2tzIGxpa2UgRXJpYyBWeW5j
a2Ugc3RpbGwgd2FudHMgdGhlIGluZm9ybWF0aW9uIG1vZGVsIHRvIGJlIGZpeGVkIHRvIGNsZWFy
IGhpcyDigJxESVNDVVNT4oCdIGJhbGxvdC4NCjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1z
b05vcm1hbCIgc3R5bGU9Im1hcmdpbi1sZWZ0Oi41aW4iPkhvdyBhYm91dCB0aGUgZm9sbG93aW5n
IHN0ZXBzOjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb0xpc3RQYXJhZ3JhcGgiIHN0eWxl
PSJtYXJnaW4tbGVmdDoxLjBpbjt0ZXh0LWluZGVudDotLjI1aW47bXNvLWxpc3Q6bDAgbGV2ZWwx
IGxmbzIiPg0KPCFbaWYgIXN1cHBvcnRMaXN0c10+PHNwYW4gc3R5bGU9Im1zby1saXN0Oklnbm9y
ZSI+LTxzcGFuIHN0eWxlPSJmb250OjcuMHB0ICZxdW90O1RpbWVzIE5ldyBSb21hbiZxdW90OyI+
Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7DQo8
L3NwYW4+PC9zcGFuPjwhW2VuZGlmXT5Bc2sgUm9tYW7igJlzIGFkdmljZSBpZiB3ZSBjYW4gc2lt
cGxpZnkgdGhlIEluZm9ybWF0aW9uIE1vZGVsIG1haW5seSB0byByZWZsZWN0IHdoYXQgaGFzIGJl
ZW4gaW4gdGhlIERhdGEgTW9kZWwuPG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTGlzdFBh
cmFncmFwaCIgc3R5bGU9Im1hcmdpbi1sZWZ0OjEuMGluO3RleHQtaW5kZW50Oi0uMjVpbjttc28t
bGlzdDpsMCBsZXZlbDEgbGZvMiI+DQo8IVtpZiAhc3VwcG9ydExpc3RzXT48c3BhbiBzdHlsZT0i
bXNvLWxpc3Q6SWdub3JlIj4tPHNwYW4gc3R5bGU9ImZvbnQ6Ny4wcHQgJnF1b3Q7VGltZXMgTmV3
IFJvbWFuJnF1b3Q7Ij4mbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsm
bmJzcDsmbmJzcDsNCjwvc3Bhbj48L3NwYW4+PCFbZW5kaWZdPk9yLCBkcm9wIHRoZSBJbmZvcm1h
dGlvbiBtb2RlbCBkcmFmdCBhbmQgcmVtb3ZlIHRoZSByZWZlbmNlIHRvIHRoZSBkcmFmdCwgYnV0
IFJvbWFuIGhhcyB0byBjb252aW5jZSBFcmljIHRvIGFncmVlIG5vdCBoYXZpbmcgdGhlIGluZm9y
bWF0aW9uIG1vZGVsLg0KPG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHls
ZT0ibWFyZ2luLWxlZnQ6LjVpbiI+Jm5ic3A7PG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIiBzdHlsZT0ibWFyZ2luLWxlZnQ6LjVpbiI+V2hhdCBkbyB5b3UgdGhpbms/IDxvOnA+
PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1hcmdpbi1sZWZ0Oi41aW4i
PiZuYnNwOzxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1hcmdp
bi1sZWZ0Oi41aW4iPkxpbmRhPG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBz
dHlsZT0ibWFyZ2luLWxlZnQ6LjVpbiI+Jm5ic3A7PG86cD48L286cD48L3A+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIiBzdHlsZT0ibWFyZ2luLWxlZnQ6LjVpbiI+Jm5ic3A7PG86cD48L286cD48L3A+
DQo8ZGl2Pg0KPGRpdiBzdHlsZT0iYm9yZGVyOm5vbmU7Ym9yZGVyLXRvcDpzb2xpZCAjRTFFMUUx
IDEuMHB0O3BhZGRpbmc6My4wcHQgMGluIDBpbiAwaW4iPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIg
c3R5bGU9Im1hcmdpbi1sZWZ0Oi41aW4iPjxiPkZyb206PC9iPiBEaWVnbyBSLiBMb3BleiAmbHQ7
PGEgaHJlZj0ibWFpbHRvOmRpZWdvLnIubG9wZXpAdGVsZWZvbmljYS5jb20iPmRpZWdvLnIubG9w
ZXpAdGVsZWZvbmljYS5jb208L2E+Jmd0Ow0KPGJyPg0KPGI+U2VudDo8L2I+IFR1ZXNkYXksIFNl
cHRlbWJlciAyMiwgMjAyMCA5OjUwIEFNPGJyPg0KPGI+VG86PC9iPiBNci4gSmFlaG9vbiBQYXVs
IEplb25nICZsdDs8YSBocmVmPSJtYWlsdG86amFlaG9vbi5wYXVsQGdtYWlsLmNvbSI+amFlaG9v
bi5wYXVsQGdtYWlsLmNvbTwvYT4mZ3Q7OyBMaW5kYSBEdW5iYXIgJmx0OzxhIGhyZWY9Im1haWx0
bzpsaW5kYS5kdW5iYXJAZnV0dXJld2VpLmNvbSI+bGluZGEuZHVuYmFyQGZ1dHVyZXdlaS5jb208
L2E+Jmd0Ozxicj4NCjxiPkNjOjwvYj4gWGlhbGlhbmcgKEZyYW5rKSAmbHQ7PGEgaHJlZj0ibWFp
bHRvOmZyYW5rLnhpYWxpYW5nQGh1YXdlaS5jb20iPmZyYW5rLnhpYWxpYW5nQGh1YXdlaS5jb208
L2E+Jmd0OzsgWW9hdiBOaXIgJmx0OzxhIGhyZWY9Im1haWx0bzp5bmlyLmlldGZAZ21haWwuY29t
Ij55bmlyLmlldGZAZ21haWwuY29tPC9hPiZndDs7IEpvaG4gU3RyYXNzbmVyICZsdDs8YSBocmVm
PSJtYWlsdG86Sm9obi5zYy5TdHJhc3NuZXJAaHVhd2VpLmNvbSI+Sm9obi5zYy5TdHJhc3NuZXJA
aHVhd2VpLmNvbTwvYT4mZ3Q7Ow0KIEFsZG8gQmFzaWxlICZsdDs8YSBocmVmPSJtYWlsdG86Y2F0
YWxkby5iYXNpbGVAcG9saXRvLml0Ij5jYXRhbGRvLmJhc2lsZUBwb2xpdG8uaXQ8L2E+Jmd0Ozsg
Um9tYW4gRGFueWxpdyAmbHQ7PGEgaHJlZj0ibWFpbHRvOnJkZEBjZXJ0Lm9yZyI+cmRkQGNlcnQu
b3JnPC9hPiZndDs8YnI+DQo8Yj5TdWJqZWN0OjwvYj4gUmU6IE9mZmVyIGZvciBSZXZpc2lvbiBI
ZWxwIGZvciBJMk5TRiBOU0ZzIENhcGFiaWxpdGllcyBJbmZvcm1hdGlvbiBNb2RlbCBEcmFmdDxv
OnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxl
PSJtYXJnaW4tbGVmdDouNWluIj4mbmJzcDs8bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29O
b3JtYWwiIHN0eWxlPSJtYXJnaW4tbGVmdDouNWluIj48c3BhbiBjbGFzcz0iRW1haWxTdHlsZTIx
Ij48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdCI+SDwvc3Bhbj48L3NwYW4+PHNwYW4gY2xh
c3M9IkVtYWlsU3R5bGUyMSI+PHNwYW4gbGFuZz0iRVMiIHN0eWxlPSJmb250LXNpemU6MTAuMHB0
Ij5pIFBhdWwsPC9zcGFuPjwvc3Bhbj48bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3Jt
YWwiIHN0eWxlPSJtYXJnaW4tbGVmdDouNWluIj48c3BhbiBjbGFzcz0iRW1haWxTdHlsZTIxIj48
c3BhbiBsYW5nPSJFUyIgc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQiPiZuYnNwOzwvc3Bhbj48L3Nw
YW4+PG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibWFyZ2luLWxl
ZnQ6LjVpbiI+PHNwYW4gY2xhc3M9IkVtYWlsU3R5bGUyMSI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6
ZToxMC4wcHQiPkJlZm9yZSB5b3UgZ28gZm9yIGl0LCBsZXQgbWUgc2hhcmUgd2l0aCB5b3Ugc29t
ZSByZWZsZWN0aW9ucyBvbiB0aGUgc3RhdGUgb2YgdGhlIGRyYWZ0LCBpbiB0aGUgc3Bpcml0IG9m
IHdoYXQgSSByZXBsaWVkIHRvIEVyaWMgVnluY2tlLjwvc3Bhbj48L3NwYW4+PG86cD48L286cD48
L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibWFyZ2luLWxlZnQ6LjVpbiI+PHNwYW4g
Y2xhc3M9IkVtYWlsU3R5bGUyMSI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQiPiZuYnNw
Ozwvc3Bhbj48L3NwYW4+PG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHls
ZT0ibWFyZ2luLWxlZnQ6LjVpbiI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7bXNvLWZh
cmVhc3QtbGFuZ3VhZ2U6RU4tVVMiPkkgbXVzdCBjb25mZXNzIHRoZXJlIGhhcyBiZWVuIGEgY29t
YmluYXRpb24gb2YgZXZlbnRzIHRoYXQgbWFkZSBtZSB0aGluayB0aGUgYmVzdCBzb2x1dGlvbiB3
YXMgdG8gbGVhdmUgdGhpcyBkcmFmdCB0byBmYWRlIGF3YXkuIEZpcnN0LCBJIHdhcyBub3QgKGhh
dmUgbm90DQogYmVlbiB5ZXQpIGFibGUgdG8gZmluZCBhIHNvbHV0aW9uIHRvIG1vc3Qgb2YgUm9t
YW7igJlzIGNvbW1lbnRzIHdpdGhvdXQgdG90YWxseSByZXdyaXRpbmcgbW9zdCwgaWYgbm90IGFs
bCwgb2YgdGhlIGRvY3VtZW50LiZuYnNwOyBTZWNvbmQsIHRoZSBmYWN0IHRoYXQgdGhlIGNhcGFi
aWxpdHkgZGF0YSBtb2RlbCB3YXMgZXZvbHZpbmcgaW4gYSBxdWl0ZSByZWFzb25hYmxlIGFuZCBw
cmFnbWF0aWMgd2F5LCBpbmNsdWRpbmcgcnVubmluZyBjb2RlIGF0IHRoZQ0KIGhhY2thdGhvbnMs
IGZvbGxvd2luZyB0aGUgc3Bpcml0IG9mIHRoZSBpbml0aWFsIHdvcmsgaW4gdGhlIGluZm9ybWF0
aW9uIG1vZGVsLCBidXQgbm90IGF0dGVtcHRpbmcgdG8gYWxpZ24gd2l0aCBpdHMgbW9zdCByZWNl
bnQgZXZvbHV0aW9uLiBJZiBJIGhhdmUgbm90IHNoYXJlZCB0aGlzIHBvc2l0aW9uIGJlZm9yZSBp
cyBiZWNhdXNlIEkgaGF2ZSBiZWVuIGxvb2tpbmcgZm9yIGEgd2F5IHRvIG1ha2UgdGhlIGlkZWEg
b2YgYnJpZGdpbmcgY2FwYWJpbGl0eQ0KIGRlY2xhcmF0aW9ucyBhbmQgc2VjdXJpdHkgcG9saWN5
IHN0YXRlbWVudHMgYXQgdGhlIEkyTlNGIGNvbnRyb2xsZXIgdmlhYmxlLCBhbmQgSSB3YXMgaG9w
aW5nIHRvIGZpbmQgc3VjaCBhIHdheSBieSByZXVzaW5nIHBhcnQgb2YgdGhlIGNhcGFiaWxpdHkg
aW5mbyBtb2RlbCBkcmFmdC48L3NwYW4+PG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9y
bWFsIiBzdHlsZT0ibWFyZ2luLWxlZnQ6LjVpbiI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC4w
cHQ7bXNvLWZhcmVhc3QtbGFuZ3VhZ2U6RU4tVVMiPiZuYnNwOzwvc3Bhbj48bzpwPjwvbzpwPjwv
cD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJnaW4tbGVmdDouNWluIj48c3BhbiBz
dHlsZT0iZm9udC1zaXplOjEwLjBwdDttc28tZmFyZWFzdC1sYW5ndWFnZTpFTi1VUyI+QXMgSSB0
b2xkIEVyaWMsIEkgYmVsaWV2ZSB0aGUgY3VycmVudCBjYXBhYmlsaXR5IG1vZGVsIGhhcyBhIHBv
d2VyZnVsICh0aG91Z2ggcHJvYmFibHkgbm90IHlldCBjb21wbGV0ZSkgY2FsY3VsdXMgZm9yIHBv
bGljeSBkZXNjcmlwdGlvbiBhbmQgdmFsaWRhdGlvbiwNCiBidXQgbm90IGRpcmVjdGx5IHJlbGF0
ZWQgdG8gdGhlIG1hbmFnZW1lbnQgbWVjaGFuaXNtcyBhZGRyZXNzZWQgaW4gdGhlIGNhcGFiaWxp
dHkgZGF0YSBtb2RlbCBhbmQgdGhlIG90aGVyIGRhdGEgbW9kZWxzIHByb2R1Y2VkIGluIEkyTlNG
LiBJIGJlbGlldmUgdGhlcmUgaXMgYW4gb3Bwb3J0dW5pdHkgZm9yIGFjY29tcGxpc2hpbmcgcG9s
aWN5LWNhcGFiaWxpdHkgYnJpZGdpbmcsIHVzaW5nIGFzIGZvdW5kYXRpb24gdGhlIGN1cnJlbnQg
Y2FwYWJpbGl0eQ0KIG1vZGVsLCB0aG91Z2ggaXQgc2VlbXMgdG8gbWUgdGhhdCB0aGlzIHRhc2sg
d291bGQgcmVxdWlyZSBzb21lIHRpbWUgdG8gY29uc29saWRhdGUgYW5kIHRoZXJlZm9yZSBpbXBs
eSBhbiBleHRlbnNpb24gb2YgdGhlIEkyTlNGIGxpZmV0aW1lLiBJIHdvdWxkIGxpa2UgdG8ga25v
dyB5b3VyIHBvc2l0aW9uKCopIGFib3V0IHN1Y2ggYW4gZXh0ZW5zaW9uLCAmbmJzcDt0aGF0IGNv
dWxkIGFsc28gYmVjb21lIGFuIG9wcG9ydHVuaXR5IHRvIHdvcmsgaW4gb3RoZXINCiBtYXR0ZXJz
IHJlbGF0ZWQgdG8gYXR0ZXN0YXRpb24gKGluIHRoZSBsaWdodCBvZiB0aGUgd29yayBpbiBSQVRT
IGFuZCB0aGUgTVVEIGluaXRpYXRpdmUgd2l0aGluIHRoZSBPcHMgQXJlYSkgYW5kIGFjY291bnRp
bmcuPC9zcGFuPjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1h
cmdpbi1sZWZ0Oi41aW4iPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O21zby1mYXJlYXN0
LWxhbmd1YWdlOkVOLVVTIj4mbmJzcDs8L3NwYW4+PG86cD48L286cD48L3A+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIiBzdHlsZT0ibWFyZ2luLWxlZnQ6LjVpbiI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6
ZToxMC4wcHQ7bXNvLWZhcmVhc3QtbGFuZ3VhZ2U6RU4tVVMiPkJlIGdvb2RlLDwvc3Bhbj48bzpw
PjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJnaW4tbGVmdDouNWlu
Ij48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDttc28tZmFyZWFzdC1sYW5ndWFnZTpFTi1V
UyI+Jm5ic3A7PC9zcGFuPjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5
bGU9Im1hcmdpbi1sZWZ0Oi41aW4iPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O21zby1m
YXJlYXN0LWxhbmd1YWdlOkVOLVVTIj4oKikgSSBhc3N1bWUgeW91IGFyZSBpbiBmYXZvciwgUGF1
bC4gQnV0IEnigJlkIGxpa2UgdG8gZ2V0IExpbmRh4oCZcywgWW9hduKAmXMgYW5kIFJvbWFu4oCZ
cyBpZGVhcywgYXMgd2VsbCBhcyB0aGUgYXZhaWxhYmlsaXR5IHRvIHdvcmsgb24gdGhpcyBmcm9t
IEZyYW5rLCBKb2huDQogYW5kIEFsZG8uPC9zcGFuPjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCIgc3R5bGU9Im1hcmdpbi1sZWZ0Oi41aW4iPjxzcGFuIHN0eWxlPSJmb250LXNp
emU6MTAuMHB0O21zby1mYXJlYXN0LWxhbmd1YWdlOkVOLVVTIj4mbmJzcDs8L3NwYW4+PG86cD48
L286cD48L3A+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1hcmdpbi1sZWZ0
Oi41aW4iPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O21zby1mYXJlYXN0LWxhbmd1YWdl
OkVOLVVTIj4tLTwvc3Bhbj48bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0
eWxlPSJtYXJnaW4tbGVmdDouNWluIj48c3BhbiBsYW5nPSJFUyIgc3R5bGU9ImZvbnQtc2l6ZTox
MC4wcHQ7bXNvLWZhcmVhc3QtbGFuZ3VhZ2U6RU4tVVMiPiZxdW90O0VzdGEgdmV6IG5vIGZhbGxh
cmVtb3MsIERvY3RvciBJbmZpZXJubyZxdW90Ozwvc3Bhbj48bzpwPjwvbzpwPjwvcD4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJnaW4tbGVmdDouNWluIj48c3BhbiBsYW5nPSJFUyIg
c3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7bXNvLWZhcmVhc3QtbGFuZ3VhZ2U6RU4tVVMiPiZuYnNw
Ozwvc3Bhbj48bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJn
aW4tbGVmdDouNWluIj48c3BhbiBsYW5nPSJFUyIgc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7bXNv
LWZhcmVhc3QtbGFuZ3VhZ2U6RU4tVVMiPkRyIERpZWdvIFIuIExvcGV6PC9zcGFuPjxvOnA+PC9v
OnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1hcmdpbi1sZWZ0Oi41aW4iPjxz
cGFuIGxhbmc9IkVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDttc28tZmFyZWFzdC1sYW5ndWFn
ZTpFTi1VUyI+VGVsZWZvbmljYSBJK0Q8L3NwYW4+PG86cD48L286cD48L3A+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIiBzdHlsZT0ibWFyZ2luLWxlZnQ6LjVpbiI+PHNwYW4gbGFuZz0iRVMiIHN0eWxl
PSJmb250LXNpemU6MTAuMHB0O21zby1mYXJlYXN0LWxhbmd1YWdlOkVOLVVTIj48YSBocmVmPSJo
dHRwczovL25hbTExLnNhZmVsaW5rcy5wcm90ZWN0aW9uLm91dGxvb2suY29tLz91cmw9aHR0cHMl
M0ElMkYlMkZ3d3cubGlua2VkaW4uY29tJTJGaW4lMkZkcjJsb3BleiUyRiZhbXA7ZGF0YT0wMiU3
QzAxJTdDbGluZGEuZHVuYmFyJTQwZnV0dXJld2VpLmNvbSU3QzA4YTQ4ODU4ZDdiZDRkODQzYTZl
MDhkODVmNDdiNDM4JTdDMGZlZThmZjJhM2IyNDAxODljNzUzYTFkNTU5MWZlZGMlN0MxJTdDMCU3
QzYzNzM2NDEwODg2NDk0OTYzMyZhbXA7c2RhdGE9Uk9SNCUyRnlEMVdxV0RiMXJDYkp4M0VScVRp
TUNROTJpYmt5ejI2a1laZEQ4JTNEJmFtcDtyZXNlcnZlZD0wIj48c3BhbiBzdHlsZT0iY29sb3I6
IzA1NjNDMSI+aHR0cHM6Ly93d3cubGlua2VkaW4uY29tL2luL2RyMmxvcGV6Lzwvc3Bhbj48L2E+
Jm5ic3A7PC9zcGFuPjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9
Im1hcmdpbi1sZWZ0Oi41aW4iPjxzcGFuIGxhbmc9IkVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjBw
dDttc28tZmFyZWFzdC1sYW5ndWFnZTpFTi1VUyI+Jm5ic3A7PC9zcGFuPjxvOnA+PC9vOnA+PC9w
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1hcmdpbi1sZWZ0Oi41aW4iPjxzcGFuIGxh
bmc9IkVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDttc28tZmFyZWFzdC1sYW5ndWFnZTpFTi1V
UyI+ZS1tYWlsOiZuYnNwOzwvc3Bhbj48c3BhbiBsYW5nPSJFTi1HQiIgc3R5bGU9ImZvbnQtc2l6
ZToxMC4wcHQ7bXNvLWZhcmVhc3QtbGFuZ3VhZ2U6RU4tVVMiPjxhIGhyZWY9Im1haWx0bzpkaWVn
by5yLmxvcGV6QHRlbGVmb25pY2EuY29tIj48c3BhbiBsYW5nPSJFUyIgc3R5bGU9ImNvbG9yOiMw
NTYzQzEiPmRpZWdvLnIubG9wZXpAdGVsZWZvbmljYS5jb208L3NwYW4+PC9hPjwvc3Bhbj48bzpw
PjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJnaW4tbGVmdDouNWlu
Ij48c3BhbiBsYW5nPSJFTi1HQiIgc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7bXNvLWZhcmVhc3Qt
bGFuZ3VhZ2U6RU4tVVMiPlRlbDombmJzcDsmbmJzcDsmbmJzcDsgJm5ic3A7Jm5ic3A7Jm5ic3A7
Jm5ic3A7ICszNCA5MTMgMTI5IDA0MTwvc3Bhbj48bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiIHN0eWxlPSJtYXJnaW4tbGVmdDouNWluIj48c3BhbiBsYW5nPSJFTi1HQiIgc3R5
bGU9ImZvbnQtc2l6ZToxMC4wcHQ7bXNvLWZhcmVhc3QtbGFuZ3VhZ2U6RU4tVVMiPk1vYmlsZTog
Jm5ic3A7KzM0IDY4MiAwNTEgMDkxPC9zcGFuPjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibWFyZ2luLWxlZnQ6LjVpbiI+PHNwYW4gbGFuZz0iRU4t
R0IiIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O21zby1mYXJlYXN0LWxhbmd1YWdlOkVOLVVTIj4t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tPC9zcGFuPjxvOnA+PC9vOnA+PC9wPg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1hcmdpbi1sZWZ0Oi41aW4iPjxzcGFuIHN0eWxl
PSJmb250LXNpemU6MTAuMHB0O21zby1mYXJlYXN0LWxhbmd1YWdlOkVOLVVTIj4mbmJzcDs8L3Nw
YW4+PG86cD48L286cD48L3A+DQo8ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0
eWxlPSJtYXJnaW4tbGVmdDoxLjBpbiI+T24gMTcvMDkvMjAyMCwgMDE6NDIsICZxdW90O01yLiBK
YWVob29uIFBhdWwgSmVvbmcmcXVvdDsgJmx0OzxhIGhyZWY9Im1haWx0bzpqYWVob29uLnBhdWxA
Z21haWwuY29tIj5qYWVob29uLnBhdWxAZ21haWwuY29tPC9hPiZndDsgd3JvdGU6PG86cD48L286
cD48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxl
PSJtYXJnaW4tbGVmdDoxLjBpbiI+Jm5ic3A7PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibWFyZ2luLWxlZnQ6MS4waW4iPkhpIExpbmRh
LDxvOnA+PC9vOnA+PC9wPg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJn
aW4tbGVmdDoxLjBpbiI+SSB3aWxsIGFkZHJlc3Mgb3VyIEFEIFJvbWFuJ3MgY29tbWVudHMgb24g
dGhpcyBOU0ZzIGNhcGFiaWxpdGllcyBpbmZvcm1hdGlvbiBkcmFmdCBhcyB0aGUgMm5kIGVkaXRv
ciB0aHJvdWdoIHRoZSBjb2xsYWJvcmF0aW9uIHdpdGggRnJhbmsgKHRoZSAxc3QgZWRpdG9yKSBh
bmQgdGhlIG90aGVyIGF1dGhvcnMuPG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibWFyZ2luLWxlZnQ6MS4waW4iPiZuYnNwOzxvOnA+PC9v
OnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1hcmdp
bi1sZWZ0OjEuMGluIj5JIENDIG91ciBBRCBSb21hbiBhbmQgdGhlIG90aGVyIGF1dGhvcnMsIHN1
Y2ggYXMgSm9obiBhbmQgQ2F0YWxkby48bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxw
cmUgc3R5bGU9Im1hcmdpbi1sZWZ0OjEuMGluIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjkuNXB0
Ij4mbmJzcDs8L3NwYW4+PG86cD48L286cD48L3ByZT4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJnaW4tbGVmdDoxLjBpbiI+VGhhbmtzIGZvciB5b3VyIHN1
cHBvcnQgYW5kIGd1aWRhbmNlLjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1hcmdpbi1sZWZ0OjEuMGluIj4mbmJzcDs8bzpwPjwvbzpw
PjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJnaW4t
bGVmdDoxLjBpbiI+QmVzdCBSZWdhcmRzLDxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1hcmdpbi1sZWZ0OjEuMGluIj5QYXVsPG86cD48
L286cD48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1h
cmdpbi1sZWZ0OjEuMGluIj4mbmJzcDs8bzpwPjwvbzpwPjwvcD4NCjxkaXY+DQo8ZGl2Pg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1hcmdpbi1sZWZ0OjEuMGluIj4yMDIwPHNwYW4gbGFu
Zz0iWkgtQ04iIHN0eWxlPSJmb250LWZhbWlseTomcXVvdDtNYWxndW4gR290aGljJnF1b3Q7LHNh
bnMtc2VyaWYiPuuFhDwvc3Bhbj4gOTxzcGFuIGxhbmc9IlpILUNOIiBzdHlsZT0iZm9udC1mYW1p
bHk6JnF1b3Q7TWFsZ3VuIEdvdGhpYyZxdW90OyxzYW5zLXNlcmlmIj7sm5Q8L3NwYW4+IDE3PHNw
YW4gbGFuZz0iWkgtQ04iIHN0eWxlPSJmb250LWZhbWlseTomcXVvdDtNYWxndW4gR290aGljJnF1
b3Q7LHNhbnMtc2VyaWYiPuydvDwvc3Bhbj4NCiAoPHNwYW4gbGFuZz0iWkgtQ04iIHN0eWxlPSJm
b250LWZhbWlseTomcXVvdDtNYWxndW4gR290aGljJnF1b3Q7LHNhbnMtc2VyaWYiPuuqqTwvc3Bh
bj4pIDxzcGFuIGxhbmc9IlpILUNOIiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7TWFsZ3VuIEdv
dGhpYyZxdW90OyxzYW5zLXNlcmlmIj4NCuyYpOyghDwvc3Bhbj48c3BhbiBsYW5nPSJaSC1DTiI+
IDwvc3Bhbj4zOjQ0LCBMaW5kYSBEdW5iYXIgJmx0OzxhIGhyZWY9Im1haWx0bzpsaW5kYS5kdW5i
YXJAZnV0dXJld2VpLmNvbSI+bGluZGEuZHVuYmFyQGZ1dHVyZXdlaS5jb208L2E+Jmd0OzxzcGFu
IGxhbmc9IlpILUNOIiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7TWFsZ3VuIEdvdGhpYyZxdW90
OyxzYW5zLXNlcmlmIj7ri5jsnbQ8L3NwYW4+PHNwYW4gbGFuZz0iWkgtQ04iPg0KPC9zcGFuPjxz
cGFuIGxhbmc9IlpILUNOIiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7TWFsZ3VuIEdvdGhpYyZx
dW90OyxzYW5zLXNlcmlmIj7snpHshLE8L3NwYW4+OjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8
YmxvY2txdW90ZSBzdHlsZT0iYm9yZGVyOm5vbmU7Ym9yZGVyLWxlZnQ6c29saWQgI0NDQ0NDQyAx
LjBwdDtwYWRkaW5nOjBpbiAwaW4gMGluIDYuMHB0O21hcmdpbi1sZWZ0OjQuOHB0O21hcmdpbi10
b3A6NS4wcHQ7bWFyZ2luLXJpZ2h0OjBpbjttYXJnaW4tYm90dG9tOjUuMHB0Ij4NCjxkaXY+DQo8
ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRv
O21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvO21hcmdpbi1sZWZ0OjEuMGluIj4NClBhdWwsIDxv
OnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9w
LWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvO21hcmdpbi1sZWZ0OjEuMGluIj4N
CiZuYnNwOzxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1t
YXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvO21hcmdpbi1sZWZ0
OjEuMGluIj4NClRoYW5rIHlvdSB2ZXJ5IG11Y2ggZm9yIG9mZmVyaW5nIHRvIGFkZHJlc3MgdGhl
IEFEIGNvbW1lbnRzIHRvIHRoaXMgZHJhZnQuIExvb2tzIGxpa2UgdGhlIGN1cnJlbnQgYXV0aG9y
cyBhcmUgdG9vIGJ1c3kgdG8gYWRkcmVzcyB0aG9zZSBjb21tZW50cy4gSXQgaGFzIGJlZW4gb3Zl
ciBhIHllYXIgc2luY2UgdGhlIEFEIGNvbW1lbnRzIHdlcmUgZ2l2ZW4uJm5ic3A7IFdlIG5lZWQg
dG8gbW92ZSB0aGUgZHJhZnQgZm9yd2FyZC4gVGhlcmVmb3JlLCBJMk5TRg0KIGNoYWlycyBoYXZl
IGF1dGhvcml6ZWQgeW91IHRvIGJlIG9uZSBvZiB0aGUgZWRpdG9ycyB0byBhZGRyZXNzIHRoZSBB
RCBjb21tZW50cyBhbmQgcmV2aXNlIHRoZSBkcmFmdC4NCjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4t
Ym90dG9tLWFsdDphdXRvO21hcmdpbi1sZWZ0OjEuMGluIj4NCiZuYnNwOzxvOnA+PC9vOnA+PC9w
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21z
by1tYXJnaW4tYm90dG9tLWFsdDphdXRvO21hcmdpbi1sZWZ0OjEuMGluIj4NCiZuYnNwOzxvOnA+
PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFs
dDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvO21hcmdpbi1sZWZ0OjEuMGluIj4NClRo
YW5rIHlvdSB2ZXJ5IG11Y2guIDxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIg
c3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRv
O21hcmdpbi1sZWZ0OjEuMGluIj4NCiZuYnNwOzxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1z
b05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9t
LWFsdDphdXRvO21hcmdpbi1sZWZ0OjEuMGluIj4NCkxpbmRhICZhbXA7IFlvYXY8bzpwPjwvbzpw
PjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0
bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0bzttYXJnaW4tbGVmdDoxLjBpbiI+DQombmJzcDs8
bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRv
cC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0bzttYXJnaW4tbGVmdDoxLjBpbiI+
DQombmJzcDs8bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28t
bWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0bzttYXJnaW4tbGVm
dDoxLjBpbiI+DQo8Yj5Gcm9tOjwvYj4gTXIuIEphZWhvb24gUGF1bCBKZW9uZyAmbHQ7PGEgaHJl
Zj0ibWFpbHRvOmphZWhvb24ucGF1bEBnbWFpbC5jb20iIHRhcmdldD0iX2JsYW5rIj5qYWVob29u
LnBhdWxAZ21haWwuY29tPC9hPiZndDsNCjxicj4NCjxiPlNlbnQ6PC9iPiBTdW5kYXksIFNlcHRl
bWJlciAxMywgMjAyMCAxMDowOSBBTTxicj4NCjxiPlRvOjwvYj4gWGlhbGlhbmcgKEZyYW5rKSAm
bHQ7PGEgaHJlZj0ibWFpbHRvOmZyYW5rLnhpYWxpYW5nQGh1YXdlaS5jb20iIHRhcmdldD0iX2Js
YW5rIj5mcmFuay54aWFsaWFuZ0BodWF3ZWkuY29tPC9hPiZndDs8YnI+DQo8Yj5DYzo8L2I+IExp
bmRhIER1bmJhciAmbHQ7PGEgaHJlZj0ibWFpbHRvOmxpbmRhLmR1bmJhckBmdXR1cmV3ZWkuY29t
IiB0YXJnZXQ9Il9ibGFuayI+bGluZGEuZHVuYmFyQGZ1dHVyZXdlaS5jb208L2E+Jmd0OzsgWW9h
diBOaXIgJmx0OzxhIGhyZWY9Im1haWx0bzp5bmlyLmlldGZAZ21haWwuY29tIiB0YXJnZXQ9Il9i
bGFuayI+eW5pci5pZXRmQGdtYWlsLmNvbTwvYT4mZ3Q7OyBESUVHTyBMT1BFWiBHQVJDSUEgJmx0
OzxhIGhyZWY9Im1haWx0bzpkaWVnby5yLmxvcGV6QHRlbGVmb25pY2EuY29tIiB0YXJnZXQ9Il9i
bGFuayI+ZGllZ28uci5sb3BlekB0ZWxlZm9uaWNhLmNvbTwvYT4mZ3Q7Ow0KIEphZWhvb24gSmVv
bmcgJmx0OzxhIGhyZWY9Im1haWx0bzpqYWVob29uLnBhdWxAZ21haWwuY29tIiB0YXJnZXQ9Il9i
bGFuayI+amFlaG9vbi5wYXVsQGdtYWlsLmNvbTwvYT4mZ3Q7PGJyPg0KPGI+U3ViamVjdDo8L2I+
IE9mZmVyIGZvciBSZXZpc2lvbiBIZWxwIGZvciBJMk5TRiBOU0ZzIENhcGFiaWxpdGllcyBJbmZv
cm1hdGlvbiBNb2RlbCBEcmFmdDxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIg
c3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRv
O21hcmdpbi1sZWZ0OjEuMGluIj4NCiZuYnNwOzxvOnA+PC9vOnA+PC9wPg0KPGRpdj4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2lu
LWJvdHRvbS1hbHQ6YXV0bzttYXJnaW4tbGVmdDoxLjBpbiI+DQpIaSBGcmFuayw8bzpwPjwvbzpw
PjwvcD4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3At
YWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG87bWFyZ2luLWxlZnQ6MS4waW4iPg0K
Q291bGQgSSBoZWxwIHlvdSB0byByZXZpc2UgeW91ciBpbmZvcm1hdGlvbiBtb2RlbCBkcmFmdCBm
b3Igb3VyIEFEIFJvbWFuIERhbnlsaXcncyByZXZpZXcgY29tbWVudHMmbmJzcDsgYXMgYSBjby1l
ZGl0b3I/PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
IiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1
dG87bWFyZ2luLWxlZnQ6MS4waW4iPg0KPGEgaHJlZj0iaHR0cHM6Ly9uYW0xMS5zYWZlbGlua3Mu
cHJvdGVjdGlvbi5vdXRsb29rLmNvbS8/dXJsPWh0dHBzJTNBJTJGJTJGZGF0YXRyYWNrZXIuaWV0
Zi5vcmclMkZkb2MlMkZkcmFmdC1pZXRmLWkybnNmLWNhcGFiaWxpdHklMkYlM0ZpbmNsdWRlX3Rl
eHQlM0QxJmFtcDtkYXRhPTAyJTdDMDElN0NsaW5kYS5kdW5iYXIlNDBmdXR1cmV3ZWkuY29tJTdD
MDhhNDg4NThkN2JkNGQ4NDNhNmUwOGQ4NWY0N2I0MzglN0MwZmVlOGZmMmEzYjI0MDE4OWM3NTNh
MWQ1NTkxZmVkYyU3QzElN0MwJTdDNjM3MzY0MTA4ODY0OTU5NjI2JmFtcDtzZGF0YT1HVXJiYVl1
MlE0TjFZTlVVZXQyb1ZSUHFieW5BNzhjU0JUZiUyRkJlU0NZNDQlM0QmYW1wO3Jlc2VydmVkPTAi
IHRhcmdldD0iX2JsYW5rIj5odHRwczovL2RhdGF0cmFja2VyLmlldGYub3JnL2RvYy9kcmFmdC1p
ZXRmLWkybnNmLWNhcGFiaWxpdHkvP2luY2x1ZGVfdGV4dD0xPC9hPjxvOnA+PC9vOnA+PC9wPg0K
PC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9w
LWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvO21hcmdpbi1sZWZ0OjEuMGluIj4N
CiZuYnNwOzxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1h
bCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDph
dXRvO21hcmdpbi1sZWZ0OjEuMGluIj4NCkFzIHlvdSBrbm93LCBJIGhhdmUgZmluaXNoZWQgb3Vy
IEkyTlNGIGRhdGEgbW9kZWwgZHJhZnRzLjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1t
YXJnaW4tYm90dG9tLWFsdDphdXRvO21hcmdpbi1sZWZ0OjEuMGluIj4NCiZuYnNwOzxvOnA+PC9v
OnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1t
YXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvO21hcmdpbi1sZWZ0
OjEuMGluIj4NCkkgYW0gaGFwcHkgdG8gd29yayBvbiB0aGUgcmV2aXNpb24gd2l0aCB5b3UgaW4g
b3JkZXIgdG8gY29tcGxldGUgb3VyIEkyTlNGIGRlbGl2ZXJhYmxlcy48bzpwPjwvbzpwPjwvcD4N
CjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRv
cC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0bzttYXJnaW4tbGVmdDoxLjBpbiI+
DQombmJzcDs8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3Jt
YWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6
YXV0bzttYXJnaW4tbGVmdDoxLjBpbiI+DQpUaGFua3MuPG86cD48L286cD48L3A+DQo8L2Rpdj4N
CjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1
dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG87bWFyZ2luLWxlZnQ6MS4waW4iPg0KJm5ic3A7
PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHls
ZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG87bWFy
Z2luLWxlZnQ6MS4waW4iPg0KQmVzdCBSZWdhcmRzLDxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8
ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRv
O21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvO21hcmdpbi1sZWZ0OjEuMGluIj4NClBhdWw8bzpw
PjwvbzpwPjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9ibG9ja3F1b3Rl
Pg0KPC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibWFyZ2luLWxlZnQ6LjVpbiI+
Jm5ic3A7PG86cD48L286cD48L3A+DQo8ZGl2IHN0eWxlPSJtYXJnaW4tbGVmdDouNWluIj4NCjxk
aXYgY2xhc3M9Ik1zb05vcm1hbCIgYWxpZ249ImNlbnRlciIgc3R5bGU9InRleHQtYWxpZ246Y2Vu
dGVyIj4NCjxociBzaXplPSIxIiB3aWR0aD0iMTAwJSIgYWxpZ249ImNlbnRlciI+DQo8L2Rpdj4N
CjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1hcmdpbi1sZWZ0Oi41aW4iPjxz
cGFuIHN0eWxlPSJmb250LXNpemU6Ny41cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwmcXVvdDss
c2Fucy1zZXJpZjtjb2xvcjpncmF5Ij48YnI+DQpFc3RlIG1lbnNhamUgeSBzdXMgYWRqdW50b3Mg
c2UgZGlyaWdlbiBleGNsdXNpdmFtZW50ZSBhIHN1IGRlc3RpbmF0YXJpbywgcHVlZGUgY29udGVu
ZXIgaW5mb3JtYWNpw7NuIHByaXZpbGVnaWFkYSBvIGNvbmZpZGVuY2lhbCB5IGVzIHBhcmEgdXNv
IGV4Y2x1c2l2byBkZSBsYSBwZXJzb25hIG8gZW50aWRhZCBkZSBkZXN0aW5vLiBTaSBubyBlcyB1
c3RlZC4gZWwgZGVzdGluYXRhcmlvIGluZGljYWRvLCBxdWVkYSBub3RpZmljYWRvIGRlIHF1ZSBs
YQ0KIGxlY3R1cmEsIHV0aWxpemFjacOzbiwgZGl2dWxnYWNpw7NuIHkvbyBjb3BpYSBzaW4gYXV0
b3JpemFjacOzbiBwdWVkZSBlc3RhciBwcm9oaWJpZGEgZW4gdmlydHVkIGRlIGxhIGxlZ2lzbGFj
acOzbiB2aWdlbnRlLiBTaSBoYSByZWNpYmlkbyBlc3RlIG1lbnNhamUgcG9yIGVycm9yLCBsZSBy
b2dhbW9zIHF1ZSBub3MgbG8gY29tdW5pcXVlIGlubWVkaWF0YW1lbnRlIHBvciBlc3RhIG1pc21h
IHbDrWEgeSBwcm9jZWRhIGEgc3UgZGVzdHJ1Y2Npw7NuLjxicj4NCjxicj4NClRoZSBpbmZvcm1h
dGlvbiBjb250YWluZWQgaW4gdGhpcyB0cmFuc21pc3Npb24gaXMgcHJpdmlsZWdlZCBhbmQgY29u
ZmlkZW50aWFsIGluZm9ybWF0aW9uIGludGVuZGVkIG9ubHkgZm9yIHRoZSB1c2Ugb2YgdGhlIGlu
ZGl2aWR1YWwgb3IgZW50aXR5IG5hbWVkIGFib3ZlLiBJZiB0aGUgcmVhZGVyIG9mIHRoaXMgbWVz
c2FnZSBpcyBub3QgdGhlIGludGVuZGVkIHJlY2lwaWVudCwgeW91IGFyZSBoZXJlYnkgbm90aWZp
ZWQgdGhhdCBhbnkgZGlzc2VtaW5hdGlvbiwNCiBkaXN0cmlidXRpb24gb3IgY29weWluZyBvZiB0
aGlzIGNvbW11bmljYXRpb24gaXMgc3RyaWN0bHkgcHJvaGliaXRlZC4gSWYgeW91IGhhdmUgcmVj
ZWl2ZWQgdGhpcyB0cmFuc21pc3Npb24gaW4gZXJyb3IsIGRvIG5vdCByZWFkIGl0LiBQbGVhc2Ug
aW1tZWRpYXRlbHkgcmVwbHkgdG8gdGhlIHNlbmRlciB0aGF0IHlvdSBoYXZlIHJlY2VpdmVkIHRo
aXMgY29tbXVuaWNhdGlvbiBpbiBlcnJvciBhbmQgdGhlbiBkZWxldGUgaXQuPGJyPg0KPGJyPg0K
RXN0YSBtZW5zYWdlbSBlIHNldXMgYW5leG9zIHNlIGRpcmlnZW0gZXhjbHVzaXZhbWVudGUgYW8g
c2V1IGRlc3RpbmF0w6FyaW8sIHBvZGUgY29udGVyIGluZm9ybWHDp8OjbyBwcml2aWxlZ2lhZGEg
b3UgY29uZmlkZW5jaWFsIGUgw6kgcGFyYSB1c28gZXhjbHVzaXZvIGRhIHBlc3NvYSBvdSBlbnRp
ZGFkZSBkZSBkZXN0aW5vLiBTZSBuw6NvIMOpIHZvc3NhIHNlbmhvcmlhIG8gZGVzdGluYXTDoXJp
byBpbmRpY2FkbywgZmljYSBub3RpZmljYWRvIGRlIHF1ZSBhDQogbGVpdHVyYSwgdXRpbGl6YcOn
w6NvLCBkaXZ1bGdhw6fDo28gZS9vdSBjw7NwaWEgc2VtIGF1dG9yaXphw6fDo28gcG9kZSBlc3Rh
ciBwcm9pYmlkYSBlbSB2aXJ0dWRlIGRhIGxlZ2lzbGHDp8OjbyB2aWdlbnRlLiBTZSByZWNlYmV1
IGVzdGEgbWVuc2FnZW0gcG9yIGVycm8sIHJvZ2Ftb3MtbGhlIHF1ZSBub3MgbyBjb211bmlxdWUg
aW1lZGlhdGFtZW50ZSBwb3IgZXN0YSBtZXNtYSB2aWEgZSBwcm9jZWRhIGEgc3VhIGRlc3RydWnD
p8Ojbzwvc3Bhbj48bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5i
c3A7PC9vOnA+PC9wPg0KPGRpdiBjbGFzcz0iTXNvTm9ybWFsIiBhbGlnbj0iY2VudGVyIiBzdHls
ZT0idGV4dC1hbGlnbjpjZW50ZXIiPg0KPGhyIHNpemU9IjIiIHdpZHRoPSIxMDAlIiBhbGlnbj0i
Y2VudGVyIj4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQt
c2l6ZTo3LjVwdDtmb250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90OyxzYW5zLXNlcmlmO2NvbG9y
OmdyYXkiPjxicj4NCkVzdGUgbWVuc2FqZSB5IHN1cyBhZGp1bnRvcyBzZSBkaXJpZ2VuIGV4Y2x1
c2l2YW1lbnRlIGEgc3UgZGVzdGluYXRhcmlvLCBwdWVkZSBjb250ZW5lciBpbmZvcm1hY2nDs24g
cHJpdmlsZWdpYWRhIG8gY29uZmlkZW5jaWFsIHkgZXMgcGFyYSB1c28gZXhjbHVzaXZvIGRlIGxh
IHBlcnNvbmEgbyBlbnRpZGFkIGRlIGRlc3Rpbm8uIFNpIG5vIGVzIHVzdGVkLiBlbCBkZXN0aW5h
dGFyaW8gaW5kaWNhZG8sIHF1ZWRhIG5vdGlmaWNhZG8gZGUgcXVlIGxhDQogbGVjdHVyYSwgdXRp
bGl6YWNpw7NuLCBkaXZ1bGdhY2nDs24geS9vIGNvcGlhIHNpbiBhdXRvcml6YWNpw7NuIHB1ZWRl
IGVzdGFyIHByb2hpYmlkYSBlbiB2aXJ0dWQgZGUgbGEgbGVnaXNsYWNpw7NuIHZpZ2VudGUuIFNp
IGhhIHJlY2liaWRvIGVzdGUgbWVuc2FqZSBwb3IgZXJyb3IsIGxlIHJvZ2Ftb3MgcXVlIG5vcyBs
byBjb211bmlxdWUgaW5tZWRpYXRhbWVudGUgcG9yIGVzdGEgbWlzbWEgdsOtYSB5IHByb2NlZGEg
YSBzdSBkZXN0cnVjY2nDs24uPGJyPg0KPGJyPg0KVGhlIGluZm9ybWF0aW9uIGNvbnRhaW5lZCBp
biB0aGlzIHRyYW5zbWlzc2lvbiBpcyBwcml2aWxlZ2VkIGFuZCBjb25maWRlbnRpYWwgaW5mb3Jt
YXRpb24gaW50ZW5kZWQgb25seSBmb3IgdGhlIHVzZSBvZiB0aGUgaW5kaXZpZHVhbCBvciBlbnRp
dHkgbmFtZWQgYWJvdmUuIElmIHRoZSByZWFkZXIgb2YgdGhpcyBtZXNzYWdlIGlzIG5vdCB0aGUg
aW50ZW5kZWQgcmVjaXBpZW50LCB5b3UgYXJlIGhlcmVieSBub3RpZmllZCB0aGF0IGFueSBkaXNz
ZW1pbmF0aW9uLA0KIGRpc3RyaWJ1dGlvbiBvciBjb3B5aW5nIG9mIHRoaXMgY29tbXVuaWNhdGlv
biBpcyBzdHJpY3RseSBwcm9oaWJpdGVkLiBJZiB5b3UgaGF2ZSByZWNlaXZlZCB0aGlzIHRyYW5z
bWlzc2lvbiBpbiBlcnJvciwgZG8gbm90IHJlYWQgaXQuIFBsZWFzZSBpbW1lZGlhdGVseSByZXBs
eSB0byB0aGUgc2VuZGVyIHRoYXQgeW91IGhhdmUgcmVjZWl2ZWQgdGhpcyBjb21tdW5pY2F0aW9u
IGluIGVycm9yIGFuZCB0aGVuIGRlbGV0ZSBpdC48YnI+DQo8YnI+DQpFc3RhIG1lbnNhZ2VtIGUg
c2V1cyBhbmV4b3Mgc2UgZGlyaWdlbSBleGNsdXNpdmFtZW50ZSBhbyBzZXUgZGVzdGluYXTDoXJp
bywgcG9kZSBjb250ZXIgaW5mb3JtYcOnw6NvIHByaXZpbGVnaWFkYSBvdSBjb25maWRlbmNpYWwg
ZSDDqSBwYXJhIHVzbyBleGNsdXNpdm8gZGEgcGVzc29hIG91IGVudGlkYWRlIGRlIGRlc3Rpbm8u
IFNlIG7Do28gw6kgdm9zc2Egc2VuaG9yaWEgbyBkZXN0aW5hdMOhcmlvIGluZGljYWRvLCBmaWNh
IG5vdGlmaWNhZG8gZGUgcXVlIGENCiBsZWl0dXJhLCB1dGlsaXphw6fDo28sIGRpdnVsZ2HDp8Oj
byBlL291IGPDs3BpYSBzZW0gYXV0b3JpemHDp8OjbyBwb2RlIGVzdGFyIHByb2liaWRhIGVtIHZp
cnR1ZGUgZGEgbGVnaXNsYcOnw6NvIHZpZ2VudGUuIFNlIHJlY2ViZXUgZXN0YSBtZW5zYWdlbSBw
b3IgZXJybywgcm9nYW1vcy1saGUgcXVlIG5vcyBvIGNvbXVuaXF1ZSBpbWVkaWF0YW1lbnRlIHBv
ciBlc3RhIG1lc21hIHZpYSBlIHByb2NlZGEgYSBzdWEgZGVzdHJ1acOnw6NvPC9zcGFuPjxvOnA+
PC9vOnA+PC9wPg0KPC9kaXY+DQo8L2JvZHk+DQo8L2h0bWw+DQo=

--_000_SN6PR13MB23343DE9392FA9EDDDA65651850B0SN6PR13MB2334namp_--


From nobody Fri Oct  9 00:08:55 2020
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 949743A0CBA for <i2nsf@ietfa.amsl.com>; Fri,  9 Oct 2020 00:08:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.987
X-Spam-Level: 
X-Spam-Status: No, score=-1.987 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, T_HK_NAME_FM_MR_MRS=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=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 lpV611TN7dGt for <i2nsf@ietfa.amsl.com>; Fri,  9 Oct 2020 00:08:50 -0700 (PDT)
Received: from mail-lj1-x236.google.com (mail-lj1-x236.google.com [IPv6:2a00:1450:4864:20::236]) (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 E74553A0CBE for <i2nsf@ietf.org>; Fri,  9 Oct 2020 00:08:49 -0700 (PDT)
Received: by mail-lj1-x236.google.com with SMTP id y16so7414114ljk.1 for <i2nsf@ietf.org>; Fri, 09 Oct 2020 00:08:49 -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=G61LSfYgEVQuxHTKL2xUyzqRFMnA5RHwvOdGenjYG0c=; b=n7yx8T+zMyqhx4IBdbQjX6S3y9frbVsaRGRhrh9dfSkod39C75DnOSZUFhZPjbYG7i 72HnlKy6XZ1TA5ap9vofKgFm1NRjhoh6jt44gSEj8bl+MZpgd5Bg2DssqQx/78VhmIYK n505cBzTglJ384JUeGL1x04xH14/+z9JOY4mtQZQAXe3H8DG1ocAuf1KyXOA2ct342Ww QEbjNPHB+LeD0ieokE/BuKReFRWwbQQxin7xuUIHWgtdtv0cMvP5d8550qgZbJZGss+M YHffNt6kqU/uEqaGvQkfV2Ww4rcR9njojMpxPyDfdlCj1ta1Dv8BJTb7J5bBCbf2cOwc W2Mg==
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=G61LSfYgEVQuxHTKL2xUyzqRFMnA5RHwvOdGenjYG0c=; b=Nz7KNRQnQtlCVzY7aIMSxS9SDo4hYW8argBEDZGj0wfYsKVTLbPCiiAFPayVkosRSe y7pAiwCMOPAzhVoQ8ypEk8GVZP1okGN3PGutgQ9/els9j02EJmEvu1rzhVKU353awCTO sSyPRIbJjtXXNv09aIoa2qCresWeScBry1z1dwIh2wjXhitq+JQvIxfr3WjoYX8sr4p5 VZqoQAjsBfyq9BFNQGJ/eMRdU3BDWydccZlyiIydRSwCNYUM45m4j4f7JpCz/OQU7fm4 Ku6MXXnqlPPyRWrB1uBqnDPXtWxd9JboB8LcaF+j9ogT0ooGy6LPDvk7xDsFpZ+qMivq Fs0Q==
X-Gm-Message-State: AOAM533TweIRWwkT2YFfi2GDdOncBz0QZq/IzdnJnQO4uVvLXeKh6uGr mWabBLzBhcM6DvTwqNO1KyiS4v5oNneRXmSHDJ8=
X-Google-Smtp-Source: ABdhPJwerxscP+CajeFiMpN15MsQjFvMRGBNiJrn4c0qwBAuMowoGISMBzk09XCqmNjFi6OvZW7Lh7AsXM8mIkiejSU=
X-Received: by 2002:a2e:86d2:: with SMTP id n18mr4283095ljj.400.1602227327785;  Fri, 09 Oct 2020 00:08:47 -0700 (PDT)
MIME-Version: 1.0
References: <CAPK2DewqhYHS2d0bJ_zvTOX+NR+bONNvr_Q_Tc6yj8UzKp+mMg@mail.gmail.com> <SN6PR13MB233437E84CA06E5096DF15C585210@SN6PR13MB2334.namprd13.prod.outlook.com> <CAPK2Dez4VRhS1ssu0wf1vcno=o_FZ+9cVqHDxDMXn1mDLibTaQ@mail.gmail.com> <45654AE3-E1B4-4D04-B295-BBF6A133F587@telefonica.com>
In-Reply-To: <45654AE3-E1B4-4D04-B295-BBF6A133F587@telefonica.com>
From: "Mr. Jaehoon Paul Jeong" <jaehoon.paul@gmail.com>
Date: Fri, 9 Oct 2020 16:08:12 +0900
Message-ID: <CAPK2Dexw9vZE98ZzAaEdXwrMxJcijMyTikuJ4y7nYJLf6v-bow@mail.gmail.com>
To: "Diego R. Lopez" <diego.r.lopez@telefonica.com>
Cc: Linda Dunbar <linda.dunbar@futurewei.com>,  "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>, "i2nsf@ietf.org" <i2nsf@ietf.org>,  skku-iotlab-members <skku-iotlab-members@googlegroups.com>
Content-Type: multipart/alternative; boundary="000000000000b8df5305b1379ea4"
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2nsf/I_g6fHLftQ-ednhnI1IdRtbtQOA>
Subject: Re: [I2nsf] Offer for Revision Help for I2NSF NSFs Capabilities Information 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: Fri, 09 Oct 2020 07:08:55 -0000

--000000000000b8df5305b1379ea4
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hi Diego,
I agree with you that the extension of the I2NSF NSF Capabilities
Information Model will be used for
other areas in the I2NSF such as Remote Attestation and closed-loop
security management.
I have much interest in this Remote Attestation in the I2NSF, too.
I would like to propose an extension of I2NSF for closed-loop security
management through
the NSF monitoring and the analysis of the monitoring data for an augmented
security policy
or a new security policy.
I would like to propose this closed-loop security management for the
rechartering along with
the remote attestation.
For this closed-loop security management, we need to extend the I2NSF
framework and
need additional interfaces for the feedback interface from the I2NSF
monitoring data analyzer to
the I2NSF security controller.

Thanks.

Best Regards,
Paul

On Tue, Sep 22, 2020 at 11:50 PM Diego R. Lopez <
diego.r.lopez@telefonica.com> wrote:

> =EF=BB=BFHi 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=E2=80=99s co=
mments
> without totally rewriting most, if not all, of the document.  Second, the
> fact that the capability data model was evolving in a quite reasonable an=
d
> pragmatic way, including running code at the hackathons, following the
> spirit of the initial work in the information model, but not attempting t=
o
> 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 address=
ed
> 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 see=
ms
> 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 opportuni=
ty
> 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=E2=80=99d like to get Linda=E2=
=80=99s, Yoav=E2=80=99s
> and Roman=E2=80=99s ideas, as well as the availability to work on this fr=
om Frank,
> John and Aldo.
>
>
>
> --
>
> "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
>
> 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=EB=85=84 9=EC=9B=94 17=EC=9D=BC (=EB=AA=A9) =EC=98=A4=EC=A0=84 3:44,=
 Linda Dunbar <linda.dunbar@futurewei.com>=EB=8B=98=EC=9D=B4 =EC=9E=91=EC=
=84=B1:
>
> 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 t=
he
> draft forward. Therefore, I2NSF chairs have authorized you to be one of t=
he
> 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_tex=
t=3D1
> <https://nam11.safelinks.protection.outlook.com/?url=3Dhttps%3A%2F%2Fdata=
tracker.ietf.org%2Fdoc%2Fdraft-ietf-i2nsf-capability%2F%3Finclude_text%3D1&=
data=3D02%7C01%7Clinda.dunbar%40futurewei.com%7C34e743abe97044391c7408d857f=
6ed45%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C1%7C637356065339807897&sdata=
=3DiqwH7Qp8SGTB84gRz4jk1AwyoA3gEn0hBpxmxgnSxFU%3D&reserved=3D0>
>
>
>
> 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 I2NS=
F
> deliverables.
>
>
>
> Thanks.
>
>
>
> Best Regards,
>
> Paul
>
>
> ------------------------------
>
> Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario,
> puede contener informaci=C3=B3n 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=C3=
=B3n,
> divulgaci=C3=B3n y/o copia sin autorizaci=C3=B3n puede estar prohibida en=
 virtud de
> la legislaci=C3=B3n vigente. Si ha recibido este mensaje por error, le ro=
gamos
> que nos lo comunique inmediatamente por esta misma v=C3=ADa y proceda a s=
u
> destrucci=C3=B3n.
>
> 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 o=
r
> copying of this communication is strictly prohibited. If you have receive=
d
> this transmission in error, do not read it. Please immediately reply to t=
he
> sender that you have received this communication in error and then delete
> it.
>
> Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinat=C3=
=A1rio,
> pode conter informa=C3=A7=C3=A3o privilegiada ou confidencial e =C3=A9 pa=
ra uso exclusivo
> da pessoa ou entidade de destino. Se n=C3=A3o =C3=A9 vossa senhoria o des=
tinat=C3=A1rio
> indicado, fica notificado de que a leitura, utiliza=C3=A7=C3=A3o, divulga=
=C3=A7=C3=A3o e/ou
> c=C3=B3pia sem autoriza=C3=A7=C3=A3o pode estar proibida em virtude da le=
gisla=C3=A7=C3=A3o vigente.
> Se recebeu esta mensagem por erro, rogamos-lhe que nos o comunique
> imediatamente por esta mesma via e proceda a sua destrui=C3=A7=C3=A3o
>


--=20
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D
Mr. Jaehoon (Paul) Jeong, Ph.D.
Associate Professor
Department of Computer Science and Engineering
Sungkyunkwan University
Office: +82-31-299-4957
Email: jaehoon.paul@gmail.com, pauljeong@skku.edu
Personal Homepage: http://iotlab.skku.edu/people-jaehoon-jeong.php
<http://cpslab.skku.edu/people-jaehoon-jeong.php>

--000000000000b8df5305b1379ea4
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Hi Diego,</div><div>I agree=C2=A0with you that the ex=
tension of the I2NSF NSF Capabilities Information Model will be used for</d=
iv><div>other=C2=A0areas in the I2NSF such as Remote Attestation and closed=
-loop security management.=C2=A0</div><div>I have=C2=A0much interest in thi=
s Remote Attestation in the I2NSF, too.</div><div>I would like to propose a=
n extension=C2=A0of I2NSF for closed-loop security management through=C2=A0=
</div><div>the NSF monitoring and the analysis of the monitoring data for a=
n augmented security policy=C2=A0</div><div>or a new security policy.</div>=
<div>I would like to propose this closed-loop security management for the r=
echartering along with</div><div>the remote attestation.</div><div>For this=
 closed-loop security management, we need to extend the I2NSF framework and=
</div><div>need additional interfaces for the feedback interface from the I=
2NSF monitoring data analyzer to</div><div>the I2NSF security controller.</=
div><div><br></div><div>Thanks.</div><div><br></div><div>Best=C2=A0Regards,=
</div><div>Paul</div><div></div></div><br><div class=3D"gmail_quote"><div d=
ir=3D"ltr" class=3D"gmail_attr">On Tue, Sep 22, 2020 at 11:50 PM Diego R. L=
opez &lt;<a href=3D"mailto:diego.r.lopez@telefonica.com">diego.r.lopez@tele=
fonica.com</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=
=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding=
-left:1ex">





<div lang=3D"en-ES" style=3D"overflow-wrap: break-word;">
<div class=3D"gmail-m_5369920383902584301WordSection1">
<p class=3D"MsoNormal"><span class=3D"gmail-m_5369920383902584301EmailStyle=
20"><span style=3D"font-size:10pt">=EF=BB=BFH</span></span><span class=3D"g=
mail-m_5369920383902584301EmailStyle20"><span lang=3D"ES" style=3D"font-siz=
e:10pt">i Paul,<u></u><u></u></span></span></p>
<p class=3D"MsoNormal"><span class=3D"gmail-m_5369920383902584301EmailStyle=
20"><span lang=3D"ES" style=3D"font-size:10pt"><u></u>=C2=A0<u></u></span><=
/span></p>
<p class=3D"MsoNormal"><span class=3D"gmail-m_5369920383902584301EmailStyle=
20"><span lang=3D"EN-US" style=3D"font-size:10pt">Before you go for it, let=
 me share with you some reflections on the state of the draft, in the spiri=
t of what I replied to Eric Vyncke.<u></u><u></u></span></span></p>
<p class=3D"MsoNormal"><span class=3D"gmail-m_5369920383902584301EmailStyle=
20"><span lang=3D"EN-US" style=3D"font-size:10pt"><u></u>=C2=A0<u></u></spa=
n></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10pt">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=E2=80=99s comments without totall=
y rewriting most, if not all, of the document.=C2=A0 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 t=
his position before is because I have been looking for a way to make the id=
ea of bridging capability declarations
 and security policy statements at the I2NSF controller viable, and I was h=
oping to find such a way by reusing part of the capability info model draft=
.<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10pt"><u></u=
><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10pt">As I t=
old Eric, I believe the current capability model has a powerful (though pro=
bably not yet complete) calculus for policy description and validation, but=
 not directly
 related to the management mechanisms addressed in the capability data mode=
l and the other data models produced in I2NSF. I believe there is an opport=
unity 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 t=
herefore imply an extension of the I2NSF lifetime. I would like to know you=
r position(*) about such an extension, =C2=A0that could also become an oppo=
rtunity to work in other matters related
 to attestation (in the light of the work in RATS and the MUD initiative wi=
thin the Ops Area) and accounting.<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10pt"><u></u=
>=C2=A0<u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10pt">Be goo=
de,<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10pt"><u></u=
>=C2=A0<u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10pt">(*) I =
assume you are in favor, Paul. But I=E2=80=99d like to get Linda=E2=80=99s,=
 Yoav=E2=80=99s and Roman=E2=80=99s ideas, as well as the availability to w=
ork on this from Frank, John and Aldo.<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10pt"><u></u=
>=C2=A0<u></u></span></p>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10pt">--<u><=
/u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"ES" style=3D"font-size:10pt">&quot;Est=
a vez no fallaremos, Doctor Infierno&quot;<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"ES" style=3D"font-size:10pt">=C2=A0<u>=
</u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"ES" style=3D"font-size:10pt">Dr Diego =
R. Lopez<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"ES" style=3D"font-size:10pt">Telefonic=
a I+D<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"ES" style=3D"font-size:10pt"><a href=
=3D"https://www.linkedin.com/in/dr2lopez/" target=3D"_blank"><span style=3D=
"color:rgb(5,99,193)">https://www.linkedin.com/in/dr2lopez/</span></a>=C2=
=A0<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"ES" style=3D"font-size:10pt">=C2=A0<u>=
</u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"ES" style=3D"font-size:10pt">e-mail:=
=C2=A0</span><span lang=3D"EN-GB" style=3D"font-size:10pt"><a href=3D"mailt=
o:diego.r.lopez@telefonica.com" target=3D"_blank"><span lang=3D"ES" style=
=3D"color:rgb(5,99,193)">diego.r.lopez@telefonica.com</span></a></span><spa=
n lang=3D"ES" style=3D"font-size:10pt"><u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB" style=3D"font-size:10pt">Tel:=
=C2=A0=C2=A0=C2=A0 =C2=A0=C2=A0=C2=A0=C2=A0 +34 913 129 041<u></u><u></u></=
span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB" style=3D"font-size:10pt">Mobile=
: =C2=A0+34 682 051 091<u></u><u></u></span></p>
</div>
<p class=3D"MsoNormal"><span lang=3D"EN-GB" style=3D"font-size:10pt">------=
----------------------------</span><span style=3D"font-size:10pt"><u></u><u=
></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10pt"><u></u>=C2=A0<u></u><=
/span></p>
<div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:36pt">On 17/09/2020, 01:42, &qu=
ot;Mr. Jaehoon Paul Jeong&quot; &lt;<a href=3D"mailto:jaehoon.paul@gmail.co=
m" target=3D"_blank">jaehoon.paul@gmail.com</a>&gt; wrote:<u></u><u></u></p=
>
</div>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:36pt"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:36pt">Hi Linda,<u></u><u></u></=
p>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:36pt">I will address our AD Rom=
an&#39;s comments on this NSFs capabilities information draft as the 2nd ed=
itor through the collaboration with Frank (the 1st editor) and the other au=
thors.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:36pt"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:36pt">I CC our AD Roman and the=
 other authors, such as John and Cataldo.<u></u><u></u></p>
</div>
<div>
<pre style=3D"margin-left:36pt"><span style=3D"font-size:9.5pt"><u></u>=C2=
=A0<u></u></span></pre>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:36pt">Thanks for your support a=
nd guidance.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:36pt"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:36pt">Best Regards,<u></u><u></=
u></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:36pt">Paul<u></u><u></u></p>
</div>
</div>
<p class=3D"MsoNormal" style=3D"margin-left:36pt"><u></u>=C2=A0<u></u></p>
<div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:36pt">2020<span lang=3D"EN-GB" =
style=3D"font-family:&quot;Malgun Gothic&quot;,sans-serif">=EB=85=84</span>=
 9<span lang=3D"EN-GB" style=3D"font-family:&quot;Malgun Gothic&quot;,sans-=
serif">=EC=9B=94</span> 17<span lang=3D"EN-GB" style=3D"font-family:&quot;M=
algun Gothic&quot;,sans-serif">=EC=9D=BC</span>
 (<span lang=3D"EN-GB" style=3D"font-family:&quot;Malgun Gothic&quot;,sans-=
serif">=EB=AA=A9</span>) <span lang=3D"EN-GB" style=3D"font-family:&quot;Ma=
lgun Gothic&quot;,sans-serif">
=EC=98=A4=EC=A0=84</span> 3:44, Linda Dunbar &lt;<a href=3D"mailto:linda.du=
nbar@futurewei.com" target=3D"_blank">linda.dunbar@futurewei.com</a>&gt;<sp=
an lang=3D"EN-GB" style=3D"font-family:&quot;Malgun Gothic&quot;,sans-serif=
">=EB=8B=98=EC=9D=B4</span><span lang=3D"EN-GB">
</span><span lang=3D"EN-GB" style=3D"font-family:&quot;Malgun Gothic&quot;,=
sans-serif">=EC=9E=91=EC=84=B1</span>:<u></u><u></u></p>
</div>
<blockquote style=3D"border-top:none;border-right:none;border-bottom:none;b=
order-left:1pt solid rgb(204,204,204);padding:0cm 0cm 0cm 6pt;margin-left:4=
.8pt;margin-right:0cm">
<div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:36pt">
<span lang=3D"EN-US">Paul, <u></u><u></u></span></p>
<p class=3D"MsoNormal" style=3D"margin-left:36pt">
<span lang=3D"EN-US">=C2=A0<u></u><u></u></span></p>
<p class=3D"MsoNormal" style=3D"margin-left:36pt">
<span lang=3D"EN-US">Thank you very much for offering to address the AD com=
ments 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.=
=C2=A0 We need to move the draft forward.
 Therefore, I2NSF chairs have authorized you to be one of the editors to ad=
dress the AD comments and revise the draft.
<u></u><u></u></span></p>
<p class=3D"MsoNormal" style=3D"margin-left:36pt">
<span lang=3D"EN-US">=C2=A0<u></u><u></u></span></p>
<p class=3D"MsoNormal" style=3D"margin-left:36pt">
<span lang=3D"EN-US">=C2=A0<u></u><u></u></span></p>
<p class=3D"MsoNormal" style=3D"margin-left:36pt">
<span lang=3D"EN-US">Thank you very much. <u></u><u></u></span></p>
<p class=3D"MsoNormal" style=3D"margin-left:36pt">
<span lang=3D"EN-US">=C2=A0<u></u><u></u></span></p>
<p class=3D"MsoNormal" style=3D"margin-left:36pt">
<span lang=3D"EN-US">Linda &amp; Yoav<u></u><u></u></span></p>
<p class=3D"MsoNormal" style=3D"margin-left:36pt">
<span lang=3D"EN-US">=C2=A0<u></u><u></u></span></p>
<p class=3D"MsoNormal" style=3D"margin-left:36pt">
<span lang=3D"EN-US">=C2=A0<u></u><u></u></span></p>
<p class=3D"MsoNormal" style=3D"margin-left:36pt">
<b><span lang=3D"EN-US">From:</span></b><span lang=3D"EN-US"> Mr. Jaehoon P=
aul Jeong &lt;<a href=3D"mailto:jaehoon.paul@gmail.com" target=3D"_blank">j=
aehoon.paul@gmail.com</a>&gt;
<br>
<b>Sent:</b> Sunday, September 13, 2020 10:09 AM<br>
<b>To:</b> Xialiang (Frank) &lt;<a href=3D"mailto:frank.xialiang@huawei.com=
" target=3D"_blank">frank.xialiang@huawei.com</a>&gt;<br>
<b>Cc:</b> Linda Dunbar &lt;<a href=3D"mailto:linda.dunbar@futurewei.com" t=
arget=3D"_blank">linda.dunbar@futurewei.com</a>&gt;; Yoav Nir &lt;<a href=
=3D"mailto:ynir.ietf@gmail.com" target=3D"_blank">ynir.ietf@gmail.com</a>&g=
t;; DIEGO LOPEZ GARCIA &lt;<a href=3D"mailto:diego.r.lopez@telefonica.com" =
target=3D"_blank">diego.r.lopez@telefonica.com</a>&gt;;
 Jaehoon Jeong &lt;<a href=3D"mailto:jaehoon.paul@gmail.com" target=3D"_bla=
nk">jaehoon.paul@gmail.com</a>&gt;<br>
<b>Subject:</b> Offer for Revision Help for I2NSF NSFs Capabilities Informa=
tion Model Draft<u></u><u></u></span></p>
<p class=3D"MsoNormal" style=3D"margin-left:36pt">
<span lang=3D"EN-US">=C2=A0<u></u><u></u></span></p>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:36pt">
<span lang=3D"EN-US">Hi Frank,<u></u><u></u></span></p>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:36pt">
<span lang=3D"EN-US">Could I help you to revise your information model draf=
t for our AD Roman Danyliw&#39;s review comments=C2=A0 as a co-editor?<u></=
u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:36pt">
<span lang=3D"EN-US"><a href=3D"https://nam11.safelinks.protection.outlook.=
com/?url=3Dhttps%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fdraft-ietf-i2nsf-capa=
bility%2F%3Finclude_text%3D1&amp;data=3D02%7C01%7Clinda.dunbar%40futurewei.=
com%7C34e743abe97044391c7408d857f6ed45%7C0fee8ff2a3b240189c753a1d5591fedc%7=
C1%7C1%7C637356065339807897&amp;sdata=3DiqwH7Qp8SGTB84gRz4jk1AwyoA3gEn0hBpx=
mxgnSxFU%3D&amp;reserved=3D0" target=3D"_blank">https://datatracker.ietf.or=
g/doc/draft-ietf-i2nsf-capability/?include_text=3D1</a><u></u><u></u></span=
></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:36pt">
<span lang=3D"EN-US">=C2=A0<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:36pt">
<span lang=3D"EN-US">As you know, I have finished our I2NSF data model draf=
ts.<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:36pt">
<span lang=3D"EN-US">=C2=A0<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:36pt">
<span lang=3D"EN-US">I am happy to work on the revision with you in order t=
o complete our I2NSF deliverables.<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:36pt">
<span lang=3D"EN-US">=C2=A0<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:36pt">
<span lang=3D"EN-US">Thanks.<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:36pt">
<span lang=3D"EN-US">=C2=A0<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:36pt">
<span lang=3D"EN-US">Best Regards,<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:36pt">
<span lang=3D"EN-US">Paul<u></u><u></u></span></p>
</div>
</div>
</div>
</div>
</blockquote>
</div>
</div>
<br>
<hr>
<font face=3D"Arial" color=3D"Gray" size=3D"1"><br>
Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, pu=
ede contener informaci=C3=B3n privilegiada o confidencial y es para uso exc=
lusivo de la persona o entidad de destino. Si no es usted. el destinatario =
indicado, queda notificado de que la
 lectura, utilizaci=C3=B3n, divulgaci=C3=B3n y/o copia sin autorizaci=C3=B3=
n puede estar prohibida en virtud de la legislaci=C3=B3n vigente. Si ha rec=
ibido este mensaje por error, le rogamos que nos lo comunique inmediatament=
e por esta misma v=C3=ADa y proceda a su destrucci=C3=B3n.<br>
<br>
The information contained in this transmission is privileged and confidenti=
al 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 y=
ou have received this transmission in error, do not read it. Please immedia=
tely reply to the sender that you have received this communication in error=
 and then delete it.<br>
<br>
Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinat=C3=A1=
rio, pode conter informa=C3=A7=C3=A3o privilegiada ou confidencial e =C3=A9=
 para uso exclusivo da pessoa ou entidade de destino. Se n=C3=A3o =C3=A9 vo=
ssa senhoria o destinat=C3=A1rio indicado, fica notificado de que a
 leitura, utiliza=C3=A7=C3=A3o, divulga=C3=A7=C3=A3o e/ou c=C3=B3pia sem au=
toriza=C3=A7=C3=A3o pode estar proibida em virtude da legisla=C3=A7=C3=A3o =
vigente. Se recebeu esta mensagem por erro, rogamos-lhe que nos o comunique=
 imediatamente por esta mesma via e proceda a sua destrui=C3=A7=C3=A3o<br>
</font>
</div>

</blockquote></div><br clear=3D"all"><div><br></div>-- <br><div dir=3D"ltr"=
 class=3D"gmail_signature"><div dir=3D"ltr"><div><div dir=3D"ltr"><div><div=
 dir=3D"ltr"><div><div dir=3D"ltr">=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br>Mr. Jaehoon (Paul) Jeong, Ph.=
D.<br>Associate Professor<br>Department of Computer Science and Engineering=
<br>Sungkyunkwan University<br>Office: +82-31-299-4957<br>Email: <a href=3D=
"mailto:jaehoon.paul@gmail.com" target=3D"_blank">jaehoon.paul@gmail.com</a=
>,=C2=A0<a href=3D"mailto:pauljeong@skku.edu" style=3D"font-size:12.8px" ta=
rget=3D"_blank">pauljeong@skku.edu</a><br>Personal Homepage: <a href=3D"htt=
p://cpslab.skku.edu/people-jaehoon-jeong.php" target=3D"_blank">http://iotl=
ab.skku.edu/people-jaehoon-jeong.php</a><br></div></div></div></div></div><=
/div></div></div>

--000000000000b8df5305b1379ea4--


From nobody Fri Oct  9 00:09:20 2020
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 6B0833A0CBA for <i2nsf@ietfa.amsl.com>; Fri,  9 Oct 2020 00:09:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.344
X-Spam-Level: 
X-Spam-Status: No, score=0.344 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=2.331, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_HK_NAME_FM_MR_MRS=0.01, 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 pgzm7p-PuizL for <i2nsf@ietfa.amsl.com>; Fri,  9 Oct 2020 00:09:16 -0700 (PDT)
Received: from mail-lf1-x136.google.com (mail-lf1-x136.google.com [IPv6:2a00:1450:4864:20::136]) (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 818463A0C43 for <i2nsf@ietf.org>; Fri,  9 Oct 2020 00:09:15 -0700 (PDT)
Received: by mail-lf1-x136.google.com with SMTP id b22so9555715lfs.13 for <i2nsf@ietf.org>; Fri, 09 Oct 2020 00:09:15 -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=yoAFUzYHGNaraGXI0M+eRTNfb2wgABFHEcI7vA0AV3U=; b=SX1d2MU86OLi0nCC8lnjA1g7Wp5wXGIAJ/czv+R7NF+0bkCgtX6CdKD74UWJF9Cwt0 iNKn6QoQVvvTZWhwy3JSLsapWpElkeKPQU+xi/VoE6qYFVZBda6WGUBANA+liHN3Rsej Wmc+DVsGNB0RYZtGt8QWSEWm2v4rtLYm70doF0itreUL2fY6OLK2LUUiV2NANZ+L37NI 0FhIeoQ/j2dpDqWdfv8uf5DagwmOoJU0K+DTpYUi5jHEHVkyUqdBU7IUPVprkwUODGi5 8GvALjLtO65nJKNwMkxfpg8AszQP0gVkWkVJ4bMB1ODcRHV4/mqXfQB7iLrzmNiPJo5T e69Q==
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=yoAFUzYHGNaraGXI0M+eRTNfb2wgABFHEcI7vA0AV3U=; b=XbFP32r0Ry9QZjw4yxmQin5Gj3PyHh6ghYkGhgNlS1y/xDH95It7Nlu1Y1C20Jbbdq hPaDcknJxdW3/lUP4G7Wcv8R1F2NPUBrO4F08ZFM91MwSX5eq6dGBl2fwXiec9Ai4kDV CqhY+T29wRrtDP/ud5L89/6IK/yQvBH5GelH71sU/v0x+u6yfTRFph3lrpRs2vhqMZso xm2JryZ1hPU9nzl+oXYzGWzCn6Rrw0WX3Y8cCKSgTGdfSR4B7n0ZnUSK4GmLuWwVoFjV HqOtD0Pl1jcOgrbvJo42PeHogUHtNKVO0B3p78g1NIDSJYx6gsT02rBQu8/WXMBocSOG jWiw==
X-Gm-Message-State: AOAM531EJlD3EGAQTNVE/95xvBW89Q0H3CZTeR335fMh9Nv20CjxcYrr DpeMDCSWf1bFQSceSvfUyUEC/kv6X4rRC0y9+ug=
X-Google-Smtp-Source: ABdhPJx/lj2lozEkTHXLX337LMPmTtWQnd+yVHYnPt8KeSGn7TsH3gujLsGNMUreOMnDMYUaoxNcdn7t2HLaJiMMLLw=
X-Received: by 2002:ac2:4643:: with SMTP id s3mr3588829lfo.397.1602227353462;  Fri, 09 Oct 2020 00:09:13 -0700 (PDT)
MIME-Version: 1.0
References: <SN6PR13MB23343DE9392FA9EDDDA65651850B0@SN6PR13MB2334.namprd13.prod.outlook.com>
In-Reply-To: <SN6PR13MB23343DE9392FA9EDDDA65651850B0@SN6PR13MB2334.namprd13.prod.outlook.com>
From: "Mr. Jaehoon Paul Jeong" <jaehoon.paul@gmail.com>
Date: Fri, 9 Oct 2020 16:08:38 +0900
Message-ID: <CAPK2DeyAfrxkorQV-GUbBz2MUzfq5VrxaifmhJ-xL_tnTs0JRg@mail.gmail.com>
To: Linda Dunbar <linda.dunbar@futurewei.com>
Cc: "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="00000000000040aca705b137a05f"
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2nsf/X4VEMZXShEPAYxjKb1yEnag8Eaw>
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: Fri, 09 Oct 2020 07:09:18 -0000

--00000000000040aca705b137a05f
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hi Linda,
Okay, I will remove the reference to the Capability Information Model draft=
.
Patrick and I are reflecting the comments of the IESG (e.g., Benjamin
Kaduk, Barry Leiba, =C3=89ric Vyncke,
Erik Kline, Magnus Westerlund, Murray Kucherawy, and Alvaro Retana).

I will be able to post the revised version by October 21, 2020.

Thanks.

Best Regards,
Paul


On Fri, Oct 9, 2020 at 6:35 AM Linda Dunbar <linda.dunbar@futurewei.com>
wrote:

> I2nsf WG,
>
>
>
> There has been any objection to the Author=E2=80=99s request for sunsetti=
ng 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 evolvi=
ng
> 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=E2=80=99t hear any objecti=
on 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=E2=80=99d prefer the second option, as it seems more straightforward an=
d 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=3Dhttps%3A%2F%2Fwww.=
linkedin.com%2Fin%2Fdr2lopez%2F&data=3D02%7C01%7Clinda.dunbar%40futurewei.c=
om%7C08a48858d7bd4d843a6e08d85f47b438%7C0fee8ff2a3b240189c753a1d5591fedc%7C=
1%7C0%7C637364108864949633&sdata=3DROR4%2FyD1WqWDb1rCbJx3ERqTiMCQ92ibkyz26k=
YZdD8%3D&reserved=3D0>
>
>
>
>
> 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 =E2=80=9Cthe capability data =
model was
> evolving in a quite reasonable and pragmatic way, including running code =
at
> the hackathons=E2=80=9D.
>
>
>
> Looks like Eric Vyncke still wants the information model to be fixed to
> clear his =E2=80=9CDISCUSS=E2=80=9D ballot.
>
> How about the following steps:
>
> -          Ask Roman=E2=80=99s 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=E2=80=99s co=
mments
> without totally rewriting most, if not all, of the document.  Second, the
> fact that the capability data model was evolving in a quite reasonable an=
d
> pragmatic way, including running code at the hackathons, following the
> spirit of the initial work in the information model, but not attempting t=
o
> 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 address=
ed
> 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 see=
ms
> 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 opportuni=
ty
> 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=E2=80=99d like to get Linda=E2=
=80=99s, Yoav=E2=80=99s
> and Roman=E2=80=99s ideas, as well as the availability to work on this fr=
om 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=3Dhttps%3A%2F%2Fwww.=
linkedin.com%2Fin%2Fdr2lopez%2F&data=3D02%7C01%7Clinda.dunbar%40futurewei.c=
om%7C08a48858d7bd4d843a6e08d85f47b438%7C0fee8ff2a3b240189c753a1d5591fedc%7C=
1%7C0%7C637364108864949633&sdata=3DROR4%2FyD1WqWDb1rCbJx3ERqTiMCQ92ibkyz26k=
YZdD8%3D&reserved=3D0>
>
>
>
>
> 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=EB=85=84 9=EC=9B=94 17=EC=9D=BC (=EB=AA=A9) =EC=98=A4=EC=A0=84 3:44,=
 Linda Dunbar <linda.dunbar@futurewei.com>=EB=8B=98=EC=9D=B4 =EC=9E=91=EC=
=84=B1:
>
> 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 t=
he
> draft forward. Therefore, I2NSF chairs have authorized you to be one of t=
he
> 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_tex=
t=3D1
> <https://nam11.safelinks.protection.outlook.com/?url=3Dhttps%3A%2F%2Fdata=
tracker.ietf.org%2Fdoc%2Fdraft-ietf-i2nsf-capability%2F%3Finclude_text%3D1&=
data=3D02%7C01%7Clinda.dunbar%40futurewei.com%7C08a48858d7bd4d843a6e08d85f4=
7b438%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C637364108864959626&sdata=
=3DGUrbaYu2Q4N1YNUUet2oVRPqbynA78cSBTf%2FBeSCY44%3D&reserved=3D0>
>
>
>
> 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 I2NS=
F
> deliverables.
>
>
>
> Thanks.
>
>
>
> Best Regards,
>
> Paul
>
>
> ------------------------------
>
>
> Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario,
> puede contener informaci=C3=B3n 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=C3=
=B3n,
> divulgaci=C3=B3n y/o copia sin autorizaci=C3=B3n puede estar prohibida en=
 virtud de
> la legislaci=C3=B3n vigente. Si ha recibido este mensaje por error, le ro=
gamos
> que nos lo comunique inmediatamente por esta misma v=C3=ADa y proceda a s=
u
> destrucci=C3=B3n.
>
> 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 o=
r
> copying of this communication is strictly prohibited. If you have receive=
d
> this transmission in error, do not read it. Please immediately reply to t=
he
> sender that you have received this communication in error and then delete
> it.
>
> Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinat=C3=
=A1rio,
> pode conter informa=C3=A7=C3=A3o privilegiada ou confidencial e =C3=A9 pa=
ra uso exclusivo
> da pessoa ou entidade de destino. Se n=C3=A3o =C3=A9 vossa senhoria o des=
tinat=C3=A1rio
> indicado, fica notificado de que a leitura, utiliza=C3=A7=C3=A3o, divulga=
=C3=A7=C3=A3o e/ou
> c=C3=B3pia sem autoriza=C3=A7=C3=A3o pode estar proibida em virtude da le=
gisla=C3=A7=C3=A3o vigente.
> Se recebeu esta mensagem por erro, rogamos-lhe que nos o comunique
> imediatamente por esta mesma via e proceda a sua destrui=C3=A7=C3=A3o
>
>
> ------------------------------
>
>
> Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario,
> puede contener informaci=C3=B3n 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=C3=
=B3n,
> divulgaci=C3=B3n y/o copia sin autorizaci=C3=B3n puede estar prohibida en=
 virtud de
> la legislaci=C3=B3n vigente. Si ha recibido este mensaje por error, le ro=
gamos
> que nos lo comunique inmediatamente por esta misma v=C3=ADa y proceda a s=
u
> destrucci=C3=B3n.
>
> 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 o=
r
> copying of this communication is strictly prohibited. If you have receive=
d
> this transmission in error, do not read it. Please immediately reply to t=
he
> sender that you have received this communication in error and then delete
> it.
>
> Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinat=C3=
=A1rio,
> pode conter informa=C3=A7=C3=A3o privilegiada ou confidencial e =C3=A9 pa=
ra uso exclusivo
> da pessoa ou entidade de destino. Se n=C3=A3o =C3=A9 vossa senhoria o des=
tinat=C3=A1rio
> indicado, fica notificado de que a leitura, utiliza=C3=A7=C3=A3o, divulga=
=C3=A7=C3=A3o e/ou
> c=C3=B3pia sem autoriza=C3=A7=C3=A3o pode estar proibida em virtude da le=
gisla=C3=A7=C3=A3o vigente.
> Se recebeu esta mensagem por erro, rogamos-lhe que nos o comunique
> imediatamente por esta mesma via e proceda a sua destrui=C3=A7=C3=A3o
> _______________________________________________
> I2nsf mailing list
> I2nsf@ietf.org
> https://www.ietf.org/mailman/listinfo/i2nsf
>


--=20
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D
Mr. Jaehoon (Paul) Jeong, Ph.D.
Associate Professor
Department of Computer Science and Engineering
Sungkyunkwan University
Office: +82-31-299-4957
Email: jaehoon.paul@gmail.com, pauljeong@skku.edu
Personal Homepage: http://iotlab.skku.edu/people-jaehoon-jeong.php
<http://cpslab.skku.edu/people-jaehoon-jeong.php>

--00000000000040aca705b137a05f
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr">Hi Linda,<div>Okay, I will remove the ref=
erence to the=C2=A0Capability Information Model draft.</div><div>Patrick an=
d I are reflecting the comments of the IESG (e.g., Benjamin Kaduk, Barry Le=
iba, =C3=89ric Vyncke,</div><div>Erik Kline, Magnus Westerlund, Murray Kuch=
erawy, and Alvaro Retana).</div><div><br></div><div>I will be able to post =
the revised version by October 21, 2020.</div><div><br></div><div>Thanks.<b=
r></div><div><br></div><div>Best=C2=A0Regards,</div><div>Paul</div><div><br=
></div></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail=
_attr">On Fri, Oct 9, 2020 at 6:35 AM Linda Dunbar &lt;<a href=3D"mailto:li=
nda.dunbar@futurewei.com" target=3D"_blank">linda.dunbar@futurewei.com</a>&=
gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0=
px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">





<div lang=3D"EN-US">
<div>
<p class=3D"MsoNormal">I2nsf WG, <u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">There has been any objection to the Author=E2=80=99s=
 request for sunsetting the =C2=A0draft-ietf-i2nsf-capability-05.
<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">Authors of the draft-ietf-i2nsf-capability-data-mode=
l: please remove the reference to the Capability Information Model and uplo=
ad a new draft. We can ask IESG to re-review it.
<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">Thank you very much. <u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">Linda &amp; Yoav. <u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<div>
<div style=3D"border-right:none;border-bottom:none;border-left:none;border-=
top:1pt solid rgb(225,225,225);padding:3pt 0in 0in">
<p class=3D"MsoNormal"><b>From:</b> Linda Dunbar <br>
<b>Sent:</b> Monday, September 28, 2020 11:00 AM<br>
<b>To:</b> <a href=3D"mailto:i2nsf@ietf.org" target=3D"_blank">i2nsf@ietf.o=
rg</a><br>
<b>Subject:</b> Is there any objection of sunset the I2NSF Capabilities Inf=
ormation Model Draft and merge the relevant information to the I2NSF Capabi=
lity Data model draft?
<u></u><u></u></p>
</div>
</div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">I2NSF WG, <u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">As Diego has expressed that the original I2NSF capab=
ility information model was based on a policy expression calculus suitable =
for manipulating high-level policy expressions.=C2=A0 The capability data m=
odel has been evolving in a quite reasonable
 and pragmatic way, including running code at the hackathons.<u></u><u></u>=
</p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">The I2NSF Capability Information Model has fulfilled=
 its purpose of kickstarting and guiding the data model, and the authors be=
lieve that it is better to let the capability information model to be withd=
rawn. For the content in the information
 model still relevant to I2NSF Capability Data Model, they should be merged=
 into the Capability Data Model.
<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">Is there any objection from the WG?=C2=A0 If we don=
=E2=80=99t hear any objection by Oct 5, we will change the status of the dr=
aft.
<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">Cheers, =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0
<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">Linda &amp; Yoav<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<div>
<div style=3D"border-right:none;border-bottom:none;border-left:none;border-=
top:1pt solid rgb(225,225,225);padding:3pt 0in 0in">
<p class=3D"MsoNormal"><b>From:</b> Diego R. Lopez &lt;<a href=3D"mailto:di=
ego.r.lopez@telefonica.com" target=3D"_blank">diego.r.lopez@telefonica.com<=
/a>&gt;
<br>
<b>Sent:</b> Tuesday, September 22, 2020 5:35 PM<br>
<b>To:</b> Linda Dunbar &lt;<a href=3D"mailto:linda.dunbar@futurewei.com" t=
arget=3D"_blank">linda.dunbar@futurewei.com</a>&gt;; Mr. Jaehoon Paul Jeong=
 &lt;<a href=3D"mailto:jaehoon.paul@gmail.com" target=3D"_blank">jaehoon.pa=
ul@gmail.com</a>&gt;<br>
<b>Cc:</b> Xialiang (Frank) &lt;<a href=3D"mailto:frank.xialiang@huawei.com=
" target=3D"_blank">frank.xialiang@huawei.com</a>&gt;; Yoav Nir &lt;<a href=
=3D"mailto:ynir.ietf@gmail.com" target=3D"_blank">ynir.ietf@gmail.com</a>&g=
t;; John Strassner &lt;<a href=3D"mailto:John.sc.Strassner@huawei.com" targ=
et=3D"_blank">John.sc.Strassner@huawei.com</a>&gt;;
 Aldo Basile &lt;<a href=3D"mailto:cataldo.basile@polito.it" target=3D"_bla=
nk">cataldo.basile@polito.it</a>&gt;; Roman Danyliw &lt;<a href=3D"mailto:r=
dd@cert.org" target=3D"_blank">rdd@cert.org</a>&gt;<br>
<b>Subject:</b> Re: Offer for Revision Help for I2NSF NSFs Capabilities Inf=
ormation Model Draft<u></u><u></u></p>
</div>
</div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal"><span lang=3D"ES" style=3D"font-size:10pt">Hi Linda,=
<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"ES" style=3D"font-size:10pt"><u></u>=
=C2=A0<u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10pt">I=E2=80=99d prefer th=
e 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 allowin=
g us to reuse the
 capability model for policy-control transformation, and to incorporate the=
 attestation matters you know I was so much interested in.<u></u><u></u></s=
pan></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10pt"><u></u>=C2=A0<u></u><=
/span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10pt">Be goode,<u></u><u></=
u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10pt"><u></u>=C2=A0<u></u><=
/span></p>
<div>
<p class=3D"MsoNormal"><span lang=3D"ES" style=3D"font-size:10pt">--<u></u>=
<u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"ES" style=3D"font-size:10pt">&quot;Est=
a vez no fallaremos, Doctor Infierno&quot;<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"ES" style=3D"font-size:10pt">=C2=A0<u>=
</u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"ES" style=3D"font-size:10pt">Dr Diego =
R. Lopez<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"ES" style=3D"font-size:10pt">Telefonic=
a I+D<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"ES" style=3D"font-size:10pt"><a href=
=3D"https://nam11.safelinks.protection.outlook.com/?url=3Dhttps%3A%2F%2Fwww=
.linkedin.com%2Fin%2Fdr2lopez%2F&amp;data=3D02%7C01%7Clinda.dunbar%40future=
wei.com%7C08a48858d7bd4d843a6e08d85f47b438%7C0fee8ff2a3b240189c753a1d5591fe=
dc%7C1%7C0%7C637364108864949633&amp;sdata=3DROR4%2FyD1WqWDb1rCbJx3ERqTiMCQ9=
2ibkyz26kYZdD8%3D&amp;reserved=3D0" target=3D"_blank"><span style=3D"color:=
rgb(5,99,193)">https://www.linkedin.com/in/dr2lopez/</span></a>=C2=A0<u></u=
><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"ES" style=3D"font-size:10pt">=C2=A0<u>=
</u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"ES" style=3D"font-size:10pt">e-mail:=
=C2=A0</span><span lang=3D"EN-GB" style=3D"font-size:10pt"><a href=3D"mailt=
o:diego.r.lopez@telefonica.com" target=3D"_blank"><span lang=3D"ES" style=
=3D"color:rgb(5,99,193)">diego.r.lopez@telefonica.com</span></a></span><spa=
n lang=3D"ES" style=3D"font-size:10pt"><u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB" style=3D"font-size:10pt">Tel:=
=C2=A0=C2=A0=C2=A0 =C2=A0=C2=A0=C2=A0=C2=A0 +34 913 129 041<u></u><u></u></=
span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB" style=3D"font-size:10pt">Mobile=
: =C2=A0+34 682 051 091<u></u><u></u></span></p>
</div>
<p class=3D"MsoNormal"><span lang=3D"EN-GB" style=3D"font-size:10pt">------=
----------------------------</span><span style=3D"font-size:10pt"><u></u><u=
></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10pt"><u></u>=C2=A0<u></u><=
/span></p>
<div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:0.5in">On 22/09/2020, 18:01, &q=
uot;Linda Dunbar&quot; &lt;<a href=3D"mailto:linda.dunbar@futurewei.com" ta=
rget=3D"_blank">linda.dunbar@futurewei.com</a>&gt; wrote:<u></u><u></u></p>
</div>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:0.5in"><u></u>=C2=A0<u></u></p>
</div>
<p class=3D"MsoNormal" style=3D"margin-left:0.5in">Diego: <u></u><u></u></p=
>
<p class=3D"MsoNormal" style=3D"margin-left:0.5in">=C2=A0<u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:0.5in">Thank you very much for =
the reflection of the Capabilities Information Model Draft. Agree with your=
 statement that =E2=80=9Cthe capability data model was evolving in a quite =
reasonable and pragmatic way, including running
 code at the hackathons=E2=80=9D. <u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:0.5in">=C2=A0<u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:0.5in">Looks like Eric Vyncke s=
till wants the information model to be fixed to clear his =E2=80=9CDISCUSS=
=E2=80=9D ballot.
<u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:0.5in">How about the following =
steps:<u></u><u></u></p>
<p style=3D"margin-left:1in">
<u></u><span>-<span style=3D"font:7pt &quot;Times New Roman&quot;">=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0
</span></span><u></u>Ask Roman=E2=80=99s advice if we can simplify the Info=
rmation Model mainly to reflect what has been in the Data Model.<u></u><u><=
/u></p>
<p style=3D"margin-left:1in">
<u></u><span>-<span style=3D"font:7pt &quot;Times New Roman&quot;">=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0
</span></span><u></u>Or, drop the Information model draft and remove the re=
fence to the draft, but Roman has to convince Eric to agree not having the =
information model.
<u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:0.5in">=C2=A0<u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:0.5in">What do you think? <u></=
u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:0.5in">=C2=A0<u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:0.5in">Linda<u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:0.5in">=C2=A0<u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:0.5in">=C2=A0<u></u><u></u></p>
<div>
<div style=3D"border-right:none;border-bottom:none;border-left:none;border-=
top:1pt solid rgb(225,225,225);padding:3pt 0in 0in">
<p class=3D"MsoNormal" style=3D"margin-left:0.5in"><b>From:</b> Diego R. Lo=
pez &lt;<a href=3D"mailto:diego.r.lopez@telefonica.com" target=3D"_blank">d=
iego.r.lopez@telefonica.com</a>&gt;
<br>
<b>Sent:</b> Tuesday, September 22, 2020 9:50 AM<br>
<b>To:</b> Mr. Jaehoon Paul Jeong &lt;<a href=3D"mailto:jaehoon.paul@gmail.=
com" target=3D"_blank">jaehoon.paul@gmail.com</a>&gt;; Linda Dunbar &lt;<a =
href=3D"mailto:linda.dunbar@futurewei.com" target=3D"_blank">linda.dunbar@f=
uturewei.com</a>&gt;<br>
<b>Cc:</b> Xialiang (Frank) &lt;<a href=3D"mailto:frank.xialiang@huawei.com=
" target=3D"_blank">frank.xialiang@huawei.com</a>&gt;; Yoav Nir &lt;<a href=
=3D"mailto:ynir.ietf@gmail.com" target=3D"_blank">ynir.ietf@gmail.com</a>&g=
t;; John Strassner &lt;<a href=3D"mailto:John.sc.Strassner@huawei.com" targ=
et=3D"_blank">John.sc.Strassner@huawei.com</a>&gt;;
 Aldo Basile &lt;<a href=3D"mailto:cataldo.basile@polito.it" target=3D"_bla=
nk">cataldo.basile@polito.it</a>&gt;; Roman Danyliw &lt;<a href=3D"mailto:r=
dd@cert.org" target=3D"_blank">rdd@cert.org</a>&gt;<br>
<b>Subject:</b> Re: Offer for Revision Help for I2NSF NSFs Capabilities Inf=
ormation Model Draft<u></u><u></u></p>
</div>
</div>
<p class=3D"MsoNormal" style=3D"margin-left:0.5in">=C2=A0<u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:0.5in"><span><span style=3D"fon=
t-size:10pt">H</span></span><span><span lang=3D"ES" style=3D"font-size:10pt=
">i Paul,</span></span><u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:0.5in"><span><span lang=3D"ES" =
style=3D"font-size:10pt">=C2=A0</span></span><u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:0.5in"><span><span style=3D"fon=
t-size:10pt">Before you go for it, let me share with you some reflections o=
n the state of the draft, in the spirit of what I replied to Eric Vyncke.</=
span></span><u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:0.5in"><span><span style=3D"fon=
t-size:10pt">=C2=A0</span></span><u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:0.5in"><span style=3D"font-size=
:10pt">I must confess there has been a combination of events that made me t=
hink the best solution was to leave this draft to fade away. First, I was n=
ot (have not
 been yet) able to find a solution to most of Roman=E2=80=99s comments with=
out totally rewriting most, if not all, of the document.=C2=A0 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 mo=
del, 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 inf=
o model draft.</span><u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:0.5in"><span style=3D"font-size=
:10pt">=C2=A0</span><u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:0.5in"><span style=3D"font-size=
:10pt">As I told Eric, I believe the current capability model has a powerfu=
l (though probably not yet complete) calculus for policy description and va=
lidation,
 but not directly related to the management mechanisms addressed in the cap=
ability data model and the other data models produced in I2NSF. I believe t=
here 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 con=
solidate and therefore imply an extension of the I2NSF lifetime. I would li=
ke to know your position(*) about such an extension, =C2=A0that could also =
become an opportunity to work in other
 matters related to attestation (in the light of the work in RATS and the M=
UD initiative within the Ops Area) and accounting.</span><u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:0.5in"><span style=3D"font-size=
:10pt">=C2=A0</span><u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:0.5in"><span style=3D"font-size=
:10pt">Be goode,</span><u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:0.5in"><span style=3D"font-size=
:10pt">=C2=A0</span><u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:0.5in"><span style=3D"font-size=
:10pt">(*) I assume you are in favor, Paul. But I=E2=80=99d like to get Lin=
da=E2=80=99s, Yoav=E2=80=99s and Roman=E2=80=99s ideas, as well as the avai=
lability to work on this from Frank, John
 and Aldo.</span><u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:0.5in"><span style=3D"font-size=
:10pt">=C2=A0</span><u></u><u></u></p>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:0.5in"><span style=3D"font-size=
:10pt">--</span><u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:0.5in"><span lang=3D"ES" style=
=3D"font-size:10pt">&quot;Esta vez no fallaremos, Doctor Infierno&quot;</sp=
an><u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:0.5in"><span lang=3D"ES" style=
=3D"font-size:10pt">=C2=A0</span><u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:0.5in"><span lang=3D"ES" style=
=3D"font-size:10pt">Dr Diego R. Lopez</span><u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:0.5in"><span lang=3D"ES" style=
=3D"font-size:10pt">Telefonica I+D</span><u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:0.5in"><span lang=3D"ES" style=
=3D"font-size:10pt"><a href=3D"https://nam11.safelinks.protection.outlook.c=
om/?url=3Dhttps%3A%2F%2Fwww.linkedin.com%2Fin%2Fdr2lopez%2F&amp;data=3D02%7=
C01%7Clinda.dunbar%40futurewei.com%7C08a48858d7bd4d843a6e08d85f47b438%7C0fe=
e8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C637364108864949633&amp;sdata=3DROR4=
%2FyD1WqWDb1rCbJx3ERqTiMCQ92ibkyz26kYZdD8%3D&amp;reserved=3D0" target=3D"_b=
lank"><span style=3D"color:rgb(5,99,193)">https://www.linkedin.com/in/dr2lo=
pez/</span></a>=C2=A0</span><u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:0.5in"><span lang=3D"ES" style=
=3D"font-size:10pt">=C2=A0</span><u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:0.5in"><span lang=3D"ES" style=
=3D"font-size:10pt">e-mail:=C2=A0</span><span lang=3D"EN-GB" style=3D"font-=
size:10pt"><a href=3D"mailto:diego.r.lopez@telefonica.com" target=3D"_blank=
"><span lang=3D"ES" style=3D"color:rgb(5,99,193)">diego.r.lopez@telefonica.=
com</span></a></span><u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:0.5in"><span lang=3D"EN-GB" sty=
le=3D"font-size:10pt">Tel:=C2=A0=C2=A0=C2=A0 =C2=A0=C2=A0=C2=A0=C2=A0 +34 9=
13 129 041</span><u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:0.5in"><span lang=3D"EN-GB" sty=
le=3D"font-size:10pt">Mobile: =C2=A0+34 682 051 091</span><u></u><u></u></p=
>
</div>
<p class=3D"MsoNormal" style=3D"margin-left:0.5in"><span lang=3D"EN-GB" sty=
le=3D"font-size:10pt">----------------------------------</span><u></u><u></=
u></p>
<p class=3D"MsoNormal" style=3D"margin-left:0.5in"><span style=3D"font-size=
:10pt">=C2=A0</span><u></u><u></u></p>
<div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:1in">On 17/09/2020, 01:42, &quo=
t;Mr. Jaehoon Paul Jeong&quot; &lt;<a href=3D"mailto:jaehoon.paul@gmail.com=
" target=3D"_blank">jaehoon.paul@gmail.com</a>&gt; wrote:<u></u><u></u></p>
</div>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:1in">=C2=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:1in">Hi Linda,<u></u><u></u></p=
>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:1in">I will address our AD Roma=
n&#39;s comments on this NSFs capabilities information draft as the 2nd edi=
tor through the collaboration with Frank (the 1st editor) and the other aut=
hors.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:1in">=C2=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:1in">I CC our AD Roman and the =
other authors, such as John and Cataldo.<u></u><u></u></p>
</div>
<div>
<pre style=3D"margin-left:1in"><span style=3D"font-size:9.5pt">=C2=A0</span=
><u></u><u></u></pre>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:1in">Thanks for your support an=
d guidance.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:1in">=C2=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:1in">Best Regards,<u></u><u></u=
></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:1in">Paul<u></u><u></u></p>
</div>
</div>
<p class=3D"MsoNormal" style=3D"margin-left:1in">=C2=A0<u></u><u></u></p>
<div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:1in">2020<span lang=3D"ZH-CN" s=
tyle=3D"font-family:&quot;Malgun Gothic&quot;,sans-serif">=EB=85=84</span> =
9<span lang=3D"ZH-CN" style=3D"font-family:&quot;Malgun Gothic&quot;,sans-s=
erif">=EC=9B=94</span> 17<span lang=3D"ZH-CN" style=3D"font-family:&quot;Ma=
lgun Gothic&quot;,sans-serif">=EC=9D=BC</span>
 (<span lang=3D"ZH-CN" style=3D"font-family:&quot;Malgun Gothic&quot;,sans-=
serif">=EB=AA=A9</span>) <span lang=3D"ZH-CN" style=3D"font-family:&quot;Ma=
lgun Gothic&quot;,sans-serif">
=EC=98=A4=EC=A0=84</span><span lang=3D"ZH-CN"> </span>3:44, Linda Dunbar &l=
t;<a href=3D"mailto:linda.dunbar@futurewei.com" target=3D"_blank">linda.dun=
bar@futurewei.com</a>&gt;<span lang=3D"ZH-CN" style=3D"font-family:&quot;Ma=
lgun Gothic&quot;,sans-serif">=EB=8B=98=EC=9D=B4</span><span lang=3D"ZH-CN"=
>
</span><span lang=3D"ZH-CN" style=3D"font-family:&quot;Malgun Gothic&quot;,=
sans-serif">=EC=9E=91=EC=84=B1</span>:<u></u><u></u></p>
</div>
<blockquote style=3D"border-top:none;border-right:none;border-bottom:none;b=
order-left:1pt solid rgb(204,204,204);padding:0in 0in 0in 6pt;margin:5pt 0i=
n 5pt 4.8pt">
<div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:1in">
Paul, <u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:1in">
=C2=A0<u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:1in">
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 h=
as been over a year since the AD comments were given.=C2=A0 We need to move=
 the draft forward. Therefore, I2NSF
 chairs have authorized you to be one of the editors to address the AD comm=
ents and revise the draft.
<u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:1in">
=C2=A0<u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:1in">
=C2=A0<u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:1in">
Thank you very much. <u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:1in">
=C2=A0<u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:1in">
Linda &amp; Yoav<u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:1in">
=C2=A0<u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:1in">
=C2=A0<u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:1in">
<b>From:</b> Mr. Jaehoon Paul Jeong &lt;<a href=3D"mailto:jaehoon.paul@gmai=
l.com" target=3D"_blank">jaehoon.paul@gmail.com</a>&gt;
<br>
<b>Sent:</b> Sunday, September 13, 2020 10:09 AM<br>
<b>To:</b> Xialiang (Frank) &lt;<a href=3D"mailto:frank.xialiang@huawei.com=
" target=3D"_blank">frank.xialiang@huawei.com</a>&gt;<br>
<b>Cc:</b> Linda Dunbar &lt;<a href=3D"mailto:linda.dunbar@futurewei.com" t=
arget=3D"_blank">linda.dunbar@futurewei.com</a>&gt;; Yoav Nir &lt;<a href=
=3D"mailto:ynir.ietf@gmail.com" target=3D"_blank">ynir.ietf@gmail.com</a>&g=
t;; DIEGO LOPEZ GARCIA &lt;<a href=3D"mailto:diego.r.lopez@telefonica.com" =
target=3D"_blank">diego.r.lopez@telefonica.com</a>&gt;;
 Jaehoon Jeong &lt;<a href=3D"mailto:jaehoon.paul@gmail.com" target=3D"_bla=
nk">jaehoon.paul@gmail.com</a>&gt;<br>
<b>Subject:</b> Offer for Revision Help for I2NSF NSFs Capabilities Informa=
tion Model Draft<u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:1in">
=C2=A0<u></u><u></u></p>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:1in">
Hi Frank,<u></u><u></u></p>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:1in">
Could I help you to revise your information model draft for our AD Roman Da=
nyliw&#39;s review comments=C2=A0 as a co-editor?<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:1in">
<a href=3D"https://nam11.safelinks.protection.outlook.com/?url=3Dhttps%3A%2=
F%2Fdatatracker.ietf.org%2Fdoc%2Fdraft-ietf-i2nsf-capability%2F%3Finclude_t=
ext%3D1&amp;data=3D02%7C01%7Clinda.dunbar%40futurewei.com%7C08a48858d7bd4d8=
43a6e08d85f47b438%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C637364108864=
959626&amp;sdata=3DGUrbaYu2Q4N1YNUUet2oVRPqbynA78cSBTf%2FBeSCY44%3D&amp;res=
erved=3D0" target=3D"_blank">https://datatracker.ietf.org/doc/draft-ietf-i2=
nsf-capability/?include_text=3D1</a><u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:1in">
=C2=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:1in">
As you know, I have finished our I2NSF data model drafts.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:1in">
=C2=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:1in">
I am happy to work on the revision with you in order to complete our I2NSF =
deliverables.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:1in">
=C2=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:1in">
Thanks.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:1in">
=C2=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:1in">
Best Regards,<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:1in">
Paul<u></u><u></u></p>
</div>
</div>
</div>
</div>
</blockquote>
</div>
<p class=3D"MsoNormal" style=3D"margin-left:0.5in">=C2=A0<u></u><u></u></p>
<div style=3D"margin-left:0.5in">
<div class=3D"MsoNormal" align=3D"center" style=3D"text-align:center">
<hr size=3D"1" width=3D"100%" align=3D"center">
</div>
</div>
<p class=3D"MsoNormal" style=3D"margin-left:0.5in"><span style=3D"font-size=
:7.5pt;font-family:Arial,sans-serif;color:gray"><br>
Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, pu=
ede contener informaci=C3=B3n privilegiada o confidencial y es para uso exc=
lusivo de la persona o entidad de destino. Si no es usted. el destinatario =
indicado, queda notificado de que la
 lectura, utilizaci=C3=B3n, divulgaci=C3=B3n y/o copia sin autorizaci=C3=B3=
n puede estar prohibida en virtud de la legislaci=C3=B3n vigente. Si ha rec=
ibido este mensaje por error, le rogamos que nos lo comunique inmediatament=
e por esta misma v=C3=ADa y proceda a su destrucci=C3=B3n.<br>
<br>
The information contained in this transmission is privileged and confidenti=
al 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 y=
ou have received this transmission in error, do not read it. Please immedia=
tely reply to the sender that you have received this communication in error=
 and then delete it.<br>
<br>
Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinat=C3=A1=
rio, pode conter informa=C3=A7=C3=A3o privilegiada ou confidencial e =C3=A9=
 para uso exclusivo da pessoa ou entidade de destino. Se n=C3=A3o =C3=A9 vo=
ssa senhoria o destinat=C3=A1rio indicado, fica notificado de que a
 leitura, utiliza=C3=A7=C3=A3o, divulga=C3=A7=C3=A3o e/ou c=C3=B3pia sem au=
toriza=C3=A7=C3=A3o pode estar proibida em virtude da legisla=C3=A7=C3=A3o =
vigente. Se recebeu esta mensagem por erro, rogamos-lhe que nos o comunique=
 imediatamente por esta mesma via e proceda a sua destrui=C3=A7=C3=A3o</spa=
n><u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<div class=3D"MsoNormal" align=3D"center" style=3D"text-align:center">
<hr size=3D"2" width=3D"100%" align=3D"center">
</div>
<p class=3D"MsoNormal"><span style=3D"font-size:7.5pt;font-family:Arial,san=
s-serif;color:gray"><br>
Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, pu=
ede contener informaci=C3=B3n privilegiada o confidencial y es para uso exc=
lusivo de la persona o entidad de destino. Si no es usted. el destinatario =
indicado, queda notificado de que la
 lectura, utilizaci=C3=B3n, divulgaci=C3=B3n y/o copia sin autorizaci=C3=B3=
n puede estar prohibida en virtud de la legislaci=C3=B3n vigente. Si ha rec=
ibido este mensaje por error, le rogamos que nos lo comunique inmediatament=
e por esta misma v=C3=ADa y proceda a su destrucci=C3=B3n.<br>
<br>
The information contained in this transmission is privileged and confidenti=
al 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 y=
ou have received this transmission in error, do not read it. Please immedia=
tely reply to the sender that you have received this communication in error=
 and then delete it.<br>
<br>
Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinat=C3=A1=
rio, pode conter informa=C3=A7=C3=A3o privilegiada ou confidencial e =C3=A9=
 para uso exclusivo da pessoa ou entidade de destino. Se n=C3=A3o =C3=A9 vo=
ssa senhoria o destinat=C3=A1rio indicado, fica notificado de que a
 leitura, utiliza=C3=A7=C3=A3o, divulga=C3=A7=C3=A3o e/ou c=C3=B3pia sem au=
toriza=C3=A7=C3=A3o pode estar proibida em virtude da legisla=C3=A7=C3=A3o =
vigente. Se recebeu esta mensagem por erro, rogamos-lhe que nos o comunique=
 imediatamente por esta mesma via e proceda a sua destrui=C3=A7=C3=A3o</spa=
n><u></u><u></u></p>
</div>
</div>

_______________________________________________<br>
I2nsf mailing list<br>
<a href=3D"mailto:I2nsf@ietf.org" target=3D"_blank">I2nsf@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/i2nsf" rel=3D"noreferrer" =
target=3D"_blank">https://www.ietf.org/mailman/listinfo/i2nsf</a><br>
</blockquote></div><br clear=3D"all"><div><br></div>-- <br><div dir=3D"ltr"=
><div dir=3D"ltr"><div><div dir=3D"ltr"><div><div dir=3D"ltr"><div><div dir=
=3D"ltr">=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D<br>Mr. Jaehoon (Paul) Jeong, Ph.D.<br>Associate Professor<b=
r>Department of Computer Science and Engineering<br>Sungkyunkwan University=
<br>Office: +82-31-299-4957<br>Email: <a href=3D"mailto:jaehoon.paul@gmail.=
com" target=3D"_blank">jaehoon.paul@gmail.com</a>,=C2=A0<a href=3D"mailto:p=
auljeong@skku.edu" style=3D"font-size:12.8px" target=3D"_blank">pauljeong@s=
kku.edu</a><br>Personal Homepage: <a href=3D"http://cpslab.skku.edu/people-=
jaehoon-jeong.php" target=3D"_blank">http://iotlab.skku.edu/people-jaehoon-=
jeong.php</a><br></div></div></div></div></div></div></div></div>
</div>

--00000000000040aca705b137a05f--


From nobody Fri Oct  9 07:58:18 2020
Return-Path: <linda.dunbar@futurewei.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 A81333A090B for <i2nsf@ietfa.amsl.com>; Fri,  9 Oct 2020 07:58:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.352
X-Spam-Level: 
X-Spam-Status: No, score=0.352 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, LH_URI_DOM_IN_PATH=2.331, RCVD_IN_MSPIKE_H2=-0.001, T_FILL_THIS_FORM_SHORT=0.01, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=futurewei.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 S7rigGe1BR2o for <i2nsf@ietfa.amsl.com>; Fri,  9 Oct 2020 07:58:13 -0700 (PDT)
Received: from NAM10-BN7-obe.outbound.protection.outlook.com (mail-bn7nam10on2096.outbound.protection.outlook.com [40.107.92.96]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5C0003A02DC for <i2nsf@ietf.org>; Fri,  9 Oct 2020 07:58:12 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=iffsmXiuhZkwiXDgUTb58jIh5GBcGSuAu2OOk1pFft27nDGNKmm9tr3GODqJZUoS9PBwjuon7pIYpLphVZoev+mYnsC2lazCZNyVkvOcL/0vKOaoTwaIY379KfbAtuYnwcu739mLgeWEMfOkvB0c00mqkvR4QwRZqFCmQP6pUs20S+A/alv1ixSGHUkrbmWCstjV6RAxFLihlBAyai7zIsrf/DG657Xir5ng5g4IJ2cUTyuN5jGK7y4EkrYI7ebK/6C6SSxEUVZzFob7WS7yYquH6BS9A0Sb+pBXud84PXYJcNgx+GFjwKPzlJ43yTaUgbBZR4qGrRinY3tz0q5+gg==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=KwnoDOWbBlJG3l803oLVSwk0faf/j1CensdiXMMsjgo=; b=l2ofFZSyKrme1lGg+3TWUZRyd7zZggTNRz8eQPCo+f1jlTyZucZGIa3oU6MYJdEwQY3TqjCvvhCM5OSoPp2fBrDuQclToHP1zzlCXcWSiGX3bpiSWXrVRUmMAYvHeD83WRuMtsYIfNKv9HofvFIAmA+/iHiWo1tmRJJjaTC8n5c7lwHhtj5OWVwIqYfY9V2uc8jMvv9Rxq9XKErkS2P6X6ifqP3moU+rcR2KKRiKiLrouL6cmRvyPsLf2cbz3N6SL5kj8estmTAi2XGZRooD92JI9mUBrKy4IRIFItLnvjpGOZh3k/d/plAxx0t4UBXZ6CgkUOMqHUC3y+XhAOkqIw==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=futurewei.com; dmarc=pass action=none header.from=futurewei.com; dkim=pass header.d=futurewei.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=Futurewei.com; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=KwnoDOWbBlJG3l803oLVSwk0faf/j1CensdiXMMsjgo=; b=dk5QUV+Z7rIEKYVOoQpp7xLtZ7W16Uxh87jr8ZPSxW2a1/R7ydzhrXy5Uz9evsTFT8BJFpRgJ+04vX4RccW9RsJhi9I24VN9ghGC7eCVW9tvkYAs5pMxTr8a/k4Fha3mSloByXEBq/Qz0SnIWdakR4EzPIcNwL4Uoq3N/hEv0K8=
Received: from SN6PR13MB2334.namprd13.prod.outlook.com (2603:10b6:805:55::16) by SA0PR13MB4094.namprd13.prod.outlook.com (2603:10b6:806:9f::10) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3477.11; Fri, 9 Oct 2020 14:58:10 +0000
Received: from SN6PR13MB2334.namprd13.prod.outlook.com ([fe80::8c05:b4f5:cc16:eeb]) by SN6PR13MB2334.namprd13.prod.outlook.com ([fe80::8c05:b4f5:cc16:eeb%7]) with mapi id 15.20.3477.011; Fri, 9 Oct 2020 14:58:10 +0000
From: Linda Dunbar <linda.dunbar@futurewei.com>
To: "i2nsf@ietf.org" <i2nsf@ietf.org>
Thread-Topic: 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? 
Thread-Index: Adaduvh8zkKOxDGwSr68F8vVxkzqSwAkUk9g
Date: Fri, 9 Oct 2020 14:58:09 +0000
Message-ID: <SN6PR13MB23342D6464F8F67CBFE0129C85080@SN6PR13MB2334.namprd13.prod.outlook.com>
References: <SN6PR13MB23343DE9392FA9EDDDA65651850B0@SN6PR13MB2334.namprd13.prod.outlook.com>
In-Reply-To: <SN6PR13MB23343DE9392FA9EDDDA65651850B0@SN6PR13MB2334.namprd13.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=none action=none header.from=futurewei.com;
x-originating-ip: [2603:8081:1700:ab:cd16:586:4419:7b06]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: ef492658-d10a-4d9c-325b-08d86c63bcf5
x-ms-traffictypediagnostic: SA0PR13MB4094:
x-microsoft-antispam-prvs: <SA0PR13MB40944A5135A8AD1640DC080385080@SA0PR13MB4094.namprd13.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: md2/t9SryyRnYJ1XR1HhwMcMuLSPIJoMEtAS1uOF8HYDfDwEBa0LaK1N1lFiD/Fhj0rGd9V26shL113B+qIy6gFxvarMeU0gzMDXhaQ8MBqCcslZIOFIBejEPrOHfaC1sD73GOMdlJZKeuGnph/MfasKk6Dr7J3ZcPyYML9wrbcw8FVzvAN6dXX5D6O/CtuFbkWq9sDbVTmQYBUYEDTUvlO+0nE7ceuqtBKOxPpTYDLv7hmS0jOMPYKf27jj2u0iFVzLA9D68NLw2216M1J6gJMDlohAivadVqkRwRjepyeZKzG7TkJSl4jR0izqW04zNYqMXrIUYTLIQ1H6PytB1E1qXmb5icbOwDvLm3ms4sTFFUh7Miz5l42KqB9vu+yA85drU090DBF4kvgVeqMtHmdoWTgTIz7DKVb5Xk6i/gL5pCtR04/TrJ+78IfyhrO/qJFgjCZZrjYgPX1croiSew==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;  IPV:NLI; SFV:NSPM; H:SN6PR13MB2334.namprd13.prod.outlook.com; PTR:; CAT:NONE;  SFS:(4636009)(136003)(346002)(366004)(396003)(376002)(39840400004)(4743002)(66446008)(5660300002)(55016002)(83380400001)(86362001)(33656002)(6506007)(44832011)(7696005)(166002)(53546011)(83080400001)(66574015)(186003)(76116006)(316002)(6916009)(66476007)(9686003)(45080400002)(30864003)(71200400001)(66946007)(8676002)(2906002)(64756008)(8936002)(52536014)(478600001)(66556008)(966005)(219693003); DIR:OUT; SFP:1102; 
x-ms-exchange-antispam-messagedata: lwonL6ACXy6jQXbToGuiwg7uYOUK/haWroHEx1PbNvo+Rdno1ZD8v7ZbGUMAl4waTo4D6RdOtpcJSpcRs1SYANOKntX3evOP2IY7EOv2zu5KMXml1Vgeshi4RrKp6tWX1SmF/1Q7VeoB6x+A45TTsDsDnHgWwMpdzYgIL02coIGjaE9btn2qKbmDPCmDAVADBS27i21e5hFlQFvrR2/5tPuFkevPFLRxPF3NYUg9oshAVcfU8c5AFCWWls/cYBywhIsGPeF/kG58RkKNbNTk9Ot9NdT/8XsFXKyJjzrHnQuzzJhRu9yumfii0UWEOXh8Eho96EGzZXgE9RKR0zMVGjAhxZH2pn0PBvnWfuI6P4WfC1J42UTn4Xier27qCHKk9KbDSepMmZoQHSmqE8jCHRNzPp/8aJKIBMOr1TwUhrNl0sMlkKqYT0gdKtBRqCfC7hwznSpeK/uwY8u1xuJ/NvjXhl5FXHrqoNb2LrISa2dB20wImI78BQhBNHuSqp/VVP+6maX2XWr3FvhJeQOJlNOELEEw4/eTbAclE4BRgLKJ+M7jZFQGDT35Zr4KlgIoMWXzG7dHIXBWjZKvKPtOnDj8otlGmvWPHJDAXEg79REUX78dEHzoiMuWhqwhtiNJrpIJ7W5UyTrLcZwuVSDjr1xjWe+5oDAhKz29XAudJZEZj9zEmNMuNOTVe+2/Olqp39M2LZ00Lqxg1oUr3mkZyw==
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_SN6PR13MB23342D6464F8F67CBFE0129C85080SN6PR13MB2334namp_"
MIME-Version: 1.0
X-OriginatorOrg: Futurewei.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: SN6PR13MB2334.namprd13.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: ef492658-d10a-4d9c-325b-08d86c63bcf5
X-MS-Exchange-CrossTenant-originalarrivaltime: 09 Oct 2020 14:58:09.9493 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 0fee8ff2-a3b2-4018-9c75-3a1d5591fedc
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: imJTAl+bKATTMS8QSaajdB1IH/7Cmk88HlRcBSS+NGRUDeI0dmsMA9Hp0GT+IWxlXM53fv7QTLIFrGMahyG8mQ==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: SA0PR13MB4094
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2nsf/KSCwt3B7rt7j3eoXrMkNcwH2i6c>
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: Fri, 09 Oct 2020 14:58:17 -0000

--_000_SN6PR13MB23342D6464F8F67CBFE0129C85080SN6PR13MB2334namp_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

STJOU0YgV0csDQoNCkNvcnJlY3Rpb246DQoNClRoZXJlIGhhcyBiZWVuIE5PIG9iamVjdCB0byB0
aGUgQXV0aG9y4oCZcyByZXF1ZXN0IGZvciBzdW5zZXR0aW5nIHRoZSBkcmFmdC1pZXRmLWkybnNm
LWNhcGFiaWxpdHktNS4NCg0KV2UgaGF2ZSBtYXJrZWQgdGhlIGRyYWZ0IGFzIOKAnERFQUTigJ0g
aW4gdGhlIFdHIHN0YXR1cy4NCg0KTWFueSB0aGFua3MgdG8gdGhlIGF1dGhvcnMgZm9yIHB1dHRp
bmcgdGhlIGVmZm9ydCBpbiB0aGlzIGRyYWZ0IGZvciBraWNrc3RhcnRpbmcgYWxsIHRoZSBkYXRh
IG1vZGVscyBpbiBJMk5TRiBXRy4NCg0KTGluZGEgJiBZb2F2DQoNCkZyb206IExpbmRhIER1bmJh
cg0KU2VudDogVGh1cnNkYXksIE9jdG9iZXIgOCwgMjAyMCA0OjM2IFBNDQpUbzogaTJuc2ZAaWV0
Zi5vcmcNClN1YmplY3Q6IGRyYWZ0LWlldGYtaTJuc2YtY2FwYWJpbGl0eS0wNSBpcyBvZmZpY2lh
bGx5IHJlbW92ZWQgZnJvbSBJMk5TRiBXRyAoIHdhcyBSRTogSXMgdGhlcmUgYW55IG9iamVjdGlv
biBvZiBzdW5zZXQgdGhlIEkyTlNGIENhcGFiaWxpdGllcyBJbmZvcm1hdGlvbiBNb2RlbCBEcmFm
dCBhbmQgbWVyZ2UgdGhlIHJlbGV2YW50IGluZm9ybWF0aW9uIHRvIHRoZSBJMk5TRiBDYXBhYmls
aXR5IERhdGEgbW9kZWwgZHJhZnQ/DQoNCkkybnNmIFdHLA0KDQpUaGVyZSBoYXMgYmVlbiBhbnkg
b2JqZWN0aW9uIHRvIHRoZSBBdXRob3LigJlzIHJlcXVlc3QgZm9yIHN1bnNldHRpbmcgdGhlICBk
cmFmdC1pZXRmLWkybnNmLWNhcGFiaWxpdHktMDUuDQoNCkF1dGhvcnMgb2YgdGhlIGRyYWZ0LWll
dGYtaTJuc2YtY2FwYWJpbGl0eS1kYXRhLW1vZGVsOiBwbGVhc2UgcmVtb3ZlIHRoZSByZWZlcmVu
Y2UgdG8gdGhlIENhcGFiaWxpdHkgSW5mb3JtYXRpb24gTW9kZWwgYW5kIHVwbG9hZCBhIG5ldyBk
cmFmdC4gV2UgY2FuIGFzayBJRVNHIHRvIHJlLXJldmlldyBpdC4NCg0KVGhhbmsgeW91IHZlcnkg
bXVjaC4NCg0KTGluZGEgJiBZb2F2Lg0KDQpGcm9tOiBMaW5kYSBEdW5iYXINClNlbnQ6IE1vbmRh
eSwgU2VwdGVtYmVyIDI4LCAyMDIwIDExOjAwIEFNDQpUbzogaTJuc2ZAaWV0Zi5vcmc8bWFpbHRv
OmkybnNmQGlldGYub3JnPg0KU3ViamVjdDogSXMgdGhlcmUgYW55IG9iamVjdGlvbiBvZiBzdW5z
ZXQgdGhlIEkyTlNGIENhcGFiaWxpdGllcyBJbmZvcm1hdGlvbiBNb2RlbCBEcmFmdCBhbmQgbWVy
Z2UgdGhlIHJlbGV2YW50IGluZm9ybWF0aW9uIHRvIHRoZSBJMk5TRiBDYXBhYmlsaXR5IERhdGEg
bW9kZWwgZHJhZnQ/DQoNCkkyTlNGIFdHLA0KDQpBcyBEaWVnbyBoYXMgZXhwcmVzc2VkIHRoYXQg
dGhlIG9yaWdpbmFsIEkyTlNGIGNhcGFiaWxpdHkgaW5mb3JtYXRpb24gbW9kZWwgd2FzIGJhc2Vk
IG9uIGEgcG9saWN5IGV4cHJlc3Npb24gY2FsY3VsdXMgc3VpdGFibGUgZm9yIG1hbmlwdWxhdGlu
ZyBoaWdoLWxldmVsIHBvbGljeSBleHByZXNzaW9ucy4gIFRoZSBjYXBhYmlsaXR5IGRhdGEgbW9k
ZWwgaGFzIGJlZW4gZXZvbHZpbmcgaW4gYSBxdWl0ZSByZWFzb25hYmxlIGFuZCBwcmFnbWF0aWMg
d2F5LCBpbmNsdWRpbmcgcnVubmluZyBjb2RlIGF0IHRoZSBoYWNrYXRob25zLg0KDQpUaGUgSTJO
U0YgQ2FwYWJpbGl0eSBJbmZvcm1hdGlvbiBNb2RlbCBoYXMgZnVsZmlsbGVkIGl0cyBwdXJwb3Nl
IG9mIGtpY2tzdGFydGluZyBhbmQgZ3VpZGluZyB0aGUgZGF0YSBtb2RlbCwgYW5kIHRoZSBhdXRo
b3JzIGJlbGlldmUgdGhhdCBpdCBpcyBiZXR0ZXIgdG8gbGV0IHRoZSBjYXBhYmlsaXR5IGluZm9y
bWF0aW9uIG1vZGVsIHRvIGJlIHdpdGhkcmF3bi4gRm9yIHRoZSBjb250ZW50IGluIHRoZSBpbmZv
cm1hdGlvbiBtb2RlbCBzdGlsbCByZWxldmFudCB0byBJMk5TRiBDYXBhYmlsaXR5IERhdGEgTW9k
ZWwsIHRoZXkgc2hvdWxkIGJlIG1lcmdlZCBpbnRvIHRoZSBDYXBhYmlsaXR5IERhdGEgTW9kZWwu
DQoNCklzIHRoZXJlIGFueSBvYmplY3Rpb24gZnJvbSB0aGUgV0c/ICBJZiB3ZSBkb27igJl0IGhl
YXIgYW55IG9iamVjdGlvbiBieSBPY3QgNSwgd2Ugd2lsbCBjaGFuZ2UgdGhlIHN0YXR1cyBvZiB0
aGUgZHJhZnQuDQoNCkNoZWVycywNCg0KTGluZGEgJiBZb2F2DQoNCg0KDQpGcm9tOiBEaWVnbyBS
LiBMb3BleiA8ZGllZ28uci5sb3BlekB0ZWxlZm9uaWNhLmNvbTxtYWlsdG86ZGllZ28uci5sb3Bl
ekB0ZWxlZm9uaWNhLmNvbT4+DQpTZW50OiBUdWVzZGF5LCBTZXB0ZW1iZXIgMjIsIDIwMjAgNToz
NSBQTQ0KVG86IExpbmRhIER1bmJhciA8bGluZGEuZHVuYmFyQGZ1dHVyZXdlaS5jb208bWFpbHRv
OmxpbmRhLmR1bmJhckBmdXR1cmV3ZWkuY29tPj47IE1yLiBKYWVob29uIFBhdWwgSmVvbmcgPGph
ZWhvb24ucGF1bEBnbWFpbC5jb208bWFpbHRvOmphZWhvb24ucGF1bEBnbWFpbC5jb20+Pg0KQ2M6
IFhpYWxpYW5nIChGcmFuaykgPGZyYW5rLnhpYWxpYW5nQGh1YXdlaS5jb208bWFpbHRvOmZyYW5r
LnhpYWxpYW5nQGh1YXdlaS5jb20+PjsgWW9hdiBOaXIgPHluaXIuaWV0ZkBnbWFpbC5jb208bWFp
bHRvOnluaXIuaWV0ZkBnbWFpbC5jb20+PjsgSm9obiBTdHJhc3NuZXIgPEpvaG4uc2MuU3RyYXNz
bmVyQGh1YXdlaS5jb208bWFpbHRvOkpvaG4uc2MuU3RyYXNzbmVyQGh1YXdlaS5jb20+PjsgQWxk
byBCYXNpbGUgPGNhdGFsZG8uYmFzaWxlQHBvbGl0by5pdDxtYWlsdG86Y2F0YWxkby5iYXNpbGVA
cG9saXRvLml0Pj47IFJvbWFuIERhbnlsaXcgPHJkZEBjZXJ0Lm9yZzxtYWlsdG86cmRkQGNlcnQu
b3JnPj4NClN1YmplY3Q6IFJlOiBPZmZlciBmb3IgUmV2aXNpb24gSGVscCBmb3IgSTJOU0YgTlNG
cyBDYXBhYmlsaXRpZXMgSW5mb3JtYXRpb24gTW9kZWwgRHJhZnQNCg0KSGkgTGluZGEsDQoNCkni
gJlkIHByZWZlciB0aGUgc2Vjb25kIG9wdGlvbiwgYXMgaXQgc2VlbXMgbW9yZSBzdHJhaWdodGZv
cndhcmQgYW5kIG5hdHVyYWwgdG8gbWUsIGFuZCBpbiBwYXJhbGxlbCB3b3VsZCBsaWtlIHlvdSB0
byBjb25zaWRlciB0aGUgaWRlYSBvZiBhbiBJMk5TRiBleHRlbnNpb24gYWxsb3dpbmcgdXMgdG8g
cmV1c2UgdGhlIGNhcGFiaWxpdHkgbW9kZWwgZm9yIHBvbGljeS1jb250cm9sIHRyYW5zZm9ybWF0
aW9uLCBhbmQgdG8gaW5jb3Jwb3JhdGUgdGhlIGF0dGVzdGF0aW9uIG1hdHRlcnMgeW91IGtub3cg
SSB3YXMgc28gbXVjaCBpbnRlcmVzdGVkIGluLg0KDQpCZSBnb29kZSwNCg0KLS0NCiJFc3RhIHZl
eiBubyBmYWxsYXJlbW9zLCBEb2N0b3IgSW5maWVybm8iDQoNCkRyIERpZWdvIFIuIExvcGV6DQpU
ZWxlZm9uaWNhIEkrRA0KaHR0cHM6Ly93d3cubGlua2VkaW4uY29tL2luL2RyMmxvcGV6LzxodHRw
czovL25hbTExLnNhZmVsaW5rcy5wcm90ZWN0aW9uLm91dGxvb2suY29tLz91cmw9aHR0cHMlM0El
MkYlMkZ3d3cubGlua2VkaW4uY29tJTJGaW4lMkZkcjJsb3BleiUyRiZkYXRhPTAyJTdDMDElN0Ns
aW5kYS5kdW5iYXIlNDBmdXR1cmV3ZWkuY29tJTdDMDhhNDg4NThkN2JkNGQ4NDNhNmUwOGQ4NWY0
N2I0MzglN0MwZmVlOGZmMmEzYjI0MDE4OWM3NTNhMWQ1NTkxZmVkYyU3QzElN0MwJTdDNjM3MzY0
MTA4ODY0OTQ5NjMzJnNkYXRhPVJPUjQlMkZ5RDFXcVdEYjFyQ2JKeDNFUnFUaU1DUTkyaWJreXoy
NmtZWmREOCUzRCZyZXNlcnZlZD0wPg0KDQplLW1haWw6IGRpZWdvLnIubG9wZXpAdGVsZWZvbmlj
YS5jb208bWFpbHRvOmRpZWdvLnIubG9wZXpAdGVsZWZvbmljYS5jb20+DQpUZWw6ICAgICAgICAg
KzM0IDkxMyAxMjkgMDQxDQpNb2JpbGU6ICArMzQgNjgyIDA1MSAwOTENCi0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0NCg0KT24gMjIvMDkvMjAyMCwgMTg6MDEsICJMaW5kYSBEdW5i
YXIiIDxsaW5kYS5kdW5iYXJAZnV0dXJld2VpLmNvbTxtYWlsdG86bGluZGEuZHVuYmFyQGZ1dHVy
ZXdlaS5jb20+PiB3cm90ZToNCg0KRGllZ286DQoNClRoYW5rIHlvdSB2ZXJ5IG11Y2ggZm9yIHRo
ZSByZWZsZWN0aW9uIG9mIHRoZSBDYXBhYmlsaXRpZXMgSW5mb3JtYXRpb24gTW9kZWwgRHJhZnQu
IEFncmVlIHdpdGggeW91ciBzdGF0ZW1lbnQgdGhhdCDigJx0aGUgY2FwYWJpbGl0eSBkYXRhIG1v
ZGVsIHdhcyBldm9sdmluZyBpbiBhIHF1aXRlIHJlYXNvbmFibGUgYW5kIHByYWdtYXRpYyB3YXks
IGluY2x1ZGluZyBydW5uaW5nIGNvZGUgYXQgdGhlIGhhY2thdGhvbnPigJ0uDQoNCkxvb2tzIGxp
a2UgRXJpYyBWeW5ja2Ugc3RpbGwgd2FudHMgdGhlIGluZm9ybWF0aW9uIG1vZGVsIHRvIGJlIGZp
eGVkIHRvIGNsZWFyIGhpcyDigJxESVNDVVNT4oCdIGJhbGxvdC4NCkhvdyBhYm91dCB0aGUgZm9s
bG93aW5nIHN0ZXBzOg0KDQotICAgICAgICAgIEFzayBSb21hbuKAmXMgYWR2aWNlIGlmIHdlIGNh
biBzaW1wbGlmeSB0aGUgSW5mb3JtYXRpb24gTW9kZWwgbWFpbmx5IHRvIHJlZmxlY3Qgd2hhdCBo
YXMgYmVlbiBpbiB0aGUgRGF0YSBNb2RlbC4NCg0KLSAgICAgICAgICBPciwgZHJvcCB0aGUgSW5m
b3JtYXRpb24gbW9kZWwgZHJhZnQgYW5kIHJlbW92ZSB0aGUgcmVmZW5jZSB0byB0aGUgZHJhZnQs
IGJ1dCBSb21hbiBoYXMgdG8gY29udmluY2UgRXJpYyB0byBhZ3JlZSBub3QgaGF2aW5nIHRoZSBp
bmZvcm1hdGlvbiBtb2RlbC4NCg0KV2hhdCBkbyB5b3UgdGhpbms/DQoNCkxpbmRhDQoNCg0KRnJv
bTogRGllZ28gUi4gTG9wZXogPGRpZWdvLnIubG9wZXpAdGVsZWZvbmljYS5jb208bWFpbHRvOmRp
ZWdvLnIubG9wZXpAdGVsZWZvbmljYS5jb20+Pg0KU2VudDogVHVlc2RheSwgU2VwdGVtYmVyIDIy
LCAyMDIwIDk6NTAgQU0NClRvOiBNci4gSmFlaG9vbiBQYXVsIEplb25nIDxqYWVob29uLnBhdWxA
Z21haWwuY29tPG1haWx0bzpqYWVob29uLnBhdWxAZ21haWwuY29tPj47IExpbmRhIER1bmJhciA8
bGluZGEuZHVuYmFyQGZ1dHVyZXdlaS5jb208bWFpbHRvOmxpbmRhLmR1bmJhckBmdXR1cmV3ZWku
Y29tPj4NCkNjOiBYaWFsaWFuZyAoRnJhbmspIDxmcmFuay54aWFsaWFuZ0BodWF3ZWkuY29tPG1h
aWx0bzpmcmFuay54aWFsaWFuZ0BodWF3ZWkuY29tPj47IFlvYXYgTmlyIDx5bmlyLmlldGZAZ21h
aWwuY29tPG1haWx0bzp5bmlyLmlldGZAZ21haWwuY29tPj47IEpvaG4gU3RyYXNzbmVyIDxKb2hu
LnNjLlN0cmFzc25lckBodWF3ZWkuY29tPG1haWx0bzpKb2huLnNjLlN0cmFzc25lckBodWF3ZWku
Y29tPj47IEFsZG8gQmFzaWxlIDxjYXRhbGRvLmJhc2lsZUBwb2xpdG8uaXQ8bWFpbHRvOmNhdGFs
ZG8uYmFzaWxlQHBvbGl0by5pdD4+OyBSb21hbiBEYW55bGl3IDxyZGRAY2VydC5vcmc8bWFpbHRv
OnJkZEBjZXJ0Lm9yZz4+DQpTdWJqZWN0OiBSZTogT2ZmZXIgZm9yIFJldmlzaW9uIEhlbHAgZm9y
IEkyTlNGIE5TRnMgQ2FwYWJpbGl0aWVzIEluZm9ybWF0aW9uIE1vZGVsIERyYWZ0DQoNCkhpIFBh
dWwsDQoNCkJlZm9yZSB5b3UgZ28gZm9yIGl0LCBsZXQgbWUgc2hhcmUgd2l0aCB5b3Ugc29tZSBy
ZWZsZWN0aW9ucyBvbiB0aGUgc3RhdGUgb2YgdGhlIGRyYWZ0LCBpbiB0aGUgc3Bpcml0IG9mIHdo
YXQgSSByZXBsaWVkIHRvIEVyaWMgVnluY2tlLg0KDQpJIG11c3QgY29uZmVzcyB0aGVyZSBoYXMg
YmVlbiBhIGNvbWJpbmF0aW9uIG9mIGV2ZW50cyB0aGF0IG1hZGUgbWUgdGhpbmsgdGhlIGJlc3Qg
c29sdXRpb24gd2FzIHRvIGxlYXZlIHRoaXMgZHJhZnQgdG8gZmFkZSBhd2F5LiBGaXJzdCwgSSB3
YXMgbm90IChoYXZlIG5vdCBiZWVuIHlldCkgYWJsZSB0byBmaW5kIGEgc29sdXRpb24gdG8gbW9z
dCBvZiBSb21hbuKAmXMgY29tbWVudHMgd2l0aG91dCB0b3RhbGx5IHJld3JpdGluZyBtb3N0LCBp
ZiBub3QgYWxsLCBvZiB0aGUgZG9jdW1lbnQuICBTZWNvbmQsIHRoZSBmYWN0IHRoYXQgdGhlIGNh
cGFiaWxpdHkgZGF0YSBtb2RlbCB3YXMgZXZvbHZpbmcgaW4gYSBxdWl0ZSByZWFzb25hYmxlIGFu
ZCBwcmFnbWF0aWMgd2F5LCBpbmNsdWRpbmcgcnVubmluZyBjb2RlIGF0IHRoZSBoYWNrYXRob25z
LCBmb2xsb3dpbmcgdGhlIHNwaXJpdCBvZiB0aGUgaW5pdGlhbCB3b3JrIGluIHRoZSBpbmZvcm1h
dGlvbiBtb2RlbCwgYnV0IG5vdCBhdHRlbXB0aW5nIHRvIGFsaWduIHdpdGggaXRzIG1vc3QgcmVj
ZW50IGV2b2x1dGlvbi4gSWYgSSBoYXZlIG5vdCBzaGFyZWQgdGhpcyBwb3NpdGlvbiBiZWZvcmUg
aXMgYmVjYXVzZSBJIGhhdmUgYmVlbiBsb29raW5nIGZvciBhIHdheSB0byBtYWtlIHRoZSBpZGVh
IG9mIGJyaWRnaW5nIGNhcGFiaWxpdHkgZGVjbGFyYXRpb25zIGFuZCBzZWN1cml0eSBwb2xpY3kg
c3RhdGVtZW50cyBhdCB0aGUgSTJOU0YgY29udHJvbGxlciB2aWFibGUsIGFuZCBJIHdhcyBob3Bp
bmcgdG8gZmluZCBzdWNoIGEgd2F5IGJ5IHJldXNpbmcgcGFydCBvZiB0aGUgY2FwYWJpbGl0eSBp
bmZvIG1vZGVsIGRyYWZ0Lg0KDQpBcyBJIHRvbGQgRXJpYywgSSBiZWxpZXZlIHRoZSBjdXJyZW50
IGNhcGFiaWxpdHkgbW9kZWwgaGFzIGEgcG93ZXJmdWwgKHRob3VnaCBwcm9iYWJseSBub3QgeWV0
IGNvbXBsZXRlKSBjYWxjdWx1cyBmb3IgcG9saWN5IGRlc2NyaXB0aW9uIGFuZCB2YWxpZGF0aW9u
LCBidXQgbm90IGRpcmVjdGx5IHJlbGF0ZWQgdG8gdGhlIG1hbmFnZW1lbnQgbWVjaGFuaXNtcyBh
ZGRyZXNzZWQgaW4gdGhlIGNhcGFiaWxpdHkgZGF0YSBtb2RlbCBhbmQgdGhlIG90aGVyIGRhdGEg
bW9kZWxzIHByb2R1Y2VkIGluIEkyTlNGLiBJIGJlbGlldmUgdGhlcmUgaXMgYW4gb3Bwb3J0dW5p
dHkgZm9yIGFjY29tcGxpc2hpbmcgcG9saWN5LWNhcGFiaWxpdHkgYnJpZGdpbmcsIHVzaW5nIGFz
IGZvdW5kYXRpb24gdGhlIGN1cnJlbnQgY2FwYWJpbGl0eSBtb2RlbCwgdGhvdWdoIGl0IHNlZW1z
IHRvIG1lIHRoYXQgdGhpcyB0YXNrIHdvdWxkIHJlcXVpcmUgc29tZSB0aW1lIHRvIGNvbnNvbGlk
YXRlIGFuZCB0aGVyZWZvcmUgaW1wbHkgYW4gZXh0ZW5zaW9uIG9mIHRoZSBJMk5TRiBsaWZldGlt
ZS4gSSB3b3VsZCBsaWtlIHRvIGtub3cgeW91ciBwb3NpdGlvbigqKSBhYm91dCBzdWNoIGFuIGV4
dGVuc2lvbiwgIHRoYXQgY291bGQgYWxzbyBiZWNvbWUgYW4gb3Bwb3J0dW5pdHkgdG8gd29yayBp
biBvdGhlciBtYXR0ZXJzIHJlbGF0ZWQgdG8gYXR0ZXN0YXRpb24gKGluIHRoZSBsaWdodCBvZiB0
aGUgd29yayBpbiBSQVRTIGFuZCB0aGUgTVVEIGluaXRpYXRpdmUgd2l0aGluIHRoZSBPcHMgQXJl
YSkgYW5kIGFjY291bnRpbmcuDQoNCkJlIGdvb2RlLA0KDQooKikgSSBhc3N1bWUgeW91IGFyZSBp
biBmYXZvciwgUGF1bC4gQnV0IEnigJlkIGxpa2UgdG8gZ2V0IExpbmRh4oCZcywgWW9hduKAmXMg
YW5kIFJvbWFu4oCZcyBpZGVhcywgYXMgd2VsbCBhcyB0aGUgYXZhaWxhYmlsaXR5IHRvIHdvcmsg
b24gdGhpcyBmcm9tIEZyYW5rLCBKb2huIGFuZCBBbGRvLg0KDQotLQ0KIkVzdGEgdmV6IG5vIGZh
bGxhcmVtb3MsIERvY3RvciBJbmZpZXJubyINCg0KRHIgRGllZ28gUi4gTG9wZXoNClRlbGVmb25p
Y2EgSStEDQpodHRwczovL3d3dy5saW5rZWRpbi5jb20vaW4vZHIybG9wZXovPGh0dHBzOi8vbmFt
MTEuc2FmZWxpbmtzLnByb3RlY3Rpb24ub3V0bG9vay5jb20vP3VybD1odHRwcyUzQSUyRiUyRnd3
dy5saW5rZWRpbi5jb20lMkZpbiUyRmRyMmxvcGV6JTJGJmRhdGE9MDIlN0MwMSU3Q2xpbmRhLmR1
bmJhciU0MGZ1dHVyZXdlaS5jb20lN0MwOGE0ODg1OGQ3YmQ0ZDg0M2E2ZTA4ZDg1ZjQ3YjQzOCU3
QzBmZWU4ZmYyYTNiMjQwMTg5Yzc1M2ExZDU1OTFmZWRjJTdDMSU3QzAlN0M2MzczNjQxMDg4NjQ5
NDk2MzMmc2RhdGE9Uk9SNCUyRnlEMVdxV0RiMXJDYkp4M0VScVRpTUNROTJpYmt5ejI2a1laZEQ4
JTNEJnJlc2VydmVkPTA+DQoNCmUtbWFpbDogZGllZ28uci5sb3BlekB0ZWxlZm9uaWNhLmNvbTxt
YWlsdG86ZGllZ28uci5sb3BlekB0ZWxlZm9uaWNhLmNvbT4NClRlbDogICAgICAgICArMzQgOTEz
IDEyOSAwNDENCk1vYmlsZTogICszNCA2ODIgMDUxIDA5MQ0KLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLQ0KDQpPbiAxNy8wOS8yMDIwLCAwMTo0MiwgIk1yLiBKYWVob29uIFBhdWwg
SmVvbmciIDxqYWVob29uLnBhdWxAZ21haWwuY29tPG1haWx0bzpqYWVob29uLnBhdWxAZ21haWwu
Y29tPj4gd3JvdGU6DQoNCkhpIExpbmRhLA0KSSB3aWxsIGFkZHJlc3Mgb3VyIEFEIFJvbWFuJ3Mg
Y29tbWVudHMgb24gdGhpcyBOU0ZzIGNhcGFiaWxpdGllcyBpbmZvcm1hdGlvbiBkcmFmdCBhcyB0
aGUgMm5kIGVkaXRvciB0aHJvdWdoIHRoZSBjb2xsYWJvcmF0aW9uIHdpdGggRnJhbmsgKHRoZSAx
c3QgZWRpdG9yKSBhbmQgdGhlIG90aGVyIGF1dGhvcnMuDQoNCkkgQ0Mgb3VyIEFEIFJvbWFuIGFu
ZCB0aGUgb3RoZXIgYXV0aG9ycywgc3VjaCBhcyBKb2huIGFuZCBDYXRhbGRvLg0KDQoNClRoYW5r
cyBmb3IgeW91ciBzdXBwb3J0IGFuZCBndWlkYW5jZS4NCg0KQmVzdCBSZWdhcmRzLA0KUGF1bA0K
DQoyMDIw64WEIDnsm5QgMTfsnbwgKOuqqSkg7Jik7KCEIDM6NDQsIExpbmRhIER1bmJhciA8bGlu
ZGEuZHVuYmFyQGZ1dHVyZXdlaS5jb208bWFpbHRvOmxpbmRhLmR1bmJhckBmdXR1cmV3ZWkuY29t
Pj7ri5jsnbQg7J6R7ISxOg0KUGF1bCwNCg0KVGhhbmsgeW91IHZlcnkgbXVjaCBmb3Igb2ZmZXJp
bmcgdG8gYWRkcmVzcyB0aGUgQUQgY29tbWVudHMgdG8gdGhpcyBkcmFmdC4gTG9va3MgbGlrZSB0
aGUgY3VycmVudCBhdXRob3JzIGFyZSB0b28gYnVzeSB0byBhZGRyZXNzIHRob3NlIGNvbW1lbnRz
LiBJdCBoYXMgYmVlbiBvdmVyIGEgeWVhciBzaW5jZSB0aGUgQUQgY29tbWVudHMgd2VyZSBnaXZl
bi4gIFdlIG5lZWQgdG8gbW92ZSB0aGUgZHJhZnQgZm9yd2FyZC4gVGhlcmVmb3JlLCBJMk5TRiBj
aGFpcnMgaGF2ZSBhdXRob3JpemVkIHlvdSB0byBiZSBvbmUgb2YgdGhlIGVkaXRvcnMgdG8gYWRk
cmVzcyB0aGUgQUQgY29tbWVudHMgYW5kIHJldmlzZSB0aGUgZHJhZnQuDQoNCg0KVGhhbmsgeW91
IHZlcnkgbXVjaC4NCg0KTGluZGEgJiBZb2F2DQoNCg0KRnJvbTogTXIuIEphZWhvb24gUGF1bCBK
ZW9uZyA8amFlaG9vbi5wYXVsQGdtYWlsLmNvbTxtYWlsdG86amFlaG9vbi5wYXVsQGdtYWlsLmNv
bT4+DQpTZW50OiBTdW5kYXksIFNlcHRlbWJlciAxMywgMjAyMCAxMDowOSBBTQ0KVG86IFhpYWxp
YW5nIChGcmFuaykgPGZyYW5rLnhpYWxpYW5nQGh1YXdlaS5jb208bWFpbHRvOmZyYW5rLnhpYWxp
YW5nQGh1YXdlaS5jb20+Pg0KQ2M6IExpbmRhIER1bmJhciA8bGluZGEuZHVuYmFyQGZ1dHVyZXdl
aS5jb208bWFpbHRvOmxpbmRhLmR1bmJhckBmdXR1cmV3ZWkuY29tPj47IFlvYXYgTmlyIDx5bmly
LmlldGZAZ21haWwuY29tPG1haWx0bzp5bmlyLmlldGZAZ21haWwuY29tPj47IERJRUdPIExPUEVa
IEdBUkNJQSA8ZGllZ28uci5sb3BlekB0ZWxlZm9uaWNhLmNvbTxtYWlsdG86ZGllZ28uci5sb3Bl
ekB0ZWxlZm9uaWNhLmNvbT4+OyBKYWVob29uIEplb25nIDxqYWVob29uLnBhdWxAZ21haWwuY29t
PG1haWx0bzpqYWVob29uLnBhdWxAZ21haWwuY29tPj4NClN1YmplY3Q6IE9mZmVyIGZvciBSZXZp
c2lvbiBIZWxwIGZvciBJMk5TRiBOU0ZzIENhcGFiaWxpdGllcyBJbmZvcm1hdGlvbiBNb2RlbCBE
cmFmdA0KDQpIaSBGcmFuaywNCkNvdWxkIEkgaGVscCB5b3UgdG8gcmV2aXNlIHlvdXIgaW5mb3Jt
YXRpb24gbW9kZWwgZHJhZnQgZm9yIG91ciBBRCBSb21hbiBEYW55bGl3J3MgcmV2aWV3IGNvbW1l
bnRzICBhcyBhIGNvLWVkaXRvcj8NCmh0dHBzOi8vZGF0YXRyYWNrZXIuaWV0Zi5vcmcvZG9jL2Ry
YWZ0LWlldGYtaTJuc2YtY2FwYWJpbGl0eS8/aW5jbHVkZV90ZXh0PTE8aHR0cHM6Ly9uYW0xMS5z
YWZlbGlua3MucHJvdGVjdGlvbi5vdXRsb29rLmNvbS8/dXJsPWh0dHBzJTNBJTJGJTJGZGF0YXRy
YWNrZXIuaWV0Zi5vcmclMkZkb2MlMkZkcmFmdC1pZXRmLWkybnNmLWNhcGFiaWxpdHklMkYlM0Zp
bmNsdWRlX3RleHQlM0QxJmRhdGE9MDIlN0MwMSU3Q2xpbmRhLmR1bmJhciU0MGZ1dHVyZXdlaS5j
b20lN0MwOGE0ODg1OGQ3YmQ0ZDg0M2E2ZTA4ZDg1ZjQ3YjQzOCU3QzBmZWU4ZmYyYTNiMjQwMTg5
Yzc1M2ExZDU1OTFmZWRjJTdDMSU3QzAlN0M2MzczNjQxMDg4NjQ5NTk2MjYmc2RhdGE9R1VyYmFZ
dTJRNE4xWU5VVWV0Mm9WUlBxYnluQTc4Y1NCVGYlMkZCZVNDWTQ0JTNEJnJlc2VydmVkPTA+DQoN
CkFzIHlvdSBrbm93LCBJIGhhdmUgZmluaXNoZWQgb3VyIEkyTlNGIGRhdGEgbW9kZWwgZHJhZnRz
Lg0KDQpJIGFtIGhhcHB5IHRvIHdvcmsgb24gdGhlIHJldmlzaW9uIHdpdGggeW91IGluIG9yZGVy
IHRvIGNvbXBsZXRlIG91ciBJMk5TRiBkZWxpdmVyYWJsZXMuDQoNClRoYW5rcy4NCg0KQmVzdCBS
ZWdhcmRzLA0KUGF1bA0KDQpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KDQpFc3Rl
IG1lbnNhamUgeSBzdXMgYWRqdW50b3Mgc2UgZGlyaWdlbiBleGNsdXNpdmFtZW50ZSBhIHN1IGRl
c3RpbmF0YXJpbywgcHVlZGUgY29udGVuZXIgaW5mb3JtYWNpw7NuIHByaXZpbGVnaWFkYSBvIGNv
bmZpZGVuY2lhbCB5IGVzIHBhcmEgdXNvIGV4Y2x1c2l2byBkZSBsYSBwZXJzb25hIG8gZW50aWRh
ZCBkZSBkZXN0aW5vLiBTaSBubyBlcyB1c3RlZC4gZWwgZGVzdGluYXRhcmlvIGluZGljYWRvLCBx
dWVkYSBub3RpZmljYWRvIGRlIHF1ZSBsYSBsZWN0dXJhLCB1dGlsaXphY2nDs24sIGRpdnVsZ2Fj
acOzbiB5L28gY29waWEgc2luIGF1dG9yaXphY2nDs24gcHVlZGUgZXN0YXIgcHJvaGliaWRhIGVu
IHZpcnR1ZCBkZSBsYSBsZWdpc2xhY2nDs24gdmlnZW50ZS4gU2kgaGEgcmVjaWJpZG8gZXN0ZSBt
ZW5zYWplIHBvciBlcnJvciwgbGUgcm9nYW1vcyBxdWUgbm9zIGxvIGNvbXVuaXF1ZSBpbm1lZGlh
dGFtZW50ZSBwb3IgZXN0YSBtaXNtYSB2w61hIHkgcHJvY2VkYSBhIHN1IGRlc3RydWNjacOzbi4N
Cg0KVGhlIGluZm9ybWF0aW9uIGNvbnRhaW5lZCBpbiB0aGlzIHRyYW5zbWlzc2lvbiBpcyBwcml2
aWxlZ2VkIGFuZCBjb25maWRlbnRpYWwgaW5mb3JtYXRpb24gaW50ZW5kZWQgb25seSBmb3IgdGhl
IHVzZSBvZiB0aGUgaW5kaXZpZHVhbCBvciBlbnRpdHkgbmFtZWQgYWJvdmUuIElmIHRoZSByZWFk
ZXIgb2YgdGhpcyBtZXNzYWdlIGlzIG5vdCB0aGUgaW50ZW5kZWQgcmVjaXBpZW50LCB5b3UgYXJl
IGhlcmVieSBub3RpZmllZCB0aGF0IGFueSBkaXNzZW1pbmF0aW9uLCBkaXN0cmlidXRpb24gb3Ig
Y29weWluZyBvZiB0aGlzIGNvbW11bmljYXRpb24gaXMgc3RyaWN0bHkgcHJvaGliaXRlZC4gSWYg
eW91IGhhdmUgcmVjZWl2ZWQgdGhpcyB0cmFuc21pc3Npb24gaW4gZXJyb3IsIGRvIG5vdCByZWFk
IGl0LiBQbGVhc2UgaW1tZWRpYXRlbHkgcmVwbHkgdG8gdGhlIHNlbmRlciB0aGF0IHlvdSBoYXZl
IHJlY2VpdmVkIHRoaXMgY29tbXVuaWNhdGlvbiBpbiBlcnJvciBhbmQgdGhlbiBkZWxldGUgaXQu
DQoNCkVzdGEgbWVuc2FnZW0gZSBzZXVzIGFuZXhvcyBzZSBkaXJpZ2VtIGV4Y2x1c2l2YW1lbnRl
IGFvIHNldSBkZXN0aW5hdMOhcmlvLCBwb2RlIGNvbnRlciBpbmZvcm1hw6fDo28gcHJpdmlsZWdp
YWRhIG91IGNvbmZpZGVuY2lhbCBlIMOpIHBhcmEgdXNvIGV4Y2x1c2l2byBkYSBwZXNzb2Egb3Ug
ZW50aWRhZGUgZGUgZGVzdGluby4gU2UgbsOjbyDDqSB2b3NzYSBzZW5ob3JpYSBvIGRlc3RpbmF0
w6FyaW8gaW5kaWNhZG8sIGZpY2Egbm90aWZpY2FkbyBkZSBxdWUgYSBsZWl0dXJhLCB1dGlsaXph
w6fDo28sIGRpdnVsZ2HDp8OjbyBlL291IGPDs3BpYSBzZW0gYXV0b3JpemHDp8OjbyBwb2RlIGVz
dGFyIHByb2liaWRhIGVtIHZpcnR1ZGUgZGEgbGVnaXNsYcOnw6NvIHZpZ2VudGUuIFNlIHJlY2Vi
ZXUgZXN0YSBtZW5zYWdlbSBwb3IgZXJybywgcm9nYW1vcy1saGUgcXVlIG5vcyBvIGNvbXVuaXF1
ZSBpbWVkaWF0YW1lbnRlIHBvciBlc3RhIG1lc21hIHZpYSBlIHByb2NlZGEgYSBzdWEgZGVzdHJ1
acOnw6NvDQoNCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQoNCkVzdGUgbWVuc2Fq
ZSB5IHN1cyBhZGp1bnRvcyBzZSBkaXJpZ2VuIGV4Y2x1c2l2YW1lbnRlIGEgc3UgZGVzdGluYXRh
cmlvLCBwdWVkZSBjb250ZW5lciBpbmZvcm1hY2nDs24gcHJpdmlsZWdpYWRhIG8gY29uZmlkZW5j
aWFsIHkgZXMgcGFyYSB1c28gZXhjbHVzaXZvIGRlIGxhIHBlcnNvbmEgbyBlbnRpZGFkIGRlIGRl
c3Rpbm8uIFNpIG5vIGVzIHVzdGVkLiBlbCBkZXN0aW5hdGFyaW8gaW5kaWNhZG8sIHF1ZWRhIG5v
dGlmaWNhZG8gZGUgcXVlIGxhIGxlY3R1cmEsIHV0aWxpemFjacOzbiwgZGl2dWxnYWNpw7NuIHkv
byBjb3BpYSBzaW4gYXV0b3JpemFjacOzbiBwdWVkZSBlc3RhciBwcm9oaWJpZGEgZW4gdmlydHVk
IGRlIGxhIGxlZ2lzbGFjacOzbiB2aWdlbnRlLiBTaSBoYSByZWNpYmlkbyBlc3RlIG1lbnNhamUg
cG9yIGVycm9yLCBsZSByb2dhbW9zIHF1ZSBub3MgbG8gY29tdW5pcXVlIGlubWVkaWF0YW1lbnRl
IHBvciBlc3RhIG1pc21hIHbDrWEgeSBwcm9jZWRhIGEgc3UgZGVzdHJ1Y2Npw7NuLg0KDQpUaGUg
aW5mb3JtYXRpb24gY29udGFpbmVkIGluIHRoaXMgdHJhbnNtaXNzaW9uIGlzIHByaXZpbGVnZWQg
YW5kIGNvbmZpZGVudGlhbCBpbmZvcm1hdGlvbiBpbnRlbmRlZCBvbmx5IGZvciB0aGUgdXNlIG9m
IHRoZSBpbmRpdmlkdWFsIG9yIGVudGl0eSBuYW1lZCBhYm92ZS4gSWYgdGhlIHJlYWRlciBvZiB0
aGlzIG1lc3NhZ2UgaXMgbm90IHRoZSBpbnRlbmRlZCByZWNpcGllbnQsIHlvdSBhcmUgaGVyZWJ5
IG5vdGlmaWVkIHRoYXQgYW55IGRpc3NlbWluYXRpb24sIGRpc3RyaWJ1dGlvbiBvciBjb3B5aW5n
IG9mIHRoaXMgY29tbXVuaWNhdGlvbiBpcyBzdHJpY3RseSBwcm9oaWJpdGVkLiBJZiB5b3UgaGF2
ZSByZWNlaXZlZCB0aGlzIHRyYW5zbWlzc2lvbiBpbiBlcnJvciwgZG8gbm90IHJlYWQgaXQuIFBs
ZWFzZSBpbW1lZGlhdGVseSByZXBseSB0byB0aGUgc2VuZGVyIHRoYXQgeW91IGhhdmUgcmVjZWl2
ZWQgdGhpcyBjb21tdW5pY2F0aW9uIGluIGVycm9yIGFuZCB0aGVuIGRlbGV0ZSBpdC4NCg0KRXN0
YSBtZW5zYWdlbSBlIHNldXMgYW5leG9zIHNlIGRpcmlnZW0gZXhjbHVzaXZhbWVudGUgYW8gc2V1
IGRlc3RpbmF0w6FyaW8sIHBvZGUgY29udGVyIGluZm9ybWHDp8OjbyBwcml2aWxlZ2lhZGEgb3Ug
Y29uZmlkZW5jaWFsIGUgw6kgcGFyYSB1c28gZXhjbHVzaXZvIGRhIHBlc3NvYSBvdSBlbnRpZGFk
ZSBkZSBkZXN0aW5vLiBTZSBuw6NvIMOpIHZvc3NhIHNlbmhvcmlhIG8gZGVzdGluYXTDoXJpbyBp
bmRpY2FkbywgZmljYSBub3RpZmljYWRvIGRlIHF1ZSBhIGxlaXR1cmEsIHV0aWxpemHDp8Ojbywg
ZGl2dWxnYcOnw6NvIGUvb3UgY8OzcGlhIHNlbSBhdXRvcml6YcOnw6NvIHBvZGUgZXN0YXIgcHJv
aWJpZGEgZW0gdmlydHVkZSBkYSBsZWdpc2xhw6fDo28gdmlnZW50ZS4gU2UgcmVjZWJldSBlc3Rh
IG1lbnNhZ2VtIHBvciBlcnJvLCByb2dhbW9zLWxoZSBxdWUgbm9zIG8gY29tdW5pcXVlIGltZWRp
YXRhbWVudGUgcG9yIGVzdGEgbWVzbWEgdmlhIGUgcHJvY2VkYSBhIHN1YSBkZXN0cnVpw6fDo28N
Cg==

--_000_SN6PR13MB23342D6464F8F67CBFE0129C85080SN6PR13MB2334namp_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTUgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPCEtLVtp
ZiAhbXNvXT48c3R5bGU+dlw6KiB7YmVoYXZpb3I6dXJsKCNkZWZhdWx0I1ZNTCk7fQ0Kb1w6KiB7
YmVoYXZpb3I6dXJsKCNkZWZhdWx0I1ZNTCk7fQ0Kd1w6KiB7YmVoYXZpb3I6dXJsKCNkZWZhdWx0
I1ZNTCk7fQ0KLnNoYXBlIHtiZWhhdmlvcjp1cmwoI2RlZmF1bHQjVk1MKTt9DQo8L3N0eWxlPjwh
W2VuZGlmXS0tPjxzdHlsZT48IS0tDQovKiBGb250IERlZmluaXRpb25zICovDQpAZm9udC1mYWNl
DQoJe2ZvbnQtZmFtaWx5OldpbmdkaW5nczsNCglwYW5vc2UtMTo1IDAgMCAwIDAgMCAwIDAgMCAw
O30NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6IkNhbWJyaWEgTWF0aCI7DQoJcGFub3NlLTE6
MiA0IDUgMyA1IDQgNiAzIDIgNDt9DQpAZm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5OkRlbmdYaWFu
Ow0KCXBhbm9zZS0xOjIgMSA2IDAgMyAxIDEgMSAxIDE7fQ0KQGZvbnQtZmFjZQ0KCXtmb250LWZh
bWlseTpDYWxpYnJpOw0KCXBhbm9zZS0xOjIgMTUgNSAyIDIgMiA0IDMgMiA0O30NCkBmb250LWZh
Y2UNCgl7Zm9udC1mYW1pbHk6IlxARGVuZ1hpYW4iOw0KCXBhbm9zZS0xOjIgMSA2IDAgMyAxIDEg
MSAxIDE7fQ0KQGZvbnQtZmFjZQ0KCXtmb250LWZhbWlseTpDb25zb2xhczsNCglwYW5vc2UtMToy
IDExIDYgOSAyIDIgNCAzIDIgNDt9DQpAZm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5OiJNYWxndW4g
R290aGljIjsNCglwYW5vc2UtMToyIDExIDUgMyAyIDAgMCAyIDAgNDt9DQpAZm9udC1mYWNlDQoJ
e2ZvbnQtZmFtaWx5OiJcQE1hbGd1biBHb3RoaWMiO30NCi8qIFN0eWxlIERlZmluaXRpb25zICov
DQpwLk1zb05vcm1hbCwgbGkuTXNvTm9ybWFsLCBkaXYuTXNvTm9ybWFsDQoJe21hcmdpbjowaW47
DQoJbWFyZ2luLWJvdHRvbTouMDAwMXB0Ow0KCWZvbnQtc2l6ZToxMS4wcHQ7DQoJZm9udC1mYW1p
bHk6IkNhbGlicmkiLHNhbnMtc2VyaWY7fQ0KYTpsaW5rLCBzcGFuLk1zb0h5cGVybGluaw0KCXtt
c28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJY29sb3I6Ymx1ZTsNCgl0ZXh0LWRlY29yYXRpb246dW5k
ZXJsaW5lO30NCnByZQ0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJbXNvLXN0eWxlLWxpbms6
IkhUTUwgUHJlZm9ybWF0dGVkIENoYXIiOw0KCW1hcmdpbjowaW47DQoJbWFyZ2luLWJvdHRvbTou
MDAwMXB0Ow0KCWZvbnQtc2l6ZToxMC4wcHQ7DQoJZm9udC1mYW1pbHk6IkNvdXJpZXIgTmV3Ijt9
DQpwLk1zb0xpc3RQYXJhZ3JhcGgsIGxpLk1zb0xpc3RQYXJhZ3JhcGgsIGRpdi5Nc29MaXN0UGFy
YWdyYXBoDQoJe21zby1zdHlsZS1wcmlvcml0eTozNDsNCgltYXJnaW4tdG9wOjBpbjsNCgltYXJn
aW4tcmlnaHQ6MGluOw0KCW1hcmdpbi1ib3R0b206MGluOw0KCW1hcmdpbi1sZWZ0Oi41aW47DQoJ
bWFyZ2luLWJvdHRvbTouMDAwMXB0Ow0KCWZvbnQtc2l6ZToxMS4wcHQ7DQoJZm9udC1mYW1pbHk6
IkNhbGlicmkiLHNhbnMtc2VyaWY7fQ0Kc3Bhbi5IVE1MUHJlZm9ybWF0dGVkQ2hhcg0KCXttc28t
c3R5bGUtbmFtZToiSFRNTCBQcmVmb3JtYXR0ZWQgQ2hhciI7DQoJbXNvLXN0eWxlLXByaW9yaXR5
Ojk5Ow0KCW1zby1zdHlsZS1saW5rOiJIVE1MIFByZWZvcm1hdHRlZCI7DQoJZm9udC1mYW1pbHk6
Q29uc29sYXM7fQ0Kc3Bhbi5FbWFpbFN0eWxlMjENCgl7bXNvLXN0eWxlLXR5cGU6cGVyc29uYWw7
DQoJZm9udC1mYW1pbHk6IkNhbGlicmkiLHNhbnMtc2VyaWY7DQoJY29sb3I6d2luZG93dGV4dDt9
DQpzcGFuLkVtYWlsU3R5bGUyNA0KCXttc28tc3R5bGUtdHlwZTpwZXJzb25hbC1yZXBseTsNCglm
b250LWZhbWlseToiQ2FsaWJyaSIsc2Fucy1zZXJpZjsNCgljb2xvcjp3aW5kb3d0ZXh0O30NCi5N
c29DaHBEZWZhdWx0DQoJe21zby1zdHlsZS10eXBlOmV4cG9ydC1vbmx5Ow0KCWZvbnQtc2l6ZTox
MC4wcHQ7fQ0KQHBhZ2UgV29yZFNlY3Rpb24xDQoJe3NpemU6OC41aW4gMTEuMGluOw0KCW1hcmdp
bjoxLjBpbiAxLjBpbiAxLjBpbiAxLjBpbjt9DQpkaXYuV29yZFNlY3Rpb24xDQoJe3BhZ2U6V29y
ZFNlY3Rpb24xO30NCi8qIExpc3QgRGVmaW5pdGlvbnMgKi8NCkBsaXN0IGwwDQoJe21zby1saXN0
LWlkOjg5MTU3NTU3ODsNCgltc28tbGlzdC10eXBlOmh5YnJpZDsNCgltc28tbGlzdC10ZW1wbGF0
ZS1pZHM6NTcxNDkxODc0IC0xOTE5Nzc5MDQ4IDY3Njk4NjkxIDY3Njk4NjkzIDY3Njk4Njg5IDY3
Njk4NjkxIDY3Njk4NjkzIDY3Njk4Njg5IDY3Njk4NjkxIDY3Njk4NjkzO30NCkBsaXN0IGwwOmxl
dmVsMQ0KCXttc28tbGV2ZWwtc3RhcnQtYXQ6MDsNCgltc28tbGV2ZWwtbnVtYmVyLWZvcm1hdDpi
dWxsZXQ7DQoJbXNvLWxldmVsLXRleHQ6LTsNCgltc28tbGV2ZWwtdGFiLXN0b3A6bm9uZTsNCglt
c28tbGV2ZWwtbnVtYmVyLXBvc2l0aW9uOmxlZnQ7DQoJdGV4dC1pbmRlbnQ6LS4yNWluOw0KCWZv
bnQtZmFtaWx5OiJDYWxpYnJpIixzYW5zLXNlcmlmOw0KCW1zby1mYXJlYXN0LWZvbnQtZmFtaWx5
OkRlbmdYaWFuO30NCkBsaXN0IGwwOmxldmVsMg0KCXttc28tbGV2ZWwtbnVtYmVyLWZvcm1hdDpi
dWxsZXQ7DQoJbXNvLWxldmVsLXRleHQ6bzsNCgltc28tbGV2ZWwtdGFiLXN0b3A6bm9uZTsNCglt
c28tbGV2ZWwtbnVtYmVyLXBvc2l0aW9uOmxlZnQ7DQoJdGV4dC1pbmRlbnQ6LS4yNWluOw0KCWZv
bnQtZmFtaWx5OiJDb3VyaWVyIE5ldyI7fQ0KQGxpc3QgbDA6bGV2ZWwzDQoJe21zby1sZXZlbC1u
dW1iZXItZm9ybWF0OmJ1bGxldDsNCgltc28tbGV2ZWwtdGV4dDrvgqc7DQoJbXNvLWxldmVsLXRh
Yi1zdG9wOm5vbmU7DQoJbXNvLWxldmVsLW51bWJlci1wb3NpdGlvbjpsZWZ0Ow0KCXRleHQtaW5k
ZW50Oi0uMjVpbjsNCglmb250LWZhbWlseTpXaW5nZGluZ3M7fQ0KQGxpc3QgbDA6bGV2ZWw0DQoJ
e21zby1sZXZlbC1udW1iZXItZm9ybWF0OmJ1bGxldDsNCgltc28tbGV2ZWwtdGV4dDrvgrc7DQoJ
bXNvLWxldmVsLXRhYi1zdG9wOm5vbmU7DQoJbXNvLWxldmVsLW51bWJlci1wb3NpdGlvbjpsZWZ0
Ow0KCXRleHQtaW5kZW50Oi0uMjVpbjsNCglmb250LWZhbWlseTpTeW1ib2w7fQ0KQGxpc3QgbDA6
bGV2ZWw1DQoJe21zby1sZXZlbC1udW1iZXItZm9ybWF0OmJ1bGxldDsNCgltc28tbGV2ZWwtdGV4
dDpvOw0KCW1zby1sZXZlbC10YWItc3RvcDpub25lOw0KCW1zby1sZXZlbC1udW1iZXItcG9zaXRp
b246bGVmdDsNCgl0ZXh0LWluZGVudDotLjI1aW47DQoJZm9udC1mYW1pbHk6IkNvdXJpZXIgTmV3
Ijt9DQpAbGlzdCBsMDpsZXZlbDYNCgl7bXNvLWxldmVsLW51bWJlci1mb3JtYXQ6YnVsbGV0Ow0K
CW1zby1sZXZlbC10ZXh0Ou+CpzsNCgltc28tbGV2ZWwtdGFiLXN0b3A6bm9uZTsNCgltc28tbGV2
ZWwtbnVtYmVyLXBvc2l0aW9uOmxlZnQ7DQoJdGV4dC1pbmRlbnQ6LS4yNWluOw0KCWZvbnQtZmFt
aWx5OldpbmdkaW5nczt9DQpAbGlzdCBsMDpsZXZlbDcNCgl7bXNvLWxldmVsLW51bWJlci1mb3Jt
YXQ6YnVsbGV0Ow0KCW1zby1sZXZlbC10ZXh0Ou+CtzsNCgltc28tbGV2ZWwtdGFiLXN0b3A6bm9u
ZTsNCgltc28tbGV2ZWwtbnVtYmVyLXBvc2l0aW9uOmxlZnQ7DQoJdGV4dC1pbmRlbnQ6LS4yNWlu
Ow0KCWZvbnQtZmFtaWx5OlN5bWJvbDt9DQpAbGlzdCBsMDpsZXZlbDgNCgl7bXNvLWxldmVsLW51
bWJlci1mb3JtYXQ6YnVsbGV0Ow0KCW1zby1sZXZlbC10ZXh0Om87DQoJbXNvLWxldmVsLXRhYi1z
dG9wOm5vbmU7DQoJbXNvLWxldmVsLW51bWJlci1wb3NpdGlvbjpsZWZ0Ow0KCXRleHQtaW5kZW50
Oi0uMjVpbjsNCglmb250LWZhbWlseToiQ291cmllciBOZXciO30NCkBsaXN0IGwwOmxldmVsOQ0K
CXttc28tbGV2ZWwtbnVtYmVyLWZvcm1hdDpidWxsZXQ7DQoJbXNvLWxldmVsLXRleHQ674KnOw0K
CW1zby1sZXZlbC10YWItc3RvcDpub25lOw0KCW1zby1sZXZlbC1udW1iZXItcG9zaXRpb246bGVm
dDsNCgl0ZXh0LWluZGVudDotLjI1aW47DQoJZm9udC1mYW1pbHk6V2luZ2RpbmdzO30NCm9sDQoJ
e21hcmdpbi1ib3R0b206MGluO30NCnVsDQoJe21hcmdpbi1ib3R0b206MGluO30NCi0tPjwvc3R5
bGU+PCEtLVtpZiBndGUgbXNvIDldPjx4bWw+DQo8bzpzaGFwZWRlZmF1bHRzIHY6ZXh0PSJlZGl0
IiBzcGlkbWF4PSIxMDI2IiAvPg0KPC94bWw+PCFbZW5kaWZdLS0+PCEtLVtpZiBndGUgbXNvIDld
Pjx4bWw+DQo8bzpzaGFwZWxheW91dCB2OmV4dD0iZWRpdCI+DQo8bzppZG1hcCB2OmV4dD0iZWRp
dCIgZGF0YT0iMSIgLz4NCjwvbzpzaGFwZWxheW91dD48L3htbD48IVtlbmRpZl0tLT4NCjwvaGVh
ZD4NCjxib2R5IGxhbmc9IkVOLVVTIiBsaW5rPSJibHVlIiB2bGluaz0icHVycGxlIj4NCjxkaXYg
Y2xhc3M9IldvcmRTZWN0aW9uMSI+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5JMk5TRiBXRywgPG86
cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiPkNvcnJlY3Rpb246IDxvOnA+PC9vOnA+PC9wPg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij5UaGVyZSBoYXMgYmVlbiBOTyBvYmplY3QgdG8gdGhlIEF1dGhvcuKAmXMgcmVxdWVzdCBmb3Ig
c3Vuc2V0dGluZyB0aGUgZHJhZnQtaWV0Zi1pMm5zZi1jYXBhYmlsaXR5LTUuDQo8bzpwPjwvbzpw
PjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCI+V2UgaGF2ZSBtYXJrZWQgdGhlIGRyYWZ0IGFzIOKAnERFQUTigJ0gaW4g
dGhlIFdHIHN0YXR1cy4gPG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpw
PiZuYnNwOzwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPk1hbnkgdGhhbmtzIHRvIHRo
ZSBhdXRob3JzIGZvciBwdXR0aW5nIHRoZSBlZmZvcnQgaW4gdGhpcyBkcmFmdCBmb3Iga2lja3N0
YXJ0aW5nIGFsbCB0aGUgZGF0YSBtb2RlbHMgaW4gSTJOU0YgV0cuDQo8bzpwPjwvbzpwPjwvcD4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1z
b05vcm1hbCI+TGluZGEgJmFtcDsgWW9hdjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8ZGl2Pg0KPGRpdiBzdHlsZT0iYm9yZGVyOm5v
bmU7Ym9yZGVyLXRvcDpzb2xpZCAjRTFFMUUxIDEuMHB0O3BhZGRpbmc6My4wcHQgMGluIDBpbiAw
aW4iPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PGI+RnJvbTo8L2I+IExpbmRhIER1bmJhciA8YnI+
DQo8Yj5TZW50OjwvYj4gVGh1cnNkYXksIE9jdG9iZXIgOCwgMjAyMCA0OjM2IFBNPGJyPg0KPGI+
VG86PC9iPiBpMm5zZkBpZXRmLm9yZzxicj4NCjxiPlN1YmplY3Q6PC9iPiBkcmFmdC1pZXRmLWky
bnNmLWNhcGFiaWxpdHktMDUgaXMgb2ZmaWNpYWxseSByZW1vdmVkIGZyb20gSTJOU0YgV0cgKCB3
YXMgUkU6IElzIHRoZXJlIGFueSBvYmplY3Rpb24gb2Ygc3Vuc2V0IHRoZSBJMk5TRiBDYXBhYmls
aXRpZXMgSW5mb3JtYXRpb24gTW9kZWwgRHJhZnQgYW5kIG1lcmdlIHRoZSByZWxldmFudCBpbmZv
cm1hdGlvbiB0byB0aGUgSTJOU0YgQ2FwYWJpbGl0eSBEYXRhIG1vZGVsIGRyYWZ0Pw0KPG86cD48
L286cD48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJz
cDs8L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5JMm5zZiBXRywgPG86cD48L286cD48
L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiPlRoZXJlIGhhcyBiZWVuIGFueSBvYmplY3Rpb24gdG8gdGhlIEF1dGhvcuKA
mXMgcmVxdWVzdCBmb3Igc3Vuc2V0dGluZyB0aGUgJm5ic3A7ZHJhZnQtaWV0Zi1pMm5zZi1jYXBh
YmlsaXR5LTA1Lg0KPG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZu
YnNwOzwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPkF1dGhvcnMgb2YgdGhlIGRyYWZ0
LWlldGYtaTJuc2YtY2FwYWJpbGl0eS1kYXRhLW1vZGVsOiBwbGVhc2UgcmVtb3ZlIHRoZSByZWZl
cmVuY2UgdG8gdGhlIENhcGFiaWxpdHkgSW5mb3JtYXRpb24gTW9kZWwgYW5kIHVwbG9hZCBhIG5l
dyBkcmFmdC4gV2UgY2FuIGFzayBJRVNHIHRvIHJlLXJldmlldyBpdC4NCjxvOnA+PC9vOnA+PC9w
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIj5UaGFuayB5b3UgdmVyeSBtdWNoLiA8bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+
TGluZGEgJmFtcDsgWW9hdi4gPG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48
bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxkaXY+DQo8ZGl2IHN0eWxlPSJib3JkZXI6bm9uZTtib3Jk
ZXItdG9wOnNvbGlkICNFMUUxRTEgMS4wcHQ7cGFkZGluZzozLjBwdCAwaW4gMGluIDBpbiI+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIj48Yj5Gcm9tOjwvYj4gTGluZGEgRHVuYmFyIDxicj4NCjxiPlNl
bnQ6PC9iPiBNb25kYXksIFNlcHRlbWJlciAyOCwgMjAyMCAxMTowMCBBTTxicj4NCjxiPlRvOjwv
Yj4gPGEgaHJlZj0ibWFpbHRvOmkybnNmQGlldGYub3JnIj5pMm5zZkBpZXRmLm9yZzwvYT48YnI+
DQo8Yj5TdWJqZWN0OjwvYj4gSXMgdGhlcmUgYW55IG9iamVjdGlvbiBvZiBzdW5zZXQgdGhlIEky
TlNGIENhcGFiaWxpdGllcyBJbmZvcm1hdGlvbiBNb2RlbCBEcmFmdCBhbmQgbWVyZ2UgdGhlIHJl
bGV2YW50IGluZm9ybWF0aW9uIHRvIHRoZSBJMk5TRiBDYXBhYmlsaXR5IERhdGEgbW9kZWwgZHJh
ZnQ/DQo8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPkkyTlNGIFdHLCA8
bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9w
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+QXMgRGllZ28gaGFzIGV4cHJlc3NlZCB0aGF0IHRoZSBv
cmlnaW5hbCBJMk5TRiBjYXBhYmlsaXR5IGluZm9ybWF0aW9uIG1vZGVsIHdhcyBiYXNlZCBvbiBh
IHBvbGljeSBleHByZXNzaW9uIGNhbGN1bHVzIHN1aXRhYmxlIGZvciBtYW5pcHVsYXRpbmcgaGln
aC1sZXZlbCBwb2xpY3kgZXhwcmVzc2lvbnMuJm5ic3A7IFRoZSBjYXBhYmlsaXR5IGRhdGEgbW9k
ZWwgaGFzIGJlZW4gZXZvbHZpbmcgaW4gYSBxdWl0ZSByZWFzb25hYmxlDQogYW5kIHByYWdtYXRp
YyB3YXksIGluY2x1ZGluZyBydW5uaW5nIGNvZGUgYXQgdGhlIGhhY2thdGhvbnMuPG86cD48L286
cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiPlRoZSBJMk5TRiBDYXBhYmlsaXR5IEluZm9ybWF0aW9uIE1vZGVsIGhh
cyBmdWxmaWxsZWQgaXRzIHB1cnBvc2Ugb2Yga2lja3N0YXJ0aW5nIGFuZCBndWlkaW5nIHRoZSBk
YXRhIG1vZGVsLCBhbmQgdGhlIGF1dGhvcnMgYmVsaWV2ZSB0aGF0IGl0IGlzIGJldHRlciB0byBs
ZXQgdGhlIGNhcGFiaWxpdHkgaW5mb3JtYXRpb24gbW9kZWwgdG8gYmUgd2l0aGRyYXduLiBGb3Ig
dGhlIGNvbnRlbnQgaW4gdGhlIGluZm9ybWF0aW9uDQogbW9kZWwgc3RpbGwgcmVsZXZhbnQgdG8g
STJOU0YgQ2FwYWJpbGl0eSBEYXRhIE1vZGVsLCB0aGV5IHNob3VsZCBiZSBtZXJnZWQgaW50byB0
aGUgQ2FwYWJpbGl0eSBEYXRhIE1vZGVsLg0KPG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPklzIHRo
ZXJlIGFueSBvYmplY3Rpb24gZnJvbSB0aGUgV0c/ICZuYnNwO0lmIHdlIGRvbuKAmXQgaGVhciBh
bnkgb2JqZWN0aW9uIGJ5IE9jdCA1LCB3ZSB3aWxsIGNoYW5nZSB0aGUgc3RhdHVzIG9mIHRoZSBk
cmFmdC4NCjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8
L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5DaGVlcnMsICZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOw0KPG86cD48L286cD48L3A+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29O
b3JtYWwiPkxpbmRhICZhbXA7IFlvYXY8bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3Jt
YWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJz
cDs8L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4N
CjxkaXY+DQo8ZGl2IHN0eWxlPSJib3JkZXI6bm9uZTtib3JkZXItdG9wOnNvbGlkICNFMUUxRTEg
MS4wcHQ7cGFkZGluZzozLjBwdCAwaW4gMGluIDBpbiI+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48
Yj5Gcm9tOjwvYj4gRGllZ28gUi4gTG9wZXogJmx0OzxhIGhyZWY9Im1haWx0bzpkaWVnby5yLmxv
cGV6QHRlbGVmb25pY2EuY29tIj5kaWVnby5yLmxvcGV6QHRlbGVmb25pY2EuY29tPC9hPiZndDsN
Cjxicj4NCjxiPlNlbnQ6PC9iPiBUdWVzZGF5LCBTZXB0ZW1iZXIgMjIsIDIwMjAgNTozNSBQTTxi
cj4NCjxiPlRvOjwvYj4gTGluZGEgRHVuYmFyICZsdDs8YSBocmVmPSJtYWlsdG86bGluZGEuZHVu
YmFyQGZ1dHVyZXdlaS5jb20iPmxpbmRhLmR1bmJhckBmdXR1cmV3ZWkuY29tPC9hPiZndDs7IE1y
LiBKYWVob29uIFBhdWwgSmVvbmcgJmx0OzxhIGhyZWY9Im1haWx0bzpqYWVob29uLnBhdWxAZ21h
aWwuY29tIj5qYWVob29uLnBhdWxAZ21haWwuY29tPC9hPiZndDs8YnI+DQo8Yj5DYzo8L2I+IFhp
YWxpYW5nIChGcmFuaykgJmx0OzxhIGhyZWY9Im1haWx0bzpmcmFuay54aWFsaWFuZ0BodWF3ZWku
Y29tIj5mcmFuay54aWFsaWFuZ0BodWF3ZWkuY29tPC9hPiZndDs7IFlvYXYgTmlyICZsdDs8YSBo
cmVmPSJtYWlsdG86eW5pci5pZXRmQGdtYWlsLmNvbSI+eW5pci5pZXRmQGdtYWlsLmNvbTwvYT4m
Z3Q7OyBKb2huIFN0cmFzc25lciAmbHQ7PGEgaHJlZj0ibWFpbHRvOkpvaG4uc2MuU3RyYXNzbmVy
QGh1YXdlaS5jb20iPkpvaG4uc2MuU3RyYXNzbmVyQGh1YXdlaS5jb208L2E+Jmd0OzsNCiBBbGRv
IEJhc2lsZSAmbHQ7PGEgaHJlZj0ibWFpbHRvOmNhdGFsZG8uYmFzaWxlQHBvbGl0by5pdCI+Y2F0
YWxkby5iYXNpbGVAcG9saXRvLml0PC9hPiZndDs7IFJvbWFuIERhbnlsaXcgJmx0OzxhIGhyZWY9
Im1haWx0bzpyZGRAY2VydC5vcmciPnJkZEBjZXJ0Lm9yZzwvYT4mZ3Q7PGJyPg0KPGI+U3ViamVj
dDo8L2I+IFJlOiBPZmZlciBmb3IgUmV2aXNpb24gSGVscCBmb3IgSTJOU0YgTlNGcyBDYXBhYmls
aXRpZXMgSW5mb3JtYXRpb24gTW9kZWwgRHJhZnQ8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPC9k
aXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDttc28t
ZmFyZWFzdC1sYW5ndWFnZTpFTi1VUyI+SGkgTGluZGEsPG86cD48L286cD48L3NwYW4+PC9wPg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRVMiIHN0eWxlPSJmb250LXNpemU6MTAu
MHB0O21zby1mYXJlYXN0LWxhbmd1YWdlOkVOLVVTIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48
L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtt
c28tZmFyZWFzdC1sYW5ndWFnZTpFTi1VUyI+SeKAmWQgcHJlZmVyIHRoZSBzZWNvbmQgb3B0aW9u
LCBhcyBpdCBzZWVtcyBtb3JlIHN0cmFpZ2h0Zm9yd2FyZCBhbmQgbmF0dXJhbCB0byBtZSwgYW5k
IGluIHBhcmFsbGVsIHdvdWxkIGxpa2UgeW91IHRvIGNvbnNpZGVyIHRoZSBpZGVhIG9mIGFuIEky
TlNGIGV4dGVuc2lvbiBhbGxvd2luZyB1cyB0byByZXVzZSB0aGUNCiBjYXBhYmlsaXR5IG1vZGVs
IGZvciBwb2xpY3ktY29udHJvbCB0cmFuc2Zvcm1hdGlvbiwgYW5kIHRvIGluY29ycG9yYXRlIHRo
ZSBhdHRlc3RhdGlvbiBtYXR0ZXJzIHlvdSBrbm93IEkgd2FzIHNvIG11Y2ggaW50ZXJlc3RlZCBp
bi48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHls
ZT0iZm9udC1zaXplOjEwLjBwdDttc28tZmFyZWFzdC1sYW5ndWFnZTpFTi1VUyI+PG86cD4mbmJz
cDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZv
bnQtc2l6ZToxMC4wcHQ7bXNvLWZhcmVhc3QtbGFuZ3VhZ2U6RU4tVVMiPkJlIGdvb2RlLDxvOnA+
PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250
LXNpemU6MTAuMHB0O21zby1mYXJlYXN0LWxhbmd1YWdlOkVOLVVTIj48bzpwPiZuYnNwOzwvbzpw
Pjwvc3Bhbj48L3A+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRVMi
IHN0eWxlPSJmb250LXNpemU6MTAuMHB0O21zby1mYXJlYXN0LWxhbmd1YWdlOkVOLVVTIj4tLTxv
OnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVT
IiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDttc28tZmFyZWFzdC1sYW5ndWFnZTpFTi1VUyI+JnF1
b3Q7RXN0YSB2ZXogbm8gZmFsbGFyZW1vcywgRG9jdG9yIEluZmllcm5vJnF1b3Q7PG86cD48L286
cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRVMiIHN0eWxl
PSJmb250LXNpemU6MTAuMHB0O21zby1mYXJlYXN0LWxhbmd1YWdlOkVOLVVTIj4mbmJzcDs8bzpw
PjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFUyIg
c3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7bXNvLWZhcmVhc3QtbGFuZ3VhZ2U6RU4tVVMiPkRyIERp
ZWdvIFIuIExvcGV6PG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+
PHNwYW4gbGFuZz0iRVMiIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O21zby1mYXJlYXN0LWxhbmd1
YWdlOkVOLVVTIj5UZWxlZm9uaWNhIEkrRDxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDttc28t
ZmFyZWFzdC1sYW5ndWFnZTpFTi1VUyI+PGEgaHJlZj0iaHR0cHM6Ly9uYW0xMS5zYWZlbGlua3Mu
cHJvdGVjdGlvbi5vdXRsb29rLmNvbS8/dXJsPWh0dHBzJTNBJTJGJTJGd3d3LmxpbmtlZGluLmNv
bSUyRmluJTJGZHIybG9wZXolMkYmYW1wO2RhdGE9MDIlN0MwMSU3Q2xpbmRhLmR1bmJhciU0MGZ1
dHVyZXdlaS5jb20lN0MwOGE0ODg1OGQ3YmQ0ZDg0M2E2ZTA4ZDg1ZjQ3YjQzOCU3QzBmZWU4ZmYy
YTNiMjQwMTg5Yzc1M2ExZDU1OTFmZWRjJTdDMSU3QzAlN0M2MzczNjQxMDg4NjQ5NDk2MzMmYW1w
O3NkYXRhPVJPUjQlMkZ5RDFXcVdEYjFyQ2JKeDNFUnFUaU1DUTkyaWJreXoyNmtZWmREOCUzRCZh
bXA7cmVzZXJ2ZWQ9MCI+PHNwYW4gc3R5bGU9ImNvbG9yOiMwNTYzQzEiPmh0dHBzOi8vd3d3Lmxp
bmtlZGluLmNvbS9pbi9kcjJsb3Blei88L3NwYW4+PC9hPiZuYnNwOzxvOnA+PC9vOnA+PC9zcGFu
PjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVTIiBzdHlsZT0iZm9udC1z
aXplOjEwLjBwdDttc28tZmFyZWFzdC1sYW5ndWFnZTpFTi1VUyI+Jm5ic3A7PG86cD48L286cD48
L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRVMiIHN0eWxlPSJm
b250LXNpemU6MTAuMHB0O21zby1mYXJlYXN0LWxhbmd1YWdlOkVOLVVTIj5lLW1haWw6Jm5ic3A7
PC9zcGFuPjxzcGFuIGxhbmc9IkVOLUdCIiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDttc28tZmFy
ZWFzdC1sYW5ndWFnZTpFTi1VUyI+PGEgaHJlZj0ibWFpbHRvOmRpZWdvLnIubG9wZXpAdGVsZWZv
bmljYS5jb20iPjxzcGFuIGxhbmc9IkVTIiBzdHlsZT0iY29sb3I6IzA1NjNDMSI+ZGllZ28uci5s
b3BlekB0ZWxlZm9uaWNhLmNvbTwvc3Bhbj48L2E+PC9zcGFuPjxzcGFuIGxhbmc9IkVTIiBzdHls
ZT0iZm9udC1zaXplOjEwLjBwdDttc28tZmFyZWFzdC1sYW5ndWFnZTpFTi1VUyI+PG86cD48L286
cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tR0IiIHN0
eWxlPSJmb250LXNpemU6MTAuMHB0O21zby1mYXJlYXN0LWxhbmd1YWdlOkVOLVVTIj5UZWw6Jm5i
c3A7Jm5ic3A7Jm5ic3A7ICZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyArMzQgOTEzIDEyOSAwNDE8
bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJF
Ti1HQiIgc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7bXNvLWZhcmVhc3QtbGFuZ3VhZ2U6RU4tVVMi
Pk1vYmlsZTogJm5ic3A7KzM0IDY4MiAwNTEgMDkxPG86cD48L286cD48L3NwYW4+PC9wPg0KPC9k
aXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1HQiIgc3R5bGU9ImZvbnQt
c2l6ZToxMC4wcHQ7bXNvLWZhcmVhc3QtbGFuZ3VhZ2U6RU4tVVMiPi0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS08L3NwYW4+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7bXNv
LWZhcmVhc3QtbGFuZ3VhZ2U6RU4tVVMiPjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O21zby1mYXJlYXN0LWxh
bmd1YWdlOkVOLVVTIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8ZGl2Pg0KPGRpdj4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJnaW4tbGVmdDouNWluIj5PbiAyMi8wOS8y
MDIwLCAxODowMSwgJnF1b3Q7TGluZGEgRHVuYmFyJnF1b3Q7ICZsdDs8YSBocmVmPSJtYWlsdG86
bGluZGEuZHVuYmFyQGZ1dHVyZXdlaS5jb20iPmxpbmRhLmR1bmJhckBmdXR1cmV3ZWkuY29tPC9h
PiZndDsgd3JvdGU6PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJnaW4tbGVmdDouNWluIj48bzpwPiZuYnNwOzwvbzpw
PjwvcD4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1hcmdpbi1sZWZ0Oi41
aW4iPkRpZWdvOiA8bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJt
YXJnaW4tbGVmdDouNWluIj4mbmJzcDs8bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3Jt
YWwiIHN0eWxlPSJtYXJnaW4tbGVmdDouNWluIj5UaGFuayB5b3UgdmVyeSBtdWNoIGZvciB0aGUg
cmVmbGVjdGlvbiBvZiB0aGUgQ2FwYWJpbGl0aWVzIEluZm9ybWF0aW9uIE1vZGVsIERyYWZ0LiBB
Z3JlZSB3aXRoIHlvdXIgc3RhdGVtZW50IHRoYXQg4oCcdGhlIGNhcGFiaWxpdHkgZGF0YSBtb2Rl
bCB3YXMgZXZvbHZpbmcgaW4gYSBxdWl0ZSByZWFzb25hYmxlIGFuZCBwcmFnbWF0aWMgd2F5LCBp
bmNsdWRpbmcgcnVubmluZw0KIGNvZGUgYXQgdGhlIGhhY2thdGhvbnPigJ0uIDxvOnA+PC9vOnA+
PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1hcmdpbi1sZWZ0Oi41aW4iPiZuYnNw
OzxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1hcmdpbi1sZWZ0
Oi41aW4iPkxvb2tzIGxpa2UgRXJpYyBWeW5ja2Ugc3RpbGwgd2FudHMgdGhlIGluZm9ybWF0aW9u
IG1vZGVsIHRvIGJlIGZpeGVkIHRvIGNsZWFyIGhpcyDigJxESVNDVVNT4oCdIGJhbGxvdC4NCjxv
OnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1hcmdpbi1sZWZ0Oi41
aW4iPkhvdyBhYm91dCB0aGUgZm9sbG93aW5nIHN0ZXBzOjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xh
c3M9Ik1zb0xpc3RQYXJhZ3JhcGgiIHN0eWxlPSJtYXJnaW4tbGVmdDoxLjBpbjt0ZXh0LWluZGVu
dDotLjI1aW47bXNvLWxpc3Q6bDAgbGV2ZWwxIGxmbzIiPg0KPCFbaWYgIXN1cHBvcnRMaXN0c10+
PHNwYW4gc3R5bGU9Im1zby1saXN0Oklnbm9yZSI+LTxzcGFuIHN0eWxlPSJmb250OjcuMHB0ICZx
dW90O1RpbWVzIE5ldyBSb21hbiZxdW90OyI+Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7
Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7DQo8L3NwYW4+PC9zcGFuPjwhW2VuZGlmXT5Bc2sgUm9t
YW7igJlzIGFkdmljZSBpZiB3ZSBjYW4gc2ltcGxpZnkgdGhlIEluZm9ybWF0aW9uIE1vZGVsIG1h
aW5seSB0byByZWZsZWN0IHdoYXQgaGFzIGJlZW4gaW4gdGhlIERhdGEgTW9kZWwuPG86cD48L286
cD48L3A+DQo8cCBjbGFzcz0iTXNvTGlzdFBhcmFncmFwaCIgc3R5bGU9Im1hcmdpbi1sZWZ0OjEu
MGluO3RleHQtaW5kZW50Oi0uMjVpbjttc28tbGlzdDpsMCBsZXZlbDEgbGZvMiI+DQo8IVtpZiAh
c3VwcG9ydExpc3RzXT48c3BhbiBzdHlsZT0ibXNvLWxpc3Q6SWdub3JlIj4tPHNwYW4gc3R5bGU9
ImZvbnQ6Ny4wcHQgJnF1b3Q7VGltZXMgTmV3IFJvbWFuJnF1b3Q7Ij4mbmJzcDsmbmJzcDsmbmJz
cDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsNCjwvc3Bhbj48L3NwYW4+PCFb
ZW5kaWZdPk9yLCBkcm9wIHRoZSBJbmZvcm1hdGlvbiBtb2RlbCBkcmFmdCBhbmQgcmVtb3ZlIHRo
ZSByZWZlbmNlIHRvIHRoZSBkcmFmdCwgYnV0IFJvbWFuIGhhcyB0byBjb252aW5jZSBFcmljIHRv
IGFncmVlIG5vdCBoYXZpbmcgdGhlIGluZm9ybWF0aW9uIG1vZGVsLg0KPG86cD48L286cD48L3A+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibWFyZ2luLWxlZnQ6LjVpbiI+Jm5ic3A7PG86
cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibWFyZ2luLWxlZnQ6LjVp
biI+V2hhdCBkbyB5b3UgdGhpbms/IDxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1h
bCIgc3R5bGU9Im1hcmdpbi1sZWZ0Oi41aW4iPiZuYnNwOzxvOnA+PC9vOnA+PC9wPg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1hcmdpbi1sZWZ0Oi41aW4iPkxpbmRhPG86cD48L286cD48
L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibWFyZ2luLWxlZnQ6LjVpbiI+Jm5ic3A7
PG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibWFyZ2luLWxlZnQ6
LjVpbiI+Jm5ic3A7PG86cD48L286cD48L3A+DQo8ZGl2Pg0KPGRpdiBzdHlsZT0iYm9yZGVyOm5v
bmU7Ym9yZGVyLXRvcDpzb2xpZCAjRTFFMUUxIDEuMHB0O3BhZGRpbmc6My4wcHQgMGluIDBpbiAw
aW4iPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1hcmdpbi1sZWZ0Oi41aW4iPjxiPkZy
b206PC9iPiBEaWVnbyBSLiBMb3BleiAmbHQ7PGEgaHJlZj0ibWFpbHRvOmRpZWdvLnIubG9wZXpA
dGVsZWZvbmljYS5jb20iPmRpZWdvLnIubG9wZXpAdGVsZWZvbmljYS5jb208L2E+Jmd0Ow0KPGJy
Pg0KPGI+U2VudDo8L2I+IFR1ZXNkYXksIFNlcHRlbWJlciAyMiwgMjAyMCA5OjUwIEFNPGJyPg0K
PGI+VG86PC9iPiBNci4gSmFlaG9vbiBQYXVsIEplb25nICZsdDs8YSBocmVmPSJtYWlsdG86amFl
aG9vbi5wYXVsQGdtYWlsLmNvbSI+amFlaG9vbi5wYXVsQGdtYWlsLmNvbTwvYT4mZ3Q7OyBMaW5k
YSBEdW5iYXIgJmx0OzxhIGhyZWY9Im1haWx0bzpsaW5kYS5kdW5iYXJAZnV0dXJld2VpLmNvbSI+
bGluZGEuZHVuYmFyQGZ1dHVyZXdlaS5jb208L2E+Jmd0Ozxicj4NCjxiPkNjOjwvYj4gWGlhbGlh
bmcgKEZyYW5rKSAmbHQ7PGEgaHJlZj0ibWFpbHRvOmZyYW5rLnhpYWxpYW5nQGh1YXdlaS5jb20i
PmZyYW5rLnhpYWxpYW5nQGh1YXdlaS5jb208L2E+Jmd0OzsgWW9hdiBOaXIgJmx0OzxhIGhyZWY9
Im1haWx0bzp5bmlyLmlldGZAZ21haWwuY29tIj55bmlyLmlldGZAZ21haWwuY29tPC9hPiZndDs7
IEpvaG4gU3RyYXNzbmVyICZsdDs8YSBocmVmPSJtYWlsdG86Sm9obi5zYy5TdHJhc3NuZXJAaHVh
d2VpLmNvbSI+Sm9obi5zYy5TdHJhc3NuZXJAaHVhd2VpLmNvbTwvYT4mZ3Q7Ow0KIEFsZG8gQmFz
aWxlICZsdDs8YSBocmVmPSJtYWlsdG86Y2F0YWxkby5iYXNpbGVAcG9saXRvLml0Ij5jYXRhbGRv
LmJhc2lsZUBwb2xpdG8uaXQ8L2E+Jmd0OzsgUm9tYW4gRGFueWxpdyAmbHQ7PGEgaHJlZj0ibWFp
bHRvOnJkZEBjZXJ0Lm9yZyI+cmRkQGNlcnQub3JnPC9hPiZndDs8YnI+DQo8Yj5TdWJqZWN0Ojwv
Yj4gUmU6IE9mZmVyIGZvciBSZXZpc2lvbiBIZWxwIGZvciBJMk5TRiBOU0ZzIENhcGFiaWxpdGll
cyBJbmZvcm1hdGlvbiBNb2RlbCBEcmFmdDxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8L2Rpdj4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJnaW4tbGVmdDouNWluIj4mbmJzcDs8bzpw
PjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJnaW4tbGVmdDouNWlu
Ij48c3BhbiBjbGFzcz0iRW1haWxTdHlsZTIxIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjBw
dCI+SDwvc3Bhbj48L3NwYW4+PHNwYW4gY2xhc3M9IkVtYWlsU3R5bGUyMSI+PHNwYW4gbGFuZz0i
RVMiIHN0eWxlPSJmb250LXNpemU6MTAuMHB0Ij5pIFBhdWwsPC9zcGFuPjwvc3Bhbj48bzpwPjwv
bzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJnaW4tbGVmdDouNWluIj48
c3BhbiBjbGFzcz0iRW1haWxTdHlsZTIxIj48c3BhbiBsYW5nPSJFUyIgc3R5bGU9ImZvbnQtc2l6
ZToxMC4wcHQiPiZuYnNwOzwvc3Bhbj48L3NwYW4+PG86cD48L286cD48L3A+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIiBzdHlsZT0ibWFyZ2luLWxlZnQ6LjVpbiI+PHNwYW4gY2xhc3M9IkVtYWlsU3R5
bGUyMSI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQiPkJlZm9yZSB5b3UgZ28gZm9yIGl0
LCBsZXQgbWUgc2hhcmUgd2l0aCB5b3Ugc29tZSByZWZsZWN0aW9ucyBvbiB0aGUgc3RhdGUgb2Yg
dGhlIGRyYWZ0LCBpbiB0aGUgc3Bpcml0IG9mIHdoYXQgSSByZXBsaWVkIHRvIEVyaWMgVnluY2tl
Ljwvc3Bhbj48L3NwYW4+PG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHls
ZT0ibWFyZ2luLWxlZnQ6LjVpbiI+PHNwYW4gY2xhc3M9IkVtYWlsU3R5bGUyMSI+PHNwYW4gc3R5
bGU9ImZvbnQtc2l6ZToxMC4wcHQiPiZuYnNwOzwvc3Bhbj48L3NwYW4+PG86cD48L286cD48L3A+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibWFyZ2luLWxlZnQ6LjVpbiI+PHNwYW4gc3R5
bGU9ImZvbnQtc2l6ZToxMC4wcHQ7bXNvLWZhcmVhc3QtbGFuZ3VhZ2U6RU4tVVMiPkkgbXVzdCBj
b25mZXNzIHRoZXJlIGhhcyBiZWVuIGEgY29tYmluYXRpb24gb2YgZXZlbnRzIHRoYXQgbWFkZSBt
ZSB0aGluayB0aGUgYmVzdCBzb2x1dGlvbiB3YXMgdG8gbGVhdmUgdGhpcyBkcmFmdCB0byBmYWRl
IGF3YXkuIEZpcnN0LCBJIHdhcyBub3QgKGhhdmUgbm90DQogYmVlbiB5ZXQpIGFibGUgdG8gZmlu
ZCBhIHNvbHV0aW9uIHRvIG1vc3Qgb2YgUm9tYW7igJlzIGNvbW1lbnRzIHdpdGhvdXQgdG90YWxs
eSByZXdyaXRpbmcgbW9zdCwgaWYgbm90IGFsbCwgb2YgdGhlIGRvY3VtZW50LiZuYnNwOyBTZWNv
bmQsIHRoZSBmYWN0IHRoYXQgdGhlIGNhcGFiaWxpdHkgZGF0YSBtb2RlbCB3YXMgZXZvbHZpbmcg
aW4gYSBxdWl0ZSByZWFzb25hYmxlIGFuZCBwcmFnbWF0aWMgd2F5LCBpbmNsdWRpbmcgcnVubmlu
ZyBjb2RlIGF0IHRoZQ0KIGhhY2thdGhvbnMsIGZvbGxvd2luZyB0aGUgc3Bpcml0IG9mIHRoZSBp
bml0aWFsIHdvcmsgaW4gdGhlIGluZm9ybWF0aW9uIG1vZGVsLCBidXQgbm90IGF0dGVtcHRpbmcg
dG8gYWxpZ24gd2l0aCBpdHMgbW9zdCByZWNlbnQgZXZvbHV0aW9uLiBJZiBJIGhhdmUgbm90IHNo
YXJlZCB0aGlzIHBvc2l0aW9uIGJlZm9yZSBpcyBiZWNhdXNlIEkgaGF2ZSBiZWVuIGxvb2tpbmcg
Zm9yIGEgd2F5IHRvIG1ha2UgdGhlIGlkZWEgb2YgYnJpZGdpbmcgY2FwYWJpbGl0eQ0KIGRlY2xh
cmF0aW9ucyBhbmQgc2VjdXJpdHkgcG9saWN5IHN0YXRlbWVudHMgYXQgdGhlIEkyTlNGIGNvbnRy
b2xsZXIgdmlhYmxlLCBhbmQgSSB3YXMgaG9waW5nIHRvIGZpbmQgc3VjaCBhIHdheSBieSByZXVz
aW5nIHBhcnQgb2YgdGhlIGNhcGFiaWxpdHkgaW5mbyBtb2RlbCBkcmFmdC48L3NwYW4+PG86cD48
L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibWFyZ2luLWxlZnQ6LjVpbiI+
PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7bXNvLWZhcmVhc3QtbGFuZ3VhZ2U6RU4tVVMi
PiZuYnNwOzwvc3Bhbj48bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxl
PSJtYXJnaW4tbGVmdDouNWluIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDttc28tZmFy
ZWFzdC1sYW5ndWFnZTpFTi1VUyI+QXMgSSB0b2xkIEVyaWMsIEkgYmVsaWV2ZSB0aGUgY3VycmVu
dCBjYXBhYmlsaXR5IG1vZGVsIGhhcyBhIHBvd2VyZnVsICh0aG91Z2ggcHJvYmFibHkgbm90IHll
dCBjb21wbGV0ZSkgY2FsY3VsdXMgZm9yIHBvbGljeSBkZXNjcmlwdGlvbiBhbmQgdmFsaWRhdGlv
biwNCiBidXQgbm90IGRpcmVjdGx5IHJlbGF0ZWQgdG8gdGhlIG1hbmFnZW1lbnQgbWVjaGFuaXNt
cyBhZGRyZXNzZWQgaW4gdGhlIGNhcGFiaWxpdHkgZGF0YSBtb2RlbCBhbmQgdGhlIG90aGVyIGRh
dGEgbW9kZWxzIHByb2R1Y2VkIGluIEkyTlNGLiBJIGJlbGlldmUgdGhlcmUgaXMgYW4gb3Bwb3J0
dW5pdHkgZm9yIGFjY29tcGxpc2hpbmcgcG9saWN5LWNhcGFiaWxpdHkgYnJpZGdpbmcsIHVzaW5n
IGFzIGZvdW5kYXRpb24gdGhlIGN1cnJlbnQgY2FwYWJpbGl0eQ0KIG1vZGVsLCB0aG91Z2ggaXQg
c2VlbXMgdG8gbWUgdGhhdCB0aGlzIHRhc2sgd291bGQgcmVxdWlyZSBzb21lIHRpbWUgdG8gY29u
c29saWRhdGUgYW5kIHRoZXJlZm9yZSBpbXBseSBhbiBleHRlbnNpb24gb2YgdGhlIEkyTlNGIGxp
ZmV0aW1lLiBJIHdvdWxkIGxpa2UgdG8ga25vdyB5b3VyIHBvc2l0aW9uKCopIGFib3V0IHN1Y2gg
YW4gZXh0ZW5zaW9uLCAmbmJzcDt0aGF0IGNvdWxkIGFsc28gYmVjb21lIGFuIG9wcG9ydHVuaXR5
IHRvIHdvcmsgaW4gb3RoZXINCiBtYXR0ZXJzIHJlbGF0ZWQgdG8gYXR0ZXN0YXRpb24gKGluIHRo
ZSBsaWdodCBvZiB0aGUgd29yayBpbiBSQVRTIGFuZCB0aGUgTVVEIGluaXRpYXRpdmUgd2l0aGlu
IHRoZSBPcHMgQXJlYSkgYW5kIGFjY291bnRpbmcuPC9zcGFuPjxvOnA+PC9vOnA+PC9wPg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1hcmdpbi1sZWZ0Oi41aW4iPjxzcGFuIHN0eWxlPSJm
b250LXNpemU6MTAuMHB0O21zby1mYXJlYXN0LWxhbmd1YWdlOkVOLVVTIj4mbmJzcDs8L3NwYW4+
PG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibWFyZ2luLWxlZnQ6
LjVpbiI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7bXNvLWZhcmVhc3QtbGFuZ3VhZ2U6
RU4tVVMiPkJlIGdvb2RlLDwvc3Bhbj48bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3Jt
YWwiIHN0eWxlPSJtYXJnaW4tbGVmdDouNWluIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjBw
dDttc28tZmFyZWFzdC1sYW5ndWFnZTpFTi1VUyI+Jm5ic3A7PC9zcGFuPjxvOnA+PC9vOnA+PC9w
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1hcmdpbi1sZWZ0Oi41aW4iPjxzcGFuIHN0
eWxlPSJmb250LXNpemU6MTAuMHB0O21zby1mYXJlYXN0LWxhbmd1YWdlOkVOLVVTIj4oKikgSSBh
c3N1bWUgeW91IGFyZSBpbiBmYXZvciwgUGF1bC4gQnV0IEnigJlkIGxpa2UgdG8gZ2V0IExpbmRh
4oCZcywgWW9hduKAmXMgYW5kIFJvbWFu4oCZcyBpZGVhcywgYXMgd2VsbCBhcyB0aGUgYXZhaWxh
YmlsaXR5IHRvIHdvcmsgb24gdGhpcyBmcm9tIEZyYW5rLCBKb2huDQogYW5kIEFsZG8uPC9zcGFu
PjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1hcmdpbi1sZWZ0
Oi41aW4iPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O21zby1mYXJlYXN0LWxhbmd1YWdl
OkVOLVVTIj4mbmJzcDs8L3NwYW4+PG86cD48L286cD48L3A+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1z
b05vcm1hbCIgc3R5bGU9Im1hcmdpbi1sZWZ0Oi41aW4iPjxzcGFuIHN0eWxlPSJmb250LXNpemU6
MTAuMHB0O21zby1mYXJlYXN0LWxhbmd1YWdlOkVOLVVTIj4tLTwvc3Bhbj48bzpwPjwvbzpwPjwv
cD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJnaW4tbGVmdDouNWluIj48c3BhbiBs
YW5nPSJFUyIgc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7bXNvLWZhcmVhc3QtbGFuZ3VhZ2U6RU4t
VVMiPiZxdW90O0VzdGEgdmV6IG5vIGZhbGxhcmVtb3MsIERvY3RvciBJbmZpZXJubyZxdW90Ozwv
c3Bhbj48bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJnaW4t
bGVmdDouNWluIj48c3BhbiBsYW5nPSJFUyIgc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7bXNvLWZh
cmVhc3QtbGFuZ3VhZ2U6RU4tVVMiPiZuYnNwOzwvc3Bhbj48bzpwPjwvbzpwPjwvcD4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJnaW4tbGVmdDouNWluIj48c3BhbiBsYW5nPSJFUyIg
c3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7bXNvLWZhcmVhc3QtbGFuZ3VhZ2U6RU4tVVMiPkRyIERp
ZWdvIFIuIExvcGV6PC9zcGFuPjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIg
c3R5bGU9Im1hcmdpbi1sZWZ0Oi41aW4iPjxzcGFuIGxhbmc9IkVTIiBzdHlsZT0iZm9udC1zaXpl
OjEwLjBwdDttc28tZmFyZWFzdC1sYW5ndWFnZTpFTi1VUyI+VGVsZWZvbmljYSBJK0Q8L3NwYW4+
PG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibWFyZ2luLWxlZnQ6
LjVpbiI+PHNwYW4gbGFuZz0iRVMiIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O21zby1mYXJlYXN0
LWxhbmd1YWdlOkVOLVVTIj48YSBocmVmPSJodHRwczovL25hbTExLnNhZmVsaW5rcy5wcm90ZWN0
aW9uLm91dGxvb2suY29tLz91cmw9aHR0cHMlM0ElMkYlMkZ3d3cubGlua2VkaW4uY29tJTJGaW4l
MkZkcjJsb3BleiUyRiZhbXA7ZGF0YT0wMiU3QzAxJTdDbGluZGEuZHVuYmFyJTQwZnV0dXJld2Vp
LmNvbSU3QzA4YTQ4ODU4ZDdiZDRkODQzYTZlMDhkODVmNDdiNDM4JTdDMGZlZThmZjJhM2IyNDAx
ODljNzUzYTFkNTU5MWZlZGMlN0MxJTdDMCU3QzYzNzM2NDEwODg2NDk0OTYzMyZhbXA7c2RhdGE9
Uk9SNCUyRnlEMVdxV0RiMXJDYkp4M0VScVRpTUNROTJpYmt5ejI2a1laZEQ4JTNEJmFtcDtyZXNl
cnZlZD0wIj48c3BhbiBzdHlsZT0iY29sb3I6IzA1NjNDMSI+aHR0cHM6Ly93d3cubGlua2VkaW4u
Y29tL2luL2RyMmxvcGV6Lzwvc3Bhbj48L2E+Jm5ic3A7PC9zcGFuPjxvOnA+PC9vOnA+PC9wPg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1hcmdpbi1sZWZ0Oi41aW4iPjxzcGFuIGxhbmc9
IkVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDttc28tZmFyZWFzdC1sYW5ndWFnZTpFTi1VUyI+
Jm5ic3A7PC9zcGFuPjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9
Im1hcmdpbi1sZWZ0Oi41aW4iPjxzcGFuIGxhbmc9IkVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjBw
dDttc28tZmFyZWFzdC1sYW5ndWFnZTpFTi1VUyI+ZS1tYWlsOiZuYnNwOzwvc3Bhbj48c3BhbiBs
YW5nPSJFTi1HQiIgc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7bXNvLWZhcmVhc3QtbGFuZ3VhZ2U6
RU4tVVMiPjxhIGhyZWY9Im1haWx0bzpkaWVnby5yLmxvcGV6QHRlbGVmb25pY2EuY29tIj48c3Bh
biBsYW5nPSJFUyIgc3R5bGU9ImNvbG9yOiMwNTYzQzEiPmRpZWdvLnIubG9wZXpAdGVsZWZvbmlj
YS5jb208L3NwYW4+PC9hPjwvc3Bhbj48bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3Jt
YWwiIHN0eWxlPSJtYXJnaW4tbGVmdDouNWluIj48c3BhbiBsYW5nPSJFTi1HQiIgc3R5bGU9ImZv
bnQtc2l6ZToxMC4wcHQ7bXNvLWZhcmVhc3QtbGFuZ3VhZ2U6RU4tVVMiPlRlbDombmJzcDsmbmJz
cDsmbmJzcDsgJm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7ICszNCA5MTMgMTI5IDA0MTwvc3Bhbj48
bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJnaW4tbGVmdDou
NWluIj48c3BhbiBsYW5nPSJFTi1HQiIgc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7bXNvLWZhcmVh
c3QtbGFuZ3VhZ2U6RU4tVVMiPk1vYmlsZTogJm5ic3A7KzM0IDY4MiAwNTEgMDkxPC9zcGFuPjxv
OnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibWFyZ2lu
LWxlZnQ6LjVpbiI+PHNwYW4gbGFuZz0iRU4tR0IiIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O21z
by1mYXJlYXN0LWxhbmd1YWdlOkVOLVVTIj4tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tPC9zcGFuPjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1h
cmdpbi1sZWZ0Oi41aW4iPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O21zby1mYXJlYXN0
LWxhbmd1YWdlOkVOLVVTIj4mbmJzcDs8L3NwYW4+PG86cD48L286cD48L3A+DQo8ZGl2Pg0KPGRp
dj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJnaW4tbGVmdDoxLjBpbiI+T24gMTcv
MDkvMjAyMCwgMDE6NDIsICZxdW90O01yLiBKYWVob29uIFBhdWwgSmVvbmcmcXVvdDsgJmx0Ozxh
IGhyZWY9Im1haWx0bzpqYWVob29uLnBhdWxAZ21haWwuY29tIj5qYWVob29uLnBhdWxAZ21haWwu
Y29tPC9hPiZndDsgd3JvdGU6PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPGRpdj4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJnaW4tbGVmdDoxLjBpbiI+Jm5ic3A7PG86
cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0i
bWFyZ2luLWxlZnQ6MS4waW4iPkhpIExpbmRhLDxvOnA+PC9vOnA+PC9wPg0KPGRpdj4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJnaW4tbGVmdDoxLjBpbiI+SSB3aWxsIGFkZHJlc3Mg
b3VyIEFEIFJvbWFuJ3MgY29tbWVudHMgb24gdGhpcyBOU0ZzIGNhcGFiaWxpdGllcyBpbmZvcm1h
dGlvbiBkcmFmdCBhcyB0aGUgMm5kIGVkaXRvciB0aHJvdWdoIHRoZSBjb2xsYWJvcmF0aW9uIHdp
dGggRnJhbmsgKHRoZSAxc3QgZWRpdG9yKSBhbmQgdGhlIG90aGVyIGF1dGhvcnMuPG86cD48L286
cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibWFyZ2lu
LWxlZnQ6MS4waW4iPiZuYnNwOzxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1hcmdpbi1sZWZ0OjEuMGluIj5JIENDIG91ciBBRCBSb21h
biBhbmQgdGhlIG90aGVyIGF1dGhvcnMsIHN1Y2ggYXMgSm9obiBhbmQgQ2F0YWxkby48bzpwPjwv
bzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwcmUgc3R5bGU9Im1hcmdpbi1sZWZ0OjEuMGluIj48
c3BhbiBzdHlsZT0iZm9udC1zaXplOjkuNXB0Ij4mbmJzcDs8L3NwYW4+PG86cD48L286cD48L3By
ZT4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJnaW4tbGVm
dDoxLjBpbiI+VGhhbmtzIGZvciB5b3VyIHN1cHBvcnQgYW5kIGd1aWRhbmNlLjxvOnA+PC9vOnA+
PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1hcmdpbi1s
ZWZ0OjEuMGluIj4mbmJzcDs8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJnaW4tbGVmdDoxLjBpbiI+QmVzdCBSZWdhcmRzLDxvOnA+
PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1h
cmdpbi1sZWZ0OjEuMGluIj5QYXVsPG86cD48L286cD48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1hcmdpbi1sZWZ0OjEuMGluIj4mbmJzcDs8bzpwPjwv
bzpwPjwvcD4NCjxkaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1hcmdp
bi1sZWZ0OjEuMGluIj4yMDIwPHNwYW4gbGFuZz0iWkgtQ04iIHN0eWxlPSJmb250LWZhbWlseTom
cXVvdDtNYWxndW4gR290aGljJnF1b3Q7LHNhbnMtc2VyaWYiPuuFhDwvc3Bhbj4gOTxzcGFuIGxh
bmc9IlpILUNOIiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7TWFsZ3VuIEdvdGhpYyZxdW90Oyxz
YW5zLXNlcmlmIj7sm5Q8L3NwYW4+IDE3PHNwYW4gbGFuZz0iWkgtQ04iIHN0eWxlPSJmb250LWZh
bWlseTomcXVvdDtNYWxndW4gR290aGljJnF1b3Q7LHNhbnMtc2VyaWYiPuydvDwvc3Bhbj4NCiAo
PHNwYW4gbGFuZz0iWkgtQ04iIHN0eWxlPSJmb250LWZhbWlseTomcXVvdDtNYWxndW4gR290aGlj
JnF1b3Q7LHNhbnMtc2VyaWYiPuuqqTwvc3Bhbj4pIDxzcGFuIGxhbmc9IlpILUNOIiBzdHlsZT0i
Zm9udC1mYW1pbHk6JnF1b3Q7TWFsZ3VuIEdvdGhpYyZxdW90OyxzYW5zLXNlcmlmIj4NCuyYpOyg
hDwvc3Bhbj48c3BhbiBsYW5nPSJaSC1DTiI+IDwvc3Bhbj4zOjQ0LCBMaW5kYSBEdW5iYXIgJmx0
OzxhIGhyZWY9Im1haWx0bzpsaW5kYS5kdW5iYXJAZnV0dXJld2VpLmNvbSI+bGluZGEuZHVuYmFy
QGZ1dHVyZXdlaS5jb208L2E+Jmd0OzxzcGFuIGxhbmc9IlpILUNOIiBzdHlsZT0iZm9udC1mYW1p
bHk6JnF1b3Q7TWFsZ3VuIEdvdGhpYyZxdW90OyxzYW5zLXNlcmlmIj7ri5jsnbQ8L3NwYW4+PHNw
YW4gbGFuZz0iWkgtQ04iPg0KPC9zcGFuPjxzcGFuIGxhbmc9IlpILUNOIiBzdHlsZT0iZm9udC1m
YW1pbHk6JnF1b3Q7TWFsZ3VuIEdvdGhpYyZxdW90OyxzYW5zLXNlcmlmIj7snpHshLE8L3NwYW4+
OjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8YmxvY2txdW90ZSBzdHlsZT0iYm9yZGVyOm5vbmU7
Ym9yZGVyLWxlZnQ6c29saWQgI0NDQ0NDQyAxLjBwdDtwYWRkaW5nOjBpbiAwaW4gMGluIDYuMHB0
O21hcmdpbi1sZWZ0OjQuOHB0O21hcmdpbi10b3A6NS4wcHQ7bWFyZ2luLXJpZ2h0OjBpbjttYXJn
aW4tYm90dG9tOjUuMHB0Ij4NCjxkaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5
bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvO21h
cmdpbi1sZWZ0OjEuMGluIj4NClBhdWwsIDxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFs
dDphdXRvO21hcmdpbi1sZWZ0OjEuMGluIj4NCiZuYnNwOzxvOnA+PC9vOnA+PC9wPg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4t
Ym90dG9tLWFsdDphdXRvO21hcmdpbi1sZWZ0OjEuMGluIj4NClRoYW5rIHlvdSB2ZXJ5IG11Y2gg
Zm9yIG9mZmVyaW5nIHRvIGFkZHJlc3MgdGhlIEFEIGNvbW1lbnRzIHRvIHRoaXMgZHJhZnQuIExv
b2tzIGxpa2UgdGhlIGN1cnJlbnQgYXV0aG9ycyBhcmUgdG9vIGJ1c3kgdG8gYWRkcmVzcyB0aG9z
ZSBjb21tZW50cy4gSXQgaGFzIGJlZW4gb3ZlciBhIHllYXIgc2luY2UgdGhlIEFEIGNvbW1lbnRz
IHdlcmUgZ2l2ZW4uJm5ic3A7IFdlIG5lZWQgdG8gbW92ZSB0aGUgZHJhZnQgZm9yd2FyZC4gVGhl
cmVmb3JlLCBJMk5TRg0KIGNoYWlycyBoYXZlIGF1dGhvcml6ZWQgeW91IHRvIGJlIG9uZSBvZiB0
aGUgZWRpdG9ycyB0byBhZGRyZXNzIHRoZSBBRCBjb21tZW50cyBhbmQgcmV2aXNlIHRoZSBkcmFm
dC4NCjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJn
aW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvO21hcmdpbi1sZWZ0OjEu
MGluIj4NCiZuYnNwOzxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9
Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvO21hcmdp
bi1sZWZ0OjEuMGluIj4NCiZuYnNwOzxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1h
bCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDph
dXRvO21hcmdpbi1sZWZ0OjEuMGluIj4NClRoYW5rIHlvdSB2ZXJ5IG11Y2guIDxvOnA+PC9vOnA+
PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRv
O21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvO21hcmdpbi1sZWZ0OjEuMGluIj4NCiZuYnNwOzxv
OnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9w
LWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvO21hcmdpbi1sZWZ0OjEuMGluIj4N
CkxpbmRhICZhbXA7IFlvYXY8bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0
eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0bztt
YXJnaW4tbGVmdDoxLjBpbiI+DQombmJzcDs8bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29O
b3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1h
bHQ6YXV0bzttYXJnaW4tbGVmdDoxLjBpbiI+DQombmJzcDs8bzpwPjwvbzpwPjwvcD4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2lu
LWJvdHRvbS1hbHQ6YXV0bzttYXJnaW4tbGVmdDoxLjBpbiI+DQo8Yj5Gcm9tOjwvYj4gTXIuIEph
ZWhvb24gUGF1bCBKZW9uZyAmbHQ7PGEgaHJlZj0ibWFpbHRvOmphZWhvb24ucGF1bEBnbWFpbC5j
b20iIHRhcmdldD0iX2JsYW5rIj5qYWVob29uLnBhdWxAZ21haWwuY29tPC9hPiZndDsNCjxicj4N
CjxiPlNlbnQ6PC9iPiBTdW5kYXksIFNlcHRlbWJlciAxMywgMjAyMCAxMDowOSBBTTxicj4NCjxi
PlRvOjwvYj4gWGlhbGlhbmcgKEZyYW5rKSAmbHQ7PGEgaHJlZj0ibWFpbHRvOmZyYW5rLnhpYWxp
YW5nQGh1YXdlaS5jb20iIHRhcmdldD0iX2JsYW5rIj5mcmFuay54aWFsaWFuZ0BodWF3ZWkuY29t
PC9hPiZndDs8YnI+DQo8Yj5DYzo8L2I+IExpbmRhIER1bmJhciAmbHQ7PGEgaHJlZj0ibWFpbHRv
OmxpbmRhLmR1bmJhckBmdXR1cmV3ZWkuY29tIiB0YXJnZXQ9Il9ibGFuayI+bGluZGEuZHVuYmFy
QGZ1dHVyZXdlaS5jb208L2E+Jmd0OzsgWW9hdiBOaXIgJmx0OzxhIGhyZWY9Im1haWx0bzp5bmly
LmlldGZAZ21haWwuY29tIiB0YXJnZXQ9Il9ibGFuayI+eW5pci5pZXRmQGdtYWlsLmNvbTwvYT4m
Z3Q7OyBESUVHTyBMT1BFWiBHQVJDSUEgJmx0OzxhIGhyZWY9Im1haWx0bzpkaWVnby5yLmxvcGV6
QHRlbGVmb25pY2EuY29tIiB0YXJnZXQ9Il9ibGFuayI+ZGllZ28uci5sb3BlekB0ZWxlZm9uaWNh
LmNvbTwvYT4mZ3Q7Ow0KIEphZWhvb24gSmVvbmcgJmx0OzxhIGhyZWY9Im1haWx0bzpqYWVob29u
LnBhdWxAZ21haWwuY29tIiB0YXJnZXQ9Il9ibGFuayI+amFlaG9vbi5wYXVsQGdtYWlsLmNvbTwv
YT4mZ3Q7PGJyPg0KPGI+U3ViamVjdDo8L2I+IE9mZmVyIGZvciBSZXZpc2lvbiBIZWxwIGZvciBJ
Mk5TRiBOU0ZzIENhcGFiaWxpdGllcyBJbmZvcm1hdGlvbiBNb2RlbCBEcmFmdDxvOnA+PC9vOnA+
PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRv
O21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvO21hcmdpbi1sZWZ0OjEuMGluIj4NCiZuYnNwOzxv
OnA+PC9vOnA+PC9wPg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFy
Z2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0bzttYXJnaW4tbGVmdDox
LjBpbiI+DQpIaSBGcmFuayw8bzpwPjwvbzpwPjwvcD4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9y
bWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0
OmF1dG87bWFyZ2luLWxlZnQ6MS4waW4iPg0KQ291bGQgSSBoZWxwIHlvdSB0byByZXZpc2UgeW91
ciBpbmZvcm1hdGlvbiBtb2RlbCBkcmFmdCBmb3Igb3VyIEFEIFJvbWFuIERhbnlsaXcncyByZXZp
ZXcgY29tbWVudHMmbmJzcDsgYXMgYSBjby1lZGl0b3I/PG86cD48L286cD48L3A+DQo8L2Rpdj4N
CjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1
dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG87bWFyZ2luLWxlZnQ6MS4waW4iPg0KPGEgaHJl
Zj0iaHR0cHM6Ly9uYW0xMS5zYWZlbGlua3MucHJvdGVjdGlvbi5vdXRsb29rLmNvbS8/dXJsPWh0
dHBzJTNBJTJGJTJGZGF0YXRyYWNrZXIuaWV0Zi5vcmclMkZkb2MlMkZkcmFmdC1pZXRmLWkybnNm
LWNhcGFiaWxpdHklMkYlM0ZpbmNsdWRlX3RleHQlM0QxJmFtcDtkYXRhPTAyJTdDMDElN0NsaW5k
YS5kdW5iYXIlNDBmdXR1cmV3ZWkuY29tJTdDMDhhNDg4NThkN2JkNGQ4NDNhNmUwOGQ4NWY0N2I0
MzglN0MwZmVlOGZmMmEzYjI0MDE4OWM3NTNhMWQ1NTkxZmVkYyU3QzElN0MwJTdDNjM3MzY0MTA4
ODY0OTU5NjI2JmFtcDtzZGF0YT1HVXJiYVl1MlE0TjFZTlVVZXQyb1ZSUHFieW5BNzhjU0JUZiUy
RkJlU0NZNDQlM0QmYW1wO3Jlc2VydmVkPTAiIHRhcmdldD0iX2JsYW5rIj5odHRwczovL2RhdGF0
cmFja2VyLmlldGYub3JnL2RvYy9kcmFmdC1pZXRmLWkybnNmLWNhcGFiaWxpdHkvP2luY2x1ZGVf
dGV4dD0xPC9hPjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFs
dDphdXRvO21hcmdpbi1sZWZ0OjEuMGluIj4NCiZuYnNwOzxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+
DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDph
dXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvO21hcmdpbi1sZWZ0OjEuMGluIj4NCkFzIHlv
dSBrbm93LCBJIGhhdmUgZmluaXNoZWQgb3VyIEkyTlNGIGRhdGEgbW9kZWwgZHJhZnRzLjxvOnA+
PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1z
by1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvO21hcmdpbi1s
ZWZ0OjEuMGluIj4NCiZuYnNwOzxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4t
Ym90dG9tLWFsdDphdXRvO21hcmdpbi1sZWZ0OjEuMGluIj4NCkkgYW0gaGFwcHkgdG8gd29yayBv
biB0aGUgcmV2aXNpb24gd2l0aCB5b3UgaW4gb3JkZXIgdG8gY29tcGxldGUgb3VyIEkyTlNGIGRl
bGl2ZXJhYmxlcy48bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29O
b3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1h
bHQ6YXV0bzttYXJnaW4tbGVmdDoxLjBpbiI+DQombmJzcDs8bzpwPjwvbzpwPjwvcD4NCjwvZGl2
Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6
YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0bzttYXJnaW4tbGVmdDoxLjBpbiI+DQpUaGFu
a3MuPG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBz
dHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG87
bWFyZ2luLWxlZnQ6MS4waW4iPg0KJm5ic3A7PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNv
LW1hcmdpbi1ib3R0b20tYWx0OmF1dG87bWFyZ2luLWxlZnQ6MS4waW4iPg0KQmVzdCBSZWdhcmRz
LDxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5
bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvO21h
cmdpbi1sZWZ0OjEuMGluIj4NClBhdWw8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8
L2Rpdj4NCjwvZGl2Pg0KPC9ibG9ja3F1b3RlPg0KPC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
IiBzdHlsZT0ibWFyZ2luLWxlZnQ6LjVpbiI+Jm5ic3A7PG86cD48L286cD48L3A+DQo8ZGl2IHN0
eWxlPSJtYXJnaW4tbGVmdDouNWluIj4NCjxkaXYgY2xhc3M9Ik1zb05vcm1hbCIgYWxpZ249ImNl
bnRlciIgc3R5bGU9InRleHQtYWxpZ246Y2VudGVyIj4NCjxociBzaXplPSIxIiB3aWR0aD0iMTAw
JSIgYWxpZ249ImNlbnRlciI+DQo8L2Rpdj4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIg
c3R5bGU9Im1hcmdpbi1sZWZ0Oi41aW4iPjxzcGFuIHN0eWxlPSJmb250LXNpemU6Ny41cHQ7Zm9u
dC1mYW1pbHk6JnF1b3Q7QXJpYWwmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjpncmF5Ij48YnI+DQpF
c3RlIG1lbnNhamUgeSBzdXMgYWRqdW50b3Mgc2UgZGlyaWdlbiBleGNsdXNpdmFtZW50ZSBhIHN1
IGRlc3RpbmF0YXJpbywgcHVlZGUgY29udGVuZXIgaW5mb3JtYWNpw7NuIHByaXZpbGVnaWFkYSBv
IGNvbmZpZGVuY2lhbCB5IGVzIHBhcmEgdXNvIGV4Y2x1c2l2byBkZSBsYSBwZXJzb25hIG8gZW50
aWRhZCBkZSBkZXN0aW5vLiBTaSBubyBlcyB1c3RlZC4gZWwgZGVzdGluYXRhcmlvIGluZGljYWRv
LCBxdWVkYSBub3RpZmljYWRvIGRlIHF1ZSBsYQ0KIGxlY3R1cmEsIHV0aWxpemFjacOzbiwgZGl2
dWxnYWNpw7NuIHkvbyBjb3BpYSBzaW4gYXV0b3JpemFjacOzbiBwdWVkZSBlc3RhciBwcm9oaWJp
ZGEgZW4gdmlydHVkIGRlIGxhIGxlZ2lzbGFjacOzbiB2aWdlbnRlLiBTaSBoYSByZWNpYmlkbyBl
c3RlIG1lbnNhamUgcG9yIGVycm9yLCBsZSByb2dhbW9zIHF1ZSBub3MgbG8gY29tdW5pcXVlIGlu
bWVkaWF0YW1lbnRlIHBvciBlc3RhIG1pc21hIHbDrWEgeSBwcm9jZWRhIGEgc3UgZGVzdHJ1Y2Np
w7NuLjxicj4NCjxicj4NClRoZSBpbmZvcm1hdGlvbiBjb250YWluZWQgaW4gdGhpcyB0cmFuc21p
c3Npb24gaXMgcHJpdmlsZWdlZCBhbmQgY29uZmlkZW50aWFsIGluZm9ybWF0aW9uIGludGVuZGVk
IG9ubHkgZm9yIHRoZSB1c2Ugb2YgdGhlIGluZGl2aWR1YWwgb3IgZW50aXR5IG5hbWVkIGFib3Zl
LiBJZiB0aGUgcmVhZGVyIG9mIHRoaXMgbWVzc2FnZSBpcyBub3QgdGhlIGludGVuZGVkIHJlY2lw
aWVudCwgeW91IGFyZSBoZXJlYnkgbm90aWZpZWQgdGhhdCBhbnkgZGlzc2VtaW5hdGlvbiwNCiBk
aXN0cmlidXRpb24gb3IgY29weWluZyBvZiB0aGlzIGNvbW11bmljYXRpb24gaXMgc3RyaWN0bHkg
cHJvaGliaXRlZC4gSWYgeW91IGhhdmUgcmVjZWl2ZWQgdGhpcyB0cmFuc21pc3Npb24gaW4gZXJy
b3IsIGRvIG5vdCByZWFkIGl0LiBQbGVhc2UgaW1tZWRpYXRlbHkgcmVwbHkgdG8gdGhlIHNlbmRl
ciB0aGF0IHlvdSBoYXZlIHJlY2VpdmVkIHRoaXMgY29tbXVuaWNhdGlvbiBpbiBlcnJvciBhbmQg
dGhlbiBkZWxldGUgaXQuPGJyPg0KPGJyPg0KRXN0YSBtZW5zYWdlbSBlIHNldXMgYW5leG9zIHNl
IGRpcmlnZW0gZXhjbHVzaXZhbWVudGUgYW8gc2V1IGRlc3RpbmF0w6FyaW8sIHBvZGUgY29udGVy
IGluZm9ybWHDp8OjbyBwcml2aWxlZ2lhZGEgb3UgY29uZmlkZW5jaWFsIGUgw6kgcGFyYSB1c28g
ZXhjbHVzaXZvIGRhIHBlc3NvYSBvdSBlbnRpZGFkZSBkZSBkZXN0aW5vLiBTZSBuw6NvIMOpIHZv
c3NhIHNlbmhvcmlhIG8gZGVzdGluYXTDoXJpbyBpbmRpY2FkbywgZmljYSBub3RpZmljYWRvIGRl
IHF1ZSBhDQogbGVpdHVyYSwgdXRpbGl6YcOnw6NvLCBkaXZ1bGdhw6fDo28gZS9vdSBjw7NwaWEg
c2VtIGF1dG9yaXphw6fDo28gcG9kZSBlc3RhciBwcm9pYmlkYSBlbSB2aXJ0dWRlIGRhIGxlZ2lz
bGHDp8OjbyB2aWdlbnRlLiBTZSByZWNlYmV1IGVzdGEgbWVuc2FnZW0gcG9yIGVycm8sIHJvZ2Ft
b3MtbGhlIHF1ZSBub3MgbyBjb211bmlxdWUgaW1lZGlhdGFtZW50ZSBwb3IgZXN0YSBtZXNtYSB2
aWEgZSBwcm9jZWRhIGEgc3VhIGRlc3RydWnDp8Ojbzwvc3Bhbj48bzpwPjwvbzpwPjwvcD4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPGRpdiBjbGFzcz0iTXNv
Tm9ybWFsIiBhbGlnbj0iY2VudGVyIiBzdHlsZT0idGV4dC1hbGlnbjpjZW50ZXIiPg0KPGhyIHNp
emU9IjIiIHdpZHRoPSIxMDAlIiBhbGlnbj0iY2VudGVyIj4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1z
b05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZTo3LjVwdDtmb250LWZhbWlseTomcXVvdDtB
cmlhbCZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOmdyYXkiPjxicj4NCkVzdGUgbWVuc2FqZSB5IHN1
cyBhZGp1bnRvcyBzZSBkaXJpZ2VuIGV4Y2x1c2l2YW1lbnRlIGEgc3UgZGVzdGluYXRhcmlvLCBw
dWVkZSBjb250ZW5lciBpbmZvcm1hY2nDs24gcHJpdmlsZWdpYWRhIG8gY29uZmlkZW5jaWFsIHkg
ZXMgcGFyYSB1c28gZXhjbHVzaXZvIGRlIGxhIHBlcnNvbmEgbyBlbnRpZGFkIGRlIGRlc3Rpbm8u
IFNpIG5vIGVzIHVzdGVkLiBlbCBkZXN0aW5hdGFyaW8gaW5kaWNhZG8sIHF1ZWRhIG5vdGlmaWNh
ZG8gZGUgcXVlIGxhDQogbGVjdHVyYSwgdXRpbGl6YWNpw7NuLCBkaXZ1bGdhY2nDs24geS9vIGNv
cGlhIHNpbiBhdXRvcml6YWNpw7NuIHB1ZWRlIGVzdGFyIHByb2hpYmlkYSBlbiB2aXJ0dWQgZGUg
bGEgbGVnaXNsYWNpw7NuIHZpZ2VudGUuIFNpIGhhIHJlY2liaWRvIGVzdGUgbWVuc2FqZSBwb3Ig
ZXJyb3IsIGxlIHJvZ2Ftb3MgcXVlIG5vcyBsbyBjb211bmlxdWUgaW5tZWRpYXRhbWVudGUgcG9y
IGVzdGEgbWlzbWEgdsOtYSB5IHByb2NlZGEgYSBzdSBkZXN0cnVjY2nDs24uPGJyPg0KPGJyPg0K
VGhlIGluZm9ybWF0aW9uIGNvbnRhaW5lZCBpbiB0aGlzIHRyYW5zbWlzc2lvbiBpcyBwcml2aWxl
Z2VkIGFuZCBjb25maWRlbnRpYWwgaW5mb3JtYXRpb24gaW50ZW5kZWQgb25seSBmb3IgdGhlIHVz
ZSBvZiB0aGUgaW5kaXZpZHVhbCBvciBlbnRpdHkgbmFtZWQgYWJvdmUuIElmIHRoZSByZWFkZXIg
b2YgdGhpcyBtZXNzYWdlIGlzIG5vdCB0aGUgaW50ZW5kZWQgcmVjaXBpZW50LCB5b3UgYXJlIGhl
cmVieSBub3RpZmllZCB0aGF0IGFueSBkaXNzZW1pbmF0aW9uLA0KIGRpc3RyaWJ1dGlvbiBvciBj
b3B5aW5nIG9mIHRoaXMgY29tbXVuaWNhdGlvbiBpcyBzdHJpY3RseSBwcm9oaWJpdGVkLiBJZiB5
b3UgaGF2ZSByZWNlaXZlZCB0aGlzIHRyYW5zbWlzc2lvbiBpbiBlcnJvciwgZG8gbm90IHJlYWQg
aXQuIFBsZWFzZSBpbW1lZGlhdGVseSByZXBseSB0byB0aGUgc2VuZGVyIHRoYXQgeW91IGhhdmUg
cmVjZWl2ZWQgdGhpcyBjb21tdW5pY2F0aW9uIGluIGVycm9yIGFuZCB0aGVuIGRlbGV0ZSBpdC48
YnI+DQo8YnI+DQpFc3RhIG1lbnNhZ2VtIGUgc2V1cyBhbmV4b3Mgc2UgZGlyaWdlbSBleGNsdXNp
dmFtZW50ZSBhbyBzZXUgZGVzdGluYXTDoXJpbywgcG9kZSBjb250ZXIgaW5mb3JtYcOnw6NvIHBy
aXZpbGVnaWFkYSBvdSBjb25maWRlbmNpYWwgZSDDqSBwYXJhIHVzbyBleGNsdXNpdm8gZGEgcGVz
c29hIG91IGVudGlkYWRlIGRlIGRlc3Rpbm8uIFNlIG7Do28gw6kgdm9zc2Egc2VuaG9yaWEgbyBk
ZXN0aW5hdMOhcmlvIGluZGljYWRvLCBmaWNhIG5vdGlmaWNhZG8gZGUgcXVlIGENCiBsZWl0dXJh
LCB1dGlsaXphw6fDo28sIGRpdnVsZ2HDp8OjbyBlL291IGPDs3BpYSBzZW0gYXV0b3JpemHDp8Oj
byBwb2RlIGVzdGFyIHByb2liaWRhIGVtIHZpcnR1ZGUgZGEgbGVnaXNsYcOnw6NvIHZpZ2VudGUu
IFNlIHJlY2ViZXUgZXN0YSBtZW5zYWdlbSBwb3IgZXJybywgcm9nYW1vcy1saGUgcXVlIG5vcyBv
IGNvbXVuaXF1ZSBpbWVkaWF0YW1lbnRlIHBvciBlc3RhIG1lc21hIHZpYSBlIHByb2NlZGEgYSBz
dWEgZGVzdHJ1acOnw6NvPC9zcGFuPjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8L2JvZHk+DQo8
L2h0bWw+DQo=

--_000_SN6PR13MB23342D6464F8F67CBFE0129C85080SN6PR13MB2334namp_--


From nobody Fri Oct  9 17:55:07 2020
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 0ED633A1683 for <i2nsf@ietfa.amsl.com>; Fri,  9 Oct 2020 17:55:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.344
X-Spam-Level: 
X-Spam-Status: No, score=0.344 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=2.331, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_HK_NAME_FM_MR_MRS=0.01, 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 KYYtNIKefpcq for <i2nsf@ietfa.amsl.com>; Fri,  9 Oct 2020 17:55:01 -0700 (PDT)
Received: from mail-lf1-x129.google.com (mail-lf1-x129.google.com [IPv6:2a00:1450:4864:20::129]) (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 68FA33A1689 for <i2nsf@ietf.org>; Fri,  9 Oct 2020 17:55:00 -0700 (PDT)
Received: by mail-lf1-x129.google.com with SMTP id 184so12513190lfd.6 for <i2nsf@ietf.org>; Fri, 09 Oct 2020 17:55:00 -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=7Hj8tZVb1RbcMLBDE1ftZKtM46pQSmaUXaSludNwHv4=; b=ArXA5Cu6qU7JZxwnmCh/70b1XF7gHLDB2T/bQcLmfsaD6fde3XaRttJN4DvrfiOS5s tg7+FeFjYXHeq0W9MIiYd1xmbY4ySxKtOKOr7lgFeGA1jRNKxuNilONaoVNSTz1ekVUd /c2xeYTQ8iiSH8Y+hCkN12belZynpPUTmGpet78dDE3rdZezTX4HkPY0X6cRfmtYZ/wM Jurm+24zJdlEOfnShsQT02R7kJ8AE+L0gvwJCMEYpCcH0pM0gkMoBsRibor/OP3S3wcA OF5KL+2F63Odzs2iKyRKyZQaVYD11lMA7Y9+OV4RyN9MRQ77XodXp6Fw9ErUrKoGfLIN Ks8g==
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=7Hj8tZVb1RbcMLBDE1ftZKtM46pQSmaUXaSludNwHv4=; b=gSyoj5p7zqjtB3oiT+2VUqlkh/aoA5QGDqXPOtlOljd0qaUlq/xPlelMhlnfJkmFAc gEA+26ge6kWMYI3h2MDAPWN3SVKNTD8ZchD60TtoiRwjKwIwWBULDYxyragmNwp2U/bh DD2IvPCOh9znEvjtsjqCC0pFLBbrqNHIs8CifR7LQkivKWQC3wxEWSsUbj2D+wFoQ8p0 WJaIKHcPlIussGbfwLncyQgMwI2uhzE8wqrQ+355TZNXdsA2TmKi2VL9SoD3MxRhFvrU XBDeD85LWyxQ2TRWZelsnBp9uCFE5zRpXRv+f+briHXdMY9cw1Z/aOEzX3lHcV6Qs07e 2UDg==
X-Gm-Message-State: AOAM533jUDiPbC7keur5l+16NwCXHuPQshGHpw0uN0fLXmHbJC+U5Mvu EmUStWAsF0sMcSZtnJi6ZZMs8usVj/xQ7BKSkJn66pqnlHw=
X-Google-Smtp-Source: ABdhPJwfjQMQDaHGjjvAzHIjiQgrCl9eV2LiPceCVIaxSN1JDLy9Xf1JblBMH5SV5OOvaJlPTxOn5iEmSC7TgVpbHpU=
X-Received: by 2002:a19:4a83:: with SMTP id x125mr5466344lfa.38.1602291298356;  Fri, 09 Oct 2020 17:54:58 -0700 (PDT)
MIME-Version: 1.0
References: <SN6PR13MB23343DE9392FA9EDDDA65651850B0@SN6PR13MB2334.namprd13.prod.outlook.com> <SN6PR13MB23342D6464F8F67CBFE0129C85080@SN6PR13MB2334.namprd13.prod.outlook.com>
In-Reply-To: <SN6PR13MB23342D6464F8F67CBFE0129C85080@SN6PR13MB2334.namprd13.prod.outlook.com>
From: "Mr. Jaehoon Paul Jeong" <jaehoon.paul@gmail.com>
Date: Sat, 10 Oct 2020 09:54:48 +0900
Message-ID: <CAPK2DewMACWfR50824XEvfjMQPF7jcyTKAN7npiXnFvPHGT7OA@mail.gmail.com>
To: Linda Dunbar <linda.dunbar@futurewei.com>
Cc: i2nsf@ietf.org, skku-iotlab-members <skku-iotlab-members@googlegroups.com>, Jaehoon Jeong <jaehoon.paul@gmail.com>
Content-Type: multipart/alternative; boundary="000000000000aa53b805b1468314"
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2nsf/MvEti_9dFFIWK3TtBdrDS9QFSDI>
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, 10 Oct 2020 00:55:04 -0000

--000000000000aa53b805b1468314
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

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=EB=85=84 10=EC=9B=94 9=EC=9D=BC (=EA=B8=88) =EC=98=A4=ED=9B=84 11:58, =
Linda Dunbar <linda.dunbar@futurewei.com>=EB=8B=98=EC=9D=B4 =EC=9E=91=EC=84=
=B1:

> I2NSF WG,
>
>
>
> Correction:
>
>
>
> There has been NO object to the Author=E2=80=99s request for sunsetting t=
he
> draft-ietf-i2nsf-capability-5.
>
>
>
> We have marked the draft as =E2=80=9CDEAD=E2=80=9D 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 Capabilitie=
s
> 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=E2=80=99s request for sunsetti=
ng 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 evolvi=
ng
> 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=E2=80=99t hear any objecti=
on 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=E2=80=99d prefer the second option, as it seems more straightforward an=
d 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=3Dhttps%3A%2F%2Fwww.=
linkedin.com%2Fin%2Fdr2lopez%2F&data=3D02%7C01%7Clinda.dunbar%40futurewei.c=
om%7C08a48858d7bd4d843a6e08d85f47b438%7C0fee8ff2a3b240189c753a1d5591fedc%7C=
1%7C0%7C637364108864949633&sdata=3DROR4%2FyD1WqWDb1rCbJx3ERqTiMCQ92ibkyz26k=
YZdD8%3D&reserved=3D0>
>
>
>
>
> 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 =E2=80=9Cthe capability data =
model was
> evolving in a quite reasonable and pragmatic way, including running code =
at
> the hackathons=E2=80=9D.
>
>
>
> Looks like Eric Vyncke still wants the information model to be fixed to
> clear his =E2=80=9CDISCUSS=E2=80=9D ballot.
>
> How about the following steps:
>
> -          Ask Roman=E2=80=99s 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=E2=80=99s co=
mments
> without totally rewriting most, if not all, of the document.  Second, the
> fact that the capability data model was evolving in a quite reasonable an=
d
> pragmatic way, including running code at the hackathons, following the
> spirit of the initial work in the information model, but not attempting t=
o
> 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 address=
ed
> 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 see=
ms
> 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 opportuni=
ty
> 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=E2=80=99d like to get Linda=E2=
=80=99s, Yoav=E2=80=99s
> and Roman=E2=80=99s ideas, as well as the availability to work on this fr=
om 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=3Dhttps%3A%2F%2Fwww.=
linkedin.com%2Fin%2Fdr2lopez%2F&data=3D02%7C01%7Clinda.dunbar%40futurewei.c=
om%7C08a48858d7bd4d843a6e08d85f47b438%7C0fee8ff2a3b240189c753a1d5591fedc%7C=
1%7C0%7C637364108864949633&sdata=3DROR4%2FyD1WqWDb1rCbJx3ERqTiMCQ92ibkyz26k=
YZdD8%3D&reserved=3D0>
>
>
>
>
> 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=EB=85=84 9=EC=9B=94 17=EC=9D=BC (=EB=AA=A9) =EC=98=A4=EC=A0=84 3:44,=
 Linda Dunbar <linda.dunbar@futurewei.com>=EB=8B=98=EC=9D=B4 =EC=9E=91=EC=
=84=B1:
>
> 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 t=
he
> draft forward. Therefore, I2NSF chairs have authorized you to be one of t=
he
> 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_tex=
t=3D1
> <https://nam11.safelinks.protection.outlook.com/?url=3Dhttps%3A%2F%2Fdata=
tracker.ietf.org%2Fdoc%2Fdraft-ietf-i2nsf-capability%2F%3Finclude_text%3D1&=
data=3D02%7C01%7Clinda.dunbar%40futurewei.com%7C08a48858d7bd4d843a6e08d85f4=
7b438%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C637364108864959626&sdata=
=3DGUrbaYu2Q4N1YNUUet2oVRPqbynA78cSBTf%2FBeSCY44%3D&reserved=3D0>
>
>
>
> 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 I2NS=
F
> deliverables.
>
>
>
> Thanks.
>
>
>
> Best Regards,
>
> Paul
>
>
> ------------------------------
>
>
> Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario,
> puede contener informaci=C3=B3n 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=C3=
=B3n,
> divulgaci=C3=B3n y/o copia sin autorizaci=C3=B3n puede estar prohibida en=
 virtud de
> la legislaci=C3=B3n vigente. Si ha recibido este mensaje por error, le ro=
gamos
> que nos lo comunique inmediatamente por esta misma v=C3=ADa y proceda a s=
u
> destrucci=C3=B3n.
>
> 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 o=
r
> copying of this communication is strictly prohibited. If you have receive=
d
> this transmission in error, do not read it. Please immediately reply to t=
he
> sender that you have received this communication in error and then delete
> it.
>
> Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinat=C3=
=A1rio,
> pode conter informa=C3=A7=C3=A3o privilegiada ou confidencial e =C3=A9 pa=
ra uso exclusivo
> da pessoa ou entidade de destino. Se n=C3=A3o =C3=A9 vossa senhoria o des=
tinat=C3=A1rio
> indicado, fica notificado de que a leitura, utiliza=C3=A7=C3=A3o, divulga=
=C3=A7=C3=A3o e/ou
> c=C3=B3pia sem autoriza=C3=A7=C3=A3o pode estar proibida em virtude da le=
gisla=C3=A7=C3=A3o vigente.
> Se recebeu esta mensagem por erro, rogamos-lhe que nos o comunique
> imediatamente por esta mesma via e proceda a sua destrui=C3=A7=C3=A3o
>
>
> ------------------------------
>
>
> Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario,
> puede contener informaci=C3=B3n 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=C3=
=B3n,
> divulgaci=C3=B3n y/o copia sin autorizaci=C3=B3n puede estar prohibida en=
 virtud de
> la legislaci=C3=B3n vigente. Si ha recibido este mensaje por error, le ro=
gamos
> que nos lo comunique inmediatamente por esta misma v=C3=ADa y proceda a s=
u
> destrucci=C3=B3n.
>
> 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 o=
r
> copying of this communication is strictly prohibited. If you have receive=
d
> this transmission in error, do not read it. Please immediately reply to t=
he
> sender that you have received this communication in error and then delete
> it.
>
> Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinat=C3=
=A1rio,
> pode conter informa=C3=A7=C3=A3o privilegiada ou confidencial e =C3=A9 pa=
ra uso exclusivo
> da pessoa ou entidade de destino. Se n=C3=A3o =C3=A9 vossa senhoria o des=
tinat=C3=A1rio
> indicado, fica notificado de que a leitura, utiliza=C3=A7=C3=A3o, divulga=
=C3=A7=C3=A3o e/ou
> c=C3=B3pia sem autoriza=C3=A7=C3=A3o pode estar proibida em virtude da le=
gisla=C3=A7=C3=A3o vigente.
> Se recebeu esta mensagem por erro, rogamos-lhe que nos o comunique
> imediatamente por esta mesma via e proceda a sua destrui=C3=A7=C3=A3o
> _______________________________________________
> I2nsf mailing list
> I2nsf@ietf.org
> https://www.ietf.org/mailman/listinfo/i2nsf
>

--000000000000aa53b805b1468314
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto"><div>Hi Linda,</div><div dir=3D"auto">As I understand, I =
need to merge the relevant contents of the NSFs Capability Information Mode=
l Draft into the I2NSF NSF Capability Data Model Draft.</div><div dir=3D"au=
to"><br></div><div dir=3D"auto">Is it correct?</div><div dir=3D"auto"><br><=
/div><div dir=3D"auto">Thanks.</div><div dir=3D"auto"><br></div><div dir=3D=
"auto">Best Regards,</div><div dir=3D"auto">Paul</div><div dir=3D"auto"><br=
><div class=3D"gmail_quote" dir=3D"auto"><div dir=3D"ltr" class=3D"gmail_at=
tr">2020=EB=85=84 10=EC=9B=94 9=EC=9D=BC (=EA=B8=88) =EC=98=A4=ED=9B=84 11:=
58, Linda Dunbar &lt;<a href=3D"mailto:linda.dunbar@futurewei.com">linda.du=
nbar@futurewei.com</a>&gt;=EB=8B=98=EC=9D=B4 =EC=9E=91=EC=84=B1:<br></div><=
blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px=
 #ccc solid;padding-left:1ex">





<div lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"m_3697213585076377193WordSection1">
<p class=3D"MsoNormal">I2NSF WG, <u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">Correction: <u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">There has been NO object to the Author=E2=80=99s req=
uest for sunsetting the draft-ietf-i2nsf-capability-5.
<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">We have marked the draft as =E2=80=9CDEAD=E2=80=9D i=
n the WG status. <u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">Many thanks to the authors for putting the effort in=
 this draft for kickstarting all the data models in I2NSF WG.
<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">Linda &amp; Yoav<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<div>
<div style=3D"border:none;border-top:solid #e1e1e1 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b>From:</b> Linda Dunbar <br>
<b>Sent:</b> Thursday, October 8, 2020 4:36 PM<br>
<b>To:</b> <a href=3D"mailto:i2nsf@ietf.org" target=3D"_blank" rel=3D"noref=
errer">i2nsf@ietf.org</a><br>
<b>Subject:</b> draft-ietf-i2nsf-capability-05 is officially removed from I=
2NSF WG ( was RE: Is there any objection of sunset the I2NSF Capabilities I=
nformation Model Draft and merge the relevant information to the I2NSF Capa=
bility Data model draft?
<u></u><u></u></p>
</div>
</div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">I2nsf WG, <u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">There has been any objection to the Author=E2=80=99s=
 request for sunsetting the =C2=A0draft-ietf-i2nsf-capability-05.
<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">Authors of the draft-ietf-i2nsf-capability-data-mode=
l: please remove the reference to the Capability Information Model and uplo=
ad a new draft. We can ask IESG to re-review it.
<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">Thank you very much. <u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">Linda &amp; Yoav. <u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<div>
<div style=3D"border:none;border-top:solid #e1e1e1 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b>From:</b> Linda Dunbar <br>
<b>Sent:</b> Monday, September 28, 2020 11:00 AM<br>
<b>To:</b> <a href=3D"mailto:i2nsf@ietf.org" target=3D"_blank" rel=3D"noref=
errer">i2nsf@ietf.org</a><br>
<b>Subject:</b> Is there any objection of sunset the I2NSF Capabilities Inf=
ormation Model Draft and merge the relevant information to the I2NSF Capabi=
lity Data model draft?
<u></u><u></u></p>
</div>
</div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">I2NSF WG, <u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">As Diego has expressed that the original I2NSF capab=
ility information model was based on a policy expression calculus suitable =
for manipulating high-level policy expressions.=C2=A0 The capability data m=
odel has been evolving in a quite reasonable
 and pragmatic way, including running code at the hackathons.<u></u><u></u>=
</p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">The I2NSF Capability Information Model has fulfilled=
 its purpose of kickstarting and guiding the data model, and the authors be=
lieve that it is better to let the capability information model to be withd=
rawn. For the content in the information
 model still relevant to I2NSF Capability Data Model, they should be merged=
 into the Capability Data Model.
<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">Is there any objection from the WG?=C2=A0 If we don=
=E2=80=99t hear any objection by Oct 5, we will change the status of the dr=
aft.
<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">Cheers, =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0
<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">Linda &amp; Yoav<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<div>
<div style=3D"border:none;border-top:solid #e1e1e1 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b>From:</b> Diego R. Lopez &lt;<a href=3D"mailto:di=
ego.r.lopez@telefonica.com" target=3D"_blank" rel=3D"noreferrer">diego.r.lo=
pez@telefonica.com</a>&gt;
<br>
<b>Sent:</b> Tuesday, September 22, 2020 5:35 PM<br>
<b>To:</b> Linda Dunbar &lt;<a href=3D"mailto:linda.dunbar@futurewei.com" t=
arget=3D"_blank" rel=3D"noreferrer">linda.dunbar@futurewei.com</a>&gt;; Mr.=
 Jaehoon Paul Jeong &lt;<a href=3D"mailto:jaehoon.paul@gmail.com" target=3D=
"_blank" rel=3D"noreferrer">jaehoon.paul@gmail.com</a>&gt;<br>
<b>Cc:</b> Xialiang (Frank) &lt;<a href=3D"mailto:frank.xialiang@huawei.com=
" target=3D"_blank" rel=3D"noreferrer">frank.xialiang@huawei.com</a>&gt;; Y=
oav Nir &lt;<a href=3D"mailto:ynir.ietf@gmail.com" target=3D"_blank" rel=3D=
"noreferrer">ynir.ietf@gmail.com</a>&gt;; John Strassner &lt;<a href=3D"mai=
lto:John.sc.Strassner@huawei.com" target=3D"_blank" rel=3D"noreferrer">John=
.sc.Strassner@huawei.com</a>&gt;;
 Aldo Basile &lt;<a href=3D"mailto:cataldo.basile@polito.it" target=3D"_bla=
nk" rel=3D"noreferrer">cataldo.basile@polito.it</a>&gt;; Roman Danyliw &lt;=
<a href=3D"mailto:rdd@cert.org" target=3D"_blank" rel=3D"noreferrer">rdd@ce=
rt.org</a>&gt;<br>
<b>Subject:</b> Re: Offer for Revision Help for I2NSF NSFs Capabilities Inf=
ormation Model Draft<u></u><u></u></p>
</div>
</div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal"><span lang=3D"ES" style=3D"font-size:10.0pt">Hi Lind=
a,<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"ES" style=3D"font-size:10.0pt"><u></u>=
=C2=A0<u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt">I=E2=80=99d 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 allow=
ing us to reuse the
 capability model for policy-control transformation, and to incorporate the=
 attestation matters you know I was so much interested in.<u></u><u></u></s=
pan></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt"><u></u>=C2=A0<u></u=
></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt">Be goode,<u></u><u>=
</u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt"><u></u>=C2=A0<u></u=
></span></p>
<div>
<p class=3D"MsoNormal"><span lang=3D"ES" style=3D"font-size:10.0pt">--<u></=
u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"ES" style=3D"font-size:10.0pt">&quot;E=
sta vez no fallaremos, Doctor Infierno&quot;<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"ES" style=3D"font-size:10.0pt">=C2=A0<=
u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"ES" style=3D"font-size:10.0pt">Dr Dieg=
o R. Lopez<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"ES" style=3D"font-size:10.0pt">Telefon=
ica I+D<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"ES" style=3D"font-size:10.0pt"><a href=
=3D"https://nam11.safelinks.protection.outlook.com/?url=3Dhttps%3A%2F%2Fwww=
.linkedin.com%2Fin%2Fdr2lopez%2F&amp;data=3D02%7C01%7Clinda.dunbar%40future=
wei.com%7C08a48858d7bd4d843a6e08d85f47b438%7C0fee8ff2a3b240189c753a1d5591fe=
dc%7C1%7C0%7C637364108864949633&amp;sdata=3DROR4%2FyD1WqWDb1rCbJx3ERqTiMCQ9=
2ibkyz26kYZdD8%3D&amp;reserved=3D0" target=3D"_blank" rel=3D"noreferrer"><s=
pan style=3D"color:#0563c1">https://www.linkedin.com/in/dr2lopez/</span></a=
>=C2=A0<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"ES" style=3D"font-size:10.0pt">=C2=A0<=
u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"ES" style=3D"font-size:10.0pt">e-mail:=
=C2=A0</span><span lang=3D"EN-GB" style=3D"font-size:10.0pt"><a href=3D"mai=
lto:diego.r.lopez@telefonica.com" target=3D"_blank" rel=3D"noreferrer"><spa=
n lang=3D"ES" style=3D"color:#0563c1">diego.r.lopez@telefonica.com</span></=
a></span><span lang=3D"ES" style=3D"font-size:10.0pt"><u></u><u></u></span>=
</p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB" style=3D"font-size:10.0pt">Tel:=
=C2=A0=C2=A0=C2=A0 =C2=A0=C2=A0=C2=A0=C2=A0 +34 913 129 041<u></u><u></u></=
span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB" style=3D"font-size:10.0pt">Mobi=
le: =C2=A0+34 682 051 091<u></u><u></u></span></p>
</div>
<p class=3D"MsoNormal"><span lang=3D"EN-GB" style=3D"font-size:10.0pt">----=
------------------------------</span><span style=3D"font-size:10.0pt"><u></=
u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt"><u></u>=C2=A0<u></u=
></span></p>
<div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:.5in">On 22/09/2020, 18:01, &qu=
ot;Linda Dunbar&quot; &lt;<a href=3D"mailto:linda.dunbar@futurewei.com" tar=
get=3D"_blank" rel=3D"noreferrer">linda.dunbar@futurewei.com</a>&gt; wrote:=
<u></u><u></u></p>
</div>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:.5in"><u></u>=C2=A0<u></u></p>
</div>
<p class=3D"MsoNormal" style=3D"margin-left:.5in">Diego: <u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in">=C2=A0<u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in">Thank you very much for t=
he reflection of the Capabilities Information Model Draft. Agree with your =
statement that =E2=80=9Cthe capability data model was evolving in a quite r=
easonable and pragmatic way, including running
 code at the hackathons=E2=80=9D. <u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in">=C2=A0<u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in">Looks like Eric Vyncke st=
ill wants the information model to be fixed to clear his =E2=80=9CDISCUSS=
=E2=80=9D ballot.
<u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in">How about the following s=
teps:<u></u><u></u></p>
<p class=3D"m_3697213585076377193MsoListParagraph" style=3D"margin-left:1.0=
in">
<u></u><span>-<span style=3D"font:7.0pt &quot;Times New Roman&quot;">=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0
</span></span><u></u>Ask Roman=E2=80=99s advice if we can simplify the Info=
rmation Model mainly to reflect what has been in the Data Model.<u></u><u><=
/u></p>
<p class=3D"m_3697213585076377193MsoListParagraph" style=3D"margin-left:1.0=
in">
<u></u><span>-<span style=3D"font:7.0pt &quot;Times New Roman&quot;">=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0
</span></span><u></u>Or, drop the Information model draft and remove the re=
fence to the draft, but Roman has to convince Eric to agree not having the =
information model.
<u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in">=C2=A0<u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in">What do you think? <u></u=
><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in">=C2=A0<u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in">Linda<u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in">=C2=A0<u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in">=C2=A0<u></u><u></u></p>
<div>
<div style=3D"border:none;border-top:solid #e1e1e1 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal" style=3D"margin-left:.5in"><b>From:</b> Diego R. Lop=
ez &lt;<a href=3D"mailto:diego.r.lopez@telefonica.com" target=3D"_blank" re=
l=3D"noreferrer">diego.r.lopez@telefonica.com</a>&gt;
<br>
<b>Sent:</b> Tuesday, September 22, 2020 9:50 AM<br>
<b>To:</b> Mr. Jaehoon Paul Jeong &lt;<a href=3D"mailto:jaehoon.paul@gmail.=
com" target=3D"_blank" rel=3D"noreferrer">jaehoon.paul@gmail.com</a>&gt;; L=
inda Dunbar &lt;<a href=3D"mailto:linda.dunbar@futurewei.com" target=3D"_bl=
ank" rel=3D"noreferrer">linda.dunbar@futurewei.com</a>&gt;<br>
<b>Cc:</b> Xialiang (Frank) &lt;<a href=3D"mailto:frank.xialiang@huawei.com=
" target=3D"_blank" rel=3D"noreferrer">frank.xialiang@huawei.com</a>&gt;; Y=
oav Nir &lt;<a href=3D"mailto:ynir.ietf@gmail.com" target=3D"_blank" rel=3D=
"noreferrer">ynir.ietf@gmail.com</a>&gt;; John Strassner &lt;<a href=3D"mai=
lto:John.sc.Strassner@huawei.com" target=3D"_blank" rel=3D"noreferrer">John=
.sc.Strassner@huawei.com</a>&gt;;
 Aldo Basile &lt;<a href=3D"mailto:cataldo.basile@polito.it" target=3D"_bla=
nk" rel=3D"noreferrer">cataldo.basile@polito.it</a>&gt;; Roman Danyliw &lt;=
<a href=3D"mailto:rdd@cert.org" target=3D"_blank" rel=3D"noreferrer">rdd@ce=
rt.org</a>&gt;<br>
<b>Subject:</b> Re: Offer for Revision Help for I2NSF NSFs Capabilities Inf=
ormation Model Draft<u></u><u></u></p>
</div>
</div>
<p class=3D"MsoNormal" style=3D"margin-left:.5in">=C2=A0<u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in"><span class=3D"m_36972135=
85076377193EmailStyle21"><span style=3D"font-size:10.0pt">H</span></span><s=
pan class=3D"m_3697213585076377193EmailStyle21"><span lang=3D"ES" style=3D"=
font-size:10.0pt">i Paul,</span></span><u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in"><span class=3D"m_36972135=
85076377193EmailStyle21"><span lang=3D"ES" style=3D"font-size:10.0pt">=C2=
=A0</span></span><u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in"><span class=3D"m_36972135=
85076377193EmailStyle21"><span style=3D"font-size:10.0pt">Before you go for=
 it, let me share with you some reflections on the state of the draft, in t=
he spirit of what I replied to Eric Vyncke.</span></span><u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in"><span class=3D"m_36972135=
85076377193EmailStyle21"><span style=3D"font-size:10.0pt">=C2=A0</span></sp=
an><u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in"><span style=3D"font-size:=
10.0pt">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=E2=80=99s comments with=
out totally rewriting most, if not all, of the document.=C2=A0 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 mo=
del, 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 inf=
o model draft.</span><u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in"><span style=3D"font-size:=
10.0pt">=C2=A0</span><u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in"><span style=3D"font-size:=
10.0pt">As I told Eric, I believe the current capability model has a powerf=
ul (though probably not yet complete) calculus for policy description and v=
alidation,
 but not directly related to the management mechanisms addressed in the cap=
ability data model and the other data models produced in I2NSF. I believe t=
here 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 con=
solidate and therefore imply an extension of the I2NSF lifetime. I would li=
ke to know your position(*) about such an extension, =C2=A0that could also =
become an opportunity to work in other
 matters related to attestation (in the light of the work in RATS and the M=
UD initiative within the Ops Area) and accounting.</span><u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in"><span style=3D"font-size:=
10.0pt">=C2=A0</span><u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in"><span style=3D"font-size:=
10.0pt">Be goode,</span><u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in"><span style=3D"font-size:=
10.0pt">=C2=A0</span><u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in"><span style=3D"font-size:=
10.0pt">(*) I assume you are in favor, Paul. But I=E2=80=99d like to get Li=
nda=E2=80=99s, Yoav=E2=80=99s and Roman=E2=80=99s ideas, as well as the ava=
ilability to work on this from Frank, John
 and Aldo.</span><u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in"><span style=3D"font-size:=
10.0pt">=C2=A0</span><u></u><u></u></p>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:.5in"><span style=3D"font-size:=
10.0pt">--</span><u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in"><span lang=3D"ES" style=
=3D"font-size:10.0pt">&quot;Esta vez no fallaremos, Doctor Infierno&quot;</=
span><u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in"><span lang=3D"ES" style=
=3D"font-size:10.0pt">=C2=A0</span><u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in"><span lang=3D"ES" style=
=3D"font-size:10.0pt">Dr Diego R. Lopez</span><u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in"><span lang=3D"ES" style=
=3D"font-size:10.0pt">Telefonica I+D</span><u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in"><span lang=3D"ES" style=
=3D"font-size:10.0pt"><a href=3D"https://nam11.safelinks.protection.outlook=
.com/?url=3Dhttps%3A%2F%2Fwww.linkedin.com%2Fin%2Fdr2lopez%2F&amp;data=3D02=
%7C01%7Clinda.dunbar%40futurewei.com%7C08a48858d7bd4d843a6e08d85f47b438%7C0=
fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C637364108864949633&amp;sdata=3DRO=
R4%2FyD1WqWDb1rCbJx3ERqTiMCQ92ibkyz26kYZdD8%3D&amp;reserved=3D0" target=3D"=
_blank" rel=3D"noreferrer"><span style=3D"color:#0563c1">https://www.linked=
in.com/in/dr2lopez/</span></a>=C2=A0</span><u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in"><span lang=3D"ES" style=
=3D"font-size:10.0pt">=C2=A0</span><u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in"><span lang=3D"ES" style=
=3D"font-size:10.0pt">e-mail:=C2=A0</span><span lang=3D"EN-GB" style=3D"fon=
t-size:10.0pt"><a href=3D"mailto:diego.r.lopez@telefonica.com" target=3D"_b=
lank" rel=3D"noreferrer"><span lang=3D"ES" style=3D"color:#0563c1">diego.r.=
lopez@telefonica.com</span></a></span><u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in"><span lang=3D"EN-GB" styl=
e=3D"font-size:10.0pt">Tel:=C2=A0=C2=A0=C2=A0 =C2=A0=C2=A0=C2=A0=C2=A0 +34 =
913 129 041</span><u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in"><span lang=3D"EN-GB" styl=
e=3D"font-size:10.0pt">Mobile: =C2=A0+34 682 051 091</span><u></u><u></u></=
p>
</div>
<p class=3D"MsoNormal" style=3D"margin-left:.5in"><span lang=3D"EN-GB" styl=
e=3D"font-size:10.0pt">----------------------------------</span><u></u><u><=
/u></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in"><span style=3D"font-size:=
10.0pt">=C2=A0</span><u></u><u></u></p>
<div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:1.0in">On 17/09/2020, 01:42, &q=
uot;Mr. Jaehoon Paul Jeong&quot; &lt;<a href=3D"mailto:jaehoon.paul@gmail.c=
om" target=3D"_blank" rel=3D"noreferrer">jaehoon.paul@gmail.com</a>&gt; wro=
te:<u></u><u></u></p>
</div>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:1.0in">=C2=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:1.0in">Hi Linda,<u></u><u></u><=
/p>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:1.0in">I will address our AD Ro=
man&#39;s comments on this NSFs capabilities information draft as the 2nd e=
ditor through the collaboration with Frank (the 1st editor) and the other a=
uthors.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:1.0in">=C2=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:1.0in">I CC our AD Roman and th=
e other authors, such as John and Cataldo.<u></u><u></u></p>
</div>
<div>
<pre style=3D"margin-left:1.0in"><span style=3D"font-size:9.5pt">=C2=A0</sp=
an><u></u><u></u></pre>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:1.0in">Thanks for your support =
and guidance.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:1.0in">=C2=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:1.0in">Best Regards,<u></u><u><=
/u></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:1.0in">Paul<u></u><u></u></p>
</div>
</div>
<p class=3D"MsoNormal" style=3D"margin-left:1.0in">=C2=A0<u></u><u></u></p>
<div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:1.0in">2020<span lang=3D"ZH-CN"=
 style=3D"font-family:&quot;Malgun Gothic&quot;,sans-serif">=EB=85=84</span=
> 9<span lang=3D"ZH-CN" style=3D"font-family:&quot;Malgun Gothic&quot;,sans=
-serif">=EC=9B=94</span> 17<span lang=3D"ZH-CN" style=3D"font-family:&quot;=
Malgun Gothic&quot;,sans-serif">=EC=9D=BC</span>
 (<span lang=3D"ZH-CN" style=3D"font-family:&quot;Malgun Gothic&quot;,sans-=
serif">=EB=AA=A9</span>) <span lang=3D"ZH-CN" style=3D"font-family:&quot;Ma=
lgun Gothic&quot;,sans-serif">
=EC=98=A4=EC=A0=84</span><span lang=3D"ZH-CN"> </span>3:44, Linda Dunbar &l=
t;<a href=3D"mailto:linda.dunbar@futurewei.com" target=3D"_blank" rel=3D"no=
referrer">linda.dunbar@futurewei.com</a>&gt;<span lang=3D"ZH-CN" style=3D"f=
ont-family:&quot;Malgun Gothic&quot;,sans-serif">=EB=8B=98=EC=9D=B4</span><=
span lang=3D"ZH-CN">
</span><span lang=3D"ZH-CN" style=3D"font-family:&quot;Malgun Gothic&quot;,=
sans-serif">=EC=9E=91=EC=84=B1</span>:<u></u><u></u></p>
</div>
<blockquote style=3D"border:none;border-left:solid #cccccc 1.0pt;padding:0i=
n 0in 0in 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0in;margin-=
bottom:5.0pt">
<div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:1.0in">
Paul, <u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:1.0in">
=C2=A0<u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:1.0in">
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 h=
as been over a year since the AD comments were given.=C2=A0 We need to move=
 the draft forward. Therefore, I2NSF
 chairs have authorized you to be one of the editors to address the AD comm=
ents and revise the draft.
<u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:1.0in">
=C2=A0<u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:1.0in">
=C2=A0<u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:1.0in">
Thank you very much. <u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:1.0in">
=C2=A0<u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:1.0in">
Linda &amp; Yoav<u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:1.0in">
=C2=A0<u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:1.0in">
=C2=A0<u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:1.0in">
<b>From:</b> Mr. Jaehoon Paul Jeong &lt;<a href=3D"mailto:jaehoon.paul@gmai=
l.com" target=3D"_blank" rel=3D"noreferrer">jaehoon.paul@gmail.com</a>&gt;
<br>
<b>Sent:</b> Sunday, September 13, 2020 10:09 AM<br>
<b>To:</b> Xialiang (Frank) &lt;<a href=3D"mailto:frank.xialiang@huawei.com=
" target=3D"_blank" rel=3D"noreferrer">frank.xialiang@huawei.com</a>&gt;<br=
>
<b>Cc:</b> Linda Dunbar &lt;<a href=3D"mailto:linda.dunbar@futurewei.com" t=
arget=3D"_blank" rel=3D"noreferrer">linda.dunbar@futurewei.com</a>&gt;; Yoa=
v Nir &lt;<a href=3D"mailto:ynir.ietf@gmail.com" target=3D"_blank" rel=3D"n=
oreferrer">ynir.ietf@gmail.com</a>&gt;; DIEGO LOPEZ GARCIA &lt;<a href=3D"m=
ailto:diego.r.lopez@telefonica.com" target=3D"_blank" rel=3D"noreferrer">di=
ego.r.lopez@telefonica.com</a>&gt;;
 Jaehoon Jeong &lt;<a href=3D"mailto:jaehoon.paul@gmail.com" target=3D"_bla=
nk" rel=3D"noreferrer">jaehoon.paul@gmail.com</a>&gt;<br>
<b>Subject:</b> Offer for Revision Help for I2NSF NSFs Capabilities Informa=
tion Model Draft<u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:1.0in">
=C2=A0<u></u><u></u></p>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:1.0in">
Hi Frank,<u></u><u></u></p>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:1.0in">
Could I help you to revise your information model draft for our AD Roman Da=
nyliw&#39;s review comments=C2=A0 as a co-editor?<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:1.0in">
<a href=3D"https://nam11.safelinks.protection.outlook.com/?url=3Dhttps%3A%2=
F%2Fdatatracker.ietf.org%2Fdoc%2Fdraft-ietf-i2nsf-capability%2F%3Finclude_t=
ext%3D1&amp;data=3D02%7C01%7Clinda.dunbar%40futurewei.com%7C08a48858d7bd4d8=
43a6e08d85f47b438%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C637364108864=
959626&amp;sdata=3DGUrbaYu2Q4N1YNUUet2oVRPqbynA78cSBTf%2FBeSCY44%3D&amp;res=
erved=3D0" target=3D"_blank" rel=3D"noreferrer">https://datatracker.ietf.or=
g/doc/draft-ietf-i2nsf-capability/?include_text=3D1</a><u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:1.0in">
=C2=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:1.0in">
As you know, I have finished our I2NSF data model drafts.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:1.0in">
=C2=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:1.0in">
I am happy to work on the revision with you in order to complete our I2NSF =
deliverables.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:1.0in">
=C2=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:1.0in">
Thanks.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:1.0in">
=C2=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:1.0in">
Best Regards,<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:1.0in">
Paul<u></u><u></u></p>
</div>
</div>
</div>
</div>
</blockquote>
</div>
<p class=3D"MsoNormal" style=3D"margin-left:.5in">=C2=A0<u></u><u></u></p>
<div style=3D"margin-left:.5in">
<div class=3D"MsoNormal" align=3D"center" style=3D"text-align:center">
<hr size=3D"1" width=3D"100%" align=3D"center">
</div>
</div>
<p class=3D"MsoNormal" style=3D"margin-left:.5in"><span style=3D"font-size:=
7.5pt;font-family:&quot;Arial&quot;,sans-serif;color:gray"><br>
Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, pu=
ede contener informaci=C3=B3n privilegiada o confidencial y es para uso exc=
lusivo de la persona o entidad de destino. Si no es usted. el destinatario =
indicado, queda notificado de que la
 lectura, utilizaci=C3=B3n, divulgaci=C3=B3n y/o copia sin autorizaci=C3=B3=
n puede estar prohibida en virtud de la legislaci=C3=B3n vigente. Si ha rec=
ibido este mensaje por error, le rogamos que nos lo comunique inmediatament=
e por esta misma v=C3=ADa y proceda a su destrucci=C3=B3n.<br>
<br>
The information contained in this transmission is privileged and confidenti=
al 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 y=
ou have received this transmission in error, do not read it. Please immedia=
tely reply to the sender that you have received this communication in error=
 and then delete it.<br>
<br>
Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinat=C3=A1=
rio, pode conter informa=C3=A7=C3=A3o privilegiada ou confidencial e =C3=A9=
 para uso exclusivo da pessoa ou entidade de destino. Se n=C3=A3o =C3=A9 vo=
ssa senhoria o destinat=C3=A1rio indicado, fica notificado de que a
 leitura, utiliza=C3=A7=C3=A3o, divulga=C3=A7=C3=A3o e/ou c=C3=B3pia sem au=
toriza=C3=A7=C3=A3o pode estar proibida em virtude da legisla=C3=A7=C3=A3o =
vigente. Se recebeu esta mensagem por erro, rogamos-lhe que nos o comunique=
 imediatamente por esta mesma via e proceda a sua destrui=C3=A7=C3=A3o</spa=
n><u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<div class=3D"MsoNormal" align=3D"center" style=3D"text-align:center">
<hr size=3D"2" width=3D"100%" align=3D"center">
</div>
<p class=3D"MsoNormal"><span style=3D"font-size:7.5pt;font-family:&quot;Ari=
al&quot;,sans-serif;color:gray"><br>
Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, pu=
ede contener informaci=C3=B3n privilegiada o confidencial y es para uso exc=
lusivo de la persona o entidad de destino. Si no es usted. el destinatario =
indicado, queda notificado de que la
 lectura, utilizaci=C3=B3n, divulgaci=C3=B3n y/o copia sin autorizaci=C3=B3=
n puede estar prohibida en virtud de la legislaci=C3=B3n vigente. Si ha rec=
ibido este mensaje por error, le rogamos que nos lo comunique inmediatament=
e por esta misma v=C3=ADa y proceda a su destrucci=C3=B3n.<br>
<br>
The information contained in this transmission is privileged and confidenti=
al 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 y=
ou have received this transmission in error, do not read it. Please immedia=
tely reply to the sender that you have received this communication in error=
 and then delete it.<br>
<br>
Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinat=C3=A1=
rio, pode conter informa=C3=A7=C3=A3o privilegiada ou confidencial e =C3=A9=
 para uso exclusivo da pessoa ou entidade de destino. Se n=C3=A3o =C3=A9 vo=
ssa senhoria o destinat=C3=A1rio indicado, fica notificado de que a
 leitura, utiliza=C3=A7=C3=A3o, divulga=C3=A7=C3=A3o e/ou c=C3=B3pia sem au=
toriza=C3=A7=C3=A3o pode estar proibida em virtude da legisla=C3=A7=C3=A3o =
vigente. Se recebeu esta mensagem por erro, rogamos-lhe que nos o comunique=
 imediatamente por esta mesma via e proceda a sua destrui=C3=A7=C3=A3o</spa=
n><u></u><u></u></p>
</div>
</div>

_______________________________________________<br>
I2nsf mailing list<br>
<a href=3D"mailto:I2nsf@ietf.org" target=3D"_blank" rel=3D"noreferrer">I2ns=
f@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/i2nsf" rel=3D"noreferrer n=
oreferrer" target=3D"_blank">https://www.ietf.org/mailman/listinfo/i2nsf</a=
><br>
</blockquote></div></div></div>

--000000000000aa53b805b1468314--


From nobody Fri Oct  9 18:20:54 2020
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 011743A16CB for <i2nsf@ietfa.amsl.com>; Fri,  9 Oct 2020 18:20:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.335
X-Spam-Level: 
X-Spam-Status: No, score=0.335 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=2.331, MIME_QP_LONG_LINE=0.001, 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 CwvWfqi87of6 for <i2nsf@ietfa.amsl.com>; Fri,  9 Oct 2020 18:20:50 -0700 (PDT)
Received: from mail-ot1-x32d.google.com (mail-ot1-x32d.google.com [IPv6:2607:f8b0:4864:20::32d]) (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 C10C23A16CA for <i2nsf@ietf.org>; Fri,  9 Oct 2020 18:20:49 -0700 (PDT)
Received: by mail-ot1-x32d.google.com with SMTP id m13so10638992otl.9 for <i2nsf@ietf.org>; Fri, 09 Oct 2020 18:20:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=content-transfer-encoding:from:mime-version:subject:date:message-id :references:cc:in-reply-to:to; bh=Jasj/DJLTnu0/Az746qzzvrgNXhWL9g5ZABxkVlHs0c=; b=p/Gq+6A0/61HRkxjIHc24H/uTqQ7RJB0AH3IL4OjPGOHQkovnEwPgRT2Z88QXdwVmT 3ZKxFDxRv6h+646/FRTkq3vnz4RE+gLcutNd0wwyOE28Tsz1FYq9mFhNpI4rtgNeKzJf OLxFRFlfwPiZ/RoWaybsSs9boCLm3SjdRJ41NI//TZoIUq3c05eWtNGh7cFqpAmlC7zh vX6MUYHFx9sJe5215dqYsVUc5NF7OlZ15Mrz1TU4wa7+l/vzXz31DygwI+Y+sfpIILtM 1tRqbHhZriMRCMbmO87GWtW8xSZXTImhHg6Qpxj3kHdNafAkP10d8mvTrNbldAl6Toff uStQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:content-transfer-encoding:from:mime-version :subject:date:message-id:references:cc:in-reply-to:to; bh=Jasj/DJLTnu0/Az746qzzvrgNXhWL9g5ZABxkVlHs0c=; b=VRy45TrHrr5P4MvHpFH1pPuUYvgTfyjNMbFnDhySfyJMMCZUos6mS6r0eRDlkGn1r1 0QWGGx7p5Rd/Thm0sVgvqMjL1wL6SLiPNveff5xvONGJtqJBuJnt7dMsQ8aKohg7mAbq r807r8QpLVg3COmlPpN/BpZ2kXCq7i2+HZjEkiefO6YKql7YY89dw/rcPtMoK4f5sSgy PLxBqUsKJUoEb6k3vWkkY8YqgY9V4NBkC03y4wOtzB5ss4i9jAf1UZGFHpz9SajlnnD3 J6RYlIaARP0xcIJvmBPxZhxiBei6GA7ioGPlzyiEIFc+kpR6JNccFjrGNmMRuaknCBPh cS2A==
X-Gm-Message-State: AOAM532zf6nMhSOOWvYHdjWMLdajSBPXPppLQgCD2M3mMsYSZ5PRoI3q gzMRS6v9bW0wbEnMjIIMdZk=
X-Google-Smtp-Source: ABdhPJzoK9YPQ29pMV/u/K/B9RYrXmq9N406itGRCXY1A1zunKjXemtES27vcPzuAM/vFVbLNjobvg==
X-Received: by 2002:a9d:6acc:: with SMTP id m12mr9985931otq.95.1602292848938;  Fri, 09 Oct 2020 18:20:48 -0700 (PDT)
Received: from ?IPv6:2607:fb90:4456:e44a:5087:d6cf:ef82:2157? ([2607:fb90:4456:e44a:5087:d6cf:ef82:2157]) by smtp.gmail.com with ESMTPSA id 15sm7961777ooy.36.2020.10.09.18.20.47 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 09 Oct 2020 18:20:47 -0700 (PDT)
Content-Type: multipart/alternative; boundary=Apple-Mail-BC3396EB-1C7D-4D52-BE71-1547FADAF566
Content-Transfer-Encoding: 7bit
From: Linda <dunbar.ll@gmail.com>
Mime-Version: 1.0 (1.0)
Date: Fri, 9 Oct 2020 20:20:46 -0500
Message-Id: <6DBEDEEF-2EE4-49AF-A7F0-A257499C34F8@gmail.com>
References: <CAPK2DewMACWfR50824XEvfjMQPF7jcyTKAN7npiXnFvPHGT7OA@mail.gmail.com>
Cc: Linda Dunbar <linda.dunbar@futurewei.com>, i2nsf@ietf.org, skku-iotlab-members <skku-iotlab-members@googlegroups.com>
In-Reply-To: <CAPK2DewMACWfR50824XEvfjMQPF7jcyTKAN7npiXnFvPHGT7OA@mail.gmail.com>
To: "Mr. Jaehoon Paul Jeong" <jaehoon.paul@gmail.com>
X-Mailer: iPhone Mail (17G80)
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2nsf/JEPuoO7eHroIO_wa1-hCGmCZ2yo>
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, 10 Oct 2020 01:20:53 -0000

--Apple-Mail-BC3396EB-1C7D-4D52-BE71-1547FADAF566
Content-Type: text/plain;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable

Yes=20
Linda

Sent from my iPhone

> On Oct 9, 2020, at 7:55 PM, Mr. Jaehoon Paul Jeong <jaehoon.paul@gmail.com=
> wrote:
>=20
> =EF=BB=BF
> Hi Linda,
> As I understand, I need to merge the relevant contents of the NSFs Capabil=
ity Information Model Draft into the I2NSF NSF Capability Data Model Draft.
>=20
> Is it correct?
>=20
> Thanks.
>=20
> Best Regards,
> Paul
>=20
> 2020=EB=85=84 10=EC=9B=94 9=EC=9D=BC (=EA=B8=88) =EC=98=A4=ED=9B=84 11:58,=
 Linda Dunbar <linda.dunbar@futurewei.com>=EB=8B=98=EC=9D=B4 =EC=9E=91=EC=84=
=B1:
>> I2NSF WG,
>>=20
>> =20
>>=20
>> Correction:
>>=20
>> =20
>>=20
>> There has been NO object to the Author=E2=80=99s request for sunsetting t=
he draft-ietf-i2nsf-capability-5.
>>=20
>> =20
>>=20
>> We have marked the draft as =E2=80=9CDEAD=E2=80=9D in the WG status.
>>=20
>> =20
>>=20
>> Many thanks to the authors for putting the effort in this draft for kicks=
tarting all the data models in I2NSF WG.
>>=20
>> =20
>>=20
>> Linda & Yoav
>>=20
>> =20
>>=20
>> From: Linda Dunbar=20
>> Sent: Thursday, October 8, 2020 4:36 PM
>> To: i2nsf@ietf.org
>> Subject: draft-ietf-i2nsf-capability-05 is officially removed from I2NSF W=
G ( was RE: Is there any objection of sunset the I2NSF Capabilities Informat=
ion Model Draft and merge the relevant information to the I2NSF Capability D=
ata model draft?
>>=20
>> =20
>>=20
>> I2nsf WG,
>>=20
>> =20
>>=20
>> There has been any objection to the Author=E2=80=99s request for sunsetti=
ng the  draft-ietf-i2nsf-capability-05.
>>=20
>> =20
>>=20
>> Authors of the draft-ietf-i2nsf-capability-data-model: please remove the r=
eference to the Capability Information Model and upload a new draft. We can a=
sk IESG to re-review it.
>>=20
>> =20
>>=20
>> Thank you very much.
>>=20
>> =20
>>=20
>> Linda & Yoav.
>>=20
>> =20
>>=20
>> From: Linda Dunbar=20
>> Sent: Monday, September 28, 2020 11:00 AM
>> To: i2nsf@ietf.org
>> Subject: Is there any objection of sunset the I2NSF Capabilities Informat=
ion Model Draft and merge the relevant information to the I2NSF Capability D=
ata model draft?
>>=20
>> =20
>>=20
>> I2NSF WG,
>>=20
>> =20
>>=20
>> As Diego has expressed that the original I2NSF capability information mod=
el was based on a policy expression calculus suitable for manipulating high-=
level policy expressions.  The capability data model has been evolving in a q=
uite reasonable and pragmatic way, including running code at the hackathons.=

>>=20
>> =20
>>=20
>> The I2NSF Capability Information Model has fulfilled its purpose of kicks=
tarting and guiding the data model, and the authors believe that it is bette=
r to let the capability information model to be withdrawn. For the content i=
n the information model still relevant to I2NSF Capability Data Model, they s=
hould be merged into the Capability Data Model.
>>=20
>> =20
>>=20
>> Is there any objection from the WG?  If we don=E2=80=99t hear any objecti=
on by Oct 5, we will change the status of the draft.
>>=20
>> =20
>>=20
>> Cheers,                                                                  =
                   =20
>>=20
>> =20
>>=20
>> Linda & Yoav
>>=20
>> =20
>>=20
>> =20
>>=20
>> =20
>>=20
>> From: Diego R. Lopez <diego.r.lopez@telefonica.com>=20
>> Sent: Tuesday, September 22, 2020 5:35 PM
>> To: Linda Dunbar <linda.dunbar@futurewei.com>; Mr. Jaehoon Paul Jeong <ja=
ehoon.paul@gmail.com>
>> Cc: Xialiang (Frank) <frank.xialiang@huawei.com>; Yoav Nir <ynir.ietf@gma=
il.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 Informat=
ion Model Draft
>>=20
>> =20
>>=20
>> Hi Linda,
>>=20
>> =20
>>=20
>> I=E2=80=99d prefer the second option, as it seems more straightforward an=
d natural to me, and in parallel would like you to consider the idea of an I=
2NSF extension allowing us to reuse the capability model for policy-control t=
ransformation, and to incorporate the attestation matters you know I was so m=
uch interested in.
>>=20
>> =20
>>=20
>> Be goode,
>>=20
>> =20
>>=20
>> --
>>=20
>> "Esta vez no fallaremos, Doctor Infierno"
>>=20
>> =20
>>=20
>> Dr Diego R. Lopez
>>=20
>> Telefonica I+D
>>=20
>> https://www.linkedin.com/in/dr2lopez/=20
>>=20
>> =20
>>=20
>> e-mail: diego.r.lopez@telefonica.com
>>=20
>> Tel:         +34 913 129 041
>>=20
>> Mobile:  +34 682 051 091
>>=20
>> ----------------------------------
>>=20
>> =20
>>=20
>> On 22/09/2020, 18:01, "Linda Dunbar" <linda.dunbar@futurewei.com> wrote:
>>=20
>> =20
>>=20
>> Diego:
>>=20
>> =20
>>=20
>> Thank you very much for the reflection of the Capabilities Information Mo=
del Draft. Agree with your statement that =E2=80=9Cthe capability data model=
 was evolving in a quite reasonable and pragmatic way, including running cod=
e at the hackathons=E2=80=9D.
>>=20
>> =20
>>=20
>> Looks like Eric Vyncke still wants the information model to be fixed to c=
lear his =E2=80=9CDISCUSS=E2=80=9D ballot.
>>=20
>> How about the following steps:
>>=20
>> -          Ask Roman=E2=80=99s advice if we can simplify the Information M=
odel mainly to reflect what has been in the Data Model.
>>=20
>> -          Or, drop the Information model draft and remove the refence to=
 the draft, but Roman has to convince Eric to agree not having the informati=
on model.
>>=20
>> =20
>>=20
>> What do you think?
>>=20
>> =20
>>=20
>> Linda
>>=20
>> =20
>>=20
>> =20
>>=20
>> From: Diego R. Lopez <diego.r.lopez@telefonica.com>=20
>> 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@gma=
il.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 Informat=
ion Model Draft
>>=20
>> =20
>>=20
>> Hi Paul,
>>=20
>> =20
>>=20
>> 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.
>>=20
>> =20
>>=20
>> I must confess there has been a combination of events that made me think t=
he best solution was to leave this draft to fade away. First, I was not (hav=
e not been yet) able to find a solution to most of Roman=E2=80=99s comments w=
ithout totally rewriting most, if not all, of the document.  Second, the fac=
t that the capability data model was evolving in a quite reasonable and prag=
matic 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 bec=
ause I have been looking for a way to make the idea of bridging capability d=
eclarations and security policy statements at the I2NSF controller viable, a=
nd I was hoping to find such a way by reusing part of the capability info mo=
del draft.
>>=20
>> =20
>>=20
>> As I told Eric, I believe the current capability model has a powerful (th=
ough probably not yet complete) calculus for policy description and validati=
on, but not directly related to the management mechanisms addressed in the c=
apability data model and the other data models produced in I2NSF. I believe t=
here is an opportunity for accomplishing policy-capability bridging, using a=
s foundation the current capability model, though it seems to me that this t=
ask would require some time to consolidate and therefore imply an extension o=
f the I2NSF lifetime. I would like to know your position(*) about such an ex=
tension,  that could also become an opportunity to work in other matters rel=
ated to attestation (in the light of the work in RATS and the MUD initiative=
 within the Ops Area) and accounting.
>>=20
>> =20
>>=20
>> Be goode,
>>=20
>> =20
>>=20
>> (*) I assume you are in favor, Paul. But I=E2=80=99d like to get Linda=E2=
=80=99s, Yoav=E2=80=99s and Roman=E2=80=99s ideas, as well as the availabili=
ty to work on this from Frank, John and Aldo.
>>=20
>> =20
>>=20
>> --
>>=20
>> "Esta vez no fallaremos, Doctor Infierno"
>>=20
>> =20
>>=20
>> Dr Diego R. Lopez
>>=20
>> Telefonica I+D
>>=20
>> https://www.linkedin.com/in/dr2lopez/=20
>>=20
>> =20
>>=20
>> e-mail: diego.r.lopez@telefonica.com
>>=20
>> Tel:         +34 913 129 041
>>=20
>> Mobile:  +34 682 051 091
>>=20
>> ----------------------------------
>>=20
>> =20
>>=20
>> On 17/09/2020, 01:42, "Mr. Jaehoon Paul Jeong" <jaehoon.paul@gmail.com> w=
rote:
>>=20
>> =20
>>=20
>> Hi Linda,
>>=20
>> I will address our AD Roman's comments on this NSFs capabilities informat=
ion draft as the 2nd editor through the collaboration with Frank (the 1st ed=
itor) and the other authors.
>>=20
>> =20
>>=20
>> I CC our AD Roman and the other authors, such as John and Cataldo.
>>=20
>> =20
>> Thanks for your support and guidance.
>>=20
>> =20
>>=20
>> Best Regards,
>>=20
>> Paul
>>=20
>> =20
>>=20
>> 2020=EB=85=84 9=EC=9B=94 17=EC=9D=BC (=EB=AA=A9) =EC=98=A4=EC=A0=84 3:44,=
 Linda Dunbar <linda.dunbar@futurewei.com>=EB=8B=98=EC=9D=B4 =EC=9E=91=EC=84=
=B1:
>>=20
>> Paul,
>>=20
>> =20
>>=20
>> 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 h=
as been over a year since the AD comments were given.  We need to move the d=
raft forward. Therefore, I2NSF chairs have authorized you to be one of the e=
ditors to address the AD comments and revise the draft.
>>=20
>> =20
>>=20
>> =20
>>=20
>> Thank you very much.
>>=20
>> =20
>>=20
>> Linda & Yoav
>>=20
>> =20
>>=20
>> =20
>>=20
>> From: Mr. Jaehoon Paul Jeong <jaehoon.paul@gmail.com>=20
>> 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 <jaeh=
oon.paul@gmail.com>
>> Subject: Offer for Revision Help for I2NSF NSFs Capabilities Information M=
odel Draft
>>=20
>> =20
>>=20
>> Hi Frank,
>>=20
>> Could I help you to revise your information model draft for our AD Roman D=
anyliw's review comments  as a co-editor?
>>=20
>> https://datatracker.ietf.org/doc/draft-ietf-i2nsf-capability/?include_tex=
t=3D1
>>=20
>> =20
>>=20
>> As you know, I have finished our I2NSF data model drafts.
>>=20
>> =20
>>=20
>> I am happy to work on the revision with you in order to complete our I2NS=
F deliverables.
>>=20
>> =20
>>=20
>> Thanks.
>>=20
>> =20
>>=20
>> Best Regards,
>>=20
>> Paul
>>=20
>> =20
>>=20
>>=20
>> Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, p=
uede contener informaci=C3=B3n privilegiada o confidencial y es para uso exc=
lusivo de la persona o entidad de destino. Si no es usted. el destinatario i=
ndicado, queda notificado de que la lectura, utilizaci=C3=B3n, divulgaci=C3=B3=
n y/o copia sin autorizaci=C3=B3n puede estar prohibida en virtud de la legi=
slaci=C3=B3n vigente. Si ha recibido este mensaje por error, le rogamos que n=
os lo comunique inmediatamente por esta misma v=C3=ADa y proceda a su destru=
cci=C3=B3n.
>>=20
>> The information contained in this transmission is privileged and confiden=
tial 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 com=
munication 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.
>>=20
>> Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinat=C3=A1=
rio, pode conter informa=C3=A7=C3=A3o privilegiada ou confidencial e =C3=A9 p=
ara uso exclusivo da pessoa ou entidade de destino. Se n=C3=A3o =C3=A9 vossa=
 senhoria o destinat=C3=A1rio indicado, fica notificado de que a leitura, ut=
iliza=C3=A7=C3=A3o, divulga=C3=A7=C3=A3o e/ou c=C3=B3pia sem autoriza=C3=A7=C3=
=A3o pode estar proibida em virtude da legisla=C3=A7=C3=A3o vigente. Se rece=
beu esta mensagem por erro, rogamos-lhe que nos o comunique imediatamente po=
r esta mesma via e proceda a sua destrui=C3=A7=C3=A3o
>>=20
>> =20
>>=20
>>=20
>> Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, p=
uede contener informaci=C3=B3n privilegiada o confidencial y es para uso exc=
lusivo de la persona o entidad de destino. Si no es usted. el destinatario i=
ndicado, queda notificado de que la lectura, utilizaci=C3=B3n, divulgaci=C3=B3=
n y/o copia sin autorizaci=C3=B3n puede estar prohibida en virtud de la legi=
slaci=C3=B3n vigente. Si ha recibido este mensaje por error, le rogamos que n=
os lo comunique inmediatamente por esta misma v=C3=ADa y proceda a su destru=
cci=C3=B3n.
>>=20
>> The information contained in this transmission is privileged and confiden=
tial 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 com=
munication 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.
>>=20
>> Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinat=C3=A1=
rio, pode conter informa=C3=A7=C3=A3o privilegiada ou confidencial e =C3=A9 p=
ara uso exclusivo da pessoa ou entidade de destino. Se n=C3=A3o =C3=A9 vossa=
 senhoria o destinat=C3=A1rio indicado, fica notificado de que a leitura, ut=
iliza=C3=A7=C3=A3o, divulga=C3=A7=C3=A3o e/ou c=C3=B3pia sem autoriza=C3=A7=C3=
=A3o pode estar proibida em virtude da legisla=C3=A7=C3=A3o vigente. Se rece=
beu esta mensagem por erro, rogamos-lhe que nos o comunique imediatamente po=
r esta mesma via e proceda a sua destrui=C3=A7=C3=A3o
>>=20
>> _______________________________________________
>> 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

--Apple-Mail-BC3396EB-1C7D-4D52-BE71-1547FADAF566
Content-Type: text/html;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable

<html><head><meta http-equiv=3D"content-type" content=3D"text/html; charset=3D=
utf-8"></head><body dir=3D"auto">Yes&nbsp;<div>Linda<br><br><div dir=3D"ltr"=
>Sent from my iPhone</div><div dir=3D"ltr"><br><blockquote type=3D"cite">On O=
ct 9, 2020, at 7:55 PM, Mr. Jaehoon Paul Jeong &lt;jaehoon.paul@gmail.com&gt=
; wrote:<br><br></blockquote></div><blockquote type=3D"cite"><div dir=3D"ltr=
">=EF=BB=BF<div dir=3D"auto"><div>Hi Linda,</div><div dir=3D"auto">As I unde=
rstand, I need to merge the relevant contents of the NSFs Capability Informa=
tion Model Draft into the I2NSF NSF Capability Data Model Draft.</div><div d=
ir=3D"auto"><br></div><div dir=3D"auto">Is it correct?</div><div dir=3D"auto=
"><br></div><div dir=3D"auto">Thanks.</div><div dir=3D"auto"><br></div><div d=
ir=3D"auto">Best Regards,</div><div dir=3D"auto">Paul</div><div dir=3D"auto"=
><br><div class=3D"gmail_quote" dir=3D"auto"><div dir=3D"ltr" class=3D"gmail=
_attr">2020=EB=85=84 10=EC=9B=94 9=EC=9D=BC (=EA=B8=88) =EC=98=A4=ED=9B=84 1=
1:58, Linda Dunbar &lt;<a href=3D"mailto:linda.dunbar@futurewei.com">linda.d=
unbar@futurewei.com</a>&gt;=EB=8B=98=EC=9D=B4 =EC=9E=91=EC=84=B1:<br></div><=
blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #=
ccc solid;padding-left:1ex">





<div lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"m_3697213585076377193WordSection1">
<p class=3D"MsoNormal">I2NSF WG, <u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p>
<p class=3D"MsoNormal">Correction: <u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p>
<p class=3D"MsoNormal">There has been NO object to the Author=E2=80=99s requ=
est for sunsetting the draft-ietf-i2nsf-capability-5.
<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p>
<p class=3D"MsoNormal">We have marked the draft as =E2=80=9CDEAD=E2=80=9D in=
 the WG status. <u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p>
<p class=3D"MsoNormal">Many thanks to the authors for putting the effort in t=
his draft for kickstarting all the data models in I2NSF WG.
<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p>
<p class=3D"MsoNormal">Linda &amp; Yoav<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p>
<div>
<div style=3D"border:none;border-top:solid #e1e1e1 1.0pt;padding:3.0pt 0in 0=
in 0in">
<p class=3D"MsoNormal"><b>From:</b> Linda Dunbar <br>
<b>Sent:</b> Thursday, October 8, 2020 4:36 PM<br>
<b>To:</b> <a href=3D"mailto:i2nsf@ietf.org" target=3D"_blank" rel=3D"norefe=
rrer">i2nsf@ietf.org</a><br>
<b>Subject:</b> draft-ietf-i2nsf-capability-05 is officially removed from I2=
NSF WG ( was RE: Is there any objection of sunset the I2NSF Capabilities Inf=
ormation Model Draft and merge the relevant information to the I2NSF Capabil=
ity Data model draft?
<u></u><u></u></p>
</div>
</div>
<p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p>
<p class=3D"MsoNormal">I2nsf WG, <u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p>
<p class=3D"MsoNormal">There has been any objection to the Author=E2=80=99s r=
equest for sunsetting the &nbsp;draft-ietf-i2nsf-capability-05.
<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p>
<p class=3D"MsoNormal">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.
<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p>
<p class=3D"MsoNormal">Thank you very much. <u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p>
<p class=3D"MsoNormal">Linda &amp; Yoav. <u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p>
<div>
<div style=3D"border:none;border-top:solid #e1e1e1 1.0pt;padding:3.0pt 0in 0=
in 0in">
<p class=3D"MsoNormal"><b>From:</b> Linda Dunbar <br>
<b>Sent:</b> Monday, September 28, 2020 11:00 AM<br>
<b>To:</b> <a href=3D"mailto:i2nsf@ietf.org" target=3D"_blank" rel=3D"norefe=
rrer">i2nsf@ietf.org</a><br>
<b>Subject:</b> Is there any objection of sunset the I2NSF Capabilities Info=
rmation Model Draft and merge the relevant information to the I2NSF Capabili=
ty Data model draft?
<u></u><u></u></p>
</div>
</div>
<p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p>
<p class=3D"MsoNormal">I2NSF WG, <u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p>
<p class=3D"MsoNormal">As Diego has expressed that the original I2NSF capabi=
lity information model was based on a policy expression calculus suitable fo=
r manipulating high-level policy expressions.&nbsp; The capability data mode=
l has been evolving in a quite reasonable
 and pragmatic way, including running code at the hackathons.<u></u><u></u><=
/p>
<p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p>
<p class=3D"MsoNormal">The I2NSF Capability Information Model has fulfilled i=
ts purpose of kickstarting and guiding the data model, and the authors belie=
ve 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 i=
nto the Capability Data Model.
<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p>
<p class=3D"MsoNormal">Is there any objection from the WG?&nbsp; If we don=E2=
=80=99t hear any objection by Oct 5, we will change the status of the draft.=

<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p>
<p class=3D"MsoNormal">Cheers, &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;
<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p>
<p class=3D"MsoNormal">Linda &amp; Yoav<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p>
<p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p>
<p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p>
<div>
<div style=3D"border:none;border-top:solid #e1e1e1 1.0pt;padding:3.0pt 0in 0=
in 0in">
<p class=3D"MsoNormal"><b>From:</b> Diego R. Lopez &lt;<a href=3D"mailto:die=
go.r.lopez@telefonica.com" target=3D"_blank" rel=3D"noreferrer">diego.r.lope=
z@telefonica.com</a>&gt;
<br>
<b>Sent:</b> Tuesday, September 22, 2020 5:35 PM<br>
<b>To:</b> Linda Dunbar &lt;<a href=3D"mailto:linda.dunbar@futurewei.com" ta=
rget=3D"_blank" rel=3D"noreferrer">linda.dunbar@futurewei.com</a>&gt;; Mr. J=
aehoon Paul Jeong &lt;<a href=3D"mailto:jaehoon.paul@gmail.com" target=3D"_b=
lank" rel=3D"noreferrer">jaehoon.paul@gmail.com</a>&gt;<br>
<b>Cc:</b> Xialiang (Frank) &lt;<a href=3D"mailto:frank.xialiang@huawei.com"=
 target=3D"_blank" rel=3D"noreferrer">frank.xialiang@huawei.com</a>&gt;; Yoa=
v Nir &lt;<a href=3D"mailto:ynir.ietf@gmail.com" target=3D"_blank" rel=3D"no=
referrer">ynir.ietf@gmail.com</a>&gt;; John Strassner &lt;<a href=3D"mailto:=
John.sc.Strassner@huawei.com" target=3D"_blank" rel=3D"noreferrer">John.sc.S=
trassner@huawei.com</a>&gt;;
 Aldo Basile &lt;<a href=3D"mailto:cataldo.basile@polito.it" target=3D"_blan=
k" rel=3D"noreferrer">cataldo.basile@polito.it</a>&gt;; Roman Danyliw &lt;<a=
 href=3D"mailto:rdd@cert.org" target=3D"_blank" rel=3D"noreferrer">rdd@cert.=
org</a>&gt;<br>
<b>Subject:</b> Re: Offer for Revision Help for I2NSF NSFs Capabilities Info=
rmation Model Draft<u></u><u></u></p>
</div>
</div>
<p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p>
<p class=3D"MsoNormal"><span lang=3D"ES" style=3D"font-size:10.0pt">Hi Linda=
,<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"ES" style=3D"font-size:10.0pt"><u></u>&=
nbsp;<u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt">I=E2=80=99d prefer t=
he 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 a=
ttestation matters you know I was so much interested in.<u></u><u></u></span=
></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt"><u></u>&nbsp;<u></u>=
</span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt">Be goode,<u></u><u><=
/u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt"><u></u>&nbsp;<u></u>=
</span></p>
<div>
<p class=3D"MsoNormal"><span lang=3D"ES" style=3D"font-size:10.0pt">--<u></u=
><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"ES" style=3D"font-size:10.0pt">"Esta ve=
z no fallaremos, Doctor Infierno"<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"ES" style=3D"font-size:10.0pt">&nbsp;<u=
></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"ES" style=3D"font-size:10.0pt">Dr Diego=
 R. Lopez<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"ES" style=3D"font-size:10.0pt">Telefoni=
ca I+D<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"ES" style=3D"font-size:10.0pt"><a href=3D=
"https://nam11.safelinks.protection.outlook.com/?url=3Dhttps%3A%2F%2Fwww.lin=
kedin.com%2Fin%2Fdr2lopez%2F&amp;data=3D02%7C01%7Clinda.dunbar%40futurewei.c=
om%7C08a48858d7bd4d843a6e08d85f47b438%7C0fee8ff2a3b240189c753a1d5591fedc%7C1=
%7C0%7C637364108864949633&amp;sdata=3DROR4%2FyD1WqWDb1rCbJx3ERqTiMCQ92ibkyz2=
6kYZdD8%3D&amp;reserved=3D0" target=3D"_blank" rel=3D"noreferrer"><span styl=
e=3D"color:#0563c1">https://www.linkedin.com/in/dr2lopez/</span></a>&nbsp;<u=
></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"ES" style=3D"font-size:10.0pt">&nbsp;<u=
></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"ES" style=3D"font-size:10.0pt">e-mail:&=
nbsp;</span><span lang=3D"EN-GB" style=3D"font-size:10.0pt"><a href=3D"mailt=
o:diego.r.lopez@telefonica.com" target=3D"_blank" rel=3D"noreferrer"><span l=
ang=3D"ES" style=3D"color:#0563c1">diego.r.lopez@telefonica.com</span></a></=
span><span lang=3D"ES" style=3D"font-size:10.0pt"><u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB" style=3D"font-size:10.0pt">Tel:&=
nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp; +34 913 129 041<u></u><u></u></sp=
an></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB" style=3D"font-size:10.0pt">Mobil=
e: &nbsp;+34 682 051 091<u></u><u></u></span></p>
</div>
<p class=3D"MsoNormal"><span lang=3D"EN-GB" style=3D"font-size:10.0pt">-----=
-----------------------------</span><span style=3D"font-size:10.0pt"><u></u>=
<u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt"><u></u>&nbsp;<u></u>=
</span></p>
<div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:.5in">On 22/09/2020, 18:01, "Lin=
da Dunbar" &lt;<a href=3D"mailto:linda.dunbar@futurewei.com" target=3D"_blan=
k" rel=3D"noreferrer">linda.dunbar@futurewei.com</a>&gt; wrote:<u></u><u></u=
></p>
</div>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:.5in"><u></u>&nbsp;<u></u></p>
</div>
<p class=3D"MsoNormal" style=3D"margin-left:.5in">Diego: <u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in">&nbsp;<u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in">Thank you very much for th=
e reflection of the Capabilities Information Model Draft. Agree with your st=
atement that =E2=80=9Cthe capability data model was evolving in a quite reas=
onable and pragmatic way, including running
 code at the hackathons=E2=80=9D. <u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in">&nbsp;<u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in">Looks like Eric Vyncke sti=
ll wants the information model to be fixed to clear his =E2=80=9CDISCUSS=E2=80=
=9D ballot.
<u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in">How about the following st=
eps:<u></u><u></u></p>
<p class=3D"m_3697213585076377193MsoListParagraph" style=3D"margin-left:1.0i=
n">
<u></u><span>-<span style=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span><u></u>Ask Roman=E2=80=99s advice if we can simplify the Infor=
mation Model mainly to reflect what has been in the Data Model.<u></u><u></u=
></p>
<p class=3D"m_3697213585076377193MsoListParagraph" style=3D"margin-left:1.0i=
n">
<u></u><span>-<span style=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span><u></u>Or, drop the Information model draft and remove the ref=
ence to the draft, but Roman has to convince Eric to agree not having the in=
formation model.
<u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in">&nbsp;<u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in">What do you think? <u></u>=
<u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in">&nbsp;<u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in">Linda<u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in">&nbsp;<u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in">&nbsp;<u></u><u></u></p>
<div>
<div style=3D"border:none;border-top:solid #e1e1e1 1.0pt;padding:3.0pt 0in 0=
in 0in">
<p class=3D"MsoNormal" style=3D"margin-left:.5in"><b>From:</b> Diego R. Lope=
z &lt;<a href=3D"mailto:diego.r.lopez@telefonica.com" target=3D"_blank" rel=3D=
"noreferrer">diego.r.lopez@telefonica.com</a>&gt;
<br>
<b>Sent:</b> Tuesday, September 22, 2020 9:50 AM<br>
<b>To:</b> Mr. Jaehoon Paul Jeong &lt;<a href=3D"mailto:jaehoon.paul@gmail.c=
om" target=3D"_blank" rel=3D"noreferrer">jaehoon.paul@gmail.com</a>&gt;; Lin=
da Dunbar &lt;<a href=3D"mailto:linda.dunbar@futurewei.com" target=3D"_blank=
" rel=3D"noreferrer">linda.dunbar@futurewei.com</a>&gt;<br>
<b>Cc:</b> Xialiang (Frank) &lt;<a href=3D"mailto:frank.xialiang@huawei.com"=
 target=3D"_blank" rel=3D"noreferrer">frank.xialiang@huawei.com</a>&gt;; Yoa=
v Nir &lt;<a href=3D"mailto:ynir.ietf@gmail.com" target=3D"_blank" rel=3D"no=
referrer">ynir.ietf@gmail.com</a>&gt;; John Strassner &lt;<a href=3D"mailto:=
John.sc.Strassner@huawei.com" target=3D"_blank" rel=3D"noreferrer">John.sc.S=
trassner@huawei.com</a>&gt;;
 Aldo Basile &lt;<a href=3D"mailto:cataldo.basile@polito.it" target=3D"_blan=
k" rel=3D"noreferrer">cataldo.basile@polito.it</a>&gt;; Roman Danyliw &lt;<a=
 href=3D"mailto:rdd@cert.org" target=3D"_blank" rel=3D"noreferrer">rdd@cert.=
org</a>&gt;<br>
<b>Subject:</b> Re: Offer for Revision Help for I2NSF NSFs Capabilities Info=
rmation Model Draft<u></u><u></u></p>
</div>
</div>
<p class=3D"MsoNormal" style=3D"margin-left:.5in">&nbsp;<u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in"><span class=3D"m_369721358=
5076377193EmailStyle21"><span style=3D"font-size:10.0pt">H</span></span><spa=
n class=3D"m_3697213585076377193EmailStyle21"><span lang=3D"ES" style=3D"fon=
t-size:10.0pt">i Paul,</span></span><u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in"><span class=3D"m_369721358=
5076377193EmailStyle21"><span lang=3D"ES" style=3D"font-size:10.0pt">&nbsp;<=
/span></span><u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in"><span class=3D"m_369721358=
5076377193EmailStyle21"><span style=3D"font-size:10.0pt">Before you go for i=
t, let me share with you some reflections on the state of the draft, in the s=
pirit of what I replied to Eric Vyncke.</span></span><u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in"><span class=3D"m_369721358=
5076377193EmailStyle21"><span style=3D"font-size:10.0pt">&nbsp;</span></span=
><u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in"><span style=3D"font-size:1=
0.0pt">I must confess there has been a combination of events that made me th=
ink 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=E2=80=99s comments witho=
ut totally rewriting most, if not all, of the document.&nbsp; Second, the fa=
ct that the capability data model was evolving in a quite reasonable and pra=
gmatic way, including running code at the
 hackathons, following the spirit of the initial work in the information mod=
el, but not attempting to align with its most recent evolution. If I have no=
t shared this position before is because I have been looking for a way to ma=
ke 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 m=
odel draft.</span><u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in"><span style=3D"font-size:1=
0.0pt">&nbsp;</span><u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in"><span style=3D"font-size:1=
0.0pt">As I told Eric, I believe the current capability model has a powerful=
 (though probably not yet complete) calculus for policy description and vali=
dation,
 but not directly related to the management mechanisms addressed in the capa=
bility data model and the other data models produced in I2NSF. I believe the=
re is an opportunity for accomplishing policy-capability bridging, using as f=
oundation the current capability
 model, though it seems to me that this task would require some time to cons=
olidate and therefore imply an extension of the I2NSF lifetime. I would like=
 to know your position(*) about such an extension, &nbsp;that could also bec=
ome an opportunity to work in other
 matters related to attestation (in the light of the work in RATS and the MU=
D initiative within the Ops Area) and accounting.</span><u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in"><span style=3D"font-size:1=
0.0pt">&nbsp;</span><u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in"><span style=3D"font-size:1=
0.0pt">Be goode,</span><u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in"><span style=3D"font-size:1=
0.0pt">&nbsp;</span><u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in"><span style=3D"font-size:1=
0.0pt">(*) I assume you are in favor, Paul. But I=E2=80=99d like to get Lind=
a=E2=80=99s, Yoav=E2=80=99s and Roman=E2=80=99s ideas, as well as the availa=
bility to work on this from Frank, John
 and Aldo.</span><u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in"><span style=3D"font-size:1=
0.0pt">&nbsp;</span><u></u><u></u></p>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:.5in"><span style=3D"font-size:1=
0.0pt">--</span><u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in"><span lang=3D"ES" style=3D=
"font-size:10.0pt">"Esta vez no fallaremos, Doctor Infierno"</span><u></u><u=
></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in"><span lang=3D"ES" style=3D=
"font-size:10.0pt">&nbsp;</span><u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in"><span lang=3D"ES" style=3D=
"font-size:10.0pt">Dr Diego R. Lopez</span><u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in"><span lang=3D"ES" style=3D=
"font-size:10.0pt">Telefonica I+D</span><u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in"><span lang=3D"ES" style=3D=
"font-size:10.0pt"><a href=3D"https://nam11.safelinks.protection.outlook.com=
/?url=3Dhttps%3A%2F%2Fwww.linkedin.com%2Fin%2Fdr2lopez%2F&amp;data=3D02%7C01=
%7Clinda.dunbar%40futurewei.com%7C08a48858d7bd4d843a6e08d85f47b438%7C0fee8ff=
2a3b240189c753a1d5591fedc%7C1%7C0%7C637364108864949633&amp;sdata=3DROR4%2FyD=
1WqWDb1rCbJx3ERqTiMCQ92ibkyz26kYZdD8%3D&amp;reserved=3D0" target=3D"_blank" r=
el=3D"noreferrer"><span style=3D"color:#0563c1">https://www.linkedin.com/in/=
dr2lopez/</span></a>&nbsp;</span><u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in"><span lang=3D"ES" style=3D=
"font-size:10.0pt">&nbsp;</span><u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in"><span lang=3D"ES" style=3D=
"font-size:10.0pt">e-mail:&nbsp;</span><span lang=3D"EN-GB" style=3D"font-si=
ze:10.0pt"><a href=3D"mailto:diego.r.lopez@telefonica.com" target=3D"_blank"=
 rel=3D"noreferrer"><span lang=3D"ES" style=3D"color:#0563c1">diego.r.lopez@=
telefonica.com</span></a></span><u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in"><span lang=3D"EN-GB" style=
=3D"font-size:10.0pt">Tel:&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp; +34 91=
3 129 041</span><u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in"><span lang=3D"EN-GB" style=
=3D"font-size:10.0pt">Mobile: &nbsp;+34 682 051 091</span><u></u><u></u></p>=

</div>
<p class=3D"MsoNormal" style=3D"margin-left:.5in"><span lang=3D"EN-GB" style=
=3D"font-size:10.0pt">----------------------------------</span><u></u><u></u=
></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in"><span style=3D"font-size:1=
0.0pt">&nbsp;</span><u></u><u></u></p>
<div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:1.0in">On 17/09/2020, 01:42, "Mr=
. Jaehoon Paul Jeong" &lt;<a href=3D"mailto:jaehoon.paul@gmail.com" target=3D=
"_blank" rel=3D"noreferrer">jaehoon.paul@gmail.com</a>&gt; wrote:<u></u><u><=
/u></p>
</div>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:1.0in">&nbsp;<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:1.0in">Hi Linda,<u></u><u></u></=
p>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:1.0in">I will address our AD Rom=
an's comments on this NSFs capabilities information draft as the 2nd editor t=
hrough the collaboration with Frank (the 1st editor) and the other authors.<=
u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:1.0in">&nbsp;<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:1.0in">I CC our AD Roman and the=
 other authors, such as John and Cataldo.<u></u><u></u></p>
</div>
<div>
<pre style=3D"margin-left:1.0in"><span style=3D"font-size:9.5pt">&nbsp;</spa=
n><u></u><u></u></pre>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:1.0in">Thanks for your support a=
nd guidance.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:1.0in">&nbsp;<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:1.0in">Best Regards,<u></u><u></=
u></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:1.0in">Paul<u></u><u></u></p>
</div>
</div>
<p class=3D"MsoNormal" style=3D"margin-left:1.0in">&nbsp;<u></u><u></u></p>
<div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:1.0in">2020<span lang=3D"ZH-CN" s=
tyle=3D"font-family:&quot;Malgun Gothic&quot;,sans-serif">=EB=85=84</span> 9=
<span lang=3D"ZH-CN" style=3D"font-family:&quot;Malgun Gothic&quot;,sans-ser=
if">=EC=9B=94</span> 17<span lang=3D"ZH-CN" style=3D"font-family:&quot;Malgu=
n Gothic&quot;,sans-serif">=EC=9D=BC</span>
 (<span lang=3D"ZH-CN" style=3D"font-family:&quot;Malgun Gothic&quot;,sans-s=
erif">=EB=AA=A9</span>) <span lang=3D"ZH-CN" style=3D"font-family:&quot;Malg=
un Gothic&quot;,sans-serif">
=EC=98=A4=EC=A0=84</span><span lang=3D"ZH-CN"> </span>3:44, Linda Dunbar &lt=
;<a href=3D"mailto:linda.dunbar@futurewei.com" target=3D"_blank" rel=3D"nore=
ferrer">linda.dunbar@futurewei.com</a>&gt;<span lang=3D"ZH-CN" style=3D"font=
-family:&quot;Malgun Gothic&quot;,sans-serif">=EB=8B=98=EC=9D=B4</span><span=
 lang=3D"ZH-CN">
</span><span lang=3D"ZH-CN" style=3D"font-family:&quot;Malgun Gothic&quot;,s=
ans-serif">=EC=9E=91=EC=84=B1</span>:<u></u><u></u></p>
</div>
<blockquote style=3D"border:none;border-left:solid #cccccc 1.0pt;padding:0in=
 0in 0in 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0in;margin-bo=
ttom:5.0pt">
<div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:1.0in">
Paul, <u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:1.0in">
&nbsp;<u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:1.0in">
Thank you very much for offering to address the AD comments to this draft. L=
ooks like the current authors are too busy to address those comments. It has=
 been over a year since the AD comments were given.&nbsp; We need to move th=
e draft forward. Therefore, I2NSF
 chairs have authorized you to be one of the editors to address the AD comme=
nts and revise the draft.
<u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:1.0in">
&nbsp;<u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:1.0in">
&nbsp;<u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:1.0in">
Thank you very much. <u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:1.0in">
&nbsp;<u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:1.0in">
Linda &amp; Yoav<u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:1.0in">
&nbsp;<u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:1.0in">
&nbsp;<u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:1.0in">
<b>From:</b> Mr. Jaehoon Paul Jeong &lt;<a href=3D"mailto:jaehoon.paul@gmail=
.com" target=3D"_blank" rel=3D"noreferrer">jaehoon.paul@gmail.com</a>&gt;
<br>
<b>Sent:</b> Sunday, September 13, 2020 10:09 AM<br>
<b>To:</b> Xialiang (Frank) &lt;<a href=3D"mailto:frank.xialiang@huawei.com"=
 target=3D"_blank" rel=3D"noreferrer">frank.xialiang@huawei.com</a>&gt;<br>
<b>Cc:</b> Linda Dunbar &lt;<a href=3D"mailto:linda.dunbar@futurewei.com" ta=
rget=3D"_blank" rel=3D"noreferrer">linda.dunbar@futurewei.com</a>&gt;; Yoav N=
ir &lt;<a href=3D"mailto:ynir.ietf@gmail.com" target=3D"_blank" rel=3D"noref=
errer">ynir.ietf@gmail.com</a>&gt;; DIEGO LOPEZ GARCIA &lt;<a href=3D"mailto=
:diego.r.lopez@telefonica.com" target=3D"_blank" rel=3D"noreferrer">diego.r.=
lopez@telefonica.com</a>&gt;;
 Jaehoon Jeong &lt;<a href=3D"mailto:jaehoon.paul@gmail.com" target=3D"_blan=
k" rel=3D"noreferrer">jaehoon.paul@gmail.com</a>&gt;<br>
<b>Subject:</b> Offer for Revision Help for I2NSF NSFs Capabilities Informat=
ion Model Draft<u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:1.0in">
&nbsp;<u></u><u></u></p>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:1.0in">
Hi Frank,<u></u><u></u></p>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:1.0in">
Could I help you to revise your information model draft for our AD Roman Dan=
yliw's review comments&nbsp; as a co-editor?<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:1.0in">
<a href=3D"https://nam11.safelinks.protection.outlook.com/?url=3Dhttps%3A%2F%=
2Fdatatracker.ietf.org%2Fdoc%2Fdraft-ietf-i2nsf-capability%2F%3Finclude_text=
%3D1&amp;data=3D02%7C01%7Clinda.dunbar%40futurewei.com%7C08a48858d7bd4d843a6=
e08d85f47b438%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C63736410886495962=
6&amp;sdata=3DGUrbaYu2Q4N1YNUUet2oVRPqbynA78cSBTf%2FBeSCY44%3D&amp;reserved=3D=
0" target=3D"_blank" rel=3D"noreferrer">https://datatracker.ietf.org/doc/dra=
ft-ietf-i2nsf-capability/?include_text=3D1</a><u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:1.0in">
&nbsp;<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:1.0in">
As you know, I have finished our I2NSF data model drafts.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:1.0in">
&nbsp;<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:1.0in">
I am happy to work on the revision with you in order to complete our I2NSF d=
eliverables.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:1.0in">
&nbsp;<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:1.0in">
Thanks.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:1.0in">
&nbsp;<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:1.0in">
Best Regards,<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:1.0in">
Paul<u></u><u></u></p>
</div>
</div>
</div>
</div>
</blockquote>
</div>
<p class=3D"MsoNormal" style=3D"margin-left:.5in">&nbsp;<u></u><u></u></p>
<div style=3D"margin-left:.5in">
<div class=3D"MsoNormal" align=3D"center" style=3D"text-align:center">
<hr size=3D"1" width=3D"100%" align=3D"center">
</div>
</div>
<p class=3D"MsoNormal" style=3D"margin-left:.5in"><span style=3D"font-size:7=
.5pt;font-family:&quot;Arial&quot;,sans-serif;color:gray"><br>
Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, pue=
de contener informaci=C3=B3n privilegiada o confidencial y es para uso exclu=
sivo de la persona o entidad de destino. Si no es usted. el destinatario ind=
icado, queda notificado de que la
 lectura, utilizaci=C3=B3n, divulgaci=C3=B3n y/o copia sin autorizaci=C3=B3n=
 puede estar prohibida en virtud de la legislaci=C3=B3n vigente. Si ha recib=
ido este mensaje por error, le rogamos que nos lo comunique inmediatamente p=
or esta misma v=C3=ADa y proceda a su destrucci=C3=B3n.<br>
<br>
The information contained in this transmission is privileged and confidentia=
l information intended only for the use of the individual or entity named ab=
ove. If the reader of this message is not the intended recipient, you are he=
reby notified that any dissemination,
 distribution or copying of this communication is strictly prohibited. If yo=
u have received this transmission in error, do not read it. Please immediate=
ly reply to the sender that you have received this communication in error an=
d then delete it.<br>
<br>
Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinat=C3=A1r=
io, pode conter informa=C3=A7=C3=A3o privilegiada ou confidencial e =C3=A9 p=
ara uso exclusivo da pessoa ou entidade de destino. Se n=C3=A3o =C3=A9 vossa=
 senhoria o destinat=C3=A1rio indicado, fica notificado de que a
 leitura, utiliza=C3=A7=C3=A3o, divulga=C3=A7=C3=A3o e/ou c=C3=B3pia sem aut=
oriza=C3=A7=C3=A3o pode estar proibida em virtude da legisla=C3=A7=C3=A3o vi=
gente. Se recebeu esta mensagem por erro, rogamos-lhe que nos o comunique im=
ediatamente por esta mesma via e proceda a sua destrui=C3=A7=C3=A3o</span><u=
></u><u></u></p>
<p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p>
<div class=3D"MsoNormal" align=3D"center" style=3D"text-align:center">
<hr size=3D"2" width=3D"100%" align=3D"center">
</div>
<p class=3D"MsoNormal"><span style=3D"font-size:7.5pt;font-family:&quot;Aria=
l&quot;,sans-serif;color:gray"><br>
Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, pue=
de contener informaci=C3=B3n privilegiada o confidencial y es para uso exclu=
sivo de la persona o entidad de destino. Si no es usted. el destinatario ind=
icado, queda notificado de que la
 lectura, utilizaci=C3=B3n, divulgaci=C3=B3n y/o copia sin autorizaci=C3=B3n=
 puede estar prohibida en virtud de la legislaci=C3=B3n vigente. Si ha recib=
ido este mensaje por error, le rogamos que nos lo comunique inmediatamente p=
or esta misma v=C3=ADa y proceda a su destrucci=C3=B3n.<br>
<br>
The information contained in this transmission is privileged and confidentia=
l information intended only for the use of the individual or entity named ab=
ove. If the reader of this message is not the intended recipient, you are he=
reby notified that any dissemination,
 distribution or copying of this communication is strictly prohibited. If yo=
u have received this transmission in error, do not read it. Please immediate=
ly reply to the sender that you have received this communication in error an=
d then delete it.<br>
<br>
Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinat=C3=A1r=
io, pode conter informa=C3=A7=C3=A3o privilegiada ou confidencial e =C3=A9 p=
ara uso exclusivo da pessoa ou entidade de destino. Se n=C3=A3o =C3=A9 vossa=
 senhoria o destinat=C3=A1rio indicado, fica notificado de que a
 leitura, utiliza=C3=A7=C3=A3o, divulga=C3=A7=C3=A3o e/ou c=C3=B3pia sem aut=
oriza=C3=A7=C3=A3o pode estar proibida em virtude da legisla=C3=A7=C3=A3o vi=
gente. Se recebeu esta mensagem por erro, rogamos-lhe que nos o comunique im=
ediatamente por esta mesma via e proceda a sua destrui=C3=A7=C3=A3o</span><u=
></u><u></u></p>
</div>
</div>

_______________________________________________<br>
I2nsf mailing list<br>
<a href=3D"mailto:I2nsf@ietf.org" target=3D"_blank" rel=3D"noreferrer">I2nsf=
@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/i2nsf" rel=3D"noreferrer no=
referrer" target=3D"_blank">https://www.ietf.org/mailman/listinfo/i2nsf</a><=
br>
</blockquote></div></div></div>
<span>_______________________________________________</span><br><span>I2nsf m=
ailing list</span><br><span>I2nsf@ietf.org</span><br><span>https://www.ietf.=
org/mailman/listinfo/i2nsf</span><br></div></blockquote></div></body></html>=

--Apple-Mail-BC3396EB-1C7D-4D52-BE71-1547FADAF566--


From nobody Fri Oct  9 18:33:23 2020
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 87A8C3A16E6 for <i2nsf@ietfa.amsl.com>; Fri,  9 Oct 2020 18:33:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.344
X-Spam-Level: 
X-Spam-Status: No, score=0.344 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=2.331, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_HK_NAME_FM_MR_MRS=0.01, 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 ZG5tE9ueWv-O for <i2nsf@ietfa.amsl.com>; Fri,  9 Oct 2020 18:33:18 -0700 (PDT)
Received: from mail-lj1-x236.google.com (mail-lj1-x236.google.com [IPv6:2a00:1450:4864:20::236]) (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 DBD1B3A110E for <i2nsf@ietf.org>; Fri,  9 Oct 2020 18:33:17 -0700 (PDT)
Received: by mail-lj1-x236.google.com with SMTP id 133so11307905ljj.0 for <i2nsf@ietf.org>; Fri, 09 Oct 2020 18:33:17 -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=GaIG+ZwI2xTRxKfm0VNOZTygkqkkhoAkIWIUf0Pkq1c=; b=iP27N/Md/nOihGP20r6x90yNiIPtoHMiqoOzksjz8GDh6xnoBm3IP8tZ8j+fe5q3Oo Fi++aGuUgOD6aNC6LzUn6nYndkY0nQdnGl1qJlWkH2iZJuy7YFagochyzynO7EeI8SK0 I9dUO7CXR+f0gWf/PYR7XNiS9Y4vL5FL85f/L+BjuYc9agDmCFvw26MIlt6gKj5MN5Wt Bm32CSGcgyv8f0fACs9DcKENQw8XbkzoN4LVKjTfSfu0r7ugLY6q70FfkleMUBCglMPV 2Bc11avUHBxR2w66MLkzUqNUxU0XOMFBy25whRrnBZLVoLP+lkKx9y9E6SACa5e6PH9q 1sTw==
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=GaIG+ZwI2xTRxKfm0VNOZTygkqkkhoAkIWIUf0Pkq1c=; b=pg3NI2QktLQjmbQvAJgG5tCcrg+M3zOALTs1h/d2KU7QIFrV6rYXjc+MEMQY23k8Wb S0jITYeml0Cc86kMB+ps0/9FFKL5fZor1hJPu/1au9qF3tvVvJR/LHC442esOlGsNCuc FIpYiBtpAM4WI34xSD2p78MRyFAPS/YL82JvFGbgrNp6CqmqInctk3gRXji5PO/OevlK QygGBH59kHDO/5FjkbRtAWu6vMLBkeTm1dMQLh3HwFp5w/Czu6XhP5FvTmaOAmfzwEiW yzbTGGlDvwgYpmulUtGKSDD8aCo7dwLCTtpdRKouHnIj5X71qVUjHr/zBb/lGZ5XDaXK Vs0Q==
X-Gm-Message-State: AOAM532PzTLf076FrzEmHiJXOd7jTKoXK1nf7DCshB7K0fTu0AjxuDRF 6w/tlHr1hFyWZ3Lf+z2BlIQihJvde4rOaVlVY/Y=
X-Google-Smtp-Source: ABdhPJzhg/xKVck7oBj5aVXIpMpx9S0sUVpFVXEiLiu/ApjAwFA2TUDzilKkB3Ac9LQcnY6eKSXLbD8EVCHJBKxwcCY=
X-Received: by 2002:a2e:5c83:: with SMTP id q125mr5801247ljb.387.1602293595810;  Fri, 09 Oct 2020 18:33:15 -0700 (PDT)
MIME-Version: 1.0
References: <CAPK2DewMACWfR50824XEvfjMQPF7jcyTKAN7npiXnFvPHGT7OA@mail.gmail.com> <6DBEDEEF-2EE4-49AF-A7F0-A257499C34F8@gmail.com>
In-Reply-To: <6DBEDEEF-2EE4-49AF-A7F0-A257499C34F8@gmail.com>
From: "Mr. Jaehoon Paul Jeong" <jaehoon.paul@gmail.com>
Date: Sat, 10 Oct 2020 10:33:06 +0900
Message-ID: <CAPK2DexF7qwLCYh_mCFiHVBPaT=ccX1TBTeRUt+w8sDNauGfPQ@mail.gmail.com>
To: Linda <dunbar.ll@gmail.com>
Cc: Linda Dunbar <linda.dunbar@futurewei.com>, i2nsf@ietf.org,  skku-iotlab-members <skku-iotlab-members@googlegroups.com>
Content-Type: multipart/alternative; boundary="0000000000009aad6e05b1470cf8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2nsf/d7WHQQhSxud7ZmPJ4nzeAy5Y-Nk>
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, 10 Oct 2020 01:33:22 -0000

--0000000000009aad6e05b1470cf8
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Linda,
I see.

I will do the merging.

Thanks.

Best Regards,
Paul

2020=EB=85=84 10=EC=9B=94 10=EC=9D=BC (=ED=86=A0) =EC=98=A4=EC=A0=84 10:20,=
 Linda <dunbar.ll@gmail.com>=EB=8B=98=EC=9D=B4 =EC=9E=91=EC=84=B1:

> Yes
> Linda
>
> Sent from my iPhone
>
> On Oct 9, 2020, at 7:55 PM, Mr. Jaehoon Paul Jeong <jaehoon.paul@gmail.co=
m>
> wrote:
>
> =EF=BB=BF
> 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 Mod=
el
> Draft.
>
> Is it correct?
>
> Thanks.
>
> Best Regards,
> Paul
>
> 2020=EB=85=84 10=EC=9B=94 9=EC=9D=BC (=EA=B8=88) =EC=98=A4=ED=9B=84 11:58=
, Linda Dunbar <linda.dunbar@futurewei.com>=EB=8B=98=EC=9D=B4 =EC=9E=91=EC=
=84=B1:
>
>> I2NSF WG,
>>
>>
>>
>> Correction:
>>
>>
>>
>> There has been NO object to the Author=E2=80=99s request for sunsetting =
the
>> draft-ietf-i2nsf-capability-5.
>>
>>
>>
>> We have marked the draft as =E2=80=9CDEAD=E2=80=9D 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 Capabiliti=
es
>> 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=E2=80=99s request for sunsett=
ing 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 manipulatin=
g
>> high-level policy expressions.  The capability data model has been evolv=
ing
>> 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=E2=80=99t hear any object=
ion 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=E2=80=99d prefer the second option, as it seems more straightforward a=
nd
>> 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 matter=
s
>> 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=3Dhttps%3A%2F%2Fwww=
.linkedin.com%2Fin%2Fdr2lopez%2F&data=3D02%7C01%7Clinda.dunbar%40futurewei.=
com%7C08a48858d7bd4d843a6e08d85f47b438%7C0fee8ff2a3b240189c753a1d5591fedc%7=
C1%7C0%7C637364108864949633&sdata=3DROR4%2FyD1WqWDb1rCbJx3ERqTiMCQ92ibkyz26=
kYZdD8%3D&reserved=3D0>
>>
>>
>>
>>
>> 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 =E2=80=9Cthe capability data=
 model was
>> evolving in a quite reasonable and pragmatic way, including running code=
 at
>> the hackathons=E2=80=9D.
>>
>>
>>
>> Looks like Eric Vyncke still wants the information model to be fixed to
>> clear his =E2=80=9CDISCUSS=E2=80=9D ballot.
>>
>> How about the following steps:
>>
>> -          Ask Roman=E2=80=99s 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 stat=
e
>> 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=E2=80=99s c=
omments
>> without totally rewriting most, if not all, of the document.  Second, th=
e
>> fact that the capability data model was evolving in a quite reasonable a=
nd
>> 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 addres=
sed
>> 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 se=
ems
>> to me that this task would require some time to consolidate and therefor=
e
>> imply an extension of the I2NSF lifetime. I would like to know your
>> position(*) about such an extension,  that could also become an opportun=
ity
>> to work in other matters related to attestation (in the light of the wor=
k
>> in RATS and the MUD initiative within the Ops Area) and accounting.
>>
>>
>>
>> Be goode,
>>
>>
>>
>> (*) I assume you are in favor, Paul. But I=E2=80=99d like to get Linda=
=E2=80=99s, Yoav=E2=80=99s
>> and Roman=E2=80=99s ideas, as well as the availability to work on this f=
rom 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=3Dhttps%3A%2F%2Fwww=
.linkedin.com%2Fin%2Fdr2lopez%2F&data=3D02%7C01%7Clinda.dunbar%40futurewei.=
com%7C08a48858d7bd4d843a6e08d85f47b438%7C0fee8ff2a3b240189c753a1d5591fedc%7=
C1%7C0%7C637364108864949633&sdata=3DROR4%2FyD1WqWDb1rCbJx3ERqTiMCQ92ibkyz26=
kYZdD8%3D&reserved=3D0>
>>
>>
>>
>>
>> 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=EB=85=84 9=EC=9B=94 17=EC=9D=BC (=EB=AA=A9) =EC=98=A4=EC=A0=84 3:44=
, Linda Dunbar <linda.dunbar@futurewei.com>=EB=8B=98=EC=9D=B4 =EC=9E=91=EC=
=84=B1:
>>
>> 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_te=
xt=3D1
>> <https://nam11.safelinks.protection.outlook.com/?url=3Dhttps%3A%2F%2Fdat=
atracker.ietf.org%2Fdoc%2Fdraft-ietf-i2nsf-capability%2F%3Finclude_text%3D1=
&data=3D02%7C01%7Clinda.dunbar%40futurewei.com%7C08a48858d7bd4d843a6e08d85f=
47b438%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C637364108864959626&sdat=
a=3DGUrbaYu2Q4N1YNUUet2oVRPqbynA78cSBTf%2FBeSCY44%3D&reserved=3D0>
>>
>>
>>
>> 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=C3=B3n privilegiada o confidencial y es para us=
o
>> exclusivo de la persona o entidad de destino. Si no es usted. el
>> destinatario indicado, queda notificado de que la lectura, utilizaci=C3=
=B3n,
>> divulgaci=C3=B3n y/o copia sin autorizaci=C3=B3n puede estar prohibida e=
n virtud de
>> la legislaci=C3=B3n vigente. Si ha recibido este mensaje por error, le r=
ogamos
>> que nos lo comunique inmediatamente por esta misma v=C3=ADa y proceda a =
su
>> destrucci=C3=B3n.
>>
>> 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 receiv=
ed
>> this transmission in error, do not read it. Please immediately reply to =
the
>> sender that you have received this communication in error and then delet=
e
>> it.
>>
>> Esta mensagem e seus anexos se dirigem exclusivamente ao seu
>> destinat=C3=A1rio, pode conter informa=C3=A7=C3=A3o privilegiada ou conf=
idencial e =C3=A9 para
>> uso exclusivo da pessoa ou entidade de destino. Se n=C3=A3o =C3=A9 vossa=
 senhoria o
>> destinat=C3=A1rio indicado, fica notificado de que a leitura, utiliza=C3=
=A7=C3=A3o,
>> divulga=C3=A7=C3=A3o e/ou c=C3=B3pia sem autoriza=C3=A7=C3=A3o pode esta=
r proibida em virtude da
>> legisla=C3=A7=C3=A3o vigente. Se recebeu esta mensagem por erro, rogamos=
-lhe que nos
>> o comunique imediatamente por esta mesma via e proceda a sua destrui=C3=
=A7=C3=A3o
>>
>>
>> ------------------------------
>>
>>
>> Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario,
>> puede contener informaci=C3=B3n privilegiada o confidencial y es para us=
o
>> exclusivo de la persona o entidad de destino. Si no es usted. el
>> destinatario indicado, queda notificado de que la lectura, utilizaci=C3=
=B3n,
>> divulgaci=C3=B3n y/o copia sin autorizaci=C3=B3n puede estar prohibida e=
n virtud de
>> la legislaci=C3=B3n vigente. Si ha recibido este mensaje por error, le r=
ogamos
>> que nos lo comunique inmediatamente por esta misma v=C3=ADa y proceda a =
su
>> destrucci=C3=B3n.
>>
>> 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 receiv=
ed
>> this transmission in error, do not read it. Please immediately reply to =
the
>> sender that you have received this communication in error and then delet=
e
>> it.
>>
>> Esta mensagem e seus anexos se dirigem exclusivamente ao seu
>> destinat=C3=A1rio, pode conter informa=C3=A7=C3=A3o privilegiada ou conf=
idencial e =C3=A9 para
>> uso exclusivo da pessoa ou entidade de destino. Se n=C3=A3o =C3=A9 vossa=
 senhoria o
>> destinat=C3=A1rio indicado, fica notificado de que a leitura, utiliza=C3=
=A7=C3=A3o,
>> divulga=C3=A7=C3=A3o e/ou c=C3=B3pia sem autoriza=C3=A7=C3=A3o pode esta=
r proibida em virtude da
>> legisla=C3=A7=C3=A3o vigente. Se recebeu esta mensagem por erro, rogamos=
-lhe que nos
>> o comunique imediatamente por esta mesma via e proceda a sua destrui=C3=
=A7=C3=A3o
>> _______________________________________________
>> 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
>
>

--0000000000009aad6e05b1470cf8
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto">Linda,<div dir=3D"auto">I see.</div><div dir=3D"auto"><br=
></div><div dir=3D"auto">I will do the merging.</div><div dir=3D"auto"><br>=
</div><div dir=3D"auto">Thanks.</div><div dir=3D"auto"><br></div><div dir=
=3D"auto">Best Regards,</div><div dir=3D"auto">Paul</div></div><br><div cla=
ss=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">2020=EB=85=84 10=
=EC=9B=94 10=EC=9D=BC (=ED=86=A0) =EC=98=A4=EC=A0=84 10:20, Linda &lt;<a hr=
ef=3D"mailto:dunbar.ll@gmail.com">dunbar.ll@gmail.com</a>&gt;=EB=8B=98=EC=
=9D=B4 =EC=9E=91=EC=84=B1:<br></div><blockquote class=3D"gmail_quote" style=
=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir=
=3D"auto">Yes=C2=A0<div>Linda<br><br><div dir=3D"ltr">Sent from my iPhone</=
div><div dir=3D"ltr"><br><blockquote type=3D"cite">On Oct 9, 2020, at 7:55 =
PM, Mr. Jaehoon Paul Jeong &lt;<a href=3D"mailto:jaehoon.paul@gmail.com" ta=
rget=3D"_blank" rel=3D"noreferrer">jaehoon.paul@gmail.com</a>&gt; wrote:<br=
><br></blockquote></div><blockquote type=3D"cite"><div dir=3D"ltr">=EF=BB=
=BF<div dir=3D"auto"><div>Hi Linda,</div><div dir=3D"auto">As I understand,=
 I need to merge the relevant contents of the NSFs Capability Information M=
odel Draft into the I2NSF NSF Capability Data Model Draft.</div><div dir=3D=
"auto"><br></div><div dir=3D"auto">Is it correct?</div><div dir=3D"auto"><b=
r></div><div dir=3D"auto">Thanks.</div><div dir=3D"auto"><br></div><div dir=
=3D"auto">Best Regards,</div><div dir=3D"auto">Paul</div><div dir=3D"auto">=
<br><div class=3D"gmail_quote" dir=3D"auto"><div dir=3D"ltr" class=3D"gmail=
_attr">2020=EB=85=84 10=EC=9B=94 9=EC=9D=BC (=EA=B8=88) =EC=98=A4=ED=9B=84 =
11:58, Linda Dunbar &lt;<a href=3D"mailto:linda.dunbar@futurewei.com" targe=
t=3D"_blank" rel=3D"noreferrer">linda.dunbar@futurewei.com</a>&gt;=EB=8B=98=
=EC=9D=B4 =EC=9E=91=EC=84=B1:<br></div><blockquote class=3D"gmail_quote" st=
yle=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">





<div lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div>
<p class=3D"MsoNormal">I2NSF WG, <u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">Correction: <u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">There has been NO object to the Author=E2=80=99s req=
uest for sunsetting the draft-ietf-i2nsf-capability-5.
<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">We have marked the draft as =E2=80=9CDEAD=E2=80=9D i=
n the WG status. <u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">Many thanks to the authors for putting the effort in=
 this draft for kickstarting all the data models in I2NSF WG.
<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">Linda &amp; Yoav<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<div>
<div style=3D"border:none;border-top:solid #e1e1e1 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b>From:</b> Linda Dunbar <br>
<b>Sent:</b> Thursday, October 8, 2020 4:36 PM<br>
<b>To:</b> <a href=3D"mailto:i2nsf@ietf.org" rel=3D"noreferrer noreferrer" =
target=3D"_blank">i2nsf@ietf.org</a><br>
<b>Subject:</b> draft-ietf-i2nsf-capability-05 is officially removed from I=
2NSF WG ( was RE: Is there any objection of sunset the I2NSF Capabilities I=
nformation Model Draft and merge the relevant information to the I2NSF Capa=
bility Data model draft?
<u></u><u></u></p>
</div>
</div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">I2nsf WG, <u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">There has been any objection to the Author=E2=80=99s=
 request for sunsetting the =C2=A0draft-ietf-i2nsf-capability-05.
<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">Authors of the draft-ietf-i2nsf-capability-data-mode=
l: please remove the reference to the Capability Information Model and uplo=
ad a new draft. We can ask IESG to re-review it.
<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">Thank you very much. <u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">Linda &amp; Yoav. <u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<div>
<div style=3D"border:none;border-top:solid #e1e1e1 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b>From:</b> Linda Dunbar <br>
<b>Sent:</b> Monday, September 28, 2020 11:00 AM<br>
<b>To:</b> <a href=3D"mailto:i2nsf@ietf.org" rel=3D"noreferrer noreferrer" =
target=3D"_blank">i2nsf@ietf.org</a><br>
<b>Subject:</b> Is there any objection of sunset the I2NSF Capabilities Inf=
ormation Model Draft and merge the relevant information to the I2NSF Capabi=
lity Data model draft?
<u></u><u></u></p>
</div>
</div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">I2NSF WG, <u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">As Diego has expressed that the original I2NSF capab=
ility information model was based on a policy expression calculus suitable =
for manipulating high-level policy expressions.=C2=A0 The capability data m=
odel has been evolving in a quite reasonable
 and pragmatic way, including running code at the hackathons.<u></u><u></u>=
</p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">The I2NSF Capability Information Model has fulfilled=
 its purpose of kickstarting and guiding the data model, and the authors be=
lieve that it is better to let the capability information model to be withd=
rawn. For the content in the information
 model still relevant to I2NSF Capability Data Model, they should be merged=
 into the Capability Data Model.
<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">Is there any objection from the WG?=C2=A0 If we don=
=E2=80=99t hear any objection by Oct 5, we will change the status of the dr=
aft.
<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">Cheers, =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0
<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">Linda &amp; Yoav<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<div>
<div style=3D"border:none;border-top:solid #e1e1e1 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b>From:</b> Diego R. Lopez &lt;<a href=3D"mailto:di=
ego.r.lopez@telefonica.com" rel=3D"noreferrer noreferrer" target=3D"_blank"=
>diego.r.lopez@telefonica.com</a>&gt;
<br>
<b>Sent:</b> Tuesday, September 22, 2020 5:35 PM<br>
<b>To:</b> Linda Dunbar &lt;<a href=3D"mailto:linda.dunbar@futurewei.com" r=
el=3D"noreferrer noreferrer" target=3D"_blank">linda.dunbar@futurewei.com</=
a>&gt;; Mr. Jaehoon Paul Jeong &lt;<a href=3D"mailto:jaehoon.paul@gmail.com=
" rel=3D"noreferrer noreferrer" target=3D"_blank">jaehoon.paul@gmail.com</a=
>&gt;<br>
<b>Cc:</b> Xialiang (Frank) &lt;<a href=3D"mailto:frank.xialiang@huawei.com=
" rel=3D"noreferrer noreferrer" target=3D"_blank">frank.xialiang@huawei.com=
</a>&gt;; Yoav Nir &lt;<a href=3D"mailto:ynir.ietf@gmail.com" rel=3D"norefe=
rrer noreferrer" target=3D"_blank">ynir.ietf@gmail.com</a>&gt;; John Strass=
ner &lt;<a href=3D"mailto:John.sc.Strassner@huawei.com" rel=3D"noreferrer n=
oreferrer" target=3D"_blank">John.sc.Strassner@huawei.com</a>&gt;;
 Aldo Basile &lt;<a href=3D"mailto:cataldo.basile@polito.it" rel=3D"norefer=
rer noreferrer" target=3D"_blank">cataldo.basile@polito.it</a>&gt;; Roman D=
anyliw &lt;<a href=3D"mailto:rdd@cert.org" rel=3D"noreferrer noreferrer" ta=
rget=3D"_blank">rdd@cert.org</a>&gt;<br>
<b>Subject:</b> Re: Offer for Revision Help for I2NSF NSFs Capabilities Inf=
ormation Model Draft<u></u><u></u></p>
</div>
</div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal"><span lang=3D"ES" style=3D"font-size:10.0pt">Hi Lind=
a,<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"ES" style=3D"font-size:10.0pt"><u></u>=
=C2=A0<u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt">I=E2=80=99d 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 allow=
ing us to reuse the
 capability model for policy-control transformation, and to incorporate the=
 attestation matters you know I was so much interested in.<u></u><u></u></s=
pan></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt"><u></u>=C2=A0<u></u=
></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt">Be goode,<u></u><u>=
</u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt"><u></u>=C2=A0<u></u=
></span></p>
<div>
<p class=3D"MsoNormal"><span lang=3D"ES" style=3D"font-size:10.0pt">--<u></=
u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"ES" style=3D"font-size:10.0pt">&quot;E=
sta vez no fallaremos, Doctor Infierno&quot;<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"ES" style=3D"font-size:10.0pt">=C2=A0<=
u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"ES" style=3D"font-size:10.0pt">Dr Dieg=
o R. Lopez<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"ES" style=3D"font-size:10.0pt">Telefon=
ica I+D<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"ES" style=3D"font-size:10.0pt"><a href=
=3D"https://nam11.safelinks.protection.outlook.com/?url=3Dhttps%3A%2F%2Fwww=
.linkedin.com%2Fin%2Fdr2lopez%2F&amp;data=3D02%7C01%7Clinda.dunbar%40future=
wei.com%7C08a48858d7bd4d843a6e08d85f47b438%7C0fee8ff2a3b240189c753a1d5591fe=
dc%7C1%7C0%7C637364108864949633&amp;sdata=3DROR4%2FyD1WqWDb1rCbJx3ERqTiMCQ9=
2ibkyz26kYZdD8%3D&amp;reserved=3D0" rel=3D"noreferrer noreferrer" target=3D=
"_blank"><span style=3D"color:#0563c1">https://www.linkedin.com/in/dr2lopez=
/</span></a>=C2=A0<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"ES" style=3D"font-size:10.0pt">=C2=A0<=
u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"ES" style=3D"font-size:10.0pt">e-mail:=
=C2=A0</span><span lang=3D"EN-GB" style=3D"font-size:10.0pt"><a href=3D"mai=
lto:diego.r.lopez@telefonica.com" rel=3D"noreferrer noreferrer" target=3D"_=
blank"><span lang=3D"ES" style=3D"color:#0563c1">diego.r.lopez@telefonica.c=
om</span></a></span><span lang=3D"ES" style=3D"font-size:10.0pt"><u></u><u>=
</u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB" style=3D"font-size:10.0pt">Tel:=
=C2=A0=C2=A0=C2=A0 =C2=A0=C2=A0=C2=A0=C2=A0 +34 913 129 041<u></u><u></u></=
span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB" style=3D"font-size:10.0pt">Mobi=
le: =C2=A0+34 682 051 091<u></u><u></u></span></p>
</div>
<p class=3D"MsoNormal"><span lang=3D"EN-GB" style=3D"font-size:10.0pt">----=
------------------------------</span><span style=3D"font-size:10.0pt"><u></=
u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt"><u></u>=C2=A0<u></u=
></span></p>
<div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:.5in">On 22/09/2020, 18:01, &qu=
ot;Linda Dunbar&quot; &lt;<a href=3D"mailto:linda.dunbar@futurewei.com" rel=
=3D"noreferrer noreferrer" target=3D"_blank">linda.dunbar@futurewei.com</a>=
&gt; wrote:<u></u><u></u></p>
</div>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:.5in"><u></u>=C2=A0<u></u></p>
</div>
<p class=3D"MsoNormal" style=3D"margin-left:.5in">Diego: <u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in">=C2=A0<u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in">Thank you very much for t=
he reflection of the Capabilities Information Model Draft. Agree with your =
statement that =E2=80=9Cthe capability data model was evolving in a quite r=
easonable and pragmatic way, including running
 code at the hackathons=E2=80=9D. <u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in">=C2=A0<u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in">Looks like Eric Vyncke st=
ill wants the information model to be fixed to clear his =E2=80=9CDISCUSS=
=E2=80=9D ballot.
<u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in">How about the following s=
teps:<u></u><u></u></p>
<p style=3D"margin-left:1.0in">
<u></u><span>-<span style=3D"font:7.0pt &quot;Times New Roman&quot;">=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0
</span></span><u></u>Ask Roman=E2=80=99s advice if we can simplify the Info=
rmation Model mainly to reflect what has been in the Data Model.<u></u><u><=
/u></p>
<p style=3D"margin-left:1.0in">
<u></u><span>-<span style=3D"font:7.0pt &quot;Times New Roman&quot;">=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0
</span></span><u></u>Or, drop the Information model draft and remove the re=
fence to the draft, but Roman has to convince Eric to agree not having the =
information model.
<u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in">=C2=A0<u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in">What do you think? <u></u=
><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in">=C2=A0<u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in">Linda<u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in">=C2=A0<u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in">=C2=A0<u></u><u></u></p>
<div>
<div style=3D"border:none;border-top:solid #e1e1e1 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal" style=3D"margin-left:.5in"><b>From:</b> Diego R. Lop=
ez &lt;<a href=3D"mailto:diego.r.lopez@telefonica.com" rel=3D"noreferrer no=
referrer" target=3D"_blank">diego.r.lopez@telefonica.com</a>&gt;
<br>
<b>Sent:</b> Tuesday, September 22, 2020 9:50 AM<br>
<b>To:</b> Mr. Jaehoon Paul Jeong &lt;<a href=3D"mailto:jaehoon.paul@gmail.=
com" rel=3D"noreferrer noreferrer" target=3D"_blank">jaehoon.paul@gmail.com=
</a>&gt;; Linda Dunbar &lt;<a href=3D"mailto:linda.dunbar@futurewei.com" re=
l=3D"noreferrer noreferrer" target=3D"_blank">linda.dunbar@futurewei.com</a=
>&gt;<br>
<b>Cc:</b> Xialiang (Frank) &lt;<a href=3D"mailto:frank.xialiang@huawei.com=
" rel=3D"noreferrer noreferrer" target=3D"_blank">frank.xialiang@huawei.com=
</a>&gt;; Yoav Nir &lt;<a href=3D"mailto:ynir.ietf@gmail.com" rel=3D"norefe=
rrer noreferrer" target=3D"_blank">ynir.ietf@gmail.com</a>&gt;; John Strass=
ner &lt;<a href=3D"mailto:John.sc.Strassner@huawei.com" rel=3D"noreferrer n=
oreferrer" target=3D"_blank">John.sc.Strassner@huawei.com</a>&gt;;
 Aldo Basile &lt;<a href=3D"mailto:cataldo.basile@polito.it" rel=3D"norefer=
rer noreferrer" target=3D"_blank">cataldo.basile@polito.it</a>&gt;; Roman D=
anyliw &lt;<a href=3D"mailto:rdd@cert.org" rel=3D"noreferrer noreferrer" ta=
rget=3D"_blank">rdd@cert.org</a>&gt;<br>
<b>Subject:</b> Re: Offer for Revision Help for I2NSF NSFs Capabilities Inf=
ormation Model Draft<u></u><u></u></p>
</div>
</div>
<p class=3D"MsoNormal" style=3D"margin-left:.5in">=C2=A0<u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in"><span><span style=3D"font=
-size:10.0pt">H</span></span><span><span lang=3D"ES" style=3D"font-size:10.=
0pt">i Paul,</span></span><u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in"><span><span lang=3D"ES" s=
tyle=3D"font-size:10.0pt">=C2=A0</span></span><u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in"><span><span style=3D"font=
-size:10.0pt">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.<=
/span></span><u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in"><span><span style=3D"font=
-size:10.0pt">=C2=A0</span></span><u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in"><span style=3D"font-size:=
10.0pt">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=E2=80=99s comments with=
out totally rewriting most, if not all, of the document.=C2=A0 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 mo=
del, 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 inf=
o model draft.</span><u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in"><span style=3D"font-size:=
10.0pt">=C2=A0</span><u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in"><span style=3D"font-size:=
10.0pt">As I told Eric, I believe the current capability model has a powerf=
ul (though probably not yet complete) calculus for policy description and v=
alidation,
 but not directly related to the management mechanisms addressed in the cap=
ability data model and the other data models produced in I2NSF. I believe t=
here 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 con=
solidate and therefore imply an extension of the I2NSF lifetime. I would li=
ke to know your position(*) about such an extension, =C2=A0that could also =
become an opportunity to work in other
 matters related to attestation (in the light of the work in RATS and the M=
UD initiative within the Ops Area) and accounting.</span><u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in"><span style=3D"font-size:=
10.0pt">=C2=A0</span><u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in"><span style=3D"font-size:=
10.0pt">Be goode,</span><u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in"><span style=3D"font-size:=
10.0pt">=C2=A0</span><u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in"><span style=3D"font-size:=
10.0pt">(*) I assume you are in favor, Paul. But I=E2=80=99d like to get Li=
nda=E2=80=99s, Yoav=E2=80=99s and Roman=E2=80=99s ideas, as well as the ava=
ilability to work on this from Frank, John
 and Aldo.</span><u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in"><span style=3D"font-size:=
10.0pt">=C2=A0</span><u></u><u></u></p>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:.5in"><span style=3D"font-size:=
10.0pt">--</span><u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in"><span lang=3D"ES" style=
=3D"font-size:10.0pt">&quot;Esta vez no fallaremos, Doctor Infierno&quot;</=
span><u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in"><span lang=3D"ES" style=
=3D"font-size:10.0pt">=C2=A0</span><u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in"><span lang=3D"ES" style=
=3D"font-size:10.0pt">Dr Diego R. Lopez</span><u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in"><span lang=3D"ES" style=
=3D"font-size:10.0pt">Telefonica I+D</span><u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in"><span lang=3D"ES" style=
=3D"font-size:10.0pt"><a href=3D"https://nam11.safelinks.protection.outlook=
.com/?url=3Dhttps%3A%2F%2Fwww.linkedin.com%2Fin%2Fdr2lopez%2F&amp;data=3D02=
%7C01%7Clinda.dunbar%40futurewei.com%7C08a48858d7bd4d843a6e08d85f47b438%7C0=
fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C637364108864949633&amp;sdata=3DRO=
R4%2FyD1WqWDb1rCbJx3ERqTiMCQ92ibkyz26kYZdD8%3D&amp;reserved=3D0" rel=3D"nor=
eferrer noreferrer" target=3D"_blank"><span style=3D"color:#0563c1">https:/=
/www.linkedin.com/in/dr2lopez/</span></a>=C2=A0</span><u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in"><span lang=3D"ES" style=
=3D"font-size:10.0pt">=C2=A0</span><u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in"><span lang=3D"ES" style=
=3D"font-size:10.0pt">e-mail:=C2=A0</span><span lang=3D"EN-GB" style=3D"fon=
t-size:10.0pt"><a href=3D"mailto:diego.r.lopez@telefonica.com" rel=3D"noref=
errer noreferrer" target=3D"_blank"><span lang=3D"ES" style=3D"color:#0563c=
1">diego.r.lopez@telefonica.com</span></a></span><u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in"><span lang=3D"EN-GB" styl=
e=3D"font-size:10.0pt">Tel:=C2=A0=C2=A0=C2=A0 =C2=A0=C2=A0=C2=A0=C2=A0 +34 =
913 129 041</span><u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in"><span lang=3D"EN-GB" styl=
e=3D"font-size:10.0pt">Mobile: =C2=A0+34 682 051 091</span><u></u><u></u></=
p>
</div>
<p class=3D"MsoNormal" style=3D"margin-left:.5in"><span lang=3D"EN-GB" styl=
e=3D"font-size:10.0pt">----------------------------------</span><u></u><u><=
/u></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in"><span style=3D"font-size:=
10.0pt">=C2=A0</span><u></u><u></u></p>
<div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:1.0in">On 17/09/2020, 01:42, &q=
uot;Mr. Jaehoon Paul Jeong&quot; &lt;<a href=3D"mailto:jaehoon.paul@gmail.c=
om" rel=3D"noreferrer noreferrer" target=3D"_blank">jaehoon.paul@gmail.com<=
/a>&gt; wrote:<u></u><u></u></p>
</div>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:1.0in">=C2=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:1.0in">Hi Linda,<u></u><u></u><=
/p>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:1.0in">I will address our AD Ro=
man&#39;s comments on this NSFs capabilities information draft as the 2nd e=
ditor through the collaboration with Frank (the 1st editor) and the other a=
uthors.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:1.0in">=C2=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:1.0in">I CC our AD Roman and th=
e other authors, such as John and Cataldo.<u></u><u></u></p>
</div>
<div>
<pre style=3D"margin-left:1.0in"><span style=3D"font-size:9.5pt">=C2=A0</sp=
an><u></u><u></u></pre>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:1.0in">Thanks for your support =
and guidance.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:1.0in">=C2=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:1.0in">Best Regards,<u></u><u><=
/u></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:1.0in">Paul<u></u><u></u></p>
</div>
</div>
<p class=3D"MsoNormal" style=3D"margin-left:1.0in">=C2=A0<u></u><u></u></p>
<div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:1.0in">2020<span lang=3D"ZH-CN"=
 style=3D"font-family:&quot;Malgun Gothic&quot;,sans-serif">=EB=85=84</span=
> 9<span lang=3D"ZH-CN" style=3D"font-family:&quot;Malgun Gothic&quot;,sans=
-serif">=EC=9B=94</span> 17<span lang=3D"ZH-CN" style=3D"font-family:&quot;=
Malgun Gothic&quot;,sans-serif">=EC=9D=BC</span>
 (<span lang=3D"ZH-CN" style=3D"font-family:&quot;Malgun Gothic&quot;,sans-=
serif">=EB=AA=A9</span>) <span lang=3D"ZH-CN" style=3D"font-family:&quot;Ma=
lgun Gothic&quot;,sans-serif">
=EC=98=A4=EC=A0=84</span><span lang=3D"ZH-CN"> </span>3:44, Linda Dunbar &l=
t;<a href=3D"mailto:linda.dunbar@futurewei.com" rel=3D"noreferrer noreferre=
r" target=3D"_blank">linda.dunbar@futurewei.com</a>&gt;<span lang=3D"ZH-CN"=
 style=3D"font-family:&quot;Malgun Gothic&quot;,sans-serif">=EB=8B=98=EC=9D=
=B4</span><span lang=3D"ZH-CN">
</span><span lang=3D"ZH-CN" style=3D"font-family:&quot;Malgun Gothic&quot;,=
sans-serif">=EC=9E=91=EC=84=B1</span>:<u></u><u></u></p>
</div>
<blockquote style=3D"border:none;border-left:solid #cccccc 1.0pt;padding:0i=
n 0in 0in 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0in;margin-=
bottom:5.0pt">
<div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:1.0in">
Paul, <u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:1.0in">
=C2=A0<u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:1.0in">
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 h=
as been over a year since the AD comments were given.=C2=A0 We need to move=
 the draft forward. Therefore, I2NSF
 chairs have authorized you to be one of the editors to address the AD comm=
ents and revise the draft.
<u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:1.0in">
=C2=A0<u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:1.0in">
=C2=A0<u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:1.0in">
Thank you very much. <u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:1.0in">
=C2=A0<u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:1.0in">
Linda &amp; Yoav<u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:1.0in">
=C2=A0<u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:1.0in">
=C2=A0<u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:1.0in">
<b>From:</b> Mr. Jaehoon Paul Jeong &lt;<a href=3D"mailto:jaehoon.paul@gmai=
l.com" rel=3D"noreferrer noreferrer" target=3D"_blank">jaehoon.paul@gmail.c=
om</a>&gt;
<br>
<b>Sent:</b> Sunday, September 13, 2020 10:09 AM<br>
<b>To:</b> Xialiang (Frank) &lt;<a href=3D"mailto:frank.xialiang@huawei.com=
" rel=3D"noreferrer noreferrer" target=3D"_blank">frank.xialiang@huawei.com=
</a>&gt;<br>
<b>Cc:</b> Linda Dunbar &lt;<a href=3D"mailto:linda.dunbar@futurewei.com" r=
el=3D"noreferrer noreferrer" target=3D"_blank">linda.dunbar@futurewei.com</=
a>&gt;; Yoav Nir &lt;<a href=3D"mailto:ynir.ietf@gmail.com" rel=3D"noreferr=
er noreferrer" target=3D"_blank">ynir.ietf@gmail.com</a>&gt;; DIEGO LOPEZ G=
ARCIA &lt;<a href=3D"mailto:diego.r.lopez@telefonica.com" rel=3D"noreferrer=
 noreferrer" target=3D"_blank">diego.r.lopez@telefonica.com</a>&gt;;
 Jaehoon Jeong &lt;<a href=3D"mailto:jaehoon.paul@gmail.com" rel=3D"norefer=
rer noreferrer" target=3D"_blank">jaehoon.paul@gmail.com</a>&gt;<br>
<b>Subject:</b> Offer for Revision Help for I2NSF NSFs Capabilities Informa=
tion Model Draft<u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:1.0in">
=C2=A0<u></u><u></u></p>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:1.0in">
Hi Frank,<u></u><u></u></p>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:1.0in">
Could I help you to revise your information model draft for our AD Roman Da=
nyliw&#39;s review comments=C2=A0 as a co-editor?<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:1.0in">
<a href=3D"https://nam11.safelinks.protection.outlook.com/?url=3Dhttps%3A%2=
F%2Fdatatracker.ietf.org%2Fdoc%2Fdraft-ietf-i2nsf-capability%2F%3Finclude_t=
ext%3D1&amp;data=3D02%7C01%7Clinda.dunbar%40futurewei.com%7C08a48858d7bd4d8=
43a6e08d85f47b438%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C637364108864=
959626&amp;sdata=3DGUrbaYu2Q4N1YNUUet2oVRPqbynA78cSBTf%2FBeSCY44%3D&amp;res=
erved=3D0" rel=3D"noreferrer noreferrer" target=3D"_blank">https://datatrac=
ker.ietf.org/doc/draft-ietf-i2nsf-capability/?include_text=3D1</a><u></u><u=
></u></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:1.0in">
=C2=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:1.0in">
As you know, I have finished our I2NSF data model drafts.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:1.0in">
=C2=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:1.0in">
I am happy to work on the revision with you in order to complete our I2NSF =
deliverables.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:1.0in">
=C2=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:1.0in">
Thanks.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:1.0in">
=C2=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:1.0in">
Best Regards,<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:1.0in">
Paul<u></u><u></u></p>
</div>
</div>
</div>
</div>
</blockquote>
</div>
<p class=3D"MsoNormal" style=3D"margin-left:.5in">=C2=A0<u></u><u></u></p>
<div style=3D"margin-left:.5in">
<div class=3D"MsoNormal" align=3D"center" style=3D"text-align:center">
<hr size=3D"1" width=3D"100%" align=3D"center">
</div>
</div>
<p class=3D"MsoNormal" style=3D"margin-left:.5in"><span style=3D"font-size:=
7.5pt;font-family:&quot;Arial&quot;,sans-serif;color:gray"><br>
Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, pu=
ede contener informaci=C3=B3n privilegiada o confidencial y es para uso exc=
lusivo de la persona o entidad de destino. Si no es usted. el destinatario =
indicado, queda notificado de que la
 lectura, utilizaci=C3=B3n, divulgaci=C3=B3n y/o copia sin autorizaci=C3=B3=
n puede estar prohibida en virtud de la legislaci=C3=B3n vigente. Si ha rec=
ibido este mensaje por error, le rogamos que nos lo comunique inmediatament=
e por esta misma v=C3=ADa y proceda a su destrucci=C3=B3n.<br>
<br>
The information contained in this transmission is privileged and confidenti=
al 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 y=
ou have received this transmission in error, do not read it. Please immedia=
tely reply to the sender that you have received this communication in error=
 and then delete it.<br>
<br>
Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinat=C3=A1=
rio, pode conter informa=C3=A7=C3=A3o privilegiada ou confidencial e =C3=A9=
 para uso exclusivo da pessoa ou entidade de destino. Se n=C3=A3o =C3=A9 vo=
ssa senhoria o destinat=C3=A1rio indicado, fica notificado de que a
 leitura, utiliza=C3=A7=C3=A3o, divulga=C3=A7=C3=A3o e/ou c=C3=B3pia sem au=
toriza=C3=A7=C3=A3o pode estar proibida em virtude da legisla=C3=A7=C3=A3o =
vigente. Se recebeu esta mensagem por erro, rogamos-lhe que nos o comunique=
 imediatamente por esta mesma via e proceda a sua destrui=C3=A7=C3=A3o</spa=
n><u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<div class=3D"MsoNormal" align=3D"center" style=3D"text-align:center">
<hr size=3D"2" width=3D"100%" align=3D"center">
</div>
<p class=3D"MsoNormal"><span style=3D"font-size:7.5pt;font-family:&quot;Ari=
al&quot;,sans-serif;color:gray"><br>
Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, pu=
ede contener informaci=C3=B3n privilegiada o confidencial y es para uso exc=
lusivo de la persona o entidad de destino. Si no es usted. el destinatario =
indicado, queda notificado de que la
 lectura, utilizaci=C3=B3n, divulgaci=C3=B3n y/o copia sin autorizaci=C3=B3=
n puede estar prohibida en virtud de la legislaci=C3=B3n vigente. Si ha rec=
ibido este mensaje por error, le rogamos que nos lo comunique inmediatament=
e por esta misma v=C3=ADa y proceda a su destrucci=C3=B3n.<br>
<br>
The information contained in this transmission is privileged and confidenti=
al 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 y=
ou have received this transmission in error, do not read it. Please immedia=
tely reply to the sender that you have received this communication in error=
 and then delete it.<br>
<br>
Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinat=C3=A1=
rio, pode conter informa=C3=A7=C3=A3o privilegiada ou confidencial e =C3=A9=
 para uso exclusivo da pessoa ou entidade de destino. Se n=C3=A3o =C3=A9 vo=
ssa senhoria o destinat=C3=A1rio indicado, fica notificado de que a
 leitura, utiliza=C3=A7=C3=A3o, divulga=C3=A7=C3=A3o e/ou c=C3=B3pia sem au=
toriza=C3=A7=C3=A3o pode estar proibida em virtude da legisla=C3=A7=C3=A3o =
vigente. Se recebeu esta mensagem por erro, rogamos-lhe que nos o comunique=
 imediatamente por esta mesma via e proceda a sua destrui=C3=A7=C3=A3o</spa=
n><u></u><u></u></p>
</div>
</div>

_______________________________________________<br>
I2nsf mailing list<br>
<a href=3D"mailto:I2nsf@ietf.org" rel=3D"noreferrer noreferrer" target=3D"_=
blank">I2nsf@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/i2nsf" rel=3D"noreferrer n=
oreferrer noreferrer" target=3D"_blank">https://www.ietf.org/mailman/listin=
fo/i2nsf</a><br>
</blockquote></div></div></div>
<span>_______________________________________________</span><br><span>I2nsf=
 mailing list</span><br><span><a href=3D"mailto:I2nsf@ietf.org" target=3D"_=
blank" rel=3D"noreferrer">I2nsf@ietf.org</a></span><br><span><a href=3D"htt=
ps://www.ietf.org/mailman/listinfo/i2nsf" target=3D"_blank" rel=3D"noreferr=
er">https://www.ietf.org/mailman/listinfo/i2nsf</a></span><br></div></block=
quote></div></div></blockquote></div>

--0000000000009aad6e05b1470cf8--


From nobody Mon Oct 12 09:02:37 2020
Return-Path: <rwilton@cisco.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 E68153A1590; Mon, 12 Oct 2020 09:02:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.597
X-Spam-Level: 
X-Spam-Status: No, score=-9.597 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, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com header.b=nFVudMF6; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=EsTOEfR9
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 eZ1LvKF2Ns08; Mon, 12 Oct 2020 09:02:32 -0700 (PDT)
Received: from alln-iport-2.cisco.com (alln-iport-2.cisco.com [173.37.142.89]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 49DB33A158C; Mon, 12 Oct 2020 09:02:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=23128; q=dns/txt; s=iport; t=1602518552; x=1603728152; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=R45xVfktmefBwhhK0WzB6liNpJ2XnaFJxl77VtlHXNY=; b=nFVudMF67vrUJe0K3yXtae1AtfmHQM2DUTyityP1pbITv321eGZkWINN AhptBLhVBKa96RawmNicSjLIri4qtNMegN55kT344zVWsouE1bEsP8XLJ jwnH0TGKP4DUZFi5i7F5gAl3yIP4JDqB0LEcgIhkOa7iqReBft+t4+WwC g=;
IronPort-PHdr: =?us-ascii?q?9a23=3Ac9/q4BcErTcNbEOI8s7gxFVVlGMj4e+mNxMJ6p?= =?us-ascii?q?chl7NFe7ii+JKnJkHE+PFxlwaQB9fa5u5Kze3MvPOoVW8B5MOHt3YPONxJWg?= =?us-ascii?q?QegMob1wonHIaeCEL9IfKrCk5yHMlLWFJ/uX3uN09TFZX/akHc5Hqo4m1aFh?= =?us-ascii?q?D2LwEgIOPzF8bbhNi20Obn/ZrVbk1IiTOxbKk0Ig+xqFDat9Idhs1pLaNixw?= =?us-ascii?q?=3D=3D?=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0DrCQBcfYRf/4kNJK1gHgEBCxIMgzI?= =?us-ascii?q?vUQdwWS8sCoQzg0YDjVCUDIRvglMDVQsBAQENAQEYAQoKAgQBAYRKAheBfwI?= =?us-ascii?q?lOBMCAwEBCwEBBQEBAQIBBgRthVwMhXIBAQEEAQEQEQoTAQEsCwEPAgEIEQQ?= =?us-ascii?q?BASQEAwICAiULFAkIAgQBDQUIEweDBYF+TQMuAQMLnEkCgTmIYXaBMoMBAQE?= =?us-ascii?q?FhQYYghADBoE4gnKDboZWG4FBP4FUgk0+glwBAQKBXxUWCYJhM4ILIpBagjQ?= =?us-ascii?q?8hwYmi1qRFAqCaI9bizChOpMioCUCBAIEBQIOAQEFgWsjKoEtcBU7gmlQFwI?= =?us-ascii?q?Njh83gzqFFIVCdAI1AgYBCQEBAwl8jDsBgRABAQ?=
X-IronPort-AV: E=Sophos;i="5.77,367,1596499200";  d="scan'208,217";a="580392982"
Received: from alln-core-4.cisco.com ([173.36.13.137]) by alln-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 12 Oct 2020 16:01:37 +0000
Received: from XCH-ALN-005.cisco.com (xch-aln-005.cisco.com [173.36.7.15]) by alln-core-4.cisco.com (8.15.2/8.15.2) with ESMTPS id 09CG1beJ027057 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Mon, 12 Oct 2020 16:01:37 GMT
Received: from xhs-aln-002.cisco.com (173.37.135.119) by XCH-ALN-005.cisco.com (173.36.7.15) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Mon, 12 Oct 2020 11:01:37 -0500
Received: from xhs-rtp-001.cisco.com (64.101.210.228) by xhs-aln-002.cisco.com (173.37.135.119) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Mon, 12 Oct 2020 11:01:37 -0500
Received: from NAM12-DM6-obe.outbound.protection.outlook.com (64.101.32.56) by xhs-rtp-001.cisco.com (64.101.210.228) with Microsoft SMTP Server (TLS) id 15.0.1497.2 via Frontend Transport; Mon, 12 Oct 2020 12:01:36 -0400
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=XaooTw1ffAT/ca8NF5bng5L4Ntj41HQIjj+nI9gxVSCO3KUiHItd1CaMyQvFscf8IbwrgiAF/Q9AXgVwABiTpMZNas47KpEKcSXG8+2+9PZYo5LCW185vywxVEPvvlLm+vhzzQ78LCSRvuhxZEjEiVKsm6fwgYzBe/OUtqoNKLj3pCRfzVe2XBVEHK9B5zWj5gYKCdToPkKc+dA55UvfoZpjzGhR4NK8f9U0oSZX25ji9NxQJBeWkh8oQFfph3/OwNgDFfQwzdBARoCJBshO0QSLck4/95gACaTlGKJFhAxe5kAmTgnPcshDVWmbfdzkSl0uR2YrlgponrTOK3A3UQ==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=R45xVfktmefBwhhK0WzB6liNpJ2XnaFJxl77VtlHXNY=; b=RH9Pnk/jo3bkRDVYEz/J3fo+ca/BLyryTvobCINpfCVOEFwJ1FiCjp/94eJ64OD6LsBLydjpgPzBQnlZDXbkEd8mI0/5KM7WOWnU/CVXuqlVJzBVjauMm0IYGdxmGBOcQE36nnQIH0YE1/RY00AYJFjXOaXBpL54M5dEPMoCCn8A/lKSO/+yEdF1BzT1fxr6KdA5Ku6tj+UU/3SwB5zMVi4Vr7wbPA8/cEJle+gl1YU3Bft1Dec42ycLuWQ8LLxkcmTIAN1Z/HeLwQMzDcgAHs46XxoH/MFNO6Rgfo5OH/0Il/GJsLvT6f5T3DVeI5RslB/a3JzpE4nCJt6NHQAvUw==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=cisco.com; dmarc=pass action=none header.from=cisco.com; dkim=pass header.d=cisco.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.onmicrosoft.com;  s=selector2-cisco-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=R45xVfktmefBwhhK0WzB6liNpJ2XnaFJxl77VtlHXNY=; b=EsTOEfR9eQuTCo1j0PFQ6AvxqNc1NmKNVxvVJdz5NQ3Tv4mdVdqp6iXsXgntPGFcBKol/FrGTeScb6Df7Q+XKOEksedsFXcRICnMYCQzIykrrzTWNK04pGDENPIwO98n5g5tvvRyofzA76Ee1whsoZQMZoc7ap34gj8lRqiEbmM=
Received: from MN2PR11MB4366.namprd11.prod.outlook.com (2603:10b6:208:190::17) by MN2PR11MB4479.namprd11.prod.outlook.com (2603:10b6:208:17b::32) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3455.21; Mon, 12 Oct 2020 16:01:35 +0000
Received: from MN2PR11MB4366.namprd11.prod.outlook.com ([fe80::d84a:115:9ce0:8241]) by MN2PR11MB4366.namprd11.prod.outlook.com ([fe80::d84a:115:9ce0:8241%4]) with mapi id 15.20.3455.030; Mon, 12 Oct 2020 16:01:35 +0000
From: "Rob Wilton (rwilton)" <rwilton@cisco.com>
To: "draft-ietf-i2nsf-sdn-ipsec-flow-protection.all@ietf.org" <draft-ietf-i2nsf-sdn-ipsec-flow-protection.all@ietf.org>, Rafa Marin-Lopez <rafa@um.es>
CC: "i2nsf@ietf.org" <i2nsf@ietf.org>, Gabriel Lopez <gabilm@um.es>, "ipsec@ietf.org" <ipsec@ietf.org>, "last-call@ietf.org" <last-call@ietf.org>, "yang-doctors@ietf.org" <yang-doctors@ietf.org>, Christian Hopps <chopps@chopps.org>, Lou Berger <lberger@labn.net>, =?utf-8?B?TWFydGluIEJqw7Zya2x1bmQ=?= <mbj+ietf@4668.se>
Thread-Topic: [yang-doctors] [IPsec] [Last-Call] [I2nsf] Yangdoctors last call review of draft-ietf-i2nsf-sdn-ipsec-flow-protection-08
Thread-Index: AQHWlNo2e9jni2YANkmtZfreFx+hBKmUJBxQ
Date: Mon, 12 Oct 2020 16:01:35 +0000
Message-ID: <MN2PR11MB43662E1711367EDE9A066452B5070@MN2PR11MB4366.namprd11.prod.outlook.com>
References: <MN2PR11MB4366E30B3C372D13B391AE07B53B0@MN2PR11MB4366.namprd11.prod.outlook.com> <2B88888E-A264-4D81-A8DA-9C6225E83E0E@um.es> <70A0A406-0742-4F28-A5A4-8D539B160E24@chopps.org> <20200923.125826.1562347052257995146.id@4668.se> <CBC552B2-6039-48E8-988D-4F2BA3FD6B2E@chopps.org> <023fc27b-f86e-ed71-0c8f-d270c338f08c@labn.net>
In-Reply-To: <023fc27b-f86e-ed71-0c8f-d270c338f08c@labn.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=none action=none header.from=cisco.com;
x-originating-ip: [82.12.233.180]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 197de273-39cd-4ae0-e9f7-08d86ec81877
x-ms-traffictypediagnostic: MN2PR11MB4479:
x-microsoft-antispam-prvs: <MN2PR11MB44790EF4804ACEB8128EBF6CB5070@MN2PR11MB4479.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:6108;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: RcXF/gJdKhpmR5iMthNMuzv9oG7ByCotzDYUjpLyeMDT1CB6IS4RpQwuBLWNpvcGcNV/IV2huKBS4brfAx7GZHHO/qhUtrCKV6hUTl5orG6zRdG9cnG+R9uA0EUKTib4YtTHu9LEyrq/Z69nZfWQIK50yEJUP0K21S83W9NVO9BTDOIbk1s/2ww6Xu8+9yCW1XJc3MoxZS9kUjkZAYTnzWedk1+e8rhUOvSlf1+emmSqdK0JRRASavafNfdJyv4EWaSpflvew4n8eSX71mWtjeZ/jSeTeajjjFZ2BHYWxr9EeDHWLjX016SfMPvAxomsgLv6GKYV0N9A08h3aw6Ov938wOcXU4ETdRoXbg50Ehk=
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;  IPV:NLI; SFV:NSPM; H:MN2PR11MB4366.namprd11.prod.outlook.com; PTR:; CAT:NONE;  SFS:(346002)(39860400002)(376002)(396003)(366004)(136003)(64756008)(66556008)(316002)(76116006)(54906003)(66476007)(55016002)(66574015)(26005)(478600001)(6506007)(66446008)(2906002)(166002)(7696005)(71200400001)(186003)(66946007)(52536014)(53546011)(33656002)(83380400001)(966005)(5660300002)(7416002)(86362001)(9686003)(4326008)(110136005)(8936002)(8676002); DIR:OUT; SFP:1101; 
x-ms-exchange-antispam-messagedata: kxi6eiwaeGAcJG2Eflbgf2SlPlKoJUUadl0MAEIUwtO2eYPmPp/JnC60UIKsqO54DBWGEkdxzX7PNdCCMIlJx7/WG01ibcoVMfrb2HMt3rlEzrVpFjJ1Fqk77ZoXpm7OpvNA3uTXwjTrDhpR+gxUfUXOsKKI2C35fK4/0sgfOkTN2c/270SazQL4pvjLmnpdhRHdjs9iQMSR4SLcNXoFDsXZf3L8Ljz6prnB43hau7zKWNaXmhldOoCZ0lOqlBjUjRXJBRJmVKT9Ia9z2WcApJgAwDPwY75AA2JSKW5YJQh7EOAq8/4j6z8CpzpQ6ME2Hfok9css5wu1o8CKUEiisNfzeGeTFw1+MjhnR6dcL7TKx62jzxCEMgnxCd2IggvaeD4/fVt4FDzWjNdO46zXqTRTB4cc3/RDN6mrjcUKJv/UQNrzORUG5ou2r6jKapZ8GuxtBLKI5PCpHOgO2rvkG2fauc5LgRnODINRH2n/QGD0ayDFAbS4UwEz4aT0ZkxkenvJ615FDfeS4CRWDCzQK3AKHgbw/6pHaZ84Zj/ww6Gmv202DcZj7VAtgV23SHaJ8sxioDT+yeD3Hew4AMySKbmcgrHukK5iol8Gr99iLARfZfVN3du0fOm5pmP4CnLuibcmbxw+CWx0Qdxola7zaQ==
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_MN2PR11MB43662E1711367EDE9A066452B5070MN2PR11MB4366namp_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: MN2PR11MB4366.namprd11.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 197de273-39cd-4ae0-e9f7-08d86ec81877
X-MS-Exchange-CrossTenant-originalarrivaltime: 12 Oct 2020 16:01:35.5132 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5ae1af62-9505-4097-a69a-c1553ef7840e
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: hud1L3ceUBFx9J8YF0e/YEf9EbvXwlARqZJ1TaJWUxpy12xHvOhXtosGgVgLNEnuF8kZBGwNwqhSnHVabNI3wg==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MN2PR11MB4479
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.36.7.15, xch-aln-005.cisco.com
X-Outbound-Node: alln-core-4.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2nsf/OpMm2_iP5_tGvYhPsLCyxWkbzxI>
Subject: Re: [I2nsf] [yang-doctors] [IPsec] [Last-Call] Yangdoctors last call review of draft-ietf-i2nsf-sdn-ipsec-flow-protection-08
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: Mon, 12 Oct 2020 16:02:35 -0000

--_000_MN2PR11MB43662E1711367EDE9A066452B5070MN2PR11MB4366namp_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

SGkgUmFmYSwgYXV0aG9ycywNCg0KSnVzdCB0byBjaGVjay4NCg0KSGFzIHRoZXJlIGJlZW4gYW55
IGNsb3N1cmUgb24gdGhlIHN1Z2dlc3Rpb24gZnJvbSBDaHJpcyBvbiDigJxub3RpZmljYXRpb25z
IGluIHRoZSBpa2VsZXNzIG1vZHVsZSBhcyBhIGZlYXR1cmUiPyAgVGhpcyB3b3VsZCBzZWVtIHRv
IGJlIGEgZmFpcmx5IGNoZWFwICYgZWFzeSBjb21wcm9taXNlLg0KDQpUaGFua3MsDQpSb2INCg0K
DQpGcm9tOiB5YW5nLWRvY3RvcnMgPHlhbmctZG9jdG9ycy1ib3VuY2VzQGlldGYub3JnPiBPbiBC
ZWhhbGYgT2YgTG91IEJlcmdlcg0KU2VudDogMjcgU2VwdGVtYmVyIDIwMjAgMTU6MjYNClRvOiBD
aHJpc3RpYW4gSG9wcHMgPGNob3Bwc0BjaG9wcHMub3JnPjsgTWFydGluIEJqw7Zya2x1bmQgPG1i
aitpZXRmQDQ2Njguc2U+DQpDYzogUm9iZXJ0IFdpbHRvbiA8cndpbHRvbj00MGNpc2NvLmNvbUBk
bWFyYy5pZXRmLm9yZz47IGkybnNmQGlldGYub3JnOyBHYWJyaWVsIExvcGV6IDxnYWJpbG1AdW0u
ZXM+OyBkcmFmdC1pZXRmLWkybnNmLXNkbi1pcHNlYy1mbG93LXByb3RlY3Rpb24uYWxsQGlldGYu
b3JnOyBpcHNlY0BpZXRmLm9yZzsgbGFzdC1jYWxsQGlldGYub3JnOyBSYWZhIE1hcmluLUxvcGV6
IDxyYWZhQHVtLmVzPjsgeWFuZy1kb2N0b3JzQGlldGYub3JnDQpTdWJqZWN0OiBSZTogW3lhbmct
ZG9jdG9yc10gW0lQc2VjXSBbTGFzdC1DYWxsXSBbSTJuc2ZdIFlhbmdkb2N0b3JzIGxhc3QgY2Fs
bCByZXZpZXcgb2YgZHJhZnQtaWV0Zi1pMm5zZi1zZG4taXBzZWMtZmxvdy1wcm90ZWN0aW9uLTA4
DQoNClRoaXMgaXMgYSBzdWItb3B0aW1hbCBjb21wcm9taXNlIGIvYyBhbGwgSVBzZWMgaGF2ZSBT
QSBkYXRhYmFzZXMgZXZlbiBvbmVzIHJ1bm5pbmcgSUtFIC0tIGkuZS4sIFNBIGRhdGFiYXNlcyBh
cmUgY29tbW9uIHdoZXRoZXIgZXhwb3NlZCBpbiBZQU5HIG9yIG5vdCAtLSBidXQgaWYgaXQgY2Fu
IG1vdmUgaXQgZm9yd2FyZCBwZXJoYXBzIGdvb2QgZW5vdWdoLg0KDQoNClNwZWFraW5nIGFzIGFu
IGludGVyZXN0ZWQgcGFydHksIEkgaG9wZSB0aGF0IHNvbWUgY29tcHJvbWlzZSAvIGdvb2QgZW5v
dWdoIHNvbHV0aW9uIGlzIGZvbGxvd2VkIGluIHRoZSAtMDkgdmVyc2lvbiBvZiAgdGhpcyBkcmFm
dC4NCg0KTG91DQpPbiA5LzIzLzIwMjAgNzoyMCBBTSwgQ2hyaXN0aWFuIEhvcHBzIHdyb3RlOg0K
DQoNCg0KT24gU2VwIDIzLCAyMDIwLCBhdCA2OjU4IEFNLCBNYXJ0aW4gQmrDtnJrbHVuZCA8bWJq
K2lldGZANDY2OC5zZTxtYWlsdG86bWJqK2lldGZANDY2OC5zZT4+IHdyb3RlOg0KDQpIaSwNCg0K
Q2hyaXN0aWFuIEhvcHBzIDxjaG9wcHNAY2hvcHBzLm9yZzxtYWlsdG86Y2hvcHBzQGNob3Bwcy5v
cmc+PiB3cm90ZToNCg0KDQoNCg0KT24gU2VwIDIzLCAyMDIwLCBhdCA1OjI5IEFNLCBSYWZhIE1h
cmluLUxvcGV6IDxyYWZhQHVtLmVzPG1haWx0bzpyYWZhQHVtLmVzPj4gd3JvdGU6DQoNCg0KDQoN
CkJ1dCBJIHdvdWxkIGxpa2UgdG8gY2hlY2s6IE15IHVuZGVyc3RhbmRpbmcgaXMgdGhhdCB0aGUg
Y2hhbmdlcyB0aGF0DQpDaHJpcyBpcyBwcm9wb3NpbmcgYXJlIHByZXR0eSBzbWFsbC4gIEkuZS4g
bW92ZSB0aGUgU0Egc3RydWN0dXJlIHVuZGVyDQppcHNlYy1jb21tb24sIGFuZCBwdXQgaXQgdW5k
ZXIgYSBZQU5HIGZlYXR1cmUuICBBcmUgeW91IHN1cmUgdGhhdCBpdA0KaXMgaW1wcmFjdGljYWwg
dG8gYWNjb21tb2RhdGUgdGhpcyBjaGFuZ2Ugd2hpY2ggd291bGQgYWxsb3cgYSBzaW5nbGUNCmlw
c2VjIG1vZHVsZSB0byBiZSBzaGFyZWQgYW5kIGV4dGVuZGVkIHZpYSBZQU5HIGF1Z21lbnRhdGlv
bnM/DQoNCg0KSW4gdGhlIGNvbnRleHQgb2Ygb3VyIEktRCwgaWYgd2UgbW92ZSBTQUQgc3RydWN0
dXJlIHRvIGlwc2VjLWNvbW1vbiwNCndoYXQgd2UgYXJlIG1lYW5pbmcgaXMgdGhhdCBJUHNlYyBT
QSBjb25maWd1cmF0aW9uIGRhdGEgKHNldHRpbmcNCnZhbHVlcyB0byB0aGUgU0FEIHN0cnVjdHVy
ZSkgYXJlIGNvbW1vbiB0byB0aGUgSUtFIGNhc2UgYW5kIHRoZQ0KSUtFLWxlc3MgY2FzZXMsIHdo
aWNoIGFyZSBub3QuIEl0IGlzIGNvbmZ1c2luZy4NCg0KU29tZXRoaW5nIGRlZmluZWQgaW4gYSBj
b21tb24gbW9kdWxlIGJ1dCBtYXJrZWQgYXMgYSBmZWF0dXJlIGRvZXMgbm90DQppbXBseSB0aGF0
IHRoYXQgZmVhdHVyZSBoYXMgdG8gYmUgaW1wbGVtZW50ZWQgYnkgYW4gaW1wb3J0aW5nDQptb2R1
bGUuIFRoaXMgaXMgbm90IGNvbmZ1c2luZyB0byBZQU5HIGltcGxlbWVudGVycyBvciB1c2VycyBJ
DQp0aGluay4gSWYgd2UgYXJlIGp1c3QgdGFsa2luZyBhYm91dCBkb2N1bWVudCBmbG93IGhlcmUs
IHRoZW4gYQ0Kc2VudGVuY2Ugc2F5aW5nICJ0aGUgU0FEIGZlYXR1cmUgaXMgbm90IHJlcXVpcmVk
IHRvIGltcGxlbWVudCBJS0UNCmZ1bmN0aW9uYWxpdHkiIGlzIHF1aXRlIGVub3VnaCB0byBjbGVh
ciB0aGF0IHVwIEkgdGhpbmsuDQoNCkFub3RoZXIgYWx0ZXJuYXRpdmUgY291bGQgYmUgdG8gbW92
ZSB0aGVzZSBjb250YWluZXJzIHRvIGFub3RoZXINCihuZXcpIG1vZHVsZS4NCg0KSXQgbWF5IGFs
c28gYmUgZW5vdWdoIHRvIG1hcmsgdGhlIG5vdGlmaWNhdGlvbnMgaW4gdGhlIGlrZWxlc3MgbW9k
dWxlIGFzIGEgZmVhdHVyZSBJIHN1cHBvc2UuIFRoYXQgaXMgdGhlIGFjdHVhbCB0aGluZyBJIHRo
aW5rIG5vbi1TRE4gaW1wbGVtZW50YXRpb25zIHdvdWxkIHdhbnQgdG8gb21pdC4gVGhlIG1vZHVs
ZSBuYW1lICJpa2VsZXNzIiBpcyBub3QgZ3JlYXQgaW4gdGhpcyBjYXNlLCBidXQgcGVyaGFwcyB3
b3JrYWJsZS4NCg0KDQpUaGlzIGlzIGEgc3ViLW9wdGltYWwgY29tcHJvbWlzZSBiL2MgYWxsIElQ
c2VjIGhhdmUgU0EgZGF0YWJhc2VzIGV2ZW4gb25lcyBydW5uaW5nIElLRSAtLSBpLmUuLCBTQSBk
YXRhYmFzZXMgYXJlIGNvbW1vbiB3aGV0aGVyIGV4cG9zZWQgaW4gWUFORyBvciBub3QgLS0gYnV0
IGlmIGl0IGNhbiBtb3ZlIGl0IGZvcndhcmQgcGVyaGFwcyBnb29kIGVub3VnaC4NCg0KDQpJJ20g
ZGVmaW5pdGVseSBjb25jZXJuZWQgYWJvdXQgSUVURiBwcm9jZXNzIGFuZCByZWFsIHdvcmxkIHVz
YWJpbGl0eSBoZXJlLiBUaGVzZSBtb2R1bGVzIGFyZSBiYXNpY2FsbHkgd29ya2FibGUgZm9yIGlw
c2VjIEkgdGhpbmssIHRoZXkgY291bGQgYmUgdXNlZCBieSBvcGVyYXRvcnMgdG9kYXkuIElmIHdl
IHJlc3RhcnQgdGhlIGVudGlyZSBwcm9jZXNzIHRvIHJlZG8gdGhpcyB3b3JrIGZvciB0aGUgbW9y
ZSBnZW5lcmljIElQc2VjIGNhc2UgaXQgd2lsbCBwcm9iYWJseSBiZSB5ZWFycyBiZWZvcmUgdGhl
eSBhcmUgZmluaXNoZWQgYW5kIGluIHRoZSBmaWVsZC4gVGhpcyBuZXcgd29yayBjYW4gYmUgc3Rh
cnRlZCwgYnV0IHdoeSBub3QgaGF2ZSBzb21ldGhpbmcgdXNhYmxlIGluIHRoZSBtZWFudGltZT8N
Cg0KVGhhbmtzLA0KQ2hyaXMuDQoNCg0KDQovbWFydGluDQoNCg0KDQoNCg0KVGhhbmtzLA0KQ2hy
aXMuDQoNCg0KTW9yZW92ZXIsIHRoZSB1c2FnZSBvZiBmZWF0dXJlIG1lYW5zIHRoYXQsIGFmdGVy
IGFsbCwgdGhpcyDigJxjb21tb27igJ0gaXMNCm5vdCDigJxjb21tb27igJ0gdG8gYm90aCBjYXNl
cyBJS0UgY2FzZSBhbmQgSUtFLWxlc3MuIEFnYWluLCBpdCBzZWVtcw0KY29uZnVzaW5nLiBJbiB0
aGUgSUtFIGNhc2UsIHRoZSBTRE4vSTJOU0YgY29udHJvbGxlciBkb2VzIG5vdA0KY29uZmlndXJl
IHRoZSBTQUQgYXQgYWxsIGJ1dCB0aGUgSUtFIGltcGxlbWVudGF0aW9uIGluIHRoZSBOU0YuIElu
IG91cg0Kb3BpbmlvbiwgaW4gb3JkZXIgdG8gcHJvcGVybHkgYWRkIHRoaXMgSVBzZWMgU0Egb3Bl
cmF0aW9uYWwgc3RhdGUgdG8NCnRoZSBJS0UgY2FzZSB3ZSBzaG91bGQgaW5jbHVkZSBvcGVyYXRp
b25hbCBkYXRhIGFib3V0IHRoZSBJUHNlYyBTQXMNCihjb25maWcgZmFsc2UpIHRvIHRoZSBpZXRm
LWlwc2VjLWlrZS4gQWx0ZXJuYXRpdmVseSwgd2UgaGF2ZSBjZXJ0YWluDQpvcGVyYXRpb25hbCBk
YXRhIChybykgaW4gdGhlIFNBRCBzdHJ1Y3R1cmUgaW4gdGhlIElLRS1sZXNzIGNhc2UuIElmDQpv
bmx5IHRob3NlIGFyZSBtb3ZlZCB0byB0aGUgY29tbW9uIHBhcnQgc2hvdWxkIGJlIG9rIGJ1dCB3
ZSB0aGluayBpdA0KZG9lcyBub3Qgc29sdmUgdGhlIHByb2JsZW0uDQoNCi0tDQpsYXN0LWNhbGwg
bWFpbGluZyBsaXN0DQpsYXN0LWNhbGxAaWV0Zi5vcmc8bWFpbHRvOmxhc3QtY2FsbEBpZXRmLm9y
Zz4NCmh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vbGFzdC1jYWxsDQoNCg0K
DQoNCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQoNCklQ
c2VjIG1haWxpbmcgbGlzdA0KDQpJUHNlY0BpZXRmLm9yZzxtYWlsdG86SVBzZWNAaWV0Zi5vcmc+
DQoNCmh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vaXBzZWMNCg==

--_000_MN2PR11MB43662E1711367EDE9A066452B5070MN2PR11MB4366namp_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTUgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
IkNhbWJyaWEgTWF0aCI7DQoJcGFub3NlLTE6MiA0IDUgMyA1IDQgNiAzIDIgNDt9DQpAZm9udC1m
YWNlDQoJe2ZvbnQtZmFtaWx5OkNhbGlicmk7DQoJcGFub3NlLTE6MiAxNSA1IDIgMiAyIDQgMyAy
IDQ7fQ0KQGZvbnQtZmFjZQ0KCXtmb250LWZhbWlseTpDb25zb2xhczsNCglwYW5vc2UtMToyIDEx
IDYgOSAyIDIgNCAzIDIgNDt9DQpAZm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5Ok1lbmxvLVJlZ3Vs
YXI7DQoJcGFub3NlLTE6MCAwIDAgMCAwIDAgMCAwIDAgMDt9DQovKiBTdHlsZSBEZWZpbml0aW9u
cyAqLw0KcC5Nc29Ob3JtYWwsIGxpLk1zb05vcm1hbCwgZGl2Lk1zb05vcm1hbA0KCXttYXJnaW46
MGNtOw0KCWZvbnQtc2l6ZToxMS4wcHQ7DQoJZm9udC1mYW1pbHk6IkNhbGlicmkiLHNhbnMtc2Vy
aWY7fQ0KYTpsaW5rLCBzcGFuLk1zb0h5cGVybGluaw0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7
DQoJY29sb3I6Ymx1ZTsNCgl0ZXh0LWRlY29yYXRpb246dW5kZXJsaW5lO30NCnByZQ0KCXttc28t
c3R5bGUtcHJpb3JpdHk6OTk7DQoJbXNvLXN0eWxlLWxpbms6IkhUTUwgUHJlZm9ybWF0dGVkIENo
YXIiOw0KCW1hcmdpbjowY207DQoJZm9udC1zaXplOjEwLjBwdDsNCglmb250LWZhbWlseToiQ291
cmllciBOZXciO30NCnNwYW4uYXBwbGUtY29udmVydGVkLXNwYWNlDQoJe21zby1zdHlsZS1uYW1l
OmFwcGxlLWNvbnZlcnRlZC1zcGFjZTt9DQpzcGFuLkhUTUxQcmVmb3JtYXR0ZWRDaGFyDQoJe21z
by1zdHlsZS1uYW1lOiJIVE1MIFByZWZvcm1hdHRlZCBDaGFyIjsNCgltc28tc3R5bGUtcHJpb3Jp
dHk6OTk7DQoJbXNvLXN0eWxlLWxpbms6IkhUTUwgUHJlZm9ybWF0dGVkIjsNCglmb250LWZhbWls
eTpDb25zb2xhczt9DQpzcGFuLkVtYWlsU3R5bGUyMg0KCXttc28tc3R5bGUtdHlwZTpwZXJzb25h
bC1yZXBseTsNCglmb250LWZhbWlseToiQ2FsaWJyaSIsc2Fucy1zZXJpZjsNCgljb2xvcjp3aW5k
b3d0ZXh0O30NCi5Nc29DaHBEZWZhdWx0DQoJe21zby1zdHlsZS10eXBlOmV4cG9ydC1vbmx5Ow0K
CWZvbnQtc2l6ZToxMC4wcHQ7fQ0KQHBhZ2UgV29yZFNlY3Rpb24xDQoJe3NpemU6NjEyLjBwdCA3
OTIuMHB0Ow0KCW1hcmdpbjo3Mi4wcHQgNzIuMHB0IDcyLjBwdCA3Mi4wcHQ7fQ0KZGl2LldvcmRT
ZWN0aW9uMQ0KCXtwYWdlOldvcmRTZWN0aW9uMTt9DQotLT48L3N0eWxlPjwhLS1baWYgZ3RlIG1z
byA5XT48eG1sPg0KPG86c2hhcGVkZWZhdWx0cyB2OmV4dD0iZWRpdCIgc3BpZG1heD0iMTAyNiIg
Lz4NCjwveG1sPjwhW2VuZGlmXS0tPjwhLS1baWYgZ3RlIG1zbyA5XT48eG1sPg0KPG86c2hhcGVs
YXlvdXQgdjpleHQ9ImVkaXQiPg0KPG86aWRtYXAgdjpleHQ9ImVkaXQiIGRhdGE9IjEiIC8+DQo8
L286c2hhcGVsYXlvdXQ+PC94bWw+PCFbZW5kaWZdLS0+DQo8L2hlYWQ+DQo8Ym9keSBsYW5nPSJF
Ti1HQiIgbGluaz0iYmx1ZSIgdmxpbms9InB1cnBsZSI+DQo8ZGl2IGNsYXNzPSJXb3JkU2VjdGlv
bjEiPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9Im1zby1mYXJlYXN0LWxhbmd1
YWdlOkVOLVVTIj5IaSBSYWZhLCBhdXRob3JzLDxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJtc28tZmFyZWFzdC1sYW5ndWFnZTpFTi1VUyI+
PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4g
c3R5bGU9Im1zby1mYXJlYXN0LWxhbmd1YWdlOkVOLVVTIj5KdXN0IHRvIGNoZWNrLjxvOnA+PC9v
OnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJtc28tZmFy
ZWFzdC1sYW5ndWFnZTpFTi1VUyI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9Im1zby1mYXJlYXN0LWxhbmd1YWdlOkVOLVVTIj5I
YXMgdGhlcmUgYmVlbiBhbnkgY2xvc3VyZSBvbiB0aGUgc3VnZ2VzdGlvbiBmcm9tIENocmlzIG9u
IOKAnDwvc3Bhbj48c3BhbiBzdHlsZT0iY29sb3I6YmxhY2siPm5vdGlmaWNhdGlvbnMgaW4gdGhl
IGlrZWxlc3MgbW9kdWxlIGFzIGEgZmVhdHVyZSZxdW90Oz8mbmJzcDsgVGhpcyB3b3VsZCBzZWVt
IHRvIGJlIGEgZmFpcmx5IGNoZWFwICZhbXA7IGVhc3kgY29tcHJvbWlzZS48bzpwPjwvbzpwPjwv
c3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iY29sb3I6YmxhY2si
PjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFu
IHN0eWxlPSJjb2xvcjpibGFjayI+VGhhbmtzLDxicj4NClJvYjxvOnA+PC9vOnA+PC9zcGFuPjwv
cD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJjb2xvcjpibGFjayI+PG86cD4m
bmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9
Im1zby1mYXJlYXN0LWxhbmd1YWdlOkVOLVVTIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+
DQo8ZGl2IHN0eWxlPSJib3JkZXI6bm9uZTtib3JkZXItbGVmdDpzb2xpZCBibHVlIDEuNXB0O3Bh
ZGRpbmc6MGNtIDBjbSAwY20gNC4wcHQiPg0KPGRpdj4NCjxkaXYgc3R5bGU9ImJvcmRlcjpub25l
O2JvcmRlci10b3A6c29saWQgI0UxRTFFMSAxLjBwdDtwYWRkaW5nOjMuMHB0IDBjbSAwY20gMGNt
Ij4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxiPjxzcGFuIGxhbmc9IkVOLVVTIj5Gcm9tOjwvc3Bh
bj48L2I+PHNwYW4gbGFuZz0iRU4tVVMiPiB5YW5nLWRvY3RvcnMgJmx0O3lhbmctZG9jdG9ycy1i
b3VuY2VzQGlldGYub3JnJmd0Ow0KPGI+T24gQmVoYWxmIE9mIDwvYj5Mb3UgQmVyZ2VyPGJyPg0K
PGI+U2VudDo8L2I+IDI3IFNlcHRlbWJlciAyMDIwIDE1OjI2PGJyPg0KPGI+VG86PC9iPiBDaHJp
c3RpYW4gSG9wcHMgJmx0O2Nob3Bwc0BjaG9wcHMub3JnJmd0OzsgTWFydGluIEJqw7Zya2x1bmQg
Jmx0O21iaitpZXRmQDQ2Njguc2UmZ3Q7PGJyPg0KPGI+Q2M6PC9iPiBSb2JlcnQgV2lsdG9uICZs
dDtyd2lsdG9uPTQwY2lzY28uY29tQGRtYXJjLmlldGYub3JnJmd0OzsgaTJuc2ZAaWV0Zi5vcmc7
IEdhYnJpZWwgTG9wZXogJmx0O2dhYmlsbUB1bS5lcyZndDs7IGRyYWZ0LWlldGYtaTJuc2Ytc2Ru
LWlwc2VjLWZsb3ctcHJvdGVjdGlvbi5hbGxAaWV0Zi5vcmc7IGlwc2VjQGlldGYub3JnOyBsYXN0
LWNhbGxAaWV0Zi5vcmc7IFJhZmEgTWFyaW4tTG9wZXogJmx0O3JhZmFAdW0uZXMmZ3Q7OyB5YW5n
LWRvY3RvcnNAaWV0Zi5vcmc8YnI+DQo8Yj5TdWJqZWN0OjwvYj4gUmU6IFt5YW5nLWRvY3RvcnNd
IFtJUHNlY10gW0xhc3QtQ2FsbF0gW0kybnNmXSBZYW5nZG9jdG9ycyBsYXN0IGNhbGwgcmV2aWV3
IG9mIGRyYWZ0LWlldGYtaTJuc2Ytc2RuLWlwc2VjLWZsb3ctcHJvdGVjdGlvbi0wODxvOnA+PC9v
OnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpw
PiZuYnNwOzwvbzpwPjwvcD4NCjxibG9ja3F1b3RlIHN0eWxlPSJtYXJnaW4tdG9wOjUuMHB0O21h
cmdpbi1ib3R0b206NS4wcHQiPg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPlRoaXMgaXMg
YSBzdWItb3B0aW1hbCBjb21wcm9taXNlIGIvYyBhbGwgSVBzZWMgaGF2ZSBTQSBkYXRhYmFzZXMg
ZXZlbiBvbmVzIHJ1bm5pbmcgSUtFIC0tIGkuZS4sIFNBIGRhdGFiYXNlcyBhcmUgY29tbW9uIHdo
ZXRoZXIgZXhwb3NlZCBpbiBZQU5HIG9yIG5vdCAtLSBidXQgaWYgaXQgY2FuIG1vdmUgaXQgZm9y
d2FyZCBwZXJoYXBzIGdvb2QgZW5vdWdoLjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCI+PGJyPg0KPGJyPg0KPG86cD48L286cD48L3A+DQo8L2Rpdj4N
CjwvYmxvY2txdW90ZT4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPlNwZWFraW5nIGFzIGFuIGludGVy
ZXN0ZWQgcGFydHksIEkgaG9wZSB0aGF0IHNvbWUgY29tcHJvbWlzZSAvIGdvb2QgZW5vdWdoIHNv
bHV0aW9uIGlzIGZvbGxvd2VkIGluIHRoZSAtMDkgdmVyc2lvbiBvZiZuYnNwOyB0aGlzIGRyYWZ0
LjxvOnA+PC9vOnA+PC9wPg0KPHA+TG91PG86cD48L286cD48L3A+DQo8ZGl2Pg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCI+T24gOS8yMy8yMDIwIDc6MjAgQU0sIENocmlzdGlhbiBIb3BwcyB3cm90ZTo8
bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGJsb2NrcXVvdGUgc3R5bGU9Im1hcmdpbi10b3A6NS4w
cHQ7bWFyZ2luLWJvdHRvbTo1LjBwdCI+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNw
OzwvbzpwPjwvcD4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48YnI+DQo8YnI+DQo8bzpw
PjwvbzpwPjwvcD4NCjxibG9ja3F1b3RlIHN0eWxlPSJtYXJnaW4tdG9wOjUuMHB0O21hcmdpbi1i
b3R0b206NS4wcHQiPg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPk9uIFNlcCAyMywgMjAy
MCwgYXQgNjo1OCBBTSwgTWFydGluIEJqw7Zya2x1bmQgJmx0OzxhIGhyZWY9Im1haWx0bzptYmor
aWV0ZkA0NjY4LnNlIj5tYmoraWV0ZkA0NjY4LnNlPC9hPiZndDsgd3JvdGU6PG86cD48L286cD48
L3A+DQo8L2Rpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0K
PGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuNXB0
O2ZvbnQtZmFtaWx5OiZxdW90O01lbmxvLVJlZ3VsYXImcXVvdDssc2VyaWYiPkhpLDxicj4NCjxi
cj4NCkNocmlzdGlhbiBIb3BwcyAmbHQ7PC9zcGFuPjxhIGhyZWY9Im1haWx0bzpjaG9wcHNAY2hv
cHBzLm9yZyI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC41cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7
TWVubG8tUmVndWxhciZxdW90OyxzZXJpZiI+Y2hvcHBzQGNob3Bwcy5vcmc8L3NwYW4+PC9hPjxz
cGFuIHN0eWxlPSJmb250LXNpemU6MTAuNXB0O2ZvbnQtZmFtaWx5OiZxdW90O01lbmxvLVJlZ3Vs
YXImcXVvdDssc2VyaWYiPiZndDsgd3JvdGU6PGJyIHN0eWxlPSJjYXJldC1jb2xvcjogcmdiKDAs
IDAsIDApO2ZvbnQtdmFyaWFudC1jYXBzOiBub3JtYWw7dGV4dC1hbGlnbjpzdGFydDstd2Via2l0
LXRleHQtc3Ryb2tlLXdpZHRoOiAwcHg7d29yZC1zcGFjaW5nOjBweCI+DQo8YnI+DQo8L3NwYW4+
PG86cD48L286cD48L3A+DQo8YmxvY2txdW90ZSBzdHlsZT0ibWFyZ2luLXRvcDo1LjBwdDttYXJn
aW4tYm90dG9tOjUuMHB0Ij4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250
LXNpemU6MTAuNXB0O2ZvbnQtZmFtaWx5OiZxdW90O01lbmxvLVJlZ3VsYXImcXVvdDssc2VyaWYi
Pjxicj4NCjxicj4NCjxicj4NCjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxibG9ja3F1b3RlIHN0
eWxlPSJtYXJnaW4tdG9wOjUuMHB0O21hcmdpbi1ib3R0b206NS4wcHQiPg0KPHAgY2xhc3M9Ik1z
b05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC41cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7
TWVubG8tUmVndWxhciZxdW90OyxzZXJpZiI+T24gU2VwIDIzLCAyMDIwLCBhdCA1OjI5IEFNLCBS
YWZhIE1hcmluLUxvcGV6ICZsdDs8YSBocmVmPSJtYWlsdG86cmFmYUB1bS5lcyI+cmFmYUB1bS5l
czwvYT4mZ3Q7IHdyb3RlOjxicj4NCjxicj4NCjxicj4NCjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4N
CjxibG9ja3F1b3RlIHN0eWxlPSJtYXJnaW4tdG9wOjUuMHB0O21hcmdpbi1ib3R0b206NS4wcHQi
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC41cHQ7Zm9u
dC1mYW1pbHk6JnF1b3Q7TWVubG8tUmVndWxhciZxdW90OyxzZXJpZiI+PGJyPg0KPGJyPg0KQnV0
IEkgd291bGQgbGlrZSB0byBjaGVjazogTXkgdW5kZXJzdGFuZGluZyBpcyB0aGF0IHRoZSBjaGFu
Z2VzIHRoYXQ8YnI+DQpDaHJpcyBpcyBwcm9wb3NpbmcgYXJlIHByZXR0eSBzbWFsbC4gJm5ic3A7
SS5lLiBtb3ZlIHRoZSBTQSBzdHJ1Y3R1cmUgdW5kZXI8YnI+DQppcHNlYy1jb21tb24sIGFuZCBw
dXQgaXQgdW5kZXIgYSBZQU5HIGZlYXR1cmUuICZuYnNwO0FyZSB5b3Ugc3VyZSB0aGF0IGl0PGJy
Pg0KaXMgaW1wcmFjdGljYWwgdG8gYWNjb21tb2RhdGUgdGhpcyBjaGFuZ2Ugd2hpY2ggd291bGQg
YWxsb3cgYSBzaW5nbGU8YnI+DQppcHNlYyBtb2R1bGUgdG8gYmUgc2hhcmVkIGFuZCBleHRlbmRl
ZCB2aWEgWUFORyBhdWdtZW50YXRpb25zPzxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvYmxvY2tx
dW90ZT4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuNXB0
O2ZvbnQtZmFtaWx5OiZxdW90O01lbmxvLVJlZ3VsYXImcXVvdDssc2VyaWYiPjxicj4NCjxicj4N
CkluIHRoZSBjb250ZXh0IG9mIG91ciBJLUQsIGlmIHdlIG1vdmUgU0FEIHN0cnVjdHVyZSB0byBp
cHNlYy1jb21tb24sPGJyPg0Kd2hhdCB3ZSBhcmUgbWVhbmluZyBpcyB0aGF0IElQc2VjIFNBIGNv
bmZpZ3VyYXRpb24gZGF0YSAoc2V0dGluZzxicj4NCnZhbHVlcyB0byB0aGUgU0FEIHN0cnVjdHVy
ZSkgYXJlIGNvbW1vbiB0byB0aGUgSUtFIGNhc2UgYW5kIHRoZTxicj4NCklLRS1sZXNzIGNhc2Vz
LCB3aGljaCBhcmUgbm90LiBJdCBpcyBjb25mdXNpbmcuPG86cD48L286cD48L3NwYW4+PC9wPg0K
PC9ibG9ja3F1b3RlPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6
ZToxMC41cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7TWVubG8tUmVndWxhciZxdW90OyxzZXJpZiI+PGJy
Pg0KU29tZXRoaW5nIGRlZmluZWQgaW4gYSBjb21tb24gbW9kdWxlIGJ1dCBtYXJrZWQgYXMgYSBm
ZWF0dXJlIGRvZXMgbm90PGJyPg0KaW1wbHkgdGhhdCB0aGF0IGZlYXR1cmUgaGFzIHRvIGJlIGlt
cGxlbWVudGVkIGJ5IGFuIGltcG9ydGluZzxicj4NCm1vZHVsZS4gVGhpcyBpcyBub3QgY29uZnVz
aW5nIHRvIFlBTkcgaW1wbGVtZW50ZXJzIG9yIHVzZXJzIEk8YnI+DQp0aGluay4gSWYgd2UgYXJl
IGp1c3QgdGFsa2luZyBhYm91dCBkb2N1bWVudCBmbG93IGhlcmUsIHRoZW4gYTxicj4NCnNlbnRl
bmNlIHNheWluZyAmcXVvdDt0aGUgU0FEIGZlYXR1cmUgaXMgbm90IHJlcXVpcmVkIHRvIGltcGxl
bWVudCBJS0U8YnI+DQpmdW5jdGlvbmFsaXR5JnF1b3Q7IGlzIHF1aXRlIGVub3VnaCB0byBjbGVh
ciB0aGF0IHVwIEkgdGhpbmsuPG86cD48L286cD48L3NwYW4+PC9wPg0KPC9ibG9ja3F1b3RlPg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC41cHQ7Zm9udC1m
YW1pbHk6JnF1b3Q7TWVubG8tUmVndWxhciZxdW90OyxzZXJpZiI+PGJyPg0KQW5vdGhlciBhbHRl
cm5hdGl2ZSBjb3VsZCBiZSB0byBtb3ZlIHRoZXNlIGNvbnRhaW5lcnMgdG8gYW5vdGhlcjxicj4N
CihuZXcpIG1vZHVsZS48L3NwYW4+PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjwvYmxvY2txdW90
ZT4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwv
ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImNvbG9yOmJsYWNrIj5JdCBt
YXkgYWxzbyBiZSBlbm91Z2ggdG8gbWFyayB0aGUgbm90aWZpY2F0aW9ucyBpbiB0aGUgaWtlbGVz
cyBtb2R1bGUgYXMgYSBmZWF0dXJlIEkgc3VwcG9zZS4gVGhhdCBpcyB0aGUgYWN0dWFsIHRoaW5n
IEkgdGhpbmsgbm9uLVNETiBpbXBsZW1lbnRhdGlvbnMgd291bGQgd2FudCB0byBvbWl0LiBUaGUg
bW9kdWxlIG5hbWUgJnF1b3Q7aWtlbGVzcyZxdW90OyBpcyBub3QgZ3JlYXQNCiBpbiB0aGlzIGNh
c2UsIGJ1dCBwZXJoYXBzIHdvcmthYmxlLjwvc3Bhbj48bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0K
PGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJjb2xvcjpibGFjayI+PGJy
Pg0KPGJyPg0KPC9zcGFuPjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImNvbG9yOmJsYWNrIj5UaGlzIGlzIGEgc3ViLW9wdGlt
YWwgY29tcHJvbWlzZSBiL2MgYWxsIElQc2VjIGhhdmUgU0EgZGF0YWJhc2VzIGV2ZW4gb25lcyBy
dW5uaW5nIElLRSAtLSBpLmUuLCBTQSBkYXRhYmFzZXMgYXJlIGNvbW1vbiB3aGV0aGVyIGV4cG9z
ZWQgaW4gWUFORyBvciBub3QgLS0gYnV0IGlmIGl0IGNhbiBtb3ZlIGl0IGZvcndhcmQgcGVyaGFw
cyBnb29kIGVub3VnaC48L3NwYW4+PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iY29sb3I6YmxhY2siPjxicj4NCjxicj4NCjwv
c3Bhbj48bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
PjxzcGFuIHN0eWxlPSJjb2xvcjpibGFjayI+SSdtIGRlZmluaXRlbHkgY29uY2VybmVkIGFib3V0
IElFVEYgcHJvY2VzcyBhbmQgcmVhbCB3b3JsZCB1c2FiaWxpdHkgaGVyZS4gVGhlc2UgbW9kdWxl
cyBhcmUgYmFzaWNhbGx5IHdvcmthYmxlIGZvciBpcHNlYyBJIHRoaW5rLCB0aGV5IGNvdWxkIGJl
IHVzZWQgYnkgb3BlcmF0b3JzIHRvZGF5LiBJZiB3ZSByZXN0YXJ0IHRoZSBlbnRpcmUgcHJvY2Vz
cyB0byByZWRvDQogdGhpcyB3b3JrIGZvciB0aGUgbW9yZSBnZW5lcmljIElQc2VjIGNhc2UgaXQg
d2lsbCBwcm9iYWJseSBiZSB5ZWFycyBiZWZvcmUgdGhleSBhcmUgZmluaXNoZWQgYW5kIGluIHRo
ZSBmaWVsZC4gVGhpcyBuZXcgd29yayBjYW4gYmUgc3RhcnRlZCwgYnV0IHdoeSBub3QgaGF2ZSBz
b21ldGhpbmcgdXNhYmxlIGluIHRoZSBtZWFudGltZT88L3NwYW4+PG86cD48L286cD48L3A+DQo8
L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4N
CjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPlRoYW5rcyw8bzpwPjwvbzpwPjwv
cD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPkNocmlzLjxvOnA+PC9vOnA+
PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286
cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8YmxvY2txdW90ZSBzdHlsZT0ibWFyZ2luLXRvcDo1LjBw
dDttYXJnaW4tYm90dG9tOjUuMHB0Ij4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3Bh
biBzdHlsZT0iZm9udC1zaXplOjEwLjVwdDtmb250LWZhbWlseTomcXVvdDtNZW5sby1SZWd1bGFy
JnF1b3Q7LHNlcmlmIj48YnI+DQo8YnI+DQovbWFydGluPGJyPg0KPGJyPg0KPGJyPg0KPGJyIHN0
eWxlPSJjYXJldC1jb2xvcjogcmdiKDAsIDAsIDApO2ZvbnQtdmFyaWFudC1jYXBzOiBub3JtYWw7
dGV4dC1hbGlnbjpzdGFydDstd2Via2l0LXRleHQtc3Ryb2tlLXdpZHRoOiAwcHg7d29yZC1zcGFj
aW5nOjBweCI+DQo8YnI+DQo8L3NwYW4+PG86cD48L286cD48L3A+DQo8YmxvY2txdW90ZSBzdHls
ZT0ibWFyZ2luLXRvcDo1LjBwdDttYXJnaW4tYm90dG9tOjUuMHB0Ij4NCjxwIGNsYXNzPSJNc29O
b3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuNXB0O2ZvbnQtZmFtaWx5OiZxdW90O01l
bmxvLVJlZ3VsYXImcXVvdDssc2VyaWYiPjxicj4NClRoYW5rcyw8YnI+DQpDaHJpcy48YnI+DQo8
YnI+DQo8YnI+DQo8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8YmxvY2txdW90ZSBzdHlsZT0ibWFy
Z2luLXRvcDo1LjBwdDttYXJnaW4tYm90dG9tOjUuMHB0Ij4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
IHN0eWxlPSJtYXJnaW4tYm90dG9tOjEyLjBwdCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC41
cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7TWVubG8tUmVndWxhciZxdW90OyxzZXJpZiI+TW9yZW92ZXIs
IHRoZSB1c2FnZSBvZiBmZWF0dXJlIG1lYW5zIHRoYXQsIGFmdGVyIGFsbCwgdGhpcyDigJxjb21t
b27igJ0gaXM8YnI+DQpub3Qg4oCcY29tbW9u4oCdIHRvIGJvdGggY2FzZXMgSUtFIGNhc2UgYW5k
IElLRS1sZXNzLiBBZ2FpbiwgaXQgc2VlbXM8YnI+DQpjb25mdXNpbmcuIEluIHRoZSBJS0UgY2Fz
ZSwgdGhlIFNETi9JMk5TRiBjb250cm9sbGVyIGRvZXMgbm90PGJyPg0KY29uZmlndXJlIHRoZSBT
QUQgYXQgYWxsIGJ1dCB0aGUgSUtFIGltcGxlbWVudGF0aW9uIGluIHRoZSBOU0YuIEluIG91cjxi
cj4NCm9waW5pb24sIGluIG9yZGVyIHRvIHByb3Blcmx5IGFkZCB0aGlzIElQc2VjIFNBIG9wZXJh
dGlvbmFsIHN0YXRlIHRvPGJyPg0KdGhlIElLRSBjYXNlIHdlIHNob3VsZCBpbmNsdWRlIG9wZXJh
dGlvbmFsIGRhdGEgYWJvdXQgdGhlIElQc2VjIFNBczxicj4NCihjb25maWcgZmFsc2UpIHRvIHRo
ZSBpZXRmLWlwc2VjLWlrZS4gQWx0ZXJuYXRpdmVseSwgd2UgaGF2ZSBjZXJ0YWluPGJyPg0Kb3Bl
cmF0aW9uYWwgZGF0YSAocm8pIGluIHRoZSBTQUQgc3RydWN0dXJlIGluIHRoZSBJS0UtbGVzcyBj
YXNlLiBJZjxicj4NCm9ubHkgdGhvc2UgYXJlIG1vdmVkIHRvIHRoZSBjb21tb24gcGFydCBzaG91
bGQgYmUgb2sgYnV0IHdlIHRoaW5rIGl0PGJyPg0KZG9lcyBub3Qgc29sdmUgdGhlIHByb2JsZW0u
PG86cD48L286cD48L3NwYW4+PC9wPg0KPC9ibG9ja3F1b3RlPg0KPHAgY2xhc3M9Ik1zb05vcm1h
bCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC41cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7TWVubG8t
UmVndWxhciZxdW90OyxzZXJpZiI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPC9ibG9j
a3F1b3RlPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC41
cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7TWVubG8tUmVndWxhciZxdW90OyxzZXJpZiI+LS08c3BhbiBj
bGFzcz0iYXBwbGUtY29udmVydGVkLXNwYWNlIj4mbmJzcDs8L3NwYW4+PGJyPg0KbGFzdC1jYWxs
IG1haWxpbmcgbGlzdDxicj4NCjwvc3Bhbj48YSBocmVmPSJtYWlsdG86bGFzdC1jYWxsQGlldGYu
b3JnIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjVwdDtmb250LWZhbWlseTomcXVvdDtNZW5s
by1SZWd1bGFyJnF1b3Q7LHNlcmlmIj5sYXN0LWNhbGxAaWV0Zi5vcmc8L3NwYW4+PC9hPjxzcGFu
IHN0eWxlPSJmb250LXNpemU6MTAuNXB0O2ZvbnQtZmFtaWx5OiZxdW90O01lbmxvLVJlZ3VsYXIm
cXVvdDssc2VyaWYiPjxicj4NCjwvc3Bhbj48YSBocmVmPSJodHRwczovL3d3dy5pZXRmLm9yZy9t
YWlsbWFuL2xpc3RpbmZvL2xhc3QtY2FsbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC41cHQ7
Zm9udC1mYW1pbHk6JnF1b3Q7TWVubG8tUmVndWxhciZxdW90OyxzZXJpZiI+aHR0cHM6Ly93d3cu
aWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9sYXN0LWNhbGw8L3NwYW4+PC9hPjxvOnA+PC9vOnA+
PC9wPg0KPC9kaXY+DQo8L2Jsb2NrcXVvdGU+DQo8L2Rpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
Pjxicj4NCjxicj4NCjxicj4NCjxvOnA+PC9vOnA+PC9wPg0KPHByZT5fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXzxvOnA+PC9vOnA+PC9wcmU+DQo8cHJlPklQ
c2VjIG1haWxpbmcgbGlzdDxvOnA+PC9vOnA+PC9wcmU+DQo8cHJlPjxhIGhyZWY9Im1haWx0bzpJ
UHNlY0BpZXRmLm9yZyI+SVBzZWNAaWV0Zi5vcmc8L2E+PG86cD48L286cD48L3ByZT4NCjxwcmU+
PGEgaHJlZj0iaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9pcHNlYyI+aHR0
cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9pcHNlYzwvYT48bzpwPjwvbzpwPjwv
cHJlPg0KPC9ibG9ja3F1b3RlPg0KPC9kaXY+DQo8L2Rpdj4NCjwvYm9keT4NCjwvaHRtbD4NCg==

--_000_MN2PR11MB43662E1711367EDE9A066452B5070MN2PR11MB4366namp_--


From nobody Mon Oct 12 11:15:59 2020
Return-Path: <internet-drafts@ietf.org>
X-Original-To: i2nsf@ietf.org
Delivered-To: i2nsf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 300543A15F3; Mon, 12 Oct 2020 11:15:52 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
Cc: i2nsf@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 7.20.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: i2nsf@ietf.org
Message-ID: <160252655215.514.13659824821779072247@ietfa.amsl.com>
Date: Mon, 12 Oct 2020 11:15:52 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2nsf/0PmY7mNXJ4fMnPWHjw686i10u6s>
Subject: [I2nsf] I-D Action: draft-ietf-i2nsf-sdn-ipsec-flow-protection-09.txt
X-BeenThere: i2nsf@ietf.org
X-Mailman-Version: 2.1.29
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: Mon, 12 Oct 2020 18:15:52 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Interface to Network Security Functions WG of the IETF.

        Title           : Software-Defined Networking (SDN)-based IPsec Flow Protection
        Authors         : Rafa Marin-Lopez
                          Gabriel Lopez-Millan
                          Fernando Pereniguez-Garcia
	Filename        : draft-ietf-i2nsf-sdn-ipsec-flow-protection-09.txt
	Pages           : 92
	Date            : 2020-10-12

Abstract:
   This document describes how to provide IPsec-based flow protection
   (integrity and confidentiality) by means of an Interface to Network
   Security Function (I2NSF) controller.  It considers two main well-
   known scenarios in IPsec: (i) gateway-to-gateway and (ii) host-to-
   host.  The service described in this document allows the
   configuration and monitoring of IPsec Security Associations (SAs)
   from a I2NSF Controller to one or several flow-based Network Security
   Functions (NSFs) that rely on IPsec to protect data traffic.

   The document focuses on the I2NSF NSF-facing interface by providing
   YANG data models for configuring the IPsec databases (SPD, SAD, PAD)
   and IKEv2.  This allows IPsec SA establishment with minimal
   intervention by the network administrator.  It does not define any
   new protocol.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-i2nsf-sdn-ipsec-flow-protection/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-i2nsf-sdn-ipsec-flow-protection-09
https://datatracker.ietf.org/doc/html/draft-ietf-i2nsf-sdn-ipsec-flow-protection-09

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-i2nsf-sdn-ipsec-flow-protection-09


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/



From nobody Mon Oct 12 12:08:10 2020
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 4323B3A00E3; Mon, 12 Oct 2020 12:08:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.096
X-Spam-Level: 
X-Spam-Status: No, score=-2.096 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, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=um.es
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 7LqUxCNGHOOt; Mon, 12 Oct 2020 12:08:06 -0700 (PDT)
Received: from mx02.puc.rediris.es (outbound4sev.lav.puc.rediris.es [130.206.19.178]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 91BCD3A00D2; Mon, 12 Oct 2020 12:08:05 -0700 (PDT)
Received: from xenon43.um.es (xenon43.um.es [155.54.212.170]) by mx02.puc.rediris.es  with ESMTP id 09CJ7sxQ030785-09CJ7sxR030785; Mon, 12 Oct 2020 21:07:54 +0200
Received: from localhost (localhost [127.0.0.1]) by xenon43.um.es (Postfix) with ESMTP id BA58220017; Mon, 12 Oct 2020 21:07:54 +0200 (CEST)
X-Virus-Scanned: by antispam in UMU at xenon43.um.es
Received: from xenon43.um.es ([127.0.0.1]) by localhost (xenon43.um.es [127.0.0.1]) (amavisd-new, port 10024) with LMTP id Yn4Tv_CJGZkn; Mon, 12 Oct 2020 21:07:54 +0200 (CEST)
Received: from [192.168.1.33] (135.red-79-150-250.dynamicip.rima-tde.net [79.150.250.135]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: rafa@um.es) by xenon43.um.es (Postfix) with ESMTPSA id 24C96203A0; Mon, 12 Oct 2020 21:07:47 +0200 (CEST)
From: Rafa Marin-Lopez <rafa@um.es>
Message-Id: <E827743C-74A1-42CE-9765-7ECD062D8E41@um.es>
Content-Type: multipart/alternative; boundary="Apple-Mail=_9DBA0896-01DA-4AE8-AD6F-ED8776315628"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.14\))
Date: Mon, 12 Oct 2020 21:07:46 +0200
In-Reply-To: <MN2PR11MB43662E1711367EDE9A066452B5070@MN2PR11MB4366.namprd11.prod.outlook.com>
Cc: Rafa Marin-Lopez <rafa@um.es>, "draft-ietf-i2nsf-sdn-ipsec-flow-protection.all@ietf.org" <draft-ietf-i2nsf-sdn-ipsec-flow-protection.all@ietf.org>,  "i2nsf@ietf.org" <i2nsf@ietf.org>, Gabriel Lopez <gabilm@um.es>, Christian Hopps <chopps@chopps.org>, "ipsec@ietf.org" <ipsec@ietf.org>, "last-call@ietf.org" <last-call@ietf.org>, =?utf-8?Q?Martin_Bj=C3=B6rklund?= <mbj+ietf@4668.se>, "yang-doctors@ietf.org" <yang-doctors@ietf.org>, Lou Berger <lberger@labn.net>
To: "Rob Wilton (rwilton)" <rwilton=40cisco.com@dmarc.ietf.org>
References: <MN2PR11MB4366E30B3C372D13B391AE07B53B0@MN2PR11MB4366.namprd11.prod.outlook.com> <2B88888E-A264-4D81-A8DA-9C6225E83E0E@um.es> <70A0A406-0742-4F28-A5A4-8D539B160E24@chopps.org> <20200923.125826.1562347052257995146.id@4668.se> <CBC552B2-6039-48E8-988D-4F2BA3FD6B2E@chopps.org> <023fc27b-f86e-ed71-0c8f-d270c338f08c@labn.net> <MN2PR11MB43662E1711367EDE9A066452B5070@MN2PR11MB4366.namprd11.prod.outlook.com>
X-Mailer: Apple Mail (2.3445.104.14)
X-FEAS-SPF: spf-result=pass, ip=155.54.212.170, helo=xenon43.um.es, mailFrom=rafa@um.es
Authentication-Results: mx02.puc.rediris.es; spf=pass (rediris.es: domain of rafa@um.es designates 155.54.212.170 as permitted sender) smtp.mailfrom=rafa@um.es
X-FE-Policy-ID: 2:15:0: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=noTpIhZtxIuJXWK6Yh83PqwvrZhAse39eBxRtYtyAEU=; b=omTwEgxbrrI//DXo1s6taImYBmkM8X5V0//cbKO0bj5vbV5YUYTHGkprIPQNCvVAATjlSpwe5Bnu 1s3p8ExKSrmYPLXqpF4/w8EoV5J4zmlSj6H/VCxGLszkuBXYfm1n4IhIWNXRRl7rIQMqXKBQRKU7 XGhmL5Jui8RmVZIdMdGYXF/sroJ0ymqinP4WJ5nGPhxsp4bmMGGe45qaoimdHtyOThzW23tN+zaS 2+6Yv5Z7Dp3Cn6KV0gqmo9/EQrNz4n5R8MshDKI64usyl+Ity/lYXhvnXFZLhETqGW9l0fXPeBz7 b9MBZCY8I6jL89prIIRUJEbWHefew9SRWAwAug==
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2nsf/qIz9-4woF4Dpblq21R0R3dNg4MU>
Subject: Re: [I2nsf] [yang-doctors] [IPsec] [Last-Call] Yangdoctors last call review of draft-ietf-i2nsf-sdn-ipsec-flow-protection-08
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: Mon, 12 Oct 2020 19:08:08 -0000

--Apple-Mail=_9DBA0896-01DA-4AE8-AD6F-ED8776315628
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Hi Rob:

My apologies but I have just seen this e-mail. We were working on =
posting last v09 precisely today, assuming this was all clarified and =
the decision was to change the names as Tom suggested.

Regarding your comment, having "the notifications in the ikeless module =
as a feature" would not help. Let me explain. The ikeless module needs =
something inherent to operate, which are the notifications. It is not =
something optional for the ikeless module to implement.

Hope this helps.

Best Regards.

> El 12 oct 2020, a las 18:01, Rob Wilton (rwilton) =
<rwilton=3D40cisco.com@dmarc.ietf.org> escribi=C3=B3:
>=20
> Hi Rafa, authors,
> =20
> Just to check.
> =20
> Has there been any closure on the suggestion from Chris on =
=E2=80=9Cnotifications in the ikeless module as a feature"?  This would =
seem to be a fairly cheap & easy compromise.
> =20
> Thanks,
> Rob
> =20
> =20
> From: yang-doctors <yang-doctors-bounces@ietf.org> On Behalf Of Lou =
Berger
> Sent: 27 September 2020 15:26
> To: Christian Hopps <chopps@chopps.org>; Martin Bj=C3=B6rklund =
<mbj+ietf@4668.se>
> Cc: Robert Wilton <rwilton=3D40cisco.com@dmarc.ietf.org>; =
i2nsf@ietf.org; Gabriel Lopez <gabilm@um.es>; =
draft-ietf-i2nsf-sdn-ipsec-flow-protection.all@ietf.org; ipsec@ietf.org; =
last-call@ietf.org; Rafa Marin-Lopez <rafa@um.es>; yang-doctors@ietf.org
> Subject: Re: [yang-doctors] [IPsec] [Last-Call] [I2nsf] Yangdoctors =
last call review of draft-ietf-i2nsf-sdn-ipsec-flow-protection-08
> =20
> This is a sub-optimal compromise b/c all IPsec have SA databases even =
ones running IKE -- i.e., SA databases are common whether exposed in =
YANG or not -- but if it can move it forward perhaps good enough.
>=20
>=20
> Speaking as an interested party, I hope that some compromise / good =
enough solution is followed in the -09 version of  this draft.
> Lou
>=20
> On 9/23/2020 7:20 AM, Christian Hopps wrote:
> =20
>=20
>=20
> On Sep 23, 2020, at 6:58 AM, Martin Bj=C3=B6rklund <mbj+ietf@4668.se =
<mailto:mbj+ietf@4668.se>> wrote:
> =20
> Hi,
>=20
> Christian Hopps <chopps@chopps.org <mailto:chopps@chopps.org>> wrote:
>=20
>=20
>=20
>=20
> On Sep 23, 2020, at 5:29 AM, Rafa Marin-Lopez <rafa@um.es =
<mailto:rafa@um.es>> wrote:
>=20
>=20
>=20
>=20
> But I would like to check: My understanding is that the changes that
> Chris is proposing are pretty small.  I.e. move the SA structure under
> ipsec-common, and put it under a YANG feature.  Are you sure that it
> is impractical to accommodate this change which would allow a single
> ipsec module to be shared and extended via YANG augmentations?
>=20
>=20
> In the context of our I-D, if we move SAD structure to ipsec-common,
> what we are meaning is that IPsec SA configuration data (setting
> values to the SAD structure) are common to the IKE case and the
> IKE-less cases, which are not. It is confusing.
>=20
> Something defined in a common module but marked as a feature does not
> imply that that feature has to be implemented by an importing
> module. This is not confusing to YANG implementers or users I
> think. If we are just talking about document flow here, then a
> sentence saying "the SAD feature is not required to implement IKE
> functionality" is quite enough to clear that up I think.
>=20
> Another alternative could be to move these containers to another
> (new) module.
> =20
> It may also be enough to mark the notifications in the ikeless module =
as a feature I suppose. That is the actual thing I think non-SDN =
implementations would want to omit. The module name "ikeless" is not =
great in this case, but perhaps workable.
>=20
>=20
> This is a sub-optimal compromise b/c all IPsec have SA databases even =
ones running IKE -- i.e., SA databases are common whether exposed in =
YANG or not -- but if it can move it forward perhaps good enough.
>=20
>=20
> I'm definitely concerned about IETF process and real world usability =
here. These modules are basically workable for ipsec I think, they could =
be used by operators today. If we restart the entire process to redo =
this work for the more generic IPsec case it will probably be years =
before they are finished and in the field. This new work can be started, =
but why not have something usable in the meantime?
> =20
> Thanks,
> Chris.
> =20
>=20
>=20
> /martin
>=20
>=20
>=20
>=20
>=20
> Thanks,
> Chris.
>=20
>=20
> Moreover, the usage of feature means that, after all, this =
=E2=80=9Ccommon=E2=80=9D is
> not =E2=80=9Ccommon=E2=80=9D to both cases IKE case and IKE-less. =
Again, it seems
> confusing. In the IKE case, the SDN/I2NSF controller does not
> configure the SAD at all but the IKE implementation in the NSF. In our
> opinion, in order to properly add this IPsec SA operational state to
> the IKE case we should include operational data about the IPsec SAs
> (config false) to the ietf-ipsec-ike. Alternatively, we have certain
> operational data (ro) in the SAD structure in the IKE-less case. If
> only those are moved to the common part should be ok but we think it
> does not solve the problem.
>=20
> =20
> --=20
> last-call mailing list
> last-call@ietf.org <mailto:last-call@ietf.org>
> https://www.ietf.org/mailman/listinfo/last-call =
<https://www.ietf.org/mailman/listinfo/last-call>
>=20
>=20
>=20
> _______________________________________________
> IPsec mailing list
> IPsec@ietf.org <mailto:IPsec@ietf.org>
> https://www.ietf.org/mailman/listinfo/ipsec =
<https://www.ietf.org/mailman/listinfo/ipsec>_____________________________=
__________________
> I2nsf mailing list
> I2nsf@ietf.org
> 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
-------------------------------------------------------





--Apple-Mail=_9DBA0896-01DA-4AE8-AD6F-ED8776315628
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: after-white-space;" class=3D"">Hi =
Rob:<div class=3D""><br class=3D""></div><div class=3D"">My apologies =
but I have just seen this e-mail. We were working on posting last v09 =
precisely today, assuming this was all clarified and the decision was to =
change the names as Tom suggested.</div><div class=3D""><br =
class=3D""></div><div class=3D"">Regarding your comment, having "the =
notifications in the ikeless module as a feature" would not help. Let me =
explain. The ikeless module needs something inherent to operate, which =
are the notifications. It is not something optional for the ikeless =
module to implement.</div><div style=3D"caret-color: rgb(0, 0, 0); =
color: rgb(0, 0, 0);"><br class=3D""></div><div style=3D"caret-color: =
rgb(0, 0, 0); color: rgb(0, 0, 0);">Hope this helps.</div><div =
class=3D""><br class=3D""></div><div class=3D"">Best Regards.<br =
class=3D""><div><br class=3D""><blockquote type=3D"cite" class=3D""><div =
class=3D"">El 12 oct 2020, a las 18:01, Rob Wilton (rwilton) &lt;<a =
href=3D"mailto:rwilton=3D40cisco.com@dmarc.ietf.org" =
class=3D"">rwilton=3D40cisco.com@dmarc.ietf.org</a>&gt; =
escribi=C3=B3:</div><br class=3D"Apple-interchange-newline"><div =
class=3D""><div class=3D"WordSection1" style=3D"page: WordSection1; =
caret-color: rgb(0, 0, 0); font-family: Courier; font-size: 16px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none;"><div =
style=3D"margin: 0cm; font-size: 11pt; font-family: Calibri, =
sans-serif;" class=3D""><span class=3D"">Hi Rafa, authors,<o:p =
class=3D""></o:p></span></div><div style=3D"margin: 0cm; font-size: =
11pt; font-family: Calibri, sans-serif;" class=3D""><span class=3D""><o:p =
class=3D"">&nbsp;</o:p></span></div><div style=3D"margin: 0cm; =
font-size: 11pt; font-family: Calibri, sans-serif;" class=3D""><span =
class=3D"">Just to check.<o:p class=3D""></o:p></span></div><div =
style=3D"margin: 0cm; font-size: 11pt; font-family: Calibri, =
sans-serif;" class=3D""><span class=3D""><o:p =
class=3D"">&nbsp;</o:p></span></div><div style=3D"margin: 0cm; =
font-size: 11pt; font-family: Calibri, sans-serif;" class=3D""><span =
class=3D"">Has there been any closure on the suggestion from Chris on =
=E2=80=9C</span><span style=3D"" class=3D"">notifications in the ikeless =
module as a feature"?&nbsp; This would seem to be a fairly cheap &amp; =
easy compromise.<o:p class=3D""></o:p></span></div><div style=3D"margin: =
0cm; font-size: 11pt; font-family: Calibri, sans-serif;" class=3D""><span =
style=3D"" class=3D""><o:p class=3D"">&nbsp;</o:p></span></div><div =
style=3D"margin: 0cm; font-size: 11pt; font-family: Calibri, =
sans-serif;" class=3D""><span style=3D"" class=3D"">Thanks,<br =
class=3D"">Rob<o:p class=3D""></o:p></span></div><div style=3D"margin: =
0cm; font-size: 11pt; font-family: Calibri, sans-serif;" class=3D""><span =
style=3D"" class=3D""><o:p class=3D"">&nbsp;</o:p></span></div><div =
style=3D"margin: 0cm; font-size: 11pt; font-family: Calibri, =
sans-serif;" class=3D""><span class=3D""><o:p =
class=3D"">&nbsp;</o:p></span></div><div style=3D"border-style: none =
none none solid; border-left-width: 1.5pt; border-left-color: blue; =
padding: 0cm 0cm 0cm 4pt;" class=3D""><div class=3D""><div =
style=3D"border-style: solid none none; border-top-width: 1pt; =
border-top-color: rgb(225, 225, 225); padding: 3pt 0cm 0cm;" =
class=3D""><div style=3D"margin: 0cm; font-size: 11pt; font-family: =
Calibri, sans-serif;" class=3D""><b class=3D""><span lang=3D"EN-US" =
class=3D"">From:</span></b><span lang=3D"EN-US" class=3D""><span =
class=3D"Apple-converted-space">&nbsp;</span>yang-doctors &lt;<a =
href=3D"mailto:yang-doctors-bounces@ietf.org" =
class=3D"">yang-doctors-bounces@ietf.org</a>&gt;<span =
class=3D"Apple-converted-space">&nbsp;</span><b class=3D"">On Behalf =
Of<span class=3D"Apple-converted-space">&nbsp;</span></b>Lou Berger<br =
class=3D""><b class=3D"">Sent:</b><span =
class=3D"Apple-converted-space">&nbsp;</span>27 September 2020 15:26<br =
class=3D""><b class=3D"">To:</b><span =
class=3D"Apple-converted-space">&nbsp;</span>Christian Hopps &lt;<a =
href=3D"mailto:chopps@chopps.org" class=3D"">chopps@chopps.org</a>&gt;; =
Martin Bj=C3=B6rklund &lt;<a href=3D"mailto:mbj+ietf@4668.se" =
class=3D"">mbj+ietf@4668.se</a>&gt;<br class=3D""><b =
class=3D"">Cc:</b><span =
class=3D"Apple-converted-space">&nbsp;</span>Robert Wilton &lt;<a =
href=3D"mailto:rwilton=3D40cisco.com@dmarc.ietf.org" =
class=3D"">rwilton=3D40cisco.com@dmarc.ietf.org</a>&gt;; <a =
href=3D"mailto:i2nsf@ietf.org" class=3D"">i2nsf@ietf.org</a>; Gabriel =
Lopez &lt;<a href=3D"mailto:gabilm@um.es" class=3D"">gabilm@um.es</a>&gt;;=
 <a =
href=3D"mailto:draft-ietf-i2nsf-sdn-ipsec-flow-protection.all@ietf.org" =
class=3D"">draft-ietf-i2nsf-sdn-ipsec-flow-protection.all@ietf.org</a>; =
<a href=3D"mailto:ipsec@ietf.org" class=3D"">ipsec@ietf.org</a>; <a =
href=3D"mailto:last-call@ietf.org" class=3D"">last-call@ietf.org</a>; =
Rafa Marin-Lopez &lt;<a href=3D"mailto:rafa@um.es" =
class=3D"">rafa@um.es</a>&gt;; <a href=3D"mailto:yang-doctors@ietf.org" =
class=3D"">yang-doctors@ietf.org</a><br class=3D""><b =
class=3D"">Subject:</b><span =
class=3D"Apple-converted-space">&nbsp;</span>Re: [yang-doctors] [IPsec] =
[Last-Call] [I2nsf] Yangdoctors last call review of =
draft-ietf-i2nsf-sdn-ipsec-flow-protection-08<o:p =
class=3D""></o:p></span></div></div></div><div style=3D"margin: 0cm; =
font-size: 11pt; font-family: Calibri, sans-serif;" class=3D""><o:p =
class=3D"">&nbsp;</o:p></div><blockquote style=3D"margin-top: 5pt; =
margin-bottom: 5pt;" class=3D""><div class=3D""><div style=3D"margin: =
0cm; font-size: 11pt; font-family: Calibri, sans-serif;" class=3D"">This =
is a sub-optimal compromise b/c all IPsec have SA databases even ones =
running IKE -- i.e., SA databases are common whether exposed in YANG or =
not -- but if it can move it forward perhaps good enough.<o:p =
class=3D""></o:p></div></div><div class=3D""><div style=3D"margin: 0cm; =
font-size: 11pt; font-family: Calibri, sans-serif;" class=3D""><br =
class=3D""><br class=3D""><o:p =
class=3D""></o:p></div></div></blockquote><div style=3D"margin: 0cm; =
font-size: 11pt; font-family: Calibri, sans-serif;" class=3D"">Speaking =
as an interested party, I hope that some compromise / good enough =
solution is followed in the -09 version of&nbsp; this draft.<o:p =
class=3D""></o:p></div><p class=3D"">Lou<o:p class=3D""></o:p></p><div =
class=3D""><div style=3D"margin: 0cm; font-size: 11pt; font-family: =
Calibri, sans-serif;" class=3D"">On 9/23/2020 7:20 AM, Christian Hopps =
wrote:<o:p class=3D""></o:p></div></div><blockquote style=3D"margin-top: =
5pt; margin-bottom: 5pt;" class=3D""><div style=3D"margin: 0cm; =
font-size: 11pt; font-family: Calibri, sans-serif;" class=3D""><o:p =
class=3D"">&nbsp;</o:p></div><div class=3D""><div style=3D"margin: 0cm; =
font-size: 11pt; font-family: Calibri, sans-serif;" class=3D""><br =
class=3D""><br class=3D""><o:p class=3D""></o:p></div><blockquote =
style=3D"margin-top: 5pt; margin-bottom: 5pt;" class=3D""><div =
class=3D""><div style=3D"margin: 0cm; font-size: 11pt; font-family: =
Calibri, sans-serif;" class=3D"">On Sep 23, 2020, at 6:58 AM, Martin =
Bj=C3=B6rklund &lt;<a href=3D"mailto:mbj+ietf@4668.se" style=3D"color: =
blue; text-decoration: underline;" class=3D"">mbj+ietf@4668.se</a>&gt; =
wrote:<o:p class=3D""></o:p></div></div><div style=3D"margin: 0cm; =
font-size: 11pt; font-family: Calibri, sans-serif;" class=3D""><o:p =
class=3D"">&nbsp;</o:p></div><div class=3D""><div style=3D"margin: 0cm; =
font-size: 11pt; font-family: Calibri, sans-serif;" class=3D""><span =
style=3D"font-size: 10.5pt; font-family: Menlo-Regular, serif;" =
class=3D"">Hi,<br class=3D""><br class=3D"">Christian Hopps =
&lt;</span><a href=3D"mailto:chopps@chopps.org" style=3D"color: blue; =
text-decoration: underline;" class=3D""><span style=3D"font-size: =
10.5pt; font-family: Menlo-Regular, serif;" =
class=3D"">chopps@chopps.org</span></a><span style=3D"font-size: 10.5pt; =
font-family: Menlo-Regular, serif;" class=3D"">&gt; wrote:<br =
style=3D"caret-color: rgb(0, 0, 0); font-variant-caps: normal; =
text-align: start; -webkit-text-stroke-width: 0px; word-spacing: 0px;" =
class=3D""><br class=3D""></span><o:p class=3D""></o:p></div><blockquote =
style=3D"margin-top: 5pt; margin-bottom: 5pt;" class=3D""><div =
style=3D"margin: 0cm; font-size: 11pt; font-family: Calibri, =
sans-serif;" class=3D""><span style=3D"font-size: 10.5pt; font-family: =
Menlo-Regular, serif;" class=3D""><br class=3D""><br class=3D""><br =
class=3D""><o:p class=3D""></o:p></span></div><blockquote =
style=3D"margin-top: 5pt; margin-bottom: 5pt;" class=3D""><div =
style=3D"margin: 0cm; font-size: 11pt; font-family: Calibri, =
sans-serif;" class=3D""><span style=3D"font-size: 10.5pt; font-family: =
Menlo-Regular, serif;" class=3D"">On Sep 23, 2020, at 5:29 AM, Rafa =
Marin-Lopez &lt;<a href=3D"mailto:rafa@um.es" style=3D"color: blue; =
text-decoration: underline;" class=3D"">rafa@um.es</a>&gt; wrote:<br =
class=3D""><br class=3D""><br class=3D""><o:p =
class=3D""></o:p></span></div><blockquote style=3D"margin-top: 5pt; =
margin-bottom: 5pt;" class=3D""><div style=3D"margin: 0cm; font-size: =
11pt; font-family: Calibri, sans-serif;" class=3D""><span =
style=3D"font-size: 10.5pt; font-family: Menlo-Regular, serif;" =
class=3D""><br class=3D""><br class=3D"">But I would like to check: My =
understanding is that the changes that<br class=3D"">Chris is proposing =
are pretty small. &nbsp;I.e. move the SA structure under<br =
class=3D"">ipsec-common, and put it under a YANG feature. &nbsp;Are you =
sure that it<br class=3D"">is impractical to accommodate this change =
which would allow a single<br class=3D"">ipsec module to be shared and =
extended via YANG augmentations?<o:p =
class=3D""></o:p></span></div></blockquote><div style=3D"margin: 0cm; =
font-size: 11pt; font-family: Calibri, sans-serif;" class=3D""><span =
style=3D"font-size: 10.5pt; font-family: Menlo-Regular, serif;" =
class=3D""><br class=3D""><br class=3D"">In the context of our I-D, if =
we move SAD structure to ipsec-common,<br class=3D"">what we are meaning =
is that IPsec SA configuration data (setting<br class=3D"">values to the =
SAD structure) are common to the IKE case and the<br class=3D"">IKE-less =
cases, which are not. It is confusing.<o:p =
class=3D""></o:p></span></div></blockquote><div style=3D"margin: 0cm; =
font-size: 11pt; font-family: Calibri, sans-serif;" class=3D""><span =
style=3D"font-size: 10.5pt; font-family: Menlo-Regular, serif;" =
class=3D""><br class=3D"">Something defined in a common module but =
marked as a feature does not<br class=3D"">imply that that feature has =
to be implemented by an importing<br class=3D"">module. This is not =
confusing to YANG implementers or users I<br class=3D"">think. If we are =
just talking about document flow here, then a<br class=3D"">sentence =
saying "the SAD feature is not required to implement IKE<br =
class=3D"">functionality" is quite enough to clear that up I think.<o:p =
class=3D""></o:p></span></div></blockquote><div style=3D"margin: 0cm; =
font-size: 11pt; font-family: Calibri, sans-serif;" class=3D""><span =
style=3D"font-size: 10.5pt; font-family: Menlo-Regular, serif;" =
class=3D""><br class=3D"">Another alternative could be to move these =
containers to another<br class=3D"">(new) module.</span><o:p =
class=3D""></o:p></div></div></blockquote><div class=3D""><div =
style=3D"margin: 0cm; font-size: 11pt; font-family: Calibri, =
sans-serif;" class=3D""><o:p class=3D"">&nbsp;</o:p></div></div><div =
style=3D"margin: 0cm; font-size: 11pt; font-family: Calibri, =
sans-serif;" class=3D""><span style=3D"" class=3D"">It may also be =
enough to mark the notifications in the ikeless module as a feature I =
suppose. That is the actual thing I think non-SDN implementations would =
want to omit. The module name "ikeless" is not great in this case, but =
perhaps workable.</span><o:p class=3D""></o:p></div></div><div =
class=3D""><div style=3D"margin: 0cm; font-size: 11pt; font-family: =
Calibri, sans-serif;" class=3D""><span style=3D"" class=3D""><br =
class=3D""><br class=3D""></span><o:p class=3D""></o:p></div></div><div =
class=3D""><div style=3D"margin: 0cm; font-size: 11pt; font-family: =
Calibri, sans-serif;" class=3D""><span style=3D"" class=3D"">This is a =
sub-optimal compromise b/c all IPsec have SA databases even ones running =
IKE -- i.e., SA databases are common whether exposed in YANG or not -- =
but if it can move it forward perhaps good enough.</span><o:p =
class=3D""></o:p></div></div><div class=3D""><div style=3D"margin: 0cm; =
font-size: 11pt; font-family: Calibri, sans-serif;" class=3D""><span =
style=3D"" class=3D""><br class=3D""><br class=3D""></span><o:p =
class=3D""></o:p></div></div><div class=3D""><div style=3D"margin: 0cm; =
font-size: 11pt; font-family: Calibri, sans-serif;" class=3D""><span =
style=3D"" class=3D"">I'm definitely concerned about IETF process and =
real world usability here. These modules are basically workable for =
ipsec I think, they could be used by operators today. If we restart the =
entire process to redo this work for the more generic IPsec case it will =
probably be years before they are finished and in the field. This new =
work can be started, but why not have something usable in the =
meantime?</span><o:p class=3D""></o:p></div></div><div class=3D""><div =
style=3D"margin: 0cm; font-size: 11pt; font-family: Calibri, =
sans-serif;" class=3D""><o:p class=3D"">&nbsp;</o:p></div></div><div =
class=3D""><div style=3D"margin: 0cm; font-size: 11pt; font-family: =
Calibri, sans-serif;" class=3D"">Thanks,<o:p =
class=3D""></o:p></div></div><div class=3D""><div style=3D"margin: 0cm; =
font-size: 11pt; font-family: Calibri, sans-serif;" class=3D"">Chris.<o:p =
class=3D""></o:p></div></div><div class=3D""><div style=3D"margin: 0cm; =
font-size: 11pt; font-family: Calibri, sans-serif;" class=3D""><o:p =
class=3D"">&nbsp;</o:p></div></div><div class=3D""><blockquote =
style=3D"margin-top: 5pt; margin-bottom: 5pt;" class=3D""><div =
class=3D""><div style=3D"margin: 0cm; font-size: 11pt; font-family: =
Calibri, sans-serif;" class=3D""><span style=3D"font-size: 10.5pt; =
font-family: Menlo-Regular, serif;" class=3D""><br class=3D""><br =
class=3D"">/martin<br class=3D""><br class=3D""><br class=3D""><br =
style=3D"caret-color: rgb(0, 0, 0); font-variant-caps: normal; =
text-align: start; -webkit-text-stroke-width: 0px; word-spacing: 0px;" =
class=3D""><br class=3D""></span><o:p class=3D""></o:p></div><blockquote =
style=3D"margin-top: 5pt; margin-bottom: 5pt;" class=3D""><div =
style=3D"margin: 0cm; font-size: 11pt; font-family: Calibri, =
sans-serif;" class=3D""><span style=3D"font-size: 10.5pt; font-family: =
Menlo-Regular, serif;" class=3D""><br class=3D"">Thanks,<br =
class=3D"">Chris.<br class=3D""><br class=3D""><br class=3D""><o:p =
class=3D""></o:p></span></div><blockquote style=3D"margin-top: 5pt; =
margin-bottom: 5pt;" class=3D""><p class=3D"MsoNormal" style=3D"margin: =
0cm 0cm 12pt; font-size: 11pt; font-family: Calibri, sans-serif;"><span =
style=3D"font-size: 10.5pt; font-family: Menlo-Regular, serif;" =
class=3D"">Moreover, the usage of feature means that, after all, this =
=E2=80=9Ccommon=E2=80=9D is<br class=3D"">not =E2=80=9Ccommon=E2=80=9D =
to both cases IKE case and IKE-less. Again, it seems<br =
class=3D"">confusing. In the IKE case, the SDN/I2NSF controller does =
not<br class=3D"">configure the SAD at all but the IKE implementation in =
the NSF. In our<br class=3D"">opinion, in order to properly add this =
IPsec SA operational state to<br class=3D"">the IKE case we should =
include operational data about the IPsec SAs<br class=3D"">(config =
false) to the ietf-ipsec-ike. Alternatively, we have certain<br =
class=3D"">operational data (ro) in the SAD structure in the IKE-less =
case. If<br class=3D"">only those are moved to the common part should be =
ok but we think it<br class=3D"">does not solve the problem.<o:p =
class=3D""></o:p></span></p></blockquote><div style=3D"margin: 0cm; =
font-size: 11pt; font-family: Calibri, sans-serif;" class=3D""><span =
style=3D"font-size: 10.5pt; font-family: Menlo-Regular, serif;" =
class=3D""><o:p class=3D"">&nbsp;</o:p></span></div></blockquote><div =
style=3D"margin: 0cm; font-size: 11pt; font-family: Calibri, =
sans-serif;" class=3D""><span style=3D"font-size: 10.5pt; font-family: =
Menlo-Regular, serif;" class=3D"">--<span =
class=3D"apple-converted-space">&nbsp;</span><br class=3D"">last-call =
mailing list<br class=3D""></span><a href=3D"mailto:last-call@ietf.org" =
style=3D"color: blue; text-decoration: underline;" class=3D""><span =
style=3D"font-size: 10.5pt; font-family: Menlo-Regular, serif;" =
class=3D"">last-call@ietf.org</span></a><span style=3D"font-size: =
10.5pt; font-family: Menlo-Regular, serif;" class=3D""><br =
class=3D""></span><a =
href=3D"https://www.ietf.org/mailman/listinfo/last-call" style=3D"color: =
blue; text-decoration: underline;" class=3D""><span style=3D"font-size: =
10.5pt; font-family: Menlo-Regular, serif;" =
class=3D"">https://www.ietf.org/mailman/listinfo/last-call</span></a><o:p =
class=3D""></o:p></div></div></blockquote></div><div style=3D"margin: =
0cm; font-size: 11pt; font-family: Calibri, sans-serif;" class=3D""><br =
class=3D""><br class=3D""><br class=3D""><o:p class=3D""></o:p></div><pre =
style=3D"margin: 0cm; font-size: 10pt; font-family: &quot;Courier =
New&quot;;" class=3D"">_______________________________________________<o:p=
 class=3D""></o:p></pre><pre style=3D"margin: 0cm; font-size: 10pt; =
font-family: &quot;Courier New&quot;;" class=3D"">IPsec mailing list<o:p =
class=3D""></o:p></pre><pre style=3D"margin: 0cm; font-size: 10pt; =
font-family: &quot;Courier New&quot;;" class=3D""><a =
href=3D"mailto:IPsec@ietf.org" style=3D"color: blue; text-decoration: =
underline;" class=3D"">IPsec@ietf.org</a><o:p class=3D""></o:p></pre><pre =
style=3D"margin: 0cm; font-size: 10pt; font-family: &quot;Courier =
New&quot;;" class=3D""><a =
href=3D"https://www.ietf.org/mailman/listinfo/ipsec" style=3D"color: =
blue; text-decoration: underline;" =
class=3D"">https://www.ietf.org/mailman/listinfo/ipsec</a><o:p =
class=3D""></o:p></pre></blockquote></div></div><span =
style=3D"caret-color: rgb(0, 0, 0); font-family: Courier; font-size: =
16px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none; float: none; =
display: inline !important;" =
class=3D"">_______________________________________________</span><br =
style=3D"caret-color: rgb(0, 0, 0); font-family: Courier; font-size: =
16px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none;" class=3D""><span =
style=3D"caret-color: rgb(0, 0, 0); font-family: Courier; font-size: =
16px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none; float: none; =
display: inline !important;" class=3D"">I2nsf mailing list</span><br =
style=3D"caret-color: rgb(0, 0, 0); font-family: Courier; font-size: =
16px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none;" class=3D""><span =
style=3D"caret-color: rgb(0, 0, 0); font-family: Courier; font-size: =
16px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none; float: none; =
display: inline !important;" class=3D""><a href=3D"mailto:I2nsf@ietf.org" =
class=3D"">I2nsf@ietf.org</a></span><br style=3D"caret-color: rgb(0, 0, =
0); font-family: Courier; font-size: 16px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;" class=3D""><span style=3D"caret-color: rgb(0, 0, =
0); font-family: Courier; font-size: 16px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none; float: none; display: inline !important;" =
class=3D""><a href=3D"https://www.ietf.org/mailman/listinfo/i2nsf" =
class=3D"">https://www.ietf.org/mailman/listinfo/i2nsf</a></span></div></b=
lockquote></div><br class=3D""><div class=3D"">
<div style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space;" class=3D""><div style=3D"color: =
rgb(0, 0, 0); font-family: Courier; font-size: 16px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
orphans: auto; text-align: start; text-indent: 0px; text-transform: =
none; white-space: normal; widows: auto; word-spacing: 0px; =
-webkit-text-stroke-width: =
0px;">-------------------------------------------------------<br =
class=3D"">Rafa Marin-Lopez, PhD<br class=3D"">Dept. Information =
and&nbsp;Communications&nbsp;Engineering (DIIC)<br class=3D"">Faculty of =
Computer&nbsp;Science-University of&nbsp;Murcia<br class=3D"">30100 =
Murcia - Spain<br class=3D"">Telf: +34868888501 Fax:&nbsp;+34868884151 =
<a href=3D"mailto:rafa@um.es" class=3D"">e-mail:&nbsp;rafa@um.es</a><br =
class=3D"">-------------------------------------------------------</div><d=
iv style=3D"color: rgb(0, 0, 0); font-family: Courier; font-size: 16px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; orphans: auto; text-align: start; text-indent: =
0px; text-transform: none; white-space: normal; widows: auto; =
word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=3D""><br =
class=3D""></div><br class=3D"Apple-interchange-newline"></div><br =
class=3D"Apple-interchange-newline">
</div>
<br class=3D""></div></body></html>=

--Apple-Mail=_9DBA0896-01DA-4AE8-AD6F-ED8776315628--


From nobody Mon Oct 12 13:22:01 2020
Return-Path: <chopps@chopps.org>
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 969CF3A0924; Mon, 12 Oct 2020 13:21:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.895
X-Spam-Level: 
X-Spam-Status: No, score=-1.895 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 rxD5fOY3MAXT; Mon, 12 Oct 2020 13:21:54 -0700 (PDT)
Received: from smtp.chopps.org (smtp.chopps.org [54.88.81.56]) by ietfa.amsl.com (Postfix) with ESMTP id 63B633A090B; Mon, 12 Oct 2020 13:21:54 -0700 (PDT)
Received: from stubbs.int.chopps.org (047-050-069-038.biz.spectrum.com [47.50.69.38]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by smtp.chopps.org (Postfix) with ESMTPSA id 0B0366046D; Mon, 12 Oct 2020 20:21:52 +0000 (UTC)
From: Christian Hopps <chopps@chopps.org>
Message-Id: <10116C35-8FBF-4914-9846-883D2C7F7A11@chopps.org>
Content-Type: multipart/signed; boundary="Apple-Mail=_CA75578A-46A3-479A-96A1-3B569DBF40FB"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\))
Date: Mon, 12 Oct 2020 16:21:51 -0400
In-Reply-To: <E827743C-74A1-42CE-9765-7ECD062D8E41@um.es>
Cc: Christian Hopps <chopps@chopps.org>, Robert Wilton <rwilton=40cisco.com@dmarc.ietf.org>, =?utf-8?Q?Martin_Bj=C3=B6rklund?= <mbj+ietf@4668.se>, "i2nsf@ietf.org" <i2nsf@ietf.org>, Gabriel Lopez <gabilm@um.es>, "draft-ietf-i2nsf-sdn-ipsec-flow-protection.all@ietf.org" <draft-ietf-i2nsf-sdn-ipsec-flow-protection.all@ietf.org>,  "ipsec@ietf.org" <ipsec@ietf.org>, "last-call@ietf.org" <last-call@ietf.org>, "yang-doctors@ietf.org" <yang-doctors@ietf.org>, Lou Berger <lberger@labn.net>
To: Rafa Marin-Lopez <rafa@um.es>
References: <MN2PR11MB4366E30B3C372D13B391AE07B53B0@MN2PR11MB4366.namprd11.prod.outlook.com> <2B88888E-A264-4D81-A8DA-9C6225E83E0E@um.es> <70A0A406-0742-4F28-A5A4-8D539B160E24@chopps.org> <20200923.125826.1562347052257995146.id@4668.se> <CBC552B2-6039-48E8-988D-4F2BA3FD6B2E@chopps.org> <023fc27b-f86e-ed71-0c8f-d270c338f08c@labn.net> <MN2PR11MB43662E1711367EDE9A066452B5070@MN2PR11MB4366.namprd11.prod.outlook.com> <E827743C-74A1-42CE-9765-7ECD062D8E41@um.es>
X-Mailer: Apple Mail (2.3608.120.23.2.4)
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2nsf/jxYk1S_aD4bxRTqKB-KHvqOlC9Q>
Subject: Re: [I2nsf] [IPsec] [yang-doctors] [Last-Call] Yangdoctors last call review of draft-ietf-i2nsf-sdn-ipsec-flow-protection-08
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: Mon, 12 Oct 2020 20:21:57 -0000

--Apple-Mail=_CA75578A-46A3-479A-96A1-3B569DBF40FB
Content-Type: multipart/alternative;
	boundary="Apple-Mail=_A3E336BA-8ED5-454D-AC4A-3BF68BEB56D8"


--Apple-Mail=_A3E336BA-8ED5-454D-AC4A-3BF68BEB56D8
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8



> On Oct 12, 2020, at 3:07 PM, Rafa Marin-Lopez <rafa@um.es> wrote:
>=20
> Hi Rob:
>=20
> My apologies but I have just seen this e-mail. We were working on =
posting last v09 precisely today, assuming this was all clarified and =
the decision was to change the names as Tom suggested.
>=20
> Regarding your comment, having "the notifications in the ikeless =
module as a feature" would not help. Let me explain. The ikeless module =
needs something inherent to operate, which are the notifications. It is =
not something optional for the ikeless module to implement.

That does not seem like enough justification for not having the module =
be usable in such a broader fashion. It is obvious to anyone =
implementing this for your use case that the notifications must be =
implemented. If you feel that it is not obvious for some reason a simple =
sentence can make that clear. Although I would think that sentence might =
start with the word "Obviously, ..." :)

Thanks,
Chris.

>=20
> Hope this helps.
>=20
> Best Regards.
>=20
>> El 12 oct 2020, a las 18:01, Rob Wilton (rwilton) =
<rwilton=3D40cisco.com@dmarc.ietf.org =
<mailto:rwilton=3D40cisco.com@dmarc.ietf.org>> escribi=C3=B3:
>>=20
>> Hi Rafa, authors,
>>=20
>> Just to check.
>>=20
>> Has there been any closure on the suggestion from Chris on =
=E2=80=9Cnotifications in the ikeless module as a feature"?  This would =
seem to be a fairly cheap & easy compromise.
>>=20
>> Thanks,
>> Rob
>>=20
>>=20
>> From: yang-doctors <yang-doctors-bounces@ietf.org =
<mailto:yang-doctors-bounces@ietf.org>> On Behalf Of Lou Berger
>> Sent: 27 September 2020 15:26
>> To: Christian Hopps <chopps@chopps.org <mailto:chopps@chopps.org>>; =
Martin Bj=C3=B6rklund <mbj+ietf@4668.se <mailto:mbj+ietf@4668.se>>
>> Cc: Robert Wilton <rwilton=3D40cisco.com@dmarc.ietf.org =
<mailto:rwilton=3D40cisco.com@dmarc.ietf.org>>; i2nsf@ietf.org =
<mailto:i2nsf@ietf.org>; Gabriel Lopez <gabilm@um.es =
<mailto:gabilm@um.es>>; =
draft-ietf-i2nsf-sdn-ipsec-flow-protection.all@ietf.org =
<mailto:draft-ietf-i2nsf-sdn-ipsec-flow-protection.all@ietf.org>; =
ipsec@ietf.org <mailto:ipsec@ietf.org>; last-call@ietf.org =
<mailto:last-call@ietf.org>; Rafa Marin-Lopez <rafa@um.es =
<mailto:rafa@um.es>>; yang-doctors@ietf.org =
<mailto:yang-doctors@ietf.org>
>> Subject: Re: [yang-doctors] [IPsec] [Last-Call] [I2nsf] Yangdoctors =
last call review of draft-ietf-i2nsf-sdn-ipsec-flow-protection-08
>>=20
>> This is a sub-optimal compromise b/c all IPsec have SA databases even =
ones running IKE -- i.e., SA databases are common whether exposed in =
YANG or not -- but if it can move it forward perhaps good enough.
>>=20
>>=20
>> Speaking as an interested party, I hope that some compromise / good =
enough solution is followed in the -09 version of  this draft.
>> Lou
>>=20
>> On 9/23/2020 7:20 AM, Christian Hopps wrote:
>>=20
>>=20
>>=20
>> On Sep 23, 2020, at 6:58 AM, Martin Bj=C3=B6rklund <mbj+ietf@4668.se =
<mailto:mbj+ietf@4668.se>> wrote:
>>=20
>> Hi,
>>=20
>> Christian Hopps <chopps@chopps.org <mailto:chopps@chopps.org>> wrote:
>>=20
>>=20
>>=20
>>=20
>> On Sep 23, 2020, at 5:29 AM, Rafa Marin-Lopez <rafa@um.es =
<mailto:rafa@um.es>> wrote:
>>=20
>>=20
>>=20
>>=20
>> But I would like to check: My understanding is that the changes that
>> Chris is proposing are pretty small.  I.e. move the SA structure =
under
>> ipsec-common, and put it under a YANG feature.  Are you sure that it
>> is impractical to accommodate this change which would allow a single
>> ipsec module to be shared and extended via YANG augmentations?
>>=20
>>=20
>> In the context of our I-D, if we move SAD structure to ipsec-common,
>> what we are meaning is that IPsec SA configuration data (setting
>> values to the SAD structure) are common to the IKE case and the
>> IKE-less cases, which are not. It is confusing.
>>=20
>> Something defined in a common module but marked as a feature does not
>> imply that that feature has to be implemented by an importing
>> module. This is not confusing to YANG implementers or users I
>> think. If we are just talking about document flow here, then a
>> sentence saying "the SAD feature is not required to implement IKE
>> functionality" is quite enough to clear that up I think.
>>=20
>> Another alternative could be to move these containers to another
>> (new) module.
>>=20
>> It may also be enough to mark the notifications in the ikeless module =
as a feature I suppose. That is the actual thing I think non-SDN =
implementations would want to omit. The module name "ikeless" is not =
great in this case, but perhaps workable.
>>=20
>>=20
>> This is a sub-optimal compromise b/c all IPsec have SA databases even =
ones running IKE -- i.e., SA databases are common whether exposed in =
YANG or not -- but if it can move it forward perhaps good enough.
>>=20
>>=20
>> I'm definitely concerned about IETF process and real world usability =
here. These modules are basically workable for ipsec I think, they could =
be used by operators today. If we restart the entire process to redo =
this work for the more generic IPsec case it will probably be years =
before they are finished and in the field. This new work can be started, =
but why not have something usable in the meantime?
>>=20
>> Thanks,
>> Chris.
>>=20
>>=20
>>=20
>> /martin
>>=20
>>=20
>>=20
>>=20
>>=20
>> Thanks,
>> Chris.
>>=20
>>=20
>> Moreover, the usage of feature means that, after all, this =
=E2=80=9Ccommon=E2=80=9D is
>> not =E2=80=9Ccommon=E2=80=9D to both cases IKE case and IKE-less. =
Again, it seems
>> confusing. In the IKE case, the SDN/I2NSF controller does not
>> configure the SAD at all but the IKE implementation in the NSF. In =
our
>> opinion, in order to properly add this IPsec SA operational state to
>> the IKE case we should include operational data about the IPsec SAs
>> (config false) to the ietf-ipsec-ike. Alternatively, we have certain
>> operational data (ro) in the SAD structure in the IKE-less case. If
>> only those are moved to the common part should be ok but we think it
>> does not solve the problem.
>>=20
>>=20
>> --
>> last-call mailing list
>> last-call@ietf.org <mailto:last-call@ietf.org>
>> https://www.ietf.org/mailman/listinfo/last-call =
<https://www.ietf.org/mailman/listinfo/last-call>
>>=20
>>=20
>>=20
>> _______________________________________________
>> IPsec mailing list
>> IPsec@ietf.org <mailto:IPsec@ietf.org>
>> https://www.ietf.org/mailman/listinfo/ipsec =
<https://www.ietf.org/mailman/listinfo/ipsec>_____________________________=
__________________
>> 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:=C2=A0rafa@um.es =
<mailto:rafa@um.es>
> -------------------------------------------------------
>=20
>=20
>=20
>=20
> _______________________________________________
> IPsec mailing list
> IPsec@ietf.org <mailto:IPsec@ietf.org>
> https://www.ietf.org/mailman/listinfo/ipsec =
<https://www.ietf.org/mailman/listinfo/ipsec>

--Apple-Mail=_A3E336BA-8ED5-454D-AC4A-3BF68BEB56D8
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: after-white-space;" class=3D""><br =
class=3D""><div><br class=3D""><blockquote type=3D"cite" class=3D""><div =
class=3D"">On Oct 12, 2020, at 3:07 PM, Rafa Marin-Lopez &lt;<a =
href=3D"mailto:rafa@um.es" class=3D"">rafa@um.es</a>&gt; wrote:</div><br =
class=3D"Apple-interchange-newline"><div class=3D""><span =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
18px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none; float: none; =
display: inline !important;" class=3D"">Hi Rob:</span><div class=3D"" =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
18px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none;"><br =
class=3D""></div><div class=3D"" style=3D"caret-color: rgb(0, 0, 0); =
font-family: Helvetica; font-size: 18px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;">My apologies but I have just seen this e-mail. =
We were working on posting last v09 precisely today, assuming this was =
all clarified and the decision was to change the names as Tom =
suggested.</div><div class=3D"" style=3D"caret-color: rgb(0, 0, 0); =
font-family: Helvetica; font-size: 18px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;"><br class=3D""></div><div class=3D"" =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
18px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none;">Regarding your =
comment, having "the notifications in the ikeless module as a feature" =
would not help. Let me explain. The ikeless module needs something =
inherent to operate, which are the notifications. It is not something =
optional for the ikeless module to =
implement.</div></div></blockquote><div><br class=3D""></div><div>That =
does not seem like enough justification for not having the module be =
usable in such a broader fashion. It is obvious to anyone implementing =
this for your use case that the notifications must be implemented. If =
you feel that it is not obvious for some reason a simple sentence can =
make that clear. Although I would think that sentence might start with =
the word "Obviously, ..." :)</div><div><br =
class=3D""></div><div>Thanks,</div><div>Chris.</div><br =
class=3D""><blockquote type=3D"cite" class=3D""><div class=3D""><div =
style=3D"font-family: Helvetica; font-size: 18px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none; caret-color: rgb(0, 0, 0);" class=3D""><br =
class=3D""></div><div style=3D"font-family: Helvetica; font-size: 18px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none; caret-color: =
rgb(0, 0, 0);" class=3D"">Hope this helps.</div><div class=3D"" =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
18px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none;"><br =
class=3D""></div><div class=3D"" style=3D"caret-color: rgb(0, 0, 0); =
font-family: Helvetica; font-size: 18px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;">Best Regards.<br class=3D""><div class=3D""><br =
class=3D""><blockquote type=3D"cite" class=3D""><div class=3D"">El 12 =
oct 2020, a las 18:01, Rob Wilton (rwilton) &lt;<a =
href=3D"mailto:rwilton=3D40cisco.com@dmarc.ietf.org" =
class=3D"">rwilton=3D40cisco.com@dmarc.ietf.org</a>&gt; =
escribi=C3=B3:</div><br class=3D"Apple-interchange-newline"><div =
class=3D""><div class=3D"WordSection1" style=3D"page: WordSection1; =
caret-color: rgb(0, 0, 0); font-family: Courier; font-size: 16px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none;"><div class=3D"" =
style=3D"margin: 0cm; font-size: 11pt; font-family: Calibri, =
sans-serif;"><span class=3D"">Hi Rafa, authors,<o:p =
class=3D""></o:p></span></div><div class=3D"" style=3D"margin: 0cm; =
font-size: 11pt; font-family: Calibri, sans-serif;"><span class=3D""><o:p =
class=3D"">&nbsp;</o:p></span></div><div class=3D"" style=3D"margin: =
0cm; font-size: 11pt; font-family: Calibri, sans-serif;"><span =
class=3D"">Just to check.<o:p class=3D""></o:p></span></div><div =
class=3D"" style=3D"margin: 0cm; font-size: 11pt; font-family: Calibri, =
sans-serif;"><span class=3D""><o:p =
class=3D"">&nbsp;</o:p></span></div><div class=3D"" style=3D"margin: =
0cm; font-size: 11pt; font-family: Calibri, sans-serif;"><span =
class=3D"">Has there been any closure on the suggestion from Chris on =
=E2=80=9C</span><span class=3D"">notifications in the ikeless module as =
a feature"?&nbsp; This would seem to be a fairly cheap &amp; easy =
compromise.<o:p class=3D""></o:p></span></div><div class=3D"" =
style=3D"margin: 0cm; font-size: 11pt; font-family: Calibri, =
sans-serif;"><span class=3D""><o:p =
class=3D"">&nbsp;</o:p></span></div><div class=3D"" style=3D"margin: =
0cm; font-size: 11pt; font-family: Calibri, sans-serif;"><span =
class=3D"">Thanks,<br class=3D"">Rob<o:p =
class=3D""></o:p></span></div><div class=3D"" style=3D"margin: 0cm; =
font-size: 11pt; font-family: Calibri, sans-serif;"><span class=3D""><o:p =
class=3D"">&nbsp;</o:p></span></div><div class=3D"" style=3D"margin: =
0cm; font-size: 11pt; font-family: Calibri, sans-serif;"><span =
class=3D""><o:p class=3D"">&nbsp;</o:p></span></div><div class=3D"" =
style=3D"border-style: none none none solid; border-left-width: 1.5pt; =
border-left-color: blue; padding: 0cm 0cm 0cm 4pt;"><div class=3D""><div =
class=3D"" style=3D"border-style: solid none none; border-top-width: =
1pt; border-top-color: rgb(225, 225, 225); padding: 3pt 0cm 0cm;"><div =
class=3D"" style=3D"margin: 0cm; font-size: 11pt; font-family: Calibri, =
sans-serif;"><b class=3D""><span lang=3D"EN-US" =
class=3D"">From:</span></b><span lang=3D"EN-US" class=3D""><span =
class=3D"Apple-converted-space">&nbsp;</span>yang-doctors &lt;<a =
href=3D"mailto:yang-doctors-bounces@ietf.org" =
class=3D"">yang-doctors-bounces@ietf.org</a>&gt;<span =
class=3D"Apple-converted-space">&nbsp;</span><b class=3D"">On Behalf =
Of<span class=3D"Apple-converted-space">&nbsp;</span></b>Lou Berger<br =
class=3D""><b class=3D"">Sent:</b><span =
class=3D"Apple-converted-space">&nbsp;</span>27 September 2020 15:26<br =
class=3D""><b class=3D"">To:</b><span =
class=3D"Apple-converted-space">&nbsp;</span>Christian Hopps &lt;<a =
href=3D"mailto:chopps@chopps.org" class=3D"">chopps@chopps.org</a>&gt;; =
Martin Bj=C3=B6rklund &lt;<a href=3D"mailto:mbj+ietf@4668.se" =
class=3D"">mbj+ietf@4668.se</a>&gt;<br class=3D""><b =
class=3D"">Cc:</b><span =
class=3D"Apple-converted-space">&nbsp;</span>Robert Wilton &lt;<a =
href=3D"mailto:rwilton=3D40cisco.com@dmarc.ietf.org" =
class=3D"">rwilton=3D40cisco.com@dmarc.ietf.org</a>&gt;;<span =
class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"mailto:i2nsf@ietf.org" class=3D"">i2nsf@ietf.org</a>; Gabriel =
Lopez &lt;<a href=3D"mailto:gabilm@um.es" =
class=3D"">gabilm@um.es</a>&gt;;<span =
class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"mailto:draft-ietf-i2nsf-sdn-ipsec-flow-protection.all@ietf.org" =
class=3D"">draft-ietf-i2nsf-sdn-ipsec-flow-protection.all@ietf.org</a>;<sp=
an class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"mailto:ipsec@ietf.org" class=3D"">ipsec@ietf.org</a>;<span =
class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"mailto:last-call@ietf.org" class=3D"">last-call@ietf.org</a>; =
Rafa Marin-Lopez &lt;<a href=3D"mailto:rafa@um.es" =
class=3D"">rafa@um.es</a>&gt;;<span =
class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"mailto:yang-doctors@ietf.org" =
class=3D"">yang-doctors@ietf.org</a><br class=3D""><b =
class=3D"">Subject:</b><span =
class=3D"Apple-converted-space">&nbsp;</span>Re: [yang-doctors] [IPsec] =
[Last-Call] [I2nsf] Yangdoctors last call review of =
draft-ietf-i2nsf-sdn-ipsec-flow-protection-08<o:p =
class=3D""></o:p></span></div></div></div><div class=3D"" style=3D"margin:=
 0cm; font-size: 11pt; font-family: Calibri, sans-serif;"><o:p =
class=3D"">&nbsp;</o:p></div><blockquote class=3D"" style=3D"margin-top: =
5pt; margin-bottom: 5pt;"><div class=3D""><div class=3D"" style=3D"margin:=
 0cm; font-size: 11pt; font-family: Calibri, sans-serif;">This is a =
sub-optimal compromise b/c all IPsec have SA databases even ones running =
IKE -- i.e., SA databases are common whether exposed in YANG or not -- =
but if it can move it forward perhaps good enough.<o:p =
class=3D""></o:p></div></div><div class=3D""><div class=3D"" =
style=3D"margin: 0cm; font-size: 11pt; font-family: Calibri, =
sans-serif;"><br class=3D""><br class=3D""><o:p =
class=3D""></o:p></div></div></blockquote><div class=3D"" style=3D"margin:=
 0cm; font-size: 11pt; font-family: Calibri, sans-serif;">Speaking as an =
interested party, I hope that some compromise / good enough solution is =
followed in the -09 version of&nbsp; this draft.<o:p =
class=3D""></o:p></div><p class=3D"">Lou<o:p class=3D""></o:p></p><div =
class=3D""><div class=3D"" style=3D"margin: 0cm; font-size: 11pt; =
font-family: Calibri, sans-serif;">On 9/23/2020 7:20 AM, Christian Hopps =
wrote:<o:p class=3D""></o:p></div></div><blockquote class=3D"" =
style=3D"margin-top: 5pt; margin-bottom: 5pt;"><div class=3D"" =
style=3D"margin: 0cm; font-size: 11pt; font-family: Calibri, =
sans-serif;"><o:p class=3D"">&nbsp;</o:p></div><div class=3D""><div =
class=3D"" style=3D"margin: 0cm; font-size: 11pt; font-family: Calibri, =
sans-serif;"><br class=3D""><br class=3D""><o:p =
class=3D""></o:p></div><blockquote class=3D"" style=3D"margin-top: 5pt; =
margin-bottom: 5pt;"><div class=3D""><div class=3D"" style=3D"margin: =
0cm; font-size: 11pt; font-family: Calibri, sans-serif;">On Sep 23, =
2020, at 6:58 AM, Martin Bj=C3=B6rklund &lt;<a =
href=3D"mailto:mbj+ietf@4668.se" class=3D"" style=3D"color: blue; =
text-decoration: underline;">mbj+ietf@4668.se</a>&gt; wrote:<o:p =
class=3D""></o:p></div></div><div class=3D"" style=3D"margin: 0cm; =
font-size: 11pt; font-family: Calibri, sans-serif;"><o:p =
class=3D"">&nbsp;</o:p></div><div class=3D""><div class=3D"" =
style=3D"margin: 0cm; font-size: 11pt; font-family: Calibri, =
sans-serif;"><span class=3D"" style=3D"font-size: 10.5pt; font-family: =
Menlo-Regular, serif;">Hi,<br class=3D""><br class=3D"">Christian Hopps =
&lt;</span><a href=3D"mailto:chopps@chopps.org" class=3D"" style=3D"color:=
 blue; text-decoration: underline;"><span class=3D"" style=3D"font-size: =
10.5pt; font-family: Menlo-Regular, =
serif;">chopps@chopps.org</span></a><span class=3D"" style=3D"font-size: =
10.5pt; font-family: Menlo-Regular, serif;">&gt; wrote:<br class=3D"" =
style=3D"caret-color: rgb(0, 0, 0); font-variant-caps: normal; =
text-align: start; -webkit-text-stroke-width: 0px; word-spacing: =
0px;"><br class=3D""></span><o:p class=3D""></o:p></div><blockquote =
class=3D"" style=3D"margin-top: 5pt; margin-bottom: 5pt;"><div class=3D"" =
style=3D"margin: 0cm; font-size: 11pt; font-family: Calibri, =
sans-serif;"><span class=3D"" style=3D"font-size: 10.5pt; font-family: =
Menlo-Regular, serif;"><br class=3D""><br class=3D""><br class=3D""><o:p =
class=3D""></o:p></span></div><blockquote class=3D"" style=3D"margin-top: =
5pt; margin-bottom: 5pt;"><div class=3D"" style=3D"margin: 0cm; =
font-size: 11pt; font-family: Calibri, sans-serif;"><span class=3D"" =
style=3D"font-size: 10.5pt; font-family: Menlo-Regular, serif;">On Sep =
23, 2020, at 5:29 AM, Rafa Marin-Lopez &lt;<a href=3D"mailto:rafa@um.es" =
class=3D"" style=3D"color: blue; text-decoration: =
underline;">rafa@um.es</a>&gt; wrote:<br class=3D""><br class=3D""><br =
class=3D""><o:p class=3D""></o:p></span></div><blockquote class=3D"" =
style=3D"margin-top: 5pt; margin-bottom: 5pt;"><div class=3D"" =
style=3D"margin: 0cm; font-size: 11pt; font-family: Calibri, =
sans-serif;"><span class=3D"" style=3D"font-size: 10.5pt; font-family: =
Menlo-Regular, serif;"><br class=3D""><br class=3D"">But I would like to =
check: My understanding is that the changes that<br class=3D"">Chris is =
proposing are pretty small. &nbsp;I.e. move the SA structure under<br =
class=3D"">ipsec-common, and put it under a YANG feature. &nbsp;Are you =
sure that it<br class=3D"">is impractical to accommodate this change =
which would allow a single<br class=3D"">ipsec module to be shared and =
extended via YANG augmentations?<o:p =
class=3D""></o:p></span></div></blockquote><div class=3D"" =
style=3D"margin: 0cm; font-size: 11pt; font-family: Calibri, =
sans-serif;"><span class=3D"" style=3D"font-size: 10.5pt; font-family: =
Menlo-Regular, serif;"><br class=3D""><br class=3D"">In the context of =
our I-D, if we move SAD structure to ipsec-common,<br class=3D"">what we =
are meaning is that IPsec SA configuration data (setting<br =
class=3D"">values to the SAD structure) are common to the IKE case and =
the<br class=3D"">IKE-less cases, which are not. It is confusing.<o:p =
class=3D""></o:p></span></div></blockquote><div class=3D"" =
style=3D"margin: 0cm; font-size: 11pt; font-family: Calibri, =
sans-serif;"><span class=3D"" style=3D"font-size: 10.5pt; font-family: =
Menlo-Regular, serif;"><br class=3D"">Something defined in a common =
module but marked as a feature does not<br class=3D"">imply that that =
feature has to be implemented by an importing<br class=3D"">module. This =
is not confusing to YANG implementers or users I<br class=3D"">think. If =
we are just talking about document flow here, then a<br =
class=3D"">sentence saying "the SAD feature is not required to implement =
IKE<br class=3D"">functionality" is quite enough to clear that up I =
think.<o:p class=3D""></o:p></span></div></blockquote><div class=3D"" =
style=3D"margin: 0cm; font-size: 11pt; font-family: Calibri, =
sans-serif;"><span class=3D"" style=3D"font-size: 10.5pt; font-family: =
Menlo-Regular, serif;"><br class=3D"">Another alternative could be to =
move these containers to another<br class=3D"">(new) module.</span><o:p =
class=3D""></o:p></div></div></blockquote><div class=3D""><div class=3D"" =
style=3D"margin: 0cm; font-size: 11pt; font-family: Calibri, =
sans-serif;"><o:p class=3D"">&nbsp;</o:p></div></div><div class=3D"" =
style=3D"margin: 0cm; font-size: 11pt; font-family: Calibri, =
sans-serif;"><span class=3D"">It may also be enough to mark the =
notifications in the ikeless module as a feature I suppose. That is the =
actual thing I think non-SDN implementations would want to omit. The =
module name "ikeless" is not great in this case, but perhaps =
workable.</span><o:p class=3D""></o:p></div></div><div class=3D""><div =
class=3D"" style=3D"margin: 0cm; font-size: 11pt; font-family: Calibri, =
sans-serif;"><span class=3D""><br class=3D""><br class=3D""></span><o:p =
class=3D""></o:p></div></div><div class=3D""><div class=3D"" =
style=3D"margin: 0cm; font-size: 11pt; font-family: Calibri, =
sans-serif;"><span class=3D"">This is a sub-optimal compromise b/c all =
IPsec have SA databases even ones running IKE -- i.e., SA databases are =
common whether exposed in YANG or not -- but if it can move it forward =
perhaps good enough.</span><o:p class=3D""></o:p></div></div><div =
class=3D""><div class=3D"" style=3D"margin: 0cm; font-size: 11pt; =
font-family: Calibri, sans-serif;"><span class=3D""><br class=3D""><br =
class=3D""></span><o:p class=3D""></o:p></div></div><div class=3D""><div =
class=3D"" style=3D"margin: 0cm; font-size: 11pt; font-family: Calibri, =
sans-serif;"><span class=3D"">I'm definitely concerned about IETF =
process and real world usability here. These modules are basically =
workable for ipsec I think, they could be used by operators today. If we =
restart the entire process to redo this work for the more generic IPsec =
case it will probably be years before they are finished and in the =
field. This new work can be started, but why not have something usable =
in the meantime?</span><o:p class=3D""></o:p></div></div><div =
class=3D""><div class=3D"" style=3D"margin: 0cm; font-size: 11pt; =
font-family: Calibri, sans-serif;"><o:p =
class=3D"">&nbsp;</o:p></div></div><div class=3D""><div class=3D"" =
style=3D"margin: 0cm; font-size: 11pt; font-family: Calibri, =
sans-serif;">Thanks,<o:p class=3D""></o:p></div></div><div class=3D""><div=
 class=3D"" style=3D"margin: 0cm; font-size: 11pt; font-family: Calibri, =
sans-serif;">Chris.<o:p class=3D""></o:p></div></div><div class=3D""><div =
class=3D"" style=3D"margin: 0cm; font-size: 11pt; font-family: Calibri, =
sans-serif;"><o:p class=3D"">&nbsp;</o:p></div></div><div =
class=3D""><blockquote class=3D"" style=3D"margin-top: 5pt; =
margin-bottom: 5pt;"><div class=3D""><div class=3D"" style=3D"margin: =
0cm; font-size: 11pt; font-family: Calibri, sans-serif;"><span class=3D"" =
style=3D"font-size: 10.5pt; font-family: Menlo-Regular, serif;"><br =
class=3D""><br class=3D"">/martin<br class=3D""><br class=3D""><br =
class=3D""><br class=3D"" style=3D"caret-color: rgb(0, 0, 0); =
font-variant-caps: normal; text-align: start; -webkit-text-stroke-width: =
0px; word-spacing: 0px;"><br class=3D""></span><o:p =
class=3D""></o:p></div><blockquote class=3D"" style=3D"margin-top: 5pt; =
margin-bottom: 5pt;"><div class=3D"" style=3D"margin: 0cm; font-size: =
11pt; font-family: Calibri, sans-serif;"><span class=3D"" =
style=3D"font-size: 10.5pt; font-family: Menlo-Regular, serif;"><br =
class=3D"">Thanks,<br class=3D"">Chris.<br class=3D""><br class=3D""><br =
class=3D""><o:p class=3D""></o:p></span></div><blockquote class=3D"" =
style=3D"margin-top: 5pt; margin-bottom: 5pt;"><p class=3D"MsoNormal" =
style=3D"margin: 0cm 0cm 12pt; font-size: 11pt; font-family: Calibri, =
sans-serif;"><span class=3D"" style=3D"font-size: 10.5pt; font-family: =
Menlo-Regular, serif;">Moreover, the usage of feature means that, after =
all, this =E2=80=9Ccommon=E2=80=9D is<br class=3D"">not =E2=80=9Ccommon=E2=
=80=9D to both cases IKE case and IKE-less. Again, it seems<br =
class=3D"">confusing. In the IKE case, the SDN/I2NSF controller does =
not<br class=3D"">configure the SAD at all but the IKE implementation in =
the NSF. In our<br class=3D"">opinion, in order to properly add this =
IPsec SA operational state to<br class=3D"">the IKE case we should =
include operational data about the IPsec SAs<br class=3D"">(config =
false) to the ietf-ipsec-ike. Alternatively, we have certain<br =
class=3D"">operational data (ro) in the SAD structure in the IKE-less =
case. If<br class=3D"">only those are moved to the common part should be =
ok but we think it<br class=3D"">does not solve the problem.<o:p =
class=3D""></o:p></span></p></blockquote><div class=3D"" style=3D"margin: =
0cm; font-size: 11pt; font-family: Calibri, sans-serif;"><span class=3D"" =
style=3D"font-size: 10.5pt; font-family: Menlo-Regular, serif;"><o:p =
class=3D"">&nbsp;</o:p></span></div></blockquote><div class=3D"" =
style=3D"margin: 0cm; font-size: 11pt; font-family: Calibri, =
sans-serif;"><span class=3D"" style=3D"font-size: 10.5pt; font-family: =
Menlo-Regular, serif;">--<span =
class=3D"apple-converted-space">&nbsp;</span><br class=3D"">last-call =
mailing list<br class=3D""></span><a href=3D"mailto:last-call@ietf.org" =
class=3D"" style=3D"color: blue; text-decoration: underline;"><span =
class=3D"" style=3D"font-size: 10.5pt; font-family: Menlo-Regular, =
serif;">last-call@ietf.org</span></a><span class=3D"" style=3D"font-size: =
10.5pt; font-family: Menlo-Regular, serif;"><br class=3D""></span><a =
href=3D"https://www.ietf.org/mailman/listinfo/last-call" class=3D"" =
style=3D"color: blue; text-decoration: underline;"><span class=3D"" =
style=3D"font-size: 10.5pt; font-family: Menlo-Regular, =
serif;">https://www.ietf.org/mailman/listinfo/last-call</span></a><o:p =
class=3D""></o:p></div></div></blockquote></div><div class=3D"" =
style=3D"margin: 0cm; font-size: 11pt; font-family: Calibri, =
sans-serif;"><br class=3D""><br class=3D""><br class=3D""><o:p =
class=3D""></o:p></div><pre class=3D"" style=3D"margin: 0cm; font-size: =
10pt; font-family: &quot;Courier =
New&quot;;">_______________________________________________<o:p =
class=3D""></o:p></pre><pre class=3D"" style=3D"margin: 0cm; font-size: =
10pt; font-family: &quot;Courier New&quot;;">IPsec mailing list<o:p =
class=3D""></o:p></pre><pre class=3D"" style=3D"margin: 0cm; font-size: =
10pt; font-family: &quot;Courier New&quot;;"><a =
href=3D"mailto:IPsec@ietf.org" class=3D"" style=3D"color: blue; =
text-decoration: underline;">IPsec@ietf.org</a><o:p =
class=3D""></o:p></pre><pre class=3D"" style=3D"margin: 0cm; font-size: =
10pt; font-family: &quot;Courier New&quot;;"><a =
href=3D"https://www.ietf.org/mailman/listinfo/ipsec" class=3D"" =
style=3D"color: blue; text-decoration: =
underline;">https://www.ietf.org/mailman/listinfo/ipsec</a><o:p =
class=3D""></o:p></pre></blockquote></div></div><span class=3D"" =
style=3D"caret-color: rgb(0, 0, 0); font-family: Courier; font-size: =
16px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none; float: none; =
display: inline =
!important;">_______________________________________________</span><br =
class=3D"" style=3D"caret-color: rgb(0, 0, 0); font-family: Courier; =
font-size: 16px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none;"><span class=3D"" style=3D"caret-color: rgb(0, 0, 0); font-family: =
Courier; font-size: 16px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none; float: none; display: inline !important;">I2nsf mailing =
list</span><br class=3D"" style=3D"caret-color: rgb(0, 0, 0); =
font-family: Courier; font-size: 16px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;"><span class=3D"" style=3D"caret-color: rgb(0, 0, =
0); font-family: Courier; font-size: 16px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none; float: none; display: inline !important;"><a =
href=3D"mailto:I2nsf@ietf.org" class=3D"">I2nsf@ietf.org</a></span><br =
class=3D"" style=3D"caret-color: rgb(0, 0, 0); font-family: Courier; =
font-size: 16px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none;"><span class=3D"" style=3D"caret-color: rgb(0, 0, 0); font-family: =
Courier; font-size: 16px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none; float: none; display: inline !important;"><a =
href=3D"https://www.ietf.org/mailman/listinfo/i2nsf" =
class=3D"">https://www.ietf.org/mailman/listinfo/i2nsf</a></span></div></b=
lockquote></div><br class=3D""><div class=3D""><div class=3D"" =
style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; line-break: =
after-white-space;"><div style=3D"font-family: Courier; font-size: 16px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px;" =
class=3D"">-------------------------------------------------------<br =
class=3D"">Rafa Marin-Lopez, PhD<br class=3D"">Dept. Information =
and&nbsp;Communications&nbsp;Engineering (DIIC)<br class=3D"">Faculty of =
Computer&nbsp;Science-University of&nbsp;Murcia<br class=3D"">30100 =
Murcia - Spain<br class=3D"">Telf: +34868888501 =
Fax:&nbsp;+34868884151<span =
class=3D"Apple-converted-space">&nbsp;</span><a href=3D"mailto:rafa@um.es"=
 class=3D"">e-mail:&nbsp;rafa@um.es</a><br =
class=3D"">-------------------------------------------------------</div><d=
iv class=3D"" style=3D"font-family: Courier; font-size: 16px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px;"><br class=3D""></div><br =
class=3D"Apple-interchange-newline"></div><br =
class=3D"Apple-interchange-newline"></div><br class=3D""></div><span =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
18px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none; float: none; =
display: inline !important;" =
class=3D"">_______________________________________________</span><br =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
18px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none;" class=3D""><span =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
18px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none; float: none; =
display: inline !important;" class=3D"">IPsec mailing list</span><br =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
18px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none;" class=3D""><a =
href=3D"mailto:IPsec@ietf.org" style=3D"font-family: Helvetica; =
font-size: 18px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; orphans: auto; text-align: =
start; text-indent: 0px; text-transform: none; white-space: normal; =
widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; =
-webkit-text-stroke-width: 0px;" class=3D"">IPsec@ietf.org</a><br =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
18px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none;" class=3D""><a =
href=3D"https://www.ietf.org/mailman/listinfo/ipsec" style=3D"font-family:=
 Helvetica; font-size: 18px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; orphans: auto; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; =
-webkit-text-stroke-width: 0px;" =
class=3D"">https://www.ietf.org/mailman/listinfo/ipsec</a></div></blockquo=
te></div><br class=3D""></body></html>=

--Apple-Mail=_A3E336BA-8ED5-454D-AC4A-3BF68BEB56D8--

--Apple-Mail=_CA75578A-46A3-479A-96A1-3B569DBF40FB
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEm56yH/NF+m1FHa6lLh2DDte4MCUFAl+Eut8ACgkQLh2DDte4
MCXHhA/+M3wdyFzaBTgirCquTnoK07Hce7bOWNP38z9DrtANKox21wItyQhSd0is
bdIantdAQhcrOMrM953daB3f0laifg46Ykuw7WEzBrx1JhoX0f0B/P4VDwypLqv4
thuGzjX3oJrXTd82NzsGZgF6T4+BefNbx1zPEvSYCWXe+9zri+/qvaVtAnHO0iox
eYUp22ujd7E9wWWbLGZG7bVjZqSUeujch5XbAI2O1ylkLbOc6a3GJeJtg9Q3rLuX
HwTrsag3px4R2KxKRcvl0+39g+3c8gcUu27phTZIkbfe3MW8JwS9N2euI+/sIlK3
KTPcuoWbo549GutHnFtg7RMSGYtFMvFxiNusJIWYwpxodRR+RiKYWOZb5nO3NtCq
+vPztz5UomNU266icjmwdSvbIxjixWegojqmOKWMzYb7i9tlQgbzqTjkw4gVRwdY
l36h7HFYBbT7RgGEfkeLUEKBYUojEIfFbnWd6Vaoh3GRALKe4b1DLvrOh2CHroJy
2Vs3fkH+t/aJFQY/UtOfbhoNDjRCDfS8anvvv8RGbF4v0BuXRCIIYJ9ZVeLg/V6T
paCrookEL/JzcswPg+51rKtFOmMZCGwL4vDwMCFnQw9LpnSdKctgnodz4VI7ZY11
SCiJV1erZAoMapxmE+hHn9R3Zh8SbiL7VFFCqSHrp0TjA0sPvSs=
=iJtB
-----END PGP SIGNATURE-----

--Apple-Mail=_CA75578A-46A3-479A-96A1-3B569DBF40FB--


From nobody Mon Oct 12 21:16:25 2020
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 65F3D3A0925; Mon, 12 Oct 2020 21:16:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.096
X-Spam-Level: 
X-Spam-Status: No, score=-2.096 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, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, 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=um.es
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 PKWTI6TUdyF2; Mon, 12 Oct 2020 21:16:16 -0700 (PDT)
Received: from mx02.puc.rediris.es (outbound6sev.lav.puc.rediris.es [130.206.19.181]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E8F623A09A4; Mon, 12 Oct 2020 21:16:15 -0700 (PDT)
Received: from xenon44.um.es (xenon44.um.es [155.54.212.171]) by mx02.puc.rediris.es  with ESMTP id 09D4G1Ct032462-09D4G1Cu032462; Tue, 13 Oct 2020 06:16:01 +0200
Received: from localhost (localhost [127.0.0.1]) by xenon44.um.es (Postfix) with ESMTP id 30B611FF01; Tue, 13 Oct 2020 06:16:01 +0200 (CEST)
X-Virus-Scanned: by antispam in UMU at xenon44.um.es
Received: from xenon44.um.es ([127.0.0.1]) by localhost (xenon44.um.es [127.0.0.1]) (amavisd-new, port 10024) with LMTP id Vn3D3uA8q_wJ; Tue, 13 Oct 2020 06:16:01 +0200 (CEST)
Received: from [192.168.1.33] (135.red-79-150-250.dynamicip.rima-tde.net [79.150.250.135]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: rafa@um.es) by xenon44.um.es (Postfix) with ESMTPSA id C4A662024E; Tue, 13 Oct 2020 06:15:53 +0200 (CEST)
From: Rafa Marin-Lopez <rafa@um.es>
Message-Id: <B3282660-5C6A-4B69-8CFC-57AFBCE2B544@um.es>
Content-Type: multipart/alternative; boundary="Apple-Mail=_86C75A4C-578C-4DFD-A1B4-2555C14193A2"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.14\))
Date: Tue, 13 Oct 2020 06:15:52 +0200
In-Reply-To: <10116C35-8FBF-4914-9846-883D2C7F7A11@chopps.org>
Cc: Rafa Marin-Lopez <rafa@um.es>, "i2nsf@ietf.org" <i2nsf@ietf.org>, Gabriel Lopez <gabilm@um.es>, "draft-ietf-i2nsf-sdn-ipsec-flow-protection.all@ietf.org" <draft-ietf-i2nsf-sdn-ipsec-flow-protection.all@ietf.org>,  "ipsec@ietf.org" <ipsec@ietf.org>, "last-call@ietf.org" <last-call@ietf.org>, =?utf-8?Q?Martin_Bj=C3=B6rklund?= <mbj+ietf@4668.se>, "yang-doctors@ietf.org" <yang-doctors@ietf.org>, Lou Berger <lberger@labn.net>
To: Christian Hopps <chopps@chopps.org>, "Rob Wilton (rwilton)" <rwilton@cisco.com>
References: <MN2PR11MB4366E30B3C372D13B391AE07B53B0@MN2PR11MB4366.namprd11.prod.outlook.com> <2B88888E-A264-4D81-A8DA-9C6225E83E0E@um.es> <70A0A406-0742-4F28-A5A4-8D539B160E24@chopps.org> <20200923.125826.1562347052257995146.id@4668.se> <CBC552B2-6039-48E8-988D-4F2BA3FD6B2E@chopps.org> <023fc27b-f86e-ed71-0c8f-d270c338f08c@labn.net> <MN2PR11MB43662E1711367EDE9A066452B5070@MN2PR11MB4366.namprd11.prod.outlook.com> <E827743C-74A1-42CE-9765-7ECD062D8E41@um.es> <10116C35-8FBF-4914-9846-883D2C7F7A11@chopps.org>
X-Mailer: Apple Mail (2.3445.104.14)
X-FEAS-SPF: spf-result=pass, ip=155.54.212.171, helo=xenon44.um.es, mailFrom=rafa@um.es
Authentication-Results: mx02.puc.rediris.es; spf=pass (rediris.es: domain of rafa@um.es designates 155.54.212.171 as permitted sender) smtp.mailfrom=rafa@um.es
X-FE-Policy-ID: 2:15:0: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=BlaINpGGh4b1aMAXRbmZzd6saaXUWKt8dRmRumfZ74U=; b=gPJJTGFEv8NWSvZrcjKj/POeGXScjJVtRRThAZSlRUzQAfC8KUBj62Ur+nLhvwvW6+G6HSQ1QoLG b/Emqs8L/4n41QlFvGgtNJbDcvqDjyeukf/7eNkoXRlXowPgcbAKVOCvmojncJSPMiuemo2w8zvJ gucvetwcuEmwGfs393AbdzIR+48GB5ErjjdpnzZb0sweyCx9s7uqV0STiTftUXtYJpZMakzcN+en OPTHfDw9MTblcu5a3CkFkxUqX1Hoq5mY6SZ7Yx7GylpxPz9wv/xW9QxYvs2olvP6dnlnbW/PH8Ku mRBmPPUzAUmTswiC0rglfdr70POmAX1+K8AX4Q==
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2nsf/wTzB0Ann_uxx751WdosuSQ_tRIE>
Subject: Re: [I2nsf] [IPsec] [yang-doctors] [Last-Call] Yangdoctors last call review of draft-ietf-i2nsf-sdn-ipsec-flow-protection-08
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: Tue, 13 Oct 2020 04:16:20 -0000

--Apple-Mail=_86C75A4C-578C-4DFD-A1B4-2555C14193A2
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Hi Christian (, Rob):

Thanks for your comments. We really appreciate them. Please see some =
comments inline.

> El 12 oct 2020, a las 22:21, Christian Hopps <chopps@chopps.org> =
escribi=C3=B3:
>=20
>=20
>=20
>> On Oct 12, 2020, at 3:07 PM, Rafa Marin-Lopez <rafa@um.es =
<mailto:rafa@um.es>> wrote:
>>=20
>> Hi Rob:
>>=20
>> My apologies but I have just seen this e-mail. We were working on =
posting last v09 precisely today, assuming this was all clarified and =
the decision was to change the names as Tom suggested.
>>=20
>> Regarding your comment, having "the notifications in the ikeless =
module as a feature" would not help. Let me explain. The ikeless module =
needs something inherent to operate, which are the notifications. It is =
not something optional for the ikeless module to implement.
>=20
> That does not seem like enough justification for not having the module =
be usable in such a broader fashion. It is obvious to anyone =
implementing this for your use case that the notifications must be =
implemented. If you feel that it is not obvious for some reason a simple =
sentence can make that clear. Although I would think that sentence might =
start with the word "Obviously, ..." :)

As you may remember we gave several justifications about why these =
changes are not correct in the context of the I2NSF work. Let me send =
you the link to avoid repeating myself :)=20

https://mailarchive.ietf.org/arch/msg/i2nsf/IZyRrrTZu7tVm5Kpqe2mw5-kZ1w/ =
<https://mailarchive.ietf.org/arch/msg/i2nsf/IZyRrrTZu7tVm5Kpqe2mw5-kZ1w/>=
=20

Thus, the change =E2=80=9Cthe notifications in the ikeless module as a =
feature=E2=80=9D is just the tip of the iceberg of a bigger change =
discussed in that link (moving SAD container to the common module). In =
other words, just simply adding "the notifications in the ikeless module =
as a feature=E2=80=9D is not useful and does not help. In fact, the =
notifications must be defined in the ikeless module, and adding a =
feature in the ikeless module would not make any sense.=20

As a consequence, the resolution was to move forward with a pragmatic =
approach at this point of time, by changing the names of the modules =
(and prefixes) to refer to the I2NSF work.

Best Regards.

>=20
> Thanks,
> Chris.
>=20
>>=20
>> Hope this helps.
>>=20
>> Best Regards.
>>=20
>>> El 12 oct 2020, a las 18:01, Rob Wilton (rwilton) =
<rwilton=3D40cisco.com@dmarc.ietf.org =
<mailto:rwilton=3D40cisco.com@dmarc.ietf.org>> escribi=C3=B3:
>>>=20
>>> Hi Rafa, authors,
>>> =20
>>> Just to check.
>>> =20
>>> Has there been any closure on the suggestion from Chris on =
=E2=80=9Cnotifications in the ikeless module as a feature"?  This would =
seem to be a fairly cheap & easy compromise.
>>> =20
>>> Thanks,
>>> Rob
>>> =20
>>> =20
>>> From: yang-doctors <yang-doctors-bounces@ietf.org =
<mailto:yang-doctors-bounces@ietf.org>> On Behalf Of Lou Berger
>>> Sent: 27 September 2020 15:26
>>> To: Christian Hopps <chopps@chopps.org <mailto:chopps@chopps.org>>; =
Martin Bj=C3=B6rklund <mbj+ietf@4668.se <mailto:mbj+ietf@4668.se>>
>>> Cc: Robert Wilton <rwilton=3D40cisco.com@dmarc.ietf.org =
<mailto:rwilton=3D40cisco.com@dmarc.ietf.org>>; i2nsf@ietf.org =
<mailto:i2nsf@ietf.org>; Gabriel Lopez <gabilm@um.es =
<mailto:gabilm@um.es>>; =
draft-ietf-i2nsf-sdn-ipsec-flow-protection.all@ietf.org =
<mailto:draft-ietf-i2nsf-sdn-ipsec-flow-protection.all@ietf.org>; =
ipsec@ietf.org <mailto:ipsec@ietf.org>; last-call@ietf.org =
<mailto:last-call@ietf.org>; Rafa Marin-Lopez <rafa@um.es =
<mailto:rafa@um.es>>; yang-doctors@ietf.org =
<mailto:yang-doctors@ietf.org>
>>> Subject: Re: [yang-doctors] [IPsec] [Last-Call] [I2nsf] Yangdoctors =
last call review of draft-ietf-i2nsf-sdn-ipsec-flow-protection-08
>>> =20
>>> This is a sub-optimal compromise b/c all IPsec have SA databases =
even ones running IKE -- i.e., SA databases are common whether exposed =
in YANG or not -- but if it can move it forward perhaps good enough.
>>>=20
>>>=20
>>> Speaking as an interested party, I hope that some compromise / good =
enough solution is followed in the -09 version of  this draft.
>>> Lou
>>>=20
>>> On 9/23/2020 7:20 AM, Christian Hopps wrote:
>>> =20
>>>=20
>>>=20
>>> On Sep 23, 2020, at 6:58 AM, Martin Bj=C3=B6rklund <mbj+ietf@4668.se =
<mailto:mbj+ietf@4668.se>> wrote:
>>> =20
>>> Hi,
>>>=20
>>> Christian Hopps <chopps@chopps.org <mailto:chopps@chopps.org>> =
wrote:
>>>=20
>>>=20
>>>=20
>>>=20
>>> On Sep 23, 2020, at 5:29 AM, Rafa Marin-Lopez <rafa@um.es =
<mailto:rafa@um.es>> wrote:
>>>=20
>>>=20
>>>=20
>>>=20
>>> But I would like to check: My understanding is that the changes that
>>> Chris is proposing are pretty small.  I.e. move the SA structure =
under
>>> ipsec-common, and put it under a YANG feature.  Are you sure that it
>>> is impractical to accommodate this change which would allow a single
>>> ipsec module to be shared and extended via YANG augmentations?
>>>=20
>>>=20
>>> In the context of our I-D, if we move SAD structure to ipsec-common,
>>> what we are meaning is that IPsec SA configuration data (setting
>>> values to the SAD structure) are common to the IKE case and the
>>> IKE-less cases, which are not. It is confusing.
>>>=20
>>> Something defined in a common module but marked as a feature does =
not
>>> imply that that feature has to be implemented by an importing
>>> module. This is not confusing to YANG implementers or users I
>>> think. If we are just talking about document flow here, then a
>>> sentence saying "the SAD feature is not required to implement IKE
>>> functionality" is quite enough to clear that up I think.
>>>=20
>>> Another alternative could be to move these containers to another
>>> (new) module.
>>> =20
>>> It may also be enough to mark the notifications in the ikeless =
module as a feature I suppose. That is the actual thing I think non-SDN =
implementations would want to omit. The module name "ikeless" is not =
great in this case, but perhaps workable.
>>>=20
>>>=20
>>> This is a sub-optimal compromise b/c all IPsec have SA databases =
even ones running IKE -- i.e., SA databases are common whether exposed =
in YANG or not -- but if it can move it forward perhaps good enough.
>>>=20
>>>=20
>>> I'm definitely concerned about IETF process and real world usability =
here. These modules are basically workable for ipsec I think, they could =
be used by operators today. If we restart the entire process to redo =
this work for the more generic IPsec case it will probably be years =
before they are finished and in the field. This new work can be started, =
but why not have something usable in the meantime?
>>> =20
>>> Thanks,
>>> Chris.
>>> =20
>>>=20
>>>=20
>>> /martin
>>>=20
>>>=20
>>>=20
>>>=20
>>>=20
>>> Thanks,
>>> Chris.
>>>=20
>>>=20
>>> Moreover, the usage of feature means that, after all, this =
=E2=80=9Ccommon=E2=80=9D is
>>> not =E2=80=9Ccommon=E2=80=9D to both cases IKE case and IKE-less. =
Again, it seems
>>> confusing. In the IKE case, the SDN/I2NSF controller does not
>>> configure the SAD at all but the IKE implementation in the NSF. In =
our
>>> opinion, in order to properly add this IPsec SA operational state to
>>> the IKE case we should include operational data about the IPsec SAs
>>> (config false) to the ietf-ipsec-ike. Alternatively, we have certain
>>> operational data (ro) in the SAD structure in the IKE-less case. If
>>> only those are moved to the common part should be ok but we think it
>>> does not solve the problem.
>>>=20
>>> =20
>>> --=20
>>> last-call mailing list
>>> last-call@ietf.org <mailto:last-call@ietf.org>
>>> https://www.ietf.org/mailman/listinfo/last-call =
<https://www.ietf.org/mailman/listinfo/last-call>
>>>=20
>>>=20
>>>=20
>>> _______________________________________________
>>> IPsec mailing list
>>> IPsec@ietf.org <mailto:IPsec@ietf.org>
>>> https://www.ietf.org/mailman/listinfo/ipsec =
<https://www.ietf.org/mailman/listinfo/ipsec>_____________________________=
__________________
>>> 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:=C2=A0rafa@um.es =
<mailto:rafa@um.es>
>> -------------------------------------------------------
>>=20
>>=20
>>=20
>>=20
>> _______________________________________________
>> IPsec mailing list
>> IPsec@ietf.org <mailto:IPsec@ietf.org>
>> https://www.ietf.org/mailman/listinfo/ipsec =
<https://www.ietf.org/mailman/listinfo/ipsec>
> _______________________________________________
> 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
-------------------------------------------------------





--Apple-Mail=_86C75A4C-578C-4DFD-A1B4-2555C14193A2
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: after-white-space;" class=3D"">Hi =
Christian (, Rob):<div class=3D""><br class=3D""></div><div =
class=3D"">Thanks for your comments. We really appreciate them. Please =
see some comments inline.<br class=3D""><div><br class=3D""><blockquote =
type=3D"cite" class=3D""><div class=3D"">El 12 oct 2020, a las 22:21, =
Christian Hopps &lt;<a href=3D"mailto:chopps@chopps.org" =
class=3D"">chopps@chopps.org</a>&gt; escribi=C3=B3:</div><br =
class=3D"Apple-interchange-newline"><div class=3D""><div =
style=3D"caret-color: rgb(0, 0, 0); font-family: Courier; font-size: =
16px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none;" class=3D""><br =
class=3D"Apple-interchange-newline"><br class=3D""><blockquote =
type=3D"cite" class=3D""><div class=3D"">On Oct 12, 2020, at 3:07 PM, =
Rafa Marin-Lopez &lt;<a href=3D"mailto:rafa@um.es" =
class=3D"">rafa@um.es</a>&gt; wrote:</div><br =
class=3D"Apple-interchange-newline"><div class=3D""><span class=3D"" =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
18px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none; float: none; =
display: inline !important;">Hi Rob:</span><div class=3D"" =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
18px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none;"><br =
class=3D""></div><div class=3D"" style=3D"caret-color: rgb(0, 0, 0); =
font-family: Helvetica; font-size: 18px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;">My apologies but I have just seen this e-mail. =
We were working on posting last v09 precisely today, assuming this was =
all clarified and the decision was to change the names as Tom =
suggested.</div><div class=3D"" style=3D"caret-color: rgb(0, 0, 0); =
font-family: Helvetica; font-size: 18px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;"><br class=3D""></div><div class=3D"" =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
18px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none;">Regarding your =
comment, having "the notifications in the ikeless module as a feature" =
would not help. Let me explain. The ikeless module needs something =
inherent to operate, which are the notifications. It is not something =
optional for the ikeless module to =
implement.</div></div></blockquote><div class=3D""><br =
class=3D""></div><div class=3D"">That does not seem like enough =
justification for not having the module be usable in such a broader =
fashion. It is obvious to anyone implementing this for your use case =
that the notifications must be implemented. If you feel that it is not =
obvious for some reason a simple sentence can make that clear. Although =
I would think that sentence might start with the word "Obviously, ..." =
:)</div></div></div></blockquote><div><br class=3D""></div><div>As you =
may remember we gave several justifications about why these changes are =
not correct in the context of the I2NSF work. Let me send you the link =
to avoid repeating myself :)&nbsp;</div><div><br class=3D""></div><div><a =
href=3D"https://mailarchive.ietf.org/arch/msg/i2nsf/IZyRrrTZu7tVm5Kpqe2mw5=
-kZ1w/" =
class=3D"">https://mailarchive.ietf.org/arch/msg/i2nsf/IZyRrrTZu7tVm5Kpqe2=
mw5-kZ1w/</a>&nbsp;</div><div><br class=3D""></div><div>Thus, the change =
=E2=80=9Cthe notifications in the ikeless module as a feature=E2=80=9D =
is just the tip of the iceberg of a bigger change discussed in that link =
(moving SAD container to the common module). In other words, just simply =
adding "the notifications in the ikeless module as a feature=E2=80=9D is =
not useful and does not help. In fact, the notifications must be defined =
in the ikeless module, and adding a feature in the ikeless module would =
not make any sense.&nbsp;</div><div><br class=3D""></div><div>As a =
consequence, the resolution was to move forward with a pragmatic =
approach at this point of time, by changing the names of the modules =
(and prefixes) to refer to the I2NSF work.</div><div><br =
class=3D""></div><div>Best Regards.</div><br class=3D""><blockquote =
type=3D"cite" class=3D""><div class=3D""><div style=3D"caret-color: =
rgb(0, 0, 0); font-family: Courier; font-size: 16px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;" class=3D""><div class=3D""><br =
class=3D""></div><div class=3D"">Thanks,</div><div =
class=3D"">Chris.</div><br class=3D""><blockquote type=3D"cite" =
class=3D""><div class=3D""><div class=3D"" style=3D"font-family: =
Helvetica; font-size: 18px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none; caret-color: rgb(0, 0, 0);"><br class=3D""></div><div class=3D"" =
style=3D"font-family: Helvetica; font-size: 18px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none; caret-color: rgb(0, 0, 0);">Hope this =
helps.</div><div class=3D"" style=3D"caret-color: rgb(0, 0, 0); =
font-family: Helvetica; font-size: 18px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;"><br class=3D""></div><div class=3D"" =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
18px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none;">Best Regards.<br =
class=3D""><div class=3D""><br class=3D""><blockquote type=3D"cite" =
class=3D""><div class=3D"">El 12 oct 2020, a las 18:01, Rob Wilton =
(rwilton) &lt;<a href=3D"mailto:rwilton=3D40cisco.com@dmarc.ietf.org" =
class=3D"">rwilton=3D40cisco.com@dmarc.ietf.org</a>&gt; =
escribi=C3=B3:</div><br class=3D"Apple-interchange-newline"><div =
class=3D""><div class=3D"WordSection1" style=3D"page: WordSection1; =
caret-color: rgb(0, 0, 0); font-family: Courier; font-size: 16px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none;"><div class=3D"" =
style=3D"margin: 0cm; font-size: 11pt; font-family: Calibri, =
sans-serif;"><span class=3D"">Hi Rafa, authors,<o:p =
class=3D""></o:p></span></div><div class=3D"" style=3D"margin: 0cm; =
font-size: 11pt; font-family: Calibri, sans-serif;"><span class=3D""><o:p =
class=3D"">&nbsp;</o:p></span></div><div class=3D"" style=3D"margin: =
0cm; font-size: 11pt; font-family: Calibri, sans-serif;"><span =
class=3D"">Just to check.<o:p class=3D""></o:p></span></div><div =
class=3D"" style=3D"margin: 0cm; font-size: 11pt; font-family: Calibri, =
sans-serif;"><span class=3D""><o:p =
class=3D"">&nbsp;</o:p></span></div><div class=3D"" style=3D"margin: =
0cm; font-size: 11pt; font-family: Calibri, sans-serif;"><span =
class=3D"">Has there been any closure on the suggestion from Chris on =
=E2=80=9C</span><span class=3D"">notifications in the ikeless module as =
a feature"?&nbsp; This would seem to be a fairly cheap &amp; easy =
compromise.<o:p class=3D""></o:p></span></div><div class=3D"" =
style=3D"margin: 0cm; font-size: 11pt; font-family: Calibri, =
sans-serif;"><span class=3D""><o:p =
class=3D"">&nbsp;</o:p></span></div><div class=3D"" style=3D"margin: =
0cm; font-size: 11pt; font-family: Calibri, sans-serif;"><span =
class=3D"">Thanks,<br class=3D"">Rob<o:p =
class=3D""></o:p></span></div><div class=3D"" style=3D"margin: 0cm; =
font-size: 11pt; font-family: Calibri, sans-serif;"><span class=3D""><o:p =
class=3D"">&nbsp;</o:p></span></div><div class=3D"" style=3D"margin: =
0cm; font-size: 11pt; font-family: Calibri, sans-serif;"><span =
class=3D""><o:p class=3D"">&nbsp;</o:p></span></div><div class=3D"" =
style=3D"border-style: none none none solid; border-left-width: 1.5pt; =
border-left-color: blue; padding: 0cm 0cm 0cm 4pt;"><div class=3D""><div =
class=3D"" style=3D"border-style: solid none none; border-top-width: =
1pt; border-top-color: rgb(225, 225, 225); padding: 3pt 0cm 0cm;"><div =
class=3D"" style=3D"margin: 0cm; font-size: 11pt; font-family: Calibri, =
sans-serif;"><b class=3D""><span lang=3D"EN-US" =
class=3D"">From:</span></b><span lang=3D"EN-US" class=3D""><span =
class=3D"Apple-converted-space">&nbsp;</span>yang-doctors &lt;<a =
href=3D"mailto:yang-doctors-bounces@ietf.org" =
class=3D"">yang-doctors-bounces@ietf.org</a>&gt;<span =
class=3D"Apple-converted-space">&nbsp;</span><b class=3D"">On Behalf =
Of<span class=3D"Apple-converted-space">&nbsp;</span></b>Lou Berger<br =
class=3D""><b class=3D"">Sent:</b><span =
class=3D"Apple-converted-space">&nbsp;</span>27 September 2020 15:26<br =
class=3D""><b class=3D"">To:</b><span =
class=3D"Apple-converted-space">&nbsp;</span>Christian Hopps &lt;<a =
href=3D"mailto:chopps@chopps.org" class=3D"">chopps@chopps.org</a>&gt;; =
Martin Bj=C3=B6rklund &lt;<a href=3D"mailto:mbj+ietf@4668.se" =
class=3D"">mbj+ietf@4668.se</a>&gt;<br class=3D""><b =
class=3D"">Cc:</b><span =
class=3D"Apple-converted-space">&nbsp;</span>Robert Wilton &lt;<a =
href=3D"mailto:rwilton=3D40cisco.com@dmarc.ietf.org" =
class=3D"">rwilton=3D40cisco.com@dmarc.ietf.org</a>&gt;;<span =
class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"mailto:i2nsf@ietf.org" class=3D"">i2nsf@ietf.org</a>; Gabriel =
Lopez &lt;<a href=3D"mailto:gabilm@um.es" =
class=3D"">gabilm@um.es</a>&gt;;<span =
class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"mailto:draft-ietf-i2nsf-sdn-ipsec-flow-protection.all@ietf.org" =
class=3D"">draft-ietf-i2nsf-sdn-ipsec-flow-protection.all@ietf.org</a>;<sp=
an class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"mailto:ipsec@ietf.org" class=3D"">ipsec@ietf.org</a>;<span =
class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"mailto:last-call@ietf.org" class=3D"">last-call@ietf.org</a>; =
Rafa Marin-Lopez &lt;<a href=3D"mailto:rafa@um.es" =
class=3D"">rafa@um.es</a>&gt;;<span =
class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"mailto:yang-doctors@ietf.org" =
class=3D"">yang-doctors@ietf.org</a><br class=3D""><b =
class=3D"">Subject:</b><span =
class=3D"Apple-converted-space">&nbsp;</span>Re: [yang-doctors] [IPsec] =
[Last-Call] [I2nsf] Yangdoctors last call review of =
draft-ietf-i2nsf-sdn-ipsec-flow-protection-08<o:p =
class=3D""></o:p></span></div></div></div><div class=3D"" style=3D"margin:=
 0cm; font-size: 11pt; font-family: Calibri, sans-serif;"><o:p =
class=3D"">&nbsp;</o:p></div><blockquote class=3D"" style=3D"margin-top: =
5pt; margin-bottom: 5pt;"><div class=3D""><div class=3D"" style=3D"margin:=
 0cm; font-size: 11pt; font-family: Calibri, sans-serif;">This is a =
sub-optimal compromise b/c all IPsec have SA databases even ones running =
IKE -- i.e., SA databases are common whether exposed in YANG or not -- =
but if it can move it forward perhaps good enough.<o:p =
class=3D""></o:p></div></div><div class=3D""><div class=3D"" =
style=3D"margin: 0cm; font-size: 11pt; font-family: Calibri, =
sans-serif;"><br class=3D""><br class=3D""><o:p =
class=3D""></o:p></div></div></blockquote><div class=3D"" style=3D"margin:=
 0cm; font-size: 11pt; font-family: Calibri, sans-serif;">Speaking as an =
interested party, I hope that some compromise / good enough solution is =
followed in the -09 version of&nbsp; this draft.<o:p =
class=3D""></o:p></div><p class=3D"">Lou<o:p class=3D""></o:p></p><div =
class=3D""><div class=3D"" style=3D"margin: 0cm; font-size: 11pt; =
font-family: Calibri, sans-serif;">On 9/23/2020 7:20 AM, Christian Hopps =
wrote:<o:p class=3D""></o:p></div></div><blockquote class=3D"" =
style=3D"margin-top: 5pt; margin-bottom: 5pt;"><div class=3D"" =
style=3D"margin: 0cm; font-size: 11pt; font-family: Calibri, =
sans-serif;"><o:p class=3D"">&nbsp;</o:p></div><div class=3D""><div =
class=3D"" style=3D"margin: 0cm; font-size: 11pt; font-family: Calibri, =
sans-serif;"><br class=3D""><br class=3D""><o:p =
class=3D""></o:p></div><blockquote class=3D"" style=3D"margin-top: 5pt; =
margin-bottom: 5pt;"><div class=3D""><div class=3D"" style=3D"margin: =
0cm; font-size: 11pt; font-family: Calibri, sans-serif;">On Sep 23, =
2020, at 6:58 AM, Martin Bj=C3=B6rklund &lt;<a =
href=3D"mailto:mbj+ietf@4668.se" class=3D"" style=3D"color: blue; =
text-decoration: underline;">mbj+ietf@4668.se</a>&gt; wrote:<o:p =
class=3D""></o:p></div></div><div class=3D"" style=3D"margin: 0cm; =
font-size: 11pt; font-family: Calibri, sans-serif;"><o:p =
class=3D"">&nbsp;</o:p></div><div class=3D""><div class=3D"" =
style=3D"margin: 0cm; font-size: 11pt; font-family: Calibri, =
sans-serif;"><span class=3D"" style=3D"font-size: 10.5pt; font-family: =
Menlo-Regular, serif;">Hi,<br class=3D""><br class=3D"">Christian Hopps =
&lt;</span><a href=3D"mailto:chopps@chopps.org" class=3D"" style=3D"color:=
 blue; text-decoration: underline;"><span class=3D"" style=3D"font-size: =
10.5pt; font-family: Menlo-Regular, =
serif;">chopps@chopps.org</span></a><span class=3D"" style=3D"font-size: =
10.5pt; font-family: Menlo-Regular, serif;">&gt; wrote:<br class=3D"" =
style=3D"caret-color: rgb(0, 0, 0); font-variant-caps: normal; =
text-align: start; -webkit-text-stroke-width: 0px; word-spacing: =
0px;"><br class=3D""></span><o:p class=3D""></o:p></div><blockquote =
class=3D"" style=3D"margin-top: 5pt; margin-bottom: 5pt;"><div class=3D"" =
style=3D"margin: 0cm; font-size: 11pt; font-family: Calibri, =
sans-serif;"><span class=3D"" style=3D"font-size: 10.5pt; font-family: =
Menlo-Regular, serif;"><br class=3D""><br class=3D""><br class=3D""><o:p =
class=3D""></o:p></span></div><blockquote class=3D"" style=3D"margin-top: =
5pt; margin-bottom: 5pt;"><div class=3D"" style=3D"margin: 0cm; =
font-size: 11pt; font-family: Calibri, sans-serif;"><span class=3D"" =
style=3D"font-size: 10.5pt; font-family: Menlo-Regular, serif;">On Sep =
23, 2020, at 5:29 AM, Rafa Marin-Lopez &lt;<a href=3D"mailto:rafa@um.es" =
class=3D"" style=3D"color: blue; text-decoration: =
underline;">rafa@um.es</a>&gt; wrote:<br class=3D""><br class=3D""><br =
class=3D""><o:p class=3D""></o:p></span></div><blockquote class=3D"" =
style=3D"margin-top: 5pt; margin-bottom: 5pt;"><div class=3D"" =
style=3D"margin: 0cm; font-size: 11pt; font-family: Calibri, =
sans-serif;"><span class=3D"" style=3D"font-size: 10.5pt; font-family: =
Menlo-Regular, serif;"><br class=3D""><br class=3D"">But I would like to =
check: My understanding is that the changes that<br class=3D"">Chris is =
proposing are pretty small. &nbsp;I.e. move the SA structure under<br =
class=3D"">ipsec-common, and put it under a YANG feature. &nbsp;Are you =
sure that it<br class=3D"">is impractical to accommodate this change =
which would allow a single<br class=3D"">ipsec module to be shared and =
extended via YANG augmentations?<o:p =
class=3D""></o:p></span></div></blockquote><div class=3D"" =
style=3D"margin: 0cm; font-size: 11pt; font-family: Calibri, =
sans-serif;"><span class=3D"" style=3D"font-size: 10.5pt; font-family: =
Menlo-Regular, serif;"><br class=3D""><br class=3D"">In the context of =
our I-D, if we move SAD structure to ipsec-common,<br class=3D"">what we =
are meaning is that IPsec SA configuration data (setting<br =
class=3D"">values to the SAD structure) are common to the IKE case and =
the<br class=3D"">IKE-less cases, which are not. It is confusing.<o:p =
class=3D""></o:p></span></div></blockquote><div class=3D"" =
style=3D"margin: 0cm; font-size: 11pt; font-family: Calibri, =
sans-serif;"><span class=3D"" style=3D"font-size: 10.5pt; font-family: =
Menlo-Regular, serif;"><br class=3D"">Something defined in a common =
module but marked as a feature does not<br class=3D"">imply that that =
feature has to be implemented by an importing<br class=3D"">module. This =
is not confusing to YANG implementers or users I<br class=3D"">think. If =
we are just talking about document flow here, then a<br =
class=3D"">sentence saying "the SAD feature is not required to implement =
IKE<br class=3D"">functionality" is quite enough to clear that up I =
think.<o:p class=3D""></o:p></span></div></blockquote><div class=3D"" =
style=3D"margin: 0cm; font-size: 11pt; font-family: Calibri, =
sans-serif;"><span class=3D"" style=3D"font-size: 10.5pt; font-family: =
Menlo-Regular, serif;"><br class=3D"">Another alternative could be to =
move these containers to another<br class=3D"">(new) module.</span><o:p =
class=3D""></o:p></div></div></blockquote><div class=3D""><div class=3D"" =
style=3D"margin: 0cm; font-size: 11pt; font-family: Calibri, =
sans-serif;"><o:p class=3D"">&nbsp;</o:p></div></div><div class=3D"" =
style=3D"margin: 0cm; font-size: 11pt; font-family: Calibri, =
sans-serif;"><span class=3D"">It may also be enough to mark the =
notifications in the ikeless module as a feature I suppose. That is the =
actual thing I think non-SDN implementations would want to omit. The =
module name "ikeless" is not great in this case, but perhaps =
workable.</span><o:p class=3D""></o:p></div></div><div class=3D""><div =
class=3D"" style=3D"margin: 0cm; font-size: 11pt; font-family: Calibri, =
sans-serif;"><span class=3D""><br class=3D""><br class=3D""></span><o:p =
class=3D""></o:p></div></div><div class=3D""><div class=3D"" =
style=3D"margin: 0cm; font-size: 11pt; font-family: Calibri, =
sans-serif;"><span class=3D"">This is a sub-optimal compromise b/c all =
IPsec have SA databases even ones running IKE -- i.e., SA databases are =
common whether exposed in YANG or not -- but if it can move it forward =
perhaps good enough.</span><o:p class=3D""></o:p></div></div><div =
class=3D""><div class=3D"" style=3D"margin: 0cm; font-size: 11pt; =
font-family: Calibri, sans-serif;"><span class=3D""><br class=3D""><br =
class=3D""></span><o:p class=3D""></o:p></div></div><div class=3D""><div =
class=3D"" style=3D"margin: 0cm; font-size: 11pt; font-family: Calibri, =
sans-serif;"><span class=3D"">I'm definitely concerned about IETF =
process and real world usability here. These modules are basically =
workable for ipsec I think, they could be used by operators today. If we =
restart the entire process to redo this work for the more generic IPsec =
case it will probably be years before they are finished and in the =
field. This new work can be started, but why not have something usable =
in the meantime?</span><o:p class=3D""></o:p></div></div><div =
class=3D""><div class=3D"" style=3D"margin: 0cm; font-size: 11pt; =
font-family: Calibri, sans-serif;"><o:p =
class=3D"">&nbsp;</o:p></div></div><div class=3D""><div class=3D"" =
style=3D"margin: 0cm; font-size: 11pt; font-family: Calibri, =
sans-serif;">Thanks,<o:p class=3D""></o:p></div></div><div class=3D""><div=
 class=3D"" style=3D"margin: 0cm; font-size: 11pt; font-family: Calibri, =
sans-serif;">Chris.<o:p class=3D""></o:p></div></div><div class=3D""><div =
class=3D"" style=3D"margin: 0cm; font-size: 11pt; font-family: Calibri, =
sans-serif;"><o:p class=3D"">&nbsp;</o:p></div></div><div =
class=3D""><blockquote class=3D"" style=3D"margin-top: 5pt; =
margin-bottom: 5pt;"><div class=3D""><div class=3D"" style=3D"margin: =
0cm; font-size: 11pt; font-family: Calibri, sans-serif;"><span class=3D"" =
style=3D"font-size: 10.5pt; font-family: Menlo-Regular, serif;"><br =
class=3D""><br class=3D"">/martin<br class=3D""><br class=3D""><br =
class=3D""><br class=3D"" style=3D"caret-color: rgb(0, 0, 0); =
font-variant-caps: normal; text-align: start; -webkit-text-stroke-width: =
0px; word-spacing: 0px;"><br class=3D""></span><o:p =
class=3D""></o:p></div><blockquote class=3D"" style=3D"margin-top: 5pt; =
margin-bottom: 5pt;"><div class=3D"" style=3D"margin: 0cm; font-size: =
11pt; font-family: Calibri, sans-serif;"><span class=3D"" =
style=3D"font-size: 10.5pt; font-family: Menlo-Regular, serif;"><br =
class=3D"">Thanks,<br class=3D"">Chris.<br class=3D""><br class=3D""><br =
class=3D""><o:p class=3D""></o:p></span></div><blockquote class=3D"" =
style=3D"margin-top: 5pt; margin-bottom: 5pt;"><p class=3D"MsoNormal" =
style=3D"margin: 0cm 0cm 12pt; font-size: 11pt; font-family: Calibri, =
sans-serif;"><span class=3D"" style=3D"font-size: 10.5pt; font-family: =
Menlo-Regular, serif;">Moreover, the usage of feature means that, after =
all, this =E2=80=9Ccommon=E2=80=9D is<br class=3D"">not =E2=80=9Ccommon=E2=
=80=9D to both cases IKE case and IKE-less. Again, it seems<br =
class=3D"">confusing. In the IKE case, the SDN/I2NSF controller does =
not<br class=3D"">configure the SAD at all but the IKE implementation in =
the NSF. In our<br class=3D"">opinion, in order to properly add this =
IPsec SA operational state to<br class=3D"">the IKE case we should =
include operational data about the IPsec SAs<br class=3D"">(config =
false) to the ietf-ipsec-ike. Alternatively, we have certain<br =
class=3D"">operational data (ro) in the SAD structure in the IKE-less =
case. If<br class=3D"">only those are moved to the common part should be =
ok but we think it<br class=3D"">does not solve the problem.<o:p =
class=3D""></o:p></span></p></blockquote><div class=3D"" style=3D"margin: =
0cm; font-size: 11pt; font-family: Calibri, sans-serif;"><span class=3D"" =
style=3D"font-size: 10.5pt; font-family: Menlo-Regular, serif;"><o:p =
class=3D"">&nbsp;</o:p></span></div></blockquote><div class=3D"" =
style=3D"margin: 0cm; font-size: 11pt; font-family: Calibri, =
sans-serif;"><span class=3D"" style=3D"font-size: 10.5pt; font-family: =
Menlo-Regular, serif;">--<span =
class=3D"apple-converted-space">&nbsp;</span><br class=3D"">last-call =
mailing list<br class=3D""></span><a href=3D"mailto:last-call@ietf.org" =
class=3D"" style=3D"color: blue; text-decoration: underline;"><span =
class=3D"" style=3D"font-size: 10.5pt; font-family: Menlo-Regular, =
serif;">last-call@ietf.org</span></a><span class=3D"" style=3D"font-size: =
10.5pt; font-family: Menlo-Regular, serif;"><br class=3D""></span><a =
href=3D"https://www.ietf.org/mailman/listinfo/last-call" class=3D"" =
style=3D"color: blue; text-decoration: underline;"><span class=3D"" =
style=3D"font-size: 10.5pt; font-family: Menlo-Regular, =
serif;">https://www.ietf.org/mailman/listinfo/last-call</span></a><o:p =
class=3D""></o:p></div></div></blockquote></div><div class=3D"" =
style=3D"margin: 0cm; font-size: 11pt; font-family: Calibri, =
sans-serif;"><br class=3D""><br class=3D""><br class=3D""><o:p =
class=3D""></o:p></div><pre class=3D"" style=3D"margin: 0cm; font-size: =
10pt; font-family: &quot;Courier =
New&quot;;">_______________________________________________<o:p =
class=3D""></o:p></pre><pre class=3D"" style=3D"margin: 0cm; font-size: =
10pt; font-family: &quot;Courier New&quot;;">IPsec mailing list<o:p =
class=3D""></o:p></pre><pre class=3D"" style=3D"margin: 0cm; font-size: =
10pt; font-family: &quot;Courier New&quot;;"><a =
href=3D"mailto:IPsec@ietf.org" class=3D"" style=3D"color: blue; =
text-decoration: underline;">IPsec@ietf.org</a><o:p =
class=3D""></o:p></pre><pre class=3D"" style=3D"margin: 0cm; font-size: =
10pt; font-family: &quot;Courier New&quot;;"><a =
href=3D"https://www.ietf.org/mailman/listinfo/ipsec" class=3D"" =
style=3D"color: blue; text-decoration: =
underline;">https://www.ietf.org/mailman/listinfo/ipsec</a><o:p =
class=3D""></o:p></pre></blockquote></div></div><span class=3D"" =
style=3D"caret-color: rgb(0, 0, 0); font-family: Courier; font-size: =
16px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none; float: none; =
display: inline =
!important;">_______________________________________________</span><br =
class=3D"" style=3D"caret-color: rgb(0, 0, 0); font-family: Courier; =
font-size: 16px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none;"><span class=3D"" style=3D"caret-color: rgb(0, 0, 0); font-family: =
Courier; font-size: 16px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none; float: none; display: inline !important;">I2nsf mailing =
list</span><br class=3D"" style=3D"caret-color: rgb(0, 0, 0); =
font-family: Courier; font-size: 16px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;"><span class=3D"" style=3D"caret-color: rgb(0, 0, =
0); font-family: Courier; font-size: 16px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none; float: none; display: inline !important;"><a =
href=3D"mailto:I2nsf@ietf.org" class=3D"">I2nsf@ietf.org</a></span><br =
class=3D"" style=3D"caret-color: rgb(0, 0, 0); font-family: Courier; =
font-size: 16px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none;"><span class=3D"" style=3D"caret-color: rgb(0, 0, 0); font-family: =
Courier; font-size: 16px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none; float: none; display: inline !important;"><a =
href=3D"https://www.ietf.org/mailman/listinfo/i2nsf" =
class=3D"">https://www.ietf.org/mailman/listinfo/i2nsf</a></span></div></b=
lockquote></div><br class=3D""><div class=3D""><div class=3D"" =
style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; line-break: =
after-white-space;"><div class=3D"" style=3D"font-family: Courier; =
font-size: 16px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: =
0px;">-------------------------------------------------------<br =
class=3D"">Rafa Marin-Lopez, PhD<br class=3D"">Dept. Information =
and&nbsp;Communications&nbsp;Engineering (DIIC)<br class=3D"">Faculty of =
Computer&nbsp;Science-University of&nbsp;Murcia<br class=3D"">30100 =
Murcia - Spain<br class=3D"">Telf: +34868888501 =
Fax:&nbsp;+34868884151<span =
class=3D"Apple-converted-space">&nbsp;</span><a href=3D"mailto:rafa@um.es"=
 class=3D"">e-mail:&nbsp;rafa@um.es</a><br =
class=3D"">-------------------------------------------------------</div><d=
iv class=3D"" style=3D"font-family: Courier; font-size: 16px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px;"><br class=3D""></div><br =
class=3D"Apple-interchange-newline"></div><br =
class=3D"Apple-interchange-newline"></div><br class=3D""></div><span =
class=3D"" style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; =
font-size: 18px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none; float: none; display: inline =
!important;">_______________________________________________</span><br =
class=3D"" style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; =
font-size: 18px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none;"><span class=3D"" style=3D"caret-color: rgb(0, 0, 0); font-family: =
Helvetica; font-size: 18px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none; float: none; display: inline !important;">IPsec mailing =
list</span><br class=3D"" style=3D"caret-color: rgb(0, 0, 0); =
font-family: Helvetica; font-size: 18px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;"><a href=3D"mailto:IPsec@ietf.org" class=3D"" =
style=3D"font-family: Helvetica; font-size: 18px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: =
0px;">IPsec@ietf.org</a><br class=3D"" style=3D"caret-color: rgb(0, 0, =
0); font-family: Helvetica; font-size: 18px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;"><a =
href=3D"https://www.ietf.org/mailman/listinfo/ipsec" class=3D"" =
style=3D"font-family: Helvetica; font-size: 18px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: =
0px;">https://www.ietf.org/mailman/listinfo/ipsec</a></div></blockquote></=
div><br class=3D"" style=3D"caret-color: rgb(0, 0, 0); font-family: =
Courier; font-size: 16px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none;"><span style=3D"caret-color: rgb(0, 0, 0); font-family: Courier; =
font-size: 16px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none; float: none; display: inline !important;" =
class=3D"">_______________________________________________</span><br =
style=3D"caret-color: rgb(0, 0, 0); font-family: Courier; font-size: =
16px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none;" class=3D""><span =
style=3D"caret-color: rgb(0, 0, 0); font-family: Courier; font-size: =
16px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none; float: none; =
display: inline !important;" class=3D"">I2nsf mailing list</span><br =
style=3D"caret-color: rgb(0, 0, 0); font-family: Courier; font-size: =
16px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none;" class=3D""><a =
href=3D"mailto:I2nsf@ietf.org" style=3D"font-family: Courier; font-size: =
16px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; orphans: auto; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; widows: =
auto; word-spacing: 0px; -webkit-text-size-adjust: auto; =
-webkit-text-stroke-width: 0px;" class=3D"">I2nsf@ietf.org</a><br =
style=3D"caret-color: rgb(0, 0, 0); font-family: Courier; font-size: =
16px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none;" class=3D""><a =
href=3D"https://www.ietf.org/mailman/listinfo/i2nsf" style=3D"font-family:=
 Courier; font-size: 16px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; orphans: auto; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; =
-webkit-text-stroke-width: 0px;" =
class=3D"">https://www.ietf.org/mailman/listinfo/i2nsf</a></div></blockquo=
te></div><br class=3D""><div class=3D"">
<div style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space;" class=3D""><div style=3D"color: =
rgb(0, 0, 0); font-family: Courier; font-size: 16px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
orphans: auto; text-align: start; text-indent: 0px; text-transform: =
none; white-space: normal; widows: auto; word-spacing: 0px; =
-webkit-text-stroke-width: =
0px;">-------------------------------------------------------<br =
class=3D"">Rafa Marin-Lopez, PhD<br class=3D"">Dept. Information =
and&nbsp;Communications&nbsp;Engineering (DIIC)<br class=3D"">Faculty of =
Computer&nbsp;Science-University of&nbsp;Murcia<br class=3D"">30100 =
Murcia - Spain<br class=3D"">Telf: +34868888501 Fax:&nbsp;+34868884151 =
<a href=3D"mailto:rafa@um.es" class=3D"">e-mail:&nbsp;rafa@um.es</a><br =
class=3D"">-------------------------------------------------------</div><d=
iv style=3D"color: rgb(0, 0, 0); font-family: Courier; font-size: 16px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; orphans: auto; text-align: start; text-indent: =
0px; text-transform: none; white-space: normal; widows: auto; =
word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=3D""><br =
class=3D""></div><br class=3D"Apple-interchange-newline"></div><br =
class=3D"Apple-interchange-newline">
</div>
<br class=3D""></div></body></html>=

--Apple-Mail=_86C75A4C-578C-4DFD-A1B4-2555C14193A2--



From nobody Tue Oct 13 01:38:39 2020
Return-Path: <chopps@chopps.org>
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 6E3A43A097C; Tue, 13 Oct 2020 01:38:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level: 
X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 FJa5COP79H4f; Tue, 13 Oct 2020 01:38:34 -0700 (PDT)
Received: from smtp.chopps.org (smtp.chopps.org [54.88.81.56]) by ietfa.amsl.com (Postfix) with ESMTP id 469E23A0992; Tue, 13 Oct 2020 01:38:34 -0700 (PDT)
Received: from stubbs.int.chopps.org (047-050-069-038.biz.spectrum.com [47.50.69.38]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by smtp.chopps.org (Postfix) with ESMTPSA id 0E10761679; Tue, 13 Oct 2020 08:38:32 +0000 (UTC)
From: Christian Hopps <chopps@chopps.org>
Message-Id: <7C422A91-5543-41A0-B907-6AAD9F83E6DA@chopps.org>
Content-Type: multipart/signed; boundary="Apple-Mail=_011F4A32-7E56-4EF1-8008-905FB0467BFB"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\))
Date: Tue, 13 Oct 2020 04:38:31 -0400
In-Reply-To: <B3282660-5C6A-4B69-8CFC-57AFBCE2B544@um.es>
Cc: Christian Hopps <chopps@chopps.org>, "Rob Wilton (rwilton)" <rwilton@cisco.com>, =?utf-8?Q?Martin_Bj=C3=B6rklund?= <mbj+ietf@4668.se>, "i2nsf@ietf.org" <i2nsf@ietf.org>, Gabriel Lopez <gabilm@um.es>, "draft-ietf-i2nsf-sdn-ipsec-flow-protection.all@ietf.org" <draft-ietf-i2nsf-sdn-ipsec-flow-protection.all@ietf.org>,  "ipsec@ietf.org" <ipsec@ietf.org>, "last-call@ietf.org" <last-call@ietf.org>, "yang-doctors@ietf.org" <yang-doctors@ietf.org>, Lou Berger <lberger@labn.net>
To: Rafa Marin-Lopez <rafa@um.es>
References: <MN2PR11MB4366E30B3C372D13B391AE07B53B0@MN2PR11MB4366.namprd11.prod.outlook.com> <2B88888E-A264-4D81-A8DA-9C6225E83E0E@um.es> <70A0A406-0742-4F28-A5A4-8D539B160E24@chopps.org> <20200923.125826.1562347052257995146.id@4668.se> <CBC552B2-6039-48E8-988D-4F2BA3FD6B2E@chopps.org> <023fc27b-f86e-ed71-0c8f-d270c338f08c@labn.net> <MN2PR11MB43662E1711367EDE9A066452B5070@MN2PR11MB4366.namprd11.prod.outlook.com> <E827743C-74A1-42CE-9765-7ECD062D8E41@um.es> <10116C35-8FBF-4914-9846-883D2C7F7A11@chopps.org> <B3282660-5C6A-4B69-8CFC-57AFBCE2B544@um.es>
X-Mailer: Apple Mail (2.3608.120.23.2.4)
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2nsf/HWegIVwHgu9f-EJg0WeJIvaztso>
Subject: Re: [I2nsf] [IPsec] [yang-doctors] [Last-Call] Yangdoctors last call review of draft-ietf-i2nsf-sdn-ipsec-flow-protection-08
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: Tue, 13 Oct 2020 08:38:38 -0000

--Apple-Mail=_011F4A32-7E56-4EF1-8008-905FB0467BFB
Content-Type: multipart/alternative;
	boundary="Apple-Mail=_445EA150-8B61-486D-8188-16D7FF811B67"


--Apple-Mail=_445EA150-8B61-486D-8188-16D7FF811B67
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8



> On Oct 13, 2020, at 12:15 AM, Rafa Marin-Lopez <rafa@um.es> wrote:
>=20
> Hi Christian (, Rob):
>=20
> Thanks for your comments. We really appreciate them. Please see some =
comments inline.
>=20
>> El 12 oct 2020, a las 22:21, Christian Hopps <chopps@chopps.org =
<mailto:chopps@chopps.org>> escribi=C3=B3:
>>=20
>>=20
>>=20
>>> On Oct 12, 2020, at 3:07 PM, Rafa Marin-Lopez <rafa@um.es =
<mailto:rafa@um.es>> wrote:
>>>=20
>>> Hi Rob:
>>>=20
>>> My apologies but I have just seen this e-mail. We were working on =
posting last v09 precisely today, assuming this was all clarified and =
the decision was to change the names as Tom suggested.
>>>=20
>>> Regarding your comment, having "the notifications in the ikeless =
module as a feature" would not help. Let me explain. The ikeless module =
needs something inherent to operate, which are the notifications. It is =
not something optional for the ikeless module to implement.
>>=20
>> That does not seem like enough justification for not having the =
module be usable in such a broader fashion. It is obvious to anyone =
implementing this for your use case that the notifications must be =
implemented. If you feel that it is not obvious for some reason a simple =
sentence can make that clear. Although I would think that sentence might =
start with the word "Obviously, ..." :)
>=20
> As you may remember we gave several justifications about why these =
changes are not correct in the context of the I2NSF work. Let me send =
you the link to avoid repeating myself :)
>=20
> =
https://mailarchive.ietf.org/arch/msg/i2nsf/IZyRrrTZu7tVm5Kpqe2mw5-kZ1w/ =
<https://mailarchive.ietf.org/arch/msg/i2nsf/IZyRrrTZu7tVm5Kpqe2mw5-kZ1w/>=

>=20
> Thus, the change =E2=80=9Cthe notifications in the ikeless module as a =
feature=E2=80=9D is just the tip of the iceberg of a bigger change =
discussed in that link (moving SAD container to the common module). In =
other words, just simply adding "the notifications in the ikeless module =
as a feature=E2=80=9D is not useful and does not help. In fact, the =
notifications must be defined in the ikeless module, and adding a =
feature in the ikeless module would not make any sense.
>=20
> As a consequence, the resolution was to move forward with a pragmatic =
approach at this point of time, by changing the names of the modules =
(and prefixes) to refer to the I2NSF work.

These are 2 different things. The original discussion was about moving =
the SAD and SPD from ikeless module to the common one which then would =
have brought them into the IKE module, and required people just =
implementing IKE to also implement the SAD and SPD parts.

In comparison this new compromise request is a tiny change, and allows a =
much larger audience to reap the benefit of your work. The change is the =
addition of "feature ikeless-notification" and then putting the "if =
ikeless-notification" under the notifications.

This doesn't change the semantics of your module it just allows people =
to re-use the ikeless module for supporting SAD and SPD w/o implementing =
the notifications.

If you feel more clarity is needed for the SDN use-case then adding the =
text, "To allow for greater re-use of this module, the notifications are =
marked as a feature. For the SDN use case clients will expect this =
feature to be implemented."

Features are reported just as modules are in the capabilities. An SDN =
client would look for both capabilities rather than just the one (along =
with all the other capabilities they will be looking for to actually be =
a functional YANG client).

Thanks,
Chris.

>=20
> Best Regards.
>=20
>>=20
>> Thanks,
>> Chris.
>>=20
>>>=20
>>> Hope this helps.
>>>=20
>>> Best Regards.
>>>=20
>>>> El 12 oct 2020, a las 18:01, Rob Wilton (rwilton) =
<rwilton=3D40cisco.com@dmarc.ietf.org =
<mailto:rwilton=3D40cisco.com@dmarc.ietf.org>> escribi=C3=B3:
>>>>=20
>>>> Hi Rafa, authors,
>>>>=20
>>>> Just to check.
>>>>=20
>>>> Has there been any closure on the suggestion from Chris on =
=E2=80=9Cnotifications in the ikeless module as a feature"?  This would =
seem to be a fairly cheap & easy compromise.
>>>>=20
>>>> Thanks,
>>>> Rob
>>>>=20
>>>>=20
>>>> From: yang-doctors <yang-doctors-bounces@ietf.org =
<mailto:yang-doctors-bounces@ietf.org>> On Behalf Of Lou Berger
>>>> Sent: 27 September 2020 15:26
>>>> To: Christian Hopps <chopps@chopps.org <mailto:chopps@chopps.org>>; =
Martin Bj=C3=B6rklund <mbj+ietf@4668.se <mailto:mbj+ietf@4668.se>>
>>>> Cc: Robert Wilton <rwilton=3D40cisco.com@dmarc.ietf.org =
<mailto:rwilton=3D40cisco.com@dmarc.ietf.org>>; i2nsf@ietf.org =
<mailto:i2nsf@ietf.org>; Gabriel Lopez <gabilm@um.es =
<mailto:gabilm@um.es>>; =
draft-ietf-i2nsf-sdn-ipsec-flow-protection.all@ietf.org =
<mailto:draft-ietf-i2nsf-sdn-ipsec-flow-protection.all@ietf.org>; =
ipsec@ietf.org <mailto:ipsec@ietf.org>; last-call@ietf.org =
<mailto:last-call@ietf.org>; Rafa Marin-Lopez <rafa@um.es =
<mailto:rafa@um.es>>; yang-doctors@ietf.org =
<mailto:yang-doctors@ietf.org>
>>>> Subject: Re: [yang-doctors] [IPsec] [Last-Call] [I2nsf] Yangdoctors =
last call review of draft-ietf-i2nsf-sdn-ipsec-flow-protection-08
>>>>=20
>>>> This is a sub-optimal compromise b/c all IPsec have SA databases =
even ones running IKE -- i.e., SA databases are common whether exposed =
in YANG or not -- but if it can move it forward perhaps good enough.
>>>>=20
>>>>=20
>>>> Speaking as an interested party, I hope that some compromise / good =
enough solution is followed in the -09 version of  this draft.
>>>> Lou
>>>>=20
>>>> On 9/23/2020 7:20 AM, Christian Hopps wrote:
>>>>=20
>>>>=20
>>>>=20
>>>> On Sep 23, 2020, at 6:58 AM, Martin Bj=C3=B6rklund =
<mbj+ietf@4668.se <mailto:mbj+ietf@4668.se>> wrote:
>>>>=20
>>>> Hi,
>>>>=20
>>>> Christian Hopps <chopps@chopps.org <mailto:chopps@chopps.org>> =
wrote:
>>>>=20
>>>>=20
>>>>=20
>>>>=20
>>>> On Sep 23, 2020, at 5:29 AM, Rafa Marin-Lopez <rafa@um.es =
<mailto:rafa@um.es>> wrote:
>>>>=20
>>>>=20
>>>>=20
>>>>=20
>>>> But I would like to check: My understanding is that the changes =
that
>>>> Chris is proposing are pretty small.  I.e. move the SA structure =
under
>>>> ipsec-common, and put it under a YANG feature.  Are you sure that =
it
>>>> is impractical to accommodate this change which would allow a =
single
>>>> ipsec module to be shared and extended via YANG augmentations?
>>>>=20
>>>>=20
>>>> In the context of our I-D, if we move SAD structure to =
ipsec-common,
>>>> what we are meaning is that IPsec SA configuration data (setting
>>>> values to the SAD structure) are common to the IKE case and the
>>>> IKE-less cases, which are not. It is confusing.
>>>>=20
>>>> Something defined in a common module but marked as a feature does =
not
>>>> imply that that feature has to be implemented by an importing
>>>> module. This is not confusing to YANG implementers or users I
>>>> think. If we are just talking about document flow here, then a
>>>> sentence saying "the SAD feature is not required to implement IKE
>>>> functionality" is quite enough to clear that up I think.
>>>>=20
>>>> Another alternative could be to move these containers to another
>>>> (new) module.
>>>>=20
>>>> It may also be enough to mark the notifications in the ikeless =
module as a feature I suppose. That is the actual thing I think non-SDN =
implementations would want to omit. The module name "ikeless" is not =
great in this case, but perhaps workable.
>>>>=20
>>>>=20
>>>> This is a sub-optimal compromise b/c all IPsec have SA databases =
even ones running IKE -- i.e., SA databases are common whether exposed =
in YANG or not -- but if it can move it forward perhaps good enough.
>>>>=20
>>>>=20
>>>> I'm definitely concerned about IETF process and real world =
usability here. These modules are basically workable for ipsec I think, =
they could be used by operators today. If we restart the entire process =
to redo this work for the more generic IPsec case it will probably be =
years before they are finished and in the field. This new work can be =
started, but why not have something usable in the meantime?
>>>>=20
>>>> Thanks,
>>>> Chris.
>>>>=20
>>>>=20
>>>>=20
>>>> /martin
>>>>=20
>>>>=20
>>>>=20
>>>>=20
>>>>=20
>>>> Thanks,
>>>> Chris.
>>>>=20
>>>>=20
>>>> Moreover, the usage of feature means that, after all, this =
=E2=80=9Ccommon=E2=80=9D is
>>>> not =E2=80=9Ccommon=E2=80=9D to both cases IKE case and IKE-less. =
Again, it seems
>>>> confusing. In the IKE case, the SDN/I2NSF controller does not
>>>> configure the SAD at all but the IKE implementation in the NSF. In =
our
>>>> opinion, in order to properly add this IPsec SA operational state =
to
>>>> the IKE case we should include operational data about the IPsec SAs
>>>> (config false) to the ietf-ipsec-ike. Alternatively, we have =
certain
>>>> operational data (ro) in the SAD structure in the IKE-less case. If
>>>> only those are moved to the common part should be ok but we think =
it
>>>> does not solve the problem.
>>>>=20
>>>>=20
>>>> --
>>>> last-call mailing list
>>>> last-call@ietf.org <mailto:last-call@ietf.org>
>>>> https://www.ietf.org/mailman/listinfo/last-call =
<https://www.ietf.org/mailman/listinfo/last-call>
>>>>=20
>>>>=20
>>>>=20
>>>> _______________________________________________
>>>> IPsec mailing list
>>>> IPsec@ietf.org <mailto:IPsec@ietf.org>
>>>> https://www.ietf.org/mailman/listinfo/ipsec =
<https://www.ietf.org/mailman/listinfo/ipsec>_____________________________=
__________________
>>>> 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:=C2=A0rafa@um.es =
<mailto:rafa@um.es>
>>> -------------------------------------------------------
>>>=20
>>>=20
>>>=20
>>>=20
>>> _______________________________________________
>>> IPsec mailing list
>>> IPsec@ietf.org <mailto:IPsec@ietf.org>
>>> https://www.ietf.org/mailman/listinfo/ipsec =
<https://www.ietf.org/mailman/listinfo/ipsec>
>> _______________________________________________
>> 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:=C2=A0rafa@um.es =
<mailto:rafa@um.es>
> -------------------------------------------------------
>=20
>=20
>=20
>=20
> _______________________________________________
> IPsec mailing list
> IPsec@ietf.org <mailto:IPsec@ietf.org>
> https://www.ietf.org/mailman/listinfo/ipsec =
<https://www.ietf.org/mailman/listinfo/ipsec>

--Apple-Mail=_445EA150-8B61-486D-8188-16D7FF811B67
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: after-white-space;" class=3D""><br =
class=3D""><div><br class=3D""><blockquote type=3D"cite" class=3D""><div =
class=3D"">On Oct 13, 2020, at 12:15 AM, Rafa Marin-Lopez &lt;<a =
href=3D"mailto:rafa@um.es" class=3D"">rafa@um.es</a>&gt; wrote:</div><br =
class=3D"Apple-interchange-newline"><div class=3D""><span =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
18px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none; float: none; =
display: inline !important;" class=3D"">Hi Christian (, Rob):</span><div =
class=3D"" style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; =
font-size: 18px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none;"><br class=3D""></div><div class=3D"" style=3D"caret-color: rgb(0, =
0, 0); font-family: Helvetica; font-size: 18px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;">Thanks for your comments. We really appreciate =
them. Please see some comments inline.<br class=3D""><div class=3D""><br =
class=3D""><blockquote type=3D"cite" class=3D""><div class=3D"">El 12 =
oct 2020, a las 22:21, Christian Hopps &lt;<a =
href=3D"mailto:chopps@chopps.org" class=3D"">chopps@chopps.org</a>&gt; =
escribi=C3=B3:</div><br class=3D"Apple-interchange-newline"><div =
class=3D""><div class=3D"" style=3D"caret-color: rgb(0, 0, 0); =
font-family: Courier; font-size: 16px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;"><br class=3D"Apple-interchange-newline"><br =
class=3D""><blockquote type=3D"cite" class=3D""><div class=3D"">On Oct =
12, 2020, at 3:07 PM, Rafa Marin-Lopez &lt;<a href=3D"mailto:rafa@um.es" =
class=3D"">rafa@um.es</a>&gt; wrote:</div><br =
class=3D"Apple-interchange-newline"><div class=3D""><span class=3D"" =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
18px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none; float: none; =
display: inline !important;">Hi Rob:</span><div class=3D"" =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
18px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none;"><br =
class=3D""></div><div class=3D"" style=3D"caret-color: rgb(0, 0, 0); =
font-family: Helvetica; font-size: 18px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;">My apologies but I have just seen this e-mail. =
We were working on posting last v09 precisely today, assuming this was =
all clarified and the decision was to change the names as Tom =
suggested.</div><div class=3D"" style=3D"caret-color: rgb(0, 0, 0); =
font-family: Helvetica; font-size: 18px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;"><br class=3D""></div><div class=3D"" =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
18px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none;">Regarding your =
comment, having "the notifications in the ikeless module as a feature" =
would not help. Let me explain. The ikeless module needs something =
inherent to operate, which are the notifications. It is not something =
optional for the ikeless module to =
implement.</div></div></blockquote><div class=3D""><br =
class=3D""></div><div class=3D"">That does not seem like enough =
justification for not having the module be usable in such a broader =
fashion. It is obvious to anyone implementing this for your use case =
that the notifications must be implemented. If you feel that it is not =
obvious for some reason a simple sentence can make that clear. Although =
I would think that sentence might start with the word "Obviously, ..." =
:)</div></div></div></blockquote><div class=3D""><br class=3D""></div><div=
 class=3D"">As you may remember we gave several justifications about why =
these changes are not correct in the context of the I2NSF work. Let me =
send you the link to avoid repeating myself :)&nbsp;</div><div =
class=3D""><br class=3D""></div><div class=3D""><a =
href=3D"https://mailarchive.ietf.org/arch/msg/i2nsf/IZyRrrTZu7tVm5Kpqe2mw5=
-kZ1w/" =
class=3D"">https://mailarchive.ietf.org/arch/msg/i2nsf/IZyRrrTZu7tVm5Kpqe2=
mw5-kZ1w/</a>&nbsp;</div><div class=3D""><br class=3D""></div><div =
class=3D"">Thus, the change =E2=80=9Cthe notifications in the ikeless =
module as a feature=E2=80=9D is just the tip of the iceberg of a bigger =
change discussed in that link (moving SAD container to the common =
module). In other words, just simply adding "the notifications in the =
ikeless module as a feature=E2=80=9D is not useful and does not help. In =
fact, the notifications must be defined in the ikeless module, and =
adding a feature in the ikeless module would not make any =
sense.&nbsp;</div><div class=3D""><br class=3D""></div><div class=3D"">As =
a consequence, the resolution was to move forward with a pragmatic =
approach at this point of time, by changing the names of the modules =
(and prefixes) to refer to the I2NSF =
work.</div></div></div></div></blockquote><div><br =
class=3D""></div><div>These are 2 different things. The original =
discussion was about moving the SAD and SPD from ikeless module to the =
common one which then would have brought them into the IKE module, and =
required people just implementing IKE to also implement the SAD and SPD =
parts.</div><div><br class=3D""></div><div>In comparison this new =
compromise request is a tiny change, and allows a much larger audience =
to reap the benefit of your work. The change is the addition of "feature =
ikeless-notification" and then putting the "if ikeless-notification" =
under the notifications.</div><div><br class=3D""></div><div>This =
doesn't change the semantics of your module it just allows people to =
re-use the ikeless module for supporting SAD and SPD w/o implementing =
the notifications.</div><div><br class=3D""></div><div>If you feel more =
clarity is needed for the SDN use-case then adding the text, "To allow =
for greater re-use of this module, the notifications are marked as a =
feature. For the SDN use case clients will expect this feature to be =
implemented."</div></div><div><br class=3D""></div><div>Features are =
reported just as modules are in the capabilities. An SDN client would =
look for both capabilities rather than just the one (along with all the =
other capabilities they will be looking for to actually be a functional =
YANG client).</div><div><br =
class=3D""></div><div>Thanks,</div><div>Chris.</div><div><br =
class=3D""><blockquote type=3D"cite" class=3D""><div class=3D""><div =
class=3D"" style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; =
font-size: 18px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none;"><div class=3D""><div class=3D""><br class=3D""></div><div =
class=3D"">Best Regards.</div><br class=3D""><blockquote type=3D"cite" =
class=3D""><div class=3D""><div class=3D"" style=3D"caret-color: rgb(0, =
0, 0); font-family: Courier; font-size: 16px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;"><div class=3D""><br class=3D""></div><div =
class=3D"">Thanks,</div><div class=3D"">Chris.</div><br =
class=3D""><blockquote type=3D"cite" class=3D""><div class=3D""><div =
class=3D"" style=3D"font-family: Helvetica; font-size: 18px; font-style: =
normal; font-variant-caps: normal; font-weight: normal; letter-spacing: =
normal; text-align: start; text-indent: 0px; text-transform: none; =
white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none; caret-color: rgb(0, 0, 0);"><br =
class=3D""></div><div class=3D"" style=3D"font-family: Helvetica; =
font-size: 18px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none; caret-color: rgb(0, 0, 0);">Hope this helps.</div><div class=3D"" =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
18px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none;"><br =
class=3D""></div><div class=3D"" style=3D"caret-color: rgb(0, 0, 0); =
font-family: Helvetica; font-size: 18px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;">Best Regards.<br class=3D""><div class=3D""><br =
class=3D""><blockquote type=3D"cite" class=3D""><div class=3D"">El 12 =
oct 2020, a las 18:01, Rob Wilton (rwilton) &lt;<a =
href=3D"mailto:rwilton=3D40cisco.com@dmarc.ietf.org" =
class=3D"">rwilton=3D40cisco.com@dmarc.ietf.org</a>&gt; =
escribi=C3=B3:</div><br class=3D"Apple-interchange-newline"><div =
class=3D""><div class=3D"WordSection1" style=3D"page: WordSection1; =
caret-color: rgb(0, 0, 0); font-family: Courier; font-size: 16px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none;"><div class=3D"" =
style=3D"margin: 0cm; font-size: 11pt; font-family: Calibri, =
sans-serif;"><span class=3D"">Hi Rafa, authors,<o:p =
class=3D""></o:p></span></div><div class=3D"" style=3D"margin: 0cm; =
font-size: 11pt; font-family: Calibri, sans-serif;"><span class=3D""><o:p =
class=3D"">&nbsp;</o:p></span></div><div class=3D"" style=3D"margin: =
0cm; font-size: 11pt; font-family: Calibri, sans-serif;"><span =
class=3D"">Just to check.<o:p class=3D""></o:p></span></div><div =
class=3D"" style=3D"margin: 0cm; font-size: 11pt; font-family: Calibri, =
sans-serif;"><span class=3D""><o:p =
class=3D"">&nbsp;</o:p></span></div><div class=3D"" style=3D"margin: =
0cm; font-size: 11pt; font-family: Calibri, sans-serif;"><span =
class=3D"">Has there been any closure on the suggestion from Chris on =
=E2=80=9C</span><span class=3D"">notifications in the ikeless module as =
a feature"?&nbsp; This would seem to be a fairly cheap &amp; easy =
compromise.<o:p class=3D""></o:p></span></div><div class=3D"" =
style=3D"margin: 0cm; font-size: 11pt; font-family: Calibri, =
sans-serif;"><span class=3D""><o:p =
class=3D"">&nbsp;</o:p></span></div><div class=3D"" style=3D"margin: =
0cm; font-size: 11pt; font-family: Calibri, sans-serif;"><span =
class=3D"">Thanks,<br class=3D"">Rob<o:p =
class=3D""></o:p></span></div><div class=3D"" style=3D"margin: 0cm; =
font-size: 11pt; font-family: Calibri, sans-serif;"><span class=3D""><o:p =
class=3D"">&nbsp;</o:p></span></div><div class=3D"" style=3D"margin: =
0cm; font-size: 11pt; font-family: Calibri, sans-serif;"><span =
class=3D""><o:p class=3D"">&nbsp;</o:p></span></div><div class=3D"" =
style=3D"border-style: none none none solid; border-left-width: 1.5pt; =
border-left-color: blue; padding: 0cm 0cm 0cm 4pt;"><div class=3D""><div =
class=3D"" style=3D"border-style: solid none none; border-top-width: =
1pt; border-top-color: rgb(225, 225, 225); padding: 3pt 0cm 0cm;"><div =
class=3D"" style=3D"margin: 0cm; font-size: 11pt; font-family: Calibri, =
sans-serif;"><b class=3D""><span lang=3D"EN-US" =
class=3D"">From:</span></b><span lang=3D"EN-US" class=3D""><span =
class=3D"Apple-converted-space">&nbsp;</span>yang-doctors &lt;<a =
href=3D"mailto:yang-doctors-bounces@ietf.org" =
class=3D"">yang-doctors-bounces@ietf.org</a>&gt;<span =
class=3D"Apple-converted-space">&nbsp;</span><b class=3D"">On Behalf =
Of<span class=3D"Apple-converted-space">&nbsp;</span></b>Lou Berger<br =
class=3D""><b class=3D"">Sent:</b><span =
class=3D"Apple-converted-space">&nbsp;</span>27 September 2020 15:26<br =
class=3D""><b class=3D"">To:</b><span =
class=3D"Apple-converted-space">&nbsp;</span>Christian Hopps &lt;<a =
href=3D"mailto:chopps@chopps.org" class=3D"">chopps@chopps.org</a>&gt;; =
Martin Bj=C3=B6rklund &lt;<a href=3D"mailto:mbj+ietf@4668.se" =
class=3D"">mbj+ietf@4668.se</a>&gt;<br class=3D""><b =
class=3D"">Cc:</b><span =
class=3D"Apple-converted-space">&nbsp;</span>Robert Wilton &lt;<a =
href=3D"mailto:rwilton=3D40cisco.com@dmarc.ietf.org" =
class=3D"">rwilton=3D40cisco.com@dmarc.ietf.org</a>&gt;;<span =
class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"mailto:i2nsf@ietf.org" class=3D"">i2nsf@ietf.org</a>; Gabriel =
Lopez &lt;<a href=3D"mailto:gabilm@um.es" =
class=3D"">gabilm@um.es</a>&gt;;<span =
class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"mailto:draft-ietf-i2nsf-sdn-ipsec-flow-protection.all@ietf.org" =
class=3D"">draft-ietf-i2nsf-sdn-ipsec-flow-protection.all@ietf.org</a>;<sp=
an class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"mailto:ipsec@ietf.org" class=3D"">ipsec@ietf.org</a>;<span =
class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"mailto:last-call@ietf.org" class=3D"">last-call@ietf.org</a>; =
Rafa Marin-Lopez &lt;<a href=3D"mailto:rafa@um.es" =
class=3D"">rafa@um.es</a>&gt;;<span =
class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"mailto:yang-doctors@ietf.org" =
class=3D"">yang-doctors@ietf.org</a><br class=3D""><b =
class=3D"">Subject:</b><span =
class=3D"Apple-converted-space">&nbsp;</span>Re: [yang-doctors] [IPsec] =
[Last-Call] [I2nsf] Yangdoctors last call review of =
draft-ietf-i2nsf-sdn-ipsec-flow-protection-08<o:p =
class=3D""></o:p></span></div></div></div><div class=3D"" style=3D"margin:=
 0cm; font-size: 11pt; font-family: Calibri, sans-serif;"><o:p =
class=3D"">&nbsp;</o:p></div><blockquote class=3D"" style=3D"margin-top: =
5pt; margin-bottom: 5pt;"><div class=3D""><div class=3D"" style=3D"margin:=
 0cm; font-size: 11pt; font-family: Calibri, sans-serif;">This is a =
sub-optimal compromise b/c all IPsec have SA databases even ones running =
IKE -- i.e., SA databases are common whether exposed in YANG or not -- =
but if it can move it forward perhaps good enough.<o:p =
class=3D""></o:p></div></div><div class=3D""><div class=3D"" =
style=3D"margin: 0cm; font-size: 11pt; font-family: Calibri, =
sans-serif;"><br class=3D""><br class=3D""><o:p =
class=3D""></o:p></div></div></blockquote><div class=3D"" style=3D"margin:=
 0cm; font-size: 11pt; font-family: Calibri, sans-serif;">Speaking as an =
interested party, I hope that some compromise / good enough solution is =
followed in the -09 version of&nbsp; this draft.<o:p =
class=3D""></o:p></div><p class=3D"">Lou<o:p class=3D""></o:p></p><div =
class=3D""><div class=3D"" style=3D"margin: 0cm; font-size: 11pt; =
font-family: Calibri, sans-serif;">On 9/23/2020 7:20 AM, Christian Hopps =
wrote:<o:p class=3D""></o:p></div></div><blockquote class=3D"" =
style=3D"margin-top: 5pt; margin-bottom: 5pt;"><div class=3D"" =
style=3D"margin: 0cm; font-size: 11pt; font-family: Calibri, =
sans-serif;"><o:p class=3D"">&nbsp;</o:p></div><div class=3D""><div =
class=3D"" style=3D"margin: 0cm; font-size: 11pt; font-family: Calibri, =
sans-serif;"><br class=3D""><br class=3D""><o:p =
class=3D""></o:p></div><blockquote class=3D"" style=3D"margin-top: 5pt; =
margin-bottom: 5pt;"><div class=3D""><div class=3D"" style=3D"margin: =
0cm; font-size: 11pt; font-family: Calibri, sans-serif;">On Sep 23, =
2020, at 6:58 AM, Martin Bj=C3=B6rklund &lt;<a =
href=3D"mailto:mbj+ietf@4668.se" class=3D"" style=3D"color: blue; =
text-decoration: underline;">mbj+ietf@4668.se</a>&gt; wrote:<o:p =
class=3D""></o:p></div></div><div class=3D"" style=3D"margin: 0cm; =
font-size: 11pt; font-family: Calibri, sans-serif;"><o:p =
class=3D"">&nbsp;</o:p></div><div class=3D""><div class=3D"" =
style=3D"margin: 0cm; font-size: 11pt; font-family: Calibri, =
sans-serif;"><span class=3D"" style=3D"font-size: 10.5pt; font-family: =
Menlo-Regular, serif;">Hi,<br class=3D""><br class=3D"">Christian Hopps =
&lt;</span><a href=3D"mailto:chopps@chopps.org" class=3D"" style=3D"color:=
 blue; text-decoration: underline;"><span class=3D"" style=3D"font-size: =
10.5pt; font-family: Menlo-Regular, =
serif;">chopps@chopps.org</span></a><span class=3D"" style=3D"font-size: =
10.5pt; font-family: Menlo-Regular, serif;">&gt; wrote:<br class=3D"" =
style=3D"caret-color: rgb(0, 0, 0); font-variant-caps: normal; =
text-align: start; -webkit-text-stroke-width: 0px; word-spacing: =
0px;"><br class=3D""></span><o:p class=3D""></o:p></div><blockquote =
class=3D"" style=3D"margin-top: 5pt; margin-bottom: 5pt;"><div class=3D"" =
style=3D"margin: 0cm; font-size: 11pt; font-family: Calibri, =
sans-serif;"><span class=3D"" style=3D"font-size: 10.5pt; font-family: =
Menlo-Regular, serif;"><br class=3D""><br class=3D""><br class=3D""><o:p =
class=3D""></o:p></span></div><blockquote class=3D"" style=3D"margin-top: =
5pt; margin-bottom: 5pt;"><div class=3D"" style=3D"margin: 0cm; =
font-size: 11pt; font-family: Calibri, sans-serif;"><span class=3D"" =
style=3D"font-size: 10.5pt; font-family: Menlo-Regular, serif;">On Sep =
23, 2020, at 5:29 AM, Rafa Marin-Lopez &lt;<a href=3D"mailto:rafa@um.es" =
class=3D"" style=3D"color: blue; text-decoration: =
underline;">rafa@um.es</a>&gt; wrote:<br class=3D""><br class=3D""><br =
class=3D""><o:p class=3D""></o:p></span></div><blockquote class=3D"" =
style=3D"margin-top: 5pt; margin-bottom: 5pt;"><div class=3D"" =
style=3D"margin: 0cm; font-size: 11pt; font-family: Calibri, =
sans-serif;"><span class=3D"" style=3D"font-size: 10.5pt; font-family: =
Menlo-Regular, serif;"><br class=3D""><br class=3D"">But I would like to =
check: My understanding is that the changes that<br class=3D"">Chris is =
proposing are pretty small. &nbsp;I.e. move the SA structure under<br =
class=3D"">ipsec-common, and put it under a YANG feature. &nbsp;Are you =
sure that it<br class=3D"">is impractical to accommodate this change =
which would allow a single<br class=3D"">ipsec module to be shared and =
extended via YANG augmentations?<o:p =
class=3D""></o:p></span></div></blockquote><div class=3D"" =
style=3D"margin: 0cm; font-size: 11pt; font-family: Calibri, =
sans-serif;"><span class=3D"" style=3D"font-size: 10.5pt; font-family: =
Menlo-Regular, serif;"><br class=3D""><br class=3D"">In the context of =
our I-D, if we move SAD structure to ipsec-common,<br class=3D"">what we =
are meaning is that IPsec SA configuration data (setting<br =
class=3D"">values to the SAD structure) are common to the IKE case and =
the<br class=3D"">IKE-less cases, which are not. It is confusing.<o:p =
class=3D""></o:p></span></div></blockquote><div class=3D"" =
style=3D"margin: 0cm; font-size: 11pt; font-family: Calibri, =
sans-serif;"><span class=3D"" style=3D"font-size: 10.5pt; font-family: =
Menlo-Regular, serif;"><br class=3D"">Something defined in a common =
module but marked as a feature does not<br class=3D"">imply that that =
feature has to be implemented by an importing<br class=3D"">module. This =
is not confusing to YANG implementers or users I<br class=3D"">think. If =
we are just talking about document flow here, then a<br =
class=3D"">sentence saying "the SAD feature is not required to implement =
IKE<br class=3D"">functionality" is quite enough to clear that up I =
think.<o:p class=3D""></o:p></span></div></blockquote><div class=3D"" =
style=3D"margin: 0cm; font-size: 11pt; font-family: Calibri, =
sans-serif;"><span class=3D"" style=3D"font-size: 10.5pt; font-family: =
Menlo-Regular, serif;"><br class=3D"">Another alternative could be to =
move these containers to another<br class=3D"">(new) module.</span><o:p =
class=3D""></o:p></div></div></blockquote><div class=3D""><div class=3D"" =
style=3D"margin: 0cm; font-size: 11pt; font-family: Calibri, =
sans-serif;"><o:p class=3D"">&nbsp;</o:p></div></div><div class=3D"" =
style=3D"margin: 0cm; font-size: 11pt; font-family: Calibri, =
sans-serif;"><span class=3D"">It may also be enough to mark the =
notifications in the ikeless module as a feature I suppose. That is the =
actual thing I think non-SDN implementations would want to omit. The =
module name "ikeless" is not great in this case, but perhaps =
workable.</span><o:p class=3D""></o:p></div></div><div class=3D""><div =
class=3D"" style=3D"margin: 0cm; font-size: 11pt; font-family: Calibri, =
sans-serif;"><span class=3D""><br class=3D""><br class=3D""></span><o:p =
class=3D""></o:p></div></div><div class=3D""><div class=3D"" =
style=3D"margin: 0cm; font-size: 11pt; font-family: Calibri, =
sans-serif;"><span class=3D"">This is a sub-optimal compromise b/c all =
IPsec have SA databases even ones running IKE -- i.e., SA databases are =
common whether exposed in YANG or not -- but if it can move it forward =
perhaps good enough.</span><o:p class=3D""></o:p></div></div><div =
class=3D""><div class=3D"" style=3D"margin: 0cm; font-size: 11pt; =
font-family: Calibri, sans-serif;"><span class=3D""><br class=3D""><br =
class=3D""></span><o:p class=3D""></o:p></div></div><div class=3D""><div =
class=3D"" style=3D"margin: 0cm; font-size: 11pt; font-family: Calibri, =
sans-serif;"><span class=3D"">I'm definitely concerned about IETF =
process and real world usability here. These modules are basically =
workable for ipsec I think, they could be used by operators today. If we =
restart the entire process to redo this work for the more generic IPsec =
case it will probably be years before they are finished and in the =
field. This new work can be started, but why not have something usable =
in the meantime?</span><o:p class=3D""></o:p></div></div><div =
class=3D""><div class=3D"" style=3D"margin: 0cm; font-size: 11pt; =
font-family: Calibri, sans-serif;"><o:p =
class=3D"">&nbsp;</o:p></div></div><div class=3D""><div class=3D"" =
style=3D"margin: 0cm; font-size: 11pt; font-family: Calibri, =
sans-serif;">Thanks,<o:p class=3D""></o:p></div></div><div class=3D""><div=
 class=3D"" style=3D"margin: 0cm; font-size: 11pt; font-family: Calibri, =
sans-serif;">Chris.<o:p class=3D""></o:p></div></div><div class=3D""><div =
class=3D"" style=3D"margin: 0cm; font-size: 11pt; font-family: Calibri, =
sans-serif;"><o:p class=3D"">&nbsp;</o:p></div></div><div =
class=3D""><blockquote class=3D"" style=3D"margin-top: 5pt; =
margin-bottom: 5pt;"><div class=3D""><div class=3D"" style=3D"margin: =
0cm; font-size: 11pt; font-family: Calibri, sans-serif;"><span class=3D"" =
style=3D"font-size: 10.5pt; font-family: Menlo-Regular, serif;"><br =
class=3D""><br class=3D"">/martin<br class=3D""><br class=3D""><br =
class=3D""><br class=3D"" style=3D"caret-color: rgb(0, 0, 0); =
font-variant-caps: normal; text-align: start; -webkit-text-stroke-width: =
0px; word-spacing: 0px;"><br class=3D""></span><o:p =
class=3D""></o:p></div><blockquote class=3D"" style=3D"margin-top: 5pt; =
margin-bottom: 5pt;"><div class=3D"" style=3D"margin: 0cm; font-size: =
11pt; font-family: Calibri, sans-serif;"><span class=3D"" =
style=3D"font-size: 10.5pt; font-family: Menlo-Regular, serif;"><br =
class=3D"">Thanks,<br class=3D"">Chris.<br class=3D""><br class=3D""><br =
class=3D""><o:p class=3D""></o:p></span></div><blockquote class=3D"" =
style=3D"margin-top: 5pt; margin-bottom: 5pt;"><p class=3D"MsoNormal" =
style=3D"margin: 0cm 0cm 12pt; font-size: 11pt; font-family: Calibri, =
sans-serif;"><span class=3D"" style=3D"font-size: 10.5pt; font-family: =
Menlo-Regular, serif;">Moreover, the usage of feature means that, after =
all, this =E2=80=9Ccommon=E2=80=9D is<br class=3D"">not =E2=80=9Ccommon=E2=
=80=9D to both cases IKE case and IKE-less. Again, it seems<br =
class=3D"">confusing. In the IKE case, the SDN/I2NSF controller does =
not<br class=3D"">configure the SAD at all but the IKE implementation in =
the NSF. In our<br class=3D"">opinion, in order to properly add this =
IPsec SA operational state to<br class=3D"">the IKE case we should =
include operational data about the IPsec SAs<br class=3D"">(config =
false) to the ietf-ipsec-ike. Alternatively, we have certain<br =
class=3D"">operational data (ro) in the SAD structure in the IKE-less =
case. If<br class=3D"">only those are moved to the common part should be =
ok but we think it<br class=3D"">does not solve the problem.<o:p =
class=3D""></o:p></span></p></blockquote><div class=3D"" style=3D"margin: =
0cm; font-size: 11pt; font-family: Calibri, sans-serif;"><span class=3D"" =
style=3D"font-size: 10.5pt; font-family: Menlo-Regular, serif;"><o:p =
class=3D"">&nbsp;</o:p></span></div></blockquote><div class=3D"" =
style=3D"margin: 0cm; font-size: 11pt; font-family: Calibri, =
sans-serif;"><span class=3D"" style=3D"font-size: 10.5pt; font-family: =
Menlo-Regular, serif;">--<span =
class=3D"apple-converted-space">&nbsp;</span><br class=3D"">last-call =
mailing list<br class=3D""></span><a href=3D"mailto:last-call@ietf.org" =
class=3D"" style=3D"color: blue; text-decoration: underline;"><span =
class=3D"" style=3D"font-size: 10.5pt; font-family: Menlo-Regular, =
serif;">last-call@ietf.org</span></a><span class=3D"" style=3D"font-size: =
10.5pt; font-family: Menlo-Regular, serif;"><br class=3D""></span><a =
href=3D"https://www.ietf.org/mailman/listinfo/last-call" class=3D"" =
style=3D"color: blue; text-decoration: underline;"><span class=3D"" =
style=3D"font-size: 10.5pt; font-family: Menlo-Regular, =
serif;">https://www.ietf.org/mailman/listinfo/last-call</span></a><o:p =
class=3D""></o:p></div></div></blockquote></div><div class=3D"" =
style=3D"margin: 0cm; font-size: 11pt; font-family: Calibri, =
sans-serif;"><br class=3D""><br class=3D""><br class=3D""><o:p =
class=3D""></o:p></div><pre class=3D"" style=3D"margin: 0cm; font-size: =
10pt; font-family: &quot;Courier =
New&quot;;">_______________________________________________<o:p =
class=3D""></o:p></pre><pre class=3D"" style=3D"margin: 0cm; font-size: =
10pt; font-family: &quot;Courier New&quot;;">IPsec mailing list<o:p =
class=3D""></o:p></pre><pre class=3D"" style=3D"margin: 0cm; font-size: =
10pt; font-family: &quot;Courier New&quot;;"><a =
href=3D"mailto:IPsec@ietf.org" class=3D"" style=3D"color: blue; =
text-decoration: underline;">IPsec@ietf.org</a><o:p =
class=3D""></o:p></pre><pre class=3D"" style=3D"margin: 0cm; font-size: =
10pt; font-family: &quot;Courier New&quot;;"><a =
href=3D"https://www.ietf.org/mailman/listinfo/ipsec" class=3D"" =
style=3D"color: blue; text-decoration: =
underline;">https://www.ietf.org/mailman/listinfo/ipsec</a><o:p =
class=3D""></o:p></pre></blockquote></div></div><span class=3D"" =
style=3D"caret-color: rgb(0, 0, 0); font-family: Courier; font-size: =
16px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none; float: none; =
display: inline =
!important;">_______________________________________________</span><br =
class=3D"" style=3D"caret-color: rgb(0, 0, 0); font-family: Courier; =
font-size: 16px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none;"><span class=3D"" style=3D"caret-color: rgb(0, 0, 0); font-family: =
Courier; font-size: 16px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none; float: none; display: inline !important;">I2nsf mailing =
list</span><br class=3D"" style=3D"caret-color: rgb(0, 0, 0); =
font-family: Courier; font-size: 16px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;"><span class=3D"" style=3D"caret-color: rgb(0, 0, =
0); font-family: Courier; font-size: 16px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none; float: none; display: inline !important;"><a =
href=3D"mailto:I2nsf@ietf.org" class=3D"">I2nsf@ietf.org</a></span><br =
class=3D"" style=3D"caret-color: rgb(0, 0, 0); font-family: Courier; =
font-size: 16px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none;"><span class=3D"" style=3D"caret-color: rgb(0, 0, 0); font-family: =
Courier; font-size: 16px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none; float: none; display: inline !important;"><a =
href=3D"https://www.ietf.org/mailman/listinfo/i2nsf" =
class=3D"">https://www.ietf.org/mailman/listinfo/i2nsf</a></span></div></b=
lockquote></div><br class=3D""><div class=3D""><div class=3D"" =
style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; line-break: =
after-white-space;"><div class=3D"" style=3D"font-family: Courier; =
font-size: 16px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: =
0px;">-------------------------------------------------------<br =
class=3D"">Rafa Marin-Lopez, PhD<br class=3D"">Dept. Information =
and&nbsp;Communications&nbsp;Engineering (DIIC)<br class=3D"">Faculty of =
Computer&nbsp;Science-University of&nbsp;Murcia<br class=3D"">30100 =
Murcia - Spain<br class=3D"">Telf: +34868888501 =
Fax:&nbsp;+34868884151<span =
class=3D"Apple-converted-space">&nbsp;</span><a href=3D"mailto:rafa@um.es"=
 class=3D"">e-mail:&nbsp;rafa@um.es</a><br =
class=3D"">-------------------------------------------------------</div><d=
iv class=3D"" style=3D"font-family: Courier; font-size: 16px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px;"><br class=3D""></div><br =
class=3D"Apple-interchange-newline"></div><br =
class=3D"Apple-interchange-newline"></div><br class=3D""></div><span =
class=3D"" style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; =
font-size: 18px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none; float: none; display: inline =
!important;">_______________________________________________</span><br =
class=3D"" style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; =
font-size: 18px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none;"><span class=3D"" style=3D"caret-color: rgb(0, 0, 0); font-family: =
Helvetica; font-size: 18px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none; float: none; display: inline !important;">IPsec mailing =
list</span><br class=3D"" style=3D"caret-color: rgb(0, 0, 0); =
font-family: Helvetica; font-size: 18px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;"><a href=3D"mailto:IPsec@ietf.org" class=3D"" =
style=3D"font-family: Helvetica; font-size: 18px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: =
0px;">IPsec@ietf.org</a><br class=3D"" style=3D"caret-color: rgb(0, 0, =
0); font-family: Helvetica; font-size: 18px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;"><a =
href=3D"https://www.ietf.org/mailman/listinfo/ipsec" class=3D"" =
style=3D"font-family: Helvetica; font-size: 18px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: =
0px;">https://www.ietf.org/mailman/listinfo/ipsec</a></div></blockquote></=
div><br class=3D"" style=3D"caret-color: rgb(0, 0, 0); font-family: =
Courier; font-size: 16px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none;"><span class=3D"" style=3D"caret-color: rgb(0, 0, 0); font-family: =
Courier; font-size: 16px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none; float: none; display: inline =
!important;">_______________________________________________</span><br =
class=3D"" style=3D"caret-color: rgb(0, 0, 0); font-family: Courier; =
font-size: 16px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none;"><span class=3D"" style=3D"caret-color: rgb(0, 0, 0); font-family: =
Courier; font-size: 16px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none; float: none; display: inline !important;">I2nsf mailing =
list</span><br class=3D"" style=3D"caret-color: rgb(0, 0, 0); =
font-family: Courier; font-size: 16px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;"><a href=3D"mailto:I2nsf@ietf.org" class=3D"" =
style=3D"font-family: Courier; font-size: 16px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: =
0px;">I2nsf@ietf.org</a><br class=3D"" style=3D"caret-color: rgb(0, 0, =
0); font-family: Courier; font-size: 16px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;"><a =
href=3D"https://www.ietf.org/mailman/listinfo/i2nsf" class=3D"" =
style=3D"font-family: Courier; font-size: 16px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: =
0px;">https://www.ietf.org/mailman/listinfo/i2nsf</a></div></blockquote></=
div><br class=3D""><div class=3D""><div class=3D"" style=3D"word-wrap: =
break-word; -webkit-nbsp-mode: space; line-break: =
after-white-space;"><div style=3D"font-family: Courier; font-size: 16px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px;" =
class=3D"">-------------------------------------------------------<br =
class=3D"">Rafa Marin-Lopez, PhD<br class=3D"">Dept. Information =
and&nbsp;Communications&nbsp;Engineering (DIIC)<br class=3D"">Faculty of =
Computer&nbsp;Science-University of&nbsp;Murcia<br class=3D"">30100 =
Murcia - Spain<br class=3D"">Telf: +34868888501 =
Fax:&nbsp;+34868884151<span =
class=3D"Apple-converted-space">&nbsp;</span><a href=3D"mailto:rafa@um.es"=
 class=3D"">e-mail:&nbsp;rafa@um.es</a><br =
class=3D"">-------------------------------------------------------</div><d=
iv class=3D"" style=3D"font-family: Courier; font-size: 16px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px;"><br class=3D""></div><br =
class=3D"Apple-interchange-newline"></div><br =
class=3D"Apple-interchange-newline"></div><br class=3D""></div><span =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
18px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none; float: none; =
display: inline !important;" =
class=3D"">_______________________________________________</span><br =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
18px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none;" class=3D""><span =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
18px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none; float: none; =
display: inline !important;" class=3D"">IPsec mailing list</span><br =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
18px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none;" class=3D""><a =
href=3D"mailto:IPsec@ietf.org" style=3D"font-family: Helvetica; =
font-size: 18px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; orphans: auto; text-align: =
start; text-indent: 0px; text-transform: none; white-space: normal; =
widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; =
-webkit-text-stroke-width: 0px;" class=3D"">IPsec@ietf.org</a><br =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
18px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none;" class=3D""><a =
href=3D"https://www.ietf.org/mailman/listinfo/ipsec" style=3D"font-family:=
 Helvetica; font-size: 18px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; orphans: auto; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; =
-webkit-text-stroke-width: 0px;" =
class=3D"">https://www.ietf.org/mailman/listinfo/ipsec</a></div></blockquo=
te></div><br class=3D""></body></html>=

--Apple-Mail=_445EA150-8B61-486D-8188-16D7FF811B67--

--Apple-Mail=_011F4A32-7E56-4EF1-8008-905FB0467BFB
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEm56yH/NF+m1FHa6lLh2DDte4MCUFAl+FZ4cACgkQLh2DDte4
MCUoBw/7BeAw9RxI9QYZGzbk4TVu/9SsW9PX6ouvomOxAS+Rf7HUPRxS6ppGnEdf
todua/iN+eY8V7Y7/8LKNIXaRZF5gFuBgEYL8v0INl464CdV5Dsu3UeIM63xwDgg
oq4PzEcqpqzcnyL2uUjfw7IiqdGsU1uldqzT0BUe0Qd6xnsReruWXKjJuklzpnKr
eXw1wp6sAAnGy5tvLpjbLnQvr6qOe8YFkbYdW7YCMPmuTBfZtcfnSshxHoNORkHT
p7eLUcvHNNh/8aCgZa+yElXxdX7SYpzqzGOnJwGjkBbafO8sZOlWOULFB7DLuBqX
sAc6LZmx+xvM3XzPIl8lggv2vjvNWKosgRl/XorhKKYOfPgrXQXSNVLXMalCBT46
sR8z05V7D9XYCaCgRLpHCG8lvH8D3uQaBDl6/jyl+7SOVKOYmrWaYbRcaMgMV4a7
LK3zGubQDHtNHgdLxDPFTxb8WybMlD/zw14gG2+9d4rww5EW+KYrlKc4euhw8Hc5
JPkbCY1hZq7WoblgL865hMtxNvVBRx+Ck2q6Xtc8Jg3KlWUM33vgWXs1r8LIGz/x
BYyX+Vev7/jRN7ndafZ2FGe2EZ57o8b7RgoXJmMc8a8Kg1e3dfH5zXHLCFZCaCqQ
wNPSJ3OwqUwpuZ3SseERh0EKT6i7S2doVzgrI3a2r/dmC8FSUmk=
=oFq7
-----END PGP SIGNATURE-----

--Apple-Mail=_011F4A32-7E56-4EF1-8008-905FB0467BFB--


From nobody Thu Oct 15 00:12:58 2020
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 F11473A1323; Thu, 15 Oct 2020 00:12:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.096
X-Spam-Level: 
X-Spam-Status: No, score=-2.096 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, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, 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=um.es
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 KEa1359Mkzgi; Thu, 15 Oct 2020 00:12:54 -0700 (PDT)
Received: from mx02.puc.rediris.es (outbound4sev.lav.puc.rediris.es [130.206.19.178]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B517F3A131A; Thu, 15 Oct 2020 00:12:53 -0700 (PDT)
Received: from xenon44.um.es (xenon44.um.es [155.54.212.171]) by mx02.puc.rediris.es  with ESMTP id 09F7Cd7H003315-09F7Cd7I003315; Thu, 15 Oct 2020 09:12:39 +0200
Received: from localhost (localhost [127.0.0.1]) by xenon44.um.es (Postfix) with ESMTP id AF008202AF; Thu, 15 Oct 2020 09:12:39 +0200 (CEST)
X-Virus-Scanned: by antispam in UMU at xenon44.um.es
Received: from xenon44.um.es ([127.0.0.1]) by localhost (xenon44.um.es [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 8_NZFiH63X1F; Thu, 15 Oct 2020 09:12:39 +0200 (CEST)
Received: from [192.168.1.33] (135.red-79-150-250.dynamicip.rima-tde.net [79.150.250.135]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: rafa@um.es) by xenon44.um.es (Postfix) with ESMTPSA id DF937201D7; Thu, 15 Oct 2020 09:12:33 +0200 (CEST)
From: Rafa Marin-Lopez <rafa@um.es>
Message-Id: <1142B610-2D58-4DE5-96F7-773D02C1B42A@um.es>
Content-Type: multipart/alternative; boundary="Apple-Mail=_372870A4-A581-4A53-8C03-2CCC4A3A7F5C"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.14\))
Date: Thu, 15 Oct 2020 09:12:32 +0200
In-Reply-To: <7C422A91-5543-41A0-B907-6AAD9F83E6DA@chopps.org>
Cc: Rafa Marin-Lopez <rafa@um.es>, "last-call@ietf.org" <last-call@ietf.org>,  Gabriel Lopez <gabilm@um.es>, "draft-ietf-i2nsf-sdn-ipsec-flow-protection.all@ietf.org" <draft-ietf-i2nsf-sdn-ipsec-flow-protection.all@ietf.org>,  "ipsec@ietf.org" <ipsec@ietf.org>, "i2nsf@ietf.org" <i2nsf@ietf.org>, =?utf-8?Q?Martin_Bj=C3=B6rklund?= <mbj+ietf@4668.se>, "yang-doctors@ietf.org" <yang-doctors@ietf.org>, Lou Berger <lberger@labn.net>, Fernando Pereniguez-Garcia <fernando.pereniguez@cud.upct.es>
To: Christian Hopps <chopps@chopps.org>, "Rob Wilton (rwilton)" <rwilton@cisco.com>
References: <MN2PR11MB4366E30B3C372D13B391AE07B53B0@MN2PR11MB4366.namprd11.prod.outlook.com> <2B88888E-A264-4D81-A8DA-9C6225E83E0E@um.es> <70A0A406-0742-4F28-A5A4-8D539B160E24@chopps.org> <20200923.125826.1562347052257995146.id@4668.se> <CBC552B2-6039-48E8-988D-4F2BA3FD6B2E@chopps.org> <023fc27b-f86e-ed71-0c8f-d270c338f08c@labn.net> <MN2PR11MB43662E1711367EDE9A066452B5070@MN2PR11MB4366.namprd11.prod.outlook.com> <E827743C-74A1-42CE-9765-7ECD062D8E41@um.es> <10116C35-8FBF-4914-9846-883D2C7F7A11@chopps.org> <B3282660-5C6A-4B69-8CFC-57AFBCE2B544@um.es> <7C422A91-5543-41A0-B907-6AAD9F83E6DA@chopps.org>
X-Mailer: Apple Mail (2.3445.104.14)
X-FEAS-SPF: spf-result=pass, ip=155.54.212.171, helo=xenon44.um.es, mailFrom=rafa@um.es
Authentication-Results: mx02.puc.rediris.es; spf=pass (rediris.es: domain of rafa@um.es designates 155.54.212.171 as permitted sender) smtp.mailfrom=rafa@um.es
X-FE-Policy-ID: 2:15:0:SYSTEM, 2:15:1:upct.es
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=c0sJhzBv7Ffkj7pK4oNyxSyXmgL89HH3UIdpJBJmHRE=; b=WgC4VAxmJ4208E9ukUk1v5CnfyiSuIWOXR64wSfuD9QhmQ8ep7DuwcbxEup0m5lpRoRuSFEjd4FM CpCN1az83i/ffpGflnqQ0CIOoE2vUPSck3DRO+YhLeYTmrWXO+T7YpWaglVgvBAC36iJCW//MdNV QIFQMKzaXMcKzfNtu3b552J9DfgRNRe7QB+S3Ok5UBviKtfQalfvrOQcqj/3+34c0SnAVLB/xfz8 3NHYT4PREbM6feY6ckmWMvDC2CV8vF3CB3bYQK8D694iuqC+wOsUsfTAfvTnMSbUb8wNLznx0TT4 wz0lcB5Lr+ez+V0MA7Y3+NgaUlA5x2x7m/fgpw==
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2nsf/Y7V-MueK3BLsAsNZwYlcxA1PsQY>
Subject: Re: [I2nsf] [IPsec] [yang-doctors] [Last-Call] Yangdoctors last call review of draft-ietf-i2nsf-sdn-ipsec-flow-protection-08
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: Thu, 15 Oct 2020 07:12:57 -0000

--Apple-Mail=_372870A4-A581-4A53-8C03-2CCC4A3A7F5C
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Hi Christian (,Rob):

Thanks again for this conversation. Please see our comments inline.

>>=20
>> As a consequence, the resolution was to move forward with a pragmatic =
approach at this point of time, by changing the names of the modules =
(and prefixes) to refer to the I2NSF work.
>=20
> These are 2 different things. The original discussion was about moving =
the SAD and SPD from ikeless module to the common one which then would =
have brought them into the IKE module, and required people just =
implementing IKE to also implement the SAD and SPD parts.
>=20
> In comparison this new compromise request is a tiny change, and allows =
a much larger audience to reap the benefit of your work. The change is =
the addition of "feature ikeless-notification" and then putting the "if =
ikeless-notification" under the notifications.
>=20
> This doesn't change the semantics of your module it just allows people =
to re-use the ikeless module for supporting SAD and SPD w/o implementing =
the notifications.
>=20
> If you feel more clarity is needed for the SDN use-case then adding =
the text, "To allow for greater re-use of this module, the notifications =
are marked as a feature. For the SDN use case clients will expect this =
feature to be implemented.=E2=80=9D

We agree that this is a small change (if no other change is required). =
In fact, we have tested it and we have not observed any technical =
problem. The main concern is the one I mentioned to Rob: having a =
feature to =E2=80=9Cactivate=E2=80=9D notifications (or not) in the =
ikeless module does not fit in the context of this I-D, unless we find =
out a valid use case where this feature makes sense.=20

In other words, it would be really nice if the inclusion of the text you =
proposed (=E2=80=9CTo allow for greater=E2=80=A6=E2=80=9D ) had a main =
text to support how this is useful in the context of this I-D. =
Personally, this would make me feel more confortable.=20

Having said all this, let us inform about v09 changes to I2NSF wg and =
ask about this new change in order to see if there is any objection. =
Then, if there is no objection we can prepare v10 very quickly with this =
additional modification.

We hope this is reasonable.

Best Regards.
>=20
> Features are reported just as modules are in the capabilities. An SDN =
client would look for both capabilities rather than just the one (along =
with all the other capabilities they will be looking for to actually be =
a functional YANG client).
>=20
> Thanks,
> Chris.
>=20
>>=20
>> Best Regards.
>>=20
>>>=20
>>> Thanks,
>>> Chris.
>>>=20
>>>>=20
>>>> Hope this helps.
>>>>=20
>>>> Best Regards.
>>>>=20
>>>>> El 12 oct 2020, a las 18:01, Rob Wilton (rwilton) =
<rwilton=3D40cisco.com@dmarc.ietf.org =
<mailto:rwilton=3D40cisco.com@dmarc.ietf.org>> escribi=C3=B3:
>>>>>=20
>>>>> Hi Rafa, authors,
>>>>> =20
>>>>> Just to check.
>>>>> =20
>>>>> Has there been any closure on the suggestion from Chris on =
=E2=80=9Cnotifications in the ikeless module as a feature"?  This would =
seem to be a fairly cheap & easy compromise.
>>>>> =20
>>>>> Thanks,
>>>>> Rob
>>>>> =20
>>>>> =20
>>>>> From: yang-doctors <yang-doctors-bounces@ietf.org =
<mailto:yang-doctors-bounces@ietf.org>> On Behalf Of Lou Berger
>>>>> Sent: 27 September 2020 15:26
>>>>> To: Christian Hopps <chopps@chopps.org =
<mailto:chopps@chopps.org>>; Martin Bj=C3=B6rklund <mbj+ietf@4668.se =
<mailto:mbj+ietf@4668.se>>
>>>>> Cc: Robert Wilton <rwilton=3D40cisco.com@dmarc.ietf.org =
<mailto:rwilton=3D40cisco.com@dmarc.ietf.org>>; i2nsf@ietf.org =
<mailto:i2nsf@ietf.org>; Gabriel Lopez <gabilm@um.es =
<mailto:gabilm@um.es>>; =
draft-ietf-i2nsf-sdn-ipsec-flow-protection.all@ietf.org =
<mailto:draft-ietf-i2nsf-sdn-ipsec-flow-protection.all@ietf.org>; =
ipsec@ietf.org <mailto:ipsec@ietf.org>; last-call@ietf.org =
<mailto:last-call@ietf.org>; Rafa Marin-Lopez <rafa@um.es =
<mailto:rafa@um.es>>; yang-doctors@ietf.org =
<mailto:yang-doctors@ietf.org>
>>>>> Subject: Re: [yang-doctors] [IPsec] [Last-Call] [I2nsf] =
Yangdoctors last call review of =
draft-ietf-i2nsf-sdn-ipsec-flow-protection-08
>>>>> =20
>>>>> This is a sub-optimal compromise b/c all IPsec have SA databases =
even ones running IKE -- i.e., SA databases are common whether exposed =
in YANG or not -- but if it can move it forward perhaps good enough.
>>>>>=20
>>>>>=20
>>>>> Speaking as an interested party, I hope that some compromise / =
good enough solution is followed in the -09 version of  this draft.
>>>>> Lou
>>>>>=20
>>>>> On 9/23/2020 7:20 AM, Christian Hopps wrote:
>>>>> =20
>>>>>=20
>>>>>=20
>>>>> On Sep 23, 2020, at 6:58 AM, Martin Bj=C3=B6rklund =
<mbj+ietf@4668.se <mailto:mbj+ietf@4668.se>> wrote:
>>>>> =20
>>>>> Hi,
>>>>>=20
>>>>> Christian Hopps <chopps@chopps.org <mailto:chopps@chopps.org>> =
wrote:
>>>>>=20
>>>>>=20
>>>>>=20
>>>>>=20
>>>>> On Sep 23, 2020, at 5:29 AM, Rafa Marin-Lopez <rafa@um.es =
<mailto:rafa@um.es>> wrote:
>>>>>=20
>>>>>=20
>>>>>=20
>>>>>=20
>>>>> But I would like to check: My understanding is that the changes =
that
>>>>> Chris is proposing are pretty small.  I.e. move the SA structure =
under
>>>>> ipsec-common, and put it under a YANG feature.  Are you sure that =
it
>>>>> is impractical to accommodate this change which would allow a =
single
>>>>> ipsec module to be shared and extended via YANG augmentations?
>>>>>=20
>>>>>=20
>>>>> In the context of our I-D, if we move SAD structure to =
ipsec-common,
>>>>> what we are meaning is that IPsec SA configuration data (setting
>>>>> values to the SAD structure) are common to the IKE case and the
>>>>> IKE-less cases, which are not. It is confusing.
>>>>>=20
>>>>> Something defined in a common module but marked as a feature does =
not
>>>>> imply that that feature has to be implemented by an importing
>>>>> module. This is not confusing to YANG implementers or users I
>>>>> think. If we are just talking about document flow here, then a
>>>>> sentence saying "the SAD feature is not required to implement IKE
>>>>> functionality" is quite enough to clear that up I think.
>>>>>=20
>>>>> Another alternative could be to move these containers to another
>>>>> (new) module.
>>>>> =20
>>>>> It may also be enough to mark the notifications in the ikeless =
module as a feature I suppose. That is the actual thing I think non-SDN =
implementations would want to omit. The module name "ikeless" is not =
great in this case, but perhaps workable.
>>>>>=20
>>>>>=20
>>>>> This is a sub-optimal compromise b/c all IPsec have SA databases =
even ones running IKE -- i.e., SA databases are common whether exposed =
in YANG or not -- but if it can move it forward perhaps good enough.
>>>>>=20
>>>>>=20
>>>>> I'm definitely concerned about IETF process and real world =
usability here. These modules are basically workable for ipsec I think, =
they could be used by operators today. If we restart the entire process =
to redo this work for the more generic IPsec case it will probably be =
years before they are finished and in the field. This new work can be =
started, but why not have something usable in the meantime?
>>>>> =20
>>>>> Thanks,
>>>>> Chris.
>>>>> =20
>>>>>=20
>>>>>=20
>>>>> /martin
>>>>>=20
>>>>>=20
>>>>>=20
>>>>>=20
>>>>>=20
>>>>> Thanks,
>>>>> Chris.
>>>>>=20
>>>>>=20
>>>>> Moreover, the usage of feature means that, after all, this =
=E2=80=9Ccommon=E2=80=9D is
>>>>> not =E2=80=9Ccommon=E2=80=9D to both cases IKE case and IKE-less. =
Again, it seems
>>>>> confusing. In the IKE case, the SDN/I2NSF controller does not
>>>>> configure the SAD at all but the IKE implementation in the NSF. In =
our
>>>>> opinion, in order to properly add this IPsec SA operational state =
to
>>>>> the IKE case we should include operational data about the IPsec =
SAs
>>>>> (config false) to the ietf-ipsec-ike. Alternatively, we have =
certain
>>>>> operational data (ro) in the SAD structure in the IKE-less case. =
If
>>>>> only those are moved to the common part should be ok but we think =
it
>>>>> does not solve the problem.
>>>>>=20
>>>>> =20
>>>>> --=20
>>>>> last-call mailing list
>>>>> last-call@ietf.org <mailto:last-call@ietf.org>
>>>>> https://www.ietf.org/mailman/listinfo/last-call =
<https://www.ietf.org/mailman/listinfo/last-call>
>>>>>=20
>>>>>=20
>>>>>=20
>>>>> _______________________________________________
>>>>> IPsec mailing list
>>>>> IPsec@ietf.org <mailto:IPsec@ietf.org>
>>>>> https://www.ietf.org/mailman/listinfo/ipsec =
<https://www.ietf.org/mailman/listinfo/ipsec>_____________________________=
__________________
>>>>> 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:=C2=A0rafa@um.es =
<mailto:rafa@um.es>
>>>> -------------------------------------------------------
>>>>=20
>>>>=20
>>>>=20
>>>>=20
>>>> _______________________________________________
>>>> IPsec mailing list
>>>> IPsec@ietf.org <mailto:IPsec@ietf.org>
>>>> https://www.ietf.org/mailman/listinfo/ipsec =
<https://www.ietf.org/mailman/listinfo/ipsec>
>>> _______________________________________________
>>> 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:=C2=A0rafa@um.es =
<mailto:rafa@um.es>
>> -------------------------------------------------------
>>=20
>>=20
>>=20
>>=20
>> _______________________________________________
>> IPsec mailing list
>> IPsec@ietf.org <mailto:IPsec@ietf.org>
>> https://www.ietf.org/mailman/listinfo/ipsec =
<https://www.ietf.org/mailman/listinfo/ipsec>
> _______________________________________________
> IPsec mailing list
> IPsec@ietf.org <mailto:IPsec@ietf.org>
> https://www.ietf.org/mailman/listinfo/ipsec =
<https://www.ietf.org/mailman/listinfo/ipsec>
-------------------------------------------------------
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
-------------------------------------------------------





--Apple-Mail=_372870A4-A581-4A53-8C03-2CCC4A3A7F5C
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: after-white-space;" class=3D"">Hi =
Christian (,Rob):<div class=3D""><br class=3D""></div><div =
class=3D"">Thanks again for this conversation. Please see our comments =
inline.<br class=3D""><div><br class=3D""><blockquote type=3D"cite" =
class=3D""><div class=3D""><div style=3D"caret-color: rgb(0, 0, 0); =
font-family: Courier; font-size: 16px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;" class=3D""><blockquote type=3D"cite" =
class=3D""><div class=3D""><div class=3D"" style=3D"caret-color: rgb(0, =
0, 0); font-family: Helvetica; font-size: 18px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;"><div class=3D""><div class=3D""><br =
class=3D""></div><div class=3D"">As a consequence, the resolution was to =
move forward with a pragmatic approach at this point of time, by =
changing the names of the modules (and prefixes) to refer to the I2NSF =
work.</div></div></div></div></blockquote><div class=3D""><br =
class=3D""></div><div class=3D"">These are 2 different things. The =
original discussion was about moving the SAD and SPD from ikeless module =
to the common one which then would have brought them into the IKE =
module, and required people just implementing IKE to also implement the =
SAD and SPD parts.</div><div class=3D""><br class=3D""></div><div =
class=3D"">In comparison this new compromise request is a tiny change, =
and allows a much larger audience to reap the benefit of your work. The =
change is the addition of "feature ikeless-notification" and then =
putting the "if ikeless-notification" under the =
notifications.</div></div></div></blockquote><blockquote type=3D"cite" =
class=3D""><div class=3D""><div style=3D"caret-color: rgb(0, 0, 0); =
font-family: Courier; font-size: 16px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;" class=3D""><div class=3D""><br =
class=3D""></div><div class=3D"">This doesn't change the semantics of =
your module it just allows people to re-use the ikeless module for =
supporting SAD and SPD w/o implementing the notifications.</div><div =
class=3D""><br class=3D""></div><div class=3D"">If you feel more clarity =
is needed for the SDN use-case then adding the text, "To allow for =
greater re-use of this module, the notifications are marked as a =
feature. For the SDN use case clients will expect this feature to be =
implemented.=E2=80=9D</div></div></div></blockquote><div><br =
class=3D""></div><div><div>We agree that this is a small change (if no =
other change is required). In fact, we have tested it and we have not =
observed any technical problem. The main concern is the one I mentioned =
to Rob: having a feature to =E2=80=9Cactivate=E2=80=9D notifications (or =
not) in the ikeless module does not fit in the context of this I-D, =
unless we find out a valid use case where this feature makes =
sense.&nbsp;</div><div><br class=3D""></div><div>In other words, it =
would be really nice if the inclusion of the text you proposed (=E2=80=9CT=
o allow for greater=E2=80=A6=E2=80=9D ) had a main text to support how =
this is useful in the context of this I-D. Personally, this would make =
me feel more confortable.&nbsp;</div><div class=3D""><br =
class=3D""></div></div><div>Having said all this, let us inform about =
v09 changes to I2NSF wg and ask about this new change in order to see if =
there is any objection. Then, if there is no objection we can prepare =
v10 very quickly with this additional modification.</div><div><br =
class=3D""></div><div>We hope this is reasonable.</div><div><br =
class=3D""></div><div>Best Regards.</div><blockquote type=3D"cite" =
class=3D""><div class=3D""><div style=3D"caret-color: rgb(0, 0, 0); =
font-family: Courier; font-size: 16px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;" class=3D""><br class=3D""></div><div =
style=3D"caret-color: rgb(0, 0, 0); font-family: Courier; font-size: =
16px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none;" =
class=3D"">Features are reported just as modules are in the =
capabilities. An SDN client would look for both capabilities rather than =
just the one (along with all the other capabilities they will be looking =
for to actually be a functional YANG client).</div><div =
style=3D"caret-color: rgb(0, 0, 0); font-family: Courier; font-size: =
16px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none;" class=3D""><br =
class=3D""></div><div style=3D"caret-color: rgb(0, 0, 0); font-family: =
Courier; font-size: 16px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none;" class=3D"">Thanks,</div><div style=3D"caret-color: rgb(0, 0, 0); =
font-family: Courier; font-size: 16px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;" class=3D"">Chris.</div><div style=3D"caret-color: =
rgb(0, 0, 0); font-family: Courier; font-size: 16px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;" class=3D""><br class=3D""><blockquote =
type=3D"cite" class=3D""><div class=3D""><div class=3D"" =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
18px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none;"><div =
class=3D""><div class=3D""><br class=3D""></div><div class=3D"">Best =
Regards.</div><br class=3D""><blockquote type=3D"cite" class=3D""><div =
class=3D""><div class=3D"" style=3D"caret-color: rgb(0, 0, 0); =
font-family: Courier; font-size: 16px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;"><div class=3D""><br class=3D""></div><div =
class=3D"">Thanks,</div><div class=3D"">Chris.</div><br =
class=3D""><blockquote type=3D"cite" class=3D""><div class=3D""><div =
class=3D"" style=3D"font-family: Helvetica; font-size: 18px; font-style: =
normal; font-variant-caps: normal; font-weight: normal; letter-spacing: =
normal; text-align: start; text-indent: 0px; text-transform: none; =
white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none; caret-color: rgb(0, 0, 0);"><br =
class=3D""></div><div class=3D"" style=3D"font-family: Helvetica; =
font-size: 18px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none; caret-color: rgb(0, 0, 0);">Hope this helps.</div><div class=3D"" =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
18px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none;"><br =
class=3D""></div><div class=3D"" style=3D"caret-color: rgb(0, 0, 0); =
font-family: Helvetica; font-size: 18px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;">Best Regards.<br class=3D""><div class=3D""><br =
class=3D""><blockquote type=3D"cite" class=3D""><div class=3D"">El 12 =
oct 2020, a las 18:01, Rob Wilton (rwilton) &lt;<a =
href=3D"mailto:rwilton=3D40cisco.com@dmarc.ietf.org" =
class=3D"">rwilton=3D40cisco.com@dmarc.ietf.org</a>&gt; =
escribi=C3=B3:</div><br class=3D"Apple-interchange-newline"><div =
class=3D""><div class=3D"WordSection1" style=3D"page: WordSection1; =
caret-color: rgb(0, 0, 0); font-family: Courier; font-size: 16px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none;"><div class=3D"" =
style=3D"margin: 0cm; font-size: 11pt; font-family: Calibri, =
sans-serif;"><span class=3D"">Hi Rafa, authors,<o:p =
class=3D""></o:p></span></div><div class=3D"" style=3D"margin: 0cm; =
font-size: 11pt; font-family: Calibri, sans-serif;"><span class=3D""><o:p =
class=3D"">&nbsp;</o:p></span></div><div class=3D"" style=3D"margin: =
0cm; font-size: 11pt; font-family: Calibri, sans-serif;"><span =
class=3D"">Just to check.<o:p class=3D""></o:p></span></div><div =
class=3D"" style=3D"margin: 0cm; font-size: 11pt; font-family: Calibri, =
sans-serif;"><span class=3D""><o:p =
class=3D"">&nbsp;</o:p></span></div><div class=3D"" style=3D"margin: =
0cm; font-size: 11pt; font-family: Calibri, sans-serif;"><span =
class=3D"">Has there been any closure on the suggestion from Chris on =
=E2=80=9C</span><span class=3D"">notifications in the ikeless module as =
a feature"?&nbsp; This would seem to be a fairly cheap &amp; easy =
compromise.<o:p class=3D""></o:p></span></div><div class=3D"" =
style=3D"margin: 0cm; font-size: 11pt; font-family: Calibri, =
sans-serif;"><span class=3D""><o:p =
class=3D"">&nbsp;</o:p></span></div><div class=3D"" style=3D"margin: =
0cm; font-size: 11pt; font-family: Calibri, sans-serif;"><span =
class=3D"">Thanks,<br class=3D"">Rob<o:p =
class=3D""></o:p></span></div><div class=3D"" style=3D"margin: 0cm; =
font-size: 11pt; font-family: Calibri, sans-serif;"><span class=3D""><o:p =
class=3D"">&nbsp;</o:p></span></div><div class=3D"" style=3D"margin: =
0cm; font-size: 11pt; font-family: Calibri, sans-serif;"><span =
class=3D""><o:p class=3D"">&nbsp;</o:p></span></div><div class=3D"" =
style=3D"border-style: none none none solid; border-left-width: 1.5pt; =
border-left-color: blue; padding: 0cm 0cm 0cm 4pt;"><div class=3D""><div =
class=3D"" style=3D"border-style: solid none none; border-top-width: =
1pt; border-top-color: rgb(225, 225, 225); padding: 3pt 0cm 0cm;"><div =
class=3D"" style=3D"margin: 0cm; font-size: 11pt; font-family: Calibri, =
sans-serif;"><b class=3D""><span lang=3D"EN-US" =
class=3D"">From:</span></b><span lang=3D"EN-US" class=3D""><span =
class=3D"Apple-converted-space">&nbsp;</span>yang-doctors &lt;<a =
href=3D"mailto:yang-doctors-bounces@ietf.org" =
class=3D"">yang-doctors-bounces@ietf.org</a>&gt;<span =
class=3D"Apple-converted-space">&nbsp;</span><b class=3D"">On Behalf =
Of<span class=3D"Apple-converted-space">&nbsp;</span></b>Lou Berger<br =
class=3D""><b class=3D"">Sent:</b><span =
class=3D"Apple-converted-space">&nbsp;</span>27 September 2020 15:26<br =
class=3D""><b class=3D"">To:</b><span =
class=3D"Apple-converted-space">&nbsp;</span>Christian Hopps &lt;<a =
href=3D"mailto:chopps@chopps.org" class=3D"">chopps@chopps.org</a>&gt;; =
Martin Bj=C3=B6rklund &lt;<a href=3D"mailto:mbj+ietf@4668.se" =
class=3D"">mbj+ietf@4668.se</a>&gt;<br class=3D""><b =
class=3D"">Cc:</b><span =
class=3D"Apple-converted-space">&nbsp;</span>Robert Wilton &lt;<a =
href=3D"mailto:rwilton=3D40cisco.com@dmarc.ietf.org" =
class=3D"">rwilton=3D40cisco.com@dmarc.ietf.org</a>&gt;;<span =
class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"mailto:i2nsf@ietf.org" class=3D"">i2nsf@ietf.org</a>; Gabriel =
Lopez &lt;<a href=3D"mailto:gabilm@um.es" =
class=3D"">gabilm@um.es</a>&gt;;<span =
class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"mailto:draft-ietf-i2nsf-sdn-ipsec-flow-protection.all@ietf.org" =
class=3D"">draft-ietf-i2nsf-sdn-ipsec-flow-protection.all@ietf.org</a>;<sp=
an class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"mailto:ipsec@ietf.org" class=3D"">ipsec@ietf.org</a>;<span =
class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"mailto:last-call@ietf.org" class=3D"">last-call@ietf.org</a>; =
Rafa Marin-Lopez &lt;<a href=3D"mailto:rafa@um.es" =
class=3D"">rafa@um.es</a>&gt;;<span =
class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"mailto:yang-doctors@ietf.org" =
class=3D"">yang-doctors@ietf.org</a><br class=3D""><b =
class=3D"">Subject:</b><span =
class=3D"Apple-converted-space">&nbsp;</span>Re: [yang-doctors] [IPsec] =
[Last-Call] [I2nsf] Yangdoctors last call review of =
draft-ietf-i2nsf-sdn-ipsec-flow-protection-08<o:p =
class=3D""></o:p></span></div></div></div><div class=3D"" style=3D"margin:=
 0cm; font-size: 11pt; font-family: Calibri, sans-serif;"><o:p =
class=3D"">&nbsp;</o:p></div><blockquote class=3D"" style=3D"margin-top: =
5pt; margin-bottom: 5pt;"><div class=3D""><div class=3D"" style=3D"margin:=
 0cm; font-size: 11pt; font-family: Calibri, sans-serif;">This is a =
sub-optimal compromise b/c all IPsec have SA databases even ones running =
IKE -- i.e., SA databases are common whether exposed in YANG or not -- =
but if it can move it forward perhaps good enough.<o:p =
class=3D""></o:p></div></div><div class=3D""><div class=3D"" =
style=3D"margin: 0cm; font-size: 11pt; font-family: Calibri, =
sans-serif;"><br class=3D""><br class=3D""><o:p =
class=3D""></o:p></div></div></blockquote><div class=3D"" style=3D"margin:=
 0cm; font-size: 11pt; font-family: Calibri, sans-serif;">Speaking as an =
interested party, I hope that some compromise / good enough solution is =
followed in the -09 version of&nbsp; this draft.<o:p =
class=3D""></o:p></div><p class=3D"">Lou<o:p class=3D""></o:p></p><div =
class=3D""><div class=3D"" style=3D"margin: 0cm; font-size: 11pt; =
font-family: Calibri, sans-serif;">On 9/23/2020 7:20 AM, Christian Hopps =
wrote:<o:p class=3D""></o:p></div></div><blockquote class=3D"" =
style=3D"margin-top: 5pt; margin-bottom: 5pt;"><div class=3D"" =
style=3D"margin: 0cm; font-size: 11pt; font-family: Calibri, =
sans-serif;"><o:p class=3D"">&nbsp;</o:p></div><div class=3D""><div =
class=3D"" style=3D"margin: 0cm; font-size: 11pt; font-family: Calibri, =
sans-serif;"><br class=3D""><br class=3D""><o:p =
class=3D""></o:p></div><blockquote class=3D"" style=3D"margin-top: 5pt; =
margin-bottom: 5pt;"><div class=3D""><div class=3D"" style=3D"margin: =
0cm; font-size: 11pt; font-family: Calibri, sans-serif;">On Sep 23, =
2020, at 6:58 AM, Martin Bj=C3=B6rklund &lt;<a =
href=3D"mailto:mbj+ietf@4668.se" class=3D"" style=3D"color: blue; =
text-decoration: underline;">mbj+ietf@4668.se</a>&gt; wrote:<o:p =
class=3D""></o:p></div></div><div class=3D"" style=3D"margin: 0cm; =
font-size: 11pt; font-family: Calibri, sans-serif;"><o:p =
class=3D"">&nbsp;</o:p></div><div class=3D""><div class=3D"" =
style=3D"margin: 0cm; font-size: 11pt; font-family: Calibri, =
sans-serif;"><span class=3D"" style=3D"font-size: 10.5pt; font-family: =
Menlo-Regular, serif;">Hi,<br class=3D""><br class=3D"">Christian Hopps =
&lt;</span><a href=3D"mailto:chopps@chopps.org" class=3D"" style=3D"color:=
 blue; text-decoration: underline;"><span class=3D"" style=3D"font-size: =
10.5pt; font-family: Menlo-Regular, =
serif;">chopps@chopps.org</span></a><span class=3D"" style=3D"font-size: =
10.5pt; font-family: Menlo-Regular, serif;">&gt; wrote:<br class=3D"" =
style=3D"caret-color: rgb(0, 0, 0); font-variant-caps: normal; =
text-align: start; -webkit-text-stroke-width: 0px; word-spacing: =
0px;"><br class=3D""></span><o:p class=3D""></o:p></div><blockquote =
class=3D"" style=3D"margin-top: 5pt; margin-bottom: 5pt;"><div class=3D"" =
style=3D"margin: 0cm; font-size: 11pt; font-family: Calibri, =
sans-serif;"><span class=3D"" style=3D"font-size: 10.5pt; font-family: =
Menlo-Regular, serif;"><br class=3D""><br class=3D""><br class=3D""><o:p =
class=3D""></o:p></span></div><blockquote class=3D"" style=3D"margin-top: =
5pt; margin-bottom: 5pt;"><div class=3D"" style=3D"margin: 0cm; =
font-size: 11pt; font-family: Calibri, sans-serif;"><span class=3D"" =
style=3D"font-size: 10.5pt; font-family: Menlo-Regular, serif;">On Sep =
23, 2020, at 5:29 AM, Rafa Marin-Lopez &lt;<a href=3D"mailto:rafa@um.es" =
class=3D"" style=3D"color: blue; text-decoration: =
underline;">rafa@um.es</a>&gt; wrote:<br class=3D""><br class=3D""><br =
class=3D""><o:p class=3D""></o:p></span></div><blockquote class=3D"" =
style=3D"margin-top: 5pt; margin-bottom: 5pt;"><div class=3D"" =
style=3D"margin: 0cm; font-size: 11pt; font-family: Calibri, =
sans-serif;"><span class=3D"" style=3D"font-size: 10.5pt; font-family: =
Menlo-Regular, serif;"><br class=3D""><br class=3D"">But I would like to =
check: My understanding is that the changes that<br class=3D"">Chris is =
proposing are pretty small. &nbsp;I.e. move the SA structure under<br =
class=3D"">ipsec-common, and put it under a YANG feature. &nbsp;Are you =
sure that it<br class=3D"">is impractical to accommodate this change =
which would allow a single<br class=3D"">ipsec module to be shared and =
extended via YANG augmentations?<o:p =
class=3D""></o:p></span></div></blockquote><div class=3D"" =
style=3D"margin: 0cm; font-size: 11pt; font-family: Calibri, =
sans-serif;"><span class=3D"" style=3D"font-size: 10.5pt; font-family: =
Menlo-Regular, serif;"><br class=3D""><br class=3D"">In the context of =
our I-D, if we move SAD structure to ipsec-common,<br class=3D"">what we =
are meaning is that IPsec SA configuration data (setting<br =
class=3D"">values to the SAD structure) are common to the IKE case and =
the<br class=3D"">IKE-less cases, which are not. It is confusing.<o:p =
class=3D""></o:p></span></div></blockquote><div class=3D"" =
style=3D"margin: 0cm; font-size: 11pt; font-family: Calibri, =
sans-serif;"><span class=3D"" style=3D"font-size: 10.5pt; font-family: =
Menlo-Regular, serif;"><br class=3D"">Something defined in a common =
module but marked as a feature does not<br class=3D"">imply that that =
feature has to be implemented by an importing<br class=3D"">module. This =
is not confusing to YANG implementers or users I<br class=3D"">think. If =
we are just talking about document flow here, then a<br =
class=3D"">sentence saying "the SAD feature is not required to implement =
IKE<br class=3D"">functionality" is quite enough to clear that up I =
think.<o:p class=3D""></o:p></span></div></blockquote><div class=3D"" =
style=3D"margin: 0cm; font-size: 11pt; font-family: Calibri, =
sans-serif;"><span class=3D"" style=3D"font-size: 10.5pt; font-family: =
Menlo-Regular, serif;"><br class=3D"">Another alternative could be to =
move these containers to another<br class=3D"">(new) module.</span><o:p =
class=3D""></o:p></div></div></blockquote><div class=3D""><div class=3D"" =
style=3D"margin: 0cm; font-size: 11pt; font-family: Calibri, =
sans-serif;"><o:p class=3D"">&nbsp;</o:p></div></div><div class=3D"" =
style=3D"margin: 0cm; font-size: 11pt; font-family: Calibri, =
sans-serif;"><span class=3D"">It may also be enough to mark the =
notifications in the ikeless module as a feature I suppose. That is the =
actual thing I think non-SDN implementations would want to omit. The =
module name "ikeless" is not great in this case, but perhaps =
workable.</span><o:p class=3D""></o:p></div></div><div class=3D""><div =
class=3D"" style=3D"margin: 0cm; font-size: 11pt; font-family: Calibri, =
sans-serif;"><span class=3D""><br class=3D""><br class=3D""></span><o:p =
class=3D""></o:p></div></div><div class=3D""><div class=3D"" =
style=3D"margin: 0cm; font-size: 11pt; font-family: Calibri, =
sans-serif;"><span class=3D"">This is a sub-optimal compromise b/c all =
IPsec have SA databases even ones running IKE -- i.e., SA databases are =
common whether exposed in YANG or not -- but if it can move it forward =
perhaps good enough.</span><o:p class=3D""></o:p></div></div><div =
class=3D""><div class=3D"" style=3D"margin: 0cm; font-size: 11pt; =
font-family: Calibri, sans-serif;"><span class=3D""><br class=3D""><br =
class=3D""></span><o:p class=3D""></o:p></div></div><div class=3D""><div =
class=3D"" style=3D"margin: 0cm; font-size: 11pt; font-family: Calibri, =
sans-serif;"><span class=3D"">I'm definitely concerned about IETF =
process and real world usability here. These modules are basically =
workable for ipsec I think, they could be used by operators today. If we =
restart the entire process to redo this work for the more generic IPsec =
case it will probably be years before they are finished and in the =
field. This new work can be started, but why not have something usable =
in the meantime?</span><o:p class=3D""></o:p></div></div><div =
class=3D""><div class=3D"" style=3D"margin: 0cm; font-size: 11pt; =
font-family: Calibri, sans-serif;"><o:p =
class=3D"">&nbsp;</o:p></div></div><div class=3D""><div class=3D"" =
style=3D"margin: 0cm; font-size: 11pt; font-family: Calibri, =
sans-serif;">Thanks,<o:p class=3D""></o:p></div></div><div class=3D""><div=
 class=3D"" style=3D"margin: 0cm; font-size: 11pt; font-family: Calibri, =
sans-serif;">Chris.<o:p class=3D""></o:p></div></div><div class=3D""><div =
class=3D"" style=3D"margin: 0cm; font-size: 11pt; font-family: Calibri, =
sans-serif;"><o:p class=3D"">&nbsp;</o:p></div></div><div =
class=3D""><blockquote class=3D"" style=3D"margin-top: 5pt; =
margin-bottom: 5pt;"><div class=3D""><div class=3D"" style=3D"margin: =
0cm; font-size: 11pt; font-family: Calibri, sans-serif;"><span class=3D"" =
style=3D"font-size: 10.5pt; font-family: Menlo-Regular, serif;"><br =
class=3D""><br class=3D"">/martin<br class=3D""><br class=3D""><br =
class=3D""><br class=3D"" style=3D"caret-color: rgb(0, 0, 0); =
font-variant-caps: normal; text-align: start; -webkit-text-stroke-width: =
0px; word-spacing: 0px;"><br class=3D""></span><o:p =
class=3D""></o:p></div><blockquote class=3D"" style=3D"margin-top: 5pt; =
margin-bottom: 5pt;"><div class=3D"" style=3D"margin: 0cm; font-size: =
11pt; font-family: Calibri, sans-serif;"><span class=3D"" =
style=3D"font-size: 10.5pt; font-family: Menlo-Regular, serif;"><br =
class=3D"">Thanks,<br class=3D"">Chris.<br class=3D""><br class=3D""><br =
class=3D""><o:p class=3D""></o:p></span></div><blockquote class=3D"" =
style=3D"margin-top: 5pt; margin-bottom: 5pt;"><p class=3D"MsoNormal" =
style=3D"margin: 0cm 0cm 12pt; font-size: 11pt; font-family: Calibri, =
sans-serif;"><span class=3D"" style=3D"font-size: 10.5pt; font-family: =
Menlo-Regular, serif;">Moreover, the usage of feature means that, after =
all, this =E2=80=9Ccommon=E2=80=9D is<br class=3D"">not =E2=80=9Ccommon=E2=
=80=9D to both cases IKE case and IKE-less. Again, it seems<br =
class=3D"">confusing. In the IKE case, the SDN/I2NSF controller does =
not<br class=3D"">configure the SAD at all but the IKE implementation in =
the NSF. In our<br class=3D"">opinion, in order to properly add this =
IPsec SA operational state to<br class=3D"">the IKE case we should =
include operational data about the IPsec SAs<br class=3D"">(config =
false) to the ietf-ipsec-ike. Alternatively, we have certain<br =
class=3D"">operational data (ro) in the SAD structure in the IKE-less =
case. If<br class=3D"">only those are moved to the common part should be =
ok but we think it<br class=3D"">does not solve the problem.<o:p =
class=3D""></o:p></span></p></blockquote><div class=3D"" style=3D"margin: =
0cm; font-size: 11pt; font-family: Calibri, sans-serif;"><span class=3D"" =
style=3D"font-size: 10.5pt; font-family: Menlo-Regular, serif;"><o:p =
class=3D"">&nbsp;</o:p></span></div></blockquote><div class=3D"" =
style=3D"margin: 0cm; font-size: 11pt; font-family: Calibri, =
sans-serif;"><span class=3D"" style=3D"font-size: 10.5pt; font-family: =
Menlo-Regular, serif;">--<span =
class=3D"apple-converted-space">&nbsp;</span><br class=3D"">last-call =
mailing list<br class=3D""></span><a href=3D"mailto:last-call@ietf.org" =
class=3D"" style=3D"color: blue; text-decoration: underline;"><span =
class=3D"" style=3D"font-size: 10.5pt; font-family: Menlo-Regular, =
serif;">last-call@ietf.org</span></a><span class=3D"" style=3D"font-size: =
10.5pt; font-family: Menlo-Regular, serif;"><br class=3D""></span><a =
href=3D"https://www.ietf.org/mailman/listinfo/last-call" class=3D"" =
style=3D"color: blue; text-decoration: underline;"><span class=3D"" =
style=3D"font-size: 10.5pt; font-family: Menlo-Regular, =
serif;">https://www.ietf.org/mailman/listinfo/last-call</span></a><o:p =
class=3D""></o:p></div></div></blockquote></div><div class=3D"" =
style=3D"margin: 0cm; font-size: 11pt; font-family: Calibri, =
sans-serif;"><br class=3D""><br class=3D""><br class=3D""><o:p =
class=3D""></o:p></div><pre class=3D"" style=3D"margin: 0cm; font-size: =
10pt; font-family: &quot;Courier =
New&quot;;">_______________________________________________<o:p =
class=3D""></o:p></pre><pre class=3D"" style=3D"margin: 0cm; font-size: =
10pt; font-family: &quot;Courier New&quot;;">IPsec mailing list<o:p =
class=3D""></o:p></pre><pre class=3D"" style=3D"margin: 0cm; font-size: =
10pt; font-family: &quot;Courier New&quot;;"><a =
href=3D"mailto:IPsec@ietf.org" class=3D"" style=3D"color: blue; =
text-decoration: underline;">IPsec@ietf.org</a><o:p =
class=3D""></o:p></pre><pre class=3D"" style=3D"margin: 0cm; font-size: =
10pt; font-family: &quot;Courier New&quot;;"><a =
href=3D"https://www.ietf.org/mailman/listinfo/ipsec" class=3D"" =
style=3D"color: blue; text-decoration: =
underline;">https://www.ietf.org/mailman/listinfo/ipsec</a><o:p =
class=3D""></o:p></pre></blockquote></div></div><span class=3D"" =
style=3D"caret-color: rgb(0, 0, 0); font-family: Courier; font-size: =
16px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none; float: none; =
display: inline =
!important;">_______________________________________________</span><br =
class=3D"" style=3D"caret-color: rgb(0, 0, 0); font-family: Courier; =
font-size: 16px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none;"><span class=3D"" style=3D"caret-color: rgb(0, 0, 0); font-family: =
Courier; font-size: 16px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none; float: none; display: inline !important;">I2nsf mailing =
list</span><br class=3D"" style=3D"caret-color: rgb(0, 0, 0); =
font-family: Courier; font-size: 16px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;"><span class=3D"" style=3D"caret-color: rgb(0, 0, =
0); font-family: Courier; font-size: 16px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none; float: none; display: inline !important;"><a =
href=3D"mailto:I2nsf@ietf.org" class=3D"">I2nsf@ietf.org</a></span><br =
class=3D"" style=3D"caret-color: rgb(0, 0, 0); font-family: Courier; =
font-size: 16px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none;"><span class=3D"" style=3D"caret-color: rgb(0, 0, 0); font-family: =
Courier; font-size: 16px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none; float: none; display: inline !important;"><a =
href=3D"https://www.ietf.org/mailman/listinfo/i2nsf" =
class=3D"">https://www.ietf.org/mailman/listinfo/i2nsf</a></span></div></b=
lockquote></div><br class=3D""><div class=3D""><div class=3D"" =
style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; line-break: =
after-white-space;"><div class=3D"" style=3D"font-family: Courier; =
font-size: 16px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: =
0px;">-------------------------------------------------------<br =
class=3D"">Rafa Marin-Lopez, PhD<br class=3D"">Dept. Information =
and&nbsp;Communications&nbsp;Engineering (DIIC)<br class=3D"">Faculty of =
Computer&nbsp;Science-University of&nbsp;Murcia<br class=3D"">30100 =
Murcia - Spain<br class=3D"">Telf: +34868888501 =
Fax:&nbsp;+34868884151<span =
class=3D"Apple-converted-space">&nbsp;</span><a href=3D"mailto:rafa@um.es"=
 class=3D"">e-mail:&nbsp;rafa@um.es</a><br =
class=3D"">-------------------------------------------------------</div><d=
iv class=3D"" style=3D"font-family: Courier; font-size: 16px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px;"><br class=3D""></div><br =
class=3D"Apple-interchange-newline"></div><br =
class=3D"Apple-interchange-newline"></div><br class=3D""></div><span =
class=3D"" style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; =
font-size: 18px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none; float: none; display: inline =
!important;">_______________________________________________</span><br =
class=3D"" style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; =
font-size: 18px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none;"><span class=3D"" style=3D"caret-color: rgb(0, 0, 0); font-family: =
Helvetica; font-size: 18px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none; float: none; display: inline !important;">IPsec mailing =
list</span><br class=3D"" style=3D"caret-color: rgb(0, 0, 0); =
font-family: Helvetica; font-size: 18px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;"><a href=3D"mailto:IPsec@ietf.org" class=3D"" =
style=3D"font-family: Helvetica; font-size: 18px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: =
0px;">IPsec@ietf.org</a><br class=3D"" style=3D"caret-color: rgb(0, 0, =
0); font-family: Helvetica; font-size: 18px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;"><a =
href=3D"https://www.ietf.org/mailman/listinfo/ipsec" class=3D"" =
style=3D"font-family: Helvetica; font-size: 18px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: =
0px;">https://www.ietf.org/mailman/listinfo/ipsec</a></div></blockquote></=
div><br class=3D"" style=3D"caret-color: rgb(0, 0, 0); font-family: =
Courier; font-size: 16px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none;"><span class=3D"" style=3D"caret-color: rgb(0, 0, 0); font-family: =
Courier; font-size: 16px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none; float: none; display: inline =
!important;">_______________________________________________</span><br =
class=3D"" style=3D"caret-color: rgb(0, 0, 0); font-family: Courier; =
font-size: 16px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none;"><span class=3D"" style=3D"caret-color: rgb(0, 0, 0); font-family: =
Courier; font-size: 16px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none; float: none; display: inline !important;">I2nsf mailing =
list</span><br class=3D"" style=3D"caret-color: rgb(0, 0, 0); =
font-family: Courier; font-size: 16px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;"><a href=3D"mailto:I2nsf@ietf.org" class=3D"" =
style=3D"font-family: Courier; font-size: 16px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: =
0px;">I2nsf@ietf.org</a><br class=3D"" style=3D"caret-color: rgb(0, 0, =
0); font-family: Courier; font-size: 16px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;"><a =
href=3D"https://www.ietf.org/mailman/listinfo/i2nsf" class=3D"" =
style=3D"font-family: Courier; font-size: 16px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: =
0px;">https://www.ietf.org/mailman/listinfo/i2nsf</a></div></blockquote></=
div><br class=3D""><div class=3D""><div class=3D"" style=3D"word-wrap: =
break-word; -webkit-nbsp-mode: space; line-break: =
after-white-space;"><div class=3D"" style=3D"font-family: Courier; =
font-size: 16px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: =
0px;">-------------------------------------------------------<br =
class=3D"">Rafa Marin-Lopez, PhD<br class=3D"">Dept. Information =
and&nbsp;Communications&nbsp;Engineering (DIIC)<br class=3D"">Faculty of =
Computer&nbsp;Science-University of&nbsp;Murcia<br class=3D"">30100 =
Murcia - Spain<br class=3D"">Telf: +34868888501 =
Fax:&nbsp;+34868884151<span =
class=3D"Apple-converted-space">&nbsp;</span><a href=3D"mailto:rafa@um.es"=
 class=3D"">e-mail:&nbsp;rafa@um.es</a><br =
class=3D"">-------------------------------------------------------</div><d=
iv class=3D"" style=3D"font-family: Courier; font-size: 16px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px;"><br class=3D""></div><br =
class=3D"Apple-interchange-newline"></div><br =
class=3D"Apple-interchange-newline"></div><br class=3D""></div><span =
class=3D"" style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; =
font-size: 18px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none; float: none; display: inline =
!important;">_______________________________________________</span><br =
class=3D"" style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; =
font-size: 18px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none;"><span class=3D"" style=3D"caret-color: rgb(0, 0, 0); font-family: =
Helvetica; font-size: 18px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none; float: none; display: inline !important;">IPsec mailing =
list</span><br class=3D"" style=3D"caret-color: rgb(0, 0, 0); =
font-family: Helvetica; font-size: 18px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;"><a href=3D"mailto:IPsec@ietf.org" class=3D"" =
style=3D"font-family: Helvetica; font-size: 18px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: =
0px;">IPsec@ietf.org</a><br class=3D"" style=3D"caret-color: rgb(0, 0, =
0); font-family: Helvetica; font-size: 18px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;"><a =
href=3D"https://www.ietf.org/mailman/listinfo/ipsec" class=3D"" =
style=3D"font-family: Helvetica; font-size: 18px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: =
0px;">https://www.ietf.org/mailman/listinfo/ipsec</a></div></blockquote></=
div><br class=3D"" style=3D"caret-color: rgb(0, 0, 0); font-family: =
Courier; font-size: 16px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none;"><span style=3D"caret-color: rgb(0, 0, 0); font-family: Courier; =
font-size: 16px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none; float: none; display: inline !important;" =
class=3D"">_______________________________________________</span><br =
style=3D"caret-color: rgb(0, 0, 0); font-family: Courier; font-size: =
16px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none;" class=3D""><span =
style=3D"caret-color: rgb(0, 0, 0); font-family: Courier; font-size: =
16px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none; float: none; =
display: inline !important;" class=3D"">IPsec mailing list</span><br =
style=3D"caret-color: rgb(0, 0, 0); font-family: Courier; font-size: =
16px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none;" class=3D""><a =
href=3D"mailto:IPsec@ietf.org" style=3D"font-family: Courier; font-size: =
16px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; orphans: auto; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; widows: =
auto; word-spacing: 0px; -webkit-text-size-adjust: auto; =
-webkit-text-stroke-width: 0px;" class=3D"">IPsec@ietf.org</a><br =
style=3D"caret-color: rgb(0, 0, 0); font-family: Courier; font-size: =
16px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none;" class=3D""><a =
href=3D"https://www.ietf.org/mailman/listinfo/ipsec" style=3D"font-family:=
 Courier; font-size: 16px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; orphans: auto; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; =
-webkit-text-stroke-width: 0px;" =
class=3D"">https://www.ietf.org/mailman/listinfo/ipsec</a></div></blockquo=
te></div><br class=3D""><div class=3D"">
<div style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space;" class=3D""><div style=3D"color: =
rgb(0, 0, 0); font-family: Courier; font-size: 16px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
orphans: auto; text-align: start; text-indent: 0px; text-transform: =
none; white-space: normal; widows: auto; word-spacing: 0px; =
-webkit-text-stroke-width: =
0px;">-------------------------------------------------------<br =
class=3D"">Rafa Marin-Lopez, PhD<br class=3D"">Dept. Information =
and&nbsp;Communications&nbsp;Engineering (DIIC)<br class=3D"">Faculty of =
Computer&nbsp;Science-University of&nbsp;Murcia<br class=3D"">30100 =
Murcia - Spain<br class=3D"">Telf: +34868888501 Fax:&nbsp;+34868884151 =
<a href=3D"mailto:rafa@um.es" class=3D"">e-mail:&nbsp;rafa@um.es</a><br =
class=3D"">-------------------------------------------------------</div><d=
iv style=3D"color: rgb(0, 0, 0); font-family: Courier; font-size: 16px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; orphans: auto; text-align: start; text-indent: =
0px; text-transform: none; white-space: normal; widows: auto; =
word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=3D""><br =
class=3D""></div><br class=3D"Apple-interchange-newline"></div><br =
class=3D"Apple-interchange-newline">
</div>
<br class=3D""></div></body></html>=

--Apple-Mail=_372870A4-A581-4A53-8C03-2CCC4A3A7F5C--


From nobody Thu Oct 15 03:48:35 2020
Return-Path: <chopps@chopps.org>
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 9C7A73A1370; Thu, 15 Oct 2020 03:48:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level: 
X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 DePdojSIs790; Thu, 15 Oct 2020 03:48:31 -0700 (PDT)
Received: from smtp.chopps.org (smtp.chopps.org [54.88.81.56]) by ietfa.amsl.com (Postfix) with ESMTP id 8E3CE3A11D1; Thu, 15 Oct 2020 03:48:30 -0700 (PDT)
Received: from stubbs.int.chopps.org (047-050-069-038.biz.spectrum.com [47.50.69.38]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by smtp.chopps.org (Postfix) with ESMTPSA id 624F26166F; Thu, 15 Oct 2020 10:48:27 +0000 (UTC)
From: Christian Hopps <chopps@chopps.org>
Message-Id: <0492AF3E-7A7D-4853-84CE-C13155F3E4D9@chopps.org>
Content-Type: multipart/signed; boundary="Apple-Mail=_71DD0E65-CAB8-4BA2-A065-0E5B1AC62BF0"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\))
Date: Thu, 15 Oct 2020 06:48:26 -0400
In-Reply-To: <1142B610-2D58-4DE5-96F7-773D02C1B42A@um.es>
Cc: Christian Hopps <chopps@chopps.org>, "Rob Wilton (rwilton)" <rwilton@cisco.com>, "last-call@ietf.org" <last-call@ietf.org>, Gabriel Lopez <gabilm@um.es>, "draft-ietf-i2nsf-sdn-ipsec-flow-protection.all@ietf.org" <draft-ietf-i2nsf-sdn-ipsec-flow-protection.all@ietf.org>,  "ipsec@ietf.org" <ipsec@ietf.org>, "i2nsf@ietf.org" <i2nsf@ietf.org>, =?utf-8?Q?Martin_Bj=C3=B6rklund?= <mbj+ietf@4668.se>, "yang-doctors@ietf.org" <yang-doctors@ietf.org>, Lou Berger <lberger@labn.net>, Fernando Pereniguez-Garcia <fernando.pereniguez@cud.upct.es>
To: Rafa Marin-Lopez <rafa@um.es>
References: <MN2PR11MB4366E30B3C372D13B391AE07B53B0@MN2PR11MB4366.namprd11.prod.outlook.com> <2B88888E-A264-4D81-A8DA-9C6225E83E0E@um.es> <70A0A406-0742-4F28-A5A4-8D539B160E24@chopps.org> <20200923.125826.1562347052257995146.id@4668.se> <CBC552B2-6039-48E8-988D-4F2BA3FD6B2E@chopps.org> <023fc27b-f86e-ed71-0c8f-d270c338f08c@labn.net> <MN2PR11MB43662E1711367EDE9A066452B5070@MN2PR11MB4366.namprd11.prod.outlook.com> <E827743C-74A1-42CE-9765-7ECD062D8E41@um.es> <10116C35-8FBF-4914-9846-883D2C7F7A11@chopps.org> <B3282660-5C6A-4B69-8CFC-57AFBCE2B544@um.es> <7C422A91-5543-41A0-B907-6AAD9F83E6DA@chopps.org> <1142B610-2D58-4DE5-96F7-773D02C1B42A@um.es>
X-Mailer: Apple Mail (2.3608.120.23.2.4)
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2nsf/8VRnX8sT5QpDqDRdx8DAZe8ssyw>
Subject: Re: [I2nsf] [IPsec] [yang-doctors] [Last-Call] Yangdoctors last call review of draft-ietf-i2nsf-sdn-ipsec-flow-protection-08
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: Thu, 15 Oct 2020 10:48:34 -0000

--Apple-Mail=_71DD0E65-CAB8-4BA2-A065-0E5B1AC62BF0
Content-Type: multipart/alternative;
	boundary="Apple-Mail=_90E89900-8AF2-4D6D-A86C-349952FD86D1"


--Apple-Mail=_90E89900-8AF2-4D6D-A86C-349952FD86D1
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

This is great news, Thanks!

IMO (Rob feel free to chime in here :) I don't think you need to say =
anything more about the feature in your document (other than what was =
already mentioned). This is the standard "outside the scope of this =
document" kind of thing. It's enough to put that text that says they are =
marked as a feature for greater re-usability, but SDN clients will =
expect the feature to be implemented.

FWIW, When talking about YANG features I'd use the turn of phrase "to =
indicate whether notifications are implemented by the server" rather =
than 'to "activate" notifications'. They don't get turned on or off, =
they are either implemented or not. You could swap "implemented" with =
"supported" too here with the same meaning.

Thanks,
Chris.

> On Oct 15, 2020, at 3:12 AM, Rafa Marin-Lopez <rafa@um.es> wrote:
>=20
> Hi Christian (,Rob):
>=20
> Thanks again for this conversation. Please see our comments inline.
>=20
>>>=20
>>> As a consequence, the resolution was to move forward with a =
pragmatic approach at this point of time, by changing the names of the =
modules (and prefixes) to refer to the I2NSF work.
>>=20
>> These are 2 different things. The original discussion was about =
moving the SAD and SPD from ikeless module to the common one which then =
would have brought them into the IKE module, and required people just =
implementing IKE to also implement the SAD and SPD parts.
>>=20
>> In comparison this new compromise request is a tiny change, and =
allows a much larger audience to reap the benefit of your work. The =
change is the addition of "feature ikeless-notification" and then =
putting the "if ikeless-notification" under the notifications.
>>=20
>> This doesn't change the semantics of your module it just allows =
people to re-use the ikeless module for supporting SAD and SPD w/o =
implementing the notifications.
>>=20
>> If you feel more clarity is needed for the SDN use-case then adding =
the text, "To allow for greater re-use of this module, the notifications =
are marked as a feature. For the SDN use case clients will expect this =
feature to be implemented.=E2=80=9D
>=20
> We agree that this is a small change (if no other change is required). =
In fact, we have tested it and we have not observed any technical =
problem. The main concern is the one I mentioned to Rob: having a =
feature to =E2=80=9Cactivate=E2=80=9D notifications (or not) in the =
ikeless module does not fit in the context of this I-D, unless we find =
out a valid use case where this feature makes sense.
>=20
> In other words, it would be really nice if the inclusion of the text =
you proposed (=E2=80=9CTo allow for greater=E2=80=A6=E2=80=9D ) had a =
main text to support how this is useful in the context of this I-D. =
Personally, this would make me feel more confortable.
>=20
> Having said all this, let us inform about v09 changes to I2NSF wg and =
ask about this new change in order to see if there is any objection. =
Then, if there is no objection we can prepare v10 very quickly with this =
additional modification.
>=20
> We hope this is reasonable.
>=20
> Best Regards.
>>=20
>> Features are reported just as modules are in the capabilities. An SDN =
client would look for both capabilities rather than just the one (along =
with all the other capabilities they will be looking for to actually be =
a functional YANG client).
>>=20
>> Thanks,
>> Chris.
>>=20
>>>=20
>>> Best Regards.
>>>=20
>>>>=20
>>>> Thanks,
>>>> Chris.
>>>>=20
>>>>>=20
>>>>> Hope this helps.
>>>>>=20
>>>>> Best Regards.
>>>>>=20
>>>>>> El 12 oct 2020, a las 18:01, Rob Wilton (rwilton) =
<rwilton=3D40cisco.com@dmarc.ietf.org =
<mailto:rwilton=3D40cisco.com@dmarc.ietf.org>> escribi=C3=B3:
>>>>>>=20
>>>>>> Hi Rafa, authors,
>>>>>>=20
>>>>>> Just to check.
>>>>>>=20
>>>>>> Has there been any closure on the suggestion from Chris on =
=E2=80=9Cnotifications in the ikeless module as a feature"?  This would =
seem to be a fairly cheap & easy compromise.
>>>>>>=20
>>>>>> Thanks,
>>>>>> Rob
>>>>>>=20
>>>>>>=20
>>>>>> From: yang-doctors <yang-doctors-bounces@ietf.org =
<mailto:yang-doctors-bounces@ietf.org>> On Behalf Of Lou Berger
>>>>>> Sent: 27 September 2020 15:26
>>>>>> To: Christian Hopps <chopps@chopps.org =
<mailto:chopps@chopps.org>>; Martin Bj=C3=B6rklund <mbj+ietf@4668.se =
<mailto:mbj+ietf@4668.se>>
>>>>>> Cc: Robert Wilton <rwilton=3D40cisco.com@dmarc.ietf.org =
<mailto:rwilton=3D40cisco.com@dmarc.ietf.org>>; i2nsf@ietf.org =
<mailto:i2nsf@ietf.org>; Gabriel Lopez <gabilm@um.es =
<mailto:gabilm@um.es>>; =
draft-ietf-i2nsf-sdn-ipsec-flow-protection.all@ietf.org =
<mailto:draft-ietf-i2nsf-sdn-ipsec-flow-protection.all@ietf.org>; =
ipsec@ietf.org <mailto:ipsec@ietf.org>; last-call@ietf.org =
<mailto:last-call@ietf.org>; Rafa Marin-Lopez <rafa@um.es =
<mailto:rafa@um.es>>; yang-doctors@ietf.org =
<mailto:yang-doctors@ietf.org>
>>>>>> Subject: Re: [yang-doctors] [IPsec] [Last-Call] [I2nsf] =
Yangdoctors last call review of =
draft-ietf-i2nsf-sdn-ipsec-flow-protection-08
>>>>>>=20
>>>>>> This is a sub-optimal compromise b/c all IPsec have SA databases =
even ones running IKE -- i.e., SA databases are common whether exposed =
in YANG or not -- but if it can move it forward perhaps good enough.
>>>>>>=20
>>>>>>=20
>>>>>> Speaking as an interested party, I hope that some compromise / =
good enough solution is followed in the -09 version of  this draft.
>>>>>> Lou
>>>>>>=20
>>>>>> On 9/23/2020 7:20 AM, Christian Hopps wrote:
>>>>>>=20
>>>>>>=20
>>>>>>=20
>>>>>> On Sep 23, 2020, at 6:58 AM, Martin Bj=C3=B6rklund =
<mbj+ietf@4668.se <mailto:mbj+ietf@4668.se>> wrote:
>>>>>>=20
>>>>>> Hi,
>>>>>>=20
>>>>>> Christian Hopps <chopps@chopps.org <mailto:chopps@chopps.org>> =
wrote:
>>>>>>=20
>>>>>>=20
>>>>>>=20
>>>>>>=20
>>>>>> On Sep 23, 2020, at 5:29 AM, Rafa Marin-Lopez <rafa@um.es =
<mailto:rafa@um.es>> wrote:
>>>>>>=20
>>>>>>=20
>>>>>>=20
>>>>>>=20
>>>>>> But I would like to check: My understanding is that the changes =
that
>>>>>> Chris is proposing are pretty small.  I.e. move the SA structure =
under
>>>>>> ipsec-common, and put it under a YANG feature.  Are you sure that =
it
>>>>>> is impractical to accommodate this change which would allow a =
single
>>>>>> ipsec module to be shared and extended via YANG augmentations?
>>>>>>=20
>>>>>>=20
>>>>>> In the context of our I-D, if we move SAD structure to =
ipsec-common,
>>>>>> what we are meaning is that IPsec SA configuration data (setting
>>>>>> values to the SAD structure) are common to the IKE case and the
>>>>>> IKE-less cases, which are not. It is confusing.
>>>>>>=20
>>>>>> Something defined in a common module but marked as a feature does =
not
>>>>>> imply that that feature has to be implemented by an importing
>>>>>> module. This is not confusing to YANG implementers or users I
>>>>>> think. If we are just talking about document flow here, then a
>>>>>> sentence saying "the SAD feature is not required to implement IKE
>>>>>> functionality" is quite enough to clear that up I think.
>>>>>>=20
>>>>>> Another alternative could be to move these containers to another
>>>>>> (new) module.
>>>>>>=20
>>>>>> It may also be enough to mark the notifications in the ikeless =
module as a feature I suppose. That is the actual thing I think non-SDN =
implementations would want to omit. The module name "ikeless" is not =
great in this case, but perhaps workable.
>>>>>>=20
>>>>>>=20
>>>>>> This is a sub-optimal compromise b/c all IPsec have SA databases =
even ones running IKE -- i.e., SA databases are common whether exposed =
in YANG or not -- but if it can move it forward perhaps good enough.
>>>>>>=20
>>>>>>=20
>>>>>> I'm definitely concerned about IETF process and real world =
usability here. These modules are basically workable for ipsec I think, =
they could be used by operators today. If we restart the entire process =
to redo this work for the more generic IPsec case it will probably be =
years before they are finished and in the field. This new work can be =
started, but why not have something usable in the meantime?
>>>>>>=20
>>>>>> Thanks,
>>>>>> Chris.
>>>>>>=20
>>>>>>=20
>>>>>>=20
>>>>>> /martin
>>>>>>=20
>>>>>>=20
>>>>>>=20
>>>>>>=20
>>>>>>=20
>>>>>> Thanks,
>>>>>> Chris.
>>>>>>=20
>>>>>>=20
>>>>>> Moreover, the usage of feature means that, after all, this =
=E2=80=9Ccommon=E2=80=9D is
>>>>>> not =E2=80=9Ccommon=E2=80=9D to both cases IKE case and IKE-less. =
Again, it seems
>>>>>> confusing. In the IKE case, the SDN/I2NSF controller does not
>>>>>> configure the SAD at all but the IKE implementation in the NSF. =
In our
>>>>>> opinion, in order to properly add this IPsec SA operational state =
to
>>>>>> the IKE case we should include operational data about the IPsec =
SAs
>>>>>> (config false) to the ietf-ipsec-ike. Alternatively, we have =
certain
>>>>>> operational data (ro) in the SAD structure in the IKE-less case. =
If
>>>>>> only those are moved to the common part should be ok but we think =
it
>>>>>> does not solve the problem.
>>>>>>=20
>>>>>>=20
>>>>>> --
>>>>>> last-call mailing list
>>>>>> last-call@ietf.org <mailto:last-call@ietf.org>
>>>>>> https://www.ietf.org/mailman/listinfo/last-call =
<https://www.ietf.org/mailman/listinfo/last-call>
>>>>>>=20
>>>>>>=20
>>>>>>=20
>>>>>> _______________________________________________
>>>>>> IPsec mailing list
>>>>>> IPsec@ietf.org <mailto:IPsec@ietf.org>
>>>>>> https://www.ietf.org/mailman/listinfo/ipsec =
<https://www.ietf.org/mailman/listinfo/ipsec>_____________________________=
__________________
>>>>>> 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:=C2=A0rafa@um.es =
<mailto:rafa@um.es>
>>>>> -------------------------------------------------------
>>>>>=20
>>>>>=20
>>>>>=20
>>>>>=20
>>>>> _______________________________________________
>>>>> IPsec mailing list
>>>>> IPsec@ietf.org <mailto:IPsec@ietf.org>
>>>>> https://www.ietf.org/mailman/listinfo/ipsec =
<https://www.ietf.org/mailman/listinfo/ipsec>
>>>> _______________________________________________
>>>> 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:=C2=A0rafa@um.es =
<mailto:rafa@um.es>
>>> -------------------------------------------------------
>>>=20
>>>=20
>>>=20
>>>=20
>>> _______________________________________________
>>> IPsec mailing list
>>> IPsec@ietf.org <mailto:IPsec@ietf.org>
>>> https://www.ietf.org/mailman/listinfo/ipsec =
<https://www.ietf.org/mailman/listinfo/ipsec>
>> _______________________________________________
>> IPsec mailing list
>> IPsec@ietf.org <mailto:IPsec@ietf.org>
>> https://www.ietf.org/mailman/listinfo/ipsec =
<https://www.ietf.org/mailman/listinfo/ipsec>
> -------------------------------------------------------
> 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:=C2=A0rafa@um.es =
<mailto:rafa@um.es>
> -------------------------------------------------------


--Apple-Mail=_90E89900-8AF2-4D6D-A86C-349952FD86D1
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: after-white-space;" class=3D"">This =
is great news, Thanks!<div class=3D""><br class=3D""></div><div =
class=3D"">IMO (Rob feel free to chime in here :) I don't think you need =
to say anything more about the feature in your document (other than what =
was already mentioned). This is the standard "outside the scope of this =
document" kind of thing. It's enough to put that text that says they are =
marked as a feature for greater re-usability, but SDN clients will =
expect the feature to be implemented.<div class=3D""><br =
class=3D""></div><div class=3D"">FWIW, When talking about YANG features =
I'd use the turn of phrase "to indicate whether notifications are =
implemented by the server" rather than 'to "activate" notifications'. =
They don't get turned on or off, they are either implemented or not. You =
could swap "implemented" with "supported" too here with the same =
meaning.</div><div class=3D""><br class=3D""></div><div =
class=3D"">Thanks,</div><div class=3D"">Chris.<br class=3D""><div><br =
class=3D""><blockquote type=3D"cite" class=3D""><div class=3D"">On Oct =
15, 2020, at 3:12 AM, Rafa Marin-Lopez &lt;<a href=3D"mailto:rafa@um.es" =
class=3D"">rafa@um.es</a>&gt; wrote:</div><br =
class=3D"Apple-interchange-newline"><div class=3D""><span =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
18px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none; float: none; =
display: inline !important;" class=3D"">Hi Christian (,Rob):</span><div =
class=3D"" style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; =
font-size: 18px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none;"><br class=3D""></div><div class=3D"" style=3D"caret-color: rgb(0, =
0, 0); font-family: Helvetica; font-size: 18px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;">Thanks again for this conversation. Please see =
our comments inline.<br class=3D""><div class=3D""><br =
class=3D""><blockquote type=3D"cite" class=3D""><div class=3D""><div =
class=3D"" style=3D"caret-color: rgb(0, 0, 0); font-family: Courier; =
font-size: 16px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none;"><blockquote type=3D"cite" class=3D""><div class=3D""><div =
class=3D"" style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; =
font-size: 18px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none;"><div class=3D""><div class=3D""><br class=3D""></div><div =
class=3D"">As a consequence, the resolution was to move forward with a =
pragmatic approach at this point of time, by changing the names of the =
modules (and prefixes) to refer to the I2NSF =
work.</div></div></div></div></blockquote><div class=3D""><br =
class=3D""></div><div class=3D"">These are 2 different things. The =
original discussion was about moving the SAD and SPD from ikeless module =
to the common one which then would have brought them into the IKE =
module, and required people just implementing IKE to also implement the =
SAD and SPD parts.</div><div class=3D""><br class=3D""></div><div =
class=3D"">In comparison this new compromise request is a tiny change, =
and allows a much larger audience to reap the benefit of your work. The =
change is the addition of "feature ikeless-notification" and then =
putting the "if ikeless-notification" under the =
notifications.</div></div></div></blockquote><blockquote type=3D"cite" =
class=3D""><div class=3D""><div class=3D"" style=3D"caret-color: rgb(0, =
0, 0); font-family: Courier; font-size: 16px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;"><div class=3D""><br class=3D""></div><div =
class=3D"">This doesn't change the semantics of your module it just =
allows people to re-use the ikeless module for supporting SAD and SPD =
w/o implementing the notifications.</div><div class=3D""><br =
class=3D""></div><div class=3D"">If you feel more clarity is needed for =
the SDN use-case then adding the text, "To allow for greater re-use of =
this module, the notifications are marked as a feature. For the SDN use =
case clients will expect this feature to be =
implemented.=E2=80=9D</div></div></div></blockquote><div class=3D""><br =
class=3D""></div><div class=3D""><div class=3D"">We agree that this is a =
small change (if no other change is required). In fact, we have tested =
it and we have not observed any technical problem. The main concern is =
the one I mentioned to Rob: having a feature to =E2=80=9Cactivate=E2=80=9D=
 notifications (or not) in the ikeless module does not fit in the =
context of this I-D, unless we find out a valid use case where this =
feature makes sense.&nbsp;</div><div class=3D""><br class=3D""></div><div =
class=3D"">In other words, it would be really nice if the inclusion of =
the text you proposed (=E2=80=9CTo allow for greater=E2=80=A6=E2=80=9D ) =
had a main text to support how this is useful in the context of this =
I-D. Personally, this would make me feel more =
confortable.&nbsp;</div><div class=3D""><br class=3D""></div></div><div =
class=3D"">Having said all this, let us inform about v09 changes to =
I2NSF wg and ask about this new change in order to see if there is any =
objection. Then, if there is no objection we can prepare v10 very =
quickly with this additional modification.</div><div class=3D""><br =
class=3D""></div><div class=3D"">We hope this is reasonable.</div><div =
class=3D""><br class=3D""></div><div class=3D"">Best =
Regards.</div><blockquote type=3D"cite" class=3D""><div class=3D""><div =
class=3D"" style=3D"caret-color: rgb(0, 0, 0); font-family: Courier; =
font-size: 16px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none;"><br class=3D""></div><div class=3D"" style=3D"caret-color: rgb(0, =
0, 0); font-family: Courier; font-size: 16px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;">Features are reported just as modules are in the =
capabilities. An SDN client would look for both capabilities rather than =
just the one (along with all the other capabilities they will be looking =
for to actually be a functional YANG client).</div><div class=3D"" =
style=3D"caret-color: rgb(0, 0, 0); font-family: Courier; font-size: =
16px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none;"><br =
class=3D""></div><div class=3D"" style=3D"caret-color: rgb(0, 0, 0); =
font-family: Courier; font-size: 16px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;">Thanks,</div><div class=3D"" style=3D"caret-color:=
 rgb(0, 0, 0); font-family: Courier; font-size: 16px; font-style: =
normal; font-variant-caps: normal; font-weight: normal; letter-spacing: =
normal; text-align: start; text-indent: 0px; text-transform: none; =
white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;">Chris.</div><div class=3D"" style=3D"caret-color: =
rgb(0, 0, 0); font-family: Courier; font-size: 16px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;"><br class=3D""><blockquote type=3D"cite" =
class=3D""><div class=3D""><div class=3D"" style=3D"caret-color: rgb(0, =
0, 0); font-family: Helvetica; font-size: 18px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;"><div class=3D""><div class=3D""><br =
class=3D""></div><div class=3D"">Best Regards.</div><br =
class=3D""><blockquote type=3D"cite" class=3D""><div class=3D""><div =
class=3D"" style=3D"caret-color: rgb(0, 0, 0); font-family: Courier; =
font-size: 16px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none;"><div class=3D""><br class=3D""></div><div =
class=3D"">Thanks,</div><div class=3D"">Chris.</div><br =
class=3D""><blockquote type=3D"cite" class=3D""><div class=3D""><div =
class=3D"" style=3D"font-family: Helvetica; font-size: 18px; font-style: =
normal; font-variant-caps: normal; font-weight: normal; letter-spacing: =
normal; text-align: start; text-indent: 0px; text-transform: none; =
white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none; caret-color: rgb(0, 0, 0);"><br =
class=3D""></div><div class=3D"" style=3D"font-family: Helvetica; =
font-size: 18px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none; caret-color: rgb(0, 0, 0);">Hope this helps.</div><div class=3D"" =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
18px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none;"><br =
class=3D""></div><div class=3D"" style=3D"caret-color: rgb(0, 0, 0); =
font-family: Helvetica; font-size: 18px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;">Best Regards.<br class=3D""><div class=3D""><br =
class=3D""><blockquote type=3D"cite" class=3D""><div class=3D"">El 12 =
oct 2020, a las 18:01, Rob Wilton (rwilton) &lt;<a =
href=3D"mailto:rwilton=3D40cisco.com@dmarc.ietf.org" =
class=3D"">rwilton=3D40cisco.com@dmarc.ietf.org</a>&gt; =
escribi=C3=B3:</div><br class=3D"Apple-interchange-newline"><div =
class=3D""><div class=3D"WordSection1" style=3D"page: WordSection1; =
caret-color: rgb(0, 0, 0); font-family: Courier; font-size: 16px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none;"><div class=3D"" =
style=3D"margin: 0cm; font-size: 11pt; font-family: Calibri, =
sans-serif;"><span class=3D"">Hi Rafa, authors,<o:p =
class=3D""></o:p></span></div><div class=3D"" style=3D"margin: 0cm; =
font-size: 11pt; font-family: Calibri, sans-serif;"><span class=3D""><o:p =
class=3D"">&nbsp;</o:p></span></div><div class=3D"" style=3D"margin: =
0cm; font-size: 11pt; font-family: Calibri, sans-serif;"><span =
class=3D"">Just to check.<o:p class=3D""></o:p></span></div><div =
class=3D"" style=3D"margin: 0cm; font-size: 11pt; font-family: Calibri, =
sans-serif;"><span class=3D""><o:p =
class=3D"">&nbsp;</o:p></span></div><div class=3D"" style=3D"margin: =
0cm; font-size: 11pt; font-family: Calibri, sans-serif;"><span =
class=3D"">Has there been any closure on the suggestion from Chris on =
=E2=80=9C</span><span class=3D"">notifications in the ikeless module as =
a feature"?&nbsp; This would seem to be a fairly cheap &amp; easy =
compromise.<o:p class=3D""></o:p></span></div><div class=3D"" =
style=3D"margin: 0cm; font-size: 11pt; font-family: Calibri, =
sans-serif;"><span class=3D""><o:p =
class=3D"">&nbsp;</o:p></span></div><div class=3D"" style=3D"margin: =
0cm; font-size: 11pt; font-family: Calibri, sans-serif;"><span =
class=3D"">Thanks,<br class=3D"">Rob<o:p =
class=3D""></o:p></span></div><div class=3D"" style=3D"margin: 0cm; =
font-size: 11pt; font-family: Calibri, sans-serif;"><span class=3D""><o:p =
class=3D"">&nbsp;</o:p></span></div><div class=3D"" style=3D"margin: =
0cm; font-size: 11pt; font-family: Calibri, sans-serif;"><span =
class=3D""><o:p class=3D"">&nbsp;</o:p></span></div><div class=3D"" =
style=3D"border-style: none none none solid; border-left-width: 1.5pt; =
border-left-color: blue; padding: 0cm 0cm 0cm 4pt;"><div class=3D""><div =
class=3D"" style=3D"border-style: solid none none; border-top-width: =
1pt; border-top-color: rgb(225, 225, 225); padding: 3pt 0cm 0cm;"><div =
class=3D"" style=3D"margin: 0cm; font-size: 11pt; font-family: Calibri, =
sans-serif;"><b class=3D""><span lang=3D"EN-US" =
class=3D"">From:</span></b><span lang=3D"EN-US" class=3D""><span =
class=3D"Apple-converted-space">&nbsp;</span>yang-doctors &lt;<a =
href=3D"mailto:yang-doctors-bounces@ietf.org" =
class=3D"">yang-doctors-bounces@ietf.org</a>&gt;<span =
class=3D"Apple-converted-space">&nbsp;</span><b class=3D"">On Behalf =
Of<span class=3D"Apple-converted-space">&nbsp;</span></b>Lou Berger<br =
class=3D""><b class=3D"">Sent:</b><span =
class=3D"Apple-converted-space">&nbsp;</span>27 September 2020 15:26<br =
class=3D""><b class=3D"">To:</b><span =
class=3D"Apple-converted-space">&nbsp;</span>Christian Hopps &lt;<a =
href=3D"mailto:chopps@chopps.org" class=3D"">chopps@chopps.org</a>&gt;; =
Martin Bj=C3=B6rklund &lt;<a href=3D"mailto:mbj+ietf@4668.se" =
class=3D"">mbj+ietf@4668.se</a>&gt;<br class=3D""><b =
class=3D"">Cc:</b><span =
class=3D"Apple-converted-space">&nbsp;</span>Robert Wilton &lt;<a =
href=3D"mailto:rwilton=3D40cisco.com@dmarc.ietf.org" =
class=3D"">rwilton=3D40cisco.com@dmarc.ietf.org</a>&gt;;<span =
class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"mailto:i2nsf@ietf.org" class=3D"">i2nsf@ietf.org</a>; Gabriel =
Lopez &lt;<a href=3D"mailto:gabilm@um.es" =
class=3D"">gabilm@um.es</a>&gt;;<span =
class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"mailto:draft-ietf-i2nsf-sdn-ipsec-flow-protection.all@ietf.org" =
class=3D"">draft-ietf-i2nsf-sdn-ipsec-flow-protection.all@ietf.org</a>;<sp=
an class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"mailto:ipsec@ietf.org" class=3D"">ipsec@ietf.org</a>;<span =
class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"mailto:last-call@ietf.org" class=3D"">last-call@ietf.org</a>; =
Rafa Marin-Lopez &lt;<a href=3D"mailto:rafa@um.es" =
class=3D"">rafa@um.es</a>&gt;;<span =
class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"mailto:yang-doctors@ietf.org" =
class=3D"">yang-doctors@ietf.org</a><br class=3D""><b =
class=3D"">Subject:</b><span =
class=3D"Apple-converted-space">&nbsp;</span>Re: [yang-doctors] [IPsec] =
[Last-Call] [I2nsf] Yangdoctors last call review of =
draft-ietf-i2nsf-sdn-ipsec-flow-protection-08<o:p =
class=3D""></o:p></span></div></div></div><div class=3D"" style=3D"margin:=
 0cm; font-size: 11pt; font-family: Calibri, sans-serif;"><o:p =
class=3D"">&nbsp;</o:p></div><blockquote class=3D"" style=3D"margin-top: =
5pt; margin-bottom: 5pt;"><div class=3D""><div class=3D"" style=3D"margin:=
 0cm; font-size: 11pt; font-family: Calibri, sans-serif;">This is a =
sub-optimal compromise b/c all IPsec have SA databases even ones running =
IKE -- i.e., SA databases are common whether exposed in YANG or not -- =
but if it can move it forward perhaps good enough.<o:p =
class=3D""></o:p></div></div><div class=3D""><div class=3D"" =
style=3D"margin: 0cm; font-size: 11pt; font-family: Calibri, =
sans-serif;"><br class=3D""><br class=3D""><o:p =
class=3D""></o:p></div></div></blockquote><div class=3D"" style=3D"margin:=
 0cm; font-size: 11pt; font-family: Calibri, sans-serif;">Speaking as an =
interested party, I hope that some compromise / good enough solution is =
followed in the -09 version of&nbsp; this draft.<o:p =
class=3D""></o:p></div><p class=3D"">Lou<o:p class=3D""></o:p></p><div =
class=3D""><div class=3D"" style=3D"margin: 0cm; font-size: 11pt; =
font-family: Calibri, sans-serif;">On 9/23/2020 7:20 AM, Christian Hopps =
wrote:<o:p class=3D""></o:p></div></div><blockquote class=3D"" =
style=3D"margin-top: 5pt; margin-bottom: 5pt;"><div class=3D"" =
style=3D"margin: 0cm; font-size: 11pt; font-family: Calibri, =
sans-serif;"><o:p class=3D"">&nbsp;</o:p></div><div class=3D""><div =
class=3D"" style=3D"margin: 0cm; font-size: 11pt; font-family: Calibri, =
sans-serif;"><br class=3D""><br class=3D""><o:p =
class=3D""></o:p></div><blockquote class=3D"" style=3D"margin-top: 5pt; =
margin-bottom: 5pt;"><div class=3D""><div class=3D"" style=3D"margin: =
0cm; font-size: 11pt; font-family: Calibri, sans-serif;">On Sep 23, =
2020, at 6:58 AM, Martin Bj=C3=B6rklund &lt;<a =
href=3D"mailto:mbj+ietf@4668.se" class=3D"" style=3D"color: blue; =
text-decoration: underline;">mbj+ietf@4668.se</a>&gt; wrote:<o:p =
class=3D""></o:p></div></div><div class=3D"" style=3D"margin: 0cm; =
font-size: 11pt; font-family: Calibri, sans-serif;"><o:p =
class=3D"">&nbsp;</o:p></div><div class=3D""><div class=3D"" =
style=3D"margin: 0cm; font-size: 11pt; font-family: Calibri, =
sans-serif;"><span class=3D"" style=3D"font-size: 10.5pt; font-family: =
Menlo-Regular, serif;">Hi,<br class=3D""><br class=3D"">Christian Hopps =
&lt;</span><a href=3D"mailto:chopps@chopps.org" class=3D"" style=3D"color:=
 blue; text-decoration: underline;"><span class=3D"" style=3D"font-size: =
10.5pt; font-family: Menlo-Regular, =
serif;">chopps@chopps.org</span></a><span class=3D"" style=3D"font-size: =
10.5pt; font-family: Menlo-Regular, serif;">&gt; wrote:<br class=3D"" =
style=3D"caret-color: rgb(0, 0, 0); font-variant-caps: normal; =
text-align: start; -webkit-text-stroke-width: 0px; word-spacing: =
0px;"><br class=3D""></span><o:p class=3D""></o:p></div><blockquote =
class=3D"" style=3D"margin-top: 5pt; margin-bottom: 5pt;"><div class=3D"" =
style=3D"margin: 0cm; font-size: 11pt; font-family: Calibri, =
sans-serif;"><span class=3D"" style=3D"font-size: 10.5pt; font-family: =
Menlo-Regular, serif;"><br class=3D""><br class=3D""><br class=3D""><o:p =
class=3D""></o:p></span></div><blockquote class=3D"" style=3D"margin-top: =
5pt; margin-bottom: 5pt;"><div class=3D"" style=3D"margin: 0cm; =
font-size: 11pt; font-family: Calibri, sans-serif;"><span class=3D"" =
style=3D"font-size: 10.5pt; font-family: Menlo-Regular, serif;">On Sep =
23, 2020, at 5:29 AM, Rafa Marin-Lopez &lt;<a href=3D"mailto:rafa@um.es" =
class=3D"" style=3D"color: blue; text-decoration: =
underline;">rafa@um.es</a>&gt; wrote:<br class=3D""><br class=3D""><br =
class=3D""><o:p class=3D""></o:p></span></div><blockquote class=3D"" =
style=3D"margin-top: 5pt; margin-bottom: 5pt;"><div class=3D"" =
style=3D"margin: 0cm; font-size: 11pt; font-family: Calibri, =
sans-serif;"><span class=3D"" style=3D"font-size: 10.5pt; font-family: =
Menlo-Regular, serif;"><br class=3D""><br class=3D"">But I would like to =
check: My understanding is that the changes that<br class=3D"">Chris is =
proposing are pretty small. &nbsp;I.e. move the SA structure under<br =
class=3D"">ipsec-common, and put it under a YANG feature. &nbsp;Are you =
sure that it<br class=3D"">is impractical to accommodate this change =
which would allow a single<br class=3D"">ipsec module to be shared and =
extended via YANG augmentations?<o:p =
class=3D""></o:p></span></div></blockquote><div class=3D"" =
style=3D"margin: 0cm; font-size: 11pt; font-family: Calibri, =
sans-serif;"><span class=3D"" style=3D"font-size: 10.5pt; font-family: =
Menlo-Regular, serif;"><br class=3D""><br class=3D"">In the context of =
our I-D, if we move SAD structure to ipsec-common,<br class=3D"">what we =
are meaning is that IPsec SA configuration data (setting<br =
class=3D"">values to the SAD structure) are common to the IKE case and =
the<br class=3D"">IKE-less cases, which are not. It is confusing.<o:p =
class=3D""></o:p></span></div></blockquote><div class=3D"" =
style=3D"margin: 0cm; font-size: 11pt; font-family: Calibri, =
sans-serif;"><span class=3D"" style=3D"font-size: 10.5pt; font-family: =
Menlo-Regular, serif;"><br class=3D"">Something defined in a common =
module but marked as a feature does not<br class=3D"">imply that that =
feature has to be implemented by an importing<br class=3D"">module. This =
is not confusing to YANG implementers or users I<br class=3D"">think. If =
we are just talking about document flow here, then a<br =
class=3D"">sentence saying "the SAD feature is not required to implement =
IKE<br class=3D"">functionality" is quite enough to clear that up I =
think.<o:p class=3D""></o:p></span></div></blockquote><div class=3D"" =
style=3D"margin: 0cm; font-size: 11pt; font-family: Calibri, =
sans-serif;"><span class=3D"" style=3D"font-size: 10.5pt; font-family: =
Menlo-Regular, serif;"><br class=3D"">Another alternative could be to =
move these containers to another<br class=3D"">(new) module.</span><o:p =
class=3D""></o:p></div></div></blockquote><div class=3D""><div class=3D"" =
style=3D"margin: 0cm; font-size: 11pt; font-family: Calibri, =
sans-serif;"><o:p class=3D"">&nbsp;</o:p></div></div><div class=3D"" =
style=3D"margin: 0cm; font-size: 11pt; font-family: Calibri, =
sans-serif;"><span class=3D"">It may also be enough to mark the =
notifications in the ikeless module as a feature I suppose. That is the =
actual thing I think non-SDN implementations would want to omit. The =
module name "ikeless" is not great in this case, but perhaps =
workable.</span><o:p class=3D""></o:p></div></div><div class=3D""><div =
class=3D"" style=3D"margin: 0cm; font-size: 11pt; font-family: Calibri, =
sans-serif;"><span class=3D""><br class=3D""><br class=3D""></span><o:p =
class=3D""></o:p></div></div><div class=3D""><div class=3D"" =
style=3D"margin: 0cm; font-size: 11pt; font-family: Calibri, =
sans-serif;"><span class=3D"">This is a sub-optimal compromise b/c all =
IPsec have SA databases even ones running IKE -- i.e., SA databases are =
common whether exposed in YANG or not -- but if it can move it forward =
perhaps good enough.</span><o:p class=3D""></o:p></div></div><div =
class=3D""><div class=3D"" style=3D"margin: 0cm; font-size: 11pt; =
font-family: Calibri, sans-serif;"><span class=3D""><br class=3D""><br =
class=3D""></span><o:p class=3D""></o:p></div></div><div class=3D""><div =
class=3D"" style=3D"margin: 0cm; font-size: 11pt; font-family: Calibri, =
sans-serif;"><span class=3D"">I'm definitely concerned about IETF =
process and real world usability here. These modules are basically =
workable for ipsec I think, they could be used by operators today. If we =
restart the entire process to redo this work for the more generic IPsec =
case it will probably be years before they are finished and in the =
field. This new work can be started, but why not have something usable =
in the meantime?</span><o:p class=3D""></o:p></div></div><div =
class=3D""><div class=3D"" style=3D"margin: 0cm; font-size: 11pt; =
font-family: Calibri, sans-serif;"><o:p =
class=3D"">&nbsp;</o:p></div></div><div class=3D""><div class=3D"" =
style=3D"margin: 0cm; font-size: 11pt; font-family: Calibri, =
sans-serif;">Thanks,<o:p class=3D""></o:p></div></div><div class=3D""><div=
 class=3D"" style=3D"margin: 0cm; font-size: 11pt; font-family: Calibri, =
sans-serif;">Chris.<o:p class=3D""></o:p></div></div><div class=3D""><div =
class=3D"" style=3D"margin: 0cm; font-size: 11pt; font-family: Calibri, =
sans-serif;"><o:p class=3D"">&nbsp;</o:p></div></div><div =
class=3D""><blockquote class=3D"" style=3D"margin-top: 5pt; =
margin-bottom: 5pt;"><div class=3D""><div class=3D"" style=3D"margin: =
0cm; font-size: 11pt; font-family: Calibri, sans-serif;"><span class=3D"" =
style=3D"font-size: 10.5pt; font-family: Menlo-Regular, serif;"><br =
class=3D""><br class=3D"">/martin<br class=3D""><br class=3D""><br =
class=3D""><br class=3D"" style=3D"caret-color: rgb(0, 0, 0); =
font-variant-caps: normal; text-align: start; -webkit-text-stroke-width: =
0px; word-spacing: 0px;"><br class=3D""></span><o:p =
class=3D""></o:p></div><blockquote class=3D"" style=3D"margin-top: 5pt; =
margin-bottom: 5pt;"><div class=3D"" style=3D"margin: 0cm; font-size: =
11pt; font-family: Calibri, sans-serif;"><span class=3D"" =
style=3D"font-size: 10.5pt; font-family: Menlo-Regular, serif;"><br =
class=3D"">Thanks,<br class=3D"">Chris.<br class=3D""><br class=3D""><br =
class=3D""><o:p class=3D""></o:p></span></div><blockquote class=3D"" =
style=3D"margin-top: 5pt; margin-bottom: 5pt;"><p class=3D"MsoNormal" =
style=3D"margin: 0cm 0cm 12pt; font-size: 11pt; font-family: Calibri, =
sans-serif;"><span class=3D"" style=3D"font-size: 10.5pt; font-family: =
Menlo-Regular, serif;">Moreover, the usage of feature means that, after =
all, this =E2=80=9Ccommon=E2=80=9D is<br class=3D"">not =E2=80=9Ccommon=E2=
=80=9D to both cases IKE case and IKE-less. Again, it seems<br =
class=3D"">confusing. In the IKE case, the SDN/I2NSF controller does =
not<br class=3D"">configure the SAD at all but the IKE implementation in =
the NSF. In our<br class=3D"">opinion, in order to properly add this =
IPsec SA operational state to<br class=3D"">the IKE case we should =
include operational data about the IPsec SAs<br class=3D"">(config =
false) to the ietf-ipsec-ike. Alternatively, we have certain<br =
class=3D"">operational data (ro) in the SAD structure in the IKE-less =
case. If<br class=3D"">only those are moved to the common part should be =
ok but we think it<br class=3D"">does not solve the problem.<o:p =
class=3D""></o:p></span></p></blockquote><div class=3D"" style=3D"margin: =
0cm; font-size: 11pt; font-family: Calibri, sans-serif;"><span class=3D"" =
style=3D"font-size: 10.5pt; font-family: Menlo-Regular, serif;"><o:p =
class=3D"">&nbsp;</o:p></span></div></blockquote><div class=3D"" =
style=3D"margin: 0cm; font-size: 11pt; font-family: Calibri, =
sans-serif;"><span class=3D"" style=3D"font-size: 10.5pt; font-family: =
Menlo-Regular, serif;">--<span =
class=3D"apple-converted-space">&nbsp;</span><br class=3D"">last-call =
mailing list<br class=3D""></span><a href=3D"mailto:last-call@ietf.org" =
class=3D"" style=3D"color: blue; text-decoration: underline;"><span =
class=3D"" style=3D"font-size: 10.5pt; font-family: Menlo-Regular, =
serif;">last-call@ietf.org</span></a><span class=3D"" style=3D"font-size: =
10.5pt; font-family: Menlo-Regular, serif;"><br class=3D""></span><a =
href=3D"https://www.ietf.org/mailman/listinfo/last-call" class=3D"" =
style=3D"color: blue; text-decoration: underline;"><span class=3D"" =
style=3D"font-size: 10.5pt; font-family: Menlo-Regular, =
serif;">https://www.ietf.org/mailman/listinfo/last-call</span></a><o:p =
class=3D""></o:p></div></div></blockquote></div><div class=3D"" =
style=3D"margin: 0cm; font-size: 11pt; font-family: Calibri, =
sans-serif;"><br class=3D""><br class=3D""><br class=3D""><o:p =
class=3D""></o:p></div><pre class=3D"" style=3D"margin: 0cm; font-size: =
10pt; font-family: &quot;Courier =
New&quot;;">_______________________________________________<o:p =
class=3D""></o:p></pre><pre class=3D"" style=3D"margin: 0cm; font-size: =
10pt; font-family: &quot;Courier New&quot;;">IPsec mailing list<o:p =
class=3D""></o:p></pre><pre class=3D"" style=3D"margin: 0cm; font-size: =
10pt; font-family: &quot;Courier New&quot;;"><a =
href=3D"mailto:IPsec@ietf.org" class=3D"" style=3D"color: blue; =
text-decoration: underline;">IPsec@ietf.org</a><o:p =
class=3D""></o:p></pre><pre class=3D"" style=3D"margin: 0cm; font-size: =
10pt; font-family: &quot;Courier New&quot;;"><a =
href=3D"https://www.ietf.org/mailman/listinfo/ipsec" class=3D"" =
style=3D"color: blue; text-decoration: =
underline;">https://www.ietf.org/mailman/listinfo/ipsec</a><o:p =
class=3D""></o:p></pre></blockquote></div></div><span class=3D"" =
style=3D"caret-color: rgb(0, 0, 0); font-family: Courier; font-size: =
16px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none; float: none; =
display: inline =
!important;">_______________________________________________</span><br =
class=3D"" style=3D"caret-color: rgb(0, 0, 0); font-family: Courier; =
font-size: 16px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none;"><span class=3D"" style=3D"caret-color: rgb(0, 0, 0); font-family: =
Courier; font-size: 16px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none; float: none; display: inline !important;">I2nsf mailing =
list</span><br class=3D"" style=3D"caret-color: rgb(0, 0, 0); =
font-family: Courier; font-size: 16px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;"><span class=3D"" style=3D"caret-color: rgb(0, 0, =
0); font-family: Courier; font-size: 16px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none; float: none; display: inline !important;"><a =
href=3D"mailto:I2nsf@ietf.org" class=3D"">I2nsf@ietf.org</a></span><br =
class=3D"" style=3D"caret-color: rgb(0, 0, 0); font-family: Courier; =
font-size: 16px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none;"><span class=3D"" style=3D"caret-color: rgb(0, 0, 0); font-family: =
Courier; font-size: 16px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none; float: none; display: inline !important;"><a =
href=3D"https://www.ietf.org/mailman/listinfo/i2nsf" =
class=3D"">https://www.ietf.org/mailman/listinfo/i2nsf</a></span></div></b=
lockquote></div><br class=3D""><div class=3D""><div class=3D"" =
style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; line-break: =
after-white-space;"><div class=3D"" style=3D"font-family: Courier; =
font-size: 16px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: =
0px;">-------------------------------------------------------<br =
class=3D"">Rafa Marin-Lopez, PhD<br class=3D"">Dept. Information =
and&nbsp;Communications&nbsp;Engineering (DIIC)<br class=3D"">Faculty of =
Computer&nbsp;Science-University of&nbsp;Murcia<br class=3D"">30100 =
Murcia - Spain<br class=3D"">Telf: +34868888501 =
Fax:&nbsp;+34868884151<span =
class=3D"Apple-converted-space">&nbsp;</span><a href=3D"mailto:rafa@um.es"=
 class=3D"">e-mail:&nbsp;rafa@um.es</a><br =
class=3D"">-------------------------------------------------------</div><d=
iv class=3D"" style=3D"font-family: Courier; font-size: 16px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px;"><br class=3D""></div><br =
class=3D"Apple-interchange-newline"></div><br =
class=3D"Apple-interchange-newline"></div><br class=3D""></div><span =
class=3D"" style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; =
font-size: 18px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none; float: none; display: inline =
!important;">_______________________________________________</span><br =
class=3D"" style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; =
font-size: 18px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none;"><span class=3D"" style=3D"caret-color: rgb(0, 0, 0); font-family: =
Helvetica; font-size: 18px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none; float: none; display: inline !important;">IPsec mailing =
list</span><br class=3D"" style=3D"caret-color: rgb(0, 0, 0); =
font-family: Helvetica; font-size: 18px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;"><a href=3D"mailto:IPsec@ietf.org" class=3D"" =
style=3D"font-family: Helvetica; font-size: 18px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: =
0px;">IPsec@ietf.org</a><br class=3D"" style=3D"caret-color: rgb(0, 0, =
0); font-family: Helvetica; font-size: 18px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;"><a =
href=3D"https://www.ietf.org/mailman/listinfo/ipsec" class=3D"" =
style=3D"font-family: Helvetica; font-size: 18px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: =
0px;">https://www.ietf.org/mailman/listinfo/ipsec</a></div></blockquote></=
div><br class=3D"" style=3D"caret-color: rgb(0, 0, 0); font-family: =
Courier; font-size: 16px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none;"><span class=3D"" style=3D"caret-color: rgb(0, 0, 0); font-family: =
Courier; font-size: 16px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none; float: none; display: inline =
!important;">_______________________________________________</span><br =
class=3D"" style=3D"caret-color: rgb(0, 0, 0); font-family: Courier; =
font-size: 16px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none;"><span class=3D"" style=3D"caret-color: rgb(0, 0, 0); font-family: =
Courier; font-size: 16px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none; float: none; display: inline !important;">I2nsf mailing =
list</span><br class=3D"" style=3D"caret-color: rgb(0, 0, 0); =
font-family: Courier; font-size: 16px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;"><a href=3D"mailto:I2nsf@ietf.org" class=3D"" =
style=3D"font-family: Courier; font-size: 16px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: =
0px;">I2nsf@ietf.org</a><br class=3D"" style=3D"caret-color: rgb(0, 0, =
0); font-family: Courier; font-size: 16px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;"><a =
href=3D"https://www.ietf.org/mailman/listinfo/i2nsf" class=3D"" =
style=3D"font-family: Courier; font-size: 16px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: =
0px;">https://www.ietf.org/mailman/listinfo/i2nsf</a></div></blockquote></=
div><br class=3D""><div class=3D""><div class=3D"" style=3D"word-wrap: =
break-word; -webkit-nbsp-mode: space; line-break: =
after-white-space;"><div class=3D"" style=3D"font-family: Courier; =
font-size: 16px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: =
0px;">-------------------------------------------------------<br =
class=3D"">Rafa Marin-Lopez, PhD<br class=3D"">Dept. Information =
and&nbsp;Communications&nbsp;Engineering (DIIC)<br class=3D"">Faculty of =
Computer&nbsp;Science-University of&nbsp;Murcia<br class=3D"">30100 =
Murcia - Spain<br class=3D"">Telf: +34868888501 =
Fax:&nbsp;+34868884151<span =
class=3D"Apple-converted-space">&nbsp;</span><a href=3D"mailto:rafa@um.es"=
 class=3D"">e-mail:&nbsp;rafa@um.es</a><br =
class=3D"">-------------------------------------------------------</div><d=
iv class=3D"" style=3D"font-family: Courier; font-size: 16px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px;"><br class=3D""></div><br =
class=3D"Apple-interchange-newline"></div><br =
class=3D"Apple-interchange-newline"></div><br class=3D""></div><span =
class=3D"" style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; =
font-size: 18px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none; float: none; display: inline =
!important;">_______________________________________________</span><br =
class=3D"" style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; =
font-size: 18px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none;"><span class=3D"" style=3D"caret-color: rgb(0, 0, 0); font-family: =
Helvetica; font-size: 18px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none; float: none; display: inline !important;">IPsec mailing =
list</span><br class=3D"" style=3D"caret-color: rgb(0, 0, 0); =
font-family: Helvetica; font-size: 18px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;"><a href=3D"mailto:IPsec@ietf.org" class=3D"" =
style=3D"font-family: Helvetica; font-size: 18px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: =
0px;">IPsec@ietf.org</a><br class=3D"" style=3D"caret-color: rgb(0, 0, =
0); font-family: Helvetica; font-size: 18px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;"><a =
href=3D"https://www.ietf.org/mailman/listinfo/ipsec" class=3D"" =
style=3D"font-family: Helvetica; font-size: 18px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: =
0px;">https://www.ietf.org/mailman/listinfo/ipsec</a></div></blockquote></=
div><br class=3D"" style=3D"caret-color: rgb(0, 0, 0); font-family: =
Courier; font-size: 16px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none;"><span class=3D"" style=3D"caret-color: rgb(0, 0, 0); font-family: =
Courier; font-size: 16px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none; float: none; display: inline =
!important;">_______________________________________________</span><br =
class=3D"" style=3D"caret-color: rgb(0, 0, 0); font-family: Courier; =
font-size: 16px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none;"><span class=3D"" style=3D"caret-color: rgb(0, 0, 0); font-family: =
Courier; font-size: 16px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none; float: none; display: inline !important;">IPsec mailing =
list</span><br class=3D"" style=3D"caret-color: rgb(0, 0, 0); =
font-family: Courier; font-size: 16px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;"><a href=3D"mailto:IPsec@ietf.org" class=3D"" =
style=3D"font-family: Courier; font-size: 16px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: =
0px;">IPsec@ietf.org</a><br class=3D"" style=3D"caret-color: rgb(0, 0, =
0); font-family: Courier; font-size: 16px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;"><a =
href=3D"https://www.ietf.org/mailman/listinfo/ipsec" class=3D"" =
style=3D"font-family: Courier; font-size: 16px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: =
0px;">https://www.ietf.org/mailman/listinfo/ipsec</a></div></blockquote></=
div><br class=3D""><div class=3D""><div class=3D"" style=3D"word-wrap: =
break-word; -webkit-nbsp-mode: space; line-break: =
after-white-space;"><div style=3D"font-family: Courier; font-size: 16px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px;" =
class=3D"">-------------------------------------------------------<br =
class=3D"">Rafa Marin-Lopez, PhD<br class=3D"">Dept. Information =
and&nbsp;Communications&nbsp;Engineering (DIIC)<br class=3D"">Faculty of =
Computer&nbsp;Science-University of&nbsp;Murcia<br class=3D"">30100 =
Murcia - Spain<br class=3D"">Telf: +34868888501 =
Fax:&nbsp;+34868884151<span =
class=3D"Apple-converted-space">&nbsp;</span><a href=3D"mailto:rafa@um.es"=
 class=3D"">e-mail:&nbsp;rafa@um.es</a><br =
class=3D"">-------------------------------------------------------</div></=
div></div></div></div></blockquote></div><br =
class=3D""></div></div></body></html>=

--Apple-Mail=_90E89900-8AF2-4D6D-A86C-349952FD86D1--

--Apple-Mail=_71DD0E65-CAB8-4BA2-A065-0E5B1AC62BF0
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEm56yH/NF+m1FHa6lLh2DDte4MCUFAl+IKPoACgkQLh2DDte4
MCUR6w//V4PS6XwYL/4I23q5Fx7hiUrwZ6LM6nSNixSQk43znrF2PjS1/14ChyhD
PsevSjG+TPyeOPItJOX0XuXebTkaUYKpXJlKwailJS5+5wuQjHBSQfgajHJsVqb0
kJARqaIeUN2/Q3kggUFcNGnQ/7jX0BoGYZPCul0ZYlt2qpLwYpzb6TA/yUlT927s
V1Cmb3LTYx5maBkCL08gH6ZPkfIRKL0Bp9fBMW5qXJ2Kjnms0Y96enmzlfygrhQ3
LGxBsWYywiqSCAucGDYyk/92MIRenSEBCtNkc0lUP1G/A1H0bID9y0PDetsNaCI8
0vsIxyhknr9JqNYlkj/82s5UHUaFFQM4lfRGPQLQCHC8acSn4HbHL023gthI9bN5
BeJH0wlTX87v6LsIOub7FjlhA7AS55CfmnFbmZQJbBVGdooI6wBaMHaT0koDpEcq
z8ATxLmG7wVzJkhSQIaNrDqDdHkCLlPqtGexJW4eA2Y3X4TXZysYm81sKNbsoXhw
l2Uu/Xcy/MhWEMUaDLkQQCvz87k20VMOf474c25v+TDJTztePgAcsZ5CtmLFM1tp
ZpsBTGo7l3QkPTGLGgG9XWXjXJB+8enjwgnWL/uXze4jWE0KoL1++3rMbnyLLj5Z
emJTxic2l/rBOH5jghS6H7+thNltE6AyYuY8hUvD2R9XvbWJ5Iw=
=Tt+h
-----END PGP SIGNATURE-----

--Apple-Mail=_71DD0E65-CAB8-4BA2-A065-0E5B1AC62BF0--


From nobody Fri Oct 16 01:20:08 2020
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 A10D63A0DEF; Fri, 16 Oct 2020 01:19:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.096
X-Spam-Level: 
X-Spam-Status: No, score=-2.096 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, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, 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=um.es
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 TUr1DF2iDyfV; Fri, 16 Oct 2020 01:19:56 -0700 (PDT)
Received: from mx02.puc.rediris.es (outbound4sev.lav.puc.rediris.es [130.206.19.177]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1F3203A0DDA; Fri, 16 Oct 2020 01:19:55 -0700 (PDT)
Received: from xenon41.um.es (xenon41.um.es [155.54.212.167]) by mx02.puc.rediris.es  with ESMTP id 09G8Jrii027967-09G8Jrij027967; Fri, 16 Oct 2020 10:19:53 +0200
Received: from localhost (localhost [127.0.0.1]) by xenon41.um.es (Postfix) with ESMTP id E0F5420040; Fri, 16 Oct 2020 10:19:53 +0200 (CEST)
X-Virus-Scanned: by antispam in UMU at xenon41.um.es
Received: from xenon41.um.es ([127.0.0.1]) by localhost (xenon41.um.es [127.0.0.1]) (amavisd-new, port 10024) with LMTP id U5ZseB_1jcLm; Fri, 16 Oct 2020 10:19:53 +0200 (CEST)
Received: from [192.168.1.33] (135.red-79-150-250.dynamicip.rima-tde.net [79.150.250.135]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: rafa@um.es) by xenon41.um.es (Postfix) with ESMTPSA id 0E0631FF41; Fri, 16 Oct 2020 10:19:51 +0200 (CEST)
From: Rafa Marin-Lopez <rafa@um.es>
Message-Id: <D9E7F4D7-E6EC-4268-B989-F764CEE34B2B@um.es>
Content-Type: multipart/alternative; boundary="Apple-Mail=_70C4207B-C17E-40FE-A432-F907BCC6A079"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.14\))
Date: Fri, 16 Oct 2020 10:19:50 +0200
In-Reply-To: <160252655236.514.5675626677635075934@ietfa.amsl.com>
Cc: Rafa Marin-Lopez <rafa@um.es>, ipsec@ietf.org, yang-doctors@ietf.org, last-call@ietf.org, draft-ietf-i2nsf-sdn-ipsec-flow-protection.all@ietf.org
To: i2nsf@ietf.org
References: <160252655236.514.5675626677635075934@ietfa.amsl.com>
X-Mailer: Apple Mail (2.3445.104.14)
X-FEAS-SPF: spf-result=pass, ip=155.54.212.167, helo=xenon41.um.es, mailFrom=rafa@um.es
Authentication-Results: mx02.puc.rediris.es; spf=pass (rediris.es: domain of rafa@um.es designates 155.54.212.167 as permitted sender) smtp.mailfrom=rafa@um.es
X-FE-Policy-ID: 2:15:0: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=bEQuieDtiSROx5aMushaXJBL+yWOJV/k9x4j8cKPLiw=; b=w8xJ6ULp9a/hXZByfS4nnohMv1+VAiBIQ4GnihikOOyEQL7mq4VkrrMw9CWw9Ur19YcWEOZg2Y6H ufAD6VvOD1V3+PhI2jRlpz8aQvrySuNF89wj8dHRoYMMXyXtIJvVePvtfXOknldJ2Ys8ld9fWh4b xFNQk+ZYo2ZgwNJaL8coU7Pl8uU5P2+FO4YocfFk+n7+9m/WpPgWJkDRsaExExEpqvN6+IPzADUW PIrFMn605Tyi9V16Z2SOzbRIpSApRBwXPbOcIbNWQFD9iBZNTHPEv+F4jw/gRr9jGvA+4vrNB2AH vrA2buIKQInnKwqaZfaKzaOCzatdugenDV/Zow==
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2nsf/3uTO-p-ekaexdmdAVAQXqpK4y7s>
Subject: Re: [I2nsf] New Version Notification for draft-ietf-i2nsf-sdn-ipsec-flow-protection-09.txt
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: Fri, 16 Oct 2020 08:20:03 -0000

--Apple-Mail=_70C4207B-C17E-40FE-A432-F907BCC6A079
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Dear all:

Recently we submitted v09. We would like to summarize the status:

- We have applied all the comments we received so far (except one, see =
below). In particular, we would like to highlight that we have renamed =
the modules as a consequence of some comments. In particular:

ietf-ipsec-common =E2=80=94> ietf-i2nsf-ikec
ietf-ipsec-ike =E2=80=94> ietf-i2nsf-ike
ietf-ipsec-ikeless -> ietf-i2nsf-ikeless

- Moreover we made a minor change. We realized that encryption =
algorithms should also have a key-length. For example, it is not enough =
to say the algorithm is AES-CBC without specifying the key-length (e.g. =
128 bits).=20

- Regarding the pending comment, as you may have followed in the mailing =
list, it has been proposed to add a feature ikeless-notification and the =
corresponding if ikeless-notification in each notification to indicate =
whether notifications are implemented by the NSF. The goal here is to =
ensure broader applicability of the ikeless module. If there is no =
objection, we can include this feature adding a description about the =
motivation behind this and prepare v10 very quickly.

"To ensure broader applicability of this module, the notifications are =
marked as a feature. For the implementation of ikeless case, the NSF is =
expected to implement this feature.";

The result would be (in tree format):

notifications:
    +---n sadb-acquire {ikeless-notification}?
    |  +--ro ipsec-policy-name    string
    |  +--ro traffic-selector
    |     +--ro local-subnet      inet:ip-prefix
    |     +--ro remote-subnet     inet:ip-prefix
    |     +--ro inner-protocol?   ipsec-inner-protocol
    |     +--ro local-ports* [start end]
    |     |  +--ro start    inet:port-number
    |     |  +--ro end      inet:port-number
    |     +--ro remote-ports* [start end]
    |        +--ro start    inet:port-number
    |        +--ro end      inet:port-number
    +---n sadb-expire {ikeless-notification}?
    |  +--ro ipsec-sa-name           string
    |  +--ro soft-lifetime-expire?   boolean
    |  +--ro lifetime-current
    |     +--ro time?      uint32
    |     +--ro bytes?     uint32
    |     +--ro packets?   uint32
    |     +--ro idle?      uint32
    +---n sadb-seq-overflow {ikeless-notification}?
    |  +--ro ipsec-sa-name    string
    +---n sadb-bad-spi {ikeless-notification}?
       +--ro spi    uint32


Best Regards. =20

> El 12 oct 2020, a las 20:15, internet-drafts@ietf.org escribi=C3=B3:
>=20
>=20
> A new version of I-D, =
draft-ietf-i2nsf-sdn-ipsec-flow-protection-09.txt
> has been successfully submitted by Rafa Marin-Lopez and posted to the
> IETF repository.
>=20
> Name:		draft-ietf-i2nsf-sdn-ipsec-flow-protection
> Revision:	09
> Title:		Software-Defined Networking (SDN)-based IPsec =
Flow Protection
> Document date:	2020-10-12
> Group:		i2nsf
> Pages:		92
> URL:            =
https://www.ietf.org/archive/id/draft-ietf-i2nsf-sdn-ipsec-flow-protection=
-09.txt
> Status:         =
https://datatracker.ietf.org/doc/draft-ietf-i2nsf-sdn-ipsec-flow-protectio=
n/
> Htmlized:       =
https://datatracker.ietf.org/doc/html/draft-ietf-i2nsf-sdn-ipsec-flow-prot=
ection
> Htmlized:       =
https://tools.ietf.org/html/draft-ietf-i2nsf-sdn-ipsec-flow-protection-09
> Diff:           =
https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-i2nsf-sdn-ipsec-flow-protec=
tion-09
>=20
> Abstract:
>   This document describes how to provide IPsec-based flow protection
>   (integrity and confidentiality) by means of an Interface to Network
>   Security Function (I2NSF) controller.  It considers two main well-
>   known scenarios in IPsec: (i) gateway-to-gateway and (ii) host-to-
>   host.  The service described in this document allows the
>   configuration and monitoring of IPsec Security Associations (SAs)
>   from a I2NSF Controller to one or several flow-based Network =
Security
>   Functions (NSFs) that rely on IPsec to protect data traffic.
>=20
>   The document focuses on the I2NSF NSF-facing interface by providing
>   YANG data models for configuring the IPsec databases (SPD, SAD, PAD)
>   and IKEv2.  This allows IPsec SA establishment with minimal
>   intervention by the network administrator.  It does not define any
>   new protocol.
>=20
>=20
>=20
>=20
> Please note that it may take a couple of minutes from the time of =
submission
> until the htmlized version and diff are available at tools.ietf.org.
>=20
> The IETF Secretariat
>=20
>=20

-------------------------------------------------------
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
-------------------------------------------------------





--Apple-Mail=_70C4207B-C17E-40FE-A432-F907BCC6A079
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: after-white-space;" class=3D"">Dear =
all:<div class=3D""><br class=3D""></div><div class=3D"">Recently we =
submitted v09. We would like to summarize the status:</div><div =
class=3D""><br class=3D""></div><div class=3D"">- We have applied all =
the comments we received so far (except one, see below). In particular, =
we would like to highlight that we have renamed the modules as a =
consequence of some comments. In particular:</div><div class=3D""><br =
class=3D""></div><div class=3D"">ietf-ipsec-common =E2=80=94&gt; =
ietf-i2nsf-ikec</div><div class=3D"">ietf-ipsec-ike =E2=80=94&gt; =
ietf-i2nsf-ike</div><div class=3D"">ietf-ipsec-ikeless -&gt; =
ietf-i2nsf-ikeless</div><div class=3D""><br class=3D""></div><div =
class=3D"">- Moreover we made a minor change. We realized that =
encryption algorithms should also have a key-length. For example, it is =
not enough to say the algorithm is AES-CBC without specifying the =
key-length (e.g. 128 bits).&nbsp;</div><div class=3D""><br =
class=3D""></div><div class=3D"">- Regarding the pending comment, as you =
may have followed in the mailing list, it has been proposed to add a =
feature <b class=3D"">ikeless-notification</b> and the corresponding <b =
class=3D"">if ikeless-notification</b> in each notification&nbsp;<font =
color=3D"#000000" class=3D""><span style=3D"caret-color: rgb(0, 0, 0);" =
class=3D"">to indicate whether notifications are implemented by the =
NSF.&nbsp;</span></font><font color=3D"#000000" class=3D"">The goal here =
is to ensure broader&nbsp;applicability&nbsp;of the ikeless =
module.</font>&nbsp;If there is no objection, we can include this =
feature adding a description about the motivation behind this and =
prepare v10 very quickly.</div><div class=3D""><br class=3D""></div><div =
class=3D"">"To ensure broader applicability of this module, the =
notifications are marked as a feature. For the implementation of ikeless =
case, the NSF is expected to implement this feature.";</div><div =
class=3D""><br class=3D""></div><div class=3D""><font color=3D"#000000" =
class=3D""><span style=3D"caret-color: rgb(0, 0, 0);" class=3D"">The =
result would be (in tree format):</span></font></div><div class=3D""><font=
 color=3D"#000000" class=3D""><span style=3D"caret-color: rgb(0, 0, 0);" =
class=3D""><br class=3D""></span></font></div><div class=3D""><font =
color=3D"#000000" class=3D""><span style=3D"caret-color: rgb(0, 0, 0);" =
class=3D""><div class=3D"">notifications:</div><div class=3D"">&nbsp; =
&nbsp; +---n sadb-acquire <b =
class=3D"">{ikeless-notification}</b>?</div><div class=3D"">&nbsp; =
&nbsp; | &nbsp;+--ro ipsec-policy-name &nbsp; &nbsp;string</div><div =
class=3D"">&nbsp; &nbsp; | &nbsp;+--ro traffic-selector</div><div =
class=3D"">&nbsp; &nbsp; | &nbsp; &nbsp; +--ro local-subnet &nbsp; =
&nbsp; &nbsp;inet:ip-prefix</div><div class=3D"">&nbsp; &nbsp; | &nbsp; =
&nbsp; +--ro remote-subnet &nbsp; &nbsp; inet:ip-prefix</div><div =
class=3D"">&nbsp; &nbsp; | &nbsp; &nbsp; +--ro inner-protocol? &nbsp; =
ipsec-inner-protocol</div><div class=3D"">&nbsp; &nbsp; | &nbsp; &nbsp; =
+--ro local-ports* [start end]</div><div class=3D"">&nbsp; &nbsp; | =
&nbsp; &nbsp; | &nbsp;+--ro start &nbsp; =
&nbsp;inet:port-number</div><div class=3D"">&nbsp; &nbsp; | &nbsp; =
&nbsp; | &nbsp;+--ro end &nbsp; &nbsp; &nbsp;inet:port-number</div><div =
class=3D"">&nbsp; &nbsp; | &nbsp; &nbsp; +--ro remote-ports* [start =
end]</div><div class=3D"">&nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; =
&nbsp;+--ro start &nbsp; &nbsp;inet:port-number</div><div =
class=3D"">&nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp;+--ro end &nbsp; =
&nbsp; &nbsp;inet:port-number</div><div class=3D"">&nbsp; &nbsp; +---n =
sadb-expire <b class=3D"">{ikeless-notification}</b>?</div><div =
class=3D"">&nbsp; &nbsp; | &nbsp;+--ro ipsec-sa-name &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; string</div><div class=3D"">&nbsp; &nbsp; | =
&nbsp;+--ro soft-lifetime-expire? &nbsp; boolean</div><div =
class=3D"">&nbsp; &nbsp; | &nbsp;+--ro lifetime-current</div><div =
class=3D"">&nbsp; &nbsp; | &nbsp; &nbsp; +--ro time? &nbsp; &nbsp; =
&nbsp;uint32</div><div class=3D"">&nbsp; &nbsp; | &nbsp; &nbsp; +--ro =
bytes? &nbsp; &nbsp; uint32</div><div class=3D"">&nbsp; &nbsp; | &nbsp; =
&nbsp; +--ro packets? &nbsp; uint32</div><div class=3D"">&nbsp; &nbsp; | =
&nbsp; &nbsp; +--ro idle? &nbsp; &nbsp; &nbsp;uint32</div><div =
class=3D"">&nbsp; &nbsp; +---n sadb-seq-overflow <b =
class=3D"">{ikeless-notification}</b>?</div><div class=3D"">&nbsp; =
&nbsp; | &nbsp;+--ro ipsec-sa-name &nbsp; &nbsp;string</div><div =
class=3D"">&nbsp; &nbsp; +---n sadb-bad-spi <b =
class=3D"">{ikeless-notification}</b>?</div><div class=3D"">&nbsp; =
&nbsp; &nbsp; &nbsp;+--ro spi &nbsp; =
&nbsp;uint32</div></span></font></div><div class=3D""><br =
class=3D""></div><div class=3D""><br class=3D""></div><div class=3D"">Best=
 Regards. &nbsp;</div><div class=3D""><div><br class=3D""><blockquote =
type=3D"cite" class=3D""><div class=3D"">El 12 oct 2020, a las 20:15, <a =
href=3D"mailto:internet-drafts@ietf.org" =
class=3D"">internet-drafts@ietf.org</a> escribi=C3=B3:</div><br =
class=3D"Apple-interchange-newline"><div class=3D""><div class=3D""><br =
class=3D"">A new version of I-D, =
draft-ietf-i2nsf-sdn-ipsec-flow-protection-09.txt<br class=3D"">has been =
successfully submitted by Rafa Marin-Lopez and posted to the<br =
class=3D"">IETF repository.<br class=3D""><br class=3D"">Name:<span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</span><span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</span>draft-ietf-i2nsf-sdn-ipsec-flow-protection<br =
class=3D"">Revision:<span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</span>09<br class=3D"">Title:<span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</span><span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</span>Software-Defined Networking (SDN)-based IPsec Flow Protection<br =
class=3D"">Document date:<span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</span>2020-10-12<br =
class=3D"">Group:<span class=3D"Apple-tab-span" style=3D"white-space:pre">=
	</span><span class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</span>i2nsf<br class=3D"">Pages:<span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</span><span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</span>92<br class=3D"">URL: =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a =
href=3D"https://www.ietf.org/archive/id/draft-ietf-i2nsf-sdn-ipsec-flow-pr=
otection-09.txt" =
class=3D"">https://www.ietf.org/archive/id/draft-ietf-i2nsf-sdn-ipsec-flow=
-protection-09.txt</a><br class=3D"">Status: =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a =
href=3D"https://datatracker.ietf.org/doc/draft-ietf-i2nsf-sdn-ipsec-flow-p=
rotection/" =
class=3D"">https://datatracker.ietf.org/doc/draft-ietf-i2nsf-sdn-ipsec-flo=
w-protection/</a><br class=3D"">Htmlized: =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a =
href=3D"https://datatracker.ietf.org/doc/html/draft-ietf-i2nsf-sdn-ipsec-f=
low-protection" =
class=3D"">https://datatracker.ietf.org/doc/html/draft-ietf-i2nsf-sdn-ipse=
c-flow-protection</a><br class=3D"">Htmlized: =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a =
href=3D"https://tools.ietf.org/html/draft-ietf-i2nsf-sdn-ipsec-flow-protec=
tion-09" =
class=3D"">https://tools.ietf.org/html/draft-ietf-i2nsf-sdn-ipsec-flow-pro=
tection-09</a><br class=3D"">Diff: =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a =
href=3D"https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-i2nsf-sdn-ipsec-flo=
w-protection-09" =
class=3D"">https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-i2nsf-sdn-ipsec-=
flow-protection-09</a><br class=3D""><br class=3D"">Abstract:<br =
class=3D""> &nbsp;&nbsp;This document describes how to provide =
IPsec-based flow protection<br class=3D""> &nbsp;&nbsp;(integrity and =
confidentiality) by means of an Interface to Network<br class=3D""> =
&nbsp;&nbsp;Security Function (I2NSF) controller. &nbsp;It considers two =
main well-<br class=3D""> &nbsp;&nbsp;known scenarios in IPsec: (i) =
gateway-to-gateway and (ii) host-to-<br class=3D""> &nbsp;&nbsp;host. =
&nbsp;The service described in this document allows the<br class=3D""> =
&nbsp;&nbsp;configuration and monitoring of IPsec Security Associations =
(SAs)<br class=3D""> &nbsp;&nbsp;from a I2NSF Controller to one or =
several flow-based Network Security<br class=3D""> &nbsp;&nbsp;Functions =
(NSFs) that rely on IPsec to protect data traffic.<br class=3D""><br =
class=3D""> &nbsp;&nbsp;The document focuses on the I2NSF NSF-facing =
interface by providing<br class=3D""> &nbsp;&nbsp;YANG data models for =
configuring the IPsec databases (SPD, SAD, PAD)<br class=3D""> =
&nbsp;&nbsp;and IKEv2. &nbsp;This allows IPsec SA establishment with =
minimal<br class=3D""> &nbsp;&nbsp;intervention by the network =
administrator. &nbsp;It does not define any<br class=3D""> =
&nbsp;&nbsp;new protocol.<br class=3D""><br class=3D""><br class=3D""><br =
class=3D""><br class=3D"">Please note that it may take a couple of =
minutes from the time of submission<br class=3D"">until the htmlized =
version and diff are available at <a href=3D"http://tools.ietf.org" =
class=3D"">tools.ietf.org</a>.<br class=3D""><br class=3D"">The IETF =
Secretariat<br class=3D""><br class=3D""><br =
class=3D""></div></div></blockquote></div><br class=3D""><div class=3D"">
<div style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space;" class=3D""><div style=3D"color: =
rgb(0, 0, 0); font-family: Courier; font-size: 16px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
orphans: auto; text-align: start; text-indent: 0px; text-transform: =
none; white-space: normal; widows: auto; word-spacing: 0px; =
-webkit-text-stroke-width: =
0px;">-------------------------------------------------------<br =
class=3D"">Rafa Marin-Lopez, PhD<br class=3D"">Dept. Information =
and&nbsp;Communications&nbsp;Engineering (DIIC)<br class=3D"">Faculty of =
Computer&nbsp;Science-University of&nbsp;Murcia<br class=3D"">30100 =
Murcia - Spain<br class=3D"">Telf: +34868888501 Fax:&nbsp;+34868884151 =
<a href=3D"mailto:rafa@um.es" class=3D"">e-mail:&nbsp;rafa@um.es</a><br =
class=3D"">-------------------------------------------------------</div><d=
iv style=3D"color: rgb(0, 0, 0); font-family: Courier; font-size: 16px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; orphans: auto; text-align: start; text-indent: =
0px; text-transform: none; white-space: normal; widows: auto; =
word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=3D""><br =
class=3D""></div><br class=3D"Apple-interchange-newline"></div><br =
class=3D"Apple-interchange-newline">
</div>

<br class=3D""></div></body></html>=

--Apple-Mail=_70C4207B-C17E-40FE-A432-F907BCC6A079--


From nobody Fri Oct 16 15:55:18 2020
Return-Path: <lberger@labn.net>
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 2445E3A07C3; Fri, 16 Oct 2020 15:55:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.539
X-Spam-Level: 
X-Spam-Status: No, score=-0.539 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.213, RDNS_NONE=0.793, SPF_HELO_NONE=0.001, SPF_NEUTRAL=0.779, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
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 vBbO_vF2tnLM; Fri, 16 Oct 2020 15:55:11 -0700 (PDT)
Received: from slmp-550-48.slc.westdc.net (unknown [174.127.108.195]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0C5363A07BD; Fri, 16 Oct 2020 15:55:10 -0700 (PDT)
Received: from pool-100-15-105-234.washdc.fios.verizon.net ([100.15.105.234]:61284 helo=[11.5.0.121]) by slmp-550-48.slc.westdc.net with esmtpsa (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.93) (envelope-from <lberger@labn.net>) id 1kTYcv-00Bivr-1y; Fri, 16 Oct 2020 16:55:09 -0600
To: Rafa Marin-Lopez <rafa@um.es>, i2nsf@ietf.org
Cc: ipsec@ietf.org, yang-doctors@ietf.org, last-call@ietf.org, draft-ietf-i2nsf-sdn-ipsec-flow-protection.all@ietf.org
References: <160252655236.514.5675626677635075934@ietfa.amsl.com> <D9E7F4D7-E6EC-4268-B989-F764CEE34B2B@um.es>
From: Lou Berger <lberger@labn.net>
Message-ID: <0df078b7-14b6-1262-4cfa-4d1429ef945c@labn.net>
Date: Fri, 16 Oct 2020 18:55:07 -0400
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.7.0
MIME-Version: 1.0
In-Reply-To: <D9E7F4D7-E6EC-4268-B989-F764CEE34B2B@um.es>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - slmp-550-48.slc.westdc.net
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - labn.net
X-Get-Message-Sender-Via: slmp-550-48.slc.westdc.net: authenticated_id: lberger@labn.net
X-Authenticated-Sender: slmp-550-48.slc.westdc.net: lberger@labn.net
X-Source: 
X-Source-Args: 
X-Source-Dir: 
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2nsf/GS-yBGiV1_BTXyvlJH4OWz_MVeY>
Subject: Re: [I2nsf] [IPsec] New Version Notification for draft-ietf-i2nsf-sdn-ipsec-flow-protection-09.txt
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: Fri, 16 Oct 2020 22:55:13 -0000

On 10/16/2020 4:19 AM, Rafa Marin-Lopez wrote:
 >   If there is no objection, we can include this feature adding a
 > description about the motivation behind this and prepare v10 very 
quickly.

Thank you for this.  I think it would be a really helpful change -- and 
I support it.

Lou

(as contributor with multiple hats)

On 10/16/2020 4:19 AM, Rafa Marin-Lopez wrote:
> Dear all:
> 
> Recently we submitted v09. We would like to summarize the status:
> 
> - We have applied all the comments we received so far (except one, see 
> below). In particular, we would like to highlight that we have renamed 
> the modules as a consequence of some comments. In particular:
> 
> ietf-ipsec-common —> ietf-i2nsf-ikec
> ietf-ipsec-ike —> ietf-i2nsf-ike
> ietf-ipsec-ikeless -> ietf-i2nsf-ikeless
> 
> - Moreover we made a minor change. We realized that encryption 
> algorithms should also have a key-length. For example, it is not enough 
> to say the algorithm is AES-CBC without specifying the key-length (e.g. 
> 128 bits).
> 
> - Regarding the pending comment, as you may have followed in the mailing 
> list, it has been proposed to add a feature *ikeless-notification* and 
> the corresponding *if ikeless-notification* in each notification to 
> indicate whether notifications are implemented by the NSF. The goal here 
> is to ensure broader applicability of the ikeless module. If there is no 
> objection, we can include this feature adding a description about the 
> motivation behind this and prepare v10 very quickly.
> 
> "To ensure broader applicability of this module, the notifications are 
> marked as a feature. For the implementation of ikeless case, the NSF is 
> expected to implement this feature.";
> 
> The result would be (in tree format):
> 
> notifications:
>      +---n sadb-acquire *{ikeless-notification}*?
>      |  +--ro ipsec-policy-name    string
>      |  +--ro traffic-selector
>      |     +--ro local-subnet      inet:ip-prefix
>      |     +--ro remote-subnet     inet:ip-prefix
>      |     +--ro inner-protocol?   ipsec-inner-protocol
>      |     +--ro local-ports* [start end]
>      |     |  +--ro start    inet:port-number
>      |     |  +--ro end      inet:port-number
>      |     +--ro remote-ports* [start end]
>      |        +--ro start    inet:port-number
>      |        +--ro end      inet:port-number
>      +---n sadb-expire *{ikeless-notification}*?
>      |  +--ro ipsec-sa-name           string
>      |  +--ro soft-lifetime-expire?   boolean
>      |  +--ro lifetime-current
>      |     +--ro time?      uint32
>      |     +--ro bytes?     uint32
>      |     +--ro packets?   uint32
>      |     +--ro idle?      uint32
>      +---n sadb-seq-overflow *{ikeless-notification}*?
>      |  +--ro ipsec-sa-name    string
>      +---n sadb-bad-spi *{ikeless-notification}*?
>         +--ro spi    uint32
> 
> 
> Best Regards.
> 
>> El 12 oct 2020, a las 20:15, internet-drafts@ietf.org 
>> <mailto:internet-drafts@ietf.org> escribió:
>>
>>
>> A new version of I-D, draft-ietf-i2nsf-sdn-ipsec-flow-protection-09.txt
>> has been successfully submitted by Rafa Marin-Lopez and posted to the
>> IETF repository.
>>
>> Name:draft-ietf-i2nsf-sdn-ipsec-flow-protection
>> Revision:09
>> Title:Software-Defined Networking (SDN)-based IPsec Flow Protection
>> Document date:2020-10-12
>> Group:i2nsf
>> Pages:92
>> URL: 
>> https://www.ietf.org/archive/id/draft-ietf-i2nsf-sdn-ipsec-flow-protection-09.txt
>> Status: 
>> https://datatracker.ietf.org/doc/draft-ietf-i2nsf-sdn-ipsec-flow-protection/
>> Htmlized: 
>> https://datatracker.ietf.org/doc/html/draft-ietf-i2nsf-sdn-ipsec-flow-protection
>> Htmlized: 
>> https://tools.ietf.org/html/draft-ietf-i2nsf-sdn-ipsec-flow-protection-09
>> Diff: 
>> https://www.ietf.org/rfcdiff?url2=draft-ietf-i2nsf-sdn-ipsec-flow-protection-09
>>
>> Abstract:
>>   This document describes how to provide IPsec-based flow protection
>>   (integrity and confidentiality) by means of an Interface to Network
>>   Security Function (I2NSF) controller.  It considers two main well-
>>   known scenarios in IPsec: (i) gateway-to-gateway and (ii) host-to-
>>   host.  The service described in this document allows the
>>   configuration and monitoring of IPsec Security Associations (SAs)
>>   from a I2NSF Controller to one or several flow-based Network Security
>>   Functions (NSFs) that rely on IPsec to protect data traffic.
>>
>>   The document focuses on the I2NSF NSF-facing interface by providing
>>   YANG data models for configuring the IPsec databases (SPD, SAD, PAD)
>>   and IKEv2.  This allows IPsec SA establishment with minimal
>>   intervention by the network administrator.  It does not define any
>>   new protocol.
>>
>>
>>
>>
>> Please note that it may take a couple of minutes from the time of 
>> submission
>> until the htmlized version and diff are available at tools.ietf.org 
>> <http://tools.ietf.org>.
>>
>> The IETF Secretariat
>>
>>
> 
> -------------------------------------------------------
> 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 <mailto:rafa@um.es>
> -------------------------------------------------------
> 
> 
> 
> 


From nobody Wed Oct 21 06:50:22 2020
Return-Path: <internet-drafts@ietf.org>
X-Original-To: i2nsf@ietf.org
Delivered-To: i2nsf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 43AF03A10D7; Wed, 21 Oct 2020 06:50:20 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
Cc: i2nsf@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 7.20.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: i2nsf@ietf.org
Message-ID: <160328822023.23859.17457037216027253752@ietfa.amsl.com>
Date: Wed, 21 Oct 2020 06:50:20 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2nsf/-3ugGaaF4zmQ-PjqZLn_m51I1UE>
Subject: [I2nsf] I-D Action: draft-ietf-i2nsf-sdn-ipsec-flow-protection-10.txt
X-BeenThere: i2nsf@ietf.org
X-Mailman-Version: 2.1.29
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, 21 Oct 2020 13:50:20 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Interface to Network Security Functions WG of the IETF.

        Title           : Software-Defined Networking (SDN)-based IPsec Flow Protection
        Authors         : Rafa Marin-Lopez
                          Gabriel Lopez-Millan
                          Fernando Pereniguez-Garcia
	Filename        : draft-ietf-i2nsf-sdn-ipsec-flow-protection-10.txt
	Pages           : 92
	Date            : 2020-10-21

Abstract:
   This document describes how to provide IPsec-based flow protection
   (integrity and confidentiality) by means of an Interface to Network
   Security Function (I2NSF) controller.  It considers two main well-
   known scenarios in IPsec: (i) gateway-to-gateway and (ii) host-to-
   host.  The service described in this document allows the
   configuration and monitoring of IPsec Security Associations (SAs)
   from a I2NSF Controller to one or several flow-based Network Security
   Functions (NSFs) that rely on IPsec to protect data traffic.

   The document focuses on the I2NSF NSF-facing interface by providing
   YANG data models for configuring the IPsec databases (SPD, SAD, PAD)
   and IKEv2.  This allows IPsec SA establishment with minimal
   intervention by the network administrator.  It does not define any
   new protocol.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-i2nsf-sdn-ipsec-flow-protection/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-i2nsf-sdn-ipsec-flow-protection-10
https://datatracker.ietf.org/doc/html/draft-ietf-i2nsf-sdn-ipsec-flow-protection-10

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-i2nsf-sdn-ipsec-flow-protection-10


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/



From nobody Wed Oct 21 10:07:11 2020
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 929773A1281; Wed, 21 Oct 2020 10:07:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level: 
X-Spam-Status: No, score=-2.098 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, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H2=-0.001, 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=um.es
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 sBGNI7SkbjoW; Wed, 21 Oct 2020 10:07:04 -0700 (PDT)
Received: from mx01.puc.rediris.es (outbound6mad.lav.puc.rediris.es [130.206.19.149]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 707713A1265; Wed, 21 Oct 2020 10:07:04 -0700 (PDT)
Received: from xenon41.um.es (xenon41.um.es [155.54.212.167]) by mx01.puc.rediris.es  with ESMTP id 09LH72iS005106-09LH72iT005106; Wed, 21 Oct 2020 19:07:02 +0200
Received: from localhost (localhost [127.0.0.1]) by xenon41.um.es (Postfix) with ESMTP id 07EE02121A; Wed, 21 Oct 2020 19:07:02 +0200 (CEST)
X-Virus-Scanned: by antispam in UMU at xenon41.um.es
Received: from xenon41.um.es ([127.0.0.1]) by localhost (xenon41.um.es [127.0.0.1]) (amavisd-new, port 10024) with LMTP id QkE2SWtmSIUE; Wed, 21 Oct 2020 19:07:01 +0200 (CEST)
Received: from [192.168.1.33] (135.red-79-150-250.dynamicip.rima-tde.net [79.150.250.135]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: rafa@um.es) by xenon41.um.es (Postfix) with ESMTPSA id 004FC21219; Wed, 21 Oct 2020 19:06:58 +0200 (CEST)
From: Rafa Marin-Lopez <rafa@um.es>
Content-Type: multipart/alternative; boundary="Apple-Mail=_71772B42-ED03-4C23-A8E2-7783B42728D0"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.14\))
Date: Wed, 21 Oct 2020 19:06:57 +0200
References: <160328822041.23859.7847794438066881847@ietfa.amsl.com>
Cc: Rafa Marin-Lopez <rafa@um.es>, yang-doctors@ietf.org, ipsec@ietf.org, last-call@ietf.org, Gabriel Lopez <gabilm@um.es>, Fernando Pereniguez-Garcia <fernando.pereniguez@cud.upct.es>
To: i2nsf@ietf.org
Message-Id: <684BB5B4-F54D-40D6-885E-3F8114DE33C3@um.es>
X-Mailer: Apple Mail (2.3445.104.14)
X-FEAS-SPF: spf-result=pass, ip=155.54.212.167, helo=xenon41.um.es, mailFrom=rafa@um.es
Authentication-Results: mx01.puc.rediris.es; spf=pass (rediris.es: domain of rafa@um.es designates 155.54.212.167 as permitted sender) smtp.mailfrom=rafa@um.es
X-FE-Policy-ID: 2:15:0:SYSTEM, 2:15:1:upct.es
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; d=um.es; s=DKIM; c=relaxed/relaxed;  h=from:content-type:mime-version:subject:date:references:cc:to:message-id; bh=wuRO1LHehRAZiC9LAQ3VcubTJq5au9CVs04jerKw/1w=; b=CGAaIR1Hv7ke9ThvVLMSUdNmzDdRG61JYB+y00tVgWyQtGKOe+uWdpFpCrYg22KB+V6mmAdcaMJm ypoaRq0rbIr9Ea5i+tAEYAoXUFHObswAqjqq38wU7WwTYqwoecviUSNvezsLUMNnGCbx1DfI0b14 Mbjx+gqsKTIqXEybXs7+uIveuRHpEzO8LG9L+qeqwk8Rjd/9e/13dOHJuWDhtrQlxd7gKCShsLqb lZ9UvUW4fKmYKoh/sEbdujNsx51NM/m+c/mHUiu00fI+VzDHQmYi4Bd5affqI7anShjw3tc3z6cz ITAFStO2/lknJTZPg0jXRvoX1WWamn8TFWvqIw==
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2nsf/NjDQee5Q5cCiF1MUbYMjPij356M>
Subject: [I2nsf] Fwd: New Version Notification for draft-ietf-i2nsf-sdn-ipsec-flow-protection-10.txt
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: Wed, 21 Oct 2020 17:07:07 -0000

--Apple-Mail=_71772B42-ED03-4C23-A8E2-7783B42728D0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Dear all:

We have just submitted -10 with the changes we mentioned in our previous =
e-mail about version -09.

Now we have a feature ikeless-connection and if-feature =
ikeless-notification in the notifications we have in ikeless module, so =
that we ensure broader applicability of this module, as we already =
explained in our previous e-mail.=20

Best Regards.


> Inicio del mensaje reenviado:
>=20
> De: internet-drafts@ietf.org
> Asunto: New Version Notification for =
draft-ietf-i2nsf-sdn-ipsec-flow-protection-10.txt
> Fecha: 21 de octubre de 2020, 15:50:20 CEST
> Para: "Gabriel Lopez-Millan" <gabilm@um.es>, "Rafa Marin-Lopez" =
<rafa@um.es>, "Rafael Lopez" <rafa@um.es>, "Fernando Pereniguez-Garcia" =
<fernando.pereniguez@cud.upct.es>
>=20
>=20
> A new version of I-D, =
draft-ietf-i2nsf-sdn-ipsec-flow-protection-10.txt
> has been successfully submitted by Rafa Marin-Lopez and posted to the
> IETF repository.
>=20
> Name:		draft-ietf-i2nsf-sdn-ipsec-flow-protection
> Revision:	10
> Title:		Software-Defined Networking (SDN)-based IPsec =
Flow Protection
> Document date:	2020-10-21
> Group:		i2nsf
> Pages:		92
> URL:            =
https://www.ietf.org/archive/id/draft-ietf-i2nsf-sdn-ipsec-flow-protection=
-10.txt
> Status:         =
https://datatracker.ietf.org/doc/draft-ietf-i2nsf-sdn-ipsec-flow-protectio=
n/
> Htmlized:       =
https://datatracker.ietf.org/doc/html/draft-ietf-i2nsf-sdn-ipsec-flow-prot=
ection
> Htmlized:       =
https://tools.ietf.org/html/draft-ietf-i2nsf-sdn-ipsec-flow-protection-10
> Diff:           =
https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-i2nsf-sdn-ipsec-flow-protec=
tion-10
>=20
> Abstract:
>   This document describes how to provide IPsec-based flow protection
>   (integrity and confidentiality) by means of an Interface to Network
>   Security Function (I2NSF) controller.  It considers two main well-
>   known scenarios in IPsec: (i) gateway-to-gateway and (ii) host-to-
>   host.  The service described in this document allows the
>   configuration and monitoring of IPsec Security Associations (SAs)
>   from a I2NSF Controller to one or several flow-based Network =
Security
>   Functions (NSFs) that rely on IPsec to protect data traffic.
>=20
>   The document focuses on the I2NSF NSF-facing interface by providing
>   YANG data models for configuring the IPsec databases (SPD, SAD, PAD)
>   and IKEv2.  This allows IPsec SA establishment with minimal
>   intervention by the network administrator.  It does not define any
>   new protocol.
>=20
>=20
>=20
>=20
> Please note that it may take a couple of minutes from the time of =
submission
> until the htmlized version and diff are available at tools.ietf.org.
>=20
> The IETF Secretariat
>=20
>=20

-------------------------------------------------------
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
-------------------------------------------------------





--Apple-Mail=_71772B42-ED03-4C23-A8E2-7783B42728D0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3Dus-ascii"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: after-white-space;" class=3D"">Dear =
all:<div class=3D""><br class=3D""></div><div class=3D"">We have just =
submitted -10 with the changes we mentioned in our previous e-mail about =
version -09.</div><div class=3D""><br class=3D""></div><div class=3D"">Now=
 we have a feature ikeless-connection and if-feature =
ikeless-notification in the notifications we have in ikeless module, so =
that we ensure broader applicability of this module, as we already =
explained in our previous e-mail.&nbsp;</div><div class=3D""><br =
class=3D""></div><div class=3D"">Best Regards.</div><div class=3D""><br =
class=3D""><div><br class=3D""><blockquote type=3D"cite" class=3D""><div =
class=3D"">Inicio del mensaje reenviado:</div><br =
class=3D"Apple-interchange-newline"><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px;" class=3D""><span=
 style=3D"font-family: -webkit-system-font, Helvetica Neue, Helvetica, =
sans-serif; color:rgba(0, 0, 0, 1.0);" class=3D""><b class=3D"">De: =
</b></span><span style=3D"font-family: -webkit-system-font, Helvetica =
Neue, Helvetica, sans-serif;" class=3D""><a =
href=3D"mailto:internet-drafts@ietf.org" =
class=3D"">internet-drafts@ietf.org</a><br class=3D""></span></div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px;" class=3D""><span style=3D"font-family: =
-webkit-system-font, Helvetica Neue, Helvetica, sans-serif; =
color:rgba(0, 0, 0, 1.0);" class=3D""><b class=3D"">Asunto: =
</b></span><span style=3D"font-family: -webkit-system-font, Helvetica =
Neue, Helvetica, sans-serif;" class=3D""><b class=3D"">New Version =
Notification for =
draft-ietf-i2nsf-sdn-ipsec-flow-protection-10.txt</b><br =
class=3D""></span></div><div style=3D"margin-top: 0px; margin-right: =
0px; margin-bottom: 0px; margin-left: 0px;" class=3D""><span =
style=3D"font-family: -webkit-system-font, Helvetica Neue, Helvetica, =
sans-serif; color:rgba(0, 0, 0, 1.0);" class=3D""><b class=3D"">Fecha: =
</b></span><span style=3D"font-family: -webkit-system-font, Helvetica =
Neue, Helvetica, sans-serif;" class=3D"">21 de octubre de 2020, 15:50:20 =
CEST<br class=3D""></span></div><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px;" class=3D""><span=
 style=3D"font-family: -webkit-system-font, Helvetica Neue, Helvetica, =
sans-serif; color:rgba(0, 0, 0, 1.0);" class=3D""><b class=3D"">Para: =
</b></span><span style=3D"font-family: -webkit-system-font, Helvetica =
Neue, Helvetica, sans-serif;" class=3D"">"Gabriel Lopez-Millan" &lt;<a =
href=3D"mailto:gabilm@um.es" class=3D"">gabilm@um.es</a>&gt;, "Rafa =
Marin-Lopez" &lt;<a href=3D"mailto:rafa@um.es" =
class=3D"">rafa@um.es</a>&gt;, "Rafael Lopez" &lt;<a =
href=3D"mailto:rafa@um.es" class=3D"">rafa@um.es</a>&gt;, "Fernando =
Pereniguez-Garcia" &lt;<a href=3D"mailto:fernando.pereniguez@cud.upct.es" =
class=3D"">fernando.pereniguez@cud.upct.es</a>&gt;<br =
class=3D""></span></div><br class=3D""><div class=3D""><div class=3D""><br=
 class=3D"">A new version of I-D, =
draft-ietf-i2nsf-sdn-ipsec-flow-protection-10.txt<br class=3D"">has been =
successfully submitted by Rafa Marin-Lopez and posted to the<br =
class=3D"">IETF repository.<br class=3D""><br class=3D"">Name:<span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</span><span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</span>draft-ietf-i2nsf-sdn-ipsec-flow-protection<br =
class=3D"">Revision:<span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</span>10<br class=3D"">Title:<span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</span><span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</span>Software-Defined Networking (SDN)-based IPsec Flow Protection<br =
class=3D"">Document date:<span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</span>2020-10-21<br =
class=3D"">Group:<span class=3D"Apple-tab-span" style=3D"white-space:pre">=
	</span><span class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</span>i2nsf<br class=3D"">Pages:<span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</span><span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</span>92<br class=3D"">URL: =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a =
href=3D"https://www.ietf.org/archive/id/draft-ietf-i2nsf-sdn-ipsec-flow-pr=
otection-10.txt" =
class=3D"">https://www.ietf.org/archive/id/draft-ietf-i2nsf-sdn-ipsec-flow=
-protection-10.txt</a><br class=3D"">Status: =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a =
href=3D"https://datatracker.ietf.org/doc/draft-ietf-i2nsf-sdn-ipsec-flow-p=
rotection/" =
class=3D"">https://datatracker.ietf.org/doc/draft-ietf-i2nsf-sdn-ipsec-flo=
w-protection/</a><br class=3D"">Htmlized: =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a =
href=3D"https://datatracker.ietf.org/doc/html/draft-ietf-i2nsf-sdn-ipsec-f=
low-protection" =
class=3D"">https://datatracker.ietf.org/doc/html/draft-ietf-i2nsf-sdn-ipse=
c-flow-protection</a><br class=3D"">Htmlized: =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a =
href=3D"https://tools.ietf.org/html/draft-ietf-i2nsf-sdn-ipsec-flow-protec=
tion-10" =
class=3D"">https://tools.ietf.org/html/draft-ietf-i2nsf-sdn-ipsec-flow-pro=
tection-10</a><br class=3D"">Diff: =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a =
href=3D"https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-i2nsf-sdn-ipsec-flo=
w-protection-10" =
class=3D"">https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-i2nsf-sdn-ipsec-=
flow-protection-10</a><br class=3D""><br class=3D"">Abstract:<br =
class=3D""> &nbsp;&nbsp;This document describes how to provide =
IPsec-based flow protection<br class=3D""> &nbsp;&nbsp;(integrity and =
confidentiality) by means of an Interface to Network<br class=3D""> =
&nbsp;&nbsp;Security Function (I2NSF) controller. &nbsp;It considers two =
main well-<br class=3D""> &nbsp;&nbsp;known scenarios in IPsec: (i) =
gateway-to-gateway and (ii) host-to-<br class=3D""> &nbsp;&nbsp;host. =
&nbsp;The service described in this document allows the<br class=3D""> =
&nbsp;&nbsp;configuration and monitoring of IPsec Security Associations =
(SAs)<br class=3D""> &nbsp;&nbsp;from a I2NSF Controller to one or =
several flow-based Network Security<br class=3D""> &nbsp;&nbsp;Functions =
(NSFs) that rely on IPsec to protect data traffic.<br class=3D""><br =
class=3D""> &nbsp;&nbsp;The document focuses on the I2NSF NSF-facing =
interface by providing<br class=3D""> &nbsp;&nbsp;YANG data models for =
configuring the IPsec databases (SPD, SAD, PAD)<br class=3D""> =
&nbsp;&nbsp;and IKEv2. &nbsp;This allows IPsec SA establishment with =
minimal<br class=3D""> &nbsp;&nbsp;intervention by the network =
administrator. &nbsp;It does not define any<br class=3D""> =
&nbsp;&nbsp;new protocol.<br class=3D""><br class=3D""><br class=3D""><br =
class=3D""><br class=3D"">Please note that it may take a couple of =
minutes from the time of submission<br class=3D"">until the htmlized =
version and diff are available at <a href=3D"http://tools.ietf.org" =
class=3D"">tools.ietf.org</a>.<br class=3D""><br class=3D"">The IETF =
Secretariat<br class=3D""><br class=3D""><br =
class=3D""></div></div></blockquote></div><br class=3D""><div class=3D"">
<div style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space;" class=3D""><div style=3D"color: =
rgb(0, 0, 0); font-family: Courier; font-size: 16px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
orphans: auto; text-align: start; text-indent: 0px; text-transform: =
none; white-space: normal; widows: auto; word-spacing: 0px; =
-webkit-text-stroke-width: =
0px;">-------------------------------------------------------<br =
class=3D"">Rafa Marin-Lopez, PhD<br class=3D"">Dept. Information =
and&nbsp;Communications&nbsp;Engineering (DIIC)<br class=3D"">Faculty of =
Computer&nbsp;Science-University of&nbsp;Murcia<br class=3D"">30100 =
Murcia - Spain<br class=3D"">Telf: +34868888501 Fax:&nbsp;+34868884151 =
<a href=3D"mailto:rafa@um.es" class=3D"">e-mail:&nbsp;rafa@um.es</a><br =
class=3D"">-------------------------------------------------------</div><d=
iv style=3D"color: rgb(0, 0, 0); font-family: Courier; font-size: 16px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; orphans: auto; text-align: start; text-indent: =
0px; text-transform: none; white-space: normal; widows: auto; =
word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=3D""><br =
class=3D""></div><br class=3D"Apple-interchange-newline"></div><br =
class=3D"Apple-interchange-newline">
</div>

<br class=3D""></div></body></html>=

--Apple-Mail=_71772B42-ED03-4C23-A8E2-7783B42728D0--


From nobody Thu Oct 22 06:32:56 2020
Return-Path: <internet-drafts@ietf.org>
X-Original-To: i2nsf@ietf.org
Delivered-To: i2nsf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 8D2A03A0BDB; Thu, 22 Oct 2020 06:32:50 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
Cc: i2nsf@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 7.20.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: i2nsf@ietf.org
Message-ID: <160337357054.29083.16375066387568447020@ietfa.amsl.com>
Date: Thu, 22 Oct 2020 06:32:50 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2nsf/WgY3dOklrMaWjyBJFH2Hu5gP3iM>
Subject: [I2nsf] I-D Action: draft-ietf-i2nsf-sdn-ipsec-flow-protection-11.txt
X-BeenThere: i2nsf@ietf.org
X-Mailman-Version: 2.1.29
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: Thu, 22 Oct 2020 13:32:51 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Interface to Network Security Functions WG of the IETF.

        Title           : Software-Defined Networking (SDN)-based IPsec Flow Protection
        Authors         : Rafa Marin-Lopez
                          Gabriel Lopez-Millan
                          Fernando Pereniguez-Garcia
	Filename        : draft-ietf-i2nsf-sdn-ipsec-flow-protection-11.txt
	Pages           : 92
	Date            : 2020-10-22

Abstract:
   This document describes how to provide IPsec-based flow protection
   (integrity and confidentiality) by means of an Interface to Network
   Security Function (I2NSF) controller.  It considers two main well-
   known scenarios in IPsec: (i) gateway-to-gateway and (ii) host-to-
   host.  The service described in this document allows the
   configuration and monitoring of IPsec Security Associations (SAs)
   from a I2NSF Controller to one or several flow-based Network Security
   Functions (NSFs) that rely on IPsec to protect data traffic.

   The document focuses on the I2NSF NSF-facing interface by providing
   YANG data models for configuring the IPsec databases (SPD, SAD, PAD)
   and IKEv2.  This allows IPsec SA establishment with minimal
   intervention by the network administrator.  It does not define any
   new protocol.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-i2nsf-sdn-ipsec-flow-protection/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-i2nsf-sdn-ipsec-flow-protection-11
https://datatracker.ietf.org/doc/html/draft-ietf-i2nsf-sdn-ipsec-flow-protection-11

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-i2nsf-sdn-ipsec-flow-protection-11


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/



From nobody Thu Oct 22 10:39:18 2020
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 1F4253A09DF; Thu, 22 Oct 2020 10:39:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level: 
X-Spam-Status: No, score=-2.099 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, RCVD_IN_MSPIKE_H2=-0.001, 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=um.es
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 xEV4GoxmC7gX; Thu, 22 Oct 2020 10:39:09 -0700 (PDT)
Received: from mx01.puc.rediris.es (outbound4mad.lav.puc.rediris.es [130.206.19.145]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 17BA33A09CD; Thu, 22 Oct 2020 10:39:08 -0700 (PDT)
Received: from xenon43.um.es (xenon43.um.es [155.54.212.170]) by mx01.puc.rediris.es  with ESMTP id 09MHd6b9032242-09MHd6bA032242; Thu, 22 Oct 2020 19:39:06 +0200
Received: from localhost (localhost [127.0.0.1]) by xenon43.um.es (Postfix) with ESMTP id 91F1824F52; Thu, 22 Oct 2020 19:39:06 +0200 (CEST)
X-Virus-Scanned: by antispam in UMU at xenon43.um.es
Received: from xenon43.um.es ([127.0.0.1]) by localhost (xenon43.um.es [127.0.0.1]) (amavisd-new, port 10024) with LMTP id Zp55wxfglAge; Thu, 22 Oct 2020 19:39:06 +0200 (CEST)
Received: from [192.168.1.33] (135.red-79-150-250.dynamicip.rima-tde.net [79.150.250.135]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: rafa@um.es) by xenon43.um.es (Postfix) with ESMTPSA id AC12C24F43; Thu, 22 Oct 2020 19:39:03 +0200 (CEST)
From: Rafa Marin-Lopez <rafa@um.es>
Content-Type: multipart/alternative; boundary="Apple-Mail=_EFEC2F4A-0BF7-418B-9A9A-7040280BE044"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.14\))
Date: Thu, 22 Oct 2020 19:39:02 +0200
References: <160337357077.29083.9236626834026808055@ietfa.amsl.com>
Cc: Rafa Marin-Lopez <rafa@um.es>, Gabriel Lopez <gabilm@um.es>, Fernando Pereniguez-Garcia <fernando.pereniguez@cud.upct.es>, ipsec@ietf.org, last-call@ietf.org, yang-doctors@ietf.org
To: i2nsf@ietf.org
Message-Id: <EE5AB669-73BB-4517-A6F4-23B7807FB36E@um.es>
X-Mailer: Apple Mail (2.3445.104.14)
X-FEAS-SPF: spf-result=pass, ip=155.54.212.170, helo=xenon43.um.es, mailFrom=rafa@um.es
Authentication-Results: mx01.puc.rediris.es; spf=pass (rediris.es: domain of rafa@um.es designates 155.54.212.170 as permitted sender) smtp.mailfrom=rafa@um.es
X-FE-Policy-ID: 2:15:0:SYSTEM, 2:15:1:upct.es
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; d=um.es; s=DKIM; c=relaxed/relaxed;  h=from:content-type:mime-version:subject:date:references:cc:to:message-id; bh=JXTrcbYCIhgi+BJc2/XH/o3OwqeCgof+ncrWhZoF7K0=; b=tXbJSztExe4h2taWFOMPGaX450ZTowkeIlE63nM5qsTn60Jl7WHA2RzvO3JQXZCEpWE6c5jT9pRI +87Le19k05n96FlJBCqYi3G4HXTv5HW8e+CgQ8YHQaU/F1zWZwaj/rF5qkTRUrR0ksoFUpl0Ncsw QoZ1DQLTcq4hbKN1fNYbiJyXKSlsBMoy6hHw4cyCK7Nnk1vEW8kUqAOZJ+RbPxcGCfaG1loHNsub OyNvCWSzgmEb4c0K1PuAW2dN9ee7gYAJdu/lLdNwRdHmcSXpa4feeD220LEgNC+TUCpNNguUD4Au edDbUlA+zeHsei3D7CaNyZqxnokTeUbNZ8cnSg==
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2nsf/IXLVc3_v0gTq4HeCPlfxRFYjcrY>
Subject: [I2nsf] Fwd: New Version Notification for draft-ietf-i2nsf-sdn-ipsec-flow-protection-11.txt
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: Thu, 22 Oct 2020 17:39:11 -0000

--Apple-Mail=_EFEC2F4A-0BF7-418B-9A9A-7040280BE044
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Dear all:

After receiving a suggestion to make things clearer in the feature =
ikeless-notification description, we have just uploaded a new version =
-11 with a minor change to add the following text:

feature ikeless-notification {=20
            description=20
                "This feature indicates that the server supports
                generating notifications in the ikeless module.
               =20
                To ensure broader applicability of this module,=20
                the notifications are marked as a feature.=20
                For the implementation of ikeless case,=20
                the NSF is expected to implement this=20
                feature.";
        }=20

Best Regards.

> Inicio del mensaje reenviado:
>=20
> De: internet-drafts@ietf.org
> Asunto: New Version Notification for =
draft-ietf-i2nsf-sdn-ipsec-flow-protection-11.txt
> Fecha: 22 de octubre de 2020, 15:32:50 CEST
> Para: "Fernando Pereniguez-Garcia" <fernando.pereniguez@cud.upct.es>, =
"Rafael Lopez" <rafa@um.es>, "Gabriel Lopez-Millan" <gabilm@um.es>, =
"Rafa Marin-Lopez" <rafa@um.es>
>=20
>=20
> A new version of I-D, =
draft-ietf-i2nsf-sdn-ipsec-flow-protection-11.txt
> has been successfully submitted by Rafa Marin-Lopez and posted to the
> IETF repository.
>=20
> Name:		draft-ietf-i2nsf-sdn-ipsec-flow-protection
> Revision:	11
> Title:		Software-Defined Networking (SDN)-based IPsec =
Flow Protection
> Document date:	2020-10-22
> Group:		i2nsf
> Pages:		92
> URL:            =
https://www.ietf.org/archive/id/draft-ietf-i2nsf-sdn-ipsec-flow-protection=
-11.txt
> Status:         =
https://datatracker.ietf.org/doc/draft-ietf-i2nsf-sdn-ipsec-flow-protectio=
n/
> Htmlized:       =
https://datatracker.ietf.org/doc/html/draft-ietf-i2nsf-sdn-ipsec-flow-prot=
ection
> Htmlized:       =
https://tools.ietf.org/html/draft-ietf-i2nsf-sdn-ipsec-flow-protection-11
> Diff:           =
https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-i2nsf-sdn-ipsec-flow-protec=
tion-11
>=20
> Abstract:
>   This document describes how to provide IPsec-based flow protection
>   (integrity and confidentiality) by means of an Interface to Network
>   Security Function (I2NSF) controller.  It considers two main well-
>   known scenarios in IPsec: (i) gateway-to-gateway and (ii) host-to-
>   host.  The service described in this document allows the
>   configuration and monitoring of IPsec Security Associations (SAs)
>   from a I2NSF Controller to one or several flow-based Network =
Security
>   Functions (NSFs) that rely on IPsec to protect data traffic.
>=20
>   The document focuses on the I2NSF NSF-facing interface by providing
>   YANG data models for configuring the IPsec databases (SPD, SAD, PAD)
>   and IKEv2.  This allows IPsec SA establishment with minimal
>   intervention by the network administrator.  It does not define any
>   new protocol.
>=20
>=20
>=20
>=20
> Please note that it may take a couple of minutes from the time of =
submission
> until the htmlized version and diff are available at tools.ietf.org.
>=20
> The IETF Secretariat
>=20
>=20

-------------------------------------------------------
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
-------------------------------------------------------





--Apple-Mail=_EFEC2F4A-0BF7-418B-9A9A-7040280BE044
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3Dus-ascii"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: after-white-space;" class=3D"">Dear =
all:<div class=3D""><br class=3D""></div><div class=3D"">After receiving =
a suggestion to make things clearer in the feature ikeless-notification =
description, we have just uploaded a new version -11 with a minor change =
to add the following text:</div><div class=3D""><br class=3D""></div><div =
class=3D""><div class=3D"">feature ikeless-notification =
{&nbsp;</div><div class=3D"">&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
description&nbsp;</div><div class=3D"">&nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; "<b class=3D"">This feature indicates that =
the server supports</b></div><div class=3D""><b class=3D"">&nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; generating notifications in =
the ikeless module</b>.</div><div class=3D"">&nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp;&nbsp;</div><div class=3D"">&nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; To ensure broader =
applicability of this module,&nbsp;</div><div class=3D"">&nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; the notifications are marked =
as a feature.&nbsp;</div><div class=3D"">&nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; For the implementation of ikeless =
case,&nbsp;</div><div class=3D"">&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; the NSF is expected to implement =
this&nbsp;</div><div class=3D"">&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; feature.";</div><div class=3D"">&nbsp; &nbsp; =
&nbsp; &nbsp; }&nbsp;</div></div><div class=3D""><br class=3D""></div><div=
 class=3D"">Best Regards.</div><div class=3D""><div><br =
class=3D""><blockquote type=3D"cite" class=3D""><div class=3D"">Inicio =
del mensaje reenviado:</div><br class=3D"Apple-interchange-newline"><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px;" class=3D""><span style=3D"font-family: =
-webkit-system-font, Helvetica Neue, Helvetica, sans-serif; =
color:rgba(0, 0, 0, 1.0);" class=3D""><b class=3D"">De: </b></span><span =
style=3D"font-family: -webkit-system-font, Helvetica Neue, Helvetica, =
sans-serif;" class=3D""><a href=3D"mailto:internet-drafts@ietf.org" =
class=3D"">internet-drafts@ietf.org</a><br class=3D""></span></div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px;" class=3D""><span style=3D"font-family: =
-webkit-system-font, Helvetica Neue, Helvetica, sans-serif; =
color:rgba(0, 0, 0, 1.0);" class=3D""><b class=3D"">Asunto: =
</b></span><span style=3D"font-family: -webkit-system-font, Helvetica =
Neue, Helvetica, sans-serif;" class=3D""><b class=3D"">New Version =
Notification for =
draft-ietf-i2nsf-sdn-ipsec-flow-protection-11.txt</b><br =
class=3D""></span></div><div style=3D"margin-top: 0px; margin-right: =
0px; margin-bottom: 0px; margin-left: 0px;" class=3D""><span =
style=3D"font-family: -webkit-system-font, Helvetica Neue, Helvetica, =
sans-serif; color:rgba(0, 0, 0, 1.0);" class=3D""><b class=3D"">Fecha: =
</b></span><span style=3D"font-family: -webkit-system-font, Helvetica =
Neue, Helvetica, sans-serif;" class=3D"">22 de octubre de 2020, 15:32:50 =
CEST<br class=3D""></span></div><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px;" class=3D""><span=
 style=3D"font-family: -webkit-system-font, Helvetica Neue, Helvetica, =
sans-serif; color:rgba(0, 0, 0, 1.0);" class=3D""><b class=3D"">Para: =
</b></span><span style=3D"font-family: -webkit-system-font, Helvetica =
Neue, Helvetica, sans-serif;" class=3D"">"Fernando Pereniguez-Garcia" =
&lt;<a href=3D"mailto:fernando.pereniguez@cud.upct.es" =
class=3D"">fernando.pereniguez@cud.upct.es</a>&gt;, "Rafael Lopez" =
&lt;<a href=3D"mailto:rafa@um.es" class=3D"">rafa@um.es</a>&gt;, =
"Gabriel Lopez-Millan" &lt;<a href=3D"mailto:gabilm@um.es" =
class=3D"">gabilm@um.es</a>&gt;, "Rafa Marin-Lopez" &lt;<a =
href=3D"mailto:rafa@um.es" class=3D"">rafa@um.es</a>&gt;<br =
class=3D""></span></div><br class=3D""><div class=3D""><div class=3D""><br=
 class=3D"">A new version of I-D, =
draft-ietf-i2nsf-sdn-ipsec-flow-protection-11.txt<br class=3D"">has been =
successfully submitted by Rafa Marin-Lopez and posted to the<br =
class=3D"">IETF repository.<br class=3D""><br class=3D"">Name:<span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</span><span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</span>draft-ietf-i2nsf-sdn-ipsec-flow-protection<br =
class=3D"">Revision:<span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</span>11<br class=3D"">Title:<span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</span><span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</span>Software-Defined Networking (SDN)-based IPsec Flow Protection<br =
class=3D"">Document date:<span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</span>2020-10-22<br =
class=3D"">Group:<span class=3D"Apple-tab-span" style=3D"white-space:pre">=
	</span><span class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</span>i2nsf<br class=3D"">Pages:<span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</span><span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</span>92<br class=3D"">URL: =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a =
href=3D"https://www.ietf.org/archive/id/draft-ietf-i2nsf-sdn-ipsec-flow-pr=
otection-11.txt" =
class=3D"">https://www.ietf.org/archive/id/draft-ietf-i2nsf-sdn-ipsec-flow=
-protection-11.txt</a><br class=3D"">Status: =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a =
href=3D"https://datatracker.ietf.org/doc/draft-ietf-i2nsf-sdn-ipsec-flow-p=
rotection/" =
class=3D"">https://datatracker.ietf.org/doc/draft-ietf-i2nsf-sdn-ipsec-flo=
w-protection/</a><br class=3D"">Htmlized: =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a =
href=3D"https://datatracker.ietf.org/doc/html/draft-ietf-i2nsf-sdn-ipsec-f=
low-protection" =
class=3D"">https://datatracker.ietf.org/doc/html/draft-ietf-i2nsf-sdn-ipse=
c-flow-protection</a><br class=3D"">Htmlized: =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a =
href=3D"https://tools.ietf.org/html/draft-ietf-i2nsf-sdn-ipsec-flow-protec=
tion-11" =
class=3D"">https://tools.ietf.org/html/draft-ietf-i2nsf-sdn-ipsec-flow-pro=
tection-11</a><br class=3D"">Diff: =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a =
href=3D"https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-i2nsf-sdn-ipsec-flo=
w-protection-11" =
class=3D"">https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-i2nsf-sdn-ipsec-=
flow-protection-11</a><br class=3D""><br class=3D"">Abstract:<br =
class=3D""> &nbsp;&nbsp;This document describes how to provide =
IPsec-based flow protection<br class=3D""> &nbsp;&nbsp;(integrity and =
confidentiality) by means of an Interface to Network<br class=3D""> =
&nbsp;&nbsp;Security Function (I2NSF) controller. &nbsp;It considers two =
main well-<br class=3D""> &nbsp;&nbsp;known scenarios in IPsec: (i) =
gateway-to-gateway and (ii) host-to-<br class=3D""> &nbsp;&nbsp;host. =
&nbsp;The service described in this document allows the<br class=3D""> =
&nbsp;&nbsp;configuration and monitoring of IPsec Security Associations =
(SAs)<br class=3D""> &nbsp;&nbsp;from a I2NSF Controller to one or =
several flow-based Network Security<br class=3D""> &nbsp;&nbsp;Functions =
(NSFs) that rely on IPsec to protect data traffic.<br class=3D""><br =
class=3D""> &nbsp;&nbsp;The document focuses on the I2NSF NSF-facing =
interface by providing<br class=3D""> &nbsp;&nbsp;YANG data models for =
configuring the IPsec databases (SPD, SAD, PAD)<br class=3D""> =
&nbsp;&nbsp;and IKEv2. &nbsp;This allows IPsec SA establishment with =
minimal<br class=3D""> &nbsp;&nbsp;intervention by the network =
administrator. &nbsp;It does not define any<br class=3D""> =
&nbsp;&nbsp;new protocol.<br class=3D""><br class=3D""><br class=3D""><br =
class=3D""><br class=3D"">Please note that it may take a couple of =
minutes from the time of submission<br class=3D"">until the htmlized =
version and diff are available at <a href=3D"http://tools.ietf.org" =
class=3D"">tools.ietf.org</a>.<br class=3D""><br class=3D"">The IETF =
Secretariat<br class=3D""><br class=3D""><br =
class=3D""></div></div></blockquote></div><br class=3D""><div class=3D"">
<div style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space;" class=3D""><div style=3D"color: =
rgb(0, 0, 0); font-family: Courier; font-size: 16px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
orphans: auto; text-align: start; text-indent: 0px; text-transform: =
none; white-space: normal; widows: auto; word-spacing: 0px; =
-webkit-text-stroke-width: =
0px;">-------------------------------------------------------<br =
class=3D"">Rafa Marin-Lopez, PhD<br class=3D"">Dept. Information =
and&nbsp;Communications&nbsp;Engineering (DIIC)<br class=3D"">Faculty of =
Computer&nbsp;Science-University of&nbsp;Murcia<br class=3D"">30100 =
Murcia - Spain<br class=3D"">Telf: +34868888501 Fax:&nbsp;+34868884151 =
<a href=3D"mailto:rafa@um.es" class=3D"">e-mail:&nbsp;rafa@um.es</a><br =
class=3D"">-------------------------------------------------------</div><d=
iv style=3D"color: rgb(0, 0, 0); font-family: Courier; font-size: 16px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; orphans: auto; text-align: start; text-indent: =
0px; text-transform: none; white-space: normal; widows: auto; =
word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=3D""><br =
class=3D""></div><br class=3D"Apple-interchange-newline"></div><br =
class=3D"Apple-interchange-newline">
</div>

<br class=3D""></div></body></html>=

--Apple-Mail=_EFEC2F4A-0BF7-418B-9A9A-7040280BE044--


From nobody Fri Oct 23 19:29:44 2020
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 0BF063A0C45 for <i2nsf@ietfa.amsl.com>; Fri, 23 Oct 2020 19:29:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.454
X-Spam-Level: 
X-Spam-Status: No, score=-0.454 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, T_HK_NAME_FM_MR_MRS=0.01, 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 FuCT8RicicAx for <i2nsf@ietfa.amsl.com>; Fri, 23 Oct 2020 19:29:39 -0700 (PDT)
Received: from mail-lf1-x129.google.com (mail-lf1-x129.google.com [IPv6:2a00:1450:4864:20::129]) (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 4DEB33A0C43 for <i2nsf@ietf.org>; Fri, 23 Oct 2020 19:29:39 -0700 (PDT)
Received: by mail-lf1-x129.google.com with SMTP id v6so4352108lfa.13 for <i2nsf@ietf.org>; Fri, 23 Oct 2020 19:29:39 -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=koYpaYTlAidsUwe/Y/JFK0iIx5hqqn/F+qjXcfO2SrQ=; b=t0YFvIMwzhINDdbxpYUmrpCPkQA2RBJD1vroIeVuF34HemRPrmJlrdb+49M1iWXM9Y LcJ00BiIXSGtqUSzPKNK2IF0UN3KFv5Yy0AVMtzUmOQm79tESO7I3JVE0D5iLqkgGlqy zJ77p/9hcm0/CIh99CB5+dI0C5Iq8W5ypbYwHsKzOENbirjn8hTGOd9rkofr8qLuS0tK cJ8onKBNal9dkmaT9kqONyVrNg1n3hUQk6e/HH0tvdy2fjRJn5P+C0kVCJn/9YvLUB/w WAGn2xgBtmoZgBYZeZCKRLPapJkaAT56gbjzXe3n3zy1zar8uZWT+irT5lqipG/Wq3cs KacA==
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=koYpaYTlAidsUwe/Y/JFK0iIx5hqqn/F+qjXcfO2SrQ=; b=VtkmCpmXyFa5CI/6Uhv0KYDldsOV1VlKiwKRbM54yrOxj1CxnZ77rN7hFKUzmxL/Zc BhxYO7Y/oAdqtWjwYIlTFus8GcBrBTZZdTpK5iu1Ml/JanZIe7z/W81AHTyZ5zbfZVKZ wnCHHH2N9kuApXZqZy7hJvOC1KFV/L7iVAoMzXzA0cDga5FWsOc8+dFUSPzJPVouM3K0 Sosno87OYdQuhjSyiKyNhw2njdTahzRG97d2/GZNFztn/4tAqnRPmW5+DnDo7xb90YS2 wfjR/DkiiK93LZy9Oef1cGrnY0P+QCUB/oYMHpnTtAU7nJigiv2kVHKkgDzmQvPUPFWT LXUA==
X-Gm-Message-State: AOAM532yI/ByvUEdWai7RGEISY502JWmJ4deN0Z+OY6T7LebM6fcyIOQ RtPKvvy83nxn9sz8S0n+Ohgzw515ygUkob+Pc+4=
X-Google-Smtp-Source: ABdhPJz8IyWd9mkFfTAu0vuAmHxR/V62iRdpNZKu5ZH9S7lxxZCT+6TScC68Jlp2JTUydwFhTpMfZ+IFRrmOlvFWCJY=
X-Received: by 2002:a19:e03:: with SMTP id 3mr1807041lfo.335.1603506577189; Fri, 23 Oct 2020 19:29:37 -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>
In-Reply-To: <CAPK2DexF7qwLCYh_mCFiHVBPaT=ccX1TBTeRUt+w8sDNauGfPQ@mail.gmail.com>
From: "Mr. Jaehoon Paul Jeong" <jaehoon.paul@gmail.com>
Date: Sat, 24 Oct 2020 11:29:00 +0900
Message-ID: <CAPK2DezD84CwB1E6tNgrn7AEPiypnYRtBRdZcCvVR1CWEMK6sA@mail.gmail.com>
To: Linda <dunbar.ll@gmail.com>, Yoav Nir <ynir.ietf@gmail.com>
Cc: "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="000000000000edae3505b261779c"
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2nsf/kPld15kgGJwBRe_UgPpb7ZDpPPE>
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 02:29:43 -0000

--000000000000edae3505b261779c
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

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=EB=85=84 10=EC=9B=94 10=EC=9D=BC (=ED=86=A0) =EC=98=A4=EC=A0=84 10:2=
0, Linda <dunbar.ll@gmail.com>=EB=8B=98=EC=9D=B4 =EC=9E=91=EC=84=B1:
>
>> Yes
>> Linda
>>
>> Sent from my iPhone
>>
>> On Oct 9, 2020, at 7:55 PM, Mr. Jaehoon Paul Jeong <
>> jaehoon.paul@gmail.com> wrote:
>>
>> =EF=BB=BF
>> 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 Mo=
del
>> Draft.
>>
>> Is it correct?
>>
>> Thanks.
>>
>> Best Regards,
>> Paul
>>
>> 2020=EB=85=84 10=EC=9B=94 9=EC=9D=BC (=EA=B8=88) =EC=98=A4=ED=9B=84 11:5=
8, Linda Dunbar <linda.dunbar@futurewei.com>=EB=8B=98=EC=9D=B4
>> =EC=9E=91=EC=84=B1:
>>
>>> I2NSF WG,
>>>
>>>
>>>
>>> Correction:
>>>
>>>
>>>
>>> There has been NO object to the Author=E2=80=99s request for sunsetting=
 the
>>> draft-ietf-i2nsf-capability-5.
>>>
>>>
>>>
>>> We have marked the draft as =E2=80=9CDEAD=E2=80=9D 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 Capabilit=
ies
>>> 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=E2=80=99s request for sunset=
ting the
>>>  draft-ietf-i2nsf-capability-05.
>>>
>>>
>>>
>>> Authors of the draft-ietf-i2nsf-capability-data-model: please remove th=
e
>>> reference to the Capability Information Model and upload a new draft. W=
e
>>> 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 manipulati=
ng
>>> high-level policy expressions.  The capability data model has been evol=
ving
>>> 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 i=
t is
>>> better to let the capability information model to be withdrawn. For the
>>> content in the information model still relevant to I2NSF Capability Dat=
a
>>> Model, they should be merged into the Capability Data Model.
>>>
>>>
>>>
>>> Is there any objection from the WG?  If we don=E2=80=99t hear any objec=
tion 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=E2=80=99d prefer the second option, as it seems more straightforward =
and
>>> natural to me, and in parallel would like you to consider the idea of a=
n
>>> I2NSF extension allowing us to reuse the capability model for
>>> policy-control transformation, and to incorporate the attestation matte=
rs
>>> 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=3Dhttps%3A%2F%2Fww=
w.linkedin.com%2Fin%2Fdr2lopez%2F&data=3D02%7C01%7Clinda.dunbar%40futurewei=
.com%7C08a48858d7bd4d843a6e08d85f47b438%7C0fee8ff2a3b240189c753a1d5591fedc%=
7C1%7C0%7C637364108864949633&sdata=3DROR4%2FyD1WqWDb1rCbJx3ERqTiMCQ92ibkyz2=
6kYZdD8%3D&reserved=3D0>
>>>
>>>
>>>
>>>
>>> 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 =E2=80=9Cthe capability dat=
a model was
>>> evolving in a quite reasonable and pragmatic way, including running cod=
e at
>>> the hackathons=E2=80=9D.
>>>
>>>
>>>
>>> Looks like Eric Vyncke still wants the information model to be fixed to
>>> clear his =E2=80=9CDISCUSS=E2=80=9D ballot.
>>>
>>> How about the following steps:
>>>
>>> -          Ask Roman=E2=80=99s advice if we can simplify the Informatio=
n 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 thin=
k
>>> the best solution was to leave this draft to fade away. First, I was no=
t
>>> (have not been yet) able to find a solution to most of Roman=E2=80=99s =
comments
>>> without totally rewriting most, if not all, of the document.  Second, t=
he
>>> 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 positio=
n
>>> 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 addre=
ssed
>>> in the capability data model and the other data models produced in I2NS=
F. I
>>> believe there is an opportunity for accomplishing policy-capability
>>> bridging, using as foundation the current capability model, though it s=
eems
>>> to me that this task would require some time to consolidate and therefo=
re
>>> imply an extension of the I2NSF lifetime. I would like to know your
>>> position(*) about such an extension,  that could also become an opportu=
nity
>>> to work in other matters related to attestation (in the light of the wo=
rk
>>> in RATS and the MUD initiative within the Ops Area) and accounting.
>>>
>>>
>>>
>>> Be goode,
>>>
>>>
>>>
>>> (*) I assume you are in favor, Paul. But I=E2=80=99d like to get Linda=
=E2=80=99s, Yoav=E2=80=99s
>>> and Roman=E2=80=99s 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=3Dhttps%3A%2F%2Fww=
w.linkedin.com%2Fin%2Fdr2lopez%2F&data=3D02%7C01%7Clinda.dunbar%40futurewei=
.com%7C08a48858d7bd4d843a6e08d85f47b438%7C0fee8ff2a3b240189c753a1d5591fedc%=
7C1%7C0%7C637364108864949633&sdata=3DROR4%2FyD1WqWDb1rCbJx3ERqTiMCQ92ibkyz2=
6kYZdD8%3D&reserved=3D0>
>>>
>>>
>>>
>>>
>>> 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 Fran=
k
>>> (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=EB=85=84 9=EC=9B=94 17=EC=9D=BC (=EB=AA=A9) =EC=98=A4=EC=A0=84 3:4=
4, Linda Dunbar <linda.dunbar@futurewei.com>=EB=8B=98=EC=9D=B4 =EC=9E=91=EC=
=84=B1
>>> :
>>>
>>> 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 draf=
t.
>>>
>>>
>>>
>>>
>>>
>>> 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 Roma=
n
>>> Danyliw's review comments  as a co-editor?
>>>
>>>
>>> https://datatracker.ietf.org/doc/draft-ietf-i2nsf-capability/?include_t=
ext=3D1
>>> <https://nam11.safelinks.protection.outlook.com/?url=3Dhttps%3A%2F%2Fda=
tatracker.ietf.org%2Fdoc%2Fdraft-ietf-i2nsf-capability%2F%3Finclude_text%3D=
1&data=3D02%7C01%7Clinda.dunbar%40futurewei.com%7C08a48858d7bd4d843a6e08d85=
f47b438%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C637364108864959626&sda=
ta=3DGUrbaYu2Q4N1YNUUet2oVRPqbynA78cSBTf%2FBeSCY44%3D&reserved=3D0>
>>>
>>>
>>>
>>> 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=C3=B3n privilegiada o confidencial y es para u=
so
>>> exclusivo de la persona o entidad de destino. Si no es usted. el
>>> destinatario indicado, queda notificado de que la lectura, utilizaci=C3=
=B3n,
>>> divulgaci=C3=B3n y/o copia sin autorizaci=C3=B3n puede estar prohibida =
en virtud de
>>> la legislaci=C3=B3n vigente. Si ha recibido este mensaje por error, le =
rogamos
>>> que nos lo comunique inmediatamente por esta misma v=C3=ADa y proceda a=
 su
>>> destrucci=C3=B3n.
>>>
>>> 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 recei=
ved
>>> this transmission in error, do not read it. Please immediately reply to=
 the
>>> sender that you have received this communication in error and then dele=
te
>>> it.
>>>
>>> Esta mensagem e seus anexos se dirigem exclusivamente ao seu
>>> destinat=C3=A1rio, pode conter informa=C3=A7=C3=A3o privilegiada ou con=
fidencial e =C3=A9 para
>>> uso exclusivo da pessoa ou entidade de destino. Se n=C3=A3o =C3=A9 voss=
a senhoria o
>>> destinat=C3=A1rio indicado, fica notificado de que a leitura, utiliza=
=C3=A7=C3=A3o,
>>> divulga=C3=A7=C3=A3o e/ou c=C3=B3pia sem autoriza=C3=A7=C3=A3o pode est=
ar proibida em virtude da
>>> legisla=C3=A7=C3=A3o vigente. Se recebeu esta mensagem por erro, rogamo=
s-lhe que nos
>>> o comunique imediatamente por esta mesma via e proceda a sua destrui=C3=
=A7=C3=A3o
>>>
>>>
>>> ------------------------------
>>>
>>>
>>> Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario=
,
>>> puede contener informaci=C3=B3n privilegiada o confidencial y es para u=
so
>>> exclusivo de la persona o entidad de destino. Si no es usted. el
>>> destinatario indicado, queda notificado de que la lectura, utilizaci=C3=
=B3n,
>>> divulgaci=C3=B3n y/o copia sin autorizaci=C3=B3n puede estar prohibida =
en virtud de
>>> la legislaci=C3=B3n vigente. Si ha recibido este mensaje por error, le =
rogamos
>>> que nos lo comunique inmediatamente por esta misma v=C3=ADa y proceda a=
 su
>>> destrucci=C3=B3n.
>>>
>>> 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 recei=
ved
>>> this transmission in error, do not read it. Please immediately reply to=
 the
>>> sender that you have received this communication in error and then dele=
te
>>> it.
>>>
>>> Esta mensagem e seus anexos se dirigem exclusivamente ao seu
>>> destinat=C3=A1rio, pode conter informa=C3=A7=C3=A3o privilegiada ou con=
fidencial e =C3=A9 para
>>> uso exclusivo da pessoa ou entidade de destino. Se n=C3=A3o =C3=A9 voss=
a senhoria o
>>> destinat=C3=A1rio indicado, fica notificado de que a leitura, utiliza=
=C3=A7=C3=A3o,
>>> divulga=C3=A7=C3=A3o e/ou c=C3=B3pia sem autoriza=C3=A7=C3=A3o pode est=
ar proibida em virtude da
>>> legisla=C3=A7=C3=A3o vigente. Se recebeu esta mensagem por erro, rogamo=
s-lhe que nos
>>> o comunique imediatamente por esta mesma via e proceda a sua destrui=C3=
=A7=C3=A3o
>>> _______________________________________________
>>> 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
>>
>>

--000000000000edae3505b261779c
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr">Hi Linda and Yoav,<div>I need more time t=
o merge the information model and data model for=C2=A0</div><div>draft-ietf=
-i2nsf-capability-data-model along with the reflection of the IESG&#39;s co=
mments:<br></div><div><a href=3D"https://datatracker.ietf.org/doc/draft-iet=
f-i2nsf-capability-data-model/">https://datatracker.ietf.org/doc/draft-ietf=
-i2nsf-capability-data-model/</a><br></div><div><br></div><div>I will try t=
o do the merging=C2=A0and the reflection of the comments of the IESG by IET=
F-109 I-D due (11/02/2020).</div><div><br></div><div>Thanks.</div><div><br>=
</div><div>Best Regards,</div><div>Paul</div><div><br></div></div><br><div =
class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Sat, Oct 10,=
 2020 at 10:33 AM Mr. Jaehoon Paul Jeong &lt;<a href=3D"mailto:jaehoon.paul=
@gmail.com">jaehoon.paul@gmail.com</a>&gt; wrote:<br></div><blockquote clas=
s=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid r=
gb(204,204,204);padding-left:1ex"><div dir=3D"auto">Linda,<div dir=3D"auto"=
>I see.</div><div dir=3D"auto"><br></div><div dir=3D"auto">I will do the me=
rging.</div><div dir=3D"auto"><br></div><div dir=3D"auto">Thanks.</div><div=
 dir=3D"auto"><br></div><div dir=3D"auto">Best Regards,</div><div dir=3D"au=
to">Paul</div></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=
=3D"gmail_attr">2020=EB=85=84 10=EC=9B=94 10=EC=9D=BC (=ED=86=A0) =EC=98=A4=
=EC=A0=84 10:20, Linda &lt;<a href=3D"mailto:dunbar.ll@gmail.com" target=3D=
"_blank">dunbar.ll@gmail.com</a>&gt;=EB=8B=98=EC=9D=B4 =EC=9E=91=EC=84=B1:<=
br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8e=
x;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir=3D"auto=
">Yes=C2=A0<div>Linda<br><br><div dir=3D"ltr">Sent from my iPhone</div><div=
 dir=3D"ltr"><br><blockquote type=3D"cite">On Oct 9, 2020, at 7:55 PM, Mr. =
Jaehoon Paul Jeong &lt;<a href=3D"mailto:jaehoon.paul@gmail.com" rel=3D"nor=
eferrer" target=3D"_blank">jaehoon.paul@gmail.com</a>&gt; wrote:<br><br></b=
lockquote></div><blockquote type=3D"cite"><div dir=3D"ltr">=EF=BB=BF<div di=
r=3D"auto"><div>Hi Linda,</div><div dir=3D"auto">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.</div><div dir=3D"auto"><br=
></div><div dir=3D"auto">Is it correct?</div><div dir=3D"auto"><br></div><d=
iv dir=3D"auto">Thanks.</div><div dir=3D"auto"><br></div><div dir=3D"auto">=
Best Regards,</div><div dir=3D"auto">Paul</div><div dir=3D"auto"><br><div c=
lass=3D"gmail_quote" dir=3D"auto"><div dir=3D"ltr" class=3D"gmail_attr">202=
0=EB=85=84 10=EC=9B=94 9=EC=9D=BC (=EA=B8=88) =EC=98=A4=ED=9B=84 11:58, Lin=
da Dunbar &lt;<a href=3D"mailto:linda.dunbar@futurewei.com" rel=3D"noreferr=
er" target=3D"_blank">linda.dunbar@futurewei.com</a>&gt;=EB=8B=98=EC=9D=B4 =
=EC=9E=91=EC=84=B1:<br></div><blockquote class=3D"gmail_quote" style=3D"mar=
gin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1=
ex">





<div lang=3D"EN-US">
<div>
<p class=3D"MsoNormal">I2NSF WG, <u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">Correction: <u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">There has been NO object to the Author=E2=80=99s req=
uest for sunsetting the draft-ietf-i2nsf-capability-5.
<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">We have marked the draft as =E2=80=9CDEAD=E2=80=9D i=
n the WG status. <u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">Many thanks to the authors for putting the effort in=
 this draft for kickstarting all the data models in I2NSF WG.
<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">Linda &amp; Yoav<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<div>
<div style=3D"border-right:none;border-bottom:none;border-left:none;border-=
top:1pt solid rgb(225,225,225);padding:3pt 0in 0in">
<p class=3D"MsoNormal"><b>From:</b> Linda Dunbar <br>
<b>Sent:</b> Thursday, October 8, 2020 4:36 PM<br>
<b>To:</b> <a href=3D"mailto:i2nsf@ietf.org" rel=3D"noreferrer noreferrer" =
target=3D"_blank">i2nsf@ietf.org</a><br>
<b>Subject:</b> draft-ietf-i2nsf-capability-05 is officially removed from I=
2NSF WG ( was RE: Is there any objection of sunset the I2NSF Capabilities I=
nformation Model Draft and merge the relevant information to the I2NSF Capa=
bility Data model draft?
<u></u><u></u></p>
</div>
</div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">I2nsf WG, <u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">There has been any objection to the Author=E2=80=99s=
 request for sunsetting the =C2=A0draft-ietf-i2nsf-capability-05.
<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">Authors of the draft-ietf-i2nsf-capability-data-mode=
l: please remove the reference to the Capability Information Model and uplo=
ad a new draft. We can ask IESG to re-review it.
<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">Thank you very much. <u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">Linda &amp; Yoav. <u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<div>
<div style=3D"border-right:none;border-bottom:none;border-left:none;border-=
top:1pt solid rgb(225,225,225);padding:3pt 0in 0in">
<p class=3D"MsoNormal"><b>From:</b> Linda Dunbar <br>
<b>Sent:</b> Monday, September 28, 2020 11:00 AM<br>
<b>To:</b> <a href=3D"mailto:i2nsf@ietf.org" rel=3D"noreferrer noreferrer" =
target=3D"_blank">i2nsf@ietf.org</a><br>
<b>Subject:</b> Is there any objection of sunset the I2NSF Capabilities Inf=
ormation Model Draft and merge the relevant information to the I2NSF Capabi=
lity Data model draft?
<u></u><u></u></p>
</div>
</div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">I2NSF WG, <u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">As Diego has expressed that the original I2NSF capab=
ility information model was based on a policy expression calculus suitable =
for manipulating high-level policy expressions.=C2=A0 The capability data m=
odel has been evolving in a quite reasonable
 and pragmatic way, including running code at the hackathons.<u></u><u></u>=
</p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">The I2NSF Capability Information Model has fulfilled=
 its purpose of kickstarting and guiding the data model, and the authors be=
lieve that it is better to let the capability information model to be withd=
rawn. For the content in the information
 model still relevant to I2NSF Capability Data Model, they should be merged=
 into the Capability Data Model.
<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">Is there any objection from the WG?=C2=A0 If we don=
=E2=80=99t hear any objection by Oct 5, we will change the status of the dr=
aft.
<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">Cheers, =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0
<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">Linda &amp; Yoav<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<div>
<div style=3D"border-right:none;border-bottom:none;border-left:none;border-=
top:1pt solid rgb(225,225,225);padding:3pt 0in 0in">
<p class=3D"MsoNormal"><b>From:</b> Diego R. Lopez &lt;<a href=3D"mailto:di=
ego.r.lopez@telefonica.com" rel=3D"noreferrer noreferrer" target=3D"_blank"=
>diego.r.lopez@telefonica.com</a>&gt;
<br>
<b>Sent:</b> Tuesday, September 22, 2020 5:35 PM<br>
<b>To:</b> Linda Dunbar &lt;<a href=3D"mailto:linda.dunbar@futurewei.com" r=
el=3D"noreferrer noreferrer" target=3D"_blank">linda.dunbar@futurewei.com</=
a>&gt;; Mr. Jaehoon Paul Jeong &lt;<a href=3D"mailto:jaehoon.paul@gmail.com=
" rel=3D"noreferrer noreferrer" target=3D"_blank">jaehoon.paul@gmail.com</a=
>&gt;<br>
<b>Cc:</b> Xialiang (Frank) &lt;<a href=3D"mailto:frank.xialiang@huawei.com=
" rel=3D"noreferrer noreferrer" target=3D"_blank">frank.xialiang@huawei.com=
</a>&gt;; Yoav Nir &lt;<a href=3D"mailto:ynir.ietf@gmail.com" rel=3D"norefe=
rrer noreferrer" target=3D"_blank">ynir.ietf@gmail.com</a>&gt;; John Strass=
ner &lt;<a href=3D"mailto:John.sc.Strassner@huawei.com" rel=3D"noreferrer n=
oreferrer" target=3D"_blank">John.sc.Strassner@huawei.com</a>&gt;;
 Aldo Basile &lt;<a href=3D"mailto:cataldo.basile@polito.it" rel=3D"norefer=
rer noreferrer" target=3D"_blank">cataldo.basile@polito.it</a>&gt;; Roman D=
anyliw &lt;<a href=3D"mailto:rdd@cert.org" rel=3D"noreferrer noreferrer" ta=
rget=3D"_blank">rdd@cert.org</a>&gt;<br>
<b>Subject:</b> Re: Offer for Revision Help for I2NSF NSFs Capabilities Inf=
ormation Model Draft<u></u><u></u></p>
</div>
</div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal"><span lang=3D"ES" style=3D"font-size:10pt">Hi Linda,=
<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"ES" style=3D"font-size:10pt"><u></u>=
=C2=A0<u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10pt">I=E2=80=99d prefer th=
e 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 allowin=
g us to reuse the
 capability model for policy-control transformation, and to incorporate the=
 attestation matters you know I was so much interested in.<u></u><u></u></s=
pan></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10pt"><u></u>=C2=A0<u></u><=
/span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10pt">Be goode,<u></u><u></=
u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10pt"><u></u>=C2=A0<u></u><=
/span></p>
<div>
<p class=3D"MsoNormal"><span lang=3D"ES" style=3D"font-size:10pt">--<u></u>=
<u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"ES" style=3D"font-size:10pt">&quot;Est=
a vez no fallaremos, Doctor Infierno&quot;<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"ES" style=3D"font-size:10pt">=C2=A0<u>=
</u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"ES" style=3D"font-size:10pt">Dr Diego =
R. Lopez<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"ES" style=3D"font-size:10pt">Telefonic=
a I+D<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"ES" style=3D"font-size:10pt"><a href=
=3D"https://nam11.safelinks.protection.outlook.com/?url=3Dhttps%3A%2F%2Fwww=
.linkedin.com%2Fin%2Fdr2lopez%2F&amp;data=3D02%7C01%7Clinda.dunbar%40future=
wei.com%7C08a48858d7bd4d843a6e08d85f47b438%7C0fee8ff2a3b240189c753a1d5591fe=
dc%7C1%7C0%7C637364108864949633&amp;sdata=3DROR4%2FyD1WqWDb1rCbJx3ERqTiMCQ9=
2ibkyz26kYZdD8%3D&amp;reserved=3D0" rel=3D"noreferrer noreferrer" target=3D=
"_blank"><span style=3D"color:rgb(5,99,193)">https://www.linkedin.com/in/dr=
2lopez/</span></a>=C2=A0<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"ES" style=3D"font-size:10pt">=C2=A0<u>=
</u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"ES" style=3D"font-size:10pt">e-mail:=
=C2=A0</span><span lang=3D"EN-GB" style=3D"font-size:10pt"><a href=3D"mailt=
o:diego.r.lopez@telefonica.com" rel=3D"noreferrer noreferrer" target=3D"_bl=
ank"><span lang=3D"ES" style=3D"color:rgb(5,99,193)">diego.r.lopez@telefoni=
ca.com</span></a></span><span lang=3D"ES" style=3D"font-size:10pt"><u></u><=
u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB" style=3D"font-size:10pt">Tel:=
=C2=A0=C2=A0=C2=A0 =C2=A0=C2=A0=C2=A0=C2=A0 +34 913 129 041<u></u><u></u></=
span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB" style=3D"font-size:10pt">Mobile=
: =C2=A0+34 682 051 091<u></u><u></u></span></p>
</div>
<p class=3D"MsoNormal"><span lang=3D"EN-GB" style=3D"font-size:10pt">------=
----------------------------</span><span style=3D"font-size:10pt"><u></u><u=
></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10pt"><u></u>=C2=A0<u></u><=
/span></p>
<div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:0.5in">On 22/09/2020, 18:01, &q=
uot;Linda Dunbar&quot; &lt;<a href=3D"mailto:linda.dunbar@futurewei.com" re=
l=3D"noreferrer noreferrer" target=3D"_blank">linda.dunbar@futurewei.com</a=
>&gt; wrote:<u></u><u></u></p>
</div>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:0.5in"><u></u>=C2=A0<u></u></p>
</div>
<p class=3D"MsoNormal" style=3D"margin-left:0.5in">Diego: <u></u><u></u></p=
>
<p class=3D"MsoNormal" style=3D"margin-left:0.5in">=C2=A0<u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:0.5in">Thank you very much for =
the reflection of the Capabilities Information Model Draft. Agree with your=
 statement that =E2=80=9Cthe capability data model was evolving in a quite =
reasonable and pragmatic way, including running
 code at the hackathons=E2=80=9D. <u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:0.5in">=C2=A0<u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:0.5in">Looks like Eric Vyncke s=
till wants the information model to be fixed to clear his =E2=80=9CDISCUSS=
=E2=80=9D ballot.
<u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:0.5in">How about the following =
steps:<u></u><u></u></p>
<p style=3D"margin-left:1in">
<u></u><span>-<span style=3D"font:7pt &quot;Times New Roman&quot;">=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0
</span></span><u></u>Ask Roman=E2=80=99s advice if we can simplify the Info=
rmation Model mainly to reflect what has been in the Data Model.<u></u><u><=
/u></p>
<p style=3D"margin-left:1in">
<u></u><span>-<span style=3D"font:7pt &quot;Times New Roman&quot;">=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0
</span></span><u></u>Or, drop the Information model draft and remove the re=
fence to the draft, but Roman has to convince Eric to agree not having the =
information model.
<u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:0.5in">=C2=A0<u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:0.5in">What do you think? <u></=
u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:0.5in">=C2=A0<u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:0.5in">Linda<u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:0.5in">=C2=A0<u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:0.5in">=C2=A0<u></u><u></u></p>
<div>
<div style=3D"border-right:none;border-bottom:none;border-left:none;border-=
top:1pt solid rgb(225,225,225);padding:3pt 0in 0in">
<p class=3D"MsoNormal" style=3D"margin-left:0.5in"><b>From:</b> Diego R. Lo=
pez &lt;<a href=3D"mailto:diego.r.lopez@telefonica.com" rel=3D"noreferrer n=
oreferrer" target=3D"_blank">diego.r.lopez@telefonica.com</a>&gt;
<br>
<b>Sent:</b> Tuesday, September 22, 2020 9:50 AM<br>
<b>To:</b> Mr. Jaehoon Paul Jeong &lt;<a href=3D"mailto:jaehoon.paul@gmail.=
com" rel=3D"noreferrer noreferrer" target=3D"_blank">jaehoon.paul@gmail.com=
</a>&gt;; Linda Dunbar &lt;<a href=3D"mailto:linda.dunbar@futurewei.com" re=
l=3D"noreferrer noreferrer" target=3D"_blank">linda.dunbar@futurewei.com</a=
>&gt;<br>
<b>Cc:</b> Xialiang (Frank) &lt;<a href=3D"mailto:frank.xialiang@huawei.com=
" rel=3D"noreferrer noreferrer" target=3D"_blank">frank.xialiang@huawei.com=
</a>&gt;; Yoav Nir &lt;<a href=3D"mailto:ynir.ietf@gmail.com" rel=3D"norefe=
rrer noreferrer" target=3D"_blank">ynir.ietf@gmail.com</a>&gt;; John Strass=
ner &lt;<a href=3D"mailto:John.sc.Strassner@huawei.com" rel=3D"noreferrer n=
oreferrer" target=3D"_blank">John.sc.Strassner@huawei.com</a>&gt;;
 Aldo Basile &lt;<a href=3D"mailto:cataldo.basile@polito.it" rel=3D"norefer=
rer noreferrer" target=3D"_blank">cataldo.basile@polito.it</a>&gt;; Roman D=
anyliw &lt;<a href=3D"mailto:rdd@cert.org" rel=3D"noreferrer noreferrer" ta=
rget=3D"_blank">rdd@cert.org</a>&gt;<br>
<b>Subject:</b> Re: Offer for Revision Help for I2NSF NSFs Capabilities Inf=
ormation Model Draft<u></u><u></u></p>
</div>
</div>
<p class=3D"MsoNormal" style=3D"margin-left:0.5in">=C2=A0<u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:0.5in"><span><span style=3D"fon=
t-size:10pt">H</span></span><span><span lang=3D"ES" style=3D"font-size:10pt=
">i Paul,</span></span><u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:0.5in"><span><span lang=3D"ES" =
style=3D"font-size:10pt">=C2=A0</span></span><u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:0.5in"><span><span style=3D"fon=
t-size:10pt">Before you go for it, let me share with you some reflections o=
n the state of the draft, in the spirit of what I replied to Eric Vyncke.</=
span></span><u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:0.5in"><span><span style=3D"fon=
t-size:10pt">=C2=A0</span></span><u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:0.5in"><span style=3D"font-size=
:10pt">I must confess there has been a combination of events that made me t=
hink the best solution was to leave this draft to fade away. First, I was n=
ot (have not
 been yet) able to find a solution to most of Roman=E2=80=99s comments with=
out totally rewriting most, if not all, of the document.=C2=A0 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 mo=
del, 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 inf=
o model draft.</span><u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:0.5in"><span style=3D"font-size=
:10pt">=C2=A0</span><u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:0.5in"><span style=3D"font-size=
:10pt">As I told Eric, I believe the current capability model has a powerfu=
l (though probably not yet complete) calculus for policy description and va=
lidation,
 but not directly related to the management mechanisms addressed in the cap=
ability data model and the other data models produced in I2NSF. I believe t=
here 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 con=
solidate and therefore imply an extension of the I2NSF lifetime. I would li=
ke to know your position(*) about such an extension, =C2=A0that could also =
become an opportunity to work in other
 matters related to attestation (in the light of the work in RATS and the M=
UD initiative within the Ops Area) and accounting.</span><u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:0.5in"><span style=3D"font-size=
:10pt">=C2=A0</span><u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:0.5in"><span style=3D"font-size=
:10pt">Be goode,</span><u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:0.5in"><span style=3D"font-size=
:10pt">=C2=A0</span><u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:0.5in"><span style=3D"font-size=
:10pt">(*) I assume you are in favor, Paul. But I=E2=80=99d like to get Lin=
da=E2=80=99s, Yoav=E2=80=99s and Roman=E2=80=99s ideas, as well as the avai=
lability to work on this from Frank, John
 and Aldo.</span><u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:0.5in"><span style=3D"font-size=
:10pt">=C2=A0</span><u></u><u></u></p>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:0.5in"><span style=3D"font-size=
:10pt">--</span><u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:0.5in"><span lang=3D"ES" style=
=3D"font-size:10pt">&quot;Esta vez no fallaremos, Doctor Infierno&quot;</sp=
an><u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:0.5in"><span lang=3D"ES" style=
=3D"font-size:10pt">=C2=A0</span><u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:0.5in"><span lang=3D"ES" style=
=3D"font-size:10pt">Dr Diego R. Lopez</span><u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:0.5in"><span lang=3D"ES" style=
=3D"font-size:10pt">Telefonica I+D</span><u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:0.5in"><span lang=3D"ES" style=
=3D"font-size:10pt"><a href=3D"https://nam11.safelinks.protection.outlook.c=
om/?url=3Dhttps%3A%2F%2Fwww.linkedin.com%2Fin%2Fdr2lopez%2F&amp;data=3D02%7=
C01%7Clinda.dunbar%40futurewei.com%7C08a48858d7bd4d843a6e08d85f47b438%7C0fe=
e8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C637364108864949633&amp;sdata=3DROR4=
%2FyD1WqWDb1rCbJx3ERqTiMCQ92ibkyz26kYZdD8%3D&amp;reserved=3D0" rel=3D"noref=
errer noreferrer" target=3D"_blank"><span style=3D"color:rgb(5,99,193)">htt=
ps://www.linkedin.com/in/dr2lopez/</span></a>=C2=A0</span><u></u><u></u></p=
>
<p class=3D"MsoNormal" style=3D"margin-left:0.5in"><span lang=3D"ES" style=
=3D"font-size:10pt">=C2=A0</span><u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:0.5in"><span lang=3D"ES" style=
=3D"font-size:10pt">e-mail:=C2=A0</span><span lang=3D"EN-GB" style=3D"font-=
size:10pt"><a href=3D"mailto:diego.r.lopez@telefonica.com" rel=3D"noreferre=
r noreferrer" target=3D"_blank"><span lang=3D"ES" style=3D"color:rgb(5,99,1=
93)">diego.r.lopez@telefonica.com</span></a></span><u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:0.5in"><span lang=3D"EN-GB" sty=
le=3D"font-size:10pt">Tel:=C2=A0=C2=A0=C2=A0 =C2=A0=C2=A0=C2=A0=C2=A0 +34 9=
13 129 041</span><u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:0.5in"><span lang=3D"EN-GB" sty=
le=3D"font-size:10pt">Mobile: =C2=A0+34 682 051 091</span><u></u><u></u></p=
>
</div>
<p class=3D"MsoNormal" style=3D"margin-left:0.5in"><span lang=3D"EN-GB" sty=
le=3D"font-size:10pt">----------------------------------</span><u></u><u></=
u></p>
<p class=3D"MsoNormal" style=3D"margin-left:0.5in"><span style=3D"font-size=
:10pt">=C2=A0</span><u></u><u></u></p>
<div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:1in">On 17/09/2020, 01:42, &quo=
t;Mr. Jaehoon Paul Jeong&quot; &lt;<a href=3D"mailto:jaehoon.paul@gmail.com=
" rel=3D"noreferrer noreferrer" target=3D"_blank">jaehoon.paul@gmail.com</a=
>&gt; wrote:<u></u><u></u></p>
</div>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:1in">=C2=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:1in">Hi Linda,<u></u><u></u></p=
>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:1in">I will address our AD Roma=
n&#39;s comments on this NSFs capabilities information draft as the 2nd edi=
tor through the collaboration with Frank (the 1st editor) and the other aut=
hors.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:1in">=C2=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:1in">I CC our AD Roman and the =
other authors, such as John and Cataldo.<u></u><u></u></p>
</div>
<div>
<pre style=3D"margin-left:1in"><span style=3D"font-size:9.5pt">=C2=A0</span=
><u></u><u></u></pre>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:1in">Thanks for your support an=
d guidance.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:1in">=C2=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:1in">Best Regards,<u></u><u></u=
></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:1in">Paul<u></u><u></u></p>
</div>
</div>
<p class=3D"MsoNormal" style=3D"margin-left:1in">=C2=A0<u></u><u></u></p>
<div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:1in">2020<span lang=3D"ZH-CN" s=
tyle=3D"font-family:&quot;Malgun Gothic&quot;,sans-serif">=EB=85=84</span> =
9<span lang=3D"ZH-CN" style=3D"font-family:&quot;Malgun Gothic&quot;,sans-s=
erif">=EC=9B=94</span> 17<span lang=3D"ZH-CN" style=3D"font-family:&quot;Ma=
lgun Gothic&quot;,sans-serif">=EC=9D=BC</span>
 (<span lang=3D"ZH-CN" style=3D"font-family:&quot;Malgun Gothic&quot;,sans-=
serif">=EB=AA=A9</span>) <span lang=3D"ZH-CN" style=3D"font-family:&quot;Ma=
lgun Gothic&quot;,sans-serif">
=EC=98=A4=EC=A0=84</span><span lang=3D"ZH-CN"> </span>3:44, Linda Dunbar &l=
t;<a href=3D"mailto:linda.dunbar@futurewei.com" rel=3D"noreferrer noreferre=
r" target=3D"_blank">linda.dunbar@futurewei.com</a>&gt;<span lang=3D"ZH-CN"=
 style=3D"font-family:&quot;Malgun Gothic&quot;,sans-serif">=EB=8B=98=EC=9D=
=B4</span><span lang=3D"ZH-CN">
</span><span lang=3D"ZH-CN" style=3D"font-family:&quot;Malgun Gothic&quot;,=
sans-serif">=EC=9E=91=EC=84=B1</span>:<u></u><u></u></p>
</div>
<blockquote style=3D"border-top:none;border-right:none;border-bottom:none;b=
order-left:1pt solid rgb(204,204,204);padding:0in 0in 0in 6pt;margin:5pt 0i=
n 5pt 4.8pt">
<div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:1in">
Paul, <u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:1in">
=C2=A0<u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:1in">
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 h=
as been over a year since the AD comments were given.=C2=A0 We need to move=
 the draft forward. Therefore, I2NSF
 chairs have authorized you to be one of the editors to address the AD comm=
ents and revise the draft.
<u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:1in">
=C2=A0<u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:1in">
=C2=A0<u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:1in">
Thank you very much. <u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:1in">
=C2=A0<u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:1in">
Linda &amp; Yoav<u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:1in">
=C2=A0<u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:1in">
=C2=A0<u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:1in">
<b>From:</b> Mr. Jaehoon Paul Jeong &lt;<a href=3D"mailto:jaehoon.paul@gmai=
l.com" rel=3D"noreferrer noreferrer" target=3D"_blank">jaehoon.paul@gmail.c=
om</a>&gt;
<br>
<b>Sent:</b> Sunday, September 13, 2020 10:09 AM<br>
<b>To:</b> Xialiang (Frank) &lt;<a href=3D"mailto:frank.xialiang@huawei.com=
" rel=3D"noreferrer noreferrer" target=3D"_blank">frank.xialiang@huawei.com=
</a>&gt;<br>
<b>Cc:</b> Linda Dunbar &lt;<a href=3D"mailto:linda.dunbar@futurewei.com" r=
el=3D"noreferrer noreferrer" target=3D"_blank">linda.dunbar@futurewei.com</=
a>&gt;; Yoav Nir &lt;<a href=3D"mailto:ynir.ietf@gmail.com" rel=3D"noreferr=
er noreferrer" target=3D"_blank">ynir.ietf@gmail.com</a>&gt;; DIEGO LOPEZ G=
ARCIA &lt;<a href=3D"mailto:diego.r.lopez@telefonica.com" rel=3D"noreferrer=
 noreferrer" target=3D"_blank">diego.r.lopez@telefonica.com</a>&gt;;
 Jaehoon Jeong &lt;<a href=3D"mailto:jaehoon.paul@gmail.com" rel=3D"norefer=
rer noreferrer" target=3D"_blank">jaehoon.paul@gmail.com</a>&gt;<br>
<b>Subject:</b> Offer for Revision Help for I2NSF NSFs Capabilities Informa=
tion Model Draft<u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:1in">
=C2=A0<u></u><u></u></p>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:1in">
Hi Frank,<u></u><u></u></p>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:1in">
Could I help you to revise your information model draft for our AD Roman Da=
nyliw&#39;s review comments=C2=A0 as a co-editor?<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:1in">
<a href=3D"https://nam11.safelinks.protection.outlook.com/?url=3Dhttps%3A%2=
F%2Fdatatracker.ietf.org%2Fdoc%2Fdraft-ietf-i2nsf-capability%2F%3Finclude_t=
ext%3D1&amp;data=3D02%7C01%7Clinda.dunbar%40futurewei.com%7C08a48858d7bd4d8=
43a6e08d85f47b438%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C637364108864=
959626&amp;sdata=3DGUrbaYu2Q4N1YNUUet2oVRPqbynA78cSBTf%2FBeSCY44%3D&amp;res=
erved=3D0" rel=3D"noreferrer noreferrer" target=3D"_blank">https://datatrac=
ker.ietf.org/doc/draft-ietf-i2nsf-capability/?include_text=3D1</a><u></u><u=
></u></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:1in">
=C2=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:1in">
As you know, I have finished our I2NSF data model drafts.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:1in">
=C2=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:1in">
I am happy to work on the revision with you in order to complete our I2NSF =
deliverables.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:1in">
=C2=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:1in">
Thanks.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:1in">
=C2=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:1in">
Best Regards,<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:1in">
Paul<u></u><u></u></p>
</div>
</div>
</div>
</div>
</blockquote>
</div>
<p class=3D"MsoNormal" style=3D"margin-left:0.5in">=C2=A0<u></u><u></u></p>
<div style=3D"margin-left:0.5in">
<div class=3D"MsoNormal" align=3D"center" style=3D"text-align:center">
<hr size=3D"1" width=3D"100%" align=3D"center">
</div>
</div>
<p class=3D"MsoNormal" style=3D"margin-left:0.5in"><span style=3D"font-size=
:7.5pt;font-family:Arial,sans-serif;color:gray"><br>
Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, pu=
ede contener informaci=C3=B3n privilegiada o confidencial y es para uso exc=
lusivo de la persona o entidad de destino. Si no es usted. el destinatario =
indicado, queda notificado de que la
 lectura, utilizaci=C3=B3n, divulgaci=C3=B3n y/o copia sin autorizaci=C3=B3=
n puede estar prohibida en virtud de la legislaci=C3=B3n vigente. Si ha rec=
ibido este mensaje por error, le rogamos que nos lo comunique inmediatament=
e por esta misma v=C3=ADa y proceda a su destrucci=C3=B3n.<br>
<br>
The information contained in this transmission is privileged and confidenti=
al 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 y=
ou have received this transmission in error, do not read it. Please immedia=
tely reply to the sender that you have received this communication in error=
 and then delete it.<br>
<br>
Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinat=C3=A1=
rio, pode conter informa=C3=A7=C3=A3o privilegiada ou confidencial e =C3=A9=
 para uso exclusivo da pessoa ou entidade de destino. Se n=C3=A3o =C3=A9 vo=
ssa senhoria o destinat=C3=A1rio indicado, fica notificado de que a
 leitura, utiliza=C3=A7=C3=A3o, divulga=C3=A7=C3=A3o e/ou c=C3=B3pia sem au=
toriza=C3=A7=C3=A3o pode estar proibida em virtude da legisla=C3=A7=C3=A3o =
vigente. Se recebeu esta mensagem por erro, rogamos-lhe que nos o comunique=
 imediatamente por esta mesma via e proceda a sua destrui=C3=A7=C3=A3o</spa=
n><u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<div class=3D"MsoNormal" align=3D"center" style=3D"text-align:center">
<hr size=3D"2" width=3D"100%" align=3D"center">
</div>
<p class=3D"MsoNormal"><span style=3D"font-size:7.5pt;font-family:Arial,san=
s-serif;color:gray"><br>
Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, pu=
ede contener informaci=C3=B3n privilegiada o confidencial y es para uso exc=
lusivo de la persona o entidad de destino. Si no es usted. el destinatario =
indicado, queda notificado de que la
 lectura, utilizaci=C3=B3n, divulgaci=C3=B3n y/o copia sin autorizaci=C3=B3=
n puede estar prohibida en virtud de la legislaci=C3=B3n vigente. Si ha rec=
ibido este mensaje por error, le rogamos que nos lo comunique inmediatament=
e por esta misma v=C3=ADa y proceda a su destrucci=C3=B3n.<br>
<br>
The information contained in this transmission is privileged and confidenti=
al 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 y=
ou have received this transmission in error, do not read it. Please immedia=
tely reply to the sender that you have received this communication in error=
 and then delete it.<br>
<br>
Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinat=C3=A1=
rio, pode conter informa=C3=A7=C3=A3o privilegiada ou confidencial e =C3=A9=
 para uso exclusivo da pessoa ou entidade de destino. Se n=C3=A3o =C3=A9 vo=
ssa senhoria o destinat=C3=A1rio indicado, fica notificado de que a
 leitura, utiliza=C3=A7=C3=A3o, divulga=C3=A7=C3=A3o e/ou c=C3=B3pia sem au=
toriza=C3=A7=C3=A3o pode estar proibida em virtude da legisla=C3=A7=C3=A3o =
vigente. Se recebeu esta mensagem por erro, rogamos-lhe que nos o comunique=
 imediatamente por esta mesma via e proceda a sua destrui=C3=A7=C3=A3o</spa=
n><u></u><u></u></p>
</div>
</div>

_______________________________________________<br>
I2nsf mailing list<br>
<a href=3D"mailto:I2nsf@ietf.org" rel=3D"noreferrer noreferrer" target=3D"_=
blank">I2nsf@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/i2nsf" rel=3D"noreferrer n=
oreferrer noreferrer" target=3D"_blank">https://www.ietf.org/mailman/listin=
fo/i2nsf</a><br>
</blockquote></div></div></div>
<span>_______________________________________________</span><br><span>I2nsf=
 mailing list</span><br><span><a href=3D"mailto:I2nsf@ietf.org" rel=3D"nore=
ferrer" target=3D"_blank">I2nsf@ietf.org</a></span><br><span><a href=3D"htt=
ps://www.ietf.org/mailman/listinfo/i2nsf" rel=3D"noreferrer" target=3D"_bla=
nk">https://www.ietf.org/mailman/listinfo/i2nsf</a></span><br></div></block=
quote></div></div></blockquote></div>
</blockquote></div><div dir=3D"ltr" class=3D"gmail_signature"><div dir=3D"l=
tr"><div><div dir=3D"ltr"><div><div dir=3D"ltr"><div><div dir=3D"ltr"><br><=
/div></div></div></div></div></div></div></div></div>

--000000000000edae3505b261779c--


From nobody Sat Oct 24 14:57:37 2020
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

--0000000000008d562c05b271c87f
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

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=EB=85=84 10=EC=9B=94 10=EC=9D=BC (=ED=86=A0) =EC=98=A4=EC=A0=84 10:=
20, Linda <dunbar.ll@gmail.com>=EB=8B=98=EC=9D=B4 =EC=9E=91=EC=84=B1:
>>
>>> Yes
>>> Linda
>>>
>>> Sent from my iPhone
>>>
>>> On Oct 9, 2020, at 7:55 PM, Mr. Jaehoon Paul Jeong <
>>> jaehoon.paul@gmail.com> wrote:
>>>
>>> =EF=BB=BF
>>> 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 M=
odel
>>> Draft.
>>>
>>> Is it correct?
>>>
>>> Thanks.
>>>
>>> Best Regards,
>>> Paul
>>>
>>> 2020=EB=85=84 10=EC=9B=94 9=EC=9D=BC (=EA=B8=88) =EC=98=A4=ED=9B=84 11:=
58, Linda Dunbar <linda.dunbar@futurewei.com>=EB=8B=98=EC=9D=B4
>>> =EC=9E=91=EC=84=B1:
>>>
>>>> I2NSF WG,
>>>>
>>>>
>>>>
>>>> Correction:
>>>>
>>>>
>>>>
>>>> There has been NO object to the Author=E2=80=99s request for sunsettin=
g the
>>>> draft-ietf-i2nsf-capability-5.
>>>>
>>>>
>>>>
>>>> We have marked the draft as =E2=80=9CDEAD=E2=80=9D 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 Capabili=
ties
>>>> Information Model Draft and merge the relevant information to the I2NS=
F
>>>> Capability Data model draft?
>>>>
>>>>
>>>>
>>>> I2nsf WG,
>>>>
>>>>
>>>>
>>>> There has been any objection to the Author=E2=80=99s request for sunse=
tting 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 dra=
ft.
>>>> 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 I2NS=
F
>>>> 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 manipulat=
ing
>>>> high-level policy expressions.  The capability data model has been evo=
lving
>>>> 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 th=
e
>>>> content in the information model still relevant to I2NSF Capability Da=
ta
>>>> Model, they should be merged into the Capability Data Model.
>>>>
>>>>
>>>>
>>>> Is there any objection from the WG?  If we don=E2=80=99t hear any obje=
ction 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=E2=80=99d 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 matt=
ers
>>>> 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=3Dhttps%3A%2F%2Fw=
ww.linkedin.com%2Fin%2Fdr2lopez%2F&data=3D02%7C01%7Clinda.dunbar%40futurewe=
i.com%7C08a48858d7bd4d843a6e08d85f47b438%7C0fee8ff2a3b240189c753a1d5591fedc=
%7C1%7C0%7C637364108864949633&sdata=3DROR4%2FyD1WqWDb1rCbJx3ERqTiMCQ92ibkyz=
26kYZdD8%3D&reserved=3D0>
>>>>
>>>>
>>>>
>>>>
>>>> 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 =E2=80=9Cthe capability da=
ta model was
>>>> evolving in a quite reasonable and pragmatic way, including running co=
de at
>>>> the hackathons=E2=80=9D.
>>>>
>>>>
>>>>
>>>> Looks like Eric Vyncke still wants the information model to be fixed t=
o
>>>> clear his =E2=80=9CDISCUSS=E2=80=9D ballot.
>>>>
>>>> How about the following steps:
>>>>
>>>> -          Ask Roman=E2=80=99s advice if we can simplify the Informati=
on 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=E2=80=
=99s 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 attemptin=
g to
>>>> align with its most recent evolution. If I have not shared this positi=
on
>>>> 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 reusin=
g
>>>> 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 addr=
essed
>>>> in the capability data model and the other data models produced in I2N=
SF. 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 theref=
ore
>>>> imply an extension of the I2NSF lifetime. I would like to know your
>>>> position(*) about such an extension,  that could also become an opport=
unity
>>>> to work in other matters related to attestation (in the light of the w=
ork
>>>> in RATS and the MUD initiative within the Ops Area) and accounting.
>>>>
>>>>
>>>>
>>>> Be goode,
>>>>
>>>>
>>>>
>>>> (*) I assume you are in favor, Paul. But I=E2=80=99d like to get Linda=
=E2=80=99s,
>>>> Yoav=E2=80=99s and Roman=E2=80=99s 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=3Dhttps%3A%2F%2Fw=
ww.linkedin.com%2Fin%2Fdr2lopez%2F&data=3D02%7C01%7Clinda.dunbar%40futurewe=
i.com%7C08a48858d7bd4d843a6e08d85f47b438%7C0fee8ff2a3b240189c753a1d5591fedc=
%7C1%7C0%7C637364108864949633&sdata=3DROR4%2FyD1WqWDb1rCbJx3ERqTiMCQ92ibkyz=
26kYZdD8%3D&reserved=3D0>
>>>>
>>>>
>>>>
>>>>
>>>> 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 Fra=
nk
>>>> (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=EB=85=84 9=EC=9B=94 17=EC=9D=BC (=EB=AA=A9) =EC=98=A4=EC=A0=84 3:=
44, Linda Dunbar <linda.dunbar@futurewei.com>=EB=8B=98=EC=9D=B4
>>>> =EC=9E=91=EC=84=B1:
>>>>
>>>> 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.  W=
e
>>>> need to move the draft forward. Therefore, I2NSF chairs have authorize=
d you
>>>> to be one of the editors to address the AD comments and revise the dra=
ft.
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> 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=3D1
>>>> <https://nam11.safelinks.protection.outlook.com/?url=3Dhttps%3A%2F%2Fd=
atatracker.ietf.org%2Fdoc%2Fdraft-ietf-i2nsf-capability%2F%3Finclude_text%3=
D1&data=3D02%7C01%7Clinda.dunbar%40futurewei.com%7C08a48858d7bd4d843a6e08d8=
5f47b438%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C637364108864959626&sd=
ata=3DGUrbaYu2Q4N1YNUUet2oVRPqbynA78cSBTf%2FBeSCY44%3D&reserved=3D0>
>>>>
>>>>
>>>>
>>>> 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=C3=B3n privilegiada o confidenc=
ial 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=
=C3=B3n,
>>>> divulgaci=C3=B3n y/o copia sin autorizaci=C3=B3n puede estar prohibida=
 en virtud de
>>>> la legislaci=C3=B3n vigente. Si ha recibido este mensaje por error, le=
 rogamos
>>>> que nos lo comunique inmediatamente por esta misma v=C3=ADa y proceda =
a su
>>>> destrucci=C3=B3n.
>>>>
>>>> The information contained in this transmission is privileged and
>>>> confidential information intended only for the use of the individual o=
r
>>>> entity named above. If the reader of this message is not the intended
>>>> recipient, you are hereby notified that any dissemination, distributio=
n or
>>>> copying of this communication is strictly prohibited. If you have rece=
ived
>>>> this transmission in error, do not read it. Please immediately reply t=
o the
>>>> sender that you have received this communication in error and then del=
ete
>>>> it.
>>>>
>>>> Esta mensagem e seus anexos se dirigem exclusivamente ao seu
>>>> destinat=C3=A1rio, pode conter informa=C3=A7=C3=A3o privilegiada ou co=
nfidencial e =C3=A9 para
>>>> uso exclusivo da pessoa ou entidade de destino. Se n=C3=A3o =C3=A9 vos=
sa senhoria o
>>>> destinat=C3=A1rio indicado, fica notificado de que a leitura, utiliza=
=C3=A7=C3=A3o,
>>>> divulga=C3=A7=C3=A3o e/ou c=C3=B3pia sem autoriza=C3=A7=C3=A3o pode es=
tar proibida em virtude da
>>>> legisla=C3=A7=C3=A3o vigente. Se recebeu esta mensagem por erro, rogam=
os-lhe que nos
>>>> o comunique imediatamente por esta mesma via e proceda a sua destrui=
=C3=A7=C3=A3o
>>>>
>>>>
>>>> ------------------------------
>>>>
>>>>
>>>> Este mensaje y sus adjuntos se dirigen exclusivamente a su
>>>> destinatario, puede contener informaci=C3=B3n privilegiada o confidenc=
ial 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=
=C3=B3n,
>>>> divulgaci=C3=B3n y/o copia sin autorizaci=C3=B3n puede estar prohibida=
 en virtud de
>>>> la legislaci=C3=B3n vigente. Si ha recibido este mensaje por error, le=
 rogamos
>>>> que nos lo comunique inmediatamente por esta misma v=C3=ADa y proceda =
a su
>>>> destrucci=C3=B3n.
>>>>
>>>> The information contained in this transmission is privileged and
>>>> confidential information intended only for the use of the individual o=
r
>>>> entity named above. If the reader of this message is not the intended
>>>> recipient, you are hereby notified that any dissemination, distributio=
n or
>>>> copying of this communication is strictly prohibited. If you have rece=
ived
>>>> this transmission in error, do not read it. Please immediately reply t=
o the
>>>> sender that you have received this communication in error and then del=
ete
>>>> it.
>>>>
>>>> Esta mensagem e seus anexos se dirigem exclusivamente ao seu
>>>> destinat=C3=A1rio, pode conter informa=C3=A7=C3=A3o privilegiada ou co=
nfidencial e =C3=A9 para
>>>> uso exclusivo da pessoa ou entidade de destino. Se n=C3=A3o =C3=A9 vos=
sa senhoria o
>>>> destinat=C3=A1rio indicado, fica notificado de que a leitura, utiliza=
=C3=A7=C3=A3o,
>>>> divulga=C3=A7=C3=A3o e/ou c=C3=B3pia sem autoriza=C3=A7=C3=A3o pode es=
tar proibida em virtude da
>>>> legisla=C3=A7=C3=A3o vigente. Se recebeu esta mensagem por erro, rogam=
os-lhe que nos
>>>> o comunique imediatamente por esta mesma via e proceda a sua destrui=
=C3=A7=C3=A3o
>>>> _______________________________________________
>>>> 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
>>>
>>>
>

--0000000000008d562c05b271c87f
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Paul,=C2=A0<div><br></div><div>Thank you very much for the=
 update.=C2=A0</div><div><br></div><div>Linda</div></div><br><div class=3D"=
gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Fri, Oct 23, 2020 at =
9:29 PM Mr. Jaehoon Paul Jeong &lt;<a href=3D"mailto:jaehoon.paul@gmail.com=
">jaehoon.paul@gmail.com</a>&gt; wrote:<br></div><blockquote class=3D"gmail=
_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204=
,204);padding-left:1ex"><div dir=3D"ltr"><div dir=3D"ltr">Hi Linda and Yoav=
,<div>I need more time to merge the information model and data model for=C2=
=A0</div><div>draft-ietf-i2nsf-capability-data-model along with the reflect=
ion of the IESG&#39;s comments:<br></div><div><a href=3D"https://datatracke=
r.ietf.org/doc/draft-ietf-i2nsf-capability-data-model/" target=3D"_blank">h=
ttps://datatracker.ietf.org/doc/draft-ietf-i2nsf-capability-data-model/</a>=
<br></div><div><br></div><div>I will try to do the merging=C2=A0and the ref=
lection of the comments of the IESG by IETF-109 I-D due (11/02/2020).</div>=
<div><br></div><div>Thanks.</div><div><br></div><div>Best Regards,</div><di=
v>Paul</div><div><br></div></div><br><div class=3D"gmail_quote"><div dir=3D=
"ltr" class=3D"gmail_attr">On Sat, Oct 10, 2020 at 10:33 AM Mr. Jaehoon Pau=
l Jeong &lt;<a href=3D"mailto:jaehoon.paul@gmail.com" target=3D"_blank">jae=
hoon.paul@gmail.com</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quot=
e" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204)=
;padding-left:1ex"><div dir=3D"auto">Linda,<div dir=3D"auto">I see.</div><d=
iv dir=3D"auto"><br></div><div dir=3D"auto">I will do the merging.</div><di=
v dir=3D"auto"><br></div><div dir=3D"auto">Thanks.</div><div dir=3D"auto"><=
br></div><div dir=3D"auto">Best Regards,</div><div dir=3D"auto">Paul</div><=
/div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">2=
020=EB=85=84 10=EC=9B=94 10=EC=9D=BC (=ED=86=A0) =EC=98=A4=EC=A0=84 10:20, =
Linda &lt;<a href=3D"mailto:dunbar.ll@gmail.com" target=3D"_blank">dunbar.l=
l@gmail.com</a>&gt;=EB=8B=98=EC=9D=B4 =EC=9E=91=EC=84=B1:<br></div><blockqu=
ote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px=
 solid rgb(204,204,204);padding-left:1ex"><div dir=3D"auto">Yes=C2=A0<div>L=
inda<br><br><div dir=3D"ltr">Sent from my iPhone</div><div dir=3D"ltr"><br>=
<blockquote type=3D"cite">On Oct 9, 2020, at 7:55 PM, Mr. Jaehoon Paul Jeon=
g &lt;<a href=3D"mailto:jaehoon.paul@gmail.com" rel=3D"noreferrer" target=
=3D"_blank">jaehoon.paul@gmail.com</a>&gt; wrote:<br><br></blockquote></div=
><blockquote type=3D"cite"><div dir=3D"ltr">=EF=BB=BF<div dir=3D"auto"><div=
>Hi Linda,</div><div dir=3D"auto">As I understand, I need to merge the rele=
vant contents of the NSFs Capability Information Model Draft into the I2NSF=
 NSF Capability Data Model Draft.</div><div dir=3D"auto"><br></div><div dir=
=3D"auto">Is it correct?</div><div dir=3D"auto"><br></div><div dir=3D"auto"=
>Thanks.</div><div dir=3D"auto"><br></div><div dir=3D"auto">Best Regards,</=
div><div dir=3D"auto">Paul</div><div dir=3D"auto"><br><div class=3D"gmail_q=
uote" dir=3D"auto"><div dir=3D"ltr" class=3D"gmail_attr">2020=EB=85=84 10=
=EC=9B=94 9=EC=9D=BC (=EA=B8=88) =EC=98=A4=ED=9B=84 11:58, Linda Dunbar &lt=
;<a href=3D"mailto:linda.dunbar@futurewei.com" rel=3D"noreferrer" target=3D=
"_blank">linda.dunbar@futurewei.com</a>&gt;=EB=8B=98=EC=9D=B4 =EC=9E=91=EC=
=84=B1:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px =
0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">





<div lang=3D"EN-US">
<div>
<p class=3D"MsoNormal">I2NSF WG, <u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">Correction: <u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">There has been NO object to the Author=E2=80=99s req=
uest for sunsetting the draft-ietf-i2nsf-capability-5.
<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">We have marked the draft as =E2=80=9CDEAD=E2=80=9D i=
n the WG status. <u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">Many thanks to the authors for putting the effort in=
 this draft for kickstarting all the data models in I2NSF WG.
<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">Linda &amp; Yoav<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<div>
<div style=3D"border-right:none;border-bottom:none;border-left:none;border-=
top:1pt solid rgb(225,225,225);padding:3pt 0in 0in">
<p class=3D"MsoNormal"><b>From:</b> Linda Dunbar <br>
<b>Sent:</b> Thursday, October 8, 2020 4:36 PM<br>
<b>To:</b> <a href=3D"mailto:i2nsf@ietf.org" rel=3D"noreferrer noreferrer" =
target=3D"_blank">i2nsf@ietf.org</a><br>
<b>Subject:</b> draft-ietf-i2nsf-capability-05 is officially removed from I=
2NSF WG ( was RE: Is there any objection of sunset the I2NSF Capabilities I=
nformation Model Draft and merge the relevant information to the I2NSF Capa=
bility Data model draft?
<u></u><u></u></p>
</div>
</div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">I2nsf WG, <u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">There has been any objection to the Author=E2=80=99s=
 request for sunsetting the =C2=A0draft-ietf-i2nsf-capability-05.
<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">Authors of the draft-ietf-i2nsf-capability-data-mode=
l: please remove the reference to the Capability Information Model and uplo=
ad a new draft. We can ask IESG to re-review it.
<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">Thank you very much. <u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">Linda &amp; Yoav. <u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<div>
<div style=3D"border-right:none;border-bottom:none;border-left:none;border-=
top:1pt solid rgb(225,225,225);padding:3pt 0in 0in">
<p class=3D"MsoNormal"><b>From:</b> Linda Dunbar <br>
<b>Sent:</b> Monday, September 28, 2020 11:00 AM<br>
<b>To:</b> <a href=3D"mailto:i2nsf@ietf.org" rel=3D"noreferrer noreferrer" =
target=3D"_blank">i2nsf@ietf.org</a><br>
<b>Subject:</b> Is there any objection of sunset the I2NSF Capabilities Inf=
ormation Model Draft and merge the relevant information to the I2NSF Capabi=
lity Data model draft?
<u></u><u></u></p>
</div>
</div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">I2NSF WG, <u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">As Diego has expressed that the original I2NSF capab=
ility information model was based on a policy expression calculus suitable =
for manipulating high-level policy expressions.=C2=A0 The capability data m=
odel has been evolving in a quite reasonable
 and pragmatic way, including running code at the hackathons.<u></u><u></u>=
</p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">The I2NSF Capability Information Model has fulfilled=
 its purpose of kickstarting and guiding the data model, and the authors be=
lieve that it is better to let the capability information model to be withd=
rawn. For the content in the information
 model still relevant to I2NSF Capability Data Model, they should be merged=
 into the Capability Data Model.
<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">Is there any objection from the WG?=C2=A0 If we don=
=E2=80=99t hear any objection by Oct 5, we will change the status of the dr=
aft.
<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">Cheers, =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0
<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">Linda &amp; Yoav<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<div>
<div style=3D"border-right:none;border-bottom:none;border-left:none;border-=
top:1pt solid rgb(225,225,225);padding:3pt 0in 0in">
<p class=3D"MsoNormal"><b>From:</b> Diego R. Lopez &lt;<a href=3D"mailto:di=
ego.r.lopez@telefonica.com" rel=3D"noreferrer noreferrer" target=3D"_blank"=
>diego.r.lopez@telefonica.com</a>&gt;
<br>
<b>Sent:</b> Tuesday, September 22, 2020 5:35 PM<br>
<b>To:</b> Linda Dunbar &lt;<a href=3D"mailto:linda.dunbar@futurewei.com" r=
el=3D"noreferrer noreferrer" target=3D"_blank">linda.dunbar@futurewei.com</=
a>&gt;; Mr. Jaehoon Paul Jeong &lt;<a href=3D"mailto:jaehoon.paul@gmail.com=
" rel=3D"noreferrer noreferrer" target=3D"_blank">jaehoon.paul@gmail.com</a=
>&gt;<br>
<b>Cc:</b> Xialiang (Frank) &lt;<a href=3D"mailto:frank.xialiang@huawei.com=
" rel=3D"noreferrer noreferrer" target=3D"_blank">frank.xialiang@huawei.com=
</a>&gt;; Yoav Nir &lt;<a href=3D"mailto:ynir.ietf@gmail.com" rel=3D"norefe=
rrer noreferrer" target=3D"_blank">ynir.ietf@gmail.com</a>&gt;; John Strass=
ner &lt;<a href=3D"mailto:John.sc.Strassner@huawei.com" rel=3D"noreferrer n=
oreferrer" target=3D"_blank">John.sc.Strassner@huawei.com</a>&gt;;
 Aldo Basile &lt;<a href=3D"mailto:cataldo.basile@polito.it" rel=3D"norefer=
rer noreferrer" target=3D"_blank">cataldo.basile@polito.it</a>&gt;; Roman D=
anyliw &lt;<a href=3D"mailto:rdd@cert.org" rel=3D"noreferrer noreferrer" ta=
rget=3D"_blank">rdd@cert.org</a>&gt;<br>
<b>Subject:</b> Re: Offer for Revision Help for I2NSF NSFs Capabilities Inf=
ormation Model Draft<u></u><u></u></p>
</div>
</div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal"><span lang=3D"ES" style=3D"font-size:10pt">Hi Linda,=
<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"ES" style=3D"font-size:10pt"><u></u>=
=C2=A0<u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10pt">I=E2=80=99d prefer th=
e 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 allowin=
g us to reuse the
 capability model for policy-control transformation, and to incorporate the=
 attestation matters you know I was so much interested in.<u></u><u></u></s=
pan></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10pt"><u></u>=C2=A0<u></u><=
/span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10pt">Be goode,<u></u><u></=
u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10pt"><u></u>=C2=A0<u></u><=
/span></p>
<div>
<p class=3D"MsoNormal"><span lang=3D"ES" style=3D"font-size:10pt">--<u></u>=
<u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"ES" style=3D"font-size:10pt">&quot;Est=
a vez no fallaremos, Doctor Infierno&quot;<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"ES" style=3D"font-size:10pt">=C2=A0<u>=
</u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"ES" style=3D"font-size:10pt">Dr Diego =
R. Lopez<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"ES" style=3D"font-size:10pt">Telefonic=
a I+D<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"ES" style=3D"font-size:10pt"><a href=
=3D"https://nam11.safelinks.protection.outlook.com/?url=3Dhttps%3A%2F%2Fwww=
.linkedin.com%2Fin%2Fdr2lopez%2F&amp;data=3D02%7C01%7Clinda.dunbar%40future=
wei.com%7C08a48858d7bd4d843a6e08d85f47b438%7C0fee8ff2a3b240189c753a1d5591fe=
dc%7C1%7C0%7C637364108864949633&amp;sdata=3DROR4%2FyD1WqWDb1rCbJx3ERqTiMCQ9=
2ibkyz26kYZdD8%3D&amp;reserved=3D0" rel=3D"noreferrer noreferrer" target=3D=
"_blank"><span style=3D"color:rgb(5,99,193)">https://www.linkedin.com/in/dr=
2lopez/</span></a>=C2=A0<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"ES" style=3D"font-size:10pt">=C2=A0<u>=
</u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"ES" style=3D"font-size:10pt">e-mail:=
=C2=A0</span><span lang=3D"EN-GB" style=3D"font-size:10pt"><a href=3D"mailt=
o:diego.r.lopez@telefonica.com" rel=3D"noreferrer noreferrer" target=3D"_bl=
ank"><span lang=3D"ES" style=3D"color:rgb(5,99,193)">diego.r.lopez@telefoni=
ca.com</span></a></span><span lang=3D"ES" style=3D"font-size:10pt"><u></u><=
u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB" style=3D"font-size:10pt">Tel:=
=C2=A0=C2=A0=C2=A0 =C2=A0=C2=A0=C2=A0=C2=A0 +34 913 129 041<u></u><u></u></=
span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB" style=3D"font-size:10pt">Mobile=
: =C2=A0+34 682 051 091<u></u><u></u></span></p>
</div>
<p class=3D"MsoNormal"><span lang=3D"EN-GB" style=3D"font-size:10pt">------=
----------------------------</span><span style=3D"font-size:10pt"><u></u><u=
></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10pt"><u></u>=C2=A0<u></u><=
/span></p>
<div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:0.5in">On 22/09/2020, 18:01, &q=
uot;Linda Dunbar&quot; &lt;<a href=3D"mailto:linda.dunbar@futurewei.com" re=
l=3D"noreferrer noreferrer" target=3D"_blank">linda.dunbar@futurewei.com</a=
>&gt; wrote:<u></u><u></u></p>
</div>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:0.5in"><u></u>=C2=A0<u></u></p>
</div>
<p class=3D"MsoNormal" style=3D"margin-left:0.5in">Diego: <u></u><u></u></p=
>
<p class=3D"MsoNormal" style=3D"margin-left:0.5in">=C2=A0<u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:0.5in">Thank you very much for =
the reflection of the Capabilities Information Model Draft. Agree with your=
 statement that =E2=80=9Cthe capability data model was evolving in a quite =
reasonable and pragmatic way, including running
 code at the hackathons=E2=80=9D. <u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:0.5in">=C2=A0<u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:0.5in">Looks like Eric Vyncke s=
till wants the information model to be fixed to clear his =E2=80=9CDISCUSS=
=E2=80=9D ballot.
<u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:0.5in">How about the following =
steps:<u></u><u></u></p>
<p style=3D"margin-left:1in">
<u></u><span>-<span style=3D"font:7pt &quot;Times New Roman&quot;">=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0
</span></span><u></u>Ask Roman=E2=80=99s advice if we can simplify the Info=
rmation Model mainly to reflect what has been in the Data Model.<u></u><u><=
/u></p>
<p style=3D"margin-left:1in">
<u></u><span>-<span style=3D"font:7pt &quot;Times New Roman&quot;">=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0
</span></span><u></u>Or, drop the Information model draft and remove the re=
fence to the draft, but Roman has to convince Eric to agree not having the =
information model.
<u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:0.5in">=C2=A0<u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:0.5in">What do you think? <u></=
u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:0.5in">=C2=A0<u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:0.5in">Linda<u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:0.5in">=C2=A0<u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:0.5in">=C2=A0<u></u><u></u></p>
<div>
<div style=3D"border-right:none;border-bottom:none;border-left:none;border-=
top:1pt solid rgb(225,225,225);padding:3pt 0in 0in">
<p class=3D"MsoNormal" style=3D"margin-left:0.5in"><b>From:</b> Diego R. Lo=
pez &lt;<a href=3D"mailto:diego.r.lopez@telefonica.com" rel=3D"noreferrer n=
oreferrer" target=3D"_blank">diego.r.lopez@telefonica.com</a>&gt;
<br>
<b>Sent:</b> Tuesday, September 22, 2020 9:50 AM<br>
<b>To:</b> Mr. Jaehoon Paul Jeong &lt;<a href=3D"mailto:jaehoon.paul@gmail.=
com" rel=3D"noreferrer noreferrer" target=3D"_blank">jaehoon.paul@gmail.com=
</a>&gt;; Linda Dunbar &lt;<a href=3D"mailto:linda.dunbar@futurewei.com" re=
l=3D"noreferrer noreferrer" target=3D"_blank">linda.dunbar@futurewei.com</a=
>&gt;<br>
<b>Cc:</b> Xialiang (Frank) &lt;<a href=3D"mailto:frank.xialiang@huawei.com=
" rel=3D"noreferrer noreferrer" target=3D"_blank">frank.xialiang@huawei.com=
</a>&gt;; Yoav Nir &lt;<a href=3D"mailto:ynir.ietf@gmail.com" rel=3D"norefe=
rrer noreferrer" target=3D"_blank">ynir.ietf@gmail.com</a>&gt;; John Strass=
ner &lt;<a href=3D"mailto:John.sc.Strassner@huawei.com" rel=3D"noreferrer n=
oreferrer" target=3D"_blank">John.sc.Strassner@huawei.com</a>&gt;;
 Aldo Basile &lt;<a href=3D"mailto:cataldo.basile@polito.it" rel=3D"norefer=
rer noreferrer" target=3D"_blank">cataldo.basile@polito.it</a>&gt;; Roman D=
anyliw &lt;<a href=3D"mailto:rdd@cert.org" rel=3D"noreferrer noreferrer" ta=
rget=3D"_blank">rdd@cert.org</a>&gt;<br>
<b>Subject:</b> Re: Offer for Revision Help for I2NSF NSFs Capabilities Inf=
ormation Model Draft<u></u><u></u></p>
</div>
</div>
<p class=3D"MsoNormal" style=3D"margin-left:0.5in">=C2=A0<u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:0.5in"><span><span style=3D"fon=
t-size:10pt">H</span></span><span><span lang=3D"ES" style=3D"font-size:10pt=
">i Paul,</span></span><u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:0.5in"><span><span lang=3D"ES" =
style=3D"font-size:10pt">=C2=A0</span></span><u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:0.5in"><span><span style=3D"fon=
t-size:10pt">Before you go for it, let me share with you some reflections o=
n the state of the draft, in the spirit of what I replied to Eric Vyncke.</=
span></span><u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:0.5in"><span><span style=3D"fon=
t-size:10pt">=C2=A0</span></span><u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:0.5in"><span style=3D"font-size=
:10pt">I must confess there has been a combination of events that made me t=
hink the best solution was to leave this draft to fade away. First, I was n=
ot (have not
 been yet) able to find a solution to most of Roman=E2=80=99s comments with=
out totally rewriting most, if not all, of the document.=C2=A0 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 mo=
del, 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 inf=
o model draft.</span><u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:0.5in"><span style=3D"font-size=
:10pt">=C2=A0</span><u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:0.5in"><span style=3D"font-size=
:10pt">As I told Eric, I believe the current capability model has a powerfu=
l (though probably not yet complete) calculus for policy description and va=
lidation,
 but not directly related to the management mechanisms addressed in the cap=
ability data model and the other data models produced in I2NSF. I believe t=
here 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 con=
solidate and therefore imply an extension of the I2NSF lifetime. I would li=
ke to know your position(*) about such an extension, =C2=A0that could also =
become an opportunity to work in other
 matters related to attestation (in the light of the work in RATS and the M=
UD initiative within the Ops Area) and accounting.</span><u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:0.5in"><span style=3D"font-size=
:10pt">=C2=A0</span><u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:0.5in"><span style=3D"font-size=
:10pt">Be goode,</span><u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:0.5in"><span style=3D"font-size=
:10pt">=C2=A0</span><u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:0.5in"><span style=3D"font-size=
:10pt">(*) I assume you are in favor, Paul. But I=E2=80=99d like to get Lin=
da=E2=80=99s, Yoav=E2=80=99s and Roman=E2=80=99s ideas, as well as the avai=
lability to work on this from Frank, John
 and Aldo.</span><u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:0.5in"><span style=3D"font-size=
:10pt">=C2=A0</span><u></u><u></u></p>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:0.5in"><span style=3D"font-size=
:10pt">--</span><u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:0.5in"><span lang=3D"ES" style=
=3D"font-size:10pt">&quot;Esta vez no fallaremos, Doctor Infierno&quot;</sp=
an><u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:0.5in"><span lang=3D"ES" style=
=3D"font-size:10pt">=C2=A0</span><u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:0.5in"><span lang=3D"ES" style=
=3D"font-size:10pt">Dr Diego R. Lopez</span><u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:0.5in"><span lang=3D"ES" style=
=3D"font-size:10pt">Telefonica I+D</span><u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:0.5in"><span lang=3D"ES" style=
=3D"font-size:10pt"><a href=3D"https://nam11.safelinks.protection.outlook.c=
om/?url=3Dhttps%3A%2F%2Fwww.linkedin.com%2Fin%2Fdr2lopez%2F&amp;data=3D02%7=
C01%7Clinda.dunbar%40futurewei.com%7C08a48858d7bd4d843a6e08d85f47b438%7C0fe=
e8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C637364108864949633&amp;sdata=3DROR4=
%2FyD1WqWDb1rCbJx3ERqTiMCQ92ibkyz26kYZdD8%3D&amp;reserved=3D0" rel=3D"noref=
errer noreferrer" target=3D"_blank"><span style=3D"color:rgb(5,99,193)">htt=
ps://www.linkedin.com/in/dr2lopez/</span></a>=C2=A0</span><u></u><u></u></p=
>
<p class=3D"MsoNormal" style=3D"margin-left:0.5in"><span lang=3D"ES" style=
=3D"font-size:10pt">=C2=A0</span><u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:0.5in"><span lang=3D"ES" style=
=3D"font-size:10pt">e-mail:=C2=A0</span><span lang=3D"EN-GB" style=3D"font-=
size:10pt"><a href=3D"mailto:diego.r.lopez@telefonica.com" rel=3D"noreferre=
r noreferrer" target=3D"_blank"><span lang=3D"ES" style=3D"color:rgb(5,99,1=
93)">diego.r.lopez@telefonica.com</span></a></span><u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:0.5in"><span lang=3D"EN-GB" sty=
le=3D"font-size:10pt">Tel:=C2=A0=C2=A0=C2=A0 =C2=A0=C2=A0=C2=A0=C2=A0 +34 9=
13 129 041</span><u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:0.5in"><span lang=3D"EN-GB" sty=
le=3D"font-size:10pt">Mobile: =C2=A0+34 682 051 091</span><u></u><u></u></p=
>
</div>
<p class=3D"MsoNormal" style=3D"margin-left:0.5in"><span lang=3D"EN-GB" sty=
le=3D"font-size:10pt">----------------------------------</span><u></u><u></=
u></p>
<p class=3D"MsoNormal" style=3D"margin-left:0.5in"><span style=3D"font-size=
:10pt">=C2=A0</span><u></u><u></u></p>
<div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:1in">On 17/09/2020, 01:42, &quo=
t;Mr. Jaehoon Paul Jeong&quot; &lt;<a href=3D"mailto:jaehoon.paul@gmail.com=
" rel=3D"noreferrer noreferrer" target=3D"_blank">jaehoon.paul@gmail.com</a=
>&gt; wrote:<u></u><u></u></p>
</div>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:1in">=C2=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:1in">Hi Linda,<u></u><u></u></p=
>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:1in">I will address our AD Roma=
n&#39;s comments on this NSFs capabilities information draft as the 2nd edi=
tor through the collaboration with Frank (the 1st editor) and the other aut=
hors.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:1in">=C2=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:1in">I CC our AD Roman and the =
other authors, such as John and Cataldo.<u></u><u></u></p>
</div>
<div>
<pre style=3D"margin-left:1in"><span style=3D"font-size:9.5pt">=C2=A0</span=
><u></u><u></u></pre>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:1in">Thanks for your support an=
d guidance.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:1in">=C2=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:1in">Best Regards,<u></u><u></u=
></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:1in">Paul<u></u><u></u></p>
</div>
</div>
<p class=3D"MsoNormal" style=3D"margin-left:1in">=C2=A0<u></u><u></u></p>
<div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:1in">2020<span lang=3D"ZH-CN" s=
tyle=3D"font-family:&quot;Malgun Gothic&quot;,sans-serif">=EB=85=84</span> =
9<span lang=3D"ZH-CN" style=3D"font-family:&quot;Malgun Gothic&quot;,sans-s=
erif">=EC=9B=94</span> 17<span lang=3D"ZH-CN" style=3D"font-family:&quot;Ma=
lgun Gothic&quot;,sans-serif">=EC=9D=BC</span>
 (<span lang=3D"ZH-CN" style=3D"font-family:&quot;Malgun Gothic&quot;,sans-=
serif">=EB=AA=A9</span>) <span lang=3D"ZH-CN" style=3D"font-family:&quot;Ma=
lgun Gothic&quot;,sans-serif">
=EC=98=A4=EC=A0=84</span><span lang=3D"ZH-CN"> </span>3:44, Linda Dunbar &l=
t;<a href=3D"mailto:linda.dunbar@futurewei.com" rel=3D"noreferrer noreferre=
r" target=3D"_blank">linda.dunbar@futurewei.com</a>&gt;<span lang=3D"ZH-CN"=
 style=3D"font-family:&quot;Malgun Gothic&quot;,sans-serif">=EB=8B=98=EC=9D=
=B4</span><span lang=3D"ZH-CN">
</span><span lang=3D"ZH-CN" style=3D"font-family:&quot;Malgun Gothic&quot;,=
sans-serif">=EC=9E=91=EC=84=B1</span>:<u></u><u></u></p>
</div>
<blockquote style=3D"border-top:none;border-right:none;border-bottom:none;b=
order-left:1pt solid rgb(204,204,204);padding:0in 0in 0in 6pt;margin:5pt 0i=
n 5pt 4.8pt">
<div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:1in">
Paul, <u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:1in">
=C2=A0<u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:1in">
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 h=
as been over a year since the AD comments were given.=C2=A0 We need to move=
 the draft forward. Therefore, I2NSF
 chairs have authorized you to be one of the editors to address the AD comm=
ents and revise the draft.
<u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:1in">
=C2=A0<u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:1in">
=C2=A0<u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:1in">
Thank you very much. <u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:1in">
=C2=A0<u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:1in">
Linda &amp; Yoav<u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:1in">
=C2=A0<u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:1in">
=C2=A0<u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:1in">
<b>From:</b> Mr. Jaehoon Paul Jeong &lt;<a href=3D"mailto:jaehoon.paul@gmai=
l.com" rel=3D"noreferrer noreferrer" target=3D"_blank">jaehoon.paul@gmail.c=
om</a>&gt;
<br>
<b>Sent:</b> Sunday, September 13, 2020 10:09 AM<br>
<b>To:</b> Xialiang (Frank) &lt;<a href=3D"mailto:frank.xialiang@huawei.com=
" rel=3D"noreferrer noreferrer" target=3D"_blank">frank.xialiang@huawei.com=
</a>&gt;<br>
<b>Cc:</b> Linda Dunbar &lt;<a href=3D"mailto:linda.dunbar@futurewei.com" r=
el=3D"noreferrer noreferrer" target=3D"_blank">linda.dunbar@futurewei.com</=
a>&gt;; Yoav Nir &lt;<a href=3D"mailto:ynir.ietf@gmail.com" rel=3D"noreferr=
er noreferrer" target=3D"_blank">ynir.ietf@gmail.com</a>&gt;; DIEGO LOPEZ G=
ARCIA &lt;<a href=3D"mailto:diego.r.lopez@telefonica.com" rel=3D"noreferrer=
 noreferrer" target=3D"_blank">diego.r.lopez@telefonica.com</a>&gt;;
 Jaehoon Jeong &lt;<a href=3D"mailto:jaehoon.paul@gmail.com" rel=3D"norefer=
rer noreferrer" target=3D"_blank">jaehoon.paul@gmail.com</a>&gt;<br>
<b>Subject:</b> Offer for Revision Help for I2NSF NSFs Capabilities Informa=
tion Model Draft<u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:1in">
=C2=A0<u></u><u></u></p>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:1in">
Hi Frank,<u></u><u></u></p>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:1in">
Could I help you to revise your information model draft for our AD Roman Da=
nyliw&#39;s review comments=C2=A0 as a co-editor?<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:1in">
<a href=3D"https://nam11.safelinks.protection.outlook.com/?url=3Dhttps%3A%2=
F%2Fdatatracker.ietf.org%2Fdoc%2Fdraft-ietf-i2nsf-capability%2F%3Finclude_t=
ext%3D1&amp;data=3D02%7C01%7Clinda.dunbar%40futurewei.com%7C08a48858d7bd4d8=
43a6e08d85f47b438%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C637364108864=
959626&amp;sdata=3DGUrbaYu2Q4N1YNUUet2oVRPqbynA78cSBTf%2FBeSCY44%3D&amp;res=
erved=3D0" rel=3D"noreferrer noreferrer" target=3D"_blank">https://datatrac=
ker.ietf.org/doc/draft-ietf-i2nsf-capability/?include_text=3D1</a><u></u><u=
></u></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:1in">
=C2=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:1in">
As you know, I have finished our I2NSF data model drafts.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:1in">
=C2=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:1in">
I am happy to work on the revision with you in order to complete our I2NSF =
deliverables.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:1in">
=C2=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:1in">
Thanks.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:1in">
=C2=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:1in">
Best Regards,<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:1in">
Paul<u></u><u></u></p>
</div>
</div>
</div>
</div>
</blockquote>
</div>
<p class=3D"MsoNormal" style=3D"margin-left:0.5in">=C2=A0<u></u><u></u></p>
<div style=3D"margin-left:0.5in">
<div class=3D"MsoNormal" align=3D"center" style=3D"text-align:center">
<hr size=3D"1" width=3D"100%" align=3D"center">
</div>
</div>
<p class=3D"MsoNormal" style=3D"margin-left:0.5in"><span style=3D"font-size=
:7.5pt;font-family:Arial,sans-serif;color:gray"><br>
Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, pu=
ede contener informaci=C3=B3n privilegiada o confidencial y es para uso exc=
lusivo de la persona o entidad de destino. Si no es usted. el destinatario =
indicado, queda notificado de que la
 lectura, utilizaci=C3=B3n, divulgaci=C3=B3n y/o copia sin autorizaci=C3=B3=
n puede estar prohibida en virtud de la legislaci=C3=B3n vigente. Si ha rec=
ibido este mensaje por error, le rogamos que nos lo comunique inmediatament=
e por esta misma v=C3=ADa y proceda a su destrucci=C3=B3n.<br>
<br>
The information contained in this transmission is privileged and confidenti=
al 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 y=
ou have received this transmission in error, do not read it. Please immedia=
tely reply to the sender that you have received this communication in error=
 and then delete it.<br>
<br>
Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinat=C3=A1=
rio, pode conter informa=C3=A7=C3=A3o privilegiada ou confidencial e =C3=A9=
 para uso exclusivo da pessoa ou entidade de destino. Se n=C3=A3o =C3=A9 vo=
ssa senhoria o destinat=C3=A1rio indicado, fica notificado de que a
 leitura, utiliza=C3=A7=C3=A3o, divulga=C3=A7=C3=A3o e/ou c=C3=B3pia sem au=
toriza=C3=A7=C3=A3o pode estar proibida em virtude da legisla=C3=A7=C3=A3o =
vigente. Se recebeu esta mensagem por erro, rogamos-lhe que nos o comunique=
 imediatamente por esta mesma via e proceda a sua destrui=C3=A7=C3=A3o</spa=
n><u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<div class=3D"MsoNormal" align=3D"center" style=3D"text-align:center">
<hr size=3D"2" width=3D"100%" align=3D"center">
</div>
<p class=3D"MsoNormal"><span style=3D"font-size:7.5pt;font-family:Arial,san=
s-serif;color:gray"><br>
Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, pu=
ede contener informaci=C3=B3n privilegiada o confidencial y es para uso exc=
lusivo de la persona o entidad de destino. Si no es usted. el destinatario =
indicado, queda notificado de que la
 lectura, utilizaci=C3=B3n, divulgaci=C3=B3n y/o copia sin autorizaci=C3=B3=
n puede estar prohibida en virtud de la legislaci=C3=B3n vigente. Si ha rec=
ibido este mensaje por error, le rogamos que nos lo comunique inmediatament=
e por esta misma v=C3=ADa y proceda a su destrucci=C3=B3n.<br>
<br>
The information contained in this transmission is privileged and confidenti=
al 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 y=
ou have received this transmission in error, do not read it. Please immedia=
tely reply to the sender that you have received this communication in error=
 and then delete it.<br>
<br>
Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinat=C3=A1=
rio, pode conter informa=C3=A7=C3=A3o privilegiada ou confidencial e =C3=A9=
 para uso exclusivo da pessoa ou entidade de destino. Se n=C3=A3o =C3=A9 vo=
ssa senhoria o destinat=C3=A1rio indicado, fica notificado de que a
 leitura, utiliza=C3=A7=C3=A3o, divulga=C3=A7=C3=A3o e/ou c=C3=B3pia sem au=
toriza=C3=A7=C3=A3o pode estar proibida em virtude da legisla=C3=A7=C3=A3o =
vigente. Se recebeu esta mensagem por erro, rogamos-lhe que nos o comunique=
 imediatamente por esta mesma via e proceda a sua destrui=C3=A7=C3=A3o</spa=
n><u></u><u></u></p>
</div>
</div>

_______________________________________________<br>
I2nsf mailing list<br>
<a href=3D"mailto:I2nsf@ietf.org" rel=3D"noreferrer noreferrer" target=3D"_=
blank">I2nsf@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/i2nsf" rel=3D"noreferrer n=
oreferrer noreferrer" target=3D"_blank">https://www.ietf.org/mailman/listin=
fo/i2nsf</a><br>
</blockquote></div></div></div>
<span>_______________________________________________</span><br><span>I2nsf=
 mailing list</span><br><span><a href=3D"mailto:I2nsf@ietf.org" rel=3D"nore=
ferrer" target=3D"_blank">I2nsf@ietf.org</a></span><br><span><a href=3D"htt=
ps://www.ietf.org/mailman/listinfo/i2nsf" rel=3D"noreferrer" target=3D"_bla=
nk">https://www.ietf.org/mailman/listinfo/i2nsf</a></span><br></div></block=
quote></div></div></blockquote></div>
</blockquote></div><div dir=3D"ltr"><div dir=3D"ltr"><div><div dir=3D"ltr">=
<div><div dir=3D"ltr"><div><div dir=3D"ltr"><br></div></div></div></div></d=
iv></div></div></div></div>
</blockquote></div>

--0000000000008d562c05b271c87f--


From nobody Tue Oct 27 05:43:14 2020
Return-Path: <daedulus@btconnect.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 6E1513A0062; Tue, 27 Oct 2020 05:43:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.147
X-Spam-Level: 
X-Spam-Status: No, score=-2.147 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, MSGID_FROM_MTA_HEADER=0.001, NICE_REPLY_A=-0.247, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=btconnect.onmicrosoft.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 eOVvSIzyLeUf; Tue, 27 Oct 2020 05:43:06 -0700 (PDT)
Received: from EUR01-DB5-obe.outbound.protection.outlook.com (mail-eopbgr150132.outbound.protection.outlook.com [40.107.15.132]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0EF493A005F; Tue, 27 Oct 2020 05:43:05 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=iufj6p1Mf/3KdZtrSQXHkwAeAuMItz8UTI/ye2iO4wTO8tIR6gyBbY6Qs0peOoeMZqzo64qpXWXPu91rAts1L6ZcMtInEtmIYrWb8iq5IaTuuf5yhJi6U9P8opWDY2CuuiEbbp2UKHHqnwuoNz4d1f40KJyeMEpl+nmb2Rw9PjSs8C0F3ynE9yuBx+zWnnP8KIkNfI+UFYeVWoWl8BCH+4Hr9h+e3Si4NGwvAQG+ulpBwLWUf+z9THulJtPeoDwxvOPJA2un2MqSQE/sV1UgWHG7lhsKE2HoWeVXIf7loKkFZnGAdDWAfP5dfu7qhNjOoetS3a9sRyjAbwLYWJ1sAg==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=ltQExuvXMAWg54ruttv6nJ4db80ijisYxuO+lROvI/M=; b=BLlzC46nF4L9PPH5FaZRg5otKUr4JIRCh5ShTu+OnDP6mGRHU/J8tmjlkuXBVyFAB6edHWV+tjpuPA6ZakYr733epYy/9I6JHptoL0cvhpLVuIEk8ki0oSZFTlt7eEoz70czrgVdkYHrAHYMZKjMKt9xF4ov7pAjpyY6cDX/oqVcku2H7GOh7Bkv/kCLL4QFFW0BusIHQStTW2w3snS0ElypxUWErvddhTQpTKKmN/dp1+fa8+N3hpbOOlahJWh/N9ro38TVdPvcHdsxqI+nl+TKqoFsRd/Oio9nLSlOdPWqrEHy0lxJfX8g+sgVvg1u40NNAgH2GWDRe65RMsB1Hg==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=btconnect.com; dmarc=pass action=none header.from=btconnect.com; dkim=pass header.d=btconnect.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=btconnect.onmicrosoft.com; s=selector2-btconnect-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=ltQExuvXMAWg54ruttv6nJ4db80ijisYxuO+lROvI/M=; b=vLunXBowJHNEPa3/+5fmEhnAPH9dGCJsh5MvU79uzjIx4WZXfvgrRKjqoyhE6LidMwEONSWDYym9UUMsqqx6X99h3ztDrRbkAZGIe3szdTCihRdOfCCup7NtSvMfwO+f/1BjJCQJ6kEgUiMEkSJCDPBLQDUOR7NJ/Xwp9k5Rhz8=
Authentication-Results: gmail.com; dkim=none (message not signed) header.d=none;gmail.com; dmarc=none action=none header.from=btconnect.com;
Received: from VI1PR07MB6704.eurprd07.prod.outlook.com (2603:10a6:800:18b::8) by VI1PR0701MB6861.eurprd07.prod.outlook.com (2603:10a6:800:19b::13) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3499.7; Tue, 27 Oct 2020 12:43:03 +0000
Received: from VI1PR07MB6704.eurprd07.prod.outlook.com ([fe80::6165:9c1c:e5b1:15db]) by VI1PR07MB6704.eurprd07.prod.outlook.com ([fe80::6165:9c1c:e5b1:15db%4]) with mapi id 15.20.3477.021; Tue, 27 Oct 2020 12:43:03 +0000
To: Rafa Marin-Lopez <rafa@um.es>, i2nsf@ietf.org
References: <160337357077.29083.9236626834026808055@ietfa.amsl.com> <EE5AB669-73BB-4517-A6F4-23B7807FB36E@um.es>
Cc: Gabriel Lopez <gabilm@um.es>, Fernando Pereniguez-Garcia <fernando.pereniguez@cud.upct.es>, last-call@ietf.org, ynir.ietf@gmail.com
From: tom petch <daedulus@btconnect.com>
Message-ID: <5F9815D1.9010303@btconnect.com>
Date: Tue, 27 Oct 2020 12:42:57 +0000
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:38.0) Gecko/20100101 Thunderbird/38.5.0
In-Reply-To: <EE5AB669-73BB-4517-A6F4-23B7807FB36E@um.es>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
X-Originating-IP: [86.146.121.140]
X-ClientProxiedBy: LO2P265CA0113.GBRP265.PROD.OUTLOOK.COM (2603:10a6:600:c::29) To VI1PR07MB6704.eurprd07.prod.outlook.com (2603:10a6:800:18b::8)
MIME-Version: 1.0
X-MS-Exchange-MessageSentRepresentingType: 1
Received: from [192.168.1.65] (86.146.121.140) by LO2P265CA0113.GBRP265.PROD.OUTLOOK.COM (2603:10a6:600:c::29) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.20.3499.18 via Frontend Transport; Tue, 27 Oct 2020 12:43:02 +0000
X-MS-PublicTrafficType: Email
X-MS-Office365-Filtering-Correlation-Id: 10e419b0-b0e2-47c1-2743-08d87a75d835
X-MS-TrafficTypeDiagnostic: VI1PR0701MB6861:
X-Microsoft-Antispam-PRVS: <VI1PR0701MB6861C42A607B0343F33499DCC6160@VI1PR0701MB6861.eurprd07.prod.outlook.com>
X-MS-Oob-TLC-OOBClassifiers: OLM:5516;
X-MS-Exchange-SenderADCheck: 1
X-Microsoft-Antispam: BCL:0;
X-Microsoft-Antispam-Message-Info: RUI5V3ZmnwjYhIWPRVCdFnsK2iphVxITi1UFliS2zRvExNXOwi8FnEuFyW8mdg2TLE4QFZg52gGpiDX5vUyoGnwueGKdCl/33RU8d5mkPrTGXMrY5LrfyoBZ918bN4paJi5VVIlQBMXYRapnBYNSoSckBsP3iKdOrtvtt2zD512mG+2uWAeuGNrRy6QCv+76ozR5zHMOoareI+YsxazM1kZHO28E/82KALwQ5WqULyt7P2XH4KrAABKywGjNjiV0svb2Ltnld73e6u/MycX2YoH1h0ktFhIPpOK1tHfSDdV6Ya4QtldO6UDIl/Go4tWimqSQW/X2hpa7rvqZS1Cn8WOnUxEJteTT/jxxvToVZayNEizdjIWNbBqngmuDZnxhaxKkaUal861oDS/JM0/whQ==
X-Forefront-Antispam-Report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;  IPV:NLI; SFV:NSPM; H:VI1PR07MB6704.eurprd07.prod.outlook.com; PTR:; CAT:NONE;  SFS:(396003)(136003)(376002)(366004)(346002)(39860400002)(87266011)(53546011)(33656002)(5660300002)(2906002)(8676002)(83380400001)(52116002)(54906003)(66574015)(16576012)(316002)(66946007)(4326008)(478600001)(15650500001)(36756003)(8936002)(956004)(86362001)(6666004)(66476007)(4001150100001)(26005)(966005)(186003)(16526019)(6486002)(2616005)(66556008); DIR:OUT; SFP:1102; 
X-MS-Exchange-AntiSpam-MessageData: gZiL0CVPEXH9TnW6yxrbKndzzIsDPeGD+CkfGaoKURxxv/eamoUd2v6yzAh6StEA8GYwON+SaVRRLchefJ3oT04QQ5tH24ahlvxuJQqmEVXmg6LlTzkJ0E185gxenntEapKLUgHwj4QOqOGScpzQboyIXP/2GNKW2OLRULmpkcJhTQXpM2bViOHJ8/8XvBnCe3Y4o7bOopd7SBPoqaieeL+aHC3ogqdYBM0SJ1ga33ekfCf/qGReo5T3ftpTaGg55K0OBc906LVquiWrxGzeUkOTUhuHVd3OOr2H2orzXzfpHK06w1/Jxo/oYnRr/eC0TZakf3DbSusOPT0u6wFkccnHDwGwRn5nPJqEETr4udyMpZc47gmSCWWMahoFifsQmttBSOlFBGRCixUCPiIj2RWt8PvAuHr97P+fsrMacgEbyjgtWdknx7lZoEJaX4Uewf2bDY1D6v9/UmU6k6uijZXAV5W1ZQFtpgXXqJHXxBYodLevWq/IyufKnaQxbvqNjtyHC334jgmCwN8znyBGwFDvVQmCFjcM4/g0FrKgxwz6fz/5i32c7QGaYLsLtb91LS2I5CVHBtPHONHYOpPzP7hUPnrEc6bLBseQQb8AjGIFLTSjh9ov4Uh441c85pn7t1SN+VmA2AweKT5KHnSrmQ==
X-OriginatorOrg: btconnect.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 10e419b0-b0e2-47c1-2743-08d87a75d835
X-MS-Exchange-CrossTenant-AuthSource: VI1PR07MB6704.eurprd07.prod.outlook.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 27 Oct 2020 12:43:03.2608 (UTC)
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-CrossTenant-Id: cf8853ed-96e5-465b-9185-806bfe185e30
X-MS-Exchange-CrossTenant-MailboxType: HOSTED
X-MS-Exchange-CrossTenant-UserPrincipalName: zIgAfLV25PtUnjMNpKPlRgUurxqnDFc5aU/2ry23ylBprI002ituCWHzVTK204YTOki3homK7MhdFgA6WV4haA==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: VI1PR0701MB6861
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2nsf/DTH_CTHXu9_I0s5K5QydpqiUusM>
Subject: Re: [I2nsf] [Last-Call] Fwd: New Version Notification for draft-ietf-i2nsf-sdn-ipsec-flow-protection-11.txt
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: Tue, 27 Oct 2020 12:43:09 -0000

I think that the IESG will find a number of problems with this I-D.

YANG module references RFC822 which is several years out of date

YANG module references IANA Protocol Numbers which is not in the I-D 
references

s.2 boiler plate is out of date

XXXX is standing in for more than one RFC

but the show stopper that makes a proper review of this too costly is 
the references.  Those to IANA of which there are several I want to 
pursue.  The I-D reference is to IKEv2 parameters. Sadly, this is a 
three tier structure and noone agrees on what to call the third tier so 
I will call it tier3 here.  Top level is Group, as per RFC8126, second 
level is Registry.  The I-D reference is to the Group only which is fine 
if the actual reference then specifies the Registry and Tier3 but they 
never do, usually just Tier3 e.g. Transform Type 3 which makes for a lot 
of work for the reader, too much for this one.  You have to go hunting 
in all the second level Registry until you can find a match for the 
Tier3 identifier. And there are no URL.  If you want an example that I 
find easy to use, go look at RFC8407 (as usual).

The reference for import of i2nsf-ikec gives a YANG module name; this 
needs to be the name of the RFC to be

The example IPv6 address in the YANG module has :0:0: which is usually 
just ::

And I have some way to go still.

Tom Petch

On 22/10/2020 18:39, Rafa Marin-Lopez wrote:
> Dear all:
>
> After receiving a suggestion to make things clearer in the feature ikeless-notification description, we have just uploaded a new version -11 with a minor change to add the following text:
>
> feature ikeless-notification {
>              description
>                  "This feature indicates that the server supports
>                  generating notifications in the ikeless module.
>
>                  To ensure broader applicability of this module,
>                  the notifications are marked as a feature.
>                  For the implementation of ikeless case,
>                  the NSF is expected to implement this
>                  feature.";
>          }
>
> Best Regards.
>
>> Inicio del mensaje reenviado:
>>
>> De: internet-drafts@ietf.org
>> Asunto: New Version Notification for draft-ietf-i2nsf-sdn-ipsec-flow-protection-11.txt
>> Fecha: 22 de octubre de 2020, 15:32:50 CEST
>> Para: "Fernando Pereniguez-Garcia" <fernando.pereniguez@cud.upct.es>, "Rafael Lopez" <rafa@um.es>, "Gabriel Lopez-Millan" <gabilm@um.es>, "Rafa Marin-Lopez" <rafa@um.es>
>>
>>
>> A new version of I-D, draft-ietf-i2nsf-sdn-ipsec-flow-protection-11.txt
>> has been successfully submitted by Rafa Marin-Lopez and posted to the
>> IETF repository.
>>
>> Name:		draft-ietf-i2nsf-sdn-ipsec-flow-protection
>> Revision:	11
>> Title:		Software-Defined Networking (SDN)-based IPsec Flow Protection
>> Document date:	2020-10-22
>> Group:		i2nsf
>> Pages:		92
>> URL:            https://www.ietf.org/archive/id/draft-ietf-i2nsf-sdn-ipsec-flow-protection-11.txt
>> Status:         https://datatracker.ietf.org/doc/draft-ietf-i2nsf-sdn-ipsec-flow-protection/
>> Htmlized:       https://datatracker.ietf.org/doc/html/draft-ietf-i2nsf-sdn-ipsec-flow-protection
>> Htmlized:       https://tools.ietf.org/html/draft-ietf-i2nsf-sdn-ipsec-flow-protection-11
>> Diff:           https://www.ietf.org/rfcdiff?url2=draft-ietf-i2nsf-sdn-ipsec-flow-protection-11
>>
>> Abstract:
>>    This document describes how to provide IPsec-based flow protection
>>    (integrity and confidentiality) by means of an Interface to Network
>>    Security Function (I2NSF) controller.  It considers two main well-
>>    known scenarios in IPsec: (i) gateway-to-gateway and (ii) host-to-
>>    host.  The service described in this document allows the
>>    configuration and monitoring of IPsec Security Associations (SAs)
>>    from a I2NSF Controller to one or several flow-based Network Security
>>    Functions (NSFs) that rely on IPsec to protect data traffic.
>>
>>    The document focuses on the I2NSF NSF-facing interface by providing
>>    YANG data models for configuring the IPsec databases (SPD, SAD, PAD)
>>    and IKEv2.  This allows IPsec SA establishment with minimal
>>    intervention by the network administrator.  It does not define any
>>    new protocol.
>>
>>
>>
>>
>> Please note that it may take a couple of minutes from the time of submission
>> until the htmlized version and diff are available at tools.ietf.org.
>>
>> The IETF Secretariat
>>
>>
>
> -------------------------------------------------------
> 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
> -------------------------------------------------------
>
>
>
>
>
>
>


From nobody Wed Oct 28 03:42:32 2020
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 35C803A0820; Wed, 28 Oct 2020 03:42:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level: 
X-Spam-Status: No, score=-2.099 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, RCVD_IN_MSPIKE_H2=-0.001, 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=um.es
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 zOSKEo5NUe8U; Wed, 28 Oct 2020 03:42:28 -0700 (PDT)
Received: from mx01.puc.rediris.es (outbound6mad.lav.puc.rediris.es [130.206.19.149]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D1E123A0879; Wed, 28 Oct 2020 03:42:27 -0700 (PDT)
Received: from xenon44.um.es (xenon44.um.es [155.54.212.171]) by mx01.puc.rediris.es  with ESMTP id 09SAgNPt004918-09SAgNPu004918; Wed, 28 Oct 2020 11:42:24 +0100
Received: from localhost (localhost [127.0.0.1]) by xenon44.um.es (Postfix) with ESMTP id E0C1E20737; Wed, 28 Oct 2020 11:42:23 +0100 (CET)
X-Virus-Scanned: by antispam in UMU at xenon44.um.es
Received: from xenon44.um.es ([127.0.0.1]) by localhost (xenon44.um.es [127.0.0.1]) (amavisd-new, port 10024) with LMTP id yoZzTUL1emfR; Wed, 28 Oct 2020 11:42:23 +0100 (CET)
Received: from [192.168.1.33] (135.red-79-150-250.dynamicip.rima-tde.net [79.150.250.135]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: rafa@um.es) by xenon44.um.es (Postfix) with ESMTPSA id 05DBE20706; Wed, 28 Oct 2020 11:42:20 +0100 (CET)
From: Rafa Marin-Lopez <rafa@um.es>
Message-Id: <DDE550B1-9A9E-4954-B6F9-C0A33ECE1275@um.es>
Content-Type: multipart/alternative; boundary="Apple-Mail=_1422706B-31A7-438B-91FF-96852D1AD868"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.14\))
Date: Wed, 28 Oct 2020 11:42:19 +0100
In-Reply-To: <5F9815D1.9010303@btconnect.com>
Cc: Rafa Marin-Lopez <rafa@um.es>, i2nsf@ietf.org, Gabriel Lopez <gabilm@um.es>, Fernando Pereniguez-Garcia <fernando.pereniguez@cud.upct.es>, last-call@ietf.org, ynir.ietf@gmail.com
To: tom petch <daedulus@btconnect.com>
References: <160337357077.29083.9236626834026808055@ietfa.amsl.com> <EE5AB669-73BB-4517-A6F4-23B7807FB36E@um.es> <5F9815D1.9010303@btconnect.com>
X-Mailer: Apple Mail (2.3445.104.14)
X-FEAS-SPF: spf-result=pass, ip=155.54.212.171, helo=xenon44.um.es, mailFrom=rafa@um.es
Authentication-Results: mx01.puc.rediris.es; spf=pass (rediris.es: domain of rafa@um.es designates 155.54.212.171 as permitted sender) smtp.mailfrom=rafa@um.es
X-FE-Policy-ID: 2:15:0:SYSTEM, 2:15:1:upct.es
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=SvT8rdrIJaIw+3103dMqkE4CMMAoD6sFaafZjpjPExY=; b=WeMAYRXNAh/irOewEuIpcYpf9lfarEfNKsS8OUUTwqbNett5luFTOwdoK2QTUrmamk8TNeN4si6E P/T/12EsROObvL/jkXy8YYkSNRLvSW4B0kRULm4gTRkawDCFpOcZbZKkOt0Xv0YdYeTJXxqnnt6k o0gvHnHTtBGrimeIPsSCqpoJJYzGzcy94qoCssgbQhw9Oq6EijD1zXx7PUMHB3wGi2RJiZEGtaHo jJJ2ZbcL4NTl+VBbTl1nKRcd5YkvdRwSjb35ddUIOFVmVIkZh+mTMUkEFCrwjrQhjMviU8nwelvy z8yfD6OpYa+kIOZkiUrH+zJQBIzgi/qTyQskAg==
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2nsf/nT-tpdxrtycfHZqHCwlv6ewpIqs>
Subject: Re: [I2nsf] Fwd: [Last-Call] New Version Notification for draft-ietf-i2nsf-sdn-ipsec-flow-protection-11.txt
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: Wed, 28 Oct 2020 10:42:30 -0000

--Apple-Mail=_1422706B-31A7-438B-91FF-96852D1AD868
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Hi Tom:

Thank you very much for your insight. It is very helpful. Please see our =
comments/questions inline.

> El 27 oct 2020, a las 13:42, tom petch <daedulus@btconnect.com> =
escribi=C3=B3:
>=20
> I think that the IESG will find a number of problems with this I-D.
>=20
> YANG module references RFC822 which is several years out of date

We have realized that we missed to change this, even though we discussed =
it. We will change it right away in the following way (bold):

case rfc822-address-string {
     leaf rfc822-address-string {=20
          type string;=20
          description=20
              "Specifies the identity as a
               fully-qualified RFC5322 email
               address string. An example is,
               jsmith@example.com. The string
               MUST NOT contain any
               terminators e.g., NULL, CR,
               etc.).";=20
           reference=20
                  "RFC 5322.";
     }
}

Btw, we already used in the past =E2=80=9Ccase rfc822-address-string=E2=80=
=9D and =E2=80=9Cleaf rfc822-address-string=E2=80=9D since this is =
coming from IKEv2 standard. Do you think we should change that name as =
well?


>=20
> YANG module references IANA Protocol Numbers which is not in the I-D =
references

We have included the following reference:

[IANA-Protocols-Number]
              Internet Assigned Numbers Authority (IANA), "Protocol
              Numbers", January 2020.


>=20
> s.2 boiler plate is out of date

What we see is the I-D has the second choice stated in =
https://www.ietf.org/standards/ids/guidelines/

This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at https://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

Could you refer what is out of date?
=20
>=20
> XXXX is standing in for more than one RFC

Yes, XXXX has been used because we do not know the future number =
assigned to our I-D.=20

Also we realized we also included this to refer to crypto-types I-D but =
this has been solved now in a new version -12 that we are preparing to =
include your comments. We noticed we can replace the type of rw =
cert-data?, ca-data*, crl-data? for binary without any problem.

|           |     +--rw cert-data?        binary
|           +--rw private-key?            binary
|           +--rw ca-data*                binary
|           +--rw crl-data?               binary

>=20
> but the show stopper that makes a proper review of this too costly is =
the references.  Those to IANA of which there are several I want to =
pursue.  The I-D reference is to IKEv2 parameters. Sadly, this is a =
three tier structure and noone agrees on what to call the third tier so =
I will call it tier3 here.  Top level is Group, as per RFC8126, second =
level is Registry.  The I-D reference is to the Group only which is fine =
if the actual reference then specifies the Registry and Tier3 but they =
never do, usually just Tier3 e.g. Transform Type 3 which makes for a lot =
of work for the reader, too much for this one.  You have to go hunting =
in all the second level Registry until you can find a match for the =
Tier3 identifier. And there are no URL.  If you want an example that I =
find easy to use, go look at RFC8407 (as usual).

You=E2=80=99re right. Could you point the exact part at RFC 8407 with =
that example? We would really appreciate it.

On the other hand, would it be enough to include the URL for Transform =
Type 3 =
https://www.iana.org/assignments/ikev2-parameters/ikev2-parameters.xhtml#i=
kev2-parameters-7 ?

(Same for Transform Type 1, Transform Type 4)

>=20
> The reference for import of i2nsf-ikec gives a YANG module name; this =
needs to be the name of the RFC to be

Fixed.

import ietf-i2nsf-ikec {
            prefix nsfikec;
            reference=20
                "RFC XXXX: Software-Defined Networking
               (SDN)-based IPsec Flow Protection.";
}

We still use XXXX because we do not know the number assigned to the RFC =
to be.

>=20
> The example IPv6 address in the YANG module has :0:0: which is usually =
just ::

Fixed.=20

If you have any further comments, please let us know so we can include =
them in -12

Best Regards.
>=20
> And I have some way to go still.
>=20
> Tom Petch
>=20
> On 22/10/2020 18:39, Rafa Marin-Lopez wrote:
>> Dear all:
>>=20
>> After receiving a suggestion to make things clearer in the feature =
ikeless-notification description, we have just uploaded a new version =
-11 with a minor change to add the following text:
>>=20
>> feature ikeless-notification {
>>             description
>>                 "This feature indicates that the server supports
>>                 generating notifications in the ikeless module.
>>=20
>>                 To ensure broader applicability of this module,
>>                 the notifications are marked as a feature.
>>                 For the implementation of ikeless case,
>>                 the NSF is expected to implement this
>>                 feature.";
>>         }
>>=20
>> Best Regards.
>>=20
>>> Inicio del mensaje reenviado:
>>>=20
>>> De: internet-drafts@ietf.org
>>> Asunto: New Version Notification for =
draft-ietf-i2nsf-sdn-ipsec-flow-protection-11.txt
>>> Fecha: 22 de octubre de 2020, 15:32:50 CEST
>>> Para: "Fernando Pereniguez-Garcia" =
<fernando.pereniguez@cud.upct.es>, "Rafael Lopez" <rafa@um.es>, "Gabriel =
Lopez-Millan" <gabilm@um.es>, "Rafa Marin-Lopez" <rafa@um.es>
>>>=20
>>>=20
>>> A new version of I-D, =
draft-ietf-i2nsf-sdn-ipsec-flow-protection-11.txt
>>> has been successfully submitted by Rafa Marin-Lopez and posted to =
the
>>> IETF repository.
>>>=20
>>> Name:		draft-ietf-i2nsf-sdn-ipsec-flow-protection
>>> Revision:	11
>>> Title:		Software-Defined Networking (SDN)-based IPsec =
Flow Protection
>>> Document date:	2020-10-22
>>> Group:		i2nsf
>>> Pages:		92
>>> URL:            =
https://www.ietf.org/archive/id/draft-ietf-i2nsf-sdn-ipsec-flow-protection=
-11.txt
>>> Status:         =
https://datatracker.ietf.org/doc/draft-ietf-i2nsf-sdn-ipsec-flow-protectio=
n/
>>> Htmlized:       =
https://datatracker.ietf.org/doc/html/draft-ietf-i2nsf-sdn-ipsec-flow-prot=
ection
>>> Htmlized:       =
https://tools.ietf.org/html/draft-ietf-i2nsf-sdn-ipsec-flow-protection-11
>>> Diff:           =
https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-i2nsf-sdn-ipsec-flow-protec=
tion-11
>>>=20
>>> Abstract:
>>>   This document describes how to provide IPsec-based flow protection
>>>   (integrity and confidentiality) by means of an Interface to =
Network
>>>   Security Function (I2NSF) controller.  It considers two main well-
>>>   known scenarios in IPsec: (i) gateway-to-gateway and (ii) host-to-
>>>   host.  The service described in this document allows the
>>>   configuration and monitoring of IPsec Security Associations (SAs)
>>>   from a I2NSF Controller to one or several flow-based Network =
Security
>>>   Functions (NSFs) that rely on IPsec to protect data traffic.
>>>=20
>>>   The document focuses on the I2NSF NSF-facing interface by =
providing
>>>   YANG data models for configuring the IPsec databases (SPD, SAD, =
PAD)
>>>   and IKEv2.  This allows IPsec SA establishment with minimal
>>>   intervention by the network administrator.  It does not define any
>>>   new protocol.
>>>=20
>>>=20
>>>=20
>>>=20
>>> Please note that it may take a couple of minutes from the time of =
submission
>>> until the htmlized version and diff are available at tools.ietf.org.
>>>=20
>>> The IETF Secretariat
>>>=20
>>>=20
>>=20
>> -------------------------------------------------------
>> 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
>> -------------------------------------------------------
>>=20
>>=20
>>=20
>>=20
>>=20
>>=20
>>=20

-------------------------------------------------------
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
-------------------------------------------------------





--Apple-Mail=_1422706B-31A7-438B-91FF-96852D1AD868
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: after-white-space;" class=3D""><div =
dir=3D"auto" style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
line-break: after-white-space;" class=3D"">Hi Tom:<div class=3D""><br =
class=3D""></div><div class=3D"">Thank you very much for your insight. =
It is very helpful. Please see our comments/questions inline.<br =
class=3D""><div><br class=3D""><blockquote type=3D"cite" class=3D""><div =
class=3D"">El 27 oct 2020, a las 13:42, tom petch &lt;<a =
href=3D"mailto:daedulus@btconnect.com" =
class=3D"">daedulus@btconnect.com</a>&gt; escribi=C3=B3:</div><br =
class=3D"Apple-interchange-newline"><div class=3D""><div class=3D"">I =
think that the IESG will find a number of problems with this I-D.<br =
class=3D""><br class=3D"">YANG module references RFC822 which is several =
years out of date<br class=3D""></div></div></blockquote><div><br =
class=3D""></div><div>We have realized that we missed to change this, =
even though we discussed it. We will change it right away in the =
following way (bold):</div><div><br class=3D""></div><div>case =
rfc822-address-string {<br class=3D"">&nbsp; &nbsp; &nbsp;leaf =
rfc822-address-string {&nbsp;<br class=3D"">&nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; type string;&nbsp;<br class=3D"">&nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; description&nbsp;<br class=3D"">&nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; "Specifies the identity as a<br class=3D"">&nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;fully-qualified <b =
class=3D"">RFC5322</b> email<br class=3D"">&nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp;address string. An example is,<br =
class=3D"">&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;<a =
href=3D"mailto:jsmith@example.com" class=3D"">jsmith@example.com</a>. =
The string<br class=3D"">&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp;MUST NOT contain any<br class=3D"">&nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;terminators e.g., NULL, CR,<br =
class=3D"">&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;etc.).";&nbsp;<br class=3D"">&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;reference&nbsp;<br class=3D"">&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; "<b class=3D"">RFC 5322</b>.";<br =
class=3D"">&nbsp; &nbsp; &nbsp;}<br class=3D"">}</div><div><br =
class=3D""></div><div>Btw, we already used in the past =E2=80=9Ccase =
rfc822-address-string=E2=80=9D and =E2=80=9Cleaf =
rfc822-address-string=E2=80=9D since this is coming from IKEv2 standard. =
Do you think we should change that name as well?</div><div><br =
class=3D""></div><div><br class=3D""></div><blockquote type=3D"cite" =
class=3D""><div class=3D""><div class=3D""><br class=3D"">YANG module =
references IANA Protocol Numbers which is not in the I-D references<br =
class=3D""></div></div></blockquote><div><br class=3D""></div>We have =
included the following reference:</div><div><br =
class=3D""></div><div><div>[IANA-Protocols-Number]</div><div>&nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Internet Assigned Numbers =
Authority (IANA), "Protocol</div><div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; Numbers", January 2020.</div><div class=3D""><br =
class=3D""></div></div><div><br class=3D""><blockquote type=3D"cite" =
class=3D""><div class=3D""><div class=3D""><br class=3D"">s.2 boiler =
plate is out of date<br class=3D""></div></div></blockquote><div><br =
class=3D""></div><div>What we see is the I-D has the second choice =
stated in <a href=3D"https://www.ietf.org/standards/ids/guidelines/" =
class=3D"">https://www.ietf.org/standards/ids/guidelines/</a></div><div><b=
r class=3D""></div><div><div class=3D"">This Internet-Draft is submitted =
in full conformance with the</div><div class=3D"">&nbsp; =
&nbsp;provisions of BCP 78 and BCP 79.</div><div class=3D""><br =
class=3D""></div><div class=3D"">&nbsp; &nbsp;Internet-Drafts are =
working documents of the Internet Engineering</div><div class=3D"">&nbsp; =
&nbsp;Task Force (IETF). &nbsp;Note that other groups may also =
distribute</div><div class=3D"">&nbsp; &nbsp;working documents as =
Internet-Drafts. &nbsp;The list of current Internet-</div><div =
class=3D"">&nbsp; &nbsp;Drafts is at <a =
href=3D"https://datatracker.ietf.org/drafts/current/" =
class=3D"">https://datatracker.ietf.org/drafts/current/</a>.</div><div =
class=3D""><br class=3D""></div><div class=3D"">&nbsp; =
&nbsp;Internet-Drafts are draft documents valid for a maximum of six =
months</div><div class=3D"">&nbsp; &nbsp;and may be updated, replaced, =
or obsoleted by other documents at any</div><div class=3D"">&nbsp; =
&nbsp;time. &nbsp;It is inappropriate to use Internet-Drafts as =
reference</div><div class=3D"">&nbsp; &nbsp;material or to cite them =
other than as "work in progress."</div></div><div><br =
class=3D""></div><div>Could you refer what is out of =
date?</div><div>&nbsp;</div><blockquote type=3D"cite" class=3D""><div =
class=3D""><div class=3D""><br class=3D"">XXXX is standing in for more =
than one RFC<br class=3D""></div></div></blockquote><div><br =
class=3D""></div><div>Yes, XXXX has been used because we do not know the =
future number assigned to our I-D.&nbsp;</div><div><br =
class=3D""></div><div>Also we realized we also included this to refer to =
crypto-types I-D but this has been solved now in a new version -12 that =
we are preparing to include your comments. We noticed we can replace the =
type of&nbsp;rw cert-data?,&nbsp;ca-data*,&nbsp;crl-data? for binary =
without any problem.</div><div><br class=3D""></div><div>|&nbsp;&nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp;&nbsp;|&nbsp;&nbsp; &nbsp;&nbsp;+--rw =
cert-data?&nbsp; &nbsp; &nbsp; &nbsp;&nbsp;binary<br =
class=3D"">|&nbsp;&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;&nbsp;+--rw =
private-key?&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;&nbsp;binary<br =
class=3D"">|&nbsp;&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;&nbsp;+--rw =
ca-data*&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;&nbsp;binary<br class=3D"">|&nbsp;&nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;&nbsp;+--rw crl-data?&nbsp;&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp;&nbsp;binary</div><br class=3D""><blockquote type=3D"cite" =
class=3D""><div class=3D""><div class=3D""><br class=3D"">but the show =
stopper that makes a proper review of this too costly is the references. =
&nbsp;Those to IANA of which there are several I want to pursue. =
&nbsp;The I-D reference is to IKEv2 parameters. Sadly, this is a three =
tier structure and noone agrees on what to call the third tier so I will =
call it tier3 here. &nbsp;Top level is Group, as per RFC8126, second =
level is Registry. &nbsp;The I-D reference is to the Group only which is =
fine if the actual reference then specifies the Registry and Tier3 but =
they never do, usually just Tier3 e.g. Transform Type 3 which makes for =
a lot of work for the reader, too much for this one. &nbsp;You have to =
go hunting in all the second level Registry until you can find a match =
for the Tier3 identifier. And there are no URL. &nbsp;If you want an =
example that I find easy to use, go look at RFC8407 (as usual).<br =
class=3D""></div></div></blockquote><div><br =
class=3D""></div><div>You=E2=80=99re right. Could you point the exact =
part at RFC 8407 with that example? We would really appreciate =
it.</div><div><br class=3D""></div><div>On the other hand, would it be =
enough to include the URL for Transform Type 3 <a =
href=3D"https://www.iana.org/assignments/ikev2-parameters/ikev2-parameters=
.xhtml#ikev2-parameters-7" =
class=3D"">https://www.iana.org/assignments/ikev2-parameters/ikev2-paramet=
ers.xhtml#ikev2-parameters-7</a> ?</div><div><br =
class=3D""></div><div>(Same for Transform Type 1, Transform Type =
4)</div><br class=3D""><blockquote type=3D"cite" class=3D""><div =
class=3D""><div class=3D""><br class=3D"">The reference for import of =
i2nsf-ikec gives a YANG module name; this needs to be the name of the =
RFC to be<br class=3D""></div></div></blockquote><div><br =
class=3D""></div><div>Fixed.</div><div><br =
class=3D""></div><div><div>import ietf-i2nsf-ikec {</div><div>&nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; prefix nsfikec;</div><div>&nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; reference&nbsp;</div><div>&nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; <b class=3D"">"RFC =
XXXX: Software-Defined Networking</b></div><div><b class=3D"">&nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;(SDN)-based IPsec Flow =
Protection."</b>;</div><div>}</div><div><br class=3D""></div><div>We =
still use XXXX because we do not know the number assigned to the RFC to =
be.</div></div><br class=3D""><blockquote type=3D"cite" class=3D""><div =
class=3D""><div class=3D""><br class=3D"">The example IPv6 address in =
the YANG module has :0:0: which is usually just ::<br =
class=3D""></div></div></blockquote><div><br =
class=3D""></div>Fixed.&nbsp;</div><div><br class=3D""></div><div>If you =
have any further comments, please let us know so we can include them in =
-12</div><div><br class=3D""></div><div>Best Regards.<br =
class=3D""><blockquote type=3D"cite" class=3D""><div class=3D""><div =
class=3D""><br class=3D"">And I have some way to go still.<br =
class=3D""><br class=3D"">Tom Petch<br class=3D""><br class=3D"">On =
22/10/2020 18:39, Rafa Marin-Lopez wrote:<br class=3D""><blockquote =
type=3D"cite" class=3D"">Dear all:<br class=3D""><br class=3D"">After =
receiving a suggestion to make things clearer in the feature =
ikeless-notification description, we have just uploaded a new version =
-11 with a minor change to add the following text:<br class=3D""><br =
class=3D"">feature ikeless-notification {<br class=3D""> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;de=
scription<br class=3D""> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;"This feature indicates that the server =
supports<br class=3D""> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;generating notifications in the ikeless module.<br =
class=3D""><br class=3D""> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;To ensure broader applicability of this module,<br =
class=3D""> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;the notifications are marked as a feature.<br =
class=3D""> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;For the implementation of ikeless case,<br =
class=3D""> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;the NSF is expected to implement this<br class=3D"">=
 =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;feature.";<br class=3D""> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;}<br class=3D""><br =
class=3D"">Best Regards.<br class=3D""><br class=3D""><blockquote =
type=3D"cite" class=3D"">Inicio del mensaje reenviado:<br class=3D""><br =
class=3D"">De: <a href=3D"mailto:internet-drafts@ietf.org" =
class=3D"">internet-drafts@ietf.org</a><br class=3D"">Asunto: New =
Version Notification for =
draft-ietf-i2nsf-sdn-ipsec-flow-protection-11.txt<br class=3D"">Fecha: =
22 de octubre de 2020, 15:32:50 CEST<br class=3D"">Para: "Fernando =
Pereniguez-Garcia" &lt;<a href=3D"mailto:fernando.pereniguez@cud.upct.es" =
class=3D"">fernando.pereniguez@cud.upct.es</a>&gt;, "Rafael Lopez" =
&lt;<a href=3D"mailto:rafa@um.es" class=3D"">rafa@um.es</a>&gt;, =
"Gabriel Lopez-Millan" &lt;<a href=3D"mailto:gabilm@um.es" =
class=3D"">gabilm@um.es</a>&gt;, "Rafa Marin-Lopez" &lt;<a =
href=3D"mailto:rafa@um.es" class=3D"">rafa@um.es</a>&gt;<br class=3D""><br=
 class=3D""><br class=3D"">A new version of I-D, =
draft-ietf-i2nsf-sdn-ipsec-flow-protection-11.txt<br class=3D"">has been =
successfully submitted by Rafa Marin-Lopez and posted to the<br =
class=3D"">IETF repository.<br class=3D""><br class=3D"">Name:<span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</span><span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</span>draft-ietf-i2nsf-sdn-ipsec-flow-protection<br =
class=3D"">Revision:<span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</span>11<br class=3D"">Title:<span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</span><span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</span>Software-Defined Networking (SDN)-based IPsec Flow Protection<br =
class=3D"">Document date:<span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</span>2020-10-22<br =
class=3D"">Group:<span class=3D"Apple-tab-span" style=3D"white-space:pre">=
	</span><span class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</span>i2nsf<br class=3D"">Pages:<span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</span><span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</span>92<br class=3D"">URL: =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a =
href=3D"https://www.ietf.org/archive/id/draft-ietf-i2nsf-sdn-ipsec-flow-pr=
otection-11.txt" =
class=3D"">https://www.ietf.org/archive/id/draft-ietf-i2nsf-sdn-ipsec-flow=
-protection-11.txt</a><br class=3D"">Status: =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a =
href=3D"https://datatracker.ietf.org/doc/draft-ietf-i2nsf-sdn-ipsec-flow-p=
rotection/" =
class=3D"">https://datatracker.ietf.org/doc/draft-ietf-i2nsf-sdn-ipsec-flo=
w-protection/</a><br class=3D"">Htmlized: =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a =
href=3D"https://datatracker.ietf.org/doc/html/draft-ietf-i2nsf-sdn-ipsec-f=
low-protection" =
class=3D"">https://datatracker.ietf.org/doc/html/draft-ietf-i2nsf-sdn-ipse=
c-flow-protection</a><br class=3D"">Htmlized: =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a =
href=3D"https://tools.ietf.org/html/draft-ietf-i2nsf-sdn-ipsec-flow-protec=
tion-11" =
class=3D"">https://tools.ietf.org/html/draft-ietf-i2nsf-sdn-ipsec-flow-pro=
tection-11</a><br class=3D"">Diff: =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a =
href=3D"https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-i2nsf-sdn-ipsec-flo=
w-protection-11" =
class=3D"">https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-i2nsf-sdn-ipsec-=
flow-protection-11</a><br class=3D""><br class=3D"">Abstract:<br =
class=3D""> &nbsp;&nbsp;This document describes how to provide =
IPsec-based flow protection<br class=3D""> &nbsp;&nbsp;(integrity and =
confidentiality) by means of an Interface to Network<br class=3D""> =
&nbsp;&nbsp;Security Function (I2NSF) controller. &nbsp;It considers two =
main well-<br class=3D""> &nbsp;&nbsp;known scenarios in IPsec: (i) =
gateway-to-gateway and (ii) host-to-<br class=3D""> &nbsp;&nbsp;host. =
&nbsp;The service described in this document allows the<br class=3D""> =
&nbsp;&nbsp;configuration and monitoring of IPsec Security Associations =
(SAs)<br class=3D""> &nbsp;&nbsp;from a I2NSF Controller to one or =
several flow-based Network Security<br class=3D""> &nbsp;&nbsp;Functions =
(NSFs) that rely on IPsec to protect data traffic.<br class=3D""><br =
class=3D""> &nbsp;&nbsp;The document focuses on the I2NSF NSF-facing =
interface by providing<br class=3D""> &nbsp;&nbsp;YANG data models for =
configuring the IPsec databases (SPD, SAD, PAD)<br class=3D""> =
&nbsp;&nbsp;and IKEv2. &nbsp;This allows IPsec SA establishment with =
minimal<br class=3D""> &nbsp;&nbsp;intervention by the network =
administrator. &nbsp;It does not define any<br class=3D""> =
&nbsp;&nbsp;new protocol.<br class=3D""><br class=3D""><br class=3D""><br =
class=3D""><br class=3D"">Please note that it may take a couple of =
minutes from the time of submission<br class=3D"">until the htmlized =
version and diff are available at <a href=3D"http://tools.ietf.org" =
class=3D"">tools.ietf.org</a>.<br class=3D""><br class=3D"">The IETF =
Secretariat<br class=3D""><br class=3D""><br class=3D""></blockquote><br =
class=3D"">-------------------------------------------------------<br =
class=3D"">Rafa Marin-Lopez, PhD<br class=3D"">Dept. Information and =
Communications Engineering (DIIC)<br class=3D"">Faculty of Computer =
Science-University of Murcia<br class=3D"">30100 Murcia - Spain<br =
class=3D"">Telf: +34868888501 Fax: +34868884151 <a =
href=3D"mailto:rafa@um.es" class=3D"">e-mail: rafa@um.es</a><br =
class=3D"">-------------------------------------------------------<br =
class=3D""><br class=3D""><br class=3D""><br class=3D""><br class=3D""><br=
 class=3D""><br class=3D""><br =
class=3D""></blockquote></div></div></blockquote></div><br class=3D""><div=
 class=3D"">
<div style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space;" class=3D""><div style=3D"color: =
rgb(0, 0, 0); font-family: Courier; font-size: 16px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
orphans: auto; text-align: start; text-indent: 0px; text-transform: =
none; white-space: normal; widows: auto; word-spacing: 0px; =
-webkit-text-stroke-width: =
0px;">-------------------------------------------------------<br =
class=3D"">Rafa Marin-Lopez, PhD<br class=3D"">Dept. Information =
and&nbsp;Communications&nbsp;Engineering (DIIC)<br class=3D"">Faculty of =
Computer&nbsp;Science-University of&nbsp;Murcia<br class=3D"">30100 =
Murcia - Spain<br class=3D"">Telf: +34868888501 Fax:&nbsp;+34868884151 =
<a href=3D"mailto:rafa@um.es" class=3D"">e-mail:&nbsp;rafa@um.es</a><br =
class=3D"">-------------------------------------------------------</div><d=
iv style=3D"color: rgb(0, 0, 0); font-family: Courier; font-size: 16px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; orphans: auto; text-align: start; text-indent: =
0px; text-transform: none; white-space: normal; widows: auto; =
word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=3D""><br =
class=3D""></div><br class=3D"Apple-interchange-newline"></div><br =
class=3D"Apple-interchange-newline">
</div>
<br class=3D""></div></div></body></html>=

--Apple-Mail=_1422706B-31A7-438B-91FF-96852D1AD868--


From nobody Wed Oct 28 11:02:25 2020
Return-Path: <daedulus@btconnect.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 7C7CE3A0AAB; Wed, 28 Oct 2020 11:02:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.147
X-Spam-Level: 
X-Spam-Status: No, score=-2.147 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, MSGID_FROM_MTA_HEADER=0.001, NICE_REPLY_A=-0.247, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=btconnect.onmicrosoft.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 Yv1cDF8jyIo0; Wed, 28 Oct 2020 11:02:21 -0700 (PDT)
Received: from EUR01-HE1-obe.outbound.protection.outlook.com (mail-eopbgr130113.outbound.protection.outlook.com [40.107.13.113]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 64AB23A0AA9; Wed, 28 Oct 2020 11:02:20 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=Ww5ISKdziyL+B4pco3zL6fd6MnSOj9da5A2gBeQIGVUYPcGYah4pmv7wajxG95ixTPA/uMq+tyVE9e2pAsYUk3Sp7LeKLNue+GKHDBeZ+Wruz7IlIgUxLhiLZWIEmdQdb8nRpbia7nSTz8C9+8miJqerZbkLwPai4RY60DdhUaZPV2VCyZsUHBSN4TYvsrr/bUClKbd4cb7OM0VAta8iQdDET/DZT37yBk4yg8i8C6ZTJhO/D5xX3Z3ONJm/xC0gy0n9RPBKqpCOXcSgtmBZTxvFkbNUg4In/i9PfTc0ObZK6rYyUP/2RLwxORjpAU+yHJr+LoD5koGOYjTMkAGR+Q==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=l5oSe4CIOKZYtZZk6Nt+tbrkTMMZdv28N448rxQPsUU=; b=EeFzZJ8x92HNwdUIxvTF5OBzhaJ4SWn42sdB3xtvk5D+KKXS4AftS8JB7um7PG/HJF/wbVgkFXpz5/jQZUq6U76baQuAu43VL6U6WC5psBmv9d3iZ6rGol3gcpRY6LZ2QifWzGCFs1oVHohxVlmbQF9qXYPOtFNauPTSpM7eMhkjhH8c/ClraCAybxZ2xqr2vtEgnRQCgiyNeqbT5dgNBYfeCZs0iMsJjpHxJDMHXwnj/90Uh/vGxoMyKEZGlQ6pvDzPZoCzGsgOezC2kIMxgr5uOXdGsGigf6NdKUVAi0NfVoWgQAkGQnPEtK2CiZamWPWtvl4YBV9l3tOBxsrF+Q==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=btconnect.com; dmarc=pass action=none header.from=btconnect.com; dkim=pass header.d=btconnect.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=btconnect.onmicrosoft.com; s=selector2-btconnect-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=l5oSe4CIOKZYtZZk6Nt+tbrkTMMZdv28N448rxQPsUU=; b=WPzMwJMHrBvgrl8zg4nf+wCWzevKNvq/nzCdCnvrW+ZFPPH7VJE2Pt8sdiAoRUlGV6Lm3wCuuEl39kfnpftdJv3nXZpM5vTQVlJpZgNftP9bGuwBXlnDr9RYX7DFlYKCyKumevxjhNGBQA+rbFafxIo679kUDTlhaIb4A7hr7YA=
Authentication-Results: gmail.com; dkim=none (message not signed) header.d=none;gmail.com; dmarc=none action=none header.from=btconnect.com;
Received: from VI1PR07MB6704.eurprd07.prod.outlook.com (2603:10a6:800:18b::8) by VI1PR0701MB2544.eurprd07.prod.outlook.com (2603:10a6:800:70::16) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3499.4; Wed, 28 Oct 2020 18:02:17 +0000
Received: from VI1PR07MB6704.eurprd07.prod.outlook.com ([fe80::6165:9c1c:e5b1:15db]) by VI1PR07MB6704.eurprd07.prod.outlook.com ([fe80::6165:9c1c:e5b1:15db%4]) with mapi id 15.20.3477.021; Wed, 28 Oct 2020 18:02:17 +0000
To: Rafa Marin-Lopez <rafa@um.es>
References: <160337357077.29083.9236626834026808055@ietfa.amsl.com> <EE5AB669-73BB-4517-A6F4-23B7807FB36E@um.es> <5F9815D1.9010303@btconnect.com> <DDE550B1-9A9E-4954-B6F9-C0A33ECE1275@um.es>
Cc: i2nsf@ietf.org, Gabriel Lopez <gabilm@um.es>, Fernando Pereniguez-Garcia <fernando.pereniguez@cud.upct.es>, last-call@ietf.org, ynir.ietf@gmail.com
From: tom petch <daedulus@btconnect.com>
Message-ID: <5F99B221.3040504@btconnect.com>
Date: Wed, 28 Oct 2020 18:02:09 +0000
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:38.0) Gecko/20100101 Thunderbird/38.5.0
In-Reply-To: <DDE550B1-9A9E-4954-B6F9-C0A33ECE1275@um.es>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
X-Originating-IP: [86.146.121.140]
X-ClientProxiedBy: LNXP123CA0014.GBRP123.PROD.OUTLOOK.COM (2603:10a6:600:d2::26) To VI1PR07MB6704.eurprd07.prod.outlook.com (2603:10a6:800:18b::8)
MIME-Version: 1.0
X-MS-Exchange-MessageSentRepresentingType: 1
Received: from [192.168.1.65] (86.146.121.140) by LNXP123CA0014.GBRP123.PROD.OUTLOOK.COM (2603:10a6:600:d2::26) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.20.3499.18 via Frontend Transport; Wed, 28 Oct 2020 18:02:16 +0000
X-MS-PublicTrafficType: Email
X-MS-Office365-Filtering-Correlation-Id: a7f50387-9eaf-47a9-d099-08d87b6b9b4c
X-MS-TrafficTypeDiagnostic: VI1PR0701MB2544:
X-Microsoft-Antispam-PRVS: <VI1PR0701MB2544D78AF621AF9866D28676C6170@VI1PR0701MB2544.eurprd07.prod.outlook.com>
X-MS-Oob-TLC-OOBClassifiers: OLM:8273;
X-MS-Exchange-SenderADCheck: 1
X-Microsoft-Antispam: BCL:0;
X-Microsoft-Antispam-Message-Info: 5lVrM3hlHH0LVK2ZwVXT0CJ4KyBkJtM6eMLTEl6CsL5eRFOO6AzSA0gPVrGCPaEacU+kAPibglR/BoGL6G5x12TT3S1B01L6hl15Q35aTYnUqszoTdZloJIw0VBgsVcPx/xFeXcbzlDVe+70ujApsAHtuLGP6HOwqujwwv36qjZbhzl0Qf3FHHYD0EcByFkc0oQDngfXe10UEfboVuAfy4THFuu7SYetVXTbAjrtysQynU5fA1CRkiJWf/qQeYnJZ6M23xephUlL2cgfKQDaY1RAjYa5g5s4c+1h6I3Yjq+U2tbKLVKbwsfBIN6BzOe9yBQySYU3om5n1qoIHZ01w1WeXkjO2kcSURThhpR2aJd/9zSS6ZIzrzDREwt3/D3epCi4ZGEna17rezFpFUWTpg==
X-Forefront-Antispam-Report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;  IPV:NLI; SFV:NSPM; H:VI1PR07MB6704.eurprd07.prod.outlook.com; PTR:; CAT:NONE;  SFS:(366004)(376002)(39860400002)(346002)(136003)(396003)(4326008)(26005)(6666004)(186003)(2616005)(2906002)(66476007)(66946007)(33656002)(966005)(30864003)(66556008)(15650500001)(478600001)(16576012)(5660300002)(8936002)(956004)(6916009)(6486002)(36756003)(316002)(16526019)(4001150100001)(8676002)(83380400001)(86362001)(66574015)(52116002)(53546011)(54906003)(87266011); DIR:OUT; SFP:1102; 
X-MS-Exchange-AntiSpam-MessageData: sffX6Iz/6w2sq+/qApMoNuxJDpD4m1PW9+FV3zK3ZWPhESksKaBqQaqD5gg5EhZ8fZ9rykMLrEoxTIo4oyx3Vs/0LVixMBLnY79rfrUgtHBiPHWeRNU5PhNgiik5hrTVaIkQTcQJix0RPgKO/LX5I9Kx4Hdm2/67TWCsMzMEOUZUKXpx4liPdgMXzysd7kPjGViC8D11+lDcJUsFsKpegypwr/zrSPOggdxHeNCMMwjD+PKeZjQHITJljln9vfvBKghtd376WcmwnvC5FolzqzjZsLChD1LdoOt/c7YZ+DsmgqFmdiXQKMYgitqeVpdBfiX32Mp5LXTFInYPm2HxFX6TII81c+OC3oUCB0aONIjQVeLKrbEMDDWxF9Lu1LpsT1x0wwPPt+5xgaBxq1xZYOjg0jm+RSZcSQoEAux9VRbAyoomnOnwMnV3YSqFWCcYXyCmhQxnnAsHLcSR8NNLX0Qce3nW/ngyutyVlzd/4u682oD+ZLl0zEriQmDikylmZdF2FWqiocSC+8wV+zSt3VfDI9qJDllg54trRv6uh+iFBKFYjzZWH4hHovuz4XuV7uFX3ZbCP+y/dkvG3Gk2Q39rljIqYiVsViz3K7PB5sNzs6TyU/SEAWGSiBwxR9v28RHSw7mWKoGUoX/VzrSnZQ==
X-OriginatorOrg: btconnect.com
X-MS-Exchange-CrossTenant-Network-Message-Id: a7f50387-9eaf-47a9-d099-08d87b6b9b4c
X-MS-Exchange-CrossTenant-AuthSource: VI1PR07MB6704.eurprd07.prod.outlook.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 28 Oct 2020 18:02:17.1767 (UTC)
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-CrossTenant-Id: cf8853ed-96e5-465b-9185-806bfe185e30
X-MS-Exchange-CrossTenant-MailboxType: HOSTED
X-MS-Exchange-CrossTenant-UserPrincipalName: oLpRhE896JgZNHW9HUEPEdu+rAo1J2fE8xQW0EKfNZ4w6RJWI46o03V15CbZVlVx1O3Y3EBo6izURzJBVTwmDQ==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: VI1PR0701MB2544
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2nsf/S5FWZz06OfH4UnEBvfPBrfgbFBA>
Subject: Re: [I2nsf] Fwd: [Last-Call] New Version Notification for draft-ietf-i2nsf-sdn-ipsec-flow-protection-11.txt
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: Wed, 28 Oct 2020 18:02:24 -0000

On 28/10/2020 10:42, Rafa Marin-Lopez wrote:
> Hi Tom:
>
> Thank you very much for your insight. It is very helpful. Please see our comments/questions inline.
>
>> El 27 oct 2020, a las 13:42, tom petch <daedulus@btconnect.com> escribió:
>>
>> I think that the IESG will find a number of problems with this I-D.
>>
>> YANG module references RFC822 which is several years out of date

Rafa

On boiler plate, I mean the reference to RFC2119 which now must use the 
language from RFC8174 in the body of the I-D; sorry for the confusion.

On XXXX, you have XXXX standing in for more than one RFC-to-be which 
confuses.  The convention is to use XXXX for this I-D and then AAAA BBBB 
etc for any others such as the netconf I-D in this instance.

Two big issues, for me (perhaps not for others).  The convention with 
YANG is for each successive line to be indented two characters, you have 
four, which creates a lot of white space and pushes the text to the 
right hand margin.  I think that two characters is the default when you 
use pyang to format a YANG module.

And references.  I have had to work harder than I want to to make sense 
of the IANA references.  I think you should have five separate 
references in the I-D for IANA for
Transform Type 1
Transform Type 3
Transform Type 4
Authentication Method
Protocol Numbers
and each reference in the I-D should have a URL pointing to the specific 
section of IANA web site.
In the YANG, it is harder to know what to do.  Those first three 
references are in the third tier i.e.
Group - Internet Key Exchange V2 (IKEv2) Parameters
Registry  -Transform Attribute Types
and then Type 1, 3, 4 as the third tier as I am calling it
and I think that every reference in the YANG should give me all three 
tiers after IANA in that order perhaps
IANA; IKEv2 Parameters; Transform Atribute Types; Transform Type 1
If the syntax needs tweeking, then the RFC Editor will do a good job of 
that but at present the references are inconsistent in which elements 
are specified in what order and that is something the RFC Editor 
probably cannot cope with.
Authentication Method is a registry so that just needs Group name and 
Registry name after IANA.

Some minor glitches.
I-D appears twice in the body of the I-D - perhaps document or memo.
objetives/objectives/
end port number perhaps /must/MUST/
and YANG is very good at including such checks with a must ....
'If AEAD is used .. where? this occurs in several places and I think 
that you need to specify the leaf where AEAD will be specified or implied.
And is it possible to make that a YANG 'must' statement - looking at the 
IKEv2 registries it is not obvious which are AEAD so that might be more 
complexity than it is worth.
'only available on linux kernels' Um implementation detail, you may get 
asked to remove that altogether or at least to a Informative Appendix - 
I would leave it in for now.
'import ietf-i2nsf-ikec' the reference needs to be to a RFC and if it is 
not yet an RFC then RFC XXXX <title> in both Appendix B and C
leaf-list pfs-groups could do with a reference - Transform Type 4?

I am still working my way through the YANG so may have some more 
comments tomorrow.

Tom Petch














> We have realized that we missed to change this, even though we discussed it. We will change it right away in the following way (bold):
>
> case rfc822-address-string {
>       leaf rfc822-address-string {
>            type string;
>            description
>                "Specifies the identity as a
>                 fully-qualified RFC5322 email
>                 address string. An example is,
>                 jsmith@example.com. The string
>                 MUST NOT contain any
>                 terminators e.g., NULL, CR,
>                 etc.).";
>             reference
>                    "RFC 5322.";
>       }
> }
>
> Btw, we already used in the past “case rfc822-address-string” and “leaf rfc822-address-string” since this is coming from IKEv2 standard. Do you think we should change that name as well?
>
>
>>
>> YANG module references IANA Protocol Numbers which is not in the I-D references
>
> We have included the following reference:
>
> [IANA-Protocols-Number]
>                Internet Assigned Numbers Authority (IANA), "Protocol
>                Numbers", January 2020.
>
>
>>
>> s.2 boiler plate is out of date
>
> What we see is the I-D has the second choice stated in https://www.ietf.org/standards/ids/guidelines/
>
> This Internet-Draft is submitted in full conformance with the
>     provisions of BCP 78 and BCP 79.
>
>     Internet-Drafts are working documents of the Internet Engineering
>     Task Force (IETF).  Note that other groups may also distribute
>     working documents as Internet-Drafts.  The list of current Internet-
>     Drafts is at https://datatracker.ietf.org/drafts/current/.
>
>     Internet-Drafts are draft documents valid for a maximum of six months
>     and may be updated, replaced, or obsoleted by other documents at any
>     time.  It is inappropriate to use Internet-Drafts as reference
>     material or to cite them other than as "work in progress."
>
> Could you refer what is out of date?
>
>>
>> XXXX is standing in for more than one RFC
>
> Yes, XXXX has been used because we do not know the future number assigned to our I-D.
>
> Also we realized we also included this to refer to crypto-types I-D but this has been solved now in a new version -12 that we are preparing to include your comments. We noticed we can replace the type of rw cert-data?, ca-data*, crl-data? for binary without any problem.
>
> |           |     +--rw cert-data?        binary
> |           +--rw private-key?            binary
> |           +--rw ca-data*                binary
> |           +--rw crl-data?               binary
>
>>
>> but the show stopper that makes a proper review of this too costly is the references.  Those to IANA of which there are several I want to pursue.  The I-D reference is to IKEv2 parameters. Sadly, this is a three tier structure and noone agrees on what to call the third tier so I will call it tier3 here.  Top level is Group, as per RFC8126, second level is Registry.  The I-D reference is to the Group only which is fine if the actual reference then specifies the Registry and Tier3 but they never do, usually just Tier3 e.g. Transform Type 3 which makes for a lot of work for the reader, too much for this one.  You have to go hunting in all the second level Registry until you can find a match for the Tier3 identifier. And there are no URL.  If you want an example that I find easy to use, go look at RFC8407 (as usual).
>
> You’re right. Could you point the exact part at RFC 8407 with that example? We would really appreciate it.
>
> On the other hand, would it be enough to include the URL for Transform Type 3 https://www.iana.org/assignments/ikev2-parameters/ikev2-parameters.xhtml#ikev2-parameters-7 ?
>
> (Same for Transform Type 1, Transform Type 4)
>
>>
>> The reference for import of i2nsf-ikec gives a YANG module name; this needs to be the name of the RFC to be
>
> Fixed.
>
> import ietf-i2nsf-ikec {
>              prefix nsfikec;
>              reference
>                  "RFC XXXX: Software-Defined Networking
>                 (SDN)-based IPsec Flow Protection.";
> }
>
> We still use XXXX because we do not know the number assigned to the RFC to be.
>
>>
>> The example IPv6 address in the YANG module has :0:0: which is usually just ::
>
> Fixed.
>
> If you have any further comments, please let us know so we can include them in -12
>
> Best Regards.
>>
>> And I have some way to go still.
>>
>> Tom Petch
>>
>> On 22/10/2020 18:39, Rafa Marin-Lopez wrote:
>>> Dear all:
>>>
>>> After receiving a suggestion to make things clearer in the feature ikeless-notification description, we have just uploaded a new version -11 with a minor change to add the following text:
>>>
>>> feature ikeless-notification {
>>>              description
>>>                  "This feature indicates that the server supports
>>>                  generating notifications in the ikeless module.
>>>
>>>                  To ensure broader applicability of this module,
>>>                  the notifications are marked as a feature.
>>>                  For the implementation of ikeless case,
>>>                  the NSF is expected to implement this
>>>                  feature.";
>>>          }
>>>
>>> Best Regards.
>>>
>>>> Inicio del mensaje reenviado:
>>>>
>>>> De: internet-drafts@ietf.org
>>>> Asunto: New Version Notification for draft-ietf-i2nsf-sdn-ipsec-flow-protection-11.txt
>>>> Fecha: 22 de octubre de 2020, 15:32:50 CEST
>>>> Para: "Fernando Pereniguez-Garcia" <fernando.pereniguez@cud.upct.es>, "Rafael Lopez" <rafa@um.es>, "Gabriel Lopez-Millan" <gabilm@um.es>, "Rafa Marin-Lopez" <rafa@um.es>
>>>>
>>>>
>>>> A new version of I-D, draft-ietf-i2nsf-sdn-ipsec-flow-protection-11.txt
>>>> has been successfully submitted by Rafa Marin-Lopez and posted to the
>>>> IETF repository.
>>>>
>>>> Name:		draft-ietf-i2nsf-sdn-ipsec-flow-protection
>>>> Revision:	11
>>>> Title:		Software-Defined Networking (SDN)-based IPsec Flow Protection
>>>> Document date:	2020-10-22
>>>> Group:		i2nsf
>>>> Pages:		92
>>>> URL:            https://www.ietf.org/archive/id/draft-ietf-i2nsf-sdn-ipsec-flow-protection-11.txt
>>>> Status:         https://datatracker.ietf.org/doc/draft-ietf-i2nsf-sdn-ipsec-flow-protection/
>>>> Htmlized:       https://datatracker.ietf.org/doc/html/draft-ietf-i2nsf-sdn-ipsec-flow-protection
>>>> Htmlized:       https://tools.ietf.org/html/draft-ietf-i2nsf-sdn-ipsec-flow-protection-11
>>>> Diff:           https://www.ietf.org/rfcdiff?url2=draft-ietf-i2nsf-sdn-ipsec-flow-protection-11
>>>>
>>>> Abstract:
>>>>    This document describes how to provide IPsec-based flow protection
>>>>    (integrity and confidentiality) by means of an Interface to Network
>>>>    Security Function (I2NSF) controller.  It considers two main well-
>>>>    known scenarios in IPsec: (i) gateway-to-gateway and (ii) host-to-
>>>>    host.  The service described in this document allows the
>>>>    configuration and monitoring of IPsec Security Associations (SAs)
>>>>    from a I2NSF Controller to one or several flow-based Network Security
>>>>    Functions (NSFs) that rely on IPsec to protect data traffic.
>>>>
>>>>    The document focuses on the I2NSF NSF-facing interface by providing
>>>>    YANG data models for configuring the IPsec databases (SPD, SAD, PAD)
>>>>    and IKEv2.  This allows IPsec SA establishment with minimal
>>>>    intervention by the network administrator.  It does not define any
>>>>    new protocol.
>>>>
>>>>
>>>>
>>>>
>>>> Please note that it may take a couple of minutes from the time of submission
>>>> until the htmlized version and diff are available at tools.ietf.org.
>>>>
>>>> The IETF Secretariat
>>>>
>>>>
>>>
>>> -------------------------------------------------------
>>> 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
>>> -------------------------------------------------------
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>
> -------------------------------------------------------
> 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
> -------------------------------------------------------
>
>
>
>
>


From nobody Thu Oct 29 04:23:22 2020
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 6C0C93A0AE3; Thu, 29 Oct 2020 04:23:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level: 
X-Spam-Status: No, score=-2.099 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, RCVD_IN_MSPIKE_H2=-0.001, 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=um.es
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 dDrFlud1vZXS; Thu, 29 Oct 2020 04:23:14 -0700 (PDT)
Received: from mx01.puc.rediris.es (outbound6mad.lav.puc.rediris.es [130.206.19.149]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 552393A09F5; Thu, 29 Oct 2020 04:23:14 -0700 (PDT)
Received: from xenon43.um.es (xenon43.um.es [155.54.212.170]) by mx01.puc.rediris.es  with ESMTP id 09TBN7L3002270-09TBN7L4002270; Thu, 29 Oct 2020 12:23:07 +0100
Received: from localhost (localhost [127.0.0.1]) by xenon43.um.es (Postfix) with ESMTP id 1450C21549; Thu, 29 Oct 2020 12:23:07 +0100 (CET)
X-Virus-Scanned: by antispam in UMU at xenon43.um.es
Received: from xenon43.um.es ([127.0.0.1]) by localhost (xenon43.um.es [127.0.0.1]) (amavisd-new, port 10024) with LMTP id HZKLVeum1mBw; Thu, 29 Oct 2020 12:23:06 +0100 (CET)
Received: from [192.168.1.33] (135.red-79-150-250.dynamicip.rima-tde.net [79.150.250.135]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: rafa@um.es) by xenon43.um.es (Postfix) with ESMTPSA id AB6832154E; Thu, 29 Oct 2020 12:23:04 +0100 (CET)
From: Rafa Marin-Lopez <rafa@um.es>
Message-Id: <56155C91-BFE8-4BA9-A55C-46B12E59CD94@um.es>
Content-Type: multipart/alternative; boundary="Apple-Mail=_56936A74-9FF6-43F0-9B01-C71E5025FB74"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.14\))
Date: Thu, 29 Oct 2020 12:23:03 +0100
In-Reply-To: <5F99B221.3040504@btconnect.com>
Cc: Rafa Marin-Lopez <rafa@um.es>, i2nsf@ietf.org, Gabriel Lopez <gabilm@um.es>, Fernando Pereniguez-Garcia <fernando.pereniguez@cud.upct.es>, last-call@ietf.org, ynir.ietf@gmail.com
To: tom petch <daedulus@btconnect.com>
References: <160337357077.29083.9236626834026808055@ietfa.amsl.com> <EE5AB669-73BB-4517-A6F4-23B7807FB36E@um.es> <5F9815D1.9010303@btconnect.com> <DDE550B1-9A9E-4954-B6F9-C0A33ECE1275@um.es> <5F99B221.3040504@btconnect.com>
X-Mailer: Apple Mail (2.3445.104.14)
X-FEAS-SPF: spf-result=pass, ip=155.54.212.170, helo=xenon43.um.es, mailFrom=rafa@um.es
Authentication-Results: mx01.puc.rediris.es; spf=pass (rediris.es: domain of rafa@um.es designates 155.54.212.170 as permitted sender) smtp.mailfrom=rafa@um.es
X-FE-Policy-ID: 2:15:0:SYSTEM, 2:15:1:upct.es
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=in2wvTSWO/pqnbFHCCSb7u1g8HrW4hgjY886015QLds=; b=d4UMBPZYjtSItW/7pH6e+klIyqBXRo8erzmlIatACSzFGAaTqBW29B4qlkolml/UymKPThx1eGkF eNiJMgF+FfR6+dWjLYSxaHOn5mk49BGzNUuD+b5/5dQedbSsUfcn9aaeLY/RLvAeA9MTjhQsDbrT o7icdjONOs5/mzK6efjweMwxxv+TFBr8NdAg2gaYTYz6x+pCxYHyeSfi8p7sIY7Vu6b0737S0CR9 G+buPZWbwgQsPZ0Lrp7WQaA5he/HuO4pkW+WbljhbHHRDOQCxH0pPWXZ2tkQZIe1HUMExi3hDUdS gztoRPFU2d0uD5Sc03BTwHXkqSW708TCuue/fw==
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2nsf/EULGO49LUpvwdXfAwt2DAewTD40>
Subject: Re: [I2nsf] [Last-Call] New Version Notification for draft-ietf-i2nsf-sdn-ipsec-flow-protection-11.txt
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: Thu, 29 Oct 2020 11:23:18 -0000

--Apple-Mail=_56936A74-9FF6-43F0-9B01-C71E5025FB74
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Hi Tom:

> El 28 oct 2020, a las 19:02, tom petch <daedulus@btconnect.com> =
escribi=C3=B3:
>=20
> On 28/10/2020 10:42, Rafa Marin-Lopez wrote:
>> Hi Tom:
>>=20
>> Thank you very much for your insight. It is very helpful. Please see =
our comments/questions inline.
>>=20
>>> El 27 oct 2020, a las 13:42, tom petch <daedulus@btconnect.com> =
escribi=C3=B3:
>>>=20
>>> I think that the IESG will find a number of problems with this I-D.
>>>=20
>>> YANG module references RFC822 which is several years out of date
>=20
> Rafa
>=20
> On boiler plate, I mean the reference to RFC2119 which now must use =
the language from RFC8174 in the body of the I-D; sorry for the =
confusion.

Ah ok. I guess you are referring to change that paragraph with this:


The key words "MUST", "MUST NOT", "REQUIRED",
"SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT",
"RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted
as described in BCP 14 RFC2119 RFC8174 when,=20
and only when, they appear in all capitals,=20
as shown here.

>=20
> On XXXX, you have XXXX standing in for more than one RFC-to-be which =
confuses.  The convention is to use XXXX for this I-D and then AAAA BBBB =
etc for any others such as the netconf I-D in this instance.

Ah ok. In any case, we have now only XXXX for our RFC-to-be so problem =
fixed.
>=20
> Two big issues, for me (perhaps not for others).  The convention with =
YANG is for each successive line to be indented two characters, you have =
four, which creates a lot of white space and pushes the text to the =
right hand margin.  I think that two characters is the default when you =
use pyang to format a YANG module.

We can try to reduce it to two characters.=20

>=20
> And references.  I have had to work harder than I want to to make =
sense of the IANA references.  I think you should have five separate =
references in the I-D for IANA for
> Transform Type 1
> Transform Type 3
> Transform Type 4
> Authentication Method
> Protocol Numbers
> and each reference in the I-D should have a URL pointing to the =
specific section of IANA web site.

Ok, good. This follows what we thought.

> In the YANG, it is harder to know what to do.  Those first three =
references are in the third tier i.e.
> Group - Internet Key Exchange V2 (IKEv2) Parameters
> Registry  -Transform Attribute Types
> and then Type 1, 3, 4 as the third tier as I am calling it
> and I think that every reference in the YANG should give me all three =
tiers after IANA in that order perhaps
> IANA; IKEv2 Parameters; Transform Atribute Types; Transform Type 1

Great. We also considered this as a possible solution after sending our =
e-mail. Let=E2=80=99s do it.

> If the syntax needs tweeking, then the RFC Editor will do a good job =
of that but at present the references are inconsistent in which elements =
are specified in what order and that is something the RFC Editor =
probably cannot cope with.
> Authentication Method is a registry so that just needs Group name and =
Registry name after IANA.

Ok, good.
>=20
> Some minor glitches.
> I-D appears twice in the body of the I-D - perhaps document or memo.

Ok.

> objetives/objectives/

Fixed.
> end port number perhaps /must/MUST/

> and YANG is very good at including such checks with a must ....
> 'If AEAD is used .. where? this occurs in several places and I think =
that you need to specify the leaf where AEAD will be specified or =
implied.

Ok we have changed it to:

If Authenticated Encryption with Associated Data (AEAD) is used (leaf =
esp-algorithms/encryption/algorithm-type)=20
this flag MUST be false."

> And is it possible to make that a YANG 'must' statement - looking at =
the IKEv2 registries it is not obvious which are AEAD so that might be =
more complexity than it is worth.
> 'only available on linux kernels' Um implementation detail, you may =
get asked to remove that altogether or at least to a Informative =
Appendix - I would leave it in for now.

Ok.

> 'import ietf-i2nsf-ikec' the reference needs to be to a RFC and if it =
is not yet an RFC then RFC XXXX <title> in both Appendix B and C

Yes, we have changed that to:

RFC XXXX: Software-Defined Networking
               (SDN)-based IPsec Flow Protection.

> leaf-list pfs-groups could do with a reference - Transform Type 4?

The leaf list is referring to type pfs-group and we have now

typedef pfs-group {
            type uint16;
            description=20
                "DH groups for IKE and IPsec SA rekey.";
            reference=20
                "IANA; Internet Key Exchange V2 (IKEv2) Parameters;
				Transform Atribute Types; Transform Type =
4 -
                Diffie-Hellman Group Transform IDs.
				Section 3.3.2 in RFC 7296.";
        }


>=20
> I am still working my way through the YANG so may have some more =
comments tomorrow.

Ok, do not worry we will work in -12 with these comments so far to have =
a quick response. We can prepare a another version later with the rest =
of them.

Thank you very much for your effort.
>=20
> Tom Petch
>=20
>=20
>=20
>=20
>=20
>=20
>=20
>=20
>=20
>=20
>=20
>=20
>=20
>=20
>> We have realized that we missed to change this, even though we =
discussed it. We will change it right away in the following way (bold):
>>=20
>> case rfc822-address-string {
>>      leaf rfc822-address-string {
>>           type string;
>>           description
>>               "Specifies the identity as a
>>                fully-qualified RFC5322 email
>>                address string. An example is,
>>                jsmith@example.com. The string
>>                MUST NOT contain any
>>                terminators e.g., NULL, CR,
>>                etc.).";
>>            reference
>>                   "RFC 5322.";
>>      }
>> }
>>=20
>> Btw, we already used in the past =E2=80=9Ccase =
rfc822-address-string=E2=80=9D and =E2=80=9Cleaf =
rfc822-address-string=E2=80=9D since this is coming from IKEv2 standard. =
Do you think we should change that name as well?
>>=20
>>=20
>>>=20
>>> YANG module references IANA Protocol Numbers which is not in the I-D =
references
>>=20
>> We have included the following reference:
>>=20
>> [IANA-Protocols-Number]
>>               Internet Assigned Numbers Authority (IANA), "Protocol
>>               Numbers", January 2020.
>>=20
>>=20
>>>=20
>>> s.2 boiler plate is out of date
>>=20
>> What we see is the I-D has the second choice stated in =
https://www.ietf.org/standards/ids/guidelines/
>>=20
>> This Internet-Draft is submitted in full conformance with the
>>    provisions of BCP 78 and BCP 79.
>>=20
>>    Internet-Drafts are working documents of the Internet Engineering
>>    Task Force (IETF).  Note that other groups may also distribute
>>    working documents as Internet-Drafts.  The list of current =
Internet-
>>    Drafts is at https://datatracker.ietf.org/drafts/current/.
>>=20
>>    Internet-Drafts are draft documents valid for a maximum of six =
months
>>    and may be updated, replaced, or obsoleted by other documents at =
any
>>    time.  It is inappropriate to use Internet-Drafts as reference
>>    material or to cite them other than as "work in progress."
>>=20
>> Could you refer what is out of date?
>>=20
>>>=20
>>> XXXX is standing in for more than one RFC
>>=20
>> Yes, XXXX has been used because we do not know the future number =
assigned to our I-D.
>>=20
>> Also we realized we also included this to refer to crypto-types I-D =
but this has been solved now in a new version -12 that we are preparing =
to include your comments. We noticed we can replace the type of rw =
cert-data?, ca-data*, crl-data? for binary without any problem.
>>=20
>> |           |     +--rw cert-data?        binary
>> |           +--rw private-key?            binary
>> |           +--rw ca-data*                binary
>> |           +--rw crl-data?               binary
>>=20
>>>=20
>>> but the show stopper that makes a proper review of this too costly =
is the references.  Those to IANA of which there are several I want to =
pursue.  The I-D reference is to IKEv2 parameters. Sadly, this is a =
three tier structure and noone agrees on what to call the third tier so =
I will call it tier3 here.  Top level is Group, as per RFC8126, second =
level is Registry.  The I-D reference is to the Group only which is fine =
if the actual reference then specifies the Registry and Tier3 but they =
never do, usually just Tier3 e.g. Transform Type 3 which makes for a lot =
of work for the reader, too much for this one.  You have to go hunting =
in all the second level Registry until you can find a match for the =
Tier3 identifier. And there are no URL.  If you want an example that I =
find easy to use, go look at RFC8407 (as usual).
>>=20
>> You=E2=80=99re right. Could you point the exact part at RFC 8407 with =
that example? We would really appreciate it.
>>=20
>> On the other hand, would it be enough to include the URL for =
Transform Type 3 =
https://www.iana.org/assignments/ikev2-parameters/ikev2-parameters.xhtml#i=
kev2-parameters-7 ?
>>=20
>> (Same for Transform Type 1, Transform Type 4)
>>=20
>>>=20
>>> The reference for import of i2nsf-ikec gives a YANG module name; =
this needs to be the name of the RFC to be
>>=20
>> Fixed.
>>=20
>> import ietf-i2nsf-ikec {
>>             prefix nsfikec;
>>             reference
>>                 "RFC XXXX: Software-Defined Networking
>>                (SDN)-based IPsec Flow Protection.";
>> }
>>=20
>> We still use XXXX because we do not know the number assigned to the =
RFC to be.
>>=20
>>>=20
>>> The example IPv6 address in the YANG module has :0:0: which is =
usually just ::
>>=20
>> Fixed.
>>=20
>> If you have any further comments, please let us know so we can =
include them in -12
>>=20
>> Best Regards.
>>>=20
>>> And I have some way to go still.
>>>=20
>>> Tom Petch
>>>=20
>>> On 22/10/2020 18:39, Rafa Marin-Lopez wrote:
>>>> Dear all:
>>>>=20
>>>> After receiving a suggestion to make things clearer in the feature =
ikeless-notification description, we have just uploaded a new version =
-11 with a minor change to add the following text:
>>>>=20
>>>> feature ikeless-notification {
>>>>             description
>>>>                 "This feature indicates that the server supports
>>>>                 generating notifications in the ikeless module.
>>>>=20
>>>>                 To ensure broader applicability of this module,
>>>>                 the notifications are marked as a feature.
>>>>                 For the implementation of ikeless case,
>>>>                 the NSF is expected to implement this
>>>>                 feature.";
>>>>         }
>>>>=20
>>>> Best Regards.
>>>>=20
>>>>> Inicio del mensaje reenviado:
>>>>>=20
>>>>> De: internet-drafts@ietf.org
>>>>> Asunto: New Version Notification for =
draft-ietf-i2nsf-sdn-ipsec-flow-protection-11.txt
>>>>> Fecha: 22 de octubre de 2020, 15:32:50 CEST
>>>>> Para: "Fernando Pereniguez-Garcia" =
<fernando.pereniguez@cud.upct.es>, "Rafael Lopez" <rafa@um.es>, "Gabriel =
Lopez-Millan" <gabilm@um.es>, "Rafa Marin-Lopez" <rafa@um.es>
>>>>>=20
>>>>>=20
>>>>> A new version of I-D, =
draft-ietf-i2nsf-sdn-ipsec-flow-protection-11.txt
>>>>> has been successfully submitted by Rafa Marin-Lopez and posted to =
the
>>>>> IETF repository.
>>>>>=20
>>>>> Name:		draft-ietf-i2nsf-sdn-ipsec-flow-protection
>>>>> Revision:	11
>>>>> Title:		Software-Defined Networking (SDN)-based IPsec =
Flow Protection
>>>>> Document date:	2020-10-22
>>>>> Group:		i2nsf
>>>>> Pages:		92
>>>>> URL:            =
https://www.ietf.org/archive/id/draft-ietf-i2nsf-sdn-ipsec-flow-protection=
-11.txt
>>>>> Status:         =
https://datatracker.ietf.org/doc/draft-ietf-i2nsf-sdn-ipsec-flow-protectio=
n/
>>>>> Htmlized:       =
https://datatracker.ietf.org/doc/html/draft-ietf-i2nsf-sdn-ipsec-flow-prot=
ection
>>>>> Htmlized:       =
https://tools.ietf.org/html/draft-ietf-i2nsf-sdn-ipsec-flow-protection-11
>>>>> Diff:           =
https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-i2nsf-sdn-ipsec-flow-protec=
tion-11
>>>>>=20
>>>>> Abstract:
>>>>>   This document describes how to provide IPsec-based flow =
protection
>>>>>   (integrity and confidentiality) by means of an Interface to =
Network
>>>>>   Security Function (I2NSF) controller.  It considers two main =
well-
>>>>>   known scenarios in IPsec: (i) gateway-to-gateway and (ii) =
host-to-
>>>>>   host.  The service described in this document allows the
>>>>>   configuration and monitoring of IPsec Security Associations =
(SAs)
>>>>>   from a I2NSF Controller to one or several flow-based Network =
Security
>>>>>   Functions (NSFs) that rely on IPsec to protect data traffic.
>>>>>=20
>>>>>   The document focuses on the I2NSF NSF-facing interface by =
providing
>>>>>   YANG data models for configuring the IPsec databases (SPD, SAD, =
PAD)
>>>>>   and IKEv2.  This allows IPsec SA establishment with minimal
>>>>>   intervention by the network administrator.  It does not define =
any
>>>>>   new protocol.
>>>>>=20
>>>>>=20
>>>>>=20
>>>>>=20
>>>>> Please note that it may take a couple of minutes from the time of =
submission
>>>>> until the htmlized version and diff are available at =
tools.ietf.org.
>>>>>=20
>>>>> The IETF Secretariat
>>>>>=20
>>>>>=20
>>>>=20
>>>> -------------------------------------------------------
>>>> 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
>>>> -------------------------------------------------------
>>>>=20
>>>>=20
>>>>=20
>>>>=20
>>>>=20
>>>>=20
>>>>=20
>>=20
>> -------------------------------------------------------
>> 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
>> -------------------------------------------------------
>>=20
>>=20
>>=20
>>=20
>>=20

-------------------------------------------------------
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
-------------------------------------------------------





--Apple-Mail=_56936A74-9FF6-43F0-9B01-C71E5025FB74
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: after-white-space;" class=3D""><div =
dir=3D"auto" style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
line-break: after-white-space;" class=3D"">Hi Tom:<br class=3D""><div><br =
class=3D""><blockquote type=3D"cite" class=3D""><div class=3D"">El 28 =
oct 2020, a las 19:02, tom petch &lt;<a =
href=3D"mailto:daedulus@btconnect.com" =
class=3D"">daedulus@btconnect.com</a>&gt; escribi=C3=B3:</div><br =
class=3D"Apple-interchange-newline"><div class=3D""><div class=3D"">On =
28/10/2020 10:42, Rafa Marin-Lopez wrote:<br class=3D""><blockquote =
type=3D"cite" class=3D"">Hi Tom:<br class=3D""><br class=3D"">Thank you =
very much for your insight. It is very helpful. Please see our =
comments/questions inline.<br class=3D""><br class=3D""><blockquote =
type=3D"cite" class=3D"">El 27 oct 2020, a las 13:42, tom petch &lt;<a =
href=3D"mailto:daedulus@btconnect.com" =
class=3D"">daedulus@btconnect.com</a>&gt; escribi=C3=B3:<br class=3D""><br=
 class=3D"">I think that the IESG will find a number of problems with =
this I-D.<br class=3D""><br class=3D"">YANG module references RFC822 =
which is several years out of date<br =
class=3D""></blockquote></blockquote><br class=3D"">Rafa<br class=3D""><br=
 class=3D"">On boiler plate, I mean the reference to RFC2119 which now =
must use the language from RFC8174 in the body of the I-D; sorry for the =
confusion.<br class=3D""></div></div></blockquote><div><br =
class=3D""></div><div>Ah ok. I guess you are referring to change that =
paragraph with this:</div><div><br class=3D""></div><div><br =
class=3D""></div><div><div>The key words "MUST", "MUST NOT", =
"REQUIRED",</div><div>"SHALL", "SHALL NOT", "SHOULD", "SHOULD =
NOT",</div><div>"RECOMMENDED", "NOT RECOMMENDED", "MAY", =
and</div><div>"OPTIONAL" in this document are to be =
interpreted</div><div>as described in BCP 14 RFC2119 RFC8174 =
when,&nbsp;</div><div>and only when, they appear in all =
capitals,&nbsp;</div><div>as shown here.</div></div><br =
class=3D""><blockquote type=3D"cite" class=3D""><div class=3D""><div =
class=3D""><br class=3D"">On XXXX, you have XXXX standing in for more =
than one RFC-to-be which confuses. &nbsp;The convention is to use XXXX =
for this I-D and then AAAA BBBB etc for any others such as the netconf =
I-D in this instance.<br class=3D""></div></div></blockquote><div><br =
class=3D""></div>Ah ok. In any case, we have now only XXXX for our =
RFC-to-be so problem fixed.<br class=3D""><blockquote type=3D"cite" =
class=3D""><div class=3D""><div class=3D""><br class=3D"">Two big =
issues, for me (perhaps not for others). &nbsp;The convention with YANG =
is for each successive line to be indented two characters, you have =
four, which creates a lot of white space and pushes the text to the =
right hand margin. &nbsp;I think that two characters is the default when =
you use pyang to format a YANG module.<br =
class=3D""></div></div></blockquote><div><br class=3D""></div><div>We =
can try to reduce it to two characters.&nbsp;</div><br =
class=3D""><blockquote type=3D"cite" class=3D""><div class=3D""><div =
class=3D""><br class=3D"">And references. &nbsp;I have had to work =
harder than I want to to make sense of the IANA references. &nbsp;I =
think you should have five separate references in the I-D for IANA =
for<br class=3D"">Transform Type 1<br class=3D"">Transform Type 3<br =
class=3D"">Transform Type 4<br class=3D"">Authentication Method<br =
class=3D"">Protocol Numbers</div></div></blockquote><blockquote =
type=3D"cite" class=3D""><div class=3D""><div class=3D"">and each =
reference in the I-D should have a URL pointing to the specific section =
of IANA web site.<br class=3D""></div></div></blockquote><br =
class=3D""><div>Ok, good. This follows what we thought.</div><br =
class=3D""><blockquote type=3D"cite" class=3D""><div class=3D""><div =
class=3D"">In the YANG, it is harder to know what to do. &nbsp;Those =
first three references are in the third tier i.e.<br class=3D"">Group - =
Internet Key Exchange V2 (IKEv2) Parameters<br class=3D"">Registry =
&nbsp;-Transform Attribute Types<br class=3D"">and then Type 1, 3, 4 as =
the third tier as I am calling it<br class=3D"">and I think that every =
reference in the YANG should give me all three tiers after IANA in that =
order perhaps<br class=3D"">IANA; IKEv2 Parameters; Transform Atribute =
Types; Transform Type 1<br class=3D""></div></div></blockquote><div><br =
class=3D""></div><div>Great. We also considered this as a possible =
solution after sending our e-mail. Let=E2=80=99s do it.</div><br =
class=3D""><blockquote type=3D"cite" class=3D""><div class=3D""><div =
class=3D"">If the syntax needs tweeking, then the RFC Editor will do a =
good job of that but at present the references are inconsistent in which =
elements are specified in what order and that is something the RFC =
Editor probably cannot cope with.<br class=3D"">Authentication Method is =
a registry so that just needs Group name and Registry name after =
IANA.<br class=3D""></div></div></blockquote><div><br class=3D""></div>Ok,=
 good.<br class=3D""><blockquote type=3D"cite" class=3D""><div =
class=3D""><div class=3D""><br class=3D"">Some minor glitches.<br =
class=3D"">I-D appears twice in the body of the I-D - perhaps document =
or memo.<br class=3D""></div></div></blockquote><div><br =
class=3D""></div>Ok.<br class=3D""><br class=3D""><blockquote =
type=3D"cite" class=3D""><div class=3D""><div =
class=3D"">objetives/objectives/<br =
class=3D""></div></div></blockquote><div><br class=3D""></div>Fixed.<br =
class=3D""><blockquote type=3D"cite" class=3D""><div class=3D""><div =
class=3D"">end port number perhaps /must/MUST/<br =
class=3D""></div></div></blockquote><br class=3D""><blockquote =
type=3D"cite" class=3D""><div class=3D""><div class=3D"">and YANG is =
very good at including such checks with a must ....<br class=3D"">'If =
AEAD is used .. where? this occurs in several places and I think that =
you need to specify the leaf where AEAD will be specified or implied.<br =
class=3D""></div></div></blockquote><div><br class=3D""></div><div>Ok we =
have changed it to:</div><div><br class=3D""></div><div><div>If =
Authenticated Encryption with Associated Data (AEAD) is used (leaf <b =
class=3D"">esp-algorithms/encryption/algorithm-type</b>)&nbsp;</div><div>t=
his flag MUST be false."</div></div><br class=3D""><blockquote =
type=3D"cite" class=3D""><div class=3D""><div class=3D"">And is it =
possible to make that a YANG 'must' statement - looking at the IKEv2 =
registries it is not obvious which are AEAD so that might be more =
complexity than it is worth.<br class=3D"">'only available on linux =
kernels' Um implementation detail, you may get asked to remove that =
altogether or at least to a Informative Appendix - I would leave it in =
for now.<br class=3D""></div></div></blockquote><div><br =
class=3D""></div>Ok.</div><div><br class=3D""><blockquote type=3D"cite" =
class=3D""><div class=3D""><div class=3D"">'import ietf-i2nsf-ikec' the =
reference needs to be to a RFC and if it is not yet an RFC then RFC XXXX =
&lt;title&gt; in both Appendix B and C<br =
class=3D""></div></div></blockquote><div><br class=3D""></div><div>Yes, =
we have changed that to:</div><div><br class=3D""></div><div><div>RFC =
XXXX: Software-Defined Networking</div><div>&nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp;(SDN)-based IPsec Flow =
Protection.</div></div><br class=3D""><blockquote type=3D"cite" =
class=3D""><div class=3D""><div class=3D"">leaf-list pfs-groups could do =
with a reference - Transform Type 4?<br =
class=3D""></div></div></blockquote><div><br class=3D""></div>The leaf =
list is referring to type pfs-group and we have now</div><div><br =
class=3D""></div><div>typedef pfs-group {<br class=3D"">&nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; type uint16;<br class=3D"">&nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; description&nbsp;<br class=3D"">&nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; "DH groups for IKE and =
IPsec SA rekey.";<br class=3D"">&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; reference&nbsp;<br class=3D"">&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; "<b class=3D"">IANA; Internet Key Exchange V2 =
(IKEv2) Parameters;<br class=3D""><span class=3D"Apple-tab-span" =
style=3D"white-space:pre">				</span>Transform =
Atribute Types; Transform Type 4 -<br class=3D"">&nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Diffie-Hellman Group Transform =
IDs</b>.<br class=3D""><span class=3D"Apple-tab-span" =
style=3D"white-space:pre">				</span>Section =
3.3.2 in RFC 7296.";<br class=3D"">&nbsp; &nbsp; &nbsp; &nbsp; =
}</div><div><br class=3D""></div><div><br class=3D""><blockquote =
type=3D"cite" class=3D""><div class=3D""><div class=3D""><br class=3D"">I =
am still working my way through the YANG so may have some more comments =
tomorrow.<br class=3D""></div></div></blockquote><div><br =
class=3D""></div>Ok, do not worry we will work in -12 with these =
comments so far to have a quick response. We can prepare a another =
version later with the rest of them.</div><div><br =
class=3D""></div><div>Thank you very much for your effort.<br =
class=3D""><blockquote type=3D"cite" class=3D""><div class=3D""><div =
class=3D""><br class=3D"">Tom Petch<br class=3D""><br class=3D""><br =
class=3D""><br class=3D""><br class=3D""><br class=3D""><br class=3D""><br=
 class=3D""><br class=3D""><br class=3D""><br class=3D""><br =
class=3D""><br class=3D""><br class=3D""><br class=3D""><blockquote =
type=3D"cite" class=3D"">We have realized that we missed to change this, =
even though we discussed it. We will change it right away in the =
following way (bold):<br class=3D""><br class=3D"">case =
rfc822-address-string {<br class=3D""> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;leaf rfc822-address-string {<br class=3D""> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;type =
string;<br class=3D""> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;description<br=
 class=3D""> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;"Specifies the identity as a<br class=3D""> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;fully-qualified RFC5322 email<br class=3D""> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;address string. An example is,<br class=3D""> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;<a href=3D"mailto:jsmith@example.com" =
class=3D"">jsmith@example.com</a>. The string<br class=3D""> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;MUST NOT contain any<br class=3D""> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;terminators e.g., NULL, CR,<br class=3D""> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;etc.).";<br class=3D""> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;referenc=
e<br class=3D""> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;"RFC 5322.";<br class=3D""> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;}<br class=3D"">}<br class=3D""><br =
class=3D"">Btw, we already used in the past =E2=80=9Ccase =
rfc822-address-string=E2=80=9D and =E2=80=9Cleaf =
rfc822-address-string=E2=80=9D since this is coming from IKEv2 standard. =
Do you think we should change that name as well?<br class=3D""><br =
class=3D""><br class=3D""><blockquote type=3D"cite" class=3D""><br =
class=3D"">YANG module references IANA Protocol Numbers which is not in =
the I-D references<br class=3D""></blockquote><br class=3D"">We have =
included the following reference:<br class=3D""><br =
class=3D"">[IANA-Protocols-Number]<br class=3D""> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;Internet Assigned Numbers Authority (IANA), "Protocol<br =
class=3D""> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;Numbers", January 2020.<br class=3D""><br class=3D""><br =
class=3D""><blockquote type=3D"cite" class=3D""><br class=3D"">s.2 =
boiler plate is out of date<br class=3D""></blockquote><br class=3D"">What=
 we see is the I-D has the second choice stated in <a =
href=3D"https://www.ietf.org/standards/ids/guidelines/" =
class=3D"">https://www.ietf.org/standards/ids/guidelines/</a><br =
class=3D""><br class=3D"">This Internet-Draft is submitted in full =
conformance with the<br class=3D""> &nbsp;&nbsp;&nbsp;provisions of BCP =
78 and BCP 79.<br class=3D""><br class=3D""> =
&nbsp;&nbsp;&nbsp;Internet-Drafts are working documents of the Internet =
Engineering<br class=3D""> &nbsp;&nbsp;&nbsp;Task Force (IETF). =
&nbsp;Note that other groups may also distribute<br class=3D""> =
&nbsp;&nbsp;&nbsp;working documents as Internet-Drafts. &nbsp;The list =
of current Internet-<br class=3D""> &nbsp;&nbsp;&nbsp;Drafts is at <a =
href=3D"https://datatracker.ietf.org/drafts/current/" =
class=3D"">https://datatracker.ietf.org/drafts/current/</a>.<br =
class=3D""><br class=3D""> &nbsp;&nbsp;&nbsp;Internet-Drafts are draft =
documents valid for a maximum of six months<br class=3D""> =
&nbsp;&nbsp;&nbsp;and may be updated, replaced, or obsoleted by other =
documents at any<br class=3D""> &nbsp;&nbsp;&nbsp;time. &nbsp;It is =
inappropriate to use Internet-Drafts as reference<br class=3D""> =
&nbsp;&nbsp;&nbsp;material or to cite them other than as "work in =
progress."<br class=3D""><br class=3D"">Could you refer what is out of =
date?<br class=3D""><br class=3D""><blockquote type=3D"cite" =
class=3D""><br class=3D"">XXXX is standing in for more than one RFC<br =
class=3D""></blockquote><br class=3D"">Yes, XXXX has been used because =
we do not know the future number assigned to our I-D.<br class=3D""><br =
class=3D"">Also we realized we also included this to refer to =
crypto-types I-D but this has been solved now in a new version -12 that =
we are preparing to include your comments. We noticed we can replace the =
type of rw cert-data?, ca-data*, crl-data? for binary without any =
problem.<br class=3D""><br class=3D"">| =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;| =
&nbsp;&nbsp;&nbsp;&nbsp;+--rw cert-data? =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;binary<br class=3D"">| =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;+--rw =
private-key? =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;binary<b=
r class=3D"">| =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;+--rw =
ca-data* =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;binary<br class=3D"">| =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;+--rw =
crl-data? =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;binary<br class=3D""><br class=3D""><blockquote type=3D"cite" =
class=3D""><br class=3D"">but the show stopper that makes a proper =
review of this too costly is the references. &nbsp;Those to IANA of =
which there are several I want to pursue. &nbsp;The I-D reference is to =
IKEv2 parameters. Sadly, this is a three tier structure and noone agrees =
on what to call the third tier so I will call it tier3 here. &nbsp;Top =
level is Group, as per RFC8126, second level is Registry. &nbsp;The I-D =
reference is to the Group only which is fine if the actual reference =
then specifies the Registry and Tier3 but they never do, usually just =
Tier3 e.g. Transform Type 3 which makes for a lot of work for the =
reader, too much for this one. &nbsp;You have to go hunting in all the =
second level Registry until you can find a match for the Tier3 =
identifier. And there are no URL. &nbsp;If you want an example that I =
find easy to use, go look at RFC8407 (as usual).<br =
class=3D""></blockquote><br class=3D"">You=E2=80=99re right. Could you =
point the exact part at RFC 8407 with that example? We would really =
appreciate it.<br class=3D""><br class=3D"">On the other hand, would it =
be enough to include the URL for Transform Type 3 <a =
href=3D"https://www.iana.org/assignments/ikev2-parameters/ikev2-parameters=
.xhtml#ikev2-parameters-7" =
class=3D"">https://www.iana.org/assignments/ikev2-parameters/ikev2-paramet=
ers.xhtml#ikev2-parameters-7</a> ?<br class=3D""><br class=3D"">(Same =
for Transform Type 1, Transform Type 4)<br class=3D""><br =
class=3D""><blockquote type=3D"cite" class=3D""><br class=3D"">The =
reference for import of i2nsf-ikec gives a YANG module name; this needs =
to be the name of the RFC to be<br class=3D""></blockquote><br =
class=3D"">Fixed.<br class=3D""><br class=3D"">import ietf-i2nsf-ikec =
{<br class=3D""> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;pr=
efix nsfikec;<br class=3D""> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;re=
ference<br class=3D""> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;"RFC XXXX: Software-Defined Networking<br =
class=3D""> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;(SDN)-based IPsec Flow Protection.";<br class=3D"">}<br =
class=3D""><br class=3D"">We still use XXXX because we do not know the =
number assigned to the RFC to be.<br class=3D""><br class=3D""><blockquote=
 type=3D"cite" class=3D""><br class=3D"">The example IPv6 address in the =
YANG module has :0:0: which is usually just ::<br =
class=3D""></blockquote><br class=3D"">Fixed.<br class=3D""><br =
class=3D"">If you have any further comments, please let us know so we =
can include them in -12<br class=3D""><br class=3D"">Best Regards.<br =
class=3D""><blockquote type=3D"cite" class=3D""><br class=3D"">And I =
have some way to go still.<br class=3D""><br class=3D"">Tom Petch<br =
class=3D""><br class=3D"">On 22/10/2020 18:39, Rafa Marin-Lopez =
wrote:<br class=3D""><blockquote type=3D"cite" class=3D"">Dear all:<br =
class=3D""><br class=3D"">After receiving a suggestion to make things =
clearer in the feature ikeless-notification description, we have just =
uploaded a new version -11 with a minor change to add the following =
text:<br class=3D""><br class=3D"">feature ikeless-notification {<br =
class=3D""> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;de=
scription<br class=3D""> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;"This feature indicates that the server =
supports<br class=3D""> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;generating notifications in the ikeless module.<br =
class=3D""><br class=3D""> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;To ensure broader applicability of this module,<br =
class=3D""> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;the notifications are marked as a feature.<br =
class=3D""> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;For the implementation of ikeless case,<br =
class=3D""> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;the NSF is expected to implement this<br class=3D"">=
 =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;feature.";<br class=3D""> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;}<br class=3D""><br =
class=3D"">Best Regards.<br class=3D""><br class=3D""><blockquote =
type=3D"cite" class=3D"">Inicio del mensaje reenviado:<br class=3D""><br =
class=3D"">De: <a href=3D"mailto:internet-drafts@ietf.org" =
class=3D"">internet-drafts@ietf.org</a><br class=3D"">Asunto: New =
Version Notification for =
draft-ietf-i2nsf-sdn-ipsec-flow-protection-11.txt<br class=3D"">Fecha: =
22 de octubre de 2020, 15:32:50 CEST<br class=3D"">Para: "Fernando =
Pereniguez-Garcia" &lt;<a href=3D"mailto:fernando.pereniguez@cud.upct.es" =
class=3D"">fernando.pereniguez@cud.upct.es</a>&gt;, "Rafael Lopez" =
&lt;<a href=3D"mailto:rafa@um.es" class=3D"">rafa@um.es</a>&gt;, =
"Gabriel Lopez-Millan" &lt;<a href=3D"mailto:gabilm@um.es" =
class=3D"">gabilm@um.es</a>&gt;, "Rafa Marin-Lopez" &lt;<a =
href=3D"mailto:rafa@um.es" class=3D"">rafa@um.es</a>&gt;<br class=3D""><br=
 class=3D""><br class=3D"">A new version of I-D, =
draft-ietf-i2nsf-sdn-ipsec-flow-protection-11.txt<br class=3D"">has been =
successfully submitted by Rafa Marin-Lopez and posted to the<br =
class=3D"">IETF repository.<br class=3D""><br class=3D"">Name:<span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</span><span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</span>draft-ietf-i2nsf-sdn-ipsec-flow-protection<br =
class=3D"">Revision:<span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</span>11<br class=3D"">Title:<span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</span><span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</span>Software-Defined Networking (SDN)-based IPsec Flow Protection<br =
class=3D"">Document date:<span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</span>2020-10-22<br =
class=3D"">Group:<span class=3D"Apple-tab-span" style=3D"white-space:pre">=
	</span><span class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</span>i2nsf<br class=3D"">Pages:<span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</span><span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</span>92<br class=3D"">URL: =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a =
href=3D"https://www.ietf.org/archive/id/draft-ietf-i2nsf-sdn-ipsec-flow-pr=
otection-11.txt" =
class=3D"">https://www.ietf.org/archive/id/draft-ietf-i2nsf-sdn-ipsec-flow=
-protection-11.txt</a><br class=3D"">Status: =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a =
href=3D"https://datatracker.ietf.org/doc/draft-ietf-i2nsf-sdn-ipsec-flow-p=
rotection/" =
class=3D"">https://datatracker.ietf.org/doc/draft-ietf-i2nsf-sdn-ipsec-flo=
w-protection/</a><br class=3D"">Htmlized: =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a =
href=3D"https://datatracker.ietf.org/doc/html/draft-ietf-i2nsf-sdn-ipsec-f=
low-protection" =
class=3D"">https://datatracker.ietf.org/doc/html/draft-ietf-i2nsf-sdn-ipse=
c-flow-protection</a><br class=3D"">Htmlized: =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a =
href=3D"https://tools.ietf.org/html/draft-ietf-i2nsf-sdn-ipsec-flow-protec=
tion-11" =
class=3D"">https://tools.ietf.org/html/draft-ietf-i2nsf-sdn-ipsec-flow-pro=
tection-11</a><br class=3D"">Diff: =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a =
href=3D"https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-i2nsf-sdn-ipsec-flo=
w-protection-11" =
class=3D"">https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-i2nsf-sdn-ipsec-=
flow-protection-11</a><br class=3D""><br class=3D"">Abstract:<br =
class=3D""> &nbsp;&nbsp;This document describes how to provide =
IPsec-based flow protection<br class=3D""> &nbsp;&nbsp;(integrity and =
confidentiality) by means of an Interface to Network<br class=3D""> =
&nbsp;&nbsp;Security Function (I2NSF) controller. &nbsp;It considers two =
main well-<br class=3D""> &nbsp;&nbsp;known scenarios in IPsec: (i) =
gateway-to-gateway and (ii) host-to-<br class=3D""> &nbsp;&nbsp;host. =
&nbsp;The service described in this document allows the<br class=3D""> =
&nbsp;&nbsp;configuration and monitoring of IPsec Security Associations =
(SAs)<br class=3D""> &nbsp;&nbsp;from a I2NSF Controller to one or =
several flow-based Network Security<br class=3D""> &nbsp;&nbsp;Functions =
(NSFs) that rely on IPsec to protect data traffic.<br class=3D""><br =
class=3D""> &nbsp;&nbsp;The document focuses on the I2NSF NSF-facing =
interface by providing<br class=3D""> &nbsp;&nbsp;YANG data models for =
configuring the IPsec databases (SPD, SAD, PAD)<br class=3D""> =
&nbsp;&nbsp;and IKEv2. &nbsp;This allows IPsec SA establishment with =
minimal<br class=3D""> &nbsp;&nbsp;intervention by the network =
administrator. &nbsp;It does not define any<br class=3D""> =
&nbsp;&nbsp;new protocol.<br class=3D""><br class=3D""><br class=3D""><br =
class=3D""><br class=3D"">Please note that it may take a couple of =
minutes from the time of submission<br class=3D"">until the htmlized =
version and diff are available at <a href=3D"http://tools.ietf.org" =
class=3D"">tools.ietf.org</a>.<br class=3D""><br class=3D"">The IETF =
Secretariat<br class=3D""><br class=3D""><br class=3D""></blockquote><br =
class=3D"">-------------------------------------------------------<br =
class=3D"">Rafa Marin-Lopez, PhD<br class=3D"">Dept. Information and =
Communications Engineering (DIIC)<br class=3D"">Faculty of Computer =
Science-University of Murcia<br class=3D"">30100 Murcia - Spain<br =
class=3D"">Telf: +34868888501 Fax: +34868884151 <a =
href=3D"mailto:rafa@um.es" class=3D"">e-mail: rafa@um.es</a><br =
class=3D"">-------------------------------------------------------<br =
class=3D""><br class=3D""><br class=3D""><br class=3D""><br class=3D""><br=
 class=3D""><br class=3D""><br class=3D""></blockquote></blockquote><br =
class=3D"">-------------------------------------------------------<br =
class=3D"">Rafa Marin-Lopez, PhD<br class=3D"">Dept. Information and =
Communications Engineering (DIIC)<br class=3D"">Faculty of Computer =
Science-University of Murcia<br class=3D"">30100 Murcia - Spain<br =
class=3D"">Telf: +34868888501 Fax: +34868884151 <a =
href=3D"mailto:rafa@um.es" class=3D"">e-mail: rafa@um.es</a><br =
class=3D"">-------------------------------------------------------<br =
class=3D""><br class=3D""><br class=3D""><br class=3D""><br class=3D""><br=
 class=3D""></blockquote></div></div></blockquote></div><br =
class=3D""><div class=3D"">
<div style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space;" class=3D""><div style=3D"color: =
rgb(0, 0, 0); font-family: Courier; font-size: 16px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
orphans: auto; text-align: start; text-indent: 0px; text-transform: =
none; white-space: normal; widows: auto; word-spacing: 0px; =
-webkit-text-stroke-width: =
0px;">-------------------------------------------------------<br =
class=3D"">Rafa Marin-Lopez, PhD<br class=3D"">Dept. Information =
and&nbsp;Communications&nbsp;Engineering (DIIC)<br class=3D"">Faculty of =
Computer&nbsp;Science-University of&nbsp;Murcia<br class=3D"">30100 =
Murcia - Spain<br class=3D"">Telf: +34868888501 Fax:&nbsp;+34868884151 =
<a href=3D"mailto:rafa@um.es" class=3D"">e-mail:&nbsp;rafa@um.es</a><br =
class=3D"">-------------------------------------------------------</div><d=
iv style=3D"color: rgb(0, 0, 0); font-family: Courier; font-size: 16px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; orphans: auto; text-align: start; text-indent: =
0px; text-transform: none; white-space: normal; widows: auto; =
word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=3D""><br =
class=3D""></div><br class=3D"Apple-interchange-newline"></div><br =
class=3D"Apple-interchange-newline">
</div>
<br class=3D""></div></body></html>=

--Apple-Mail=_56936A74-9FF6-43F0-9B01-C71E5025FB74--



From nobody Thu Oct 29 09:38:04 2020
Return-Path: <daedulus@btconnect.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 03A2B3A08A6; Thu, 29 Oct 2020 09:37:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.147
X-Spam-Level: 
X-Spam-Status: No, score=-2.147 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, MSGID_FROM_MTA_HEADER=0.001, NICE_REPLY_A=-0.247, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=btconnect.onmicrosoft.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 DV7onBWiIVwU; Thu, 29 Oct 2020 09:37:55 -0700 (PDT)
Received: from EUR01-HE1-obe.outbound.protection.outlook.com (mail-eopbgr130130.outbound.protection.outlook.com [40.107.13.130]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0BFA83A07A0; Thu, 29 Oct 2020 09:37:54 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=ngVPbf83FDZiTGzUGkWt9Pn10+hlLDkrq62FEDbHGLW1gYsrN9/JBdGjYUxFQGjU28r35i3LQcu38YUKO16rJDRUykv092M18ofSK02wzX+FkoJX5iiW7QUnz3MlCWAFwnD65mL6v8UdHyqrjQHo23USsnnFRFSKeGAVyZofeGvNv5nNOc+VMdCqC3nZ1M19Ej18Yn/Dy6yiwUTRou2FX5fPejgKzH2Y9A+r5gtU+IL1NSMtcXuPjVmgsa04ARTjTOnq3funlHah24hWWXn9yDhhbvkRwSMsWQsMqxoQuTXguUrb0QGNqhrugtfcXjlTTu4Go9p0CGvvdYosV27EtQ==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=outilAOJ5Ny5SBdeLWQvHGBxEiY/vV9p4qKfc3ImuMg=; b=fdua+oPBUDG5Yix+44urmiQbRk3soKSZI7pvNS58m3wptmwoLlV+F1PJC3SkF2QHbkZ2n3H5A4YQeWXLIQGRfmkCZz0IDKwlwFrCsnsua8hQGZvcPo/PKbAMTjB015libo/FU0WBN/dn+8JgBnjSWpvMOjqlz2qRqZROEzdUg1Om+y+r0dLgVQn87OZgy0c0D2cD1FAo1NCTaQGC8MLxj5gkuSyrtOIfiBjvLKM8yCjAexCu00gPzwnSdfJOyIEPY+gnVShao70b+JNKf8oaKJ23jAPbulphwSalU+rVvy6S8lVdeY3X1FSKASbWXV42yJVmfaHJzLT01gxXG/jJuw==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=btconnect.com; dmarc=pass action=none header.from=btconnect.com; dkim=pass header.d=btconnect.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=btconnect.onmicrosoft.com; s=selector2-btconnect-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=outilAOJ5Ny5SBdeLWQvHGBxEiY/vV9p4qKfc3ImuMg=; b=lgCVPtq7FbQ/DmROVnrDQMmncCgDs3pyZ0XX7zz65SPENoVIsq4iLWymwfoQv4cMf37luVuUrP0AyXf5RSUodLoTy3ajkRB1JEOVXDwwqZuHAm/nmwRWk8zVm+MmgkSVdjgNHl5w0s/wEVTA1XPFrCsXVY5now8wDzpk6HR3q9o=
Authentication-Results: gmail.com; dkim=none (message not signed) header.d=none;gmail.com; dmarc=none action=none header.from=btconnect.com;
Received: from DBAPR07MB6695.eurprd07.prod.outlook.com (2603:10a6:10:18a::15) by DBAPR07MB7046.eurprd07.prod.outlook.com (2603:10a6:10:196::8) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3499.4; Thu, 29 Oct 2020 16:37:47 +0000
Received: from DBAPR07MB6695.eurprd07.prod.outlook.com ([fe80::b1d9:17c1:e593:89e9]) by DBAPR07MB6695.eurprd07.prod.outlook.com ([fe80::b1d9:17c1:e593:89e9%6]) with mapi id 15.20.3455.029; Thu, 29 Oct 2020 16:37:47 +0000
To: Rafa Marin-Lopez <rafa@um.es>
References: <160337357077.29083.9236626834026808055@ietfa.amsl.com> <EE5AB669-73BB-4517-A6F4-23B7807FB36E@um.es> <5F9815D1.9010303@btconnect.com> <DDE550B1-9A9E-4954-B6F9-C0A33ECE1275@um.es> <5F99B221.3040504@btconnect.com> <56155C91-BFE8-4BA9-A55C-46B12E59CD94@um.es>
Cc: i2nsf@ietf.org, Gabriel Lopez <gabilm@um.es>, Fernando Pereniguez-Garcia <fernando.pereniguez@cud.upct.es>, last-call@ietf.org, ynir.ietf@gmail.com
From: tom petch <daedulus@btconnect.com>
Message-ID: <5F9AEFD3.90903@btconnect.com>
Date: Thu, 29 Oct 2020 16:37:39 +0000
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:38.0) Gecko/20100101 Thunderbird/38.5.0
In-Reply-To: <56155C91-BFE8-4BA9-A55C-46B12E59CD94@um.es>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
X-Originating-IP: [86.146.121.140]
X-ClientProxiedBy: LO4P123CA0039.GBRP123.PROD.OUTLOOK.COM (2603:10a6:600:152::8) To DBAPR07MB6695.eurprd07.prod.outlook.com (2603:10a6:10:18a::15)
MIME-Version: 1.0
X-MS-Exchange-MessageSentRepresentingType: 1
Received: from [192.168.1.65] (86.146.121.140) by LO4P123CA0039.GBRP123.PROD.OUTLOOK.COM (2603:10a6:600:152::8) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.20.3499.19 via Frontend Transport; Thu, 29 Oct 2020 16:37:47 +0000
X-MS-PublicTrafficType: Email
X-MS-Office365-Filtering-Correlation-Id: 4cffc856-0d2c-4964-fbb5-08d87c28f80a
X-MS-TrafficTypeDiagnostic: DBAPR07MB7046:
X-Microsoft-Antispam-PRVS: <DBAPR07MB7046CC1DC517124FC86E47C9C6140@DBAPR07MB7046.eurprd07.prod.outlook.com>
X-MS-Oob-TLC-OOBClassifiers: OLM:9508;
X-MS-Exchange-SenderADCheck: 1
X-Microsoft-Antispam: BCL:0;
X-Microsoft-Antispam-Message-Info: 6CDgWmknium62UP1XiFlx44+PHAHewAxVwqPZ9z5zmnupMXExgvgPxxg8wtp13KGuKfJe5Nx0mCZD/DndJEmpD0UKIiYzM/T5fucQ0OIBd6VNvh3UmE73Uvv5Qo8PK0a5WyFXWXKYFIcX0q8PCgOm4OfihKMip2hRP3UhjQdAFg3InLANvimEpsA//daa0LkYqnESthPQiPqDRE9VgLcesORo6yPjBLmmOUmAhmne0P0EqksKTCXZgEfESIC1fUSHCp5hE2Je27hlkI90dSOX0+4E/8C2y9QqSCV/84qofptAT1Ggpv/ZfpKdJJPp8NT72H7/3ShSvORE8bnKhhTFxJk6S+c8CfCoMqeC+HWbCEIC8d6NrnpfAL9Rng6cmymp8+cY3rw7rpATgWFbe1648ka48J1PmB6CSrV9K+dM1Jpme2biJH175OrhXxnr6WHcr0zC+3ncK048gmj78yd+w==
X-Forefront-Antispam-Report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;  IPV:NLI; SFV:NSPM; H:DBAPR07MB6695.eurprd07.prod.outlook.com; PTR:; CAT:NONE;  SFS:(366004)(39860400002)(376002)(346002)(136003)(396003)(8676002)(33656002)(8936002)(16576012)(54906003)(2616005)(956004)(316002)(86362001)(15650500001)(53546011)(2906002)(966005)(4001150100001)(6486002)(36756003)(52116002)(186003)(16526019)(478600001)(4326008)(30864003)(5660300002)(6916009)(26005)(66946007)(6666004)(83380400001)(66556008)(66476007)(66574015)(43740500002); DIR:OUT; SFP:1102; 
X-MS-Exchange-AntiSpam-MessageData: 1b5m6ClAPkEizHuEU7aOYe2hk1q1Wp/eov3PayEsux8I31ErcGFiml9EIrhiNHSFqmPcGN93RxjZFJhfyR4id5MAHDJSiCnemLngqMrrlpfPxSzNkyibivnyR6YVZUEZH/GZ0Y6XuZs40HEvfPUdH8UasoOeDg2a8NMhoRQzfZprPMMpp3P2DNDzsbNKp9S58OmTbKHm3m/s0ggdWOj2/TAKHwxKkPv05rsKJyagcABtPnz0C6xu4UYLFwm64MoJntzxsdtnyW5MBsjRicrVpu84cxK/0jx6NN41nuXOjGFzoFORK0sAsvmsAqYGYAI84YlHa96BbmwcFxn2vSaC6fwQMtmDmF354TVVy/ErQeFyfRA8ukKlKDh/DW2IZhW7YKu8ZsGKYUxwsEn+PFs6nZD6FT1MSsDk+1yXjmFtGjjXp02AesVsALdCdFsaA53E+EjMG8MsoqZz84YTl0nlevmVr+XoiO81ANrrH4p+LwkTjjlX2DalOEMxodnqwexvJ801hGyiuWhFjryjN8b48vDZqcKwOLyb1wSfJbUA9VvalOHBcIUwGmJILQwjBvRg8vHydF2eAi4MAIi/rKtUHttYof6fA/U5RMw2yCfkd/nxw871Z6QnHyu6z72efpwx0+k1g3hfk5QUA+Kd64xzcw==
X-OriginatorOrg: btconnect.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 4cffc856-0d2c-4964-fbb5-08d87c28f80a
X-MS-Exchange-CrossTenant-AuthSource: DBAPR07MB6695.eurprd07.prod.outlook.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 29 Oct 2020 16:37:47.8116 (UTC)
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-CrossTenant-Id: cf8853ed-96e5-465b-9185-806bfe185e30
X-MS-Exchange-CrossTenant-MailboxType: HOSTED
X-MS-Exchange-CrossTenant-UserPrincipalName: MTYLWpgyoLaSoS60vyqIGaYNG1LMUmmOo0hZtDGnagG9C3JvPByly7biY79QbAIxEu+klmYXXAa6rfarLGu8bA==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DBAPR07MB7046
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2nsf/oclaUEcQV05MUeNsblSXdg94J4o>
Subject: Re: [I2nsf] [Last-Call] New Version Notification for draft-ietf-i2nsf-sdn-ipsec-flow-protection-11.txt
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: Thu, 29 Oct 2020 16:37:59 -0000

Top posting a new, related issue that may need Security AD or WG Chair 
to act on.

It seems to me that the IANA entries for IKEv2 are incomplete.  RFC8247 
does a fine job of specifying algorithms and adding information such as 
status (MUST/SHOULD+), IoT, AEAD and so on, information which is not 
present on IANA.  The policy for, e.g. Transform Type 1, is expert 
review and entries have been added via draft-smyslov-esp-gont but the 
IANA entries lack this information and, looking at the I-D, I see no 
such information (nor is there any reason for it to be there).  Yet 
draft-ietf-i2nsf-sdn... needs this information as references in the YANG 
module show.

It seems to me that this is a similar situation to that which the TLS WG 
found itself in and which led to a revision of the TLS IANA entries to 
provide what was needed via additional columns.

I think that the IANA pages for IKEv2 need revising so that that 
additional information that RFC8247 provides is required as additional 
columns in the IANA entries at least for Type 1, Type 2, Type 3, Type 4 
and Authentication Method.

Tom Petch

On 29/10/2020 11:23, Rafa Marin-Lopez wrote:
> Hi Tom:
>
>> El 28 oct 2020, a las 19:02, tom petch <daedulus@btconnect.com> escribió:
>>
>> On 28/10/2020 10:42, Rafa Marin-Lopez wrote:
>>> Hi Tom:
>>>
>>> Thank you very much for your insight. It is very helpful. Please see our comments/questions inline.
>>>
>>>> El 27 oct 2020, a las 13:42, tom petch <daedulus@btconnect.com> escribió:
>>>>
>>>> I think that the IESG will find a number of problems with this I-D.
>>>>
>>>> YANG module references RFC822 which is several years out of date
>>
>> Rafa
>>
>> On boiler plate, I mean the reference to RFC2119 which now must use the language from RFC8174 in the body of the I-D; sorry for the confusion.
>
> Ah ok. I guess you are referring to change that paragraph with this:
>
>
> The key words "MUST", "MUST NOT", "REQUIRED",
> "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT",
> "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
> "OPTIONAL" in this document are to be interpreted
> as described in BCP 14 RFC2119 RFC8174 when,
> and only when, they appear in all capitals,
> as shown here.
>
>>
>> On XXXX, you have XXXX standing in for more than one RFC-to-be which confuses.  The convention is to use XXXX for this I-D and then AAAA BBBB etc for any others such as the netconf I-D in this instance.
>
> Ah ok. In any case, we have now only XXXX for our RFC-to-be so problem fixed.
>>
>> Two big issues, for me (perhaps not for others).  The convention with YANG is for each successive line to be indented two characters, you have four, which creates a lot of white space and pushes the text to the right hand margin.  I think that two characters is the default when you use pyang to format a YANG module.
>
> We can try to reduce it to two characters.
>
>>
>> And references.  I have had to work harder than I want to to make sense of the IANA references.  I think you should have five separate references in the I-D for IANA for
>> Transform Type 1
>> Transform Type 3
>> Transform Type 4
>> Authentication Method
>> Protocol Numbers
>> and each reference in the I-D should have a URL pointing to the specific section of IANA web site.
>
> Ok, good. This follows what we thought.
>
>> In the YANG, it is harder to know what to do.  Those first three references are in the third tier i.e.
>> Group - Internet Key Exchange V2 (IKEv2) Parameters
>> Registry  -Transform Attribute Types
>> and then Type 1, 3, 4 as the third tier as I am calling it
>> and I think that every reference in the YANG should give me all three tiers after IANA in that order perhaps
>> IANA; IKEv2 Parameters; Transform Atribute Types; Transform Type 1
>
> Great. We also considered this as a possible solution after sending our e-mail. Let’s do it.
>
>> If the syntax needs tweeking, then the RFC Editor will do a good job of that but at present the references are inconsistent in which elements are specified in what order and that is something the RFC Editor probably cannot cope with.
>> Authentication Method is a registry so that just needs Group name and Registry name after IANA.
>
> Ok, good.
>>
>> Some minor glitches.
>> I-D appears twice in the body of the I-D - perhaps document or memo.
>
> Ok.
>
>> objetives/objectives/
>
> Fixed.
>> end port number perhaps /must/MUST/
>
>> and YANG is very good at including such checks with a must ....
>> 'If AEAD is used .. where? this occurs in several places and I think that you need to specify the leaf where AEAD will be specified or implied.
>
> Ok we have changed it to:
>
> If Authenticated Encryption with Associated Data (AEAD) is used (leaf esp-algorithms/encryption/algorithm-type)
> this flag MUST be false."
>
>> And is it possible to make that a YANG 'must' statement - looking at the IKEv2 registries it is not obvious which are AEAD so that might be more complexity than it is worth.
>> 'only available on linux kernels' Um implementation detail, you may get asked to remove that altogether or at least to a Informative Appendix - I would leave it in for now.
>
> Ok.
>
>> 'import ietf-i2nsf-ikec' the reference needs to be to a RFC and if it is not yet an RFC then RFC XXXX <title> in both Appendix B and C
>
> Yes, we have changed that to:
>
> RFC XXXX: Software-Defined Networking
>                 (SDN)-based IPsec Flow Protection.
>
>> leaf-list pfs-groups could do with a reference - Transform Type 4?
>
> The leaf list is referring to type pfs-group and we have now
>
> typedef pfs-group {
>              type uint16;
>              description
>                  "DH groups for IKE and IPsec SA rekey.";
>              reference
>                  "IANA; Internet Key Exchange V2 (IKEv2) Parameters;
> 				Transform Atribute Types; Transform Type 4 -
>                  Diffie-Hellman Group Transform IDs.
> 				Section 3.3.2 in RFC 7296.";
>          }
>
>
>>
>> I am still working my way through the YANG so may have some more comments tomorrow.
>
> Ok, do not worry we will work in -12 with these comments so far to have a quick response. We can prepare a another version later with the rest of them.
>
> Thank you very much for your effort.
>>
>> Tom Petch
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>> We have realized that we missed to change this, even though we discussed it. We will change it right away in the following way (bold):
>>>
>>> case rfc822-address-string {
>>>       leaf rfc822-address-string {
>>>            type string;
>>>            description
>>>                "Specifies the identity as a
>>>                 fully-qualified RFC5322 email
>>>                 address string. An example is,
>>>                 jsmith@example.com. The string
>>>                 MUST NOT contain any
>>>                 terminators e.g., NULL, CR,
>>>                 etc.).";
>>>             reference
>>>                    "RFC 5322.";
>>>       }
>>> }
>>>
>>> Btw, we already used in the past “case rfc822-address-string” and “leaf rfc822-address-string” since this is coming from IKEv2 standard. Do you think we should change that name as well?
>>>
>>>
>>>>
>>>> YANG module references IANA Protocol Numbers which is not in the I-D references
>>>
>>> We have included the following reference:
>>>
>>> [IANA-Protocols-Number]
>>>                Internet Assigned Numbers Authority (IANA), "Protocol
>>>                Numbers", January 2020.
>>>
>>>
>>>>
>>>> s.2 boiler plate is out of date
>>>
>>> What we see is the I-D has the second choice stated in https://www.ietf.org/standards/ids/guidelines/
>>>
>>> This Internet-Draft is submitted in full conformance with the
>>>     provisions of BCP 78 and BCP 79.
>>>
>>>     Internet-Drafts are working documents of the Internet Engineering
>>>     Task Force (IETF).  Note that other groups may also distribute
>>>     working documents as Internet-Drafts.  The list of current Internet-
>>>     Drafts is at https://datatracker.ietf.org/drafts/current/.
>>>
>>>     Internet-Drafts are draft documents valid for a maximum of six months
>>>     and may be updated, replaced, or obsoleted by other documents at any
>>>     time.  It is inappropriate to use Internet-Drafts as reference
>>>     material or to cite them other than as "work in progress."
>>>
>>> Could you refer what is out of date?
>>>
>>>>
>>>> XXXX is standing in for more than one RFC
>>>
>>> Yes, XXXX has been used because we do not know the future number assigned to our I-D.
>>>
>>> Also we realized we also included this to refer to crypto-types I-D but this has been solved now in a new version -12 that we are preparing to include your comments. We noticed we can replace the type of rw cert-data?, ca-data*, crl-data? for binary without any problem.
>>>
>>> |           |     +--rw cert-data?        binary
>>> |           +--rw private-key?            binary
>>> |           +--rw ca-data*                binary
>>> |           +--rw crl-data?               binary
>>>
>>>>
>>>> but the show stopper that makes a proper review of this too costly is the references.  Those to IANA of which there are several I want to pursue.  The I-D reference is to IKEv2 parameters. Sadly, this is a three tier structure and noone agrees on what to call the third tier so I will call it tier3 here.  Top level is Group, as per RFC8126, second level is Registry.  The I-D reference is to the Group only which is fine if the actual reference then specifies the Registry and Tier3 but they never do, usually just Tier3 e.g. Transform Type 3 which makes for a lot of work for the reader, too much for this one.  You have to go hunting in all the second level Registry until you can find a match for the Tier3 identifier. And there are no URL.  If you want an example that I find easy to use, go look at RFC8407 (as usual).
>>>
>>> You’re right. Could you point the exact part at RFC 8407 with that example? We would really appreciate it.
>>>
>>> On the other hand, would it be enough to include the URL for Transform Type 3 https://www.iana.org/assignments/ikev2-parameters/ikev2-parameters.xhtml#ikev2-parameters-7 ?
>>>
>>> (Same for Transform Type 1, Transform Type 4)
>>>
>>>>
>>>> The reference for import of i2nsf-ikec gives a YANG module name; this needs to be the name of the RFC to be
>>>
>>> Fixed.
>>>
>>> import ietf-i2nsf-ikec {
>>>              prefix nsfikec;
>>>              reference
>>>                  "RFC XXXX: Software-Defined Networking
>>>                 (SDN)-based IPsec Flow Protection.";
>>> }
>>>
>>> We still use XXXX because we do not know the number assigned to the RFC to be.
>>>
>>>>
>>>> The example IPv6 address in the YANG module has :0:0: which is usually just ::
>>>
>>> Fixed.
>>>
>>> If you have any further comments, please let us know so we can include them in -12
>>>
>>> Best Regards.
>>>>
>>>> And I have some way to go still.
>>>>
>>>> Tom Petch
>>>>
>>>> On 22/10/2020 18:39, Rafa Marin-Lopez wrote:
>>>>> Dear all:
>>>>>
>>>>> After receiving a suggestion to make things clearer in the feature ikeless-notification description, we have just uploaded a new version -11 with a minor change to add the following text:
>>>>>
>>>>> feature ikeless-notification {
>>>>>              description
>>>>>                  "This feature indicates that the server supports
>>>>>                  generating notifications in the ikeless module.
>>>>>
>>>>>                  To ensure broader applicability of this module,
>>>>>                  the notifications are marked as a feature.
>>>>>                  For the implementation of ikeless case,
>>>>>                  the NSF is expected to implement this
>>>>>                  feature.";
>>>>>          }
>>>>>
>>>>> Best Regards.
>>>>>
>>>>>> Inicio del mensaje reenviado:
>>>>>>
>>>>>> De: internet-drafts@ietf.org
>>>>>> Asunto: New Version Notification for draft-ietf-i2nsf-sdn-ipsec-flow-protection-11.txt
>>>>>> Fecha: 22 de octubre de 2020, 15:32:50 CEST
>>>>>> Para: "Fernando Pereniguez-Garcia" <fernando.pereniguez@cud.upct.es>, "Rafael Lopez" <rafa@um.es>, "Gabriel Lopez-Millan" <gabilm@um.es>, "Rafa Marin-Lopez" <rafa@um.es>
>>>>>>
>>>>>>
>>>>>> A new version of I-D, draft-ietf-i2nsf-sdn-ipsec-flow-protection-11.txt
>>>>>> has been successfully submitted by Rafa Marin-Lopez and posted to the
>>>>>> IETF repository.
>>>>>>
>>>>>> Name:		draft-ietf-i2nsf-sdn-ipsec-flow-protection
>>>>>> Revision:	11
>>>>>> Title:		Software-Defined Networking (SDN)-based IPsec Flow Protection
>>>>>> Document date:	2020-10-22
>>>>>> Group:		i2nsf
>>>>>> Pages:		92
>>>>>> URL:            https://www.ietf.org/archive/id/draft-ietf-i2nsf-sdn-ipsec-flow-protection-11.txt
>>>>>> Status:         https://datatracker.ietf.org/doc/draft-ietf-i2nsf-sdn-ipsec-flow-protection/
>>>>>> Htmlized:       https://datatracker.ietf.org/doc/html/draft-ietf-i2nsf-sdn-ipsec-flow-protection
>>>>>> Htmlized:       https://tools.ietf.org/html/draft-ietf-i2nsf-sdn-ipsec-flow-protection-11
>>>>>> Diff:           https://www.ietf.org/rfcdiff?url2=draft-ietf-i2nsf-sdn-ipsec-flow-protection-11
>>>>>>
>>>>>> Abstract:
>>>>>>    This document describes how to provide IPsec-based flow protection
>>>>>>    (integrity and confidentiality) by means of an Interface to Network
>>>>>>    Security Function (I2NSF) controller.  It considers two main well-
>>>>>>    known scenarios in IPsec: (i) gateway-to-gateway and (ii) host-to-
>>>>>>    host.  The service described in this document allows the
>>>>>>    configuration and monitoring of IPsec Security Associations (SAs)
>>>>>>    from a I2NSF Controller to one or several flow-based Network Security
>>>>>>    Functions (NSFs) that rely on IPsec to protect data traffic.
>>>>>>
>>>>>>    The document focuses on the I2NSF NSF-facing interface by providing
>>>>>>    YANG data models for configuring the IPsec databases (SPD, SAD, PAD)
>>>>>>    and IKEv2.  This allows IPsec SA establishment with minimal
>>>>>>    intervention by the network administrator.  It does not define any
>>>>>>    new protocol.
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> Please note that it may take a couple of minutes from the time of submission
>>>>>> until the htmlized version and diff are available at tools.ietf.org.
>>>>>>
>>>>>> The IETF Secretariat
>>>>>>
>>>>>>
>>>>>
>>>>> -------------------------------------------------------
>>>>> 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
>>>>> -------------------------------------------------------
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>
>>> -------------------------------------------------------
>>> 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
>>> -------------------------------------------------------
>>>
>>>
>>>
>>>
>>>
>
> -------------------------------------------------------
> 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
> -------------------------------------------------------
>
>
>
>
>


From nobody Thu Oct 29 10:06:44 2020
Return-Path: <daedulus@btconnect.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 69A283A0A84; Thu, 29 Oct 2020 10:06:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.147
X-Spam-Level: 
X-Spam-Status: No, score=-2.147 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, MSGID_FROM_MTA_HEADER=0.001, NICE_REPLY_A=-0.247, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=btconnect.onmicrosoft.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 RJqd7PEwfPT2; Thu, 29 Oct 2020 10:06:36 -0700 (PDT)
Received: from EUR04-VI1-obe.outbound.protection.outlook.com (mail-eopbgr80090.outbound.protection.outlook.com [40.107.8.90]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5AE793A0A81; Thu, 29 Oct 2020 10:06:32 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=UFEegz/Wr523vutiOkRXtCaQHutLk/GtVmWvbu4Y8M7wQFtq/oqcFRTo4ZVysuPxfvlfmlHJzSseaL1R09YP+Vd2Eb+nLaUnyIBhrnMsUBUMqKUtxlYziLJosEbNtiUiw8j97VoNrkOaDzeQoHA0kYYS1B5ebQ23hixG27uL1AiNsorDX/El3lYlGK/FXzJ29oSyDoSVFGd6sH0SXYeSimxQ/4vP7Tz7e4d6stmed4MF9erVMNn8q62VNk5ao/EWdaYpLxLcWbA5KEz4n3H4KFMKDlw2PoJaznrr3zo8hJlk1MqEEm1QOUsMnUIUTHsOgnhQQrz/Eh2g9RdZSJEbXQ==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=pqBbQWfmTW0kVsReQFuInboguEDya75rtjPMO/GqN/E=; b=e6qkIpKfUwftoIdOl2xbA/F/pdnmbOvfpCguePJuIB4An1OCotZ9nTkoSIXJaNRja//ewqlWQiGWrI+NFgfIDVA2BtuaJP1mnqnYmVrsf5lqlIKhFlEF11xAQGTmW6IyvaPEymMCtWTWi+kBHVjEgn9xqAqbdyND3QEeL5WKOQnSDeOsXzViyLaPc6H0uR+TmhscHNKtuCyNIwDwWDlryLIJQklIW3qio7KGIU6UV83jj9d3iFf86OsA+FuKdGnEXo0XC5wQ7GDC9GEn4i14V+uiPWiU4EDvrVv9IXbzsTKVsPGBi5fweuG9xk9I9908kxQcgqCdpEKBAtij2pwhyQ==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=btconnect.com; dmarc=pass action=none header.from=btconnect.com; dkim=pass header.d=btconnect.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=btconnect.onmicrosoft.com; s=selector2-btconnect-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=pqBbQWfmTW0kVsReQFuInboguEDya75rtjPMO/GqN/E=; b=Vn+hK+1J5gJkxRWpPN8wtiMcS5HCO9NuPGA80vNR7czvL84phripqWNyJX2ynayo2FdiiX6xlbvwFbjOuecvLHvgDTzbXrMEAgoq+jRrTrgg/71skDpoPevYD5HAOGnmhRcXq1DkfFUmtKOutgkuUmDoRGuVdvxilDKmAryDbic=
Authentication-Results: gmail.com; dkim=none (message not signed) header.d=none;gmail.com; dmarc=none action=none header.from=btconnect.com;
Received: from DBAPR07MB6695.eurprd07.prod.outlook.com (2603:10a6:10:18a::15) by DB6PR0701MB2758.eurprd07.prod.outlook.com (2603:10a6:4:22::12) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3499.8; Thu, 29 Oct 2020 17:06:29 +0000
Received: from DBAPR07MB6695.eurprd07.prod.outlook.com ([fe80::b1d9:17c1:e593:89e9]) by DBAPR07MB6695.eurprd07.prod.outlook.com ([fe80::b1d9:17c1:e593:89e9%6]) with mapi id 15.20.3455.029; Thu, 29 Oct 2020 17:06:29 +0000
To: Rafa Marin-Lopez <rafa@um.es>
References: <160337357077.29083.9236626834026808055@ietfa.amsl.com> <EE5AB669-73BB-4517-A6F4-23B7807FB36E@um.es> <5F9815D1.9010303@btconnect.com> <DDE550B1-9A9E-4954-B6F9-C0A33ECE1275@um.es> <5F99B221.3040504@btconnect.com> <56155C91-BFE8-4BA9-A55C-46B12E59CD94@um.es>
Cc: i2nsf@ietf.org, Gabriel Lopez <gabilm@um.es>, Fernando Pereniguez-Garcia <fernando.pereniguez@cud.upct.es>, last-call@ietf.org, ynir.ietf@gmail.com
From: tom petch <daedulus@btconnect.com>
Message-ID: <5F9AF68D.7060105@btconnect.com>
Date: Thu, 29 Oct 2020 17:06:21 +0000
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:38.0) Gecko/20100101 Thunderbird/38.5.0
In-Reply-To: <56155C91-BFE8-4BA9-A55C-46B12E59CD94@um.es>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
X-Originating-IP: [86.146.121.140]
X-ClientProxiedBy: LO2P123CA0002.GBRP123.PROD.OUTLOOK.COM (2603:10a6:600:a6::14) To DBAPR07MB6695.eurprd07.prod.outlook.com (2603:10a6:10:18a::15)
MIME-Version: 1.0
X-MS-Exchange-MessageSentRepresentingType: 1
Received: from [192.168.1.65] (86.146.121.140) by LO2P123CA0002.GBRP123.PROD.OUTLOOK.COM (2603:10a6:600:a6::14) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.20.3499.19 via Frontend Transport; Thu, 29 Oct 2020 17:06:28 +0000
X-MS-PublicTrafficType: Email
X-MS-Office365-Filtering-Correlation-Id: 6a68573e-4416-45b2-fbbc-08d87c2cfa5d
X-MS-TrafficTypeDiagnostic: DB6PR0701MB2758:
X-Microsoft-Antispam-PRVS: <DB6PR0701MB275865AFFB2DF937A80BBD1CC6140@DB6PR0701MB2758.eurprd07.prod.outlook.com>
X-MS-Oob-TLC-OOBClassifiers: OLM:9508;
X-MS-Exchange-SenderADCheck: 1
X-Microsoft-Antispam: BCL:0;
X-Microsoft-Antispam-Message-Info: igGHrwzhhb/+LqMyVG8fEfFolZuCfjvrPY923tioC84bh9Bsi2aAruMce+y4WmlvQwkoggFEfCrsbP2YagAHIod2gTPuR4E/3o4apqgJUJLKpK2qjUSGOyWEMFMMeHlEfOHVsQVMFYwybVijSFqRRs7mEknEBHo5iodgFHhYllRr+xcr023fH0B4hMyAEeuTSRDqDqBRFWyB+hk49RTkegeyYv2G3THY7+KhCtKpeFNosPLyyVhaj/UeMCFIM5bEQXC+wLgwIcaI8qCnwYnReYV+nh0qCBWg+aWk6hQXyawlyMN4bzsIO809UH+Z/5822jjsVNXrAmDJZJQtVP64hpXxRLRQydDtcC67O4VNpIG9h3Z1Qqzg4zbc7JzU8RsFT5NUkLMxUqiNzIujkCnEhA==
X-Forefront-Antispam-Report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;  IPV:NLI; SFV:NSPM; H:DBAPR07MB6695.eurprd07.prod.outlook.com; PTR:; CAT:NONE;  SFS:(396003)(376002)(39860400002)(346002)(136003)(366004)(66946007)(8676002)(966005)(316002)(5660300002)(956004)(66476007)(66556008)(478600001)(36756003)(2906002)(6916009)(6666004)(8936002)(83380400001)(66574015)(52116002)(87266011)(4326008)(30864003)(33656002)(2616005)(15650500001)(53546011)(4001150100001)(26005)(54906003)(16576012)(186003)(6486002)(16526019)(86362001); DIR:OUT; SFP:1102; 
X-MS-Exchange-AntiSpam-MessageData: jcO6ECgAseubkpGBp7QLb3s2cGiEj/UhUYSkdBHbnjFVwFWsq6qut4mntoAXfv6bdjq/ypraX9vpyP3JXPEY8u5tekqTpLI1GwF/mAjw1MzK+LmTQnwc0hKV9u8N505ZOs76KMw2PN1PavlLRluWN00kTliV0BrqPOvEVD8e+c5zkURZQj7LMt12XwcQYeZCcc3EiFgC6NdqnGjBELpmp+EQYuymyvdVcuxNHUE4C4eFsD/lHy82m8Na5EX7Xod7sVmmL7MEs3aNZWrbRpExTIzIbo9m8Cxik6FHjbvm0p6gPpArI1I18FwzFik9MGGrd7rKmayyPZgsJfLJNu3talkgaLQZslxkb6L8dsQsCvQCo5yRiJtRhcUjGwbItQ5CdBEtqLFrkP4QzpZgnRgW1mq6mvuNhDH/LEXU+A3/SNx4Msmasb1IGHLVbISwZt04oqYIaZOmHfLucvEOBpFMI4dNrNurR9IZ1HjcowM4oJDbSHEEFuROE69u0rWCNaLHAGH/ncoK00awAtITeUoAuEGSwgj8vqCqos4Nql2kZE0fDHRF06Vz0/CkyJLWGWsyR1vSKvQ1YeuVHFYbgSJHTJRgEdh/JbToMZb8A0w1PyswmDk68PNdp28ISTbkh1nJdMUN6RV3OWppepOFykni3g==
X-OriginatorOrg: btconnect.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 6a68573e-4416-45b2-fbbc-08d87c2cfa5d
X-MS-Exchange-CrossTenant-AuthSource: DBAPR07MB6695.eurprd07.prod.outlook.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 29 Oct 2020 17:06:29.5775 (UTC)
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-CrossTenant-Id: cf8853ed-96e5-465b-9185-806bfe185e30
X-MS-Exchange-CrossTenant-MailboxType: HOSTED
X-MS-Exchange-CrossTenant-UserPrincipalName: Sj69Qf1fy6ArQwRBIM6SGbM0eKSEFtMLjrEshycQz9Cm7vl236UrbqmnUB/V+2wUatz+rE/NUJsELBuhDoB7dQ==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DB6PR0701MB2758
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2nsf/XaL2TbIRV96LDzJVhnH4W-R4M6g>
Subject: Re: [I2nsf] [Last-Call] New Version Notification for draft-ietf-i2nsf-sdn-ipsec-flow-protection-11.txt
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: Thu, 29 Oct 2020 17:06:40 -0000

Back to routine comments on this I-D; I don't think that any of my 
earlier ones are unresolved.

On 29/10/2020 11:23, Rafa Marin-Lopez wrote:
> Hi Tom:
>
>> El 28 oct 2020, a las 19:02, tom petch <daedulus@btconnect.com> escribió:
>>
>> On 28/10/2020 10:42, Rafa Marin-Lopez wrote:
>>> Hi Tom:
>>>
>>> Thank you very much for your insight. It is very helpful. Please see our comments/questions inline.
>>>
>>>> El 27 oct 2020, a las 13:42, tom petch <daedulus@btconnect.com> escribió:
>>>>
>>>> I think that the IESG will find a number of problems with this I-D.
>>>>
>>>> YANG module references RFC822 which is several years out of date

Rafa

Several YANG leaf are in seconds, eight I think, but none use the YANG
units seconds;
statement.  I suggest adding it.

typedef ipsec-spd-action
capitalises the actions as does RFC4301 but later uses of this have 
lower case actions; probably ok as it is

protocol number appears in several places but technically, IPv6, which 
we must all love and promote, has 'next header' instead.  Probably 
worth a mention at least once in the YANG module

On the start >= end, I was looking at nat-yang and it has
  must ". >= ../start-port-number"
which is the sort of YANG constraint I had in mind

leaf dscp-mapping
I do not understand, a hex string of indeterminate length for DSCP 
values (plural).  I expect DSCP to be six bit and values to be a leaf-list

leaf ecn
/Annex C/Appendix C/

I see that RFC8247 gives AEAD status which is a good reference to have 
except that as my other post today says there is no requirement for any 
future additions to the IANA data to include this information; IANA for 
IKEv2 needs updating iun a separate I-D!

leaf mask
hex-string with no length specified

leaf ds-algorithm
default 1
which I think is RSA; worth stating as it might raise some AD eyebrows

pfs-groups
/it is required perfect forward secrecy/perfect forward secrecy is required/
and a reference to Transform Type 4?

leaf ext-seq-num
/FALSE/false/ or /False/?

leaf encryption-algorithm (twice, in separate containers)
/the integrity leaf/ the integrity-algorithm leaf/

I have yet to look at the text or the examples, probably next week.

Tom Petch










>>
>> On boiler plate, I mean the reference to RFC2119 which now must use the language from RFC8174 in the body of the I-D; sorry for the confusion.
>
> Ah ok. I guess you are referring to change that paragraph with this:
>
>
> The key words "MUST", "MUST NOT", "REQUIRED",
> "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT",
> "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
> "OPTIONAL" in this document are to be interpreted
> as described in BCP 14 RFC2119 RFC8174 when,
> and only when, they appear in all capitals,
> as shown here.
>
>>
>> On XXXX, you have XXXX standing in for more than one RFC-to-be which confuses.  The convention is to use XXXX for this I-D and then AAAA BBBB etc for any others such as the netconf I-D in this instance.
>
> Ah ok. In any case, we have now only XXXX for our RFC-to-be so problem fixed.
>>
>> Two big issues, for me (perhaps not for others).  The convention with YANG is for each successive line to be indented two characters, you have four, which creates a lot of white space and pushes the text to the right hand margin.  I think that two characters is the default when you use pyang to format a YANG module.
>
> We can try to reduce it to two characters.
>
>>
>> And references.  I have had to work harder than I want to to make sense of the IANA references.  I think you should have five separate references in the I-D for IANA for
>> Transform Type 1
>> Transform Type 3
>> Transform Type 4
>> Authentication Method
>> Protocol Numbers
>> and each reference in the I-D should have a URL pointing to the specific section of IANA web site.
>
> Ok, good. This follows what we thought.
>
>> In the YANG, it is harder to know what to do.  Those first three references are in the third tier i.e.
>> Group - Internet Key Exchange V2 (IKEv2) Parameters
>> Registry  -Transform Attribute Types
>> and then Type 1, 3, 4 as the third tier as I am calling it
>> and I think that every reference in the YANG should give me all three tiers after IANA in that order perhaps
>> IANA; IKEv2 Parameters; Transform Atribute Types; Transform Type 1
>
> Great. We also considered this as a possible solution after sending our e-mail. Let’s do it.
>
>> If the syntax needs tweeking, then the RFC Editor will do a good job of that but at present the references are inconsistent in which elements are specified in what order and that is something the RFC Editor probably cannot cope with.
>> Authentication Method is a registry so that just needs Group name and Registry name after IANA.
>
> Ok, good.
>>
>> Some minor glitches.
>> I-D appears twice in the body of the I-D - perhaps document or memo.
>
> Ok.
>
>> objetives/objectives/
>
> Fixed.
>> end port number perhaps /must/MUST/
>
>> and YANG is very good at including such checks with a must ....
>> 'If AEAD is used .. where? this occurs in several places and I think that you need to specify the leaf where AEAD will be specified or implied.
>
> Ok we have changed it to:
>
> If Authenticated Encryption with Associated Data (AEAD) is used (leaf esp-algorithms/encryption/algorithm-type)
> this flag MUST be false."
>
>> And is it possible to make that a YANG 'must' statement - looking at the IKEv2 registries it is not obvious which are AEAD so that might be more complexity than it is worth.
>> 'only available on linux kernels' Um implementation detail, you may get asked to remove that altogether or at least to a Informative Appendix - I would leave it in for now.
>
> Ok.
>
>> 'import ietf-i2nsf-ikec' the reference needs to be to a RFC and if it is not yet an RFC then RFC XXXX <title> in both Appendix B and C
>
> Yes, we have changed that to:
>
> RFC XXXX: Software-Defined Networking
>                 (SDN)-based IPsec Flow Protection.
>
>> leaf-list pfs-groups could do with a reference - Transform Type 4?
>
> The leaf list is referring to type pfs-group and we have now
>
> typedef pfs-group {
>              type uint16;
>              description
>                  "DH groups for IKE and IPsec SA rekey.";
>              reference
>                  "IANA; Internet Key Exchange V2 (IKEv2) Parameters;
> 				Transform Atribute Types; Transform Type 4 -
>                  Diffie-Hellman Group Transform IDs.
> 				Section 3.3.2 in RFC 7296.";
>          }
>
>
>>
>> I am still working my way through the YANG so may have some more comments tomorrow.
>
> Ok, do not worry we will work in -12 with these comments so far to have a quick response. We can prepare a another version later with the rest of them.
>
> Thank you very much for your effort.
>>
>> Tom Petch
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>> We have realized that we missed to change this, even though we discussed it. We will change it right away in the following way (bold):
>>>
>>> case rfc822-address-string {
>>>       leaf rfc822-address-string {
>>>            type string;
>>>            description
>>>                "Specifies the identity as a
>>>                 fully-qualified RFC5322 email
>>>                 address string. An example is,
>>>                 jsmith@example.com. The string
>>>                 MUST NOT contain any
>>>                 terminators e.g., NULL, CR,
>>>                 etc.).";
>>>             reference
>>>                    "RFC 5322.";
>>>       }
>>> }
>>>
>>> Btw, we already used in the past “case rfc822-address-string” and “leaf rfc822-address-string” since this is coming from IKEv2 standard. Do you think we should change that name as well?
>>>
>>>
>>>>
>>>> YANG module references IANA Protocol Numbers which is not in the I-D references
>>>
>>> We have included the following reference:
>>>
>>> [IANA-Protocols-Number]
>>>                Internet Assigned Numbers Authority (IANA), "Protocol
>>>                Numbers", January 2020.
>>>
>>>
>>>>
>>>> s.2 boiler plate is out of date
>>>
>>> What we see is the I-D has the second choice stated in https://www.ietf.org/standards/ids/guidelines/
>>>
>>> This Internet-Draft is submitted in full conformance with the
>>>     provisions of BCP 78 and BCP 79.
>>>
>>>     Internet-Drafts are working documents of the Internet Engineering
>>>     Task Force (IETF).  Note that other groups may also distribute
>>>     working documents as Internet-Drafts.  The list of current Internet-
>>>     Drafts is at https://datatracker.ietf.org/drafts/current/.
>>>
>>>     Internet-Drafts are draft documents valid for a maximum of six months
>>>     and may be updated, replaced, or obsoleted by other documents at any
>>>     time.  It is inappropriate to use Internet-Drafts as reference
>>>     material or to cite them other than as "work in progress."
>>>
>>> Could you refer what is out of date?
>>>
>>>>
>>>> XXXX is standing in for more than one RFC
>>>
>>> Yes, XXXX has been used because we do not know the future number assigned to our I-D.
>>>
>>> Also we realized we also included this to refer to crypto-types I-D but this has been solved now in a new version -12 that we are preparing to include your comments. We noticed we can replace the type of rw cert-data?, ca-data*, crl-data? for binary without any problem.
>>>
>>> |           |     +--rw cert-data?        binary
>>> |           +--rw private-key?            binary
>>> |           +--rw ca-data*                binary
>>> |           +--rw crl-data?               binary
>>>
>>>>
>>>> but the show stopper that makes a proper review of this too costly is the references.  Those to IANA of which there are several I want to pursue.  The I-D reference is to IKEv2 parameters. Sadly, this is a three tier structure and noone agrees on what to call the third tier so I will call it tier3 here.  Top level is Group, as per RFC8126, second level is Registry.  The I-D reference is to the Group only which is fine if the actual reference then specifies the Registry and Tier3 but they never do, usually just Tier3 e.g. Transform Type 3 which makes for a lot of work for the reader, too much for this one.  You have to go hunting in all the second level Registry until you can find a match for the Tier3 identifier. And there are no URL.  If you want an example that I find easy to use, go look at RFC8407 (as usual).
>>>
>>> You’re right. Could you point the exact part at RFC 8407 with that example? We would really appreciate it.
>>>
>>> On the other hand, would it be enough to include the URL for Transform Type 3 https://www.iana.org/assignments/ikev2-parameters/ikev2-parameters.xhtml#ikev2-parameters-7 ?
>>>
>>> (Same for Transform Type 1, Transform Type 4)
>>>
>>>>
>>>> The reference for import of i2nsf-ikec gives a YANG module name; this needs to be the name of the RFC to be
>>>
>>> Fixed.
>>>
>>> import ietf-i2nsf-ikec {
>>>              prefix nsfikec;
>>>              reference
>>>                  "RFC XXXX: Software-Defined Networking
>>>                 (SDN)-based IPsec Flow Protection.";
>>> }
>>>
>>> We still use XXXX because we do not know the number assigned to the RFC to be.
>>>
>>>>
>>>> The example IPv6 address in the YANG module has :0:0: which is usually just ::
>>>
>>> Fixed.
>>>
>>> If you have any further comments, please let us know so we can include them in -12
>>>
>>> Best Regards.
>>>>
>>>> And I have some way to go still.
>>>>
>>>> Tom Petch
>>>>
>>>> On 22/10/2020 18:39, Rafa Marin-Lopez wrote:
>>>>> Dear all:
>>>>>
>>>>> After receiving a suggestion to make things clearer in the feature ikeless-notification description, we have just uploaded a new version -11 with a minor change to add the following text:
>>>>>
>>>>> feature ikeless-notification {
>>>>>              description
>>>>>                  "This feature indicates that the server supports
>>>>>                  generating notifications in the ikeless module.
>>>>>
>>>>>                  To ensure broader applicability of this module,
>>>>>                  the notifications are marked as a feature.
>>>>>                  For the implementation of ikeless case,
>>>>>                  the NSF is expected to implement this
>>>>>                  feature.";
>>>>>          }
>>>>>
>>>>> Best Regards.
>>>>>
>>>>>> Inicio del mensaje reenviado:
>>>>>>
>>>>>> De: internet-drafts@ietf.org
>>>>>> Asunto: New Version Notification for draft-ietf-i2nsf-sdn-ipsec-flow-protection-11.txt
>>>>>> Fecha: 22 de octubre de 2020, 15:32:50 CEST
>>>>>> Para: "Fernando Pereniguez-Garcia" <fernando.pereniguez@cud.upct.es>, "Rafael Lopez" <rafa@um.es>, "Gabriel Lopez-Millan" <gabilm@um.es>, "Rafa Marin-Lopez" <rafa@um.es>
>>>>>>
>>>>>>
>>>>>> A new version of I-D, draft-ietf-i2nsf-sdn-ipsec-flow-protection-11.txt
>>>>>> has been successfully submitted by Rafa Marin-Lopez and posted to the
>>>>>> IETF repository.
>>>>>>
>>>>>> Name:		draft-ietf-i2nsf-sdn-ipsec-flow-protection
>>>>>> Revision:	11
>>>>>> Title:		Software-Defined Networking (SDN)-based IPsec Flow Protection
>>>>>> Document date:	2020-10-22
>>>>>> Group:		i2nsf
>>>>>> Pages:		92
>>>>>> URL:            https://www.ietf.org/archive/id/draft-ietf-i2nsf-sdn-ipsec-flow-protection-11.txt
>>>>>> Status:         https://datatracker.ietf.org/doc/draft-ietf-i2nsf-sdn-ipsec-flow-protection/
>>>>>> Htmlized:       https://datatracker.ietf.org/doc/html/draft-ietf-i2nsf-sdn-ipsec-flow-protection
>>>>>> Htmlized:       https://tools.ietf.org/html/draft-ietf-i2nsf-sdn-ipsec-flow-protection-11
>>>>>> Diff:           https://www.ietf.org/rfcdiff?url2=draft-ietf-i2nsf-sdn-ipsec-flow-protection-11
>>>>>>
>>>>>> Abstract:
>>>>>>    This document describes how to provide IPsec-based flow protection
>>>>>>    (integrity and confidentiality) by means of an Interface to Network
>>>>>>    Security Function (I2NSF) controller.  It considers two main well-
>>>>>>    known scenarios in IPsec: (i) gateway-to-gateway and (ii) host-to-
>>>>>>    host.  The service described in this document allows the
>>>>>>    configuration and monitoring of IPsec Security Associations (SAs)
>>>>>>    from a I2NSF Controller to one or several flow-based Network Security
>>>>>>    Functions (NSFs) that rely on IPsec to protect data traffic.
>>>>>>
>>>>>>    The document focuses on the I2NSF NSF-facing interface by providing
>>>>>>    YANG data models for configuring the IPsec databases (SPD, SAD, PAD)
>>>>>>    and IKEv2.  This allows IPsec SA establishment with minimal
>>>>>>    intervention by the network administrator.  It does not define any
>>>>>>    new protocol.
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> Please note that it may take a couple of minutes from the time of submission
>>>>>> until the htmlized version and diff are available at tools.ietf.org.
>>>>>>
>>>>>> The IETF Secretariat
>>>>>>
>>>>>>
>>>>>
>>>>> -------------------------------------------------------
>>>>> 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
>>>>> -------------------------------------------------------
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>
>>> -------------------------------------------------------
>>> 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
>>> -------------------------------------------------------
>>>
>>>
>>>
>>>
>>>
>
> -------------------------------------------------------
> 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
> -------------------------------------------------------
>
>
>
>
>


From nobody Thu Oct 29 11:47:07 2020
Return-Path: <rdd@cert.org>
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 591DB3A09F5; Thu, 29 Oct 2020 11:47:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level: 
X-Spam-Status: No, score=-2.099 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, 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 (1024-bit key) header.d=cert.org
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 E7WDpGtjVYmH; Thu, 29 Oct 2020 11:46:57 -0700 (PDT)
Received: from taper.sei.cmu.edu (taper.sei.cmu.edu [147.72.252.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 419CB3A09F4; Thu, 29 Oct 2020 11:46:56 -0700 (PDT)
Received: from delp.sei.cmu.edu (delp.sei.cmu.edu [10.64.21.31]) by taper.sei.cmu.edu (8.14.7/8.14.7) with ESMTP id 09TIkiCu032534; Thu, 29 Oct 2020 14:46:44 -0400
DKIM-Filter: OpenDKIM Filter v2.11.0 taper.sei.cmu.edu 09TIkiCu032534
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cert.org; s=yc2bmwvrj62m; t=1603997204; bh=1bSk1gDBGucH7+6j7rRAWfbmLCWFVi9H4ZUEszMCeOw=; h=From:To:CC:Subject:Date:References:In-Reply-To:From; b=ncZkY+PV+Q2gWWQtlPMPxsF9C8kxOsJKnA9iScB4UWvGkHuh4nmgbec7DSfFVqLbE vxzJG5VHN0KyQ/5M53y5Q+vvj6wCIb1OQd1rzsh5BJ38hYFArSAP0/icHuyx+OXcyB vC7BDF8LJEkmjnpWR4mjSxbsfP0dN/AduCLIrFzs=
Received: from MORRIS.ad.sei.cmu.edu (morris.ad.sei.cmu.edu [147.72.252.46]) by delp.sei.cmu.edu (8.14.7/8.14.7) with ESMTP id 09TIkhna022114; Thu, 29 Oct 2020 14:46:43 -0400
Received: from MORRIS.ad.sei.cmu.edu (147.72.252.46) by MORRIS.ad.sei.cmu.edu (147.72.252.46) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2106.2; Thu, 29 Oct 2020 14:46:43 -0400
Received: from MORRIS.ad.sei.cmu.edu ([fe80::555b:9498:552e:d1bb]) by MORRIS.ad.sei.cmu.edu ([fe80::555b:9498:552e:d1bb%13]) with mapi id 15.01.2106.002; Thu, 29 Oct 2020 14:46:43 -0400
From: Roman Danyliw <rdd@cert.org>
To: tom petch <daedulus@btconnect.com>, Rafa Marin-Lopez <rafa@um.es>
CC: "i2nsf@ietf.org" <i2nsf@ietf.org>, Fernando Pereniguez-Garcia <fernando.pereniguez@cud.upct.es>, Gabriel Lopez <gabilm@um.es>, "ynir.ietf@gmail.com" <ynir.ietf@gmail.com>, "last-call@ietf.org" <last-call@ietf.org>
Thread-Topic: [Last-Call] New Version Notification for draft-ietf-i2nsf-sdn-ipsec-flow-protection-11.txt
Thread-Index: AQHWreX0c88acJXFBk2yYgVjsJF2bKmvCuOA///cU0A=
Date: Thu, 29 Oct 2020 18:46:42 +0000
Message-ID: <059aaae84a354411ad1023afa2a837ba@cert.org>
References: <160337357077.29083.9236626834026808055@ietfa.amsl.com> <EE5AB669-73BB-4517-A6F4-23B7807FB36E@um.es> <5F9815D1.9010303@btconnect.com> <DDE550B1-9A9E-4954-B6F9-C0A33ECE1275@um.es> <5F99B221.3040504@btconnect.com> <56155C91-BFE8-4BA9-A55C-46B12E59CD94@um.es> <5F9AEFD3.90903@btconnect.com>
In-Reply-To: <5F9AEFD3.90903@btconnect.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.64.202.126]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2nsf/AYLjHQq1JNk-BCTQDt7fu_LqEJQ>
Subject: Re: [I2nsf] [Last-Call] New Version Notification for draft-ietf-i2nsf-sdn-ipsec-flow-protection-11.txt
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: Thu, 29 Oct 2020 18:47:00 -0000

SGkgVG9tIQ0KDQo+IC0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQo+IEZyb206IGxhc3QtY2Fs
bCA8bGFzdC1jYWxsLWJvdW5jZXNAaWV0Zi5vcmc+IE9uIEJlaGFsZiBPZiB0b20gcGV0Y2gNCj4g
U2VudDogVGh1cnNkYXksIE9jdG9iZXIgMjksIDIwMjAgMTI6MzggUE0NCj4gVG86IFJhZmEgTWFy
aW4tTG9wZXogPHJhZmFAdW0uZXM+DQo+IENjOiBpMm5zZkBpZXRmLm9yZzsgRmVybmFuZG8gUGVy
ZW5pZ3Vlei1HYXJjaWENCj4gPGZlcm5hbmRvLnBlcmVuaWd1ZXpAY3VkLnVwY3QuZXM+OyBHYWJy
aWVsIExvcGV6IDxnYWJpbG1AdW0uZXM+Ow0KPiB5bmlyLmlldGZAZ21haWwuY29tOyBsYXN0LWNh
bGxAaWV0Zi5vcmcNCj4gU3ViamVjdDogUmU6IFtMYXN0LUNhbGxdIE5ldyBWZXJzaW9uIE5vdGlm
aWNhdGlvbiBmb3IgZHJhZnQtaWV0Zi1pMm5zZi1zZG4taXBzZWMtDQo+IGZsb3ctcHJvdGVjdGlv
bi0xMS50eHQNCj4gDQo+IFRvcCBwb3N0aW5nIGEgbmV3LCByZWxhdGVkIGlzc3VlIHRoYXQgbWF5
IG5lZWQgU2VjdXJpdHkgQUQgb3IgV0cgQ2hhaXIgdG8gYWN0DQo+IG9uLg0KPiANCj4gSXQgc2Vl
bXMgdG8gbWUgdGhhdCB0aGUgSUFOQSBlbnRyaWVzIGZvciBJS0V2MiBhcmUgaW5jb21wbGV0ZS4g
IFJGQzgyNDcgZG9lcyBhDQo+IGZpbmUgam9iIG9mIHNwZWNpZnlpbmcgYWxnb3JpdGhtcyBhbmQg
YWRkaW5nIGluZm9ybWF0aW9uIHN1Y2ggYXMgc3RhdHVzDQo+IChNVVNUL1NIT1VMRCspLCBJb1Qs
IEFFQUQgYW5kIHNvIG9uLCBpbmZvcm1hdGlvbiB3aGljaCBpcyBub3QgcHJlc2VudCBvbg0KPiBJ
QU5BLiAgVGhlIHBvbGljeSBmb3IsIGUuZy4gVHJhbnNmb3JtIFR5cGUgMSwgaXMgZXhwZXJ0IHJl
dmlldyBhbmQgZW50cmllcyBoYXZlDQo+IGJlZW4gYWRkZWQgdmlhIGRyYWZ0LXNteXNsb3YtZXNw
LWdvbnQgYnV0IHRoZSBJQU5BIGVudHJpZXMgbGFjayB0aGlzDQo+IGluZm9ybWF0aW9uIGFuZCwg
bG9va2luZyBhdCB0aGUgSS1ELCBJIHNlZSBubyBzdWNoIGluZm9ybWF0aW9uIChub3IgaXMgdGhl
cmUgYW55DQo+IHJlYXNvbiBmb3IgaXQgdG8gYmUgdGhlcmUpLiAgWWV0IGRyYWZ0LWlldGYtaTJu
c2Ytc2RuLi4uIG5lZWRzIHRoaXMgaW5mb3JtYXRpb24gYXMNCj4gcmVmZXJlbmNlcyBpbiB0aGUg
WUFORyBtb2R1bGUgc2hvdy4NCj4gDQo+IEl0IHNlZW1zIHRvIG1lIHRoYXQgdGhpcyBpcyBhIHNp
bWlsYXIgc2l0dWF0aW9uIHRvIHRoYXQgd2hpY2ggdGhlIFRMUyBXRyBmb3VuZA0KPiBpdHNlbGYg
aW4gYW5kIHdoaWNoIGxlZCB0byBhIHJldmlzaW9uIG9mIHRoZSBUTFMgSUFOQSBlbnRyaWVzIHRv
IHByb3ZpZGUgd2hhdCB3YXMNCj4gbmVlZGVkIHZpYSBhZGRpdGlvbmFsIGNvbHVtbnMuDQoNClBs
ZWFzZSBoZWxwIG1lIHVuZGVyc3RhbmQuICBJbiBwYXJ0aWN1bGFyLCBJJ20gbm90IGZvbGxvd2lu
ZyB3aHkgdGhpcyBkb2N1bWVudCBzaG91bGQgbW9kaWZ5IElLRSBJQU5BIHJlZ2lzdHJpZXMuICBJ
biBteSB2aWV3LCB0aGlzIGRvY3VtZW50IGlzIHByb3ZpZGVzIGEgZGF0YSBtb2RlbCB0byBlbmNv
ZGUgYW4gIklLRXYyIGNvbmZpZ3VyYXRpb24iIG9mIHNvcnRzLiAgQ2VydGFpbmx5LCB0aGVyZSBh
cmUgdmFsaWQvaW52YWxpZC9pbmNvbXBsZXRlL25vdCByZWNvbW1lbmRlZCB3YXlzIHRvIHByb3Zp
ZGUgYSBjb25maWd1cmF0aW9uIHdpdGggdGhpcyBkYXRhIG1vZGVsIGlmIG9uZSByZWxpZWQgc29s
ZWx5IG9uIHRoZSBwb2ludGVycyB0byB0aGUgSUFOQSByZWdpc3RyaWVzIGZyb20gdGhlIFlBTkcg
bW9kdWxlIGRlZmluaXRpb24uICBIb3dldmVyLCBhcyB5b3Ugbm90ZWQsIFJGQzgyNDcgYWxyZWFk
eSBwcm92aWRlcyBndWlkYW5jZSBvbiBzcGVjaWZ5aW5nIGEgY29uZmlndXJhdGlvbiAoYWxiZWl0
IHRoaXMgZ3VpZGFuY2UgaXNuJ3QgZnVsbHkgZW5jb2RlZCBpbiB0aGUgcmVnaXN0cmllcykuICBG
dXJ0aGVybW9yZSwgdGhpcyBkb2N1bWVudCBzdGF0ZXM6DQoNClNlY3Rpb24gOC4xIA0KICAgbyAg
SUtFdjIgY29uZmlndXJhdGlvbnMgc2hvdWxkIGFkaGVyZSB0byB0aGUgcmVjb21tZW5kYXRpb25z
IGluDQogICAgICBbUkZDODI0N10uDQoNCnNvIHRoZXJlIGlzIGd1aWRhbmNlIG9uIHByb2R1Y2lu
ZyBhIGNvbmZpZ3VyYXRpb24uICBXaGF0IGlzIG1pc3Npbmc/DQoNCj4gSSB0aGluayB0aGF0IHRo
ZSBJQU5BIHBhZ2VzIGZvciBJS0V2MiBuZWVkIHJldmlzaW5nIHNvIHRoYXQgdGhhdCBhZGRpdGlv
bmFsDQo+IGluZm9ybWF0aW9uIHRoYXQgUkZDODI0NyBwcm92aWRlcyBpcyByZXF1aXJlZCBhcyBh
ZGRpdGlvbmFsIGNvbHVtbnMgaW4gdGhlDQo+IElBTkEgZW50cmllcyBhdCBsZWFzdCBmb3IgVHlw
ZSAxLCBUeXBlIDIsIFR5cGUgMywgVHlwZSA0IGFuZCBBdXRoZW50aWNhdGlvbg0KPiBNZXRob2Qu
DQoNCldoaWxlIHRoaW5ncyBjb3VsZCBiZSBjbGVhcmVyLCBJJ20gdW5zdXJlIG9mIHdoeSBfdGhp
cyBZQU5HIGRvY3VtZW50XyBzaG91bGQgZG8gYSByZWdpc3RyeSByZWVuZ2luZWVyaW5nLiAgRGlk
IHlvdSBtZWFuIGl0IHNob3VsZCBiZSBkb25lIGluIGdlbmVyYWw/DQoNClJlZ2FyZHMsDQpSb21h
bg0KDQo+IFRvbSBQZXRjaA0KPiANCj4gT24gMjkvMTAvMjAyMCAxMToyMywgUmFmYSBNYXJpbi1M
b3BleiB3cm90ZToNCj4gPiBIaSBUb206DQo+ID4NCj4gPj4gRWwgMjggb2N0IDIwMjAsIGEgbGFz
IDE5OjAyLCB0b20gcGV0Y2ggPGRhZWR1bHVzQGJ0Y29ubmVjdC5jb20+IGVzY3JpYmnDszoNCj4g
Pj4NCj4gPj4gT24gMjgvMTAvMjAyMCAxMDo0MiwgUmFmYSBNYXJpbi1Mb3BleiB3cm90ZToNCj4g
Pj4+IEhpIFRvbToNCj4gPj4+DQo+ID4+PiBUaGFuayB5b3UgdmVyeSBtdWNoIGZvciB5b3VyIGlu
c2lnaHQuIEl0IGlzIHZlcnkgaGVscGZ1bC4gUGxlYXNlIHNlZSBvdXINCj4gY29tbWVudHMvcXVl
c3Rpb25zIGlubGluZS4NCj4gPj4+DQo+ID4+Pj4gRWwgMjcgb2N0IDIwMjAsIGEgbGFzIDEzOjQy
LCB0b20gcGV0Y2ggPGRhZWR1bHVzQGJ0Y29ubmVjdC5jb20+DQo+IGVzY3JpYmnDszoNCj4gPj4+
Pg0KPiA+Pj4+IEkgdGhpbmsgdGhhdCB0aGUgSUVTRyB3aWxsIGZpbmQgYSBudW1iZXIgb2YgcHJv
YmxlbXMgd2l0aCB0aGlzIEktRC4NCj4gPj4+Pg0KPiA+Pj4+IFlBTkcgbW9kdWxlIHJlZmVyZW5j
ZXMgUkZDODIyIHdoaWNoIGlzIHNldmVyYWwgeWVhcnMgb3V0IG9mIGRhdGUNCj4gPj4NCj4gPj4g
UmFmYQ0KPiA+Pg0KPiA+PiBPbiBib2lsZXIgcGxhdGUsIEkgbWVhbiB0aGUgcmVmZXJlbmNlIHRv
IFJGQzIxMTkgd2hpY2ggbm93IG11c3QgdXNlIHRoZQ0KPiBsYW5ndWFnZSBmcm9tIFJGQzgxNzQg
aW4gdGhlIGJvZHkgb2YgdGhlIEktRDsgc29ycnkgZm9yIHRoZSBjb25mdXNpb24uDQo+ID4NCj4g
PiBBaCBvay4gSSBndWVzcyB5b3UgYXJlIHJlZmVycmluZyB0byBjaGFuZ2UgdGhhdCBwYXJhZ3Jh
cGggd2l0aCB0aGlzOg0KPiA+DQo+ID4NCj4gPiBUaGUga2V5IHdvcmRzICJNVVNUIiwgIk1VU1Qg
Tk9UIiwgIlJFUVVJUkVEIiwgIlNIQUxMIiwgIlNIQUxMIE5PVCIsDQo+ID4gIlNIT1VMRCIsICJT
SE9VTEQgTk9UIiwgIlJFQ09NTUVOREVEIiwgIk5PVCBSRUNPTU1FTkRFRCIsDQo+ICJNQVkiLCBh
bmQNCj4gPiAiT1BUSU9OQUwiIGluIHRoaXMgZG9jdW1lbnQgYXJlIHRvIGJlIGludGVycHJldGVk
IGFzIGRlc2NyaWJlZCBpbiBCQ1ANCj4gPiAxNCBSRkMyMTE5IFJGQzgxNzQgd2hlbiwgYW5kIG9u
bHkgd2hlbiwgdGhleSBhcHBlYXIgaW4gYWxsIGNhcGl0YWxzLA0KPiA+IGFzIHNob3duIGhlcmUu
DQo+ID4NCj4gPj4NCj4gPj4gT24gWFhYWCwgeW91IGhhdmUgWFhYWCBzdGFuZGluZyBpbiBmb3Ig
bW9yZSB0aGFuIG9uZSBSRkMtdG8tYmUgd2hpY2gNCj4gY29uZnVzZXMuICBUaGUgY29udmVudGlv
biBpcyB0byB1c2UgWFhYWCBmb3IgdGhpcyBJLUQgYW5kIHRoZW4gQUFBQSBCQkJCIGV0Yw0KPiBm
b3IgYW55IG90aGVycyBzdWNoIGFzIHRoZSBuZXRjb25mIEktRCBpbiB0aGlzIGluc3RhbmNlLg0K
PiA+DQo+ID4gQWggb2suIEluIGFueSBjYXNlLCB3ZSBoYXZlIG5vdyBvbmx5IFhYWFggZm9yIG91
ciBSRkMtdG8tYmUgc28gcHJvYmxlbQ0KPiBmaXhlZC4NCj4gPj4NCj4gPj4gVHdvIGJpZyBpc3N1
ZXMsIGZvciBtZSAocGVyaGFwcyBub3QgZm9yIG90aGVycykuICBUaGUgY29udmVudGlvbiB3aXRo
IFlBTkcNCj4gaXMgZm9yIGVhY2ggc3VjY2Vzc2l2ZSBsaW5lIHRvIGJlIGluZGVudGVkIHR3byBj
aGFyYWN0ZXJzLCB5b3UgaGF2ZSBmb3VyLCB3aGljaA0KPiBjcmVhdGVzIGEgbG90IG9mIHdoaXRl
IHNwYWNlIGFuZCBwdXNoZXMgdGhlIHRleHQgdG8gdGhlIHJpZ2h0IGhhbmQgbWFyZ2luLiAgSQ0K
PiB0aGluayB0aGF0IHR3byBjaGFyYWN0ZXJzIGlzIHRoZSBkZWZhdWx0IHdoZW4geW91IHVzZSBw
eWFuZyB0byBmb3JtYXQgYSBZQU5HDQo+IG1vZHVsZS4NCj4gPg0KPiA+IFdlIGNhbiB0cnkgdG8g
cmVkdWNlIGl0IHRvIHR3byBjaGFyYWN0ZXJzLg0KPiA+DQo+ID4+DQo+ID4+IEFuZCByZWZlcmVu
Y2VzLiAgSSBoYXZlIGhhZCB0byB3b3JrIGhhcmRlciB0aGFuIEkgd2FudCB0byB0byBtYWtlDQo+
ID4+IHNlbnNlIG9mIHRoZSBJQU5BIHJlZmVyZW5jZXMuICBJIHRoaW5rIHlvdSBzaG91bGQgaGF2
ZSBmaXZlIHNlcGFyYXRlDQo+ID4+IHJlZmVyZW5jZXMgaW4gdGhlIEktRCBmb3IgSUFOQSBmb3Ig
VHJhbnNmb3JtIFR5cGUgMSBUcmFuc2Zvcm0gVHlwZSAzDQo+ID4+IFRyYW5zZm9ybSBUeXBlIDQg
QXV0aGVudGljYXRpb24gTWV0aG9kIFByb3RvY29sIE51bWJlcnMgYW5kIGVhY2gNCj4gPj4gcmVm
ZXJlbmNlIGluIHRoZSBJLUQgc2hvdWxkIGhhdmUgYSBVUkwgcG9pbnRpbmcgdG8gdGhlIHNwZWNp
ZmljIHNlY3Rpb24gb2YNCj4gSUFOQSB3ZWIgc2l0ZS4NCj4gPg0KPiA+IE9rLCBnb29kLiBUaGlz
IGZvbGxvd3Mgd2hhdCB3ZSB0aG91Z2h0Lg0KPiA+DQo+ID4+IEluIHRoZSBZQU5HLCBpdCBpcyBo
YXJkZXIgdG8ga25vdyB3aGF0IHRvIGRvLiAgVGhvc2UgZmlyc3QgdGhyZWUgcmVmZXJlbmNlcw0K
PiBhcmUgaW4gdGhlIHRoaXJkIHRpZXIgaS5lLg0KPiA+PiBHcm91cCAtIEludGVybmV0IEtleSBF
eGNoYW5nZSBWMiAoSUtFdjIpIFBhcmFtZXRlcnMgUmVnaXN0cnkNCj4gPj4gLVRyYW5zZm9ybSBB
dHRyaWJ1dGUgVHlwZXMgYW5kIHRoZW4gVHlwZSAxLCAzLCA0IGFzIHRoZSB0aGlyZCB0aWVyIGFz
DQo+ID4+IEkgYW0gY2FsbGluZyBpdCBhbmQgSSB0aGluayB0aGF0IGV2ZXJ5IHJlZmVyZW5jZSBp
biB0aGUgWUFORyBzaG91bGQNCj4gPj4gZ2l2ZSBtZSBhbGwgdGhyZWUgdGllcnMgYWZ0ZXIgSUFO
QSBpbiB0aGF0IG9yZGVyIHBlcmhhcHMgSUFOQTsgSUtFdjINCj4gPj4gUGFyYW1ldGVyczsgVHJh
bnNmb3JtIEF0cmlidXRlIFR5cGVzOyBUcmFuc2Zvcm0gVHlwZSAxDQo+ID4NCj4gPiBHcmVhdC4g
V2UgYWxzbyBjb25zaWRlcmVkIHRoaXMgYXMgYSBwb3NzaWJsZSBzb2x1dGlvbiBhZnRlciBzZW5k
aW5nIG91ciBlLW1haWwuDQo+IExldOKAmXMgZG8gaXQuDQo+ID4NCj4gPj4gSWYgdGhlIHN5bnRh
eCBuZWVkcyB0d2Vla2luZywgdGhlbiB0aGUgUkZDIEVkaXRvciB3aWxsIGRvIGEgZ29vZCBqb2Ig
b2YgdGhhdA0KPiBidXQgYXQgcHJlc2VudCB0aGUgcmVmZXJlbmNlcyBhcmUgaW5jb25zaXN0ZW50
IGluIHdoaWNoIGVsZW1lbnRzIGFyZSBzcGVjaWZpZWQNCj4gaW4gd2hhdCBvcmRlciBhbmQgdGhh
dCBpcyBzb21ldGhpbmcgdGhlIFJGQyBFZGl0b3IgcHJvYmFibHkgY2Fubm90IGNvcGUgd2l0aC4N
Cj4gPj4gQXV0aGVudGljYXRpb24gTWV0aG9kIGlzIGEgcmVnaXN0cnkgc28gdGhhdCBqdXN0IG5l
ZWRzIEdyb3VwIG5hbWUgYW5kDQo+IFJlZ2lzdHJ5IG5hbWUgYWZ0ZXIgSUFOQS4NCj4gPg0KPiA+
IE9rLCBnb29kLg0KPiA+Pg0KPiA+PiBTb21lIG1pbm9yIGdsaXRjaGVzLg0KPiA+PiBJLUQgYXBw
ZWFycyB0d2ljZSBpbiB0aGUgYm9keSBvZiB0aGUgSS1EIC0gcGVyaGFwcyBkb2N1bWVudCBvciBt
ZW1vLg0KPiA+DQo+ID4gT2suDQo+ID4NCj4gPj4gb2JqZXRpdmVzL29iamVjdGl2ZXMvDQo+ID4N
Cj4gPiBGaXhlZC4NCj4gPj4gZW5kIHBvcnQgbnVtYmVyIHBlcmhhcHMgL211c3QvTVVTVC8NCj4g
Pg0KPiA+PiBhbmQgWUFORyBpcyB2ZXJ5IGdvb2QgYXQgaW5jbHVkaW5nIHN1Y2ggY2hlY2tzIHdp
dGggYSBtdXN0IC4uLi4NCj4gPj4gJ0lmIEFFQUQgaXMgdXNlZCAuLiB3aGVyZT8gdGhpcyBvY2N1
cnMgaW4gc2V2ZXJhbCBwbGFjZXMgYW5kIEkgdGhpbmsgdGhhdCB5b3UNCj4gbmVlZCB0byBzcGVj
aWZ5IHRoZSBsZWFmIHdoZXJlIEFFQUQgd2lsbCBiZSBzcGVjaWZpZWQgb3IgaW1wbGllZC4NCj4g
Pg0KPiA+IE9rIHdlIGhhdmUgY2hhbmdlZCBpdCB0bzoNCj4gPg0KPiA+IElmIEF1dGhlbnRpY2F0
ZWQgRW5jcnlwdGlvbiB3aXRoIEFzc29jaWF0ZWQgRGF0YSAoQUVBRCkgaXMgdXNlZCAobGVhZg0K
PiA+IGVzcC1hbGdvcml0aG1zL2VuY3J5cHRpb24vYWxnb3JpdGhtLXR5cGUpDQo+ID4gdGhpcyBm
bGFnIE1VU1QgYmUgZmFsc2UuIg0KPiA+DQo+ID4+IEFuZCBpcyBpdCBwb3NzaWJsZSB0byBtYWtl
IHRoYXQgYSBZQU5HICdtdXN0JyBzdGF0ZW1lbnQgLSBsb29raW5nIGF0IHRoZQ0KPiBJS0V2MiBy
ZWdpc3RyaWVzIGl0IGlzIG5vdCBvYnZpb3VzIHdoaWNoIGFyZSBBRUFEIHNvIHRoYXQgbWlnaHQg
YmUgbW9yZQ0KPiBjb21wbGV4aXR5IHRoYW4gaXQgaXMgd29ydGguDQo+ID4+ICdvbmx5IGF2YWls
YWJsZSBvbiBsaW51eCBrZXJuZWxzJyBVbSBpbXBsZW1lbnRhdGlvbiBkZXRhaWwsIHlvdSBtYXkg
Z2V0DQo+IGFza2VkIHRvIHJlbW92ZSB0aGF0IGFsdG9nZXRoZXIgb3IgYXQgbGVhc3QgdG8gYSBJ
bmZvcm1hdGl2ZSBBcHBlbmRpeCAtIEkgd291bGQNCj4gbGVhdmUgaXQgaW4gZm9yIG5vdy4NCj4g
Pg0KPiA+IE9rLg0KPiA+DQo+ID4+ICdpbXBvcnQgaWV0Zi1pMm5zZi1pa2VjJyB0aGUgcmVmZXJl
bmNlIG5lZWRzIHRvIGJlIHRvIGEgUkZDIGFuZCBpZiBpdA0KPiA+PiBpcyBub3QgeWV0IGFuIFJG
QyB0aGVuIFJGQyBYWFhYIDx0aXRsZT4gaW4gYm90aCBBcHBlbmRpeCBCIGFuZCBDDQo+ID4NCj4g
PiBZZXMsIHdlIGhhdmUgY2hhbmdlZCB0aGF0IHRvOg0KPiA+DQo+ID4gUkZDIFhYWFg6IFNvZnR3
YXJlLURlZmluZWQgTmV0d29ya2luZw0KPiA+ICAgICAgICAgICAgICAgICAoU0ROKS1iYXNlZCBJ
UHNlYyBGbG93IFByb3RlY3Rpb24uDQo+ID4NCj4gPj4gbGVhZi1saXN0IHBmcy1ncm91cHMgY291
bGQgZG8gd2l0aCBhIHJlZmVyZW5jZSAtIFRyYW5zZm9ybSBUeXBlIDQ/DQo+ID4NCj4gPiBUaGUg
bGVhZiBsaXN0IGlzIHJlZmVycmluZyB0byB0eXBlIHBmcy1ncm91cCBhbmQgd2UgaGF2ZSBub3cN
Cj4gPg0KPiA+IHR5cGVkZWYgcGZzLWdyb3VwIHsNCj4gPiAgICAgICAgICAgICAgdHlwZSB1aW50
MTY7DQo+ID4gICAgICAgICAgICAgIGRlc2NyaXB0aW9uDQo+ID4gICAgICAgICAgICAgICAgICAi
REggZ3JvdXBzIGZvciBJS0UgYW5kIElQc2VjIFNBIHJla2V5LiI7DQo+ID4gICAgICAgICAgICAg
IHJlZmVyZW5jZQ0KPiA+ICAgICAgICAgICAgICAgICAgIklBTkE7IEludGVybmV0IEtleSBFeGNo
YW5nZSBWMiAoSUtFdjIpIFBhcmFtZXRlcnM7DQo+ID4gCQkJCVRyYW5zZm9ybSBBdHJpYnV0ZSBU
eXBlczsgVHJhbnNmb3JtIFR5cGUgNCAtDQo+ID4gICAgICAgICAgICAgICAgICBEaWZmaWUtSGVs
bG1hbiBHcm91cCBUcmFuc2Zvcm0gSURzLg0KPiA+IAkJCQlTZWN0aW9uIDMuMy4yIGluIFJGQyA3
Mjk2LiI7DQo+ID4gICAgICAgICAgfQ0KPiA+DQo+ID4NCj4gPj4NCj4gPj4gSSBhbSBzdGlsbCB3
b3JraW5nIG15IHdheSB0aHJvdWdoIHRoZSBZQU5HIHNvIG1heSBoYXZlIHNvbWUgbW9yZQ0KPiBj
b21tZW50cyB0b21vcnJvdy4NCj4gPg0KPiA+IE9rLCBkbyBub3Qgd29ycnkgd2Ugd2lsbCB3b3Jr
IGluIC0xMiB3aXRoIHRoZXNlIGNvbW1lbnRzIHNvIGZhciB0byBoYXZlIGENCj4gcXVpY2sgcmVz
cG9uc2UuIFdlIGNhbiBwcmVwYXJlIGEgYW5vdGhlciB2ZXJzaW9uIGxhdGVyIHdpdGggdGhlIHJl
c3Qgb2YgdGhlbS4NCj4gPg0KPiA+IFRoYW5rIHlvdSB2ZXJ5IG11Y2ggZm9yIHlvdXIgZWZmb3J0
Lg0KPiA+Pg0KPiA+PiBUb20gUGV0Y2gNCj4gPj4NCj4gPj4NCj4gPj4NCj4gPj4NCj4gPj4NCj4g
Pj4NCj4gPj4NCj4gPj4NCj4gPj4NCj4gPj4NCj4gPj4NCj4gPj4NCj4gPj4NCj4gPj4NCj4gPj4+
IFdlIGhhdmUgcmVhbGl6ZWQgdGhhdCB3ZSBtaXNzZWQgdG8gY2hhbmdlIHRoaXMsIGV2ZW4gdGhv
dWdoIHdlIGRpc2N1c3NlZA0KPiBpdC4gV2Ugd2lsbCBjaGFuZ2UgaXQgcmlnaHQgYXdheSBpbiB0
aGUgZm9sbG93aW5nIHdheSAoYm9sZCk6DQo+ID4+Pg0KPiA+Pj4gY2FzZSByZmM4MjItYWRkcmVz
cy1zdHJpbmcgew0KPiA+Pj4gICAgICAgbGVhZiByZmM4MjItYWRkcmVzcy1zdHJpbmcgew0KPiA+
Pj4gICAgICAgICAgICB0eXBlIHN0cmluZzsNCj4gPj4+ICAgICAgICAgICAgZGVzY3JpcHRpb24N
Cj4gPj4+ICAgICAgICAgICAgICAgICJTcGVjaWZpZXMgdGhlIGlkZW50aXR5IGFzIGENCj4gPj4+
ICAgICAgICAgICAgICAgICBmdWxseS1xdWFsaWZpZWQgUkZDNTMyMiBlbWFpbA0KPiA+Pj4gICAg
ICAgICAgICAgICAgIGFkZHJlc3Mgc3RyaW5nLiBBbiBleGFtcGxlIGlzLA0KPiA+Pj4gICAgICAg
ICAgICAgICAgIGpzbWl0aEBleGFtcGxlLmNvbS4gVGhlIHN0cmluZw0KPiA+Pj4gICAgICAgICAg
ICAgICAgIE1VU1QgTk9UIGNvbnRhaW4gYW55DQo+ID4+PiAgICAgICAgICAgICAgICAgdGVybWlu
YXRvcnMgZS5nLiwgTlVMTCwgQ1IsDQo+ID4+PiAgICAgICAgICAgICAgICAgZXRjLikuIjsNCj4g
Pj4+ICAgICAgICAgICAgIHJlZmVyZW5jZQ0KPiA+Pj4gICAgICAgICAgICAgICAgICAgICJSRkMg
NTMyMi4iOw0KPiA+Pj4gICAgICAgfQ0KPiA+Pj4gfQ0KPiA+Pj4NCj4gPj4+IEJ0dywgd2UgYWxy
ZWFkeSB1c2VkIGluIHRoZSBwYXN0IOKAnGNhc2UgcmZjODIyLWFkZHJlc3Mtc3RyaW5n4oCdIGFu
ZCDigJxsZWFmDQo+IHJmYzgyMi1hZGRyZXNzLXN0cmluZ+KAnSBzaW5jZSB0aGlzIGlzIGNvbWlu
ZyBmcm9tIElLRXYyIHN0YW5kYXJkLiBEbyB5b3UgdGhpbmsNCj4gd2Ugc2hvdWxkIGNoYW5nZSB0
aGF0IG5hbWUgYXMgd2VsbD8NCj4gPj4+DQo+ID4+Pg0KPiA+Pj4+DQo+ID4+Pj4gWUFORyBtb2R1
bGUgcmVmZXJlbmNlcyBJQU5BIFByb3RvY29sIE51bWJlcnMgd2hpY2ggaXMgbm90IGluIHRoZQ0K
PiA+Pj4+IEktRCByZWZlcmVuY2VzDQo+ID4+Pg0KPiA+Pj4gV2UgaGF2ZSBpbmNsdWRlZCB0aGUg
Zm9sbG93aW5nIHJlZmVyZW5jZToNCj4gPj4+DQo+ID4+PiBbSUFOQS1Qcm90b2NvbHMtTnVtYmVy
XQ0KPiA+Pj4gICAgICAgICAgICAgICAgSW50ZXJuZXQgQXNzaWduZWQgTnVtYmVycyBBdXRob3Jp
dHkgKElBTkEpLCAiUHJvdG9jb2wNCj4gPj4+ICAgICAgICAgICAgICAgIE51bWJlcnMiLCBKYW51
YXJ5IDIwMjAuDQo+ID4+Pg0KPiA+Pj4NCj4gPj4+Pg0KPiA+Pj4+IHMuMiBib2lsZXIgcGxhdGUg
aXMgb3V0IG9mIGRhdGUNCj4gPj4+DQo+ID4+PiBXaGF0IHdlIHNlZSBpcyB0aGUgSS1EIGhhcyB0
aGUgc2Vjb25kIGNob2ljZSBzdGF0ZWQgaW4NCj4gPj4+IGh0dHBzOi8vd3d3LmlldGYub3JnL3N0
YW5kYXJkcy9pZHMvZ3VpZGVsaW5lcy8NCj4gPj4+DQo+ID4+PiBUaGlzIEludGVybmV0LURyYWZ0
IGlzIHN1Ym1pdHRlZCBpbiBmdWxsIGNvbmZvcm1hbmNlIHdpdGggdGhlDQo+ID4+PiAgICAgcHJv
dmlzaW9ucyBvZiBCQ1AgNzggYW5kIEJDUCA3OS4NCj4gPj4+DQo+ID4+PiAgICAgSW50ZXJuZXQt
RHJhZnRzIGFyZSB3b3JraW5nIGRvY3VtZW50cyBvZiB0aGUgSW50ZXJuZXQgRW5naW5lZXJpbmcN
Cj4gPj4+ICAgICBUYXNrIEZvcmNlIChJRVRGKS4gIE5vdGUgdGhhdCBvdGhlciBncm91cHMgbWF5
IGFsc28gZGlzdHJpYnV0ZQ0KPiA+Pj4gICAgIHdvcmtpbmcgZG9jdW1lbnRzIGFzIEludGVybmV0
LURyYWZ0cy4gIFRoZSBsaXN0IG9mIGN1cnJlbnQgSW50ZXJuZXQtDQo+ID4+PiAgICAgRHJhZnRz
IGlzIGF0IGh0dHBzOi8vZGF0YXRyYWNrZXIuaWV0Zi5vcmcvZHJhZnRzL2N1cnJlbnQvLg0KPiA+
Pj4NCj4gPj4+ICAgICBJbnRlcm5ldC1EcmFmdHMgYXJlIGRyYWZ0IGRvY3VtZW50cyB2YWxpZCBm
b3IgYSBtYXhpbXVtIG9mIHNpeCBtb250aHMNCj4gPj4+ICAgICBhbmQgbWF5IGJlIHVwZGF0ZWQs
IHJlcGxhY2VkLCBvciBvYnNvbGV0ZWQgYnkgb3RoZXIgZG9jdW1lbnRzIGF0IGFueQ0KPiA+Pj4g
ICAgIHRpbWUuICBJdCBpcyBpbmFwcHJvcHJpYXRlIHRvIHVzZSBJbnRlcm5ldC1EcmFmdHMgYXMg
cmVmZXJlbmNlDQo+ID4+PiAgICAgbWF0ZXJpYWwgb3IgdG8gY2l0ZSB0aGVtIG90aGVyIHRoYW4g
YXMgIndvcmsgaW4gcHJvZ3Jlc3MuIg0KPiA+Pj4NCj4gPj4+IENvdWxkIHlvdSByZWZlciB3aGF0
IGlzIG91dCBvZiBkYXRlPw0KPiA+Pj4NCj4gPj4+Pg0KPiA+Pj4+IFhYWFggaXMgc3RhbmRpbmcg
aW4gZm9yIG1vcmUgdGhhbiBvbmUgUkZDDQo+ID4+Pg0KPiA+Pj4gWWVzLCBYWFhYIGhhcyBiZWVu
IHVzZWQgYmVjYXVzZSB3ZSBkbyBub3Qga25vdyB0aGUgZnV0dXJlIG51bWJlcg0KPiBhc3NpZ25l
ZCB0byBvdXIgSS1ELg0KPiA+Pj4NCj4gPj4+IEFsc28gd2UgcmVhbGl6ZWQgd2UgYWxzbyBpbmNs
dWRlZCB0aGlzIHRvIHJlZmVyIHRvIGNyeXB0by10eXBlcyBJLUQgYnV0IHRoaXMNCj4gaGFzIGJl
ZW4gc29sdmVkIG5vdyBpbiBhIG5ldyB2ZXJzaW9uIC0xMiB0aGF0IHdlIGFyZSBwcmVwYXJpbmcg
dG8gaW5jbHVkZSB5b3VyDQo+IGNvbW1lbnRzLiBXZSBub3RpY2VkIHdlIGNhbiByZXBsYWNlIHRo
ZSB0eXBlIG9mIHJ3IGNlcnQtZGF0YT8sIGNhLWRhdGEqLCBjcmwtDQo+IGRhdGE/IGZvciBiaW5h
cnkgd2l0aG91dCBhbnkgcHJvYmxlbS4NCj4gPj4+DQo+ID4+PiB8ICAgICAgICAgICB8ICAgICAr
LS1ydyBjZXJ0LWRhdGE/ICAgICAgICBiaW5hcnkNCj4gPj4+IHwgICAgICAgICAgICstLXJ3IHBy
aXZhdGUta2V5PyAgICAgICAgICAgIGJpbmFyeQ0KPiA+Pj4gfCAgICAgICAgICAgKy0tcncgY2Et
ZGF0YSogICAgICAgICAgICAgICAgYmluYXJ5DQo+ID4+PiB8ICAgICAgICAgICArLS1ydyBjcmwt
ZGF0YT8gICAgICAgICAgICAgICBiaW5hcnkNCj4gPj4+DQo+ID4+Pj4NCj4gPj4+PiBidXQgdGhl
IHNob3cgc3RvcHBlciB0aGF0IG1ha2VzIGEgcHJvcGVyIHJldmlldyBvZiB0aGlzIHRvbyBjb3N0
bHkgaXMgdGhlDQo+IHJlZmVyZW5jZXMuICBUaG9zZSB0byBJQU5BIG9mIHdoaWNoIHRoZXJlIGFy
ZSBzZXZlcmFsIEkgd2FudCB0byBwdXJzdWUuICBUaGUgSS1EDQo+IHJlZmVyZW5jZSBpcyB0byBJ
S0V2MiBwYXJhbWV0ZXJzLiBTYWRseSwgdGhpcyBpcyBhIHRocmVlIHRpZXIgc3RydWN0dXJlIGFu
ZCBub29uZQ0KPiBhZ3JlZXMgb24gd2hhdCB0byBjYWxsIHRoZSB0aGlyZCB0aWVyIHNvIEkgd2ls
bCBjYWxsIGl0IHRpZXIzIGhlcmUuICBUb3AgbGV2ZWwgaXMNCj4gR3JvdXAsIGFzIHBlciBSRkM4
MTI2LCBzZWNvbmQgbGV2ZWwgaXMgUmVnaXN0cnkuICBUaGUgSS1EIHJlZmVyZW5jZSBpcyB0byB0
aGUNCj4gR3JvdXAgb25seSB3aGljaCBpcyBmaW5lIGlmIHRoZSBhY3R1YWwgcmVmZXJlbmNlIHRo
ZW4gc3BlY2lmaWVzIHRoZSBSZWdpc3RyeSBhbmQNCj4gVGllcjMgYnV0IHRoZXkgbmV2ZXIgZG8s
IHVzdWFsbHkganVzdCBUaWVyMyBlLmcuIFRyYW5zZm9ybSBUeXBlIDMgd2hpY2ggbWFrZXMNCj4g
Zm9yIGEgbG90IG9mIHdvcmsgZm9yIHRoZSByZWFkZXIsIHRvbyBtdWNoIGZvciB0aGlzIG9uZS4g
IFlvdSBoYXZlIHRvIGdvIGh1bnRpbmcNCj4gaW4gYWxsIHRoZSBzZWNvbmQgbGV2ZWwgUmVnaXN0
cnkgdW50aWwgeW91IGNhbiBmaW5kIGEgbWF0Y2ggZm9yIHRoZSBUaWVyMw0KPiBpZGVudGlmaWVy
LiBBbmQgdGhlcmUgYXJlIG5vIFVSTC4gIElmIHlvdSB3YW50IGFuIGV4YW1wbGUgdGhhdCBJIGZp
bmQgZWFzeSB0byB1c2UsDQo+IGdvIGxvb2sgYXQgUkZDODQwNyAoYXMgdXN1YWwpLg0KPiA+Pj4N
Cj4gPj4+IFlvdeKAmXJlIHJpZ2h0LiBDb3VsZCB5b3UgcG9pbnQgdGhlIGV4YWN0IHBhcnQgYXQg
UkZDIDg0MDcgd2l0aCB0aGF0DQo+IGV4YW1wbGU/IFdlIHdvdWxkIHJlYWxseSBhcHByZWNpYXRl
IGl0Lg0KPiA+Pj4NCj4gPj4+IE9uIHRoZSBvdGhlciBoYW5kLCB3b3VsZCBpdCBiZSBlbm91Z2gg
dG8gaW5jbHVkZSB0aGUgVVJMIGZvciBUcmFuc2Zvcm0NCj4gVHlwZSAzIGh0dHBzOi8vd3d3Lmlh
bmEub3JnL2Fzc2lnbm1lbnRzL2lrZXYyLXBhcmFtZXRlcnMvaWtldjItDQo+IHBhcmFtZXRlcnMu
eGh0bWwjaWtldjItcGFyYW1ldGVycy03ID8NCj4gPj4+DQo+ID4+PiAoU2FtZSBmb3IgVHJhbnNm
b3JtIFR5cGUgMSwgVHJhbnNmb3JtIFR5cGUgNCkNCj4gPj4+DQo+ID4+Pj4NCj4gPj4+PiBUaGUg
cmVmZXJlbmNlIGZvciBpbXBvcnQgb2YgaTJuc2YtaWtlYyBnaXZlcyBhIFlBTkcgbW9kdWxlIG5h
bWU7DQo+ID4+Pj4gdGhpcyBuZWVkcyB0byBiZSB0aGUgbmFtZSBvZiB0aGUgUkZDIHRvIGJlDQo+
ID4+Pg0KPiA+Pj4gRml4ZWQuDQo+ID4+Pg0KPiA+Pj4gaW1wb3J0IGlldGYtaTJuc2YtaWtlYyB7
DQo+ID4+PiAgICAgICAgICAgICAgcHJlZml4IG5zZmlrZWM7DQo+ID4+PiAgICAgICAgICAgICAg
cmVmZXJlbmNlDQo+ID4+PiAgICAgICAgICAgICAgICAgICJSRkMgWFhYWDogU29mdHdhcmUtRGVm
aW5lZCBOZXR3b3JraW5nDQo+ID4+PiAgICAgICAgICAgICAgICAgKFNETiktYmFzZWQgSVBzZWMg
RmxvdyBQcm90ZWN0aW9uLiI7IH0NCj4gPj4+DQo+ID4+PiBXZSBzdGlsbCB1c2UgWFhYWCBiZWNh
dXNlIHdlIGRvIG5vdCBrbm93IHRoZSBudW1iZXIgYXNzaWduZWQgdG8gdGhlIFJGQw0KPiB0byBi
ZS4NCj4gPj4+DQo+ID4+Pj4NCj4gPj4+PiBUaGUgZXhhbXBsZSBJUHY2IGFkZHJlc3MgaW4gdGhl
IFlBTkcgbW9kdWxlIGhhcyA6MDowOiB3aGljaCBpcyB1c3VhbGx5DQo+IGp1c3QgOjoNCj4gPj4+
DQo+ID4+PiBGaXhlZC4NCj4gPj4+DQo+ID4+PiBJZiB5b3UgaGF2ZSBhbnkgZnVydGhlciBjb21t
ZW50cywgcGxlYXNlIGxldCB1cyBrbm93IHNvIHdlIGNhbg0KPiA+Pj4gaW5jbHVkZSB0aGVtIGlu
IC0xMg0KPiA+Pj4NCj4gPj4+IEJlc3QgUmVnYXJkcy4NCj4gPj4+Pg0KPiA+Pj4+IEFuZCBJIGhh
dmUgc29tZSB3YXkgdG8gZ28gc3RpbGwuDQo+ID4+Pj4NCj4gPj4+PiBUb20gUGV0Y2gNCj4gPj4+
Pg0KPiA+Pj4+IE9uIDIyLzEwLzIwMjAgMTg6MzksIFJhZmEgTWFyaW4tTG9wZXogd3JvdGU6DQo+
ID4+Pj4+IERlYXIgYWxsOg0KPiA+Pj4+Pg0KPiA+Pj4+PiBBZnRlciByZWNlaXZpbmcgYSBzdWdn
ZXN0aW9uIHRvIG1ha2UgdGhpbmdzIGNsZWFyZXIgaW4gdGhlIGZlYXR1cmUgaWtlbGVzcy0NCj4g
bm90aWZpY2F0aW9uIGRlc2NyaXB0aW9uLCB3ZSBoYXZlIGp1c3QgdXBsb2FkZWQgYSBuZXcgdmVy
c2lvbiAtMTEgd2l0aCBhIG1pbm9yDQo+IGNoYW5nZSB0byBhZGQgdGhlIGZvbGxvd2luZyB0ZXh0
Og0KPiA+Pj4+Pg0KPiA+Pj4+PiBmZWF0dXJlIGlrZWxlc3Mtbm90aWZpY2F0aW9uIHsNCj4gPj4+
Pj4gICAgICAgICAgICAgIGRlc2NyaXB0aW9uDQo+ID4+Pj4+ICAgICAgICAgICAgICAgICAgIlRo
aXMgZmVhdHVyZSBpbmRpY2F0ZXMgdGhhdCB0aGUgc2VydmVyIHN1cHBvcnRzDQo+ID4+Pj4+ICAg
ICAgICAgICAgICAgICAgZ2VuZXJhdGluZyBub3RpZmljYXRpb25zIGluIHRoZSBpa2VsZXNzIG1v
ZHVsZS4NCj4gPj4+Pj4NCj4gPj4+Pj4gICAgICAgICAgICAgICAgICBUbyBlbnN1cmUgYnJvYWRl
ciBhcHBsaWNhYmlsaXR5IG9mIHRoaXMgbW9kdWxlLA0KPiA+Pj4+PiAgICAgICAgICAgICAgICAg
IHRoZSBub3RpZmljYXRpb25zIGFyZSBtYXJrZWQgYXMgYSBmZWF0dXJlLg0KPiA+Pj4+PiAgICAg
ICAgICAgICAgICAgIEZvciB0aGUgaW1wbGVtZW50YXRpb24gb2YgaWtlbGVzcyBjYXNlLA0KPiA+
Pj4+PiAgICAgICAgICAgICAgICAgIHRoZSBOU0YgaXMgZXhwZWN0ZWQgdG8gaW1wbGVtZW50IHRo
aXMNCj4gPj4+Pj4gICAgICAgICAgICAgICAgICBmZWF0dXJlLiI7DQo+ID4+Pj4+ICAgICAgICAg
IH0NCj4gPj4+Pj4NCj4gPj4+Pj4gQmVzdCBSZWdhcmRzLg0KPiA+Pj4+Pg0KPiA+Pj4+Pj4gSW5p
Y2lvIGRlbCBtZW5zYWplIHJlZW52aWFkbzoNCj4gPj4+Pj4+DQo+ID4+Pj4+PiBEZTogaW50ZXJu
ZXQtZHJhZnRzQGlldGYub3JnDQo+ID4+Pj4+PiBBc3VudG86IE5ldyBWZXJzaW9uIE5vdGlmaWNh
dGlvbiBmb3INCj4gPj4+Pj4+IGRyYWZ0LWlldGYtaTJuc2Ytc2RuLWlwc2VjLWZsb3ctcHJvdGVj
dGlvbi0xMS50eHQNCj4gPj4+Pj4+IEZlY2hhOiAyMiBkZSBvY3R1YnJlIGRlIDIwMjAsIDE1OjMy
OjUwIENFU1QNCj4gPj4+Pj4+IFBhcmE6ICJGZXJuYW5kbyBQZXJlbmlndWV6LUdhcmNpYSINCj4g
Pj4+Pj4+IDxmZXJuYW5kby5wZXJlbmlndWV6QGN1ZC51cGN0LmVzPiwgIlJhZmFlbCBMb3BleiIg
PHJhZmFAdW0uZXM+LA0KPiA+Pj4+Pj4gIkdhYnJpZWwgTG9wZXotTWlsbGFuIiA8Z2FiaWxtQHVt
LmVzPiwgIlJhZmEgTWFyaW4tTG9wZXoiDQo+ID4+Pj4+PiA8cmFmYUB1bS5lcz4NCj4gPj4+Pj4+
DQo+ID4+Pj4+Pg0KPiA+Pj4+Pj4gQSBuZXcgdmVyc2lvbiBvZiBJLUQsDQo+ID4+Pj4+PiBkcmFm
dC1pZXRmLWkybnNmLXNkbi1pcHNlYy1mbG93LXByb3RlY3Rpb24tMTEudHh0DQo+ID4+Pj4+PiBo
YXMgYmVlbiBzdWNjZXNzZnVsbHkgc3VibWl0dGVkIGJ5IFJhZmEgTWFyaW4tTG9wZXogYW5kIHBv
c3RlZCB0bw0KPiA+Pj4+Pj4gdGhlIElFVEYgcmVwb3NpdG9yeS4NCj4gPj4+Pj4+DQo+ID4+Pj4+
PiBOYW1lOgkJZHJhZnQtaWV0Zi1pMm5zZi1zZG4taXBzZWMtZmxvdy1wcm90ZWN0aW9uDQo+ID4+
Pj4+PiBSZXZpc2lvbjoJMTENCj4gPj4+Pj4+IFRpdGxlOgkJU29mdHdhcmUtRGVmaW5lZCBOZXR3
b3JraW5nIChTRE4pLWJhc2VkIElQc2VjIEZsb3cNCj4gUHJvdGVjdGlvbg0KPiA+Pj4+Pj4gRG9j
dW1lbnQgZGF0ZToJMjAyMC0xMC0yMg0KPiA+Pj4+Pj4gR3JvdXA6CQlpMm5zZg0KPiA+Pj4+Pj4g
UGFnZXM6CQk5Mg0KPiA+Pj4+Pj4gVVJMOiAgICAgICAgICAgIGh0dHBzOi8vd3d3LmlldGYub3Jn
L2FyY2hpdmUvaWQvZHJhZnQtaWV0Zi1pMm5zZi1zZG4taXBzZWMtDQo+IGZsb3ctcHJvdGVjdGlv
bi0xMS50eHQNCj4gPj4+Pj4+IFN0YXR1czogICAgICAgICBodHRwczovL2RhdGF0cmFja2VyLmll
dGYub3JnL2RvYy9kcmFmdC1pZXRmLWkybnNmLXNkbi1pcHNlYy0NCj4gZmxvdy1wcm90ZWN0aW9u
Lw0KPiA+Pj4+Pj4gSHRtbGl6ZWQ6ICAgICAgIGh0dHBzOi8vZGF0YXRyYWNrZXIuaWV0Zi5vcmcv
ZG9jL2h0bWwvZHJhZnQtaWV0Zi1pMm5zZi1zZG4tDQo+IGlwc2VjLWZsb3ctcHJvdGVjdGlvbg0K
PiA+Pj4+Pj4gSHRtbGl6ZWQ6ICAgICAgIGh0dHBzOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9kcmFm
dC1pZXRmLWkybnNmLXNkbi1pcHNlYy1mbG93LQ0KPiBwcm90ZWN0aW9uLTExDQo+ID4+Pj4+PiBE
aWZmOiAgICAgICAgICAgaHR0cHM6Ly93d3cuaWV0Zi5vcmcvcmZjZGlmZj91cmwyPWRyYWZ0LWll
dGYtaTJuc2Ytc2RuLWlwc2VjLQ0KPiBmbG93LXByb3RlY3Rpb24tMTENCj4gPj4+Pj4+DQo+ID4+
Pj4+PiBBYnN0cmFjdDoNCj4gPj4+Pj4+ICAgIFRoaXMgZG9jdW1lbnQgZGVzY3JpYmVzIGhvdyB0
byBwcm92aWRlIElQc2VjLWJhc2VkIGZsb3cgcHJvdGVjdGlvbg0KPiA+Pj4+Pj4gICAgKGludGVn
cml0eSBhbmQgY29uZmlkZW50aWFsaXR5KSBieSBtZWFucyBvZiBhbiBJbnRlcmZhY2UgdG8gTmV0
d29yaw0KPiA+Pj4+Pj4gICAgU2VjdXJpdHkgRnVuY3Rpb24gKEkyTlNGKSBjb250cm9sbGVyLiAg
SXQgY29uc2lkZXJzIHR3byBtYWluIHdlbGwtDQo+ID4+Pj4+PiAgICBrbm93biBzY2VuYXJpb3Mg
aW4gSVBzZWM6IChpKSBnYXRld2F5LXRvLWdhdGV3YXkgYW5kIChpaSkgaG9zdC10by0NCj4gPj4+
Pj4+ICAgIGhvc3QuICBUaGUgc2VydmljZSBkZXNjcmliZWQgaW4gdGhpcyBkb2N1bWVudCBhbGxv
d3MgdGhlDQo+ID4+Pj4+PiAgICBjb25maWd1cmF0aW9uIGFuZCBtb25pdG9yaW5nIG9mIElQc2Vj
IFNlY3VyaXR5IEFzc29jaWF0aW9ucyAoU0FzKQ0KPiA+Pj4+Pj4gICAgZnJvbSBhIEkyTlNGIENv
bnRyb2xsZXIgdG8gb25lIG9yIHNldmVyYWwgZmxvdy1iYXNlZCBOZXR3b3JrDQo+IFNlY3VyaXR5
DQo+ID4+Pj4+PiAgICBGdW5jdGlvbnMgKE5TRnMpIHRoYXQgcmVseSBvbiBJUHNlYyB0byBwcm90
ZWN0IGRhdGEgdHJhZmZpYy4NCj4gPj4+Pj4+DQo+ID4+Pj4+PiAgICBUaGUgZG9jdW1lbnQgZm9j
dXNlcyBvbiB0aGUgSTJOU0YgTlNGLWZhY2luZyBpbnRlcmZhY2UgYnkgcHJvdmlkaW5nDQo+ID4+
Pj4+PiAgICBZQU5HIGRhdGEgbW9kZWxzIGZvciBjb25maWd1cmluZyB0aGUgSVBzZWMgZGF0YWJh
c2VzIChTUEQsIFNBRCwNCj4gUEFEKQ0KPiA+Pj4+Pj4gICAgYW5kIElLRXYyLiAgVGhpcyBhbGxv
d3MgSVBzZWMgU0EgZXN0YWJsaXNobWVudCB3aXRoIG1pbmltYWwNCj4gPj4+Pj4+ICAgIGludGVy
dmVudGlvbiBieSB0aGUgbmV0d29yayBhZG1pbmlzdHJhdG9yLiAgSXQgZG9lcyBub3QgZGVmaW5l
IGFueQ0KPiA+Pj4+Pj4gICAgbmV3IHByb3RvY29sLg0KPiA+Pj4+Pj4NCj4gPj4+Pj4+DQo+ID4+
Pj4+Pg0KPiA+Pj4+Pj4NCj4gPj4+Pj4+IFBsZWFzZSBub3RlIHRoYXQgaXQgbWF5IHRha2UgYSBj
b3VwbGUgb2YgbWludXRlcyBmcm9tIHRoZSB0aW1lIG9mDQo+ID4+Pj4+PiBzdWJtaXNzaW9uIHVu
dGlsIHRoZSBodG1saXplZCB2ZXJzaW9uIGFuZCBkaWZmIGFyZSBhdmFpbGFibGUgYXQNCj4gdG9v
bHMuaWV0Zi5vcmcuDQo+ID4+Pj4+Pg0KPiA+Pj4+Pj4gVGhlIElFVEYgU2VjcmV0YXJpYXQNCj4g
Pj4+Pj4+DQo+ID4+Pj4+Pg0KPiA+Pj4+Pg0KPiA+Pj4+PiAtLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tDQo+ID4+Pj4+IFJhZmEgTWFyaW4tTG9w
ZXosIFBoRA0KPiA+Pj4+PiBEZXB0LiBJbmZvcm1hdGlvbiBhbmQgQ29tbXVuaWNhdGlvbnMgRW5n
aW5lZXJpbmcgKERJSUMpIEZhY3VsdHkgb2YNCj4gPj4+Pj4gQ29tcHV0ZXIgU2NpZW5jZS1Vbml2
ZXJzaXR5IG9mIE11cmNpYQ0KPiA+Pj4+PiAzMDEwMCBNdXJjaWEgLSBTcGFpbg0KPiA+Pj4+PiBU
ZWxmOiArMzQ4Njg4ODg1MDEgRmF4OiArMzQ4Njg4ODQxNTEgZS1tYWlsOiByYWZhQHVtLmVzDQo+
ID4+Pj4+IC0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0NCj4gPj4+Pj4NCj4gPj4+Pj4NCj4gPj4+Pj4NCj4gPj4+Pj4NCj4gPj4+Pj4NCj4gPj4+
Pj4NCj4gPj4+Pj4NCj4gPj4+DQo+ID4+PiAtLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tDQo+ID4+PiBSYWZhIE1hcmluLUxvcGV6LCBQaEQNCj4g
Pj4+IERlcHQuIEluZm9ybWF0aW9uIGFuZCBDb21tdW5pY2F0aW9ucyBFbmdpbmVlcmluZyAoRElJ
QykgRmFjdWx0eSBvZg0KPiA+Pj4gQ29tcHV0ZXIgU2NpZW5jZS1Vbml2ZXJzaXR5IG9mIE11cmNp
YQ0KPiA+Pj4gMzAxMDAgTXVyY2lhIC0gU3BhaW4NCj4gPj4+IFRlbGY6ICszNDg2ODg4ODUwMSBG
YXg6ICszNDg2ODg4NDE1MSBlLW1haWw6IHJhZmFAdW0uZXMNCj4gPj4+IC0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0NCj4gPj4+DQo+ID4+Pg0K
PiA+Pj4NCj4gPj4+DQo+ID4+Pg0KPiA+DQo+ID4gLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQ0KPiA+IFJhZmEgTWFyaW4tTG9wZXosIFBoRA0K
PiA+IERlcHQuIEluZm9ybWF0aW9uIGFuZCBDb21tdW5pY2F0aW9ucyBFbmdpbmVlcmluZyAoRElJ
QykgRmFjdWx0eSBvZg0KPiA+IENvbXB1dGVyIFNjaWVuY2UtVW5pdmVyc2l0eSBvZiBNdXJjaWEN
Cj4gPiAzMDEwMCBNdXJjaWEgLSBTcGFpbg0KPiA+IFRlbGY6ICszNDg2ODg4ODUwMSBGYXg6ICsz
NDg2ODg4NDE1MSBlLW1haWw6IHJhZmFAdW0uZXMNCj4gPiAtLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tDQo+ID4NCj4gPg0KPiA+DQo+ID4NCj4g
Pg0KPiANCj4gLS0NCj4gbGFzdC1jYWxsIG1haWxpbmcgbGlzdA0KPiBsYXN0LWNhbGxAaWV0Zi5v
cmcNCj4gaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9sYXN0LWNhbGwNCg==


From nobody Fri Oct 30 04:14:16 2020
Return-Path: <daedulus@btconnect.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 740493A09EA; Fri, 30 Oct 2020 04:14:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.147
X-Spam-Level: 
X-Spam-Status: No, score=-2.147 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, MSGID_FROM_MTA_HEADER=0.001, NICE_REPLY_A=-0.247, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=btconnect.onmicrosoft.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 vA0B3n1Wk8GH; Fri, 30 Oct 2020 04:14:11 -0700 (PDT)
Received: from EUR04-HE1-obe.outbound.protection.outlook.com (mail-eopbgr70110.outbound.protection.outlook.com [40.107.7.110]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2F9103A098D; Fri, 30 Oct 2020 04:14:10 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=P9cN6EE3hKJCPn639dAWV418dqwlRcw+nmbwefwfl/6mGfFRRp8rsrY91FvFhojp4GU9+MbbiGSlsTGGy7BulT6/wEUjQELb5C5mxixmkVBMWeoIh8Kl5YFytvX1fU0waSGLQV8tyDDsEQLGwxT+MLzVN0TjoknkTSAoN+8VFH5LOKsd/R7nzd/jZjkmMFF0WmuukkcImdPVovTmWNLErSLAxd8insoEuLXQ4eQgbTGLgAJE0zWkZvAqkPqYqoil3K1b+ToMA4Gz9pe+0LO04nL1COuCGv7TDmjvQKcfLSqx5RnfxhvDCQKIjuykJQyq8UyyfHgpGWvKpJswyarQ8g==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=RGwFUnIR8Iivb50F8q85Ns9Poz456tWO82o8o74V0UA=; b=IwO2SAgZf6e/edrvRTdyIc+shS4zGqDh3gHOEjNh9uxm3T9l4LiwAT7jFQ+QBP8iORHc+Ox4TVYSz0K8vjeoAyZIS7QnwV6B9UskADF46/3QLd+RcXRzCNAi1vUj2extZmo5GpzBrTBe3YZ0We/y+H8+IKNJa7WbxLJPSKYgfjUHc3fnO1YG1GEWN1t2FMbMKADylazGOkSb2OYB5Z/O7+6CESFIjJ2n77m1s4EJqbfbUSc9/cVgzi894nXdK6H/JspYdAiL30hlET0I1k0jG34MW0WUtKB2T3WyiVzp2Opv/+Vzvsqr4a/1WZcghujZOaKfo/YqarK0+gyXZ1LNmQ==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=btconnect.com; dmarc=pass action=none header.from=btconnect.com; dkim=pass header.d=btconnect.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=btconnect.onmicrosoft.com; s=selector2-btconnect-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=RGwFUnIR8Iivb50F8q85Ns9Poz456tWO82o8o74V0UA=; b=mh7SX0uoS7XOQYvvPalZUUQzTjSiFk3bqlcHhw9URc0IWqPto9UZ4zm3tUwNK4waqUJICwHkUXozE4XX8LlPMS0C5uk76LQXXLipQKspfGp4iQxxxM6f6Ac5eCJah//DK2OtKlJ/ZrcH7zULDiVOge8hl3RG0eCi5vSfXeyJzpQ=
Authentication-Results: ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=none action=none header.from=btconnect.com;
Received: from VI1PR07MB6704.eurprd07.prod.outlook.com (2603:10a6:800:18b::8) by VI1PR0701MB2221.eurprd07.prod.outlook.com (2603:10a6:800:22::13) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3499.14; Fri, 30 Oct 2020 11:14:08 +0000
Received: from VI1PR07MB6704.eurprd07.prod.outlook.com ([fe80::6407:6ea2:f517:eeae]) by VI1PR07MB6704.eurprd07.prod.outlook.com ([fe80::6407:6ea2:f517:eeae%7]) with mapi id 15.20.3499.028; Fri, 30 Oct 2020 11:14:08 +0000
To: Roman Danyliw <rdd@cert.org>, Rafa Marin-Lopez <rafa@um.es>
References: <160337357077.29083.9236626834026808055@ietfa.amsl.com> <EE5AB669-73BB-4517-A6F4-23B7807FB36E@um.es> <5F9815D1.9010303@btconnect.com> <DDE550B1-9A9E-4954-B6F9-C0A33ECE1275@um.es> <5F99B221.3040504@btconnect.com> <56155C91-BFE8-4BA9-A55C-46B12E59CD94@um.es> <5F9AEFD3.90903@btconnect.com> <059aaae84a354411ad1023afa2a837ba@cert.org>
Cc: "i2nsf@ietf.org" <i2nsf@ietf.org>, Fernando Pereniguez-Garcia <fernando.pereniguez@cud.upct.es>, Gabriel Lopez <gabilm@um.es>, "ynir.ietf@gmail.com" <ynir.ietf@gmail.com>, "last-call@ietf.org" <last-call@ietf.org>
From: tom petch <daedulus@btconnect.com>
Message-ID: <5F9BF578.6000101@btconnect.com>
Date: Fri, 30 Oct 2020 11:14:00 +0000
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:38.0) Gecko/20100101 Thunderbird/38.5.0
In-Reply-To: <059aaae84a354411ad1023afa2a837ba@cert.org>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
X-Originating-IP: [86.146.121.140]
X-ClientProxiedBy: LO3P123CA0009.GBRP123.PROD.OUTLOOK.COM (2603:10a6:600:ba::14) To VI1PR07MB6704.eurprd07.prod.outlook.com (2603:10a6:800:18b::8)
MIME-Version: 1.0
X-MS-Exchange-MessageSentRepresentingType: 1
Received: from [192.168.1.65] (86.146.121.140) by LO3P123CA0009.GBRP123.PROD.OUTLOOK.COM (2603:10a6:600:ba::14) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.20.3499.18 via Frontend Transport; Fri, 30 Oct 2020 11:14:07 +0000
X-MS-PublicTrafficType: Email
X-MS-Office365-Filtering-Correlation-Id: c6f295c8-d9fa-465c-1e2d-08d87cc4eb6f
X-MS-TrafficTypeDiagnostic: VI1PR0701MB2221:
X-Microsoft-Antispam-PRVS: <VI1PR0701MB22213D3B627F65FFFCA6CA9AC6150@VI1PR0701MB2221.eurprd07.prod.outlook.com>
X-MS-Oob-TLC-OOBClassifiers: OLM:9508;
X-MS-Exchange-SenderADCheck: 1
X-Microsoft-Antispam: BCL:0;
X-Microsoft-Antispam-Message-Info: 7ZR1cgCtiY1hI12TeQs7JeWgm019DJznkNxKBHDHBaGJ5tCohJG2pWmnxsCATtNvDGlTY2PmSiNpCHcNfJ0bsM4Bi8mXeP3tnMReSkLwBw985EtJHxKbY+KAsldLxJ8UUou++AyE33SgGBx1L1/vSeEvNA9rsW+T3gpswbSyEOTT+j+B+gvZS/Q+9A+LkrnWS+tNwGcNd8QXiGhBT+ATHNL85d5itQcX8422B5wsk3BV2ZVNgGLGcOe5aHoDmflDRqb8yaIjDvjzjTjCjoGqGFvthnqeXJH9kmneSjpxe8T81KRYG73BJ5svfTUeFM2Vfgnmc7wLj7c92ZY7/ZbLpQqxO+DLiYsR2a62/kDDhLOYON47ulfRuFzl1MBGDYmgBVxGg9ZpIBWt1M4lBMo9vA==
X-Forefront-Antispam-Report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;  IPV:NLI; SFV:NSPM; H:VI1PR07MB6704.eurprd07.prod.outlook.com; PTR:; CAT:NONE;  SFS:(39860400002)(136003)(366004)(346002)(376002)(396003)(16526019)(8936002)(33656002)(15650500001)(186003)(66476007)(87266011)(66574015)(966005)(26005)(36756003)(86362001)(83380400001)(6486002)(2906002)(4326008)(16576012)(6666004)(66946007)(52116002)(66556008)(316002)(478600001)(5660300002)(8676002)(110136005)(4001150100001)(30864003)(54906003)(2616005)(53546011)(956004); DIR:OUT; SFP:1102; 
X-MS-Exchange-AntiSpam-MessageData: r9t0gKFBMQrXA8c3jD/RgTiulvKlYCV7Y72U6EUzwGF7gswLj4cbArPEV6DO32zXe8X5VhoLelI3PZxjca2ttM83LbZZ9adf7fIPvGq5722mZn7Og1hXJ8/YdnWgVKiwM5GwHLb1eGeGu4+IoUsz2Arv0+zgCykylxW6T+14P3OXII1+MtrfuaL1HkEymOFyUEvnJF1s8o9XHllX4LsNpRPz+RZ1Qrn/pXgsbf4D82mffq4UGSJ6Ryo6/H8MymdjtfzZMLf2Oq8CRBn6l+rmw6xRJ9JwD13FQcmZo+ElnGl7NgJ7tIx4DKdx31+YdYH1/WuBT7P/aYHkHipBOB8f0pIXKSR8oB/xb7FMD8aNL2o1aup3FgNSm0x73JmMqxkDGjL5LturZTUke16hjSnwRKDK7tVS7JtPvH1XTCT/BbCNcR7Zt4EybplXVFLcr5IYMFhfeUFkRzg/EKGMyOQYFuW1agQKFe83ZXXMdWhlbVzOYA/tblQcciuy8+Qi2rIKVyVZwDnx7D6fjgvjLfvxAWpbGK0gbx8wm4sQf0Vk1hDsiwM7FcSmnZO35wVYZeu7yJn0SZ/eQI5yVT++ZMQ8i7y1iDZO5ifEuCVowWhJ7nHuPiTpKnAGqW3Vy3vzbYE9E+gUNvuomNpPN/LmpwvX9A==
X-OriginatorOrg: btconnect.com
X-MS-Exchange-CrossTenant-Network-Message-Id: c6f295c8-d9fa-465c-1e2d-08d87cc4eb6f
X-MS-Exchange-CrossTenant-AuthSource: VI1PR07MB6704.eurprd07.prod.outlook.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 30 Oct 2020 11:14:08.0577 (UTC)
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-CrossTenant-Id: cf8853ed-96e5-465b-9185-806bfe185e30
X-MS-Exchange-CrossTenant-MailboxType: HOSTED
X-MS-Exchange-CrossTenant-UserPrincipalName: gWTkAwUhPCjP5WLgw4whEZIpVODs1MZsDvKfnF63ShyyL81kIi341K9yUxuOFcaMQlRaLBUwyu53EZEjAr6oFQ==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: VI1PR0701MB2221
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2nsf/805Mpu1k4QUSyZuR-69RGAP0GbQ>
Subject: Re: [I2nsf] [Last-Call] New Version Notification for draft-ietf-i2nsf-sdn-ipsec-flow-protection-11.txt
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: Fri, 30 Oct 2020 11:14:14 -0000

Roman  not this I-D but see below

On 29/10/2020 18:46, Roman Danyliw wrote:
> Hi Tom!
>
>> -----Original Message-----
>> From: last-call <last-call-bounces@ietf.org> On Behalf Of tom petch
>> Sent: Thursday, October 29, 2020 12:38 PM
>> To: Rafa Marin-Lopez <rafa@um.es>
>> Cc: i2nsf@ietf.org; Fernando Pereniguez-Garcia
>> <fernando.pereniguez@cud.upct.es>; Gabriel Lopez <gabilm@um.es>;
>> ynir.ietf@gmail.com; last-call@ietf.org
>>
>> Top posting a new, related issue that may need Security AD or WG Chair to act
>> on.
>>
>> It seems to me that the IANA entries for IKEv2 are incomplete.  RFC8247 does a
>> fine job of specifying algorithms and adding information such as status
>> (MUST/SHOULD+), IoT, AEAD and so on, information which is not present on
>> IANA.  The policy for, e.g. Transform Type 1, is expert review and entries have
>> been added via draft-smyslov-esp-gont but the IANA entries lack this
>> information and, looking at the I-D, I see no such information (nor is there any
>> reason for it to be there).  Yet draft-ietf-i2nsf-sdn... needs this information as
>> references in the YANG module show.
>>
>> It seems to me that this is a similar situation to that which the TLS WG found
>> itself in and which led to a revision of the TLS IANA entries to provide what was
>> needed via additional columns.
>
> Please help me understand.  In particular, I'm not following why this document should modify IKE IANA registries.  In my view, this document is provides a data model to encode an "IKEv2 configuration" of sorts.  Certainly, there are valid/invalid/incomplete/not recommended ways to provide a configuration with this data model if one relied solely on the pointers to the IANA registries from the YANG module definition.  However, as you noted, RFC8247 already provides guidance on specifying a configuration (albeit this guidance isn't fully encoded in the registries).  Furthermore, this document states:
>
> Section 8.1
>     o  IKEv2 configurations should adhere to the recommendations in
>        [RFC8247].
>
> so there is guidance on producing a configuration.  What is missing?
>
>> I think that the IANA pages for IKEv2 need revising so that that additional
>> information that RFC8247 provides is required as additional columns in the
>> IANA entries at least for Type 1, Type 2, Type 3, Type 4 and Authentication
>> Method.
>
> While things could be clearer, I'm unsure of why _this YANG document_ should do a registry reengineering.  Did you mean it should be done in general?

Not this I-D but another I-D from a WG with closer links to IKEv2; I 
don't know which WG that would be but a Security AD would:-)

This I-D, as you quote, points to RFC8247 for guidance and that is fine. 
  But security moves on and new algorithms will be needed and this I-D 
also points to the IANA registry, which is Expert Review, where new 
entries have been added already; and for those the IANA Registry gives 
no guidance and the I-D that IANA references for the new entries - 
written by the Expert Reviewer! - also gives no guidance. Over time we 
are likely to accrue algorithms with no guidance unless and until an 
RFC8247-bis appears or we require IANA to have columns for guidance. 
Currently the new algorithms are GOST and so perhaps of limited interest 
but on the TLS list I am always seeing new algorithms appear and there 
the new IANA entry is required to give guidance.  My sense is that IKEv2 
is a bit slower to take up new ones but, as with RFC8247, it does 
eventually.

I think that users need those extra columns that RFC8247 provides on the 
IANA website so that when new algorithms are added by Expert Review, 
then that guidance must be added as well.  This is what the TLS WG came 
round to and I think that IKEv2 needs to do the same.

Tom Petch


> Regards,
> Roman
>
>> Tom Petch
>>
>> On 29/10/2020 11:23, Rafa Marin-Lopez wrote:
>>> Hi Tom:
>>>
>>>> El 28 oct 2020, a las 19:02, tom petch <daedulus@btconnect.com> escribió:
>>>>
>>>> On 28/10/2020 10:42, Rafa Marin-Lopez wrote:
>>>>> Hi Tom:
>>>>>
>>>>> Thank you very much for your insight. It is very helpful. Please see our
>> comments/questions inline.
>>>>>
>>>>>> El 27 oct 2020, a las 13:42, tom petch <daedulus@btconnect.com>
>> escribió:
>>>>>>
>>>>>> I think that the IESG will find a number of problems with this I-D.
>>>>>>
>>>>>> YANG module references RFC822 which is several years out of date
>>>>
>>>> Rafa
>>>>
>>>> On boiler plate, I mean the reference to RFC2119 which now must use the
>> language from RFC8174 in the body of the I-D; sorry for the confusion.
>>>
>>> Ah ok. I guess you are referring to change that paragraph with this:
>>>
>>>
>>> The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
>>> "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED",
>> "MAY", and
>>> "OPTIONAL" in this document are to be interpreted as described in BCP
>>> 14 RFC2119 RFC8174 when, and only when, they appear in all capitals,
>>> as shown here.
>>>
>>>>
>>>> On XXXX, you have XXXX standing in for more than one RFC-to-be which
>> confuses.  The convention is to use XXXX for this I-D and then AAAA BBBB etc
>> for any others such as the netconf I-D in this instance.
>>>
>>> Ah ok. In any case, we have now only XXXX for our RFC-to-be so problem
>> fixed.
>>>>
>>>> Two big issues, for me (perhaps not for others).  The convention with YANG
>> is for each successive line to be indented two characters, you have four, which
>> creates a lot of white space and pushes the text to the right hand margin.  I
>> think that two characters is the default when you use pyang to format a YANG
>> module.
>>>
>>> We can try to reduce it to two characters.
>>>
>>>>
>>>> And references.  I have had to work harder than I want to to make
>>>> sense of the IANA references.  I think you should have five separate
>>>> references in the I-D for IANA for Transform Type 1 Transform Type 3
>>>> Transform Type 4 Authentication Method Protocol Numbers and each
>>>> reference in the I-D should have a URL pointing to the specific section of
>> IANA web site.
>>>
>>> Ok, good. This follows what we thought.
>>>
>>>> In the YANG, it is harder to know what to do.  Those first three references
>> are in the third tier i.e.
>>>> Group - Internet Key Exchange V2 (IKEv2) Parameters Registry
>>>> -Transform Attribute Types and then Type 1, 3, 4 as the third tier as
>>>> I am calling it and I think that every reference in the YANG should
>>>> give me all three tiers after IANA in that order perhaps IANA; IKEv2
>>>> Parameters; Transform Atribute Types; Transform Type 1
>>>
>>> Great. We also considered this as a possible solution after sending our e-mail.
>> Let’s do it.
>>>
>>>> If the syntax needs tweeking, then the RFC Editor will do a good job of that
>> but at present the references are inconsistent in which elements are specified
>> in what order and that is something the RFC Editor probably cannot cope with.
>>>> Authentication Method is a registry so that just needs Group name and
>> Registry name after IANA.
>>>
>>> Ok, good.
>>>>
>>>> Some minor glitches.
>>>> I-D appears twice in the body of the I-D - perhaps document or memo.
>>>
>>> Ok.
>>>
>>>> objetives/objectives/
>>>
>>> Fixed.
>>>> end port number perhaps /must/MUST/
>>>
>>>> and YANG is very good at including such checks with a must ....
>>>> 'If AEAD is used .. where? this occurs in several places and I think that you
>> need to specify the leaf where AEAD will be specified or implied.
>>>
>>> Ok we have changed it to:
>>>
>>> If Authenticated Encryption with Associated Data (AEAD) is used (leaf
>>> esp-algorithms/encryption/algorithm-type)
>>> this flag MUST be false."
>>>
>>>> And is it possible to make that a YANG 'must' statement - looking at the
>> IKEv2 registries it is not obvious which are AEAD so that might be more
>> complexity than it is worth.
>>>> 'only available on linux kernels' Um implementation detail, you may get
>> asked to remove that altogether or at least to a Informative Appendix - I would
>> leave it in for now.
>>>
>>> Ok.
>>>
>>>> 'import ietf-i2nsf-ikec' the reference needs to be to a RFC and if it
>>>> is not yet an RFC then RFC XXXX <title> in both Appendix B and C
>>>
>>> Yes, we have changed that to:
>>>
>>> RFC XXXX: Software-Defined Networking
>>>                  (SDN)-based IPsec Flow Protection.
>>>
>>>> leaf-list pfs-groups could do with a reference - Transform Type 4?
>>>
>>> The leaf list is referring to type pfs-group and we have now
>>>
>>> typedef pfs-group {
>>>               type uint16;
>>>               description
>>>                   "DH groups for IKE and IPsec SA rekey.";
>>>               reference
>>>                   "IANA; Internet Key Exchange V2 (IKEv2) Parameters;
>>> 				Transform Atribute Types; Transform Type 4 -
>>>                   Diffie-Hellman Group Transform IDs.
>>> 				Section 3.3.2 in RFC 7296.";
>>>           }
>>>
>>>
>>>>
>>>> I am still working my way through the YANG so may have some more
>> comments tomorrow.
>>>
>>> Ok, do not worry we will work in -12 with these comments so far to have a
>> quick response. We can prepare a another version later with the rest of them.
>>>
>>> Thank you very much for your effort.
>>>>
>>>> Tom Petch
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>> We have realized that we missed to change this, even though we discussed
>> it. We will change it right away in the following way (bold):
>>>>>
>>>>> case rfc822-address-string {
>>>>>        leaf rfc822-address-string {
>>>>>             type string;
>>>>>             description
>>>>>                 "Specifies the identity as a
>>>>>                  fully-qualified RFC5322 email
>>>>>                  address string. An example is,
>>>>>                  jsmith@example.com. The string
>>>>>                  MUST NOT contain any
>>>>>                  terminators e.g., NULL, CR,
>>>>>                  etc.).";
>>>>>              reference
>>>>>                     "RFC 5322.";
>>>>>        }
>>>>> }
>>>>>
>>>>> Btw, we already used in the past “case rfc822-address-string” and “leaf
>> rfc822-address-string” since this is coming from IKEv2 standard. Do you think
>> we should change that name as well?
>>>>>
>>>>>
>>>>>>
>>>>>> YANG module references IANA Protocol Numbers which is not in the
>>>>>> I-D references
>>>>>
>>>>> We have included the following reference:
>>>>>
>>>>> [IANA-Protocols-Number]
>>>>>                 Internet Assigned Numbers Authority (IANA), "Protocol
>>>>>                 Numbers", January 2020.
>>>>>
>>>>>
>>>>>>
>>>>>> s.2 boiler plate is out of date
>>>>>
>>>>> What we see is the I-D has the second choice stated in
>>>>> https://www.ietf.org/standards/ids/guidelines/
>>>>>
>>>>> This Internet-Draft is submitted in full conformance with the
>>>>>      provisions of BCP 78 and BCP 79.
>>>>>
>>>>>      Internet-Drafts are working documents of the Internet Engineering
>>>>>      Task Force (IETF).  Note that other groups may also distribute
>>>>>      working documents as Internet-Drafts.  The list of current Internet-
>>>>>      Drafts is at https://datatracker.ietf.org/drafts/current/.
>>>>>
>>>>>      Internet-Drafts are draft documents valid for a maximum of six months
>>>>>      and may be updated, replaced, or obsoleted by other documents at any
>>>>>      time.  It is inappropriate to use Internet-Drafts as reference
>>>>>      material or to cite them other than as "work in progress."
>>>>>
>>>>> Could you refer what is out of date?
>>>>>
>>>>>>
>>>>>> XXXX is standing in for more than one RFC
>>>>>
>>>>> Yes, XXXX has been used because we do not know the future number
>> assigned to our I-D.
>>>>>
>>>>> Also we realized we also included this to refer to crypto-types I-D but this
>> has been solved now in a new version -12 that we are preparing to include your
>> comments. We noticed we can replace the type of rw cert-data?, ca-data*, crl-
>> data? for binary without any problem.
>>>>>
>>>>> |           |     +--rw cert-data?        binary
>>>>> |           +--rw private-key?            binary
>>>>> |           +--rw ca-data*                binary
>>>>> |           +--rw crl-data?               binary
>>>>>
>>>>>>
>>>>>> but the show stopper that makes a proper review of this too costly is the
>> references.  Those to IANA of which there are several I want to pursue.  The I-D
>> reference is to IKEv2 parameters. Sadly, this is a three tier structure and noone
>> agrees on what to call the third tier so I will call it tier3 here.  Top level is
>> Group, as per RFC8126, second level is Registry.  The I-D reference is to the
>> Group only which is fine if the actual reference then specifies the Registry and
>> Tier3 but they never do, usually just Tier3 e.g. Transform Type 3 which makes
>> for a lot of work for the reader, too much for this one.  You have to go hunting
>> in all the second level Registry until you can find a match for the Tier3
>> identifier. And there are no URL.  If you want an example that I find easy to use,
>> go look at RFC8407 (as usual).
>>>>>
>>>>> You’re right. Could you point the exact part at RFC 8407 with that
>> example? We would really appreciate it.
>>>>>
>>>>> On the other hand, would it be enough to include the URL for Transform
>> Type 3 https://www.iana.org/assignments/ikev2-parameters/ikev2-
>> parameters.xhtml#ikev2-parameters-7 ?
>>>>>
>>>>> (Same for Transform Type 1, Transform Type 4)
>>>>>
>>>>>>
>>>>>> The reference for import of i2nsf-ikec gives a YANG module name;
>>>>>> this needs to be the name of the RFC to be
>>>>>
>>>>> Fixed.
>>>>>
>>>>> import ietf-i2nsf-ikec {
>>>>>               prefix nsfikec;
>>>>>               reference
>>>>>                   "RFC XXXX: Software-Defined Networking
>>>>>                  (SDN)-based IPsec Flow Protection."; }
>>>>>
>>>>> We still use XXXX because we do not know the number assigned to the RFC
>> to be.
>>>>>
>>>>>>
>>>>>> The example IPv6 address in the YANG module has :0:0: which is usually
>> just ::
>>>>>
>>>>> Fixed.
>>>>>
>>>>> If you have any further comments, please let us know so we can
>>>>> include them in -12
>>>>>
>>>>> Best Regards.
>>>>>>
>>>>>> And I have some way to go still.
>>>>>>
>>>>>> Tom Petch
>>>>>>
>>>>>> On 22/10/2020 18:39, Rafa Marin-Lopez wrote:
>>>>>>> Dear all:
>>>>>>>
>>>>>>> After receiving a suggestion to make things clearer in the feature ikeless-
>> notification description, we have just uploaded a new version -11 with a minor
>> change to add the following text:
>>>>>>>
>>>>>>> feature ikeless-notification {
>>>>>>>               description
>>>>>>>                   "This feature indicates that the server supports
>>>>>>>                   generating notifications in the ikeless module.
>>>>>>>
>>>>>>>                   To ensure broader applicability of this module,
>>>>>>>                   the notifications are marked as a feature.
>>>>>>>                   For the implementation of ikeless case,
>>>>>>>                   the NSF is expected to implement this
>>>>>>>                   feature.";
>>>>>>>           }
>>>>>>>
>>>>>>> Best Regards.
>>>>>>>
>>>>>>>> Inicio del mensaje reenviado:
>>>>>>>>
>>>>>>>> De: internet-drafts@ietf.org
>>>>>>>> Asunto: New Version Notification for
>>>>>>>> draft-ietf-i2nsf-sdn-ipsec-flow-protection-11.txt
>>>>>>>> Fecha: 22 de octubre de 2020, 15:32:50 CEST
>>>>>>>> Para: "Fernando Pereniguez-Garcia"
>>>>>>>> <fernando.pereniguez@cud.upct.es>, "Rafael Lopez" <rafa@um.es>,
>>>>>>>> "Gabriel Lopez-Millan" <gabilm@um.es>, "Rafa Marin-Lopez"
>>>>>>>> <rafa@um.es>
>>>>>>>>
>>>>>>>>
>>>>>>>> A new version of I-D,
>>>>>>>> draft-ietf-i2nsf-sdn-ipsec-flow-protection-11.txt
>>>>>>>> has been successfully submitted by Rafa Marin-Lopez and posted to
>>>>>>>> the IETF repository.
>>>>>>>>
>>>>>>>> Name:		draft-ietf-i2nsf-sdn-ipsec-flow-protection
>>>>>>>> Revision:	11
>>>>>>>> Title:		Software-Defined Networking (SDN)-based IPsec Flow
>> Protection
>>>>>>>> Document date:	2020-10-22
>>>>>>>> Group:		i2nsf
>>>>>>>> Pages:		92
>>>>>>>> URL:            https://www.ietf.org/archive/id/draft-ietf-i2nsf-sdn-ipsec-
>> flow-protection-11.txt
>>>>>>>> Status:         https://datatracker.ietf.org/doc/draft-ietf-i2nsf-sdn-ipsec-
>> flow-protection/
>>>>>>>> Htmlized:       https://datatracker.ietf.org/doc/html/draft-ietf-i2nsf-sdn-
>> ipsec-flow-protection
>>>>>>>> Htmlized:       https://tools.ietf.org/html/draft-ietf-i2nsf-sdn-ipsec-flow-
>> protection-11
>>>>>>>> Diff:           https://www.ietf.org/rfcdiff?url2=draft-ietf-i2nsf-sdn-ipsec-
>> flow-protection-11
>>>>>>>>
>>>>>>>> Abstract:
>>>>>>>>     This document describes how to provide IPsec-based flow protection
>>>>>>>>     (integrity and confidentiality) by means of an Interface to Network
>>>>>>>>     Security Function (I2NSF) controller.  It considers two main well-
>>>>>>>>     known scenarios in IPsec: (i) gateway-to-gateway and (ii) host-to-
>>>>>>>>     host.  The service described in this document allows the
>>>>>>>>     configuration and monitoring of IPsec Security Associations (SAs)
>>>>>>>>     from a I2NSF Controller to one or several flow-based Network
>> Security
>>>>>>>>     Functions (NSFs) that rely on IPsec to protect data traffic.
>>>>>>>>
>>>>>>>>     The document focuses on the I2NSF NSF-facing interface by providing
>>>>>>>>     YANG data models for configuring the IPsec databases (SPD, SAD,
>> PAD)
>>>>>>>>     and IKEv2.  This allows IPsec SA establishment with minimal
>>>>>>>>     intervention by the network administrator.  It does not define any
>>>>>>>>     new protocol.
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> Please note that it may take a couple of minutes from the time of
>>>>>>>> submission until the htmlized version and diff are available at
>> tools.ietf.org.
>>>>>>>>
>>>>>>>> The IETF Secretariat
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>> -------------------------------------------------------
>>>>>>> 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
>>>>>>> -------------------------------------------------------
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>
>>>>> -------------------------------------------------------
>>>>> 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
>>>>> -------------------------------------------------------
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>
>>> -------------------------------------------------------
>>> 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
>>> -------------------------------------------------------
>>>
>>>
>>>
>>>
>>>
>>
>> --
>> last-call mailing list
>> last-call@ietf.org
>> https://www.ietf.org/mailman/listinfo/last-call


From nobody Fri Oct 30 10:43:19 2020
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 998773A107E; Fri, 30 Oct 2020 10:43:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level: 
X-Spam-Status: No, score=-2.099 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, RCVD_IN_MSPIKE_H2=-0.001, 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=um.es
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 DQCeviE_PEoU; Fri, 30 Oct 2020 10:43:13 -0700 (PDT)
Received: from mx02.puc.rediris.es (outbound4sev.lav.puc.rediris.es [130.206.19.177]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 57F403A107F; Fri, 30 Oct 2020 10:43:13 -0700 (PDT)
Received: from xenon42.um.es (xenon42.um.es [155.54.212.169]) by mx02.puc.rediris.es  with ESMTP id 09UHh8ub012419-09UHh8uc012419; Fri, 30 Oct 2020 18:43:08 +0100
Received: from localhost (localhost [127.0.0.1]) by xenon42.um.es (Postfix) with ESMTP id 658C020570; Fri, 30 Oct 2020 18:43:08 +0100 (CET)
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 AXIYS4nW8zRw; Fri, 30 Oct 2020 18:43:08 +0100 (CET)
Received: from [192.168.1.33] (135.red-79-150-250.dynamicip.rima-tde.net [79.150.250.135]) (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 712F72005B; Fri, 30 Oct 2020 18:43:04 +0100 (CET)
From: Rafa Marin-Lopez <rafa@um.es>
Message-Id: <EC88EEFE-5F98-487A-9294-F78B99AC9C47@um.es>
Content-Type: multipart/alternative; boundary="Apple-Mail=_8D60455B-CB51-4C7A-A113-2FA3F529E451"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.14\))
Date: Fri, 30 Oct 2020 18:43:03 +0100
In-Reply-To: <5F9AF68D.7060105@btconnect.com>
Cc: Rafa Marin-Lopez <rafa@um.es>, i2nsf@ietf.org, Fernando Pereniguez-Garcia <fernando.pereniguez@cud.upct.es>, Gabriel Lopez <gabilm@um.es>, ynir.ietf@gmail.com, last-call@ietf.org
To: tom petch <daedulus@btconnect.com>
References: <160337357077.29083.9236626834026808055@ietfa.amsl.com> <EE5AB669-73BB-4517-A6F4-23B7807FB36E@um.es> <5F9815D1.9010303@btconnect.com> <DDE550B1-9A9E-4954-B6F9-C0A33ECE1275@um.es> <5F99B221.3040504@btconnect.com> <56155C91-BFE8-4BA9-A55C-46B12E59CD94@um.es> <5F9AF68D.7060105@btconnect.com>
X-Mailer: Apple Mail (2.3445.104.14)
X-FEAS-SPF: spf-result=pass, ip=155.54.212.169, helo=xenon42.um.es, mailFrom=rafa@um.es
Authentication-Results: mx02.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
X-FE-Policy-ID: 2:15:0:SYSTEM, 2:15:1:upct.es
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=oUymHWnPMq5NSzzhhf8UQmwVrDvEq6s5/LSSgiD92LI=; b=TIN1QaWSqEq1GpWBOz8wA1OJMcOTPYOssFXsem8NEq27l146N7blEZ6q1XORim07RX9mlDtAwkN4 +36FmgZN1AAiZuUjnEVg/wzh6EL6B6D+nP+uUOz3I3BAsosWHENO2FYo4860kYexV3qlag2VzQgG bnH+4adKRYWZuhpYcdaJ6Ti4TvRkMI8X7Mqer3odhfyp5CtAqnlVM7wGt1c1PoB7xxLObPC8mGnj X9AjRztd/kT015qbxt1Ztmu+ek8oVa2CQCosuC9n7LFmhdaYYV8OoDGSxJIFK4DCFm2imbH3au3Q n4PYVVH11UBXCz9P+ev5SxV6Au+laXA3u5kmRQ==
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2nsf/cSbDzzvFEzs3qrB7gTWvoMOVy0Y>
Subject: Re: [I2nsf] [Last-Call] New Version Notification for draft-ietf-i2nsf-sdn-ipsec-flow-protection-11.txt
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: Fri, 30 Oct 2020 17:43:18 -0000

--Apple-Mail=_8D60455B-CB51-4C7A-A113-2FA3F529E451
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Hi Tom:

Thank you very much again. See our comments inline:

> El 29 oct 2020, a las 18:06, tom petch <daedulus@btconnect.com> =
escribi=C3=B3:
>=20
> Back to routine comments on this I-D; I don't think that any of my =
earlier ones are unresolved.
>=20
> On 29/10/2020 11:23, Rafa Marin-Lopez wrote:
>> Hi Tom:
>>=20
>>> El 28 oct 2020, a las 19:02, tom petch <daedulus@btconnect.com> =
escribi=C3=B3:
>>>=20
>>> On 28/10/2020 10:42, Rafa Marin-Lopez wrote:
>>>> Hi Tom:
>>>>=20
>>>> Thank you very much for your insight. It is very helpful. Please =
see our comments/questions inline.
>>>>=20
>>>>> El 27 oct 2020, a las 13:42, tom petch <daedulus@btconnect.com> =
escribi=C3=B3:
>>>>>=20
>>>>> I think that the IESG will find a number of problems with this =
I-D.
>>>>>=20
>>>>> YANG module references RFC822 which is several years out of date
>=20
> Rafa
>=20
> Several YANG leaf are in seconds, eight I think, but none use the YANG
> units seconds;
> statement.  I suggest adding it.

Added. They are seven.
>=20
> typedef ipsec-spd-action
> capitalises the actions as does RFC4301 but later uses of this have =
lower case actions; probably ok as it is

Ok.
>=20
> protocol number appears in several places but technically, IPv6, which =
we must all love and promote, has 'next header' instead.  Probably worth =
a mention at least once in the YANG module

We have included this note:


NOTE: In case of IPv6, the protocol in the IP packet payload is
specified in the Next Header field of the IPv6=20
packet.";
>=20
> On the start >=3D end, I was looking at nat-yang and it has
> must ". >=3D ../start-port-number"
> which is the sort of YANG constraint I had in mind

Done.=20

must '. >=3D ../start=E2=80=99


>=20
> leaf dscp-mapping
> I do not understand, a hex string of indeterminate length for DSCP =
values (plural).  I expect DSCP to be six bit and values to be a =
leaf-list

Right. Since we have inet:dscp type , we have used that one in a =
leaf-list as you recommend.

leaf-list dscp-mapping {=20
       type inet:dscp;
       default 0;
       description=20
         "DSCP values allowed for packets carried over
         this IPsec SA.";=20
       reference
         "Section 4.4.2.1. in RFC 4301.";
     }

>=20
> leaf ecn
> /Annex C/Appendix C/

Fixed.
>=20
> I see that RFC8247 gives AEAD status which is a good reference to have =
except that as my other post today says there is no requirement for any =
future additions to the IANA data to include this information; IANA for =
IKEv2 needs updating iun a separate I-D!
>=20
> leaf mask
> hex-string with no length specified

Since this masked is after all 32-bits mask we have used uint32 instead.
>=20
> leaf ds-algorithm
> default 1
> which I think is RSA; worth stating as it might raise some AD eyebrows

Clarified in the description.
>=20
> pfs-groups
> /it is required perfect forward secrecy/perfect forward secrecy is =
required/

Fixed.

> and a reference to Transform Type 4?

As we mention earlier, this pfs-groups used the type pfs-group, which =
includes the reference to Transform Type 4.
>=20
> leaf ext-seq-num
> /FALSE/false/ or /False/?
>=20
> leaf encryption-algorithm (twice, in separate containers)

Mmmmm=E2=80=A6 we only see in one place.

> /the integrity leaf/ the integrity-algorithm leaf/

Fixed.
>=20
> I have yet to look at the text or the examples, probably next week.

Thank you very much. We are going to post -12 with all these comments =
and the previous ones so far. If there are pending comments we can =
prepare -13 right away.

Best Regards.
>=20
> Tom Petch
>=20
>=20
>=20
>=20
>=20
>=20
>=20
>=20
>=20
>=20
>>>=20
>>> On boiler plate, I mean the reference to RFC2119 which now must use =
the language from RFC8174 in the body of the I-D; sorry for the =
confusion.
>>=20
>> Ah ok. I guess you are referring to change that paragraph with this:
>>=20
>>=20
>> The key words "MUST", "MUST NOT", "REQUIRED",
>> "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT",
>> "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
>> "OPTIONAL" in this document are to be interpreted
>> as described in BCP 14 RFC2119 RFC8174 when,
>> and only when, they appear in all capitals,
>> as shown here.
>>=20
>>>=20
>>> On XXXX, you have XXXX standing in for more than one RFC-to-be which =
confuses.  The convention is to use XXXX for this I-D and then AAAA BBBB =
etc for any others such as the netconf I-D in this instance.
>>=20
>> Ah ok. In any case, we have now only XXXX for our RFC-to-be so =
problem fixed.
>>>=20
>>> Two big issues, for me (perhaps not for others).  The convention =
with YANG is for each successive line to be indented two characters, you =
have four, which creates a lot of white space and pushes the text to the =
right hand margin.  I think that two characters is the default when you =
use pyang to format a YANG module.
>>=20
>> We can try to reduce it to two characters.
>>=20
>>>=20
>>> And references.  I have had to work harder than I want to to make =
sense of the IANA references.  I think you should have five separate =
references in the I-D for IANA for
>>> Transform Type 1
>>> Transform Type 3
>>> Transform Type 4
>>> Authentication Method
>>> Protocol Numbers
>>> and each reference in the I-D should have a URL pointing to the =
specific section of IANA web site.
>>=20
>> Ok, good. This follows what we thought.
>>=20
>>> In the YANG, it is harder to know what to do.  Those first three =
references are in the third tier i.e.
>>> Group - Internet Key Exchange V2 (IKEv2) Parameters
>>> Registry  -Transform Attribute Types
>>> and then Type 1, 3, 4 as the third tier as I am calling it
>>> and I think that every reference in the YANG should give me all =
three tiers after IANA in that order perhaps
>>> IANA; IKEv2 Parameters; Transform Atribute Types; Transform Type 1
>>=20
>> Great. We also considered this as a possible solution after sending =
our e-mail. Let=E2=80=99s do it.
>>=20
>>> If the syntax needs tweeking, then the RFC Editor will do a good job =
of that but at present the references are inconsistent in which elements =
are specified in what order and that is something the RFC Editor =
probably cannot cope with.
>>> Authentication Method is a registry so that just needs Group name =
and Registry name after IANA.
>>=20
>> Ok, good.
>>>=20
>>> Some minor glitches.
>>> I-D appears twice in the body of the I-D - perhaps document or memo.
>>=20
>> Ok.
>>=20
>>> objetives/objectives/
>>=20
>> Fixed.
>>> end port number perhaps /must/MUST/
>>=20
>>> and YANG is very good at including such checks with a must ....
>>> 'If AEAD is used .. where? this occurs in several places and I think =
that you need to specify the leaf where AEAD will be specified or =
implied.
>>=20
>> Ok we have changed it to:
>>=20
>> If Authenticated Encryption with Associated Data (AEAD) is used (leaf =
esp-algorithms/encryption/algorithm-type)
>> this flag MUST be false."
>>=20
>>> And is it possible to make that a YANG 'must' statement - looking at =
the IKEv2 registries it is not obvious which are AEAD so that might be =
more complexity than it is worth.
>>> 'only available on linux kernels' Um implementation detail, you may =
get asked to remove that altogether or at least to a Informative =
Appendix - I would leave it in for now.
>>=20
>> Ok.
>>=20
>>> 'import ietf-i2nsf-ikec' the reference needs to be to a RFC and if =
it is not yet an RFC then RFC XXXX <title> in both Appendix B and C
>>=20
>> Yes, we have changed that to:
>>=20
>> RFC XXXX: Software-Defined Networking
>>                (SDN)-based IPsec Flow Protection.
>>=20
>>> leaf-list pfs-groups could do with a reference - Transform Type 4?
>>=20
>> The leaf list is referring to type pfs-group and we have now
>>=20
>> typedef pfs-group {
>>             type uint16;
>>             description
>>                 "DH groups for IKE and IPsec SA rekey.";
>>             reference
>>                 "IANA; Internet Key Exchange V2 (IKEv2) Parameters;
>> 				Transform Atribute Types; Transform Type =
4 -
>>                 Diffie-Hellman Group Transform IDs.
>> 				Section 3.3.2 in RFC 7296.";
>>         }
>>=20
>>=20
>>>=20
>>> I am still working my way through the YANG so may have some more =
comments tomorrow.
>>=20
>> Ok, do not worry we will work in -12 with these comments so far to =
have a quick response. We can prepare a another version later with the =
rest of them.
>>=20
>> Thank you very much for your effort.
>>>=20
>>> Tom Petch
>>>=20
>>>=20
>>>=20
>>>=20
>>>=20
>>>=20
>>>=20
>>>=20
>>>=20
>>>=20
>>>=20
>>>=20
>>>=20
>>>=20
>>>> We have realized that we missed to change this, even though we =
discussed it. We will change it right away in the following way (bold):
>>>>=20
>>>> case rfc822-address-string {
>>>>      leaf rfc822-address-string {
>>>>           type string;
>>>>           description
>>>>               "Specifies the identity as a
>>>>                fully-qualified RFC5322 email
>>>>                address string. An example is,
>>>>                jsmith@example.com. The string
>>>>                MUST NOT contain any
>>>>                terminators e.g., NULL, CR,
>>>>                etc.).";
>>>>            reference
>>>>                   "RFC 5322.";
>>>>      }
>>>> }
>>>>=20
>>>> Btw, we already used in the past =E2=80=9Ccase =
rfc822-address-string=E2=80=9D and =E2=80=9Cleaf =
rfc822-address-string=E2=80=9D since this is coming from IKEv2 standard. =
Do you think we should change that name as well?
>>>>=20
>>>>=20
>>>>>=20
>>>>> YANG module references IANA Protocol Numbers which is not in the =
I-D references
>>>>=20
>>>> We have included the following reference:
>>>>=20
>>>> [IANA-Protocols-Number]
>>>>               Internet Assigned Numbers Authority (IANA), "Protocol
>>>>               Numbers", January 2020.
>>>>=20
>>>>=20
>>>>>=20
>>>>> s.2 boiler plate is out of date
>>>>=20
>>>> What we see is the I-D has the second choice stated in =
https://www.ietf.org/standards/ids/guidelines/
>>>>=20
>>>> This Internet-Draft is submitted in full conformance with the
>>>>    provisions of BCP 78 and BCP 79.
>>>>=20
>>>>    Internet-Drafts are working documents of the Internet =
Engineering
>>>>    Task Force (IETF).  Note that other groups may also distribute
>>>>    working documents as Internet-Drafts.  The list of current =
Internet-
>>>>    Drafts is at https://datatracker.ietf.org/drafts/current/.
>>>>=20
>>>>    Internet-Drafts are draft documents valid for a maximum of six =
months
>>>>    and may be updated, replaced, or obsoleted by other documents at =
any
>>>>    time.  It is inappropriate to use Internet-Drafts as reference
>>>>    material or to cite them other than as "work in progress."
>>>>=20
>>>> Could you refer what is out of date?
>>>>=20
>>>>>=20
>>>>> XXXX is standing in for more than one RFC
>>>>=20
>>>> Yes, XXXX has been used because we do not know the future number =
assigned to our I-D.
>>>>=20
>>>> Also we realized we also included this to refer to crypto-types I-D =
but this has been solved now in a new version -12 that we are preparing =
to include your comments. We noticed we can replace the type of rw =
cert-data?, ca-data*, crl-data? for binary without any problem.
>>>>=20
>>>> |           |     +--rw cert-data?        binary
>>>> |           +--rw private-key?            binary
>>>> |           +--rw ca-data*                binary
>>>> |           +--rw crl-data?               binary
>>>>=20
>>>>>=20
>>>>> but the show stopper that makes a proper review of this too costly =
is the references.  Those to IANA of which there are several I want to =
pursue.  The I-D reference is to IKEv2 parameters. Sadly, this is a =
three tier structure and noone agrees on what to call the third tier so =
I will call it tier3 here.  Top level is Group, as per RFC8126, second =
level is Registry.  The I-D reference is to the Group only which is fine =
if the actual reference then specifies the Registry and Tier3 but they =
never do, usually just Tier3 e.g. Transform Type 3 which makes for a lot =
of work for the reader, too much for this one.  You have to go hunting =
in all the second level Registry until you can find a match for the =
Tier3 identifier. And there are no URL.  If you want an example that I =
find easy to use, go look at RFC8407 (as usual).
>>>>=20
>>>> You=E2=80=99re right. Could you point the exact part at RFC 8407 =
with that example? We would really appreciate it.
>>>>=20
>>>> On the other hand, would it be enough to include the URL for =
Transform Type 3 =
https://www.iana.org/assignments/ikev2-parameters/ikev2-parameters.xhtml#i=
kev2-parameters-7 ?
>>>>=20
>>>> (Same for Transform Type 1, Transform Type 4)
>>>>=20
>>>>>=20
>>>>> The reference for import of i2nsf-ikec gives a YANG module name; =
this needs to be the name of the RFC to be
>>>>=20
>>>> Fixed.
>>>>=20
>>>> import ietf-i2nsf-ikec {
>>>>             prefix nsfikec;
>>>>             reference
>>>>                 "RFC XXXX: Software-Defined Networking
>>>>                (SDN)-based IPsec Flow Protection.";
>>>> }
>>>>=20
>>>> We still use XXXX because we do not know the number assigned to the =
RFC to be.
>>>>=20
>>>>>=20
>>>>> The example IPv6 address in the YANG module has :0:0: which is =
usually just ::
>>>>=20
>>>> Fixed.
>>>>=20
>>>> If you have any further comments, please let us know so we can =
include them in -12
>>>>=20
>>>> Best Regards.
>>>>>=20
>>>>> And I have some way to go still.
>>>>>=20
>>>>> Tom Petch
>>>>>=20
>>>>> On 22/10/2020 18:39, Rafa Marin-Lopez wrote:
>>>>>> Dear all:
>>>>>>=20
>>>>>> After receiving a suggestion to make things clearer in the =
feature ikeless-notification description, we have just uploaded a new =
version -11 with a minor change to add the following text:
>>>>>>=20
>>>>>> feature ikeless-notification {
>>>>>>             description
>>>>>>                 "This feature indicates that the server supports
>>>>>>                 generating notifications in the ikeless module.
>>>>>>=20
>>>>>>                 To ensure broader applicability of this module,
>>>>>>                 the notifications are marked as a feature.
>>>>>>                 For the implementation of ikeless case,
>>>>>>                 the NSF is expected to implement this
>>>>>>                 feature.";
>>>>>>         }
>>>>>>=20
>>>>>> Best Regards.
>>>>>>=20
>>>>>>> Inicio del mensaje reenviado:
>>>>>>>=20
>>>>>>> De: internet-drafts@ietf.org
>>>>>>> Asunto: New Version Notification for =
draft-ietf-i2nsf-sdn-ipsec-flow-protection-11.txt
>>>>>>> Fecha: 22 de octubre de 2020, 15:32:50 CEST
>>>>>>> Para: "Fernando Pereniguez-Garcia" =
<fernando.pereniguez@cud.upct.es>, "Rafael Lopez" <rafa@um.es>, "Gabriel =
Lopez-Millan" <gabilm@um.es>, "Rafa Marin-Lopez" <rafa@um.es>
>>>>>>>=20
>>>>>>>=20
>>>>>>> A new version of I-D, =
draft-ietf-i2nsf-sdn-ipsec-flow-protection-11.txt
>>>>>>> has been successfully submitted by Rafa Marin-Lopez and posted =
to the
>>>>>>> IETF repository.
>>>>>>>=20
>>>>>>> Name:		draft-ietf-i2nsf-sdn-ipsec-flow-protection
>>>>>>> Revision:	11
>>>>>>> Title:		Software-Defined Networking (SDN)-based IPsec =
Flow Protection
>>>>>>> Document date:	2020-10-22
>>>>>>> Group:		i2nsf
>>>>>>> Pages:		92
>>>>>>> URL:            =
https://www.ietf.org/archive/id/draft-ietf-i2nsf-sdn-ipsec-flow-protection=
-11.txt
>>>>>>> Status:         =
https://datatracker.ietf.org/doc/draft-ietf-i2nsf-sdn-ipsec-flow-protectio=
n/
>>>>>>> Htmlized:       =
https://datatracker.ietf.org/doc/html/draft-ietf-i2nsf-sdn-ipsec-flow-prot=
ection
>>>>>>> Htmlized:       =
https://tools.ietf.org/html/draft-ietf-i2nsf-sdn-ipsec-flow-protection-11
>>>>>>> Diff:           =
https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-i2nsf-sdn-ipsec-flow-protec=
tion-11
>>>>>>>=20
>>>>>>> Abstract:
>>>>>>>   This document describes how to provide IPsec-based flow =
protection
>>>>>>>   (integrity and confidentiality) by means of an Interface to =
Network
>>>>>>>   Security Function (I2NSF) controller.  It considers two main =
well-
>>>>>>>   known scenarios in IPsec: (i) gateway-to-gateway and (ii) =
host-to-
>>>>>>>   host.  The service described in this document allows the
>>>>>>>   configuration and monitoring of IPsec Security Associations =
(SAs)
>>>>>>>   from a I2NSF Controller to one or several flow-based Network =
Security
>>>>>>>   Functions (NSFs) that rely on IPsec to protect data traffic.
>>>>>>>=20
>>>>>>>   The document focuses on the I2NSF NSF-facing interface by =
providing
>>>>>>>   YANG data models for configuring the IPsec databases (SPD, =
SAD, PAD)
>>>>>>>   and IKEv2.  This allows IPsec SA establishment with minimal
>>>>>>>   intervention by the network administrator.  It does not define =
any
>>>>>>>   new protocol.
>>>>>>>=20
>>>>>>>=20
>>>>>>>=20
>>>>>>>=20
>>>>>>> Please note that it may take a couple of minutes from the time =
of submission
>>>>>>> until the htmlized version and diff are available at =
tools.ietf.org.
>>>>>>>=20
>>>>>>> The IETF Secretariat
>>>>>>>=20
>>>>>>>=20
>>>>>>=20
>>>>>> -------------------------------------------------------
>>>>>> 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
>>>>>> -------------------------------------------------------
>>>>>>=20
>>>>>>=20
>>>>>>=20
>>>>>>=20
>>>>>>=20
>>>>>>=20
>>>>>>=20
>>>>=20
>>>> -------------------------------------------------------
>>>> 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
>>>> -------------------------------------------------------
>>>>=20
>>>>=20
>>>>=20
>>>>=20
>>>>=20
>>=20
>> -------------------------------------------------------
>> 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
>> -------------------------------------------------------
>>=20
>>=20
>>=20
>>=20
>>=20
>=20
> _______________________________________________
> I2nsf mailing list
> I2nsf@ietf.org
> 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
-------------------------------------------------------





--Apple-Mail=_8D60455B-CB51-4C7A-A113-2FA3F529E451
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: after-white-space;" class=3D"">Hi =
Tom:<div class=3D""><br class=3D""></div><div class=3D"">Thank you very =
much again. See our comments inline:<br class=3D""><div><br =
class=3D""><blockquote type=3D"cite" class=3D""><div class=3D"">El 29 =
oct 2020, a las 18:06, tom petch &lt;<a =
href=3D"mailto:daedulus@btconnect.com" =
class=3D"">daedulus@btconnect.com</a>&gt; escribi=C3=B3:</div><br =
class=3D"Apple-interchange-newline"><div class=3D""><div class=3D"">Back =
to routine comments on this I-D; I don't think that any of my earlier =
ones are unresolved.<br class=3D""><br class=3D"">On 29/10/2020 11:23, =
Rafa Marin-Lopez wrote:<br class=3D""><blockquote type=3D"cite" =
class=3D"">Hi Tom:<br class=3D""><br class=3D""><blockquote type=3D"cite" =
class=3D"">El 28 oct 2020, a las 19:02, tom petch &lt;<a =
href=3D"mailto:daedulus@btconnect.com" =
class=3D"">daedulus@btconnect.com</a>&gt; escribi=C3=B3:<br class=3D""><br=
 class=3D"">On 28/10/2020 10:42, Rafa Marin-Lopez wrote:<br =
class=3D""><blockquote type=3D"cite" class=3D"">Hi Tom:<br class=3D""><br =
class=3D"">Thank you very much for your insight. It is very helpful. =
Please see our comments/questions inline.<br class=3D""><br =
class=3D""><blockquote type=3D"cite" class=3D"">El 27 oct 2020, a las =
13:42, tom petch &lt;<a href=3D"mailto:daedulus@btconnect.com" =
class=3D"">daedulus@btconnect.com</a>&gt; escribi=C3=B3:<br class=3D""><br=
 class=3D"">I think that the IESG will find a number of problems with =
this I-D.<br class=3D""><br class=3D"">YANG module references RFC822 =
which is several years out of date<br =
class=3D""></blockquote></blockquote></blockquote></blockquote><br =
class=3D"">Rafa<br class=3D""><br class=3D"">Several YANG leaf are in =
seconds, eight I think, but none use the YANG<br class=3D"">units =
seconds;<br class=3D"">statement. &nbsp;I suggest adding it.<br =
class=3D""></div></div></blockquote><div><br class=3D""></div>Added. =
They are seven.<br class=3D""><blockquote type=3D"cite" class=3D""><div =
class=3D""><div class=3D""><br class=3D"">typedef ipsec-spd-action<br =
class=3D"">capitalises the actions as does RFC4301 but later uses of =
this have lower case actions; probably ok as it is<br =
class=3D""></div></div></blockquote><div><br class=3D""></div>Ok.<br =
class=3D""><blockquote type=3D"cite" class=3D""><div class=3D""><div =
class=3D""><br class=3D"">protocol number appears in several places but =
technically, IPv6, which we must all love and promote, has 'next header' =
instead. &nbsp;Probably worth a mention at least once in the YANG =
module<br class=3D""></div></div></blockquote><div><br class=3D""></div>We=
 have included this note:</div><div><br class=3D""></div><div><br =
class=3D""></div><div><div>NOTE: In case of IPv6, the protocol in the IP =
packet payload is</div><div>specified in the Next Header field of the =
IPv6&nbsp;</div><div>packet.";</div></div><div><blockquote type=3D"cite" =
class=3D""><div class=3D""><div class=3D""><br class=3D"">On the start =
&gt;=3D end, I was looking at nat-yang and it has<br class=3D""> must ". =
&gt;=3D ../start-port-number"<br class=3D"">which is the sort of YANG =
constraint I had in mind<br class=3D""></div></div></blockquote><div><br =
class=3D""></div>Done.&nbsp;</div><div><br class=3D""></div><div>must '. =
&gt;=3D ../start=E2=80=99</div><div><br class=3D""></div><div><br =
class=3D""><blockquote type=3D"cite" class=3D""><div class=3D""><div =
class=3D""><br class=3D"">leaf dscp-mapping<br class=3D"">I do not =
understand, a hex string of indeterminate length for DSCP values =
(plural). &nbsp;I expect DSCP to be six bit and values to be a =
leaf-list<br class=3D""></div></div></blockquote><div><br =
class=3D""></div><div>Right. Since we have inet:dscp type , we have used =
that one in a leaf-list as you recommend.</div><div><br =
class=3D""></div><div><div><b class=3D"">leaf-list</b> dscp-mapping =
{&nbsp;</div><div>&nbsp; &nbsp; &nbsp; &nbsp;<b class=3D"">type =
inet:dscp;</b></div><div>&nbsp; &nbsp; &nbsp; &nbsp;default =
0;</div><div>&nbsp; &nbsp; &nbsp; =
&nbsp;description&nbsp;</div><div>&nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;"DSCP values allowed for packets carried over</div><div>&nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp;this IPsec SA.";&nbsp;</div><div>&nbsp; =
&nbsp; &nbsp; &nbsp;reference</div><div>&nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;"Section 4.4.2.1. in RFC 4301.";</div><div>&nbsp; &nbsp; =
&nbsp;}</div></div><br class=3D""><blockquote type=3D"cite" =
class=3D""><div class=3D""><div class=3D""><br class=3D"">leaf ecn<br =
class=3D"">/Annex C/Appendix C/<br =
class=3D""></div></div></blockquote><div><br class=3D""></div>Fixed.<br =
class=3D""><blockquote type=3D"cite" class=3D""><div class=3D""><div =
class=3D""><br class=3D"">I see that RFC8247 gives AEAD status which is =
a good reference to have except that as my other post today says there =
is no requirement for any future additions to the IANA data to include =
this information; IANA for IKEv2 needs updating iun a separate I-D!<br =
class=3D""><br class=3D"">leaf mask<br class=3D"">hex-string with no =
length specified<br class=3D""></div></div></blockquote><div><br =
class=3D""></div>Since this masked is after all 32-bits mask we have =
used uint32 instead.<br class=3D""><blockquote type=3D"cite" =
class=3D""><div class=3D""><div class=3D""><br class=3D"">leaf =
ds-algorithm<br class=3D"">default 1<br class=3D"">which I think is RSA; =
worth stating as it might raise some AD eyebrows<br =
class=3D""></div></div></blockquote><div><br class=3D""></div>Clarified =
in the description.<br class=3D""><blockquote type=3D"cite" =
class=3D""><div class=3D""><div class=3D""><br class=3D"">pfs-groups<br =
class=3D"">/it is required perfect forward secrecy/perfect forward =
secrecy is required/<br class=3D""></div></div></blockquote><div><br =
class=3D""></div><div>Fixed.</div><br class=3D""><blockquote type=3D"cite"=
 class=3D""><div class=3D""><div class=3D"">and a reference to Transform =
Type 4?<br class=3D""></div></div></blockquote><div><br =
class=3D""></div>As we mention earlier, this pfs-groups used the type =
pfs-group, which includes the reference to Transform Type 4.<br =
class=3D""><blockquote type=3D"cite" class=3D""><div class=3D""><div =
class=3D""><br class=3D"">leaf ext-seq-num<br class=3D"">/FALSE/false/ =
or /False/?<br class=3D""><br class=3D"">leaf encryption-algorithm =
(twice, in separate containers)<br =
class=3D""></div></div></blockquote><div><br =
class=3D""></div><div>Mmmmm=E2=80=A6 we only see in one place.</div><br =
class=3D""><blockquote type=3D"cite" class=3D""><div class=3D""><div =
class=3D"">/the integrity leaf/ the integrity-algorithm leaf/<br =
class=3D""></div></div></blockquote><div><br class=3D""></div>Fixed.<br =
class=3D""><blockquote type=3D"cite" class=3D""><div class=3D""><div =
class=3D""><br class=3D"">I have yet to look at the text or the =
examples, probably next week.<br =
class=3D""></div></div></blockquote><div><br class=3D""></div>Thank you =
very much. We are going to post -12 with all these comments and the =
previous ones so far. If there are pending comments we can prepare -13 =
right away.</div><div><br class=3D""></div><div>Best Regards.<br =
class=3D""><blockquote type=3D"cite" class=3D""><div class=3D""><div =
class=3D""><br class=3D"">Tom Petch<br class=3D""><br class=3D""><br =
class=3D""><br class=3D""><br class=3D""><br class=3D""><br class=3D""><br=
 class=3D""><br class=3D""><br class=3D""><br class=3D""><blockquote =
type=3D"cite" class=3D""><blockquote type=3D"cite" class=3D""><br =
class=3D"">On boiler plate, I mean the reference to RFC2119 which now =
must use the language from RFC8174 in the body of the I-D; sorry for the =
confusion.<br class=3D""></blockquote><br class=3D"">Ah ok. I guess you =
are referring to change that paragraph with this:<br class=3D""><br =
class=3D""><br class=3D"">The key words "MUST", "MUST NOT", =
"REQUIRED",<br class=3D"">"SHALL", "SHALL NOT", "SHOULD", "SHOULD =
NOT",<br class=3D"">"RECOMMENDED", "NOT RECOMMENDED", "MAY", and<br =
class=3D"">"OPTIONAL" in this document are to be interpreted<br =
class=3D"">as described in BCP 14 RFC2119 RFC8174 when,<br class=3D"">and =
only when, they appear in all capitals,<br class=3D"">as shown here.<br =
class=3D""><br class=3D""><blockquote type=3D"cite" class=3D""><br =
class=3D"">On XXXX, you have XXXX standing in for more than one =
RFC-to-be which confuses. &nbsp;The convention is to use XXXX for this =
I-D and then AAAA BBBB etc for any others such as the netconf I-D in =
this instance.<br class=3D""></blockquote><br class=3D"">Ah ok. In any =
case, we have now only XXXX for our RFC-to-be so problem fixed.<br =
class=3D""><blockquote type=3D"cite" class=3D""><br class=3D"">Two big =
issues, for me (perhaps not for others). &nbsp;The convention with YANG =
is for each successive line to be indented two characters, you have =
four, which creates a lot of white space and pushes the text to the =
right hand margin. &nbsp;I think that two characters is the default when =
you use pyang to format a YANG module.<br class=3D""></blockquote><br =
class=3D"">We can try to reduce it to two characters.<br class=3D""><br =
class=3D""><blockquote type=3D"cite" class=3D""><br class=3D"">And =
references. &nbsp;I have had to work harder than I want to to make sense =
of the IANA references. &nbsp;I think you should have five separate =
references in the I-D for IANA for<br class=3D"">Transform Type 1<br =
class=3D"">Transform Type 3<br class=3D"">Transform Type 4<br =
class=3D"">Authentication Method<br class=3D"">Protocol Numbers<br =
class=3D"">and each reference in the I-D should have a URL pointing to =
the specific section of IANA web site.<br class=3D""></blockquote><br =
class=3D"">Ok, good. This follows what we thought.<br class=3D""><br =
class=3D""><blockquote type=3D"cite" class=3D"">In the YANG, it is =
harder to know what to do. &nbsp;Those first three references are in the =
third tier i.e.<br class=3D"">Group - Internet Key Exchange V2 (IKEv2) =
Parameters<br class=3D"">Registry &nbsp;-Transform Attribute Types<br =
class=3D"">and then Type 1, 3, 4 as the third tier as I am calling it<br =
class=3D"">and I think that every reference in the YANG should give me =
all three tiers after IANA in that order perhaps<br class=3D"">IANA; =
IKEv2 Parameters; Transform Atribute Types; Transform Type 1<br =
class=3D""></blockquote><br class=3D"">Great. We also considered this as =
a possible solution after sending our e-mail. Let=E2=80=99s do it.<br =
class=3D""><br class=3D""><blockquote type=3D"cite" class=3D"">If the =
syntax needs tweeking, then the RFC Editor will do a good job of that =
but at present the references are inconsistent in which elements are =
specified in what order and that is something the RFC Editor probably =
cannot cope with.<br class=3D"">Authentication Method is a registry so =
that just needs Group name and Registry name after IANA.<br =
class=3D""></blockquote><br class=3D"">Ok, good.<br class=3D""><blockquote=
 type=3D"cite" class=3D""><br class=3D"">Some minor glitches.<br =
class=3D"">I-D appears twice in the body of the I-D - perhaps document =
or memo.<br class=3D""></blockquote><br class=3D"">Ok.<br class=3D""><br =
class=3D""><blockquote type=3D"cite" class=3D"">objetives/objectives/<br =
class=3D""></blockquote><br class=3D"">Fixed.<br class=3D""><blockquote =
type=3D"cite" class=3D"">end port number perhaps /must/MUST/<br =
class=3D""></blockquote><br class=3D""><blockquote type=3D"cite" =
class=3D"">and YANG is very good at including such checks with a must =
....<br class=3D"">'If AEAD is used .. where? this occurs in several =
places and I think that you need to specify the leaf where AEAD will be =
specified or implied.<br class=3D""></blockquote><br class=3D"">Ok we =
have changed it to:<br class=3D""><br class=3D"">If Authenticated =
Encryption with Associated Data (AEAD) is used (leaf =
esp-algorithms/encryption/algorithm-type)<br class=3D"">this flag MUST =
be false."<br class=3D""><br class=3D""><blockquote type=3D"cite" =
class=3D"">And is it possible to make that a YANG 'must' statement - =
looking at the IKEv2 registries it is not obvious which are AEAD so that =
might be more complexity than it is worth.<br class=3D"">'only available =
on linux kernels' Um implementation detail, you may get asked to remove =
that altogether or at least to a Informative Appendix - I would leave it =
in for now.<br class=3D""></blockquote><br class=3D"">Ok.<br =
class=3D""><br class=3D""><blockquote type=3D"cite" class=3D"">'import =
ietf-i2nsf-ikec' the reference needs to be to a RFC and if it is not yet =
an RFC then RFC XXXX &lt;title&gt; in both Appendix B and C<br =
class=3D""></blockquote><br class=3D"">Yes, we have changed that to:<br =
class=3D""><br class=3D"">RFC XXXX: Software-Defined Networking<br =
class=3D""> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;(SDN)-based IPsec Flow Protection.<br class=3D""><br =
class=3D""><blockquote type=3D"cite" class=3D"">leaf-list pfs-groups =
could do with a reference - Transform Type 4?<br =
class=3D""></blockquote><br class=3D"">The leaf list is referring to =
type pfs-group and we have now<br class=3D""><br class=3D"">typedef =
pfs-group {<br class=3D""> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;ty=
pe uint16;<br class=3D""> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;de=
scription<br class=3D""> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;"DH groups for IKE and IPsec SA rekey.";<br =
class=3D""> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;re=
ference<br class=3D""> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;"IANA; Internet Key Exchange V2 (IKEv2) =
Parameters;<br class=3D""><span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</span><span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</span><span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</span><span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</span>Transform Atribute Types; =
Transform Type 4 -<br class=3D""> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;Diffie-Hellman Group Transform IDs.<br =
class=3D""><span class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</span><span class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</span><span class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</span><span class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</span>Section 3.3.2 in RFC 7296.";<br class=3D""> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;}<br class=3D""><br =
class=3D""><br class=3D""><blockquote type=3D"cite" class=3D""><br =
class=3D"">I am still working my way through the YANG so may have some =
more comments tomorrow.<br class=3D""></blockquote><br class=3D"">Ok, do =
not worry we will work in -12 with these comments so far to have a quick =
response. We can prepare a another version later with the rest of =
them.<br class=3D""><br class=3D"">Thank you very much for your =
effort.<br class=3D""><blockquote type=3D"cite" class=3D""><br =
class=3D"">Tom Petch<br class=3D""><br class=3D""><br class=3D""><br =
class=3D""><br class=3D""><br class=3D""><br class=3D""><br class=3D""><br=
 class=3D""><br class=3D""><br class=3D""><br class=3D""><br =
class=3D""><br class=3D""><br class=3D""><blockquote type=3D"cite" =
class=3D"">We have realized that we missed to change this, even though =
we discussed it. We will change it right away in the following way =
(bold):<br class=3D""><br class=3D"">case rfc822-address-string {<br =
class=3D""> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;leaf rfc822-address-string =
{<br class=3D""> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;type =
string;<br class=3D""> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;description<br=
 class=3D""> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;"Specifies the identity as a<br class=3D""> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;fully-qualified RFC5322 email<br class=3D""> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;address string. An example is,<br class=3D""> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;<a href=3D"mailto:jsmith@example.com" =
class=3D"">jsmith@example.com</a>. The string<br class=3D""> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;MUST NOT contain any<br class=3D""> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;terminators e.g., NULL, CR,<br class=3D""> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;etc.).";<br class=3D""> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;referenc=
e<br class=3D""> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;"RFC 5322.";<br class=3D""> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;}<br class=3D"">}<br class=3D""><br =
class=3D"">Btw, we already used in the past =E2=80=9Ccase =
rfc822-address-string=E2=80=9D and =E2=80=9Cleaf =
rfc822-address-string=E2=80=9D since this is coming from IKEv2 standard. =
Do you think we should change that name as well?<br class=3D""><br =
class=3D""><br class=3D""><blockquote type=3D"cite" class=3D""><br =
class=3D"">YANG module references IANA Protocol Numbers which is not in =
the I-D references<br class=3D""></blockquote><br class=3D"">We have =
included the following reference:<br class=3D""><br =
class=3D"">[IANA-Protocols-Number]<br class=3D""> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;Internet Assigned Numbers Authority (IANA), "Protocol<br =
class=3D""> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;Numbers", January 2020.<br class=3D""><br class=3D""><br =
class=3D""><blockquote type=3D"cite" class=3D""><br class=3D"">s.2 =
boiler plate is out of date<br class=3D""></blockquote><br class=3D"">What=
 we see is the I-D has the second choice stated in <a =
href=3D"https://www.ietf.org/standards/ids/guidelines/" =
class=3D"">https://www.ietf.org/standards/ids/guidelines/</a><br =
class=3D""><br class=3D"">This Internet-Draft is submitted in full =
conformance with the<br class=3D""> &nbsp;&nbsp;&nbsp;provisions of BCP =
78 and BCP 79.<br class=3D""><br class=3D""> =
&nbsp;&nbsp;&nbsp;Internet-Drafts are working documents of the Internet =
Engineering<br class=3D""> &nbsp;&nbsp;&nbsp;Task Force (IETF). =
&nbsp;Note that other groups may also distribute<br class=3D""> =
&nbsp;&nbsp;&nbsp;working documents as Internet-Drafts. &nbsp;The list =
of current Internet-<br class=3D""> &nbsp;&nbsp;&nbsp;Drafts is at <a =
href=3D"https://datatracker.ietf.org/drafts/current/" =
class=3D"">https://datatracker.ietf.org/drafts/current/</a>.<br =
class=3D""><br class=3D""> &nbsp;&nbsp;&nbsp;Internet-Drafts are draft =
documents valid for a maximum of six months<br class=3D""> =
&nbsp;&nbsp;&nbsp;and may be updated, replaced, or obsoleted by other =
documents at any<br class=3D""> &nbsp;&nbsp;&nbsp;time. &nbsp;It is =
inappropriate to use Internet-Drafts as reference<br class=3D""> =
&nbsp;&nbsp;&nbsp;material or to cite them other than as "work in =
progress."<br class=3D""><br class=3D"">Could you refer what is out of =
date?<br class=3D""><br class=3D""><blockquote type=3D"cite" =
class=3D""><br class=3D"">XXXX is standing in for more than one RFC<br =
class=3D""></blockquote><br class=3D"">Yes, XXXX has been used because =
we do not know the future number assigned to our I-D.<br class=3D""><br =
class=3D"">Also we realized we also included this to refer to =
crypto-types I-D but this has been solved now in a new version -12 that =
we are preparing to include your comments. We noticed we can replace the =
type of rw cert-data?, ca-data*, crl-data? for binary without any =
problem.<br class=3D""><br class=3D"">| =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;| =
&nbsp;&nbsp;&nbsp;&nbsp;+--rw cert-data? =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;binary<br class=3D"">| =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;+--rw =
private-key? =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;binary<b=
r class=3D"">| =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;+--rw =
ca-data* =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;binary<br class=3D"">| =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;+--rw =
crl-data? =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;binary<br class=3D""><br class=3D""><blockquote type=3D"cite" =
class=3D""><br class=3D"">but the show stopper that makes a proper =
review of this too costly is the references. &nbsp;Those to IANA of =
which there are several I want to pursue. &nbsp;The I-D reference is to =
IKEv2 parameters. Sadly, this is a three tier structure and noone agrees =
on what to call the third tier so I will call it tier3 here. &nbsp;Top =
level is Group, as per RFC8126, second level is Registry. &nbsp;The I-D =
reference is to the Group only which is fine if the actual reference =
then specifies the Registry and Tier3 but they never do, usually just =
Tier3 e.g. Transform Type 3 which makes for a lot of work for the =
reader, too much for this one. &nbsp;You have to go hunting in all the =
second level Registry until you can find a match for the Tier3 =
identifier. And there are no URL. &nbsp;If you want an example that I =
find easy to use, go look at RFC8407 (as usual).<br =
class=3D""></blockquote><br class=3D"">You=E2=80=99re right. Could you =
point the exact part at RFC 8407 with that example? We would really =
appreciate it.<br class=3D""><br class=3D"">On the other hand, would it =
be enough to include the URL for Transform Type 3 <a =
href=3D"https://www.iana.org/assignments/ikev2-parameters/ikev2-parameters=
.xhtml#ikev2-parameters-7" =
class=3D"">https://www.iana.org/assignments/ikev2-parameters/ikev2-paramet=
ers.xhtml#ikev2-parameters-7</a> ?<br class=3D""><br class=3D"">(Same =
for Transform Type 1, Transform Type 4)<br class=3D""><br =
class=3D""><blockquote type=3D"cite" class=3D""><br class=3D"">The =
reference for import of i2nsf-ikec gives a YANG module name; this needs =
to be the name of the RFC to be<br class=3D""></blockquote><br =
class=3D"">Fixed.<br class=3D""><br class=3D"">import ietf-i2nsf-ikec =
{<br class=3D""> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;pr=
efix nsfikec;<br class=3D""> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;re=
ference<br class=3D""> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;"RFC XXXX: Software-Defined Networking<br =
class=3D""> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;(SDN)-based IPsec Flow Protection.";<br class=3D"">}<br =
class=3D""><br class=3D"">We still use XXXX because we do not know the =
number assigned to the RFC to be.<br class=3D""><br class=3D""><blockquote=
 type=3D"cite" class=3D""><br class=3D"">The example IPv6 address in the =
YANG module has :0:0: which is usually just ::<br =
class=3D""></blockquote><br class=3D"">Fixed.<br class=3D""><br =
class=3D"">If you have any further comments, please let us know so we =
can include them in -12<br class=3D""><br class=3D"">Best Regards.<br =
class=3D""><blockquote type=3D"cite" class=3D""><br class=3D"">And I =
have some way to go still.<br class=3D""><br class=3D"">Tom Petch<br =
class=3D""><br class=3D"">On 22/10/2020 18:39, Rafa Marin-Lopez =
wrote:<br class=3D""><blockquote type=3D"cite" class=3D"">Dear all:<br =
class=3D""><br class=3D"">After receiving a suggestion to make things =
clearer in the feature ikeless-notification description, we have just =
uploaded a new version -11 with a minor change to add the following =
text:<br class=3D""><br class=3D"">feature ikeless-notification {<br =
class=3D""> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;de=
scription<br class=3D""> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;"This feature indicates that the server =
supports<br class=3D""> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;generating notifications in the ikeless module.<br =
class=3D""><br class=3D""> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;To ensure broader applicability of this module,<br =
class=3D""> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;the notifications are marked as a feature.<br =
class=3D""> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;For the implementation of ikeless case,<br =
class=3D""> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;the NSF is expected to implement this<br class=3D"">=
 =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;feature.";<br class=3D""> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;}<br class=3D""><br =
class=3D"">Best Regards.<br class=3D""><br class=3D""><blockquote =
type=3D"cite" class=3D"">Inicio del mensaje reenviado:<br class=3D""><br =
class=3D"">De: <a href=3D"mailto:internet-drafts@ietf.org" =
class=3D"">internet-drafts@ietf.org</a><br class=3D"">Asunto: New =
Version Notification for =
draft-ietf-i2nsf-sdn-ipsec-flow-protection-11.txt<br class=3D"">Fecha: =
22 de octubre de 2020, 15:32:50 CEST<br class=3D"">Para: "Fernando =
Pereniguez-Garcia" &lt;<a href=3D"mailto:fernando.pereniguez@cud.upct.es" =
class=3D"">fernando.pereniguez@cud.upct.es</a>&gt;, "Rafael Lopez" =
&lt;<a href=3D"mailto:rafa@um.es" class=3D"">rafa@um.es</a>&gt;, =
"Gabriel Lopez-Millan" &lt;<a href=3D"mailto:gabilm@um.es" =
class=3D"">gabilm@um.es</a>&gt;, "Rafa Marin-Lopez" &lt;<a =
href=3D"mailto:rafa@um.es" class=3D"">rafa@um.es</a>&gt;<br class=3D""><br=
 class=3D""><br class=3D"">A new version of I-D, =
draft-ietf-i2nsf-sdn-ipsec-flow-protection-11.txt<br class=3D"">has been =
successfully submitted by Rafa Marin-Lopez and posted to the<br =
class=3D"">IETF repository.<br class=3D""><br class=3D"">Name:<span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</span><span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</span>draft-ietf-i2nsf-sdn-ipsec-flow-protection<br =
class=3D"">Revision:<span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</span>11<br class=3D"">Title:<span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</span><span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</span>Software-Defined Networking (SDN)-based IPsec Flow Protection<br =
class=3D"">Document date:<span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</span>2020-10-22<br =
class=3D"">Group:<span class=3D"Apple-tab-span" style=3D"white-space:pre">=
	</span><span class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</span>i2nsf<br class=3D"">Pages:<span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</span><span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</span>92<br class=3D"">URL: =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a =
href=3D"https://www.ietf.org/archive/id/draft-ietf-i2nsf-sdn-ipsec-flow-pr=
otection-11.txt" =
class=3D"">https://www.ietf.org/archive/id/draft-ietf-i2nsf-sdn-ipsec-flow=
-protection-11.txt</a><br class=3D"">Status: =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a =
href=3D"https://datatracker.ietf.org/doc/draft-ietf-i2nsf-sdn-ipsec-flow-p=
rotection/" =
class=3D"">https://datatracker.ietf.org/doc/draft-ietf-i2nsf-sdn-ipsec-flo=
w-protection/</a><br class=3D"">Htmlized: =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a =
href=3D"https://datatracker.ietf.org/doc/html/draft-ietf-i2nsf-sdn-ipsec-f=
low-protection" =
class=3D"">https://datatracker.ietf.org/doc/html/draft-ietf-i2nsf-sdn-ipse=
c-flow-protection</a><br class=3D"">Htmlized: =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a =
href=3D"https://tools.ietf.org/html/draft-ietf-i2nsf-sdn-ipsec-flow-protec=
tion-11" =
class=3D"">https://tools.ietf.org/html/draft-ietf-i2nsf-sdn-ipsec-flow-pro=
tection-11</a><br class=3D"">Diff: =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a =
href=3D"https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-i2nsf-sdn-ipsec-flo=
w-protection-11" =
class=3D"">https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-i2nsf-sdn-ipsec-=
flow-protection-11</a><br class=3D""><br class=3D"">Abstract:<br =
class=3D""> &nbsp;&nbsp;This document describes how to provide =
IPsec-based flow protection<br class=3D""> &nbsp;&nbsp;(integrity and =
confidentiality) by means of an Interface to Network<br class=3D""> =
&nbsp;&nbsp;Security Function (I2NSF) controller. &nbsp;It considers two =
main well-<br class=3D""> &nbsp;&nbsp;known scenarios in IPsec: (i) =
gateway-to-gateway and (ii) host-to-<br class=3D""> &nbsp;&nbsp;host. =
&nbsp;The service described in this document allows the<br class=3D""> =
&nbsp;&nbsp;configuration and monitoring of IPsec Security Associations =
(SAs)<br class=3D""> &nbsp;&nbsp;from a I2NSF Controller to one or =
several flow-based Network Security<br class=3D""> &nbsp;&nbsp;Functions =
(NSFs) that rely on IPsec to protect data traffic.<br class=3D""><br =
class=3D""> &nbsp;&nbsp;The document focuses on the I2NSF NSF-facing =
interface by providing<br class=3D""> &nbsp;&nbsp;YANG data models for =
configuring the IPsec databases (SPD, SAD, PAD)<br class=3D""> =
&nbsp;&nbsp;and IKEv2. &nbsp;This allows IPsec SA establishment with =
minimal<br class=3D""> &nbsp;&nbsp;intervention by the network =
administrator. &nbsp;It does not define any<br class=3D""> =
&nbsp;&nbsp;new protocol.<br class=3D""><br class=3D""><br class=3D""><br =
class=3D""><br class=3D"">Please note that it may take a couple of =
minutes from the time of submission<br class=3D"">until the htmlized =
version and diff are available at <a href=3D"http://tools.ietf.org" =
class=3D"">tools.ietf.org</a>.<br class=3D""><br class=3D"">The IETF =
Secretariat<br class=3D""><br class=3D""><br class=3D""></blockquote><br =
class=3D"">-------------------------------------------------------<br =
class=3D"">Rafa Marin-Lopez, PhD<br class=3D"">Dept. Information and =
Communications Engineering (DIIC)<br class=3D"">Faculty of Computer =
Science-University of Murcia<br class=3D"">30100 Murcia - Spain<br =
class=3D"">Telf: +34868888501 Fax: +34868884151 <a =
href=3D"mailto:rafa@um.es" class=3D"">e-mail: rafa@um.es</a><br =
class=3D"">-------------------------------------------------------<br =
class=3D""><br class=3D""><br class=3D""><br class=3D""><br class=3D""><br=
 class=3D""><br class=3D""><br class=3D""></blockquote></blockquote><br =
class=3D"">-------------------------------------------------------<br =
class=3D"">Rafa Marin-Lopez, PhD<br class=3D"">Dept. Information and =
Communications Engineering (DIIC)<br class=3D"">Faculty of Computer =
Science-University of Murcia<br class=3D"">30100 Murcia - Spain<br =
class=3D"">Telf: +34868888501 Fax: +34868884151 <a =
href=3D"mailto:rafa@um.es" class=3D"">e-mail: rafa@um.es</a><br =
class=3D"">-------------------------------------------------------<br =
class=3D""><br class=3D""><br class=3D""><br class=3D""><br class=3D""><br=
 class=3D""></blockquote></blockquote><br =
class=3D"">-------------------------------------------------------<br =
class=3D"">Rafa Marin-Lopez, PhD<br class=3D"">Dept. Information and =
Communications Engineering (DIIC)<br class=3D"">Faculty of Computer =
Science-University of Murcia<br class=3D"">30100 Murcia - Spain<br =
class=3D"">Telf: +34868888501 Fax: +34868884151 <a =
href=3D"mailto:rafa@um.es" class=3D"">e-mail: rafa@um.es</a><br =
class=3D"">-------------------------------------------------------<br =
class=3D""><br class=3D""><br class=3D""><br class=3D""><br class=3D""><br=
 class=3D""></blockquote><br =
class=3D"">_______________________________________________<br =
class=3D"">I2nsf mailing list<br class=3D""><a =
href=3D"mailto:I2nsf@ietf.org" class=3D"">I2nsf@ietf.org</a><br =
class=3D"">https://www.ietf.org/mailman/listinfo/i2nsf<br =
class=3D""></div></div></blockquote></div><br class=3D""><div class=3D"">
<div style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space;" class=3D""><div style=3D"color: =
rgb(0, 0, 0); font-family: Courier; font-size: 16px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
orphans: auto; text-align: start; text-indent: 0px; text-transform: =
none; white-space: normal; widows: auto; word-spacing: 0px; =
-webkit-text-stroke-width: =
0px;">-------------------------------------------------------<br =
class=3D"">Rafa Marin-Lopez, PhD<br class=3D"">Dept. Information =
and&nbsp;Communications&nbsp;Engineering (DIIC)<br class=3D"">Faculty of =
Computer&nbsp;Science-University of&nbsp;Murcia<br class=3D"">30100 =
Murcia - Spain<br class=3D"">Telf: +34868888501 Fax:&nbsp;+34868884151 =
<a href=3D"mailto:rafa@um.es" class=3D"">e-mail:&nbsp;rafa@um.es</a><br =
class=3D"">-------------------------------------------------------</div><d=
iv style=3D"color: rgb(0, 0, 0); font-family: Courier; font-size: 16px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; orphans: auto; text-align: start; text-indent: =
0px; text-transform: none; white-space: normal; widows: auto; =
word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=3D""><br =
class=3D""></div><br class=3D"Apple-interchange-newline"></div><br =
class=3D"Apple-interchange-newline">
</div>
<br class=3D""></div></body></html>=

--Apple-Mail=_8D60455B-CB51-4C7A-A113-2FA3F529E451--


From nobody Fri Oct 30 10:46:16 2020
Return-Path: <internet-drafts@ietf.org>
X-Original-To: i2nsf@ietf.org
Delivered-To: i2nsf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 2EE1E3A1086; Fri, 30 Oct 2020 10:46:12 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
Cc: i2nsf@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 7.21.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: i2nsf@ietf.org
Message-ID: <160407997213.6326.1555001333014301343@ietfa.amsl.com>
Date: Fri, 30 Oct 2020 10:46:12 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2nsf/7fST5TdZsAXB9Ov9BdX2Xpbsmpo>
Subject: [I2nsf] I-D Action: draft-ietf-i2nsf-sdn-ipsec-flow-protection-12.txt
X-BeenThere: i2nsf@ietf.org
X-Mailman-Version: 2.1.29
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, 30 Oct 2020 17:46:12 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Interface to Network Security Functions WG of the IETF.

        Title           : Software-Defined Networking (SDN)-based IPsec Flow Protection
        Authors         : Rafa Marin-Lopez
                          Gabriel Lopez-Millan
                          Fernando Pereniguez-Garcia
	Filename        : draft-ietf-i2nsf-sdn-ipsec-flow-protection-12.txt
	Pages           : 93
	Date            : 2020-10-30

Abstract:
   This document describes how to provide IPsec-based flow protection
   (integrity and confidentiality) by means of an Interface to Network
   Security Function (I2NSF) controller.  It considers two main well-
   known scenarios in IPsec: (i) gateway-to-gateway and (ii) host-to-
   host.  The service described in this document allows the
   configuration and monitoring of IPsec Security Associations (SAs)
   from a I2NSF Controller to one or several flow-based Network Security
   Functions (NSFs) that rely on IPsec to protect data traffic.

   The document focuses on the I2NSF NSF-facing interface by providing
   YANG data models for configuring the IPsec databases (SPD, SAD, PAD)
   and IKEv2.  This allows IPsec SA establishment with minimal
   intervention by the network administrator.  It does not define any
   new protocol.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-i2nsf-sdn-ipsec-flow-protection/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-i2nsf-sdn-ipsec-flow-protection-12
https://datatracker.ietf.org/doc/html/draft-ietf-i2nsf-sdn-ipsec-flow-protection-12

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-i2nsf-sdn-ipsec-flow-protection-12


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/



From nobody Fri Oct 30 12:40:33 2020
Return-Path: <rdd@cert.org>
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 179883A11A9; Fri, 30 Oct 2020 12:40:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level: 
X-Spam-Status: No, score=-2.099 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, 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 (1024-bit key) header.d=cert.org
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 yqFsUPLdWAXP; Fri, 30 Oct 2020 12:40:24 -0700 (PDT)
Received: from veto.sei.cmu.edu (veto.sei.cmu.edu [147.72.252.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 624A83A11B0; Fri, 30 Oct 2020 12:40:23 -0700 (PDT)
Received: from delp.sei.cmu.edu (delp.sei.cmu.edu [10.64.21.31]) by veto.sei.cmu.edu (8.14.7/8.14.7) with ESMTP id 09UJe80Y005018; Fri, 30 Oct 2020 15:40:08 -0400
DKIM-Filter: OpenDKIM Filter v2.11.0 veto.sei.cmu.edu 09UJe80Y005018
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cert.org; s=yc2bmwvrj62m; t=1604086809; bh=UXDd4RoHBYuuWWCfC+/yfzH/Km+xpEg4xIRf0Vs4SPs=; h=From:To:CC:Subject:Date:References:In-Reply-To:From; b=QsQzA/RE1sglvo7WF/J12BFxKDRQFwy+9ztjW3BJfPeD2dOUnhgJ30c59KT0zv6kk I1ks2O6AKrJsfOpnIjtWGaBg6tHRVOATSf0mh1O5746giUOPUFiwCrIrMjBSuv09iF zZyNvO1M165z6fQk1k84pOvOQPOFaj4jvV+8R2rY=
Received: from MORRIS.ad.sei.cmu.edu (morris.ad.sei.cmu.edu [147.72.252.46]) by delp.sei.cmu.edu (8.14.7/8.14.7) with ESMTP id 09UJe4Ev031668; Fri, 30 Oct 2020 15:40:04 -0400
Received: from MORRIS.ad.sei.cmu.edu (147.72.252.46) by MORRIS.ad.sei.cmu.edu (147.72.252.46) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2106.2; Fri, 30 Oct 2020 15:40:04 -0400
Received: from MORRIS.ad.sei.cmu.edu ([fe80::555b:9498:552e:d1bb]) by MORRIS.ad.sei.cmu.edu ([fe80::555b:9498:552e:d1bb%13]) with mapi id 15.01.2106.002; Fri, 30 Oct 2020 15:40:03 -0400
From: Roman Danyliw <rdd@cert.org>
To: tom petch <daedulus@btconnect.com>
CC: "i2nsf@ietf.org" <i2nsf@ietf.org>, Fernando Pereniguez-Garcia <fernando.pereniguez@cud.upct.es>, Gabriel Lopez <gabilm@um.es>, "ynir.ietf@gmail.com" <ynir.ietf@gmail.com>, "last-call@ietf.org" <last-call@ietf.org>, "ipsec@ietf.org" <ipsec@ietf.org>, Rafa Marin-Lopez <rafa@um.es>
Thread-Topic: [Last-Call] New Version Notification for draft-ietf-i2nsf-sdn-ipsec-flow-protection-11.txt
Thread-Index: AQHWreX0c88acJXFBk2yYgVjsJF2bKmvCuOA///cU0CAAVuUAP//zZ2A
Date: Fri, 30 Oct 2020 19:40:03 +0000
Message-ID: <834a668ac559460a9f356bbb6c16b8fd@cert.org>
References: <160337357077.29083.9236626834026808055@ietfa.amsl.com> <EE5AB669-73BB-4517-A6F4-23B7807FB36E@um.es> <5F9815D1.9010303@btconnect.com> <DDE550B1-9A9E-4954-B6F9-C0A33ECE1275@um.es> <5F99B221.3040504@btconnect.com> <56155C91-BFE8-4BA9-A55C-46B12E59CD94@um.es> <5F9AEFD3.90903@btconnect.com> <059aaae84a354411ad1023afa2a837ba@cert.org> <5F9BF578.6000101@btconnect.com>
In-Reply-To: <5F9BF578.6000101@btconnect.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.64.202.126]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2nsf/DO-fJq2XmuIrgpNw3dooQiTlQiw>
Subject: Re: [I2nsf] [Last-Call] New Version Notification for draft-ietf-i2nsf-sdn-ipsec-flow-protection-11.txt
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: Fri, 30 Oct 2020 19:40:28 -0000

SGkgVG9tIQ0KDQo+IC0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQo+IEZyb206IHRvbSBwZXRj
aCA8ZGFlZHVsdXNAYnRjb25uZWN0LmNvbT4NCj4gU2VudDogRnJpZGF5LCBPY3RvYmVyIDMwLCAy
MDIwIDc6MTQgQU0NCj4gVG86IFJvbWFuIERhbnlsaXcgPHJkZEBjZXJ0Lm9yZz47IFJhZmEgTWFy
aW4tTG9wZXogPHJhZmFAdW0uZXM+DQo+IENjOiBpMm5zZkBpZXRmLm9yZzsgRmVybmFuZG8gUGVy
ZW5pZ3Vlei1HYXJjaWENCj4gPGZlcm5hbmRvLnBlcmVuaWd1ZXpAY3VkLnVwY3QuZXM+OyBHYWJy
aWVsIExvcGV6IDxnYWJpbG1AdW0uZXM+Ow0KPiB5bmlyLmlldGZAZ21haWwuY29tOyBsYXN0LWNh
bGxAaWV0Zi5vcmcNCj4gU3ViamVjdDogUmU6IFtMYXN0LUNhbGxdIE5ldyBWZXJzaW9uIE5vdGlm
aWNhdGlvbiBmb3IgZHJhZnQtaWV0Zi1pMm5zZi1zZG4taXBzZWMtDQo+IGZsb3ctcHJvdGVjdGlv
bi0xMS50eHQNCj4gDQo+IFJvbWFuICBub3QgdGhpcyBJLUQgYnV0IHNlZSBiZWxvdw0KPiANCj4g
T24gMjkvMTAvMjAyMCAxODo0NiwgUm9tYW4gRGFueWxpdyB3cm90ZToNCj4gPiBIaSBUb20hDQo+
ID4NCj4gPj4gLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCj4gPj4gRnJvbTogbGFzdC1jYWxs
IDxsYXN0LWNhbGwtYm91bmNlc0BpZXRmLm9yZz4gT24gQmVoYWxmIE9mIHRvbSBwZXRjaA0KPiA+
PiBTZW50OiBUaHVyc2RheSwgT2N0b2JlciAyOSwgMjAyMCAxMjozOCBQTQ0KPiA+PiBUbzogUmFm
YSBNYXJpbi1Mb3BleiA8cmFmYUB1bS5lcz4NCj4gPj4gQ2M6IGkybnNmQGlldGYub3JnOyBGZXJu
YW5kbyBQZXJlbmlndWV6LUdhcmNpYQ0KPiA+PiA8ZmVybmFuZG8ucGVyZW5pZ3VlekBjdWQudXBj
dC5lcz47IEdhYnJpZWwgTG9wZXogPGdhYmlsbUB1bS5lcz47DQo+ID4+IHluaXIuaWV0ZkBnbWFp
bC5jb207IGxhc3QtY2FsbEBpZXRmLm9yZw0KPiA+Pg0KPiA+PiBUb3AgcG9zdGluZyBhIG5ldywg
cmVsYXRlZCBpc3N1ZSB0aGF0IG1heSBuZWVkIFNlY3VyaXR5IEFEIG9yIFdHDQo+ID4+IENoYWly
IHRvIGFjdCBvbi4NCj4gPj4NCj4gPj4gSXQgc2VlbXMgdG8gbWUgdGhhdCB0aGUgSUFOQSBlbnRy
aWVzIGZvciBJS0V2MiBhcmUgaW5jb21wbGV0ZS4NCj4gPj4gUkZDODI0NyBkb2VzIGEgZmluZSBq
b2Igb2Ygc3BlY2lmeWluZyBhbGdvcml0aG1zIGFuZCBhZGRpbmcNCj4gPj4gaW5mb3JtYXRpb24g
c3VjaCBhcyBzdGF0dXMgKE1VU1QvU0hPVUxEKyksIElvVCwgQUVBRCBhbmQgc28gb24sDQo+ID4+
IGluZm9ybWF0aW9uIHdoaWNoIGlzIG5vdCBwcmVzZW50IG9uIElBTkEuICBUaGUgcG9saWN5IGZv
ciwgZS5nLg0KPiA+PiBUcmFuc2Zvcm0gVHlwZSAxLCBpcyBleHBlcnQgcmV2aWV3IGFuZCBlbnRy
aWVzIGhhdmUgYmVlbiBhZGRlZCB2aWENCj4gPj4gZHJhZnQtc215c2xvdi1lc3AtZ29udCBidXQg
dGhlIElBTkEgZW50cmllcyBsYWNrIHRoaXMgaW5mb3JtYXRpb24NCj4gPj4gYW5kLCBsb29raW5n
IGF0IHRoZSBJLUQsIEkgc2VlIG5vIHN1Y2ggaW5mb3JtYXRpb24gKG5vciBpcyB0aGVyZSBhbnkN
Cj4gPj4gcmVhc29uIGZvciBpdCB0byBiZSB0aGVyZSkuICBZZXQgZHJhZnQtaWV0Zi1pMm5zZi1z
ZG4uLi4gbmVlZHMgdGhpcyBpbmZvcm1hdGlvbg0KPiBhcyByZWZlcmVuY2VzIGluIHRoZSBZQU5H
IG1vZHVsZSBzaG93Lg0KPiA+Pg0KPiA+PiBJdCBzZWVtcyB0byBtZSB0aGF0IHRoaXMgaXMgYSBz
aW1pbGFyIHNpdHVhdGlvbiB0byB0aGF0IHdoaWNoIHRoZSBUTFMNCj4gPj4gV0cgZm91bmQgaXRz
ZWxmIGluIGFuZCB3aGljaCBsZWQgdG8gYSByZXZpc2lvbiBvZiB0aGUgVExTIElBTkENCj4gPj4g
ZW50cmllcyB0byBwcm92aWRlIHdoYXQgd2FzIG5lZWRlZCB2aWEgYWRkaXRpb25hbCBjb2x1bW5z
Lg0KPiA+DQo+ID4gUGxlYXNlIGhlbHAgbWUgdW5kZXJzdGFuZC4gIEluIHBhcnRpY3VsYXIsIEkn
bSBub3QgZm9sbG93aW5nIHdoeSB0aGlzDQo+IGRvY3VtZW50IHNob3VsZCBtb2RpZnkgSUtFIElB
TkEgcmVnaXN0cmllcy4gIEluIG15IHZpZXcsIHRoaXMgZG9jdW1lbnQgaXMNCj4gcHJvdmlkZXMg
YSBkYXRhIG1vZGVsIHRvIGVuY29kZSBhbiAiSUtFdjIgY29uZmlndXJhdGlvbiIgb2Ygc29ydHMu
ICBDZXJ0YWlubHksDQo+IHRoZXJlIGFyZSB2YWxpZC9pbnZhbGlkL2luY29tcGxldGUvbm90IHJl
Y29tbWVuZGVkIHdheXMgdG8gcHJvdmlkZSBhDQo+IGNvbmZpZ3VyYXRpb24gd2l0aCB0aGlzIGRh
dGEgbW9kZWwgaWYgb25lIHJlbGllZCBzb2xlbHkgb24gdGhlIHBvaW50ZXJzIHRvIHRoZQ0KPiBJ
QU5BIHJlZ2lzdHJpZXMgZnJvbSB0aGUgWUFORyBtb2R1bGUgZGVmaW5pdGlvbi4gIEhvd2V2ZXIs
IGFzIHlvdSBub3RlZCwNCj4gUkZDODI0NyBhbHJlYWR5IHByb3ZpZGVzIGd1aWRhbmNlIG9uIHNw
ZWNpZnlpbmcgYSBjb25maWd1cmF0aW9uIChhbGJlaXQgdGhpcw0KPiBndWlkYW5jZSBpc24ndCBm
dWxseSBlbmNvZGVkIGluIHRoZSByZWdpc3RyaWVzKS4gIEZ1cnRoZXJtb3JlLCB0aGlzIGRvY3Vt
ZW50DQo+IHN0YXRlczoNCj4gPg0KPiA+IFNlY3Rpb24gOC4xDQo+ID4gICAgIG8gIElLRXYyIGNv
bmZpZ3VyYXRpb25zIHNob3VsZCBhZGhlcmUgdG8gdGhlIHJlY29tbWVuZGF0aW9ucyBpbg0KPiA+
ICAgICAgICBbUkZDODI0N10uDQo+ID4NCj4gPiBzbyB0aGVyZSBpcyBndWlkYW5jZSBvbiBwcm9k
dWNpbmcgYSBjb25maWd1cmF0aW9uLiAgV2hhdCBpcyBtaXNzaW5nPw0KPiA+DQo+ID4+IEkgdGhp
bmsgdGhhdCB0aGUgSUFOQSBwYWdlcyBmb3IgSUtFdjIgbmVlZCByZXZpc2luZyBzbyB0aGF0IHRo
YXQNCj4gPj4gYWRkaXRpb25hbCBpbmZvcm1hdGlvbiB0aGF0IFJGQzgyNDcgcHJvdmlkZXMgaXMg
cmVxdWlyZWQgYXMNCj4gPj4gYWRkaXRpb25hbCBjb2x1bW5zIGluIHRoZSBJQU5BIGVudHJpZXMg
YXQgbGVhc3QgZm9yIFR5cGUgMSwgVHlwZSAyLA0KPiA+PiBUeXBlIDMsIFR5cGUgNCBhbmQgQXV0
aGVudGljYXRpb24gTWV0aG9kLg0KPiA+DQo+ID4gV2hpbGUgdGhpbmdzIGNvdWxkIGJlIGNsZWFy
ZXIsIEknbSB1bnN1cmUgb2Ygd2h5IF90aGlzIFlBTkcgZG9jdW1lbnRfDQo+IHNob3VsZCBkbyBh
IHJlZ2lzdHJ5IHJlZW5naW5lZXJpbmcuICBEaWQgeW91IG1lYW4gaXQgc2hvdWxkIGJlIGRvbmUg
aW4gZ2VuZXJhbD8NCj4gDQo+IE5vdCB0aGlzIEktRCBidXQgYW5vdGhlciBJLUQgZnJvbSBhIFdH
IHdpdGggY2xvc2VyIGxpbmtzIHRvIElLRXYyOyBJIGRvbid0IGtub3cNCj4gd2hpY2ggV0cgdGhh
dCB3b3VsZCBiZSBidXQgYSBTZWN1cml0eSBBRCB3b3VsZDotKQ0KDQpUaGFua3MgZm9yIGNsYXJp
ZnlpbmcuICBJUFNFQ01FIChodHRwczovL2RhdGF0cmFja2VyLmlldGYub3JnL3dnL2lwc2VjbWUv
YWJvdXQvKSAod2hvIGhhcyBiZWVuIGNyb3NzLXBvc3RlZCB3aXRoIHRoaXMgbm90ZSkgIGlzIGxp
a2VseSB0aGUgYmVzdCBwbGFjZSB0byBoYW5kbGUgSVBzZWMgbWFpbnRlbmFuY2UgYW5kIHRoZSBr
aW5kIG9mIHJlZ2lzdHJ5IG1vZGlmaWNhdGlvbnMgeW91IGRlc2NyaWJlIGJlbG93Lg0KDQpSZWdh
cmRzLA0KUm9tYW4NCg0KPiBUaGlzIEktRCwgYXMgeW91IHF1b3RlLCBwb2ludHMgdG8gUkZDODI0
NyBmb3IgZ3VpZGFuY2UgYW5kIHRoYXQgaXMgZmluZS4NCj4gICBCdXQgc2VjdXJpdHkgbW92ZXMg
b24gYW5kIG5ldyBhbGdvcml0aG1zIHdpbGwgYmUgbmVlZGVkIGFuZCB0aGlzIEktRCBhbHNvDQo+
IHBvaW50cyB0byB0aGUgSUFOQSByZWdpc3RyeSwgd2hpY2ggaXMgRXhwZXJ0IFJldmlldywgd2hl
cmUgbmV3IGVudHJpZXMgaGF2ZQ0KPiBiZWVuIGFkZGVkIGFscmVhZHk7IGFuZCBmb3IgdGhvc2Ug
dGhlIElBTkEgUmVnaXN0cnkgZ2l2ZXMgbm8gZ3VpZGFuY2UgYW5kIHRoZQ0KPiBJLUQgdGhhdCBJ
QU5BIHJlZmVyZW5jZXMgZm9yIHRoZSBuZXcgZW50cmllcyAtIHdyaXR0ZW4gYnkgdGhlIEV4cGVy
dCBSZXZpZXdlciEgLQ0KPiBhbHNvIGdpdmVzIG5vIGd1aWRhbmNlLiBPdmVyIHRpbWUgd2UgYXJl
IGxpa2VseSB0byBhY2NydWUgYWxnb3JpdGhtcyB3aXRoIG5vDQo+IGd1aWRhbmNlIHVubGVzcyBh
bmQgdW50aWwgYW4gUkZDODI0Ny1iaXMgYXBwZWFycyBvciB3ZSByZXF1aXJlIElBTkEgdG8gaGF2
ZQ0KPiBjb2x1bW5zIGZvciBndWlkYW5jZS4NCj4gQ3VycmVudGx5IHRoZSBuZXcgYWxnb3JpdGht
cyBhcmUgR09TVCBhbmQgc28gcGVyaGFwcyBvZiBsaW1pdGVkIGludGVyZXN0IGJ1dA0KPiBvbiB0
aGUgVExTIGxpc3QgSSBhbSBhbHdheXMgc2VlaW5nIG5ldyBhbGdvcml0aG1zIGFwcGVhciBhbmQg
dGhlcmUgdGhlIG5ldw0KPiBJQU5BIGVudHJ5IGlzIHJlcXVpcmVkIHRvIGdpdmUgZ3VpZGFuY2Uu
ICBNeSBzZW5zZSBpcyB0aGF0IElLRXYyIGlzIGEgYml0IHNsb3dlcg0KPiB0byB0YWtlIHVwIG5l
dyBvbmVzIGJ1dCwgYXMgd2l0aCBSRkM4MjQ3LCBpdCBkb2VzIGV2ZW50dWFsbHkuDQo+IA0KPiBJ
IHRoaW5rIHRoYXQgdXNlcnMgbmVlZCB0aG9zZSBleHRyYSBjb2x1bW5zIHRoYXQgUkZDODI0NyBw
cm92aWRlcyBvbiB0aGUgSUFOQQ0KPiB3ZWJzaXRlIHNvIHRoYXQgd2hlbiBuZXcgYWxnb3JpdGht
cyBhcmUgYWRkZWQgYnkgRXhwZXJ0IFJldmlldywgdGhlbiB0aGF0DQo+IGd1aWRhbmNlIG11c3Qg
YmUgYWRkZWQgYXMgd2VsbC4gIFRoaXMgaXMgd2hhdCB0aGUgVExTIFdHIGNhbWUgcm91bmQgdG8g
YW5kIEkNCj4gdGhpbmsgdGhhdCBJS0V2MiBuZWVkcyB0byBkbyB0aGUgc2FtZS4NCj4gDQo+IFRv
bSBQZXRjaA0KPiANCj4gDQo+ID4gUmVnYXJkcywNCj4gPiBSb21hbg0KPiA+DQo+ID4+IFRvbSBQ
ZXRjaA0KPiA+Pg0KPiA+PiBPbiAyOS8xMC8yMDIwIDExOjIzLCBSYWZhIE1hcmluLUxvcGV6IHdy
b3RlOg0KPiA+Pj4gSGkgVG9tOg0KPiA+Pj4NCj4gPj4+PiBFbCAyOCBvY3QgMjAyMCwgYSBsYXMg
MTk6MDIsIHRvbSBwZXRjaCA8ZGFlZHVsdXNAYnRjb25uZWN0LmNvbT4NCj4gZXNjcmliacOzOg0K
PiA+Pj4+DQo+ID4+Pj4gT24gMjgvMTAvMjAyMCAxMDo0MiwgUmFmYSBNYXJpbi1Mb3BleiB3cm90
ZToNCj4gPj4+Pj4gSGkgVG9tOg0KPiA+Pj4+Pg0KPiA+Pj4+PiBUaGFuayB5b3UgdmVyeSBtdWNo
IGZvciB5b3VyIGluc2lnaHQuIEl0IGlzIHZlcnkgaGVscGZ1bC4gUGxlYXNlDQo+ID4+Pj4+IHNl
ZSBvdXINCj4gPj4gY29tbWVudHMvcXVlc3Rpb25zIGlubGluZS4NCj4gPj4+Pj4NCj4gPj4+Pj4+
IEVsIDI3IG9jdCAyMDIwLCBhIGxhcyAxMzo0MiwgdG9tIHBldGNoIDxkYWVkdWx1c0BidGNvbm5l
Y3QuY29tPg0KPiA+PiBlc2NyaWJpw7M6DQo+ID4+Pj4+Pg0KPiA+Pj4+Pj4gSSB0aGluayB0aGF0
IHRoZSBJRVNHIHdpbGwgZmluZCBhIG51bWJlciBvZiBwcm9ibGVtcyB3aXRoIHRoaXMgSS1ELg0K
PiA+Pj4+Pj4NCj4gPj4+Pj4+IFlBTkcgbW9kdWxlIHJlZmVyZW5jZXMgUkZDODIyIHdoaWNoIGlz
IHNldmVyYWwgeWVhcnMgb3V0IG9mIGRhdGUNCj4gPj4+Pg0KPiA+Pj4+IFJhZmENCj4gPj4+Pg0K
PiA+Pj4+IE9uIGJvaWxlciBwbGF0ZSwgSSBtZWFuIHRoZSByZWZlcmVuY2UgdG8gUkZDMjExOSB3
aGljaCBub3cgbXVzdCB1c2UNCj4gPj4+PiB0aGUNCj4gPj4gbGFuZ3VhZ2UgZnJvbSBSRkM4MTc0
IGluIHRoZSBib2R5IG9mIHRoZSBJLUQ7IHNvcnJ5IGZvciB0aGUgY29uZnVzaW9uLg0KPiA+Pj4N
Cj4gPj4+IEFoIG9rLiBJIGd1ZXNzIHlvdSBhcmUgcmVmZXJyaW5nIHRvIGNoYW5nZSB0aGF0IHBh
cmFncmFwaCB3aXRoIHRoaXM6DQo+ID4+Pg0KPiA+Pj4NCj4gPj4+IFRoZSBrZXkgd29yZHMgIk1V
U1QiLCAiTVVTVCBOT1QiLCAiUkVRVUlSRUQiLCAiU0hBTEwiLCAiU0hBTEwgTk9UIiwNCj4gPj4+
ICJTSE9VTEQiLCAiU0hPVUxEIE5PVCIsICJSRUNPTU1FTkRFRCIsICJOT1QgUkVDT01NRU5ERUQi
LA0KPiA+PiAiTUFZIiwgYW5kDQo+ID4+PiAiT1BUSU9OQUwiIGluIHRoaXMgZG9jdW1lbnQgYXJl
IHRvIGJlIGludGVycHJldGVkIGFzIGRlc2NyaWJlZCBpbg0KPiA+Pj4gQkNQDQo+ID4+PiAxNCBS
RkMyMTE5IFJGQzgxNzQgd2hlbiwgYW5kIG9ubHkgd2hlbiwgdGhleSBhcHBlYXIgaW4gYWxsIGNh
cGl0YWxzLA0KPiA+Pj4gYXMgc2hvd24gaGVyZS4NCj4gPj4+DQo+ID4+Pj4NCj4gPj4+PiBPbiBY
WFhYLCB5b3UgaGF2ZSBYWFhYIHN0YW5kaW5nIGluIGZvciBtb3JlIHRoYW4gb25lIFJGQy10by1i
ZQ0KPiA+Pj4+IHdoaWNoDQo+ID4+IGNvbmZ1c2VzLiAgVGhlIGNvbnZlbnRpb24gaXMgdG8gdXNl
IFhYWFggZm9yIHRoaXMgSS1EIGFuZCB0aGVuIEFBQUENCj4gPj4gQkJCQiBldGMgZm9yIGFueSBv
dGhlcnMgc3VjaCBhcyB0aGUgbmV0Y29uZiBJLUQgaW4gdGhpcyBpbnN0YW5jZS4NCj4gPj4+DQo+
ID4+PiBBaCBvay4gSW4gYW55IGNhc2UsIHdlIGhhdmUgbm93IG9ubHkgWFhYWCBmb3Igb3VyIFJG
Qy10by1iZSBzbw0KPiA+Pj4gcHJvYmxlbQ0KPiA+PiBmaXhlZC4NCj4gPj4+Pg0KPiA+Pj4+IFR3
byBiaWcgaXNzdWVzLCBmb3IgbWUgKHBlcmhhcHMgbm90IGZvciBvdGhlcnMpLiAgVGhlIGNvbnZl
bnRpb24NCj4gPj4+PiB3aXRoIFlBTkcNCj4gPj4gaXMgZm9yIGVhY2ggc3VjY2Vzc2l2ZSBsaW5l
IHRvIGJlIGluZGVudGVkIHR3byBjaGFyYWN0ZXJzLCB5b3UgaGF2ZQ0KPiA+PiBmb3VyLCB3aGlj
aCBjcmVhdGVzIGEgbG90IG9mIHdoaXRlIHNwYWNlIGFuZCBwdXNoZXMgdGhlIHRleHQgdG8gdGhl
DQo+ID4+IHJpZ2h0IGhhbmQgbWFyZ2luLiAgSSB0aGluayB0aGF0IHR3byBjaGFyYWN0ZXJzIGlz
IHRoZSBkZWZhdWx0IHdoZW4NCj4gPj4geW91IHVzZSBweWFuZyB0byBmb3JtYXQgYSBZQU5HIG1v
ZHVsZS4NCj4gPj4+DQo+ID4+PiBXZSBjYW4gdHJ5IHRvIHJlZHVjZSBpdCB0byB0d28gY2hhcmFj
dGVycy4NCj4gPj4+DQo+ID4+Pj4NCj4gPj4+PiBBbmQgcmVmZXJlbmNlcy4gIEkgaGF2ZSBoYWQg
dG8gd29yayBoYXJkZXIgdGhhbiBJIHdhbnQgdG8gdG8gbWFrZQ0KPiA+Pj4+IHNlbnNlIG9mIHRo
ZSBJQU5BIHJlZmVyZW5jZXMuICBJIHRoaW5rIHlvdSBzaG91bGQgaGF2ZSBmaXZlDQo+ID4+Pj4g
c2VwYXJhdGUgcmVmZXJlbmNlcyBpbiB0aGUgSS1EIGZvciBJQU5BIGZvciBUcmFuc2Zvcm0gVHlw
ZSAxDQo+ID4+Pj4gVHJhbnNmb3JtIFR5cGUgMyBUcmFuc2Zvcm0gVHlwZSA0IEF1dGhlbnRpY2F0
aW9uIE1ldGhvZCBQcm90b2NvbA0KPiA+Pj4+IE51bWJlcnMgYW5kIGVhY2ggcmVmZXJlbmNlIGlu
IHRoZSBJLUQgc2hvdWxkIGhhdmUgYSBVUkwgcG9pbnRpbmcgdG8NCj4gPj4+PiB0aGUgc3BlY2lm
aWMgc2VjdGlvbiBvZg0KPiA+PiBJQU5BIHdlYiBzaXRlLg0KPiA+Pj4NCj4gPj4+IE9rLCBnb29k
LiBUaGlzIGZvbGxvd3Mgd2hhdCB3ZSB0aG91Z2h0Lg0KPiA+Pj4NCj4gPj4+PiBJbiB0aGUgWUFO
RywgaXQgaXMgaGFyZGVyIHRvIGtub3cgd2hhdCB0byBkby4gIFRob3NlIGZpcnN0IHRocmVlDQo+
ID4+Pj4gcmVmZXJlbmNlcw0KPiA+PiBhcmUgaW4gdGhlIHRoaXJkIHRpZXIgaS5lLg0KPiA+Pj4+
IEdyb3VwIC0gSW50ZXJuZXQgS2V5IEV4Y2hhbmdlIFYyIChJS0V2MikgUGFyYW1ldGVycyBSZWdp
c3RyeQ0KPiA+Pj4+IC1UcmFuc2Zvcm0gQXR0cmlidXRlIFR5cGVzIGFuZCB0aGVuIFR5cGUgMSwg
MywgNCBhcyB0aGUgdGhpcmQgdGllcg0KPiA+Pj4+IGFzIEkgYW0gY2FsbGluZyBpdCBhbmQgSSB0
aGluayB0aGF0IGV2ZXJ5IHJlZmVyZW5jZSBpbiB0aGUgWUFORw0KPiA+Pj4+IHNob3VsZCBnaXZl
IG1lIGFsbCB0aHJlZSB0aWVycyBhZnRlciBJQU5BIGluIHRoYXQgb3JkZXIgcGVyaGFwcw0KPiA+
Pj4+IElBTkE7IElLRXYyIFBhcmFtZXRlcnM7IFRyYW5zZm9ybSBBdHJpYnV0ZSBUeXBlczsgVHJh
bnNmb3JtIFR5cGUgMQ0KPiA+Pj4NCj4gPj4+IEdyZWF0LiBXZSBhbHNvIGNvbnNpZGVyZWQgdGhp
cyBhcyBhIHBvc3NpYmxlIHNvbHV0aW9uIGFmdGVyIHNlbmRpbmcgb3VyIGUtDQo+IG1haWwuDQo+
ID4+IExldOKAmXMgZG8gaXQuDQo+ID4+Pg0KPiA+Pj4+IElmIHRoZSBzeW50YXggbmVlZHMgdHdl
ZWtpbmcsIHRoZW4gdGhlIFJGQyBFZGl0b3Igd2lsbCBkbyBhIGdvb2QNCj4gPj4+PiBqb2Igb2Yg
dGhhdA0KPiA+PiBidXQgYXQgcHJlc2VudCB0aGUgcmVmZXJlbmNlcyBhcmUgaW5jb25zaXN0ZW50
IGluIHdoaWNoIGVsZW1lbnRzIGFyZQ0KPiA+PiBzcGVjaWZpZWQgaW4gd2hhdCBvcmRlciBhbmQg
dGhhdCBpcyBzb21ldGhpbmcgdGhlIFJGQyBFZGl0b3IgcHJvYmFibHkNCj4gY2Fubm90IGNvcGUg
d2l0aC4NCj4gPj4+PiBBdXRoZW50aWNhdGlvbiBNZXRob2QgaXMgYSByZWdpc3RyeSBzbyB0aGF0
IGp1c3QgbmVlZHMgR3JvdXAgbmFtZQ0KPiA+Pj4+IGFuZA0KPiA+PiBSZWdpc3RyeSBuYW1lIGFm
dGVyIElBTkEuDQo+ID4+Pg0KPiA+Pj4gT2ssIGdvb2QuDQo+ID4+Pj4NCj4gPj4+PiBTb21lIG1p
bm9yIGdsaXRjaGVzLg0KPiA+Pj4+IEktRCBhcHBlYXJzIHR3aWNlIGluIHRoZSBib2R5IG9mIHRo
ZSBJLUQgLSBwZXJoYXBzIGRvY3VtZW50IG9yIG1lbW8uDQo+ID4+Pg0KPiA+Pj4gT2suDQo+ID4+
Pg0KPiA+Pj4+IG9iamV0aXZlcy9vYmplY3RpdmVzLw0KPiA+Pj4NCj4gPj4+IEZpeGVkLg0KPiA+
Pj4+IGVuZCBwb3J0IG51bWJlciBwZXJoYXBzIC9tdXN0L01VU1QvDQo+ID4+Pg0KPiA+Pj4+IGFu
ZCBZQU5HIGlzIHZlcnkgZ29vZCBhdCBpbmNsdWRpbmcgc3VjaCBjaGVja3Mgd2l0aCBhIG11c3Qg
Li4uLg0KPiA+Pj4+ICdJZiBBRUFEIGlzIHVzZWQgLi4gd2hlcmU/IHRoaXMgb2NjdXJzIGluIHNl
dmVyYWwgcGxhY2VzIGFuZCBJDQo+ID4+Pj4gdGhpbmsgdGhhdCB5b3UNCj4gPj4gbmVlZCB0byBz
cGVjaWZ5IHRoZSBsZWFmIHdoZXJlIEFFQUQgd2lsbCBiZSBzcGVjaWZpZWQgb3IgaW1wbGllZC4N
Cj4gPj4+DQo+ID4+PiBPayB3ZSBoYXZlIGNoYW5nZWQgaXQgdG86DQo+ID4+Pg0KPiA+Pj4gSWYg
QXV0aGVudGljYXRlZCBFbmNyeXB0aW9uIHdpdGggQXNzb2NpYXRlZCBEYXRhIChBRUFEKSBpcyB1
c2VkDQo+ID4+PiAobGVhZg0KPiA+Pj4gZXNwLWFsZ29yaXRobXMvZW5jcnlwdGlvbi9hbGdvcml0
aG0tdHlwZSkNCj4gPj4+IHRoaXMgZmxhZyBNVVNUIGJlIGZhbHNlLiINCj4gPj4+DQo+ID4+Pj4g
QW5kIGlzIGl0IHBvc3NpYmxlIHRvIG1ha2UgdGhhdCBhIFlBTkcgJ211c3QnIHN0YXRlbWVudCAt
IGxvb2tpbmcNCj4gPj4+PiBhdCB0aGUNCj4gPj4gSUtFdjIgcmVnaXN0cmllcyBpdCBpcyBub3Qg
b2J2aW91cyB3aGljaCBhcmUgQUVBRCBzbyB0aGF0IG1pZ2h0IGJlDQo+ID4+IG1vcmUgY29tcGxl
eGl0eSB0aGFuIGl0IGlzIHdvcnRoLg0KPiA+Pj4+ICdvbmx5IGF2YWlsYWJsZSBvbiBsaW51eCBr
ZXJuZWxzJyBVbSBpbXBsZW1lbnRhdGlvbiBkZXRhaWwsIHlvdSBtYXkNCj4gPj4+PiBnZXQNCj4g
Pj4gYXNrZWQgdG8gcmVtb3ZlIHRoYXQgYWx0b2dldGhlciBvciBhdCBsZWFzdCB0byBhIEluZm9y
bWF0aXZlIEFwcGVuZGl4DQo+ID4+IC0gSSB3b3VsZCBsZWF2ZSBpdCBpbiBmb3Igbm93Lg0KPiA+
Pj4NCj4gPj4+IE9rLg0KPiA+Pj4NCj4gPj4+PiAnaW1wb3J0IGlldGYtaTJuc2YtaWtlYycgdGhl
IHJlZmVyZW5jZSBuZWVkcyB0byBiZSB0byBhIFJGQyBhbmQgaWYNCj4gPj4+PiBpdCBpcyBub3Qg
eWV0IGFuIFJGQyB0aGVuIFJGQyBYWFhYIDx0aXRsZT4gaW4gYm90aCBBcHBlbmRpeCBCIGFuZCBD
DQo+ID4+Pg0KPiA+Pj4gWWVzLCB3ZSBoYXZlIGNoYW5nZWQgdGhhdCB0bzoNCj4gPj4+DQo+ID4+
PiBSRkMgWFhYWDogU29mdHdhcmUtRGVmaW5lZCBOZXR3b3JraW5nDQo+ID4+PiAgICAgICAgICAg
ICAgICAgIChTRE4pLWJhc2VkIElQc2VjIEZsb3cgUHJvdGVjdGlvbi4NCj4gPj4+DQo+ID4+Pj4g
bGVhZi1saXN0IHBmcy1ncm91cHMgY291bGQgZG8gd2l0aCBhIHJlZmVyZW5jZSAtIFRyYW5zZm9y
bSBUeXBlIDQ/DQo+ID4+Pg0KPiA+Pj4gVGhlIGxlYWYgbGlzdCBpcyByZWZlcnJpbmcgdG8gdHlw
ZSBwZnMtZ3JvdXAgYW5kIHdlIGhhdmUgbm93DQo+ID4+Pg0KPiA+Pj4gdHlwZWRlZiBwZnMtZ3Jv
dXAgew0KPiA+Pj4gICAgICAgICAgICAgICB0eXBlIHVpbnQxNjsNCj4gPj4+ICAgICAgICAgICAg
ICAgZGVzY3JpcHRpb24NCj4gPj4+ICAgICAgICAgICAgICAgICAgICJESCBncm91cHMgZm9yIElL
RSBhbmQgSVBzZWMgU0EgcmVrZXkuIjsNCj4gPj4+ICAgICAgICAgICAgICAgcmVmZXJlbmNlDQo+
ID4+PiAgICAgICAgICAgICAgICAgICAiSUFOQTsgSW50ZXJuZXQgS2V5IEV4Y2hhbmdlIFYyIChJ
S0V2MikgUGFyYW1ldGVyczsNCj4gPj4+IAkJCQlUcmFuc2Zvcm0gQXRyaWJ1dGUgVHlwZXM7IFRy
YW5zZm9ybSBUeXBlIDQgLQ0KPiA+Pj4gICAgICAgICAgICAgICAgICAgRGlmZmllLUhlbGxtYW4g
R3JvdXAgVHJhbnNmb3JtIElEcy4NCj4gPj4+IAkJCQlTZWN0aW9uIDMuMy4yIGluIFJGQyA3Mjk2
LiI7DQo+ID4+PiAgICAgICAgICAgfQ0KPiA+Pj4NCj4gPj4+DQo+ID4+Pj4NCj4gPj4+PiBJIGFt
IHN0aWxsIHdvcmtpbmcgbXkgd2F5IHRocm91Z2ggdGhlIFlBTkcgc28gbWF5IGhhdmUgc29tZSBt
b3JlDQo+ID4+IGNvbW1lbnRzIHRvbW9ycm93Lg0KPiA+Pj4NCj4gPj4+IE9rLCBkbyBub3Qgd29y
cnkgd2Ugd2lsbCB3b3JrIGluIC0xMiB3aXRoIHRoZXNlIGNvbW1lbnRzIHNvIGZhciB0bw0KPiA+
Pj4gaGF2ZSBhDQo+ID4+IHF1aWNrIHJlc3BvbnNlLiBXZSBjYW4gcHJlcGFyZSBhIGFub3RoZXIg
dmVyc2lvbiBsYXRlciB3aXRoIHRoZSByZXN0IG9mDQo+IHRoZW0uDQo+ID4+Pg0KPiA+Pj4gVGhh
bmsgeW91IHZlcnkgbXVjaCBmb3IgeW91ciBlZmZvcnQuDQo+ID4+Pj4NCj4gPj4+PiBUb20gUGV0
Y2gNCj4gPj4+Pg0KPiA+Pj4+DQo+ID4+Pj4NCj4gPj4+Pg0KPiA+Pj4+DQo+ID4+Pj4NCj4gPj4+
Pg0KPiA+Pj4+DQo+ID4+Pj4NCj4gPj4+Pg0KPiA+Pj4+DQo+ID4+Pj4NCj4gPj4+Pg0KPiA+Pj4+
DQo+ID4+Pj4+IFdlIGhhdmUgcmVhbGl6ZWQgdGhhdCB3ZSBtaXNzZWQgdG8gY2hhbmdlIHRoaXMs
IGV2ZW4gdGhvdWdoIHdlDQo+ID4+Pj4+IGRpc2N1c3NlZA0KPiA+PiBpdC4gV2Ugd2lsbCBjaGFu
Z2UgaXQgcmlnaHQgYXdheSBpbiB0aGUgZm9sbG93aW5nIHdheSAoYm9sZCk6DQo+ID4+Pj4+DQo+
ID4+Pj4+IGNhc2UgcmZjODIyLWFkZHJlc3Mtc3RyaW5nIHsNCj4gPj4+Pj4gICAgICAgIGxlYWYg
cmZjODIyLWFkZHJlc3Mtc3RyaW5nIHsNCj4gPj4+Pj4gICAgICAgICAgICAgdHlwZSBzdHJpbmc7
DQo+ID4+Pj4+ICAgICAgICAgICAgIGRlc2NyaXB0aW9uDQo+ID4+Pj4+ICAgICAgICAgICAgICAg
ICAiU3BlY2lmaWVzIHRoZSBpZGVudGl0eSBhcyBhDQo+ID4+Pj4+ICAgICAgICAgICAgICAgICAg
ZnVsbHktcXVhbGlmaWVkIFJGQzUzMjIgZW1haWwNCj4gPj4+Pj4gICAgICAgICAgICAgICAgICBh
ZGRyZXNzIHN0cmluZy4gQW4gZXhhbXBsZSBpcywNCj4gPj4+Pj4gICAgICAgICAgICAgICAgICBq
c21pdGhAZXhhbXBsZS5jb20uIFRoZSBzdHJpbmcNCj4gPj4+Pj4gICAgICAgICAgICAgICAgICBN
VVNUIE5PVCBjb250YWluIGFueQ0KPiA+Pj4+PiAgICAgICAgICAgICAgICAgIHRlcm1pbmF0b3Jz
IGUuZy4sIE5VTEwsIENSLA0KPiA+Pj4+PiAgICAgICAgICAgICAgICAgIGV0Yy4pLiI7DQo+ID4+
Pj4+ICAgICAgICAgICAgICByZWZlcmVuY2UNCj4gPj4+Pj4gICAgICAgICAgICAgICAgICAgICAi
UkZDIDUzMjIuIjsNCj4gPj4+Pj4gICAgICAgIH0NCj4gPj4+Pj4gfQ0KPiA+Pj4+Pg0KPiA+Pj4+
PiBCdHcsIHdlIGFscmVhZHkgdXNlZCBpbiB0aGUgcGFzdCDigJxjYXNlIHJmYzgyMi1hZGRyZXNz
LXN0cmluZ+KAnSBhbmQNCj4gPj4+Pj4g4oCcbGVhZg0KPiA+PiByZmM4MjItYWRkcmVzcy1zdHJp
bmfigJ0gc2luY2UgdGhpcyBpcyBjb21pbmcgZnJvbSBJS0V2MiBzdGFuZGFyZC4gRG8NCj4gPj4g
eW91IHRoaW5rIHdlIHNob3VsZCBjaGFuZ2UgdGhhdCBuYW1lIGFzIHdlbGw/DQo+ID4+Pj4+DQo+
ID4+Pj4+DQo+ID4+Pj4+Pg0KPiA+Pj4+Pj4gWUFORyBtb2R1bGUgcmVmZXJlbmNlcyBJQU5BIFBy
b3RvY29sIE51bWJlcnMgd2hpY2ggaXMgbm90IGluIHRoZQ0KPiA+Pj4+Pj4gSS1EIHJlZmVyZW5j
ZXMNCj4gPj4+Pj4NCj4gPj4+Pj4gV2UgaGF2ZSBpbmNsdWRlZCB0aGUgZm9sbG93aW5nIHJlZmVy
ZW5jZToNCj4gPj4+Pj4NCj4gPj4+Pj4gW0lBTkEtUHJvdG9jb2xzLU51bWJlcl0NCj4gPj4+Pj4g
ICAgICAgICAgICAgICAgIEludGVybmV0IEFzc2lnbmVkIE51bWJlcnMgQXV0aG9yaXR5IChJQU5B
KSwgIlByb3RvY29sDQo+ID4+Pj4+ICAgICAgICAgICAgICAgICBOdW1iZXJzIiwgSmFudWFyeSAy
MDIwLg0KPiA+Pj4+Pg0KPiA+Pj4+Pg0KPiA+Pj4+Pj4NCj4gPj4+Pj4+IHMuMiBib2lsZXIgcGxh
dGUgaXMgb3V0IG9mIGRhdGUNCj4gPj4+Pj4NCj4gPj4+Pj4gV2hhdCB3ZSBzZWUgaXMgdGhlIEkt
RCBoYXMgdGhlIHNlY29uZCBjaG9pY2Ugc3RhdGVkIGluDQo+ID4+Pj4+IGh0dHBzOi8vd3d3Lmll
dGYub3JnL3N0YW5kYXJkcy9pZHMvZ3VpZGVsaW5lcy8NCj4gPj4+Pj4NCj4gPj4+Pj4gVGhpcyBJ
bnRlcm5ldC1EcmFmdCBpcyBzdWJtaXR0ZWQgaW4gZnVsbCBjb25mb3JtYW5jZSB3aXRoIHRoZQ0K
PiA+Pj4+PiAgICAgIHByb3Zpc2lvbnMgb2YgQkNQIDc4IGFuZCBCQ1AgNzkuDQo+ID4+Pj4+DQo+
ID4+Pj4+ICAgICAgSW50ZXJuZXQtRHJhZnRzIGFyZSB3b3JraW5nIGRvY3VtZW50cyBvZiB0aGUg
SW50ZXJuZXQgRW5naW5lZXJpbmcNCj4gPj4+Pj4gICAgICBUYXNrIEZvcmNlIChJRVRGKS4gIE5v
dGUgdGhhdCBvdGhlciBncm91cHMgbWF5IGFsc28gZGlzdHJpYnV0ZQ0KPiA+Pj4+PiAgICAgIHdv
cmtpbmcgZG9jdW1lbnRzIGFzIEludGVybmV0LURyYWZ0cy4gIFRoZSBsaXN0IG9mIGN1cnJlbnQg
SW50ZXJuZXQtDQo+ID4+Pj4+ICAgICAgRHJhZnRzIGlzIGF0IGh0dHBzOi8vZGF0YXRyYWNrZXIu
aWV0Zi5vcmcvZHJhZnRzL2N1cnJlbnQvLg0KPiA+Pj4+Pg0KPiA+Pj4+PiAgICAgIEludGVybmV0
LURyYWZ0cyBhcmUgZHJhZnQgZG9jdW1lbnRzIHZhbGlkIGZvciBhIG1heGltdW0gb2Ygc2l4DQo+
IG1vbnRocw0KPiA+Pj4+PiAgICAgIGFuZCBtYXkgYmUgdXBkYXRlZCwgcmVwbGFjZWQsIG9yIG9i
c29sZXRlZCBieSBvdGhlciBkb2N1bWVudHMgYXQNCj4gYW55DQo+ID4+Pj4+ICAgICAgdGltZS4g
IEl0IGlzIGluYXBwcm9wcmlhdGUgdG8gdXNlIEludGVybmV0LURyYWZ0cyBhcyByZWZlcmVuY2UN
Cj4gPj4+Pj4gICAgICBtYXRlcmlhbCBvciB0byBjaXRlIHRoZW0gb3RoZXIgdGhhbiBhcyAid29y
ayBpbiBwcm9ncmVzcy4iDQo+ID4+Pj4+DQo+ID4+Pj4+IENvdWxkIHlvdSByZWZlciB3aGF0IGlz
IG91dCBvZiBkYXRlPw0KPiA+Pj4+Pg0KPiA+Pj4+Pj4NCj4gPj4+Pj4+IFhYWFggaXMgc3RhbmRp
bmcgaW4gZm9yIG1vcmUgdGhhbiBvbmUgUkZDDQo+ID4+Pj4+DQo+ID4+Pj4+IFllcywgWFhYWCBo
YXMgYmVlbiB1c2VkIGJlY2F1c2Ugd2UgZG8gbm90IGtub3cgdGhlIGZ1dHVyZSBudW1iZXINCj4g
Pj4gYXNzaWduZWQgdG8gb3VyIEktRC4NCj4gPj4+Pj4NCj4gPj4+Pj4gQWxzbyB3ZSByZWFsaXpl
ZCB3ZSBhbHNvIGluY2x1ZGVkIHRoaXMgdG8gcmVmZXIgdG8gY3J5cHRvLXR5cGVzDQo+ID4+Pj4+
IEktRCBidXQgdGhpcw0KPiA+PiBoYXMgYmVlbiBzb2x2ZWQgbm93IGluIGEgbmV3IHZlcnNpb24g
LTEyIHRoYXQgd2UgYXJlIHByZXBhcmluZyB0bw0KPiA+PiBpbmNsdWRlIHlvdXIgY29tbWVudHMu
IFdlIG5vdGljZWQgd2UgY2FuIHJlcGxhY2UgdGhlIHR5cGUgb2YgcncNCj4gPj4gY2VydC1kYXRh
PywgY2EtZGF0YSosIGNybC0gZGF0YT8gZm9yIGJpbmFyeSB3aXRob3V0IGFueSBwcm9ibGVtLg0K
PiA+Pj4+Pg0KPiA+Pj4+PiB8ICAgICAgICAgICB8ICAgICArLS1ydyBjZXJ0LWRhdGE/ICAgICAg
ICBiaW5hcnkNCj4gPj4+Pj4gfCAgICAgICAgICAgKy0tcncgcHJpdmF0ZS1rZXk/ICAgICAgICAg
ICAgYmluYXJ5DQo+ID4+Pj4+IHwgICAgICAgICAgICstLXJ3IGNhLWRhdGEqICAgICAgICAgICAg
ICAgIGJpbmFyeQ0KPiA+Pj4+PiB8ICAgICAgICAgICArLS1ydyBjcmwtZGF0YT8gICAgICAgICAg
ICAgICBiaW5hcnkNCj4gPj4+Pj4NCj4gPj4+Pj4+DQo+ID4+Pj4+PiBidXQgdGhlIHNob3cgc3Rv
cHBlciB0aGF0IG1ha2VzIGEgcHJvcGVyIHJldmlldyBvZiB0aGlzIHRvbw0KPiA+Pj4+Pj4gY29z
dGx5IGlzIHRoZQ0KPiA+PiByZWZlcmVuY2VzLiAgVGhvc2UgdG8gSUFOQSBvZiB3aGljaCB0aGVy
ZSBhcmUgc2V2ZXJhbCBJIHdhbnQgdG8NCj4gPj4gcHVyc3VlLiAgVGhlIEktRCByZWZlcmVuY2Ug
aXMgdG8gSUtFdjIgcGFyYW1ldGVycy4gU2FkbHksIHRoaXMgaXMgYQ0KPiA+PiB0aHJlZSB0aWVy
IHN0cnVjdHVyZSBhbmQgbm9vbmUgYWdyZWVzIG9uIHdoYXQgdG8gY2FsbCB0aGUgdGhpcmQgdGll
cg0KPiA+PiBzbyBJIHdpbGwgY2FsbCBpdCB0aWVyMyBoZXJlLiAgVG9wIGxldmVsIGlzIEdyb3Vw
LCBhcyBwZXIgUkZDODEyNiwNCj4gPj4gc2Vjb25kIGxldmVsIGlzIFJlZ2lzdHJ5LiAgVGhlIEkt
RCByZWZlcmVuY2UgaXMgdG8gdGhlIEdyb3VwIG9ubHkNCj4gPj4gd2hpY2ggaXMgZmluZSBpZiB0
aGUgYWN0dWFsIHJlZmVyZW5jZSB0aGVuIHNwZWNpZmllcyB0aGUgUmVnaXN0cnkgYW5kDQo+ID4+
IFRpZXIzIGJ1dCB0aGV5IG5ldmVyIGRvLCB1c3VhbGx5IGp1c3QgVGllcjMgZS5nLiBUcmFuc2Zv
cm0gVHlwZSAzDQo+ID4+IHdoaWNoIG1ha2VzIGZvciBhIGxvdCBvZiB3b3JrIGZvciB0aGUgcmVh
ZGVyLCB0b28gbXVjaCBmb3IgdGhpcyBvbmUuDQo+ID4+IFlvdSBoYXZlIHRvIGdvIGh1bnRpbmcg
aW4gYWxsIHRoZSBzZWNvbmQgbGV2ZWwgUmVnaXN0cnkgdW50aWwgeW91IGNhbg0KPiA+PiBmaW5k
IGEgbWF0Y2ggZm9yIHRoZSBUaWVyMyBpZGVudGlmaWVyLiBBbmQgdGhlcmUgYXJlIG5vIFVSTC4g
IElmIHlvdQ0KPiA+PiB3YW50IGFuIGV4YW1wbGUgdGhhdCBJIGZpbmQgZWFzeSB0byB1c2UsIGdv
IGxvb2sgYXQgUkZDODQwNyAoYXMgdXN1YWwpLg0KPiA+Pj4+Pg0KPiA+Pj4+PiBZb3XigJlyZSBy
aWdodC4gQ291bGQgeW91IHBvaW50IHRoZSBleGFjdCBwYXJ0IGF0IFJGQyA4NDA3IHdpdGggdGhh
dA0KPiA+PiBleGFtcGxlPyBXZSB3b3VsZCByZWFsbHkgYXBwcmVjaWF0ZSBpdC4NCj4gPj4+Pj4N
Cj4gPj4+Pj4gT24gdGhlIG90aGVyIGhhbmQsIHdvdWxkIGl0IGJlIGVub3VnaCB0byBpbmNsdWRl
IHRoZSBVUkwgZm9yDQo+ID4+Pj4+IFRyYW5zZm9ybQ0KPiA+PiBUeXBlIDMgaHR0cHM6Ly93d3cu
aWFuYS5vcmcvYXNzaWdubWVudHMvaWtldjItcGFyYW1ldGVycy9pa2V2Mi0NCj4gPj4gcGFyYW1l
dGVycy54aHRtbCNpa2V2Mi1wYXJhbWV0ZXJzLTcgPw0KPiA+Pj4+Pg0KPiA+Pj4+PiAoU2FtZSBm
b3IgVHJhbnNmb3JtIFR5cGUgMSwgVHJhbnNmb3JtIFR5cGUgNCkNCj4gPj4+Pj4NCj4gPj4+Pj4+
DQo+ID4+Pj4+PiBUaGUgcmVmZXJlbmNlIGZvciBpbXBvcnQgb2YgaTJuc2YtaWtlYyBnaXZlcyBh
IFlBTkcgbW9kdWxlIG5hbWU7DQo+ID4+Pj4+PiB0aGlzIG5lZWRzIHRvIGJlIHRoZSBuYW1lIG9m
IHRoZSBSRkMgdG8gYmUNCj4gPj4+Pj4NCj4gPj4+Pj4gRml4ZWQuDQo+ID4+Pj4+DQo+ID4+Pj4+
IGltcG9ydCBpZXRmLWkybnNmLWlrZWMgew0KPiA+Pj4+PiAgICAgICAgICAgICAgIHByZWZpeCBu
c2Zpa2VjOw0KPiA+Pj4+PiAgICAgICAgICAgICAgIHJlZmVyZW5jZQ0KPiA+Pj4+PiAgICAgICAg
ICAgICAgICAgICAiUkZDIFhYWFg6IFNvZnR3YXJlLURlZmluZWQgTmV0d29ya2luZw0KPiA+Pj4+
PiAgICAgICAgICAgICAgICAgIChTRE4pLWJhc2VkIElQc2VjIEZsb3cgUHJvdGVjdGlvbi4iOyB9
DQo+ID4+Pj4+DQo+ID4+Pj4+IFdlIHN0aWxsIHVzZSBYWFhYIGJlY2F1c2Ugd2UgZG8gbm90IGtu
b3cgdGhlIG51bWJlciBhc3NpZ25lZCB0bw0KPiA+Pj4+PiB0aGUgUkZDDQo+ID4+IHRvIGJlLg0K
PiA+Pj4+Pg0KPiA+Pj4+Pj4NCj4gPj4+Pj4+IFRoZSBleGFtcGxlIElQdjYgYWRkcmVzcyBpbiB0
aGUgWUFORyBtb2R1bGUgaGFzIDowOjA6IHdoaWNoIGlzDQo+ID4+Pj4+PiB1c3VhbGx5DQo+ID4+
IGp1c3QgOjoNCj4gPj4+Pj4NCj4gPj4+Pj4gRml4ZWQuDQo+ID4+Pj4+DQo+ID4+Pj4+IElmIHlv
dSBoYXZlIGFueSBmdXJ0aGVyIGNvbW1lbnRzLCBwbGVhc2UgbGV0IHVzIGtub3cgc28gd2UgY2Fu
DQo+ID4+Pj4+IGluY2x1ZGUgdGhlbSBpbiAtMTINCj4gPj4+Pj4NCj4gPj4+Pj4gQmVzdCBSZWdh
cmRzLg0KPiA+Pj4+Pj4NCj4gPj4+Pj4+IEFuZCBJIGhhdmUgc29tZSB3YXkgdG8gZ28gc3RpbGwu
DQo+ID4+Pj4+Pg0KPiA+Pj4+Pj4gVG9tIFBldGNoDQo+ID4+Pj4+Pg0KPiA+Pj4+Pj4gT24gMjIv
MTAvMjAyMCAxODozOSwgUmFmYSBNYXJpbi1Mb3BleiB3cm90ZToNCj4gPj4+Pj4+PiBEZWFyIGFs
bDoNCj4gPj4+Pj4+Pg0KPiA+Pj4+Pj4+IEFmdGVyIHJlY2VpdmluZyBhIHN1Z2dlc3Rpb24gdG8g
bWFrZSB0aGluZ3MgY2xlYXJlciBpbiB0aGUNCj4gPj4+Pj4+PiBmZWF0dXJlIGlrZWxlc3MtDQo+
ID4+IG5vdGlmaWNhdGlvbiBkZXNjcmlwdGlvbiwgd2UgaGF2ZSBqdXN0IHVwbG9hZGVkIGEgbmV3
IHZlcnNpb24gLTExDQo+ID4+IHdpdGggYSBtaW5vciBjaGFuZ2UgdG8gYWRkIHRoZSBmb2xsb3dp
bmcgdGV4dDoNCj4gPj4+Pj4+Pg0KPiA+Pj4+Pj4+IGZlYXR1cmUgaWtlbGVzcy1ub3RpZmljYXRp
b24gew0KPiA+Pj4+Pj4+ICAgICAgICAgICAgICAgZGVzY3JpcHRpb24NCj4gPj4+Pj4+PiAgICAg
ICAgICAgICAgICAgICAiVGhpcyBmZWF0dXJlIGluZGljYXRlcyB0aGF0IHRoZSBzZXJ2ZXIgc3Vw
cG9ydHMNCj4gPj4+Pj4+PiAgICAgICAgICAgICAgICAgICBnZW5lcmF0aW5nIG5vdGlmaWNhdGlv
bnMgaW4gdGhlIGlrZWxlc3MgbW9kdWxlLg0KPiA+Pj4+Pj4+DQo+ID4+Pj4+Pj4gICAgICAgICAg
ICAgICAgICAgVG8gZW5zdXJlIGJyb2FkZXIgYXBwbGljYWJpbGl0eSBvZiB0aGlzIG1vZHVsZSwN
Cj4gPj4+Pj4+PiAgICAgICAgICAgICAgICAgICB0aGUgbm90aWZpY2F0aW9ucyBhcmUgbWFya2Vk
IGFzIGEgZmVhdHVyZS4NCj4gPj4+Pj4+PiAgICAgICAgICAgICAgICAgICBGb3IgdGhlIGltcGxl
bWVudGF0aW9uIG9mIGlrZWxlc3MgY2FzZSwNCj4gPj4+Pj4+PiAgICAgICAgICAgICAgICAgICB0
aGUgTlNGIGlzIGV4cGVjdGVkIHRvIGltcGxlbWVudCB0aGlzDQo+ID4+Pj4+Pj4gICAgICAgICAg
ICAgICAgICAgZmVhdHVyZS4iOw0KPiA+Pj4+Pj4+ICAgICAgICAgICB9DQo+ID4+Pj4+Pj4NCj4g
Pj4+Pj4+PiBCZXN0IFJlZ2FyZHMuDQo+ID4+Pj4+Pj4NCj4gPj4+Pj4+Pj4gSW5pY2lvIGRlbCBt
ZW5zYWplIHJlZW52aWFkbzoNCj4gPj4+Pj4+Pj4NCj4gPj4+Pj4+Pj4gRGU6IGludGVybmV0LWRy
YWZ0c0BpZXRmLm9yZw0KPiA+Pj4+Pj4+PiBBc3VudG86IE5ldyBWZXJzaW9uIE5vdGlmaWNhdGlv
biBmb3INCj4gPj4+Pj4+Pj4gZHJhZnQtaWV0Zi1pMm5zZi1zZG4taXBzZWMtZmxvdy1wcm90ZWN0
aW9uLTExLnR4dA0KPiA+Pj4+Pj4+PiBGZWNoYTogMjIgZGUgb2N0dWJyZSBkZSAyMDIwLCAxNToz
Mjo1MCBDRVNUDQo+ID4+Pj4+Pj4+IFBhcmE6ICJGZXJuYW5kbyBQZXJlbmlndWV6LUdhcmNpYSIN
Cj4gPj4+Pj4+Pj4gPGZlcm5hbmRvLnBlcmVuaWd1ZXpAY3VkLnVwY3QuZXM+LCAiUmFmYWVsIExv
cGV6IiA8cmFmYUB1bS5lcz4sDQo+ID4+Pj4+Pj4+ICJHYWJyaWVsIExvcGV6LU1pbGxhbiIgPGdh
YmlsbUB1bS5lcz4sICJSYWZhIE1hcmluLUxvcGV6Ig0KPiA+Pj4+Pj4+PiA8cmFmYUB1bS5lcz4N
Cj4gPj4+Pj4+Pj4NCj4gPj4+Pj4+Pj4NCj4gPj4+Pj4+Pj4gQSBuZXcgdmVyc2lvbiBvZiBJLUQs
DQo+ID4+Pj4+Pj4+IGRyYWZ0LWlldGYtaTJuc2Ytc2RuLWlwc2VjLWZsb3ctcHJvdGVjdGlvbi0x
MS50eHQNCj4gPj4+Pj4+Pj4gaGFzIGJlZW4gc3VjY2Vzc2Z1bGx5IHN1Ym1pdHRlZCBieSBSYWZh
IE1hcmluLUxvcGV6IGFuZCBwb3N0ZWQNCj4gPj4+Pj4+Pj4gdG8gdGhlIElFVEYgcmVwb3NpdG9y
eS4NCj4gPj4+Pj4+Pj4NCj4gPj4+Pj4+Pj4gTmFtZToJCWRyYWZ0LWlldGYtaTJuc2Ytc2RuLWlw
c2VjLWZsb3ctcHJvdGVjdGlvbg0KPiA+Pj4+Pj4+PiBSZXZpc2lvbjoJMTENCj4gPj4+Pj4+Pj4g
VGl0bGU6CQlTb2Z0d2FyZS1EZWZpbmVkIE5ldHdvcmtpbmcgKFNETiktYmFzZWQgSVBzZWMgRmxv
dw0KPiA+PiBQcm90ZWN0aW9uDQo+ID4+Pj4+Pj4+IERvY3VtZW50IGRhdGU6CTIwMjAtMTAtMjIN
Cj4gPj4+Pj4+Pj4gR3JvdXA6CQlpMm5zZg0KPiA+Pj4+Pj4+PiBQYWdlczoJCTkyDQo+ID4+Pj4+
Pj4+IFVSTDogICAgICAgICAgICBodHRwczovL3d3dy5pZXRmLm9yZy9hcmNoaXZlL2lkL2RyYWZ0
LWlldGYtaTJuc2Ytc2RuLQ0KPiBpcHNlYy0NCj4gPj4gZmxvdy1wcm90ZWN0aW9uLTExLnR4dA0K
PiA+Pj4+Pj4+PiBTdGF0dXM6ICAgICAgICAgaHR0cHM6Ly9kYXRhdHJhY2tlci5pZXRmLm9yZy9k
b2MvZHJhZnQtaWV0Zi1pMm5zZi1zZG4tDQo+IGlwc2VjLQ0KPiA+PiBmbG93LXByb3RlY3Rpb24v
DQo+ID4+Pj4+Pj4+IEh0bWxpemVkOiAgICAgICBodHRwczovL2RhdGF0cmFja2VyLmlldGYub3Jn
L2RvYy9odG1sL2RyYWZ0LWlldGYtaTJuc2YtDQo+IHNkbi0NCj4gPj4gaXBzZWMtZmxvdy1wcm90
ZWN0aW9uDQo+ID4+Pj4+Pj4+IEh0bWxpemVkOiAgICAgICBodHRwczovL3Rvb2xzLmlldGYub3Jn
L2h0bWwvZHJhZnQtaWV0Zi1pMm5zZi1zZG4taXBzZWMtDQo+IGZsb3ctDQo+ID4+IHByb3RlY3Rp
b24tMTENCj4gPj4+Pj4+Pj4gRGlmZjogICAgICAgICAgIGh0dHBzOi8vd3d3LmlldGYub3JnL3Jm
Y2RpZmY/dXJsMj1kcmFmdC1pZXRmLWkybnNmLXNkbi0NCj4gaXBzZWMtDQo+ID4+IGZsb3ctcHJv
dGVjdGlvbi0xMQ0KPiA+Pj4+Pj4+Pg0KPiA+Pj4+Pj4+PiBBYnN0cmFjdDoNCj4gPj4+Pj4+Pj4g
ICAgIFRoaXMgZG9jdW1lbnQgZGVzY3JpYmVzIGhvdyB0byBwcm92aWRlIElQc2VjLWJhc2VkIGZs
b3cNCj4gcHJvdGVjdGlvbg0KPiA+Pj4+Pj4+PiAgICAgKGludGVncml0eSBhbmQgY29uZmlkZW50
aWFsaXR5KSBieSBtZWFucyBvZiBhbiBJbnRlcmZhY2UgdG8gTmV0d29yaw0KPiA+Pj4+Pj4+PiAg
ICAgU2VjdXJpdHkgRnVuY3Rpb24gKEkyTlNGKSBjb250cm9sbGVyLiAgSXQgY29uc2lkZXJzIHR3
byBtYWluIHdlbGwtDQo+ID4+Pj4+Pj4+ICAgICBrbm93biBzY2VuYXJpb3MgaW4gSVBzZWM6IChp
KSBnYXRld2F5LXRvLWdhdGV3YXkgYW5kIChpaSkgaG9zdC10by0NCj4gPj4+Pj4+Pj4gICAgIGhv
c3QuICBUaGUgc2VydmljZSBkZXNjcmliZWQgaW4gdGhpcyBkb2N1bWVudCBhbGxvd3MgdGhlDQo+
ID4+Pj4+Pj4+ICAgICBjb25maWd1cmF0aW9uIGFuZCBtb25pdG9yaW5nIG9mIElQc2VjIFNlY3Vy
aXR5IEFzc29jaWF0aW9ucyAoU0FzKQ0KPiA+Pj4+Pj4+PiAgICAgZnJvbSBhIEkyTlNGIENvbnRy
b2xsZXIgdG8gb25lIG9yIHNldmVyYWwgZmxvdy1iYXNlZA0KPiA+Pj4+Pj4+PiBOZXR3b3JrDQo+
ID4+IFNlY3VyaXR5DQo+ID4+Pj4+Pj4+ICAgICBGdW5jdGlvbnMgKE5TRnMpIHRoYXQgcmVseSBv
biBJUHNlYyB0byBwcm90ZWN0IGRhdGEgdHJhZmZpYy4NCj4gPj4+Pj4+Pj4NCj4gPj4+Pj4+Pj4g
ICAgIFRoZSBkb2N1bWVudCBmb2N1c2VzIG9uIHRoZSBJMk5TRiBOU0YtZmFjaW5nIGludGVyZmFj
ZSBieQ0KPiBwcm92aWRpbmcNCj4gPj4+Pj4+Pj4gICAgIFlBTkcgZGF0YSBtb2RlbHMgZm9yIGNv
bmZpZ3VyaW5nIHRoZSBJUHNlYyBkYXRhYmFzZXMgKFNQRCwNCj4gPj4+Pj4+Pj4gU0FELA0KPiA+
PiBQQUQpDQo+ID4+Pj4+Pj4+ICAgICBhbmQgSUtFdjIuICBUaGlzIGFsbG93cyBJUHNlYyBTQSBl
c3RhYmxpc2htZW50IHdpdGggbWluaW1hbA0KPiA+Pj4+Pj4+PiAgICAgaW50ZXJ2ZW50aW9uIGJ5
IHRoZSBuZXR3b3JrIGFkbWluaXN0cmF0b3IuICBJdCBkb2VzIG5vdCBkZWZpbmUgYW55DQo+ID4+
Pj4+Pj4+ICAgICBuZXcgcHJvdG9jb2wuDQo+ID4+Pj4+Pj4+DQo+ID4+Pj4+Pj4+DQo+ID4+Pj4+
Pj4+DQo+ID4+Pj4+Pj4+DQo+ID4+Pj4+Pj4+IFBsZWFzZSBub3RlIHRoYXQgaXQgbWF5IHRha2Ug
YSBjb3VwbGUgb2YgbWludXRlcyBmcm9tIHRoZSB0aW1lDQo+ID4+Pj4+Pj4+IG9mIHN1Ym1pc3Np
b24gdW50aWwgdGhlIGh0bWxpemVkIHZlcnNpb24gYW5kIGRpZmYgYXJlIGF2YWlsYWJsZQ0KPiA+
Pj4+Pj4+PiBhdA0KPiA+PiB0b29scy5pZXRmLm9yZy4NCj4gPj4+Pj4+Pj4NCj4gPj4+Pj4+Pj4g
VGhlIElFVEYgU2VjcmV0YXJpYXQNCj4gPj4+Pj4+Pj4NCj4gPj4+Pj4+Pj4NCj4gPj4+Pj4+Pg0K
PiA+Pj4+Pj4+IC0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0NCj4gPj4+Pj4+PiBSYWZhIE1hcmluLUxvcGV6LCBQaEQNCj4gPj4+Pj4+PiBEZXB0
LiBJbmZvcm1hdGlvbiBhbmQgQ29tbXVuaWNhdGlvbnMgRW5naW5lZXJpbmcgKERJSUMpIEZhY3Vs
dHkNCj4gPj4+Pj4+PiBvZiBDb21wdXRlciBTY2llbmNlLVVuaXZlcnNpdHkgb2YgTXVyY2lhDQo+
ID4+Pj4+Pj4gMzAxMDAgTXVyY2lhIC0gU3BhaW4NCj4gPj4+Pj4+PiBUZWxmOiArMzQ4Njg4ODg1
MDEgRmF4OiArMzQ4Njg4ODQxNTEgZS1tYWlsOiByYWZhQHVtLmVzDQo+ID4+Pj4+Pj4gLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQ0KPiA+Pj4+
Pj4+DQo+ID4+Pj4+Pj4NCj4gPj4+Pj4+Pg0KPiA+Pj4+Pj4+DQo+ID4+Pj4+Pj4NCj4gPj4+Pj4+
Pg0KPiA+Pj4+Pj4+DQo+ID4+Pj4+DQo+ID4+Pj4+IC0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0NCj4gPj4+Pj4gUmFmYSBNYXJpbi1Mb3Bleiwg
UGhEDQo+ID4+Pj4+IERlcHQuIEluZm9ybWF0aW9uIGFuZCBDb21tdW5pY2F0aW9ucyBFbmdpbmVl
cmluZyAoRElJQykgRmFjdWx0eSBvZg0KPiA+Pj4+PiBDb21wdXRlciBTY2llbmNlLVVuaXZlcnNp
dHkgb2YgTXVyY2lhDQo+ID4+Pj4+IDMwMTAwIE11cmNpYSAtIFNwYWluDQo+ID4+Pj4+IFRlbGY6
ICszNDg2ODg4ODUwMSBGYXg6ICszNDg2ODg4NDE1MSBlLW1haWw6IHJhZmFAdW0uZXMNCj4gPj4+
Pj4gLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LQ0KPiA+Pj4+Pg0KPiA+Pj4+Pg0KPiA+Pj4+Pg0KPiA+Pj4+Pg0KPiA+Pj4+Pg0KPiA+Pj4NCj4g
Pj4+IC0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0NCj4gPj4+IFJhZmEgTWFyaW4tTG9wZXosIFBoRA0KPiA+Pj4gRGVwdC4gSW5mb3JtYXRpb24g
YW5kIENvbW11bmljYXRpb25zIEVuZ2luZWVyaW5nIChESUlDKSBGYWN1bHR5IG9mDQo+ID4+PiBD
b21wdXRlciBTY2llbmNlLVVuaXZlcnNpdHkgb2YgTXVyY2lhDQo+ID4+PiAzMDEwMCBNdXJjaWEg
LSBTcGFpbg0KPiA+Pj4gVGVsZjogKzM0ODY4ODg4NTAxIEZheDogKzM0ODY4ODg0MTUxIGUtbWFp
bDogcmFmYUB1bS5lcw0KPiA+Pj4gLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLQ0KPiA+Pj4NCj4gPj4+DQo+ID4+Pg0KPiA+Pj4NCj4gPj4+DQo+
ID4+DQo+ID4+IC0tDQo+ID4+IGxhc3QtY2FsbCBtYWlsaW5nIGxpc3QNCj4gPj4gbGFzdC1jYWxs
QGlldGYub3JnDQo+ID4+IGh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vbGFz
dC1jYWxsDQo=


From nobody Fri Oct 30 15:42:26 2020
Return-Path: <kivinen@iki.fi>
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 755D33A12A4; Fri, 30 Oct 2020 15:42:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.346
X-Spam-Level: 
X-Spam-Status: No, score=-2.346 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, NICE_REPLY_A=-0.247, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=iki.fi
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 3s6gASlk6a_9; Fri, 30 Oct 2020 15:42:19 -0700 (PDT)
Received: from meesny.iki.fi (meesny.iki.fi [195.140.195.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 79B323A03F2; Fri, 30 Oct 2020 15:42:16 -0700 (PDT)
Received: from fireball.acr.fi (fireball.kivinen.iki.fi [IPv6:2001:1bc8:100d::2]) (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) (Authenticated sender: kivinen) by meesny.iki.fi (Postfix) with ESMTPSA id 477C820ACC; Sat, 31 Oct 2020 00:42:14 +0200 (EET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=iki.fi; s=meesny; t=1604097734; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=JdObjbwBpmusZoxDTDpANds47ddtMWZ6EGdRk7tNJBU=; b=Qthps85cGvEBtLXbiXtbawX4jdWoJOgIu2afkudLq59U7HBr+GCfBUNtyw+BE8gWNt/oUm X7Xasi9w7kXO4aixrUYYHL7RTcHsug3GR9Jik3sfMk7u6WeLNMmemvqYxeDRn2rNuRS7JX 1skWp3yIc+KgI9MyjZyr0qSa8ifzs+k=
Received: by fireball.acr.fi (Postfix, from userid 15204) id 1CBEF25C132D; Sat, 31 Oct 2020 00:42:13 +0200 (EET)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <24476.38596.868667.906930@fireball.acr.fi>
Date: Sat, 31 Oct 2020 00:42:12 +0200
From: Tero Kivinen <kivinen@iki.fi>
To: Roman Danyliw <rdd@cert.org>
Cc: tom petch <daedulus@btconnect.com>, "ipsec\@ietf.org" <ipsec@ietf.org>, "i2nsf\@ietf.org" <i2nsf@ietf.org>, Gabriel Lopez <gabilm@um.es>, "ynir.ietf\@gmail.com" <ynir.ietf@gmail.com>, Fernando Pereniguez-Garcia <fernando.pereniguez@cud.upct.es>, "last-call\@ietf.org" <last-call@ietf.org>, Rafa Marin-Lopez <rafa@um.es>
In-Reply-To: <834a668ac559460a9f356bbb6c16b8fd@cert.org>
References: <160337357077.29083.9236626834026808055@ietfa.amsl.com> <EE5AB669-73BB-4517-A6F4-23B7807FB36E@um.es> <5F9815D1.9010303@btconnect.com> <DDE550B1-9A9E-4954-B6F9-C0A33ECE1275@um.es> <5F99B221.3040504@btconnect.com> <56155C91-BFE8-4BA9-A55C-46B12E59CD94@um.es> <5F9AEFD3.90903@btconnect.com> <059aaae84a354411ad1023afa2a837ba@cert.org> <5F9BF578.6000101@btconnect.com> <834a668ac559460a9f356bbb6c16b8fd@cert.org>
X-Mailer: VM 8.2.0b under 26.3 (x86_64--netbsd)
X-Edit-Time: 39 min
X-Total-Time: 39 min
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=iki.fi; s=meesny; t=1604097734; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=JdObjbwBpmusZoxDTDpANds47ddtMWZ6EGdRk7tNJBU=; b=cCiWRoA4wkfk29YI9mqXeRtZbM79247ul1IHHL1n31pmrYldwRyXQY9Gd5Z1QVf7t7L8RA Ut2BoVoXsIJUcXPqbWdDyv+3VY6JpxfPxEwyfIsxFHsJUtE38zWhv6GeQYRKK/OTJ8atmT jI70MBBOeAdMeKWoUPqwGxyJ6DaW/XE=
ARC-Authentication-Results: i=1; ORIGINATING; auth=pass smtp.auth=kivinen smtp.mailfrom=kivinen@iki.fi
ARC-Seal: i=1; s=meesny; d=iki.fi; t=1604097734; a=rsa-sha256; cv=none; b=NghmXMGVEQx7tqG2ifbLiAJ0Xp1YHyatHOkbvjhffU04VzgaoDTIQGdPHZ3S0kSLNNVDSG agbYObjYa0tFt62UBoJdmuIJfIRNKMEE2Cdvm7PHZdTTTTVzkk1bbT+Y8W9WpPMPRhQqWr y+H3a1XCUwmqQ/91HwhthkaP0k4yOCA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2nsf/p2c0LmyAWzA2vrV1JwE7EWTbYo4>
Subject: Re: [I2nsf] [IPsec] [Last-Call] New Version Notification for draft-ietf-i2nsf-sdn-ipsec-flow-protection-11.txt
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: Fri, 30 Oct 2020 22:42:22 -0000

Roman Danyliw writes:
> > >> It seems to me that the IANA entries for IKEv2 are incomplete.
> > >> RFC8247 does a fine job of specifying algorithms and adding
> > >> information such as status (MUST/SHOULD+), IoT, AEAD and so on,
> > >> information which is not present on IANA.  The policy for, e.g.
> > >> Transform Type 1, is expert review and entries have been added via
> > >> draft-smyslov-esp-gont but the IANA entries lack this information
> > >> and, looking at the I-D, I see no such information (nor is there any
> > >> reason for it to be there).  Yet draft-ietf-i2nsf-sdn... needs
> > >> this information as references in the YANG module show. 

I am lost what information is missing from the IANA registry. The
registry do include numbers from draft-smyslov-esp-gost document. The
RFC8247 says:
----------------------------------------------------------------------
1.3.  Updating Algorithm Requirement Levels
...
    .... As a result, any algorithm listed at the IKEv2
   IANA registry not mentioned in this document MAY be implemented.
----------------------------------------------------------------------
I.e., all algorithms not listed there are MAY to implement.

But I do not see any reason why the yang module should provide any
other than pointer to the IANA registry, and the IANA registry already
has pointer to the RFC8247 to indicate the requirement levels for
algorithms. 

> > >> It seems to me that this is a similar situation to that which the TLS
> > >> WG found itself in and which led to a revision of the TLS IANA
> > >> entries to provide what was needed via additional columns.

There was some requests to modify the IANA registry while we were
publishing RFC 8247 and the WG decided against it, and instead decided
to provide pointer to the RFC 8211 and RFC 8247 in the notes section.

The reason for that is that duplicating information always causes
problems, and because there is no (public) history of the IANA
registries, there is no way of finding out when and why specific
change to the registry was done unless there happens to be RFC that
actually did that change.

I myself as an IANA expert of those registries do think it is better
that working group will do RFC that will update the levels, and that
will leave audit trail and public working group mailing list
discussion about the changes. 

> > >> I think that the IANA pages for IKEv2 need revising so that that
> > >> additional information that RFC8247 provides is required as
> > >> additional columns in the IANA entries at least for Type 1, Type 2,
> > >> Type 3, Type 4 and Authentication Method.

I fail to see why does that information need to be in the IANA
registry? This is YANG model for IPsec, it should just refer to the
IANA registry about the mapping from algorithms to numbers and other
way around, but whether the algorithm is recommended or not, does not
belong to the YANG model, as that is not something that can be
modified by configuration or be part of running state.

This document seems to have wierd text in it:

      typedef encryption-algorithm-type {
        type uint16;
        description
          "The encryption algorithm is specified with a 16-bit
          number extracted from IANA Registry. The acceptable
          values MUST follow the requirement levels for
          encryption algorithms for ESP and IKEv2.";

I do not see what the last sentence of the text is trying to say? Does
it mean that this yang model cannot be shown of running configuration
where someone is using one the algorithms not considered safe anymore?
In ietf we usually just try to say what implementors are implementing,
we do not that often limit what adminstrators can configure. If the
implementation happens to implement one of those weak ciphers for
example for talking to one obsoleted old hardware that only supports
them, then I do not see why this yang model should forbid showing
running status of such configuration.

I think this document should just say that the algorithm numbers are
from the IANA registry, and nothing more. There might be informal
reference to the RFC 8221, and RFC 8247 but even that should not be
needed, as anybody implementing IKEv2 or ESP will already follow those
and only implement the algorithms from there that they seem proper. In
some cases that selection might include algorithms which are on SHOULD
NOT or even MUST NOT, if the backward compatibility to obsolete
hardware is more important than conformance.

> > This I-D, as you quote, points to RFC8247 for guidance and that is
> > fine. But security moves on and new algorithms will be needed and
> > this I-D also points to the IANA registry, which is Expert Review,
> > where new entries have been added already; and for those the IANA
> > Registry gives no guidance and the I-D that IANA references for
> > the new entries - written by the Expert Reviewer! - also gives no
> > guidance. Over time we are likely to accrue algorithms with no
> > guidance unless and until an RFC8247-bis appears or we require
> > IANA to have columns for guidance. Currently the new algorithms
> > are GOST and so perhaps of limited interest but on the TLS list I
> > am always seeing new algorithms appear and there the new IANA
> > entry is required to give guidance. My sense is that IKEv2 is a
> > bit slower to take up new ones but, as with RFC8247, it does
> > eventually.

The original cryptographic algorithm impelemtation requirements for
ESP and AH was published as RFC4305 in 2007. It was replaced with
RFC7321 in 2014, and that was replaced with RFC8221 in 2017. For IKEv2
we skipped the 2014 update, as that was not needed. We do have plans
to keep that draft up to date, and update it when there is need for
that, most likely in next 5 years or so, provided that implementation
status of some of new algorithms progresses favorably.

> > I think that users need those extra columns that RFC8247 provides
> > on the IANA website so that when new algorithms are added by
> > Expert Review, then that guidance must be added as well. This is
> > what the TLS WG came round to and I think that IKEv2 needs to do
> > the same.

I as an Expert does not want to decide whether the individual request
to add new 3rot13 cipher to the IANA registry should be MUST NOT,
SHOULD NOT, MAY or what. If the field is in the IANA registry then
whoever requests to add information to there can request whatever
value they want for that field too. Of course as an IANA expert I can
reject that by saying that 3rot13 is not MUST, but it is MUST NOT
algorithm, and then we can have discussion about that.

I rather have that discussion in the working group when we are
updating the requirements document next time. And as I said IANA
registries do not have any (public) history, or any way of finding out
why they got changed and who did the change. There has happened some
changes in the registry where I as an IANA Expert was not aware of at
all...

And if I need to find out when ENCR_MAGMA_MGM_KTREE was added or when
some of those earlier algorithms was renamed, I need to go to my
private mail archives. 
-- 
kivinen@iki.fi


From nobody Fri Oct 30 18:12:51 2020
Return-Path: <rdd@cert.org>
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 D77773A14A3; Fri, 30 Oct 2020 18:12:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level: 
X-Spam-Status: No, score=-2.099 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, 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 (1024-bit key) header.d=cert.org
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 x0yzAyzJfa_U; Fri, 30 Oct 2020 18:12:44 -0700 (PDT)
Received: from veto.sei.cmu.edu (veto.sei.cmu.edu [147.72.252.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3487F3A14A1; Fri, 30 Oct 2020 18:12:43 -0700 (PDT)
Received: from delp.sei.cmu.edu (delp.sei.cmu.edu [10.64.21.31]) by veto.sei.cmu.edu (8.14.7/8.14.7) with ESMTP id 09V1CYfR003916; Fri, 30 Oct 2020 21:12:34 -0400
DKIM-Filter: OpenDKIM Filter v2.11.0 veto.sei.cmu.edu 09V1CYfR003916
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cert.org; s=yc2bmwvrj62m; t=1604106755; bh=RFkuzr3HWVoGN8xSoMUI8oY29LQEwrQaNrkKm+N7uxA=; h=From:To:CC:Subject:Date:References:In-Reply-To:From; b=Q2AxARZ+zbJ6UJyrQrQxVLlh6TILgsK/SS4lwAkbYNDjtPOyzguv/HLuVB+EuAJo3 QTiecJppMnuMyfrEuII2RASuxRc5PdQTO9OqZfp7+y2p1P0Ma7lT7X14SyQE2oc0ms GSXbQFcEKdOB7oneVB4zSYihGPtnesGajSV2ZVjs=
Received: from MURIEL.ad.sei.cmu.edu (muriel.ad.sei.cmu.edu [147.72.252.47]) by delp.sei.cmu.edu (8.14.7/8.14.7) with ESMTP id 09V1CUmr018108; Fri, 30 Oct 2020 21:12:31 -0400
Received: from MORRIS.ad.sei.cmu.edu (147.72.252.46) by MURIEL.ad.sei.cmu.edu (147.72.252.47) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2106.2; Fri, 30 Oct 2020 21:12:30 -0400
Received: from MORRIS.ad.sei.cmu.edu ([fe80::555b:9498:552e:d1bb]) by MORRIS.ad.sei.cmu.edu ([fe80::555b:9498:552e:d1bb%13]) with mapi id 15.01.2106.002; Fri, 30 Oct 2020 21:12:30 -0400
From: Roman Danyliw <rdd@cert.org>
To: Tero Kivinen <kivinen@iki.fi>
CC: Fernando Pereniguez-Garcia <fernando.pereniguez@cud.upct.es>, "i2nsf@ietf.org" <i2nsf@ietf.org>, Gabriel Lopez <gabilm@um.es>, "ynir.ietf@gmail.com" <ynir.ietf@gmail.com>, "ipsec@ietf.org" <ipsec@ietf.org>, "last-call@ietf.org" <last-call@ietf.org>, Rafa Marin-Lopez <rafa@um.es>, tom petch <daedulus@btconnect.com>
Thread-Topic: [IPsec] [Last-Call] New Version Notification for draft-ietf-i2nsf-sdn-ipsec-flow-protection-11.txt
Thread-Index: AQHWreX0c88acJXFBk2yYgVjsJF2bKmvCuOA///cU0CAAVuUAP//zZ2AgADyqwD//+IF8A==
Date: Sat, 31 Oct 2020 01:12:29 +0000
Message-ID: <4cd0a090e912445280b33d2842714cb1@cert.org>
References: <160337357077.29083.9236626834026808055@ietfa.amsl.com> <EE5AB669-73BB-4517-A6F4-23B7807FB36E@um.es> <5F9815D1.9010303@btconnect.com> <DDE550B1-9A9E-4954-B6F9-C0A33ECE1275@um.es> <5F99B221.3040504@btconnect.com> <56155C91-BFE8-4BA9-A55C-46B12E59CD94@um.es> <5F9AEFD3.90903@btconnect.com> <059aaae84a354411ad1023afa2a837ba@cert.org> <5F9BF578.6000101@btconnect.com> <834a668ac559460a9f356bbb6c16b8fd@cert.org> <24476.38596.868667.906930@fireball.acr.fi>
In-Reply-To: <24476.38596.868667.906930@fireball.acr.fi>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.64.202.126]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2nsf/W-aZWBUynxD25jEv4M7f7tpc0z4>
Subject: Re: [I2nsf] [IPsec] [Last-Call] New Version Notification for draft-ietf-i2nsf-sdn-ipsec-flow-protection-11.txt
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, 31 Oct 2020 01:12:47 -0000

Hi Tero!

> -----Original Message-----
> From: IPsec <ipsec-bounces@ietf.org> On Behalf Of Tero Kivinen
> Sent: Friday, October 30, 2020 6:42 PM
> To: Roman Danyliw <rdd@cert.org>
> Cc: Fernando Pereniguez-Garcia <fernando.pereniguez@cud.upct.es>;
> i2nsf@ietf.org; Gabriel Lopez <gabilm@um.es>; ynir.ietf@gmail.com;
> ipsec@ietf.org; last-call@ietf.org; Rafa Marin-Lopez <rafa@um.es>; tom pe=
tch
> <daedulus@btconnect.com>
> Subject: Re: [IPsec] [Last-Call] New Version Notification for draft-ietf-=
i2nsf-sdn-
> ipsec-flow-protection-11.txt
>=20

> Roman Danyliw writes:
> > > >> It seems to me that the IANA entries for IKEv2 are incomplete.
> > > >> RFC8247 does a fine job of specifying algorithms and adding
> > > >> information such as status (MUST/SHOULD+), IoT, AEAD and so on,
> > > >> information which is not present on IANA.  The policy for, e.g.
> > > >> Transform Type 1, is expert review and entries have been added
> > > >> via draft-smyslov-esp-gont but the IANA entries lack this
> > > >> information and, looking at the I-D, I see no such information
> > > >> (nor is there any reason for it to be there).  Yet
> > > >> draft-ietf-i2nsf-sdn... needs this information as references in th=
e YANG
> module show.
>=20
> I am lost what information is missing from the IANA registry.=20

Thanks for the analysis and feedback.

I think the deep threading may have confused who said what.  The above snip=
 and all of the snips below are from Tom's assessment of the IANA registry =
situation (https://mailarchive.ietf.org/arch/msg/last-call/Cg66LRwtJjhJ5zNe=
8AEBWqKDll0/ and https://mailarchive.ietf.org/arch/msg/last-call/MMO9NsRif_=
x1WkGbJFlgKiLOGYQ/)=20

My feedback in the earlier in the part of the thread (https://mailarchive.i=
etf.org/arch/msg/last-call/vSU21Yqbczthq9Uii0N0roHQI7c/) was that RFC8247 i=
s cited by draft-ietf-i2nsf-sdn-ipsec-flow-protection to describe implement=
ation requirements (as represented in the YANG module) and that no IANA cha=
nges should be needed.

In a follow-on messages (https://mailarchive.ietf.org/arch/msg/last-call/7e=
C7LH9_EWHxkA22YbST6Ghc4tc/) which added ipsec@ietf, I was noting that IPSec=
me is the WG with expertise and scope  that is best positioned to discuss m=
anagement of the IKE registries

Regards,
Roman

> The registry do
> include numbers from draft-smyslov-esp-gost document. The
> RFC8247 says:
> ----------------------------------------------------------------------
> 1.3.  Updating Algorithm Requirement Levels ...
>     .... As a result, any algorithm listed at the IKEv2
>    IANA registry not mentioned in this document MAY be implemented.
> ----------------------------------------------------------------------
> I.e., all algorithms not listed there are MAY to implement.
>=20
> But I do not see any reason why the yang module should provide any other
> than pointer to the IANA registry, and the IANA registry already has poin=
ter to
> the RFC8247 to indicate the requirement levels for algorithms.
>=20
> > > >> It seems to me that this is a similar situation to that which the
> > > >> TLS WG found itself in and which led to a revision of the TLS
> > > >> IANA entries to provide what was needed via additional columns.
>=20
> There was some requests to modify the IANA registry while we were publish=
ing
> RFC 8247 and the WG decided against it, and instead decided to provide
> pointer to the RFC 8211 and RFC 8247 in the notes section.
>=20
> The reason for that is that duplicating information always causes problem=
s, and
> because there is no (public) history of the IANA registries, there is no =
way of
> finding out when and why specific change to the registry was done unless =
there
> happens to be RFC that actually did that change.
>=20
> I myself as an IANA expert of those registries do think it is better that=
 working
> group will do RFC that will update the levels, and that will leave audit =
trail and
> public working group mailing list discussion about the changes.
>=20
> > > >> I think that the IANA pages for IKEv2 need revising so that that
> > > >> additional information that RFC8247 provides is required as
> > > >> additional columns in the IANA entries at least for Type 1, Type
> > > >> 2, Type 3, Type 4 and Authentication Method.
>=20
> I fail to see why does that information need to be in the IANA registry? =
This is
> YANG model for IPsec, it should just refer to the IANA registry about the
> mapping from algorithms to numbers and other way around, but whether the
> algorithm is recommended or not, does not belong to the YANG model, as th=
at
> is not something that can be modified by configuration or be part of runn=
ing
> state.
>=20
> This document seems to have wierd text in it:
>=20
>       typedef encryption-algorithm-type {
>         type uint16;
>         description
>           "The encryption algorithm is specified with a 16-bit
>           number extracted from IANA Registry. The acceptable
>           values MUST follow the requirement levels for
>           encryption algorithms for ESP and IKEv2.";
>=20
> I do not see what the last sentence of the text is trying to say? Does it=
 mean
> that this yang model cannot be shown of running configuration where someo=
ne
> is using one the algorithms not considered safe anymore?
> In ietf we usually just try to say what implementors are implementing, we=
 do
> not that often limit what adminstrators can configure. If the implementat=
ion
> happens to implement one of those weak ciphers for example for talking to=
 one
> obsoleted old hardware that only supports them, then I do not see why thi=
s
> yang model should forbid showing running status of such configuration.
>=20
> I think this document should just say that the algorithm numbers are from=
 the
> IANA registry, and nothing more. There might be informal reference to the=
 RFC
> 8221, and RFC 8247 but even that should not be needed, as anybody
> implementing IKEv2 or ESP will already follow those and only implement th=
e
> algorithms from there that they seem proper. In some cases that selection
> might include algorithms which are on SHOULD NOT or even MUST NOT, if the
> backward compatibility to obsolete hardware is more important than
> conformance.
>=20
> > > This I-D, as you quote, points to RFC8247 for guidance and that is
> > > fine. But security moves on and new algorithms will be needed and
> > > this I-D also points to the IANA registry, which is Expert Review,
> > > where new entries have been added already; and for those the IANA
> > > Registry gives no guidance and the I-D that IANA references for the
> > > new entries - written by the Expert Reviewer! - also gives no
> > > guidance. Over time we are likely to accrue algorithms with no
> > > guidance unless and until an RFC8247-bis appears or we require IANA
> > > to have columns for guidance. Currently the new algorithms are GOST
> > > and so perhaps of limited interest but on the TLS list I am always
> > > seeing new algorithms appear and there the new IANA entry is
> > > required to give guidance. My sense is that IKEv2 is a bit slower to
> > > take up new ones but, as with RFC8247, it does eventually.
>=20
> The original cryptographic algorithm impelemtation requirements for ESP a=
nd
> AH was published as RFC4305 in 2007. It was replaced with
> RFC7321 in 2014, and that was replaced with RFC8221 in 2017. For IKEv2 we
> skipped the 2014 update, as that was not needed. We do have plans to keep
> that draft up to date, and update it when there is need for that, most li=
kely in
> next 5 years or so, provided that implementation status of some of new
> algorithms progresses favorably.
>=20
> > > I think that users need those extra columns that RFC8247 provides on
> > > the IANA website so that when new algorithms are added by Expert
> > > Review, then that guidance must be added as well. This is what the
> > > TLS WG came round to and I think that IKEv2 needs to do the same.
>=20
> I as an Expert does not want to decide whether the individual request to =
add
> new 3rot13 cipher to the IANA registry should be MUST NOT, SHOULD NOT,
> MAY or what. If the field is in the IANA registry then whoever requests t=
o add
> information to there can request whatever value they want for that field =
too.
> Of course as an IANA expert I can reject that by saying that 3rot13 is no=
t MUST,
> but it is MUST NOT algorithm, and then we can have discussion about that.
>=20
> I rather have that discussion in the working group when we are updating t=
he
> requirements document next time. And as I said IANA registries do not hav=
e
> any (public) history, or any way of finding out why they got changed and =
who
> did the change. There has happened some changes in the registry where I a=
s an
> IANA Expert was not aware of at all...
>=20
> And if I need to find out when ENCR_MAGMA_MGM_KTREE was added or
> when some of those earlier algorithms was renamed, I need to go to my pri=
vate
> mail archives.
> --
> kivinen@iki.fi
>=20
> _______________________________________________
> IPsec mailing list
> IPsec@ietf.org
> https://www.ietf.org/mailman/listinfo/ipsec


From nobody Fri Oct 30 19:47:28 2020
Return-Path: <rdd@cert.org>
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 42B853A150B for <i2nsf@ietfa.amsl.com>; Fri, 30 Oct 2020 19:47:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level: 
X-Spam-Status: No, score=-2.099 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, 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 (1024-bit key) header.d=cert.org
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 57J-e5Pjvcd7 for <i2nsf@ietfa.amsl.com>; Fri, 30 Oct 2020 19:47:23 -0700 (PDT)
Received: from taper.sei.cmu.edu (taper.sei.cmu.edu [147.72.252.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EA8143A1509 for <i2nsf@ietf.org>; Fri, 30 Oct 2020 19:47:22 -0700 (PDT)
Received: from delp.sei.cmu.edu (delp.sei.cmu.edu [10.64.21.31]) by taper.sei.cmu.edu (8.14.7/8.14.7) with ESMTP id 09V2lL0d009729 for <i2nsf@ietf.org>; Fri, 30 Oct 2020 22:47:21 -0400
DKIM-Filter: OpenDKIM Filter v2.11.0 taper.sei.cmu.edu 09V2lL0d009729
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cert.org; s=yc2bmwvrj62m; t=1604112441; bh=pYq1BA7sUlgvYw+GcllD3MuiqG8WsZC72lWQUZk7SDQ=; h=From:To:Subject:Date:From; b=UZOtKGSk5MHLwkaKKes3ITp6yqW2+zR1F6wG4XJ3lU7ecbR43Dot0hScyPik/CGYf PE0ojKvhjhZ/uuSQcAaVwkTC/22MurGccCjPRu6Y9eEc5EQk9F1FVEhwBWZCG5gMoq 7Y18Hj81OBKyhXMZrHGysehxWs6y05XTajzxVEa4=
Received: from MURIEL.ad.sei.cmu.edu (muriel.ad.sei.cmu.edu [147.72.252.47]) by delp.sei.cmu.edu (8.14.7/8.14.7) with ESMTP id 09V2lIWT041886 for <i2nsf@ietf.org>; Fri, 30 Oct 2020 22:47:18 -0400
Received: from MORRIS.ad.sei.cmu.edu (147.72.252.46) by MURIEL.ad.sei.cmu.edu (147.72.252.47) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2106.2; Fri, 30 Oct 2020 22:47:18 -0400
Received: from MORRIS.ad.sei.cmu.edu ([fe80::555b:9498:552e:d1bb]) by MORRIS.ad.sei.cmu.edu ([fe80::555b:9498:552e:d1bb%13]) with mapi id 15.01.2106.002; Fri, 30 Oct 2020 22:47:18 -0400
From: Roman Danyliw <rdd@cert.org>
To: "i2nsf@ietf.org" <i2nsf@ietf.org>
Thread-Topic: AD Review of draft-ietf-i2nsf-nsf-facing-interface-dm-10
Thread-Index: AdavLXN/h3lmc+bPSYWaLEwC2jUeZg==
Date: Sat, 31 Oct 2020 02:47:17 +0000
Message-ID: <cd062ee319e84c158e54ffce88119df2@cert.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.64.202.126]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2nsf/_SLa7TxvJYvARlTfU_8CFAO1xYc>
Subject: [I2nsf] AD Review of draft-ietf-i2nsf-nsf-facing-interface-dm-10
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, 31 Oct 2020 02:47:25 -0000

Hi!

I performed an AD review on draft-ietf-i2nsf-nsf-facing-interface-dm-10.  T=
hanks for writing it. =20

My feedback is as follows:

** (This is the most significant issue) This document makes a significant n=
umber of normative references to the capability information model.  However=
, the WG has decided not to publish this document (https://mailarchive.ietf=
.org/arch/msg/i2nsf/5SXo9QlIvtIEDOjHKA-d2jM1TUc/).  These are many dependen=
cies to resolve.  These are an incomplete list I noted:

-- Section 1.  There are a multiple references to the ECA model from [I-D.i=
etf-i2nsf-capability]

-- Section 4.1.  The text is relying on the deprecated draft-ietf-i2nsf-cap=
ability to describe the resolution strategies and default action.

-- Section 4.2.  This section relies on draft-ietf-i2nsf-capability to expl=
ain the event clause

-- Section 4.3. The condition clause depends on ietf-i2nsf-capability.

-- Section 4.4.  The action clause depends on ietf-i2nsf-capability.  The d=
efinition of an ingress, egress and log action are not explained.

-- YANG.  identity target-device (and all derived from it) relies on draft-=
ietf-i2nsf-capability

-- YANG.  identity content-security-controls relies on draft-ietf-i2nsf-cap=
ability.

-- YANG.  identity attack-mitigation-control relies on draft-ietf-i2nsf-cap=
ability.

-- YANG.  identity ingress-, egress- and default-action rely on draft-ietf-=
i2nsf-capability.

** Section 1. Editorial. s/ NSF-Facing Interface in Interface to Network Se=
curity Functions (I2NSF) [RFC8329]/NSF-Facing Interface in the Interface to=
 Network Security Functions (I2NSF) architecture [RFC8329]/

** Section 1.  Per "Security policy configuration for advanced network secu=
rity functions can be defined in future.", what is this referencing?  Only =
a few sentences into the introduction the scope of the module isn't clear. =
 What makes it "advanced"?

** Section 4.  "Advanced network security functions can be defined in futur=
e.", this is the second time in two pages that references are made to advan=
ced functions.  What is that referencing?

** Section 4.  Editorial. The bulleted list of the YANG module describing a=
 policy rule and ECA clauses was stated at the end of Section 1 (at the top=
 of page 3) and repeated almost verbatim again in Section 4 (at the bottom =
of page 4).  It likely doesn't need to be said twice.

** Section 4.1.  Editorial.  The sentence "This YANG tree diagram shows the=
 general I2NSF security policy rule for generic network security functions"=
 is repeated twice.

** Section 4.1. Typo. s/resolutation/resolution/

** Section 4.2.  These sentences follow each other and are nearly identical=
:
   This section shows the YANG tree diagram for an event clause for
   I2NSF security policy rules.

   This YANG tree diagram shows an event clause of an I2NSF security
   policy rule for generic network security functions. =20

** Section 4.3.  In Figure three, there is "pkt-sec-ipv4-geoip" and "pkt-se=
c-ipv4-sameip" but in the formal definition of the YANG module in Section 5=
, there are "pkt-sec-ipv4-geo-ip" and "pkt-sec-ipv4-same-ip" =20

** Section 4.3.  Per "A condition clause of context is defined ... and geog=
raphy condition", shouldn't that be a "gen-context-condition"?

** Section 4.3.
Note that this document deals only with
   simple conditions of advanced network security functions.  A
   condition clause of more advanced network security functions can be
   defined as an extension in future.  A condition clause can be
   extended according to specific vendor condition features

Previous text notes the possibility for extensions to advanced network secu=
rity features.  Here we are talking about extensions to the condition claus=
e.  Do we need a bit of text to explain the extensibility approach?

** Section 4.5.  What makes something an advanced action?  Is it the differ=
ence between a per packet vs. per flow decision?  Some other kind of state?

** Section 4.5.  Per "An I2NSF IPsec specification is used to define a meth=
od required to manage IPsec parameters for creating IPsec Security Associat=
ions (SAs) between two NSFs through either the IKEv2 protocol or the Securi=
ty Controller [I-D.ietf-i2nsf-sdn-ipsec-flow-protection]"

-- this workflow of NSF-to-NSF communication is no longer documented in iet=
f-i2nsf-sdn-ipsec-flow-protection (Section 7.1. and 7.2 were removed in -08=
) after my AD review.  Where is the interplay of two NSFs described in the =
I2NSF architecture?  Could that be explained or cited here.

-- It seems like the Security Considerations should discuss the channel sec=
urity this is enabling

** Section 5. =20
(a) The main objective of this data model is to provide both an
   information model and the corresponding YANG data model of I2NSF NSF-
   Facing Interface. =20

(b)    The semantics of the data model must be aligned with the information
   model of the NSF-Facing Interface. =20

(c) The transformation of the
   information model is performed so that this YANG data model

I don't follow what (b) is saying.  Since the information is the data model=
, how could they diverge?

Per (c), what transformation is being performed?  There is only a YANG (dat=
a) model specified.  No abstraction with an information exists in this text=
.

** YANG.  identity icmp.  Typo. s/IPv6 nett header/IPv6 next header/

** YANG.  identity target-device (and all derived from it) relies on draft-=
ietf-i2nsf-capability

** YANG.  identity-target-device.  Completeness of taxonomy:
-- What category would I choose for network infrastructure devices (switch,=
 router, etc.)

-- is a server the same as a "PC"?

** YANG identity iot.  Is iot intended to cover all operational technology =
(OT) devices?

** YANG.  identity vehicle.  Is that a car or truck?

** YANG. identity content-security-controls.  RFC8329 seems to only describ=
e firewall, IDS and IPS (in section 9.1), but not the others.  Firewall isn=
't mentioned.  Where is the definition of the others?

** YANG.  identity attack-mitigation-control.  RFC8329 is cited, but the pr=
oposed values derived values (e.g., syn-flood) aren't found in that documen=
t.  The closest appears to be Section 9.2, but that list of attack types is=
 different than what is presented here.

** YANG.  identity i2nsf-ipsec. Typo. s/Exchnage/Exchange/

** YANG.  leaf rule-priority.  With a range of 1..255, does a higher number=
 mean a higher priority?

** YANG. leaf session-aging-time.  leaf duration.  With a value of uint16, =
what is the unit, seconds?

** YANG.  container long connection.  Typo. s/enbale/enable/

** YANG.  leaf ipv4-description.  Typo. s/texual/textual/

** Section 5.  pkt-sec-ipv4-geo-ip.  What is the normative reference for th=
is format.  Are "Suricata uses GeoIP API with MaxMind database format" the =
format?

** YANG.  in a few places.  Typo. s/for an tcp/for a tcp/

** YANG.  container packet-security-url-category-condition.  What does "ven=
dors can write instructions for context condition that vendor made"?  How i=
s that different than the sentence before this text which says that "this i=
s a description of the url category condition"?

** YANG.  leaf pkt-sec-alert-rate.  What is the unit of the alert rate?  Is=
 this packets per second?

** YANG. leaf pkt-sec-alert-rate.  Isn't it also common in DoS mitigation t=
ools to handle other rates - flow/sec? bytes/sec?  Should that be supported=
?

** YANG.  left-list pkt-payload-content.  I don't understand what this mean=
s "The content keyword is very important in signatures. Between the quotati=
on marks you can write on what you would like the                signature =
to match."? What quotation marks?

** YANG. container users-conditions.  It should be noted in the Security Co=
nsiderations explicitly that user identifying information could be exchange=
d

** YANG.  container user and group. These both contain the text "The user h=
as many attributes such as name, id, password, type, authentication mode an=
d so on. Name/id is often used in the security policy to identify the user.=
"  Generically, not disagreement.  However where in this model are these at=
tributes represented?  It seems like the options are user-name, tenant info=
rmation"

** YANG.  leaf tenant.  What is "tenant information"?  Is a unint8 sufficie=
ntly large?

** YANG.  case vn-id.  Please expand vn-id.  The description is a repeat of=
 the name.

** YANG.  src and dest-geographic-location.  I don't understand the descrip=
tion "This is mapped to ip address. We can acquire destination region throu=
gh ip address stored in the database"

** YANG.  Container advanced-action.   =20

-- Per "If the packet need be additionally inspected, the packet are passed=
 to advanced network security functions according to the profile", what pro=
file?

-- I don't follow the different between a "content-security control" and a =
"attack mitigation control"

-- Per the list of "content-security-controls", "antivirus, ips, ids, url f=
iltering, mail filtering, file blocking, file isolate, packet capture, appl=
ication control, voip and volte", where are each of these described?

-- Per the content-security-controls, these seem to be unequal or overlappi=
ng things (ips is a security technology; url blocking is a technique, possi=
ble with ips; volte is a protocol)

-- Per attack-mitigation-controls, same question, where are these described=
? What does ipv6 related mean?

-- What is the origin of the attack-mitigation-list - why not "ntp amplific=
ation attack"?  this seems like an enumeration of DoS types, with some reco=
nnaissance? =20

** YANG.  leaf description. Typo. s/desription/description/

** YANG.  leaf i2nsf-ipsec.  Typo. s/Exchnage/Exchange/

** Section 6.  Per "For security requirements ... described in Appendix A",=
 there is no Appendix A in this document.

** Section 6.  Per "Configuration examples of [I-D.ietf-i2nsf-capability-da=
ta-model] are registered in I2NSF framework", I don't follow what is gettin=
g registered with what examples.

** Section 6.  Typo. s/registed/registered/

** Section 6.1.  Figure 7 and 8.  A few questions about both examples.

-- what is SNS?  Please expand the acronym (Social Networking Service?)

-- the text seems to suggest that this block will only occur during busines=
s hours.  However, the time interval is set as:
     <absolute-time-interval>
      <start-date-time>2019-08-01T09:00:00Z</start-date-time>
      <end-date-time>2019-12-31T18:00:00Z</end-date-time>
     </absolute-time-interval>

Doesn't this mean that all traffic between August 1, 2019 - December 31 201=
9 would match (not just 0900 - 1800 every day).

** Section 6.1.  Figure 9.  It doesn't not feel appropriate to call out "fa=
cebook" and "Instagram", please come up with a more generic example.

** Section 6.1.  Figure 9.  The figure text says web filtering during busin=
ess hours, but the XML doesn't seem to show time constraints.

** Section 6.1.  How does this model distinguish between per-packet vs. per=
-flow operations?  The time and IP based actions of the firewall could be e=
xecuted on a per packet basis.  However,=20
to do the URL filtering requires stream reassembly.  The action on URL filt=
ering is to drop the packet:

<packet-action>
       <egress-action>drop</egress-action>

but shouldn't it be the flow?

** Section 6.2.  Please use an example domain to represent a malicious doma=
in -- @voip.mailcious.example.com

** Section 6.3.  Typo. s/contrl/control/

** Section 8.
    o ietf-i2nsf-policy-rule-for-nsf: The attacker may provide incorrect
      policy information of any target NSFs by illegally modifying this.

I don't follow the legality of modifying the configuration.  Perhaps it wou=
ld be clearer to say that writing to almost any element of the module would=
 directly impact the configuration of the security functions on the network=
 -  completely turning off security monitoring and mitigation capabilities;=
 altering the scope of this monitoring and mitigation; creating an overwhel=
ming logging volume to overwhelm downstream analytics or storage capacity; =
or creating logging patterns which confuse or rendering useless trained sta=
tistics or artificial intelligence models.

** Idnits returned:

  =3D=3D The document doesn't use any RFC 2119 keywords, yet seems to have =
RFC
     2119 boilerplate text.

  Checking references for intended status: Proposed Standard
  -------------------------------------------------------------------------=
---

     (See RFCs 3967 and 4897 for information about using normative referenc=
es
     to lower-maturity documents in RFCs)

  ** Obsolete normative reference: RFC 1700 (Obsoleted by RFC 3232)

  ** Downref: Normative reference to an Informational RFC: RFC 3232

  ** Downref: Normative reference to an Informational RFC: RFC 3849

  ** Downref: Normative reference to an Informational RFC: RFC 5737

  ** Downref: Normative reference to an Informational RFC: RFC 8329

Per RFC3232, I'm not sure why it is being cited.  Is it being used to indic=
ate that an IANA registry stores a particular protocol value (e.g., the IPv=
4 protocol field)?  If so, then reference the IANA registry instead.

Per RFC3849 and RFC5737, just dropped these references outright.  They aren=
't need to explain the reserved addressed.

Per RFC8329, I've noted above in my feedback on my not understanding how th=
is document explain the YANG module elements in which it is being cited.

For the shepherd write-up, please just add that idnit is throwing an error =
on RFC8177, but that is a legitimate reference (in the YANG module)

Regards,
Roman


From nobody Fri Oct 30 23:41:15 2020
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 1FAB53A0B6F for <i2nsf@ietfa.amsl.com>; Fri, 30 Oct 2020 23:41:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.086
X-Spam-Level: 
X-Spam-Status: No, score=-2.086 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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_HK_NAME_FM_MR_MRS=0.01, URIBL_BLOCKED=0.001, URI_DOTEDU=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 uekxHaou0RIG for <i2nsf@ietfa.amsl.com>; Fri, 30 Oct 2020 23:41:10 -0700 (PDT)
Received: from mail-lj1-x235.google.com (mail-lj1-x235.google.com [IPv6:2a00:1450:4864:20::235]) (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 166CD3A0B6C for <i2nsf@ietf.org>; Fri, 30 Oct 2020 23:41:10 -0700 (PDT)
Received: by mail-lj1-x235.google.com with SMTP id o13so947986ljj.11 for <i2nsf@ietf.org>; Fri, 30 Oct 2020 23:41:09 -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=5JsC6dWeRzfdYV9gYHSECMsUbuHMoH6CMqFiWQmrfFQ=; b=f6Wim53gnYwxNo/Xng0y4+hy3a/6dmRLMASMHm3hFJzMrdxCoDyAiBBVvlyrEWWB+A 6yiv2AuX4dn1WKqryWi1gmTK2HakU5kDSKzBuctiTkm04QgIy85Hv+NFCN3Pq3dc3x4G L2/yXcVdTU+qlzXI8PCy5Lr9X6mzS4I0BeRRsZDF3FQSdv/qiCYzK+7yXVKSOic5GMEL Sl4lASTmn5qGNWXR0PMNSen4848ZXOaQ93phmRUWuNPa6GDVSWAl4YRe2GXPQwox+2MB 6JrxZiO6y4w9L6US1j/RL3l2DTUfkN4f6CPdslxoSr7spolus4RsV+78FIFFQmLymhYz 9cRQ==
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=5JsC6dWeRzfdYV9gYHSECMsUbuHMoH6CMqFiWQmrfFQ=; b=N2bdYWnPQ174h3gLmMSSP1IJdfJh6IU5WfHzPvDFFPVA0LMxgpzuPu8SHwrF5dcSeW rEOAmmPBPY3YS+F6G/wFk0KVj6qO6EFPhOWfgv7wZN4NUgrabi8tegeOesBOV+kOVxwy ikSI1n1RRD/4uiUvVfyWldG3WX5oACm2Zlg79tlJp1qKM1EC7lmgO81G/+X5DzXH1qyE BTqN1vLz7fix7zkVMUf+GeiilaSEXZ1v2FujKh8B5UJ6m//0DP8nGN1RD7iFYzoEqM40 Lo4vMedixB5ryOuHUmqC4cpTcKtAeL/SnFU1zcj8T+tOtD3e2lx/2pgwNPcpF+PMOHRt 6GIg==
X-Gm-Message-State: AOAM532BQHxnIO7ksn5eNA3rdgFD6ijLZ6MGq813cn96j15WKu/kM/R8 5kX6dYXQOI9+/bHd++P1iGqfZ5zf+R7owMbXz4g=
X-Google-Smtp-Source: ABdhPJxJaF2I7MnPmCv8oXvbw0PNpXmik6VGp/JcRDOFulqLDhnhwyjqg7xVXRJcgLsVyI2jmZBf4OttMwqRddhCFsk=
X-Received: by 2002:a2e:7216:: with SMTP id n22mr2705175ljc.187.1604126468086;  Fri, 30 Oct 2020 23:41:08 -0700 (PDT)
MIME-Version: 1.0
References: <cd062ee319e84c158e54ffce88119df2@cert.org>
In-Reply-To: <cd062ee319e84c158e54ffce88119df2@cert.org>
From: "Mr. Jaehoon Paul Jeong" <jaehoon.paul@gmail.com>
Date: Sat, 31 Oct 2020 15:40:34 +0900
Message-ID: <CAPK2DexA-AumKuAR+L1Kwp5+wtLaPuw65E92=i-zPoFZE37OmA@mail.gmail.com>
To: Roman Danyliw <rdd@cert.org>
Cc: "i2nsf@ietf.org" <i2nsf@ietf.org>, "Jingyong (Tim) Kim" <wlsdyd0930@nate.com>,  skku-iotlab-members <skku-iotlab-members@googlegroups.com>,  "Mr. Jaehoon Paul Jeong" <jaehoon.paul@gmail.com>
Content-Type: multipart/alternative; boundary="0000000000004e1e6f05b2f1ccd8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2nsf/QPUXTwO4FT5MlLWJKVHAbT2qJ70>
Subject: Re: [I2nsf] AD Review of draft-ietf-i2nsf-nsf-facing-interface-dm-10
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, 31 Oct 2020 06:41:14 -0000

--0000000000004e1e6f05b2f1ccd8
Content-Type: text/plain; charset="UTF-8"

Hi Roman,
We authors will revise our draft according to your review comments.

Thanks.

Best Regards,
Paul


On Sat, Oct 31, 2020 at 11:47 AM Roman Danyliw <rdd@cert.org> wrote:

> Hi!
>
> I performed an AD review on draft-ietf-i2nsf-nsf-facing-interface-dm-10.
> Thanks for writing it.
>
> My feedback is as follows:
>
> ** (This is the most significant issue) This document makes a significant
> number of normative references to the capability information model.
> However, the WG has decided not to publish this document (
> https://mailarchive.ietf.org/arch/msg/i2nsf/5SXo9QlIvtIEDOjHKA-d2jM1TUc/).
> These are many dependencies to resolve.  These are an incomplete list I
> noted:
>
> -- Section 1.  There are a multiple references to the ECA model from
> [I-D.ietf-i2nsf-capability]
>
> -- Section 4.1.  The text is relying on the deprecated
> draft-ietf-i2nsf-capability to describe the resolution strategies and
> default action.
>
> -- Section 4.2.  This section relies on draft-ietf-i2nsf-capability to
> explain the event clause
>
> -- Section 4.3. The condition clause depends on ietf-i2nsf-capability.
>
> -- Section 4.4.  The action clause depends on ietf-i2nsf-capability.  The
> definition of an ingress, egress and log action are not explained.
>
> -- YANG.  identity target-device (and all derived from it) relies on
> draft-ietf-i2nsf-capability
>
> -- YANG.  identity content-security-controls relies on
> draft-ietf-i2nsf-capability.
>
> -- YANG.  identity attack-mitigation-control relies on
> draft-ietf-i2nsf-capability.
>
> -- YANG.  identity ingress-, egress- and default-action rely on
> draft-ietf-i2nsf-capability.
>
> ** Section 1. Editorial. s/ NSF-Facing Interface in Interface to Network
> Security Functions (I2NSF) [RFC8329]/NSF-Facing Interface in the Interface
> to Network Security Functions (I2NSF) architecture [RFC8329]/
>
> ** Section 1.  Per "Security policy configuration for advanced network
> security functions can be defined in future.", what is this referencing?
> Only a few sentences into the introduction the scope of the module isn't
> clear.  What makes it "advanced"?
>
> ** Section 4.  "Advanced network security functions can be defined in
> future.", this is the second time in two pages that references are made to
> advanced functions.  What is that referencing?
>
> ** Section 4.  Editorial. The bulleted list of the YANG module describing
> a policy rule and ECA clauses was stated at the end of Section 1 (at the
> top of page 3) and repeated almost verbatim again in Section 4 (at the
> bottom of page 4).  It likely doesn't need to be said twice.
>
> ** Section 4.1.  Editorial.  The sentence "This YANG tree diagram shows
> the general I2NSF security policy rule for generic network security
> functions" is repeated twice.
>
> ** Section 4.1. Typo. s/resolutation/resolution/
>
> ** Section 4.2.  These sentences follow each other and are nearly
> identical:
>    This section shows the YANG tree diagram for an event clause for
>    I2NSF security policy rules.
>
>    This YANG tree diagram shows an event clause of an I2NSF security
>    policy rule for generic network security functions.
>
> ** Section 4.3.  In Figure three, there is "pkt-sec-ipv4-geoip" and
> "pkt-sec-ipv4-sameip" but in the formal definition of the YANG module in
> Section 5, there are "pkt-sec-ipv4-geo-ip" and "pkt-sec-ipv4-same-ip"
>
> ** Section 4.3.  Per "A condition clause of context is defined ... and
> geography condition", shouldn't that be a "gen-context-condition"?
>
> ** Section 4.3.
> Note that this document deals only with
>    simple conditions of advanced network security functions.  A
>    condition clause of more advanced network security functions can be
>    defined as an extension in future.  A condition clause can be
>    extended according to specific vendor condition features
>
> Previous text notes the possibility for extensions to advanced network
> security features.  Here we are talking about extensions to the condition
> clause.  Do we need a bit of text to explain the extensibility approach?
>
> ** Section 4.5.  What makes something an advanced action?  Is it the
> difference between a per packet vs. per flow decision?  Some other kind of
> state?
>
> ** Section 4.5.  Per "An I2NSF IPsec specification is used to define a
> method required to manage IPsec parameters for creating IPsec Security
> Associations (SAs) between two NSFs through either the IKEv2 protocol or
> the Security Controller [I-D.ietf-i2nsf-sdn-ipsec-flow-protection]"
>
> -- this workflow of NSF-to-NSF communication is no longer documented in
> ietf-i2nsf-sdn-ipsec-flow-protection (Section 7.1. and 7.2 were removed in
> -08) after my AD review.  Where is the interplay of two NSFs described in
> the I2NSF architecture?  Could that be explained or cited here.
>
> -- It seems like the Security Considerations should discuss the channel
> security this is enabling
>
> ** Section 5.
> (a) The main objective of this data model is to provide both an
>    information model and the corresponding YANG data model of I2NSF NSF-
>    Facing Interface.
>
> (b)    The semantics of the data model must be aligned with the information
>    model of the NSF-Facing Interface.
>
> (c) The transformation of the
>    information model is performed so that this YANG data model
>
> I don't follow what (b) is saying.  Since the information is the data
> model, how could they diverge?
>
> Per (c), what transformation is being performed?  There is only a YANG
> (data) model specified.  No abstraction with an information exists in this
> text.
>
> ** YANG.  identity icmp.  Typo. s/IPv6 nett header/IPv6 next header/
>
> ** YANG.  identity target-device (and all derived from it) relies on
> draft-ietf-i2nsf-capability
>
> ** YANG.  identity-target-device.  Completeness of taxonomy:
> -- What category would I choose for network infrastructure devices
> (switch, router, etc.)
>
> -- is a server the same as a "PC"?
>
> ** YANG identity iot.  Is iot intended to cover all operational technology
> (OT) devices?
>
> ** YANG.  identity vehicle.  Is that a car or truck?
>
> ** YANG. identity content-security-controls.  RFC8329 seems to only
> describe firewall, IDS and IPS (in section 9.1), but not the others.
> Firewall isn't mentioned.  Where is the definition of the others?
>
> ** YANG.  identity attack-mitigation-control.  RFC8329 is cited, but the
> proposed values derived values (e.g., syn-flood) aren't found in that
> document.  The closest appears to be Section 9.2, but that list of attack
> types is different than what is presented here.
>
> ** YANG.  identity i2nsf-ipsec. Typo. s/Exchnage/Exchange/
>
> ** YANG.  leaf rule-priority.  With a range of 1..255, does a higher
> number mean a higher priority?
>
> ** YANG. leaf session-aging-time.  leaf duration.  With a value of uint16,
> what is the unit, seconds?
>
> ** YANG.  container long connection.  Typo. s/enbale/enable/
>
> ** YANG.  leaf ipv4-description.  Typo. s/texual/textual/
>
> ** Section 5.  pkt-sec-ipv4-geo-ip.  What is the normative reference for
> this format.  Are "Suricata uses GeoIP API with MaxMind database format"
> the format?
>
> ** YANG.  in a few places.  Typo. s/for an tcp/for a tcp/
>
> ** YANG.  container packet-security-url-category-condition.  What does
> "vendors can write instructions for context condition that vendor made"?
> How is that different than the sentence before this text which says that
> "this is a description of the url category condition"?
>
> ** YANG.  leaf pkt-sec-alert-rate.  What is the unit of the alert rate?
> Is this packets per second?
>
> ** YANG. leaf pkt-sec-alert-rate.  Isn't it also common in DoS mitigation
> tools to handle other rates - flow/sec? bytes/sec?  Should that be
> supported?
>
> ** YANG.  left-list pkt-payload-content.  I don't understand what this
> means "The content keyword is very important in signatures. Between the
> quotation marks you can write on what you would like the
> signature to match."? What quotation marks?
>
> ** YANG. container users-conditions.  It should be noted in the Security
> Considerations explicitly that user identifying information could be
> exchanged
>
> ** YANG.  container user and group. These both contain the text "The user
> has many attributes such as name, id, password, type, authentication mode
> and so on. Name/id is often used in the security policy to identify the
> user."  Generically, not disagreement.  However where in this model are
> these attributes represented?  It seems like the options are user-name,
> tenant information"
>
> ** YANG.  leaf tenant.  What is "tenant information"?  Is a unint8
> sufficiently large?
>
> ** YANG.  case vn-id.  Please expand vn-id.  The description is a repeat
> of the name.
>
> ** YANG.  src and dest-geographic-location.  I don't understand the
> description "This is mapped to ip address. We can acquire destination
> region through ip address stored in the database"
>
> ** YANG.  Container advanced-action.
>
> -- Per "If the packet need be additionally inspected, the packet are
> passed to advanced network security functions according to the profile",
> what profile?
>
> -- I don't follow the different between a "content-security control" and a
> "attack mitigation control"
>
> -- Per the list of "content-security-controls", "antivirus, ips, ids, url
> filtering, mail filtering, file blocking, file isolate, packet capture,
> application control, voip and volte", where are each of these described?
>
> -- Per the content-security-controls, these seem to be unequal or
> overlapping things (ips is a security technology; url blocking is a
> technique, possible with ips; volte is a protocol)
>
> -- Per attack-mitigation-controls, same question, where are these
> described? What does ipv6 related mean?
>
> -- What is the origin of the attack-mitigation-list - why not "ntp
> amplification attack"?  this seems like an enumeration of DoS types, with
> some reconnaissance?
>
> ** YANG.  leaf description. Typo. s/desription/description/
>
> ** YANG.  leaf i2nsf-ipsec.  Typo. s/Exchnage/Exchange/
>
> ** Section 6.  Per "For security requirements ... described in Appendix
> A", there is no Appendix A in this document.
>
> ** Section 6.  Per "Configuration examples of
> [I-D.ietf-i2nsf-capability-data-model] are registered in I2NSF framework",
> I don't follow what is getting registered with what examples.
>
> ** Section 6.  Typo. s/registed/registered/
>
> ** Section 6.1.  Figure 7 and 8.  A few questions about both examples.
>
> -- what is SNS?  Please expand the acronym (Social Networking Service?)
>
> -- the text seems to suggest that this block will only occur during
> business hours.  However, the time interval is set as:
>      <absolute-time-interval>
>       <start-date-time>2019-08-01T09:00:00Z</start-date-time>
>       <end-date-time>2019-12-31T18:00:00Z</end-date-time>
>      </absolute-time-interval>
>
> Doesn't this mean that all traffic between August 1, 2019 - December 31
> 2019 would match (not just 0900 - 1800 every day).
>
> ** Section 6.1.  Figure 9.  It doesn't not feel appropriate to call out
> "facebook" and "Instagram", please come up with a more generic example.
>
> ** Section 6.1.  Figure 9.  The figure text says web filtering during
> business hours, but the XML doesn't seem to show time constraints.
>
> ** Section 6.1.  How does this model distinguish between per-packet vs.
> per-flow operations?  The time and IP based actions of the firewall could
> be executed on a per packet basis.  However,
> to do the URL filtering requires stream reassembly.  The action on URL
> filtering is to drop the packet:
>
> <packet-action>
>        <egress-action>drop</egress-action>
>
> but shouldn't it be the flow?
>
> ** Section 6.2.  Please use an example domain to represent a malicious
> domain -- @voip.mailcious.example.com
>
> ** Section 6.3.  Typo. s/contrl/control/
>
> ** Section 8.
>     o ietf-i2nsf-policy-rule-for-nsf: The attacker may provide incorrect
>       policy information of any target NSFs by illegally modifying this.
>
> I don't follow the legality of modifying the configuration.  Perhaps it
> would be clearer to say that writing to almost any element of the module
> would directly impact the configuration of the security functions on the
> network -  completely turning off security monitoring and mitigation
> capabilities; altering the scope of this monitoring and mitigation;
> creating an overwhelming logging volume to overwhelm downstream analytics
> or storage capacity; or creating logging patterns which confuse or
> rendering useless trained statistics or artificial intelligence models.
>
> ** Idnits returned:
>
>   == The document doesn't use any RFC 2119 keywords, yet seems to have RFC
>      2119 boilerplate text.
>
>   Checking references for intended status: Proposed Standard
>
> ----------------------------------------------------------------------------
>
>      (See RFCs 3967 and 4897 for information about using normative
> references
>      to lower-maturity documents in RFCs)
>
>   ** Obsolete normative reference: RFC 1700 (Obsoleted by RFC 3232)
>
>   ** Downref: Normative reference to an Informational RFC: RFC 3232
>
>   ** Downref: Normative reference to an Informational RFC: RFC 3849
>
>   ** Downref: Normative reference to an Informational RFC: RFC 5737
>
>   ** Downref: Normative reference to an Informational RFC: RFC 8329
>
> Per RFC3232, I'm not sure why it is being cited.  Is it being used to
> indicate that an IANA registry stores a particular protocol value (e.g.,
> the IPv4 protocol field)?  If so, then reference the IANA registry instead.
>
> Per RFC3849 and RFC5737, just dropped these references outright.  They
> aren't need to explain the reserved addressed.
>
> Per RFC8329, I've noted above in my feedback on my not understanding how
> this document explain the YANG module elements in which it is being cited.
>
> For the shepherd write-up, please just add that idnit is throwing an error
> on RFC8177, but that is a legitimate reference (in the YANG module)
>
> Regards,
> Roman
>
> _______________________________________________
> I2nsf mailing list
> I2nsf@ietf.org
> https://www.ietf.org/mailman/listinfo/i2nsf
>


-- 
===========================
Mr. Jaehoon (Paul) Jeong, Ph.D.
Associate Professor
Department of Computer Science and Engineering
Sungkyunkwan University
Office: +82-31-299-4957
Email: jaehoon.paul@gmail.com, pauljeong@skku.edu
Personal Homepage: http://iotlab.skku.edu/people-jaehoon-jeong.php
<http://cpslab.skku.edu/people-jaehoon-jeong.php>

--0000000000004e1e6f05b2f1ccd8
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi Roman,<div>We authors will revise our draft according t=
o your review comments.</div><div><br></div><div>Thanks.</div><div><br></di=
v><div>Best Regards,</div><div>Paul</div><div><br></div></div><br><div clas=
s=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Sat, Oct 31, 202=
0 at 11:47 AM Roman Danyliw &lt;<a href=3D"mailto:rdd@cert.org">rdd@cert.or=
g</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin=
:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"=
>Hi!<br>
<br>
I performed an AD review on draft-ietf-i2nsf-nsf-facing-interface-dm-10.=C2=
=A0 Thanks for writing it.=C2=A0 <br>
<br>
My feedback is as follows:<br>
<br>
** (This is the most significant issue) This document makes a significant n=
umber of normative references to the capability information model.=C2=A0 Ho=
wever, the WG has decided not to publish this document (<a href=3D"https://=
mailarchive.ietf.org/arch/msg/i2nsf/5SXo9QlIvtIEDOjHKA-d2jM1TUc/" rel=3D"no=
referrer" target=3D"_blank">https://mailarchive.ietf.org/arch/msg/i2nsf/5SX=
o9QlIvtIEDOjHKA-d2jM1TUc/</a>).=C2=A0 These are many dependencies to resolv=
e.=C2=A0 These are an incomplete list I noted:<br>
<br>
-- Section 1.=C2=A0 There are a multiple references to the ECA model from [=
I-D.ietf-i2nsf-capability]<br>
<br>
-- Section 4.1.=C2=A0 The text is relying on the deprecated draft-ietf-i2ns=
f-capability to describe the resolution strategies and default action.<br>
<br>
-- Section 4.2.=C2=A0 This section relies on draft-ietf-i2nsf-capability to=
 explain the event clause<br>
<br>
-- Section 4.3. The condition clause depends on ietf-i2nsf-capability.<br>
<br>
-- Section 4.4.=C2=A0 The action clause depends on ietf-i2nsf-capability.=
=C2=A0 The definition of an ingress, egress and log action are not explaine=
d.<br>
<br>
-- YANG.=C2=A0 identity target-device (and all derived from it) relies on d=
raft-ietf-i2nsf-capability<br>
<br>
-- YANG.=C2=A0 identity content-security-controls relies on draft-ietf-i2ns=
f-capability.<br>
<br>
-- YANG.=C2=A0 identity attack-mitigation-control relies on draft-ietf-i2ns=
f-capability.<br>
<br>
-- YANG.=C2=A0 identity ingress-, egress- and default-action rely on draft-=
ietf-i2nsf-capability.<br>
<br>
** Section 1. Editorial. s/ NSF-Facing Interface in Interface to Network Se=
curity Functions (I2NSF) [RFC8329]/NSF-Facing Interface in the Interface to=
 Network Security Functions (I2NSF) architecture [RFC8329]/<br>
<br>
** Section 1.=C2=A0 Per &quot;Security policy configuration for advanced ne=
twork security functions can be defined in future.&quot;, what is this refe=
rencing?=C2=A0 Only a few sentences into the introduction the scope of the =
module isn&#39;t clear.=C2=A0 What makes it &quot;advanced&quot;?<br>
<br>
** Section 4.=C2=A0 &quot;Advanced network security functions can be define=
d in future.&quot;, this is the second time in two pages that references ar=
e made to advanced functions.=C2=A0 What is that referencing?<br>
<br>
** Section 4.=C2=A0 Editorial. The bulleted list of the YANG module describ=
ing a policy rule and ECA clauses was stated at the end of Section 1 (at th=
e top of page 3) and repeated almost verbatim again in Section 4 (at the bo=
ttom of page 4).=C2=A0 It likely doesn&#39;t need to be said twice.<br>
<br>
** Section 4.1.=C2=A0 Editorial.=C2=A0 The sentence &quot;This YANG tree di=
agram shows the general I2NSF security policy rule for generic network secu=
rity functions&quot; is repeated twice.<br>
<br>
** Section 4.1. Typo. s/resolutation/resolution/<br>
<br>
** Section 4.2.=C2=A0 These sentences follow each other and are nearly iden=
tical:<br>
=C2=A0 =C2=A0This section shows the YANG tree diagram for an event clause f=
or<br>
=C2=A0 =C2=A0I2NSF security policy rules.<br>
<br>
=C2=A0 =C2=A0This YANG tree diagram shows an event clause of an I2NSF secur=
ity<br>
=C2=A0 =C2=A0policy rule for generic network security functions.=C2=A0 <br>
<br>
** Section 4.3.=C2=A0 In Figure three, there is &quot;pkt-sec-ipv4-geoip&qu=
ot; and &quot;pkt-sec-ipv4-sameip&quot; but in the formal definition of the=
 YANG module in Section 5, there are &quot;pkt-sec-ipv4-geo-ip&quot; and &q=
uot;pkt-sec-ipv4-same-ip&quot;=C2=A0 <br>
<br>
** Section 4.3.=C2=A0 Per &quot;A condition clause of context is defined ..=
. and geography condition&quot;, shouldn&#39;t that be a &quot;gen-context-=
condition&quot;?<br>
<br>
** Section 4.3.<br>
Note that this document deals only with<br>
=C2=A0 =C2=A0simple conditions of advanced network security functions.=C2=
=A0 A<br>
=C2=A0 =C2=A0condition clause of more advanced network security functions c=
an be<br>
=C2=A0 =C2=A0defined as an extension in future.=C2=A0 A condition clause ca=
n be<br>
=C2=A0 =C2=A0extended according to specific vendor condition features<br>
<br>
Previous text notes the possibility for extensions to advanced network secu=
rity features.=C2=A0 Here we are talking about extensions to the condition =
clause.=C2=A0 Do we need a bit of text to explain the extensibility approac=
h?<br>
<br>
** Section 4.5.=C2=A0 What makes something an advanced action?=C2=A0 Is it =
the difference between a per packet vs. per flow decision?=C2=A0 Some other=
 kind of state?<br>
<br>
** Section 4.5.=C2=A0 Per &quot;An I2NSF IPsec specification is used to def=
ine a method required to manage IPsec parameters for creating IPsec Securit=
y Associations (SAs) between two NSFs through either the IKEv2 protocol or =
the Security Controller [I-D.ietf-i2nsf-sdn-ipsec-flow-protection]&quot;<br=
>
<br>
-- this workflow of NSF-to-NSF communication is no longer documented in iet=
f-i2nsf-sdn-ipsec-flow-protection (Section 7.1. and 7.2 were removed in -08=
) after my AD review.=C2=A0 Where is the interplay of two NSFs described in=
 the I2NSF architecture?=C2=A0 Could that be explained or cited here.<br>
<br>
-- It seems like the Security Considerations should discuss the channel sec=
urity this is enabling<br>
<br>
** Section 5.=C2=A0 <br>
(a) The main objective of this data model is to provide both an<br>
=C2=A0 =C2=A0information model and the corresponding YANG data model of I2N=
SF NSF-<br>
=C2=A0 =C2=A0Facing Interface.=C2=A0 <br>
<br>
(b)=C2=A0 =C2=A0 The semantics of the data model must be aligned with the i=
nformation<br>
=C2=A0 =C2=A0model of the NSF-Facing Interface.=C2=A0 <br>
<br>
(c) The transformation of the<br>
=C2=A0 =C2=A0information model is performed so that this YANG data model<br=
>
<br>
I don&#39;t follow what (b) is saying.=C2=A0 Since the information is the d=
ata model, how could they diverge?<br>
<br>
Per (c), what transformation is being performed?=C2=A0 There is only a YANG=
 (data) model specified.=C2=A0 No abstraction with an information exists in=
 this text.<br>
<br>
** YANG.=C2=A0 identity icmp.=C2=A0 Typo. s/IPv6 nett header/IPv6 next head=
er/<br>
<br>
** YANG.=C2=A0 identity target-device (and all derived from it) relies on d=
raft-ietf-i2nsf-capability<br>
<br>
** YANG.=C2=A0 identity-target-device.=C2=A0 Completeness of taxonomy:<br>
-- What category would I choose for network infrastructure devices (switch,=
 router, etc.)<br>
<br>
-- is a server the same as a &quot;PC&quot;?<br>
<br>
** YANG identity iot.=C2=A0 Is iot intended to cover all operational techno=
logy (OT) devices?<br>
<br>
** YANG.=C2=A0 identity vehicle.=C2=A0 Is that a car or truck?<br>
<br>
** YANG. identity content-security-controls.=C2=A0 RFC8329 seems to only de=
scribe firewall, IDS and IPS (in section 9.1), but not the others.=C2=A0 Fi=
rewall isn&#39;t mentioned.=C2=A0 Where is the definition of the others?<br=
>
<br>
** YANG.=C2=A0 identity attack-mitigation-control.=C2=A0 RFC8329 is cited, =
but the proposed values derived values (e.g., syn-flood) aren&#39;t found i=
n that document.=C2=A0 The closest appears to be Section 9.2, but that list=
 of attack types is different than what is presented here.<br>
<br>
** YANG.=C2=A0 identity i2nsf-ipsec. Typo. s/Exchnage/Exchange/<br>
<br>
** YANG.=C2=A0 leaf rule-priority.=C2=A0 With a range of 1..255, does a hig=
her number mean a higher priority?<br>
<br>
** YANG. leaf session-aging-time.=C2=A0 leaf duration.=C2=A0 With a value o=
f uint16, what is the unit, seconds?<br>
<br>
** YANG.=C2=A0 container long connection.=C2=A0 Typo. s/enbale/enable/<br>
<br>
** YANG.=C2=A0 leaf ipv4-description.=C2=A0 Typo. s/texual/textual/<br>
<br>
** Section 5.=C2=A0 pkt-sec-ipv4-geo-ip.=C2=A0 What is the normative refere=
nce for this format.=C2=A0 Are &quot;Suricata uses GeoIP API with MaxMind d=
atabase format&quot; the format?<br>
<br>
** YANG.=C2=A0 in a few places.=C2=A0 Typo. s/for an tcp/for a tcp/<br>
<br>
** YANG.=C2=A0 container packet-security-url-category-condition.=C2=A0 What=
 does &quot;vendors can write instructions for context condition that vendo=
r made&quot;?=C2=A0 How is that different than the sentence before this tex=
t which says that &quot;this is a description of the url category condition=
&quot;?<br>
<br>
** YANG.=C2=A0 leaf pkt-sec-alert-rate.=C2=A0 What is the unit of the alert=
 rate?=C2=A0 Is this packets per second?<br>
<br>
** YANG. leaf pkt-sec-alert-rate.=C2=A0 Isn&#39;t it also common in DoS mit=
igation tools to handle other rates - flow/sec? bytes/sec?=C2=A0 Should tha=
t be supported?<br>
<br>
** YANG.=C2=A0 left-list pkt-payload-content.=C2=A0 I don&#39;t understand =
what this means &quot;The content keyword is very important in signatures. =
Between the quotation marks you can write on what you would like the=C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 signature to match.&quot;?=
 What quotation marks?<br>
<br>
** YANG. container users-conditions.=C2=A0 It should be noted in the Securi=
ty Considerations explicitly that user identifying information could be exc=
hanged<br>
<br>
** YANG.=C2=A0 container user and group. These both contain the text &quot;=
The user has many attributes such as name, id, password, type, authenticati=
on mode and so on. Name/id is often used in the security policy to identify=
 the user.&quot;=C2=A0 Generically, not disagreement.=C2=A0 However where i=
n this model are these attributes represented?=C2=A0 It seems like the opti=
ons are user-name, tenant information&quot;<br>
<br>
** YANG.=C2=A0 leaf tenant.=C2=A0 What is &quot;tenant information&quot;?=
=C2=A0 Is a unint8 sufficiently large?<br>
<br>
** YANG.=C2=A0 case vn-id.=C2=A0 Please expand vn-id.=C2=A0 The description=
 is a repeat of the name.<br>
<br>
** YANG.=C2=A0 src and dest-geographic-location.=C2=A0 I don&#39;t understa=
nd the description &quot;This is mapped to ip address. We can acquire desti=
nation region through ip address stored in the database&quot;<br>
<br>
** YANG.=C2=A0 Container advanced-action.=C2=A0 =C2=A0 <br>
<br>
-- Per &quot;If the packet need be additionally inspected, the packet are p=
assed to advanced network security functions according to the profile&quot;=
, what profile?<br>
<br>
-- I don&#39;t follow the different between a &quot;content-security contro=
l&quot; and a &quot;attack mitigation control&quot;<br>
<br>
-- Per the list of &quot;content-security-controls&quot;, &quot;antivirus, =
ips, ids, url filtering, mail filtering, file blocking, file isolate, packe=
t capture, application control, voip and volte&quot;, where are each of the=
se described?<br>
<br>
-- Per the content-security-controls, these seem to be unequal or overlappi=
ng things (ips is a security technology; url blocking is a technique, possi=
ble with ips; volte is a protocol)<br>
<br>
-- Per attack-mitigation-controls, same question, where are these described=
? What does ipv6 related mean?<br>
<br>
-- What is the origin of the attack-mitigation-list - why not &quot;ntp amp=
lification attack&quot;?=C2=A0 this seems like an enumeration of DoS types,=
 with some reconnaissance?=C2=A0 <br>
<br>
** YANG.=C2=A0 leaf description. Typo. s/desription/description/<br>
<br>
** YANG.=C2=A0 leaf i2nsf-ipsec.=C2=A0 Typo. s/Exchnage/Exchange/<br>
<br>
** Section 6.=C2=A0 Per &quot;For security requirements ... described in Ap=
pendix A&quot;, there is no Appendix A in this document.<br>
<br>
** Section 6.=C2=A0 Per &quot;Configuration examples of [I-D.ietf-i2nsf-cap=
ability-data-model] are registered in I2NSF framework&quot;, I don&#39;t fo=
llow what is getting registered with what examples.<br>
<br>
** Section 6.=C2=A0 Typo. s/registed/registered/<br>
<br>
** Section 6.1.=C2=A0 Figure 7 and 8.=C2=A0 A few questions about both exam=
ples.<br>
<br>
-- what is SNS?=C2=A0 Please expand the acronym (Social Networking Service?=
)<br>
<br>
-- the text seems to suggest that this block will only occur during busines=
s hours.=C2=A0 However, the time interval is set as:<br>
=C2=A0 =C2=A0 =C2=A0&lt;absolute-time-interval&gt;<br>
=C2=A0 =C2=A0 =C2=A0 &lt;start-date-time&gt;2019-08-01T09:00:00Z&lt;/start-=
date-time&gt;<br>
=C2=A0 =C2=A0 =C2=A0 &lt;end-date-time&gt;2019-12-31T18:00:00Z&lt;/end-date=
-time&gt;<br>
=C2=A0 =C2=A0 =C2=A0&lt;/absolute-time-interval&gt;<br>
<br>
Doesn&#39;t this mean that all traffic between August 1, 2019 - December 31=
 2019 would match (not just 0900 - 1800 every day).<br>
<br>
** Section 6.1.=C2=A0 Figure 9.=C2=A0 It doesn&#39;t not feel appropriate t=
o call out &quot;facebook&quot; and &quot;Instagram&quot;, please come up w=
ith a more generic example.<br>
<br>
** Section 6.1.=C2=A0 Figure 9.=C2=A0 The figure text says web filtering du=
ring business hours, but the XML doesn&#39;t seem to show time constraints.=
<br>
<br>
** Section 6.1.=C2=A0 How does this model distinguish between per-packet vs=
. per-flow operations?=C2=A0 The time and IP based actions of the firewall =
could be executed on a per packet basis.=C2=A0 However, <br>
to do the URL filtering requires stream reassembly.=C2=A0 The action on URL=
 filtering is to drop the packet:<br>
<br>
&lt;packet-action&gt;<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0&lt;egress-action&gt;drop&lt;/egress-action&gt;<=
br>
<br>
but shouldn&#39;t it be the flow?<br>
<br>
** Section 6.2.=C2=A0 Please use an example domain to represent a malicious=
 domain -- @<a href=3D"http://voip.mailcious.example.com" rel=3D"noreferrer=
" target=3D"_blank">voip.mailcious.example.com</a><br>
<br>
** Section 6.3.=C2=A0 Typo. s/contrl/control/<br>
<br>
** Section 8.<br>
=C2=A0 =C2=A0 o ietf-i2nsf-policy-rule-for-nsf: The attacker may provide in=
correct<br>
=C2=A0 =C2=A0 =C2=A0 policy information of any target NSFs by illegally mod=
ifying this.<br>
<br>
I don&#39;t follow the legality of modifying the configuration.=C2=A0 Perha=
ps it would be clearer to say that writing to almost any element of the mod=
ule would directly impact the configuration of the security functions on th=
e network -=C2=A0 completely turning off security monitoring and mitigation=
 capabilities; altering the scope of this monitoring and mitigation; creati=
ng an overwhelming logging volume to overwhelm downstream analytics or stor=
age capacity; or creating logging patterns which confuse or rendering usele=
ss trained statistics or artificial intelligence models.<br>
<br>
** Idnits returned:<br>
<br>
=C2=A0 =3D=3D The document doesn&#39;t use any RFC 2119 keywords, yet seems=
 to have RFC<br>
=C2=A0 =C2=A0 =C2=A02119 boilerplate text.<br>
<br>
=C2=A0 Checking references for intended status: Proposed Standard<br>
=C2=A0 --------------------------------------------------------------------=
--------<br>
<br>
=C2=A0 =C2=A0 =C2=A0(See RFCs 3967 and 4897 for information about using nor=
mative references<br>
=C2=A0 =C2=A0 =C2=A0to lower-maturity documents in RFCs)<br>
<br>
=C2=A0 ** Obsolete normative reference: RFC 1700 (Obsoleted by RFC 3232)<br=
>
<br>
=C2=A0 ** Downref: Normative reference to an Informational RFC: RFC 3232<br=
>
<br>
=C2=A0 ** Downref: Normative reference to an Informational RFC: RFC 3849<br=
>
<br>
=C2=A0 ** Downref: Normative reference to an Informational RFC: RFC 5737<br=
>
<br>
=C2=A0 ** Downref: Normative reference to an Informational RFC: RFC 8329<br=
>
<br>
Per RFC3232, I&#39;m not sure why it is being cited.=C2=A0 Is it being used=
 to indicate that an IANA registry stores a particular protocol value (e.g.=
, the IPv4 protocol field)?=C2=A0 If so, then reference the IANA registry i=
nstead.<br>
<br>
Per RFC3849 and RFC5737, just dropped these references outright.=C2=A0 They=
 aren&#39;t need to explain the reserved addressed.<br>
<br>
Per RFC8329, I&#39;ve noted above in my feedback on my not understanding ho=
w this document explain the YANG module elements in which it is being cited=
.<br>
<br>
For the shepherd write-up, please just add that idnit is throwing an error =
on RFC8177, but that is a legitimate reference (in the YANG module)<br>
<br>
Regards,<br>
Roman<br>
<br>
_______________________________________________<br>
I2nsf mailing list<br>
<a href=3D"mailto:I2nsf@ietf.org" target=3D"_blank">I2nsf@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/i2nsf" rel=3D"noreferrer" =
target=3D"_blank">https://www.ietf.org/mailman/listinfo/i2nsf</a><br>
</blockquote></div><br clear=3D"all"><div><br></div>-- <br><div dir=3D"ltr"=
 class=3D"gmail_signature"><div dir=3D"ltr"><div><div dir=3D"ltr"><div><div=
 dir=3D"ltr"><div><div dir=3D"ltr">=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br>Mr. Jaehoon (Paul) Jeong, Ph.=
D.<br>Associate Professor<br>Department of Computer Science and Engineering=
<br>Sungkyunkwan University<br>Office: +82-31-299-4957<br>Email: <a href=3D=
"mailto:jaehoon.paul@gmail.com" target=3D"_blank">jaehoon.paul@gmail.com</a=
>,=C2=A0<a href=3D"mailto:pauljeong@skku.edu" style=3D"font-size:12.8px" ta=
rget=3D"_blank">pauljeong@skku.edu</a><br>Personal Homepage: <a href=3D"htt=
p://cpslab.skku.edu/people-jaehoon-jeong.php" target=3D"_blank">http://iotl=
ab.skku.edu/people-jaehoon-jeong.php</a><br></div></div></div></div></div><=
/div></div></div>

--0000000000004e1e6f05b2f1ccd8--


From nobody Sat Oct 31 06:12:50 2020
Return-Path: <daedulus@btconnect.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 7B6A13A0AA6; Sat, 31 Oct 2020 06:12:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.148
X-Spam-Level: 
X-Spam-Status: No, score=-2.148 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, MSGID_FROM_MTA_HEADER=0.001, NICE_REPLY_A=-0.247, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=btconnect.onmicrosoft.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 O9g6sjLlbvfs; Sat, 31 Oct 2020 06:12:45 -0700 (PDT)
Received: from EUR05-VI1-obe.outbound.protection.outlook.com (mail-vi1eur05on2107.outbound.protection.outlook.com [40.107.21.107]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id ECD653A0AA3; Sat, 31 Oct 2020 06:12:44 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=V+ly9Qqi0YH/bdl7DDFHQIM+xRmUeeQzKPF7MbLPksl/bKzNhcdv8i2G0X0+Y9gYcAg1f3wd3/dW/AFX87gjEUuORvQDHJDRHeqLXpTH4TgHLr7SKK7aMUlang3tmX6e5TeZt3KKf2DiesU1ELEy0N/85p3tAAvJdvXPTIVgcpz/WEYybkImolmdQrkVclCAy1I24MAsdhUpTqPgrWRRGHYF0T2oNzAQ8huaWxUnnjiQiuxPmZSpb1JjKX61SBtEDZh6nC6KTxPdwfef1ywwxmifXbP7s+htjTiw67AaWA46fV+PzSdV4Z3/q/NXy8pD011eGUmduREBEN+bhW4nwQ==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=3v6o5bsWYpQxXTP2OwWAHMWOwOLh23jzOzjc4oRLERc=; b=Uv/8PGCQgfq/c23ccIvSkVzOExunnN8inMKNWxilEO6oYq+Q+D24QoYMlc8hbaWJtSZ7CgGZSiaS1Up99FwM+YO7cF6DZqc1p0ZwXTdO1NfHeDbC7xLv2pUb8NipvsSUPO0R4T2JTDXnLjPGtRtJg/XP6E8Zf+UxgF5RCoeRF1cBdXf+ABDB2uDAH1Ge5zHbikoWDbQu6YS2DEb75cHj5Y234QA0AWgHE3OkPy6y+1tDBmUytuIAl0zY+3jg5FwjhTK2wyjhqsHBMQK33Vdo/ria3ti/q54R/W9NSFckhe5/FPDKj9aAupmpj7vdjp2XhaiZOe/D6d/YZG6L3y9Y2g==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=btconnect.com; dmarc=pass action=none header.from=btconnect.com; dkim=pass header.d=btconnect.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=btconnect.onmicrosoft.com; s=selector2-btconnect-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=3v6o5bsWYpQxXTP2OwWAHMWOwOLh23jzOzjc4oRLERc=; b=YGvS0Ndoq1emXLj5S0u1lAPQjF0QxqU5B+Ne7U8uWlj8JGom+sDeZpBI9OBGAik45rhKbj4S9tN/0YyuXvpz3licWTVhJq/Q70WS/RExbTUCvCuSDfhNl9UIw/LemvuGNowbIk+pRK13jRqvc3HCarvnBaUoED3NryH+6hRj9wg=
Authentication-Results: um.es; dkim=none (message not signed) header.d=none;um.es; dmarc=none action=none header.from=btconnect.com;
Received: from VI1PR07MB6704.eurprd07.prod.outlook.com (2603:10a6:800:18b::8) by VI1PR07MB4815.eurprd07.prod.outlook.com (2603:10a6:803:a9::30) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3541.10; Sat, 31 Oct 2020 13:12:41 +0000
Received: from VI1PR07MB6704.eurprd07.prod.outlook.com ([fe80::6407:6ea2:f517:eeae]) by VI1PR07MB6704.eurprd07.prod.outlook.com ([fe80::6407:6ea2:f517:eeae%7]) with mapi id 15.20.3541.010; Sat, 31 Oct 2020 13:12:41 +0000
To: Tero Kivinen <kivinen@iki.fi>, Roman Danyliw <rdd@cert.org>
References: <160337357077.29083.9236626834026808055@ietfa.amsl.com> <EE5AB669-73BB-4517-A6F4-23B7807FB36E@um.es> <5F9815D1.9010303@btconnect.com> <DDE550B1-9A9E-4954-B6F9-C0A33ECE1275@um.es> <5F99B221.3040504@btconnect.com> <56155C91-BFE8-4BA9-A55C-46B12E59CD94@um.es> <5F9AEFD3.90903@btconnect.com> <059aaae84a354411ad1023afa2a837ba@cert.org> <5F9BF578.6000101@btconnect.com> <834a668ac559460a9f356bbb6c16b8fd@cert.org> <24476.38596.868667.906930@fireball.acr.fi>
Cc: "ipsec@ietf.org" <ipsec@ietf.org>, "i2nsf@ietf.org" <i2nsf@ietf.org>, Gabriel Lopez <gabilm@um.es>, "ynir.ietf@gmail.com" <ynir.ietf@gmail.com>, Fernando Pereniguez-Garcia <fernando.pereniguez@cud.upct.es>, "last-call@ietf.org" <last-call@ietf.org>, Rafa Marin-Lopez <rafa@um.es>
From: tom petch <daedulus@btconnect.com>
Message-ID: <5F9D62C0.5030908@btconnect.com>
Date: Sat, 31 Oct 2020 13:12:32 +0000
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:38.0) Gecko/20100101 Thunderbird/38.5.0
In-Reply-To: <24476.38596.868667.906930@fireball.acr.fi>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
X-Originating-IP: [86.146.121.140]
X-ClientProxiedBy: LO2P265CA0271.GBRP265.PROD.OUTLOOK.COM (2603:10a6:600:a1::19) To VI1PR07MB6704.eurprd07.prod.outlook.com (2603:10a6:800:18b::8)
MIME-Version: 1.0
X-MS-Exchange-MessageSentRepresentingType: 1
Received: from [192.168.1.65] (86.146.121.140) by LO2P265CA0271.GBRP265.PROD.OUTLOOK.COM (2603:10a6:600:a1::19) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.20.3499.18 via Frontend Transport; Sat, 31 Oct 2020 13:12:40 +0000
X-MS-PublicTrafficType: Email
X-MS-Office365-Filtering-Correlation-Id: 196b41be-23f5-4562-b420-08d87d9ea5a1
X-MS-TrafficTypeDiagnostic: VI1PR07MB4815:
X-Microsoft-Antispam-PRVS: <VI1PR07MB4815E30A850082730C04A78BC6120@VI1PR07MB4815.eurprd07.prod.outlook.com>
X-MS-Oob-TLC-OOBClassifiers: OLM:10000;
X-MS-Exchange-SenderADCheck: 1
X-Microsoft-Antispam: BCL:0;
X-Microsoft-Antispam-Message-Info: G2isJ1FlD5iAmuZlWAzkSHuIGtDsKcgPtjgBKrwVe358RMOOBo3sK8NS9bVKJt0gy5aKXIpJoZy1iH0Y3D0OY7WF2xOmV6zAHIuQkXQE6Es1olJ9kedXYEi9GqZJ0GlrLXkXuLibR7JZD9FO83+tFucGlcCm60vcLLzfDWTyFjX1XQNSv1q1HOnu/ZMwMatovU81JtwhQnxhsqrO7itE2gnS849JbwJmBfwnbn6X3IB3K41Vj+fJMC+cjrVhb05SysAbiIMXdZEls+LRtL2u0HfYM3Y9+qxEHQoCli8cdQ56dElQ/8C0zp6BeME62Rv6E6fIkaPbY8KVTk42fSnoFA==
X-Forefront-Antispam-Report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;  IPV:NLI; SFV:NSPM; H:VI1PR07MB6704.eurprd07.prod.outlook.com; PTR:; CAT:NONE;  SFS:(39860400002)(366004)(396003)(136003)(346002)(376002)(5660300002)(8676002)(478600001)(54906003)(83380400001)(66476007)(66556008)(6666004)(66946007)(86362001)(87266011)(2906002)(110136005)(8936002)(16576012)(26005)(36756003)(33656002)(316002)(2616005)(956004)(186003)(4326008)(6486002)(16526019)(52116002)(53546011)(15650500001); DIR:OUT; SFP:1102; 
X-MS-Exchange-AntiSpam-MessageData: IE4jIdDfz5JQ5pTy1PHD7POqRRjcEuuFJJxcEsaRvEc4N/r5Ns4M7+uHUTvN5v9+ThbtHXYFhezpuQ82edIolr5ViSYfikpQ0wwSlmmVg7eSTpSN1Ew4a02FmNgCFTSEZycQucwUN4tQguidV0yyJKz4VRpLVxu7IE2YXVnFFg/6LiL/KttUNRoVITEFlk+mdNPZxl+eqH47uqA2uh+JVS0C3XfKKqh4gGjwwhDj5Td/DWpZVv1H9lnmhVZxbFUjrQrTiw4TYBLqLaosYZBfwgW8q0n1riwpq4Gvr71kyn8byhCyIrllttCf/FjHQE5ZtiiK8KVcyuhGZ/5lzWmEdgzvF6RJGLqhuM9DbZ/nngNpSjN06N9v7U3r+5JAPEsccOFQOWBjx3OQwsiQ34YMaIZ8AZafwsPSr+oXMN/u+vNoJqk/JOnEJOnx9mbGoIQUOcezpHBaLDJC/L482N0aJ45hmGo3ZDaj5TzqvugKnekjfwXW4zN9/wFx2DHbrgxE0xhQHApfa3mG/GzxZK2IOLAuEyeicHaHyOOT3kRlzBaM+5arxENAo74lCsUUnDxyEQSfzCuyIZmbKr0nx+s+edLuubdkr5Zej8CKoSAwYV7dQPFGGdPhSew/lDGnEO4Y3FqLDhTnN8foHvRN0lLA0w==
X-OriginatorOrg: btconnect.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 196b41be-23f5-4562-b420-08d87d9ea5a1
X-MS-Exchange-CrossTenant-AuthSource: VI1PR07MB6704.eurprd07.prod.outlook.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 31 Oct 2020 13:12:41.2467 (UTC)
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-CrossTenant-Id: cf8853ed-96e5-465b-9185-806bfe185e30
X-MS-Exchange-CrossTenant-MailboxType: HOSTED
X-MS-Exchange-CrossTenant-UserPrincipalName: W4nQVdWWf/2iMoCcgO+e69keCa61vZO/okv6VZCTzTAAftQ9ciX3gEg/OMfeZ7S7uWssqP97VUGkzKdSlbzTkA==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: VI1PR07MB4815
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2nsf/LKclATqJ67kV9DcXR6Q1zMAdGc0>
Subject: Re: [I2nsf] [IPsec] [Last-Call] New Version Notification for draft-ietf-i2nsf-sdn-ipsec-flow-protection-11.txt
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, 31 Oct 2020 13:12:49 -0000

On 30/10/2020 22:42, Tero Kivinen wrote:
> Roman Danyliw writes:
>>>>> It seems to me that the IANA entries for IKEv2 are incomplete.
>>>>> RFC8247 does a fine job of specifying algorithms and adding
>>>>> information such as status (MUST/SHOULD+), IoT, AEAD and so on,
>>>>> information which is not present on IANA.  The policy for, e.g.
>>>>> Transform Type 1, is expert review and entries have been added via
>>>>> draft-smyslov-esp-gont but the IANA entries lack this information
>>>>> and, looking at the I-D, I see no such information (nor is there any
>>>>> reason for it to be there).  Yet draft-ietf-i2nsf-sdn... needs
>>>>> this information as references in the YANG module show.
>
> I am lost what information is missing from the IANA registry.


Tero

Thanks for getting back to me.  What is missing from the IANA registry 
is the guidance as to the status of the algorithm, how highly it is 
recommended or not.  This I-D tells people to go to RFC8247 and the IANA 
Registry for advice; RFC8247 gives that advice; the IANA web page does not.

And RFC8247 specifies which algorithm are AEAD, the web page does not. 
The YANG module behaves differently depending on whether or not the 
algorithm is AEAD; YANG implementors need to know, having this 
information on the web page would make it easier for YANG implementors.

And RFC8247 specifies IoT, which I do not think is yet a consideration here.

As I said, we are currently ok but as new algorithms get added, by 
Expert Review, then that information is needed and may not be available 
as there is no requirement for the Expert Reviewer to make it available.

As I said to Roman, the TLS WG found that they needed to add extra 
columns to their web pages of algorithms.  Different columns (e.g. DTLS 
not AEAD) but I think that the situation is otherwise identical so I am 
anticipating that in a year or two you will see what I mean:-).  In 
passing, the TLS WG determine by consensus what the status is for a new 
algorithm but the Expert Reviewer makes it available via the web site 
whether or not it is in an RFC.

I take your point about duplicating data - no relational databases here! 
- but the answer is to specify which is authoritative and for me that 
should be the IANA pages as it is for many assignments in the context of 
YANG and before that SMI going back decades.

Tom Petch


The
> registry do include numbers from draft-smyslov-esp-gost document. The
> RFC8247 says:
> ----------------------------------------------------------------------
> 1.3.  Updating Algorithm Requirement Levels
> ...
>      .... As a result, any algorithm listed at the IKEv2
>     IANA registry not mentioned in this document MAY be implemented.
> ----------------------------------------------------------------------
> I.e., all algorithms not listed there are MAY to implement.
>
> But I do not see any reason why the yang module should provide any
> other than pointer to the IANA registry, and the IANA registry already
> has pointer to the RFC8247 to indicate the requirement levels for
> algorithms.
>
>>>>> It seems to me that this is a similar situation to that which the TLS
>>>>> WG found itself in and which led to a revision of the TLS IANA
>>>>> entries to provide what was needed via additional columns.
>
> There was some requests to modify the IANA registry while we were
> publishing RFC 8247 and the WG decided against it, and instead decided
> to provide pointer to the RFC 8211 and RFC 8247 in the notes section.
>
> The reason for that is that duplicating information always causes
> problems, and because there is no (public) history of the IANA
> registries, there is no way of finding out when and why specific
> change to the registry was done unless there happens to be RFC that
> actually did that change.
>
> I myself as an IANA expert of those registries do think it is better
> that working group will do RFC that will update the levels, and that
> will leave audit trail and public working group mailing list
> discussion about the changes.
>
>>>>> I think that the IANA pages for IKEv2 need revising so that that
>>>>> additional information that RFC8247 provides is required as
>>>>> additional columns in the IANA entries at least for Type 1, Type 2,
>>>>> Type 3, Type 4 and Authentication Method.
>
> I fail to see why does that information need to be in the IANA
> registry? This is YANG model for IPsec, it should just refer to the
> IANA registry about the mapping from algorithms to numbers and other
> way around, but whether the algorithm is recommended or not, does not
> belong to the YANG model, as that is not something that can be
> modified by configuration or be part of running state.
>
> This document seems to have wierd text in it:
>
>        typedef encryption-algorithm-type {
>          type uint16;
>          description
>            "The encryption algorithm is specified with a 16-bit
>            number extracted from IANA Registry. The acceptable
>            values MUST follow the requirement levels for
>            encryption algorithms for ESP and IKEv2.";
>
> I do not see what the last sentence of the text is trying to say? Does
> it mean that this yang model cannot be shown of running configuration
> where someone is using one the algorithms not considered safe anymore?
> In ietf we usually just try to say what implementors are implementing,
> we do not that often limit what adminstrators can configure. If the
> implementation happens to implement one of those weak ciphers for
> example for talking to one obsoleted old hardware that only supports
> them, then I do not see why this yang model should forbid showing
> running status of such configuration.
>
> I think this document should just say that the algorithm numbers are
> from the IANA registry, and nothing more. There might be informal
> reference to the RFC 8221, and RFC 8247 but even that should not be
> needed, as anybody implementing IKEv2 or ESP will already follow those
> and only implement the algorithms from there that they seem proper. In
> some cases that selection might include algorithms which are on SHOULD
> NOT or even MUST NOT, if the backward compatibility to obsolete
> hardware is more important than conformance.
>
>>> This I-D, as you quote, points to RFC8247 for guidance and that is
>>> fine. But security moves on and new algorithms will be needed and
>>> this I-D also points to the IANA registry, which is Expert Review,
>>> where new entries have been added already; and for those the IANA
>>> Registry gives no guidance and the I-D that IANA references for
>>> the new entries - written by the Expert Reviewer! - also gives no
>>> guidance. Over time we are likely to accrue algorithms with no
>>> guidance unless and until an RFC8247-bis appears or we require
>>> IANA to have columns for guidance. Currently the new algorithms
>>> are GOST and so perhaps of limited interest but on the TLS list I
>>> am always seeing new algorithms appear and there the new IANA
>>> entry is required to give guidance. My sense is that IKEv2 is a
>>> bit slower to take up new ones but, as with RFC8247, it does
>>> eventually.
>
> The original cryptographic algorithm impelemtation requirements for
> ESP and AH was published as RFC4305 in 2007. It was replaced with
> RFC7321 in 2014, and that was replaced with RFC8221 in 2017. For IKEv2
> we skipped the 2014 update, as that was not needed. We do have plans
> to keep that draft up to date, and update it when there is need for
> that, most likely in next 5 years or so, provided that implementation
> status of some of new algorithms progresses favorably.
>
>>> I think that users need those extra columns that RFC8247 provides
>>> on the IANA website so that when new algorithms are added by
>>> Expert Review, then that guidance must be added as well. This is
>>> what the TLS WG came round to and I think that IKEv2 needs to do
>>> the same.
>
> I as an Expert does not want to decide whether the individual request
> to add new 3rot13 cipher to the IANA registry should be MUST NOT,
> SHOULD NOT, MAY or what. If the field is in the IANA registry then
> whoever requests to add information to there can request whatever
> value they want for that field too. Of course as an IANA expert I can
> reject that by saying that 3rot13 is not MUST, but it is MUST NOT
> algorithm, and then we can have discussion about that.
>
> I rather have that discussion in the working group when we are
> updating the requirements document next time. And as I said IANA
> registries do not have any (public) history, or any way of finding out
> why they got changed and who did the change. There has happened some
> changes in the registry where I as an IANA Expert was not aware of at
> all...
>
> And if I need to find out when ENCR_MAGMA_MGM_KTREE was added or when
> some of those earlier algorithms was renamed, I need to go to my
> private mail archives.
>


From nobody Sat Oct 31 07:01:13 2020
Return-Path: <smyslov.ietf@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 40AF93A0B79; Sat, 31 Oct 2020 07:01:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level: 
X-Spam-Status: No, score=-2.098 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, 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 W68WjCbMNIcf; Sat, 31 Oct 2020 07:01:10 -0700 (PDT)
Received: from mail-lf1-x12e.google.com (mail-lf1-x12e.google.com [IPv6:2a00:1450:4864:20::12e]) (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 DA6463A0B76; Sat, 31 Oct 2020 07:01:09 -0700 (PDT)
Received: by mail-lf1-x12e.google.com with SMTP id y184so9548852lfa.12; Sat, 31 Oct 2020 07:01:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:to:cc:references:in-reply-to:subject:date:message-id :mime-version:content-transfer-encoding:thread-index :content-language; bh=j49OLrG+oKpAh9gikEB3vX8qLgfyNMwzP8OFncFM24I=; b=WbsY6CFU4M9W/NPFdYGO+DhkSfXUVevA5lRKoHLpPs8cfHluTHLZ97u+xeM9MaIGzu 2CMLK+QAc0g9Slha5XcEntHjVONi2mpEMr8A8C3tboPuSW1pq4a0jPmXza7VfuywTrX8 OOsuXDgO6QSjMmBHU7HnC5dPwamTkD12dTOSlSOjA6tUD252LSf0hs+o0FIdkxBME+l6 Q91DODLndfgjX5vJZLewsf2aUAlmxxxeNTPAvBHmgJOH0IwwYI50a+cA0uAfAJ1tPDA+ iQT/Y025w6U6zDRyp80n6gqRvZAYpi1O5sXqgzXnxCyowU5IAUhF1QhgrEjcG1lDPx1r ddPA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:references:in-reply-to:subject:date :message-id:mime-version:content-transfer-encoding:thread-index :content-language; bh=j49OLrG+oKpAh9gikEB3vX8qLgfyNMwzP8OFncFM24I=; b=JMgHLQhhcDWiEyTpAdx3dB8aMY4yTumHo0cHMwpr7Y14MfWJkJCA0HIqovERBKE+PI VmNEaF4g4EPhUSL1czoefiZb1NF3sGObrh8PztlJxzQxg+U538xKJgeM9UbIQiunSqDN 4M3t4iwfVcXH6auC6Bj4dS2+PNm4fY/ljRQT4iJGUAGKAPi11IZOCOW9fBP7ZcyctJq7 jKaPC5l/HiQvdiGehVLznqDRMH45PAICBiVTAnU53MEyaZUGUHjnFxA70jfS/2DPMyhR vyLf1rX1849tv67NETTAp2+Tc+RMPcROznfkmk3bzPjsQd7sh7ewHxO9yv07qj/gzsCY N7pw==
X-Gm-Message-State: AOAM533uzXa780vTxYNzP91zYsC2BCIlZbFBi/6AiKDcme4TboyK+VXK wyHVESHD2rlXFc7yE6aOMXU=
X-Google-Smtp-Source: ABdhPJxotGKRU9e0wfabyZf59etV2wJFeUNahwL4ZVIPnzPTqP4d3NJNcqmpWsHROCjC97DOP78h9g==
X-Received: by 2002:ac2:5976:: with SMTP id h22mr2556309lfp.507.1604152867939;  Sat, 31 Oct 2020 07:01:07 -0700 (PDT)
Received: from chichi (37-144-56-120.broadband.corbina.ru. [37.144.56.120]) by smtp.gmail.com with ESMTPSA id y8sm933753lfl.184.2020.10.31.07.01.06 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Sat, 31 Oct 2020 07:01:07 -0700 (PDT)
From: "Valery Smyslov" <smyslov.ietf@gmail.com>
To: "'tom petch'" <daedulus@btconnect.com>, "'Tero Kivinen'" <kivinen@iki.fi>,  "'Roman Danyliw'" <rdd@cert.org>
Cc: "'Fernando Pereniguez-Garcia'" <fernando.pereniguez@cud.upct.es>, <i2nsf@ietf.org>, "'Gabriel Lopez'" <gabilm@um.es>, <ynir.ietf@gmail.com>, <ipsec@ietf.org>, <last-call@ietf.org>, "'Rafa Marin-Lopez'" <rafa@um.es>
References: <160337357077.29083.9236626834026808055@ietfa.amsl.com> <EE5AB669-73BB-4517-A6F4-23B7807FB36E@um.es> <5F9815D1.9010303@btconnect.com> <DDE550B1-9A9E-4954-B6F9-C0A33ECE1275@um.es> <5F99B221.3040504@btconnect.com> <56155C91-BFE8-4BA9-A55C-46B12E59CD94@um.es> <5F9AEFD3.90903@btconnect.com> <059aaae84a354411ad1023afa2a837ba@cert.org> <5F9BF578.6000101@btconnect.com> <834a668ac559460a9f356bbb6c16b8fd@cert.org> <24476.38596.868667.906930@fireball.acr.fi> <5F9D62C0.5030908@btconnect.com>
In-Reply-To: <5F9D62C0.5030908@btconnect.com>
Date: Sat, 31 Oct 2020 17:01:00 +0300
Message-ID: <000001d6af8e$43baa2d0$cb2fe870$@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQIoWC6Ry6044q/zCrCUKcB+KBw60wJiaB/IAqnvI9sBjCP/TgJL0fDJAoEYK+kB00mNbgLfgwdiAuAT4rcCA2fXuQGCTHRUAkPcMRyoSFYCoA==
Content-Language: ru
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2nsf/YIYBMIM6d7S1zmCEN4lmzVtCMEw>
Subject: Re: [I2nsf] [IPsec] [Last-Call] New Version Notification for draft-ietf-i2nsf-sdn-ipsec-flow-protection-11.txt
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, 31 Oct 2020 14:01:12 -0000

Hi Tom,

we discussed with the chairs the usefulness of adding "Recommended/Not
recommended" column
(as TLS WG did) into the IKEv2 algorithm registries back in 2018 in Bangkok
and I was one who 
of those who initially suggested this. However, Tero made a very good point
that 
IANA doesn't have any public history. So, in the ipsecme WG another approach
was taken - we have RFCs that say which algorithms are recommended/not
recommended
for ESP and for IKEv2 and these RFCs are updated periodically.

> Thanks for getting back to me.  What is missing from the IANA registry
> is the guidance as to the status of the algorithm, how highly it is
> recommended or not.  This I-D tells people to go to RFC8247 and the IANA
> Registry for advice; RFC8247 gives that advice; the IANA web page does
not.

As Tero said, the IANA web page references current RFCs (8221 & 8247 at the
moment) 
that list recommended algorithms. Just one more level of indirection. All
algorithms that are not listed
in these RFC are treated as "not recommended" by default, including newly
added algorithms.

> And RFC8247 specifies which algorithm are AEAD, the web page does not.
> The YANG module behaves differently depending on whether or not the
> algorithm is AEAD; YANG implementors need to know, having this
> information on the web page would make it easier for YANG implementors.

Is is a problem to open corresponding RFC or I-D? Or do you want to say that

YANG implementers don't need any other information about algorithms
except whether it's AEAD and whether it's recommended?

Regards,
Valery Smyslov.

> And RFC8247 specifies IoT, which I do not think is yet a consideration
here.
> 
> As I said, we are currently ok but as new algorithms get added, by
> Expert Review, then that information is needed and may not be available
> as there is no requirement for the Expert Reviewer to make it available.
> 
> As I said to Roman, the TLS WG found that they needed to add extra
> columns to their web pages of algorithms.  Different columns (e.g. DTLS
> not AEAD) but I think that the situation is otherwise identical so I am
> anticipating that in a year or two you will see what I mean:-).  In
> passing, the TLS WG determine by consensus what the status is for a new
> algorithm but the Expert Reviewer makes it available via the web site
> whether or not it is in an RFC.
> 
> I take your point about duplicating data - no relational databases here!
> - but the answer is to specify which is authoritative and for me that
> should be the IANA pages as it is for many assignments in the context of
> YANG and before that SMI going back decades.
> 
> Tom Petch
> 
> 
> The
> > registry do include numbers from draft-smyslov-esp-gost document. The
> > RFC8247 says:
> > ----------------------------------------------------------------------
> > 1.3.  Updating Algorithm Requirement Levels
> > ...
> >      .... As a result, any algorithm listed at the IKEv2
> >     IANA registry not mentioned in this document MAY be implemented.
> > ----------------------------------------------------------------------
> > I.e., all algorithms not listed there are MAY to implement.
> >
> > But I do not see any reason why the yang module should provide any
> > other than pointer to the IANA registry, and the IANA registry already
> > has pointer to the RFC8247 to indicate the requirement levels for
> > algorithms.
> >
> >>>>> It seems to me that this is a similar situation to that which the
TLS
> >>>>> WG found itself in and which led to a revision of the TLS IANA
> >>>>> entries to provide what was needed via additional columns.
> >
> > There was some requests to modify the IANA registry while we were
> > publishing RFC 8247 and the WG decided against it, and instead decided
> > to provide pointer to the RFC 8211 and RFC 8247 in the notes section.
> >
> > The reason for that is that duplicating information always causes
> > problems, and because there is no (public) history of the IANA
> > registries, there is no way of finding out when and why specific
> > change to the registry was done unless there happens to be RFC that
> > actually did that change.
> >
> > I myself as an IANA expert of those registries do think it is better
> > that working group will do RFC that will update the levels, and that
> > will leave audit trail and public working group mailing list
> > discussion about the changes.
> >
> >>>>> I think that the IANA pages for IKEv2 need revising so that that
> >>>>> additional information that RFC8247 provides is required as
> >>>>> additional columns in the IANA entries at least for Type 1, Type 2,
> >>>>> Type 3, Type 4 and Authentication Method.
> >
> > I fail to see why does that information need to be in the IANA
> > registry? This is YANG model for IPsec, it should just refer to the
> > IANA registry about the mapping from algorithms to numbers and other
> > way around, but whether the algorithm is recommended or not, does not
> > belong to the YANG model, as that is not something that can be
> > modified by configuration or be part of running state.
> >
> > This document seems to have wierd text in it:
> >
> >        typedef encryption-algorithm-type {
> >          type uint16;
> >          description
> >            "The encryption algorithm is specified with a 16-bit
> >            number extracted from IANA Registry. The acceptable
> >            values MUST follow the requirement levels for
> >            encryption algorithms for ESP and IKEv2.";
> >
> > I do not see what the last sentence of the text is trying to say? Does
> > it mean that this yang model cannot be shown of running configuration
> > where someone is using one the algorithms not considered safe
> anymore?
> > In ietf we usually just try to say what implementors are implementing,
> > we do not that often limit what adminstrators can configure. If the
> > implementation happens to implement one of those weak ciphers for
> > example for talking to one obsoleted old hardware that only supports
> > them, then I do not see why this yang model should forbid showing
> > running status of such configuration.
> >
> > I think this document should just say that the algorithm numbers are
> > from the IANA registry, and nothing more. There might be informal
> > reference to the RFC 8221, and RFC 8247 but even that should not be
> > needed, as anybody implementing IKEv2 or ESP will already follow those
> > and only implement the algorithms from there that they seem proper. In
> > some cases that selection might include algorithms which are on SHOULD
> > NOT or even MUST NOT, if the backward compatibility to obsolete
> > hardware is more important than conformance.
> >
> >>> This I-D, as you quote, points to RFC8247 for guidance and that is
> >>> fine. But security moves on and new algorithms will be needed and
> >>> this I-D also points to the IANA registry, which is Expert Review,
> >>> where new entries have been added already; and for those the IANA
> >>> Registry gives no guidance and the I-D that IANA references for
> >>> the new entries - written by the Expert Reviewer! - also gives no
> >>> guidance. Over time we are likely to accrue algorithms with no
> >>> guidance unless and until an RFC8247-bis appears or we require
> >>> IANA to have columns for guidance. Currently the new algorithms
> >>> are GOST and so perhaps of limited interest but on the TLS list I
> >>> am always seeing new algorithms appear and there the new IANA
> >>> entry is required to give guidance. My sense is that IKEv2 is a
> >>> bit slower to take up new ones but, as with RFC8247, it does
> >>> eventually.
> >
> > The original cryptographic algorithm impelemtation requirements for
> > ESP and AH was published as RFC4305 in 2007. It was replaced with
> > RFC7321 in 2014, and that was replaced with RFC8221 in 2017. For IKEv2
> > we skipped the 2014 update, as that was not needed. We do have plans
> > to keep that draft up to date, and update it when there is need for
> > that, most likely in next 5 years or so, provided that implementation
> > status of some of new algorithms progresses favorably.
> >
> >>> I think that users need those extra columns that RFC8247 provides
> >>> on the IANA website so that when new algorithms are added by
> >>> Expert Review, then that guidance must be added as well. This is
> >>> what the TLS WG came round to and I think that IKEv2 needs to do
> >>> the same.
> >
> > I as an Expert does not want to decide whether the individual request
> > to add new 3rot13 cipher to the IANA registry should be MUST NOT,
> > SHOULD NOT, MAY or what. If the field is in the IANA registry then
> > whoever requests to add information to there can request whatever
> > value they want for that field too. Of course as an IANA expert I can
> > reject that by saying that 3rot13 is not MUST, but it is MUST NOT
> > algorithm, and then we can have discussion about that.
> >
> > I rather have that discussion in the working group when we are
> > updating the requirements document next time. And as I said IANA
> > registries do not have any (public) history, or any way of finding out
> > why they got changed and who did the change. There has happened some
> > changes in the registry where I as an IANA Expert was not aware of at
> > all...
> >
> > And if I need to find out when ENCR_MAGMA_MGM_KTREE was added or
> when
> > some of those earlier algorithms was renamed, I need to go to my
> > private mail archives.
> >
> 
> _______________________________________________
> I2nsf mailing list
> I2nsf@ietf.org
> https://www.ietf.org/mailman/listinfo/i2nsf


From nobody Sat Oct 31 11:28:21 2020
Return-Path: <ynir.ietf@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 776843A0A1F; Sat, 31 Oct 2020 11:28:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level: 
X-Spam-Status: No, score=-2.098 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, 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 ZYq-u4A6qZdM; Sat, 31 Oct 2020 11:28:19 -0700 (PDT)
Received: from mail-ed1-x530.google.com (mail-ed1-x530.google.com [IPv6:2a00:1450:4864:20::530]) (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 178A43A0A1D; Sat, 31 Oct 2020 11:28:19 -0700 (PDT)
Received: by mail-ed1-x530.google.com with SMTP id dg9so9995168edb.12; Sat, 31 Oct 2020 11:28:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=rogoc34AoQgRRGmf7+AIwrRVGZGquvGHX+3rKTcfijs=; b=FVznnodqQxlhXxO06b7HIP27QQ9vrN44LDtS6gVEp09YATAxItsihMYE5skSfjFrAh YEyPodtr3Eh7KFAuXT3eJUOo9babibjPBcg6C3g+MGEMMQ9t1LDDNH0KijFLUjMX1RF1 A49TAVPAmEU2FnuqHHrjVLP0oa2v2O9qovas11kKHye7zws+HGjUyb67ZnJVoUHbJ89B P4pL8JQeXo3IlNi1b239HA64bFDl8GmsK7jY0Qp/XtYx59ac3tXCvMIsQpXnc0Ynx6ba //LF8+8DGzfS2e8t0DGhAhYYtn2wjrsxHkkrLMYTgUPtrqn2ENvUJh8Zhoe/PMnGGtwZ 0AtQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=rogoc34AoQgRRGmf7+AIwrRVGZGquvGHX+3rKTcfijs=; b=XVU21YCAYipQgebU2dOklctaDg9Utwf7kClj5XxuBuloC6OAC7mgNjX5U8YMBvCUkT yrReLHVZ43HZu0e65hDlMpq/5RrsLt3ylwGhA3F0d+mvVvIrA6yyVZnPKmuOAh8kD0uh 3HTH0evf1caWijBsgDS+x0bL0iDFD9m7NSLjldYVZXAS31W3ZSVla4zRxA+3Osu4PKqb SrDDmC3699Uet+xE8+rjSo9YTtvTiNjE0/c1xz9sld3/wDjHkoJum1d4VXm84WjCwftx Rv/Z7gqUt9sEFCno651NS+qnofTVja2Zc8iutIgHNfzHkjcCI6im12GlPfXQ1FxCvaGF qFJg==
X-Gm-Message-State: AOAM531C48jDjY/iXXWJJOznVfKWRKQeir/3qFyyOAGl/JrBswJWFa09 54zDrYt7bZmCXn6ii9SqQwg=
X-Google-Smtp-Source: ABdhPJwlqemdjGj47soKonBx7DKCacJ4obB00Y+pfizr/z9ri86a67aFlhDpqMPbiUFeA0CwAzQ3fQ==
X-Received: by 2002:a50:e087:: with SMTP id f7mr8597169edl.96.1604168897400; Sat, 31 Oct 2020 11:28:17 -0700 (PDT)
Received: from [192.168.1.15] ([46.120.57.147]) by smtp.gmail.com with ESMTPSA id rn28sm4848615ejb.22.2020.10.31.11.28.14 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Sat, 31 Oct 2020 11:28:16 -0700 (PDT)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\))
From: Yoav Nir <ynir.ietf@gmail.com>
In-Reply-To: <5F9D62C0.5030908@btconnect.com>
Date: Sat, 31 Oct 2020 20:28:13 +0200
Cc: Tero Kivinen <kivinen@iki.fi>, Roman Danyliw <rdd@cert.org>, "ipsec@ietf.org" <ipsec@ietf.org>, "i2nsf@ietf.org" <i2nsf@ietf.org>, Gabriel Lopez <gabilm@um.es>, Fernando Pereniguez-Garcia <fernando.pereniguez@cud.upct.es>, "last-call@ietf.org" <last-call@ietf.org>, Rafa Marin-Lopez <rafa@um.es>
Content-Transfer-Encoding: quoted-printable
Message-Id: <10736BF3-4833-4129-A3E2-B680696A80B5@gmail.com>
References: <160337357077.29083.9236626834026808055@ietfa.amsl.com> <EE5AB669-73BB-4517-A6F4-23B7807FB36E@um.es> <5F9815D1.9010303@btconnect.com> <DDE550B1-9A9E-4954-B6F9-C0A33ECE1275@um.es> <5F99B221.3040504@btconnect.com> <56155C91-BFE8-4BA9-A55C-46B12E59CD94@um.es> <5F9AEFD3.90903@btconnect.com> <059aaae84a354411ad1023afa2a837ba@cert.org> <5F9BF578.6000101@btconnect.com> <834a668ac559460a9f356bbb6c16b8fd@cert.org> <24476.38596.868667.906930@fireball.acr.fi> <5F9D62C0.5030908@btconnect.com>
To: tom petch <daedulus@btconnect.com>
X-Mailer: Apple Mail (2.3608.120.23.2.4)
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2nsf/EY09Q1LT7_R0zYYVaYGw0ncEZek>
Subject: Re: [I2nsf] [IPsec] [Last-Call] New Version Notification for draft-ietf-i2nsf-sdn-ipsec-flow-protection-11.txt
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, 31 Oct 2020 18:28:20 -0000

> On 31 Oct 2020, at 15:12, tom petch <daedulus@btconnect.com> wrote:
>=20
> On 30/10/2020 22:42, Tero Kivinen wrote:
>> Roman Danyliw writes:
>>>>>> It seems to me that the IANA entries for IKEv2 are incomplete.
>>>>>> RFC8247 does a fine job of specifying algorithms and adding
>>>>>> information such as status (MUST/SHOULD+), IoT, AEAD and so on,
>>>>>> information which is not present on IANA.  The policy for, e.g.
>>>>>> Transform Type 1, is expert review and entries have been added =
via
>>>>>> draft-smyslov-esp-gont but the IANA entries lack this information
>>>>>> and, looking at the I-D, I see no such information (nor is there =
any
>>>>>> reason for it to be there).  Yet draft-ietf-i2nsf-sdn... needs
>>>>>> this information as references in the YANG module show.
>>=20
>> I am lost what information is missing from the IANA registry.
>=20
>=20
> Tero
>=20
> Thanks for getting back to me.  What is missing from the IANA registry =
is the guidance as to the status of the algorithm, how highly it is =
recommended or not.  This I-D tells people to go to RFC8247 and the IANA =
Registry for advice; RFC8247 gives that advice; the IANA web page does =
not.

It=E2=80=99s possible to add a column in the IANA registry, but it is =
not possible to capture the information from 8247 in such a table.=20

RFC 8247 has =E2=80=9CMAY=E2=80=9D and =E2=80=9CSHOULD+=E2=80=9D labels, =
but it also has comments and a bunch of explanation, such as that some =
algorithm is a SHOULD for IoT, but not otherwise. I think it=E2=80=99s =
better to point people at the RFC where the information is, rather than =
post very partial information in an IANA table.

Yoav

