From: "Bogaert, Bart (Nokia - BE)" <bart.bogaert@nokia.com>
To: Martin Bjorklund <mbj@tail-f.com>
Thread-Topic: [netmod] BBF extensions to ietf-entity
Thread-Index: AQHSAdSd3dfqTKzQR3WYPaIL6IHWCqBfqKbg///gwACAACKLAIAK8sAAgAAiKtD//9+uAIAAI2Tg///pnAAABLZKoP//6JUA///dQsA=
Date: Mon, 5 Sep 2016 12:34:26 +0000
Message-ID: <D62E05768DBAFF42A72B9F4954476D65010EAB10A2@FR712WXCHMBA09.zeu.alcatel-lucent.com>
References: <D62E05768DBAFF42A72B9F4954476D65010EAB0FCB@FR712WXCHMBA09.zeu.alcatel-lucent.com>
 <20160905.133346.1118879196013167357.mbj@tail-f.com>
 <D62E05768DBAFF42A72B9F4954476D65010EAB1064@FR712WXCHMBA09.zeu.alcatel-lucent.com>
 <20160905.142452.2018983005061250255.mbj@tail-f.com>
In-Reply-To: <20160905.142452.2018983005061250255.mbj@tail-f.com>
Accept-Language: en-US
Content-Language: en-US
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature";
 micalg=SHA1; boundary="----=_NextPart_000_0160_01D20782.99F3A470"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/qQagbXyzwOVZufPvEn3qEZTJemU>
Cc: "netmod@ietf.org" <netmod@ietf.org>
Subject: Re: [netmod] BBF extensions to ietf-entity
Precedence: list

------=_NextPart_000_0160_01D20782.99F3A470
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

