
From nobody Sat Dec  1 01:34:29 2018
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 9182612D4E8; Sat,  1 Dec 2018 01:34:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-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 Kmw3Gzj4PRjp; Sat,  1 Dec 2018 01:34:14 -0800 (PST)
Received: from xenon44.um.es (xenon44.um.es [155.54.212.171]) by ietfa.amsl.com (Postfix) with ESMTP id EAF18129C6B; Sat,  1 Dec 2018 01:34:13 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by xenon44.um.es (Postfix) with ESMTP id 850FE20292; Sat,  1 Dec 2018 10:34:07 +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 VsHxadkwlq9q; Sat,  1 Dec 2018 10:34:07 +0100 (CET)
Received: from [192.168.1.39] (73.red-2-138-17.dynamicip.rima-tde.net [2.138.17.73]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: rafa) by xenon44.um.es (Postfix) with ESMTPSA id 55D521FE4E; Sat,  1 Dec 2018 10:34:06 +0100 (CET)
Content-Type: multipart/alternative; boundary="Apple-Mail=_F82529B5-233B-4502-A774-9BB53D71F8EB"
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
From: Rafa Marin-Lopez <rafa@um.es>
In-Reply-To: <alpine.LRH.2.21.1811180149220.25604@bofh.nohats.ca>
Date: Sat, 1 Dec 2018 10:34:06 +0100
Cc: Rafa Marin-Lopez <rafa@um.es>, Yoav Nir <ynir.ietf@gmail.com>, i2nsf@ietf.org, "ipsec@ietf.org WG" <ipsec@ietf.org>
Message-Id: <67D2C7A7-2BDC-46CB-B9BC-B5DD16015D2B@um.es>
References: <A881C135-9BF7-4E93-BB7A-75EB3D1FF605@gmail.com> <6839D47C-4074-486F-9350-8EB7B378036C@um.es> <DAE14995-8504-4134-B021-93D56A4994FB@gmail.com> <alpine.LRH.2.21.1811180149220.25604@bofh.nohats.ca>
To: Paul Wouters <paul@nohats.ca>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2nsf/x-etXo4OqNls9l7yyrWRKOC000s>
Subject: Re: [I2nsf] Review of draft-ietf-i2nsf-sdn-ipsec-flow-protection-03 (Section 5)
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, 01 Dec 2018 09:34:21 -0000

--Apple-Mail=_F82529B5-233B-4502-A774-9BB53D71F8EB
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Hi Paul,all:

Here you can find our answers for section 5.

> Section 5.1:
>=20
> The diagram lists:
>=20
> 	|   IKE    |      IPsec(SPD,PAD)  |
>=20
> Shouldn't that be:
>=20
>        | IKE(PAD) | IPsec(SPD, SAD)
>=20
> IKE is using the PAD information to tell IPsec to establish SPDs and =
SADs) ?

[Authors] The PAD is something defined in RFC 4301, which is independent =
of the key management protocol.

=46rom RFC 4301:
"The entry specifies the authentication protocol
   (e.g., IKEv1, IKEv2, KINK) method"
  =20
Therefore it is not something attached to the key management protocol =
itself but more related with IPsec implemenation. What it is true that =
PAD is not implemented in current Linux kernel and usually this =
information is set in the IKE implementation. Finally we have only =
described in Fig. 1 that SPD and PAD must be configured from the =
Controller. The SAD will be managed by the IKEv2 implementation. Same =
happens in Fig. 2.


>=20
>=20
> Section 5.1.1:
>=20
> What does this mean:
>=20
> 	Moreover, an east-west interface is required to exchange =
IPsec-related information.

[Authors] In SDN terminology an east-west interface is the communication =
interface between two controllers.

For example: https://tools.ietf.org/html/rfc7426 =
<https://tools.ietf.org/html/rfc7426>

If we have two gateways where we need to establish an IPsec SA and both =
are under the control of two different controllers then both Security =
Controllers needs to exchange information so that they need to agree in =
some information so that the configure their own gateways properly (see =
Fig. 5). An example: they have to agree that IKEv2 authentication will =
be based on raw public keys or pre-shared keys. And if it pre-shared =
keys they will have to agree in the PSK (Yes, one option to explore is =
IKEv2, more related comments in posterior answers.)
>=20
> Section 5.2:
>=20
>   In this case, the NSF does not deploy IKEv2 and, therefore, the
>   Security Controller has to perform the management of IPsec SAs by
>   populating and monitoring the SPD and the SAD.
>=20
> I would write:
>=20
> In this case, the NSF does not deploy IKEv2 and, therefore, the
> Security Controller has to perform the IKE security functions and =
management
> of IPsec SAs by populating and managing the SPD and the SAD.
>=20
> I added "IKE security functions" to make sure some entity is =
responsible
> for those items that are normally done by IKE (IV generation, prevent =
counter
> resets for same key, etc).
>=20
> I changed monitoring to managing, because I don't understand how it =
would "monitor"
> the NSF or what it would monitor. I assume also if during monitoring =
it finds
> something that needs changing (eg vpn tunnel up or down) that it will =
do so,
> so I think managing is the better word.

[Authors] Agreed with this text. Very reasonable.
>=20
> For this diagram, I would say IPsec(SPD, SAD) would need to also list =
the IKE
> security function it needs to use in an IKE-less scenario, which above =
I had
> called "management of IPsec SAs=E2=80=9D

[Authors]=20

How about this non-exhaustive list:

- IV generation
- prevent counter resets for same key
- Generation of pseudo-random cryptographic keys for the IPsec SAs
- Rekey of the IPsec SAs based on notification from the NSF  (i.e. =
expire)
- Generation of the IPsec SAs when required based on notifications (i.e. =
sadb_acquire)
- NAT Traversal discovery and management.=20
- ....


What about the following (non-exhaustive) tasks?
- SPI random generation
- Cryptographic algorithm/s selection
- Usage of extended sequence numbers
- Establishment of proper traffic selectors=20
- ....
>=20
> Section 5.3:
>=20
> As mentioned before, a better title would be: IKE vs IKEless
>=20
> I would also start this section with:
>=20
> Case 1 is more secure, because all security features of IKE are used =
to manage
> the IPsec SAs.

[Authors] We do understand the comment.

How about this new text:

=E2=80=9CIKE case provides better security properties than IKE-less =
case. In particular, the Security Controller is not able to observe what =
are the cryptographic keys used to protect data traffic."



>=20
> Section 5.3.1:
>=20
>   For case 1, the rekeying process is carried out by IKEv2, following
>   the configuration defined in the SPD.
>=20
> Technically this is the SPD and SAD, as the SPD would for example list =
the
> maximum number of packets allowed, but the SAD lists the number of =
packets
> that have happened.

[Authors] Ok. We will replace the text:=20

s/"For case 1, the rekeying process is carried out by IKEv2, following =
the configuration defined in the SPD."/"For IKEv2 case, the rekeying =
process is carried out by IKEv2, following the configuration defined in =
the SPD and SAD."
>=20
> I am a bit confused by the rekey description. I guess it assumes that =
the
> Security Controller sending of information is blocking? Eg when it =
tells
> the node to install an inbound IPsec SA, it is blocked from doing =
anything
> else. If this is not the case, then the 3 step program should be =
clarified
> that it needs to also receive confirmations. And if this is a =
non-blocking
> process, who is responsible for "retransmits" of these confirmations ?
> The same applies to the blocking or time-wait between step 2 and 3.

[Authors] Yes, the controller goes through this process in a blocking =
way per each step. That is, the Security Controller needs to finish =
correctly the step 1 before proceeding with step 2. This is possible =
since the Security Controller will receive a NETCONF rpc-reply with OK =
after installing the inbound in peer A and the same for peer B. When =
receiving both OKs, it can proceed to step 2. The same happens between =
step 2 and step 3.

The reason of doing this in this way is to prepare first the new inbound =
IPsec SAs and everything is ready, then the new outbound IPsec SAs. When =
the new outbound IPsec SAs are set, we have observed (at least in Linux =
kernel) that the new outbound IPsec SA is immediately used. Since the =
other peer has already the corresponding inbound SA no traffic loss =
happens.

However if we assume that some traffic loss is allowed, we could send =
inbound and outbound IPsec SAs in parallell to both nodes involved in =
the rekey. What do you think?

Regarding retransmission of the confirmation the NETCONF transport =
(SSH/TCP or TLS/TCP) will provide this.
>=20
> Also, I would say step 3 can be get rid of if the IPsec implementation =
can
> itself detect traffic on the new IPsec SA and it can delete the old =
IPsec
> SA itself without instruction from the Security Controller.

[Authors] Correct. We were wondering though how common this is (at least =
in linux kernels we have not seen this behaviour). Moreover, the =
Security Controller should know how this is implemented internally in =
the NSF to avoid sending this delete. Either that, or the NETCONF server =
in the NSF should pay attention to this by interacting with the kernel =
(through netlink=C2=BF?=C2=BF?) and remove it when it sees that traffic. =
I have seen that libreswan has a wishlist about this feature. Is there =
any movement in this side?
>=20
> Section 5.3.2:
>=20
> 	If one of the NSF restarts, it may lose part or all the IPsec =
state
>=20
> This "may" suggests a very interesting case. I doubt the NSF would =
store on
> non-volatile memory the IPsec symmetric keys for encryption, and the =
counter
> or ICV's used. If it could store that, the document needs some text =
about
> this in the Security Considerations because it will allow for easier =
theft
> of session material.

[Authors] Yes, this "may" is unfortunate because our assumption is that =
all this information will be in volatile memory. More specifically, we =
assume that NSF does not have any information in the startup-config =
(non-volatile), only in the running-config datastore (volatile)
>=20
> Rather, I suspect this may really is not true, and all of these =
devices would
> lose state?

[Authors] Correct. Although other aspects could be considered in the =
future (for example, is it reasonable to think that IKE configuration =
could be in non-volatile as well just in case the node falls?)
>=20
> 	In both cases, the Security Controller MUST be aware of the =
affected NSF
>=20
> I think this MUST is a little misleading. It is not desired behaviour =
but just
> an observation - it cannot not know its TCP session died ? Perhaps =
write:
>=20
> 	In both cases, the Security Controller is aware of the affected =
NSF

[Authors] Yes, this is better.

>=20
> A similar case for the next sentence MUST keyword:
>=20
> 	Moreover, the Security Controller MUST have a register about all =
the
> 	NSFs that have IPsec SAs with the affected NSF.
>=20
> so write:
>=20
> 	Moreover, the Security Controller has a register about all the
> 	NSFs that have IPsec SAs with the affected NSF.

[Authors] Agree.=20

>=20
>=20
> 	(It is TBD in the model).
>=20
> This remark seems to need to be resolved before publication ?

[Authors] It is already fixed but we missed to remove this text.

+--rw initial-contact?     boolean
>=20
>   In Case 2, if the Security Controller detects that a NSF has lost =
the
>   IPsec SAs (e.g. it reboots) it will follow similar steps to rekey:
>   the steps 1 and 2 remain equal but the step 3 will be slightly
>   different.  For example, if we assume that NSF B has lost its state,
>   the Security Controller MUST only delete the old IPsec SAs from A in
>   step 3.
>=20
> I don't understand why this paragraph about NSF state loss seems to =
talk
> about "step 3" which can only be referring to the "rekeying process" =
of
> the previous section. It should only mention that it should configure =
new
> IPsec SAs between the failed node and all the nodes the failed node =
talked
> to and only after those are estlibhsed, it can send a delete for the =
old
> IPsec SAs on the non-failed nodes. This prevents the non-failed nodes =
from
> leaking plaintext.

[Authors] Agree. However I was thinking that failed node may not come to =
life again.
In such a case, if a failed node falls, the active IPsec SAs in the rest =
of non-failed nodes with the failed node are not useful. Therefore, the =
SC could first delete the old IPsec SAs on the non-failed nodes. If the =
failed node comes to live, then the SC will install first the new =
inbound IPsec SAs and after these IPsec SAs are established then to =
install the outbound IPsec SAs. What do you think?

Having said that, we propose to replace this paragraph with the =
following text:

"In IKE-less case, if the Security Controller detects that a NSF has =
lost the IPsec SAs (e.g. it reboots) it will delete the old IPsec SAs of =
the non-failed nodes established with the failed node (step 1). This =
prevents the non-failed nodes from leaking plaintext. If the failed node =
come to live, the Security Controller will configure the new inbound =
IPsec SAs between the failed node and all the nodes the failed talked to =
(step 2). After these inbound IPsec SAs have been established, the =
Security Controller can configure the outbound IPsec SAs (step 3)."

>=20
> Section 5.3.3:
>=20
> I'm confused how the Security Controller can know what NAT ports to =
convey to
> the NSF agent. Without IKE traffic, there is no port NAT mapping? So =
unless
> the Security Controller _is_ the NAT gateway, it would never know this
> information? So I am skeptical if the NAT case can ever work without =
IKE.
> I also do not know how the Security Controller could decide between =
UDP,
> TCP or TLS without information from an IKE negotiation.

[Authors] Basically as we state in our text, the SDN paradigm generally =
assumes
 the Security Controller will have a view of the network it controls. =
Based on this, the Security Controller can know if there is a NAT =
configured between two hosts. For example, if you take a look to:
  =20
   https://tools.ietf.org/html/draft-ietf-opsawg-nat-yang-17 =
<https://tools.ietf.org/html/draft-ietf-opsawg-nat-yang-17>
  =20
   the Security Controller could use this netconf module with a gateway =
to collect NAT information or even configure a NAT.
  =20
   Regarding the usage of UDP, TCP or TLS, since it controls all the =
network it is something that the Security Controller should decide.
  =20
   In any case, if this NETCONF module is not available and the Security =
Controller cannot know if a host is behind a NAT or not, then IKE case =
should be the right one and not the IKE-less.


Best Regards.
-------------------------------------------------------
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>
-------------------------------------------------------





--Apple-Mail=_F82529B5-233B-4502-A774-9BB53D71F8EB
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"><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dutf-8"><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; -webkit-line-break: after-white-space;" =
class=3D"">Hi Paul,all:<div class=3D""><br class=3D""></div><div =
class=3D"">Here you can find our answers for section 5.<br class=3D""><div=
 class=3D""><br class=3D""><div class=3D""><blockquote type=3D"cite" =
class=3D""><div class=3D""><div class=3D"">Section 5.1:<br class=3D""><br =
class=3D"">The diagram lists:<br class=3D""><br class=3D""><span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</span>| =
&nbsp;&nbsp;IKE &nbsp;&nbsp;&nbsp;| =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;IPsec(SPD,PAD) &nbsp;|<br class=3D""><br =
class=3D"">Shouldn't that be:<br class=3D""><br class=3D""> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;| IKE(PAD) | IPsec(SPD, =
SAD)<br class=3D""><br class=3D"">IKE is using the PAD information to =
tell IPsec to establish SPDs and SADs) ?<br =
class=3D""></div></div></blockquote><div class=3D""><br =
class=3D""></div><div class=3D"">[Authors] The PAD is something defined =
in RFC 4301, which is independent of the key management =
protocol.</div><div class=3D""><br class=3D""></div><div class=3D"">=46rom=
 RFC 4301:</div><div class=3D"">"The entry specifies the authentication =
protocol</div><div class=3D"">&nbsp; &nbsp;(e.g., IKEv1, IKEv2, KINK) =
method"</div><div class=3D"">&nbsp; &nbsp;</div><div class=3D"">Therefore =
it is not something attached to the key management protocol itself but =
more related with IPsec implemenation. What it is true that PAD is not =
implemented in current Linux kernel and usually this information is set =
in the IKE implementation. Finally we have only described in Fig. 1 that =
SPD and PAD must be configured from the Controller. The SAD will be =
managed by the IKEv2 implementation. Same happens in Fig. 2.</div><div =
class=3D""><br class=3D""></div></div><div class=3D""><br =
class=3D""><blockquote type=3D"cite" class=3D""><div class=3D""><div =
class=3D""><br class=3D""><br class=3D"">Section 5.1.1:<br class=3D""><br =
class=3D"">What does this mean:<br class=3D""><br class=3D""><span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</span>Moreover, =
an east-west interface is required to exchange IPsec-related =
information.<br class=3D""></div></div></blockquote><div class=3D""><br =
class=3D""></div><div class=3D""><div class=3D""><div class=3D"">[Authors]=
 In SDN terminology an east-west interface is the communication =
interface between two controllers.</div><div class=3D""><br =
class=3D""></div><div class=3D"">For example: <a =
href=3D"https://tools.ietf.org/html/rfc7426" =
class=3D"">https://tools.ietf.org/html/rfc7426</a></div><div =
class=3D""><br class=3D""></div><div class=3D"">If we have two gateways =
where we need to establish an IPsec SA and both are under the control of =
two different controllers then both Security Controllers needs to =
exchange information so that they need to agree in some information so =
that the configure their own gateways properly (see Fig. 5). An example: =
they have to agree that IKEv2 authentication will be based on raw public =
keys or pre-shared keys. And if it pre-shared keys they will have to =
agree in the PSK (Yes, one option to explore is IKEv2, more related =
comments in posterior answers.)</div></div></div><blockquote type=3D"cite"=
 class=3D""><div class=3D""><div class=3D""><br class=3D"">Section =
5.2:<br class=3D""><br class=3D""> &nbsp;&nbsp;In this case, the NSF =
does not deploy IKEv2 and, therefore, the<br class=3D""> =
&nbsp;&nbsp;Security Controller has to perform the management of IPsec =
SAs by<br class=3D""> &nbsp;&nbsp;populating and monitoring the SPD and =
the SAD.<br class=3D""><br class=3D"">I would write:<br class=3D""><br =
class=3D"">In this case, the NSF does not deploy IKEv2 and, therefore, =
the<br class=3D"">Security Controller has to perform the IKE security =
functions and management<br class=3D"">of IPsec SAs by populating and =
managing the SPD and the SAD.<br class=3D""><br class=3D"">I added "IKE =
security functions" to make sure some entity is responsible<br =
class=3D"">for those items that are normally done by IKE (IV generation, =
prevent counter<br class=3D"">resets for same key, etc).<br class=3D""><br=
 class=3D"">I changed monitoring to managing, because I don't understand =
how it would "monitor"<br class=3D"">the NSF or what it would monitor. I =
assume also if during monitoring it finds<br class=3D"">something that =
needs changing (eg vpn tunnel up or down) that it will do so,<br =
class=3D"">so I think managing is the better word.<br =
class=3D""></div></div></blockquote><div class=3D""><br =
class=3D""></div>[Authors] Agreed with this text. Very reasonable.<br =
class=3D""><blockquote type=3D"cite" class=3D""><div class=3D""><div =
class=3D""><br class=3D"">For this diagram, I would say IPsec(SPD, SAD) =
would need to also list the IKE<br class=3D"">security function it needs =
to use in an IKE-less scenario, which above I had<br class=3D"">called =
"management of IPsec SAs=E2=80=9D</div></div></blockquote><div =
class=3D""><br class=3D""></div><div class=3D""><div =
class=3D"">[Authors]&nbsp;</div><div class=3D""><br class=3D""></div><div =
class=3D"">How about this non-exhaustive list:</div><div class=3D""><br =
class=3D""></div><div class=3D"">- IV generation</div><div class=3D"">- =
prevent counter resets for same key</div><div class=3D"">- Generation of =
pseudo-random cryptographic keys for the IPsec SAs</div><div class=3D"">- =
Rekey of the IPsec SAs based on notification from the NSF &nbsp;(i.e. =
expire)</div><div class=3D"">- Generation of the IPsec SAs when required =
based on notifications (i.e. sadb_acquire)</div><div class=3D"">- NAT =
Traversal discovery and management.&nbsp;</div><div class=3D"">- =
....</div><div class=3D""><br class=3D""></div><div class=3D""><br =
class=3D""></div><div class=3D"">What about the following =
(non-exhaustive) tasks?</div><div class=3D"">- SPI random =
generation</div><div class=3D"">- Cryptographic algorithm/s =
selection</div><div class=3D"">- Usage of extended sequence =
numbers</div><div class=3D"">- Establishment of proper traffic =
selectors&nbsp;</div><div class=3D"">- ....</div></div><blockquote =
type=3D"cite" class=3D""><div class=3D""><div class=3D""><br =
class=3D"">Section 5.3:<br class=3D""><br class=3D"">As mentioned =
before, a better title would be: IKE vs IKEless<br class=3D""><br =
class=3D"">I would also start this section with:<br class=3D""><br =
class=3D"">Case 1 is more secure, because all security features of IKE =
are used to manage<br class=3D"">the IPsec SAs.<br =
class=3D""></div></div></blockquote><div class=3D""><br =
class=3D""></div><div class=3D""><div class=3D"">[Authors] We do =
understand the comment.</div><div class=3D""><br class=3D""></div><div =
class=3D"">How about this new text:</div><div class=3D""><br =
class=3D""></div><div class=3D"">=E2=80=9CIKE case provides better =
security properties than IKE-less case. In particular, the Security =
Controller is not able to observe what are the cryptographic keys used =
to protect data traffic."</div><div class=3D""><br =
class=3D""></div></div><div class=3D""><br class=3D""></div><div =
class=3D""><br class=3D""></div><blockquote type=3D"cite" class=3D""><div =
class=3D""><div class=3D""><br class=3D"">Section 5.3.1:<br class=3D""><br=
 class=3D""> &nbsp;&nbsp;For case 1, the rekeying process is carried out =
by IKEv2, following<br class=3D""> &nbsp;&nbsp;the configuration defined =
in the SPD.<br class=3D""><br class=3D"">Technically this is the SPD and =
SAD, as the SPD would for example list the<br class=3D"">maximum number =
of packets allowed, but the SAD lists the number of packets<br =
class=3D"">that have happened.<br class=3D""></div></div></blockquote><div=
 class=3D""><br class=3D""></div><div class=3D"">[Authors] Ok. We will =
replace the text:&nbsp;</div><div class=3D""><br class=3D""></div><div =
class=3D"">s/"For case 1, the rekeying process is carried out by IKEv2, =
following the configuration defined in the SPD."/"For IKEv2 case, the =
rekeying process is carried out by IKEv2, following the configuration =
defined in the SPD and SAD."</div><blockquote type=3D"cite" =
class=3D""><div class=3D""><div class=3D""><br class=3D"">I am a bit =
confused by the rekey description. I guess it assumes that the<br =
class=3D"">Security Controller sending of information is blocking? Eg =
when it tells<br class=3D"">the node to install an inbound IPsec SA, it =
is blocked from doing anything<br class=3D"">else. If this is not the =
case, then the 3 step program should be clarified<br class=3D"">that it =
needs to also receive confirmations. And if this is a non-blocking<br =
class=3D"">process, who is responsible for "retransmits" of these =
confirmations ?<br class=3D"">The same applies to the blocking or =
time-wait between step 2 and 3.<br =
class=3D""></div></div></blockquote><div class=3D""><br =
class=3D""></div><div class=3D"">[Authors] Yes, the controller goes =
through this process in a blocking way per each step. That is, the =
Security Controller needs to finish correctly the step 1 before =
proceeding with step 2. This is possible since the Security Controller =
will receive a NETCONF rpc-reply with OK after installing the inbound in =
peer A and the same for peer B. When receiving both OKs, it can proceed =
to step 2. The same happens between step 2 and step 3.</div><div =
class=3D""><br class=3D""></div><div class=3D"">The reason of doing this =
in this way is to prepare first the new inbound IPsec SAs and everything =
is ready, then the new outbound IPsec SAs. When the new outbound IPsec =
SAs are set, we have observed (at least in Linux kernel) that the new =
outbound IPsec SA is immediately used. Since the other peer has already =
the corresponding inbound SA no traffic loss happens.</div><div =
class=3D""><br class=3D""></div><div class=3D"">However if we assume =
that some traffic loss is allowed, we could send inbound and outbound =
IPsec SAs in parallell to both nodes involved in the rekey. What do you =
think?</div><div class=3D""><br class=3D""></div><div class=3D"">Regarding=
 retransmission of the confirmation the NETCONF transport (SSH/TCP or =
TLS/TCP) will provide this.</div><blockquote type=3D"cite" class=3D""><div=
 class=3D""><div class=3D""><br class=3D"">Also, I would say step 3 can =
be get rid of if the IPsec implementation can<br class=3D"">itself =
detect traffic on the new IPsec SA and it can delete the old IPsec<br =
class=3D"">SA itself without instruction from the Security =
Controller.<br class=3D""></div></div></blockquote><div class=3D""><br =
class=3D""></div><div class=3D"">[Authors] Correct. We were wondering =
though how common this is (at least in linux kernels we have not seen =
this behaviour). Moreover, the Security Controller should know how this =
is implemented internally in the NSF to avoid sending this delete. =
Either that, or the NETCONF server in the NSF should pay attention to =
this by interacting with the kernel (through netlink=C2=BF?=C2=BF?) and =
remove it when it sees that traffic. I have seen that libreswan has a =
wishlist about this feature. Is there any movement in this =
side?</div></div><div class=3D""><blockquote type=3D"cite" class=3D""><div=
 class=3D""><div class=3D""><br class=3D"">Section 5.3.2:<br =
class=3D""><br class=3D""><span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</span>If one of the NSF restarts, it =
may lose part or all the IPsec state<br class=3D""><br class=3D"">This =
"may" suggests a very interesting case. I doubt the NSF would store =
on<br class=3D"">non-volatile memory the IPsec symmetric keys for =
encryption, and the counter<br class=3D"">or ICV's used. If it could =
store that, the document needs some text about<br class=3D"">this in the =
Security Considerations because it will allow for easier theft<br =
class=3D"">of session material.<br =
class=3D""></div></div></blockquote><div class=3D""><br =
class=3D""></div>[Authors] Yes, this "may" is unfortunate because our =
assumption is that all this information will be in volatile memory. More =
specifically, we assume that NSF does not have any information in the =
startup-config (non-volatile), only in the running-config datastore =
(volatile)<br class=3D""><blockquote type=3D"cite" class=3D""><div =
class=3D""><div class=3D""><br class=3D"">Rather, I suspect this may =
really is not true, and all of these devices would<br class=3D"">lose =
state?<br class=3D""></div></div></blockquote><div class=3D""><br =
class=3D""></div>[Authors] Correct. Although other aspects could be =
considered in the future (for example, is it reasonable to think that =
IKE configuration could be in non-volatile as well just in case the node =
falls?)<br class=3D""><blockquote type=3D"cite" class=3D""><div =
class=3D""><div class=3D""><br class=3D""><span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</span>In both cases, the Security =
Controller MUST be aware of the affected NSF<br class=3D""><br =
class=3D"">I think this MUST is a little misleading. It is not desired =
behaviour but just<br class=3D"">an observation - it cannot not know its =
TCP session died ? Perhaps write:<br class=3D""><br class=3D""><span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</span>In both =
cases, the Security Controller is aware of the affected NSF<br =
class=3D""></div></div></blockquote><div class=3D""><br =
class=3D""></div>[Authors] Yes, this is better.</div><div class=3D""><br =
class=3D""><blockquote type=3D"cite" class=3D""><div class=3D""><div =
class=3D""><br class=3D"">A similar case for the next sentence MUST =
keyword:<br class=3D""><br class=3D""><span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</span>Moreover, the Security Controller =
MUST have a register about all the<br class=3D""><span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</span>NSFs that =
have IPsec SAs with the affected NSF.<br class=3D""><br class=3D"">so =
write:<br class=3D""><br class=3D""><span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</span>Moreover, the Security Controller =
has a register about all the<br class=3D""><span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</span>NSFs that have IPsec SAs with the =
affected NSF.<br class=3D""></div></div></blockquote><div class=3D""><br =
class=3D""></div>[Authors] Agree.&nbsp;</div><div class=3D""><br =
class=3D""><blockquote type=3D"cite" class=3D""><div class=3D""><div =
class=3D""><br class=3D""><br class=3D""><span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</span>(It is TBD in the =
model).</div></div></blockquote><blockquote type=3D"cite" class=3D""><div =
class=3D""><div class=3D""><br class=3D"">This remark seems to need to =
be resolved before publication ?<br =
class=3D""></div></div></blockquote><div class=3D""><br =
class=3D""></div><div class=3D"">[Authors] It is already fixed but we =
missed to remove this text.</div><div class=3D""><br class=3D""></div><div=
 class=3D"">+--rw initial-contact? &nbsp; &nbsp; =
boolean</div><blockquote type=3D"cite" class=3D""><div class=3D""><div =
class=3D""><br class=3D""> &nbsp;&nbsp;In Case 2, if the Security =
Controller detects that a NSF has lost the<br class=3D""> =
&nbsp;&nbsp;IPsec SAs (e.g. it reboots) it will follow similar steps to =
rekey:<br class=3D""> &nbsp;&nbsp;the steps 1 and 2 remain equal but the =
step 3 will be slightly<br class=3D""> &nbsp;&nbsp;different. &nbsp;For =
example, if we assume that NSF B has lost its state,<br class=3D""> =
&nbsp;&nbsp;the Security Controller MUST only delete the old IPsec SAs =
from A in<br class=3D""> &nbsp;&nbsp;step 3.<br class=3D""><br =
class=3D"">I don't understand why this paragraph about NSF state loss =
seems to talk<br class=3D"">about "step 3" which can only be referring =
to the "rekeying process" of<br class=3D"">the previous section. It =
should only mention that it should configure new<br class=3D"">IPsec SAs =
between the failed node and all the nodes the failed node talked<br =
class=3D"">to and only after those are estlibhsed, it can send a delete =
for the old<br class=3D"">IPsec SAs on the non-failed nodes. This =
prevents the non-failed nodes from<br class=3D"">leaking plaintext.<br =
class=3D""></div></div></blockquote><div class=3D""><br =
class=3D""></div><div class=3D""><div class=3D"">[Authors] Agree. =
However I was thinking that failed node may not come to life =
again.</div><div class=3D"">In such a case, if a failed node falls, the =
active IPsec SAs in the rest of non-failed nodes with the failed node =
are not useful. Therefore, the SC could first delete the old IPsec SAs =
on the non-failed nodes. If the failed node comes to live, then the SC =
will install first the new inbound IPsec SAs and after these IPsec SAs =
are established then to install the outbound IPsec SAs. What do you =
think?</div><div class=3D""><br class=3D""></div><div class=3D"">Having =
said that, we propose to replace this paragraph with the following =
text:</div><div class=3D""><br class=3D""></div><div class=3D"">"In =
IKE-less case, if the Security Controller detects that a NSF has lost =
the IPsec SAs (e.g. it reboots) it will delete the old IPsec SAs of the =
non-failed nodes established with the failed node (step 1). This =
prevents the non-failed nodes from leaking plaintext. If the failed node =
come to live, the Security Controller will configure the new inbound =
IPsec SAs between the failed node and all the nodes the failed talked to =
(step 2). After these inbound IPsec SAs have been established, the =
Security Controller can configure the outbound IPsec SAs (step =
3)."</div></div><br class=3D""><blockquote type=3D"cite" class=3D""><div =
class=3D""><div class=3D""><br class=3D"">Section 5.3.3:<br class=3D""><br=
 class=3D"">I'm confused how the Security Controller can know what NAT =
ports to convey to<br class=3D"">the NSF agent. Without IKE traffic, =
there is no port NAT mapping? So unless<br class=3D"">the Security =
Controller _is_ the NAT gateway, it would never know this<br =
class=3D"">information? So I am skeptical if the NAT case can ever work =
without IKE.<br class=3D"">I also do not know how the Security =
Controller could decide between UDP,<br class=3D"">TCP or TLS without =
information from an IKE negotiation.<br =
class=3D""></div></div></blockquote><div class=3D""><br =
class=3D""></div><div class=3D""><div class=3D"">[Authors] Basically as =
we state in our text, the SDN paradigm generally assumes</div><div =
class=3D"">&nbsp;the Security Controller will have a view of the network =
it controls. Based on this, the Security Controller can know if there is =
a NAT configured between two hosts. For example, if you take a look =
to:</div><div class=3D"">&nbsp; &nbsp;</div><div class=3D"">&nbsp; =
&nbsp;<a =
href=3D"https://tools.ietf.org/html/draft-ietf-opsawg-nat-yang-17" =
class=3D"">https://tools.ietf.org/html/draft-ietf-opsawg-nat-yang-17</a></=
div><div class=3D"">&nbsp; &nbsp;</div><div class=3D"">&nbsp; &nbsp;the =
Security Controller could use this netconf module with a gateway to =
collect NAT information or even configure a NAT.</div><div =
class=3D"">&nbsp; &nbsp;</div><div class=3D"">&nbsp; &nbsp;Regarding the =
usage of UDP, TCP or TLS, since it controls all the network it is =
something that the Security Controller should decide.</div><div =
class=3D"">&nbsp; &nbsp;</div><div class=3D"">&nbsp; &nbsp;In any case, =
if this NETCONF module is not available and the Security Controller =
cannot know if a host is behind a NAT or not, then IKE case should be =
the right one and not the IKE-less.</div></div></div><div class=3D""><br =
class=3D""></div><div class=3D""><br class=3D""></div>Best Regards.<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;" =
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 =
e-mail:&nbsp;<a href=3D"mailto:rafa@um.es" class=3D"">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=_F82529B5-233B-4502-A774-9BB53D71F8EB--


From nobody Mon Dec  3 14:57:47 2018
Return-Path: <gabilm@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 E8640130DF9; Mon,  3 Dec 2018 14:57:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_PASS=-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 V0UHYURK3sMh; Mon,  3 Dec 2018 14:57:34 -0800 (PST)
Received: from xenon44.um.es (xenon44.um.es [IPv6:2001:720:1710:601::44]) by ietfa.amsl.com (Postfix) with ESMTP id 29145130DF5; Mon,  3 Dec 2018 14:57:33 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by xenon44.um.es (Postfix) with ESMTP id 7B83B1FF6A; Mon,  3 Dec 2018 23:57:31 +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 utaXewPMuhbm; Mon,  3 Dec 2018 23:57:31 +0100 (CET)
Received: from [192.168.1.12] (157.red-83-36-225.dynamicip.rima-tde.net [83.36.225.157]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: gabilm@um.es) by xenon44.um.es (Postfix) with ESMTPSA id D379A200B1; Mon,  3 Dec 2018 23:57:24 +0100 (CET)
From: Gabriel Lopez <gabilm@um.es>
Message-Id: <5ACB4EEB-6BB4-455C-B5DF-5C833E4A9072@um.es>
Content-Type: multipart/alternative; boundary="Apple-Mail=_18FCA7D5-4A20-491D-B0E6-3AE1029FBA50"
Mime-Version: 1.0 (Mac OS X Mail 12.1 \(3445.101.1\))
Date: Mon, 3 Dec 2018 23:50:33 +0100
In-Reply-To: <alpine.LRH.2.21.1811180149220.25604@bofh.nohats.ca>
Cc: Gabriel Lopez <gabilm@um.es>, Yoav Nir <ynir.ietf@gmail.com>, i2nsf@ietf.org, "ipsec@ietf.org WG" <ipsec@ietf.org>, Rafa Marin Lopez <rafa@um.es>
To: Paul Wouters <paul@nohats.ca>
References: <A881C135-9BF7-4E93-BB7A-75EB3D1FF605@gmail.com> <6839D47C-4074-486F-9350-8EB7B378036C@um.es> <DAE14995-8504-4134-B021-93D56A4994FB@gmail.com> <alpine.LRH.2.21.1811180149220.25604@bofh.nohats.ca>
X-Mailer: Apple Mail (2.3445.101.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2nsf/EXi9CzmogEm5R9pLHfdPWMnjoPI>
Subject: Re: [I2nsf] [IPsec] Review of draft-ietf-i2nsf-sdn-ipsec-flow-protection-03
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, 03 Dec 2018 22:57:38 -0000

--Apple-Mail=_18FCA7D5-4A20-491D-B0E6-3AE1029FBA50
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Hi Paul, all.

Answers for section 6 in line.

> El 18 nov 2018, a las 7:52, Paul Wouters <paul@nohats.ca> escribi=C3=B3:=

>=20
>=20
>=20
> Section 6.1:
>=20
> Note that the use of start and end addresses, means that this can =
never work
> with IKEv1, that can only negotiate CIDR networks. Perhaps this should =
be
> explicitely stated somewhere just in case some developer thinks they =
can
> use IKEv1 for this?

[Authors] ok, note that the yang element is explicitely named "IKEv2", =
anyway, we can clarify this point in the document. In fact, we believe =
that we should proceed with only IKEv2.

BTW, we propose to change the model moving from the current "list of TSs =
including a list of IP addresses and port ranges" for each policy  to a =
list of TSs per policy with one local and remote subnets per TS (instead =
of "ranges"). What do you think?


>=20
> I dont understand the names in:
>=20
> 	next-layer-protocol*   ipsec-next-layer-proto
>=20
> It talks about ip-address and not ipsec-next-layer-ip-address? =
Simiarly it
> talks about local-ports. So why not just call this proto or protocol ?

[Authors] The label "protocol" is widely used in the model. It is just a =
way to identify the context.

>=20
> Is selector-priority needed? Can the ts-number not be specified to be =
"lower
> numer is higher priority=E2=80=9D ?

[Authors] It could (in fact, it is ordered by user, which means the =
controller in our case)
In fact, RFC4301 only specifies that "An SPD is an ordered list of =
entries"


>=20
>=20
> Why do we have security-protocol? If you are considered about small =
footprints,
> clearly you would implement only ESP and use ESP-NULL if encryption is =
not
> needed. And simply not implement AH (which is already optional not =
mandatory
> to implement for IPsec). Also, this assumes IPCOMP, which has its own =
complexity,
> would also not be used. I think a case for AH would be very weak, =
while a case
> for IPCOMP could be made. I'd recommend only supporting ESP, at which =
point
> you would not need this parameter, or you could keep it for =
completeness
> sake even though it could only have one value "esp". This would also =
allow
> an updated ESP or some ESPlite to be used in the future if such a =
thing would
> be developed.

[Authors] We agree with only make use of  ESP and ESP-NULL.

> If we only go with AEAD algorithms, then the whole ah-algorithms part =
can be
> removed too. And esp-algorithms could be changed to only contain =
esp-encryption
> (or could be renamed aead-algorithm)

[Authors] Same as before

>=20
> I see spd-mark but not spd-security-context  (see my Labeled IPsec =
draft)


[Authors]

Regarding the XFRM mark element and the security context described in =
the draft, if there is a clear use case for these elements we can keep =
them in the model.

>=20
> I found the names in lifetimes confusing. "added" really means maxlife =
and
> "current" really means maxidle I think? So I think the names would be
> clearer as "time", "idle", "packets", "bytes". I think the time and =
idle
> units of uint64 could be narrowed down if the yang language allows =
some
> kind of timestamp type.

[Authors] We have made use of the terminology in RFC2367, Section 2.3.2. =
Indeed the yang model has a timestamp (RFC 6991). We can add "time", =
"idle", "packets" and "bytes=E2=80=9D.

>=20
> I am missing an entry for TFC (confidentiality, padding)

ok, It could be included in the model (for IKE and IKE-less cases.


> I also see no entry for IPCOMP algorithm. But I am fine with not =
allowing
> IPCOMP at all :)

[Authors] Agree

>=20
> I am missing replay window parameters ?


Currently, the replay-window parameter is defined only in the SAD =
configuration for IKE-less case. It should be also included in the SPD =
configuration for IKE case.

Do you think we should include the additional replay-seq, replay-oseq, =
replay-seq-hi, replay-oseq-hi parameters for IKE-less case?

>=20
> I don't know what statefulfragCheck is ?


Whether or not to allow IKE fragmentation. (Libreswan/Strongwan support =
that, valid values are are yes, (the default), no or force).

Probably a better name for this?

>=20
> Section 6.2
>=20
> See Section 6.1 comments.
>=20
> Why are the encap entries in 6.2 and not 6.1 ?

[Authors] For case 2 (IKE-less) espencap is configured like part of the =
SA, not the policy. For IKE case encap is part of the IKEv2 =
configuration (section 6.4)

>=20
> What is the "state?" entry ?

[Authors] state is of type sa-state (Larval, Mature, Dying, Dead).
These states can be useful when the model is used by the SC to recover =
SA's state data from the node or when modelling the sadb_expire message

>=20
> Why is rpcs: only here?


[Authors] You are right, rpcs should be in a 6.5 section. Note that =
notifications are defined for SAD and SPD in IKE-less case and that =
there are not notifications for IKE and PAD models

>=20
> I would not use minbits, maxbits. All modern ciphers, especially AEAD, =
are fixed key sizes. Make it a list of key sizes

[Authors]
Agree

>=20
> I seem to miss the AEAD IV values ?


[Authors] This container represents information about the algorithm =
supported, we assume that AEAD algorithms can be also represented here =
(AES_GCM, AES_CCM, CHACHA20-POLY1305, ....). IV values are not =
represented here.

> Possibly the truncation values ?

[Authors] For auth-trunc values, we will include that in container ah-sa =
unless AH is finally removed.

>=20
> Section 6.3:
>=20
> I only see PSK and RSA algorithms? No ECDSA via RFC 7427 Digital =
Signatures?
> (no PAKE, we have two IKE PAKE's although it looks like we want an =
CFRG new one)

[Authors]
See answer in Appendix section.

>=20
> Should PSK be of type "string". Some people want to hex entry? =
Although those are often written
> as strings with a 0x prefix.


[Authors]
Agree

>=20
> I see some CRL entries, but no OCSP entries. Is it expected those =
URI's are stored within the certificates,
> and the received OCSP responses will never be communicated through =
this interface?

[Authors]
Agree. We can add CRL and OCSP URLs

>=20
> I see no local and remote part, meaning that only symmetric =
authentication methods can be used. IKEv2 supports
> asymmetric authentication methods as well. Especially when using EAP =
and sometimes with AUTHHNULL, this method
> is very asymmetric. So I believe this entry needs to be split in a =
local/remote auth method.

[Authors]
Agree

>=20
> Section 6.4:
>=20
> type-autostartup issues...
>=20
> typedef type-autostartup {
>      type enumeration {
>         enum ALWAYSON { description " ";}
>         enum INITIATE-ON-DEMAND {description " ";}
>         enum RESPOND-ONLY {description " ";}
>      }
>      description "Different types of how IKEv2 starts the IPsec SAs";
>=20
> With libreswan we have similar keywords, and run into some interesting =
issues. We found what is really needed is to
> know the current state and the connection desired state. for example, =
when using ondemand and the connection is up,
> it is important to know it is up because of ondemand. So that when you =
receive a Delete request, you can go back
> to ondemand state. If you dont keep this state then you cannot tell =
the difference between alwayson/ondemand if
> the connection is "up". Similarly, we had issues where connections has =
a definition like above, but the administrator
> performs an action. It is unclear if such an action is considered a =
temporary override or basically a runtime update
> of the configuration. So lets say we are in respondonly, and the =
administrator brings the connection up. Now the other
> end sends a delete. Do you assume you are in alwayson state or in =
ondemand state? And if you believe alwayson, be
> prepared for a war with the remote endpoint that keeps sending deletes =
because it wants to be down.

[Authors] Do you think this is something the model should consider? We =
mean that, after all, behing the model we will have an implementation =
(could be libreswan, strongswan etc.. that it will deal with these =
aspects) It is true that we should define clearly what ALWAYSON, =
INITIATE-ON-DEMAND, RESPOND-ONLY, etc=E2=80=A6

>=20
>=20
> Why is there nat-traversal and espencap. Why not just have espencap =
allow to have a value of 'none=E2=80=99 ?


[Authors]
Agree

> IKEv2 allows more then one oaddr  (eg multiple SOURCE NAT IPs) but the =
value is not a list?

[Authors]
Agree for the IKE case.
For pfkey_v2 (setkey), it does not allow to specify oaddr.
For xfrm, it does allow to specify only one oaddr.
Does make it sense to allow more than one oaddr for IKE-less case?

>=20
> The terms phase1-* should be called ike-* or ike-sa-* as phase1/phase2 =
is IKEv1 terminalogy not used for IKEv2.

[Authors]
Agree. We can replace phase1-* by ike-sa-* and phase2-* by =
ike-child-sa-*.

>=20
> Why is combined-enc-intr needed? These are stored with the encalg =
entries anyway.


[Authors]
Agree.

>=20
> I see:
>=20
> 	+--rw local
>        |   +--rw (my-identifier-type)?
>=20
> 	+--rw remote
>        |   +--rw (my-identifier-type)?
>=20
> I think "my-identifier-type" should be "identifier-type". Talking =
about "my" for the remote peer is very confusing.

[Authors]
Agree.

>=20
> my-identifier-type does not support the value ID_NONE from RFC 7619

[Authors]
Agree. We will include that in the model.

>=20
> Why is there no secion for ike-lifetime-{soft|hard} ? We also have =
FIPS requirements that IKE SA's cannot do more
> then X bytes for Y algorithm. And also bringing down idle IKE SA's =
etc.

[Authors]
We can include a soft/hard lifetime (seconds) for IKE SA. What does it =
means a soft/hard lifetime (bytes) for IKE SA. It is implemented in =
current distributions?

>=20
> I think "added", "used", "bytes" "packets" should be called lifetime, =
idletime, maxbytes and maxpackets

[Authors]
See comment above.

>=20
> The timestamp values "added" and "used" could have a better type than =
uint64, eg unix epoch of unixtime or something?

[Authors]
Current implementations make use of __u64 or even uint32_t. Anyway, we =
can modify the type. What do you propose?

>=20
> the term ike-stats was confusing me. I thought at first these were the =
global IKE statistics, like how many tunnels
> are up, how many errors received, but it turned out to be the state of =
a singe IKE SA. So perhaps ike-sa-state is a
> better term?

[Authors]
Agree.

> IKE state I expect things like SPIi and SPIr as listed here.

[Authors]
global IKE statictics could be obtained by the SC through the =
ike-sa-state info for each IKE SA.

>=20
> I am not sure why there are three nat-* bools instead of one value =
representing the nat-state? Possibly because we
> use a number of bits to indicate which of the NAT properties are set, =
and you don't do this kind of bit mapping in
> yang?
>=20

[Authors] That could be represented with uint8 and using three bits , is =
that what you mean? We thought was clearer to have three booleans.

> I dont see an entry for "latest IKE SA". We have that in libreswan. =
You can have multiple IKE SA's when rekeying,
> and the older one is just lingering to die. Any operations such as =
informational requests, dpd/liveness probes
> should only be done with the "latest IKE SA".  However, this is kind =
of a state on the IKE node, so I am not
> sure if this belongs in the yang model or not.

[Authors] Is there any scenario where the SC is able to deal with this =
information for the IKE case? If so, we can try to model that like state =
data.=20

>=20
> I see a total SA's and halfopen SA's but I don't see anything related =
to anti-DDOS cookies. Eg the number of half
> open SA's before enabling cookies. Perhaps add =
half-open-cookies-treshhold ?
>=20

[Authors]
Several parameters can be configured here:
- half-open-threshold: number of half open IKE SAs
- half-open-cookies-threshold: number of half open IKE SAs with cookie =
activated
- half-open-timer: timeout in seconds for connecting IKE SAs.

Best regards, Gabi.

>=20

-----------------------------------------------------------
Gabriel L=C3=B3pez Mill=C3=A1n
Departamento de Ingenier=C3=ADa de la Informaci=C3=B3n y las =
Comunicaciones
University of Murcia
Spain
Tel: +34 868888504
Fax: +34 868884151
email: gabilm@um.es


--Apple-Mail=_18FCA7D5-4A20-491D-B0E6-3AE1029FBA50
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 Paul, all.<div =
class=3D""><br class=3D""></div><div class=3D"">Answers for section 6 in =
line.<br class=3D""><div><br class=3D""><blockquote type=3D"cite" =
class=3D""><div class=3D"">El 18 nov 2018, a las 7:52, Paul Wouters =
&lt;<a href=3D"mailto:paul@nohats.ca" class=3D"">paul@nohats.ca</a>&gt; =
escribi=C3=B3:</div><br class=3D"Apple-interchange-newline"><div =
class=3D""><div class=3D""><br class=3D""><br class=3D"">Section 6.1:<br =
class=3D""><br class=3D"">Note that the use of start and end addresses, =
means that this can never work<br class=3D"">with IKEv1, that can only =
negotiate CIDR networks. Perhaps this should be<br class=3D"">explicitely =
stated somewhere just in case some developer thinks they can<br =
class=3D"">use IKEv1 for this?<br =
class=3D""></div></div></blockquote><div><br class=3D""></div><div>






<!--[if gte mso 9]><xml>
 <o:OfficeDocumentSettings>
  <o:AllowPNG/>
 </o:OfficeDocumentSettings>
</xml><![endif]-->

<!--[if gte mso 9]><xml>
 <w:WordDocument>
  <w:View>Normal</w:View>
  <w:Zoom>0</w:Zoom>
  <w:TrackMoves/>
  <w:TrackFormatting/>
  <w:HyphenationZone>21</w:HyphenationZone>
  <w:PunctuationKerning/>
  <w:ValidateAgainstSchemas/>
  <w:SaveIfXMLInvalid>false</w:SaveIfXMLInvalid>
  <w:IgnoreMixedContent>false</w:IgnoreMixedContent>
  <w:AlwaysShowPlaceholderText>false</w:AlwaysShowPlaceholderText>
  <w:DoNotPromoteQF/>
  <w:LidThemeOther>ES</w:LidThemeOther>
  <w:LidThemeAsian>X-NONE</w:LidThemeAsian>
  <w:LidThemeComplexScript>X-NONE</w:LidThemeComplexScript>
  <w:Compatibility>
   <w:BreakWrappedTables/>
   <w:SnapToGridInCell/>
   <w:WrapTextWithPunct/>
   <w:UseAsianBreakRules/>
   <w:DontGrowAutofit/>
   <w:SplitPgBreakAndParaMark/>
   <w:EnableOpenTypeKerning/>
   <w:DontFlipMirrorIndents/>
   <w:OverrideTableStyleHps/>
  </w:Compatibility>
  <m:mathPr>
   <m:mathFont m:val=3D"Cambria Math"/>
   <m:brkBin m:val=3D"before"/>
   <m:brkBinSub m:val=3D"&#45;-"/>
   <m:smallFrac m:val=3D"off"/>
   <m:dispDef/>
   <m:lMargin m:val=3D"0"/>
   <m:rMargin m:val=3D"0"/>
   <m:defJc m:val=3D"centerGroup"/>
   <m:wrapIndent m:val=3D"1440"/>
   <m:intLim m:val=3D"subSup"/>
   <m:naryLim m:val=3D"undOvr"/>
  </m:mathPr></w:WordDocument>
</xml><![endif]--><!--[if gte mso 9]><xml>
 <w:LatentStyles DefLockedState=3D"false" DefUnhideWhenUsed=3D"false"
  DefSemiHidden=3D"false" DefQFormat=3D"false" DefPriority=3D"99"
  LatentStyleCount=3D"382">
  <w:LsdException Locked=3D"false" Priority=3D"0" QFormat=3D"true" =
Name=3D"Normal"/>
  <w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"9" SemiHidden=3D"true"
   UnhideWhenUsed=3D"true" QFormat=3D"true" Name=3D"heading 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"9" SemiHidden=3D"true"
   UnhideWhenUsed=3D"true" QFormat=3D"true" Name=3D"heading 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"9" SemiHidden=3D"true"
   UnhideWhenUsed=3D"true" QFormat=3D"true" Name=3D"heading 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"9" SemiHidden=3D"true"
   UnhideWhenUsed=3D"true" QFormat=3D"true" Name=3D"heading 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"9" SemiHidden=3D"true"
   UnhideWhenUsed=3D"true" QFormat=3D"true" Name=3D"heading 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"9" SemiHidden=3D"true"
   UnhideWhenUsed=3D"true" QFormat=3D"true" Name=3D"heading 7"/>
  <w:LsdException Locked=3D"false" Priority=3D"9" SemiHidden=3D"true"
   UnhideWhenUsed=3D"true" QFormat=3D"true" Name=3D"heading 8"/>
  <w:LsdException Locked=3D"false" Priority=3D"9" SemiHidden=3D"true"
   UnhideWhenUsed=3D"true" QFormat=3D"true" Name=3D"heading 9"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"index 1"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"index 2"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"index 3"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"index 4"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"index 5"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"index 6"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"index 7"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"index 8"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"index 9"/>
  <w:LsdException Locked=3D"false" Priority=3D"39" SemiHidden=3D"true"
   UnhideWhenUsed=3D"true" Name=3D"toc 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"39" SemiHidden=3D"true"
   UnhideWhenUsed=3D"true" Name=3D"toc 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"39" SemiHidden=3D"true"
   UnhideWhenUsed=3D"true" Name=3D"toc 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"39" SemiHidden=3D"true"
   UnhideWhenUsed=3D"true" Name=3D"toc 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"39" SemiHidden=3D"true"
   UnhideWhenUsed=3D"true" Name=3D"toc 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"39" SemiHidden=3D"true"
   UnhideWhenUsed=3D"true" Name=3D"toc 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"39" SemiHidden=3D"true"
   UnhideWhenUsed=3D"true" Name=3D"toc 7"/>
  <w:LsdException Locked=3D"false" Priority=3D"39" SemiHidden=3D"true"
   UnhideWhenUsed=3D"true" Name=3D"toc 8"/>
  <w:LsdException Locked=3D"false" Priority=3D"39" SemiHidden=3D"true"
   UnhideWhenUsed=3D"true" Name=3D"toc 9"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"Normal Indent"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"footnote text"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"annotation text"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"header"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"footer"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"index heading"/>
  <w:LsdException Locked=3D"false" Priority=3D"35" SemiHidden=3D"true"
   UnhideWhenUsed=3D"true" QFormat=3D"true" Name=3D"caption"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"table of figures"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"envelope address"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"envelope return"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"footnote reference"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"annotation reference"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"line number"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"page number"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"endnote reference"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"endnote text"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"table of authorities"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"macro"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"toa heading"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"List"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"List Bullet"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"List Number"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"List 2"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"List 3"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"List 4"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"List 5"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"List Bullet 2"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"List Bullet 3"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"List Bullet 4"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"List Bullet 5"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"List Number 2"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"List Number 3"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"List Number 4"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"List Number 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"10" QFormat=3D"true" =
Name=3D"Title"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"Closing"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"Signature"/>
  <w:LsdException Locked=3D"false" Priority=3D"1" SemiHidden=3D"true"
   UnhideWhenUsed=3D"true" Name=3D"Default Paragraph Font"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"Body Text"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"Body Text Indent"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"List Continue"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"List Continue 2"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"List Continue 3"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"List Continue 4"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"List Continue 5"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"Message Header"/>
  <w:LsdException Locked=3D"false" Priority=3D"11" QFormat=3D"true" =
Name=3D"Subtitle"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"Salutation"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"Date"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"Body Text First Indent"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"Body Text First Indent 2"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"Note Heading"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"Body Text 2"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"Body Text 3"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"Body Text Indent 2"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"Body Text Indent 3"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"Block Text"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"Hyperlink"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"FollowedHyperlink"/>
  <w:LsdException Locked=3D"false" Priority=3D"22" QFormat=3D"true" =
Name=3D"Strong"/>
  <w:LsdException Locked=3D"false" Priority=3D"20" QFormat=3D"true" =
Name=3D"Emphasis"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"Document Map"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"Plain Text"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"E-mail Signature"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"HTML Top of Form"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"HTML Bottom of Form"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"Normal (Web)"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"HTML Acronym"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"HTML Address"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"HTML Cite"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"HTML Code"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"HTML Definition"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"HTML Keyboard"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"HTML Preformatted"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"HTML Sample"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"HTML Typewriter"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"HTML Variable"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"Normal Table"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"annotation subject"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"No List"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"Outline List 1"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"Outline List 2"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"Outline List 3"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"Table Simple 1"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"Table Simple 2"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"Table Simple 3"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"Table Classic 1"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"Table Classic 2"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"Table Classic 3"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"Table Classic 4"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"Table Colorful 1"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"Table Colorful 2"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"Table Colorful 3"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"Table Columns 1"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"Table Columns 2"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"Table Columns 3"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"Table Columns 4"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"Table Columns 5"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"Table Grid 1"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"Table Grid 2"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"Table Grid 3"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"Table Grid 4"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"Table Grid 5"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"Table Grid 6"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"Table Grid 7"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"Table Grid 8"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"Table List 1"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"Table List 2"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"Table List 3"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"Table List 4"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"Table List 5"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"Table List 6"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"Table List 7"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"Table List 8"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"Table 3D effects 1"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"Table 3D effects 2"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"Table 3D effects 3"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"Table Contemporary"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"Table Elegant"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"Table Professional"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"Table Subtle 1"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"Table Subtle 2"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"Table Web 1"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"Table Web 2"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"Table Web 3"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"Balloon Text"/>
  <w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"Table Grid"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"Table Theme"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"Note Level 1"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"Note Level 2"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"Note Level 3"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"Note Level 4"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"Note Level 5"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"Note Level 6"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"Note Level 7"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"Note Level 8"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"Note Level 9"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" Name=3D"Placeholder=
 Text"/>
  <w:LsdException Locked=3D"false" Priority=3D"1" QFormat=3D"true" =
Name=3D"No Spacing"/>
  <w:LsdException Locked=3D"false" Priority=3D"60" Name=3D"Light =
Shading"/>
  <w:LsdException Locked=3D"false" Priority=3D"61" Name=3D"Light List"/>
  <w:LsdException Locked=3D"false" Priority=3D"62" Name=3D"Light Grid"/>
  <w:LsdException Locked=3D"false" Priority=3D"63" Name=3D"Medium =
Shading 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"64" Name=3D"Medium =
Shading 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"65" Name=3D"Medium List =
1"/>
  <w:LsdException Locked=3D"false" Priority=3D"66" Name=3D"Medium List =
2"/>
  <w:LsdException Locked=3D"false" Priority=3D"67" Name=3D"Medium Grid =
1"/>
  <w:LsdException Locked=3D"false" Priority=3D"68" Name=3D"Medium Grid =
2"/>
  <w:LsdException Locked=3D"false" Priority=3D"69" Name=3D"Medium Grid =
3"/>
  <w:LsdException Locked=3D"false" Priority=3D"70" Name=3D"Dark List"/>
  <w:LsdException Locked=3D"false" Priority=3D"71" Name=3D"Colorful =
Shading"/>
  <w:LsdException Locked=3D"false" Priority=3D"72" Name=3D"Colorful =
List"/>
  <w:LsdException Locked=3D"false" Priority=3D"73" Name=3D"Colorful =
Grid"/>
  <w:LsdException Locked=3D"false" Priority=3D"60" Name=3D"Light Shading =
Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"61" Name=3D"Light List =
Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"62" Name=3D"Light Grid =
Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"63" Name=3D"Medium =
Shading 1 Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"64" Name=3D"Medium =
Shading 2 Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"65" Name=3D"Medium List 1 =
Accent 1"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" Name=3D"Revision"/>=

  <w:LsdException Locked=3D"false" Priority=3D"34" QFormat=3D"true"
   Name=3D"List Paragraph"/>
  <w:LsdException Locked=3D"false" Priority=3D"29" QFormat=3D"true" =
Name=3D"Quote"/>
  <w:LsdException Locked=3D"false" Priority=3D"30" QFormat=3D"true"
   Name=3D"Intense Quote"/>
  <w:LsdException Locked=3D"false" Priority=3D"66" Name=3D"Medium List 2 =
Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"67" Name=3D"Medium Grid 1 =
Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"68" Name=3D"Medium Grid 2 =
Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"69" Name=3D"Medium Grid 3 =
Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"70" Name=3D"Dark List =
Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"71" Name=3D"Colorful =
Shading Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"72" Name=3D"Colorful List =
Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"73" Name=3D"Colorful Grid =
Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"60" Name=3D"Light Shading =
Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"61" Name=3D"Light List =
Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"62" Name=3D"Light Grid =
Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"63" Name=3D"Medium =
Shading 1 Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"64" Name=3D"Medium =
Shading 2 Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"65" Name=3D"Medium List 1 =
Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"66" Name=3D"Medium List 2 =
Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"67" Name=3D"Medium Grid 1 =
Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"68" Name=3D"Medium Grid 2 =
Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"69" Name=3D"Medium Grid 3 =
Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"70" Name=3D"Dark List =
Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"71" Name=3D"Colorful =
Shading Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"72" Name=3D"Colorful List =
Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"73" Name=3D"Colorful Grid =
Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"60" Name=3D"Light Shading =
Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"61" Name=3D"Light List =
Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"62" Name=3D"Light Grid =
Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"63" Name=3D"Medium =
Shading 1 Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"64" Name=3D"Medium =
Shading 2 Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"65" Name=3D"Medium List 1 =
Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"66" Name=3D"Medium List 2 =
Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"67" Name=3D"Medium Grid 1 =
Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"68" Name=3D"Medium Grid 2 =
Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"69" Name=3D"Medium Grid 3 =
Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"70" Name=3D"Dark List =
Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"71" Name=3D"Colorful =
Shading Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"72" Name=3D"Colorful List =
Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"73" Name=3D"Colorful Grid =
Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"60" Name=3D"Light Shading =
Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"61" Name=3D"Light List =
Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"62" Name=3D"Light Grid =
Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"63" Name=3D"Medium =
Shading 1 Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"64" Name=3D"Medium =
Shading 2 Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"65" Name=3D"Medium List 1 =
Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"66" Name=3D"Medium List 2 =
Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"67" Name=3D"Medium Grid 1 =
Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"68" Name=3D"Medium Grid 2 =
Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"69" Name=3D"Medium Grid 3 =
Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"70" Name=3D"Dark List =
Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"71" Name=3D"Colorful =
Shading Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"72" Name=3D"Colorful List =
Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"73" Name=3D"Colorful Grid =
Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"60" Name=3D"Light Shading =
Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"61" Name=3D"Light List =
Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"62" Name=3D"Light Grid =
Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"63" Name=3D"Medium =
Shading 1 Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"64" Name=3D"Medium =
Shading 2 Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"65" Name=3D"Medium List 1 =
Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"66" Name=3D"Medium List 2 =
Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"67" Name=3D"Medium Grid 1 =
Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"68" Name=3D"Medium Grid 2 =
Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"69" Name=3D"Medium Grid 3 =
Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"70" Name=3D"Dark List =
Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"71" Name=3D"Colorful =
Shading Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"72" Name=3D"Colorful List =
Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"73" Name=3D"Colorful Grid =
Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"60" Name=3D"Light Shading =
Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"61" Name=3D"Light List =
Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"62" Name=3D"Light Grid =
Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"63" Name=3D"Medium =
Shading 1 Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"64" Name=3D"Medium =
Shading 2 Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"65" Name=3D"Medium List 1 =
Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"66" Name=3D"Medium List 2 =
Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"67" Name=3D"Medium Grid 1 =
Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"68" Name=3D"Medium Grid 2 =
Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"69" Name=3D"Medium Grid 3 =
Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"70" Name=3D"Dark List =
Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"71" Name=3D"Colorful =
Shading Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"72" Name=3D"Colorful List =
Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"73" Name=3D"Colorful Grid =
Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"19" QFormat=3D"true"
   Name=3D"Subtle Emphasis"/>
  <w:LsdException Locked=3D"false" Priority=3D"21" QFormat=3D"true"
   Name=3D"Intense Emphasis"/>
  <w:LsdException Locked=3D"false" Priority=3D"31" QFormat=3D"true"
   Name=3D"Subtle Reference"/>
  <w:LsdException Locked=3D"false" Priority=3D"32" QFormat=3D"true"
   Name=3D"Intense Reference"/>
  <w:LsdException Locked=3D"false" Priority=3D"33" QFormat=3D"true" =
Name=3D"Book Title"/>
  <w:LsdException Locked=3D"false" Priority=3D"37" SemiHidden=3D"true"
   UnhideWhenUsed=3D"true" Name=3D"Bibliography"/>
  <w:LsdException Locked=3D"false" Priority=3D"39" SemiHidden=3D"true"
   UnhideWhenUsed=3D"true" QFormat=3D"true" Name=3D"TOC Heading"/>
  <w:LsdException Locked=3D"false" Priority=3D"41" Name=3D"Plain Table =
1"/>
  <w:LsdException Locked=3D"false" Priority=3D"42" Name=3D"Plain Table =
2"/>
  <w:LsdException Locked=3D"false" Priority=3D"43" Name=3D"Plain Table =
3"/>
  <w:LsdException Locked=3D"false" Priority=3D"44" Name=3D"Plain Table =
4"/>
  <w:LsdException Locked=3D"false" Priority=3D"45" Name=3D"Plain Table =
5"/>
  <w:LsdException Locked=3D"false" Priority=3D"40" Name=3D"Grid Table =
Light"/>
  <w:LsdException Locked=3D"false" Priority=3D"46" Name=3D"Grid Table 1 =
Light"/>
  <w:LsdException Locked=3D"false" Priority=3D"47" Name=3D"Grid Table =
2"/>
  <w:LsdException Locked=3D"false" Priority=3D"48" Name=3D"Grid Table =
3"/>
  <w:LsdException Locked=3D"false" Priority=3D"49" Name=3D"Grid Table =
4"/>
  <w:LsdException Locked=3D"false" Priority=3D"50" Name=3D"Grid Table 5 =
Dark"/>
  <w:LsdException Locked=3D"false" Priority=3D"51" Name=3D"Grid Table 6 =
Colorful"/>
  <w:LsdException Locked=3D"false" Priority=3D"52" Name=3D"Grid Table 7 =
Colorful"/>
  <w:LsdException Locked=3D"false" Priority=3D"46"
   Name=3D"Grid Table 1 Light Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"47" Name=3D"Grid Table 2 =
Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"48" Name=3D"Grid Table 3 =
Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"49" Name=3D"Grid Table 4 =
Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"50" Name=3D"Grid Table 5 =
Dark Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"51"
   Name=3D"Grid Table 6 Colorful Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"52"
   Name=3D"Grid Table 7 Colorful Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"46"
   Name=3D"Grid Table 1 Light Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"47" Name=3D"Grid Table 2 =
Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"48" Name=3D"Grid Table 3 =
Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"49" Name=3D"Grid Table 4 =
Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"50" Name=3D"Grid Table 5 =
Dark Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"51"
   Name=3D"Grid Table 6 Colorful Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"52"
   Name=3D"Grid Table 7 Colorful Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"46"
   Name=3D"Grid Table 1 Light Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"47" Name=3D"Grid Table 2 =
Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"48" Name=3D"Grid Table 3 =
Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"49" Name=3D"Grid Table 4 =
Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"50" Name=3D"Grid Table 5 =
Dark Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"51"
   Name=3D"Grid Table 6 Colorful Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"52"
   Name=3D"Grid Table 7 Colorful Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"46"
   Name=3D"Grid Table 1 Light Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"47" Name=3D"Grid Table 2 =
Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"48" Name=3D"Grid Table 3 =
Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"49" Name=3D"Grid Table 4 =
Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"50" Name=3D"Grid Table 5 =
Dark Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"51"
   Name=3D"Grid Table 6 Colorful Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"52"
   Name=3D"Grid Table 7 Colorful Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"46"
   Name=3D"Grid Table 1 Light Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"47" Name=3D"Grid Table 2 =
Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"48" Name=3D"Grid Table 3 =
Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"49" Name=3D"Grid Table 4 =
Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"50" Name=3D"Grid Table 5 =
Dark Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"51"
   Name=3D"Grid Table 6 Colorful Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"52"
   Name=3D"Grid Table 7 Colorful Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"46"
   Name=3D"Grid Table 1 Light Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"47" Name=3D"Grid Table 2 =
Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"48" Name=3D"Grid Table 3 =
Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"49" Name=3D"Grid Table 4 =
Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"50" Name=3D"Grid Table 5 =
Dark Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"51"
   Name=3D"Grid Table 6 Colorful Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"52"
   Name=3D"Grid Table 7 Colorful Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"46" Name=3D"List Table 1 =
Light"/>
  <w:LsdException Locked=3D"false" Priority=3D"47" Name=3D"List Table =
2"/>
  <w:LsdException Locked=3D"false" Priority=3D"48" Name=3D"List Table =
3"/>
  <w:LsdException Locked=3D"false" Priority=3D"49" Name=3D"List Table =
4"/>
  <w:LsdException Locked=3D"false" Priority=3D"50" Name=3D"List Table 5 =
Dark"/>
  <w:LsdException Locked=3D"false" Priority=3D"51" Name=3D"List Table 6 =
Colorful"/>
  <w:LsdException Locked=3D"false" Priority=3D"52" Name=3D"List Table 7 =
Colorful"/>
  <w:LsdException Locked=3D"false" Priority=3D"46"
   Name=3D"List Table 1 Light Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"47" Name=3D"List Table 2 =
Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"48" Name=3D"List Table 3 =
Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"49" Name=3D"List Table 4 =
Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"50" Name=3D"List Table 5 =
Dark Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"51"
   Name=3D"List Table 6 Colorful Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"52"
   Name=3D"List Table 7 Colorful Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"46"
   Name=3D"List Table 1 Light Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"47" Name=3D"List Table 2 =
Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"48" Name=3D"List Table 3 =
Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"49" Name=3D"List Table 4 =
Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"50" Name=3D"List Table 5 =
Dark Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"51"
   Name=3D"List Table 6 Colorful Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"52"
   Name=3D"List Table 7 Colorful Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"46"
   Name=3D"List Table 1 Light Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"47" Name=3D"List Table 2 =
Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"48" Name=3D"List Table 3 =
Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"49" Name=3D"List Table 4 =
Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"50" Name=3D"List Table 5 =
Dark Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"51"
   Name=3D"List Table 6 Colorful Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"52"
   Name=3D"List Table 7 Colorful Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"46"
   Name=3D"List Table 1 Light Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"47" Name=3D"List Table 2 =
Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"48" Name=3D"List Table 3 =
Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"49" Name=3D"List Table 4 =
Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"50" Name=3D"List Table 5 =
Dark Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"51"
   Name=3D"List Table 6 Colorful Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"52"
   Name=3D"List Table 7 Colorful Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"46"
   Name=3D"List Table 1 Light Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"47" Name=3D"List Table 2 =
Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"48" Name=3D"List Table 3 =
Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"49" Name=3D"List Table 4 =
Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"50" Name=3D"List Table 5 =
Dark Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"51"
   Name=3D"List Table 6 Colorful Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"52"
   Name=3D"List Table 7 Colorful Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"46"
   Name=3D"List Table 1 Light Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"47" Name=3D"List Table 2 =
Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"48" Name=3D"List Table 3 =
Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"49" Name=3D"List Table 4 =
Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"50" Name=3D"List Table 5 =
Dark Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"51"
   Name=3D"List Table 6 Colorful Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"52"
   Name=3D"List Table 7 Colorful Accent 6"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"Mention"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"Smart Hyperlink"/>
 </w:LatentStyles>
</xml><![endif]-->

<!--[if gte mso 10]>
<style>
 /* Style Definitions */
table.MsoNormalTable
	{mso-style-name:"Tabla normal";
	mso-tstyle-rowband-size:0;
	mso-tstyle-colband-size:0;
	mso-style-noshow:yes;
	mso-style-priority:99;
	mso-style-parent:"";
	mso-padding-alt:0cm 5.4pt 0cm 5.4pt;
	mso-para-margin-top:0cm;
	mso-para-margin-right:0cm;
	mso-para-margin-bottom:8.0pt;
	mso-para-margin-left:0cm;
	line-height:107%;
	mso-pagination:widow-orphan;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;
	mso-ascii-font-family:Calibri;
	mso-ascii-theme-font:minor-latin;
	mso-hansi-font-family:Calibri;
	mso-hansi-theme-font:minor-latin;
	mso-ansi-language:ES;
	mso-fareast-language:EN-US;}
</style>
<![endif]-->



<!--StartFragment--><p class=3D"MsoPlainText"><span lang=3D"EN-US" =
style=3D"font-family:&quot;Courier New&quot;,serif;
mso-ansi-language:EN-US" class=3D"">[Authors] ok, note that the yang =
element is
explicitely named "IKEv2", anyway, we can clarify this point in the
document. In fact, we believe that we should proceed with only =
IKEv2.<o:p class=3D""></o:p></span></p><p class=3D"MsoPlainText"><span =
lang=3D"EN-US" style=3D"font-family:&quot;Courier New&quot;,serif;
mso-ansi-language:EN-US" class=3D"">BTW, we propose to change the model =
moving from the
current "list of TSs including a list of IP addresses and port
ranges" for each policy&nbsp; to a list
of TSs per policy with one local and remote subnets per TS (instead of
"ranges"). What do you think?<o:p class=3D""></o:p></span></p>

<!--EndFragment--></div><br class=3D""><blockquote type=3D"cite" =
class=3D""><div class=3D""><div class=3D""><br class=3D"">I dont =
understand the names in:<br class=3D""><br class=3D""><span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</span>next-layer-protocol* &nbsp;&nbsp;ipsec-next-layer-proto<br =
class=3D""><br class=3D"">It talks about ip-address and not =
ipsec-next-layer-ip-address? Simiarly it<br class=3D"">talks about =
local-ports. So why not just call this proto or protocol ?<br =
class=3D""></div></div></blockquote><div><br class=3D""></div><div><span =
style=3D"font-family: &quot;Courier New&quot;, serif;" =
class=3D"">[Authors] The label "protocol" is widely&nbsp;used in the =
model. It is just a way to identify the context.</span></div><br =
class=3D""><blockquote type=3D"cite" class=3D""><div class=3D""><div =
class=3D""><br class=3D"">Is selector-priority needed? Can the ts-number =
not be specified to be "lower<br class=3D"">numer is higher priority=E2=80=
=9D ?<br class=3D""></div></div></blockquote><div><br class=3D""></div>






<!--[if gte mso 9]><xml>
 <o:OfficeDocumentSettings>
  <o:AllowPNG/>
 </o:OfficeDocumentSettings>
</xml><![endif]-->

<!--[if gte mso 9]><xml>
 <w:WordDocument>
  <w:View>Normal</w:View>
  <w:Zoom>0</w:Zoom>
  <w:TrackMoves/>
  <w:TrackFormatting/>
  <w:HyphenationZone>21</w:HyphenationZone>
  <w:PunctuationKerning/>
  <w:ValidateAgainstSchemas/>
  <w:SaveIfXMLInvalid>false</w:SaveIfXMLInvalid>
  <w:IgnoreMixedContent>false</w:IgnoreMixedContent>
  <w:AlwaysShowPlaceholderText>false</w:AlwaysShowPlaceholderText>
  <w:DoNotPromoteQF/>
  <w:LidThemeOther>ES</w:LidThemeOther>
  <w:LidThemeAsian>X-NONE</w:LidThemeAsian>
  <w:LidThemeComplexScript>X-NONE</w:LidThemeComplexScript>
  <w:Compatibility>
   <w:BreakWrappedTables/>
   <w:SnapToGridInCell/>
   <w:WrapTextWithPunct/>
   <w:UseAsianBreakRules/>
   <w:DontGrowAutofit/>
   <w:SplitPgBreakAndParaMark/>
   <w:EnableOpenTypeKerning/>
   <w:DontFlipMirrorIndents/>
   <w:OverrideTableStyleHps/>
  </w:Compatibility>
  <m:mathPr>
   <m:mathFont m:val=3D"Cambria Math"/>
   <m:brkBin m:val=3D"before"/>
   <m:brkBinSub m:val=3D"&#45;-"/>
   <m:smallFrac m:val=3D"off"/>
   <m:dispDef/>
   <m:lMargin m:val=3D"0"/>
   <m:rMargin m:val=3D"0"/>
   <m:defJc m:val=3D"centerGroup"/>
   <m:wrapIndent m:val=3D"1440"/>
   <m:intLim m:val=3D"subSup"/>
   <m:naryLim m:val=3D"undOvr"/>
  </m:mathPr></w:WordDocument>
</xml><![endif]--><!--[if gte mso 9]><xml>
 <w:LatentStyles DefLockedState=3D"false" DefUnhideWhenUsed=3D"false"
  DefSemiHidden=3D"false" DefQFormat=3D"false" DefPriority=3D"99"
  LatentStyleCount=3D"382">
  <w:LsdException Locked=3D"false" Priority=3D"0" QFormat=3D"true" =
Name=3D"Normal"/>
  <w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"9" SemiHidden=3D"true"
   UnhideWhenUsed=3D"true" QFormat=3D"true" Name=3D"heading 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"9" SemiHidden=3D"true"
   UnhideWhenUsed=3D"true" QFormat=3D"true" Name=3D"heading 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"9" SemiHidden=3D"true"
   UnhideWhenUsed=3D"true" QFormat=3D"true" Name=3D"heading 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"9" SemiHidden=3D"true"
   UnhideWhenUsed=3D"true" QFormat=3D"true" Name=3D"heading 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"9" SemiHidden=3D"true"
   UnhideWhenUsed=3D"true" QFormat=3D"true" Name=3D"heading 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"9" SemiHidden=3D"true"
   UnhideWhenUsed=3D"true" QFormat=3D"true" Name=3D"heading 7"/>
  <w:LsdException Locked=3D"false" Priority=3D"9" SemiHidden=3D"true"
   UnhideWhenUsed=3D"true" QFormat=3D"true" Name=3D"heading 8"/>
  <w:LsdException Locked=3D"false" Priority=3D"9" SemiHidden=3D"true"
   UnhideWhenUsed=3D"true" QFormat=3D"true" Name=3D"heading 9"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"index 1"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"index 2"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"index 3"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"index 4"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"index 5"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"index 6"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"index 7"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"index 8"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"index 9"/>
  <w:LsdException Locked=3D"false" Priority=3D"39" SemiHidden=3D"true"
   UnhideWhenUsed=3D"true" Name=3D"toc 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"39" SemiHidden=3D"true"
   UnhideWhenUsed=3D"true" Name=3D"toc 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"39" SemiHidden=3D"true"
   UnhideWhenUsed=3D"true" Name=3D"toc 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"39" SemiHidden=3D"true"
   UnhideWhenUsed=3D"true" Name=3D"toc 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"39" SemiHidden=3D"true"
   UnhideWhenUsed=3D"true" Name=3D"toc 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"39" SemiHidden=3D"true"
   UnhideWhenUsed=3D"true" Name=3D"toc 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"39" SemiHidden=3D"true"
   UnhideWhenUsed=3D"true" Name=3D"toc 7"/>
  <w:LsdException Locked=3D"false" Priority=3D"39" SemiHidden=3D"true"
   UnhideWhenUsed=3D"true" Name=3D"toc 8"/>
  <w:LsdException Locked=3D"false" Priority=3D"39" SemiHidden=3D"true"
   UnhideWhenUsed=3D"true" Name=3D"toc 9"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"Normal Indent"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"footnote text"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"annotation text"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"header"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"footer"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"index heading"/>
  <w:LsdException Locked=3D"false" Priority=3D"35" SemiHidden=3D"true"
   UnhideWhenUsed=3D"true" QFormat=3D"true" Name=3D"caption"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"table of figures"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"envelope address"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"envelope return"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"footnote reference"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"annotation reference"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"line number"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"page number"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"endnote reference"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"endnote text"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"table of authorities"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"macro"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"toa heading"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"List"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"List Bullet"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"List Number"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"List 2"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"List 3"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"List 4"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"List 5"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"List Bullet 2"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"List Bullet 3"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"List Bullet 4"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"List Bullet 5"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"List Number 2"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"List Number 3"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"List Number 4"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"List Number 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"10" QFormat=3D"true" =
Name=3D"Title"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"Closing"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"Signature"/>
  <w:LsdException Locked=3D"false" Priority=3D"1" SemiHidden=3D"true"
   UnhideWhenUsed=3D"true" Name=3D"Default Paragraph Font"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"Body Text"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"Body Text Indent"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"List Continue"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"List Continue 2"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"List Continue 3"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"List Continue 4"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"List Continue 5"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"Message Header"/>
  <w:LsdException Locked=3D"false" Priority=3D"11" QFormat=3D"true" =
Name=3D"Subtitle"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"Salutation"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"Date"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"Body Text First Indent"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"Body Text First Indent 2"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"Note Heading"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"Body Text 2"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"Body Text 3"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"Body Text Indent 2"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"Body Text Indent 3"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"Block Text"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"Hyperlink"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"FollowedHyperlink"/>
  <w:LsdException Locked=3D"false" Priority=3D"22" QFormat=3D"true" =
Name=3D"Strong"/>
  <w:LsdException Locked=3D"false" Priority=3D"20" QFormat=3D"true" =
Name=3D"Emphasis"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"Document Map"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"Plain Text"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"E-mail Signature"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"HTML Top of Form"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"HTML Bottom of Form"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"Normal (Web)"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"HTML Acronym"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"HTML Address"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"HTML Cite"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"HTML Code"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"HTML Definition"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"HTML Keyboard"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"HTML Preformatted"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"HTML Sample"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"HTML Typewriter"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"HTML Variable"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"Normal Table"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"annotation subject"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"No List"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"Outline List 1"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"Outline List 2"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"Outline List 3"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"Table Simple 1"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"Table Simple 2"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"Table Simple 3"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"Table Classic 1"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"Table Classic 2"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"Table Classic 3"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"Table Classic 4"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"Table Colorful 1"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"Table Colorful 2"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"Table Colorful 3"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"Table Columns 1"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"Table Columns 2"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"Table Columns 3"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"Table Columns 4"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"Table Columns 5"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"Table Grid 1"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"Table Grid 2"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"Table Grid 3"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"Table Grid 4"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"Table Grid 5"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"Table Grid 6"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"Table Grid 7"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"Table Grid 8"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"Table List 1"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"Table List 2"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"Table List 3"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"Table List 4"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"Table List 5"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"Table List 6"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"Table List 7"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"Table List 8"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"Table 3D effects 1"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"Table 3D effects 2"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"Table 3D effects 3"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"Table Contemporary"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"Table Elegant"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"Table Professional"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"Table Subtle 1"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"Table Subtle 2"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"Table Web 1"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"Table Web 2"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"Table Web 3"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"Balloon Text"/>
  <w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"Table Grid"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"Table Theme"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"Note Level 1"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"Note Level 2"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"Note Level 3"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"Note Level 4"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"Note Level 5"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"Note Level 6"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"Note Level 7"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"Note Level 8"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"Note Level 9"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" Name=3D"Placeholder=
 Text"/>
  <w:LsdException Locked=3D"false" Priority=3D"1" QFormat=3D"true" =
Name=3D"No Spacing"/>
  <w:LsdException Locked=3D"false" Priority=3D"60" Name=3D"Light =
Shading"/>
  <w:LsdException Locked=3D"false" Priority=3D"61" Name=3D"Light List"/>
  <w:LsdException Locked=3D"false" Priority=3D"62" Name=3D"Light Grid"/>
  <w:LsdException Locked=3D"false" Priority=3D"63" Name=3D"Medium =
Shading 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"64" Name=3D"Medium =
Shading 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"65" Name=3D"Medium List =
1"/>
  <w:LsdException Locked=3D"false" Priority=3D"66" Name=3D"Medium List =
2"/>
  <w:LsdException Locked=3D"false" Priority=3D"67" Name=3D"Medium Grid =
1"/>
  <w:LsdException Locked=3D"false" Priority=3D"68" Name=3D"Medium Grid =
2"/>
  <w:LsdException Locked=3D"false" Priority=3D"69" Name=3D"Medium Grid =
3"/>
  <w:LsdException Locked=3D"false" Priority=3D"70" Name=3D"Dark List"/>
  <w:LsdException Locked=3D"false" Priority=3D"71" Name=3D"Colorful =
Shading"/>
  <w:LsdException Locked=3D"false" Priority=3D"72" Name=3D"Colorful =
List"/>
  <w:LsdException Locked=3D"false" Priority=3D"73" Name=3D"Colorful =
Grid"/>
  <w:LsdException Locked=3D"false" Priority=3D"60" Name=3D"Light Shading =
Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"61" Name=3D"Light List =
Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"62" Name=3D"Light Grid =
Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"63" Name=3D"Medium =
Shading 1 Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"64" Name=3D"Medium =
Shading 2 Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"65" Name=3D"Medium List 1 =
Accent 1"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" Name=3D"Revision"/>=

  <w:LsdException Locked=3D"false" Priority=3D"34" QFormat=3D"true"
   Name=3D"List Paragraph"/>
  <w:LsdException Locked=3D"false" Priority=3D"29" QFormat=3D"true" =
Name=3D"Quote"/>
  <w:LsdException Locked=3D"false" Priority=3D"30" QFormat=3D"true"
   Name=3D"Intense Quote"/>
  <w:LsdException Locked=3D"false" Priority=3D"66" Name=3D"Medium List 2 =
Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"67" Name=3D"Medium Grid 1 =
Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"68" Name=3D"Medium Grid 2 =
Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"69" Name=3D"Medium Grid 3 =
Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"70" Name=3D"Dark List =
Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"71" Name=3D"Colorful =
Shading Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"72" Name=3D"Colorful List =
Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"73" Name=3D"Colorful Grid =
Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"60" Name=3D"Light Shading =
Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"61" Name=3D"Light List =
Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"62" Name=3D"Light Grid =
Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"63" Name=3D"Medium =
Shading 1 Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"64" Name=3D"Medium =
Shading 2 Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"65" Name=3D"Medium List 1 =
Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"66" Name=3D"Medium List 2 =
Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"67" Name=3D"Medium Grid 1 =
Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"68" Name=3D"Medium Grid 2 =
Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"69" Name=3D"Medium Grid 3 =
Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"70" Name=3D"Dark List =
Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"71" Name=3D"Colorful =
Shading Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"72" Name=3D"Colorful List =
Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"73" Name=3D"Colorful Grid =
Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"60" Name=3D"Light Shading =
Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"61" Name=3D"Light List =
Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"62" Name=3D"Light Grid =
Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"63" Name=3D"Medium =
Shading 1 Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"64" Name=3D"Medium =
Shading 2 Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"65" Name=3D"Medium List 1 =
Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"66" Name=3D"Medium List 2 =
Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"67" Name=3D"Medium Grid 1 =
Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"68" Name=3D"Medium Grid 2 =
Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"69" Name=3D"Medium Grid 3 =
Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"70" Name=3D"Dark List =
Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"71" Name=3D"Colorful =
Shading Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"72" Name=3D"Colorful List =
Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"73" Name=3D"Colorful Grid =
Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"60" Name=3D"Light Shading =
Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"61" Name=3D"Light List =
Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"62" Name=3D"Light Grid =
Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"63" Name=3D"Medium =
Shading 1 Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"64" Name=3D"Medium =
Shading 2 Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"65" Name=3D"Medium List 1 =
Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"66" Name=3D"Medium List 2 =
Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"67" Name=3D"Medium Grid 1 =
Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"68" Name=3D"Medium Grid 2 =
Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"69" Name=3D"Medium Grid 3 =
Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"70" Name=3D"Dark List =
Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"71" Name=3D"Colorful =
Shading Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"72" Name=3D"Colorful List =
Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"73" Name=3D"Colorful Grid =
Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"60" Name=3D"Light Shading =
Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"61" Name=3D"Light List =
Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"62" Name=3D"Light Grid =
Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"63" Name=3D"Medium =
Shading 1 Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"64" Name=3D"Medium =
Shading 2 Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"65" Name=3D"Medium List 1 =
Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"66" Name=3D"Medium List 2 =
Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"67" Name=3D"Medium Grid 1 =
Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"68" Name=3D"Medium Grid 2 =
Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"69" Name=3D"Medium Grid 3 =
Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"70" Name=3D"Dark List =
Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"71" Name=3D"Colorful =
Shading Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"72" Name=3D"Colorful List =
Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"73" Name=3D"Colorful Grid =
Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"60" Name=3D"Light Shading =
Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"61" Name=3D"Light List =
Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"62" Name=3D"Light Grid =
Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"63" Name=3D"Medium =
Shading 1 Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"64" Name=3D"Medium =
Shading 2 Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"65" Name=3D"Medium List 1 =
Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"66" Name=3D"Medium List 2 =
Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"67" Name=3D"Medium Grid 1 =
Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"68" Name=3D"Medium Grid 2 =
Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"69" Name=3D"Medium Grid 3 =
Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"70" Name=3D"Dark List =
Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"71" Name=3D"Colorful =
Shading Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"72" Name=3D"Colorful List =
Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"73" Name=3D"Colorful Grid =
Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"19" QFormat=3D"true"
   Name=3D"Subtle Emphasis"/>
  <w:LsdException Locked=3D"false" Priority=3D"21" QFormat=3D"true"
   Name=3D"Intense Emphasis"/>
  <w:LsdException Locked=3D"false" Priority=3D"31" QFormat=3D"true"
   Name=3D"Subtle Reference"/>
  <w:LsdException Locked=3D"false" Priority=3D"32" QFormat=3D"true"
   Name=3D"Intense Reference"/>
  <w:LsdException Locked=3D"false" Priority=3D"33" QFormat=3D"true" =
Name=3D"Book Title"/>
  <w:LsdException Locked=3D"false" Priority=3D"37" SemiHidden=3D"true"
   UnhideWhenUsed=3D"true" Name=3D"Bibliography"/>
  <w:LsdException Locked=3D"false" Priority=3D"39" SemiHidden=3D"true"
   UnhideWhenUsed=3D"true" QFormat=3D"true" Name=3D"TOC Heading"/>
  <w:LsdException Locked=3D"false" Priority=3D"41" Name=3D"Plain Table =
1"/>
  <w:LsdException Locked=3D"false" Priority=3D"42" Name=3D"Plain Table =
2"/>
  <w:LsdException Locked=3D"false" Priority=3D"43" Name=3D"Plain Table =
3"/>
  <w:LsdException Locked=3D"false" Priority=3D"44" Name=3D"Plain Table =
4"/>
  <w:LsdException Locked=3D"false" Priority=3D"45" Name=3D"Plain Table =
5"/>
  <w:LsdException Locked=3D"false" Priority=3D"40" Name=3D"Grid Table =
Light"/>
  <w:LsdException Locked=3D"false" Priority=3D"46" Name=3D"Grid Table 1 =
Light"/>
  <w:LsdException Locked=3D"false" Priority=3D"47" Name=3D"Grid Table =
2"/>
  <w:LsdException Locked=3D"false" Priority=3D"48" Name=3D"Grid Table =
3"/>
  <w:LsdException Locked=3D"false" Priority=3D"49" Name=3D"Grid Table =
4"/>
  <w:LsdException Locked=3D"false" Priority=3D"50" Name=3D"Grid Table 5 =
Dark"/>
  <w:LsdException Locked=3D"false" Priority=3D"51" Name=3D"Grid Table 6 =
Colorful"/>
  <w:LsdException Locked=3D"false" Priority=3D"52" Name=3D"Grid Table 7 =
Colorful"/>
  <w:LsdException Locked=3D"false" Priority=3D"46"
   Name=3D"Grid Table 1 Light Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"47" Name=3D"Grid Table 2 =
Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"48" Name=3D"Grid Table 3 =
Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"49" Name=3D"Grid Table 4 =
Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"50" Name=3D"Grid Table 5 =
Dark Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"51"
   Name=3D"Grid Table 6 Colorful Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"52"
   Name=3D"Grid Table 7 Colorful Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"46"
   Name=3D"Grid Table 1 Light Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"47" Name=3D"Grid Table 2 =
Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"48" Name=3D"Grid Table 3 =
Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"49" Name=3D"Grid Table 4 =
Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"50" Name=3D"Grid Table 5 =
Dark Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"51"
   Name=3D"Grid Table 6 Colorful Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"52"
   Name=3D"Grid Table 7 Colorful Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"46"
   Name=3D"Grid Table 1 Light Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"47" Name=3D"Grid Table 2 =
Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"48" Name=3D"Grid Table 3 =
Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"49" Name=3D"Grid Table 4 =
Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"50" Name=3D"Grid Table 5 =
Dark Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"51"
   Name=3D"Grid Table 6 Colorful Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"52"
   Name=3D"Grid Table 7 Colorful Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"46"
   Name=3D"Grid Table 1 Light Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"47" Name=3D"Grid Table 2 =
Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"48" Name=3D"Grid Table 3 =
Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"49" Name=3D"Grid Table 4 =
Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"50" Name=3D"Grid Table 5 =
Dark Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"51"
   Name=3D"Grid Table 6 Colorful Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"52"
   Name=3D"Grid Table 7 Colorful Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"46"
   Name=3D"Grid Table 1 Light Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"47" Name=3D"Grid Table 2 =
Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"48" Name=3D"Grid Table 3 =
Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"49" Name=3D"Grid Table 4 =
Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"50" Name=3D"Grid Table 5 =
Dark Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"51"
   Name=3D"Grid Table 6 Colorful Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"52"
   Name=3D"Grid Table 7 Colorful Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"46"
   Name=3D"Grid Table 1 Light Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"47" Name=3D"Grid Table 2 =
Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"48" Name=3D"Grid Table 3 =
Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"49" Name=3D"Grid Table 4 =
Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"50" Name=3D"Grid Table 5 =
Dark Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"51"
   Name=3D"Grid Table 6 Colorful Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"52"
   Name=3D"Grid Table 7 Colorful Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"46" Name=3D"List Table 1 =
Light"/>
  <w:LsdException Locked=3D"false" Priority=3D"47" Name=3D"List Table =
2"/>
  <w:LsdException Locked=3D"false" Priority=3D"48" Name=3D"List Table =
3"/>
  <w:LsdException Locked=3D"false" Priority=3D"49" Name=3D"List Table =
4"/>
  <w:LsdException Locked=3D"false" Priority=3D"50" Name=3D"List Table 5 =
Dark"/>
  <w:LsdException Locked=3D"false" Priority=3D"51" Name=3D"List Table 6 =
Colorful"/>
  <w:LsdException Locked=3D"false" Priority=3D"52" Name=3D"List Table 7 =
Colorful"/>
  <w:LsdException Locked=3D"false" Priority=3D"46"
   Name=3D"List Table 1 Light Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"47" Name=3D"List Table 2 =
Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"48" Name=3D"List Table 3 =
Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"49" Name=3D"List Table 4 =
Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"50" Name=3D"List Table 5 =
Dark Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"51"
   Name=3D"List Table 6 Colorful Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"52"
   Name=3D"List Table 7 Colorful Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"46"
   Name=3D"List Table 1 Light Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"47" Name=3D"List Table 2 =
Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"48" Name=3D"List Table 3 =
Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"49" Name=3D"List Table 4 =
Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"50" Name=3D"List Table 5 =
Dark Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"51"
   Name=3D"List Table 6 Colorful Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"52"
   Name=3D"List Table 7 Colorful Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"46"
   Name=3D"List Table 1 Light Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"47" Name=3D"List Table 2 =
Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"48" Name=3D"List Table 3 =
Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"49" Name=3D"List Table 4 =
Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"50" Name=3D"List Table 5 =
Dark Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"51"
   Name=3D"List Table 6 Colorful Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"52"
   Name=3D"List Table 7 Colorful Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"46"
   Name=3D"List Table 1 Light Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"47" Name=3D"List Table 2 =
Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"48" Name=3D"List Table 3 =
Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"49" Name=3D"List Table 4 =
Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"50" Name=3D"List Table 5 =
Dark Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"51"
   Name=3D"List Table 6 Colorful Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"52"
   Name=3D"List Table 7 Colorful Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"46"
   Name=3D"List Table 1 Light Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"47" Name=3D"List Table 2 =
Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"48" Name=3D"List Table 3 =
Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"49" Name=3D"List Table 4 =
Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"50" Name=3D"List Table 5 =
Dark Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"51"
   Name=3D"List Table 6 Colorful Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"52"
   Name=3D"List Table 7 Colorful Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"46"
   Name=3D"List Table 1 Light Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"47" Name=3D"List Table 2 =
Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"48" Name=3D"List Table 3 =
Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"49" Name=3D"List Table 4 =
Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"50" Name=3D"List Table 5 =
Dark Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"51"
   Name=3D"List Table 6 Colorful Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"52"
   Name=3D"List Table 7 Colorful Accent 6"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"Mention"/>
  <w:LsdException Locked=3D"false" SemiHidden=3D"true" =
UnhideWhenUsed=3D"true"
   Name=3D"Smart Hyperlink"/>
 </w:LatentStyles>
</xml><![endif]-->

<!--[if gte mso 10]>
<style>
 /* Style Definitions */
table.MsoNormalTable
	{mso-style-name:"Tabla normal";
	mso-tstyle-rowband-size:0;
	mso-tstyle-colband-size:0;
	mso-style-noshow:yes;
	mso-style-priority:99;
	mso-style-parent:"";
	mso-padding-alt:0cm 5.4pt 0cm 5.4pt;
	mso-para-margin-top:0cm;
	mso-para-margin-right:0cm;
	mso-para-margin-bottom:8.0pt;
	mso-para-margin-left:0cm;
	line-height:107%;
	mso-pagination:widow-orphan;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;
	mso-ascii-font-family:Calibri;
	mso-ascii-theme-font:minor-latin;
	mso-hansi-font-family:Calibri;
	mso-hansi-theme-font:minor-latin;
	mso-ansi-language:ES;
	mso-fareast-language:EN-US;}
</style>
<![endif]-->



<!--StartFragment--><p class=3D"MsoPlainText"><font face=3D"Courier New, =
serif" class=3D"">[Authors] It could (in fact, it is ordered by =
user,&nbsp;which means the controller in our case)<br class=3D"">In =
fact, RFC4301 only specifies that "An SPD is&nbsp;an ordered list of =
entries"</font></p>

<!--EndFragment--><br class=3D""><blockquote type=3D"cite" class=3D""><div=
 class=3D""><div class=3D""><br class=3D""><br class=3D"">Why do we have =
security-protocol? If you are considered about small footprints,<br =
class=3D"">clearly you would implement only ESP and use ESP-NULL if =
encryption is not<br class=3D"">needed. And simply not implement AH =
(which is already optional not mandatory<br class=3D"">to implement for =
IPsec). Also, this assumes IPCOMP, which has its own complexity,<br =
class=3D"">would also not be used. I think a case for AH would be very =
weak, while a case<br class=3D"">for IPCOMP could be made. I'd recommend =
only supporting ESP, at which point<br class=3D"">you would not need =
this parameter, or you could keep it for completeness<br class=3D"">sake =
even though it could only have one value "esp". This would also allow<br =
class=3D"">an updated ESP or some ESPlite to be used in the future if =
such a thing would<br class=3D"">be =
developed.</div></div></blockquote><div><br =
class=3D""></div><div>[Authors]&nbsp;We agree with only make use of =
&nbsp;ESP and ESP-NULL.</div><br class=3D""><blockquote type=3D"cite" =
class=3D""><div class=3D""><div class=3D"">If we only go with AEAD =
algorithms, then the whole ah-algorithms part can be<br class=3D"">removed=
 too. And esp-algorithms could be changed to only contain =
esp-encryption<br class=3D"">(or could be renamed aead-algorithm)<br =
class=3D""></div></div></blockquote><div><br class=3D""></div>[Authors] =
Same as before</div><div><br class=3D""><blockquote type=3D"cite" =
class=3D""><div class=3D""><div class=3D""><br class=3D"">I see spd-mark =
but not spd-security-context &nbsp;(see my Labeled IPsec draft)<br =
class=3D""></div></div></blockquote><div><br class=3D""></div><div><br =
class=3D""></div>[Authors]<br class=3D""><br class=3D"">Regarding the =
XFRM mark element and the security&nbsp;context described in the draft, =
if there is a clear use case&nbsp;for these elements&nbsp;we can keep =
them in the model.</div><div><br class=3D""><blockquote type=3D"cite" =
class=3D""><div class=3D""><div class=3D""><br class=3D"">I found the =
names in lifetimes confusing. "added" really means maxlife and<br =
class=3D"">"current" really means maxidle I think? So I think the names =
would be<br class=3D"">clearer as "time", "idle", "packets", "bytes". I =
think the time and idle<br class=3D"">units of uint64 could be narrowed =
down if the yang language allows some<br class=3D"">kind of timestamp =
type.<br class=3D""></div></div></blockquote><div><br =
class=3D""></div>[Authors] We have made use of the terminology =
in&nbsp;RFC2367, Section 2.3.2. Indeed the yang model has =
a&nbsp;timestamp (RFC 6991). We&nbsp;can add "time", "idle", "packets" =
and&nbsp;"bytes=E2=80=9D.</div><div><br class=3D""><blockquote =
type=3D"cite" class=3D""><div class=3D""><div class=3D""><br class=3D"">I =
am missing an entry for TFC (confidentiality, padding)<br =
class=3D""></div></div></blockquote><div><br class=3D""></div><div><p =
class=3D"MsoPlainText">ok, It could be included in the model (for IKE =
and IKE-less cases.</p>

<!--EndFragment--></div><br class=3D""><blockquote type=3D"cite" =
class=3D""><div class=3D""><div class=3D"">I also see no entry for =
IPCOMP algorithm. But I am fine with not allowing<br class=3D"">IPCOMP =
at all :)<br class=3D""></div></div></blockquote><div><br =
class=3D""></div>[Authors] Agree</div><div><br class=3D""><blockquote =
type=3D"cite" class=3D""><div class=3D""><div class=3D""><br class=3D"">I =
am missing replay window parameters ?<br =
class=3D""></div></div></blockquote><div><br class=3D""></div><div><br =
class=3D""></div><div>Currently, the replay-window parameter is defined =
only&nbsp;in the SAD configuration for IKE-less case. It should&nbsp;be =
also included in the&nbsp;SPD configuration for IKE case.<br =
class=3D""><br class=3D"">Do you think we should include the =
additional&nbsp;replay-seq, replay-oseq, replay-seq-hi, =
replay-oseq-hi&nbsp;parameters for IKE-less&nbsp;case?</div><br =
class=3D""><blockquote type=3D"cite" class=3D""><div class=3D""><div =
class=3D""><br class=3D"">I don't know what statefulfragCheck is ?<br =
class=3D""></div></div></blockquote><div><br class=3D""></div><div><br =
class=3D"">Whether or not to allow IKE fragmentation. =
(Libreswan/Strongwan support that, valid&nbsp;values are are yes, (the =
default), no or force).</div><div><br class=3D"">Probably a better name =
for this?</div><br class=3D""><blockquote type=3D"cite" class=3D""><div =
class=3D""><div class=3D""><br class=3D"">Section 6.2<br class=3D""><br =
class=3D"">See Section 6.1 comments.<br class=3D""><br class=3D"">Why =
are the encap entries in 6.2 and not 6.1 ?<br =
class=3D""></div></div></blockquote><div><br class=3D""></div>[Authors] =
For case 2 (IKE-less) espencap is configured&nbsp;like part of the SA, =
not the policy. For IKE case&nbsp;encap is part of the =
IKEv2&nbsp;configuration (section 6.4)</div><div><br =
class=3D""><blockquote type=3D"cite" class=3D""><div class=3D""><div =
class=3D""><br class=3D"">What is the "state?" entry ?<br =
class=3D""></div></div></blockquote><div><br =
class=3D""></div><div>[Authors] state is of type sa-state (Larval, =
Mature,&nbsp;Dying, Dead).<br class=3D"">These states can be useful when =
the model is used by&nbsp;the SC to recover SA's state data from the =
node or when&nbsp;modelling the sadb_expire&nbsp;message</div><br =
class=3D""><blockquote type=3D"cite" class=3D""><div class=3D""><div =
class=3D""><br class=3D"">Why is rpcs: only here?<br =
class=3D""></div></div></blockquote><div><br class=3D""></div><div><br =
class=3D""></div>[Authors] You are right, rpcs should be in a =
6.5&nbsp;section. Note that notifications are defined for SAD and =
SPD&nbsp;in IKE-less case&nbsp;and that there are not notifications for =
IKE and PAD models</div><div><br class=3D""><blockquote type=3D"cite" =
class=3D""><div class=3D""><div class=3D""><br class=3D"">I would not =
use minbits, maxbits. All modern ciphers, especially AEAD, are fixed key =
sizes. Make it a list of key sizes<br =
class=3D""></div></div></blockquote><div><br class=3D""></div>[Authors]<br=
 class=3D"">Agree</div><div><br class=3D""><blockquote type=3D"cite" =
class=3D""><div class=3D""><div class=3D""><br class=3D"">I seem to miss =
the AEAD IV values ? </div></div></blockquote><div><br =
class=3D""></div><div><br class=3D""></div><div>[Authors] This container =
represents information about&nbsp;the algorithm supported, we assume =
that AEAD algorithms&nbsp;can be also represented&nbsp;here (AES_GCM, =
AES_CCM, CHACHA20-POLY1305, ....).&nbsp;IV values are not represented =
here.</div><br class=3D""><blockquote type=3D"cite" class=3D""><div =
class=3D""><div class=3D"">Possibly the truncation values ?<br =
class=3D""></div></div></blockquote><div><br class=3D""></div>[Authors] =
For auth-trunc values, we will include that&nbsp;in container ah-sa =
unless AH is finally removed.</div><div><br class=3D""><blockquote =
type=3D"cite" class=3D""><div class=3D""><div class=3D""><br =
class=3D"">Section 6.3:<br class=3D""><br class=3D"">I only see PSK and =
RSA algorithms? No ECDSA via RFC 7427 Digital Signatures?<br =
class=3D"">(no PAKE, we have two IKE PAKE's although it looks like we =
want an CFRG new one)<br class=3D""></div></div></blockquote><div><br =
class=3D""></div>[Authors]<br class=3D"">See answer in Appendix =
section.</div><div><br class=3D""><blockquote type=3D"cite" =
class=3D""><div class=3D""><div class=3D""><br class=3D"">Should PSK be =
of type "string". Some people want to hex entry? Although those are =
often written<br class=3D"">as strings with a 0x prefix.<br =
class=3D""></div></div></blockquote><div><br class=3D""></div><div><br =
class=3D""></div>[Authors]<br class=3D"">Agree</div><div><br =
class=3D""><blockquote type=3D"cite" class=3D""><div class=3D""><div =
class=3D""><br class=3D"">I see some CRL entries, but no OCSP entries. =
Is it expected those URI's are stored within the certificates,<br =
class=3D"">and the received OCSP responses will never be communicated =
through this interface?<br class=3D""></div></div></blockquote><div><br =
class=3D""></div>[Authors]<br class=3D"">Agree. We can add CRL and OCSP =
URLs</div><div><br class=3D""><blockquote type=3D"cite" class=3D""><div =
class=3D""><div class=3D""><br class=3D"">I see no local and remote =
part, meaning that only symmetric authentication methods can be used. =
IKEv2 supports<br class=3D"">asymmetric authentication methods as well. =
Especially when using EAP and sometimes with AUTHHNULL, this method<br =
class=3D"">is very asymmetric. So I believe this entry needs to be split =
in a local/remote auth method.<br =
class=3D""></div></div></blockquote><div><br class=3D""></div>[Authors]<br=
 class=3D"">Agree</div><div><br class=3D""><blockquote type=3D"cite" =
class=3D""><div class=3D""><div class=3D""><br class=3D"">Section =
6.4:<br class=3D""><br class=3D"">type-autostartup issues...<br =
class=3D""><br class=3D""> typedef type-autostartup {<br class=3D""> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;type enumeration {<br class=3D""> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;enum ALWAYSON { =
description " ";}<br class=3D""> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;enum INITIATE-ON-DEMAND =
{description " ";}<br class=3D""> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;enum RESPOND-ONLY =
{description " ";}<br class=3D""> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;}<br =
class=3D""> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;description "Different types =
of how IKEv2 starts the IPsec SAs";<br class=3D""><br class=3D"">With =
libreswan we have similar keywords, and run into some interesting =
issues. We found what is really needed is to<br class=3D"">know the =
current state and the connection desired state. for example, when using =
ondemand and the connection is up,<br class=3D"">it is important to know =
it is up because of ondemand. So that when you receive a Delete request, =
you can go back<br class=3D"">to ondemand state. If you dont keep this =
state then you cannot tell the difference between alwayson/ondemand =
if<br class=3D"">the connection is "up". Similarly, we had issues where =
connections has a definition like above, but the administrator<br =
class=3D"">performs an action. It is unclear if such an action is =
considered a temporary override or basically a runtime update<br =
class=3D"">of the configuration. So lets say we are in respondonly, and =
the administrator brings the connection up. Now the other<br =
class=3D"">end sends a delete. Do you assume you are in alwayson state =
or in ondemand state? And if you believe alwayson, be<br =
class=3D"">prepared for a war with the remote endpoint that keeps =
sending deletes because it wants to be down.<br =
class=3D""></div></div></blockquote><div><br class=3D""></div>[Authors] =
Do you think this is something the model&nbsp;should consider? We mean =
that, after all, behing the model&nbsp;we will have =
an&nbsp;implementation (could be libreswan, strongswan etc.. that it =
will deal with&nbsp;these aspects) It&nbsp;is true that we should define =
clearly what ALWAYSON, INITIATE-ON-DEMAND,&nbsp;RESPOND-ONLY, =
etc=E2=80=A6</div><div><br class=3D""><blockquote type=3D"cite" =
class=3D""><div class=3D""><div class=3D""><br class=3D""><br =
class=3D"">Why is there nat-traversal and espencap. Why not just have =
espencap allow to have a value of 'none=E2=80=99 ?<br =
class=3D""></div></div></blockquote><div><br class=3D""></div><div><br =
class=3D""></div><div>[Authors]<br class=3D"">Agree</div><br =
class=3D""><blockquote type=3D"cite" class=3D""><div class=3D""><div =
class=3D"">IKEv2 allows more then one oaddr &nbsp;(eg multiple SOURCE =
NAT IPs) but the value is not a list?<br =
class=3D""></div></div></blockquote><div><br =
class=3D""></div><div>[Authors]<br class=3D"">Agree for the IKE case.<br =
class=3D"">For pfkey_v2 (setkey), it does not allow to =
specify&nbsp;oaddr.<br class=3D"">For xfrm, it does allow to specify =
only one oaddr.<br class=3D"">Does make it sense&nbsp;to allow more than =
one oaddr for IKE-less case?</div><br class=3D""><blockquote type=3D"cite"=
 class=3D""><div class=3D""><div class=3D""><br class=3D"">The terms =
phase1-* should be called ike-* or ike-sa-* as phase1/phase2 is IKEv1 =
terminalogy not used for IKEv2.<br =
class=3D""></div></div></blockquote><div><br class=3D""></div>[Authors]<br=
 class=3D"">Agree. We can replace phase1-* by ike-sa-* and&nbsp;phase2-* =
by ike-child-sa-*.</div><div><br class=3D""><blockquote type=3D"cite" =
class=3D""><div class=3D""><div class=3D""><br class=3D"">Why is =
combined-enc-intr needed? These are stored with the encalg entries =
anyway.<br class=3D""></div></div></blockquote><div><br =
class=3D""></div><div><br class=3D""></div>[Authors]<br =
class=3D"">Agree.</div><div><br class=3D""><blockquote type=3D"cite" =
class=3D""><div class=3D""><div class=3D""><br class=3D"">I see:<br =
class=3D""><br class=3D""><span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</span>+--rw local<br class=3D""> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;| &nbsp;&nbsp;+--rw =
(my-identifier-type)?<br class=3D""><br class=3D""><span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</span>+--rw =
remote<br class=3D""> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;| =
&nbsp;&nbsp;+--rw (my-identifier-type)?<br class=3D""><br class=3D"">I =
think "my-identifier-type" should be "identifier-type". Talking about =
"my" for the remote peer is very confusing.<br =
class=3D""></div></div></blockquote><div><br =
class=3D""></div><div>[Authors]<br class=3D"">Agree.</div><br =
class=3D""><blockquote type=3D"cite" class=3D""><div class=3D""><div =
class=3D""><br class=3D"">my-identifier-type does not support the value =
ID_NONE from RFC 7619<br class=3D""></div></div></blockquote><div><br =
class=3D""></div>[Authors]<br class=3D"">Agree. We will include that in =
the model.</div><div><br class=3D""><blockquote type=3D"cite" =
class=3D""><div class=3D""><div class=3D""><br class=3D"">Why is there =
no secion for ike-lifetime-{soft|hard} ? We also have FIPS requirements =
that IKE SA's cannot do more<br class=3D"">then X bytes for Y algorithm. =
And also bringing down idle IKE SA's etc.<br =
class=3D""></div></div></blockquote><div><br class=3D""></div>[Authors]<br=
 class=3D"">We can include a soft/hard lifetime (seconds) for =
IKE&nbsp;SA. What does it means a soft/hard lifetime (bytes) =
for&nbsp;IKE SA.&nbsp;It is&nbsp;implemented in =
current&nbsp;distributions?</div><div><br class=3D""><blockquote =
type=3D"cite" class=3D""><div class=3D""><div class=3D""><br class=3D"">I =
think "added", "used", "bytes" "packets" should be called lifetime, =
idletime, maxbytes and maxpackets<br =
class=3D""></div></div></blockquote><div><br class=3D""></div>[Authors]<br=
 class=3D"">See comment above.</div><div><br class=3D""><blockquote =
type=3D"cite" class=3D""><div class=3D""><div class=3D""><br =
class=3D"">The timestamp values "added" and "used" could have a better =
type than uint64, eg unix epoch of unixtime or something?<br =
class=3D""></div></div></blockquote><div><br class=3D""></div>[Authors]<br=
 class=3D"">Current implementations make use of __u64 or =
even&nbsp;uint32_t. Anyway, we can modify the type. What do =
you&nbsp;propose?</div><div><br class=3D""><blockquote type=3D"cite" =
class=3D""><div class=3D""><div class=3D""><br class=3D"">the term =
ike-stats was confusing me. I thought at first these were the global IKE =
statistics, like how many tunnels<br class=3D"">are up, how many errors =
received, but it turned out to be the state of a singe IKE SA. So =
perhaps ike-sa-state is a<br class=3D"">better term? =
</div></div></blockquote><div><br class=3D""></div><div>[Authors]<br =
class=3D"">Agree.</div><br class=3D""><blockquote type=3D"cite" =
class=3D""><div class=3D""><div class=3D"">IKE state I expect things =
like SPIi and SPIr as listed here.<br =
class=3D""></div></div></blockquote><div><br =
class=3D""></div><div>[Authors]<br class=3D"">global IKE statictics =
could be obtained by the SC&nbsp;through the ike-sa-state info for each =
IKE SA.</div><br class=3D""><blockquote type=3D"cite" class=3D""><div =
class=3D""><div class=3D""><br class=3D"">I am not sure why there are =
three nat-* bools instead of one value representing the nat-state? =
Possibly because we<br class=3D"">use a number of bits to indicate which =
of the NAT properties are set, and you don't do this kind of bit mapping =
in<br class=3D"">yang?<br class=3D""><br =
class=3D""></div></div></blockquote><div><br =
class=3D""></div><div>[Authors] That could be represented with uint8 =
and&nbsp;using three bits , is that what you mean? We thought =
was&nbsp;clearer to have three&nbsp;booleans.</div><br =
class=3D""><blockquote type=3D"cite" class=3D""><div class=3D""><div =
class=3D"">I dont see an entry for "latest IKE SA". We have that in =
libreswan. You can have multiple IKE SA's when rekeying,<br class=3D"">and=
 the older one is just lingering to die. Any operations such as =
informational requests, dpd/liveness probes<br class=3D"">should only be =
done with the "latest IKE SA". &nbsp;However, this is kind of a state on =
the IKE node, so I am not<br class=3D"">sure if this belongs in the yang =
model or not.<br class=3D""></div></div></blockquote><div><br =
class=3D""></div>[Authors] Is there any scenario where the SC is able to =
deal with this information for the IKE case? If so, we can try to model =
that like state data.&nbsp;</div><div><br class=3D""><blockquote =
type=3D"cite" class=3D""><div class=3D""><div class=3D""><br class=3D"">I =
see a total SA's and halfopen SA's but I don't see anything related to =
anti-DDOS cookies. Eg the number of half<br class=3D"">open SA's before =
enabling cookies. Perhaps add half-open-cookies-treshhold ?<br =
class=3D""><br class=3D""></div></div></blockquote><div><br =
class=3D""></div><div>[Authors]<br class=3D"">Several parameters can be =
configured here:<br class=3D"">- half-open-threshold: number of half =
open IKE SAs<br class=3D"">- half-open-cookies-threshold: number of half =
open IKE&nbsp;SAs with cookie activated<br class=3D"">- half-open-timer: =
timeout in seconds for connecting&nbsp;IKE SAs.</div><div><br =
class=3D""></div><div>Best regards, Gabi.</div><br class=3D""><blockquote =
type=3D"cite" class=3D""><div class=3D""><div class=3D""><br =
class=3D""></div></div></blockquote></div><br class=3D""><div class=3D"">
<div style=3D"color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
12px; 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;">-----------------------------------------------------------<br =
class=3D"">Gabriel L=C3=B3pez Mill=C3=A1n<br class=3D"">Departamento de =
Ingenier=C3=ADa de la Informaci=C3=B3n&nbsp;y las Comunicaciones<br =
class=3D"">University of Murcia<br class=3D"">Spain<br class=3D"">Tel: =
+34 868888504<br class=3D"">Fax: +34 868884151<br class=3D""><a =
href=3D"mailto:gabilm@um.es" class=3D"">email:&nbsp;gabilm@um.es</a></div>=

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

--Apple-Mail=_18FCA7D5-4A20-491D-B0E6-3AE1029FBA50--


From nobody Tue Dec  4 13:28:08 2018
Return-Path: <linda.dunbar@huawei.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 9E6A4130FD4 for <i2nsf@ietfa.amsl.com>; Tue,  4 Dec 2018 13:27:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-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 3xseXHFYzpbb for <i2nsf@ietfa.amsl.com>; Tue,  4 Dec 2018 13:27:53 -0800 (PST)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (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 25294130FF8 for <i2nsf@ietf.org>; Tue,  4 Dec 2018 13:27:53 -0800 (PST)
Received: from lhreml707-cah.china.huawei.com (unknown [172.18.7.108]) by Forcepoint Email with ESMTP id A4E282F0DDFBD for <i2nsf@ietf.org>; Tue,  4 Dec 2018 21:27:45 +0000 (GMT)
Received: from lhreml706-chm.china.huawei.com (10.201.108.55) by lhreml707-cah.china.huawei.com (10.201.108.48) with Microsoft SMTP Server (TLS) id 14.3.408.0; Tue, 4 Dec 2018 21:27:48 +0000
Received: from lhreml706-chm.china.huawei.com (10.201.108.55) by lhreml706-chm.china.huawei.com (10.201.108.55) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1591.10; Tue, 4 Dec 2018 21:27:47 +0000
Received: from SJCEML703-CHM.china.huawei.com (10.208.112.39) by lhreml706-chm.china.huawei.com (10.201.108.55) with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA_P256) id 15.1.1591.10 via Frontend Transport; Tue, 4 Dec 2018 21:27:47 +0000
Received: from SJCEML521-MBB.china.huawei.com ([169.254.6.33]) by SJCEML703-CHM.china.huawei.com ([169.254.5.160]) with mapi id 14.03.0415.000;  Tue, 4 Dec 2018 13:27:36 -0800
From: Linda Dunbar <linda.dunbar@huawei.com>
To: "i2nsf@ietf.org" <i2nsf@ietf.org>
Thread-Topic: I2NSF WG IETF 103 session minutes has been posted
Thread-Index: AdSMF4gOmxnL9H8zS0+zVj+D+isVBA==
Date: Tue, 4 Dec 2018 21:27:36 +0000
Message-ID: <4A95BA014132FF49AE685FAB4B9F17F66B1F59DF@SJCEML521-MBB.china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.192.11.90]
Content-Type: multipart/alternative; boundary="_000_4A95BA014132FF49AE685FAB4B9F17F66B1F59DFSJCEML521MBBchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2nsf/EM2b0CrMtlrDE3V0Stf3ftogQic>
Subject: [I2nsf] I2NSF WG IETF 103 session minutes has been posted
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, 04 Dec 2018 21:28:07 -0000

--_000_4A95BA014132FF49AE685FAB4B9F17F66B1F59DFSJCEML521MBBchi_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Here are the minutes from IETF103 I2NSF WG.
https://datatracker.ietf.org/meeting/103/materials/minutes-103-i2nsf-00

If we miss anything, please let us know.

Linda

--_000_4A95BA014132FF49AE685FAB4B9F17F66B1F59DFSJCEML521MBBchi_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:"\@SimSun";
	panose-1:2 1 6 0 3 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:#0563C1;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:#954F72;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri",sans-serif;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"#0563C1" vlink=3D"#954F72">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">Here are the minutes from IETF103 I2NSF WG. <o:p></o=
:p></p>
<p class=3D"MsoNormal"><a href=3D"https://datatracker.ietf.org/meeting/103/=
materials/minutes-103-i2nsf-00">https://datatracker.ietf.org/meeting/103/ma=
terials/minutes-103-i2nsf-00</a><o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">If we miss anything, please let us know. <o:p></o:p>=
</p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Linda<o:p></o:p></p>
</div>
</body>
</html>

--_000_4A95BA014132FF49AE685FAB4B9F17F66B1F59DFSJCEML521MBBchi_--


From nobody Wed Dec  5 09:28:07 2018
Return-Path: <linda.dunbar@huawei.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 771E7130E93; Wed,  5 Dec 2018 09:27:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-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 PX39i2oGepAX; Wed,  5 Dec 2018 09:27:56 -0800 (PST)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (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 E4FA0130EB8; Wed,  5 Dec 2018 09:27:54 -0800 (PST)
Received: from lhreml707-cah.china.huawei.com (unknown [172.18.7.108]) by Forcepoint Email with ESMTP id 42CED898CB92B; Wed,  5 Dec 2018 17:27:51 +0000 (GMT)
Received: from SJCEML703-CHM.china.huawei.com (10.208.112.39) by lhreml707-cah.china.huawei.com (10.201.108.48) with Microsoft SMTP Server (TLS) id 14.3.408.0; Wed, 5 Dec 2018 17:27:52 +0000
Received: from SJCEML521-MBB.china.huawei.com ([169.254.6.33]) by SJCEML703-CHM.china.huawei.com ([169.254.5.160]) with mapi id 14.03.0415.000;  Wed, 5 Dec 2018 09:27:45 -0800
From: Linda Dunbar <linda.dunbar@huawei.com>
To: "opsawg@ietf.org" <opsawg@ietf.org>
CC: "i2nsf@ietf.org" <i2nsf@ietf.org>
Thread-Topic: is there any work in Ops Area for monitoring network functions? 
Thread-Index: AdSMvzp1bJ25bMyKTtSkntvYlhrnrA==
Date: Wed, 5 Dec 2018 17:27:45 +0000
Message-ID: <4A95BA014132FF49AE685FAB4B9F17F66B1F609F@SJCEML521-MBB.china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.192.11.90]
Content-Type: multipart/alternative; boundary="_000_4A95BA014132FF49AE685FAB4B9F17F66B1F609FSJCEML521MBBchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2nsf/q3TVcuxIAJ5wlYNu8IpS6bSz7jM>
Subject: [I2nsf] is there any work in Ops Area for monitoring network functions?
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, 05 Dec 2018 17:28:06 -0000

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

T3BzYVdHOg0KDQpJMk5TRiBXRyBoYXMgYSBkcmFmdCBvbiBkYXRhIG1vZGVscyAoYW5kIGluZm9y
bWF0aW9uIG1vZGVsKSBvZiBtb25pdG9yaW5nIG5ldHdvcmsgc2VjdXJpdHkgZnVuY3Rpb25zOiBo
dHRwczovL3Rvb2xzLmlldGYub3JnL2h0bWwvZHJhZnQtaG9uZy1pMm5zZi1uc2YtbW9uaXRvcmlu
Zy1kYXRhLW1vZGVsLTA2DQoNCkl0IGluY2x1ZGVzIGRhdGEgbW9kZWxzIHRvIHJldHJpZXZlIFN5
c3RlbSBBbGFybXMsIFN5c3RlbSBFdmVudHMsIGNvdW50ZXJzLCBOU0YgRXZlbnRzL2xvZ3MsIGV0
Yy4NCg0KV2FudCB0byBzZWUgaWYgdGhlcmUgYXJlIGRhdGEgbW9kZWxzIGFscmVhZHkgc3BlY2lm
aWVkIGJ5IE9wcyBBcmVhIGZvciBtb25pdG9yaW5nIG5ldHdvcmsgZnVuY3Rpb25zIHdoaWNoIG1p
Z2h0IGhhdmUgc29tZSBjb21tb24gYXR0cmlidXRlcyB0aGF0IEkyTlNGIGNhbiBpbXBvcnQuDQoN
ClRoYW5rcywgTGluZGEgRHVuYmFyDQoNCg0KDQpGcm9tOiBNci4gSmFlaG9vbiBQYXVsIEplb25n
IFttYWlsdG86amFlaG9vbi5wYXVsQGdtYWlsLmNvbV0NClNlbnQ6IFRodXJzZGF5LCBOb3ZlbWJl
ciAxNSwgMjAxOCA2OjM1IFBNDQpUbzogTGluZGEgRHVuYmFyIDxsaW5kYS5kdW5iYXJAaHVhd2Vp
LmNvbTxtYWlsdG86bGluZGEuZHVuYmFyQGh1YXdlaS5jb20+PjsgWW9hdiBOaXIgPHluaXIuaWV0
ZkBnbWFpbC5jb208bWFpbHRvOnluaXIuaWV0ZkBnbWFpbC5jb20+Pg0KQ2M6IGkybnNmQGlldGYu
b3JnPG1haWx0bzppMm5zZkBpZXRmLm9yZz47IHNra3Vfc2VjdS1icmFpbl9hbGxAZ29vZ2xlZ3Jv
dXBzLmNvbTxtYWlsdG86c2trdV9zZWN1LWJyYWluX2FsbEBnb29nbGVncm91cHMuY29tPjsgU2Fu
Z3dvbiBIeXVuIDxzd2h5dW43N0BnbWFpbC5jb208bWFpbHRvOnN3aHl1bjc3QGdtYWlsLmNvbT4+
OyBNci4gSmFlaG9vbiBQYXVsIEplb25nIDxqYWVob29uLnBhdWxAZ21haWwuY29tPG1haWx0bzpq
YWVob29uLnBhdWxAZ21haWwuY29tPj4NClN1YmplY3Q6IFJlcXVlc3QgZm9yIFdHIEFkb3B0aW9u
IENhbGwgb24gTlNGIE1vbml0b3JpbmcgRHJhZnQNCg0KSGkgTGluZGEgYW5kIFlvYXYsDQpBcyB3
ZSBkaXNjdXNzZWQgdGhlIGxhc3QgQmFuZ2tvayBtZWV0aW5nLA0KSSBoYXZlIG1lcmdlZCB0aGUg
dHdvIGRyYWZ0cyBvZiBJbmZvcm1hdGlvbiBNb2RlbCBhbmQgRGF0YSBNb2RlbA0KZm9yIE5TRiBN
b25pdG9yaW5nIGludG8gYSBuZXcgZHJhZnQgY2FsbGVkIGRyYWZ0LWhvbmctaTJuc2YtbnNmLW1v
bml0b3JpbmctZGF0YS1tb2RlbC0wNjoNCg0KLSBUd28gSW5mb3JtYXRpb24gYW5kIERhdGEgTW9k
ZWwgRHJhZnRzDQogLiBkcmFmdC16aGFuZy1pMm5zZi1pbmZvLW1vZGVsLW1vbml0b3JpbmctMDcN
CiAuIGRyYWZ0LWhvbmctaTJuc2YtbnNmLW1vbml0b3JpbmctZGF0YS1tb2RlbC0wNQ0KDQotIEEg
TWVyZ2VkIERhdGEgTW9kZWwgRHJhZnQNCiAuIGRyYWZ0LWhvbmctaTJuc2YtbnNmLW1vbml0b3Jp
bmctZGF0YS1tb2RlbC0wNg0KIC4gaHR0cHM6Ly90b29scy5pZXRmLm9yZy9odG1sL2RyYWZ0LWhv
bmctaTJuc2YtbnNmLW1vbml0b3JpbmctZGF0YS1tb2RlbC0wNg0KDQpUaGUgTlNGIG1vbml0b3Jp
bmcgaXMgdmVyeSBpbXBvcnRhbnQgdG8gbWFuYWdlIHRoZSBJMk5TRiBzZWN1cml0eSBzZXJ2aWNl
IHN5c3RlbQ0KaW4gYSByZWxpYWJsZSBhbmQgc2NhbGFibGUgZmFzaGlvbi4NCg0KQ291bGQgeW91
IHN0YXJ0IGEgV0cgYWRvcHRpb24gY2FsbCBmb3IgdGhpcyBkcmFmdD8NCg0KVGhhbmtzLg0KDQpC
ZXN0IFJlZ2FyZHMsDQpQYXVsDQotLQ0KPT09PT09PT09PT09PT09PT09PT09PT09PT09DQpNci4g
SmFlaG9vbiAoUGF1bCkgSmVvbmcsIFBoLkQuDQpBc3NvY2lhdGUgUHJvZmVzc29yDQpEZXBhcnRt
ZW50IG9mIFNvZnR3YXJlDQpTdW5na3l1bmt3YW4gVW5pdmVyc2l0eQ0KT2ZmaWNlOiArODItMzEt
Mjk5LTQ5NTcNCkVtYWlsOiBqYWVob29uLnBhdWxAZ21haWwuY29tPG1haWx0bzpqYWVob29uLnBh
dWxAZ21haWwuY29tPiwgcGF1bGplb25nQHNra3UuZWR1PG1haWx0bzpwYXVsamVvbmdAc2trdS5l
ZHU+DQpQZXJzb25hbCBIb21lcGFnZTogaHR0cDovL2lvdGxhYi5za2t1LmVkdS9wZW9wbGUtamFl
aG9vbi1qZW9uZy5waHA8aHR0cDovL2Nwc2xhYi5za2t1LmVkdS9wZW9wbGUtamFlaG9vbi1qZW9u
Zy5waHA+DQo=

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

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTUgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
U2ltU3VuOw0KCXBhbm9zZS0xOjIgMSA2IDAgMyAxIDEgMSAxIDE7fQ0KQGZvbnQtZmFjZQ0KCXtm
b250LWZhbWlseToiQ2FtYnJpYSBNYXRoIjsNCglwYW5vc2UtMToyIDQgNSAzIDUgNCA2IDMgMiA0
O30NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6Q2FsaWJyaTsNCglwYW5vc2UtMToyIDE1IDUg
MiAyIDIgNCAzIDIgNDt9DQpAZm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5OiJcQFNpbVN1biI7DQoJ
cGFub3NlLTE6MiAxIDYgMCAzIDEgMSAxIDEgMTt9DQovKiBTdHlsZSBEZWZpbml0aW9ucyAqLw0K
cC5Nc29Ob3JtYWwsIGxpLk1zb05vcm1hbCwgZGl2Lk1zb05vcm1hbA0KCXttYXJnaW46MGluOw0K
CW1hcmdpbi1ib3R0b206LjAwMDFwdDsNCglmb250LXNpemU6MTIuMHB0Ow0KCWZvbnQtZmFtaWx5
OiJUaW1lcyBOZXcgUm9tYW4iLHNlcmlmO30NCmE6bGluaywgc3Bhbi5Nc29IeXBlcmxpbmsNCgl7
bXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0KCWNvbG9yOmJsdWU7DQoJdGV4dC1kZWNvcmF0aW9uOnVu
ZGVybGluZTt9DQphOnZpc2l0ZWQsIHNwYW4uTXNvSHlwZXJsaW5rRm9sbG93ZWQNCgl7bXNvLXN0
eWxlLXByaW9yaXR5Ojk5Ow0KCWNvbG9yOnB1cnBsZTsNCgl0ZXh0LWRlY29yYXRpb246dW5kZXJs
aW5lO30NCnNwYW4uRW1haWxTdHlsZTE3DQoJe21zby1zdHlsZS10eXBlOnBlcnNvbmFsOw0KCWZv
bnQtZmFtaWx5OiJDYWxpYnJpIixzYW5zLXNlcmlmOw0KCWNvbG9yOiMxRjQ5N0Q7fQ0Kc3Bhbi5F
bWFpbFN0eWxlMTgNCgl7bXNvLXN0eWxlLXR5cGU6cGVyc29uYWwtcmVwbHk7DQoJZm9udC1mYW1p
bHk6IkNhbGlicmkiLHNhbnMtc2VyaWY7DQoJY29sb3I6IzFGNDk3RDt9DQouTXNvQ2hwRGVmYXVs
dA0KCXttc28tc3R5bGUtdHlwZTpleHBvcnQtb25seTsNCglmb250LXNpemU6MTAuMHB0O30NCkBw
YWdlIFdvcmRTZWN0aW9uMQ0KCXtzaXplOjguNWluIDExLjBpbjsNCgltYXJnaW46MS4waW4gMS4w
aW4gMS4waW4gMS4waW47fQ0KZGl2LldvcmRTZWN0aW9uMQ0KCXtwYWdlOldvcmRTZWN0aW9uMTt9
DQotLT48L3N0eWxlPjwhLS1baWYgZ3RlIG1zbyA5XT48eG1sPg0KPG86c2hhcGVkZWZhdWx0cyB2
OmV4dD0iZWRpdCIgc3BpZG1heD0iMTAyNiIgLz4NCjwveG1sPjwhW2VuZGlmXS0tPjwhLS1baWYg
Z3RlIG1zbyA5XT48eG1sPg0KPG86c2hhcGVsYXlvdXQgdjpleHQ9ImVkaXQiPg0KPG86aWRtYXAg
djpleHQ9ImVkaXQiIGRhdGE9IjEiIC8+DQo8L286c2hhcGVsYXlvdXQ+PC94bWw+PCFbZW5kaWZd
LS0+DQo8L2hlYWQ+DQo8Ym9keSBsYW5nPSJFTi1VUyIgbGluaz0iYmx1ZSIgdmxpbms9InB1cnBs
ZSI+DQo8ZGl2IGNsYXNzPSJXb3JkU2VjdGlvbjEiPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNw
YW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90
OyxzYW5zLXNlcmlmO2NvbG9yOiMxRjQ5N0QiPk9wc2FXRzo8bzpwPjwvbzpwPjwvc3Bhbj48L3A+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250
LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6IzFGNDk3RCI+PG86
cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5
bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5z
LXNlcmlmO2NvbG9yOiMxRjQ5N0QiPkkyTlNGIFdHIGhhcyBhIGRyYWZ0IG9uIGRhdGEgbW9kZWxz
IChhbmQgaW5mb3JtYXRpb24gbW9kZWwpIG9mIG1vbml0b3JpbmcgbmV0d29yayBzZWN1cml0eSBm
dW5jdGlvbnM6DQo8L3NwYW4+PGEgaHJlZj0iaHR0cHM6Ly90b29scy5pZXRmLm9yZy9odG1sL2Ry
YWZ0LWhvbmctaTJuc2YtbnNmLW1vbml0b3JpbmctZGF0YS1tb2RlbC0wNiI+aHR0cHM6Ly90b29s
cy5pZXRmLm9yZy9odG1sL2RyYWZ0LWhvbmctaTJuc2YtbnNmLW1vbml0b3JpbmctZGF0YS1tb2Rl
bC0wNjwvYT48bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxl
PSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1z
ZXJpZjtjb2xvcjojMUY0OTdEIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFz
cz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTom
cXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6IzFGNDk3RCI+SXQgaW5jbHVkZXMg
ZGF0YSBtb2RlbHMgdG8gcmV0cmlldmUgU3lzdGVtIEFsYXJtcywgU3lzdGVtIEV2ZW50cywgY291
bnRlcnMsIE5TRiBFdmVudHMvbG9ncywgZXRjLg0KPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1p
bHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOiMxRjQ5N0QiPjxvOnA+Jm5i
c3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJm
b250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJp
Zjtjb2xvcjojMUY0OTdEIj5XYW50IHRvIHNlZSBpZiB0aGVyZSBhcmUgZGF0YSBtb2RlbHMgYWxy
ZWFkeSBzcGVjaWZpZWQgYnkgT3BzIEFyZWEgZm9yIG1vbml0b3JpbmcgbmV0d29yayBmdW5jdGlv
bnMgd2hpY2ggbWlnaHQgaGF2ZSBzb21lIGNvbW1vbiBhdHRyaWJ1dGVzIHRoYXQgSTJOU0YgY2Fu
IGltcG9ydC4NCjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxz
cGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVv
dDssc2Fucy1zZXJpZjtjb2xvcjojMUY0OTdEIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250
LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6IzFGNDk3RCI+VGhh
bmtzLCBMaW5kYSBEdW5iYXI8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9y
bWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxp
YnJpJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6IzFGNDk3RCI+PG86cD4mbmJzcDs8L286cD48L3Nw
YW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4w
cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOiMxRjQ5
N0QiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxz
cGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVv
dDssc2Fucy1zZXJpZjtjb2xvcjojMUY0OTdEIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48Yj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtm
b250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWYiPkZyb206PC9zcGFuPjwv
Yj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJp
JnF1b3Q7LHNhbnMtc2VyaWYiPiBNci4gSmFlaG9vbiBQYXVsIEplb25nIFs8YSBocmVmPSJtYWls
dG86amFlaG9vbi5wYXVsQGdtYWlsLmNvbSI+bWFpbHRvOmphZWhvb24ucGF1bEBnbWFpbC5jb208
L2E+XQ0KPGJyPg0KPGI+U2VudDo8L2I+IFRodXJzZGF5LCBOb3ZlbWJlciAxNSwgMjAxOCA2OjM1
IFBNPGJyPg0KPGI+VG86PC9iPiBMaW5kYSBEdW5iYXIgJmx0OzxhIGhyZWY9Im1haWx0bzpsaW5k
YS5kdW5iYXJAaHVhd2VpLmNvbSI+bGluZGEuZHVuYmFyQGh1YXdlaS5jb208L2E+Jmd0OzsgWW9h
diBOaXIgJmx0OzxhIGhyZWY9Im1haWx0bzp5bmlyLmlldGZAZ21haWwuY29tIj55bmlyLmlldGZA
Z21haWwuY29tPC9hPiZndDs8YnI+DQo8Yj5DYzo8L2I+IDxhIGhyZWY9Im1haWx0bzppMm5zZkBp
ZXRmLm9yZyI+aTJuc2ZAaWV0Zi5vcmc8L2E+OyA8YSBocmVmPSJtYWlsdG86c2trdV9zZWN1LWJy
YWluX2FsbEBnb29nbGVncm91cHMuY29tIj4NCnNra3Vfc2VjdS1icmFpbl9hbGxAZ29vZ2xlZ3Jv
dXBzLmNvbTwvYT47IFNhbmd3b24gSHl1biAmbHQ7PGEgaHJlZj0ibWFpbHRvOnN3aHl1bjc3QGdt
YWlsLmNvbSI+c3doeXVuNzdAZ21haWwuY29tPC9hPiZndDs7IE1yLiBKYWVob29uIFBhdWwgSmVv
bmcgJmx0OzxhIGhyZWY9Im1haWx0bzpqYWVob29uLnBhdWxAZ21haWwuY29tIj5qYWVob29uLnBh
dWxAZ21haWwuY29tPC9hPiZndDs8YnI+DQo8Yj5TdWJqZWN0OjwvYj4gUmVxdWVzdCBmb3IgV0cg
QWRvcHRpb24gQ2FsbCBvbiBOU0YgTW9uaXRvcmluZyBEcmFmdDxvOnA+PC9vOnA+PC9zcGFuPjwv
cD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPGRpdj4NCjxk
aXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+SGkgTGluZGEgYW5kIFlvYXYsPG86cD48
L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5BcyB3ZSBkaXNj
dXNzZWQgdGhlIGxhc3QgQmFuZ2tvayBtZWV0aW5nLDxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8
ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+SSBoYXZlIG1lcmdlZCB0aGUgdHdvIGRyYWZ0cyBv
ZiBJbmZvcm1hdGlvbiBNb2RlbCBhbmQgRGF0YSBNb2RlbDxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+
DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+Zm9yIE5TRiBNb25pdG9yaW5nIGludG8gYSBu
ZXcgZHJhZnQgY2FsbGVkIGRyYWZ0LWhvbmctaTJuc2YtbnNmLW1vbml0b3JpbmctZGF0YS1tb2Rl
bC0wNjo8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
PjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1h
bCI+LSBUd28gSW5mb3JtYXRpb24gYW5kIERhdGEgTW9kZWwgRHJhZnRzPG86cD48L286cD48L3A+
DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj4mbmJzcDsuIGRyYWZ0LXpoYW5n
LWkybnNmLWluZm8tbW9kZWwtbW9uaXRvcmluZy0wNyZuYnNwOzxvOnA+PC9vOnA+PC9wPg0KPC9k
aXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+Jm5ic3A7LiBkcmFmdC1ob25nLWkybnNm
LW5zZi1tb25pdG9yaW5nLWRhdGEtbW9kZWwtMDU8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRp
dj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8
ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+LSBBIE1lcmdlZCBEYXRhIE1vZGVsIERyYWZ0Jm5i
c3A7PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj4m
bmJzcDsuIGRyYWZ0LWhvbmctaTJuc2YtbnNmLW1vbml0b3JpbmctZGF0YS1tb2RlbC0wNjxvOnA+
PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+Jm5ic3A7LiA8
YSBocmVmPSJodHRwczovL3Rvb2xzLmlldGYub3JnL2h0bWwvZHJhZnQtaG9uZy1pMm5zZi1uc2Yt
bW9uaXRvcmluZy1kYXRhLW1vZGVsLTA2Ij4NCmh0dHBzOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9k
cmFmdC1ob25nLWkybnNmLW5zZi1tb25pdG9yaW5nLWRhdGEtbW9kZWwtMDY8L2E+PG86cD48L286
cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwv
bzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPlRoZSBOU0YgbW9u
aXRvcmluZyBpcyB2ZXJ5IGltcG9ydGFudCB0byBtYW5hZ2UgdGhlIEkyTlNGIHNlY3VyaXR5IHNl
cnZpY2Ugc3lzdGVtPG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIj5pbiBhIHJlbGlhYmxlIGFuZCBzY2FsYWJsZSBmYXNoaW9uLjxvOnA+PC9vOnA+PC9w
Pg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48
L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5Db3VsZCB5b3Ugc3RhcnQg
YSBXRyBhZG9wdGlvbiBjYWxsIGZvciB0aGlzIGRyYWZ0PzxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+
DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rp
dj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5UaGFua3MuPG86cD48L286cD48L3A+DQo8
L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4N
CjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPkJlc3QgUmVnYXJkcyw8bzpwPjwv
bzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPlBhdWw8bzpwPjwv
bzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPi0tJm5ic3A7PG86
cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8ZGl2Pg0KPGRpdj4NCjxkaXY+DQo8ZGl2Pg0K
PGRpdj4NCjxkaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PT09PT09PT09PT09PT09
PT09PT09PT09PT09PGJyPg0KTXIuIEphZWhvb24gKFBhdWwpIEplb25nLCBQaC5ELjxicj4NCkFz
c29jaWF0ZSBQcm9mZXNzb3I8YnI+DQpEZXBhcnRtZW50IG9mIFNvZnR3YXJlPGJyPg0KU3VuZ2t5
dW5rd2FuIFVuaXZlcnNpdHk8YnI+DQpPZmZpY2U6ICYjNDM7ODItMzEtMjk5LTQ5NTc8YnI+DQpF
bWFpbDogPGEgaHJlZj0ibWFpbHRvOmphZWhvb24ucGF1bEBnbWFpbC5jb20iIHRhcmdldD0iX2Js
YW5rIj5qYWVob29uLnBhdWxAZ21haWwuY29tPC9hPiwmbmJzcDs8YSBocmVmPSJtYWlsdG86cGF1
bGplb25nQHNra3UuZWR1IiB0YXJnZXQ9Il9ibGFuayI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZTo5
LjVwdCI+cGF1bGplb25nQHNra3UuZWR1PC9zcGFuPjwvYT48YnI+DQpQZXJzb25hbCBIb21lcGFn
ZTogPGEgaHJlZj0iaHR0cDovL2Nwc2xhYi5za2t1LmVkdS9wZW9wbGUtamFlaG9vbi1qZW9uZy5w
aHAiIHRhcmdldD0iX2JsYW5rIj4NCmh0dHA6Ly9pb3RsYWIuc2trdS5lZHUvcGVvcGxlLWphZWhv
b24tamVvbmcucGhwPC9hPjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0K
PC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8
L2Rpdj4NCjwvYm9keT4NCjwvaHRtbD4NCg==

--_000_4A95BA014132FF49AE685FAB4B9F17F66B1F609FSJCEML521MBBchi_--


From nobody Wed Dec  5 09:47:04 2018
Return-Path: <linda.dunbar@huawei.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 49DDB12D4EB; Wed,  5 Dec 2018 09:47:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-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 DTyiZvUj57dp; Wed,  5 Dec 2018 09:47:00 -0800 (PST)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (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 3A0E6127B92; Wed,  5 Dec 2018 09:47:00 -0800 (PST)
Received: from LHREML710-CAH.china.huawei.com (unknown [172.18.7.106]) by Forcepoint Email with ESMTP id 0794D1041CB36; Wed,  5 Dec 2018 17:46:56 +0000 (GMT)
Received: from SJCEML702-CHM.china.huawei.com (10.208.112.38) by LHREML710-CAH.china.huawei.com (10.201.108.33) with Microsoft SMTP Server (TLS) id 14.3.408.0; Wed, 5 Dec 2018 17:46:57 +0000
Received: from SJCEML521-MBB.china.huawei.com ([169.254.6.33]) by SJCEML702-CHM.china.huawei.com ([169.254.4.100]) with mapi id 14.03.0415.000;  Wed, 5 Dec 2018 09:46:52 -0800
From: Linda Dunbar <linda.dunbar@huawei.com>
To: "draft-ietf-i2nsf-sdn-ipsec-flow-protection@ietf.org" <draft-ietf-i2nsf-sdn-ipsec-flow-protection@ietf.org>, "i2nsf@ietf.org" <i2nsf@ietf.org>
Thread-Topic: Does it mean all "UDP" traffic are "BYPASS with the enum "UDP" is described as "BYPASS"
Thread-Index: AdSMwjJHXPPXErpOQ8q1BKH0CKWowQ==
Date: Wed, 5 Dec 2018 17:46:52 +0000
Message-ID: <4A95BA014132FF49AE685FAB4B9F17F66B1F60CB@SJCEML521-MBB.china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.192.11.90]
Content-Type: multipart/alternative; boundary="_000_4A95BA014132FF49AE685FAB4B9F17F66B1F60CBSJCEML521MBBchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2nsf/Js1MQz5nOwTYXAuw46PZJAmhsb4>
Subject: [I2nsf] Does it mean all "UDP" traffic are "BYPASS with the enum "UDP" is described as "BYPASS"
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, 05 Dec 2018 17:47:02 -0000

--_000_4A95BA014132FF49AE685FAB4B9F17F66B1F60CBSJCEML521MBBchi_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable


Gabriel and Rafa,

On Page 34 (Appendix A), you have the following typedef

typedef ipsec-next-layer-proto {
type enumeration {
enum TCP { description "PROTECT the traffic with IPsec"; }
enum UDP { description "BYPASS the traffic"; }
enum SCTP { description "PROTECT the traffic with IPsec";}
enum DCCP { description "PROTECT the traffic with IPsec";}
enum ICMP { description "PROTECT the traffic with IPsec";}
enum IPv6-ICMP { description "PROTECT the traffic with IPsec";}
enum MH {description "PROTECT the traffic with IPsec";}
enum GRE {description "PROTECT the traffic with IPsec";}
}
description "Next layer proto on top of IP";
}

With the following definition, does it mean all UDP traffic are "BYPASS"?
enum UDP { description "BYPASS the traffic"; }

Thanks, Linda

--_000_4A95BA014132FF49AE685FAB4B9F17F66B1F60CBSJCEML521MBBchi_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Courier;
	panose-1:2 7 4 9 2 2 5 2 4 4;}
@font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:"\@SimSun";
	panose-1:2 1 6 0 3 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:#0563C1;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:#954F72;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri",sans-serif;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"#0563C1" vlink=3D"#954F72">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:7.5pt;font-family:Courier">=
<o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:Courier"=
>Gabriel and Rafa,
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:Courier"=
><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:Courier"=
>On Page 34 (Appendix A), you have the following typedef<o:p></o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:Courier"=
><o:p></o:p></span></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">typedef ipsec-next-layer-proto {<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in">type enumeration {<o:p></=
o:p></p>
<p class=3D"MsoNormal" style=3D"margin-left:1.0in">enum TCP { description &=
quot;PROTECT the traffic with IPsec&quot;; }<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"margin-left:1.0in">enum UDP { description &=
quot;BYPASS the traffic&quot;; }<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"margin-left:1.0in">enum SCTP { description =
&quot;PROTECT the traffic with IPsec&quot;;}<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"margin-left:1.0in">enum DCCP { description =
&quot;PROTECT the traffic with IPsec&quot;;}<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"margin-left:1.0in">enum ICMP { description =
&quot;PROTECT the traffic with IPsec&quot;;}<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"margin-left:1.0in">enum IPv6-ICMP { descrip=
tion &quot;PROTECT the traffic with IPsec&quot;;}<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"margin-left:1.0in">enum MH {description &qu=
ot;PROTECT the traffic with IPsec&quot;;}<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"margin-left:1.0in">enum GRE {description &q=
uot;PROTECT the traffic with IPsec&quot;;}<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in">}<o:p></o:p></p>
<p class=3D"MsoNormal">description &quot;Next layer proto on top of IP&quot=
;;<o:p></o:p></p>
<p class=3D"MsoNormal">}<o:p></o:p></p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:Courier"=
><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:Courier"=
>With the following definition, does it mean all UDP traffic are &#8220;BYP=
ASS&#8221;?<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:Courier"=
>enum UDP { description &quot;BYPASS the traffic&quot;; }</span><span style=
=3D"font-size:12.0pt"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Thanks, Linda <o:p></o:p></p>
</div>
</body>
</html>

--_000_4A95BA014132FF49AE685FAB4B9F17F66B1F60CBSJCEML521MBBchi_--


From nobody Wed Dec  5 10:17:59 2018
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 217E1130DEE; Wed,  5 Dec 2018 10:17:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-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 S79t4RCKrSKE; Wed,  5 Dec 2018 10:17:54 -0800 (PST)
Received: from xenon41.um.es (xenon41.um.es [155.54.212.167]) by ietfa.amsl.com (Postfix) with ESMTP id 4CF22130E96; Wed,  5 Dec 2018 10:17:53 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by xenon41.um.es (Postfix) with ESMTP id 159F120D42; Wed,  5 Dec 2018 19:17:51 +0100 (CET)
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 Xr33BaSUjEyX; Wed,  5 Dec 2018 19:17:51 +0100 (CET)
Received: from quantum.inf.um.es (quantum.inf.um.es [155.54.204.208]) (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 55611203FD; Wed,  5 Dec 2018 19:17:49 +0100 (CET)
From: Rafa Marin-Lopez <rafa@um.es>
Message-Id: <AF796150-139B-47F1-9CED-F86883E6073B@um.es>
Content-Type: multipart/alternative; boundary="Apple-Mail=_3358CB1A-82D5-42FE-A519-07FD1A6DE562"
Mime-Version: 1.0 (Mac OS X Mail 12.0 \(3445.100.39\))
Date: Wed, 5 Dec 2018 19:17:49 +0100
In-Reply-To: <4A95BA014132FF49AE685FAB4B9F17F66B1F60CB@SJCEML521-MBB.china.huawei.com>
Cc: Rafa Marin-Lopez <rafa@um.es>, "draft-ietf-i2nsf-sdn-ipsec-flow-protection@ietf.org" <draft-ietf-i2nsf-sdn-ipsec-flow-protection@ietf.org>,  "i2nsf@ietf.org" <i2nsf@ietf.org>
To: Linda Dunbar <linda.dunbar@huawei.com>
References: <4A95BA014132FF49AE685FAB4B9F17F66B1F60CB@SJCEML521-MBB.china.huawei.com>
X-Mailer: Apple Mail (2.3445.100.39)
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2nsf/KeAqNh3eSJiKPcImefs8SoIIoZw>
Subject: Re: [I2nsf] Does it mean all "UDP" traffic are "BYPASS with the enum "UDP" is described as "BYPASS"
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, 05 Dec 2018 18:17:57 -0000

--Apple-Mail=_3358CB1A-82D5-42FE-A519-07FD1A6DE562
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Hi Linda:

No, it does not. In fact, we should fix the description associated to =
each value.

Thank you.

Best Regards.

> El 5 dic 2018, a las 18:46, Linda Dunbar <linda.dunbar@huawei.com> =
escribi=C3=B3:
>=20
> =20
> Gabriel and Rafa,
> =20
> On Page 34 (Appendix A), you have the following typedef
> =20
> typedef ipsec-next-layer-proto {
> type enumeration {
> enum TCP { description "PROTECT the traffic with IPsec"; }
> enum UDP { description "BYPASS the traffic"; }
> enum SCTP { description "PROTECT the traffic with IPsec";}
> enum DCCP { description "PROTECT the traffic with IPsec";}
> enum ICMP { description "PROTECT the traffic with IPsec";}
> enum IPv6-ICMP { description "PROTECT the traffic with IPsec";}
> enum MH {description "PROTECT the traffic with IPsec";}
> enum GRE {description "PROTECT the traffic with IPsec";}
> }
> description "Next layer proto on top of IP";
> }
> =20
> With the following definition, does it mean all UDP traffic are =
=E2=80=9CBYPASS=E2=80=9D?
> enum UDP { description "BYPASS the traffic"; }
> =20
> Thanks, Linda=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=_3358CB1A-82D5-42FE-A519-07FD1A6DE562
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 =
Linda:<div class=3D""><br class=3D""></div><div class=3D"">No, it does =
not. In fact, we should fix the description associated to each =
value.</div><div class=3D""><br class=3D""></div><div class=3D"">Thank =
you.</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 5 dic 2018, a las 18:46, Linda Dunbar =
&lt;<a href=3D"mailto:linda.dunbar@huawei.com" =
class=3D"">linda.dunbar@huawei.com</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: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif;" class=3D""><span =
style=3D"font-size: 7.5pt; font-family: Courier;" class=3D""><o:p =
class=3D"">&nbsp;</o:p></span></div><div style=3D"margin: 0in 0in =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><span style=3D"font-size: 12pt; font-family: Courier;" =
class=3D"">Gabriel and Rafa,<o:p class=3D""></o:p></span></div><div =
style=3D"margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif;" class=3D""><span style=3D"font-size: 12pt; =
font-family: Courier;" class=3D""><o:p =
class=3D"">&nbsp;</o:p></span></div><div style=3D"margin: 0in 0in =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><span style=3D"font-size: 12pt; font-family: Courier;" =
class=3D"">On Page 34 (Appendix A), you have the following typedef<o:p =
class=3D""></o:p></span></div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif;" class=3D""><span =
style=3D"font-size: 12pt; font-family: Courier;" class=3D""><o:p =
class=3D""></o:p></span></div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif;" class=3D""><o:p =
class=3D"">&nbsp;</o:p></div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif;" class=3D"">typedef =
ipsec-next-layer-proto {<o:p class=3D""></o:p></div><div style=3D"margin: =
0in 0in 0.0001pt 0.5in; font-size: 11pt; font-family: Calibri, =
sans-serif;" class=3D"">type enumeration {<o:p class=3D""></o:p></div><div=
 style=3D"margin: 0in 0in 0.0001pt 1in; font-size: 11pt; font-family: =
Calibri, sans-serif;" class=3D"">enum TCP { description "PROTECT the =
traffic with IPsec"; }<o:p class=3D""></o:p></div><div style=3D"margin: =
0in 0in 0.0001pt 1in; font-size: 11pt; font-family: Calibri, =
sans-serif;" class=3D"">enum UDP { description "BYPASS the traffic"; =
}<o:p class=3D""></o:p></div><div style=3D"margin: 0in 0in 0.0001pt 1in; =
font-size: 11pt; font-family: Calibri, sans-serif;" class=3D"">enum SCTP =
{ description "PROTECT the traffic with IPsec";}<o:p =
class=3D""></o:p></div><div style=3D"margin: 0in 0in 0.0001pt 1in; =
font-size: 11pt; font-family: Calibri, sans-serif;" class=3D"">enum DCCP =
{ description "PROTECT the traffic with IPsec";}<o:p =
class=3D""></o:p></div><div style=3D"margin: 0in 0in 0.0001pt 1in; =
font-size: 11pt; font-family: Calibri, sans-serif;" class=3D"">enum ICMP =
{ description "PROTECT the traffic with IPsec";}<o:p =
class=3D""></o:p></div><div style=3D"margin: 0in 0in 0.0001pt 1in; =
font-size: 11pt; font-family: Calibri, sans-serif;" class=3D"">enum =
IPv6-ICMP { description "PROTECT the traffic with IPsec";}<o:p =
class=3D""></o:p></div><div style=3D"margin: 0in 0in 0.0001pt 1in; =
font-size: 11pt; font-family: Calibri, sans-serif;" class=3D"">enum MH =
{description "PROTECT the traffic with IPsec";}<o:p =
class=3D""></o:p></div><div style=3D"margin: 0in 0in 0.0001pt 1in; =
font-size: 11pt; font-family: Calibri, sans-serif;" class=3D"">enum GRE =
{description "PROTECT the traffic with IPsec";}<o:p =
class=3D""></o:p></div><div style=3D"margin: 0in 0in 0.0001pt 0.5in; =
font-size: 11pt; font-family: Calibri, sans-serif;" class=3D"">}<o:p =
class=3D""></o:p></div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif;" class=3D"">description=
 "Next layer proto on top of IP";<o:p class=3D""></o:p></div><div =
style=3D"margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif;" class=3D"">}<o:p class=3D""></o:p></div><div =
style=3D"margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif;" class=3D""><span style=3D"font-size: 12pt; =
font-family: Courier;" class=3D""><o:p =
class=3D"">&nbsp;</o:p></span></div><div style=3D"margin: 0in 0in =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><span style=3D"font-size: 12pt; font-family: Courier;" =
class=3D"">With the following definition, does it mean all UDP traffic =
are =E2=80=9CBYPASS=E2=80=9D?<o:p class=3D""></o:p></span></div><div =
style=3D"margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif;" class=3D""><span style=3D"font-size: 12pt; =
font-family: Courier;" class=3D"">enum UDP { description "BYPASS the =
traffic"; }</span><span style=3D"font-size: 12pt;" class=3D""><o:p =
class=3D""></o:p></span></div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif;" class=3D""><o:p =
class=3D"">&nbsp;</o:p></div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif;" class=3D"">Thanks, =
Linda<span =
class=3D"Apple-converted-space">&nbsp;</span></div></div></div></blockquot=
e></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=_3358CB1A-82D5-42FE-A519-07FD1A6DE562--


From nobody Wed Dec  5 12:48:50 2018
Return-Path: <linda.dunbar@huawei.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 30276130EBF for <i2nsf@ietfa.amsl.com>; Wed,  5 Dec 2018 12:48:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-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 vTCroXslYkRq for <i2nsf@ietfa.amsl.com>; Wed,  5 Dec 2018 12:48:46 -0800 (PST)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (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 70A6A130E7E for <i2nsf@ietf.org>; Wed,  5 Dec 2018 12:48:46 -0800 (PST)
Received: from LHREML710-CAH.china.huawei.com (unknown [172.18.7.106]) by Forcepoint Email with ESMTP id A49B38E001AF8 for <i2nsf@ietf.org>; Wed,  5 Dec 2018 20:48:40 +0000 (GMT)
Received: from lhreml701-chm.china.huawei.com (10.201.108.50) by LHREML710-CAH.china.huawei.com (10.201.108.33) with Microsoft SMTP Server (TLS) id 14.3.408.0; Wed, 5 Dec 2018 20:48:42 +0000
Received: from lhreml701-chm.china.huawei.com (10.201.108.50) by lhreml701-chm.china.huawei.com (10.201.108.50) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1591.10; Wed, 5 Dec 2018 20:48:42 +0000
Received: from SJCEML702-CHM.china.huawei.com (10.208.112.38) by lhreml701-chm.china.huawei.com (10.201.108.50) with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA_P256) id 15.1.1591.10 via Frontend Transport; Wed, 5 Dec 2018 20:48:41 +0000
Received: from SJCEML521-MBB.china.huawei.com ([169.254.6.33]) by SJCEML702-CHM.china.huawei.com ([169.254.4.100]) with mapi id 14.03.0415.000;  Wed, 5 Dec 2018 12:48:37 -0800
From: Linda Dunbar <linda.dunbar@huawei.com>
To: Yoav Nir <ynir.ietf@gmail.com>, Rafa Marin-Lopez <rafa@um.es>
CC: "i2nsf@ietf.org" <i2nsf@ietf.org>, Paul Wouters <paul@nohats.ca>
Thread-Topic: YANG module update when new algorithms added to IPsec,  RE: [I2nsf] Reviewing sdn-ipsec-flow-protection
Thread-Index: AdSM21S4oJ64UoeTT3W/8PiJXSfgGw==
Date: Wed, 5 Dec 2018 20:48:37 +0000
Message-ID: <4A95BA014132FF49AE685FAB4B9F17F66B1F61FE@SJCEML521-MBB.china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.192.11.90]
Content-Type: multipart/alternative; boundary="_000_4A95BA014132FF49AE685FAB4B9F17F66B1F61FESJCEML521MBBchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2nsf/Ibpyd7NXHOYimBJTp-Oizqrt4cc>
Subject: [I2nsf] YANG module update when new algorithms added to IPsec, RE:  Reviewing sdn-ipsec-flow-protection
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, 05 Dec 2018 20:48:49 -0000

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

WW9hdiBhc2tlZDoNCuKAnFdoYXQgaXMgb3VyIHBsYW4gZm9yIGZ1dHVyZSBleHBhbnNpb25zPyAg
U3VwcG9zZSB0aGVyZeKAmXMgc29tZSBob3QsIG5ldyBhbGdvcml0aG0gdGhhdCBldmVyeW9uZSBp
cyBpbXBsZW1lbnRpbmcuIEhvdyBkbyB5b3UgdXBkYXRlIHRoZSBZQU5HIG1vZGVsIGluIHRoZSBm
dXR1cmUgd2hlbiB5b3UgYWRkIG5ldyB2YWx1ZXMgdG8gdGhlIGVudW1lcmF0aW9ucz8gIElzIGl0
IHVwIHRvIHRoZSBhZG1pbmlzdHJhdG9yIHRvIG1ha2Ugc3VyZSB0aGF0IHRoZSBjb250cm9sbGVy
IGFuZCBOU0ZzIGFyZSBhbGwgb24gdGhlIOKAnHNhbWUgcGFnZeKAnT/igJ0NCg0KV2UgY2FuIHVz
ZSDigJxpbXBvcnTigJ0gYW5kIOKAnGF1Z21lbnTigJ0gdG8gYWRkIG5ldyBhdHRyaWJ1dGVzIGFz
IGRlbW9uc3RyYXRlZCBieSBodHRwczovL2RhdGF0cmFja2VyLmlldGYub3JnL2RvYy9kcmFmdC1s
ZWUtY2NhbXAtb3B0aWNhbC1pbXBhaXJtZW50LXRvcG9sb2d5LXlhbmcvP2luY2x1ZGVfdGV4dD0x
DQoNCg0KTGluZGENCkZyb206IEkybnNmIFttYWlsdG86aTJuc2YtYm91bmNlc0BpZXRmLm9yZ10g
T24gQmVoYWxmIE9mIFlvYXYgTmlyDQpTZW50OiBXZWRuZXNkYXksIE5vdmVtYmVyIDE0LCAyMDE4
IDEyOjMzIFBNDQpUbzogUmFmYSBNYXJpbi1Mb3BleiA8cmFmYUB1bS5lcz4NCkNjOiBpMm5zZkBp
ZXRmLm9yZzsgUGF1bCBXb3V0ZXJzIDxwYXVsQG5vaGF0cy5jYT4NClN1YmplY3Q6IFJlOiBbSTJu
c2ZdIFJldmlld2luZyBzZG4taXBzZWMtZmxvdy1wcm90ZWN0aW9uDQoNClRoYW5rcywgUmFmYS4N
Cg0KSnVzdCBvbmUgcmVzcG9uc2UgYmVsb3cuDQoNCg0KT24gMTQgTm92IDIwMTgsIGF0IDExOjMw
LCBSYWZhIE1hcmluLUxvcGV6IDxyYWZhQHVtLmVzPG1haWx0bzpyYWZhQHVtLmVzPj4gd3JvdGU6
DQoNCkhpIFlvYXY6DQoNCg0KRWwgOCBub3YgMjAxOCwgYSBsYXMgMTc6MTEsIFlvYXYgTmlyIDx5
bmlyLmlldGZAZ21haWwuY29tPG1haWx0bzp5bmlyLmlldGZAZ21haWwuY29tPj4gZXNjcmliacOz
Og0KDQpIaSwgYWxsDQoNCkFzIGRpc2N1c3NlZCBpbiB0aGUgcm9vbSwgd2UgbmVlZCBzb21lIHJl
dmlld2VycyBmb3IgdGhlIHNkbi1pcHNlYy1mbG93LXByb3RlY3Rpb24gZHJhZnQgKFsxXSkNCg0K
VGhhbmtzIGZvciB0aGVzZSBjb21tZW50cy4gUGxlYXNlIHNlZSBvdXIgcmVzcG9uc2UgYmVsb3cu
DQoNCg0KV2hpbGUgYW55IGNvbW1lbnRzIG9uIGFueSBwYXJ0IG9mIHRoZSBkb2N1bWVudCBhcmUg
d2VsY29tZSwgSSB3b3VsZCBsaWtlIHBlb3BsZSB0byBjb25jZW50cmF0ZSBvbiB0aGUgZm9sbG93
aW5nIGlzc3VlczoNCg0KICAqICAgVGhlIFlBTkcgbW9kZWwgaW4gQXBwZW5kaXggQQ0KDQogICAg
ICogICBTb21lIG9mIHRoZSBjcnlwdG8gc2VlbXMgb2Jzb2xldGUgKGV4YW1wbGU6IERFUykuIFdl
IHdvdWxkIGdldCBpbnRvIHRyb3VibGUgaW4gU2VjRGlyIHJldmlldy4gIE9UT0ggQ2hhQ2hhMjAt
UG9seTEzMDUgaXMgbWlzc2luZy4uDQoNCkFncmVlLiBXZSB3aWxsIHJlbW92ZSBERVMgYW5kIGFk
ZCB0aGUgYWxnb3JpdGhtIHlvdSBtZW50aW9uLg0KDQpUaGUgVExTIHdvcmtpbmcgZ3JvdXAgd2Vu
dCBxdWl0ZSBmYXIgd2l0aCBUTFMgMS4zLiAgT25seSAyIGNpcGhlcnMgcmVtYWluOiBBRVMtR0NN
IHdpdGggMTYtYnl0ZSBJQ1YsIGFuZCBDaGFDaGEyMC1Qb2x5MTMwNS4gVGhhdOKAmXMgaXQuICBT
cGVjaWZpY2FsbHksIHRoZXnigJl2ZSBkZXByZWNhdGVkIGV2ZXJ5dGhpbmcgdGhhdCBpc27igJl0
IGFuIEFFQUQuDQoNClRoZSBJUHNlY01FIHdvcmtpbmcgZ3JvdXAgaGFzbuKAmXQgZ29uZSB0aGF0
IGZhciB5ZXQuICBCdXQgaW4gcHJhY3RpY2UgcHJldHR5IG11Y2ggbm90aGluZyBpcyB1c2VkIGV4
Y2VwdCAzREVTLCBBRVMtQ0JDLCBhbmQgQUVTLUdDTS4gIFBlcmhhcHMgQ2hhQ2hhMjAtUG9seTEz
MDUgaXMgc3RhcnRpbmcgdG8gc2VlIHNvbWUgdXNlIGJ5IG5vdy4gV2UgaGF2ZSBSRkMgODIyMSwg
ZXNwZWNpYWxseSBzZWN0aW9ucyA1IGFuZCA2LiAgSSB0aGluayAoYWx0aG91Z2ggaXTigJlzIHVw
IHRvIHRoZSB3b3JraW5nIGdyb3VwKSB0aGF0IHdlIHNob3VsZCBiZSBmaW5lIGRlZmluaW5nIG9u
bHkgdGhlIE1VU1RzIGFuZCB0aGUgU0hPVUxEcyBpbiB0aG9zZSBzZWN0aW9ucy4NCg0KVGhhdCBi
cmluZ3MgYW5vdGhlciBxdWVzdGlvbi4gV2hhdCBpcyBvdXIgcGxhbiBmb3IgZnV0dXJlIGV4cGFu
c2lvbnM/ICBTdXBwb3NlIHRoZXJl4oCZcyBzb21lIGhvdCwgbmV3IGFsZ29yaXRobSB0aGF0IGV2
ZXJ5b25lIGlzIGltcGxlbWVudGluZy4gSG93IGRvIHlvdSB1cGRhdGUgdGhlIFlBTkcgbW9kZWwg
aW4gdGhlIGZ1dHVyZSB3aGVuIHlvdSBhZGQgbmV3IHZhbHVlcyB0byB0aGUgZW51bWVyYXRpb25z
PyAgSXMgaXQgdXAgdG8gdGhlIGFkbWluaXN0cmF0b3IgdG8gbWFrZSBzdXJlIHRoYXQgdGhlIGNv
bnRyb2xsZXIgYW5kIE5TRnMgYXJlIGFsbCBvbiB0aGUg4oCcc2FtZSBwYWdl4oCdPw0KDQpUaGFu
a3MNCg0KWW9hdg0K

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

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTUgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
V2luZ2RpbmdzOw0KCXBhbm9zZS0xOjUgMCAwIDAgMCAwIDAgMCAwIDA7fQ0KQGZvbnQtZmFjZQ0K
CXtmb250LWZhbWlseTpTaW1TdW47DQoJcGFub3NlLTE6MiAxIDYgMCAzIDEgMSAxIDEgMTt9DQpA
Zm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5OiJDYW1icmlhIE1hdGgiOw0KCXBhbm9zZS0xOjIgNCA1
IDMgNSA0IDYgMyAyIDQ7fQ0KQGZvbnQtZmFjZQ0KCXtmb250LWZhbWlseTpDYWxpYnJpOw0KCXBh
bm9zZS0xOjIgMTUgNSAyIDIgMiA0IDMgMiA0O30NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
IlxAU2ltU3VuIjsNCglwYW5vc2UtMToyIDEgNiAwIDMgMSAxIDEgMSAxO30NCi8qIFN0eWxlIERl
ZmluaXRpb25zICovDQpwLk1zb05vcm1hbCwgbGkuTXNvTm9ybWFsLCBkaXYuTXNvTm9ybWFsDQoJ
e21hcmdpbjowaW47DQoJbWFyZ2luLWJvdHRvbTouMDAwMXB0Ow0KCWZvbnQtc2l6ZToxMi4wcHQ7
DQoJZm9udC1mYW1pbHk6IlRpbWVzIE5ldyBSb21hbiIsc2VyaWY7fQ0KYTpsaW5rLCBzcGFuLk1z
b0h5cGVybGluaw0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJY29sb3I6Ymx1ZTsNCgl0ZXh0
LWRlY29yYXRpb246dW5kZXJsaW5lO30NCmE6dmlzaXRlZCwgc3Bhbi5Nc29IeXBlcmxpbmtGb2xs
b3dlZA0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJY29sb3I6cHVycGxlOw0KCXRleHQtZGVj
b3JhdGlvbjp1bmRlcmxpbmU7fQ0Kc3Bhbi5FbWFpbFN0eWxlMTcNCgl7bXNvLXN0eWxlLXR5cGU6
cGVyc29uYWwtcmVwbHk7DQoJZm9udC1mYW1pbHk6IkNhbGlicmkiLHNhbnMtc2VyaWY7DQoJY29s
b3I6IzFGNDk3RDt9DQouTXNvQ2hwRGVmYXVsdA0KCXttc28tc3R5bGUtdHlwZTpleHBvcnQtb25s
eTsNCglmb250LXNpemU6MTAuMHB0O30NCkBwYWdlIFdvcmRTZWN0aW9uMQ0KCXtzaXplOjguNWlu
IDExLjBpbjsNCgltYXJnaW46MS4waW4gMS4waW4gMS4waW4gMS4waW47fQ0KZGl2LldvcmRTZWN0
aW9uMQ0KCXtwYWdlOldvcmRTZWN0aW9uMTt9DQovKiBMaXN0IERlZmluaXRpb25zICovDQpAbGlz
dCBsMA0KCXttc28tbGlzdC1pZDoyMzc1OTMyNTU7DQoJbXNvLWxpc3QtdGVtcGxhdGUtaWRzOi0x
MDQwMTgwMzk2O30NCkBsaXN0IGwwOmxldmVsMQ0KCXttc28tbGV2ZWwtbnVtYmVyLWZvcm1hdDpi
dWxsZXQ7DQoJbXNvLWxldmVsLXRleHQ674K3Ow0KCW1zby1sZXZlbC10YWItc3RvcDouNWluOw0K
CW1zby1sZXZlbC1udW1iZXItcG9zaXRpb246bGVmdDsNCgl0ZXh0LWluZGVudDotLjI1aW47DQoJ
bXNvLWFuc2ktZm9udC1zaXplOjEwLjBwdDsNCglmb250LWZhbWlseTpTeW1ib2w7fQ0KQGxpc3Qg
bDA6bGV2ZWwyDQoJe21zby1sZXZlbC1udW1iZXItZm9ybWF0OmJ1bGxldDsNCgltc28tbGV2ZWwt
dGV4dDpvOw0KCW1zby1sZXZlbC10YWItc3RvcDoxLjBpbjsNCgltc28tbGV2ZWwtbnVtYmVyLXBv
c2l0aW9uOmxlZnQ7DQoJdGV4dC1pbmRlbnQ6LS4yNWluOw0KCW1zby1hbnNpLWZvbnQtc2l6ZTox
MC4wcHQ7DQoJZm9udC1mYW1pbHk6IkNvdXJpZXIgTmV3IjsNCgltc28tYmlkaS1mb250LWZhbWls
eToiVGltZXMgTmV3IFJvbWFuIjt9DQpAbGlzdCBsMDpsZXZlbDMNCgl7bXNvLWxldmVsLW51bWJl
ci1mb3JtYXQ6YnVsbGV0Ow0KCW1zby1sZXZlbC10ZXh0Ou+CpzsNCgltc28tbGV2ZWwtdGFiLXN0
b3A6MS41aW47DQoJbXNvLWxldmVsLW51bWJlci1wb3NpdGlvbjpsZWZ0Ow0KCXRleHQtaW5kZW50
Oi0uMjVpbjsNCgltc28tYW5zaS1mb250LXNpemU6MTAuMHB0Ow0KCWZvbnQtZmFtaWx5Oldpbmdk
aW5nczt9DQpAbGlzdCBsMDpsZXZlbDQNCgl7bXNvLWxldmVsLW51bWJlci1mb3JtYXQ6YnVsbGV0
Ow0KCW1zby1sZXZlbC10ZXh0Ou+CpzsNCgltc28tbGV2ZWwtdGFiLXN0b3A6Mi4waW47DQoJbXNv
LWxldmVsLW51bWJlci1wb3NpdGlvbjpsZWZ0Ow0KCXRleHQtaW5kZW50Oi0uMjVpbjsNCgltc28t
YW5zaS1mb250LXNpemU6MTAuMHB0Ow0KCWZvbnQtZmFtaWx5OldpbmdkaW5nczt9DQpAbGlzdCBs
MDpsZXZlbDUNCgl7bXNvLWxldmVsLW51bWJlci1mb3JtYXQ6YnVsbGV0Ow0KCW1zby1sZXZlbC10
ZXh0Ou+CpzsNCgltc28tbGV2ZWwtdGFiLXN0b3A6Mi41aW47DQoJbXNvLWxldmVsLW51bWJlci1w
b3NpdGlvbjpsZWZ0Ow0KCXRleHQtaW5kZW50Oi0uMjVpbjsNCgltc28tYW5zaS1mb250LXNpemU6
MTAuMHB0Ow0KCWZvbnQtZmFtaWx5OldpbmdkaW5nczt9DQpAbGlzdCBsMDpsZXZlbDYNCgl7bXNv
LWxldmVsLW51bWJlci1mb3JtYXQ6YnVsbGV0Ow0KCW1zby1sZXZlbC10ZXh0Ou+CpzsNCgltc28t
bGV2ZWwtdGFiLXN0b3A6My4waW47DQoJbXNvLWxldmVsLW51bWJlci1wb3NpdGlvbjpsZWZ0Ow0K
CXRleHQtaW5kZW50Oi0uMjVpbjsNCgltc28tYW5zaS1mb250LXNpemU6MTAuMHB0Ow0KCWZvbnQt
ZmFtaWx5OldpbmdkaW5nczt9DQpAbGlzdCBsMDpsZXZlbDcNCgl7bXNvLWxldmVsLW51bWJlci1m
b3JtYXQ6YnVsbGV0Ow0KCW1zby1sZXZlbC10ZXh0Ou+CpzsNCgltc28tbGV2ZWwtdGFiLXN0b3A6
My41aW47DQoJbXNvLWxldmVsLW51bWJlci1wb3NpdGlvbjpsZWZ0Ow0KCXRleHQtaW5kZW50Oi0u
MjVpbjsNCgltc28tYW5zaS1mb250LXNpemU6MTAuMHB0Ow0KCWZvbnQtZmFtaWx5OldpbmdkaW5n
czt9DQpAbGlzdCBsMDpsZXZlbDgNCgl7bXNvLWxldmVsLW51bWJlci1mb3JtYXQ6YnVsbGV0Ow0K
CW1zby1sZXZlbC10ZXh0Ou+CpzsNCgltc28tbGV2ZWwtdGFiLXN0b3A6NC4waW47DQoJbXNvLWxl
dmVsLW51bWJlci1wb3NpdGlvbjpsZWZ0Ow0KCXRleHQtaW5kZW50Oi0uMjVpbjsNCgltc28tYW5z
aS1mb250LXNpemU6MTAuMHB0Ow0KCWZvbnQtZmFtaWx5OldpbmdkaW5nczt9DQpAbGlzdCBsMDps
ZXZlbDkNCgl7bXNvLWxldmVsLW51bWJlci1mb3JtYXQ6YnVsbGV0Ow0KCW1zby1sZXZlbC10ZXh0
Ou+CpzsNCgltc28tbGV2ZWwtdGFiLXN0b3A6NC41aW47DQoJbXNvLWxldmVsLW51bWJlci1wb3Np
dGlvbjpsZWZ0Ow0KCXRleHQtaW5kZW50Oi0uMjVpbjsNCgltc28tYW5zaS1mb250LXNpemU6MTAu
MHB0Ow0KCWZvbnQtZmFtaWx5OldpbmdkaW5nczt9DQpvbA0KCXttYXJnaW4tYm90dG9tOjBpbjt9
DQp1bA0KCXttYXJnaW4tYm90dG9tOjBpbjt9DQotLT48L3N0eWxlPjwhLS1baWYgZ3RlIG1zbyA5
XT48eG1sPg0KPG86c2hhcGVkZWZhdWx0cyB2OmV4dD0iZWRpdCIgc3BpZG1heD0iMTAyNiIgLz4N
CjwveG1sPjwhW2VuZGlmXS0tPjwhLS1baWYgZ3RlIG1zbyA5XT48eG1sPg0KPG86c2hhcGVsYXlv
dXQgdjpleHQ9ImVkaXQiPg0KPG86aWRtYXAgdjpleHQ9ImVkaXQiIGRhdGE9IjEiIC8+DQo8L286
c2hhcGVsYXlvdXQ+PC94bWw+PCFbZW5kaWZdLS0+DQo8L2hlYWQ+DQo8Ym9keSBsYW5nPSJFTi1V
UyIgbGluaz0iYmx1ZSIgdmxpbms9InB1cnBsZSI+DQo8ZGl2IGNsYXNzPSJXb3JkU2VjdGlvbjEi
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+WW9hdiBhc2tlZDo8bzpwPjwvbzpwPjwvcD4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJnaW4tbGVmdDouNWluIj7igJw8aT5XaGF0IGlzIG91
ciBwbGFuIGZvciBmdXR1cmUgZXhwYW5zaW9ucz8gJm5ic3A7U3VwcG9zZSB0aGVyZeKAmXMgc29t
ZSBob3QsIG5ldyBhbGdvcml0aG0gdGhhdCBldmVyeW9uZSBpcyBpbXBsZW1lbnRpbmcuIEhvdyBk
byB5b3UgdXBkYXRlIHRoZSBZQU5HIG1vZGVsIGluIHRoZSBmdXR1cmUgd2hlbiB5b3UgYWRkIG5l
dyB2YWx1ZXMgdG8gdGhlIGVudW1lcmF0aW9ucz8gJm5ic3A7SXMNCiBpdCB1cCB0byB0aGUgYWRt
aW5pc3RyYXRvciB0byBtYWtlIHN1cmUgdGhhdCB0aGUgY29udHJvbGxlciBhbmQgTlNGcyBhcmUg
YWxsIG9uIHRoZSDigJxzYW1lIHBhZ2XigJ0/4oCdPC9pPjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6
JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOiMxRjQ5N0QiPjxvOnA+Jm5ic3A7
PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxhIG5hbWU9Il9NYWlsRW5k
Q29tcG9zZSI+V2UgY2FuIHVzZSDigJxpbXBvcnTigJ0gYW5kIOKAnGF1Z21lbnTigJ0gdG8gYWRk
IG5ldyBhdHRyaWJ1dGVzIGFzIGRlbW9uc3RyYXRlZCBieTwvYT48c3BhbiBzdHlsZT0iZm9udC1z
aXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWY7Y29s
b3I6IzFGNDk3RCI+DQo8L3NwYW4+PGEgaHJlZj0iaHR0cHM6Ly9kYXRhdHJhY2tlci5pZXRmLm9y
Zy9kb2MvZHJhZnQtbGVlLWNjYW1wLW9wdGljYWwtaW1wYWlybWVudC10b3BvbG9neS15YW5nLz9p
bmNsdWRlX3RleHQ9MSI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6
JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmIj5odHRwczovL2RhdGF0cmFja2VyLmlldGYu
b3JnL2RvYy9kcmFmdC1sZWUtY2NhbXAtb3B0aWNhbC1pbXBhaXJtZW50LXRvcG9sb2d5LXlhbmcv
P2luY2x1ZGVfdGV4dD0xPC9zcGFuPjwvYT48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtm
b250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6IzFGNDk3RCI+
PG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9
ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNl
cmlmO2NvbG9yOiMxRjQ5N0QiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZx
dW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjojMUY0OTdEIj48bzpwPiZuYnNwOzwv
bzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5MaW5kYTxvOnA+PC9vOnA+PC9w
Pg0KPGRpdj4NCjxkaXYgc3R5bGU9ImJvcmRlcjpub25lO2JvcmRlci10b3A6c29saWQgI0UxRTFF
MSAxLjBwdDtwYWRkaW5nOjMuMHB0IDBpbiAwaW4gMGluIj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
PjxiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGli
cmkmcXVvdDssc2Fucy1zZXJpZiI+RnJvbTo8L3NwYW4+PC9iPjxzcGFuIHN0eWxlPSJmb250LXNp
emU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZiI+IEky
bnNmIFttYWlsdG86aTJuc2YtYm91bmNlc0BpZXRmLm9yZ10NCjxiPk9uIEJlaGFsZiBPZiA8L2I+
WW9hdiBOaXI8YnI+DQo8Yj5TZW50OjwvYj4gV2VkbmVzZGF5LCBOb3ZlbWJlciAxNCwgMjAxOCAx
MjozMyBQTTxicj4NCjxiPlRvOjwvYj4gUmFmYSBNYXJpbi1Mb3BleiAmbHQ7cmFmYUB1bS5lcyZn
dDs8YnI+DQo8Yj5DYzo8L2I+IGkybnNmQGlldGYub3JnOyBQYXVsIFdvdXRlcnMgJmx0O3BhdWxA
bm9oYXRzLmNhJmd0Ozxicj4NCjxiPlN1YmplY3Q6PC9iPiBSZTogW0kybnNmXSBSZXZpZXdpbmcg
c2RuLWlwc2VjLWZsb3ctcHJvdGVjdGlvbjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0K
PC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiPlRoYW5rcywgUmFmYS48bzpwPjwvbzpwPjwvcD4NCjxkaXY+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiPkp1c3Qgb25lIHJlc3BvbnNlIGJlbG93LjxvOnA+PC9vOnA+PC9w
Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxicj4NCjxicj4NCjxvOnA+PC9vOnA+PC9w
Pg0KPGJsb2NrcXVvdGUgc3R5bGU9Im1hcmdpbi10b3A6NS4wcHQ7bWFyZ2luLWJvdHRvbTo1LjBw
dCI+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+T24gMTQgTm92IDIwMTgsIGF0IDExOjMw
LCBSYWZhIE1hcmluLUxvcGV6ICZsdDs8YSBocmVmPSJtYWlsdG86cmFmYUB1bS5lcyI+cmFmYUB1
bS5lczwvYT4mZ3Q7IHdyb3RlOjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxkaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1z
b05vcm1hbCI+SGkgWW9hdjo8bzpwPjwvbzpwPjwvcD4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9y
bWFsIj48YnI+DQo8YnI+DQo8bzpwPjwvbzpwPjwvcD4NCjxibG9ja3F1b3RlIHN0eWxlPSJtYXJn
aW4tdG9wOjUuMHB0O21hcmdpbi1ib3R0b206NS4wcHQiPg0KPGRpdj4NCjxwIGNsYXNzPSJNc29O
b3JtYWwiPkVsIDggbm92IDIwMTgsIGEgbGFzIDE3OjExLCBZb2F2IE5pciAmbHQ7PGEgaHJlZj0i
bWFpbHRvOnluaXIuaWV0ZkBnbWFpbC5jb20iPnluaXIuaWV0ZkBnbWFpbC5jb208L2E+Jmd0OyBl
c2NyaWJpw7M6PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxv
OnA+Jm5ic3A7PC9vOnA+PC9wPg0KPGRpdj4NCjxkaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCI+SGksIGFsbDxvOnA+PC9vOnA+PC9wPg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
PjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1h
bCI+QXMgZGlzY3Vzc2VkIGluIHRoZSByb29tLCB3ZSBuZWVkIHNvbWUgcmV2aWV3ZXJzIGZvciB0
aGUgc2RuLWlwc2VjLWZsb3ctcHJvdGVjdGlvbiBkcmFmdCAoWzFdKTxvOnA+PC9vOnA+PC9wPg0K
PC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Jsb2NrcXVvdGU+DQo8ZGl2Pg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiPlRoYW5rcyBmb3IgdGhlc2UgY29tbWVudHMuIFBsZWFzZSBzZWUgb3VyIHJl
c3BvbnNlIGJlbG93Ljxicj4NCjxicj4NCjxvOnA+PC9vOnA+PC9wPg0KPGJsb2NrcXVvdGUgc3R5
bGU9Im1hcmdpbi10b3A6NS4wcHQ7bWFyZ2luLWJvdHRvbTo1LjBwdCI+DQo8ZGl2Pg0KPGRpdj4N
CjxkaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+
DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5XaGlsZSBhbnkgY29tbWVudHMg
b24gYW55IHBhcnQgb2YgdGhlIGRvY3VtZW50IGFyZSB3ZWxjb21lLCBJIHdvdWxkIGxpa2UgcGVv
cGxlIHRvIGNvbmNlbnRyYXRlIG9uIHRoZSBmb2xsb3dpbmcgaXNzdWVzOjxvOnA+PC9vOnA+PC9w
Pg0KPC9kaXY+DQo8ZGl2Pg0KPHVsIHR5cGU9ImRpc2MiPg0KPGxpIGNsYXNzPSJNc29Ob3JtYWwi
IHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0
bzttc28tbGlzdDpsMCBsZXZlbDEgbGZvMSI+DQpUaGUgWUFORyBtb2RlbCBpbiBBcHBlbmRpeCBB
PG86cD48L286cD48L2xpPjwvdWw+DQo8dWwgdHlwZT0iZGlzYyI+DQo8dWwgdHlwZT0iY2lyY2xl
Ij4NCjxsaSBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87
bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG87bXNvLWxpc3Q6bDAgbGV2ZWwyIGxmbzEiPg0KU29t
ZSBvZiB0aGUgY3J5cHRvIHNlZW1zIG9ic29sZXRlIChleGFtcGxlOiBERVMpLiBXZSB3b3VsZCBn
ZXQgaW50byB0cm91YmxlIGluIFNlY0RpciByZXZpZXcuICZuYnNwO09UT0ggQ2hhQ2hhMjAtUG9s
eTEzMDUgaXMgbWlzc2luZy4uPG86cD48L286cD48L2xpPjwvdWw+DQo8L3VsPg0KPC9kaXY+DQo8
L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Jsb2NrcXVvdGU+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1z
b05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIj5BZ3JlZS4gV2Ugd2lsbCByZW1vdmUgREVTIGFuZCBhZGQgdGhlIGFsZ29yaXRo
bSB5b3UgbWVudGlvbi48bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwv
ZGl2Pg0KPC9ibG9ja3F1b3RlPg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5i
c3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+VGhlIFRM
UyB3b3JraW5nIGdyb3VwIHdlbnQgcXVpdGUgZmFyIHdpdGggVExTIDEuMy4gJm5ic3A7T25seSAy
IGNpcGhlcnMgcmVtYWluOiBBRVMtR0NNIHdpdGggMTYtYnl0ZSBJQ1YsIGFuZCBDaGFDaGEyMC1Q
b2x5MTMwNS4gVGhhdOKAmXMgaXQuICZuYnNwO1NwZWNpZmljYWxseSwgdGhleeKAmXZlIGRlcHJl
Y2F0ZWQgZXZlcnl0aGluZyB0aGF0IGlzbuKAmXQgYW4gQUVBRC48bzpwPjwvbzpwPjwvcD4NCjwv
ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0K
PC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+VGhlIElQc2VjTUUgd29ya2luZyBn
cm91cCBoYXNu4oCZdCBnb25lIHRoYXQgZmFyIHlldC4gJm5ic3A7QnV0IGluIHByYWN0aWNlIHBy
ZXR0eSBtdWNoIG5vdGhpbmcgaXMgdXNlZCBleGNlcHQgM0RFUywgQUVTLUNCQywgYW5kIEFFUy1H
Q00uICZuYnNwO1BlcmhhcHMgQ2hhQ2hhMjAtUG9seTEzMDUgaXMgc3RhcnRpbmcgdG8gc2VlIHNv
bWUgdXNlIGJ5IG5vdy4gV2UgaGF2ZSBSRkMgODIyMSwgZXNwZWNpYWxseSBzZWN0aW9ucyA1IGFu
ZA0KIDYuICZuYnNwO0kgdGhpbmsgKGFsdGhvdWdoIGl04oCZcyB1cCB0byB0aGUgd29ya2luZyBn
cm91cCkgdGhhdCB3ZSBzaG91bGQgYmUgZmluZSBkZWZpbmluZyBvbmx5IHRoZSBNVVNUcyBhbmQg
dGhlIFNIT1VMRHMgaW4gdGhvc2Ugc2VjdGlvbnMuPG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxk
aXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0K
PGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPlRoYXQgYnJpbmdzIGFub3RoZXIgcXVlc3Rpb24u
IFdoYXQgaXMgb3VyIHBsYW4gZm9yIGZ1dHVyZSBleHBhbnNpb25zPyAmbmJzcDtTdXBwb3NlIHRo
ZXJl4oCZcyBzb21lIGhvdCwgbmV3IGFsZ29yaXRobSB0aGF0IGV2ZXJ5b25lIGlzIGltcGxlbWVu
dGluZy4gSG93IGRvIHlvdSB1cGRhdGUgdGhlIFlBTkcgbW9kZWwgaW4gdGhlIGZ1dHVyZSB3aGVu
IHlvdSBhZGQgbmV3IHZhbHVlcyB0byB0aGUgZW51bWVyYXRpb25zPyAmbmJzcDtJcw0KIGl0IHVw
IHRvIHRoZSBhZG1pbmlzdHJhdG9yIHRvIG1ha2Ugc3VyZSB0aGF0IHRoZSBjb250cm9sbGVyIGFu
ZCBOU0ZzIGFyZSBhbGwgb24gdGhlIOKAnHNhbWUgcGFnZeKAnT88bzpwPjwvbzpwPjwvcD4NCjwv
ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0K
PC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+VGhhbmtzPG86cD48L286cD48L3A+
DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwv
cD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPllvYXY8bzpwPjwvbzpwPjwv
cD4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9ib2R5Pg0KPC9odG1sPg0K

--_000_4A95BA014132FF49AE685FAB4B9F17F66B1F61FESJCEML521MBBchi_--


From nobody Wed Dec  5 13:29:48 2018
Return-Path: <linda.dunbar@huawei.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 D982812D4E7; Wed,  5 Dec 2018 13:29:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-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 xUf6_dIdqyVh; Wed,  5 Dec 2018 13:29:37 -0800 (PST)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (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 71E30130E95; Wed,  5 Dec 2018 13:29:36 -0800 (PST)
Received: from LHREML713-CAH.china.huawei.com (unknown [172.18.7.106]) by Forcepoint Email with ESMTP id 7DEF7E86E6890; Wed,  5 Dec 2018 21:29:31 +0000 (GMT)
Received: from SJCEML701-CHM.china.huawei.com (10.208.112.40) by LHREML713-CAH.china.huawei.com (10.201.108.36) with Microsoft SMTP Server (TLS) id 14.3.408.0; Wed, 5 Dec 2018 21:29:32 +0000
Received: from SJCEML521-MBB.china.huawei.com ([169.254.6.33]) by SJCEML701-CHM.china.huawei.com ([169.254.3.198]) with mapi id 14.03.0415.000;  Wed, 5 Dec 2018 13:29:26 -0800
From: Linda Dunbar <linda.dunbar@huawei.com>
To: Yoav Nir <ynir.ietf@gmail.com>, Gabriel Lopez <gabilm@um.es>
CC: "i2nsf@ietf.org" <i2nsf@ietf.org>, "ipsec@ietf.org WG" <ipsec@ietf.org>, Paul Wouters <paul@nohats.ca>, Rafa Marin Lopez <rafa@um.es>
Thread-Topic: [I2nsf] [IPsec] Review of draft-ietf-i2nsf-sdn-ipsec-flow-protection-03 (Section 1)
Thread-Index: AQHUhnHCQWI/aI09rEKRAvt+rExe0aVkvROAgAv4zeA=
Date: Wed, 5 Dec 2018 21:29:26 +0000
Message-ID: <4A95BA014132FF49AE685FAB4B9F17F66B1F6237@SJCEML521-MBB.china.huawei.com>
References: <A881C135-9BF7-4E93-BB7A-75EB3D1FF605@gmail.com> <6839D47C-4074-486F-9350-8EB7B378036C@um.es> <DAE14995-8504-4134-B021-93D56A4994FB@gmail.com> <alpine.LRH.2.21.1811180149220.25604@bofh.nohats.ca> <3415DDC9-ED45-462F-B561-E48773E404FB@um.es> <alpine.LRH.2.21.1811270826430.2053@bofh.nohats.ca> <B47EE67E-1B50-44BB-9821-AB439CA2C2F1@um.es> <37F4E2D9-47C3-450C-B1E8-649FC901DA82@gmail.com>
In-Reply-To: <37F4E2D9-47C3-450C-B1E8-649FC901DA82@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.192.11.90]
Content-Type: multipart/alternative; boundary="_000_4A95BA014132FF49AE685FAB4B9F17F66B1F6237SJCEML521MBBchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2nsf/DzrWl7o5l3_UOl-NKdxM9yvR8EM>
Subject: Re: [I2nsf] [IPsec] Review of draft-ietf-i2nsf-sdn-ipsec-flow-protection-03 (Section 1)
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, 05 Dec 2018 21:29:40 -0000

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

SSBsaWtlIHRoZSB0aXRsZSBvZiAg4oCcZGlzdHJpYnV0ZWQga2V5aW5n4oCdIChjYXNlIDEpIHZz
IOKAnGNlbnRyYWxpemVkIGtleWluZ+KAnSAoQ2FzZSAyKS4NCg0KTGluZGENCg0KRnJvbTogSTJu
c2YgW21haWx0bzppMm5zZi1ib3VuY2VzQGlldGYub3JnXSBPbiBCZWhhbGYgT2YgWW9hdiBOaXIN
ClNlbnQ6IFR1ZXNkYXksIE5vdmVtYmVyIDI3LCAyMDE4IDQ6MzkgUE0NClRvOiBHYWJyaWVsIExv
cGV6IDxnYWJpbG1AdW0uZXM+DQpDYzogaTJuc2ZAaWV0Zi5vcmc7IGlwc2VjQGlldGYub3JnIFdH
IDxpcHNlY0BpZXRmLm9yZz47IFBhdWwgV291dGVycyA8cGF1bEBub2hhdHMuY2E+OyBSYWZhIE1h
cmluIExvcGV6IDxyYWZhQHVtLmVzPg0KU3ViamVjdDogUmU6IFtJMm5zZl0gW0lQc2VjXSBSZXZp
ZXcgb2YgZHJhZnQtaWV0Zi1pMm5zZi1zZG4taXBzZWMtZmxvdy1wcm90ZWN0aW9uLTAzIChTZWN0
aW9uIDEpDQoNCkEgY291cGxlIG9mIHJlbWFya3MgKHdpdGggbm8gaGF0cykNCg0KSWYgd2XigJly
ZSBiaWtlc2hlZGRpbmcgdGhlIG5hbWVzLCBJIHRoaW5rIHRoZSBkaWZmZXJlbmNlIGlzIHRoYXQg
aW4gb25lIGNhc2UgdGhlIHR3byBOU0ZzIGdlbmVyYXRlIHRyYWZmaWMga2V5cyBiZXR3ZWVuIHRo
ZW1zZWx2ZXMsIGFuZCBpbiB0aGUgb3RoZXIgaXQgaXMgdGhlIGNvbnRyb2xsZXIgdGhhdCBnZW5l
cmF0ZXMgdGhlIGtleXMgZm9yIHRoZW0uICBTbyBob3cgYWJvdXQg4oCcZGlzdHJpYnV0ZWQga2V5
aW5n4oCdIHZzIOKAnGNlbnRyYWxpemVkIGtleWluZ+KAnSwgb3IgcGVyaGFwcyDigJxhdXRvbWF0
aWMga2V5aW5n4oCdIHZzIOKAnFNETiBrZXlpbmfigJ0uDQoNCg0KQWxzbywgSSBoYXZlIGJlZW4g
YXNrZWQgYnkgc29tZW9uZSBub3Qgb24gdGhpcyBsaXN0IHdoZXRoZXIgb3VyIHdvcmsgY292ZXJz
IHRoZSByb2FkIHdhcnJpb3IgdXNlIGNhc2UuIEkgc2FpZCBpdCBkaWRu4oCZdCBhbmQgd29uZGVy
ZWQgd2h5LiBTbyBJIGdvdCB0aGVzZSBwb2ludHM6DQoNCiAgKiAgIFJvYWQgd2FycmlvcnMgYXJl
IG51bWVyb3VzIGFuZCBub3Qgd2hlcmUgdGhlIGFkbWluaXN0cmF0b3IgY2FuIGNvbmZpZ3VyZSB0
aGVtIG1hbnVhbGx5Lg0KICAqICAgQWRkaXRpb25hbGx5LCB0aGUgY29uZmlndXJhdGlvbiBvZiB3
aGF0IG5ldHdvcmtzLCBnYXRld2F5cyAoTlNGcyksIGFuZCByZXNvdXJjZXMgYSByb2FkIHdhcnJp
b3IgbWF5IGFjY2VzcyAoaW4gSVBzZWMgdGVybXMsIHRoZSBTUEQgYW5kIFBBRCkgY2hhbmdlIG9m
dGVuLg0KICAqICAgQmVjYXVzZSBvZiB0aGUgYWJvdmUsIHNvbWUgYXV0b21hdGljIG1ldGhvZCBv
ZiBjb25maWd1cmluZyBTUEQgYW5kIFBBRCBpcyBuZWVkZWQuDQogICogICBUaGVyZSBpcyBhbHNv
IHRoZSBpc3N1ZSBvZiBtdWx0aXBsZSBWUE4gZ2F0ZXdheXMgY292ZXJpbmcgc2ltaWxhciBkb21h
aW5zLCBhbmQgVlBOIGdhdGV3YXlzIGJlaW5nIG92ZXJsb2FkZWQgb3IgZG93biBmb3IgbWFpbnRl
bmFuY2UsIGFzIHdlbGwgYXMgbWFsZnVuY3Rpb25zIGluIHRoZSBuZXR3b3JrIGJlaGluZCB0aG9z
ZSBWUE4gZ2F0ZXdheXMuIFNvIHRoZSBkZWNpc2lvbiBvbiB3aGljaCBnYXRld2F5IGEgcm9hZCB3
YXJyaW9yIHNob3VsZCB1c2UgdG8gYWNjZXNzIGEgcGFydGljdWxhciByZXNvdXJjZSBpcyBhbHNv
IGEgbmF0dXJhbCBxdWVzdGlvbiB0byBhc2sgYW4gU0ROIGNvbnRyb2xsZXIuDQoNClNpbmNlIEkg
dXNlZCB0byB3b3JrIGZvciBhIFZQTiB2ZW5kb3IsIEkgY2FuIHRlbGwgeW91IHdoYXQgb3VyIHBy
b2R1Y3QgZGlkOg0KDQogICogICBUaGUgY3VycmVudCBjb25maWd1cmF0aW9uIHdhcyBmb3JtYXR0
ZWQgKGF1dG9tYXRpY2FsbHkgYnkgYSBtYW5hZ2VtZW50IGZ1bmN0aW9uKSBhcyBhIHRleHQgZmls
ZSB0aGF0IHRoZSByb2FkIHdhcnJpb3IgZG93bmxvYWRlZCB0aHJvdWdoIHRoZSBWUE4gZ2F0ZXdh
eSAodGhlIGdhdGV3YXkgZG91YmxlZCBhcyBhIHNlcnZlciBzZXJ2aW5nIHRoaXMgb25lIGZpbGUp
DQogICogICBUaGUgcHJvcGVyIGdhdGV3YXkgdG8gY29ubmVjdCB0byB3YXMgZGV0ZXJtaW5lZCBi
eSBwaW5naW5nIGFsbCBnYXRld2F5cyB0aGF0IHdlcmUgcG9zc2libGUgYWNjb3JkaW5nIHRvIHRo
ZSBjb25maWd1cmF0aW9uIGZpbGUuDQogICogICBUaGlzIGRpZCBub3QgYWNjb3VudCBmb3IgYW55
IGludGVybmFsIG5ldHdvcmtpbmcgaXNzdWVzLg0KDQpJIGRvbuKAmXQga25vdyBpZiB0aGlzIHNo
b3VsZCBiZSBwYXJ0IG9mICp0aGlzKiBlZmZvcnQsIGJ1dCB0aGVyZSBpcyBhIHVzZSBjYXNlIGZv
ciByb2FkIHdhcnJpb3IgU0ROLg0KDQpZb2F2DQo=

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

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTUgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
V2luZ2RpbmdzOw0KCXBhbm9zZS0xOjUgMCAwIDAgMCAwIDAgMCAwIDA7fQ0KQGZvbnQtZmFjZQ0K
CXtmb250LWZhbWlseTpTaW1TdW47DQoJcGFub3NlLTE6MiAxIDYgMCAzIDEgMSAxIDEgMTt9DQpA
Zm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5OiJDYW1icmlhIE1hdGgiOw0KCXBhbm9zZS0xOjIgNCA1
IDMgNSA0IDYgMyAyIDQ7fQ0KQGZvbnQtZmFjZQ0KCXtmb250LWZhbWlseTpDYWxpYnJpOw0KCXBh
bm9zZS0xOjIgMTUgNSAyIDIgMiA0IDMgMiA0O30NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
IlxAU2ltU3VuIjsNCglwYW5vc2UtMToyIDEgNiAwIDMgMSAxIDEgMSAxO30NCi8qIFN0eWxlIERl
ZmluaXRpb25zICovDQpwLk1zb05vcm1hbCwgbGkuTXNvTm9ybWFsLCBkaXYuTXNvTm9ybWFsDQoJ
e21hcmdpbjowaW47DQoJbWFyZ2luLWJvdHRvbTouMDAwMXB0Ow0KCWZvbnQtc2l6ZToxMi4wcHQ7
DQoJZm9udC1mYW1pbHk6IlRpbWVzIE5ldyBSb21hbiIsc2VyaWY7fQ0KYTpsaW5rLCBzcGFuLk1z
b0h5cGVybGluaw0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJY29sb3I6IzA1NjNDMTsNCgl0
ZXh0LWRlY29yYXRpb246dW5kZXJsaW5lO30NCmE6dmlzaXRlZCwgc3Bhbi5Nc29IeXBlcmxpbmtG
b2xsb3dlZA0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJY29sb3I6Izk1NEY3MjsNCgl0ZXh0
LWRlY29yYXRpb246dW5kZXJsaW5lO30NCnNwYW4uRW1haWxTdHlsZTE3DQoJe21zby1zdHlsZS10
eXBlOnBlcnNvbmFsLXJlcGx5Ow0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIixzYW5zLXNlcmlmOw0K
CWNvbG9yOiMxRjQ5N0Q7fQ0KLk1zb0NocERlZmF1bHQNCgl7bXNvLXN0eWxlLXR5cGU6ZXhwb3J0
LW9ubHk7DQoJZm9udC1zaXplOjEwLjBwdDt9DQpAcGFnZSBXb3JkU2VjdGlvbjENCgl7c2l6ZTo4
LjVpbiAxMS4waW47DQoJbWFyZ2luOjEuMGluIDEuMGluIDEuMGluIDEuMGluO30NCmRpdi5Xb3Jk
U2VjdGlvbjENCgl7cGFnZTpXb3JkU2VjdGlvbjE7fQ0KLyogTGlzdCBEZWZpbml0aW9ucyAqLw0K
QGxpc3QgbDANCgl7bXNvLWxpc3QtaWQ6MTgwMjM4NzMxOw0KCW1zby1saXN0LXRlbXBsYXRlLWlk
czotMTY0MzE4ODIwNDt9DQpAbGlzdCBsMDpsZXZlbDENCgl7bXNvLWxldmVsLW51bWJlci1mb3Jt
YXQ6YnVsbGV0Ow0KCW1zby1sZXZlbC10ZXh0Ou+CtzsNCgltc28tbGV2ZWwtdGFiLXN0b3A6LjVp
bjsNCgltc28tbGV2ZWwtbnVtYmVyLXBvc2l0aW9uOmxlZnQ7DQoJdGV4dC1pbmRlbnQ6LS4yNWlu
Ow0KCW1zby1hbnNpLWZvbnQtc2l6ZToxMC4wcHQ7DQoJZm9udC1mYW1pbHk6U3ltYm9sO30NCkBs
aXN0IGwwOmxldmVsMg0KCXttc28tbGV2ZWwtbnVtYmVyLWZvcm1hdDpidWxsZXQ7DQoJbXNvLWxl
dmVsLXRleHQ6bzsNCgltc28tbGV2ZWwtdGFiLXN0b3A6MS4waW47DQoJbXNvLWxldmVsLW51bWJl
ci1wb3NpdGlvbjpsZWZ0Ow0KCXRleHQtaW5kZW50Oi0uMjVpbjsNCgltc28tYW5zaS1mb250LXNp
emU6MTAuMHB0Ow0KCWZvbnQtZmFtaWx5OiJDb3VyaWVyIE5ldyI7DQoJbXNvLWJpZGktZm9udC1m
YW1pbHk6IlRpbWVzIE5ldyBSb21hbiI7fQ0KQGxpc3QgbDA6bGV2ZWwzDQoJe21zby1sZXZlbC1u
dW1iZXItZm9ybWF0OmJ1bGxldDsNCgltc28tbGV2ZWwtdGV4dDrvgqc7DQoJbXNvLWxldmVsLXRh
Yi1zdG9wOjEuNWluOw0KCW1zby1sZXZlbC1udW1iZXItcG9zaXRpb246bGVmdDsNCgl0ZXh0LWlu
ZGVudDotLjI1aW47DQoJbXNvLWFuc2ktZm9udC1zaXplOjEwLjBwdDsNCglmb250LWZhbWlseTpX
aW5nZGluZ3M7fQ0KQGxpc3QgbDA6bGV2ZWw0DQoJe21zby1sZXZlbC1udW1iZXItZm9ybWF0OmJ1
bGxldDsNCgltc28tbGV2ZWwtdGV4dDrvgqc7DQoJbXNvLWxldmVsLXRhYi1zdG9wOjIuMGluOw0K
CW1zby1sZXZlbC1udW1iZXItcG9zaXRpb246bGVmdDsNCgl0ZXh0LWluZGVudDotLjI1aW47DQoJ
bXNvLWFuc2ktZm9udC1zaXplOjEwLjBwdDsNCglmb250LWZhbWlseTpXaW5nZGluZ3M7fQ0KQGxp
c3QgbDA6bGV2ZWw1DQoJe21zby1sZXZlbC1udW1iZXItZm9ybWF0OmJ1bGxldDsNCgltc28tbGV2
ZWwtdGV4dDrvgqc7DQoJbXNvLWxldmVsLXRhYi1zdG9wOjIuNWluOw0KCW1zby1sZXZlbC1udW1i
ZXItcG9zaXRpb246bGVmdDsNCgl0ZXh0LWluZGVudDotLjI1aW47DQoJbXNvLWFuc2ktZm9udC1z
aXplOjEwLjBwdDsNCglmb250LWZhbWlseTpXaW5nZGluZ3M7fQ0KQGxpc3QgbDA6bGV2ZWw2DQoJ
e21zby1sZXZlbC1udW1iZXItZm9ybWF0OmJ1bGxldDsNCgltc28tbGV2ZWwtdGV4dDrvgqc7DQoJ
bXNvLWxldmVsLXRhYi1zdG9wOjMuMGluOw0KCW1zby1sZXZlbC1udW1iZXItcG9zaXRpb246bGVm
dDsNCgl0ZXh0LWluZGVudDotLjI1aW47DQoJbXNvLWFuc2ktZm9udC1zaXplOjEwLjBwdDsNCglm
b250LWZhbWlseTpXaW5nZGluZ3M7fQ0KQGxpc3QgbDA6bGV2ZWw3DQoJe21zby1sZXZlbC1udW1i
ZXItZm9ybWF0OmJ1bGxldDsNCgltc28tbGV2ZWwtdGV4dDrvgqc7DQoJbXNvLWxldmVsLXRhYi1z
dG9wOjMuNWluOw0KCW1zby1sZXZlbC1udW1iZXItcG9zaXRpb246bGVmdDsNCgl0ZXh0LWluZGVu
dDotLjI1aW47DQoJbXNvLWFuc2ktZm9udC1zaXplOjEwLjBwdDsNCglmb250LWZhbWlseTpXaW5n
ZGluZ3M7fQ0KQGxpc3QgbDA6bGV2ZWw4DQoJe21zby1sZXZlbC1udW1iZXItZm9ybWF0OmJ1bGxl
dDsNCgltc28tbGV2ZWwtdGV4dDrvgqc7DQoJbXNvLWxldmVsLXRhYi1zdG9wOjQuMGluOw0KCW1z
by1sZXZlbC1udW1iZXItcG9zaXRpb246bGVmdDsNCgl0ZXh0LWluZGVudDotLjI1aW47DQoJbXNv
LWFuc2ktZm9udC1zaXplOjEwLjBwdDsNCglmb250LWZhbWlseTpXaW5nZGluZ3M7fQ0KQGxpc3Qg
bDA6bGV2ZWw5DQoJe21zby1sZXZlbC1udW1iZXItZm9ybWF0OmJ1bGxldDsNCgltc28tbGV2ZWwt
dGV4dDrvgqc7DQoJbXNvLWxldmVsLXRhYi1zdG9wOjQuNWluOw0KCW1zby1sZXZlbC1udW1iZXIt
cG9zaXRpb246bGVmdDsNCgl0ZXh0LWluZGVudDotLjI1aW47DQoJbXNvLWFuc2ktZm9udC1zaXpl
OjEwLjBwdDsNCglmb250LWZhbWlseTpXaW5nZGluZ3M7fQ0KQGxpc3QgbDENCgl7bXNvLWxpc3Qt
aWQ6ODY4Njg1MDkxOw0KCW1zby1saXN0LXRlbXBsYXRlLWlkczo2NzY4NTU5MTQ7fQ0KQGxpc3Qg
bDE6bGV2ZWwxDQoJe21zby1sZXZlbC1udW1iZXItZm9ybWF0OmJ1bGxldDsNCgltc28tbGV2ZWwt
dGV4dDrvgrc7DQoJbXNvLWxldmVsLXRhYi1zdG9wOi41aW47DQoJbXNvLWxldmVsLW51bWJlci1w
b3NpdGlvbjpsZWZ0Ow0KCXRleHQtaW5kZW50Oi0uMjVpbjsNCgltc28tYW5zaS1mb250LXNpemU6
MTAuMHB0Ow0KCWZvbnQtZmFtaWx5OlN5bWJvbDt9DQpAbGlzdCBsMTpsZXZlbDINCgl7bXNvLWxl
dmVsLW51bWJlci1mb3JtYXQ6YnVsbGV0Ow0KCW1zby1sZXZlbC10ZXh0Om87DQoJbXNvLWxldmVs
LXRhYi1zdG9wOjEuMGluOw0KCW1zby1sZXZlbC1udW1iZXItcG9zaXRpb246bGVmdDsNCgl0ZXh0
LWluZGVudDotLjI1aW47DQoJbXNvLWFuc2ktZm9udC1zaXplOjEwLjBwdDsNCglmb250LWZhbWls
eToiQ291cmllciBOZXciOw0KCW1zby1iaWRpLWZvbnQtZmFtaWx5OiJUaW1lcyBOZXcgUm9tYW4i
O30NCkBsaXN0IGwxOmxldmVsMw0KCXttc28tbGV2ZWwtbnVtYmVyLWZvcm1hdDpidWxsZXQ7DQoJ
bXNvLWxldmVsLXRleHQ674KnOw0KCW1zby1sZXZlbC10YWItc3RvcDoxLjVpbjsNCgltc28tbGV2
ZWwtbnVtYmVyLXBvc2l0aW9uOmxlZnQ7DQoJdGV4dC1pbmRlbnQ6LS4yNWluOw0KCW1zby1hbnNp
LWZvbnQtc2l6ZToxMC4wcHQ7DQoJZm9udC1mYW1pbHk6V2luZ2RpbmdzO30NCkBsaXN0IGwxOmxl
dmVsNA0KCXttc28tbGV2ZWwtbnVtYmVyLWZvcm1hdDpidWxsZXQ7DQoJbXNvLWxldmVsLXRleHQ6
74KnOw0KCW1zby1sZXZlbC10YWItc3RvcDoyLjBpbjsNCgltc28tbGV2ZWwtbnVtYmVyLXBvc2l0
aW9uOmxlZnQ7DQoJdGV4dC1pbmRlbnQ6LS4yNWluOw0KCW1zby1hbnNpLWZvbnQtc2l6ZToxMC4w
cHQ7DQoJZm9udC1mYW1pbHk6V2luZ2RpbmdzO30NCkBsaXN0IGwxOmxldmVsNQ0KCXttc28tbGV2
ZWwtbnVtYmVyLWZvcm1hdDpidWxsZXQ7DQoJbXNvLWxldmVsLXRleHQ674KnOw0KCW1zby1sZXZl
bC10YWItc3RvcDoyLjVpbjsNCgltc28tbGV2ZWwtbnVtYmVyLXBvc2l0aW9uOmxlZnQ7DQoJdGV4
dC1pbmRlbnQ6LS4yNWluOw0KCW1zby1hbnNpLWZvbnQtc2l6ZToxMC4wcHQ7DQoJZm9udC1mYW1p
bHk6V2luZ2RpbmdzO30NCkBsaXN0IGwxOmxldmVsNg0KCXttc28tbGV2ZWwtbnVtYmVyLWZvcm1h
dDpidWxsZXQ7DQoJbXNvLWxldmVsLXRleHQ674KnOw0KCW1zby1sZXZlbC10YWItc3RvcDozLjBp
bjsNCgltc28tbGV2ZWwtbnVtYmVyLXBvc2l0aW9uOmxlZnQ7DQoJdGV4dC1pbmRlbnQ6LS4yNWlu
Ow0KCW1zby1hbnNpLWZvbnQtc2l6ZToxMC4wcHQ7DQoJZm9udC1mYW1pbHk6V2luZ2RpbmdzO30N
CkBsaXN0IGwxOmxldmVsNw0KCXttc28tbGV2ZWwtbnVtYmVyLWZvcm1hdDpidWxsZXQ7DQoJbXNv
LWxldmVsLXRleHQ674KnOw0KCW1zby1sZXZlbC10YWItc3RvcDozLjVpbjsNCgltc28tbGV2ZWwt
bnVtYmVyLXBvc2l0aW9uOmxlZnQ7DQoJdGV4dC1pbmRlbnQ6LS4yNWluOw0KCW1zby1hbnNpLWZv
bnQtc2l6ZToxMC4wcHQ7DQoJZm9udC1mYW1pbHk6V2luZ2RpbmdzO30NCkBsaXN0IGwxOmxldmVs
OA0KCXttc28tbGV2ZWwtbnVtYmVyLWZvcm1hdDpidWxsZXQ7DQoJbXNvLWxldmVsLXRleHQ674Kn
Ow0KCW1zby1sZXZlbC10YWItc3RvcDo0LjBpbjsNCgltc28tbGV2ZWwtbnVtYmVyLXBvc2l0aW9u
OmxlZnQ7DQoJdGV4dC1pbmRlbnQ6LS4yNWluOw0KCW1zby1hbnNpLWZvbnQtc2l6ZToxMC4wcHQ7
DQoJZm9udC1mYW1pbHk6V2luZ2RpbmdzO30NCkBsaXN0IGwxOmxldmVsOQ0KCXttc28tbGV2ZWwt
bnVtYmVyLWZvcm1hdDpidWxsZXQ7DQoJbXNvLWxldmVsLXRleHQ674KnOw0KCW1zby1sZXZlbC10
YWItc3RvcDo0LjVpbjsNCgltc28tbGV2ZWwtbnVtYmVyLXBvc2l0aW9uOmxlZnQ7DQoJdGV4dC1p
bmRlbnQ6LS4yNWluOw0KCW1zby1hbnNpLWZvbnQtc2l6ZToxMC4wcHQ7DQoJZm9udC1mYW1pbHk6
V2luZ2RpbmdzO30NCm9sDQoJe21hcmdpbi1ib3R0b206MGluO30NCnVsDQoJe21hcmdpbi1ib3R0
b206MGluO30NCi0tPjwvc3R5bGU+PCEtLVtpZiBndGUgbXNvIDldPjx4bWw+DQo8bzpzaGFwZWRl
ZmF1bHRzIHY6ZXh0PSJlZGl0IiBzcGlkbWF4PSIxMDI2IiAvPg0KPC94bWw+PCFbZW5kaWZdLS0+
PCEtLVtpZiBndGUgbXNvIDldPjx4bWw+DQo8bzpzaGFwZWxheW91dCB2OmV4dD0iZWRpdCI+DQo8
bzppZG1hcCB2OmV4dD0iZWRpdCIgZGF0YT0iMSIgLz4NCjwvbzpzaGFwZWxheW91dD48L3htbD48
IVtlbmRpZl0tLT4NCjwvaGVhZD4NCjxib2R5IGxhbmc9IkVOLVVTIiBsaW5rPSIjMDU2M0MxIiB2
bGluaz0iIzk1NEY3MiI+DQo8ZGl2IGNsYXNzPSJXb3JkU2VjdGlvbjEiPg0KPHAgY2xhc3M9Ik1z
b05vcm1hbCI+SSBsaWtlIHRoZSB0aXRsZSBvZjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0
O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjojMUY0OTdE
Ij4gJm5ic3A7PC9zcGFuPuKAnGRpc3RyaWJ1dGVkIGtleWluZ+KAnSAoY2FzZSAxKSB2cyDigJxj
ZW50cmFsaXplZCBrZXlpbmfigJ0gKENhc2UgMikuDQo8bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+
TGluZGE8c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxp
YnJpJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6IzFGNDk3RCI+PG86cD48L286cD48L3NwYW4+PC9w
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PGEgbmFtZT0iX01haWxFbmRDb21wb3NlIj48c3BhbiBz
dHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNh
bnMtc2VyaWY7Y29sb3I6IzFGNDk3RCI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9hPjwvcD4N
CjxkaXY+DQo8ZGl2IHN0eWxlPSJib3JkZXI6bm9uZTtib3JkZXItdG9wOnNvbGlkICNFMUUxRTEg
MS4wcHQ7cGFkZGluZzozLjBwdCAwaW4gMGluIDBpbiI+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48
Yj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJp
JnF1b3Q7LHNhbnMtc2VyaWYiPkZyb206PC9zcGFuPjwvYj48c3BhbiBzdHlsZT0iZm9udC1zaXpl
OjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWYiPiBJMm5z
ZiBbbWFpbHRvOmkybnNmLWJvdW5jZXNAaWV0Zi5vcmddDQo8Yj5PbiBCZWhhbGYgT2YgPC9iPllv
YXYgTmlyPGJyPg0KPGI+U2VudDo8L2I+IFR1ZXNkYXksIE5vdmVtYmVyIDI3LCAyMDE4IDQ6Mzkg
UE08YnI+DQo8Yj5Ubzo8L2I+IEdhYnJpZWwgTG9wZXogJmx0O2dhYmlsbUB1bS5lcyZndDs8YnI+
DQo8Yj5DYzo8L2I+IGkybnNmQGlldGYub3JnOyBpcHNlY0BpZXRmLm9yZyBXRyAmbHQ7aXBzZWNA
aWV0Zi5vcmcmZ3Q7OyBQYXVsIFdvdXRlcnMgJmx0O3BhdWxAbm9oYXRzLmNhJmd0OzsgUmFmYSBN
YXJpbiBMb3BleiAmbHQ7cmFmYUB1bS5lcyZndDs8YnI+DQo8Yj5TdWJqZWN0OjwvYj4gUmU6IFtJ
Mm5zZl0gW0lQc2VjXSBSZXZpZXcgb2YgZHJhZnQtaWV0Zi1pMm5zZi1zZG4taXBzZWMtZmxvdy1w
cm90ZWN0aW9uLTAzIChTZWN0aW9uIDEpPG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8
L2Rpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCI+QSBjb3VwbGUgb2YgcmVtYXJrcyAod2l0aCBubyBoYXRzKTxvOnA+PC9v
OnA+PC9wPg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9w
Pg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+SWYgd2XigJlyZSBiaWtlc2hl
ZGRpbmcgdGhlIG5hbWVzLCBJIHRoaW5rIHRoZSBkaWZmZXJlbmNlIGlzIHRoYXQgaW4gb25lIGNh
c2UgdGhlIHR3byBOU0ZzIGdlbmVyYXRlIHRyYWZmaWMga2V5cyBiZXR3ZWVuIHRoZW1zZWx2ZXMs
IGFuZCBpbiB0aGUgb3RoZXIgaXQgaXMgdGhlIGNvbnRyb2xsZXIgdGhhdCBnZW5lcmF0ZXMgdGhl
IGtleXMgZm9yIHRoZW0uICZuYnNwO1NvIGhvdyBhYm91dCDigJxkaXN0cmlidXRlZCBrZXlpbmfi
gJ0NCiB2cyDigJxjZW50cmFsaXplZCBrZXlpbmfigJ0sIG9yIHBlcmhhcHMg4oCcYXV0b21hdGlj
IGtleWluZ+KAnSB2cyDigJxTRE4ga2V5aW5n4oCdLjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8
ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4N
CjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2
Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPkFsc28sIEkgaGF2ZSBiZWVuIGFza2VkIGJ5
IHNvbWVvbmUgbm90IG9uIHRoaXMgbGlzdCB3aGV0aGVyIG91ciB3b3JrIGNvdmVycyB0aGUgcm9h
ZCB3YXJyaW9yIHVzZSBjYXNlLiBJIHNhaWQgaXQgZGlkbuKAmXQgYW5kIHdvbmRlcmVkIHdoeS4g
U28gSSBnb3QgdGhlc2UgcG9pbnRzOjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHVs
IHR5cGU9ImRpc2MiPg0KPGxpIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRv
cC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0bzttc28tbGlzdDpsMSBsZXZlbDEg
bGZvMSI+DQpSb2FkIHdhcnJpb3JzIGFyZSBudW1lcm91cyBhbmQgbm90IHdoZXJlIHRoZSBhZG1p
bmlzdHJhdG9yIGNhbiBjb25maWd1cmUgdGhlbSBtYW51YWxseS48bzpwPjwvbzpwPjwvbGk+PGxp
IGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFy
Z2luLWJvdHRvbS1hbHQ6YXV0bzttc28tbGlzdDpsMSBsZXZlbDEgbGZvMSI+DQpBZGRpdGlvbmFs
bHksIHRoZSBjb25maWd1cmF0aW9uIG9mIHdoYXQgbmV0d29ya3MsIGdhdGV3YXlzIChOU0ZzKSwg
YW5kIHJlc291cmNlcyBhIHJvYWQgd2FycmlvciBtYXkgYWNjZXNzIChpbiBJUHNlYyB0ZXJtcywg
dGhlIFNQRCBhbmQgUEFEKSBjaGFuZ2Ugb2Z0ZW4uPG86cD48L286cD48L2xpPjxsaSBjbGFzcz0i
TXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0
b20tYWx0OmF1dG87bXNvLWxpc3Q6bDEgbGV2ZWwxIGxmbzEiPg0KQmVjYXVzZSBvZiB0aGUgYWJv
dmUsIHNvbWUgYXV0b21hdGljIG1ldGhvZCBvZiBjb25maWd1cmluZyBTUEQgYW5kIFBBRCBpcyBu
ZWVkZWQuPG86cD48L286cD48L2xpPjxsaSBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1h
cmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG87bXNvLWxpc3Q6bDEg
bGV2ZWwxIGxmbzEiPg0KVGhlcmUgaXMgYWxzbyB0aGUgaXNzdWUgb2YgbXVsdGlwbGUgVlBOIGdh
dGV3YXlzIGNvdmVyaW5nIHNpbWlsYXIgZG9tYWlucywgYW5kIFZQTiBnYXRld2F5cyBiZWluZyBv
dmVybG9hZGVkIG9yIGRvd24gZm9yIG1haW50ZW5hbmNlLCBhcyB3ZWxsIGFzIG1hbGZ1bmN0aW9u
cyBpbiB0aGUgbmV0d29yayBiZWhpbmQgdGhvc2UgVlBOIGdhdGV3YXlzLiBTbyB0aGUgZGVjaXNp
b24gb24gd2hpY2ggZ2F0ZXdheSBhIHJvYWQgd2FycmlvciBzaG91bGQgdXNlDQogdG8gYWNjZXNz
IGEgcGFydGljdWxhciByZXNvdXJjZSBpcyBhbHNvIGEgbmF0dXJhbCBxdWVzdGlvbiB0byBhc2sg
YW4gU0ROIGNvbnRyb2xsZXIuPG86cD48L286cD48L2xpPjwvdWw+DQo8ZGl2Pg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPGRpdj4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiPlNpbmNlIEkgdXNlZCB0byB3b3JrIGZvciBhIFZQTiB2ZW5k
b3IsIEkgY2FuIHRlbGwgeW91IHdoYXQgb3VyIHByb2R1Y3QgZGlkOjxvOnA+PC9vOnA+PC9wPg0K
PC9kaXY+DQo8ZGl2Pg0KPHVsIHR5cGU9ImRpc2MiPg0KPGxpIGNsYXNzPSJNc29Ob3JtYWwiIHN0
eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0bztt
c28tbGlzdDpsMCBsZXZlbDEgbGZvMiI+DQpUaGUgY3VycmVudCBjb25maWd1cmF0aW9uIHdhcyBm
b3JtYXR0ZWQgKGF1dG9tYXRpY2FsbHkgYnkgYSBtYW5hZ2VtZW50IGZ1bmN0aW9uKSBhcyBhIHRl
eHQgZmlsZSB0aGF0IHRoZSByb2FkIHdhcnJpb3IgZG93bmxvYWRlZCB0aHJvdWdoIHRoZSBWUE4g
Z2F0ZXdheSAodGhlIGdhdGV3YXkgZG91YmxlZCBhcyBhIHNlcnZlciBzZXJ2aW5nIHRoaXMgb25l
IGZpbGUpPG86cD48L286cD48L2xpPjxsaSBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1h
cmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG87bXNvLWxpc3Q6bDAg
bGV2ZWwxIGxmbzIiPg0KVGhlIHByb3BlciBnYXRld2F5IHRvIGNvbm5lY3QgdG8gd2FzIGRldGVy
bWluZWQgYnkgcGluZ2luZyBhbGwgZ2F0ZXdheXMgdGhhdCB3ZXJlIHBvc3NpYmxlIGFjY29yZGlu
ZyB0byB0aGUgY29uZmlndXJhdGlvbiBmaWxlLjxvOnA+PC9vOnA+PC9saT48bGkgY2xhc3M9Ik1z
b05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9t
LWFsdDphdXRvO21zby1saXN0OmwwIGxldmVsMSBsZm8yIj4NClRoaXMgZGlkIG5vdCBhY2NvdW50
IGZvciBhbnkgaW50ZXJuYWwgbmV0d29ya2luZyBpc3N1ZXMuPG86cD48L286cD48L2xpPjwvdWw+
DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rp
dj4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPkkgZG9u4oCZdCBrbm93IGlm
IHRoaXMgc2hvdWxkIGJlIHBhcnQgb2YgKnRoaXMqIGVmZm9ydCwgYnV0IHRoZXJlIGlzIGEgdXNl
IGNhc2UgZm9yIHJvYWQgd2FycmlvciBTRE4uPG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRp
dj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPllvYXY8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPC9k
aXY+DQo8L2JvZHk+DQo8L2h0bWw+DQo=

--_000_4A95BA014132FF49AE685FAB4B9F17F66B1F6237SJCEML521MBBchi_--


From nobody Wed Dec  5 13:48:42 2018
Return-Path: <linda.dunbar@huawei.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 3A6BD130E95; Wed,  5 Dec 2018 13:48:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-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 dU2xN4kZeImM; Wed,  5 Dec 2018 13:48:38 -0800 (PST)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (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 6D9D8130DFF; Wed,  5 Dec 2018 13:48:38 -0800 (PST)
Received: from lhreml701-cah.china.huawei.com (unknown [172.18.7.108]) by Forcepoint Email with ESMTP id 51A4CFA0FC6A9; Wed,  5 Dec 2018 21:48:34 +0000 (GMT)
Received: from SJCEML702-CHM.china.huawei.com (10.208.112.38) by lhreml701-cah.china.huawei.com (10.201.108.42) with Microsoft SMTP Server (TLS) id 14.3.408.0; Wed, 5 Dec 2018 21:48:35 +0000
Received: from SJCEML521-MBB.china.huawei.com ([169.254.6.33]) by SJCEML702-CHM.china.huawei.com ([169.254.4.100]) with mapi id 14.03.0415.000;  Wed, 5 Dec 2018 13:48:34 -0800
From: Linda Dunbar <linda.dunbar@huawei.com>
To: "draft-ietf-i2nsf-sdn-ipsec-flow-protection@ietf.org" <draft-ietf-i2nsf-sdn-ipsec-flow-protection@ietf.org>, "i2nsf@ietf.org" <i2nsf@ietf.org>
Thread-Topic: Typo? in Appendix A of draft-i2nsf-sdn-ipsec-flow-protection? 
Thread-Index: AdSMxIk0k2a5BkmlTXuDMYdzdX4TBQ==
Date: Wed, 5 Dec 2018 21:48:34 +0000
Message-ID: <4A95BA014132FF49AE685FAB4B9F17F66B1F627A@SJCEML521-MBB.china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.192.11.90]
Content-Type: multipart/alternative; boundary="_000_4A95BA014132FF49AE685FAB4B9F17F66B1F627ASJCEML521MBBchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2nsf/HxzI5kzpp75xE-dtGEdbHZ-HcwU>
Subject: [I2nsf] Typo? in Appendix A of draft-i2nsf-sdn-ipsec-flow-protection?
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, 05 Dec 2018 21:48:40 -0000

--_000_4A95BA014132FF49AE685FAB4B9F17F66B1F627ASJCEML521MBBchi_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable


Gabriel and Rafa,

On Page 36 (Appendix A), you have the following :
grouping port-range {
description "Port range grouping";
leaf start { type inet:port-number; description "Start IP address"; }
leaf end { type inet:port-number; description "End IP address"; }
}

Do you mean "Start Port number" and "End Port Number"?


Thanks, Linda

--_000_4A95BA014132FF49AE685FAB4B9F17F66B1F627ASJCEML521MBBchi_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Courier;
	panose-1:2 7 4 9 2 2 5 2 4 4;}
@font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:"\@SimSun";
	panose-1:2 1 6 0 3 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:#0563C1;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:#954F72;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:"Calibri",sans-serif;
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"#0563C1" vlink=3D"#954F72">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:7.5pt;font-family:Courier">=
<o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Arial&quot;,sans-se=
rif">Gabriel and Rafa,
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Arial&quot;,sans-se=
rif"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Arial&quot;,sans-se=
rif">On Page 36 (Appendix A), you have the following :<o:p></o:p></span></p=
>
<p class=3D"MsoNormal" style=3D"text-autospace:none"><span style=3D"font-fa=
mily:&quot;Arial&quot;,sans-serif">grouping port-range {<o:p></o:p></span><=
/p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in;text-autospace:none"><span=
 style=3D"font-family:&quot;Arial&quot;,sans-serif">description &quot;Port =
range grouping&quot;;<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in;text-autospace:none"><span=
 style=3D"font-family:&quot;Arial&quot;,sans-serif">leaf start { type inet:=
port-number; description &quot;Start IP address&quot;; }<o:p></o:p></span><=
/p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in;text-autospace:none"><span=
 style=3D"font-family:&quot;Arial&quot;,sans-serif">leaf end { type inet:po=
rt-number; description &quot;End IP address&quot;; }<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Arial&quot;,sans-se=
rif">}</span><span style=3D"font-family:&quot;Arial&quot;,sans-serif"><o:p>=
</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Arial&quot;,sans-se=
rif"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Arial&quot;,sans-se=
rif">Do you mean &#8220;Start Port number&#8221; and &#8220;End Port Number=
&#8221;?
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Arial&quot;,sans-se=
rif"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Arial&quot;,sans-se=
rif"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Arial&quot;,sans-se=
rif">Thanks, Linda <o:p>
</o:p></span></p>
</div>
</body>
</html>

--_000_4A95BA014132FF49AE685FAB4B9F17F66B1F627ASJCEML521MBBchi_--


From nobody Wed Dec  5 14:31:47 2018
Return-Path: <linda.dunbar@huawei.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 D82C6130E14 for <i2nsf@ietfa.amsl.com>; Wed,  5 Dec 2018 14:31:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-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 TI-rR2bMOZfo for <i2nsf@ietfa.amsl.com>; Wed,  5 Dec 2018 14:31:42 -0800 (PST)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (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 6861712F1AC for <i2nsf@ietf.org>; Wed,  5 Dec 2018 14:31:42 -0800 (PST)
Received: from lhreml701-cah.china.huawei.com (unknown [172.18.7.108]) by Forcepoint Email with ESMTP id 4998DB2F7AB09 for <i2nsf@ietf.org>; Wed,  5 Dec 2018 22:31:37 +0000 (GMT)
Received: from SJCEML703-CHM.china.huawei.com (10.208.112.39) by lhreml701-cah.china.huawei.com (10.201.108.42) with Microsoft SMTP Server (TLS) id 14.3.408.0; Wed, 5 Dec 2018 22:31:38 +0000
Received: from SJCEML521-MBB.china.huawei.com ([169.254.6.33]) by SJCEML703-CHM.china.huawei.com ([169.254.5.160]) with mapi id 14.03.0415.000;  Wed, 5 Dec 2018 14:31:32 -0800
From: Linda Dunbar <linda.dunbar@huawei.com>
To: "i2nsf@ietf.org" <i2nsf@ietf.org>
Thread-Topic: Call for WG Adoption on NSF Monitoring Draft
Thread-Index: AdSM6WC8tNKqbgUPR0unKhFeH73oNw==
Date: Wed, 5 Dec 2018 22:31:32 +0000
Message-ID: <4A95BA014132FF49AE685FAB4B9F17F66B1F6399@SJCEML521-MBB.china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.192.11.90]
Content-Type: multipart/alternative; boundary="_000_4A95BA014132FF49AE685FAB4B9F17F66B1F6399SJCEML521MBBchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2nsf/SZLTgE-O2uPuzMILP3ammeSuyVw>
Subject: [I2nsf] Call for WG Adoption on NSF Monitoring 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: Wed, 05 Dec 2018 22:31:45 -0000

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

VGhpcyBpcyB0aGUgc3RhcnQgb2YgYSB0d28gd2Vla3MgY2FsbCBmb3IgaW5wdXQgb24gdGhlIFdH
IGFkb3B0aW9uIG9mIHRoZSBkb2N1bWVudDogaHR0cHM6Ly90b29scy5pZXRmLm9yZy9odG1sL2Ry
YWZ0LWhvbmctaTJuc2YtbnNmLW1vbml0b3JpbmctZGF0YS1tb2RlbC0wNg0KDQpUaGFua3MgZm9y
IHRoZSBhdXRob3JzIG9mIHRoZSB0d28gSTJOU0YgTW9uaXRvcmluZyBkcmFmdHMgdGFraW5nIGFj
dGlvbnMgb2YgbWVyZ2luZyB0aGUgY29udGVudC4NCldlIG5lZWQgbW9yZSBvZiB0aG9zZSBhY3Rp
b25zLiBBcyBvZiBub3cgd2UgaGF2ZSA4IFdHIGRyYWZ0cy4gV2UgbmVlZCB0byBmaW5pc2ggdGhl
bSBuZXh0IGZldyBtb250aHMuDQoNCkJlYXIgaW4gbWluZCB0aGF0IFdHIGFkb3B0aW9uIGRvZXNu
4oCZdCBtZWFuIHRoZSBkcmFmdCBpcyByZWFkeSwgb25seSBtZWFucyB0aGF0IFdHIHdpbGwgd29y
ayB0b2dldGhlciBvbiB0aGUgZHJhZnQgKGluc3RlYWQgb2YgaW5kaXZpZHVhbHMpLg0KDQpQbGVh
c2UgcHJvdmlkZSBmZWVkYmFjayB0byB0aGUgbGlzdC9jaGFpcnMgaWYgeW91IGJlbGlldmUgdGhh
dCB0aGlzIGRvY3VtZW50IHNob3VsZCBiZSBhZG9wdGVkIGFzIGEgV0cgZG9jdW1lbnQuDQoNClRo
YW5rcywNCg0KTGluZGEgJiBZb2F2DQoNCkZyb206IE1yLiBKYWVob29uIFBhdWwgSmVvbmcgW21h
aWx0bzpqYWVob29uLnBhdWxAZ21haWwuY29tXQ0KU2VudDogVGh1cnNkYXksIE5vdmVtYmVyIDE1
LCAyMDE4IDY6MzUgUE0NClRvOiBMaW5kYSBEdW5iYXIgPGxpbmRhLmR1bmJhckBodWF3ZWkuY29t
PjsgWW9hdiBOaXIgPHluaXIuaWV0ZkBnbWFpbC5jb20+DQpDYzogaTJuc2ZAaWV0Zi5vcmc7IHNr
a3Vfc2VjdS1icmFpbl9hbGxAZ29vZ2xlZ3JvdXBzLmNvbTsgU2FuZ3dvbiBIeXVuIDxzd2h5dW43
N0BnbWFpbC5jb20+OyBNci4gSmFlaG9vbiBQYXVsIEplb25nIDxqYWVob29uLnBhdWxAZ21haWwu
Y29tPg0KU3ViamVjdDogUmVxdWVzdCBmb3IgV0cgQWRvcHRpb24gQ2FsbCBvbiBOU0YgTW9uaXRv
cmluZyBEcmFmdA0KDQpIaSBMaW5kYSBhbmQgWW9hdiwNCkFzIHdlIGRpc2N1c3NlZCB0aGUgbGFz
dCBCYW5na29rIG1lZXRpbmcsDQpJIGhhdmUgbWVyZ2VkIHRoZSB0d28gZHJhZnRzIG9mIEluZm9y
bWF0aW9uIE1vZGVsIGFuZCBEYXRhIE1vZGVsDQpmb3IgTlNGIE1vbml0b3JpbmcgaW50byBhIG5l
dyBkcmFmdCBjYWxsZWQgZHJhZnQtaG9uZy1pMm5zZi1uc2YtbW9uaXRvcmluZy1kYXRhLW1vZGVs
LTA2Og0KDQotIFR3byBJbmZvcm1hdGlvbiBhbmQgRGF0YSBNb2RlbCBEcmFmdHMNCiAuIGRyYWZ0
LXpoYW5nLWkybnNmLWluZm8tbW9kZWwtbW9uaXRvcmluZy0wNw0KIC4gZHJhZnQtaG9uZy1pMm5z
Zi1uc2YtbW9uaXRvcmluZy1kYXRhLW1vZGVsLTA1DQoNCi0gQSBNZXJnZWQgRGF0YSBNb2RlbCBE
cmFmdA0KIC4gZHJhZnQtaG9uZy1pMm5zZi1uc2YtbW9uaXRvcmluZy1kYXRhLW1vZGVsLTA2DQog
LiBodHRwczovL3Rvb2xzLmlldGYub3JnL2h0bWwvZHJhZnQtaG9uZy1pMm5zZi1uc2YtbW9uaXRv
cmluZy1kYXRhLW1vZGVsLTA2DQoNClRoZSBOU0YgbW9uaXRvcmluZyBpcyB2ZXJ5IGltcG9ydGFu
dCB0byBtYW5hZ2UgdGhlIEkyTlNGIHNlY3VyaXR5IHNlcnZpY2Ugc3lzdGVtDQppbiBhIHJlbGlh
YmxlIGFuZCBzY2FsYWJsZSBmYXNoaW9uLg0KDQpDb3VsZCB5b3Ugc3RhcnQgYSBXRyBhZG9wdGlv
biBjYWxsIGZvciB0aGlzIGRyYWZ0Pw0KDQpUaGFua3MuDQoNCkJlc3QgUmVnYXJkcywNClBhdWwN
Ci0tDQo9PT09PT09PT09PT09PT09PT09PT09PT09PT0NCk1yLiBKYWVob29uIChQYXVsKSBKZW9u
ZywgUGguRC4NCkFzc29jaWF0ZSBQcm9mZXNzb3INCkRlcGFydG1lbnQgb2YgU29mdHdhcmUNClN1
bmdreXVua3dhbiBVbml2ZXJzaXR5DQpPZmZpY2U6ICs4Mi0zMS0yOTktNDk1Nw0KRW1haWw6IGph
ZWhvb24ucGF1bEBnbWFpbC5jb208bWFpbHRvOmphZWhvb24ucGF1bEBnbWFpbC5jb20+LCBwYXVs
amVvbmdAc2trdS5lZHU8bWFpbHRvOnBhdWxqZW9uZ0Bza2t1LmVkdT4NClBlcnNvbmFsIEhvbWVw
YWdlOiBodHRwOi8vaW90bGFiLnNra3UuZWR1L3Blb3BsZS1qYWVob29uLWplb25nLnBocDxodHRw
Oi8vY3BzbGFiLnNra3UuZWR1L3Blb3BsZS1qYWVob29uLWplb25nLnBocD4NCg==

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

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTUgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
U2ltU3VuOw0KCXBhbm9zZS0xOjIgMSA2IDAgMyAxIDEgMSAxIDE7fQ0KQGZvbnQtZmFjZQ0KCXtm
b250LWZhbWlseToiQ2FtYnJpYSBNYXRoIjsNCglwYW5vc2UtMToyIDQgNSAzIDUgNCA2IDMgMiA0
O30NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6Q2FsaWJyaTsNCglwYW5vc2UtMToyIDE1IDUg
MiAyIDIgNCAzIDIgNDt9DQpAZm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5OiJcQFNpbVN1biI7DQoJ
cGFub3NlLTE6MiAxIDYgMCAzIDEgMSAxIDEgMTt9DQovKiBTdHlsZSBEZWZpbml0aW9ucyAqLw0K
cC5Nc29Ob3JtYWwsIGxpLk1zb05vcm1hbCwgZGl2Lk1zb05vcm1hbA0KCXttYXJnaW46MGluOw0K
CW1hcmdpbi1ib3R0b206LjAwMDFwdDsNCglmb250LXNpemU6MTIuMHB0Ow0KCWZvbnQtZmFtaWx5
OiJUaW1lcyBOZXcgUm9tYW4iLHNlcmlmO30NCmE6bGluaywgc3Bhbi5Nc29IeXBlcmxpbmsNCgl7
bXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0KCWNvbG9yOmJsdWU7DQoJdGV4dC1kZWNvcmF0aW9uOnVu
ZGVybGluZTt9DQphOnZpc2l0ZWQsIHNwYW4uTXNvSHlwZXJsaW5rRm9sbG93ZWQNCgl7bXNvLXN0
eWxlLXByaW9yaXR5Ojk5Ow0KCWNvbG9yOnB1cnBsZTsNCgl0ZXh0LWRlY29yYXRpb246dW5kZXJs
aW5lO30NCnNwYW4uRW1haWxTdHlsZTE3DQoJe21zby1zdHlsZS10eXBlOnBlcnNvbmFsLXJlcGx5
Ow0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIixzYW5zLXNlcmlmOw0KCWNvbG9yOiMxRjQ5N0Q7fQ0K
Lk1zb0NocERlZmF1bHQNCgl7bXNvLXN0eWxlLXR5cGU6ZXhwb3J0LW9ubHk7DQoJZm9udC1mYW1p
bHk6IkNhbGlicmkiLHNhbnMtc2VyaWY7fQ0KQHBhZ2UgV29yZFNlY3Rpb24xDQoJe3NpemU6OC41
aW4gMTEuMGluOw0KCW1hcmdpbjoxLjBpbiAxLjBpbiAxLjBpbiAxLjBpbjt9DQpkaXYuV29yZFNl
Y3Rpb24xDQoJe3BhZ2U6V29yZFNlY3Rpb24xO30NCi0tPjwvc3R5bGU+PCEtLVtpZiBndGUgbXNv
IDldPjx4bWw+DQo8bzpzaGFwZWRlZmF1bHRzIHY6ZXh0PSJlZGl0IiBzcGlkbWF4PSIxMDI2IiAv
Pg0KPC94bWw+PCFbZW5kaWZdLS0+PCEtLVtpZiBndGUgbXNvIDldPjx4bWw+DQo8bzpzaGFwZWxh
eW91dCB2OmV4dD0iZWRpdCI+DQo8bzppZG1hcCB2OmV4dD0iZWRpdCIgZGF0YT0iMSIgLz4NCjwv
bzpzaGFwZWxheW91dD48L3htbD48IVtlbmRpZl0tLT4NCjwvaGVhZD4NCjxib2R5IGxhbmc9IkVO
LVVTIiBsaW5rPSJibHVlIiB2bGluaz0icHVycGxlIj4NCjxkaXYgY2xhc3M9IldvcmRTZWN0aW9u
MSI+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtm
b250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6IzFGNDk3RCI+
VGhpcyBpcyB0aGUgc3RhcnQgb2YgYSB0d28gd2Vla3MgY2FsbCBmb3IgaW5wdXQgb24gdGhlIFdH
IGFkb3B0aW9uIG9mIHRoZSBkb2N1bWVudDoNCjwvc3Bhbj48YSBocmVmPSJodHRwczovL3Rvb2xz
LmlldGYub3JnL2h0bWwvZHJhZnQtaG9uZy1pMm5zZi1uc2YtbW9uaXRvcmluZy1kYXRhLW1vZGVs
LTA2Ij5odHRwczovL3Rvb2xzLmlldGYub3JnL2h0bWwvZHJhZnQtaG9uZy1pMm5zZi1uc2YtbW9u
aXRvcmluZy1kYXRhLW1vZGVsLTA2PC9hPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2Zv
bnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjojMUY0OTdEIj48
bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0i
Zm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2Vy
aWY7Y29sb3I6IzFGNDk3RCI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1
b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOiMxRjQ5N0QiPlRoYW5rcyBmb3IgdGhl
IGF1dGhvcnMgb2YgdGhlIHR3byBJMk5TRiBNb25pdG9yaW5nIGRyYWZ0cyB0YWtpbmcgYWN0aW9u
cyBvZiBtZXJnaW5nIHRoZSBjb250ZW50Lg0KPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6
JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOiMxRjQ5N0QiPldlIG5lZWQgbW9y
ZSBvZiB0aG9zZSBhY3Rpb25zLiBBcyBvZiBub3cgd2UgaGF2ZSA4IFdHIGRyYWZ0cy4gV2UgbmVl
ZCB0byBmaW5pc2ggdGhlbSBuZXh0IGZldyBtb250aHMuDQo8bzpwPjwvbzpwPjwvc3Bhbj48L3A+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250
LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6IzFGNDk3RCI+PG86
cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5
bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5z
LXNlcmlmO2NvbG9yOiMxRjQ5N0QiPkJlYXIgaW4gbWluZCB0aGF0IFdHIGFkb3B0aW9uIGRvZXNu
4oCZdCBtZWFuIHRoZSBkcmFmdCBpcyByZWFkeSwgb25seSBtZWFucyB0aGF0IFdHIHdpbGwgd29y
ayB0b2dldGhlciBvbiB0aGUgZHJhZnQgKGluc3RlYWQgb2YgaW5kaXZpZHVhbHMpLg0KPG86cD48
L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQt
c2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmO2Nv
bG9yOiMxRjQ5N0QiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29O
b3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0Nh
bGlicmkmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjojMUY0OTdEIj5QbGVhc2UgcHJvdmlkZSBmZWVk
YmFjayB0byB0aGUgbGlzdC9jaGFpcnMgaWYgeW91IGJlbGlldmUgdGhhdCB0aGlzIGRvY3VtZW50
IHNob3VsZCBiZSBhZG9wdGVkIGFzIGEgV0cgZG9jdW1lbnQuPG86cD48L286cD48L3NwYW4+PC9w
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9u
dC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOiMxRjQ5N0QiPjxv
OnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0
eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fu
cy1zZXJpZjtjb2xvcjojMUY0OTdEIj5UaGFua3MsDQo8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZh
bWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6IzFGNDk3RCI+PG86cD4m
bmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9
ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNl
cmlmO2NvbG9yOiMxRjQ5N0QiPkxpbmRhICZhbXA7IFlvYXY8bzpwPjwvbzpwPjwvc3Bhbj48L3A+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250
LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6IzFGNDk3RCI+PG86
cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PGEgbmFtZT0iX01haWxF
bmRDb21wb3NlIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVv
dDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6IzFGNDk3RCI+PG86cD4mbmJzcDs8L286
cD48L3NwYW4+PC9hPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxiPjxzcGFuIHN0eWxlPSJm
b250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJp
ZiI+RnJvbTo8L3NwYW4+PC9iPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFt
aWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZiI+IE1yLiBKYWVob29uIFBhdWwgSmVv
bmcgW21haWx0bzpqYWVob29uLnBhdWxAZ21haWwuY29tXQ0KPGJyPg0KPGI+U2VudDo8L2I+IFRo
dXJzZGF5LCBOb3ZlbWJlciAxNSwgMjAxOCA2OjM1IFBNPGJyPg0KPGI+VG86PC9iPiBMaW5kYSBE
dW5iYXIgJmx0O2xpbmRhLmR1bmJhckBodWF3ZWkuY29tJmd0OzsgWW9hdiBOaXIgJmx0O3luaXIu
aWV0ZkBnbWFpbC5jb20mZ3Q7PGJyPg0KPGI+Q2M6PC9iPiBpMm5zZkBpZXRmLm9yZzsgc2trdV9z
ZWN1LWJyYWluX2FsbEBnb29nbGVncm91cHMuY29tOyBTYW5nd29uIEh5dW4gJmx0O3N3aHl1bjc3
QGdtYWlsLmNvbSZndDs7IE1yLiBKYWVob29uIFBhdWwgSmVvbmcgJmx0O2phZWhvb24ucGF1bEBn
bWFpbC5jb20mZ3Q7PGJyPg0KPGI+U3ViamVjdDo8L2I+IFJlcXVlc3QgZm9yIFdHIEFkb3B0aW9u
IENhbGwgb24gTlNGIE1vbml0b3JpbmcgRHJhZnQ8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxkaXY+DQo8ZGl2Pg0KPGRp
dj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPkhpIExpbmRhIGFuZCBZb2F2LDxvOnA+PC9vOnA+PC9w
Pg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+QXMgd2UgZGlzY3Vzc2VkIHRo
ZSBsYXN0IEJhbmdrb2sgbWVldGluZyw8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiPkkgaGF2ZSBtZXJnZWQgdGhlIHR3byBkcmFmdHMgb2YgSW5mb3Jt
YXRpb24gTW9kZWwgYW5kIERhdGEgTW9kZWw8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiPmZvciBOU0YgTW9uaXRvcmluZyBpbnRvIGEgbmV3IGRyYWZ0
IGNhbGxlZCBkcmFmdC1ob25nLWkybnNmLW5zZi1tb25pdG9yaW5nLWRhdGEtbW9kZWwtMDY6PG86
cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZu
YnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPi0gVHdv
IEluZm9ybWF0aW9uIGFuZCBEYXRhIE1vZGVsIERyYWZ0czxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+
DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+Jm5ic3A7LiBkcmFmdC16aGFuZy1pMm5zZi1p
bmZvLW1vZGVsLW1vbml0b3JpbmctMDcmbmJzcDs8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRp
dj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPiZuYnNwOy4gZHJhZnQtaG9uZy1pMm5zZi1uc2YtbW9u
aXRvcmluZy1kYXRhLW1vZGVsLTA1PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiPi0gQSBNZXJnZWQgRGF0YSBNb2RlbCBEcmFmdCZuYnNwOzxvOnA+
PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+Jm5ic3A7LiBk
cmFmdC1ob25nLWkybnNmLW5zZi1tb25pdG9yaW5nLWRhdGEtbW9kZWwtMDY8bzpwPjwvbzpwPjwv
cD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPiZuYnNwOy4gPGEgaHJlZj0i
aHR0cHM6Ly90b29scy5pZXRmLm9yZy9odG1sL2RyYWZ0LWhvbmctaTJuc2YtbnNmLW1vbml0b3Jp
bmctZGF0YS1tb2RlbC0wNiI+DQpodHRwczovL3Rvb2xzLmlldGYub3JnL2h0bWwvZHJhZnQtaG9u
Zy1pMm5zZi1uc2YtbW9uaXRvcmluZy1kYXRhLW1vZGVsLTA2PC9hPjxvOnA+PC9vOnA+PC9wPg0K
PC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+
DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5UaGUgTlNGIG1vbml0b3Jpbmcg
aXMgdmVyeSBpbXBvcnRhbnQgdG8gbWFuYWdlIHRoZSBJMk5TRiBzZWN1cml0eSBzZXJ2aWNlIHN5
c3RlbTxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+
aW4gYSByZWxpYWJsZSBhbmQgc2NhbGFibGUgZmFzaGlvbi48bzpwPjwvbzpwPjwvcD4NCjwvZGl2
Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9k
aXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+Q291bGQgeW91IHN0YXJ0IGEgV0cgYWRv
cHRpb24gY2FsbCBmb3IgdGhpcyBkcmFmdD88bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+VGhhbmtzLjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8
ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4N
CjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5CZXN0IFJlZ2FyZHMsPG86cD48L286cD48L3A+
DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5QYXVsPG86cD48L286cD48L3A+
DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj4tLSZuYnNwOzxvOnA+PC9vOnA+
PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPGRpdj4NCjxkaXY+DQo8ZGl2Pg0KPGRpdj4NCjxkaXY+DQo8
ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPj09PT09PT09PT09PT09PT09PT09PT09
PT09PTxicj4NCk1yLiBKYWVob29uIChQYXVsKSBKZW9uZywgUGguRC48YnI+DQpBc3NvY2lhdGUg
UHJvZmVzc29yPGJyPg0KRGVwYXJ0bWVudCBvZiBTb2Z0d2FyZTxicj4NClN1bmdreXVua3dhbiBV
bml2ZXJzaXR5PGJyPg0KT2ZmaWNlOiAmIzQzOzgyLTMxLTI5OS00OTU3PGJyPg0KRW1haWw6IDxh
IGhyZWY9Im1haWx0bzpqYWVob29uLnBhdWxAZ21haWwuY29tIiB0YXJnZXQ9Il9ibGFuayI+amFl
aG9vbi5wYXVsQGdtYWlsLmNvbTwvYT4sJm5ic3A7PGEgaHJlZj0ibWFpbHRvOnBhdWxqZW9uZ0Bz
a2t1LmVkdSIgdGFyZ2V0PSJfYmxhbmsiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6OS41cHQiPnBh
dWxqZW9uZ0Bza2t1LmVkdTwvc3Bhbj48L2E+PGJyPg0KUGVyc29uYWwgSG9tZXBhZ2U6IDxhIGhy
ZWY9Imh0dHA6Ly9jcHNsYWIuc2trdS5lZHUvcGVvcGxlLWphZWhvb24tamVvbmcucGhwIiB0YXJn
ZXQ9Il9ibGFuayI+DQpodHRwOi8vaW90bGFiLnNra3UuZWR1L3Blb3BsZS1qYWVob29uLWplb25n
LnBocDwvYT48bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0K
PC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8
L2JvZHk+DQo8L2h0bWw+DQo=

--_000_4A95BA014132FF49AE685FAB4B9F17F66B1F6399SJCEML521MBBchi_--


From nobody Wed Dec  5 15:13:10 2018
Return-Path: <gabilm@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 F39A7130E14; Wed,  5 Dec 2018 15:13:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_PASS=-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 XQSaHa3V7G2t; Wed,  5 Dec 2018 15:13:06 -0800 (PST)
Received: from xenon44.um.es (xenon44.um.es [IPv6:2001:720:1710:601::44]) by ietfa.amsl.com (Postfix) with ESMTP id 1E970130DC1; Wed,  5 Dec 2018 15:13:06 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by xenon44.um.es (Postfix) with ESMTP id 3940E2053E; Thu,  6 Dec 2018 00:13:01 +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 2m0FNA_cDd2m; Thu,  6 Dec 2018 00:13:01 +0100 (CET)
Received: from [192.168.1.12] (157.red-83-36-225.dynamicip.rima-tde.net [83.36.225.157]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: gabilm@um.es) by xenon44.um.es (Postfix) with ESMTPSA id BDE6D2001D; Thu,  6 Dec 2018 00:12:59 +0100 (CET)
From: Gabriel Lopez <gabilm@um.es>
Message-Id: <BEF88113-15FD-44C4-8EAB-3E17C5230862@um.es>
Content-Type: multipart/alternative; boundary="Apple-Mail=_F0D60BD5-1F71-4207-AC6F-F9FF15F3992B"
Mime-Version: 1.0 (Mac OS X Mail 12.1 \(3445.101.1\))
Date: Thu, 6 Dec 2018 00:12:58 +0100
In-Reply-To: <4A95BA014132FF49AE685FAB4B9F17F66B1F627A@SJCEML521-MBB.china.huawei.com>
Cc: Gabriel Lopez <gabilm@um.es>, "draft-ietf-i2nsf-sdn-ipsec-flow-protection@ietf.org" <draft-ietf-i2nsf-sdn-ipsec-flow-protection@ietf.org>,  "i2nsf@ietf.org" <i2nsf@ietf.org>
To: Linda Dunbar <linda.dunbar@huawei.com>
References: <4A95BA014132FF49AE685FAB4B9F17F66B1F627A@SJCEML521-MBB.china.huawei.com>
X-Mailer: Apple Mail (2.3445.101.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2nsf/GQVLLwLTnXAx3wHC46qrykRRVdg>
Subject: Re: [I2nsf] Typo? in Appendix A of draft-i2nsf-sdn-ipsec-flow-protection?
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, 05 Dec 2018 23:13:09 -0000

--Apple-Mail=_F0D60BD5-1F71-4207-AC6F-F9FF15F3992B
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Hi Linda,=20

> El 5 dic 2018, a las 22:48, Linda Dunbar <linda.dunbar@huawei.com> =
escribi=C3=B3:
>=20
> =20
> Gabriel and Rafa,
> =20
> On Page 36 (Appendix A), you have the following :
> grouping port-range {
> description "Port range grouping";
> leaf start { type inet:port-number; description "Start IP address"; }
> leaf end { type inet:port-number; description "End IP address"; }
> }
> =20
> Do you mean =E2=80=9CStart Port number=E2=80=9D and =E2=80=9CEnd Port =
Number=E2=80=9D?

Yes, it is a typo.

Regards, Gabi.
> =20
> =20
> Thanks, Linda=20
> _______________________________________________
> I2nsf mailing list
> I2nsf@ietf.org <mailto:I2nsf@ietf.org>
> https://www.ietf.org/mailman/listinfo/i2nsf =
<https://www.ietf.org/mailman/listinfo/i2nsf>
-----------------------------------------------------------
Gabriel L=C3=B3pez Mill=C3=A1n
Departamento de Ingenier=C3=ADa de la Informaci=C3=B3n y las =
Comunicaciones
University of Murcia
Spain
Tel: +34 868888504
Fax: +34 868884151
email: gabilm@um.es




--Apple-Mail=_F0D60BD5-1F71-4207-AC6F-F9FF15F3992B
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 =
Linda,&nbsp;<br class=3D""><div><br class=3D""><blockquote type=3D"cite" =
class=3D""><div class=3D"">El 5 dic 2018, a las 22:48, Linda Dunbar =
&lt;<a href=3D"mailto:linda.dunbar@huawei.com" =
class=3D"">linda.dunbar@huawei.com</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: Helvetica; font-size: 12px; 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: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif;" class=3D""><span =
style=3D"font-size: 7.5pt; font-family: Courier;" class=3D""><o:p =
class=3D"">&nbsp;</o:p></span></div><div style=3D"margin: 0in 0in =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><span style=3D"font-family: Arial, sans-serif;" =
class=3D"">Gabriel and Rafa,<o:p class=3D""></o:p></span></div><div =
style=3D"margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif;" class=3D""><span style=3D"font-family: Arial, =
sans-serif;" class=3D""><o:p class=3D"">&nbsp;</o:p></span></div><div =
style=3D"margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif;" class=3D""><span style=3D"font-family: Arial, =
sans-serif;" class=3D"">On Page 36 (Appendix A), you have the following =
:<o:p class=3D""></o:p></span></div><div style=3D"margin: 0in 0in =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><span style=3D"font-family: Arial, sans-serif;" =
class=3D"">grouping port-range {<o:p class=3D""></o:p></span></div><div =
style=3D"margin: 0in 0in 0.0001pt 0.5in; font-size: 11pt; font-family: =
Calibri, sans-serif;" class=3D""><span style=3D"font-family: Arial, =
sans-serif;" class=3D"">description "Port range grouping";<o:p =
class=3D""></o:p></span></div><div style=3D"margin: 0in 0in 0.0001pt =
0.5in; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><span style=3D"font-family: Arial, sans-serif;" class=3D"">leaf=
 start { type inet:port-number; description "Start IP address"; }<o:p =
class=3D""></o:p></span></div><div style=3D"margin: 0in 0in 0.0001pt =
0.5in; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><span style=3D"font-family: Arial, sans-serif;" class=3D"">leaf=
 end { type inet:port-number; description "End IP address"; }<o:p =
class=3D""></o:p></span></div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif;" class=3D""><span =
style=3D"font-family: Arial, sans-serif;" class=3D"">}</span><span =
style=3D"font-family: Arial, sans-serif;" class=3D""><o:p =
class=3D""></o:p></span></div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif;" class=3D""><span =
style=3D"font-family: Arial, sans-serif;" class=3D""><o:p =
class=3D"">&nbsp;</o:p></span></div><div style=3D"margin: 0in 0in =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><span style=3D"font-family: Arial, sans-serif;" class=3D"">Do =
you mean =E2=80=9CStart Port number=E2=80=9D and =E2=80=9CEnd Port =
Number=E2=80=9D?</span></div></div></div></blockquote><div><br =
class=3D""></div>Yes, it is a typo.</div><div><br =
class=3D""></div><div>Regards, Gabi.<br class=3D""><blockquote =
type=3D"cite" class=3D""><div class=3D""><div class=3D"WordSection1" =
style=3D"page: WordSection1; caret-color: rgb(0, 0, 0); font-family: =
Helvetica; font-size: 12px; 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: 0in 0in 0.0001pt; font-size: 11pt; =
font-family: Calibri, sans-serif;" class=3D""><span style=3D"font-family: =
Arial, sans-serif;" class=3D""><o:p class=3D""></o:p></span></div><div =
style=3D"margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif;" class=3D""><span style=3D"font-family: Arial, =
sans-serif;" class=3D""><o:p class=3D"">&nbsp;</o:p></span></div><div =
style=3D"margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif;" class=3D""><span style=3D"font-family: Arial, =
sans-serif;" class=3D""><o:p class=3D"">&nbsp;</o:p></span></div><div =
style=3D"margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif;" class=3D""><span style=3D"font-family: Arial, =
sans-serif;" class=3D"">Thanks, Linda<span =
class=3D"Apple-converted-space">&nbsp;</span><o:p =
class=3D""></o:p></span></div></div><span style=3D"caret-color: rgb(0, =
0, 0); font-family: Helvetica; font-size: 12px; 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: =
12px; 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: =
12px; 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: Helvetica; font-size: =
12px; 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"color: rgb(149, 79, 114); =
text-decoration: underline; font-family: Helvetica; font-size: 12px; =
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: Helvetica; font-size: =
12px; 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"color: =
rgb(149, 79, 114); text-decoration: underline; font-family: Helvetica; =
font-size: 12px; 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"color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
12px; 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;">-----------------------------------------------------------<br =
class=3D"">Gabriel L=C3=B3pez Mill=C3=A1n<br class=3D"">Departamento de =
Ingenier=C3=ADa de la Informaci=C3=B3n y las&nbsp;Comunicaciones<br =
class=3D"">University of Murcia<br class=3D"">Spain<br class=3D"">Tel: =
+34 868888504<br class=3D"">Fax: +34 868884151<br class=3D""><a =
href=3D"mailto:gabilm@um.es" =
class=3D"">email:&nbsp;gabilm@um.es</a></div><div style=3D"color: rgb(0, =
0, 0); font-family: Helvetica; font-size: 12px; 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""><br class=3D""></div><br class=3D"Apple-interchange-newline">
</div>
<br class=3D""></body></html>=

--Apple-Mail=_F0D60BD5-1F71-4207-AC6F-F9FF15F3992B--


From nobody Wed Dec  5 19:29:55 2018
Return-Path: <hyoungshick@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 DF71B130EB4 for <i2nsf@ietfa.amsl.com>; Wed,  5 Dec 2018 19:29:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.649
X-Spam-Level: 
X-Spam-Status: No, score=-1.649 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, 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 zPZJt-pluKyk for <i2nsf@ietfa.amsl.com>; Wed,  5 Dec 2018 19:29:49 -0800 (PST)
Received: from mail-lj1-f173.google.com (mail-lj1-f173.google.com [209.85.208.173]) (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 0B401130DE1 for <i2nsf@ietf.org>; Wed,  5 Dec 2018 19:29:49 -0800 (PST)
Received: by mail-lj1-f173.google.com with SMTP id e5-v6so20351003lja.4 for <i2nsf@ietf.org>; Wed, 05 Dec 2018 19:29:48 -0800 (PST)
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:content-transfer-encoding; bh=KZZHts+Pmkr1jFIZn68r+RYQB+YDsywaEYbNxthztTc=; b=m4s0iy36sERFP4jt/l9a6oot1dyau09B44trI8YSxGoh4i+4MGLfrTjPf/TDR5cZM/ 9RLSneo43A17GnKjNxPmv16HOD1cP45TxXyGqGba+IWSt4lcc8Ve74UrYKUAOwaEz7+W KgAf1iO9zdT3UEy+y5Yj/TvZIAEsrU9lHEODj52TO5Kxj5CaooBKGRIGle8LQA9NDG5w NdslSLxEHiolQxbtU4g+sAbangxHB0EzQ9r+Ti+oqwEG+F0vdVOeMJHTCq77Z72UNikX hke9bRqjAQ6bayrwjJsObY+eE85xwQJAOXQ2aUXLTTvRX8oKT3JJPp0tkFJP9Ri1VV0g vmzA==
X-Gm-Message-State: AA+aEWbC2NQJapWU6kIj6pJuLdt63cHX4wm09VHci7ziSRhrJfMbjAhH QEREvmZsxAezLA2bNWHqDOtqc859tdqz3vvaYu8=
X-Google-Smtp-Source: AFSGD/VVRU1tC/qYPozsj1RobU13w+LMdijz7m+CcOEvT8AHa6rGgmsmCGcLGYyA6DKNPwo/MiZSv86WaesX5hV9mAU=
X-Received: by 2002:a2e:5356:: with SMTP id t22-v6mr16593722ljd.26.1544066986922;  Wed, 05 Dec 2018 19:29:46 -0800 (PST)
MIME-Version: 1.0
References: <4A95BA014132FF49AE685FAB4B9F17F66B1F6399@SJCEML521-MBB.china.huawei.com>
In-Reply-To: <4A95BA014132FF49AE685FAB4B9F17F66B1F6399@SJCEML521-MBB.china.huawei.com>
From: Hyoungshick Kim <hyoung@skku.edu>
Date: Thu, 6 Dec 2018 12:29:34 +0900
Message-ID: <CANQNX+z_WpVLcO30g9Lhw3V7FUxbnPG3CpMR8VC+U54T96A22Q@mail.gmail.com>
To: Linda Dunbar <linda.dunbar@huawei.com>
Cc: i2nsf@ietf.org
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2nsf/tQU1EwYTY23WvqHPmZveqX3hxS0>
Subject: Re: [I2nsf] Call for WG Adoption on NSF Monitoring 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, 06 Dec 2018 03:29:54 -0000

Hi I2NSF WG,

I fully support the WG adoption of this NSF Monitoring Data Model draft.
The NSF monitoring is very important to maintain the I2NSF framework
in an efficient and effective way, which can monitor the functionality
and load of NSFs,
and detect suspicious activities, such as DDoS attacks and malicious
code packets.
This draft provides the security industry with a concise and
comprehensive data model
along with an information model for NSF monitoring.

Best regards,

Hyoungshick
On Thu, Dec 6, 2018 at 7:31 AM Linda Dunbar <linda.dunbar@huawei.com> wrote=
:
>
> This is the start of a two weeks call for input on the WG adoption of the=
 document: https://tools.ietf.org/html/draft-hong-i2nsf-nsf-monitoring-data=
-model-06
>
>
>
> Thanks for the authors of the two I2NSF Monitoring drafts taking actions =
of merging the content.
>
> We need more of those actions. As of now we have 8 WG drafts. We need to =
finish them next few months.
>
>
>
> Bear in mind that WG adoption doesn=E2=80=99t mean the draft is ready, on=
ly means that WG will work together on the draft (instead of individuals).
>
>
>
> Please provide feedback to the list/chairs if you believe that this docum=
ent should be adopted as a WG document.
>
>
>
> Thanks,
>
>
>
> Linda & Yoav
>
>
>
> From: Mr. Jaehoon Paul Jeong [mailto:jaehoon.paul@gmail.com]
> Sent: Thursday, November 15, 2018 6:35 PM
> To: Linda Dunbar <linda.dunbar@huawei.com>; Yoav Nir <ynir.ietf@gmail.com=
>
> Cc: i2nsf@ietf.org; skku_secu-brain_all@googlegroups.com; Sangwon Hyun <s=
whyun77@gmail.com>; Mr. Jaehoon Paul Jeong <jaehoon.paul@gmail.com>
> Subject: Request for WG Adoption Call on NSF Monitoring Draft
>
>
>
> Hi Linda and Yoav,
>
> As we discussed the last Bangkok meeting,
>
> I have merged the two drafts of Information Model and Data Model
>
> for NSF Monitoring into a new draft called draft-hong-i2nsf-nsf-monitorin=
g-data-model-06:
>
>
>
> - Two Information and Data Model Drafts
>
>  . draft-zhang-i2nsf-info-model-monitoring-07
>
>  . draft-hong-i2nsf-nsf-monitoring-data-model-05
>
>
>
> - A Merged Data Model Draft
>
>  . draft-hong-i2nsf-nsf-monitoring-data-model-06
>
>  . https://tools.ietf.org/html/draft-hong-i2nsf-nsf-monitoring-data-model=
-06
>
>
>
> The NSF monitoring is very important to manage the I2NSF security service=
 system
>
> in a reliable and scalable fashion.
>
>
>
> Could you start a WG adoption call for this draft?
>
>
>
> Thanks.
>
>
>
> Best Regards,
>
> Paul
>
> --
>
> =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 Software
> 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
>
> _______________________________________________
> I2nsf mailing list
> I2nsf@ietf.org
> https://www.ietf.org/mailman/listinfo/i2nsf



--=20
_______________________________
Hyoungshick (Hyoung) Kim,

Department of Software
College of Software
Office 27324, 2066 Seobu-Ro, Jangan-gu, Suwon, Gyeonggi-do 440-746, Korea
+82-31-299-4324 (mobile: +82-10-5557-3081)
hyoung@skku.edu
http://seclab.skku.edu/people/hyoungshick-kim/


From nobody Thu Dec  6 00:54:05 2018
Return-Path: <diego.r.lopez@telefonica.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 541B5130DDB for <i2nsf@ietfa.amsl.com>; Thu,  6 Dec 2018 00:54:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.449
X-Spam-Level: 
X-Spam-Status: No, score=-3.449 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-1.46, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_FILL_THIS_FORM_SHORT=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=telefonica.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 XjvRstRQgRdY for <i2nsf@ietfa.amsl.com>; Thu,  6 Dec 2018 00:53:59 -0800 (PST)
Received: from EUR01-HE1-obe.outbound.protection.outlook.com (mail-eopbgr130093.outbound.protection.outlook.com [40.107.13.93]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 764C8127B4C for <i2nsf@ietf.org>; Thu,  6 Dec 2018 00:53:58 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telefonica.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=5Am8qCR5DoK/WW0Ds26QVndJCy/3rKvKqY7C5WbAp0s=; b=y4TY40gPpO+RVVDjN/6xJM39v5JTY0BJSUwJGx6hKS+Q6lYSDgU2zqL6JGZ+LolGBZRSHDoFLzUAn+Y7/7FZmyWWAB5fYVz5uG0PLwCy36/cP3OxQBE4GLHohIIGnGlfk7SJTRHSWaQqyyqXEml8zTr7/JHYsIBad6kSZT9+Vjc=
Received: from DB3PR0602MB3788.eurprd06.prod.outlook.com (52.134.70.148) by DB3PR0602MB3802.eurprd06.prod.outlook.com (52.134.70.151) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1382.22; Thu, 6 Dec 2018 08:53:50 +0000
Received: from DB3PR0602MB3788.eurprd06.prod.outlook.com ([fe80::9153:c6e3:56db:860e]) by DB3PR0602MB3788.eurprd06.prod.outlook.com ([fe80::9153:c6e3:56db:860e%4]) with mapi id 15.20.1404.019; Thu, 6 Dec 2018 08:53:50 +0000
From: "Diego R. Lopez" <diego.r.lopez@telefonica.com>
To: Linda Dunbar <linda.dunbar@huawei.com>, "i2nsf@ietf.org" <i2nsf@ietf.org>
Thread-Topic: [I2nsf] Call for WG Adoption on NSF Monitoring Draft
Thread-Index: AQHUjUE1nXgHbwPSCU6uaUQRg063lg==
Date: Thu, 6 Dec 2018 08:53:50 +0000
Message-ID: <5D96C619-820E-44A4-A191-DB99715D63D5@telefonica.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/10.10.4.181110
authentication-results: spf=none (sender IP is ) smtp.mailfrom=diego.r.lopez@telefonica.com; 
x-originating-ip: [195.238.226.2]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; DB3PR0602MB3802; 6:lHehKNabHWsHHp/rJR2xokYEE8M15pNUUBduCObWRmzGnn4lF4KDAeQsxz4FD5gyggVwAgTL2uf2sfOB3loTQ3d6nr7NHGFquFyiC2DXBPFI/ySaEkocb7UFPAcrZoJsbFuywg5IYfWZM2yB7Z2u0hVAouEQqPTQQEyIgKyNlQU2//3ZHXe3tuemFz48gIzZw81glaIZIx/h+yXahiWbdvr079gaH0LhKeh7Zo0VQ94Wk65SeLtrbJZoVlX+bPJwLB084Kre4tqNfUDJC3HY3HQGEPWMHGNZSLFAG+haOLmBw3DsyUo6I04DOr9uco7oEQ6Jy1Y4/rDjzNnwbjhhleU/Ny9Mlk6+U1z5pubimCOL6Aq/+LcHpBh3ymZ6ejPimrE2l/NwuQwsWrlrqGcT9vS00oe4YFSZWTzCQYucpmx4KVqj2Lnfu47N7NrirTMOgjlGzrrTUvw9kL9Y3v/w6Q==; 5:bo0tLTmwwC34GOwQvWXj09gHHch3hoIH4Usi9L9FGxBUVqIGoVxCFE+pUlLLPTI8p0puhEiaEkzA7ul+R4hSKHDsaYpLJHdM/P3Ff3Ulia+e11EYMpK6mBxhswRB+FitJbI+n6ms8ZK+LfxRbvNWyIV5cEtay1U9v9u7XMn9Jck=; 7:jUxDnhkFHFm/5nvadaadgDR27e1BcqtLBnzMFbmhJNhbL0AWXGdmDf1uyMvDubhbsasTVGiJkuGLEAWS688cs/+n1UU9okJWKbq11Xzz83loMPt3VxJMtOdKPo6nByYibXZqk/Ny7UQ5wiIFeoVhpw==
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-ms-office365-filtering-correlation-id: 2f18746b-adee-407e-cd95-08d65b58579e
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390098)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600074)(711020)(4618075)(2017052603328)(7153060)(7193020); SRVR:DB3PR0602MB3802; 
x-ms-traffictypediagnostic: DB3PR0602MB3802:
x-microsoft-antispam-prvs: <DB3PR0602MB380277A91DC6383C407F1E48DFA90@DB3PR0602MB3802.eurprd06.prod.outlook.com>
x-ms-exchange-senderadcheck: 1
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(8211001083)(6040522)(2401047)(8121501046)(5005006)(10201501046)(3002001)(93006095)(93001095)(3231455)(999002)(944501520)(4982022)(52105112)(6055026)(148016)(149066)(150057)(6041310)(201703131423095)(201702281529075)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123558120)(20161123562045)(20161123560045)(20161123564045)(201708071742011)(7699051)(76991095); SRVR:DB3PR0602MB3802; BCL:0; PCL:0; RULEID:; SRVR:DB3PR0602MB3802; 
x-forefront-prvs: 087894CD3C
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(396003)(136003)(366004)(376002)(346002)(39860400002)(189003)(199004)(51914003)(40134004)(252514010)(6486002)(6512007)(54896002)(6306002)(2501003)(71190400001)(229853002)(83716004)(71200400001)(7736002)(66574009)(236005)(3846002)(6116002)(966005)(325944009)(45080400002)(15188155005)(14454004)(8676002)(6436002)(81156014)(478600001)(99286004)(81166006)(2906002)(106356001)(25786009)(8936002)(105586002)(36756003)(16799955002)(33656002)(66066001)(26005)(14444005)(256004)(110136005)(486006)(186003)(58126008)(2616005)(53546011)(476003)(82746002)(102836004)(86362001)(6506007)(6246003)(53936002)(97736004)(68736007)(5660300001)(316002)(606006)(786003); DIR:OUT; SFP:1102; SCL:1; SRVR:DB3PR0602MB3802; H:DB3PR0602MB3788.eurprd06.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1; 
received-spf: None (protection.outlook.com: telefonica.com does not designate permitted sender hosts)
x-microsoft-antispam-message-info: JhRy0duczuYyT24XaIVpKVkvckCWjwL56QKpwIrcv0Lzs3mziDZspyuFNTVnMYqxBVjjZM5y+Lob2UPVvS1rksEc1fTofwQrXm9pCi2KaetYeh/F86OzBtZnqXdcX0kbzPZkywkdYDf1JSt+vC5L1HmU2osGTxC4bTtui+GmakchHujcXEgQVex6lfiIG+Mnm+4XxBwm+KV5ON9JgW5+VgljAq2fFvKGPc0hgncHPpy7cEmNYVfTmp64v3PH6y0MFfY77JbrJQID8GpQe9soXpjif5aoVhge6pMt2QyqdPkiYWOnCGeqn77pQWeraqIaxAs05OzCroe40trRLLAMM26jG7PcGn5sSK9qVOiTDZ4=
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_5D96C619820E44A4A191DB99715D63D5telefonicacom_"
MIME-Version: 1.0
X-OriginatorOrg: telefonica.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 2f18746b-adee-407e-cd95-08d65b58579e
X-MS-Exchange-CrossTenant-originalarrivaltime: 06 Dec 2018 08:53:50.4078 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 9744600e-3e04-492e-baa1-25ec245c6f10
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DB3PR0602MB3802
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2nsf/VDZLFMTb_3UICS89YqCoz_5DIp0>
Subject: Re: [I2nsf] Call for WG Adoption on NSF Monitoring 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, 06 Dec 2018 08:54:04 -0000

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

SGksDQoNCldoaWxlIEkgYWdyZWUgdGhlIG1hdHRlciBhZGRyZXNzZWQgYnkgdGhlIGRyYWZ0IGlz
IHF1aXRlIHJlbGV2YW50IGFuZCB3ZSBhcyBhIGdyb3VwIG5lZWQgdG8gY29uc2lkZXIgYSBkYXRh
IG1vZGVsIGZvciBtb25pdG9yaW5nLCBJIGFtIGNvbmNlcm5lZCBhYm91dCBwb3RlbnRpYWwgcmVp
bnZlbnRpb25zIG9mIHRoZSB3aGVlbCwgYXMgdGhpcyBkYXRhIG1vZGVsIHNob3VsZCBiZSBhbiBl
eHRlbnNpb24gb2YgYW55IG90aGVyIG1vcmUgZ2VuZXJhbCBtb25pdG9yaW5nIGRhdGEgbW9kZWwg
b3V0IHRoZXJlLiBTbyBJIHRoaW5rIHRoZSBxdWVyeSBMaW5kYSBpbml0aWF0ZWQgb24gaXMgYSB3
aXNlIG1vdmUuDQoNCkluIHN1bW1hcnksIEkgc3VwcG9ydCB0aGUgYWRvcHRpb24gYW5kIEkgcmVx
dWVzdCBpdCBldm9sdmVzIGludG8gYW4gaW5jcmVtZW50YWwgYXBwcm9hY2ggd2l0aCByZXNwZWN0
IGFueSBzdWl0YWJsZSBnZW5lcmFsIG1vbml0b3JpbmcgbW9kZWwuDQoNCkJlIGdvb2RlLA0KDQot
LQ0KIkVzdGEgdmV6IG5vIGZhbGxhcmVtb3MsIERvY3RvciBJbmZpZXJubyINCg0KRHIgRGllZ28g
Ui4gTG9wZXoNClRlbGVmb25pY2EgSStEDQpodHRwczovL3d3dy5saW5rZWRpbi5jb20vaW4vZHIy
bG9wZXovDQoNCmUtbWFpbDogZGllZ28uci5sb3BlekB0ZWxlZm9uaWNhLmNvbTxtYWlsdG86ZGll
Z28uci5sb3BlekB0ZWxlZm9uaWNhLmNvbT4NClRlbDogICAgICAgICArMzQgOTEzIDEyOSAwNDEN
Ck1vYmlsZTogICszNCA2ODIgMDUxIDA5MQ0KLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLQ0KDQpPbiAwNS8xMi8yMDE4LCAyMzozMSwgIkkybnNmIG9uIGJlaGFsZiBvZiBMaW5kYSBE
dW5iYXIiIDxpMm5zZi1ib3VuY2VzQGlldGYub3JnPG1haWx0bzppMm5zZi1ib3VuY2VzQGlldGYu
b3JnPiBvbiBiZWhhbGYgb2YgbGluZGEuZHVuYmFyQGh1YXdlaS5jb208bWFpbHRvOmxpbmRhLmR1
bmJhckBodWF3ZWkuY29tPj4gd3JvdGU6DQoNClRoaXMgaXMgdGhlIHN0YXJ0IG9mIGEgdHdvIHdl
ZWtzIGNhbGwgZm9yIGlucHV0IG9uIHRoZSBXRyBhZG9wdGlvbiBvZiB0aGUgZG9jdW1lbnQ6IGh0
dHBzOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9kcmFmdC1ob25nLWkybnNmLW5zZi1tb25pdG9yaW5n
LWRhdGEtbW9kZWwtMDYNCg0KVGhhbmtzIGZvciB0aGUgYXV0aG9ycyBvZiB0aGUgdHdvIEkyTlNG
IE1vbml0b3JpbmcgZHJhZnRzIHRha2luZyBhY3Rpb25zIG9mIG1lcmdpbmcgdGhlIGNvbnRlbnQu
DQpXZSBuZWVkIG1vcmUgb2YgdGhvc2UgYWN0aW9ucy4gQXMgb2Ygbm93IHdlIGhhdmUgOCBXRyBk
cmFmdHMuIFdlIG5lZWQgdG8gZmluaXNoIHRoZW0gbmV4dCBmZXcgbW9udGhzLg0KDQpCZWFyIGlu
IG1pbmQgdGhhdCBXRyBhZG9wdGlvbiBkb2VzbuKAmXQgbWVhbiB0aGUgZHJhZnQgaXMgcmVhZHks
IG9ubHkgbWVhbnMgdGhhdCBXRyB3aWxsIHdvcmsgdG9nZXRoZXIgb24gdGhlIGRyYWZ0IChpbnN0
ZWFkIG9mIGluZGl2aWR1YWxzKS4NCg0KUGxlYXNlIHByb3ZpZGUgZmVlZGJhY2sgdG8gdGhlIGxp
c3QvY2hhaXJzIGlmIHlvdSBiZWxpZXZlIHRoYXQgdGhpcyBkb2N1bWVudCBzaG91bGQgYmUgYWRv
cHRlZCBhcyBhIFdHIGRvY3VtZW50Lg0KDQpUaGFua3MsDQoNCkxpbmRhICYgWW9hdg0KDQpGcm9t
OiBNci4gSmFlaG9vbiBQYXVsIEplb25nIFttYWlsdG86amFlaG9vbi5wYXVsQGdtYWlsLmNvbV0N
ClNlbnQ6IFRodXJzZGF5LCBOb3ZlbWJlciAxNSwgMjAxOCA2OjM1IFBNDQpUbzogTGluZGEgRHVu
YmFyIDxsaW5kYS5kdW5iYXJAaHVhd2VpLmNvbT47IFlvYXYgTmlyIDx5bmlyLmlldGZAZ21haWwu
Y29tPg0KQ2M6IGkybnNmQGlldGYub3JnOyBza2t1X3NlY3UtYnJhaW5fYWxsQGdvb2dsZWdyb3Vw
cy5jb207IFNhbmd3b24gSHl1biA8c3doeXVuNzdAZ21haWwuY29tPjsgTXIuIEphZWhvb24gUGF1
bCBKZW9uZyA8amFlaG9vbi5wYXVsQGdtYWlsLmNvbT4NClN1YmplY3Q6IFJlcXVlc3QgZm9yIFdH
IEFkb3B0aW9uIENhbGwgb24gTlNGIE1vbml0b3JpbmcgRHJhZnQNCg0KSGkgTGluZGEgYW5kIFlv
YXYsDQpBcyB3ZSBkaXNjdXNzZWQgdGhlIGxhc3QgQmFuZ2tvayBtZWV0aW5nLA0KSSBoYXZlIG1l
cmdlZCB0aGUgdHdvIGRyYWZ0cyBvZiBJbmZvcm1hdGlvbiBNb2RlbCBhbmQgRGF0YSBNb2RlbA0K
Zm9yIE5TRiBNb25pdG9yaW5nIGludG8gYSBuZXcgZHJhZnQgY2FsbGVkIGRyYWZ0LWhvbmctaTJu
c2YtbnNmLW1vbml0b3JpbmctZGF0YS1tb2RlbC0wNjoNCg0KLSBUd28gSW5mb3JtYXRpb24gYW5k
IERhdGEgTW9kZWwgRHJhZnRzDQogLiBkcmFmdC16aGFuZy1pMm5zZi1pbmZvLW1vZGVsLW1vbml0
b3JpbmctMDcNCiAuIGRyYWZ0LWhvbmctaTJuc2YtbnNmLW1vbml0b3JpbmctZGF0YS1tb2RlbC0w
NQ0KDQotIEEgTWVyZ2VkIERhdGEgTW9kZWwgRHJhZnQNCiAuIGRyYWZ0LWhvbmctaTJuc2YtbnNm
LW1vbml0b3JpbmctZGF0YS1tb2RlbC0wNg0KIC4gaHR0cHM6Ly90b29scy5pZXRmLm9yZy9odG1s
L2RyYWZ0LWhvbmctaTJuc2YtbnNmLW1vbml0b3JpbmctZGF0YS1tb2RlbC0wNg0KDQpUaGUgTlNG
IG1vbml0b3JpbmcgaXMgdmVyeSBpbXBvcnRhbnQgdG8gbWFuYWdlIHRoZSBJMk5TRiBzZWN1cml0
eSBzZXJ2aWNlIHN5c3RlbQ0KaW4gYSByZWxpYWJsZSBhbmQgc2NhbGFibGUgZmFzaGlvbi4NCg0K
Q291bGQgeW91IHN0YXJ0IGEgV0cgYWRvcHRpb24gY2FsbCBmb3IgdGhpcyBkcmFmdD8NCg0KVGhh
bmtzLg0KDQpCZXN0IFJlZ2FyZHMsDQpQYXVsDQotLQ0KPT09PT09PT09PT09PT09PT09PT09PT09
PT09DQpNci4gSmFlaG9vbiAoUGF1bCkgSmVvbmcsIFBoLkQuDQpBc3NvY2lhdGUgUHJvZmVzc29y
DQpEZXBhcnRtZW50IG9mIFNvZnR3YXJlDQpTdW5na3l1bmt3YW4gVW5pdmVyc2l0eQ0KT2ZmaWNl
OiArODItMzEtMjk5LTQ5NTcNCkVtYWlsOiBqYWVob29uLnBhdWxAZ21haWwuY29tPG1haWx0bzpq
YWVob29uLnBhdWxAZ21haWwuY29tPiwgcGF1bGplb25nQHNra3UuZWR1PG1haWx0bzpwYXVsamVv
bmdAc2trdS5lZHU+DQpQZXJzb25hbCBIb21lcGFnZTogaHR0cDovL2lvdGxhYi5za2t1LmVkdS9w
ZW9wbGUtamFlaG9vbi1qZW9uZy5waHA8aHR0cDovL2Nwc2xhYi5za2t1LmVkdS9wZW9wbGUtamFl
aG9vbi1qZW9uZy5waHA+DQoNCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQoNCkVz
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_5D96C619820E44A4A191DB99715D63D5telefonicacom_
Content-Type: text/html; charset="utf-8"
Content-ID: <CC7C26472F191F4AB00911817D6D628A@eurprd06.prod.outlook.com>
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6bz0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6b2ZmaWNlIiB4
bWxuczp3PSJ1cm46c2NoZW1hcy1taWNyb3NvZnQtY29tOm9mZmljZTp3b3JkIiB4bWxuczptPSJo
dHRwOi8vc2NoZW1hcy5taWNyb3NvZnQuY29tL29mZmljZS8yMDA0LzEyL29tbWwiIHhtbG5zPSJo
dHRwOi8vd3d3LnczLm9yZy9UUi9SRUMtaHRtbDQwIj4NCjxoZWFkPg0KPG1ldGEgaHR0cC1lcXVp
dj0iQ29udGVudC1UeXBlIiBjb250ZW50PSJ0ZXh0L2h0bWw7IGNoYXJzZXQ9dXRmLTgiPg0KPG1l
dGEgbmFtZT0iR2VuZXJhdG9yIiBjb250ZW50PSJNaWNyb3NvZnQgV29yZCAxNSAoZmlsdGVyZWQg
bWVkaXVtKSI+DQo8c3R5bGU+PCEtLQ0KLyogRm9udCBEZWZpbml0aW9ucyAqLw0KQGZvbnQtZmFj
ZQ0KCXtmb250LWZhbWlseToiQ2FtYnJpYSBNYXRoIjsNCglwYW5vc2UtMToyIDQgNSAzIDUgNCA2
IDMgMiA0O30NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6Q2FsaWJyaTsNCglwYW5vc2UtMToy
IDE1IDUgMiAyIDIgNCAzIDIgNDt9DQovKiBTdHlsZSBEZWZpbml0aW9ucyAqLw0KcC5Nc29Ob3Jt
YWwsIGxpLk1zb05vcm1hbCwgZGl2Lk1zb05vcm1hbA0KCXttYXJnaW46MGNtOw0KCW1hcmdpbi1i
b3R0b206LjAwMDFwdDsNCglmb250LXNpemU6MTIuMHB0Ow0KCWZvbnQtZmFtaWx5OiJUaW1lcyBO
ZXcgUm9tYW4iLHNlcmlmO30NCmE6bGluaywgc3Bhbi5Nc29IeXBlcmxpbmsNCgl7bXNvLXN0eWxl
LXByaW9yaXR5Ojk5Ow0KCWNvbG9yOmJsdWU7DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVybGluZTt9
DQphOnZpc2l0ZWQsIHNwYW4uTXNvSHlwZXJsaW5rRm9sbG93ZWQNCgl7bXNvLXN0eWxlLXByaW9y
aXR5Ojk5Ow0KCWNvbG9yOnB1cnBsZTsNCgl0ZXh0LWRlY29yYXRpb246dW5kZXJsaW5lO30NCnAu
bXNvbm9ybWFsMCwgbGkubXNvbm9ybWFsMCwgZGl2Lm1zb25vcm1hbDANCgl7bXNvLXN0eWxlLW5h
bWU6bXNvbm9ybWFsOw0KCW1zby1tYXJnaW4tdG9wLWFsdDphdXRvOw0KCW1hcmdpbi1yaWdodDow
Y207DQoJbXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG87DQoJbWFyZ2luLWxlZnQ6MGNtOw0KCWZv
bnQtc2l6ZToxMS4wcHQ7DQoJZm9udC1mYW1pbHk6IkNhbGlicmkiLHNhbnMtc2VyaWY7fQ0Kc3Bh
bi5FbWFpbFN0eWxlMTgNCgl7bXNvLXN0eWxlLXR5cGU6cGVyc29uYWw7DQoJZm9udC1mYW1pbHk6
IkNhbGlicmkiLHNhbnMtc2VyaWY7DQoJY29sb3I6IzFGNDk3RDt9DQpzcGFuLkVtYWlsU3R5bGUx
OQ0KCXttc28tc3R5bGUtdHlwZTpwZXJzb25hbC1yZXBseTsNCglmb250LWZhbWlseToiQ2FsaWJy
aSIsc2Fucy1zZXJpZjsNCgljb2xvcjp3aW5kb3d0ZXh0O30NCi5Nc29DaHBEZWZhdWx0DQoJe21z
by1zdHlsZS10eXBlOmV4cG9ydC1vbmx5Ow0KCWZvbnQtc2l6ZToxMC4wcHQ7fQ0KQHBhZ2UgV29y
ZFNlY3Rpb24xDQoJe3NpemU6NjEyLjBwdCA3OTIuMHB0Ow0KCW1hcmdpbjo3Mi4wcHQgNzIuMHB0
IDcyLjBwdCA3Mi4wcHQ7fQ0KZGl2LldvcmRTZWN0aW9uMQ0KCXtwYWdlOldvcmRTZWN0aW9uMTt9
DQotLT48L3N0eWxlPg0KPC9oZWFkPg0KPGJvZHkgbGFuZz0iRVMiIGxpbms9ImJsdWUiIHZsaW5r
PSJwdXJwbGUiPg0KPGRpdiBjbGFzcz0iV29yZFNlY3Rpb24xIj4NCjxwIGNsYXNzPSJNc29Ob3Jt
YWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGli
cmkmcXVvdDssc2Fucy1zZXJpZiI+SGksPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1
b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6
ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmIj5XaGls
ZSBJIGFncmVlIHRoZSBtYXR0ZXIgYWRkcmVzc2VkIGJ5IHRoZSBkcmFmdCBpcyBxdWl0ZSByZWxl
dmFudCBhbmQgd2UgYXMgYSBncm91cCBuZWVkIHRvIGNvbnNpZGVyIGEgZGF0YSBtb2RlbCBmb3Ig
bW9uaXRvcmluZywgSSBhbSBjb25jZXJuZWQgYWJvdXQgcG90ZW50aWFsDQogcmVpbnZlbnRpb25z
IG9mIHRoZSB3aGVlbCwgYXMgdGhpcyBkYXRhIG1vZGVsIHNob3VsZCBiZSBhbiBleHRlbnNpb24g
b2YgYW55IG90aGVyIG1vcmUgZ2VuZXJhbCBtb25pdG9yaW5nIGRhdGEgbW9kZWwgb3V0IHRoZXJl
LiBTbyBJIHRoaW5rIHRoZSBxdWVyeSBMaW5kYSBpbml0aWF0ZWQgb24gaXMgYSB3aXNlIG1vdmUu
PG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0i
RU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkm
cXVvdDssc2Fucy1zZXJpZiI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2Zv
bnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZiI+SW4gc3VtbWFyeSwgSSBz
dXBwb3J0IHRoZSBhZG9wdGlvbiBhbmQgSSByZXF1ZXN0IGl0IGV2b2x2ZXMgaW50byBhbiBpbmNy
ZW1lbnRhbCBhcHByb2FjaCB3aXRoIHJlc3BlY3QgYW55IHN1aXRhYmxlIGdlbmVyYWwgbW9uaXRv
cmluZyBtb2RlbC48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48
c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1
b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6
ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmIj5CZSBn
b29kZSw8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBs
YW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2Fs
aWJyaSZxdW90OyxzYW5zLXNlcmlmIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8ZGl2
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9u
dC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmIj4tLTxvOnA+PC9vOnA+PC9z
cGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAu
MHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZiI+JnF1b3Q7RXN0
YSB2ZXogbm8gZmFsbGFyZW1vcywgRG9jdG9yIEluZmllcm5vJnF1b3Q7PG86cD48L286cD48L3Nw
YW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC4w
cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmIj4mbmJzcDs8bzpw
PjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9u
dC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWYi
PkRyIERpZWdvIFIuIExvcGV6PG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2Fs
aWJyaSZxdW90OyxzYW5zLXNlcmlmIj5UZWxlZm9uaWNhIEkmIzQzO0Q8bzpwPjwvbzpwPjwvc3Bh
bj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjBw
dDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWYiPjxhIGhyZWY9Imh0
dHBzOi8vd3d3LmxpbmtlZGluLmNvbS9pbi9kcjJsb3Blei8iPjxzcGFuIHN0eWxlPSJjb2xvcjoj
MDU2M0MxIj5odHRwczovL3d3dy5saW5rZWRpbi5jb20vaW4vZHIybG9wZXovPC9zcGFuPjwvYT4m
bmJzcDs8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBz
dHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNh
bnMtc2VyaWYiPiZuYnNwOzxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3Jt
YWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGli
cmkmcXVvdDssc2Fucy1zZXJpZiI+ZS1tYWlsOiZuYnNwOzwvc3Bhbj48c3BhbiBsYW5nPSJFTi1H
QiIgc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90
OyxzYW5zLXNlcmlmIj48YSBocmVmPSJtYWlsdG86ZGllZ28uci5sb3BlekB0ZWxlZm9uaWNhLmNv
bSI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJjb2xvcjojMDU2M0MxIj48c3BhbiBsYW5nPSJF
Ti1VUyI+ZGllZ28uci5sb3BlekB0ZWxlZm9uaWNhLmNvbTwvc3Bhbj48L3NwYW4+PC9hPjwvc3Bh
bj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJp
JnF1b3Q7LHNhbnMtc2VyaWYiPjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29O
b3JtYWwiPjxzcGFuIGxhbmc9IkVOLUdCIiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZh
bWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWYiPlRlbDombmJzcDsmbmJzcDsmbmJz
cDsgJm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7ICYjNDM7MzQgOTEzIDEyOSAwNDE8bzpwPjwvbzpw
Pjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1HQiIgc3R5
bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5z
LXNlcmlmIj5Nb2JpbGU6ICZuYnNwOyYjNDM7MzQgNjgyIDA1MSAwOTE8bzpwPjwvbzpwPjwvc3Bh
bj48L3A+DQo8L2Rpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLUdCIiBz
dHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNh
bnMtc2VyaWYiPi0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS08L3NwYW4+PHNwYW4g
bGFuZz0iRU4tR0IiIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0Nh
bGlicmkmcXVvdDssc2Fucy1zZXJpZiI+PG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tR0IiIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2Zv
bnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZiI+PG86cD4mbmJzcDs8L286
cD48L3NwYW4+PC9wPg0KPGRpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0i
bWFyZ2luLWxlZnQ6MzYuMHB0Ij5PbiAwNS8xMi8yMDE4LCAyMzozMSwgJnF1b3Q7STJuc2Ygb24g
YmVoYWxmIG9mIExpbmRhIER1bmJhciZxdW90OyAmbHQ7PGEgaHJlZj0ibWFpbHRvOmkybnNmLWJv
dW5jZXNAaWV0Zi5vcmciPmkybnNmLWJvdW5jZXNAaWV0Zi5vcmc8L2E+IG9uIGJlaGFsZiBvZg0K
PGEgaHJlZj0ibWFpbHRvOmxpbmRhLmR1bmJhckBodWF3ZWkuY29tIj5saW5kYS5kdW5iYXJAaHVh
d2VpLmNvbTwvYT4mZ3Q7IHdyb3RlOjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0Ij48bzpw
PjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29O
b3JtYWwiIHN0eWxlPSJtYXJnaW4tbGVmdDozNi4wcHQiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0K
PC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibWFyZ2luLWxlZnQ6MzYuMHB0Ij48
c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1
b3Q7LHNhbnMtc2VyaWY7Y29sb3I6IzFGNDk3RCI+VGhpcyBpcyB0aGUgc3RhcnQgb2YgYSB0d28g
d2Vla3MgY2FsbCBmb3IgaW5wdXQgb24gdGhlIFdHIGFkb3B0aW9uIG9mIHRoZSBkb2N1bWVudDoN
Cjwvc3Bhbj48YSBocmVmPSJodHRwczovL3Rvb2xzLmlldGYub3JnL2h0bWwvZHJhZnQtaG9uZy1p
Mm5zZi1uc2YtbW9uaXRvcmluZy1kYXRhLW1vZGVsLTA2Ij5odHRwczovL3Rvb2xzLmlldGYub3Jn
L2h0bWwvZHJhZnQtaG9uZy1pMm5zZi1uc2YtbW9uaXRvcmluZy1kYXRhLW1vZGVsLTA2PC9hPjxv
OnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1hcmdpbi1sZWZ0OjM2
LjBwdCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2Fs
aWJyaSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOiMxRjQ5N0QiPiZuYnNwOzwvc3Bhbj48bzpwPjwv
bzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJnaW4tbGVmdDozNi4wcHQi
PjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkm
cXVvdDssc2Fucy1zZXJpZjtjb2xvcjojMUY0OTdEIj5UaGFua3MgZm9yIHRoZSBhdXRob3JzIG9m
IHRoZSB0d28gSTJOU0YgTW9uaXRvcmluZyBkcmFmdHMgdGFraW5nIGFjdGlvbnMgb2YgbWVyZ2lu
ZyB0aGUgY29udGVudC4NCjwvc3Bhbj48bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3Jt
YWwiIHN0eWxlPSJtYXJnaW4tbGVmdDozNi4wcHQiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEu
MHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjojMUY0
OTdEIj5XZSBuZWVkIG1vcmUgb2YgdGhvc2UgYWN0aW9ucy4gQXMgb2Ygbm93IHdlIGhhdmUgOCBX
RyBkcmFmdHMuIFdlIG5lZWQgdG8gZmluaXNoIHRoZW0gbmV4dCBmZXcgbW9udGhzLg0KPC9zcGFu
PjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1hcmdpbi1sZWZ0
OjM2LjBwdCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7
Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOiMxRjQ5N0QiPiZuYnNwOzwvc3Bhbj48bzpw
PjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJnaW4tbGVmdDozNi4w
cHQiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGli
cmkmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjojMUY0OTdEIj5CZWFyIGluIG1pbmQgdGhhdCBXRyBh
ZG9wdGlvbiBkb2VzbuKAmXQgbWVhbiB0aGUgZHJhZnQgaXMgcmVhZHksIG9ubHkgbWVhbnMgdGhh
dCBXRyB3aWxsIHdvcmsgdG9nZXRoZXIgb24gdGhlIGRyYWZ0IChpbnN0ZWFkIG9mIGluZGl2aWR1
YWxzKS4NCjwvc3Bhbj48bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxl
PSJtYXJnaW4tbGVmdDozNi4wcHQiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQt
ZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjojMUY0OTdEIj4mbmJz
cDs8L3NwYW4+PG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibWFy
Z2luLWxlZnQ6MzYuMHB0Ij48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWls
eTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6IzFGNDk3RCI+UGxlYXNlIHBy
b3ZpZGUgZmVlZGJhY2sgdG8gdGhlIGxpc3QvY2hhaXJzIGlmIHlvdSBiZWxpZXZlIHRoYXQgdGhp
cyBkb2N1bWVudCBzaG91bGQgYmUgYWRvcHRlZCBhcyBhIFdHIGRvY3VtZW50Ljwvc3Bhbj48bzpw
PjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJnaW4tbGVmdDozNi4w
cHQiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGli
cmkmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjojMUY0OTdEIj4mbmJzcDs8L3NwYW4+PG86cD48L286
cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibWFyZ2luLWxlZnQ6MzYuMHB0Ij48
c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1
b3Q7LHNhbnMtc2VyaWY7Y29sb3I6IzFGNDk3RCI+VGhhbmtzLA0KPC9zcGFuPjxvOnA+PC9vOnA+
PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1hcmdpbi1sZWZ0OjM2LjBwdCI+PHNw
YW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90
OyxzYW5zLXNlcmlmO2NvbG9yOiMxRjQ5N0QiPiZuYnNwOzwvc3Bhbj48bzpwPjwvbzpwPjwvcD4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJnaW4tbGVmdDozNi4wcHQiPjxzcGFuIHN0
eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fu
cy1zZXJpZjtjb2xvcjojMUY0OTdEIj5MaW5kYSAmYW1wOyBZb2F2PC9zcGFuPjxvOnA+PC9vOnA+
PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1hcmdpbi1sZWZ0OjM2LjBwdCI+PHNw
YW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90
OyxzYW5zLXNlcmlmO2NvbG9yOiMxRjQ5N0QiPiZuYnNwOzwvc3Bhbj48bzpwPjwvbzpwPjwvcD4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJnaW4tbGVmdDozNi4wcHQiPjxiPjxzcGFu
IHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDss
c2Fucy1zZXJpZiI+RnJvbTo8L3NwYW4+PC9iPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0
O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZiI+IE1yLiBKYWVob29u
IFBhdWwgSmVvbmcgW21haWx0bzpqYWVob29uLnBhdWxAZ21haWwuY29tXQ0KPGJyPg0KPGI+U2Vu
dDo8L2I+IFRodXJzZGF5LCBOb3ZlbWJlciAxNSwgMjAxOCA2OjM1IFBNPGJyPg0KPGI+VG86PC9i
PiBMaW5kYSBEdW5iYXIgJmx0O2xpbmRhLmR1bmJhckBodWF3ZWkuY29tJmd0OzsgWW9hdiBOaXIg
Jmx0O3luaXIuaWV0ZkBnbWFpbC5jb20mZ3Q7PGJyPg0KPGI+Q2M6PC9iPiBpMm5zZkBpZXRmLm9y
Zzsgc2trdV9zZWN1LWJyYWluX2FsbEBnb29nbGVncm91cHMuY29tOyBTYW5nd29uIEh5dW4gJmx0
O3N3aHl1bjc3QGdtYWlsLmNvbSZndDs7IE1yLiBKYWVob29uIFBhdWwgSmVvbmcgJmx0O2phZWhv
b24ucGF1bEBnbWFpbC5jb20mZ3Q7PGJyPg0KPGI+U3ViamVjdDo8L2I+IFJlcXVlc3QgZm9yIFdH
IEFkb3B0aW9uIENhbGwgb24gTlNGIE1vbml0b3JpbmcgRHJhZnQ8L3NwYW4+PG86cD48L286cD48
L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibWFyZ2luLWxlZnQ6MzYuMHB0Ij4mbmJz
cDs8bzpwPjwvbzpwPjwvcD4NCjxkaXY+DQo8ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3Jt
YWwiIHN0eWxlPSJtYXJnaW4tbGVmdDozNi4wcHQiPkhpIExpbmRhIGFuZCBZb2F2LDxvOnA+PC9v
OnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1hcmdp
bi1sZWZ0OjM2LjBwdCI+QXMgd2UgZGlzY3Vzc2VkIHRoZSBsYXN0IEJhbmdrb2sgbWVldGluZyw8
bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxl
PSJtYXJnaW4tbGVmdDozNi4wcHQiPkkgaGF2ZSBtZXJnZWQgdGhlIHR3byBkcmFmdHMgb2YgSW5m
b3JtYXRpb24gTW9kZWwgYW5kIERhdGEgTW9kZWw8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRp
dj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJnaW4tbGVmdDozNi4wcHQiPmZvciBO
U0YgTW9uaXRvcmluZyBpbnRvIGEgbmV3IGRyYWZ0IGNhbGxlZCBkcmFmdC1ob25nLWkybnNmLW5z
Zi1tb25pdG9yaW5nLWRhdGEtbW9kZWwtMDY6PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibWFyZ2luLWxlZnQ6MzYuMHB0Ij4mbmJzcDs8
bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxl
PSJtYXJnaW4tbGVmdDozNi4wcHQiPi0gVHdvIEluZm9ybWF0aW9uIGFuZCBEYXRhIE1vZGVsIERy
YWZ0czxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIg
c3R5bGU9Im1hcmdpbi1sZWZ0OjM2LjBwdCI+Jm5ic3A7LiBkcmFmdC16aGFuZy1pMm5zZi1pbmZv
LW1vZGVsLW1vbml0b3JpbmctMDcmbmJzcDs8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJnaW4tbGVmdDozNi4wcHQiPiZuYnNwOy4g
ZHJhZnQtaG9uZy1pMm5zZi1uc2YtbW9uaXRvcmluZy1kYXRhLW1vZGVsLTA1PG86cD48L286cD48
L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibWFyZ2luLWxl
ZnQ6MzYuMHB0Ij4mbmJzcDs8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJnaW4tbGVmdDozNi4wcHQiPi0gQSBNZXJnZWQgRGF0YSBN
b2RlbCBEcmFmdCZuYnNwOzxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCIgc3R5bGU9Im1hcmdpbi1sZWZ0OjM2LjBwdCI+Jm5ic3A7LiBkcmFmdC1ob25n
LWkybnNmLW5zZi1tb25pdG9yaW5nLWRhdGEtbW9kZWwtMDY8bzpwPjwvbzpwPjwvcD4NCjwvZGl2
Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJnaW4tbGVmdDozNi4wcHQi
PiZuYnNwOy4gPGEgaHJlZj0iaHR0cHM6Ly90b29scy5pZXRmLm9yZy9odG1sL2RyYWZ0LWhvbmct
aTJuc2YtbnNmLW1vbml0b3JpbmctZGF0YS1tb2RlbC0wNiI+DQpodHRwczovL3Rvb2xzLmlldGYu
b3JnL2h0bWwvZHJhZnQtaG9uZy1pMm5zZi1uc2YtbW9uaXRvcmluZy1kYXRhLW1vZGVsLTA2PC9h
PjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5
bGU9Im1hcmdpbi1sZWZ0OjM2LjBwdCI+Jm5ic3A7PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxk
aXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibWFyZ2luLWxlZnQ6MzYuMHB0Ij5UaGUg
TlNGIG1vbml0b3JpbmcgaXMgdmVyeSBpbXBvcnRhbnQgdG8gbWFuYWdlIHRoZSBJMk5TRiBzZWN1
cml0eSBzZXJ2aWNlIHN5c3RlbTxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1hcmdpbi1sZWZ0OjM2LjBwdCI+aW4gYSByZWxpYWJsZSBh
bmQgc2NhbGFibGUgZmFzaGlvbi48bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJnaW4tbGVmdDozNi4wcHQiPiZuYnNwOzxvOnA+PC9v
OnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1hcmdp
bi1sZWZ0OjM2LjBwdCI+Q291bGQgeW91IHN0YXJ0IGEgV0cgYWRvcHRpb24gY2FsbCBmb3IgdGhp
cyBkcmFmdD88bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3Jt
YWwiIHN0eWxlPSJtYXJnaW4tbGVmdDozNi4wcHQiPiZuYnNwOzxvOnA+PC9vOnA+PC9wPg0KPC9k
aXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1hcmdpbi1sZWZ0OjM2LjBw
dCI+VGhhbmtzLjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCIgc3R5bGU9Im1hcmdpbi1sZWZ0OjM2LjBwdCI+Jm5ic3A7PG86cD48L286cD48L3A+DQo8
L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibWFyZ2luLWxlZnQ6MzYu
MHB0Ij5CZXN0IFJlZ2FyZHMsPG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFz
cz0iTXNvTm9ybWFsIiBzdHlsZT0ibWFyZ2luLWxlZnQ6MzYuMHB0Ij5QYXVsPG86cD48L286cD48
L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibWFyZ2luLWxl
ZnQ6MzYuMHB0Ij4tLSZuYnNwOzxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPGRpdj4N
CjxkaXY+DQo8ZGl2Pg0KPGRpdj4NCjxkaXY+DQo8ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29O
b3JtYWwiIHN0eWxlPSJtYXJnaW4tbGVmdDozNi4wcHQiPj09PT09PT09PT09PT09PT09PT09PT09
PT09PTxicj4NCk1yLiBKYWVob29uIChQYXVsKSBKZW9uZywgUGguRC48YnI+DQpBc3NvY2lhdGUg
UHJvZmVzc29yPGJyPg0KRGVwYXJ0bWVudCBvZiBTb2Z0d2FyZTxicj4NClN1bmdreXVua3dhbiBV
bml2ZXJzaXR5PGJyPg0KT2ZmaWNlOiAmIzQzOzgyLTMxLTI5OS00OTU3PGJyPg0KRW1haWw6IDxh
IGhyZWY9Im1haWx0bzpqYWVob29uLnBhdWxAZ21haWwuY29tIiB0YXJnZXQ9Il9ibGFuayI+amFl
aG9vbi5wYXVsQGdtYWlsLmNvbTwvYT4sJm5ic3A7PGEgaHJlZj0ibWFpbHRvOnBhdWxqZW9uZ0Bz
a2t1LmVkdSIgdGFyZ2V0PSJfYmxhbmsiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6OS41cHQiPnBh
dWxqZW9uZ0Bza2t1LmVkdTwvc3Bhbj48L2E+PGJyPg0KUGVyc29uYWwgSG9tZXBhZ2U6IDxhIGhy
ZWY9Imh0dHA6Ly9jcHNsYWIuc2trdS5lZHUvcGVvcGxlLWphZWhvb24tamVvbmcucGhwIiB0YXJn
ZXQ9Il9ibGFuayI+DQpodHRwOi8vaW90bGFiLnNra3UuZWR1L3Blb3BsZS1qYWVob29uLWplb25n
LnBocDwvYT48bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0K
PC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8
YnI+DQo8aHI+DQo8Zm9udCBmYWNlPSJBcmlhbCIgY29sb3I9IkdyYXkiIHNpemU9IjEiPjxicj4N
CkVzdGUgbWVuc2FqZSB5IHN1cyBhZGp1bnRvcyBzZSBkaXJpZ2VuIGV4Y2x1c2l2YW1lbnRlIGEg
c3UgZGVzdGluYXRhcmlvLCBwdWVkZSBjb250ZW5lciBpbmZvcm1hY2nDs24gcHJpdmlsZWdpYWRh
IG8gY29uZmlkZW5jaWFsIHkgZXMgcGFyYSB1c28gZXhjbHVzaXZvIGRlIGxhIHBlcnNvbmEgbyBl
bnRpZGFkIGRlIGRlc3Rpbm8uIFNpIG5vIGVzIHVzdGVkLiBlbCBkZXN0aW5hdGFyaW8gaW5kaWNh
ZG8sIHF1ZWRhIG5vdGlmaWNhZG8gZGUgcXVlIGxhDQogbGVjdHVyYSwgdXRpbGl6YWNpw7NuLCBk
aXZ1bGdhY2nDs24geS9vIGNvcGlhIHNpbiBhdXRvcml6YWNpw7NuIHB1ZWRlIGVzdGFyIHByb2hp
YmlkYSBlbiB2aXJ0dWQgZGUgbGEgbGVnaXNsYWNpw7NuIHZpZ2VudGUuIFNpIGhhIHJlY2liaWRv
IGVzdGUgbWVuc2FqZSBwb3IgZXJyb3IsIGxlIHJvZ2Ftb3MgcXVlIG5vcyBsbyBjb211bmlxdWUg
aW5tZWRpYXRhbWVudGUgcG9yIGVzdGEgbWlzbWEgdsOtYSB5IHByb2NlZGEgYSBzdSBkZXN0cnVj
Y2nDs24uPGJyPg0KPGJyPg0KVGhlIGluZm9ybWF0aW9uIGNvbnRhaW5lZCBpbiB0aGlzIHRyYW5z
bWlzc2lvbiBpcyBwcml2aWxlZ2VkIGFuZCBjb25maWRlbnRpYWwgaW5mb3JtYXRpb24gaW50ZW5k
ZWQgb25seSBmb3IgdGhlIHVzZSBvZiB0aGUgaW5kaXZpZHVhbCBvciBlbnRpdHkgbmFtZWQgYWJv
dmUuIElmIHRoZSByZWFkZXIgb2YgdGhpcyBtZXNzYWdlIGlzIG5vdCB0aGUgaW50ZW5kZWQgcmVj
aXBpZW50LCB5b3UgYXJlIGhlcmVieSBub3RpZmllZCB0aGF0IGFueSBkaXNzZW1pbmF0aW9uLA0K
IGRpc3RyaWJ1dGlvbiBvciBjb3B5aW5nIG9mIHRoaXMgY29tbXVuaWNhdGlvbiBpcyBzdHJpY3Rs
eSBwcm9oaWJpdGVkLiBJZiB5b3UgaGF2ZSByZWNlaXZlZCB0aGlzIHRyYW5zbWlzc2lvbiBpbiBl
cnJvciwgZG8gbm90IHJlYWQgaXQuIFBsZWFzZSBpbW1lZGlhdGVseSByZXBseSB0byB0aGUgc2Vu
ZGVyIHRoYXQgeW91IGhhdmUgcmVjZWl2ZWQgdGhpcyBjb21tdW5pY2F0aW9uIGluIGVycm9yIGFu
ZCB0aGVuIGRlbGV0ZSBpdC48YnI+DQo8YnI+DQpFc3RhIG1lbnNhZ2VtIGUgc2V1cyBhbmV4b3Mg
c2UgZGlyaWdlbSBleGNsdXNpdmFtZW50ZSBhbyBzZXUgZGVzdGluYXTDoXJpbywgcG9kZSBjb250
ZXIgaW5mb3JtYcOnw6NvIHByaXZpbGVnaWFkYSBvdSBjb25maWRlbmNpYWwgZSDDqSBwYXJhIHVz
byBleGNsdXNpdm8gZGEgcGVzc29hIG91IGVudGlkYWRlIGRlIGRlc3Rpbm8uIFNlIG7Do28gw6kg
dm9zc2Egc2VuaG9yaWEgbyBkZXN0aW5hdMOhcmlvIGluZGljYWRvLCBmaWNhIG5vdGlmaWNhZG8g
ZGUgcXVlIGENCiBsZWl0dXJhLCB1dGlsaXphw6fDo28sIGRpdnVsZ2HDp8OjbyBlL291IGPDs3Bp
YSBzZW0gYXV0b3JpemHDp8OjbyBwb2RlIGVzdGFyIHByb2liaWRhIGVtIHZpcnR1ZGUgZGEgbGVn
aXNsYcOnw6NvIHZpZ2VudGUuIFNlIHJlY2ViZXUgZXN0YSBtZW5zYWdlbSBwb3IgZXJybywgcm9n
YW1vcy1saGUgcXVlIG5vcyBvIGNvbXVuaXF1ZSBpbWVkaWF0YW1lbnRlIHBvciBlc3RhIG1lc21h
IHZpYSBlIHByb2NlZGEgYSBzdWEgZGVzdHJ1acOnw6NvPGJyPg0KPC9mb250Pg0KPC9ib2R5Pg0K
PC9odG1sPg0K

--_000_5D96C619820E44A4A191DB99715D63D5telefonicacom_--


From nobody Thu Dec  6 01:11:25 2018
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 ADCDC127B4C; Thu,  6 Dec 2018 01:11:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-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 huhH37k0g_p5; Thu,  6 Dec 2018 01:11:21 -0800 (PST)
Received: from xenon41.um.es (xenon41.um.es [155.54.212.167]) by ietfa.amsl.com (Postfix) with ESMTP id 55336130DC9; Thu,  6 Dec 2018 01:11:21 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by xenon41.um.es (Postfix) with ESMTP id 320DD208D6; Thu,  6 Dec 2018 10:11:19 +0100 (CET)
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 KkC7cr84s2IL; Thu,  6 Dec 2018 10:11:19 +0100 (CET)
Received: from [192.168.1.34] (73.red-2-138-17.dynamicip.rima-tde.net [2.138.17.73]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: rafa@um.es) by xenon41.um.es (Postfix) with ESMTPSA id 216C9206C6; Thu,  6 Dec 2018 10:11:16 +0100 (CET)
Date: Thu, 06 Dec 2018 10:11:14 +0100
User-Agent: K-9 Mail for Android
In-Reply-To: <4A95BA014132FF49AE685FAB4B9F17F66B1F627A@SJCEML521-MBB.china.huawei.com>
References: <4A95BA014132FF49AE685FAB4B9F17F66B1F627A@SJCEML521-MBB.china.huawei.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----ULO72TTMNO46OHYUI1MZXT39I7MCH8"
Content-Transfer-Encoding: 7bit
To: Linda Dunbar <linda.dunbar@huawei.com>, "draft-ietf-i2nsf-sdn-ipsec-flow-protection@ietf.org" <draft-ietf-i2nsf-sdn-ipsec-flow-protection@ietf.org>, "i2nsf@ietf.org" <i2nsf@ietf.org>
From: Rafa Marin-Lopez <rafa@um.es>
Message-ID: <F5E65753-67EE-4001-A308-46EADE06636C@um.es>
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2nsf/ljbLTBu9SCtxuIbDE9bm6ekmx14>
Subject: Re: [I2nsf] Typo? in Appendix A of draft-i2nsf-sdn-ipsec-flow-protection?
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, 06 Dec 2018 09:11:24 -0000

------ULO72TTMNO46OHYUI1MZXT39I7MCH8
Content-Type: text/plain;
 charset=utf-8
Content-Transfer-Encoding: quoted-printable

Yes, correct, it is a typo=2E

Thank you=2E

El 5 de diciembre de 2018 22:48:34 CET, Linda Dunbar <linda=2Edunbar@huawe=
i=2Ecom> escribi=C3=B3:
>
>Gabriel and Rafa,
>
>On Page 36 (Appendix A), you have the following :
>grouping port-range {
>description "Port range grouping";
>leaf start { type inet:port-number; description "Start IP address"; }
>leaf end { type inet:port-number; description "End IP address"; }
>}
>
>Do you mean "Start Port number" and "End Port Number"?
>
>
>Thanks, Linda

--=20
Enviado desde mi dispositivo Android con K-9 Mail=2E Por favor, disculpa m=
i brevedad=2E
------ULO72TTMNO46OHYUI1MZXT39I7MCH8
Content-Type: text/html;
 charset=utf-8
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas=2Emicrosoft=2Ecom/office/2004/12/omml" xmlns=3D"h=
ttp://www=2Ew3=2Eorg/TR/REC-html40"><head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii=
">
<meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Courier;
	panose-1:2 7 4 9 2 2 5 2 4 4;}
@font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:"\@SimSun";
	panose-1:2 1 6 0 3 1 1 1 1 1;}
/* Style Definitions */
p=2EMsoNormal, li=2EMsoNormal, div=2EMsoNormal
	{margin:0in;
	margin-bottom:=2E0001pt;
	font-size:11=2E0pt;
	font-family:"Calibri",sans-serif;}
a:link, span=2EMsoHyperlink
	{mso-style-priority:99;
	color:#0563C1;
	text-decoration:underline;}
a:visited, span=2EMsoHyperlinkFollowed
	{mso-style-priority:99;
	color:#954F72;
	text-decoration:underline;}
span=2EEmailStyle17
	{mso-style-type:personal;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
span=2EEmailStyle18
	{mso-style-type:personal-reply;
	font-family:"Calibri",sans-serif;
	color:#1F497D;}
=2EMsoChpDefault
	{mso-style-type:export-only;
	font-size:10=2E0pt;}
@page WordSection1
	{size:8=2E5in 11=2E0in;
	margin:1=2E0in 1=2E0in 1=2E0in 1=2E0in;}
div=2EWordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"#0563C1" vlink=3D"#954F72">Yes, correct, it i=
s a typo=2E<br><br>Thank you=2E<br><br><div class=3D"gmail_quote">El 5 de d=
iciembre de 2018 22:48:34 CET, Linda Dunbar &lt;linda=2Edunbar@huawei=2Ecom=
&gt; escribi=C3=B3:<blockquote class=3D"gmail_quote" style=3D"margin: 0pt 0=
pt 0pt 0=2E8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1e=
x;">

<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:7=2E5pt;font-family:Courie=
r"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Arial&quot;,sans-s=
erif">Gabriel and Rafa,
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Arial&quot;,sans-s=
erif"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Arial&quot;,sans-s=
erif">On Page 36 (Appendix A), you have the following :<o:p></o:p></span></=
p>
<p class=3D"MsoNormal" style=3D"text-autospace:none"><span style=3D"font-f=
amily:&quot;Arial&quot;,sans-serif">grouping port-range {<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal" style=3D"margin-left:=2E5in;text-autospace:none"><s=
pan style=3D"font-family:&quot;Arial&quot;,sans-serif">description "Port ra=
nge grouping";<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-left:=2E5in;text-autospace:none"><s=
pan style=3D"font-family:&quot;Arial&quot;,sans-serif">leaf start { type in=
et:port-number; description "Start IP address"; }<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-left:=2E5in;text-autospace:none"><s=
pan style=3D"font-family:&quot;Arial&quot;,sans-serif">leaf end { type inet=
:port-number; description "End IP address"; }<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Arial&quot;,sans-s=
erif">}</span><span style=3D"font-family:&quot;Arial&quot;,sans-serif"><o:p=
></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Arial&quot;,sans-s=
erif"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Arial&quot;,sans-s=
erif">Do you mean =E2=80=9CStart Port number=E2=80=9D and =E2=80=9CEnd Port=
 Number=E2=80=9D?
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Arial&quot;,sans-s=
erif"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Arial&quot;,sans-s=
erif"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Arial&quot;,sans-s=
erif">Thanks, Linda <o:p>
</o:p></span></p>
</div>


</blockquote></div><br>-- <br>Enviado desde mi dispositivo Android con K-9=
 Mail=2E Por favor, disculpa mi brevedad=2E</body></html>
------ULO72TTMNO46OHYUI1MZXT39I7MCH8--


From nobody Thu Dec  6 01:38:36 2018
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 292E0131123 for <i2nsf@ietfa.amsl.com>; Thu,  6 Dec 2018 01:38:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_PASS=-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 olpb7CiRaiSb for <i2nsf@ietfa.amsl.com>; Thu,  6 Dec 2018 01:38:30 -0800 (PST)
Received: from xenon42.um.es (xenon42.um.es [IPv6:2001:720:1710:601::42]) by ietfa.amsl.com (Postfix) with ESMTP id C699913111D for <i2nsf@ietf.org>; Thu,  6 Dec 2018 01:38:29 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by xenon42.um.es (Postfix) with ESMTP id 88027201D0; Thu,  6 Dec 2018 10:38:28 +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 GWkyk9m9sWjI; Thu,  6 Dec 2018 10:38:28 +0100 (CET)
Received: from [192.168.1.39] (73.red-2-138-17.dynamicip.rima-tde.net [2.138.17.73]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: rafa) by xenon42.um.es (Postfix) with ESMTPSA id 299A32048A; Thu,  6 Dec 2018 10:38:26 +0100 (CET)
Content-Type: multipart/alternative; boundary="Apple-Mail=_477E673E-C439-4423-8D23-9400CCB51A21"
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
From: Rafa Marin Lopez <rafa@um.es>
In-Reply-To: <4A95BA014132FF49AE685FAB4B9F17F66B1F61FE@SJCEML521-MBB.china.huawei.com>
Date: Thu, 6 Dec 2018 10:38:36 +0100
Cc: Rafa Marin Lopez <rafa@um.es>, Yoav Nir <ynir.ietf@gmail.com>, "i2nsf@ietf.org" <i2nsf@ietf.org>, Paul Wouters <paul@nohats.ca>
Message-Id: <B964B976-957F-4824-9A18-576C683159FC@um.es>
References: <4A95BA014132FF49AE685FAB4B9F17F66B1F61FE@SJCEML521-MBB.china.huawei.com>
To: Linda Dunbar <linda.dunbar@huawei.com>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2nsf/4zZJaWTpSxHo3qeaODdzgeV4gEQ>
Subject: Re: [I2nsf] YANG module update when new algorithms added to IPsec, RE:  Reviewing sdn-ipsec-flow-protection
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, 06 Dec 2018 09:38:35 -0000

--Apple-Mail=_477E673E-C439-4423-8D23-9400CCB51A21
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Hi Linda:

That was also suggested. In fact, our doubt is whether we should refer =
to something like:

https://tools.ietf.org/html/draft-ietf-netconf-crypto-types-02

In fact you can see in this reference things like:

identity hmac-sha2-256-128 {
      base "mac-algorithm";
      description
        "Generating a 256 bits MAC using SHA2 hash function and truncate
         it to 128 bits";
      reference
        "
RFC 4868
:
           Using HMAC-SHA-256, HMAC-SHA-384, and HMAC-SHA-512 with
           IPSec";

Although I think that the content of this reference should be expanded.

As another example, besides yours, they follow the model of importing:

https://tools.ietf.org/html/draft-ietf-netconf-tls-client-server-08

Best Regards.


> El 5 dic 2018, a las 21:48, Linda Dunbar <linda.dunbar@huawei.com> =
escribi=C3=B3:
>=20
> Yoav asked:
> =E2=80=9CWhat is our plan for future expansions?  Suppose there=E2=80=99=
s some hot, new algorithm that everyone is implementing. How do you =
update the YANG model in the future when you add new values to the =
enumerations?  Is it up to the administrator to make sure that the =
controller and NSFs are all on the =E2=80=9Csame page=E2=80=9D?=E2=80=9D
> =20
> We can use =E2=80=9Cimport=E2=80=9D and =E2=80=9Caugment=E2=80=9D to =
add new attributes as demonstrated by =
<>https://datatracker.ietf.org/doc/draft-lee-ccamp-optical-impairment-topo=
logy-yang/?include_text=3D1 =
<https://datatracker.ietf.org/doc/draft-lee-ccamp-optical-impairment-topol=
ogy-yang/?include_text=3D1>
> =20
> =20
> Linda
> From: I2nsf [mailto:i2nsf-bounces@ietf.org =
<mailto:i2nsf-bounces@ietf.org>] On Behalf Of Yoav Nir
> Sent: Wednesday, November 14, 2018 12:33 PM
> To: Rafa Marin-Lopez <rafa@um.es <mailto:rafa@um.es>>
> Cc: i2nsf@ietf.org <mailto:i2nsf@ietf.org>; Paul Wouters =
<paul@nohats.ca <mailto:paul@nohats.ca>>
> Subject: Re: [I2nsf] Reviewing sdn-ipsec-flow-protection
> =20
> Thanks, Rafa.
> =20
> Just one response below.
>=20
>=20
> On 14 Nov 2018, at 11:30, Rafa Marin-Lopez <rafa@um.es =
<mailto:rafa@um.es>> wrote:
> =20
> Hi Yoav:
>=20
>=20
> El 8 nov 2018, a las 17:11, Yoav Nir <ynir.ietf@gmail.com =
<mailto:ynir.ietf@gmail.com>> escribi=C3=B3:
> =20
> Hi, all
> =20
> As discussed in the room, we need some reviewers for the =
sdn-ipsec-flow-protection draft ([1])
> =20
> Thanks for these comments. Please see our response below.
>=20
> =20
> While any comments on any part of the document are welcome, I would =
like people to concentrate on the following issues:
> The YANG model in Appendix A
> Some of the crypto seems obsolete (example: DES). We would get into =
trouble in SecDir review.  OTOH ChaCha20-Poly1305 is missing..
> =20
> Agree. We will remove DES and add the algorithm you mention.
> =20
> The TLS working group went quite far with TLS 1.3.  Only 2 ciphers =
remain: AES-GCM with 16-byte ICV, and ChaCha20-Poly1305. That=E2=80=99s =
it.  Specifically, they=E2=80=99ve deprecated everything that isn=E2=80=99=
t an AEAD.
> =20
> The IPsecME working group hasn=E2=80=99t gone that far yet.  But in =
practice pretty much nothing is used except 3DES, AES-CBC, and AES-GCM.  =
Perhaps ChaCha20-Poly1305 is starting to see some use by now. We have =
RFC 8221, especially sections 5 and 6.  I think (although it=E2=80=99s =
up to the working group) that we should be fine defining only the MUSTs =
and the SHOULDs in those sections.
> =20
> That brings another question. What is our plan for future expansions?  =
Suppose there=E2=80=99s some hot, new algorithm that everyone is =
implementing. How do you update the YANG model in the future when you =
add new values to the enumerations?  Is it up to the administrator to =
make sure that the controller and NSFs are all on the =E2=80=9Csame =
page=E2=80=9D?
> =20
> Thanks
> =20
> Yoav
> _______________________________________________
> I2nsf mailing list
> I2nsf@ietf.org <mailto:I2nsf@ietf.org>
> https://www.ietf.org/mailman/listinfo/i2nsf =
<https://www.ietf.org/mailman/listinfo/i2nsf>

--Apple-Mail=_477E673E-C439-4423-8D23-9400CCB51A21
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; -webkit-line-break: after-white-space;" =
class=3D"">Hi Linda:<div class=3D""><br class=3D""></div><div =
class=3D"">That was also suggested. In fact, our doubt is whether we =
should refer to something like:</div><div class=3D""><br =
class=3D""></div><div class=3D""><a =
href=3D"https://tools.ietf.org/html/draft-ietf-netconf-crypto-types-02" =
class=3D"">https://tools.ietf.org/html/draft-ietf-netconf-crypto-types-02<=
/a></div><div class=3D""><br class=3D""></div><div class=3D"">In fact =
you can see in this reference things like:</div><div class=3D""><br =
class=3D""></div><div class=3D""><div class=3D"">identity =
hmac-sha2-256-128 {</div><div class=3D"">&nbsp; &nbsp; &nbsp; base =
"mac-algorithm";</div><div class=3D"">&nbsp; &nbsp; &nbsp; =
description</div><div class=3D"">&nbsp; &nbsp; &nbsp; &nbsp; "Generating =
a 256 bits MAC using SHA2 hash function and truncate</div><div =
class=3D"">&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;it to 128 bits";</div><div =
class=3D"">&nbsp; &nbsp; &nbsp; reference</div><div class=3D"">&nbsp; =
&nbsp; &nbsp; &nbsp; "</div>RFC 4868<div class=3D"">:</div><div =
class=3D"">&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Using HMAC-SHA-256, =
HMAC-SHA-384, and HMAC-SHA-512 with</div><div class=3D"">&nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp;<b class=3D"">IPSec</b>";</div></div><div =
class=3D""><br class=3D""></div><div class=3D"">Although I think that =
the content of this reference should be expanded.</div><div class=3D""><br=
 class=3D""></div><div class=3D"">As another example, besides yours, =
they follow the model of importing:</div><div class=3D""><br =
class=3D""></div><div class=3D""><a =
href=3D"https://tools.ietf.org/html/draft-ietf-netconf-tls-client-server-0=
8" =
class=3D"">https://tools.ietf.org/html/draft-ietf-netconf-tls-client-serve=
r-08</a></div><div class=3D""><br class=3D""></div><div class=3D"">Best =
Regards.</div><div class=3D""><br class=3D""></div><div class=3D""><br =
class=3D""><div><blockquote type=3D"cite" class=3D""><div class=3D"">El =
5 dic 2018, a las 21:48, Linda Dunbar &lt;<a =
href=3D"mailto:linda.dunbar@huawei.com" =
class=3D"">linda.dunbar@huawei.com</a>&gt; escribi=C3=B3:</div><br =
class=3D"Apple-interchange-newline"><div class=3D""><div =
class=3D"WordSection1" style=3D"page: WordSection1; font-family: =
Courier; font-size: 14px; 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;"><div =
style=3D"margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times =
New Roman', serif;" class=3D"">Yoav asked:<o:p class=3D""></o:p></div><div=
 style=3D"margin: 0in 0in 0.0001pt 0.5in; font-size: 12pt; font-family: =
'Times New Roman', serif;" class=3D"">=E2=80=9C<i class=3D"">What is our =
plan for future expansions? &nbsp;Suppose there=E2=80=99s some hot, new =
algorithm that everyone is implementing. How do you update the YANG =
model in the future when you add new values to the enumerations? =
&nbsp;Is it up to the administrator to make sure that the controller and =
NSFs are all on the =E2=80=9Csame page=E2=80=9D?=E2=80=9D</i><o:p =
class=3D""></o:p></div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 12pt; font-family: 'Times New Roman', serif;" class=3D""><span =
style=3D"font-size: 11pt; font-family: Calibri, sans-serif; color: =
rgb(31, 73, 125);" class=3D""><o:p =
class=3D"">&nbsp;</o:p></span></div><div style=3D"margin: 0in 0in =
0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;" =
class=3D""><a name=3D"_MailEndCompose" class=3D"">We can use =
=E2=80=9Cimport=E2=80=9D and =E2=80=9Caugment=E2=80=9D to add new =
attributes as demonstrated by</a><span style=3D"font-size: 11pt; =
font-family: Calibri, sans-serif; color: rgb(31, 73, 125);" =
class=3D""></span><a =
href=3D"https://datatracker.ietf.org/doc/draft-lee-ccamp-optical-impairmen=
t-topology-yang/?include_text=3D1" style=3D"color: purple; =
text-decoration: underline;" class=3D""><span style=3D"font-size: 11pt; =
font-family: Calibri, sans-serif;" =
class=3D"">https://datatracker.ietf.org/doc/draft-lee-ccamp-optical-impair=
ment-topology-yang/?include_text=3D1</span></a><span style=3D"font-size: =
11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);" =
class=3D""><o:p class=3D""></o:p></span></div><div style=3D"margin: 0in =
0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;" =
class=3D""><span style=3D"font-size: 11pt; font-family: Calibri, =
sans-serif; color: rgb(31, 73, 125);" class=3D""><o:p =
class=3D"">&nbsp;</o:p></span></div><div style=3D"margin: 0in 0in =
0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;" =
class=3D""><span style=3D"font-size: 11pt; font-family: Calibri, =
sans-serif; color: rgb(31, 73, 125);" class=3D""><o:p =
class=3D"">&nbsp;</o:p></span></div><div style=3D"margin: 0in 0in =
0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;" =
class=3D"">Linda<o:p class=3D""></o:p></div><div class=3D""><div =
style=3D"border-style: solid none none; border-top-color: rgb(225, 225, =
225); border-top-width: 1pt; padding: 3pt 0in 0in;" class=3D""><div =
style=3D"margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times =
New Roman', serif;" class=3D""><b class=3D""><span style=3D"font-size: =
11pt; font-family: Calibri, sans-serif;" class=3D"">From:</span></b><span =
style=3D"font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><span class=3D"Apple-converted-space">&nbsp;</span>I2nsf [<a =
href=3D"mailto:i2nsf-bounces@ietf.org" style=3D"color: purple; =
text-decoration: underline;" =
class=3D"">mailto:i2nsf-bounces@ietf.org</a>]<span =
class=3D"Apple-converted-space">&nbsp;</span><b class=3D"">On Behalf =
Of<span class=3D"Apple-converted-space">&nbsp;</span></b>Yoav Nir<br =
class=3D""><b class=3D"">Sent:</b><span =
class=3D"Apple-converted-space">&nbsp;</span>Wednesday, November 14, =
2018 12:33 PM<br class=3D""><b class=3D"">To:</b><span =
class=3D"Apple-converted-space">&nbsp;</span>Rafa Marin-Lopez &lt;<a =
href=3D"mailto:rafa@um.es" style=3D"color: purple; text-decoration: =
underline;" class=3D"">rafa@um.es</a>&gt;<br class=3D""><b =
class=3D"">Cc:</b><span class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"mailto:i2nsf@ietf.org" style=3D"color: purple; text-decoration: =
underline;" class=3D"">i2nsf@ietf.org</a>; Paul Wouters &lt;<a =
href=3D"mailto:paul@nohats.ca" style=3D"color: purple; text-decoration: =
underline;" class=3D"">paul@nohats.ca</a>&gt;<br class=3D""><b =
class=3D"">Subject:</b><span =
class=3D"Apple-converted-space">&nbsp;</span>Re: [I2nsf] Reviewing =
sdn-ipsec-flow-protection<o:p =
class=3D""></o:p></span></div></div></div><div style=3D"margin: 0in 0in =
0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;" =
class=3D""><o:p class=3D"">&nbsp;</o:p></div><div style=3D"margin: 0in =
0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;" =
class=3D"">Thanks, Rafa.<o:p class=3D""></o:p></div><div class=3D""><div =
style=3D"margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times =
New Roman', serif;" class=3D""><o:p =
class=3D"">&nbsp;</o:p></div></div><div class=3D""><div style=3D"margin: =
0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', =
serif;" class=3D"">Just one response below.<o:p =
class=3D""></o:p></div><div class=3D""><div style=3D"margin: 0in 0in =
0.0001pt; font-size: 12pt; font-family: 'Times New Roman', 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: =
0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', =
serif;" class=3D"">On 14 Nov 2018, at 11:30, Rafa Marin-Lopez &lt;<a =
href=3D"mailto:rafa@um.es" style=3D"color: purple; text-decoration: =
underline;" class=3D"">rafa@um.es</a>&gt; wrote:<o:p =
class=3D""></o:p></div></div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 12pt; font-family: 'Times New Roman', serif;" class=3D""><o:p =
class=3D"">&nbsp;</o:p></div><div class=3D""><div class=3D""><div =
style=3D"margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times =
New Roman', serif;" class=3D"">Hi Yoav:<o:p class=3D""></o:p></div><div =
class=3D""><div style=3D"margin: 0in 0in 0.0001pt; font-size: 12pt; =
font-family: 'Times New Roman', 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:=
 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', =
serif;" class=3D"">El 8 nov 2018, a las 17:11, Yoav Nir &lt;<a =
href=3D"mailto:ynir.ietf@gmail.com" style=3D"color: purple; =
text-decoration: underline;" class=3D"">ynir.ietf@gmail.com</a>&gt; =
escribi=C3=B3:<o:p class=3D""></o:p></div></div><div style=3D"margin: =
0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', =
serif;" class=3D""><o:p class=3D"">&nbsp;</o:p></div><div class=3D""><div =
class=3D""><div class=3D""><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 12pt; font-family: 'Times New Roman', serif;" class=3D"">Hi, =
all<o:p class=3D""></o:p></div><div class=3D""><div style=3D"margin: 0in =
0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;" =
class=3D""><o:p class=3D"">&nbsp;</o:p></div></div><div class=3D""><div =
style=3D"margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times =
New Roman', serif;" class=3D"">As discussed in the room, we need some =
reviewers for the sdn-ipsec-flow-protection draft ([1])<o:p =
class=3D""></o:p></div></div></div></div></div></blockquote><div =
class=3D""><div style=3D"margin: 0in 0in 0.0001pt; font-size: 12pt; =
font-family: 'Times New Roman', serif;" class=3D""><o:p =
class=3D"">&nbsp;</o:p></div></div><div style=3D"margin: 0in 0in =
0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;" =
class=3D"">Thanks for these comments. Please see our response below.<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 class=3D""><div class=3D""><div class=3D""><div =
style=3D"margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times =
New Roman', serif;" class=3D""><o:p =
class=3D"">&nbsp;</o:p></div></div><div class=3D""><div style=3D"margin: =
0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', =
serif;" class=3D"">While any comments on any part of the document are =
welcome, I would like people to concentrate on the following issues:<o:p =
class=3D""></o:p></div></div><div class=3D""><ul type=3D"disc" =
style=3D"margin-bottom: 0in;" class=3D""><li class=3D"MsoNormal" =
style=3D"margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times =
New Roman', serif;">The YANG model in Appendix A<o:p =
class=3D""></o:p></li></ul><ul type=3D"disc" style=3D"margin-bottom: =
0in;" class=3D""><ul type=3D"circle" style=3D"margin-bottom: 0in;" =
class=3D""><li class=3D"MsoNormal" style=3D"margin: 0in 0in 0.0001pt; =
font-size: 12pt; font-family: 'Times New Roman', serif;">Some of the =
crypto seems obsolete (example: DES). We would get into trouble in =
SecDir review. &nbsp;OTOH ChaCha20-Poly1305 is missing..<o:p =
class=3D""></o:p></li></ul></ul></div></div></div></div></blockquote><div =
class=3D""><div style=3D"margin: 0in 0in 0.0001pt; font-size: 12pt; =
font-family: 'Times New Roman', serif;" class=3D""><o:p =
class=3D"">&nbsp;</o:p></div></div><div class=3D""><div style=3D"margin: =
0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', =
serif;" class=3D"">Agree. We will remove DES and add the algorithm you =
mention.<o:p =
class=3D""></o:p></div></div></div></div></div></blockquote><div =
class=3D""><div style=3D"margin: 0in 0in 0.0001pt; font-size: 12pt; =
font-family: 'Times New Roman', serif;" class=3D""><o:p =
class=3D"">&nbsp;</o:p></div></div><div class=3D""><div style=3D"margin: =
0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', =
serif;" class=3D"">The TLS working group went quite far with TLS 1.3. =
&nbsp;Only 2 ciphers remain: AES-GCM with 16-byte ICV, and =
ChaCha20-Poly1305. That=E2=80=99s it. &nbsp;Specifically, they=E2=80=99ve =
deprecated everything that isn=E2=80=99t an AEAD.<o:p =
class=3D""></o:p></div></div><div class=3D""><div style=3D"margin: 0in =
0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;" =
class=3D""><o:p class=3D"">&nbsp;</o:p></div></div><div class=3D""><div =
style=3D"margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times =
New Roman', serif;" class=3D"">The IPsecME working group hasn=E2=80=99t =
gone that far yet. &nbsp;But in practice pretty much nothing is used =
except 3DES, AES-CBC, and AES-GCM. &nbsp;Perhaps ChaCha20-Poly1305 is =
starting to see some use by now. We have RFC 8221, especially sections 5 =
and 6. &nbsp;I think (although it=E2=80=99s up to the working group) =
that we should be fine defining only the MUSTs and the SHOULDs in those =
sections.<o:p class=3D""></o:p></div></div><div class=3D""><div =
style=3D"margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times =
New Roman', serif;" class=3D""><o:p =
class=3D"">&nbsp;</o:p></div></div><div class=3D""><div style=3D"margin: =
0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', =
serif;" class=3D"">That brings another question. What is our plan for =
future expansions? &nbsp;Suppose there=E2=80=99s some hot, new algorithm =
that everyone is implementing. How do you update the YANG model in the =
future when you add new values to the enumerations? &nbsp;Is it up to =
the administrator to make sure that the controller and NSFs are all on =
the =E2=80=9Csame page=E2=80=9D?<o:p class=3D""></o:p></div></div><div =
class=3D""><div style=3D"margin: 0in 0in 0.0001pt; font-size: 12pt; =
font-family: 'Times New Roman', serif;" class=3D""><o:p =
class=3D"">&nbsp;</o:p></div></div><div class=3D""><div style=3D"margin: =
0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', =
serif;" class=3D"">Thanks<o:p class=3D""></o:p></div></div><div =
class=3D""><div style=3D"margin: 0in 0in 0.0001pt; font-size: 12pt; =
font-family: 'Times New Roman', serif;" class=3D""><o:p =
class=3D"">&nbsp;</o:p></div></div><div class=3D""><div style=3D"margin: =
0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', =
serif;" class=3D"">Yoav<o:p =
class=3D""></o:p></div></div></div></div></div><span style=3D"font-family:=
 Courier; font-size: 14px; 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; =
float: none; display: inline !important;" =
class=3D"">_______________________________________________</span><br =
style=3D"font-family: Courier; font-size: 14px; 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""><span style=3D"font-family: =
Courier; font-size: 14px; 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; float: =
none; display: inline !important;" class=3D"">I2nsf mailing =
list</span><br style=3D"font-family: Courier; font-size: 14px; =
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""><a =
href=3D"mailto:I2nsf@ietf.org" style=3D"color: purple; text-decoration: =
underline; font-family: Courier; font-size: 14px; 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"">I2nsf@ietf.org</a><br =
style=3D"font-family: Courier; font-size: 14px; 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""><a =
href=3D"https://www.ietf.org/mailman/listinfo/i2nsf" style=3D"color: =
purple; text-decoration: underline; font-family: Courier; font-size: =
14px; 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"">https://www.ietf.org/mailman/listinfo/i2nsf</a></div></blockquo=
te></div><br class=3D""></div></body></html>=

--Apple-Mail=_477E673E-C439-4423-8D23-9400CCB51A21--


From nobody Thu Dec  6 02:14:24 2018
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 E333D130E23; Thu,  6 Dec 2018 02:14:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_PASS=-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 Pu-l5Wj0VnvZ; Thu,  6 Dec 2018 02:14:11 -0800 (PST)
Received: from xenon43.um.es (xenon43.um.es [IPv6:2001:720:1710:601::43]) by ietfa.amsl.com (Postfix) with ESMTP id 20A48130DCE; Thu,  6 Dec 2018 02:14:11 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by xenon43.um.es (Postfix) with ESMTP id C96D521703; Thu,  6 Dec 2018 11:14:08 +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 qf0OPW4UJpLa; Thu,  6 Dec 2018 11:14:08 +0100 (CET)
Received: from [192.168.1.36] (23.red-88-10-88.dynamicip.rima-tde.net [88.10.88.23]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: rafa) by xenon43.um.es (Postfix) with ESMTPSA id 74EA921730; Thu,  6 Dec 2018 11:14:05 +0100 (CET)
Content-Type: multipart/alternative; boundary="Apple-Mail=_541542A4-482B-4037-9C10-A3C4BA557473"
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
From: Rafa Marin Lopez <rafa@um.es>
In-Reply-To: <4A95BA014132FF49AE685FAB4B9F17F66B1F6237@SJCEML521-MBB.china.huawei.com>
Date: Thu, 6 Dec 2018 11:06:44 +0100
Cc: Rafa Marin Lopez <rafa@um.es>, Yoav Nir <ynir.ietf@gmail.com>, Gabriel Lopez <gabilm@um.es>, "i2nsf@ietf.org" <i2nsf@ietf.org>, "ipsec@ietf.org WG" <ipsec@ietf.org>, Paul Wouters <paul@nohats.ca>
Message-Id: <F9F55099-C1FD-4847-A093-8DABF22ADC9B@um.es>
References: <A881C135-9BF7-4E93-BB7A-75EB3D1FF605@gmail.com> <6839D47C-4074-486F-9350-8EB7B378036C@um.es> <DAE14995-8504-4134-B021-93D56A4994FB@gmail.com> <alpine.LRH.2.21.1811180149220.25604@bofh.nohats.ca> <3415DDC9-ED45-462F-B561-E48773E404FB@um.es> <alpine.LRH.2.21.1811270826430.2053@bofh.nohats.ca> <B47EE67E-1B50-44BB-9821-AB439CA2C2F1@um.es> <37F4E2D9-47C3-450C-B1E8-649FC901DA82@gmail.com> <4A95BA014132FF49AE685FAB4B9F17F66B1F6237@SJCEML521-MBB.china.huawei.com>
To: Linda Dunbar <linda.dunbar@huawei.com>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2nsf/oD4mOGSmHy-RrSEOkv5L-3MlbHw>
Subject: Re: [I2nsf] [IPsec] Review of draft-ietf-i2nsf-sdn-ipsec-flow-protection-03 (Section 1)
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, 06 Dec 2018 10:14:16 -0000

--Apple-Mail=_541542A4-482B-4037-9C10-A3C4BA557473
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Hi Linda:

I still have doubts about these terms. In both cases, there is a =
centralized key distribution: with IKE , the controller may distribute =
key material (i.g. the PSK for IKE authentication) or some =
certification. Without IKE  (case 2) the centralized key distribution =
refers to IPsec SAs.=20

Moreover the word IKE is important in case 1 , only IKEv2 is considered.=20=


Best Regards.


> El 5 dic 2018, a las 22:29, Linda Dunbar <linda.dunbar@huawei.com> =
escribi=C3=B3:
>=20
> I like the title of  =E2=80=9Cdistributed keying=E2=80=9D (case 1) vs =
=E2=80=9Ccentralized keying=E2=80=9D (Case 2).
> =20
> Linda
> =C2=A0 <>
> From: I2nsf [mailto:i2nsf-bounces@ietf.org] On Behalf Of Yoav Nir
> Sent: Tuesday, November 27, 2018 4:39 PM
> To: Gabriel Lopez <gabilm@um.es>
> Cc: i2nsf@ietf.org; ipsec@ietf.org WG <ipsec@ietf.org>; Paul Wouters =
<paul@nohats.ca>; Rafa Marin Lopez <rafa@um.es>
> Subject: Re: [I2nsf] [IPsec] Review of =
draft-ietf-i2nsf-sdn-ipsec-flow-protection-03 (Section 1)
> =20
> A couple of remarks (with no hats)
> =20
> If we=E2=80=99re bikeshedding the names, I think the difference is =
that in one case the two NSFs generate traffic keys between themselves, =
and in the other it is the controller that generates the keys for them.  =
So how about =E2=80=9Cdistributed keying=E2=80=9D vs =E2=80=9Ccentralized =
keying=E2=80=9D, or perhaps =E2=80=9Cautomatic keying=E2=80=9D vs =E2=80=9C=
SDN keying=E2=80=9D.
> =20
> =20
> Also, I have been asked by someone not on this list whether our work =
covers the road warrior use case. I said it didn=E2=80=99t and wondered =
why. So I got these points:
> Road warriors are numerous and not where the administrator can =
configure them manually.
> Additionally, the configuration of what networks, gateways (NSFs), and =
resources a road warrior may access (in IPsec terms, the SPD and PAD) =
change often.
> Because of the above, some automatic method of configuring SPD and PAD =
is needed.
> There is also the issue of multiple VPN gateways covering similar =
domains, and VPN gateways being overloaded or down for maintenance, as =
well as malfunctions in the network behind those VPN gateways. So the =
decision on which gateway a road warrior should use to access a =
particular resource is also a natural question to ask an SDN controller.
> =20
> Since I used to work for a VPN vendor, I can tell you what our product =
did:
> The current configuration was formatted (automatically by a management =
function) as a text file that the road warrior downloaded through the =
VPN gateway (the gateway doubled as a server serving this one file)
> The proper gateway to connect to was determined by pinging all =
gateways that were possible according to the configuration file.
> This did not account for any internal networking issues.
> =20
> I don=E2=80=99t know if this should be part of *this* effort, but =
there is a use case for road warrior SDN.
> =20
> Yoav


--Apple-Mail=_541542A4-482B-4037-9C10-A3C4BA557473
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; -webkit-line-break: after-white-space;" =
class=3D"">Hi Linda:<div class=3D""><br class=3D""></div><div class=3D"">I=
 still have doubts about these terms. In both cases, there is a =
centralized key distribution: with IKE , the controller may distribute =
key material (i.g. the PSK for IKE authentication) or some =
certification. Without IKE &nbsp;(case 2) the centralized key =
distribution refers to IPsec SAs.&nbsp;</div><div class=3D""><br =
class=3D""></div><div class=3D"">Moreover the word IKE is important in =
case 1 , only IKEv2 is considered.&nbsp;</div><div class=3D""><br =
class=3D""></div><div class=3D"">Best Regards.</div><div class=3D""><br =
class=3D""></div><div class=3D""><br class=3D""><div><blockquote =
type=3D"cite" class=3D""><div class=3D"">El 5 dic 2018, a las 22:29, =
Linda Dunbar &lt;<a href=3D"mailto:linda.dunbar@huawei.com" =
class=3D"">linda.dunbar@huawei.com</a>&gt; escribi=C3=B3:</div><br =
class=3D"Apple-interchange-newline"><div class=3D""><div =
class=3D"WordSection1" style=3D"page: WordSection1; font-family: =
Courier; font-size: 14px; 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;"><div =
style=3D"margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times =
New Roman', serif;" class=3D"">I like the title of<span =
style=3D"font-size: 11pt; font-family: Calibri, sans-serif; color: =
rgb(31, 73, 125);" class=3D""><span =
class=3D"Apple-converted-space">&nbsp;</span>&nbsp;</span>=E2=80=9Cdistrib=
uted keying=E2=80=9D (case 1) vs =E2=80=9Ccentralized keying=E2=80=9D =
(Case 2).<o:p class=3D""></o:p></div><div style=3D"margin: 0in 0in =
0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;" =
class=3D""><o:p class=3D"">&nbsp;</o:p></div><div style=3D"margin: 0in =
0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;" =
class=3D"">Linda<span style=3D"font-size: 11pt; font-family: Calibri, =
sans-serif; color: rgb(31, 73, 125);" class=3D""><o:p =
class=3D""></o:p></span></div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 12pt; font-family: 'Times New Roman', serif;" class=3D""><a =
name=3D"_MailEndCompose" class=3D""><span style=3D"font-size: 11pt; =
font-family: Calibri, sans-serif; color: rgb(31, 73, 125);" =
class=3D""><o:p class=3D"">&nbsp;</o:p></span></a></div><div =
class=3D""><div style=3D"border-style: solid none none; =
border-top-color: rgb(225, 225, 225); border-top-width: 1pt; padding: =
3pt 0in 0in;" class=3D""><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 12pt; font-family: 'Times New Roman', serif;" class=3D""><b =
class=3D""><span style=3D"font-size: 11pt; font-family: Calibri, =
sans-serif;" class=3D"">From:</span></b><span style=3D"font-size: 11pt; =
font-family: Calibri, sans-serif;" class=3D""><span =
class=3D"Apple-converted-space">&nbsp;</span>I2nsf [<a =
href=3D"mailto:i2nsf-bounces@ietf.org" =
class=3D"">mailto:i2nsf-bounces@ietf.org</a>]<span =
class=3D"Apple-converted-space">&nbsp;</span><b class=3D"">On Behalf =
Of<span class=3D"Apple-converted-space">&nbsp;</span></b>Yoav Nir<br =
class=3D""><b class=3D"">Sent:</b><span =
class=3D"Apple-converted-space">&nbsp;</span>Tuesday, November 27, 2018 =
4:39 PM<br class=3D""><b class=3D"">To:</b><span =
class=3D"Apple-converted-space">&nbsp;</span>Gabriel Lopez &lt;<a =
href=3D"mailto:gabilm@um.es" class=3D"">gabilm@um.es</a>&gt;<br =
class=3D""><b class=3D"">Cc:</b><span =
class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"mailto:i2nsf@ietf.org" class=3D"">i2nsf@ietf.org</a>; <a =
href=3D"mailto:ipsec@ietf.org" class=3D"">ipsec@ietf.org</a> WG &lt;<a =
href=3D"mailto:ipsec@ietf.org" class=3D"">ipsec@ietf.org</a>&gt;; Paul =
Wouters &lt;<a href=3D"mailto:paul@nohats.ca" =
class=3D"">paul@nohats.ca</a>&gt;; Rafa Marin Lopez &lt;<a =
href=3D"mailto:rafa@um.es" class=3D"">rafa@um.es</a>&gt;<br class=3D""><b =
class=3D"">Subject:</b><span =
class=3D"Apple-converted-space">&nbsp;</span>Re: [I2nsf] [IPsec] Review =
of draft-ietf-i2nsf-sdn-ipsec-flow-protection-03 (Section 1)<o:p =
class=3D""></o:p></span></div></div></div><div style=3D"margin: 0in 0in =
0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;" =
class=3D""><o:p class=3D"">&nbsp;</o:p></div><div style=3D"margin: 0in =
0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;" =
class=3D"">A couple of remarks (with no hats)<o:p =
class=3D""></o:p></div><div class=3D""><div style=3D"margin: 0in 0in =
0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;" =
class=3D""><o:p class=3D"">&nbsp;</o:p></div></div><div class=3D""><div =
style=3D"margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times =
New Roman', serif;" class=3D"">If we=E2=80=99re bikeshedding the names, =
I think the difference is that in one case the two NSFs generate traffic =
keys between themselves, and in the other it is the controller that =
generates the keys for them. &nbsp;So how about =E2=80=9Cdistributed =
keying=E2=80=9D vs =E2=80=9Ccentralized keying=E2=80=9D, or perhaps =
=E2=80=9Cautomatic keying=E2=80=9D vs =E2=80=9CSDN keying=E2=80=9D.<o:p =
class=3D""></o:p></div></div><div class=3D""><div style=3D"margin: 0in =
0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;" =
class=3D""><o:p class=3D"">&nbsp;</o:p></div></div><div class=3D""><div =
style=3D"margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times =
New Roman', serif;" class=3D""><o:p =
class=3D"">&nbsp;</o:p></div></div><div class=3D""><div style=3D"margin: =
0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', =
serif;" class=3D"">Also, I have been asked by someone not on this list =
whether our work covers the road warrior use case. I said it didn=E2=80=99=
t and wondered why. So I got these points:<o:p =
class=3D""></o:p></div></div><div class=3D""><ul type=3D"disc" =
style=3D"margin-bottom: 0in;" class=3D""><li class=3D"MsoNormal" =
style=3D"margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times =
New Roman', serif;">Road warriors are numerous and not where the =
administrator can configure them manually.<o:p class=3D""></o:p></li><li =
class=3D"MsoNormal" style=3D"margin: 0in 0in 0.0001pt; font-size: 12pt; =
font-family: 'Times New Roman', serif;">Additionally, the configuration =
of what networks, gateways (NSFs), and resources a road warrior may =
access (in IPsec terms, the SPD and PAD) change often.<o:p =
class=3D""></o:p></li><li class=3D"MsoNormal" style=3D"margin: 0in 0in =
0.0001pt; font-size: 12pt; font-family: 'Times New Roman', =
serif;">Because of the above, some automatic method of configuring SPD =
and PAD is needed.<o:p class=3D""></o:p></li><li class=3D"MsoNormal" =
style=3D"margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times =
New Roman', serif;">There is also the issue of multiple VPN gateways =
covering similar domains, and VPN gateways being overloaded or down for =
maintenance, as well as malfunctions in the network behind those VPN =
gateways. So the decision on which gateway a road warrior should use to =
access a particular resource is also a natural question to ask an SDN =
controller.<o:p class=3D""></o:p></li></ul><div class=3D""><div =
style=3D"margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times =
New Roman', serif;" class=3D""><o:p =
class=3D"">&nbsp;</o:p></div></div></div><div class=3D""><div =
style=3D"margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times =
New Roman', serif;" class=3D"">Since I used to work for a VPN vendor, I =
can tell you what our product did:<o:p class=3D""></o:p></div></div><div =
class=3D""><ul type=3D"disc" style=3D"margin-bottom: 0in;" class=3D""><li =
class=3D"MsoNormal" style=3D"margin: 0in 0in 0.0001pt; font-size: 12pt; =
font-family: 'Times New Roman', serif;">The current configuration was =
formatted (automatically by a management function) as a text file that =
the road warrior downloaded through the VPN gateway (the gateway doubled =
as a server serving this one file)<o:p class=3D""></o:p></li><li =
class=3D"MsoNormal" style=3D"margin: 0in 0in 0.0001pt; font-size: 12pt; =
font-family: 'Times New Roman', serif;">The proper gateway to connect to =
was determined by pinging all gateways that were possible according to =
the configuration file.<o:p class=3D""></o:p></li><li class=3D"MsoNormal" =
style=3D"margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times =
New Roman', serif;">This did not account for any internal networking =
issues.<o:p class=3D""></o:p></li></ul><div class=3D""><div =
style=3D"margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times =
New Roman', serif;" class=3D""><o:p =
class=3D"">&nbsp;</o:p></div></div></div><div class=3D""><div =
style=3D"margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times =
New Roman', serif;" class=3D"">I don=E2=80=99t know if this should be =
part of *this* effort, but there is a use case for road warrior SDN.<o:p =
class=3D""></o:p></div></div><div class=3D""><div style=3D"margin: 0in =
0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;" =
class=3D""><o:p class=3D"">&nbsp;</o:p></div></div><div class=3D""><div =
style=3D"margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times =
New Roman', serif;" =
class=3D"">Yoav</div></div></div></div></blockquote></div><br =
class=3D""></div></body></html>=

--Apple-Mail=_541542A4-482B-4037-9C10-A3C4BA557473--


From nobody Thu Dec  6 02:49:40 2018
Return-Path: <fnumber@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 AD7BE130E61 for <i2nsf@ietfa.amsl.com>; Thu,  6 Dec 2018 02:49:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level: 
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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 qacOQ0X6pZuV for <i2nsf@ietfa.amsl.com>; Thu,  6 Dec 2018 02:49:33 -0800 (PST)
Received: from mail-pf1-x42b.google.com (mail-pf1-x42b.google.com [IPv6:2607:f8b0:4864:20::42b]) (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 C87C0130E23 for <i2nsf@ietf.org>; Thu,  6 Dec 2018 02:49:33 -0800 (PST)
Received: by mail-pf1-x42b.google.com with SMTP id b85so738pfc.3 for <i2nsf@ietf.org>; Thu, 06 Dec 2018 02:49:33 -0800 (PST)
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=+ohKwQSgEphHracOGGIl+xTHIzVdqQNg2HJTA+tTGa0=; b=oAi2Ph85zRC0AkRaqIxkK5WROEcspq+aQ/tCtU++zOZbuTvBgjQzwqBvMczpc9MaCw ZxPhq+ig6Rrgk4ObIP9q3WV2TYltg7ZAQUwVHuut/RB2R/vLmWau4dKyOWSAJ4P/I1Xk Kd5aTGVhWtd9MDafXXLiurSUYWrqXQHdFGaQ01AXZYm7ImVuC5903vABltjGC+o/JPtP Ng2EaGSUahEOLuGdyxqpRXunfCZUZljxGje7ytvFHHzd5sbLK6gGElnxwUjgvyanTaPo EGr2v5AZ8dZzk38Tx8zocKKv3Qprp8mB1VZPe1CBHfcsJzxe1I1HofPi2X1ViCOkcQRz vZOA==
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=+ohKwQSgEphHracOGGIl+xTHIzVdqQNg2HJTA+tTGa0=; b=UIf/PuTnKwFpWdfstJ3zQ7g1fX6y/JngvWu2gGiYaX18uAZ5Rn+hnCdiS7AZk5Uxil Kztj4D0Nn1O2R1g58loyiR7ARIFBP766viHMGeJrLsVTi9rul+QcO1VUxaI1S2lh7xkn R3rE2VVXY9t2rB17NE4XdnEZFnjG07hD6rxTVQpq9v6hls4JvHenotNC87Nf/y2+bVxs 18zSxGlSdFMfS5obMLO7UDzOiI9o2fln35SYrmQPl0bvRXeGcuP1AM0cSNwRrJzo7Y/o L25HjvyHGCGeqOr70NLJ1EHjhdYjb9/o6ghSuDWQXYQH9aLan+eSjvp8+nUJvQUCzzdL gA/w==
X-Gm-Message-State: AA+aEWZJhYtn3nSCPw4VyA1+b5hr/+vOOzpu514TkvRHAVXaGsvG5UT7 YlCdQGXfWLiBn5d6ai80udfInlEm7nRn/GQ2zmutgp8eCrkX0Q==
X-Google-Smtp-Source: AFSGD/VITNAEwN1JF4GB1fG/ZWavLZDLiu8O5X76gSwy5XGK3pz/1eQEgLGvAvSWb0L50g+lJugB0nimrjHFjnTNHD4=
X-Received: by 2002:a63:e915:: with SMTP id i21mr23117339pgh.409.1544093373132;  Thu, 06 Dec 2018 02:49:33 -0800 (PST)
MIME-Version: 1.0
References: <4A95BA014132FF49AE685FAB4B9F17F66B1F6399@SJCEML521-MBB.china.huawei.com>
In-Reply-To: <4A95BA014132FF49AE685FAB4B9F17F66B1F6399@SJCEML521-MBB.china.huawei.com>
From: Jung-Soo Park <fnumber@gmail.com>
Date: Thu, 6 Dec 2018 19:49:21 +0900
Message-ID: <CAE9rxx7BcR0L7Xo-y1zz3A2uUHzKWuUjWBCy+Fo8RkaYQGA3vw@mail.gmail.com>
To: linda.dunbar@huawei.com
Cc: i2nsf@ietf.org
Content-Type: multipart/alternative; boundary="000000000000017593057c584168"
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2nsf/CF2oOGTEa73XbwEP6Jiq-5zVddE>
Subject: Re: [I2nsf] Call for WG Adoption on NSF Monitoring 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, 06 Dec 2018 10:49:39 -0000

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

Hi I2NSF WG,
I strongly support the WG adoption of this NSF Monitoring Data Model draft
document.

The NSF monitoring is very important feature in order to maintain the I2NSF
framework.
It can monitor the functionalities of NSFs and detect suspicious or
malicious activities.
This draft will support the security business model with the data and
information model for NSF monitoring.

Thanks.

Jungsoo, PARK

On Thu, Dec 6, 2018 at 7:31 AM Linda Dunbar <linda.dunbar@huawei.com> wrote=
:

> This is the start of a two weeks call for input on the WG adoption of the
> document:
> https://tools.ietf.org/html/draft-hong-i2nsf-nsf-monitoring-data-model-06
>
>
>
> Thanks for the authors of the two I2NSF Monitoring drafts taking actions
> of merging the content.
>
> We need more of those actions. As of now we have 8 WG drafts. We need to
> finish them next few months.
>
>
>
> Bear in mind that WG adoption doesn=E2=80=99t mean the draft is ready, on=
ly means
> that WG will work together on the draft (instead of individuals).
>
>
>
> Please provide feedback to the list/chairs if you believe that this
> document should be adopted as a WG document.
>
>
>
> Thanks,
>
>
>
> Linda & Yoav
>
>
>
> *From:* Mr. Jaehoon Paul Jeong [mailto:jaehoon.paul@gmail.com]
> *Sent:* Thursday, November 15, 2018 6:35 PM
> *To:* Linda Dunbar <linda.dunbar@huawei.com>; Yoav Nir <
> ynir.ietf@gmail.com>
> *Cc:* i2nsf@ietf.org; skku_secu-brain_all@googlegroups.com; Sangwon Hyun =
<
> swhyun77@gmail.com>; Mr. Jaehoon Paul Jeong <jaehoon.paul@gmail.com>
> *Subject:* Request for WG Adoption Call on NSF Monitoring Draft
>
>
>
> Hi Linda and Yoav,
>
> As we discussed the last Bangkok meeting,
>
> I have merged the two drafts of Information Model and Data Model
>
> for NSF Monitoring into a new draft called
> draft-hong-i2nsf-nsf-monitoring-data-model-06:
>
>
>
> - Two Information and Data Model Drafts
>
>  . draft-zhang-i2nsf-info-model-monitoring-07
>
>  . draft-hong-i2nsf-nsf-monitoring-data-model-05
>
>
>
> - A Merged Data Model Draft
>
>  . draft-hong-i2nsf-nsf-monitoring-data-model-06
>
>  .
> https://tools.ietf.org/html/draft-hong-i2nsf-nsf-monitoring-data-model-06
>
>
>
> The NSF monitoring is very important to manage the I2NSF security service
> system
>
> in a reliable and scalable fashion.
>
>
>
> Could you start a WG adoption call for this draft?
>
>
>
> Thanks.
>
>
>
> Best Regards,
>
> Paul
>
> --
>
> =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 Software
> 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>
> _______________________________________________
> I2nsf mailing list
> I2nsf@ietf.org
> https://www.ietf.org/mailman/listinfo/i2nsf
>


--=20
Dr. JungSoo PARK
-----------------
Network Standardization Team
Electronics and Telecommunications Research Institute (ETRI), Korea
Tel:+82-42-860-6514, Fax:861-5404
MSN: fnumber@msn.com, E-mail : pjs@etri.re.kr

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

<div dir=3D"ltr"><div dir=3D"ltr"><div style=3D"color:rgb(0,0,0);font-famil=
y:-webkit-standard">Hi I2NSF WG,</div><div style=3D"color:rgb(0,0,0);font-f=
amily:-webkit-standard">I strongly support the WG adoption of this NSF Moni=
toring Data Model draft document.</div><div style=3D"color:rgb(0,0,0);font-=
family:-webkit-standard"><br></div><div style=3D"color:rgb(0,0,0);font-fami=
ly:-webkit-standard">The NSF monitoring is very important feature in order =
to maintain the I2NSF framework.</div><div style=3D"color:rgb(0,0,0);font-f=
amily:-webkit-standard">It can monitor the functionalities of NSFs and dete=
ct suspicious or malicious activities.</div><div style=3D"color:rgb(0,0,0);=
font-family:-webkit-standard">This draft will support the security business=
 model with the data and information model for NSF monitoring.</div><div st=
yle=3D"color:rgb(0,0,0);font-family:-webkit-standard"><br></div><div style=
=3D"color:rgb(0,0,0);font-family:-webkit-standard">Thanks.</div><div style=
=3D"color:rgb(0,0,0);font-family:-webkit-standard"><br></div><div style=3D"=
color:rgb(0,0,0);font-family:-webkit-standard">Jungsoo, PARK</div><br><div =
class=3D"gmail_quote"><div dir=3D"ltr">On Thu, Dec 6, 2018 at 7:31 AM Linda=
 Dunbar &lt;<a href=3D"mailto:linda.dunbar@huawei.com">linda.dunbar@huawei.=
com</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"marg=
in:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-l=
eft-color:rgb(204,204,204);padding-left:1ex">





<div lang=3D"EN-US">
<div class=3D"gmail-m_-5998671876284642785WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:11pt;font-family:Calibri,sa=
ns-serif;color:rgb(31,73,125)">This is the start of a two weeks call for in=
put on the WG adoption of the document:
</span><a href=3D"https://tools.ietf.org/html/draft-hong-i2nsf-nsf-monitori=
ng-data-model-06" target=3D"_blank">https://tools.ietf.org/html/draft-hong-=
i2nsf-nsf-monitoring-data-model-06</a><span style=3D"font-size:11pt;font-fa=
mily:Calibri,sans-serif;color:rgb(31,73,125)"><u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11pt;font-family:Calibri,sa=
ns-serif;color:rgb(31,73,125)"><u></u>=C2=A0<u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11pt;font-family:Calibri,sa=
ns-serif;color:rgb(31,73,125)">Thanks for the authors of the two I2NSF Moni=
toring drafts taking actions of merging the content.
<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11pt;font-family:Calibri,sa=
ns-serif;color:rgb(31,73,125)">We need more of those actions. As of now we =
have 8 WG drafts. We need to finish them next few months.
<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11pt;font-family:Calibri,sa=
ns-serif;color:rgb(31,73,125)"><u></u>=C2=A0<u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11pt;font-family:Calibri,sa=
ns-serif;color:rgb(31,73,125)">Bear in mind that WG adoption doesn=E2=80=99=
t mean the draft is ready, only means that WG will work together on the dra=
ft (instead of individuals).
<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11pt;font-family:Calibri,sa=
ns-serif;color:rgb(31,73,125)"><u></u>=C2=A0<u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11pt;font-family:Calibri,sa=
ns-serif;color:rgb(31,73,125)">Please provide feedback to the list/chairs i=
f you believe that this document should be adopted as a WG document.<u></u>=
<u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11pt;font-family:Calibri,sa=
ns-serif;color:rgb(31,73,125)"><u></u>=C2=A0<u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11pt;font-family:Calibri,sa=
ns-serif;color:rgb(31,73,125)">Thanks,
<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11pt;font-family:Calibri,sa=
ns-serif;color:rgb(31,73,125)"><u></u>=C2=A0<u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11pt;font-family:Calibri,sa=
ns-serif;color:rgb(31,73,125)">Linda &amp; Yoav<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11pt;font-family:Calibri,sa=
ns-serif;color:rgb(31,73,125)"><u></u><u></u></span></p>
<p class=3D"MsoNormal"><a name=3D"m_-5998671876284642785__MailEndCompose"><=
span style=3D"font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73=
,125)"><u></u>=C2=A0<u></u></span></a></p>
<p class=3D"MsoNormal"><b><span style=3D"font-size:11pt;font-family:Calibri=
,sans-serif">From:</span></b><span style=3D"font-size:11pt;font-family:Cali=
bri,sans-serif"> Mr. Jaehoon Paul Jeong [mailto:<a href=3D"mailto:jaehoon.p=
aul@gmail.com" target=3D"_blank">jaehoon.paul@gmail.com</a>]
<br>
<b>Sent:</b> Thursday, November 15, 2018 6:35 PM<br>
<b>To:</b> Linda Dunbar &lt;<a href=3D"mailto:linda.dunbar@huawei.com" targ=
et=3D"_blank">linda.dunbar@huawei.com</a>&gt;; Yoav Nir &lt;<a href=3D"mail=
to:ynir.ietf@gmail.com" target=3D"_blank">ynir.ietf@gmail.com</a>&gt;<br>
<b>Cc:</b> <a href=3D"mailto:i2nsf@ietf.org" target=3D"_blank">i2nsf@ietf.o=
rg</a>; <a href=3D"mailto:skku_secu-brain_all@googlegroups.com" target=3D"_=
blank">skku_secu-brain_all@googlegroups.com</a>; Sangwon Hyun &lt;<a href=
=3D"mailto:swhyun77@gmail.com" target=3D"_blank">swhyun77@gmail.com</a>&gt;=
; Mr. Jaehoon Paul Jeong &lt;<a href=3D"mailto:jaehoon.paul@gmail.com" targ=
et=3D"_blank">jaehoon.paul@gmail.com</a>&gt;<br>
<b>Subject:</b> Request for WG Adoption Call on NSF Monitoring Draft<u></u>=
<u></u></span></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<div>
<div>
<div>
<p class=3D"MsoNormal">Hi Linda and Yoav,<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">As we discussed the last Bangkok meeting,<u></u><u><=
/u></p>
</div>
<div>
<p class=3D"MsoNormal">I have merged the two drafts of Information Model an=
d Data Model<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">for NSF Monitoring into a new draft called draft-hon=
g-i2nsf-nsf-monitoring-data-model-06:<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">- Two Information and Data Model Drafts<u></u><u></u=
></p>
</div>
<div>
<p class=3D"MsoNormal">=C2=A0. draft-zhang-i2nsf-info-model-monitoring-07=
=C2=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=C2=A0. draft-hong-i2nsf-nsf-monitoring-data-model-0=
5<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">- A Merged Data Model Draft=C2=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=C2=A0. draft-hong-i2nsf-nsf-monitoring-data-model-0=
6<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=C2=A0. <a href=3D"https://tools.ietf.org/html/draft=
-hong-i2nsf-nsf-monitoring-data-model-06" target=3D"_blank">
https://tools.ietf.org/html/draft-hong-i2nsf-nsf-monitoring-data-model-06</=
a><u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">The NSF monitoring is very important to manage the I=
2NSF security service system<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">in a reliable and scalable fashion.<u></u><u></u></p=
>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Could you start a WG adoption call for this draft?<u=
></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Thanks.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Best Regards,<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Paul<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">--=C2=A0<u></u><u></u></p>
</div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<p class=3D"MsoNormal">=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 Software<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" target=3D"_b=
lank"><span style=3D"font-size:9.5pt">pauljeong@skku.edu</span></a><br>
Personal Homepage: <a href=3D"http://cpslab.skku.edu/people-jaehoon-jeong.p=
hp" target=3D"_blank">
http://iotlab.skku.edu/people-jaehoon-jeong.php</a><u></u><u></u></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</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"=
 class=3D"gmail_signature">Dr. JungSoo PARK<br>-----------------<br>Network=
 Standardization Team<br>Electronics and Telecommunications Research Instit=
ute (ETRI), Korea<br>Tel:+82-42-860-6514, Fax:861-5404<br>MSN: <a href=3D"m=
ailto:fnumber@msn.com" target=3D"_blank">fnumber@msn.com</a>, E-mail : <a h=
ref=3D"mailto:pjs@etri.re.kr" target=3D"_blank">pjs@etri.re.kr</a></div></d=
iv></div>

--000000000000017593057c584168--


From nobody Thu Dec  6 04:12:16 2018
Return-Path: <yangun@dcn.ssu.ac.kr>
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 7BA4B130DCC for <i2nsf@ietfa.amsl.com>; Thu,  6 Dec 2018 04:12:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.357
X-Spam-Level: 
X-Spam-Status: No, score=-3.357 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-1.459, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=dcn-ssu-ac-kr.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 HjANvi2rBYBY for <i2nsf@ietfa.amsl.com>; Thu,  6 Dec 2018 04:12:09 -0800 (PST)
Received: from mail-pg1-x52b.google.com (mail-pg1-x52b.google.com [IPv6:2607:f8b0:4864:20::52b]) (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 9914A1277CC for <i2nsf@ietf.org>; Thu,  6 Dec 2018 04:12:09 -0800 (PST)
Received: by mail-pg1-x52b.google.com with SMTP id 80so83516pge.4 for <i2nsf@ietf.org>; Thu, 06 Dec 2018 04:12:09 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=dcn-ssu-ac-kr.20150623.gappssmtp.com; s=20150623; h=from:to:references:in-reply-to:subject:date:message-id:mime-version :content-language:thread-index; bh=ulZnCOT+Fr+Xg2xZLqxWCIspd2pX36QheuOj4rmIsnE=; b=R0HtVmfkmVP0of8lf1Vlj1sIF8e89+rGpJSwwyjFeBCQmqITLrVwgXGNzTK64i6Tvc uDWQlZovKG09K6Q5fE2owI6X2PF1pY4RK9gzq+AGO5MWjVQHUS/c1XM/HmkGbvrk7F3H QiuPOQHBVHrJpWJdq5FWKLMt73fTdtZDV3Wn4dfTUMthSqMu6JC3Sz0WsQxZS1uLM78Q Z0a34/5SMGzpUWhj3ReFkabF+mVFo1uckjD4aFONFa15n2A+V0yJhcaZ4MIVWRBLSrhG NSI3mVJ4Z30fItiesB8JH09wvZCXJOP8UDqnpqyuavLCQRzwKsESIBlDzUhtnRVLTpE6 EbzQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:references:in-reply-to:subject:date :message-id:mime-version:content-language:thread-index; bh=ulZnCOT+Fr+Xg2xZLqxWCIspd2pX36QheuOj4rmIsnE=; b=jXPbZnuiBVWys62E2D2JDoUy0ZxpvrA7MHgpktipgvhO5fFXwIW/Zds3NR0xC8sngJ 34oGS75HKoyDUq+9Hff3BjNoe6Ob6clQrwc7ecffmvqzwuCMMbIXCtHLtp/CxbvXXD7+ 5CD8QryONHGwHsvLLGv2VxJHYwob6k3qw+1Jmxx5O5LIlxLCBSBwEJ4tYEk9GAUvNKtA kxWXeTIjUtrPPjWJjo1jIQbbxo8JC8sL8nfhnEEzCtEKhpKtzbZSN7lfg5LyOpZ+vigl mW2pejJUE45rQAIHN6Zoul4JVxPOnqMU+Kk51FpV5LiH8FVIk741ggicCr7znSazGKVj 8lDw==
X-Gm-Message-State: AA+aEWaMS4Xlhr8B2qIP8kAoKOEMbke1MVHpZegakNdUwoUVk7O3L/C4 oYQ8xXkYoTymEHAuR8yb++sRYv4fa38=
X-Google-Smtp-Source: AFSGD/Xdyj/v+Df7EGEJ01eXd3zoOXZ7DR8DTG2ztJt2B+8iqQdPQwXOnOkHDRMtd+pVLysEqcaRhQ==
X-Received: by 2002:a62:cd44:: with SMTP id o65mr28103171pfg.222.1544098328217;  Thu, 06 Dec 2018 04:12:08 -0800 (PST)
Received: from hyunchic ([39.115.19.177]) by smtp.gmail.com with ESMTPSA id l69sm336159pfb.75.2018.12.06.04.12.06 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 06 Dec 2018 04:12:07 -0800 (PST)
From: <yangun@dcn.ssu.ac.kr>
To: "'Linda Dunbar'" <linda.dunbar@huawei.com>, <i2nsf@ietf.org>
References: <4A95BA014132FF49AE685FAB4B9F17F66B1F6399@SJCEML521-MBB.china.huawei.com>
In-Reply-To: <4A95BA014132FF49AE685FAB4B9F17F66B1F6399@SJCEML521-MBB.china.huawei.com>
Date: Thu, 6 Dec 2018 21:12:02 +0900
Message-ID: <ea3b01d48d5c$e69cf260$b3d6d720$@dcn.ssu.ac.kr>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_EA3C_01D48DA8.56866F20"
X-Mailer: Microsoft Outlook 16.0
Content-Language: ko
Thread-Index: AQM2ITJY/SI2/32U7WIJXz92vB5d1aKudZsA
x-officeplugin-mail-id: 83c16811e0ea4da59b8f9daddaa4f584
x-officeplugin-issue: 0
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2nsf/uC9EhYUiFGjNIllI-hLLYtPsZ1g>
Subject: Re: [I2nsf] Call for WG Adoption on NSF Monitoring 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, 06 Dec 2018 12:12:14 -0000

This is a multipart message in MIME format.

------=_NextPart_000_EA3C_01D48DA8.56866F20
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Hello  I2NSF WG, 

 

I fully support the WG adoption of this NSF Monitoring Data Model draft. 

This draft provides a comprehensive and concise data model for the security
industry along with an information model for NSF monitoring. 

Likewise it also provides an efficient way to monitor the functionality and
load of NSFs.

I think  this draft will be helpful for the I2NSF framework.

 

Thanks

 

Hyunsik Yang

 

From: I2nsf <i2nsf-bounces@ietf.org> On Behalf Of Linda Dunbar
Sent: Thursday, December 6, 2018 7:32 AM
To: i2nsf@ietf.org
Subject: [I2nsf] Call for WG Adoption on NSF Monitoring Draft

 

This is the start of a two weeks call for input on the WG adoption of the
document:
https://tools.ietf.org/html/draft-hong-i2nsf-nsf-monitoring-data-model-06

 

Thanks for the authors of the two I2NSF Monitoring drafts taking actions of
merging the content. 

We need more of those actions. As of now we have 8 WG drafts. We need to
finish them next few months. 

 

Bear in mind that WG adoption doesn't mean the draft is ready, only means
that WG will work together on the draft (instead of individuals). 

 

Please provide feedback to the list/chairs if you believe that this document
should be adopted as a WG document.

 

Thanks, 

 

Linda & Yoav

 

 

From: Mr. Jaehoon Paul Jeong [mailto:jaehoon.paul@gmail.com] 
Sent: Thursday, November 15, 2018 6:35 PM
To: Linda Dunbar <linda.dunbar@huawei.com <mailto:linda.dunbar@huawei.com>
>; Yoav Nir <ynir.ietf@gmail.com <mailto:ynir.ietf@gmail.com> >
Cc: i2nsf@ietf.org <mailto:i2nsf@ietf.org> ;
skku_secu-brain_all@googlegroups.com
<mailto:skku_secu-brain_all@googlegroups.com> ; Sangwon Hyun
<swhyun77@gmail.com <mailto:swhyun77@gmail.com> >; Mr. Jaehoon Paul Jeong
<jaehoon.paul@gmail.com <mailto:jaehoon.paul@gmail.com> >
Subject: Request for WG Adoption Call on NSF Monitoring Draft

 

Hi Linda and Yoav,

As we discussed the last Bangkok meeting,

I have merged the two drafts of Information Model and Data Model

for NSF Monitoring into a new draft called
draft-hong-i2nsf-nsf-monitoring-data-model-06:

 

- Two Information and Data Model Drafts

 . draft-zhang-i2nsf-info-model-monitoring-07 

 . draft-hong-i2nsf-nsf-monitoring-data-model-05

 

- A Merged Data Model Draft 

 . draft-hong-i2nsf-nsf-monitoring-data-model-06

 . https://tools.ietf.org/html/draft-hong-i2nsf-nsf-monitoring-data-model-06

 

The NSF monitoring is very important to manage the I2NSF security service
system

in a reliable and scalable fashion.

 

Could you start a WG adoption call for this draft?

 

Thanks.

 

Best Regards,

Paul

-- 

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


------=_NextPart_000_EA3C_01D48DA8.56866F20
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta name=3DGenerator =
content=3D"Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:\AD74\B9BC;
	panose-1:2 11 6 0 0 1 1 1 1 1;}
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:"\B9D1\C740 \ACE0\B515";
	panose-1:2 11 5 3 2 0 0 2 0 4;}
@font-face
	{font-family:"\@\AD74\B9BC";
	panose-1:2 11 6 0 0 1 1 1 1 1;}
@font-face
	{font-family:"\@\B9D1\C740 \ACE0\B515";}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman",serif;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.msonormal0, li.msonormal0, div.msonormal0
	{mso-style-name:msonormal;
	mso-margin-top-alt:auto;
	margin-right:0cm;
	mso-margin-bottom-alt:auto;
	margin-left:0cm;
	font-size:12.0pt;
	font-family:\AD74\B9BC;}
span.EmailStyle18
	{mso-style-type:personal;
	font-family:"Calibri",sans-serif;
	color:#1F497D;}
span.EmailStyle20
	{mso-style-type:personal;
	font-family:"\B9D1\C740 \ACE0\B515";}
span.EmailStyle21
	{mso-style-type:personal-compose;
	font-family:"\B9D1\C740 \ACE0\B515";}
.MsoChpDefault
	{mso-style-type:export-only;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style></head><body lang=3DKO link=3Dblue vlink=3Dpurple><div =
class=3DWordSection1><p class=3DMsoNormal =
style=3D'word-break:break-hangul'><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"&#47569;&#51008; =
&#44256;&#46357;"'>Hello&nbsp; I2NSF WG, <o:p></o:p></span></p><p =
class=3DMsoNormal style=3D'word-break:break-hangul'><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"&#47569;&#51008; =
&#44256;&#46357;"'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal =
style=3D'word-break:break-hangul'><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"&#47569;&#51008; =
&#44256;&#46357;"'>I fully support the WG adoption of this NSF =
Monitoring Data Model draft. <o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'word-break:break-hangul'><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"&#47569;&#51008; =
&#44256;&#46357;"'>This draft provides a comprehensive and concise data =
model for the security industry along with an information model for NSF =
monitoring. <o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'word-break:break-hangul'><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"&#47569;&#51008; =
&#44256;&#46357;"'>Likewise it also provides an efficient way to monitor =
the functionality and load of NSFs.<o:p></o:p></span></p><p =
class=3DMsoNormal style=3D'word-break:break-hangul'><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"&#47569;&#51008; =
&#44256;&#46357;"'>I think&nbsp; this draft will be helpful for the =
I2NSF framework.<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'word-break:break-hangul'><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"&#47569;&#51008; =
&#44256;&#46357;"'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal =
style=3D'word-break:break-hangul'><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"&#47569;&#51008; =
&#44256;&#46357;"'>Thanks<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'word-break:break-hangul'><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"&#47569;&#51008; =
&#44256;&#46357;"'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal =
style=3D'word-break:break-hangul'><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"&#47569;&#51008; =
&#44256;&#46357;"'>Hyunsik Yang<o:p></o:p></span></p><p =
class=3DMsoNormal style=3D'word-break:break-hangul'><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"&#47569;&#51008; =
&#44256;&#46357;"'><o:p>&nbsp;</o:p></span></p><div><div =
style=3D'border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm =
0cm 0cm'><p class=3DMsoNormal><b><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri",sans-serif'>From:</span><=
/b><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri",sans-serif'> I2nsf =
&lt;i2nsf-bounces@ietf.org&gt; <b>On Behalf Of </b>Linda =
Dunbar<br><b>Sent:</b> Thursday, December 6, 2018 7:32 AM<br><b>To:</b> =
i2nsf@ietf.org<br><b>Subject:</b> [I2nsf] Call for WG Adoption on NSF =
Monitoring Draft<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'=
>This is the start of a two weeks call for input on the WG adoption of =
the document: </span><span lang=3DEN-US><a =
href=3D"https://tools.ietf.org/html/draft-hong-i2nsf-nsf-monitoring-data-=
model-06">https://tools.ietf.org/html/draft-hong-i2nsf-nsf-monitoring-dat=
a-model-06</a></span><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'=
><o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'=
><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'=
>Thanks for the authors of the two I2NSF Monitoring drafts taking =
actions of merging the content. <o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'=
>We need more of those actions. As of now we have 8 WG drafts. We need =
to finish them next few months. <o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'=
><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'=
>Bear in mind that WG adoption doesn&#8217;t mean the draft is ready, =
only means that WG will work together on the draft (instead of =
individuals). <o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'=
><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'=
>Please provide feedback to the list/chairs if you believe that this =
document should be adopted as a WG document.<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'=
><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'=
>Thanks, <o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'=
><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'=
>Linda &amp; Yoav<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'=
><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'=
><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><b><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri",sans-serif'>From:</span><=
/b><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri",sans-serif'> Mr. Jaehoon =
Paul Jeong [<a =
href=3D"mailto:jaehoon.paul@gmail.com">mailto:jaehoon.paul@gmail.com</a>]=
 <br><b>Sent:</b> Thursday, November 15, 2018 6:35 PM<br><b>To:</b> =
Linda Dunbar &lt;<a =
href=3D"mailto:linda.dunbar@huawei.com">linda.dunbar@huawei.com</a>&gt;; =
Yoav Nir &lt;<a =
href=3D"mailto:ynir.ietf@gmail.com">ynir.ietf@gmail.com</a>&gt;<br><b>Cc:=
</b> <a href=3D"mailto:i2nsf@ietf.org">i2nsf@ietf.org</a>; <a =
href=3D"mailto:skku_secu-brain_all@googlegroups.com">skku_secu-brain_all@=
googlegroups.com</a>; Sangwon Hyun &lt;<a =
href=3D"mailto:swhyun77@gmail.com">swhyun77@gmail.com</a>&gt;; Mr. =
Jaehoon Paul Jeong &lt;<a =
href=3D"mailto:jaehoon.paul@gmail.com">jaehoon.paul@gmail.com</a>&gt;<br>=
<b>Subject:</b> Request for WG Adoption Call on NSF Monitoring =
Draft<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><div><div><div><p =
class=3DMsoNormal><span lang=3DEN-US>Hi Linda and =
Yoav,<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
lang=3DEN-US>As we discussed the last Bangkok =
meeting,<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
lang=3DEN-US>I have merged the two drafts of Information Model and Data =
Model<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
lang=3DEN-US>for NSF Monitoring into a new draft called =
draft-hong-i2nsf-nsf-monitoring-data-model-06:<o:p></o:p></span></p></div=
><div><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p></div><div><p =
class=3DMsoNormal><span lang=3DEN-US>- Two Information and Data Model =
Drafts<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
lang=3DEN-US>&nbsp;. =
draft-zhang-i2nsf-info-model-monitoring-07&nbsp;<o:p></o:p></span></p></d=
iv><div><p class=3DMsoNormal><span lang=3DEN-US>&nbsp;. =
draft-hong-i2nsf-nsf-monitoring-data-model-05<o:p></o:p></span></p></div>=
<div><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p></div><div><p =
class=3DMsoNormal><span lang=3DEN-US>- A Merged Data Model =
Draft&nbsp;<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
lang=3DEN-US>&nbsp;. =
draft-hong-i2nsf-nsf-monitoring-data-model-06<o:p></o:p></span></p></div>=
<div><p class=3DMsoNormal><span lang=3DEN-US>&nbsp;. <a =
href=3D"https://tools.ietf.org/html/draft-hong-i2nsf-nsf-monitoring-data-=
model-06">https://tools.ietf.org/html/draft-hong-i2nsf-nsf-monitoring-dat=
a-model-06</a><o:p></o:p></span></p></div><div><p =
class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p></div><div><p =
class=3DMsoNormal><span lang=3DEN-US>The NSF monitoring is very =
important to manage the I2NSF security service =
system<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
lang=3DEN-US>in a reliable and scalable =
fashion.<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p></div><div><p =
class=3DMsoNormal><span lang=3DEN-US>Could you start a WG adoption call =
for this draft?<o:p></o:p></span></p></div><div><p =
class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p></div><div><p =
class=3DMsoNormal><span =
lang=3DEN-US>Thanks.<o:p></o:p></span></p></div><div><p =
class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p></div><div><p =
class=3DMsoNormal><span lang=3DEN-US>Best =
Regards,<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
lang=3DEN-US>Paul<o:p></o:p></span></p></div><div><p =
class=3DMsoNormal><span =
lang=3DEN-US>--&nbsp;<o:p></o:p></span></p></div><div><div><div><div><div=
><div><div><div><p class=3DMsoNormal><span =
lang=3DEN-US>=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 Software<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>,&nbsp;<a =
href=3D"mailto:pauljeong@skku.edu" target=3D"_blank"><span =
style=3D'font-size:9.5pt'>pauljeong@skku.edu</span></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><o:p=
></o:p></span></p></div></div></div></div></div></div></div></div></div><=
/div></div></body></html>
------=_NextPart_000_EA3C_01D48DA8.56866F20--


From nobody Thu Dec  6 05:26:10 2018
Return-Path: <paul@nohats.ca>
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 5F1DD129385 for <i2nsf@ietfa.amsl.com>; Thu,  6 Dec 2018 05:26:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nohats.ca
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 8FijjLz4ICLl for <i2nsf@ietfa.amsl.com>; Thu,  6 Dec 2018 05:26:06 -0800 (PST)
Received: from mx.nohats.ca (mx.nohats.ca [IPv6:2a03:6000:1004:1::68]) (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 41352128C65 for <i2nsf@ietf.org>; Thu,  6 Dec 2018 05:26:06 -0800 (PST)
Received: from localhost (localhost [IPv6:::1]) by mx.nohats.ca (Postfix) with ESMTP id 439bvs16MyzFkH; Thu,  6 Dec 2018 14:26:01 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nohats.ca; s=default; t=1544102761; bh=omelAdlar8QSXGmj6/adEkbe/7un91cs7Pn6KRgB3Hk=; h=Date:From:To:cc:Subject:In-Reply-To:References; b=PyA7WCYy4JJ4P9nTnVfm8RHhYppJwtJ7S8Rq+epI4LrlPPP48TPdLbISh1c/3vqMJ 2NwWR3iVzzuEhoakdFNTi7N1mXGvCJ5n+N9FMK2c+e9zgD/x9zIEFSy0lULb0SJCXX GQ88lzFzdPZ2LoINROZXVbhNBDVMTPL3Drurn0AM=
X-Virus-Scanned: amavisd-new at mx.nohats.ca
Received: from mx.nohats.ca ([IPv6:::1]) by localhost (mx.nohats.ca [IPv6:::1]) (amavisd-new, port 10024) with ESMTP id ewF8VnmkIpLL; Thu,  6 Dec 2018 14:25:59 +0100 (CET)
Received: from bofh.nohats.ca (bofh.nohats.ca [76.10.157.69]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx.nohats.ca (Postfix) with ESMTPS; Thu,  6 Dec 2018 14:25:58 +0100 (CET)
Received: by bofh.nohats.ca (Postfix, from userid 1000) id D14F3345876; Thu,  6 Dec 2018 08:25:57 -0500 (EST)
DKIM-Filter: OpenDKIM Filter v2.11.0 bofh.nohats.ca D14F3345876
Received: from localhost (localhost [127.0.0.1]) by bofh.nohats.ca (Postfix) with ESMTP id C52B0418760B; Thu,  6 Dec 2018 08:25:57 -0500 (EST)
Date: Thu, 6 Dec 2018 08:25:57 -0500 (EST)
From: Paul Wouters <paul@nohats.ca>
To: Linda Dunbar <linda.dunbar@huawei.com>
cc: "i2nsf@ietf.org" <i2nsf@ietf.org>
In-Reply-To: <5D96C619-820E-44A4-A191-DB99715D63D5@telefonica.com>
Message-ID: <alpine.LRH.2.21.1812060823290.1622@bofh.nohats.ca>
References: <5D96C619-820E-44A4-A191-DB99715D63D5@telefonica.com>
User-Agent: Alpine 2.21 (LRH 202 2017-01-01)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII; format=flowed
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2nsf/hIGRD2bQAox3DOww3ENYWz6oxfA>
Subject: Re: [I2nsf] Call for WG Adoption on NSF Monitoring 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, 06 Dec 2018 13:26:08 -0000

> On 05/12/2018, 23:31, "I2nsf on behalf of Linda Dunbar" <i2nsf-bounces@ietf.org on behalf of linda.dunbar@huawei.com> wrote:
> 
> 
> This is the start of a two weeks call for input on the WG adoption of the document: https://tools.ietf.org/html/draft-hong-i2nsf-nsf-monitoring-data-model-06

I support adoption. Coming from the IPsec community, one the worst
properties is vendor lock on management of devices. I think it is very
important to get all different kinds of vendors to support a single API
and to allow different devices to communicate and configure and monitor
the security of a network comprising of different vendor equipment.

Paul


From nobody Thu Dec  6 05:31:40 2018
Return-Path: <swhyun77@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 CC378130DD5 for <i2nsf@ietfa.amsl.com>; Thu,  6 Dec 2018 05:31:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.748
X-Spam-Level: 
X-Spam-Status: No, score=-0.748 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, FREEMAIL_REPLY=1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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 lyuwygHrnDBm for <i2nsf@ietfa.amsl.com>; Thu,  6 Dec 2018 05:31:34 -0800 (PST)
Received: from mail-qt1-x82f.google.com (mail-qt1-x82f.google.com [IPv6:2607:f8b0:4864:20::82f]) (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 261DF13115A for <i2nsf@ietf.org>; Thu,  6 Dec 2018 05:31:30 -0800 (PST)
Received: by mail-qt1-x82f.google.com with SMTP id t13so498443qtn.3 for <i2nsf@ietf.org>; Thu, 06 Dec 2018 05:31:30 -0800 (PST)
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;  bh=I87pSsalN2dKHrNTD+vql7qtbQLoHHX0oOWZ0c2mCQ4=; b=VcdiFXCzS7TZt2tTh6Mqa/gJ30jJuTGRQCgu9gbEzLaWkMyRAtVp70TmM6xEPXB0cW LjUwaWKDt5R0Ja1suaZMnBMcSvwRUyTgswCx+H4+d949ZEEXSmGLaTG/toD7kOcSnvLy 4kdfqwPS4kdud6s+MPcblCgqFL843KfYk6GfQas2aA+spBIUN7HWe8cnzbDvPt+V7lqi ZiSRQ66V8MbpRQWL6x5E7DO4gYjZB1M4MaIUjmvZPWYSmFR3Ccxi8TT+M65A/vyy8lhj tqYKZf+V8k73YOvUr4aDJHhS2xNFM65SDLF9TBxwzgjt2mO+3X5kztxGxMP0NfRXTIvH ASZQ==
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; bh=I87pSsalN2dKHrNTD+vql7qtbQLoHHX0oOWZ0c2mCQ4=; b=tXMJ+UNdFoKoZM3ZzLZKosyFpWLMXSe8qHTwfMw2XAL+LIuh61YE8Grane5kXfwhoV CbwhIdJQVT080MICFe0UAJBhhvtPEW6kWvk7foN+X+NCyeCq/UYRsp1SayV+vjBUurye jnfPSLiqrMZgsoksXXM5MaA1I3pKel3sp0Wkw4yeSakhUdsQApJHGYxCpaVjzV8v+hkO jJdiUjwmfeWv/d0gBTlW/K7IK0rIRx446YzkjimGdBrge0mV6JOizx3aLGvdLYqo8U1m ikZnWU9YpjZ8mn2wCtLQ91igKG+uP38k0OaCfNwmOfB+nzzwOUMGIp/wwsNo8qXqo8Bx XQYg==
X-Gm-Message-State: AA+aEWbEclNZzgQP8eI9uUPe8UHyhfC7HC/UmcE+2Cg3si2DF+MfjQrv 3CD0v9REG4LWIuOjg57mU0kA5UI6ZYu7o/I+vMQ=
X-Google-Smtp-Source: AFSGD/XhCGN+EwtERceGbLsJhBaY4I5/zi2sT+5Mno86a+HPAyRG3GZ1tXpA5CpIgjgVK/DfZ8qHv9qe1zvkhZ0M61M=
X-Received: by 2002:ac8:3312:: with SMTP id t18mr27406543qta.225.1544103089152;  Thu, 06 Dec 2018 05:31:29 -0800 (PST)
MIME-Version: 1.0
References: <4A95BA014132FF49AE685FAB4B9F17F66B1F6399@SJCEML521-MBB.china.huawei.com> <ea3b01d48d5c$e69cf260$b3d6d720$@dcn.ssu.ac.kr>
In-Reply-To: <ea3b01d48d5c$e69cf260$b3d6d720$@dcn.ssu.ac.kr>
From: Sangwon Hyun <swhyun77@gmail.com>
Date: Thu, 6 Dec 2018 22:31:17 +0900
Message-ID: <CAOFzWun89zQH8v+VDWEnUG600c_tux5oKyi+pRSe_gzFamj08g@mail.gmail.com>
To: Linda Dunbar <linda.dunbar@huawei.com>, i2nsf@ietf.org
Content-Type: multipart/alternative; boundary="00000000000020270b057c5a8487"
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2nsf/GL3ORSa9roYrCuiuXzKwQ4Et1CU>
Subject: Re: [I2nsf] Call for WG Adoption on NSF Monitoring 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, 06 Dec 2018 13:31:39 -0000

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

Hi I2NSF WG,


I strongly support the adoption of this NSF Monitoring Data Model draft.


This NSF Monitoring Data Model allows monitoring the functionality and work=
load
of NSFs, and this feature is essential for efficient maintenance of the
I2NSF framework. In addition, it is also possible to detect malicious
activities by monitoring NSFs with this data model.

This draft will provide the security industry with a concise and
comprehensive data model along with an information model for NSF monitoring=
.


Best regards,


Sangwon.



2018=EB=85=84 12=EC=9B=94 6=EC=9D=BC (=EB=AA=A9) =EC=98=A4=ED=9B=84 9:12, <=
yangun@dcn.ssu.ac.kr>=EB=8B=98=EC=9D=B4 =EC=9E=91=EC=84=B1:

> Hello  I2NSF WG,
>
>
>
> I fully support the WG adoption of this NSF Monitoring Data Model draft.
>
> This draft provides a comprehensive and concise data model for the
> security industry along with an information model for NSF monitoring.
>
> Likewise it also provides an efficient way to monitor the functionality
> and load of NSFs.
>
> I think  this draft will be helpful for the I2NSF framework.
>
>
>
> Thanks
>
>
>
> Hyunsik Yang
>
>
>
> *From:* I2nsf <i2nsf-bounces@ietf.org> *On Behalf Of *Linda Dunbar
> *Sent:* Thursday, December 6, 2018 7:32 AM
> *To:* i2nsf@ietf.org
> *Subject:* [I2nsf] Call for WG Adoption on NSF Monitoring Draft
>
>
>
> This is the start of a two weeks call for input on the WG adoption of the
> document:
> https://tools.ietf.org/html/draft-hong-i2nsf-nsf-monitoring-data-model-06
>
>
>
> Thanks for the authors of the two I2NSF Monitoring drafts taking actions
> of merging the content.
>
> We need more of those actions. As of now we have 8 WG drafts. We need to
> finish them next few months.
>
>
>
> Bear in mind that WG adoption doesn=E2=80=99t mean the draft is ready, on=
ly means
> that WG will work together on the draft (instead of individuals).
>
>
>
> Please provide feedback to the list/chairs if you believe that this
> document should be adopted as a WG document.
>
>
>
> Thanks,
>
>
>
> Linda & Yoav
>
>
>
>
>
> *From:* Mr. Jaehoon Paul Jeong [mailto:jaehoon.paul@gmail.com
> <jaehoon.paul@gmail.com>]
> *Sent:* Thursday, November 15, 2018 6:35 PM
> *To:* Linda Dunbar <linda.dunbar@huawei.com>; Yoav Nir <
> ynir.ietf@gmail.com>
> *Cc:* i2nsf@ietf.org; skku_secu-brain_all@googlegroups.com; Sangwon Hyun =
<
> swhyun77@gmail.com>; Mr. Jaehoon Paul Jeong <jaehoon.paul@gmail.com>
> *Subject:* Request for WG Adoption Call on NSF Monitoring Draft
>
>
>
> Hi Linda and Yoav,
>
> As we discussed the last Bangkok meeting,
>
> I have merged the two drafts of Information Model and Data Model
>
> for NSF Monitoring into a new draft called
> draft-hong-i2nsf-nsf-monitoring-data-model-06:
>
>
>
> - Two Information and Data Model Drafts
>
>  . draft-zhang-i2nsf-info-model-monitoring-07
>
>  . draft-hong-i2nsf-nsf-monitoring-data-model-05
>
>
>
> - A Merged Data Model Draft
>
>  . draft-hong-i2nsf-nsf-monitoring-data-model-06
>
>  .
> https://tools.ietf.org/html/draft-hong-i2nsf-nsf-monitoring-data-model-06
>
>
>
> The NSF monitoring is very important to manage the I2NSF security service
> system
>
> in a reliable and scalable fashion.
>
>
>
> Could you start a WG adoption call for this draft?
>
>
>
> Thanks.
>
>
>
> Best Regards,
>
> Paul
>
> --
>
> =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 Software
> 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>
> _______________________________________________
> I2nsf mailing list
> I2nsf@ietf.org
> https://www.ietf.org/mailman/listinfo/i2nsf
>

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

<div dir=3D"ltr"><p style=3D"margin:0in;font-family:Calibri;font-size:11pt"=
 lang=3D"en-US">Hi I2NSF
WG,</p><p style=3D"margin:0in;font-family:Calibri;font-size:11pt" lang=3D"e=
n-US"><br></p>

<p style=3D"margin:0in;font-family:Calibri;font-size:11pt" lang=3D"en-US">I
strongly support the adoption of this NSF Monitoring Data Model draft.</p><=
p style=3D"margin:0in;font-family:Calibri;font-size:11pt" lang=3D"en-US"><b=
r></p><p style=3D"margin:0in;font-size:11pt"><span style=3D"font-family:Cal=
ibri" lang=3D"en-US">This NSF Monitoring Data Model allows monitoring </spa=
n><span style=3D"font-family:&quot;Malgun Gothic&quot;" lang=3D"ko">the fun=
ctionality and </span><span style=3D"font-family:&quot;Malgun Gothic&quot;"=
 lang=3D"en-US">work</span><span style=3D"font-family:&quot;Malgun Gothic&q=
uot;" lang=3D"ko">load of NSFs</span><span style=3D"font-family:&quot;Malgu=
n Gothic&quot;" lang=3D"en-US">, and this feature is essential
for efficient maintenance of the I2NSF framework.=C2=A0</span><span style=
=3D"font-family:&quot;Malgun Gothic&quot;;font-size:11pt">In
addition, it is also possible to detect malicious activities by monitoring =
NSFs
with this data model.</span></p><p style=3D"margin:0in;font-family:Calibri;=
font-size:11pt" lang=3D"en-US">



</p><p style=3D"margin:0in;font-family:&quot;Malgun Gothic&quot;;font-size:=
11pt"><span lang=3D"en-US">This draft will provide the security industry </=
span><span lang=3D"ko">with
a concise and comprehensive data model along with an information model for =
NSF
monitoring.</span></p><p style=3D"margin:0in;font-family:&quot;Malgun Gothi=
c&quot;;font-size:11pt"><span lang=3D"ko"><br></span></p><p style=3D"margin=
:0in;font-family:&quot;Malgun Gothic&quot;;font-size:11pt"><span lang=3D"ko=
">Best regards,</span></p><p style=3D"margin:0in;font-family:&quot;Malgun G=
othic&quot;;font-size:11pt"><span lang=3D"ko"><br></span></p><p style=3D"ma=
rgin:0in;font-family:&quot;Malgun Gothic&quot;;font-size:11pt"><span lang=
=3D"ko">Sangwon.</span></p><p style=3D"margin:0in;font-family:&quot;Malgun =
Gothic&quot;;font-size:11pt"><span lang=3D"ko"><br></span></p></div><br><di=
v class=3D"gmail_quote"><div dir=3D"ltr">2018=EB=85=84 12=EC=9B=94 6=EC=9D=
=BC (=EB=AA=A9) =EC=98=A4=ED=9B=84 9:12, &lt;<a href=3D"mailto:yangun@dcn.s=
su.ac.kr">yangun@dcn.ssu.ac.kr</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;bor=
der-left:1px #ccc solid;padding-left:1ex"><div lang=3D"KO" link=3D"blue" vl=
ink=3D"purple"><div class=3D"m_-7265096196055266908WordSection1"><p class=
=3D"MsoNormal" style=3D"word-break:break-hangul"><span lang=3D"EN-US" style=
=3D"font-size:10.0pt;font-family:&quot;\00b9d1\00c740  \00ace0\00b515&quot;=
">Hello=C2=A0 I2NSF WG, <u></u><u></u></span></p><p class=3D"MsoNormal" sty=
le=3D"word-break:break-hangul"><span lang=3D"EN-US" style=3D"font-size:10.0=
pt;font-family:&quot;\00b9d1\00c740  \00ace0\00b515&quot;"><u></u>=C2=A0<u>=
</u></span></p><p class=3D"MsoNormal" style=3D"word-break:break-hangul"><sp=
an lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;\00b9d1\00c74=
0  \00ace0\00b515&quot;">I fully support the WG adoption of this NSF Monito=
ring Data Model draft. <u></u><u></u></span></p><p class=3D"MsoNormal" styl=
e=3D"word-break:break-hangul"><span lang=3D"EN-US" style=3D"font-size:10.0p=
t;font-family:&quot;\00b9d1\00c740  \00ace0\00b515&quot;">This draft provid=
es a comprehensive and concise data model for the security industry along w=
ith an information model for NSF monitoring. <u></u><u></u></span></p><p cl=
ass=3D"MsoNormal" style=3D"word-break:break-hangul"><span lang=3D"EN-US" st=
yle=3D"font-size:10.0pt;font-family:&quot;\00b9d1\00c740  \00ace0\00b515&qu=
ot;">Likewise it also provides an efficient way to monitor the functionalit=
y and load of NSFs.<u></u><u></u></span></p><p class=3D"MsoNormal" style=3D=
"word-break:break-hangul"><span lang=3D"EN-US" style=3D"font-size:10.0pt;fo=
nt-family:&quot;\00b9d1\00c740  \00ace0\00b515&quot;">I think=C2=A0 this dr=
aft will be helpful for the I2NSF framework.<u></u><u></u></span></p><p cla=
ss=3D"MsoNormal" style=3D"word-break:break-hangul"><span lang=3D"EN-US" sty=
le=3D"font-size:10.0pt;font-family:&quot;\00b9d1\00c740  \00ace0\00b515&quo=
t;"><u></u>=C2=A0<u></u></span></p><p class=3D"MsoNormal" style=3D"word-bre=
ak:break-hangul"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family=
:&quot;\00b9d1\00c740  \00ace0\00b515&quot;">Thanks<u></u><u></u></span></p=
><p class=3D"MsoNormal" style=3D"word-break:break-hangul"><span lang=3D"EN-=
US" style=3D"font-size:10.0pt;font-family:&quot;\00b9d1\00c740  \00ace0\00b=
515&quot;"><u></u>=C2=A0<u></u></span></p><p class=3D"MsoNormal" style=3D"w=
ord-break:break-hangul"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font=
-family:&quot;\00b9d1\00c740  \00ace0\00b515&quot;">Hyunsik Yang<u></u><u><=
/u></span></p><p class=3D"MsoNormal" style=3D"word-break:break-hangul"><spa=
n lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;\00b9d1\00c740=
  \00ace0\00b515&quot;"><u></u>=C2=A0<u></u></span></p><div><div style=3D"b=
order:none;border-top:solid #e1e1e1 1.0pt;padding:3.0pt 0cm 0cm 0cm"><p cla=
ss=3D"MsoNormal"><b><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-fam=
ily:&quot;Calibri&quot;,sans-serif">From:</span></b><span lang=3D"EN-US" st=
yle=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-serif"> I2nsf =
&lt;<a href=3D"mailto:i2nsf-bounces@ietf.org" target=3D"_blank">i2nsf-bounc=
es@ietf.org</a>&gt; <b>On Behalf Of </b>Linda Dunbar<br><b>Sent:</b> Thursd=
ay, December 6, 2018 7:32 AM<br><b>To:</b> <a href=3D"mailto:i2nsf@ietf.org=
" target=3D"_blank">i2nsf@ietf.org</a><br><b>Subject:</b> [I2nsf] Call for =
WG Adoption on NSF Monitoring Draft<u></u><u></u></span></p></div></div><p =
class=3D"MsoNormal"><span lang=3D"EN-US"><u></u>=C2=A0<u></u></span></p><p =
class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-fam=
ily:&quot;Calibri&quot;,sans-serif;color:#1f497d">This is the start of a tw=
o weeks call for input on the WG adoption of the document: </span><span lan=
g=3D"EN-US"><a href=3D"https://tools.ietf.org/html/draft-hong-i2nsf-nsf-mon=
itoring-data-model-06" target=3D"_blank">https://tools.ietf.org/html/draft-=
hong-i2nsf-nsf-monitoring-data-model-06</a></span><span lang=3D"EN-US" styl=
e=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-serif;color:#1f4=
97d"><u></u><u></u></span></p><p class=3D"MsoNormal"><span lang=3D"EN-US" s=
tyle=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-serif;color:#=
1f497d"><u></u>=C2=A0<u></u></span></p><p class=3D"MsoNormal"><span lang=3D=
"EN-US" style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-seri=
f;color:#1f497d">Thanks for the authors of the two I2NSF Monitoring drafts =
taking actions of merging the content. <u></u><u></u></span></p><p class=3D=
"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-family:&quo=
t;Calibri&quot;,sans-serif;color:#1f497d">We need more of those actions. As=
 of now we have 8 WG drafts. We need to finish them next few months. <u></u=
><u></u></span></p><p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"fon=
t-size:11.0pt;font-family:&quot;Calibri&quot;,sans-serif;color:#1f497d"><u>=
</u>=C2=A0<u></u></span></p><p class=3D"MsoNormal"><span lang=3D"EN-US" sty=
le=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-serif;color:#1f=
497d">Bear in mind that WG adoption doesn=E2=80=99t mean the draft is ready=
, only means that WG will work together on the draft (instead of individual=
s). <u></u><u></u></span></p><p class=3D"MsoNormal"><span lang=3D"EN-US" st=
yle=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-serif;color:#1=
f497d"><u></u>=C2=A0<u></u></span></p><p class=3D"MsoNormal"><span lang=3D"=
EN-US" style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-serif=
;color:#1f497d">Please provide feedback to the list/chairs if you believe t=
hat this document should be adopted as a WG document.<u></u><u></u></span><=
/p><p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;fo=
nt-family:&quot;Calibri&quot;,sans-serif;color:#1f497d"><u></u>=C2=A0<u></u=
></span></p><p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:=
11.0pt;font-family:&quot;Calibri&quot;,sans-serif;color:#1f497d">Thanks, <u=
></u><u></u></span></p><p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D=
"font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-serif;color:#1f497d"=
><u></u>=C2=A0<u></u></span></p><p class=3D"MsoNormal"><span lang=3D"EN-US"=
 style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-serif;color=
:#1f497d">Linda &amp; Yoav<u></u><u></u></span></p><p class=3D"MsoNormal"><=
span lang=3D"EN-US" style=3D"font-size:11.0pt;font-family:&quot;Calibri&quo=
t;,sans-serif;color:#1f497d"><u></u>=C2=A0<u></u></span></p><p class=3D"Mso=
Normal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#1f497d"><u></u>=C2=A0<u></u></span></p><p cla=
ss=3D"MsoNormal"><b><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-fam=
ily:&quot;Calibri&quot;,sans-serif">From:</span></b><span lang=3D"EN-US" st=
yle=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-serif"> Mr. Ja=
ehoon Paul Jeong [<a href=3D"mailto:jaehoon.paul@gmail.com" target=3D"_blan=
k">mailto:jaehoon.paul@gmail.com</a>] <br><b>Sent:</b> Thursday, November 1=
5, 2018 6:35 PM<br><b>To:</b> Linda Dunbar &lt;<a href=3D"mailto:linda.dunb=
ar@huawei.com" target=3D"_blank">linda.dunbar@huawei.com</a>&gt;; Yoav Nir =
&lt;<a href=3D"mailto:ynir.ietf@gmail.com" target=3D"_blank">ynir.ietf@gmai=
l.com</a>&gt;<br><b>Cc:</b> <a href=3D"mailto:i2nsf@ietf.org" target=3D"_bl=
ank">i2nsf@ietf.org</a>; <a href=3D"mailto:skku_secu-brain_all@googlegroups=
.com" target=3D"_blank">skku_secu-brain_all@googlegroups.com</a>; Sangwon H=
yun &lt;<a href=3D"mailto:swhyun77@gmail.com" target=3D"_blank">swhyun77@gm=
ail.com</a>&gt;; Mr. Jaehoon Paul Jeong &lt;<a href=3D"mailto:jaehoon.paul@=
gmail.com" target=3D"_blank">jaehoon.paul@gmail.com</a>&gt;<br><b>Subject:<=
/b> Request for WG Adoption Call on NSF Monitoring Draft<u></u><u></u></spa=
n></p><p class=3D"MsoNormal"><span lang=3D"EN-US"><u></u>=C2=A0<u></u></spa=
n></p><div><div><div><p class=3D"MsoNormal"><span lang=3D"EN-US">Hi Linda a=
nd Yoav,<u></u><u></u></span></p></div><div><p class=3D"MsoNormal"><span la=
ng=3D"EN-US">As we discussed the last Bangkok meeting,<u></u><u></u></span>=
</p></div><div><p class=3D"MsoNormal"><span lang=3D"EN-US">I have merged th=
e two drafts of Information Model and Data Model<u></u><u></u></span></p></=
div><div><p class=3D"MsoNormal"><span lang=3D"EN-US">for NSF Monitoring int=
o a new draft called draft-hong-i2nsf-nsf-monitoring-data-model-06:<u></u><=
u></u></span></p></div><div><p class=3D"MsoNormal"><span lang=3D"EN-US"><u>=
</u>=C2=A0<u></u></span></p></div><div><p class=3D"MsoNormal"><span lang=3D=
"EN-US">- Two Information and Data Model Drafts<u></u><u></u></span></p></d=
iv><div><p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0. draft-zhang-i2n=
sf-info-model-monitoring-07=C2=A0<u></u><u></u></span></p></div><div><p cla=
ss=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0. draft-hong-i2nsf-nsf-monitori=
ng-data-model-05<u></u><u></u></span></p></div><div><p class=3D"MsoNormal">=
<span lang=3D"EN-US"><u></u>=C2=A0<u></u></span></p></div><div><p class=3D"=
MsoNormal"><span lang=3D"EN-US">- A Merged Data Model Draft=C2=A0<u></u><u>=
</u></span></p></div><div><p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=
=A0. draft-hong-i2nsf-nsf-monitoring-data-model-06<u></u><u></u></span></p>=
</div><div><p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0. <a href=3D"h=
ttps://tools.ietf.org/html/draft-hong-i2nsf-nsf-monitoring-data-model-06" t=
arget=3D"_blank">https://tools.ietf.org/html/draft-hong-i2nsf-nsf-monitorin=
g-data-model-06</a><u></u><u></u></span></p></div><div><p class=3D"MsoNorma=
l"><span lang=3D"EN-US"><u></u>=C2=A0<u></u></span></p></div><div><p class=
=3D"MsoNormal"><span lang=3D"EN-US">The NSF monitoring is very important to=
 manage the I2NSF security service system<u></u><u></u></span></p></div><di=
v><p class=3D"MsoNormal"><span lang=3D"EN-US">in a reliable and scalable fa=
shion.<u></u><u></u></span></p></div><div><p class=3D"MsoNormal"><span lang=
=3D"EN-US"><u></u>=C2=A0<u></u></span></p></div><div><p class=3D"MsoNormal"=
><span lang=3D"EN-US">Could you start a WG adoption call for this draft?<u>=
</u><u></u></span></p></div><div><p class=3D"MsoNormal"><span lang=3D"EN-US=
"><u></u>=C2=A0<u></u></span></p></div><div><p class=3D"MsoNormal"><span la=
ng=3D"EN-US">Thanks.<u></u><u></u></span></p></div><div><p class=3D"MsoNorm=
al"><span lang=3D"EN-US"><u></u>=C2=A0<u></u></span></p></div><div><p class=
=3D"MsoNormal"><span lang=3D"EN-US">Best Regards,<u></u><u></u></span></p><=
/div><div><p class=3D"MsoNormal"><span lang=3D"EN-US">Paul<u></u><u></u></s=
pan></p></div><div><p class=3D"MsoNormal"><span lang=3D"EN-US">--=C2=A0<u><=
/u><u></u></span></p></div><div><div><div><div><div><div><div><div><p class=
=3D"MsoNormal"><span lang=3D"EN-US">=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 Software<br>Sungkyunkwan Univers=
ity<br>Office: +82-31-299-4957<br>Email: <a href=3D"mailto:jaehoon.paul@gma=
il.com" target=3D"_blank">jaehoon.paul@gmail.com</a>,=C2=A0<a href=3D"mailt=
o:pauljeong@skku.edu" target=3D"_blank"><span style=3D"font-size:9.5pt">pau=
ljeong@skku.edu</span></a><br>Personal Homepage: <a href=3D"http://cpslab.s=
kku.edu/people-jaehoon-jeong.php" target=3D"_blank">http://iotlab.skku.edu/=
people-jaehoon-jeong.php</a><u></u><u></u></span></p></div></div></div></di=
v></div></div></div></div></div></div></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>

--00000000000020270b057c5a8487--


From nobody Thu Dec  6 05:57:41 2018
Return-Path: <shares@ndzh.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 6ACEA1252B7 for <i2nsf@ietfa.amsl.com>; Thu,  6 Dec 2018 05:57:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.947
X-Spam-Level: 
X-Spam-Status: No, score=0.947 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DOS_OUTLOOK_TO_MX=2.845, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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 XaV08zf8paZo for <i2nsf@ietfa.amsl.com>; Thu,  6 Dec 2018 05:57:36 -0800 (PST)
Received: from hickoryhill-consulting.com (50-245-122-97-static.hfc.comcastbusiness.net [50.245.122.97]) (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 5E653124D68 for <i2nsf@ietf.org>; Thu,  6 Dec 2018 05:57:36 -0800 (PST)
X-Default-Received-SPF: pass (skip=loggedin (res=PASS)) x-ip-name=166.177.57.147; 
From: "Susan Hares" <shares@ndzh.com>
To: "'Linda Dunbar'" <linda.dunbar@huawei.com>, <i2nsf@ietf.org>
References: <4A95BA014132FF49AE685FAB4B9F17F66B1F6399@SJCEML521-MBB.china.huawei.com>
In-Reply-To: <4A95BA014132FF49AE685FAB4B9F17F66B1F6399@SJCEML521-MBB.china.huawei.com>
Date: Thu, 6 Dec 2018 08:57:20 -0500
Message-ID: <00e401d48d6b$9bc3e230$d34ba690$@ndzh.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_00E5_01D48D41.B2F21FF0"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQM2ITJY/SI2/32U7WIJXz92vB5d1aKulJ8A
Content-Language: en-us
X-Antivirus: AVG (VPS 181206-0, 12/06/2018), Outbound message
X-Antivirus-Status: Not-Tested
X-Authenticated-User: skh@ndzh.com 
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2nsf/2Su4bGowQ9dI_Qln-DTuj6JnYoA>
Subject: Re: [I2nsf] Call for WG Adoption on NSF Monitoring 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, 06 Dec 2018 13:57:41 -0000

This is a multipart message in MIME format.

------=_NextPart_000_00E5_01D48D41.B2F21FF0
Content-Type: text/plain;
	charset="utf-8"
Content-Transfer-Encoding: quoted-printable

I support adoption of this draft (as co-author).  I do not know of any =
IPR related to this draft.=20

=20

Susan Hares=20

=20

From: I2nsf [mailto:i2nsf-bounces@ietf.org] On Behalf Of Linda Dunbar
Sent: Wednesday, December 5, 2018 5:32 PM
To: i2nsf@ietf.org
Subject: [I2nsf] Call for WG Adoption on NSF Monitoring Draft

=20

This is the start of a two weeks call for input on the WG adoption of =
the document: =
https://tools.ietf.org/html/draft-hong-i2nsf-nsf-monitoring-data-model-06=


=20

Thanks for the authors of the two I2NSF Monitoring drafts taking actions =
of merging the content.=20

We need more of those actions. As of now we have 8 WG drafts. We need to =
finish them next few months.=20

=20

Bear in mind that WG adoption doesn=E2=80=99t mean the draft is ready, =
only means that WG will work together on the draft (instead of =
individuals).=20

=20

Please provide feedback to the list/chairs if you believe that this =
document should be adopted as a WG document.

=20

Thanks,=20

=20

Linda & Yoav

=20

=20

From: Mr. Jaehoon Paul Jeong [mailto:jaehoon.paul@gmail.com]=20
Sent: Thursday, November 15, 2018 6:35 PM
To: Linda Dunbar <linda.dunbar@huawei.com>; Yoav Nir =
<ynir.ietf@gmail.com>
Cc: i2nsf@ietf.org; skku_secu-brain_all@googlegroups.com; Sangwon Hyun =
<swhyun77@gmail.com>; Mr. Jaehoon Paul Jeong <jaehoon.paul@gmail.com>
Subject: Request for WG Adoption Call on NSF Monitoring Draft

=20

Hi Linda and Yoav,

As we discussed the last Bangkok meeting,

I have merged the two drafts of Information Model and Data Model

for NSF Monitoring into a new draft called =
draft-hong-i2nsf-nsf-monitoring-data-model-06:

=20

- Two Information and Data Model Drafts

 . draft-zhang-i2nsf-info-model-monitoring-07=20

 . draft-hong-i2nsf-nsf-monitoring-data-model-05

=20

- A Merged Data Model Draft=20

 . draft-hong-i2nsf-nsf-monitoring-data-model-06

 . =
https://tools.ietf.org/html/draft-hong-i2nsf-nsf-monitoring-data-model-06=


=20

The NSF monitoring is very important to manage the I2NSF security =
service system

in a reliable and scalable fashion.

=20

Could you start a WG adoption call for this draft?

=20

Thanks.

=20

Best Regards,

Paul

--=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 Software
Sungkyunkwan University
Office: +82-31-299-4957
Email: jaehoon.paul@gmail.com,  <mailto:pauljeong@skku.edu> =
pauljeong@skku.edu
Personal Homepage: http://iotlab.skku.edu/people-jaehoon-jeong.php =
<http://cpslab.skku.edu/people-jaehoon-jeong.php>=20


------=_NextPart_000_00E5_01D48D41.B2F21FF0
Content-Type: text/html;
	charset="utf-8"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; charset=3Dutf-8"><meta =
name=3DGenerator content=3D"Microsoft Word 14 (filtered =
medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>I support adoption of this draft (as co-author).=C2=A0 I do not know =
of any IPR related to this draft. <o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Susan Hares <o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><div><div =
style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in'><p class=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> =
I2nsf [mailto:i2nsf-bounces@ietf.org] <b>On Behalf Of </b>Linda =
Dunbar<br><b>Sent:</b> Wednesday, December 5, 2018 5:32 PM<br><b>To:</b> =
i2nsf@ietf.org<br><b>Subject:</b> [I2nsf] Call for WG Adoption on NSF =
Monitoring Draft<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>This is the start of a two weeks call for input on the WG adoption of =
the document: </span><a =
href=3D"https://tools.ietf.org/html/draft-hong-i2nsf-nsf-monitoring-data-=
model-06">https://tools.ietf.org/html/draft-hong-i2nsf-nsf-monitoring-dat=
a-model-06</a><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Thanks for the authors of the two I2NSF Monitoring drafts taking =
actions of merging the content. <o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>We need more of those actions. As of now we have 8 WG drafts. We need =
to finish them next few months. <o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Bear in mind that WG adoption doesn=E2=80=99t mean the draft is =
ready, only means that WG will work together on the draft (instead of =
individuals). <o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Please provide feedback to the list/chairs if you believe that this =
document should be adopted as a WG document.<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Thanks, <o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Linda &amp; Yoav<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><a =
name=3D"_MailEndCompose"></a><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><b><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>From:</span=
></b><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'> Mr. =
Jaehoon Paul Jeong [mailto:jaehoon.paul@gmail.com] <br><b>Sent:</b> =
Thursday, November 15, 2018 6:35 PM<br><b>To:</b> Linda Dunbar =
&lt;linda.dunbar@huawei.com&gt;; Yoav Nir =
&lt;ynir.ietf@gmail.com&gt;<br><b>Cc:</b> i2nsf@ietf.org; =
skku_secu-brain_all@googlegroups.com; Sangwon Hyun =
&lt;swhyun77@gmail.com&gt;; Mr. Jaehoon Paul Jeong =
&lt;jaehoon.paul@gmail.com&gt;<br><b>Subject:</b> Request for WG =
Adoption Call on NSF Monitoring Draft<o:p></o:p></span></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><div><div><div><p =
class=3DMsoNormal>Hi Linda and Yoav,<o:p></o:p></p></div><div><p =
class=3DMsoNormal>As we discussed the last Bangkok =
meeting,<o:p></o:p></p></div><div><p class=3DMsoNormal>I have merged the =
two drafts of Information Model and Data =
Model<o:p></o:p></p></div><div><p class=3DMsoNormal>for NSF Monitoring =
into a new draft called =
draft-hong-i2nsf-nsf-monitoring-data-model-06:<o:p></o:p></p></div><div><=
p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>- Two Information and Data Model =
Drafts<o:p></o:p></p></div><div><p class=3DMsoNormal>&nbsp;. =
draft-zhang-i2nsf-info-model-monitoring-07&nbsp;<o:p></o:p></p></div><div=
><p class=3DMsoNormal>&nbsp;. =
draft-hong-i2nsf-nsf-monitoring-data-model-05<o:p></o:p></p></div><div><p=
 class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>- A Merged Data Model =
Draft&nbsp;<o:p></o:p></p></div><div><p class=3DMsoNormal>&nbsp;. =
draft-hong-i2nsf-nsf-monitoring-data-model-06<o:p></o:p></p></div><div><p=
 class=3DMsoNormal>&nbsp;. <a =
href=3D"https://tools.ietf.org/html/draft-hong-i2nsf-nsf-monitoring-data-=
model-06">https://tools.ietf.org/html/draft-hong-i2nsf-nsf-monitoring-dat=
a-model-06</a><o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>The NSF monitoring is very important to manage the =
I2NSF security service system<o:p></o:p></p></div><div><p =
class=3DMsoNormal>in a reliable and scalable =
fashion.<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>Could you start a WG adoption call for this =
draft?<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>Thanks.<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>Best Regards,<o:p></o:p></p></div><div><p =
class=3DMsoNormal>Paul<o:p></o:p></p></div><div><p =
class=3DMsoNormal>--&nbsp;<o:p></o:p></p></div><div><div><div><div><div><=
div><div><div><p =
class=3DMsoNormal>=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 Software<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>,&nbsp;<a =
href=3D"mailto:pauljeong@skku.edu" target=3D"_blank"><span =
style=3D'font-size:9.5pt'>pauljeong@skku.edu</span></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><o:p=
></o:p></p></div></div></div></div></div></div></div></div></div></div></=
div></body></html>
------=_NextPart_000_00E5_01D48D41.B2F21FF0--


From nobody Thu Dec  6 07:38:49 2018
Return-Path: <linda.dunbar@huawei.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 ECDFC12F1A2 for <i2nsf@ietfa.amsl.com>; Thu,  6 Dec 2018 07:38:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-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 howDZBifpeJZ for <i2nsf@ietfa.amsl.com>; Thu,  6 Dec 2018 07:38:42 -0800 (PST)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (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 8122F12F18C for <i2nsf@ietf.org>; Thu,  6 Dec 2018 07:38:41 -0800 (PST)
Received: from lhreml707-cah.china.huawei.com (unknown [172.18.7.108]) by Forcepoint Email with ESMTP id 9A7415F59737A for <i2nsf@ietf.org>; Thu,  6 Dec 2018 15:38:35 +0000 (GMT)
Received: from SJCEML701-CHM.china.huawei.com (10.208.112.40) by lhreml707-cah.china.huawei.com (10.201.108.48) with Microsoft SMTP Server (TLS) id 14.3.408.0; Thu, 6 Dec 2018 15:38:36 +0000
Received: from SJCEML521-MBB.china.huawei.com ([169.254.6.33]) by SJCEML701-CHM.china.huawei.com ([169.254.3.198]) with mapi id 14.03.0415.000;  Thu, 6 Dec 2018 07:38:35 -0800
From: Linda Dunbar <linda.dunbar@huawei.com>
To: Rafa Marin Lopez <rafa@um.es>
CC: Yoav Nir <ynir.ietf@gmail.com>, "i2nsf@ietf.org" <i2nsf@ietf.org>, "Paul Wouters" <paul@nohats.ca>
Thread-Topic: [I2nsf] YANG module update when new algorithms added to IPsec, RE:  Reviewing sdn-ipsec-flow-protection
Thread-Index: AQHUjUd8RTSeyIfDg0q9NNgvvBIq0qVx2M3A
Date: Thu, 6 Dec 2018 15:38:35 +0000
Message-ID: <4A95BA014132FF49AE685FAB4B9F17F66B1F6A75@SJCEML521-MBB.china.huawei.com>
References: <4A95BA014132FF49AE685FAB4B9F17F66B1F61FE@SJCEML521-MBB.china.huawei.com> <B964B976-957F-4824-9A18-576C683159FC@um.es>
In-Reply-To: <B964B976-957F-4824-9A18-576C683159FC@um.es>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.218.180.231]
Content-Type: multipart/alternative; boundary="_000_4A95BA014132FF49AE685FAB4B9F17F66B1F6A75SJCEML521MBBchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2nsf/5p5QkWh8M3wRBa5sP1QcjxFfvis>
Subject: Re: [I2nsf] YANG module update when new algorithms added to IPsec, RE:  Reviewing sdn-ipsec-flow-protection
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, 06 Dec 2018 15:38:47 -0000

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

UmFmYSwNCg0KVGhhbmtzIGZvciBnZXR0aW5nIGEgYmV0dGVyIHJlZmVyZW5jZS4gSSBsaWtlIHlv
dXIgYXBwcm9hY2guDQoNCkxpbmRhDQoNCkZyb206IFJhZmEgTWFyaW4gTG9wZXogW21haWx0bzpy
YWZhQHVtLmVzXQ0KU2VudDogVGh1cnNkYXksIERlY2VtYmVyIDA2LCAyMDE4IDM6MzkgQU0NClRv
OiBMaW5kYSBEdW5iYXIgPGxpbmRhLmR1bmJhckBodWF3ZWkuY29tPg0KQ2M6IFJhZmEgTWFyaW4g
TG9wZXogPHJhZmFAdW0uZXM+OyBZb2F2IE5pciA8eW5pci5pZXRmQGdtYWlsLmNvbT47IGkybnNm
QGlldGYub3JnOyBQYXVsIFdvdXRlcnMgPHBhdWxAbm9oYXRzLmNhPg0KU3ViamVjdDogUmU6IFtJ
Mm5zZl0gWUFORyBtb2R1bGUgdXBkYXRlIHdoZW4gbmV3IGFsZ29yaXRobXMgYWRkZWQgdG8gSVBz
ZWMsIFJFOiBSZXZpZXdpbmcgc2RuLWlwc2VjLWZsb3ctcHJvdGVjdGlvbg0KDQpIaSBMaW5kYToN
Cg0KVGhhdCB3YXMgYWxzbyBzdWdnZXN0ZWQuIEluIGZhY3QsIG91ciBkb3VidCBpcyB3aGV0aGVy
IHdlIHNob3VsZCByZWZlciB0byBzb21ldGhpbmcgbGlrZToNCg0KaHR0cHM6Ly90b29scy5pZXRm
Lm9yZy9odG1sL2RyYWZ0LWlldGYtbmV0Y29uZi1jcnlwdG8tdHlwZXMtMDINCg0KSW4gZmFjdCB5
b3UgY2FuIHNlZSBpbiB0aGlzIHJlZmVyZW5jZSB0aGluZ3MgbGlrZToNCg0KaWRlbnRpdHkgaG1h
Yy1zaGEyLTI1Ni0xMjggew0KICAgICAgYmFzZSAibWFjLWFsZ29yaXRobSI7DQogICAgICBkZXNj
cmlwdGlvbg0KICAgICAgICAiR2VuZXJhdGluZyBhIDI1NiBiaXRzIE1BQyB1c2luZyBTSEEyIGhh
c2ggZnVuY3Rpb24gYW5kIHRydW5jYXRlDQogICAgICAgICBpdCB0byAxMjggYml0cyI7DQogICAg
ICByZWZlcmVuY2UNCiAgICAgICAgIg0KUkZDIDQ4NjgNCjoNCiAgICAgICAgICAgVXNpbmcgSE1B
Qy1TSEEtMjU2LCBITUFDLVNIQS0zODQsIGFuZCBITUFDLVNIQS01MTIgd2l0aA0KICAgICAgICAg
ICBJUFNlYyI7DQoNCkFsdGhvdWdoIEkgdGhpbmsgdGhhdCB0aGUgY29udGVudCBvZiB0aGlzIHJl
ZmVyZW5jZSBzaG91bGQgYmUgZXhwYW5kZWQuDQoNCkFzIGFub3RoZXIgZXhhbXBsZSwgYmVzaWRl
cyB5b3VycywgdGhleSBmb2xsb3cgdGhlIG1vZGVsIG9mIGltcG9ydGluZzoNCg0KaHR0cHM6Ly90
b29scy5pZXRmLm9yZy9odG1sL2RyYWZ0LWlldGYtbmV0Y29uZi10bHMtY2xpZW50LXNlcnZlci0w
OA0KDQpCZXN0IFJlZ2FyZHMuDQoNCg0KRWwgNSBkaWMgMjAxOCwgYSBsYXMgMjE6NDgsIExpbmRh
IER1bmJhciA8bGluZGEuZHVuYmFyQGh1YXdlaS5jb208bWFpbHRvOmxpbmRhLmR1bmJhckBodWF3
ZWkuY29tPj4gZXNjcmliacOzOg0KDQpZb2F2IGFza2VkOg0K4oCcV2hhdCBpcyBvdXIgcGxhbiBm
b3IgZnV0dXJlIGV4cGFuc2lvbnM/ICBTdXBwb3NlIHRoZXJl4oCZcyBzb21lIGhvdCwgbmV3IGFs
Z29yaXRobSB0aGF0IGV2ZXJ5b25lIGlzIGltcGxlbWVudGluZy4gSG93IGRvIHlvdSB1cGRhdGUg
dGhlIFlBTkcgbW9kZWwgaW4gdGhlIGZ1dHVyZSB3aGVuIHlvdSBhZGQgbmV3IHZhbHVlcyB0byB0
aGUgZW51bWVyYXRpb25zPyAgSXMgaXQgdXAgdG8gdGhlIGFkbWluaXN0cmF0b3IgdG8gbWFrZSBz
dXJlIHRoYXQgdGhlIGNvbnRyb2xsZXIgYW5kIE5TRnMgYXJlIGFsbCBvbiB0aGUg4oCcc2FtZSBw
YWdl4oCdP+KAnQ0KDQpXZSBjYW4gdXNlIOKAnGltcG9ydOKAnSBhbmQg4oCcYXVnbWVudOKAnSB0
byBhZGQgbmV3IGF0dHJpYnV0ZXMgYXMgZGVtb25zdHJhdGVkIGJ5aHR0cHM6Ly9kYXRhdHJhY2tl
ci5pZXRmLm9yZy9kb2MvZHJhZnQtbGVlLWNjYW1wLW9wdGljYWwtaW1wYWlybWVudC10b3BvbG9n
eS15YW5nLz9pbmNsdWRlX3RleHQ9MQ0KDQoNCkxpbmRhDQpGcm9tOiBJMm5zZiBbbWFpbHRvOmky
bnNmLWJvdW5jZXNAaWV0Zi5vcmddIE9uIEJlaGFsZiBPZiBZb2F2IE5pcg0KU2VudDogV2VkbmVz
ZGF5LCBOb3ZlbWJlciAxNCwgMjAxOCAxMjozMyBQTQ0KVG86IFJhZmEgTWFyaW4tTG9wZXogPHJh
ZmFAdW0uZXM8bWFpbHRvOnJhZmFAdW0uZXM+Pg0KQ2M6IGkybnNmQGlldGYub3JnPG1haWx0bzpp
Mm5zZkBpZXRmLm9yZz47IFBhdWwgV291dGVycyA8cGF1bEBub2hhdHMuY2E8bWFpbHRvOnBhdWxA
bm9oYXRzLmNhPj4NClN1YmplY3Q6IFJlOiBbSTJuc2ZdIFJldmlld2luZyBzZG4taXBzZWMtZmxv
dy1wcm90ZWN0aW9uDQoNClRoYW5rcywgUmFmYS4NCg0KSnVzdCBvbmUgcmVzcG9uc2UgYmVsb3cu
DQoNCg0KDQpPbiAxNCBOb3YgMjAxOCwgYXQgMTE6MzAsIFJhZmEgTWFyaW4tTG9wZXogPHJhZmFA
dW0uZXM8bWFpbHRvOnJhZmFAdW0uZXM+PiB3cm90ZToNCg0KSGkgWW9hdjoNCg0KDQoNCkVsIDgg
bm92IDIwMTgsIGEgbGFzIDE3OjExLCBZb2F2IE5pciA8eW5pci5pZXRmQGdtYWlsLmNvbTxtYWls
dG86eW5pci5pZXRmQGdtYWlsLmNvbT4+IGVzY3JpYmnDszoNCg0KSGksIGFsbA0KDQpBcyBkaXNj
dXNzZWQgaW4gdGhlIHJvb20sIHdlIG5lZWQgc29tZSByZXZpZXdlcnMgZm9yIHRoZSBzZG4taXBz
ZWMtZmxvdy1wcm90ZWN0aW9uIGRyYWZ0IChbMV0pDQoNClRoYW5rcyBmb3IgdGhlc2UgY29tbWVu
dHMuIFBsZWFzZSBzZWUgb3VyIHJlc3BvbnNlIGJlbG93Lg0KDQoNCg0KV2hpbGUgYW55IGNvbW1l
bnRzIG9uIGFueSBwYXJ0IG9mIHRoZSBkb2N1bWVudCBhcmUgd2VsY29tZSwgSSB3b3VsZCBsaWtl
IHBlb3BsZSB0byBjb25jZW50cmF0ZSBvbiB0aGUgZm9sbG93aW5nIGlzc3VlczoNCg0KICAqICAg
VGhlIFlBTkcgbW9kZWwgaW4gQXBwZW5kaXggQQ0KDQogICAgICogICBTb21lIG9mIHRoZSBjcnlw
dG8gc2VlbXMgb2Jzb2xldGUgKGV4YW1wbGU6IERFUykuIFdlIHdvdWxkIGdldCBpbnRvIHRyb3Vi
bGUgaW4gU2VjRGlyIHJldmlldy4gIE9UT0ggQ2hhQ2hhMjAtUG9seTEzMDUgaXMgbWlzc2luZy4u
DQoNCkFncmVlLiBXZSB3aWxsIHJlbW92ZSBERVMgYW5kIGFkZCB0aGUgYWxnb3JpdGhtIHlvdSBt
ZW50aW9uLg0KDQpUaGUgVExTIHdvcmtpbmcgZ3JvdXAgd2VudCBxdWl0ZSBmYXIgd2l0aCBUTFMg
MS4zLiAgT25seSAyIGNpcGhlcnMgcmVtYWluOiBBRVMtR0NNIHdpdGggMTYtYnl0ZSBJQ1YsIGFu
ZCBDaGFDaGEyMC1Qb2x5MTMwNS4gVGhhdOKAmXMgaXQuICBTcGVjaWZpY2FsbHksIHRoZXnigJl2
ZSBkZXByZWNhdGVkIGV2ZXJ5dGhpbmcgdGhhdCBpc27igJl0IGFuIEFFQUQuDQoNClRoZSBJUHNl
Y01FIHdvcmtpbmcgZ3JvdXAgaGFzbuKAmXQgZ29uZSB0aGF0IGZhciB5ZXQuICBCdXQgaW4gcHJh
Y3RpY2UgcHJldHR5IG11Y2ggbm90aGluZyBpcyB1c2VkIGV4Y2VwdCAzREVTLCBBRVMtQ0JDLCBh
bmQgQUVTLUdDTS4gIFBlcmhhcHMgQ2hhQ2hhMjAtUG9seTEzMDUgaXMgc3RhcnRpbmcgdG8gc2Vl
IHNvbWUgdXNlIGJ5IG5vdy4gV2UgaGF2ZSBSRkMgODIyMSwgZXNwZWNpYWxseSBzZWN0aW9ucyA1
IGFuZCA2LiAgSSB0aGluayAoYWx0aG91Z2ggaXTigJlzIHVwIHRvIHRoZSB3b3JraW5nIGdyb3Vw
KSB0aGF0IHdlIHNob3VsZCBiZSBmaW5lIGRlZmluaW5nIG9ubHkgdGhlIE1VU1RzIGFuZCB0aGUg
U0hPVUxEcyBpbiB0aG9zZSBzZWN0aW9ucy4NCg0KVGhhdCBicmluZ3MgYW5vdGhlciBxdWVzdGlv
bi4gV2hhdCBpcyBvdXIgcGxhbiBmb3IgZnV0dXJlIGV4cGFuc2lvbnM/ICBTdXBwb3NlIHRoZXJl
4oCZcyBzb21lIGhvdCwgbmV3IGFsZ29yaXRobSB0aGF0IGV2ZXJ5b25lIGlzIGltcGxlbWVudGlu
Zy4gSG93IGRvIHlvdSB1cGRhdGUgdGhlIFlBTkcgbW9kZWwgaW4gdGhlIGZ1dHVyZSB3aGVuIHlv
dSBhZGQgbmV3IHZhbHVlcyB0byB0aGUgZW51bWVyYXRpb25zPyAgSXMgaXQgdXAgdG8gdGhlIGFk
bWluaXN0cmF0b3IgdG8gbWFrZSBzdXJlIHRoYXQgdGhlIGNvbnRyb2xsZXIgYW5kIE5TRnMgYXJl
IGFsbCBvbiB0aGUg4oCcc2FtZSBwYWdl4oCdPw0KDQpUaGFua3MNCg0KWW9hdg0KX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCkkybnNmIG1haWxpbmcgbGlz
dA0KSTJuc2ZAaWV0Zi5vcmc8bWFpbHRvOkkybnNmQGlldGYub3JnPg0KaHR0cHM6Ly93d3cuaWV0
Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9pMm5zZg0KDQo=

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

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTUgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
Q291cmllcjsNCglwYW5vc2UtMToyIDcgNCA5IDIgMiA1IDIgNCA0O30NCkBmb250LWZhY2UNCgl7
Zm9udC1mYW1pbHk6U2ltU3VuOw0KCXBhbm9zZS0xOjIgMSA2IDAgMyAxIDEgMSAxIDE7fQ0KQGZv
bnQtZmFjZQ0KCXtmb250LWZhbWlseToiQ2FtYnJpYSBNYXRoIjsNCglwYW5vc2UtMToyIDQgNSAz
IDUgNCA2IDMgMiA0O30NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6Q2FsaWJyaTsNCglwYW5v
c2UtMToyIDE1IDUgMiAyIDIgNCAzIDIgNDt9DQpAZm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5OiJc
QFNpbVN1biI7DQoJcGFub3NlLTE6MiAxIDYgMCAzIDEgMSAxIDEgMTt9DQovKiBTdHlsZSBEZWZp
bml0aW9ucyAqLw0KcC5Nc29Ob3JtYWwsIGxpLk1zb05vcm1hbCwgZGl2Lk1zb05vcm1hbA0KCXtt
YXJnaW46MGluOw0KCW1hcmdpbi1ib3R0b206LjAwMDFwdDsNCglmb250LXNpemU6MTIuMHB0Ow0K
CWZvbnQtZmFtaWx5OiJUaW1lcyBOZXcgUm9tYW4iLHNlcmlmO30NCmE6bGluaywgc3Bhbi5Nc29I
eXBlcmxpbmsNCgl7bXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0KCWNvbG9yOmJsdWU7DQoJdGV4dC1k
ZWNvcmF0aW9uOnVuZGVybGluZTt9DQphOnZpc2l0ZWQsIHNwYW4uTXNvSHlwZXJsaW5rRm9sbG93
ZWQNCgl7bXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0KCWNvbG9yOnB1cnBsZTsNCgl0ZXh0LWRlY29y
YXRpb246dW5kZXJsaW5lO30NCnNwYW4uYXBwbGUtY29udmVydGVkLXNwYWNlDQoJe21zby1zdHls
ZS1uYW1lOmFwcGxlLWNvbnZlcnRlZC1zcGFjZTt9DQpzcGFuLkVtYWlsU3R5bGUxOA0KCXttc28t
c3R5bGUtdHlwZTpwZXJzb25hbC1yZXBseTsNCglmb250LWZhbWlseToiQ2FsaWJyaSIsc2Fucy1z
ZXJpZjsNCgljb2xvcjojMUY0OTdEO30NCi5Nc29DaHBEZWZhdWx0DQoJe21zby1zdHlsZS10eXBl
OmV4cG9ydC1vbmx5Ow0KCWZvbnQtc2l6ZToxMC4wcHQ7fQ0KQHBhZ2UgV29yZFNlY3Rpb24xDQoJ
e3NpemU6OC41aW4gMTEuMGluOw0KCW1hcmdpbjoxLjBpbiAxLjBpbiAxLjBpbiAxLjBpbjt9DQpk
aXYuV29yZFNlY3Rpb24xDQoJe3BhZ2U6V29yZFNlY3Rpb24xO30NCi8qIExpc3QgRGVmaW5pdGlv
bnMgKi8NCkBsaXN0IGwwDQoJe21zby1saXN0LWlkOjE3MDcyNzY3MjsNCgltc28tbGlzdC10ZW1w
bGF0ZS1pZHM6MjUxOTQyMDc2O30NCkBsaXN0IGwwOmxldmVsMQ0KCXttc28tbGV2ZWwtbnVtYmVy
LWZvcm1hdDpidWxsZXQ7DQoJbXNvLWxldmVsLXRleHQ674K3Ow0KCW1zby1sZXZlbC10YWItc3Rv
cDouNWluOw0KCW1zby1sZXZlbC1udW1iZXItcG9zaXRpb246bGVmdDsNCgl0ZXh0LWluZGVudDot
LjI1aW47DQoJbXNvLWFuc2ktZm9udC1zaXplOjEwLjBwdDsNCglmb250LWZhbWlseTpTeW1ib2w7
fQ0KQGxpc3QgbDA6bGV2ZWwyDQoJe21zby1sZXZlbC1udW1iZXItZm9ybWF0OmJ1bGxldDsNCglt
c28tbGV2ZWwtdGV4dDpvOw0KCW1zby1sZXZlbC10YWItc3RvcDoxLjBpbjsNCgltc28tbGV2ZWwt
bnVtYmVyLXBvc2l0aW9uOmxlZnQ7DQoJdGV4dC1pbmRlbnQ6LS4yNWluOw0KCW1zby1hbnNpLWZv
bnQtc2l6ZToxMC4wcHQ7DQoJZm9udC1mYW1pbHk6IkNvdXJpZXIgTmV3IjsNCgltc28tYmlkaS1m
b250LWZhbWlseToiVGltZXMgTmV3IFJvbWFuIjt9DQpAbGlzdCBsMDpsZXZlbDMNCgl7bXNvLWxl
dmVsLW51bWJlci1mb3JtYXQ6YnVsbGV0Ow0KCW1zby1sZXZlbC10ZXh0Ou+CtzsNCgltc28tbGV2
ZWwtdGFiLXN0b3A6MS41aW47DQoJbXNvLWxldmVsLW51bWJlci1wb3NpdGlvbjpsZWZ0Ow0KCXRl
eHQtaW5kZW50Oi0uMjVpbjsNCgltc28tYW5zaS1mb250LXNpemU6MTAuMHB0Ow0KCWZvbnQtZmFt
aWx5OlN5bWJvbDt9DQpAbGlzdCBsMDpsZXZlbDQNCgl7bXNvLWxldmVsLW51bWJlci1mb3JtYXQ6
YnVsbGV0Ow0KCW1zby1sZXZlbC10ZXh0Ou+CtzsNCgltc28tbGV2ZWwtdGFiLXN0b3A6Mi4waW47
DQoJbXNvLWxldmVsLW51bWJlci1wb3NpdGlvbjpsZWZ0Ow0KCXRleHQtaW5kZW50Oi0uMjVpbjsN
Cgltc28tYW5zaS1mb250LXNpemU6MTAuMHB0Ow0KCWZvbnQtZmFtaWx5OlN5bWJvbDt9DQpAbGlz
dCBsMDpsZXZlbDUNCgl7bXNvLWxldmVsLW51bWJlci1mb3JtYXQ6YnVsbGV0Ow0KCW1zby1sZXZl
bC10ZXh0Ou+CtzsNCgltc28tbGV2ZWwtdGFiLXN0b3A6Mi41aW47DQoJbXNvLWxldmVsLW51bWJl
ci1wb3NpdGlvbjpsZWZ0Ow0KCXRleHQtaW5kZW50Oi0uMjVpbjsNCgltc28tYW5zaS1mb250LXNp
emU6MTAuMHB0Ow0KCWZvbnQtZmFtaWx5OlN5bWJvbDt9DQpAbGlzdCBsMDpsZXZlbDYNCgl7bXNv
LWxldmVsLW51bWJlci1mb3JtYXQ6YnVsbGV0Ow0KCW1zby1sZXZlbC10ZXh0Ou+CtzsNCgltc28t
bGV2ZWwtdGFiLXN0b3A6My4waW47DQoJbXNvLWxldmVsLW51bWJlci1wb3NpdGlvbjpsZWZ0Ow0K
CXRleHQtaW5kZW50Oi0uMjVpbjsNCgltc28tYW5zaS1mb250LXNpemU6MTAuMHB0Ow0KCWZvbnQt
ZmFtaWx5OlN5bWJvbDt9DQpAbGlzdCBsMDpsZXZlbDcNCgl7bXNvLWxldmVsLW51bWJlci1mb3Jt
YXQ6YnVsbGV0Ow0KCW1zby1sZXZlbC10ZXh0Ou+CtzsNCgltc28tbGV2ZWwtdGFiLXN0b3A6My41
aW47DQoJbXNvLWxldmVsLW51bWJlci1wb3NpdGlvbjpsZWZ0Ow0KCXRleHQtaW5kZW50Oi0uMjVp
bjsNCgltc28tYW5zaS1mb250LXNpemU6MTAuMHB0Ow0KCWZvbnQtZmFtaWx5OlN5bWJvbDt9DQpA
bGlzdCBsMDpsZXZlbDgNCgl7bXNvLWxldmVsLW51bWJlci1mb3JtYXQ6YnVsbGV0Ow0KCW1zby1s
ZXZlbC10ZXh0Ou+CtzsNCgltc28tbGV2ZWwtdGFiLXN0b3A6NC4waW47DQoJbXNvLWxldmVsLW51
bWJlci1wb3NpdGlvbjpsZWZ0Ow0KCXRleHQtaW5kZW50Oi0uMjVpbjsNCgltc28tYW5zaS1mb250
LXNpemU6MTAuMHB0Ow0KCWZvbnQtZmFtaWx5OlN5bWJvbDt9DQpAbGlzdCBsMDpsZXZlbDkNCgl7
bXNvLWxldmVsLW51bWJlci1mb3JtYXQ6YnVsbGV0Ow0KCW1zby1sZXZlbC10ZXh0Ou+CtzsNCglt
c28tbGV2ZWwtdGFiLXN0b3A6NC41aW47DQoJbXNvLWxldmVsLW51bWJlci1wb3NpdGlvbjpsZWZ0
Ow0KCXRleHQtaW5kZW50Oi0uMjVpbjsNCgltc28tYW5zaS1mb250LXNpemU6MTAuMHB0Ow0KCWZv
bnQtZmFtaWx5OlN5bWJvbDt9DQpAbGlzdCBsMQ0KCXttc28tbGlzdC1pZDoxODQ2MDIwMDQ1Ow0K
CW1zby1saXN0LXRlbXBsYXRlLWlkczotOTk5OTQxMjMwO30NCkBsaXN0IGwxOmxldmVsMQ0KCXtt
c28tbGV2ZWwtbnVtYmVyLWZvcm1hdDpidWxsZXQ7DQoJbXNvLWxldmVsLXRleHQ674K3Ow0KCW1z
by1sZXZlbC10YWItc3RvcDouNWluOw0KCW1zby1sZXZlbC1udW1iZXItcG9zaXRpb246bGVmdDsN
Cgl0ZXh0LWluZGVudDotLjI1aW47DQoJbXNvLWFuc2ktZm9udC1zaXplOjEwLjBwdDsNCglmb250
LWZhbWlseTpTeW1ib2w7fQ0KQGxpc3QgbDE6bGV2ZWwyDQoJe21zby1sZXZlbC1udW1iZXItZm9y
bWF0OmJ1bGxldDsNCgltc28tbGV2ZWwtdGV4dDrvgrc7DQoJbXNvLWxldmVsLXRhYi1zdG9wOjEu
MGluOw0KCW1zby1sZXZlbC1udW1iZXItcG9zaXRpb246bGVmdDsNCgl0ZXh0LWluZGVudDotLjI1
aW47DQoJbXNvLWFuc2ktZm9udC1zaXplOjEwLjBwdDsNCglmb250LWZhbWlseTpTeW1ib2w7fQ0K
QGxpc3QgbDE6bGV2ZWwzDQoJe21zby1sZXZlbC1udW1iZXItZm9ybWF0OmJ1bGxldDsNCgltc28t
bGV2ZWwtdGV4dDrvgrc7DQoJbXNvLWxldmVsLXRhYi1zdG9wOjEuNWluOw0KCW1zby1sZXZlbC1u
dW1iZXItcG9zaXRpb246bGVmdDsNCgl0ZXh0LWluZGVudDotLjI1aW47DQoJbXNvLWFuc2ktZm9u
dC1zaXplOjEwLjBwdDsNCglmb250LWZhbWlseTpTeW1ib2w7fQ0KQGxpc3QgbDE6bGV2ZWw0DQoJ
e21zby1sZXZlbC1udW1iZXItZm9ybWF0OmJ1bGxldDsNCgltc28tbGV2ZWwtdGV4dDrvgrc7DQoJ
bXNvLWxldmVsLXRhYi1zdG9wOjIuMGluOw0KCW1zby1sZXZlbC1udW1iZXItcG9zaXRpb246bGVm
dDsNCgl0ZXh0LWluZGVudDotLjI1aW47DQoJbXNvLWFuc2ktZm9udC1zaXplOjEwLjBwdDsNCglm
b250LWZhbWlseTpTeW1ib2w7fQ0KQGxpc3QgbDE6bGV2ZWw1DQoJe21zby1sZXZlbC1udW1iZXIt
Zm9ybWF0OmJ1bGxldDsNCgltc28tbGV2ZWwtdGV4dDrvgrc7DQoJbXNvLWxldmVsLXRhYi1zdG9w
OjIuNWluOw0KCW1zby1sZXZlbC1udW1iZXItcG9zaXRpb246bGVmdDsNCgl0ZXh0LWluZGVudDot
LjI1aW47DQoJbXNvLWFuc2ktZm9udC1zaXplOjEwLjBwdDsNCglmb250LWZhbWlseTpTeW1ib2w7
fQ0KQGxpc3QgbDE6bGV2ZWw2DQoJe21zby1sZXZlbC1udW1iZXItZm9ybWF0OmJ1bGxldDsNCglt
c28tbGV2ZWwtdGV4dDrvgrc7DQoJbXNvLWxldmVsLXRhYi1zdG9wOjMuMGluOw0KCW1zby1sZXZl
bC1udW1iZXItcG9zaXRpb246bGVmdDsNCgl0ZXh0LWluZGVudDotLjI1aW47DQoJbXNvLWFuc2kt
Zm9udC1zaXplOjEwLjBwdDsNCglmb250LWZhbWlseTpTeW1ib2w7fQ0KQGxpc3QgbDE6bGV2ZWw3
DQoJe21zby1sZXZlbC1udW1iZXItZm9ybWF0OmJ1bGxldDsNCgltc28tbGV2ZWwtdGV4dDrvgrc7
DQoJbXNvLWxldmVsLXRhYi1zdG9wOjMuNWluOw0KCW1zby1sZXZlbC1udW1iZXItcG9zaXRpb246
bGVmdDsNCgl0ZXh0LWluZGVudDotLjI1aW47DQoJbXNvLWFuc2ktZm9udC1zaXplOjEwLjBwdDsN
Cglmb250LWZhbWlseTpTeW1ib2w7fQ0KQGxpc3QgbDE6bGV2ZWw4DQoJe21zby1sZXZlbC1udW1i
ZXItZm9ybWF0OmJ1bGxldDsNCgltc28tbGV2ZWwtdGV4dDrvgrc7DQoJbXNvLWxldmVsLXRhYi1z
dG9wOjQuMGluOw0KCW1zby1sZXZlbC1udW1iZXItcG9zaXRpb246bGVmdDsNCgl0ZXh0LWluZGVu
dDotLjI1aW47DQoJbXNvLWFuc2ktZm9udC1zaXplOjEwLjBwdDsNCglmb250LWZhbWlseTpTeW1i
b2w7fQ0KQGxpc3QgbDE6bGV2ZWw5DQoJe21zby1sZXZlbC1udW1iZXItZm9ybWF0OmJ1bGxldDsN
Cgltc28tbGV2ZWwtdGV4dDrvgrc7DQoJbXNvLWxldmVsLXRhYi1zdG9wOjQuNWluOw0KCW1zby1s
ZXZlbC1udW1iZXItcG9zaXRpb246bGVmdDsNCgl0ZXh0LWluZGVudDotLjI1aW47DQoJbXNvLWFu
c2ktZm9udC1zaXplOjEwLjBwdDsNCglmb250LWZhbWlseTpTeW1ib2w7fQ0Kb2wNCgl7bWFyZ2lu
LWJvdHRvbTowaW47fQ0KdWwNCgl7bWFyZ2luLWJvdHRvbTowaW47fQ0KLS0+PC9zdHlsZT48IS0t
W2lmIGd0ZSBtc28gOV0+PHhtbD4NCjxvOnNoYXBlZGVmYXVsdHMgdjpleHQ9ImVkaXQiIHNwaWRt
YXg9IjEwMjYiIC8+DQo8L3htbD48IVtlbmRpZl0tLT48IS0tW2lmIGd0ZSBtc28gOV0+PHhtbD4N
CjxvOnNoYXBlbGF5b3V0IHY6ZXh0PSJlZGl0Ij4NCjxvOmlkbWFwIHY6ZXh0PSJlZGl0IiBkYXRh
PSIxIiAvPg0KPC9vOnNoYXBlbGF5b3V0PjwveG1sPjwhW2VuZGlmXS0tPg0KPC9oZWFkPg0KPGJv
ZHkgbGFuZz0iRU4tVVMiIGxpbms9ImJsdWUiIHZsaW5rPSJwdXJwbGUiPg0KPGRpdiBjbGFzcz0i
V29yZFNlY3Rpb24xIj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNp
emU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZjtjb2xv
cjojMUY0OTdEIj5SYWZhLA0KPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2Fs
aWJyaSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOiMxRjQ5N0QiPjxvOnA+Jm5ic3A7PC9vOnA+PC9z
cGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEu
MHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjojMUY0
OTdEIj5UaGFua3MgZm9yIGdldHRpbmcgYSBiZXR0ZXIgcmVmZXJlbmNlLiBJIGxpa2UgeW91ciBh
cHByb2FjaC4NCjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxz
cGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVv
dDssc2Fucy1zZXJpZjtjb2xvcjojMUY0OTdEIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250
LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6IzFGNDk3RCI+TGlu
ZGE8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48YSBuYW1lPSJf
TWFpbEVuZENvbXBvc2UiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5
OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjojMUY0OTdEIj48bzpwPiZuYnNw
OzwvbzpwPjwvc3Bhbj48L2E+PC9wPg0KPGRpdj4NCjxkaXYgc3R5bGU9ImJvcmRlcjpub25lO2Jv
cmRlci10b3A6c29saWQgI0UxRTFFMSAxLjBwdDtwYWRkaW5nOjMuMHB0IDBpbiAwaW4gMGluIj4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2Zv
bnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZiI+RnJvbTo8L3NwYW4+PC9i
PjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkm
cXVvdDssc2Fucy1zZXJpZiI+IFJhZmEgTWFyaW4gTG9wZXogW21haWx0bzpyYWZhQHVtLmVzXQ0K
PGJyPg0KPGI+U2VudDo8L2I+IFRodXJzZGF5LCBEZWNlbWJlciAwNiwgMjAxOCAzOjM5IEFNPGJy
Pg0KPGI+VG86PC9iPiBMaW5kYSBEdW5iYXIgJmx0O2xpbmRhLmR1bmJhckBodWF3ZWkuY29tJmd0
Ozxicj4NCjxiPkNjOjwvYj4gUmFmYSBNYXJpbiBMb3BleiAmbHQ7cmFmYUB1bS5lcyZndDs7IFlv
YXYgTmlyICZsdDt5bmlyLmlldGZAZ21haWwuY29tJmd0OzsgaTJuc2ZAaWV0Zi5vcmc7IFBhdWwg
V291dGVycyAmbHQ7cGF1bEBub2hhdHMuY2EmZ3Q7PGJyPg0KPGI+U3ViamVjdDo8L2I+IFJlOiBb
STJuc2ZdIFlBTkcgbW9kdWxlIHVwZGF0ZSB3aGVuIG5ldyBhbGdvcml0aG1zIGFkZGVkIHRvIElQ
c2VjLCBSRTogUmV2aWV3aW5nIHNkbi1pcHNlYy1mbG93LXByb3RlY3Rpb248bzpwPjwvbzpwPjwv
c3Bhbj48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJz
cDs8L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5IaSBMaW5kYTo8bzpwPjwvbzpwPjwv
cD4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwv
ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPlRoYXQgd2FzIGFsc28gc3VnZ2VzdGVk
LiBJbiBmYWN0LCBvdXIgZG91YnQgaXMgd2hldGhlciB3ZSBzaG91bGQgcmVmZXIgdG8gc29tZXRo
aW5nIGxpa2U6PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9y
bWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29O
b3JtYWwiPjxhIGhyZWY9Imh0dHBzOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9kcmFmdC1pZXRmLW5l
dGNvbmYtY3J5cHRvLXR5cGVzLTAyIj5odHRwczovL3Rvb2xzLmlldGYub3JnL2h0bWwvZHJhZnQt
aWV0Zi1uZXRjb25mLWNyeXB0by10eXBlcy0wMjwvYT48bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0K
PGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+
DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+SW4gZmFjdCB5b3UgY2FuIHNlZSBpbiB0aGlz
IHJlZmVyZW5jZSB0aGluZ3MgbGlrZTo8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0K
PGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPmlkZW50aXR5IGhtYWMtc2hhMi0yNTYtMTI4IHs8
bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPiZuYnNw
OyAmbmJzcDsgJm5ic3A7IGJhc2UgJnF1b3Q7bWFjLWFsZ29yaXRobSZxdW90Ozs8bzpwPjwvbzpw
PjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPiZuYnNwOyAmbmJzcDsg
Jm5ic3A7IGRlc2NyaXB0aW9uPG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFz
cz0iTXNvTm9ybWFsIj4mbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJnF1b3Q7R2VuZXJhdGlu
ZyBhIDI1NiBiaXRzIE1BQyB1c2luZyBTSEEyIGhhc2ggZnVuY3Rpb24gYW5kIHRydW5jYXRlPG86
cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj4mbmJzcDsg
Jm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7aXQgdG8gMTI4IGJpdHMmcXVvdDs7PG86cD48L286
cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj4mbmJzcDsgJm5ic3A7
ICZuYnNwOyByZWZlcmVuY2U8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiPiZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmcXVvdDs8bzpwPjwvbzpw
PjwvcD4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+UkZDIDQ4Njg8bzpwPjwvbzpwPjwv
cD4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj46PG86cD48L286cD48L3A+DQo8L2Rpdj4N
CjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj4mbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsg
Jm5ic3A7ICZuYnNwO1VzaW5nIEhNQUMtU0hBLTI1NiwgSE1BQy1TSEEtMzg0LCBhbmQgSE1BQy1T
SEEtNTEyIHdpdGg8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29O
b3JtYWwiPiZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7PGI+SVBTZWM8
L2I+JnF1b3Q7OzxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFz
cz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiPkFsdGhvdWdoIEkgdGhpbmsgdGhhdCB0aGUgY29udGVudCBvZiB0aGlz
IHJlZmVyZW5jZSBzaG91bGQgYmUgZXhwYW5kZWQuPG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxk
aXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0K
PGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPkFzIGFub3RoZXIgZXhhbXBsZSwgYmVzaWRlcyB5
b3VycywgdGhleSBmb2xsb3cgdGhlIG1vZGVsIG9mIGltcG9ydGluZzo8bzpwPjwvbzpwPjwvcD4N
CjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9w
Pg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PGEgaHJlZj0iaHR0cHM6Ly90
b29scy5pZXRmLm9yZy9odG1sL2RyYWZ0LWlldGYtbmV0Y29uZi10bHMtY2xpZW50LXNlcnZlci0w
OCI+aHR0cHM6Ly90b29scy5pZXRmLm9yZy9odG1sL2RyYWZ0LWlldGYtbmV0Y29uZi10bHMtY2xp
ZW50LXNlcnZlci0wODwvYT48bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCI+QmVzdCBSZWdhcmRzLjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjxk
aXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxkaXY+DQo8
YmxvY2txdW90ZSBzdHlsZT0ibWFyZ2luLXRvcDo1LjBwdDttYXJnaW4tYm90dG9tOjUuMHB0Ij4N
CjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5FbCA1IGRpYyAyMDE4LCBhIGxhcyAyMTo0OCwg
TGluZGEgRHVuYmFyICZsdDs8YSBocmVmPSJtYWlsdG86bGluZGEuZHVuYmFyQGh1YXdlaS5jb20i
PmxpbmRhLmR1bmJhckBodWF3ZWkuY29tPC9hPiZndDsgZXNjcmliacOzOjxvOnA+PC9vOnA+PC9w
Pg0KPC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxk
aXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+WW9hdiBhc2tlZDo8bzpwPjwvbzpwPjwv
cD4NCjwvZGl2Pg0KPGRpdiBzdHlsZT0ibWFyZ2luLWxlZnQ6LjVpbiI+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIj7igJw8aT5XaGF0IGlzIG91ciBwbGFuIGZvciBmdXR1cmUgZXhwYW5zaW9ucz8gJm5i
c3A7U3VwcG9zZSB0aGVyZeKAmXMgc29tZSBob3QsIG5ldyBhbGdvcml0aG0gdGhhdCBldmVyeW9u
ZSBpcyBpbXBsZW1lbnRpbmcuIEhvdyBkbyB5b3UgdXBkYXRlIHRoZSBZQU5HIG1vZGVsIGluIHRo
ZSBmdXR1cmUgd2hlbiB5b3UgYWRkIG5ldyB2YWx1ZXMgdG8gdGhlIGVudW1lcmF0aW9ucz8gJm5i
c3A7SXMgaXQgdXAgdG8gdGhlIGFkbWluaXN0cmF0b3INCiB0byBtYWtlIHN1cmUgdGhhdCB0aGUg
Y29udHJvbGxlciBhbmQgTlNGcyBhcmUgYWxsIG9uIHRoZSDigJxzYW1lIHBhZ2XigJ0/4oCdPC9p
PjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNw
YW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90
OyxzYW5zLXNlcmlmO2NvbG9yOiMxRjQ5N0QiPiZuYnNwOzwvc3Bhbj48bzpwPjwvbzpwPjwvcD4N
CjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPldlIGNhbiB1c2Ug4oCcaW1wb3J0
4oCdIGFuZCDigJxhdWdtZW504oCdIHRvIGFkZCBuZXcgYXR0cmlidXRlcyBhcyBkZW1vbnN0cmF0
ZWQgYnk8YSBocmVmPSJodHRwczovL2RhdGF0cmFja2VyLmlldGYub3JnL2RvYy9kcmFmdC1sZWUt
Y2NhbXAtb3B0aWNhbC1pbXBhaXJtZW50LXRvcG9sb2d5LXlhbmcvP2luY2x1ZGVfdGV4dD0xIj48
c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1
b3Q7LHNhbnMtc2VyaWY7Y29sb3I6cHVycGxlIj5odHRwczovL2RhdGF0cmFja2VyLmlldGYub3Jn
L2RvYy9kcmFmdC1sZWUtY2NhbXAtb3B0aWNhbC1pbXBhaXJtZW50LXRvcG9sb2d5LXlhbmcvP2lu
Y2x1ZGVfdGV4dD0xPC9zcGFuPjwvYT48bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFt
aWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjojMUY0OTdEIj4mbmJzcDs8
L3NwYW4+PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJp
JnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6IzFGNDk3RCI+Jm5ic3A7PC9zcGFuPjxvOnA+PC9vOnA+
PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+TGluZGE8bzpwPjwvbzpw
PjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxkaXYgc3R5bGU9ImJvcmRlcjpub25lO2JvcmRlci10b3A6
c29saWQgI0UxRTFFMSAxLjBwdDtwYWRkaW5nOjMuMHB0IDBpbiAwaW4gMGluIj4NCjxkaXY+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIj48Yj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250
LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWYiPkZyb206PC9zcGFuPjwvYj48
c3BhbiBjbGFzcz0iYXBwbGUtY29udmVydGVkLXNwYWNlIj48c3BhbiBzdHlsZT0iZm9udC1zaXpl
OjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWYiPiZuYnNw
Ozwvc3Bhbj48L3NwYW4+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6
JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmIj5JMm5zZg0KIFs8YSBocmVmPSJtYWlsdG86
aTJuc2YtYm91bmNlc0BpZXRmLm9yZyI+PHNwYW4gc3R5bGU9ImNvbG9yOnB1cnBsZSI+bWFpbHRv
OmkybnNmLWJvdW5jZXNAaWV0Zi5vcmc8L3NwYW4+PC9hPl08c3BhbiBjbGFzcz0iYXBwbGUtY29u
dmVydGVkLXNwYWNlIj4mbmJzcDs8L3NwYW4+PGI+T24gQmVoYWxmIE9mPHNwYW4gY2xhc3M9ImFw
cGxlLWNvbnZlcnRlZC1zcGFjZSI+Jm5ic3A7PC9zcGFuPjwvYj5Zb2F2IE5pcjxicj4NCjxiPlNl
bnQ6PC9iPjxzcGFuIGNsYXNzPSJhcHBsZS1jb252ZXJ0ZWQtc3BhY2UiPiZuYnNwOzwvc3Bhbj5X
ZWRuZXNkYXksIE5vdmVtYmVyIDE0LCAyMDE4IDEyOjMzIFBNPGJyPg0KPGI+VG86PC9iPjxzcGFu
IGNsYXNzPSJhcHBsZS1jb252ZXJ0ZWQtc3BhY2UiPiZuYnNwOzwvc3Bhbj5SYWZhIE1hcmluLUxv
cGV6ICZsdDs8YSBocmVmPSJtYWlsdG86cmFmYUB1bS5lcyI+PHNwYW4gc3R5bGU9ImNvbG9yOnB1
cnBsZSI+cmFmYUB1bS5lczwvc3Bhbj48L2E+Jmd0Ozxicj4NCjxiPkNjOjwvYj48c3BhbiBjbGFz
cz0iYXBwbGUtY29udmVydGVkLXNwYWNlIj4mbmJzcDs8L3NwYW4+PGEgaHJlZj0ibWFpbHRvOmky
bnNmQGlldGYub3JnIj48c3BhbiBzdHlsZT0iY29sb3I6cHVycGxlIj5pMm5zZkBpZXRmLm9yZzwv
c3Bhbj48L2E+OyBQYXVsIFdvdXRlcnMgJmx0OzxhIGhyZWY9Im1haWx0bzpwYXVsQG5vaGF0cy5j
YSI+PHNwYW4gc3R5bGU9ImNvbG9yOnB1cnBsZSI+cGF1bEBub2hhdHMuY2E8L3NwYW4+PC9hPiZn
dDs8YnI+DQo8Yj5TdWJqZWN0OjwvYj48c3BhbiBjbGFzcz0iYXBwbGUtY29udmVydGVkLXNwYWNl
Ij4mbmJzcDs8L3NwYW4+UmU6IFtJMm5zZl0gUmV2aWV3aW5nIHNkbi1pcHNlYy1mbG93LXByb3Rl
Y3Rpb248L3NwYW4+PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8ZGl2
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+Jm5ic3A7PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxk
aXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5UaGFua3MsIFJhZmEuPG86cD48L286cD48L3A+DQo8
L2Rpdj4NCjxkaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+Jm5ic3A7PG86cD48L286
cD48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPGRpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij5KdXN0IG9uZSByZXNwb25zZSBiZWxvdy48bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4N
CjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48YnI+DQo8YnI+DQo8YnI+DQo8bzpwPjwvbzpw
PjwvcD4NCjwvZGl2Pg0KPGJsb2NrcXVvdGUgc3R5bGU9Im1hcmdpbi10b3A6NS4wcHQ7bWFyZ2lu
LWJvdHRvbTo1LjBwdCI+DQo8ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPk9uIDE0
IE5vdiAyMDE4LCBhdCAxMTozMCwgUmFmYSBNYXJpbi1Mb3BleiAmbHQ7PGEgaHJlZj0ibWFpbHRv
OnJhZmFAdW0uZXMiPjxzcGFuIHN0eWxlPSJjb2xvcjpwdXJwbGUiPnJhZmFAdW0uZXM8L3NwYW4+
PC9hPiZndDsgd3JvdGU6PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPGRpdj4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiPiZuYnNwOzxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0K
PGRpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5IaSBZb2F2OjxvOnA+PC9vOnA+PC9w
Pg0KPC9kaXY+DQo8ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxicj4NCjxicj4N
Cjxicj4NCjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8YmxvY2txdW90ZSBzdHlsZT0ibWFyZ2lu
LXRvcDo1LjBwdDttYXJnaW4tYm90dG9tOjUuMHB0Ij4NCjxkaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCI+RWwgOCBub3YgMjAxOCwgYSBsYXMgMTc6MTEsIFlvYXYgTmlyICZsdDs8YSBo
cmVmPSJtYWlsdG86eW5pci5pZXRmQGdtYWlsLmNvbSI+PHNwYW4gc3R5bGU9ImNvbG9yOnB1cnBs
ZSI+eW5pci5pZXRmQGdtYWlsLmNvbTwvc3Bhbj48L2E+Jmd0OyBlc2NyaWJpw7M6PG86cD48L286
cD48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPiZuYnNw
OzxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPGRpdj4NCjxkaXY+DQo8ZGl2Pg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCI+SGksIGFsbDxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0K
PGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPiZuYnNwOzxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+
DQo8L2Rpdj4NCjxkaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+QXMgZGlzY3Vzc2Vk
IGluIHRoZSByb29tLCB3ZSBuZWVkIHNvbWUgcmV2aWV3ZXJzIGZvciB0aGUgc2RuLWlwc2VjLWZs
b3ctcHJvdGVjdGlvbiBkcmFmdCAoWzFdKTxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8L2Rpdj4N
CjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvYmxvY2txdW90ZT4NCjxkaXY+DQo8ZGl2Pg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCI+Jm5ic3A7PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0K
PGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPlRoYW5rcyBmb3IgdGhlc2UgY29tbWVudHMuIFBs
ZWFzZSBzZWUgb3VyIHJlc3BvbnNlIGJlbG93Ljxicj4NCjxicj4NCjxicj4NCjxvOnA+PC9vOnA+
PC9wPg0KPC9kaXY+DQo8YmxvY2txdW90ZSBzdHlsZT0ibWFyZ2luLXRvcDo1LjBwdDttYXJnaW4t
Ym90dG9tOjUuMHB0Ij4NCjxkaXY+DQo8ZGl2Pg0KPGRpdj4NCjxkaXY+DQo8ZGl2Pg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCI+Jm5ic3A7PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPGRp
dj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5XaGlsZSBhbnkgY29tbWVudHMgb24gYW55
IHBhcnQgb2YgdGhlIGRvY3VtZW50IGFyZSB3ZWxjb21lLCBJIHdvdWxkIGxpa2UgcGVvcGxlIHRv
IGNvbmNlbnRyYXRlIG9uIHRoZSBmb2xsb3dpbmcgaXNzdWVzOjxvOnA+PC9vOnA+PC9wPg0KPC9k
aXY+DQo8L2Rpdj4NCjxkaXY+DQo8dWwgc3R5bGU9Im1hcmdpbi10b3A6MGluIiB0eXBlPSJkaXNj
Ij4NCjxsaSBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLWxpc3Q6bDEgbGV2ZWwxIGxmbzEi
PlRoZSBZQU5HIG1vZGVsIGluIEFwcGVuZGl4IEE8bzpwPjwvbzpwPjwvbGk+PC91bD4NCjx1bCBz
dHlsZT0ibWFyZ2luLXRvcDowaW4iIHR5cGU9ImRpc2MiPg0KPHVsIHN0eWxlPSJtYXJnaW4tdG9w
OjBpbiIgdHlwZT0iY2lyY2xlIj4NCjxsaSBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLWxp
c3Q6bDAgbGV2ZWwyIGxmbzIiPlNvbWUgb2YgdGhlIGNyeXB0byBzZWVtcyBvYnNvbGV0ZSAoZXhh
bXBsZTogREVTKS4gV2Ugd291bGQgZ2V0IGludG8gdHJvdWJsZSBpbiBTZWNEaXIgcmV2aWV3LiAm
bmJzcDtPVE9IIENoYUNoYTIwLVBvbHkxMzA1IGlzIG1pc3NpbmcuLjxvOnA+PC9vOnA+PC9saT48
L3VsPg0KPC91bD4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9ibG9ja3F1b3Rl
Pg0KPGRpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj4mbmJzcDs8bzpwPjwvbzpwPjwv
cD4NCjwvZGl2Pg0KPC9kaXY+DQo8ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPkFn
cmVlLiBXZSB3aWxsIHJlbW92ZSBERVMgYW5kIGFkZCB0aGUgYWxnb3JpdGhtIHlvdSBtZW50aW9u
LjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4N
CjwvYmxvY2txdW90ZT4NCjxkaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+Jm5ic3A7
PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPGRpdj4NCjxkaXY+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIj5UaGUgVExTIHdvcmtpbmcgZ3JvdXAgd2VudCBxdWl0ZSBmYXIgd2l0aCBUTFMg
MS4zLiAmbmJzcDtPbmx5IDIgY2lwaGVycyByZW1haW46IEFFUy1HQ00gd2l0aCAxNi1ieXRlIElD
ViwgYW5kIENoYUNoYTIwLVBvbHkxMzA1LiBUaGF04oCZcyBpdC4gJm5ic3A7U3BlY2lmaWNhbGx5
LCB0aGV54oCZdmUgZGVwcmVjYXRlZCBldmVyeXRoaW5nIHRoYXQgaXNu4oCZdCBhbiBBRUFELjxv
OnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjxkaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1z
b05vcm1hbCI+Jm5ic3A7PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPGRpdj4NCjxk
aXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5UaGUgSVBzZWNNRSB3b3JraW5nIGdyb3VwIGhhc27i
gJl0IGdvbmUgdGhhdCBmYXIgeWV0LiAmbmJzcDtCdXQgaW4gcHJhY3RpY2UgcHJldHR5IG11Y2gg
bm90aGluZyBpcyB1c2VkIGV4Y2VwdCAzREVTLCBBRVMtQ0JDLCBhbmQgQUVTLUdDTS4gJm5ic3A7
UGVyaGFwcyBDaGFDaGEyMC1Qb2x5MTMwNSBpcyBzdGFydGluZyB0byBzZWUgc29tZSB1c2UgYnkg
bm93LiBXZSBoYXZlIFJGQyA4MjIxLCBlc3BlY2lhbGx5IHNlY3Rpb25zIDUgYW5kDQogNi4gJm5i
c3A7SSB0aGluayAoYWx0aG91Z2ggaXTigJlzIHVwIHRvIHRoZSB3b3JraW5nIGdyb3VwKSB0aGF0
IHdlIHNob3VsZCBiZSBmaW5lIGRlZmluaW5nIG9ubHkgdGhlIE1VU1RzIGFuZCB0aGUgU0hPVUxE
cyBpbiB0aG9zZSBzZWN0aW9ucy48bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8ZGl2
Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPiZuYnNwOzxvOnA+PC9vOnA+PC9wPg0KPC9k
aXY+DQo8L2Rpdj4NCjxkaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+VGhhdCBicmlu
Z3MgYW5vdGhlciBxdWVzdGlvbi4gV2hhdCBpcyBvdXIgcGxhbiBmb3IgZnV0dXJlIGV4cGFuc2lv
bnM/ICZuYnNwO1N1cHBvc2UgdGhlcmXigJlzIHNvbWUgaG90LCBuZXcgYWxnb3JpdGhtIHRoYXQg
ZXZlcnlvbmUgaXMgaW1wbGVtZW50aW5nLiBIb3cgZG8geW91IHVwZGF0ZSB0aGUgWUFORyBtb2Rl
bCBpbiB0aGUgZnV0dXJlIHdoZW4geW91IGFkZCBuZXcgdmFsdWVzIHRvIHRoZSBlbnVtZXJhdGlv
bnM/ICZuYnNwO0lzDQogaXQgdXAgdG8gdGhlIGFkbWluaXN0cmF0b3IgdG8gbWFrZSBzdXJlIHRo
YXQgdGhlIGNvbnRyb2xsZXIgYW5kIE5TRnMgYXJlIGFsbCBvbiB0aGUg4oCcc2FtZSBwYWdl4oCd
PzxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjxkaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCI+Jm5ic3A7PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPGRpdj4N
CjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5UaGFua3M8bzpwPjwvbzpwPjwvcD4NCjwvZGl2
Pg0KPC9kaXY+DQo8ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPiZuYnNwOzxvOnA+
PC9vOnA+PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjxkaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCI+WW9hdjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjVwdDtmb250
LWZhbWlseTpDb3VyaWVyIj5fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fXzxicj4NCkkybnNmIG1haWxpbmcgbGlzdDxicj4NCjwvc3Bhbj48YSBocmVmPSJtYWls
dG86STJuc2ZAaWV0Zi5vcmciPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuNXB0O2ZvbnQtZmFt
aWx5OkNvdXJpZXI7Y29sb3I6cHVycGxlIj5JMm5zZkBpZXRmLm9yZzwvc3Bhbj48L2E+PHNwYW4g
c3R5bGU9ImZvbnQtc2l6ZToxMC41cHQ7Zm9udC1mYW1pbHk6Q291cmllciI+PGJyPg0KPC9zcGFu
PjxhIGhyZWY9Imh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vaTJuc2YiPjxz
cGFuIHN0eWxlPSJmb250LXNpemU6MTAuNXB0O2ZvbnQtZmFtaWx5OkNvdXJpZXI7Y29sb3I6cHVy
cGxlIj5odHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL2kybnNmPC9zcGFuPjwv
YT48bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPC9ibG9ja3F1b3RlPg0KPC9kaXY+DQo8cCBjbGFz
cz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Jv
ZHk+DQo8L2h0bWw+DQo=

--_000_4A95BA014132FF49AE685FAB4B9F17F66B1F6A75SJCEML521MBBchi_--


From nobody Mon Dec 10 06:42:04 2018
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 A7609129533 for <i2nsf@ietfa.amsl.com>; Mon, 10 Dec 2018 06:42:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.988
X-Spam-Level: 
X-Spam-Status: No, score=-1.988 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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 3eecQ5CWM9lB for <i2nsf@ietfa.amsl.com>; Mon, 10 Dec 2018 06:41:57 -0800 (PST)
Received: from mail-io1-xd2b.google.com (mail-io1-xd2b.google.com [IPv6:2607:f8b0:4864:20::d2b]) (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 F202E12896A for <i2nsf@ietf.org>; Mon, 10 Dec 2018 06:41:56 -0800 (PST)
Received: by mail-io1-xd2b.google.com with SMTP id r9so8939915ioa.1 for <i2nsf@ietf.org>; Mon, 10 Dec 2018 06:41:56 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:from:date:message-id:subject:to:cc; bh=N70apyqJ0BFdAsXQM7gHC2VbeiX5P0xcGWCanUWYQsI=; b=CSdHnQfHwvVr/aQRAT0qpsHvF2rw2NWyciLsU3nStAPQ0ofgLKTyBa1HdJK65IpHv5 RtNcN3EpAwnl6nUNiUUEkoEwR3eDqwLZorPEXPdL9rSYbB8O9V/AsaNacu603R1u35D9 jMzb2b6Zcb9cDzyNJPTse0HeaZLkIX2G0LJ1o8XAcE2bV68YhY+8h+N095CmjvXcgL1Y pdGbXRvGhaycI0O/rXqf52DxxdLmbVx8oMixR5hWsDvhyK1FJMwONP4XhwdsLBPnGYqz uQNGlUyDqjkdIEqXg8NHuIQny4CKmz8ilNk8foz6F8hgljRCjARzG+Zf68Yu6IRA0kIP oWoQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to:cc; bh=N70apyqJ0BFdAsXQM7gHC2VbeiX5P0xcGWCanUWYQsI=; b=AH87sOmThqmFlKfpjWCEINjuhfrRd3Bf8ynMfvaYy67Btpis6DNGGPIvTHTIdMxI5a AP8r4pFfBwurJzOy/j7sezJZzzuhqbYgJ4y9LwvGl6TKUWOzae/kMOaDuuMpD2pKreVn ZNGy5DjUS9BjHYq0dWMgz4PdKEPEJ7d2dJN6aMX7LYTkeuCUMO4E9qmA8ZjC7RMNSzJm KMrUwRi2tygCZobGLqItAx/r4Atn+Dxpp2lRhNw/WKyEugAK4tu4Su1q0TQGGGrr+ZZv J5gpJvkCxUD925LSQV3BAafseD6HVnKvwldZo9hXLNbG39IFnb0wnfMgary4DOYlo3ln 4I+A==
X-Gm-Message-State: AA+aEWYS7sBIsPjoA0sVYSQsaPQN233U9bzcDFFMVXshlpKRXsFPYqtC IfnIKY8OQsV6pei7oXD6vsvH9hkC6/8cCAi5BoY=
X-Google-Smtp-Source: AFSGD/WS8yfo6qqNOyOiuzS4FnPJXHbD44mYRoTokw8gD+Py0dZUM7Gxj5I3rIi+G4zfe1IUVZt+TTQ5uUcV4yjawjk=
X-Received: by 2002:a5e:d910:: with SMTP id n16mr10820227iop.58.1544452916221;  Mon, 10 Dec 2018 06:41:56 -0800 (PST)
MIME-Version: 1.0
From: "Mr. Jaehoon Paul Jeong" <jaehoon.paul@gmail.com>
Date: Mon, 10 Dec 2018 23:41:18 +0900
Message-ID: <CAPK2DewpwQGKwuSEW7ebQPmpG=13Z8WyAgVxn4s5bH=DB36d_Q@mail.gmail.com>
To: Linda Dunbar <linda.dunbar@huawei.com>, Yoav Nir <ynir.ietf@gmail.com>
Cc: "i2nsf@ietf.org" <i2nsf@ietf.org>, skku_secu-brain_all@googlegroups.com,  Sangwon Hyun <swhyun77@gmail.com>, "Mr. Jaehoon Paul Jeong" <jaehoon.paul@gmail.com>
Content-Type: multipart/alternative; boundary="000000000000719bea057cabf7d7"
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2nsf/HODOpv7eD2vE7_rmFqECDyfrli4>
Subject: [I2nsf] Request for Applicability I-D to IESG
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, 10 Dec 2018 14:42:04 -0000

--000000000000719bea057cabf7d7
Content-Type: text/plain; charset="UTF-8"

Hi Linda and Yoav,
A couple months have passed after the WGLC of our I2NSF Applicability
Document:
https://tools.ietf.org/html/draft-ietf-i2nsf-applicability-07

Could you finish your write-up and submit it to the IESG soon?

Thanks.

Best Regards,
Paul
-- 
===========================
Mr. Jaehoon (Paul) Jeong, Ph.D.
Associate Professor
Department of Software
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>

--000000000000719bea057cabf7d7
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>A couple months ha=
ve passed after the WGLC of our I2NSF Applicability Document:</div><div><a =
href=3D"https://tools.ietf.org/html/draft-ietf-i2nsf-applicability-07">http=
s://tools.ietf.org/html/draft-ietf-i2nsf-applicability-07</a></div><div><br=
></div><div>Could you finish your write-up and submit it to the IESG soon?<=
/div><div><br></div><div>Thanks.</div><div><br></div><div>Best Regards,</di=
v><div>Paul<br>-- <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>Departm=
ent of Software<br>Sungkyunkwan University<br>Office: +82-31-299-4957<br>Em=
ail: <a href=3D"mailto:jaehoon.paul@gmail.com" target=3D"_blank">jaehoon.pa=
ul@gmail.com</a>,=C2=A0<a href=3D"mailto:pauljeong@skku.edu" style=3D"font-=
size:12.8px" target=3D"_blank">pauljeong@skku.edu</a><br>Personal Homepage:=
 <a href=3D"http://cpslab.skku.edu/people-jaehoon-jeong.php" target=3D"_bla=
nk">http://iotlab.skku.edu/people-jaehoon-jeong.php</a><br></div></div></di=
v></div></div></div></div></div></div></div></div>

--000000000000719bea057cabf7d7--


From nobody Mon Dec 10 08:14:37 2018
Return-Path: <linda.dunbar@huawei.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 0ECF5130FF4 for <i2nsf@ietfa.amsl.com>; Mon, 10 Dec 2018 08:14:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-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 J_T-qYG3P06q for <i2nsf@ietfa.amsl.com>; Mon, 10 Dec 2018 08:14:34 -0800 (PST)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (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 32A1E130FE9 for <i2nsf@ietf.org>; Mon, 10 Dec 2018 08:14:34 -0800 (PST)
Received: from lhreml704-cah.china.huawei.com (unknown [172.18.7.108]) by Forcepoint Email with ESMTP id 5B63847E963E9 for <i2nsf@ietf.org>; Mon, 10 Dec 2018 16:14:29 +0000 (GMT)
Received: from SJCEML703-CHM.china.huawei.com (10.208.112.39) by lhreml704-cah.china.huawei.com (10.201.108.45) with Microsoft SMTP Server (TLS) id 14.3.408.0; Mon, 10 Dec 2018 16:14:30 +0000
Received: from SJCEML521-MBS.china.huawei.com ([169.254.2.185]) by SJCEML703-CHM.china.huawei.com ([169.254.5.67]) with mapi id 14.03.0415.000; Mon, 10 Dec 2018 08:14:25 -0800
From: Linda Dunbar <linda.dunbar@huawei.com>
To: "Mr. Jaehoon Paul Jeong" <jaehoon.paul@gmail.com>, Yoav Nir <ynir.ietf@gmail.com>
CC: "i2nsf@ietf.org" <i2nsf@ietf.org>, "skku_secu-brain_all@googlegroups.com" <skku_secu-brain_all@googlegroups.com>, Sangwon Hyun <swhyun77@gmail.com>
Thread-Topic: Request for Applicability I-D to IESG
Thread-Index: AQHUkJaKBQOsO8EB/keJqdLWRO/mLqV4JVRQ
Date: Mon, 10 Dec 2018 16:14:24 +0000
Message-ID: <4A95BA014132FF49AE685FAB4B9F17F66B204795@sjceml521-mbs.china.huawei.com>
References: <CAPK2DewpwQGKwuSEW7ebQPmpG=13Z8WyAgVxn4s5bH=DB36d_Q@mail.gmail.com>
In-Reply-To: <CAPK2DewpwQGKwuSEW7ebQPmpG=13Z8WyAgVxn4s5bH=DB36d_Q@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.192.11.103]
Content-Type: multipart/alternative; boundary="_000_4A95BA014132FF49AE685FAB4B9F17F66B204795sjceml521mbschi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2nsf/eSswXfZb-vzJEZnSatF8d8ecL8g>
Subject: Re: [I2nsf] Request for Applicability I-D to IESG
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, 10 Dec 2018 16:14:36 -0000

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

V2UgZmluaXNoZWQgdGhlIHNoZXBoZXJkIHdyaXRlLXVwICg0MCBkYXlzIGFnbyksIHdhaXRpbmcg
Zm9yIEFEIHRvIG1vdmUgaXQgZm9yd2FyZC4gRXJpYyBoYXMgYmVlbiBzbG93IChIZSBwcm9taXNl
ZCBhIHdlZWsgYWdvIHRvIGFjdCBvbiBpdCkNCg0KTGluZGENCg0KRnJvbTogTXIuIEphZWhvb24g
UGF1bCBKZW9uZyBbbWFpbHRvOmphZWhvb24ucGF1bEBnbWFpbC5jb21dDQpTZW50OiBNb25kYXks
IERlY2VtYmVyIDEwLCAyMDE4IDg6NDEgQU0NClRvOiBMaW5kYSBEdW5iYXIgPGxpbmRhLmR1bmJh
ckBodWF3ZWkuY29tPjsgWW9hdiBOaXIgPHluaXIuaWV0ZkBnbWFpbC5jb20+DQpDYzogaTJuc2ZA
aWV0Zi5vcmc7IHNra3Vfc2VjdS1icmFpbl9hbGxAZ29vZ2xlZ3JvdXBzLmNvbTsgU2FuZ3dvbiBI
eXVuIDxzd2h5dW43N0BnbWFpbC5jb20+OyBNci4gSmFlaG9vbiBQYXVsIEplb25nIDxqYWVob29u
LnBhdWxAZ21haWwuY29tPg0KU3ViamVjdDogUmVxdWVzdCBmb3IgQXBwbGljYWJpbGl0eSBJLUQg
dG8gSUVTRw0KDQpIaSBMaW5kYSBhbmQgWW9hdiwNCkEgY291cGxlIG1vbnRocyBoYXZlIHBhc3Nl
ZCBhZnRlciB0aGUgV0dMQyBvZiBvdXIgSTJOU0YgQXBwbGljYWJpbGl0eSBEb2N1bWVudDoNCmh0
dHBzOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9kcmFmdC1pZXRmLWkybnNmLWFwcGxpY2FiaWxpdHkt
MDcNCg0KQ291bGQgeW91IGZpbmlzaCB5b3VyIHdyaXRlLXVwIGFuZCBzdWJtaXQgaXQgdG8gdGhl
IElFU0cgc29vbj8NCg0KVGhhbmtzLg0KDQpCZXN0IFJlZ2FyZHMsDQpQYXVsDQotLQ0KPT09PT09
PT09PT09PT09PT09PT09PT09PT09DQpNci4gSmFlaG9vbiAoUGF1bCkgSmVvbmcsIFBoLkQuDQpB
c3NvY2lhdGUgUHJvZmVzc29yDQpEZXBhcnRtZW50IG9mIFNvZnR3YXJlDQpTdW5na3l1bmt3YW4g
VW5pdmVyc2l0eQ0KT2ZmaWNlOiArODItMzEtMjk5LTQ5NTcNCkVtYWlsOiBqYWVob29uLnBhdWxA
Z21haWwuY29tPG1haWx0bzpqYWVob29uLnBhdWxAZ21haWwuY29tPiwgcGF1bGplb25nQHNra3Uu
ZWR1PG1haWx0bzpwYXVsamVvbmdAc2trdS5lZHU+DQpQZXJzb25hbCBIb21lcGFnZTogaHR0cDov
L2lvdGxhYi5za2t1LmVkdS9wZW9wbGUtamFlaG9vbi1qZW9uZy5waHA8aHR0cDovL2Nwc2xhYi5z
a2t1LmVkdS9wZW9wbGUtamFlaG9vbi1qZW9uZy5waHA+DQo=

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

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTUgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
U2ltU3VuOw0KCXBhbm9zZS0xOjIgMSA2IDAgMyAxIDEgMSAxIDE7fQ0KQGZvbnQtZmFjZQ0KCXtm
b250LWZhbWlseToiQ2FtYnJpYSBNYXRoIjsNCglwYW5vc2UtMToyIDQgNSAzIDUgNCA2IDMgMiA0
O30NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6Q2FsaWJyaTsNCglwYW5vc2UtMToyIDE1IDUg
MiAyIDIgNCAzIDIgNDt9DQpAZm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5OiJcQFNpbVN1biI7DQoJ
cGFub3NlLTE6MiAxIDYgMCAzIDEgMSAxIDEgMTt9DQovKiBTdHlsZSBEZWZpbml0aW9ucyAqLw0K
cC5Nc29Ob3JtYWwsIGxpLk1zb05vcm1hbCwgZGl2Lk1zb05vcm1hbA0KCXttYXJnaW46MGluOw0K
CW1hcmdpbi1ib3R0b206LjAwMDFwdDsNCglmb250LXNpemU6MTIuMHB0Ow0KCWZvbnQtZmFtaWx5
OiJUaW1lcyBOZXcgUm9tYW4iLHNlcmlmO30NCmE6bGluaywgc3Bhbi5Nc29IeXBlcmxpbmsNCgl7
bXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0KCWNvbG9yOmJsdWU7DQoJdGV4dC1kZWNvcmF0aW9uOnVu
ZGVybGluZTt9DQphOnZpc2l0ZWQsIHNwYW4uTXNvSHlwZXJsaW5rRm9sbG93ZWQNCgl7bXNvLXN0
eWxlLXByaW9yaXR5Ojk5Ow0KCWNvbG9yOnB1cnBsZTsNCgl0ZXh0LWRlY29yYXRpb246dW5kZXJs
aW5lO30NCnNwYW4uRW1haWxTdHlsZTE3DQoJe21zby1zdHlsZS10eXBlOnBlcnNvbmFsLXJlcGx5
Ow0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIixzYW5zLXNlcmlmOw0KCWNvbG9yOiMxRjQ5N0Q7fQ0K
Lk1zb0NocERlZmF1bHQNCgl7bXNvLXN0eWxlLXR5cGU6ZXhwb3J0LW9ubHk7DQoJZm9udC1mYW1p
bHk6IkNhbGlicmkiLHNhbnMtc2VyaWY7fQ0KQHBhZ2UgV29yZFNlY3Rpb24xDQoJe3NpemU6OC41
aW4gMTEuMGluOw0KCW1hcmdpbjoxLjBpbiAxLjBpbiAxLjBpbiAxLjBpbjt9DQpkaXYuV29yZFNl
Y3Rpb24xDQoJe3BhZ2U6V29yZFNlY3Rpb24xO30NCi0tPjwvc3R5bGU+PCEtLVtpZiBndGUgbXNv
IDldPjx4bWw+DQo8bzpzaGFwZWRlZmF1bHRzIHY6ZXh0PSJlZGl0IiBzcGlkbWF4PSIxMDI2IiAv
Pg0KPC94bWw+PCFbZW5kaWZdLS0+PCEtLVtpZiBndGUgbXNvIDldPjx4bWw+DQo8bzpzaGFwZWxh
eW91dCB2OmV4dD0iZWRpdCI+DQo8bzppZG1hcCB2OmV4dD0iZWRpdCIgZGF0YT0iMSIgLz4NCjwv
bzpzaGFwZWxheW91dD48L3htbD48IVtlbmRpZl0tLT4NCjwvaGVhZD4NCjxib2R5IGxhbmc9IkVO
LVVTIiBsaW5rPSJibHVlIiB2bGluaz0icHVycGxlIj4NCjxkaXYgY2xhc3M9IldvcmRTZWN0aW9u
MSI+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtm
b250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6IzFGNDk3RCI+
V2UgZmluaXNoZWQgdGhlIHNoZXBoZXJkIHdyaXRlLXVwICg0MCBkYXlzIGFnbyksIHdhaXRpbmcg
Zm9yIEFEIHRvIG1vdmUgaXQgZm9yd2FyZC4gRXJpYyBoYXMgYmVlbiBzbG93IChIZSBwcm9taXNl
ZCBhIHdlZWsgYWdvIHRvIGFjdCBvbiBpdCk8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFz
cz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTom
cXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6IzFGNDk3RCI+PG86cD4mbmJzcDs8
L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQt
c2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmO2Nv
bG9yOiMxRjQ5N0QiPkxpbmRhPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCI+PGEgbmFtZT0iX01haWxFbmRDb21wb3NlIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEx
LjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6IzFG
NDk3RCI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9hPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3Jt
YWwiPjxiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0Nh
bGlicmkmcXVvdDssc2Fucy1zZXJpZiI+RnJvbTo8L3NwYW4+PC9iPjxzcGFuIHN0eWxlPSJmb250
LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZiI+
IE1yLiBKYWVob29uIFBhdWwgSmVvbmcgW21haWx0bzpqYWVob29uLnBhdWxAZ21haWwuY29tXQ0K
PGJyPg0KPGI+U2VudDo8L2I+IE1vbmRheSwgRGVjZW1iZXIgMTAsIDIwMTggODo0MSBBTTxicj4N
CjxiPlRvOjwvYj4gTGluZGEgRHVuYmFyICZsdDtsaW5kYS5kdW5iYXJAaHVhd2VpLmNvbSZndDs7
IFlvYXYgTmlyICZsdDt5bmlyLmlldGZAZ21haWwuY29tJmd0Ozxicj4NCjxiPkNjOjwvYj4gaTJu
c2ZAaWV0Zi5vcmc7IHNra3Vfc2VjdS1icmFpbl9hbGxAZ29vZ2xlZ3JvdXBzLmNvbTsgU2FuZ3dv
biBIeXVuICZsdDtzd2h5dW43N0BnbWFpbC5jb20mZ3Q7OyBNci4gSmFlaG9vbiBQYXVsIEplb25n
ICZsdDtqYWVob29uLnBhdWxAZ21haWwuY29tJmd0Ozxicj4NCjxiPlN1YmplY3Q6PC9iPiBSZXF1
ZXN0IGZvciBBcHBsaWNhYmlsaXR5IEktRCB0byBJRVNHPG86cD48L286cD48L3NwYW4+PC9wPg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8ZGl2Pg0KPGRpdj4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiPkhpIExpbmRhIGFuZCBZb2F2LDxvOnA+PC9vOnA+PC9wPg0K
PGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPkEgY291cGxlIG1vbnRocyBoYXZlIHBhc3NlZCBh
ZnRlciB0aGUgV0dMQyBvZiBvdXIgSTJOU0YgQXBwbGljYWJpbGl0eSBEb2N1bWVudDo8bzpwPjwv
bzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxhIGhyZWY9Imh0
dHBzOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9kcmFmdC1pZXRmLWkybnNmLWFwcGxpY2FiaWxpdHkt
MDciPmh0dHBzOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9kcmFmdC1pZXRmLWkybnNmLWFwcGxpY2Fi
aWxpdHktMDc8L2E+PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiPkNvdWxkIHlvdSBmaW5pc2ggeW91ciB3cml0ZS11cCBhbmQgc3VibWl0IGl0IHRv
IHRoZSBJRVNHIHNvb24/PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiPlRoYW5rcy48bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCI+QmVzdCBSZWdhcmRzLDxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8
ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+UGF1bDxicj4NCi0tIDxvOnA+PC9vOnA+PC9wPg0K
PGRpdj4NCjxkaXY+DQo8ZGl2Pg0KPGRpdj4NCjxkaXY+DQo8ZGl2Pg0KPGRpdj4NCjxkaXY+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIj49PT09PT09PT09PT09PT09PT09PT09PT09PT08YnI+DQpNci4g
SmFlaG9vbiAoUGF1bCkgSmVvbmcsIFBoLkQuPGJyPg0KQXNzb2NpYXRlIFByb2Zlc3Nvcjxicj4N
CkRlcGFydG1lbnQgb2YgU29mdHdhcmU8YnI+DQpTdW5na3l1bmt3YW4gVW5pdmVyc2l0eTxicj4N
Ck9mZmljZTogJiM0Mzs4Mi0zMS0yOTktNDk1Nzxicj4NCkVtYWlsOiA8YSBocmVmPSJtYWlsdG86
amFlaG9vbi5wYXVsQGdtYWlsLmNvbSIgdGFyZ2V0PSJfYmxhbmsiPmphZWhvb24ucGF1bEBnbWFp
bC5jb208L2E+LCZuYnNwOzxhIGhyZWY9Im1haWx0bzpwYXVsamVvbmdAc2trdS5lZHUiIHRhcmdl
dD0iX2JsYW5rIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjkuNXB0Ij5wYXVsamVvbmdAc2trdS5l
ZHU8L3NwYW4+PC9hPjxicj4NClBlcnNvbmFsIEhvbWVwYWdlOiA8YSBocmVmPSJodHRwOi8vY3Bz
bGFiLnNra3UuZWR1L3Blb3BsZS1qYWVob29uLWplb25nLnBocCIgdGFyZ2V0PSJfYmxhbmsiPg0K
aHR0cDovL2lvdGxhYi5za2t1LmVkdS9wZW9wbGUtamFlaG9vbi1qZW9uZy5waHA8L2E+PG86cD48
L286cD48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+
DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2JvZHk+
DQo8L2h0bWw+DQo=

--_000_4A95BA014132FF49AE685FAB4B9F17F66B204795sjceml521mbschi_--


From nobody Mon Dec 10 15:37:03 2018
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 78A3E129C6A for <i2nsf@ietfa.amsl.com>; Mon, 10 Dec 2018 15:37:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.988
X-Spam-Level: 
X-Spam-Status: No, score=-1.988 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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 58Wg0aUYvjSX for <i2nsf@ietfa.amsl.com>; Mon, 10 Dec 2018 15:36:59 -0800 (PST)
Received: from mail-io1-xd35.google.com (mail-io1-xd35.google.com [IPv6:2607:f8b0:4864:20::d35]) (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 DD6A2129A87 for <i2nsf@ietf.org>; Mon, 10 Dec 2018 15:36:58 -0800 (PST)
Received: by mail-io1-xd35.google.com with SMTP id v10so10261935ios.13 for <i2nsf@ietf.org>; Mon, 10 Dec 2018 15:36:58 -0800 (PST)
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=wpfrc+Yyr6baNIWFVaDGRqfOK+gNgL4bCbeOA9PAT6g=; b=EEDMb4WQYIGGm8qm2i42z0VwosO5Xuxm2s1XH964P2v3EWZEyswj9yJz7pBYj3tjE0 zepoAH78lchIvtl+SMm9o+2fUt/+Lofr8/s3Mf7MflF3MrDVhdbzu24FynpozF2vR/Gv plNG/khWJFxFCAODay79q83qUj4onLxbiPG95H0HGdHciJmGb933bfpOZRkKOxhP+8W4 vGo/78P0TanjqkpQAr45o/FHy2M4e0wzSBillrP52e0ZTSK5WBrXzdI0+5d/RI5TtsF/ gJwUB1vLR86X5JJnYxsAcQF9j3Z5G+Q15p52b3Sx6bDjsaiEVNSmaJzz9LLOVI1jgbuX ApbQ==
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=wpfrc+Yyr6baNIWFVaDGRqfOK+gNgL4bCbeOA9PAT6g=; b=CZcdOnTJCGT/kHS41ObZYd5AXxihCuHwE7fB6c09ZgdQMdZVh3SdxwUimgBJOPunmv BuEulTtnieG0F3LQfw39pO2jCK5piZJH9Ljpx11JRiAyttY+bR9exeOGzSQOWxFOFqNY RCFvl1npFPJ27XDm1YdjwskhlP5ncLamWtDEPrrsVscjyeWPkUtcBODswaYCRLCSTIpy yn4CnQw//TwZvJLNFTM49tkkGtAzc3H8Gy1D4rgolZfx7jWCMvIJ1yXiaN/7HDiAFDp2 +oXcsax72+vxnG573zdizf7DghPwBBxL7m1q88aE7btCKI6eVElBf02Tv49Y4VqvY/fa aERw==
X-Gm-Message-State: AA+aEWa7Fq1eEkcvj7V0FoccCZxKWA9H95MGhNstu0NEpzlUWymp4Hrc mENnmfZFYmjWs7WfU8V4FGVNJQPy1idu2JoOj0E=
X-Google-Smtp-Source: AFSGD/WeS6s2tM3xuDitGsYc3O9OsiFOeewVRvMndX6MmLM+D7JmbWJK1MLRQ8zcbNLLQI2AQh5+bjcqfDpESOPuyyE=
X-Received: by 2002:a5e:d910:: with SMTP id n16mr12512596iop.58.1544485018061;  Mon, 10 Dec 2018 15:36:58 -0800 (PST)
MIME-Version: 1.0
References: <CAPK2DewpwQGKwuSEW7ebQPmpG=13Z8WyAgVxn4s5bH=DB36d_Q@mail.gmail.com> <4A95BA014132FF49AE685FAB4B9F17F66B204795@sjceml521-mbs.china.huawei.com>
In-Reply-To: <4A95BA014132FF49AE685FAB4B9F17F66B204795@sjceml521-mbs.china.huawei.com>
From: "Mr. Jaehoon Paul Jeong" <jaehoon.paul@gmail.com>
Date: Tue, 11 Dec 2018 08:36:44 +0900
Message-ID: <CAPK2DeyYRWKM02FLieX0ADQbXgNUfyibta6JCHEhNNPzOBHU1g@mail.gmail.com>
To: Linda Dunbar <linda.dunbar@huawei.com>
Cc: Yoav Nir <ynir.ietf@gmail.com>, i2nsf@ietf.org, Sangwon Hyun <swhyun77@gmail.com>,  "skku_secu-brain_all@googlegroups.com" <skku_secu-brain_all@googlegroups.com>
Content-Type: multipart/alternative; boundary="000000000000dcd4bf057cb37057"
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2nsf/ZbjrF6OFOhTJdgDtOiMbXK1rwuM>
Subject: Re: [I2nsf] Request for Applicability I-D to IESG
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, 10 Dec 2018 23:37:02 -0000

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

Linda,
I see.

Thanks for your guidance and help.

Best Regards,
Paul

2018=EB=85=84 12=EC=9B=94 11=EC=9D=BC (=ED=99=94) =EC=98=A4=EC=A0=84 1:14=
=EC=97=90 Linda Dunbar <linda.dunbar@huawei.com>=EB=8B=98=EC=9D=B4 =EC=9E=
=91=EC=84=B1:

> We finished the shepherd write-up (40 days ago), waiting for AD to move i=
t
> forward. Eric has been slow (He promised a week ago to act on it)
>
>
>
> Linda
>
>
>
> *From:* Mr. Jaehoon Paul Jeong [mailto:jaehoon.paul@gmail.com]
> *Sent:* Monday, December 10, 2018 8:41 AM
> *To:* Linda Dunbar <linda.dunbar@huawei.com>; Yoav Nir <
> ynir.ietf@gmail.com>
> *Cc:* i2nsf@ietf.org; skku_secu-brain_all@googlegroups.com; Sangwon Hyun =
<
> swhyun77@gmail.com>; Mr. Jaehoon Paul Jeong <jaehoon.paul@gmail.com>
> *Subject:* Request for Applicability I-D to IESG
>
>
>
> Hi Linda and Yoav,
>
> A couple months have passed after the WGLC of our I2NSF Applicability
> Document:
>
> https://tools.ietf.org/html/draft-ietf-i2nsf-applicability-07
>
>
>
> Could you finish your write-up and submit it to the IESG soon?
>
>
>
> Thanks.
>
>
>
> Best Regards,
>
> Paul
> --
>
> =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 Software
> 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>
> _______________________________________________
> I2nsf mailing list
> I2nsf@ietf.org
> https://www.ietf.org/mailman/listinfo/i2nsf
>

--000000000000dcd4bf057cb37057
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">Thanks for your guidance and help.</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">2018=EB=85=
=84 12=EC=9B=94 11=EC=9D=BC (=ED=99=94) =EC=98=A4=EC=A0=84 1:14=EC=97=90 Li=
nda Dunbar &lt;<a href=3D"mailto:linda.dunbar@huawei.com">linda.dunbar@huaw=
ei.com</a>&gt;=EB=8B=98=EC=9D=B4 =EC=9E=91=EC=84=B1:<br></div><blockquote c=
lass=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_126440928430756362WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#1f497d">We finished the shepherd write-up (40=
 days ago), waiting for AD to move it forward. Eric has been slow (He promi=
sed a week ago to act on it)<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#1f497d"><u></u>=C2=A0<u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#1f497d">Linda<u></u><u></u></span></p>
<p class=3D"MsoNormal"><a name=3D"m_126440928430756362__MailEndCompose" rel=
=3D"noreferrer"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&q=
uot;,sans-serif;color:#1f497d"><u></u>=C2=A0<u></u></span></a></p>
<p class=3D"MsoNormal"><b><span style=3D"font-size:11.0pt;font-family:&quot=
;Calibri&quot;,sans-serif">From:</span></b><span style=3D"font-size:11.0pt;=
font-family:&quot;Calibri&quot;,sans-serif"> Mr. Jaehoon Paul Jeong [mailto=
:<a href=3D"mailto:jaehoon.paul@gmail.com" target=3D"_blank" rel=3D"norefer=
rer">jaehoon.paul@gmail.com</a>]
<br>
<b>Sent:</b> Monday, December 10, 2018 8:41 AM<br>
<b>To:</b> Linda Dunbar &lt;<a href=3D"mailto:linda.dunbar@huawei.com" targ=
et=3D"_blank" rel=3D"noreferrer">linda.dunbar@huawei.com</a>&gt;; Yoav Nir =
&lt;<a href=3D"mailto:ynir.ietf@gmail.com" target=3D"_blank" rel=3D"norefer=
rer">ynir.ietf@gmail.com</a>&gt;<br>
<b>Cc:</b> <a href=3D"mailto:i2nsf@ietf.org" target=3D"_blank" rel=3D"noref=
errer">i2nsf@ietf.org</a>; <a href=3D"mailto:skku_secu-brain_all@googlegrou=
ps.com" target=3D"_blank" rel=3D"noreferrer">skku_secu-brain_all@googlegrou=
ps.com</a>; Sangwon Hyun &lt;<a href=3D"mailto:swhyun77@gmail.com" target=
=3D"_blank" rel=3D"noreferrer">swhyun77@gmail.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>Subject:</b> Request for Applicability I-D to IESG<u></u><u></u></span><=
/p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<div>
<div>
<p class=3D"MsoNormal">Hi Linda and Yoav,<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">A couple months have passed after the WGLC of our I2=
NSF Applicability Document:<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><a href=3D"https://tools.ietf.org/html/draft-ietf-i2=
nsf-applicability-07" target=3D"_blank" rel=3D"noreferrer">https://tools.ie=
tf.org/html/draft-ietf-i2nsf-applicability-07</a><u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Could you finish your write-up and submit it to the =
IESG soon?<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Thanks.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Best Regards,<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Paul<br>
-- <u></u><u></u></p>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<p class=3D"MsoNormal">=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 Software<br>
Sungkyunkwan University<br>
Office: +82-31-299-4957<br>
Email: <a href=3D"mailto:jaehoon.paul@gmail.com" target=3D"_blank" rel=3D"n=
oreferrer">jaehoon.paul@gmail.com</a>,=C2=A0<a href=3D"mailto:pauljeong@skk=
u.edu" target=3D"_blank" rel=3D"noreferrer"><span style=3D"font-size:9.5pt"=
>pauljeong@skku.edu</span></a><br>
Personal Homepage: <a href=3D"http://cpslab.skku.edu/people-jaehoon-jeong.p=
hp" target=3D"_blank" rel=3D"noreferrer">
http://iotlab.skku.edu/people-jaehoon-jeong.php</a><u></u><u></u></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</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>

--000000000000dcd4bf057cb37057--


From nobody Mon Dec 10 19:24:39 2018
Return-Path: <frank.xialiang@huawei.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 73B1F12426A for <i2nsf@ietfa.amsl.com>; Mon, 10 Dec 2018 19:24:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-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 tjMidr0Y4CP0 for <i2nsf@ietfa.amsl.com>; Mon, 10 Dec 2018 19:24:36 -0800 (PST)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (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 94E8B124BAA for <i2nsf@ietf.org>; Mon, 10 Dec 2018 19:24:35 -0800 (PST)
Received: from LHREML710-CAH.china.huawei.com (unknown [172.18.7.106]) by Forcepoint Email with ESMTP id 69C735B91229B for <i2nsf@ietf.org>; Tue, 11 Dec 2018 03:24:31 +0000 (GMT)
Received: from lhreml705-chm.china.huawei.com (10.201.108.54) by LHREML710-CAH.china.huawei.com (10.201.108.33) with Microsoft SMTP Server (TLS) id 14.3.408.0; Tue, 11 Dec 2018 03:24:32 +0000
Received: from lhreml705-chm.china.huawei.com (10.201.108.54) by lhreml705-chm.china.huawei.com (10.201.108.54) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1591.10; Tue, 11 Dec 2018 03:24:32 +0000
Received: from DGGEMM422-HUB.china.huawei.com (10.1.198.39) by lhreml705-chm.china.huawei.com (10.201.108.54) with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA_P256) id 15.1.1591.10 via Frontend Transport; Tue, 11 Dec 2018 03:24:32 +0000
Received: from DGGEMM531-MBS.china.huawei.com ([169.254.6.27]) by dggemm422-hub.china.huawei.com ([10.1.198.39]) with mapi id 14.03.0415.000; Tue, 11 Dec 2018 11:24:23 +0800
From: "Xialiang (Frank, Network Integration Technology Research Dept)" <frank.xialiang@huawei.com>
To: Linda Dunbar <linda.dunbar@huawei.com>
CC: "i2nsf@ietf.org" <i2nsf@ietf.org>
Thread-Topic: Call for WG Adoption on NSF Monitoring Draft
Thread-Index: AdSM6WC8tNKqbgUPR0unKhFeH73oNwEF4/zQ
Date: Tue, 11 Dec 2018 03:24:23 +0000
Message-ID: <C02846B1344F344EB4FAA6FA7AF481F12C945504@DGGEMM531-MBS.china.huawei.com>
References: <4A95BA014132FF49AE685FAB4B9F17F66B1F6399@SJCEML521-MBB.china.huawei.com>
In-Reply-To: <4A95BA014132FF49AE685FAB4B9F17F66B1F6399@SJCEML521-MBB.china.huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.134.159.76]
Content-Type: multipart/alternative; boundary="_000_C02846B1344F344EB4FAA6FA7AF481F12C945504DGGEMM531MBSchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2nsf/o1APAE-EeE8NtQJ4OdmA7bNPsoc>
Subject: [I2nsf] =?utf-8?b?562U5aSNOiBDYWxsIGZvciBXRyBBZG9wdGlvbiBvbiBO?= =?utf-8?q?SF_Monitoring_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: Tue, 11 Dec 2018 03:24:38 -0000

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

SGkgTGluZGEsDQpJIHN1cHBvcnQgYWRvcHRpb24gb2YgdGhpcyBkcmFmdCAoYXMgY28tYXV0aG9y
KS4gIEkgZG8gbm90IGtub3cgb2YgYW55IElQUiByZWxhdGVkIHRvIHRoaXMgZHJhZnQuDQoNClRo
YW5rcyENCg0KQi5SLg0KRnJhbmsNCg0K5Y+R5Lu25Lq6OiBJMm5zZiBbbWFpbHRvOmkybnNmLWJv
dW5jZXNAaWV0Zi5vcmddIOS7o+ihqCBMaW5kYSBEdW5iYXINCuWPkemAgeaXtumXtDogMjAxOOW5
tDEy5pyINuaXpSA2OjMyDQrmlLbku7bkuro6IGkybnNmQGlldGYub3JnDQrkuLvpopg6IFtJMm5z
Zl0gQ2FsbCBmb3IgV0cgQWRvcHRpb24gb24gTlNGIE1vbml0b3JpbmcgRHJhZnQNCg0KVGhpcyBp
cyB0aGUgc3RhcnQgb2YgYSB0d28gd2Vla3MgY2FsbCBmb3IgaW5wdXQgb24gdGhlIFdHIGFkb3B0
aW9uIG9mIHRoZSBkb2N1bWVudDogaHR0cHM6Ly90b29scy5pZXRmLm9yZy9odG1sL2RyYWZ0LWhv
bmctaTJuc2YtbnNmLW1vbml0b3JpbmctZGF0YS1tb2RlbC0wNg0KDQpUaGFua3MgZm9yIHRoZSBh
dXRob3JzIG9mIHRoZSB0d28gSTJOU0YgTW9uaXRvcmluZyBkcmFmdHMgdGFraW5nIGFjdGlvbnMg
b2YgbWVyZ2luZyB0aGUgY29udGVudC4NCldlIG5lZWQgbW9yZSBvZiB0aG9zZSBhY3Rpb25zLiBB
cyBvZiBub3cgd2UgaGF2ZSA4IFdHIGRyYWZ0cy4gV2UgbmVlZCB0byBmaW5pc2ggdGhlbSBuZXh0
IGZldyBtb250aHMuDQoNCkJlYXIgaW4gbWluZCB0aGF0IFdHIGFkb3B0aW9uIGRvZXNu4oCZdCBt
ZWFuIHRoZSBkcmFmdCBpcyByZWFkeSwgb25seSBtZWFucyB0aGF0IFdHIHdpbGwgd29yayB0b2dl
dGhlciBvbiB0aGUgZHJhZnQgKGluc3RlYWQgb2YgaW5kaXZpZHVhbHMpLg0KDQpQbGVhc2UgcHJv
dmlkZSBmZWVkYmFjayB0byB0aGUgbGlzdC9jaGFpcnMgaWYgeW91IGJlbGlldmUgdGhhdCB0aGlz
IGRvY3VtZW50IHNob3VsZCBiZSBhZG9wdGVkIGFzIGEgV0cgZG9jdW1lbnQuDQoNClRoYW5rcywN
Cg0KTGluZGEgJiBZb2F2DQoNCg0KRnJvbTogTXIuIEphZWhvb24gUGF1bCBKZW9uZyBbbWFpbHRv
OmphZWhvb24ucGF1bEBnbWFpbC5jb21dDQpTZW50OiBUaHVyc2RheSwgTm92ZW1iZXIgMTUsIDIw
MTggNjozNSBQTQ0KVG86IExpbmRhIER1bmJhciA8bGluZGEuZHVuYmFyQGh1YXdlaS5jb208bWFp
bHRvOmxpbmRhLmR1bmJhckBodWF3ZWkuY29tPj47IFlvYXYgTmlyIDx5bmlyLmlldGZAZ21haWwu
Y29tPG1haWx0bzp5bmlyLmlldGZAZ21haWwuY29tPj4NCkNjOiBpMm5zZkBpZXRmLm9yZzxtYWls
dG86aTJuc2ZAaWV0Zi5vcmc+OyBza2t1X3NlY3UtYnJhaW5fYWxsQGdvb2dsZWdyb3Vwcy5jb208
bWFpbHRvOnNra3Vfc2VjdS1icmFpbl9hbGxAZ29vZ2xlZ3JvdXBzLmNvbT47IFNhbmd3b24gSHl1
biA8c3doeXVuNzdAZ21haWwuY29tPG1haWx0bzpzd2h5dW43N0BnbWFpbC5jb20+PjsgTXIuIEph
ZWhvb24gUGF1bCBKZW9uZyA8amFlaG9vbi5wYXVsQGdtYWlsLmNvbTxtYWlsdG86amFlaG9vbi5w
YXVsQGdtYWlsLmNvbT4+DQpTdWJqZWN0OiBSZXF1ZXN0IGZvciBXRyBBZG9wdGlvbiBDYWxsIG9u
IE5TRiBNb25pdG9yaW5nIERyYWZ0DQoNCkhpIExpbmRhIGFuZCBZb2F2LA0KQXMgd2UgZGlzY3Vz
c2VkIHRoZSBsYXN0IEJhbmdrb2sgbWVldGluZywNCkkgaGF2ZSBtZXJnZWQgdGhlIHR3byBkcmFm
dHMgb2YgSW5mb3JtYXRpb24gTW9kZWwgYW5kIERhdGEgTW9kZWwNCmZvciBOU0YgTW9uaXRvcmlu
ZyBpbnRvIGEgbmV3IGRyYWZ0IGNhbGxlZCBkcmFmdC1ob25nLWkybnNmLW5zZi1tb25pdG9yaW5n
LWRhdGEtbW9kZWwtMDY6DQoNCi0gVHdvIEluZm9ybWF0aW9uIGFuZCBEYXRhIE1vZGVsIERyYWZ0
cw0KIC4gZHJhZnQtemhhbmctaTJuc2YtaW5mby1tb2RlbC1tb25pdG9yaW5nLTA3DQogLiBkcmFm
dC1ob25nLWkybnNmLW5zZi1tb25pdG9yaW5nLWRhdGEtbW9kZWwtMDUNCg0KLSBBIE1lcmdlZCBE
YXRhIE1vZGVsIERyYWZ0DQogLiBkcmFmdC1ob25nLWkybnNmLW5zZi1tb25pdG9yaW5nLWRhdGEt
bW9kZWwtMDYNCiAuIGh0dHBzOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9kcmFmdC1ob25nLWkybnNm
LW5zZi1tb25pdG9yaW5nLWRhdGEtbW9kZWwtMDYNCg0KVGhlIE5TRiBtb25pdG9yaW5nIGlzIHZl
cnkgaW1wb3J0YW50IHRvIG1hbmFnZSB0aGUgSTJOU0Ygc2VjdXJpdHkgc2VydmljZSBzeXN0ZW0N
CmluIGEgcmVsaWFibGUgYW5kIHNjYWxhYmxlIGZhc2hpb24uDQoNCkNvdWxkIHlvdSBzdGFydCBh
IFdHIGFkb3B0aW9uIGNhbGwgZm9yIHRoaXMgZHJhZnQ/DQoNClRoYW5rcy4NCg0KQmVzdCBSZWdh
cmRzLA0KUGF1bA0KLS0NCj09PT09PT09PT09PT09PT09PT09PT09PT09PQ0KTXIuIEphZWhvb24g
KFBhdWwpIEplb25nLCBQaC5ELg0KQXNzb2NpYXRlIFByb2Zlc3Nvcg0KRGVwYXJ0bWVudCBvZiBT
b2Z0d2FyZQ0KU3VuZ2t5dW5rd2FuIFVuaXZlcnNpdHkNCk9mZmljZTogKzgyLTMxLTI5OS00OTU3
DQpFbWFpbDogamFlaG9vbi5wYXVsQGdtYWlsLmNvbTxtYWlsdG86amFlaG9vbi5wYXVsQGdtYWls
LmNvbT4sIHBhdWxqZW9uZ0Bza2t1LmVkdTxtYWlsdG86cGF1bGplb25nQHNra3UuZWR1Pg0KUGVy
c29uYWwgSG9tZXBhZ2U6IGh0dHA6Ly9pb3RsYWIuc2trdS5lZHUvcGVvcGxlLWphZWhvb24tamVv
bmcucGhwPGh0dHA6Ly9jcHNsYWIuc2trdS5lZHUvcGVvcGxlLWphZWhvb24tamVvbmcucGhwPg0K

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

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTUgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
5a6L5L2TOw0KCXBhbm9zZS0xOjIgMSA2IDAgMyAxIDEgMSAxIDE7fQ0KQGZvbnQtZmFjZQ0KCXtm
b250LWZhbWlseToiQ2FtYnJpYSBNYXRoIjsNCglwYW5vc2UtMToyIDQgNSAzIDUgNCA2IDMgMiA0
O30NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6Q2FsaWJyaTsNCglwYW5vc2UtMToyIDE1IDUg
MiAyIDIgNCAzIDIgNDt9DQpAZm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5OuW+rui9r+mbhem7kTsN
CglwYW5vc2UtMToyIDExIDUgMyAyIDIgNCAyIDIgNDt9DQpAZm9udC1mYWNlDQoJe2ZvbnQtZmFt
aWx5OiJcQOW+rui9r+mbhem7kSI7DQoJcGFub3NlLTE6MiAxMSA1IDMgMiAyIDQgMiAyIDQ7fQ0K
QGZvbnQtZmFjZQ0KCXtmb250LWZhbWlseToiXEDlrovkvZMiOw0KCXBhbm9zZS0xOjIgMSA2IDAg
MyAxIDEgMSAxIDE7fQ0KLyogU3R5bGUgRGVmaW5pdGlvbnMgKi8NCnAuTXNvTm9ybWFsLCBsaS5N
c29Ob3JtYWwsIGRpdi5Nc29Ob3JtYWwNCgl7bWFyZ2luOjBjbTsNCgltYXJnaW4tYm90dG9tOi4w
MDAxcHQ7DQoJZm9udC1zaXplOjEyLjBwdDsNCglmb250LWZhbWlseToiVGltZXMgTmV3IFJvbWFu
IixzZXJpZjt9DQphOmxpbmssIHNwYW4uTXNvSHlwZXJsaW5rDQoJe21zby1zdHlsZS1wcmlvcml0
eTo5OTsNCgljb2xvcjpibHVlOw0KCXRleHQtZGVjb3JhdGlvbjp1bmRlcmxpbmU7fQ0KYTp2aXNp
dGVkLCBzcGFuLk1zb0h5cGVybGlua0ZvbGxvd2VkDQoJe21zby1zdHlsZS1wcmlvcml0eTo5OTsN
Cgljb2xvcjpwdXJwbGU7DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVybGluZTt9DQpzcGFuLkVtYWls
U3R5bGUxNw0KCXttc28tc3R5bGUtdHlwZTpwZXJzb25hbDsNCglmb250LWZhbWlseToiQ2FsaWJy
aSIsc2Fucy1zZXJpZjsNCgljb2xvcjojMUY0OTdEO30NCnNwYW4uRW1haWxTdHlsZTE4DQoJe21z
by1zdHlsZS10eXBlOnBlcnNvbmFsLXJlcGx5Ow0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIixzYW5z
LXNlcmlmOw0KCWNvbG9yOiMxRjQ5N0Q7fQ0KLk1zb0NocERlZmF1bHQNCgl7bXNvLXN0eWxlLXR5
cGU6ZXhwb3J0LW9ubHk7DQoJZm9udC1zaXplOjEwLjBwdDt9DQpAcGFnZSBXb3JkU2VjdGlvbjEN
Cgl7c2l6ZTo2MTIuMHB0IDc5Mi4wcHQ7DQoJbWFyZ2luOjcyLjBwdCA3Mi4wcHQgNzIuMHB0IDcy
LjBwdDt9DQpkaXYuV29yZFNlY3Rpb24xDQoJe3BhZ2U6V29yZFNlY3Rpb24xO30NCi0tPjwvc3R5
bGU+PCEtLVtpZiBndGUgbXNvIDldPjx4bWw+DQo8bzpzaGFwZWRlZmF1bHRzIHY6ZXh0PSJlZGl0
IiBzcGlkbWF4PSIxMDI2IiAvPg0KPC94bWw+PCFbZW5kaWZdLS0+PCEtLVtpZiBndGUgbXNvIDld
Pjx4bWw+DQo8bzpzaGFwZWxheW91dCB2OmV4dD0iZWRpdCI+DQo8bzppZG1hcCB2OmV4dD0iZWRp
dCIgZGF0YT0iMSIgLz4NCjwvbzpzaGFwZWxheW91dD48L3htbD48IVtlbmRpZl0tLT4NCjwvaGVh
ZD4NCjxib2R5IGxhbmc9IlpILUNOIiBsaW5rPSJibHVlIiB2bGluaz0icHVycGxlIj4NCjxkaXYg
Y2xhc3M9IldvcmRTZWN0aW9uMSI+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJF
Ti1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMC41cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZx
dW90OyxzYW5zLXNlcmlmO2NvbG9yOiMxRjQ5N0QiPkhpIExpbmRhLDxvOnA+PC9vOnA+PC9zcGFu
PjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9u
dC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWY7
Y29sb3I6IzFGNDk3RCI+SSBzdXBwb3J0IGFkb3B0aW9uIG9mIHRoaXMgZHJhZnQgKGFzIGNvLWF1
dGhvcikuJm5ic3A7IEkgZG8gbm90IGtub3cgb2YgYW55IElQUiByZWxhdGVkIHRvIHRoaXMgZHJh
ZnQuDQo8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBs
YW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMC41cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2Fs
aWJyaSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOiMxRjQ5N0QiPjxvOnA+Jm5ic3A7PC9vOnA+PC9z
cGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0i
Zm9udC1zaXplOjEwLjVwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2Vy
aWY7Y29sb3I6IzFGNDk3RCI+VGhhbmtzITxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjVwdDtm
b250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6IzFGNDk3RCI+
PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4g
bGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAuNXB0O2ZvbnQtZmFtaWx5OiZxdW90O0Nh
bGlicmkmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjojMUY0OTdEIj5CLlIuPG86cD48L286cD48L3Nw
YW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJm
b250LXNpemU6MTAuNXB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJp
Zjtjb2xvcjojMUY0OTdEIj5GcmFuazxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjVwdDtmb250
LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6IzFGNDk3RCI+PG86
cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPGRpdj4NCjxkaXYgc3R5bGU9ImJvcmRlcjpub25l
O2JvcmRlci10b3A6c29saWQgI0UxRTFFMSAxLjBwdDtwYWRkaW5nOjMuMHB0IDBjbSAwY20gMGNt
Ij4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0
O2ZvbnQtZmFtaWx5OiZxdW90O+W+rui9r+mbhem7kSZxdW90OyxzYW5zLXNlcmlmIj7lj5Hku7bk
uro8c3BhbiBsYW5nPSJFTi1VUyI+Ojwvc3Bhbj48L3NwYW4+PC9iPjxzcGFuIGxhbmc9IkVOLVVT
IiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDvlvq7ova/pm4Xpu5Em
cXVvdDssc2Fucy1zZXJpZiI+IEkybnNmIFttYWlsdG86aTJuc2YtYm91bmNlc0BpZXRmLm9yZ10N
Cjwvc3Bhbj48Yj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVv
dDvlvq7ova/pm4Xpu5EmcXVvdDssc2Fucy1zZXJpZiI+5Luj6KGoIDwvc3Bhbj4NCjwvYj48c3Bh
biBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7
5b6u6L2v6ZuF6buRJnF1b3Q7LHNhbnMtc2VyaWYiPkxpbmRhIER1bmJhcjxicj4NCjwvc3Bhbj48
Yj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDvlvq7ova/p
m4Xpu5EmcXVvdDssc2Fucy1zZXJpZiI+5Y+R6YCB5pe26Ze0PHNwYW4gbGFuZz0iRU4tVVMiPjo8
L3NwYW4+PC9zcGFuPjwvYj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMS4w
cHQ7Zm9udC1mYW1pbHk6JnF1b3Q75b6u6L2v6ZuF6buRJnF1b3Q7LHNhbnMtc2VyaWYiPiAyMDE4
PC9zcGFuPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O+W+
rui9r+mbhem7kSZxdW90OyxzYW5zLXNlcmlmIj7lubQ8c3BhbiBsYW5nPSJFTi1VUyI+MTI8L3Nw
YW4+5pyIPHNwYW4gbGFuZz0iRU4tVVMiPjY8L3NwYW4+5pelPHNwYW4gbGFuZz0iRU4tVVMiPg0K
IDY6MzI8YnI+DQo8L3NwYW4+PGI+5pS25Lu25Lq6PHNwYW4gbGFuZz0iRU4tVVMiPjo8L3NwYW4+
PC9iPjxzcGFuIGxhbmc9IkVOLVVTIj4gaTJuc2ZAaWV0Zi5vcmc8YnI+DQo8L3NwYW4+PGI+5Li7
6aKYPHNwYW4gbGFuZz0iRU4tVVMiPjo8L3NwYW4+PC9iPjxzcGFuIGxhbmc9IkVOLVVTIj4gW0ky
bnNmXSBDYWxsIGZvciBXRyBBZG9wdGlvbiBvbiBOU0YgTW9uaXRvcmluZyBEcmFmdDxvOnA+PC9v
OnA+PC9zcGFuPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1h
bCI+PHNwYW4gbGFuZz0iRU4tVVMiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjExLjBw
dDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6IzFGNDk3
RCI+VGhpcyBpcyB0aGUgc3RhcnQgb2YgYSB0d28gd2Vla3MgY2FsbCBmb3IgaW5wdXQgb24gdGhl
IFdHIGFkb3B0aW9uIG9mIHRoZSBkb2N1bWVudDoNCjwvc3Bhbj48c3BhbiBsYW5nPSJFTi1VUyI+
PGEgaHJlZj0iaHR0cHM6Ly90b29scy5pZXRmLm9yZy9odG1sL2RyYWZ0LWhvbmctaTJuc2YtbnNm
LW1vbml0b3JpbmctZGF0YS1tb2RlbC0wNiI+aHR0cHM6Ly90b29scy5pZXRmLm9yZy9odG1sL2Ry
YWZ0LWhvbmctaTJuc2YtbnNmLW1vbml0b3JpbmctZGF0YS1tb2RlbC0wNjwvYT48L3NwYW4+PHNw
YW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90
O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjojMUY0OTdEIj48bzpwPjwvbzpwPjwvc3Bh
bj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZv
bnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlm
O2NvbG9yOiMxRjQ5N0QiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250
LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6IzFGNDk3RCI+VGhh
bmtzIGZvciB0aGUgYXV0aG9ycyBvZiB0aGUgdHdvIEkyTlNGIE1vbml0b3JpbmcgZHJhZnRzIHRh
a2luZyBhY3Rpb25zIG9mIG1lcmdpbmcgdGhlIGNvbnRlbnQuDQo8bzpwPjwvbzpwPjwvc3Bhbj48
L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQt
c2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmO2Nv
bG9yOiMxRjQ5N0QiPldlIG5lZWQgbW9yZSBvZiB0aG9zZSBhY3Rpb25zLiBBcyBvZiBub3cgd2Ug
aGF2ZSA4IFdHIGRyYWZ0cy4gV2UgbmVlZCB0byBmaW5pc2ggdGhlbSBuZXh0IGZldyBtb250aHMu
DQo8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5n
PSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJy
aSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOiMxRjQ5N0QiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFu
PjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9u
dC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWY7
Y29sb3I6IzFGNDk3RCI+QmVhciBpbiBtaW5kIHRoYXQgV0cgYWRvcHRpb24gZG9lc27igJl0IG1l
YW4gdGhlIGRyYWZ0IGlzIHJlYWR5LCBvbmx5IG1lYW5zIHRoYXQgV0cgd2lsbCB3b3JrIHRvZ2V0
aGVyIG9uIHRoZSBkcmFmdCAoaW5zdGVhZCBvZiBpbmRpdmlkdWFscykuDQo8bzpwPjwvbzpwPjwv
c3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9
ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNl
cmlmO2NvbG9yOiMxRjQ5N0QiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtm
b250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6IzFGNDk3RCI+
UGxlYXNlIHByb3ZpZGUgZmVlZGJhY2sgdG8gdGhlIGxpc3QvY2hhaXJzIGlmIHlvdSBiZWxpZXZl
IHRoYXQgdGhpcyBkb2N1bWVudCBzaG91bGQgYmUgYWRvcHRlZCBhcyBhIFdHIGRvY3VtZW50Ljxv
OnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVO
LVVTIiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1
b3Q7LHNhbnMtc2VyaWY7Y29sb3I6IzFGNDk3RCI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9w
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNp
emU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZjtjb2xv
cjojMUY0OTdEIj5UaGFua3MsDQo8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1m
YW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOiMxRjQ5N0QiPjxvOnA+
Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9
IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJp
JnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6IzFGNDk3RCI+TGluZGEgJmFtcDsgWW9hdjxvOnA+PC9v
OnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBz
dHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNh
bnMtc2VyaWY7Y29sb3I6IzFGNDk3RCI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCI+PGEgbmFtZT0iX01haWxFbmRDb21wb3NlIj48L2E+PHNwYW4gbGFu
Zz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGli
cmkmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjojMUY0OTdEIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bh
bj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48Yj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9
ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNl
cmlmIj5Gcm9tOjwvc3Bhbj48L2I+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6
MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZiI+IE1yLiBK
YWVob29uIFBhdWwgSmVvbmcgWzxhIGhyZWY9Im1haWx0bzpqYWVob29uLnBhdWxAZ21haWwuY29t
Ij5tYWlsdG86amFlaG9vbi5wYXVsQGdtYWlsLmNvbTwvYT5dDQo8YnI+DQo8Yj5TZW50OjwvYj4g
VGh1cnNkYXksIE5vdmVtYmVyIDE1LCAyMDE4IDY6MzUgUE08YnI+DQo8Yj5Ubzo8L2I+IExpbmRh
IER1bmJhciAmbHQ7PGEgaHJlZj0ibWFpbHRvOmxpbmRhLmR1bmJhckBodWF3ZWkuY29tIj5saW5k
YS5kdW5iYXJAaHVhd2VpLmNvbTwvYT4mZ3Q7OyBZb2F2IE5pciAmbHQ7PGEgaHJlZj0ibWFpbHRv
OnluaXIuaWV0ZkBnbWFpbC5jb20iPnluaXIuaWV0ZkBnbWFpbC5jb208L2E+Jmd0Ozxicj4NCjxi
PkNjOjwvYj4gPGEgaHJlZj0ibWFpbHRvOmkybnNmQGlldGYub3JnIj5pMm5zZkBpZXRmLm9yZzwv
YT47IDxhIGhyZWY9Im1haWx0bzpza2t1X3NlY3UtYnJhaW5fYWxsQGdvb2dsZWdyb3Vwcy5jb20i
Pg0Kc2trdV9zZWN1LWJyYWluX2FsbEBnb29nbGVncm91cHMuY29tPC9hPjsgU2FuZ3dvbiBIeXVu
ICZsdDs8YSBocmVmPSJtYWlsdG86c3doeXVuNzdAZ21haWwuY29tIj5zd2h5dW43N0BnbWFpbC5j
b208L2E+Jmd0OzsgTXIuIEphZWhvb24gUGF1bCBKZW9uZyAmbHQ7PGEgaHJlZj0ibWFpbHRvOmph
ZWhvb24ucGF1bEBnbWFpbC5jb20iPmphZWhvb24ucGF1bEBnbWFpbC5jb208L2E+Jmd0Ozxicj4N
CjxiPlN1YmplY3Q6PC9iPiBSZXF1ZXN0IGZvciBXRyBBZG9wdGlvbiBDYWxsIG9uIE5TRiBNb25p
dG9yaW5nIERyYWZ0PG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+
PHNwYW4gbGFuZz0iRU4tVVMiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxkaXY+DQo8
ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIj5IaSBM
aW5kYSBhbmQgWW9hdiw8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyI+QXMgd2UgZGlzY3Vzc2VkIHRoZSBs
YXN0IEJhbmdrb2sgbWVldGluZyw8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyI+SSBoYXZlIG1lcmdlZCB0
aGUgdHdvIGRyYWZ0cyBvZiBJbmZvcm1hdGlvbiBNb2RlbCBhbmQgRGF0YSBNb2RlbDxvOnA+PC9v
OnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFu
IGxhbmc9IkVOLVVTIj5mb3IgTlNGIE1vbml0b3JpbmcgaW50byBhIG5ldyBkcmFmdCBjYWxsZWQg
ZHJhZnQtaG9uZy1pMm5zZi1uc2YtbW9uaXRvcmluZy1kYXRhLW1vZGVsLTA2OjxvOnA+PC9vOnA+
PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxh
bmc9IkVOLVVTIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyI+LSBUd28gSW5mb3JtYXRpb24g
YW5kIERhdGEgTW9kZWwgRHJhZnRzPG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiPiZuYnNwOy4gZHJhZnQt
emhhbmctaTJuc2YtaW5mby1tb2RlbC1tb25pdG9yaW5nLTA3Jm5ic3A7PG86cD48L286cD48L3Nw
YW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0i
RU4tVVMiPiZuYnNwOy4gZHJhZnQtaG9uZy1pMm5zZi1uc2YtbW9uaXRvcmluZy1kYXRhLW1vZGVs
LTA1PG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjwv
ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIj4tIEEg
TWVyZ2VkIERhdGEgTW9kZWwgRHJhZnQmbmJzcDs8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rp
dj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyI+Jm5ic3A7
LiBkcmFmdC1ob25nLWkybnNmLW5zZi1tb25pdG9yaW5nLWRhdGEtbW9kZWwtMDY8bzpwPjwvbzpw
Pjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBs
YW5nPSJFTi1VUyI+Jm5ic3A7LiA8YSBocmVmPSJodHRwczovL3Rvb2xzLmlldGYub3JnL2h0bWwv
ZHJhZnQtaG9uZy1pMm5zZi1uc2YtbW9uaXRvcmluZy1kYXRhLW1vZGVsLTA2Ij4NCmh0dHBzOi8v
dG9vbHMuaWV0Zi5vcmcvaHRtbC9kcmFmdC1ob25nLWkybnNmLW5zZi1tb25pdG9yaW5nLWRhdGEt
bW9kZWwtMDY8L2E+PG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFu
PjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVO
LVVTIj5UaGUgTlNGIG1vbml0b3JpbmcgaXMgdmVyeSBpbXBvcnRhbnQgdG8gbWFuYWdlIHRoZSBJ
Mk5TRiBzZWN1cml0eSBzZXJ2aWNlIHN5c3RlbTxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2
Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIj5pbiBhIHJl
bGlhYmxlIGFuZCBzY2FsYWJsZSBmYXNoaW9uLjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2
Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIj48bzpwPiZu
YnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij48c3BhbiBsYW5nPSJFTi1VUyI+Q291bGQgeW91IHN0YXJ0IGEgV0cgYWRvcHRpb24gY2FsbCBm
b3IgdGhpcyBkcmFmdD88bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyI+PG86cD4mbmJzcDs8L286cD48L3Nw
YW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0i
RU4tVVMiPlRoYW5rcy48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyI+PG86cD4mbmJzcDs8L286cD48L3Nw
YW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0i
RU4tVVMiPkJlc3QgUmVnYXJkcyw8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyI+UGF1bDxvOnA+PC9vOnA+
PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxh
bmc9IkVOLVVTIj4tLSZuYnNwOzxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4N
CjxkaXY+DQo8ZGl2Pg0KPGRpdj4NCjxkaXY+DQo8ZGl2Pg0KPGRpdj4NCjxkaXY+DQo8cCBjbGFz
cz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyI+PT09PT09PT09PT09PT09PT09PT09PT09
PT09PGJyPg0KTXIuIEphZWhvb24gKFBhdWwpIEplb25nLCBQaC5ELjxicj4NCkFzc29jaWF0ZSBQ
cm9mZXNzb3I8YnI+DQpEZXBhcnRtZW50IG9mIFNvZnR3YXJlPGJyPg0KU3VuZ2t5dW5rd2FuIFVu
aXZlcnNpdHk8YnI+DQpPZmZpY2U6ICYjNDM7ODItMzEtMjk5LTQ5NTc8YnI+DQpFbWFpbDogPGEg
aHJlZj0ibWFpbHRvOmphZWhvb24ucGF1bEBnbWFpbC5jb20iIHRhcmdldD0iX2JsYW5rIj5qYWVo
b29uLnBhdWxAZ21haWwuY29tPC9hPiwmbmJzcDs8YSBocmVmPSJtYWlsdG86cGF1bGplb25nQHNr
a3UuZWR1IiB0YXJnZXQ9Il9ibGFuayI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZTo5LjVwdCI+cGF1
bGplb25nQHNra3UuZWR1PC9zcGFuPjwvYT48YnI+DQpQZXJzb25hbCBIb21lcGFnZTogPGEgaHJl
Zj0iaHR0cDovL2Nwc2xhYi5za2t1LmVkdS9wZW9wbGUtamFlaG9vbi1qZW9uZy5waHAiIHRhcmdl
dD0iX2JsYW5rIj4NCmh0dHA6Ly9pb3RsYWIuc2trdS5lZHUvcGVvcGxlLWphZWhvb24tamVvbmcu
cGhwPC9hPjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwv
ZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9k
aXY+DQo8L2JvZHk+DQo8L2h0bWw+DQo=

--_000_C02846B1344F344EB4FAA6FA7AF481F12C945504DGGEMM531MBSchi_--


From nobody Tue Dec 11 03:21:56 2018
Return-Path: <ietfc@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 2DC90130DDE; Tue, 11 Dec 2018 03:21:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.738
X-Spam-Level: *
X-Spam-Status: No, score=1.738 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-1.459, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RATWARE_MS_HASH=2.148, RATWARE_OUTLOOK_NONAME=2.95, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no 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 fAJz24YjwQCQ; Tue, 11 Dec 2018 03:21:52 -0800 (PST)
Received: from EUR01-DB5-obe.outbound.protection.outlook.com (mail-eopbgr150133.outbound.protection.outlook.com [40.107.15.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4A7E3130DD0; Tue, 11 Dec 2018 03:21:52 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=btconnect.onmicrosoft.com; s=selector1-btconnect-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=jA9poiVb1mMfbIvG6Txzr1e4IgdA+LzFPXqdA8FZVbk=; b=aGX9hVNixbZOKFZgbNbeB6O23wjx1c5FPpgbCih3+KtcfVqSFCt00BL9e3ztA8ZN5a2Nb8yOZkKTaL1cFycP/5VxJ96B67nLPSCvAY0LkXWvw/nj8eWIwqu2eBiY30Ly74q3+yFr+e5PAjbwAmopfOO27NW2x7d9Hae0PifOGUI=
Received: from VI1PR07MB4717.eurprd07.prod.outlook.com (20.177.54.82) by VI1PR07MB0958.eurprd07.prod.outlook.com (10.161.110.150) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1425.12; Tue, 11 Dec 2018 11:21:49 +0000
Received: from VI1PR07MB4717.eurprd07.prod.outlook.com ([fe80::1575:d33b:33dd:c7c4]) by VI1PR07MB4717.eurprd07.prod.outlook.com ([fe80::1575:d33b:33dd:c7c4%5]) with mapi id 15.20.1425.016; Tue, 11 Dec 2018 11:21:49 +0000
From: tom petch <ietfc@btconnect.com>
To: Linda Dunbar <linda.dunbar@huawei.com>, "opsawg@ietf.org" <opsawg@ietf.org>
CC: "i2nsf@ietf.org" <i2nsf@ietf.org>
Thread-Topic: [OPSAWG] is there any work in Ops Area for monitoring network functions?
Thread-Index: AQHUkUO1T0Lu/xD+tkuIG3RwDsQz5w==
Date: Tue, 11 Dec 2018 11:21:49 +0000
Message-ID: <039901d49143$5d6dcba0$4001a8c0@gateway.2wire.net>
References: <4A95BA014132FF49AE685FAB4B9F17F66B1F609F@SJCEML521-MBB.china.huawei.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-clientproxiedby: LO2P265CA0196.GBRP265.PROD.OUTLOOK.COM (2603:10a6:600:9e::16) To VI1PR07MB4717.eurprd07.prod.outlook.com (2603:10a6:803:69::18)
x-ms-exchange-messagesentrepresentingtype: 1
x-originating-ip: [86.139.215.184]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; VI1PR07MB0958; 6:7JPxeOcaJAFwMdO9GmkqRs+A2gEJ8Us4Q6lEJFaDeQuzC71PLqGfEzJvQPU6PAln7M0Kb+fscksbayVOwj3PTKAaxyFNyEvsraf+iZvEyB4KVGGPDUi9V9mOAWu0ocglzyYlAxjJvMe+bGDJeggxvYTwBapcDYMll2G+6I93ZEJqvt59XQk9R1aZmo50mmL5C9qxWZRlAwEJXd2eASuwHC31ZrCMVZRkyMQAl+91ECqhyzzaGNrABeCUMlT2ROmAJLtH4EXXWQJYvndAhNDuBOns8t2mmrcqoJ/6i8BPogMCKr6ir93ro7B0ENLPKg4lAi2ahcKoQItM2LhrYqiyq2XMY/xkbuaCA2TUM2p7Oan7goT6znpkYr7Yx5gfiNxmkTqICyqing2ciOMLSm3mPsJO7xlqmJKk9CSo7xqk+fQwyryfpJA6trEoCVJG9If+XLB8TuI88m1alxaSekKEYemHNffsJXYKuLqZXebg1U4=; 5:bS2ry1mL/am+RtdRuTcsy1iro2uifxInkmwd11Hsw/yiA0ixaOgkhr/6k2oM3puHl6vueAy++rmt5Y1WXEFTvOBXwPom895/DVXIDZPYmaLqYuEBM1gdz6+LdgE5GS+3tREHoe4Nl0evCEcgxR6dHOmn61Ada/NgTb/Xttc+tpg=; 7:XDHpmy+XL6hlpFBKupdu33isQ2AgRLsIgGrOXl+i/07NtTDq9w4g8uAU8bonvFdTUz7YnE4nRrV2wsmewAeivcvdY4vu2DtEg8TyKn3yuBpShqBs9QgtWDf06JBiwTRcCbhpsaxlY0Ju9JHEBC/TqQ==
x-ms-office365-filtering-correlation-id: e9114df8-7a1c-4bfc-c00b-08d65f5ad809
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390098)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600074)(711020)(2017052603328)(7193020); SRVR:VI1PR07MB0958; 
x-ms-traffictypediagnostic: VI1PR07MB0958:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=ietfc@btconnect.com; 
x-microsoft-antispam-prvs: <VI1PR07MB0958377504E8912D88148A30A0A60@VI1PR07MB0958.eurprd07.prod.outlook.com>
x-ms-exchange-senderadcheck: 1
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(3230017)(999002)(6040522)(2401047)(8121501046)(5005006)(10201501046)(93006095)(93001095)(3002001)(3231472)(944501520)(4982022)(52105112)(6055026)(148016)(149066)(150057)(6041310)(20161123560045)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123558120)(20161123564045)(20161123562045)(201708071742011)(7699051)(76991095); SRVR:VI1PR07MB0958; BCL:0; PCL:0; RULEID:; SRVR:VI1PR07MB0958; 
x-forefront-prvs: 08831F51DC
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(39860400002)(136003)(376002)(366004)(346002)(396003)(199004)(189003)(13464003)(105586002)(6246003)(325944009)(966005)(478600001)(305945005)(2501003)(1556002)(6306002)(6512007)(9686003)(53936002)(86152003)(14496001)(7736002)(81156014)(81166006)(316002)(14454004)(110136005)(8936002)(106356001)(14444005)(3846002)(15188155005)(186003)(71190400001)(26005)(71200400001)(97736004)(52116002)(6486002)(6116002)(8676002)(84392002)(66066001)(76176011)(44736005)(53546011)(6506007)(25786009)(2906002)(33896004)(386003)(229853002)(16799955002)(446003)(68736007)(99286004)(102836004)(4326008)(6436002)(5660300001)(486006)(476003)(86362001)(256004); DIR:OUT; SFP:1102; SCL:1; SRVR:VI1PR07MB0958; H:VI1PR07MB4717.eurprd07.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:0; MX:1; 
received-spf: None (protection.outlook.com: btconnect.com does not designate permitted sender hosts)
x-microsoft-antispam-message-info: 2gE2+CDRSu9vIM6aHwKjwSe3iiroZpUCVa6WuRrn3uAEWRKYGtT7EqSB3cpdMTlkDk5RvcbKHS+XxUYDaU3/I/YmRiy1mDc5ubE4LkoGlcX7A6SsLWlxBkRnXi75l+Wno1sod5do62ap9y93ldsdj+qCY4mDEh4OLyyE5FtzA5+u2J54OVelKV4GeXq0Oko4P18eRWhlStrgv5sCbKAHvT3j+K6WCuYC+GZArekddl1nVOQ6EOv6rwzJiVHp663aYcL7a+lQGMyCKK03Wp5m2n0rI5W3Uixa0RJp36WrZ/2DebbCgHa4afw0xcNbgN2y
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="utf-8"
Content-ID: <8F61734ECFF19E48AF48C2C824558BCD@eurprd07.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: btconnect.com
X-MS-Exchange-CrossTenant-Network-Message-Id: e9114df8-7a1c-4bfc-c00b-08d65f5ad809
X-MS-Exchange-CrossTenant-originalarrivaltime: 11 Dec 2018 11:21:49.8028 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: cf8853ed-96e5-465b-9185-806bfe185e30
X-MS-Exchange-Transport-CrossTenantHeadersStamped: VI1PR07MB0958
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2nsf/N98kLFE8zDu9lzpExmi47FbKLAs>
Subject: Re: [I2nsf] [OPSAWG] is there any work in Ops Area for monitoring network functions?
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, 11 Dec 2018 11:21:55 -0000

TGluZGENCg0KSSBsb29rZWQgYXQgdGhlIGRyYWZ0IGFuZCB0aGluayB0aGF0IGl0IG5lZWRzIHNv
bWUgd29yayBiZWZvcmUgaXQgaXMgYQ0KWUFORyBtb2R1bGU6LSkNCg0KLSBOTURBIGNvbmZvcm1h
bmNlIGlzIG5vdCBtZW50aW9uZWQNCg0KLSB0aGUgcmVmZXJlbmNlIHRvIFJGQzIxMTkgaXMgb3V0
IG9mIGRhdGUNCg0KLSB0aGUgZm9ybWF0IGZvciB0cmVlIGRpYWdyYW1zIGlzIG5vdyBzcGVjaWZp
ZWQgaW4gUkZDODM0MA0KDQotIFlBTkcgaW1wb3J0IHN0YXRlbWVudHMgbGFjayAncmVmZXJlbmNl
JyBhcyBpbg0KICAgICBpbXBvcnQgaWV0Zi1pbmV0LXR5cGVzIHsNCiAgICAgICBwcmVmaXggImlu
ZXQiOw0KICAgICAgIHJlZmVyZW5jZSAiUkZDIDY5OTEgLSBDb21tb24gWUFORyBEYXRhIFR5cGVz
IjsNCg0KLSBZQU5HIG1vZHVsZSBoYXMgbm8gY29weXJpZ2h0DQoNCi0gWUFORyBtb2R1bGUgaGFz
IChhbG1vc3QpIG5vIHJlZmVyZW5jZSBzdGF0ZW1lbnRzIHRvIHRlbGwgdGhlIHVzZXINCihsaWtl
IG1lKSAgd2hlcmV0byBnbyB0byB1bmRlcnN0YW5kIGl0LiBsb29rLCBmb3IgZXhhbXBsZSwgYXQN
CmRyYWZ0LWlldGYtb3BzYXdnLW5hdC15YW5nDQpmb3IgYSBtb2R1bGUgdGhhdCBpcyB3ZWxsIHN1
cHBsaWVkIHdpdGggcmVmZXJlbmNlIHN0YXRlbWVudHMNCg0KLSBZQU5HIG1vZHVsZSBzaG91bGQg
cmVmZXJlbmNlIHRoZSBSRkMgZnJvbSB3aGljaCBpdCBjb21lcw0KDQotIHRoZSBvbmUgYW5kIG9u
bHkgcmVmZXJlbmNlIGluIHRoZSBZQU5HIG1vZHVsZSBpcw0KICAgICAgcmVmZXJlbmNlDQogICAg
ICAgICAiZHJhZnQtemhhbmctaTJuc2YtaW5mby1tb2RlbC1tb25pdG9yaW5nLTA3IjsNCmJ1dCB0
aGUgSS1EIGlzDQogICAgICAgICBkcmFmdC1ob25nLWkybnNmLW5zZi1tb25pdG9yaW5nLWRhdGEt
bW9kZWwtMDYNCkkgZG8gbm90IHVuZGVyc3RhbmQNCg0KLSB3aGVyZSB5b3UgcmVmZXJlbmNlIGFu
IEktRCwgaXQgbmVlZHMgYSBOb3RlIHRvIHRoZSBSRkMgRWRpdG9yIGUuZy4NCiByZWZlcmVuY2Ug
ICAgICAgImRyYWZ0LXpoYW5nLWkybnNmLWluZm8tbW9kZWwtbW9uaXRvcmluZy0wNyI7DQpiZWNv
bWVzDQogcmVmZXJlbmNlIFJGQyBZWVlZICIuLi4uLiINCi0tIE5vdGUgdG8gUkZDIEVkaXRvciBw
bGVhc2UgcmVwbGFjZSBZWVlZIHdpdGggdGhlIG51bWJlciBhc3NpZ25lZCB0bw0KICAgICAgICAg
ImRyYWZ0LXpoYW5nLWkybnNmLWluZm8tbW9kZWwtbW9uaXRvcmluZyINCg0KLSBJQU5BIENvbnNp
ZGVyYXRpb25zIG11c3QgYmUgcHJlc2VudA0KDQotIFNlY3VyaXR5IENvbnNpZGVyYXRpb25zIG11
c3QgaW5jbHVkZSB0aGUgWUFORyB0ZW1wbGF0ZQ0KDQpIVEg6LSkNCg0KSSBhbSBub3Qgb24gdGhl
IEkyTlNGIGxpc3QuDQoNClRvbSBQZXRjaA0KDQotLS0tLSBPcmlnaW5hbCBNZXNzYWdlIC0tLS0t
DQpGcm9tOiAiTGluZGEgRHVuYmFyIiA8bGluZGEuZHVuYmFyQGh1YXdlaS5jb20+DQpUbzogPG9w
c2F3Z0BpZXRmLm9yZz4NCkNjOiA8aTJuc2ZAaWV0Zi5vcmc+DQpTZW50OiBXZWRuZXNkYXksIERl
Y2VtYmVyIDA1LCAyMDE4IDU6MjcgUE0NCg0KPiBPcHNhV0c6DQo+DQo+IEkyTlNGIFdHIGhhcyBh
IGRyYWZ0IG9uIGRhdGEgbW9kZWxzIChhbmQgaW5mb3JtYXRpb24gbW9kZWwpIG9mDQptb25pdG9y
aW5nIG5ldHdvcmsgc2VjdXJpdHkgZnVuY3Rpb25zOg0KaHR0cHM6Ly90b29scy5pZXRmLm9yZy9o
dG1sL2RyYWZ0LWhvbmctaTJuc2YtbnNmLW1vbml0b3JpbmctZGF0YS1tb2RlbC0wDQo2DQo+DQo+
IEl0IGluY2x1ZGVzIGRhdGEgbW9kZWxzIHRvIHJldHJpZXZlIFN5c3RlbSBBbGFybXMsIFN5c3Rl
bSBFdmVudHMsDQpjb3VudGVycywgTlNGIEV2ZW50cy9sb2dzLCBldGMuDQo+DQo+IFdhbnQgdG8g
c2VlIGlmIHRoZXJlIGFyZSBkYXRhIG1vZGVscyBhbHJlYWR5IHNwZWNpZmllZCBieSBPcHMgQXJl
YSBmb3INCm1vbml0b3JpbmcgbmV0d29yayBmdW5jdGlvbnMgd2hpY2ggbWlnaHQgaGF2ZSBzb21l
IGNvbW1vbiBhdHRyaWJ1dGVzDQp0aGF0IEkyTlNGIGNhbiBpbXBvcnQuDQo+DQo+IFRoYW5rcywg
TGluZGEgRHVuYmFyDQo+DQo+IEZyb206IE1yLiBKYWVob29uIFBhdWwgSmVvbmcgW21haWx0bzpq
YWVob29uLnBhdWxAZ21haWwuY29tXQ0KPiBTZW50OiBUaHVyc2RheSwgTm92ZW1iZXIgMTUsIDIw
MTggNjozNSBQTQ0KPiBUbzogTGluZGEgRHVuYmFyDQo8bGluZGEuZHVuYmFyQGh1YXdlaS5jb208
bWFpbHRvOmxpbmRhLmR1bmJhckBodWF3ZWkuY29tPj47IFlvYXYgTmlyDQo8eW5pci5pZXRmQGdt
YWlsLmNvbTxtYWlsdG86eW5pci5pZXRmQGdtYWlsLmNvbT4+DQo+IENjOiBpMm5zZkBpZXRmLm9y
ZzxtYWlsdG86aTJuc2ZAaWV0Zi5vcmc+Ow0Kc2trdV9zZWN1LWJyYWluX2FsbEBnb29nbGVncm91
cHMuY29tPG1haWx0bzpza2t1X3NlY3UtYnJhaW5fYWxsQGdvb2dsZWdyDQpvdXBzLmNvbT47IFNh
bmd3b24gSHl1biA8c3doeXVuNzdAZ21haWwuY29tPG1haWx0bzpzd2h5dW43N0BnbWFpbC5jb20+
PjsNCk1yLiBKYWVob29uIFBhdWwgSmVvbmcNCjxqYWVob29uLnBhdWxAZ21haWwuY29tPG1haWx0
bzpqYWVob29uLnBhdWxAZ21haWwuY29tPj4NCj4gU3ViamVjdDogUmVxdWVzdCBmb3IgV0cgQWRv
cHRpb24gQ2FsbCBvbiBOU0YgTW9uaXRvcmluZyBEcmFmdA0KPg0KPiBIaSBMaW5kYSBhbmQgWW9h
diwNCj4gQXMgd2UgZGlzY3Vzc2VkIHRoZSBsYXN0IEJhbmdrb2sgbWVldGluZywNCj4gSSBoYXZl
IG1lcmdlZCB0aGUgdHdvIGRyYWZ0cyBvZiBJbmZvcm1hdGlvbiBNb2RlbCBhbmQgRGF0YSBNb2Rl
bA0KPiBmb3IgTlNGIE1vbml0b3JpbmcgaW50byBhIG5ldyBkcmFmdCBjYWxsZWQNCmRyYWZ0LWhv
bmctaTJuc2YtbnNmLW1vbml0b3JpbmctZGF0YS1tb2RlbC0wNjoNCj4NCj4gLSBUd28gSW5mb3Jt
YXRpb24gYW5kIERhdGEgTW9kZWwgRHJhZnRzDQo+ICAuIGRyYWZ0LXpoYW5nLWkybnNmLWluZm8t
bW9kZWwtbW9uaXRvcmluZy0wNw0KPiAgLiBkcmFmdC1ob25nLWkybnNmLW5zZi1tb25pdG9yaW5n
LWRhdGEtbW9kZWwtMDUNCj4NCj4gLSBBIE1lcmdlZCBEYXRhIE1vZGVsIERyYWZ0DQo+ICAuIGRy
YWZ0LWhvbmctaTJuc2YtbnNmLW1vbml0b3JpbmctZGF0YS1tb2RlbC0wNg0KPiAgLg0KaHR0cHM6
Ly90b29scy5pZXRmLm9yZy9odG1sL2RyYWZ0LWhvbmctaTJuc2YtbnNmLW1vbml0b3JpbmctZGF0
YS1tb2RlbC0wDQo2DQo+DQo+IFRoZSBOU0YgbW9uaXRvcmluZyBpcyB2ZXJ5IGltcG9ydGFudCB0
byBtYW5hZ2UgdGhlIEkyTlNGIHNlY3VyaXR5DQpzZXJ2aWNlIHN5c3RlbQ0KPiBpbiBhIHJlbGlh
YmxlIGFuZCBzY2FsYWJsZSBmYXNoaW9uLg0KPg0KPiBDb3VsZCB5b3Ugc3RhcnQgYSBXRyBhZG9w
dGlvbiBjYWxsIGZvciB0aGlzIGRyYWZ0Pw0KPg0KPiBUaGFua3MuDQo+DQo+IEJlc3QgUmVnYXJk
cywNCj4gUGF1bA0KPiAtLQ0KPiA9PT09PT09PT09PT09PT09PT09PT09PT09PT0NCj4gTXIuIEph
ZWhvb24gKFBhdWwpIEplb25nLCBQaC5ELg0KPiBBc3NvY2lhdGUgUHJvZmVzc29yDQo+IERlcGFy
dG1lbnQgb2YgU29mdHdhcmUNCj4gU3VuZ2t5dW5rd2FuIFVuaXZlcnNpdHkNCj4gT2ZmaWNlOiAr
ODItMzEtMjk5LTQ5NTcNCj4gRW1haWw6IGphZWhvb24ucGF1bEBnbWFpbC5jb208bWFpbHRvOmph
ZWhvb24ucGF1bEBnbWFpbC5jb20+LA0KcGF1bGplb25nQHNra3UuZWR1PG1haWx0bzpwYXVsamVv
bmdAc2trdS5lZHU+DQo+IFBlcnNvbmFsIEhvbWVwYWdlOg0KaHR0cDovL2lvdGxhYi5za2t1LmVk
dS9wZW9wbGUtamFlaG9vbi1qZW9uZy5waHA8aHR0cDovL2Nwc2xhYi5za2t1LmVkdS9wDQplb3Bs
ZS1qYWVob29uLWplb25nLnBocD4NCg0K


From nobody Tue Dec 11 04:29:57 2018
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 61233127333; Tue, 11 Dec 2018 04:29:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_PASS=-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 72F7ogHjw8zD; Tue, 11 Dec 2018 04:29:51 -0800 (PST)
Received: from xenon43.um.es (xenon43.um.es [IPv6:2001:720:1710:601::43]) by ietfa.amsl.com (Postfix) with ESMTP id 4B305130DD0; Tue, 11 Dec 2018 04:29:50 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by xenon43.um.es (Postfix) with ESMTP id D30951FF31; Tue, 11 Dec 2018 13:29:47 +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 LkbqUGxFejrP; Tue, 11 Dec 2018 13:29:47 +0100 (CET)
Received: from quantum.inf.um.es (quantum.inf.um.es [155.54.204.208]) (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 D37D21FEBD; Tue, 11 Dec 2018 13:29:45 +0100 (CET)
From: Rafa Marin-Lopez <rafa@um.es>
Message-Id: <13E3B826-18EB-431A-ACE9-70E7B13B636F@um.es>
Content-Type: multipart/alternative; boundary="Apple-Mail=_C27FF821-CD48-4BF8-A1FE-34A3663B504C"
Mime-Version: 1.0 (Mac OS X Mail 12.0 \(3445.100.39\))
Date: Tue, 11 Dec 2018 13:29:44 +0100
In-Reply-To: <alpine.LRH.2.21.1811180149220.25604@bofh.nohats.ca>
Cc: Rafa Marin-Lopez <rafa@um.es>, Yoav Nir <ynir.ietf@gmail.com>, i2nsf@ietf.org, "ipsec@ietf.org WG" <ipsec@ietf.org>
To: Paul Wouters <paul@nohats.ca>
References: <A881C135-9BF7-4E93-BB7A-75EB3D1FF605@gmail.com> <6839D47C-4074-486F-9350-8EB7B378036C@um.es> <DAE14995-8504-4134-B021-93D56A4994FB@gmail.com> <alpine.LRH.2.21.1811180149220.25604@bofh.nohats.ca>
X-Mailer: Apple Mail (2.3445.100.39)
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2nsf/eszKbkgmyY-gcCuTW8F6sByiMcY>
Subject: Re: [I2nsf] Review of draft-ietf-i2nsf-sdn-ipsec-flow-protection-03 (Appendix A)
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, 11 Dec 2018 12:29:56 -0000

--Apple-Mail=_C27FF821-CD48-4BF8-A1FE-34A3663B504C
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Hi Paul, all:


>=20
> Appendix A:
>=20
> Why is it "eipsec" and not "ipsec=E2=80=9D ?

[Authors] We have fixed this now.
>=20
> Why is the organization not the IETF? Is this commonly done for yang =
models?

[Authors] You're right. We will change this to:

"IETF I2NSF (Interface to Network Security Functions) Working Group"
>=20
> encryption-algorithm-t - I think this should only list the MUST/SOULD =
items, so AES_GCM (1 flavour), AES_CCM (1 flavour) CHACHAPOLY1305 and =
NULL
>=20
> 	description "Encryption algorithms -&gt; RFC_5996=E2=80=9D;

[Authors] Right. Our doubt here is if we should refer instead to=20

https://tools.ietf.org/html/draft-ietf-netconf-crypto-types-02

such as=20

https://tools.ietf.org/html/draft-ietf-netconf-tls-client-server-08

is doing. If you check this link you will notice is referring to=20

<algorithm xmlns:ct=3D"urn:ietf:params:xml:ns:yang:ietf-crypto-t\
   ypes">ct:rsa2048</algorithm>
  =20
which is referring to ietf-crypto-types

>=20
> RFC 5996 is an obsolete reference. It should either refer to RFC 7296, =
or it should simply refer to the IANA registry involved.

[Authors] OK.
>=20
> integrity-algorithm-t: If the above is agreed, this enumeration should =
only contain "none" and the entries from aes-cmac-96 and up. That is,
> not contain des,md5,sha1 and aes_xcbc.  Same obsolete reference is =
used here in the description.

[Authors] Ok.

>=20
> type-autostartup: Maybe instead of RESPOND-ONLY, a better word is =
"STANDBY"? That way, the node could decide itself to bring a connection =
up
> without _requiring_ a remote signal, and could be triggered locally as =
as well as remotely to come up.

[Authors] Sounds reasonable. We should provide a better description of =
each value as well.

>=20
>      description "Different types of how IKEv2 starts the IPsec SAs";
>=20
> I would say "different policies of when to start an IKEv2 based IPsec =
SA". Does it need clarification this value is ignored or unused for the
> "case 2" scenario?

[Authors] This typedef is not used in the part of the model associated =
to case 2 but we can something in the description.=20
>=20
> auth-protocol-type:  This should only contain IKEv2. The enum should =
remain in case we get IKEv2.1 or IKEv3 in the future.

[Author] Agree.

>=20
>      description "Peer authentication protocols=E2=80=9D;
>=20
> I would say "IKE authentication protocol version", unless you want to =
keep the option open to have a non-IKE protocol. But I think that would
> run into many more issues of having parameters that are not defined =
for IKE?

[Author] Agree.
>=20
> ipsec-mode: It should only contain Tunnel and Transport Mode. It would =
be nice to see some text that forbids using Transport Mode when NAT is
> requested, just to avoid a lot of problems and disappointments. =
L2TP/IPsec still has major scars due to its use of Transport Mode with =
NAT.

[Authors] Sounds reasonable.

>=20
> esp-encap: as stated before, we are missing the port entry. I can also =
image that multiple encaps could be allowed, such as TCP-443 and =
TLS-443.
> Also note that the RFC for ESP over TCP recommends to continiously =
check if UDP encapsulation has become available, since it is so much =
prefered
> over TCP. But that only makes sense when the remote is a roaming =
client, and makes less sense if the network consists of data centers.

[Authors] Ok. Let's add the port entry. In any case, I believe that is =
something that implementation in the NSF (in particular the NETCONF =
server) could check (UDP encapsulation)


>=20
> ipsec-protocol: I think this should only contain esp. See earlier =
comments. Notably, if supporting ipcomp here, the yang model must be =
clear
> that it could need an ipcomp + esp IPsec SA for a single 'connection'. =
Even if we only leave esp as a valid option, keep this enum in case
> we come up with a new esp version of some esp-lite version.

[Authors] We are in favour on leaving only ESP. If the WG agrees, let's =
proceed that way.

>=20
> lifetime-action only has "terminate" and "rekey". For libreswan we use =
"clear", "hold" and "restart". The difference
> between clear and hold is what kernel policy to install for cleartext =
packets. For roadwarrionrs coming in, you
> want clear to leave no trace. for a site-to-site VPN you generally =
want "hold" to ensure you drop all packets until
> a new tunnel is established (possible ondemand, so this is different =
from restart)
[Authors] Basically we have "terminate" and "rekey" since RFC 4301 says:

"Lifetime of this SA: a time interval after which an SA must be
      replaced with a new SA (and new SPI) or terminated, plus an
      indication of which of these actions should occur."
	 =20
We are realizing that RFC 4301 should also be updated to reflect these =
new possibilities.

In any case, could you elaborate a little bit more about the difference =
between clear and hold and the effect in the kernel? We are assuming =
that affects the SAD.

>=20
> ipsec-traffic-direction:
>=20
> Traditionally, freeswan ony used inbound/outbound and not forward. =
Unfortunately, KAME and Linux/XFRM kept forward there. But I see no use
> case for it in these deployments. We have nothing specified in about =
ipsec-sa's for the forward (it's basically implied "completely open")
> But I understand it might be useful to just specify this because it is =
needed. But perhaps more language is then needed to clarify this?

[Authors] We think this is an implementation aspect. We think it is =
better to remove fwd policy. If fwd policy is required because we have =
an implementation based on Linux, the NETCONF server should install that =
fwd policy based on the in/out received.
>=20
> ipsec-spd-operation:
>=20
> The value BYPASS probably means "let go in the clear" but I don't find =
the name very obvious.

[Authors] It has been extracted from RFC 4301 definition.=20

"Processing info -- which action is required -- PROTECT,
             BYPASS, or DISCARD."
			=20
In relation with our previous comment we think it would be worthy to =
carry out an update in the RFC 4301

> The operation modes BYPASS and DISCARD cannot be configured with the =
current yang parameters
> for IKE? How would this be configured, eg to place a DISCARD for =
192.1.2.0/24 ?

[Authors] It is not needed to configure it in the IKE model since it is =
already configured in the SPD model. The RFC 4301 defines how the SPD is =
composed, and following this, we have defined the SPD model regardless =
whether we are in IKE case or IKEless case. In other words, both cases =
uses the information contained in the SPD model. Having said this, we =
think it would be useful to explicitly "link" each connection in IKEv2 =
with the SPD entries associated to that connection. For example, per =
each connection we could add a list of spd-entry-id, which point to the =
SPD entries associated to that connection. =46rom your comment we have =
realized that this issue is not well explained in the document.

Thus, regardless the case we are using, the policies establishing the =
type of traffic and protection to be applied are indicated in the SPD =
model (i.e. by means of a list of spd-entry). So the SPD model is used =
for both, IKE case and IKE-less case. Thus, we have the following =
situation.=20

- For IKE case, the whole configuration is distributed in two parts. =
While the IKE SA configuration is represented as =E2=80=9Cike-conn-entries=
=E2=80=9D, the the CHILD SA configuration will be found as a list of =
=E2=80=9Cspd-entry=E2=80=9D.=20
- For IKE-less case, only the CHILD SA configuration will be accessible =
as a list of =E2=80=9Cspd-entry=E2=80=9D.

What do you think?



> In libreswan
> we can configure a connection with type=3Dtransport|tunnel|drop|reject =
but that meshes up the
> IPsec Mode with the SPD Operation. It is also a bit odd to configure =
"IKE" for a "DISCARD"
> since it really does not define anything in IKE - it bypasses IKE to =
put in an IPsec policy
> (SPD). But if the yang model used the ipsec parts to do this, it could =
be mixing IKE + manual
> IPsec policies, which could really confuse the IKE daemon. I am not =
sure what the best fix for
> this is. Note REJECT which is DISCARD+ICMP message is not defined =
here. Should it? I don't
> think Linux/XFRM/netlink supports this.

[Authors] As we see it, we are not mixing IKE + manual IPsec policies. =
SPD is the central point of configuration for IPsec policies in the =
model. In any case, we talk about implementation. In particular, when =
the controller configures the SPD first and the IKE model with a =
connection, this connection will have a list of spd-entry-id to refer to =
the particular SPD entries that it has to configure in the IKE daemon =
associated to that connection.  About what is happening with drop / =
reject and the fix we don't really know either but I think this is not a =
problem for the model itself, right? As a note, ip xfrm allows : "allow" =
or "block"=20
>=20
> ipsec-next-layer-proto:
>=20
> See earlier note. I think this is a really bad name.

[Authors] This is defined in RFC 4301 with this name. In ip xfrm is =
UPSPEC.  is Upper Layer Protocol better?
>=20
> ipsec-spd-nam:
>=20
> This is the first time I have seen an SPD as having a name. normally =
these just have numbers. Or they
> have a number that is the link between SPD and SAD (with linux, that =
is called reqid=3D)
> So maybe add an enum id_number so implementors could map this onto the =
linux implementation ?

[Authors] RFC 4301 says explicitly in page 28.

"- Name:  This is not a selector like the others above.  It is not
        acquired from a packet.  A name may be used as a symbolic
        identifier for an IPsec Local or Remote address."
	=09
"An SPD is an ordered list of entries each of which contains the
		   following fields.

		           o Name -- a list of IDs.  This quasi-selector =
is optional.
		             The forms that MUST be supported are =
described above in
		             Section 4.4.1.1 under "Name". =E2=80=9C"


But yes, we can replace this name by other identifier, as you suggest.
>=20
> auth-method-type:
>=20
> See earlier comment about asymmetric authentication.
>=20
> This should only contain pre-shared, null, eap, rsa, rfc7427(digital =
signatures). That is I think dss-signature can be removed.
> I also wonder if this entry needs to have a better difference for the =
source of the private/public keypair, eg raw RSA versus
> RSA certificate based authentication. I guess this is now implied by =
not having a certificate entry?

[Authors] Mmmmm... good question. We think we should include at least a =
"raw public key" leaf so if the leaf is set then we have raw public key. =
If we include certificate then we will have RSA certificate based =
authentication. In any case, if ECC-based signature is required we would =
also need to support ECC public and private keys. In any case, this part =
in the model needs to be udpated to support RFC 7670 and RFC 7427

 There is also another aspect: if eap is chosen, what eap method is =
allowed. I think a container mentioning the EAP method should  be =
included. Moreover, we should include a way to send the credentials for =
the particular EAP method.

>=20
> Also rename description "Peer authentication method" to "IKE =
authentication method" (it should mention this is IKE, but also
> in case of asymmetric use, this is not neccessarilly for the peer but =
how we authenticate _to_ the peer)

[Authors] Sounds reasonable

>=20
> sa-state:  I am not sure why this is needed? Unless someone would want =
to manually place larval/acquire states in the kernel
> without IKE, but then who is going to listen to these ACQUIRE =
messages? A non-IKE daemon? See earlier discussion on this topic.
> If you do want to get netlink/pf_key messages for max-counter, =
max-bytes etc without IKE, then this would be required. Otherwise
> this should be removed.

[Authors] This is precisely what we want: "to get netlink/pf_key =
messages for max-counter, max-bytes etc without IKE" . This is captured =
by the NETCONF server to send notifications to the controller in IKEless =
case. Having said this, most probably this state is not completely =
required though as we mentioned in section 6's comments , the IPsec SA =
appears in the state. It seems too much detail for the regular operation =
of the controller, even considering IKEless case.
>=20
> lifetime: See earlier comments.
>=20
> grouping auth-method-grouping: See earlier comments about asymmetric =
authentication and raw vs cert based signatures. Note based
> on above entries, this is missing a dss-signature section. So if you =
agree with earlier comment to remove dss-signature, then
> it not appearing here is fine.

[Authors] Yes, we are going to remove dss-signature and extend the =
auth-method container to contemplate the use of raw public keys as well =
as generic digital signatures (rfc 7427).
>=20
> grouping identity-grouping:  See earlier comments on ID_NULL / =
AUTH_NULL support

[Authors] We failed to see this earlier comments about ID_NULL and =
AUTH_NULL, could you point us to them?


>=20
> grouping port-range: I don't see anywhere that protocol and ports =
together are "overloaded" for things like ICMP message types.
> Should language be added for that?

[Authors] Not sure what are you are referring here... could you =
elaborate? We have seen that description should be changed as well.
>=20
> SAD and SPD grouping : See earlier note about Security Labels. It =
would need to be added here. Linux/XFRM already supports these.

[Authors] Not sure about this. Right now, the usage of security labels =
seems associated to specific implemenation (Linux/XFRM) and =
https://tools.ietf.org/html/draft-sprasad-ipsecme-labeled-ipsec-00 has =
not been evolved since March 2018 (is it going to be adopted?).
>=20
> I see container-ah and container-esp, but what about container-ipcomp? =
Again, if we remove IPCOMP as I'd like, then we are fine
> here. but if not, then something needs to be added here. If AH is =
removed as I'd recommended, it needs to be removed here.

[Authors] That's right. We think we could remove that ipcomp and ah if =
the WG is agree.
>=20
> 	container sad-lifetime-soft {
>         	description "SAD lifetime hard state data";
>=20
> that "hard" should be "soft=E2=80=9D.

[Authors] Right.
>=20
> I am confused that "hard" and "soft" have an action that can be =
similar. soft could have an action to just notify userland via
> XFRM/PF_key, but "hard" can only have an option "terminate=E2=80=9D ?

[Authors] Your comment makes sense.=20
>=20
> container encap: Now I see the sport / dport, but I'm still confused =
how this is populated from the higher level Security Controller
> communication (if not IKE). Note also the Security Controllers cannot =
know the port numbers without sending any traffic so the
> NAT gateway crates a mapping.

[Authors] As mentioned earlier, this can be informed by the NSF through =
a YANG module related with NAT management.=20
>=20
> list traffic-selector-list: Can a traffic selector have a direction of =
fwd ? Not in the IKE protocol.

[Authors] fwd direction has been removed now.
>=20
>            leaf mode { type ipsec-mode; description =
"transport/tunnel"; }

[Authors] True. We will add them but removing BEET.
>=20
> This "description" does not match all the available options defined =
before.
>=20
> container ah-algorithms: See AH comments before. Also see IPCOMP =
comments before.

[Authors] As mentioned we are in favour of removing AH and IPCOMP if the =
WG agrees on that.

>=20
> 	description "Configure ESP encryption"
>=20
> Maybe say "Configure ESP/AEAD encryption=E2=80=9D

[Authors] This would be applicable if we finally agree that only AEAD =
will be used. But in the last e-mail exchange in the mailing list, it =
looks like we are not limiting us to a case where only AEAD is allowed.=20=

>=20
> spd-mark:
>=20
> Note that the IKE case cannot negotiate this spd-mark value. Is such a =
capability needed? It is similar to negotiating a Security Context.

[Authors] It is in linux kernels and handled by XFRM but we think you're =
right and we could remove it from the model. In any case, do you think =
there is an important example case for its usage?
>=20
>=20
> container spd-lifetime-*: See earlier comments on hard/soft and =
acceptable actions

[Authors] OK.
>=20
> grouping isakmp-proposal: I would call this ike-proposal as isakmp is =
kind of an IKEv1 term. See also phase1-* value suggestions earlier to
> make those ike-* or ike-sa-* values. This group is also missing pfs=3D =
which for IKEv2 only starts to matter when rekeying and whether or not
> to do a new DH.

[Authors] Agree. We will change the name. Also true about pfs. We will =
add this information.

>=20
> grouping phase2-info: Call this ipsec-info: or ipsec-sa-info:

[Authors] Correct. As mentioned we think it would be better if this =
ipsec-sa-info has a lists of spd-entry-id pointing the SPD policies =
associated.
>=20
> 	leaf-list pfs_group { type uint32;


>=20
> This should really be an enum and not a uint32.

[Authors] Ok. We will change it.
>=20
> typedef sadb-msg-type: where/when are these used? That is, I =
understand the IKE <-> IPsec API uses this, but when does this ever need =
to
> go over the Security Controller's communication ?

[Authors] In IKEless, the sadb_acquire notification carries this =
information to the Controller. Basically, what it is happenning is that =
the NETCONF server in the NSF captures the sadb_acquire from the kernel =
and builds a NETCONF notification which is sent to the Controller. =
Having said this, it is true that this is not required anymore since we =
know that this type can be only SADB_ACQUIRE since we are sending a =
sadb_acquire.=20
>=20
> typedef sadb-msg-satype: same here

[Authors] The controller needs to know what IPsec SA should be =
negotiated. We have realized that notificiation sabd_acquire should =
carry the policy that caused the acquire so that the Controller can know =
how to add the IPsec SA. Thus, we propose the following modification to =
the sadb_acquire notification:

notification sadb_acquire {
      description "A IPsec SA is required ";
      uses selector-grouping;
	  container tunnel {
	           when "../mode =3D 'TUNNEL'";
	           uses tunnel-grouping;
	           description "If TUNNEL mode is used the sadb_acquire =
notification carries the endpoints";
	        }
   }
>=20
> container algorithm-supported: See earlier comments about all moderm =
algorithms not having a min/max but only having a limited set, for
> current ones this is only 128/192/256

[Authors] Ok.
>=20
> Note the version of IKE within the ietf-ipsec namespace only has =
IKEv2. I agree with that now but earlier in the document it has IKEv1
> support/entries. So this needs to be made consistent here.
[Authors] Correct. We should only keep ikev2

>=20
> container ike-stats: does not contain encaps entry to show if it is =
using UDP, TCP or TLS and on which port.

[Authors] Are you referrig to the encapsulation of the IKEv2 messages?=20=

>=20
> list child-sas: does not contain some "state" that can be negotiated =
as part of an IKE session. For example, if narrowing was used, it could
> be that the current SPD is more narrow then the "connection" defined =
SPD. There seems to be no way to store this. Thus narrowing is not
> possible. If narrowing is not in scope here, it should probably be =
made more explicit. Otherwise, it needs to be better integrated.

[Authors] Basically, we are including a list of child-sas negotiated. =
Basically, in terms of implementation, as an example, we would provide =
this information with the output, for example, either ip xfrm state list =
or using the list-sa event in strongswan =
(https://www.strongswan.org/apidoc/md_src_libcharon_plugins_vici_README.ht=
ml)
>=20
> container number-ike-sas: See earlier note about missing COOKIES =
parameter here.
>=20
>=20
> SPD related question: Is there support for multiple TSi/TSr generating =
a list of spd's in a single Child SA? If so, a Child SA can have
> multiple SPDs. Otherwise, it cannot. I dont think the model is very =
clear on this aspect. (I speak from experience, libreswan as an
> implementation is also not very clearly specified here, and we have =
one known interop issue with openbsd's iked because of this)

[Authors] So openbsd's iked allows a child SA assocciated to several =
policies, right?=20

Regarding your comment " list of spd's in a single Child SA" . Could you =
ellaborate a little bit more? The model is not clear in this aspect =
since we have not considered this case. Are you referring that a list of =
policies are mapped to the same child SA?. In any case, we think this =
would be part of the implemenation of the ike model. That is: we are =
doing is to inject the SPD entries that have been configured in the SPD =
model in the connections defined in the IKEv2 model into the particular =
IKEv2 implementation. For example we can use VICI in strongswan for =
that. If the IKEv2 implementation is able to associate a list of spd in =
single child SA, should the controller be able to say anything about it? =
Do you think we should add a flag or something for this?
>=20
>=20
> // Those RPCs are needed by a Security Controller in case 2 */
>=20
> Please think about XFRM/netlink and/or ACQUIRE messages that are =
needed if there is no IKE daemon. eg when max-counter is reached
> or when a hard limit action is performed by the kernel.

[Authors] We already have modelled those messages (sadb_acquire is a =
notification)=20

notification sadb_acquire {
      description "A IPsec SA is required ";
      uses base-grouping;
   }

   notification sadb_expire {
      description "A IPsec SA expiration (soft or hard)";
	  ....

>=20
> I am missing an "SPI already in use" error, in the case it is =
attempted to install an SPD that already exists and thus would conflict.
>=20
>=20

[Authors] That will happen when the controller sends an NETCONF =
edit-config trying to add that an already existing SPI. =46rom NETCONF =
rfc  "The <rpc-error> element is sent in <rpc-reply> messages if an =
error
   occurs during the processing of an <rpc> request."

Right now, , the spi value is the key element for the list of SAs in the =
model for this case, so the NETCONF server will detect it is already =
used. If it is already used the NETCONF server considers the SC wants to =
"update" de SA, but not to add a new one.=20
  =20
It is true that we have NOT defined any explicit "error-message" for =
this rpc-error. We will add this.

Best Regards.

-------------------------------------------------------
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=_C27FF821-CD48-4BF8-A1FE-34A3663B504C
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 =
Paul, all:<div class=3D""><br class=3D""></div><div class=3D""><div><br =
class=3D""><blockquote type=3D"cite" class=3D""><div class=3D""><br =
class=3D""></div><div class=3D""><div class=3D"">Appendix A:<br =
class=3D""><br class=3D"">Why is it "eipsec" and not "ipsec=E2=80=9D =
?<br class=3D""></div></div></blockquote><div><br =
class=3D""></div>[Authors] We have fixed this now.<br =
class=3D""><blockquote type=3D"cite" class=3D""><div class=3D""><div =
class=3D""><br class=3D"">Why is the organization not the IETF? Is this =
commonly done for yang models?<br =
class=3D""></div></div></blockquote><div><br =
class=3D""></div><div>[Authors] You're right. We will change this =
to:</div><div><br class=3D""></div><div>"IETF I2NSF (Interface to =
Network Security Functions) Working Group"</div><blockquote type=3D"cite" =
class=3D""><div class=3D""><div class=3D""><br =
class=3D"">encryption-algorithm-t - I think this should only list the =
MUST/SOULD items, so AES_GCM (1 flavour), AES_CCM (1 flavour) =
CHACHAPOLY1305 and NULL<br class=3D""><br class=3D""><span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</span>description "Encryption algorithms -&amp;gt; RFC_5996=E2=80=9D;<br =
class=3D""></div></div></blockquote><div><br =
class=3D""></div><div>[Authors] Right. Our doubt here is if we should =
refer instead to&nbsp;</div><div><br class=3D""></div><div><a =
href=3D"https://tools.ietf.org/html/draft-ietf-netconf-crypto-types-02" =
class=3D"">https://tools.ietf.org/html/draft-ietf-netconf-crypto-types-02<=
/a></div><div><br class=3D""></div><div>such as&nbsp;</div><div><br =
class=3D""></div><div><a =
href=3D"https://tools.ietf.org/html/draft-ietf-netconf-tls-client-server-0=
8" =
class=3D"">https://tools.ietf.org/html/draft-ietf-netconf-tls-client-serve=
r-08</a></div><div><br class=3D""></div><div>is doing. If you check this =
link you will notice is referring to&nbsp;</div><div><br =
class=3D""></div><div>&lt;algorithm =
xmlns:ct=3D"urn:ietf:params:xml:ns:yang:ietf-crypto-t\</div><div>&nbsp; =
&nbsp;ypes"&gt;ct:rsa2048&lt;/algorithm&gt;</div><div>&nbsp; =
&nbsp;</div><div>which is referring to ietf-crypto-types</div><div =
class=3D""><br class=3D""></div><blockquote type=3D"cite" class=3D""><div =
class=3D""><div class=3D""><br class=3D"">RFC 5996 is an obsolete =
reference. It should either refer to RFC 7296, or it should simply refer =
to the IANA registry involved.<br =
class=3D""></div></div></blockquote><div><br class=3D""></div>[Authors] =
OK.<br class=3D""><blockquote type=3D"cite" class=3D""><div =
class=3D""><div class=3D""><br class=3D"">integrity-algorithm-t: If the =
above is agreed, this enumeration should only contain "none" and the =
entries from aes-cmac-96 and up. That is,<br class=3D"">not contain =
des,md5,sha1 and aes_xcbc. &nbsp;Same obsolete reference is used here in =
the description.<br class=3D""></div></div></blockquote><div><br =
class=3D""></div>[Authors] Ok.</div><div><br class=3D""><blockquote =
type=3D"cite" class=3D""><div class=3D""><div class=3D""><br =
class=3D"">type-autostartup: Maybe instead of RESPOND-ONLY, a better =
word is "STANDBY"? That way, the node could decide itself to bring a =
connection up<br class=3D"">without _requiring_ a remote signal, and =
could be triggered locally as as well as remotely to come up.<br =
class=3D""></div></div></blockquote><div><br class=3D""></div>[Authors] =
Sounds reasonable. We should provide a better description of each value =
as well.</div><div><br class=3D""><blockquote type=3D"cite" =
class=3D""><div class=3D""><div class=3D""><br class=3D""> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;description "Different types of how IKEv2 =
starts the IPsec SAs";<br class=3D""><br class=3D"">I would say =
"different policies of when to start an IKEv2 based IPsec SA". Does it =
need clarification this value is ignored or unused for the<br =
class=3D"">"case 2" scenario?<br =
class=3D""></div></div></blockquote><div><br class=3D""></div>[Authors] =
This typedef is not used in the part of the model associated to case 2 =
but we can something in the description.&nbsp;<br class=3D""><blockquote =
type=3D"cite" class=3D""><div class=3D""><div class=3D""><br =
class=3D"">auth-protocol-type: &nbsp;This should only contain IKEv2. The =
enum should remain in case we get IKEv2.1 or IKEv3 in the future.<br =
class=3D""></div></div></blockquote><div><br class=3D""></div>[Author] =
Agree.</div><div><br class=3D""><blockquote type=3D"cite" class=3D""><div =
class=3D""><div class=3D""><br class=3D""> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;description "Peer authentication =
protocols=E2=80=9D;</div></div></blockquote><blockquote type=3D"cite" =
class=3D""><div class=3D""><div class=3D""><br class=3D"">I would say =
"IKE authentication protocol version", unless you want to keep the =
option open to have a non-IKE protocol. But I think that would<br =
class=3D"">run into many more issues of having parameters that are not =
defined for IKE?<br class=3D""></div></div></blockquote><div><br =
class=3D""></div>[Author] Agree.<br class=3D""><blockquote type=3D"cite" =
class=3D""><div class=3D""><div class=3D""><br class=3D"">ipsec-mode: It =
should only contain Tunnel and Transport Mode. It would be nice to see =
some text that forbids using Transport Mode when NAT is<br =
class=3D"">requested, just to avoid a lot of problems and =
disappointments. L2TP/IPsec still has major scars due to its use of =
Transport Mode with NAT.<br class=3D""></div></div></blockquote><div><br =
class=3D""></div>[Authors] Sounds reasonable.</div><div><br =
class=3D""><blockquote type=3D"cite" class=3D""><div class=3D""><div =
class=3D""><br class=3D"">esp-encap: as stated before, we are missing =
the port entry. I can also image that multiple encaps could be allowed, =
such as TCP-443 and TLS-443.<br class=3D"">Also note that the RFC for =
ESP over TCP recommends to continiously check if UDP encapsulation has =
become available, since it is so much prefered<br class=3D"">over TCP. =
But that only makes sense when the remote is a roaming client, and makes =
less sense if the network consists of data centers.<br =
class=3D""></div></div></blockquote><div><br class=3D""></div>[Authors] =
Ok. Let's add the port entry. In any case, I believe that is something =
that implementation in the NSF (in particular the NETCONF server) could =
check (UDP encapsulation)</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"">ipsec-protocol: I think this should only =
contain esp. See earlier comments. Notably, if supporting ipcomp here, =
the yang model must be clear<br class=3D"">that it could need an ipcomp =
+ esp IPsec SA for a single 'connection'. Even if we only leave esp as a =
valid option, keep this enum in case<br class=3D"">we come up with a new =
esp version of some esp-lite version.<br =
class=3D""></div></div></blockquote><div><br class=3D""></div>[Authors] =
We are in favour on leaving only ESP. If the WG agrees, let's proceed =
that way.</div><div><br class=3D""><blockquote type=3D"cite" =
class=3D""><div class=3D""><div class=3D""><br class=3D"">lifetime-action =
only has "terminate" and "rekey". For libreswan we use "clear", "hold" =
and "restart". The difference<br class=3D"">between clear and hold is =
what kernel policy to install for cleartext packets. For roadwarrionrs =
coming in, you<br class=3D"">want clear to leave no trace. for a =
site-to-site VPN you generally want "hold" to ensure you drop all =
packets until<br class=3D"">a new tunnel is established (possible =
ondemand, so this is different from restart)<br =
class=3D""></div></div></blockquote><div>[Authors] Basically we have =
"terminate" and "rekey" since RFC 4301 says:</div><div><br =
class=3D""></div><div>"Lifetime of this SA: a time interval after which =
an SA must be</div><div>&nbsp; &nbsp; &nbsp; replaced with a new SA (and =
new SPI) or terminated, plus an</div><div>&nbsp; &nbsp; &nbsp; =
indication of which of these actions should occur."</div><div><span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</span> =
&nbsp;</div><div>We are realizing that RFC 4301 should also be updated =
to reflect these new possibilities.</div><div><br class=3D""></div><div>In=
 any case, could you elaborate a little bit more about the difference =
between clear and hold and the effect in the kernel? We are assuming =
that affects the SAD.</div><div class=3D""><br =
class=3D""></div><blockquote type=3D"cite" class=3D""><div class=3D""><div=
 class=3D""><br class=3D"">ipsec-traffic-direction:<br class=3D""><br =
class=3D"">Traditionally, freeswan ony used inbound/outbound and not =
forward. Unfortunately, KAME and Linux/XFRM kept forward there. But I =
see no use<br class=3D"">case for it in these deployments. We have =
nothing specified in about ipsec-sa's for the forward (it's basically =
implied "completely open")<br class=3D"">But I understand it might be =
useful to just specify this because it is needed. But perhaps more =
language is then needed to clarify this?<br =
class=3D""></div></div></blockquote><div><br class=3D""></div>[Authors] =
We think this is an implementation aspect. We think it is better to =
remove fwd policy. If fwd policy is required because we have an =
implementation based on Linux, the NETCONF server should install that =
fwd policy based on the in/out received.<br class=3D""><blockquote =
type=3D"cite" class=3D""><div class=3D""><div class=3D""><br =
class=3D"">ipsec-spd-operation:<br class=3D""><br class=3D"">The value =
BYPASS probably means "let go in the clear" but I don't find the name =
very obvious.<br class=3D""></div></div></blockquote><div><br =
class=3D""></div><div>[Authors] It has been extracted from RFC 4301 =
definition.&nbsp;</div><div><br class=3D""></div><div>"Processing info =
-- which action is required -- PROTECT,</div><div>&nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp;BYPASS, or DISCARD."</div><div><span =
class=3D"Apple-tab-span" style=3D"white-space:pre">			=
</span>&nbsp;</div><div>In relation with our previous comment we think =
it would be worthy to carry out an update in the RFC 4301</div><div =
class=3D""><br class=3D""></div><blockquote type=3D"cite" class=3D""><div =
class=3D""><div class=3D"">The operation modes BYPASS and DISCARD cannot =
be configured with the current yang parameters<br class=3D"">for IKE? =
How would this be configured, eg to place a DISCARD for 192.1.2.0/24 ? =
</div></div></blockquote><div><br class=3D""></div><div><div>[Authors] =
It is not needed to configure it in the IKE model since it is already =
configured in the SPD model. The RFC 4301 defines how the SPD is =
composed, and following this, we have defined the SPD model regardless =
whether we are in IKE case or IKEless case. In other words, both cases =
uses the information contained in the SPD model. Having said this, we =
think it would be useful to explicitly "link" each connection in IKEv2 =
with the SPD entries associated to that connection. For example, per =
each connection we could add a list of spd-entry-id, which point to the =
SPD entries associated to that connection. =46rom your comment we have =
realized that this issue is not well explained in the =
document.</div><div><br class=3D""></div><div>Thus, regardless the case =
we are using, the policies establishing the type of traffic and =
protection to be applied are indicated in the SPD model (i.e. by means =
of a list of spd-entry). So the SPD model is used for both, IKE case and =
IKE-less case. Thus, we have the following =
situation.&nbsp;</div><div><br class=3D""></div><div>- For IKE case, the =
whole configuration is distributed in two parts. While the IKE SA =
configuration is represented as =E2=80=9Cike-conn-entries=E2=80=9D, the =
the CHILD SA configuration will be found as a list of =
=E2=80=9Cspd-entry=E2=80=9D.&nbsp;</div><div>- For IKE-less case, only =
the CHILD SA configuration will be accessible as a list of =
=E2=80=9Cspd-entry=E2=80=9D.</div><div><br class=3D""></div><div>What do =
you think?</div><div class=3D""><br class=3D""></div></div><div><br =
class=3D""></div><br class=3D""><blockquote type=3D"cite" class=3D""><div =
class=3D""><div class=3D"">In libreswan<br class=3D"">we can configure a =
connection with type=3Dtransport|tunnel|drop|reject but that meshes up =
the<br class=3D"">IPsec Mode with the SPD Operation. It is also a bit =
odd to configure "IKE" for a "DISCARD"<br class=3D"">since it really =
does not define anything in IKE - it bypasses IKE to put in an IPsec =
policy<br class=3D"">(SPD). But if the yang model used the ipsec parts =
to do this, it could be mixing IKE + manual<br class=3D"">IPsec =
policies, which could really confuse the IKE daemon. I am not sure what =
the best fix for<br class=3D"">this is. Note REJECT which is =
DISCARD+ICMP message is not defined here. Should it? I don't<br =
class=3D"">think Linux/XFRM/netlink supports this.<br =
class=3D""></div></div></blockquote><div><br class=3D""></div>[Authors] =
As we see it, we are not mixing IKE + manual IPsec policies. SPD is the =
central point of configuration for IPsec policies in the model. In any =
case, we talk about implementation. In particular, when the controller =
configures the SPD first and the IKE model with a connection, this =
connection will have a list of spd-entry-id to refer to the particular =
SPD entries that it has to configure in the IKE daemon associated to =
that connection. &nbsp;About what is happening with drop / reject and =
the fix we don't really know either but I think this is not a problem =
for the model itself, right? As a note, ip xfrm allows : "allow" or =
"block"&nbsp;<br class=3D""><blockquote type=3D"cite" class=3D""><div =
class=3D""><div class=3D""><br class=3D"">ipsec-next-layer-proto:<br =
class=3D""><br class=3D"">See earlier note. I think this is a really bad =
name.<br class=3D""></div></div></blockquote><div><br =
class=3D""></div>[Authors] This is defined in RFC 4301 with this name. =
In ip xfrm is UPSPEC. &nbsp;is Upper Layer Protocol better?<br =
class=3D""><blockquote type=3D"cite" class=3D""><div class=3D""><div =
class=3D""><br class=3D"">ipsec-spd-nam:<br class=3D""><br class=3D"">This=
 is the first time I have seen an SPD as having a name. normally these =
just have numbers. Or they<br class=3D"">have a number that is the link =
between SPD and SAD (with linux, that is called reqid=3D)<br class=3D"">So=
 maybe add an enum id_number so implementors could map this onto the =
linux implementation ?<br class=3D""></div></div></blockquote><div><br =
class=3D""></div><div>[Authors] RFC 4301 says explicitly in page =
28.</div><div><br class=3D""></div><div>"- Name: &nbsp;This is not a =
selector like the others above. &nbsp;It is not</div><div>&nbsp; &nbsp; =
&nbsp; &nbsp; acquired from a packet. &nbsp;A name may be used as a =
symbolic</div><div>&nbsp; &nbsp; &nbsp; &nbsp; identifier for an IPsec =
Local or Remote address."</div><div><span class=3D"Apple-tab-span" =
style=3D"white-space:pre">		</span></div><div>"An SPD is an =
ordered list of entries each of which contains the</div><div><span =
class=3D"Apple-tab-span" style=3D"white-space:pre">		</span> =
&nbsp; following fields.</div><div><br class=3D""></div><div><span =
class=3D"Apple-tab-span" style=3D"white-space:pre">		</span> =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; o Name -- a list of IDs. &nbsp;This =
quasi-selector is optional.</div><div><span class=3D"Apple-tab-span" =
style=3D"white-space:pre">		</span> &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; The forms that MUST be supported are described =
above in</div><div><span class=3D"Apple-tab-span" =
style=3D"white-space:pre">		</span> &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; Section 4.4.1.1 under "Name". =E2=80=9C"</div><div><b=
r class=3D""></div><div><br class=3D""></div><div>But yes, we can =
replace this name by other identifier, as you suggest.</div><blockquote =
type=3D"cite" class=3D""><div class=3D""><div class=3D""><br =
class=3D"">auth-method-type:<br class=3D""><br class=3D"">See earlier =
comment about asymmetric authentication.<br class=3D""><br class=3D"">This=
 should only contain pre-shared, null, eap, rsa, rfc7427(digital =
signatures). That is I think dss-signature can be removed.<br class=3D"">I=
 also wonder if this entry needs to have a better difference for the =
source of the private/public keypair, eg raw RSA versus<br class=3D"">RSA =
certificate based authentication. I guess this is now implied by not =
having a certificate entry?<br =
class=3D""></div></div></blockquote><div><br =
class=3D""></div><div>[Authors] Mmmmm... good question. We think we =
should include at least a "raw public key" leaf so if the leaf is set =
then we have raw public key. If we include certificate then we will have =
RSA certificate based authentication. In any case, if ECC-based =
signature is required we would also need to support ECC public and =
private keys. In any case, this part in the model needs to be udpated to =
support RFC 7670 and RFC 7427</div><div><br =
class=3D""></div><div>&nbsp;There is also another aspect: if eap is =
chosen, what eap method is allowed. I think a container mentioning the =
EAP method should &nbsp;be included. Moreover, we should include a way =
to send the credentials for the particular EAP method.</div><div><br =
class=3D""></div><blockquote type=3D"cite" class=3D""><div class=3D""><div=
 class=3D""><br class=3D"">Also rename description "Peer authentication =
method" to "IKE authentication method" (it should mention this is IKE, =
but also<br class=3D"">in case of asymmetric use, this is not =
neccessarilly for the peer but how we authenticate _to_ the peer)<br =
class=3D""></div></div></blockquote><div><br class=3D""></div>[Authors] =
Sounds reasonable</div><div><br class=3D""><blockquote type=3D"cite" =
class=3D""><div class=3D""><div class=3D""><br class=3D"">sa-state: =
&nbsp;I am not sure why this is needed? Unless someone would want to =
manually place larval/acquire states in the kernel<br class=3D"">without =
IKE, but then who is going to listen to these ACQUIRE messages? A =
non-IKE daemon? See earlier discussion on this topic.<br class=3D"">If =
you do want to get netlink/pf_key messages for max-counter, max-bytes =
etc without IKE, then this would be required. Otherwise<br class=3D"">this=
 should be removed.<br class=3D""></div></div></blockquote><div><br =
class=3D""></div>[Authors] This is precisely what we want: "to get =
netlink/pf_key messages for max-counter, max-bytes etc without IKE" . =
This is captured by the NETCONF server to send notifications to the =
controller in IKEless case. Having said this, most probably this state =
is not completely required though as we mentioned in section 6's =
comments , the IPsec SA appears in the state. It seems too much detail =
for the regular operation of the controller, even considering IKEless =
case.<br class=3D""><blockquote type=3D"cite" class=3D""><div =
class=3D""><div class=3D""><br class=3D"">lifetime: See earlier =
comments.<br class=3D""><br class=3D"">grouping auth-method-grouping: =
See earlier comments about asymmetric authentication and raw vs cert =
based signatures. Note based<br class=3D"">on above entries, this is =
missing a dss-signature section. So if you agree with earlier comment to =
remove dss-signature, then<br class=3D"">it not appearing here is =
fine.<br class=3D""></div></div></blockquote><div><br =
class=3D""></div>[Authors] Yes, we are going to remove dss-signature and =
extend the auth-method container to contemplate the use of raw public =
keys as well as generic digital signatures (rfc 7427).<br =
class=3D""><blockquote type=3D"cite" class=3D""><div class=3D""><div =
class=3D""><br class=3D"">grouping identity-grouping: &nbsp;See earlier =
comments on ID_NULL / AUTH_NULL support<br =
class=3D""></div></div></blockquote><div><br class=3D""></div>[Authors] =
We failed to see this earlier comments about ID_NULL and AUTH_NULL, =
could you point us to them?</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"">grouping port-range: I don't see anywhere that =
protocol and ports together are "overloaded" for things like ICMP =
message types.<br class=3D"">Should language be added for that?<br =
class=3D""></div></div></blockquote><div><br class=3D""></div>[Authors] =
Not sure what are you are referring here... could you elaborate? We have =
seen that description should be changed as well.<br class=3D""><blockquote=
 type=3D"cite" class=3D""><div class=3D""><div class=3D""><br =
class=3D"">SAD and SPD grouping : See earlier note about Security =
Labels. It would need to be added here. Linux/XFRM already supports =
these.<br class=3D""></div></div></blockquote><div><br =
class=3D""></div>[Authors] Not sure about this. Right now, the usage of =
security labels seems associated to specific implemenation (Linux/XFRM) =
and <a =
href=3D"https://tools.ietf.org/html/draft-sprasad-ipsecme-labeled-ipsec-00=
" =
class=3D"">https://tools.ietf.org/html/draft-sprasad-ipsecme-labeled-ipsec=
-00</a> has not been evolved since March 2018 (is it going to be =
adopted?).<br class=3D""><blockquote type=3D"cite" class=3D""><div =
class=3D""><div class=3D""><br class=3D"">I see container-ah and =
container-esp, but what about container-ipcomp? Again, if we remove =
IPCOMP as I'd like, then we are fine<br class=3D"">here. but if not, =
then something needs to be added here. If AH is removed as I'd =
recommended, it needs to be removed here.<br =
class=3D""></div></div></blockquote><div><br class=3D""></div>[Authors] =
That's right. We think we could remove that ipcomp and ah if the WG is =
agree.<br class=3D""><blockquote type=3D"cite" class=3D""><div =
class=3D""><div class=3D""><br class=3D""><span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</span>container sad-lifetime-soft {<br =
class=3D""> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</span>description "SAD lifetime hard state data";<br class=3D""><br =
class=3D"">that "hard" should be "soft=E2=80=9D.<br =
class=3D""></div></div></blockquote><div><br class=3D""></div>[Authors] =
Right.<br class=3D""><blockquote type=3D"cite" class=3D""><div =
class=3D""><div class=3D""><br class=3D"">I am confused that "hard" and =
"soft" have an action that can be similar. soft could have an action to =
just notify userland via<br class=3D"">XFRM/PF_key, but "hard" can only =
have an option "terminate=E2=80=9D ?<br =
class=3D""></div></div></blockquote><div><br class=3D""></div>[Authors] =
Your comment makes sense.&nbsp;<br class=3D""><blockquote type=3D"cite" =
class=3D""><div class=3D""><div class=3D""><br class=3D"">container =
encap: Now I see the sport / dport, but I'm still confused how this is =
populated from the higher level Security Controller<br =
class=3D"">communication (if not IKE). Note also the Security =
Controllers cannot know the port numbers without sending any traffic so =
the<br class=3D"">NAT gateway crates a mapping.<br =
class=3D""></div></div></blockquote><div><br class=3D""></div>[Authors] =
As mentioned earlier, this can be informed by the NSF through a YANG =
module related with NAT management.&nbsp;<br class=3D""><blockquote =
type=3D"cite" class=3D""><div class=3D""><div class=3D""><br =
class=3D"">list traffic-selector-list: Can a traffic selector have a =
direction of fwd ? Not in the IKE protocol.<br =
class=3D""></div></div></blockquote><div><br class=3D""></div>[Authors] =
fwd direction has been removed now.<br class=3D""><blockquote =
type=3D"cite" class=3D""><div class=3D""><div class=3D""><br class=3D""> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;leaf =
mode { type ipsec-mode; description "transport/tunnel"; }<br =
class=3D""></div></div></blockquote><div><br class=3D""></div>[Authors] =
True. We will add them but removing BEET.<br class=3D""><blockquote =
type=3D"cite" class=3D""><div class=3D""><div class=3D""><br =
class=3D"">This "description" does not match all the available options =
defined before.<br class=3D""><br class=3D"">container ah-algorithms: =
See AH comments before. Also see IPCOMP comments before.<br =
class=3D""></div></div></blockquote><div><br class=3D""></div>[Authors] =
As mentioned we are in favour of removing AH and IPCOMP if the WG agrees =
on that.</div><div><br class=3D""><blockquote type=3D"cite" =
class=3D""><div class=3D""><div class=3D""><br class=3D""><span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</span>description "Configure ESP encryption"<br class=3D""><br =
class=3D"">Maybe say "Configure ESP/AEAD =
encryption=E2=80=9D</div></div></blockquote><div><br =
class=3D""></div>[Authors] This would be applicable if we finally agree =
that only AEAD will be used. But in the last e-mail exchange in the =
mailing list, it looks like we are not limiting us to a case where only =
AEAD is allowed.&nbsp;<br class=3D""><blockquote type=3D"cite" =
class=3D""><div class=3D""><div class=3D""><br class=3D"">spd-mark:<br =
class=3D""><br class=3D"">Note that the IKE case cannot negotiate this =
spd-mark value. Is such a capability needed? It is similar to =
negotiating a Security Context.<br =
class=3D""></div></div></blockquote><div><br class=3D""></div>[Authors] =
It is in linux kernels and handled by XFRM but we think you're right and =
we could remove it from the model. In any case, do you think there is an =
important example case for its usage?<br class=3D""><blockquote =
type=3D"cite" class=3D""><div class=3D""><div class=3D""><br =
class=3D""><br class=3D"">container spd-lifetime-*: See earlier comments =
on hard/soft and acceptable actions<br =
class=3D""></div></div></blockquote><div><br class=3D""></div>[Authors] =
OK.<br class=3D""><blockquote type=3D"cite" class=3D""><div =
class=3D""><div class=3D""><br class=3D"">grouping isakmp-proposal: I =
would call this ike-proposal as isakmp is kind of an IKEv1 term. See =
also phase1-* value suggestions earlier to<br class=3D"">make those =
ike-* or ike-sa-* values. This group is also missing pfs=3D which for =
IKEv2 only starts to matter when rekeying and whether or not<br =
class=3D"">to do a new DH.<br class=3D""></div></div></blockquote><div><br=
 class=3D""></div>[Authors] Agree. We will change the name. Also true =
about pfs. We will add this information.</div><div><br =
class=3D""><blockquote type=3D"cite" class=3D""><div class=3D""><div =
class=3D""><br class=3D"">grouping phase2-info: Call this ipsec-info: or =
ipsec-sa-info:<br class=3D""></div></div></blockquote><div><br =
class=3D""></div>[Authors] Correct. As mentioned we think it would be =
better if this ipsec-sa-info has a lists of spd-entry-id pointing the =
SPD policies associated.<br class=3D""><blockquote type=3D"cite" =
class=3D""><div class=3D""><div class=3D""><br class=3D""><span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</span>leaf-list =
pfs_group { type uint32;<br class=3D""></div></div></blockquote><div><br =
class=3D""></div><br class=3D""><blockquote type=3D"cite" class=3D""><div =
class=3D""><div class=3D""><br class=3D"">This should really be an enum =
and not a uint32.<br class=3D""></div></div></blockquote><div><br =
class=3D""></div>[Authors] Ok. We will change it.<br =
class=3D""><blockquote type=3D"cite" class=3D""><div class=3D""><div =
class=3D""><br class=3D"">typedef sadb-msg-type: where/when are these =
used? That is, I understand the IKE &lt;-&gt; IPsec API uses this, but =
when does this ever need to<br class=3D"">go over the Security =
Controller's communication ?<br =
class=3D""></div></div></blockquote><div><br class=3D""></div>[Authors] =
In IKEless, the sadb_acquire notification carries this information to =
the Controller. Basically, what it is happenning is that the NETCONF =
server in the NSF captures the sadb_acquire from the kernel and builds a =
NETCONF notification which is sent to the Controller. Having said this, =
it is true that this is not required anymore since we know that this =
type can be only SADB_ACQUIRE since we are sending a =
sadb_acquire.&nbsp;<br class=3D""><blockquote type=3D"cite" =
class=3D""><div class=3D""><div class=3D""><br class=3D"">typedef =
sadb-msg-satype: same here<br class=3D""></div></div></blockquote><div><br=
 class=3D""></div><div>[Authors] The controller needs to know what IPsec =
SA should be negotiated. We have realized that notificiation =
sabd_acquire should carry the policy that caused the acquire so that the =
Controller can know how to add the IPsec SA. Thus, we propose the =
following modification to the sadb_acquire notification:</div><div><br =
class=3D""></div><div>notification sadb_acquire {</div><div>&nbsp; =
&nbsp; &nbsp; description "A IPsec SA is required ";</div><div>&nbsp; =
&nbsp; &nbsp; uses selector-grouping;</div><div><span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</span> =
&nbsp;container tunnel {</div><div><span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</span> &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; when "../mode =3D 'TUNNEL'";</div><div><span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</span> &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; uses tunnel-grouping;</div><div><span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</span> &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; description "If TUNNEL mode is used the =
sadb_acquire notification carries the endpoints";</div><div><span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</span> &nbsp; =
&nbsp; &nbsp; &nbsp;}</div><div>&nbsp; &nbsp;}</div><blockquote =
type=3D"cite" class=3D""><div class=3D""><div class=3D""><br =
class=3D"">container algorithm-supported: See earlier comments about all =
moderm algorithms not having a min/max but only having a limited set, =
for<br class=3D"">current ones this is only 128/192/256<br =
class=3D""></div></div></blockquote><div><br class=3D""></div>[Authors] =
Ok.<br class=3D""><blockquote type=3D"cite" class=3D""><div =
class=3D""><div class=3D""><br class=3D"">Note the version of IKE within =
the ietf-ipsec namespace only has IKEv2. I agree with that now but =
earlier in the document it has IKEv1<br class=3D"">support/entries. So =
this needs to be made consistent here.<br =
class=3D""></div></div></blockquote>[Authors] Correct. We should only =
keep ikev2</div><div><br class=3D""><blockquote type=3D"cite" =
class=3D""><div class=3D""><div class=3D""><br class=3D"">container =
ike-stats: does not contain encaps entry to show if it is using UDP, TCP =
or TLS and on which port.<br class=3D""></div></div></blockquote><div><br =
class=3D""></div>[Authors] Are you referrig to the encapsulation of the =
IKEv2 messages?&nbsp;<br class=3D""><blockquote type=3D"cite" =
class=3D""><div class=3D""><div class=3D""><br class=3D"">list =
child-sas: does not contain some "state" that can be negotiated as part =
of an IKE session. For example, if narrowing was used, it could<br =
class=3D"">be that the current SPD is more narrow then the "connection" =
defined SPD. There seems to be no way to store this. Thus narrowing is =
not<br class=3D"">possible. If narrowing is not in scope here, it should =
probably be made more explicit. Otherwise, it needs to be better =
integrated.<br class=3D""></div></div></blockquote><div><br =
class=3D""></div>[Authors] Basically, we are including a list of =
child-sas negotiated. Basically, in terms of implementation, as an =
example, we would provide this information with the output, for example, =
either ip xfrm state list or using the list-sa event in strongswan (<a =
href=3D"https://www.strongswan.org/apidoc/md_src_libcharon_plugins_vici_RE=
ADME.html" =
class=3D"">https://www.strongswan.org/apidoc/md_src_libcharon_plugins_vici=
_README.html</a>)<br class=3D""><blockquote type=3D"cite" class=3D""><div =
class=3D""><div class=3D""><br class=3D"">container number-ike-sas: See =
earlier note about missing COOKIES parameter here.<br class=3D""><br =
class=3D""><br class=3D"">SPD related question: Is there support for =
multiple TSi/TSr generating a list of spd's in a single Child SA? If so, =
a Child SA can have<br class=3D"">multiple SPDs. Otherwise, it cannot. I =
dont think the model is very clear on this aspect. (I speak from =
experience, libreswan as an<br class=3D"">implementation is also not =
very clearly specified here, and we have one known interop issue with =
openbsd's iked because of this)<br =
class=3D""></div></div></blockquote><div><br class=3D""></div>[Authors] =
So openbsd's iked allows a child SA assocciated to several policies, =
right?&nbsp;</div><div><br class=3D""></div><div>Regarding your comment =
" list of spd's in a single Child SA" . Could you ellaborate a little =
bit more? The model is not clear in this aspect since we have not =
considered this case. Are you referring that a list of policies are =
mapped to the same child SA?. In any case, we think this would be part =
of the implemenation of the ike model. That is: we are doing is to =
inject the SPD entries that have been configured in the SPD model in the =
connections defined in the IKEv2 model into the particular IKEv2 =
implementation. For example we can use VICI in strongswan for that. If =
the IKEv2 implementation is able to associate a list of spd in single =
child SA, should the controller be able to say anything about it? Do you =
think we should add a flag or something for this?<br =
class=3D""><blockquote type=3D"cite" class=3D""><div class=3D""><div =
class=3D""><br class=3D""><br class=3D"">// Those RPCs are needed by a =
Security Controller in case 2 */<br class=3D""><br class=3D"">Please =
think about XFRM/netlink and/or ACQUIRE messages that are needed if =
there is no IKE daemon. eg when max-counter is reached<br class=3D"">or =
when a hard limit action is performed by the kernel.<br =
class=3D""></div></div></blockquote><div><br class=3D""></div>[Authors] =
We already have modelled those messages (sadb_acquire is a =
notification)&nbsp;</div><div><br class=3D""></div><div><div>notification =
sadb_acquire {</div><div>&nbsp; &nbsp; &nbsp; description "A IPsec SA is =
required ";</div><div>&nbsp; &nbsp; &nbsp; uses =
base-grouping;</div><div>&nbsp; &nbsp;}</div><div><br =
class=3D""></div><div>&nbsp; &nbsp;notification sadb_expire =
{</div><div>&nbsp; &nbsp; &nbsp; description "A IPsec SA expiration =
(soft or hard)";</div><div><span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</span> &nbsp;....</div><div =
class=3D""><br class=3D""></div><blockquote type=3D"cite" class=3D""><div =
class=3D""><div class=3D""><br class=3D"">I am missing an "SPI already =
in use" error, in the case it is attempted to install an SPD that =
already exists and thus would conflict.<br class=3D""><br class=3D""><br =
class=3D""></div></div></blockquote><div><br =
class=3D""></div><div><div>[Authors] That will happen when the =
controller sends an NETCONF edit-config trying to add that an already =
existing SPI. =46rom NETCONF rfc &nbsp;"The &lt;rpc-error&gt; element is =
sent in &lt;rpc-reply&gt; messages if an error</div><div>&nbsp; =
&nbsp;occurs during the processing of an &lt;rpc&gt; =
request."</div><div><br class=3D""></div><div>Right now, , the spi value =
is the key element for the list of SAs in the model for this case, so =
the NETCONF server will detect it is already used. If it is already used =
the NETCONF server considers the SC wants to "update" de SA, but not to =
add a new one.&nbsp;</div><div>&nbsp; &nbsp;</div><div>It is true that =
we have NOT defined any explicit "error-message" for this rpc-error. We =
will add this.</div><div class=3D""><br class=3D""></div></div></div>Best =
Regards.</div><div class=3D""><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=_C27FF821-CD48-4BF8-A1FE-34A3663B504C--


From nobody Tue Dec 11 08:12:28 2018
Return-Path: <linda.dunbar@huawei.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 3BFD4130E1D; Tue, 11 Dec 2018 08:12:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level: 
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-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 R0wnMgXYnfLk; Tue, 11 Dec 2018 08:12:18 -0800 (PST)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (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 F0EB1124C04; Tue, 11 Dec 2018 08:12:17 -0800 (PST)
Received: from LHREML711-CAH.china.huawei.com (unknown [172.18.7.108]) by Forcepoint Email with ESMTP id 1393FCFAB13A1; Tue, 11 Dec 2018 16:12:13 +0000 (GMT)
Received: from lhreml709-chm.china.huawei.com (10.201.108.58) by LHREML711-CAH.china.huawei.com (10.201.108.34) with Microsoft SMTP Server (TLS) id 14.3.408.0; Tue, 11 Dec 2018 16:12:14 +0000
Received: from lhreml709-chm.china.huawei.com (10.201.108.58) by lhreml709-chm.china.huawei.com (10.201.108.58) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1591.10; Tue, 11 Dec 2018 16:12:15 +0000
Received: from SJCEML703-CHM.china.huawei.com (10.208.112.39) by lhreml709-chm.china.huawei.com (10.201.108.58) with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA_P256) id 15.1.1591.10 via Frontend Transport; Tue, 11 Dec 2018 16:12:14 +0000
Received: from SJCEML521-MBS.china.huawei.com ([169.254.2.185]) by SJCEML703-CHM.china.huawei.com ([169.254.5.67]) with mapi id 14.03.0415.000; Tue, 11 Dec 2018 08:12:11 -0800
From: Linda Dunbar <linda.dunbar@huawei.com>
To: tom petch <ietfc@btconnect.com>, "opsawg@ietf.org" <opsawg@ietf.org>, "draft-hong-i2nsf-nsf-monitoring-data-model@ietf.org" <draft-hong-i2nsf-nsf-monitoring-data-model@ietf.org>
CC: "i2nsf@ietf.org" <i2nsf@ietf.org>
Thread-Topic: [OPSAWG] is there any work in Ops Area for monitoring network functions?
Thread-Index: AQHUkUO+ttdu7Btv+EWRQt1tMCs7+qV5sE7Q
Date: Tue, 11 Dec 2018 16:12:10 +0000
Message-ID: <4A95BA014132FF49AE685FAB4B9F17F66B20E18F@sjceml521-mbs.china.huawei.com>
References: <4A95BA014132FF49AE685FAB4B9F17F66B1F609F@SJCEML521-MBB.china.huawei.com> <039901d49143$5d6dcba0$4001a8c0@gateway.2wire.net>
In-Reply-To: <039901d49143$5d6dcba0$4001a8c0@gateway.2wire.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.192.11.103]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2nsf/jxSVOMZLAOXCl423IcAJH-g6xNI>
Subject: Re: [I2nsf] [OPSAWG] is there any work in Ops Area for monitoring network functions?
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, 11 Dec 2018 16:12:20 -0000

VG9tLCANCg0KVGhhbmsgeW91IHZlcnkgbXVjaCBmb3IgdGhlIHJldmlldyBhbmQgY29tbWVudHMu
IFNvIHRoZXJlIGlzIG5vIGR1cGxpY2F0ZWQgd29yayBpbiBPcHNBcmVhPyANCg0KDQpBdXRob3Jz
IG9mIHRoZSBkcmFmdC1ob25nLWkybnNmLW5zZi1tb25pdG9yaW5nLWRhdGEtbW9kZWw6IENhbiB5
b3UgcGxlYXNlIHVwZGF0ZSB0aGUgZHJhZnQgcGVyIFRvbSdzIGNvbW1lbnRzLiANCg0KTGluZGEu
IA0KDQotLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KRnJvbTogdG9tIHBldGNoIFttYWlsdG86
aWV0ZmNAYnRjb25uZWN0LmNvbV0gDQpTZW50OiBUdWVzZGF5LCBEZWNlbWJlciAxMSwgMjAxOCA1
OjIyIEFNDQpUbzogTGluZGEgRHVuYmFyIDxsaW5kYS5kdW5iYXJAaHVhd2VpLmNvbT47IG9wc2F3
Z0BpZXRmLm9yZw0KQ2M6IGkybnNmQGlldGYub3JnDQpTdWJqZWN0OiBSZTogW09QU0FXR10gaXMg
dGhlcmUgYW55IHdvcmsgaW4gT3BzIEFyZWEgZm9yIG1vbml0b3JpbmcgbmV0d29yayBmdW5jdGlv
bnM/DQoNCkxpbmRhDQoNCkkgbG9va2VkIGF0IHRoZSBkcmFmdCBhbmQgdGhpbmsgdGhhdCBpdCBu
ZWVkcyBzb21lIHdvcmsgYmVmb3JlIGl0IGlzIGEgWUFORyBtb2R1bGU6LSkNCg0KLSBOTURBIGNv
bmZvcm1hbmNlIGlzIG5vdCBtZW50aW9uZWQNCg0KLSB0aGUgcmVmZXJlbmNlIHRvIFJGQzIxMTkg
aXMgb3V0IG9mIGRhdGUNCg0KLSB0aGUgZm9ybWF0IGZvciB0cmVlIGRpYWdyYW1zIGlzIG5vdyBz
cGVjaWZpZWQgaW4gUkZDODM0MA0KDQotIFlBTkcgaW1wb3J0IHN0YXRlbWVudHMgbGFjayAncmVm
ZXJlbmNlJyBhcyBpbg0KICAgICBpbXBvcnQgaWV0Zi1pbmV0LXR5cGVzIHsNCiAgICAgICBwcmVm
aXggImluZXQiOw0KICAgICAgIHJlZmVyZW5jZSAiUkZDIDY5OTEgLSBDb21tb24gWUFORyBEYXRh
IFR5cGVzIjsNCg0KLSBZQU5HIG1vZHVsZSBoYXMgbm8gY29weXJpZ2h0DQoNCi0gWUFORyBtb2R1
bGUgaGFzIChhbG1vc3QpIG5vIHJlZmVyZW5jZSBzdGF0ZW1lbnRzIHRvIHRlbGwgdGhlIHVzZXIg
KGxpa2UgbWUpICB3aGVyZXRvIGdvIHRvIHVuZGVyc3RhbmQgaXQuIGxvb2ssIGZvciBleGFtcGxl
LCBhdCBkcmFmdC1pZXRmLW9wc2F3Zy1uYXQteWFuZyBmb3IgYSBtb2R1bGUgdGhhdCBpcyB3ZWxs
IHN1cHBsaWVkIHdpdGggcmVmZXJlbmNlIHN0YXRlbWVudHMNCg0KLSBZQU5HIG1vZHVsZSBzaG91
bGQgcmVmZXJlbmNlIHRoZSBSRkMgZnJvbSB3aGljaCBpdCBjb21lcw0KDQotIHRoZSBvbmUgYW5k
IG9ubHkgcmVmZXJlbmNlIGluIHRoZSBZQU5HIG1vZHVsZSBpcw0KICAgICAgcmVmZXJlbmNlDQog
ICAgICAgICAiZHJhZnQtemhhbmctaTJuc2YtaW5mby1tb2RlbC1tb25pdG9yaW5nLTA3IjsNCmJ1
dCB0aGUgSS1EIGlzDQogICAgICAgICBkcmFmdC1ob25nLWkybnNmLW5zZi1tb25pdG9yaW5nLWRh
dGEtbW9kZWwtMDYNCkkgZG8gbm90IHVuZGVyc3RhbmQNCg0KLSB3aGVyZSB5b3UgcmVmZXJlbmNl
IGFuIEktRCwgaXQgbmVlZHMgYSBOb3RlIHRvIHRoZSBSRkMgRWRpdG9yIGUuZy4NCiByZWZlcmVu
Y2UgICAgICAgImRyYWZ0LXpoYW5nLWkybnNmLWluZm8tbW9kZWwtbW9uaXRvcmluZy0wNyI7DQpi
ZWNvbWVzDQogcmVmZXJlbmNlIFJGQyBZWVlZICIuLi4uLiINCi0tIE5vdGUgdG8gUkZDIEVkaXRv
ciBwbGVhc2UgcmVwbGFjZSBZWVlZIHdpdGggdGhlIG51bWJlciBhc3NpZ25lZCB0bw0KICAgICAg
ICAgImRyYWZ0LXpoYW5nLWkybnNmLWluZm8tbW9kZWwtbW9uaXRvcmluZyINCg0KLSBJQU5BIENv
bnNpZGVyYXRpb25zIG11c3QgYmUgcHJlc2VudA0KDQotIFNlY3VyaXR5IENvbnNpZGVyYXRpb25z
IG11c3QgaW5jbHVkZSB0aGUgWUFORyB0ZW1wbGF0ZQ0KDQpIVEg6LSkNCg0KSSBhbSBub3Qgb24g
dGhlIEkyTlNGIGxpc3QuDQoNClRvbSBQZXRjaA0KDQotLS0tLSBPcmlnaW5hbCBNZXNzYWdlIC0t
LS0tDQpGcm9tOiAiTGluZGEgRHVuYmFyIiA8bGluZGEuZHVuYmFyQGh1YXdlaS5jb20+DQpUbzog
PG9wc2F3Z0BpZXRmLm9yZz4NCkNjOiA8aTJuc2ZAaWV0Zi5vcmc+DQpTZW50OiBXZWRuZXNkYXks
IERlY2VtYmVyIDA1LCAyMDE4IDU6MjcgUE0NCg0KPiBPcHNhV0c6DQo+DQo+IEkyTlNGIFdHIGhh
cyBhIGRyYWZ0IG9uIGRhdGEgbW9kZWxzIChhbmQgaW5mb3JtYXRpb24gbW9kZWwpIG9mDQptb25p
dG9yaW5nIG5ldHdvcmsgc2VjdXJpdHkgZnVuY3Rpb25zOg0KaHR0cHM6Ly90b29scy5pZXRmLm9y
Zy9odG1sL2RyYWZ0LWhvbmctaTJuc2YtbnNmLW1vbml0b3JpbmctZGF0YS1tb2RlbC0wDQo2DQo+
DQo+IEl0IGluY2x1ZGVzIGRhdGEgbW9kZWxzIHRvIHJldHJpZXZlIFN5c3RlbSBBbGFybXMsIFN5
c3RlbSBFdmVudHMsDQpjb3VudGVycywgTlNGIEV2ZW50cy9sb2dzLCBldGMuDQo+DQo+IFdhbnQg
dG8gc2VlIGlmIHRoZXJlIGFyZSBkYXRhIG1vZGVscyBhbHJlYWR5IHNwZWNpZmllZCBieSBPcHMg
QXJlYSBmb3INCm1vbml0b3JpbmcgbmV0d29yayBmdW5jdGlvbnMgd2hpY2ggbWlnaHQgaGF2ZSBz
b21lIGNvbW1vbiBhdHRyaWJ1dGVzIHRoYXQgSTJOU0YgY2FuIGltcG9ydC4NCj4NCj4gVGhhbmtz
LCBMaW5kYSBEdW5iYXINCj4NCj4gRnJvbTogTXIuIEphZWhvb24gUGF1bCBKZW9uZyBbbWFpbHRv
OmphZWhvb24ucGF1bEBnbWFpbC5jb21dDQo+IFNlbnQ6IFRodXJzZGF5LCBOb3ZlbWJlciAxNSwg
MjAxOCA2OjM1IFBNDQo+IFRvOiBMaW5kYSBEdW5iYXINCjxsaW5kYS5kdW5iYXJAaHVhd2VpLmNv
bTxtYWlsdG86bGluZGEuZHVuYmFyQGh1YXdlaS5jb20+PjsgWW9hdiBOaXIgPHluaXIuaWV0ZkBn
bWFpbC5jb208bWFpbHRvOnluaXIuaWV0ZkBnbWFpbC5jb20+Pg0KPiBDYzogaTJuc2ZAaWV0Zi5v
cmc8bWFpbHRvOmkybnNmQGlldGYub3JnPjsNCnNra3Vfc2VjdS1icmFpbl9hbGxAZ29vZ2xlZ3Jv
dXBzLmNvbTxtYWlsdG86c2trdV9zZWN1LWJyYWluX2FsbEBnb29nbGVncg0Kb3Vwcy5jb20+OyBT
YW5nd29uIEh5dW4gPHN3aHl1bjc3QGdtYWlsLmNvbTxtYWlsdG86c3doeXVuNzdAZ21haWwuY29t
Pj47DQpNci4gSmFlaG9vbiBQYXVsIEplb25nDQo8amFlaG9vbi5wYXVsQGdtYWlsLmNvbTxtYWls
dG86amFlaG9vbi5wYXVsQGdtYWlsLmNvbT4+DQo+IFN1YmplY3Q6IFJlcXVlc3QgZm9yIFdHIEFk
b3B0aW9uIENhbGwgb24gTlNGIE1vbml0b3JpbmcgRHJhZnQNCj4NCj4gSGkgTGluZGEgYW5kIFlv
YXYsDQo+IEFzIHdlIGRpc2N1c3NlZCB0aGUgbGFzdCBCYW5na29rIG1lZXRpbmcsIEkgaGF2ZSBt
ZXJnZWQgdGhlIHR3byBkcmFmdHMgDQo+IG9mIEluZm9ybWF0aW9uIE1vZGVsIGFuZCBEYXRhIE1v
ZGVsIGZvciBOU0YgTW9uaXRvcmluZyBpbnRvIGEgbmV3IA0KPiBkcmFmdCBjYWxsZWQNCmRyYWZ0
LWhvbmctaTJuc2YtbnNmLW1vbml0b3JpbmctZGF0YS1tb2RlbC0wNjoNCj4NCj4gLSBUd28gSW5m
b3JtYXRpb24gYW5kIERhdGEgTW9kZWwgRHJhZnRzICAuIA0KPiBkcmFmdC16aGFuZy1pMm5zZi1p
bmZvLW1vZGVsLW1vbml0b3JpbmctMDcNCj4gIC4gZHJhZnQtaG9uZy1pMm5zZi1uc2YtbW9uaXRv
cmluZy1kYXRhLW1vZGVsLTA1DQo+DQo+IC0gQSBNZXJnZWQgRGF0YSBNb2RlbCBEcmFmdA0KPiAg
LiBkcmFmdC1ob25nLWkybnNmLW5zZi1tb25pdG9yaW5nLWRhdGEtbW9kZWwtMDYNCj4gIC4NCmh0
dHBzOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9kcmFmdC1ob25nLWkybnNmLW5zZi1tb25pdG9yaW5n
LWRhdGEtbW9kZWwtMA0KNg0KPg0KPiBUaGUgTlNGIG1vbml0b3JpbmcgaXMgdmVyeSBpbXBvcnRh
bnQgdG8gbWFuYWdlIHRoZSBJMk5TRiBzZWN1cml0eQ0Kc2VydmljZSBzeXN0ZW0NCj4gaW4gYSBy
ZWxpYWJsZSBhbmQgc2NhbGFibGUgZmFzaGlvbi4NCj4NCj4gQ291bGQgeW91IHN0YXJ0IGEgV0cg
YWRvcHRpb24gY2FsbCBmb3IgdGhpcyBkcmFmdD8NCj4NCj4gVGhhbmtzLg0KPg0KPiBCZXN0IFJl
Z2FyZHMsDQo+IFBhdWwNCj4gLS0NCj4gPT09PT09PT09PT09PT09PT09PT09PT09PT09DQo+IE1y
LiBKYWVob29uIChQYXVsKSBKZW9uZywgUGguRC4NCj4gQXNzb2NpYXRlIFByb2Zlc3Nvcg0KPiBE
ZXBhcnRtZW50IG9mIFNvZnR3YXJlDQo+IFN1bmdreXVua3dhbiBVbml2ZXJzaXR5DQo+IE9mZmlj
ZTogKzgyLTMxLTI5OS00OTU3DQo+IEVtYWlsOiBqYWVob29uLnBhdWxAZ21haWwuY29tPG1haWx0
bzpqYWVob29uLnBhdWxAZ21haWwuY29tPiwNCnBhdWxqZW9uZ0Bza2t1LmVkdTxtYWlsdG86cGF1
bGplb25nQHNra3UuZWR1Pg0KPiBQZXJzb25hbCBIb21lcGFnZToNCmh0dHA6Ly9pb3RsYWIuc2tr
dS5lZHUvcGVvcGxlLWphZWhvb24tamVvbmcucGhwPGh0dHA6Ly9jcHNsYWIuc2trdS5lZHUvcA0K
ZW9wbGUtamFlaG9vbi1qZW9uZy5waHA+DQoNCg==


From nobody Tue Dec 11 10:52:56 2018
Return-Path: <fernando.pereniguez@cud.upct.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 7AEFA130F17; Tue, 11 Dec 2018 10:52:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.62
X-Spam-Level: 
X-Spam-Status: No, score=-1.62 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FROM_EXCESS_BASE64=0.979, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] 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 qpBoF7vFfhYI; Tue, 11 Dec 2018 10:52:46 -0800 (PST)
Received: from telmad-lavadora-l1mail1v.puc.rediris.es (te-l1mail1v-out02a.puc.rediris.es [IPv6:2001:720:418:ca03::76]) (using TLSv1.2 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CDD07130F20; Tue, 11 Dec 2018 10:52:45 -0800 (PST)
X-IPAS-Result: =?us-ascii?q?A2EXAACEBhBcjNMUgNRkHAEBAQQBAQcEAQGBUQcBAQsBg2u?= =?us-ascii?q?EIoEdhnxfl0iNSoF6DYRsAoMPNAkNAQMBAQEBAQECAgIQAQEBJliFPgMDI1YQC?= =?us-ascii?q?QIEBzcCAiISAQUBHIM6ggIEiimQBzyLDYEviSGBDo5RgRGDEogFglcCiSkSjDu?= =?us-ascii?q?LBQcCkVEYgVyFF4pNgwGWIw8hgSU3gVgzgT4GgjaCNBuODD6MHQEB?=
X-IronPort-AV: E=Sophos;i="5.56,343,1539640800";  d="scan'208,217";a="244847433"
Received: from mail.upct.es (HELO relay1.si.upct.es) ([212.128.20.211]) by smtpout.puc.rediris.es with ESMTP/TLS/DHE-RSA-AES256-SHA; 11 Dec 2018 19:52:43 +0100
Received: from mail-it1-f177.google.com (mail-it1-f177.google.com [209.85.166.177]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by relay1.si.upct.es (Postfix) with ESMTPSA id 5DDF21CD25; Tue, 11 Dec 2018 19:52:37 +0100 (CET)
Received: by mail-it1-f177.google.com with SMTP id m8so11588070itk.0; Tue, 11 Dec 2018 10:52:37 -0800 (PST)
X-Gm-Message-State: AA+aEWZe0yo4M+RVnRJ6+TOyFnwvTEBxjLzWh8s7RbeStAgQsE+cKMYS dsCDeb+npD/E8FVK3VvfCIDuJly0zXZhZzC6nVc=
X-Google-Smtp-Source: AFSGD/VAjnAb5tvmGmQ4fh6fg7p7T+Xk+gacHUjx+8rMoJ99FfOwy7fjIsuTnF+qHWAnoksBuE11oqoyLjPDODQC/UA=
X-Received: by 2002:a24:1a90:: with SMTP id 138mr3114739iti.171.1544554346012;  Tue, 11 Dec 2018 10:52:26 -0800 (PST)
MIME-Version: 1.0
References: <A881C135-9BF7-4E93-BB7A-75EB3D1FF605@gmail.com> <6839D47C-4074-486F-9350-8EB7B378036C@um.es> <DAE14995-8504-4134-B021-93D56A4994FB@gmail.com> <alpine.LRH.2.21.1811180149220.25604@bofh.nohats.ca>
In-Reply-To: <alpine.LRH.2.21.1811180149220.25604@bofh.nohats.ca>
From: =?UTF-8?B?RmVybmFuZG8gUGVyZcOxw61ndWV6IEdhcmPDrWE=?= <fernando.pereniguez@cud.upct.es>
Date: Tue, 11 Dec 2018 19:52:13 +0100
X-Gmail-Original-Message-ID: <CAB=gXc66hBpXBMOzkwXeH-ORrQWO47as4-TPQDe591_Zi=CKDQ@mail.gmail.com>
Message-ID: <CAB=gXc66hBpXBMOzkwXeH-ORrQWO47as4-TPQDe591_Zi=CKDQ@mail.gmail.com>
To: paul@nohats.ca
Cc: ynir.ietf@gmail.com, i2nsf@ietf.org, ipsec@ietf.org,  Rafa Marin Lopez <rafa@um.es>, =?UTF-8?Q?Gabriel_L=C3=B3pez_Mill=C3=A1n?= <gabilm@um.es>
Content-Type: multipart/alternative; boundary="000000000000216657057cc395a4"
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2nsf/4MsT5fZPg-CyP50kol5EPIoRpiw>
Subject: Re: [I2nsf] Review of draft-ietf-i2nsf-sdn-ipsec-flow-protection-03 (Sections 8 - 9)
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, 11 Dec 2018 18:52:50 -0000

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

Hi Paul, all,

Next you can find our answers to your comments on sections 8 and 9.


Section 8:

Is this section supposed to be an "Implementation Details" Section as per
RFC 7942? If so, it is missing the required
note to the RFC Editor to remove the entire section before publication as
RFC.

[Authors]

Agree. We will include it.


Section 9.1:

In case 1, add a note to use only strong PSKs, with a minimal length and
strength.

[Authors]
Agree. We will add it.

Section 9.2:

when ESP is used

Hoping my advise is taken to only use ESP and not AH, and to use ESP-null
in the case of encryption being unwanted, please
remove this comment as ESP would always be used.

includes the keys for integrity and encryption

If we only allow AEAD's, maybe rewrite or leave this out.

[Authors]

s/"In the case 2, the controller sends the IPsec SA information to the SAD
that includes the keys for integrity and encryption (when ESP is used)" /
"In the case 2, the controller sends the IPsec SA information to the SAD
that includes the required cryptographic keys for ESP or AH"


Regards,
Fernando.


--=20
---------------------------------------------------------------------------=
-------------------------
Fernando Pere=C3=B1=C3=ADguez Garc=C3=ADa, PhD
Department of Sciences and Informatics
University Defense Center, (CUD), San Javier Air Force Base, MDE-UPCT
C/ Coronel Lopez Pe=C3=B1a, s/n, 30720, San Javier, Murcia - SPAIN
Tel: +34 968 189 946 Fax: +34 968 189 970
---------------------------------------------------------------------------=
---------------------------

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

<div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr">Hi Paul, all,<div><br></=
div><div>Next you can find our answers to your comments on sections 8 and 9=
.=C2=A0</div><div><br></div><div><br></div><div><div>Section 8:</div><div><=
br></div><div>Is this section supposed to be an &quot;Implementation Detail=
s&quot; Section as per RFC 7942? If so, it is missing the required</div><di=
v>note to the RFC Editor to remove the entire section before publication as=
 RFC.</div><div><br></div><div>[Authors]</div><div><br></div><div>Agree. We=
 will include it.</div></div><div><br></div><div><br></div><div><div>Sectio=
n 9.1:</div><div><br></div><div>In case 1, add a note to use only strong PS=
Ks, with a minimal length and strength.</div><div><br></div><div>[Authors]<=
/div><div>Agree. We will add it.</div><div><br></div><div>Section 9.2:</div=
><div><br></div><div><span style=3D"white-space:pre">	</span>when ESP is us=
ed</div><div><br></div><div>Hoping my advise is taken to only use ESP and n=
ot AH, and to use ESP-null in the case of encryption being unwanted, please=
</div><div>remove this comment as ESP would always be used.</div><div><br><=
/div><div><span style=3D"white-space:pre">	</span>includes the keys for int=
egrity and encryption</div><div><br></div><div>If we only allow AEAD&#39;s,=
 maybe rewrite or leave this out.</div><div><br></div><div>[Authors]</div><=
div><br></div><div>s/&quot;In the case 2, the controller sends the IPsec SA=
 information to the SAD that includes the keys for integrity and encryption=
 (when ESP is used)&quot; /=C2=A0</div><div>&quot;In the case 2, the contro=
ller sends the IPsec SA information to the SAD that includes the required c=
ryptographic keys for ESP or AH&quot;</div></div><div><br></div><div><br></=
div><div>Regards,</div><div>Fernando.</div><div><br></div><div><div class=
=3D"gmail_quote"><div>=C2=A0</div></div>-- <br><div dir=3D"ltr" class=3D"gm=
ail-m_-3248620141668657945gmail_signature"><div dir=3D"ltr"><div><div dir=
=3D"ltr"><div><div dir=3D"ltr"><div><div dir=3D"ltr"><div><div dir=3D"ltr">=
<div><div dir=3D"ltr"><span style=3D"font-family:arial,helvetica,sans-serif=
;font-size:small">---------------------------------------------------------=
-------------------------------------------</span><br></div><font face=3D"a=
rial, helvetica, sans-serif" size=3D"2">Fernando Pere=C3=B1=C3=ADguez Garc=
=C3=ADa, PhD<br>Department of Sciences and Informatics<br>University Defens=
e Center, (CUD), San Javier Air Force Base, MDE-UPCT<br>C/ Coronel Lopez Pe=
=C3=B1a, s/n, 30720, San Javier, Murcia - SPAIN<br>Tel: +34 968 189 946 Fax=
: +34 968 189 970<br>------------------------------------------------------=
------------------------------------------------</font></div></div></div></=
div></div></div></div></div></div></div></div></div></div></div></div>

--000000000000216657057cc395a4--


From nobody Tue Dec 11 12:59:21 2018
Return-Path: <paul@nohats.ca>
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 0970E130F14; Tue, 11 Dec 2018 12:59:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nohats.ca
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 C1vaSJMjihmF; Tue, 11 Dec 2018 12:59:18 -0800 (PST)
Received: from mx.nohats.ca (mx.nohats.ca [193.110.157.68]) (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 642AE12E036; Tue, 11 Dec 2018 12:59:18 -0800 (PST)
Received: from localhost (localhost [IPv6:::1]) by mx.nohats.ca (Postfix) with ESMTP id 43DskY0lSyzG8X; Tue, 11 Dec 2018 21:59:17 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nohats.ca; s=default; t=1544561957; bh=6hx1lXi/ZwAqUY67vHPT43p/jFMNry4gV4+0lj0mibI=; h=Date:From:To:cc:Subject:In-Reply-To:References; b=XMFYTZlTtLvCK8OUFyXxM7aBhuETvoi98iLd2K2uM84+oCK2CU8HB1LoKPDv2DEAf lVlKn48+A9jeHZQkjbb+vsDEiyf37fEBGDW/ZQQBz4O2TOFKgX5G2jCq2Zhm2xLwXY iKM1UFwzsuE+PYs1QYCXMzMI9CUQfLWV2IoM2t1A=
X-Virus-Scanned: amavisd-new at mx.nohats.ca
Received: from mx.nohats.ca ([IPv6:::1]) by localhost (mx.nohats.ca [IPv6:::1]) (amavisd-new, port 10024) with ESMTP id N1teXh0kb46A; Tue, 11 Dec 2018 21:59:16 +0100 (CET)
Received: from bofh.nohats.ca (bofh.nohats.ca [76.10.157.69]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx.nohats.ca (Postfix) with ESMTPS; Tue, 11 Dec 2018 21:59:16 +0100 (CET)
Received: by bofh.nohats.ca (Postfix, from userid 1000) id F42202E75A2; Tue, 11 Dec 2018 15:59:14 -0500 (EST)
DKIM-Filter: OpenDKIM Filter v2.11.0 bofh.nohats.ca F42202E75A2
Received: from localhost (localhost [127.0.0.1]) by bofh.nohats.ca (Postfix) with ESMTP id EB906407AA79; Tue, 11 Dec 2018 15:59:14 -0500 (EST)
Date: Tue, 11 Dec 2018 15:59:14 -0500 (EST)
From: Paul Wouters <paul@nohats.ca>
To: =?ISO-8859-15?Q?Fernando_Pere=F1=EDguez_Garc=EDa?= <fernando.pereniguez@cud.upct.es>
cc: ynir.ietf@gmail.com, i2nsf@ietf.org, ipsec@ietf.org,  Rafa Marin Lopez <rafa@um.es>,  =?ISO-8859-15?Q?Gabriel_L=F3pez_Mill=E1n?= <gabilm@um.es>
In-Reply-To: <CAB=gXc66hBpXBMOzkwXeH-ORrQWO47as4-TPQDe591_Zi=CKDQ@mail.gmail.com>
Message-ID: <alpine.LRH.2.21.1812111558510.22818@bofh.nohats.ca>
References: <A881C135-9BF7-4E93-BB7A-75EB3D1FF605@gmail.com> <6839D47C-4074-486F-9350-8EB7B378036C@um.es> <DAE14995-8504-4134-B021-93D56A4994FB@gmail.com> <alpine.LRH.2.21.1811180149220.25604@bofh.nohats.ca> <CAB=gXc66hBpXBMOzkwXeH-ORrQWO47as4-TPQDe591_Zi=CKDQ@mail.gmail.com>
User-Agent: Alpine 2.21 (LRH 202 2017-01-01)
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8BIT
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2nsf/tM5oSpJH0FM36CfvnmBA3FQqQCo>
Subject: Re: [I2nsf] Review of draft-ietf-i2nsf-sdn-ipsec-flow-protection-03 (Sections 8 - 9)
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, 11 Dec 2018 20:59:20 -0000

On Tue, 11 Dec 2018, Fernando Pereñíguez García wrote:

These answers look fine. Thanks.

Paul
(the other emails will take a little more time :)

> Date: Tue, 11 Dec 2018 13:52:13
> From: Fernando Pereñíguez García <fernando.pereniguez@cud.upct.es>
> Cc: ynir.ietf@gmail.com, i2nsf@ietf.org, ipsec@ietf.org,
>     Rafa Marin Lopez <rafa@um.es>, Gabriel López Millán <gabilm@um.es>
> To: paul@nohats.ca
> Subject: Re: [I2nsf] Review of draft-ietf-i2nsf-sdn-ipsec-flow-protection-03
>     (Sections 8 - 9)
> X-Spam-Flag: NO
> 
> Hi Paul, all,
> Next you can find our answers to your comments on sections 8 and 9. 
> 
> 
> Section 8:
> 
> Is this section supposed to be an "Implementation Details" Section as per RFC 7942? If so, it is missing the required
> note to the RFC Editor to remove the entire section before publication as RFC.
> 
> [Authors]
> 
> Agree. We will include it.
> 
> 
> Section 9.1:
> 
> In case 1, add a note to use only strong PSKs, with a minimal length and strength.
> 
> [Authors]
> Agree. We will add it.
> 
> Section 9.2:
> 
> when ESP is used
> 
> Hoping my advise is taken to only use ESP and not AH, and to use ESP-null in the case of encryption being unwanted, please
> remove this comment as ESP would always be used.
> 
> includes the keys for integrity and encryption
> 
> If we only allow AEAD's, maybe rewrite or leave this out.
> 
> [Authors]
> 
> s/"In the case 2, the controller sends the IPsec SA information to the SAD that includes the keys for integrity and encryption (when ESP is used)" / 
> "In the case 2, the controller sends the IPsec SA information to the SAD that includes the required cryptographic keys for ESP or AH"
> 
> 
> Regards,
> Fernando.
> 
>  
> --
> ----------------------------------------------------------------------------------------------------
> Fernando Pereñíguez García, PhD
> Department of Sciences and Informatics
> University Defense Center, (CUD), San Javier Air Force Base, MDE-UPCT
> C/ Coronel Lopez Peña, s/n, 30720, San Javier, Murcia - SPAIN
> Tel: +34 968 189 946 Fax: +34 968 189 970
> ------------------------------------------------------------------------------------------------------
> 
>


From nobody Tue Dec 11 16:43:31 2018
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 C66DF130F6D; Tue, 11 Dec 2018 16:43:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.988
X-Spam-Level: 
X-Spam-Status: No, score=-1.988 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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 zr1u-fQ00tnP; Tue, 11 Dec 2018 16:43:27 -0800 (PST)
Received: from mail-it1-x134.google.com (mail-it1-x134.google.com [IPv6:2607:f8b0: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 60968129C6B; Tue, 11 Dec 2018 16:43:27 -0800 (PST)
Received: by mail-it1-x134.google.com with SMTP id h65so7140565ith.3; Tue, 11 Dec 2018 16:43:27 -0800 (PST)
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=FEebgOiOV4kH6HhglDe3AobPtOenxfPRHfuE2VwmOPo=; b=WtX+SBjwabGbZNdZVPDeWuUegPXLrzVseqYKiRbFdBRbTFlou+RZUSwESYM5oBaTWy kA7do4u80RwIfMIJwqHuIY0/7IZfuxqnaF/rbM6AaZW9euTFI0F3+uBV5qkJw0OOdPoG BtyEk2oHt5OLvELm/djX6FhV17VkzV726IcLq5zIBI8Qh1cwppp0y89mOA5TjreNiDNl JAV+MewgRcUw94bpCGdUOAIR19IJuwzuefPGhx34+K2vn76gz2xdETFxG4nnk1X/fFQ8 ISZ2LhZ9XaKJRMR0/ePGg67mLSxfdGv64p1AljW/oP/31mstJZMI4nnB6fVLtRYCGGUh QYdQ==
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=FEebgOiOV4kH6HhglDe3AobPtOenxfPRHfuE2VwmOPo=; b=uGv7kDeIPcpRbLy/y8vz1/dHuuQZvpOOx5CZPqQ1mZjeQ/izXAAq42sP5LIJC6vSAU wYtW9V1EBW5dGRK14GEveJoVm8O/VWSDv9Ws8sUhBJZ2P05+SIbnX4HiSR4bkfmdAiRI m1y+zvxFBmSJDfE7fBcgxCNdWABBlhj4X7FeY5YC488w+KomYEw8OLzjQDhLCqKUlDC+ o7MIYh6hqw3OSeHf/z74TPZN91ZnPJ2kSCyec+dXG4IehOZiHl256Y2B/PROhFVq/Ll4 Yzl2XCptDN4LpMkdi9/IMv17YgnFAf0Gyicaq9jNREBGtRaFBMidR4qrjLdKgY/rDwgS j9UA==
X-Gm-Message-State: AA+aEWYSUTO7fAgtDMjrM6CBEiDUMooOqYHbgxbLaypMmnkjmprnjZ4z Q0BA0Xzmon3lz1uupSyiqqH9u0R5dT1WwI9gsg8=
X-Google-Smtp-Source: AFSGD/UAu5+1l/3PJ71+EY8QZ90HFza+9rjz4CQ+NnDyE/u6KycsBptf5yIl3HXvxsAuPKQ3AwFk5bS1X9ROr3xX7Ek=
X-Received: by 2002:a05:660c:445:: with SMTP id d5mr3829141itl.156.1544575406461;  Tue, 11 Dec 2018 16:43:26 -0800 (PST)
MIME-Version: 1.0
References: <4A95BA014132FF49AE685FAB4B9F17F66B1F609F@SJCEML521-MBB.china.huawei.com> <039901d49143$5d6dcba0$4001a8c0@gateway.2wire.net>
In-Reply-To: <039901d49143$5d6dcba0$4001a8c0@gateway.2wire.net>
From: "Mr. Jaehoon Paul Jeong" <jaehoon.paul@gmail.com>
Date: Wed, 12 Dec 2018 09:42:52 +0900
Message-ID: <CAPK2DewP5m+fU9YMWr8HAbgAwQS_vqA4xFmOoiiY4KTDoJUYRw@mail.gmail.com>
To: ietfc@btconnect.com
Cc: Linda Dunbar <linda.dunbar@huawei.com>, opsawg@ietf.org,  "i2nsf@ietf.org" <i2nsf@ietf.org>, skku_secu-brain_all@googlegroups.com,  "Mr. Jaehoon Paul Jeong" <jaehoon.paul@gmail.com>
Content-Type: multipart/alternative; boundary="0000000000006e5bf2057cc87c44"
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2nsf/wYSgsWMWoIUaWRBHsGGuMts-Vpk>
Subject: Re: [I2nsf] [OPSAWG] is there any work in Ops Area for monitoring network functions?
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, 12 Dec 2018 00:43:30 -0000

--0000000000006e5bf2057cc87c44
Content-Type: text/plain; charset="UTF-8"

Hi Tom,
Thanks for your good comments and guidance.

We authors will reflect your comments and guidance on the revision of the
NSF Monitoring Data Model draft.

One thing to note is that
draft-zhang-i2nsf-info-model-monitoring-07 (which is the NSF Monitoring
Information Model draft)
was merged into draft-hong-i2nsf-nsf-monitoring-data-model-06, so we do not
need to reference it in
our data model draft.

Except this, others will be reflected on the revision.

Thanks.

Best Regards,
Paul

On Tue, Dec 11, 2018 at 8:22 PM tom petch <ietfc@btconnect.com> wrote:

> Linda
>
> I looked at the draft and think that it needs some work before it is a
> YANG module:-)
>
> - NMDA conformance is not mentioned
>
> - the reference to RFC2119 is out of date
>
> - the format for tree diagrams is now specified in RFC8340
>
> - YANG import statements lack 'reference' as in
>      import ietf-inet-types {
>        prefix "inet";
>        reference "RFC 6991 - Common YANG Data Types";
>
> - YANG module has no copyright
>
> - YANG module has (almost) no reference statements to tell the user
> (like me)  whereto go to understand it. look, for example, at
> draft-ietf-opsawg-nat-yang
> for a module that is well supplied with reference statements
>
> - YANG module should reference the RFC from which it comes
>
> - the one and only reference in the YANG module is
>       reference
>          "draft-zhang-i2nsf-info-model-monitoring-07";
> but the I-D is
>          draft-hong-i2nsf-nsf-monitoring-data-model-06
> I do not understand
>
> - where you reference an I-D, it needs a Note to the RFC Editor e.g.
>  reference       "draft-zhang-i2nsf-info-model-monitoring-07";
> becomes
>  reference RFC YYYY "....."
> -- Note to RFC Editor please replace YYYY with the number assigned to
>          "draft-zhang-i2nsf-info-model-monitoring"
>
> - IANA Considerations must be present
>
> - Security Considerations must include the YANG template
>
> HTH:-)
>
> I am not on the I2NSF list.
>
> Tom Petch
>
> ----- Original Message -----
> From: "Linda Dunbar" <linda.dunbar@huawei.com>
> To: <opsawg@ietf.org>
> Cc: <i2nsf@ietf.org>
> Sent: Wednesday, December 05, 2018 5:27 PM
>
> > OpsaWG:
> >
> > I2NSF WG has a draft on data models (and information model) of
> monitoring network security functions:
> https://tools.ietf.org/html/draft-hong-i2nsf-nsf-monitoring-data-model-0
> 6
> >
> > It includes data models to retrieve System Alarms, System Events,
> counters, NSF Events/logs, etc.
> >
> > Want to see if there are data models already specified by Ops Area for
> monitoring network functions which might have some common attributes
> that I2NSF can import.
> >
> > Thanks, Linda Dunbar
> >
> > From: Mr. Jaehoon Paul Jeong [mailto:jaehoon.paul@gmail.com]
> > Sent: Thursday, November 15, 2018 6:35 PM
> > To: Linda Dunbar
> <linda.dunbar@huawei.com<mailto:linda.dunbar@huawei.com>>; Yoav Nir
> <ynir.ietf@gmail.com<mailto:ynir.ietf@gmail.com>>
> > Cc: i2nsf@ietf.org<mailto:i2nsf@ietf.org>;
> skku_secu-brain_all@googlegroups.com<mailto:skku_secu-brain_all@googlegr
> oups.com>; Sangwon Hyun <swhyun77@gmail.com<mailto:swhyun77@gmail.com>>;
> Mr. Jaehoon Paul Jeong
> <jaehoon.paul@gmail.com<mailto:jaehoon.paul@gmail.com>>
> > Subject: Request for WG Adoption Call on NSF Monitoring Draft
> >
> > Hi Linda and Yoav,
> > As we discussed the last Bangkok meeting,
> > I have merged the two drafts of Information Model and Data Model
> > for NSF Monitoring into a new draft called
> draft-hong-i2nsf-nsf-monitoring-data-model-06:
> >
> > - Two Information and Data Model Drafts
> >  . draft-zhang-i2nsf-info-model-monitoring-07
> >  . draft-hong-i2nsf-nsf-monitoring-data-model-05
> >
> > - A Merged Data Model Draft
> >  . draft-hong-i2nsf-nsf-monitoring-data-model-06
> >  .
> https://tools.ietf.org/html/draft-hong-i2nsf-nsf-monitoring-data-model-0
> 6
> >
> > The NSF monitoring is very important to manage the I2NSF security
> service system
> > in a reliable and scalable fashion.
> >
> > Could you start a WG adoption call for this draft?
> >
> > Thanks.
> >
> > Best Regards,
> > Paul
> > --
> > ===========================
> > Mr. Jaehoon (Paul) Jeong, Ph.D.
> > Associate Professor
> > Department of Software
> > Sungkyunkwan University
> > Office: +82-31-299-4957
> > Email: jaehoon.paul@gmail.com<mailto:jaehoon.paul@gmail.com>,
> pauljeong@skku.edu<mailto:pauljeong@skku.edu>
> > Personal Homepage:
> http://iotlab.skku.edu/people-jaehoon-jeong.php<http://cpslab.skku.edu/p
> eople-jaehoon-jeong.php <http://cpslab.skku.edu/people-jaehoon-jeong.php>>
>
> _______________________________________________
> I2nsf mailing list
> I2nsf@ietf.org
> https://www.ietf.org/mailman/listinfo/i2nsf
>


-- 
===========================
Mr. Jaehoon (Paul) Jeong, Ph.D.
Associate Professor
Department of Software
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>

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

<div dir=3D"ltr"><div dir=3D"ltr">Hi Tom,<div>Thanks for your good comments=
 and guidance.</div><div><br></div><div>We authors will reflect your commen=
ts and guidance on the revision of the NSF Monitoring Data Model draft.</di=
v><div><br></div><div>One thing to note is that=C2=A0</div><div><div>draft-=
zhang-i2nsf-info-model-monitoring-07 (which is the NSF Monitoring Informati=
on Model draft)=C2=A0</div><div>was merged into draft-hong-i2nsf-nsf-monito=
ring-data-model-06, so we do not need to reference it in=C2=A0</div><div>ou=
r data model draft.</div></div><div><br></div><div>Except this, others will=
 be reflected on the revision.</div><div><br></div><div>Thanks.</div><div><=
br></div><div>Best Regards,</div><div>Paul</div></div><br><div class=3D"gma=
il_quote"><div dir=3D"ltr">On Tue, Dec 11, 2018 at 8:22 PM tom petch &lt;<a=
 href=3D"mailto:ietfc@btconnect.com" target=3D"_blank">ietfc@btconnect.com<=
/a>&gt; wrote:<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">L=
inda<br>
<br>
I looked at the draft and think that it needs some work before it is a<br>
YANG module:-)<br>
<br>
- NMDA conformance is not mentioned<br>
<br>
- the reference to RFC2119 is out of date<br>
<br>
- the format for tree diagrams is now specified in RFC8340<br>
<br>
- YANG import statements lack &#39;reference&#39; as in<br>
=C2=A0 =C2=A0 =C2=A0import ietf-inet-types {<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0prefix &quot;inet&quot;;<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0reference &quot;RFC 6991 - Common YANG Data Type=
s&quot;;<br>
<br>
- YANG module has no copyright<br>
<br>
- YANG module has (almost) no reference statements to tell the user<br>
(like me)=C2=A0 whereto go to understand it. look, for example, at<br>
draft-ietf-opsawg-nat-yang<br>
for a module that is well supplied with reference statements<br>
<br>
- YANG module should reference the RFC from which it comes<br>
<br>
- the one and only reference in the YANG module is<br>
=C2=A0 =C2=A0 =C2=A0 reference<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&quot;draft-zhang-i2nsf-info-model-monito=
ring-07&quot;;<br>
but the I-D is<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0draft-hong-i2nsf-nsf-monitoring-data-mode=
l-06<br>
I do not understand<br>
<br>
- where you reference an I-D, it needs a Note to the RFC Editor e.g.<br>
=C2=A0reference=C2=A0 =C2=A0 =C2=A0 =C2=A0&quot;draft-zhang-i2nsf-info-mode=
l-monitoring-07&quot;;<br>
becomes<br>
=C2=A0reference RFC YYYY &quot;.....&quot;<br>
-- Note to RFC Editor please replace YYYY with the number assigned to<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&quot;draft-zhang-i2nsf-info-model-monito=
ring&quot;<br>
<br>
- IANA Considerations must be present<br>
<br>
- Security Considerations must include the YANG template<br>
<br>
HTH:-)<br>
<br>
I am not on the I2NSF list.<br>
<br>
Tom Petch<br>
<br>
----- Original Message -----<br>
From: &quot;Linda Dunbar&quot; &lt;<a href=3D"mailto:linda.dunbar@huawei.co=
m" target=3D"_blank">linda.dunbar@huawei.com</a>&gt;<br>
To: &lt;<a href=3D"mailto:opsawg@ietf.org" target=3D"_blank">opsawg@ietf.or=
g</a>&gt;<br>
Cc: &lt;<a href=3D"mailto:i2nsf@ietf.org" target=3D"_blank">i2nsf@ietf.org<=
/a>&gt;<br>
Sent: Wednesday, December 05, 2018 5:27 PM<br>
<br>
&gt; OpsaWG:<br>
&gt;<br>
&gt; I2NSF WG has a draft on data models (and information model) of<br>
monitoring network security functions:<br>
<a href=3D"https://tools.ietf.org/html/draft-hong-i2nsf-nsf-monitoring-data=
-model-0" rel=3D"noreferrer" target=3D"_blank">https://tools.ietf.org/html/=
draft-hong-i2nsf-nsf-monitoring-data-model-0</a><br>
6<br>
&gt;<br>
&gt; It includes data models to retrieve System Alarms, System Events,<br>
counters, NSF Events/logs, etc.<br>
&gt;<br>
&gt; Want to see if there are data models already specified by Ops Area for=
<br>
monitoring network functions which might have some common attributes<br>
that I2NSF can import.<br>
&gt;<br>
&gt; Thanks, Linda Dunbar<br>
&gt;<br>
&gt; From: Mr. Jaehoon Paul Jeong [mailto:<a href=3D"mailto:jaehoon.paul@gm=
ail.com" target=3D"_blank">jaehoon.paul@gmail.com</a>]<br>
&gt; Sent: Thursday, November 15, 2018 6:35 PM<br>
&gt; To: Linda Dunbar<br>
&lt;<a href=3D"mailto:linda.dunbar@huawei.com" target=3D"_blank">linda.dunb=
ar@huawei.com</a>&lt;mailto:<a href=3D"mailto:linda.dunbar@huawei.com" targ=
et=3D"_blank">linda.dunbar@huawei.com</a>&gt;&gt;; Yoav Nir<br>
&lt;<a href=3D"mailto:ynir.ietf@gmail.com" target=3D"_blank">ynir.ietf@gmai=
l.com</a>&lt;mailto:<a href=3D"mailto:ynir.ietf@gmail.com" target=3D"_blank=
">ynir.ietf@gmail.com</a>&gt;&gt;<br>
&gt; Cc: <a href=3D"mailto:i2nsf@ietf.org" target=3D"_blank">i2nsf@ietf.org=
</a>&lt;mailto:<a href=3D"mailto:i2nsf@ietf.org" target=3D"_blank">i2nsf@ie=
tf.org</a>&gt;;<br>
<a href=3D"mailto:skku_secu-brain_all@googlegroups.com" target=3D"_blank">s=
kku_secu-brain_all@googlegroups.com</a>&lt;mailto:<a href=3D"mailto:skku_se=
cu-brain_all@googlegr" target=3D"_blank">skku_secu-brain_all@googlegr</a><b=
r>
<a href=3D"http://oups.com" rel=3D"noreferrer" target=3D"_blank">oups.com</=
a>&gt;; Sangwon Hyun &lt;<a href=3D"mailto:swhyun77@gmail.com" target=3D"_b=
lank">swhyun77@gmail.com</a>&lt;mailto:<a href=3D"mailto:swhyun77@gmail.com=
" target=3D"_blank">swhyun77@gmail.com</a>&gt;&gt;;<br>
Mr. Jaehoon Paul Jeong<br>
&lt;<a href=3D"mailto:jaehoon.paul@gmail.com" target=3D"_blank">jaehoon.pau=
l@gmail.com</a>&lt;mailto:<a href=3D"mailto:jaehoon.paul@gmail.com" target=
=3D"_blank">jaehoon.paul@gmail.com</a>&gt;&gt;<br>
&gt; Subject: Request for WG Adoption Call on NSF Monitoring Draft<br>
&gt;<br>
&gt; Hi Linda and Yoav,<br>
&gt; As we discussed the last Bangkok meeting,<br>
&gt; I have merged the two drafts of Information Model and Data Model<br>
&gt; for NSF Monitoring into a new draft called<br>
draft-hong-i2nsf-nsf-monitoring-data-model-06:<br>
&gt;<br>
&gt; - Two Information and Data Model Drafts<br>
&gt;=C2=A0 . draft-zhang-i2nsf-info-model-monitoring-07<br>
&gt;=C2=A0 . draft-hong-i2nsf-nsf-monitoring-data-model-05<br>
&gt;<br>
&gt; - A Merged Data Model Draft<br>
&gt;=C2=A0 . draft-hong-i2nsf-nsf-monitoring-data-model-06<br>
&gt;=C2=A0 .<br>
<a href=3D"https://tools.ietf.org/html/draft-hong-i2nsf-nsf-monitoring-data=
-model-0" rel=3D"noreferrer" target=3D"_blank">https://tools.ietf.org/html/=
draft-hong-i2nsf-nsf-monitoring-data-model-0</a><br>
6<br>
&gt;<br>
&gt; The NSF monitoring is very important to manage the I2NSF security<br>
service system<br>
&gt; in a reliable and scalable fashion.<br>
&gt;<br>
&gt; Could you start a WG adoption call for this draft?<br>
&gt;<br>
&gt; Thanks.<br>
&gt;<br>
&gt; Best Regards,<br>
&gt; Paul<br>
&gt; --<br>
&gt; =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>
&gt; Mr. Jaehoon (Paul) Jeong, Ph.D.<br>
&gt; Associate Professor<br>
&gt; Department of Software<br>
&gt; Sungkyunkwan University<br>
&gt; Office: +82-31-299-4957<br>
&gt; Email: <a href=3D"mailto:jaehoon.paul@gmail.com" target=3D"_blank">jae=
hoon.paul@gmail.com</a>&lt;mailto:<a href=3D"mailto:jaehoon.paul@gmail.com"=
 target=3D"_blank">jaehoon.paul@gmail.com</a>&gt;,<br>
<a href=3D"mailto:pauljeong@skku.edu" target=3D"_blank">pauljeong@skku.edu<=
/a>&lt;mailto:<a href=3D"mailto:pauljeong@skku.edu" target=3D"_blank">paulj=
eong@skku.edu</a>&gt;<br>
&gt; Personal Homepage:<br>
<a href=3D"http://iotlab.skku.edu/people-jaehoon-jeong.php" rel=3D"noreferr=
er" target=3D"_blank">http://iotlab.skku.edu/people-jaehoon-jeong.php</a>&l=
t;<a href=3D"http://cpslab.skku.edu/people-jaehoon-jeong.php" rel=3D"norefe=
rrer" target=3D"_blank">http://cpslab.skku.edu/p<br>
eople-jaehoon-jeong.php</a>&gt;<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"m_8237782782454455013gmail_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. Jaeh=
oon (Paul) Jeong, Ph.D.<br>Associate Professor<br>Department of Software<br=
>Sungkyunkwan University<br>Office: +82-31-299-4957<br>Email: <a href=3D"ma=
ilto: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" targ=
et=3D"_blank">pauljeong@skku.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></d=
iv></div></div></div>

--0000000000006e5bf2057cc87c44--


From nobody Tue Dec 11 17:07:31 2018
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 28828127598; Tue, 11 Dec 2018 17:07:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.988
X-Spam-Level: 
X-Spam-Status: No, score=-1.988 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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 W0t8JdfQY0WD; Tue, 11 Dec 2018 17:07:26 -0800 (PST)
Received: from mail-io1-xd35.google.com (mail-io1-xd35.google.com [IPv6:2607:f8b0:4864:20::d35]) (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 B511F129A87; Tue, 11 Dec 2018 17:07:26 -0800 (PST)
Received: by mail-io1-xd35.google.com with SMTP id n3so2729997iog.12; Tue, 11 Dec 2018 17:07:26 -0800 (PST)
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=eqfjoyXbXGdXwTodH1bzuNaF2HLtUFAlECLv9jE43VU=; b=pP3GaJH3vOfe76QAmrM09naPZ8D0th/Ou6R1hY/8gurkNGK8w0+BKssIuFf2GfcYHv BPgUNwrg8tCEg3lPpHMUuC+MarGnJqCUc9BzUqg3CipN1gULrbmPb4WcdyskjaDb+/bE nm06lFC1suasTUQjQexl/T32sJABcnriiwmysz7LNXo1Xp+TYwACKpnZStvzUfEvy25P kGIvSgbJnni3yl/JXiA4UH9dBEn9YoKEpiZlQuXmPXHPczGg07dSu+0uA/TrPGToIbOq Z1xI11GTg2mmjd1QOELpJvnRFkhdn9Ns7PtZreloRv6TMBCg6RSe4IA0gOqCcrVgODpA Cmyg==
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=eqfjoyXbXGdXwTodH1bzuNaF2HLtUFAlECLv9jE43VU=; b=ETjBRbAR3qnSZUGhkyxMTltMdyHOagLk+3N4UTB1NRsGVO/vkgSfoO0R0RFVAfXxr7 yatu/Cco+wvtSKKZ+vFKWlvqmxvDGwsiKb7SlS3K1UVICwyGU1ifVXO4+JX+jH++s6mf lpi7JW/u1sketX4BHbWl6sCj0rC5YZgApcvV5RehnU8MnsCfg+pQZ4cEpiiH1DQOr9/4 PgMzDW5UdmjHIead2kTBPA+OLq7vvWFjc8GsEypicRljT4HukzJ8W80ZNH/F8PhG5qOm USj++RUUBXE5go5RhnrgJxCEXLFIgY0E34vt3ODaydP+7Grsw8V69OHDss8yzTYLa4Kl mEDA==
X-Gm-Message-State: AA+aEWYS+ccTe2ab9D45uhPJfL4n6fowNSz6cnb+QsaqoDwYGaOq3K2B O7lIa65FVVjiqSknv9qDmDvkUKoI13fzokNKm9c=
X-Google-Smtp-Source: AFSGD/U2bgLkl5os3yU7Mo/wcIs0JgokBKF7jq6jMUxAIi82WT+7NG7rSp4jLy0ld2vnaV1un7SM0rQVLhhbAf9n5q4=
X-Received: by 2002:a6b:e802:: with SMTP id f2mr14682371ioh.296.1544576845872;  Tue, 11 Dec 2018 17:07:25 -0800 (PST)
MIME-Version: 1.0
References: <4A95BA014132FF49AE685FAB4B9F17F66B1F609F@SJCEML521-MBB.china.huawei.com> <039901d49143$5d6dcba0$4001a8c0@gateway.2wire.net> <4A95BA014132FF49AE685FAB4B9F17F66B20E18F@sjceml521-mbs.china.huawei.com>
In-Reply-To: <4A95BA014132FF49AE685FAB4B9F17F66B20E18F@sjceml521-mbs.china.huawei.com>
From: "Mr. Jaehoon Paul Jeong" <jaehoon.paul@gmail.com>
Date: Wed, 12 Dec 2018 10:06:52 +0900
Message-ID: <CAPK2Dey7njzgUkWyfgicu3GrJdCtO7yurgEAo=+ZTB1e1kVjjA@mail.gmail.com>
To: Linda Dunbar <linda.dunbar@huawei.com>
Cc: ietfc@btconnect.com, opsawg@ietf.org,  draft-hong-i2nsf-nsf-monitoring-data-model@ietf.org,  "i2nsf@ietf.org" <i2nsf@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000003a0613057cc8d292"
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2nsf/oED-GhhwANj8D0Zwm1G4n1_UfhQ>
Subject: Re: [I2nsf] [OPSAWG] is there any work in Ops Area for monitoring network functions?
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, 12 Dec 2018 01:07:30 -0000

--0000000000003a0613057cc8d292
Content-Type: text/plain; charset="UTF-8"

Hi Linda,
We authors will reflect Tom's comments on the revision.

Thanks.

Best Regards,
Paul

On Wed, Dec 12, 2018 at 1:12 AM Linda Dunbar <linda.dunbar@huawei.com>
wrote:

> Tom,
>
> Thank you very much for the review and comments. So there is no duplicated
> work in OpsArea?
>
>
> Authors of the draft-hong-i2nsf-nsf-monitoring-data-model: Can you please
> update the draft per Tom's comments.
>
> Linda.
>
> -----Original Message-----
> From: tom petch [mailto:ietfc@btconnect.com]
> Sent: Tuesday, December 11, 2018 5:22 AM
> To: Linda Dunbar <linda.dunbar@huawei.com>; opsawg@ietf.org
> Cc: i2nsf@ietf.org
> Subject: Re: [OPSAWG] is there any work in Ops Area for monitoring network
> functions?
>
> Linda
>
> I looked at the draft and think that it needs some work before it is a
> YANG module:-)
>
> - NMDA conformance is not mentioned
>
> - the reference to RFC2119 is out of date
>
> - the format for tree diagrams is now specified in RFC8340
>
> - YANG import statements lack 'reference' as in
>      import ietf-inet-types {
>        prefix "inet";
>        reference "RFC 6991 - Common YANG Data Types";
>
> - YANG module has no copyright
>
> - YANG module has (almost) no reference statements to tell the user (like
> me)  whereto go to understand it. look, for example, at
> draft-ietf-opsawg-nat-yang for a module that is well supplied with
> reference statements
>
> - YANG module should reference the RFC from which it comes
>
> - the one and only reference in the YANG module is
>       reference
>          "draft-zhang-i2nsf-info-model-monitoring-07";
> but the I-D is
>          draft-hong-i2nsf-nsf-monitoring-data-model-06
> I do not understand
>
> - where you reference an I-D, it needs a Note to the RFC Editor e.g.
>  reference       "draft-zhang-i2nsf-info-model-monitoring-07";
> becomes
>  reference RFC YYYY "....."
> -- Note to RFC Editor please replace YYYY with the number assigned to
>          "draft-zhang-i2nsf-info-model-monitoring"
>
> - IANA Considerations must be present
>
> - Security Considerations must include the YANG template
>
> HTH:-)
>
> I am not on the I2NSF list.
>
> Tom Petch
>
> ----- Original Message -----
> From: "Linda Dunbar" <linda.dunbar@huawei.com>
> To: <opsawg@ietf.org>
> Cc: <i2nsf@ietf.org>
> Sent: Wednesday, December 05, 2018 5:27 PM
>
> > OpsaWG:
> >
> > I2NSF WG has a draft on data models (and information model) of
> monitoring network security functions:
> https://tools.ietf.org/html/draft-hong-i2nsf-nsf-monitoring-data-model-0
> 6
> >
> > It includes data models to retrieve System Alarms, System Events,
> counters, NSF Events/logs, etc.
> >
> > Want to see if there are data models already specified by Ops Area for
> monitoring network functions which might have some common attributes that
> I2NSF can import.
> >
> > Thanks, Linda Dunbar
> >
> > From: Mr. Jaehoon Paul Jeong [mailto:jaehoon.paul@gmail.com]
> > Sent: Thursday, November 15, 2018 6:35 PM
> > To: Linda Dunbar
> <linda.dunbar@huawei.com<mailto:linda.dunbar@huawei.com>>; Yoav Nir <
> ynir.ietf@gmail.com<mailto:ynir.ietf@gmail.com>>
> > Cc: i2nsf@ietf.org<mailto:i2nsf@ietf.org>;
> skku_secu-brain_all@googlegroups.com<mailto:skku_secu-brain_all@googlegr
> oups.com>; Sangwon Hyun <swhyun77@gmail.com<mailto:swhyun77@gmail.com>>;
> Mr. Jaehoon Paul Jeong
> <jaehoon.paul@gmail.com<mailto:jaehoon.paul@gmail.com>>
> > Subject: Request for WG Adoption Call on NSF Monitoring Draft
> >
> > Hi Linda and Yoav,
> > As we discussed the last Bangkok meeting, I have merged the two drafts
> > of Information Model and Data Model for NSF Monitoring into a new
> > draft called
> draft-hong-i2nsf-nsf-monitoring-data-model-06:
> >
> > - Two Information and Data Model Drafts  .
> > draft-zhang-i2nsf-info-model-monitoring-07
> >  . draft-hong-i2nsf-nsf-monitoring-data-model-05
> >
> > - A Merged Data Model Draft
> >  . draft-hong-i2nsf-nsf-monitoring-data-model-06
> >  .
> https://tools.ietf.org/html/draft-hong-i2nsf-nsf-monitoring-data-model-0
> 6
> >
> > The NSF monitoring is very important to manage the I2NSF security
> service system
> > in a reliable and scalable fashion.
> >
> > Could you start a WG adoption call for this draft?
> >
> > Thanks.
> >
> > Best Regards,
> > Paul
> > --
> > ===========================
> > Mr. Jaehoon (Paul) Jeong, Ph.D.
> > Associate Professor
> > Department of Software
> > Sungkyunkwan University
> > Office: +82-31-299-4957
> > Email: jaehoon.paul@gmail.com<mailto:jaehoon.paul@gmail.com>,
> pauljeong@skku.edu<mailto:pauljeong@skku.edu>
> > Personal Homepage:
> http://iotlab.skku.edu/people-jaehoon-jeong.php<http://cpslab.skku.edu/p
> eople-jaehoon-jeong.php <http://cpslab.skku.edu/people-jaehoon-jeong.php>>
>
>

-- 
===========================
Mr. Jaehoon (Paul) Jeong, Ph.D.
Associate Professor
Department of Software
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>

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

<div dir=3D"ltr">Hi Linda,<div>We authors will reflect Tom&#39;s comments o=
n the revision.</div><div><br></div><div>Thanks.</div><div><br></div><div>B=
est Regards,</div><div>Paul</div></div><br><div class=3D"gmail_quote"><div =
dir=3D"ltr">On Wed, Dec 12, 2018 at 1:12 AM Linda Dunbar &lt;<a href=3D"mai=
lto:linda.dunbar@huawei.com">linda.dunbar@huawei.com</a>&gt; wrote:<br></di=
v><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;borde=
r-left:1px solid rgb(204,204,204);padding-left:1ex">Tom, <br>
<br>
Thank you very much for the review and comments. So there is no duplicated =
work in OpsArea? <br>
<br>
<br>
Authors of the draft-hong-i2nsf-nsf-monitoring-data-model: Can you please u=
pdate the draft per Tom&#39;s comments. <br>
<br>
Linda. <br>
<br>
-----Original Message-----<br>
From: tom petch [mailto:<a href=3D"mailto:ietfc@btconnect.com" target=3D"_b=
lank">ietfc@btconnect.com</a>] <br>
Sent: Tuesday, December 11, 2018 5:22 AM<br>
To: Linda Dunbar &lt;<a href=3D"mailto:linda.dunbar@huawei.com" target=3D"_=
blank">linda.dunbar@huawei.com</a>&gt;; <a href=3D"mailto:opsawg@ietf.org" =
target=3D"_blank">opsawg@ietf.org</a><br>
Cc: <a href=3D"mailto:i2nsf@ietf.org" target=3D"_blank">i2nsf@ietf.org</a><=
br>
Subject: Re: [OPSAWG] is there any work in Ops Area for monitoring network =
functions?<br>
<br>
Linda<br>
<br>
I looked at the draft and think that it needs some work before it is a YANG=
 module:-)<br>
<br>
- NMDA conformance is not mentioned<br>
<br>
- the reference to RFC2119 is out of date<br>
<br>
- the format for tree diagrams is now specified in RFC8340<br>
<br>
- YANG import statements lack &#39;reference&#39; as in<br>
=C2=A0 =C2=A0 =C2=A0import ietf-inet-types {<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0prefix &quot;inet&quot;;<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0reference &quot;RFC 6991 - Common YANG Data Type=
s&quot;;<br>
<br>
- YANG module has no copyright<br>
<br>
- YANG module has (almost) no reference statements to tell the user (like m=
e)=C2=A0 whereto go to understand it. look, for example, at draft-ietf-opsa=
wg-nat-yang for a module that is well supplied with reference statements<br=
>
<br>
- YANG module should reference the RFC from which it comes<br>
<br>
- the one and only reference in the YANG module is<br>
=C2=A0 =C2=A0 =C2=A0 reference<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&quot;draft-zhang-i2nsf-info-model-monito=
ring-07&quot;;<br>
but the I-D is<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0draft-hong-i2nsf-nsf-monitoring-data-mode=
l-06<br>
I do not understand<br>
<br>
- where you reference an I-D, it needs a Note to the RFC Editor e.g.<br>
=C2=A0reference=C2=A0 =C2=A0 =C2=A0 =C2=A0&quot;draft-zhang-i2nsf-info-mode=
l-monitoring-07&quot;;<br>
becomes<br>
=C2=A0reference RFC YYYY &quot;.....&quot;<br>
-- Note to RFC Editor please replace YYYY with the number assigned to<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&quot;draft-zhang-i2nsf-info-model-monito=
ring&quot;<br>
<br>
- IANA Considerations must be present<br>
<br>
- Security Considerations must include the YANG template<br>
<br>
HTH:-)<br>
<br>
I am not on the I2NSF list.<br>
<br>
Tom Petch<br>
<br>
----- Original Message -----<br>
From: &quot;Linda Dunbar&quot; &lt;<a href=3D"mailto:linda.dunbar@huawei.co=
m" target=3D"_blank">linda.dunbar@huawei.com</a>&gt;<br>
To: &lt;<a href=3D"mailto:opsawg@ietf.org" target=3D"_blank">opsawg@ietf.or=
g</a>&gt;<br>
Cc: &lt;<a href=3D"mailto:i2nsf@ietf.org" target=3D"_blank">i2nsf@ietf.org<=
/a>&gt;<br>
Sent: Wednesday, December 05, 2018 5:27 PM<br>
<br>
&gt; OpsaWG:<br>
&gt;<br>
&gt; I2NSF WG has a draft on data models (and information model) of<br>
monitoring network security functions:<br>
<a href=3D"https://tools.ietf.org/html/draft-hong-i2nsf-nsf-monitoring-data=
-model-0" rel=3D"noreferrer" target=3D"_blank">https://tools.ietf.org/html/=
draft-hong-i2nsf-nsf-monitoring-data-model-0</a><br>
6<br>
&gt;<br>
&gt; It includes data models to retrieve System Alarms, System Events,<br>
counters, NSF Events/logs, etc.<br>
&gt;<br>
&gt; Want to see if there are data models already specified by Ops Area for=
<br>
monitoring network functions which might have some common attributes that I=
2NSF can import.<br>
&gt;<br>
&gt; Thanks, Linda Dunbar<br>
&gt;<br>
&gt; From: Mr. Jaehoon Paul Jeong [mailto:<a href=3D"mailto:jaehoon.paul@gm=
ail.com" target=3D"_blank">jaehoon.paul@gmail.com</a>]<br>
&gt; Sent: Thursday, November 15, 2018 6:35 PM<br>
&gt; To: Linda Dunbar<br>
&lt;<a href=3D"mailto:linda.dunbar@huawei.com" target=3D"_blank">linda.dunb=
ar@huawei.com</a>&lt;mailto:<a href=3D"mailto:linda.dunbar@huawei.com" targ=
et=3D"_blank">linda.dunbar@huawei.com</a>&gt;&gt;; Yoav Nir &lt;<a href=3D"=
mailto:ynir.ietf@gmail.com" target=3D"_blank">ynir.ietf@gmail.com</a>&lt;ma=
ilto:<a href=3D"mailto:ynir.ietf@gmail.com" target=3D"_blank">ynir.ietf@gma=
il.com</a>&gt;&gt;<br>
&gt; Cc: <a href=3D"mailto:i2nsf@ietf.org" target=3D"_blank">i2nsf@ietf.org=
</a>&lt;mailto:<a href=3D"mailto:i2nsf@ietf.org" target=3D"_blank">i2nsf@ie=
tf.org</a>&gt;;<br>
<a href=3D"mailto:skku_secu-brain_all@googlegroups.com" target=3D"_blank">s=
kku_secu-brain_all@googlegroups.com</a>&lt;mailto:<a href=3D"mailto:skku_se=
cu-brain_all@googlegr" target=3D"_blank">skku_secu-brain_all@googlegr</a><b=
r>
<a href=3D"http://oups.com" rel=3D"noreferrer" target=3D"_blank">oups.com</=
a>&gt;; Sangwon Hyun &lt;<a href=3D"mailto:swhyun77@gmail.com" target=3D"_b=
lank">swhyun77@gmail.com</a>&lt;mailto:<a href=3D"mailto:swhyun77@gmail.com=
" target=3D"_blank">swhyun77@gmail.com</a>&gt;&gt;;<br>
Mr. Jaehoon Paul Jeong<br>
&lt;<a href=3D"mailto:jaehoon.paul@gmail.com" target=3D"_blank">jaehoon.pau=
l@gmail.com</a>&lt;mailto:<a href=3D"mailto:jaehoon.paul@gmail.com" target=
=3D"_blank">jaehoon.paul@gmail.com</a>&gt;&gt;<br>
&gt; Subject: Request for WG Adoption Call on NSF Monitoring Draft<br>
&gt;<br>
&gt; Hi Linda and Yoav,<br>
&gt; As we discussed the last Bangkok meeting, I have merged the two drafts=
 <br>
&gt; of Information Model and Data Model for NSF Monitoring into a new <br>
&gt; draft called<br>
draft-hong-i2nsf-nsf-monitoring-data-model-06:<br>
&gt;<br>
&gt; - Two Information and Data Model Drafts=C2=A0 . <br>
&gt; draft-zhang-i2nsf-info-model-monitoring-07<br>
&gt;=C2=A0 . draft-hong-i2nsf-nsf-monitoring-data-model-05<br>
&gt;<br>
&gt; - A Merged Data Model Draft<br>
&gt;=C2=A0 . draft-hong-i2nsf-nsf-monitoring-data-model-06<br>
&gt;=C2=A0 .<br>
<a href=3D"https://tools.ietf.org/html/draft-hong-i2nsf-nsf-monitoring-data=
-model-0" rel=3D"noreferrer" target=3D"_blank">https://tools.ietf.org/html/=
draft-hong-i2nsf-nsf-monitoring-data-model-0</a><br>
6<br>
&gt;<br>
&gt; The NSF monitoring is very important to manage the I2NSF security<br>
service system<br>
&gt; in a reliable and scalable fashion.<br>
&gt;<br>
&gt; Could you start a WG adoption call for this draft?<br>
&gt;<br>
&gt; Thanks.<br>
&gt;<br>
&gt; Best Regards,<br>
&gt; Paul<br>
&gt; --<br>
&gt; =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>
&gt; Mr. Jaehoon (Paul) Jeong, Ph.D.<br>
&gt; Associate Professor<br>
&gt; Department of Software<br>
&gt; Sungkyunkwan University<br>
&gt; Office: +82-31-299-4957<br>
&gt; Email: <a href=3D"mailto:jaehoon.paul@gmail.com" target=3D"_blank">jae=
hoon.paul@gmail.com</a>&lt;mailto:<a href=3D"mailto:jaehoon.paul@gmail.com"=
 target=3D"_blank">jaehoon.paul@gmail.com</a>&gt;,<br>
<a href=3D"mailto:pauljeong@skku.edu" target=3D"_blank">pauljeong@skku.edu<=
/a>&lt;mailto:<a href=3D"mailto:pauljeong@skku.edu" target=3D"_blank">paulj=
eong@skku.edu</a>&gt;<br>
&gt; Personal Homepage:<br>
<a href=3D"http://iotlab.skku.edu/people-jaehoon-jeong.php" rel=3D"noreferr=
er" target=3D"_blank">http://iotlab.skku.edu/people-jaehoon-jeong.php</a>&l=
t;<a href=3D"http://cpslab.skku.edu/people-jaehoon-jeong.php" rel=3D"norefe=
rrer" target=3D"_blank">http://cpslab.skku.edu/p<br>
eople-jaehoon-jeong.php</a>&gt;<br>
<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 Software<br>Sungkyunkwan Univers=
ity<br>Office: +82-31-299-4957<br>Email: <a href=3D"mailto:jaehoon.paul@gma=
il.com" target=3D"_blank">jaehoon.paul@gmail.com</a>,=C2=A0<a href=3D"mailt=
o:pauljeong@skku.edu" style=3D"font-size:12.8px" target=3D"_blank">pauljeon=
g@skku.edu</a><br>Personal Homepage: <a href=3D"http://cpslab.skku.edu/peop=
le-jaehoon-jeong.php" target=3D"_blank">http://iotlab.skku.edu/people-jaeho=
on-jeong.php</a><br></div></div></div></div></div></div></div></div>

--0000000000003a0613057cc8d292--


From nobody Wed Dec 12 02:38:20 2018
Return-Path: <ietfc@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 0FABA130DBE; Wed, 12 Dec 2018 02:38:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.739
X-Spam-Level: *
X-Spam-Status: No, score=1.739 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-1.459, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RATWARE_MS_HASH=2.148, RATWARE_OUTLOOK_NONAME=2.95, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 RbxW7w26zCC5; Wed, 12 Dec 2018 02:38:15 -0800 (PST)
Received: from EUR02-AM5-obe.outbound.protection.outlook.com (mail-eopbgr00103.outbound.protection.outlook.com [40.107.0.103]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E2D7B12F1AC; Wed, 12 Dec 2018 02:38:14 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=btconnect.onmicrosoft.com; s=selector1-btconnect-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=VDLzZf4teGkSypT1eoNxH9OawE+cQZhIHTuaO1bBs4A=; b=Yw6JkyuEBdt7jR6sITtzk4/oScVHFxNZytl9LfNPkAi4H32tQEN68ijEMPR21JxWIsIBJxqINjKoD/9kh/leCdsz18HDtLuMbgRU2GiJpl2lZ9EhUjQnZQuAuZThIWdazEd+peAHwYX0ww3ww9UkttvzfH3q5XUFxRLl5pVNHQA=
Received: from VI1PR07MB4717.eurprd07.prod.outlook.com (20.177.54.82) by VI1PR07MB4878.eurprd07.prod.outlook.com (20.177.200.20) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1425.9; Wed, 12 Dec 2018 10:38:12 +0000
Received: from VI1PR07MB4717.eurprd07.prod.outlook.com ([fe80::1575:d33b:33dd:c7c4]) by VI1PR07MB4717.eurprd07.prod.outlook.com ([fe80::1575:d33b:33dd:c7c4%5]) with mapi id 15.20.1425.016; Wed, 12 Dec 2018 10:38:12 +0000
From: tom petch <ietfc@btconnect.com>
To: Linda Dunbar <linda.dunbar@huawei.com>, "opsawg@ietf.org" <opsawg@ietf.org>, "draft-hong-i2nsf-nsf-monitoring-data-model@ietf.org" <draft-hong-i2nsf-nsf-monitoring-data-model@ietf.org>
CC: "i2nsf@ietf.org" <i2nsf@ietf.org>
Thread-Topic: [OPSAWG] is there any work in Ops Area for monitoring network functions?
Thread-Index: AQHUkUO1T0Lu/xD+tkuIG3RwDsQz5w==
Date: Wed, 12 Dec 2018 10:38:12 +0000
Message-ID: <012001d49206$6ed997c0$4001a8c0@gateway.2wire.net>
References: <4A95BA014132FF49AE685FAB4B9F17F66B1F609F@SJCEML521-MBB.china.huawei.com> <039901d49143$5d6dcba0$4001a8c0@gateway.2wire.net> <4A95BA014132FF49AE685FAB4B9F17F66B20E18F@sjceml521-mbs.china.huawei.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-clientproxiedby: LNXP265CA0003.GBRP265.PROD.OUTLOOK.COM (2603:10a6:600:5e::15) To VI1PR07MB4717.eurprd07.prod.outlook.com (2603:10a6:803:69::18)
x-ms-exchange-messagesentrepresentingtype: 1
x-originating-ip: [86.139.215.184]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; VI1PR07MB4878; 6:V81iYO4twnf+okKtOTI3Do1Ab+XhAwYENUWVc5G9LHYtpduhvfx7dNBQ7B/5A/mx5SjchDowD7SaLs8+fmcV2QCvVPbBF99oYXpWw4fKa1/0KhE5Jr3N5IOj3YI7cPQuAeo3mBHBy+8YI7bVMH67vFKk273EPVyt+SiBVde3KAXOQtBeeqjA9uJVkD71HqkSJr+FOpe/+YVeT1gbvFqwA6hVNW8yZOqBrmNoYkvW+7oUyTvRI8Nlob6cLVK1je6gESGZMishJaJdvuNj33kg/++ZqrkkN+wLjB0Ku2rZ+vmoo9tlBh2DQLvtO6uESiTA/E5PxvXKTcVL+TYxcmiPPhGScX0lnz27noLksuEZ91uJ3iItH0j2qAb3aY7iYoqeErM0PtTUMq+vZGoy+a0iCzpVsBfZFAsydL5S2PqUf9iwtGVu8aG+wQ+EpYtSyIgXBysE+CT+mc4t1e3aH5l1HQ==; 5:R2EsjC0GtJQlkREbURKXgr5Y7gL8gWa4mwLK0mvONHy2rekERvkBO1a9V3ZTpR1Km+twYs8ydf9drjiOxj5/+8axRH/oT+SlmP3/eXafFpalm820KRjiFEU13prr5MG7N39+t5duK3vkGNw5YW3DaK4OPcM+0BsoW8UUo3hmV8w=; 7:HzPshhC+peVc/hvzivjgmINn908IajoMViI+G4VXQp5+XDR5rNAPus2LtbmEYOkCrmvLdZ9rMvqDqlCB9nwFpVAW9Dx3xwy2ynolEeyHV++5jaqvoqGfTz0db4qLRVKrmICMGDDZW/DeqEqTLBEn6Q==
x-ms-office365-filtering-correlation-id: 0c644ed8-a8aa-4e89-9d1b-08d6601dea2a
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390098)(7020095)(4652040)(8989299)(5600074)(711020)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(2017052603328)(7193020); SRVR:VI1PR07MB4878; 
x-ms-traffictypediagnostic: VI1PR07MB4878:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=ietfc@btconnect.com; 
x-microsoft-antispam-prvs: <VI1PR07MB4878B326343F44F21A1DAAA4A0A70@VI1PR07MB4878.eurprd07.prod.outlook.com>
x-ms-exchange-senderadcheck: 1
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(3230017)(999002)(6040522)(2401047)(5005006)(8121501046)(3002001)(10201501046)(93006095)(93001095)(3231472)(944501520)(4982022)(52105112)(6055026)(148016)(149066)(150057)(6041310)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123560045)(20161123564045)(20161123562045)(20161123558120)(201708071742011)(7699051)(76991095); SRVR:VI1PR07MB4878; BCL:0; PCL:0; RULEID:; SRVR:VI1PR07MB4878; 
x-forefront-prvs: 0884AAA693
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(39860400002)(346002)(136003)(396003)(366004)(376002)(199004)(189003)(13464003)(51444003)(14444005)(14496001)(26005)(102836004)(105586002)(5660300001)(2501003)(229853002)(6486002)(44736005)(186003)(6306002)(86152003)(6512007)(305945005)(97736004)(15188155005)(1556002)(9686003)(106356001)(53936002)(256004)(110136005)(71190400001)(71200400001)(6436002)(2201001)(7736002)(316002)(86362001)(325944009)(8936002)(6116002)(84392002)(14454004)(3846002)(16799955002)(8676002)(81166006)(81156014)(478600001)(2906002)(66066001)(33896004)(76176011)(486006)(6506007)(386003)(53546011)(6246003)(4326008)(25786009)(99286004)(52116002)(966005)(68736007)(476003)(446003); DIR:OUT; SFP:1102; SCL:1; SRVR:VI1PR07MB4878; H:VI1PR07MB4717.eurprd07.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:0; MX:1; 
received-spf: None (protection.outlook.com: btconnect.com does not designate permitted sender hosts)
x-microsoft-antispam-message-info: MYeeE+ySB7FgwSAXhOe1wrPYg2ZuS9cVBAd6PQNGEwq7zFvbtnA3wnufd/yaYkMIapo4xrMWDx8XjvGowMHIuqb8Yz8qlfcAOPyss2bo37EIHbUkkxigAKhPeQFT77kWLm1UlYtf3574sv2LriI6oSfrxvUth5HrtJKXwmRIh/ctMJ187ZsO5aIayl4prkQWSp7CrOSjY1o7cBUsAUrI+THPRf2bAMK+r3jZGV6VsjiRvrIUzyd1ZANSCijWlzjIt0LcFaX4XfsRKlK0jUpjc2pS7hsapOCv2PGfKSJQfMXvFDiEnT1P3ccJrzMzxwTW
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="utf-8"
Content-ID: <5DEADF58C3543D4982466687232CB214@eurprd07.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: btconnect.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 0c644ed8-a8aa-4e89-9d1b-08d6601dea2a
X-MS-Exchange-CrossTenant-originalarrivaltime: 12 Dec 2018 10:38:12.2135 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: cf8853ed-96e5-465b-9185-806bfe185e30
X-MS-Exchange-Transport-CrossTenantHeadersStamped: VI1PR07MB4878
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2nsf/caa4xQwKDPLLLMNbHfhOn8WPEo0>
Subject: Re: [I2nsf] [OPSAWG] is there any work in Ops Area for monitoring network functions?
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, 12 Dec 2018 10:38:18 -0000

LS0tLS0gT3JpZ2luYWwgTWVzc2FnZSAtLS0tLQ0KRnJvbTogIkxpbmRhIER1bmJhciIgPGxpbmRh
LmR1bmJhckBodWF3ZWkuY29tPg0KU2VudDogVHVlc2RheSwgRGVjZW1iZXIgMTEsIDIwMTggNDox
MiBQTQ0KDQo+IFRvbSwNCj4NCj4gVGhhbmsgeW91IHZlcnkgbXVjaCBmb3IgdGhlIHJldmlldyBh
bmQgY29tbWVudHMuIFNvIHRoZXJlIGlzIG5vDQpkdXBsaWNhdGVkIHdvcmsgaW4gT3BzQXJlYT8N
Cg0KTGluZGENCg0KSSBzdXNwZWN0IHRoYXQgdGhlcmUgaXMgZHVwbGljYXRlZCB3b3JrIGJ1dCB0
aGUgYWJzZW5jZSBvZiBZQU5HDQoncmVmZXJlbmNlJyBzdGF0ZW1lbnRzIGluIHRoZSBtb2R1bGUg
bWFrZSB0aGF0IGhhcmRlciB0byBhc3Nlc3MuICBJZiB0d28NCllBTkcgbW9kdWxlcyByZWZlcmVu
Y2UgdGhlIHNhbWUgc2VjdGlvbiBvZiB0aGUgc2FtZSBkb2N1bWVudCwgdGhlbiB0aGV5DQphcmUg
bGlrZWx5IG1vZGVsbGluZyB0aGUgc2FtZSBvYmplY3QhICBFdmVuIGlmIHRoZSByZWZlcmVuY2Ug
aXMgb25seSB0bw0KdGhlIGRvY3VtZW50LCBpdCBkb2VzIG1ha2UgY29tcGFyaXNvbiBlYXNpZXIu
ICBIZXJlLCB0aGVyZSBhcmUgemVybw0KcmVmZXJlbmNlcy4NCg0KVGhlcmUgaXMgY2VydGFpbmx5
IG92ZXJsYXAgd2l0aCB3b3JrIGluIE5FVENPTkYgd2hlcmUgcHVsbC1wdXNoLCBwdWItc3ViDQph
bmQgdGhlIGxpa2UgaGF2ZSBiZWVuIG11Y2ggZGViYXRlZCwgb2Z0ZW4gaW4gYSBzZWVtaW5nbHkg
Y2lyY3VsYXINCm1hbm5lciwgd2l0aCBJLURzIHN1Y2ggYXMNCmRyYWZ0LWlldGYtbmV0Y29uZi1z
dWJzY3JpYmVkLW5vdGlmaWNhdGlvbnMNCmRyYWZ0LWlldGYtbmV0Y29uZi11ZHAtcHViLWNoYW5u
ZWwtMDMNCmRyYWZ0LWlldGYtbmV0Y29uZi15YW5nLXB1c2gNCmRyYWZ0LWlldGYtbmV0Y29uZi1u
ZXRjb25mLWV2ZW50LW5vdGlmaWNhdGlvbnMNCmRyYWZ0LWlldGYtbmV0Y29uZi1yZXN0Y29uZi1u
b3RpZg0KYnV0IHRoYXQgV0cgaXMgYWxzbyB3cmVzdGxpbmcgd2l0aCBzZXZlbiBjbGllbnQtc2Vy
dmVyIGRyYWZ0cyB3aGljaA0KaW50ZXJhY3Qgd2l0aCB0aGVtIHNvIEkgZmluZCBpdCBoYXJkIHRv
IGtlZXAgdHJhY2sgb2YgdGhpcyB3b3JrLg0KDQpPbiB0aGUgYXBwcm9hY2ggdG8gZXZlbnQvYWxh
cm0vbm90aWZpY2F0aW9uLCB0aGVyZSBpcyBvdmVybGFwIHdpdGgNCmRyYWZ0LWlldGYtY2NhbXAt
YWxhcm0tbW9kdWxlDQp3aGljaCBpcyBhbGwgYWJvdXQgYWxhcm1zIGFuZCBub3QgbXVjaCB0byBk
byB3aXRoIGNjYW1wIElNSE8uIFRoaXMgd29yaw0KaXMgYW4gZXZvbHV0aW9uIG9mIFJGQzM4Nzcg
c28gaXMgcHJvYmFibHkgdGhlIG9uZSB0aGF0IHlvdSBzaG91bGQgYmUNCmZhbWlsaWFyIHdpdGgu
ICBJIHRoaW5rIHRoYXQgaWYgdGhpcyBJLUQgbG9va3MgZGlmZmVyZW50IHRvIFJGQzM4NzcsIGl0
DQppcyBiZWNhdXNlIElUVS1UIGhhdmUgbW92ZWQgb24gYW5kIHdlIGhhdmUgZm9sbG93ZWQuDQoN
Ck9uIHRoZSBpZGVudGl0aWVzLCBpcCwgaXB2NCwgZnRwIGV0YyB0aGVyZSBpcyBvdmVybGFwIGV2
ZXJ5d2hlcmUuDQoNCk5vdCBzdXJlIHRoYXQgdGhhdCBoZWxwcyBidXQgdGhhdCBpcyB0aGUgSUVU
Ri4NCg0KVG9tIFBldGNoDQoNCj4gQXV0aG9ycyBvZiB0aGUgZHJhZnQtaG9uZy1pMm5zZi1uc2Yt
bW9uaXRvcmluZy1kYXRhLW1vZGVsOiBDYW4geW91DQpwbGVhc2UgdXBkYXRlIHRoZSBkcmFmdCBw
ZXIgVG9tJ3MgY29tbWVudHMuDQo+DQo+IExpbmRhLg0KPg0KPiAtLS0tLU9yaWdpbmFsIE1lc3Nh
Z2UtLS0tLQ0KPiBGcm9tOiB0b20gcGV0Y2ggW21haWx0bzppZXRmY0BidGNvbm5lY3QuY29tXQ0K
PiBTZW50OiBUdWVzZGF5LCBEZWNlbWJlciAxMSwgMjAxOCA1OjIyIEFNDQo+IFRvOiBMaW5kYSBE
dW5iYXIgPGxpbmRhLmR1bmJhckBodWF3ZWkuY29tPjsgb3BzYXdnQGlldGYub3JnDQo+IENjOiBp
Mm5zZkBpZXRmLm9yZw0KPiBTdWJqZWN0OiBSZTogW09QU0FXR10gaXMgdGhlcmUgYW55IHdvcmsg
aW4gT3BzIEFyZWEgZm9yIG1vbml0b3JpbmcNCm5ldHdvcmsgZnVuY3Rpb25zPw0KPg0KPiBMaW5k
YQ0KPg0KPiBJIGxvb2tlZCBhdCB0aGUgZHJhZnQgYW5kIHRoaW5rIHRoYXQgaXQgbmVlZHMgc29t
ZSB3b3JrIGJlZm9yZSBpdCBpcyBhDQpZQU5HIG1vZHVsZTotKQ0KPg0KPiAtIE5NREEgY29uZm9y
bWFuY2UgaXMgbm90IG1lbnRpb25lZA0KPg0KPiAtIHRoZSByZWZlcmVuY2UgdG8gUkZDMjExOSBp
cyBvdXQgb2YgZGF0ZQ0KPg0KPiAtIHRoZSBmb3JtYXQgZm9yIHRyZWUgZGlhZ3JhbXMgaXMgbm93
IHNwZWNpZmllZCBpbiBSRkM4MzQwDQo+DQo+IC0gWUFORyBpbXBvcnQgc3RhdGVtZW50cyBsYWNr
ICdyZWZlcmVuY2UnIGFzIGluDQo+ICAgICAgaW1wb3J0IGlldGYtaW5ldC10eXBlcyB7DQo+ICAg
ICAgICBwcmVmaXggImluZXQiOw0KPiAgICAgICAgcmVmZXJlbmNlICJSRkMgNjk5MSAtIENvbW1v
biBZQU5HIERhdGEgVHlwZXMiOw0KPg0KPiAtIFlBTkcgbW9kdWxlIGhhcyBubyBjb3B5cmlnaHQN
Cj4NCj4gLSBZQU5HIG1vZHVsZSBoYXMgKGFsbW9zdCkgbm8gcmVmZXJlbmNlIHN0YXRlbWVudHMg
dG8gdGVsbCB0aGUgdXNlcg0KKGxpa2UgbWUpICB3aGVyZXRvIGdvIHRvIHVuZGVyc3RhbmQgaXQu
IGxvb2ssIGZvciBleGFtcGxlLCBhdA0KZHJhZnQtaWV0Zi1vcHNhd2ctbmF0LXlhbmcgZm9yIGEg
bW9kdWxlIHRoYXQgaXMgd2VsbCBzdXBwbGllZCB3aXRoDQpyZWZlcmVuY2Ugc3RhdGVtZW50cw0K
Pg0KPiAtIFlBTkcgbW9kdWxlIHNob3VsZCByZWZlcmVuY2UgdGhlIFJGQyBmcm9tIHdoaWNoIGl0
IGNvbWVzDQo+DQo+IC0gdGhlIG9uZSBhbmQgb25seSByZWZlcmVuY2UgaW4gdGhlIFlBTkcgbW9k
dWxlIGlzDQo+ICAgICAgIHJlZmVyZW5jZQ0KPiAgICAgICAgICAiZHJhZnQtemhhbmctaTJuc2Yt
aW5mby1tb2RlbC1tb25pdG9yaW5nLTA3IjsNCj4gYnV0IHRoZSBJLUQgaXMNCj4gICAgICAgICAg
ZHJhZnQtaG9uZy1pMm5zZi1uc2YtbW9uaXRvcmluZy1kYXRhLW1vZGVsLTA2DQo+IEkgZG8gbm90
IHVuZGVyc3RhbmQNCj4NCj4gLSB3aGVyZSB5b3UgcmVmZXJlbmNlIGFuIEktRCwgaXQgbmVlZHMg
YSBOb3RlIHRvIHRoZSBSRkMgRWRpdG9yIGUuZy4NCj4gIHJlZmVyZW5jZSAgICAgICAiZHJhZnQt
emhhbmctaTJuc2YtaW5mby1tb2RlbC1tb25pdG9yaW5nLTA3IjsNCj4gYmVjb21lcw0KPiAgcmVm
ZXJlbmNlIFJGQyBZWVlZICIuLi4uLiINCj4gLS0gTm90ZSB0byBSRkMgRWRpdG9yIHBsZWFzZSBy
ZXBsYWNlIFlZWVkgd2l0aCB0aGUgbnVtYmVyIGFzc2lnbmVkIHRvDQo+ICAgICAgICAgICJkcmFm
dC16aGFuZy1pMm5zZi1pbmZvLW1vZGVsLW1vbml0b3JpbmciDQo+DQo+IC0gSUFOQSBDb25zaWRl
cmF0aW9ucyBtdXN0IGJlIHByZXNlbnQNCj4NCj4gLSBTZWN1cml0eSBDb25zaWRlcmF0aW9ucyBt
dXN0IGluY2x1ZGUgdGhlIFlBTkcgdGVtcGxhdGUNCj4NCj4gSFRIOi0pDQo+DQo+IEkgYW0gbm90
IG9uIHRoZSBJMk5TRiBsaXN0Lg0KPg0KPiBUb20gUGV0Y2gNCj4NCj4gLS0tLS0gT3JpZ2luYWwg
TWVzc2FnZSAtLS0tLQ0KPiBGcm9tOiAiTGluZGEgRHVuYmFyIiA8bGluZGEuZHVuYmFyQGh1YXdl
aS5jb20+DQo+IFRvOiA8b3BzYXdnQGlldGYub3JnPg0KPiBDYzogPGkybnNmQGlldGYub3JnPg0K
PiBTZW50OiBXZWRuZXNkYXksIERlY2VtYmVyIDA1LCAyMDE4IDU6MjcgUE0NCj4NCj4gPiBPcHNh
V0c6DQo+ID4NCj4gPiBJMk5TRiBXRyBoYXMgYSBkcmFmdCBvbiBkYXRhIG1vZGVscyAoYW5kIGlu
Zm9ybWF0aW9uIG1vZGVsKSBvZg0KPiBtb25pdG9yaW5nIG5ldHdvcmsgc2VjdXJpdHkgZnVuY3Rp
b25zOg0KPg0KaHR0cHM6Ly90b29scy5pZXRmLm9yZy9odG1sL2RyYWZ0LWhvbmctaTJuc2YtbnNm
LW1vbml0b3JpbmctZGF0YS1tb2RlbC0wDQo+IDYNCj4gPg0KPiA+IEl0IGluY2x1ZGVzIGRhdGEg
bW9kZWxzIHRvIHJldHJpZXZlIFN5c3RlbSBBbGFybXMsIFN5c3RlbSBFdmVudHMsDQo+IGNvdW50
ZXJzLCBOU0YgRXZlbnRzL2xvZ3MsIGV0Yy4NCj4gPg0KPiA+IFdhbnQgdG8gc2VlIGlmIHRoZXJl
IGFyZSBkYXRhIG1vZGVscyBhbHJlYWR5IHNwZWNpZmllZCBieSBPcHMgQXJlYQ0KZm9yDQo+IG1v
bml0b3JpbmcgbmV0d29yayBmdW5jdGlvbnMgd2hpY2ggbWlnaHQgaGF2ZSBzb21lIGNvbW1vbiBh
dHRyaWJ1dGVzDQp0aGF0IEkyTlNGIGNhbiBpbXBvcnQuDQo+ID4NCj4gPiBUaGFua3MsIExpbmRh
IER1bmJhcg0KPiA+DQo+ID4gRnJvbTogTXIuIEphZWhvb24gUGF1bCBKZW9uZyBbbWFpbHRvOmph
ZWhvb24ucGF1bEBnbWFpbC5jb21dDQo+ID4gU2VudDogVGh1cnNkYXksIE5vdmVtYmVyIDE1LCAy
MDE4IDY6MzUgUE0NCj4gPiBUbzogTGluZGEgRHVuYmFyDQo+IDxsaW5kYS5kdW5iYXJAaHVhd2Vp
LmNvbTxtYWlsdG86bGluZGEuZHVuYmFyQGh1YXdlaS5jb20+PjsgWW9hdiBOaXINCjx5bmlyLmll
dGZAZ21haWwuY29tPG1haWx0bzp5bmlyLmlldGZAZ21haWwuY29tPj4NCj4gPiBDYzogaTJuc2ZA
aWV0Zi5vcmc8bWFpbHRvOmkybnNmQGlldGYub3JnPjsNCj4NCnNra3Vfc2VjdS1icmFpbl9hbGxA
Z29vZ2xlZ3JvdXBzLmNvbTxtYWlsdG86c2trdV9zZWN1LWJyYWluX2FsbEBnb29nbGVncg0KPiBv
dXBzLmNvbT47IFNhbmd3b24gSHl1bg0KPHN3aHl1bjc3QGdtYWlsLmNvbTxtYWlsdG86c3doeXVu
NzdAZ21haWwuY29tPj47DQo+IE1yLiBKYWVob29uIFBhdWwgSmVvbmcNCj4gPGphZWhvb24ucGF1
bEBnbWFpbC5jb208bWFpbHRvOmphZWhvb24ucGF1bEBnbWFpbC5jb20+Pg0KPiA+IFN1YmplY3Q6
IFJlcXVlc3QgZm9yIFdHIEFkb3B0aW9uIENhbGwgb24gTlNGIE1vbml0b3JpbmcgRHJhZnQNCj4g
Pg0KPiA+IEhpIExpbmRhIGFuZCBZb2F2LA0KPiA+IEFzIHdlIGRpc2N1c3NlZCB0aGUgbGFzdCBC
YW5na29rIG1lZXRpbmcsIEkgaGF2ZSBtZXJnZWQgdGhlIHR3bw0KZHJhZnRzDQo+ID4gb2YgSW5m
b3JtYXRpb24gTW9kZWwgYW5kIERhdGEgTW9kZWwgZm9yIE5TRiBNb25pdG9yaW5nIGludG8gYSBu
ZXcNCj4gPiBkcmFmdCBjYWxsZWQNCj4gZHJhZnQtaG9uZy1pMm5zZi1uc2YtbW9uaXRvcmluZy1k
YXRhLW1vZGVsLTA2Og0KPiA+DQo+ID4gLSBUd28gSW5mb3JtYXRpb24gYW5kIERhdGEgTW9kZWwg
RHJhZnRzICAuDQo+ID4gZHJhZnQtemhhbmctaTJuc2YtaW5mby1tb2RlbC1tb25pdG9yaW5nLTA3
DQo+ID4gIC4gZHJhZnQtaG9uZy1pMm5zZi1uc2YtbW9uaXRvcmluZy1kYXRhLW1vZGVsLTA1DQo+
ID4NCj4gPiAtIEEgTWVyZ2VkIERhdGEgTW9kZWwgRHJhZnQNCj4gPiAgLiBkcmFmdC1ob25nLWky
bnNmLW5zZi1tb25pdG9yaW5nLWRhdGEtbW9kZWwtMDYNCj4gPiAgLg0KPg0KaHR0cHM6Ly90b29s
cy5pZXRmLm9yZy9odG1sL2RyYWZ0LWhvbmctaTJuc2YtbnNmLW1vbml0b3JpbmctZGF0YS1tb2Rl
bC0wDQo+IDYNCj4gPg0KPiA+IFRoZSBOU0YgbW9uaXRvcmluZyBpcyB2ZXJ5IGltcG9ydGFudCB0
byBtYW5hZ2UgdGhlIEkyTlNGIHNlY3VyaXR5DQo+IHNlcnZpY2Ugc3lzdGVtDQo+ID4gaW4gYSBy
ZWxpYWJsZSBhbmQgc2NhbGFibGUgZmFzaGlvbi4NCj4gPg0KPiA+IENvdWxkIHlvdSBzdGFydCBh
IFdHIGFkb3B0aW9uIGNhbGwgZm9yIHRoaXMgZHJhZnQ/DQo+ID4NCj4gPiBUaGFua3MuDQo+ID4N
Cj4gPiBCZXN0IFJlZ2FyZHMsDQo+ID4gUGF1bA0KPiA+IC0tDQo+ID4gPT09PT09PT09PT09PT09
PT09PT09PT09PT09DQo+ID4gTXIuIEphZWhvb24gKFBhdWwpIEplb25nLCBQaC5ELg0KPiA+IEFz
c29jaWF0ZSBQcm9mZXNzb3INCj4gPiBEZXBhcnRtZW50IG9mIFNvZnR3YXJlDQo+ID4gU3VuZ2t5
dW5rd2FuIFVuaXZlcnNpdHkNCj4gPiBPZmZpY2U6ICs4Mi0zMS0yOTktNDk1Nw0KPiA+IEVtYWls
OiBqYWVob29uLnBhdWxAZ21haWwuY29tPG1haWx0bzpqYWVob29uLnBhdWxAZ21haWwuY29tPiwN
Cj4gcGF1bGplb25nQHNra3UuZWR1PG1haWx0bzpwYXVsamVvbmdAc2trdS5lZHU+DQo+ID4gUGVy
c29uYWwgSG9tZXBhZ2U6DQo+DQpodHRwOi8vaW90bGFiLnNra3UuZWR1L3Blb3BsZS1qYWVob29u
LWplb25nLnBocDxodHRwOi8vY3BzbGFiLnNra3UuZWR1L3ANCj4gZW9wbGUtamFlaG9vbi1qZW9u
Zy5waHA+DQo+DQo+DQoNCg==


From nobody Wed Dec 19 15:16:26 2018
Return-Path: <linda.dunbar@huawei.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 0976F12D4F0 for <i2nsf@ietfa.amsl.com>; Wed, 19 Dec 2018 15:16:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-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 RnGBIyF9wjrg for <i2nsf@ietfa.amsl.com>; Wed, 19 Dec 2018 15:16:21 -0800 (PST)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (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 60D58126F72 for <i2nsf@ietf.org>; Wed, 19 Dec 2018 15:16:21 -0800 (PST)
Received: from lhreml702-cah.china.huawei.com (unknown [172.18.7.107]) by Forcepoint Email with ESMTP id 5C238781DD9C for <i2nsf@ietf.org>; Wed, 19 Dec 2018 23:16:16 +0000 (GMT)
Received: from SJCEML702-CHM.china.huawei.com (10.208.112.38) by lhreml702-cah.china.huawei.com (10.201.108.43) with Microsoft SMTP Server (TLS) id 14.3.408.0; Wed, 19 Dec 2018 23:16:17 +0000
Received: from SJCEML521-MBS.china.huawei.com ([169.254.2.185]) by SJCEML702-CHM.china.huawei.com ([169.254.4.220]) with mapi id 14.03.0415.000;  Wed, 19 Dec 2018 15:16:14 -0800
From: Linda Dunbar <linda.dunbar@huawei.com>
To: "i2nsf@ietf.org" <i2nsf@ietf.org>
Thread-Topic: Call for WG Adoption on NSF Monitoring Draft has been closed
Thread-Index: AdSX8IdEeC6vkOGIQF22XOn98pFdIA==
Date: Wed, 19 Dec 2018 23:16:13 +0000
Message-ID: <4A95BA014132FF49AE685FAB4B9F17F66B21A81B@sjceml521-mbs.china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.192.11.95]
Content-Type: multipart/alternative; boundary="_000_4A95BA014132FF49AE685FAB4B9F17F66B21A81Bsjceml521mbschi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2nsf/9aXpbAGubKCjtrBg-qcqK-aDpR8>
Subject: [I2nsf] Call for WG Adoption on NSF Monitoring Draft has been closed
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, 19 Dec 2018 23:16:24 -0000

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

V2UgaGF2ZSBnb3Qgc3VmZmljaWVudCBzdXBwb3J0IGZvciBhZG9wdGluZyB0aGUgaHR0cHM6Ly90
b29scy5pZXRmLm9yZy9odG1sL2RyYWZ0LWhvbmctaTJuc2YtbnNmLW1vbml0b3JpbmctZGF0YS1t
b2RlbC0wNiBhcyBJMk5TRiBXRyBkcmFmdC4NCg0KQXV0aG9yczogcGxlYXNlIGFkZHJlc3MgYWxs
IHRoZSBjb21tZW50cyBjb21pbmcgZnJvbSB0aGUgV0cgQWRvcHRpb24gQ2FsbCBwcm9jZXNzIGFu
ZCB1cGxvYWQgdGhlIHJldmlzZWQgZHJhZnQgaW4gdGhlIG5hbWUgb2Yg4oCcZHJhZnQtaWV0Zi1p
Mm5zZi1uc2YtbW9uaXRvcmluZy1kYXRhLW1vZGVs4oCdLg0KDQpUaGFua3MgdG8gZXZlcnlvbmUg
cmV2aWV3aW5nIHRoZSBkcmFmdCBhbmQgcHJvdmlkaW5nIHRoZSBjb21tZW50cy4NCg0KTGluZGEg
JiBZb2F2DQoNCkZyb206IExpbmRhIER1bmJhcg0KU2VudDogV2VkbmVzZGF5LCBEZWNlbWJlciAw
NSwgMjAxOCA0OjMyIFBNDQpUbzogJ2kybnNmQGlldGYub3JnJyA8aTJuc2ZAaWV0Zi5vcmc+DQpT
dWJqZWN0OiBDYWxsIGZvciBXRyBBZG9wdGlvbiBvbiBOU0YgTW9uaXRvcmluZyBEcmFmdA0KDQpU
aGlzIGlzIHRoZSBzdGFydCBvZiBhIHR3byB3ZWVrcyBjYWxsIGZvciBpbnB1dCBvbiB0aGUgV0cg
YWRvcHRpb24gb2YgdGhlIGRvY3VtZW50OiBodHRwczovL3Rvb2xzLmlldGYub3JnL2h0bWwvZHJh
ZnQtaG9uZy1pMm5zZi1uc2YtbW9uaXRvcmluZy1kYXRhLW1vZGVsLTA2DQoNClRoYW5rcyBmb3Ig
dGhlIGF1dGhvcnMgb2YgdGhlIHR3byBJMk5TRiBNb25pdG9yaW5nIGRyYWZ0cyB0YWtpbmcgYWN0
aW9ucyBvZiBtZXJnaW5nIHRoZSBjb250ZW50Lg0KV2UgbmVlZCBtb3JlIG9mIHRob3NlIGFjdGlv
bnMuIEFzIG9mIG5vdyB3ZSBoYXZlIDggV0cgZHJhZnRzLiBXZSBuZWVkIHRvIGZpbmlzaCB0aGVt
IG5leHQgZmV3IG1vbnRocy4NCg0KQmVhciBpbiBtaW5kIHRoYXQgV0cgYWRvcHRpb24gZG9lc27i
gJl0IG1lYW4gdGhlIGRyYWZ0IGlzIHJlYWR5LCBvbmx5IG1lYW5zIHRoYXQgV0cgd2lsbCB3b3Jr
IHRvZ2V0aGVyIG9uIHRoZSBkcmFmdCAoaW5zdGVhZCBvZiBpbmRpdmlkdWFscykuDQoNClBsZWFz
ZSBwcm92aWRlIGZlZWRiYWNrIHRvIHRoZSBsaXN0L2NoYWlycyBpZiB5b3UgYmVsaWV2ZSB0aGF0
IHRoaXMgZG9jdW1lbnQgc2hvdWxkIGJlIGFkb3B0ZWQgYXMgYSBXRyBkb2N1bWVudC4NCg0KVGhh
bmtzLA0KDQpMaW5kYSAmIFlvYXYNCg0KDQpGcm9tOiBNci4gSmFlaG9vbiBQYXVsIEplb25nIFtt
YWlsdG86amFlaG9vbi5wYXVsQGdtYWlsLmNvbV0NClNlbnQ6IFRodXJzZGF5LCBOb3ZlbWJlciAx
NSwgMjAxOCA2OjM1IFBNDQpUbzogTGluZGEgRHVuYmFyIDxsaW5kYS5kdW5iYXJAaHVhd2VpLmNv
bTxtYWlsdG86bGluZGEuZHVuYmFyQGh1YXdlaS5jb20+PjsgWW9hdiBOaXIgPHluaXIuaWV0ZkBn
bWFpbC5jb208bWFpbHRvOnluaXIuaWV0ZkBnbWFpbC5jb20+Pg0KQ2M6IGkybnNmQGlldGYub3Jn
PG1haWx0bzppMm5zZkBpZXRmLm9yZz47IHNra3Vfc2VjdS1icmFpbl9hbGxAZ29vZ2xlZ3JvdXBz
LmNvbTxtYWlsdG86c2trdV9zZWN1LWJyYWluX2FsbEBnb29nbGVncm91cHMuY29tPjsgU2FuZ3dv
biBIeXVuIDxzd2h5dW43N0BnbWFpbC5jb208bWFpbHRvOnN3aHl1bjc3QGdtYWlsLmNvbT4+OyBN
ci4gSmFlaG9vbiBQYXVsIEplb25nIDxqYWVob29uLnBhdWxAZ21haWwuY29tPG1haWx0bzpqYWVo
b29uLnBhdWxAZ21haWwuY29tPj4NClN1YmplY3Q6IFJlcXVlc3QgZm9yIFdHIEFkb3B0aW9uIENh
bGwgb24gTlNGIE1vbml0b3JpbmcgRHJhZnQNCg0KSGkgTGluZGEgYW5kIFlvYXYsDQpBcyB3ZSBk
aXNjdXNzZWQgdGhlIGxhc3QgQmFuZ2tvayBtZWV0aW5nLA0KSSBoYXZlIG1lcmdlZCB0aGUgdHdv
IGRyYWZ0cyBvZiBJbmZvcm1hdGlvbiBNb2RlbCBhbmQgRGF0YSBNb2RlbA0KZm9yIE5TRiBNb25p
dG9yaW5nIGludG8gYSBuZXcgZHJhZnQgY2FsbGVkIGRyYWZ0LWhvbmctaTJuc2YtbnNmLW1vbml0
b3JpbmctZGF0YS1tb2RlbC0wNjoNCg0KLSBUd28gSW5mb3JtYXRpb24gYW5kIERhdGEgTW9kZWwg
RHJhZnRzDQogLiBkcmFmdC16aGFuZy1pMm5zZi1pbmZvLW1vZGVsLW1vbml0b3JpbmctMDcNCiAu
IGRyYWZ0LWhvbmctaTJuc2YtbnNmLW1vbml0b3JpbmctZGF0YS1tb2RlbC0wNQ0KDQotIEEgTWVy
Z2VkIERhdGEgTW9kZWwgRHJhZnQNCiAuIGRyYWZ0LWhvbmctaTJuc2YtbnNmLW1vbml0b3Jpbmct
ZGF0YS1tb2RlbC0wNg0KIC4gaHR0cHM6Ly90b29scy5pZXRmLm9yZy9odG1sL2RyYWZ0LWhvbmct
aTJuc2YtbnNmLW1vbml0b3JpbmctZGF0YS1tb2RlbC0wNg0KDQpUaGUgTlNGIG1vbml0b3Jpbmcg
aXMgdmVyeSBpbXBvcnRhbnQgdG8gbWFuYWdlIHRoZSBJMk5TRiBzZWN1cml0eSBzZXJ2aWNlIHN5
c3RlbQ0KaW4gYSByZWxpYWJsZSBhbmQgc2NhbGFibGUgZmFzaGlvbi4NCg0KQ291bGQgeW91IHN0
YXJ0IGEgV0cgYWRvcHRpb24gY2FsbCBmb3IgdGhpcyBkcmFmdD8NCg0KVGhhbmtzLg0KDQpCZXN0
IFJlZ2FyZHMsDQpQYXVsDQotLQ0KPT09PT09PT09PT09PT09PT09PT09PT09PT09DQpNci4gSmFl
aG9vbiAoUGF1bCkgSmVvbmcsIFBoLkQuDQpBc3NvY2lhdGUgUHJvZmVzc29yDQpEZXBhcnRtZW50
IG9mIFNvZnR3YXJlDQpTdW5na3l1bmt3YW4gVW5pdmVyc2l0eQ0KT2ZmaWNlOiArODItMzEtMjk5
LTQ5NTcNCkVtYWlsOiBqYWVob29uLnBhdWxAZ21haWwuY29tPG1haWx0bzpqYWVob29uLnBhdWxA
Z21haWwuY29tPiwgcGF1bGplb25nQHNra3UuZWR1PG1haWx0bzpwYXVsamVvbmdAc2trdS5lZHU+
DQpQZXJzb25hbCBIb21lcGFnZTogaHR0cDovL2lvdGxhYi5za2t1LmVkdS9wZW9wbGUtamFlaG9v
bi1qZW9uZy5waHA8aHR0cDovL2Nwc2xhYi5za2t1LmVkdS9wZW9wbGUtamFlaG9vbi1qZW9uZy5w
aHA+DQo=

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

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTUgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
U2ltU3VuOw0KCXBhbm9zZS0xOjIgMSA2IDAgMyAxIDEgMSAxIDE7fQ0KQGZvbnQtZmFjZQ0KCXtm
b250LWZhbWlseToiQ2FtYnJpYSBNYXRoIjsNCglwYW5vc2UtMToyIDQgNSAzIDUgNCA2IDMgMiA0
O30NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6Q2FsaWJyaTsNCglwYW5vc2UtMToyIDE1IDUg
MiAyIDIgNCAzIDIgNDt9DQpAZm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5OiJcQFNpbVN1biI7DQoJ
cGFub3NlLTE6MiAxIDYgMCAzIDEgMSAxIDEgMTt9DQovKiBTdHlsZSBEZWZpbml0aW9ucyAqLw0K
cC5Nc29Ob3JtYWwsIGxpLk1zb05vcm1hbCwgZGl2Lk1zb05vcm1hbA0KCXttYXJnaW46MGluOw0K
CW1hcmdpbi1ib3R0b206LjAwMDFwdDsNCglmb250LXNpemU6MTIuMHB0Ow0KCWZvbnQtZmFtaWx5
OiJUaW1lcyBOZXcgUm9tYW4iLHNlcmlmO30NCmE6bGluaywgc3Bhbi5Nc29IeXBlcmxpbmsNCgl7
bXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0KCWNvbG9yOmJsdWU7DQoJdGV4dC1kZWNvcmF0aW9uOnVu
ZGVybGluZTt9DQphOnZpc2l0ZWQsIHNwYW4uTXNvSHlwZXJsaW5rRm9sbG93ZWQNCgl7bXNvLXN0
eWxlLXByaW9yaXR5Ojk5Ow0KCWNvbG9yOnB1cnBsZTsNCgl0ZXh0LWRlY29yYXRpb246dW5kZXJs
aW5lO30NCnNwYW4uRW1haWxTdHlsZTE3DQoJe21zby1zdHlsZS10eXBlOnBlcnNvbmFsOw0KCWZv
bnQtZmFtaWx5OiJDYWxpYnJpIixzYW5zLXNlcmlmOw0KCWNvbG9yOiMxRjQ5N0Q7fQ0Kc3Bhbi5F
bWFpbFN0eWxlMTgNCgl7bXNvLXN0eWxlLXR5cGU6cGVyc29uYWwtcmVwbHk7DQoJZm9udC1mYW1p
bHk6IkNhbGlicmkiLHNhbnMtc2VyaWY7DQoJY29sb3I6IzFGNDk3RDt9DQouTXNvQ2hwRGVmYXVs
dA0KCXttc28tc3R5bGUtdHlwZTpleHBvcnQtb25seTsNCglmb250LXNpemU6MTAuMHB0O30NCkBw
YWdlIFdvcmRTZWN0aW9uMQ0KCXtzaXplOjguNWluIDExLjBpbjsNCgltYXJnaW46MS4waW4gMS4w
aW4gMS4waW4gMS4waW47fQ0KZGl2LldvcmRTZWN0aW9uMQ0KCXtwYWdlOldvcmRTZWN0aW9uMTt9
DQotLT48L3N0eWxlPjwhLS1baWYgZ3RlIG1zbyA5XT48eG1sPg0KPG86c2hhcGVkZWZhdWx0cyB2
OmV4dD0iZWRpdCIgc3BpZG1heD0iMTAyNiIgLz4NCjwveG1sPjwhW2VuZGlmXS0tPjwhLS1baWYg
Z3RlIG1zbyA5XT48eG1sPg0KPG86c2hhcGVsYXlvdXQgdjpleHQ9ImVkaXQiPg0KPG86aWRtYXAg
djpleHQ9ImVkaXQiIGRhdGE9IjEiIC8+DQo8L286c2hhcGVsYXlvdXQ+PC94bWw+PCFbZW5kaWZd
LS0+DQo8L2hlYWQ+DQo8Ym9keSBsYW5nPSJFTi1VUyIgbGluaz0iYmx1ZSIgdmxpbms9InB1cnBs
ZSI+DQo8ZGl2IGNsYXNzPSJXb3JkU2VjdGlvbjEiPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNw
YW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90
OyxzYW5zLXNlcmlmO2NvbG9yOiMxRjQ5N0QiPldlIGhhdmUgZ290IHN1ZmZpY2llbnQgc3VwcG9y
dCBmb3IgYWRvcHRpbmcgdGhlDQo8L3NwYW4+PGEgaHJlZj0iaHR0cHM6Ly90b29scy5pZXRmLm9y
Zy9odG1sL2RyYWZ0LWhvbmctaTJuc2YtbnNmLW1vbml0b3JpbmctZGF0YS1tb2RlbC0wNiI+aHR0
cHM6Ly90b29scy5pZXRmLm9yZy9odG1sL2RyYWZ0LWhvbmctaTJuc2YtbnNmLW1vbml0b3Jpbmct
ZGF0YS1tb2RlbC0wNjwvYT48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWls
eTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6IzFGNDk3RCI+IGFzIEkyTlNG
IFdHDQogZHJhZnQuIDxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
PjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkm
cXVvdDssc2Fucy1zZXJpZjtjb2xvcjojMUY0OTdEIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48
L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtm
b250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6IzFGNDk3RCI+
QXV0aG9yczogcGxlYXNlIGFkZHJlc3MgYWxsIHRoZSBjb21tZW50cyBjb21pbmcgZnJvbSB0aGUg
V0cgQWRvcHRpb24gQ2FsbCBwcm9jZXNzIGFuZCB1cGxvYWQgdGhlIHJldmlzZWQgZHJhZnQgaW4g
dGhlIG5hbWUgb2Yg4oCcZHJhZnQtaWV0Zi1pMm5zZi1uc2YtbW9uaXRvcmluZy1kYXRhLW1vZGVs
4oCdLg0KPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4g
c3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90Oyxz
YW5zLXNlcmlmO2NvbG9yOiMxRjQ5N0QiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFt
aWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjojMUY0OTdEIj5UaGFua3Mg
dG8gZXZlcnlvbmUgcmV2aWV3aW5nIHRoZSBkcmFmdCBhbmQgcHJvdmlkaW5nIHRoZSBjb21tZW50
cy4NCjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0
eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fu
cy1zZXJpZjtjb2xvcjojMUY0OTdEIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWls
eTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6IzFGNDk3RCI+TGluZGEgJmFt
cDsgWW9hdjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxhIG5h
bWU9Il9NYWlsRW5kQ29tcG9zZSI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1m
YW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOiMxRjQ5N0QiPjxvOnA+
Jm5ic3A7PC9vOnA+PC9zcGFuPjwvYT48L3A+DQo8ZGl2Pg0KPGRpdiBzdHlsZT0iYm9yZGVyOm5v
bmU7Ym9yZGVyLXRvcDpzb2xpZCAjRTFFMUUxIDEuMHB0O3BhZGRpbmc6My4wcHQgMGluIDBpbiAw
aW4iPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PGI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4w
cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmIj5Gcm9tOjwvc3Bh
bj48L2I+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2Fs
aWJyaSZxdW90OyxzYW5zLXNlcmlmIj4gTGluZGEgRHVuYmFyDQo8YnI+DQo8Yj5TZW50OjwvYj4g
V2VkbmVzZGF5LCBEZWNlbWJlciAwNSwgMjAxOCA0OjMyIFBNPGJyPg0KPGI+VG86PC9iPiAnaTJu
c2ZAaWV0Zi5vcmcnICZsdDtpMm5zZkBpZXRmLm9yZyZndDs8YnI+DQo8Yj5TdWJqZWN0OjwvYj4g
Q2FsbCBmb3IgV0cgQWRvcHRpb24gb24gTlNGIE1vbml0b3JpbmcgRHJhZnQ8bzpwPjwvbzpwPjwv
c3Bhbj48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJz
cDs8L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXpl
OjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6
IzFGNDk3RCI+VGhpcyBpcyB0aGUgc3RhcnQgb2YgYSB0d28gd2Vla3MgY2FsbCBmb3IgaW5wdXQg
b24gdGhlIFdHIGFkb3B0aW9uIG9mIHRoZSBkb2N1bWVudDoNCjwvc3Bhbj48YSBocmVmPSJodHRw
czovL3Rvb2xzLmlldGYub3JnL2h0bWwvZHJhZnQtaG9uZy1pMm5zZi1uc2YtbW9uaXRvcmluZy1k
YXRhLW1vZGVsLTA2Ij5odHRwczovL3Rvb2xzLmlldGYub3JnL2h0bWwvZHJhZnQtaG9uZy1pMm5z
Zi1uc2YtbW9uaXRvcmluZy1kYXRhLW1vZGVsLTA2PC9hPjxzcGFuIHN0eWxlPSJmb250LXNpemU6
MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjoj
MUY0OTdEIj48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3Bh
biBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7
LHNhbnMtc2VyaWY7Y29sb3I6IzFGNDk3RCI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1m
YW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOiMxRjQ5N0QiPlRoYW5r
cyBmb3IgdGhlIGF1dGhvcnMgb2YgdGhlIHR3byBJMk5TRiBNb25pdG9yaW5nIGRyYWZ0cyB0YWtp
bmcgYWN0aW9ucyBvZiBtZXJnaW5nIHRoZSBjb250ZW50Lg0KPG86cD48L286cD48L3NwYW4+PC9w
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9u
dC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOiMxRjQ5N0QiPldl
IG5lZWQgbW9yZSBvZiB0aG9zZSBhY3Rpb25zLiBBcyBvZiBub3cgd2UgaGF2ZSA4IFdHIGRyYWZ0
cy4gV2UgbmVlZCB0byBmaW5pc2ggdGhlbSBuZXh0IGZldyBtb250aHMuDQo8bzpwPjwvbzpwPjwv
c3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEx
LjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6IzFG
NDk3RCI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+
PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZx
dW90OyxzYW5zLXNlcmlmO2NvbG9yOiMxRjQ5N0QiPkJlYXIgaW4gbWluZCB0aGF0IFdHIGFkb3B0
aW9uIGRvZXNu4oCZdCBtZWFuIHRoZSBkcmFmdCBpcyByZWFkeSwgb25seSBtZWFucyB0aGF0IFdH
IHdpbGwgd29yayB0b2dldGhlciBvbiB0aGUgZHJhZnQgKGluc3RlYWQgb2YgaW5kaXZpZHVhbHMp
Lg0KPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5
bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5z
LXNlcmlmO2NvbG9yOiMxRjQ5N0QiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5
OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjojMUY0OTdEIj5QbGVhc2UgcHJv
dmlkZSBmZWVkYmFjayB0byB0aGUgbGlzdC9jaGFpcnMgaWYgeW91IGJlbGlldmUgdGhhdCB0aGlz
IGRvY3VtZW50IHNob3VsZCBiZSBhZG9wdGVkIGFzIGEgV0cgZG9jdW1lbnQuPG86cD48L286cD48
L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZTox
MS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOiMx
RjQ5N0QiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
PjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkm
cXVvdDssc2Fucy1zZXJpZjtjb2xvcjojMUY0OTdEIj5UaGFua3MsDQo8bzpwPjwvbzpwPjwvc3Bh
bj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBw
dDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6IzFGNDk3
RCI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNw
YW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90
OyxzYW5zLXNlcmlmO2NvbG9yOiMxRjQ5N0QiPkxpbmRhICZhbXA7IFlvYXY8bzpwPjwvbzpwPjwv
c3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEx
LjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6IzFG
NDk3RCI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+
PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZx
dW90OyxzYW5zLXNlcmlmO2NvbG9yOiMxRjQ5N0QiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwv
cD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0
O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZiI+RnJvbTo8L3NwYW4+
PC9iPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGli
cmkmcXVvdDssc2Fucy1zZXJpZiI+IE1yLiBKYWVob29uIFBhdWwgSmVvbmcgWzxhIGhyZWY9Im1h
aWx0bzpqYWVob29uLnBhdWxAZ21haWwuY29tIj5tYWlsdG86amFlaG9vbi5wYXVsQGdtYWlsLmNv
bTwvYT5dDQo8YnI+DQo8Yj5TZW50OjwvYj4gVGh1cnNkYXksIE5vdmVtYmVyIDE1LCAyMDE4IDY6
MzUgUE08YnI+DQo8Yj5Ubzo8L2I+IExpbmRhIER1bmJhciAmbHQ7PGEgaHJlZj0ibWFpbHRvOmxp
bmRhLmR1bmJhckBodWF3ZWkuY29tIj5saW5kYS5kdW5iYXJAaHVhd2VpLmNvbTwvYT4mZ3Q7OyBZ
b2F2IE5pciAmbHQ7PGEgaHJlZj0ibWFpbHRvOnluaXIuaWV0ZkBnbWFpbC5jb20iPnluaXIuaWV0
ZkBnbWFpbC5jb208L2E+Jmd0Ozxicj4NCjxiPkNjOjwvYj4gPGEgaHJlZj0ibWFpbHRvOmkybnNm
QGlldGYub3JnIj5pMm5zZkBpZXRmLm9yZzwvYT47IDxhIGhyZWY9Im1haWx0bzpza2t1X3NlY3Ut
YnJhaW5fYWxsQGdvb2dsZWdyb3Vwcy5jb20iPg0Kc2trdV9zZWN1LWJyYWluX2FsbEBnb29nbGVn
cm91cHMuY29tPC9hPjsgU2FuZ3dvbiBIeXVuICZsdDs8YSBocmVmPSJtYWlsdG86c3doeXVuNzdA
Z21haWwuY29tIj5zd2h5dW43N0BnbWFpbC5jb208L2E+Jmd0OzsgTXIuIEphZWhvb24gUGF1bCBK
ZW9uZyAmbHQ7PGEgaHJlZj0ibWFpbHRvOmphZWhvb24ucGF1bEBnbWFpbC5jb20iPmphZWhvb24u
cGF1bEBnbWFpbC5jb208L2E+Jmd0Ozxicj4NCjxiPlN1YmplY3Q6PC9iPiBSZXF1ZXN0IGZvciBX
RyBBZG9wdGlvbiBDYWxsIG9uIE5TRiBNb25pdG9yaW5nIERyYWZ0PG86cD48L286cD48L3NwYW4+
PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8ZGl2Pg0K
PGRpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5IaSBMaW5kYSBhbmQgWW9hdiw8bzpw
PjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPkFzIHdlIGRp
c2N1c3NlZCB0aGUgbGFzdCBCYW5na29rIG1lZXRpbmcsPG86cD48L286cD48L3A+DQo8L2Rpdj4N
CjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5JIGhhdmUgbWVyZ2VkIHRoZSB0d28gZHJhZnRz
IG9mIEluZm9ybWF0aW9uIE1vZGVsIGFuZCBEYXRhIE1vZGVsPG86cD48L286cD48L3A+DQo8L2Rp
dj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5mb3IgTlNGIE1vbml0b3JpbmcgaW50byBh
IG5ldyBkcmFmdCBjYWxsZWQgZHJhZnQtaG9uZy1pMm5zZi1uc2YtbW9uaXRvcmluZy1kYXRhLW1v
ZGVsLTA2OjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1h
bCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9y
bWFsIj4tIFR3byBJbmZvcm1hdGlvbiBhbmQgRGF0YSBNb2RlbCBEcmFmdHM8bzpwPjwvbzpwPjwv
cD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPiZuYnNwOy4gZHJhZnQtemhh
bmctaTJuc2YtaW5mby1tb2RlbC1tb25pdG9yaW5nLTA3Jm5ic3A7PG86cD48L286cD48L3A+DQo8
L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj4mbmJzcDsuIGRyYWZ0LWhvbmctaTJu
c2YtbnNmLW1vbml0b3JpbmctZGF0YS1tb2RlbC0wNTxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8
ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4N
CjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj4tIEEgTWVyZ2VkIERhdGEgTW9kZWwgRHJhZnQm
bmJzcDs8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
PiZuYnNwOy4gZHJhZnQtaG9uZy1pMm5zZi1uc2YtbW9uaXRvcmluZy1kYXRhLW1vZGVsLTA2PG86
cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj4mbmJzcDsu
IDxhIGhyZWY9Imh0dHBzOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9kcmFmdC1ob25nLWkybnNmLW5z
Zi1tb25pdG9yaW5nLWRhdGEtbW9kZWwtMDYiPg0KaHR0cHM6Ly90b29scy5pZXRmLm9yZy9odG1s
L2RyYWZ0LWhvbmctaTJuc2YtbnNmLW1vbml0b3JpbmctZGF0YS1tb2RlbC0wNjwvYT48bzpwPjwv
bzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7
PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+VGhlIE5TRiBt
b25pdG9yaW5nIGlzIHZlcnkgaW1wb3J0YW50IHRvIG1hbmFnZSB0aGUgSTJOU0Ygc2VjdXJpdHkg
c2VydmljZSBzeXN0ZW08bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiPmluIGEgcmVsaWFibGUgYW5kIHNjYWxhYmxlIGZhc2hpb24uPG86cD48L286cD48
L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpw
PjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPkNvdWxkIHlvdSBzdGFy
dCBhIFdHIGFkb3B0aW9uIGNhbGwgZm9yIHRoaXMgZHJhZnQ/PG86cD48L286cD48L3A+DQo8L2Rp
dj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwv
ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPlRoYW5rcy48bzpwPjwvbzpwPjwvcD4N
CjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9w
Pg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+QmVzdCBSZWdhcmRzLDxvOnA+
PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+UGF1bDxvOnA+
PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+LS0mbmJzcDs8
bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxkaXY+DQo8ZGl2Pg0KPGRpdj4NCjxkaXY+
DQo8ZGl2Pg0KPGRpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj49PT09PT09PT09PT09
PT09PT09PT09PT09PT08YnI+DQpNci4gSmFlaG9vbiAoUGF1bCkgSmVvbmcsIFBoLkQuPGJyPg0K
QXNzb2NpYXRlIFByb2Zlc3Nvcjxicj4NCkRlcGFydG1lbnQgb2YgU29mdHdhcmU8YnI+DQpTdW5n
a3l1bmt3YW4gVW5pdmVyc2l0eTxicj4NCk9mZmljZTogJiM0Mzs4Mi0zMS0yOTktNDk1Nzxicj4N
CkVtYWlsOiA8YSBocmVmPSJtYWlsdG86amFlaG9vbi5wYXVsQGdtYWlsLmNvbSIgdGFyZ2V0PSJf
YmxhbmsiPmphZWhvb24ucGF1bEBnbWFpbC5jb208L2E+LCZuYnNwOzxhIGhyZWY9Im1haWx0bzpw
YXVsamVvbmdAc2trdS5lZHUiIHRhcmdldD0iX2JsYW5rIj48c3BhbiBzdHlsZT0iZm9udC1zaXpl
OjkuNXB0Ij5wYXVsamVvbmdAc2trdS5lZHU8L3NwYW4+PC9hPjxicj4NClBlcnNvbmFsIEhvbWVw
YWdlOiA8YSBocmVmPSJodHRwOi8vY3BzbGFiLnNra3UuZWR1L3Blb3BsZS1qYWVob29uLWplb25n
LnBocCIgdGFyZ2V0PSJfYmxhbmsiPg0KaHR0cDovL2lvdGxhYi5za2t1LmVkdS9wZW9wbGUtamFl
aG9vbi1qZW9uZy5waHA8L2E+PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+
DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4N
CjwvZGl2Pg0KPC9ib2R5Pg0KPC9odG1sPg0K

--_000_4A95BA014132FF49AE685FAB4B9F17F66B21A81Bsjceml521mbschi_--


From nobody Wed Dec 19 15:22:30 2018
Return-Path: <ietf-secretariat-reply@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 53F78130DC9; Wed, 19 Dec 2018 15:22:28 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: IETF Secretariat <ietf-secretariat-reply@ietf.org>
To: <i2nsf@ietf.org>, <i2nsf-chairs@ietf.org>, <draft-hong-i2nsf-nsf-monitoring-data-model@ietf.org>, 
X-Test-IDTracker: no
X-IETF-IDTracker: 6.89.2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <154526174833.2191.696998778777837380.idtracker@ietfa.amsl.com>
Date: Wed, 19 Dec 2018 15:22:28 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2nsf/Nwi_kCCrbfZU3clsroQkUofcMD4>
Subject: [I2nsf] The I2NSF WG has placed draft-hong-i2nsf-nsf-monitoring-data-model in state "Adopted by a WG"
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, 19 Dec 2018 23:22:28 -0000

The I2NSF WG has placed draft-hong-i2nsf-nsf-monitoring-data-model in state
Adopted by a WG (entered by Linda Dunbar)

The document is available at
https://datatracker.ietf.org/doc/draft-hong-i2nsf-nsf-monitoring-data-model/

Comment:
we got sufficient support for adopting this draft to I2NSF WG draft


From nobody Wed Dec 19 18:38:16 2018
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 D5E41130DE8 for <i2nsf@ietfa.amsl.com>; Wed, 19 Dec 2018 18:38:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.499
X-Spam-Level: 
X-Spam-Status: No, score=-0.499 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HK_NAME_FM_MR_MRS=1.499, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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 cy2QKKUlCd8b for <i2nsf@ietfa.amsl.com>; Wed, 19 Dec 2018 18:38:13 -0800 (PST)
Received: from mail-io1-xd2b.google.com (mail-io1-xd2b.google.com [IPv6:2607:f8b0:4864:20::d2b]) (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 C5B59130DD5 for <i2nsf@ietf.org>; Wed, 19 Dec 2018 18:38:12 -0800 (PST)
Received: by mail-io1-xd2b.google.com with SMTP id l14so168507ioj.5 for <i2nsf@ietf.org>; Wed, 19 Dec 2018 18:38:12 -0800 (PST)
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=KHkrsVhUBXq1m45sPw88driLA4XwVfgo+9342h/jg5k=; b=AhSM6E5jfY5rZgZ/7NHI476FyC9SGIZFDLOf23l4flG0qciCPCZlKrPZHtFHt6fHh8 Oo6vZ41qa7Ou2daWFjYxS2RcENM0GazdIep3CuBc4HE+71COP2CKPS3ICoJ+1o5b2UqN vNfoAaCRFt8cTPuT1hqA/6uWlKFz5J7VMxbwG9DVwq03cAftsrkq8GYkXfQPda8WpCGo AsjcZFUOvBMbi0uvYTrOfM3NsIQj7xfRbSG8S9mI8igZuL48sPJZEvAIwdAjrAgAHceS arHz49ptS5mjH+n4BjCLHUAO5WINOAwoouHmx3hYSamdoQlsS02iHNAFsM+vvcEL863T hCMA==
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=KHkrsVhUBXq1m45sPw88driLA4XwVfgo+9342h/jg5k=; b=PZtmJ6m4j+PBDG84G0zH9ZHju26nf02ZRzMWw58ZRbEJZdoAsFTmEPQmvK7mrguw0t yAoXWpdP6ctvfpLYWFwwk7ScwKC1nK01z9/s2T0G5lRFR2BxY+ObdehHn4xgoTOuTsda B2ripGq+kZU4a5KG1YCHmkTghfpv4miXRNIoIlU68LaBHIiFu9+UpKEZP6EKnj8SWFha nOSUxgvholq8qjni8akUgJ9zY5p9kuSL9jsQ9NxX7mP2xbHYj/Bxk27/X2TJPMA/rR3b HMwUjS9U9voyRv3NavfKzhf8SuLguoLjZ6Ab80Mb18gCHyW/joZmxJniGQkEfJFcUsRb PS+Q==
X-Gm-Message-State: AA+aEWY6zsiCs4yeF+gDFWBAr4Mn5HhMgKZ9JnmeNehkwKIbZgpNJaAa Tlp2m0nTMrAowhOwYqKr2B5MG/93zROrxvYOyg0=
X-Google-Smtp-Source: AFSGD/XIxDEslTkX4iU9PqlSglkAMXAUhTF7vJDZB0eukrPWwknSIWrAInmq0t/obAxSvYZIsUDtIJysgKhtcl6q9FA=
X-Received: by 2002:a6b:2c92:: with SMTP id s140mr19762094ios.218.1545273491836;  Wed, 19 Dec 2018 18:38:11 -0800 (PST)
MIME-Version: 1.0
References: <4A95BA014132FF49AE685FAB4B9F17F66B21A81B@sjceml521-mbs.china.huawei.com>
In-Reply-To: <4A95BA014132FF49AE685FAB4B9F17F66B21A81B@sjceml521-mbs.china.huawei.com>
From: "Mr. Jaehoon Paul Jeong" <jaehoon.paul@gmail.com>
Date: Thu, 20 Dec 2018 11:39:55 +0900
Message-ID: <CAPK2Dex-jBYyqZX-t7F198bTZx5rMsafagTtNwa-TAvA7UUCnA@mail.gmail.com>
To: Linda Dunbar <linda.dunbar@huawei.com>, Yoav Nir <ynir.ietf@gmail.com>
Cc: "i2nsf@ietf.org" <i2nsf@ietf.org>, skku_secu-brain_all@googlegroups.com,  Sangwon Hyun <swhyun77@gmail.com>, "Mr. Jaehoon Paul Jeong" <jaehoon.paul@gmail.com>
Content-Type: multipart/alternative; boundary="0000000000008fd4b5057d6b0509"
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2nsf/AAiTF-fGD0mfBXjAdxf5XdWhuOQ>
Subject: Re: [I2nsf] Call for WG Adoption on NSF Monitoring Draft has been closed
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, 20 Dec 2018 02:38:15 -0000

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

Dear Linda and Yoav,
Sure, we authors will address all of the comments raised during the WG
adoption call,
and then will submit the NSF Monitoring WG document to the IETF.

Thanks.

Best Regards,
Paul

On Thu, Dec 20, 2018 at 8:16 AM Linda Dunbar <linda.dunbar@huawei.com>
wrote:

> We have got sufficient support for adopting the
> https://tools.ietf.org/html/draft-hong-i2nsf-nsf-monitoring-data-model-06
> as I2NSF WG draft.
>
>
>
> Authors: please address all the comments coming from the WG Adoption Call
> process and upload the revised draft in the name of
> =E2=80=9Cdraft-ietf-i2nsf-nsf-monitoring-data-model=E2=80=9D.
>
>
>
> Thanks to everyone reviewing the draft and providing the comments.
>
>
>
> Linda & Yoav
>
>
>
> *From:* Linda Dunbar
> *Sent:* Wednesday, December 05, 2018 4:32 PM
> *To:* 'i2nsf@ietf.org' <i2nsf@ietf.org>
> *Subject:* Call for WG Adoption on NSF Monitoring Draft
>
>
>
> This is the start of a two weeks call for input on the WG adoption of the
> document:
> https://tools.ietf.org/html/draft-hong-i2nsf-nsf-monitoring-data-model-06
>
>
>
> Thanks for the authors of the two I2NSF Monitoring drafts taking actions
> of merging the content.
>
> We need more of those actions. As of now we have 8 WG drafts. We need to
> finish them next few months.
>
>
>
> Bear in mind that WG adoption doesn=E2=80=99t mean the draft is ready, on=
ly means
> that WG will work together on the draft (instead of individuals).
>
>
>
> Please provide feedback to the list/chairs if you believe that this
> document should be adopted as a WG document.
>
>
>
> Thanks,
>
>
>
> Linda & Yoav
>
>
>
>
>
> *From:* Mr. Jaehoon Paul Jeong [mailto:jaehoon.paul@gmail.com
> <jaehoon.paul@gmail.com>]
> *Sent:* Thursday, November 15, 2018 6:35 PM
> *To:* Linda Dunbar <linda.dunbar@huawei.com>; Yoav Nir <
> ynir.ietf@gmail.com>
> *Cc:* i2nsf@ietf.org; skku_secu-brain_all@googlegroups.com; Sangwon Hyun =
<
> swhyun77@gmail.com>; Mr. Jaehoon Paul Jeong <jaehoon.paul@gmail.com>
> *Subject:* Request for WG Adoption Call on NSF Monitoring Draft
>
>
>
> Hi Linda and Yoav,
>
> As we discussed the last Bangkok meeting,
>
> I have merged the two drafts of Information Model and Data Model
>
> for NSF Monitoring into a new draft called
> draft-hong-i2nsf-nsf-monitoring-data-model-06:
>
>
>
> - Two Information and Data Model Drafts
>
>  . draft-zhang-i2nsf-info-model-monitoring-07
>
>  . draft-hong-i2nsf-nsf-monitoring-data-model-05
>
>
>
> - A Merged Data Model Draft
>
>  . draft-hong-i2nsf-nsf-monitoring-data-model-06
>
>  .
> https://tools.ietf.org/html/draft-hong-i2nsf-nsf-monitoring-data-model-06
>
>
>
> The NSF monitoring is very important to manage the I2NSF security service
> system
>
> in a reliable and scalable fashion.
>
>
>
> Could you start a WG adoption call for this draft?
>
>
>
> Thanks.
>
>
>
> Best Regards,
>
> Paul
>
> --
>
> =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 Software
> 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>
> _______________________________________________
> 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 Software
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>

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

<div dir=3D"ltr">Dear Linda and Yoav,<div>Sure, we authors will address all=
 of the comments raised during the WG adoption call,=C2=A0</div><div>and th=
en will submit the NSF Monitoring WG document to the IETF.</div><div><br></=
div><div>Thanks.</div><div><br></div><div>Best Regards,</div><div>Paul</div=
></div><br><div class=3D"gmail_quote"><div dir=3D"ltr">On Thu, Dec 20, 2018=
 at 8:16 AM Linda Dunbar &lt;<a href=3D"mailto:linda.dunbar@huawei.com" tar=
get=3D"_blank">linda.dunbar@huawei.com</a>&gt; wrote:<br></div><blockquote =
class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px sol=
id rgb(204,204,204);padding-left:1ex">





<div lang=3D"EN-US">
<div class=3D"gmail-m_-3414274780453005874gmail-m_-4585376461347101157WordS=
ection1">
<p class=3D"MsoNormal"><span style=3D"font-size:11pt;font-family:Calibri,sa=
ns-serif;color:rgb(31,73,125)">We have got sufficient support for adopting =
the
</span><a href=3D"https://tools.ietf.org/html/draft-hong-i2nsf-nsf-monitori=
ng-data-model-06" target=3D"_blank">https://tools.ietf.org/html/draft-hong-=
i2nsf-nsf-monitoring-data-model-06</a><span style=3D"font-size:11pt;font-fa=
mily:Calibri,sans-serif;color:rgb(31,73,125)"> as I2NSF WG
 draft. <u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11pt;font-family:Calibri,sa=
ns-serif;color:rgb(31,73,125)"><u></u>=C2=A0<u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11pt;font-family:Calibri,sa=
ns-serif;color:rgb(31,73,125)">Authors: please address all the comments com=
ing from the WG Adoption Call process and upload the revised draft in the n=
ame of =E2=80=9Cdraft-ietf-i2nsf-nsf-monitoring-data-model=E2=80=9D.
<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11pt;font-family:Calibri,sa=
ns-serif;color:rgb(31,73,125)"><u></u>=C2=A0<u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11pt;font-family:Calibri,sa=
ns-serif;color:rgb(31,73,125)">Thanks to everyone reviewing the draft and p=
roviding the comments.
<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11pt;font-family:Calibri,sa=
ns-serif;color:rgb(31,73,125)"><u></u>=C2=A0<u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11pt;font-family:Calibri,sa=
ns-serif;color:rgb(31,73,125)">Linda &amp; Yoav<u></u><u></u></span></p>
<p class=3D"MsoNormal"><a name=3D"m_-3414274780453005874_m_-458537646134710=
1157__MailEndCompose"><span style=3D"font-size:11pt;font-family:Calibri,san=
s-serif;color:rgb(31,73,125)"><u></u>=C2=A0<u></u></span></a></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><span style=3D"font-size:11pt;font-family:Calibri=
,sans-serif">From:</span></b><span style=3D"font-size:11pt;font-family:Cali=
bri,sans-serif"> Linda Dunbar
<br>
<b>Sent:</b> Wednesday, December 05, 2018 4:32 PM<br>
<b>To:</b> &#39;<a href=3D"mailto:i2nsf@ietf.org" target=3D"_blank">i2nsf@i=
etf.org</a>&#39; &lt;<a href=3D"mailto:i2nsf@ietf.org" target=3D"_blank">i2=
nsf@ietf.org</a>&gt;<br>
<b>Subject:</b> Call for WG Adoption on NSF Monitoring Draft<u></u><u></u><=
/span></p>
</div>
</div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11pt;font-family:Calibri,sa=
ns-serif;color:rgb(31,73,125)">This is the start of a two weeks call for in=
put on the WG adoption of the document:
</span><a href=3D"https://tools.ietf.org/html/draft-hong-i2nsf-nsf-monitori=
ng-data-model-06" target=3D"_blank">https://tools.ietf.org/html/draft-hong-=
i2nsf-nsf-monitoring-data-model-06</a><span style=3D"font-size:11pt;font-fa=
mily:Calibri,sans-serif;color:rgb(31,73,125)"><u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11pt;font-family:Calibri,sa=
ns-serif;color:rgb(31,73,125)"><u></u>=C2=A0<u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11pt;font-family:Calibri,sa=
ns-serif;color:rgb(31,73,125)">Thanks for the authors of the two I2NSF Moni=
toring drafts taking actions of merging the content.
<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11pt;font-family:Calibri,sa=
ns-serif;color:rgb(31,73,125)">We need more of those actions. As of now we =
have 8 WG drafts. We need to finish them next few months.
<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11pt;font-family:Calibri,sa=
ns-serif;color:rgb(31,73,125)"><u></u>=C2=A0<u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11pt;font-family:Calibri,sa=
ns-serif;color:rgb(31,73,125)">Bear in mind that WG adoption doesn=E2=80=99=
t mean the draft is ready, only means that WG will work together on the dra=
ft (instead of individuals).
<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11pt;font-family:Calibri,sa=
ns-serif;color:rgb(31,73,125)"><u></u>=C2=A0<u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11pt;font-family:Calibri,sa=
ns-serif;color:rgb(31,73,125)">Please provide feedback to the list/chairs i=
f you believe that this document should be adopted as a WG document.<u></u>=
<u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11pt;font-family:Calibri,sa=
ns-serif;color:rgb(31,73,125)"><u></u>=C2=A0<u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11pt;font-family:Calibri,sa=
ns-serif;color:rgb(31,73,125)">Thanks,
<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11pt;font-family:Calibri,sa=
ns-serif;color:rgb(31,73,125)"><u></u>=C2=A0<u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11pt;font-family:Calibri,sa=
ns-serif;color:rgb(31,73,125)">Linda &amp; Yoav<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11pt;font-family:Calibri,sa=
ns-serif;color:rgb(31,73,125)"><u></u>=C2=A0<u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11pt;font-family:Calibri,sa=
ns-serif;color:rgb(31,73,125)"><u></u>=C2=A0<u></u></span></p>
<p class=3D"MsoNormal"><b><span style=3D"font-size:11pt;font-family:Calibri=
,sans-serif">From:</span></b><span style=3D"font-size:11pt;font-family:Cali=
bri,sans-serif"> Mr. Jaehoon Paul Jeong [<a href=3D"mailto:jaehoon.paul@gma=
il.com" target=3D"_blank">mailto:jaehoon.paul@gmail.com</a>]
<br>
<b>Sent:</b> Thursday, November 15, 2018 6:35 PM<br>
<b>To:</b> Linda Dunbar &lt;<a href=3D"mailto:linda.dunbar@huawei.com" targ=
et=3D"_blank">linda.dunbar@huawei.com</a>&gt;; Yoav Nir &lt;<a href=3D"mail=
to:ynir.ietf@gmail.com" target=3D"_blank">ynir.ietf@gmail.com</a>&gt;<br>
<b>Cc:</b> <a href=3D"mailto:i2nsf@ietf.org" target=3D"_blank">i2nsf@ietf.o=
rg</a>; <a href=3D"mailto:skku_secu-brain_all@googlegroups.com" target=3D"_=
blank">
skku_secu-brain_all@googlegroups.com</a>; Sangwon Hyun &lt;<a href=3D"mailt=
o:swhyun77@gmail.com" target=3D"_blank">swhyun77@gmail.com</a>&gt;; Mr. Jae=
hoon Paul Jeong &lt;<a href=3D"mailto:jaehoon.paul@gmail.com" target=3D"_bl=
ank">jaehoon.paul@gmail.com</a>&gt;<br>
<b>Subject:</b> Request for WG Adoption Call on NSF Monitoring Draft<u></u>=
<u></u></span></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<div>
<div>
<div>
<p class=3D"MsoNormal">Hi Linda and Yoav,<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">As we discussed the last Bangkok meeting,<u></u><u><=
/u></p>
</div>
<div>
<p class=3D"MsoNormal">I have merged the two drafts of Information Model an=
d Data Model<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">for NSF Monitoring into a new draft called draft-hon=
g-i2nsf-nsf-monitoring-data-model-06:<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">- Two Information and Data Model Drafts<u></u><u></u=
></p>
</div>
<div>
<p class=3D"MsoNormal">=C2=A0. draft-zhang-i2nsf-info-model-monitoring-07=
=C2=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=C2=A0. draft-hong-i2nsf-nsf-monitoring-data-model-0=
5<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">- A Merged Data Model Draft=C2=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=C2=A0. draft-hong-i2nsf-nsf-monitoring-data-model-0=
6<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=C2=A0. <a href=3D"https://tools.ietf.org/html/draft=
-hong-i2nsf-nsf-monitoring-data-model-06" target=3D"_blank">
https://tools.ietf.org/html/draft-hong-i2nsf-nsf-monitoring-data-model-06</=
a><u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">The NSF monitoring is very important to manage the I=
2NSF security service system<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">in a reliable and scalable fashion.<u></u><u></u></p=
>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Could you start a WG adoption call for this draft?<u=
></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Thanks.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Best Regards,<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Paul<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">--=C2=A0<u></u><u></u></p>
</div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<p class=3D"MsoNormal">=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 Software<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" target=3D"_b=
lank"><span style=3D"font-size:9.5pt">pauljeong@skku.edu</span></a><br>
Personal Homepage: <a href=3D"http://cpslab.skku.edu/people-jaehoon-jeong.p=
hp" target=3D"_blank">
http://iotlab.skku.edu/people-jaehoon-jeong.php</a><u></u><u></u></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</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"=
 class=3D"gmail-m_-3414274780453005874gmail_signature"><div dir=3D"ltr"><di=
v><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 Softw=
are<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"=
 target=3D"_blank">pauljeong@skku.edu</a><br>Personal Homepage: <a href=3D"=
http://cpslab.skku.edu/people-jaehoon-jeong.php" target=3D"_blank">http://i=
otlab.skku.edu/people-jaehoon-jeong.php</a><br></div></div></div></div></di=
v></div></div></div>

--0000000000008fd4b5057d6b0509--


From nobody Sat Dec 22 06:42:58 2018
Return-Path: <ekr@rtfm.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 171E9126DBF for <i2nsf@ietfa.amsl.com>; Sat, 22 Dec 2018 06:42:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=rtfm-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 LJ8wxqCEb-Jn for <i2nsf@ietfa.amsl.com>; Sat, 22 Dec 2018 06:42:54 -0800 (PST)
Received: from mail-lf1-x12a.google.com (mail-lf1-x12a.google.com [IPv6:2a00:1450:4864:20::12a]) (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 BD100123FFD for <i2nsf@ietf.org>; Sat, 22 Dec 2018 06:42:53 -0800 (PST)
Received: by mail-lf1-x12a.google.com with SMTP id n18so5840930lfh.6 for <i2nsf@ietf.org>; Sat, 22 Dec 2018 06:42:53 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rtfm-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=oOoWl+Z7ngV7tjD78zz52HeVgraWhd8FedigYRWU/1M=; b=sO9dKMq6pQ3aDmrC6jBCcd9+HtxAKgfDGhMtCSzEyd3m1agIHTYkaNXI8js8ZMLpmW miWlrYyM4jtGM9BE5223ID5sT8jRaO/5tJhZS+VaGVanfgijWy0698EdqmE7ylcBPb03 cA8MB7NBq3vky3cWVN3YAtGBwLMlonEfH77YJMAhT7nN9hJZqJvCZUKe1me47Hy/TJxV Hg7owdW054LW71COFLSZ5aEDbjFReexygcf7sBCGoZGIjx7/GfPV1pVSy9vJIxuIie3H dPfiFb+dScAxhbGOrMDE85gKbY4anmxXxdMRqRUw1ZvI8G3Gqq3yUOmA+glJqf8cHDkT Yj3Q==
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; bh=oOoWl+Z7ngV7tjD78zz52HeVgraWhd8FedigYRWU/1M=; b=skWMeTu5wcnlfpkPGIMrTWfBSWhVCgQJRAXWpdwExKjrAlyu69uKeouru8dFBbH4JP p6ABt0kDHgl0unx+3ZBfmspEwLeTqxqa7qhteQhvcem9C1Q2AAlvOcLAHVnnJIF2KFZq zKEI3vgdWURURz9anMumYMiZ8BFu6LIPTPkk2v3DQrv4iolhkw5p/39iIIdZooWqOyDn iDSHGJ3ga8UptfaJJOtBqY3R6Jg3IBdD1gCuYT+9ex6UT1oDFf7ChoQ7TPEDWE70QQ9h 3U6krqlY6rEHDZsHva8hPS4JT107paFTFirPIVAclDZAGVzpl4Mj7XsTMHdGopyvYjzD cwMQ==
X-Gm-Message-State: AA+aEWbp3SQBgWXXkMgZ6U9UercPCNubw+xJAw8RRLtPsZXMBgYfpNrS QT5Fsaql45Q2ckeP5erdv7/k0R+5xOOxxbGeNJBgI0BB
X-Google-Smtp-Source: AFSGD/WH4sdtdzsxVBW6bCUfbu/3cnQsbxEW521LD6G1Ns3Ac61mbZoU1gtHh415FxuDif9j3ecyI45d+0ckI40nJaQ=
X-Received: by 2002:a19:910d:: with SMTP id t13mr3329406lfd.98.1545489771366;  Sat, 22 Dec 2018 06:42:51 -0800 (PST)
MIME-Version: 1.0
References: <CABcZeBOjhEpw4gNDRgJD=FCWy1Wrirz_EsJefJjDHpp5mVe1fw@mail.gmail.com>
In-Reply-To: <CABcZeBOjhEpw4gNDRgJD=FCWy1Wrirz_EsJefJjDHpp5mVe1fw@mail.gmail.com>
From: Eric Rescorla <ekr@rtfm.com>
Date: Sat, 22 Dec 2018 06:42:14 -0800
Message-ID: <CABcZeBNJn_wZV6Q5fo6U2-WWOiV1B_LrXSm8wYZshEJY6qgS5A@mail.gmail.com>
To: i2nsf@ietf.org
Content-Type: multipart/alternative; boundary="000000000000d3a264057d9d601e"
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2nsf/bVTGfSXR70UcFkwfkV4FsNHg8uo>
Subject: [I2nsf] Fwd: AD Review of draft-ietf-i2nsf-applicability-07
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, 22 Dec 2018 14:42:57 -0000

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

CCing the WG because I was wrong about the aliases.

---------- Forwarded message ---------
From: Eric Rescorla <ekr@rtfm.com>
Date: Fri, Dec 21, 2018 at 6:32 AM
Subject: AD Review of draft-ietf-i2nsf-applicability-07
To: <draft-ietf-i2nsf-applicability@ietf.org>


Rich version of this review at:
https://mozphab-ietf.devsvcdev.mozaws.net/D3181


I found a number of typographical and grammar errors. Please give this
document a thorough read.

IMPORTANT
S 1.
>
>      Interface to Network Security Functions (I2NSF) defines a framework
>      and interfaces for interacting with Network Security Functions
>      (NSFs).  The I2NSF framework allows heterogeneous NSFs developed by
>      different security solution vendors to be used in the Network
>      Functions Virtualization (NFV) environment [ETSI-NFV] by utilizing

Much of this document cannot be understood without reading ETSI-NFV,
so it has to be a normative reference. It also would be helpful to
provide a link.


S 2.
>      This document uses the terminology described in [RFC7149],
>      [ITU-T.Y.3300], [ONF-OpenFlow], [ONF-SDN-Architecture],
>      [ITU-T.X.1252], [ITU-T.X.800], [RFC8329], [i2nsf-terminology],
>      [consumer-facing-inf-im], [consumer-facing-inf-dm],
>      [i2nsf-nsf-cap-im], [nsf-facing-inf-dm], [registration-inf-dm], and
>      [nsf-triggered-steering].  In addition, the following terms are

Every term in this document needs to be understandable without
reference to closed specifications or internally defined. Please
ensure that this is so,


S 3.
>      used for the I2NSF NSF-Facing Interface.
>
>      The Registration Interface between the Security Controller and the
>      Developer's Management System can be implemented by RESTCONF
>      [RFC8040].  The data model defined in [registration-inf-dm] can be
>      used for the I2NSF Registration Interface.

What role does the Developer's Management System play in this? I think
this refers to the text above starting with "The developers (or
vendors)...". Is that correct?

Assuming I am correct, this seems like a potentially serious security
vulnerability in this design in that it potentially allows an inside
attacker at the developer to seriously weaken a system's security.
What protections exist to prevent this?


S 4.
>      administrator wants to control the staff members' access to a
>      particular Interner service (e.g., Example.com) during business
>      hours.  The following is an example high-level security policy rule
>      that the administrator requests: Block the staff members' access to
>      Example.com from 9 AM to 6 PM.  The administrator sends this high-
>      level security policy to the Security Controller, then the Security

The text above suggests that high-level policies are via
RESTCONF/YANG, but this is clearly freeform text.
COMMENTS
S 1.
>
>   1.  Introduction
>
>      Interface to Network Security Functions (I2NSF) defines a framework
>      and interfaces for interacting with Network Security Functions
>      (NSFs).  The I2NSF framework allows heterogeneous NSFs developed by

Please define "Network Security Functions" here.




S 1.
>      functions in the NFV platform.  In the I2NSF framework, each NSF
>      initially registers the profile of its own capabilities into the
>      system in order for themselves to be available in the system.  In
>      addition, the Security Controller is validated by the I2NSF Client
>      (also called I2NSF User) that the user is employing, so that the user
>      can request security services through the Security Controller.

In this case the user is the system administrator.


S 1.
>      [RFC7149] to provide different security functionality such as
>      firewalls [opsawg-firewalls], Deep Packet Inspection (DPI), and
>      Distributed Denial of Service (DDoS) attack mitigation; (iv) the use
>      of NFV as supporting technology.  The implementation of I2NSF in
>      these scenarios has allowed us to verify the applicability and
>      effectiveness of the I2NSF framework for a variety of use cases.

This would be easier to read with a standard bulleted list.


S 2.
>         network resources, which facilitates the design, delivery and
>         operation of network services in a dynamic and scalable manner
>         [ITU-T.Y.3300].
>
>      o  Firewall: A service function at the junction of two network
>         segments that inspects every packet that attempts to cross the

Nit: It might not inspect *every* packet.


S 4.
>
>   4.  Time-dependent Web Access Control Service
>
>      This service scenario assumes that an enterprise network
>      administrator wants to control the staff members' access to a
>      particular Interner service (e.g., Example.com) during business

Nit: "Internet"


S 4.
>      inspection capability is required to check whether the target URL of
>      a received packet is in the Example.com domain or not.
>
>      The Security Controller maintains the security capabilities of each
>      NSF running in the I2NSF system, which have been reported by the
>      Developer's Management System via the Registation interface.  Based

Nit: "Registration"


S 4.
>      currently using the network.  Based on the retrieved information, the
>      Security Controller generates low-level security rules to check
>      whether the source IP address of a received packet matches any one
>      being used by a staff member.  In addition, the low-level security
>      rules should be able to determine that a received packet is of HTTP
>      protocol.  The low-level security rules for web filter checks that

Nit: "rules"... "checks" disagree.


S 6.
>      translated into their packet forwarding rules, whereas NSFs enforce
>      NSF-related security rules requiring the security capabilities of the
>      NSFs.  For this purpose, the Security Controller instructs the SDN
>      Controller via NSF-Facing Interface so that SDN forwarding elements
>      can perform the required security services with flow tables under the
>      supervision of the SDN Controller.

I'm having some trouble understanding the difference here between NSFs
and SDN elements. They both seem to be software controlled network
elements. Is this just some continuum about CPU power?


S 6.
>      can perform the required security services with flow tables under the
>      supervision of the SDN Controller.
>
>      As an example, let us consider two different types of security rules:
>
>      Rule A is a simple packet fltering rule that checks only the IP

Nit: "filtering"


S 6.2.
>          packets that have the same call-id.
>
>      6.  The SDN Controller installs new rules (e.g., drop packets) into
>          underlying switches.
>
>      7.  The illegal packets are dropped by these switches.

"Illegal" is probably the wrong wrod here.


S 6.3.
>         is helpful to determine security policies for such a network.
>
>   6.3.  Attack Mitigation: Centralized DDoS-attack Mitigation System
>
>      A centralized DDoS-attack mitigation can manage each network resource
>      and manipulate rules to each switch through a common server for DDoS-

"manipulate rules to" is not grammatical.


S 6.3.
>
>      Servers are categorized into stateless servers (e.g., DNS servers)
>      and stateful servers (e.g., web servers).  For DDoS-attack
>      mitigation, traffic flows in switches are dynamically configured by
>      traffic flow forwarding path management according to the category of
>      servers [AVANT-GUARD].  Such a managenent should consider the load

1. This seems hard to understand without this reference, which is not
public.
2. "management"


S 6.3.
>      mitigation, traffic flows in switches are dynamically configured by
>      traffic flow forwarding path management according to the category of
>      servers [AVANT-GUARD].  Such a managenent should consider the load
>      balance among the switches for the defense against DDoS attacks.
>
>      The procedure of DDoS-attack mitigation operations in this system is

"procedure of... operations" is ungrammatical

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

<div dir=3D"ltr">CCing the WG because I was wrong about the aliases.<br><di=
v><div><br><div class=3D"gmail_quote"><div dir=3D"ltr">---------- Forwarded=
 message ---------<br>From: <b class=3D"gmail_sendername" dir=3D"auto">Eric=
 Rescorla</b> <span dir=3D"ltr">&lt;<a href=3D"mailto:ekr@rtfm.com">ekr@rtf=
m.com</a>&gt;</span><br>Date: Fri, Dec 21, 2018 at 6:32 AM<br>Subject: AD R=
eview of draft-ietf-i2nsf-applicability-07<br>To:  &lt;<a href=3D"mailto:dr=
aft-ietf-i2nsf-applicability@ietf.org">draft-ietf-i2nsf-applicability@ietf.=
org</a>&gt;<br></div><br><br><div dir=3D"ltr"><div dir=3D"ltr">Rich version=
 of this review at:<br><a href=3D"https://mozphab-ietf.devsvcdev.mozaws.net=
/D3181" target=3D"_blank">https://mozphab-ietf.devsvcdev.mozaws.net/D3181</=
a><br><br><br>I found a number of typographical and grammar errors. Please =
give this<br>document a thorough read.<br><br>IMPORTANT<br>S 1.<br>&gt;=C2=
=A0=C2=A0 <br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Interface to Network Secur=
ity Functions (I2NSF) defines a framework<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0 and interfaces for interacting with Network Security Functions<br>&g=
t;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 (NSFs).=C2=A0 The I2NSF framework allows h=
eterogeneous NSFs developed by<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 differ=
ent security solution vendors to be used in the Network<br>&gt;=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0 Functions Virtualization (NFV) environment [ETSI-NFV] by=
 utilizing<br><br>Much of this document cannot be understood without readin=
g ETSI-NFV,<br>so it has to be a normative reference. It also would be help=
ful to<br>provide a link.<br><br><br>S 2.<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0 This document uses the terminology described in [RFC7149],<br>&gt;=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 [ITU-T.Y.3300], [ONF-OpenFlow], [ONF-SDN-Arc=
hitecture],<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 [ITU-T.X.1252], [ITU-T.X.=
800], [RFC8329], [i2nsf-terminology],<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
 [consumer-facing-inf-im], [consumer-facing-inf-dm],<br>&gt;=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0 [i2nsf-nsf-cap-im], [nsf-facing-inf-dm], [registration-inf-=
dm], and<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 [nsf-triggered-steering].=C2=
=A0 In addition, the following terms are<br><br>Every term in this document=
 needs to be understandable without<br>reference to closed specifications o=
r internally defined. Please<br>ensure that this is so,<br><br><br>S 3.<br>=
&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 used for the I2NSF NSF-Facing Interface.=
<br>&gt;=C2=A0=C2=A0 <br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 The Registratio=
n Interface between the Security Controller and the<br>&gt;=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0 Developer&#39;s Management System can be implemented by RES=
TCONF<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 [RFC8040].=C2=A0 The data model=
 defined in [registration-inf-dm] can be<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0 used for the I2NSF Registration Interface.<br><br>What role does the De=
veloper&#39;s Management System play in this? I think<br>this refers to the=
 text above starting with &quot;The developers (or<br>vendors)...&quot;. Is=
 that correct?<br><br>Assuming I am correct, this seems like a potentially =
serious security<br>vulnerability in this design in that it potentially all=
ows an inside<br>attacker at the developer to seriously weaken a system&#39=
;s security.<br>What protections exist to prevent this?<br><br><br>S 4.<br>=
&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 administrator wants to control the staff=
 members&#39; access to a<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 particular =
Interner service (e.g., Example.com) during business<br>&gt;=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0 hours.=C2=A0 The following is an example high-level securit=
y policy rule<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 that the administrator =
requests: Block the staff members&#39; access to<br>&gt;=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0 Example.com from 9 AM to 6 PM.=C2=A0 The administrator sends t=
his high-<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 level security policy to th=
e Security Controller, then the Security<br><br>The text above suggests tha=
t high-level policies are via<br>RESTCONF/YANG, but this is clearly freefor=
m text.<br>COMMENTS<br>S 1.<br>&gt;=C2=A0=C2=A0 <br>&gt;=C2=A0=C2=A0 1.=C2=
=A0 Introduction<br>&gt;=C2=A0=C2=A0 <br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
 Interface to Network Security Functions (I2NSF) defines a framework<br>&gt=
;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 and interfaces for interacting with Network=
 Security Functions<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 (NSFs).=C2=A0 The=
 I2NSF framework allows heterogeneous NSFs developed by<br><br>Please defin=
e &quot;Network Security Functions&quot; here.<br><br><br><br><br>S 1.<br>&=
gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 functions in the NFV platform.=C2=A0 In t=
he I2NSF framework, each NSF<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 initiall=
y registers the profile of its own capabilities into the<br>&gt;=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0 system in order for themselves to be available in the=
 system.=C2=A0 In<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 addition, the Secur=
ity Controller is validated by the I2NSF Client<br>&gt;=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0 (also called I2NSF User) that the user is employing, so that t=
he user<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 can request security services=
 through the Security Controller.<br><br>In this case the user is the syste=
m administrator.<br><br><br>S 1.<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 [RFC=
7149] to provide different security functionality such as<br>&gt;=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0 firewalls [opsawg-firewalls], Deep Packet Inspection =
(DPI), and<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Distributed Denial of Serv=
ice (DDoS) attack mitigation; (iv) the use<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0 of NFV as supporting technology.=C2=A0 The implementation of I2NSF i=
n<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 these scenarios has allowed us to v=
erify the applicability and<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 effective=
ness of the I2NSF framework for a variety of use cases.<br><br>This would b=
e easier to read with a standard bulleted list.<br><br><br>S 2.<br>&gt;=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 network resources, which faci=
litates the design, delivery and<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0 operation of network services in a dynamic and scalable man=
ner<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 [ITU-T.Y.3300].=
<br>&gt;=C2=A0=C2=A0 <br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 o=C2=A0 Firewal=
l: A service function at the junction of two network<br>&gt;=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 segments that inspects every packet that =
attempts to cross the<br><br>Nit: It might not inspect *every* packet.<br><=
br><br>S 4.<br>&gt;=C2=A0=C2=A0 <br>&gt;=C2=A0=C2=A0 4.=C2=A0 Time-dependen=
t Web Access Control Service<br>&gt;=C2=A0=C2=A0 <br>&gt;=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0 This service scenario assumes that an enterprise network<br>&g=
t;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 administrator wants to control the staff m=
embers&#39; access to a<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 particular In=
terner service (e.g., Example.com) during business<br><br>Nit: &quot;Intern=
et&quot;<br><br><br>S 4.<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 inspection c=
apability is required to check whether the target URL of<br>&gt;=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0 a received packet is in the Example.com domain or not=
.<br>&gt;=C2=A0=C2=A0 <br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 The Security C=
ontroller maintains the security capabilities of each<br>&gt;=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0 NSF running in the I2NSF system, which have been reporte=
d by the<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Developer&#39;s Management S=
ystem via the Registation interface.=C2=A0 Based<br><br>Nit: &quot;Registra=
tion&quot;<br><br><br>S 4.<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 currently =
using the network.=C2=A0 Based on the retrieved information, the<br>&gt;=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0 Security Controller generates low-level securit=
y rules to check<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 whether the source I=
P address of a received packet matches any one<br>&gt;=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0 being used by a staff member.=C2=A0 In addition, the low-level se=
curity<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 rules should be able to determ=
ine that a received packet is of HTTP<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
 protocol.=C2=A0 The low-level security rules for web filter checks that<br=
><br>Nit: &quot;rules&quot;... &quot;checks&quot; disagree.<br><br><br>S 6.=
<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 translated into their packet forward=
ing rules, whereas NSFs enforce<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 NSF-r=
elated security rules requiring the security capabilities of the<br>&gt;=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0 NSFs.=C2=A0 For this purpose, the Security Cont=
roller instructs the SDN<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Controller v=
ia NSF-Facing Interface so that SDN forwarding elements<br>&gt;=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0 can perform the required security services with flow tab=
les under the<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 supervision of the SDN =
Controller.<br><br>I&#39;m having some trouble understanding the difference=
 here between NSFs<br>and SDN elements. They both seem to be software contr=
olled network<br>elements. Is this just some continuum about CPU power?<br>=
<br><br>S 6.<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 can perform the required=
 security services with flow tables under the<br>&gt;=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0 supervision of the SDN Controller.<br>&gt;=C2=A0=C2=A0 <br>&gt;=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 As an example, let us consider two different=
 types of security rules:<br>&gt;=C2=A0=C2=A0 <br>&gt;=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0 Rule A is a simple packet fltering rule that checks only the IP<b=
r><br>Nit: &quot;filtering&quot;<br><br><br>S 6.2.<br>&gt;=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 packets that have the same call-id.=
<br>&gt;=C2=A0=C2=A0 <br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 6.=C2=A0 The SD=
N Controller installs new rules (e.g., drop packets) into<br>&gt;=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 underlying switches.<br>&gt;=
=C2=A0=C2=A0 <br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 7.=C2=A0 The illegal pa=
ckets are dropped by these switches.<br><br>&quot;Illegal&quot; is probably=
 the wrong wrod here.<br><br><br>S 6.3.<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0 is helpful to determine security policies for such a =
network.<br>&gt;=C2=A0=C2=A0 <br>&gt;=C2=A0=C2=A0 6.3.=C2=A0 Attack Mitigat=
ion: Centralized DDoS-attack Mitigation System<br>&gt;=C2=A0=C2=A0 <br>&gt;=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 A centralized DDoS-attack mitigation can man=
age each network resource<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 and manipul=
ate rules to each switch through a common server for DDoS-<br><br>&quot;man=
ipulate rules to&quot; is not grammatical.<br><br><br>S 6.3.<br>&gt;=C2=A0=
=C2=A0 <br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Servers are categorized into =
stateless servers (e.g., DNS servers)<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
 and stateful servers (e.g., web servers).=C2=A0 For DDoS-attack<br>&gt;=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0 mitigation, traffic flows in switches are dynam=
ically configured by<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 traffic flow for=
warding path management according to the category of<br>&gt;=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0 servers [AVANT-GUARD].=C2=A0 Such a managenent should consi=
der the load<br><br>1. This seems hard to understand without this reference=
, which is not<br>public.<br>2. &quot;management&quot;<br><br><br>S 6.3.<br=
>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 mitigation, traffic flows in switches a=
re dynamically configured by<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 traffic =
flow forwarding path management according to the category of<br>&gt;=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0 servers [AVANT-GUARD].=C2=A0 Such a managenent sho=
uld consider the load<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 balance among t=
he switches for the defense against DDoS attacks.<br>&gt;=C2=A0=C2=A0 <br>&=
gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 The procedure of DDoS-attack mitigation o=
perations in this system is<br><br>&quot;procedure of... operations&quot; i=
s ungrammatical<br><br></div></div>
</div></div></div></div>

--000000000000d3a264057d9d601e--


From nobody Tue Dec 25 06:32:24 2018
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 A2B3C130E04; Tue, 25 Dec 2018 06:32:21 -0800 (PST)
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: 6.89.2
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: i2nsf@ietf.org
Message-ID: <154574834161.23972.3119044330877656350@ietfa.amsl.com>
Date: Tue, 25 Dec 2018 06:32:21 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2nsf/kHrPa22gOrDKMjNb9yVRjmgdr8s>
Subject: [I2nsf] I-D Action: draft-ietf-i2nsf-applicability-08.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: Tue, 25 Dec 2018 14:32:22 -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           : Applicability of Interfaces to Network Security Functions to Network-Based Security Services
        Authors         : Jaehoon Paul Jeong
                          Sangwon Hyun
                          Tae-Jin Ahn
                          Susan Hares
                          Diego R. Lopez
	Filename        : draft-ietf-i2nsf-applicability-08.txt
	Pages           : 26
	Date            : 2018-12-25

Abstract:
   This document describes the applicability of Interface to Network
   Security Functions (I2NSF) to network-based security services in
   Network Functions Virtualization (NFV) environments, such as
   firewall, deep packet inspection, or attack mitigation engines.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-i2nsf-applicability/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-i2nsf-applicability-08
https://datatracker.ietf.org/doc/html/draft-ietf-i2nsf-applicability-08

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-i2nsf-applicability-08


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 Tue Dec 25 06:42:42 2018
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 BE532130E03 for <i2nsf@ietfa.amsl.com>; Tue, 25 Dec 2018 06:42:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.5
X-Spam-Level: 
X-Spam-Status: No, score=-0.5 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HK_NAME_FM_MR_MRS=1.499, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-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 F5YdYCXbP0Qx for <i2nsf@ietfa.amsl.com>; Tue, 25 Dec 2018 06:42:38 -0800 (PST)
Received: from mail-it1-x12d.google.com (mail-it1-x12d.google.com [IPv6:2607:f8b0: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 C109E12D4E6 for <i2nsf@ietf.org>; Tue, 25 Dec 2018 06:42:37 -0800 (PST)
Received: by mail-it1-x12d.google.com with SMTP id m62so18498259ith.5 for <i2nsf@ietf.org>; Tue, 25 Dec 2018 06:42:37 -0800 (PST)
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=Yvq7V/NLYsgitS/hToQA62QPy5hs3dlbfCZoaop62hY=; b=HG/4xUrAmg8jKa7ET/DU003YrQdTWSb1xzEXMaIgDfjmPmwv7cKZPyn6qBU/QLMdPq Fh8/t9OMR2tkLB75pXl5XqR46UIEQPOLXepCDOkERQkQ3wXAn9TnxCYdYAFjDosBdgj3 I46xdmWJPiLUkCTnRjqQv/2ZuJQwDR9yc0G+1IbNbyuIoatqH1Ps0U3Gu5zafQrIdkhK cNCBfECM91sNzOYtvNz1LuzC1PL77qlMuQeWQF6Li93NuGsTL56GWJtozZGq0NHHV8oh 8QrffP560A5CkCcZtZZvf/QX+JQzOYX+Dk01cv2VKv7X50ScDQFfKpDTDv+mlHW9LMep 1a/w==
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=Yvq7V/NLYsgitS/hToQA62QPy5hs3dlbfCZoaop62hY=; b=F4Z1EHSsKHKxT3hDc8E3OHJMXrjvNOuDIdwwDSa5V5WXbr1v3EFRr1VRlFl0Wej04J 604kiK3fvJfbwh8bTQT/8DS0vQetL8K9H7rJ14bQ8FamhMfHu82nr9GetvI1guECDyBu +KkkxtHsP0/0GxlU+kcJsruJbvsYCW6lrd1BFS78ysFmfEodExaBBiClj4mpTY8p4XJq 8pN8Xk21dBUCnr/aZpF7RAFDfRHGdc9JDCXPNhDLCNWyo6VCqs7mRydikptm+5/zQ/vm iqCArmngFtmCksw5SLnbKz/2px0WDmW8yKr4ghBhXVjdogf6CopVkfFg9e0jEYiLdK2W iz5Q==
X-Gm-Message-State: AJcUukc13iIpExkBoR1yjlJtIDY4PtGTu1qC8JS9YbzLclOW5EVhIJ6s kmIseIPOGECRa+0LrOibt+ux4w2d8T+lQe55f4o=
X-Google-Smtp-Source: ALg8bN7g6pHDwR0Pn3mpZyXAAHmoBlRZwUnrhlIvVlVgbSDFu3KhDa7DNMOHVIO+7jVKMnySHnujcgPSJutSEaglPG4=
X-Received: by 2002:a24:2914:: with SMTP id p20mr3004227itp.156.1545748956840;  Tue, 25 Dec 2018 06:42:36 -0800 (PST)
MIME-Version: 1.0
References: <CABcZeBOjhEpw4gNDRgJD=FCWy1Wrirz_EsJefJjDHpp5mVe1fw@mail.gmail.com>
In-Reply-To: <CABcZeBOjhEpw4gNDRgJD=FCWy1Wrirz_EsJefJjDHpp5mVe1fw@mail.gmail.com>
From: "Mr. Jaehoon Paul Jeong" <jaehoon.paul@gmail.com>
Date: Tue, 25 Dec 2018 23:41:59 +0900
Message-ID: <CAPK2DewE2vbjAr41xErxnjmxK2CTmK2h9fXFTBSFCigpNj9XPQ@mail.gmail.com>
To: Eric Rescorla <ekr@rtfm.com>, Linda Dunbar <linda.dunbar@huawei.com>,  Yoav Nir <ynir.ietf@gmail.com>
Cc: "i2nsf@ietf.org" <i2nsf@ietf.org>, skku_secu-brain_all@googlegroups.com,  "Mr. Jaehoon Paul Jeong" <jaehoon.paul@gmail.com>
Content-Type: multipart/alternative; boundary="0000000000007c0738057dd9b939"
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2nsf/np64-GEPESaIj4yBrslhoe8INtE>
Subject: Re: [I2nsf] AD Review of draft-ietf-i2nsf-applicability-07
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, 25 Dec 2018 14:42:41 -0000

--0000000000007c0738057dd9b939
Content-Type: text/plain; charset="UTF-8"

Hi Eric, Linda and Yoav,
I have reflected all the comments from Eric and submitted the revision -08
as follows:
https://tools.ietf.org/html/draft-ietf-i2nsf-applicability-08

The changes are described in Appendix A of -08 document as follows:
-------------------------------------------------------------------------------------------------
Appendix A.  Changes from draft-ietf-i2nsf-applicability-07

   The following changes have been made from
   draft-ietf-i2nsf-applicability-07:

   o  This version has reflected all the comments from Eric Rescorla who
      is a Security Area Director as follows.

   o  In Section 1, Network Security Function (NFV) is defined in the
      viewpoint of the I2NSF framework.

   o  In Section 1, a user using the I2NSF User is clarified as a system
      administrator in the I2NSF framework.

   o  In Section 1, as the applicability of the I2NSF framework, four
      different scenarios are represented with a standard bulleted list.

   o  The standard document about ETSI-NFV is moved to Normative
      References.

   o  In Section 2, key terms (e.g., Network Function, Network Security
      Function, Network Functions Virtualization, and Servive Function
      Chaining) are internally defined along with the reference to open
      specifications.

   o  In Section 2, the definition of Firewall is corrected such that
      some suspicious packets are inspected by the firewall rather than
      every packet.

   o  In Section 3, for a Developer's Management System, the problem of
      an inside attacker is addressed, and a possible solution for the
      inside attacks is suggested through I2NSF NSF monitoring
      functionality.

   o  In Section 4, an XML file for the RESTCONF/YANG for the time-
      dependent web access control is pointed out with a reference to
      the Consumer-Facing Interface's data model
      [consumer-facing-inf-dm].

   o  In Section 6, the definitions of an SDN forwarding element and an
      NSF are clarified such that an SDN forwarding element is a switch
      running as either a hardware middle box or a software virtual
      switch, and an NSF is a virtual network function for a security
      service.

   o  In Section 6.3, a flow forwarding path management scheme in
      [AVANT-GUARD] is described in a self-contained way as follows.
      For DDoS-attack mitigation, the forwarding of traffic flows in
      switches can be dynamically configured such that malicious traffic
      flows are handled by the paths separated from normal traffic flows
      in order to minimize the impact of those malicious traffic on the
      the servers.  This flow path separation can be done by a flow
      forwarding path management scheme based on [AVANT-GUARD].

   o  Some typos are corrected such as "Interner -> Internet",
      "Registation -> Registration", "The low-level security rules for
      web filter checks -> The low-level security rules for web filter
      check", "fltering -> filtering", "illegal packets -> malicious
      packets", "manipulate rules -> configure rules", "managenent ->
      management", and "DDoS-attack mitigation operations -> DDoS-attack
      mitigation".
-------------------------------------------------------------------------------------------------

Thanks and Merry Christmas!

Best Regards,
Paul

On Fri, Dec 21, 2018 at 11:33 PM Eric Rescorla <ekr@rtfm.com> wrote:

> Rich version of this review at:
> https://mozphab-ietf.devsvcdev.mozaws.net/D3181
>
>
> I found a number of typographical and grammar errors. Please give this
> document a thorough read.
>
> IMPORTANT
> S 1.
> >
> >      Interface to Network Security Functions (I2NSF) defines a framework
> >      and interfaces for interacting with Network Security Functions
> >      (NSFs).  The I2NSF framework allows heterogeneous NSFs developed by
> >      different security solution vendors to be used in the Network
> >      Functions Virtualization (NFV) environment [ETSI-NFV] by utilizing
>
> Much of this document cannot be understood without reading ETSI-NFV,
> so it has to be a normative reference. It also would be helpful to
> provide a link.
>
>
> S 2.
> >      This document uses the terminology described in [RFC7149],
> >      [ITU-T.Y.3300], [ONF-OpenFlow], [ONF-SDN-Architecture],
> >      [ITU-T.X.1252], [ITU-T.X.800], [RFC8329], [i2nsf-terminology],
> >      [consumer-facing-inf-im], [consumer-facing-inf-dm],
> >      [i2nsf-nsf-cap-im], [nsf-facing-inf-dm], [registration-inf-dm], and
> >      [nsf-triggered-steering].  In addition, the following terms are
>
> Every term in this document needs to be understandable without
> reference to closed specifications or internally defined. Please
> ensure that this is so,
>
>
> S 3.
> >      used for the I2NSF NSF-Facing Interface.
> >
> >      The Registration Interface between the Security Controller and the
> >      Developer's Management System can be implemented by RESTCONF
> >      [RFC8040].  The data model defined in [registration-inf-dm] can be
> >      used for the I2NSF Registration Interface.
>
> What role does the Developer's Management System play in this? I think
> this refers to the text above starting with "The developers (or
> vendors)...". Is that correct?
>
> Assuming I am correct, this seems like a potentially serious security
> vulnerability in this design in that it potentially allows an inside
> attacker at the developer to seriously weaken a system's security.
> What protections exist to prevent this?
>
>
> S 4.
> >      administrator wants to control the staff members' access to a
> >      particular Interner service (e.g., Example.com) during business
> >      hours.  The following is an example high-level security policy rule
> >      that the administrator requests: Block the staff members' access to
> >      Example.com from 9 AM to 6 PM.  The administrator sends this high-
> >      level security policy to the Security Controller, then the Security
>
> The text above suggests that high-level policies are via
> RESTCONF/YANG, but this is clearly freeform text.
> COMMENTS
> S 1.
> >
> >   1.  Introduction
> >
> >      Interface to Network Security Functions (I2NSF) defines a framework
> >      and interfaces for interacting with Network Security Functions
> >      (NSFs).  The I2NSF framework allows heterogeneous NSFs developed by
>
> Please define "Network Security Functions" here.
>
>
>
>
> S 1.
> >      functions in the NFV platform.  In the I2NSF framework, each NSF
> >      initially registers the profile of its own capabilities into the
> >      system in order for themselves to be available in the system.  In
> >      addition, the Security Controller is validated by the I2NSF Client
> >      (also called I2NSF User) that the user is employing, so that the
> user
> >      can request security services through the Security Controller.
>
> In this case the user is the system administrator.
>
>
> S 1.
> >      [RFC7149] to provide different security functionality such as
> >      firewalls [opsawg-firewalls], Deep Packet Inspection (DPI), and
> >      Distributed Denial of Service (DDoS) attack mitigation; (iv) the use
> >      of NFV as supporting technology.  The implementation of I2NSF in
> >      these scenarios has allowed us to verify the applicability and
> >      effectiveness of the I2NSF framework for a variety of use cases.
>
> This would be easier to read with a standard bulleted list.
>
>
> S 2.
> >         network resources, which facilitates the design, delivery and
> >         operation of network services in a dynamic and scalable manner
> >         [ITU-T.Y.3300].
> >
> >      o  Firewall: A service function at the junction of two network
> >         segments that inspects every packet that attempts to cross the
>
> Nit: It might not inspect *every* packet.
>
>
> S 4.
> >
> >   4.  Time-dependent Web Access Control Service
> >
> >      This service scenario assumes that an enterprise network
> >      administrator wants to control the staff members' access to a
> >      particular Interner service (e.g., Example.com) during business
>
> Nit: "Internet"
>
>
> S 4.
> >      inspection capability is required to check whether the target URL of
> >      a received packet is in the Example.com domain or not.
> >
> >      The Security Controller maintains the security capabilities of each
> >      NSF running in the I2NSF system, which have been reported by the
> >      Developer's Management System via the Registation interface.  Based
>
> Nit: "Registration"
>
>
> S 4.
> >      currently using the network.  Based on the retrieved information,
> the
> >      Security Controller generates low-level security rules to check
> >      whether the source IP address of a received packet matches any one
> >      being used by a staff member.  In addition, the low-level security
> >      rules should be able to determine that a received packet is of HTTP
> >      protocol.  The low-level security rules for web filter checks that
>
> Nit: "rules"... "checks" disagree.
>
>
> S 6.
> >      translated into their packet forwarding rules, whereas NSFs enforce
> >      NSF-related security rules requiring the security capabilities of
> the
> >      NSFs.  For this purpose, the Security Controller instructs the SDN
> >      Controller via NSF-Facing Interface so that SDN forwarding elements
> >      can perform the required security services with flow tables under
> the
> >      supervision of the SDN Controller.
>
> I'm having some trouble understanding the difference here between NSFs
> and SDN elements. They both seem to be software controlled network
> elements. Is this just some continuum about CPU power?
>
>
> S 6.
> >      can perform the required security services with flow tables under
> the
> >      supervision of the SDN Controller.
> >
> >      As an example, let us consider two different types of security
> rules:
> >
> >      Rule A is a simple packet fltering rule that checks only the IP
>
> Nit: "filtering"
>
>
> S 6.2.
> >          packets that have the same call-id.
> >
> >      6.  The SDN Controller installs new rules (e.g., drop packets) into
> >          underlying switches.
> >
> >      7.  The illegal packets are dropped by these switches.
>
> "Illegal" is probably the wrong wrod here.
>
>
> S 6.3.
> >         is helpful to determine security policies for such a network.
> >
> >   6.3.  Attack Mitigation: Centralized DDoS-attack Mitigation System
> >
> >      A centralized DDoS-attack mitigation can manage each network
> resource
> >      and manipulate rules to each switch through a common server for
> DDoS-
>
> "manipulate rules to" is not grammatical.
>
>
> S 6.3.
> >
> >      Servers are categorized into stateless servers (e.g., DNS servers)
> >      and stateful servers (e.g., web servers).  For DDoS-attack
> >      mitigation, traffic flows in switches are dynamically configured by
> >      traffic flow forwarding path management according to the category of
> >      servers [AVANT-GUARD].  Such a managenent should consider the load
>
> 1. This seems hard to understand without this reference, which is not
> public.
> 2. "management"
>
>
> S 6.3.
> >      mitigation, traffic flows in switches are dynamically configured by
> >      traffic flow forwarding path management according to the category of
> >      servers [AVANT-GUARD].  Such a managenent should consider the load
> >      balance among the switches for the defense against DDoS attacks.
> >
> >      The procedure of DDoS-attack mitigation operations in this system is
>
> "procedure of... operations" is ungrammatical
>
>

-- 
===========================
Mr. Jaehoon (Paul) Jeong, Ph.D.
Associate Professor
Department of Software
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>

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

<div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr">Hi Eric, Linda and Yoav,=
<div>I have reflected all the comments from Eric and submitted the revision=
 -08 as follows:</div><div><a href=3D"https://tools.ietf.org/html/draft-iet=
f-i2nsf-applicability-08">https://tools.ietf.org/html/draft-ietf-i2nsf-appl=
icability-08</a><br></div><div><br></div><div>The changes are described in =
Appendix A of -08 document as follows:</div><div>--------------------------=
-----------------------------------------------------------------------</di=
v><div><div>Appendix A.=C2=A0 Changes from draft-ietf-i2nsf-applicability-0=
7</div><div><br></div><div>=C2=A0 =C2=A0The following changes have been mad=
e from</div><div>=C2=A0 =C2=A0draft-ietf-i2nsf-applicability-07:</div><div>=
<br></div><div>=C2=A0 =C2=A0o=C2=A0 This version has reflected all the comm=
ents from Eric Rescorla who</div><div>=C2=A0 =C2=A0 =C2=A0 is a Security Ar=
ea Director as follows.</div><div><br></div><div>=C2=A0 =C2=A0o=C2=A0 In Se=
ction 1, Network Security Function (NFV) is defined in the</div><div>=C2=A0=
 =C2=A0 =C2=A0 viewpoint of the I2NSF framework.</div><div><br></div><div>=
=C2=A0 =C2=A0o=C2=A0 In Section 1, a user using the I2NSF User is clarified=
 as a system</div><div>=C2=A0 =C2=A0 =C2=A0 administrator in the I2NSF fram=
ework.</div><div><br></div><div>=C2=A0 =C2=A0o=C2=A0 In Section 1, as the a=
pplicability of the I2NSF framework, four</div><div>=C2=A0 =C2=A0 =C2=A0 di=
fferent scenarios are represented with a standard bulleted list.</div><div>=
<br></div><div>=C2=A0 =C2=A0o=C2=A0 The standard document about ETSI-NFV is=
 moved to Normative</div><div>=C2=A0 =C2=A0 =C2=A0 References.</div><div><b=
r></div><div>=C2=A0 =C2=A0o=C2=A0 In Section 2, key terms (e.g., Network Fu=
nction, Network Security</div><div>=C2=A0 =C2=A0 =C2=A0 Function, Network F=
unctions Virtualization, and Servive Function</div><div>=C2=A0 =C2=A0 =C2=
=A0 Chaining) are internally defined along with the reference to open</div>=
<div>=C2=A0 =C2=A0 =C2=A0 specifications.</div><div><br></div><div>=C2=A0 =
=C2=A0o=C2=A0 In Section 2, the definition of Firewall is corrected such th=
at</div><div>=C2=A0 =C2=A0 =C2=A0 some suspicious packets are inspected by =
the firewall rather than</div><div>=C2=A0 =C2=A0 =C2=A0 every packet.</div>=
<div><br></div><div>=C2=A0 =C2=A0o=C2=A0 In Section 3, for a Developer&#39;=
s Management System, the problem of</div><div>=C2=A0 =C2=A0 =C2=A0 an insid=
e attacker is addressed, and a possible solution for the</div><div>=C2=A0 =
=C2=A0 =C2=A0 inside attacks is suggested through I2NSF NSF monitoring</div=
><div>=C2=A0 =C2=A0 =C2=A0 functionality.</div><div><br></div><div>=C2=A0 =
=C2=A0o=C2=A0 In Section 4, an XML file for the RESTCONF/YANG for the time-=
</div><div>=C2=A0 =C2=A0 =C2=A0 dependent web access control is pointed out=
 with a reference to</div><div>=C2=A0 =C2=A0 =C2=A0 the Consumer-Facing Int=
erface&#39;s data model</div><div>=C2=A0 =C2=A0 =C2=A0 [consumer-facing-inf=
-dm].</div><div><br></div><div>=C2=A0 =C2=A0o=C2=A0 In Section 6, the defin=
itions of an SDN forwarding element and an</div><div>=C2=A0 =C2=A0 =C2=A0 N=
SF are clarified such that an SDN forwarding element is a switch</div><div>=
=C2=A0 =C2=A0 =C2=A0 running as either a hardware middle box or a software =
virtual</div><div>=C2=A0 =C2=A0 =C2=A0 switch, and an NSF is a virtual netw=
ork function for a security</div><div>=C2=A0 =C2=A0 =C2=A0 service.</div><d=
iv><br></div><div>=C2=A0 =C2=A0o=C2=A0 In Section 6.3, a flow forwarding pa=
th management scheme in</div><div>=C2=A0 =C2=A0 =C2=A0 [AVANT-GUARD] is des=
cribed in a self-contained way as follows.</div><div>=C2=A0 =C2=A0 =C2=A0 F=
or DDoS-attack mitigation, the forwarding of traffic flows in</div><div>=C2=
=A0 =C2=A0 =C2=A0 switches can be dynamically configured such that maliciou=
s traffic</div><div>=C2=A0 =C2=A0 =C2=A0 flows are handled by the paths sep=
arated from normal traffic flows</div><div>=C2=A0 =C2=A0 =C2=A0 in order to=
 minimize the impact of those malicious traffic on the</div><div>=C2=A0 =C2=
=A0 =C2=A0 the servers.=C2=A0 This flow path separation can be done by a fl=
ow</div><div>=C2=A0 =C2=A0 =C2=A0 forwarding path management scheme based o=
n [AVANT-GUARD].</div><div><br></div><div>=C2=A0 =C2=A0o=C2=A0 Some typos a=
re corrected such as &quot;Interner -&gt; Internet&quot;,</div><div>=C2=A0 =
=C2=A0 =C2=A0 &quot;Registation -&gt; Registration&quot;, &quot;The low-lev=
el security rules for</div><div>=C2=A0 =C2=A0 =C2=A0 web filter checks -&gt=
; The low-level security rules for web filter</div><div>=C2=A0 =C2=A0 =C2=
=A0 check&quot;, &quot;fltering -&gt; filtering&quot;, &quot;illegal packet=
s -&gt; malicious</div><div>=C2=A0 =C2=A0 =C2=A0 packets&quot;, &quot;manip=
ulate rules -&gt; configure rules&quot;, &quot;managenent -&gt;</div><div>=
=C2=A0 =C2=A0 =C2=A0 management&quot;, and &quot;DDoS-attack mitigation ope=
rations -&gt; DDoS-attack</div><div>=C2=A0 =C2=A0 =C2=A0 mitigation&quot;.<=
/div></div><div>-----------------------------------------------------------=
--------------------------------------=C2=A0</div><div>=C2=A0<br></div><div=
>Thanks and Merry Christmas!</div><div><br></div><div>Best Regards,</div><d=
iv>Paul</div></div></div></div><br><div class=3D"gmail_quote"><div dir=3D"l=
tr">On Fri, Dec 21, 2018 at 11:33 PM Eric Rescorla &lt;<a href=3D"mailto:ek=
r@rtfm.com">ekr@rtfm.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">Rich version of t=
his review at:<br><a href=3D"https://mozphab-ietf.devsvcdev.mozaws.net/D318=
1" target=3D"_blank">https://mozphab-ietf.devsvcdev.mozaws.net/D3181</a><br=
><br><br>I found a number of typographical and grammar errors. Please give =
this<br>document a thorough read.<br><br>IMPORTANT<br>S 1.<br>&gt;=C2=A0=C2=
=A0 <br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Interface to Network Security Fu=
nctions (I2NSF) defines a framework<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 a=
nd interfaces for interacting with Network Security Functions<br>&gt;=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0 (NSFs).=C2=A0 The I2NSF framework allows heterogen=
eous NSFs developed by<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 different secu=
rity solution vendors to be used in the Network<br>&gt;=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0 Functions Virtualization (NFV) environment [ETSI-NFV] by utili=
zing<br><br>Much of this document cannot be understood without reading ETSI=
-NFV,<br>so it has to be a normative reference. It also would be helpful to=
<br>provide a link.<br><br><br>S 2.<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 T=
his document uses the terminology described in [RFC7149],<br>&gt;=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0 [ITU-T.Y.3300], [ONF-OpenFlow], [ONF-SDN-Architecture=
],<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 [ITU-T.X.1252], [ITU-T.X.800], [RF=
C8329], [i2nsf-terminology],<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 [consume=
r-facing-inf-im], [consumer-facing-inf-dm],<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0 [i2nsf-nsf-cap-im], [nsf-facing-inf-dm], [registration-inf-dm], and<=
br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 [nsf-triggered-steering].=C2=A0 In ad=
dition, the following terms are<br><br>Every term in this document needs to=
 be understandable without<br>reference to closed specifications or interna=
lly defined. Please<br>ensure that this is so,<br><br><br>S 3.<br>&gt;=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0 used for the I2NSF NSF-Facing Interface.<br>&gt=
;=C2=A0=C2=A0 <br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 The Registration Inter=
face between the Security Controller and the<br>&gt;=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0 Developer&#39;s Management System can be implemented by RESTCONF<=
br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 [RFC8040].=C2=A0 The data model defin=
ed in [registration-inf-dm] can be<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 us=
ed for the I2NSF Registration Interface.<br><br>What role does the Develope=
r&#39;s Management System play in this? I think<br>this refers to the text =
above starting with &quot;The developers (or<br>vendors)...&quot;. Is that =
correct?<br><br>Assuming I am correct, this seems like a potentially seriou=
s security<br>vulnerability in this design in that it potentially allows an=
 inside<br>attacker at the developer to seriously weaken a system&#39;s sec=
urity.<br>What protections exist to prevent this?<br><br><br>S 4.<br>&gt;=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 administrator wants to control the staff mem=
bers&#39; access to a<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 particular Inte=
rner service (e.g., Example.com) during business<br>&gt;=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0 hours.=C2=A0 The following is an example high-level security p=
olicy rule<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 that the administrator req=
uests: Block the staff members&#39; access to<br>&gt;=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0 Example.com from 9 AM to 6 PM.=C2=A0 The administrator sends this=
 high-<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 level security policy to the S=
ecurity Controller, then the Security<br><br>The text above suggests that h=
igh-level policies are via<br>RESTCONF/YANG, but this is clearly freeform t=
ext.<br>COMMENTS<br>S 1.<br>&gt;=C2=A0=C2=A0 <br>&gt;=C2=A0=C2=A0 1.=C2=A0 =
Introduction<br>&gt;=C2=A0=C2=A0 <br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Int=
erface to Network Security Functions (I2NSF) defines a framework<br>&gt;=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0 and interfaces for interacting with Network Sec=
urity Functions<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 (NSFs).=C2=A0 The I2N=
SF framework allows heterogeneous NSFs developed by<br><br>Please define &q=
uot;Network Security Functions&quot; here.<br><br><br><br><br>S 1.<br>&gt;=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 functions in the NFV platform.=C2=A0 In the =
I2NSF framework, each NSF<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 initially r=
egisters the profile of its own capabilities into the<br>&gt;=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0 system in order for themselves to be available in the sy=
stem.=C2=A0 In<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 addition, the Security=
 Controller is validated by the I2NSF Client<br>&gt;=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0 (also called I2NSF User) that the user is employing, so that the =
user<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 can request security services th=
rough the Security Controller.<br><br>In this case the user is the system a=
dministrator.<br><br><br>S 1.<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 [RFC714=
9] to provide different security functionality such as<br>&gt;=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0 firewalls [opsawg-firewalls], Deep Packet Inspection (DP=
I), and<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Distributed Denial of Service=
 (DDoS) attack mitigation; (iv) the use<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0 of NFV as supporting technology.=C2=A0 The implementation of I2NSF in<b=
r>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 these scenarios has allowed us to veri=
fy the applicability and<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 effectivenes=
s of the I2NSF framework for a variety of use cases.<br><br>This would be e=
asier to read with a standard bulleted list.<br><br><br>S 2.<br>&gt;=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 network resources, which facilit=
ates the design, delivery and<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0 operation of network services in a dynamic and scalable manner=
<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 [ITU-T.Y.3300].<br=
>&gt;=C2=A0=C2=A0 <br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 o=C2=A0 Firewall: =
A service function at the junction of two network<br>&gt;=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 segments that inspects every packet that att=
empts to cross the<br><br>Nit: It might not inspect *every* packet.<br><br>=
<br>S 4.<br>&gt;=C2=A0=C2=A0 <br>&gt;=C2=A0=C2=A0 4.=C2=A0 Time-dependent W=
eb Access Control Service<br>&gt;=C2=A0=C2=A0 <br>&gt;=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0 This service scenario assumes that an enterprise network<br>&gt;=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 administrator wants to control the staff mem=
bers&#39; access to a<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 particular Inte=
rner service (e.g., Example.com) during business<br><br>Nit: &quot;Internet=
&quot;<br><br><br>S 4.<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 inspection cap=
ability is required to check whether the target URL of<br>&gt;=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0 a received packet is in the Example.com domain or not.<b=
r>&gt;=C2=A0=C2=A0 <br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 The Security Cont=
roller maintains the security capabilities of each<br>&gt;=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0 NSF running in the I2NSF system, which have been reported b=
y the<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Developer&#39;s Management Syst=
em via the Registation interface.=C2=A0 Based<br><br>Nit: &quot;Registratio=
n&quot;<br><br><br>S 4.<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 currently usi=
ng the network.=C2=A0 Based on the retrieved information, the<br>&gt;=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0 Security Controller generates low-level security r=
ules to check<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 whether the source IP a=
ddress of a received packet matches any one<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0 being used by a staff member.=C2=A0 In addition, the low-level secur=
ity<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 rules should be able to determine=
 that a received packet is of HTTP<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 pr=
otocol.=C2=A0 The low-level security rules for web filter checks that<br><b=
r>Nit: &quot;rules&quot;... &quot;checks&quot; disagree.<br><br><br>S 6.<br=
>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 translated into their packet forwarding=
 rules, whereas NSFs enforce<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 NSF-rela=
ted security rules requiring the security capabilities of the<br>&gt;=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0 NSFs.=C2=A0 For this purpose, the Security Control=
ler instructs the SDN<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Controller via =
NSF-Facing Interface so that SDN forwarding elements<br>&gt;=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0 can perform the required security services with flow tables=
 under the<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 supervision of the SDN Con=
troller.<br><br>I&#39;m having some trouble understanding the difference he=
re between NSFs<br>and SDN elements. They both seem to be software controll=
ed network<br>elements. Is this just some continuum about CPU power?<br><br=
><br>S 6.<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 can perform the required se=
curity services with flow tables under the<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0 supervision of the SDN Controller.<br>&gt;=C2=A0=C2=A0 <br>&gt;=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0 As an example, let us consider two different ty=
pes of security rules:<br>&gt;=C2=A0=C2=A0 <br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0 Rule A is a simple packet fltering rule that checks only the IP<br><=
br>Nit: &quot;filtering&quot;<br><br><br>S 6.2.<br>&gt;=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 packets that have the same call-id.<br=
>&gt;=C2=A0=C2=A0 <br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 6.=C2=A0 The SDN C=
ontroller installs new rules (e.g., drop packets) into<br>&gt;=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 underlying switches.<br>&gt;=C2=
=A0=C2=A0 <br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 7.=C2=A0 The illegal packe=
ts are dropped by these switches.<br><br>&quot;Illegal&quot; is probably th=
e wrong wrod here.<br><br><br>S 6.3.<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0 is helpful to determine security policies for such a net=
work.<br>&gt;=C2=A0=C2=A0 <br>&gt;=C2=A0=C2=A0 6.3.=C2=A0 Attack Mitigation=
: Centralized DDoS-attack Mitigation System<br>&gt;=C2=A0=C2=A0 <br>&gt;=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0 A centralized DDoS-attack mitigation can manage=
 each network resource<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 and manipulate=
 rules to each switch through a common server for DDoS-<br><br>&quot;manipu=
late rules to&quot; is not grammatical.<br><br><br>S 6.3.<br>&gt;=C2=A0=C2=
=A0 <br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Servers are categorized into sta=
teless servers (e.g., DNS servers)<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 an=
d stateful servers (e.g., web servers).=C2=A0 For DDoS-attack<br>&gt;=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0 mitigation, traffic flows in switches are dynamica=
lly configured by<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 traffic flow forwar=
ding path management according to the category of<br>&gt;=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0 servers [AVANT-GUARD].=C2=A0 Such a managenent should consider=
 the load<br><br>1. This seems hard to understand without this reference, w=
hich is not<br>public.<br>2. &quot;management&quot;<br><br><br>S 6.3.<br>&g=
t;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 mitigation, traffic flows in switches are =
dynamically configured by<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 traffic flo=
w forwarding path management according to the category of<br>&gt;=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0 servers [AVANT-GUARD].=C2=A0 Such a managenent should=
 consider the load<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 balance among the =
switches for the defense against DDoS attacks.<br>&gt;=C2=A0=C2=A0 <br>&gt;=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 The procedure of DDoS-attack mitigation oper=
ations in this system is<br><br>&quot;procedure of... operations&quot; is u=
ngrammatical<br><br></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 Software<br>Sungkyunkwan Univers=
ity<br>Office: +82-31-299-4957<br>Email: <a href=3D"mailto:jaehoon.paul@gma=
il.com" target=3D"_blank">jaehoon.paul@gmail.com</a>,=C2=A0<a href=3D"mailt=
o:pauljeong@skku.edu" style=3D"font-size:12.8px" target=3D"_blank">pauljeon=
g@skku.edu</a><br>Personal Homepage: <a href=3D"http://cpslab.skku.edu/peop=
le-jaehoon-jeong.php" target=3D"_blank">http://iotlab.skku.edu/people-jaeho=
on-jeong.php</a><br></div></div></div></div></div></div></div></div>

--0000000000007c0738057dd9b939--


From nobody Wed Dec 26 10:44:49 2018
Return-Path: <ekr@rtfm.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 2E78C1311D2 for <i2nsf@ietfa.amsl.com>; Wed, 26 Dec 2018 10:44:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=rtfm-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 QZMNi8LFXdin for <i2nsf@ietfa.amsl.com>; Wed, 26 Dec 2018 10:44:44 -0800 (PST)
Received: from mail-lf1-x12c.google.com (mail-lf1-x12c.google.com [IPv6:2a00:1450:4864:20::12c]) (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 4A6651311D7 for <i2nsf@ietf.org>; Wed, 26 Dec 2018 10:44:43 -0800 (PST)
Received: by mail-lf1-x12c.google.com with SMTP id l10so11328500lfh.9 for <i2nsf@ietf.org>; Wed, 26 Dec 2018 10:44:43 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rtfm-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=WWnrG9yhLRMTViVBS/N1rU3qUZlglGNYedx0Y1J2sxE=; b=vkorg18UZwCzpK5MTu28vB3g/3n49G9Kj/0q6Ng0Wl8b7uWUMRyIsoEr0nzcU5HCaE 7OdlXz+UPExAqbBuSL1yyMcLEePkCBX6uZpgNEZzqezl6wMtDb0CVBl6HHjA3+RJ1AQQ Jq/4tlDE9cWC6xoID0I6j9rCHczkll/iMhab9XuPZ6wvRnOII3vIld/1WxebbS+YQxGj cM+vsRHv/KAsOHaXYvJfBbQS1rBFP0hkrLiGvsMRDggHRapYsQw++1lPabppvbURZhVw 8ve4eO/10ycrfFy14r93FE7REhPkdRt0I1O4P3VBt+/wtAkefsmMtwzViImK8l0nHrrw OmjQ==
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=WWnrG9yhLRMTViVBS/N1rU3qUZlglGNYedx0Y1J2sxE=; b=hGucoBa5VEgq1dFG7OSf9RokQh61lD2O4zQDzmRt1PdNNVPf3z+AxKNXT9GoIMeeNd imUc98yfUoIYissb6gaZVYH338D1q/oiE4s9ivEjOdgVkwfZB+0LUQuH5ZiaWFzxnzgZ 8M0GVieJyfXzoZXs1oJbG2ehxisYIyhfWRJW+r3o9mLrSrt291DmjFcyI0Rm02DSpagk 7ecGpfSoAMUET+dK+8wIcDxQ3rh/j8qRHAXQhp4TAHlvVcTveXRkgdlBEk2bqy6hswij Eahl2DSdit8hvw6MlEa+c+RwsrJF4T8/lhaCLlRkLiM2A6G7YL4kFZF5jRlA2tUc46DR K8gw==
X-Gm-Message-State: AA+aEWazmCVI7GPsEgnqkyQkyES8l+GMEFibeiZrmfb6ARJ0RO/Y0DJU PP04CRM5UI5/9W7rDk2gznw9zmpjExPhbTDvB2YWGQ==
X-Google-Smtp-Source: AFSGD/Xz/5PRfjpXjHPm+lkrJ7HACX2fBkvllVtbNSYRv9Dpi1FMVd90IqJEqomFxL767Rxv5xDizGyBvVrhCl6OkUI=
X-Received: by 2002:a19:54d7:: with SMTP id b84mr9848275lfl.131.1545849881383;  Wed, 26 Dec 2018 10:44:41 -0800 (PST)
MIME-Version: 1.0
References: <CABcZeBOjhEpw4gNDRgJD=FCWy1Wrirz_EsJefJjDHpp5mVe1fw@mail.gmail.com> <CAPK2DewE2vbjAr41xErxnjmxK2CTmK2h9fXFTBSFCigpNj9XPQ@mail.gmail.com>
In-Reply-To: <CAPK2DewE2vbjAr41xErxnjmxK2CTmK2h9fXFTBSFCigpNj9XPQ@mail.gmail.com>
From: Eric Rescorla <ekr@rtfm.com>
Date: Wed, 26 Dec 2018 10:44:01 -0800
Message-ID: <CABcZeBNZhqTawAFcj9p01ig-tE=XaFm5yCXuGJQFiqoOGgNZxA@mail.gmail.com>
To: "Mr. Jaehoon Paul Jeong" <jaehoon.paul@gmail.com>
Cc: Linda Dunbar <linda.dunbar@huawei.com>, Yoav Nir <ynir.ietf@gmail.com>,  "i2nsf@ietf.org" <i2nsf@ietf.org>, skku_secu-brain_all@googlegroups.com
Content-Type: multipart/alternative; boundary="0000000000000e6abe057df139a3"
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2nsf/lqRRx8HjNizQDnNok0Mh6F1lCmk>
Subject: Re: [I2nsf] AD Review of draft-ietf-i2nsf-applicability-07
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, 26 Dec 2018 18:44:48 -0000

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

Paul,

Thanks for your new version. Some responses below.


On Tue, Dec 25, 2018 at 6:42 AM Mr. Jaehoon Paul Jeong <
jaehoon.paul@gmail.com> wrote:

> Hi Eric, Linda and Yoav,
> I have reflected all the comments from Eric and submitted the revision -08
> as follows:
> https://tools.ietf.org/html/draft-ietf-i2nsf-applicability-08
>
> The changes are described in Appendix A of -08 document as follows:
>
> -------------------------------------------------------------------------------------------------
> Appendix A.  Changes from draft-ietf-i2nsf-applicability-07
>
>    The following changes have been made from
>    draft-ietf-i2nsf-applicability-07:
>
>    o  This version has reflected all the comments from Eric Rescorla who
>       is a Security Area Director as follows.
>
>    o  In Section 1, Network Security Function (NFV) is defined in the
>       viewpoint of the I2NSF framework.
>
>    o  In Section 1, a user using the I2NSF User is clarified as a system
>       administrator in the I2NSF framework.
>
>    o  In Section 1, as the applicability of the I2NSF framework, four
>       different scenarios are represented with a standard bulleted list.
>
>    o  The standard document about ETSI-NFV is moved to Normative
>       References.
>
>    o  In Section 2, key terms (e.g., Network Function, Network Security
>       Function, Network Functions Virtualization, and Servive Function
>       Chaining) are internally defined along with the reference to open
>       specifications.
>
>    o  In Section 2, the definition of Firewall is corrected such that
>       some suspicious packets are inspected by the firewall rather than
>       every packet.
>
>    o  In Section 3, for a Developer's Management System, the problem of
>       an inside attacker is addressed, and a possible solution for the
>       inside attacks is suggested through I2NSF NSF monitoring
>       functionality.
>

I'm still pretty concerned about this. Standardizing a situation in which
the
developer of your firewall has real-time management-level access to
that firewall seems extremely insecure, especially when that access is
authenticated via conventional credentials that are online as part of
the transaction (as opposed to software builds which can be signed
offline). This doesn't seem like a best practice. Why is it necessary?



   o  In Section 4, an XML file for the RESTCONF/YANG for the time-
>       dependent web access control is pointed out with a reference to
>       the Consumer-Facing Interface's data model
>       [consumer-facing-inf-dm].
>

I didn't follow this change. The example you give of a high level security
policy is clearly freeform text and then you talk about XML. Is this just
example a summary of the semantics of something which would actually be an
XML file? Something else?



   o  In Section 6, the definitions of an SDN forwarding element and an
>       NSF are clarified such that an SDN forwarding element is a switch
>       running as either a hardware middle box or a software virtual
>       switch, and an NSF is a virtual network function for a security
>       service.
>

This wasn't clear to me either. Based on this text it would seem that
you could run an NSF on an SDN element, so it's not clear why they
are disjoint sets. Can you give me more information here?

-Ekr


>    o  In Section 6.3, a flow forwarding path management scheme in
>       [AVANT-GUARD] is described in a self-contained way as follows.
>       For DDoS-attack mitigation, the forwarding of traffic flows in
>       switches can be dynamically configured such that malicious traffic
>       flows are handled by the paths separated from normal traffic flows
>       in order to minimize the impact of those malicious traffic on the
>       the servers.  This flow path separation can be done by a flow
>       forwarding path management scheme based on [AVANT-GUARD].
>
>    o  Some typos are corrected such as "Interner -> Internet",
>       "Registation -> Registration", "The low-level security rules for
>       web filter checks -> The low-level security rules for web filter
>       check", "fltering -> filtering", "illegal packets -> malicious
>       packets", "manipulate rules -> configure rules", "managenent ->
>       management", and "DDoS-attack mitigation operations -> DDoS-attack
>       mitigation".
>
> -------------------------------------------------------------------------------------------------
>
> Thanks and Merry Christmas!
>
> Best Regards,
> Paul
>
> On Fri, Dec 21, 2018 at 11:33 PM Eric Rescorla <ekr@rtfm.com> wrote:
>
>> Rich version of this review at:
>> https://mozphab-ietf.devsvcdev.mozaws.net/D3181
>>
>>
>> I found a number of typographical and grammar errors. Please give this
>> document a thorough read.
>>
>> IMPORTANT
>> S 1.
>> >
>> >      Interface to Network Security Functions (I2NSF) defines a framework
>> >      and interfaces for interacting with Network Security Functions
>> >      (NSFs).  The I2NSF framework allows heterogeneous NSFs developed by
>> >      different security solution vendors to be used in the Network
>> >      Functions Virtualization (NFV) environment [ETSI-NFV] by utilizing
>>
>> Much of this document cannot be understood without reading ETSI-NFV,
>> so it has to be a normative reference. It also would be helpful to
>> provide a link.
>>
>>
>> S 2.
>> >      This document uses the terminology described in [RFC7149],
>> >      [ITU-T.Y.3300], [ONF-OpenFlow], [ONF-SDN-Architecture],
>> >      [ITU-T.X.1252], [ITU-T.X.800], [RFC8329], [i2nsf-terminology],
>> >      [consumer-facing-inf-im], [consumer-facing-inf-dm],
>> >      [i2nsf-nsf-cap-im], [nsf-facing-inf-dm], [registration-inf-dm], and
>> >      [nsf-triggered-steering].  In addition, the following terms are
>>
>> Every term in this document needs to be understandable without
>> reference to closed specifications or internally defined. Please
>> ensure that this is so,
>>
>>
>> S 3.
>> >      used for the I2NSF NSF-Facing Interface.
>> >
>> >      The Registration Interface between the Security Controller and the
>> >      Developer's Management System can be implemented by RESTCONF
>> >      [RFC8040].  The data model defined in [registration-inf-dm] can be
>> >      used for the I2NSF Registration Interface.
>>
>> What role does the Developer's Management System play in this? I think
>> this refers to the text above starting with "The developers (or
>> vendors)...". Is that correct?
>>
>> Assuming I am correct, this seems like a potentially serious security
>> vulnerability in this design in that it potentially allows an inside
>> attacker at the developer to seriously weaken a system's security.
>> What protections exist to prevent this?
>>
>>
>> S 4.
>> >      administrator wants to control the staff members' access to a
>> >      particular Interner service (e.g., Example.com) during business
>> >      hours.  The following is an example high-level security policy rule
>> >      that the administrator requests: Block the staff members' access to
>> >      Example.com from 9 AM to 6 PM.  The administrator sends this high-
>> >      level security policy to the Security Controller, then the Security
>>
>> The text above suggests that high-level policies are via
>> RESTCONF/YANG, but this is clearly freeform text.
>> COMMENTS
>> S 1.
>> >
>> >   1.  Introduction
>> >
>> >      Interface to Network Security Functions (I2NSF) defines a framework
>> >      and interfaces for interacting with Network Security Functions
>> >      (NSFs).  The I2NSF framework allows heterogeneous NSFs developed by
>>
>> Please define "Network Security Functions" here.
>>
>>
>>
>>
>> S 1.
>> >      functions in the NFV platform.  In the I2NSF framework, each NSF
>> >      initially registers the profile of its own capabilities into the
>> >      system in order for themselves to be available in the system.  In
>> >      addition, the Security Controller is validated by the I2NSF Client
>> >      (also called I2NSF User) that the user is employing, so that the
>> user
>> >      can request security services through the Security Controller.
>>
>> In this case the user is the system administrator.
>>
>>
>> S 1.
>> >      [RFC7149] to provide different security functionality such as
>> >      firewalls [opsawg-firewalls], Deep Packet Inspection (DPI), and
>> >      Distributed Denial of Service (DDoS) attack mitigation; (iv) the
>> use
>> >      of NFV as supporting technology.  The implementation of I2NSF in
>> >      these scenarios has allowed us to verify the applicability and
>> >      effectiveness of the I2NSF framework for a variety of use cases.
>>
>> This would be easier to read with a standard bulleted list.
>>
>>
>> S 2.
>> >         network resources, which facilitates the design, delivery and
>> >         operation of network services in a dynamic and scalable manner
>> >         [ITU-T.Y.3300].
>> >
>> >      o  Firewall: A service function at the junction of two network
>> >         segments that inspects every packet that attempts to cross the
>>
>> Nit: It might not inspect *every* packet.
>>
>>
>> S 4.
>> >
>> >   4.  Time-dependent Web Access Control Service
>> >
>> >      This service scenario assumes that an enterprise network
>> >      administrator wants to control the staff members' access to a
>> >      particular Interner service (e.g., Example.com) during business
>>
>> Nit: "Internet"
>>
>>
>> S 4.
>> >      inspection capability is required to check whether the target URL
>> of
>> >      a received packet is in the Example.com domain or not.
>> >
>> >      The Security Controller maintains the security capabilities of each
>> >      NSF running in the I2NSF system, which have been reported by the
>> >      Developer's Management System via the Registation interface.  Based
>>
>> Nit: "Registration"
>>
>>
>> S 4.
>> >      currently using the network.  Based on the retrieved information,
>> the
>> >      Security Controller generates low-level security rules to check
>> >      whether the source IP address of a received packet matches any one
>> >      being used by a staff member.  In addition, the low-level security
>> >      rules should be able to determine that a received packet is of HTTP
>> >      protocol.  The low-level security rules for web filter checks that
>>
>> Nit: "rules"... "checks" disagree.
>>
>>
>> S 6.
>> >      translated into their packet forwarding rules, whereas NSFs enforce
>> >      NSF-related security rules requiring the security capabilities of
>> the
>> >      NSFs.  For this purpose, the Security Controller instructs the SDN
>> >      Controller via NSF-Facing Interface so that SDN forwarding elements
>> >      can perform the required security services with flow tables under
>> the
>> >      supervision of the SDN Controller.
>>
>> I'm having some trouble understanding the difference here between NSFs
>> and SDN elements. They both seem to be software controlled network
>> elements. Is this just some continuum about CPU power?
>>
>>
>> S 6.
>> >      can perform the required security services with flow tables under
>> the
>> >      supervision of the SDN Controller.
>> >
>> >      As an example, let us consider two different types of security
>> rules:
>> >
>> >      Rule A is a simple packet fltering rule that checks only the IP
>>
>> Nit: "filtering"
>>
>>
>> S 6.2.
>> >          packets that have the same call-id.
>> >
>> >      6.  The SDN Controller installs new rules (e.g., drop packets) into
>> >          underlying switches.
>> >
>> >      7.  The illegal packets are dropped by these switches.
>>
>> "Illegal" is probably the wrong wrod here.
>>
>>
>> S 6.3.
>> >         is helpful to determine security policies for such a network.
>> >
>> >   6.3.  Attack Mitigation: Centralized DDoS-attack Mitigation System
>> >
>> >      A centralized DDoS-attack mitigation can manage each network
>> resource
>> >      and manipulate rules to each switch through a common server for
>> DDoS-
>>
>> "manipulate rules to" is not grammatical.
>>
>>
>> S 6.3.
>> >
>> >      Servers are categorized into stateless servers (e.g., DNS servers)
>> >      and stateful servers (e.g., web servers).  For DDoS-attack
>> >      mitigation, traffic flows in switches are dynamically configured by
>> >      traffic flow forwarding path management according to the category
>> of
>> >      servers [AVANT-GUARD].  Such a managenent should consider the load
>>
>> 1. This seems hard to understand without this reference, which is not
>> public.
>> 2. "management"
>>
>>
>> S 6.3.
>> >      mitigation, traffic flows in switches are dynamically configured by
>> >      traffic flow forwarding path management according to the category
>> of
>> >      servers [AVANT-GUARD].  Such a managenent should consider the load
>> >      balance among the switches for the defense against DDoS attacks.
>> >
>> >      The procedure of DDoS-attack mitigation operations in this system
>> is
>>
>> "procedure of... operations" is ungrammatical
>>
>>
>
> --
> ===========================
> Mr. Jaehoon (Paul) Jeong, Ph.D.
> Associate Professor
> Department of Software
> 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>
>

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

<div dir=3D"ltr"><div dir=3D"ltr"><div>Paul,</div><div><br></div><div>Thank=
s for your new version. Some responses below.<br></div><div><br></div></div=
><br><div class=3D"gmail_quote"><div dir=3D"ltr">On Tue, Dec 25, 2018 at 6:=
42 AM 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_q=
uote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,2=
04);padding-left:1ex"><div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr">Hi=
 Eric, Linda and Yoav,<div>I have reflected all the comments from Eric and =
submitted the revision -08 as follows:</div><div><a href=3D"https://tools.i=
etf.org/html/draft-ietf-i2nsf-applicability-08" target=3D"_blank">https://t=
ools.ietf.org/html/draft-ietf-i2nsf-applicability-08</a><br></div><div><br>=
</div><div>The changes are described in Appendix A of -08 document as follo=
ws:</div><div>-------------------------------------------------------------=
------------------------------------</div><div><div>Appendix A.=C2=A0 Chang=
es from draft-ietf-i2nsf-applicability-07</div><div><br></div><div>=C2=A0 =
=C2=A0The following changes have been made from</div><div>=C2=A0 =C2=A0draf=
t-ietf-i2nsf-applicability-07:</div><div><br></div><div>=C2=A0 =C2=A0o=C2=
=A0 This version has reflected all the comments from Eric Rescorla who</div=
><div>=C2=A0 =C2=A0 =C2=A0 is a Security Area Director as follows.</div><di=
v><br></div><div>=C2=A0 =C2=A0o=C2=A0 In Section 1, Network Security Functi=
on (NFV) is defined in the</div><div>=C2=A0 =C2=A0 =C2=A0 viewpoint of the =
I2NSF framework.</div><div><br></div><div>=C2=A0 =C2=A0o=C2=A0 In Section 1=
, a user using the I2NSF User is clarified as a system</div><div>=C2=A0 =C2=
=A0 =C2=A0 administrator in the I2NSF framework.</div><div><br></div><div>=
=C2=A0 =C2=A0o=C2=A0 In Section 1, as the applicability of the I2NSF framew=
ork, four</div><div>=C2=A0 =C2=A0 =C2=A0 different scenarios are represente=
d with a standard bulleted list.</div><div><br></div><div>=C2=A0 =C2=A0o=C2=
=A0 The standard document about ETSI-NFV is moved to Normative</div><div>=
=C2=A0 =C2=A0 =C2=A0 References.</div><div><br></div><div>=C2=A0 =C2=A0o=C2=
=A0 In Section 2, key terms (e.g., Network Function, Network Security</div>=
<div>=C2=A0 =C2=A0 =C2=A0 Function, Network Functions Virtualization, and S=
ervive Function</div><div>=C2=A0 =C2=A0 =C2=A0 Chaining) are internally def=
ined along with the reference to open</div><div>=C2=A0 =C2=A0 =C2=A0 specif=
ications.</div><div><br></div><div>=C2=A0 =C2=A0o=C2=A0 In Section 2, the d=
efinition of Firewall is corrected such that</div><div>=C2=A0 =C2=A0 =C2=A0=
 some suspicious packets are inspected by the firewall rather than</div><di=
v>=C2=A0 =C2=A0 =C2=A0 every packet.</div><div><br></div><div>=C2=A0 =C2=A0=
o=C2=A0 In Section 3, for a Developer&#39;s Management System, the problem =
of</div><div>=C2=A0 =C2=A0 =C2=A0 an inside attacker is addressed, and a po=
ssible solution for the</div><div>=C2=A0 =C2=A0 =C2=A0 inside attacks is su=
ggested through I2NSF NSF monitoring</div><div>=C2=A0 =C2=A0 =C2=A0 functio=
nality.</div></div></div></div></div></blockquote><div><br></div><div>I&#39=
;m still pretty concerned about this. Standardizing a situation in which th=
e</div><div>developer of your firewall has real-time management-level acces=
s to</div><div>that firewall seems extremely insecure, especially when that=
 access is</div><div>authenticated via conventional credentials that are on=
line as part of</div><div>the transaction (as opposed to software builds wh=
ich can be signed</div><div>offline). This doesn&#39;t seem like a best pra=
ctice. Why is it necessary?</div><div><br></div><div><br></div><div><br></d=
iv><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;bord=
er-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr"><div =
dir=3D"ltr"><div dir=3D"ltr"><div><div>=C2=A0 =C2=A0o=C2=A0 In Section 4, a=
n XML file for the RESTCONF/YANG for the time-</div><div>=C2=A0 =C2=A0 =C2=
=A0 dependent web access control is pointed out with a reference to</div><d=
iv>=C2=A0 =C2=A0 =C2=A0 the Consumer-Facing Interface&#39;s data model</div=
><div>=C2=A0 =C2=A0 =C2=A0 [consumer-facing-inf-dm].</div></div></div></div=
></div></blockquote><div><br></div><div>I didn&#39;t follow this change. Th=
e example you give of a high level security</div><div>policy is clearly fre=
eform text and then you talk about XML. Is this just</div><div>example a su=
mmary of the semantics of something which would actually be an</div><div>XM=
L file? Something else?</div><div><br></div><div><br></div><div><br></div><=
blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-l=
eft:1px solid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr"><div dir=
=3D"ltr"><div dir=3D"ltr"><div><div>=C2=A0 =C2=A0o=C2=A0 In Section 6, the =
definitions of an SDN forwarding element and an</div><div>=C2=A0 =C2=A0 =C2=
=A0 NSF are clarified such that an SDN forwarding element is a switch</div>=
<div>=C2=A0 =C2=A0 =C2=A0 running as either a hardware middle box or a soft=
ware virtual</div><div>=C2=A0 =C2=A0 =C2=A0 switch, and an NSF is a virtual=
 network function for a security</div><div>=C2=A0 =C2=A0 =C2=A0 service.</d=
iv></div></div></div></div></blockquote><div><br></div><div>This wasn&#39;t=
 clear to me either. Based on this text it would seem that</div><div>you co=
uld run an NSF on an SDN element, so it&#39;s not clear why they</div><div>=
are disjoint sets. Can you give me more information here?<br></div><div><br=
></div><div>-Ekr</div><div><br></div><blockquote class=3D"gmail_quote" styl=
e=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);paddin=
g-left:1ex"><div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr"><div><div><b=
r></div><div>=C2=A0 =C2=A0o=C2=A0 In Section 6.3, a flow forwarding path ma=
nagement scheme in</div><div>=C2=A0 =C2=A0 =C2=A0 [AVANT-GUARD] is describe=
d in a self-contained way as follows.</div><div>=C2=A0 =C2=A0 =C2=A0 For DD=
oS-attack mitigation, the forwarding of traffic flows in</div><div>=C2=A0 =
=C2=A0 =C2=A0 switches can be dynamically configured such that malicious tr=
affic</div><div>=C2=A0 =C2=A0 =C2=A0 flows are handled by the paths separat=
ed from normal traffic flows</div><div>=C2=A0 =C2=A0 =C2=A0 in order to min=
imize the impact of those malicious traffic on the</div><div>=C2=A0 =C2=A0 =
=C2=A0 the servers.=C2=A0 This flow path separation can be done by a flow</=
div><div>=C2=A0 =C2=A0 =C2=A0 forwarding path management scheme based on [A=
VANT-GUARD].</div><div><br></div><div>=C2=A0 =C2=A0o=C2=A0 Some typos are c=
orrected such as &quot;Interner -&gt; Internet&quot;,</div><div>=C2=A0 =C2=
=A0 =C2=A0 &quot;Registation -&gt; Registration&quot;, &quot;The low-level =
security rules for</div><div>=C2=A0 =C2=A0 =C2=A0 web filter checks -&gt; T=
he low-level security rules for web filter</div><div>=C2=A0 =C2=A0 =C2=A0 c=
heck&quot;, &quot;fltering -&gt; filtering&quot;, &quot;illegal packets -&g=
t; malicious</div><div>=C2=A0 =C2=A0 =C2=A0 packets&quot;, &quot;manipulate=
 rules -&gt; configure rules&quot;, &quot;managenent -&gt;</div><div>=C2=A0=
 =C2=A0 =C2=A0 management&quot;, and &quot;DDoS-attack mitigation operation=
s -&gt; DDoS-attack</div><div>=C2=A0 =C2=A0 =C2=A0 mitigation&quot;.</div><=
/div><div>-----------------------------------------------------------------=
--------------------------------=C2=A0</div><div>=C2=A0<br></div><div>Thank=
s and Merry Christmas!</div><div><br></div><div>Best Regards,</div><div>Pau=
l</div></div></div></div><br><div class=3D"gmail_quote"><div dir=3D"ltr">On=
 Fri, Dec 21, 2018 at 11:33 PM Eric Rescorla &lt;<a href=3D"mailto:ekr@rtfm=
.com" target=3D"_blank">ekr@rtfm.com</a>&gt; wrote:<br></div><blockquote cl=
ass=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">Rich =
version of this review at:<br><a href=3D"https://mozphab-ietf.devsvcdev.moz=
aws.net/D3181" target=3D"_blank">https://mozphab-ietf.devsvcdev.mozaws.net/=
D3181</a><br><br><br>I found a number of typographical and grammar errors. =
Please give this<br>document a thorough read.<br><br>IMPORTANT<br>S 1.<br>&=
gt;=C2=A0=C2=A0 <br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Interface to Network=
 Security Functions (I2NSF) defines a framework<br>&gt;=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0 and interfaces for interacting with Network Security Functions=
<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 (NSFs).=C2=A0 The I2NSF framework al=
lows heterogeneous NSFs developed by<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 =
different security solution vendors to be used in the Network<br>&gt;=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0 Functions Virtualization (NFV) environment [ETSI-N=
FV] by utilizing<br><br>Much of this document cannot be understood without =
reading ETSI-NFV,<br>so it has to be a normative reference. It also would b=
e helpful to<br>provide a link.<br><br><br>S 2.<br>&gt;=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0 This document uses the terminology described in [RFC7149],<br>=
&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 [ITU-T.Y.3300], [ONF-OpenFlow], [ONF-SDN=
-Architecture],<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 [ITU-T.X.1252], [ITU-=
T.X.800], [RFC8329], [i2nsf-terminology],<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0 [consumer-facing-inf-im], [consumer-facing-inf-dm],<br>&gt;=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0 [i2nsf-nsf-cap-im], [nsf-facing-inf-dm], [registratio=
n-inf-dm], and<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 [nsf-triggered-steerin=
g].=C2=A0 In addition, the following terms are<br><br>Every term in this do=
cument needs to be understandable without<br>reference to closed specificat=
ions or internally defined. Please<br>ensure that this is so,<br><br><br>S =
3.<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 used for the I2NSF NSF-Facing Inte=
rface.<br>&gt;=C2=A0=C2=A0 <br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 The Regis=
tration Interface between the Security Controller and the<br>&gt;=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0 Developer&#39;s Management System can be implemented =
by RESTCONF<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 [RFC8040].=C2=A0 The data=
 model defined in [registration-inf-dm] can be<br>&gt;=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0 used for the I2NSF Registration Interface.<br><br>What role does =
the Developer&#39;s Management System play in this? I think<br>this refers =
to the text above starting with &quot;The developers (or<br>vendors)...&quo=
t;. Is that correct?<br><br>Assuming I am correct, this seems like a potent=
ially serious security<br>vulnerability in this design in that it potential=
ly allows an inside<br>attacker at the developer to seriously weaken a syst=
em&#39;s security.<br>What protections exist to prevent this?<br><br><br>S =
4.<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 administrator wants to control the=
 staff members&#39; access to a<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 parti=
cular Interner service (e.g., Example.com) during business<br>&gt;=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0 hours.=C2=A0 The following is an example high-level s=
ecurity policy rule<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 that the administ=
rator requests: Block the staff members&#39; access to<br>&gt;=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0 Example.com from 9 AM to 6 PM.=C2=A0 The administrator s=
ends this high-<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 level security policy=
 to the Security Controller, then the Security<br><br>The text above sugges=
ts that high-level policies are via<br>RESTCONF/YANG, but this is clearly f=
reeform text.<br>COMMENTS<br>S 1.<br>&gt;=C2=A0=C2=A0 <br>&gt;=C2=A0=C2=A0 =
1.=C2=A0 Introduction<br>&gt;=C2=A0=C2=A0 <br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0 Interface to Network Security Functions (I2NSF) defines a framework<=
br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 and interfaces for interacting with N=
etwork Security Functions<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 (NSFs).=C2=
=A0 The I2NSF framework allows heterogeneous NSFs developed by<br><br>Pleas=
e define &quot;Network Security Functions&quot; here.<br><br><br><br><br>S =
1.<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 functions in the NFV platform.=C2=
=A0 In the I2NSF framework, each NSF<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 =
initially registers the profile of its own capabilities into the<br>&gt;=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0 system in order for themselves to be available =
in the system.=C2=A0 In<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 addition, the=
 Security Controller is validated by the I2NSF Client<br>&gt;=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0 (also called I2NSF User) that the user is employing, so =
that the user<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 can request security se=
rvices through the Security Controller.<br><br>In this case the user is the=
 system administrator.<br><br><br>S 1.<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0 [RFC7149] to provide different security functionality such as<br>&gt;=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 firewalls [opsawg-firewalls], Deep Packet In=
spection (DPI), and<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Distributed Denia=
l of Service (DDoS) attack mitigation; (iv) the use<br>&gt;=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0 of NFV as supporting technology.=C2=A0 The implementation o=
f I2NSF in<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 these scenarios has allowe=
d us to verify the applicability and<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 =
effectiveness of the I2NSF framework for a variety of use cases.<br><br>Thi=
s would be easier to read with a standard bulleted list.<br><br><br>S 2.<br=
>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 network resources, wh=
ich facilitates the design, delivery and<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0 operation of network services in a dynamic and scalab=
le manner<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 [ITU-T.Y.=
3300].<br>&gt;=C2=A0=C2=A0 <br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 o=C2=A0 F=
irewall: A service function at the junction of two network<br>&gt;=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 segments that inspects every packet=
 that attempts to cross the<br><br>Nit: It might not inspect *every* packet=
.<br><br><br>S 4.<br>&gt;=C2=A0=C2=A0 <br>&gt;=C2=A0=C2=A0 4.=C2=A0 Time-de=
pendent Web Access Control Service<br>&gt;=C2=A0=C2=A0 <br>&gt;=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0 This service scenario assumes that an enterprise network=
<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 administrator wants to control the s=
taff members&#39; access to a<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 particu=
lar Interner service (e.g., Example.com) during business<br><br>Nit: &quot;=
Internet&quot;<br><br><br>S 4.<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 inspec=
tion capability is required to check whether the target URL of<br>&gt;=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0 a received packet is in the Example.com domain =
or not.<br>&gt;=C2=A0=C2=A0 <br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 The Secu=
rity Controller maintains the security capabilities of each<br>&gt;=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0 NSF running in the I2NSF system, which have been r=
eported by the<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Developer&#39;s Manage=
ment System via the Registation interface.=C2=A0 Based<br><br>Nit: &quot;Re=
gistration&quot;<br><br><br>S 4.<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 curr=
ently using the network.=C2=A0 Based on the retrieved information, the<br>&=
gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Security Controller generates low-level s=
ecurity rules to check<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 whether the so=
urce IP address of a received packet matches any one<br>&gt;=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0 being used by a staff member.=C2=A0 In addition, the low-le=
vel security<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 rules should be able to =
determine that a received packet is of HTTP<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0 protocol.=C2=A0 The low-level security rules for web filter checks t=
hat<br><br>Nit: &quot;rules&quot;... &quot;checks&quot; disagree.<br><br><b=
r>S 6.<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 translated into their packet f=
orwarding rules, whereas NSFs enforce<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
 NSF-related security rules requiring the security capabilities of the<br>&=
gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 NSFs.=C2=A0 For this purpose, the Securit=
y Controller instructs the SDN<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Contro=
ller via NSF-Facing Interface so that SDN forwarding elements<br>&gt;=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0 can perform the required security services with fl=
ow tables under the<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 supervision of th=
e SDN Controller.<br><br>I&#39;m having some trouble understanding the diff=
erence here between NSFs<br>and SDN elements. They both seem to be software=
 controlled network<br>elements. Is this just some continuum about CPU powe=
r?<br><br><br>S 6.<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 can perform the re=
quired security services with flow tables under the<br>&gt;=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0 supervision of the SDN Controller.<br>&gt;=C2=A0=C2=A0 <br>=
&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 As an example, let us consider two diffe=
rent types of security rules:<br>&gt;=C2=A0=C2=A0 <br>&gt;=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0 Rule A is a simple packet fltering rule that checks only th=
e IP<br><br>Nit: &quot;filtering&quot;<br><br><br>S 6.2.<br>&gt;=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 packets that have the same ca=
ll-id.<br>&gt;=C2=A0=C2=A0 <br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 6.=C2=A0 =
The SDN Controller installs new rules (e.g., drop packets) into<br>&gt;=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 underlying switches.<br=
>&gt;=C2=A0=C2=A0 <br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 7.=C2=A0 The illeg=
al packets are dropped by these switches.<br><br>&quot;Illegal&quot; is pro=
bably the wrong wrod here.<br><br><br>S 6.3.<br>&gt;=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0 is helpful to determine security policies for s=
uch a network.<br>&gt;=C2=A0=C2=A0 <br>&gt;=C2=A0=C2=A0 6.3.=C2=A0 Attack M=
itigation: Centralized DDoS-attack Mitigation System<br>&gt;=C2=A0=C2=A0 <b=
r>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 A centralized DDoS-attack mitigation c=
an manage each network resource<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 and m=
anipulate rules to each switch through a common server for DDoS-<br><br>&qu=
ot;manipulate rules to&quot; is not grammatical.<br><br><br>S 6.3.<br>&gt;=
=C2=A0=C2=A0 <br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Servers are categorized=
 into stateless servers (e.g., DNS servers)<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0 and stateful servers (e.g., web servers).=C2=A0 For DDoS-attack<br>&=
gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 mitigation, traffic flows in switches are=
 dynamically configured by<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 traffic fl=
ow forwarding path management according to the category of<br>&gt;=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0 servers [AVANT-GUARD].=C2=A0 Such a managenent should=
 consider the load<br><br>1. This seems hard to understand without this ref=
erence, which is not<br>public.<br>2. &quot;management&quot;<br><br><br>S 6=
.3.<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 mitigation, traffic flows in swit=
ches are dynamically configured by<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 tr=
affic flow forwarding path management according to the category of<br>&gt;=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 servers [AVANT-GUARD].=C2=A0 Such a managene=
nt should consider the load<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 balance a=
mong the switches for the defense against DDoS attacks.<br>&gt;=C2=A0=C2=A0=
 <br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 The procedure of DDoS-attack mitiga=
tion operations in this system is<br><br>&quot;procedure of... operations&q=
uot; is ungrammatical<br><br></div></div>
</blockquote></div><br clear=3D"all"><div><br></div>-- <br><div dir=3D"ltr"=
 class=3D"gmail-m_-9111533177071645325gmail_signature"><div dir=3D"ltr"><di=
v><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 Softw=
are<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"=
 target=3D"_blank">pauljeong@skku.edu</a><br>Personal Homepage: <a href=3D"=
http://cpslab.skku.edu/people-jaehoon-jeong.php" target=3D"_blank">http://i=
otlab.skku.edu/people-jaehoon-jeong.php</a><br></div></div></div></div></di=
v></div></div></div>
</blockquote></div></div>

--0000000000000e6abe057df139a3--


From nobody Wed Dec 26 18:42:31 2018
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 F0651130E30 for <i2nsf@ietfa.amsl.com>; Wed, 26 Dec 2018 18:42:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.5
X-Spam-Level: 
X-Spam-Status: No, score=-0.5 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HK_NAME_FM_MR_MRS=1.499, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-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 r887xxhlf_Qr for <i2nsf@ietfa.amsl.com>; Wed, 26 Dec 2018 18:42:25 -0800 (PST)
Received: from mail-io1-xd2b.google.com (mail-io1-xd2b.google.com [IPv6:2607:f8b0:4864:20::d2b]) (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 C402C12870E for <i2nsf@ietf.org>; Wed, 26 Dec 2018 18:42:24 -0800 (PST)
Received: by mail-io1-xd2b.google.com with SMTP id s22so13544372ioc.8 for <i2nsf@ietf.org>; Wed, 26 Dec 2018 18:42:24 -0800 (PST)
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=vG1MmHxhYHRsvjpNIEVnjDwqx8JhcwwduabMMogYDN8=; b=RBmzKkrAQGE6JkMdcr95pkjJdJrZn5ex8SBsaXj1B/yn8X4xpnGp7lAXstxkNJ6UkN qziYUhObcPwQN2sJJsktPTkjKmJC/enguQ+Qe6h6UMdmV/9wVmReuGVTOA8CcnyS5b1h QYmXAA6WASD+h/y6fyIBNiTGbuvPyTfLRdGtAAvbo0yHgnRVj5RywFqL/UHCXdn++W3k SmkWgOS52MpztE2O76KtIeOieumqP5NCwSdFwIka1sWRwRRsjNHcCCMuNrBe5pQQNj2P 0DxLSKI6Kb0WbL5p86uinJoEnSzUR92CbdUkPUQzv/OoI77tPxc16idEELgrhDGKJE7X HuOg==
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=vG1MmHxhYHRsvjpNIEVnjDwqx8JhcwwduabMMogYDN8=; b=Rq7Rh5H3PlW9givMoZdwUB5j9m94KhSwqZQsjZZkv+EGPkKOZgBbOMt05pK44a2XW4 cf/9tyQfrcv7HxyrHwWJp4RUfdq5KF3eP8HAFPO+gLS3ikB01qrBALO1vTFE6/6gjara z1Szv5wPcAaaCCFh9v86O8fuxJBlwf4RopGnCg+4TM6ojoJMo4dvEE2G90aub+ppyX+5 D/AJbs+8iCAkPeCEIodWmmTnkwj+mBkcVM73vQE8hreSCzoz5iEBroI80uy9uPQSkGpX U0HeXnye7NvAoAlWlpEScjLM73zuEII/GbCwkvSBF/DBbVDBUXBTdutM/SMI3LHYW4Y4 jlCw==
X-Gm-Message-State: AJcUukdeBjhWpVmoDdQvBCdUi8juDWgoB975Bn3ikhyfzRt/O1Mi2C6W 36kZkcnjYM7teGIkmv6Tr/hQGdZ+LRpw9ogcqwM=
X-Google-Smtp-Source: ALg8bN4X8sk5svnfprN7xfRyEg5lQQ7d8gASnnG0njSJytD4DDMQWuM4wKen6vTN5wDDM6FCdHxNJ+3hdrix3UQ4Dtw=
X-Received: by 2002:a6b:e802:: with SMTP id f2mr14477502ioh.296.1545878543726;  Wed, 26 Dec 2018 18:42:23 -0800 (PST)
MIME-Version: 1.0
References: <CABcZeBOjhEpw4gNDRgJD=FCWy1Wrirz_EsJefJjDHpp5mVe1fw@mail.gmail.com> <CAPK2DewE2vbjAr41xErxnjmxK2CTmK2h9fXFTBSFCigpNj9XPQ@mail.gmail.com> <CABcZeBNZhqTawAFcj9p01ig-tE=XaFm5yCXuGJQFiqoOGgNZxA@mail.gmail.com>
In-Reply-To: <CABcZeBNZhqTawAFcj9p01ig-tE=XaFm5yCXuGJQFiqoOGgNZxA@mail.gmail.com>
From: "Mr. Jaehoon Paul Jeong" <jaehoon.paul@gmail.com>
Date: Thu, 27 Dec 2018 11:42:09 +0900
Message-ID: <CAPK2Dex7hbKC3Cpq2Jy+UXr7YFqgjGUGvzNiSYMix7M5qQhx=w@mail.gmail.com>
To: Eric Rescorla <ekr@rtfm.com>
Cc: Linda Dunbar <linda.dunbar@huawei.com>, Yoav Nir <ynir.ietf@gmail.com>, i2nsf@ietf.org,  skku_secu-brain_all@googlegroups.com, Jaehoon Jeong <jaehoon.paul@gmail.com>
Content-Type: multipart/alternative; boundary="000000000000770089057df7e50c"
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2nsf/PdmaCBZn0dsTX42gYqz_daidlgM>
Subject: Re: [I2nsf] AD Review of draft-ietf-i2nsf-applicability-07
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, 27 Dec 2018 02:42:30 -0000

--000000000000770089057df7e50c
Content-Type: text/plain; charset="UTF-8"

Hi Eric,
Here are my answers inlines below.

On Thu, Dec 27, 2018 at 3:44 AM Eric Rescorla <ekr@rtfm.com> wrote:

> Paul,
>
> Thanks for your new version. Some responses below.
>
>
> On Tue, Dec 25, 2018 at 6:42 AM Mr. Jaehoon Paul Jeong <
> jaehoon.paul@gmail.com> wrote:
>
>> Hi Eric, Linda and Yoav,
>> I have reflected all the comments from Eric and submitted the revision
>> -08 as follows:
>> https://tools.ietf.org/html/draft-ietf-i2nsf-applicability-08
>>
>> The changes are described in Appendix A of -08 document as follows:
>>
>> -------------------------------------------------------------------------------------------------
>> Appendix A.  Changes from draft-ietf-i2nsf-applicability-07
>>
>>    The following changes have been made from
>>    draft-ietf-i2nsf-applicability-07:
>>
>>    o  This version has reflected all the comments from Eric Rescorla who
>>       is a Security Area Director as follows.
>>
>>    o  In Section 1, Network Security Function (NFV) is defined in the
>>       viewpoint of the I2NSF framework.
>>
>>    o  In Section 1, a user using the I2NSF User is clarified as a system
>>       administrator in the I2NSF framework.
>>
>>    o  In Section 1, as the applicability of the I2NSF framework, four
>>       different scenarios are represented with a standard bulleted list.
>>
>>    o  The standard document about ETSI-NFV is moved to Normative
>>       References.
>>
>>    o  In Section 2, key terms (e.g., Network Function, Network Security
>>       Function, Network Functions Virtualization, and Servive Function
>>       Chaining) are internally defined along with the reference to open
>>       specifications.
>>
>>    o  In Section 2, the definition of Firewall is corrected such that
>>       some suspicious packets are inspected by the firewall rather than
>>       every packet.
>>
>>    o  In Section 3, for a Developer's Management System, the problem of
>>       an inside attacker is addressed, and a possible solution for the
>>       inside attacks is suggested through I2NSF NSF monitoring
>>       functionality.
>>
>
> I'm still pretty concerned about this. Standardizing a situation in which
> the
> developer of your firewall has real-time management-level access to
> that firewall seems extremely insecure, especially when that access is
> authenticated via conventional credentials that are online as part of
> the transaction (as opposed to software builds which can be signed
> offline). This doesn't seem like a best practice. Why is it necessary?
>


>  =>  The developer of a firewall does not have real-time management-level
access
       even though its management system works the control plane as part of
the I2NSF system.
       The developer's management system provides the Security Controller
with
       the interface (i.e., Registration Interface) that is used to
register the capability of
       the developer's security network function (i.e., firewall), to
search an NSF for the required capability for a high-level security policy,
and to help the lifecycle management
       of such an NSF for the Security Controller through an NFV interface
(i.e., Ve-Vnfm interface) with the NFV's MANO.
      In our NFV system, it is assumed that the developer's management
system and its
      NSF images are trustworthy as an element management system and
Virtual Network Functions, respectively.


>
>
>    o  In Section 4, an XML file for the RESTCONF/YANG for the time-
>>       dependent web access control is pointed out with a reference to
>>       the Consumer-Facing Interface's data model
>>       [consumer-facing-inf-dm].
>>
>
> I didn't follow this change. The example you give of a high level security
> policy is clearly freeform text and then you talk about XML. Is this just
> example a summary of the semantics of something which would actually be an
> XML file? Something else?
>

  => Even though the high-level security policy looks like a freeform
text,  it is formatted
      in an XML according to the high-level security policy YANG model for
the Consumer-Facing Interface.
      Yes, it is just an example of a summary of the semantics for such a
high-level security policy,
      which is represented as an XML file.
      Here it an XML file for the web filter from the Consumer-Facing
Interface Data Model document
      (
https://tools.ietf.org/html/draft-ietf-i2nsf-consumer-facing-interface-dm-02
):

      You can see the XML file from

https://tools.ietf.org/html/draft-ietf-i2nsf-consumer-facing-interface-dm-02#page-49

      <?xml version="1.1" encoding="UTF-8"?>
 <rpc message-id="4" xmlns="urn:ietf:params:xml:ns:restconf:base:1.0">
  <edit-config>
   <target>
    <running/>
   </target>
    <config>
     <i2nsf-cf-interface-wf-req nc:operation="create">
         <policy-wf>
             <rule-wf>
                 <rule-wf-id>03</rule-wf-id>
                 <rule-wf-name>wf-policy-example</rule-wf-name>
                 <rule-wf-date>2018.10.26/14:03:17</rule-wf-date>
                 <event>
                     <event-id>04</event-id>
                     <event-name>wf</event-name>
                     <event-date>2018.10.26/14:03:17</event-date>
                     <event-type>wf</event-type>
                     <event-map-group>04</event-map-group>
                     <enable>True</enable>
                 </event>
                 <condition>
                     <condition-id>04</condition-id>
                     <source-ip>192.168.1.3</source-ip>
                     <destination-url>www.facebook.com</destination-url>
                     <time-information>
                         <begin-time>09:00</begin-time>
                         <end-time>18:00</end-time>
                     </time-information>
                     <match-direction>default</match-direction>
                     <exeption>00</exeption>
                 </condition>
                 <action>
                     <action-id>04</action-id>
                     <action-name>action-wf</action-name>
                     <action-date>2018.10.26/14:03:17</action-date>
                     <primary-action>REJECT</primary-action>
                     <secondary-action>LOG</secondary-action>
                 </action>
                 <precedence>none</precedence>
               <owner>
                 <owner-id>03</owner-id>
                 <name>i2nsf-admin</name>
               </owner>
             </rule-wf>
         </policy-wf>
     </i2nsf-cf-interface-wf-req>
    </config>
  </edit-config>
 </rpc>
  => In the above, source ip is used for the employees.
  Instead of the source ip, we can make and use "source group" for
employees that can be translated
  into a set of IP addresses of the source group.


>
>
>    o  In Section 6, the definitions of an SDN forwarding element and an
>>       NSF are clarified such that an SDN forwarding element is a switch
>>       running as either a hardware middle box or a software virtual
>>       switch, and an NSF is a virtual network function for a security
>>       service.
>>
>
> This wasn't clear to me either. Based on this text it would seem that
> you could run an NSF on an SDN element, so it's not clear why they
> are disjoint sets. Can you give me more information here?
>

 => An SDN switch can run as a virtual network function like an NSF, but
the main functionality of the SDN switch is packet forwarding with a flow
table along with simple filtering rules. More complicated security services
can be done at dedicated NSFs. For example, there is the Open Virtual
Switch (OVS) project for such a software-based SDN switch:
https://www.openvswitch.org

Thus, the SDN switches and NSFs are logically disjoint sets though all of
them  can run physically as virtual network functions.

If you have further questions, please let me know.

Thanks.

Best Regards,
Paul

>
> -Ekr
>
>
>>    o  In Section 6.3, a flow forwarding path management scheme in
>>       [AVANT-GUARD] is described in a self-contained way as follows.
>>       For DDoS-attack mitigation, the forwarding of traffic flows in
>>       switches can be dynamically configured such that malicious traffic
>>       flows are handled by the paths separated from normal traffic flows
>>       in order to minimize the impact of those malicious traffic on the
>>       the servers.  This flow path separation can be done by a flow
>>       forwarding path management scheme based on [AVANT-GUARD].
>>
>>    o  Some typos are corrected such as "Interner -> Internet",
>>       "Registation -> Registration", "The low-level security rules for
>>       web filter checks -> The low-level security rules for web filter
>>       check", "fltering -> filtering", "illegal packets -> malicious
>>       packets", "manipulate rules -> configure rules", "managenent ->
>>       management", and "DDoS-attack mitigation operations -> DDoS-attack
>>       mitigation".
>>
>> -------------------------------------------------------------------------------------------------
>>
>> Thanks and Merry Christmas!
>>
>> Best Regards,
>> Paul
>>
>> On Fri, Dec 21, 2018 at 11:33 PM Eric Rescorla <ekr@rtfm.com> wrote:
>>
>>> Rich version of this review at:
>>> https://mozphab-ietf.devsvcdev.mozaws.net/D3181
>>>
>>>
>>> I found a number of typographical and grammar errors. Please give this
>>> document a thorough read.
>>>
>>> IMPORTANT
>>> S 1.
>>> >
>>> >      Interface to Network Security Functions (I2NSF) defines a
>>> framework
>>> >      and interfaces for interacting with Network Security Functions
>>> >      (NSFs).  The I2NSF framework allows heterogeneous NSFs developed
>>> by
>>> >      different security solution vendors to be used in the Network
>>> >      Functions Virtualization (NFV) environment [ETSI-NFV] by utilizing
>>>
>>> Much of this document cannot be understood without reading ETSI-NFV,
>>> so it has to be a normative reference. It also would be helpful to
>>> provide a link.
>>>
>>>
>>> S 2.
>>> >      This document uses the terminology described in [RFC7149],
>>> >      [ITU-T.Y.3300], [ONF-OpenFlow], [ONF-SDN-Architecture],
>>> >      [ITU-T.X.1252], [ITU-T.X.800], [RFC8329], [i2nsf-terminology],
>>> >      [consumer-facing-inf-im], [consumer-facing-inf-dm],
>>> >      [i2nsf-nsf-cap-im], [nsf-facing-inf-dm], [registration-inf-dm],
>>> and
>>> >      [nsf-triggered-steering].  In addition, the following terms are
>>>
>>> Every term in this document needs to be understandable without
>>> reference to closed specifications or internally defined. Please
>>> ensure that this is so,
>>>
>>>
>>> S 3.
>>> >      used for the I2NSF NSF-Facing Interface.
>>> >
>>> >      The Registration Interface between the Security Controller and the
>>> >      Developer's Management System can be implemented by RESTCONF
>>> >      [RFC8040].  The data model defined in [registration-inf-dm] can be
>>> >      used for the I2NSF Registration Interface.
>>>
>>> What role does the Developer's Management System play in this? I think
>>> this refers to the text above starting with "The developers (or
>>> vendors)...". Is that correct?
>>>
>>> Assuming I am correct, this seems like a potentially serious security
>>> vulnerability in this design in that it potentially allows an inside
>>> attacker at the developer to seriously weaken a system's security.
>>> What protections exist to prevent this?
>>>
>>>
>>> S 4.
>>> >      administrator wants to control the staff members' access to a
>>> >      particular Interner service (e.g., Example.com) during business
>>> >      hours.  The following is an example high-level security policy
>>> rule
>>> >      that the administrator requests: Block the staff members' access
>>> to
>>> >      Example.com from 9 AM to 6 PM.  The administrator sends this high-
>>> >      level security policy to the Security Controller, then the
>>> Security
>>>
>>> The text above suggests that high-level policies are via
>>> RESTCONF/YANG, but this is clearly freeform text.
>>> COMMENTS
>>> S 1.
>>> >
>>> >   1.  Introduction
>>> >
>>> >      Interface to Network Security Functions (I2NSF) defines a
>>> framework
>>> >      and interfaces for interacting with Network Security Functions
>>> >      (NSFs).  The I2NSF framework allows heterogeneous NSFs developed
>>> by
>>>
>>> Please define "Network Security Functions" here.
>>>
>>>
>>>
>>>
>>> S 1.
>>> >      functions in the NFV platform.  In the I2NSF framework, each NSF
>>> >      initially registers the profile of its own capabilities into the
>>> >      system in order for themselves to be available in the system.  In
>>> >      addition, the Security Controller is validated by the I2NSF Client
>>> >      (also called I2NSF User) that the user is employing, so that the
>>> user
>>> >      can request security services through the Security Controller.
>>>
>>> In this case the user is the system administrator.
>>>
>>>
>>> S 1.
>>> >      [RFC7149] to provide different security functionality such as
>>> >      firewalls [opsawg-firewalls], Deep Packet Inspection (DPI), and
>>> >      Distributed Denial of Service (DDoS) attack mitigation; (iv) the
>>> use
>>> >      of NFV as supporting technology.  The implementation of I2NSF in
>>> >      these scenarios has allowed us to verify the applicability and
>>> >      effectiveness of the I2NSF framework for a variety of use cases.
>>>
>>> This would be easier to read with a standard bulleted list.
>>>
>>>
>>> S 2.
>>> >         network resources, which facilitates the design, delivery and
>>> >         operation of network services in a dynamic and scalable manner
>>> >         [ITU-T.Y.3300].
>>> >
>>> >      o  Firewall: A service function at the junction of two network
>>> >         segments that inspects every packet that attempts to cross the
>>>
>>> Nit: It might not inspect *every* packet.
>>>
>>>
>>> S 4.
>>> >
>>> >   4.  Time-dependent Web Access Control Service
>>> >
>>> >      This service scenario assumes that an enterprise network
>>> >      administrator wants to control the staff members' access to a
>>> >      particular Interner service (e.g., Example.com) during business
>>>
>>> Nit: "Internet"
>>>
>>>
>>> S 4.
>>> >      inspection capability is required to check whether the target URL
>>> of
>>> >      a received packet is in the Example.com domain or not.
>>> >
>>> >      The Security Controller maintains the security capabilities of
>>> each
>>> >      NSF running in the I2NSF system, which have been reported by the
>>> >      Developer's Management System via the Registation interface.
>>> Based
>>>
>>> Nit: "Registration"
>>>
>>>
>>> S 4.
>>> >      currently using the network.  Based on the retrieved information,
>>> the
>>> >      Security Controller generates low-level security rules to check
>>> >      whether the source IP address of a received packet matches any one
>>> >      being used by a staff member.  In addition, the low-level security
>>> >      rules should be able to determine that a received packet is of
>>> HTTP
>>> >      protocol.  The low-level security rules for web filter checks that
>>>
>>> Nit: "rules"... "checks" disagree.
>>>
>>>
>>> S 6.
>>> >      translated into their packet forwarding rules, whereas NSFs
>>> enforce
>>> >      NSF-related security rules requiring the security capabilities of
>>> the
>>> >      NSFs.  For this purpose, the Security Controller instructs the SDN
>>> >      Controller via NSF-Facing Interface so that SDN forwarding
>>> elements
>>> >      can perform the required security services with flow tables under
>>> the
>>> >      supervision of the SDN Controller.
>>>
>>> I'm having some trouble understanding the difference here between NSFs
>>> and SDN elements. They both seem to be software controlled network
>>> elements. Is this just some continuum about CPU power?
>>>
>>>
>>> S 6.
>>> >      can perform the required security services with flow tables under
>>> the
>>> >      supervision of the SDN Controller.
>>> >
>>> >      As an example, let us consider two different types of security
>>> rules:
>>> >
>>> >      Rule A is a simple packet fltering rule that checks only the IP
>>>
>>> Nit: "filtering"
>>>
>>>
>>> S 6.2.
>>> >          packets that have the same call-id.
>>> >
>>> >      6.  The SDN Controller installs new rules (e.g., drop packets)
>>> into
>>> >          underlying switches.
>>> >
>>> >      7.  The illegal packets are dropped by these switches.
>>>
>>> "Illegal" is probably the wrong wrod here.
>>>
>>>
>>> S 6.3.
>>> >         is helpful to determine security policies for such a network.
>>> >
>>> >   6.3.  Attack Mitigation: Centralized DDoS-attack Mitigation System
>>> >
>>> >      A centralized DDoS-attack mitigation can manage each network
>>> resource
>>> >      and manipulate rules to each switch through a common server for
>>> DDoS-
>>>
>>> "manipulate rules to" is not grammatical.
>>>
>>>
>>> S 6.3.
>>> >
>>> >      Servers are categorized into stateless servers (e.g., DNS servers)
>>> >      and stateful servers (e.g., web servers).  For DDoS-attack
>>> >      mitigation, traffic flows in switches are dynamically configured
>>> by
>>> >      traffic flow forwarding path management according to the category
>>> of
>>> >      servers [AVANT-GUARD].  Such a managenent should consider the load
>>>
>>> 1. This seems hard to understand without this reference, which is not
>>> public.
>>> 2. "management"
>>>
>>>
>>> S 6.3.
>>> >      mitigation, traffic flows in switches are dynamically configured
>>> by
>>> >      traffic flow forwarding path management according to the category
>>> of
>>> >      servers [AVANT-GUARD].  Such a managenent should consider the load
>>> >      balance among the switches for the defense against DDoS attacks.
>>> >
>>> >      The procedure of DDoS-attack mitigation operations in this system
>>> is
>>>
>>> "procedure of... operations" is ungrammatical
>>>
>>>
>>
>> --
>> ===========================
>> Mr. Jaehoon (Paul) Jeong, Ph.D.
>> Associate Professor
>> Department of Software
>> Sungkyunkwan University
>> Office: +82-31-299-4957
>> Email: jaehoon.paul@gmail.com
>> 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 Software
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>

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

<div dir=3D"auto"><div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr"><div d=
ir=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr"><div>Hi Eric,</div><div dir=3D=
"auto">Here are my answers inlines below.</div><br><div class=3D"gmail_quot=
e"><div dir=3D"ltr">On Thu, Dec 27, 2018 at 3:44 AM Eric Rescorla &lt;<a hr=
ef=3D"mailto:ekr@rtfm.com" target=3D"_blank" rel=3D"noreferrer">ekr@rtfm.co=
m</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"><div>Paul,</div><div><br></div><div>Than=
ks for your new version. Some responses below.<br></div><div><br></div></di=
v><br><div class=3D"gmail_quote"><div dir=3D"ltr">On Tue, Dec 25, 2018 at 6=
:42 AM 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:=
<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8=
ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr=
"><div dir=3D"ltr"><div dir=3D"ltr">Hi Eric, Linda and Yoav,<div>I have ref=
lected all the comments from Eric and submitted the revision -08 as follows=
:</div><div><a href=3D"https://tools.ietf.org/html/draft-ietf-i2nsf-applica=
bility-08" target=3D"_blank" rel=3D"noreferrer">https://tools.ietf.org/html=
/draft-ietf-i2nsf-applicability-08</a><br></div><div><br></div><div>The cha=
nges are described in Appendix A of -08 document as follows:</div><div>----=
---------------------------------------------------------------------------=
------------------</div><div><div>Appendix A.=C2=A0 Changes from draft-ietf=
-i2nsf-applicability-07</div><div><br></div><div>=C2=A0 =C2=A0The following=
 changes have been made from</div><div>=C2=A0 =C2=A0draft-ietf-i2nsf-applic=
ability-07:</div><div><br></div><div>=C2=A0 =C2=A0o=C2=A0 This version has =
reflected all the comments from Eric Rescorla who</div><div>=C2=A0 =C2=A0 =
=C2=A0 is a Security Area Director as follows.</div><div><br></div><div>=C2=
=A0 =C2=A0o=C2=A0 In Section 1, Network Security Function (NFV) is defined =
in the</div><div>=C2=A0 =C2=A0 =C2=A0 viewpoint of the I2NSF framework.</di=
v><div><br></div><div>=C2=A0 =C2=A0o=C2=A0 In Section 1, a user using the I=
2NSF User is clarified as a system</div><div>=C2=A0 =C2=A0 =C2=A0 administr=
ator in the I2NSF framework.</div><div><br></div><div>=C2=A0 =C2=A0o=C2=A0 =
In Section 1, as the applicability of the I2NSF framework, four</div><div>=
=C2=A0 =C2=A0 =C2=A0 different scenarios are represented with a standard bu=
lleted list.</div><div><br></div><div>=C2=A0 =C2=A0o=C2=A0 The standard doc=
ument about ETSI-NFV is moved to Normative</div><div>=C2=A0 =C2=A0 =C2=A0 R=
eferences.</div><div><br></div><div>=C2=A0 =C2=A0o=C2=A0 In Section 2, key =
terms (e.g., Network Function, Network Security</div><div>=C2=A0 =C2=A0 =C2=
=A0 Function, Network Functions Virtualization, and Servive Function</div><=
div>=C2=A0 =C2=A0 =C2=A0 Chaining) are internally defined along with the re=
ference to open</div><div>=C2=A0 =C2=A0 =C2=A0 specifications.</div><div><b=
r></div><div>=C2=A0 =C2=A0o=C2=A0 In Section 2, the definition of Firewall =
is corrected such that</div><div>=C2=A0 =C2=A0 =C2=A0 some suspicious packe=
ts are inspected by the firewall rather than</div><div>=C2=A0 =C2=A0 =C2=A0=
 every packet.</div><div><br></div><div>=C2=A0 =C2=A0o=C2=A0 In Section 3, =
for a Developer&#39;s Management System, the problem of</div><div>=C2=A0 =
=C2=A0 =C2=A0 an inside attacker is addressed, and a possible solution for =
the</div><div>=C2=A0 =C2=A0 =C2=A0 inside attacks is suggested through I2NS=
F NSF monitoring</div><div>=C2=A0 =C2=A0 =C2=A0 functionality.</div></div><=
/div></div></div></blockquote><div><br></div><div>I&#39;m still pretty conc=
erned about this. Standardizing a situation in which the</div><div>develope=
r of your firewall has real-time management-level access to</div><div>that =
firewall seems extremely insecure, especially when that access is</div><div=
>authenticated via conventional credentials that are online as part of</div=
><div>the transaction (as opposed to software builds which can be signed</d=
iv><div>offline). This doesn&#39;t seem like a best practice. Why is it nec=
essary?</div><div></div></div></div></blockquote></div></div></div></div></=
div></div></div><div dir=3D"auto"><br></div><div dir=3D"ltr"><div dir=3D"lt=
r"><div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr"><div=
 class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margin:0p=
x 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><d=
iv dir=3D"ltr"><div class=3D"gmail_quote"><div><br></div></div></div></bloc=
kquote><div>=C2=A0=3D&gt;=C2=A0 The developer of a firewall does not have r=
eal-time management-level access</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0even =
though its management system works the control plane as part of the I2NSF s=
ystem.</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0The developer&#39;s management =
system provides the Security Controller with</div><div>=C2=A0 =C2=A0 =C2=A0=
 =C2=A0the interface (i.e., Registration Interface) that is used to registe=
r the capability of</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0the developer&#39;=
s security network function (i.e., firewall), to search an NSF for the requ=
ired capability for a high-level security policy, and to help the lifecycle=
 management</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0of such an NSF for the Sec=
urity Controller through an NFV interface (i.e., Ve-Vnfm interface) with th=
e NFV&#39;s MANO.=C2=A0</div><div>=C2=A0 =C2=A0 =C2=A0 In our NFV system, i=
t is assumed that the developer&#39;s management system and its</div><div>=
=C2=A0 =C2=A0 =C2=A0 NSF images are trustworthy as an element management sy=
stem and Virtual Network Functions, respectively.</div><div>=C2=A0<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 cl=
ass=3D"gmail_quote"><div></div><div><br></div><div><br></div><blockquote cl=
ass=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"><div =
dir=3D"ltr"><div><div>=C2=A0 =C2=A0o=C2=A0 In Section 4, an XML file for th=
e RESTCONF/YANG for the time-</div><div>=C2=A0 =C2=A0 =C2=A0 dependent web =
access control is pointed out with a reference to</div><div>=C2=A0 =C2=A0 =
=C2=A0 the Consumer-Facing Interface&#39;s data model</div><div>=C2=A0 =C2=
=A0 =C2=A0 [consumer-facing-inf-dm].</div></div></div></div></div></blockqu=
ote><div><br></div><div>I didn&#39;t follow this change. The example you gi=
ve of a high level security</div><div>policy is clearly freeform text and t=
hen you talk about XML. Is this just</div><div>example a summary of the sem=
antics of something which would actually be an</div><div>XML file? Somethin=
g else?</div></div></div></blockquote><div>=C2=A0</div><div dir=3D"auto">=
=C2=A0 =3D&gt; Even though the high-level security policy looks like a free=
form text,=C2=A0 it is formatted</div><div>=C2=A0 =C2=A0 =C2=A0 in an XML a=
ccording to the high-level security policy YANG model for the Consumer-Faci=
ng Interface.</div><div>=C2=A0 =C2=A0 =C2=A0 Yes, it is just an example of =
a summary of the semantics for such a high-level security policy,=C2=A0</di=
v><div>=C2=A0 =C2=A0 =C2=A0 which is represented as an XML file.</div><div>=
=C2=A0 =C2=A0 =C2=A0 Here it an XML file for the web filter from the Consum=
er-Facing Interface Data Model document</div><div>=C2=A0 =C2=A0 =C2=A0 (<a =
href=3D"https://tools.ietf.org/html/draft-ietf-i2nsf-consumer-facing-interf=
ace-dm-02" target=3D"_blank" rel=3D"noreferrer">https://tools.ietf.org/html=
/draft-ietf-i2nsf-consumer-facing-interface-dm-02</a>):</div><div><br></div=
><div>=C2=A0 =C2=A0 =C2=A0 You can see the XML file from=C2=A0</div><div>=
=C2=A0 =C2=A0 =C2=A0 =C2=A0<a href=3D"https://tools.ietf.org/html/draft-iet=
f-i2nsf-consumer-facing-interface-dm-02#page-49" target=3D"_blank" rel=3D"n=
oreferrer">https://tools.ietf.org/html/draft-ietf-i2nsf-consumer-facing-int=
erface-dm-02#page-49</a></div><div><br></div><div>=C2=A0 =C2=A0 =C2=A0 &lt;=
?xml version=3D&quot;1.1&quot; encoding=3D&quot;UTF-8&quot;?&gt;</div><div>=
=C2=A0&lt;rpc message-id=3D&quot;4&quot; xmlns=3D&quot;urn:ietf:params:xml:=
ns:restconf:base:1.0&quot;&gt;</div><div>=C2=A0 &lt;edit-config&gt;</div><d=
iv>=C2=A0 =C2=A0&lt;target&gt;</div><div>=C2=A0 =C2=A0 &lt;running/&gt;</di=
v><div>=C2=A0 =C2=A0&lt;/target&gt;</div><div>=C2=A0 =C2=A0 &lt;config&gt;<=
/div><div>=C2=A0 =C2=A0 =C2=A0&lt;i2nsf-cf-interface-wf-req nc:operation=3D=
&quot;create&quot;&gt;</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&lt;poli=
cy-wf&gt;</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&lt;rul=
e-wf&gt;</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0&lt;rule-wf-id&gt;03&lt;/rule-wf-id&gt;</div><div>=C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&lt;rule-wf-name&gt;wf-policy-=
example&lt;/rule-wf-name&gt;</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0&lt;rule-wf-date&gt;2018.10.26/14:03:17&lt;/rule=
-wf-date&gt;</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0&lt;event&gt;</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0=
 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&lt;event-id&gt;04&lt;/event-id&gt;</div=
><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0=
 =C2=A0&lt;event-name&gt;wf&lt;/event-name&gt;</div><div>=C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&lt;event-date&g=
t;2018.10.26/14:03:17&lt;/event-date&gt;</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&lt;event-type&gt;wf&lt=
;/event-type&gt;</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0=
 =C2=A0 =C2=A0 =C2=A0 =C2=A0&lt;event-map-group&gt;04&lt;/event-map-group&g=
t;</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0=
 =C2=A0 =C2=A0&lt;enable&gt;True&lt;/enable&gt;</div><div>=C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&lt;/event&gt;</div><div>=C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&lt;condition&gt=
;</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0&lt;condition-id&gt;04&lt;/condition-id&gt;</div><div>=C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&lt;so=
urce-ip&gt;192.168.1.3&lt;/source-ip&gt;</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&lt;destination-url&gt;=
<a href=3D"http://www.facebook.com" target=3D"_blank" rel=3D"noreferrer">ww=
w.facebook.com</a>&lt;/destination-url&gt;</div><div>=C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&lt;time-information=
&gt;</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&lt;begin-time&gt;09:00&lt;/begin-time&gt;</=
div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0&lt;end-time&gt;18:00&lt;/end-time&gt;</div><div>=
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0&lt;/time-information&gt;</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&lt;match-direction&gt;default&lt;=
/match-direction&gt;</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&lt;exeption&gt;00&lt;/exeption&gt;</div>=
<div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&lt;/con=
dition&gt;</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0&lt;action&gt;</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&lt;action-id&gt;04&lt;/action-id&gt;=
</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0&lt;action-name&gt;action-wf&lt;/action-name&gt;</div><div>=C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&l=
t;action-date&gt;2018.10.26/14:03:17&lt;/action-date&gt;</div><div>=C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&lt;pr=
imary-action&gt;REJECT&lt;/primary-action&gt;</div><div>=C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&lt;secondary-ac=
tion&gt;LOG&lt;/secondary-action&gt;</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&lt;/action&gt;</div><div>=C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&lt;precedence&gt;none&lt;/=
precedence&gt;</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0&lt;owner&gt;</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0&lt;owner-id&gt;03&lt;/owner-id&gt;</div><div>=C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&lt;name&gt;i2nsf-admin=
&lt;/name&gt;</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0&lt;/owner&gt;</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0&lt;/rule-wf&gt;</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&lt;/pol=
icy-wf&gt;</div><div>=C2=A0 =C2=A0 =C2=A0&lt;/i2nsf-cf-interface-wf-req&gt;=
</div><div>=C2=A0 =C2=A0 &lt;/config&gt;</div><div>=C2=A0 &lt;/edit-config&=
gt;</div><div>=C2=A0&lt;/rpc&gt;</div><div>=C2=A0 =3D&gt;<span style=3D"whi=
te-space:pre-wrap">	</span>In the above, source ip is used for the employee=
s.<br></div><div><div><span style=3D"white-space:pre-wrap">=C2=A0 </span>In=
stead of the source ip, we can make and use &quot;source group&quot; for em=
ployees that can be translated=C2=A0</div><div dir=3D"auto">=C2=A0 into a s=
et of IP addresses of the source group.</div></div><div dir=3D"auto"><br></=
div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;bor=
der-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr"><div=
 class=3D"gmail_quote"><div><br></div><div><br></div><div><br></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 dir=3D"ltr=
"><div dir=3D"ltr"><div><div>=C2=A0 =C2=A0o=C2=A0 In Section 6, the definit=
ions of an SDN forwarding element and an</div><div>=C2=A0 =C2=A0 =C2=A0 NSF=
 are clarified such that an SDN forwarding element is a switch</div><div>=
=C2=A0 =C2=A0 =C2=A0 running as either a hardware middle box or a software =
virtual</div><div>=C2=A0 =C2=A0 =C2=A0 switch, and an NSF is a virtual netw=
ork function for a security</div><div>=C2=A0 =C2=A0 =C2=A0 service.</div></=
div></div></div></div></blockquote><div><br></div><div>This wasn&#39;t clea=
r to me either. Based on this text it would seem that</div><div>you could r=
un an NSF on an SDN element, so it&#39;s not clear why they</div><div>are d=
isjoint sets. Can you give me more information here?<br></div></div></div><=
/blockquote></div></div></div></div></div></div></div><div dir=3D"auto"><br=
></div><div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr">=
<div dir=3D"ltr"><div dir=3D"ltr"><div class=3D"gmail_quote"><blockquote cl=
ass=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 class=3D"gmail_qu=
ote"><div></div></div></div></blockquote></div></div></div></div></div></di=
v></div><div dir=3D"auto">=C2=A0=3D&gt; An SDN switch can run as a virtual =
network function like an NSF, but the main functionality of the SDN switch =
is packet forwarding with a flow table along with simple filtering rules. M=
ore complicated security services can be done at dedicated NSFs. For exampl=
e, there is the Open Virtual Switch (OVS) project for such a software-based=
 SDN switch:=C2=A0<a href=3D"https://www.openvswitch.org">https://www.openv=
switch.org</a></div><div dir=3D"auto"><br></div><div dir=3D"auto">Thus, the=
 SDN switches and NSFs are logically disjoint sets though all of them=C2=A0=
 can run physically as virtual network functions.</div><div dir=3D"auto"><b=
r></div><div dir=3D"auto">If you have further questions, please let me know=
.</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"ltr"><div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"lt=
r"><div dir=3D"ltr"><div dir=3D"ltr"><div class=3D"gmail_quote"><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"><div dir=3D"ltr"><div class=3D"gmail=
_quote"><div></div><div><br></div><div>-Ekr</div><div><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"><div dir=3D"ltr"><div dir=3D"ltr"><d=
iv dir=3D"ltr"><div><div><br></div><div>=C2=A0 =C2=A0o=C2=A0 In Section 6.3=
, a flow forwarding path management scheme in</div><div>=C2=A0 =C2=A0 =C2=
=A0 [AVANT-GUARD] is described in a self-contained way as follows.</div><di=
v>=C2=A0 =C2=A0 =C2=A0 For DDoS-attack mitigation, the forwarding of traffi=
c flows in</div><div>=C2=A0 =C2=A0 =C2=A0 switches can be dynamically confi=
gured such that malicious traffic</div><div>=C2=A0 =C2=A0 =C2=A0 flows are =
handled by the paths separated from normal traffic flows</div><div>=C2=A0 =
=C2=A0 =C2=A0 in order to minimize the impact of those malicious traffic on=
 the</div><div>=C2=A0 =C2=A0 =C2=A0 the servers.=C2=A0 This flow path separ=
ation can be done by a flow</div><div>=C2=A0 =C2=A0 =C2=A0 forwarding path =
management scheme based on [AVANT-GUARD].</div><div><br></div><div>=C2=A0 =
=C2=A0o=C2=A0 Some typos are corrected such as &quot;Interner -&gt; Interne=
t&quot;,</div><div>=C2=A0 =C2=A0 =C2=A0 &quot;Registation -&gt; Registratio=
n&quot;, &quot;The low-level security rules for</div><div>=C2=A0 =C2=A0 =C2=
=A0 web filter checks -&gt; The low-level security rules for web filter</di=
v><div>=C2=A0 =C2=A0 =C2=A0 check&quot;, &quot;fltering -&gt; filtering&quo=
t;, &quot;illegal packets -&gt; malicious</div><div>=C2=A0 =C2=A0 =C2=A0 pa=
ckets&quot;, &quot;manipulate rules -&gt; configure rules&quot;, &quot;mana=
genent -&gt;</div><div>=C2=A0 =C2=A0 =C2=A0 management&quot;, and &quot;DDo=
S-attack mitigation operations -&gt; DDoS-attack</div><div>=C2=A0 =C2=A0 =
=C2=A0 mitigation&quot;.</div></div><div>----------------------------------=
---------------------------------------------------------------=C2=A0</div>=
<div>=C2=A0<br></div><div>Thanks and Merry Christmas!</div><div><br></div><=
div>Best Regards,</div><div>Paul</div></div></div></div><br><div class=3D"g=
mail_quote"><div dir=3D"ltr">On Fri, Dec 21, 2018 at 11:33 PM Eric Rescorla=
 &lt;<a href=3D"mailto:ekr@rtfm.com" target=3D"_blank" rel=3D"noreferrer">e=
kr@rtfm.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">Rich version of this review at=
:<br><a href=3D"https://mozphab-ietf.devsvcdev.mozaws.net/D3181" target=3D"=
_blank" rel=3D"noreferrer">https://mozphab-ietf.devsvcdev.mozaws.net/D3181<=
/a><br><br><br>I found a number of typographical and grammar errors. Please=
 give this<br>document a thorough read.<br><br>IMPORTANT<br>S 1.<br>&gt;=C2=
=A0=C2=A0 <br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Interface to Network Secur=
ity Functions (I2NSF) defines a framework<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0 and interfaces for interacting with Network Security Functions<br>&g=
t;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 (NSFs).=C2=A0 The I2NSF framework allows h=
eterogeneous NSFs developed by<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 differ=
ent security solution vendors to be used in the Network<br>&gt;=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0 Functions Virtualization (NFV) environment [ETSI-NFV] by=
 utilizing<br><br>Much of this document cannot be understood without readin=
g ETSI-NFV,<br>so it has to be a normative reference. It also would be help=
ful to<br>provide a link.<br><br><br>S 2.<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0 This document uses the terminology described in [RFC7149],<br>&gt;=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 [ITU-T.Y.3300], [ONF-OpenFlow], [ONF-SDN-Arc=
hitecture],<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 [ITU-T.X.1252], [ITU-T.X.=
800], [RFC8329], [i2nsf-terminology],<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
 [consumer-facing-inf-im], [consumer-facing-inf-dm],<br>&gt;=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0 [i2nsf-nsf-cap-im], [nsf-facing-inf-dm], [registration-inf-=
dm], and<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 [nsf-triggered-steering].=C2=
=A0 In addition, the following terms are<br><br>Every term in this document=
 needs to be understandable without<br>reference to closed specifications o=
r internally defined. Please<br>ensure that this is so,<br><br><br>S 3.<br>=
&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 used for the I2NSF NSF-Facing Interface.=
<br>&gt;=C2=A0=C2=A0 <br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 The Registratio=
n Interface between the Security Controller and the<br>&gt;=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0 Developer&#39;s Management System can be implemented by RES=
TCONF<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 [RFC8040].=C2=A0 The data model=
 defined in [registration-inf-dm] can be<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0 used for the I2NSF Registration Interface.<br><br>What role does the De=
veloper&#39;s Management System play in this? I think<br>this refers to the=
 text above starting with &quot;The developers (or<br>vendors)...&quot;. Is=
 that correct?<br><br>Assuming I am correct, this seems like a potentially =
serious security<br>vulnerability in this design in that it potentially all=
ows an inside<br>attacker at the developer to seriously weaken a system&#39=
;s security.<br>What protections exist to prevent this?<br><br><br>S 4.<br>=
&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 administrator wants to control the staff=
 members&#39; access to a<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 particular =
Interner service (e.g., Example.com) during business<br>&gt;=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0 hours.=C2=A0 The following is an example high-level securit=
y policy rule<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 that the administrator =
requests: Block the staff members&#39; access to<br>&gt;=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0 Example.com from 9 AM to 6 PM.=C2=A0 The administrator sends t=
his high-<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 level security policy to th=
e Security Controller, then the Security<br><br>The text above suggests tha=
t high-level policies are via<br>RESTCONF/YANG, but this is clearly freefor=
m text.<br>COMMENTS<br>S 1.<br>&gt;=C2=A0=C2=A0 <br>&gt;=C2=A0=C2=A0 1.=C2=
=A0 Introduction<br>&gt;=C2=A0=C2=A0 <br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
 Interface to Network Security Functions (I2NSF) defines a framework<br>&gt=
;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 and interfaces for interacting with Network=
 Security Functions<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 (NSFs).=C2=A0 The=
 I2NSF framework allows heterogeneous NSFs developed by<br><br>Please defin=
e &quot;Network Security Functions&quot; here.<br><br><br><br><br>S 1.<br>&=
gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 functions in the NFV platform.=C2=A0 In t=
he I2NSF framework, each NSF<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 initiall=
y registers the profile of its own capabilities into the<br>&gt;=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0 system in order for themselves to be available in the=
 system.=C2=A0 In<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 addition, the Secur=
ity Controller is validated by the I2NSF Client<br>&gt;=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0 (also called I2NSF User) that the user is employing, so that t=
he user<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 can request security services=
 through the Security Controller.<br><br>In this case the user is the syste=
m administrator.<br><br><br>S 1.<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 [RFC=
7149] to provide different security functionality such as<br>&gt;=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0 firewalls [opsawg-firewalls], Deep Packet Inspection =
(DPI), and<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Distributed Denial of Serv=
ice (DDoS) attack mitigation; (iv) the use<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0 of NFV as supporting technology.=C2=A0 The implementation of I2NSF i=
n<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 these scenarios has allowed us to v=
erify the applicability and<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 effective=
ness of the I2NSF framework for a variety of use cases.<br><br>This would b=
e easier to read with a standard bulleted list.<br><br><br>S 2.<br>&gt;=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 network resources, which faci=
litates the design, delivery and<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0 operation of network services in a dynamic and scalable man=
ner<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 [ITU-T.Y.3300].=
<br>&gt;=C2=A0=C2=A0 <br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 o=C2=A0 Firewal=
l: A service function at the junction of two network<br>&gt;=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 segments that inspects every packet that =
attempts to cross the<br><br>Nit: It might not inspect *every* packet.<br><=
br><br>S 4.<br>&gt;=C2=A0=C2=A0 <br>&gt;=C2=A0=C2=A0 4.=C2=A0 Time-dependen=
t Web Access Control Service<br>&gt;=C2=A0=C2=A0 <br>&gt;=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0 This service scenario assumes that an enterprise network<br>&g=
t;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 administrator wants to control the staff m=
embers&#39; access to a<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 particular In=
terner service (e.g., Example.com) during business<br><br>Nit: &quot;Intern=
et&quot;<br><br><br>S 4.<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 inspection c=
apability is required to check whether the target URL of<br>&gt;=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0 a received packet is in the Example.com domain or not=
.<br>&gt;=C2=A0=C2=A0 <br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 The Security C=
ontroller maintains the security capabilities of each<br>&gt;=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0 NSF running in the I2NSF system, which have been reporte=
d by the<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Developer&#39;s Management S=
ystem via the Registation interface.=C2=A0 Based<br><br>Nit: &quot;Registra=
tion&quot;<br><br><br>S 4.<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 currently =
using the network.=C2=A0 Based on the retrieved information, the<br>&gt;=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0 Security Controller generates low-level securit=
y rules to check<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 whether the source I=
P address of a received packet matches any one<br>&gt;=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0 being used by a staff member.=C2=A0 In addition, the low-level se=
curity<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 rules should be able to determ=
ine that a received packet is of HTTP<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
 protocol.=C2=A0 The low-level security rules for web filter checks that<br=
><br>Nit: &quot;rules&quot;... &quot;checks&quot; disagree.<br><br><br>S 6.=
<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 translated into their packet forward=
ing rules, whereas NSFs enforce<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 NSF-r=
elated security rules requiring the security capabilities of the<br>&gt;=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0 NSFs.=C2=A0 For this purpose, the Security Cont=
roller instructs the SDN<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Controller v=
ia NSF-Facing Interface so that SDN forwarding elements<br>&gt;=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0 can perform the required security services with flow tab=
les under the<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 supervision of the SDN =
Controller.<br><br>I&#39;m having some trouble understanding the difference=
 here between NSFs<br>and SDN elements. They both seem to be software contr=
olled network<br>elements. Is this just some continuum about CPU power?<br>=
<br><br>S 6.<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 can perform the required=
 security services with flow tables under the<br>&gt;=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0 supervision of the SDN Controller.<br>&gt;=C2=A0=C2=A0 <br>&gt;=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 As an example, let us consider two different=
 types of security rules:<br>&gt;=C2=A0=C2=A0 <br>&gt;=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0 Rule A is a simple packet fltering rule that checks only the IP<b=
r><br>Nit: &quot;filtering&quot;<br><br><br>S 6.2.<br>&gt;=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 packets that have the same call-id.=
<br>&gt;=C2=A0=C2=A0 <br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 6.=C2=A0 The SD=
N Controller installs new rules (e.g., drop packets) into<br>&gt;=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 underlying switches.<br>&gt;=
=C2=A0=C2=A0 <br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 7.=C2=A0 The illegal pa=
ckets are dropped by these switches.<br><br>&quot;Illegal&quot; is probably=
 the wrong wrod here.<br><br><br>S 6.3.<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0 is helpful to determine security policies for such a =
network.<br>&gt;=C2=A0=C2=A0 <br>&gt;=C2=A0=C2=A0 6.3.=C2=A0 Attack Mitigat=
ion: Centralized DDoS-attack Mitigation System<br>&gt;=C2=A0=C2=A0 <br>&gt;=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 A centralized DDoS-attack mitigation can man=
age each network resource<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 and manipul=
ate rules to each switch through a common server for DDoS-<br><br>&quot;man=
ipulate rules to&quot; is not grammatical.<br><br><br>S 6.3.<br>&gt;=C2=A0=
=C2=A0 <br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Servers are categorized into =
stateless servers (e.g., DNS servers)<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
 and stateful servers (e.g., web servers).=C2=A0 For DDoS-attack<br>&gt;=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0 mitigation, traffic flows in switches are dynam=
ically configured by<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 traffic flow for=
warding path management according to the category of<br>&gt;=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0 servers [AVANT-GUARD].=C2=A0 Such a managenent should consi=
der the load<br><br>1. This seems hard to understand without this reference=
, which is not<br>public.<br>2. &quot;management&quot;<br><br><br>S 6.3.<br=
>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 mitigation, traffic flows in switches a=
re dynamically configured by<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 traffic =
flow forwarding path management according to the category of<br>&gt;=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0 servers [AVANT-GUARD].=C2=A0 Such a managenent sho=
uld consider the load<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 balance among t=
he switches for the defense against DDoS attacks.<br>&gt;=C2=A0=C2=A0 <br>&=
gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 The procedure of DDoS-attack mitigation o=
perations in this system is<br><br>&quot;procedure of... operations&quot; i=
s ungrammatical<br><br></div></div>
</blockquote></div><br clear=3D"all"><div><br></div>-- <br><div dir=3D"ltr"=
 class=3D"m_-6695152896369925623gmail-m_-607987677208405722gmail-m_-9111533=
177071645325gmail_signature"><div dir=3D"ltr"><div><div dir=3D"ltr"><div><d=
iv 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 Software<br>Sungkyunkwan Univ=
ersity<br>Office: +82-31-299-4957<br>Email: <a href=3D"mailto:jaehoon.paul@=
gmail.com" target=3D"_blank" rel=3D"noreferrer">jaehoon.paul@gmail.com</a><=
br>Personal Homepage: <a href=3D"http://cpslab.skku.edu/people-jaehoon-jeon=
g.php" target=3D"_blank" rel=3D"noreferrer">http://iotlab.skku.edu/people-j=
aehoon-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"m_-6695152896369925623gmail_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. Jaeh=
oon (Paul) Jeong, Ph.D.<br>Associate Professor<br>Department of Software<br=
>Sungkyunkwan University<br>Office: +82-31-299-4957<br>Email: <a href=3D"ma=
ilto:jaehoon.paul@gmail.com" target=3D"_blank" rel=3D"noreferrer">jaehoon.p=
aul@gmail.com</a>,=C2=A0<a href=3D"mailto:pauljeong@skku.edu" style=3D"font=
-size:12.8px" target=3D"_blank" rel=3D"noreferrer">pauljeong@skku.edu</a><b=
r>Personal Homepage: <a href=3D"http://cpslab.skku.edu/people-jaehoon-jeong=
.php" target=3D"_blank" rel=3D"noreferrer">http://iotlab.skku.edu/people-ja=
ehoon-jeong.php</a><br></div></div></div></div></div></div></div></div></di=
v></div></div></div></div></div></div>

--000000000000770089057df7e50c--


From nobody Thu Dec 27 07:00:07 2018
Return-Path: <ekr@rtfm.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 501A612426A for <i2nsf@ietfa.amsl.com>; Thu, 27 Dec 2018 07:00:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=rtfm-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 D5MTuHghQ9uf for <i2nsf@ietfa.amsl.com>; Thu, 27 Dec 2018 06:59:59 -0800 (PST)
Received: from mail-lf1-x12f.google.com (mail-lf1-x12f.google.com [IPv6:2a00:1450:4864:20::12f]) (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 90C78126DBF for <i2nsf@ietf.org>; Thu, 27 Dec 2018 06:59:58 -0800 (PST)
Received: by mail-lf1-x12f.google.com with SMTP id f23so12816352lfc.13 for <i2nsf@ietf.org>; Thu, 27 Dec 2018 06:59:58 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rtfm-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=7Pc81sk0lBxA+NXOFyuTzSTgHBOZlhxk3v+NuyJmRT8=; b=N4pBjpa6a0IqBcjNizJ5wDY7XjjX6p0O3xrCUFqTulbPSbVyt/JKEWaEXZBNWUC0Nk ZeRYuFHSYCJQu6qp3N8Env5WoQxli3C/mJurWHBQrPAmygd4jwSa3NDsKNba1BXg5ING Mf0tbkCio1Lqb4Pq+eo3HFgxVp7eRPZPt9cWqjBHHHmHP3+ciw2H+v7fQvvcdPcOv9jl nuBK1zojcO5GEgLyV3D7ndR+Ac+dsJOExmNuK6jvNGTHDh6iO3NBiQltn9sUJjmtACfv 8N/b1FD82tGdgflSJjIDZQUkCHb8Rbc9uV/hjADqpJSI2jeSwaktWRZ3GGBCwLo5A9gt 1QxQ==
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=7Pc81sk0lBxA+NXOFyuTzSTgHBOZlhxk3v+NuyJmRT8=; b=uaEjaZraf+ctulFNq2oJuTVW8adUHJ288GNlP/nEfEtcGMi99pBUSvpDQElKya+y7Q jkPBahHZg6bp7e2Npm+y0viMof05ijPkDWwv/q7BMYoneGqIudHzxckyaTkjY9UUb/Ej hC4XAlsdNRBXOAL5+sbYIEd4MGsriKnPv8QWEVSPQLf0eWGf6vUMulqHzlX8xx5v0Ciq xFkBsnjkZbg93VhhxCw8vxj5XlRgD+6dLP4Nrcwl/RWo0Q2pp3yOOTwZLWw6THX9O/Gq rIkVH7WALiiYsvesCdi/UEAIWyBXDN/0E6Mm6QPcKahx+a+A9ZsoqZnNNNApH2fQo9ku 58CQ==
X-Gm-Message-State: AA+aEWa74uSwtucXb4Gr65x6/f6Cfdmto6klODo3iiWGbl2gW96ugGvg E3EWxPEtlc4rAKOBqtd5qj2CaX34AYc2QYKE+Mq/3w==
X-Google-Smtp-Source: AFSGD/WSvVRK9cQX9VksufeSjivdtqeyPAC71B8y0dMZgCZAUqzM7s0bIqE6Kdq++7Zbs4lakms8zuMVX7iNYJ9wDNw=
X-Received: by 2002:a19:a9d2:: with SMTP id s201mr11612223lfe.154.1545922796612;  Thu, 27 Dec 2018 06:59:56 -0800 (PST)
MIME-Version: 1.0
References: <CABcZeBOjhEpw4gNDRgJD=FCWy1Wrirz_EsJefJjDHpp5mVe1fw@mail.gmail.com> <CAPK2DewE2vbjAr41xErxnjmxK2CTmK2h9fXFTBSFCigpNj9XPQ@mail.gmail.com> <CABcZeBNZhqTawAFcj9p01ig-tE=XaFm5yCXuGJQFiqoOGgNZxA@mail.gmail.com> <CAPK2Dex7hbKC3Cpq2Jy+UXr7YFqgjGUGvzNiSYMix7M5qQhx=w@mail.gmail.com>
In-Reply-To: <CAPK2Dex7hbKC3Cpq2Jy+UXr7YFqgjGUGvzNiSYMix7M5qQhx=w@mail.gmail.com>
From: Eric Rescorla <ekr@rtfm.com>
Date: Thu, 27 Dec 2018 06:59:16 -0800
Message-ID: <CABcZeBMyRGZ5QEwxLQRkcrkz665vWgOFPv+dwAuF5HSg1=B6eA@mail.gmail.com>
To: "Mr. Jaehoon Paul Jeong" <jaehoon.paul@gmail.com>
Cc: Linda Dunbar <linda.dunbar@huawei.com>, Yoav Nir <ynir.ietf@gmail.com>, i2nsf@ietf.org, skku_secu-brain_all@googlegroups.com
Content-Type: multipart/alternative; boundary="0000000000002484df057e0233b5"
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2nsf/YiTAW5kVJZjwFELDzDCwZuj5b40>
Subject: Re: [I2nsf] AD Review of draft-ietf-i2nsf-applicability-07
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, 27 Dec 2018 15:00:05 -0000

--0000000000002484df057e0233b5
Content-Type: text/plain; charset="UTF-8"

On Wed, Dec 26, 2018 at 6:42 PM Mr. Jaehoon Paul Jeong <
jaehoon.paul@gmail.com> wrote:

> Hi Eric,
> Here are my answers inlines below.
>
> On Thu, Dec 27, 2018 at 3:44 AM Eric Rescorla <ekr@rtfm.com> wrote:
>
>> Paul,
>>
>> Thanks for your new version. Some responses below.
>>
>>
>> On Tue, Dec 25, 2018 at 6:42 AM Mr. Jaehoon Paul Jeong <
>> jaehoon.paul@gmail.com> wrote:
>>
>>> Hi Eric, Linda and Yoav,
>>> I have reflected all the comments from Eric and submitted the revision
>>> -08 as follows:
>>> https://tools.ietf.org/html/draft-ietf-i2nsf-applicability-08
>>>
>>> The changes are described in Appendix A of -08 document as follows:
>>>
>>> -------------------------------------------------------------------------------------------------
>>> Appendix A.  Changes from draft-ietf-i2nsf-applicability-07
>>>
>>>    The following changes have been made from
>>>    draft-ietf-i2nsf-applicability-07:
>>>
>>>    o  This version has reflected all the comments from Eric Rescorla who
>>>       is a Security Area Director as follows.
>>>
>>>    o  In Section 1, Network Security Function (NFV) is defined in the
>>>       viewpoint of the I2NSF framework.
>>>
>>>    o  In Section 1, a user using the I2NSF User is clarified as a system
>>>       administrator in the I2NSF framework.
>>>
>>>    o  In Section 1, as the applicability of the I2NSF framework, four
>>>       different scenarios are represented with a standard bulleted list.
>>>
>>>    o  The standard document about ETSI-NFV is moved to Normative
>>>       References.
>>>
>>>    o  In Section 2, key terms (e.g., Network Function, Network Security
>>>       Function, Network Functions Virtualization, and Servive Function
>>>       Chaining) are internally defined along with the reference to open
>>>       specifications.
>>>
>>>    o  In Section 2, the definition of Firewall is corrected such that
>>>       some suspicious packets are inspected by the firewall rather than
>>>       every packet.
>>>
>>>    o  In Section 3, for a Developer's Management System, the problem of
>>>       an inside attacker is addressed, and a possible solution for the
>>>       inside attacks is suggested through I2NSF NSF monitoring
>>>       functionality.
>>>
>>
>> I'm still pretty concerned about this. Standardizing a situation in which
>> the
>> developer of your firewall has real-time management-level access to
>> that firewall seems extremely insecure, especially when that access is
>> authenticated via conventional credentials that are online as part of
>> the transaction (as opposed to software builds which can be signed
>> offline). This doesn't seem like a best practice. Why is it necessary?
>>
>
>
>>  =>  The developer of a firewall does not have real-time management-level
> access
>        even though its management system works the control plane as part
> of the I2NSF system.
>        The developer's management system provides the Security Controller
> with
>        the interface (i.e., Registration Interface) that is used to
> register the capability of
>        the developer's security network function (i.e., firewall), to
> search an NSF for the required capability for a high-level security policy,
> and to help the lifecycle management
>        of such an NSF for the Security Controller through an NFV interface
> (i.e., Ve-Vnfm interface) with the NFV's MANO.
>

I don't understand the distinction you are drawing here. Under what
conditions can the developer modify the behavior of the I2NSF system? Can
it do so at any time and without explicit action by the admin.


      In our NFV system, it is assumed that the developer's management
> system and its
>       NSF images are trustworthy as an element management system and
> Virtual Network Functions, respectively.
>

This sounds like you are describing what I am saying is bad practice.


>
>>
>>
>>    o  In Section 4, an XML file for the RESTCONF/YANG for the time-
>>>       dependent web access control is pointed out with a reference to
>>>       the Consumer-Facing Interface's data model
>>>       [consumer-facing-inf-dm].
>>>
>>
>> I didn't follow this change. The example you give of a high level security
>> policy is clearly freeform text and then you talk about XML. Is this just
>> example a summary of the semantics of something which would actually be an
>> XML file? Something else?
>>
>
>   => Even though the high-level security policy looks like a freeform
> text,  it is formatted
>       in an XML according to the high-level security policy YANG model for
> the Consumer-Facing Interface.
>       Yes, it is just an example of a summary of the semantics for such a
> high-level security policy,
>       which is represented as an XML file.
>       Here it an XML file for the web filter from the Consumer-Facing
> Interface Data Model document
>       (
> https://tools.ietf.org/html/draft-ietf-i2nsf-consumer-facing-interface-dm-02
> ):
>
>       You can see the XML file from
>
> https://tools.ietf.org/html/draft-ietf-i2nsf-consumer-facing-interface-dm-02#page-49
>
>       <?xml version="1.1" encoding="UTF-8"?>
>  <rpc message-id="4" xmlns="urn:ietf:params:xml:ns:restconf:base:1.0">
>   <edit-config>
>    <target>
>     <running/>
>    </target>
>     <config>
>      <i2nsf-cf-interface-wf-req nc:operation="create">
>          <policy-wf>
>              <rule-wf>
>                  <rule-wf-id>03</rule-wf-id>
>                  <rule-wf-name>wf-policy-example</rule-wf-name>
>                  <rule-wf-date>2018.10.26/14:03:17</rule-wf-date>
>                  <event>
>                      <event-id>04</event-id>
>                      <event-name>wf</event-name>
>                      <event-date>2018.10.26/14:03:17</event-date>
>                      <event-type>wf</event-type>
>                      <event-map-group>04</event-map-group>
>                      <enable>True</enable>
>                  </event>
>                  <condition>
>                      <condition-id>04</condition-id>
>                      <source-ip>192.168.1.3</source-ip>
>                      <destination-url>www.facebook.com</destination-url>
>                      <time-information>
>                          <begin-time>09:00</begin-time>
>                          <end-time>18:00</end-time>
>                      </time-information>
>                      <match-direction>default</match-direction>
>                      <exeption>00</exeption>
>                  </condition>
>                  <action>
>                      <action-id>04</action-id>
>                      <action-name>action-wf</action-name>
>                      <action-date>2018.10.26/14:03:17</action-date>
>                      <primary-action>REJECT</primary-action>
>                      <secondary-action>LOG</secondary-action>
>                  </action>
>                  <precedence>none</precedence>
>                <owner>
>                  <owner-id>03</owner-id>
>                  <name>i2nsf-admin</name>
>                </owner>
>              </rule-wf>
>          </policy-wf>
>      </i2nsf-cf-interface-wf-req>
>     </config>
>   </edit-config>
>  </rpc>
>   => In the above, source ip is used for the employees.
>   Instead of the source ip, we can make and use "source group" for
> employees that can be translated
>   into a set of IP addresses of the source group.
>

You need to make this clear, then. It would probably be easier to just show
the XML and then provide the text summary.


   o  In Section 6, the definitions of an SDN forwarding element and an
>>>       NSF are clarified such that an SDN forwarding element is a switch
>>>       running as either a hardware middle box or a software virtual
>>>       switch, and an NSF is a virtual network function for a security
>>>       service.
>>>
>>
>> This wasn't clear to me either. Based on this text it would seem that
>> you could run an NSF on an SDN element, so it's not clear why they
>> are disjoint sets. Can you give me more information here?
>>
>
>  => An SDN switch can run as a virtual network function like an NSF, but
> the main functionality of the SDN switch is packet forwarding with a flow
> table along with simple filtering rules. More complicated security services
> can be done at dedicated NSFs. For example, there is the Open Virtual
> Switch (OVS) project for such a software-based SDN switch:
> https://www.openvswitch.org
>
> Thus, the SDN switches and NSFs are logically disjoint sets though all of
> them  can run physically as virtual network functions.
>

I'm sorry, this still isn't clear, at least to me. How can I look at a
given software element and determine whether it's an NSF or a virtualized
SDN switch?

-Ekr

>
> If you have further questions, please let me know.
>
> Thanks.
>
> Best Regards,
> Paul
>
>>
>> -Ekr
>>
>>
>>>    o  In Section 6.3, a flow forwarding path management scheme in
>>>       [AVANT-GUARD] is described in a self-contained way as follows.
>>>       For DDoS-attack mitigation, the forwarding of traffic flows in
>>>       switches can be dynamically configured such that malicious traffic
>>>       flows are handled by the paths separated from normal traffic flows
>>>       in order to minimize the impact of those malicious traffic on the
>>>       the servers.  This flow path separation can be done by a flow
>>>       forwarding path management scheme based on [AVANT-GUARD].
>>>
>>>    o  Some typos are corrected such as "Interner -> Internet",
>>>       "Registation -> Registration", "The low-level security rules for
>>>       web filter checks -> The low-level security rules for web filter
>>>       check", "fltering -> filtering", "illegal packets -> malicious
>>>       packets", "manipulate rules -> configure rules", "managenent ->
>>>       management", and "DDoS-attack mitigation operations -> DDoS-attack
>>>       mitigation".
>>>
>>> -------------------------------------------------------------------------------------------------
>>>
>>> Thanks and Merry Christmas!
>>>
>>> Best Regards,
>>> Paul
>>>
>>> On Fri, Dec 21, 2018 at 11:33 PM Eric Rescorla <ekr@rtfm.com> wrote:
>>>
>>>> Rich version of this review at:
>>>> https://mozphab-ietf.devsvcdev.mozaws.net/D3181
>>>>
>>>>
>>>> I found a number of typographical and grammar errors. Please give this
>>>> document a thorough read.
>>>>
>>>> IMPORTANT
>>>> S 1.
>>>> >
>>>> >      Interface to Network Security Functions (I2NSF) defines a
>>>> framework
>>>> >      and interfaces for interacting with Network Security Functions
>>>> >      (NSFs).  The I2NSF framework allows heterogeneous NSFs developed
>>>> by
>>>> >      different security solution vendors to be used in the Network
>>>> >      Functions Virtualization (NFV) environment [ETSI-NFV] by
>>>> utilizing
>>>>
>>>> Much of this document cannot be understood without reading ETSI-NFV,
>>>> so it has to be a normative reference. It also would be helpful to
>>>> provide a link.
>>>>
>>>>
>>>> S 2.
>>>> >      This document uses the terminology described in [RFC7149],
>>>> >      [ITU-T.Y.3300], [ONF-OpenFlow], [ONF-SDN-Architecture],
>>>> >      [ITU-T.X.1252], [ITU-T.X.800], [RFC8329], [i2nsf-terminology],
>>>> >      [consumer-facing-inf-im], [consumer-facing-inf-dm],
>>>> >      [i2nsf-nsf-cap-im], [nsf-facing-inf-dm], [registration-inf-dm],
>>>> and
>>>> >      [nsf-triggered-steering].  In addition, the following terms are
>>>>
>>>> Every term in this document needs to be understandable without
>>>> reference to closed specifications or internally defined. Please
>>>> ensure that this is so,
>>>>
>>>>
>>>> S 3.
>>>> >      used for the I2NSF NSF-Facing Interface.
>>>> >
>>>> >      The Registration Interface between the Security Controller and
>>>> the
>>>> >      Developer's Management System can be implemented by RESTCONF
>>>> >      [RFC8040].  The data model defined in [registration-inf-dm] can
>>>> be
>>>> >      used for the I2NSF Registration Interface.
>>>>
>>>> What role does the Developer's Management System play in this? I think
>>>> this refers to the text above starting with "The developers (or
>>>> vendors)...". Is that correct?
>>>>
>>>> Assuming I am correct, this seems like a potentially serious security
>>>> vulnerability in this design in that it potentially allows an inside
>>>> attacker at the developer to seriously weaken a system's security.
>>>> What protections exist to prevent this?
>>>>
>>>>
>>>> S 4.
>>>> >      administrator wants to control the staff members' access to a
>>>> >      particular Interner service (e.g., Example.com) during business
>>>> >      hours.  The following is an example high-level security policy
>>>> rule
>>>> >      that the administrator requests: Block the staff members' access
>>>> to
>>>> >      Example.com from 9 AM to 6 PM.  The administrator sends this
>>>> high-
>>>> >      level security policy to the Security Controller, then the
>>>> Security
>>>>
>>>> The text above suggests that high-level policies are via
>>>> RESTCONF/YANG, but this is clearly freeform text.
>>>> COMMENTS
>>>> S 1.
>>>> >
>>>> >   1.  Introduction
>>>> >
>>>> >      Interface to Network Security Functions (I2NSF) defines a
>>>> framework
>>>> >      and interfaces for interacting with Network Security Functions
>>>> >      (NSFs).  The I2NSF framework allows heterogeneous NSFs developed
>>>> by
>>>>
>>>> Please define "Network Security Functions" here.
>>>>
>>>>
>>>>
>>>>
>>>> S 1.
>>>> >      functions in the NFV platform.  In the I2NSF framework, each NSF
>>>> >      initially registers the profile of its own capabilities into the
>>>> >      system in order for themselves to be available in the system.  In
>>>> >      addition, the Security Controller is validated by the I2NSF
>>>> Client
>>>> >      (also called I2NSF User) that the user is employing, so that the
>>>> user
>>>> >      can request security services through the Security Controller.
>>>>
>>>> In this case the user is the system administrator.
>>>>
>>>>
>>>> S 1.
>>>> >      [RFC7149] to provide different security functionality such as
>>>> >      firewalls [opsawg-firewalls], Deep Packet Inspection (DPI), and
>>>> >      Distributed Denial of Service (DDoS) attack mitigation; (iv) the
>>>> use
>>>> >      of NFV as supporting technology.  The implementation of I2NSF in
>>>> >      these scenarios has allowed us to verify the applicability and
>>>> >      effectiveness of the I2NSF framework for a variety of use cases.
>>>>
>>>> This would be easier to read with a standard bulleted list.
>>>>
>>>>
>>>> S 2.
>>>> >         network resources, which facilitates the design, delivery and
>>>> >         operation of network services in a dynamic and scalable manner
>>>> >         [ITU-T.Y.3300].
>>>> >
>>>> >      o  Firewall: A service function at the junction of two network
>>>> >         segments that inspects every packet that attempts to cross the
>>>>
>>>> Nit: It might not inspect *every* packet.
>>>>
>>>>
>>>> S 4.
>>>> >
>>>> >   4.  Time-dependent Web Access Control Service
>>>> >
>>>> >      This service scenario assumes that an enterprise network
>>>> >      administrator wants to control the staff members' access to a
>>>> >      particular Interner service (e.g., Example.com) during business
>>>>
>>>> Nit: "Internet"
>>>>
>>>>
>>>> S 4.
>>>> >      inspection capability is required to check whether the target
>>>> URL of
>>>> >      a received packet is in the Example.com domain or not.
>>>> >
>>>> >      The Security Controller maintains the security capabilities of
>>>> each
>>>> >      NSF running in the I2NSF system, which have been reported by the
>>>> >      Developer's Management System via the Registation interface.
>>>> Based
>>>>
>>>> Nit: "Registration"
>>>>
>>>>
>>>> S 4.
>>>> >      currently using the network.  Based on the retrieved
>>>> information, the
>>>> >      Security Controller generates low-level security rules to check
>>>> >      whether the source IP address of a received packet matches any
>>>> one
>>>> >      being used by a staff member.  In addition, the low-level
>>>> security
>>>> >      rules should be able to determine that a received packet is of
>>>> HTTP
>>>> >      protocol.  The low-level security rules for web filter checks
>>>> that
>>>>
>>>> Nit: "rules"... "checks" disagree.
>>>>
>>>>
>>>> S 6.
>>>> >      translated into their packet forwarding rules, whereas NSFs
>>>> enforce
>>>> >      NSF-related security rules requiring the security capabilities
>>>> of the
>>>> >      NSFs.  For this purpose, the Security Controller instructs the
>>>> SDN
>>>> >      Controller via NSF-Facing Interface so that SDN forwarding
>>>> elements
>>>> >      can perform the required security services with flow tables
>>>> under the
>>>> >      supervision of the SDN Controller.
>>>>
>>>> I'm having some trouble understanding the difference here between NSFs
>>>> and SDN elements. They both seem to be software controlled network
>>>> elements. Is this just some continuum about CPU power?
>>>>
>>>>
>>>> S 6.
>>>> >      can perform the required security services with flow tables
>>>> under the
>>>> >      supervision of the SDN Controller.
>>>> >
>>>> >      As an example, let us consider two different types of security
>>>> rules:
>>>> >
>>>> >      Rule A is a simple packet fltering rule that checks only the IP
>>>>
>>>> Nit: "filtering"
>>>>
>>>>
>>>> S 6.2.
>>>> >          packets that have the same call-id.
>>>> >
>>>> >      6.  The SDN Controller installs new rules (e.g., drop packets)
>>>> into
>>>> >          underlying switches.
>>>> >
>>>> >      7.  The illegal packets are dropped by these switches.
>>>>
>>>> "Illegal" is probably the wrong wrod here.
>>>>
>>>>
>>>> S 6.3.
>>>> >         is helpful to determine security policies for such a network.
>>>> >
>>>> >   6.3.  Attack Mitigation: Centralized DDoS-attack Mitigation System
>>>> >
>>>> >      A centralized DDoS-attack mitigation can manage each network
>>>> resource
>>>> >      and manipulate rules to each switch through a common server for
>>>> DDoS-
>>>>
>>>> "manipulate rules to" is not grammatical.
>>>>
>>>>
>>>> S 6.3.
>>>> >
>>>> >      Servers are categorized into stateless servers (e.g., DNS
>>>> servers)
>>>> >      and stateful servers (e.g., web servers).  For DDoS-attack
>>>> >      mitigation, traffic flows in switches are dynamically configured
>>>> by
>>>> >      traffic flow forwarding path management according to the
>>>> category of
>>>> >      servers [AVANT-GUARD].  Such a managenent should consider the
>>>> load
>>>>
>>>> 1. This seems hard to understand without this reference, which is not
>>>> public.
>>>> 2. "management"
>>>>
>>>>
>>>> S 6.3.
>>>> >      mitigation, traffic flows in switches are dynamically configured
>>>> by
>>>> >      traffic flow forwarding path management according to the
>>>> category of
>>>> >      servers [AVANT-GUARD].  Such a managenent should consider the
>>>> load
>>>> >      balance among the switches for the defense against DDoS attacks.
>>>> >
>>>> >      The procedure of DDoS-attack mitigation operations in this
>>>> system is
>>>>
>>>> "procedure of... operations" is ungrammatical
>>>>
>>>>
>>>
>>> --
>>> ===========================
>>> Mr. Jaehoon (Paul) Jeong, Ph.D.
>>> Associate Professor
>>> Department of Software
>>> Sungkyunkwan University
>>> Office: +82-31-299-4957
>>> Email: jaehoon.paul@gmail.com
>>> 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 Software
> 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>
>

--0000000000002484df057e0233b5
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">On Wed, Dec 26, 2018 at 6:42 PM Mr. Jaehoon Paul Jeong &lt=
;<a href=3D"mailto:jaehoon.paul@gmail.com">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"auto"><div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"lt=
r"><div dir=3D"ltr"><div dir=3D"ltr"><div>Hi Eric,</div><div dir=3D"auto">H=
ere are my answers inlines below.</div><br><div class=3D"gmail_quote"><div =
dir=3D"ltr">On Thu, Dec 27, 2018 at 3:44 AM Eric Rescorla &lt;<a href=3D"ma=
ilto:ekr@rtfm.com" rel=3D"noreferrer" target=3D"_blank">ekr@rtfm.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 di=
r=3D"ltr"><div dir=3D"ltr"><div>Paul,</div><div><br></div><div>Thanks for y=
our new version. Some responses below.<br></div><div><br></div></div><br><d=
iv class=3D"gmail_quote"><div dir=3D"ltr">On Tue, Dec 25, 2018 at 6:42 AM M=
r. Jaehoon Paul Jeong &lt;<a href=3D"mailto:jaehoon.paul@gmail.com" rel=3D"=
noreferrer" target=3D"_blank">jaehoon.paul@gmail.com</a>&gt; wrote:<br></di=
v><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;borde=
r-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr"><div d=
ir=3D"ltr"><div dir=3D"ltr">Hi Eric, Linda and Yoav,<div>I have reflected a=
ll the comments from Eric and submitted the revision -08 as follows:</div><=
div><a href=3D"https://tools.ietf.org/html/draft-ietf-i2nsf-applicability-0=
8" rel=3D"noreferrer" target=3D"_blank">https://tools.ietf.org/html/draft-i=
etf-i2nsf-applicability-08</a><br></div><div><br></div><div>The changes are=
 described in Appendix A of -08 document as follows:</div><div>------------=
---------------------------------------------------------------------------=
----------</div><div><div>Appendix A.=C2=A0 Changes from draft-ietf-i2nsf-a=
pplicability-07</div><div><br></div><div>=C2=A0 =C2=A0The following changes=
 have been made from</div><div>=C2=A0 =C2=A0draft-ietf-i2nsf-applicability-=
07:</div><div><br></div><div>=C2=A0 =C2=A0o=C2=A0 This version has reflecte=
d all the comments from Eric Rescorla who</div><div>=C2=A0 =C2=A0 =C2=A0 is=
 a Security Area Director as follows.</div><div><br></div><div>=C2=A0 =C2=
=A0o=C2=A0 In Section 1, Network Security Function (NFV) is defined in the<=
/div><div>=C2=A0 =C2=A0 =C2=A0 viewpoint of the I2NSF framework.</div><div>=
<br></div><div>=C2=A0 =C2=A0o=C2=A0 In Section 1, a user using the I2NSF Us=
er is clarified as a system</div><div>=C2=A0 =C2=A0 =C2=A0 administrator in=
 the I2NSF framework.</div><div><br></div><div>=C2=A0 =C2=A0o=C2=A0 In Sect=
ion 1, as the applicability of the I2NSF framework, four</div><div>=C2=A0 =
=C2=A0 =C2=A0 different scenarios are represented with a standard bulleted =
list.</div><div><br></div><div>=C2=A0 =C2=A0o=C2=A0 The standard document a=
bout ETSI-NFV is moved to Normative</div><div>=C2=A0 =C2=A0 =C2=A0 Referenc=
es.</div><div><br></div><div>=C2=A0 =C2=A0o=C2=A0 In Section 2, key terms (=
e.g., Network Function, Network Security</div><div>=C2=A0 =C2=A0 =C2=A0 Fun=
ction, Network Functions Virtualization, and Servive Function</div><div>=C2=
=A0 =C2=A0 =C2=A0 Chaining) are internally defined along with the reference=
 to open</div><div>=C2=A0 =C2=A0 =C2=A0 specifications.</div><div><br></div=
><div>=C2=A0 =C2=A0o=C2=A0 In Section 2, the definition of Firewall is corr=
ected such that</div><div>=C2=A0 =C2=A0 =C2=A0 some suspicious packets are =
inspected by the firewall rather than</div><div>=C2=A0 =C2=A0 =C2=A0 every =
packet.</div><div><br></div><div>=C2=A0 =C2=A0o=C2=A0 In Section 3, for a D=
eveloper&#39;s Management System, the problem of</div><div>=C2=A0 =C2=A0 =
=C2=A0 an inside attacker is addressed, and a possible solution for the</di=
v><div>=C2=A0 =C2=A0 =C2=A0 inside attacks is suggested through I2NSF NSF m=
onitoring</div><div>=C2=A0 =C2=A0 =C2=A0 functionality.</div></div></div></=
div></div></blockquote><div><br></div><div>I&#39;m still pretty concerned a=
bout this. Standardizing a situation in which the</div><div>developer of yo=
ur firewall has real-time management-level access to</div><div>that firewal=
l seems extremely insecure, especially when that access is</div><div>authen=
ticated via conventional credentials that are online as part of</div><div>t=
he transaction (as opposed to software builds which can be signed</div><div=
>offline). This doesn&#39;t seem like a best practice. Why is it necessary?=
</div><div></div></div></div></blockquote></div></div></div></div></div></d=
iv></div><div dir=3D"auto"><br></div><div dir=3D"ltr"><div dir=3D"ltr"><div=
 dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr"><div class=
=3D"gmail_quote"><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 class=3D"gmail_quote"><div><br></div></div></div></blockquote=
><div>=C2=A0=3D&gt;=C2=A0 The developer of a firewall does not have real-ti=
me management-level access</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0even though=
 its management system works the control plane as part of the I2NSF system.=
</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0The developer&#39;s management system=
 provides the Security Controller with</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=
=A0the interface (i.e., Registration Interface) that is used to register th=
e capability of</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0the developer&#39;s se=
curity network function (i.e., firewall), to search an NSF for the required=
 capability for a high-level security policy, and to help the lifecycle man=
agement</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0of such an NSF for the Securit=
y Controller through an NFV interface (i.e., Ve-Vnfm interface) with the NF=
V&#39;s MANO.=C2=A0</div></div></div></div></div></div></div></div></div></=
blockquote><div><br></div><div>I don&#39;t understand the distinction you a=
re drawing here. Under what conditions can the developer modify the behavio=
r of the I2NSF system? Can it do so at any time and without explicit action=
 by the admin.<br></div><div><br></div><div> <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"auto"><div dir=3D"ltr"><div dir=
=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr=
"><div class=3D"gmail_quote"><div>=C2=A0 =C2=A0 =C2=A0 In our NFV system, i=
t is assumed that the developer&#39;s management system and its</div><div>=
=C2=A0 =C2=A0 =C2=A0 NSF images are trustworthy as an element management sy=
stem and Virtual Network Functions, respectively.</div></div></div></div></=
div></div></div></div></div></blockquote><div><br></div><div>This sounds li=
ke you are describing what I am saying is bad practice.</div><div><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"auto"><div d=
ir=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"l=
tr"><div dir=3D"ltr"><div class=3D"gmail_quote"><div>=C2=A0<br></div><block=
quote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1=
px solid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr"><div class=3D"=
gmail_quote"><div></div><div><br></div><div><br></div><blockquote class=3D"=
gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(20=
4,204,204);padding-left:1ex"><div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"=
ltr"><div><div>=C2=A0 =C2=A0o=C2=A0 In Section 4, an XML file for the RESTC=
ONF/YANG for the time-</div><div>=C2=A0 =C2=A0 =C2=A0 dependent web access =
control is pointed out with a reference to</div><div>=C2=A0 =C2=A0 =C2=A0 t=
he Consumer-Facing Interface&#39;s data model</div><div>=C2=A0 =C2=A0 =C2=
=A0 [consumer-facing-inf-dm].</div></div></div></div></div></blockquote><di=
v><br></div><div>I didn&#39;t follow this change. The example you give of a=
 high level security</div><div>policy is clearly freeform text and then you=
 talk about XML. Is this just</div><div>example a summary of the semantics =
of something which would actually be an</div><div>XML file? Something else?=
</div></div></div></blockquote><div>=C2=A0</div><div dir=3D"auto">=C2=A0 =
=3D&gt; Even though the high-level security policy looks like a freeform te=
xt,=C2=A0 it is formatted</div><div>=C2=A0 =C2=A0 =C2=A0 in an XML accordin=
g to the high-level security policy YANG model for the Consumer-Facing Inte=
rface.</div><div>=C2=A0 =C2=A0 =C2=A0 Yes, it is just an example of a summa=
ry of the semantics for such a high-level security policy,=C2=A0</div><div>=
=C2=A0 =C2=A0 =C2=A0 which is represented as an XML file.</div><div>=C2=A0 =
=C2=A0 =C2=A0 Here it an XML file for the web filter from the Consumer-Faci=
ng Interface Data Model document</div><div>=C2=A0 =C2=A0 =C2=A0 (<a href=3D=
"https://tools.ietf.org/html/draft-ietf-i2nsf-consumer-facing-interface-dm-=
02" rel=3D"noreferrer" target=3D"_blank">https://tools.ietf.org/html/draft-=
ietf-i2nsf-consumer-facing-interface-dm-02</a>):</div><div><br></div><div>=
=C2=A0 =C2=A0 =C2=A0 You can see the XML file from=C2=A0</div><div>=C2=A0 =
=C2=A0 =C2=A0 =C2=A0<a href=3D"https://tools.ietf.org/html/draft-ietf-i2nsf=
-consumer-facing-interface-dm-02#page-49" rel=3D"noreferrer" target=3D"_bla=
nk">https://tools.ietf.org/html/draft-ietf-i2nsf-consumer-facing-interface-=
dm-02#page-49</a></div><div><br></div><div>=C2=A0 =C2=A0 =C2=A0 &lt;?xml ve=
rsion=3D&quot;1.1&quot; encoding=3D&quot;UTF-8&quot;?&gt;</div><div>=C2=A0&=
lt;rpc message-id=3D&quot;4&quot; xmlns=3D&quot;urn:ietf:params:xml:ns:rest=
conf:base:1.0&quot;&gt;</div><div>=C2=A0 &lt;edit-config&gt;</div><div>=C2=
=A0 =C2=A0&lt;target&gt;</div><div>=C2=A0 =C2=A0 &lt;running/&gt;</div><div=
>=C2=A0 =C2=A0&lt;/target&gt;</div><div>=C2=A0 =C2=A0 &lt;config&gt;</div><=
div>=C2=A0 =C2=A0 =C2=A0&lt;i2nsf-cf-interface-wf-req nc:operation=3D&quot;=
create&quot;&gt;</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&lt;policy-wf&=
gt;</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&lt;rule-wf&g=
t;</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0=
&lt;rule-wf-id&gt;03&lt;/rule-wf-id&gt;</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&lt;rule-wf-name&gt;wf-policy-example=
&lt;/rule-wf-name&gt;</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0&lt;rule-wf-date&gt;2018.10.26/14:03:17&lt;/rule-wf-dat=
e&gt;</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0&lt;event&gt;</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0=
 =C2=A0 =C2=A0 =C2=A0 =C2=A0&lt;event-id&gt;04&lt;/event-id&gt;</div><div>=
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0&lt;event-name&gt;wf&lt;/event-name&gt;</div><div>=C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&lt;event-date&gt;20=
18.10.26/14:03:17&lt;/event-date&gt;</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&lt;event-type&gt;wf&lt;/ev=
ent-type&gt;</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0&lt;event-map-group&gt;04&lt;/event-map-group&gt;</=
div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0&lt;enable&gt;True&lt;/enable&gt;</div><div>=C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&lt;/event&gt;</div><div>=C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&lt;condition&gt;</d=
iv><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0&lt;condition-id&gt;04&lt;/condition-id&gt;</div><div>=C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&lt;sourc=
e-ip&gt;192.168.1.3&lt;/source-ip&gt;</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0=
 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&lt;destination-url&gt;<a =
href=3D"http://www.facebook.com" rel=3D"noreferrer" target=3D"_blank">www.f=
acebook.com</a>&lt;/destination-url&gt;</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&lt;time-information&gt=
;</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0&lt;begin-time&gt;09:00&lt;/begin-time&gt;</div>=
<div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0&lt;end-time&gt;18:00&lt;/end-time&gt;</div><div>=C2=A0=
 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&lt;/=
time-information&gt;</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&lt;match-direction&gt;default&lt;/match-=
direction&gt;</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0&lt;exeption&gt;00&lt;/exeption&gt;</div><div>=
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&lt;/conditio=
n&gt;</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0&lt;action&gt;</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&lt;action-id&gt;04&lt;/action-id&gt;</div><=
div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0&lt;action-name&gt;action-wf&lt;/action-name&gt;</div><div>=C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&lt;actio=
n-date&gt;2018.10.26/14:03:17&lt;/action-date&gt;</div><div>=C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&lt;primary-a=
ction&gt;REJECT&lt;/primary-action&gt;</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&lt;secondary-action&gt=
;LOG&lt;/secondary-action&gt;</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0&lt;/action&gt;</div><div>=C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&lt;precedence&gt;none&lt;/precede=
nce&gt;</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&l=
t;owner&gt;</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0&lt;owner-id&gt;03&lt;/owner-id&gt;</div><div>=C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&lt;name&gt;i2nsf-admin&lt;/na=
me&gt;</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&lt=
;/owner&gt;</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&lt;/=
rule-wf&gt;</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&lt;/policy-wf&gt;<=
/div><div>=C2=A0 =C2=A0 =C2=A0&lt;/i2nsf-cf-interface-wf-req&gt;</div><div>=
=C2=A0 =C2=A0 &lt;/config&gt;</div><div>=C2=A0 &lt;/edit-config&gt;</div><d=
iv>=C2=A0&lt;/rpc&gt;</div><div>=C2=A0 =3D&gt;<span style=3D"white-space:pr=
e-wrap">	</span>In the above, source ip is used for the employees.<br></div=
><div><div><span style=3D"white-space:pre-wrap">=C2=A0 </span>Instead of th=
e source ip, we can make and use &quot;source group&quot; for employees tha=
t can be translated=C2=A0</div><div dir=3D"auto">=C2=A0 into a set of IP ad=
dresses of the source group.</div></div></div></div></div></div></div></div=
></div></div></blockquote><div><br></div><div>You need to make this clear, =
then. It would probably be easier to just show the XML and then provide the=
 text summary.<br></div><div><br></div><div><br></div><blockquote class=3D"=
gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(20=
4,204,204);padding-left:1ex"><div dir=3D"auto"><div dir=3D"ltr"><div dir=3D=
"ltr"><div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr"><=
div class=3D"gmail_quote"><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 class=3D"gmail_quote"><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"><div dir=3D"ltr"><div dir=3D"ltr"><div=
><div>=C2=A0 =C2=A0o=C2=A0 In Section 6, the definitions of an SDN forwardi=
ng element and an</div><div>=C2=A0 =C2=A0 =C2=A0 NSF are clarified such tha=
t an SDN forwarding element is a switch</div><div>=C2=A0 =C2=A0 =C2=A0 runn=
ing as either a hardware middle box or a software virtual</div><div>=C2=A0 =
=C2=A0 =C2=A0 switch, and an NSF is a virtual network function for a securi=
ty</div><div>=C2=A0 =C2=A0 =C2=A0 service.</div></div></div></div></div></b=
lockquote><div><br></div><div>This wasn&#39;t clear to me either. Based on =
this text it would seem that</div><div>you could run an NSF on an SDN eleme=
nt, so it&#39;s not clear why they</div><div>are disjoint sets. Can you giv=
e me more information here?<br></div></div></div></blockquote></div></div><=
/div></div></div></div></div><div dir=3D"auto"><br></div><div dir=3D"ltr"><=
div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr"><div dir=
=3D"ltr"><div class=3D"gmail_quote"><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 class=3D"gmail_quote"><div></div></div></d=
iv></blockquote></div></div></div></div></div></div></div><div dir=3D"auto"=
>=C2=A0=3D&gt; An SDN switch can run as a virtual network function like an =
NSF, but the main functionality of the SDN switch is packet forwarding with=
 a flow table along with simple filtering rules. More complicated security =
services can be done at dedicated NSFs. For example, there is the Open Virt=
ual Switch (OVS) project for such a software-based SDN switch:=C2=A0<a href=
=3D"https://www.openvswitch.org" target=3D"_blank">https://www.openvswitch.=
org</a></div><div dir=3D"auto"><br></div><div dir=3D"auto">Thus, the SDN sw=
itches and NSFs are logically disjoint sets though all of them=C2=A0 can ru=
n physically as virtual network functions.</div></div></blockquote><div><br=
></div><div>I&#39;m sorry, this still isn&#39;t clear, at least to me. How =
can I look at a given software element and determine whether it&#39;s an NS=
F or a virtualized SDN switch?<br></div><div><br></div><div>-Ekr<br></div><=
blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-l=
eft:1px solid rgb(204,204,204);padding-left:1ex"><div dir=3D"auto"><div dir=
=3D"auto"><br></div><div dir=3D"auto">If you have further questions, please=
 let me know.</div><div dir=3D"auto"><br></div><div dir=3D"auto">Thanks.</d=
iv><div dir=3D"auto"><br></div><div dir=3D"auto">Best Regards,</div><div di=
r=3D"auto">Paul</div><div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr"><di=
v dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr"><div class=3D"gmail_quote">=
<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 cla=
ss=3D"gmail_quote"><div></div><div><br></div><div>-Ekr</div><div><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"><div dir=3D"ltr"><div><div><br></div><div>=C2=A0 =C2=A0o=C2=A0 In =
Section 6.3, a flow forwarding path management scheme in</div><div>=C2=A0 =
=C2=A0 =C2=A0 [AVANT-GUARD] is described in a self-contained way as follows=
.</div><div>=C2=A0 =C2=A0 =C2=A0 For DDoS-attack mitigation, the forwarding=
 of traffic flows in</div><div>=C2=A0 =C2=A0 =C2=A0 switches can be dynamic=
ally configured such that malicious traffic</div><div>=C2=A0 =C2=A0 =C2=A0 =
flows are handled by the paths separated from normal traffic flows</div><di=
v>=C2=A0 =C2=A0 =C2=A0 in order to minimize the impact of those malicious t=
raffic on the</div><div>=C2=A0 =C2=A0 =C2=A0 the servers.=C2=A0 This flow p=
ath separation can be done by a flow</div><div>=C2=A0 =C2=A0 =C2=A0 forward=
ing path management scheme based on [AVANT-GUARD].</div><div><br></div><div=
>=C2=A0 =C2=A0o=C2=A0 Some typos are corrected such as &quot;Interner -&gt;=
 Internet&quot;,</div><div>=C2=A0 =C2=A0 =C2=A0 &quot;Registation -&gt; Reg=
istration&quot;, &quot;The low-level security rules for</div><div>=C2=A0 =
=C2=A0 =C2=A0 web filter checks -&gt; The low-level security rules for web =
filter</div><div>=C2=A0 =C2=A0 =C2=A0 check&quot;, &quot;fltering -&gt; fil=
tering&quot;, &quot;illegal packets -&gt; malicious</div><div>=C2=A0 =C2=A0=
 =C2=A0 packets&quot;, &quot;manipulate rules -&gt; configure rules&quot;, =
&quot;managenent -&gt;</div><div>=C2=A0 =C2=A0 =C2=A0 management&quot;, and=
 &quot;DDoS-attack mitigation operations -&gt; DDoS-attack</div><div>=C2=A0=
 =C2=A0 =C2=A0 mitigation&quot;.</div></div><div>--------------------------=
-----------------------------------------------------------------------=C2=
=A0</div><div>=C2=A0<br></div><div>Thanks and Merry Christmas!</div><div><b=
r></div><div>Best Regards,</div><div>Paul</div></div></div></div><br><div c=
lass=3D"gmail_quote"><div dir=3D"ltr">On Fri, Dec 21, 2018 at 11:33 PM Eric=
 Rescorla &lt;<a href=3D"mailto:ekr@rtfm.com" rel=3D"noreferrer" target=3D"=
_blank">ekr@rtfm.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"><div dir=3D"ltr">Rich version of this =
review at:<br><a href=3D"https://mozphab-ietf.devsvcdev.mozaws.net/D3181" r=
el=3D"noreferrer" target=3D"_blank">https://mozphab-ietf.devsvcdev.mozaws.n=
et/D3181</a><br><br><br>I found a number of typographical and grammar error=
s. Please give this<br>document a thorough read.<br><br>IMPORTANT<br>S 1.<b=
r>&gt;=C2=A0=C2=A0 <br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Interface to Netw=
ork Security Functions (I2NSF) defines a framework<br>&gt;=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0 and interfaces for interacting with Network Security Functi=
ons<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 (NSFs).=C2=A0 The I2NSF framework=
 allows heterogeneous NSFs developed by<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0 different security solution vendors to be used in the Network<br>&gt;=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Functions Virtualization (NFV) environment [=
ETSI-NFV] by utilizing<br><br>Much of this document cannot be understood wi=
thout reading ETSI-NFV,<br>so it has to be a normative reference. It also w=
ould be helpful to<br>provide a link.<br><br><br>S 2.<br>&gt;=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0 This document uses the terminology described in [RFC7149=
],<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 [ITU-T.Y.3300], [ONF-OpenFlow], [O=
NF-SDN-Architecture],<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 [ITU-T.X.1252],=
 [ITU-T.X.800], [RFC8329], [i2nsf-terminology],<br>&gt;=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0 [consumer-facing-inf-im], [consumer-facing-inf-dm],<br>&gt;=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0 [i2nsf-nsf-cap-im], [nsf-facing-inf-dm], [regis=
tration-inf-dm], and<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 [nsf-triggered-s=
teering].=C2=A0 In addition, the following terms are<br><br>Every term in t=
his document needs to be understandable without<br>reference to closed spec=
ifications or internally defined. Please<br>ensure that this is so,<br><br>=
<br>S 3.<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 used for the I2NSF NSF-Facin=
g Interface.<br>&gt;=C2=A0=C2=A0 <br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 The=
 Registration Interface between the Security Controller and the<br>&gt;=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0 Developer&#39;s Management System can be implem=
ented by RESTCONF<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 [RFC8040].=C2=A0 Th=
e data model defined in [registration-inf-dm] can be<br>&gt;=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0 used for the I2NSF Registration Interface.<br><br>What role=
 does the Developer&#39;s Management System play in this? I think<br>this r=
efers to the text above starting with &quot;The developers (or<br>vendors).=
..&quot;. Is that correct?<br><br>Assuming I am correct, this seems like a =
potentially serious security<br>vulnerability in this design in that it pot=
entially allows an inside<br>attacker at the developer to seriously weaken =
a system&#39;s security.<br>What protections exist to prevent this?<br><br>=
<br>S 4.<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 administrator wants to contr=
ol the staff members&#39; access to a<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
 particular Interner service (e.g., Example.com) during business<br>&gt;=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0 hours.=C2=A0 The following is an example high-l=
evel security policy rule<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 that the ad=
ministrator requests: Block the staff members&#39; access to<br>&gt;=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0 Example.com from 9 AM to 6 PM.=C2=A0 The administr=
ator sends this high-<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 level security =
policy to the Security Controller, then the Security<br><br>The text above =
suggests that high-level policies are via<br>RESTCONF/YANG, but this is cle=
arly freeform text.<br>COMMENTS<br>S 1.<br>&gt;=C2=A0=C2=A0 <br>&gt;=C2=A0=
=C2=A0 1.=C2=A0 Introduction<br>&gt;=C2=A0=C2=A0 <br>&gt;=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0 Interface to Network Security Functions (I2NSF) defines a fram=
ework<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 and interfaces for interacting =
with Network Security Functions<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 (NSFs=
).=C2=A0 The I2NSF framework allows heterogeneous NSFs developed by<br><br>=
Please define &quot;Network Security Functions&quot; here.<br><br><br><br><=
br>S 1.<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 functions in the NFV platform=
.=C2=A0 In the I2NSF framework, each NSF<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0 initially registers the profile of its own capabilities into the<br>&gt=
;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 system in order for themselves to be availa=
ble in the system.=C2=A0 In<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 addition,=
 the Security Controller is validated by the I2NSF Client<br>&gt;=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0 (also called I2NSF User) that the user is employing, =
so that the user<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 can request security=
 services through the Security Controller.<br><br>In this case the user is =
the system administrator.<br><br><br>S 1.<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0 [RFC7149] to provide different security functionality such as<br>&gt=
;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 firewalls [opsawg-firewalls], Deep Packet I=
nspection (DPI), and<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Distributed Deni=
al of Service (DDoS) attack mitigation; (iv) the use<br>&gt;=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0 of NFV as supporting technology.=C2=A0 The implementation o=
f I2NSF in<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 these scenarios has allowe=
d us to verify the applicability and<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 =
effectiveness of the I2NSF framework for a variety of use cases.<br><br>Thi=
s would be easier to read with a standard bulleted list.<br><br><br>S 2.<br=
>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 network resources, wh=
ich facilitates the design, delivery and<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0 operation of network services in a dynamic and scalab=
le manner<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 [ITU-T.Y.=
3300].<br>&gt;=C2=A0=C2=A0 <br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 o=C2=A0 F=
irewall: A service function at the junction of two network<br>&gt;=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 segments that inspects every packet=
 that attempts to cross the<br><br>Nit: It might not inspect *every* packet=
.<br><br><br>S 4.<br>&gt;=C2=A0=C2=A0 <br>&gt;=C2=A0=C2=A0 4.=C2=A0 Time-de=
pendent Web Access Control Service<br>&gt;=C2=A0=C2=A0 <br>&gt;=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0 This service scenario assumes that an enterprise network=
<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 administrator wants to control the s=
taff members&#39; access to a<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 particu=
lar Interner service (e.g., Example.com) during business<br><br>Nit: &quot;=
Internet&quot;<br><br><br>S 4.<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 inspec=
tion capability is required to check whether the target URL of<br>&gt;=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0 a received packet is in the Example.com domain =
or not.<br>&gt;=C2=A0=C2=A0 <br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 The Secu=
rity Controller maintains the security capabilities of each<br>&gt;=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0 NSF running in the I2NSF system, which have been r=
eported by the<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Developer&#39;s Manage=
ment System via the Registation interface.=C2=A0 Based<br><br>Nit: &quot;Re=
gistration&quot;<br><br><br>S 4.<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 curr=
ently using the network.=C2=A0 Based on the retrieved information, the<br>&=
gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Security Controller generates low-level s=
ecurity rules to check<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 whether the so=
urce IP address of a received packet matches any one<br>&gt;=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0 being used by a staff member.=C2=A0 In addition, the low-le=
vel security<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 rules should be able to =
determine that a received packet is of HTTP<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0 protocol.=C2=A0 The low-level security rules for web filter checks t=
hat<br><br>Nit: &quot;rules&quot;... &quot;checks&quot; disagree.<br><br><b=
r>S 6.<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 translated into their packet f=
orwarding rules, whereas NSFs enforce<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
 NSF-related security rules requiring the security capabilities of the<br>&=
gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 NSFs.=C2=A0 For this purpose, the Securit=
y Controller instructs the SDN<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Contro=
ller via NSF-Facing Interface so that SDN forwarding elements<br>&gt;=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0 can perform the required security services with fl=
ow tables under the<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 supervision of th=
e SDN Controller.<br><br>I&#39;m having some trouble understanding the diff=
erence here between NSFs<br>and SDN elements. They both seem to be software=
 controlled network<br>elements. Is this just some continuum about CPU powe=
r?<br><br><br>S 6.<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 can perform the re=
quired security services with flow tables under the<br>&gt;=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0 supervision of the SDN Controller.<br>&gt;=C2=A0=C2=A0 <br>=
&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 As an example, let us consider two diffe=
rent types of security rules:<br>&gt;=C2=A0=C2=A0 <br>&gt;=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0 Rule A is a simple packet fltering rule that checks only th=
e IP<br><br>Nit: &quot;filtering&quot;<br><br><br>S 6.2.<br>&gt;=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 packets that have the same ca=
ll-id.<br>&gt;=C2=A0=C2=A0 <br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 6.=C2=A0 =
The SDN Controller installs new rules (e.g., drop packets) into<br>&gt;=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 underlying switches.<br=
>&gt;=C2=A0=C2=A0 <br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 7.=C2=A0 The illeg=
al packets are dropped by these switches.<br><br>&quot;Illegal&quot; is pro=
bably the wrong wrod here.<br><br><br>S 6.3.<br>&gt;=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0 is helpful to determine security policies for s=
uch a network.<br>&gt;=C2=A0=C2=A0 <br>&gt;=C2=A0=C2=A0 6.3.=C2=A0 Attack M=
itigation: Centralized DDoS-attack Mitigation System<br>&gt;=C2=A0=C2=A0 <b=
r>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 A centralized DDoS-attack mitigation c=
an manage each network resource<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 and m=
anipulate rules to each switch through a common server for DDoS-<br><br>&qu=
ot;manipulate rules to&quot; is not grammatical.<br><br><br>S 6.3.<br>&gt;=
=C2=A0=C2=A0 <br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Servers are categorized=
 into stateless servers (e.g., DNS servers)<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0 and stateful servers (e.g., web servers).=C2=A0 For DDoS-attack<br>&=
gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 mitigation, traffic flows in switches are=
 dynamically configured by<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 traffic fl=
ow forwarding path management according to the category of<br>&gt;=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0 servers [AVANT-GUARD].=C2=A0 Such a managenent should=
 consider the load<br><br>1. This seems hard to understand without this ref=
erence, which is not<br>public.<br>2. &quot;management&quot;<br><br><br>S 6=
.3.<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 mitigation, traffic flows in swit=
ches are dynamically configured by<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 tr=
affic flow forwarding path management according to the category of<br>&gt;=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 servers [AVANT-GUARD].=C2=A0 Such a managene=
nt should consider the load<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 balance a=
mong the switches for the defense against DDoS attacks.<br>&gt;=C2=A0=C2=A0=
 <br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 The procedure of DDoS-attack mitiga=
tion operations in this system is<br><br>&quot;procedure of... operations&q=
uot; is ungrammatical<br><br></div></div>
</blockquote></div><br clear=3D"all"><div><br></div>-- <br><div dir=3D"ltr"=
 class=3D"gmail-m_7571128782014320286m_-6695152896369925623gmail-m_-6079876=
77208405722gmail-m_-9111533177071645325gmail_signature"><div dir=3D"ltr"><d=
iv><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 So=
ftware<br>Sungkyunkwan University<br>Office: +82-31-299-4957<br>Email: <a h=
ref=3D"mailto:jaehoon.paul@gmail.com" rel=3D"noreferrer" target=3D"_blank">=
jaehoon.paul@gmail.com</a><br>Personal Homepage: <a href=3D"http://cpslab.s=
kku.edu/people-jaehoon-jeong.php" rel=3D"noreferrer" 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-m_7571128782014320286m_-6695152896369925623gmail_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<b=
r>Department of Software<br>Sungkyunkwan University<br>Office: +82-31-299-4=
957<br>Email: <a href=3D"mailto:jaehoon.paul@gmail.com" rel=3D"noreferrer" =
target=3D"_blank">jaehoon.paul@gmail.com</a>,=C2=A0<a href=3D"mailto:paulje=
ong@skku.edu" style=3D"font-size:12.8px" rel=3D"noreferrer" target=3D"_blan=
k">pauljeong@skku.edu</a><br>Personal Homepage: <a href=3D"http://cpslab.sk=
ku.edu/people-jaehoon-jeong.php" rel=3D"noreferrer" target=3D"_blank">http:=
//iotlab.skku.edu/people-jaehoon-jeong.php</a><br></div></div></div></div><=
/div></div></div></div></div></div></div></div></div></div></div>
</blockquote></div></div>

--0000000000002484df057e0233b5--


From nobody Thu Dec 27 19:21:46 2018
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 6E3BD130E1F for <i2nsf@ietfa.amsl.com>; Thu, 27 Dec 2018 19:21:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.499
X-Spam-Level: 
X-Spam-Status: No, score=-0.499 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HK_NAME_FM_MR_MRS=1.499, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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 H8kmNhiw2b5R for <i2nsf@ietfa.amsl.com>; Thu, 27 Dec 2018 19:21:40 -0800 (PST)
Received: from mail-it1-x136.google.com (mail-it1-x136.google.com [IPv6:2607:f8b0: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 6C90D1286D9 for <i2nsf@ietf.org>; Thu, 27 Dec 2018 19:21:40 -0800 (PST)
Received: by mail-it1-x136.google.com with SMTP id h193so25855123ita.5 for <i2nsf@ietf.org>; Thu, 27 Dec 2018 19:21:40 -0800 (PST)
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=LDclM07yZngOKwXwCinCTRs25qN+XUTfGMcfQjAL35E=; b=kBegryF4IYLyuX+KWMrjDZ3gEr8fH/qhZ8N9ucBRbIsWMLkhN6W3SXm2Q3W1YVRbEi Lw8LhfJuuykiBF38GktVn7FQZRuFCcNSs5W6KlGH7+q8i9QOyHJ2X19Lrz+1CVyH0SFq 7mJeXsIRzkpTx1BMk+M6w7zXNjjoyzMGgP2YvDjsG2WXZl4T12db/dZvwt43iTuyG5cE LHspvt5PHfi9mLd8nUxNyIYaaJREO01yXaiKQc0uGOB5gwoaSFArdynK98pr73bBnR74 tnWpZFvjuUamr3pH+M6sZsXJSX+PYWItj+FvULg4AxnW6HQ8BZtteWzl4wmYngSMuf+F fKyg==
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=LDclM07yZngOKwXwCinCTRs25qN+XUTfGMcfQjAL35E=; b=FrklB+YPgTGNn4TkZzMOR82zqah8kDI+PvbYEzG248gqIhy+W+i+M+s8z/MqtTWhWX J27YOz7KfFrgv+fKhuKT7OySmpN+RjYKWi9qPDRMVdOSNjFMGpwJGfjXmFMzeJrW6Bwf fOP9BvqzNJgI6zq2lpFF0RVKsg8bwgWReKKOlivBS90yWIyQDjO7GBJ9/+9+x7PnhwhA 1iDoUEfrD5pwzgtNtmzwGkG6tmesMc1kaunzY3FCpcItAn41yaMkyXbjFe3dKvmHBMcO v970S0U485lzWdIbuPTLhEINSbwhm6ewBDsZh3hPAoPzFK2AyQObTfkaZXbsF2FTHrlb pUCg==
X-Gm-Message-State: AJcUukcTFV2zVk1PGEQGUF0CPb72sgY8nNt+1AxPyafMwXIFzPHrxnxq Unrd7AmNxZKLhfc7nkQYC5CuPRjRxLw7hqQeIGA=
X-Google-Smtp-Source: AFSGD/W/zabWVU5AUMuaJXHLRGgt+XOq+vLriIS5TGk4zqP01LEvqrtbgKMcblOVlogtgFcTllEmIbEyezJmLOLy73I=
X-Received: by 2002:a24:d441:: with SMTP id x62mr16606229itg.141.1545967299453;  Thu, 27 Dec 2018 19:21:39 -0800 (PST)
MIME-Version: 1.0
References: <CABcZeBOjhEpw4gNDRgJD=FCWy1Wrirz_EsJefJjDHpp5mVe1fw@mail.gmail.com> <CAPK2DewE2vbjAr41xErxnjmxK2CTmK2h9fXFTBSFCigpNj9XPQ@mail.gmail.com> <CABcZeBNZhqTawAFcj9p01ig-tE=XaFm5yCXuGJQFiqoOGgNZxA@mail.gmail.com> <CAPK2Dex7hbKC3Cpq2Jy+UXr7YFqgjGUGvzNiSYMix7M5qQhx=w@mail.gmail.com> <CABcZeBMyRGZ5QEwxLQRkcrkz665vWgOFPv+dwAuF5HSg1=B6eA@mail.gmail.com>
In-Reply-To: <CABcZeBMyRGZ5QEwxLQRkcrkz665vWgOFPv+dwAuF5HSg1=B6eA@mail.gmail.com>
From: "Mr. Jaehoon Paul Jeong" <jaehoon.paul@gmail.com>
Date: Fri, 28 Dec 2018 12:20:58 +0900
Message-ID: <CAPK2Deyn1=vVShbq=hMRmvQ1=G5_Yew8pYgqQC=Vh-dG9d2Wrg@mail.gmail.com>
To: Eric Rescorla <ekr@rtfm.com>
Cc: Linda Dunbar <linda.dunbar@huawei.com>, Yoav Nir <ynir.ietf@gmail.com>,  DIEGO LOPEZ GARCIA <diego.r.lopez@telefonica.com>, "i2nsf@ietf.org" <i2nsf@ietf.org>, skku_secu-brain_all@googlegroups.com,  "Mr. Jaehoon Paul Jeong" <jaehoon.paul@gmail.com>
Content-Type: multipart/alternative; boundary="000000000000b7e5a0057e0c8fa8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2nsf/NVl-JUpyOlfiEcDXNl7vMSxlxCs>
Subject: Re: [I2nsf] AD Review of draft-ietf-i2nsf-applicability-07
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, 28 Dec 2018 03:21:45 -0000

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

Eric,
Let me answer your further questions below.

On Thu, Dec 27, 2018 at 11:59 PM Eric Rescorla <ekr@rtfm.com> wrote:

>
>
> On Wed, Dec 26, 2018 at 6:42 PM Mr. Jaehoon Paul Jeong <
> jaehoon.paul@gmail.com> wrote:
>
>> Hi Eric,
>> Here are my answers inlines below.
>>
>> On Thu, Dec 27, 2018 at 3:44 AM Eric Rescorla <ekr@rtfm.com> wrote:
>>
>>> Paul,
>>>
>>> Thanks for your new version. Some responses below.
>>>
>>>
>>> On Tue, Dec 25, 2018 at 6:42 AM Mr. Jaehoon Paul Jeong <
>>> jaehoon.paul@gmail.com> wrote:
>>>
>>>> Hi Eric, Linda and Yoav,
>>>> I have reflected all the comments from Eric and submitted the revision
>>>> -08 as follows:
>>>> https://tools.ietf.org/html/draft-ietf-i2nsf-applicability-08
>>>>
>>>> The changes are described in Appendix A of -08 document as follows:
>>>>
>>>> -------------------------------------------------------------------------------------------------
>>>> Appendix A.  Changes from draft-ietf-i2nsf-applicability-07
>>>>
>>>>    The following changes have been made from
>>>>    draft-ietf-i2nsf-applicability-07:
>>>>
>>>>    o  This version has reflected all the comments from Eric Rescorla who
>>>>       is a Security Area Director as follows.
>>>>
>>>>    o  In Section 1, Network Security Function (NFV) is defined in the
>>>>       viewpoint of the I2NSF framework.
>>>>
>>>>    o  In Section 1, a user using the I2NSF User is clarified as a system
>>>>       administrator in the I2NSF framework.
>>>>
>>>>    o  In Section 1, as the applicability of the I2NSF framework, four
>>>>       different scenarios are represented with a standard bulleted list.
>>>>
>>>>    o  The standard document about ETSI-NFV is moved to Normative
>>>>       References.
>>>>
>>>>    o  In Section 2, key terms (e.g., Network Function, Network Security
>>>>       Function, Network Functions Virtualization, and Servive Function
>>>>       Chaining) are internally defined along with the reference to open
>>>>       specifications.
>>>>
>>>>    o  In Section 2, the definition of Firewall is corrected such that
>>>>       some suspicious packets are inspected by the firewall rather than
>>>>       every packet.
>>>>
>>>>    o  In Section 3, for a Developer's Management System, the problem of
>>>>       an inside attacker is addressed, and a possible solution for the
>>>>       inside attacks is suggested through I2NSF NSF monitoring
>>>>       functionality.
>>>>
>>>
>>> I'm still pretty concerned about this. Standardizing a situation in
>>> which the
>>> developer of your firewall has real-time management-level access to
>>> that firewall seems extremely insecure, especially when that access is
>>> authenticated via conventional credentials that are online as part of
>>> the transaction (as opposed to software builds which can be signed
>>> offline). This doesn't seem like a best practice. Why is it necessary?
>>>
>>
>>
>>>  =>  The developer of a firewall does not have real-time
>> management-level access
>>        even though its management system works the control plane as part
>> of the I2NSF system.
>>        The developer's management system provides the Security Controller
>> with
>>        the interface (i.e., Registration Interface) that is used to
>> register the capability of
>>        the developer's security network function (i.e., firewall), to
>> search an NSF for the required capability for a high-level security policy,
>> and to help the lifecycle management
>>        of such an NSF for the Security Controller through an NFV
>> interface (i.e., Ve-Vnfm interface) with the NFV's MANO.
>>
>
> I don't understand the distinction you are drawing here. Under what
> conditions can the developer modify the behavior of the I2NSF system? Can
> it do so at any time and without explicit action by the admin.
>
>  =>  The developer means a security solution vendor (e.g., McAfee and
Symantec) who provides the I2NSF system with security solutions,
       such as firewall, web filter, DPI, IDS/IPS, and DDoS-attack
mitigator. Actually, the developer's management system
       cannot modify the behavior of the I2NSF system in run-time as long
as the vendor doesn't have any backdoor to
       their developer's management system.
       This developer's management system facilitates the security service
government by the Security Controller
       by providing the Security Controller with the Registration Interface
for the capability registration and instantiation/de-instantiation
       of the image of a security service function.
       Thus, only the administrator can modify the behavior of the I2NSF
system.

       Maybe,
       Diego Lopez can clarify my answer because he is the editor of RFC
8329 (Framework for Interface to Network Security Functions):
       https://tools.ietf.org/html/rfc8329



>
>       In our NFV system, it is assumed that the developer's management
>> system and its
>>       NSF images are trustworthy as an element management system and
>> Virtual Network Functions, respectively.
>>
>
> This sounds like you are describing what I am saying is bad practice.
>

 => If the developer's management system and NSFs are not trustworthy, our
I2NSF system is vulnerable to an insider's attack
      in the same way with the legacy security systems. However, I would
say that the I2NSF monitoring functionality can be used to
      monitor and regulate the behaviors of the developer's management
system and NSFs.

     For this answer, maybe other I2NSF members can help me clarify my
assumption for you.

>
>
>>
>>>
>>>
>>>    o  In Section 4, an XML file for the RESTCONF/YANG for the time-
>>>>       dependent web access control is pointed out with a reference to
>>>>       the Consumer-Facing Interface's data model
>>>>       [consumer-facing-inf-dm].
>>>>
>>>
>>> I didn't follow this change. The example you give of a high level
>>> security
>>> policy is clearly freeform text and then you talk about XML. Is this just
>>> example a summary of the semantics of something which would actually be
>>> an
>>> XML file? Something else?
>>>
>>
>>   => Even though the high-level security policy looks like a freeform
>> text,  it is formatted
>>       in an XML according to the high-level security policy YANG model
>> for the Consumer-Facing Interface.
>>       Yes, it is just an example of a summary of the semantics for such a
>> high-level security policy,
>>       which is represented as an XML file.
>>       Here it an XML file for the web filter from the Consumer-Facing
>> Interface Data Model document
>>       (
>> https://tools.ietf.org/html/draft-ietf-i2nsf-consumer-facing-interface-dm-02
>> ):
>>
>>       You can see the XML file from
>>
>> https://tools.ietf.org/html/draft-ietf-i2nsf-consumer-facing-interface-dm-02#page-49
>>
>>       <?xml version="1.1" encoding="UTF-8"?>
>>  <rpc message-id="4" xmlns="urn:ietf:params:xml:ns:restconf:base:1.0">
>>   <edit-config>
>>    <target>
>>     <running/>
>>    </target>
>>     <config>
>>      <i2nsf-cf-interface-wf-req nc:operation="create">
>>          <policy-wf>
>>              <rule-wf>
>>                  <rule-wf-id>03</rule-wf-id>
>>                  <rule-wf-name>wf-policy-example</rule-wf-name>
>>                  <rule-wf-date>2018.10.26/14:03:17</rule-wf-date>
>>                  <event>
>>                      <event-id>04</event-id>
>>                      <event-name>wf</event-name>
>>                      <event-date>2018.10.26/14:03:17</event-date>
>>                      <event-type>wf</event-type>
>>                      <event-map-group>04</event-map-group>
>>                      <enable>True</enable>
>>                  </event>
>>                  <condition>
>>                      <condition-id>04</condition-id>
>>                      <source-ip>192.168.1.3</source-ip>
>>                      <destination-url>www.facebook.com</destination-url>
>>                      <time-information>
>>                          <begin-time>09:00</begin-time>
>>                          <end-time>18:00</end-time>
>>                      </time-information>
>>                      <match-direction>default</match-direction>
>>                      <exeption>00</exeption>
>>                  </condition>
>>                  <action>
>>                      <action-id>04</action-id>
>>                      <action-name>action-wf</action-name>
>>                      <action-date>2018.10.26/14:03:17</action-date>
>>                      <primary-action>REJECT</primary-action>
>>                      <secondary-action>LOG</secondary-action>
>>                  </action>
>>                  <precedence>none</precedence>
>>                <owner>
>>                  <owner-id>03</owner-id>
>>                  <name>i2nsf-admin</name>
>>                </owner>
>>              </rule-wf>
>>          </policy-wf>
>>      </i2nsf-cf-interface-wf-req>
>>     </config>
>>   </edit-config>
>>  </rpc>
>>   => In the above, source ip is used for the employees.
>>   Instead of the source ip, we can make and use "source group" for
>> employees that can be translated
>>   into a set of IP addresses of the source group.
>>
>
> You need to make this clear, then. It would probably be easier to just
> show the XML and then provide the text summary.
>
>   => Okay. I will include a simplified example XML code for web filter and
provide the text summary as below.

   This service scenario assumes that an enterprise network
   administrator wants to control the staff members' access to a
   particular Internet service (e.g., Example.com) during business
   hours.  The following is an example high-level security policy rule
   for a web filter that the administrator requests: Block the staff
members' access to Example.com from 9 AM to 6 PM.
   Here is an example XML code for this web filter:
<I2NSF>
    <name>block_website</name>
        <cond>
            <src>Staff_Member's_PC</src>
            <dest>Example.com</dest>
    <time-span-start>9:00AM</time-span-start>
            <time-span-end>-6:00PM</time-span-end>
        </cond>
        <action>block<action>
</I2NSF>

   The security policy name is "bloc_website" with the tag "name".
   The filtering condition has the source group "Staff_Member's_PC" with
the tag "src",
   the destination website "Example.com" with the tag "dest",
   the filtering start time is the time "9:00AM" with the tag "
time-span-start",
   and the filtering end time is the time "6:00PM" with the tag "
time-span-end".
   The action is to "block" the packets satisfying the above condition,
   that is, to drop those packets.


>
>    o  In Section 6, the definitions of an SDN forwarding element and an
>>>>       NSF are clarified such that an SDN forwarding element is a switch
>>>>       running as either a hardware middle box or a software virtual
>>>>       switch, and an NSF is a virtual network function for a security
>>>>       service.
>>>>
>>>
>>> This wasn't clear to me either. Based on this text it would seem that
>>> you could run an NSF on an SDN element, so it's not clear why they
>>> are disjoint sets. Can you give me more information here?
>>>
>>
>>  => An SDN switch can run as a virtual network function like an NSF, but
>> the main functionality of the SDN switch is packet forwarding with a flow
>> table along with simple filtering rules. More complicated security services
>> can be done at dedicated NSFs. For example, there is the Open Virtual
>> Switch (OVS) project for such a software-based SDN switch:
>> https://www.openvswitch.org
>>
>> Thus, the SDN switches and NSFs are logically disjoint sets though all of
>> them  can run physically as virtual network functions.
>>
>
> I'm sorry, this still isn't clear, at least to me. How can I look at a
> given software element and determine whether it's an NSF or a virtualized
> SDN switch?
>

 => The distinction is logically done such that the NFV system having the
I2NSF system categorizes some VNFs as NSFs for dedicated security services
      and some VNFs as virtualized SDN switches for packet switching and
simple filtering rule enforcement.

     If there is an expert in the NFV, please let us know for further
clarification.

     Thanks.

     Best Regards,
     Paul


>
> -Ekr
>
>>
>> If you have further questions, please let me know.
>>
>> Thanks.
>>
>> Best Regards,
>> Paul
>>
>>>
>>> -Ekr
>>>
>>>
>>>>    o  In Section 6.3, a flow forwarding path management scheme in
>>>>       [AVANT-GUARD] is described in a self-contained way as follows.
>>>>       For DDoS-attack mitigation, the forwarding of traffic flows in
>>>>       switches can be dynamically configured such that malicious traffic
>>>>       flows are handled by the paths separated from normal traffic flows
>>>>       in order to minimize the impact of those malicious traffic on the
>>>>       the servers.  This flow path separation can be done by a flow
>>>>       forwarding path management scheme based on [AVANT-GUARD].
>>>>
>>>>    o  Some typos are corrected such as "Interner -> Internet",
>>>>       "Registation -> Registration", "The low-level security rules for
>>>>       web filter checks -> The low-level security rules for web filter
>>>>       check", "fltering -> filtering", "illegal packets -> malicious
>>>>       packets", "manipulate rules -> configure rules", "managenent ->
>>>>       management", and "DDoS-attack mitigation operations -> DDoS-attack
>>>>       mitigation".
>>>>
>>>> -------------------------------------------------------------------------------------------------
>>>>
>>>> Thanks and Merry Christmas!
>>>>
>>>> Best Regards,
>>>> Paul
>>>>
>>>> On Fri, Dec 21, 2018 at 11:33 PM Eric Rescorla <ekr@rtfm.com> wrote:
>>>>
>>>>> Rich version of this review at:
>>>>> https://mozphab-ietf.devsvcdev.mozaws.net/D3181
>>>>>
>>>>>
>>>>> I found a number of typographical and grammar errors. Please give this
>>>>> document a thorough read.
>>>>>
>>>>> IMPORTANT
>>>>> S 1.
>>>>> >
>>>>> >      Interface to Network Security Functions (I2NSF) defines a
>>>>> framework
>>>>> >      and interfaces for interacting with Network Security Functions
>>>>> >      (NSFs).  The I2NSF framework allows heterogeneous NSFs
>>>>> developed by
>>>>> >      different security solution vendors to be used in the Network
>>>>> >      Functions Virtualization (NFV) environment [ETSI-NFV] by
>>>>> utilizing
>>>>>
>>>>> Much of this document cannot be understood without reading ETSI-NFV,
>>>>> so it has to be a normative reference. It also would be helpful to
>>>>> provide a link.
>>>>>
>>>>>
>>>>> S 2.
>>>>> >      This document uses the terminology described in [RFC7149],
>>>>> >      [ITU-T.Y.3300], [ONF-OpenFlow], [ONF-SDN-Architecture],
>>>>> >      [ITU-T.X.1252], [ITU-T.X.800], [RFC8329], [i2nsf-terminology],
>>>>> >      [consumer-facing-inf-im], [consumer-facing-inf-dm],
>>>>> >      [i2nsf-nsf-cap-im], [nsf-facing-inf-dm], [registration-inf-dm],
>>>>> and
>>>>> >      [nsf-triggered-steering].  In addition, the following terms are
>>>>>
>>>>> Every term in this document needs to be understandable without
>>>>> reference to closed specifications or internally defined. Please
>>>>> ensure that this is so,
>>>>>
>>>>>
>>>>> S 3.
>>>>> >      used for the I2NSF NSF-Facing Interface.
>>>>> >
>>>>> >      The Registration Interface between the Security Controller and
>>>>> the
>>>>> >      Developer's Management System can be implemented by RESTCONF
>>>>> >      [RFC8040].  The data model defined in [registration-inf-dm] can
>>>>> be
>>>>> >      used for the I2NSF Registration Interface.
>>>>>
>>>>> What role does the Developer's Management System play in this? I think
>>>>> this refers to the text above starting with "The developers (or
>>>>> vendors)...". Is that correct?
>>>>>
>>>>> Assuming I am correct, this seems like a potentially serious security
>>>>> vulnerability in this design in that it potentially allows an inside
>>>>> attacker at the developer to seriously weaken a system's security.
>>>>> What protections exist to prevent this?
>>>>>
>>>>>
>>>>> S 4.
>>>>> >      administrator wants to control the staff members' access to a
>>>>> >      particular Interner service (e.g., Example.com) during business
>>>>> >      hours.  The following is an example high-level security policy
>>>>> rule
>>>>> >      that the administrator requests: Block the staff members'
>>>>> access to
>>>>> >      Example.com from 9 AM to 6 PM.  The administrator sends this
>>>>> high-
>>>>> >      level security policy to the Security Controller, then the
>>>>> Security
>>>>>
>>>>> The text above suggests that high-level policies are via
>>>>> RESTCONF/YANG, but this is clearly freeform text.
>>>>> COMMENTS
>>>>> S 1.
>>>>> >
>>>>> >   1.  Introduction
>>>>> >
>>>>> >      Interface to Network Security Functions (I2NSF) defines a
>>>>> framework
>>>>> >      and interfaces for interacting with Network Security Functions
>>>>> >      (NSFs).  The I2NSF framework allows heterogeneous NSFs
>>>>> developed by
>>>>>
>>>>> Please define "Network Security Functions" here.
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> S 1.
>>>>> >      functions in the NFV platform.  In the I2NSF framework, each NSF
>>>>> >      initially registers the profile of its own capabilities into the
>>>>> >      system in order for themselves to be available in the system.
>>>>> In
>>>>> >      addition, the Security Controller is validated by the I2NSF
>>>>> Client
>>>>> >      (also called I2NSF User) that the user is employing, so that
>>>>> the user
>>>>> >      can request security services through the Security Controller.
>>>>>
>>>>> In this case the user is the system administrator.
>>>>>
>>>>>
>>>>> S 1.
>>>>> >      [RFC7149] to provide different security functionality such as
>>>>> >      firewalls [opsawg-firewalls], Deep Packet Inspection (DPI), and
>>>>> >      Distributed Denial of Service (DDoS) attack mitigation; (iv)
>>>>> the use
>>>>> >      of NFV as supporting technology.  The implementation of I2NSF in
>>>>> >      these scenarios has allowed us to verify the applicability and
>>>>> >      effectiveness of the I2NSF framework for a variety of use cases.
>>>>>
>>>>> This would be easier to read with a standard bulleted list.
>>>>>
>>>>>
>>>>> S 2.
>>>>> >         network resources, which facilitates the design, delivery and
>>>>> >         operation of network services in a dynamic and scalable
>>>>> manner
>>>>> >         [ITU-T.Y.3300].
>>>>> >
>>>>> >      o  Firewall: A service function at the junction of two network
>>>>> >         segments that inspects every packet that attempts to cross
>>>>> the
>>>>>
>>>>> Nit: It might not inspect *every* packet.
>>>>>
>>>>>
>>>>> S 4.
>>>>> >
>>>>> >   4.  Time-dependent Web Access Control Service
>>>>> >
>>>>> >      This service scenario assumes that an enterprise network
>>>>> >      administrator wants to control the staff members' access to a
>>>>> >      particular Interner service (e.g., Example.com) during business
>>>>>
>>>>> Nit: "Internet"
>>>>>
>>>>>
>>>>> S 4.
>>>>> >      inspection capability is required to check whether the target
>>>>> URL of
>>>>> >      a received packet is in the Example.com domain or not.
>>>>> >
>>>>> >      The Security Controller maintains the security capabilities of
>>>>> each
>>>>> >      NSF running in the I2NSF system, which have been reported by the
>>>>> >      Developer's Management System via the Registation interface.
>>>>> Based
>>>>>
>>>>> Nit: "Registration"
>>>>>
>>>>>
>>>>> S 4.
>>>>> >      currently using the network.  Based on the retrieved
>>>>> information, the
>>>>> >      Security Controller generates low-level security rules to check
>>>>> >      whether the source IP address of a received packet matches any
>>>>> one
>>>>> >      being used by a staff member.  In addition, the low-level
>>>>> security
>>>>> >      rules should be able to determine that a received packet is of
>>>>> HTTP
>>>>> >      protocol.  The low-level security rules for web filter checks
>>>>> that
>>>>>
>>>>> Nit: "rules"... "checks" disagree.
>>>>>
>>>>>
>>>>> S 6.
>>>>> >      translated into their packet forwarding rules, whereas NSFs
>>>>> enforce
>>>>> >      NSF-related security rules requiring the security capabilities
>>>>> of the
>>>>> >      NSFs.  For this purpose, the Security Controller instructs the
>>>>> SDN
>>>>> >      Controller via NSF-Facing Interface so that SDN forwarding
>>>>> elements
>>>>> >      can perform the required security services with flow tables
>>>>> under the
>>>>> >      supervision of the SDN Controller.
>>>>>
>>>>> I'm having some trouble understanding the difference here between NSFs
>>>>> and SDN elements. They both seem to be software controlled network
>>>>> elements. Is this just some continuum about CPU power?
>>>>>
>>>>>
>>>>> S 6.
>>>>> >      can perform the required security services with flow tables
>>>>> under the
>>>>> >      supervision of the SDN Controller.
>>>>> >
>>>>> >      As an example, let us consider two different types of security
>>>>> rules:
>>>>> >
>>>>> >      Rule A is a simple packet fltering rule that checks only the IP
>>>>>
>>>>> Nit: "filtering"
>>>>>
>>>>>
>>>>> S 6.2.
>>>>> >          packets that have the same call-id.
>>>>> >
>>>>> >      6.  The SDN Controller installs new rules (e.g., drop packets)
>>>>> into
>>>>> >          underlying switches.
>>>>> >
>>>>> >      7.  The illegal packets are dropped by these switches.
>>>>>
>>>>> "Illegal" is probably the wrong wrod here.
>>>>>
>>>>>
>>>>> S 6.3.
>>>>> >         is helpful to determine security policies for such a network.
>>>>> >
>>>>> >   6.3.  Attack Mitigation: Centralized DDoS-attack Mitigation System
>>>>> >
>>>>> >      A centralized DDoS-attack mitigation can manage each network
>>>>> resource
>>>>> >      and manipulate rules to each switch through a common server for
>>>>> DDoS-
>>>>>
>>>>> "manipulate rules to" is not grammatical.
>>>>>
>>>>>
>>>>> S 6.3.
>>>>> >
>>>>> >      Servers are categorized into stateless servers (e.g., DNS
>>>>> servers)
>>>>> >      and stateful servers (e.g., web servers).  For DDoS-attack
>>>>> >      mitigation, traffic flows in switches are dynamically
>>>>> configured by
>>>>> >      traffic flow forwarding path management according to the
>>>>> category of
>>>>> >      servers [AVANT-GUARD].  Such a managenent should consider the
>>>>> load
>>>>>
>>>>> 1. This seems hard to understand without this reference, which is not
>>>>> public.
>>>>> 2. "management"
>>>>>
>>>>>
>>>>> S 6.3.
>>>>> >      mitigation, traffic flows in switches are dynamically
>>>>> configured by
>>>>> >      traffic flow forwarding path management according to the
>>>>> category of
>>>>> >      servers [AVANT-GUARD].  Such a managenent should consider the
>>>>> load
>>>>> >      balance among the switches for the defense against DDoS attacks.
>>>>> >
>>>>> >      The procedure of DDoS-attack mitigation operations in this
>>>>> system is
>>>>>
>>>>> "procedure of... operations" is ungrammatical
>>>>>
>>>>>
>>>>
>>>> --
>>>> ===========================
>>>> Mr. Jaehoon (Paul) Jeong, Ph.D.
>>>> Associate Professor
>>>> Department of Software
>>>> Sungkyunkwan University
>>>> Office: +82-31-299-4957
>>>> Email: jaehoon.paul@gmail.com
>>>> 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 Software
>> 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 Software
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>

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

<div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr"><div>Er=
ic,</div><div>Let me answer your further questions below.</div><br><div cla=
ss=3D"gmail_quote"><div dir=3D"ltr">On Thu, Dec 27, 2018 at 11:59 PM Eric R=
escorla &lt;<a href=3D"mailto:ekr@rtfm.com">ekr@rtfm.com</a>&gt; wrote:<br>=
</div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;b=
order-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr"><d=
iv dir=3D"ltr"><br></div><br><div class=3D"gmail_quote"><div dir=3D"ltr">On=
 Wed, Dec 26, 2018 at 6:42 PM Mr. Jaehoon Paul Jeong &lt;<a href=3D"mailto:=
jaehoon.paul@gmail.com" target=3D"_blank">jaehoon.paul@gmail.com</a>&gt; wr=
ote:<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=
"auto"><div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr">=
<div dir=3D"ltr"><div dir=3D"ltr"><div>Hi Eric,</div><div dir=3D"auto">Here=
 are my answers inlines below.</div><br><div class=3D"gmail_quote"><div dir=
=3D"ltr">On Thu, Dec 27, 2018 at 3:44 AM Eric Rescorla &lt;<a href=3D"mailt=
o:ekr@rtfm.com" rel=3D"noreferrer" target=3D"_blank">ekr@rtfm.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"><div dir=3D"ltr"><div>Paul,</div><div><br></div><div>Thanks for yo=
ur new version. Some responses below.<br></div><div><br></div></div><br><di=
v class=3D"gmail_quote"><div dir=3D"ltr">On Tue, Dec 25, 2018 at 6:42 AM Mr=
. Jaehoon Paul Jeong &lt;<a href=3D"mailto:jaehoon.paul@gmail.com" rel=3D"n=
oreferrer" 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"ltr"><div di=
r=3D"ltr"><div dir=3D"ltr">Hi Eric, Linda and Yoav,<div>I have reflected al=
l the comments from Eric and submitted the revision -08 as follows:</div><d=
iv><a href=3D"https://tools.ietf.org/html/draft-ietf-i2nsf-applicability-08=
" rel=3D"noreferrer" target=3D"_blank">https://tools.ietf.org/html/draft-ie=
tf-i2nsf-applicability-08</a><br></div><div><br></div><div>The changes are =
described in Appendix A of -08 document as follows:</div><div>-------------=
---------------------------------------------------------------------------=
---------</div><div><div>Appendix A.=C2=A0 Changes from draft-ietf-i2nsf-ap=
plicability-07</div><div><br></div><div>=C2=A0 =C2=A0The following changes =
have been made from</div><div>=C2=A0 =C2=A0draft-ietf-i2nsf-applicability-0=
7:</div><div><br></div><div>=C2=A0 =C2=A0o=C2=A0 This version has reflected=
 all the comments from Eric Rescorla who</div><div>=C2=A0 =C2=A0 =C2=A0 is =
a Security Area Director as follows.</div><div><br></div><div>=C2=A0 =C2=A0=
o=C2=A0 In Section 1, Network Security Function (NFV) is defined in the</di=
v><div>=C2=A0 =C2=A0 =C2=A0 viewpoint of the I2NSF framework.</div><div><br=
></div><div>=C2=A0 =C2=A0o=C2=A0 In Section 1, a user using the I2NSF User =
is clarified as a system</div><div>=C2=A0 =C2=A0 =C2=A0 administrator in th=
e I2NSF framework.</div><div><br></div><div>=C2=A0 =C2=A0o=C2=A0 In Section=
 1, as the applicability of the I2NSF framework, four</div><div>=C2=A0 =C2=
=A0 =C2=A0 different scenarios are represented with a standard bulleted lis=
t.</div><div><br></div><div>=C2=A0 =C2=A0o=C2=A0 The standard document abou=
t ETSI-NFV is moved to Normative</div><div>=C2=A0 =C2=A0 =C2=A0 References.=
</div><div><br></div><div>=C2=A0 =C2=A0o=C2=A0 In Section 2, key terms (e.g=
., Network Function, Network Security</div><div>=C2=A0 =C2=A0 =C2=A0 Functi=
on, Network Functions Virtualization, and Servive Function</div><div>=C2=A0=
 =C2=A0 =C2=A0 Chaining) are internally defined along with the reference to=
 open</div><div>=C2=A0 =C2=A0 =C2=A0 specifications.</div><div><br></div><d=
iv>=C2=A0 =C2=A0o=C2=A0 In Section 2, the definition of Firewall is correct=
ed such that</div><div>=C2=A0 =C2=A0 =C2=A0 some suspicious packets are ins=
pected by the firewall rather than</div><div>=C2=A0 =C2=A0 =C2=A0 every pac=
ket.</div><div><br></div><div>=C2=A0 =C2=A0o=C2=A0 In Section 3, for a Deve=
loper&#39;s Management System, the problem of</div><div>=C2=A0 =C2=A0 =C2=
=A0 an inside attacker is addressed, and a possible solution for the</div><=
div>=C2=A0 =C2=A0 =C2=A0 inside attacks is suggested through I2NSF NSF moni=
toring</div><div>=C2=A0 =C2=A0 =C2=A0 functionality.</div></div></div></div=
></div></blockquote><div><br></div><div>I&#39;m still pretty concerned abou=
t this. Standardizing a situation in which the</div><div>developer of your =
firewall has real-time management-level access to</div><div>that firewall s=
eems extremely insecure, especially when that access is</div><div>authentic=
ated via conventional credentials that are online as part of</div><div>the =
transaction (as opposed to software builds which can be signed</div><div>of=
fline). This doesn&#39;t seem like a best practice. Why is it necessary?</d=
iv><div></div></div></div></blockquote></div></div></div></div></div></div>=
</div><div dir=3D"auto"><br></div><div dir=3D"ltr"><div dir=3D"ltr"><div di=
r=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr"><div class=3D"=
gmail_quote"><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 class=3D"gmail_quote"><div><br></div></div></div></blockquote><di=
v>=C2=A0=3D&gt;=C2=A0 The developer of a firewall does not have real-time m=
anagement-level access</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0even though its=
 management system works the control plane as part of the I2NSF system.</di=
v><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0The developer&#39;s management system pro=
vides the Security Controller with</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0the=
 interface (i.e., Registration Interface) that is used to register the capa=
bility of</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0the developer&#39;s security=
 network function (i.e., firewall), to search an NSF for the required capab=
ility for a high-level security policy, and to help the lifecycle managemen=
t</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0of such an NSF for the Security Cont=
roller through an NFV interface (i.e., Ve-Vnfm interface) with the NFV&#39;=
s MANO.=C2=A0</div></div></div></div></div></div></div></div></div></blockq=
uote><div><br></div><div>I don&#39;t understand the distinction you are dra=
wing here. Under what conditions can the developer modify the behavior of t=
he I2NSF system? Can it do so at any time and without explicit action by th=
e admin.<br></div><div><br></div></div></div></blockquote><div>=C2=A0=3D&gt=
;=C2=A0 The developer means a security solution vendor (e.g., McAfee and Sy=
mantec) who provides the I2NSF system with security solutions,=C2=A0</div><=
div>=C2=A0 =C2=A0 =C2=A0 =C2=A0such as firewall, web filter, DPI, IDS/IPS, =
and DDoS-attack mitigator. Actually, the developer&#39;s management system<=
/div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0cannot modify the behavior of the I2NS=
F system in run-time as long as the vendor doesn&#39;t have any backdoor to=
=C2=A0</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0their developer&#39;s managemen=
t system.</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0This developer&#39;s managem=
ent system facilitates the security service government by the Security Cont=
roller=C2=A0</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0by providing the Security=
 Controller with the Registration Interface for the capability registration=
 and instantiation/de-instantiation=C2=A0</div><div>=C2=A0 =C2=A0 =C2=A0 =
=C2=A0of the image of a security service function.</div><div>=C2=A0 =C2=A0 =
=C2=A0 =C2=A0Thus, only the administrator can modify the behavior of the I2=
NSF system.</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0</div><div>=C2=A0 =C2=A0 =
=C2=A0 =C2=A0Maybe,</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0Diego Lopez can cl=
arify my answer because he is the editor of RFC 8329 (Framework for Interfa=
ce to Network Security Functions):</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0<a =
href=3D"https://tools.ietf.org/html/rfc8329">https://tools.ietf.org/html/rf=
c8329</a></div><div><br></div><div>=C2=A0 =C2=A0 =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 class=3D"g=
mail_quote"><div></div><div> <br></div><blockquote class=3D"gmail_quote" st=
yle=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padd=
ing-left:1ex"><div dir=3D"auto"><div dir=3D"ltr"><div dir=3D"ltr"><div dir=
=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr"><div class=3D"g=
mail_quote"><div>=C2=A0 =C2=A0 =C2=A0 In our NFV system, it is assumed that=
 the developer&#39;s management system and its</div><div>=C2=A0 =C2=A0 =C2=
=A0 NSF images are trustworthy as an element management system and Virtual =
Network Functions, respectively.</div></div></div></div></div></div></div><=
/div></div></blockquote><div><br></div><div>This sounds like you are descri=
bing what I am saying is bad practice.</div></div></div></blockquote><div><=
br></div><div>=C2=A0=3D&gt; If the developer&#39;s management system and NS=
Fs are not trustworthy, our I2NSF system is vulnerable to an insider&#39;s =
attack=C2=A0</div><div>=C2=A0 =C2=A0 =C2=A0 in the same way with the legacy=
 security systems. However, I would say that the I2NSF monitoring functiona=
lity can be used to=C2=A0</div><div>=C2=A0 =C2=A0 =C2=A0 monitor and regula=
te the behaviors of the developer&#39;s management system and NSFs.</div><d=
iv><br></div><div>=C2=A0 =C2=A0 =C2=A0For this answer, maybe other I2NSF me=
mbers can help me clarify my assumption for you.</div><blockquote class=3D"=
gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(20=
4,204,204);padding-left:1ex"><div dir=3D"ltr"><div class=3D"gmail_quote"><d=
iv><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"=
auto"><div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr"><=
div dir=3D"ltr"><div dir=3D"ltr"><div class=3D"gmail_quote"><div>=C2=A0<br>=
</div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;b=
order-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr"><d=
iv class=3D"gmail_quote"><div></div><div><br></div><div><br></div><blockquo=
te 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">=
<div dir=3D"ltr"><div><div>=C2=A0 =C2=A0o=C2=A0 In Section 4, an XML file f=
or the RESTCONF/YANG for the time-</div><div>=C2=A0 =C2=A0 =C2=A0 dependent=
 web access control is pointed out with a reference to</div><div>=C2=A0 =C2=
=A0 =C2=A0 the Consumer-Facing Interface&#39;s data model</div><div>=C2=A0 =
=C2=A0 =C2=A0 [consumer-facing-inf-dm].</div></div></div></div></div></bloc=
kquote><div><br></div><div>I didn&#39;t follow this change. The example you=
 give of a high level security</div><div>policy is clearly freeform text an=
d then you talk about XML. Is this just</div><div>example a summary of the =
semantics of something which would actually be an</div><div>XML file? Somet=
hing else?</div></div></div></blockquote><div>=C2=A0</div><div dir=3D"auto"=
>=C2=A0 =3D&gt; Even though the high-level security policy looks like a fre=
eform text,=C2=A0 it is formatted</div><div>=C2=A0 =C2=A0 =C2=A0 in an XML =
according to the high-level security policy YANG model for the Consumer-Fac=
ing Interface.</div><div>=C2=A0 =C2=A0 =C2=A0 Yes, it is just an example of=
 a summary of the semantics for such a high-level security policy,=C2=A0</d=
iv><div>=C2=A0 =C2=A0 =C2=A0 which is represented as an XML file.</div><div=
>=C2=A0 =C2=A0 =C2=A0 Here it an XML file for the web filter from the Consu=
mer-Facing Interface Data Model document</div><div>=C2=A0 =C2=A0 =C2=A0 (<a=
 href=3D"https://tools.ietf.org/html/draft-ietf-i2nsf-consumer-facing-inter=
face-dm-02" rel=3D"noreferrer" target=3D"_blank">https://tools.ietf.org/htm=
l/draft-ietf-i2nsf-consumer-facing-interface-dm-02</a>):</div><div><br></di=
v><div>=C2=A0 =C2=A0 =C2=A0 You can see the XML file from=C2=A0</div><div>=
=C2=A0 =C2=A0 =C2=A0 =C2=A0<a href=3D"https://tools.ietf.org/html/draft-iet=
f-i2nsf-consumer-facing-interface-dm-02#page-49" rel=3D"noreferrer" target=
=3D"_blank">https://tools.ietf.org/html/draft-ietf-i2nsf-consumer-facing-in=
terface-dm-02#page-49</a></div><div><br></div><div>=C2=A0 =C2=A0 =C2=A0 &lt=
;?xml version=3D&quot;1.1&quot; encoding=3D&quot;UTF-8&quot;?&gt;</div><div=
>=C2=A0&lt;rpc message-id=3D&quot;4&quot; xmlns=3D&quot;urn:ietf:params:xml=
:ns:restconf:base:1.0&quot;&gt;</div><div>=C2=A0 &lt;edit-config&gt;</div><=
div>=C2=A0 =C2=A0&lt;target&gt;</div><div>=C2=A0 =C2=A0 &lt;running/&gt;</d=
iv><div>=C2=A0 =C2=A0&lt;/target&gt;</div><div>=C2=A0 =C2=A0 &lt;config&gt;=
</div><div>=C2=A0 =C2=A0 =C2=A0&lt;i2nsf-cf-interface-wf-req nc:operation=
=3D&quot;create&quot;&gt;</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&lt;p=
olicy-wf&gt;</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&lt;=
rule-wf&gt;</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0&lt;rule-wf-id&gt;03&lt;/rule-wf-id&gt;</div><div>=C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&lt;rule-wf-name&gt;wf-poli=
cy-example&lt;/rule-wf-name&gt;</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&lt;rule-wf-date&gt;2018.10.26/14:03:17&lt;/=
rule-wf-date&gt;</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0=
 =C2=A0 =C2=A0&lt;event&gt;</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&lt;event-id&gt;04&lt;/event-id&gt=
;</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0&lt;event-name&gt;wf&lt;/event-name&gt;</div><div>=C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&lt;event=
-date&gt;2018.10.26/14:03:17&lt;/event-date&gt;</div><div>=C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&lt;event-type&g=
t;wf&lt;/event-type&gt;</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0=
 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&lt;event-map-group&gt;04&lt;/event-map-=
group&gt;</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0=
 =C2=A0 =C2=A0 =C2=A0&lt;enable&gt;True&lt;/enable&gt;</div><div>=C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&lt;/event&gt;</div><di=
v>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&lt;conditi=
on&gt;</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0&lt;condition-id&gt;04&lt;/condition-id&gt;</div><div>=
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0&lt;source-ip&gt;192.168.1.3&lt;/source-ip&gt;</div><div>=C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&lt;destinati=
on-url&gt;<a href=3D"http://www.facebook.com" rel=3D"noreferrer" target=3D"=
_blank">www.facebook.com</a>&lt;/destination-url&gt;</div><div>=C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&lt;time-=
information&gt;</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&lt;begin-time&gt;09:00&lt;/begin-=
time&gt;</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&lt;end-time&gt;18:00&lt;/end-time&gt;</d=
iv><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0&lt;/time-information&gt;</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&lt;match-direction&gt;defa=
ult&lt;/match-direction&gt;</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&lt;exeption&gt;00&lt;/exeption&gt=
;</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&=
lt;/condition&gt;</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0&lt;action&gt;</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&lt;action-id&gt;04&lt;/action=
-id&gt;</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0&lt;action-name&gt;action-wf&lt;/action-name&gt;</div><=
div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0&lt;action-date&gt;2018.10.26/14:03:17&lt;/action-date&gt;</div><div>=
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0&lt;primary-action&gt;REJECT&lt;/primary-action&gt;</div><div>=C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&lt;secon=
dary-action&gt;LOG&lt;/secondary-action&gt;</div><div>=C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&lt;/action&gt;</div><div>=C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&lt;precedence&gt;no=
ne&lt;/precedence&gt;</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0&lt;owner&gt;</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0&lt;owner-id&gt;03&lt;/owner-id&gt;</div><div>=C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&lt;name&gt;i2ns=
f-admin&lt;/name&gt;</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0&lt;/owner&gt;</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0&lt;/rule-wf&gt;</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&=
lt;/policy-wf&gt;</div><div>=C2=A0 =C2=A0 =C2=A0&lt;/i2nsf-cf-interface-wf-=
req&gt;</div><div>=C2=A0 =C2=A0 &lt;/config&gt;</div><div>=C2=A0 &lt;/edit-=
config&gt;</div><div>=C2=A0&lt;/rpc&gt;</div><div>=C2=A0 =3D&gt;<span style=
=3D"white-space:pre-wrap">	</span>In the above, source ip is used for the e=
mployees.<br></div><div><div><span style=3D"white-space:pre-wrap">=C2=A0 </=
span>Instead of the source ip, we can make and use &quot;source group&quot;=
 for employees that can be translated=C2=A0</div><div dir=3D"auto">=C2=A0 i=
nto a set of IP addresses of the source group.</div></div></div></div></div=
></div></div></div></div></div></blockquote><div><br></div><div>You need to=
 make this clear, then. It would probably be easier to just show the XML an=
d then provide the text summary.<br></div><div><br></div></div></div></bloc=
kquote><div>=C2=A0 =3D&gt; Okay. I will include a simplified example XML co=
de for web filter and provide the text summary as below.</div><div><br></di=
v><div><div>=C2=A0 =C2=A0This service scenario assumes that an enterprise n=
etwork</div><div>=C2=A0 =C2=A0administrator wants to control the staff memb=
ers&#39; access to a</div><div>=C2=A0 =C2=A0particular Internet service (e.=
g., Example.com) during business</div><div>=C2=A0 =C2=A0hours.=C2=A0 The fo=
llowing is an example high-level security policy rule</div><div>=C2=A0 =C2=
=A0for a web filter that the administrator requests: Block the staff member=
s&#39; access to Example.com from 9 AM to 6 PM.=C2=A0=C2=A0</div><div>=C2=
=A0 =C2=A0Here is an example XML code for this web filter:</div><div>&lt;I2=
NSF&gt;</div><div>=C2=A0 =C2=A0 &lt;name&gt;block_website&lt;/name&gt;</div=
><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 &lt;cond&gt;</div><div>=C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 &lt;src&gt;Staff_Member&#39;s_PC&lt;/src&gt;</div>=
<div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 &lt;dest&gt;Example.com&lt;/=
dest&gt;</div><div><span style=3D"white-space:pre">		</span>=C2=A0 =C2=A0 &=
lt;time-span-start&gt;9:00AM&lt;/time-span-start&gt;</div><div>=C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 &lt;time-span-end&gt;-6:00PM&lt;/time-span-=
end&gt;</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 &lt;/cond&gt;</div><div>=C2=
=A0 =C2=A0 =C2=A0 =C2=A0 &lt;action&gt;block&lt;action&gt;</div><div>&lt;/I=
2NSF&gt;</div><div><br></div><div>=C2=A0 =C2=A0The security policy name is =
&quot;bloc_website&quot; with the tag &quot;name&quot;.</div><div>=C2=A0 =
=C2=A0The filtering condition has the source group &quot;Staff_Member&#39;s=
_PC&quot; with the tag &quot;src&quot;,</div><div>=C2=A0 =C2=A0the destinat=
ion website &quot;Example.com&quot; with the tag &quot;dest&quot;,</div><di=
v>=C2=A0 =C2=A0the filtering start time is the time &quot;9:00AM&quot; with=
 the tag &quot;

time-span-start&quot;,=C2=A0</div><div>=C2=A0 =C2=A0and the filtering end t=
ime is the time &quot;6:00PM&quot; with the tag &quot;

time-span-end&quot;.</div><div>=C2=A0 =C2=A0The action is to &quot;block&qu=
ot; the packets satisfying the above condition,=C2=A0</div><div>=C2=A0 =C2=
=A0that is, to drop those packets.</div></div><div>=C2=A0</div><blockquote =
class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px sol=
id rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr"><div class=3D"gmail_=
quote"><div></div><div><br></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"auto"><div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr=
"><div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr"><div class=3D"gmail_qu=
ote"><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;bo=
rder-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr"><di=
v class=3D"gmail_quote"><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 dir=3D"ltr"><div dir=3D"ltr"><div><div>=C2=A0 =C2=A0o=
=C2=A0 In Section 6, the definitions of an SDN forwarding element and an</d=
iv><div>=C2=A0 =C2=A0 =C2=A0 NSF are clarified such that an SDN forwarding =
element is a switch</div><div>=C2=A0 =C2=A0 =C2=A0 running as either a hard=
ware middle box or a software virtual</div><div>=C2=A0 =C2=A0 =C2=A0 switch=
, and an NSF is a virtual network function for a security</div><div>=C2=A0 =
=C2=A0 =C2=A0 service.</div></div></div></div></div></blockquote><div><br><=
/div><div>This wasn&#39;t clear to me either. Based on this text it would s=
eem that</div><div>you could run an NSF on an SDN element, so it&#39;s not =
clear why they</div><div>are disjoint sets. Can you give me more informatio=
n here?<br></div></div></div></blockquote></div></div></div></div></div></d=
iv></div><div dir=3D"auto"><br></div><div dir=3D"ltr"><div dir=3D"ltr"><div=
 dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr"><div class=
=3D"gmail_quote"><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 class=3D"gmail_quote"><div></div></div></div></blockquote></d=
iv></div></div></div></div></div></div><div dir=3D"auto">=C2=A0=3D&gt; An S=
DN switch can run as a virtual network function like an NSF, but the main f=
unctionality of the SDN switch is packet forwarding with a flow table along=
 with simple filtering rules. More complicated security services can be don=
e at dedicated NSFs. For example, there is the Open Virtual Switch (OVS) pr=
oject for such a software-based SDN switch:=C2=A0<a href=3D"https://www.ope=
nvswitch.org" target=3D"_blank">https://www.openvswitch.org</a></div><div d=
ir=3D"auto"><br></div><div dir=3D"auto">Thus, the SDN switches and NSFs are=
 logically disjoint sets though all of them=C2=A0 can run physically as vir=
tual network functions.</div></div></blockquote><div><br></div><div>I&#39;m=
 sorry, this still isn&#39;t clear, at least to me. How can I look at a giv=
en software element and determine whether it&#39;s an NSF or a virtualized =
SDN switch?<br></div></div></div></blockquote><div><br></div><div>=C2=A0=3D=
&gt; The distinction is logically done such that the NFV system having the =
I2NSF system categorizes some VNFs as NSFs for dedicated security services<=
/div><div>=C2=A0 =C2=A0 =C2=A0 and some VNFs as virtualized SDN switches fo=
r packet switching and simple filtering rule enforcement.</div><div><br></d=
iv><div>=C2=A0 =C2=A0 =C2=A0If there is an expert in the NFV, please let us=
 know for further clarification.</div><div><br></div><div>=C2=A0 =C2=A0 =C2=
=A0Thanks.</div><div><br></div><div>=C2=A0 =C2=A0 =C2=A0Best Regards,</div>=
<div>=C2=A0 =C2=A0 =C2=A0Paul</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 class=3D"gmail_quote"><div=
></div><div><br></div><div>-Ekr<br></div><blockquote class=3D"gmail_quote" =
style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);pa=
dding-left:1ex"><div dir=3D"auto"><div dir=3D"auto"><br></div><div dir=3D"a=
uto">If you have further questions, please let me know.</div><div dir=3D"au=
to"><br></div><div dir=3D"auto">Thanks.</div><div dir=3D"auto">=C2=A0</div>=
<div dir=3D"auto">Best Regards,</div><div dir=3D"auto">Paul</div><div dir=
=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr=
"><div dir=3D"ltr"><div class=3D"gmail_quote"><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"><div dir=3D"ltr"><div class=3D"gmail_quote"><div></div=
><div><br></div><div>-Ekr</div><div><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"><div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr"><di=
v><div><br></div><div>=C2=A0 =C2=A0o=C2=A0 In Section 6.3, a flow forwardin=
g path management scheme in</div><div>=C2=A0 =C2=A0 =C2=A0 [AVANT-GUARD] is=
 described in a self-contained way as follows.</div><div>=C2=A0 =C2=A0 =C2=
=A0 For DDoS-attack mitigation, the forwarding of traffic flows in</div><di=
v>=C2=A0 =C2=A0 =C2=A0 switches can be dynamically configured such that mal=
icious traffic</div><div>=C2=A0 =C2=A0 =C2=A0 flows are handled by the path=
s separated from normal traffic flows</div><div>=C2=A0 =C2=A0 =C2=A0 in ord=
er to minimize the impact of those malicious traffic on the</div><div>=C2=
=A0 =C2=A0 =C2=A0 the servers.=C2=A0 This flow path separation can be done =
by a flow</div><div>=C2=A0 =C2=A0 =C2=A0 forwarding path management scheme =
based on [AVANT-GUARD].</div><div><br></div><div>=C2=A0 =C2=A0o=C2=A0 Some =
typos are corrected such as &quot;Interner -&gt; Internet&quot;,</div><div>=
=C2=A0 =C2=A0 =C2=A0 &quot;Registation -&gt; Registration&quot;, &quot;The =
low-level security rules for</div><div>=C2=A0 =C2=A0 =C2=A0 web filter chec=
ks -&gt; The low-level security rules for web filter</div><div>=C2=A0 =C2=
=A0 =C2=A0 check&quot;, &quot;fltering -&gt; filtering&quot;, &quot;illegal=
 packets -&gt; malicious</div><div>=C2=A0 =C2=A0 =C2=A0 packets&quot;, &quo=
t;manipulate rules -&gt; configure rules&quot;, &quot;managenent -&gt;</div=
><div>=C2=A0 =C2=A0 =C2=A0 management&quot;, and &quot;DDoS-attack mitigati=
on operations -&gt; DDoS-attack</div><div>=C2=A0 =C2=A0 =C2=A0 mitigation&q=
uot;.</div></div><div>-----------------------------------------------------=
--------------------------------------------=C2=A0</div><div>=C2=A0<br></di=
v><div>Thanks and Merry Christmas!</div><div><br></div><div>Best Regards,</=
div><div>Paul</div></div></div></div><br><div class=3D"gmail_quote"><div di=
r=3D"ltr">On Fri, Dec 21, 2018 at 11:33 PM Eric Rescorla &lt;<a href=3D"mai=
lto:ekr@rtfm.com" rel=3D"noreferrer" target=3D"_blank">ekr@rtfm.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">Rich version of this review at:<br><a href=3D"htt=
ps://mozphab-ietf.devsvcdev.mozaws.net/D3181" rel=3D"noreferrer" target=3D"=
_blank">https://mozphab-ietf.devsvcdev.mozaws.net/D3181</a><br><br><br>I fo=
und a number of typographical and grammar errors. Please give this<br>docum=
ent a thorough read.<br><br>IMPORTANT<br>S 1.<br>&gt;=C2=A0=C2=A0 <br>&gt;=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Interface to Network Security Functions (I2N=
SF) defines a framework<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 and interface=
s for interacting with Network Security Functions<br>&gt;=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0 (NSFs).=C2=A0 The I2NSF framework allows heterogeneous NSFs de=
veloped by<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 different security solutio=
n vendors to be used in the Network<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 F=
unctions Virtualization (NFV) environment [ETSI-NFV] by utilizing<br><br>Mu=
ch of this document cannot be understood without reading ETSI-NFV,<br>so it=
 has to be a normative reference. It also would be helpful to<br>provide a =
link.<br><br><br>S 2.<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 This document u=
ses the terminology described in [RFC7149],<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0 [ITU-T.Y.3300], [ONF-OpenFlow], [ONF-SDN-Architecture],<br>&gt;=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0 [ITU-T.X.1252], [ITU-T.X.800], [RFC8329], [i2ns=
f-terminology],<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 [consumer-facing-inf-=
im], [consumer-facing-inf-dm],<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 [i2nsf=
-nsf-cap-im], [nsf-facing-inf-dm], [registration-inf-dm], and<br>&gt;=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0 [nsf-triggered-steering].=C2=A0 In addition, the f=
ollowing terms are<br><br>Every term in this document needs to be understan=
dable without<br>reference to closed specifications or internally defined. =
Please<br>ensure that this is so,<br><br><br>S 3.<br>&gt;=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0 used for the I2NSF NSF-Facing Interface.<br>&gt;=C2=A0=C2=A0 <=
br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 The Registration Interface between th=
e Security Controller and the<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Develop=
er&#39;s Management System can be implemented by RESTCONF<br>&gt;=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0 [RFC8040].=C2=A0 The data model defined in [registrat=
ion-inf-dm] can be<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 used for the I2NSF=
 Registration Interface.<br><br>What role does the Developer&#39;s Manageme=
nt System play in this? I think<br>this refers to the text above starting w=
ith &quot;The developers (or<br>vendors)...&quot;. Is that correct?<br><br>=
Assuming I am correct, this seems like a potentially serious security<br>vu=
lnerability in this design in that it potentially allows an inside<br>attac=
ker at the developer to seriously weaken a system&#39;s security.<br>What p=
rotections exist to prevent this?<br><br><br>S 4.<br>&gt;=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0 administrator wants to control the staff members&#39; access t=
o a<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 particular Interner service (e.g.=
, Example.com) during business<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 hours.=
=C2=A0 The following is an example high-level security policy rule<br>&gt;=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 that the administrator requests: Block the s=
taff members&#39; access to<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Example.c=
om from 9 AM to 6 PM.=C2=A0 The administrator sends this high-<br>&gt;=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0 level security policy to the Security Controlle=
r, then the Security<br><br>The text above suggests that high-level policie=
s are via<br>RESTCONF/YANG, but this is clearly freeform text.<br>COMMENTS<=
br>S 1.<br>&gt;=C2=A0=C2=A0 <br>&gt;=C2=A0=C2=A0 1.=C2=A0 Introduction<br>&=
gt;=C2=A0=C2=A0 <br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Interface to Network=
 Security Functions (I2NSF) defines a framework<br>&gt;=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0 and interfaces for interacting with Network Security Functions=
<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 (NSFs).=C2=A0 The I2NSF framework al=
lows heterogeneous NSFs developed by<br><br>Please define &quot;Network Sec=
urity Functions&quot; here.<br><br><br><br><br>S 1.<br>&gt;=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0 functions in the NFV platform.=C2=A0 In the I2NSF framework=
, each NSF<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 initially registers the pr=
ofile of its own capabilities into the<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0 system in order for themselves to be available in the system.=C2=A0 In<=
br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 addition, the Security Controller is =
validated by the I2NSF Client<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 (also c=
alled I2NSF User) that the user is employing, so that the user<br>&gt;=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0 can request security services through the Secur=
ity Controller.<br><br>In this case the user is the system administrator.<b=
r><br><br>S 1.<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 [RFC7149] to provide d=
ifferent security functionality such as<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0 firewalls [opsawg-firewalls], Deep Packet Inspection (DPI), and<br>&gt;=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Distributed Denial of Service (DDoS) attack =
mitigation; (iv) the use<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 of NFV as su=
pporting technology.=C2=A0 The implementation of I2NSF in<br>&gt;=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0 these scenarios has allowed us to verify the applicab=
ility and<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 effectiveness of the I2NSF =
framework for a variety of use cases.<br><br>This would be easier to read w=
ith a standard bulleted list.<br><br><br>S 2.<br>&gt;=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0 network resources, which facilitates the design=
, delivery and<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 oper=
ation of network services in a dynamic and scalable manner<br>&gt;=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 [ITU-T.Y.3300].<br>&gt;=C2=A0=C2=A0=
 <br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 o=C2=A0 Firewall: A service functio=
n at the junction of two network<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0 segments that inspects every packet that attempts to cross =
the<br><br>Nit: It might not inspect *every* packet.<br><br><br>S 4.<br>&gt=
;=C2=A0=C2=A0 <br>&gt;=C2=A0=C2=A0 4.=C2=A0 Time-dependent Web Access Contr=
ol Service<br>&gt;=C2=A0=C2=A0 <br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 This =
service scenario assumes that an enterprise network<br>&gt;=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0 administrator wants to control the staff members&#39; acces=
s to a<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 particular Interner service (e=
.g., Example.com) during business<br><br>Nit: &quot;Internet&quot;<br><br><=
br>S 4.<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 inspection capability is requ=
ired to check whether the target URL of<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0 a received packet is in the Example.com domain or not.<br>&gt;=C2=A0=C2=
=A0 <br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 The Security Controller maintain=
s the security capabilities of each<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 N=
SF running in the I2NSF system, which have been reported by the<br>&gt;=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0 Developer&#39;s Management System via the Regis=
tation interface.=C2=A0 Based<br><br>Nit: &quot;Registration&quot;<br><br><=
br>S 4.<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 currently using the network.=
=C2=A0 Based on the retrieved information, the<br>&gt;=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0 Security Controller generates low-level security rules to check<b=
r>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 whether the source IP address of a rec=
eived packet matches any one<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 being us=
ed by a staff member.=C2=A0 In addition, the low-level security<br>&gt;=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0 rules should be able to determine that a receiv=
ed packet is of HTTP<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 protocol.=C2=A0 =
The low-level security rules for web filter checks that<br><br>Nit: &quot;r=
ules&quot;... &quot;checks&quot; disagree.<br><br><br>S 6.<br>&gt;=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0 translated into their packet forwarding rules, wherea=
s NSFs enforce<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 NSF-related security r=
ules requiring the security capabilities of the<br>&gt;=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0 NSFs.=C2=A0 For this purpose, the Security Controller instruct=
s the SDN<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Controller via NSF-Facing I=
nterface so that SDN forwarding elements<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0 can perform the required security services with flow tables under the<b=
r>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 supervision of the SDN Controller.<br>=
<br>I&#39;m having some trouble understanding the difference here between N=
SFs<br>and SDN elements. They both seem to be software controlled network<b=
r>elements. Is this just some continuum about CPU power?<br><br><br>S 6.<br=
>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 can perform the required security servi=
ces with flow tables under the<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 superv=
ision of the SDN Controller.<br>&gt;=C2=A0=C2=A0 <br>&gt;=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0 As an example, let us consider two different types of security=
 rules:<br>&gt;=C2=A0=C2=A0 <br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Rule A i=
s a simple packet fltering rule that checks only the IP<br><br>Nit: &quot;f=
iltering&quot;<br><br><br>S 6.2.<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0 packets that have the same call-id.<br>&gt;=C2=A0=C2=
=A0 <br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 6.=C2=A0 The SDN Controller inst=
alls new rules (e.g., drop packets) into<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0 underlying switches.<br>&gt;=C2=A0=C2=A0 <br>&g=
t;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 7.=C2=A0 The illegal packets are dropped b=
y these switches.<br><br>&quot;Illegal&quot; is probably the wrong wrod her=
e.<br><br><br>S 6.3.<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0 is helpful to determine security policies for such a network.<br>&gt;=
=C2=A0=C2=A0 <br>&gt;=C2=A0=C2=A0 6.3.=C2=A0 Attack Mitigation: Centralized=
 DDoS-attack Mitigation System<br>&gt;=C2=A0=C2=A0 <br>&gt;=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0 A centralized DDoS-attack mitigation can manage each networ=
k resource<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 and manipulate rules to ea=
ch switch through a common server for DDoS-<br><br>&quot;manipulate rules t=
o&quot; is not grammatical.<br><br><br>S 6.3.<br>&gt;=C2=A0=C2=A0 <br>&gt;=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Servers are categorized into stateless serve=
rs (e.g., DNS servers)<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 and stateful s=
ervers (e.g., web servers).=C2=A0 For DDoS-attack<br>&gt;=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0 mitigation, traffic flows in switches are dynamically configur=
ed by<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 traffic flow forwarding path ma=
nagement according to the category of<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
 servers [AVANT-GUARD].=C2=A0 Such a managenent should consider the load<br=
><br>1. This seems hard to understand without this reference, which is not<=
br>public.<br>2. &quot;management&quot;<br><br><br>S 6.3.<br>&gt;=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0 mitigation, traffic flows in switches are dynamically=
 configured by<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 traffic flow forwardin=
g path management according to the category of<br>&gt;=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0 servers [AVANT-GUARD].=C2=A0 Such a managenent should consider th=
e load<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 balance among the switches for=
 the defense against DDoS attacks.<br>&gt;=C2=A0=C2=A0 <br>&gt;=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0 The procedure of DDoS-attack mitigation operations in th=
is system is<br><br>&quot;procedure of... operations&quot; is ungrammatical=
<br><br></div></div>
</blockquote></div><br clear=3D"all"><div><br></div>-- <br><div dir=3D"ltr"=
 class=3D"gmail-m_-4645637776060181596gmail-m_7571128782014320286m_-6695152=
896369925623gmail-m_-607987677208405722gmail-m_-9111533177071645325gmail_si=
gnature"><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 Pr=
ofessor<br>Department of Software<br>Sungkyunkwan University<br>Office: +82=
-31-299-4957<br>Email: <a href=3D"mailto:jaehoon.paul@gmail.com" rel=3D"nor=
eferrer" target=3D"_blank">jaehoon.paul@gmail.com</a><br>Personal Homepage:=
 <a href=3D"http://cpslab.skku.edu/people-jaehoon-jeong.php" rel=3D"norefer=
rer" 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-m_-4645637776060181596gmail-m_7571128782014320286m_-6695152=
896369925623gmail_signature"><div dir=3D"ltr"><div><div dir=3D"ltr"><div><d=
iv 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 Software<br>Sungkyunkwan Univ=
ersity<br>Office: +82-31-299-4957<br>Email: <a href=3D"mailto:jaehoon.paul@=
gmail.com" rel=3D"noreferrer" target=3D"_blank">jaehoon.paul@gmail.com</a>,=
=C2=A0<a href=3D"mailto:pauljeong@skku.edu" style=3D"font-size:12.8px" rel=
=3D"noreferrer" target=3D"_blank">pauljeong@skku.edu</a><br>Personal Homepa=
ge: <a href=3D"http://cpslab.skku.edu/people-jaehoon-jeong.php" rel=3D"nore=
ferrer" target=3D"_blank">http://iotlab.skku.edu/people-jaehoon-jeong.php</=
a><br></div></div></div></div></div></div></div></div></div></div></div></d=
iv></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 Software<br>Sungkyunkwan Univers=
ity<br>Office: +82-31-299-4957<br>Email: <a href=3D"mailto:jaehoon.paul@gma=
il.com" target=3D"_blank">jaehoon.paul@gmail.com</a>,=C2=A0<a href=3D"mailt=
o:pauljeong@skku.edu" style=3D"font-size:12.8px" target=3D"_blank">pauljeon=
g@skku.edu</a><br>Personal Homepage: <a href=3D"http://cpslab.skku.edu/peop=
le-jaehoon-jeong.php" target=3D"_blank">http://iotlab.skku.edu/people-jaeho=
on-jeong.php</a><br></div></div></div></div></div></div></div></div></div><=
/div></div></div>

--000000000000b7e5a0057e0c8fa8--


From nobody Fri Dec 28 06:09:09 2018
Return-Path: <ekr@rtfm.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 08043126BED for <i2nsf@ietfa.amsl.com>; Fri, 28 Dec 2018 06:09:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=rtfm-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 AqEfGIVTIwNK for <i2nsf@ietfa.amsl.com>; Fri, 28 Dec 2018 06:09:02 -0800 (PST)
Received: from mail-lf1-x131.google.com (mail-lf1-x131.google.com [IPv6:2a00:1450:4864:20::131]) (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 A87FF12426A for <i2nsf@ietf.org>; Fri, 28 Dec 2018 06:09:01 -0800 (PST)
Received: by mail-lf1-x131.google.com with SMTP id v5so14619916lfe.7 for <i2nsf@ietf.org>; Fri, 28 Dec 2018 06:09:01 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rtfm-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=sqA4Rh39VrhG62YV7gxAwAQboEFWwwJTj1olNSDYFKA=; b=RsDzpx+sTtGLrgByk8Q0kHc0LagtaR2tRVrRxOu6X1yufOpAVVNpvLAq38g3bUQQ3k aymanu+l5fGHFKmBCbYrPjVCi/XkhIVo7NosfsQSpD+ZquZACT7vkuCYqxi+9lyxx6hm En4cUPPprxbdOUQ7wvW4KrmxM7gPMFx18VIsXCNkNoslALQgow+UCMcKf9IEVmxArEGa uWiAlFkPKlA+MB9Ugp4ENUbTOAp63v+YSgm6k4kEH3P+MtJ7gqRKeqwmygmM9HQaou4J hcFBduXyEgEfDVQ7l/W1GAu+zkvmsQkp+1XSSybDoSsv4PsGkxxP6PU6Mg+nFo/dWU1H 24Kg==
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=sqA4Rh39VrhG62YV7gxAwAQboEFWwwJTj1olNSDYFKA=; b=VJnBMVlJ5XvPnlJtZLI5ZISMwgFRkH6lINjlSk8Hr1L1A7WOoXKFoMdtPvgoAjNLeD b1IRoOREdOZW+k8ZSQ1290nxqEQLG5f3isTV7FjzqHFLpnrQzU2a5CedZFY1EOXjnXAw AtiqbQplJi6NYfXeLFUzM2FQsxiQFfyFvJnucEgfifA+ih2UKtA6FzCoVNlJH9ZRUuzw 9xA7j/THr/pnLXnTaLejVNFcrOYH3Jadd/m5liO0LY5ESpv4bQBQWUZdxGdTuTFjFe0k OwbkHuMEyjWrb2TCFzO1POM0xGURgb55eX5p1xoEuo/bGP84YKNBGzYCAzmKQI6QwIBg 7hDg==
X-Gm-Message-State: AA+aEWZbksS2nJRvGlqqpoTK8CWUkXuC1/X5aEBqMRzafWp50/DhK9Nu p3fH5qzIYH9Y5r6ImG4b31IMJ2A/BaETTz5buRd1oA==
X-Google-Smtp-Source: AFSGD/WfBLTGSKyZiBZ8Mkg7gJBoElBStyCjayEMEwy3fd73onBIvLSsRCdaSX9QjQPwmGttamHkaodUu8fizYFyBuk=
X-Received: by 2002:a19:ca51:: with SMTP id h17mr13234276lfj.126.1546006139480;  Fri, 28 Dec 2018 06:08:59 -0800 (PST)
MIME-Version: 1.0
References: <CABcZeBOjhEpw4gNDRgJD=FCWy1Wrirz_EsJefJjDHpp5mVe1fw@mail.gmail.com> <CAPK2DewE2vbjAr41xErxnjmxK2CTmK2h9fXFTBSFCigpNj9XPQ@mail.gmail.com> <CABcZeBNZhqTawAFcj9p01ig-tE=XaFm5yCXuGJQFiqoOGgNZxA@mail.gmail.com> <CAPK2Dex7hbKC3Cpq2Jy+UXr7YFqgjGUGvzNiSYMix7M5qQhx=w@mail.gmail.com> <CABcZeBMyRGZ5QEwxLQRkcrkz665vWgOFPv+dwAuF5HSg1=B6eA@mail.gmail.com> <CAPK2Deyn1=vVShbq=hMRmvQ1=G5_Yew8pYgqQC=Vh-dG9d2Wrg@mail.gmail.com>
In-Reply-To: <CAPK2Deyn1=vVShbq=hMRmvQ1=G5_Yew8pYgqQC=Vh-dG9d2Wrg@mail.gmail.com>
From: Eric Rescorla <ekr@rtfm.com>
Date: Fri, 28 Dec 2018 06:08:18 -0800
Message-ID: <CABcZeBPd2B5QB0-+eJ5z77rACvTLTTpZRrRKBrCAZHdBCFurGw@mail.gmail.com>
To: "Mr. Jaehoon Paul Jeong" <jaehoon.paul@gmail.com>
Cc: Linda Dunbar <linda.dunbar@huawei.com>, Yoav Nir <ynir.ietf@gmail.com>,  DIEGO LOPEZ GARCIA <diego.r.lopez@telefonica.com>, "i2nsf@ietf.org" <i2nsf@ietf.org>, skku_secu-brain_all@googlegroups.com
Content-Type: multipart/alternative; boundary="000000000000c3c1cb057e159a63"
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2nsf/Xc92QkEPgRWC3FKuRvnaiNNFY2o>
Subject: Re: [I2nsf] AD Review of draft-ietf-i2nsf-applicability-07
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, 28 Dec 2018 14:09:07 -0000

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

On Thu, Dec 27, 2018 at 7:21 PM Mr. Jaehoon Paul Jeong <
jaehoon.paul@gmail.com> wrote:

> Eric,
> Let me answer your further questions below.
>
> On Thu, Dec 27, 2018 at 11:59 PM Eric Rescorla <ekr@rtfm.com> wrote:
>
>>
>>
>> On Wed, Dec 26, 2018 at 6:42 PM Mr. Jaehoon Paul Jeong <
>> jaehoon.paul@gmail.com> wrote:
>>
>>> Hi Eric,
>>> Here are my answers inlines below.
>>>
>>> On Thu, Dec 27, 2018 at 3:44 AM Eric Rescorla <ekr@rtfm.com> wrote:
>>>
>>>> Paul,
>>>>
>>>> Thanks for your new version. Some responses below.
>>>>
>>>>
>>>> On Tue, Dec 25, 2018 at 6:42 AM Mr. Jaehoon Paul Jeong <
>>>> jaehoon.paul@gmail.com> wrote:
>>>>
>>>>> Hi Eric, Linda and Yoav,
>>>>> I have reflected all the comments from Eric and submitted the revision
>>>>> -08 as follows:
>>>>> https://tools.ietf.org/html/draft-ietf-i2nsf-applicability-08
>>>>>
>>>>> The changes are described in Appendix A of -08 document as follows:
>>>>>
>>>>> -------------------------------------------------------------------------------------------------
>>>>> Appendix A.  Changes from draft-ietf-i2nsf-applicability-07
>>>>>
>>>>>    The following changes have been made from
>>>>>    draft-ietf-i2nsf-applicability-07:
>>>>>
>>>>>    o  This version has reflected all the comments from Eric Rescorla
>>>>> who
>>>>>       is a Security Area Director as follows.
>>>>>
>>>>>    o  In Section 1, Network Security Function (NFV) is defined in the
>>>>>       viewpoint of the I2NSF framework.
>>>>>
>>>>>    o  In Section 1, a user using the I2NSF User is clarified as a
>>>>> system
>>>>>       administrator in the I2NSF framework.
>>>>>
>>>>>    o  In Section 1, as the applicability of the I2NSF framework, four
>>>>>       different scenarios are represented with a standard bulleted
>>>>> list.
>>>>>
>>>>>    o  The standard document about ETSI-NFV is moved to Normative
>>>>>       References.
>>>>>
>>>>>    o  In Section 2, key terms (e.g., Network Function, Network Security
>>>>>       Function, Network Functions Virtualization, and Servive Function
>>>>>       Chaining) are internally defined along with the reference to open
>>>>>       specifications.
>>>>>
>>>>>    o  In Section 2, the definition of Firewall is corrected such that
>>>>>       some suspicious packets are inspected by the firewall rather than
>>>>>       every packet.
>>>>>
>>>>>    o  In Section 3, for a Developer's Management System, the problem of
>>>>>       an inside attacker is addressed, and a possible solution for the
>>>>>       inside attacks is suggested through I2NSF NSF monitoring
>>>>>       functionality.
>>>>>
>>>>
>>>> I'm still pretty concerned about this. Standardizing a situation in
>>>> which the
>>>> developer of your firewall has real-time management-level access to
>>>> that firewall seems extremely insecure, especially when that access is
>>>> authenticated via conventional credentials that are online as part of
>>>> the transaction (as opposed to software builds which can be signed
>>>> offline). This doesn't seem like a best practice. Why is it necessary?
>>>>
>>>
>>>
>>>>  =>  The developer of a firewall does not have real-time
>>> management-level access
>>>        even though its management system works the control plane as part
>>> of the I2NSF system.
>>>        The developer's management system provides the Security
>>> Controller with
>>>        the interface (i.e., Registration Interface) that is used to
>>> register the capability of
>>>        the developer's security network function (i.e., firewall), to
>>> search an NSF for the required capability for a high-level security policy,
>>> and to help the lifecycle management
>>>        of such an NSF for the Security Controller through an NFV
>>> interface (i.e., Ve-Vnfm interface) with the NFV's MANO.
>>>
>>
>> I don't understand the distinction you are drawing here. Under what
>> conditions can the developer modify the behavior of the I2NSF system? Can
>> it do so at any time and without explicit action by the admin.
>>
>>  =>  The developer means a security solution vendor (e.g., McAfee and
> Symantec) who provides the I2NSF system with security solutions,
>        such as firewall, web filter, DPI, IDS/IPS, and DDoS-attack
> mitigator. Actually, the developer's management system
>        cannot modify the behavior of the I2NSF system in run-time as long
> as the vendor doesn't have any backdoor to
>        their developer's management system.
>        This developer's management system facilitates the security service
> government by the Security Controller
>        by providing the Security Controller with the Registration
> Interface for the capability registration and
> instantiation/de-instantiation
>        of the image of a security service function.
>        Thus, only the administrator can modify the behavior of the I2NSF
> system.
>
>        Maybe,
>        Diego Lopez can clarify my answer because he is the editor of RFC
> 8329 (Framework for Interface to Network Security Functions):
>        https://tools.ietf.org/html/rfc832
> <https://tools.ietf.org/html/rfc8329>
>

Yeah, I'm not really following this. What functions can the Developer
perform on the system.


   o  In Section 4, an XML file for the RESTCONF/YANG for the time-
>>>>>       dependent web access control is pointed out with a reference to
>>>>>       the Consumer-Facing Interface's data model
>>>>>       [consumer-facing-inf-dm].
>>>>>
>>>>
>>>> I didn't follow this change. The example you give of a high level
>>>> security
>>>> policy is clearly freeform text and then you talk about XML. Is this
>>>> just
>>>> example a summary of the semantics of something which would actually be
>>>> an
>>>> XML file? Something else?
>>>>
>>>
>>>   => Even though the high-level security policy looks like a freeform
>>> text,  it is formatted
>>>       in an XML according to the high-level security policy YANG model
>>> for the Consumer-Facing Interface.
>>>       Yes, it is just an example of a summary of the semantics for such
>>> a high-level security policy,
>>>       which is represented as an XML file.
>>>       Here it an XML file for the web filter from the Consumer-Facing
>>> Interface Data Model document
>>>       (
>>> https://tools.ietf.org/html/draft-ietf-i2nsf-consumer-facing-interface-dm-02
>>> ):
>>>
>>>       You can see the XML file from
>>>
>>> https://tools.ietf.org/html/draft-ietf-i2nsf-consumer-facing-interface-dm-02#page-49
>>>
>>>       <?xml version="1.1" encoding="UTF-8"?>
>>>  <rpc message-id="4" xmlns="urn:ietf:params:xml:ns:restconf:base:1.0">
>>>   <edit-config>
>>>    <target>
>>>     <running/>
>>>    </target>
>>>     <config>
>>>      <i2nsf-cf-interface-wf-req nc:operation="create">
>>>          <policy-wf>
>>>              <rule-wf>
>>>                  <rule-wf-id>03</rule-wf-id>
>>>                  <rule-wf-name>wf-policy-example</rule-wf-name>
>>>                  <rule-wf-date>2018.10.26/14:03:17</rule-wf-date>
>>>                  <event>
>>>                      <event-id>04</event-id>
>>>                      <event-name>wf</event-name>
>>>                      <event-date>2018.10.26/14:03:17</event-date>
>>>                      <event-type>wf</event-type>
>>>                      <event-map-group>04</event-map-group>
>>>                      <enable>True</enable>
>>>                  </event>
>>>                  <condition>
>>>                      <condition-id>04</condition-id>
>>>                      <source-ip>192.168.1.3</source-ip>
>>>                      <destination-url>www.facebook.com</destination-url>
>>>                      <time-information>
>>>                          <begin-time>09:00</begin-time>
>>>                          <end-time>18:00</end-time>
>>>                      </time-information>
>>>                      <match-direction>default</match-direction>
>>>                      <exeption>00</exeption>
>>>                  </condition>
>>>                  <action>
>>>                      <action-id>04</action-id>
>>>                      <action-name>action-wf</action-name>
>>>                      <action-date>2018.10.26/14:03:17</action-date>
>>>                      <primary-action>REJECT</primary-action>
>>>                      <secondary-action>LOG</secondary-action>
>>>                  </action>
>>>                  <precedence>none</precedence>
>>>                <owner>
>>>                  <owner-id>03</owner-id>
>>>                  <name>i2nsf-admin</name>
>>>                </owner>
>>>              </rule-wf>
>>>          </policy-wf>
>>>      </i2nsf-cf-interface-wf-req>
>>>     </config>
>>>   </edit-config>
>>>  </rpc>
>>>   => In the above, source ip is used for the employees.
>>>   Instead of the source ip, we can make and use "source group" for
>>> employees that can be translated
>>>   into a set of IP addresses of the source group.
>>>
>>
>> You need to make this clear, then. It would probably be easier to just
>> show the XML and then provide the text summary.
>>
>>   => Okay. I will include a simplified example XML code for web filter
> and provide the text summary as below.
>
>    This service scenario assumes that an enterprise network
>    administrator wants to control the staff members' access to a
>    particular Internet service (e.g., Example.com) during business
>    hours.  The following is an example high-level security policy rule
>    for a web filter that the administrator requests: Block the staff
> members' access to Example.com from 9 AM to 6 PM.
>    Here is an example XML code for this web filter:
> <I2NSF>
>     <name>block_website</name>
>         <cond>
>             <src>Staff_Member's_PC</src>
>             <dest>Example.com</dest>
>     <time-span-start>9:00AM</time-span-start>
>             <time-span-end>-6:00PM</time-span-end>
>         </cond>
>         <action>block<action>
> </I2NSF>
>
>    The security policy name is "bloc_website" with the tag "name".
>    The filtering condition has the source group "Staff_Member's_PC" with
> the tag "src",
>    the destination website "Example.com" with the tag "dest",
>    the filtering start time is the time "9:00AM" with the tag "
> time-span-start",
>    and the filtering end time is the time "6:00PM" with the tag "
> time-span-end".
>    The action is to "block" the packets satisfying the above condition,
>    that is, to drop those packets
>

LGTM.



>
>>
>>    o  In Section 6, the definitions of an SDN forwarding element and an
>>>>>       NSF are clarified such that an SDN forwarding element is a switch
>>>>>       running as either a hardware middle box or a software virtual
>>>>>       switch, and an NSF is a virtual network function for a security
>>>>>       service.
>>>>>
>>>>
>>>> This wasn't clear to me either. Based on this text it would seem that
>>>> you could run an NSF on an SDN element, so it's not clear why they
>>>> are disjoint sets. Can you give me more information here?
>>>>
>>>
>>>  => An SDN switch can run as a virtual network function like an NSF, but
>>> the main functionality of the SDN switch is packet forwarding with a flow
>>> table along with simple filtering rules. More complicated security services
>>> can be done at dedicated NSFs. For example, there is the Open Virtual
>>> Switch (OVS) project for such a software-based SDN switch:
>>> https://www.openvswitch.org
>>>
>>> Thus, the SDN switches and NSFs are logically disjoint sets though all
>>> of them  can run physically as virtual network functions.
>>>
>>
>> I'm sorry, this still isn't clear, at least to me. How can I look at a
>> given software element and determine whether it's an NSF or a virtualized
>> SDN switch?
>>
>
>  => The distinction is logically done such that the NFV system having the
> I2NSF system categorizes some VNFs as NSFs for dedicated security services
>       and some VNFs as virtualized SDN switches for packet switching and
> simple filtering rule enforcement.
>
>      If there is an expert in the NFV, please let us know for further
> clarification.
>

I'm not following this either, so that would definitely help.

-Ekr


>      Thanks.
>
>      Best Regards,
>      Paul
>
>
>>
>> -Ekr
>>
>>>
>>> If you have further questions, please let me know.
>>>
>>> Thanks.
>>>
>>> Best Regards,
>>> Paul
>>>
>>>>
>>>> -Ekr
>>>>
>>>>
>>>>>    o  In Section 6.3, a flow forwarding path management scheme in
>>>>>       [AVANT-GUARD] is described in a self-contained way as follows.
>>>>>       For DDoS-attack mitigation, the forwarding of traffic flows in
>>>>>       switches can be dynamically configured such that malicious
>>>>> traffic
>>>>>       flows are handled by the paths separated from normal traffic
>>>>> flows
>>>>>       in order to minimize the impact of those malicious traffic on the
>>>>>       the servers.  This flow path separation can be done by a flow
>>>>>       forwarding path management scheme based on [AVANT-GUARD].
>>>>>
>>>>>    o  Some typos are corrected such as "Interner -> Internet",
>>>>>       "Registation -> Registration", "The low-level security rules for
>>>>>       web filter checks -> The low-level security rules for web filter
>>>>>       check", "fltering -> filtering", "illegal packets -> malicious
>>>>>       packets", "manipulate rules -> configure rules", "managenent ->
>>>>>       management", and "DDoS-attack mitigation operations ->
>>>>> DDoS-attack
>>>>>       mitigation".
>>>>>
>>>>> -------------------------------------------------------------------------------------------------
>>>>>
>>>>> Thanks and Merry Christmas!
>>>>>
>>>>> Best Regards,
>>>>> Paul
>>>>>
>>>>> On Fri, Dec 21, 2018 at 11:33 PM Eric Rescorla <ekr@rtfm.com> wrote:
>>>>>
>>>>>> Rich version of this review at:
>>>>>> https://mozphab-ietf.devsvcdev.mozaws.net/D3181
>>>>>>
>>>>>>
>>>>>> I found a number of typographical and grammar errors. Please give this
>>>>>> document a thorough read.
>>>>>>
>>>>>> IMPORTANT
>>>>>> S 1.
>>>>>> >
>>>>>> >      Interface to Network Security Functions (I2NSF) defines a
>>>>>> framework
>>>>>> >      and interfaces for interacting with Network Security Functions
>>>>>> >      (NSFs).  The I2NSF framework allows heterogeneous NSFs
>>>>>> developed by
>>>>>> >      different security solution vendors to be used in the Network
>>>>>> >      Functions Virtualization (NFV) environment [ETSI-NFV] by
>>>>>> utilizing
>>>>>>
>>>>>> Much of this document cannot be understood without reading ETSI-NFV,
>>>>>> so it has to be a normative reference. It also would be helpful to
>>>>>> provide a link.
>>>>>>
>>>>>>
>>>>>> S 2.
>>>>>> >      This document uses the terminology described in [RFC7149],
>>>>>> >      [ITU-T.Y.3300], [ONF-OpenFlow], [ONF-SDN-Architecture],
>>>>>> >      [ITU-T.X.1252], [ITU-T.X.800], [RFC8329], [i2nsf-terminology],
>>>>>> >      [consumer-facing-inf-im], [consumer-facing-inf-dm],
>>>>>> >      [i2nsf-nsf-cap-im], [nsf-facing-inf-dm],
>>>>>> [registration-inf-dm], and
>>>>>> >      [nsf-triggered-steering].  In addition, the following terms are
>>>>>>
>>>>>> Every term in this document needs to be understandable without
>>>>>> reference to closed specifications or internally defined. Please
>>>>>> ensure that this is so,
>>>>>>
>>>>>>
>>>>>> S 3.
>>>>>> >      used for the I2NSF NSF-Facing Interface.
>>>>>> >
>>>>>> >      The Registration Interface between the Security Controller and
>>>>>> the
>>>>>> >      Developer's Management System can be implemented by RESTCONF
>>>>>> >      [RFC8040].  The data model defined in [registration-inf-dm]
>>>>>> can be
>>>>>> >      used for the I2NSF Registration Interface.
>>>>>>
>>>>>> What role does the Developer's Management System play in this? I think
>>>>>> this refers to the text above starting with "The developers (or
>>>>>> vendors)...". Is that correct?
>>>>>>
>>>>>> Assuming I am correct, this seems like a potentially serious security
>>>>>> vulnerability in this design in that it potentially allows an inside
>>>>>> attacker at the developer to seriously weaken a system's security.
>>>>>> What protections exist to prevent this?
>>>>>>
>>>>>>
>>>>>> S 4.
>>>>>> >      administrator wants to control the staff members' access to a
>>>>>> >      particular Interner service (e.g., Example.com) during business
>>>>>> >      hours.  The following is an example high-level security policy
>>>>>> rule
>>>>>> >      that the administrator requests: Block the staff members'
>>>>>> access to
>>>>>> >      Example.com from 9 AM to 6 PM.  The administrator sends this
>>>>>> high-
>>>>>> >      level security policy to the Security Controller, then the
>>>>>> Security
>>>>>>
>>>>>> The text above suggests that high-level policies are via
>>>>>> RESTCONF/YANG, but this is clearly freeform text.
>>>>>> COMMENTS
>>>>>> S 1.
>>>>>> >
>>>>>> >   1.  Introduction
>>>>>> >
>>>>>> >      Interface to Network Security Functions (I2NSF) defines a
>>>>>> framework
>>>>>> >      and interfaces for interacting with Network Security Functions
>>>>>> >      (NSFs).  The I2NSF framework allows heterogeneous NSFs
>>>>>> developed by
>>>>>>
>>>>>> Please define "Network Security Functions" here.
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> S 1.
>>>>>> >      functions in the NFV platform.  In the I2NSF framework, each
>>>>>> NSF
>>>>>> >      initially registers the profile of its own capabilities into
>>>>>> the
>>>>>> >      system in order for themselves to be available in the system.
>>>>>> In
>>>>>> >      addition, the Security Controller is validated by the I2NSF
>>>>>> Client
>>>>>> >      (also called I2NSF User) that the user is employing, so that
>>>>>> the user
>>>>>> >      can request security services through the Security Controller.
>>>>>>
>>>>>> In this case the user is the system administrator.
>>>>>>
>>>>>>
>>>>>> S 1.
>>>>>> >      [RFC7149] to provide different security functionality such as
>>>>>> >      firewalls [opsawg-firewalls], Deep Packet Inspection (DPI), and
>>>>>> >      Distributed Denial of Service (DDoS) attack mitigation; (iv)
>>>>>> the use
>>>>>> >      of NFV as supporting technology.  The implementation of I2NSF
>>>>>> in
>>>>>> >      these scenarios has allowed us to verify the applicability and
>>>>>> >      effectiveness of the I2NSF framework for a variety of use
>>>>>> cases.
>>>>>>
>>>>>> This would be easier to read with a standard bulleted list.
>>>>>>
>>>>>>
>>>>>> S 2.
>>>>>> >         network resources, which facilitates the design, delivery
>>>>>> and
>>>>>> >         operation of network services in a dynamic and scalable
>>>>>> manner
>>>>>> >         [ITU-T.Y.3300].
>>>>>> >
>>>>>> >      o  Firewall: A service function at the junction of two network
>>>>>> >         segments that inspects every packet that attempts to cross
>>>>>> the
>>>>>>
>>>>>> Nit: It might not inspect *every* packet.
>>>>>>
>>>>>>
>>>>>> S 4.
>>>>>> >
>>>>>> >   4.  Time-dependent Web Access Control Service
>>>>>> >
>>>>>> >      This service scenario assumes that an enterprise network
>>>>>> >      administrator wants to control the staff members' access to a
>>>>>> >      particular Interner service (e.g., Example.com) during business
>>>>>>
>>>>>> Nit: "Internet"
>>>>>>
>>>>>>
>>>>>> S 4.
>>>>>> >      inspection capability is required to check whether the target
>>>>>> URL of
>>>>>> >      a received packet is in the Example.com domain or not.
>>>>>> >
>>>>>> >      The Security Controller maintains the security capabilities of
>>>>>> each
>>>>>> >      NSF running in the I2NSF system, which have been reported by
>>>>>> the
>>>>>> >      Developer's Management System via the Registation interface.
>>>>>> Based
>>>>>>
>>>>>> Nit: "Registration"
>>>>>>
>>>>>>
>>>>>> S 4.
>>>>>> >      currently using the network.  Based on the retrieved
>>>>>> information, the
>>>>>> >      Security Controller generates low-level security rules to check
>>>>>> >      whether the source IP address of a received packet matches any
>>>>>> one
>>>>>> >      being used by a staff member.  In addition, the low-level
>>>>>> security
>>>>>> >      rules should be able to determine that a received packet is of
>>>>>> HTTP
>>>>>> >      protocol.  The low-level security rules for web filter checks
>>>>>> that
>>>>>>
>>>>>> Nit: "rules"... "checks" disagree.
>>>>>>
>>>>>>
>>>>>> S 6.
>>>>>> >      translated into their packet forwarding rules, whereas NSFs
>>>>>> enforce
>>>>>> >      NSF-related security rules requiring the security capabilities
>>>>>> of the
>>>>>> >      NSFs.  For this purpose, the Security Controller instructs the
>>>>>> SDN
>>>>>> >      Controller via NSF-Facing Interface so that SDN forwarding
>>>>>> elements
>>>>>> >      can perform the required security services with flow tables
>>>>>> under the
>>>>>> >      supervision of the SDN Controller.
>>>>>>
>>>>>> I'm having some trouble understanding the difference here between NSFs
>>>>>> and SDN elements. They both seem to be software controlled network
>>>>>> elements. Is this just some continuum about CPU power?
>>>>>>
>>>>>>
>>>>>> S 6.
>>>>>> >      can perform the required security services with flow tables
>>>>>> under the
>>>>>> >      supervision of the SDN Controller.
>>>>>> >
>>>>>> >      As an example, let us consider two different types of security
>>>>>> rules:
>>>>>> >
>>>>>> >      Rule A is a simple packet fltering rule that checks only the IP
>>>>>>
>>>>>> Nit: "filtering"
>>>>>>
>>>>>>
>>>>>> S 6.2.
>>>>>> >          packets that have the same call-id.
>>>>>> >
>>>>>> >      6.  The SDN Controller installs new rules (e.g., drop packets)
>>>>>> into
>>>>>> >          underlying switches.
>>>>>> >
>>>>>> >      7.  The illegal packets are dropped by these switches.
>>>>>>
>>>>>> "Illegal" is probably the wrong wrod here.
>>>>>>
>>>>>>
>>>>>> S 6.3.
>>>>>> >         is helpful to determine security policies for such a
>>>>>> network.
>>>>>> >
>>>>>> >   6.3.  Attack Mitigation: Centralized DDoS-attack Mitigation System
>>>>>> >
>>>>>> >      A centralized DDoS-attack mitigation can manage each network
>>>>>> resource
>>>>>> >      and manipulate rules to each switch through a common server
>>>>>> for DDoS-
>>>>>>
>>>>>> "manipulate rules to" is not grammatical.
>>>>>>
>>>>>>
>>>>>> S 6.3.
>>>>>> >
>>>>>> >      Servers are categorized into stateless servers (e.g., DNS
>>>>>> servers)
>>>>>> >      and stateful servers (e.g., web servers).  For DDoS-attack
>>>>>> >      mitigation, traffic flows in switches are dynamically
>>>>>> configured by
>>>>>> >      traffic flow forwarding path management according to the
>>>>>> category of
>>>>>> >      servers [AVANT-GUARD].  Such a managenent should consider the
>>>>>> load
>>>>>>
>>>>>> 1. This seems hard to understand without this reference, which is not
>>>>>> public.
>>>>>> 2. "management"
>>>>>>
>>>>>>
>>>>>> S 6.3.
>>>>>> >      mitigation, traffic flows in switches are dynamically
>>>>>> configured by
>>>>>> >      traffic flow forwarding path management according to the
>>>>>> category of
>>>>>> >      servers [AVANT-GUARD].  Such a managenent should consider the
>>>>>> load
>>>>>> >      balance among the switches for the defense against DDoS
>>>>>> attacks.
>>>>>> >
>>>>>> >      The procedure of DDoS-attack mitigation operations in this
>>>>>> system is
>>>>>>
>>>>>> "procedure of... operations" is ungrammatical
>>>>>>
>>>>>>
>>>>>
>>>>> --
>>>>> ===========================
>>>>> Mr. Jaehoon (Paul) Jeong, Ph.D.
>>>>> Associate Professor
>>>>> Department of Software
>>>>> Sungkyunkwan University
>>>>> Office: +82-31-299-4957
>>>>> Email: jaehoon.paul@gmail.com
>>>>> 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 Software
>>> 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 Software
> 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>
>

--000000000000c3c1cb057e159a63
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">On Thu, Dec 27, 2018 at 7:21 PM Mr. Jaehoon Paul Jeong &lt=
;<a href=3D"mailto:jaehoon.paul@gmail.com">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"><div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr"><div>Eric,</div=
><div>Let me answer your further questions below.</div><br><div class=3D"gm=
ail_quote"><div dir=3D"ltr">On Thu, Dec 27, 2018 at 11:59 PM Eric Rescorla =
&lt;<a href=3D"mailto:ekr@rtfm.com" target=3D"_blank">ekr@rtfm.com</a>&gt; =
wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0=
px 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">On Wed, Dec 26, 2018 at 6:42 PM Mr. Jaehoon Paul Jeong &lt;<a href=
=3D"mailto: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 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">=
<div dir=3D"auto"><div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr"><div d=
ir=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr"><div>Hi Eric,</div><div dir=3D=
"auto">Here are my answers inlines below.</div><br><div class=3D"gmail_quot=
e"><div dir=3D"ltr">On Thu, Dec 27, 2018 at 3:44 AM Eric Rescorla &lt;<a hr=
ef=3D"mailto:ekr@rtfm.com" rel=3D"noreferrer" target=3D"_blank">ekr@rtfm.co=
m</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"><div>Paul,</div><div><br></div><div>Than=
ks for your new version. Some responses below.<br></div><div><br></div></di=
v><br><div class=3D"gmail_quote"><div dir=3D"ltr">On Tue, Dec 25, 2018 at 6=
:42 AM Mr. Jaehoon Paul Jeong &lt;<a href=3D"mailto:jaehoon.paul@gmail.com"=
 rel=3D"noreferrer" target=3D"_blank">jaehoon.paul@gmail.com</a>&gt; wrote:=
<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8=
ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr=
"><div dir=3D"ltr"><div dir=3D"ltr">Hi Eric, Linda and Yoav,<div>I have ref=
lected all the comments from Eric and submitted the revision -08 as follows=
:</div><div><a href=3D"https://tools.ietf.org/html/draft-ietf-i2nsf-applica=
bility-08" rel=3D"noreferrer" target=3D"_blank">https://tools.ietf.org/html=
/draft-ietf-i2nsf-applicability-08</a><br></div><div><br></div><div>The cha=
nges are described in Appendix A of -08 document as follows:</div><div>----=
---------------------------------------------------------------------------=
------------------</div><div><div>Appendix A.=C2=A0 Changes from draft-ietf=
-i2nsf-applicability-07</div><div><br></div><div>=C2=A0 =C2=A0The following=
 changes have been made from</div><div>=C2=A0 =C2=A0draft-ietf-i2nsf-applic=
ability-07:</div><div><br></div><div>=C2=A0 =C2=A0o=C2=A0 This version has =
reflected all the comments from Eric Rescorla who</div><div>=C2=A0 =C2=A0 =
=C2=A0 is a Security Area Director as follows.</div><div><br></div><div>=C2=
=A0 =C2=A0o=C2=A0 In Section 1, Network Security Function (NFV) is defined =
in the</div><div>=C2=A0 =C2=A0 =C2=A0 viewpoint of the I2NSF framework.</di=
v><div><br></div><div>=C2=A0 =C2=A0o=C2=A0 In Section 1, a user using the I=
2NSF User is clarified as a system</div><div>=C2=A0 =C2=A0 =C2=A0 administr=
ator in the I2NSF framework.</div><div><br></div><div>=C2=A0 =C2=A0o=C2=A0 =
In Section 1, as the applicability of the I2NSF framework, four</div><div>=
=C2=A0 =C2=A0 =C2=A0 different scenarios are represented with a standard bu=
lleted list.</div><div><br></div><div>=C2=A0 =C2=A0o=C2=A0 The standard doc=
ument about ETSI-NFV is moved to Normative</div><div>=C2=A0 =C2=A0 =C2=A0 R=
eferences.</div><div><br></div><div>=C2=A0 =C2=A0o=C2=A0 In Section 2, key =
terms (e.g., Network Function, Network Security</div><div>=C2=A0 =C2=A0 =C2=
=A0 Function, Network Functions Virtualization, and Servive Function</div><=
div>=C2=A0 =C2=A0 =C2=A0 Chaining) are internally defined along with the re=
ference to open</div><div>=C2=A0 =C2=A0 =C2=A0 specifications.</div><div><b=
r></div><div>=C2=A0 =C2=A0o=C2=A0 In Section 2, the definition of Firewall =
is corrected such that</div><div>=C2=A0 =C2=A0 =C2=A0 some suspicious packe=
ts are inspected by the firewall rather than</div><div>=C2=A0 =C2=A0 =C2=A0=
 every packet.</div><div><br></div><div>=C2=A0 =C2=A0o=C2=A0 In Section 3, =
for a Developer&#39;s Management System, the problem of</div><div>=C2=A0 =
=C2=A0 =C2=A0 an inside attacker is addressed, and a possible solution for =
the</div><div>=C2=A0 =C2=A0 =C2=A0 inside attacks is suggested through I2NS=
F NSF monitoring</div><div>=C2=A0 =C2=A0 =C2=A0 functionality.</div></div><=
/div></div></div></blockquote><div><br></div><div>I&#39;m still pretty conc=
erned about this. Standardizing a situation in which the</div><div>develope=
r of your firewall has real-time management-level access to</div><div>that =
firewall seems extremely insecure, especially when that access is</div><div=
>authenticated via conventional credentials that are online as part of</div=
><div>the transaction (as opposed to software builds which can be signed</d=
iv><div>offline). This doesn&#39;t seem like a best practice. Why is it nec=
essary?</div><div></div></div></div></blockquote></div></div></div></div></=
div></div></div><div dir=3D"auto"><br></div><div dir=3D"ltr"><div dir=3D"lt=
r"><div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr"><div=
 class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margin:0p=
x 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><d=
iv dir=3D"ltr"><div class=3D"gmail_quote"><div><br></div></div></div></bloc=
kquote><div>=C2=A0=3D&gt;=C2=A0 The developer of a firewall does not have r=
eal-time management-level access</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0even =
though its management system works the control plane as part of the I2NSF s=
ystem.</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0The developer&#39;s management =
system provides the Security Controller with</div><div>=C2=A0 =C2=A0 =C2=A0=
 =C2=A0the interface (i.e., Registration Interface) that is used to registe=
r the capability of</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0the developer&#39;=
s security network function (i.e., firewall), to search an NSF for the requ=
ired capability for a high-level security policy, and to help the lifecycle=
 management</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0of such an NSF for the Sec=
urity Controller through an NFV interface (i.e., Ve-Vnfm interface) with th=
e NFV&#39;s MANO.=C2=A0</div></div></div></div></div></div></div></div></di=
v></blockquote><div><br></div><div>I don&#39;t understand the distinction y=
ou are drawing here. Under what conditions can the developer modify the beh=
avior of the I2NSF system? Can it do so at any time and without explicit ac=
tion by the admin.<br></div><div><br></div></div></div></blockquote><div>=
=C2=A0=3D&gt;=C2=A0 The developer means a security solution vendor (e.g., M=
cAfee and Symantec) who provides the I2NSF system with security solutions,=
=C2=A0</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0such as firewall, web filter, D=
PI, IDS/IPS, and DDoS-attack mitigator. Actually, the developer&#39;s manag=
ement system</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0cannot modify the behavio=
r of the I2NSF system in run-time as long as the vendor doesn&#39;t have an=
y backdoor to=C2=A0</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0their developer&#3=
9;s management system.</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0This developer&=
#39;s management system facilitates the security service government by the =
Security Controller=C2=A0</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0by providing=
 the Security Controller with the Registration Interface for the capability=
 registration and instantiation/de-instantiation=C2=A0</div><div>=C2=A0 =C2=
=A0 =C2=A0 =C2=A0of the image of a security service function.</div><div>=C2=
=A0 =C2=A0 =C2=A0 =C2=A0Thus, only the administrator can modify the behavio=
r of the I2NSF system.</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0</div><div>=C2=
=A0 =C2=A0 =C2=A0 =C2=A0Maybe,</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0Diego L=
opez can clarify my answer because he is the editor of RFC 8329 (Framework =
for Interface to Network Security Functions):</div><div>=C2=A0 =C2=A0 =C2=
=A0 =C2=A0<a href=3D"https://tools.ietf.org/html/rfc8329" target=3D"_blank"=
>https://tools.ietf.org/html/rfc832</a></div></div></div></div></div></div>=
</blockquote><div><br></div><div>Yeah, I&#39;m not really following this. W=
hat functions can the Developer perform on the system.</div><div><br></div>=
<br><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;bor=
der-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr"><div=
 dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr"><div class=3D"gmail_quote"><=
blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-l=
eft:1px solid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr"><div clas=
s=3D"gmail_quote"><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 di=
r=3D"auto"><div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"l=
tr"><div dir=3D"ltr"><div dir=3D"ltr"><div class=3D"gmail_quote"><blockquot=
e class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px s=
olid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr"><div class=3D"gmai=
l_quote"><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"ltr"=
><div dir=3D"ltr"><div dir=3D"ltr"><div><div>=C2=A0 =C2=A0o=C2=A0 In Sectio=
n 4, an XML file for the RESTCONF/YANG for the time-</div><div>=C2=A0 =C2=
=A0 =C2=A0 dependent web access control is pointed out with a reference to<=
/div><div>=C2=A0 =C2=A0 =C2=A0 the Consumer-Facing Interface&#39;s data mod=
el</div><div>=C2=A0 =C2=A0 =C2=A0 [consumer-facing-inf-dm].</div></div></di=
v></div></div></blockquote><div><br></div><div>I didn&#39;t follow this cha=
nge. The example you give of a high level security</div><div>policy is clea=
rly freeform text and then you talk about XML. Is this just</div><div>examp=
le a summary of the semantics of something which would actually be an</div>=
<div>XML file? Something else?</div></div></div></blockquote><div>=C2=A0</d=
iv><div dir=3D"auto">=C2=A0 =3D&gt; Even though the high-level security pol=
icy looks like a freeform text,=C2=A0 it is formatted</div><div>=C2=A0 =C2=
=A0 =C2=A0 in an XML according to the high-level security policy YANG model=
 for the Consumer-Facing Interface.</div><div>=C2=A0 =C2=A0 =C2=A0 Yes, it =
is just an example of a summary of the semantics for such a high-level secu=
rity policy,=C2=A0</div><div>=C2=A0 =C2=A0 =C2=A0 which is represented as a=
n XML file.</div><div>=C2=A0 =C2=A0 =C2=A0 Here it an XML file for the web =
filter from the Consumer-Facing Interface Data Model document</div><div>=C2=
=A0 =C2=A0 =C2=A0 (<a href=3D"https://tools.ietf.org/html/draft-ietf-i2nsf-=
consumer-facing-interface-dm-02" rel=3D"noreferrer" target=3D"_blank">https=
://tools.ietf.org/html/draft-ietf-i2nsf-consumer-facing-interface-dm-02</a>=
):</div><div><br></div><div>=C2=A0 =C2=A0 =C2=A0 You can see the XML file f=
rom=C2=A0</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0<a href=3D"https://tools.iet=
f.org/html/draft-ietf-i2nsf-consumer-facing-interface-dm-02#page-49" rel=3D=
"noreferrer" target=3D"_blank">https://tools.ietf.org/html/draft-ietf-i2nsf=
-consumer-facing-interface-dm-02#page-49</a></div><div><br></div><div>=C2=
=A0 =C2=A0 =C2=A0 &lt;?xml version=3D&quot;1.1&quot; encoding=3D&quot;UTF-8=
&quot;?&gt;</div><div>=C2=A0&lt;rpc message-id=3D&quot;4&quot; xmlns=3D&quo=
t;urn:ietf:params:xml:ns:restconf:base:1.0&quot;&gt;</div><div>=C2=A0 &lt;e=
dit-config&gt;</div><div>=C2=A0 =C2=A0&lt;target&gt;</div><div>=C2=A0 =C2=
=A0 &lt;running/&gt;</div><div>=C2=A0 =C2=A0&lt;/target&gt;</div><div>=C2=
=A0 =C2=A0 &lt;config&gt;</div><div>=C2=A0 =C2=A0 =C2=A0&lt;i2nsf-cf-interf=
ace-wf-req nc:operation=3D&quot;create&quot;&gt;</div><div>=C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0&lt;policy-wf&gt;</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0=
 =C2=A0 =C2=A0 =C2=A0&lt;rule-wf&gt;</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&lt;rule-wf-id&gt;03&lt;/rule-wf-id&gt;</=
div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&lt;=
rule-wf-name&gt;wf-policy-example&lt;/rule-wf-name&gt;</div><div>=C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&lt;rule-wf-date&gt;201=
8.10.26/14:03:17&lt;/rule-wf-date&gt;</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0=
 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&lt;event&gt;</div><div>=C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&lt;event-id&=
gt;04&lt;/event-id&gt;</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&lt;event-name&gt;wf&lt;/event-name&gt;</=
div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0&lt;event-date&gt;2018.10.26/14:03:17&lt;/event-date&gt;</div><di=
v>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0&lt;event-type&gt;wf&lt;/event-type&gt;</div><div>=C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&lt;event-map-group&=
gt;04&lt;/event-map-group&gt;</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&lt;enable&gt;True&lt;/enable&gt;<=
/div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&lt=
;/event&gt;</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0&lt;condition&gt;</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&lt;condition-id&gt;04&lt;/conditi=
on-id&gt;</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0=
 =C2=A0 =C2=A0 =C2=A0&lt;source-ip&gt;192.168.1.3&lt;/source-ip&gt;</div><d=
iv>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0&lt;destination-url&gt;<a href=3D"http://www.facebook.com" rel=3D"nor=
eferrer" target=3D"_blank">www.facebook.com</a>&lt;/destination-url&gt;</di=
v><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0&lt;time-information&gt;</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&lt;begin-tim=
e&gt;09:00&lt;/begin-time&gt;</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&lt;end-time&gt;18:0=
0&lt;/end-time&gt;</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&lt;/time-information&gt;</div><div>=C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&lt;ma=
tch-direction&gt;default&lt;/match-direction&gt;</div><div>=C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&lt;exeption&=
gt;00&lt;/exeption&gt;</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0&lt;/condition&gt;</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&lt;action&gt;</div><div>=C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&lt;actio=
n-id&gt;04&lt;/action-id&gt;</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&lt;action-name&gt;action-wf&lt;/a=
ction-name&gt;</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0&lt;action-date&gt;2018.10.26/14:03:17&lt;/actio=
n-date&gt;</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0&lt;primary-action&gt;REJECT&lt;/primary-action&gt;=
</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0&lt;secondary-action&gt;LOG&lt;/secondary-action&gt;</div><div=
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&lt;/action&=
gt;</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0&lt;precedence&gt;none&lt;/precedence&gt;</div><div>=C2=A0 =C2=A0 =C2=A0=
 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&lt;owner&gt;</div><div>=C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&lt;owner-id&gt;03&lt;/owne=
r-id&gt;</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0&lt;name&gt;i2nsf-admin&lt;/name&gt;</div><div>=C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&lt;/owner&gt;</div><div>=C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&lt;/rule-wf&gt;</div><div>=C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0&lt;/policy-wf&gt;</div><div>=C2=A0 =C2=A0 =C2=A0&lt;/i=
2nsf-cf-interface-wf-req&gt;</div><div>=C2=A0 =C2=A0 &lt;/config&gt;</div><=
div>=C2=A0 &lt;/edit-config&gt;</div><div>=C2=A0&lt;/rpc&gt;</div><div>=C2=
=A0 =3D&gt;<span style=3D"white-space:pre-wrap">	</span>In the above, sourc=
e ip is used for the employees.<br></div><div><div><span style=3D"white-spa=
ce:pre-wrap">=C2=A0 </span>Instead of the source ip, we can make and use &q=
uot;source group&quot; for employees that can be translated=C2=A0</div><div=
 dir=3D"auto">=C2=A0 into a set of IP addresses of the source group.</div><=
/div></div></div></div></div></div></div></div></div></blockquote><div><br>=
</div><div>You need to make this clear, then. It would probably be easier t=
o just show the XML and then provide the text summary.<br></div><div><br></=
div></div></div></blockquote><div>=C2=A0 =3D&gt; Okay. I will include a sim=
plified example XML code for web filter and provide the text summary as bel=
ow.</div><div><br></div><div><div>=C2=A0 =C2=A0This service scenario assume=
s that an enterprise network</div><div>=C2=A0 =C2=A0administrator wants to =
control the staff members&#39; access to a</div><div>=C2=A0 =C2=A0particula=
r Internet service (e.g., Example.com) during business</div><div>=C2=A0 =C2=
=A0hours.=C2=A0 The following is an example high-level security policy rule=
</div><div>=C2=A0 =C2=A0for a web filter that the administrator requests: B=
lock the staff members&#39; access to Example.com from 9 AM to 6 PM.=C2=A0=
=C2=A0</div><div>=C2=A0 =C2=A0Here is an example XML code for this web filt=
er:</div><div>&lt;I2NSF&gt;</div><div>=C2=A0 =C2=A0 &lt;name&gt;block_websi=
te&lt;/name&gt;</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 &lt;cond&gt;</div><di=
v>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 &lt;src&gt;Staff_Member&#39;s_P=
C&lt;/src&gt;</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 &lt;dest&=
gt;Example.com&lt;/dest&gt;</div><div><span style=3D"white-space:pre-wrap">=
		</span>=C2=A0 =C2=A0 &lt;time-span-start&gt;9:00AM&lt;/time-span-start&gt=
;</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 &lt;time-span-end&gt;=
-6:00PM&lt;/time-span-end&gt;</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 &lt;/co=
nd&gt;</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 &lt;action&gt;block&lt;action&=
gt;</div><div>&lt;/I2NSF&gt;</div><div><br></div><div>=C2=A0 =C2=A0The secu=
rity policy name is &quot;bloc_website&quot; with the tag &quot;name&quot;.=
</div><div>=C2=A0 =C2=A0The filtering condition has the source group &quot;=
Staff_Member&#39;s_PC&quot; with the tag &quot;src&quot;,</div><div>=C2=A0 =
=C2=A0the destination website &quot;Example.com&quot; with the tag &quot;de=
st&quot;,</div><div>=C2=A0 =C2=A0the filtering start time is the time &quot=
;9:00AM&quot; with the tag &quot;

time-span-start&quot;,=C2=A0</div><div>=C2=A0 =C2=A0and the filtering end t=
ime is the time &quot;6:00PM&quot; with the tag &quot;

time-span-end&quot;.</div><div>=C2=A0 =C2=A0The action is to &quot;block&qu=
ot; the packets satisfying the above condition,=C2=A0</div><div>=C2=A0 =C2=
=A0that is, to drop those packets</div></div></div></div></div></div></div>=
</blockquote><div><br></div><div>LGTM.</div><div><br></div><div> <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"><div dir=3D"ltr"><div dir=3D"ltr"><div class=3D"gmail_quote"><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 class=3D"gmail_quote"><div></div><div><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"auto"><div dir=3D"ltr"><div di=
r=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"lt=
r"><div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"ma=
rgin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:=
1ex"><div dir=3D"ltr"><div class=3D"gmail_quote"><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"><div dir=3D"ltr">=
<div><div>=C2=A0 =C2=A0o=C2=A0 In Section 6, the definitions of an SDN forw=
arding element and an</div><div>=C2=A0 =C2=A0 =C2=A0 NSF are clarified such=
 that an SDN forwarding element is a switch</div><div>=C2=A0 =C2=A0 =C2=A0 =
running as either a hardware middle box or a software virtual</div><div>=C2=
=A0 =C2=A0 =C2=A0 switch, and an NSF is a virtual network function for a se=
curity</div><div>=C2=A0 =C2=A0 =C2=A0 service.</div></div></div></div></div=
></blockquote><div><br></div><div>This wasn&#39;t clear to me either. Based=
 on this text it would seem that</div><div>you could run an NSF on an SDN e=
lement, so it&#39;s not clear why they</div><div>are disjoint sets. Can you=
 give me more information here?<br></div></div></div></blockquote></div></d=
iv></div></div></div></div></div><div dir=3D"auto"><br></div><div dir=3D"lt=
r"><div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr"><div=
 dir=3D"ltr"><div class=3D"gmail_quote"><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 class=3D"gmail_quote"><div></div></div=
></div></blockquote></div></div></div></div></div></div></div><div dir=3D"a=
uto">=C2=A0=3D&gt; An SDN switch can run as a virtual network function like=
 an NSF, but the main functionality of the SDN switch is packet forwarding =
with a flow table along with simple filtering rules. More complicated secur=
ity services can be done at dedicated NSFs. For example, there is the Open =
Virtual Switch (OVS) project for such a software-based SDN switch:=C2=A0<a =
href=3D"https://www.openvswitch.org" target=3D"_blank">https://www.openvswi=
tch.org</a></div><div dir=3D"auto"><br></div><div dir=3D"auto">Thus, the SD=
N switches and NSFs are logically disjoint sets though all of them=C2=A0 ca=
n run physically as virtual network functions.</div></div></blockquote><div=
><br></div><div>I&#39;m sorry, this still isn&#39;t clear, at least to me. =
How can I look at a given software element and determine whether it&#39;s a=
n NSF or a virtualized SDN switch?<br></div></div></div></blockquote><div><=
br></div><div>=C2=A0=3D&gt; The distinction is logically done such that the=
 NFV system having the I2NSF system categorizes some VNFs as NSFs for dedic=
ated security services</div><div>=C2=A0 =C2=A0 =C2=A0 and some VNFs as virt=
ualized SDN switches for packet switching and simple filtering rule enforce=
ment.</div><div><br></div><div>=C2=A0 =C2=A0 =C2=A0If there is an expert in=
 the NFV, please let us know for further clarification.</div></div></div></=
div></div></div></blockquote><div><br></div><div>I&#39;m not following this=
 either, so that would definitely help.<br></div><div><br></div><div>-Ekr</=
div><div><br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0p=
x 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div d=
ir=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr"><div class=3D=
"gmail_quote"><div><br></div><div>=C2=A0 =C2=A0 =C2=A0Thanks.</div><div><br=
></div><div>=C2=A0 =C2=A0 =C2=A0Best Regards,</div><div>=C2=A0 =C2=A0 =C2=
=A0Paul</div><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"ma=
rgin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:=
1ex"><div dir=3D"ltr"><div class=3D"gmail_quote"><div></div><div><br></div>=
<div>-Ekr<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0p=
x 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div d=
ir=3D"auto"><div dir=3D"auto"><br></div><div dir=3D"auto">If you have furth=
er questions, please let me know.</div><div dir=3D"auto"><br></div><div dir=
=3D"auto">Thanks.</div><div dir=3D"auto">=C2=A0</div><div dir=3D"auto">Best=
 Regards,</div><div dir=3D"auto">Paul</div><div dir=3D"ltr"><div dir=3D"ltr=
"><div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr"><div =
class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margin:0px=
 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><di=
v dir=3D"ltr"><div class=3D"gmail_quote"><div></div><div><br></div><div>-Ek=
r</div><div><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"><di=
v dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr"><div><div><br></div><div>=
=C2=A0 =C2=A0o=C2=A0 In Section 6.3, a flow forwarding path management sche=
me in</div><div>=C2=A0 =C2=A0 =C2=A0 [AVANT-GUARD] is described in a self-c=
ontained way as follows.</div><div>=C2=A0 =C2=A0 =C2=A0 For DDoS-attack mit=
igation, the forwarding of traffic flows in</div><div>=C2=A0 =C2=A0 =C2=A0 =
switches can be dynamically configured such that malicious traffic</div><di=
v>=C2=A0 =C2=A0 =C2=A0 flows are handled by the paths separated from normal=
 traffic flows</div><div>=C2=A0 =C2=A0 =C2=A0 in order to minimize the impa=
ct of those malicious traffic on the</div><div>=C2=A0 =C2=A0 =C2=A0 the ser=
vers.=C2=A0 This flow path separation can be done by a flow</div><div>=C2=
=A0 =C2=A0 =C2=A0 forwarding path management scheme based on [AVANT-GUARD].=
</div><div><br></div><div>=C2=A0 =C2=A0o=C2=A0 Some typos are corrected suc=
h as &quot;Interner -&gt; Internet&quot;,</div><div>=C2=A0 =C2=A0 =C2=A0 &q=
uot;Registation -&gt; Registration&quot;, &quot;The low-level security rule=
s for</div><div>=C2=A0 =C2=A0 =C2=A0 web filter checks -&gt; The low-level =
security rules for web filter</div><div>=C2=A0 =C2=A0 =C2=A0 check&quot;, &=
quot;fltering -&gt; filtering&quot;, &quot;illegal packets -&gt; malicious<=
/div><div>=C2=A0 =C2=A0 =C2=A0 packets&quot;, &quot;manipulate rules -&gt; =
configure rules&quot;, &quot;managenent -&gt;</div><div>=C2=A0 =C2=A0 =C2=
=A0 management&quot;, and &quot;DDoS-attack mitigation operations -&gt; DDo=
S-attack</div><div>=C2=A0 =C2=A0 =C2=A0 mitigation&quot;.</div></div><div>-=
---------------------------------------------------------------------------=
---------------------=C2=A0</div><div>=C2=A0<br></div><div>Thanks and Merry=
 Christmas!</div><div><br></div><div>Best Regards,</div><div>Paul</div></di=
v></div></div><br><div class=3D"gmail_quote"><div dir=3D"ltr">On Fri, Dec 2=
1, 2018 at 11:33 PM Eric Rescorla &lt;<a href=3D"mailto:ekr@rtfm.com" rel=
=3D"noreferrer" target=3D"_blank">ekr@rtfm.com</a>&gt; wrote:<br></div><blo=
ckquote 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">Rich version of this review at:<br><a href=3D"https://mozphab-ietf.dev=
svcdev.mozaws.net/D3181" rel=3D"noreferrer" target=3D"_blank">https://mozph=
ab-ietf.devsvcdev.mozaws.net/D3181</a><br><br><br>I found a number of typog=
raphical and grammar errors. Please give this<br>document a thorough read.<=
br><br>IMPORTANT<br>S 1.<br>&gt;=C2=A0=C2=A0 <br>&gt;=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0 Interface to Network Security Functions (I2NSF) defines a framewo=
rk<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 and interfaces for interacting wit=
h Network Security Functions<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 (NSFs).=
=C2=A0 The I2NSF framework allows heterogeneous NSFs developed by<br>&gt;=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 different security solution vendors to be us=
ed in the Network<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Functions Virtualiz=
ation (NFV) environment [ETSI-NFV] by utilizing<br><br>Much of this documen=
t cannot be understood without reading ETSI-NFV,<br>so it has to be a norma=
tive reference. It also would be helpful to<br>provide a link.<br><br><br>S=
 2.<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 This document uses the terminolog=
y described in [RFC7149],<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 [ITU-T.Y.33=
00], [ONF-OpenFlow], [ONF-SDN-Architecture],<br>&gt;=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0 [ITU-T.X.1252], [ITU-T.X.800], [RFC8329], [i2nsf-terminology],<br=
>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 [consumer-facing-inf-im], [consumer-fac=
ing-inf-dm],<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 [i2nsf-nsf-cap-im], [nsf=
-facing-inf-dm], [registration-inf-dm], and<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0 [nsf-triggered-steering].=C2=A0 In addition, the following terms are=
<br><br>Every term in this document needs to be understandable without<br>r=
eference to closed specifications or internally defined. Please<br>ensure t=
hat this is so,<br><br><br>S 3.<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 used =
for the I2NSF NSF-Facing Interface.<br>&gt;=C2=A0=C2=A0 <br>&gt;=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0 The Registration Interface between the Security Contr=
oller and the<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Developer&#39;s Managem=
ent System can be implemented by RESTCONF<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0 [RFC8040].=C2=A0 The data model defined in [registration-inf-dm] can=
 be<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 used for the I2NSF Registration I=
nterface.<br><br>What role does the Developer&#39;s Management System play =
in this? I think<br>this refers to the text above starting with &quot;The d=
evelopers (or<br>vendors)...&quot;. Is that correct?<br><br>Assuming I am c=
orrect, this seems like a potentially serious security<br>vulnerability in =
this design in that it potentially allows an inside<br>attacker at the deve=
loper to seriously weaken a system&#39;s security.<br>What protections exis=
t to prevent this?<br><br><br>S 4.<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 ad=
ministrator wants to control the staff members&#39; access to a<br>&gt;=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0 particular Interner service (e.g., Example.com)=
 during business<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 hours.=C2=A0 The fol=
lowing is an example high-level security policy rule<br>&gt;=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0 that the administrator requests: Block the staff members&#3=
9; access to<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Example.com from 9 AM to=
 6 PM.=C2=A0 The administrator sends this high-<br>&gt;=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0 level security policy to the Security Controller, then the Sec=
urity<br><br>The text above suggests that high-level policies are via<br>RE=
STCONF/YANG, but this is clearly freeform text.<br>COMMENTS<br>S 1.<br>&gt;=
=C2=A0=C2=A0 <br>&gt;=C2=A0=C2=A0 1.=C2=A0 Introduction<br>&gt;=C2=A0=C2=A0=
 <br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Interface to Network Security Funct=
ions (I2NSF) defines a framework<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 and =
interfaces for interacting with Network Security Functions<br>&gt;=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0 (NSFs).=C2=A0 The I2NSF framework allows heterogeneou=
s NSFs developed by<br><br>Please define &quot;Network Security Functions&q=
uot; here.<br><br><br><br><br>S 1.<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 fu=
nctions in the NFV platform.=C2=A0 In the I2NSF framework, each NSF<br>&gt;=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 initially registers the profile of its own c=
apabilities into the<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 system in order =
for themselves to be available in the system.=C2=A0 In<br>&gt;=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0 addition, the Security Controller is validated by the I2=
NSF Client<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 (also called I2NSF User) t=
hat the user is employing, so that the user<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0 can request security services through the Security Controller.<br><b=
r>In this case the user is the system administrator.<br><br><br>S 1.<br>&gt=
;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 [RFC7149] to provide different security fun=
ctionality such as<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 firewalls [opsawg-=
firewalls], Deep Packet Inspection (DPI), and<br>&gt;=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0 Distributed Denial of Service (DDoS) attack mitigation; (iv) the =
use<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 of NFV as supporting technology.=
=C2=A0 The implementation of I2NSF in<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
 these scenarios has allowed us to verify the applicability and<br>&gt;=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0 effectiveness of the I2NSF framework for a vari=
ety of use cases.<br><br>This would be easier to read with a standard bulle=
ted list.<br><br><br>S 2.<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0 network resources, which facilitates the design, delivery and<br>&gt=
;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 operation of network serv=
ices in a dynamic and scalable manner<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0 [ITU-T.Y.3300].<br>&gt;=C2=A0=C2=A0 <br>&gt;=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0 o=C2=A0 Firewall: A service function at the junction of =
two network<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 segment=
s that inspects every packet that attempts to cross the<br><br>Nit: It migh=
t not inspect *every* packet.<br><br><br>S 4.<br>&gt;=C2=A0=C2=A0 <br>&gt;=
=C2=A0=C2=A0 4.=C2=A0 Time-dependent Web Access Control Service<br>&gt;=C2=
=A0=C2=A0 <br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 This service scenario assu=
mes that an enterprise network<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 admini=
strator wants to control the staff members&#39; access to a<br>&gt;=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0 particular Interner service (e.g., Example.com) du=
ring business<br><br>Nit: &quot;Internet&quot;<br><br><br>S 4.<br>&gt;=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0 inspection capability is required to check whet=
her the target URL of<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 a received pack=
et is in the Example.com domain or not.<br>&gt;=C2=A0=C2=A0 <br>&gt;=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0 The Security Controller maintains the security cap=
abilities of each<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 NSF running in the =
I2NSF system, which have been reported by the<br>&gt;=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0 Developer&#39;s Management System via the Registation interface.=
=C2=A0 Based<br><br>Nit: &quot;Registration&quot;<br><br><br>S 4.<br>&gt;=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 currently using the network.=C2=A0 Based on =
the retrieved information, the<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Securi=
ty Controller generates low-level security rules to check<br>&gt;=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0 whether the source IP address of a received packet ma=
tches any one<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 being used by a staff m=
ember.=C2=A0 In addition, the low-level security<br>&gt;=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0 rules should be able to determine that a received packet is of=
 HTTP<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 protocol.=C2=A0 The low-level s=
ecurity rules for web filter checks that<br><br>Nit: &quot;rules&quot;... &=
quot;checks&quot; disagree.<br><br><br>S 6.<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0 translated into their packet forwarding rules, whereas NSFs enforce<=
br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 NSF-related security rules requiring =
the security capabilities of the<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 NSFs=
.=C2=A0 For this purpose, the Security Controller instructs the SDN<br>&gt;=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Controller via NSF-Facing Interface so that =
SDN forwarding elements<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 can perform t=
he required security services with flow tables under the<br>&gt;=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0 supervision of the SDN Controller.<br><br>I&#39;m hav=
ing some trouble understanding the difference here between NSFs<br>and SDN =
elements. They both seem to be software controlled network<br>elements. Is =
this just some continuum about CPU power?<br><br><br>S 6.<br>&gt;=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0 can perform the required security services with flow =
tables under the<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 supervision of the S=
DN Controller.<br>&gt;=C2=A0=C2=A0 <br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 A=
s an example, let us consider two different types of security rules:<br>&gt=
;=C2=A0=C2=A0 <br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Rule A is a simple pac=
ket fltering rule that checks only the IP<br><br>Nit: &quot;filtering&quot;=
<br><br><br>S 6.2.<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0 packets that have the same call-id.<br>&gt;=C2=A0=C2=A0 <br>&gt;=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0 6.=C2=A0 The SDN Controller installs new rules =
(e.g., drop packets) into<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0 underlying switches.<br>&gt;=C2=A0=C2=A0 <br>&gt;=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0 7.=C2=A0 The illegal packets are dropped by these switch=
es.<br><br>&quot;Illegal&quot; is probably the wrong wrod here.<br><br><br>=
S 6.3.<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 is helpful t=
o determine security policies for such a network.<br>&gt;=C2=A0=C2=A0 <br>&=
gt;=C2=A0=C2=A0 6.3.=C2=A0 Attack Mitigation: Centralized DDoS-attack Mitig=
ation System<br>&gt;=C2=A0=C2=A0 <br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 A c=
entralized DDoS-attack mitigation can manage each network resource<br>&gt;=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 and manipulate rules to each switch through =
a common server for DDoS-<br><br>&quot;manipulate rules to&quot; is not gra=
mmatical.<br><br><br>S 6.3.<br>&gt;=C2=A0=C2=A0 <br>&gt;=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0 Servers are categorized into stateless servers (e.g., DNS serv=
ers)<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 and stateful servers (e.g., web =
servers).=C2=A0 For DDoS-attack<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 mitig=
ation, traffic flows in switches are dynamically configured by<br>&gt;=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0 traffic flow forwarding path management accordi=
ng to the category of<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 servers [AVANT-=
GUARD].=C2=A0 Such a managenent should consider the load<br><br>1. This see=
ms hard to understand without this reference, which is not<br>public.<br>2.=
 &quot;management&quot;<br><br><br>S 6.3.<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0 mitigation, traffic flows in switches are dynamically configured by<=
br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 traffic flow forwarding path manageme=
nt according to the category of<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 serve=
rs [AVANT-GUARD].=C2=A0 Such a managenent should consider the load<br>&gt;=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 balance among the switches for the defense a=
gainst DDoS attacks.<br>&gt;=C2=A0=C2=A0 <br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0 The procedure of DDoS-attack mitigation operations in this system is=
<br><br>&quot;procedure of... operations&quot; is ungrammatical<br><br></di=
v></div>
</blockquote></div><br clear=3D"all"><div><br></div>-- <br><div dir=3D"ltr"=
 class=3D"gmail-m_-5775707567964940138gmail-m_-4645637776060181596gmail-m_7=
571128782014320286m_-6695152896369925623gmail-m_-607987677208405722gmail-m_=
-9111533177071645325gmail_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) J=
eong, Ph.D.<br>Associate Professor<br>Department of Software<br>Sungkyunkwa=
n University<br>Office: +82-31-299-4957<br>Email: <a href=3D"mailto:jaehoon=
.paul@gmail.com" rel=3D"noreferrer" target=3D"_blank">jaehoon.paul@gmail.co=
m</a><br>Personal Homepage: <a href=3D"http://cpslab.skku.edu/people-jaehoo=
n-jeong.php" rel=3D"noreferrer" target=3D"_blank">http://iotlab.skku.edu/pe=
ople-jaehoon-jeong.php</a><br></div></div></div></div></div></div></div></d=
iv>
</blockquote></div></div>
</blockquote></div><br clear=3D"all"><div><br></div>-- <br><div dir=3D"ltr"=
 class=3D"gmail-m_-5775707567964940138gmail-m_-4645637776060181596gmail-m_7=
571128782014320286m_-6695152896369925623gmail_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 So=
ftware<br>Sungkyunkwan University<br>Office: +82-31-299-4957<br>Email: <a h=
ref=3D"mailto:jaehoon.paul@gmail.com" rel=3D"noreferrer" target=3D"_blank">=
jaehoon.paul@gmail.com</a>,=C2=A0<a href=3D"mailto:pauljeong@skku.edu" styl=
e=3D"font-size:12.8px" rel=3D"noreferrer" target=3D"_blank">pauljeong@skku.=
edu</a><br>Personal Homepage: <a href=3D"http://cpslab.skku.edu/people-jaeh=
oon-jeong.php" rel=3D"noreferrer" target=3D"_blank">http://iotlab.skku.edu/=
people-jaehoon-jeong.php</a><br></div></div></div></div></div></div></div><=
/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-m_-5775707567964940138gmail_signature"><div dir=3D"ltr"><di=
v><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 Softw=
are<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"=
 target=3D"_blank">pauljeong@skku.edu</a><br>Personal Homepage: <a href=3D"=
http://cpslab.skku.edu/people-jaehoon-jeong.php" target=3D"_blank">http://i=
otlab.skku.edu/people-jaehoon-jeong.php</a><br></div></div></div></div></di=
v></div></div></div></div></div></div></div>
</blockquote></div></div>

--000000000000c3c1cb057e159a63--


From nobody Fri Dec 28 07:08:27 2018
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 86A3C126BED for <i2nsf@ietfa.amsl.com>; Fri, 28 Dec 2018 07:08:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.499
X-Spam-Level: 
X-Spam-Status: No, score=-0.499 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HK_NAME_FM_MR_MRS=1.499, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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 hAhcCETjoKK7 for <i2nsf@ietfa.amsl.com>; Fri, 28 Dec 2018 07:08:22 -0800 (PST)
Received: from mail-it1-x136.google.com (mail-it1-x136.google.com [IPv6:2607:f8b0: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 51089126C01 for <i2nsf@ietf.org>; Fri, 28 Dec 2018 07:08:22 -0800 (PST)
Received: by mail-it1-x136.google.com with SMTP id w18so28680388ite.1 for <i2nsf@ietf.org>; Fri, 28 Dec 2018 07:08:22 -0800 (PST)
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=lNYy0p0qjSJi2m+6PBIxvgcJGwl6TS/6/qHFj5dm8ps=; b=hRJqohrCFCQB1Do1craupKeVz3T01D5MtVRQK9dXVvxkAzAwGktKCbmUyVknAX73Zb ohlV5dV4Puw74mvOK/a2QMop6gBK7WCIyGL5b0cx7XZ6DrNwKOP8PT6q5Y8Bakozrw6B yPz20J5v+9uU2PKyNHaOmt+PCOdCynhkpOHDuhOe/3jk0RKbZuf0jOa4ad0YeAVKo/Ox b9qylnG9mF6rPjPpcxHzIeB9acisV0p3iClX+MFXDxiBxucv3fcsg/txOz2IhB8Bi9/p ZyBzniNy1Uo8qsHxoq4GuQ/113haQr1x/36ALwsfeHCbCGtNx7Y/C23D4SG8+UDcCB5X VxkA==
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=lNYy0p0qjSJi2m+6PBIxvgcJGwl6TS/6/qHFj5dm8ps=; b=n5hvbeZ4S3/b1MRKIADH+jk7wnR7sj1wCIGrRVCusPwSlEG850peabh4bHQUqpXY2e uvjHJLBtJh2YiWhQgBIpwqH4IUn3EoWDIPT+k4avnZk38uVjvUwhdCZZJAd63nl97l9r 3n/K7D9vHZ0nImR1ThIF8Oh2bD2zxFknICVSgY7PktLdFZe2b4gdrf/l2UrsHA5mWeFu 4BZU+GotYkKbrMJN3aMjM+lr2G8MPPbtOHr0Zy3DN5BmnzxmLtVew6p9TPw4MS2sejJt LyMwrdcajznNW2KcyDYY9k9kgcYk/wr578zK8K+zNYKncf3GA5hY3MnpHFbCoRItiV1m psTw==
X-Gm-Message-State: AJcUukcXF4XzST1CmzBXpI056wswDN3FqejnD6hSj4m69vO9fnoxwixX oe1iD9dIfsjJMzYNwxvzKVIMbiK8hj+tgfOZcnI=
X-Google-Smtp-Source: ALg8bN4C1DnBjFlKHe8lr6n9WGNzkNm2zef2IKDV97RGjK5d+chyzpRvIdQNI+VJqTHG60JCmhghXcN74gRUygr8oPo=
X-Received: by 2002:a24:2914:: with SMTP id p20mr9352056itp.156.1546009701364;  Fri, 28 Dec 2018 07:08:21 -0800 (PST)
MIME-Version: 1.0
References: <CABcZeBOjhEpw4gNDRgJD=FCWy1Wrirz_EsJefJjDHpp5mVe1fw@mail.gmail.com> <CAPK2DewE2vbjAr41xErxnjmxK2CTmK2h9fXFTBSFCigpNj9XPQ@mail.gmail.com> <CABcZeBNZhqTawAFcj9p01ig-tE=XaFm5yCXuGJQFiqoOGgNZxA@mail.gmail.com> <CAPK2Dex7hbKC3Cpq2Jy+UXr7YFqgjGUGvzNiSYMix7M5qQhx=w@mail.gmail.com> <CABcZeBMyRGZ5QEwxLQRkcrkz665vWgOFPv+dwAuF5HSg1=B6eA@mail.gmail.com> <CAPK2Deyn1=vVShbq=hMRmvQ1=G5_Yew8pYgqQC=Vh-dG9d2Wrg@mail.gmail.com> <CABcZeBPd2B5QB0-+eJ5z77rACvTLTTpZRrRKBrCAZHdBCFurGw@mail.gmail.com>
In-Reply-To: <CABcZeBPd2B5QB0-+eJ5z77rACvTLTTpZRrRKBrCAZHdBCFurGw@mail.gmail.com>
From: "Mr. Jaehoon Paul Jeong" <jaehoon.paul@gmail.com>
Date: Sat, 29 Dec 2018 00:08:09 +0900
Message-ID: <CAPK2DexxmGj1YWW8=WdLEx32eVmGhoSehZFA20gjNgALMSQVMA@mail.gmail.com>
To: Eric Rescorla <ekr@rtfm.com>, Susan Hares <shares@ndzh.com>,  DIEGO LOPEZ GARCIA <diego.r.lopez@telefonica.com>, Sangwon Hyun <swhyun77@gmail.com>, Tae-Jin Ahn <taejin.ahn@kt.com>
Cc: Linda Dunbar <linda.dunbar@huawei.com>, Yoav Nir <ynir.ietf@gmail.com>, i2nsf@ietf.org,  skku_secu-brain_all@googlegroups.com, Jaehoon Jeong <jaehoon.paul@gmail.com>
Content-Type: multipart/alternative; boundary="00000000000011c114057e166f54"
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2nsf/UOIxhT7GyHEpU8Bm4S0HrtbK-WQ>
Subject: Re: [I2nsf] AD Review of draft-ietf-i2nsf-applicability-07
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, 28 Dec 2018 15:08:26 -0000

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

Susan, Diego, Sangwon, and Taejin,
Could you clarify my explanation for Eric as coauthors?

Thanks.

Best Regards,
Paul

2018=EB=85=84 12=EC=9B=94 28=EC=9D=BC (=EA=B8=88) =EC=98=A4=ED=9B=84 11:09=
=EC=97=90 Eric Rescorla <ekr@rtfm.com>=EB=8B=98=EC=9D=B4 =EC=9E=91=EC=84=B1=
:

>
>
> On Thu, Dec 27, 2018 at 7:21 PM Mr. Jaehoon Paul Jeong <
> jaehoon.paul@gmail.com> wrote:
>
>> Eric,
>> Let me answer your further questions below.
>>
>> On Thu, Dec 27, 2018 at 11:59 PM Eric Rescorla <ekr@rtfm.com> wrote:
>>
>>>
>>>
>>> On Wed, Dec 26, 2018 at 6:42 PM Mr. Jaehoon Paul Jeong <
>>> jaehoon.paul@gmail.com> wrote:
>>>
>>>> Hi Eric,
>>>> Here are my answers inlines below.
>>>>
>>>> On Thu, Dec 27, 2018 at 3:44 AM Eric Rescorla <ekr@rtfm.com> wrote:
>>>>
>>>>> Paul,
>>>>>
>>>>> Thanks for your new version. Some responses below.
>>>>>
>>>>>
>>>>> On Tue, Dec 25, 2018 at 6:42 AM Mr. Jaehoon Paul Jeong <
>>>>> jaehoon.paul@gmail.com> wrote:
>>>>>
>>>>>> Hi Eric, Linda and Yoav,
>>>>>> I have reflected all the comments from Eric and submitted the
>>>>>> revision -08 as follows:
>>>>>> https://tools.ietf.org/html/draft-ietf-i2nsf-applicability-08
>>>>>>
>>>>>> The changes are described in Appendix A of -08 document as follows:
>>>>>>
>>>>>> --------------------------------------------------------------------=
-----------------------------
>>>>>> Appendix A.  Changes from draft-ietf-i2nsf-applicability-07
>>>>>>
>>>>>>    The following changes have been made from
>>>>>>    draft-ietf-i2nsf-applicability-07:
>>>>>>
>>>>>>    o  This version has reflected all the comments from Eric Rescorla
>>>>>> who
>>>>>>       is a Security Area Director as follows.
>>>>>>
>>>>>>    o  In Section 1, Network Security Function (NFV) is defined in th=
e
>>>>>>       viewpoint of the I2NSF framework.
>>>>>>
>>>>>>    o  In Section 1, a user using the I2NSF User is clarified as a
>>>>>> system
>>>>>>       administrator in the I2NSF framework.
>>>>>>
>>>>>>    o  In Section 1, as the applicability of the I2NSF framework, fou=
r
>>>>>>       different scenarios are represented with a standard bulleted
>>>>>> list.
>>>>>>
>>>>>>    o  The standard document about ETSI-NFV is moved to Normative
>>>>>>       References.
>>>>>>
>>>>>>    o  In Section 2, key terms (e.g., Network Function, Network
>>>>>> Security
>>>>>>       Function, Network Functions Virtualization, and Servive Functi=
on
>>>>>>       Chaining) are internally defined along with the reference to
>>>>>> open
>>>>>>       specifications.
>>>>>>
>>>>>>    o  In Section 2, the definition of Firewall is corrected such tha=
t
>>>>>>       some suspicious packets are inspected by the firewall rather
>>>>>> than
>>>>>>       every packet.
>>>>>>
>>>>>>    o  In Section 3, for a Developer's Management System, the problem
>>>>>> of
>>>>>>       an inside attacker is addressed, and a possible solution for t=
he
>>>>>>       inside attacks is suggested through I2NSF NSF monitoring
>>>>>>       functionality.
>>>>>>
>>>>>
>>>>> I'm still pretty concerned about this. Standardizing a situation in
>>>>> which the
>>>>> developer of your firewall has real-time management-level access to
>>>>> that firewall seems extremely insecure, especially when that access i=
s
>>>>> authenticated via conventional credentials that are online as part of
>>>>> the transaction (as opposed to software builds which can be signed
>>>>> offline). This doesn't seem like a best practice. Why is it necessary=
?
>>>>>
>>>>
>>>>
>>>>>  =3D>  The developer of a firewall does not have real-time
>>>> management-level access
>>>>        even though its management system works the control plane as
>>>> part of the I2NSF system.
>>>>        The developer's management system provides the Security
>>>> Controller with
>>>>        the interface (i.e., Registration Interface) that is used to
>>>> register the capability of
>>>>        the developer's security network function (i.e., firewall), to
>>>> search an NSF for the required capability for a high-level security po=
licy,
>>>> and to help the lifecycle management
>>>>        of such an NSF for the Security Controller through an NFV
>>>> interface (i.e., Ve-Vnfm interface) with the NFV's MANO.
>>>>
>>>
>>> I don't understand the distinction you are drawing here. Under what
>>> conditions can the developer modify the behavior of the I2NSF system? C=
an
>>> it do so at any time and without explicit action by the admin.
>>>
>>>  =3D>  The developer means a security solution vendor (e.g., McAfee and
>> Symantec) who provides the I2NSF system with security solutions,
>>        such as firewall, web filter, DPI, IDS/IPS, and DDoS-attack
>> mitigator. Actually, the developer's management system
>>        cannot modify the behavior of the I2NSF system in run-time as lon=
g
>> as the vendor doesn't have any backdoor to
>>        their developer's management system.
>>        This developer's management system facilitates the security
>> service government by the Security Controller
>>        by providing the Security Controller with the Registration
>> Interface for the capability registration and
>> instantiation/de-instantiation
>>        of the image of a security service function.
>>        Thus, only the administrator can modify the behavior of the I2NSF
>> system.
>>
>>        Maybe,
>>        Diego Lopez can clarify my answer because he is the editor of RFC
>> 8329 (Framework for Interface to Network Security Functions):
>>        https://tools.ietf.org/html/rfc832
>> <https://tools.ietf.org/html/rfc8329>
>>
>
> Yeah, I'm not really following this. What functions can the Developer
> perform on the system.
>
>
>    o  In Section 4, an XML file for the RESTCONF/YANG for the time-
>>>>>>       dependent web access control is pointed out with a reference t=
o
>>>>>>       the Consumer-Facing Interface's data model
>>>>>>       [consumer-facing-inf-dm].
>>>>>>
>>>>>
>>>>> I didn't follow this change. The example you give of a high level
>>>>> security
>>>>> policy is clearly freeform text and then you talk about XML. Is this
>>>>> just
>>>>> example a summary of the semantics of something which would actually
>>>>> be an
>>>>> XML file? Something else?
>>>>>
>>>>
>>>>   =3D> Even though the high-level security policy looks like a freefor=
m
>>>> text,  it is formatted
>>>>       in an XML according to the high-level security policy YANG model
>>>> for the Consumer-Facing Interface.
>>>>       Yes, it is just an example of a summary of the semantics for suc=
h
>>>> a high-level security policy,
>>>>       which is represented as an XML file.
>>>>       Here it an XML file for the web filter from the Consumer-Facing
>>>> Interface Data Model document
>>>>       (
>>>> https://tools.ietf.org/html/draft-ietf-i2nsf-consumer-facing-interface=
-dm-02
>>>> ):
>>>>
>>>>       You can see the XML file from
>>>>
>>>> https://tools.ietf.org/html/draft-ietf-i2nsf-consumer-facing-interface=
-dm-02#page-49
>>>>
>>>>       <?xml version=3D"1.1" encoding=3D"UTF-8"?>
>>>>  <rpc message-id=3D"4" xmlns=3D"urn:ietf:params:xml:ns:restconf:base:1=
.0">
>>>>   <edit-config>
>>>>    <target>
>>>>     <running/>
>>>>    </target>
>>>>     <config>
>>>>      <i2nsf-cf-interface-wf-req nc:operation=3D"create">
>>>>          <policy-wf>
>>>>              <rule-wf>
>>>>                  <rule-wf-id>03</rule-wf-id>
>>>>                  <rule-wf-name>wf-policy-example</rule-wf-name>
>>>>                  <rule-wf-date>2018.10.26/14:03:17</rule-wf-date>
>>>>                  <event>
>>>>                      <event-id>04</event-id>
>>>>                      <event-name>wf</event-name>
>>>>                      <event-date>2018.10.26/14:03:17</event-date>
>>>>                      <event-type>wf</event-type>
>>>>                      <event-map-group>04</event-map-group>
>>>>                      <enable>True</enable>
>>>>                  </event>
>>>>                  <condition>
>>>>                      <condition-id>04</condition-id>
>>>>                      <source-ip>192.168.1.3</source-ip>
>>>>                      <destination-url>www.facebook.com
>>>> </destination-url>
>>>>                      <time-information>
>>>>                          <begin-time>09:00</begin-time>
>>>>                          <end-time>18:00</end-time>
>>>>                      </time-information>
>>>>                      <match-direction>default</match-direction>
>>>>                      <exeption>00</exeption>
>>>>                  </condition>
>>>>                  <action>
>>>>                      <action-id>04</action-id>
>>>>                      <action-name>action-wf</action-name>
>>>>                      <action-date>2018.10.26/14:03:17</action-date>
>>>>                      <primary-action>REJECT</primary-action>
>>>>                      <secondary-action>LOG</secondary-action>
>>>>                  </action>
>>>>                  <precedence>none</precedence>
>>>>                <owner>
>>>>                  <owner-id>03</owner-id>
>>>>                  <name>i2nsf-admin</name>
>>>>                </owner>
>>>>              </rule-wf>
>>>>          </policy-wf>
>>>>      </i2nsf-cf-interface-wf-req>
>>>>     </config>
>>>>   </edit-config>
>>>>  </rpc>
>>>>   =3D> In the above, source ip is used for the employees.
>>>>   Instead of the source ip, we can make and use "source group" for
>>>> employees that can be translated
>>>>   into a set of IP addresses of the source group.
>>>>
>>>
>>> You need to make this clear, then. It would probably be easier to just
>>> show the XML and then provide the text summary.
>>>
>>>   =3D> Okay. I will include a simplified example XML code for web filte=
r
>> and provide the text summary as below.
>>
>>    This service scenario assumes that an enterprise network
>>    administrator wants to control the staff members' access to a
>>    particular Internet service (e.g., Example.com) during business
>>    hours.  The following is an example high-level security policy rule
>>    for a web filter that the administrator requests: Block the staff
>> members' access to Example.com from 9 AM to 6 PM.
>>    Here is an example XML code for this web filter:
>> <I2NSF>
>>     <name>block_website</name>
>>         <cond>
>>             <src>Staff_Member's_PC</src>
>>             <dest>Example.com</dest>
>>     <time-span-start>9:00AM</time-span-start>
>>             <time-span-end>-6:00PM</time-span-end>
>>         </cond>
>>         <action>block<action>
>> </I2NSF>
>>
>>    The security policy name is "bloc_website" with the tag "name".
>>    The filtering condition has the source group "Staff_Member's_PC" with
>> the tag "src",
>>    the destination website "Example.com" with the tag "dest",
>>    the filtering start time is the time "9:00AM" with the tag "
>> time-span-start",
>>    and the filtering end time is the time "6:00PM" with the tag "
>> time-span-end".
>>    The action is to "block" the packets satisfying the above condition,
>>    that is, to drop those packets
>>
>
> LGTM.
>
>
>
>>
>>>
>>>    o  In Section 6, the definitions of an SDN forwarding element and an
>>>>>>       NSF are clarified such that an SDN forwarding element is a
>>>>>> switch
>>>>>>       running as either a hardware middle box or a software virtual
>>>>>>       switch, and an NSF is a virtual network function for a securit=
y
>>>>>>       service.
>>>>>>
>>>>>
>>>>> This wasn't clear to me either. Based on this text it would seem that
>>>>> you could run an NSF on an SDN element, so it's not clear why they
>>>>> are disjoint sets. Can you give me more information here?
>>>>>
>>>>
>>>>  =3D> An SDN switch can run as a virtual network function like an NSF,
>>>> but the main functionality of the SDN switch is packet forwarding with=
 a
>>>> flow table along with simple filtering rules. More complicated securit=
y
>>>> services can be done at dedicated NSFs. For example, there is the Open
>>>> Virtual Switch (OVS) project for such a software-based SDN switch:
>>>> https://www.openvswitch.org
>>>>
>>>> Thus, the SDN switches and NSFs are logically disjoint sets though all
>>>> of them  can run physically as virtual network functions.
>>>>
>>>
>>> I'm sorry, this still isn't clear, at least to me. How can I look at a
>>> given software element and determine whether it's an NSF or a virtualiz=
ed
>>> SDN switch?
>>>
>>
>>  =3D> The distinction is logically done such that the NFV system having =
the
>> I2NSF system categorizes some VNFs as NSFs for dedicated security servic=
es
>>       and some VNFs as virtualized SDN switches for packet switching and
>> simple filtering rule enforcement.
>>
>>      If there is an expert in the NFV, please let us know for further
>> clarification.
>>
>
> I'm not following this either, so that would definitely help.
>
> -Ekr
>
>
>>      Thanks.
>>
>>      Best Regards,
>>      Paul
>>
>>
>>>
>>> -Ekr
>>>
>>>>
>>>> If you have further questions, please let me know.
>>>>
>>>> Thanks.
>>>>
>>>> Best Regards,
>>>> Paul
>>>>
>>>>>
>>>>> -Ekr
>>>>>
>>>>>
>>>>>>    o  In Section 6.3, a flow forwarding path management scheme in
>>>>>>       [AVANT-GUARD] is described in a self-contained way as follows.
>>>>>>       For DDoS-attack mitigation, the forwarding of traffic flows in
>>>>>>       switches can be dynamically configured such that malicious
>>>>>> traffic
>>>>>>       flows are handled by the paths separated from normal traffic
>>>>>> flows
>>>>>>       in order to minimize the impact of those malicious traffic on
>>>>>> the
>>>>>>       the servers.  This flow path separation can be done by a flow
>>>>>>       forwarding path management scheme based on [AVANT-GUARD].
>>>>>>
>>>>>>    o  Some typos are corrected such as "Interner -> Internet",
>>>>>>       "Registation -> Registration", "The low-level security rules f=
or
>>>>>>       web filter checks -> The low-level security rules for web filt=
er
>>>>>>       check", "fltering -> filtering", "illegal packets -> malicious
>>>>>>       packets", "manipulate rules -> configure rules", "managenent -=
>
>>>>>>       management", and "DDoS-attack mitigation operations ->
>>>>>> DDoS-attack
>>>>>>       mitigation".
>>>>>>
>>>>>> --------------------------------------------------------------------=
-----------------------------
>>>>>>
>>>>>> Thanks and Merry Christmas!
>>>>>>
>>>>>> Best Regards,
>>>>>> Paul
>>>>>>
>>>>>> On Fri, Dec 21, 2018 at 11:33 PM Eric Rescorla <ekr@rtfm.com> wrote:
>>>>>>
>>>>>>> Rich version of this review at:
>>>>>>> https://mozphab-ietf.devsvcdev.mozaws.net/D3181
>>>>>>>
>>>>>>>
>>>>>>> I found a number of typographical and grammar errors. Please give
>>>>>>> this
>>>>>>> document a thorough read.
>>>>>>>
>>>>>>> IMPORTANT
>>>>>>> S 1.
>>>>>>> >
>>>>>>> >      Interface to Network Security Functions (I2NSF) defines a
>>>>>>> framework
>>>>>>> >      and interfaces for interacting with Network Security Functio=
ns
>>>>>>> >      (NSFs).  The I2NSF framework allows heterogeneous NSFs
>>>>>>> developed by
>>>>>>> >      different security solution vendors to be used in the Networ=
k
>>>>>>> >      Functions Virtualization (NFV) environment [ETSI-NFV] by
>>>>>>> utilizing
>>>>>>>
>>>>>>> Much of this document cannot be understood without reading ETSI-NFV=
,
>>>>>>> so it has to be a normative reference. It also would be helpful to
>>>>>>> provide a link.
>>>>>>>
>>>>>>>
>>>>>>> S 2.
>>>>>>> >      This document uses the terminology described in [RFC7149],
>>>>>>> >      [ITU-T.Y.3300], [ONF-OpenFlow], [ONF-SDN-Architecture],
>>>>>>> >      [ITU-T.X.1252], [ITU-T.X.800], [RFC8329], [i2nsf-terminology=
],
>>>>>>> >      [consumer-facing-inf-im], [consumer-facing-inf-dm],
>>>>>>> >      [i2nsf-nsf-cap-im], [nsf-facing-inf-dm],
>>>>>>> [registration-inf-dm], and
>>>>>>> >      [nsf-triggered-steering].  In addition, the following terms
>>>>>>> are
>>>>>>>
>>>>>>> Every term in this document needs to be understandable without
>>>>>>> reference to closed specifications or internally defined. Please
>>>>>>> ensure that this is so,
>>>>>>>
>>>>>>>
>>>>>>> S 3.
>>>>>>> >      used for the I2NSF NSF-Facing Interface.
>>>>>>> >
>>>>>>> >      The Registration Interface between the Security Controller
>>>>>>> and the
>>>>>>> >      Developer's Management System can be implemented by RESTCONF
>>>>>>> >      [RFC8040].  The data model defined in [registration-inf-dm]
>>>>>>> can be
>>>>>>> >      used for the I2NSF Registration Interface.
>>>>>>>
>>>>>>> What role does the Developer's Management System play in this? I
>>>>>>> think
>>>>>>> this refers to the text above starting with "The developers (or
>>>>>>> vendors)...". Is that correct?
>>>>>>>
>>>>>>> Assuming I am correct, this seems like a potentially serious securi=
ty
>>>>>>> vulnerability in this design in that it potentially allows an insid=
e
>>>>>>> attacker at the developer to seriously weaken a system's security.
>>>>>>> What protections exist to prevent this?
>>>>>>>
>>>>>>>
>>>>>>> S 4.
>>>>>>> >      administrator wants to control the staff members' access to =
a
>>>>>>> >      particular Interner service (e.g., Example.com) during
>>>>>>> business
>>>>>>> >      hours.  The following is an example high-level security
>>>>>>> policy rule
>>>>>>> >      that the administrator requests: Block the staff members'
>>>>>>> access to
>>>>>>> >      Example.com from 9 AM to 6 PM.  The administrator sends this
>>>>>>> high-
>>>>>>> >      level security policy to the Security Controller, then the
>>>>>>> Security
>>>>>>>
>>>>>>> The text above suggests that high-level policies are via
>>>>>>> RESTCONF/YANG, but this is clearly freeform text.
>>>>>>> COMMENTS
>>>>>>> S 1.
>>>>>>> >
>>>>>>> >   1.  Introduction
>>>>>>> >
>>>>>>> >      Interface to Network Security Functions (I2NSF) defines a
>>>>>>> framework
>>>>>>> >      and interfaces for interacting with Network Security Functio=
ns
>>>>>>> >      (NSFs).  The I2NSF framework allows heterogeneous NSFs
>>>>>>> developed by
>>>>>>>
>>>>>>> Please define "Network Security Functions" here.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> S 1.
>>>>>>> >      functions in the NFV platform.  In the I2NSF framework, each
>>>>>>> NSF
>>>>>>> >      initially registers the profile of its own capabilities into
>>>>>>> the
>>>>>>> >      system in order for themselves to be available in the
>>>>>>> system.  In
>>>>>>> >      addition, the Security Controller is validated by the I2NSF
>>>>>>> Client
>>>>>>> >      (also called I2NSF User) that the user is employing, so that
>>>>>>> the user
>>>>>>> >      can request security services through the Security Controlle=
r.
>>>>>>>
>>>>>>> In this case the user is the system administrator.
>>>>>>>
>>>>>>>
>>>>>>> S 1.
>>>>>>> >      [RFC7149] to provide different security functionality such a=
s
>>>>>>> >      firewalls [opsawg-firewalls], Deep Packet Inspection (DPI),
>>>>>>> and
>>>>>>> >      Distributed Denial of Service (DDoS) attack mitigation; (iv)
>>>>>>> the use
>>>>>>> >      of NFV as supporting technology.  The implementation of I2NS=
F
>>>>>>> in
>>>>>>> >      these scenarios has allowed us to verify the applicability a=
nd
>>>>>>> >      effectiveness of the I2NSF framework for a variety of use
>>>>>>> cases.
>>>>>>>
>>>>>>> This would be easier to read with a standard bulleted list.
>>>>>>>
>>>>>>>
>>>>>>> S 2.
>>>>>>> >         network resources, which facilitates the design, delivery
>>>>>>> and
>>>>>>> >         operation of network services in a dynamic and scalable
>>>>>>> manner
>>>>>>> >         [ITU-T.Y.3300].
>>>>>>> >
>>>>>>> >      o  Firewall: A service function at the junction of two netwo=
rk
>>>>>>> >         segments that inspects every packet that attempts to cros=
s
>>>>>>> the
>>>>>>>
>>>>>>> Nit: It might not inspect *every* packet.
>>>>>>>
>>>>>>>
>>>>>>> S 4.
>>>>>>> >
>>>>>>> >   4.  Time-dependent Web Access Control Service
>>>>>>> >
>>>>>>> >      This service scenario assumes that an enterprise network
>>>>>>> >      administrator wants to control the staff members' access to =
a
>>>>>>> >      particular Interner service (e.g., Example.com) during
>>>>>>> business
>>>>>>>
>>>>>>> Nit: "Internet"
>>>>>>>
>>>>>>>
>>>>>>> S 4.
>>>>>>> >      inspection capability is required to check whether the targe=
t
>>>>>>> URL of
>>>>>>> >      a received packet is in the Example.com domain or not.
>>>>>>> >
>>>>>>> >      The Security Controller maintains the security capabilities
>>>>>>> of each
>>>>>>> >      NSF running in the I2NSF system, which have been reported by
>>>>>>> the
>>>>>>> >      Developer's Management System via the Registation interface.
>>>>>>> Based
>>>>>>>
>>>>>>> Nit: "Registration"
>>>>>>>
>>>>>>>
>>>>>>> S 4.
>>>>>>> >      currently using the network.  Based on the retrieved
>>>>>>> information, the
>>>>>>> >      Security Controller generates low-level security rules to
>>>>>>> check
>>>>>>> >      whether the source IP address of a received packet matches
>>>>>>> any one
>>>>>>> >      being used by a staff member.  In addition, the low-level
>>>>>>> security
>>>>>>> >      rules should be able to determine that a received packet is
>>>>>>> of HTTP
>>>>>>> >      protocol.  The low-level security rules for web filter check=
s
>>>>>>> that
>>>>>>>
>>>>>>> Nit: "rules"... "checks" disagree.
>>>>>>>
>>>>>>>
>>>>>>> S 6.
>>>>>>> >      translated into their packet forwarding rules, whereas NSFs
>>>>>>> enforce
>>>>>>> >      NSF-related security rules requiring the security
>>>>>>> capabilities of the
>>>>>>> >      NSFs.  For this purpose, the Security Controller instructs
>>>>>>> the SDN
>>>>>>> >      Controller via NSF-Facing Interface so that SDN forwarding
>>>>>>> elements
>>>>>>> >      can perform the required security services with flow tables
>>>>>>> under the
>>>>>>> >      supervision of the SDN Controller.
>>>>>>>
>>>>>>> I'm having some trouble understanding the difference here between
>>>>>>> NSFs
>>>>>>> and SDN elements. They both seem to be software controlled network
>>>>>>> elements. Is this just some continuum about CPU power?
>>>>>>>
>>>>>>>
>>>>>>> S 6.
>>>>>>> >      can perform the required security services with flow tables
>>>>>>> under the
>>>>>>> >      supervision of the SDN Controller.
>>>>>>> >
>>>>>>> >      As an example, let us consider two different types of
>>>>>>> security rules:
>>>>>>> >
>>>>>>> >      Rule A is a simple packet fltering rule that checks only the
>>>>>>> IP
>>>>>>>
>>>>>>> Nit: "filtering"
>>>>>>>
>>>>>>>
>>>>>>> S 6.2.
>>>>>>> >          packets that have the same call-id.
>>>>>>> >
>>>>>>> >      6.  The SDN Controller installs new rules (e.g., drop
>>>>>>> packets) into
>>>>>>> >          underlying switches.
>>>>>>> >
>>>>>>> >      7.  The illegal packets are dropped by these switches.
>>>>>>>
>>>>>>> "Illegal" is probably the wrong wrod here.
>>>>>>>
>>>>>>>
>>>>>>> S 6.3.
>>>>>>> >         is helpful to determine security policies for such a
>>>>>>> network.
>>>>>>> >
>>>>>>> >   6.3.  Attack Mitigation: Centralized DDoS-attack Mitigation
>>>>>>> System
>>>>>>> >
>>>>>>> >      A centralized DDoS-attack mitigation can manage each network
>>>>>>> resource
>>>>>>> >      and manipulate rules to each switch through a common server
>>>>>>> for DDoS-
>>>>>>>
>>>>>>> "manipulate rules to" is not grammatical.
>>>>>>>
>>>>>>>
>>>>>>> S 6.3.
>>>>>>> >
>>>>>>> >      Servers are categorized into stateless servers (e.g., DNS
>>>>>>> servers)
>>>>>>> >      and stateful servers (e.g., web servers).  For DDoS-attack
>>>>>>> >      mitigation, traffic flows in switches are dynamically
>>>>>>> configured by
>>>>>>> >      traffic flow forwarding path management according to the
>>>>>>> category of
>>>>>>> >      servers [AVANT-GUARD].  Such a managenent should consider th=
e
>>>>>>> load
>>>>>>>
>>>>>>> 1. This seems hard to understand without this reference, which is n=
ot
>>>>>>> public.
>>>>>>> 2. "management"
>>>>>>>
>>>>>>>
>>>>>>> S 6.3.
>>>>>>> >      mitigation, traffic flows in switches are dynamically
>>>>>>> configured by
>>>>>>> >      traffic flow forwarding path management according to the
>>>>>>> category of
>>>>>>> >      servers [AVANT-GUARD].  Such a managenent should consider th=
e
>>>>>>> load
>>>>>>> >      balance among the switches for the defense against DDoS
>>>>>>> attacks.
>>>>>>> >
>>>>>>> >      The procedure of DDoS-attack mitigation operations in this
>>>>>>> system is
>>>>>>>
>>>>>>> "procedure of... operations" is ungrammatical
>>>>>>>
>>>>>>>
>>>>>>
>>>>>> --
>>>>>> =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 Software
>>>>>> Sungkyunkwan University
>>>>>> Office: +82-31-299-4957
>>>>>> Email: jaehoon.paul@gmail.com
>>>>>> Personal Homepage: http://iotlab.skku.edu/people-jaehoon-jeong.php
>>>>>> <http://cpslab.skku.edu/people-jaehoon-jeong.php>
>>>>>>
>>>>>
>>>>
>>>> --
>>>> =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 Software
>>>> 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>
>>>>
>>>
>>
>> --
>> =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 Software
>> 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>
>>
>

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

<div dir=3D"auto">Susan, Diego, Sangwon, and Taejin,<div dir=3D"auto"><div =
dir=3D"auto">Could you clarify my explanation for Eric as coauthors?</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></div><br><div class=3D"gmail_quote"><div dir=3D"ltr">2018=EB=85=84 =
12=EC=9B=94 28=EC=9D=BC (=EA=B8=88) =EC=98=A4=ED=9B=84 11:09=EC=97=90 Eric =
Rescorla &lt;<a href=3D"mailto:ekr@rtfm.com">ekr@rtfm.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 =
dir=3D"ltr"><div dir=3D"ltr"><br></div><br><div class=3D"gmail_quote"><div =
dir=3D"ltr">On Thu, Dec 27, 2018 at 7:21 PM Mr. Jaehoon Paul Jeong &lt;<a h=
ref=3D"mailto:jaehoon.paul@gmail.com" target=3D"_blank" rel=3D"noreferrer">=
jaehoon.paul@gmail.com</a>&gt; wrote:<br></div><blockquote class=3D"gmail_q=
uote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,2=
04);padding-left:1ex"><div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr"><d=
iv dir=3D"ltr"><div>Eric,</div><div>Let me answer your further questions be=
low.</div><br><div class=3D"gmail_quote"><div dir=3D"ltr">On Thu, Dec 27, 2=
018 at 11:59 PM Eric Rescorla &lt;<a href=3D"mailto:ekr@rtfm.com" target=3D=
"_blank" rel=3D"noreferrer">ekr@rtfm.com</a>&gt; wrote:<br></div><blockquot=
e class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px s=
olid 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">On Wed, Dec 26, 20=
18 at 6:42 PM Mr. Jaehoon Paul Jeong &lt;<a href=3D"mailto:jaehoon.paul@gma=
il.com" target=3D"_blank" rel=3D"noreferrer">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"auto"><div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"lt=
r"><div dir=3D"ltr"><div dir=3D"ltr"><div>Hi Eric,</div><div dir=3D"auto">H=
ere are my answers inlines below.</div><br><div class=3D"gmail_quote"><div =
dir=3D"ltr">On Thu, Dec 27, 2018 at 3:44 AM Eric Rescorla &lt;<a href=3D"ma=
ilto:ekr@rtfm.com" rel=3D"noreferrer noreferrer" target=3D"_blank">ekr@rtfm=
.com</a>&gt; wrote:<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 dir=3D"ltr"><div dir=3D"ltr"><div>Paul,</div><div><br></div><div>T=
hanks for your new version. Some responses below.<br></div><div><br></div><=
/div><br><div class=3D"gmail_quote"><div dir=3D"ltr">On Tue, Dec 25, 2018 a=
t 6:42 AM Mr. Jaehoon Paul Jeong &lt;<a href=3D"mailto:jaehoon.paul@gmail.c=
om" rel=3D"noreferrer noreferrer" target=3D"_blank">jaehoon.paul@gmail.com<=
/a>&gt; wrote:<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 dir=3D"ltr"><div dir=3D"ltr">Hi Eric, Linda and Yoav,<=
div>I have reflected all the comments from Eric and submitted the revision =
-08 as follows:</div><div><a href=3D"https://tools.ietf.org/html/draft-ietf=
-i2nsf-applicability-08" rel=3D"noreferrer noreferrer" target=3D"_blank">ht=
tps://tools.ietf.org/html/draft-ietf-i2nsf-applicability-08</a><br></div><d=
iv><br></div><div>The changes are described in Appendix A of -08 document a=
s follows:</div><div>------------------------------------------------------=
-------------------------------------------</div><div><div>Appendix A.=C2=
=A0 Changes from draft-ietf-i2nsf-applicability-07</div><div><br></div><div=
>=C2=A0 =C2=A0The following changes have been made from</div><div>=C2=A0 =
=C2=A0draft-ietf-i2nsf-applicability-07:</div><div><br></div><div>=C2=A0 =
=C2=A0o=C2=A0 This version has reflected all the comments from Eric Rescorl=
a who</div><div>=C2=A0 =C2=A0 =C2=A0 is a Security Area Director as follows=
.</div><div><br></div><div>=C2=A0 =C2=A0o=C2=A0 In Section 1, Network Secur=
ity Function (NFV) is defined in the</div><div>=C2=A0 =C2=A0 =C2=A0 viewpoi=
nt of the I2NSF framework.</div><div><br></div><div>=C2=A0 =C2=A0o=C2=A0 In=
 Section 1, a user using the I2NSF User is clarified as a system</div><div>=
=C2=A0 =C2=A0 =C2=A0 administrator in the I2NSF framework.</div><div><br></=
div><div>=C2=A0 =C2=A0o=C2=A0 In Section 1, as the applicability of the I2N=
SF framework, four</div><div>=C2=A0 =C2=A0 =C2=A0 different scenarios are r=
epresented with a standard bulleted list.</div><div><br></div><div>=C2=A0 =
=C2=A0o=C2=A0 The standard document about ETSI-NFV is moved to Normative</d=
iv><div>=C2=A0 =C2=A0 =C2=A0 References.</div><div><br></div><div>=C2=A0 =
=C2=A0o=C2=A0 In Section 2, key terms (e.g., Network Function, Network Secu=
rity</div><div>=C2=A0 =C2=A0 =C2=A0 Function, Network Functions Virtualizat=
ion, and Servive Function</div><div>=C2=A0 =C2=A0 =C2=A0 Chaining) are inte=
rnally defined along with the reference to open</div><div>=C2=A0 =C2=A0 =C2=
=A0 specifications.</div><div><br></div><div>=C2=A0 =C2=A0o=C2=A0 In Sectio=
n 2, the definition of Firewall is corrected such that</div><div>=C2=A0 =C2=
=A0 =C2=A0 some suspicious packets are inspected by the firewall rather tha=
n</div><div>=C2=A0 =C2=A0 =C2=A0 every packet.</div><div><br></div><div>=C2=
=A0 =C2=A0o=C2=A0 In Section 3, for a Developer&#39;s Management System, th=
e problem of</div><div>=C2=A0 =C2=A0 =C2=A0 an inside attacker is addressed=
, and a possible solution for the</div><div>=C2=A0 =C2=A0 =C2=A0 inside att=
acks is suggested through I2NSF NSF monitoring</div><div>=C2=A0 =C2=A0 =C2=
=A0 functionality.</div></div></div></div></div></blockquote><div><br></div=
><div>I&#39;m still pretty concerned about this. Standardizing a situation =
in which the</div><div>developer of your firewall has real-time management-=
level access to</div><div>that firewall seems extremely insecure, especiall=
y when that access is</div><div>authenticated via conventional credentials =
that are online as part of</div><div>the transaction (as opposed to softwar=
e builds which can be signed</div><div>offline). This doesn&#39;t seem like=
 a best practice. Why is it necessary?</div><div></div></div></div></blockq=
uote></div></div></div></div></div></div></div><div dir=3D"auto"><br></div>=
<div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr"><div di=
r=3D"ltr"><div dir=3D"ltr"><div class=3D"gmail_quote"><blockquote class=3D"=
gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(20=
4,204,204);padding-left:1ex"><div dir=3D"ltr"><div class=3D"gmail_quote"><d=
iv><br></div></div></div></blockquote><div>=C2=A0=3D&gt;=C2=A0 The develope=
r of a firewall does not have real-time management-level access</div><div>=
=C2=A0 =C2=A0 =C2=A0 =C2=A0even though its management system works the cont=
rol plane as part of the I2NSF system.</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=
=A0The developer&#39;s management system provides the Security Controller w=
ith</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0the interface (i.e., Registration =
Interface) that is used to register the capability of</div><div>=C2=A0 =C2=
=A0 =C2=A0 =C2=A0the developer&#39;s security network function (i.e., firew=
all), to search an NSF for the required capability for a high-level securit=
y policy, and to help the lifecycle management</div><div>=C2=A0 =C2=A0 =C2=
=A0 =C2=A0of such an NSF for the Security Controller through an NFV interfa=
ce (i.e., Ve-Vnfm interface) with the NFV&#39;s MANO.=C2=A0</div></div></di=
v></div></div></div></div></div></div></blockquote><div><br></div><div>I do=
n&#39;t understand the distinction you are drawing here. Under what conditi=
ons can the developer modify the behavior of the I2NSF system? Can it do so=
 at any time and without explicit action by the admin.<br></div><div><br></=
div></div></div></blockquote><div>=C2=A0=3D&gt;=C2=A0 The developer means a=
 security solution vendor (e.g., McAfee and Symantec) who provides the I2NS=
F system with security solutions,=C2=A0</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=
=A0such as firewall, web filter, DPI, IDS/IPS, and DDoS-attack mitigator. A=
ctually, the developer&#39;s management system</div><div>=C2=A0 =C2=A0 =C2=
=A0 =C2=A0cannot modify the behavior of the I2NSF system in run-time as lon=
g as the vendor doesn&#39;t have any backdoor to=C2=A0</div><div>=C2=A0 =C2=
=A0 =C2=A0 =C2=A0their developer&#39;s management system.</div><div>=C2=A0 =
=C2=A0 =C2=A0 =C2=A0This developer&#39;s management system facilitates the =
security service government by the Security Controller=C2=A0</div><div>=C2=
=A0 =C2=A0 =C2=A0 =C2=A0by providing the Security Controller with the Regis=
tration Interface for the capability registration and instantiation/de-inst=
antiation=C2=A0</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0of the image of a secu=
rity service function.</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0Thus, only the =
administrator can modify the behavior of the I2NSF system.</div><div>=C2=A0=
 =C2=A0 =C2=A0 =C2=A0</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0Maybe,</div><div=
>=C2=A0 =C2=A0 =C2=A0 =C2=A0Diego Lopez can clarify my answer because he is=
 the editor of RFC 8329 (Framework for Interface to Network Security Functi=
ons):</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0<a href=3D"https://tools.ietf.or=
g/html/rfc8329" target=3D"_blank" rel=3D"noreferrer">https://tools.ietf.org=
/html/rfc832</a></div></div></div></div></div></div></blockquote><div><br><=
/div><div>Yeah, I&#39;m not really following this. What functions can the D=
eveloper perform on the system.</div><div><br></div><br><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"><div dir=
=3D"ltr"><div dir=3D"ltr"><div class=3D"gmail_quote"><blockquote class=3D"g=
mail_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 class=3D"gmail_quote"><bl=
ockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-lef=
t:1px solid rgb(204,204,204);padding-left:1ex"><div dir=3D"auto"><div dir=
=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr=
"><div dir=3D"ltr"><div class=3D"gmail_quote"><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"><div dir=3D"ltr"><div class=3D"gmail_quote"><blockquot=
e class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px s=
olid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr"><div dir=3D"ltr"><=
div dir=3D"ltr"><div><div>=C2=A0 =C2=A0o=C2=A0 In Section 4, an XML file fo=
r the RESTCONF/YANG for the time-</div><div>=C2=A0 =C2=A0 =C2=A0 dependent =
web access control is pointed out with a reference to</div><div>=C2=A0 =C2=
=A0 =C2=A0 the Consumer-Facing Interface&#39;s data model</div><div>=C2=A0 =
=C2=A0 =C2=A0 [consumer-facing-inf-dm].</div></div></div></div></div></bloc=
kquote><div><br></div><div>I didn&#39;t follow this change. The example you=
 give of a high level security</div><div>policy is clearly freeform text an=
d then you talk about XML. Is this just</div><div>example a summary of the =
semantics of something which would actually be an</div><div>XML file? Somet=
hing else?</div></div></div></blockquote><div>=C2=A0</div><div dir=3D"auto"=
>=C2=A0 =3D&gt; Even though the high-level security policy looks like a fre=
eform text,=C2=A0 it is formatted</div><div>=C2=A0 =C2=A0 =C2=A0 in an XML =
according to the high-level security policy YANG model for the Consumer-Fac=
ing Interface.</div><div>=C2=A0 =C2=A0 =C2=A0 Yes, it is just an example of=
 a summary of the semantics for such a high-level security policy,=C2=A0</d=
iv><div>=C2=A0 =C2=A0 =C2=A0 which is represented as an XML file.</div><div=
>=C2=A0 =C2=A0 =C2=A0 Here it an XML file for the web filter from the Consu=
mer-Facing Interface Data Model document</div><div>=C2=A0 =C2=A0 =C2=A0 (<a=
 href=3D"https://tools.ietf.org/html/draft-ietf-i2nsf-consumer-facing-inter=
face-dm-02" rel=3D"noreferrer noreferrer" target=3D"_blank">https://tools.i=
etf.org/html/draft-ietf-i2nsf-consumer-facing-interface-dm-02</a>):</div><d=
iv><br></div><div>=C2=A0 =C2=A0 =C2=A0 You can see the XML file from=C2=A0<=
/div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0<a href=3D"https://tools.ietf.org/html=
/draft-ietf-i2nsf-consumer-facing-interface-dm-02#page-49" rel=3D"noreferre=
r noreferrer" target=3D"_blank">https://tools.ietf.org/html/draft-ietf-i2ns=
f-consumer-facing-interface-dm-02#page-49</a></div><div><br></div><div>=C2=
=A0 =C2=A0 =C2=A0 &lt;?xml version=3D&quot;1.1&quot; encoding=3D&quot;UTF-8=
&quot;?&gt;</div><div>=C2=A0&lt;rpc message-id=3D&quot;4&quot; xmlns=3D&quo=
t;urn:ietf:params:xml:ns:restconf:base:1.0&quot;&gt;</div><div>=C2=A0 &lt;e=
dit-config&gt;</div><div>=C2=A0 =C2=A0&lt;target&gt;</div><div>=C2=A0 =C2=
=A0 &lt;running/&gt;</div><div>=C2=A0 =C2=A0&lt;/target&gt;</div><div>=C2=
=A0 =C2=A0 &lt;config&gt;</div><div>=C2=A0 =C2=A0 =C2=A0&lt;i2nsf-cf-interf=
ace-wf-req nc:operation=3D&quot;create&quot;&gt;</div><div>=C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0&lt;policy-wf&gt;</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0=
 =C2=A0 =C2=A0 =C2=A0&lt;rule-wf&gt;</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&lt;rule-wf-id&gt;03&lt;/rule-wf-id&gt;</=
div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&lt;=
rule-wf-name&gt;wf-policy-example&lt;/rule-wf-name&gt;</div><div>=C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&lt;rule-wf-date&gt;201=
8.10.26/14:03:17&lt;/rule-wf-date&gt;</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0=
 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&lt;event&gt;</div><div>=C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&lt;event-id&=
gt;04&lt;/event-id&gt;</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&lt;event-name&gt;wf&lt;/event-name&gt;</=
div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0&lt;event-date&gt;2018.10.26/14:03:17&lt;/event-date&gt;</div><di=
v>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0&lt;event-type&gt;wf&lt;/event-type&gt;</div><div>=C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&lt;event-map-group&=
gt;04&lt;/event-map-group&gt;</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&lt;enable&gt;True&lt;/enable&gt;<=
/div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&lt=
;/event&gt;</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0&lt;condition&gt;</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&lt;condition-id&gt;04&lt;/conditi=
on-id&gt;</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0=
 =C2=A0 =C2=A0 =C2=A0&lt;source-ip&gt;192.168.1.3&lt;/source-ip&gt;</div><d=
iv>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0&lt;destination-url&gt;<a href=3D"http://www.facebook.com" rel=3D"nor=
eferrer noreferrer" target=3D"_blank">www.facebook.com</a>&lt;/destination-=
url&gt;</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0&lt;time-information&gt;</div><div>=C2=A0 =C2=A0 =C2=A0=
 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&lt;b=
egin-time&gt;09:00&lt;/begin-time&gt;</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0=
 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&lt;end-time=
&gt;18:00&lt;/end-time&gt;</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&lt;/time-information&gt;</div><div>=
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0&lt;match-direction&gt;default&lt;/match-direction&gt;</div><div>=C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&lt;ex=
eption&gt;00&lt;/exeption&gt;</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0&lt;/condition&gt;</div><div>=C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&lt;action&gt;</div><div>=C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&l=
t;action-id&gt;04&lt;/action-id&gt;</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&lt;action-name&gt;action-w=
f&lt;/action-name&gt;</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&lt;action-date&gt;2018.10.26/14:03:17&lt=
;/action-date&gt;</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&lt;primary-action&gt;REJECT&lt;/primary-act=
ion&gt;</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0&lt;secondary-action&gt;LOG&lt;/secondary-action&gt;</d=
iv><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&lt;/=
action&gt;</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0&lt;precedence&gt;none&lt;/precedence&gt;</div><div>=C2=A0 =C2=A0=
 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&lt;owner&gt;</div><div>=C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&lt;owner-id&gt;03&l=
t;/owner-id&gt;</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0&lt;name&gt;i2nsf-admin&lt;/name&gt;</div><div>=C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&lt;/owner&gt;</div><div>=C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&lt;/rule-wf&gt;</div><div>=C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0&lt;/policy-wf&gt;</div><div>=C2=A0 =C2=A0 =C2=
=A0&lt;/i2nsf-cf-interface-wf-req&gt;</div><div>=C2=A0 =C2=A0 &lt;/config&g=
t;</div><div>=C2=A0 &lt;/edit-config&gt;</div><div>=C2=A0&lt;/rpc&gt;</div>=
<div>=C2=A0 =3D&gt;<span style=3D"white-space:pre-wrap">	</span>In the abov=
e, source ip is used for the employees.<br></div><div><div><span style=3D"w=
hite-space:pre-wrap">=C2=A0 </span>Instead of the source ip, we can make an=
d use &quot;source group&quot; for employees that can be translated=C2=A0</=
div><div dir=3D"auto">=C2=A0 into a set of IP addresses of the source group=
.</div></div></div></div></div></div></div></div></div></div></blockquote><=
div><br></div><div>You need to make this clear, then. It would probably be =
easier to just show the XML and then provide the text summary.<br></div><di=
v><br></div></div></div></blockquote><div>=C2=A0 =3D&gt; Okay. I will inclu=
de a simplified example XML code for web filter and provide the text summar=
y as below.</div><div><br></div><div><div>=C2=A0 =C2=A0This service scenari=
o assumes that an enterprise network</div><div>=C2=A0 =C2=A0administrator w=
ants to control the staff members&#39; access to a</div><div>=C2=A0 =C2=A0p=
articular Internet service (e.g., Example.com) during business</div><div>=
=C2=A0 =C2=A0hours.=C2=A0 The following is an example high-level security p=
olicy rule</div><div>=C2=A0 =C2=A0for a web filter that the administrator r=
equests: Block the staff members&#39; access to Example.com from 9 AM to 6 =
PM.=C2=A0=C2=A0</div><div>=C2=A0 =C2=A0Here is an example XML code for this=
 web filter:</div><div>&lt;I2NSF&gt;</div><div>=C2=A0 =C2=A0 &lt;name&gt;bl=
ock_website&lt;/name&gt;</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 &lt;cond&gt;=
</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 &lt;src&gt;Staff_Membe=
r&#39;s_PC&lt;/src&gt;</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
&lt;dest&gt;Example.com&lt;/dest&gt;</div><div><span style=3D"white-space:p=
re-wrap">		</span>=C2=A0 =C2=A0 &lt;time-span-start&gt;9:00AM&lt;/time-span=
-start&gt;</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 &lt;time-spa=
n-end&gt;-6:00PM&lt;/time-span-end&gt;</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=
=A0 &lt;/cond&gt;</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 &lt;action&gt;block=
&lt;action&gt;</div><div>&lt;/I2NSF&gt;</div><div><br></div><div>=C2=A0 =C2=
=A0The security policy name is &quot;bloc_website&quot; with the tag &quot;=
name&quot;.</div><div>=C2=A0 =C2=A0The filtering condition has the source g=
roup &quot;Staff_Member&#39;s_PC&quot; with the tag &quot;src&quot;,</div><=
div>=C2=A0 =C2=A0the destination website &quot;Example.com&quot; with the t=
ag &quot;dest&quot;,</div><div>=C2=A0 =C2=A0the filtering start time is the=
 time &quot;9:00AM&quot; with the tag &quot;

time-span-start&quot;,=C2=A0</div><div>=C2=A0 =C2=A0and the filtering end t=
ime is the time &quot;6:00PM&quot; with the tag &quot;

time-span-end&quot;.</div><div>=C2=A0 =C2=A0The action is to &quot;block&qu=
ot; the packets satisfying the above condition,=C2=A0</div><div>=C2=A0 =C2=
=A0that is, to drop those packets</div></div></div></div></div></div></div>=
</blockquote><div><br></div><div>LGTM.</div><div><br></div><div> <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"><div dir=3D"ltr"><div dir=3D"ltr"><div class=3D"gmail_quote"><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 class=3D"gmail_quote"><div></div><div><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"auto"><div dir=3D"ltr"><div di=
r=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"lt=
r"><div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"ma=
rgin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:=
1ex"><div dir=3D"ltr"><div class=3D"gmail_quote"><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"><div dir=3D"ltr">=
<div><div>=C2=A0 =C2=A0o=C2=A0 In Section 6, the definitions of an SDN forw=
arding element and an</div><div>=C2=A0 =C2=A0 =C2=A0 NSF are clarified such=
 that an SDN forwarding element is a switch</div><div>=C2=A0 =C2=A0 =C2=A0 =
running as either a hardware middle box or a software virtual</div><div>=C2=
=A0 =C2=A0 =C2=A0 switch, and an NSF is a virtual network function for a se=
curity</div><div>=C2=A0 =C2=A0 =C2=A0 service.</div></div></div></div></div=
></blockquote><div><br></div><div>This wasn&#39;t clear to me either. Based=
 on this text it would seem that</div><div>you could run an NSF on an SDN e=
lement, so it&#39;s not clear why they</div><div>are disjoint sets. Can you=
 give me more information here?<br></div></div></div></blockquote></div></d=
iv></div></div></div></div></div><div dir=3D"auto"><br></div><div dir=3D"lt=
r"><div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr"><div=
 dir=3D"ltr"><div class=3D"gmail_quote"><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 class=3D"gmail_quote"><div></div></div=
></div></blockquote></div></div></div></div></div></div></div><div dir=3D"a=
uto">=C2=A0=3D&gt; An SDN switch can run as a virtual network function like=
 an NSF, but the main functionality of the SDN switch is packet forwarding =
with a flow table along with simple filtering rules. More complicated secur=
ity services can be done at dedicated NSFs. For example, there is the Open =
Virtual Switch (OVS) project for such a software-based SDN switch:=C2=A0<a =
href=3D"https://www.openvswitch.org" target=3D"_blank" rel=3D"noreferrer">h=
ttps://www.openvswitch.org</a></div><div dir=3D"auto"><br></div><div dir=3D=
"auto">Thus, the SDN switches and NSFs are logically disjoint sets though a=
ll of them=C2=A0 can run physically as virtual network functions.</div></di=
v></blockquote><div><br></div><div>I&#39;m sorry, this still isn&#39;t clea=
r, at least to me. How can I look at a given software element and determine=
 whether it&#39;s an NSF or a virtualized SDN switch?<br></div></div></div>=
</blockquote><div><br></div><div>=C2=A0=3D&gt; The distinction is logically=
 done such that the NFV system having the I2NSF system categorizes some VNF=
s as NSFs for dedicated security services</div><div>=C2=A0 =C2=A0 =C2=A0 an=
d some VNFs as virtualized SDN switches for packet switching and simple fil=
tering rule enforcement.</div><div><br></div><div>=C2=A0 =C2=A0 =C2=A0If th=
ere is an expert in the NFV, please let us know for further clarification.<=
/div></div></div></div></div></div></blockquote><div><br></div><div>I&#39;m=
 not following this either, so that would definitely help.<br></div><div><b=
r></div><div>-Ekr</div><div><br></div><blockquote class=3D"gmail_quote" sty=
le=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);paddi=
ng-left:1ex"><div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D=
"ltr"><div class=3D"gmail_quote"><div><br></div><div>=C2=A0 =C2=A0 =C2=A0Th=
anks.</div><div><br></div><div>=C2=A0 =C2=A0 =C2=A0Best Regards,</div><div>=
=C2=A0 =C2=A0 =C2=A0Paul</div><div>=C2=A0</div><blockquote class=3D"gmail_q=
uote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,2=
04);padding-left:1ex"><div dir=3D"ltr"><div class=3D"gmail_quote"><div></di=
v><div><br></div><div>-Ekr<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"auto"><div dir=3D"auto"><br></div><div dir=3D"auto">=
If you have further questions, please let me know.</div><div dir=3D"auto"><=
br></div><div dir=3D"auto">Thanks.</div><div dir=3D"auto">=C2=A0</div><div =
dir=3D"auto">Best Regards,</div><div dir=3D"auto">Paul</div><div dir=3D"ltr=
"><div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr"><div =
dir=3D"ltr"><div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" st=
yle=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padd=
ing-left:1ex"><div dir=3D"ltr"><div class=3D"gmail_quote"><div></div><div><=
br></div><div>-Ekr</div><div><br></div><blockquote class=3D"gmail_quote" st=
yle=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padd=
ing-left:1ex"><div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr"><div><div>=
<br></div><div>=C2=A0 =C2=A0o=C2=A0 In Section 6.3, a flow forwarding path =
management scheme in</div><div>=C2=A0 =C2=A0 =C2=A0 [AVANT-GUARD] is descri=
bed in a self-contained way as follows.</div><div>=C2=A0 =C2=A0 =C2=A0 For =
DDoS-attack mitigation, the forwarding of traffic flows in</div><div>=C2=A0=
 =C2=A0 =C2=A0 switches can be dynamically configured such that malicious t=
raffic</div><div>=C2=A0 =C2=A0 =C2=A0 flows are handled by the paths separa=
ted from normal traffic flows</div><div>=C2=A0 =C2=A0 =C2=A0 in order to mi=
nimize the impact of those malicious traffic on the</div><div>=C2=A0 =C2=A0=
 =C2=A0 the servers.=C2=A0 This flow path separation can be done by a flow<=
/div><div>=C2=A0 =C2=A0 =C2=A0 forwarding path management scheme based on [=
AVANT-GUARD].</div><div><br></div><div>=C2=A0 =C2=A0o=C2=A0 Some typos are =
corrected such as &quot;Interner -&gt; Internet&quot;,</div><div>=C2=A0 =C2=
=A0 =C2=A0 &quot;Registation -&gt; Registration&quot;, &quot;The low-level =
security rules for</div><div>=C2=A0 =C2=A0 =C2=A0 web filter checks -&gt; T=
he low-level security rules for web filter</div><div>=C2=A0 =C2=A0 =C2=A0 c=
heck&quot;, &quot;fltering -&gt; filtering&quot;, &quot;illegal packets -&g=
t; malicious</div><div>=C2=A0 =C2=A0 =C2=A0 packets&quot;, &quot;manipulate=
 rules -&gt; configure rules&quot;, &quot;managenent -&gt;</div><div>=C2=A0=
 =C2=A0 =C2=A0 management&quot;, and &quot;DDoS-attack mitigation operation=
s -&gt; DDoS-attack</div><div>=C2=A0 =C2=A0 =C2=A0 mitigation&quot;.</div><=
/div><div>-----------------------------------------------------------------=
--------------------------------=C2=A0</div><div>=C2=A0<br></div><div>Thank=
s and Merry Christmas!</div><div><br></div><div>Best Regards,</div><div>Pau=
l</div></div></div></div><br><div class=3D"gmail_quote"><div dir=3D"ltr">On=
 Fri, Dec 21, 2018 at 11:33 PM Eric Rescorla &lt;<a href=3D"mailto:ekr@rtfm=
.com" rel=3D"noreferrer noreferrer" target=3D"_blank">ekr@rtfm.com</a>&gt; =
wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0=
px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir=
=3D"ltr"><div dir=3D"ltr">Rich version of this review at:<br><a href=3D"htt=
ps://mozphab-ietf.devsvcdev.mozaws.net/D3181" rel=3D"noreferrer noreferrer"=
 target=3D"_blank">https://mozphab-ietf.devsvcdev.mozaws.net/D3181</a><br><=
br><br>I found a number of typographical and grammar errors. Please give th=
is<br>document a thorough read.<br><br>IMPORTANT<br>S 1.<br>&gt;=C2=A0=C2=
=A0 <br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Interface to Network Security Fu=
nctions (I2NSF) defines a framework<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 a=
nd interfaces for interacting with Network Security Functions<br>&gt;=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0 (NSFs).=C2=A0 The I2NSF framework allows heterogen=
eous NSFs developed by<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 different secu=
rity solution vendors to be used in the Network<br>&gt;=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0 Functions Virtualization (NFV) environment [ETSI-NFV] by utili=
zing<br><br>Much of this document cannot be understood without reading ETSI=
-NFV,<br>so it has to be a normative reference. It also would be helpful to=
<br>provide a link.<br><br><br>S 2.<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 T=
his document uses the terminology described in [RFC7149],<br>&gt;=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0 [ITU-T.Y.3300], [ONF-OpenFlow], [ONF-SDN-Architecture=
],<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 [ITU-T.X.1252], [ITU-T.X.800], [RF=
C8329], [i2nsf-terminology],<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 [consume=
r-facing-inf-im], [consumer-facing-inf-dm],<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0 [i2nsf-nsf-cap-im], [nsf-facing-inf-dm], [registration-inf-dm], and<=
br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 [nsf-triggered-steering].=C2=A0 In ad=
dition, the following terms are<br><br>Every term in this document needs to=
 be understandable without<br>reference to closed specifications or interna=
lly defined. Please<br>ensure that this is so,<br><br><br>S 3.<br>&gt;=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0 used for the I2NSF NSF-Facing Interface.<br>&gt=
;=C2=A0=C2=A0 <br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 The Registration Inter=
face between the Security Controller and the<br>&gt;=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0 Developer&#39;s Management System can be implemented by RESTCONF<=
br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 [RFC8040].=C2=A0 The data model defin=
ed in [registration-inf-dm] can be<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 us=
ed for the I2NSF Registration Interface.<br><br>What role does the Develope=
r&#39;s Management System play in this? I think<br>this refers to the text =
above starting with &quot;The developers (or<br>vendors)...&quot;. Is that =
correct?<br><br>Assuming I am correct, this seems like a potentially seriou=
s security<br>vulnerability in this design in that it potentially allows an=
 inside<br>attacker at the developer to seriously weaken a system&#39;s sec=
urity.<br>What protections exist to prevent this?<br><br><br>S 4.<br>&gt;=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 administrator wants to control the staff mem=
bers&#39; access to a<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 particular Inte=
rner service (e.g., Example.com) during business<br>&gt;=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0 hours.=C2=A0 The following is an example high-level security p=
olicy rule<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 that the administrator req=
uests: Block the staff members&#39; access to<br>&gt;=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0 Example.com from 9 AM to 6 PM.=C2=A0 The administrator sends this=
 high-<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 level security policy to the S=
ecurity Controller, then the Security<br><br>The text above suggests that h=
igh-level policies are via<br>RESTCONF/YANG, but this is clearly freeform t=
ext.<br>COMMENTS<br>S 1.<br>&gt;=C2=A0=C2=A0 <br>&gt;=C2=A0=C2=A0 1.=C2=A0 =
Introduction<br>&gt;=C2=A0=C2=A0 <br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Int=
erface to Network Security Functions (I2NSF) defines a framework<br>&gt;=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0 and interfaces for interacting with Network Sec=
urity Functions<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 (NSFs).=C2=A0 The I2N=
SF framework allows heterogeneous NSFs developed by<br><br>Please define &q=
uot;Network Security Functions&quot; here.<br><br><br><br><br>S 1.<br>&gt;=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 functions in the NFV platform.=C2=A0 In the =
I2NSF framework, each NSF<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 initially r=
egisters the profile of its own capabilities into the<br>&gt;=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0 system in order for themselves to be available in the sy=
stem.=C2=A0 In<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 addition, the Security=
 Controller is validated by the I2NSF Client<br>&gt;=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0 (also called I2NSF User) that the user is employing, so that the =
user<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 can request security services th=
rough the Security Controller.<br><br>In this case the user is the system a=
dministrator.<br><br><br>S 1.<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 [RFC714=
9] to provide different security functionality such as<br>&gt;=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0 firewalls [opsawg-firewalls], Deep Packet Inspection (DP=
I), and<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Distributed Denial of Service=
 (DDoS) attack mitigation; (iv) the use<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0 of NFV as supporting technology.=C2=A0 The implementation of I2NSF in<b=
r>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 these scenarios has allowed us to veri=
fy the applicability and<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 effectivenes=
s of the I2NSF framework for a variety of use cases.<br><br>This would be e=
asier to read with a standard bulleted list.<br><br><br>S 2.<br>&gt;=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 network resources, which facilit=
ates the design, delivery and<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0 operation of network services in a dynamic and scalable manner=
<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 [ITU-T.Y.3300].<br=
>&gt;=C2=A0=C2=A0 <br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 o=C2=A0 Firewall: =
A service function at the junction of two network<br>&gt;=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 segments that inspects every packet that att=
empts to cross the<br><br>Nit: It might not inspect *every* packet.<br><br>=
<br>S 4.<br>&gt;=C2=A0=C2=A0 <br>&gt;=C2=A0=C2=A0 4.=C2=A0 Time-dependent W=
eb Access Control Service<br>&gt;=C2=A0=C2=A0 <br>&gt;=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0 This service scenario assumes that an enterprise network<br>&gt;=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 administrator wants to control the staff mem=
bers&#39; access to a<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 particular Inte=
rner service (e.g., Example.com) during business<br><br>Nit: &quot;Internet=
&quot;<br><br><br>S 4.<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 inspection cap=
ability is required to check whether the target URL of<br>&gt;=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0 a received packet is in the Example.com domain or not.<b=
r>&gt;=C2=A0=C2=A0 <br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 The Security Cont=
roller maintains the security capabilities of each<br>&gt;=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0 NSF running in the I2NSF system, which have been reported b=
y the<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Developer&#39;s Management Syst=
em via the Registation interface.=C2=A0 Based<br><br>Nit: &quot;Registratio=
n&quot;<br><br><br>S 4.<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 currently usi=
ng the network.=C2=A0 Based on the retrieved information, the<br>&gt;=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0 Security Controller generates low-level security r=
ules to check<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 whether the source IP a=
ddress of a received packet matches any one<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0 being used by a staff member.=C2=A0 In addition, the low-level secur=
ity<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 rules should be able to determine=
 that a received packet is of HTTP<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 pr=
otocol.=C2=A0 The low-level security rules for web filter checks that<br><b=
r>Nit: &quot;rules&quot;... &quot;checks&quot; disagree.<br><br><br>S 6.<br=
>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 translated into their packet forwarding=
 rules, whereas NSFs enforce<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 NSF-rela=
ted security rules requiring the security capabilities of the<br>&gt;=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0 NSFs.=C2=A0 For this purpose, the Security Control=
ler instructs the SDN<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Controller via =
NSF-Facing Interface so that SDN forwarding elements<br>&gt;=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0 can perform the required security services with flow tables=
 under the<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 supervision of the SDN Con=
troller.<br><br>I&#39;m having some trouble understanding the difference he=
re between NSFs<br>and SDN elements. They both seem to be software controll=
ed network<br>elements. Is this just some continuum about CPU power?<br><br=
><br>S 6.<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 can perform the required se=
curity services with flow tables under the<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0 supervision of the SDN Controller.<br>&gt;=C2=A0=C2=A0 <br>&gt;=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0 As an example, let us consider two different ty=
pes of security rules:<br>&gt;=C2=A0=C2=A0 <br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0 Rule A is a simple packet fltering rule that checks only the IP<br><=
br>Nit: &quot;filtering&quot;<br><br><br>S 6.2.<br>&gt;=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 packets that have the same call-id.<br=
>&gt;=C2=A0=C2=A0 <br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 6.=C2=A0 The SDN C=
ontroller installs new rules (e.g., drop packets) into<br>&gt;=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 underlying switches.<br>&gt;=C2=
=A0=C2=A0 <br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 7.=C2=A0 The illegal packe=
ts are dropped by these switches.<br><br>&quot;Illegal&quot; is probably th=
e wrong wrod here.<br><br><br>S 6.3.<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0 is helpful to determine security policies for such a net=
work.<br>&gt;=C2=A0=C2=A0 <br>&gt;=C2=A0=C2=A0 6.3.=C2=A0 Attack Mitigation=
: Centralized DDoS-attack Mitigation System<br>&gt;=C2=A0=C2=A0 <br>&gt;=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0 A centralized DDoS-attack mitigation can manage=
 each network resource<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 and manipulate=
 rules to each switch through a common server for DDoS-<br><br>&quot;manipu=
late rules to&quot; is not grammatical.<br><br><br>S 6.3.<br>&gt;=C2=A0=C2=
=A0 <br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Servers are categorized into sta=
teless servers (e.g., DNS servers)<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 an=
d stateful servers (e.g., web servers).=C2=A0 For DDoS-attack<br>&gt;=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0 mitigation, traffic flows in switches are dynamica=
lly configured by<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 traffic flow forwar=
ding path management according to the category of<br>&gt;=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0 servers [AVANT-GUARD].=C2=A0 Such a managenent should consider=
 the load<br><br>1. This seems hard to understand without this reference, w=
hich is not<br>public.<br>2. &quot;management&quot;<br><br><br>S 6.3.<br>&g=
t;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 mitigation, traffic flows in switches are =
dynamically configured by<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 traffic flo=
w forwarding path management according to the category of<br>&gt;=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0 servers [AVANT-GUARD].=C2=A0 Such a managenent should=
 consider the load<br>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 balance among the =
switches for the defense against DDoS attacks.<br>&gt;=C2=A0=C2=A0 <br>&gt;=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 The procedure of DDoS-attack mitigation oper=
ations in this system is<br><br>&quot;procedure of... operations&quot; is u=
ngrammatical<br><br></div></div>
</blockquote></div><br clear=3D"all"><div><br></div>-- <br><div dir=3D"ltr"=
 class=3D"m_7083261673679643115gmail-m_-5775707567964940138gmail-m_-4645637=
776060181596gmail-m_7571128782014320286m_-6695152896369925623gmail-m_-60798=
7677208405722gmail-m_-9111533177071645325gmail_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 So=
ftware<br>Sungkyunkwan University<br>Office: +82-31-299-4957<br>Email: <a h=
ref=3D"mailto:jaehoon.paul@gmail.com" rel=3D"noreferrer noreferrer" target=
=3D"_blank">jaehoon.paul@gmail.com</a><br>Personal Homepage: <a href=3D"htt=
p://cpslab.skku.edu/people-jaehoon-jeong.php" rel=3D"noreferrer noreferrer"=
 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"m_7083261673679643115gmail-m_-5775707567964940138gmail-m_-4645637=
776060181596gmail-m_7571128782014320286m_-6695152896369925623gmail_signatur=
e"><div dir=3D"ltr"><div><div dir=3D"ltr"><div><div dir=3D"ltr"><div><div d=
ir=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 Professo=
r<br>Department of Software<br>Sungkyunkwan University<br>Office: +82-31-29=
9-4957<br>Email: <a href=3D"mailto:jaehoon.paul@gmail.com" rel=3D"noreferre=
r noreferrer" target=3D"_blank">jaehoon.paul@gmail.com</a>,=C2=A0<a href=3D=
"mailto:pauljeong@skku.edu" style=3D"font-size:12.8px" rel=3D"noreferrer no=
referrer" target=3D"_blank">pauljeong@skku.edu</a><br>Personal Homepage: <a=
 href=3D"http://cpslab.skku.edu/people-jaehoon-jeong.php" rel=3D"noreferrer=
 noreferrer" target=3D"_blank">http://iotlab.skku.edu/people-jaehoon-jeong.=
php</a><br></div></div></div></div></div></div></div></div></div></div></di=
v></div></div></div></div>
</blockquote></div></div>
</blockquote></div><br clear=3D"all"><div><br></div>-- <br><div dir=3D"ltr"=
 class=3D"m_7083261673679643115gmail-m_-5775707567964940138gmail_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<b=
r>Department of Software<br>Sungkyunkwan University<br>Office: +82-31-299-4=
957<br>Email: <a href=3D"mailto:jaehoon.paul@gmail.com" target=3D"_blank" r=
el=3D"noreferrer">jaehoon.paul@gmail.com</a>,=C2=A0<a href=3D"mailto:paulje=
ong@skku.edu" style=3D"font-size:12.8px" target=3D"_blank" rel=3D"noreferre=
r">pauljeong@skku.edu</a><br>Personal Homepage: <a href=3D"http://cpslab.sk=
ku.edu/people-jaehoon-jeong.php" target=3D"_blank" rel=3D"noreferrer">http:=
//iotlab.skku.edu/people-jaehoon-jeong.php</a><br></div></div></div></div><=
/div></div></div></div></div></div></div></div>
</blockquote></div></div>
</blockquote></div>

--00000000000011c114057e166f54--

