Coupon Campaign
9+
Action
Another action
Something else here
7
Action
Another action
Something else here
Settings
Activity Log
Logout
Dashboard
Pages
Login Screens:
Login
Register
Forgot Password
Other Pages:
404 Page
Blank Page
Charts
Campaigns
Coupons
Distributions
Customers
Reedem Customers
Coupons
Campaign ID
Quantity
Customer id
Start Date
End Date
Status
Amount
All Coupons
Name
Coupon quantity
Start date
Expiry date
No of Coupons
Active Status
Name
Coupon quantity
Start date
Expiry date
No of Coupons
Active Status
More tables coming soon...
Ready to Leave?
×
Select "Logout" below if you are ready to end your current session.


Health Minister dismisses 'rushed calls' to distribute ambulances
Health Minister, Kwaku Agyemang-Manu, has shrugged off what he believes to be rushed calls for over 40 ambulances imported into the country to be commissioned for use.
He told host of Joy FM’s Super Morning Show, Daniel Dadzie, on Tuesday that calls for the ambulances to be distributed for use are politically motivated.
The 40 ambulances parked in front of Parliament are part of some 300 vehicles expected by December this year.
“The suppliers have not handed the vehicles to the Ministry yet…meaning pre-delivery inspection and other things haven’t been done…when the supplier hasn’t called you to say that these are your keys… how do we distribute the vehicles for use?” he asked.
The Minority National Democratic Congress in Parliament wants the government to distribute ambulances immediately, stating that while the vehicles sit idle, many Ghanaians are losing their lives.
Kwaku Agyemang-Manu was on the SMS on Tuesday
Addressing the press in Parliament, the Ranking Member on Parliament’s Health Committee, Kwabena Mintah Akandoh urged the President to commission the ambulances, parked at the forecourt of the Parliament House, for use within three days.
Pressure group OccupyGhana has also questioned the Special Development Initiatives Ministry’s explanation for the delay in distributing ambulances.
“We can excuse the fitting of the trackers. We can even excuse the training of the paramedics. But what cannot be excused is the lack of receiving points for these ambulances.
New ambulances
“In emergency care, the stepwise care of the critically ill or injured goes by algorithms that are known as the “ABCDs.” They are important because following them leads to the saving of lives,” OccupyGhana said in a press release on Sunday.
But responding to these concerns on the Super Morning Show, the Minister said although the ambulances have arrived, some important technical provisions have not been completed.
He said apart from technical inspections, more emergency health workers would have to be trained to ensure the ambulances best serve their purpose.
He was also unsure whether a December 2019 deadline for the ambulance to hit the streets would be achieved.
Government promised some 300 ambulances last year when it emerged that 29 million Ghanaians depend on only 55 functional ambulances across the country.


_ndy The burgundy ribbon was so bendy that it could be twisted and turned into beautiful shapes, but still remained soft and supple.[G|D] The organdy dress was so sweet, like the candy she had been craving, that when she tried it on, she knew it was the perfect choice for her.[G|D] Randy was walking along the sandy beach, letting the sun warm his skin as he thought of all the possibilities that lay before him.[G|D] His trendy outfit was the perfect choice for a windy day, keeping him warm and stylish as he ventured out into the city.[G|D]


--- layout: default title: Workshop permalink: workshop-mar2020 ---
Summary
The Midwest is characterized by a vast network of regional economic activity, as well as a mobile and dynamic workforce. The challenge for policy makers is that while state data systems end at state borders, economic and social activity does not, making it difficult to evaluate the impact of state interventions in many areas, but most clearly in understanding the transitions across education and work.
The Midwest Collaborative is an opportunity for the region to build a data system, the associated legal framework, and human resources that will dramatically improve the ability to monitor the health of our region’s interconnected education and workforce systems.
A group of universities and education/workforce agencies in the Midwest have worked together to design a system that enables individual states to answer critical questions that are relevant to society. This convening will synthesize the lessons we learned over the last three years and chart a course for formalizing our partnership as the Midwest Collaborative: Data for Evidence-Based Policy.
Final Report
Logistics
Who: Invited leaders and stakeholders representing workforce, education, government, research and philanthropy
When: March 5-6, 2020
Time: 9:00 a.m. - 5:00 p.m.
Location: The Ohio Union at The Ohio State University, Cartoon Room
1739 N. High Street
Columbus, OH 43210
Recommended Hotel: Hyatt Place Columbus/OSU
795 Yard Street
Columbus, OH 43212
Reservations can be made by calling<PHONE_NUMBER> or via the hotel website at www.hyattplacecolumbusosu.com utilizing the group booking code G-JGSL.
Your rate includes complimentary hot breakfast buffet in the Guest Kitchen each morning, complimentary WiFi and complimentary parking. Please coordinate your reservations prior to February 3, 2020 for applicable group rate.
Workshop Registration Link: Click Here
Agenda
March 4:
We will start the workshop with a welcome dinner for attendees from 7:00 p.m.
- 9:00 p.m.
March 5:
| 8:30 - 9:00 a.m. | Registration and Coffee |
| 9:00 - 9:30 a.m. | Welcome and Introductions |
| 9:30 - 10:30 a.m. | Motivation – The Case for a Collaborative |
| 10:30 - 10:45 a.m | Break |
| 10:45 a.m. - Noon | What has been done (slides: Chapin Hall), (slides: OSU), (slides: IRIS) |
| Noon - 1:00 p.m. | Lunch |
| 1:00 - 1:45 p.m. | Building common foundations; ADRF and Data Stewardship (slides) |
| 1:45 - 2:45 p.m. | A National Perspective |
| 2:45 - 3:15 p.m. | Break |
| 3:15 - 4:15 p.m. | Defining states' interests |
March 6:
| 9:00 - 10:30 a.m. | Moving from concept to reality, program of work for Midwest |
| 10:30 - 10:45 a.m. | Break |
| 10:45 - Noon | Regional governance and data systems |
| Noon - 1:00 p.m. | Lunch |
| 1:00 - 2:30 p.m. | Report Out from working groups/closing session |
Posters


The current version of MiStaMover is 0.1.0-alpha. This can be downloaded from:
Version 0.1.0-alpha
MiStaMover requires at least version Python 2.5 on your operating system and that at least one transfer protocol allows connection to a remote host to which data can be pushed. That is it!
Previous versions of MiStaMover are listed below.
Utilities
Enter search terms or a module, class or function name.