"Bogaert, Bart (Nokia - BE)" <bart.bogaert@nokia.com> wrote:
> "Bogaert, Bart (Nokia - BE)" <bart.bogaert@nokia.com> wrote:
> > Hi Martin,
> > 
> > "Bogaert, Bart (Nokia - BE)" <bart.bogaert@nokia.com> wrote:
> > > From: Martin Bjorklund [mailto:mbj@tail-f.com]
> > > Sent: 05 September 2016 12:41
> > > To: Bogaert, Bart (Nokia - BE)
> > > Cc: netmod@ietf.org
> > > Subject: Re: [netmod] BBF extensions to ietf-entity
> > > 
> > > "Bogaert, Bart (Nokia - BE)" <bart.bogaert@nokia.com> wrote:
> > > > "Bogaert, Bart (Nokia - BE)" <bart.bogaert@nokia.com> wrote:
> > > > > Hi Martin,
> > > > > 
> > > > > In BBF this pointer from HW to interface will be available (it 
> > > > > has been proposed in the Berling BBF meeting already).
> > > > 
> > > > I assume this is done as an augmentation?  Is it an augmentation 
> > > > to the interface list, or to the hardware list?  I.e., is it a 
> > > > pointer from an interface to the hardware, or the other way around?
> > > > [Bart Bogaert] It is an augmentation to the hardware list
> > > 
> > > Ok.  Would it be possible to have the pointer the other way around?
> > > If not, why?
> > > 
> > > [Bart Bogaert] So you mean from entity to interfaces?  Similar to 
> > > the "stack" in interfaces we assumed it more logical to point from 
> > > the higher to the lower layer.  That is the reason why the 
> > > reference is from the interface to the entity.
> > 
> > Aha, I mis-read your text "augemntation to the hardware list" as 
> > meaning that the augment target was the hardware list.
> > 
> > Good, I agree that the pointer from the high-level to lower-level is
> better.
> > 
> > So then my question remains; why isn't the pre-provisioning handled 
> > in the interface layer, and the hardware list is purely for monitoring?
> > 
> > [Bart Bogaert] Can you explain exactly what you mean by this 
> > statement?  The link is there to connect the HW to the logical 
> > interfaces defined on top of this HW.  It also allows "visualization"
> > on management GUIs to which HW an interface is linked.  Is this what 
> > you
> mean by "monitoring"?
> 
> You explained that the reason for making the hardware list 
> configurable was to allow pre-provisioning:
> 
>     2. the network operator determines that a node will "run out" of 
>     available ports and hence wants to start planning new 
>     configuration and hence he wants to configure some boards in the 
>     empty slots and even may want to start to pre-configure certain 
>     data of the ports contained by these boards.  In that case we 
>     need the RW leaf to indicate which board type will be inserted 
>     as the service that can be offered depends on the board being
inserted.
>     When the board is inserted, the planned configuration can 
>     directly be applied to the newly inserted board (given the fact 
>     that the detected class is the same
> 
> My comment was that pre-provisioning can be handled by the interface 
> layer, rather than the hardware layer.
> 
> But maybe you are right in the sense that if we support any config 
> true parameters for the hardware, we should also support 
> pre-provisioning of these parameters.
> 
> What kind of data do you expect the operator to be able to 
> pre-configure in this list?
> 
> [Bart Bogaert] Assume you would have a node with a number of slots 
> (which are currently empty - so no board has been plugged yet) then it 
> should be possible for an operator to plan a configuration meaning 
> that a board can planned to be present in the first slot and that e.g. 
> mgf-name, model-name, parent-rel-pos and may be other parameters could 
> be configured by the operator.  In case there is a more "extensive" HW 
> stacking we may also have to allow setting of the class of an entity, 
> indicate in which entity the new entity will be created (so reflecting 
> in setting of a contained-in leaf in the RW section)

Here's my view of how pre-configuration would work.  Let me know if you
agree or not.

We have a list of components that can be (pre)configured.  Each entry has a
set of leafs that identifies the component somehow, and a set of
configuration parameters to be applied to the component.  If the system
finds a physical component that matches the identification criteria leafs,
then the corresponding configuration parameters are applied.
[Bart Bogaert] More or less but it could be that a system is initially
deployed with a minimum set of boards and the system gets extended when the
request for services grows (so boards are planned and get inserted some time
after).  For boards that are present when the systems starts I agree that
the system is able to detect what has been inserted.

In the simplest case (which is what we have today in ietf-entity), the
identification leaf is just the name of the component.  This means that in
order to do pre-provisioning, the operator needs to be able to predict the
name of the component.
[Bart Bogaert] Indeed, but in case of pre-provisioning it is not predicting,
the network operator actually tells what the configuration has to look like
(and in case the detected configuration differs from what was intended, the
system generates a mismatch alarm).

By also adding the leaf 'class' I suspect that this would be used as an
identification leaf, so that both the 'name' and 'class' have to match in
order for the rest of the parameters to be applied?
[Bart Bogaert] This could be indeed a possible intention.

/Bart


/martin



> 
> /Bart
> 
> /martin
> 
> 
> 
> > 
> > 
> > /martin
> > 
> > 
> > > 
> > > Bart
> > > 
> > > 
> > > /martin
> > > 
> > > 
> > > > 
> > > > Bart
> > > > 
> > > > I would prefer to view the hardware list as just monitoring 
> > > > (config
> > > > false) [1], and have config true pointers from the higher-level 
> > > > concepts back to the hardware [2].  Possibly with config false
> > > back-pointers.
> > > > 
> > > > [1] this doesn't preclude the config true list in current
ietf-entity.
> > > > 
> > > > [2] this pointer is (as noted) often implicit in the interface 
> > > > name
> > today.
> > > > 
> > > > 
> > > > /martin
> > > > 
> > > > 
> > > > 
> > > > 
> > > > 
> > > > > 
> > > > > Best regards - Vriendelijke groeten, Bart Bogaert 
> > > > > Broadband-Access System Architect Data Contact number +32 3
> > > > > 2408310
> > > > > (+32 477 673952)
> > > > > 
> > > > > NOKIA
> > > > > Copernicuslaan 50, 2018 Antwerp, Belgium Fortis 220-0002334-42 
> > > > > VAT BE
> > > > > 0404 621 642 Register of Legal Entities Antwerp
> > > > > 
> > > > > <<
> > > > > This message (including any attachments) contains confidential 
> > > > > information intended for a specific individual and purpose, 
> > > > > and is protected by law. If you are not the intended 
> > > > > recipient, you should delete this message. Any disclosure, 
> > > > > copying, or distribution of this message, or the taking of any 
> > > > > action based on it, is strictly prohibited without the prior 
> > > > > consent of its
> author.
> > > > > >> 
> > > > > 
> > > > > 
> > > > > -----Original Message-----
> > > > > From: Martin Bjorklund [mailto:mbj@tail-f.com]
> > > > > Sent: 29 August 2016 11:06
> > > > > To: Bogaert, Bart (Nokia - BE)
> > > > > Cc: netmod@ietf.org
> > > > > Subject: Re: [netmod] BBF extensions to ietf-entity
> > > > > 
> > > > > Hi,
> > > > > 
> > > > > [We had mail server problems during the weekend, so this reply 
> > > > > might not get the thread's history right.]
> > > > > 
> > > > > "Bogaert, Bart (Nokia - BE)" <bart.bogaert@nokia.com> wrote:
> > > > > > Martin Bjorklund <mbj@tail-f.com> wrote:
> > > > > > "Bogaert, Bart (Nokia - BE)" <bart.bogaert@nokia.com> wrote:
> > > > > > > I would like to bring this to the ietf-entity group.  
> > > > > > > Currently BBF is proposing to add new RW leafs to the 
> > > > > > > entity object.  This is done in the context of plugable 
> > > > > > > entities and hence it means that when an operator (via a 
> > > > > > > NC client) configures a plugable item it is required to 
> > > > > > > define the entity type.  For this reason additional RW 
> > > > > > > attributes are
> needed.
> > > > > > > Two of the new leafs are class and contained-in (same as
> > > > > the RO class leaf).
> > > > > > > 
> > > > > > > -          class: we think that the class leaf needs to be
> > mandatory
> > > > but
> > > > > > > adding this via an augment is not possible as we can't add 
> > > > > > > a mandatory leaf via an augment.  Making class implicit 
> > > > > > > for the client based on "some information" exchanged 
> > > > > > > between device vendors and management applications is 
> > > > > > > maybe not such a sound
> > > > approach.
> > > > > > 
> > > > > > Can you explain in more detail how this would be used?  The 
> > > > > > idea is that 'class' is a property of the physical hw, and 
> > > > > > that the underlying system provides this info.  I can see 
> > > > > > that it could be useful for the client to set this if the 
> > > > > > system can't do the classification (i.e., the system-set 
> > > > > > value is 'unknown').  But that's probably not the use case you
had in mind?
> > > > > > 
> > > > > > [Bart Bogaert] Assume you have a system with a number of 
> > > > > > slots that can hold several different cards and the system 
> > > > > > was deployed in the field with some cards inserted and some 
> > > > > > other slots that were still left empty.  When an operator 
> > > > > > wants to extend the system we can have
> > > > > > 2
> > > > > ways of doing this:
> > > > > > 1. a field engineer goes 'on-site' and plugs cards in the
system.
> 
> > > > > > If done this way, the system itself can detect what has been 
> > > > > > inserted and we do not really need the RW leafs.  However in 
> > > > > > this case an operator has to wait configuring user services 
> > > > > > on these cards until they are
> > > > > inserted.
> > > > > > 2. the network operator determines that a node will "run out" 
> > > > > > of available ports and hence wants to start planning new 
> > > > > > configuration and hence he wants to configure some boards in 
> > > > > > the empty slots and even may want to start to pre-configure 
> > > > > > certain data of the ports contained by these boards.  In 
> > > > > > that case we need the RW leaf to indicate which board type 
> > > > > > will be inserted as the service that can be offered depends 
> > > > > > on the board being
> > inserted.
> > > > > > When the board is inserted, the planned configuration can 
> > > > > > directly be applied to the newly inserted board (given the 
> > > > > > fact that the detected class is the same
> > > > > as the planned class).
> > > > > 
> > > > > Shouldn't this be handled by the support for pre-configuration 
> > > > > in the interfaces data model?  I.e., the general model would 
> > > > > be that the entity/hardware list is monitoring of the hardware 
> > > > > that is really present, and other models that need to refer to 
> > > > > this hardware (like
> > > > > interfaces) support pre-configuration.
> > > > > 
> > > > > The interface model lacks an explicit pointer to the 
> > > > > entity/hardware model; but in many systems this reference is 
> > > > > implicit in the name of the
> > > > interface.
> > > > > 
> > > > > 
> > > > > /martin
> > > > > 
> > > > > 
> > > > > 
> > > > > > There are customers using method 1 and other customers use 
> > > > > > method
> 2.
> > > > > > 
> > > > > > > -          contained-in: for plugable items contained-in
> requires
> > to
> > > > be
> > > > > > > mandatory too as a plugable item can't be "floating" in 
> > > > > > > the
> > device.
> > > > > > 
> > > > > > Can you explain in more detail what this means, and provide 
> > > > > > some use cases?
> > > > > >
> > > > > > [Bart Bogaert] For DSL we are faced with "wiring" aspects 
> > > > > > that "ripple through" to the MDF.  So assume we again have a 
> > > > > > system with plugable
> > > > > slots.
> > > > > > If we have 2 slots containing the same type of board (same
> > > > > > class) and the operator is applying the pre-configuration 
> > > > > > mode of working (method
> > > > > > 2 in above), we have to be sure that user A, connected to 
> > > > > > the first port of the board plugged in the first slot will 
> > > > > > really be in
> > > slot 1.
> > > > > > If the NC client has no means to detect which board is 
> > > > > > plugged in which slot (they are both of the same class) we 
> > > > > > need other means to ensure the containment is as intended 
> > > > > > (and user A being connected to the first port of the board 
> > > > > > in slot A is also visualized as such on the GUI of the NC 
> > > > > > client).  Using the serial number of the board seems not 
> > > > > > very practical as board may break and are sent to repair or 
> > > > > > replaced by another board of the same type but with a 
> > > > > > different serial number.  I do not think operators will like 
> > > > > > it a lot to manage a system in a manual way based on these 
> > > > > > attributes hence also a need to plan
> > > > > a board in a specific slot.
> > > > > 

------=_NextPart_000_0160_01D20782.99F3A470
Content-Type: application/x-pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIP/TCCA7Ew
ggKZoAMCAQICEBErBTlXKN63QvT+VRPTt1EwDQYJKoZIhvcNAQEFBQAwQzEXMBUGA1UEChMOQWxj
YXRlbCBMdWNlbnQxKDAmBgNVBAMTH0FsY2F0ZWwgTHVjZW50IEludGVybmFsIFJvb3QgQ0EwHhcN
MDgxMTAzMTU0MTE2WhcNMjgxMTAzMTU0MTE2WjBDMRcwFQYDVQQKEw5BbGNhdGVsIEx1Y2VudDEo
MCYGA1UEAxMfQWxjYXRlbCBMdWNlbnQgSW50ZXJuYWwgUm9vdCBDQTCCASIwDQYJKoZIhvcNAQEB
BQADggEPADCCAQoCggEBAL5IGBVth8afQdnpuLDI0Z37GgIcPWznOOzFJUV1gVbztqQ5CIxkVL4K
soAfLzc8LQHqNl2Nk3YbVBputIyCe2nzGsRjQeVt+HO2PV7h2YpMQlVd+XGsmpJ4fAP3A38wkTl6
tFPAYspyUFvjNON1J3BJE/2cuY7apvn9ZfSz99x7y4QBZh3hvm4g5Fn7mK04/q7K6O4Z8Y6zkSxG
ZFNyZ6NIuAPNCODZASqYnHiAgtEcCR4WPs6rj+Y8MU0q56ddwuIZ0qeP2ScHY0wVtnmqXzHyCzEQ
Eb2eJCsGpXFwUalVaxPUZEVoVDfjO+2ZN5gNJrGMTu7Mv9k1WG0LR3zZ1QsCAwEAAaOBoDCBnTAL
BgNVHQ8EBAMCAYYwDwYDVR0TAQH/BAUwAwEB/zAdBgNVHQ4EFgQUB6yyWvZhiXxcfOvilycpaQyK
H/AwEAYJKwYBBAGCNxUBBAMCAQAwTAYDVR0gBEUwQzBBBgRVHSAAMDkwNwYIKwYBBQUHAgEWK2h0
dHA6Ly93d3cuYWxjYXRlbC1sdWNlbnQuY29tL1BLSS9jcC9jcC5odG0wDQYJKoZIhvcNAQEFBQAD
ggEBADBMWG3WQyC6+mBzuuFuCGqJAiC4v+TQ3ZErd5KKSRGh8dwjzK5L2C51wJPVe6EAjb59CEb2
p2aPKSkoMrCC8seBRM/bs23DMyna1Jr9Q5EZDrmRqBLJy3Cs8NFpa/cKb6SkegFHcB/vi+SYgSdR
BwoNE5+y6MRPXcEBadI/9W8Zlkk5sJ3w55e+i8OCNg/fDYAQuJPa+hD3/byWGxUgGSMNGQ/GS2st
NETAa5Z/88Sh9FHk2BtrxSz7jPtekKhjsidD2ANJZTCyj9iRB+Nt9FEetNpcN6ke1FlepRbCsV10
I0y6weLwZ34h2GWbN9qEOSQV88NBA149a5ugJ/oCbHEwggTdMIIDxaADAgECAgoanQrOAAAAAAAG
MA0GCSqGSIb3DQEBBQUAMEMxFzAVBgNVBAoTDkFsY2F0ZWwgTHVjZW50MSgwJgYDVQQDEx9BbGNh
dGVsIEx1Y2VudCBJbnRlcm5hbCBSb290IENBMB4XDTA4MTEyMTIxNTcyOFoXDTE4MTEyMTIyMDcy
OFowgYUxEzARBgoJkiaJk/IsZAEZFgNjb20xFjAUBgoJkiaJk/IsZAEZFgZsdWNlbnQxFDASBgoJ
kiaJk/IsZAEZFgRuYTAyMRcwFQYDVQQKEw5BbGNhdGVsIEx1Y2VudDEnMCUGA1UEAxMeQWxjYXRl
bCBMdWNlbnQgSW50ZXJuYWwgU3ViIENBMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA
2Ocmcli3LbVU6TRh+JLMtquBr5/grS+gzfN5YL/lauFCHmDlF7kNQvxtDWqwNpOkzb97CwWcVsdf
kyWAiGzVWeRIrYGhK/xNPFRYXOKYXLGqxFWkltZkYpSRudHzjTneUC4EVdMXnREMu8FTC0CM38Vb
xMvQ+ygjEyicg2QT9lZHWkKP9kCI1818P+AmS7905t6kXR9Q2m1GjcCa0KqARPGX/xe2toQS+Vdi
UwDary1Enk8j19KFmvFg1bhY2mNSHgzN2AWnhsOi/EID1SalzBwHylByB/UbbEv2dZUsAdMuOtYt
Z/8dM1axS0d3fW7q7mAYV5uM42mYX9o1B/RzjwIDAQABo4IBjjCCAYowDwYDVR0TAQH/BAUwAwEB
/zAdBgNVHQ4EFgQU2exrvZZYIvfYpnfN/k2B77qXvRIwCwYDVR0PBAQDAgHGMBAGCSsGAQQBgjcV
AQQDAgEAMBkGCSsGAQQBgjcUAgQMHgoAUwB1AGIAQwBBMB8GA1UdIwQYMBaAFAesslr2YYl8XHzr
4pcnKWkMih/wMHgGA1UdHwRxMG8wbaBroGmGOWh0dHA6Ly9zZXJ2aWNlcy5zdXBwb3J0LmFsY2F0
ZWwtbHVjZW50LmNvbS9QS0kvcm9vdENBLmNybIYsaHR0cDovL3d3dy5hbGNhdGVsLWx1Y2VudC5j
b20vUEtJL3Jvb3RDQS5jcmwwgYIGCCsGAQUFBwEBBHYwdDA4BggrBgEFBQcwAoYsaHR0cDovL3d3
dy5hbGNhdGVsLWx1Y2VudC5jb20vUEtJL3Jvb3RDQS5jcnQwOAYIKwYBBQUHMAKGLGh0dHA6Ly93
d3cuYWxjYXRlbC1sdWNlbnQuY29tL1BLSS9yb290Q0EuY3J0MA0GCSqGSIb3DQEBBQUAA4IBAQCl
GxDp5Z1IDjIEz8VaTEWa8Q1OWUbXwsszdoNg5Gg3F1a2VFFVegmsrpt4axbESlgE6AT/rkUUiyjb
EhcUgY2OHdeKN5Gc7VOGh9D7SER9peARwSwx4NYRrsIaRXDrUswWAM6T6ilDUogjKYk3uK2zZ6Vy
7z3JewxVlhpeSsNPQSMoyNibKkYLRoh6rvz94vB0mvcT0uVx7xowPNoTOjjGRAk4J/MBaNOupvwf
RfPmwRetdnD6NC5x8aRkhr4ZNBjvYxFT8IJaeLk8piQYMPRDlzi7dlb9d6C5WuC0LRpomk2r3bd6
/XpNOx2FyG18axeeASWtENgPvqEirM5MjwkCMIIHYzCCBkugAwIBAgIKXRYRuwAAAADQ8TANBgkq
hkiG9w0BAQUFADCBhTETMBEGCgmSJomT8ixkARkWA2NvbTEWMBQGCgmSJomT8ixkARkWBmx1Y2Vu
dDEUMBIGCgmSJomT8ixkARkWBG5hMDIxFzAVBgNVBAoTDkFsY2F0ZWwgTHVjZW50MScwJQYDVQQD
Ex5BbGNhdGVsIEx1Y2VudCBJbnRlcm5hbCBTdWIgQ0EwHhcNMTUwNDE2MDU1MjI4WhcNMTcwNDE1
MDU1MjI4WjBDMREwDwYDVQQDEwhib2dhZXJ0YjEuMCwGCSqGSIb3DQEJARYfYmFydC5ib2dhZXJ0
QGFsY2F0ZWwtbHVjZW50LmNvbTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAJBS7alw
mZfOimfXIdJjyp1G8U+E4Rs5y+eXtDfKWEuy6UOCstRCUiSz+eljCu737ZPkMHmPMdXDHZGnsV9y
HsInD5cZHBTNnboc8lV7zLVpTrtrnflClsOiRD75CS1Vvehx+JnFuW4Mo/VeWjQtUD4tUU67W7b0
QPOkcB3KkZixozjERSxPUFHf6pMShshwQlKtvV6YLdhnNePiuFimfYqUDiOQs1LR8C+r3eSMHi8o
lyWTHf49vFPL7z62HWSldeEkf6vhtuZuWLfH7xqO3CIQH63zUJF9p23ko2/Gtc1MpAcdWMwV3ymj
V8ef+gZac/SFwFgA547zeawhhvtdiOUCAwEAAaOCBBQwggQQMD0GCSsGAQQBgjcVBwQwMC4GJisG
AQQBgjcVCIW9xVmD47E5h6WBKoa/w0KFlJgZgQv55kyE/bVaAgFkAgEFMB8GA1UdJQQYMBYGCisG
AQQBgjcKAwQGCCsGAQUFBwMEMAsGA1UdDwQEAwIFoDApBgkrBgEEAYI3FQoEHDAaMAwGCisGAQQB
gjcKAwQwCgYIKwYBBQUHAwQwRAYJKoZIhvcNAQkPBDcwNTAOBggqhkiG9w0DAgICAIAwDgYIKoZI
hvcNAwQCAgCAMAcGBSsOAwIHMAoGCCqGSIb3DQMHMB0GA1UdDgQWBBTzjeedsBUMWk5eyOwD8/c9
1B1G8jAfBgNVHSMEGDAWgBTZ7Gu9llgi99imd83+TYHvupe9EjCCAV0GA1UdHwSCAVQwggFQMIIB
TKCCAUigggFEhoHZbGRhcDovLy9DTj1BbGNhdGVsJTIwTHVjZW50JTIwSW50ZXJuYWwlMjBTdWIl
MjBDQSxDTj11c25hdnNwa2kwM3AsQ049Q0RQLENOPVB1YmxpYyUyMEtleSUyMFNlcnZpY2VzLENO
PVNlcnZpY2VzLENOPUNvbmZpZ3VyYXRpb24sREM9bHVhZCxEQz1sdWNlbnQsREM9Y29tP2NlcnRp
ZmljYXRlUmV2b2NhdGlvbkxpc3Q/YmFzZT9vYmplY3RDbGFzcz1jUkxEaXN0cmlidXRpb25Qb2lu
dIYsaHR0cHM6Ly93d3cuYWxjYXRlbC1sdWNlbnQuY29tL1BLSS9zdWJDQS5jcmyGOGh0dHA6Ly9z
ZXJ2aWNlcy5zdXBwb3J0LmFsY2F0ZWwtbHVjZW50LmNvbS9QS0kvc3ViQ0EuY3JsMIIBYQYIKwYB
BQUHAQEEggFTMIIBTzCBzAYIKwYBBQUHMAKGgb9sZGFwOi8vL0NOPUFsY2F0ZWwlMjBMdWNlbnQl
MjBJbnRlcm5hbCUyMFN1YiUyMENBLENOPUFJQSxDTj1QdWJsaWMlMjBLZXklMjBTZXJ2aWNlcyxD
Tj1TZXJ2aWNlcyxDTj1Db25maWd1cmF0aW9uLERDPWx1YWQsREM9bHVjZW50LERDPWNvbT9jQUNl
cnRpZmljYXRlP2Jhc2U/b2JqZWN0Q2xhc3M9Y2VydGlmaWNhdGlvbkF1dGhvcml0eTA4BggrBgEF
BQcwAoYsaHR0cHM6Ly93d3cuYWxjYXRlbC1sdWNlbnQuY29tL1BLSS9zdWJDQS5jcnQwRAYIKwYB
BQUHMAKGOGh0dHA6Ly9zZXJ2aWNlcy5zdXBwb3J0LmFsY2F0ZWwtbHVjZW50LmNvbS9QS0kvc3Vi
Q0EuY3J0MCoGA1UdEQQjMCGBH2JhcnQuYm9nYWVydEBhbGNhdGVsLWx1Y2VudC5jb20wDQYJKoZI
hvcNAQEFBQADggEBAEARoPJfuwXhstAQ/fAz/XKDC//Je9A0RG9Q5XV7+URvR5GxhwuikL/MEtXs
Dspufv0eHG/b92AVZxaSgdpzC6neLoW2Q/Rdeavuifm7H/Ob645vIufqDQEqRqsyt9xRP+31VphA
do994d7kU6v5BI7DAA8s5rl6h4PFbtvY5qe8VLNiTnon1dCwPQ+mRSrLfgjlZUw+WsMh69JEOWZX
EufZMg0oUvCboUe3LNNvh8+DtLafaT1gS/kpv3c+dXVApTjb1tPbeZHc5L85AVQBsbq/vYpWhiZR
qDiyVyPh+dh7vTa/GBJx/UVLwv6IswAwtCWZ/r9aReHssqkgMH9evF8xggQpMIIEJQIBATCBlDCB
hTETMBEGCgmSJomT8ixkARkWA2NvbTEWMBQGCgmSJomT8ixkARkWBmx1Y2VudDEUMBIGCgmSJomT
8ixkARkWBG5hMDIxFzAVBgNVBAoTDkFsY2F0ZWwgTHVjZW50MScwJQYDVQQDEx5BbGNhdGVsIEx1
Y2VudCBJbnRlcm5hbCBTdWIgQ0ECCl0WEbsAAAAA0PEwCQYFKw4DAhoFAKCCAmkwGAYJKoZIhvcN
AQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcNMTYwOTA1MTIzNDI1WjAjBgkqhkiG9w0B
CQQxFgQUkWHMbKpgH4pGr6eUJeSUbNBoB10wgaUGCSsGAQQBgjcQBDGBlzCBlDCBhTETMBEGCgmS
JomT8ixkARkWA2NvbTEWMBQGCgmSJomT8ixkARkWBmx1Y2VudDEUMBIGCgmSJomT8ixkARkWBG5h
MDIxFzAVBgNVBAoTDkFsY2F0ZWwgTHVjZW50MScwJQYDVQQDEx5BbGNhdGVsIEx1Y2VudCBJbnRl
cm5hbCBTdWIgQ0ECCl0WEbsAAAAA0PEwgacGCyqGSIb3DQEJEAILMYGXoIGUMIGFMRMwEQYKCZIm
iZPyLGQBGRYDY29tMRYwFAYKCZImiZPyLGQBGRYGbHVjZW50MRQwEgYKCZImiZPyLGQBGRYEbmEw
MjEXMBUGA1UEChMOQWxjYXRlbCBMdWNlbnQxJzAlBgNVBAMTHkFsY2F0ZWwgTHVjZW50IEludGVy
bmFsIFN1YiBDQQIKXRYRuwAAAADQ8TCBtwYJKoZIhvcNAQkPMYGpMIGmMAsGCWCGSAFlAwQBKjAL
BglghkgBZQMEARYwCgYIKoZIhvcNAwcwCwYJYIZIAWUDBAECMA4GCCqGSIb3DQMCAgIAgDAHBgUr
DgMCBzANBggqhkiG9w0DAgIBQDANBggqhkiG9w0DAgIBKDAHBgUrDgMCGjALBglghkgBZQMEAgMw
CwYJYIZIAWUDBAICMAsGCWCGSAFlAwQCATAKBggqhkiG9w0CBTANBgkqhkiG9w0BAQEFAASCAQB7
iQLtVqDO9mXDo42k0spYer6qzlUXeYAsAe6lE3O6/ScShIGYcgMOtX19OO20ZeS9tLJmlKHsS5DP
q6mp0Q5PQyKXGRi4Ood+nddGGzW4p74mHGh+RdmN43Ot94VoVOEMPg7NF8UlbKVE5XH/Z7n4rIow
4M4ddDds9T2jeqxNZ7BX+lo8Xs7MYbgepzaWwRSiDEgoCm7pW1g8yLJgwrQVT5A/82//WTIzZ6RO
RPI2JOQ6zU7z6VcjIAWqfQOJXuPjG8fJIBATSAVsx5R5y5QjnVCy7CYHu2b8y6S/u5b3HKdbRsBY
nceu/7YkAeLshLNbvFJBiphyskyfVCd4FZ9tAAAAAAAA

------=_NextPart_000_0160_01D20782.99F3A470--