--Apple-Mail=_1EFF15CC-95EA-4A35-8535-3E217B94E3CA
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
charset=utf-8
Hi Linda,
The abstraction layer here is the one =E2=80=9Con top=E2=80=9D the NSFs, =
that expose their features as capabilities that are manageable by the =
controller. Using an analogy with OpenFlow, the OpenFlow protocol =
provides an abstraction layer so the forwarding elements can translate =
their status and events in terms of the protocol commands and responses.
Be goode,
=20
> On 17 Jun 2016, at 11:10 , Linda Dunbar <[email protected]> =
wrote:
>=20
> John,
> =20
> My thinking maybe too simplistic.
> I picture a =E2=80=9CController=E2=80=9D having two ports,
> - one port connecting to clients (which can be another domain =
controller or Overlay network controller), interface from this port is =
=E2=80=9CService layer interface=E2=80=9D
> - another port connecting to NSFs, the interface from this port =
is =E2=80=9Ccapability layer interface=E2=80=9D.
> =20
> So I thought that the Service Layer interface is the North Bound =
interface to the Controller, the capability interface is the south bound =
to the controller.
> =20
> What extra meaning does it carry with the wording =E2=80=9Cabstraction =
Layer=E2=80=9D ?
> Capability Layer: Defines an abstraction layer that exposes a set of =
{features that are available from a managed entity} of the I2NSF system.
> Thank you.
> =20
> Linda
> =20
> From: John Strassner [mailto:[email protected] =
<mailto:[email protected]>]=20
> Sent: Thursday, June 16, 2016 12:58 AM
> To: Linda Dunbar; John Strassner
> Cc: Susan Hares; DIEGO LOPEZ GARCIA ([email protected] =
<mailto:[email protected]>); [email protected] =
<mailto:[email protected]>
> Subject: Re: questions about some terminologies defined by =
draft-ietf-i2nsf-terminology-00
> =20
> HI Linda,
> =20
> I don't see the conflict in the two definitions. If I substitute the =
first (within braces) into the second, I get:
> =20
> Capability Layer: Defines an abstraction layer that exposes a set of =
{features that are available from a managed entity} of the I2NSF system.
> =20
> When I look at the Charter's Capability Layer, I think we're still OK =
- the Charter "...specifies how to control and monitor NSFs at a =
functional level...", and Capabilities (the features that are available) =
are essential for planning how to control and monitor NSFs.
> =20
> Features (i.e., capabilities) are independent of interface (northbound =
or southbound). Would you like us to add that point to the terminology =
I-D?
> =20
> best regards,
> John
> =20
> =20
> On Wed, Jun 15, 2016 at 8:40 AM, Linda Dunbar <[email protected] =
<mailto:[email protected]>> wrote:
> Dear Authors:
> =20
> The term =E2=80=9CCapability Layer=E2=80=9D defined by the =
=E2=80=9Cdraft-ietf-i2nsf-terminology-00=E2=80=9D carries different =
meaning than the =E2=80=9CCapability Layer=E2=80=9D used by the I2NSF =
charter.
> =20
> =E2=80=9Cdraft-ietf-i2nsf-terminology-00=E2=80=9D:
> Capability: Defines a set of features that are available from a =
managed entity (see also I2NSF Capability).
> =20
> Capability Layer: Defines an abstraction layer that exposes a set of =
capabilities of the I2NSF system.
> =20
> I2NSF Charter:
> I2NSF will specify interfaces at two functional levels for the control =
and monitoring of network security functions:
>=20
> The I2NSF Capability Layer specifies how to control and monitor NSFs =
at a functional implementation level. The term "Functional =
Implementation" is used to emphasize that the rules (for control and =
monitor) of NSFs have to be implementable by most NSFs. I2NSF will =
standardize a set of interfaces by which a security controller can =
invoke, operate, and monitor NSFs.
>=20
> The I2NSF Service Layer defines how clients' security policies may be =
expressed to a security controller. The controller implements its =
policies according to the various capabilities provided by the I2NSF =
Capability Layer. The I2NSF Service Layer also allows the client to =
monitor the client specific policies.
>=20
> =20
> If we use the definitions by the =
=E2=80=9Cdraft-ietf-i2nsf-terminology-00=E2=80=9D, we should create a =
different terminology to represent the =E2=80=9CSouth bound Interface=E2=80=
=9D between Controller and NSF.
> =20
> Thanks, Linda
> =20
> =20
>=20
>=20
>=20
> --=20
> regards,
> John
--
"Esta vez no fallaremos, Doctor Infierno"
Dr Diego R. Lopez
Telefonica I+D
http://people.tid.es/diego.lopez/
e-mail: [email protected]
Tel: +34 913 129 041
Mobile: +34 682 051 091
----------------------------------
--Apple-Mail=_1EFF15CC-95EA-4A35-8535-3E217B94E3CA
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"">The abstraction layer here is the one =E2=80=9Con top=E2=80=9D =
the NSFs, that expose their features as capabilities that are manageable =
by the controller. Using an analogy with OpenFlow, the OpenFlow protocol =
provides an abstraction layer so the forwarding elements can translate =
their status and events in terms of the protocol commands and =
responses.</div><div class=3D""><br class=3D""></div><div class=3D"">Be =
goode,</div><div class=3D""> <br class=3D""><div><blockquote =
type=3D"cite" class=3D""><div class=3D"">On 17 Jun 2016, at 11:10 , =
Linda Dunbar <<a href=3D"mailto:[email protected]"; =
class=3D"">[email protected]</a>> wrote:</div><br =
class=3D"Apple-interchange-newline"><div class=3D""><div =
class=3D"WordSection1" style=3D"page: WordSection1; font-family: =
LucidaGrande; font-size: 11px; font-style: normal; font-variant: normal; =
font-weight: normal; letter-spacing: normal; line-height: 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""><span =
style=3D"font-size: 11pt; font-family: Calibri, sans-serif; color: =
rgb(31, 73, 125);" class=3D"">John,<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""> </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"">My thinking maybe too simplistic.<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"">I picture a =E2=80=9CController=E2=80=9D =
having two ports,<o:p class=3D""></o:p></span></div><div style=3D"margin: =
0in 0in 0.0001pt 0.5in; font-size: 12pt; font-family: 'Times New Roman', =
serif; text-indent: -0.25in;" class=3D""><span style=3D"font-size: 11pt; =
font-family: Calibri, sans-serif; color: rgb(31, 73, 125);" =
class=3D""><span class=3D"">-<span style=3D"font-style: normal; =
font-variant: normal; font-weight: normal; font-size: 7pt; line-height: =
normal; font-family: 'Times New Roman';" =
class=3D""> <span =
class=3D"Apple-converted-space"> </span></span></span></span><span =
style=3D"font-size: 11pt; font-family: Calibri, sans-serif; color: =
rgb(31, 73, 125);" class=3D"">one port connecting to clients (which can =
be another domain controller or Overlay network controller), interface =
from this port is =E2=80=9CService layer interface=E2=80=9D<o:p =
class=3D""></o:p></span></div><div style=3D"margin: 0in 0in 0.0001pt =
0.5in; font-size: 12pt; font-family: 'Times New Roman', serif; =
text-indent: -0.25in;" class=3D""><span style=3D"font-size: 11pt; =
font-family: Calibri, sans-serif; color: rgb(31, 73, 125);" =
class=3D""><span class=3D"">-<span style=3D"font-style: normal; =
font-variant: normal; font-weight: normal; font-size: 7pt; line-height: =
normal; font-family: 'Times New Roman';" =
class=3D""> <span =
class=3D"Apple-converted-space"> </span></span></span></span><span =
style=3D"font-size: 11pt; font-family: Calibri, sans-serif; color: =
rgb(31, 73, 125);" class=3D"">another port connecting to NSFs, the =
interface from this port is =E2=80=9Ccapability layer interface=E2=80=9D.<=
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""> </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"">So =
I thought that the Service Layer interface is the North Bound interface =
to the Controller, the capability interface is the south bound to the =
controller.<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""> </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"">What extra meaning does it carry with the wording =
=E2=80=9Cabstraction Layer=E2=80=9D ?<o:p =
class=3D""></o:p></span></div><div style=3D"margin: 0in 0in 0.0001pt =
0.5in; font-size: 12pt; font-family: 'Times New Roman', serif;" =
class=3D""><em class=3D""><span style=3D"font-size: 9pt; font-family: =
'PT Serif', serif; color: rgb(34, 34, 34);" class=3D"">Capability Layer: =
Defines an abstraction layer that exposes a set of {features that are =
available from a managed entity} of the I2NSF system.</span></em><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"">Thank you.<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""> </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"">Linda<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""> </span></div><div =
style=3D"border-style: solid none none; border-top-color: rgb(181, 196, =
223); 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: =
10pt; font-family: Tahoma, sans-serif;" class=3D"">From:</span></b><span =
style=3D"font-size: 10pt; font-family: Tahoma, sans-serif;" =
class=3D""><span class=3D"Apple-converted-space"> </span>John =
Strassner [<a href=3D"mailto:[email protected]"; style=3D"color: purple; =
text-decoration: underline;" =
class=3D"">mailto:[email protected]</a>]<span =
class=3D"Apple-converted-space"> </span><br class=3D""><b =
class=3D"">Sent:</b><span =
class=3D"Apple-converted-space"> </span>Thursday, June 16, 2016 =
12:58 AM<br class=3D""><b class=3D"">To:</b><span =
class=3D"Apple-converted-space"> </span>Linda Dunbar; John =
Strassner<br class=3D""><b class=3D"">Cc:</b><span =
class=3D"Apple-converted-space"> </span>Susan Hares; DIEGO LOPEZ =
GARCIA (<a href=3D"mailto:[email protected]"; style=3D"color: =
purple; text-decoration: underline;" =
class=3D"">[email protected]</a>);<span =
class=3D"Apple-converted-space"> </span><a =
href=3D"mailto:[email protected]"; style=3D"color: purple; text-decoration: =
underline;" class=3D"">[email protected]</a><br class=3D""><b =
class=3D"">Subject:</b><span =
class=3D"Apple-converted-space"> </span>Re: questions about some =
terminologies defined by draft-ietf-i2nsf-terminology-00<o:p =
class=3D""></o:p></span></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""> </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 Linda,<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""> </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"">I don't see the conflict in the two =
definitions. If I substitute the first (within braces) into the second, =
I get:<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""> </o:p></div></div><div class=3D""><div style=3D"margin: =
0in 0in 0.0001pt 0.5in; font-size: 12pt; font-family: 'Times New Roman', =
serif;" class=3D""><em class=3D""><span style=3D"font-size: 9pt; =
font-family: 'PT Serif', serif; color: rgb(34, 34, 34);" =
class=3D"">Capability Layer: Defines an abstraction layer that exposes a =
set of {features that are available from a managed entity} of the I2NSF =
system.</span></em><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""> </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"">When I look at the Charter's Capability Layer, I =
think we're still OK - the Charter "...specifies how to control and =
monitor NSFs at a functional level...", and Capabilities (the features =
that are available) are essential for planning how to control and =
monitor NSFs.<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""> </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"">Features (i.e., capabilities) are independent of =
interface (northbound or southbound). Would you like us to add that =
point to the terminology I-D?<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""> </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"">best regards,<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"">John<o:p =
class=3D""></o:p></div></div><div class=3D""><div style=3D"margin: 0in =
0in 0.0001pt 0.5in; font-size: 12pt; font-family: 'Times New Roman', =
serif;" class=3D""><o:p class=3D""> </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""><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"">On Wed, Jun 15, 2016 at 8:40 AM, Linda Dunbar <<a =
href=3D"mailto:[email protected]"; target=3D"_blank" style=3D"color: =
purple; text-decoration: underline;" =
class=3D"">[email protected]</a>> wrote:<o:p =
class=3D""></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"">Dear Authors:<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""></o:p></div><div style=3D"margin: 0in =
0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;" =
class=3D"">The term =E2=80=9CCapability Layer=E2=80=9D defined by the =
=E2=80=9Cdraft-ietf-i2nsf-terminology-00=E2=80=9D carries different =
meaning than the =E2=80=9CCapability Layer=E2=80=9D used by the =
I2NSF charter.<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: 10pt; font-family: Courier;" =
class=3D""> </span><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"">=E2=80=9Cdraft-ietf-i2nsf-terminology-00=E2=80=9D:<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""><i =
class=3D""><span style=3D"font-size: 9pt; font-family: 'PT Serif', =
serif; color: rgb(34, 34, 34);" class=3D"">Capability: Defines a set of =
features that are available from a managed entity (see also I2NSF =
Capability).</span></i><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""><i class=3D""><span style=3D"font-size: 9pt; =
font-family: 'PT Serif', serif; color: rgb(34, 34, 34);" =
class=3D""> </span></i><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""><i class=3D""><span =
style=3D"font-size: 9pt; font-family: 'PT Serif', serif; color: rgb(34, =
34, 34);" class=3D"">Capability Layer: Defines an abstraction layer that =
exposes a set of capabilities of the I2NSF system.</span></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""> <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"">I2NSF Charter:<o:p class=3D""></o:p></div><p =
class=3D"MsoNormal" style=3D"margin: 0in 0in 6.3pt 0.5in; font-size: =
12pt; font-family: 'Times New Roman', serif;"><i class=3D""><span =
style=3D"font-size: 9pt; font-family: 'PT Serif', serif; color: rgb(34, =
34, 34);" class=3D"">I2NSF will specify interfaces at two functional =
levels for the control and monitoring of network security =
functions:</span></i><o:p class=3D""></o:p></p><p class=3D"MsoNormal" =
style=3D"margin: 0in 0in 6.3pt 0.5in; font-size: 12pt; font-family: =
'Times New Roman', serif;"><i class=3D""><span style=3D"font-size: 9pt; =
font-family: 'PT Serif', serif; color: rgb(34, 34, 34);" class=3D"">The =
I2NSF Capability Layer specifies how to control and monitor NSFs at a =
functional implementation level. The term "Functional Implementation" is =
used to emphasize that the rules (for control and monitor) of NSFs have =
to be implementable by most NSFs. I2NSF will standardize a set of =
interfaces by which a security controller can invoke, operate, and =
monitor NSFs.<br class=3D""><br class=3D"">The I2NSF Service Layer =
defines how clients' security policies may be expressed to a security =
controller. The controller implements its policies according to the =
various capabilities provided by the I2NSF Capability Layer. The I2NSF =
Service Layer also allows the client to monitor the client specific =
policies.</span></i><o:p class=3D""></o:p></p><div style=3D"margin: 0in =
0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;" =
class=3D""> <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"">If we use the definitions by the =
=E2=80=9Cdraft-ietf-i2nsf-terminology-00=E2=80=9D, we should create a =
different terminology to represent the =E2=80=9CSouth bound Interface=E2=80=
=9D between Controller and NSF.<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""></o:p></div><div =
style=3D"margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times =
New Roman', serif;" class=3D"">Thanks, Linda<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""></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""></o:p></div></div></div></div><div =
style=3D"margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times =
New Roman', serif;" class=3D""><br class=3D""><br clear=3D"all" =
class=3D""><br class=3D"">--<span =
class=3D"Apple-converted-space"> </span><o:p =
class=3D""></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"">regards,<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"">John</div></div></div></div></div></div></blockquote></div><br =
class=3D""><div apple-content-edited=3D"true" class=3D"">
<div style=3D"color: rgb(0, 0, 0); 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; word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D"">--<br class=3D"">"Esta vez no fallaremos, Doctor Infierno"<br =
class=3D""><br class=3D"">Dr Diego R. Lopez<br class=3D"">Telefonica =
I+D<br class=3D""><a href=3D"http://people.tid.es/diego.lopez/"; =
class=3D"">http://people.tid.es/diego.lopez/</a><br class=3D""><br =
class=3D"">e-mail: [email protected]<br class=3D"">Tel: =
+34 913 129 041<br class=3D"">Mobile: +34 682 051 091<br =
class=3D"">----------------------------------</div>
</div>
<br class=3D""></div></body></html>=
--Apple-Mail=_1EFF15CC-95EA-4A35-8535-3E217B94E3CA--
________________________________
Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, puede
contener información privilegiada o confidencial y es para uso exclusivo de la
persona o entidad de destino. Si no es usted. el destinatario indicado, queda
notificado de que la lectura, utilización, divulgación y/o copia sin
autorización puede estar prohibida en virtud de la legislación vigente. Si ha
recibido este mensaje por error, le rogamos que nos lo comunique inmediatamente
por esta misma vía y proceda a su destrucción.
The information contained in this transmission is privileged and confidential
information intended only for the use of the individual or entity named above.
If the reader of this message is not the intended recipient, you are hereby
notified that any dissemination, distribution or copying of this communication
is strictly prohibited. If you have received this transmission in error, do not
read it. Please immediately reply to the sender that you have received this
communication in error and then delete it.
Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinatário, pode
conter informação privilegiada ou confidencial e é para uso exclusivo da pessoa
ou entidade de destino. Se não é vossa senhoria o destinatário indicado, fica
notificado de que a leitura, utilização, divulgação e/ou cópia sem autorização
pode estar proibida em virtude da legislação vigente. Se recebeu esta mensagem
por erro, rogamos-lhe que nos o comunique imediatamente por esta mesma via e
proceda a sua destruição
_______________________________________________
I2nsf mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/i2nsf