--- layout: default ---
Network Working Group D. Nelson Request for Comments: 5607 Elbrys Networks, Inc. Category: Standards Track G. Weber Individual Contributor July 2009 Remote Authentication Dial-In User Service (RADIUS) Authorization for Network Access Server (NAS) Management Abstract This document specifies Remote Authentication Dial-In User Service (RADIUS) attributes for authorizing management access to a Network Access Server (NAS). Both local and remote management are supported, with granular access rights and management privileges. Specific provisions are made for remote management via Framed Management protocols and for management access over a secure transport protocol. Status of This Memo This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. Copyright Notice Copyright (c) 2009 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents in effect on the date of publication of this document (http://trustee.ietf.org/license-info). Please review these documents carefully, as they describe your rights and restrictions with respect to this document. This document may contain material from IETF Documents or IETF Contributions published or made publicly available before November 10, 2008. The person(s) controlling the copyright in some of this material may not have granted the IETF Trust the right to allow modifications of such material outside the IETF Standards Process. Without obtaining an adequate license from the person(s) controlling the copyright in such materials, this document may not be modified outside the IETF Standards Process, and derivative works of it may Nelson & Weber Standards Track [Page 1] RFC 5607 RADIUS NAS-Management Authorization July 2009 not be created outside the IETF Standards Process, except to format it for publication as an RFC or to translate it into languages other than English. Table of Contents 1.                        Introduction
RFC 2865 [RFC2865] defines the NAS-Prompt (7) and Administrative (6) values of the Service-Type (6) Attribute. Both of these values provide access to the interactive, text-based Command Line Interface (CLI) of the NAS, and were originally developed to control access to the physical console port of the NAS, most often a serial port. Remote access to the CLI of the NAS has been available in NAS implementations for many years, using protocols such as Telnet, Rlogin, and the remote terminal service of the Secure SHell (SSH). In order to distinguish local, physical, console access from remote access, the NAS-Port-Type (61) Attribute is generally included in Access-Request and Access-Accept messages, along with the Service- Type (6) Attribute, to indicate the form of access. A NAS-Port-Type (61) Attribute with a value of Async (0) is used to signify a local serial port connection, while a value of Virtual (5) is used to signify a remote connection, via a remote terminal protocol. This usage provides no selectivity among the various available remote terminal protocols (e.g., Telnet, Rlogin, SSH, etc.). Today, it is common for network devices to support more than the two privilege levels for management access provided by the Service-Type (6) Attribute with values of NAS-Prompt (7) (non-privileged) and Administrative (6) (privileged). Also, other management mechanisms may be used, such as Web-based management, the Simple Network Management Protocol (SNMP), and the Network Configuration Protocol (NETCONF). To provide support for these additional features, this specification defines attributes for Framed Management protocols, management protocol security, and management access privilege levels. Remote management via the command line is carried over protocols such as Telnet, Rlogin, and the remote terminal service of SSH. Since these protocols are primarily for the delivery of terminal or terminal emulation services, the term "Framed Management" is used to describe management protocols supporting techniques other than the command line. Typically, these mechanisms format management information in a binary or textual encoding such as HTML, XML, or ASN.1/BER. Examples include Web-based management (HTML over HTTP or HTTPS), NETCONF (XML over SSH or BEEP or SOAP), and SNMP (SMI over ASN.1/BER). Command line interface, menu interface, or other text- based (e.g., ASCII or UTF-8) terminal emulation services are not considered to be Framed Management protocols. Nelson & Weber Standards Track [Page 3] RFC 5607 RADIUS NAS-Management Authorization July 20092. Terminology
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 [RFC2119]. This document uses terminology from RFC 2865 [RFC2865], RFC 2866 [RFC2866], and RFC 5176 [RFC5176]. The term "integrity protection", as used in this document, is *not* the same as "authentication", as used in SNMP. Integrity protection requires the sharing of cryptographic keys, but it does not require authenticated principals. Integrity protection could be used, for example, with anonymous Diffie-Hellman key agreement. In SNMP, the proof of identity of the principals (authentication) is conflated with tamper-resistance of the protected messages (integrity). In this document, we assume that integrity protection and authentication are separate concerns. Authentication is part of the base RADIUS protocol. SNMP uses the terms "auth" and "noAuth", as well as "priv" and "noPriv". There is no analog to auth or noAuth in this document. In this document, we are assuming that authentication always occurs when it is required, i.e., as a prerequisite to provisioning of access via an Access-Accept packet.3. Overview
To support the authorization and provisioning of Framed Management access to managed entities, this document introduces a new value for the Service-Type (6) Attribute [RFC2865] and one new attribute. The new value for the Service-Type (6) Attribute is Framed-Management (18), used for remote device management via a Framed Management protocol. The new attribute is Framed-Management-Protocol (133), the value of which specifies a particular protocol for use in the remote management session. Two new attributes are introduced in this document in support of granular management access rights or command privilege levels. The Management-Policy-Id (135) Attribute provides a text string specifying a policy name of local scope, that is assumed to have been pre-provisioned on the NAS. This use of an attribute to specify use of a pre-provisioned policy is similar to the Filter-Id (11) Attribute defined in [RFC2865] Section 5.11. The local application of the Management-Policy-Id (135) Attribute within the managed entity may take the form of (a) one of an enumeration of command privilege levels, (b) a mapping into an SNMP Nelson & Weber Standards Track [Page 4] RFC 5607 RADIUS NAS-Management Authorization July 2009 Access Control Model, such as the View-Based Access Control Model (VACM) [RFC3415], or (c) some other set of management access policy rules that is mutually understood by the managed entity and the remote management application. Examples are given in Section 8. The Management-Privilege-Level (136) Attribute contains an integer- valued management privilege level indication. This attribute serves to modify or augment the management permissions provided by the NAS- Prompt (7) value of the Service-Type (6) Attribute, and thus applies to CLI management. To enable management security requirements to be specified, the Management-Transport-Protection (134) Attribute is introduced. The value of this attribute indicates the minimum level of secure transport protocol protection required for the provisioning of NAS- Prompt (7), Administrative (6), or Framed-Management (18) service.4. Domain of Applicability
Most of the RADIUS attributes defined in this document have broad applicability for provisioning local and remote management access to NAS devices. However, those attributes that provision remote access over Framed Management protocols and over secure transports have special considerations. This document does not specify the details of the integration of these protocols with a RADIUS client in the NAS implementation. However, there are functional requirements for correct application of Framed Management protocols and/or secure transport protocols that will limit the selection of such protocols that can be considered for use with RADIUS. Since the RADIUS user credentials are typically obtained by the RADIUS client from the secure transport protocol server or the Framed Management protocol server, the protocol, and its implementation in the NAS, MUST support forms of credentials that are compatible with the authentication methods supported by RADIUS. RADIUS currently supports the following user authentication methods, although others may be added in the future: o Password - RFC 2865 o CHAP (Challenge Handshake Authentication Protocol) - RFC 2865 o ARAP (Apple Remote Access Protocol) - RFC 2869 o EAP (Extensible Authentication Protocol) - RFC 2869, RFC 3579 o HTTP Digest - RFC 5090 Nelson & Weber Standards Track [Page 5] RFC 5607 RADIUS NAS-Management Authorization July 2009 The remote management protocols selected for use with the RADIUS remote NAS management sessions, for example, those described in Section 6.1, and the secure transport protocols selected to meet the protection requirements, as described in Section 6.2, obviously need to support user authentication methods that are compatible with those that exist in RADIUS. The RADIUS authentication methods most likely usable with these protocols are Password, CHAP, and possibly HTTP Digest, with Password being the distinct common denominator. There are many secure transports that support other, more robust, authentication mechanisms, such as public key. RADIUS has no support for public key authentication, except within the context of an EAP Method. The applicability statement for EAP indicates that it is not intended for use as an application-layer authentication mechanism, so its use with the mechanisms described in this document is NOT RECOMMENDED. In some cases, Password may be the only compatible RADIUS authentication method available.5. New Values for Existing RADIUS Attributes
5.1. Service-Type
The Service-Type (6) Attribute is defined in Section 5.6 of RFC 2865 [RFC2865]. This document defines a new value of the Service-Type Attribute, as follows: 18 Framed-Management The semantics of the Framed-Management service are as follows: Framed-Management A Framed Management protocol session should be started on the NAS.6. New RADIUS Attributes
This document defines four new RADIUS attributes related to management authorization.6.1. Framed-Management-Protocol
The Framed-Management-Protocol (133) Attribute indicates the application-layer management protocol to be used for Framed Management access. It MAY be used in both Access-Request and Access- Accept packets. This attribute is used in conjunction with a Service-Type (6) Attribute with the value of Framed-Management (18). It is RECOMMENDED that the NAS include an appropriately valued Framed-Management-Protocol (133) Attribute in an Access-Request packet, indicating the type of management access being requested. It Nelson & Weber Standards Track [Page 6] RFC 5607 RADIUS NAS-Management Authorization July 2009 is further RECOMMENDED that the NAS include a Service-Type (6) Attribute with the value Framed-Management (18) in the same Access- Request packet. The RADIUS server MAY use these attributes as a hint in making its authorization decision. The RADIUS server MAY include a Framed-Management-Protocol (133) Attribute in an Access-Accept packet that also includes a Service- Type (6) Attribute with a value of Framed-Management (18), when the RADIUS server chooses to enforce a management access policy for the authenticated user that dictates one form of management access in preference to others. When a NAS receives a Framed-Management-Protocol (133) Attribute in an Access-Accept packet, it MUST deliver that specified form of management access or disconnect the session. If the NAS does not support the provisioned management application-layer protocol, or the management access protocol requested by the user does not match that of the Framed-Management-Protocol (133) Attribute in the Access- Accept packet, the NAS MUST treat the Access-Accept packet as if it had been an Access-Reject. A summary of the Framed-Management-Protocol (133) Attribute format is shown below. The fields are transmitted from left to right. 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Type | Length | Value +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Value (cont) | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Type 133 for Framed-Management-Protocol. Length 6 Nelson & Weber Standards Track [Page 7] RFC 5607 RADIUS NAS-Management Authorization July 2009 Value The Value field is a four-octet enumerated value. 1 SNMP 2 Web-based 3 NETCONF 4 FTP 5 TFTP 6 SFTP 7 RCP 8 SCP All other values are reserved for IANA allocation subject to the provisions of Section 11. The acronyms used in the above table expand as follows: o SNMP: Simple Network Management Protocol [RFC3411], [RFC3412], [RFC3413], [RFC3414], [RFC3415], [RFC3416], [RFC3417], [RFC3418]. o Web-based: Use of an embedded web server in the NAS for management via a generic web browser client. The interface presented to the administrator may be graphical, tabular, or textual. The protocol is HTML over HTTP. The protocol may optionally be HTML over HTTPS, i.e., using HTTP over TLS [HTML] [RFC2616]. o NETCONF: Management via the NETCONF protocol using XML over supported transports (e.g., SSH, BEEP, SOAP). As secure transport profiles are defined for NETCONF, the list of transport options may expand [RFC4741], [RFC4742], [RFC4743], [RFC4744]. o FTP: File Transfer Protocol, used to transfer configuration files to and from the NAS [RFC0959]. o TFTP: Trivial File Transfer Protocol, used to transfer configuration files to and from the NAS [RFC1350]. o SFTP: SSH File Transfer Protocol, used to securely transfer configuration files to and from the NAS. SFTP uses the services of SSH [SFTP]. See also Section 3.7, "SSH and File Transfers" of [SSH]. Additional information on the "sftp" program may typically be found in the online documentation ("man" pages) of Unix systems. Nelson & Weber Standards Track [Page 8] RFC 5607 RADIUS NAS-Management Authorization July 2009 o RCP: Remote CoPy file copy utility (Unix-based), used to transfer configuration files to and from the NAS. See Section 3.7, "SSH and File Transfers", of [SSH]. Additional information on the "rcp" program may typically be found in the online documentation ("man" pages) of Unix systems. o SCP: Secure CoPy file copy utility (Unix-based), used to transfer configuration files to and from the NAS. The "scp" program is a simple wrapper around SSH. It's basically a patched BSD Unix "rcp", which uses ssh to do the data transfer (instead of using "rcmd"). See Section 3.7, "SSH and File Transfers", of [SSH]. Additional information on the "scp" program may typically be found in the online documentation ("man" pages) of Unix systems.6.2. Management-Transport-Protection
The Management-Transport-Protection (134) Attribute specifies the minimum level of protection that is required for a protected transport used with the Framed or non-Framed Management access session. The protected transport used by the NAS MAY provide a greater level of protection, but MUST NOT provide a lower level of protection. When a secure form of non-Framed Management access is specified, it means that the remote terminal session is encapsulated in some form of protected transport, or tunnel. It may also mean that an explicit secure mode of operation is required, when the Framed Management protocol contains an intrinsic secure mode of operation. The Management-Transport-Protection (134) Attribute does not apply to CLI access via a local serial port, or other non-remote connection. When a secure form of Framed Management access is specified, it means that the application-layer management protocol is encapsulated in some form of protected transport, or tunnel. It may also mean that an explicit secure mode of operation is required, when the Framed Management protocol contains an intrinsic secure mode of operation. A value of "No Protection (1)" indicates that a secure transport protocol is not required, and that the NAS SHOULD accept a connection over any transport associated with the application-layer management protocol. The definitions of management application to transport bindings are defined in the relevant documents that specify those management application protocols. The same "No Protection" semantics are conveyed by omitting this attribute from an Access-Accept packet. Specific protected transport protocols, cipher suites, key agreement methods, or authentication methods are not specified by this attribute. Such provisioning is beyond the scope of this document. Nelson & Weber Standards Track [Page 9] RFC 5607 RADIUS NAS-Management Authorization July 2009 It is RECOMMENDED that the NAS include an appropriately valued Management-Transport-Protection (134) Attribute in an Access-Request packet, indicating the level of transport protection for the management access being requested, when that information is available to the RADIUS client. The RADIUS server MAY use this attribute as a hint in making its authorization decision. The RADIUS server MAY include a Management-Transport-Protection (134) Attribute in an Access-Accept packet that also includes a Service- Type (6) Attribute with a value of Framed-Management (18), when the RADIUS server chooses to enforce a management access security policy for the authenticated user that dictates a minimum level of transport security. When a NAS receives a Management-Transport-Protection (134) Attribute in an Access-Accept packet, it MUST deliver the management access over a transport with equal or better protection characteristics or disconnect the session. If the NAS does not support protected management transport protocols, or the level of protection available does not match that of the Management-Transport-Protection (134) Attribute in the Access-Accept packet, the NAS MUST treat the response packet as if it had been an Access-Reject. A summary of the Management-Transport-Protection (134) Attribute format is shown below. The fields are transmitted from left to right. 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Type | Length | Value +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Value (cont) | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Type 134 for Management-Transport-Protection. Length 6 Nelson & Weber Standards Track [Page 10] RFC 5607 RADIUS NAS-Management Authorization July 2009 Value The Value field is a four-octet enumerated value. 1 No-Protection 2 Integrity-Protection 3 Integrity-Confidentiality-Protection All other values are reserved for IANA allocation subject to the provisions of Section 11. The names used in the above table are elaborated as follows: o No-Protection: No transport protection is required. Accept connections via any supported transport. o Integrity-Protection: The management transport MUST provide Integrity Protection, i.e., protection from unauthorized modification, using a cryptographic checksum. o Integrity-Confidentiality-Protection: The management transport MUST provide both Integrity Protection and Confidentiality Protection, i.e., protection from unauthorized modification, using a cryptographic checksum, and protection from unauthorized disclosure, using encryption. The configuration or negotiation of acceptable algorithms, modes, and credentials for the cryptographic protection mechanisms used in implementing protected management transports is outside the scope of this document. Many such mechanisms have standardized methods of configuration and key management.6.3. Management-Policy-Id
The Management-Policy-Id (135) Attribute indicates the name of the management access policy for this user. Zero or one Management- Policy-Id (135) Attributes MAY be sent in an Access-Accept packet. Identifying a policy by name allows the policy to be used on different NASes without regard to implementation details. Multiple forms of management access rules may be expressed by the underlying named policy, the definition of which is beyond the scope of this document. The management access policy MAY be applied contextually, based on the nature of the management access method. For example, some named policies may only be valid for application to NAS-Prompt (7) services and some other policies may only be valid for SNMP. Nelson & Weber Standards Track [Page 11] RFC 5607 RADIUS NAS-Management Authorization July 2009 The management access policy named in this attribute, received in an Access-Accept packet, MUST be applied to the session authorized by the Access-Accept. If the NAS supports this attribute, but the policy name is unknown, or if the RADIUS client is able to determine that the policy rules are incorrectly formatted, the NAS MUST treat the Access-Accept packet as if it had been an Access-Reject. No precedence relationship is defined for multiple occurrences of the Management-Policy-Id (135) Attribute. NAS behavior in such cases is undefined. Therefore, two or more occurrences of this attribute SHOULD NOT be included in an Access-Accept or CoA-Request (Change-of- Authorization). In the absence of further specification defining some sort of precedence relationship, it is not possible to guarantee multi-vendor interoperability when using multiple instances of this attribute in a single Access-Accept or CoA-Request packet. The content of the Management-Policy-Id (135) Attribute is expected to be the name of a management access policy of local significance to the NAS, within a namespace of significance to the NAS. In this regard, the behavior is similar to that for the Filter-Id (11) Attribute. The policy names and rules are committed to the local configuration data-store of the NAS, and are provisioned by means beyond the scope of this document, such as via SNMP, NETCONF, or CLI. The namespace used in the Management-Policy-Id (135) Attribute is simple and monolithic. There is no explicit or implicit structure or hierarchy. For example, in the text string "example.com", the "." (period or dot) is just another character. It is expected that text string matching will be performed without parsing the text string into any sub-fields. Overloading or subdividing this simple name with multi-part specifiers (e.g., Access=remote, Level=7) is likely to lead to poor multi-vendor interoperability and SHOULD NOT be utilized. If a simple, unstructured policy name is not sufficient, it is RECOMMENDED that a Vendor Specific (26) Attribute be used instead, rather than overloading the semantics of Management-Policy-Id. Nelson & Weber Standards Track [Page 12] RFC 5607 RADIUS NAS-Management Authorization July 2009 A summary of the Management-Policy-Id (135) Attribute format is shown below. The fields are transmitted from left to right. 0 1 2 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+- | Type | Length | Text ... +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+- Type 135 for Management-Policy-Id. Length >= 3 Text The Text field is one or more octets, and its contents are implementation dependent. It is intended to be human readable and the contents MUST NOT be parsed by the receiver; the contents can only be used to look up locally defined policies. It is RECOMMENDED that the message contain UTF-8 encoded 10646 [RFC3629] characters.6.4. Management-Privilege-Level
The Management-Privilege-Level (136) Attribute indicates the integer- valued privilege level to be assigned for management access for the authenticated user. Many NASes provide the notion of differentiated management privilege levels denoted by an integer value. The specific access rights conferred by each value are implementation dependent. It MAY be used in both Access-Request and Access-Accept packets. The mapping of integer values for this attribute to specific collections of management access rights or permissions on the NAS is vendor and implementation specific. Such mapping is often a user- configurable feature. It's RECOMMENDED that greater numeric values imply greater privilege. However, it would be a mistake to assume that this recommendation always holds. The management access level indicated in this attribute, received in an Access-Accept packet, MUST be applied to the session authorized by the Access-Accept. If the NAS supports this attribute, but the privilege level is unknown, the NAS MUST treat the Access-Accept packet as if it had been an Access-Reject. Nelson & Weber Standards Track [Page 13] RFC 5607 RADIUS NAS-Management Authorization July 2009 A summary of the Management-Privilege-Level (136) Attribute format is show below. The fields are transmitted from left to right. 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Type | Length | Value +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Value (cont) | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Type 136 for Management-Privilege-Level. Length 6 Value The Value field is a four-octet Integer, denoting a management privilege level. It is RECOMMENDED to limit use of the Management-Privilege-Level (136) Attribute to sessions where the Service-Type (6) Attribute has a value of NAS-Prompt (7) (not Administrative). Typically, NASes treat NAS-Prompt as the minimal privilege CLI service and Administrative as full privilege. Using the Management-Privilege- Level (136) Attribute with a Service-Type (6) Attribute having a value of NAS-Prompt (7) will have the effect of increasing the minimum privilege level. Conversely, it is NOT RECOMMENDED to use this attribute with a Service-Type (6) Attribute with a value of Administrative (6), which may require decreasing the maximum privilege level. It is NOT RECOMMENDED to use the Management-Privilege-Level (136) Attribute in combination with a Management-Policy-Id (135) Attribute or for management access methods other than interactive CLI. The behavior resulting from such an overlay of management access control provisioning is not defined by this document, and in the absence of further specification, is likely to lead to unexpected behaviors, especially in multi-vendor environments. Nelson & Weber Standards Track [Page 14] RFC 5607 RADIUS NAS-Management Authorization July 20097. Use with Dynamic Authorization
It is entirely OPTIONAL for the NAS management authorization attributes specified in this document to be used in conjunction with Dynamic Authorization extensions to RADIUS [RFC5176]. When such usage occurs, those attributes MAY be used as listed in the Table of Attributes in Section 10. Some guidance on how to identify existing management sessions on a NAS for the purposes of Dynamic Authorization is useful. The primary session identifiers SHOULD be User-Name (1) and Service-Type (6). To accommodate instances when that information alone does not uniquely identify a session, a NAS supporting Dynamic Authorization SHOULD maintain one or more internal session identifiers that can be represented as RADIUS attributes. Examples of such attributes include Acct-Session-Id (44), Acct-Multi-Session-Id (50), NAS-Port (5), or NAS-Port-Id (87). In the case of a remote management session, common identifier values might include things such as the remote IP address and remote TCP port number, or the file descriptor value for use with the open socket. Any such identifier is obviously transient in nature, and implementations SHOULD take care to avoid and/or properly handle duplicate or stale values. In order for the session identification attributes to be available to the Dynamic Authorization Client, a NAS supporting Dynamic Authorization for management sessions SHOULD include those session identification attributes in the Access-Request message for each such session. Additional discussion of session identification attribute usage may be found in Section 3 of [RFC5176].8. Examples of Attribute Groupings
1. Unprotected CLI access, via the local console, to the "super- user" access level: * Service-Type (6) = Administrative (6) * NAS-Port-Type (61) = Async (0) * Management-Transport-Protection (134) = No-Protection (1) 2. Unprotected CLI access, via a remote console, to the "super-user" access level: * Service-Type (6) = Administrative (6) * NAS-Port-Type (61) = Virtual (5) Nelson & Weber Standards Track [Page 15] RFC 5607 RADIUS NAS-Management Authorization July 2009 * Management-Transport-Protection (134) = No-Protection (1) 3. CLI access, via a fully protected secure remote terminal service to the non-privileged user access level: * Service-Type (6) = NAS-Prompt (7) * NAS-Port-Type (61) = Virtual (5) * Management-Transport-Protection (134) = Integrity- Confidentiality-Protection (3) 4. CLI access, via a fully protected secure remote terminal service, to a custom management access level, defined by a policy: * Service-Type (6) = NAS-Prompt (7) * NAS-Port-Type (61) = Virtual (5) * Management-Transport-Protection (134) = Integrity- Confidentiality-Protection (3) * Management-Policy-Id (135) = "Network Administrator" 5. CLI access, via a fully protected secure remote terminal service, with a management privilege level of 15: * Service-Type (6) = NAS-Prompt (7) * NAS-Port-Type (61) = Virtual (5) * Management-Transport-Protection (134) = Integrity- Confidentiality-Protection (3) * Management-Privilege-Level (136) = 15 6. SNMP access, using an Access Control Model specifier, such as a custom VACM View, defined by a policy: * Service-Type (6) = Framed-Management (18) * NAS-Port-Type (61) = Virtual (5) * Framed-Management-Protocol (133) = SNMP (1) * Management-Policy-Id (135) = "SNMP Network Administrator View" Nelson & Weber Standards Track [Page 16] RFC 5607 RADIUS NAS-Management Authorization July 2009 There is currently no standardized way of implementing this management policy mapping within SNMP. Such mechanisms are the topic of current research. 7. SNMP fully protected access: * Service-Type (6) = Framed-Management (18) * NAS-Port-Type (61) = Virtual (5) * Framed-Management-Protocol (133) = SNMP (1) * Management-Transport-Protection (134) = Integrity- Confidentiality-Protection (3) 8. Web (HTTP/HTML) access: * Service-Type (6) = Framed-Management (18) * NAS-Port-Type (61) = Virtual (5) * Framed-Management-Protocol (133) = Web-based (2) 9. Secure web access, using a custom management access level, defined by a policy: * Service-Type (6) = Framed-Management (18) * NAS-Port-Type (61) = Virtual (5) * Framed-Management-Protocol (133) = Web-based (2) * Management-Transport-Protection (134) = Integrity- Confidentiality-Protection (3) * Management-Policy-Id (135) = "Read-only web access"9. Diameter Translation Considerations
When used in Diameter, the attributes defined in this specification can be used as Diameter attribute-value pairs (AVPs) from the Code space 1-255 (RADIUS attribute compatibility space). No additional Diameter Code values are therefore allocated. The data types and flag rules for the attributes are as follows: Nelson & Weber Standards Track [Page 17] RFC 5607 RADIUS NAS-Management Authorization July 2009 +---------------------+ | AVP Flag rules | |----+-----+----+-----|----+ | | SHOULD MUST| | Attribute Name Value Type |MUST| MAY | NOT| NOT|Encr| ---------------------------------|----+-----+----+-----|----| Service-Type | | | | | | Enumerated | M | P | | V | Y | Framed-Management-Protocol | | | | | | Enumerated | M | P | | V | Y | Management-Transport-Protection | | | | | | Enumerated | M | P | | V | Y | Management-Policy-Id | | | | | | UTF8String | M | P | | V | Y | Management-Privilege-Level | | | | | | Integer | M | P | | V | Y | ---------------------------------|----+-----+----+-----|----| The attributes in this specification have no special translation requirements for Diameter to RADIUS or RADIUS to Diameter gateways; they are copied as is, except for changes relating to headers, alignment, and padding. See also [RFC3588], Section 4.1, and [RFC4005], Section 9. What this specification says about the applicability of the attributes for RADIUS Access-Request packets applies in Diameter to AA-Request [RFC4005]. What is said about Access-Accept applies in Diameter to AA-Answer messages that indicate success.10. Table of Attributes
The following table provides a guide to which attributes may be found in which kinds of packets, and in what quantity. Access Messages Request Accept Reject Challenge # Attribute --------------------------------------------------------------------- 0-1 0-1 0 0 133 Framed-Management-Protocol 0-1 0-1 0 0 134 Management-Transport-Protection 0 0-1 0 0 135 Management-Policy-Id 0 0-1 0 0 136 Management-Privilege-Level Nelson & Weber Standards Track [Page 18] RFC 5607 RADIUS NAS-Management Authorization July 2009 Accounting Messages Request Response # Attribute --------------------------------------------------------------------- 0-1 0 133 Framed-Management-Protocol 0-1 0 134 Management-Transport-Protection 0-1 0 135 Management-Policy-Id 0-1 0 136 Management-Privilege-Level Change-of-Authorization Messages Request ACK NAK # Attribute -------------------------------------------------------------------- 0 0 0 133 Framed-Management-Protocol 0 0 0 134 Management-Transport-Protection 0-1 0 0 135 Management-Policy-Id (Note 1) 0-1 0 0 136 Management-Privilege-Level (Note 1) Disconnect Messages Request ACK NAK # Attribute --------------------------------------------------------------------- 0 0 0 133 Framed-Management-Protocol 0 0 0 134 Management-Transport-Protection 0 0 0 135 Management-Policy-Id 0 0 0 136 Management-Privilege-Level (Note 1) When included within a CoA-Request, these attributes represent an authorization change request. When one of these attributes is omitted from a CoA-Request, the NAS assumes that the attribute value is to remain unchanged. Attributes included in a CoA-Request replace all existing values of the same attribute(s). The following table defines the meaning of the above table entries. 0 This attribute MUST NOT be present in a packet. 0+ Zero or more instances of this attribute MAY be present in a packet. 0-1 Zero or one instance of this attribute MAY be present in a packet. 1 Exactly one instance of this attribute MUST be present in a packet.11. IANA Considerations
The following numbers have been assigned in the RADIUS Attribute Types registry. Nelson & Weber Standards Track [Page 19] RFC 5607 RADIUS NAS-Management Authorization July 2009 o New enumerated value for the existing Service-Type Attribute: * Framed-Management (18) o New RADIUS Attribute Types: * Framed-Management-Protocol (133) * Management-Transport-Protection (134) * Management-Policy-Id (135) * Management-Privilege-Level (136) The enumerated values of the newly assigned RADIUS Attribute Types as defined in this document were assigned at the same time as the new Attribute Types. For the Framed-Management-Protocol Attribute: 1 SNMP 2 Web-based 3 NETCONF 4 FTP 5 TFTP 6 SFTP 7 RCP 8 SCP For the Management-Transport-Protection Attribute: 1 No-Protection 2 Integrity-Protection 3 Integrity-Confidentiality-Protection Assignments of additional enumerated values for the RADIUS attributes defined in this document are to be processed as described in [RFC3575], subject to the additional requirement of a published specification.12. Security Considerations
12.1. General Considerations
This specification describes the use of RADIUS and Diameter for purposes of authentication, authorization, and accounting for management access to devices within networks. RADIUS threats and security issues for this application are described in [RFC3579] and Nelson & Weber Standards Track [Page 20] RFC 5607 RADIUS NAS-Management Authorization July 2009 [RFC3580]; security issues encountered in roaming are described in [RFC2607]. For Diameter, the security issues relating to this application are described in [RFC4005] and [RFC4072]. This document specifies new attributes that can be included in existing RADIUS packets, which may be protected as described in [RFC3579] and [RFC5176]. In Diameter, the attributes are protected as specified in [RFC3588]. See those documents for a more detailed description. The security mechanisms supported in RADIUS and Diameter are focused on preventing an attacker from spoofing packets or modifying packets in transit. They do not prevent an authorized RADIUS/Diameter server or proxy from inserting attributes with malicious intent. A legacy NAS may not recognize the attributes in this document that supplement the provisioning of CLI management access. If the value of the Service-Type Attribute is NAS-Prompt or Administrative, the legacy NAS may silently discard such attributes, while permitting the user to access the CLI management interface(s) of the NAS. This can lead to users improperly receiving authorized management access to the NAS, or access with greater levels of access rights than were intended. RADIUS servers SHOULD attempt to ascertain whether or not the NAS supports these attributes before sending them in an Access- Accept message that provisions CLI access. It is possible that certain NAS implementations may not be able to determine the protection properties of the underlying transport protocol as specified by the Management-Transport-Protection Attribute. This may be a limitation of the standard application programming interface of the underlying transport implementation or of the integration of the transport into the NAS implementation. In either event, NASes conforming to this specification, which cannot determine the protection state of the remote management connection, MUST treat an Access-Accept message containing a Management- Transport-Protection Attribute containing a value other than No- Protection (1) as if it were an Access-Reject message, unless specifically overridden by local policy configuration. Use of the No-Protection (1) option for the Management-Transport- Protection (134) Attribute is NOT RECOMMENDED in any deployment where secure management or configuration is required. Nelson & Weber Standards Track [Page 21] RFC 5607 RADIUS NAS-Management Authorization July 200912.2. RADIUS Proxy Operation Considerations
The device management access authorization attributes presented in this document present certain considerations when used in RADIUS proxy environments. These considerations are not different from those that exist in RFC 2865 [RFC2865] with respect to the Service- Type Attribute values of Administrative and NAS-Prompt. Most RADIUS proxy environments are also multi-party environments. In multi-party proxy environments it is important to distinguish which entities have the authority to provision management access to the edge devices, i.e., NASes, and which entities only have authority to provision network access services of various sorts. It may be important that operators of the NAS are able to ensure that access to the CLI, or other management interfaces of the NAS, is only provisioned to their own employees or contractors. One way for the NAS to enforce this requirement is to use only local, non-proxy RADIUS servers for management access requests. Proxy RADIUS servers could be used for non-management access requests, based on local policy. This "bifurcation" of RADIUS authentication and authorization is a simple case of separate administrative realms. The NAS may be designed so as to maintain separate lists of RADIUS servers for management AAA use and for non-management AAA use. An alternate method of enforcing this requirement would be for the first-hop RADIUS proxy server, operated by the owner of the NAS, to filter out any RADIUS attributes that provision management access rights that originate from "up-stream" proxy servers not operated by the NAS owner. Access-Accept messages that provision such locally unauthorized management access MAY be treated as if they were an Access-Reject by the first-hop proxy server. An additional exposure present in proxy deployments is that sensitive user credentials, e.g., passwords, are likely to be available in cleartext form at each of the proxy servers. Encrypted or hashed credentials are not subject to this risk, but password authentication is a very commonly used mechanism for management access authentication, and in RADIUS passwords are only protected on a hop- by-hop basis. Malicious proxy servers could misuse this sensitive information. These issues are not of concern when all the RADIUS servers, local and proxy, used by the NAS are under the sole administrative control of the NAS owner. Nelson & Weber Standards Track [Page 22] RFC 5607 RADIUS NAS-Management Authorization July 200913. Acknowledgments
Many thanks to all reviewers, including Bernard Aboba, Alan DeKok, David Harrington, Mauricio Sanchez, Juergen Schoenwaelder, Hannes Tschofenig, Barney Wolff, and Glen Zorn.14. References
14.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. [RFC2865] Rigney, C., Willens, S., Rubens, A., and W. Simpson, "Remote Authentication Dial In User Service (RADIUS)", RFC 2865, June 2000. [RFC3629] Yergeau, F., "UTF-8, a transformation format of ISO 10646", STD 63, RFC 3629, November 2003.14.2. Informative References
[HTML] Raggett, D., Le Hors, A., and I. Jacobs, "The HTML 4.01 Specification, W3C", December 1999. [RFC0959] Postel, J. and J. Reynolds, "File Transfer Protocol", STD 9, RFC 959, October 1985. [RFC1350] Sollins, K., "The TFTP Protocol (Revision 2)", STD 33, RFC 1350, July 1992. [RFC2607] Aboba, B. and J. Vollbrecht, "Proxy Chaining and Policy Implementation in Roaming", RFC 2607, June 1999. [RFC2616] Fielding, R., Gettys, J., Mogul, J., Frystyk, H., Masinter, L., Leach, P., and T. Berners-Lee, "Hypertext Transfer Protocol -- HTTP/1.1", RFC 2616, June 1999. [RFC2866] Rigney, C., "RADIUS Accounting", RFC 2866, June 2000. [RFC3411] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture for Describing Simple Network Management Protocol (SNMP) Management Frameworks", STD 62, RFC 3411, December 2002. Nelson & Weber Standards Track [Page 23] RFC 5607 RADIUS NAS-Management Authorization July 2009 [RFC3412] Case, J., Harrington, D., Presuhn, R., and B. Wijnen, "Message Processing and Dispatching for the Simple Network Management Protocol (SNMP)", STD 62, RFC 3412, December 2002. [RFC3413] Levi, D., Meyer, P., and B. Stewart, "Simple Network Management Protocol (SNMP) Applications", STD 62, RFC 3413, December 2002. [RFC3414] Blumenthal, U. and B. Wijnen, "User-based Security Model (USM) for version 3 of the Simple Network Management Protocol (SNMPv3)", STD 62, RFC 3414, December 2002. [RFC3415] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based Access Control Model (VACM) for the Simple Network Management Protocol (SNMP)", STD 62, RFC 3415, December 2002. [RFC3416] Presuhn, R., "Version 2 of the Protocol Operations for the Simple Network Management Protocol (SNMP)", STD 62, RFC 3416, December 2002. [RFC3417] Presuhn, R., "Transport Mappings for the Simple Network Management Protocol (SNMP)", STD 62, RFC 3417, December 2002. [RFC3418] Presuhn, R., "Management Information Base (MIB) for the Simple Network Management Protocol (SNMP)", STD 62, RFC 3418, December 2002. [RFC3575] Aboba, B., "IANA Considerations for RADIUS (Remote Authentication Dial In User Service)", RFC 3575, July 2003. [RFC3579] Aboba, B. and P. Calhoun, "RADIUS (Remote Authentication Dial In User Service) Support For Extensible Authentication Protocol (EAP)", RFC 3579, September 2003. [RFC3580] Congdon, P., Aboba, B., Smith, A., Zorn, G., and J. Roese, "IEEE 802.1X Remote Authentication Dial In User Service (RADIUS) Usage Guidelines", RFC 3580, September 2003. [RFC3588] Calhoun, P., Loughney, J., Guttman, E., Zorn, G., and J. Arkko, "Diameter Base Protocol", RFC 3588, September 2003. [RFC4005] Calhoun, P., Zorn, G., Spence, D., and D. Mitton, "Diameter Network Access Server Application", RFC 4005, August 2005. Nelson & Weber Standards Track [Page 24] RFC 5607 RADIUS NAS-Management Authorization July 2009 [RFC4072] Eronen, P., Hiller, T., and G. Zorn, "Diameter Extensible Authentication Protocol (EAP) Application", RFC 4072, August 2005. [RFC4741] Enns, R., "NETCONF Configuration Protocol", RFC 4741, December 2006. [RFC4742] Wasserman, M. and T. Goddard, "Using the NETCONF Configuration Protocol over Secure SHell (SSH)", RFC 4742, December 2006. [RFC4743] Goddard, T., "Using NETCONF over the Simple Object Access Protocol (SOAP)", RFC 4743, December 2006. [RFC4744] Lear, E. and K. Crozier, "Using the NETCONF Protocol over the Blocks Extensible Exchange Protocol (BEEP)", RFC 4744, December 2006. [RFC5176] Chiba, M., Dommety, G., Eklund, M., Mitton, D., and B. Aboba, "Dynamic Authorization Extensions to Remote Authentication Dial In User Service (RADIUS)", RFC 5176, January 2008. [SFTP] Galbraith, J. and O. Saarenmaa, "SSH File Transfer Protocol", Work in Progress, July 2006. [SSH] Barrett, D., Silverman, R., and R. Byrnes, "SSH, the Secure Shell: The Definitive Guide, Second Edition, O'Reilly and Associates", May 2005. Authors' Addresses David B. Nelson Elbrys Networks, Inc. 282 Corporate Drive Portsmouth, NH 03801 USA EMail<EMAIL_ADDRESS>Greg Weber Individual Contributor Knoxville, TN 37932 USA EMail<EMAIL_ADDRESS>Nelson & Weber Standards Track [Page 25]


How To Download And Install Macos Big Sur 11 2 3 On Your Mac Imore
Macos Big Sur 11 1 Download Now Available Iphone In Canada Blog
Dowlnoad Macos Big Sur 11 1 Software Update For Mac
Https Www Bu Edu Tech Files 2019 12 Downloading Teams Pdf
3 Ways To Speed Up Slow Safari Downloads Techrepublic
Safari Technology Preview For Mac Free Download Review Latest Version
Safari Web Browser Wikipedia
Safari 14 0 Download Released By Apple Before Macos Big Sur 11 Iphone In Canada Blog
Disable Prevent Cross Site Tracking Arcola Theatre
How To Downgrade Safari 14 To 13 Supported Unsupported Options
Progressive Web Apps On Ios Are Here By Maximiliano Firtman Firt Dev Medium
Macos Big Sur Is Now Available To Download The Verge
How To Stay As Private As Possible On The Mac Computerworld
How To Install Adobe Flash Player On Mac Macworld Uk
Unable To Submit Content Using Safari 11 1 Utsonline Help
Greg Whitworth On Twitter Pretty Exciting As Of Chrome 66 You Can Use Format Variations Eg Format Truetype Variations Within Font Face And Chrome Won T Download It If The Browser Doesn T Support Variable Fonts Safari 11 1
Safari 14 Is Now Available For Macos Catalina And Mojave The Verge


FEATURES
Lorem ipsum, or lipsum as it is sometimes known, is dummy text used in laying out print, graphic or web designs. The passage is attributed to an unknown typesetter in the 15th century who is thought to have scrambled parts of Cicero's De Finibus Bonorum et Malorum for use in a type specimen book.
for use in a type specimen book.
The passage is attributed to an unknown typesetter in the 15th century who is thought to have scrambled parts of Cicero's De Finibus Bonorum et Malorum for use in a type specimen book.
SERVICE
This is test under description
This is test under description
This is test under description
This is test under description
testmonial
Hello! Welcome to the Man's Style! if you want to MachoStyle, you are choise me!
Aroha! My Style is basic of classic! If you want to NomalStyle, you are choise me!
Hey! Come here!  My Style is Unic!, you are choise me!


My Class List
Software Development
Innovations 10
Debate
Chemistry
English 10
History 10
Pre Calculus
Spanish 3


The service isn't available at the moment
We’re carrying out some maintenance on the service. It will be available again as soon as possible.
Check back again later.
This is a paragraph of text. It explains in more detail what has happened and wraps across several lines.
This paragraph has a link to find out more about this subject.


{% extends 'stackdio/base.html' %} {% block content %}
Oops... It looks like something has gone wrong on our end.


Our product is a web application that allows you to organize your articles and share them with your peers. You will be able to share your boards and your peers will be able to search and find them as well.

"Simple and easy to use!"
"Made my research more organized"
Tech Award Winner
Find an article
you like
Save it to
your board
It's that simple!


#Binance Will Support @KomodoPlatform ( $KMD) Staking & Launch a 250,000 KMD Initial Staking Reward Airdrop
Users holding KMD on Binance may expect to receive a 1st staking reward bonus from an additional $300,000 equivalent pool of KMD.
https://t.co/7p3WY1QZ4D
So we should send some coins @ binance ?
If you want them to collect the rewards and decide who gets them, then sure, go ahead
Caglio23-Jul-19 09:38 AM
Oh... interesting point of view
Alexfrog23-Jul-19 09:38 AM
oh that is nice
PHBA206123-Jul-19 09:38 AM
they probably discovered that last week from the 30K block
finally Komodo receives some attentions, but this probably means we will see 5% / 12 more sell pressure each month from the Binance staking ..(edited)
ComputerGenie 👴👴👴23-Jul-19 09:39 AM
KMD generated by each user = Total KMD staking rewards received by Binance * User KMD holdings ratio.
User KMD holdings ratio = User KMD holdings / Total KMD staked by Binance.
(edited)
Alexfrog23-Jul-19 09:39 AM
holy shit they are giving out 250000 KMD based on peoples KMD balances on binance
on the downside, all the KMD is going to go to binance now
ComputerGenie 👴👴👴23-Jul-19 09:40 AM
until now they gave it to the miners
Alexfrog23-Jul-19 09:40 AM
it seems that they collected it
p.23-Jul-19 09:40 AM
Frontpage boys
Alexfrog23-Jul-19 09:40 AM
to the tune of having 250k from staking
ComputerGenie 👴👴👴23-Jul-19 09:42 AM
they probably discovered that last week from the 30K block
I'm certain they knew before that, but I think that number might have been a "why are we doing that still?" moment
owerache23-Jul-19 09:45 AM
sorry repost
mrtzmp323-Jul-19 09:45 AM
@Alexfrog 1351 in one candle
You awake yet
Alexfrog23-Jul-19 09:46 AM
its already almost lost it all
on the other hand, i will get some free KMD by depositing it to binance and holdign it there until sept 1
then everyone will get free KMD and dump it, destroying the price
PHBA206123-Jul-19 09:48 AM
on the postive side, KMD price may slowly increase from now until Sep 1st
mrtzmp323-Jul-19 09:48 AM
Dude bro y must stop worrying
Short term swings
Caglio23-Jul-19 09:49 AM
Well I sent 500 kmd
on wrong address
Thats lovely
Alexfrog23-Jul-19 09:49 AM
ow
mrtzmp323-Jul-19 09:49 AM
Rekt
Fucking rekt
Alexfrog23-Jul-19 09:49 AM
dont do that
mrtzmp323-Jul-19 09:49 AM
@Caglio
Caglio23-Jul-19 09:49 AM
well thankfully
its my old agama wallet address
Alexfrog23-Jul-19 09:49 AM
unless you accidentally send it to me, then its great
Caglio23-Jul-19 09:49 AM
one that has been compromised tho
Alexfrog23-Jul-19 09:49 AM
so log in and send it again
before hacker does
mrtzmp323-Jul-19 09:49 AM
Dude what y typing here
Caglio23-Jul-19 09:50 AM
I need to find fucking key for it
mrtzmp323-Jul-19 09:50 AM
Get inside agama asap
Like right now
Caglio23-Jul-19 09:50 AM
I dont have agama anymore, I deleted it rofl
ComputerGenie 👴👴👴23-Jul-19 09:50 AM
@Alexfrog When you hold millions, the per-day compounding adds up a lot quicker than you'd think
Alexfrog23-Jul-19 09:50 AM
I would love to experience that.


--- layout: tutorial-extended title: The Weather App --- {% assign tutorial_github_url = "https://github.com/infinispan/infinispan-embedded-tutorial" %} {% assign @tutorial_steps = "The Weather Application, Initializing the CacheManager, Putting stuff in the cache, Making entries expire, Configuring the default cache, Clustering the application, Listen to changes in the cluster, Listen to changes in the cache, Grouping entries together, Temperature averages with streams, Declarative configuration" | split: ", " %} {% assign tutorial_step = 0 %}
Let's begin by checking out the project. Fire up your terminal and enter:
git clone https://github.com/infinispan/infinispan-embedded-tutorial.git && cd infinispan-embedded-tutorial
The above commands will create a local copy (clone) of the git repository and change the current directory so that all subsequent commands will run from the project root directory. We now want to move to "Step 0" in the project:
git checkout -f step-0
The initial step is just a plain Maven Java project with an implementation of our Weather Application. The application connects to the OpenWeatherMap API to retrieve current weather data for a variety of cities. Usage of the OpenWeatherMap API requires registering for a free API key. Before launching the application, ensure you've set the OWMAPIKEY environment variable to your API key:
export OWMAPIKEY=111111
In Windows you'd use:
C:\> set OWMAPIKEY=111111
If you'd rather not register, if you don't have an Internet connection or you are having trouble connecting to the service, don't worry: the application will use a random weather service. This initial step has no dependencies and uses JDK logging. The following image shows the layout of the project:
Let's compile and run it:
mvn clean package
Maven will run both goals specified on the command-line in order. The first goal (clean) just cleans any previously generated files and the second one (package) compiles the project, runs any unit tests and packages the resulting code into a Jar file. At this point we can also run the code. The main() method of the WeatherApp class initializes the WeatherService and retrieves the current temperature for the list of cities twice and prints the elapsed time after each retrieval. Since no caching is being done at this stage, the application is quite slow on both runs, since it always has to retrieve the information.
mvn exec:exec
---- Fetching weather information ----
Rome, Italy - Temperature: 12.9° C, Conditions: light rain
Como, Italy - Temperature: 6.3° C, Conditions: Sky is Clear
Basel, Switzerland - Temperature: 0.8° C, Conditions: overcast clouds
Bern, Switzerland - Temperature: -1.6° C, Conditions: broken clouds
London, UK - Temperature: 1.8° C, Conditions: light rain
Newcastle, UK - Temperature: 2.6° C, Conditions: scattered clouds
Bucharest, Romania - Temperature: 9.3° C, Conditions: scattered clouds
Cluj-Napoca, Romania - Temperature: 6.4° C, Conditions: scattered clouds
Ottawa, Canada - Temperature: -7.0° C, Conditions: overcast clouds
Toronto, Canada - Temperature: -7.0° C, Conditions: broken clouds
Lisbon, Portugal - Temperature: 14.6° C, Conditions: overcast clouds
Porto, Portugal - Temperature: 12.2° C, Conditions: moderate rain
Raleigh, USA - Temperature: 3.9° C, Conditions: Sky is Clear
Washington, USA - Temperature: 3.4° C, Conditions: light rain
---- Fetched in 2210ms ----
---- Fetching weather information ----
Rome, Italy - Temperature: 12.9° C, Conditions: light rain
Como, Italy - Temperature: 6.3° C, Conditions: Sky is Clear
Basel, Switzerland - Temperature: 0.8° C, Conditions: overcast clouds
Bern, Switzerland - Temperature: -1.6° C, Conditions: broken clouds
London, UK - Temperature: 1.8° C, Conditions: light rain
Newcastle, UK - Temperature: 2.6° C, Conditions: scattered clouds
Bucharest, Romania - Temperature: 9.3° C, Conditions: scattered clouds
Cluj-Napoca, Romania - Temperature: 6.4° C, Conditions: scattered clouds
Ottawa, Canada - Temperature: -7.0° C, Conditions: overcast clouds
Toronto, Canada - Temperature: -7.0° C, Conditions: broken clouds
Lisbon, Portugal - Temperature: 14.6° C, Conditions: overcast clouds
Porto, Portugal - Temperature: 12.2° C, Conditions: moderate rain
Raleigh, USA - Temperature: 3.9° C, Conditions: Sky is Clear
Washington, USA - Temperature: 3.4° C, Conditions: light rain
---- Fetched in 1820ms ----
Things will get more interesting in the next step.


Create User
Your name:
Superheroes movies!
Please select your favorite movie
Deadpool
Batman v Superman
Captain America: Civil War
Doctor Strange
Suicide Squad
X-Men: Apocalypse
Guardians of the Galaxy Vol 2
Justice League
Logan
Spider-Man: Homecoming
Wonder Woman
Thor: Ragnarok
Black Panther
Upload your avatar!
Add new user


CableLabs Micronets
Developer documentation for CableLabs Micronets
Micronets Home
About Micronets
Home
>
Micronets
>
Tags
Next - Getting Started
Home
Getting Started
Micronets Gateway
Example /etc/network/interfaces
Server Components
Micronets Manager
Identity Server
MSO Portal
Registration Server
Authorization Server
Idora Server
MUD Services
Websocket Proxy
Using Docker
Test Components
Idora Client App
QR Code Scanner
ProtoMed Device


This has been a crazy busy year so far. I’ve been doing tons, but I’m still way behind on my list. I’ve had maybe one full-day off from anything business-related since Christmas.
One consequence is that I have not really gotten started blogging here.
So, I’m taking next week off from client work. No billable hours, but I need the time.
If I’m able, I’ll try to write up a full & proper post. Or, at least, a non-micro post.


enum class AttachmentType
(source)
image |
|
audio |
|
video |
|
file |
|
template |
toTockAttachmentType |
fun toTockAttachmentType(): AttachmentType |
fromTockAttachmentType |
fun fromTockAttachmentType(type: AttachmentType): AttachmentType |


pdf
Interface to create a PDF document.
File information
Classes
IPdfProvider
class IPdfProvider {
public:
virtual ~IPdfProvider() { };
virtual class IPdf * CreatePdf(class IInstanceLog * log = 0) = 0;
};
Public functions
CreatePdf
-
Creates an IPdf object. This object is to be deleted after use.
Parameters
| class IInstanceLog log |
If given and the app tracing is enabled, error messages are logged. |
IPdf
class IPdf {
public:
virtual ~IPdf() { };
enum class InfoType {
Author,
Creator,
Title,
Subject,
Keywords,
};
enum Compressions {
CompressionNone = 0x0,
CompressionText = 0x1,
CompressionImage = 0x2,
CompressionMetaData = 0x4,
CompressionAll = 0xf,
};
enum Directions {
DirectionPortrait,
DirectionLandscape,
};
enum Sizes {
SizeA4,
};
enum class DefaultFont {
Courier,
Helvetica,
Times,
};
enum class FontWeight {
Normal,
Bold,
};
enum class FontStyle {
Normal,
Italic,
};
enum class TextHAlign {
Left,
Right,
Center,
};
enum StreamTypes {
StreamTypeCcittG31D,
};
virtual class IPdf & SetInfo(InfoType type, const char * info) = 0;
virtual class IPdf & SetCompressionMode(unsigned compressionMode) = 0;
virtual class IPdf & SetFont(const class IPdfFont * font) = 0;
virtual class IPdf & SetFontSize(unsigned int fontSize) = 0;
virtual class IPdf & SetMargin(float all) = 0;
virtual class IPdf & SetMargin(float top, float right, float bottom, float left) = 0;
virtual class IPdfFont * AddFont(const char * fontFileName) = 0;
virtual class IPdfFont * AddFont(DefaultFont font = DefaultFont::Helvetica,
FontWeight weight = FontWeight::Normal,
FontStyle style = FontStyle::Normal) = 0;
virtual const class IPdfColor * AddColor(float gray) = 0;
virtual class IPdfImage * AddPngImage(const byte * data, unsigned int length) = 0;
virtual class IPdfPage * AddPage(enum IPdf::Sizes size = IPdf::SizeA4,
enum IPdf::Directions direction = IPdf::DirectionPortrait) = 0;
virtual void Complete() = 0; // Obsolete
virtual void Get(const byte * & data, unsigned & length, bool * last = 0) = 0;
};
Public functions
SetInfo
-
With this function serveral information of the PDF file can be set. The types are: the author, the creator, the title, the subject or keywords.
Parameters
| InfoType type |
The type of the information which is set. |
| const char * info |
The text in UTF-8 encoding. |
Return value
Returns itself as reference.
SetCompressionMode
- The function sets the compression mode of the PDF document.
Parameters
| unsigned compressionMode |
Bit mask which type of content should be compressed. |
Return value
Returns itself as reference.
SetFont
-
Sets the current font to be used.
Parameters
| const class IPdfFont * font |
A font added to the document before. |
Return value
Returns itself as reference.
SetFontSize
-
Sets the current font size to be used.
Parameters
| unsigned int font-size |
The font size. |
Return value
Returns itself as reference.
SetMargin
-
Sets the margin of the document used for the first page. Further pages use the current margin of the last page.
Parameters
| float all |
Sets all four margins to this value. |
SetMargin
-
Sets the margin of the document used for the first page. Further pages use the current margin of the last page.
Parameters
| float top |
The top margin value. |
| float right |
The right margin value. |
| float bottom |
The bottom margin value. |
| float left |
The left margin value. |
AddFont
-
Loads a true type font file exists in the local directory with the given file name for later usage. This font is embedded in the generated PDF file.
Parameters
| const char * fontFileName |
The file name of the font. |
Return value
Returns the font handle if succeeds, otherwise zero.
AddFont
-
Adds a standard PDF font to the document which needn't to be embedded in the PDF file. The used encoding is LATIN-1. The expected UTF-8 text is transcribed into this encoding.
Parameters
| DefaultFont font |
(Default DefaultFont::Helvetica)The font. |
| FontWeight weight |
(Default FontWeight::Normal)The font weight. |
| FontStyle style |
(Default FontStyle::Normal)The font style. |
Return value
Returns the font handle if succeeds, otherwise zero.
AddColor
-
Adds a gray value as color to the document for later usage.
Parameters
| float gray |
The gray value. Zero is black, one is white. |
Return value
Returns the color handle.
AddPngImage
-
Loads a PNG image from memory which is embedded in the PDF file and can be shown at several document positions later.
Parameters
| const byte * data |
The PNG data. |
| unsigned int length |
The PNG data length. |
Return value
Returns the image handle if succeeds, otherwise zero.
AddPage
- This function adds a new page to the document.
Parameters
| enum IPdf::Sizes size |
(Default IPdf::SizeA4) The size of the page. |
| enum IPdf::Directions direction |
(Default IPdf::DirectionPortrait) The direction of the page. |
Return value
Returns the new page.
Complete
- The function is obsolete. Don't use it.
Get
-
Get the document data. The data pointer is set to a pointer allocated by IPdf. The end of the document is reached if length is zero or last is true.
Parameters
| const byte * & data |
Reference to the data pointer which is set by the function to the internal data. |
| unsigned & length |
Reference to a unsigned variable which is set by the function to the data length. |
| bool * last |
(Default 0) Reference to a bool variable, whose value is set by the function. The value is set to true if the end of the data is reached.
This parameter can also be a null pointer, in which case it is not used. |
IPdfFont
Overview
A font object handled by the PDF document.
IPdfColor
Overview
A color object handled by the PDF document.
IPdfImage
Overview
A image object handled by the PDF document.
IPdfPage
class IPdfPage {
public:
virtual class IPdfPage * GetPreviousPage() = 0;
virtual const class IPdfPage * GetPreviousPage() const = 0;
virtual class IPdfPage * GetNextPage() = 0;
virtual const class IPdfPage * GetNextPage() const = 0;
virtual enum IPdf::Sizes GetSize() const = 0;
virtual enum IPdf::Directions GetDirection() const = 0;
virtual float GetWidth() const = 0;
virtual float GetHeight() const = 0;
virtual const class IPdfDocumentPosition & GetContentStart() const = 0;
virtual const class IPdfDocumentPosition & GetContentEnd() const = 0;
virtual void SetSize(enum IPdf::Sizes size) = 0;
virtual void SetDirection(enum IPdf::Directions direction) = 0;
virtual void SetMargin(float all) = 0;
virtual void SetMargin(float top, float right, float bottom, float left) = 0;
virtual unsigned int AddText(const char * text,
const class IPdfDocumentPosition & position,
IPdf::TextHAlign align = IPdf::TextHAlign::Left,
float maxWidth = 0,
float maxHeight = 0,
float * height = 0) = 0;
virtual void AddImage(const class IPdfImage * image,
float positionX,
float positionY,
float width,
float height) = 0;
virtual void AddBackground(const class IPdfColor * color,
const class IPdfDocumentPosition & startPosition,
const class IPdfDocumentPosition & endPosition) = 0;
virtual void AddHorizontalLine(const class IPdfDocumentPosition & startPosition,
float length,
float lineWidth,
const class IPdfColor * color) = 0;
virtual class IPdfImageStream * AddImageStream(enum IPdf::StreamTypes type) = 0;
virtual class IPdfTable * AddTable(const class IPdfDocumentPosition * startPosition = 0) = 0;
virtual void Complete() = 0; // Obsolete
protected:
virtual ~IPdfPage() { };
};
Public functions
GetPreviousPage
-
Gets the previous page of this page.
Return value
Returns a handle of a page, if a previous page exists, otherwise zero.
GetNextPage
-
Gets the next page of this page.
Return value
Returns a handle of a page, if a next page exists, otherwise zero.
GetSize
-
Gets the size format of this this page.
Return value
Returns the format type.
GetDirection
-
Gets the direction of this this page.
Return value
Returns the direction type: portrait or landscape.
GetWidth
- Gets the page width.
Return value
Returns the width of the page.
GetHeight
- Gets the page height.
Return value
Returns the height of the page.
GetContentStart
-
Gets the left upper position of this page which considers the page margin.
Return value
Returns a constant document position.
GetContentEnd
-
Gets the right lower position of this page which considers the page margin.
Return value
Returns a constant document position.
SetSize
- Set the page size.
Parameters
| enum IPdf::Sizes size |
The supported size is A4. |
SetDirection
- Set the page direction.
Parameters
| enum IPdf::Directions direction |
Portrait or landscape. |
SetMargin
-
Sets a new margin of the this page.
Parameters
| float all |
Sets all four margins to this value. |
SetMargin
-
Sets a new margin of the this page.
Parameters
| float top |
The top margin value. |
| float right |
The right margin value. |
| float bottom |
The bottom margin value. |
| float left |
The left margin value. |
AddText
-
Adds UTF-8 encoded text within a given space to this page beginning at the given start position. The page of the document position is ignored, this page is used. No page break is done.
Parameters
| const char * text |
The text to be added. |
| const class IPdfDocumentPosition & position |
The start position of the text. |
| IPdf::TextHAlign align |
(Default IPdf::TextHAlign::Left) The horizontal alignment of the text. |
| float maxWidth |
(Default 0) The available width for the text. If it is set, the page's right content margin is ignored, otherwise the width from the horizontal start position to the right content margin is used. |
| float maxHeight |
(Default 0) The available height for the text. If it isn't set, the height from the vertical start position to the bottom margin is used. The configured page bottom margin isn't considered. |
| float * height |
(Default 0) If the pointer is set, the used height is written. |
Return value
Returns the number of the bytes which could be added on this page within the available space.
AddImage
-
Adds an image of the document to this page at the given position.
Parameters
| const class IPdfImage * image |
The image handle. |
| float positionX |
The horizonal left position for the image in pixel. |
| float positionY |
The vertical bottom position for the image in pixel. |
| float width |
The width for the image in pixel. |
| float height |
The height for the image in pixel. |
AddBackground
-
Adds a background in the defined color within two corners.
Parameters
| const class IPdfColor * color |
A color handle. |
| const class IPdfDocumentPosition & startPosition |
The left upper corner. |
| const class IPdfDocumentPosition & endPosition |
The right lower corner. |
AddHorizontalLine
-
Adds a horizontal line with a defined length, width and color on this page.
Parameters
| const class IPdfDocumentPosition & startPosition |
The start position for the line. |
| float length |
The length of the line in pixel. |
| float lineWidth |
The width of the line in pixel. |
| const class IPdfColor * color |
The color of the line. |
AddImageStream
- Adds an image stream to the page.
Parameters
| enum IPdf::StreamTypes type |
The supported type is one-dimentional G3 data. |
Return value
Returns a handle to the image stream.
AddTable
-
Adds a new table to this page.
Parameters
| const class IPdfDocumentPosition * startPosition |
(Default 0) If set, the table starts at this position within this page. Otherweise the content start position of this page is used. |
Return value
Returns the handle of the new table.
Complete
- This function is obsolete.
IPdfDocumentPosition
class IPdfDocumentPosition {
public:
virtual class IPdfPage * GetPage() const = 0;
virtual float GetHorizontalPosition() const = 0;
virtual float GetVerticalPosition() const = 0;
virtual class IPdfDocumentPosition & Move(float horizontalRight, float verticalDown) = 0;
virtual class IPdfDocumentPosition & MoveTo(const class IPdfDocumentPosition & position) = 0;
virtual class IPdfDocumentPosition * Clone() const = 0;
protected:
IPdfDocumentPosition& operator=(const IPdfDocumentPosition&) = default;
~IPdfDocumentPosition() = default;
};
Overview
The IPdfDocumentPosition object handles a valid position within a PDF document.
Public functions
GetPage
-
Returns the page of this document position.
GetHorizontalPosition
-
Returns the horizontal position in pixel.
GetVerticalPosition
-
Returns the vertical position in pixel.
Move
-
Moves the current position within the current page for the given values in pixel in direction right and down.
Parameters
| float horizontalRight |
The value in pixel for the horizontal direction. A negative value moves left. |
| float verticalDown |
The value in pixel for the vertical direction. A negative value moves upwards. |
MoveTo
-
Moves to another given document position.
Parameters
| const class IPdfDocumentPosition & position |
The new position. |
Clone
-
Returns a created document position with the current position. The object is handled by the PDF document, can be used, but not be deleted and is valid till the PDF document is deleted.
IPdfImageStream
class IPdfImageStream {
public:
virtual ~IPdfImageStream() { };
virtual void Write(const byte * data, unsigned length) = 0;
virtual void SetStreamWidth(unsigned int width) = 0;
virtual void SetStreamHeight(unsigned int height) = 0;
virtual void Draw(float x, float y, float width, float height) = 0;
};
Public functions
Write
- The function is to be called to write data into the image stream.
Parameters
| const byte * data |
Pointer to the data block to write. |
| unsigned length |
Length of the data block to write. |
SetStreamWidth
- This function must be called to set the internal width parameter to the width of the written image.
Parameters
| unsigned int width |
The width in pixel. |
SetStreamHeight
- This function must be called to set the internal height parameter to the height of the written image.
Parameters
| unsigned int height |
The height in pixel. |
Draw
-
The function is to be called if the stream is complete. After this, IPdfImageStream is invalid.
Parameters
| float x |
Horizontal start position of the image in the page. |
| float y |
Vertical start position of the image in the page. |
| float width |
Width of the image in the page. |
| float height |
Height of the image in the page. |
IPdfTable
class IPdfTable {
public:
virtual ~IPdfTable() = default;
virtual const class IPdfDocumentPosition & GetEndPosition() const = 0;
virtual class IPdfTable & SetFont(const class IPdfFont * font) = 0;
virtual class IPdfTable & SetContentMargin(float all) = 0;
virtual class IPdfTable & SetContentMargin(float top, float right, float bottom, float left) = 0;
virtual class IPdfTable & SetHorizontalLine(float width, const class IPdfColor * color) = 0;
virtual class IPdfTable & SetEvenRowBackground(const class IPdfColor * color) = 0;
virtual class IPdfTable & SetOddRowBackground(const class IPdfColor * color) = 0;
virtual class IPdfTableHeader * AddHeader() = 0;
virtual class IPdfTableColumn * AddColumn(float width,
IPdf::TextHAlign align = IPdf::TextHAlign::Left) = 0;
virtual void AddRows(class UPdfTable * user,
unsigned int count = 1) = 0;
};
Public functions
SetFont
-
Sets the font of the table content.
Parameters
| const class IPdfFont * font |
A font added to the document before. |
SetContentMargin
-
Sets the margin width for the table content fields.
Parameters
| float all |
Sets all four margins to this value. |
SetContentMargin
-
Sets the margin width for the table content fields.
Parameters
| float top |
The top margin value. |
| float right |
The right margin value. |
| float bottom |
The bottom margin value. |
| float left |
The left margin value. |
SetHorizontalLine
-
Configures a horizontal line between rows.
Parameters
| float width |
The line width in pixel. |
| const class IPdfColor * color |
A color added to the document before. |
SetEvenRowBackground
-
Sets the background color of the even rows.
Parameters
| const class IPdfColor * color |
A color added to the document before. |
SetOddRowBackground
-
Sets the background color of the odd rows.
Parameters
| const class IPdfColor * color |
A color added to the document before. |
-
Adds a table header to this table which can be configured. The header is added to the page with the first row added to the table.The UPdfTable object is used to get the table header content.
AddColumn
-
Defines a column added to the table. Must be called before rows are added.
Parameters
| float width |
The column width in pixel. |
| IPdf::TextHAlign align |
The horizontal text alignment of this column. |
AddRows
-
Adds a number of rows to this table. The UPdfTable object is used to get the field contents.
Parameters
| class UPdfTable * user |
A UPdfTable object for the call-back functions. |
| unsigned int count |
The number of the rows to be addes to this table. |
GetEndPosition
-
Gets the current end position of the table in the document.
UPdfTable
class UPdfTable {
public:
virtual const char * GetFieldContent(class IPdfTable * table,
unsigned int row,
unsigned int column,
const class IPdfDocumentPosition & startPosition,
class IPdfDocumentPosition & endPosition) = 0;
virtual const char * GetHeaderContent(class IPdfTable * table,
unsigned int column,
const class IPdfDocumentPosition & startPosition,
class IPdfDocumentPosition & endPosition) { return 0; };
};
This class defines the call-back functions needed to use the IPdfTable.
Public functions
GetFieldContent
-
This function is called for every row is to be added to the table and for every column of the row. It gets the field content in the return value reference. This return value must be valid till the next function call or the AddRows function returns.
Parameters
| class IPdfTable * table |
It is set to the table which is called the AddRows function. |
| unsigned int row |
It is set to the current row number beginning from zero. |
| unsigned int column |
It is set to the current column number beginning from zero. |
| const class IPdfDocumentPosition & startPosition |
It is set to the content field start position considered the left margin. |
| class IPdfDocumentPosition & endPosition |
It is a given reference to the content field end position which can be changed to a lower vertical position to enhance the row height. |
-
This function is called for every column of the table header to get the field content in the return value reference. This return value must be valid till the next function call or the GetFieldContent function call.
Parameters
| class IPdfTable * table |
It is set to the table which is called the AddRows function. |
| unsigned int column |
It is set to the current column number beginning from zero. |
| const class IPdfDocumentPosition & startPosition |
It is set to the column start position considered the left margin. |
| class IPdfDocumentPosition & endPosition |
It is a given reference to the content field end position which can be changed to a lower vertical position to enhance the header line height. |
IPdfTableHeader
class IPdfTableHeader {
public:
virtual class IPdfTableHeader & SetFont(const class IPdfFont * font) = 0;
virtual class IPdfTableHeader & SetHorizontalLine(float width, const class IPdfColor * color) = 0;
protected:
~IPdfTableHeader() = default;
};
-
Sets the font of the table header text.
Parameters
| const class IPdfFont * font |
A font added to the document before. |
-
Defines a horizontal line after the table header.
Parameters
| float width |
The line width in pixel. |
| const class IPdfColor * color |
A color added to the document before. |


echoframework
/
org.echo.mobile.framework.support
/
EthAddressValidator
/
isAddressValid
isAddressValid
fun
isAddressValid
(
ethAddress
:
String
)
:
Boolean
Enter point of address validation process


Good Day, I am writing this letter with confidence believing that if it is the wish of God for you to help me and my younger brother, God almighty will bless and reward you aboundantly and you would never regreat of helping us,i know that you will be surprise to recieve this mail,before i go on let me tell you a little bit of myself,my name is Miss Mariam Sinko from republic of Liberia in west Africa,i and my younger brother Johnson jr.Sinko were the only surviving children of our late father Mr.jonhson sinko. My late father was a dealer of row Gold and Diamond, he was a very prosperous businessman, infact they call him the richest man in the town of Lofa,but he was killed one early morning on 20/4/2003 by the rebels,may his soul rest in peace,those rebels broke in and captured the town of vangerma which is the main city in lofa county,killing and looting,it was there my family has been executed,they killed my father and mother with my three younger once,i and my only brother johnson jr. the only son we have were saved because were at school when the whole insindant was happning then we ran into forest,it was a long story,we have under go so many diffcuties,but i thank God for our life,so when we get back to our house all our family has been killed i dont know what to do cos the rebels have loots everything in our house, luckly to us,i found my fathers suitcase with some documents showing that he deposited the sum of five million five hundred thousand united state dollars in a financial/security company in Abroad with my younger brother's name as his next of kin so we made away with these documents.so what we need is a trusted and God fearing person who shall help us secure this money into his account in which we shall meet him for him to invest the money for us and we shall contuine our school,the person will take us as his own children, on hearing from you we shall give you the contact of the holding firm for you to discuss on our behalf,awaits to hear from you as you read this mail.you can also contact us at<EMAIL_ADDRESS>; i remain with the best of regards. Mariam Sinko.


A sentinel will continue to operate properly and protect its verifiers even if it runs out of disk space. However, it will be unable to write new block files to disk. The next time the sentinel process initializes, it will not have recent blocks, and it will have to follow the blockchain for 4 cycles to begin protecting its managed verifiers again.
To ensure that sentinel disk-space issues do not go unnoticed, indication of available disk space could be added to the sentinel web interface. This would allow sentinel operators to easily track disk space across multiple sentinels without the need for separate monitoring tools.
NTTP-6: we propose adding disk-space monitoring to the sentinel web interface
Available disk space would be displayed above the Protecting verifiers line in the top section of the sentinel interface. Color-coding (green, yellow, red) would be according to user-adjustable thresholds.
This NTTP will be implemented without payment.


Multiplay examples
I took the Pointerlock example from mrdoob (the creator of the famous three.js JavaScript library) and created a small prototype to showcase multiplayer and multiple viewport capabilities.
Viewports example
Multiplayer example
These will work best if you open multiple tabs/browsers.
u1
v1
The MIT License (MIT), Copyright (c) 2014 Dirk Krause, dirkk0@gmail.com


Rob Gronkowski Scolds Tom Brady, Patriots For Their Negativity: ‘I Don’t Miss That’ (VIDEO)
by Darrelle LincolnLike most people, Rob Gronkowski noticed Tom Brady’s reaction to the New England Patriots’ win over the Philadelphia Eagles last week and he instantly knew that he did not miss playing for the Patriots.
Brady was upset about the offense not being able to get it together and even expressed deeper frustrations in a radio interview on WEEI 24 hours after the game.
On Sunday, Gronk, who is serving as an NFL analyst for FOX, basically called out his former team for being so negative after a loss.
“He’s so frustrated, too. It’s like, ‘Yo, you guys are 9-1.’ That’s one part I don’t miss about being there. Hand down. I’m not going to lie. I don’t miss that,” Gronkowski said on air before Sunday’s Week 12 games began. “They’re frustrated. They’re 9-1. They win a game against Philly last week. We lost to them two years ago in the Super Bowl. They should be happy. Instead, you’re sitting there Sunday night thinking, ‘What did I do wrong?’ No, that’s not the feeling you should be having. But you won the game. Enjoy it. Go out next week, and build off it.”
As far as Gronk coming back to the Patriots this season, he also cleared those rumors by stating he would not.


OU’s Campus Recreation has been preparing for an eventful fall. Within Campus Recreation, there are multiple sectors, including, but not limited to, fitness, competitive sports and outdoor pursuits.
Tony Gregory, assistant director for University Well-Being and Fitness, said fitness classes will begin to be in-person. Of the approximate 25 classes a week, 75-80% will be a new F45 training program. The remaining percent of classes will be traditional group fitness classes, such as cardio, dance, yoga or cycling.
Those interested in the F45 classes will have to possess a semester or month membership, depending on the level of commitment. However, F45 classes are free as of right now and the first week of classes.
There will also be one-on-one and private training sessions.
“I think, especially for first-year students, when you're coming into a new setting, away from your parents, I think it really helps reinforce creating a strong sense of belonging with the university and establishing Ohio University as a place of comfort,” Gregory said.
Gregory said OU will feel more like home when students get involved with new activities.
Along with fitness, Nathan Ferdinand, assistant director for University Competitive Sports and Community Programming, said involving oneself in sports can be another useful outlet.
In the fall, intramural sports and club sports will begin, operating at a larger capacity than last year. Registration will begin during Party at Ping on Aug. 21 and sports will start mid-September.
Some sports that are open for registration include ultimate frisbee, softball, 4 v. 4 mini soccer and 2 v. 2 sand volleyball. Flag football and 7 v. 7 soccer will be making a return this fall as well. Students can join a three week program competitively or a five week program recreationally.
Additionally, there will be weekend tournaments like badminton, dodgeball and water basketball in the Aquatic Center.
“Having things to help connect you to the community – help keep you active – it really promotes not only a sense of belonging but your overall well-being,” Ferdinand said. “It's also, for a lot of people, a way to stay physically active. We offer a lot of that within our department, to keep people physically engaged, motivated and involved throughout the year.”
Ferdinand said these opportunities are a way to build relationships and form friendships that will last throughout students’ OU experiences.
Caeley Grady, a graduate assistant with Outdoor Pursuits, said Outdoor Pursuits has a full schedule this fall, including many trips and hiking.
There are also backpacking trips coming up in October, specifically to Zaleski State Forest and Grayson Highlands State Park.
The rock climbing wall in Ping will also be open for use starting Aug. 30, Monday through Saturday. The challenge course will also be open for team building and low-rope courses.
“We're trying to create community between campus and other students,” Grady said. “This is my first year as a graduate assistant, but in my undergraduate, I participated in a lot of outdoor pursuits and a lot of outdoor pursuit trips. When I was there, I gained a lot of new friends and met a lot of new people. I was able to network with a lot of new people.”
Grady said no one has to be an expert or even knowledgeable on outdoor pursuits to join on the trips. Outdoor Pursuits encourages all – beginners and experienced – to participate.
Gregory, Ferdinand and Grady all agree these physical activities are not only beneficial to physical health but mental health too.
“We recognize mental health is at the forefront of the conversation, especially as we are in the middle of a pandemic,” Gregory said. “Being able to cope with stress through recreation (is) one of the main reasons that we do the work that we do – to provide students with that outlet. When they are stressed with classes, when they feel like they don't have a place to go or when they feel like they need to meet new people and build those positive relationships, they can participate in our programs and contribute to their well-being and help take care of themselves as well as a student.”
“We recognize mental health is at the forefront of the conversation, especially as we are in the middle of a pandemic. Being able to cope with stress through recreation (is) one of the main reasons that we do the work that we do – to provide students with that outlet."—Tony Gregory, assistant director for University Well-Being and Recreation, Well-Being and Fitness
Grady said she believes the programs are made to boost the mental health of students. Ferdinand also believes the programs are made to separate the students from their academic life and take a moment to de-stress through an active outlet.
Dylan Westmeyer, a sophomore studying journalism, said joining club tennis gave him an opportunity to clear his mind after a stressful week or help him through a difficult time.
“If the student can find something to take their mind off these complications for even an hour a day I feel as though they will feel better and be able to focus more on the difficult portions of college,” Westmeyer said in a message.


Which service are you interested in?
Unleashing Innovation
Design Thinking and Experimentation
Rapid Prototyping
|
Business Intimacy
We have an intimate understanding of your business to support you in taking an innovative approach to solve business challenges.
|
Expertise & Capability
We have a talented team of experts to empower you with the mindset, methods, and tools that fosters Innovation.
|
Fresh Perspective
We bring a fresh and unbiased perspective to help challenge the status quo and encourage outside of the box thinking.
|
|
Art of the Possible
We demonstrate how to look to the future and leverage emerging technologies such as augmented reality and HoloLens.
|
Value
Innovation Capability rates are significantly lower than external providers for comparable services.
|
|
Eddy Ku,
Innovation Capability Lead |
Eryk Korfel,
Innovation Capability Coach |
Amy Lai,
Innovation Capability Coach |
Jesse Arundell,
Open Innovation Consultant |
|
Raymon Manalo,
UX & Rapid Prototyping Specialist |
Marc Sorio,
UX & Rapid Prototyping Specialist |
Justin De Guzman,
UX & UI Developer |
Brandon "The Boss" Cheung,
The Boss |
|
CommBank Intrapreneur 2017
Leveraging the Unleashing Innovation platform, to host CommBank’s biggest global innovation competition – creating the future of CommBank and the world around you.
Services used: Unleashing Innovation, Coaching
|
JumpStart
Empowering Indigenous businesses through Design Thinking to help them develop and grow their business, through an innovative approach to solving their challenges.
Services used: Coaching, Prototyping
|
HoloTraining
Partnering with the Emerging Technology Team to explore the capability of Microsoft HoloLens and how it could disrupt the future of the bank.
Services used: Prototyping - Immersive Experiences
|